#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
12 years, 8 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
12 years, 10 months
#3507: Secondary arche only packages need to be unblocked in primary arch koji
by Fedora Release Engineering
#3507: Secondary arche only packages need to be unblocked in primary arch koji
---------------------+------------------------------------------------------
Reporter: ausil | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: meeting |
---------------------+------------------------------------------------------
Blocking secondary arch only packages causes two issues
1) they do not get branched at mass branch time
2) they get blocked in secondary arches when they sync blocked packages
I recommend that we unblock them on the primary arches.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3507>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
12 years, 10 months
#3695: perl as multi-arch in x86_64
by Fedora Release Engineering
#3695: perl as multi-arch in x86_64
-----------------------------+----------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 13 Final | Component: other
Keywords: |
-----------------------------+----------------------------------------------
perl is since F-10 shipped for x86_64 twice as perl.i686 and perl.x86_64.
We didn't ship it as multiarch before. I suppose this is a bug because I'm
not aware about any reason for this change. Could you fix it(remove i686
from x86_64 channel) for F-13 and later?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3695>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 1 month
#3561: metadata_expire=7d in branched Fedora repo files
by Fedora Release Engineering
#3561: metadata_expire=7d in branched Fedora repo files
---------------------+------------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: defect | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
We put:
metadata_expire=7d
in the 'main' fedora repo files. This works great with the release tree,
as it doesn't change. This doesn't work well with the branched repo,
however, as we push it every day.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3561>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 1 month
#3239: deltarpm missing for eclipse update (F12) - 3.5.1-20 => -21
by Fedora Release Engineering
#3239: deltarpm missing for eclipse update (F12) - 3.5.1-20 => -21
--------------------+-------------------------------------------------------
Reporter: bbaetz | Owner: rel-eng(a)lists.fedoraproject.org
Type: defect | Status: new
Milestone: | Component: other
Keywords: |
--------------------+-------------------------------------------------------
An update to eclipse was pushed today, however the eclipse packages don't
have the appropriate drpms available.
A drpm is available from the 'base' eclipse-jdt-3.5.1-4.fc12, but not from
the last update to -20
(https://admin.fedoraproject.org/updates/F12/FEDORA-2009-11860)
For example, I had eclipse-jdt-3.5.1-20.fc12.x86_64.rpm installed.
/fedora/linux/updates/12/x86_64/drpms/ on my local mirror has eclipse-
jdt-3.5.1-4.fc12_3.5.1-21.fc12.x86_64.drpm but no other relevant file.
I can generate a drpm locally using makedeltarpm, and apply it to the koji
(unsigned) -20 package to get an identical package. This means that I have
to download a 24M package rather than a 94k drpm. (Similarly for the 27M
eclipse-platform package)
Some packages (eg NetworkManager) do have a drpm from both the initial
version and the previous updated version.
I've seen this happen before (missing drpm) with other packages (internet
caps in .au means I notice large package updates), but haven't previously
looked into why.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3239>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 1 month
#3768: Override tag request: libfm-0.1.12-1.fc13
by Fedora Release Engineering
#3768: Override tag request: libfm-0.1.12-1.fc13
---------------------+------------------------------------------------------
Reporter: mtasaka | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
Hello:[[BR]]
[[BR]]
I plan to update pcmanfm to 0.9.7 on F-13 and for this the following
package
need to be in buildroot. Please tag the following package as
override.[[BR]]
[[BR]]
libfm-0.1.12-1.fc13
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3768>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 3 months
#3770: please tag opal-3.6.8-1 into build over rides
by Fedora Release Engineering
#3770: please tag opal-3.6.8-1 into build over rides
------------------------+---------------------------------------------------
Reporter: pbrobinson | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------------+---------------------------------------------------
Please tag the following builds into their respective Fedora release build
overrides.
opal-3.6.8-1.fc13
opal-3.6.8-1.fc12
opal-3.6.8-1.fc11
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3770>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
13 years, 3 months