rel-eng March 2014

rel-eng@lists.fedoraproject.org

12 participants
152 discussions

#5665: Providing a master CHECKSUMS file for boot.fpo
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5665: Providing a master CHECKSUMS file for boot.fpo -----------------------------+------------------------ Reporter: shaiton | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, as requested to webmasters[1], could we get a CHECKSUMS file (as provided for other Fedora releases) including all checksums? It also needs to be signed of course. You might decide that it is not needed, just forwarded the query. [1] https://lists.fedoraproject.org/pipermail/websites/2013-July/011535.html -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5665> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#1107: auto-cleanup rawhide trees
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#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

1 8

#5805: add index.asc files for cloud images for virt-builder
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5805: add index.asc files for cloud images for virt-builder ----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 20 Beta | Component: other Keywords: | Blocked By: Blocking: | ----------------------------+------------------------ Please add a GPG-signed 'index.asc' file to the Fedora 20 Images/ directory describing cloud images for virt-builder and other tools. The format is documented at http://libguestfs.org/virt-builder.1.html #creating-your-own-templates, and there's actually a Fedora example there. Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5805> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 16

#5721: Need application icons and application descriptions
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5721: Need application icons and application descriptions ----------------------------+------------------------ Reporter: rhughes | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Beta | Component: koji Keywords: | Blocked By: Blocking: | ----------------------------+------------------------ Hi, For the application installer preview I need the application icons and localized description data. I had the fedora-app-data package NAKd, but something needs to provide this data. Spot seemed to think it would be okay to include as metadata. The idea is to: * Generate the appstream.xml and appstream.tar files on koji * xmlmerge the .xml files and cat the .tar files when mash'ing the compose together. I've got C code to do the former, although someone familiar with python probably wants to re-write the code before putting it into koji. For F20 we can probably just ship the 15 most popular application icons and descriptions in gnome-software, although this won't scale with all the apps in Fedora. Any questions, I'm hughsie on IRC. Thanks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5721> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 19

#5856: tag git commit for successful builds in dist-git
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5856: tag git commit for successful builds in dist-git -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ After a build succeeded, the commit used to build from should be tagged in dist-git. The tag should probably be the build's name-version-release. The information about successful builds could be fetched from fedmsg. Action Items: - Check whether fedmsg contains messages for successful builds - Decide on the name for tags I can work on this, I just want to track this publicly here. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5856> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#5843: Create koji plugin to allow building only from whitelisted git branches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5843: Create koji plugin to allow building only from whitelisted git branches -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ To allow user git branches, koji needs to be able to allow building only from whitelisted git branches such as master or epel-7. This might need to be addressed in a koji plugin. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5843> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 7

#5878: noarch packages corrupted on import on ppc.koji.fp.o
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5878: noarch packages corrupted on import on ppc.koji.fp.o -----------------------------+------------------------ Reporter: dwa | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 20 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ (Filing a ticket so other people can weigh in / brainstorm without getting lost in an e-mail thread) Recently (in the past 2 weeks or so) I've seen a number of source RPMs become corrupted when koji-shadow imports them to ppc.koji.fp.o. This was previously a once-in-a-blue-moon occurence but it's now happened multiple times. Most recently corrupted srpm: * moodle-2.5.5-1.fc20.src.rpm Previously: * mingw-gnutls-3.1.21-1.fc20 * elementary-xfce-icon-theme-0.4-1.fc20 * kde-l10n-4.12.3-1.fc20 * oxygen-icon-theme-4.12.3-1.fc20 I've not noticed this happening with any f19 packages, and f21 isn't signed (which is when we typically notice this is when signing packages.) ppc.koji is currently running koji-1.8.0-2.el6. Any ideas for troubleshooting? It's not difficult to fix (I've documented the procedure I'm using at https://fedoraproject.org/wiki/User:Dwa#Corrupt_noarch_RPMs ) but it'd be nice for it to not happen at all. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5878> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5678: koji package for cloud images so they can be non-scratch, and garbage collection policies for those packages
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5678: koji package for cloud images so they can be non-scratch, and garbage collection policies for those packages -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Replying to [ticket:3897 mattdm]: > We want to generate non-scratch cloud images. Because of a bug, these currently need to have the name of the architecture in the package. That will be fixed in the Real Soon Future, but in the meantime I'd like to get going with what we have. Could we please create koji packages named > > {{{ > Fedora-19-cloud-x86_64 > Fedora-19-cloud-i386 > Fedora-20-cloud-x86_64 > Fedora-20-cloud-i386 > Fedora-rawhide-cloud-x86_64 > Fedora-rawhide-cloud-i386 > }}} > > And, we would also like to have a custom garbage collection policy for these; even though they are not scratch builds, they don't need to stay around forever. If we can do a nightly builds (ideal), then I think a week is fine; if they are weekly, keeping a month around seems good. Of course, longer is always better. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5678> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#5622: [RFE] Allow user to (create/)delete private branches
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5622: [RFE] Allow user to (create/)delete private branches -----------------------------+------------------------ Reporter: vondruch | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 19 Alpha | Component: git Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I'd like to be able to manage my private branches. For example, in preparation for Ruby 2.0 release, I was pushing my changes to .spec file into Ruby's repository in dist git, into ruby-2.0 branch. This branch is already merged into master for some while and I'd like to delete it, but it is forbidden: {{{ $ git push -f origin :ruby-2.0 remote: + refs/heads/ruby-2.0 ruby vondruch DENIED by fallthru remote: error: hook declined to update refs/heads/ruby-2.0 To ssh://vondruch@pkgs.fedoraproject.org/ruby ! [remote rejected] ruby-2.0 (hook declined) error: failed to push some refs to 'ssh://vondruch@pkgs.fedoraproject.org/ruby' }}} Would it be possible to allow some development branches, which can be created and deleted as well, without need of opening rel-eng tickets etc? Thanks -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5622> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5329: RFE: Send branched report only when there is any change committed
by Fedora Release Engineering 29 Apr '15

29 Apr '15

#5329: RFE: Send branched report only when there is any change committed -----------------------------+------------------------ Reporter: pnemade | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, While we are in freeze, can branched report be only sent to the devel/test list when there is any change added for any package? Parag. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5329> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng March 2014