Aw: conflicts between Debian's and upstream's Debian package
Harald Dunkel wrote:
> I would like to use upstream's Debian/Ubuntu packages for a
> certain tool 'foo'. Its closer to what I need, and I don't
> have migrate between both versions before asking the mailing
> list for help or for reporting/fixing problems.
>
> Problem: The Debian maintainer messed up the version numbers
> and had to introduce a "1:" for his foo package. Now upstream's
> package always appears to be out of date, forcing me to override
> apt-get.
>
> If upstream's Debian package of a tool is "not good enough"
> for Debian for some reason, wouldn't it be reasonable to avoid
> a naming conflict on creating the Debian package?
Just to understand your problem: there is a package foo. Debian provides
it with version 1:A-B and upstream provides some self-compiled packages
with the same name under version C-D (and C-D < 1:A-B) and you want to
force apt to install the package from the upstream developers site.
I therefor guess, there is a sources list entry for the upstream .deb
repository?
IMO you could high-pin the upstream repository and down-pin debian.org
for this special package (even so, that it won't get installed at all).
Use the o= or a= syntax (man apt_preferences). Simply run
apt-cache policy
without any further arguments to see the values associated with
each sources.list entry. If you don't have a sources.list entry, you
might be able to pin-down the Debian-version number to make apt
stop trying to install the Debian-provided package.
These are the ways, I would try.
HTH and regerads, Daniel
Reply to: