[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#151119: marked as done (apt: using pins (slowly) pulls in unstable)

Your message dated Thu, 13 Aug 2015 22:26:22 +0200
with message-id <20150813222525.GA2407@debian.org>
and subject line Re: Bug#151119: apt: using pins (slowly) pulls in unstable
has caused the Debian Bug report #151119,
regarding apt: using pins (slowly) pulls in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
151119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=151119
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.5.4
Severity: normal

Some time ago I was using pins to have some packages from unstable on
a generally testing system.  Then one day one of those packages got
upgraded and pulled in a newer version of some library from unstable.
Unfortunately, that version conflicted with some other programs I had
installed, so those got upgraded to unstable too.  In the end I had a
system with a lot of packages from unstable.

Unfortunately I don't remember which packages were involved in that,
the issue just came up again and I thought it might be of interest.

I have no idea for a good solution to this problem, the only thing
that comes to mind is a warning (maybe requiring confirmation) when a
certain number of packages gets upgraded to unstable.

Jö.

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux jupiter 2.4.18-jupiter #1 Mon Apr 15 21:55:09 CEST 2002 i586
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages apt depends on:
ii  libc6                         2.2.5-6    GNU C Library: Shared libraries an
ii  libstdc++2.10-glibc2.2        1:2.95.4-7 The GNU stdc++ library

-- 
<Ku]aku> seen _Armus_
-:- SignOff Ku]aku: #macht (changing servers)
<Volk> I don't know who _Armus_ is.

--- End Message ---
--- Begin Message --- 
On Thu, Jun 27, 2002 at 02:38:31AM +0200, Jö Fahlke wrote:
> Package: apt
> Version: 0.5.4
> Severity: normal
> 
> Some time ago I was using pins to have some packages from unstable on
> a generally testing system.  Then one day one of those packages got
> upgraded and pulled in a newer version of some library from unstable.
> Unfortunately, that version conflicted with some other programs I had
> installed, so those got upgraded to unstable too.  In the end I had a
> system with a lot of packages from unstable.
> 
> Unfortunately I don't remember which packages were involved in that,
> the issue just came up again and I thought it might be of interest.
> 
> I have no idea for a good solution to this problem, the only thing
> that comes to mind is a warning (maybe requiring confirmation) when a
> certain number of packages gets upgraded to unstable.
> 
Closing this, as we will not fix it. The apt_preferences(5) manual
page now mentions that pinning can be dangerous, so I think that's
OK.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
    - If you don't I might ignore you.

--- End Message ---
Reply to: