#4993: Retire mediawiki115
--------------------+-------------------------------------------------------
Reporter: smooge | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
mediawiki115 is no longer supported and should be removed from EPEL
streams.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4993>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4992: Retire mediawiki114
--------------------+-------------------------------------------------------
Reporter: smooge | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
Package is End of Life and no longer supportable.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4992>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5019: Help needed recovering from a messed up nss-softokn-3.13.1-15.fc15 update
in bodhi
------------------------+------------------------
Reporter: emaldonado | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
------------------------+------------------------
Clicking on https://admin.fedoraproject.org/updates/nss-
softokn-3.13.1-15.fc15
will report an internal server error. I get failures using the bodhi
command line tools aslo and I think know the cause. While editing this
update I accidentally removed all builds from the list. Not realizing
that, I saved the edit which messed up things up in Bodhi.
Please help me recover from this. If the last resort solution is deleting
it, I'm okay with this. Thanks in advance.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5019>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5010: Tag nspr-4.8.9-2.fc15 into buildroot override for f15
------------------------+------------------------
Reporter: emaldonado | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
------------------------+------------------------
Needed to build nss-softokn
Attempts to to do it via bodhi fails with
bodhi --buildroot-override=nss-softokn-nspr-4.8.9-2.fc15 --notes="Needed
to build nss-softokn" -u emaldonado
Failed:
Error: buildroot override for u'nspr-4.8.9-2.fc15' already exists
To my surprise, attempt to manually expire it failed also
bodhi -u emaldonado --expire-override=nspr-4.8.9-2.fc15
Override nspr-4.8.9-2.fc15 already expired!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5010>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5006: nss-util broken F16
--------------------------+---------------------------------------------
Reporter: shakthimaan | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocking:
Blocked By: |
--------------------------+---------------------------------------------
One of my packages (flterm) doesn't build on F16 due to broken nss-utils.
http://koji.fedoraproject.org/koji/getfile?taskID=3600394&name=mock_output.…
It builds fine on F15 and F17.
Can you please resolve the nss-utils package? Thanks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5006>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5004: Tag request
---------------------+---------------------------------------------
Reporter: xhorak | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocking:
Blocked By: |
---------------------+---------------------------------------------
We need to tag: nss-3.13.1-9.fc16
as override due to firefox and thunderbird rebuild. Other nss packages are
already overridden.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5004>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4966: Please could you add geany-0.21-1.el6 to the buildroot for EL6
------------------+---------------------------------------------------------
Reporter: jgu | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------+---------------------------------------------------------
Hi,
I've tried adding a buildroot override via bodhi, but it doesn't seem to
work for EPEL? Anyway, please could you add geany-0.21-1.el6 to the
buildroot so I can build geany-plugins.
Thansk
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4966>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4955: update releases/15 repomd.xml timestamps to be newer than published
development/15 timestamps
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
https://fedorahosted.org/mirrormanager/ticket/35
<mdomsch> dgilmore: development/15 got a newer tree (with newer repomd.xml
timestamps) after releases/15 was published
<dgilmore> mdomsch: yeah i didsabled branched a day late
<mdomsch> which is a problem for anyone who updated in that window
<dgilmore> disabled
<mdomsch> now yum sees the development/15 timestamp, and the "older"
releases/15 timestamp, and throws out the releases/15 repomd.xml, keeping
the now-incorrect one.
<mdomsch> yum clean is needed to fix it
<dgilmore> mdomsch: considering the development/15 was removed ages ago im
not sure anyone should still see that
<mdomsch> skvidal: unfortunately yes
<skvidal> mdomsch: yum clean expire-cache should d oit
<mdomsch> skvidal: yum clean --enablerepo=\* or somesuch to pick up
debuginfo repos too...
<mdomsch> dgilmore: it's not that they still see it, it's that they saw it
once, with a newer timestamp than what they see now
<mdomsch> so a manual expire-cache is needed
<mdomsch> so between skvidal and dgilmore, how can we avoid that for f16+
?
<skvidal> how much newer is the timestamp?
<dgilmore> mdomsch: we really cant,
<skvidal> can we just touch the file(s) and move along?
<mdomsch> skvidal: hours
<mdomsch> it's not the file system timestamp, it's the repomd.xml
timestamp
<skvidal> okay can we modify the file manually
<dgilmore> mdomsch: well when we say go, i need to make sure i disabled
the branched repo then rsync the contents into place i guess
<mdomsch> <revision>1305638986</revision>
<mdomsch> is correct
<skvidal> right - I'm saying
<mdomsch> <revision>1305725445</revision>
<skvidal> 1. touch the files for a future date
<skvidal> 2. modify the repomd.xml to reflect that molestation
<mdomsch> skvidal: I like it
<skvidal> the mirrors should pick up the change in the repomd.xml and
mirror it out
<skvidal> the contents are all the same in the repodata - it just LOOKS
newer
<skvidal> this is not something I'd recommend doing often
<skvidal> but as a one-time deal
<skvidal> it seems easy enough
<mdomsch> skvidal: I presume that's a rel-eng task, and I should assign
there?
<skvidal> mdomsch: I think so....
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4955>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project