smani reported a new issue against the project: `releng` that you are following:
``
On F27 the current version of apitrace is apitrace-7.1-7.fc27.
On F27 x86_64 however,
# dnf install --refresh apitrace-libs.i686
currently gives you apitrace-libs-7.1-7.fc27.i686 (note: -7 instead of -9). On the other hand,
# dnf install --refresh apitrace-libs
gives you apitrace-libs-7.1-9.fc27.x86_64 as expected.
apitrace-libs is multilib whitelisted, but appears to be out of sync.
See also #1541099.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7354
langdon reported a new issue against the project: `releng` that you are following:
``
Once [#7227](https://pagure.io/releng/issue/7227) is complete, I wanted to confirm that:
* We should continue to make PRs against [variants-modular.xml](https://pagure.io/pungi-fedora/blob/master/f/variants-modular.xml) and file tickets here to get new modules added to the compose.
* Should we file tickets here or use some other method to get changes to fedora-release* rpms? Specifically, we will need to include a system profile ([for example](https://github.com/sgallagher/semimodular_poc/blob/master/semimodu…) and modify it as modules are added.
/cc @sgallagh @psabata
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7316
petersen reported a new issue against the project: `releng` that you are following:
``
* For which release?
F30
* Name of the side tag? (Generally fxx-pkg)
f30-ghc
* Number of builds that are expected in the side tag?
500
* How long do you need the side tag?
2 weeks
* Any extra information?
Corresponding Fedora Change for updating to ghc-8.4 to follow soon
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8014
rdieter reported a new issue against the project: `releng` that you are following:
``
* For which release?
fedora 30
* Name of the side tag? (Generally fxx-pkg)
f30-kde
* Number of builds that are expected in the side tag?
30-40 initially
* How long do you need the side tag?
Likely on/off for the duration of fedora 30 lifetime.
* Any extra information?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7966
sharkcz reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
libmspack
* FAS username of the new maintainer?
orion
* Branches that you need it to be unretired for?
epel7
* Package re-review BZ URL?
N/A, it's still an active package in Fedora
* Any extra information?
The epel7 branch got retired because libmspack appeared in RHEL 7.6, but it's not provided for all arches. Thus will be reintroduced as arch-limited package.
CCing @orion
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7997
tstellar reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I need to break the ABI of libLLVM.so without a soname bump in order to fix an llvm bug[1]. I need a side-tag in order to rebuild all dependent packages without creating a disruption.
[1] https://bugs.llvm.org/show_bug.cgi?id=39427
* When do you need this? (YYYY/MM/DD)
2018/11/01
* When is this no longer needed or useful? (YYYY/MM/DD)
2019/08/01
* If we cannot complete your request, what is the impact?
Users will not be able to link programs compiled with clang against Fedora's llvm-libs package.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7900
kni reported a new issue against the project: `releng` that you are following:
``
Please unorphan the following branches for the netatalk package:
- rawhide
- f29
- f28
- epel7
FAS Account: kni
Thank you.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7984
mohanboddu opened a new pull-request against the project: `releng` that you are following:
``
Edit the targets of newly branched release
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7871
cverna reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I am trying to build the fedora container base image in OSBS, but I am getting the following error " Image build failed. Error in plugin add_filesystem: ActionNotAllowed('image permission required') "
I believe this is something that needs to be allowed in Koji
* When do you need this? (YYYY/MM/DD)
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8058
kellin reported a new issue against the project: `releng` that you are following:
``
$ koji taginfo f27
Tag: f27 [417]
Arches: armv7hl i686 x86_64 ppc64 ppc64le aarch64
^PGroups: appliance-build, build, livecd-build, livemedia-build, srpm-build
Required permission: 'admin'
Tag options:
mock.package_manager : 'dnf'
Inheritance:
$ koji taginfo f27-build
Tag: f27-build [425]
Arches: aarch64 armv7hl i686 ppc64 ppc64le s390x x86_64
Groups: appliance-build, build, livecd-build, livemedia-build, srpm-build
Required permission: 'admin'
Tag options:
This tag is a buildroot for one or more targets
Current repo: repo#785431: 2017-09-14 21:09:29.969602
Targets that build from this tag:
f27-candidate
f27-rebuild
f27-binutils-rebuild
f27
Inheritance:
0 .... f27-override [424]
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7031