[releng] Issue #8058: Give OSBS permission to create images in koji
by Clement Verna
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
5 years, 3 months
[releng] Issue #8122: f30-readline8 side tag
by Igor Gnatenko
ignatenkobrain 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-readline8
* Number of builds that are expected in the side tag?
~200 ± 50
* How long do you need the side tag?
week or two
* Any extra information?
I would appreciate if you could create it asap.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8122
5 years, 3 months
[releng] Issue #8116: mass-rebuild-modules.py: will rebuild many extra things
by Igor Gnatenko
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
@mboddu @sgallagh
I think there is something wrong with the mass-rebuild-modules.py script.
It shows that it would rebuild `0ad:master` while that one has:
```
dependencies:
- buildrequires:
flatpak-common: [f29]
flatpak-runtime: [f29]
platform: [f29]
requires:
flatpak-common: [f29]
flatpak-runtime: [f29]
platform: [f29]
```
It should not be rebuilt.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8116
5 years, 3 months
Fedora Release Engineering Meeting Summary for 2018-02-14
by Mohan Boddu
======================================
#fedora-meeting-2: RELENG (2019-02-14)
======================================
Meeting started by mboddu at 17:00:56 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2019-02-14/releng.20...
.
Meeting summary
---------------
* init process (mboddu, 17:00:56)
* #7793 Implement new Fedora Security policy for retiring packages with
security bugs (mboddu, 17:03:39)
* LINK: https://pagure.io/releng/issue/7793 (mboddu, 17:03:45)
* mboddu will file a ticket with FESCo on more clarification about the
timing of this process (mboddu, 17:21:10)
* suggestion is - proposing we change it to start after branching in
rawhide only and confirm 8 weeks is the notification time before
orphaning. (mboddu, 17:21:36)
* LINK:
https://fedorapeople.org/groups/schedule/f-30/f-30-releng-tasks.html
(nirik, 17:23:23)
* PGM schedule already has this scheduled, mboddu will ask if we
should try it or punt it to f31 (mboddu, 17:25:56)
* Change Meeting time (mboddu, 17:30:04)
* LINK: https://framadate.org/fedorarelengmeeting (mboddu, 17:30:33)
* Fedora RelEng meeting will be moved to every Wednesday 16:00 UTC
(mboddu, 17:44:23)
* mboddu will send an email to releng list and update the calendar
(mboddu, 17:44:38)
* Open Floor (mboddu, 17:48:39)
* Mass Branching is next week, Feb 19th (mboddu, 17:50:40)
* Finally I started running mass rebuild on modules but it failed due
to some missing permissions on what the token can do (mboddu,
17:52:48)
* Patrick is working on fixing it (mboddu, 17:52:59)
* mboddu will create the key and nirik/puiterwijk will work on adding
fedora-31 key to autosign (mboddu, 17:54:43)
Meeting ended at 18:07:17 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (89)
* nirik (59)
* cverna (23)
* zodbot (7)
* relrod (6)
* puiterwijk (5)
* smooge (2)
* dustymabe (1)
* sharkcz (1)
* tyll (0)
* masta (0)
* Kellin (0)
* pbrobinson (0)
* pingou (0)
* maxamillion (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 3 months
[releng] Issue #7031: Should f27 and f27-build have different architectures?
by Kellin
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
5 years, 3 months
[releng] Issue #8057: Unblock/reactivate the 9.6 stream branch of the
postgresql module
by Nils Philippsen
nphilipp reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The `9.6` stream branch of the `postgresql` module is inactive, probably because it's past its EOL date which was set to 2018-12-01 when it was created. The maintainer of the module @praiskup reported this to the [Modularity Tracker](https://pagure.io/modularity/issue/123).
Two possible remedies come to mind:
- Manually set the `bug_fixes` (and `security_fixes`?) EOL date for the `modules/postgresql:9.6` branch to 2021-12-01, corresponding with the upstream EOL date of 2021-11-11.
- Or, ignore the SL metadata when determining which branch is active ([background](https://pagure.io/modularity/issue/124#comment-549423), [#2](https://pagure.io/modularity/issue/112)). This probably involves changes in code/scripts.
* When do you need this? (YYYY/MM/DD)
I assume the sooner the better. @praiskup?
* When is this no longer needed or useful? (YYYY/MM/DD)
End of 2021 when 9.6 maintenance ceases upstream.
* If we cannot complete your request, what is the impact?
The `9.6` stream can't be updated.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8057
5 years, 3 months