landgraf reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
As gcc-gnat has been updated I have to rebuild all ada packages some of them has circular BR (i.e. xmlada needs gprbuild and gprbuild has xmlada in BR which is broken because of libgnat so bump). So it'd be good to have side tag (f30-ada or somehing like that) to rebuild all packages there and merge it back once it's done
* When do you need this? (YYYY/MM/DD)
2019/02/07
* When is this no longer needed or useful? (YYYY/MM/DD)
2019/03/07
* If we cannot complete your request, what is the impact?
All ada packages are broken and I have to spend a lot of time on waiting rawhide repo to rebuild them. I'm waiting for new rawhide repo for ~18 hrs right now and it's blocker.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8101
nickc reported a new issue against the project: `releng` that you are following:
``
The GOLD linker is currently part of the binutils package. Unfortunately it seems that Google have decided not to continue development of the linker, and so it is possible that it may start to bit-rot. The linker is still being maintained by the upstream GNU Binutils project, but new development is not happening. Thus as a precautionary measure I would like to move GOLD into its own sub-package of the binutils, in case in the future we decide that it should be deprecated.
As an aside , it appears that development of LLD, the linker from the LLVM project, is taking off, so in the long term LLD may well replace GOLD.
Ideally I would like to introduce this change into Fedora 31. It will affect other packages that use GOLD as their linker of choice, but I am hopeful that targetting F31 will provide sufficient time to locate and update all such packages.
This request is not essential, and if it decided not to allow it, then GOLD can just continue to be part of the normal binutils package.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8130
jwrdegoede reported a new issue against the project: `releng` that you are following:
``
As discussed on the devel list, I will take-over sdljava as I have a package which depends on it.
I do not know how / why this was orphaned. This package has 2 other admin's in the user/group settings (I'm one of them), we really need to fix our orphan procedure so that packages just go to the next admin in cases like this to avoid needless churn (and work for releng).
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8124
hobbes1069 reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
arm-none-eabi-gdb
* FAS username of the new maintainer?
hobbes1069
* Any extra information?
I have filed BZ#1589251 since one of the headers conflicts with the install of gdb but the package is apparently orphaned.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8121
salimma reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
When updating python-ttystatus I accidentally recalled the wrong command from the history and invoked 'fedpkg retire' instead. While I reverted and pushed a new commit immediately, then performed a build, it turns out the package is still retired and the new build went to trash:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1181348
I noticed the expiration when building a dependency that requires ttystatus (cmdtest).
Since this package is actually active in other branch, can it be unretired without going through are-review?
* When do you need this? (YYYY/MM/DD)
2019/02/10
* When is this no longer needed or useful? (YYYY/MM/DD)
2019/02/19
* If we cannot complete your request, what is the impact?
Blocking the rebuilding of some packages that are FTBFS including cmdtest - I want to get these done before F30 is branched
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8102
besser82 reported a new issue against the project: `releng` that you are following:
``
In the last time there have been at least two builds, that broke the Rawhide buildroot entirely. The usual way to fix this is to untag the problematic `NEVR` of that package and to rebuild the package after fixing it.
Before autosign was fully implemented, the package owner / maintainer and provenpackagers could untag builds themselves from the `fXX` tag. Today there is always intervention from someone having Koji-admin powers involved, which may result in a broken Rawhide buildroot for a longer period.
That should not be hard to implement, as builds can still be tagged and untagged from the `fXX-pending` tags by the package owner / maintainers and provenpackagers.
CC: @tmraz and @cverna
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8105
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
Hello release engineering folks,
The Rust SIG never updates any crates in released Fedora's. Is it possible to opt-out from branching so that users won't get outdated crates?
I can provide list of packages, but roughly that would be whatever matches `rust-*` with a few exceptions.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8084
rdieter reported a new issue against the project: `releng` that you are following:
``
Please create a f28-kde koji side target. It will be invaluable to work on batched builds (Qt5, in particular) to avoid and minimize breaking rawhide depenedencies in the meantime.
Thanks.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7320