rel-eng May 2014

rel-eng@lists.fedoraproject.org

8 participants
170 discussions

#5878: noarch packages corrupted on import on ppc.koji.fp.o
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5878: noarch packages corrupted on import on ppc.koji.fp.o -----------------------------+------------------------ Reporter: dwa | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 20 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ (Filing a ticket so other people can weigh in / brainstorm without getting lost in an e-mail thread) Recently (in the past 2 weeks or so) I've seen a number of source RPMs become corrupted when koji-shadow imports them to ppc.koji.fp.o. This was previously a once-in-a-blue-moon occurence but it's now happened multiple times. Most recently corrupted srpm: * moodle-2.5.5-1.fc20.src.rpm Previously: * mingw-gnutls-3.1.21-1.fc20 * elementary-xfce-icon-theme-0.4-1.fc20 * kde-l10n-4.12.3-1.fc20 * oxygen-icon-theme-4.12.3-1.fc20 I've not noticed this happening with any f19 packages, and f21 isn't signed (which is when we typically notice this is when signing packages.) ppc.koji is currently running koji-1.8.0-2.el6. Any ideas for troubleshooting? It's not difficult to fix (I've documented the procedure I'm using at https://fedoraproject.org/wiki/User:Dwa#Corrupt_noarch_RPMs ) but it'd be nice for it to not happen at all. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5878> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5678: koji package for cloud images so they can be non-scratch, and garbage collection policies for those packages
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5678: koji package for cloud images so they can be non-scratch, and garbage collection policies for those packages -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Replying to [ticket:3897 mattdm]: > We want to generate non-scratch cloud images. Because of a bug, these currently need to have the name of the architecture in the package. That will be fixed in the Real Soon Future, but in the meantime I'd like to get going with what we have. Could we please create koji packages named > > {{{ > Fedora-19-cloud-x86_64 > Fedora-19-cloud-i386 > Fedora-20-cloud-x86_64 > Fedora-20-cloud-i386 > Fedora-rawhide-cloud-x86_64 > Fedora-rawhide-cloud-i386 > }}} > > And, we would also like to have a custom garbage collection policy for these; even though they are not scratch builds, they don't need to stay around forever. If we can do a nightly builds (ideal), then I think a week is fine; if they are weekly, keeping a month around seems good. Of course, longer is always better. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5678> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#5622: [RFE] Allow user to (create/)delete private branches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5622: [RFE] Allow user to (create/)delete private branches -----------------------------+------------------------ Reporter: vondruch | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 19 Alpha | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I'd like to be able to manage my private branches. For example, in preparation for Ruby 2.0 release, I was pushing my changes to .spec file into Ruby's repository in dist git, into ruby-2.0 branch. This branch is already merged into master for some while and I'd like to delete it, but it is forbidden: {{{ $ git push -f origin :ruby-2.0 remote: + refs/heads/ruby-2.0 ruby vondruch DENIED by fallthru remote: error: hook declined to update refs/heads/ruby-2.0 To ssh://vondruch@pkgs.fedoraproject.org/ruby ! [remote rejected] ruby-2.0 (hook declined) error: failed to push some refs to 'ssh://vondruch@pkgs.fedoraproject.org/ruby' }}} Would it be possible to allow some development branches, which can be created and deleted as well, without need of opening rel-eng tickets etc? Thanks -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5622> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5329: RFE: Send branched report only when there is any change committed
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5329: RFE: Send branched report only when there is any change committed -----------------------------+------------------------ Reporter: pnemade | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, While we are in freeze, can branched report be only sent to the devel/test list when there is any change added for any package? Parag. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5329> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#5218: block httpd-devel.i686, php-devel.i686 from x86_64 compose
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5218: block httpd-devel.i686, php-devel.i686 from x86_64 compose -----------------------------+------------------------ Reporter: jorton | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Could the .i686 packages for both httpd-devel and php-devel be blocked from inclusion in the x86_64 compose, we don't (can't/won't) support them biarch. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5218> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#5215: Stage comps and spin-kickstarts during freezes
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5215: Stage comps and spin-kickstarts during freezes -----------------------------+------------------------ Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ As noted on the F17 QA retrospective by me and Bruno Wolff: https://fedoraproject.org/wiki/Fedora_17_QA_Retrospective it's a problem that we use git master of both comps and spin-kickstarts for composes - not the latest packaged version - and both these git repos are not frozen during freezes. During the 17 cycle, we had a concrete example of a comps change during a freeze causing considerable trouble: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=807879 - pulling Boxes into comps during the Beta freeze made that issue a serious problem. For spin-kickstarts, the same kind of thing is possible, and we also have a release criterion requiring a spin-kickstarts package which matches the .ks files used for the compose to be present in the release repository; obviously, the lack of a git freeze makes this tricky to ensure. So we would strongly recommend, at minimum, a mechanism for freezing spin- kickstarts and comps at Alpha, Beta and Final freeze. Post-freeze changes could be made following the same blocker/NTH process used for other post- freeze changes. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5215> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#5223: F18 TODO: automate torrent generation
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5223: F18 TODO: automate torrent generation -----------------------------+------------------------ Reporter: ausil | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Torrent Releases Infrastructure SOP http://torrent.fedoraproject.org/ is our master torrent server for Fedora distribution. It runs out of ServerBeach. Contact Information Owner: Fedora Infrastructure Team Contact: #fedora-admin, sysadmin-torrent group Location: ibiblio Servers: torrent.fedoraproject.org Purpose: Provides the torrent master server for Fedora distribution Torrent Release When you want to add a new torrent to the tracker at http://torrent.fedoraproject.org you need to take the following steps to have it listed correctly: 1. login to torrent.fedoraproject.org. If you are unable to do so please contact the fedora infrastructure group about access. This procedure requires membership in the torrentadmin group. 2. upload the files you want to add to the torrent to torrent.fedoraproject.org:/srv/torrent/new/$yourOrg/ 3. use sha1sum and verify the file you have uploaded matches the source 4. organize the files into subdirs (or not) as you would like 5. run /srv/torrent/new/maketorrent [file-or-dir-to-torrent] ([file-or-dir-to-torrent]) to generate a .torrent file or files 6. copy the .torrent file(s) to: /srv/torrent/www/torrents/$yourOrg/ 7. cd to /srv/torrent/torrent-generator/ or /srv/torrent/spins- generator/ (depending on if it is an official release or spins release) 8. add a .ini file in this directory for the content you'll be torrenting. we use fedora-torrent-ini.py from fedora releng git repo to generate it 9. mv all files from /srv/torrent/new/$yourOrg into /srv/torrent/btholding/ - this includes the files you uploaded as well as the .torrent files you've created. Your files will be linked on the website and available on the tracker after this. $yourOrg is one of fedora or spins this all needs to be setup to be done via a single script. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5223> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#5332: [RFE] Generate .composeinfo for Fedora secondary arches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5332: [RFE] Generate .composeinfo for Fedora secondary arches -----------------------------+------------------------ Reporter: bpeck | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Please generate a .composeinfo for secondary arches. The secondary arches that we are interested in are: arm, ppc, and s390. Ideally we could get a .composeinfo when *all* these arches are complete. But I understand that they have different time schedules and may update at different times. Worst case we look to see if the datetime on the file changes and we can re-import again with the newly added arch. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5332> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#5866: Create new channel for building Java packages
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5866: Create new channel for building Java packages ----------------------+------------------------ Reporter: mizdebsk | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: koji Keywords: | Blocked By: Blocking: | ----------------------+------------------------ == Request == Please create a new Koji channel for building Java packages which would exclude ARM builders, or implement an equivalent solution. My goal is to be able to build noarch Java packages skipping any ARM builders. Using custom koji command is not a problem for me. == Justification == The great majority of Java packages are noarch. As such they are most often pisked up by ARM builders. Java performance on ARM is very poor. The situation got even worse after JIT for ARM was disabled in JVM. ARM machines are often slower by one to three orders of magnitude than x86_64. Some tests which execute in a few seconds on x86_64 can take over half an hour on ARM. Current state of Java on ARM combined with Koji configuration makes it difficult to maintain Java packages in Fedora. A substantial amount of human resources is wasted on waiting for builds to complete, debugging tests which fail only on ARM, keeping track on builds and resubmitting them. That resources could be utilised better and I think that justifies my request. == Alternative solutions == I have tried differnt alternative solutions since ARM became a primary architecture and none of them is good enough. One ad-hoc solution is submitting numerous dummy koji tasks for ARM builders until their capacity is exhausted, then submitting Java package build and canceling ARM tasks. This is obviously a hack and should be avoided. If Koji configuration is not improved the only remaining solution will be converting Java packages from noarch to arch-specific and adding ExcludeArch. I still hope that ARM situation will eventually improve, so I would like to avoid doing drastic things like that, if possible. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5866> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 20

#5870: rawhide signing
by Fedora Release Engineering 23 Mar '15

23 Mar '15

#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

1 18

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng May 2014