debootstrap_1.0.122_source.changes ACCEPTED into unstable

2020-03-12 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:
 ff3186a084c91b776423003cba2b20343f58ed81 1919 debootstrap_1.0.122.dsc
 31ec8dddceb54dde4272d01a5dea8bd17ad195b8 77405 debootstrap_1.0.122.tar.gz
 66fa1b72d250953bf01529483bd36befc9473f20 6704 
debootstrap_1.0.122_source.buildinfo
Checksums-Sha256:
 88f92b2651d7884584a2739f2fe4b2a9cdc4e21ab2b306ccaafd96e009d542d1 1919 
debootstrap_1.0.122.dsc
 30711aa32868a1a7000da225b4abd71b32ef924c290619a443ac7ec2cf6c1f12 77405 
debootstrap_1.0.122.tar.gz
 6e3352b93fafe2f2bbc3ced4bff8f57e9fee3cd8708c45bc27266a65f075bf96 6704 
debootstrap_1.0.122_source.buildinfo
Files:
 63239e8f6874c545437be5c44b4e1f0a 1919 admin optional debootstrap_1.0.122.dsc
 30b4b8d3698f58f31c0e203b399dd9aa 77405 admin optional 
debootstrap_1.0.122.tar.gz
 cd2fa15b0de39a42e32a6f12750945f3 6704 admin optional 
debootstrap_1.0.122_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAl5rECQACgkQ/5FK8MKz
VSC0Pg//YtBs9dYRiCYDnBPGxjh47aHvjQc3kzO6cib0CSH6L+MK5VLeWhI2z8bf
IZAEANqgETY/pWTPXsjmkr8WLIPNxvK6BOTtpyuxzWQDEbejSpCJ49XEF54ebCen
uzlBh3dbUygKlmJcYqV6Gk7F3fkkdUfWRRoigPeVE3qXNiIlhR8CKhiuPkGQWOrJ
Ole7HyoWboyGd8dKKlkl98jn1CSuK1fJXXGIZUJeUFJVtLkkN6kv9PbvE9Pcmgv7
g39CYehBddxp5Uwu/YqiwjIUhuJtej53cNEgqfFDlvVIsmwRXiGCi9TIwELFaTFI
HMTva8GgJ5xqBAN74lTKx+yQK2QYhvUvpsn4xZ5cHdo5gvC4HkmIr65a5T9cUrdP
KTrkBS5Il9sXt+ylneV2wsi2+X8KgeZ9WB1JEG9m+kZda6V3yg6g82+D9bCdwm8q
0Aioi8fV5Lu9ti+GZUOpTmUOjsiB7mgcPVxb7uqMtKGNFT4tKZuGX7uiO0X1U/mb
YQvBBkKSNAGDAaDW/k1EmZ5a49oUxWtkEmaG4Ye5CbAT3bEcb6NvN9+YEw8Ub5DN
h74llfupR6eHYtWVKnyh78ZJ0VJu6+PjQVO0nmqMPlqxBG7wmW3YnB781Ay7ivNC
PUEUBvpgEmLyCNifhVTtJVp3lIH+wx013i/QdsgMiINt1DwGeDE=
=ix01
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of debootstrap_1.0.122_source.changes

2020-03-12 Thread Debian FTP Masters 
debootstrap_1.0.122_source.changes uploaded successfully to localhost
along with the files:
  debootstrap_1.0.122.dsc
  debootstrap_1.0.122.tar.gz
  debootstrap_1.0.122_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#953588: marked as done (debootstrap: fails for mirrors without translations)

2020-03-12 Thread Debian Bug Tracking System 
Your message dated Fri, 13 Mar 2020 05:04:08 +
with message-id 
and subject line Bug#953588: fixed in debootstrap 1.0.122
has caused the Debian Bug report #953588,
regarding debootstrap: fails for mirrors without translations
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 ow...@bugs.debian.org
immediately.)


-- 
953588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.121
Severity: normal

Hi,

recent debootstrap fails silently if the given mirror does not contain
translations. From debootstrap.log:

Ign:1 http://127.0.0.1/debian stable InRelease
Hit:2 http://127.0.0.1/debian stable Release
Ign:4 http://127.0.0.1/debian stable/main Translation-en
Ign:4 http://127.0.0.1/debian stable/main Translation-en
Ign:4 http://127.0.0.1/debian stable/main Translation-en
Err:4 http://127.0.0.1/debian stable/main Translation-en
  404  File not found [IP: 127.0.0.1 80]
Get:5 http://security-cdn.debian.org/debian-security stable/updates InRelease 
[65.4 kB]
Get:6 http://security-cdn.debian.org/debian-security stable/updates/main amd64 
Packages [182 kB]
Get:7 http://security-cdn.debian.org/debian-security stable/updates/main 
Translation-en [96.0 kB]
Fetched 343 kB in 1s (501 kB/s)
Reading package lists...
E: Failed to fetch 
http://127.0.0.1/debian/dists/stable/main/i18n/Translation-en  404  File not 
found [IP: 127.0.0.1 80]
E: Some index files failed to download. They have been ignored, or old ones 
used instead.


Another problem is, that this happens silently after the message "I:
Base system installed successfully." I noticed the problem because my
shell is printing the exit status of the last command but other users
might just think that debootstrap finished successfully. There should
definitely be some kind of error message when apt fails. Best including
either the reason or a pointer to debootstrap.log which is currently not
documented in the man page.

Thanks!

cheers, josch


-- System Information:
Debian Release: bullseye/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debootstrap depends on:
ii  wget  1.20.1-1.1

Versions of packages debootstrap recommends:
ii  arch-test   0.15-2
ii  debian-archive-keyring  2019.1
ii  gnupg   2.2.19-2

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client   
ii  ubuntu-keyring [ubuntu-archive-keyring]  2018.09.18.1-5

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.122
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:

Bug#951709: /boot should get a bigger share of disk in default installation

2020-03-12 Thread Cyril Brulebois 
Steve McIntyre  (2020-03-12):
> I'm torn - that's a good plan for large systems, but people on smaller
> platforms (e.g. small SD on rpi) that's a lot of space.

Don't people usually flash ready to use images on such devices, instead
of going through d-i? Meaning acepting whatever (hopefully appropriate)
choices were made by recipe authors?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#953617: marked as done (E: Release file for ... is expired)

2020-03-12 Thread Debian Bug Tracking System 
Your message dated Fri, 13 Mar 2020 05:04:08 +
with message-id 
and subject line Bug#953617: fixed in debootstrap 1.0.122
has caused the Debian Bug report #953617,
regarding E: Release file for ... is expired
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 ow...@bugs.debian.org
immediately.)


-- 
953617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.121
Severity: normal

Hi,

the autopkgtest of debuerreotype fails because debootstrap attempts to
run "apt-get update". See this log for details:

https://ci.debian.net/data/autopkgtest/testing/amd64/d/debuerreotype/4521193/log.gz

E: Release file for
http://snapshot.debian.org/archive/debian/20170101T00Z/dists/stretch/InRelease
is expired (invalid since 1158d 0h 32min 57s). Updates for this
repository will not be applied.

Thanks!

cheers, josch


-- System Information:
Debian Release: bullseye/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debootstrap depends on:
ii  wget  1.20.1-1.1

Versions of packages debootstrap recommends:
ii  arch-test   0.15-2
ii  debian-archive-keyring  2019.1
ii  gnupg   2.2.19-2

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client   
ii  ubuntu-keyring [ubuntu-archive-keyring]  2018.09.18.1-5

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.122
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:
 ff3186a084c91b776423003cba2b20343f58ed81 1919 debootstrap_1.0.122.dsc
 31ec8dddceb54dde4272d01a5dea8bd17ad195b8 77405 debootstrap_1.0.122.tar.gz
 66fa1b72d250953bf01529483bd36befc9473f20 6704 
debootstrap_1.0.122_source.buildinfo
Checksums-Sha256:
 88f92b2651d7884584a2739f2fe4b2a9cdc4e21ab2b306ccaafd96e009d542d1 1919 
debootstrap_1.0.122.dsc
 30711aa32868a1a7000da225b4abd71b32ef924c290619a443ac7ec2cf6c1f12 77405 
debootstrap_1.0.122.tar.gz
 6e3352b93fafe2f2bbc3ced4bff8f57e9fee3cd8708c45bc27266a65f075bf96 6704 
debootstrap_1.0.122_source.buildinfo
Files:
 63239e8f6874c545437be5c44b4e1f0a 1919 admin optional debootstrap_1.0.122.dsc
 30b4b8d3698f58f31c0e203b399dd9aa 77405 admin optional 
debootstrap_1.0.122.tar.gz
 cd2fa15b0de39a42e32a6f12750945f3 6704 admin optional 
debootstrap_1.0.122_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAl5rECQACgkQ/5FK8MKz
VSC0Pg//YtBs9dYRiCYDnBPGxjh47aHvjQc3kzO6cib0CSH6L+MK5VLeWhI2z8bf
IZAEANqgETY/pWTPXsjmkr8WLIPNxvK6BOTtpyuxzWQDEbejSpCJ49XEF54ebCen

Bug#953594: marked as done (debootstrap: not anymore possible to do stable debootstrap from snapshot.d.o)

2020-03-12 Thread Debian Bug Tracking System 
Your message dated Fri, 13 Mar 2020 05:04:08 +
with message-id 
and subject line Bug#953594: fixed in debootstrap 1.0.122
has caused the Debian Bug report #953594,
regarding debootstrap: not anymore possible to do stable debootstrap from 
snapshot.d.o
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 ow...@bugs.debian.org
immediately.)


-- 
953594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.121
Severity: normal

Hi,

when I debootstrap a stable release from snapshot.d.o, the security
mirror gets added to the sources.list and an upgrade is performed. There
is no option to prevent this from happening. This means that I cannot
anymore create a chroot of a specific stable snapshot with debootstrap
because debootstrap will enforce an upgrade from the current security
mirror. I think it should be possible to use debootstrap for this
purpose.

Thanks!

cheers, josch


-- System Information:
Debian Release: bullseye/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debootstrap depends on:
ii  wget  1.20.1-1.1

Versions of packages debootstrap recommends:
ii  arch-test   0.15-2
ii  debian-archive-keyring  2019.1
ii  gnupg   2.2.19-2

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client   
ii  ubuntu-keyring [ubuntu-archive-keyring]  2018.09.18.1-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.122
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:
 ff3186a084c91b776423003cba2b20343f58ed81 1919 debootstrap_1.0.122.dsc
 31ec8dddceb54dde4272d01a5dea8bd17ad195b8 77405 debootstrap_1.0.122.tar.gz
 66fa1b72d250953bf01529483bd36befc9473f20 6704 
debootstrap_1.0.122_source.buildinfo
Checksums-Sha256:
 88f92b2651d7884584a2739f2fe4b2a9cdc4e21ab2b306ccaafd96e009d542d1 1919 
debootstrap_1.0.122.dsc
 30711aa32868a1a7000da225b4abd71b32ef924c290619a443ac7ec2cf6c1f12 77405 
debootstrap_1.0.122.tar.gz
 6e3352b93fafe2f2bbc3ced4bff8f57e9fee3cd8708c45bc27266a65f075bf96 6704 
debootstrap_1.0.122_source.buildinfo
Files:
 63239e8f6874c545437be5c44b4e1f0a 1919 admin optional debootstrap_1.0.122.dsc
 30b4b8d3698f58f31c0e203b399dd9aa 77405 admin optional 
debootstrap_1.0.122.tar.gz
 cd2fa15b0de39a42e32a6f12750945f3 6704 admin optional 
debootstrap_1.0.122_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAl5rECQACgkQ/5FK8MKz
VSC0Pg//YtBs9dYRiCYDnBPGxjh47aHvjQc3kzO6cib0CSH6L+MK5VLeWhI2z8bf

Bug#953593: marked as done (debootstrap: --no-check-gpg and --keyring options not working with Debian stable chroots)

2020-03-12 Thread Debian Bug Tracking System 
Your message dated Fri, 13 Mar 2020 05:04:08 +
with message-id 
and subject line Bug#953593: fixed in debootstrap 1.0.122
has caused the Debian Bug report #953593,
regarding debootstrap: --no-check-gpg and --keyring options not working with 
Debian stable chroots
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 ow...@bugs.debian.org
immediately.)


-- 
953593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.121
Severity: normal

Hi,

the --keyring and --no-check-gpg options do not seem to be passed on to
"apt-get update". When I try to debootstrap with these options I get in
my debootstrap.log:

Ign:1 http://127.0.0.1:8000/debian stable InRelease
Hit:2 http://127.0.0.1:8000/debian stable Release
Ign:3 http://127.0.0.1:8000/debian stable Release.gpg
Get:4 http://security.debian.org/debian-security stable/updates InRelease [65.4 
kB]
Get:5 http://security.debian.org/debian-security stable/updates/main amd64 
Packages [182 kB]
Get:6 http://security.debian.org/debian-security stable/updates/main 
Translation-en [96.0 kB]
Reading package lists...
E: The repository 'http://127.0.0.1:8000/debian stable Release' is not signed.

The rest of debootstrap before worked fine because I used --no-check-gpg
but it fails at this step. Same with the --keyring option.

Thanks!

cheers, josch


-- System Information:
Debian Release: bullseye/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debootstrap depends on:
ii  wget  1.20.1-1.1

Versions of packages debootstrap recommends:
ii  arch-test   0.15-2
ii  debian-archive-keyring  2019.1
ii  gnupg   2.2.19-2

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client   
ii  ubuntu-keyring [ubuntu-archive-keyring]  2018.09.18.1-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.122
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:
 ff3186a084c91b776423003cba2b20343f58ed81 1919 debootstrap_1.0.122.dsc
 31ec8dddceb54dde4272d01a5dea8bd17ad195b8 77405 debootstrap_1.0.122.tar.gz
 66fa1b72d250953bf01529483bd36befc9473f20 6704 
debootstrap_1.0.122_source.buildinfo
Checksums-Sha256:
 88f92b2651d7884584a2739f2fe4b2a9cdc4e21ab2b306ccaafd96e009d542d1 1919 
debootstrap_1.0.122.dsc
 30711aa32868a1a7000da225b4abd71b32ef924c290619a443ac7ec2cf6c1f12 77405 
debootstrap_1.0.122.tar.gz
 6e3352b93fafe2f2bbc3ced4bff8f57e9fee3cd8708c45bc27266a65f075bf96 6704 
debootstrap_1.0.122_source.buildinfo
Files:
 63239e8f6874c545437be5c44b4e1f0a 1919 admin

Bug#953759: marked as done (debootstrap: mandatory security support breaks too many things)

2020-03-12 Thread Debian Bug Tracking System 
Your message dated Fri, 13 Mar 2020 05:04:08 +
with message-id 
and subject line Bug#953759: fixed in debootstrap 1.0.122
has caused the Debian Bug report #953759,
regarding debootstrap: mandatory security support breaks too many things
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 ow...@bugs.debian.org
immediately.)


-- 
953759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.120
Severity: serious
Justification: RoM

Hi,

It seems my comments in [1] were ignored, so filing an RC bug to make
sure this is tracked at least by the BTS and britney.

 1. https://lists.debian.org/debian-boot/2020/03/msg00103.html

The latest batch of bug reports filed by Johannes 'josch' Schauer seems
to confirm my initial assessment: this will break (too) many use cases
(#953404, #953588, #953593, #953594, #953617).

Right now, my current plan would be:
 - creating a branch called “mandatory-security-support” (or something
   similar) at 1.0.121, so that people wanting to turn that into something
   suitable can try to do so, but I'm still unconvinced even having that as
   an option (disabled by default) would be appropriate, for all the
   problems that can come up when trying to drive apt.
 - remove support in master entirely, for the time being.

Rationale for plain removal is: we need to be able to upload debootstrap
with bugfixes, without having to suffer from all the side effects coming
from that recent change.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.122
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Mar 2020 05:43:24 +0100
Source: debootstrap
Architecture: source
Version: 1.0.122
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 953588 953593 953594 953617 953759
Changes:
 debootstrap (1.0.122) unstable; urgency=medium
 .
   * Revert the addition of (mandatory) security support as debootstrap's
 goal is to provide with a basic Debian system that many provisioning
 systems are built upon. Changing behaviour now seems to be doing a
 disservice to all those tools that would need adapting. In addition to
 not seeming to be a good idea, that triggers regressions for a number
 of use cases (Closes: #953759, #953588, #953593, #953594, #953617).
Checksums-Sha1:
 ff3186a084c91b776423003cba2b20343f58ed81 1919 debootstrap_1.0.122.dsc
 31ec8dddceb54dde4272d01a5dea8bd17ad195b8 77405 debootstrap_1.0.122.tar.gz
 66fa1b72d250953bf01529483bd36befc9473f20 6704 
debootstrap_1.0.122_source.buildinfo
Checksums-Sha256:
 88f92b2651d7884584a2739f2fe4b2a9cdc4e21ab2b306ccaafd96e009d542d1 1919 
debootstrap_1.0.122.dsc
 30711aa32868a1a7000da225b4abd71b32ef924c290619a443ac7ec2cf6c1f12 77405 
debootstrap_1.0.122.tar.gz
 6e3352b93fafe2f2bbc3ced4bff8f57e9fee3cd8708c45bc27266a65f075bf96 6704 
debootstrap_1.0.122_source.buildinfo
Files:
 63239e8f6874c545437be5c44b4e1f0a 1919 admin optional debootstrap_1.0.122.dsc
 30b4b8d3698f58f31c0e203b399dd9aa 77405 admin optional 
debootstrap_1.0.122.tar.gz
 cd2fa15b0de39a42e32a6f12750945f3 6704 admin optional 
debootstrap_1.0.122_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAl5rECQACgkQ/5FK8MKz
VSC0Pg//YtBs9dYRiCYDnBPGxjh47aHvjQc3kzO6cib0CSH6L+MK5VLeWhI2z8bf
IZAEANqgETY/pWTPXsjmkr8WLIPNxvK6BOTtpyuxzWQDEbejSpCJ49XEF54ebCen
uzlBh3dbUygKlmJcYqV6Gk7F3fkkdUfWRRoigPeVE3qXNiIlhR8CKhiuPkGQWOrJ
Ole7HyoWboyGd8dKKlkl98jn1CSuK1fJXXGIZUJeUFJVtLkkN6kv9PbvE9Pcmgv7
g39CYehBddxp5Uwu/YqiwjIUhuJtej53cNEgqfFDlvVIsmwRXiGCi9TIwELFaTFI

Processed: Bug#953759 marked as pending in debootstrap

2020-03-12 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #953759 [debootstrap] debootstrap: mandatory security support breaks too 
many things
Added tag(s) pending.

-- 
953759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#953588 marked as pending in debootstrap

2020-03-12 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #953588 [debootstrap] debootstrap: fails for mirrors without translations
Added tag(s) pending.

-- 
953588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#953617 marked as pending in debootstrap

2020-03-12 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #953617 [debootstrap] E: Release file for ... is expired
Added tag(s) pending.

-- 
953617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#953759: debootstrap: mandatory security support breaks too many things

2020-03-12 Thread Steve McIntyre 
On Fri, Mar 13, 2020 at 02:26:04AM +0100, Cyril Brulebois wrote:
>Package: debootstrap
>Version: 1.0.120
>Severity: serious
>Justification: RoM
>
>Hi,
>
>It seems my comments in [1] were ignored, so filing an RC bug to make
>sure this is tracked at least by the BTS and britney.
>
> 1. https://lists.debian.org/debian-boot/2020/03/msg00103.html
>
>The latest batch of bug reports filed by Johannes 'josch' Schauer seems
>to confirm my initial assessment: this will break (too) many use cases
>(#953404, #953588, #953593, #953594, #953617).
>
>Right now, my current plan would be:
> - creating a branch called “mandatory-security-support” (or something
>   similar) at 1.0.121, so that people wanting to turn that into something
>   suitable can try to do so, but I'm still unconvinced even having that as
>   an option (disabled by default) would be appropriate, for all the
>   problems that can come up when trying to drive apt.
> - remove support in master entirely, for the time being.
>
>Rationale for plain removal is: we need to be able to upload debootstrap
>with bugfixes, without having to suffer from all the side effects coming
>from that recent change.

Sounds sensible enough to me...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.

Bug#953759: debootstrap: mandatory security support breaks too many things

2020-03-12 Thread Cyril Brulebois 
Package: debootstrap
Version: 1.0.120
Severity: serious
Justification: RoM

Hi,

It seems my comments in [1] were ignored, so filing an RC bug to make
sure this is tracked at least by the BTS and britney.

 1. https://lists.debian.org/debian-boot/2020/03/msg00103.html

The latest batch of bug reports filed by Johannes 'josch' Schauer seems
to confirm my initial assessment: this will break (too) many use cases
(#953404, #953588, #953593, #953594, #953617).

Right now, my current plan would be:
 - creating a branch called “mandatory-security-support” (or something
   similar) at 1.0.121, so that people wanting to turn that into something
   suitable can try to do so, but I'm still unconvinced even having that as
   an option (disabled by default) would be appropriate, for all the
   problems that can come up when trying to drive apt.
 - remove support in master entirely, for the time being.

Rationale for plain removal is: we need to be able to upload debootstrap
with bugfixes, without having to suffer from all the side effects coming
from that recent change.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Re: boot-time accessibility issues

2020-03-12 Thread Jude DaShiell 
I would try something with timing and detection of a sound card in
addition to the monitor.  Ubuntu systems use ks.cfg files Debian uses
preseed files.  I saved from several years ago a ks.cfg file in braille
that was offered by a website in England and believe it or not actually
got ubuntu in an earlier version talking after an install from that
website file.  I don't know if a preseed file is more desireable than a
kickstart file and I think I can find the braille notes in my pile of
braille papers here.

On Thu, 12 Mar 2020, Rich Morin wrote:

> Date: Thu, 12 Mar 2020 12:28:49
> From: Rich Morin 
> To: debian-boot@lists.debian.org
> Cc: debian-accessibil...@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Thu, 12 Mar 2020 16:29:21 + (UTC)
> Resent-From: debian-accessibil...@lists.debian.org
>
> The idea of detecting the presence (or absence) of a blind-related device 
> seems worth pursuing, even if there are some issues to be resolved.
>
> For example, following Jude's notion of checking for a monitor, maybe Avahi 
> and SSH could be enabled whenever a monitor isn't found.  For that matter, 
> enabling Orca (or whatever) by default when no monitor is present wouldn't be 
> that big a problem for a sighted user.  Devin's notion of checking for a 
> braille display could be expanded to include a range of USB devices such as 
> braille printers and such.
>
> I've been wondering about the notion of checking for a USB flash drive that 
> contains some sort of magic files.  The files probably can't contain 
> executable binary files (due to hardware incompatibility issues), but they 
> could certainly contain textual configuration data.  Can anyone suggest ideas 
> for file content, format, naming, etc?
>
> -r
>
>

--

Re: boot-time accessibility issues

2020-03-12 Thread Rich Morin 
The idea of detecting the presence (or absence) of a blind-related device seems 
worth pursuing, even if there are some issues to be resolved.

For example, following Jude's notion of checking for a monitor, maybe Avahi and 
SSH could be enabled whenever a monitor isn't found.  For that matter, enabling 
Orca (or whatever) by default when no monitor is present wouldn't be that big a 
problem for a sighted user.  Devin's notion of checking for a braille display 
could be expanded to include a range of USB devices such as braille printers 
and such.

I've been wondering about the notion of checking for a USB flash drive that 
contains some sort of magic files.  The files probably can't contain executable 
binary files (due to hardware incompatibility issues), but they could certainly 
contain textual configuration data.  Can anyone suggest ideas for file content, 
format, naming, etc?

-r

Bug#951709: /boot should get a bigger share of disk in default installation

2020-03-12 Thread Steve McIntyre 
On Tue, Mar 10, 2020 at 11:21:10PM +0100, Julien Cristau wrote:
>On Tue, Mar 10, 2020 at 09:50:07PM +0100, Holger Wansing wrote:
>> Hi,
>> 
>> Ben Hutchings  wrote:
>> > On Thu, 2020-02-20 at 18:50 +0530, Pirate Praveen wrote:
>> > > Package: debian-installer
>> > > Version: 20190702+deb10u3
>> > > Severity: important
>> > > 
>> > > With initrd around 60+ MBs, 236 MB /boot in a 300 GB hard disk can hold 
>> > > only 2 versions of the kernels at the same time. When installing a 3rd 
>> > > kernel /boot gets filled up. I think it should be able to store at 
>> > > least 3 kernels and ideally 4 or even more.
>> > >
>> > > The paritions were created automatically with just /home in a separate 
>> > > partition with lvm by debian buster installer.
>> > 
>> > I agree; the default size of /boot is now too small.  I think we should
>> > normally allocate at least 500 MB to it.
>> 
>> This has just been addressed; see
>> https://salsa.debian.org/installer-team/partman-auto/-/commit/cf6b2d152b08b6c78da6a6f7ca26a99bdadfdfce
>> 
>Not quite.  If Ben says we need at least 500M, then we'll have to
>adjust further, as that commit uses 512M as a maximum.  For comparison
>Ubuntu's partman-auto sets the min at 512M and max at 768M.  Do people
>feel that's where we should go?

I'm torn - that's a good plan for large systems, but people on smaller
platforms (e.g. small SD on rpi) that's a lot of space.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"War does not determine who is right - only who is left."
   -- Bertrand Russell

Re: boot-time accessibility issues

2020-03-12 Thread Devin Prater 
At least if a Braille Display is connected, accessibility resources should be 
enabled. Also, I don’t think desktops and such should have an accessibility 
toggle. If it doesn’t bother the visuals, accessibility setting for the desktop 
GUI itself, not Orca and such, should always be set to on. That way, if a blind 
person does turn on Orca, the desktop will be accessible. Also, if Fenrir 
becomes a standard, built into distributions, perhaps have a hotkey to turn it 
on at this log in, and have a way to set that as default. Also, desktops should 
come with a key binding for Orca, and display that there is one, and what it 
is, prominently on their help pages.

> On Mar 11, 2020, at 10:35 PM, Jude DaShiell  wrote:
> 
> full circle, solutions zero.
> 
> On Thu, 5 Mar 2020, Rich Morin wrote:
> 
>> Date: Thu, 5 Mar 2020 23:54:14
>> From: Rich Morin 
>> To: debian-boot@lists.debian.org
>> Cc: debian-accessibil...@lists.debian.org
>> Subject: Re: boot-time accessibility issues
>> Resent-Date: Thu, 12 Mar 2020 02:07:16 + (UTC)
>> Resent-From: debian-accessibil...@lists.debian.org
>> 
>> Jude DaShiell said:
>> 
>>> If dummy was used for monitor type, the screen reader could come up talking 
>>> without any monitor attached. ...
>> 
>> I can think of a couple of issues with this approach.  First, there are 
>> various reasons for leaving a monitor off a system.  For example, if a RasPi 
>> is being used as a server, running it "headless" might be a normal strategy, 
>> having nothing to do with blindness.
>> 
>> Contrariwise, there are various reasons a blind user might want to keep an 
>> active  monitor.  They might have a sighted associate with whom they 
>> occasionally collaborate. Alternatively, they might want to run a touch 
>> screen (e.g., to type on).
>> 
>> The fundamental problem is that keying off the presence of a monitor 
>> complects two separate and otherwise independent phenomena.  So, it's just 
>> asking for conflicts.
>> 
>> -r
>> 
>> 
> 
> -- 
>