Bug#988696: installation-reports: No network management in LXDE task

2021-05-18 Thread Holger Wansing
Control: reassign -1 lxde


Hi,

Andreas Tille  wrote (Tue, 18 May 2021 10:37:12 +0200):
> I decided for the LXDE task (and unselected Gnome).  This ends up with
> no network management on the rebootet system.  My solution was wo
> plug-in the installation USB stick and install network-manager (+
> network-manager-gnome) and all its dependencies manually.  This problem
> is not only valid for this box.  I have installed three laptops in a row
> and its always the same.  My suggestion is to simply add network-manager
> to the LXDE task.

The LXDE metapackage has a Recommends on 
connman-gtk | network-manager-gnome
so connman-gtk should be installed, when choosing the LXDE task.

And I verified that it gets installed (here).

I guess, your problem was, that connman-gtk is not being started automatically
when rebooting after installation, so you don't find anything related to
network configuration in the system tray (as you might be used to).
Starting connman-gtk from the menu works though (under 'LXDE menu' -> Settings 
->
Connman Settings). 

So, as a possible way to get around this, LXDE people might want to think about
adding connman-gtk into "Autostart" under 'LXDE menu' -> Settings -> Default 
applications for LXSession, so that network management tool is automatically 
started and accessible to the user (and user are aware of such tool)...

Many people will most probably want to use network management tool on desktop 
systems.


Re-assigning to lxde people.

Holger



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



Bug#736373: using this patch with salsa & openqa

2021-05-18 Thread Philip Hands
Hi Ian,

Thanks for the patch. It's proven very useful while seting up pipelines
on salsa that can be run when a udeb's git repo is pushed, such that a
mini.iso is produced that will make use of a repository containing that
udeb.

While getting that to work, I noticed that your patch does not deal well
with the repos that aptly produces because they do not include a
Packages.xz, which means that when the Packages.xz is found in the main
repo, it stops searching the devel repo.

That being the case, I've re-jigged things a bit, as seen here:

  
https://salsa.debian.org/philh/net-retriever/-/compare/master...extra-udeb-repo?w=1

(BTW I intend to tidy up the commits there tomorrow, as they include
some false starts at present, so probably best to wait until I've done
that before using anything out of that branch)

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY



Bug#988740: unblock: glibc/2.31-12

2021-05-18 Thread Aurelien Jarno
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-gl...@lists.debian.org, debian-boot@lists.debian.org

Please unblock package glibc

[ Reason ]
This new version fixes testsuite failures when run on a kernel which has
kernel.unprivileged_userns_clone set to 1. This is the case of the
Bullseye kernel. This problem manifests itself as an FTBFS when building
the package or a failed autopkgtests.

In addition this version also fixes the display of non-ascii characters
in German debconf template. It also includes fixes from the upstream
stable branch fixing:
- a wrong assumption of available instructions on s390x in the memmove
  code which might be triggered by a kernel parameter or some older
  versions of zVM
- a fix in the way of AT_SECURE binaries are handled, which might be
  used to facilitate the exploitation of security issues in those
  binaries

[ Impact ]
If the unblock is not granted, users won't be able to build the package
from sources on a Bullseye system without using the nocheck build option
or disabling kernel.unprivileged_userns_clone. In addition users with
a German locale will have to understand the displayed text without the
non-ASCII letters.

[ Tests ]
The changes related to the testsuite actually improves the testsuite
coverage. This allowed to find an issue in the debian/rules makefile
causing the value of the --build= parameter to be wrongly empty.

The debconf changes have been tested manually on a system set to German
locale.

The upstream changes related to the AT_SECURE binaries come with
additional tests. Note that those tests actually represent the bigger
part of the debdiff.

[ Risks ]
The fixes related to the testsuite involves many changes to our build
system, by letting the upstream makefiles to install the ld.so symlink
instead of doing it in the Debian makefiles, in an architecture specific
way for bi/tri-arch packages. While the changes might look risky at a
first glance, they do not change the code in the binaries, but only the
ld.so symlinks and the libc.so linker scripts. Those have been verified
manually on the packages built by glibc and cross-toolchain-base.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
The decision to install the ld.so symlink using the Debian specific
makefiles instead of the upstream ones seems to have been taken many
years ago to avoid changing dpkg-cross. dpkg-cross has been fixed
recently in version 2.6.18+nmu1 (already in Bullseye), so this is not
an issue anymore. No conflicts or breaks against dpkg-cross have been
added as dpkg-cross is basically a .deb mangler which takes any .deb
file from the command line.

unblock glibc/2.31-12
diff -Nru glibc-2.31/debian/changelog glibc-2.31/debian/changelog
--- glibc-2.31/debian/changelog 2021-03-31 22:09:32.0 +0200
+++ glibc-2.31/debian/changelog 2021-05-01 22:56:06.0 +0200
@@ -1,3 +1,29 @@
+glibc (2.31-12) unstable; urgency=medium
+
+  * debian/po/de.po: fix encoding declaration.  Closes: #986450.
+  * debian/patches/git-updates.diff: update from upstream stable branch:
+- On s390x, check for vector support in memmove ifunc-selector in
+  addition to Miscellaneous-Instruction-Extensions.
+  * debian/patches/any/local-rtlddir-cross.diff: drop patch, letting upstream
+makefiles to install the dynamic linker symlink directly in the right
+location. This fixes the temporary installation done by upstream makefiles
+to run some tests in a container.  Closes: #973278, #985617.
+  * debian/rules.d/build.mk: do not create the dynamic linker manually.
+  * debian/sysdeps/*.mk: do not create the dynamic linker manually for
+bi/tri-arch packages.
+  * debian/rules.d/build.mk: create the soname symlink for ld-2.xx.so, to
+avoid its creation later by ldconfig.
+  * debian/debhelper.in/libc.install, debhelper.in/libc-alt.install,
+debhelper.in/libc-udeb.install, debhelper.in/libc-udeb.install.hurd-i386:
+adjust given that the dynamic linker symlink is now already at the correct
+location.
+  * debian/patches/git-updates.diff: update from upstream stable branch:
+- Fix GLIBC_TUNABLES parsing for AT_SECURE binaries.
+  * debian/rules.d/build.mk: escape EOL so that $configure_build is correctly
+passed to the configure script.
+
+ -- Aurelien Jarno   Sat, 01 May 2021 22:56:06 +0200
+
 glibc (2.31-11) unstable; urgency=medium
 
   * debian/debhelper.in/libc.preinst: handle the case where debconf
diff -Nru glibc-2.31/debian/debhelper.in/libc-alt.install 
glibc-2.31/debian/debhelper.in/libc-alt.install
--- glibc-2.31/debian/debhelper.in/libc-alt.install 2019-07-29 
11:56:57.0 +0200
+++ glibc-2.31/debian/debhelper.in/libc-alt.install 2021-04-25 
18:11:42.0 +0200
@@ -1,4 +1,5 @@
 # This file is used for biarch libraries.

Processed: Re: Bug#988696: installation-reports: No network management in LXDE task

2021-05-18 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 lxde
Bug #988696 [installation-reports] installation-reports: No network management 
in LXDE task
Bug reassigned from package 'installation-reports' to 'lxde'.
Ignoring request to alter found versions of bug #988696 to the same values 
previously set
Ignoring request to alter fixed versions of bug #988696 to the same values 
previously set

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



Bug#988696: installation-reports: No network management in LXDE task

2021-05-18 Thread Andreas Tille
Package: installation-reports
Severity: normal

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/bullseye_di_rc1+nonfree/amd64/iso-dvd/firmware-bullseye-DI-rc1-amd64-DVD-1.iso
Date: 

Machine: Lenovo X240
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [x]
Detect network card:[x]
Configure network:  [x]
Detect media:   [x]
Load installer modules: [x]
Clock/timezone setup:   [x]
User/password setup:[x]
Detect hard drives: [x]
Partition hard drives:  [x]
Install base system:[x]
Install tasks:  [x]
Install boot loader:[x]
Overall install:[x]

Comments/Problems:

I decided for the LXDE task (and unselected Gnome).  This ends up with
no network management on the rebootet system.  My solution was wo
plug-in the installation USB stick and install network-manager (+
network-manager-gnome) and all its dependencies manually.  This problem
is not only valid for this box.  I have installed three laptops in a row
and its always the same.  My suggestion is to simply add network-manager
to the LXDE task.


Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info: