-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/30/2014 04:05 AM, Andrei POPESCU wrote:
> On Ma, 29 iul 14, 22:52:15, The Wanderer wrote:
>
>>
>> Package: removal-prevention
>> Pin: version 1.0
>> Pin-Priority: 1001
>>
>>
>> produces no change in behavior; dist-upgrade s
On Ma, 29 iul 14, 22:52:15, The Wanderer wrote:
>
>
> Package: removal-prevention
> Pin: version 1.0
> Pin-Priority: 1001
>
>
> produces no change in behavior; dist-upgrade still wants to remove
> removal-prevention, and the packages it depends on.
>
> Similar things happen wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/29/2014 05:30 PM, Andrei POPESCU wrote:
> On Ma, 29 iul 14, 08:36:48, The Wanderer wrote:
>
>> root@apologia:/home/wanderer# apt-cache show removal-prevention
>> Package: removal-prevention
>> Status: install ok installed
>> Priority: require
On Ma, 29 iul 14, 08:36:48, The Wanderer wrote:
> root@apologia:/home/wanderer# apt-cache show removal-prevention
> Package: removal-prevention
> Status: install ok installed
> Priority: required
> Section: misc
> Installed-Size: 26
> Maintainer: Andrew Buehler
> Architecture: all
> Version: 1.0
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/29/2014 04:53 AM, Andrei POPESCU wrote:
> On Lu, 28 iul 14, 22:47:56, The Wanderer wrote:
>
>> I just now tried that as well (in combination with 'Priority:
>> required'), and it produced the same result: apt-get wanted to
>> remove the metap
On Lu, 28 iul 14, 22:47:56, The Wanderer wrote:
>
> I just now tried that as well (in combination with 'Priority:
> required'), and it produced the same result: apt-get wanted to remove
> the metapackage on dist-upgrade.
Could you please post the full output for that and 'apt-cache show' and
'ap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/28/2014 03:43 PM, Andrei POPESCU wrote:
> On Du, 27 iul 14, 16:07:34, The Wanderer wrote:
>
>> On 07/20/2014 09:10 AM, Andrei POPESCU wrote:
>>
>> Yes, even with 'Priority: essential'. Possibly that's a side effect
>> of something else (the
On Du, 27 iul 14, 16:07:34, The Wanderer wrote:
> On 07/20/2014 09:10 AM, Andrei POPESCU wrote:
>
> Yes, even with 'Priority: essential'. Possibly that's a side effect of
> something else (the default of 'Section: misc', maybe?), but I have
> nothing to really support that idea.
Essential is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/20/2014 09:10 AM, Andrei POPESCU wrote:
> On Du, 20 iul 14, 08:13:30, The Wanderer wrote:
>>
>> What I was aiming at with the version-number wildcard is to let a
>> single pinning stanza work repeatedly, for different fglrx-driver
>> versions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/21/2014 08:38 AM, The Wanderer wrote:
> On 07/21/2014 06:18 AM, Andrei POPESCU wrote:
>
>> On Du, 20 iul 14, 08:13:30, The Wanderer wrote:
>
>>> What I was aiming at with the version-number wildcard is to let a
>>> single pinning stanza work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/21/2014 06:18 AM, Andrei POPESCU wrote:
> On Du, 20 iul 14, 08:13:30, The Wanderer wrote:
>
>> What I was aiming at with the version-number wildcard is to let a
>> single pinning stanza work repeatedly, for different fglrx-driver
>> versions,
On Du, 20 iul 14, 08:13:30, The Wanderer wrote:
>
> What I was aiming at with the version-number wildcard is to let a single
> pinning stanza work repeatedly, for different fglrx-driver versions,
> without need for manual intervention.
Would it be acceptable to pin to a release? Something like
P
On Monday 21 July 2014 01:46:07 Ric Moore wrote:
> What
> is worse, I'm running in my Ubuntu partition to have a working desktop.
> That cuts a fella. :( Ric
:-(
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...
On 07/20/2014 11:53 AM, Chris Bannister wrote:
On Sun, Jul 20, 2014 at 08:39:16AM -0600, Joe Pfeiffer wrote:
Andrei POPESCU writes:
Note: I'd probably have the same problem with nvidia-driver, but my
aptitude is not suggesting removals as first option anymore due to:
// tweak Aptitude to not
On Sun, Jul 20, 2014 at 08:39:16AM -0600, Joe Pfeiffer wrote:
> Andrei POPESCU writes:
>
> > Note: I'd probably have the same problem with nvidia-driver, but my
> > aptitude is not suggesting removals as first option anymore due to:
> >
> > // tweak Aptitude to not suggest removals as first opti
Andrei POPESCU writes:
> Note: I'd probably have the same problem with nvidia-driver, but my
> aptitude is not suggesting removals as first option anymore due to:
>
> // tweak Aptitude to not suggest removals as first option
> Aptitude::ProblemResolver::SolutionCost "removals";
Whether it helps
On Du, 20 iul 14, 08:13:30, The Wanderer wrote:
>
> What I was aiming at with the version-number wildcard is to let a single
> pinning stanza work repeatedly, for different fglrx-driver versions,
> without need for manual intervention.
Right. I just thought of an entirely different approach: use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/20/2014 05:54 AM, Andrei POPESCU wrote:
> On Sb, 19 iul 14, 21:58:13, The Wanderer wrote:
>
>> Is there a way to tell apt to calculate its dependency resolution
>> so as to avoid removing a particular package, without limiting that
>> package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/20/2014 01:37 AM, Marko Randjelovic wrote:
> On Sat, 19 Jul 2014 21:58:13 -0400 The Wanderer
> wrote:
>
>> when an X not compatible with the newest available fglrx-driver is
>> available, 'apt-get dist-upgrade' still tries to remove
>> fglrx
On Sb, 19 iul 14, 21:58:13, The Wanderer wrote:
> Is there a way to tell apt to calculate its dependency resolution so as
> to avoid removing a particular package, without limiting that package to
> a particular version?
This is an interesting problem. I'd try pinning the installed version to
the
On Sat, 19 Jul 2014 21:58:13 -0400
The Wanderer wrote:
> when an X not compatible with the newest
> available fglrx-driver is available, 'apt-get dist-upgrade' still tries
> to remove fglrx-driver.
Then why don't you pin X?
--
http://markorandjelovic.hopto.org
Please make your donation for hu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Is there a way to tell apt to calculate its dependency resolution so as
to avoid removing a particular package, without limiting that package to
a particular version?
Specifically, I'd like to pin fglrx-driver to "installed" (but not
necessarily to
22 matches
Mail list logo
