#5985: Delete branch created by mistake in dist-git: openstack-glance/f21-patches
-----------------------------+------------------------
Reporter: hguemar | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Hi, someone created a branch by mistake in dist-git: f21-patches in
openstack-glance. Could someone delete it ?
http://pkgs.fedoraproject.org/cgit/openstack-glance.git/log/?h=f21-patches
Thanks
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5985>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#5986: write script to get all git commits used to build a package
-----------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: other
Keywords: easyfix | Blocked By:
Blocking: 5856 |
-----------------------------+------------------------
Create a mapping from build NVR to commit ID and vice-versa.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5986>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#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
#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
#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
#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
#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
#5218: block httpd-devel.i686, php-devel.i686 from x86_64 compose
-----------------------------+------------------------
Reporter: jorton | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 18 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Could the .i686 packages for both httpd-devel and php-devel be blocked
from inclusion in the x86_64 compose, we don't (can't/won't) support them
biarch.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5218>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5215: Stage comps and spin-kickstarts during freezes
-----------------------------+------------------------
Reporter: adamwill | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 18 Alpha | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
As noted on the F17 QA retrospective by me and Bruno Wolff:
https://fedoraproject.org/wiki/Fedora_17_QA_Retrospective
it's a problem that we use git master of both comps and spin-kickstarts
for composes - not the latest packaged version - and both these git repos
are not frozen during freezes.
During the 17 cycle, we had a concrete example of a comps change during a
freeze causing considerable trouble:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=807879 - pulling
Boxes into comps during the Beta freeze made that issue a serious problem.
For spin-kickstarts, the same kind of thing is possible, and we also have
a release criterion requiring a spin-kickstarts package which matches the
.ks files used for the compose to be present in the release repository;
obviously, the lack of a git freeze makes this tricky to ensure.
So we would strongly recommend, at minimum, a mechanism for freezing spin-
kickstarts and comps at Alpha, Beta and Final freeze. Post-freeze changes
could be made following the same blocker/NTH process used for other post-
freeze changes.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5215>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project