Bug#874051: swami 2.0.0-svn389-5 seg faults with error 4 in libgobject-2.0.so.0.5304.0

[Arnaldo Pirrone]

Package: swami
Version: 2.0.0+svn389-5+b11
Followup-For: Bug #874051

Hi,
I can confirm the bug is still present.



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

Kernel: Linux 5.2.0-8.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages swami depends on:
ii  libc6   2.28-10
ii  libfftw3-single33.3.8-2
ii  libfluidsynth1  1.1.11-4
ii  libglib2.0-02.60.6-1
ii  libgnomecanvas2-0   2.30.3-4
ii  libgtk2.0-0 2.24.32-3
ii  libinstpatch-1.0-0  1.0.0-7
ii  libswami0   2.0.0+svn389-5+b11

Versions of packages swami recommends:
ii  jackd  5+nmu1

swami suggests no packages.

-- no debconf information

Bug#926509: Package orphaned?

[Julian Andres Klode]

On Thu, Aug 15, 2019 at 01:20:13AM +, nemo Inis wrote:
> Has this package been orphaned? It seems unlikely that a security tool such 
> as a password
> manager would lag one year behind upstream's current version?

No. We were in freeze. We are now out of freeze and I'll push out
an update to unstable soon.

> 
> Should we just call it quit and switch to the upstream AppImage?
> 
> I'm not being snarky here - this is a safety issue. A word of reassurance (or 
> of any other
> news) from the maintainer would be welcome.

If there had been a CVE, you would have gotten a security update.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#859122: 31 DLAs missing from the website

[Brian May]

Holger Levsen  writes:

> ERROR: .data or .wml file missing for DLA 145-2

Hmm. Looks like that really should exist, and point to next version
5.3.3-7+squeeze25

(DLA-145-1 points to 5.3.3-7+squeeze24)


Here is the relevant information I can find:


commit f225a141ff91e4790ef74f00893cf29c2521eff6
Author: Thorsten Alteholz 
Date:   Mon Feb 2 16:30:14 2015 +

DLA-145-1 php5 regression update

git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@31913 
e39458fd-73e7-0310-bf30-c45bca0a0e42

diff --git a/data/DLA/list b/data/DLA/list
index efe2117968..abf5a895cd 100644
--- a/data/DLA/list
+++ b/data/DLA/list
@@ -1,3 +1,5 @@
+[02 Feb 2015] DLA-145-2 php5 - regression update
+   [squeeze] - php5 5.3.3-7+squeeze25
 [31 Jan 2015] DLA-145-1 php5 - security update
{CVE-2014-0237 CVE-2014-0238 CVE-2014-2270 CVE-2014-8117}
[squeeze] - php5 5.3.3-7+squeeze24



php5 (5.3.3-7+squeeze25) squeeze-lts; urgency=high

  * Non-maintainer upload by the Squeeze LTS Team.
  * as the patch for PHP bug 68739 seems to break cURL cookie handling
it is removed again in this version, CVE-2015-TEMP-1.patch is affected
(bug report can be found in: 
 https://lists.debian.org/debian-lts/2015/02/msg7.html)

 -- Thorsten Alteholz   Mon, 02 Feb 2015 14:17:00 +0100


* https://bugs.php.net/bug.php?id=68739: upstream bug.

* https://lists.debian.org/debian-lts/2015/02/msg7.html contains
technical information on the regression.


So it looks like the fix was reverted, which means in turn means that
CVE-2015-TEMP-1 was not fixed despite DLA 145-1 declaring otherwise,
however no point worrying about that now :-)


Where to from here? Should I invent an appropriate DLA-145-2 based on
the information above?
-- 
Brian May 

Bug#934791: libgtk-3-0: complains when attempting to register already registered client

[Simon McVittie]

Control: tags -1 + moreinfo

On Wed, 14 Aug 2019 at 23:48:09 +, brian m. carlson wrote:
> GTK+ produces the following warning when attempting to register a client
> with the session manager and the client is already registered:
> 
>   (caja:3729): Gtk-WARNING **: 02:59:57.229: Failed to register client: 
> GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
> client

Under what circumstances does this occur? I see the program in question
is caja. What desktop environment is this in, and how can this bug be
reproduced?

(I assume it's either GNOME, one of the various GNOME forks, or XFCE,
based on the D-Bus APIs used in the function that contains that warning.)

I don't know the session manager API well enough to know immediately
whether this message indicates a bug in the session manager, the
application, GTK, or something else.

smcv

Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer

[Otto Kekäläinen]

Thanks Pollo if you can look into this!

Currently this also affects mariadb-10.3 in a way that no new releases
migrate to testing.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921194

Bug#872994: fuse-emulator-gtk: screen with wrong size at startup.

[Alberto Garcia]

Control: reassign 872994 fuse-emulator-gtk 1.3.8+dfsg1-1
Control: forwarded 872994 https://sourceforge.net/p/fuse-emulator/bugs/367/

> This is a problem that only happens with Wayland, and only in the
> GTK+ version of the Fuse emulator (the SDL build works fine), so I
> suspect the problem is in the Wayland backend of GTK+.

This bug hasn't been fixed yet but the problem seems to be with Fuse
after all (there's an upstream bug report about it) so I'm reassigning
it back to the fuse-emulator-gtk package.

One workaround is to force GTK to use the X11 GDK backend instead of
the Wayland one by setting the GDK_BACKEND=x11 environment variable.

I'm considering to patch Fuse with this as a temporary solution until
the actual bug is fixed.

Berto

Bug#934805: lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service)

[Simon McVittie]

Package: lintian
Version: 2.18.0
Severity: minor

Some packages contain "instanced" systemd units named like foo@.service,
which represent a family of possible systemd units foo@bar.service for
arbitrary values of bar. For example, quake2-server in contrib is one of
these: you can run any number of servers on different ports by creating
more than one configuration file and enabling multiple instances of
the unit.

This is not a feature that exists in LSB init scripts, so I don't think
maintainers can be expected to provide it. I can see two possible
improvements here:

- do not emit package-supports-alternative-init-but-no-init.d-script for
  foo@.service at all, on the basis that the feature does not exist in
  LSB init, so feature parity is not implementable

- do not emit package-supports-alternative-init-but-no-init.d-script for
  foo@.service if /etc/init.d/foo exists, on the assumption that
  /etc/init.d/foo is equivalent to one of the instances of foo@.service

If a package contains /etc/init.d/foo and foo@.service, then it should
likely also either contain foo.service (e.g. quake2-server follows this
pattern), or "mask" foo.service by making it a symlink to /dev/null to
avoid both /etc/init.d/foo and instances of foo@.service being invoked
under systemd.

Thanks,
smcv

Bug#934806: python3-scipy: test_nan_inputs hangs on hppa, riscv64, sparc64

[Drew Parsons]

Package: python3-scipy
Version: 1.3.1-1exp1
Severity: normal
Control: forwarded -1 https://github.com/scipy/scipy/issues/10656

hppa, riscv64, sparc64 are hanging on the same built-time test,
stopping at test_nan_inputs[iv]:

../../debian/python3-scipy/usr/lib/python3.7/dist-packages/scipy/special/tests/test_nan_inputs.py::test_nan_inputs[itmodstruve0]`
 PASSED [ 89%]
../../debian/python3-scipy/usr/lib/python3.7/dist-packages/scipy/special/tests/test_nan_inputs.py::test_nan_inputs[itstruve0]
 PASSED [ 89%]
../../debian/python3-scipy/usr/lib/python3.7/dist-packages/scipy/special/tests/test_nan_inputs.py::test_nan_inputs[iv]
E: Build killed with signal TERM after 600 minutes of inactivity

Since the failing test is the same on each architrecture, it suggests
this might be a scipy bug which is fixable.

Upstream has acknowledged it in Issue#10656, hopefully they'll have a
fix soon.


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

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

Versions of packages python3-scipy depends on:
ii  libatlas3-base [liblapack.so.3] 3.10.3-8
ii  libblas3 [libblas.so.3] 3.8.0-2
ii  libc6   2.28-10
ii  libgcc1 1:9.1.0-10
ii  libgfortran59.1.0-10
ii  liblapack3 [liblapack.so.3] 3.8.0-2
ii  liblbfgsb0  3.0+dfsg.3-5
ii  libopenblas-base [liblapack.so.3]   0.3.6+ds-1
ii  libquadmath09.1.0-10
ii  libstdc++6  9.1.0-10
ii  python3 3.7.3-1
ii  python3-decorator   4.3.0-1.1
ii  python3-numpy [python3-numpy-abi9]  1:1.16.2-1

Versions of packages python3-scipy recommends:
ii  g++   4:8.3.0-1
ii  g++-7 [c++-compiler]  7.4.0-10
ii  g++-8 [c++-compiler]  8.3.0-19
ii  python3-pil   6.1.0-1

Versions of packages python3-scipy suggests:
ii  python-scipy-doc  1.3.1-1exp1

-- no debconf information

Bug#923634: for fdroid build use fdroidserver from git

[Hans-Christoph Steiner]

The workaround is to use fdroidserver from git.  Running builds on the
buildserver and using `fdroid build` are currently maintained for setups
running fdroidserver from git.

Upstream welcomes contributions to make it possible everything via the
Debian packages.

Bug#934807: want warning for misplaced positional dgit options

[Ian Jackson]

Package: dgit
Version: 9.7
User: d...@packages.debian.org
Usertags: rsn

Félix Sipma writes ("Re: dgit for DM [and 1 more messages]"):
> On 2019-08-14 08:00+0100, Ian Jackson wrote:
> > Félix Sipma writes ("Re: dgit for DM [and 1 more messages]"):
> >>(~/src/khard)$ dgit sbuild --gbp 
> > 
> > The --gbp is an option to dgit.  "dgit sbuild" is followed by options
> > to sbuild.  Of course sbuild wouldn't recognise "--gbp" but dgit
> > doesn't get that far...
> > 
> > Try
> >   dgit --gbp sbuild
> 
> Thanks. I finally found it by myself but maybe it would be nice to have
> something like "Maybe you meant 'dgit --dgit-option sbuild'?" message to
> users running 'dgit sbuild --dgit-option', to give them a clue of what
> could be wrong?

This is a good idea; thanks for the suggestion.  (I trust you don't
mind me leaking your private emails to me to the BTS in this way.)

It's rather a layering violation: it means dgit has to peer into
sbuild's options.  dgit won't get this 100% right (eg, I don't think
it is sensible for dgit to try to accurately distinguish sbuild
options from values passed to those options), so dgit may become
confused.  But if the only effect is to print a warning message to
stderr, that's probably OK.

I think it's possible that dgit's code for massaging arguments to
dpkg-buildpackage (used for all the non-sbuild builders) already does
this.  That needs to be checked.

I think not all dgit options would have to be spotted, because: if
dgit's own work had succeeded and it had invoked sbuild, sbuild would
have printed a message about --gbp, making the situation reasonably
obvious.  And short options are too ambiguous.  So I don't propose to
somehow reuse dgit's own option parser code (or table-ify it).  We'll
just have an ad-hoc list of things to warn about.  To be clear an
option should be included if
  - it might avert an error which prevents dgit from running sbuild
 (eg quilt options, --ignore-dirty)
  - it might avert processing which dgit does before running sbuild
 but which the user presumably didn't intend (eg --dry-run, -w*)
(For sbuild, read "the builder".)

Tagging this rsn because I think it is a fairly easy useability
improvement, if done in the ad-hoc way I propose above.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#932673: docker.io: CVE-2019-13509

[Arnaud Rebillout]

On 8/13/19 12:31 PM, Salvatore Bonaccorso wrote:

The severity does indeed not need to imply that or a no-dsa
necessarily. In this concrete case we have already marked the issue as
no-dsa though:
https://security-tracker.debian.org/tracker/CVE-2019-13509


Thanks for the link! I thought the no-dsa would show up as a tag on the 
bugtracker. Now I now where to look, thanks.

Bug#934808: kbackup's docbook handbook files cannot be read by khelpcentre

[Rik Mills]

Package: kbackup
Version: 18.12.1-1
Version: 19.04.3-1

kbackup build gzips the produced .docbook files, meaning khelpcentre
cannot read them and reports the docs as missing.

Reproduce with 'Help > Help Centre Handbook' or by pressing F1 in kbackup

In debian/rules the package is built with simple dh $@

Additionally passing '--with kf5' to dh should ensure the .docbooks are
not compressed, so can be found and read by khelpcentre

Bug#918276: (no subject)

[Сергей Фёдоров]

Vlc 3.0.3-1-0+deb9u1 works fine in Debian
Vlc 3.0.6-0+deb9u1 in Debian 9.9 Stretch Stable works fine
All other versions of Vlc, including 3.0.7.1-3 when opening media files
instantly hang Debian, so no log-files do not have time to form.

When I install Debian-64 10 Stable, it is installed by default
"parole 1.0.2-1", not VLC, which is suggestive.

Removed "parole 1.0.2-1" and installed packages:

lua5.2   5.2.4-1.1+b3

qt5-default  5.11.3+dfsg1-3
libqt5core5a 5.11.3+dfsg1-3
libqt5gui5   5.11.3+dfsg1-3
libqt5svg5-dev   5.11.3-2
libqt5widgets5   5.11.3+dfsg1-3
libqt5x11extras5-dev 5.11.3-2

libcairo2-dev1.16.0-4
libegl1  1.1.0-1
libgl1   1.1.0-1
libgles2 1.1.0-1
libva-drm2   2.5.0-1
libva-dev2.5.0-1
libva2   2.5.0-1
libva-x11-2  2.5.0-1
libwayland-dev   1.17.0-1
libwayland-client0   1.17.0-1
libwayland-egl1  1.17.0-1
libx11-dev   2:1.6.7-1
libx11-6 2:1.6.7-1

libjpeg62-turbo-dev  1:1.5.2-2+b1
libpng16-16  1.6.37-1
librsvg2-dev 2.44.14-1
libfontconfig1-dev   2.13.1-2
libfreetype6-dev 2.9.1-4
libfribidi-dev   1.0.5-3.1

liblua5.25.2.4-1.1+b3
liblua5.2-dev5.2.4-1.1+b3

liba52-0.7.4-dev 0.7.4-19
libavutil-dev7:4.1.4-1+b1
libavcodec-dev   7:4.1.4-1+b1
libavformat-dev  7:4.1.4-1+b1
libmatroska-dev  1.5.2-2
libmpeg2-4-dev   0.5.1-8
libmpg123-dev1.25.10-2
libogg-dev   1.3.2-1+b1
libopus-dev  1.3-1
libpostproc-dev  7:4.1.4-1+b1
libswscale-dev   7:4.1.4-1+b1
libtheora-dev1.1.1+dfsg.1-15

libxcb-composite0-dev  1.13.1-2
libxcb-keysyms1-dev0.4.0-1+b2
libxcb-randr0-dev  1.13.1-2
libxcb-xv0-dev 1.13.1-2
libxcb1-dev1.13.1-2

libass-dev   1:0.14.0-2
libaribb24-dev   1.0.3-2

Created a folder, entered it, unzipped the source archive
vlc-3.0.7.1.tar.xz.

And run the following commands:

./configure

If you need to reinstall VLC, and "make clean" gives error 2, it is necessary
remove the source folder and reinstall it from the archive, then make
goes well.

make -j&(nprocs)
sudo make install
ldconfig

And it worked. What is the problem, I have not found.


01.03.2019, 20:33, "Sebastian Ramacher" :
> Hi
>
> On 2019-02-26 12:17:30, Сергей Фёдоров wrote:
>>  Installed Debian 9.8 amd64 from scratch. In it in "stable" vlc 
>> 3.0.6-0+deb9u1
>>  works fine, but if you install vlc 3.0.6-1 from sid, when you open
>>  any video file Debian freezes and only the mouse cursor moves across the 
>> screen.
>>  I.e. everything in Debian to 9.6. In Debian 9.6, amd64 worked fine in
>>  "stable" vlc 3.0.3-1-0+deb9u1, and if you install vlc 3.0.5-1 from "sid", 
>> then when
>>  open any *.mp4 file Debian hangs on the screen and moves the cursor
>>  mice.
>
> We really need those logs. And when you upgraded to vlc from sid, did you 
> upgrade the rest of your
> system as well?
>
>>  If it does not open the video file, vlc --version, then it will report:
>>  VLC media player 3.0.6 Vetinari (revision 3.0.6-0-g5803e85f73)
>>  VLC version 3.0.6 Vetinari (3.0.6-0-g5803e85f73)
>>  Compiled by buildd on x86-ubc-01.debian.org (Jan 10 2019 19:03:32)
>>  Compiler: gcc version 8.2.0 (Debian 8.2.0-14)
>>  This program comes with NO WARRANTY, to the extent permitted by law.
>>  You may redistribute it under the terms of the GNU General Public License;
>>  see the file named COPYING for details.
>>  Written by the VideoLAN team; see the AUTHORS file.
>>
>>  I. e. not 3.0.6-1, but 3.0.6-0, which looks suspicious.
>
> Nothing suspicious here. That's just what git describe produces as version 
> information for the 3.0.6
> tag.
>
> Cheers
> --
> Sebastian Ramacher

Bug#934809: opus 1.3.1 available

[Sebastien Bacher]

Package: opus
Version: 1.3-1

There is a new bugfix version available, could you update the Debian
package?
http://www.opus-codec.org/release/stable/2019/04/12/libopus-1_3_1.html

Thanks,

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

[Mark Hindley]

On Tue, Aug 13, 2019 at 04:46:32PM +0200, Thorsten Glaser wrote:
> But TTBOMK it is possible to install sysvinit alongside systemd,
> then reboot and select sysvinit as “alternative” init from the
> GRUB menu, then remove everything else. Now that I see /sbin/init
> is part of sysvinit-core, I wonder if this is really possible any
> more and, if not, why not… packages are not supposed to depend on
> systemd-sysv… (but, ouch, libpam-systemd does).

Can you point me to any official documentation that says packages should not
depend on systemd-sysv?

Thanks.

Mark

Bug#931806: your mail

[Tobias Frost]

[Dropping the mia alias from CC on puropse]

Hi Thomas,

sorry for the late reply, DebConf and other stuff came into the way ;-)

On Sat, Jul 13, 2019 at 05:44:51PM -0400, Thomas Ward wrote:
> Tobias, et. al:
> 
> On 7/13/19 2:17 PM, Thomas Ward wrote:

(...)

> Note that these changes and this repository, as well as my use of the
> gbp workflow thus far, I am going to be basing the remainder of my ITS
> and the packaging I will be uploading to Mentors for sponsoring to
> here.  At that time, the ITS will be 'waiting' for further movement.

Ok, I see the package on mentors, but I do not see the changes on the
git repository. (You should not be afraid to push them even if review is
not done) Note that I did not take a look at the package itself, so I
can't say about quality. (It is marked as NOT needing a sponsor anyway)

(If you need a sponsor, you want to file a RFS bug against the
sponsorship-requests pseudo-package, so that the review can happen in the open
and it also increases changes that you'll find a sponsor)

> Only two remaining questions for this before I move forward with
> updating the Salsa repository with further changes (or the preferred way
> I would be doing to get a second set of eyes on the changes, a pull
> request from my own namespace in for all three branches). As I am
> currently not the specified maintainer for this package, and given that
> I have filed this ITS:
> 
> (1) should I write the changelog entries from the perspective of an NMU
> or as if I am the maintainer/co-maintainer of the repository?

The ITS changes ownership of the package, so it is not an NMU. 
The change needs to be documented in the changelog. So you would write
something like
 - New Maintainer (Closes #ITS-Bug)  and change d/control accordingly.
as maybe the first or second entry of the changelog

> (2) Should the Uploaders field be updated in the process as well to
> include myself as well, or should I let that be handled at a later point
> in time by the MIA team or by another DD?

You want to have d/control reflect "reality", so please remove the old
maintainer(s).

> 
> Thomas
> 
-- 
Cheers,
tobi


signature.asc
Description: PGP signature

Bug#934810: aspell 0.60.7 available

[Sebastien Bacher]

Package: aspell
Version: 0.60.7~20110707-6

There is a new bugfix version available, could we get it uploaded to Debian?
http://aspell.net/aspell-0.60.7.txt

Thanks!

Bug#931873: [tlbuild] Core dump with image inclusion inside LuaTeX on Sparc Solaris

[Hilmar Preuße]

Am 15.08.2019 um 02:02 teilte John Paul Adrian Glaubitz mit:

Hi Adrian,

> @Hilmar:
> 
> If you patch texk/web2c/luatexdir/luapplib/{ppconf.h,ppheap.c,util/utilarm.h} 
> to
> replace "( defined(__sun) && defined(__SVR4))" with "defined __sparc", the 
> problem
> should be fixed on Debian sparc64.
> 
Many thanks for the patch [1]. Do you want me to do something? I could
try to build the package using the patch on Sparc64, however I'm pretty
sure you did that already. If you want me to do another build please
install the missing BD's on gcc202.

libbrotli-dev libgd-dev libgs-dev libpaper-dev libpotrace-dev (>= 1.11)
libteckit-dev libwoff-dev libxxhash-dev libzzip-dev (>= 0.12)

Many thanks,
  Hilmar

[1]
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=931873;filename=sparc64-fix-alignment.patch;msg=60
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#934811: webrtc-audio-processing 0.3.1 available

[Sebastien Bacher]

Package: webrtc-audio-processing
Version: 0.3-1 

There is a new 0.3.1 version available since July 2018, it includes some
simple build and documentation fixes, would be nice to have it uploaded
to Debian
http://freedesktop.org/software/pulseaudio/webrtc-audio-processing/webrtc-audio-processing-0.3.1.tar.xz

Thanks

Bug#933534: www.debian.org: missing link to /security/2019/dsa-4483.es.html in /security/2019/dsa-4483.en.html

[Rafa]

Hi,

On Wed, Jul 31, 2019 at 11:36:26AM +0200, Rafa wrote:
> Package: www.debian.org
> Severity: normal
> 
> Dear Maintainers,
> 
> [...]
> However, for some reason that escapes me, the page with the original
> english version (https://www.debian.org/security/2019/dsa-4483.en.html)
> does not cointain the usual link to the Spanish version in its footer.
> [...]

It is fixed. I don't know when or how it was fixed but, anyway, today (15
Aug 2019) I have noticed that the missing link is already in place.

So, I think that this bug can be closed.

Thanks,

Rafa.



signature.asc
Description: PGP signature

Bug#934812: python3.7: please enable optimizations for arm64, too

[Josua Mayer]

Package: python3.7
Version: 3.7.3-2
Severity: wishlist
Tags: patch

Dear Maintainer,

Please enable LTO and PGO for arm64 builds of python.
These optimizations area already enabled for an exhaustive list of 
architectures,
including the slowest of arm.

Please find attached a small patch extending the list of architectures for both 
pgo and lto.

Yours sincerely
Josua Mayer


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.1.0-trunk-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3.7 depends on:
ii  libpython3.7-stdlib  3.7.3-2
ii  mime-support 3.62
ii  python3.7-minimal3.7.3-2

python3.7 recommends no packages.

Versions of packages python3.7 suggests:
ii  binutils2.31.1-16
pn  python3.7-doc   
pn  python3.7-venv  

-- no debconf information
diff --git a/debian/rules b/debian/rules
index a43e5dd..6b1b34c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -171,13 +171,13 @@ endif
 
 ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
   ifeq ($(DEB_HOST_ARCH_OS),linux)
-ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc 
ppc64 ppc64el s390x))
+ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 
powerpc ppc64 ppc64el s390x))
   with_pgo := yes
 endif
   endif
 endif
 
-ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64 
ppc64el s390x))
+ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 powerpc 
ppc64 ppc64el s390x))
   with_lto := yes
 endif
 
diff --git a/debian/rules b/debian/rules
index a43e5dd..6b1b34c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -171,13 +171,13 @@ endif
 
 ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
   ifeq ($(DEB_HOST_ARCH_OS),linux)
-ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc 
ppc64 ppc64el s390x))
+ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 
powerpc ppc64 ppc64el s390x))
   with_pgo := yes
 endif
   endif
 endif
 
-ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64 
ppc64el s390x))
+ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 powerpc 
ppc64 ppc64el s390x))
   with_lto := yes
 endif
 

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

[Mark Hindley]

Thanks for everybody's input with this thorny issue.

I am now wondering if the prime responsibliity for the system breakage here is
down to apt's behaviour.

On Sun, Aug 11, 2019 at 03:31:00PM +0100, Simon McVittie wrote:
> Actual result (transcript below):
> 
> * systemd-sysv is removed
> * sysvinit-core is unpacked
> * systemd is also removed
> * systemd's prerm fails because it is still the active init system
>   (this check is present since Debian systemd commit c3f5f249 in 44-6,
>   released in 2012 - it appears the intention is that anyone wishing to
>   switch from systemd to sysvinit should replace systemd-sysv with
>   sysvinit-core, then reboot into sysvinit, and only (auto)remove
>   systemd after that reboot)

At this point apt has failed to remove systemd/241-7 which depends on libsystemd
(=241-7). Surely it should not then go on to try and remove the systemd
dependency? libelogind0 provides libsystemd0 (=241.3) so could never satisfy
that requirement.

> * libsystemd0 is removed anyway

That is wrong and breaks systemd, never mind apt…

Am I missing something?

Mark

Bug#930526: incron creates zombie processes

[Herman van Rink]

I'm also seeing this after a buster upgrade.

Applying this patch and rebuilding the package seems to have done the trick

-- 

Met vriendelijke groet / Regards,

Herman van Rink
Initfour websolutions

Bug#933002: docker.io: CVE-2019-13139

[Arnaud Rebillout]

On 8/13/19 12:35 PM, Salvatore Bonaccorso wrote:

On Tue, Aug 13, 2019 at 11:31:41AM +0200, Arnaud Rebillout wrote:

This is fixed in unstable.

Thanks!



Oh well, not fixed in unstable yet actually, as the package doesn't 
build anymore due to changes in the dependency tree...




This one is marked as no-dsa. But if something is not yet marked it
can as well mean we simply have not assessed it for buster or stretch.
Feel free to CC the security team alias when unsure.

For getting packages via a point release there are some steps outlined
here:
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable

When involving security some guidelines are given at
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#s5.6.4
and
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#bug-security



Thanks for all the references!


  Arnaud

Bug#931873: [tlbuild] Core dump with image inclusion inside LuaTeX on Sparc Solaris

[John Paul Adrian Glaubitz]

Hi Hilmar!

> On Aug 15, 2019, at 11:49 AM, Hilmar Preuße  wrote:
> 
> Many thanks for the patch [1]. Do you want me to do something? I could
> try to build the package using the patch on Sparc64, however I'm pretty
> sure you did that already. If you want me to do another build please
> install the missing BD's on gcc202.

The patch fixes the problem for me. I just did a test build on the Debian 
porterbox „kyoto“ and the testsuite passes without any problems now.

So, it would be great if you could upload a new version with the patch included 
as soon as possible as the broken texlive-bin package blocks a lot of other 
packages on sparc64.

For upstream, I just suggest replacing „defined __sun && defined __SVR4“ with 
„defined __sparc“ as suggested earlier in this thread.

Adrian

Bug#932594: rkhunter: SCRIPTWHITELIST change to /usr/bin/egrep causes failure if usrmerge has not been run

[John Horne]

On Sun, 21 Jul 2019 02:00:30 +0100 Julian Gilbey  wrote:
> Package: rkhunter
> Version: 1.4.6-7
> Severity: important
>
> Hi!
>
> Unfortunately the fix for bug #931396 fixes machines which have run
> usrmerge.  But for those which have not, rkhunter now fails fatally:
>
> erdos:~ # /usr/share/rkhunter/scripts/rkhupd.sh
> Invalid SCRIPTWHITELIST configuration option: Non-existent pathname:
/usr/bin/egrep
> Invalid SCRIPTWHITELIST configuration option: Non-existent pathname:
/usr/bin/fgrep
> erdos:~ #
>
> I don't know whether there is a way of saying "whitelist this script
> if it is found, otherwise ignore it".  If there is, then this should
> be applied to both /usr/bin/egrep and /bin/egrep, and likewise for
> fgrep and any other /bin/... scripts.  If not, then I don't know what
> to suggest.
>
Take a look at the EXISTWHITELIST config option - it may do what you want.


John.

--
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK

[http://www.plymouth.ac.uk/images/email_footer.gif]

This email and any files with it are confidential and intended solely for the 
use of the recipient to whom it is addressed. If you are not the intended 
recipient then copying, distribution or other use of the information contained 
is strictly prohibited and you should not rely on it. If you have received this 
email in error please let the sender know immediately and delete it from your 
system(s). Internet emails are not necessarily secure. While we take every 
care, University of Plymouth accepts no responsibility for viruses and it is 
your responsibility to scan emails and their attachments. University of 
Plymouth does not accept responsibility for any changes made after it was sent. 
Nothing in this email or its attachments constitutes an order for goods or 
services unless accompanied by an official order form.

Bug#934814: libdballe7: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Package: libdballe7
Control: affects -1 mariadb-10.3

Hello!

The current version of this package in unstable is quite old and has
been built against libmariadbclient18, which no longer exists in
Debian unstable (superceeded by libmariadb3).

This affects mariadb-10.3 which cannot currently migrate form Debian
unstable to Debian testing due to this old package stopping it with
its outdated run-time dependency.

Please consider making a new upload of this package so that the
run-time dependencies update.

Bug#934813: gajim: GPG agent option cannot be enabled

[Timur Irikovich Davletshin]

Package: gajim
Version: 1.1.2-2
Severity: normal

Dear Maintainer,

1. GPG agent cannot be enabled.
2. Known bug
3. Please backport one line fix to Debian 10 (Buster)
https://dev.gajim.org/gajim/gajim/commit/0dbcac4efebfa76db9bf2c4c68bf95859dda25be

Thank you very much in advance,

Timur.



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gajim depends on:
ii  gir1.2-gtk-3.0   3.24.5-1
ii  python3  3.7.3-1
ii  python3-cssutils 1.0.2-2
ii  python3-gi   3.30.4-1
ii  python3-gi-cairo 3.30.4-1
ii  python3-idna 2.6-1
ii  python3-keyring  17.1.1-1
ii  python3-nbxmpp   0.6.10-1
ii  python3-openssl  19.0.0-1
ii  python3-precis-i18n  1.0.0-1

Versions of packages gajim recommends:
ii  alsa-utils 1.1.8-2
ii  aspell-en [aspell-dictionary]  2018.04.16-0-1
ii  aspell-ru [aspell-dictionary]  0.99g5-23
ii  ca-certificates20190110
ii  dbus   1.12.16-1
ii  fonts-noto-color-emoji 0~20180810-1
ii  gajim-omemo2.6.27-1
ii  gajim-pgp  1.2.24-1
ii  gir1.2-farstream-0.2   0.2.8-4.1
ii  gir1.2-geoclue-2.0 2.5.2-1
ii  gir1.2-gspell-11.6.1-2
ii  gir1.2-gst-plugins-base-1.01.14.4-2
ii  gir1.2-gstreamer-1.0   1.14.4-1
ii  gir1.2-gupnpigd-1.00.2.5-3
ii  gir1.2-secret-10.18.7-1
ii  gnome-shell [notification-daemon]  3.30.2-9
ii  gstreamer1.0-plugins-ugly  1.14.4-1
ii  notification-daemon3.20.0-4
ii  pulseaudio-utils   12.2-4
ii  python3-crypto 2.6.1-9+b1
ii  python3-dbus   1.2.8-3
ii  python3-gnupg  0.4.4-1
ii  python3-pil5.4.1-2

Versions of packages gajim suggests:
ii  avahi-daemon  0.7-4+b1
ii  libxss1   1:1.2.3-1
ii  nautilus-sendto   3.8.6-3
pn  python3-kerberos  
ii  python3-pycurl7.43.0.2-0.1

-- no debconf information

Bug#934815: mosquitto-auth-plugin: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Package: mosquitto-auth-plugin
Control: affects -1 mariadb-10.3

Hello!

The current version of this package in unstable is quite old and has
been built against libmariadbclient18, which no longer exists in
Debian unstable (superceeded by libmariadb3).

This affects mariadb-10.3 which cannot currently migrate form Debian
unstable to Debian testing due to this old package stopping it with
its outdated run-time dependency.

Please consider making a new upload of this package so that the
run-time dependencies update.

Bug#934816: tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Package: tcl8.6-tdbc-mysql
Control: affects -1 mariadb-10.3

Hello!

The current version of this package in unstable is quite old and has
been built against libmariadbclient18, which no longer exists in
Debian unstable (superceeded by libmariadb3).

This affects mariadb-10.3 which cannot currently migrate form Debian
unstable to Debian testing due to this old package stopping it with
its outdated run-time dependency.

Please consider making a new upload of this package so that the
run-time dependencies update.

Bug#934817: libmysql++3v5: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Package: libmysql++3v5
Control: affects -1 mariadb-10.3

Hello!

The current version of this package in unstable is quite old and has
been built against libmariadbclient18, which no longer exists in
Debian unstable (superceeded by libmariadb3).

This affects mariadb-10.3 which cannot currently migrate form Debian
unstable to Debian testing due to this old package stopping it with
its outdated run-time dependency.

Please consider making a new upload of this package so that the
run-time dependencies update.

Bug#934818: libquickfix16: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Package: libquickfix16
Control: affects -1 mariadb-10.3

Hello!

The current version of this package in unstable is quite old and has
been built against libmariadbclient18, which no longer exists in
Debian unstable (superceeded by libmariadb3).

This affects mariadb-10.3 which cannot currently migrate form Debian
unstable to Debian testing due to this old package stopping it with
its outdated run-time dependency.

Please consider making a new upload of this package so that the
run-time dependencies update.

Bug#934819: stardict-tools: built with libmariadbclient18, which doesn't exist any longer

[Otto Kekäläinen]

Package: stardict-tools
Control: affects -1 mariadb-10.3

Hello!

The current version of this package in unstable is quite old and has
been built against libmariadbclient18, which no longer exists in
Debian unstable (superceeded by libmariadb3).

This affects mariadb-10.3 which cannot currently migrate form Debian
unstable to Debian testing due to this old package stopping it with
its outdated run-time dependency.

Please consider making a new upload of this package so that the
run-time dependencies update.

Bug#929696: Upgrading PSToedit fixes this

[D Haley]

Hi,

I experienced the same problem. Manually rebuilding and installing
pstoedit-3.74-1 fixed the problem for me.

Currently 3.74 is stuck in unstable.

Bug#934817: libmysql++3v5: built with libmariadbclient18, which doesn't exist any longer

[Roberto C . Sánchez]

On Thu, Aug 15, 2019 at 01:52:18PM +0300, Otto Kekäläinen wrote:
> Package: libmysql++3v5
> Control: affects -1 mariadb-10.3
> 
> Hello!
> 
> The current version of this package in unstable is quite old and has
> been built against libmariadbclient18, which no longer exists in
> Debian unstable (superceeded by libmariadb3).
> 
> This affects mariadb-10.3 which cannot currently migrate form Debian
> unstable to Debian testing due to this old package stopping it with
> its outdated run-time dependency.
> 
> Please consider making a new upload of this package so that the
> run-time dependencies update.

I will be preparing an upload of the latest upstream release (3.2.5) in
the next days.  I will make sure to address this and the other
outstanding bugs at that time.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#435901: rdiff --paranoia produces (spurious?) critical errors

[Donovan Baarda]

Thanks for reporting this.

This should not be happening. It's unlikely to cause any corruption (which
would require a strong-sum collision), but it might be indicating a rollsum
bug that could be causing delta calculation to miss some matches, resulting
in a larger delta than it should.

I was just considering removing the --paranoia setting because I thought
the delta code in librsync was pretty mature and we didn't need it any more.

I filed an upstream bug against librsync and will investigate/fix;

https://github.com/librsync/librsync/issues/155

-- 
Donovan Baarda 

Bug#934721: sbuild: Lintian run via sbuild produces different output than running lintian manually with the same options

[Johannes Schauer]

Hi Bill,

Quoting Bill Blough (2019-08-15 03:43:51)
> I've had a chance to do some more exploration.
> 
> Lintian is indeed getting run with a different .changes file than what
> is output to screen/disk.
> 
> The package build creates a changes file in the temporary 
> that contains a Distribution of UNRELEASED.  This happens even if the
> distribution is specified with -d.
> 
> The .changes file later gets written to BUILD_DIR, with the Distribution
> field set to what was specified by -d.
> 
> However, lintian is run against the original (Dist: UNRELEASED) .changes
> file left in , not the modified version written in BUILD_DIR.
> 
> It seems to me that lintian should be run against the modified .changes
> file that is provided to the user after the build, rather than the
> leftover one in  that is different.

I agree. The lintian checks done by sbuild should be carried out on the same
artifacts as they are created by sbuild outside of the chroot.

> Also, after the new .changes file is written, there's an attempt to delete
> the old one in , but it seems to fail silently.  So I assume this
> is a bug, rather than an intentional choice. (Also, the variables in question
> are very similarly named, so I think it would be an easy mistake to make).

I assume you are referring to this unlink call?

https://sources.debian.org/src/sbuild/0.78.1-2/lib/Sbuild/Build.pm/#L2620

> I've attached a small patch that makes it use the modified .changes file
> instead of the unmodified one.  On my system, this makes it behave as I would
> expect.  That is, lintian run via sbuild behaves the same way as lintian run
> manually, since they're now using the exact same .changes file.

that your patch works for you is coincidental. By using
$self->get_conf('BUILD_DIR') instead of $self->get('Build Dir') you will end up
using the output directory of the build artifacts *outside* the chroot. See the
documentation for the BUILD_DIR config option in sbuild.conf(5). That it works
for you might mean that you have set up your chroots in a way such that lintian
inside the chroot has access to the path outside of it. Maybe you are building
in /tmp and have that mounted inside as well, for example?

If you would like to prepare a patch that fixes this issue, then what should
actually happen is probably that the "copy_changes()" subroutine modifies the
.changes files inplace inside the chroot so that when Lintian is called later,
it sees the same files as the ones that get copied to the outside by
"copy_changes()".

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#934761: exim4: 2) Callout timeout in recipient verify can result in the lost of the TLS incoming connexion

[Andreas Metzler]

Control: forwarded -1 https://bugs.exim.org/show_bug.cgi?id=2431

On 2019-08-14 Martin Duspiva  wrote:
> Package: exim4
> Version: 4.92-8+deb10u1~bpo9+1
> Severity: normal
> Tags: upstream

> Dear Maintainer,

> I think that the bug #887489, which is already archived, is still
> persist.  I have Debin 9 with backported Exim4 ( 4.92-8+deb10u1~bpo9+1
> ) and the callout funciton in rcpt acl has  as the same bad behavior
> as described in bug #887489.
[...]

Hello,

I have forwarded the issue to the upstream bug tracking system.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#934820: consider review and merge of linux-hardened patches (free, Libre alternative to grsecurity)

[Patrick Schleizer]

Package: linux
Severity: wishlist
X-Debbugs-CC: whonix-de...@whonix.org

Dear maintainer,

Could you please consider review and merge of linux-hardened patches
(free, Libre alternative to grsecurity).

https://github.com/anthraxx/linux-hardened

Alternatively perhaps as a separate package.

RFP: linux-hardened - hardened Linux kernel

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934751

Kind regards,
Patrick

Bug#934821: fcm: usr/bin/fcm_test_battery uses invalid interpreter (/usr/bin/bash instead of /bin/bash)

[Niels Thykier]

Package: fcm
Version: 2019.05.0-1
Severity: serious

Hi,

Found by lintian and confirmed manually; the fcm_test_battery script
installed into the default PATH uses /usr/bin/bash as interpreter.
This only works on /usr-merged systems.  However, Debian systems
cannot be assumed to have been /usr-merged.

"""
#!/usr/bin/bash
#---
# Copyright (C) 2006-2019 British Crown (Met Office) & Contributors.
#
"""

Thanks,
~Niels

Bug#934822: debian-installer: include free firmware-ath9k-htc

[John Scott]

Package: debian-installer
Severity: normal
Tags: d-i
Control: block -1 by 900171 931283

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

firmware-ath9k-htc includes firmware for some of the few Wi-Fi USB
dongles that work without non-free software. In particular, all dongles
supporting 802.11n that are Respects Your Freedom certified require this.
Its inclusion would make installing Debian easier for me.

- -- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iHUEARMIAB0WIQQd3xxna2VescxVfdXYKFckL7guMwUCXVVKkAAKCRDYKFckL7gu
M1MLAP4tJhGfxnvjshgTCxNMqnX1S9z3LTRo8sNypjKrM3+JnwD6A8WnB5rsueDL
dFecnQzTxMLH1tAP4ARiOEWSRJSv2Hs=
=yU+o
-END PGP SIGNATURE-

Bug#934823: glibc needs an update for linux-5.2 kernel headers (alpha)

[Matthias Klose]

Package: src:glibc
Version: 2.28-10
Severity: sersious
Tags: sid bullseye patch

currently c-t-b-p ftbfs on alpha. A patch needs to be backported.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836064

the c-t-b-ports package ftbfs:

/bin/bash ../scripts/move-if-change
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h
touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp
if test -r /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new;
then mv -f /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \
else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi
In file included from :1:
../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" redefined
[-Werror]
 #define __NR_osf_shmat 209

In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24,
 from ../sysdeps/unix/sysdep.h:20,
 from ../sysdeps/unix/alpha/sysdep.h:19,
 from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29,
 from :1:
/<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the
location of the previous definition
 #define __NR_osf_shmat __NR_shmat

cc1: all warnings being treated as errors

a definition of __NR_osf_shmat was added during the 5.1 cycle:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=12b57c5c70f397a9410411d4e348096edada20f9

Looks like a fix has been applied to upstream glibc:

https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d5ecee822e72a2fd156338ab2be2f2e70a1da55a

Bug#934721: sbuild: Lintian run via sbuild produces different output than running lintian manually with the same options

[Bill Blough]

On Thu, Aug 15, 2019 at 01:38:48PM +0200, Johannes Schauer wrote:
> 
> > Also, after the new .changes file is written, there's an attempt to delete
> > the old one in , but it seems to fail silently.  So I assume this
> > is a bug, rather than an intentional choice. (Also, the variables in 
> > question
> > are very similarly named, so I think it would be an easy mistake to make).
> 
> I assume you are referring to this unlink call?
> 
> https://sources.debian.org/src/sbuild/0.78.1-2/lib/Sbuild/Build.pm/#L2620

Yes.

> 
> > I've attached a small patch that makes it use the modified .changes file
> > instead of the unmodified one.  On my system, this makes it behave as I 
> > would
> > expect.  That is, lintian run via sbuild behaves the same way as lintian run
> > manually, since they're now using the exact same .changes file.
> 
> that your patch works for you is coincidental. By using
> $self->get_conf('BUILD_DIR') instead of $self->get('Build Dir') you will end 
> up
> using the output directory of the build artifacts *outside* the chroot. See 
> the
> documentation for the BUILD_DIR config option in sbuild.conf(5). That it works
> for you might mean that you have set up your chroots in a way such that 
> lintian
> inside the chroot has access to the path outside of it. Maybe you are building
> in /tmp and have that mounted inside as well, for example?

You're right.  I forgot that for troubleshooting purposes I modified my schroot
to mount my homedir. Good catch.

> 
> If you would like to prepare a patch that fixes this issue, then what should
> actually happen is probably that the "copy_changes()" subroutine modifies the
> .changes files inplace inside the chroot so that when Lintian is called later,
> it sees the same files as the ones that get copied to the outside by
> "copy_changes()".

Sure.  I'll see what I can do.

Thanks.

Bill

Bug#934690: networkmanager does not parse interface config file correctly

[andreimpopescu]

On Mi, 14 aug 19, 15:18:15, Hans-Cees Speel wrote:
> On 13-08-19 21:15, andreimpope...@gmail.com wrote:
> > 
> > Raspbian is making several changes compared to a pristine Debian system.
> > Combine this with images being produced by third parties, with possible
> > additional customizations and it becomes impossible to diagnoze an issue
> > from Debian perspective.
> > 
> > Please kindly report bugs in Debian only if you can reproduce the
> > behaviour with a pure Debian install.
> > 
> > I would suggest you contact Raspbian support channels to find a solution
> > to your problem and if this is indeed a bug report it to Raspbian.
> 
> While I respect your difficulties from the debian perspective:

Please note I'm only triaging bugs filed against unknown packages.
 
>  * some more info would be welcome. Is my assertion correct that given
>my configuration file form netwerokmanager resolv.conf should only
>have one dns-address. If this is not the case my and your time is
>wasted to find out more

The file /etc/resolvconf/resolv.conf.d/head in Debian stretch looks like 
this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN


You can verify that yourself by downloading the package from a Debian 
mirror and inspecting it, e.g. with mc.

It seems like your issue is due to a Raspbian and/or image specific 
customization.

Hope this helps,
Andrei
-- 
Looking after bugs reported against inexistent or removed packages


signature.asc
Description: PGP signature

Bug#934761: exim4: 2) Callout timeout in recipient verify can result in the lost of the TLS incoming connexion

[Andreas Metzler]

On 2019-08-14 Martin Duspiva  wrote:
[...]
> I think that the bug #887489, which is  already archived, is still persist.
> I have Debin 9 with backported Exim4 ( 4.92-8+deb10u1~bpo9+1 ) and the 
> callout funciton in rcpt acl has  as the same bad behavior as described in 
> bug #887489.

> My acl rule in acl_smtp_rcpt :

>   accept hosts =  +relay_from_hosts
> !verify = recipient/defer_ok/callout=30s,defer_ok,use_sender
[...]
> And relay hosts sometimes get te following 421 error when sending email:
> "SMTP command timeout on TLS connection from of.aira.cz (remote.aira.cz) 
> [84.242.100.166]"


> This is in Exim's debug log:

>  5272 tls_write(0x5639a0cfa550, 14)
>  5272 gnutls_record_send(SSL, 0x5639a0cfa550, 14)
>  5272 outbytes=14
>  5272 DSN: orcpt: NULL  flags: 0
>  5272 Calling gnutls_record_recv(0x5639a0d8d410, 0x5639a11560e0, 4096)
>  5272 GnuTLS<3>: ASSERT: buffers.c[_gnutls_io_read_buffered]:587
>  5272 GnuTLS<3>: ASSERT: record.c[_gnutls_recv_int]:1473
>  5272 LOG: lost_incoming_connection MAIN
>  5272   SMTP command timeout on TLS connection from of.aira.cz 
> (remote.aira.cz) [84.242.100.166]
>  5272 SMTP>> 421 holub.aira.cz: SMTP command timeout - closing connection

> The acl works well with comment out "callout" line. 

Hello Martin,

can you please clarify where/which host saw what error message and to
what part of the connection the above debug log belongs?

I only see two hosts holub.aira.cz = remote.aira.cz and of.aira.cz) but
would have expected three (1 mail server, that is were exim runs. 2 a
remote host trying to submit a message to exim. 3 the remote host exim
is calling out to.)

I would appreciate if you could reply directly on the upstream report
 https://bugs.exim.org/show_bug.cgi?id=2431 

 cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#934105: another backtrace

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2019-08-11 at 09:28 +0800, Jun Jiang wrote:
> I hope this is helpful.

Hi,

could it be that the crashes started occurring after a glib update?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1VWiMACgkQ3rYcyPpX
RFthtwf/bgI1PpRgepKq1+2jWcjo73bMg3uX41TNj0Vi2aZMN/G0fjYhnR1Vev7o
evAe89db1FqU8FqXJ1ddijJCYezTcjTYoePUwnbwJmyDm4OTZ1TpNStydupuDWMU
UMCpQCBS9cV7ESS0v41W+7GGE1wFswlP427clRIf6ik70C6vdZvdwciw2iy+j0Wn
cNkpScfiK1U9ulTOtwtZ0XWS+u1pBOA5cYR5w/2mAaJx1kDzMeAuobKtgaiJHIcR
7IgGpSwWWHvD+1C92fB06KOrEqpNQvrjd4m50NpAdWFVl8JLXr89sgi3Ug57eNuq
5bOYTVWWrzYUKWy6/tsU2CYfCjt+Jg==
=i6RY
-END PGP SIGNATURE-

Bug#934302: [Pkg-swan-devel] Bug#934302: new upstream version with IPv6 support for charon-nm

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 2019-08-09 at 12:12 +0200, Harald Dunkel wrote:
> Upstream provides a new strongswan version 5.8.0, including
> IPv6 support for charon-nm. See
> 
> https://wiki.strongswan.org/issues/1143
> 
> Would it be possible to include this version for Bullseye?

Yes, that's planned.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1VWp0ACgkQ3rYcyPpX
RFvREQf8DR6zcQAOmsBIhKA37ycxU5Lwg3lLqzbHyUEbGgkRSdCNmQsXPxWRxb5Z
vKKT4x72DQkZbUzwMbvH6t2DfGnR1IeBLRkyLPbjnhcfCvSfmql8lMBY6DWN6/fb
48hjY7KZpLCnhYGB8pM3QTf+MMrar8ZGsMDP7H++jueamlHOmmOMQ8QSKGE/RkPe
bqFCgCYXtUUjkoCVkCUKnaJHjTB9EfwHa5BWce8QG7d2HxgGp5ONB5f27wu6MbUX
6AEZqvK/jgfTxOSylWnWi4l9vbXEwr3aZu0SDDilUbTajCoofgKQxsha+q/Pbnql
uvLJ7TP/Qz21+8B0v53l9KccuEX4VQ==
=+fnR
-END PGP SIGNATURE-

Bug#933491: [Pkg-swan-devel] Bug#933491: swanctl.conf must not be world-readable

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2019-07-31 at 00:12 +0600, Vladimir Bezhenar wrote:
> By default file /etc/swanctl/swanctl.conf is world-readable
> (permissions 644). This file can contain passwords for EAP
> authentications, therefore it must not be world-readable, as this
> information is confidential.

Hey,

I'm not entirely sure I agree with this. I mean, it definitely make sense to
protect private assets, but that's why there are subfolders (with relevant
permissions) for private keys and stuff like that.

If people want to (or rather have to) use stuff like passwords, I think they
really should make sure those are not exposed by too wide permissions.

That beeing said, I'm not sure how much it “hurts” to have swanctl.conf (and
conf.d) not world readable by default. I'll ask upstream about that.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1VWk0ACgkQ3rYcyPpX
RFuxYwgAtqhsyi0k68jUlmlPccwgDwy3gWpFKCm3NnrsdsmZ1CA2QJOluuAJf4r1
7bBpF6UnVZii5OqcZzqRSw3u6zg0sEEiTK7fWl2n870BxWC6COpigue+FTo+tWzf
m+PzVlBKZqRiDZkKITvX7bbCc4gtfDNFZxHKPGTSHbqN1z1B+6uVovECXFv5eI4Z
PnDn+7Tbxrtt5LDacFFn7/Oc36FbZXGlCbkQr5LqlLnGhhl6IBA17sLVRKWywdJp
AZ14hHp9+2A4z4EcKJjh1gCBO3n47j6rMLdliPcpt9sQ+S1YG9pBLVhFwDwzoJqR
Ep3j5/xrFv4kOleQgZ6iLOwiKCw2Sg==
=L9qn
-END PGP SIGNATURE-

Bug#934387: lxc: I have this problem too, any plan to backport?

[John Wong]

Package: lxc
Version: 1:3.1.0+really3.0.4-1
Followup-For: Bug #934387

Dear Maintainer,
 I have this problem too, any plan to backport the fix?
 Thanks.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages lxc depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.28-10
ii  libcap21:2.25-2
ii  libgcc11:9.2.1-1
ii  liblxc11:3.1.0+really3.0.4-1
ii  libseccomp22.4.1-2
ii  libselinux12.9-2+b2
ii  lsb-base   11.0.1

Versions of packages lxc recommends:
ii  apparmor   2.13.3-4
ii  bridge-utils   1.6-2
pn  debootstrap
ii  dirmngr2.2.17-3
pn  dnsmasq-base   
ii  gnupg  2.2.17-3
ii  iproute2   5.2.0-1
pn  libpam-cgfs
ii  lxc-templates  3.0.3-1+b1
ii  lxcfs  3.0.4-2
ii  nftables   0.9.1-2+b1
ii  openssl1.1.1c-1
ii  rsync  3.1.3-6+b1
pn  uidmap 

Versions of packages lxc suggests:
ii  btrfs-progs  5.2.1-1
ii  lvm2 2.03.02-3
ii  python3-lxc  1:3.0.3-1+b1

-- debconf information excluded

Bug#934824: bug script doesn't grok missing /e/n/i

[Marc Haber]

Package: src:linux
Version: 5.2.7-1
Severity: normal
File: /usr/share/bug/linux-image-5.2.0-2-amd64/script

Hi,

I have long purged ifupdown from my system, there is no
/etc/network/interfaces. The bug script doesn't handle this situation:

Please select tags: (one at a time) [none]
Gathering additional data, this may take a while...
Use sudo to read the kernel log? y
[sudo] password for mh:
Include network configuration and status from this computer? y
/usr/share/bug/linux-image-5.2.0-2-amd64/include-network: line 7: 
/etc/network/interfaces: No such file or directory
The package bug script /usr/share/bug/linux-image-5.2.0-2-amd64/script exited 
with an error status (return code = 256). Do you still want to file a report? 
[y|N|q|?]?

The script should catch this situation and continue its work.

Greetings
Marc

-- Package-specific info:
** Version:
Linux version 5.2.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-19)) #1 SMP Debian 5.2.7-1 (2019-08-07)

** Command line:
BOOT_IMAGE=/vmlinuz-5.2.0-2-amd64 root=/dev/mapper/dropbtr0 ro 
rootflags=subvol=drop-root quiet splash

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20F5S5X100
product_version: ThinkPad X260
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: R02ET63W (1.36 )
board_vendor: LENOVO
board_name: 20F5S5X100
board_version: 0B98417 WIN

** Loaded modules:
hid_generic
usbhid
hid
tun
ctr
ccm
rfcomm
cpufreq_userspace
cpufreq_powersave
cpufreq_conservative
cdc_mbim
cdc_wdm
cdc_ncm
cmac
bnep
fuse
cdc_ether
option
usbnet
mii
usb_wwan
usbserial
btusb
btrtl
btbcm
btintel
bluetooth
drbg
ansi_cprng
ecdh_generic
ecc
bridge
stp
llc
dummy
ip6t_REJECT
nf_reject_ipv6
arc4
ip6_tables
nft_chain_nat
xt_MASQUERADE
nf_nat
msr
xt_TCPMSS
intel_rapl
snd_soc_skl
snd_hda_codec_hdmi
iwlmvm
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
nft_counter
snd_hda_ext_core
x86_pkg_temp_thermal
intel_powerclamp
snd_soc_acpi_intel_match
snd_soc_acpi
mac80211
kvm_intel
snd_hda_codec_realtek
ipt_REJECT
nf_reject_ipv4
snd_soc_core
snd_hda_codec_generic
mei_wdt
xt_tcpudp
snd_compress
kvm
snd_hda_intel
iwlwifi
xt_conntrack
snd_hda_codec
irqbypass
joydev
nf_conntrack
nf_defrag_ipv6
intel_cstate
iTCO_wdt
nf_defrag_ipv4
cfg80211
rtsx_pci_ms
iTCO_vendor_support
intel_uncore
snd_hda_core
sg
intel_rapl_perf
wmi_bmof
watchdog
nft_compat
snd_hwdep
memstick
serio_raw
tpm_tis
thinkpad_acpi
snd_pcm
mei_me
tpm_tis_core
snd_timer
nvram
mei
ledtrig_audio
intel_pch_thermal
tpm
snd
pcc_cpufreq
soundcore
rng_core
nf_tables
rfkill
ac
battery
evdev
nfnetlink
tcp_bbr
sch_fq
nfsd
coretemp
loop
parport_pc
auth_rpcgss
ppdev
lp
nfs_acl
lockd
parport
grace
sunrpc
ip_tables
x_tables
autofs4
btrfs
zstd_decompress
zstd_compress
ext4
crc16
mbcache
jbd2
algif_skcipher
af_alg
dm_crypt
dm_mod
uas
usb_storage
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
sd_mod
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
i915
rtsx_pci_sdmmc
mmc_core
aesni_intel
i2c_algo_bit
drm_kms_helper
aes_x86_64
crypto_simd
cryptd
glue_helper
psmouse
ahci
xhci_pci
drm
libahci
xhci_hcd
libata
e1000e
i2c_i801
usbcore
scsi_mod
rtsx_pci
mfd_core
usb_common
wmi
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Host Bridge/DRAM Registers [17aa:504a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD 
Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:504a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:504a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 21)
Subsystem: Lenovo Sunrise Point-LP Thermal subsyste

Bug#933887:

[Gert van Dijk]

Also ran into this issue.

I have created a merge request to fix this:
https://salsa.debian.org/giraffe-team/kopanocore/merge_requests/6

HTH

Gert

Bug#925837: systemc: ftbfs with GCC-9

[أحمد المحمودي]

On Wed, Mar 27, 2019 at 07:48:14PM +, Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
> http://gcc.gnu.org/gcc-9/porting_to.html
> 
> [...]
> - 
> _ZN5sc_dt13b_xor_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
>  2.3.3
> +#MISSING: 2.3.3-2# 
> _ZN5sc_dt13b_xor_assign_INS_10sc_bv_baseENS_10sc_lv_baseEEERT_RNS_8sc_proxyIS3_EERKNS5_IT0_EE@Base
>  2.3.3
> [...]
---end quoted text---

The wierd symbol mangling in C++ ks causing this proble, with rvery 
gcc/g++ update, I tried using c++filt symbols (using c++ tag), but it 
was of no use.
Hence, I think the best solution is to remove the symbols file for this 
package.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#934713: os-prober: missing dependency on mount

[Cyril Brulebois]

Johannes 'josch' Schauer  (2019-08-13):
> Package: os-prober
> Version: 1.76
> Severity: important
> 
> Hi,
> 
> The script /usr/lib/os-probes/50mounted-tests calls the `umount` utility
> which resides in the mount package. But os-prober does not depend on
> mount and thus one might get this error message:
> 
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-5.2.0-2-amd64
> Found initrd image: /boot/initrd.img-5.2.0-2-amd64
> /usr/lib/os-probes/50mounted-tests: 10: umount: not found
> rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
> 
> 
> The mount package used to be Essential:yes. Since version 2.29.2-3 it is
> not essential anymore and os-prober should depend on it.

How come packages drop their Essential: yes bit all of a sudden?


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


signature.asc
Description: PGP signature

Bug#934434: Missing bullets on items

[Tatsuya Kinoshita]

On August 11, 2019 at 4:35AM +0800, jidanni (at jidanni.org) wrote:
> Package: w3m-el-snapshot
> Version: 1.4.632+0.20190731-1
> 
> X is missing its bullet!

It depends on your fonts configuration.

Workaround: (setq w3m-use-symbol nil)

Is it safe to disable w3m-use-symbol by default?

Thanks,
-- 
Tatsuya Kinoshita

Bug#934825: python-yappi: migration blocked by binary upload

[Esa Peuha]

Source: python-yappi
Version: 1.0-1

python-yappi isn't migrating to testing due to a maintainer-uploaded
amd64 binary package. This blocks migration of python-oslo.service
which is currently unbuildable in testing. Please make a source-only
upload of python-yappi.

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

[Cyril Brulebois]

Hi,

Holger Wansing  (2019-08-14):
> Martin-Éric Racine  wrote:
> > Package: keyboard-configuration
> > Version: 1.191
> > Severity: important
> > Tags: l10n
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > The debconf template in keyboard-configuration for Finnish is full of 
> > prompts 
> > and selectable options written in Russian or Spanish. This is a serious
> > usability issue. In cases where a template has not been fully localised, 
> > text in the locale C would be expected.
> 
> I which environment did you see this?
> Did this happen while installing Debian with the debian-installer?

#924657 I suppose?


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


signature.asc
Description: PGP signature

Bug#934492: debian-installer: installing drivers through preseed file causes black screen

[Cyril Brulebois]

Hi,

Wouter Wijsman  (2019-08-11):
> Lately I've been playing with creating my own Debian ISO files with
> some drivers in them. In doing so I have found an issue with the
> installer which is causing me some problems.
> 
> When I use the pkgsel line in my default.preseed file to install
> either the package nvidia-driver or broadcom-sta-dkms, the screen will
> go black directly after the installer installed one of these packages.
> It will not go back to normal, even after waiting over for 10 minutes
> and constantly moving the mouse and pressing buttons on the keyboard,
> but the installer itself doesn't crash.  If the default.preseed file
> automates every step after installing one or both of these packages,
> the installation will finish without other issues, even with the black
> screen.
> 
> When I don't have the nvidia-driver or broadcom-sta-dkms package in my
> default.preseed, I do not experience this issue. I have tested this on
> an Alienware Steam Machine, a Zotac ZBOX-CI323NANO (which has intel
> graphics) and in Virtualbox and I'm seeing this issue on all of them.
> 
> I think this is related to dkms being triggered, as I haven't seen
> this issue being caused by other packages so far. I hope this can be
> resolved without having to rebuild these packages to not do so.

While I understand why that must be not fun, I'm not sure I'd call that
a bug in the installer… You might need to take some extra step in some
preseed command to ensure DKMS doesn't kick in while you're installing
those packages, if that triggers such issues during the installation.


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


signature.asc
Description: PGP signature

Bug#859122: 31 DLAs missing from the website

[Holger Levsen]

Hi Brian,

thanks for caring about this old information!

On Thu, Aug 15, 2019 at 05:31:51PM +1000, Brian May wrote:
> Where to from here? Should I invent an appropriate DLA-145-2 based on
> the information above?

yes, that seems very reasonable.


-- 
tschau,
cheers,
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

Bug#934826: buster-pu: package console-setup/1.193~deb10u1

[Cyril Brulebois]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to get #924657 fixed in buster. A Perl change triggered a bunch
of brokenness in translations, and I haven't been able to review the fix
before the release. I've done that now, as documented in:
  https://bugs.debian.org/924657#49

Since I've double checked this, 1.193 was uploaded with a few translation
updates and it seems to make sense to include them as well, hence this
proposed 1.193~deb10u1.

Changes from 1.191:
| console-setup (1.193~deb10u1) buster; urgency=medium
| 
|   * Rebuild for buster.
| 
|  -- Cyril Brulebois   Thu, 15 Aug 2019 16:11:30 > 0200
| 
| console-setup (1.193) unstable; urgency=medium
| 
|   * Team upload
| 
|   [ Updated translations ]
|   * Croatian (hr.po) by gogogogi
|   * Tajik (tg.po) by Victor Ibragimov
| 
|  -- Holger Wansing   Sun, 04 Aug 2019 12:08:32 > 0200
| 
| console-setup (1.192) unstable; urgency=medium
| 
|   * Remove Christian Perrier from Uploaders, with many thanks for all
| his contributions over the years! (Closes: #927511)
|   * Merge patch by Iain Lane to fix internationalization issues when
| switching locales with Perl >= 5.28 (Closes: #924657, LP: #1817453).
| 
|  -- Cyril Brulebois   Thu, 04 Jul 2019 17:41:47 > 0200

git diff from the tag attached.


Thanks for considering, and thanks for your time.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff --git a/Keyboard/kbdnames-maker b/Keyboard/kbdnames-maker
index 9d66731..56d42d8 100755
--- a/Keyboard/kbdnames-maker
+++ b/Keyboard/kbdnames-maker
@@ -39,6 +39,8 @@ for my $mo () {
 $lang =~ s:/usr/share/locale/(.*)/LC_MESSAGES/xkeyboard-config.mo:$1:;
 $ENV{'LANGUAGE'} = $lang;
 setlocale(LC_ALL,"");
+bindtextdomain("xkeyboard-config", "/usr/share/locale");
+textdomain("xkeyboard-config");
 
 $lang =~ s:\@:__:;
 $lang =~ s:__Latn:__latin:; # special fixup for sr
diff --git a/debian/changelog b/debian/changelog
index 2b8cf2d..afd1c0a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,24 @@
+console-setup (1.193) unstable; urgency=medium
+
+  * Team upload
+
+  [ Updated translations ]
+  * Croatian (hr.po) by gogogogi
+  * Tajik (tg.po) by Victor Ibragimov
+
+ -- Holger Wansing   Sun, 04 Aug 2019 12:08:32 +0200
+
+console-setup (1.192) unstable; urgency=medium
+
+  * Remove Christian Perrier from Uploaders, with many thanks for all
+his contributions over the years! (Closes: #927511)
+  * Merge patch by Iain Lane to fix internationalization issues when
+switching locales with Perl >= 5.28 (Closes: #924657, LP: #1817453).
+
+ -- Cyril Brulebois   Thu, 04 Jul 2019 17:41:47 +0200
+
 console-setup (1.191) unstable; urgency=medium
+
   * Team upload
 
   [ Updated translations ]
@@ -8,6 +28,7 @@ console-setup (1.191) unstable; urgency=medium
  -- Holger Wansing   Sat, 23 Mar 2019 21:13:24 +0100
 
 console-setup (1.190) unstable; urgency=medium
+
   * Team upload
 
   * console-setup(5) manpage: correct section of setfont manpage and remove
@@ -20,6 +41,7 @@ console-setup (1.190) unstable; urgency=medium
  -- Holger Wansing   Mon, 04 Mar 2019 04:44:51 +0100
 
 console-setup (1.189) unstable; urgency=medium
+
   * Team upload
 
   [ Holger Wansing ]
diff --git a/debian/control b/debian/control
index ceba9df..b8e69f0 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: console-setup
 Section: utils
 Priority: optional
 Maintainer: Debian Install System Team 
-Uploaders: Anton Zinoviev , Christian Perrier 
+Uploaders: Anton Zinoviev 
 Build-Depends-Indep: xkb-data (>= 1.6), locales-all, sharutils
 Build-Depends: perl, debhelper (>= 9), po-debconf, libxml-parser-perl, bdfresize, liblocale-gettext-perl, dh-systemd
 Standards-Version: 3.9.1
diff --git a/debian/po/ar.po b/debian/po/ar.po
index 9c70c7f..99ffd82 100644
--- a/debian/po/ar.po
+++ b/debian/po/ar.po
@@ -11,6 +11,7 @@
 # Abdelhak Bougouffa, 2017.
 # najib LAARIBI , 2018.
 # ButterflyOfFire , 2018.
+# Osama , 2019.
 #
 # Translations from iso-codes:
 # Translations taken from ICU SVN on 2007-09-09
@@ -27,7 +28,7 @@ msgstr ""
 "Project-Id-Version: ar\n"
 "Report-Msgid-Bugs-To: console-se...@packages.debian.org\n"
 "POT-Creation-Date: 2018-03-10 23:15+0100\n"
-"PO-Revision-Date: 2018-10-05 16:21+\n"
+"PO-Revision-Date: 2019-06-10 10:55+\n"
 "Last-Translator: ButterflyOfFire \n"
 "Language-Team: \n"
 "Language: ar\n"
@@ -169,14 +170,15 @@ msgstr "# Latin2 - وسط أوروبا والرومانية"
 #. :sl3:
 #: ../console-setup.templates:5001
 msgid "# Latin3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh"
-msgstr "# Latin3 و Latin8 - تشيتشيوا; إسبترنتو; الآيرلندية; المالتيز والولش"
+msgstr ""
+"# Latin3 و Latin8 - تشيتشيوا ؛ الإسبترنتو ؛ الإيرلندية ؛ المالتيز والولش"
 
 #. Type: select
 #. Choices
 #. :sl3:
 #: ../console-setup.templates:5001
 msgid "#

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

[Martin-Éric Racine]

to 15. elok. 2019 klo 16.53 Cyril Brulebois (k...@debian.org) kirjoitti:
> Holger Wansing  (2019-08-14):
> > Martin-Éric Racine  wrote:
> > > Package: keyboard-configuration
> > > Version: 1.191
> > > Severity: important
> > > Tags: l10n
> > >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > The debconf template in keyboard-configuration for Finnish is full of 
> > > prompts
> > > and selectable options written in Russian or Spanish. This is a serious
> > > usability issue. In cases where a template has not been fully localised,
> > > text in the locale C would be expected.
> >
> > I which environment did you see this?
> > Did this happen while installing Debian with the debian-installer?
>
> #924657 I suppose?

It seems similar enough.  However, #924657 works under the assumption
of a changed locale, yet the locale on this host has remained at
fi_FI.UTF-8 ever since Debian migrated away from Latin encodings.

Martin-Éric

Bug#851774: fixed in apt-setup 1:0.151

[Cyril Brulebois]

Hi,

Moritz Muehlenhoff  (2019-07-17):
> On Fri, Jul 12, 2019 at 09:07:45AM +, Cyril Brulebois wrote:
> >  apt-setup (1:0.151) unstable; urgency=medium
> >  .
> >[ Moritz Mühlenhoff ]
> >* When preseeding a local repository via apt-setup/localX/repository,
> >  the repository key for Secure Apt needs to be configured with
> >  apt-setup/localX/key. This key used to be set up with apt-key, but
> >  its use is deprecated and apt's former dependency on gnupg has been
> >  demoted to a Suggests, rendering apt-key non-functional in d-i.
> >  Apply a patch by Lars Kollstedt (thanks!) which adds the repository
> >  key(s) to /etc/apt/trusted.gpg.d, following the approach used by
> >  pbuilder (Closes: #851774, #928931):
> >   - .asc suffix if the key file seems to be armoured ASCII (i.e. it
> > contains a “-BEGIN PGP PUBLIC KEY BLOCK-” line);
> >   - .gpg suffix otherwise. Please note that only “GPG key public ring”
> > are supported by APT, newer “keybox database” format isn't at the
> > moment.
> 
> Hi Cyril,
> as discussed on #debian-boot last week: I've tested a Buster installation with
> "d-i mirror/udeb/suite   string  unstable" and our previous
> "d-i base-installer/includes string  gnupg" workaround dropped which uses
> the https://apt.wikimedia.org repository and that worked fine.

Many thanks, I'll be submitting a buster-pu bug accordingly. I wouldn't
mind an extra confirmation after it's been published in a point release
(peace of mind and all that).

> I've also submitted a patch to installation-guide to enhance the docs
> so that the constraints for the Secure Apt key file are explicitly
> mentioned (#932284)

Much appreciated, thanks.


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


signature.asc
Description: PGP signature

Bug#934713: os-prober: missing dependency on mount

[Johannes Schauer]

Quoting Cyril Brulebois (2019-08-15 15:50:03)
> > The script /usr/lib/os-probes/50mounted-tests calls the `umount` utility
> > which resides in the mount package. But os-prober does not depend on mount
> > and thus one might get this error message:
> > 
> > Generating grub configuration file ...
> > Found linux image: /boot/vmlinuz-5.2.0-2-amd64
> > Found initrd image: /boot/initrd.img-5.2.0-2-amd64
> > /usr/lib/os-probes/50mounted-tests: 10: umount: not found
> > rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
> > 
> > 
> > The mount package used to be Essential:yes. Since version 2.29.2-3 it is
> > not essential anymore and os-prober should depend on it.
> 
> How come packages drop their Essential: yes bit all of a sudden?

Version 2.29.2-3 was released more than two years ago. It was brought up on
debian-devel here:

https://lists.debian.org/20170726081846.ga22...@fatal.se

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#931729: apt-mirror: SSUse of uninitialized value $lines{"Files:"} in split at /usr/bin/apt-mirror line 829

[Сергей Фёдоров]

Package: apt-mirror
Version: 0.5.4-1
Followup-For: Bug #931729

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), 
LANGUAGE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-mirror depends on:
ii  adduser  3.118
ii  perl 5.28.1-6
ii  wget 1.20.3-1+b1

apt-mirror recommends no packages.

apt-mirror suggests no packages.

-- Configuration Files:
/etc/apt/mirror.list changed:
set base_path /mnt/repo/debian/DebianMirror
set mirror_path  $base_path/mirror
set skel_path$base_path/skel
set var_path $base_path/var
set cleanscript $var_path/clean.sh
set defaultarch amd64
set run_postmirror  0
set nthreads   20
set tilde   0
debhttp://ftp.debian.org/debian jessie  main contrib non-free
deb-srchttp://ftp.debian.org/debian jessie  main contrib non-free
debhttp://ftp.debian.org/debian buster main contrib non-free
deb-srchttp://ftp.debian.org/debian buster main contrib non-free
debhttp://ftp.debian.org/debian  sid main contrib non-free
deb-srchttp://ftp.debian.org/debian  sid main contrib non-free
debhttp://ftp.debian.org/debian jessie-updates main contrib non-free
deb-srchttp://ftp.debian.org/debian jessie-updates main contrib non-free
debhttp://ftp.debian.org/debian buster-updates main contrib non-free
deb-srchttp://ftp.debian.org/debian buster-updates main contrib non-free
clean http://ftp.debian.org/debian


-- no debconf information

2019-08-15 15:00 What does it mean?

root@A1:/home/u1# apt-mirror; cd /mnt/repo/debian/DebianMirror/var/; ./clean.sh
Downloading 210 index files using 20 threads...
Begin time: Thu Aug 15 14:46:37 2019
[20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]... [11]... 
[10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]... [1]... [0]...
End time: Thu Aug 15 14:51:36 2019

Processing translation indexes: [T]

Downloading 120 translation files using 20 threads...
Begin time: Thu Aug 15 14:51:36 2019
[20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]... [11]... 
[10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]... [1]... [0]...
End time: Thu Aug 15 14:51:57 2019

Processing DEP-11 indexes: [D]

Downloading 30 dep11 files using 20 threads...
Begin time: Thu Aug 15 14:51:57 2019
[20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]... [11]... 
[10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]... [1]... [0]...
End time: Thu Aug 15 14:51:58 2019

Processing indexes: [SUse of uninitialized value $lines{"Files:"} in split 
at /usr/bin/apt-mirror line 829,  line 1.
Use of uninitialized value $lines{"Files:"} in split at /usr/bin/apt-mirror 
line 829,  line 2.
P]

2.1 GiB will be downloaded into archive.
Downloading 1419 archive files using 20 threads...
Begin time: Thu Aug 15 14:52:17 2019
[20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]... [11]... 
[10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]... [1]... [0]...
End time: Thu Aug 15 17:10:12 2019

2.1 GiB in 1315 files and 13 directories can be freed.
Run /mnt/repo/debian/DebianMirror/var/clean.sh for this purpose.

Removing 1315 unnecessary files [2.1 GiB]...
[0%]..[38%]..[76%]done.

Removing 13 unnecessary directories...
[0%].done.

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

[Cyril Brulebois]

Martin-Éric Racine  (2019-08-15):
> to 15. elok. 2019 klo 16.53 Cyril Brulebois (k...@debian.org) kirjoitti:
> > #924657 I suppose?
> 
> It seems similar enough.  However, #924657 works under the assumption
> of a changed locale, yet the locale on this host has remained at
> fi_FI.UTF-8 ever since Debian migrated away from Latin encodings.

No? The contents of the buster binaries are broken, because of the
locale changes at build time.

(Just filed #934826 BTW.)


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


signature.asc
Description: PGP signature

Bug#934703: keyboard-configuration: debconf localisation for Finnish full of Russian and Spanish prompts

[Martin-Éric Racine]

to 15. elok. 2019 klo 17.30 Cyril Brulebois (k...@debian.org) kirjoitti:
>
> Martin-Éric Racine  (2019-08-15):
> > to 15. elok. 2019 klo 16.53 Cyril Brulebois (k...@debian.org) kirjoitti:
> > > #924657 I suppose?
> >
> > It seems similar enough.  However, #924657 works under the assumption
> > of a changed locale, yet the locale on this host has remained at
> > fi_FI.UTF-8 ever since Debian migrated away from Latin encodings.
>
> No? The contents of the buster binaries are broken, because of the
> locale changes at build time.

Broken locales at build time sounds plausible.

> (Just filed #934826 BTW.)

Thanks!

-- Martin-Éric

Bug#934713: os-prober: missing dependency on mount

[Cyril Brulebois]

Johannes Schauer  (2019-08-15):
> Quoting Cyril Brulebois (2019-08-15 15:50:03)
> > > The script /usr/lib/os-probes/50mounted-tests calls the `umount` utility
> > > which resides in the mount package. But os-prober does not depend on mount
> > > and thus one might get this error message:
> > > 
> > > Generating grub configuration file ...
> > > Found linux image: /boot/vmlinuz-5.2.0-2-amd64
> > > Found initrd image: /boot/initrd.img-5.2.0-2-amd64
> > > /usr/lib/os-probes/50mounted-tests: 10: umount: not found
> > > rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource 
> > > busy
> > > 
> > > 
> > > The mount package used to be Essential:yes. Since version 2.29.2-3
> > > it is not essential anymore and os-prober should depend on it.
> > 
> > How come packages drop their Essential: yes bit all of a sudden?
> 
> Version 2.29.2-3 was released more than two years ago. It was brought
> up on debian-devel here:
> 
> https://lists.debian.org/20170726081846.ga22...@fatal.se

Well, debian-devel@ isn't where one files bug reports against packages
that suddenly need a dependency?


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


signature.asc
Description: PGP signature

Bug#934721: sbuild: Lintian run via sbuild produces different output than running lintian manually with the same options

[Bill Blough]

Hi Josch,

Here's an updated patch.

Now .changes.new is written to $build_dir, then renamed to .changes, and
copied from the chroot to sys_build_dir.

I removed the call to unlink() since we want to keep the .changes file
in $build_dir so it can be used by lintian.

Also, I saw in HACKING that the emacs perl-mode style is used.  I don't
use emacs, and unfortunately a web search didn't turn up the specifics
of what that styling entails.  So I tried to match the style the best I
could.  Apologies if it's off slightly.

Let me know if you see any issues with the patch.

Thanks,
Bill
diff --git a/lib/Sbuild/Build.pm b/lib/Sbuild/Build.pm
index f5660148..5e60436f 100644
--- a/lib/Sbuild/Build.pm
+++ b/lib/Sbuild/Build.pm
@@ -2601,8 +2601,9 @@ sub build {
 	}
 
 	my $sys_build_dir = $self->get_conf('BUILD_DIR');
-	if (!open( F2, ">$sys_build_dir/$changes.new" )) {
-		$self->log("Cannot create $sys_build_dir/$changes.new: $!\n");
+	my $F2 = $session->get_write_file_handle("$build_dir/$changes.new");
+	if (!$F2) {
+		$self->log("Cannot create $build_dir/$changes.new\n");
 		$self->log("Distribution field may be wrong!!!\n");
 		if ($build_dir) {
 		if(!$session->copy_from_chroot("$build_dir/$changes", ".")) {
@@ -2611,14 +2612,21 @@ sub build {
 		}
 	} else {
 		$pchanges->output(\*STDOUT);
-		$pchanges->output(\*F2);
-
-		close( F2 );
-		rename("$sys_build_dir/$changes.new", "$sys_build_dir/$changes")
-		or $self->log("$sys_build_dir/$changes.new could not be " .
-		"renamed to $sys_build_dir/$changes: $!\n");
-		unlink("$build_dir/$changes")
-		if $build_dir;
+		$pchanges->output(\*$F2);
+
+		close( $F2 );
+
+		$session->rename("$build_dir/$changes.new", "$build_dir/$changes");
+		if ($? == 0) {
+		$self->log("$build_dir/$changes.new could not be " .
+			"renamed to $build_dir/$changes: $!\n");
+		$self->log("Distribution field may be wrong!!!");
+		}
+		if ($build_dir) {
+		if (!$session->copy_from_chroot("$build_dir/$changes", "$sys_build_dir")) {
+			$self->log("Could not copy $build_dir/$changes to $sys_build_dir");
+		}
+		}
 	}
 
 	return $pchanges;

Bug#934713: os-prober: missing dependency on mount

[Johannes Schauer]

Hi,

Quoting Cyril Brulebois (2019-08-15 16:44:05)
> > Version 2.29.2-3 was released more than two years ago. It was brought up on
> > debian-devel here:
> > 
> > https://lists.debian.org/20170726081846.ga22...@fatal.se
> 
> Well, debian-devel@ isn't where one files bug reports against packages that
> suddenly need a dependency?

I was not trying to justify or excuse the omission of the src:util-linux
maintainers. I can only imagine that os-prober somehow slipped through the
cracks when the src:util-linux maintainers filed bugs against all packages that
need the mount utilities during the buster release cycle.

I agree that the situation now is unfortunate but I only reported this problem
once I stumbled across it. I was not involved in the decision two years ago.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#934827: buster-pu: package apt-setup/1:0.151~deb10u1

[Cyril Brulebois]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to get apt-setup updated in buster to fix preeeding apt keys
(#851774). This update was kindly tested by Moritz by fetching the
updated udebs from unstable, on buster systems:
  https://bugs.debian.org/851774#108

I'd think backporting the package currently in unstable would make
sense, and also include some l10n updates:

 debian/changelog   |   30 ++
 debian/po/ar.po|   12 +-
 debian/po/hi.po|5 -
 debian/po/hr.po|  254 ++---
 generators/60local |   18 ++-
 5 files changed, 176 insertions(+), 143 deletions(-)

Changes from buster:
| apt-setup (1:0.151~deb10u1) buster; urgency=medium
| 
|   * Rebuild for buster.
| 
|  -- Cyril Brulebois https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
diff --git a/debian/changelog b/debian/changelog
index 182e8a4..9d6ae16 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,33 @@
+apt-setup (1:0.151~deb10u1) buster; urgency=medium
+
+  * Rebuild for buster.
+
+ -- Cyril Brulebois   Thu, 15 Aug 2019 16:27:55 +0200
+
+apt-setup (1:0.151) unstable; urgency=medium
+
+  [ Moritz Mühlenhoff ]
+  * When preseeding a local repository via apt-setup/localX/repository,
+the repository key for Secure Apt needs to be configured with
+apt-setup/localX/key. This key used to be set up with apt-key, but
+its use is deprecated and apt's former dependency on gnupg has been
+demoted to a Suggests, rendering apt-key non-functional in d-i.
+Apply a patch by Lars Kollstedt (thanks!) which adds the repository
+key(s) to /etc/apt/trusted.gpg.d, following the approach used by
+pbuilder (Closes: #851774, #928931):
+ - .asc suffix if the key file seems to be armoured ASCII (i.e. it
+   contains a “-BEGIN PGP PUBLIC KEY BLOCK-” line);
+ - .gpg suffix otherwise. Please note that only “GPG key public ring”
+   are supported by APT, newer “keybox database” format isn't at the
+   moment.
+
+  [ Updated translations ]
+  * Arabic (ar.po) by ButterflyOfFire
+  * Hindi (hi.po) by KushagraKarira
+  * Croatian (hr.po) by gogogogi
+
+ -- Cyril Brulebois   Fri, 12 Jul 2019 10:49:08 +0200
+
 apt-setup (1:0.150) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/po/ar.po b/debian/po/ar.po
index c467737..45ce0fc 100644
--- a/debian/po/ar.po
+++ b/debian/po/ar.po
@@ -11,6 +11,7 @@
 # Abdelhak Bougouffa, 2017.
 # najib LAARIBI , 2018.
 # ButterflyOfFire , 2018.
+# Osama , 2019.
 #
 # Translations from iso-codes:
 # Translations taken from ICU SVN on 2007-09-09
@@ -27,7 +28,7 @@ msgstr ""
 "Project-Id-Version: ar\n"
 "Report-Msgid-Bugs-To: apt-se...@packages.debian.org\n"
 "POT-Creation-Date: 2019-01-28 21:20+\n"
-"PO-Revision-Date: 2018-01-25 01:44+\n"
+"PO-Revision-Date: 2019-06-10 10:55+\n"
 "Last-Translator: ButterflyOfFire \n"
 "Language-Team: \n"
 "Language: ar\n"
@@ -259,8 +260,9 @@ msgstr ""
 #. Description
 #. :sl3:
 #: ../apt-setup-udeb.templates:12001
+#, fuzzy
 msgid "Enable source repositories in APT?"
-msgstr ""
+msgstr "تمكين المستودعات المصدرية في APT؟"
 
 #. Type: boolean
 #. Description
@@ -396,15 +398,11 @@ msgstr "تغيير القرص"
 #. This template uses the same text as used in the package apt for apt-cdrom
 #. Do not translate "/cdrom/" (the mount point)
 #: ../apt-cdrom-setup.templates:7001
-#, fuzzy
-#| msgid ""
-#| "/cdrom/:Please insert the disc labeled: '${LABEL}' in the drive '/cdrom/' "
-#| "and press enter."
 msgid ""
 "/cdrom/: Please insert the disc labeled '${LABEL}' in the drive '/cdrom/' "
 "and press enter."
 msgstr ""
-"/cdrom/:رجاءً أدخل القرص السمى: '${LABEL}' في السواقة '/cdrom/' واضغط زر "
+"/cdrom/: رجاءً أدخل القرص المسمى '${LABEL}' في السواقة '/cdrom/' واضغط زر "
 "الإدخال."
 
 #. Type: text
diff --git a/debian/po/hi.po b/debian/po/hi.po
index b096ceb..ce85477 100644
--- a/debian/po/hi.po
+++ b/debian/po/hi.po
@@ -32,8 +32,8 @@ msgstr ""
 "Project-Id-Version: debian-installer_packages_po_sublevel1_hi\n"
 "Report-Msgid-Bugs-To: apt-se...@packages.debian.org\n"
 "POT-Creation-Date: 2019-01-28 21:20+\n"
-"PO-Revision-Date: 2018-10-06 15:28+\n"
-"Last-Translator: Kumar Appaiah\n"
+"PO-Revision-Date: 2019-06-18 19:05+\n"
+"Last-Translator: KushagraKarira \n"
 "Language-Team: \n"
 "Language: hi\n"
 "MIME-Version: 1.0\n"
@@ -250,7 +250,6 @@ msgstr ""
 #. Description
 #. :sl1:
 #: ../apt-setup-udeb.templates:11002
-#, fuzzy
 msgid ""
 "Backported software are adapted from the development version to work with "
 "this release. Although this software has not gone through such complete "
diff --git a/debian/po/hr.po b/debian/po/hr.po
index 6abc559..6c55c15 100644
--- a/debian/po/hr.po
+++ b/debian/po/hr.po
@@ -23,15 +23,15 @@ msgstr ""
 "Project-Id-Version: Debian-installer 1st-stage master file HR\n"
 "Report-Msgid-Bugs-To: apt-se...@packages.debia

Bug#925823: scotch: ftbfs with GCC-9

[Drew Parsons]

Package: scotch
Version: 6.0.7-2
Followup-For: Bug #925823

gdb backtrace suggests the error occurs in l.229 order_io.c:

Program received signal SIGSEGV, Segmentation fault.
0x77f9c2f9 in _SCOTCHorderSaveMap (ordeptr=,
vlbltab=, stream=0x9260) at order_io.c:229
229order_io.c: No such file or directory.
(gdb) bt
#0  0x77f9c2f9 in _SCOTCHorderSaveMap (ordeptr=, vlbltab=, stream=0x9260) at order_io.c:229
#1  0x53e5 in main (argc=, argv=) at test_scotch_graph_order.c:143


order_io.c:229 says...
   if (fprintf (stream, GNUMSTRING "\t" GNUMSTRING "\n",   
from ...
  vlbltax = (vlbltab != NULL) ? (vlbltab - ordeptr->baseval) : NULL;
  for (vnodnum = ordeptr->baseval, o = 0; vnodnum < vnodnnd; vnodnum ++) {
if (fprintf (stream, GNUMSTRING "\t" GNUMSTRING "\n",
 (Gnum) ((vlbltax != NULL) ? vlbltax[vnodnum] : vnodnum),
 (Gnum) cblktax[vnodnum]) == EOF) {
  errorPrint ("orderSaveMap: bad output (2)");
  o = 1;
  break;
}
  }

stream is not zero...
(gdb) p stream
$1 = (FILE * const) 0x9260

vlbltax is zero...
(gdb) p vlbltax
$5 = (const Gnum * restrict) 0x0

but that is supposed to be guarded in the call with vlbltax != NULL.

Does it mean the use of the "vlbltax != NULL" pattern is now broken in
gcc9 ?


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

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

Versions of packages scotch depends on:
ii  libbz2-1.0 1.0.6-9.2
ii  libc6  2.28-10
ii  liblzma5   5.2.4-1
ii  libopenmpi33.1.3-11
ii  libscotch-6.0  6.0.7-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

scotch recommends no packages.

scotch suggests no packages.

-- no debconf information

Bug#934761: exim4: 2) Callout timeout in recipient verify can result in the lost of the TLS incoming connexion

[Martin Duspiva]

Hi Andres,
I had answered to the upstream.

MD.

Bug#856443: [Pkg-xfce-devel] Bug#856443: mousepad: Fonts settings not working

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, 2019-06-15 at 09:21 +0100, Amy Wrigley wrote:
> While I am not the user who originally reported this, I can confirm
> that this bug is still present in the current testing/unstable version
> of mousepad. I don't know what more I can say about the problem
> other than that the 'Select Font...' settings have absolutely no effect
> on the text that is displayed. It is always the defaults mousepad
> started with no matter which settings I select.

Is there anything displayed on the console or something? Is something peculiar
about your setup? Because here everything just works as it should so I'm a bit
lost at what happens for you.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1VdHUACgkQ3rYcyPpX
RFuHHgf+KxQe9sKQmjOjNsD2ULJHLT8uEmWA0d0d83cbWSdtpAKQ08X2wo2cVul3
KojOc9bf9W1yjMiNisM4asQZKDnl8+WgLcEwg71KP7p9FUx/phTcPSGj8LbFhrmL
7yBdTXgaRmthEKd+hK+eA9e3LBGhbd+w4+TycfkRzb3RfvAtOQMs22dV6F9csN1e
2N7Lplx514BRE/k1fQbgdLv41E2whQ8KnevQT7CjN1n/wA/wUUjNkJ1IP/sj3yHH
FbsCJugCIK0AeqAQu+X8PEtsOyEoLHzpRBIUUqiIcV3yMh/hEMyrZOwp5bxPs6tU
Vu2K7TDRoiwPfbVmDuCxUMwn0L5slg==
=sKIb
-END PGP SIGNATURE-

Bug#682342: Latest patch successfully tested

[Cyril Brulebois]

Hi,

Nishanth Aravamudan  (2019-08-14):
> We are able to reproduce this issue at will in Ubuntu Bionic's
> installer (not identical to Debian's, but code-wise in this path the
> same).  While quite a while after the last update from Philipp, we
> tested the patch (netcfg_dhcp_domain.patch) after updating it to avoid
> a compilation issue, we found it did fix the problem for us.
> 
> I am not sure if I can get Debian into our infrastructure to test
> explicitly, but I will work on it; at the same time,  the code change
> seems straightforward.

Thanks for your feedback. Care to share the fixed version? :)

I'm a little reluctant to blindly merging this patch (originally
labeled “untested”) without a go from its author. Philipp, should
I go ahead?


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


signature.asc
Description: PGP signature

Bug#933911: buster-pu: package pulseaudio

[Felipe Sateler]

Control: tags -1 -moreinfo

On Sun, Aug 11, 2019 at 9:53 AM Jonathan Wiltshire  wrote:

> Control: tag -1 moreinfo
>
> Hi,
>
> On Sun, Aug 04, 2019 at 09:31:37PM -0400, Felipe Sateler wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: buster
> > User: release.debian@packages.debian.org
> > Usertags: pu
> >
> > Dear release team,
> >
> > There is a bug affecting pulseaudio users: #913102. This bug causes the
> > mute state to be incorrectly restored. Some users have asked for the fix
> > (which is now on unstable), to be backported to buster given that GDM is
> > affected by this bug. The upstream patch fixing this issue is very
> > small[1].
> >
> > The full diff is attached.
>
> The attachment looks like the change as it was uploaded to sid; please
> prepare a proposed update to buster and attach a source debdiff and remove
> the moreinfo tag from this bug.
>

Please find the debdiff attached

-- 

Saludos,
Felipe Sateler
diff -Nru pulseaudio-12.2/debian/changelog pulseaudio-12.2/debian/changelog
--- pulseaudio-12.2/debian/changelog	2019-02-14 20:05:41.0 -0300
+++ pulseaudio-12.2/debian/changelog	2019-08-15 11:21:19.0 -0400
@@ -1,3 +1,10 @@
+pulseaudio (12.2-4+deb10u1) buster; urgency=medium
+
+  * Pick upstream patch fixing mute state restoring (Closes: #913102)
+  * Add gbp config for buster branch
+
+ -- Felipe Sateler   Thu, 15 Aug 2019 11:21:19 -0400
+
 pulseaudio (12.2-4) unstable; urgency=medium
 
   [ Jan Graichen ]
diff -Nru pulseaudio-12.2/debian/gbp.conf pulseaudio-12.2/debian/gbp.conf
--- pulseaudio-12.2/debian/gbp.conf	2019-02-14 20:05:41.0 -0300
+++ pulseaudio-12.2/debian/gbp.conf	2019-08-15 11:21:19.0 -0400
@@ -1,2 +1,3 @@
 [DEFAULT]
 pristine-tar = True
+debian-branch = debian/buster
diff -Nru pulseaudio-12.2/debian/patches/series pulseaudio-12.2/debian/patches/series
--- pulseaudio-12.2/debian/patches/series	2019-02-14 20:05:41.0 -0300
+++ pulseaudio-12.2/debian/patches/series	2019-08-15 11:21:19.0 -0400
@@ -2,3 +2,4 @@
 alsa-mixer-Update-to-support-Arctis-Pro-Wireless-headset.patch
 alsa-mixer-Add-support-for-2018-Arctis-7.patch
 Don-t-compile-with-ffast-math.patch
+sink-source-Don-t-change-suspend-cause-when-unlinking.patch
diff -Nru pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch
--- pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch	1969-12-31 21:00:00.0 -0300
+++ pulseaudio-12.2/debian/patches/sink-source-Don-t-change-suspend-cause-when-unlinking.patch	2019-08-15 11:21:19.0 -0400
@@ -0,0 +1,47 @@
+From: Tanu Kaskinen 
+Date: Mon, 10 Jun 2019 14:18:47 +0300
+Subject: sink, source: Don't change suspend cause when unlinking
+
+See the added comments for why this is necessary.
+
+Fixes: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/667
+(cherry picked from commit 7fb85e0a5bfdec339fda9f7584f65cf9ddbd50a1)
+---
+ src/pulsecore/sink.c   | 6 +-
+ src/pulsecore/source.c | 6 +-
+ 2 files changed, 10 insertions(+), 2 deletions(-)
+
+diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
+index 38e8e50..4a0 100644
+--- a/src/pulsecore/sink.c
 b/src/pulsecore/sink.c
+@@ -760,7 +760,11 @@ void pa_sink_unlink(pa_sink* s) {
+ }
+ 
+ if (linked)
+-sink_set_state(s, PA_SINK_UNLINKED, 0);
++/* It's important to keep the suspend cause unchanged when unlinking,
++ * because if we remove the SESSION suspend cause here, the alsa sink
++ * will sync its volume with the hardware while another user is
++ * active, messing up the volume for that other user. */
++sink_set_state(s, PA_SINK_UNLINKED, s->suspend_cause);
+ else
+ s->state = PA_SINK_UNLINKED;
+ 
+diff --git a/src/pulsecore/source.c b/src/pulsecore/source.c
+index 02ae87a..c11d89b 100644
+--- a/src/pulsecore/source.c
 b/src/pulsecore/source.c
+@@ -702,7 +702,11 @@ void pa_source_unlink(pa_source *s) {
+ }
+ 
+ if (linked)
+-source_set_state(s, PA_SOURCE_UNLINKED, 0);
++/* It's important to keep the suspend cause unchanged when unlinking,
++ * because if we remove the SESSION suspend cause here, the alsa
++ * source will sync its volume with the hardware while another user is
++ * active, messing up the volume for that other user. */
++source_set_state(s, PA_SOURCE_UNLINKED, s->suspend_cause);
+ else
+ s->state = PA_SOURCE_UNLINKED;
+ 

Bug#925823: scotch: ftbfs with GCC-9

[Drew Parsons]

Package: scotch
Version: 6.0.7-2
Followup-For: Bug #925823

The segfault is also triggered by order_io.c l.292, still segfaulting in
./test_scotch_graph_order data/bump_b1.grf

Program received signal SIGSEGV, Segmentation fault.
0x77f9c531 in _SCOTCHorderSaveTree (ordeptr=, 
vlbltab=, stream=0x9260) at order_io.c:292
292 order_io.c: No such file or directory.
(gdb) bt
#0  0x77f9c531 in _SCOTCHorderSaveTree (ordeptr=, 
vlbltab=, stream=0x9260) at order_io.c:292
#1  0x53f3 in main (argc=, argv=) at 
test_scotch_graph_order.c:144


bump_b1.grf seems to be causing problems, see also Bug#932777.

I'll work around by skipping the failing bump_b1.grf tests (patch
skip_failing_tests.patch), until upstream addresses
https://gforge.inria.fr/tracker/index.php?func=detail&aid=21768&group_id=248&atid=1079





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

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

Versions of packages scotch depends on:
ii  libbz2-1.0 1.0.6-9.2
ii  libc6  2.28-10
ii  liblzma5   5.2.4-1
ii  libopenmpi33.1.3-11
ii  libscotch-6.0  6.0.7-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

scotch recommends no packages.

scotch suggests no packages.

-- no debconf information

Bug#546028: (no subject)

[Miguel Figueiredo]

Although this was the behavior from the initial versions, localepurge 
doesn't do this anymore.

Documentation will be updated accordingly for a next version.

--
Best regards / Melhores cumprimentos,

Miguel Figueiredo

Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Paride Legovini]

Dmitry Bogatov wrote on 06/08/2019:
> So, please:
> 
>  * drop --as-needed
>  * fix spelling
>  * finalize changelog (dch -r)

Done.

Paride

Bug#934828: iwl_mvm_add_new_dqa_stream_wk BUG in lib/list_debug.c:56

[Marc Haber]

Package: src:linux
Version: 5.2.7-1
Severity: normal

Hi,

this is an issue that I have been seing on my locally built kernels
since the migration from 5.0 to the cursed 5.1 release. I tried
reporting it to the netdev mailing list but only got "me too" answers,
so I know that I am not the only one who is affected. Unfortunately, no
kernel dev bothered.

You can see the issue at https://lkml.org/lkml/2019/5/30/723

Since I also experience this issue with a distribution kernel, I can now
happily pass on the ball ;-)

My primary notebook is a Lenovo X260 with an Intel Wireless 8260
(8086:24f3). The machine has quite a number of malfunctions with
wireless LAN with the affected kernels. I haven't gone back to a 5.0 or
earlier kernel to check since the issue sometimes doesn't happen for a
week. Then, it happens three times a day.

This is what I usually find in my syslog when the thing happens:
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: SME: Trying to authenticate 
with 02:9f:c2:ab:b6:9f (SSID='incluesion' freq=5240 MHz)
Aug 15 10:47:32 drop kernel: [253016.092764] lanw0: disconnect from AP 
f2:9f:c2:aa:b6:9f for new auth to 02:9f:c2:ab:b6:9f
Aug 15 10:47:32 drop kernel: [253016.104831] lanw0: authenticate with 
02:9f:c2:ab:b6:9f
Aug 15 10:47:32 drop kernel: [253016.113674] lanw0: send auth to 
02:9f:c2:ab:b6:9f (try 1/3)
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.3284] device 
(lanw0): supplicant interface state: completed -> authenticating
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.3284] device 
(p2p-dev-lanw0): supplicant management interface state: completed -> 
authenticati
ng
Aug 15 10:47:32 drop systemd-networkd[875]: lanw0: Lost carrier
Aug 15 10:47:32 drop kernel: [253016.127961] lanw0: 02:9f:c2:ab:b6:9f denied 
authentication (status 53)
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: CTRL-EVENT-AUTH-REJECT 
02:9f:c2:ab:b6:9f auth_type=2 auth_transaction=2 status_code=53
Aug 15 10:47:32 drop wpa_supplicant[1110]: dbus: wpa_dbus_property_changed: no 
property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/0
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.3732] device 
(lanw0): supplicant interface state: authenticating -> disconnected
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.3733] device 
(p2p-dev-lanw0): supplicant management interface state: authenticating -> 
disconn
ected
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.4782] device 
(lanw0): supplicant interface state: disconnected -> scanning
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.4782] device 
(p2p-dev-lanw0): supplicant management interface state: disconnected -> scanning
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: SME: Trying to authenticate 
with f2:9f:c2:aa:b6:9f (SSID='incluesion' freq=2412 MHz)
Aug 15 10:47:32 drop kernel: [253016.470907] lanw0: authenticate with 
f2:9f:c2:aa:b6:9f
Aug 15 10:47:32 drop kernel: [253016.481429] lanw0: send auth to 
f2:9f:c2:aa:b6:9f (try 1/3)
Aug 15 10:47:32 drop wpa_supplicant[1110]: FT: Failed to set PTK to the driver
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: Trying to associate with 
f2:9f:c2:aa:b6:9f (SSID='incluesion' freq=2412 MHz)
Aug 15 10:47:32 drop kernel: [253016.492701] lanw0: authenticated
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.7090] device 
(lanw0): supplicant interface state: scanning -> authenticating
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.7090] device 
(p2p-dev-lanw0): supplicant management interface state: scanning -> 
authenticatin
g
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.7132] device 
(lanw0): supplicant interface state: authenticating -> associating
Aug 15 10:47:32 drop NetworkManager[4151]:   [1565858852.7132] device 
(p2p-dev-lanw0): supplicant management interface state: authenticating -> 
associa
ting
Aug 15 10:47:32 drop kernel: [253016.496648] lanw0: associate with 
f2:9f:c2:aa:b6:9f (try 1/3)
Aug 15 10:47:32 drop kernel: [253016.511399] lanw0: RX ReassocResp from 
f2:9f:c2:aa:b6:9f (capab=0x1431 status=0 aid=1)
Aug 15 10:47:32 drop kernel: [253016.534359] lanw0: associated
Aug 15 10:47:32 drop wpa_supplicant[1110]: dbus: wpa_dbus_property_changed: no 
property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: Associated with 
f2:9f:c2:aa:b6:9f
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: WPA: Key negotiation 
completed with f2:9f:c2:aa:b6:9f [PTK=CCMP GTK=CCMP]
Aug 15 10:47:32 drop wpa_supplicant[1110]: dbus: wpa_dbus_property_changed: no 
property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/0
Aug 15 10:47:32 drop wpa_supplicant[1110]: dbus: wpa_dbus_property_changed: no 
property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/0
Aug 15 10:47:32 drop wpa_supplicant[1110]: lanw0: CTRL-EVENT-CONNECTED - 
Connection to f2:9f:c2:aa:b6:9f completed [id=1 id_str=]
Aug 15 10:47:32 drop systemd-networkd[875]: lanw0: Gained carrier
Aug 15 10:47:3

Bug#886384: rxvt-unicode: font issue with FreeType 2.8 and TrueType fonts

[Vincent Lefevre]

On 2018-01-05 09:10:40 +0100, Vincent Lefevre wrote:
> Package: rxvt-unicode
> Version: 9.22-2
> Severity: important
> 
> Just like xterm and Emacs, rxvt-unicode has font issues with
> FreeType 2.8, which uses different rounding rules for ascender
> and descender for TrueType fonts. 2 consequences:
>   * The window is taller and wider than expected (which can break
> existing configurations and waste screen space).

A workaround for the wide window due to additional spacing between
letters is to use "-letsp -1".

Unfortunately, for the spacing between lines, using "-lsp -1" does
not have any effect.

>   * There sometimes (not always) are blank lines (rows or columns)
> between characters, which is an issue for line-drawing characters.

No issue with the built-in block graphics/line drawing characters
(the default), but some characters, not handled by this code, are
affected, e.g.


(the issue disappears with "-letsp -1") and

⎧
⎪
⎪
⎨
⎪
⎪
⎩

One may consider that supporting negative values with -lsp would
solve this bug (this would first need checking that the expected
blank line is removed).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#934829: kodi: does not use VAAPI

[sacrediou]

Package: kodi
Version: 2:17.6+dfsg1-4+b1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
After debian stretch to buster migration, the CPU usage in Kodi is very high
when playing video content (1080p H264).

When looking kodi's log


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (1000, 'stable-updates'), (1000, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kodi depends on:
ii  kodi-bin   2:17.6+dfsg1-4+b1
ii  kodi-data  2:17.6+dfsg1-4

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:17.6+dfsg1-4
ii  kodi-visualization-spectrum 1.1.1-1

kodi suggests no packages.

-- no debconf information

Bug#934829: kodi: does not use VAAPI

[sacrediou]

Package: kodi
Version: 2:17.6+dfsg1-4+b1
Followup-For: Bug #934829

Ooops,

Missed Kodi's logs :

NOTICE: Creating video codec with codec id: 27
NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: H.264 / AVC / MPEG-4 AVC /
MPEG-4 part 10
NOTICE: Opening stream: 2 source: 256
NOTICE: Closing stream player 3
NOTICE: Opening stream: 6 source: 256
NOTICE: Creating audio stream (codec id: 86056, channels: 2, sample rate:
48000, no pass-through)
ERROR: VAAPI::CheckSuccess error: unknown libva error
NOTICE: VAAPI::Close
NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: H.264 / AVC / MPEG-4 AVC /
MPEG-4 part 10
NOTICE: PulseAudio: Opened device alsa_output.pci-_00_1b.0.iec958-stereo in
pcm mode with Buffersize 150 ms
NOTICE: GL: Selecting Single Pass YUV 2 RGB shader
NOTICE: GL: NPOT texture support detected
NOTICE: GL: Using GL_ARB_pixel_buffer_object
NOTICE: Using GL_TEXTURE_2D
NOTICE: GL: Selecting Single Pass YUV 2 RGB shader
NOTICE: GL: NPOT texture support detected
NOTICE: GL: Using GL_ARB_pixel_buffer_object
WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
WARNING: Previous line repeats 3 times.
NOTICE: CDVDVideoCodecFFmpeg::CDropControl: calculated diff time: 4
NOTICE: CVideoPlayer::CloseFile()
NOTICE: VideoPlayer: waiting for threads to exit
WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
WARNING: Previous line repeats 2 times.

By the way, VAAPI seems to work fine when using VLC with the same video on the
same computer.

I tried using gnome on xorg instead of wayland and the problem is the same.



-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (1000, 'stable-updates'), (1000, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kodi depends on:
ii  kodi-bin   2:17.6+dfsg1-4+b1
ii  kodi-data  2:17.6+dfsg1-4

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:17.6+dfsg1-4
ii  kodi-visualization-spectrum 1.1.1-1

kodi suggests no packages.

-- no debconf information

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

[Thorsten Glaser]

On Thu, 15 Aug 2019, Mark Hindley wrote:

> Can you point me to any official documentation that says packages
> should not depend on systemd-sysv?

No, but why should they? It’s an almost empty package, and it
can be fulfilled by just depending on systemd.

It does not guarantee that systemd is the currently-running init,
nor that this will be so at the next boot.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

[Thorsten Glaser]

On Thu, 15 Aug 2019, Mark Hindley wrote:

> I am now wondering if the prime responsibliity for the system breakage here is
> down to apt's behaviour.
[…]
> At this point apt has failed to remove systemd/241-7 which depends on 
> libsystemd
> (=241-7). Surely it should not then go on to try and remove the systemd
> dependency?

Unsure if that’s apt or dpkg. Plus, the failing prerm is in systemd,
not in libsystemd0.

For dpkg, it makes sense to remove libsystemd0 nevertheless, when
called literally; for apt, it doesn’t. (Interestingly enough,
the dpkg developer has been telling the apt developers for ages
that dpkg now can handle this kind of dependencies, and not to
use the “do what I said and ignore dependencies” mode any more.)

It does make sense to bring the developers of both apt and dpkg
into this, irrelevant of where an improvement can be done, unless
my beer-induced idea I already posted works.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#934830: ffmpeg h264_vaapi ignore -qp options

[Aymeric]

Package: ffmpeg
Version: 7:4.1.3-1
Severity: normal

Dear Maintainer,

When trying to convert a video using h264_vaapi codec there is two way
to define the quality of the videos:
- With the 'qp' parameters (works like crf setting of libx264)
- with bitrate control (using -b:v xk).

Only the bitrate control setting works, the qp parameters is not
working (it seem to be encoding as 'lossless' setting with bitrate more
than 3kbits/s - some test produce bitrate at 60Mbits/s), using the
same 'qp' parameters on Debian Stretch (ffmpeg 3.3.9) works as expected.
Tested on two computers just upgraded to Debian Buster where ffmpeg and
vaapi was working fine.

To reproduce take any video as input and encode with:

$ ffmpeg -vaapi_device /dev/dri/renderD128 -i foo.mp4 \
-vf 'format=nv12,hwupload' -c:V h264_vaapi -qp 23 -an bar.mp4

Change the value of -qp to anything within the range 0 to 51.

You can check the -qp setting of h264_vaapi codec using:
$ ffmpeg -h encoder=h264_vaapi

Unfortunatly I can't try with static build from ffmpeg because of bug
#68 (https://github.com/zimbatm/ffmpeg-static/issues/68).
Neither with version from snapcraft as vaapi doesn't work either.

This issue is probably more on libavcodec side than on ffmpeg.

Thanks.


-- System Information:
Debian Release: 10.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ffmpeg depends on:
ii libavcodec58 7:4.1.3-1
ii libavdevice58 7:4.1.3-1
ii libavfilter7 7:4.1.3-1
ii libavformat58 7:4.1.3-1
ii libavresample4 7:4.1.3-1
ii libavutil56 7:4.1.3-1
ii libc6 2.28-10
ii libpostproc55 7:4.1.3-1
ii libsdl2-2.0-0 2.0.9+dfsg1-1
ii libswresample3 7:4.1.3-1
ii libswscale5 7:4.1.3-1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn ffmpeg-doc 

-- no debconf information

Bug#933185: fai-server: /etc/fai/apt/sources.list should not contain trusted=yes to skip GPG verification

[Christian Seiler]

Hi,

(Sorry, overlooked your email.)

Am 2019-08-12 21:31, schrieb Thomas Lange:

I think we cannot fix it in this way.
gpg --export 2BF8D9FE074BCDE4 may not work, if the key is not already
downloaded and available for gpg. I also do not want to force to
install the package debian-keyring on the fai server.
And we should not create a file when calling fai-make-nfsroot under
/etc which is normally a config file.

The idea is to ship the gpg key directly in the fai-server package.
So I would add the file /etc/fai/apt/trusted.gpg.d/fai-project.gpg to
the package fai-server. What do you think?


Sorry if I wasn't clearer in my bugreport. Yes, I did mean that
you should simply add the fai-project.gpg to the package. The
gpg --export was just a demonstration how to work around this
issue with the current version of FAI.

So yes, if you added the file to the package and removed the
[trusted=yes] in the /etc/fai/apt/sources.list, that would be
perfect.

Thanks!

Best regards,
Christian

Bug#934662: grace: Font mapping breaks with base35 *.t1 fonts

[Nicholas Breen]

On Tue, Aug 13, 2019 at 12:47:07AM -0500, Carlo Segre wrote:
> If the links ending in *.t1 in the /usr/share/grace/fonts/type1/ directory
> are renamed as *.pfb, then grace identifies all the fonts correctly and
> makes them all available with their proper name designations.  This
> indicates that the bug is in the source code for grace which should add a
> search for a fourth variant of the file name, i.e. with *.t1 as the
> extension.

Even worse: it's split between grace and t1lib code, with an awkward
interface between the two.

I'd *like* to solve it this way but only have a partial fix so far.
I'll poke at it further as time permits over the next few days, and
switch to your update-grace-fonts patch if it seems intractable. Thanks!


-- 
Nicholas Breen
nbr...@debian.org

Bug#934831: RM: pylibssh2 -- RoQA; orphaned; dead upstream; no Python 3 support and no reverse deps

[Andrey Rahmatullin]

Package: ftp.debian.org
Severity: normal

Last upstream release in 2011, http://www.wallix.org/pylibssh2-project/ doesn't
work.

Reverse deps checked with dak rm -Rnb python-libssh2

Bug#934832: RM: pygpiv -- RoQA; orphaned; no Python 3 support and no reverse deps

[Andrey Rahmatullin]

Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal

No upstream releases since 2009.

Reverse deps checked with dak rm -Rnb python-gpiv

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#934833: raspi3-firmware: Add custom parameter to config.txt

[Sebastian Fiedler]

Package: raspi3-firmware
Version: 1.20190215-1
Severity: wishlist

Dear Maintainer,

please add an option to add custom parameter to
config.txt

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.19.0-5-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set 
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default 
locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages raspi3-firmware depends on:
ii  dosfstools  4.1-2

raspi3-firmware recommends no packages.

raspi3-firmware suggests no packages.

-- debconf information excluded

diff --git a/debian/default/raspi-firmware b/debian/default/raspi-firmware
index ce65dee..53625e0 100644
--- a/debian/default/raspi-firmware
+++ b/debian/default/raspi-firmware
@@ -48,3 +48,7 @@
 #   screen and on the uart:
 #   CONSOLES="tty0 ttyS1,115200"
 #CONSOLES="auto"
+
+# Create a file "/etc/default/raspi-firmware-custom" to add custom parameter
+# to startup the kernel. Maybe not all options are supported.
+# (see https://www.raspberrypi.org/documentation/configuration/config-txt/)
diff --git a/debian/kernel/postinst.d/z50-raspi-firmware 
b/debian/kernel/postinst.d/z50-raspi-firmware
index b2d0a85..b50fb07 100755
--- a/debian/kernel/postinst.d/z50-raspi-firmware
+++ b/debian/kernel/postinst.d/z50-raspi-firmware
@@ -125,9 +125,17 @@ if [ "$INITRAMFS" != "no" ]; then
 # For details on the initramfs directive, see
 # https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532
 initramfs ${latest_initrd_basename}
+
 EOF
 fi

+firmware_custom="/etc/default/raspi-firmware-custom"
+if [ -f "$firmware_custom" ]; then
+  cat >>/boot/firmware/config.txt 

Bug#934834: konsole: Update konsole to latest upstream version

[Shmerl]

Package: konsole
Version: 4:18.04.0-1
Severity: normal

Dear Maintainer,

Konsole in Debian repos got quite outdated, and upstream accumulated a lot of
bug fixes
and major features like support for extended DECSCUSR escape sequences (helps
for nvim)
and proper window splitting.

See:

* https://bugs.kde.org/show_bug.cgi?id=347323
* https://bugs.kde.org/show_bug.cgi?id=178320

Please upload the latest upstream version (at the time of writing - 19.08.0).

Thanks!



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-rc2 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages konsole depends on:
ii  kio   5.54.1-1
ii  konsole-kpart 4:18.04.0-1
ii  libc6 2.28-10
ii  libkf5completion5 5.54.0-1
ii  libkf5configcore5 5.54.0-2
ii  libkf5configgui5  5.54.0-2
ii  libkf5configwidgets5  5.54.0-1
ii  libkf5coreaddons5 5.54.0-1
ii  libkf5crash5  5.54.0-1
ii  libkf5dbusaddons5 5.54.0-1
ii  libkf5globalaccel55.54.0-1
ii  libkf5i18n5   5.54.0-1
ii  libkf5iconthemes5 5.54.0-1
ii  libkf5kiowidgets5 5.54.1-1
ii  libkf5notifyconfig5   5.54.0-1
ii  libkf5widgetsaddons5  5.54.0-1
ii  libkf5windowsystem5   5.54.0-1
ii  libkf5xmlgui5 5.54.0-1
ii  libqt5core5a  5.11.3+dfsg1-2+b1
ii  libqt5gui55.11.3+dfsg1-2+b1
ii  libqt5widgets55.11.3+dfsg1-2+b1
ii  libstdc++69.1.0-10

konsole recommends no packages.

konsole suggests no packages.

-- no debconf information

Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer

[Louis-Philippe Véronneau]

Control: tag -1 patch

Well, since this is a Team maintained package, I've created a Merge
Request on the Salsa VCS and asked people on IRC to merge and upload it:

https://salsa.debian.org/qt-kde-team/extras/amarok/merge_requests/1/diffs

As stated on Salsa, I've built with this patch on Sid and Testing and
the resulting package depends on libmariadb19 instead of libmariadb18.

From the feedback I've had this should be uploaded soonish.

Cheers!

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#934785: does not include lis.so driver

[Dominique Dumont]

Hi

On mercredi 14 août 2019 22:21:21 CEST you wrote:
> The package fails to include the lis.so module.

As of lcdproc 0.5.9-2, lis module is no longer delivered. (see lcdproc 
changelog) because build dependency on libftdi-dev and libusb-dev were 
removed.

libftdi-dev and libusb-dev are deprecated library with newer replacements. 
Nobody stepped up upstream to port these module to new usb library, so, 
unfortunately, I had to remove these modules.
 
> Which is odd, because I did a local build and lis.so is indeed built
> and included with the 'lcdproc' package.

Probably because libusb-dev libftdi-dev are installed on your system.

All the best

Bug#934835: [lintian] unmet dependency on libio-async-loop-epoll-perl (>= 0.20)@stretch-backports

[Agustin Henze]

Package: lintian
Version: 2.17.0~bpo9+1
Severity: normal

Hi there, last release backported to stretch is uninstallable because it has
unmet dependencies:

root@8329fb73036a:/# apt-get install lintian/stretch-backports
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '2.17.0~bpo9+1' (Debian Backports:stretch-backports [all]) for
'lintian'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 lintian : Depends: libio-async-loop-epoll-perl (>= 0.20) but 0.17-1 is to be
installed
   Recommends: libperlio-gzip-perl but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

--
TiN





signature.asc
Description: OpenPGP digital signature

Bug#934035: ocrmypdf: FTBFS in stretch (failing tests)

[Sean Whitton]

Hello,

On Tue 06 Aug 2019 at 12:31pm -07, James R Barlow wrote:

> The issue here is that we have an old version of ocrmypdf (4.3.5) with a
> backported version of Ghostscript (9.26) and the latter's behavior has
> changed in a way that breaks the test.
>
> I recommend disabling the test and documenting a caveat that certain
> metadata may not be preserved in output files. This is arguably a fairly
> minor loss of functionality.

Thanks.  My intention is to just update ocrmypdf to a newer release.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#905456: Please create new list debian-clojure

[Sean Whitton]

Hello,

On Mon 12 Aug 2019 at 10:37pm -05, Rob Browning wrote:

> Alexander Wirt  writes:
>
>> That bug is still missing any other mails from interested people for that
>> list. Is that mail really consense?
>
> Hmm, I'm not sure what the preferable alternatives might be, so to
> whatever extent my vote is appropriate, I think it'd probably be helpful
> to have a list to discuss Debian Clojure related issues -- if it's not
> too much of a mainenance burden,

I agree.  Thanks!

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#915895: python-limits FTBFS: ERROR: Failure: ImportError (cannot import name b)

[Andrey Rahmatullin]

Control: reassign -1 src:redis-py-cluster/1.3.3-1
Control: severity -1 grave
Control: forwarded -1 https://github.com/Grokzen/redis-py-cluster/issues/295
Control: affects -1 src:python-limits

On Sat, Feb 09, 2019 at 06:57:54PM +0100, Slavko wrote:
> while this of course affects the python-limits build, it is not its
> bug. As one can see, it is caused in test by importing rediscluster:
Exactly. Fixing the bug metadata accordingly.
Work in progress is at
https://github.com/Grokzen/redis-py-cluster/pull/296 and looks promising.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#893009: icu-devtools: pkgdata command segfaults when given -m static

[Scott Talbert]

On Wed, 7 Aug 2019, Scott Talbert wrote:


On Wed, Aug 7, 2019 at 3:57 PM Scott Talbert  wrote:

It would be really helpful if this could get fixed in the stretch 9.10
release.  Is there anything I can do to help make that happen?

Please build and test the proposed package on your system. Then
please report back if it really fixes your problem.

Thanks,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/icu_57.1-6+deb9u3.dsc


I can confirm that building LTFS fails with icu_57.1-6+deb9u2 but succeeds 
with icu_57.1-6+deb9u3.


Just a gentle reminder to please upload this.  :)

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

[Olivier]

Hello,

I have the same bug as Svetlana...

$ sudo modprobe binder_linux# OK
$ sudo modprobe ashmem_linux# OK
$ sudo service anbox-container-manager start# OK
$ ls /var/lib/anbox/
android_amd64.img
(That file was downloaded from https://build.anbox.io/android-images/2018/07/19)

$ sudo service anbox-session-manager start  # NOT OK
Failed to start anbox-session-manager.service: Unit anbox-session 
manager.service not found.


I don't know how to diagnose or to understand more.

--
Olivier

---
$ anbox system-info

version: 0.0~git20190124-1-Debian
cpu:
  arch:  x86
  brand:   Intel(R) Pentium(R) CPU  N3700  @ 1.60GHz
  features:
- aes
os:
  name: Debian GNU/Linux
  version:
  snap-based: false
kernel:
  version: Linux version 4.18.0-2-amd64 (debian-ker...@lists.debian.org) (gcc 
version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.10-2 (2018-11-02)

  binder: true
  ashmem: true
graphics:
  egl:
vendor: Mesa Project
version: 1.4 (DRI2)
extensions:
  - EGL_ANDROID_native_fence_sync
  - EGL_CHROMIUM_sync_control
  - EGL_EXT_create_context_robustness
  - EGL_EXT_image_dma_buf_import
  - EGL_EXT_image_dma_buf_import_modifiers
  - EGL_KHR_config_attribs
  - EGL_KHR_create_context
  - EGL_KHR_create_context_no_error
  - EGL_KHR_fence_sync
  - EGL_KHR_get_all_proc_addresses
  - EGL_KHR_gl_colorspace
  - EGL_KHR_gl_renderbuffer_image
  - EGL_KHR_gl_texture_2D_image
  - EGL_KHR_gl_texture_3D_image
  - EGL_KHR_gl_texture_cubemap_image
  - EGL_KHR_image
  - EGL_KHR_image_base
  - EGL_KHR_image_pixmap
  - EGL_KHR_no_config_context
  - EGL_KHR_reusable_sync
  - EGL_KHR_surfaceless_context
  - EGL_KHR_wait_sync
  - EGL_MESA_configless_context
  - EGL_MESA_drm_image
  - EGL_MESA_image_dma_buf_export
  - EGL_NOK_swap_region
  - EGL_NOK_texture_from_pixmap
  - EGL_NV_post_sub_buffer
  - EGL_WL_bind_wayland_display
  gles2:
vendor: Intel Open Source Technology Center
vendor: OpenGL ES 3.1 Mesa 18.2.8
extensions:
  - GL_EXT_blend_minmax
  - GL_EXT_multi_draw_arrays
  - GL_EXT_texture_filter_anisotropic
  - GL_EXT_occlusion_query_boolean
  - GL_EXT_texture_compression_dxt1
  - GL_EXT_texture_format_BGRA
  - GL_OES_compressed_ETC1_RGB8_texture
  - GL_OES_depth24
  - GL_OES_element_index_uint
  - GL_OES_fbo_render_mipmap
  - GL_OES_mapbuffer
  - GL_OES_rgb8_rgba8
  - GL_OES_standard_derivatives
  - GL_OES_stencil8
  - GL_OES_texture_3D
  - GL_OES_texture_float
  - GL_OES_texture_float_linear
  - GL_OES_texture_half_float
  - GL_OES_texture_half_float_linear
  - GL_OES_texture_npot
  - GL_OES_vertex_half_float
  - GL_EXT_texture_sRGB_decode
  - GL_OES_EGL_image
  - GL_OES_depth_texture
  - GL_OES_packed_depth_stencil
  - GL_EXT_texture_type_2_10_10_10_REV
  - GL_OES_get_program_binary
  - GL_APPLE_texture_max_level
  - GL_EXT_discard_framebuffer
  - GL_EXT_read_format_bgra
  - GL_EXT_frag_depth
  - GL_NV_fbo_color_attachments
  - GL_OES_EGL_image_external
  - GL_OES_EGL_sync
  - GL_OES_vertex_array_object
  - GL_OES_viewport_array
  - GL_ANGLE_texture_compression_dxt3
  - GL_ANGLE_texture_compression_dxt5
  - GL_EXT_robustness
  - GL_EXT_texture_rg
  - GL_EXT_unpack_subimage
  - GL_NV_draw_buffers
  - GL_NV_read_buffer
  - GL_NV_read_depth
  - GL_NV_read_depth_stencil
  - GL_NV_read_stencil
  - GL_EXT_draw_buffers
  - GL_EXT_map_buffer_range
  - GL_KHR_debug
  - GL_KHR_robustness
  - GL_OES_depth_texture_cube_map
  - GL_OES_required_internalformat
  - GL_OES_surfaceless_context
  - GL_EXT_color_buffer_float
  - GL_EXT_separate_shader_objects
  - GL_EXT_shader_integer_mix
  - GL_EXT_tessellation_point_size
  - GL_EXT_tessellation_shader
  - GL_INTEL_performance_query
  - GL_EXT_base_instance
  - GL_EXT_compressed_ETC1_RGB8_sub_texture
  - GL_EXT_copy_image
  - GL_EXT_draw_buffers_indexed
  - GL_EXT_draw_elements_base_vertex
  - GL_EXT_gpu_shader5
  - GL_EXT_polygon_offset_clamp
  - GL_EXT_primitive_bounding_box
  - GL_EXT_shader_io_blocks
  - GL_EXT_texture_border_clamp
  - GL_EXT_texture_buffer
  - GL_EXT_texture_cube_map_array
  - GL_EXT_texture_norm16
  - GL_KHR_blend_equation_advanced
  - GL_KHR_context_flush_control
  - GL_KHR_robust_buffer_access_behavior
  - GL_NV_image_formats
  - GL_OES_copy_image
  - GL_OES_draw_buffers_indexed
  - GL_OES_draw_elements_base_vertex
  - GL_OES_gpu_shader5
  - GL_OES_primitive_bounding_box
  - GL_OES_sample_shading
  - GL_OES_sample_variables
  - GL_OES_shader_io_blocks
  - GL_OES_shader_mu

Bug#934836: Request to upload OpenSSL version 3.0.0 to experimental

[Sakirnth Nagarasa]

Package: openssl
Version: 3.0.0
Severity: wishlist

Hi,

Could someone upload OpenSSL version 3.0.0 to expermiental please. I'm
packaging ngtcp2 and it needs OpenSSL version 3.0.0 + a patch to build
properly. It would be helpful for me when this version of OpenSSL would
be in debian.

Thanks and Cheers,
Sakirnth (Saki)

Bug#934837: gcc-doc-base: GCC 9 is now the default

[Thorsten Glaser]

Package: gcc-doc-base
Version: 8.3.0-1
Severity: important

Please bump gcc-doc-base to follow GCC 9, as gcc-defaults
has just done. Thanks!

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

-- no debconf information