Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #220778

Re: [OT] testing on unstable sources list

From Andrei POPESCU <andreimpopescu@gmail.com>
Newsgroups linux.debian.user
Subject Re: [OT] testing on unstable sources list
Date 2020-04-01 17:50 +0200
Message-ID <zQNMS-2W8-5@gated-at.bofh.it> (permalink)
References (4 earlier) <zPHqa-2ER-19@gated-at.bofh.it> <zPLk6-52A-23@gated-at.bofh.it> <zQ09s-5Ok-5@gated-at.bofh.it> <zQ0M9-6gU-7@gated-at.bofh.it> <zQKYF-17c-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Mi, 01 apr 20, 15:49:25, dalios wrote:
> On 3/30/20 2:26 PM, Andrei POPESCU wrote:
> 
> >> [...] and still retain testing in sources.list (having testing in 
> > sources.list when running unstable is a good idea anyway).
> 
> Can you be so kind and explain to me how is that a good idea? I am
> _definitely not_ as knowledgeable as you are, but that sounds strange
> enough to make me wonder what have I missed...
> 
> I have only tried unstable twice and only on secondary machines, just
> for experimenting. This question is only for learning purpose.

The recommendation is based on the statement of a Debian Release Manager 
some years ago[1].

Basically it may happen that a particular package is removed from 
unstable, which will also affect other packages that depend on it.

With testing in sources.list the package can be installed from there 
instead.

Because apt[2] by default prefers newer versions of a package, if a 
package is available in unstable and testing with different versions the 
unstable version will be preferred.

So the only downsides I can think of would be slightly longer download 
times on 'apt update' and possibly a late alert that a specific package 
is being removed from Debian (typically packages are removed from 
testing first, but it may happen the other way around as well).

[1] https://lists.debian.org/debian-devel/2009/03/msg00582.html
[2] and other package managers like aptitude, etc.

Hope this explains,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye Martin <mb0087@gmail.com> - 2020-03-29 00:00 +0100
  Re: Unsolvable dependency problems around libc / libcrypt on debian  testing/bullseye Andrei POPESCU <andreimpopescu@gmail.com> - 2020-03-29 08:00 +0200
    Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye Martin <mb0087@gmail.com> - 2020-03-29 12:40 +0200
      Re: Unsolvable dependency problems around libc / libcrypt on debian  testing/bullseye Andrei POPESCU <andreimpopescu@gmail.com> - 2020-03-29 13:40 +0200
        Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye Martin <mb0087@gmail.com> - 2020-03-29 16:50 +0200
          Re: Unsolvable dependency problems around libc / libcrypt on debian  testing/bullseye Andrei POPESCU <andreimpopescu@gmail.com> - 2020-03-29 21:00 +0200
            Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye Martin <mb0087@gmail.com> - 2020-03-30 12:50 +0200
              Re: Unsolvable dependency problems around libc / libcrypt on debian  testing/bullseye Andrei POPESCU <andreimpopescu@gmail.com> - 2020-03-30 13:30 +0200
                Re: [OT] testing on unstable sources list dalios <dalios@eumx.net> - 2020-04-01 14:50 +0200
                Re: [OT] testing on unstable sources list Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-01 17:50 +0200
                Re: [OT] testing on unstable sources list dalios <dalios@eumx.net> - 2020-04-02 09:00 +0200
    Re: Unsolvable dependency problems around libc / libcrypt on debian testing/bullseye Martin <mb0087@gmail.com> - 2020-03-29 12:40 +0200

csiph-web