rel-eng April 2012

rel-eng@lists.fedoraproject.org

3 participants
134 discussions

#3883: more meaningful error if module isn't found
by Fedora Release Engineering 17 Jul '13

17 Jul '13

#3883: more meaningful error if module isn't found -------------------------+-------------------------------------------------- Reporter: kalev | Owner: rel-eng(a)lists.fedoraproject.org Type: enhancement | Status: new Milestone: | Component: other Keywords: | -------------------------+-------------------------------------------------- Right now fedpkg fails with access denied message if there is not such module: {{{ $ fedpkg clone gtkmm30 R access for gtkmm30 DENIED to kalev }}} Would be nice to get a more meaningful error in that case, perhaps "module not found". Filing it in releng trac as the error is coming from gitolite, just being passed along by fedpkg. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3883> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#5033: bodhi: unable to delete obsoleted update - internal server error
by Fedora Release Engineering 17 Jul '13

17 Jul '13

#5033: bodhi: unable to delete obsoleted update - internal server error ----------------------+------------------------ Reporter: jskarvad | Owner: rel-eng@… Type: defect | Status: new Milestone: | Component: other Keywords: | Blocked By: Blocking: | ----------------------+------------------------ memtest86+-4.20-3.fc16 update is obsoleted: https://admin.fedoraproject.org/updates/FEDORA-2011-16943/memtest86+-4.20-3… I tried to delete it by hitting the delete button, but it doesn't work: > 500 Internal error > > The server encountered an unexpected condition which prevented it from fulfilling > the request. > > Powered by CherryPy 2.3.0 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5033> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#3759: bad distro tags in Fedora 13/x86_64
by Fedora Release Engineering 17 Jul '13

17 Jul '13

#3759: bad distro tags in Fedora 13/x86_64 -------------------+-------------------------------------------------------- Reporter: james | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | -------------------+-------------------------------------------------------- From yum repolist -v fedora ... Repo-id : fedora Repo-name : Fedora 13 - x86_64 Repo-revision: 1274245576 Repo-tags : binary-x86_64 Repo-distro-tags: [cpe:/o:fedoraproject:fedora:13]: rawhide ...this isn't rawhide though. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3759> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 7

#2244: How to mass branch s390utils and other non-primary arch packages
by Fedora Release Engineering 17 Jul '13

17 Jul '13

#2244: How to mass branch s390utils and other non-primary arch packages --------------------+------------------------------------------------------- Reporter: toshio | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | --------------------+------------------------------------------------------- This is a rel-eng decision that I'll need input on. Currently the packagedb branches packages which are not blocked in koji. Some packages which are not built for the primary arch are blocked in koji -- s390utils for instance. Does the packagedb need to whitelist these or should the packages be unblocked as they are discovered? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2244> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#4605: bodhi crashes with 500 internal server error when i try to remove a build from a ticket
by Fedora Release Engineering 17 Jul '13

17 Jul '13

#4605: bodhi crashes with 500 internal server error when i try to remove a build from a ticket ---------------------+------------------------------------------------------ Reporter: lennart | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ Wanted to edit https://admin.fedoraproject.org/updates/selinux- policy-3.9.16-9.fc15,systemd-22-1.fc15 and replace selinux-policy-3.9.16-9.fc15 by selinux-policy-3.9.16-10.fc15, and i couldn't, because bodhi crashed. Regardless whether I tried to replace -9 with -10, or just tried to remove -9. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4605> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases
by Fedora Release Engineering 16 Jul '13

16 Jul '13

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ----------------------+----------------------------------------------------- Going through the F16 QA retrospective, there's this series of linked points from Andre Robatino: "robatino - Alpha and Beta torrents often have unsigned checksum files - this just happened with 16 Alpha. It also happened during F13 and F14 - see http://lists.fedoraproject.org/pipermail/test/2010-April/090106.html for F13 Beta, and https://bugzilla.redhat.com/show_activity.cgi?id=638738 for F14 Alpha and Beta. When it's pointed out, we're told that it's not feasible to change them once people have started downloading, but if this is true, there needs to be better checking (at least as much as for mirror content, which can be changed) to make sure the torrents are correct before being posted. Filed https://fedorahosted.org/fedora-qa/ticket/237 and https://fedorahosted.org/rel-eng/ticket/4906 . No response from releng as of yet. Unless QA is given access prior to public posting, it is powerless to prevent this. robatino - Also, it's possible that the checksum files can be signed more than once. There are two versions of the signed checksum files for F15, one on the torrents (the original ones) and a different one on the mirrors. See http://robatino.fedorapeople.org/checksums/15-Final/ for the two versions - for example, Fedora-15-i386-CHECKSUM.orig and Fedora-15-i386-CHECKSUM. While not nearly as serious as the above issue (since the checksums are the same and both signatures are good), it could be confusing. " A quick mail discussion prompted the suggestion from Andre that the best way to cover all these issues would be for there to be a Deliverables wiki page / SOP which clearly lists all the 'bits' that should be delivered for each image drop - Alpha, Beta, Final, TC and RC. This would provide a simple reference for whoever's doing the build to make sure everything has been provided. It would make most sense for this to live in releng's wiki space, I think, so filing against releng trac, but a QA person could certainly take care of creating the page in theory, I think. We should have this in place prior to F17 Alpha TC1. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#4149: Need a way to point EC2 instances to specific mirrors
by Fedora Release Engineering 21 Jun '13

21 Jun '13

#4149: Need a way to point EC2 instances to specific mirrors --------------------+------------------------------------------------------- Reporter: gholms | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: other Keywords: | --------------------+------------------------------------------------------- To get Fedora working well on Amazon's EC2 cloud computing service ![1] the Cloud SIG is working on creating yum mirrors inside Amazon's network. Doing so provides a number of benefits: * Faster updates for users * People with hundreds of Fedora instances don't overload other public mirrors * No data transfer costs for users or those who fund the EC2 mirrors (traffic within a given cloud region is free) Unfortunately, data transfers are only free if they stay within a given region. This, combined with the fact that EC2's IP addresses freely roam between regions, makes normal IP-based direction via !MirrorManager impossible. We therefore need another way of directing clients toward the mirrors that reside within their own regions. Our list of proposed solutions to this are posted in the "Client Access" portion of my overall proposal for EC2 mirror infrastructure ![2]. Could you folks (a) offer any feedback, or (b) choose which solution would be best? I apologize if this is more of a FESCo question; I can take it to them if that would be better. ![1] https://fedoraproject.org/wiki/Features/EC2 ![2] https://fedoraproject.org/wiki/User:Gholms/EC2_Mirror_Proposal#Client_Access -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4149> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 10

#5162: Keep Branched TCs/RCs until Final GOLD
by Fedora Release Engineering 29 Apr '13

29 Apr '13

#5162: Keep Branched TCs/RCs until Final GOLD -----------------------------+------------------------ Reporter: kparal | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 17 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ There has been this discussion: http://lists.fedoraproject.org/pipermail/test/2012-April/106961.html After some responses were gathered on test list, I humbly ask RelEng team to keep all the TCs/RCs available in the future until Fedora Branched is GOLD, unless some technical problems appear (storage, bandwidth). It will improve the release quality. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5162> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#4963: Remove delta RPMs from Everything before release
by Fedora Release Engineering 13 Jan '13

13 Jan '13

#4963: Remove delta RPMs from Everything before release --------------------+------------------------------------------------------- Reporter: gholms | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: mash Keywords: | --------------------+------------------------------------------------------- F15's Everything tree contains around 4G of delta RPMs that are of limited use when the release is finalized. If they aren't necessary, I would appreciate the extra mirror space that removing them from F16 and beyond would free up. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4963> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#4057: Update gitolite build
by Fedora Release Engineering 19 Oct '12

19 Oct '12

#4057: Update gitolite build ----------------------+----------------------------------------------------- Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: cvs Keywords: | ----------------------+----------------------------------------------------- Need to do a new gitolite build from upstream and get it into el6 and test it on pkgs.stg then move it to pkgs. This should allow us to remove some of our custom hacks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4057> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng April 2012