Bug 1063030 - Update to debhelper-9.20131227
Summary: Update to debhelper-9.20131227
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: debhelper
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Oron Peled
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-09 17:10 UTC by Sandro Mani
Modified: 2014-03-04 06:40 UTC (History)
2 users (show)

Fixed In Version: debhelper-9.20131227-2.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-04 06:40:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sandro Mani 2014-02-09 17:10:31 UTC
Description of problem:
FYI, doing some debian packaging stuff, I've update debhelper locally, my SRPM is here [1]. Happy to help maintaining debhelper if desired.

[1] http://smani.fedorapeople.org/debhelper-9.20131227-1.fc21.src.rpm

Comment 1 Sergio Basto 2014-02-09 21:32:53 UTC
Hi, 
I review this package but I don't have commit permissions for this package. 
debhelper-9.20131227 is already used in testing of Debian [¹] . So I agree in update this package at least for F21 . 

Oron, if you are very busy please accept me has committer in https://admin.fedoraproject.org/pkgdb/acls/name/debhelper


[¹] http://packages.debian.org/search?keywords=debhelper

Comment 2 Oron Peled 2014-02-09 22:30:24 UTC
regarding comment #1

 * Sergio, you are approved as committer to debhelper.
   (sorry for delaying this for so long).

 * I agree with you that Debian/stable long-release cycle
   doesn't match Fedora's

 * IMO, it's best to follow Debian/testing with all our deb* packages.
   - This is because Debian/stable release cycle is very long and
     doesn't match Fedora release cycle.
   - I think it's reasonable for both rawhide and current version
     (F20, F21 in our case).
   - With previous version (F19) we may choose to be more conservative
     and stop its updates when it's neer EOL.

Comment 3 Sandro Mani 2014-02-09 22:36:21 UTC
So you keep up to date with testing in rawhide an F20, but leave as-is in old-stable (except for security backports and critical bugs)? Just asking, so that I can follow the same practice with my debian related packages.

Comment 4 Fedora Update System 2014-02-10 20:03:24 UTC
debhelper-9.20131227-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/debhelper-9.20131227-1.fc20

Comment 5 Fedora Update System 2014-02-11 22:58:58 UTC
Package debhelper-9.20131227-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing debhelper-9.20131227-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-2249/debhelper-9.20131227-1.fc20
then log in and leave karma (feedback).

Comment 6 Sergio Basto 2014-02-12 17:03:08 UTC
(In reply to Oron Peled from comment #2)
> regarding comment #1
> 
>  * Sergio, you are approved as committer to debhelper.
>    (sorry for delaying this for so long).

no worries

(In reply to Sandro Mani from comment #3)
> So you keep up to date with testing in rawhide an F20, but leave as-is in
> old-stable (except for security backports and critical bugs)? Just asking,
> so that I can follow the same practice with my debian related packages.

Well , after debhelper-9.20131227 hit stable repo and no one complains, I will build that version for F19 ...

Comment 7 Fedora Update System 2014-02-19 23:39:10 UTC
debhelper-9.20131227-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/debhelper-9.20131227-2.fc20

Comment 8 Fedora Update System 2014-03-04 06:40:06 UTC
debhelper-9.20131227-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.