#5439: Please remove virt-v2v from EPEL5
----------------------+------------------------
Reporter: crobinso | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
virt-v2v was once in EPEL5, but is now retired and dead.package'd. Though
I
still keep getting mails warning about broken dependencies:
https://lists.fedoraproject.org/pipermail/virt-
maint/2013-January/009602.html
Can this package be removed from EPEL5?
(sorry if this is the wrong place to ask, there's a non-existent email
address listed here:
https://fedoraproject.org/wiki/EPEL/FAQ#What_do_I_have_to_do_to_get_a_packa…
)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5439>
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
#5359: GenericError: Error importing archive file,
/mnt/koji/packages/texlive/2012/3.20120926_r27815.fc18/src/texlive-2012-3.20120926_r27815.fc18.src.rpm
already exists
-------------------+------------------------
Reporter: jnovy | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
-------------------+------------------------
Two consecutive builds failed with the message in ticket summary. One of
such build is this one:
http://koji.fedoraproject.org/koji/taskinfo?taskID=4576260
The srpm name shouldn't conflict with F19 builds because the F18 srpm
contains its %dist tag. Any hints?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5359>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5334: yum-langpacks-0.3.0-2.fc17 pushed stable but still in updates-testing!
----------------------+------------------------
Reporter: petersen | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
https://admin.fedoraproject.org/updates/FEDORA-2012-11861/yum-
langpacks-0.3.0-2.fc17 was pushed to stable on 2012-08-14 but in fact the
package is still in updates-testing
http://dl.fedoraproject.org/pub/fedora/linux/updates/testing/17/SRPMS/
Could you please sort it out?
I also would suggest doing a quick audit of f*-updates-testing to make
sure that there are not other builds there actually tagged to f*-updates.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5334>
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