rel-eng January 2015

rel-eng@lists.fedoraproject.org

11 participants
120 discussions

#5775: switch to partitioned image and "hd00" pvgrub akis for EC2; remove editing of menu.lst from image processing
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#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

1 6

#6081: please keep releases.txt up-to-date
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#6081: please keep releases.txt up-to-date -----------------------------+------------------------ Reporter: mclasen | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ In order to implement a graphical fedup frontend, we need to have a way to find out when new releases become available. preupgrade had this, with http://mirrors.fedoraproject.org/releases.txt. We'd like to keep using the same mechanism. Of the fields mentioned that are listed in the files documentation, only version and installmirrorlist are really important for us, although eol-date may be useful as well. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6081> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 7

#4985: Extend test image creation SOP to require notification of delays
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#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

1 4

#5836: Update gitolite to gitolite3
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#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

1 2

#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#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

1 3

#6038: rawhide cloud image nightlies failing with "Could not reach destination to fetch boot media"
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#6038: rawhide cloud image nightlies failing with "Could not reach destination to fetch boot media" -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Rawhide nightly cloud images are failing, and Oz gives the error "Could not reach destination to fetch boot media". See for example: http://koji.fedoraproject.org/koji/taskinfo?taskID=8080223 This is obviously less urgent than all F21-related tasks, but would be nice to have fixed. Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6038> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#6056: Branched: no images/ or LiveOS/ directory created due to package conflicts
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#6056: Branched: no images/ or LiveOS/ directory created due to package conflicts -----------------------------+------------------------ Reporter: kparal | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 21 Final | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ 20141125 is the last day we have images/, LiveOS/ and similar directories: http://koji.fedoraproject.org/mash/branched-20141125/21/x86_64/os/ After that, only Packages/ and repodata/ are available: http://koji.fedoraproject.org/mash/branched-20141127/21/x86_64/os/ The log says: {{{ yum.verbose.YumBase.INFO_2: Running Transaction Check pylorax.ltmpl.ERROR: template command error in runtime-install.tmpl: pylorax.ltmpl.ERROR: run_pkg_transaction pylorax.ltmpl.ERROR: YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'fedora-productimg-cloud conflicts with fedora-productimg- workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-cloud-21-6.fc21.noarch', 'fedora- productimg-workstation conflicts with fedora-productimg- cloud-21-6.fc21.noarch', 'fedora-productimg-cloud conflicts with fedora- productimg-server-21-6.fc21.noarch', 'fedora-productimg-workstation conflicts with fedora-productimg-server-21-6.fc21.noarch'] pylorax.ltmpl.DEBUG: Traceback (most recent call last): pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/pylorax/ltmpl.py", line 508, in run_pkg_transaction pylorax.ltmpl.DEBUG: rpmDisplay=LoraxRpmCallback()) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6469, in processTransaction pylorax.ltmpl.DEBUG: self._doTestTransaction(callback,display=rpmTestDisplay) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6548, in _doTestTransaction pylorax.ltmpl.DEBUG: raise Errors.YumRPMCheckError,retmsgs pylorax.ltmpl.DEBUG: YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'fedora-productimg-cloud conflicts with fedora-productimg- workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-cloud-21-6.fc21.noarch', 'fedora- productimg-workstation conflicts with fedora-productimg- cloud-21-6.fc21.noarch', 'fedora-productimg-cloud conflicts with fedora- productimg-server-21-6.fc21.noarch', 'fedora-productimg-workstation conflicts with fedora-productimg-server-21-6.fc21.noarch'] }}} http://koji.fedoraproject.org/mash/branched-20141127/logs/x86_64.log I'm not sure whether this affects our ability to create a full Fedora 21 release compose? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6056> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6086: please add opendnssec package to repos for F21 Server
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#6086: please add opendnssec package to repos for F21 Server -----------------------------+------------------------ Reporter: pspacek | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hello, it seems that opendnssec package is missing in F21 Server repos. This unfortunately means that FreeIPA (which is in server repos) cannot support DNSSEC. Also, I would argue that opendnssec package should be included in Server variant because it is clearly server software. Thank you for fixing this! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6086> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#6095: post-receive traceback on dist-git
by Fedora Release Engineering 09 Mar '15

09 Mar '15

#6095: post-receive traceback on dist-git -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ {{{ $ git push --all Zähle Objekte: 8, Fertig. Delta compression using up to 2 threads. Komprimiere Objekte: 100% (8/8), Fertig. Schreibe Objekte: 100% (8/8), 1.16 KiB | 0 bytes/s, Fertig. Total 8 (delta 6), reused 0 (delta 0) remote: Traceback (most recent call last): remote: File "./hooks/post-receive-chained.d/post-receive-email", line 941, in <module> remote: main() remote: File "./hooks/post-receive-chained.d/post-receive-email", line 936, in main remote: change.prepare() remote: File "./hooks/post-receive-chained.d/post-receive-email", line 234, in prepare remote: detailed_commit_args.append("^" + all_changes[branch].oldrev) remote: TypeError: cannot concatenate 'str' and 'NoneType' objects remote: Emitting a message to the fedmsg bus. To ssh://till@pkgs.fedoraproject.org/youtube-dl 58db9ae..b978157 f20 -> f20 58db9ae..b978157 f21 -> f21 58db9ae..b978157 master -> master * [new branch] byte -> byte ! [rejected] epel7 -> epel7 (non-fast-forward) error: Fehler beim Versenden einiger Referenzen nach 'ssh://till@pkgs.fedoraproject.org/youtube-dl' Hinweis: Aktualisierungen wurden zurückgewiesen, weil die Spitze eines versendeten Hinweis: Branches hinter seinem externen Gegenstück zurückgefallen ist. Checken Sie Hinweis: diesen Branch aus und führen Sie die externen Änderungen zusammen Hinweis: (z.B. 'git pull ...') bevor Sie erneut "push" ausführen. Hinweis: Siehe auch die Sektion 'Note about fast-forwards' in 'git push --help' Hinweis: für weitere Details. }}} -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6095> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#5959: Enable keep-alive connections for koji (primary and secondaries)
by Fedora Release Engineering 02 Mar '15

02 Mar '15

#5959: Enable keep-alive connections for koji (primary and secondaries) -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ Keeping connections alive will speed up koji acces when multiCall() is not used without a significant speed penalty. Therefore it is a good idea to support this. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5959> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

← Newer
1
2
3
4
5
6
7
8
...
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2015