churchyard opened a new pull-request against the project: `releng` that you are following:
``
Add a script to retire FTBFS packages
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/8592
bcl reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
It is dead. I want to revive and maintain it (lorax uses it as one of its tests in Travis CI)
* When do you need this? (YYYY/MM/DD)
now
* When is this no longer needed or useful? (YYYY/MM/DD)
never
* If we cannot complete your request, what is the impact?
sad developers, uncovered code. And nobody wants to see uncovered code.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8587
zsun reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The package menu-cache is owned by @cwickert . And from [this email thread](https://lists.fedoraproject.org/archives/list/devel@lists.fedorap... I know that he is no longer actively maintaining his packages.
Currently I am the active maintainer of LXQt Desktop. menu-cache is used by some of LXQt packages. I've filed a bug to [get menu-cache updated in EPEL7](https://bugzilla.redhat.com/show_bug.cgi?id=1724495) but it only get response after a long time.
Since cwickert is open for new maintainers, I would like to request for the ownership or commit access to menu-cache.
* When do you need this? (YYYY/MM/DD)
As soon as possible.
* When is this no longer needed or useful? (YYYY/MM/DD)
None
* If we cannot complete your request, what is the impact?
No seriou impact since I can always find some proven-packager to update if really needed. But sometimes it is not in a timely manner.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8577
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2019-08-07 from 16:00:00 to 17:00:00 UTC
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/9274/
The list of release-blocking deliverables for Fedora 31 is now
available[1]. If there are any changes that should be made that were
part of an already-accepted Fedora 31 Change proposal, please let me
know. If an edit is required that was not part of an accepted Change
proposal, please file a FESCo ticket[2].
Please note that this is the first time we have used an
announcement-based model instead of a poll-based model for blockers as
approved by FESCo[3]. I am open to your suggestions on timing and
format for this in future releases.
[1] https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking
[2] https://pagure.io/fesco/new_issue
[3] https://pagure.io/fesco/issue/2108
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
mnguyen reported a new issue against the project: `releng` that you are following:
``
You should be able to do it with this command:
> python push-two-week-atomic.py -k fedora-29 -r 29 --pungi-compose-id Fedora-29-updates-20190805.0
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8586
churchyard reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
python-epel-rpm-macros and python3-rpm are epel only packages, please block them for f31 in Koji.
* When do you need this? any time
* When is this no longer needed or useful? N/A
* If we cannot complete your request, what is the impact? unknown, possibly dangerous
Actual result:
```
$ koji list-pkgs --show-blocked --tag f31 --package python3-rpm
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
python3-rpm f31 releng
$ koji list-pkgs --show-blocked --tag f31 --package python-epel-rpm-macros
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
python-epel-rpm-macros f31 releng
```
Expected result:
```
$ koji list-pkgs --show-blocked --tag f31 --package python3-rpm
(no matching packages)
$ koji list-pkgs --show-blocked --tag f31 --package python-epel-rpm-macros
(no matching packages)
```
Or:
```
$ koji list-pkgs --show-blocked --tag f31 --package python3-rpm
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
python3-rpm f31 releng [BLOCKED]
$ koji list-pkgs --show-blocked --tag f31 --package python-epel-rpm-macros
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
python-epel-rpm-macros f31 releng [BLOCKED]
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8469
ngompa reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
`containers`
* FAS username of the new maintainer?
`ngompa`
* Any extra information?
It's a build dependency of `appstream-generator`
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8584