#4352: koji block request for renamed package: mcs
-----------------------+----------------------------------------------------
Reporter: mschwendt | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
-----------------------+----------------------------------------------------
Please block dead package "mcs" in koji: f15 f14 f13
It has been renamed in http://bugzilla.redhat.com/664963 and imported and
built for: f15 f14 f13
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4352>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4357: Block xfce4-remmina-plugin and gnome-applet-remmina from rawhide
----------------------+-----------------------------------------------------
Reporter: cwickert | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Please block xfce4-remmina-plugin and gnome-applet-remmina from rawhide.
Both packages are retired because remmina now has a generic trayicon.
Additionally, xfce4-remmina-plugin has broken deps because it does not
build with the xfce4-panel 4.8.
Boch packages are retired in packadb and marked dead.package in git. Is
there and anything more I need to do to?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4357>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4274: delete acidentally created branch
---------------------+------------------------------------------------------
Reporter: jvcelak | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: git
Keywords: |
---------------------+------------------------------------------------------
Hi,
I accidentally managed to create remote branch by typing:
{{{
$ git push f14:origin/f14/master
}}}
Instead of:
{{{
$ git push origin f14:f14/master
}}}
But I'm unable to delete it now:
{{{
$ git push origin :origin/f14/master
remote: + refs/heads/origin/f14/master tuned jvcelak DENIED by fallthru
remote: error: hook declined to update refs/heads/origin/f14/master
To ssh://jvcelak@pkgs.fedoraproject.org/tuned
! [remote rejected] origin/f14/master (hook declined)
error: failed to push some refs to
'ssh://jvcelak@pkgs.fedoraproject.org/tuned'
}}}
Please, can you delete it for me? It's tuned component.
(Maybe the hooks are wrong if I'm able to create the branch, but not to
delete it.)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4274>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
Hi list,
I'd like to help with (un)tagging packages to buildroot overrides and,
when I gained some practice with that, help with (un)blocking packages
and retiring orphaned packages.
I'm provenpackager and proventester, reviewed quite a few packages
and have read most SOPs at [2].
You can find more information on my userpage [1].
What is the usual process now?
(e.g. How to find a mentor/get started...)
Greetings,
Thomas
[1] https://fedoraproject.org/wiki/User:Tomspur
[2] http://fedoraproject.org/wiki/Category:Release_Engineering_SOPs
I saw that nirik was talking about needing people to help process
buildroot override requests, and thought I would offer to help.
I've read http://fedoraproject.org/wiki/Buildroot_override_SOP and just
need to have whatever access is necessary in koji granted to me.
Nick
--
Nick Bebout
nb(a)fedoraproject.org
#4363: Package unblock request : haddock
---------------------+------------------------------------------------------
Reporter: narasim | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: haddock |
---------------------+------------------------------------------------------
I have taken ownership of haddock package and got a re review completed at
https://bugzilla.redhat.com/show_bug.cgi?id=651613
Requesting to unblock builds for package haddock on F13 F14 and devel
branches
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4363>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#4369: Tag request ctpl-0.3.2-1.fc14 for dist-f14-override
--------------------+-------------------------------------------------------
Reporter: dmaphy | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Component: koji |
--------------------+-------------------------------------------------------
CTPL 0.3 is required by the new upstream release of Geany-Plugins. Without
it available it won't be possible to build Geany-Plugins 0.20. Thanks very
much in advance. :)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4369>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project