Bug 474911 - don't depend directly on fedora-release
Summary: don't depend directly on fedora-release
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: apt
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Axel Thimm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-05 21:28 UTC by Rahul Sundaram
Modified: 2013-03-13 05:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-12-31 11:14:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rahul Sundaram 2008-12-05 21:28:45 UTC
Description of problem:

To enable Fedora remixes, all packages which require repository files should depend on system-release instead of fedora-release directly, so as to allow someone to add fedora-release which provides system-release and avoid running afoul of the Fedora trademark guidelines and easily rebrand the distribution. I have ensured that all packages in Fedora and third party repo release packages as well have fixed this problem except apt. Please fix apt (and your repo release files) to depend on system-release instead of fedora-release. Thanks.

Comment 1 Panu Matilainen 2008-12-23 08:55:24 UTC
FWIW before this can happen apt needs to be taught to look into provides for APT::DistroVerPkg, currently it only looks at package name. No big deal and just a matter of doing, but until then the direct dependency on fedora-release is real.

Comment 2 Panu Matilainen 2008-12-31 11:14:32 UTC
Fixed in upstream + rawhide now

Comment 3 Fedora Update System 2009-01-07 08:05:11 UTC
apt-0.5.15lorg3.95-0.git416.3.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/apt-0.5.15lorg3.95-0.git416.3.fc10

Comment 4 Fedora Update System 2009-01-15 03:10:46 UTC
apt-0.5.15lorg3.95-0.git416.3.fc10 has been pushed to the Fedora 10 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.