#5967: Enable source repo generation
-------------------------+------------------------
Reporter: mizdebsk | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------------
Please enable source repository generation in kojira, at least for rawhide
(currently f22-build).
Justification: There are many use cases which require access to YUM source
repository. One of them is Koschei (a continous rebuild service), which
requires SRPM repo for resolving package build-dependencies.
Implementation of this feature should be simple - it just involves editing
kojira.conf file
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5967>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2015-03-30 from 16:30:00 to 17:30:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org//calendar//meeting/2026/
#6125: single atomic ostree repository
-----------------------------+------------------------
Reporter: walters | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
The way OSTree is designed, a repository can contain multiple branches.
It's natural to have multiple states represented in a single repository, a
good example being:
fedora-atomic/f21/x86_64/docker-host
fedora-atomic/f21/x86_64/updates-testing/docker-host
However, it's more convenient from the command line to go between multiple
releases if they're part of the same repository, one can just do e.g.:
# rpm-ostree rebase fedora-atomic/f22/x86_64/docker-host
If there is one repository per major release, it means that the remote
name needs to be versioned, which is not the end of the world - it's just
more awkward.
Something like:
diff --git a/scripts/buildbranched b/scripts/buildbranched
index 19b9363..157553f 100755
--- a/scripts/buildbranched
+++ b/scripts/buildbranched
@@ -28,7 +28,7 @@ SUBJECT='F-'$BRANCHED' Branched report: '$DATE' changes'
FROM="Fedora Branched Report <rawhide(a)fedoraproject.org>"
RSYNCPREFIX="sudo -u ftpsync"
ATOMIC=$(mktemp -d /tmp/atomici.${DIST}.$DATE.XXXX)
-ATOMICREPO="/mnt/koji/mash/atomic/$BRANCHED/"
-ATOMICDEST="/pub/fedora/linux/atomic/$BRANCHED/"
+ATOMICREPO="/mnt/koji/mash/atomic/repo/"
+ATOMICDEST="/pub/fedora/linux/atomic/repo/"
source ./scripts/build-functions.sh
Seems like it would start this, but it would need some compatibility code.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6125>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6140: Block cobertura and maven-plugin-cobertura in f23
----------------------+------------------------
Reporter: mizdebsk | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
Please block packages cobertura and maven-plugin-cobertura in f23.
They have been retired.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6140>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2015-03-23 from 16:30:00 to 17:30:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org//calendar//meeting/2026/
#5870: rawhide signing
-----------------------------+------------------------
Reporter: kevin | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Final | Component: koji
Keywords: meeting | Blocked By:
Blocking: |
-----------------------------+------------------------
We have talked a number of times about getting rawhide packages signed,
but haven't been able to come up with a solution that is secure and meets
our needs. We should try and do so. :)
This came up again today because gnome-software has different code paths
for signed/unsigned content and they would very much like rawhide to be
signed so it tests the same code as for stable releases.
* There is a koji plugin to sign all builds, but it's not implemented in a
very nice way and stores it's keys/passphrases in clear text files on the
hub.
* Manually signing with sigul could be done, but since there's no gating,
it would mean either large amounts of packages would go out unsigned or
composes would fail for unsigned packages often.
* Additional space would be taken up by more signed rpms/signatures.
* Any solution we come up with could possibly be also used by copr, which
also wishes to sign builds in an unattended manner.
Ideas welcome. ;)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5870>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5931: [Proposal] Move new branch and unretire requests to pkgdb2
-------------------------+------------------------
Reporter: pingou | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: | Component: git
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------------
Till suggested me recently that maybe we could port the new-branch
requests to pkgdb2, together with the requests that for a package to be
unretired.
I have been working with these ideas, they are simply a way for users to
ask an admin to perform an action (atm: request.branch and
request.unretire).
The output can be seen for admins via the UI at:
http://209.132.184.188/admin/actions/
Or for everyone via the API at:
http://209.132.184.188/api/admin/actions/
Note: the logic to change the status of a request isn't there yet but I
thought I would first run the idea by you guys to get some early feedback,
especially since if you like the idea, some tools will need adjustments.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5931>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6139: unblock docker package build for rawhide and f22
----------------------------+------------------------
Reporter: lsm5 | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
I'm trying to build 'docker' (now moved over from docker-io) in koji for
rawhide and f22, and I see this error:
FAILED: BuildError: package docker is blocked for tag f22-updates-
candidate
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6139>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6130: Improve the package retire process
----------------------------+------------------------
Reporter: pnemade | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Beta | Component: epel
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
When a package is retired from any branch, I have a question why then
people still listed as package admin, committer, watch{bugzilla/commits}
for that branch?
I request to remove all such permissions for all users for the retired
branch as part of the retire process.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6130>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project