Public bug reported:

I want to fetch a particular set of packages from a PPA, but not all
(the current example is getting a new version of update-manager from
Michael Vogt's repository at https://launchpad.net/~mvo/+archive - I
don't want to also drag in new experimental versions of apt that this
doesn't require).

So I tried setting up an apt preferences file as follows:
{{{
Package: update-manager
Pin: release o=LP-PPA-mvo
Pin-Priority: 600

Package: *
Pin: release o=LP-PPA-mvo
Pin-Priority: 0
}}}

This seems to be because although the main release file
(http://ppa.launchpad.net/mvo/ubuntu/dists/hardy/Release) for the
repository lists its origin as `LP-PPA-mvo`, the release file for the
component
(http://ppa.launchpad.net/mvo/ubuntu/dists/hardy/main/binary-i386/Release)
lists its origin as `Ubuntu`

Ways of fixing this to me would include:

1) Fix the component to reflect the origin LP-PPA-mvo (simplest, but involves 
reliance on the upstream repository)
2) Add the ability to set options for individual repositories in the sources 
lists (it seems crazy that you can't label stuff client side for selection)

A workaround is to use Pin: origin ppa.launchpad.net, but this then
applies to all PPAs and means you have to explicitly list all the
packages you want to fetch.

** Affects: apt (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Allow pinning based on individual PPA repository
https://bugs.launchpad.net/bugs/270817
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to