Bug#921815: debootstrap umount "host" /proc when running in a Docker container

[Kristian Klausen]

Package: debootstrap
Version: 1.0.110~bpo9+1

Hi

When running debootstrap inside a Docker container, debootstrap umount both 
/proc and $TARGET/proc.
This is due to a missing check at:
https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L104
Due to the missing check debootstrap umount "$TARGET/proc", which is a symlink 
to /proc [1].

I will open a MR shortly.

[1] 
https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L68

- Kristian Klausen

Re: Multiple console support in d-i

[Wookey]

On 2019-01-25 03:45 +, Wookey wrote:
> So, unless anyone can see a problem with this approach, I'll finish
> this off. Trying to do it with separate /var/run/consoles and
> /var/run/extra-consoles files was getting very messy. 

OK. This took way longer than I hoped as it was not entirely trivial
to get everything working.

Attached is a patch which provides working multiconsole support for
linux (not hurd or bsd, sorry).

After getting the proc/console choosing code working nicely the
installer was still mysteriously not working (nothing on consoles
except debug) unless I let it respawn in which case it sort of worked
(things appeared but input oddness and continuous respawning isn't much
use to anyone).

I was confused for a while as to what was going on but eventually worked it out.

Just to recap:
The objective here is to run D-I on all the enabled consoles, (and
ideally not fiddle with the code any more than is needed).

First step was upgrading the console parsing code to use
/proc/consoles to get the list, noting the preferred console if there
is one marked as such.

The main complication is that reopen-consoles is
run twice by init, once with debian-installer-startup and once with 
debian-installer:
# main rc script
::sysinit:/sbin/reopen-console /sbin/debian-installer-startup
# main setup program
::respawn:/sbin/reopen-console /sbin/debian-installer

The first run of reopen-console works out which consoles to use, and
writes it in a file, (/var/run/console-devices), the second run just
uses that file.
debian-installer-startup is just a shell script that runs through all the
debian-installer-startup.d rc scripts, like S01mount, S04countcpus-linux-hppa, 
S10syslog.

debian-installer actually runs the installer, on the second invocation
of reopen-consoles.

So the original plan was just to run $@ (debian-installer) on the
found consoles. But doing that for the rc scripts is not helpful. Most
of it is idempotent, but you end up with two syslogs and two klogds
and running it all twice on different consoles really isn't right.

So I added an --all-consoles option to declare that we want something
(/sbin/debian-installer in this case) run on all the consoles.

# main rc script
::sysinit:/sbin/reopen-console /sbin/debian-installer-startup
# main setup program
::respawn:/sbin/reopen-console --all-consoles /sbin/debian-installer

It's also worth noting that 'steal-ctty' cannot set the process as
'controlling tty' when two are run, because only one process can be
controlling tty in a session. So I did add error checking to that (it
had none before), but had to take it out again for the 'set ctty'
IOCTL as it's correct for it to fail in the muti-console case.

So what happens now is that the rc-scripts are run on the 'preferred'
console (or the first console listed if none are marked preferred),
then D-I is run on all of them. It does not return to init in this
case (as previously discussed).

This is an important improvement so despite it having ended up rather
late in the day, I hope we can include this for buster. I'm happy to
do more work on tidying up any breakage if we find any.

Future work:

All this faffage has made me realise that a better approach to all
this would probably be to get rid of all this 'steal-ctty' bodgery,
and use init to do it's job: it's designed to run multiple things on
multiple consoles, and deal with file handles and them failing etc.

The catch is that to make this work we'd have to use sysinit: to run
the console-choosing code, then write a new inittab containing one
respawn:/sbin/debian-installer for each console instance, then HUP
init. This should do exactly the right thing (assuming that busybox
init isn't too thick to get HUPing right).

That is way cleaner and I'm happy to have a go at that, but it feels
more intrusive and unless I'm very lucky it may take a while so I
sugest we go with the above for now, as it works already.

One bug I just noticed in the bit we did today is that the 'default'
preferred console (for when one is not indicated by the kernel) avoids
the existence-check for the /dev file, so that should be
improved. It's not hard, but I'll resist doing it now and sending an
untested patch :-)

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/
diff --git a/src/etc/inittab-linux b/src/etc/inittab-linux
index a7b8a23..437e208 100644
--- a/src/etc/inittab-linux
+++ b/src/etc/inittab-linux
@@ -5,7 +5,7 @@
 ::sysinit:/sbin/reopen-console /sbin/debian-installer-startup
 
 # main setup program
-::respawn:/sbin/reopen-console /sbin/debian-installer
+::respawn:/sbin/reopen-console --all-consoles /sbin/debian-installer
 
 # convenience shells
 tty2::askfirst:-/bin/sh
diff --git a/src/sbin/reopen-console-linux b/src/sbin/reopen-console-linux
index 3287dd0..32dfd24 100755
--- a/src/sbin/reopen-console-linux
+++ b/src/sbin/reopen-console-linux
@@ -1,74 +1,67 @@
 #!/bin/sh
 
 # In order to give proper access to the tty, we need to locate 

cryptsetup 2.1.0-1 in sid: new default LUKS version, and more changes

[Guilhem Moulin]

Dear d-i team,

I'd like to bring your attention to the fact that cryptsetup 2.1.0-1,
which I just uploaded to sid, might affect the installer.  (While the
release has a significant changelog there was no SONAME bump, so it'll
hopefully make it to buster.)

I was able to install from a netinst ISO image to which I added the new
cryptsetup-udeb & libcryptsetup12-udeb, so hopefully no major bug will
show up.  But just so you know:

On Sat, 09 Feb 2019 at 00:34:47 +, Debian FTP Masters wrote:
> * New upstream release.  Highlights include:
> - The on-disk LUKS format version now defaults to LUKS2 (use `luksFormat
> --type luks1` to use LUKS1 format). Closes: #919725.

I'm glad mjg59 closed his merge request [0].  That's IMHO the kind of
change that should be done system-wise, and needs to be coordinated with
both upstream and the packaging team.  Turns out upstream had valid
reasons not to default to LUKS2, cf. the release notes for 2.0.[4-6] :-)

You might notice “WARNING: Locking directory /run/cryptsetup is missing!”
in the d-i syslog, just before the first LUKS2 device is opened.  (This
is because updates to the LUKS2 header requires multiple writes, and
atomicity is guaranteed by flock(2)'ing a file under that directory.)
The warning is harmless as the directory is created automatically (with
mode 0700) as long as its parent exists.  Of course it's always possible
to run `mkdir -m0700 /run/cryptsetup` prior to the first call to
`cryptsetup luksOpen`, like we're doing in our initramfs scripts (but
unlike for d-i, at initramfs stage the warning is annoying as it's shown
to the user before the prompt).  Failures to flock(2) immediately abort
the `open` command, so there is no risk of ending up with inconsistent
metadata here.

> - The cryptographic backend used for LUKS header processing is now libssl
> instead of libgcrypt.

Works out of the box since there is already an libssl1.1-udeb package.

> - LUKS' default key size is now 512 in XTS mode, half of which is used for
> block encryption.  XTS mode uses two internal keys, hence the previous
> default key size (256) caused AES-128 to be used for block encryption,
> while users were expecting AES-256.

`luksFormat` might cause entropy starvation on low-entropy systems that
use the default key size (i.e., don't pass `-s`) *and* use `--use-random`.
(The default RNG source for volume keys was, and still is, /dev/urandom.)
Probably irrelevant for d-i?

See


https://tracker.debian.org/news/1028794/accepted-cryptsetup-2210-1-source-into-unstable/
and/or

https://salsa.debian.org/cryptsetup-team/cryptsetup/blob/v2.1.0/docs/v2.1.0-ReleaseNotes

for the full changelog.  And of course, please shout if that upload
broke anything :-)

Keep up the good work!
-- 
Guilhem.

[0] https://salsa.debian.org/installer-team/partman-crypto/merge_requests/1


signature.asc
Description: PGP signature

Re: default desktop

[Jeremy Bicha]

On Fri, Feb 8, 2019 at 7:37 PM Samuel Thibault  wrote:
> As mentioned earlier in the thread, the default desktop for
> accessibility is already MATE. I'm here talking about the choice of
> default desktop for Debian indeed. IIRC one of the reasons for the
> choice of gnome was its general accessibility, and I'm just saying I
> believe that part has changed.

Ok, then you need to discuss this with the rest of the Debian GNOME
team. I suggest the debian-gtk-gnome list. (And I think it would have
been more polite to talk to them before talking to the tasksel team.)

It's a bit late to be talking about reverting Wayland by default for
everyone since this has been enabled for Testing since soon after the
Stretch release.

Thanks,
Jeremy Bicha

Re: default desktop

[Samuel Thibault]

Jeremy Bicha, le ven. 08 févr. 2019 18:57:30 -0500, a ecrit:
> On Fri, Feb 8, 2019 at 12:07 PM Samuel Thibault  wrote:
> > Re-opening the question of the default desktop just a bit to provide
> > updated information: the current gnome-with-wayland default is a concern
> > for accessibility. Accessibility on Wayland has a lot of glitches in
> > all kinds of places, and nobody is working on fixing them yet. Also,
> > MATE+Compiz now provides very nice zoom support.
> 
> Sorry: I have lots of questions.
> 
> Could you rephrase this email and provide more context?
> 
> Are you proposing to change Debian's default desktop or just the
> default desktop for accessibility?

As mentioned earlier in the thread, the default desktop for
accessibility is already MATE. I'm here talking about the choice of
default desktop for Debian indeed. IIRC one of the reasons for the
choice of gnome was its general accessibility, and I'm just saying I
believe that part has changed.

> Could you point to issues with accessibility using GNOME on Wayland?

I don't have a list, I just heard it a lot, and notably from Joanmarie.
The basics of accessibility do work, but apparently a lot of small
details pose problem.

One instance could be Bug#919417 which only happens with Wayland.
Bug#919411 is also about Orca not having support for catching capslock
as an Orca key, which is a concern on laptops.

> You can force disable GNOME on Wayland completely by setting
> WaylandEnable=false in /etc/gdm3/daemon.conf

Sure, but the question is the accessibility of a default debian system.

> I assume MATE isn't defaulting to using Compiz now?

It isn't.

Samuel

Re: default desktop

[Jeremy Bicha]

On Fri, Feb 8, 2019 at 12:07 PM Samuel Thibault  wrote:
> Re-opening the question of the default desktop just a bit to provide
> updated information: the current gnome-with-wayland default is a concern
> for accessibility. Accessibility on Wayland has a lot of glitches in
> all kinds of places, and nobody is working on fixing them yet. Also,
> MATE+Compiz now provides very nice zoom support.

Sorry: I have lots of questions.

Could you rephrase this email and provide more context?

Are you proposing to change Debian's default desktop or just the
default desktop for accessibility? If it's just for accessibility,
could you explain more about how users opt in to that and what its
effects are? Sorry I don't install Debian very often and I've not
tried doing it with accessibility enabled.

Could you point to issues with accessibility using GNOME on Wayland?

You can force disable GNOME on Wayland completely by setting
WaylandEnable=false in /etc/gdm3/daemon.conf

I assume MATE isn't defaulting to using Compiz now? If so, it seems
simpler to just disable Wayland for accessible users than installing
MATE and switching to Compiz?

Thanks,
Jeremy Bicha

partman-auto-lvm_73_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Feb 2019 00:21:29 +0100
Source: partman-auto-lvm
Architecture: source
Version: 73
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-auto-lvm (73) unstable; urgency=medium
 .
   * Remove trailing whitespace from changelog file, to fix lintian tag.
 .
   [ Updated translations ]
   * Hebrew (he.po) by Yaron Shahrabani
   * Kazakh (kk.po) by Baurzhan Muftakhidinov
   * Simplified Chinese (zh_CN.po) by Boyuan Yang
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 0d561443ef859cac4ca1fa208cb4b4f2101a1d35 1743 partman-auto-lvm_73.dsc
 582993a21915fa5bf9fc0b8af855f0bb93807f1c 119192 partman-auto-lvm_73.tar.xz
 00f53e9046f3d6822f27e377275da36a4a51f08d 5316 
partman-auto-lvm_73_amd64.buildinfo
Checksums-Sha256:
 e9c9614ea4bf0b4871d082968db6fbdcd7f3c045189b225b499228e732935343 1743 
partman-auto-lvm_73.dsc
 832d6267b0bcdf2d981aeb71792e89f98d0f7d864ac473c3bb68903e253b23ee 119192 
partman-auto-lvm_73.tar.xz
 b38a5f9f9955518c3893b770aaea34707d590f139797b53634091c8e983028b7 5316 
partman-auto-lvm_73_amd64.buildinfo
Files:
 65d2a2a3ffa699242f70b58f6d08cc2f 1743 debian-installer optional 
partman-auto-lvm_73.dsc
 fa9698e5051f92cf70f2c7fb5e1a4d35 119192 debian-installer optional 
partman-auto-lvm_73.tar.xz
 29dd092f3884d3a885b2d067c7cb1b5e 5316 debian-installer optional 
partman-auto-lvm_73_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxeEHMVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB29UYP/1Ri5wCV18L+bOdbOzK4itHeE2Y8
ZBK0cxtgynI67Fkmilmj6585zp2xvFuDuR+IbjlmVNaek3FIjpHyRIcx8iHiFbAj
Fb2R77POOdXhJaWnKD0LTIbKTJG/S/co7cRriAQeauzdDvK7EbanVnStb+CNqoN4
hJJ1eCfs4scPPqU4zYRfygLB302lKec/IqK7koJyjzqEu2nky6uLQG2bpqaftJmu
Pc0QBEN7nbtBD7PFIupKDEWAMUSLwBp10VwF8LsumCNoRYK0zKlnEbs79nFZGOtw
y/XVHoPx/Uu7tCbWQCWzUcir1yhwvuDsFGpKD739t+fx9FTvZfqfetTUUIUOgaUu
XZHHP2Ng8QdVMrwUh5wZZ32xNWhPKjASgT/c4JqYHG+A/dvbWw6qeweG0M4FAhtA
42bkPBfGd3fELRhNZL6uUiyPmXjrqaJOoV4UB30t2xs//RCqKFj4cq0fwf2PPw1j
OpEf8cd/YimQsC7NWEKi/teUqxKVGfymoel4efGPOZbu9EeLN9eRMQLYpSAEkPts
L3aXa/QY2N88SsZr3S5B6GwQkbGdvmqdPbdICvj5lQssvjc8UZKdNeK8sz9PTDMZ
tThFVtGDrEz3bR9kJ80GIWNIbHlSJvVvRYQErQ0WedENieAxeyhL2KBGDJZWeZUA
aFlFi9KavUm6+XXo
=AdoA
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of partman-auto-lvm_73_source.changes

[Debian FTP Masters]

partman-auto-lvm_73_source.changes uploaded successfully to localhost
along with the files:
  partman-auto-lvm_73.dsc
  partman-auto-lvm_73.tar.xz
  partman-auto-lvm_73_amd64.buildinfo

Greetings,

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

console-setup_1.189_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 23:22:53 +0100
Source: console-setup
Architecture: source
Version: 1.189
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 920287
Changes:
 console-setup (1.189) unstable; urgency=medium
 .
   * Team upload
 .
   [ Holger Wansing ]
   * Correct release date/time of version 1.188 in changelog file.
   * Remove trailing whitespaces from control and rules files, to fix
 lintian tag.
 .
   [ Antonio Larrosa ]
   * Keyboard: Translate ISO_Left_Tab to Meta_Tab. Closes: #920287
 .
   [ Updated translations ]
   * Danish (da.po) by Joe Hansen
   * Finnish (fi.po) by Juhani Numminen
   * Hebrew (he.po) by Yaron Shahrabani
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 062efb9cff03400efdbc3a8736833bce21adf29b 3360 console-setup_1.189.dsc
 d05111368cc5474a7f9b42d4a7bfbbd6378a8020 1649820 console-setup_1.189.tar.xz
 b21d601704464d8b057c695904653f71cf6518c8 11512 
console-setup_1.189_amd64.buildinfo
Checksums-Sha256:
 9969e7661754c2ebe6601685b22dac191d4c991dfb4274155fa37353f6dc8f72 3360 
console-setup_1.189.dsc
 5288659f82fb368fca18f3e541eaf877304dda59b38b398b71e6d448bc893eb1 1649820 
console-setup_1.189.tar.xz
 a778f0dee6451931a0b53d8af806a3deedfe25df477ad5df209275f52851d4ba 11512 
console-setup_1.189_amd64.buildinfo
Files:
 55b56ba9da5a62b8ebd393427a09cd3e 3360 utils optional console-setup_1.189.dsc
 c31ace51628f2cebbcb1b1a6d7fe1085 1649820 utils optional 
console-setup_1.189.tar.xz
 630d73c174829941f8cf263660508ee6 11512 utils optional 
console-setup_1.189_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxeDeMVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2exwQAKDwMCzjpdfOY0FWXTRUx4W5kifF
FWOV01I7fpRMd28EpE43a26Y66tM6nfLkL2mJdqNeNaLOoNPUKszoMVkxJLbR112
lC+dNoE7rZQdldZK4uzm9F7ron7joi4KO9abGkKQb0/C/I2s9qK8yyr/IwwOWLEk
P8Ozzc+q5K2l56aoCkE86luZlsRUsvD2u8hKsG7dpDM9Z8PvJUhdkSrFluoSWIks
YW/ZS4rj9czCL87aujwjLD0xsCfwKQj9Ebf9ezVIOOHha473j6ySbUntWchp3k6l
y1ZQ4LwFhs1iIL4L/C/hpRukXu7kvIK+bWtvp2GCSy2XqniWmxDC7wq7dhy+RNCo
GyJI5wJknBqrGczcfJSo48Ye5eo7iZVgCWTt9SBiq4gfOIEyqdydVDUIhPFEeVXV
QfPocdqC/dZ26wcw+d39vRlfhALzkG+WR6KMCfWqoaii+husIQyeZKz6xid/5H6F
e8ugWgJvsYgXXIGTFOi9JGvbrCxYipKAsH6eJLcIgErR6o18vjKwVNRKy915HE7Z
yIRovgDyVm75tCJilKGmFfH1+A3k/s6/12+Xu4wYBBcA++Q8mHFGHk62fmf2Wyql
o9VQdN2nswGbEPtV4S34G7VrtpJqIc10FuJrV8O5DhnzExkgKFh+UH6FpIW42YNF
yfXIEK/bzT07vl1E
=SInK
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of console-setup_1.189_source.changes

[Debian FTP Masters]

console-setup_1.189_source.changes uploaded successfully to localhost
along with the files:
  console-setup_1.189.dsc
  console-setup_1.189.tar.xz
  console-setup_1.189_amd64.buildinfo

Greetings,

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

Bug#920287: marked as done (Shift-Tab doesn't work in text mode)

[Debian Bug Tracking System]

Your message dated Fri, 08 Feb 2019 23:35:09 +
with message-id 
and subject line Bug#920287: fixed in console-setup 1.189
has caused the Debian Bug report #920287,
regarding Shift-Tab doesn't work in text mode
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.)


-- 
920287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup
Version: 1.188
Severity: important
Tags: patch upstream

Shift-Tab doesn't work in text mode so for example, in the debian installer or
openSUSE's YaST, pressing Tab goes to the next focusable item but pressing
Shift-Tab (which should go to the previous focusable item) just works as if only
Tab was pressed.

This is due to ISO_Left_Tab being translated just to Tab by ckbcomp when
converting the text layouts.

Looking at how the keyboard layouts were defined before xkb layouts were parsed,
I noticed legacy layouts were defined like:

```
keycode 15 = Tab
shift  keycode 15 = Meta_Tab
```

The attached patch changes ckbcomp to translate ISO_Left_Tab to Meta_Tab fixing
the issue for Yast and I guess also for the debian installer (in openSUSE the
kbd package has to be rebuilt with the fixed console-setup package, and in
debian I think the console-data package has to be rebuilt the same way too)

Note that I also submitted a merge request at
https://salsa.debian.org/installer-team/console-setup/merge_requests/1
with the same patch and the commit log explains more about the issue.

>From 564f2dfbe9661df5094a0107568878d405fc2fae Mon Sep 17 00:00:00 2001
From: Antonio Larrosa 
Date: Tue, 22 Jan 2019 18:06:28 +0100
Subject: [PATCH] Translate ISO_Left_Tab to Meta_Tab

Short description:
ISO_Left_Tab shouldn't be translated to Tab (just like regular Tab)
otherwise there's no way to differentiate between Tab and Shift-Tab
on text mode. This commit changes ckbcomp to translate ISO_Left_Tab
to Meta_Tab.

Long description:
Currently, in most Linux distribution, most keyboard layouts in text
mode assign the Tab and Shift-Tab key presses the same code.
This can be checked by pressing ctrl-alt-f1, logging in and running:
"showkey -a"

Pressing Tab and Shift-Tab generate the same code (0x09), so for
example, when Yast runs with ncurses, Tab moves the focus to the next
focusable item, but Shift-Tab can't be used as it behaves just like
Tab and there's no way applications can differentiate both.

Changing the keyboard layout with "loadkeys es", "loadkeys de" or
"loadkeys fr" doesn't help.

I investigated this and found that ckbcomp was translating the
ISO_Left_Tab symbol to Tab just like it does with Tab, which doesn't
make sense since Shift-Tab should produce a "Left Tab" (in many
keyboards it's even printed in the Tab key over the regular Right-Tab
drawing).

Looking at how the keyboard layouts were defined before xkb layouts
were parsed, I noticed legacy layouts were defined like:

keycode 15 = Tab
shift  keycode 15 = Meta_Tab

So ISO_Left_Tab is now translated to Meta_Tab to fix this and let it
generate the same code it did in the past.

Now "showkey -a" shows the (0x09) code for Tab and (0x1b 0x09) for
Shift-Tab which can be recognized by text applications as different
and automatically fixes Yast.

In SUSE/openSUSE distributions, after applying this change and
rebuilding the kbd package with the generated console-setup (which
regenerates the kbd keymaps with the fixed ckbcomp script) fixes this.
I guess other distributions would also need to rebuild kbd after
applying this patch.
---
 Keyboard/ckbcomp| 2 +-
 Keyboard/compose_translator | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Keyboard/ckbcomp b/Keyboard/ckbcomp
index b0df606..47ec922 100755
--- a/Keyboard/ckbcomp
+++ b/Keyboard/ckbcomp
@@ -2581,7 +2581,7 @@ if ($freebsd) {
  'any' => 'NoSymbol', # Is this recognised by X ?
  'VoidSymbol' => 'VoidSymbol',
  'voidsymbol' => 'VoidSymbol', # Is this recognised by X ?
- 'ISO_Left_Tab' => 'Tab',
+ 'ISO_Left_Tab' => 'Meta_Tab',
  'Clear' => 'VoidSymbol',
  'Pause' => 'Pause',
  'Scroll_Lock' => 'Scroll_Lock',
diff --git a/Keyboard/compose_translator b/Keyboard/compose_translator
index d478def..3af492f 100755
--- a/Keyboard/compose_translator
+++ b/Keyboard/compose_translator
@@ -1827,7 +1827,7 @@ my %xkbsym_table = (
  'any' => 'NoSymbol', # Is this recognised by X ?
  'VoidSymbol' => 'VoidSymbol',
  'voidsymbol' => 'VoidSymbol', # Is this recognised by X ?
- 'ISO_Left_Tab' => 'Tab',
+ 

choose-mirror_2.97_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 23:07:16 +0100
Source: choose-mirror
Architecture: source
Version: 2.97
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 choose-mirror (2.97) unstable; urgency=medium
 .
   * Remove trailing whitespaces from changelog file, to fix lintian tag.
 .
   [ Updated translations ]
   * Persian (fa.po) by nima sahraneshin
   * Finnish (fi.po) by Juhani Numminen
   * Hebrew (he.po) by Yaron Shahrabani
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 7185514d27de40fb8d11ac4db1d51d41f3b89cca 1896 choose-mirror_2.97.dsc
 871a7a999fdccead14c389cda63d8e66e41346aa 187184 choose-mirror_2.97.tar.xz
 2b08c4b00397332f1d4c77db1acadf569525772d 6100 
choose-mirror_2.97_amd64.buildinfo
Checksums-Sha256:
 8c9f8c167df17c594fb824ce2d0c02100e200dde2b825e20ba74645075696f3d 1896 
choose-mirror_2.97.dsc
 358db7f992f20ef659859ac753bed18a24b65b523e51101a339b16a9c2dc9068 187184 
choose-mirror_2.97.tar.xz
 c5f1701aab1bd6ae39b5063abbf4b008a05806ad4634768d19f24478437594ae 6100 
choose-mirror_2.97_amd64.buildinfo
Files:
 023baa49de5ff0816bdd6477e9430684 1896 debian-installer optional 
choose-mirror_2.97.dsc
 c898b7645486f9d77c9d02dd6ae7ab48 187184 debian-installer optional 
choose-mirror_2.97.tar.xz
 8857991453a6abc81c8f5d4ceaa5568d 6100 debian-installer optional 
choose-mirror_2.97_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxd/8YVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2tvQP/RHpOxTnf14Yl2IaeL2w/uPQPhs5
I6VNz/OlldSlJ//Q1LhNgG2a4MhpPd39/Xpu5qF1DvOX2fC/yHkR0z5wObfg+gKe
rtdDHUT8vDDtMgyAhwkMz2EMqH9yYNLpOZIdMbOt/LafWWxMjcgZDkttoN4wSsvE
lPhYpQrRFp/+clQDFlDCR44Y7eYLoy5ADr3LauoLav0Vtk5a4GFjHgZZB2sg/rBQ
kPC8BaIE9cJGy9B843Map0a210wyR89yIsWmAb75PpKHpIny+oAgHzyReVsuJMZd
QYPifM0KATY3cWywspd6g1cfNfho2vvzsSvvASswkPcSyJpfW+ENm6m7fmp/tt+d
lBTQbIe+CT6CTCgoWEpYBkBKgaGW4cM431h4UXWiW5YxjpLd8aaUFTTbx8M7EOIc
lMvuIZUiHIB6vaHFiING3ecp4xJkjrRLDEExGSVGs3/ETuvVCszenTduxOSJ5xwD
9x1NWEvuqbLlNEQa2OSFLr0rsV6NA6fGfuZ+Bq9bxjD8GaBwEfQYw/iDYyaTG2TY
T5zjNfYEWrL1fKnHBWHxdvkYAE0CdP9jXrczE/Yuy/yWT7209JtmUeW3+6kEoWKg
0SXFAbYGN15VzFWqrOoS804P/2FoWUPmdLsc78UyGucZx/Dbn7yRFf19/tZx8qRT
JqVfm1YXSe3WI4rG
=AAt9
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of choose-mirror_2.97_source.changes

[Debian FTP Masters]

choose-mirror_2.97_source.changes uploaded successfully to localhost
along with the files:
  choose-mirror_2.97.dsc
  choose-mirror_2.97.tar.xz
  choose-mirror_2.97_amd64.buildinfo

Greetings,

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

preseed_1.100_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 22:47:19 +0100
Source: preseed
Architecture: source
Version: 1.100
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 preseed (1.100) unstable; urgency=medium
 .
   * Team upload
 .
   * Remove trailing whitespaces from changelog file, to fix lintian tag.
 .
   [ Updated translations ]
   * Hebrew (he.po) by Yaron Shahrabani
   * Kazakh (kk.po) by Baurzhan Muftakhidinov
   * Romanian (ro.po) by Andrei POPESCU
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 4595312fd41f499fae2d7378403643883aefefe9 1943 preseed_1.100.dsc
 3dced95aabae60558ab34aa34043a297d59657b8 82960 preseed_1.100.tar.xz
 002184ca492b6c66b647d24d81a24e0190d93ef8 6296 preseed_1.100_amd64.buildinfo
Checksums-Sha256:
 47c3fac9ed079692e5b34fcb0942c2e3ef81184103df7ff6aa81792ba887b75a 1943 
preseed_1.100.dsc
 a5e36504374361fd4afb97c10faa5c26235446582848cd96c36013843a539daa 82960 
preseed_1.100.tar.xz
 33aa3ee5e216f2983c9b4f25b4f2ab0aabbf591ee25eb4f1d11cf7748a83147a 6296 
preseed_1.100_amd64.buildinfo
Files:
 3e190628bd71022c88e3db317e8565a8 1943 debian-installer optional 
preseed_1.100.dsc
 2c2160f2bf0c494937fe9e351abffc36 82960 debian-installer optional 
preseed_1.100.tar.xz
 b577e403306dd86038aba5a7736bb045 6296 debian-installer optional 
preseed_1.100_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxd/EEVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2DJ4P/3rkDL+rWxikVdW+O3LZHwKeQIpK
AlEm/g+JaqkxDxhueb239G7++zNQgKNW4v+iASkW4/iKuDU+Yh3h1ITFgZWtSQ75
FkEcYxPq0FyGKNGzNBxqqcm2INIWO9wtu4ccjWthhG6pZt3nVknpgF1AJd0D8PWg
WJyHJGvK9/3eVGImSJgPIs0s+0szMZ0cRwG1Xocaij6rAc7BP4bq9Vr1s9HAnQUm
NJYm8rhQQ8eQUEFYvNJx+I+MBb4aFPOS2Xc/2mhq2TbD/jHPG9OZUUU3qrwsTWFO
4KMRhbaMP2p5UGrymYLuVDwk4qB2Kgw0B9NEAqOq5tb8yPnRuM6ff+j5JrqjmKWT
TW7H0XvEyoMLMpveVzEnuY6cJWq6qdhGOeaA9Yv12eJJaqeVactW9Ct2dWRPE3z6
NyTK4TO4ltXIjdfUhOULPboQeInZ+wJlFlj5WfVlBauCrcRsApql5x46Q+Em/qbl
GOzhiGs79KCldRz+OsZMh+ne6Povn5i7SSa6e6T/Hh93pWKS+LqZDk+OKqEZ7aRL
44G8atNoynbbd8ZHGQtdq5LMbzjZCjCeeIUJvLeK4u2Q2nM6874vHheYSug0UjSb
y0sdW0Foa7vx3xpmVeAVC7MmAze3hsnRksgkosNqxIFDNqXOzU+sDDCRc3eFOXax
mEUJ6Z8LsMeURfYL
=smuE
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of preseed_1.100_source.changes

[Debian FTP Masters]

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

Greetings,

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

tasksel_3.50_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 22:28:45 +0100
Source: tasksel
Architecture: source
Version: 3.50
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 680668
Changes:
 tasksel (3.50) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yves-Alexis Perez ]
   * task-xfce-desktop: drop dependency on orage since it will be removed
 before Buster
 .
   [ Holger Wansing ]
   * task-kannada-desktop: move 'firefox-esr-l10n-kn | firefox-l10n-kn' from
 Depends to Recommends, as it is for all other language task, to fix
 #913159 for Buster.
   * Remove trailing whitespace from control file, to fix lintian tag.
   * task-chinese-t-desktop: switch input method from scim to fcitx for
 Traditional Chinese. Closes: #680668
Checksums-Sha1:
 1186ce4c844d4638eb9d3f1200985560bff9bc3f 17102 tasksel_3.50.dsc
 f577737152ebe2bb7e4e2167efb0ad46cecc63c9 289304 tasksel_3.50.tar.xz
 0dc611d9fb9b711265c1898a9710b1e8cd42704a 65041 tasksel_3.50_amd64.buildinfo
Checksums-Sha256:
 335bb4510af813718bdc8275f0c6b56b52b0076dacb79216730eafd6b62b6439 17102 
tasksel_3.50.dsc
 1478b04ad7e93019e96a8ea5140b30269aa030ea3c0aba837ce84aec68319260 289304 
tasksel_3.50.tar.xz
 f0967ba39c65a31f1b04cf8b84a04c90431f8856e12e925a89565f64e8e29589 65041 
tasksel_3.50_amd64.buildinfo
Files:
 6a8e3c81868994b7da6dae4f38045457 17102 tasks optional tasksel_3.50.dsc
 d7e220810704b05f4025b0f0dd6b4c29 289304 tasks optional tasksel_3.50.tar.xz
 1285723d5f0d9e407f027e28f42390ea 65041 tasks optional 
tasksel_3.50_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxd93UVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB27UQP/1mA30iNSC67A6vsdGiONpoCHQBl
46vPpZfFpy+ZFPRlIFwG7cfpxyYGAtLhBDTA8yQwJxFgQMfCysaHgObTpnLO/Rj5
s7o19BEpAgBogHK+Ex9+bM2L8o+PIaWyv7c9eEHoVAFzljwcq+hrGO1uRyDzRGnh
2Vooei2sf0Qgxtpa8igg5fxqZxYHuCazqovXp0l+cYs+KBWixDQlnZSbLMaD2nlQ
wK9SafmnHofJxRUutQDVIJ/DgsDqE8KOTl42vyNNJrxB5Uc0ecsAlv9YisN0TGZF
vjgN7n4riTf/pJUiggErMnih9+Iw623r9HUEDgQPCe11UCs8eEZ48yZbsQsgzjaW
3AXjZi7QF/iCMKIH1SrBvt1Qx2FYQeMrDf50VzP31fGCRf7iIKHvY64/l1VK2lFu
ThkXwiMmxqTR3iQzqa3qzwEKcJJ/zyu5pDTSfGF6dPHVUCJW86wLwbPmazbqe3oy
AzfJUxGy4GFTx8Ch9nxvNuSeWqA74FDLeKTR/Dd/+hx4gZeAzEhALXuo/HNPHaSH
KugWpMtgUmtnkIij9WcXhCsrVQ0RRDm/G3kBEJOBpCpAX1TLprlS1ai4YjhmRffO
nJXIvLupuV9L73OZl5SyS1vzVi5YjTDRAjk29QvAoe+OOpn0ff1ft5xyztyQDb2+
gfVKgN/2ifNjd/KA
=DF0a
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#680668: marked as done (tasksel: Updating chinese-t-desktop in tasksel for Wheezy.)

[Debian Bug Tracking System]

Your message dated Fri, 08 Feb 2019 22:08:52 +
with message-id 
and subject line Bug#680668: fixed in tasksel 3.50
has caused the Debian Bug report #680668,
regarding tasksel: Updating chinese-t-desktop in tasksel for Wheezy.
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.)


-- 
680668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tasksel
Version: 3.10
Severity: wishlist

Dear Maintainers/Users,

Let's do an update for chinese-t-desktop in tasksel for wheezy release
shortly.

Cause tasksel changes are related cd/dvd images builts, so that
Christian Perrier suggested a deadline will be the end of July.

In another words, this bug should be closed when the deadline reached.

Please feel free to give suggestions before the deadline.

Thanks in advance,

-Andrew

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

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tasksel depends on:
ii  apt 0.9.7.1
ii  debconf [debconf-2.0]   1.5.45
ii  liblocale-gettext-perl  1.05-7+b1
ii  perl5.14.2-12
ii  tasksel-data3.10

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information excluded


--- End Message ---
--- Begin Message ---
Source: tasksel
Source-Version: 3.50

We believe that the bug you reported is fixed in the latest version of
tasksel, 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 680...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated tasksel 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: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 22:28:45 +0100
Source: tasksel
Architecture: source
Version: 3.50
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 680668
Changes:
 tasksel (3.50) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yves-Alexis Perez ]
   * task-xfce-desktop: drop dependency on orage since it will be removed
 before Buster
 .
   [ Holger Wansing ]
   * task-kannada-desktop: move 'firefox-esr-l10n-kn | firefox-l10n-kn' from
 Depends to Recommends, as it is for all other language task, to fix
 #913159 for Buster.
   * Remove trailing whitespace from control file, to fix lintian tag.
   * task-chinese-t-desktop: switch input method from scim to fcitx for
 Traditional Chinese. Closes: #680668
Checksums-Sha1:
 1186ce4c844d4638eb9d3f1200985560bff9bc3f 17102 tasksel_3.50.dsc
 f577737152ebe2bb7e4e2167efb0ad46cecc63c9 289304 tasksel_3.50.tar.xz
 0dc611d9fb9b711265c1898a9710b1e8cd42704a 65041 tasksel_3.50_amd64.buildinfo
Checksums-Sha256:
 335bb4510af813718bdc8275f0c6b56b52b0076dacb79216730eafd6b62b6439 17102 
tasksel_3.50.dsc
 1478b04ad7e93019e96a8ea5140b30269aa030ea3c0aba837ce84aec68319260 289304 
tasksel_3.50.tar.xz
 f0967ba39c65a31f1b04cf8b84a04c90431f8856e12e925a89565f64e8e29589 65041 
tasksel_3.50_amd64.buildinfo
Files:
 6a8e3c81868994b7da6dae4f38045457 17102 tasks optional tasksel_3.50.dsc
 d7e220810704b05f4025b0f0dd6b4c29 289304 tasks optional tasksel_3.50.tar.xz
 1285723d5f0d9e407f027e28f42390ea 65041 tasks optional 
tasksel_3.50_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxd93UVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB27UQP/1mA30iNSC67A6vsdGiONpoCHQBl
46vPpZfFpy+ZFPRlIFwG7cfpxyYGAtLhBDTA8yQwJxFgQMfCysaHgObTpnLO/Rj5
s7o19BEpAgBogHK+Ex9+bM2L8o+PIaWyv7c9eEHoVAFzljwcq+hrGO1uRyDzRGnh
2Vooei2sf0Qgxtpa8igg5fxqZxYHuCazqovXp0l+cYs+KBWixDQlnZSbLMaD2nlQ
wK9SafmnHofJxRUutQDVIJ/DgsDqE8KOTl42vyNNJrxB5Uc0ecsAlv9YisN0TGZF
vjgN7n4riTf/pJUiggErMnih9+Iw623r9HUEDgQPCe11UCs8eEZ48yZbsQsgzjaW
3AXjZi7QF/iCMKIH1SrBvt1Qx2FYQeMrDf50VzP31fGCRf7iIKHvY64/l1VK2lFu
ThkXwiMmxqTR3iQzqa3qzwEKcJJ/zyu5pDTSfGF6dPHVUCJW86wLwbPmazbqe3oy

Processing of tasksel_3.50_source.changes

[Debian FTP Masters]

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

Greetings,

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

pkgsel_0.63_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 22:07:38 +0100
Source: pkgsel
Architecture: source
Version: 0.63
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 pkgsel (0.63) unstable; urgency=medium
 .
   * Team upload
 .
   * Correct release date/time of version 0.62 in changelog file.
 .
   [ Updated translations in ./packages/pkgsel ]
   * Danish (da.po) by Joe Hansen
   * Persian (fa.po) by nima sahraneshin
   * Finnish (fi.po) by Juhani Numminen
   * Gujarati (gu.po) by Kartik Mistry
   * Kazakh (kk.po) by Baurzhan Muftakhidinov
   * Telugu (te.po) by Praveen Illa
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 7b7d80cb431808f1a9c49f48015a6f1ef6cb205f 1620 pkgsel_0.63.dsc
 72142b591b8024f481aceaa8af610056d8dd54ee 54824 pkgsel_0.63.tar.xz
 6d113459531c850b25dff3fb762db915a34664bf 5218 pkgsel_0.63_amd64.buildinfo
Checksums-Sha256:
 ccd1ea3379db6526800fb920e3b992208fac2f7596c3228539d1c09059f810e7 1620 
pkgsel_0.63.dsc
 89f331a6a75925e9dbcb7fff4ad11e79b0b4349d5742246d8e47413f350917a3 54824 
pkgsel_0.63.tar.xz
 5acbe8d1a22201345815692b9f90b3389bb717be3248d1e59c0ad4827bc6a324 5218 
pkgsel_0.63_amd64.buildinfo
Files:
 fa22602fa7651079451838ff68dd19c3 1620 debian-installer standard pkgsel_0.63.dsc
 ef954a5abde6e7fb595b389a090d8858 54824 debian-installer standard 
pkgsel_0.63.tar.xz
 6e1ed3483c4b9c433dcb7c3a4378a365 5218 debian-installer standard 
pkgsel_0.63_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxd8+MVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2HTcQALxOYg6kRed/cP/gy9qxnWTjXWGr
s6B6rLvojktlVAILgdV+zuEgJjXbLV/KKKpNJUwwhE8qTstjlQM6HMnmzVU3hc4i
aAVSs0a0MXUddutFfIV4fAXzUjE3Gtp0DooI2nYX8bAsWmzCAepmfmv8FjDNNbTt
iabFtFo5t2hl9uNrVeCXFKQXgSoUI9unQ+kMbKmhWWU88LI+s0BjyfUeRPazlXdd
OUxPE72lvTvpZST4dLCKVvQOSFzGjrsFXstaNwj0lgey41PbRN898yTz5oa5KcbP
LnB794XXZvaIDAShXTsanW2RjuKXtecErRXvlRAtuQ+uc8xj6hb+qDi0iiJpcn+U
4Ir0CGPHF9RxyiDnlAgpWQgrQsHaPEHk2rUBiJRnM+kD35CI/q4u4cVK0/N8zGI6
LWUpDplyVT4qkKXDwOaiogIxYr0BPS/u/an2InIBmkVnw+kphRwKkGCchChXdoIr
hI1DZrTUY2ST3rdWw39rBTQxtLgazOkalbpNFLQA2TQ+udlr+zt7oaYVZQGkq4uK
aUCvJgygBQJuEAVUZfiQTpcedjM4RuUtcdfVaR7TGxc1vAUac/lmwcmTgxiunGYy
/I+1E+NqrS+T07vWDwFoK6Rj586YZ5AFGea9vBbLI/VPBhDah0Add3n6TrRxNIDq
sSLlx3DMJZMOHUli
=xCDW
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of pkgsel_0.63_source.changes

[Debian FTP Masters]

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

Greetings,

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

Bug#918846: busybox: CVE-2018-20679

[Moritz Mühlenhoff]

On Wed, Jan 09, 2019 at 09:39:33PM +0100, Salvatore Bonaccorso wrote:
> Source: busybox
> Version: 1:1.27.2-3
> Severity: normal
> Tags: patch security upstream
> Forwarded: https://bugs.busybox.net/show_bug.cgi?id=11506
> 
> Hi,
> 
> The following vulnerability was published for busybox.
> 
> CVE-2018-20679[0]:
> | An issue was discovered in BusyBox before 1.30.0. An out of bounds read
> | in udhcp components (consumed by the DHCP server, client, and relay)
> | allows a remote attacker to leak sensitive information from the stack
> | by sending a crafted DHCP message. This is related to verification in
> | udhcp_get_option() in networking/udhcp/common.c that 4-byte options are
> | indeed 4 bytes.
> 
> Note that the only once commit initially referenced for CVE-2018-20679
> is incomplete, but see security-tracker for further notes.

Fixed by:
https://git.busybox.net/busybox/commit/?id=6d3b4bb24da9a07c263f3c1acf8df85382ff562c
https://git.busybox.net/busybox/commit/?id=74d9f1ba37010face4bd1449df4d60dd84450b06

Can we please get that fixed before the buster freeze?

Cheers,
Moritz

Re: default desktop

[Mewtamer]

Checking Aptitude, libgtk-3-0 depends on libwayland-client, and
Firefox depends on libgtk-3-0 and Orca has libwayland-client and
libgtk-3-0 somewhere in its dependency chains. I don't run a full
desktop environment, but as these are the only graphical programs I
run, I suspect most, if not all, currently maintained GTK applications
depend on libwayland-client or some other wayland component and its
only a matter of time before Wayland becomes the default across all
GTK-based desktops.

Assuming that Orca's compatibility with Qt and less widely used GUI
toolkits remains as poor as I've been lead to believe, we might find
ourselves racing the clock to fix glitches in Wayland before it fully
takes over from whatever its in the process of replacing(I think it's
Xorg, but I confess I don't really understand the house of cards that
goes into building a Desktop environment even without the extra deck
accessibility adds to the mix).

Re: default desktop

[Didier Spaier]

On 08/02/2019 19:24, john doe wrote:
> Do you have any pointers on where I can find what happened in Mate with
> regard to blindness?

Well I am not Samuel, but I will give my answers ;)

First of all, you'd need to have compiz-reloaded version 8-16, released
two months ago to get all the enhacements, cf. for instance:
https://gitlab.com/compiz/compiz-core/blob/master/NEWS
which includes:
Introduce at-spi support for ezoom

Practically that means that a user with a low vision will have
the cursor staying in the same screen area when zooming
(e.g. a text editor or a terminal) and typing: that's the
window that moves, rather than the cursor.

Then, if you tune your keyboard shortcuts that can brink nice
accessibility key bindings cf.:
http://slackware.uk/slint/x86_64/slint-testing/source/slint-docs/accessibilty/CompizShortcuts

It is also possible to tune the configuration of marco and
compiz so the main navigation key bindings be the same, for instance:
Cycle between windows Tab
Cycle backward between windows Tab
Cycle between panels and the desktop 
Cycle backwards between panels and the desktop 

Here (next Slint) I patched org.mate.marco.gschema.xml to get
this result, cf.:
http://slackware.uk/slint/x86_64/slint-testing/source/marco/Slint_keybindings_to_cycle_windows_and_panels.diff
but I have no idea about the default settings in Debian.

Best,

Didier

Re: default desktop

[Samuel Thibault]

john doe, le ven. 08 févr. 2019 19:43:22 +0100, a ecrit:
> On 2/8/2019 7:25 PM, Samuel Thibault wrote:
> > john doe, le ven. 08 févr. 2019 19:09:39 +0100, a ecrit:
> >> On 2/8/2019 6:47 PM, Samuel Thibault wrote:
> >>> Holger Levsen, le ven. 08 févr. 2019 17:42:42 +, a ecrit:
>  On Fri, Feb 08, 2019 at 06:07:17PM +0100, Samuel Thibault wrote:
> > Re-opening the question of the default desktop just a bit to provide
> > updated information: the current gnome-with-wayland default is a concern
> > for accessibility. Accessibility on Wayland has a lot of glitches in
> > all kinds of places, and nobody is working on fixing them yet. Also,
> > MATE+Compiz now provides very nice zoom support.
> 
>  are you suggesting to change the default install or the default install
>  if accessibility boot options have been selected?
> >>>
> >>> Well, we already do the latter since years :)
> >>>
>  if the former, I think you'd need to bring this up to a wider audience.
>  (and it might also be too late), like -devel or -release.
> >>>
> >>> Well, I don't really have the time to coordinate such a discussion. Just
> >>> providing the information.
> >>>
> >>
> >> What information are you refering to?
> >
> > That now that gnome uses wayland by default, it is quite less accessible
> > than previously.
> >
> 
> If my understanding is correct, Mate will eventually favor wayland; that
> is according to (1).
> 
> 1)  https://wiki.debian.org/Wayland#Unsupported

Sure, eventually we'll have to fix Wayland issues. It just hasn't
really started yet.

Samuel

Re: default desktop

[john doe]

On 2/8/2019 7:25 PM, Samuel Thibault wrote:
> john doe, le ven. 08 févr. 2019 19:09:39 +0100, a ecrit:
>> On 2/8/2019 6:47 PM, Samuel Thibault wrote:
>>> Holger Levsen, le ven. 08 févr. 2019 17:42:42 +, a ecrit:
 On Fri, Feb 08, 2019 at 06:07:17PM +0100, Samuel Thibault wrote:
> Re-opening the question of the default desktop just a bit to provide
> updated information: the current gnome-with-wayland default is a concern
> for accessibility. Accessibility on Wayland has a lot of glitches in
> all kinds of places, and nobody is working on fixing them yet. Also,
> MATE+Compiz now provides very nice zoom support.

 are you suggesting to change the default install or the default install
 if accessibility boot options have been selected?
>>>
>>> Well, we already do the latter since years :)
>>>
 if the former, I think you'd need to bring this up to a wider audience.
 (and it might also be too late), like -devel or -release.
>>>
>>> Well, I don't really have the time to coordinate such a discussion. Just
>>> providing the information.
>>>
>>
>> What information are you refering to?
>
> That now that gnome uses wayland by default, it is quite less accessible
> than previously.
>

If my understanding is correct, Mate will eventually favor wayland; that
is according to (1).

1)  https://wiki.debian.org/Wayland#Unsupported

--
John Doe

Re: default desktop

[Samuel Thibault]

john doe, le ven. 08 févr. 2019 19:09:39 +0100, a ecrit:
> On 2/8/2019 6:47 PM, Samuel Thibault wrote:
> > Holger Levsen, le ven. 08 févr. 2019 17:42:42 +, a ecrit:
> >> On Fri, Feb 08, 2019 at 06:07:17PM +0100, Samuel Thibault wrote:
> >>> Re-opening the question of the default desktop just a bit to provide
> >>> updated information: the current gnome-with-wayland default is a concern
> >>> for accessibility. Accessibility on Wayland has a lot of glitches in
> >>> all kinds of places, and nobody is working on fixing them yet. Also,
> >>> MATE+Compiz now provides very nice zoom support.
> >>
> >> are you suggesting to change the default install or the default install
> >> if accessibility boot options have been selected?
> >
> > Well, we already do the latter since years :)
> >
> >> if the former, I think you'd need to bring this up to a wider audience.
> >> (and it might also be too late), like -devel or -release.
> >
> > Well, I don't really have the time to coordinate such a discussion. Just
> > providing the information.
> >
> 
> What information are you refering to?

That now that gnome uses wayland by default, it is quite less accessible
than previously.

Samuel

Re: default desktop

[john doe]

On 2/8/2019 6:45 PM, Samuel Thibault wrote:
> john doe, le ven. 08 févr. 2019 18:39:39 +0100, a ecrit:
>> What about Orca?
>> The last time I checked Mate, it wasn't as usable as 'Debian desktop
>> environment' (Gnome).
>
> When was that time?
> A lot of things happened on the Mate side :)
>

A fiew months back.
Do you have any pointers on where I can find what happened in Mate with
regard to blindness?

--
John Doe

Re: default desktop

[john doe]

On 2/8/2019 6:47 PM, Samuel Thibault wrote:
> Hello,
>
> Holger Levsen, le ven. 08 févr. 2019 17:42:42 +, a ecrit:
>> On Fri, Feb 08, 2019 at 06:07:17PM +0100, Samuel Thibault wrote:
>>> Re-opening the question of the default desktop just a bit to provide
>>> updated information: the current gnome-with-wayland default is a concern
>>> for accessibility. Accessibility on Wayland has a lot of glitches in
>>> all kinds of places, and nobody is working on fixing them yet. Also,
>>> MATE+Compiz now provides very nice zoom support.
>>
>> are you suggesting to change the default install or the default install
>> if accessibility boot options have been selected?
>
> Well, we already do the latter since years :)
>
>> if the former, I think you'd need to bring this up to a wider audience.
>> (and it might also be too late), like -devel or -release.
>
> Well, I don't really have the time to coordinate such a discussion. Just
> providing the information.
>

What information are you refering to?
I'm also with 'Holger Levsen' on that one.

--
John Doe

Re: default desktop

[Samuel Thibault]

Hello,

Holger Levsen, le ven. 08 févr. 2019 17:42:42 +, a ecrit:
> On Fri, Feb 08, 2019 at 06:07:17PM +0100, Samuel Thibault wrote:
> > Re-opening the question of the default desktop just a bit to provide
> > updated information: the current gnome-with-wayland default is a concern
> > for accessibility. Accessibility on Wayland has a lot of glitches in
> > all kinds of places, and nobody is working on fixing them yet. Also,
> > MATE+Compiz now provides very nice zoom support.
> 
> are you suggesting to change the default install or the default install
> if accessibility boot options have been selected?

Well, we already do the latter since years :)

> if the former, I think you'd need to bring this up to a wider audience.
> (and it might also be too late), like -devel or -release.

Well, I don't really have the time to coordinate such a discussion. Just
providing the information.

Samuel

Re: default desktop

[Samuel Thibault]

john doe, le ven. 08 févr. 2019 18:39:39 +0100, a ecrit:
> What about Orca?
> The last time I checked Mate, it wasn't as usable as 'Debian desktop
> environment' (Gnome).

When was that time?
A lot of things happened on the Mate side :)

Samuel

Re: default desktop

[Holger Levsen]

Hi Samuel,

On Fri, Feb 08, 2019 at 06:07:17PM +0100, Samuel Thibault wrote:
> Re-opening the question of the default desktop just a bit to provide
> updated information: the current gnome-with-wayland default is a concern
> for accessibility. Accessibility on Wayland has a lot of glitches in
> all kinds of places, and nobody is working on fixing them yet. Also,
> MATE+Compiz now provides very nice zoom support.

are you suggesting to change the default install or the default install
if accessibility boot options have been selected?

if the former, I think you'd need to bring this up to a wider audience.
(and it might also be too late), like -devel or -release.


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Re: default desktop

[john doe]

On 2/8/2019 6:07 PM, Samuel Thibault wrote:
> Hello,
>
> Re-opening the question of the default desktop just a bit to provide
> updated information: the current gnome-with-wayland default is a concern
> for accessibility. Accessibility on Wayland has a lot of glitches in
> all kinds of places, and nobody is working on fixing them yet. Also,
> MATE+Compiz now provides very nice zoom support.
>

What about Orca?
The last time I checked Mate, it wasn't as usable as 'Debian desktop
environment' (Gnome).

P.S. Keeping 'task...@packages.debian.org' in the loop, not sure if it
is useful.

--
John Doe

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

[Emilio Pozuelo Monfort]

On 08/02/2019 17:21, Simon McVittie wrote:
> On Fri, 08 Feb 2019 at 16:48:52 +0100, Cyril Brulebois wrote:
>> I'm not sure how to hide a particular entry on a particular arch; I'm
>> not a tasksel expert and won't be one in the next 5 minutes. But it
>> seems to me the immediate concern was about the default desktop anyway,
>> which shouldn't be an issue in the first place because of this
>> default_desktop shell function?
> 
> The immediate concern is that gjs and friends don't migrate to testing,
> because the release team's migration infrastructure asserts that all
> task packages remain installable on all release architectures, and that
> isn't true any more for task-gnome-desktop on s390x.
> 
> Do you consider it to be OK that non-default desktops can be uninstallable
> on s390x? If so, hopefully the release team can relax that check.

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.

Cheers,
Emilio

apt-setup_0.146_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 17:22:44 +0100
Source: apt-setup
Architecture: source
Version: 1:0.146
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 apt-setup (1:0.146) unstable; urgency=medium
 .
   * Team upload
 .
   * Fix missing space and superfluous colon in templates file (and sync
 translations).
 .
   [ Updated translations ]
   * German (de.po) by Holger Wansing
   * Finnish (fi.po) by Juhani Numminen
   * Hebrew (he.po) by Yaron Shahrabani
   * Kazakh (kk.po) by Baurzhan Muftakhidinov
   * Traditional Chinese (zh_TW.po) by Louies
Checksums-Sha1:
 28459619985cbe3b1bc3a39c69b026452079ba25 1863 apt-setup_0.146.dsc
 a997e2c78d2f1cb20bc7efd2aeaa036d17afbea5 252876 apt-setup_0.146.tar.xz
 e39f27b9abd83488438de8ca0d7f6394beebecf3 5832 apt-setup_0.146_amd64.buildinfo
Checksums-Sha256:
 7bceccff0de8b0002afd1e7f8b3a80157f28fbbf45bd08613abe898132a6792e 1863 
apt-setup_0.146.dsc
 154b506d86ea0ce6c3b0860ccc16f5b0195b60a27d55f29974ee4c7ad74346d6 252876 
apt-setup_0.146.tar.xz
 837d3ae188f7340911fc4386b6d8164e2de1b1996c9667d77714b0045e4044ff 5832 
apt-setup_0.146_amd64.buildinfo
Files:
 a9ad5f2650b8a653c240aae2aa866c49 1863 debian-installer optional 
apt-setup_0.146.dsc
 f654ce9d1528b1a2a3eb2d2f4c81430c 252876 debian-installer optional 
apt-setup_0.146.tar.xz
 f37a69e9052b87df983235e4455bb70a 5832 debian-installer optional 
apt-setup_0.146_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxdr/oVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2tR4P/3S1CZxvi/J/VsA0w5ah8TQOgpwe
BCCSEtr1itenw9xW8sjT+tXAE5w0sdlMqXlniHWPv80zpyrp8DCB10+qZsLXux1o
0XLNUTJQEl+Dqapu3fVywkb9Ywdi7OcMHVrVFVB+WQQ981GzsgEE/IRNIPJcM9Jv
8GU2q/pusqYtuKfkM46iTTmNWiZXf3hbIU9qslkpHNt68TLxWBqFD7JxAPO8h52s
7U081AIGDiibDod+tO05QNDssxIyNqocvOXW4VufhDjWTe2fa1cyH5A5xD/VkQOd
aGt57I3Vpm5yuvgNK1osnlgesqdviMTCcQvYCCt/CjzIH0+/fefYTHDLNwuoM6Nc
JVR/ogKkkJ/jjYtulCpiIl5SxPOlUBQMa22RJitnwM//gD5H1aoKCNrR6kQBiYxJ
6hRuBMveV2MtLYZYISJ2rED+Oxph1oloLTs9Xf5xzI6S+8GLksd0A8icLJNtXX7u
UuAXANEcxFzbkDDNJ5ekFe3FUe1ELm+8pt2ehdXqRFjSvCvmOqMigFXS52KUuba6
HidcFBKaBlxfZGrohqxwRAnXCp/5BIaJT/BW9A6TOgRt6Cv7FRjOsSXugS7VwGKE
b2x6CrjtBRO8u0aG126QuFg12TVecRMAZmaoexmWhXMir8w1o/Hc8cm/w7LQcD9m
MgsqQAxdgHiYEdED
=Nw87
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Re: default desktop

[Samuel Thibault]

Hello,

Re-opening the question of the default desktop just a bit to provide
updated information: the current gnome-with-wayland default is a concern
for accessibility. Accessibility on Wayland has a lot of glitches in
all kinds of places, and nobody is working on fixing them yet. Also,
MATE+Compiz now provides very nice zoom support.

Samuel

Processing of apt-setup_0.146_source.changes

[Debian FTP Masters]

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

Greetings,

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

cdrom-checker_1.41_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Feb 2019 16:36:01 +0100
Source: cdrom-checker
Architecture: source
Version: 1.41
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 cdrom-checker (1.41) unstable; urgency=medium
 .
   * Team upload
 .
   * Remove trailing whitespaces from changelog file, to fix lintian tag.
   * Update source URL in copyright file.
   * Fix double space in templates file (and sync translations).
Checksums-Sha1:
 7281bb9edfbf2a155bc566717159f9cf092adedc 1735 cdrom-checker_1.41.dsc
 0a5ff61764dab3efe988bea1acdaabe2dae68a5d 69620 cdrom-checker_1.41.tar.xz
 51b66db9fe4258aef35632bc63280983dc21a926 5439 
cdrom-checker_1.41_amd64.buildinfo
Checksums-Sha256:
 cc95bdcd804d2811fc216cc62b8473d6a59afb167f5a45ddbe719caab89d7e56 1735 
cdrom-checker_1.41.dsc
 cb1679dc740bdf7f1ce588842be297bb1a76aa605f7113dcbe53c03c922f41f0 69620 
cdrom-checker_1.41.tar.xz
 e1f07bf4638673ee33541ab64a84e6f2847c61ca00b9bb0fa2965f85f9c8b863 5439 
cdrom-checker_1.41_amd64.buildinfo
Files:
 56994ac8e51faf38316c58f14da0c5b6 1735 debian-installer optional 
cdrom-checker_1.41.dsc
 da0a6a31a599a45da5526f52eb39670b 69620 debian-installer optional 
cdrom-checker_1.41.tar.xz
 6639665fd32206abec2198499f27051e 5439 debian-installer optional 
cdrom-checker_1.41_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlxdqjkVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2eQYP/j3MV+2QeuOm+5GFNIhyv28lXlz7
3m7uY9Co0eyoIWqhwGyo10AVMaISZvi8FHbwyAR4TA8oMkvIimCBlLeistL5aVCY
AnfTNhVxUgRBz46nuC6lyS5AhcqL0n5Inda4RYcEZuRj8BMIDmkYIEWLGRmRo36U
AZh/QH73ID9kqLUBWAgluhDa/wwqFdeQ/oZGkyZrXp49oaD8PMs33QAuDEojcjvc
ByWYKtNfWzHMkBjbbBIYqrYjuoCPs2L02blM6a0dk+AvgrJwICcd3sbqmiq94ySF
QzzQJV9ZDYoHjguKGWYkH+eAuSk3evSP8U+TcejPVrPKMZdhHCA896sNAwdq+u+u
OCocsWJN+k3ZiC2nZBqhOKjKbAUgHoK1wIPola0klO32JIaQGvmX4YZoW65qQaET
51a4KCI7YmopI30EOqxAYF0iKF89tBpa+nKY0Y2iEPmtwpXMCkhliVNwyfrb6TN4
a4nO1/mfUf+poXhAeqSlO9QXcBeT9Knq1N5ijLNBpej1+DjuFHGXRtHG5XkdLzXK
hsrIpxAYBVtZW1pEAFYZGs3FFRH2F2iobKQk+U6tbqJUBEE3tMihTPmYxNyXb3mC
C+ESuAQdmHm6iH8MbPIpKC9UPqFUgPmLaHJQbil+9gNnUpDODia8lXnl5+LkRc8W
Zm3ahomTdJXXOYrs
=PyXg
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of cdrom-checker_1.41_source.changes

[Debian FTP Masters]

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

Greetings,

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

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

[Simon McVittie]

On Fri, 08 Feb 2019 at 16:48:52 +0100, Cyril Brulebois wrote:
> I'm not sure how to hide a particular entry on a particular arch; I'm
> not a tasksel expert and won't be one in the next 5 minutes. But it
> seems to me the immediate concern was about the default desktop anyway,
> which shouldn't be an issue in the first place because of this
> default_desktop shell function?

The immediate concern is that gjs and friends don't migrate to testing,
because the release team's migration infrastructure asserts that all
task packages remain installable on all release architectures, and that
isn't true any more for task-gnome-desktop on s390x.

Do you consider it to be OK that non-default desktops can be uninstallable
on s390x? If so, hopefully the release team can relax that check.

Thanks,
smcv

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

[Cyril Brulebois]

Hi,

Emilio Pozuelo Monfort  (2019-02-08):
> > On Thu, 17 Jan 2019 at 10:25:01 +0100, Emilio Pozuelo Monfort wrote:
> >> On 17/12/2018 15:56, Simon McVittie wrote:
> >>> The options I can see are:
> >>>
> >>> * Accept that task-gnome-desktop is not going to be installable on s390x.
> >>>   Change the testing migration scripts to skip installability testing for
> >>>   that package on s390x, or ignore the fact that it fails. Optionally
> >>>   change tasksel to make task-gnome-desktop Architecture: any, and give it
> >>>   some Build-Depends-Arch that are not satisfiable on s390x so that it 
> >>> will
> >>>   not be built there.
> >>>   - s390x d-i users will not be able to install a GNOME desktop. Hopefully
> >>> the menu item would not appear, and task-desktop would pick up the
> >>> second-preference desktop instead, which currently seems to be XFCE?
> >>>   - Risk: is it possible to ignore uninstallability of task-gnome-desktop
> >>> without ignoring uninstallability of other task packages?
> > 
> > I would prefer this option if possible: the GNOME desktop is clearly
> > not intended for use on mainframes, and I doubt anyone is seriously
> > trying to use it there (as opposed to individual GNOME apps in a
> > remote-desktop framework, which might be something that people do).
> > However, it requires action from the release team and d-i
> > maintainers.
> 
> Cyril, can we do something to not offer task-gnome-desktop on s390x?
> Does that need changes in d-i or tasksel?

FWIW we already have this in place, regarding the default desktop:
  https://salsa.debian.org/installer-team/tasksel/blob/master/default_desktop

I'm not sure how to hide a particular entry on a particular arch; I'm
not a tasksel expert and won't be one in the next 5 minutes. But it
seems to me the immediate concern was about the default desktop anyway,
which shouldn't be an issue in the first place because of this
default_desktop shell function?


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


signature.asc
Description: PGP signature

Bug#820911: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

[Samuel Thibault]

Holger Wansing, le ven. 08 févr. 2019 15:58:10 +0100, a ecrit:
> Samuel Thibault  wrote:
> > Hello,
> > 
> > Holger Wansing, le mar. 01 janv. 2019 23:40:29 +0100, a ecrit:
> > > I have played with the syslinux config for legacy BIOS mode, and as far 
> > > as I
> > > can test, it works for the netboot-gtk image, see the patch attached plus 
> > > some 
> > > new files that need to be added (for debian-installer/build/boot/x86).
> > 
> > I have reworked it and applied it.
> 
> That's great, thanks!
> 
> Regarding the documentation in the installation-guide:
> maybe we could add something about how to use the dark theme via keyboard 
> shortcuts?
> (if that's not too complex, because of differences between grub and syslinux, 
> etc.)

Done so in between :)

Samuel

Bug#820911: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

[Holger Wansing]

Hi,

Samuel Thibault  wrote:
> Hello,
> 
> Holger Wansing, le mar. 01 janv. 2019 23:40:29 +0100, a ecrit:
> > I have played with the syslinux config for legacy BIOS mode, and as far as I
> > can test, it works for the netboot-gtk image, see the patch attached plus 
> > some 
> > new files that need to be added (for debian-installer/build/boot/x86).
> 
> I have reworked it and applied it.

That's great, thanks!

Regarding the documentation in the installation-guide:
maybe we could add something about how to use the dark theme via keyboard 
shortcuts?
(if that's not too complex, because of differences between grub and syslinux, 
etc.)

Something like 
"There are also keyboard shortcuts available, to activate this: 
type 'd' + 'i' at the boot prompt for the text-based install or
'd' + 'g' for graphical installation.

Will need to investigate the exact shortcuts though...



Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

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

[Emilio Pozuelo Monfort]

Hi,

On 05/02/2019 11:16, Simon McVittie wrote:
> Please could we have a decision on this in plenty of time before the freeze?
> Given the upstream GC improvements aimed at mitigating or solving "the memory
> leak problem" in gjs 1.54.x, I am not comfortable with releasing buster with
> gjs 1.52.x (which has a backport of those changes done by a developer who does
> not have in-depth knowledge of gjs, namely me); so I would like to ask for a
> freeze exception to complete this transition.

Yes, it is my intention to finish this.

> On Thu, 17 Jan 2019 at 10:25:01 +0100, Emilio Pozuelo Monfort wrote:
>> On 17/12/2018 15:56, Simon McVittie wrote:
>>> The options I can see are:
>>>
>>> * Accept that task-gnome-desktop is not going to be installable on s390x.
>>>   Change the testing migration scripts to skip installability testing for
>>>   that package on s390x, or ignore the fact that it fails. Optionally
>>>   change tasksel to make task-gnome-desktop Architecture: any, and give it
>>>   some Build-Depends-Arch that are not satisfiable on s390x so that it will
>>>   not be built there.
>>>   - s390x d-i users will not be able to install a GNOME desktop. Hopefully
>>> the menu item would not appear, and task-desktop would pick up the
>>> second-preference desktop instead, which currently seems to be XFCE?
>>>   - Risk: is it possible to ignore uninstallability of task-gnome-desktop
>>> without ignoring uninstallability of other task packages?
> 
> I would prefer this option if possible: the GNOME desktop is clearly not
> intended for use on mainframes, and I doubt anyone is seriously trying to use
> it there (as opposed to individual GNOME apps in a remote-desktop framework,
> which might be something that people do). However, it requires action from the
> release team and d-i maintainers.

Cyril, can we do something to not offer task-gnome-desktop on s390x? Does that
need changes in d-i or tasksel?

>>> * 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 instead of gnome-session and
>>>   gnome-shell, and lightdm instead of gdm3.
>>>   - s390x users will not get the same GNOME desktop everyone else does.
>>>   - Risk: if GNOME Flashback becomes unsupportable in some future release
>>> (it's a GNOME 2 derivative a bit like MATE, although without using
>>> forks of the apps, and most upstream and downstream GNOME maintainers
>>> don't use or maintain it), we're back where we started.
> 
> With the freeze approaching fast, if we can't have a solution that requires
> action to be taken outside the GNOME team, this is probably the best thing 
> that
> the GNOME team can do unilaterally. An untested git branch for this:
> https://salsa.debian.org/gnome-team/meta-gnome3/merge_requests/3

Alternatively, this is probably the way to go.

Cheers,
Emilio

Re: Bug#921715: libgtk2.0-0-udeb: wrong dependency while building on buster based system

[Simon McVittie]

Control: reassign 921715 libxinerama1 1.1.4-1
Control: reassign 921712 libxinerama1 1.1.4-1
Control: merge 921715 921712
Control: severity 921715 serious
Control: affects 921715 + libgtk2.0-0-udeb

On Fri, 08 Feb 2019 at 09:27:20 +, Mayer, Dirk wrote:
> while building the gtk+2.0 source package on a buster based build system, the 
> resulting package libgtk2.0-0-udeb yields a wrong dependency.
> Instead of the correct dependency to the package libxinerama1-udeb it depends 
> on the wrong package libxinerama1.
> On the stretch based build system the dependency correctly refers to the udeb 
> package.

This seems to be a regression in libxinerama1 1.1.4-1. Its shlibs
metadata doesn't list a record for a udeb:

$ cat /var/lib/dpkg/info/libxinerama1:amd64.shlibs
libXinerama 1 libxinerama1

whereas other X11 udebs have an extra line for udebs, for example:

$ /var/lib/dpkg/info/libxcursor1:amd64.shlibs
libXcursor 1 libxcursor1 (>> 1.1.2)
udeb: libXcursor 1 libxcursor1-udeb (>> 1.1.2)

As a result, when gtk+2.0 is compiled, dh_shlibdeps doesn't know that
its udeb should depend on libxinerama1-udeb.

I think this is because the "--add-udeb=$(PACKAGE)-udeb" option wasn't
preserved during the rewrite of d/rules from traditional debhelper style
to dh.

I've raised this bug to serious severity, because I think it would break the
graphical installer next time gtk+2.0 is rebuilt (we've just been lucky that
the most recent gtk+2.0 upload was a few days before libxinerama1 1.1.4-1). The
X11 and d-i maintainers are of course welcome to reduce the severity if they
disagree with my assessment of its impact.

This probably also affects gtk+3.0, but I don't think debian-installer uses
that yet, so it's only a theoretical issue there.

> Duplicate to Bug #921712 because of wrong package tag
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921712

I've merged the bugs.

Thanks,
smcv