rel-eng July 2010

rel-eng@lists.fedoraproject.org

5 participants
109 discussions

#1107: auto-cleanup rawhide trees
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#1107: auto-cleanup rawhide trees -------------------------+-------------------------------------------------- Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org Type: enhancement | Status: new Milestone: | Component: koji Keywords: | -------------------------+-------------------------------------------------- Rawhide tree expiry is manual at the moment, unless I missed something. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1107> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 8

#3903: change component owner in bugzilla
by Fedora Release Engineering 07 Sep '14

07 Sep '14

#3903: change component owner in bugzilla ----------------------+----------------------------------------------------- Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: other Keywords: | ----------------------+----------------------------------------------------- Could you create perl-fedora-maint as bug owner for all my perl-* modules and perl component? I'm sharing bugs with my colleagues in RHEL and we'd like to have it also for Fedora. I suppose set up mailing list is also needed. This should be applied only for perl modules, where I am an owner of the package. Not only co-maintainer. The group perl-fedora-maint should include mmaslano, ppisar, psabata. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3903> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 15

#3624: fullfilelist changes
by Fedora Release Engineering 20 Jan '14

20 Jan '14

#3624: fullfilelist changes -------------------------+-------------------------------------------------- Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org Type: enhancement | Status: new Milestone: | Component: other Keywords: | -------------------------+-------------------------------------------------- After each push, we need to run the following command: rsync -r . > fullfilelist This should overwrite the fullfilelist that's there and isn't very useful at the moment: http://download.fedora.redhat.com/pub/fedora/fullfilelist We can't do this via a cron job, it has to go out after each push so it needs to be added to those scripts. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3624> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#3761: add gpg signature for .treeinfo file and/or add CHECKSUM file for unsigned content of images
by Fedora Release Engineering 06 Jan '14

06 Jan '14

#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

1 2

#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

#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

#3802: Symlink for latest branched and rawhide mash
by Fedora Release Engineering 19 Oct '12

19 Oct '12

#3802: Symlink for latest branched and rawhide mash --------------------+------------------------------------------------------- Reporter: jlaska | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: mash Keywords: | --------------------+------------------------------------------------------- == Problem Space == Currently, the [http://fedoraproject.org/wiki/Critical_Path_Packages Critical Path Packages] wiki page links to most recently branched and rawhide critpath.txt files. However, depending on the status of the compose/mash/pungi, or the timing of the branched schedule, these log files may not be available. In order to eliminate confusion and 404 links from the wiki, it would be helpful to provide a link to an ''always'' available critpath.log URL. == Proposal == Create a symlink for the latest successful branched and rawhide pungi/mash/compose. This symlink will be referenced when directing users to the latest definition of the critical path. For example: * http://kojipkgs.fedoraproject.org/mash/rawhide-latest -> http://kojipkgs.fedoraproject.org/mash/rawhide-20100618/ * http://kojipkgs.fedoraproject.org/mash/branched-latest -> http://kojipkgs.fedoraproject.org/mash/branched-20100518/ The symlink would be updated upon successful mashing of rawhide or branched. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3802> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 8

#2025: Too hard to build dependent packages in stable
by Fedora Release Engineering 17 Oct '12

17 Oct '12

#2025: Too hard to build dependent packages in stable -------------------------+-------------------------------------------------- Reporter: hadess | Owner: rel-eng(a)lists.fedoraproject.org Type: enhancement | Status: new Milestone: | Component: koji Keywords: | -------------------------+-------------------------------------------------- It's too complicated, human-dependent, and time-consuming to build interdependent package updates in stable releases. Two cases: * gstreamer and gstreamer-plugins-base are released at the same time, and so are pre-releases of those. They soft-depend on each other (gstreamer can be updated on its own). It's currently not possible for me to offer both pre-releases of gstreamer and gsteamer-plugins-base without either: 1. asking for a package to be tagged into the build roots 2. pushing gstreamer into stable (takes a few days at best), and push the gstreamer-plugins-base package separately * gnome-bluetooth and gnome-phone-manager, where I need to ask for gnome- bluetooth to be pushed into the buildroot tree. Sometimes that just doesn't work (as could have been seen in http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7140 / https://fedorahosted.org/rel-eng/ticket/1945 and http://koji.fedoraproject.org/koji/buildinfo?buildID=112091 ) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2025> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#3740: fix critpath generation to be per branch and properly import into pkgdb
by Fedora Release Engineering 26 Jan '12

26 Jan '12

#3740: fix critpath generation to be per branch and properly import into pkgdb ---------------------+------------------------------------------------------ Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ As I understand it, critical path generation should work like this: {{{ * Lists are generated at rawhide, branched, or updates compose time * These lists are synced into pkgdb for that branch * bodhi then reads these from pkgdb }}} Where are we currently? For the first item, we only generate critpath during rawhide/branched compose. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3740> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2010