empty reply from server error

[Globe Trotter]

Hello,

I was trying to fix a minor but severe error in the packging of osmo, and I get the
following error:


$ fedpkg import ~/rpmbuild/SRPMS/osmo-0.4.4-2.fc36.src.rpm
 
Could not execute import_srpm: (52, 'Empty reply from server')


Where is this error from and how do I get around it?

Thanks in advance for any suggestions!

[Globe Trotter]

Never mind, I figured this out. Bad oversight on my part.



However, I get the following error in the build log (of koji):



checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
configure: error: C compiler cannot create executables
See `config.log' for more details


Where is the config.log? I only have 

build.log (tail)
hw_info.log (tail)
mock_output.log (tail)
root.log (tail)
state.log (tail)

Thanks again!








On Tuesday, July 19, 2022 at 08:33:57 AM CDT, Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote: 





Hello,

I was trying to fix a minor but severe error in the packging of osmo, and I get the
following error:


$ fedpkg import ~/rpmbuild/SRPMS/osmo-0.4.4-2.fc36.src.rpm
 
Could not execute import_srpm: (52, 'Empty reply from server')


Where is this error from and how do I get around it?

Thanks in advance for any suggestions!
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Petr Pisar]

V Tue, Jul 19, 2022 at 01:47:12PM +0000, Globe Trotter via devel napsal(a):
>  However, I get the following error in the build log (of koji):
>  
>  
>  
>  checking whether the C compiler works... no
>  configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
>  configure: error: C compiler cannot create executables
>  See `config.log' for more details
>
>  
>  Where is the config.log? I only have 
>  
In the working directory on a Koji builder. Cleaned up and deleted.

Ammend your osmo.spec to print config.log content if ./configure command
fails.  The cause will either be missing BuildRequires: gcc, or the build
scripts is too creative with compiler or linker flags and produces
a combination which does not work. Or somebody broke gcc or annobin or other
vital part of a tool chain.

-- Petr

[Adam Williamson]

On Tue, 2022-07-19 at 16:47 +0200, Petr Pisar wrote:
>  V Tue, Jul 19, 2022 at 01:47:12PM +0000, Globe Trotter via devel
> napsal(a):
>  > However, I get the following error in the build log (of koji):
>  > 
>  > 
>  > 
>  > checking whether the C compiler works... no
>  > configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
>  > configure: error: C compiler cannot create executables
>  > See `config.log' for more details
>  > 
>  > 
>  > Where is the config.log? I only have 
>  > 
>  In the working directory on a Koji builder. Cleaned up and deleted.
>  
>  Ammend your osmo.spec to print config.log content if ./configure command
>  fails.  The cause will either be missing BuildRequires: gcc, or the build
>  scripts is too creative with compiler or linker flags and produces
>  a combination which does not work. Or somebody broke gcc or annobin or other
>  vital part of a tool chain. 
Another option if the necessary stuff isn't logged to the Koji build
logs is to run a build in mock locally. When a mock build fails the
buildroot is not cleaned up, so you can look at it, either under
wherever your mock home is (/var/lib/mock or /home/mockbase probably)
or with mock -r (whatever) -shell to get a shell inside the mock
environment.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

[Globe Trotter]

Never mind, I figured this out. Bad oversight on my part.



However, I get the following error in the build log (of koji):



checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
configure: error: C compiler cannot create executables
See `config.log' for more details


Where is the config.log? I only have

build.log (tail)
hw_info.log (tail)
mock_output.log (tail)
root.log (tail)
state.log (tail)

Thanks again!









On Tuesday, July 19, 2022 at 08:33:57 AM CDT, Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote: 





Hello,

I was trying to fix a minor but severe error in the packging of osmo, and I get the
following error:


$ fedpkg import ~/rpmbuild/SRPMS/osmo-0.4.4-2.fc36.src.rpm
 
Could not execute import_srpm: (52, 'Empty reply from server')


Where is this error from and how do I get around it?

Thanks in advance for any suggestions!
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Jerry James]

On Tue, Jul 19, 2022 at 7:52 AM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  checking whether the C compiler works... no
>  configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
>  configure: error: C compiler cannot create executables
>  See `config.log' for more details
>
>
>  Where is the config.log? 
config.log is in the buildroot.  Try running "koji save-failed-tree
<taskid>", where <taskid> is the task ID koji gave you when you
started the build.  That will give you a tarball containing the
buildroot.  Look in there for config.log.

Also, see /usr/share/doc/koji/docs/source/plugins.rst for how to
download only parts of the buildroot; e.g., config.log only.
-- 
Jerry James
http://www.jamezone.org/

[Globe Trotter]

Thanks, btw, the command here says unknown command (see below).

Btw, the log is here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2004683

Thanks!



$ koji save-failed-tree 2004683
Available commands:

admin commands:
        add-channel               Add a channel
        add-external-repo         Create an external repo and/or add one to a tag
        add-group                 Add a group to a tag
        add-group-pkg             Add a package to a group's package listing
        add-group-req             Add a group to a group's required list
        add-host                  Add a host
        add-host-to-channel       Add a host to a channel
        add-pkg                   Add a package to the listing for tag
        add-tag                   Add a new tag to the database
        add-tag-inheritance       Add to a tag's inheritance
        add-target                Create a new build target
        add-user                  Add a user
        add-volume                Add a new storage volume
        assign-task               Assign a task to a host
        block-group               Block group in tag
        block-group-pkg           Block a package from a group's package listing
        block-group-req           Block a group's requirement listing
        block-pkg                 Block a package in the listing for tag
        clone-tag                 Duplicate the contents of one tag onto another tag
        disable-channel           Mark one or more channels as disabled
        disable-host              Mark one or more hosts as disabled
        disable-user              Disable logins by a user
        edit-channel              Edit a channel
        edit-external-repo        Edit data for an external repo
        edit-host                 Edit a host
        edit-permission           Edit a permission description
        edit-tag                  Alter tag information
        edit-tag-inheritance      Edit tag inheritance
        edit-target               Set the name, build_tag, and/or dest_tag of an existing
build target to new values
        edit-user                 Alter user information
        enable-channel            Mark one or more channels as enabled
        enable-host               Mark one or more hosts as enabled
        enable-user               Enable logins by a user
        free-task                 Free a task
        grant-cg-access           Add a user to a content generator
        grant-permission          Grant a permission to a user
        import                    Import externally built RPMs into the database
        import-archive            Import an archive file and associate it with a build
        import-cg                 Import external builds with rich metadata
        import-sig                Import signatures into the database and write signed
RPMs
        list-signed               List signed copies of rpms
        lock-tag                  Lock a tag
        make-task                 Create an arbitrary task
        prune-signed-copies       Prune signed copies
        regen-repo                Force a repo to be regenerated
        remove-channel            Remove a channel entirely
        remove-external-repo      Remove an external repo from a tag or tags, or remove
entirely
        remove-group              Remove group from tag
        remove-host-from-channel  Remove a host from a channel
        remove-pkg                Remove a package from the listing for tag
        remove-sig                Remove signed RPMs from db and disk
        remove-tag                Remove a tag
        remove-tag-inheritance    Remove a tag inheritance link
        remove-target             Remove a build target
        restart-hosts             Restart enabled hosts
        revoke-cg-access          Remove a user from a content generator
        revoke-permission         Revoke a permission from a user
        set-build-volume          Move a build to a different volume
        set-pkg-arches            Set the list of extra arches for a package
        set-pkg-owner             Set the owner for a package
        set-pkg-owner-global      Set the owner for a package globally
        set-task-priority         Set task priority
        unblock-group-pkg         Unblock a package from a group's package listing
        unblock-group-req         Unblock a group's requirement listing
        unblock-pkg               Unblock a package in the listing for tag
        unlock-tag                Unlock a tag
        userinfo                  Show information about a user
        write-signed-rpm          Write signed RPMs to disk

bind commands:
        move-build                'Move' one or more builds between tags
        tag-build                 Apply a tag to one or more builds
        untag-build               Remove a tag from one or more builds

build commands:
        build                     Build a package from source
        cancel                    Cancel tasks and/or builds
        chain-build               Build one or more packages from source
        image-build               Create a disk image given an install tree
        image-build-indirection   Create a disk image using other disk images via the
Indirection plugin
        maven-build               Build a Maven package from source
        maven-chain               Run a set of Maven builds in dependency order
        resubmit                  Retry a canceled or failed task, using the same
parameter as the original task.
        spin-appliance            Create an appliance given a kickstart file
        spin-livecd               Create a live CD image given a kickstart file
        spin-livemedia            Create a livemedia image given a kickstart file
        win-build                 Build a Windows package from source
        wrapper-rpm               Build wrapper rpms for any archives associated with a
build.

download commands:
        download-build            Download a built package
        download-logs             Download logs for task
        download-task             Download the output of a build task

info commands:
        buildinfo                 Print basic information about a build
        help                      List available commands
        hostinfo                  Print basic information about a host
        latest-build              Print the latest builds for a tag
        list-api                  Print the list of XML-RPC APIs
        list-buildroot            List the rpms used in or built in a buildroot
        list-builds               Print the build listing
        list-channels             Print channels listing
        list-external-repos       List external repos
        list-groups               Print the group listings
        list-history              Display historical data
        list-hosts                Print the host listing
        list-permissions          List user permissions
        list-pkgs                 Print the package listing for tag or for owner
        list-tag-inheritance      Print the inheritance information for a tag
        list-tagged               List the builds or rpms in a tag
        list-tags                 Print the list of tags
        list-targets              List the build targets
        list-tasks                Print the list of tasks
        list-untagged             List untagged builds
        list-volumes              List storage volumes
        mock-config               Create a mock config
        rpminfo                   Print basic information about an RPM
        show-groups               Show groups data for a tag
        taginfo                   Print basic information about a tag
        taskinfo                  Show information about a task

miscellaneous commands:
        call                      Execute an arbitrary XML-RPC call
        dist-repo                 Create a yum repo with distribution options
        import-comps              Import group/package information from a comps file
        moshimoshi                Introduce yourself
        version                   Report client and hub versions

monitor commands:
        add-notification          Add user's notification
        block-notification        Block user's notifications
        edit-notification         Edit user's notification
        list-notifications        List user's notifications and blocks
        remove-notification       Remove user's notifications
        unblock-notification      Unblock user's notification
        wait-repo                 Wait for a repo to be regenerated
        watch-logs                Watch logs in realtime
        watch-task                Track progress of particular tasks

search commands:
        search                    Search the system

Try "koji --help" for help about global options
Try "koji help" to get all available commands
Try "koji <command> --help" for help about the options of a particular
command
Try "koji help <category>" to get commands under a particular category
Available categories are: admin, all, bind, build, download, info, misc, monitor, search
2022-07-19 09:44:16,973 [ERROR] koji: Unknown command: save-failed-tree










On Tuesday, July 19, 2022 at 09:40:23 AM CDT, Jerry James <loganjerry(a)gmail.com&gt;
wrote: 





On Tue, Jul 19, 2022 at 7:52 AM Globe Trotter via devel

<devel(a)lists.fedoraproject.org&gt; wrote:
>  checking whether the C compiler works... no
>  configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
>  configure: error: C compiler cannot create executables
>  See `config.log' for more details
>
>
>  Where is the config.log? 

config.log is in the buildroot.  Try running "koji save-failed-tree
<taskid>", where <taskid> is the task ID koji gave you when you
started the build.  That will give you a tarball containing the
buildroot.  Look in there for config.log.

Also, see /usr/share/doc/koji/docs/source/plugins.rst for how to
download only parts of the buildroot; e.g., config.log only.
-- 
Jerry James
http://www.jamezone.org/

[Ralf Corsépius]

Am 19.07.22 um 16:45 schrieb Globe Trotter via devel:
>  Thanks, btw, the command here says unknown command (see below).
>  
>  Btw, the log is here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2004683
The trigger of this breakdown is the sped missing "BuildRequires: gcc"

However, I regret having to say this, this package's spec could use a 
major overhaul. It contains quite a of rpm-spec-anachronisms and 
unnecessary things.


Ralf

[Globe Trotter]

Yes, thank you, this fixed it. 

I appreciate tthe comment on the spec. I inherited it as a to-be orphan and I have
continued only fixing the spec file at the margins when things break.

Would be happy to have some help in fixing the spec.







On Tuesday, July 19, 2022 at 10:21:38 AM CDT, Ralf Corsépius <rc040203(a)freenet.de&gt;
wrote: 





Am 19.07.22 um 16:45 schrieb Globe Trotter via devel:
>  Thanks, btw, the command here says unknown command (see below).
>  
>  Btw, the log is here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2004683
The trigger of this breakdown is the sped missing "BuildRequires: gcc"

However, I regret having to say this, this package's spec could use a 
major overhaul. It contains quite a of rpm-spec-anachronisms and 
unnecessary things.


Ralf

_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure