July 2014 - rel-eng - Fedora Mailing-Lists

#5941: Requesting Koji user certificate for Koschei

by Fedora Release Engineering

#5941: Requesting Koji user certificate for Koschei -----------------------------+------------------------ Reporter: msimacek | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Koschei is a continuous integration tool for Fedora packages that does scratch-builds of packages in rawhide as their dependencies change. Right now it is using my personal certificate for initiating the scratch-builds, but since we'd like to deploy it in the Fedora Infrastructure, we need a separate Koji account for it. It will be used only for scratch-building, no other permissions are needed. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5941> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 11 months

1
12
0 / 0

#5870: rawhide signing

by Fedora Release Engineering

#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

9 years

1
18
0 / 0

#5931: [Proposal] Move new branch and unretire requests to pkgdb2

by Fedora Release Engineering

#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

9 years

1
21
0 / 0

#5775: switch to partitioned image and "hd00" pvgrub akis for EC2; remove editing of menu.lst from image processing

by Fedora Release Engineering

#5775: switch to partitioned image and "hd00" pvgrub akis for EC2; remove editing of menu.lst from image processing ----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Beta | Component: koji Keywords: | Blocked By: Blocking: | ----------------------------+------------------------ The "hd00 aki" is like the pvgrub kernel image we are using now, but meant for a partitioned device. If we switched to doing this, we could avoid editing the menu.lst file, and therefore would have a more-identical image. . See http://www.dowdandassociates.com/content/howto-amazon-ec2-kernel- images-pv-grub/ (or http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedkernels.html, which seems to have vanished today) for more. You can find the images in each region with: euca-describe-images -o amazon --filter "manifest-location=*pv-grub- hd00*" and of course take the newest version. At this point, I doubt we want to change this by alpha, but maybe we could for beta? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5775> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
6
0 / 0

#4985: Extend test image creation SOP to require notification of delays

by Fedora Release Engineering

#4985: Extend test image creation SOP to require notification of delays ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ----------------------+----------------------------------------------------- Working through the F16 QA retrospective here: https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective One of the notes is: "jlaska - Alpha TC1 - Missed the Alpha-TC1 milestone by 1 week, little to no communication regarding status. With only two weeks Alpha ISO test time, losing 50% of time almost certainly results in a slip. See rel-eng ticket#4844 . None of the Alpha rel-eng release tickets have been filed at this time. adamw - perhaps releng image compose SOP should require updating of ticket with progress info, especially when image compose / delivery is delayed?" So: this ticket proposes that the releng 'Composing test images' SOP - https://fedoraproject.org/wiki/Composing_test_images - should be extended to require whoever is creating the images to post a comment on the image request ticket if the compose is delayed, explaining the reasons for the delay (so that any other interested party can attempt to contribute to resolving them) and giving a best estimate of an ETA if possible (so other groups can adjust their scheduling as best they can). Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4985> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
4
0 / 0

#5836: Update gitolite to gitolite3

by Fedora Release Engineering

#5836: Update gitolite to gitolite3 ------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: git Keywords: | Blocked By: Blocking: | ------------------+------------------------ The package gitolite3 in EPEL should be used to update gitolite for dist- git. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5836> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
2
0 / 0

#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org

by Fedora Release Engineering

#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org -----------------------------+------------------------ Reporter: jakub | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ In the gcc-4.9.0-12.fc21 build logs I saw a weird error: /builddir/build/BUILD/gcc-4.9.0-20140619/obj-x86_64-redhat-linux/gcc/xgcc -B/builddir/build/BUILD/gcc-4.9.0-20140619/obj-x86_64-redhat-linux/gcc/ /builddir/build/BUILD/gcc-4.9.0-20140619/gcc/testsuite/gcc.target/i386/pr57275.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -march=native -lm -o ./pr57275.exe /builddir/build/BUILD/gcc-4.9.0-20140619/gcc/testsuite/gcc.target/i386/pr57275.c:1:0: error: CPU you selected does not support x86-64 instruction set and I'd like to debug that, but don't know of a way to force e.g. a scratch rpm build to a particular build host. Would it be possible for some release engineer to run gcc -v -march=native -S -xc /dev/null -o /tmp/foo.s cat /proc/cpuinfo in the F21 mock chroot on that box? Perhaps we are missing something in the -m{arch,tune}=native logic, a CPU which clearly does support x86_64 64-bit ISA should not be determined as one that does not. Thanks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5924> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
3
0 / 0

Lookaside: Move away from md5

by Mathieu Bridon

We should move to something more secure than md5 for the uploaded sources. This patch series implements the client-side part of this change. We might want to drop the md5 fallback once we have migrated completely, that is when: 1. all archives on the lookaside have been moved to a stronger hash 2. the "sources" file in all git repos has been updated to the same hash https://fedorahosted.org/rel-eng/ticket/5846

9 years, 1 month

5
10
0 / 0

#5846: move away from md5 for look-aside cache

by Fedora Release Engineering

#5846: move away from md5 for look-aside cache ------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Keywords: | Blocked By: Blocking: | ------------------+------------------------ The lookaside cache uses md5, but something more secure like sha-256 or sha-512 should be used instead. Maybe it should even be made to allow easy changes in the future. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5846> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
22
0 / 0

#5654: Report full image creation for quality website updates

by Fedora Release Engineering

#5654: Report full image creation for quality website updates -----------------------------+------------------------ Reporter: shaiton | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 19 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, we already discussed a bit about this issues with nirik, before the F19 release day. However, yesterday was worse as expected. Please see the number of fixes: https://git.fedorahosted.org/cgit/fedora-web.git/log/ (7 important fixes after the merge into prod aedf487eb). == Summary of major issues: * http://torrent.fedoraproject.org/spins/ changed to http://torrent.fedoraproject.org/torrents and we had no idea about this. * The naming scheme of the file changed which introduced a bug in our spins website build as it is based against the Json file. We had to fix a 2 years old python code. And we did not know about this. * Each release we have the 32 bit arch named i686 or i386, it's always changing. We defined variables in order to help us maintain the websites.. And this does not help us. I know that it depends of the proc instruction set. But where is the need to change that really? Could we avoid it? Sooner or later we will drop 32 bit arch... Couldn't we define which arch to stick with? * We don't know before last minute if the Spin has built for GA and therefore if it is going to be released. We need to check it manually. And really, we can't do it all manually. (as lazy programmers we can't even think about this). * Even the spins name has changed in the past, which break our code and already existing URLs. And then we need to define URL redirect... I hope jam-kde won't be changed to jam-mate-compiz-fusion-dark at some point.. Just wondering... * The secondary (ARM) path changed from Images/arm/ to Images/armhfp/.. I understand the need to tell if it's using FP or not, but again we didn't know about this before testing in prod. That should not happen again. Please, help me define the best way to avoid this. It could be improving SOP, or updating a file after each build.. whatever. It's a probably wider collaboration issues as it is involving primary, secondary, SIGs (spins, cloud).. But starting with Releng we can probably sort this and define the smoother solution for all. What we need in a simple way (script friendly) and easy to generate for you is a way to get: All image full name, path (if possible before release), size (not needed for torrents), format (torrent, spin, dvd, cloud... whatever) and checksum. What can't be available easily can have an easy process to get them or at least we need to know how and when to get them. The most important of course is the image full name. If we don't know that this image exists (or died), we won't be able to update it. Any brillant idea? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5654> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 2 months

1
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2014