vondruch reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Koschei builds of rubygem-rails started to fail randomly \[[1]\] with errors such as:
~~~
DEBUG util.py:522: Executing command: ['/usr/bin/dnf', 'builddep', '--installroot', '/var/lib/mock/f30-build-13572340-985213/root/', '/var/lib/mock/f30-build-13572340-985213/root//builddir/build/SRPMS/rubygem-railties-5.2.1-2.fc30.src.rpm', '--setopt=tsflags=nocontexts'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8', 'LC_MESSAGES': 'C'} and shell False
DEBUG util.py:439: Last metadata expiration check: 0:00:01 ago on Thu 30 Aug 2018 04:01:54 PM UTC.
DEBUG util.py:439: No matching package to install: 'rubygem(bootsnap)'
DEBUG util.py:439: Not all dependencies satisfied
DEBUG util.py:439: Error: Some packages could not be found.
DEBUG util.py:577: Child return code was: 1
~~~
This is weird because it sometimes works and it does not work the other time. It seems to be some issues on the builder side.
[1]: https://apps.fedoraproject.org/koschei/package/rubygem-railties?collection=…
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7739
sagitter reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
lzma
* Maintainer's FAS username?
sagitter
* Any extra information?
Although [LZMA Utils are no longer developed and replaced by XZ](https://tukaani.org/lzma/), they're still required by other packages on Fedora.
lzma package is still correctly compiled on fedora 28+, it can endure for a little while yet as long as all dependent software migrate to XZ.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7712
dmach reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Module metadata in released F28 repos has no context or arch.
This impacts new libnf module dependency resolution code that needs both for proper functionality.
More details in bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1603109
* When do you need this? (2018/07/20)
* When is this no longer needed or useful? (2019/05/07)
* If we cannot complete your request, what is the impact?
New libdnf with dependency resolution that supports stream expansion and architectures won't work on Fedora 28.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7645
grinnz reported a new issue against the project: `releng` that you are following:
``
The Cinnamon livemedia compose is missing several packages that are dependencies of the 'cinnamon' metapackage, despite including that package and others from the @cinnamon-desktop group as the kickstart has been unchanged. The issue seems to have started occurring after 2018-01-06, the earliest compose log that's still there is: https://kojipkgs.fedoraproject.org//packages/Fedora-Cinnamon-Live/Rawhide/2… and here is one from today: https://kojipkgs.fedoraproject.org//packages/Fedora-Cinnamon-Live/Rawhide/2…
These logs say "Downloading 1426 RPMs" or so, I don't have the logs from 2018-01-05 and earlier but the number is supposed to be around 1470. As the kickstart isn't doing anything except including the @cinnamon-desktop group itself, I'm not sure how to debug this further.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7325
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
It would be very nice if you could set up automatic removal of all files except `dead.package` for repositories. Since `rpm-specs-latest.tar.xz` is not updated very often, I try to run grep on all git repositories, but unfortunately there are packages which are dead but still have spec file in there. I know that I could filter all such packages, but I think it would be better to clean them up anyway.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7311
adamwill reported a new issue against the project: `releng` that you are following:
``
Going by fedmsg logs, there have been some very wrongly-formed attempts at update composes (my personal favourite is `Fedora-Modular-f27-updates-updates-Fedora-Modular-27-20171013.0`...), but most of them seem to have been cleaned up. There is still one that's clearly wrong, though, this one:
https://kojipkgs.fedoraproject.org/compose/updates/Fedora-Modular--updates-…
It was obviously meant to be `Fedora-Modular-27-updates-testing-20171031.0`, but somehow lost the release number. It'd make things cleaner if it got killed, I think.
(There's probably very little value in keeping *any* of those `Fedora-Modular-27-updates-testing` composes around, but I'll leave that to you to figure out).
@mohanboddu
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7268
vondruch reported a new issue against the project: `releng` that you are following:
``
I was wondering why rubygem-factory_girl is not build by Koschei \[[1]\] and I was told by @msimacek that the package is not properly tagged for F28:
~~~
$ koji list-tagged --inherit f28-build --latest | grep rubygem-factory_girl
~~~
Please note that the package was incorrectly unbolcked in #6904 and the unblocking was later fixed by #6982, so this still might be some outfall of this. Not sure ...
[1]: https://apps.fedoraproject.org/koschei/package/rubygem-factory_girl
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7212