October 2013 - rel-eng - Fedora Mailing-Lists

#3761: add gpg signature for .treeinfo file and/or add CHECKSUM file for unsigned content of images

by Fedora Release Engineering

#3761: add gpg signature for .treeinfo file and/or add CHECKSUM file for unsigned content of images ----------------------+----------------------------------------------------- Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: other Keywords: meeting | ----------------------+----------------------------------------------------- Description of problem: Currently the only way to verify the contents of .treeinfo or the installer images is to download the .iso and the regarding -CHECKSUM file and check it. But e.g. preupgrade does not download the .iso but the *.img files, the kernel and the .treeinfo directly from a mirror. Therefore it is also not possible to easily verify these files. I guess the preupgrade way of updating is somehow popular, therefore it should be possible to do this securely. I filed a bug against preupgrade for not verifying anything and not announcing this here: bug 509338 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3761> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 3 months

1
2
0 / 0

#5767: F20 stable push requests

by Fedora Release Engineering

#5767: F20 stable push requests -----------------------------+------------------------ Reporter: pschindl | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F20 release freezes. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process. Similar to TC/RC request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed. First request, current Alpha blocker / FE fixes with sufficient karma to be pushed: * https://admin.fedoraproject.org/updates/fedora-release-20-0.7 * https://admin.fedoraproject.org/updates/sddm-0.2.0-0.6.20130821gite707e22... * https://admin.fedoraproject.org/updates/vinagre-3.9.90-2.fc20 * https://admin.fedoraproject.org/updates/FEDORA-2013-16256/desktop- backgrounds-20.0.0-1.fc20,heisenbug-backgrounds-19.90.0-1.fc20 * https://admin.fedoraproject.org/updates/gnome-desktop3-3.9.91-2.fc20 * https://admin.fedoraproject.org/updates/systemd-206-11.fc20 * https://admin.fedoraproject.org/updates/kernel-3.11.0-300.fc20 Thank you! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5767> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 4 months

1
33
0 / 0

#4267: collectd in EPEL

by Fedora Release Engineering

#4267: collectd in EPEL ----------------------+----------------------------------------------------- Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: mash Keywords: | ----------------------+----------------------------------------------------- Can we get collectd in EPEL set to disable multi-lib? It has become an issue on EPEL where installing "collectd" via yum creates conflicts it shouldn't. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4267> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 4 months

1
4
0 / 0

#5787: Create Fedora 20 Beta test compose (TC) and release candidate (RC)

by Fedora Release Engineering

#5787: Create Fedora 20 Beta test compose (TC) and release candidate (RC) ----------------------------+------------------------ Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Beta | Component: koji Keywords: | Blocked By: Blocking: | ----------------------------+------------------------ It's that time again...Beta time. I've done a test live image and it worked fine, so we have a shot at a working TC1. Just one update to pull in: * [https://admin.fedoraproject.org/updates/FEDORA-2013-17921/pykickstart-1.9... pykickstart-1.99.41-1.fc20,anaconda-20.21-1.fc20] for multiple blockers and FEs Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5787> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
33
0 / 0

#5702: several rel-eng scripts are missing proper license headers

by Fedora Release Engineering

#5702: several rel-eng scripts are missing proper license headers -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ The scripts in the rel-eng git are not properly licensed, for example: * need-rebuild.py * buildbranched * build_composeinfo -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5702> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
3
0 / 0

#5781: Live ISO image for F20 l10n and i18n test days

by Fedora Release Engineering

#5781: Live ISO image for F20 l10n and i18n test days -----------------------------+------------------------ Reporter: anipeter | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, Please create a live image for Fedora l10n and i18n test days. The test days are scheduled as below:- L10n test day: 3rd Oct 2013 (https://fedorahosted.org/fedora- qa/ticket/408) I18n test day: 29th Oct 2013 (https://fedorahosted.org/fedora- qa/ticket/409) Hence, appreciate if we can have the image ready by 30th Sept (Monday) latest. The mail request to rel-eng team is here: https://lists.fedoraproject.org/pipermail/rel- eng/2013-September/016644.html Thanks Ani Peter FLTG (https://fedoraproject.org/wiki/FLTG) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5781> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
8
0 / 0

#5748: Mash fails for i386

by Fedora Release Engineering

#5748: Mash fails for i386 -----------------------------+------------------------ Reporter: kparal | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 20 Alpha | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ vmlinuz and initrd.img are missing for i386. Probably caused by this: {{{ yum.YumBase.CRITICAL: installing package hdparm-9.43-5.fc20.i686 needs 1446MB on the / filesystem yum.YumBase.CRITICAL: installing package ethtool-2:3.10-2.fc20.i686 needs 1446MB on the / filesystem pylorax.ltmpl.ERROR: template command error in runtime-install.tmpl: pylorax.ltmpl.ERROR: run_pkg_transaction pylorax.ltmpl.ERROR: YumRPMTransError: Could not run transaction. pylorax.ltmpl.DEBUG: Traceback (most recent call last): pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/pylorax/ltmpl.py", line 488, in run_pkg_transaction pylorax.ltmpl.DEBUG: rpmDisplay=LoraxRpmCallback()) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6377, in processTransaction pylorax.ltmpl.DEBUG: self._doTransaction(callback,display=rpmDisplay) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6489, in _doTransaction pylorax.ltmpl.DEBUG: self.runTransaction( cb=cb ) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 1830, in runTransaction pylorax.ltmpl.DEBUG: errors=errors) pylorax.ltmpl.DEBUG: YumRPMTransError: Could not run transaction. }}} http://koji.fedoraproject.org/mash/branched-20130826/logs/i386.log The template needs more disk space configured. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5748> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
1
0 / 0

#5785: Mash fails for i386

by Fedora Release Engineering

#5785: Mash fails for i386 ----------------------------+------------------------ Reporter: kparal | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 20 Beta | Component: mash Keywords: | Blocked By: Blocking: | ----------------------------+------------------------ {{{ 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:', 'sysvinit-tools < 2.88-14 conflicts with util- linux-2.24-0.1.fc20.i686'] pylorax.ltmpl.DEBUG: Traceback (most recent call last): pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/pylorax/ltmpl.py", line 488, in run_pkg_transaction pylorax.ltmpl.DEBUG: rpmDisplay=LoraxRpmCallback()) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6374, in processTransaction pylorax.ltmpl.DEBUG: self._doTestTransaction(callback,display=rpmTestDisplay) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6453, in _doTestTransaction pylorax.ltmpl.DEBUG: raise Errors.YumRPMCheckError,retmsgs pylorax.ltmpl.DEBUG: YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'sysvinit-tools < 2.88-14 conflicts with util- linux-2.24-0.1.fc20.i686'] }}} http://koji.fedoraproject.org/mash/branched-20130930/logs/i386.log The pxeboot i386 images are missing because of this. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5785> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
2
0 / 0

#5636: Use a staging area for test composes and safe practices when naming them

by Fedora Release Engineering

#5636: Use a staging area for test composes and safe practices when naming them -----------------------------+------------------------ Reporter: kparal | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 19 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Summary: There was a hiccup for F19 TC3 compose. First it was created with an old anaconda, then it was deleted and created with a new anaconda. The announcement was sent only afterwards. Unfortunately the mirrors do not heed announcements, they periodically sync everything. For Brno office our mirror synced the old TC3 -> we came to work -> saw TC3 announcement -> saw TC3 on our local mirror -> tested the (outdated) TC3 version for the whole day -> and *by pure chance* learned that we have been using an outdated compose (and wasted a day's work) at the end of the day. I don't mean to blame anyone. It was unfortunate, and I'd like to improve our workflow to minimize a chance of that happening again. I have heard a solution "If you download images before announcement, make sure they match the upstream checksums after the announcement is out". First, a lot of people (e.g. us) don't download images manually, our mirror does. So this essentially means checking timestamps or checksums for every compose that we sync. That 1) requires some time spent for dozens of individuals 2) is error-prone, because *nobody* will do that every time, like a machine. Can we do better? I see two very simple solutions and they can be combined: 1. Use a "staging area" for new composes. It's really simple - create a directory that is not world-readable (thus not mirrored) and create the compose there. Once you are sure everything looks OK, move the compose to the correct directory. The other benefit is that this is nearly atomic, thus making sure we don't have half-synced mirrors. 2. Once something is public, don't change contents. It might happen that we publish something in error. But this is the same situation as in source tarballs for software projects. You can never change it, because you never know if somebody hasn't downloaded it in the (albeit short) meantime. You can delete, sure, but the fixed file/tarball/compose should always have a bumped version. There's no problem in that, really. If TC3 is published in error, delete it if you want, and create TC3.1 or TC4. It's just a safety practice and we don't mind, really, quite the opposite. This is a risk- prevention. If we combine these approaches, I believe there is no actual increase in your workload (these are just work approaches, but no extra load) and we increase the reliability of our tools and processes. Thanks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5636> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
15
0 / 0

#5802: Please retire btparser

by Fedora Release Engineering

#5802: Please retire btparser ---------------------+------------------------ Reporter: mmilata | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Keywords: | Blocked By: Blocking: | ---------------------+------------------------ I would like to retire btparser [1] from pkgdb, however the owner is ''abrt-team'' and noone from the team seems to know how to access this account. It is already retired in dist-git. Thank you! [1] https://admin.fedoraproject.org/pkgdb/acls/name/btparser -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5802> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 5 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng October 2013