pbrobinson reported a new issue against the project: `releng` that you are following:
``
https://fedoraproject.org/wiki/Changes/uEFIforARMv7
Change for uEFI on ARMv7. There will need to be a new version of oz deployed on aarch64 builder userd for building images to enable us to build ARMv7 images on those devices. I will co-ordinate with infra/rel-eng to deploy and test this on stage/prod infrastructure, and once deployed and tested will provide a PR with the pungi config changes (minor) to enable this in the nightly composes.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7606
emeryberger reported a new issue against the project: `releng` that you are following:
``
* Hoard has been orphaned; I am claiming it and taking it over. (I am the author and maintainer of Hoard.)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7996
kevin reported a new issue against the project: `releng` that you are following:
``
These packages do not have git repos on pkgs02, but are active in pdc:
```
ERROR: /srv/git/repositories/rpms/R-gnomeGUI.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/actdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/compat-ImageMagick6.9.3.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/gnome-cpufreq-applet.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/kf5-textwidgets.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/nwdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/python-elementtree.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/repsurgeon.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/seqdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-beamer.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-pgf.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-xcolor.git does not appear to be a directory
```
so, likely they should be marked eol in pdc and blocked in koji?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8143
ralph reported a new issue against the project: `releng` that you are following:
``
It has master and f27, but no f28. Did it get missed in mass-branching?
As packagers, we're disallowed by dist-git to push the branch ourselves.
/cc @gnaponie
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7490
sgallagh reported a new issue against the project: `releng` that you are following:
``
* Name of the module?
hub
* Stream name(s) and the new EOL date?
prerelease
New EOL date is EOL of Fedora 29.
* Any extra information?
This stream is not useful as it was originally addressing the lack of upstream releases for two years. However, upstream is now doing monthly releases and so it should go away.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8166
kalev reported a new issue against the project: `releng` that you are following:
``
I'm getting the following when trying to build a flatpak for thunderbird:
```
$ fedpkg flatpak-build
Created task: 32963187
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=32963187
Watching tasks (this may be safely interrupted)...
32963187 buildContainer (noarch): free
32963187 buildContainer (noarch): free -> open (buildvm-12.phx2.fedoraproject.org)
32963187 buildContainer (noarch): open (buildvm-12.phx2.fedoraproject.org) -> FAILED: Fault: <Fault 2001: 'Image build failed. Error in plugin orchestrate_build: \'{"aarch64": {"general": "\\\\"AllClustersFailedException(\\\'Could not find appropriate cluster for worker build.\\\')\\\\""}}\'. OSBS build id: thunderbird-master-79998-3'>
0 free 0 open 0 done 1 failed
32963187 buildContainer (noarch) failed
```
I assume this is fallout from https://pagure.io/releng/issue/8133 that added the aarch64 architecture to container build tags in koji.
@cverna @otaylor Any ideas?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8158
kalev reported a new issue against the project: `releng` that you are following:
``
Hi,
I just finished a new round of openh264 builds. Please sign and send the following to Cisco:
openh264-1.8.0-3.fc29
openh264-1.8.0-3.fc30
openh264-1.8.0-3.fc31
Thanks,
Kalev
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8157
zsun reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
This is a general question.
Given I am the LXQt spin maintainer, when I want to test my changes to kickstart files of generating livemedia, I need a way to try like the production.
I saw there is a page about [Building Images in Koji](https://docs.pagure.org/koji/image_build/). So I tried like that
```
koji spin-livemedia fedora-lxqt 30 f30 x86_64 ./flat-live-lxqt.ks --scratch
```
But I got
```
2019-02-20 11:20:15,915 [ERROR] koji: ActionNotAllowed: livemedia permission required
```
So my questions are
* Is the livemedia permission granted only to Release Engineering people, or also spin maintainers
* If this also grants to spin maintainers, can you grant me this permission?
* If this only grants to Release Engineering, can you provide some guide for building a livemedia like it does in Koji? I saw [this wiki](https://fedoraproject.org/wiki/Livemedia-creator-_How_to_create_and_u… already but I always need to set `selinux --permissive` to make a working Fedora Rawhide(f30) livemedia.
Thanks!
* When do you need this? (YYYY/MM/DD)
No ETA but as soon as possible
* When is this no longer needed or useful? (YYYY/MM/DD)
As long as I am still contributing to Fedora, this is still useful ;-)
* If we cannot complete your request, what is the impact?
Minimal. It just makes my work a little complex
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8145