#1107: auto-cleanup rawhide trees
-------------------------+--------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------+--------------------------------------------------
Rawhide tree expiry is manual at the moment, unless I missed something.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1107>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4985: Extend test image creation SOP to require notification of delays
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Working through the F16 QA retrospective here:
https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective
One of the notes is:
"jlaska - Alpha TC1 - Missed the Alpha-TC1 milestone by 1 week, little to
no communication regarding status. With only two weeks Alpha ISO test
time, losing 50% of time almost certainly results in a slip. See rel-eng
ticket#4844 . None of the Alpha rel-eng release tickets have been filed at
this time.
adamw - perhaps releng image compose SOP should require updating of ticket
with progress info, especially when image compose / delivery is delayed?"
So: this ticket proposes that the releng 'Composing test images' SOP -
https://fedoraproject.org/wiki/Composing_test_images - should be extended
to require whoever is creating the images to post a comment on the image
request ticket if the compose is delayed, explaining the reasons for the
delay (so that any other interested party can attempt to contribute to
resolving them) and giving a best estimate of an ETA if possible (so other
groups can adjust their scheduling as best they can).
Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4985>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4071: Block pushes to origin/ in gitolite ACLs
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: git
Keywords: |
----------------------+-----------------------------------------------------
Common typo to create a new branch that starts with "origin/". We can
stop that at the ACL level.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4071>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4355: metadata for "grouped" files on master mirror
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
This may be less of an issue now that we don't have the split CD set, but
I would like it if rel-eng could produce a file into the master mirror
tree for "groups" of files that should be a single consistent download
set, such as a DVD and the checksum file, or the set of files that are
together inside a single torrent. MirrorManager is growing the idea of a
"file group", a single requestable entity that will return a metalink
listing each of the files in the file group. The intent was to use it for
the multi-CD download sets, but it's just as valuable for the DVD and
checksum file, or other similar groups. But it needs to be a file (say,
.fileset or something), in a directory that MM can find and use to build
the FileGroups.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4355>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3903: change component owner in bugzilla
----------------------+-----------------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
Could you create perl-fedora-maint as bug owner for all my perl-* modules
and perl component? I'm sharing bugs with my colleagues in RHEL and we'd
like to have it also for Fedora. I suppose set up mailing list is also
needed.
This should be applied only for perl modules, where I am an owner of the
package. Not only co-maintainer.
The group perl-fedora-maint should include mmaslano, ppisar, psabata.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3903>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3624: fullfilelist changes
-------------------------+--------------------------------------------------
Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: other
Keywords: |
-------------------------+--------------------------------------------------
After each push, we need to run the following command:
rsync -r . > fullfilelist
This should overwrite the fullfilelist that's there and isn't very useful
at the moment:
http://download.fedora.redhat.com/pub/fedora/fullfilelist
We can't do this via a cron job, it has to go out after each push so it
needs to be added to those scripts.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3624>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3761: add gpg signature for .treeinfo file and/or add CHECKSUM file for unsigned
content of images
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: meeting |
----------------------+-----------------------------------------------------
Description of problem:
Currently the only way to verify the contents of .treeinfo or the
installer
images is to download the .iso and the regarding -CHECKSUM file and check
it.
But e.g. preupgrade does not download the .iso but the *.img files, the
kernel
and the .treeinfo directly from a mirror. Therefore it is also not
possible to
easily verify these files. I guess the preupgrade way of updating is
somehow
popular, therefore it should be possible to do this securely.
I filed a bug against preupgrade for not verifying anything and not
announcing
this here: bug 509338
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3761>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4267: collectd in EPEL
----------------------+-----------------------------------------------------
Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: mash
Keywords: |
----------------------+-----------------------------------------------------
Can we get collectd in EPEL set to disable multi-lib? It has become an
issue on EPEL where installing "collectd" via yum creates conflicts it
shouldn't.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4267>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4324: Change product string in pungi for better syslinux usability
-------------------+--------------------------------------------------------
Reporter: duffy | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
-------------------+--------------------------------------------------------
Right now when you boot Fedora live media or otherwise call up Syslinux,
you are greeted with:
"Welcome to Fedora-14-x86_64-Live-Desktop!"
It's not the most welcoming message though because the string is a bit
unwieldy and hard-to-read. Syslinux pulls from the PRODUCT string produced
via pungi:
scripts/mk-images.x86: sed -i "s/@PRODUCT@/$PRODUCT/g"
$MBD_BOOTTREE/syslinux.cfg
I was hoping that string produced by pungi could be cleaned up a bit to be
more friendly. Some examples I think that would be better:
Fedora 14 (32-bit)
Fedora 14 (64-bit)
Fedora 14 (32-bit DVD)
Fedora 14 (64-bit DVD)
Fedora 14: KDE Plasma (32-bit)
Fedora 14: KDE Plasma (64-bit)
Fedora 14: LXDE (32-bit)
Fedora 14: LXDE (64-bit)
Fedora 14: Xfce (32-bit)
Fedora 14: Xfce (64-bit)
Fedora 14: Electronic Lab (32-bit)
Fedora 14: Electronic Lab (64-bit)
Fedora 14: Design Suite (32-bit)
Fedora 14: Design Suite (64-bit)
Fedora 14: Sugar on a Stick (32-bit)
Fedora 14: Sugar on a Stick (64-bit)
Fedora 14: Games Spin (32-bit)
Fedora 14: Games Spin (64-bit)
Fedora 14: Security Lab (32-bit)
Fedora 14: Security Lab (64-bit)
So the rules I'm suggesting for the strings:
- The default desktop is called simply "Fedora $VERSION ($ARCH)"
- Any non-default spins are called "Fedora $VERSION: $NAME_OF_SPIN
($ARCH)"
- The spin name is derived from either the http://fedoraproject.org/en
/get-fedora-options#desktops get.fpo options page or the
spins.fedoraproject.org full name for the spin. (KDE is probably updating
theirs to KDE Plasma as reflected in example strings above.)
- Put the arch in () after the name of the spin. Where arch is '32-bit',
'64-bit', 'Power PC', etc. The arch names here are suggested to be
consistent with what the downloads are labeled on our main web pages
(get.fpo and spins.fpo)
- If it's live media, don't indicate that, don't point it out. Only
indicate if it's a DVD.
If it's DVD, point it out after the arch in the ( )
- $VERSION should be a whole number without decimals for a final release.
For test releases / release candidates it would be nice to indicate
something like, '14.92 RC1' '14.91 Nightly 06 Jan 2011' but that's up to
your discretion!
This is where the text will appear in syslinux:
https://fedoraproject.org/w/uploads/3/3d/Installux-syslinux-
prop1-proto1-ss2.png
What do you think?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4324>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3883: more meaningful error if module isn't found
-------------------------+--------------------------------------------------
Reporter: kalev | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: other
Keywords: |
-------------------------+--------------------------------------------------
Right now fedpkg fails with access denied message if there is not such
module:
{{{
$ fedpkg clone gtkmm30
R access for gtkmm30 DENIED to kalev
}}}
Would be nice to get a more meaningful error in that case, perhaps "module
not found".
Filing it in releng trac as the error is coming from gitolite, just being
passed along by fedpkg.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3883>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#2244: How to mass branch s390utils and other non-primary arch packages
--------------------+-------------------------------------------------------
Reporter: toshio | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
This is a rel-eng decision that I'll need input on. Currently the
packagedb branches packages which are not blocked in koji. Some packages
which are not built for the primary arch are blocked in koji -- s390utils
for instance. Does the packagedb need to whitelist these or should the
packages be unblocked as they are discovered?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2244>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4605: bodhi crashes with 500 internal server error when i try to remove a build
from a ticket
---------------------+------------------------------------------------------
Reporter: lennart | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
Wanted to edit https://admin.fedoraproject.org/updates/selinux-
policy-3.9.16-9.fc15,systemd-22-1.fc15
and replace selinux-policy-3.9.16-9.fc15 by selinux-policy-3.9.16-10.fc15,
and i couldn't, because bodhi crashed. Regardless whether I tried to
replace -9 with -10, or just tried to remove -9.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4605>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent
files, signatures, checksums etc should be provided with (pre)-releases
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Going through the F16 QA retrospective, there's this series of linked
points from Andre Robatino:
"robatino - Alpha and Beta torrents often have unsigned checksum files -
this just happened with 16 Alpha. It also happened during F13 and F14 -
see http://lists.fedoraproject.org/pipermail/test/2010-April/090106.html
for F13 Beta, and https://bugzilla.redhat.com/show_activity.cgi?id=638738
for F14 Alpha and Beta. When it's pointed out, we're told that it's not
feasible to change them once people have started downloading, but if this
is true, there needs to be better checking (at least as much as for mirror
content, which can be changed) to make sure the torrents are correct
before being posted. Filed https://fedorahosted.org/fedora-qa/ticket/237
and https://fedorahosted.org/rel-eng/ticket/4906 . No response from releng
as of yet. Unless QA is given access prior to public posting, it is
powerless to prevent this.
robatino - Also, it's possible that the checksum files can be signed more
than once. There are two versions of the signed checksum files for F15,
one on the torrents (the original ones) and a different one on the
mirrors. See http://robatino.fedorapeople.org/checksums/15-Final/ for the
two versions - for example, Fedora-15-i386-CHECKSUM.orig and
Fedora-15-i386-CHECKSUM. While not nearly as serious as the above issue
(since the checksums are the same and both signatures are good), it could
be confusing. "
A quick mail discussion prompted the suggestion from Andre that the best
way to cover all these issues would be for there to be a Deliverables wiki
page / SOP which clearly lists all the 'bits' that should be delivered for
each image drop - Alpha, Beta, Final, TC and RC. This would provide a
simple reference for whoever's doing the build to make sure everything has
been provided.
It would make most sense for this to live in releng's wiki space, I think,
so filing against releng trac, but a QA person could certainly take care
of creating the page in theory, I think.
We should have this in place prior to F17 Alpha TC1.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4149: Need a way to point EC2 instances to specific mirrors
--------------------+-------------------------------------------------------
Reporter: gholms | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
--------------------+-------------------------------------------------------
To get Fedora working well on Amazon's EC2 cloud computing service ![1]
the Cloud SIG is working on creating yum mirrors inside Amazon's network.
Doing so provides a number of benefits:
* Faster updates for users
* People with hundreds of Fedora instances don't overload other public
mirrors
* No data transfer costs for users or those who fund the EC2 mirrors
(traffic within a given cloud region is free)
Unfortunately, data transfers are only free if they stay within a given
region. This, combined with the fact that EC2's IP addresses freely roam
between regions, makes normal IP-based direction via !MirrorManager
impossible. We therefore need another way of directing clients toward the
mirrors that reside within their own regions.
Our list of proposed solutions to this are posted in the "Client Access"
portion of my overall proposal for EC2 mirror infrastructure ![2]. Could
you folks (a) offer any feedback, or (b) choose which solution would be
best? I apologize if this is more of a FESCo question; I can take it to
them if that would be better.
![1] https://fedoraproject.org/wiki/Features/EC2
![2]
https://fedoraproject.org/wiki/User:Gholms/EC2_Mirror_Proposal#Client_Access
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4149>
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
#4057: Update gitolite build
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: cvs
Keywords: |
----------------------+-----------------------------------------------------
Need to do a new gitolite build from upstream and get it into el6 and test
it on pkgs.stg then move it to pkgs. This should allow us to remove some
of our custom hacks.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4057>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3802: Symlink for latest branched and rawhide mash
--------------------+-------------------------------------------------------
Reporter: jlaska | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: mash
Keywords: |
--------------------+-------------------------------------------------------
== Problem Space ==
Currently, the [http://fedoraproject.org/wiki/Critical_Path_Packages
Critical Path Packages] wiki page links to most recently branched and
rawhide critpath.txt files. However, depending on the status of the
compose/mash/pungi, or the timing of the branched schedule, these log
files may not be available. In order to eliminate confusion and 404 links
from the wiki, it would be helpful to provide a link to an ''always''
available critpath.log URL.
== Proposal ==
Create a symlink for the latest successful branched and rawhide
pungi/mash/compose. This symlink will be referenced when directing users
to the latest definition of the critical path. For example:
* http://kojipkgs.fedoraproject.org/mash/rawhide-latest ->
http://kojipkgs.fedoraproject.org/mash/rawhide-20100618/
* http://kojipkgs.fedoraproject.org/mash/branched-latest ->
http://kojipkgs.fedoraproject.org/mash/branched-20100518/
The symlink would be updated upon successful mashing of rawhide or
branched.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3802>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#2025: Too hard to build dependent packages in stable
-------------------------+--------------------------------------------------
Reporter: hadess | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------+--------------------------------------------------
It's too complicated, human-dependent, and time-consuming to build
interdependent package updates in stable releases.
Two cases:
* gstreamer and gstreamer-plugins-base are released at the same time, and
so are pre-releases of those. They soft-depend on each other (gstreamer
can be updated on its own). It's currently not possible for me to offer
both pre-releases of gstreamer and gsteamer-plugins-base without either:
1. asking for a package to be tagged into the build roots
2. pushing gstreamer into stable (takes a few days at best), and push the
gstreamer-plugins-base package separately
* gnome-bluetooth and gnome-phone-manager, where I need to ask for gnome-
bluetooth to be pushed into the buildroot tree. Sometimes that just
doesn't work (as could have been seen in
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7140 /
https://fedorahosted.org/rel-eng/ticket/1945 and
http://koji.fedoraproject.org/koji/buildinfo?buildID=112091 )
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2025>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4987: Not able to mark fedora-review as '+' in bugzilla
--------------------+-------------------------------------------------------
Reporter: mmorsi | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
--------------------+-------------------------------------------------------
I have approved two packages for Fedora in bugzilla, rubygem-idn and
rubygem-addressable but am not able to select '+' as an option for the
fedora-review field. This has worked for me in the past and I was
wondering if anything was changed / broken and if anything had to be done
to resolve this.
https://bugzilla.redhat.com/show_bug.cgi?id=728088https://bugzilla.redhat.com/show_bug.cgi?id=588428
Thank you greatly.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4987>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5008: problem setting cvs flag - new package request
------------------+------------------------
Reporter: jcm | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: git
Keywords: | Blocked By:
Blocking: |
------------------+------------------------
NOTE: Trying to get this out in time for the holidays so folks can test :)
Hello everyone!
I have a new package request that has been reviewed, and I've added the
SCM boilerplate text:
https://bugzilla.redhat.com/show_bug.cgi?id=769832
I can't set the flag for you to review for some reason. Could you look
into fixing this for me? This package will replace module-init-tools in
a future Fedora release, and I am packaging it and preparing it now. It
is parallel installable at this time, and won't deprecate anything yet
without some co-ordination between everyone who is involved :)
Appreciate any help. I hope to get some initial rawhide packages built
over the holidays if you can resolve getting branches setup.
Jon.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5008>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4682: need empty updates-debuginfo repos created too
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
At the branchpoint, the rel-eng SOP includes creating empty
updates/{newversion}/{arch}/ repositories, and creating empty
updates/testing/{newversion}/{arch}/ repositories. However, corresponding
debuginfo repositories in updates/ are not created, while they are in
updates/testing/.
updates/testing/15/SRPMS/repodata
updates/testing/15/i386/debug/repodata
updates/testing/15/i386/repodata
updates/testing/15/x86_64/debug/repodata
updates/testing/15/x86_64/repodata
updates/15/i386/repodata
updates/15/SRPMS/repodata
updates/15/x86_64/repodata
MirrorManager returns an (empty) metalink document for non-existant
requested repositories. Yum requests these debuginfo repositories as well,
and doesn't like it when it gets back this (empty) metalink document. See
bug https://bugzilla.redhat.com/show_bug.cgi?id=679783
Please adjust the SOP to ensure that empty
updates/{newversion}/{arch}/debug/ repositories are created at the same
time updates/{newversion}/{arch} repositories are created.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4682>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4772: Update after 3 days in testing cannot be pushed to stable
----------------------+-----------------------------------------------------
Reporter: vondruch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
Hello, today I have received email from Bodhi:
bodhi - 2011-06-10 05:03:57 (karma: 0)
This update has reached 3 days in testing and can be pushed to stable now
if the maintainer wishes
However it can't be pushed according to bodhi:
This update has not yet met the minimum testing requirements defined in
the Package Update Acceptance Criteria
I believe it was always 7 days for stable release. Could you please fix
this discrepancy?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4772>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#4894: build override itstool-1.1.0-2.fc16
----------------------+-----------------------------------------------------
Reporter: sundaram | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
needed for deja-dup. can't do it via bodhi because I am not the
maintainer of itstool and bodhi won't let me
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4894>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4889: EPEL6: build root override - perl-Devel-StackTrace-AsHTML
------------------+---------------------------------------------------------
Reporter: jpo | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------+---------------------------------------------------------
Hi,
I would like to request an EPEL6 build root override for "perl-Devel-
StackTrace-AsHTML" as I need it to build perl-Plack. perl-Devel-
StackTrace-AsHTML-0.11-2.el6.1 has just been pushed for EPEL6 updates-
testing.
Warning: I don't have commit rights in rawhide; I only own the EPEL6
branch.
tia, [[BR]]
jpo
PS - These are other packages in the long perl-Dancer requirements list
(https://bugzilla.redhat.com/show_bug.cgi?id=729504)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4889>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4791: install of buildroot failed but install started
----------------------+-----------------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
The installation of buildroot failed, see:
http://koji.fedoraproject.org/koji/getfile?taskID=3149029&name=root.log
But build phase started, see:
http://koji.fedoraproject.org/koji/getfile?taskID=3149029&name=build.log
I'd like to point out that this bug is serious. Imagine, that you have
package in C, which is checking by configure installed packages. In
buildroot they are missing, but install could be successful because
configure detect available packages and use available. Therefore you can
have in specfile --with-selinux, but build could be done without SElinux
support.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4791>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4878: Buildroot override request for xmlrpc-c
----------------------+-----------------------------------------------------
Reporter: sgallagh | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
We're trying to get FreeIPA built for Fedora, but we need a buildroot
override of xmlrpc-c-1.27.4-1600.svn2171.fc16 and
xmlrpc-c-1.25.4-1500.svn2077.fc15 to their respective buildroots
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4878>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4823: Buildroot overrides for bouncycastle-mail-1.46-1.el6
---------------------+------------------------------------------------------
Reporter: s4504kr | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
I want to request a buildroot overirdes for the package bouncycastle-
mail-1.46-1.el6 to the dist-6E-epel tag
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4823>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4786: update mock in koji
----------------------+-----------------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Could you please update to new mock 1.1.11? It does solve build failures
with pty/tty devices.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4786>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4999: Need to un-block gnome-applet-sensors
----------------------+-----------------------------------------------------
Reporter: huzaifas | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Hi,
gnome-applet-sensors was blocked from building in koji, because it had
FTBS for a few releases, and also because the code was not compatible with
gnome 3. The problem has been solved now, and i want to re-introduce g-a-s
into fedora.
Can you please un-block it?
Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4999>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4056: Update sigul systems
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
there is new python-nss stuff we should built up and look at. Might also
setup a staging environment on el6 and see if things work (better?) there.
Also need to make a change to the user environment so that v3 sigs are
preferred by default.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4056>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4883: unblock scantailor for rawhide
--------------------+-------------------------------------------------------
Reporter: xhorak | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
package scantailor was blocked for rawhide, I'd like to have it unblocked
to supply updates for this package.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4883>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3740: fix critpath generation to be per branch and properly import into pkgdb
---------------------+------------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
As I understand it, critical path generation should work like this:
{{{
* Lists are generated at rawhide, branched, or updates compose time
* These lists are synced into pkgdb for that branch
* bodhi then reads these from pkgdb
}}}
Where are we currently? For the first item, we only generate critpath
during rawhide/branched compose.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3740>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4988: Package not being pushed to updates-testing
--------------------+-------------------------------------------------------
Reporter: dbhole | Owner: rel-eng(a)lists.fedoraproject.org
Type: defect | Status: new
Milestone: | Component: koji
Keywords: |
--------------------+-------------------------------------------------------
Hi,
https://admin.fedoraproject.org/updates/FEDORA-2011-16438/icedtea-
web-1.1.4-3.fc16 says that the update was pushed to updates-testing on the
25th. However I don't see it on any of the mirrors even though those
mirrors seem to have items on them that were pushed after the 25th.
Is this a bug, or just expected delay?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4988>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#859: updates-newkey doesn't have group_gz member
-------------------------------------+--------------------------------------
Reporter: james(a)fedoraproject.org | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------------------+--------------------------------------
I assume the createrepo instance that generates the Fedora 9 updates-
newkey/updates-testing-newkey is the RHEL-5 version?
Can we change this to be the Fedora 9 version so that we'll get group_gz
as well as group (ie. comps.xml.gz as well as comps.xml). This makes for
much less data to download, to get group information.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/859>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4722: Create tickets and plan tasks for EOL
-----------------------------+----------------------------------------------
Reporter: ausil | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 15 Final | Component: koji
-----------------------------+----------------------------------------------
Create tickets and plan tasks for EOL
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4722>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4719: Propose Schedule for Next Release
-----------------------------+----------------------------------------------
Reporter: ausil | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 15 Final | Component: koji
-----------------------------+----------------------------------------------
Propose Schedule for Next Release
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4719>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4994: Make it clear in releng SOPs that branching must be complete prior to Alpha
compose
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
I'm working through the F16 QA retrospective:
https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective
One of the notes there from jlaska reads:
jlaska - Alpha branch - Unclear when the F16 branch was completed as not
all tasks in the Mass_Branching_SOP were completed. The SOP either needs
to be followed or updated.
MirrorManager was not updated to add a fedora-16 repo tag, therefore,
TC1 installations could not find a repository to install from (RHBZ
#727428)
TC1 images were built with Version=16-Alpha.TC1 specified as the
--version argument to pungi. This results in a file /.buildstamp in the
install image with an incorrect version (Version=16-Alpha.TC1) that is
used as the $releasever variable for yum. The net result is that there are
no yum repos that match repo=16-Alpha.TC1&arch=x86_64. The version needs
to be an integer, or MirrorManager redirects need to be established prior
to compose.
The fedora-release package was not properly updated to include
[fedora] with enabled=1. As a result, TC1 images included a fedora-release
package that didn't enable the Fedora 16 repos.
The fedora-release package was not updated to include the Fedora 16
release name Verne. This is a minor issue, but results in login prompts
claiming the system is Rawhide. Recommend updating (or creating) the
existing Mass_Branching_SOP to document expected results when updating
fedora-release
adamw - seems branching may not actually have been completed by time
of TC1 delivery, even. Perhaps appropriate releng SOPs should be updated
to clarify that branching - or at least some specified subset of branching
tasks - must be completed before Alpha TC1 delivery
Due to all of those issues, it seems like releng should have an SOP for
all the various tasks involved in branching, and the relationships between
releng SOPs should make it clear that all the branching tasks have to be
completed before an Alpha compose is attempted.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4994>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5001: Block some GNOME java packages from rawhide
----------------------+---------------------------------------------
Reporter: nsoranzo | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+---------------------------------------------
The following packages are dead upstream, orphaned since F16 and
deprecated for rawhide:
cairo-java
glib-java
libgconf-java
libglade-java
libgnome-java
libgtk-java
libvte-java
The only package still requiring them is frysk.
Please block them from rawhide.
Thanks,
Nicola
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5001>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5005: Retire rubygem-multimap
---------------------+---------------------------------------------
Reporter: mmorsi | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocking:
Blocked By: |
---------------------+---------------------------------------------
We've received word from the upstream project that it is dead / deprecated
(the one other package depending on it has been updated).
Could you please block further builds on this package starting in rawhide
/ F17.
Thank you
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5005>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project