rel-eng January 2010

rel-eng@lists.fedoraproject.org

4 participants
85 discussions

#3298: Urgent help needed - test update cannot be pulled!
by Fedora Release Engineering 29 Jan '10

29 Jan '10

#3298: Urgent help needed - test update cannot be pulled! -----------------------+---------------------------------------------------- Reporter: mschwendt | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | -----------------------+---------------------------------------------------- I've run into a series of problems with bodhi. https://fedorahosted.org/bodhi/ticket/385 The latest defect is that the test update is "pending", but the packages are in the updates-testing repo and tagged accordingly, too. This is like that since yesterday. I _cannot_ edit the bodhi ticket to pull them and push a newer audacious release (2.2-10.fc12), since the packages are stuck in updates-testing. They are not moved back and tagged as candidates. Help! Is it possible to pull the packages? The test update is broken and requires another fix. I'd like to move on with this. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3298> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

SOP for your review
by John Poelstra 28 Jan '10

28 Jan '10

The dangerous duo of Jesse and John strikes again! Please review the latest SOP in advance of our meeting Monday so we can ratify it and start work on the next one. :) *Please make all changes to the wiki page.* https://fedoraproject.org/wiki/Purging_orphaned_packages Read it and review it from the perspective of: o not having any familiarity with the environment o could you execute this SOP using only the information presented on this page? New SOP writers are welcome at any time. You write up the raw text and I'll format it, proof it and put it on a wiki page. What could be easier? John

1 0

#3288: block 'sigen' from F-11, F-12 and rawhide
by Fedora Release Engineering 28 Jan '10

28 Jan '10

#3288: block 'sigen' from F-11, F-12 and rawhide ---------------------+------------------------------------------------------ Reporter: tomspur | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ sigen was retired, because upstream is dead and nothing else requires it anyway. (http://cvs.fedoraproject.org/viewvc/devel/sigen/) Please bock sigen from F-11, F-12 and rawhide. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3288> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#3296: Block lxde-settings-daemon from rawhide
by Fedora Release Engineering 28 Jan '10

28 Jan '10

#3296: Block lxde-settings-daemon from rawhide ----------------------+----------------------------------------------------- Reporter: cwickert | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ----------------------+----------------------------------------------------- Please remove lxde-settings-daemon from rawhide because it's functionality was merged into lxsession with 0.4.0. The package has been retired in pkgdb and marked dead in CVS. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3296> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#3297: rename qpidc into qpid-cpp in F13 and rawhide
by Fedora Release Engineering 28 Jan '10

28 Jan '10

#3297: rename qpidc into qpid-cpp in F13 and rawhide ---------------------+------------------------------------------------------ Reporter: nsantos | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ The qpidc package for F13 and rawhide needs to be renamed to qpid-cpp, to keep with upstream changes (fwiw, RHEL6 has already made the change). The specfile will have the necessary obsoletes. Could you please create the qpid-cpp top-level module for those two branches? Thanks, Nuno -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3297> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

Upcoming Fedora 13 Tasks
by John Poelstra 27 Jan '10

27 Jan '10

Start End Name Tue 26-Jan Tue 26-Jan Feature Submission Deadline Tue 26-Jan Tue 26-Jan Custom Spins Submission Deadline Thu 28-Jan Thu 28-Jan Create Installable Images for QA testing #2 Thu 04-Feb Thu 04-Feb Create Installable Images for QA testing #3 Fri 05-Feb Fri 05-Feb Alpha Blocker Meeting (F13Alpha) #1 Tue 09-Feb Tue 09-Feb Branch Fedora 13 from Rawhide Tue 09-Feb Tue 09-Feb Spins Freeze Tue 09-Feb Tue 09-Feb Orphan Rawhide Packages Tue 09-Feb Tue 09-Feb Feature Freeze (Testable|Complete)

1 0

#3294: Please block kmid from dist-f13
by Fedora Release Engineering 27 Jan '10

27 Jan '10

#3294: Please block kmid from dist-f13 ---------------------+------------------------------------------------------ Reporter: kkofler | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ The kmid package is obsoleted by kmid2 and is being retired from F13. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3294> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#3293: Need buildroot overrides for new package aseqmm
by Fedora Release Engineering 27 Jan '10

27 Jan '10

#3293: Need buildroot overrides for new package aseqmm ---------------------+------------------------------------------------------ Reporter: kkofler | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ I need the new package aseqmm tagged into the buildroots so I can build the also new package kmid2: aseqmm-0.2.0-2.fc12 into dist-f12-override aseqmm-0.2.0-2.fc11 into dist-f11-override -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3293> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

#3291: building for fc13 appears to be broken due to prob with glib2-2.23.2-2.fc13.x86_64
by Fedora Release Engineering 26 Jan '10

26 Jan '10

#3291: building for fc13 appears to be broken due to prob with glib2-2.23.2-2.fc13.x86_64 ---------------------+------------------------------------------------------ Reporter: kwright | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ DEBUG util.py:256: Error: Missing Dependency: libc.so.6(GLIBC_PRIVATE)(64bit) is needed by package glib2-2.23.2-2.fc13.x86_64 (build) DEBUG util.py:256: You could try using --skip-broken to work around the problem here are three examples: http://koji.fedoraproject.org/koji/taskinfo?taskID=1944495 http://koji.fedoraproject.org/koji/taskinfo?taskID=1944481 http://koji.fedoraproject.org/koji/taskinfo?taskID=1944512 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3291> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

New SOPs--please review and correct
by John Poelstra 26 Jan '10

26 Jan '10

Jesse wrote all the steps down and I wiki-fied them. Please review the pages below and *make changes to the wiki* as necessary. https://fedoraproject.org/wiki/Create_release_signing_key https://fedoraproject.org/wiki/Composing_test_images I suggest making these SOPs as detailed as possible, even if the needed commands are obvious to most people. We are creating these for people new to Release Engineering (like me) who can become potential contributors so we should make it as easy as possible for them. Please understand that that I have never performed any of these tasks myself or access to the systems to do. Therefore I have no way to know if what I've formalized makes complete sense or works. If system access is available to do so I'd be glad to proof these SOPs in that way. I'd love to get feedback and updates by Monday's Release Engineering meeting so that we can mark these done and tackle another one next week! :) Thanks, John

2 2

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2010