Bug#923764: console-setup-linux: boot script needs to label /run/console-setup on SE Linux systems

[Russell Coker]

Package: console-setup-linux
Version: 1.190
Severity: normal

The following patch makes it correctly label /run/console-setup.  If SE Linux
isn't enabled then restorecon does nothing, if restorecon isn't installed then
nothing happens.

--- /lib/console-setup/console-setup.sh.orig2019-03-05 16:15:58.324868518 
+1100
+++ /lib/console-setup/console-setup.sh 2019-03-05 16:16:07.916893505 +1100
@@ -10,6 +10,7 @@
 # Skip only the first time (i.e. when the system boots)
 [ ! -f /run/console-setup/boot_completed ] || do_configure=yes
 mkdir -p /run/console-setup
+   [ -x /sbin/restorecon ] && /sbin/restorecon /run/console-setup
 > /run/console-setup/boot_completed
 
 [ /etc/console-setup/cached_setup_terminal.sh \

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.56+nmu1
ii  kbd 2.0.4-4
ii  keyboard-configuration  1.190

console-setup-linux recommends no packages.

Versions of packages console-setup-linux suggests:
ii  console-setup  1.190

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.70
ii  liblocale-gettext-perl  1.07-3+b4

Versions of packages console-setup depends on:
ii  debconf 1.5.70
ii  keyboard-configuration  1.190
ii  xkb-data2.23.1-1

Versions of packages console-setup suggests:
ii  locales   2.28-5
ii  lsb-base  10.2018112800

Versions of packages console-setup-linux is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.4-4
ii  systemd   240-4

-- debconf information excluded

-- debsums errors found:
debsums: changed file /lib/console-setup/console-setup.sh (from 
console-setup-linux package)

Bug#923681: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

debian-installer-9-netboot-armel | 20170615+deb9u5.b2 | all
debian-installer-9-netboot-armhf | 20170615+deb9u5.b2 | all
debian-installer-9-netboot-i386 | 20170615+deb9u5.b2 | all
debian-installer-9-netboot-mips | 20170615+deb9u5.b2 | all
debian-installer-9-netboot-mips64el | 20170615+deb9u5.b2 | all
debian-installer-9-netboot-mipsel | 20170615+deb9u5.b2 | all
debian-installer-9-netboot-ppc64el | 20170615+deb9u5.b2 | all

--- Reason ---
RoQA; cruft arch:all packages, replaced by versions s/9/10/
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/923681

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

netcfg_1.159_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Mar 2019 23:55:30 +0100
Source: netcfg
Architecture: source
Version: 1.159
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 netcfg (1.159) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Vietnamese (vi.po) by Trần Ngọc Quân
Checksums-Sha1:
 58d316653ee0c22c18a536fa257643d7095ca31f 1943 netcfg_1.159.dsc
 0979c1ef538eff531e107b59c0c49493e539d6f1 394188 netcfg_1.159.tar.xz
 fc40fb9be38763c82c84bfa9f8a41b02909abd51 5761 netcfg_1.159_amd64.buildinfo
Checksums-Sha256:
 c506008ef285b62f0bba56e8c6f81ae0a0878c3e03f8e997ed835743055c6985 1943 
netcfg_1.159.dsc
 47efb0897f4dae00240d616a47abbef67848a2b2be2636906580925e5c578d61 394188 
netcfg_1.159.tar.xz
 11ac592aefa35380d0850aca52faeb7a807aab19cced75574ffec0ce719c7413 5761 
netcfg_1.159_amd64.buildinfo
Files:
 9f6b6c93f75b2543b45fe32ad1def530 1943 debian-installer optional 
netcfg_1.159.dsc
 e5127123e9d0d1a42cd8200e0485cb6f 394188 debian-installer optional 
netcfg_1.159.tar.xz
 9e91e7aa99476923e284e9e81c2e6c29 5761 debian-installer optional 
netcfg_1.159_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlx9rjsVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2xCwP/2RM0D2SAxQqu/KZUAyTWwDdV3M2
2wRBV4qtbUwwYx9m6Rd6w5xsUCh4jV5WpMSJeQmedst5c0k2hppCbhp9MmCkoisU
Hb9KiQEKsgV86hCrOLWgxwSpjuPega4MYsVxHlVqwjp00k7mjoIjNSFKI1Wdz+4D
LnIZ8X0KB3tOx5uZM5+LS7fIoY2XG9QLmP3CjPCK4wCt4ifXnoj9Bxt9dHfUi7Eq
ZgeKt7W9DVT9h4SnKPHt3XC7jfpq+7EXMY8SS/c5Y+73GAwPFsFSsYKayCkZ+1bQ
wqZn7SzMaAAmhs3lHtkTI4OxVQ74iWwpKQYPuZIICy/4N5p2xv0T/k/yuQkOCYRn
cL1fW9HRKDt1lGjQyicBalcCe+mglHJhsNoAId451SCagSGjhPoFxLcgf61Atch8
GuOBiJsxsMDsoolltzcO194eCTKDKJVMNntoE6iOt8e4AWm+YrAH1BGsN0u1dRFi
6icWifbqFD/Ee2R+LxoNBNuxyJQfuxR8FYGXd+ZRuIasaFa0BQvETDPFlCHpHhAr
Mlp10h0vW0dtPYkgvgc3Pq+HDoMJut18gqsctJhdwzcFx2+mplIH+6L4cE05zquz
miGQXHAsp+F3E9pqz1TVG96WD6XH8izu1Nz1gmxoLuAmRpI/E5/iXI1cVZiJ/EnJ
GtTjUc/K8KgMeyjN
=foYT
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of netcfg_1.159_source.changes

[Debian FTP Masters]

netcfg_1.159_source.changes uploaded successfully to localhost
along with the files:
  netcfg_1.159.dsc
  netcfg_1.159.tar.xz
  netcfg_1.159_amd64.buildinfo

Greetings,

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

partman-base_206_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Mar 2019 22:49:35 +
Source: partman-base
Architecture: source
Version: 206
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Colin Watson 
Changes:
 partman-base (206) unstable; urgency=medium
 .
   [ Iain Lane ]
   * Replace use of '%as' (and '%a[...]') scanf directives with '%ms'
 (LP: #1818285).
Checksums-Sha1:
 500f2d71c08905d7c9cabcc03fbf5bff04d9a063 1867 partman-base_206.dsc
 e7f72783b5293339f49335feb4d6ef57f63c2358 174540 partman-base_206.tar.xz
 b2c0d8e4c8836507a3b415154dd84f1db8935445 6774 partman-base_206_source.buildinfo
Checksums-Sha256:
 1c6d9459ece51f3a087648bd44d68e0c8699e5ea17ffaf3b99ba109c0e6f163d 1867 
partman-base_206.dsc
 873e218f153677a1945e52cb7288f470e64617fba5b21320f560c75ae67779c6 174540 
partman-base_206.tar.xz
 1c19f895565ed113f0d9fc249d26149bd86d7bc04b84d8fc55f505967fc5ac42 6774 
partman-base_206_source.buildinfo
Files:
 a9147c8f6245b1bd9b12de4c6f82f1c5 1867 debian-installer standard 
partman-base_206.dsc
 858c44e0ff899b48661794ebbba041e6 174540 debian-installer standard 
partman-base_206.tar.xz
 99f1153258e4bf45c8b869a054ef743d 6774 debian-installer standard 
partman-base_206_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAlx9q8oACgkQOTWH2X2G
UAtnRg//ZQp8UjPSmd+aocu38TzuDIeMurY+gJVbzOBC5h2cuwneSv54o/oMsC/F
JA6SHcFTfVrKYhitsDt1kEs5hf2vToWcegQxz9X5reiVPmT08yoOTe0zPM6QUgP3
lx8dEttlU/nOrzZZt5imsteiDFv7+5JACCB/QAPkcebG6r7n2i6leBHUiFRtNjJ5
Tw52YYhNn+6X9LWdoVChFh3hX0Q0QudFp7qdXMuABLhecN6566VeDvZB3eba2z4M
j6qRUq8ZLDkEc7lIKhuEmWm7NfHHhi4+WSqmV3eKF7caYPNW5VCWodhzbcl7z1fd
NucnWxoZZCIBXf3rNiLI2aUkHk7JSL4V/1pgm4Ho4gnPx7IEy8VIDKodU95ASPZD
Tcr1n+gZLn0MFkyi5i1H0UghMQuwKi6JWgRL1iL7tGRSwpL/CStxJLm6g5r4BjQP
9zSS3wV3gMXSU3DANrXOgfSQlUSdsVxIN+/+YuF6zBwPE1e8wddqDeO4kSlsk4Q2
d7fro4yn/01QUNlFDppCxXNGPZi+b+Mlep+yR/Y3ONq6ZBhyuDmCimI8bDaJB0lv
EFjeUVWOVIQtl8tz9vsW1SgpEl9/D/MoROMNe1U0tLgSHwvnLSezR5kWxDvWeqlc
vyOgkFa9UgXrSp7zf/DPPrqg+NDXP49BIo9Q9O+l8054vf+IcHk=
=SyR7
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of partman-base_206_source.changes

[Debian FTP Masters]

partman-base_206_source.changes uploaded successfully to localhost
along with the files:
  partman-base_206.dsc
  partman-base_206.tar.xz
  partman-base_206_source.buildinfo

Greetings,

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

cdrom-checker_1.42_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Mar 2019 23:20:01 +0100
Source: cdrom-checker
Architecture: source
Version: 1.42
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 cdrom-checker (1.42) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Khmer (km.po) by
   * Vietnamese (vi.po) by Trần Ngọc Quân
Checksums-Sha1:
 8f4862e0e4769cc7295940327fe1282fed815540 1735 cdrom-checker_1.42.dsc
 c44934c275813ba39394ecb8bb9e1eacb061caf2 69700 cdrom-checker_1.42.tar.xz
 217b63b67e51d3e9fb1c9f9c363594dd87ef8109 5420 
cdrom-checker_1.42_amd64.buildinfo
Checksums-Sha256:
 722a2b3c3de786d0d1d095e201287c3bcae3e7be06cb989dfa1cf8430b553946 1735 
cdrom-checker_1.42.dsc
 52042544180be2057a219e3ec708a3db1863413c29605f35a7d1e657da480653 69700 
cdrom-checker_1.42.tar.xz
 2fe4894bc5513245671ac079463c42a78c7b867ec3ecb6e6cc634691ad430f18 5420 
cdrom-checker_1.42_amd64.buildinfo
Files:
 c74f408fa26bf7a49797e3840a7113f1 1735 debian-installer optional 
cdrom-checker_1.42.dsc
 ccdc97c70278da0505ab8591cd084dc7 69700 debian-installer optional 
cdrom-checker_1.42.tar.xz
 79fbcf32ce08b830c3f284e5ae3c1a2b 5420 debian-installer optional 
cdrom-checker_1.42_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlx9pqkVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB20ugQAIoQkMhFaMzLPdcM7mqVZxz8WK9r
T1nxx9jf3vryTpRv5if3dmImlkoFdtyXqYtSlBhTjHAvE8zwyWHvbZ9NtfFS/gI9
nNQSEVe3micfvyFswLrDnSVXScZNQqeVzZ+YXI6OvcDecjrwrCEsUt3bwvIp/MUR
VkT9nOXyHeWCMWLx1mttOU8ulxnPlMA9+01CiODX/1lBI6OTSUVoiXtCTe4ZHpNx
YdKieJC4N9ncf6U6qLWm068/07QFWokXZOV8M5AuhZ2wAR0LTKgqrKcuUWL3m02O
JQcQDFw4qfhLonve4njXtP3vpfPhx4Ijf0UeDinCJfVOrd0CUomwCABIRbioqWWq
TTwy6bTAGszhWWDuQbjjXrDOYDMhlHM+KQlO10hjpl/QMTLZ4oKHYi4pZ8+Yb2qj
0llw37vPIPf+3jiZLNLoaARG3BzICzLEQKwUhZwxkh6/atOy72/nLOfWYEbLtoIQ
UV6ApDPu2KnsphBOpl/KJEbfBcoU1ngSWwOLm36ynMiQnQ9HWkSm9PJxpHnQCeeJ
pT+m7Xe8hlOoaPe5L+tAlZ6gzin0B4FX41r45hR3RjHBBPcSqTki8GLZHRxapX9p
ohi6UNWFnIkWRfVN8WjjXzP2RQFY8qyp8HrRCUoMOB+H3ViJfyGYYyGP+PgVq/WU
jWCm4MeNRN3KabRa
=frQn
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of cdrom-checker_1.42_source.changes

[Debian FTP Masters]

cdrom-checker_1.42_source.changes uploaded successfully to localhost
along with the files:
  cdrom-checker_1.42.dsc
  cdrom-checker_1.42.tar.xz
  cdrom-checker_1.42_amd64.buildinfo

Greetings,

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

apt-setup_0.148_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Mar 2019 23:09:07 +0100
Source: apt-setup
Architecture: source
Version: 1:0.148
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 apt-setup (1:0.148) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Punjabi (pa.po) by Aman ALam
   * Vietnamese (vi.po) by Trần Ngọc Quân
Checksums-Sha1:
 034f3cb772978e44297c7574fe98bfcc480de9e2 1863 apt-setup_0.148.dsc
 6e333f0c73a2518767fb5f49b3711dd601e9c3f9 253172 apt-setup_0.148.tar.xz
 c0e1ff4e561f85577ae1bf14684b03c8af210256 5813 apt-setup_0.148_amd64.buildinfo
Checksums-Sha256:
 e2a144a8ce4919fd31a2bfd713ea00a58b927cfcc13ba3463e6ad956d41e2f44 1863 
apt-setup_0.148.dsc
 fe1c24c7ca91d1a3c75e24d51a2c9a6ba7c729e1a4a2bfcf6633dd0f2afe0e7d 253172 
apt-setup_0.148.tar.xz
 0091b5f94e66e36cdb811de7e12871168318c1fb4c7474a67e25fae4e35a0612 5813 
apt-setup_0.148_amd64.buildinfo
Files:
 e8fbaed302add009693889cceeef00a4 1863 debian-installer optional 
apt-setup_0.148.dsc
 d2126d9039d9447762bb5f1b5d463c74 253172 debian-installer optional 
apt-setup_0.148.tar.xz
 817f3eee9a341741142c156f74e34434 5813 debian-installer optional 
apt-setup_0.148_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlx9o6wVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2G8gP/RnsOYDE5TskEKzbfEV3lJpwuYBa
b++0Mt+8JoD+p78SdpMxBneZBbWLUUVeQmv1KC3F64I/Sit95ldk90WLvzobyQ8o
jHJ0gAVy85UFnD2P3pKYMB6z4G9qkSY3CpOBBiTJ9YXmt477yzHTZCEKJ31hOMTl
cu2+sxeVPe+KAn5rTsaYYKji5bl3bmLslb/qgDn+UNpaV2Kdhcw/xqXFRXea90Hf
hVlZhsZOVGwshapBz2tot0apK0DrjEwiDp2QItkPH/lNLzE3yWQ70L/h66oHFk3a
K/hXMXEIU90BXNBXZ/ePgq93RAm9T9Sq5uDPXFuE7Rk3tmML6draF6/JyQCkT4Wp
1Bg4U6h4zyavkSduCVABEIMoxUYn/3HvK/Y5dVq8AOW/KgiFpPdN6UY383XSeisF
rBdy8v6eBKrPXWB+C1li+Ofn5inKKlNcTW5IW3YX39KBKlZKMFfzaV6RjjG+f425
Z1ancZWGZqqI/i6E5JivhxyUb2E/5WLmCL/J7bzvtaigv8uoQPxy8hZ6C/kUF85k
J4FeQw1EdYCPDzffG8bfjmAU56ZOsZIKEZp3SgmcP+LW1nsahIw2jxq06E3NqUhF
/Uq88qT1m7b04wvi7KaHnrROw8X+Otnmmlz5pe5tn4OEv/KJbqujnC2RaTsv9sWC
ZWPT6eI5XnTUS73b
=2RAt
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of apt-setup_0.148_source.changes

[Debian FTP Masters]

apt-setup_0.148_source.changes uploaded successfully to localhost
along with the files:
  apt-setup_0.148.dsc
  apt-setup_0.148.tar.xz
  apt-setup_0.148_amd64.buildinfo

Greetings,

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

Re: Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

[Margarita Manterola]

Hi,

> - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> The winners are:
>Option M `middle`
>Option H `hard`
> 
> - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> Dear Marga, as Chair, could you please make use of your casting vote to break 
> this tie?

I'm using my casting vote to vote in favor of M `middle` (i.e. consider
that the desirable situation at the time of bullseye is that both directory
schemes are allowed, all packages can be built on either).

My rationale for taking this decision is as follows:

Right now we are not ready to migrate to building on merged-usr systems in
Debian, there are still 29 known packages that are broken and need to be
fixed.  My expectation is that those packages will be fixed in the not so
distant future (i.e.  before bullseye) and that after that, the buildd
profile in debootstrap will default to having a merged /usr, so that new
buildd chroots will use that setup.

However, we have no control over how fast individual developers and
derivative distributions will migrate to the new format. It's possible that
more time will be required until everyone is ready to migrate.

Additionally, as of our current understanding of the issue, there are no
known problems for building on a non-merged system. Supporting this
setup does not imply additional work from the point of view of our
maintainers (for now).

In the future, it would be a bug if a problem is discovered with building a
package on a non-merged /usr system. I understand that this would mean
additional work to the maintainers of such a package, but at least as of
today this is a non-issue. Eventually, when fixing such bugs becomes a
significant burden for our maintainers, it can be decided that the setup is
no-longer supported, but my personal recommendation would be to wait at
least until bullseye+1. That's why I'm voting "Middle" for bullseye.

-- 
Thanks,
Marga


signature.asc
Description: PGP signature

s390-netdevice_0.0.67_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Mapping sid to unstable.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Mar 2019 21:37:28 +0100
Source: s390-netdevice
Architecture: source
Version: 0.0.67
Distribution: sid
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 s390-netdevice (0.0.67) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Khmer (km.po) by
   * Vietnamese (vi.po) by Trần Ngọc Quân
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 98b44dc1a84690dae644d3d72e884e25321ed3c8 1835 s390-netdevice_0.0.67.dsc
 fde5e40765f8a90dc0f2c0cf229e177dbc9be4d8 96060 s390-netdevice_0.0.67.tar.xz
 d89a7e85a32924427ed4250bfc0954f2d45ff9e3 5415 
s390-netdevice_0.0.67_s390x.buildinfo
Checksums-Sha256:
 7a45d2a75411b1ccc52c93c2926ae861b5d8511487b824ca48e9f888b7f7a457 1835 
s390-netdevice_0.0.67.dsc
 d929f5d42b626711ad0ea8999a38c0cdaed6de7bda0f1a22e189c60ca53bca92 96060 
s390-netdevice_0.0.67.tar.xz
 1399de1de35e4807caa95c92325383eb82a1f73aa0b8b199976f15f5f2af74b4 5415 
s390-netdevice_0.0.67_s390x.buildinfo
Files:
 75e0ba9504c4e2dc5b9c9c67a3843b72 1835 debian-installer standard 
s390-netdevice_0.0.67.dsc
 b4c56e666980be62940efc54da55b0bf 96060 debian-installer standard 
s390-netdevice_0.0.67.tar.xz
 16d110252844db89595c7bdef304fd2c 5415 debian-installer standard 
s390-netdevice_0.0.67_s390x.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlx9jvQVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB221oP/3EHDOIcXpvajnJmNU5pJJBHN9ei
/GcUSS4y+6yalsqGY9t4OZpDqIUpEnQwzyrlJAHTRsEN6pAQvr94KPhWZ5em98UM
Sw740S9O/5+miUKnHIW761+9lzyUNZzheLA5TL56YyYuZsw8+ELEU10IP6af8+lt
fPIwKLR2pZLvK3Vfqo1iSyz+jGwENyBVx3EFaudu7+RClidbOSB6IMQWgAchGKbj
vjC8Zo21AQhLBENyPWioCnQmMRwo4Q4Co7KMIs+ZXDYBY8OpkBu7NiX0c8QhMLba
jesJgM+jLsXLHGeY69fdXr4sFGZmr+tQQargsYmD/5Y8YYGNAbWeogZAhtidrSnb
ldAPzkHlPyvkZC/Ee9xu/3jKAOqxr0NRTiYM4Oa+2UipzQvnrdNT72wCAzhvwBy1
xQtpUOGRJvHAmHgNpl02XmtR0/cp8B5JYdW4TRrXjKWJzxnrHoOySHx8YA2HRquV
fMc1TMm9CGZM1Nl0DK5kvQO8CLf3pV58o1OK+Ri9pIldr7wuGc05ynSB7DHMHtcP
qTJ4HuIotQerdZ/Dz5eoTANAsZLPMk5zT5YHUAGFkN6dkeerc/Qno8IzGzKCVW4U
YWjIcXbBPoXAWsGYUyIZZOZrgEemyFEYNiYviz4UzRUTs+tdSPWLRLAnlK9WzaXQ
dV6XWICxLd5qKB4I
=M9b9
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of s390-netdevice_0.0.67_source.changes

[Debian FTP Masters]

s390-netdevice_0.0.67_source.changes uploaded successfully to localhost
along with the files:
  s390-netdevice_0.0.67.dsc
  s390-netdevice_0.0.67.tar.xz
  s390-netdevice_0.0.67_s390x.buildinfo

Greetings,

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

Bug#716710: marked as done (debian-installer: keymap is not an alias of keyboard-configuration/xkb-keymap in a preseed file)

[Debian Bug Tracking System]

Your message dated Mon, 4 Mar 2019 21:07:15 +0100
with message-id <77764023-9ec6-62cc-b955-958ec83fe...@debian.org>
and subject line Re: debian-installer: keymap is not an alias of 
keyboard-configuration/xkb-keymap in a preseed file
has caused the Debian Bug report #716710,
regarding debian-installer: keymap is not an alias of 
keyboard-configuration/xkb-keymap in a preseed file
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.)


-- 
716710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20130613
Severity: minor

Hi,

Quoting http://www.debian.org/releases/wheezy/amd64/apbs04.html.en:

# keymap is an alias for keyboard-configuration/xkb-keymap
d-i keymap select us

But this form does not actually work (for me at least): one has to
use the long form:

d-i keyboard-configuration/xkb-keymap select us

Please fix either the documentation or the implementation; the alias
already works on the command line, which is very useful, but I
personally do not mind using the long form in the preseed file.
-- 
Thanks,
Feri.
--- End Message ---
--- Begin Message ---
Control: reassign -1 debian-installer

Hi Ferenc,

On Thu, 11 Jul 2013 17:27:40 +0200 =?utf-8?q?Ferenc_W=C3=A1gner?=
 wrote:
> Quoting http://www.debian.org/releases/wheezy/amd64/apbs04.html.en:
> 
> # keymap is an alias for keyboard-configuration/xkb-keymap
> d-i keymap select us
> 
> But this form does not actually work (for me at least): one has to
> use the long form:
> 
> d-i keyboard-configuration/xkb-keymap select us
> 
> Please fix either the documentation or the implementation; the alias
> already works on the command line, which is very useful, but I
> personally do not mind using the long form in the preseed file.

Thanks for reporting this issue. This was already fixed in the stretch
release notes: https://www.debian.org/releases/stretch/amd64/apbs04.html.en

Paul



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Re: Bug#906016: transition: gjs built with mozjs60

[Cyril Brulebois]

Hi,

Simon McVittie  (2019-03-02):
> On Tue, 05 Feb 2019 at 10:16:56 +, Simon McVittie wrote:
> > > > * Require task-gnome-desktop to be installable on s390x, but modify
> > > >   meta-gnome3 so that on s390x, gnome-core installs something that is 
> > > > not
> > > >   the full GNOME 3 desktop used on other architectures, for example
> > > >   the GNOME-2-derived gnome-session-flashback
> 
> In the absence of other progress, I've staged this in git. I'll release
> it soon if nobody else in the team gets there first. The resulting
> metapackage appears to be installable on a s390x buster qemu VM with only
> sid as an apt source (so, only able to see the version of gjs in sid that
> we want to migrate, and not the one in buster that we want to supersede).
> 
> On Fri, 08 Feb 2019 at 18:10:01 +0100, Emilio Pozuelo Monfort wrote:
> > My worry if I were to do that is that the installer would still offer to 
> > install
> > GNOME on s390x, and I don't know what would happen if one chose that (I 
> > suppose
> > apt would realise it's uninstallable and give a proper error, but maybe 
> > things
> > would explode).
> > 
> > So if we're going to make task-gnome-desktop uninstallable there, maybe the
> > installer shouldn't offer to install it, and that needs changes somewhere in
> > tasksel or d-i.
> 
> Some questions whose answers I think might be relevant to determining
> how much effort is justifiable here:
> 
> * Do s390x users install with debian-installer?
> * If so, do they install desktop tasks that way?
> * Does GNOME (the desktop, as opposed to individual apps) work on s390x
>   in earlier Debian releases? (If, as I suspect, the answer is "we don't
>   know, nobody has tried it" then that is itself useful information.)

I don't have any answers here. My searching debian-boot@ for “s390x” in
the body and “installation-report” in the subject returned this small
list of bug reports: #575682, #296930, #608407, #694771, #851790,
#859889, #923524 (which you know about…).


Anyway, just to confirm: if one hacks an archive to get gnome-core out
of the amd64's Packages file, tasksel (run from a chroot rather than
from d-i, configured with this hacked repository) still lists the gnome
desktop task as an available option…


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


signature.asc
Description: PGP signature

Re: Problems with shim and shim-signed in unstable, and proposed solutions to unblock us

[Cyril Brulebois]

Steve McIntyre  (2019-03-04):
> And Mark says:
> 
> "we don't want to go rewinding version numbers in unstable; that could
> lead to all sorts of unforeseeable breakage.
> 
> much as we'd expected. Any more feedback please? Cyril prefers
> approach #2 below, I prefer #3.

To clarify: #2 was my preferred approach when we first tried to get #3 to
work, seeing how many things could need tweaking; #2 is mostly about
re-uploading packages that we know were working (albeit with different
version numbers), which looked more reassuring.

Given the amount of research we've done since then, it seems that we've
ironed out what could be an issue (mostly the fact we moved files from one
binary package to another one), and we didn't spot other packages having
relationships to either binary packages, that could have an issue with the
new layout. Building a binary package for real, even if in a chroot with
some specific versions also looks cleaner to me than repacking and
re-uploading old binaries.

Long story short: #3 looks good to me.


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


signature.asc
Description: PGP signature

Re: Problems with shim and shim-signed in unstable, and proposed solutions to unblock us

[Steve McIntyre]

I've had a reply from Mark (ftpteam) in IRC:

On Sun, Mar 03, 2019 at 11:35:45PM +, Steve McIntyre wrote:

...

>So, we're looking at three hacky options options here to work our way
>out of this hole. In (probably?) descending order of hackitude:
>
>1. Ask the nice ftpmaster people to bodge the archive by hand:
>1a. Remove the current shim source and binary packages from
>unstable (version 15+1533136590.3beb971-2)
>1b. Copy the older source and binary from buster back into
>unstable for us.
>1c. We're not even sure if this is *possible*, let alone a nice
>thing to do - thoughts?
>1d. Expecting that this might break all kinds of tools inside and
>outside of the archive maybe?

And Mark says:

"we don't want to go rewinding version numbers in unstable; that could
lead to all sorts of unforeseeable breakage.

much as we'd expected. Any more feedback please? Cyril prefers
approach #2 below, I prefer #3.

>OR
>
>2. Upload new bodged versions of shim and shim-signed to get us
>   back to working with the previously-signed shimx64.efi.signed
>   binary
>2a. Create new shim and shim-signed source packages, along with
>matching binary packages.
>2b. These binary packages will contain the *exact* same EFI
>binaries as we have in buster but with a higher version number
>in the packaging.
>2c. As we cannot *exactly* reproduce the binaries sensibly, we
>will have to hand-hack the contents of the binary packages.
>2d. We *know* this is grotty too, but we can at least make this
>work entirely at a package level.
>2e. Already tested and working: Cyril has built packages like this
>and I have tested the results successfully on my test SB
>system here.
>
>Current versions in buster:
> - shim:
>- source: 0.9+1474479173.6c180c6-1
>- binary: 0.9+1474479173.6c180c6-1
> - shim-signed:
>- source: 1.28+nmu1
>- binary: 1.28+nmu1+0.9+1474479173.6c180c6-1
>
>Possible versions targetting sid:
> - shim:
> - source: 16+1474479173.6c180c6-1 (bumped “epoch-like” N+
>   prefix, but same contents as 0.9+1474479173.6c180c6-1)
> - binary: 16+1474479173.6c180c6-1
> - shim-signed:
> - source: 1.28+nmu2 (new upload to adjust the Depends)
> - binary: 1.28+nmu2+16+1474479173.6c180c6-1
>
>OR
>
>3. Upload new version of the shim-signed source package and a
>   (lightly) bodged binary package
>3a. Use versions:
> - source: 1.28+nmu2
> - binary: 1.28+nmu2+0.9+1474479173.6c180c6-1
>3b. Needs as build-deps an old version of sbsigntool (0.6-3.2) and
>specifically version 0.9+1474479173.6c180c6-1 of shim in the
>build chroot
>3c. Then upload source+amd64
>3d. New shim-signed binary package changes in a few ways:
>* new version of the binary now include fbx64.efi.signed and
>  mmx64.efi.signed (copied across from the shim binary package)
>* add Replaces: shim (= 0.9+1474479173.6c180c6-1) so we don't
>  conflict on those binaries
>* remove Depends: shim (the whole point!)
>* change Build-Depends to list the specific versions used for
>  shim and sbsigntool
>3e. Already tested and working. I built this (source and binary
>debdiffs attached) and tested OK on SB system
>3f. This package is instantly RC-buggy due to the unavailable
>build-deps. We know...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?


signature.asc
Description: PGP signature

Re: Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

[Didier 'OdyX' Raboud]

Le lundi, 25 février 2019, 14.58:09 h CET Didier 'OdyX' Raboud a écrit :
> I call for vote immediately on the following resolution.
> 
> === Resolution ===
> 
> The Technical Committee resolves to decline to override the debootstrap
> maintainers.
> 
> Furthermore, using its §6.1.5 "Offering advice" power, the Technical
> Committee considers that the desirable solution at the time of `bullseye`
> is:
> 
> * W: `weak`: both directory schemes are allowed, but packages should only
>  be built on hosts with classical directory schemes (or in such
>  chroots)
> 
> * M: `middle`: both directory schemes are allowed, and packages (including
>official packages) can be built on hosts with either
> classical or "merged `/usr`" directory schemes
> 
> * H: `hard`: both directory schemes are allowed, but packages should only
>  be built on hosts with "merged `/usr`" directory schemes (or in
> such chroots)
> 
> * FD: Further Discussion
> 
> === End Resolution ===

Dear all,

with 6 votes in, and one week gone, the outcome of this vote is still in 
doubt; here's an abstract of the vote calculation (a clearsigned verbose 
version is attached):

/--WMHF
V: 3214 odyx
V: 2134 bremner
V: 4213 gwolf
V: 3124 ntyni
V: 2134 marga
V: 4213 fil
  Option
  W M H F 
===   ===   ===   === 
Option W0 2 4 
Option M  6   3 6 
Option H  4 3   6 
Option F  2 0 0   

Option W Reached quorum: 4 >= 2
Option M Reached quorum: 6 >= 2
Option H Reached quorum: 6 >= 2

Option W passes Majority.   2.000 (4/2) > 1

  Option M defeats Option W by (   6 -0) =6 votes.
  Option H defeats Option W by (   4 -2) =2 votes.
  Option W defeats Option F by (   4 -2) =2 votes.
  Option M defeats Option F by (   6 -0) =6 votes.
  Option H defeats Option F by (   6 -0) =6 votes.

- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The winners are:
 Option M `middle`
 Option H `hard`

- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


So. We have a tie, and the voting period is over. I am quite confident we can 
neither continue discussing (FD lost to M and H unanimously, and to W by 2), 
nor allow smcv to vote (the voting period is over). We're left with the 
Chair's casting vote (as per §6.3.2). So…

Dear Marga, as Chair, could you please make use of your casting vote to break 
this tie?

Cheers,
OdyX-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Starting results calculation at Mon Mar  4 15:34:31 2019

/--WMHF
V: 3214 odyx
V: 2134 bremner
V: 4213 gwolf
V: 3124 ntyni
V: 2134 marga
V: 4213 fil
Option W "`weak`: both directory schemes are allowed, but packages should only 
be built on hosts with classical directory schemes (or in such chroots)"
Option M "`middle`: both directory schemes are allowed, and packages (including 
official packages) can be built on hosts with either classical or "merged 
`/usr`" directory schemes"
Option H "`hard`: both directory schemes are allowed, but packages should only 
be built on hosts with "merged `/usr`" directory schemes (or in such chroots)"
Option F "Further Discussion"

In the following table, tally[row x][col y] represents the votes that
option x received over option y.

  Option
  W M H F 
===   ===   ===   === 
Option W0 2 4 
Option M  6   3 6 
Option H  4 3   6 
Option F  2 0 0   



Looking at row 2, column 1, M
received 6 votes over W

Looking at row 1, column 2, W
received 0 votes over M.

Option W Reached quorum: 4 >= 2
Option M Reached quorum: 6 >= 2
Option H Reached quorum: 6 >= 2


Option W passes Majority.   2.000 (4/2) > 1


  Option M defeats Option W by (   6 -0) =6 votes.
  Option H defeats Option W by (   4 -2) =2 votes.
  Option W defeats Option F by (   4 -2) =2 votes.
  Option M defeats Option F by (   6 -0) =6 votes.
  Option H defeats Option F by (   6 -0) =6 votes.


The Schwartz Set contains:
 Option M "`middle`: both directory schemes are allowed, and packages 
(including official packages) can be built on hosts with either classical or 
"merged `/usr`" directory schemes"
 Option H "`hard`: both directory schemes are allowed, but packages 
should only be built on hosts with "merged `/usr`" directory schemes (or in 
such chroots)"



- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The winners are:
 Option M "`middle`: both directory schemes are allowed, and packages 
(including official packages) can be built on hosts with either classical or 
"merged `/usr`" directory schemes"
 Option H "`hard`: both directory 

Re: No AMD64 daily netboot builds for the past 23 days

[Steve McIntyre]

On Mon, Mar 04, 2019 at 02:24:45PM +0200, George Diamantopoulos wrote:
>Hello all,
>
>I've noticed that there have been no D-I daily builds available for amd64 since
>February 9th:
>
>https://d-i.debian.org/daily-images/daily-build-overview.html
>
>Builds seem to be available for other architectures. Is this a known issue?
>Thanks!

Hi George,

It's a problem caused by bug #922179 - a build-dependency
(shim-signed) was not installable in unstable and tha blocked
builds. Should be fixed shortly.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I used to be the first kid on the block wanting a cranial implant,
 now I want to be the first with a cranial firewall. " -- Charlie Stross

No AMD64 daily netboot builds for the past 23 days

[George Diamantopoulos]

Hello all,

I've noticed that there have been no D-I daily builds available for amd64
since February 9th:

https://d-i.debian.org/daily-images/daily-build-overview.html

Builds seem to be available for other architectures. Is this a known issue?
Thanks!

BR,
George