[Fedora Release Engineering] #859: updates-newkey doesn't have group_gz member
by Fedora Release Engineering
#859: updates-newkey doesn't have group_gz member
-------------------------------------+--------------------------------------
Reporter: james(a)fedoraproject.org | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------------------+--------------------------------------
I assume the createrepo instance that generates the Fedora 9 updates-
newkey/updates-testing-newkey is the RHEL-5 version?
Can we change this to be the Fedora 9 version so that we'll get group_gz
as well as group (ie. comps.xml.gz as well as comps.xml). This makes for
much less data to download, to get group information.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/859>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
12 years, 3 months
#4054: Add regular FTBFS handling to each cycle
by Fedora Release Engineering
#4054: Add regular FTBFS handling to each cycle
-------------------+--------------------------------------------------------
Reporter: kevin | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
-------------------+--------------------------------------------------------
Each cycle Matt Domsch runs a mass rebuild against all fedora packages:
http://fedoraproject.org/wiki/FTBFS
Those that fail to build from source have bugs filed on them to be fixed.
After the Alpha we should orphan all packages that have FTBFS bugs that
are in "NEW" state (ie, not looked at by the maintainer). This would give
other folks a chance to pick up the package and fix it so it builds. In
the event that the package is not taken over or fixed, it would be dropped
at the same time as all the other orphans are dropped.
Timing for this should be determined and added to the rel-eng calendar and
list of tasks as well as a SOP written up to handle how to do this.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4054>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
12 years, 9 months
#3565: Please Tag libproxy-0.3.1-4.fc13 for F-13 Beta - default install of libproxy modules
by Fedora Release Engineering
#3565: Please Tag libproxy-0.3.1-4.fc13 for F-13 Beta - default install of
libproxy modules
----------------------------+-----------------------------------------------
Reporter: kwizart | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 13 Beta | Component: koji
Keywords: |
----------------------------+-----------------------------------------------
Hello,
I request libproxy-0.3.1-4.fc13 to be tagged as F-13 Beta.
This is the last update before the ABI change of the 0.4.0 version that
has already appeared in F-14.
Here is the Changelog between 0.2.3 and 0.3.1:
http://code.google.com/p/libproxy/source/browse/trunk/ChangeLog
On a side note, installing libproxy on a default desktop install of F-13
Alpha will, lead to have:
libproxy
libproxy-bin
libproxy-python
With this package, the default will lead to have:
libproxy
And that will be all, as all unneeded dependencies have been dropped as
described in:
https://bugzilla.redhat.com/show_bug.cgi?id=537569
Once that said, it would be more valuable to have libproxy-gnome installed
as soon as the gnome desktop is selected on install. (1)
Upstream advice is to use Rpm's 'Suggests' instead of 'Requires', as
requires would imply some circle dependencies.
But we don't use Suggests much if possible. So I think it would be better
handled by comps for now.
(1)
Same for:
libproxy-kde and KDE desktop
libproxy-mozjs and firefox
libproxy-webkit and WebKit-gtk
libproxy-networkmanager and NetworkManager
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3565>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years
#3575: Provide deltaisos for development releases
by Fedora Release Engineering
#3575: Provide deltaisos for development releases
--------------------+-------------------------------------------------------
Reporter: kparal | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
--------------------+-------------------------------------------------------
'''Background:'''
Currently Fedora 13 is in a development, that means Test Composes, Release
Candidates and Final versions of Alpha/Beta/Final milestones are regularly
released. During this period there may be even several releases in one
week. Each release consists of 1x 3.5GB DVD, 6x 700MB CD, 1x 200MB netinst
image and 1x 1GB LiveCD. This is created for i386 and x86_64
architectures.
This is quite large amount of data. Every person interested in occasional
or regular testing must download substantial part of this release. That
makes certain demands on user's internet connection and also !RelEng
infrastructure (internet bandwidth, I/O).
'''Proposal:'''
Release Engineering team will create a deltaiso file for every release of
current Fedora development series. This deltaiso file will contain
differences between that particular release and a previous release. That
means deltaisos will be created in this fashion:
* Fedora 13 Alpha TC1 -> Fedora 13 Alpha TC2
* Fedora 13 Alpha TC2 -> Fedora 13 Alpha RC1
* Fedora 13 Alpha RC1 -> Fedora 13 Alpha
* Fedora 13 Alpha -> Fedora 13 Beta TC1
* Fedora 13 Beta TC1 -> Fedora 13 Beta RC1
* Fedora 13 Beta RC1 -> Fedora 13 Beta RC2
* Fedora 13 Beta RC2 -> Fedora 13 Beta
* Fedora 13 Beta -> Fedora 13 (Final) TC1
* Fedora 13 (Final) TC1 -> Fedora 13 (Final) RC1
* Fedora 13 (Final) RC1 -> Fedora 13 (Final) RC2
* Fedora 13 (Final) RC2 -> Fedora 13 (Final)
Because deltaisos are useful typically for media that consists
[https://fedoraproject.org/wiki/Delta_ISOs mainly of RPM files] this
process would involve mainly DVD image and would not involve LiveCD. For
other media (CD, netinst) the decision is still to be made. Deltaisos for
DVDs are [http://thepiratebay.org/user/andre14965/ typically around
100MB].
Deltaisos will be stored in a single directory (e.g. deltaisos/ in
[http://alt.fedoraproject.org/pub/alt/stage/ /pub/alt/stage]), so it is
easy to convert any older ISO the user currently has into a new one, even
several releases forward. These deltaisos will be stored for the period of
the development release - beginning with Fxx Alpha TC and ending with Fxx
Final (with a small extra time after the final release to allow people to
upgrade their ISOs to the final release).
The deltaiso creation process may be easily automated and
[https://fedoraproject.org/wiki/Delta_ISOs is described on our wiki]. No
additional human interaction should be needed.
'''Rationale:'''
The main reason for this proposal is to enable people with slower internet
connection to participate in installation testing. This often involves not
only developing countries, but also highly-developed countries
[http://lists.fedoraproject.org/pipermail/devel/2010-March/133326.html
like the USA]. I believe that although some more people would be
interested in doing installation testing, it is currently too expensive
for them from download time and bandwidth perspective.
Quite interestingly this also includes me as a Red Hat employee. While it
is my job to perform installation testing regularly, our office does not
have internet line thick enough such that I could afford downloading DVD-
sized images several times a week. Performing regular nightly mirroring is
not an option when new releases may be pushed even daily.
Up till now Andre Robatino (CCed) has been performing the repetitive task
of downloading every development release for every architecture, creating
deltaisos and publishing them [http://thepiratebay.org/user/andre14965/ as
torrents] (because he doesn't have any publicly available storage). Our
evidence shows that these torrents are used, which means they are useful
for people (and his work is invaluable for me personally). QA has started
to exploit his work officially
[https://fedoraproject.org/wiki/Test_Results:Fedora_13_Beta_RC3_Install on
every installation testing page].
The problem is that Andre is usually the only seeder, so the download
speed is really slow and there are connection problems sometimes, so
people often
[http://lists.fedoraproject.org/pipermail/test/2010-March/089110.html
complain about it]. Second problem is that those deltaisos are published
with a noticeable delay (Andre has to detect new release, download, build,
upload and announce). Overall this a huge waste of Andre's time and
energy. A defined and automated process from !RelEng side would simplify
all of this and improve the experience for our users a lot.
Another benefit would be lowered IO/bandwidth load on Fedora
infrastructure.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3575>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 3 months
#3996: 1 Package missing from mirrors
by Fedora Release Engineering
#3996: 1 Package missing from mirrors
------------------+---------------------------------------------------------
Reporter: limb | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: mash
Keywords: |
------------------+---------------------------------------------------------
ailurus-10.07.8-2.fc13 was announced 8/10/2010, but as of 8/23 is not
present.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3996>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 5 months
#3838: File F-14 rel-eng ISO tickets early
by Fedora Release Engineering
#3838: File F-14 rel-eng ISO tickets early
--------------------+-------------------------------------------------------
Reporter: jlaska | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
--------------------+-------------------------------------------------------
Greetings, during the
[https://fedoraproject.org/wiki/Fedora_13_QA_Retrospective#Release_Enginee...
Fedora 13 QA retrospective], it was identified that the tickets used to
track QA ISO drops were tremendously useful, but often not created ahead
of time. This ticket is intended to trac any changes or recommendations
to improve the situation. I'm not sure if you'd like to create all F-14
rel-eng tickets ahead of time, or establish some other process.
The hope is that we could collaborate on these tasks ahead of time and
avoid filing tickets that would only be CLOSED DUPLICATE.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3838>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 6 months
#3763: Scan comps for dead packages
by Fedora Release Engineering
#3763: Scan comps for dead packages
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
Often maintainers forget to remove packages from comps when they get
retired. We should check periodically for this situation and alert
releng.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3763>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 6 months