Bug 1089575 - Please upgrade package to latest upstream (2.17)
Summary: Please upgrade package to latest upstream (2.17)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fakechroot
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Meng
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-21 02:31 UTC by Amit Saha
Modified: 2015-07-26 22:15 UTC (History)
4 users (show)

Fixed In Version: fakechroot-2.17.2-1.fc21
Clone Of:
Environment:
Last Closed: 2015-03-13 17:28:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Amit Saha 2014-04-21 02:31:34 UTC
Description of problem:

The latest upstream release is 2.17.2 and is actually backward incompatible with 2.9. For eg. an issue i ran into while working on a common code base for Fedora and Ubuntu (which has 2.17.2): http://unix.stackexchange.com/questions/125680/different-fakechroot-behavior-on-fedora-and-ubuntu/125719#125719


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Please let me know if you need any help in packaging it. I am not a packager, but I can try to help. thanks!

Comment 1 Amit Saha 2014-04-22 06:23:40 UTC
I could build the RPMs using the SPEC file from the current SRPM. I stripped off the patches (since it looks like they are already there in the upstream source) and also made other changes related to number of new config files and binaries. Here is the SPEC file I used: https://gist.github.com/amitsaha/11167198

It would be great if the package can be updated. Thanks.

Comment 2 Christopher Meng 2014-07-15 00:46:48 UTC
Can't you get the latest to f21 at least?

Comment 3 Fedora Admin XMLRPC Client 2015-02-26 11:16:43 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Update System 2015-03-05 13:14:46 UTC
fakechroot-2.17.2-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/fakechroot-2.17.2-1.fc22

Comment 5 Fedora Update System 2015-03-05 13:14:51 UTC
fakechroot-2.17.2-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/fakechroot-2.17.2-1.fc21

Comment 6 Fedora Update System 2015-03-05 17:11:12 UTC
Package fakechroot-2.17.2-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fakechroot-2.17.2-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3270/fakechroot-2.17.2-1.fc22
then log in and leave karma (feedback).

Comment 7 Amit Saha 2015-03-06 01:56:19 UTC
(In reply to Fedora Update System from comment #5)
> fakechroot-2.17.2-1.fc21 has been submitted as an update for Fedora 21.
> https://admin.fedoraproject.org/updates/fakechroot-2.17.2-1.fc21

sudo yum update --enablerepo=updates-testing fakechroot-2.17.2-1.fc21
Loaded plugins: langpacks, priorities
No Match for argument: fakechroot-2.17.2-1.fc21
No package fakechroot-2.17.2-1.fc21 available.
No packages marked for update


Any idea what I am doing wrong?

Comment 8 Christopher Meng 2015-03-06 05:32:55 UTC
fc21 testing update hasn't been pushed yet.

When there is a similar comment like comment 6, things are done really.

Comment 9 Fedora Update System 2015-03-13 17:28:01 UTC
fakechroot-2.17.2-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2015-03-14 09:17:46 UTC
fakechroot-2.17.2-1.fc21 has been pushed to the Fedora 21 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.