Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2021-03-26 Thread Justin B Rye
Justin B Rye wrote:
> It looks good, but I'd just made a note to myself that we might also
> want to mention this in upgrading.dbk where it discusses editing APT
> sources.  Hoping to send in some patches tomorrow.

Better late than never.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index 669a32bb..b26fb656 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -344,6 +344,17 @@ $ apt-forktracer | sort
 
   
 
+  
+The security section
+
+  For APT source lines referencing the security archive, the format
+  has changed slightly along with the release name, going from
+  buster/updates to
+  bullseye-security; see
+  .
+
+  
+
   
 The proposed-updates section
 


Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2021-03-17 Thread Justin B Rye
Paul Gevers wrote:
> On Wed, 10 Jul 2019 13:16:27 +0200 Ansgar Burchardt 
> wrote:
>> For bullseye, the security suite is now named bullseye-security
>> instead of buster/updates and users should adapt their sources.list
>> accordingly when upgrading.
>> 
>> People should probably use something like
>> 
>>   deb http://security.debian.org/debian-security bullseye-security main
>> 
[...]
> 
> Proposed patch attached.

It looks good, but I'd just made a note to myself that we might also
want to mention this in upgrading.dbk where it discusses editing APT
sources.  Hoping to send in some patches tomorrow.

Incidentally, the deb lines in our recipes are all http:// rather than
https://, because this is the first dist-upgrade where users have
started with apt-transport-https already guaranteed available.  We
might want to upgrade them all to https now.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package



Re: Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2021-03-17 Thread Paul Gevers
Hi,

On 17-03-2021 21:53, Andrei POPESCU wrote:
> On Mi, 17 mar 21, 21:30:04, Paul Gevers wrote:
>>
>> Proposed patch attached.
> 
> Any particular reason to use 'testing-security' instead of 
> 'bullseye-security' for the archive name?

Because I made a copy/paste mistake. I spotted the mistake while reading
the thread, but forgot about it when I wanted the deb.d.o, in stead of
the security.d.o. string.

So, thanks.

Paul



OpenPGP_signature
Description: OpenPGP digital signature


Re: Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2021-03-17 Thread Andrei POPESCU
On Mi, 17 mar 21, 21:30:04, Paul Gevers wrote:
> 
> Proposed patch attached.

Any particular reason to use 'testing-security' instead of 
'bullseye-security' for the archive name?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2021-03-17 Thread Paul Gevers
Control: tags -1 patch

Hi,

On Wed, 10 Jul 2019 13:16:27 +0200 Ansgar Burchardt 
wrote:
> For bullseye, the security suite is now named bullseye-security
> instead of buster/updates and users should adapt their sources.list
> accordingly when upgrading.
> 
> People should probably use something like
> 
>   deb http://security.debian.org/debian-security bullseye-security main
> 
> (adding /debian-security was proposed in [1]).
> 
> See [2][3][4] for some more information.
> 
> I should probably also sent a mail to d-d-a@ or so about this in the
> near future...
> 
> Ansgar
> 
>   [1] https://lists.debian.org/debian-devel/2015/12/msg00333.html
>   [2] https://bugs.debian.org/614204
>   [3] https://lists.debian.org/debian-devel/2015/12/msg00254.html
>   [4] https://lists.debian.org/debian-security/2019/06/msg00015.html

Proposed patch attached.

Paul
From 7f7113422f15aae8526521dde0d869e4af343a2f Mon Sep 17 00:00:00 2001
From: Paul Gevers 
Date: Wed, 17 Mar 2021 21:27:50 +0100
Subject: [PATCH] issues.dbk: security archive layout

Closes: #931785
---
 en/issues.dbk | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/en/issues.dbk b/en/issues.dbk
index 219aa89b..7e46bf40 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -67,6 +67,21 @@ information mentioned in .
 
   
 
+  
+
+Changed security archive layout
+
+  For bullseye, the security suite is now named
+  bullseye-security instead of
+  buster/updates and users should adapt their
+  APT source-list files accordingly when upgrading.
+
+
+  The security line in your APT configuration may look like:
+  deb https://deb.debian.org/debian-security testing-security main contrib
+
+  
+
   
 Noteworthy obsolete packages
 
-- 
2.30.2



OpenPGP_signature
Description: OpenPGP digital signature


Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2020-07-06 Thread Andrei POPESCU
On Lu, 06 iul 20, 10:55:22, Ansgar wrote:
> Andrei POPESCU writes:
> > On Mi, 10 iul 19, 13:16:27, Ansgar Burchardt wrote:
> >> People should probably use something like
> >>
> >>   deb http://security.debian.org/debian-security bullseye-security main
> >>
> >> (adding /debian-security was proposed in [1]).
> >
> > Could this be /debian instead, to be consistent with the other suites?
> 
> I think that would be a bad idea as they are different archives.
> /debian and /debian-security contain different things, giving them the
> same name would be confusing.  Also deb.d.o needs different names.

Ok.

I was hoping this was possible, considering that -updates and 
-proposed-updates are also under /debian ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2020-07-06 Thread Ansgar
Andrei POPESCU writes:
> On Mi, 10 iul 19, 13:16:27, Ansgar Burchardt wrote:
>> People should probably use something like
>>
>>   deb http://security.debian.org/debian-security bullseye-security main
>>
>> (adding /debian-security was proposed in [1]).
>
> Could this be /debian instead, to be consistent with the other suites?

I think that would be a bad idea as they are different archives.
/debian and /debian-security contain different things, giving them the
same name would be confusing.  Also deb.d.o needs different names.

Ansgar



Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2020-07-05 Thread Andrei POPESCU
On Mi, 10 iul 19, 13:16:27, Ansgar Burchardt wrote:
> Package: release-notes
> Severity: normal
> 
> For bullseye, the security suite is now named bullseye-security
> instead of buster/updates and users should adapt their sources.list
> accordingly when upgrading.
> 
> People should probably use something like
> 
>   deb http://security.debian.org/debian-security bullseye-security main
> 
> (adding /debian-security was proposed in [1]).

Could this be /debian instead, to be consistent with the other suites?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2019-07-10 Thread Ansgar Burchardt
Package: release-notes
Severity: normal

For bullseye, the security suite is now named bullseye-security
instead of buster/updates and users should adapt their sources.list
accordingly when upgrading.

People should probably use something like

  deb http://security.debian.org/debian-security bullseye-security main

(adding /debian-security was proposed in [1]).

See [2][3][4] for some more information.

I should probably also sent a mail to d-d-a@ or so about this in the
near future...

Ansgar

  [1] https://lists.debian.org/debian-devel/2015/12/msg00333.html
  [2] https://bugs.debian.org/614204
  [3] https://lists.debian.org/debian-devel/2015/12/msg00254.html
  [4] https://lists.debian.org/debian-security/2019/06/msg00015.html