[releng] Issue #7643: koji is not tag building packages to f29-build
by Jaroslav Škarvada
jskarvad reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Despite the output of the koji CLI tool:
...
28412141 build (rawhide, /rpms/gr-fcdproplus.git:886b640b08a11f31701e6f3d4fb430b0ea588700): open (buildvm-08.phx2.fedoraproject.org) -> closed
0 free 0 open 9 done 0 failed
28412430 tagBuild (noarch): closed
28412141 build (rawhide, /rpms/gr-fcdproplus.git:886b640b08a11f31701e6f3d4fb430b0ea588700) completed successfully
the packages are not tagged to f29-build. I had to tag them by hand, e.g.:
$ koji tag-build f29-build gr-fcdproplus-3.7.2-0.4.rc1.20180618gite5ff8396.fc29
Otherwise the packages are not available in the build root, e.g. after the build:
$ koji wait-repo --build=gr-fcdproplus-3.7.2-0.4.rc1.20180618gite5ff8396.fc29 f29-build
Warning: nvr gr-fcdproplus-3.7.2-0.4.rc1.20180618gite5ff8396.fc29 is not current in tag f29-build
latest build in f29-build is gr-fcdproplus-3.7.2-0.2.rc1.20180618gite5ff8396.fc29
and it never returns.
It's second day I am able to reproduce this with my packages.
* 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/7643
5 years, 9 months
Fedora Release Engineering Meeting Summary for 2018-07-19
by Mohan Boddu
======================================
#fedora-meeting-2: RELENG (2018-07-19)
======================================
Meeting started by mboddu at 17:00:24 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2018-07-19/releng.20...
.
Meeting summary
---------------
* init process (mboddu, 17:00:25)
* #7645 module metadata in releases/28/Modular/$basearch/os/repodata/
has no context or arch (mboddu, 17:04:45)
* LINK: https://pagure.io/releng/issue/7645 (mboddu, 17:04:51)
* nirik will update the ticket but we cannot rerun the compose and
rebuild something that is already GA. We thought of other options
like redirecting it to some other place in mirror manager or master
mirror, but still we need a way to generate the metadata which we
are not sure of. (mboddu, 17:17:22)
* Since in the ticket they mentioned they can skip it for F28 and
include it in F29, we are thinking that might be the best way to go.
(mboddu, 17:18:13)
* FTBFS Updates (mboddu, 17:18:38)
* Open Floor (mboddu, 17:32:15)
* nirik was going through rawhide vs 29 naming and wanted to ask some
more questions in that ticket. (mboddu, 17:46:24)
Meeting ended at 17:48:45 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (80)
* nirik (42)
* cverna (15)
* zodbot (7)
* Kellin (2)
* smooge (1)
* tyll (0)
* puiterwijk (0)
* masta (0)
* pbrobinson (0)
* dustymabe (0)
* pingou (0)
* maxamillion (0)
* sharkcz (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 10 months
[releng] Issue #7642: Take over 389-ds module ownership
by Matus Honek
mhonek reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Previously, the 389-ds module was created for experiments. Now, 389DS team would like to push forward and deliver official releases. Within the team we decided I should own the module.
https://src.fedoraproject.org/modules/389-ds
* When do you need this? (YYYY/MM/DD)
At your convenience, however sooner the better.
* When is this no longer needed or useful? (YYYY/MM/DD)
This is planned as a new feature so there's really no prospect of dropping the request.
* If we cannot complete your request, what is the impact?
Inability to deliver the module which is additionally planned to be depended on by IPA module.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7642
5 years, 10 months