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

Groups > linux.debian.user > #235556 > unrolled thread

Upgrading to Bullseye?

Back to article view | Back to linux.debian.user

Contents

  Upgrading to Bullseye? latincom@vcn.bc.ca - 2021-05-27 15:10 +0200
    Re: Upgrading to Bullseye? Greg Wooledge <greg@wooledge.org> - 2021-05-27 15:20 +0200
      Re: Upgrading to Bullseye? Kenneth Parker <sea7kenp@gmail.com> - 2021-05-27 15:40 +0200
        Re: Upgrading to Bullseye? <tomas@tuxteam.de> - 2021-05-27 16:20 +0200
        Re: Upgrading to Bullseye? latincom <latincom@resist.ca> - 2021-05-27 18:00 +0200
          Re: Upgrading to Bullseye? Greg Wooledge <greg@wooledge.org> - 2021-05-27 18:00 +0200
            Re: Upgrading to Bullseye? Cindy Sue Causey <butterflybytes@gmail.com> - 2021-05-27 21:00 +0200
    Re: Upgrading to Bullseye? <tomas@tuxteam.de> - 2021-05-27 15:20 +0200
      Re: Upgrading to Bullseye? latincom@vcn.bc.ca - 2021-05-27 18:10 +0200
    Re: Upgrading to Bullseye? Peter Ehlert <peter@sdi-baja.com> - 2021-05-27 16:00 +0200

#235556 — Upgrading to Bullseye?

Hello list

can somebody help with the correct sources.lst Bullseye please?

[toc] | [next] | [standalone]

#235557

On Thu, May 27, 2021 at 05:45:33AM -0700, latincom@vcn.bc.ca wrote:
> Hello list
> 
> can somebody help with the correct sources.lst Bullseye please?

There are several correct answers, depending on what you want.

If you intend to *stay* on bullseye when it becomes stable, then I
would go with:

deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free

Right now, those last two lines don't do anything, but they'll become
active once bullseye is stable.  Note that the format of the security
line has changed slightly since buster, so simply replacing buster with
bullseye in a file from a current Debian release isn't correct.

You may also need to add bullseye-backports later, but you can worry
about those later, if you need them.

If you intend to continue tracking "testing" even after bullseye
becomes stable, then simply use this:

deb http://deb.debian.org/debian/ testing main contrib non-free

There are no security updates for testing, so that's it.

[toc] | [prev] | [next] | [standalone]

#235560

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

On Thu, May 27, 2021, 9:12 AM Greg Wooledge <greg@wooledge.org> wrote:

> On Thu, May 27, 2021 at 05:45:33AM -0700, latincom@vcn.bc.ca wrote:
> > Hello list
> >
> > can somebody help with the correct sources.lst Bullseye please?
>
> There are several correct answers, depending on what you want.
>
> If you intend to *stay* on bullseye when it becomes stable, then I
> would go with:
>
> deb http://deb.debian.org/debian bullseye main contrib non-free
> deb http://security.debian.org/debian-security bullseye-security main
> contrib non-free
> deb http://deb.debian.org/debian bullseye-updates main contrib non-free
>

Thank you for reminding me to add "bullseye-security".  I went to Bullseye
a while ago, because Buster didn't have my needed release level of
qemu-kvm.  But this is, pretty close to being a "production system".

Right now, those last two lines don't do anything, but they'll become
> active once bullseye is stable.  Note that the format of the security
> line has changed slightly since buster, so simply replacing buster with
> bullseye in a file from a current Debian release isn't correct.
>
> You may also need to add bullseye-backports later, but you can worry
> about those later, if you need them.
>

I only use Backports, if needed for a particular product.

>
> If you intend to continue tracking "testing" even after bullseye
> becomes stable, then simply use this:
>
> deb http://deb.debian.org/debian/ testing main contrib non-free
>
> There are no security updates for testing, so that's it.
>

Thanks!

Kenneth Parker

>

[toc] | [prev] | [next] | [standalone]

#235563

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

On Thu, May 27, 2021 at 09:32:08AM -0400, Kenneth Parker wrote:

[...]

> > You may also need to add bullseye-backports later, but you can worry
> > about those later, if you need them.
> >
> 
> I only use Backports, if needed for a particular product.

AFAIK, by default backports have a lower priority than stable, so you'd
have to specify "-t backports" anyway on a case by case basis.

Unless you mess with the defaults, having the repo in the sources.list
is convenient: it makes installation (and browsing) much easier.

Cheers
 - t

[toc] | [prev] | [next] | [standalone]

#235569

Thank you

Here is the mistake:

deb http://security.debian.org/debian-security bullseye-security main 
contrib non-free

deb http://security.debian.org/debian-security buster/updates main 
contrib non-free

[toc] | [prev] | [next] | [standalone]

#235577

On Thu, May 27, 2021 at 08:30:16AM -0700, latincom wrote:
> Thank you
> 
> Here is the mistake:
> 
> deb http://security.debian.org/debian-security bullseye-security main
> contrib non-free
> 
> deb http://security.debian.org/debian-security buster/updates main contrib
> non-free

Yes, the format for the security line is changing in bullseye.  The new
format should be less confusing (no more "is it foo-updates or foo/updates"
questions) in the long run, but there will obviously be some initial
confusion during the transition.

[toc] | [prev] | [next] | [standalone]

#235590

On 5/27/21, Greg Wooledge <greg@wooledge.org> wrote:
> On Thu, May 27, 2021 at 08:30:16AM -0700, latincom wrote:
>> Thank you
>>
>> Here is the mistake:
>>
>> deb http://security.debian.org/debian-security bullseye-security main
>> contrib non-free
>>
>> deb http://security.debian.org/debian-security buster/updates main
>> contrib
>> non-free
>
> Yes, the format for the security line is changing in bullseye.  The new
> format should be less confusing (no more "is it foo-updates or foo/updates"
> questions) in the long run, but there will obviously be some initial
> confusion during the transition.


Speaking of Bullseye and transitions, "man sources.list" is now again
listing dot sources files. It did so a while back just long enough for
me to stumble on it then the extended reference seemed to disappear.
Today's "man sources.list" has two references under the
"SOURCES.LIST.D" and "DEB822-STYLE FORMAT" headings.

One caveat is that third party vendors will need to be advised on how
to sniff out a User's CHOICE toward that format. They will need to
adjust what they do accordingly. Once they figure it out the first
time, it's not an ongoing changing deal. It's just going to take them
adding one or more additional lines of code that have a checkpoint for
dot sources files.

Warnings about duplicate entries for any package after a User updates
apt or apt-get is the sign that tweak needs addressed by the TRUSTED
outside/third party vendor. That complaint will occur because the
vendor doesn't know to sniff the User's dot sources file(s) for their
own repositories in the same way vendors already take a poke at our
longstanding dot list files (based on personal experience).

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#235558

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

On Thu, May 27, 2021 at 05:45:33AM -0700, latincom@vcn.bc.ca wrote:
> Hello list
> 
> can somebody help with the correct sources.lst Bullseye please?

How do yours look at the moment?

Cheers
 - t

[toc] | [prev] | [next] | [standalone]

#235570

> On Thu, May 27, 2021 at 05:45:33AM -0700, latincom@vcn.bc.ca wrote:
>> Hello list
>>
>> can somebody help with the correct sources.lst Bullseye please?
>
> How do yours look at the moment?
>
> Cheers
>  - t
>

deb http://deb.debian.org/debian/ buster main non-free contrib
# deb-src http://deb.debian.org/debian/ buster main non-free contrib

deb http://security.debian.org/debian-security buster/updates main contrib
non-free
# deb-src http://security.debian.org/debian-security buster/updates main
contrib non-free

# buster-updates, previously known as 'volatile'
# deb http://deb.debian.org/debian/ buster-updates main contrib non-free
# deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

[toc] | [prev] | [next] | [standalone]

#235562

On 5/27/21 5:45 AM, latincom@vcn.bc.ca wrote:
> Hello list
>
> can somebody help with the correct sources.lst Bullseye please?
>
>
that's kinda complicated, as the others have already said

1. I suggest you review this, lots of info 
https://wiki.debian.org/DebianTesting

2. probably a fresh install, using the new RC1 ISO would be cleaner... 
https://www.debian.org/devel/debian-installer/

3. best yet, wait a few weeks. They are almost done repackaging it. It 
will be Stable real soon

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web