[Bug 270817] Re: Allow pinning based on individual PPA repository

2011-04-15 Thread Julian Andres Klode
To the submitter: Pin-Priority: 0 does not exists. Only pins larger than 0 or less than 0 are correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/270817 Title: Allow pinning based on individual P

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-22 Thread Fr3ddie
> You can specify "Package: *" though... This is why I opened a new bug, but no answer unitl now... References: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/399474 -- Allow pinning based on individual PPA repository https://bugs.launchpad.net/bugs/270817 You received this bug notification

Re: [Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-22 Thread David Fraser
- "Julian Edwards" wrote: > For anyone reading this in the future, the package name in the > preferences file must be specified in full, you can't use wildcards > it > seems. (Thanks to Fr3ddie for the feedback) You can specify "Package: *" though... -- Allow pinning based on individual

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-13 Thread Julian Edwards
For anyone reading this in the future, the package name in the preferences file must be specified in full, you can't use wildcards it seems. (Thanks to Fr3ddie for the feedback) -- Allow pinning based on individual PPA repository https://bugs.launchpad.net/bugs/270817 You received this bug notif

Re: [Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-02 Thread Celso Providelo
On Thu, Jul 2, 2009 at 11:36 AM, Fr3ddie wrote: > Hi 'Celso', > > which is the list address? Can't find it. Become a member of https://edge.launchpad.net/~launchpad-users -- Celso Providelo IRC: cprov, Jabber: cp...@jabber.org, Skype: cprovidelo 1024D/681B6469 C858 2652 1A6E F6A6 037B B3F7 9F

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-02 Thread Fr3ddie
Hi 'Celso', which is the list address? Can't find it. Thank you -- 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 ubun

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-02 Thread Celso Providelo
Hi 'Freddie', It was fixed server-side, each PPA has a unique Origin: field, including the named ones. I don't think of anything that should be changed in previous series. Can you please send an email to launchpad-users ML describing the problem your are experiencing in details (sources_list you

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-07-02 Thread Fr3ddie
Hi, I'm using Hardy, and having the same problem till now: is the fix released for Hardy *too*? Thanks, -- 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 Ub

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-03-05 Thread Alan
Sorry, please disregard my two latest comments. There seems to have been a pinning conflict which led such files to have too an high priority. Everything works as expected. -- Allow pinning based on individual PPA repository https://bugs.launchpad.net/bugs/270817 You received this bug notificati

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-03-05 Thread Alan
Sorry, I ate the most importante sentence away. I wanted to say: if I make a pin like that, apt still tries to update some deb packages I already have in my system if it finds them in the ppa, (e.g. emerald, libemerald, some kde libs.) -- Allow pinning based on individual PPA repository https://

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-03-05 Thread Alan
I have got a similar issue with pinning with amd64 intrepid kde3 repos. http://ppa.launchpad.net/kb9vqf/ This is the sources.list.d file: deb http://ppa.launchpad.net/kb9vqf/ubuntu intrepid main deb-src http://ppa.launchpad.net/kb9vqf/ubuntu intrepid main Both the main Release file and the com

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-02-12 Thread Celso Providelo
That's right, David, good point. Also bear in mind that when we finish multiple-ppas per user (bug #158570) there will be a small change in the 'Origin' value, it will include the proposed PPA name. We will warn users appropriately when it's time and thanks for testing this feature. -- Allow pi

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-02-12 Thread David Fraser
Note that the change to the Origin will only be updated when a new package is released, so this will still be a problem on PPAs that haven't been updated since the fix was released -- Allow pinning based on individual PPA repository https://bugs.launchpad.net/bugs/270817 You received this bug not

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-02-11 Thread David Fraser
Yay, tested and working - setting Pin: release o=LP-PPA-mvo works now -- 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

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-01-29 Thread Celso Providelo
** Changed in: soyuz Status: Fix Committed => Fix Released -- 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 ubu

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-01-07 Thread Celso Providelo
RF 7513 ** Changed in: soyuz Status: In Progress => Fix Committed -- 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

[Bug 270817] Re: Allow pinning based on individual PPA repository

2009-01-06 Thread Celso Providelo
** Changed in: soyuz Status: Triaged => In Progress -- 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-bug

[Bug 270817] Re: Allow pinning based on individual PPA repository

2008-12-16 Thread Celso Providelo
** Changed in: soyuz Target: pending => 2.2.1 -- 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@list

[Bug 270817] Re: Allow pinning based on individual PPA repository

2008-11-03 Thread Lionel Dricot
I think my problem is a similar one. We use at work an apt-proxy that cache the official repository but also all the needed PPA. For example, we use the bzr ppa and thus we are having sources.list like that : #The official ubuntu repository deb http://local:/ubuntu intrepid main restricted u

[Bug 270817] Re: Allow pinning based on individual PPA repository

2008-10-28 Thread Celso Providelo
Thanks for reporting this inconsistency. ** Changed in: soyuz Importance: Undecided => High Assignee: (unassigned) => Celso Providelo (cprov) Status: Confirmed => Triaged Target: None => pending ** Tags added: ppa soyuz-publish -- Allow pinning based on individual PPA repo

[Bug 270817] Re: Allow pinning based on individual PPA repository

2008-10-28 Thread Anders Kaseorg
** Also affects: soyuz Importance: Undecided Status: New ** Changed in: soyuz Status: New => Confirmed ** Changed in: apt (Ubuntu) Status: New => Invalid -- Allow pinning based on individual PPA repository https://bugs.launchpad.net/bugs/270817 You received this bug noti