[releng] Issue #6671 `Figure out how to block real builds in koji coming
from forks in pagure`
by Pierre-YvesChibon
pingou reported a new issue against the project: `releng` that you are following:
``
As far as I understood from Patrick the current mechanism for koji to allow/deny building from a source is fairly simple.
With pagure on the top of dist-git, we may need something a little more flexible as we would like to support the following use-cases:
* Builds from main repo proceed as now
* Builds from forks can only be either (or both) of:
* scratch-build
* in a certain tag used for the CI integration (redefining the dist tag to allow building the same package, once for testing and once for real)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6671
6 years, 4 months
[releng] Issue #6713 `create daily run of f26 atomic host `
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
We'd like to put out "pre-release" images for Fedora 26 atomic host. I was told by dennis that we should not use the images that are created by the nightly f26 branched "gloabal" compose because those get cleaned up quickly. Thus, we'd like to run a daily run of fedora 26 atomic host, just like we do for f25 (where we are using `fedora-atomic.conf` from the pungi-fedora repo and the results stored at https://kojipkgs.fedoraproject.org/compose/twoweek/ like the 25 results are so that we can allow people to test using them.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6713
6 years, 5 months
[releng] Issue #6689 `f26-kde koji build target`
by Rex Dieter
rdieter reported a new issue against the project: `releng` that you are following:
``
To ease the building of batch updates of kde-related packages (of up to 70 packages at a time), please create a f26-kde koji build target (similar to how f25-kde works). Thanks.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6689
6 years, 5 months
[releng] Issue #6721 `Fedora Media Writer build changes`
by Martin Bříza
mbriza reported a new issue against the project: `releng` that you are following:
``
Hello,
for testing, I have released FMW 4.0.95. To accommodate the changes I'll list below you can use that, however I'd like to ship 4.1.0 (when it's done) as the release for F26.
Mac builds:
======
Homebrew ( https://brew.sh/ ) or an other package manager is required. Use it to install xz (to provide /usr/lib/liblzma.dylib and the required headers).
It's then necessary to include the liblzma.dylib file inside the package (in Contents/Frameworks) and change the rpath pointing at it with install_name_tool. See https://github.com/MartinBriza/MediaWriter/blob/master/dist/mac/build.sh#L38 to see how it's done. No special signing is required for this file.
If you're using macdeployqt with the --always-overwrite argument, you need to stop using it or the compose will fail.
Windows builds:
======
It's necessary to build using F26 or Rawhide. There is a multitude of bugs solved by updating to Qt 5.7.1 which is now included only in F26 and above.
No extra build steps are required, however there's more dynamic libraries to include in the package. See https://github.com/MartinBriza/MediaWriter/blob/master/dist/win/build.sh#L34 .
Also please note that when your code signing certificate for Windows expires, it's now necessary to get a "secure flash drive" from Unizeto with a new one, making it now more than €100 instead of €14 - we should probably change the certificate provider.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6721
6 years, 5 months
[releng] Issue #6756: "ActionNotAllowed" when attempting "koji untag-build
f27"
by Mat Booth
mbooth reported a new issue against the project: `releng` that you are following:
``
I used to be able to untag rawhide builds I'd just built, but when I tried today I get:
"ActionNotAllowed: tag requires autosign permission"
The command I attempted was:
"koji untag-build f27 eclipse-ecf-3.13.3-3.fc27 eclipse-emf-2.12.0-5.fc27"
I am trying to untag eclipse-ecf-3.13.3-3.fc27 and eclipse-emf-2.12.0-5.fc27
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6756
6 years, 5 months