#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
#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
#4071: Block pushes to origin/ in gitolite ACLs
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: git
Keywords: |
----------------------+-----------------------------------------------------
Common typo to create a new branch that starts with "origin/". We can
stop that at the ACL level.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4071>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4355: metadata for "grouped" files on master mirror
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
This may be less of an issue now that we don't have the split CD set, but
I would like it if rel-eng could produce a file into the master mirror
tree for "groups" of files that should be a single consistent download
set, such as a DVD and the checksum file, or the set of files that are
together inside a single torrent. MirrorManager is growing the idea of a
"file group", a single requestable entity that will return a metalink
listing each of the files in the file group. The intent was to use it for
the multi-CD download sets, but it's just as valuable for the DVD and
checksum file, or other similar groups. But it needs to be a file (say,
.fileset or something), in a directory that MM can find and use to build
the FileGroups.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4355>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#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
#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
#4324: Change product string in pungi for better syslinux usability
-------------------+--------------------------------------------------------
Reporter: duffy | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
-------------------+--------------------------------------------------------
Right now when you boot Fedora live media or otherwise call up Syslinux,
you are greeted with:
"Welcome to Fedora-14-x86_64-Live-Desktop!"
It's not the most welcoming message though because the string is a bit
unwieldy and hard-to-read. Syslinux pulls from the PRODUCT string produced
via pungi:
scripts/mk-images.x86: sed -i "s/@PRODUCT@/$PRODUCT/g"
$MBD_BOOTTREE/syslinux.cfg
I was hoping that string produced by pungi could be cleaned up a bit to be
more friendly. Some examples I think that would be better:
Fedora 14 (32-bit)
Fedora 14 (64-bit)
Fedora 14 (32-bit DVD)
Fedora 14 (64-bit DVD)
Fedora 14: KDE Plasma (32-bit)
Fedora 14: KDE Plasma (64-bit)
Fedora 14: LXDE (32-bit)
Fedora 14: LXDE (64-bit)
Fedora 14: Xfce (32-bit)
Fedora 14: Xfce (64-bit)
Fedora 14: Electronic Lab (32-bit)
Fedora 14: Electronic Lab (64-bit)
Fedora 14: Design Suite (32-bit)
Fedora 14: Design Suite (64-bit)
Fedora 14: Sugar on a Stick (32-bit)
Fedora 14: Sugar on a Stick (64-bit)
Fedora 14: Games Spin (32-bit)
Fedora 14: Games Spin (64-bit)
Fedora 14: Security Lab (32-bit)
Fedora 14: Security Lab (64-bit)
So the rules I'm suggesting for the strings:
- The default desktop is called simply "Fedora $VERSION ($ARCH)"
- Any non-default spins are called "Fedora $VERSION: $NAME_OF_SPIN
($ARCH)"
- The spin name is derived from either the http://fedoraproject.org/en
/get-fedora-options#desktops get.fpo options page or the
spins.fedoraproject.org full name for the spin. (KDE is probably updating
theirs to KDE Plasma as reflected in example strings above.)
- Put the arch in () after the name of the spin. Where arch is '32-bit',
'64-bit', 'Power PC', etc. The arch names here are suggested to be
consistent with what the downloads are labeled on our main web pages
(get.fpo and spins.fpo)
- If it's live media, don't indicate that, don't point it out. Only
indicate if it's a DVD.
If it's DVD, point it out after the arch in the ( )
- $VERSION should be a whole number without decimals for a final release.
For test releases / release candidates it would be nice to indicate
something like, '14.92 RC1' '14.91 Nightly 06 Jan 2011' but that's up to
your discretion!
This is where the text will appear in syslinux:
https://fedoraproject.org/w/uploads/3/3d/Installux-syslinux-
prop1-proto1-ss2.png
What do you think?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4324>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#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
#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
#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
#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
#5181: i686 java-1.6.0-openjdk is in x86_64 repos
-----------------------------+------------------------
Reporter: dbhole | Owner: rel-eng@…
Type: defect | Status: new
Milestone: Fedora 17 Final | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
The x86_64 repos for Fedora 17 currently contain the i686 versions of
java-1.7.0-openjdk. These should be removed as 32-bit on 64-bit packages
are not supported atm:
http://mirrors.kernel.org/fedora/development/17/x86_64/os/Packages/j/
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5181>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#5174: F-17 update cannot be pushed despite qualifying for stable
-----------------------------+------------------------
Reporter: pghmcfc | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 17 Final | Component: other
Keywords: bodhi | Blocked By:
Blocking: |
-----------------------------+------------------------
I have a critical path update that has been in updates-testing for over
two weeks and has no negative karma, yet I still can't push it to stable:
https://admin.fedoraproject.org/updates/FEDORA-2012-6165/perl-IO-Socket-
SSL-1.66-1.fc17
Yesterday I received an email telling me it had been in updates-testing
for 14 days and I could push it to stable - but I couldn't.
Today I received an "old testing" reminder that I was able to push the
update. I still can't.
There is no "Mark as stable" link, editing the update and putting "Stable"
for "Request" has no effect, and using the bodhi command-line client tells
me that the update has not yet met the stable update criteria.
What's going on?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5174>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#5109: Change live media dirs to i386 to avoid confusion
----------------------------+------------------------
Reporter: kevin | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 17 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
See: https://fedorahosted.org/fesco/ticket/602
We would like to change the dir that live media are in from i686 to i386,
and the iso images themselves to be i386 instead of i686.
This would reflect that they are all 32bit images.
If there's some reason we shouldn't/can't do this, feel free to reopen the
fesco ticket for more discussion.
Thanks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5109>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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