Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2015-12-14 from 15:30:00 to 16:30:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/2026/
#6311: please retire the el5 branch of python-pycurl in pkgdb
-----------------------------+------------------------
Reporter: kdudka | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Final | Component: epel
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
As discussed with Tomas Hoger in Bugzilla:
https://bugzilla.redhat.com/1277490#c7
... python-pycurl should not exist in EPEL-5 because the package is
already included in RHEL-5. I have retired the el5 branch in dist-git but
I am not allowed to retire the branch in pkgdb:
{{{
$ pkgdb-cli orphan --retire python-pycurl el5
You are not allowed to retire the package: python-pycurl on branch el5.
}}}
Any help appreciated!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6311>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2015-12-07 from 15:30:00 to 16:30:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/2026/
Hello all,
One of the goals I had in mind with the initial proposal to move
all of the Rel Eng documentation out of the Fedora Wiki and into the
releng git repository on pagure[0] was to make the documentation
easier to keep up to date.
To further this idea, I wanted to propose a guideline (policy?) that:
1) In the event someone submits a pull request to introduce a new
script to the releng repo, it must come with documentation either in
the form or a Standard Operating Procedure (which we have a template
for also in the repo) or whatever is alternatively applicable before
it is accepted and merged.
2) In the event someone submits a pull request that changes
functionality in a user facing way that needs to be reflected in the
current documentation, the applicable section of the documentation
must be updated in order to have the pull request review passed and
merged.
The whole thing basically boils down to, "if you change or introduce
code that needs docs, you must add/change the docs to get the code
merged"
I look forward to feedback.
Thank you,
-AdamM
[0] - https://pagure.io/releng
Hello all,
On the off chance someone is looking for me later today or
tomorrow, I'll be out having sinus surgery. I'll be back online on
Monday and doing my best to keep up with email between now and then.
Happy hacking,
-AdamM
#6310: Unretiring aeskulap
------------------------------------+------------------------
Reporter: jenslody | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Final | Component: other
Keywords: request for unretiring | Blocked By:
Blocking: |
------------------------------------+------------------------
My name is Jens Lody (FAS-name: jenslody), I want to unretire aeskulap an
open-source DICOM viewer.
It was retired because of dependency problems.
These issue are fixed now.
The development on upstream has stalled since 2007 (except accepting some
pull-requests of debian maintainers).
I talked to the former upstream maintainer, and he mailed me, that he has
no time to work on this package any more, but would be glad if somebody
would work on it.
So I decided to fork the github repo and become the new upstream, at least
(hopefully) for Fedora.
I also talked to the former Fedora packager and he also has no objections.
The package is now (re-)reviewed:
https://bugzilla.redhat.com/show_bug.cgi?id=1269649 .
I can not do a package-db request, because the package already exists
(obviously).
I'll be happy if you can unblock the package for F22, F23 and devel
(rawhide).
Jens
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6310>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project