#1462: tag google-gadgets-0.10.5-4.fc11
by Fedora Release Engineering
#1462: tag google-gadgets-0.10.5-4.fc11
-----------------------------+----------------------------------------------
Reporter: rdieter | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 11 Final | Component: other
Keywords: |
-----------------------------+----------------------------------------------
tag google-gadgets-0.10.5-4.fc11 for f-10 -> f11 upgrade path
(discovered myself this morning trying to upgrade to rawhide).
It's just a simple bump Release and rebuild, should be mostly harmless.
implicit +1 from me.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1462>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years
#1464: mash-0.5.0-1.fc11
by Fedora Release Engineering
#1464: mash-0.5.0-1.fc11
-----------------------------+----------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 11 Final | Component: koji
Keywords: |
-----------------------------+----------------------------------------------
Delta support! Sort of needed if we want to be able to generate them.
Yes, it's late. Patch is pretty small, though.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1464>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years
fedora-logos-11.0.0-1.fc11
by Tom Callaway
I went ahead and did this build and tagged into dist-f11, since we do
want the new art for the RC. It is missing the kde-splash logo, but
supposedly, I will get that before we go final.
~spot
15 years
Tagging for F11 release
by Jesse Keating
I'm trying something slightly different this freeze. dist-f11 tag is
locked, and builds are by default going to dist-f11-updates-candidate.
I'm not creating a f11-final tag just yet, so to fulfill tag requests a
move-pkg (--force) from dist-f11-updates-candidate to dist-f11 is
sufficient.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
15 years
#1455: urgent - untag shadow-utils-4.1.3-1.fc11
by Fedora Release Engineering
#1455: urgent - untag shadow-utils-4.1.3-1.fc11
---------------------+------------------------------------------------------
Reporter: pvrabec | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
I'm sorry, but I have crashed the buildsystem, because I removed obsolete
option in shadow-utils that was used by mock.
DEBUG util.py:280: Executing command: /usr/sbin/useradd -o -m -u 103 -g
103 -d /builddir -n mockbuild
DEBUG util.py:256: /usr/sbin/useradd: invalid option -- 'n'
Please, remove shadow-utils-4.1.3-1.fc11 as soon as possible. I have new
release already prepared. It's one line fix.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1455>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years
F-11 libunwind rebase permission
by Jan Kratochvil
Hi,
* A description of what you want to change
I would like to rebase libunwind on the upstream snapshot but there is now
a development freeze.
* Rationale for why the change is important enough to be allowed in after the
development freeze.
The basic rationale for permitting such rebase is that in fact nothing is
dependent on libunwind on Fedora.
Got a mail (2009-03-18) about google-perftools depending on the upstream
version of libunwind from Arun Sharma / Google already after the development
freeze.
Till that time I was not aware any tools is dynamically dependent on it,
besides gdb exclusively on ia64, which uses only its basic functionality.
Fedora gcc package also started to be dependent on libunwind exclusively on
ia64 due to https://bugzilla.redhat.com/show_bug.cgi?id=480412 , this decision
was made on 2009-04-02, also after the development freeze:
http://lists.gnu.org/archive/html/libunwind-devel/2009-04/msg00007.html
libunwind is also in use by frysk but (a) it has still in the latest Rawhide
build linked it in statically and (b) the frysk development is currently no
longer active.
For the Fedora arches (=non-ia64) it is used only by google-perftools which
track the upstream version (although they appear to be working with
frysk-patched libunwind).
* Impact of *not* accepting the development at this point of the schedule.
Not accepting the change just can make later support for google-perftools more
complicated during the whole RHEL-6 lifecycle.
It can also have some unexpected compatibility problems with google-perftools
as they are tested with the upstream libunwind variant. (I do not expect much
this case would happen.)
* Information on what testing you've already done on the development to help
reduce the risk.
Ran `pprof --text' of google-perftools on x86_64 to verify it works the same
way after the libunwind replace.
Scratch built:
http://koji.fedoraproject.org/scratch/jkratoch/task_1292040/
Thanks,
Jan
15 years
#1442: please tag lv2core in dist-f10
by Fedora Release Engineering
#1442: please tag lv2core in dist-f10
------------------+---------------------------------------------------------
Reporter: oget | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------+---------------------------------------------------------
The new ardour update requires slv2 which requires lv2core.
After lv2core is tagged and slv2 is built I will have to open another
ticket for tagging slv2.
Thanks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1442>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years
