Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

[Steffen Ullrich]

Actually, the fix is probably even simpler.

The bug does not happen with an original libwww. It only happens with an LWP
which contains Debian patches. Specifically the patch
drop-non-blocking-socket.patch causes the problem since it keeps the socket
blocking while the original libwww explicitly sets the socket non-blocking
in _new_socket.
From my understanding of the code the original problem which caused the
patch to be added (#216821) should be no longer relevant since the socket is
actually connected before it is set to non-blocking.

Thus I recommend to just remove this old patch (from 2003) instead of
introducing yet another patch.

Regards,
Steffen

On Sun, May 12, 2019 at 01:11:45AM +0200, gregor herrmann  
wrote:
> On Sat, 11 May 2019 21:56:01 +0200, Steffen Ullrich wrote:
>
> > I think the issue is a  bit different than what was analyzed so far.
> […]
>
> Thank you for this detailed analysis!
>
> > The following small patch for LWP::protocol::http seems to fix the
> > problem for me:
> >
> > --- /usr/share/perl5/LWP/Protocol/http.pm   2019-05-11 
> > 19:05:21.488561325 +
> > +++ lib/LWP/Protocol/http.pm   2019-05-11 19:40:49.332810627 +
> > @@ -374,7 +374,9 @@
> > if (defined($rbits) && $rbits =~ /[^\0]/) {
> > # readable
> > my $buf = $socket->_rbuf;
> > +   my $was_blocking = $socket->blocking(0);
> > my $n = $socket->sysread($buf, 1024, length($buf));
> > +   $socket->blocking(1) if $was_blocking;
> >  unless (defined $n) {
> >  die "read failed: $!" unless  $!{EINTR} || 
> > $!{EWOULDBLOCK} || $!{EAGAIN};
> >  # if we get here the rest of the block will do nothing
>
> I've now tried the following, as per Guilhem's proposal in message
> #126:
>
> Terminal 1:
>
> % openssl req -x509 -keyout /tmp/key.pem -out /tmp/cert.pem -subj 
> /CN=127.0.0.1 -nodes
> % openssl s_server -accept 127.0.0.1:4433 -key /tmp/key.pem -cert 
> /tmp/cert.pem -tls1_3
>
> Terminal 2:
>
> % strace -y -ttt -etrace=select,read,write -o ~/tmp/strace.orig perl 
> -MLWP::UserAgent -e 'LWP::UserAgent->new(ssl_opts => {SSL_ca_file => 
> "/tmp/cert.pem"})->post("https://127.0.0.1:4433;, {data => "foo"})'
>
> and with the patch applied:
>
> % strace -y -ttt -etrace=select,read,write -o ~/tmp/strace.patched perl 
> -MLWP::UserAgent -e 'LWP::UserAgent->new(ssl_opts => {SSL_ca_file => 
> "/tmp/cert.pem"})->post("https://127.0.0.1:4433;, {data => "foo"})'
>
>
> Result:
>
> Terminal 1
>
> Before the patch:
>
> Using default temp DH parameters
> ACCEPT
> -BEGIN SSL SESSION PARAMETERS-
> MH0CAQECAgMEBAITAgQgr5ycydiRESVmPMev7McV6BfGSUqTodBWWKKM08FFNagE
> MOxvDk39ZVjQ0w/KpEvrm839LIrrWeigYwg3ofZJiFoT/Hu9VUbpxzDrx3EOTx3a
> oqEGAgRc11T3ogQCAhwgpAYEBAEAAACuBgIEaCDB8g==
> -END SSL SESSION PARAMETERS-
> Shared 
> ciphers:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:AES128-GCM-SHA256:AES256-SHA:AES128-SHA:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:AES256-SHA256
> Signature Algorithms: 
> ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
> Shared Signature Algorithms: 
> ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224
> Supported Elliptic Groups: X25519:P-256:X448:P-521:P-384
> Shared Elliptic groups: X25519:P-256:X448:P-521:P-384
> ---
> No server certificate CA names sent
> CIPHER is TLS_AES_256_GCM_SHA384
> Secure Renegotiation IS supported
> ERROR
> shutting down SSL
> CONNECTION CLOSED
>
>
> After the patch:
>
> -BEGIN SSL SESSION PARAMETERS-
> MH4CAQECAgMEBAITAgQgm+J0M38juLT4Xzeo8Vtx8JH/JPianuR8GUsyGMV3MfIE
> MIVGCLjmfpGauD0228pm7jpxjhdcZ1KvRW4ag/Xx9MifU4n/zUKVrnUQrivvcOoq
> caEGAgRc11UeogQCAhwgpAYEBAEAAACuBwIFAOBjKP4=
> -END SSL SESSION PARAMETERS-
> Shared 
> ciphers:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:AES128-GCM-SHA256:AES256-SHA:AES128-SHA:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:AES256-SHA256
> Signature Algorithms: 
> 

Bug#928836: wiki.debian.org: add word to localspellingwords

[Paul Wise]

On Sun, May 12, 2019 at 9:21 AM Moshe Piekarski wrote:

> Now would probably be a good time to start including 2020s in 
> https://wiki.debian.org/LocalSpellingWords

Feel free to update this page and close the bug when you are done.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#928372: ITP: golang-github-anacrolix-dms-dev -- a UPnP DLNA Digital Media Server that includes basic video transcoding

[Drew Parsons]

On 2019-05-04 13:25, Drew Parsons wrote:

On 2019-05-04 03:23, Stephen Gelman wrote:

On Fri, 3 May 2019, Drew Parsons wrote:
How important do you consider dlna support in rclone?


In a perfect world it would be nice but I don't think it necessarily
blocks updating it since it's a very new feature.  Maybe upload it
without then file a bug with severity wishlist?


I'll see if it's feasible to disable the dlna with a simple debian 
patch.



dh-make-golang is a useful tool.

$ dh-make-golang estimate github.com/anacrolix/dms
2019/05/12 13:20:59 Bringing github.com/anacrolix/dms to Debian requires 
packaging the following Go packages:

github.com/anacrolix/dms
github.com/anacrolix/ffprobe
  github.com/anacrolix/envpprof
  github.com/anacrolix/missinggo
  github.com/mattn/go-gtk
github.com/mattn/go-pointer


So only a half dozen modules need packaging to get dms and dlna support 
in.  Not the biggest burden in the world.



In the meantime rclone 1.47 is now uploaded in experimental without dlna 
support ("1.47.0.ex1" via uscan (debian/watch) and Files-Excluded in 
debian/copyright).

Bug#928842: l2tpns FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: l2tpns
Version: 2.2.1-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

l2tpns fails to cross build from source, because it does not pass cross
tools to make. The easiest way of fixing that - using dh_auto_build -
does not entirely fix that, because l2tpns also needs LD to be set. The
attached patch fixes both and makes l2tpns cross buildable. Please
consider applying it.

Helmut
diff --minimal -Nru l2tpns-2.2.1/debian/changelog l2tpns-2.2.1/debian/changelog
--- l2tpns-2.2.1/debian/changelog   2016-07-05 12:07:33.0 +0200
+++ l2tpns-2.2.1/debian/changelog   2019-05-12 06:44:30.0 +0200
@@ -1,3 +1,12 @@
+l2tpns (2.2.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ Also pass compiler as LD.
+
+ -- Helmut Grohne   Sun, 12 May 2019 06:44:30 +0200
+
 l2tpns (2.2.1-2) unstable; urgency=low
 
   * Fix log buffer overrun, thanks to Dave Reeve (closes: #817837)
diff --minimal -Nru l2tpns-2.2.1/debian/rules l2tpns-2.2.1/debian/rules
--- l2tpns-2.2.1/debian/rules   2013-06-05 00:16:33.0 +0200
+++ l2tpns-2.2.1/debian/rules   2019-05-12 06:44:30.0 +0200
@@ -20,7 +20,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE)
+   dh_auto_build -- LD='$$(CC)'
#/usr/bin/docbook-to-man debian/l2tpns.sgml > l2tpns.1
 
touch build-stamp

Bug#928844: eureka FTCBFS: wrong strip

[Helmut Grohne]

Source: eureka
Version: 1.24-2
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

eureka fails to cross build from source, because make install strips
with the wrong strip. Beyond breaking cross compilation, this breaks
DEB_BUILD_OPTIONS=nostrip and generation of -dbgsym packages. It is best
to leave all stripping up to dh_strip. The attached patch makes
stripping optional and fixes all of the above. Please consider applying
it.

Helmut
--- eureka-1.24.orig/Makefile
+++ eureka-1.24/Makefile
@@ -140,7 +140,7 @@
 
 INSTALL_DIR=$(DESTDIR)$(PREFIX)/share/eureka
 
-install: stripped
+install: all
 	install -o root -m 755 $(PROGRAM) $(DESTDIR)$(PREFIX)/bin/
 	install -d $(INSTALL_DIR)/games
 	install -d $(INSTALL_DIR)/common

Bug#928846: fwlogwatch FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: fwlogwatch
Version: 1.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

fwlogwatch fails to cross build from source, because it does not pass
cross tools to make. The easiest way of fixing that - using
dh_auto_build - makes fwlogwatch cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru fwlogwatch-1.4/debian/changelog 
fwlogwatch-1.4/debian/changelog
--- fwlogwatch-1.4/debian/changelog 2015-08-24 01:08:47.0 +0200
+++ fwlogwatch-1.4/debian/changelog 2019-05-12 06:55:36.0 +0200
@@ -1,3 +1,10 @@
+fwlogwatch (1.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 12 May 2019 06:55:36 +0200
+
 fwlogwatch (1.4-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #676656)
diff --minimal -Nru fwlogwatch-1.4/debian/rules fwlogwatch-1.4/debian/rules
--- fwlogwatch-1.4/debian/rules 2015-08-22 02:02:41.0 +0200
+++ fwlogwatch-1.4/debian/rules 2019-05-12 06:55:32.0 +0200
@@ -30,7 +30,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE)
+   dh_auto_build
#/usr/bin/docbook-to-man debian/fwlogwatch.sgml > fwlogwatch.1
 
touch build-stamp

Bug#928848: gwaei FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: gwaei
Version: 3.6.2-6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gwaei fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of fixing that - using dh_auto_configure
- makes gwaei cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru gwaei-3.6.2/debian/changelog gwaei-3.6.2/debian/changelog
--- gwaei-3.6.2/debian/changelog2019-03-03 01:26:40.0 +0100
+++ gwaei-3.6.2/debian/changelog2019-05-12 06:42:24.0 +0200
@@ -1,3 +1,10 @@
+gwaei (3.6.2-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 12 May 2019 06:42:24 +0200
+
 gwaei (3.6.2-6) unstable; urgency=medium
 
   * update VCS and email
diff --minimal -Nru gwaei-3.6.2/debian/rules gwaei-3.6.2/debian/rules
--- gwaei-3.6.2/debian/rules2019-03-03 01:26:40.0 +0100
+++ gwaei-3.6.2/debian/rules2019-05-12 06:42:24.0 +0200
@@ -50,9 +50,9 @@
 config-stamp: configure
dh_testdir
dh_autoreconf
-   CFLAGS="$(CFLAGS)" ./configure --prefix=/usr\
+   CFLAGS="$(CFLAGS)" dh_auto_configure -- \
--sysconfdir=/usr/share \
-   --mandir=/usr/share/man \
+   --libdir='$${prefix}/lib' \
--disable-scrollkeeper
# convert png icons to xpm so that we can use them with menu system
#for i in 16x16 24x24 32x32 ; do \

Bug#928845: yamdi FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: yamdi
Version: 1.4-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

yamdi fails to cross build from source, because it does not pass cross
tools to make. The easiest way of doing so - using dh_auto_build - makes
yamdi cross buildable. Please consider applying the attached patch.

Helmut
diff -u yamdi-1.4/debian/rules yamdi-1.4/debian/rules
--- yamdi-1.4/debian/rules
+++ yamdi-1.4/debian/rules
@@ -24,7 +24,7 @@
 build-stamp: configure-stamp 
dh_testdir
 
-   $(MAKE)
+   dh_auto_build
 
touch $@
 
diff -u yamdi-1.4/debian/control yamdi-1.4/debian/control
--- yamdi-1.4/debian/control
+++ yamdi-1.4/debian/control
@@ -2,7 +2,7 @@
 Section: utils
 Priority: extra
 Maintainer: Todd Troxell 
-Build-Depends: debhelper (>= 5), dpatch
+Build-Depends: debhelper (>= 7), dpatch
 Standards-Version: 3.7.2
 XS-Vcs-Hg: http://code.rapidpacket.com/yamdi/
 
diff -u yamdi-1.4/debian/changelog yamdi-1.4/debian/changelog
--- yamdi-1.4/debian/changelog
+++ yamdi-1.4/debian/changelog
@@ -1,3 +1,10 @@
+yamdi (1.4-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 12 May 2019 06:49:57 +0200
+
 yamdi (1.4-2) unstable; urgency=low
 
   * Add dpatch to Build-Depends

Bug#928843: kimwitu FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: kimwitu
Version: 4.6.1-7.2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

kimwitu fails to cross build from source, because it does not pass cross
tools to make. The easiest way of fixing that - using dh_auto_build -
makes kimwitu cross buildable. Please consider applying the attached
patch.

Helmut
diff -u kimwitu-4.6.1/debian/changelog kimwitu-4.6.1/debian/changelog
--- kimwitu-4.6.1/debian/changelog
+++ kimwitu-4.6.1/debian/changelog
@@ -1,3 +1,10 @@
+kimwitu (4.6.1-7.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 12 May 2019 07:10:53 +0200
+
 kimwitu (4.6.1-7.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u kimwitu-4.6.1/debian/rules kimwitu-4.6.1/debian/rules
--- kimwitu-4.6.1/debian/rules
+++ kimwitu-4.6.1/debian/rules
@@ -7,7 +7,7 @@
dh_testdir
 
 # compile the package.
-   cd src; $(MAKE)
+   dh_auto_build --sourcedirectory=src
 
touch build-stamp
 

Bug#928847: libomxil-bellagio-dev: move libomxil-bellagio.pc to a multiarch location

[Helmut Grohne]

Package: libomxil-bellagio-dev
Version: 0.9.3-4.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:libomxcamera

libomxcamera fails to cross build from source, because pkg-config fails
finding libomxil-bellagio.pc. During cross compilation, it searches
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig and /usr/share/pkgconfig, but
not /usr/lib/pkgconfig. Thus the .pc file needs to be moved. The
attached patch implements that in a minimal way. Please consider doing
one of the following:
 * Applying the patch.
 * Adding --libdir='$${prefix}/lib/${DEB_HOST_MULTIARCH}' to ./configure.
 * Bumping to debhelper compat level >= 9 (will insert the --libdir
   flag).

Helmut
diff --minimal -Nru libomxil-bellagio-0.9.3/debian/changelog 
libomxil-bellagio-0.9.3/debian/changelog
--- libomxil-bellagio-0.9.3/debian/changelog2018-09-22 21:56:46.0 
+0200
+++ libomxil-bellagio-0.9.3/debian/changelog2019-05-12 07:01:53.0 
+0200
@@ -1,3 +1,10 @@
+libomxil-bellagio (0.9.3-4.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move libomxil-bellagio.pc to a multiarch location. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 12 May 2019 07:01:53 +0200
+
 libomxil-bellagio (0.9.3-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru libomxil-bellagio-0.9.3/debian/rules 
libomxil-bellagio-0.9.3/debian/rules
--- libomxil-bellagio-0.9.3/debian/rules2018-09-22 21:56:46.0 
+0200
+++ libomxil-bellagio-0.9.3/debian/rules2019-05-12 07:01:52.0 
+0200
@@ -1,5 +1,6 @@
 #!/usr/bin/make -f
 
+include /usr/share/dpkg/architecture.mk
 DEB_SOURCE := $(shell dpkg-parsechangelog | grep Source: | sed -e 's/Source: 
//')
 DEB_VERSION := $(shell dpkg-parsechangelog | grep Version: | sed -e 
's/Version: //')
 DEB_UPSTREAM_VERSION := $(shell echo $(DEB_VERSION) | sed -e 's/-[^-]*$$//')
@@ -23,6 +24,11 @@
dh_strip -plibomxil-bellagio0-components-base 
--dbg-package=libomxil-bellagio0-components-base-dbg
dh_strip --remaining-packages --dbg-package=libomxil-bellagio0-dbg
 
+override_dh_install:
+   dh_install
+   mkdir -p debian/libomxil-bellagio-dev/usr/lib/$(DEB_HOST_MULTIARCH)
+   mv debian/libomxil-bellagio-dev/usr/lib/pkgconfig 
debian/libomxil-bellagio-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig
+
 update-patch-series:
mkdir -p $(CURDIR)/debian/patches
rm -f $(CURDIR)/debian/patches/*.patch

Bug#928418: unblock: preapproval: corekeeper/1.7

[Paul Wise]

Control: tags -1 - moreinfo

On Sat, 2019-05-11 at 16:36 +0200, Paul Gevers wrote:

> Please go ahead and upload to unstable and remove the moreinfo tag
> when it's build.

Uploaded and built by the buildds.

> For reference, if you're confident that an upload meets the freeze
> policy, i.e. it only fixes release critical bugs (or important bugs
> for optional packages), feel free to upload without a pre-approval.
> Most of the time it's easier to review when the package is available
> and it saves a round-trip. That said, if unsure feel free to ask for
> pre-approval.

Ack, in this case I wasn't sure all of the changes were acceptable.

Once the package has reached buster I'd like to do a stable-pu upload.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



signature.asc
Description: This is a digitally signed message part

Bug#928841: pacemaker-common: fails to upgrade from 'testing': dpkg-statoverride: error: an override for '/var/lib/pacemaker/pengine' already exists; aborting

[Andreas Beckmann]

Package: pacemaker-common
Version: 2.0.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../pacemaker-common_2.0.1-3_all.deb ...
  Unpacking pacemaker-common (2.0.1-3) over (2.0.1-2) ...
  Setting up pacemaker-common (2.0.1-3) ...
  addgroup: The group `haclient' already exists as a system group. Exiting.
  The system user `hacluster' already exists. Exiting.
  dpkg-statoverride: error: an override for '/var/lib/pacemaker/pengine' 
already exists; aborting
  dpkg: error processing package pacemaker-common (--configure):
   installed pacemaker-common package post-installation script subprocess 
returned error exit status 2
  Setting up libcom-err2:amd64 (1.45.0-1) ...
  Setting up libss2:amd64 (1.45.0-1) ...
  Setting up e2fsprogs (1.45.0-1) ...
  Installing new version of config file /etc/mke2fs.conf ...
  Processing triggers for libc-bin (2.28-10) ...
  Errors were encountered while processing:
   pacemaker-common


cheers,

Andreas


pacemaker-common_2.0.1-3.log.gz
Description: application/gzip

Bug#928840: boot hangs forever at live-config when libnss-systemd in image

[Steven Monai]

Package: live-config
Version: 5.20190415
Severity: normal

Dear Maintainer,

When the package 'libnss-systemd' is included in a debian-live image,
all attempts to boot the image fail, hanging forever at a particular
point in the boot process. The following message appears in the
console (all on one line), with the kinetic red "cylon" effect on the
left, and a time counter counting up towards infinity on the right:

``[ ***   ] A start job is running for live-config contains the
components that configure a live system during the boot process
(late userspace). (10min 1s / no limit)''

If it matters: I build my debian-live images with 'live-build', and
I include all Standard priority packages with the one-line package
list macro "! Packages Priority standard". In order to work around
this hanging-boot problem, I have been blocking the 'libnss-systemd'
package from my debian-live images via apt pinning.

I have tried adding "live-config.debug" to the boot command
line, but no additional useful information appears in the console.
And, furthermore, I cannot access the debug logs in the live
system, since tty consoles are not yet available at the point that
the live-config service hangs the boot sequence.

I have tried booting in both legacy/BIOS mode and in UEFI mode
(with secure boot disabled), and the behaviour is the always the
same: hanging boot.

I maintain a number of debian-live build recipes in salsa. The
following one can be used to create an ISO image that exhibits the
hanging boot problem (just remove the pin in 'config/apt/preferences'
before running the 'make.sh' script):

https://salsa.debian.org/smonaica-guest/sid-standard-live.git

Best regards,
-S.M.


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/1 CPU core)
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 live-config depends on:
ii  live-config-systemd [live-config-backend]  5.20190415

Versions of packages live-config recommends:
ii  iproute24.20.0-2
ii  keyboard-configuration  1.191
ii  live-config-doc 5.20190415
ii  live-tools  1:20171207
ii  locales 2.28-10
ii  sudo1.8.27-1
ii  user-setup  1.81

Versions of packages live-config suggests:
ii  pciutils  1:3.5.2-5
ii  wget  1.20.1-1.1

-- no debconf information

Bug#928666: Want dgit FAQ

[Sean Whitton]

Hello,

Shall we put this on wiki.debian.org?

The only reason that I can think not to do that is that you and I will
probably write most of the FAQ, and both of us dislike editing web based
wikis.  But, wiki.debian.org seems like the most appropriate place for
an FAQ about a Debian tool...

An alternative would be the "GitLab pages" feature of salsa, where we
push markdown/rst/whatever to a repo and GitLab CI builds HTML and
publishes it.  We already have a dgit project on there.

~ ~ ~

A high priority FAQ item, based on the recent -devel thread, is "How
does usage of dgit benefit Debian's users and downstreams?"

Reference for writing that entry:


And there should perhaps be a link to:


-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#903392: Preferred git branch structure when upstream moves from tarballs to git

[Sean Whitton]

Hello,

On Thu 09 May 2019 at 01:23PM +01, Ian Jackson wrote:

> For your workflow, I see broadly two possibilities, depending what
> representation you use for upstream source code:
>
>  (i) You use upstream tarballs as your representation of the upstream
>  source code, and do not use upstream git branches.
>
>  If this is the case then the benefits for everyone in me
>  implementing #903392 for you, and you then using `dgit
>  push-source', are - frankly - limited.  The resulting dgit git
>  branch would still contain imports of .orig tarballs, rather than
>  the actual upstream git history.
>
>  The user of `dgit clone' would get your *packaging* history,
>  sure, but this is a much more minor benefit.

A benefit not mentioned here is that it gets another class of DDs typing
`dgit push-source` for their uploads.  If getting all DDs typing `dgit
push-source` to upload is going to be how we make source packages
obsolete, that's significant.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#928822: raqm: clean after build deletes docs/html/* which is not regenerated

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

On Sat, May 11, 2019 at 08:56:42PM +0200, Andreas Beckmann wrote:
> raqm/experimental fails to build twice in a row. The first build
> succeeds, but the subsequent clean deletes
> docs/html/* which is not regenerated during the
> second build, fausing this to fail with:
---end quoted text---

I checked the diff between upstream sources 0.5.0 (the one in testing) & 
0.6.0, and I don't see any significant difference in Makefiles or docs/ 
to cause this. It might something in experimental's toolchain ?

-- 
‎أحمد المحمودي (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#928838: cups: Printing from local queue via remote queue not working any more, jobs just vanish

[Robert Senger]

Package: cups
Version: 2.2.10-6
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Setup:

Laptop (Client) running Debian 9/10 and CUPS 2.2.1/2.2.10
Server/Router running Debian 10 and CUPS 2.2.10
Printer Samsung Xpress C480W, LAN/WLAN

Laptop is connected to Server via SSID WLAN_1, Subnet 1
Printer is connected to Server via SSID WLAN_2, Subnet 2
Server should act as a print server running CUPS. Clients (laptop, printer) in
different subnets should not communicate directly.

Printer is configured in CUPS on the server as ipp://printername:631/ipp/print,
with Samsung C48x driver, queue name SAMSUNG, printing test pages from the
server's web interface works fine
Printer is configured in CUPS on the Laptop as
ipps://servername:631/printers/SAMSUNG

With Debian 9 and CUPS 2.2.1 on the Server, this setup worked fine.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Upgraded Server to Debian 10, CUPS 2.2.10

   * What was the outcome of this action?

Printing as describes above stopped working. Jobs sent from the laptop just go
into Nirvana, they vanish and do not show up in the server's queue. The servers
access_log reports success, but printing never happens. No errors are reported
neither on the laptop nor on the server.

   * What outcome did you expect instead?

Printing as before.

   * Workaround(s)

- Downgrading CUPS from 2.2.10 to 2.2.1 (debs from Debian 9) on the Debian 10
server fixes this problem, printing works fine again.
- Using a client.conf file with "ServerName servername" makes printing
possible, but without a local queue there's no queue dialog that can report
failures (emtpy tray, paper jam) on the client
- Printing directly to the printer from the laptop works, but is not desired

So, CUPS 2.2.10 is broken when used as a print server for clients running local
queues.



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

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

Versions of packages cups depends on:
ii  cups-client2.2.10-6
ii  cups-common2.2.10-6
ii  cups-core-drivers  2.2.10-6
ii  cups-daemon2.2.10-6
ii  cups-filters   1.21.6-5
ii  cups-ppdc  2.2.10-6
ii  cups-server-common 2.2.10-6
ii  debconf [debconf-2.0]  1.5.71
ii  ghostscript9.27~dfsg-1
ii  libavahi-client3   0.7-4+b1
ii  libavahi-common3   0.7-4+b1
ii  libc6  2.28-10
ii  libcups2   2.2.10-6
ii  libcupsimage2  2.2.10-6
ii  libgcc11:8.3.0-6
ii  libstdc++6 8.3.0-6
ii  libusb-1.0-0   2:1.0.22-2
ii  poppler-utils  0.71.0-3
ii  procps 2:3.3.15-2

Versions of packages cups recommends:
ii  avahi-daemon 0.7-4+b1
ii  colord   1.4.3-4
ii  cups-filters [ghostscript-cups]  1.21.6-5
ii  printer-driver-gutenprint5.3.1-7

Versions of packages cups suggests:
ii  cups-bsd   2.2.10-6
pn  cups-pdf   
ii  foomatic-db20181217-2
ii  hplip  3.18.12+dfsg0-2
ii  printer-driver-hpcups  3.18.12+dfsg0-2
pn  smbclient  
ii  udev   241-3

-- Configuration Files:
/etc/cups/cupsd.conf [Errno 13] Keine Berechtigung: '/etc/cups/cupsd.conf'

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true

Bug#928836: wiki.debian.org: add word to localspellingwords

[Moshe Piekarski]

Package: wiki.debian.org
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Now would probably be a good time to start including 2020s in 
https://wiki.debian.org/LocalSpellingWords

- -- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
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/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJNBAEBCAA3FiEEXbk7X2RxJi0NGP5lMn/Nf3K/IoEFAlzXc/kZHGRlYmlhbi5i
dWdzQG1lbGFjaGltLm5ldAAKCRAyf81/cr8igTSAEACGhNQSEJ3q+sbvB26AM/d/
xeCLmHaLmMZbCj9K7neUDLNMAW5LYyFmdzTUsKghAu09iWaf6SLaX2i3WWCePjTG
MZka+jSTI2YCXCn+xbTwFcvmcLk+J3LFCrdzaxfS7xPYr+Ai6Ixng4j/0LMPJYIK
5EMjHyyflx+xvkV11KJxR5ca3Ryy8satJRXBWve3PvASzYiMTJmFzzetuoUhexdW
ug1Gvmh2F7vIGpdXghWA9Ziwhxgs1MW0HQ+lpzOHNNhwDD/73/L1w9VAGwY0iWr8
/VXxIOEEa2ec5h519Rew2DQ7O2ULxViqd5EAf0/vp+1ettw35D1bmDFskhq+nCIg
UNBvDriBkmQP8bYFnHyQs54G+9veAO0ZEhdPHgfBGK373UBYzSntlB/7TkEYBwsm
pfEhlnxMv7KULTbsJ7nhanqcwq65ddqdqd110CMPbQ180qVjYldwR5CoVnMdHtOM
sNU6y1iKQfjJJ7l+G1F2pv8NoKFxRJtG9QDENG8ipM2ZFlRxVqfev0mXqMdo/eou
G3lWpU5uwGDlSuN+4qnKLPt68Z0KnsI1w0PZH/fdchYejeyeTLoZF/PwRpNAxSlF
vrgFJH4z00lGyPm5cd0ZmzqbAtENocqwOhAsOjHGqxyj8Kug7tcaa/ShKmdnm26K
mfkHdqTAy3ntrhoy+57lmQ==
=+RH6
-END PGP SIGNATURE-

Bug#928554: dgit-nmu-simple should give an example of generating a patches-unapplied nmudiff

[Sean Whitton]

Hello Sam,

On Mon 06 May 2019 at 10:31PM -04, Sam Hartman wrote:

> It's unclear that we actually have a standard on whether an nmudiff
> should be patches-applied or patches-unapplied.

debdiff generates patches-applied diffs by default, and nmudiff from
devscripts calls debdiff, so that's our de facto standard, so far as I
can tell.

I agree that having the changes shown twice, as a change to
debian/patches and as a change to the upstream source, makes reviewing
harder.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#928503: Want "dgit reportbug" to submit a patch, or something

[Sean Whitton]

Hello,

On Mon 06 May 2019 at 11:33AM +01, Ian Jackson wrote:

> Package: dgit
> Version: 8.4
> Severity: wishlist
>
> 08:08  Diziet, spwhitton: would it make sense for dgit to "support"
>change submission? dgit-user "SHARING YOUR WORK" seems to leave
>too much manual to me. would "dgit reportbug" make sense as a
>means to invoke reportbug with the right source, version,
>template, attachment? or maybe integrate with devscripts/salsa
>mr? not sure.
> 08:10  it seems to me that a primary purpose of dgit is to deemphasize
>package ownership by making the interaction with packages more
>uniform. (<- that seems very valuable to me)
> 08:11  while it makes source packages more accessible to
>non-maintainers, it doesn't make contribution significantly
>easiert it seems.
>
> Hi.  Thanks for your suggestion.
>
> I agree that something like this would be nice.  I'm not sure if it
> should be part of dgit.  It has the same issue as "dgit nmudiff" that
> it does not involve source packages.  But maybe this is just me being
> overly picky.  Certainly this should exist and the dgit source package
> is a good place for it.

What seems to be wanted here is something of a combination, or wrapper,
of three tools: git-format-patch(1), git-send-email(1) and reportbug(1).

I think that in the vast majority of cases this tool would produce the
needed output even if your git tree was not obtained with dgit clone, so
I would hope that it could be completely decoupled from dgit.

(so, I would rather put it in devscripts, but that is unimportant)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#928835: 2.3.6 available upstream!

[積丹尼 Dan Jacobson]

Package: linklint
Version: 2.3.5-5.1
Severity: important

As mentioned in #425632
2.3.6 is available in
http://linklint.org/download/
ever since 2002.

Bug#928834: Allow just

[積丹尼 Dan Jacobson]

Package: linklint
Version: 2.3.5-5.1

Can I please just use https://stackoverflow.com/questions/484719/should-i-make-html-anchors-with-name-or-id

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

[gregor herrmann]

On Sat, 11 May 2019 21:56:01 +0200, Steffen Ullrich wrote:

> I think the issue is a  bit different than what was analyzed so far.
[…]

Thank you for this detailed analysis!

> The following small patch for LWP::protocol::http seems to fix the
> problem for me:
> 
> --- /usr/share/perl5/LWP/Protocol/http.pm   2019-05-11 19:05:21.488561325 
> +
> +++ lib/LWP/Protocol/http.pm   2019-05-11 19:40:49.332810627 +
> @@ -374,7 +374,9 @@
> if (defined($rbits) && $rbits =~ /[^\0]/) {
> # readable
> my $buf = $socket->_rbuf;
> +   my $was_blocking = $socket->blocking(0);
> my $n = $socket->sysread($buf, 1024, length($buf));
> +   $socket->blocking(1) if $was_blocking;
>  unless (defined $n) {
>  die "read failed: $!" unless  $!{EINTR} || 
> $!{EWOULDBLOCK} || $!{EAGAIN};
>  # if we get here the rest of the block will do nothing

I've now tried the following, as per Guilhem's proposal in message
#126:

Terminal 1:

% openssl req -x509 -keyout /tmp/key.pem -out /tmp/cert.pem -subj /CN=127.0.0.1 
-nodes
% openssl s_server -accept 127.0.0.1:4433 -key /tmp/key.pem -cert /tmp/cert.pem 
-tls1_3

Terminal 2:

% strace -y -ttt -etrace=select,read,write -o ~/tmp/strace.orig perl 
-MLWP::UserAgent -e 'LWP::UserAgent->new(ssl_opts => {SSL_ca_file => 
"/tmp/cert.pem"})->post("https://127.0.0.1:4433;, {data => "foo"})'

and with the patch applied:

% strace -y -ttt -etrace=select,read,write -o ~/tmp/strace.patched perl 
-MLWP::UserAgent -e 'LWP::UserAgent->new(ssl_opts => {SSL_ca_file => 
"/tmp/cert.pem"})->post("https://127.0.0.1:4433;, {data => "foo"})'


Result:

Terminal 1

Before the patch:

Using default temp DH parameters
ACCEPT
-BEGIN SSL SESSION PARAMETERS-
MH0CAQECAgMEBAITAgQgr5ycydiRESVmPMev7McV6BfGSUqTodBWWKKM08FFNagE
MOxvDk39ZVjQ0w/KpEvrm839LIrrWeigYwg3ofZJiFoT/Hu9VUbpxzDrx3EOTx3a
oqEGAgRc11T3ogQCAhwgpAYEBAEAAACuBgIEaCDB8g==
-END SSL SESSION PARAMETERS-
Shared 
ciphers:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:AES128-GCM-SHA256:AES256-SHA:AES128-SHA:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:AES256-SHA256
Signature Algorithms: 
ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
Shared Signature Algorithms: 
ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224
Supported Elliptic Groups: X25519:P-256:X448:P-521:P-384
Shared Elliptic groups: X25519:P-256:X448:P-521:P-384
---
No server certificate CA names sent
CIPHER is TLS_AES_256_GCM_SHA384
Secure Renegotiation IS supported
ERROR
shutting down SSL
CONNECTION CLOSED


After the patch:

-BEGIN SSL SESSION PARAMETERS-
MH4CAQECAgMEBAITAgQgm+J0M38juLT4Xzeo8Vtx8JH/JPianuR8GUsyGMV3MfIE
MIVGCLjmfpGauD0228pm7jpxjhdcZ1KvRW4ag/Xx9MifU4n/zUKVrnUQrivvcOoq
caEGAgRc11UeogQCAhwgpAYEBAEAAACuBwIFAOBjKP4=
-END SSL SESSION PARAMETERS-
Shared 
ciphers:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:AES128-GCM-SHA256:AES256-SHA:AES128-SHA:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:AES256-SHA256
Signature Algorithms: 
ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
Shared Signature Algorithms: 
ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224
Supported Elliptic Groups: X25519:P-256:X448:P-521:P-384
Shared Elliptic groups: X25519:P-256:X448:P-521:P-384
---
No server certificate CA names sent
CIPHER is TLS_AES_256_GCM_SHA384
Secure Renegotiation IS supported
POST / HTTP/1.1
TE: deflate,gzip;q=0.3
Connection: TE, close
Host: 127.0.0.1:4433
User-Agent: libwww-perl/6.36
Content-Length: 8
Content-Type: application/x-www-form-urlencoded

data=fooERROR
shutting down SSL
CONNECTION CLOSED


So in the second case, the POST actually 

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

[Norbert Preining]

On Sat, 11 May 2019, Hilmar Preuße wrote:
> Is even in unstable a rather huge package. Do you known, why Karl made
> this step?

Not Karl, Petr Olsak, the author of cstex.

> I personally tend to test, which langs are really needed, although I
> have only little hope, that it is significantly smaller than -all.

You can read from the diff which languages are needed, then one needs to
search the respective packages ...

I won't have time for that in the next days, and then travelling to
Europe ... we will see

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#928621: Old software

[plshelpme19132]

I believe it may indeed be abandoned upstream. However, a package doesn't exist 
for it yet and I've only seen one minor bug that doesn't affect the 
functionality of the software. Packaging it would still be useful since there 
isn't another Windows like taskbar for XFCE in the Debian repositories.

> Hi,
>
> The last commit for this software is 6 years old. I know that mature
> software doesn't need update, but I doubt this is the case here. Maybe
> it is abandoned upstream?
>
> Adrien

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

[Hilmar Preuße]

On 11.05.19 18:41, Norbert Preining wrote:
> On Sat, 11 May 2019, Hilmar Preuße wrote:

Hi,

>> ! I can't find file `hyph-en-gb'.
> 
> indeed, cstex switched to load *loads* of patterns in 3/2019. What a
> pain. See
> http://git.texlive.info/texlive/commit/?id=e6ecf62a1727571cc47129fa4b4e198eadbe2ed3
> 
> That needs some serious rework ... I tend to depend on texlive-lang-all
> ..
> 
root@amd64-sid:~# apt install texlive-lang-all

0 upgraded, 27 newly installed, 0 to remove and 0 not upgraded.
Need to get 467 MB of archives.
After this operation, 1,055 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Is even in unstable a rather huge package. Do you known, why Karl made
this step?
I personally tend to test, which langs are really needed, although I
have only little hope, that it is significantly smaller than -all.

H.
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#928827: [Pkg-javascript-devel] Bug#928827: libjs-jquery: Minified version of jquery.js (jquery.min.js) throws syntax error

[Xavier]

Control: fixed -1 3.1.1-1
Control: notfound -1 1.7.2+dfsg-3.2
Control: tags -1 confirmed

Le 11/05/2019 à 21:52, Harald Oest a écrit :
> Package: libjs-jquery
> Version: 1.7.2+dfsg-3.2+deb8u6
> Severity: normal
> 
> Dear Maintainer,
> 
> the minified jquery library ('/usr/share/javascript/jquery/jquery.min.js') 
> crashes with error 'SyntaxError: nothing to repeat' (as reported by Firefox 
> JS console).
> 
> Step to reproduce this behaviour is to include the library and initialize 
> jquery, e.g.
> 
> 
> 
>$(function() {
>console.log( "Hi, i'm jquery!" );
>});
> 
> 
> The not-minified version ('/usr/share/javascript/jquery/jquery.js') works 
> just well.
> 
> Bests
> 
> Harald

Thanks for this report. Here is a simple script to test jquery files:

  #!/bin/sh
  JQUERY=$1
  if test "$JQUERY" = ""; then
echo "Usage $0 /path/to/jquery" >&2
exit 1
  fi
  echo '
  
  NOK
  
  
  $("#d").text("OK");
  
  
  ' >/tmp/index.html
  firefox /tmp/index.html

Only deb8u* versions are affected by this bug (oldstable only)

Bug#928833: RFS: blastem/0.6.3.1-1 -- Fast and accurate Genesis emulator

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "blastem"

 * Package name: blastem
   Version : 0.6.3.1-1
   Upstream Author : Michael Pavone 
 * URL : https://www.retrodev.com/blastem
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  blastem - Fast and accurate Genesis emulator

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/blastem

  Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/blastem/blastem_0.6.3.1-1.dsc

  More information about blastem can be obtained from 
https://gitlab.com/coringao/blastem.

  Changes since the last upload:

  * New upstream release
  * Fix FTCBFS: Thanks 'Helmut Grohne' (Closes:926498)
+ debian/rules: Let dh_auto_build pass cross tools to make

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#928832: [PATCH] elfutils: FTBFS on riscv64

[Karsten Merker]

Source: elfutils
Version: 0.176-1
Severity: important
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello Kurt,

elfutils currently FTBFS for riscv64 and this is the last remaining
blocker to get a working debian-installer for riscv64.  As already
discussed together with elfutils upstream, there is a workaround that
requires only a one-line change in a riscv-specific file plus
extending the existing architecture-specific build-dependency on
libc6-dbg for [powerpc powerpcspe ppc64 ppc64el armel armhf arm64
sparc64] to also include riscv64.

I would therefore like to ask you to upload a version of elfutils
with the attached patch to unstable.  The patch should pose no
problem with the freeze as it only touches an arch-specific source
file for a non-release architecture and doesn't have any effect at
all on any release architecture.  At the same time it is very
important for the riscv64 port as without the patch we cannot make
progress with d-i on riscv64, and having a working d-i is a
significant milestone for the riscv64 port.

Regards,
Karsten
-- 
Ich widerspreche hiermit ausdrücklich der Nutzung sowie der
Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung
sowie der Markt- oder Meinungsforschung.
diff -Nur elfutils-0.176/debian/control elfutils-0.176.patched/debian/control
--- elfutils-0.176/debian/control
+++ elfutils-0.176.patched/debian/control
@@ -1,7 +1,7 @@
 Source: elfutils
 Priority: optional
 Maintainer: Kurt Roeckx 
-Build-Depends: debhelper (>= 9), autotools-dev, autoconf, automake, bzip2, zlib1g-dev, zlib1g-dev:native, libbz2-dev, liblzma-dev, m4, gettext, autoconf, automake, gawk, dpkg-dev (>= 1.16.1~), gcc-multilib [any-amd64 sparc64] , libc6-dbg [powerpc powerpcspe ppc64 ppc64el armel armhf arm64 sparc64], flex, bison
+Build-Depends: debhelper (>= 9), autotools-dev, autoconf, automake, bzip2, zlib1g-dev, zlib1g-dev:native, libbz2-dev, liblzma-dev, m4, gettext, autoconf, automake, gawk, dpkg-dev (>= 1.16.1~), gcc-multilib [any-amd64 sparc64] , libc6-dbg [powerpc powerpcspe ppc64 ppc64el armel armhf arm64 sparc64 riscv64], flex, bison
 Build-Conflicts: autoconf2.13, automake1.4
 Standards-Version: 4.1.0
 Section: libs
diff -Nur elfutils-0.176/debian/patches/riscv-retval-workaround.patch elfutils-0.176.patched/debian/patches/riscv-retval-workaround.patch
--- elfutils-0.176/debian/patches/riscv-retval-workaround.patch	1970-01-01 01:00:00.0 +0100
+++ elfutils-0.176.patched/debian/patches/riscv-retval-workaround.patch	2019-05-11 20:26:06.736089789 +0200
@@ -0,0 +1,11 @@
+--- a/backends/riscv_retval.c
 b/backends/riscv_retval.c
+@@ -111,7 +111,7 @@
+ 		   Dwarf_Die *arg1 __attribute__ ((unused)))
+ {
+   /* ??? */
+-  return 1;
++  return 0;
+ }
+ 
+ static int
diff -Nur elfutils-0.176/debian/patches/series elfutils-0.176.patched/debian/patches/series
--- elfutils-0.176/debian/patches/series
+++ elfutils-0.176.patched/debian/patches/series
@@ -11,3 +11,4 @@
 ignore_strmerge.diff
 disable_werror.patch
 mips_cfi.patch
+riscv-retval-workaround.patch

Bug#928831: mgen FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: mgen
Version: 5.02.b+dfsg1-2.2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mgen fails to cross build from source, because it does not pass cross
tools to make. The easiest way of fixing that - using dh_auto_build -
does not make mgen cross buildable, because mgen stores the C++ compiler
in the CC variable, which is normally used for the C compiler. Renaming
the variable is necessary here. The attached patch makes mgen cross
buildable. Please consider applying it.

Helmut
diff --minimal -Nru mgen-5.02.b+dfsg1/debian/changelog 
mgen-5.02.b+dfsg1/debian/changelog
--- mgen-5.02.b+dfsg1/debian/changelog  2018-11-10 04:53:51.0 +0100
+++ mgen-5.02.b+dfsg1/debian/changelog  2019-05-11 22:08:53.0 +0200
@@ -1,3 +1,12 @@
+mgen (5.02.b+dfsg1-2.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ Pass C++ compiler as CC.
+
+ -- Helmut Grohne   Sat, 11 May 2019 22:08:53 +0200
+
 mgen (5.02.b+dfsg1-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru mgen-5.02.b+dfsg1/debian/rules 
mgen-5.02.b+dfsg1/debian/rules
--- mgen-5.02.b+dfsg1/debian/rules  2018-11-10 04:53:51.0 +0100
+++ mgen-5.02.b+dfsg1/debian/rules  2019-05-11 22:08:53.0 +0200
@@ -11,7 +11,7 @@
 endif
 
 override_dh_auto_build:
-   cd makefiles && make -f $(MAKEFILE)
+   dh_auto_build --sourcedirectory=makefiles --buildsystem=makefile -- -f 
$(MAKEFILE) CC='$$(CXX)'
 
 override_dh_auto_clean:
cd makefiles && make -f $(MAKEFILE) clean

Bug#928830: libkaz FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: libkaz
Version: 1.21-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libkaz fails to cross build from source, because it does not pass cross
tools to make. The easiest way of doing so - using dh_auto_build - makes
libkaz cross buildable. Please consider applying the attached patch.

Helmut
diff --minimal -Nru libkaz-1.21/debian/changelog libkaz-1.21/debian/changelog
--- libkaz-1.21/debian/changelog2013-08-17 14:21:32.0 +0200
+++ libkaz-1.21/debian/changelog2019-05-11 21:43:20.0 +0200
@@ -1,3 +1,10 @@
+libkaz (1.21-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 11 May 2019 21:43:20 +0200
+
 libkaz (1.21-2) unstable; urgency=low
 
   * set CFLAGS properly in debian/rules
diff --minimal -Nru libkaz-1.21/debian/rules libkaz-1.21/debian/rules
--- libkaz-1.21/debian/rules2013-08-17 14:21:32.0 +0200
+++ libkaz-1.21/debian/rules2019-05-11 21:43:19.0 +0200
@@ -12,7 +12,7 @@
 CFLAGS := $(shell dpkg-buildflags --get CFLAGS) -fPIC -I$(CURDIR)
 
 override_dh_auto_build:
-   make -f Makefile.gcc CFLAGS="$(CFLAGS)" libkaz.a libkaz.so.1.0.0
+   dh_auto_build --buildsystem=makefile -- -f Makefile.gcc 
CFLAGS="$(CFLAGS)" libkaz.a libkaz.so.1.0.0
 
 build:
dh build

Bug#928828: kopano-webapp-common: leaves broken symlink after purge: /etc/php/7.3/apache2/conf.d/20-mapi.ini -> /etc/php/7.3/mods-available/mapi.ini

[Andreas Beckmann]

Package: kopano-webapp-common
Version: 3.5.3+dfsg1-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

1m16.5s ERROR: FAIL: Broken symlinks:
  /etc/php/7.3/apache2/conf.d/20-mapi.ini -> 
/etc/php/7.3/mods-available/mapi.ini


cheers,

Andreas


kopano-webapp-common_3.5.3+dfsg1-1.log.gz
Description: application/gzip

Bug#928829: jazip FTCBFS: does not pass cross tools to make

[Helmut Grohne]

Source: jazip
Version: 0.34-15.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

jazip fails to cross build from source, because it does not pass cross
tools to make. The easiest way of doing so - using dh_auto_build - makes
jazip cross buildable. Please consider applying the attached patch.

Helmut
diff --minimal -Nru jazip-0.34/debian/changelog jazip-0.34/debian/changelog
--- jazip-0.34/debian/changelog 2011-12-14 04:42:39.0 +0100
+++ jazip-0.34/debian/changelog 2019-05-11 21:46:07.0 +0200
@@ -1,3 +1,10 @@
+jazip (0.34-15.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 11 May 2019 21:46:07 +0200
+
 jazip (0.34-15.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff --minimal -Nru jazip-0.34/debian/rules jazip-0.34/debian/rules
--- jazip-0.34/debian/rules 2010-05-28 01:50:52.0 +0200
+++ jazip-0.34/debian/rules 2019-05-11 21:46:06.0 +0200
@@ -17,7 +17,7 @@
 
 build:
dh_testdir
-   make shared CFLAGS="$(CFLAGS)"
+   dh_auto_build -- shared CFLAGS="$(CFLAGS)"
touch build
 
 clean:

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

[Steffen Ullrich]

I think the issue is a  bit different than what was analyzed so far.
As far as I can see it has nothing to do with SSL_MODE_AUTO_RETRY but
instead is caused by expectations on the behavior of select which are wrong
with TLS 1.3.

I've added some more debugging to IO::Socket::SSL and what I saw was:

- With TLS 1.2 LWP did first a write to send the request and then a read to
  read the response - that's expected.
- With TLS 1.3 LWP first tried to read the response and then hang there,
  i.e. no request was even send to the server. This is obviously not what is
  expected.

The reason for this is that LWP::protocol::http::request does not actually
try to write the request first. Instead it creates a select-loop to wait for
both read and write events on the socket and then acts based on what event
select returns.

The obvious expectation is, that there is nothing to read first but that
it will be able to write the request. After the request is sent it will
disable selecting for write-events and only care about reads.

Only, with TLS 1.3 this expectation is wrong.
Up to TLS 1.2 issuing session tickets by the server were part of the TLS
handshake. With TLS 1.3 this is no longer the case and these are send after
the TLS handshake is done. This means that the initial select will actually
trigger a read-event since there are actual data to read on the underlying
socket: the session tickets send by the server.
Only, these are no application data. But sysread on a blocking socket is
supposed to only return if there was at least 1 byte read or if the peer
closed the connection or if a permanent error occured. And since no
application data were send it just hangs.

I don't see how this can be fixed in IO::Socket::SSL only since the real
problem is that sysread is called at this stage (i.e. no request sent yet)
in the first place. Instead the code which is making the wrong assumptions
about select need to be fixed, so that sysread either not get called at this
stage or at least not get called with blocking.

The following small patch for LWP::protocol::http seems to fix the
problem for me:

--- /usr/share/perl5/LWP/Protocol/http.pm   2019-05-11 19:05:21.488561325 
+
+++ lib/LWP/Protocol/http.pm   2019-05-11 19:40:49.332810627 +
@@ -374,7 +374,9 @@
if (defined($rbits) && $rbits =~ /[^\0]/) {
# readable
my $buf = $socket->_rbuf;
+   my $was_blocking = $socket->blocking(0);
my $n = $socket->sysread($buf, 1024, length($buf));
+   $socket->blocking(1) if $was_blocking;
 unless (defined $n) {
 die "read failed: $!" unless  $!{EINTR} || $!{EWOULDBLOCK} 
|| $!{EAGAIN};
 # if we get here the rest of the block will do nothing


Regards,
Steffen

Bug#928827: libjs-jquery: Minified version of jquery.js (jquery.min.js) throws syntax error

[Harald Oest]

Package: libjs-jquery
Version: 1.7.2+dfsg-3.2+deb8u6
Severity: normal

Dear Maintainer,

the minified jquery library ('/usr/share/javascript/jquery/jquery.min.js') 
crashes with error 'SyntaxError: nothing to repeat' (as reported by Firefox JS 
console).

Step to reproduce this behaviour is to include the library and initialize 
jquery, e.g.



   $(function() {
   console.log( "Hi, i'm jquery!" );
   });


The not-minified version ('/usr/share/javascript/jquery/jquery.js') works just 
well.

Bests

Harald

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

Kernel: Linux 3.16.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

libjs-jquery depends on no packages.

Versions of packages libjs-jquery recommends:
ii  javascript-common  11

libjs-jquery suggests no packages.

-- no debconf information

Bug#928826: 'module' function not defined in interactive non-login shells

[Xavier Delaruelle]

Block 928826 with 814358

>From my analysis, it seems this issue is related to dash and the removal of
bash shell functions performed by this shell. As dash shell is run at some
step of the graphical desktop environment initialization, shbash shell
function defined in earlier stage are dropped. See
https://bugs.debian.org/814358 for details.

Bug#928826: 'module' function not defined in interactive non-login shells

[Xavier Delaruelle]

Package: environment-modules
Version: 4.2.2-1

environment-modules package installs the /etc/profile.d/modules.sh script
to be initialized in interactive shells (like those obtained when running a
terminal in a graphical session).

The main part of this initialization is the definition of the 'module'
shell function, which is set for export in order to be found in sub-shells.

In a graphical desktop environment, when a bash shell is obtained via a
terminal application like gnome-terminal or xterm, the 'module' shell
function is found undefined although /etc/profile.d/modules.sh is correctly
executed during the initialization of the graphical desktop environment.

Steps to reproduce the issue:

1. apt-get install environment-modules
2. disconnect the current desktop session
3. log-in to get a new desktop session
4. start a terminal app (like gnome-terminal or xterm)
5. in this terminal app, try 'module --version'

As a result, a 'command not found' error is obtained. Whereas the 'module'
shell function is expected to be found.

Bug#928825: environment-modules relies on /usr/bin/tclsh which may not be installed

[Xavier Delaruelle]

Package: environment-modules
Version: 4.2.2-1

When installing environment-modules on a fresh system (with no Tcl package
pre-installed):

  $ sudo apt-get install environment-modules
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
libtcl8.6 tcl8.6
  Suggested packages:
tcl-tclreadline
  The following NEW packages will be installed:
environment-modules libtcl8.6 tcl8.6
  0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1544 kB of archives.
  After this operation, 5261 kB of additional disk space will be used.
  ...

This installation triggers installation of tcl8.6. However, scripts in
environment-modules package rely on /usr/bin/tclsh, not on
/usr/bin/tclsh8.6.

So if tcl package is not installed, it leads to issue:

  $ source /etc/profile.d/modules.sh
  bash: /usr/bin/tclsh: No such file or directory

Bug#928824: s3ql: Please release s3ql 3.1 with buster for Google OAuth compatibility

[David Gilman]

Package: s3ql
Version: 3.0+dfsg-1
Severity: important

Dear Maintainer,

Can you please lobby the Debian release powers that be to allow 3.1 to
be released with Buster? The fix to s3ql_oauth_client is important
enough that I feel it should be shipped with the release. Important
functionality of this package is broken if a new release is not made.

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
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)
LSM: AppArmor: enabled

Versions of packages s3ql depends on:
ii  fuse   2.9.9-1
ii  libc6  2.28-10
ii  libjs-sphinxdoc1.8.4-1
ii  libsqlite3-0   3.27.2-2
ii  procps 2:3.3.15-2
ii  psmisc 23.2-1
ii  python33.7.2-1
ii  python3-apsw   3.24.0-r1-1
ii  python3-cryptography   2.6.1-3
ii  python3-defusedxml 0.5.0-2
ii  python3-dugong 3.7.4+dfsg-1
ii  python3-llfuse 1.3.6+dfsg-1
ii  python3-pkg-resources  40.8.0-1
ii  python3-requests   2.21.0-1

Versions of packages s3ql recommends:
ii  python3-systemd  234-2+b1

s3ql suggests no packages.

-- no debconf information

Bug#928823: codfis FTCBFS: non-standard compiler variable

[Helmut Grohne]

Source: codfis
Version: 0.4.7-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

codfis fails to cross build from source, because its Makefile uses the
non-standard CPP variable for the C++ compiler while dh_auto_build
passes it as CXX. Renaming the variable fixes the cross build. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru codfis-0.4.7/debian/changelog codfis-0.4.7/debian/changelog
--- codfis-0.4.7/debian/changelog   2012-01-16 16:11:21.0 +0100
+++ codfis-0.4.7/debian/changelog   2019-05-11 21:34:21.0 +0200
@@ -1,3 +1,10 @@
+codfis (0.4.7-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Rename C++ compiler to CPP. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 11 May 2019 21:34:21 +0200
+
 codfis (0.4.7-2) unstable; urgency=low
 
   * Add Italian name for greater probabilities to be found in
diff --minimal -Nru codfis-0.4.7/debian/rules codfis-0.4.7/debian/rules
--- codfis-0.4.7/debian/rules   2012-01-16 16:11:21.0 +0100
+++ codfis-0.4.7/debian/rules   2019-05-11 21:34:20.0 +0200
@@ -6,3 +6,6 @@
 
 %:
dh $@
+
+override_dh_auto_build:
+   dh_auto_build -- 'CPP=$$(CXX)'

Bug#928738: closed by Brian Potkin (Re: Bug#928738: printer-driver-cups-pdf Still Produces PDF Files that Lack Searchable Text and are Unusable with pdftotext)

[Neil R. Ormos]

Brian Potkin wrote:
> Neil Ormos wrote:

>> I have no idea why the new print queue including the
>> pdftops-renderer=pdftocairo option was not established, as
>> expected, during the original installation, by the
>> printer-driver-cups-pdf.postinst script.  I wonder if, somehow,
>> the old PDF queue was not fully removed when I removed the old
>> printer-driver-cups-pdf (2.6.1-22) package.

> I can reproduce your experience on unstable. Purged
> printer-driver-cups-pdf. Installed the stretch package and then
> upgraded. The stretch print queue was left intact, so the renderer
> option was not applied. "Skipped automatic creation of the PDF
> queue" was displayed onscreen.

> Any fix to the package is above my pay grade and is for a maintainer
> to deal with. I hope it can make it into buster.

Brian:

Thanks very much for your help and for reopening and retitling this bug report.

I offer the following summary for anyone who might experience this issue and 
finds this report before the package is fixed:

Some versions of printer-driver-cups-pdf, including the 2.6.1-22 version now 
distributed in Stretch, produce PDF files that do not contain searchable text 
and cannot usefully be processed with pdftotext.  That problem has been fixed 
in a subsequent version.  The 3.0.1-5 version now available in Buster includes 
the fix.  However, in some cases, an upgrade to 3.0.1-5 will leave the old 
print queue in place, which effectively defeats the fix.  This condition can be 
detected by running
lpoptions -d PDF
and looking for the string "pdftops-renderer=pdftocairo".  If that string is 
absent, the old print queue remains.  In that case, removing 
printer-driver-cups-pdf 3.0.1-5 and reinstalling the same version should create 
the correct PDF queue.  This can be confirmed using lpoptions.

Best regards,

--Neil Ormos

Bug#928822: raqm: clean after build deletes docs/html/* which is not regenerated

[Andreas Beckmann]

Source: raqm
Version: 0.6.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

raqm/experimental fails to build twice in a row. The first build
succeeds, but the subsequent clean deletes
docs/html/* which is not regenerated during the
second build, fausing this to fail with:

   dh_install
dh_install: Cannot find (any matches for) "usr/share/gtk-doc/html/raqm" (tried 
in ., debian/tmp)

dh_install: libraqm-dev missing files: usr/share/gtk-doc/html/raqm
dh_install: missing files, aborting


I did not see an obvious command in the buildlog that is responsible
for the deletion.

I'm attaching the full buildlog as well as the diff between the
first andsecond build.

Andreas


raqm.build.diff.gz
Description: application/gzip


raqm_0.6.0-2_twice.log.gz
Description: application/gzip

Bug#928821: Section 3.1 'An overview of the boot strap process' should reference UEFI

[sixerjman]

Package: debian-reference
Source: debian-reference
Severity: wishlist
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
Reading Section 3.1 'Bootstrap Process'

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
N/A

   * What was the outcome of this action?
No information on the bootstrap process for modern UEFI enabled
machines

   * What outcome did you expect instead?
Short segment about the bootstrap process on UEFI machines

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


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

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

Bug#928818: pcmanfm-qt does not start as root on Debian live

[Alf Gaida]

Thanks adrian15, very helpful. After testing and discussing it a bit 
upstream the leading bug in that case is


https://github.com/lxqt/pcmanfm-qt/issues/958

Fixed in: https://github.com/lxqt/pcmanfm-qt/pull/960

Cheers Alf

Bug#583196: [regression]: nano cannot edit FIFOs anymore

[Benno Schulenberg]

[Sorry for getting so late to this.  However, it would have been
better to report this upstream.]

Hmmm...  Being able to edit a FIFO does sounds like a useful capability
to me.

Checking the versions I have available, I saw that 2.1.10 was still
able to edit a FIFO (read from it, and then write to it).  Checking
the commits since then, luckily it was the very first commit after
2.1.10 that broke this ability: the addition of is_file_writable().

Commit f8f90272:
   http://git.savannah.gnu.org/cgit/nano.git/commit/?id=f8f90272

Disabling that function (and another check that was added since then)
gives back the ability to edit a FIFO to nano-4.2.  So... I will be
looking into this, also because is_file_writable() causes another issue:
  https://savannah.gnu.org/bugs/?29312

Benno

Bug#926383: unblock: neutron-dynamic-routing-common/2:13.0.0-2

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Thu, Apr 04, 2019 at 11:40:42AM +0200, Michal Arbet wrote:
> I want to just ask you for exception for neutron-dynamic-routing package
> currently in sid.
> >> https://packages.debian.org/sid/neutron-dynamic-routing-common
> I'm working in debian-openstack-team on openstack packages.
> 
> I reworked neutron main package to new filesystem layout and also add
> maintainer script to enable/disable neutron plugins.
> 
> Main package neutron and his plugins are migrated in buster already,
> unfortunatelly this one plugin I forgot to update to fit new layout and
> enable plugin via maintainer script .
> 
> Also , I found a bug
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924476

Neither of these seem to fit the freeze criteria on the face of it. What
would be the impact of *not* migrating this package to buster?

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#928014: nmu: wine-development_4.2-4

[Paul Gevers]

Hi Jens,

On 09-05-2019 22:54, Jens Reyer wrote:

[...]

> The files built with unicode-data are in arch-specific packages, so a
> binnmu should work.

[...]

> So what do you think, binnmu or new source upload?

Than I have a preference for binNMU (this could be my first binNMU as well).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#915444: ITA: aspell-el

[Vangelis Mouhtsis]

Control: owner 915444 vange...@gnugr.org | !

Thanks

-- 
GPG Fingerprint: 868D EF24 37CC E9F5 C5DC  63B7 5E57 25A1 FB41 2219




signature.asc
Description: OpenPGP digital signature

Bug#928820: unblock: libxmlada/18-4

[Nicolas Boulenguez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package libxmlada

The update of unicode from 11 to 12 in testing has broken the build of
libxmlada/18-3, which generates Ada code from the unicode standard.

Most key Ada packages indirectly build-depend on libxmlada via
gprbuild. They automatically marked for removal from testing at the
end of the month.

A fix follows. It only adds a few manual exceptions to the translator,
as done for each Unicode version.

You may find more details at https://bugs.debian.org/927943.

unblock libxmlada/18-4

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libxmlada (18-4) unstable; urgency=medium
+
+  * Update to unicode version 12. Closes: #927943.
+
+ -- Nicolas Boulenguez   Thu, 02 May 2019 11:47:15 +0200
+
 libxmlada (18-3) unstable; urgency=medium
 
   * Update to unicode version 11, really closing #903380.
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@
 Build-Depends: debhelper (>= 11),
  gnat, gnat-8,
 # Note: the rules script parses this line to extract the gnat version.
- unicode-data (>= 11~), unicode-data (<< 12~),
+ unicode-data (>= 12~), unicode-data (<< 13~),
 # Used by debian/rules to generate unicode-names-*.ads.
 # When a new unicode standard is released, we most probably have to
 # increase the ALI version of xmlada-unicode and all reverse dependencies.
--- a/debian/patches/generate-unicode-9-names.diff
+++ b/debian/patches/generate-unicode-9-names.diff
@@ -14,7 +14,7 @@
  end Translators.Alias;
 --- a/unicode/importer/translators-block.adb
 +++ b/unicode/importer/translators-block.adb
-@@ -164,6 +164,10 @@
+@@ -164,6 +164,15 @@
 "Phags_Pa");
Add ("CJK Compatibility Forms",
 "Cjk_Compatibility_Forms");
@@ -22,6 +22,11 @@
 +  --  Unicode 9.
 +  Add ("Ideographic Symbols and Punctuation",
 +   "Ideograph_Symb_Punct");
++  --  Unicode 12.
++  Add ("Egyptian Hieroglyph Format Controls",
++   "Egypt_Hieroglyph_Fmt_Ctrl");
++  Add ("Symbols and Pictographs Extended-A",
++   "Symbols_Pictographs_Ext_A");
 end Set_Exceptions;
  
  end Translators.Block;

Bug#53434: Need Your Advise

[mohammed sultan]

Good day,

Please, am seriously looking for a profitable business where I can invest
in a very lucrative and profitable venture.

I will be waiting for your positive investment idea/advice.

Kindly forward me your direct telephone contact for our easy discussion and
further arrange on ways forward to utilize my investment funds

I look forward to hearing from you soon.
Looking for investment advice
Thanks.
Mr.Mohammed Sultan

Bug#904309: tilda: diff for NMU version 1.4.1-2.1

[Niels Thykier]

Sebastian Geiger:
> Hi Niels,
> 
> Thanks for the upload. It looks good to me. I think you can push that to the 
> repository. 
> 
> Best Regards
> Mit freundlichen Grüßen
> Dipl. Ing. Sebastian Geiger
> 
> [...]

Hi Sebastian,

Thanks for your feedback.

Just to confirm, when you wrote "push that to the repository", did you
mean push changes to the git repo on salsa (master branch) or remove the
delay of the upload to the archive (or both)?

Thanks,
~Niels

Bug#927304: unblock: aptly/1.3.0+ds1-2.2

[Jonathan Wiltshire]

Control: tag -1 confirmed moreinfo

On Mon, Apr 22, 2019 at 01:18:40AM +0800, Shengjing Zhu wrote:
> Control: retitle -1 testing-pu: aptly/1.3.0+ds1-2.1+deb10u1
> Control: tags -1 buster
> Control: usertag -1 = pu
> 
> Since the build-depends golang-github-mattn-go-isatty and
> golang-golang-x-sys are updated with new version in unstable, aptly
> needs to be built in testing now.
> 
> The debdiff is almost same, only the version should be changed
> to1.3.0+ds1-2.1+deb10u1

Please go ahead but use version 1.3.0+ds1-2.2~deb10u1 since this is
backport of something in unstable, not a divergence of testing.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#928764: alsa-utils does not store or restore configuration

[Elimar Riesebieter]

Control: tags -1 wontfix

* MERLIN Philippe  [2019-05-11 18:58 +0200]:

> Le samedi 11 mai 2019, 17:27:55 CEST Elimar Riesebieter a écrit :
> > Control: tags -1 unreproducible
> > Control: severity -1 normal
> > 
> > * MERLIN Philippe  [2019-05-11 16:59 +0200]:
> > 
> > [...]
> > 
> > > Yes , i have removed pulseaudio, i don't like it, i have had too many
> > > problems with pulseaudio.
> > > For the plugin libasound2-plugins it's important ?
> > 
> > Not that much. It depends on your soundcard
> > 
> > Well I can't reproduce your behaviour. I have a machine running only
> > libasound2, libasund2-data and alsa-utils. The sound card settings
> > are restored by the systemd services. And I have a clean environment
> > with no .asoundrc or /etc/alsa settings.
> > 
> > You can check your installation with:
> > 
> > $ dpkg -l | egrep '(alsa|libasound|pulsea)'
> > 
> > Hmm
> > Elimar 
> > dpkg -l | egrep '(alsa|libasound|pulsea
> Copy paste must introduce parasitic characters that prevent sending full 
> message

Hmm, I recommend to use an appropriate editor to compose your emails.

> dpkg -l | egrep '(alsa|libasound|pulsea)'
> 
> ii  alsa-base 1.0.27+1
> ii  alsa-firmware-loaders 1.1.7-1
> ii  alsa-oss  1.1.8-1
> ii  alsa-utils1.1.8-2
> ii  gstreamer0.10-alsa:amd64  0.10.36-2
> ii  gstreamer1.0-pulseaudio:amd64 1.14.4-dmo2
> ii  libasound2:amd64  1.1.8-1
> ii  libasound2:i386   1.1.8-1
> ii  libasound2-data   1.1.8-1
> ii  libasound2-dev:amd64  1.1.8-1
> ii  libasound2-plugins:amd64  1:1.1.8-dmo1
> ii  libasound2-plugins:i386   1:1.1.8-dmo1
> rc  libsdl1.2debian-alsa  1.2.14-6.2
> ii  libsnack2-alsa2.2.10-dfsg1-12.1
> ii  libsox-fmt-alsa:amd64 14.4.2+git20190427-1
> rc  pulseaudio11.1-2

I can't help any further. Despite the use of deb-multimedia packages
which we don't maintain. Anyway I assume that you have an alsa
config flying around in your system which resets your mixer status
at each login. Just create another user and try with that virgin
environment. I don't want to know details of your system, but I
think you have to cleanup your installation a bit ;-) So I tag this
bug as wontfix hereby.

Good luck
Elimar
-- 
  Experience is something you don't get until
  just after you need it!


signature.asc
Description: PGP signature

Bug#928489: unblock: spf-engine/2.9.0-4

[Niels Thykier]

Control: tags -1 moreinfo confirmed

Scott Kitterman:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package spf-engine
> 
> It's just been reported that postfix-policyd-spf-python is missing a
> depends on python3-pkg-resources, which caused me to discover it's also
> missing for pyspf-milter from the same source package.
> 
> This was not found up to this point because on most systems it is pulled
> in by another package.  The fix is minimal and has no regression risk
> (see attached debdiff).
> 
> Scott K
> 
> unblock spf-engine/2.9.0-4
> 

Hi,

Please upload the package to unstable and remove the moreinfo tag when
it is ready to be unblocked.

Thanks,
~Niels

Bug#680781: nano: copying a full line with the mouse misses the end-of-line

[Benno Schulenberg]

[Resending as debbugs doesn't CC the reporter.]

Indeed, if you haven't dragged far enough to the right, the LF will
not be copied.  But if you drag beyond the end of the line, you will
see that suddenly all empty space beyond the end-of-line will get
highlighted too -- this means that the LF was selected; then doing
'Paste' after 'Copy' will paste the LF too.  Please try it, and
report back.

Benno

Bug#928819: GParted installed with aptitude is not properly registered in Debian Buster with MATE

[foonge]

Package: gparted
Version: 0.32.0-2
Severity: 3
Tags: gparted mate debian apt-get aptitude

I have Debian Buster running in a virtual machine where I installed 
GParted using aptitude. During and after installation no error is shown.


GParted isn't registered in the command line (don't know the exact 
terminolgy) so when I as root type the command "gparted" it says "bash: 
/usr/bin/gparted: No such file or directory"


Also in Debian Jessie, GParted was available in MATE from the menu bar 
(System > Administration > GParted) which is not the case now in Debian 
Buster.


GParted is installed at /usr/sbin/gparted instead of /usr/bin/gparted.

It's my assumption that the APT packaging is not 100% correct. Other 
programs I installed with aptitude in the current Debian version did not 
have this issue.


My workaround is to create a symbolic link in the /usr/bin/ directory 
after which I can properly execute GParted from the command line as 
root. Thus:

ln -s /usr/sbin/gparted /usr/bin/gparted

Debian version: Linux debian 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 
(2019-03-15) x86_64 GNU/Linux

Aptitude version: 0.8.11-7
GParted version: 0.32.0-2
MATE desktop version: 1.20.4-2

Bug#820514: crafty: Please package latest upstream 25.0.1

[PICCORO McKAY Lenz]

why this can be done in so time?

if need i can provide dsc sources from my personal opensuse build service

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#928818: pcmanfm-qt does not start as root on Debian live

[adrian15]

Package: pcmanfm-qt
Severity: important

Dear Maintainer,

It does not start - without a meaningful message

* Expected Behavior

it should start as root

* Current Behavior

It does not start at all as root

* Possible Solution

Use:
lxsudo dbus-launch pcmanfm-qt
instead which requires dbus-x11 package to be installed.

* Steps to Reproduce (for bugs)

** Get a live ISO (siduction, manjaro, debian buster)
** Start and open a terminal
** lx(sudo) pcmanfm-qt
** lxsudo ends and no window appears

* Context

I want ot use pcmanfm-qt as root even on live isos - not possible

Additional information

* Original upstream bug https://github.com/lxqt/libfm-qt/issues/427 .
* Add a menu entry to the live cds to start pcmanfm-qt as root if it
does not exist yet.

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pcmanfm-qt depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.22-0+deb9u1
ii  dbus-x11 [dbus-session-bus]   1.10.22-0+deb9u1
ii  libc6 2.24-11+deb9u1
ii  libfm-modules 1.2.5-1
pn  libfm-qt3 
ii  libfm41.2.5-1
ii  libglib2.0-0  2.50.3-2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libstdc++66.3.0-18
ii  libxcb1   1.12-1

Versions of packages pcmanfm-qt recommends:
ii  breeze-icon-theme  4:5.28.0-1
ii  eject  2.1.5+deb1+cvs20081104-13.2
ii  gksu   2.0.2-9+b1
ii  gnome-icon-theme   3.12.0-2
ii  gvfs-backends  1.30.4-1
ii  oxygen-icon-theme  5:5.28.0-1
pn  pcmanfm-qt-l10n

Versions of packages pcmanfm-qt suggests:
pn  cdtool  

Bug#915444: ITA: aspell-el

[Vangelis Mouhtsis]

Control: retitle -1 915444 aspell-el

-- 
GPG Fingerprint: 868D EF24 37CC E9F5 C5DC  63B7 5E57 25A1 FB41 2219




signature.asc
Description: OpenPGP digital signature

Bug#928764: alsa-utils does not store or restore configuration

[MERLIN Philippe]

Le samedi 11 mai 2019, 17:27:55 CEST Elimar Riesebieter a écrit :
> Control: tags -1 unreproducible
> Control: severity -1 normal
> 
> * MERLIN Philippe  [2019-05-11 16:59 +0200]:
> 
> [...]
> 
> > Yes , i have removed pulseaudio, i don't like it, i have had too many
> > problems with pulseaudio.
> > For the plugin libasound2-plugins it's important ?
> 
> Not that much. It depends on your soundcard
> 
> Well I can't reproduce your behaviour. I have a machine running only
> libasound2, libasund2-data and alsa-utils. The sound card settings
> are restored by the systemd services. And I have a clean environment
> with no .asoundrc or /etc/alsa settings.
> 
> You can check your installation with:
> 
> $ dpkg -l | egrep '(alsa|libasound|pulsea)'
> 
> Hmm
> Elimar dpkg -l | egrep '(alsa|libasound|pulsea
Copy paste must introduce parasitic characters that prevent sending full 
message
dpkg -l | egrep '(alsa|libasound|pulsea)'

ii  alsa-base 1.0.27+1  
   
ii  alsa-firmware-loaders   1.1.7-1  amd64  

Amd64
ii  alsa-oss   1.1.8-1   amd64  
   
ii  alsa-utils  1.1.8-2   amd64 
 
ii  gstreamer0.10-alsa:amd640.10.36-2 amd64 
   
ii  gstreamer1.0-pulseaudio:amd64  1.14.4-dmo2 amd64
  
ii  libasound2:amd641.1.8-1 amd64   
   
ii  libasound2:i386 1.1.8-1 i386
  
ii  libasound2-data1.1.8-1 all
ii  libasound2-dev:amd641.1.8-1 amd64   
   
ii  libasound2-plugins:amd64  1:1.1.8-dmo1 amd64
ii  libasound2-plugins:i386   1:1.1.8-dmo1 i386
rc  libsdl1.2debian-alsa 1.2.14-6.2 amd64 
ii  libsnack2-alsa2.2.10-dfsg1-12.1   amd64
ii  libsox-fmt-alsa:amd64 14.4.2+git20190427-1   amd64
rc  pulseaudio  11.1-2  amd64  
Thanks.
Philippe Merlin

Bug#926778: unblock: python3.7 3.7.3 packages

[Paul Gevers]

Control: tags -1 moreinfo

Hi doko,

On Wed, 10 Apr 2019 10:23:15 +0200 Matthias Klose  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock python3.7, python3-stdlib-extensions and python3-defaults,
> bumping the version to the final 3.7.3 release, and fixing a bus error on 
> armhf,
> and avoiding unaligned memory accesses on arm64.

This looks mostly OK (albeit a new upstream release, which we try to
avoid unblocking), except you didn't document nor mentioned the g++-8
B-D change the locales change. Can you explain why that was done? These
kind of changes are not in line with the freeze policy unless they fix
serious issues. On top of that, (my python skills aren't that great), is
the change in platform-lsbrelease.diff really required, or just more robust?

Please make sure that during the release, you document *all* packaging
changes in the changelog and if needed, elaborate in the unblock request.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#928817: xdx: [INTL:fr] French templates translation

[Jean-Pierre Giraud]

Package: xdx
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation updated, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege



fr.po.gz
Description: application/gzip

Bug#928816: backup-manager: [INTL:fr] French templates translation

[Jean-Pierre Giraud]

Package: backup-manager
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation updated, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege



fr.po.gz
Description: application/gzip

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

[Norbert Preining]

Umpf,...

On Sat, 11 May 2019, Hilmar Preuße wrote:
> ! I can't find file `hyph-en-gb'.

indeed, cstex switched to load *loads* of patterns in 3/2019. What a
pain. See
http://git.texlive.info/texlive/commit/?id=e6ecf62a1727571cc47129fa4b4e198eadbe2ed3

That needs some serious rework ... I tend to depend on texlive-lang-all
..

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#909196: geany: webhelper seems ported to webkit2gtk, please reenable it

[Lee Garrett]

Hi,

it seems as though geany-plugin-webhelper was removed from buster/sid.
Looking at the changelog, there's the following entry:

geany-plugins (1.32+dfsg-3) unstable; urgency=medium

  * [67b34ed] Disable webkit-using plugins: markdown, webhelper
webkitgtk-3.0 is not to be used as it is deprecated, but the port to
webkit2gtk-4.0 isn't ready yet.

 -- Chow Loong Jin   Thu, 11 Jan 2018 03:17:55 +0800

Since the packages cleanly install and also upgrade fine, I'm lowering
the severity of this bug report. I don't expect this to be enabled again
at this point in the release cycle (buster is in deep freeze), but it
might be possible that this gets added to buster-backports.

HTH,
Lee

On Wed, 19 Sep 2018 11:40:55 -0400 PICCORO McKAY Lenz
 wrote:
> Package: geany-plugin-webhelper
> Version: geany-plugin-webhelper unable to install in testing
> Severity: grave
> 
> when upgrade geany-plugin-webhelper are missing and due that breaks my
> geany instalation
> 
> i make pressure due i'm unnable to use webhelper and geany becomes
> unnusable.. crash when push save button (due make refresh to the
> plugin that does not exist and config file said are enabled, but its a
> older version)
> 
> The geany and geany-plugins packages are 1.33-1 version,
> geany-plugin-webhelper still only in 1.29 and it is unable to install
> cause dependencies error:
> 
> geany-plugin-webhelper:
>  Depende: geany-abi-71
>   Depende: geany-plugins-common (=1.29+dfsg-1) pero se va a instalar
> 1.33+dfsg-1+b1
> 
> 
> Seems problema around webkit support was resolved with that commit:
> 
> https://github.com/geany/geany-plugins/pull/746/commits/4039a13882f4b9e2127f6e7b018bdbdffe36e2a2
> 
> and the bugt reported
> https://github.com/geany/geany-plugins/issues/412 ; i added notes
> about it!
> 
> 
> 
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
> 
> 

Bug#928815: u-boot: Olimex Teres-I support is missing USB

[Jonas Smedegaard]

Source: u-boot
Version: 2019.01+dfsg-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The recently added patch to enable support for Olimex Teres-I
has now been accepted into mainline u-boot.

The accepted patch has one addition compared to the patch
currently included with u-boot targeted Buster:
It properly enables the USB controller.

There is a know issue that the keyboard on the Teres-I laptop
still is not activated (suspected to be an issue with how the
firmware in that keyboard is initialized), but with the one-line
change to the teres-i patch an externally attached USB keyboard works.

Please consider merging the git branch wip/teres-i-buster
where I have prepared the update, and push that to Buster.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlzW85gACgkQLHwxRsGg
ASHaZBAAnVMim5LYP3vzQKXhOM1wisV6K2O8BJVCchm+rHGtTX2Hj3V28/V8x9vu
VIC4Cm5xRg27BAkFqM2BCzLEyDfLblFUGEgX1GUSujM69FoW4BT/59nGSm9cZk83
sj5LFAUGFJrwowcuorYBzyuNPAPYUgoQnDbJQQBJhcmbEvUmWTgDIAw/yLgcenN5
KDNDf5aSmuHHiiVoimt/iVOaMXaZoIx5M6LJSCQTniEk2zFrRy39TAAcko7JfxgO
nnOhLn0aC376YrF2PLnS6ilSagyFzzHliqzoew0GznnT/TcZx0E3w3Ucgo8G2+gr
4FzRatgFKC0YfHSAiFR18BzfaGoylmOW2coNN2hejVP88gE2DIGWhbroYdULCL7r
R8mXZs2Sie0KDFXeVZ/zzbThzcgNzUfMSaLKASUTUiVsQaWqg+J3JN+5lSQMK8qN
pgkNZzeDCc/VMlsu8Mc+jHdwFMPHasqxB6hliHjyxV/9wWKeFsXKmdn7PPY7wd5W
RYutdlII/RAfASFF5RE8ArUGPk79S+U9x01BVkYQNXIsag7Cs7eHUBWepJccotz9
A/e4kQmd+TwCMXeWOAZN2YmMcCbBD+shFYaEw9O6pSv87A3xCoTphN8nn8royZDt
8DtW9HWs7QUEBEFxqNDaqXSpepDjbBQMNh4h0D9OLe4YnU5v6w4=
=vG+D
-END PGP SIGNATURE-

Bug#928764: alsa-utils does not store or restore configuration

[Elimar Riesebieter]

* MERLIN Philippe  [2019-05-11 17:58 +0200]:

> Le samedi 11 mai 2019, 17:27:55 CEST Elimar Riesebieter a écrit :
> > Control: tags -1 unreproducible
> > Control: severity -1 normal
> > 
> > * MERLIN Philippe  [2019-05-11 16:59 +0200]:
> > 
> > [...]
> > 
> > > Yes , i have removed pulseaudio, i don't like it, i have had too many
> > > problems with pulseaudio.
> > > For the plugin libasound2-plugins it's important ?
> > 
> > Not that much. It depends on your soundcard
> > 
> > Well I can't reproduce your behaviour. I have a machine running only
> > libasound2, libasund2-data and alsa-utils. The sound card settings
> > are restored by the systemd services. And I have a clean environment
> > with no .asoundrc or /etc/alsa settings.
> > 
> > You can check your installation with:
> > 
> > $ dpkg -l | egrep '(alsa|libasound|pulsea)'
> > 
> > Hmm
> > Elimar
> it seems tht i have libasound2-plugins installed.
> dpkg -l | egrep '(alsa|libasound|pulsea)' 

I don't see it?

Here:

$ dpkg -l | egrep '(alsa|libasound|pulsea)' | awk '{ print $1, $2}'
ii alsa-utils
ii libasound2:amd64
ii libasound2-data

Elimar
-- 
  Do you smell something burning or is it me?


signature.asc
Description: PGP signature

Bug#928810: patch: Make debian-watch-uses-insecure-uri more generic

[Jelmer Vernooij]

On Sat, May 11, 2019 at 02:49:11PM +, Dmitry Bogatov wrote:
> From 2789fed85a6088c85f8f37ba96984eb7f3d8e8ef Mon Sep 17 00:00:00 2001
> From: Dmitry Bogatov 
> Date: Fri, 10 May 2019 23:32:01 +
> Subject: [PATCH] Make debian-watch-uses-insecure-uri more generic
> 
> Instead of using hard-coded list of hosts, that are known to support
> https new implementation just replace "http://; with "https://; and
> makes sure, that uscan report is same.
Does lintian-brush still build successfully under e.g. sbuild with this patch?
I suspect that this makes the test for debian-watch-uses-insecure-uri fail
because it now needs internet access.

This also seems to unconditionally run uscan, regardless of whether there are 
any
http: URLs in debian/watch, slowing down lintian-brush in situations when
there's nothing to fix. Could you perhaps grep for http: first?

> ---
>  fixers/debian-watch-uses-insecure-uri.sh | 17 ++---
>  1 file changed, 14 insertions(+), 3 deletions(-)
> 
> diff --git a/fixers/debian-watch-uses-insecure-uri.sh 
> b/fixers/debian-watch-uses-insecure-uri.sh
> index 85136b8..59c1e4f 100755
> --- a/fixers/debian-watch-uses-insecure-uri.sh
> +++ b/fixers/debian-watch-uses-insecure-uri.sh
> @@ -1,6 +1,17 @@
>  #!/bin/sh
> -perl -p -i -e 
> 's/http:\/\/code.launchpad.net\//https:\/\/code.launchpad.net\//' debian/watch
> -perl -p -i -e 's/http:\/\/launchpad.net\//https:\/\/launchpad.net\//' 
> debian/watch
> -perl -p -i -e 's/http:\/\/ftp.gnu.org\//https:\/\/ftp.gnu.org\//' 
> debian/watch
> +before=$(mktemp)
> +after=$(mktemp)
> +uscan --dehs > "${before}" 2>&1
> +sed -i.bak s,http://,https://,g debian/watch
> +uscan --dehs > "${after}" 2>&1
> +
> +# Make sure that reports are same up to http/https substitution in URL.
> +sed -i s,http://,https://,g "${before}" "${after}"
> +if cmp -s "${before}" "${after}" ; then
> + rm -f debian/watch.bak
> +else
> + mv debian/watch.bak debian/watch
> +fi
> +rm -f "${before}" "${after}"
>  echo "Use secure URI in debian/watch."
>  echo "Fixed-Lintian-Tags: debian-watch-uses-insecure-uri"

Bug#928764: alsa-utils does not store or restore configuration

[MERLIN Philippe]

Le samedi 11 mai 2019, 17:27:55 CEST Elimar Riesebieter a écrit :
> Control: tags -1 unreproducible
> Control: severity -1 normal
> 
> * MERLIN Philippe  [2019-05-11 16:59 +0200]:
> 
> [...]
> 
> > Yes , i have removed pulseaudio, i don't like it, i have had too many
> > problems with pulseaudio.
> > For the plugin libasound2-plugins it's important ?
> 
> Not that much. It depends on your soundcard
> 
> Well I can't reproduce your behaviour. I have a machine running only
> libasound2, libasund2-data and alsa-utils. The sound card settings
> are restored by the systemd services. And I have a clean environment
> with no .asoundrc or /etc/alsa settings.
> 
> You can check your installation with:
> 
> $ dpkg -l | egrep '(alsa|libasound|pulsea)'
> 
> Hmm
> Elimar
it seems tht i have libasound2-plugins installed.
dpkg -l | egrep '(alsa|libasound|pulsea)' 

Bug#928811: patch: New fixer: patch-file-present-but-not-mentioned-in-series.sh

[Jelmer Vernooij]

Thanks! Makes sense.

Any chance you could add a test case for this under 
tests/patch-file-present-but-not-mentioned-in-series/ ?

On Sat, May 11, 2019 at 02:49:14PM +, Dmitry Bogatov wrote:
> 
> Package: lintian-brush
> Severity: wishlist
> Tags: patch
> 
> From dac3dbdaf7505502a860bb365ccd88da1717dc87 Mon Sep 17 00:00:00 2001
> From: Dmitry Bogatov 
> Date: Sat, 11 May 2019 14:46:44 +
> Subject: [PATCH] New fixer: patch-file-present-but-not-mentioned-in-series.sh
> 
> Make sure that debian/patches contain only patches, mentioned in series
> file.
> ---
>  fixers/index.desc  |  3 +++
>  .../patch-file-present-but-not-mentioned-in-series.sh  | 10 ++
>  2 files changed, 13 insertions(+)
>  create mode 100755 fixers/patch-file-present-but-not-mentioned-in-series.sh
> 
> diff --git a/fixers/index.desc b/fixers/index.desc
> index 735179f..058889c 100644
> --- a/fixers/index.desc
> +++ b/fixers/index.desc
> @@ -120,6 +120,9 @@ Lintian-Tags:
>package-uses-deprecated-debhelper-compat-version,
>package-uses-old-debhelper-compat-version
>  
> +Fix-Script: patch-file-present-but-not-mentioned-in-series.sh
> +Lintian-Tags: patch-file-present-but-not-mentioned-in-series
> +
>  Fix-Script: possible-missing-colon-in-closes.sh
>  Lintian-Tags: possible-missing-colon-in-closes
>  
> diff --git a/fixers/patch-file-present-but-not-mentioned-in-series.sh 
> b/fixers/patch-file-present-but-not-mentioned-in-series.sh
> new file mode 100755
> index 000..66ff555
> --- /dev/null
> +++ b/fixers/patch-file-present-but-not-mentioned-in-series.sh
> @@ -0,0 +1,10 @@
> +#!/bin/sh -eu
> +test -r debian/patches/series || exit 0
> +cd debian/patches
> +
> +for f in * ; do
> + test "${f}" != series || continue
> + grep -q -- "${f}" series || rm "${f}"
> +done
> +echo "Remove patches missing from debian/patches/series."
> +echo "Fixed-Lintian-Tags: patch-file-present-but-not-mentioned-in-series"

Bug#928814: package-update-indicator: Install updates greyed out, never shows update notification

[fmiz]

Package: package-update-indicator
Version: 2.0-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I stopped receiving update notifications, after about a month I checked with
apt and pkcon get-updates,
the system had 145 updates. I am running XFCE 4.12 on testing, the green update
icon is always present,
but it looks like it is not doing anything.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I updated everything (and noticed the update icon never went away), then ran
package-update-indicator --quit and restarted it,
then downgraded a package, ran pkcon refresh, apt and packagekit show the
update,
the update icon is in the taskbar but it still had the "Install updates" option
greyed out.

Also, I started searching and found another bug report for this package and
noticed that a "--debug" option exists,
it is not in the manpage.
This is what it shows:

(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.531:
property "update-command" set to ""
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.615:
indicator icon: system-software-update, notification title: "", notification
body: ""
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.620:
backend: aptcc
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.620:
roles: cancel;depends-on;get-details;get-files;get-packages;get-repo-
list;required-by;get-update-detail;get-updates;install-files;install-
packages;install-signature;refresh-cache;remove-packages;repo-
enable;resolve;search-details;search-file;search-group;search-name;update-
packages;what-provides;download-packages;get-old-transactions;repair-
system;get-details-local;get-files-local;repo-remove
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.621:
network-state: online
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.622:
property "refresh-interval" set to 0
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.622:
property "use-mobile-connection" set to false
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.622:
state initial -> up-to-date
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.622:
indicator icon: system-software-update, notification title: "Up to Date",
notification body: "The system is up to date."
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.633:
setting HTTP proxy to "(null)"
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.633:
setting HTTPS proxy to "(null)"
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.633:
setting FTP proxy to "(null)"
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.633:
setting SOCKS proxy to "(null)"
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.633:
setting the list of download IPs which should not go through a proxy to
"(null)"
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:24:01.633:
setting the PAC string to "(null)"

(package-update-indicator:2281): Gdk-CRITICAL **: 17:24:01.821:
gdk_window_thaw_toplevel_updates: assertion
'window->update_and_descendants_freeze_count > 0' failed
(package-update-indicator-prefs:2286): package-update-indicator-DEBUG:
17:24:06.768: mapping refresh-interval 0 to index 0
(package-update-indicator-prefs:2339): package-update-indicator-DEBUG:
17:25:21.445: mapping refresh-interval 0 to index 0
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:27:26.929:
number of updates changed
(package-update-indicator:2281): package-update-indicator-DEBUG: 17:27:45.929:
number of updates changed

I do not know how to troubleshoot this... hence the bug report.
Thanks,
fmiz



-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-4-686-pae (SMP w/2 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages package-update-indicator depends on:
ii  dconf-gsettings-backend [gsettings-backend  0.30.1-2
ii  libappindicator3-1  0.4.92-7
ii  libatk1.0-0 2.30.0-2
ii  libc6   2.28-10
ii  libcairo-gobject2   1.16.0-4
ii  libcairo2   1.16.0-4
ii  libdbusmenu-glib4   18.10.20180917~bzr490+repack1-1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-1
ii  libgtk-3-0  3.24.5-1
ii  libpackagekit-glib2-18  1.1.12-5
ii  libpango-1.0-0

Bug#928764: alsa-utils does not store or restore configuration

[Elimar Riesebieter]

Control: tags -1 unreproducible
Control: severity -1 normal

* MERLIN Philippe  [2019-05-11 16:59 +0200]:

[...]
> Yes , i have removed pulseaudio, i don't like it, i have had too many 
> problems 
> with pulseaudio.
> For the plugin libasound2-plugins it's important ?

Not that much. It depends on your soundcard

Well I can't reproduce your behaviour. I have a machine running only
libasound2, libasund2-data and alsa-utils. The sound card settings
are restored by the systemd services. And I have a clean environment
with no .asoundrc or /etc/alsa settings.

You can check your installation with:

$ dpkg -l | egrep '(alsa|libasound|pulsea)'

Hmm
Elimar
-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds


signature.asc
Description: PGP signature

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

[Hilmar Preuße]

On 11.05.19 15:55, Andreas Beckmann wrote:

> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
> 
Error message from fmtutil:

(/usr/share/texlive/texmf-dist/tex/csplain/base/hyphen.ex
Enhyphex.tex English exception words.)
Loading UK English hyphenation patterns in ASCII encoding, \engbPatt=101
(engb)
.
! I can't find file `hyph-en-gb'.
 \input hyph-en-gb

\loadpatterns ...encoding, \string #1=#2 (#3).} #5
   \endgroup
\expandafter \g...
l.199 ...  {\input hyph-en-gb }23 \relax \engbPatt


Not sure why it needs English hyphenation pattern, when building format
files for csplain. Anyhow: the file provided by texlive-lang-english.

Hilmar
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#926630: unblock: libpng1.6/1.6.36-6

[Paul Gevers]

Control: tags -1 confirmed d-i

Hi Gianfranco,

On Mon, 8 Apr 2019 11:22:05 +0200 Gianfranco Costamagna
 wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: unblock
> Severity: normal
> 
> Please unblock package libpng1.6
> 
> Finally, the arm issue we are facing since a lot of time (upstream had a 
> look, to understand if the failing test
> was a real bug or a testsuite one, and now it seems to be a real missing free 
> in the code).
> 
> Previously, to let the package migrate, I uncommented part of the upstream 
> fix, because it was making the test pass on arm*.
> 
> Now, with this updated and fixed approach, I have been able to:
> 1) uncomment the 70d122aac42933ab8a708c538f973c3307853212 (this fix was 
> needed but was making things worse, now with the followup
> commits it works again)
> 2) add  82ae623ec9bc3cb5c68aad22596a766e86d593b7 and 
> a627bd26a375f5c41d54f90a47c838157d1bec97, the two proper fixes for this issue
> 3) comment 272 proposed patch, this is now superseded by the above.
> 
> I also tweaked the patch description for the CVE fix, so we have a link to 
> the upstream commit that merged it.
> I also took the possibility to update the maintainers list to fix bug 925014
> 
> debdiff attached
> 
> thanks for caring,
> 
> unblock libpng1.6/1.6.36-6

I am fine with this, but it needs a review by d-i (CC-ed kibi).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#928294: unblock: suricata/4.1.4-1

[Paul Gevers]

Control: tags -1 moreinfo

Hi Pierre,

On Wed, 1 May 2019 14:24:06 +0200 Pierre Chifflier 
wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Although it is an upstream release, please unblock suricata 4.1.4-1 for
> buster.
> Suricata is an Intrusion Detection System (IDS), which makes it
> exposed to malicious traffic by design. The upstream release 4.1.4 fixes
> several bugs and security issues (no CVE numbers).
> 
> The debdiff since 4.1.3 is too big to be included here (it contains
> updates to many auto-generated files like configure), so I'm adding the
> upstream changelog here:
> 
> Changes
> 
> Bug #2870: pcap logging with lz4 coverity warning
> Bug #2883: ssh: heap buffer overflow
> Bug #2884: mpls: heapbuffer overflow in file decode-mpls.c
> Bug #2887: decode-ethernet: heapbuffer overflow in file decode-ethernet.c
> Bug #2888: 4.1.3 core in HCBDCreateSpace
> Bug #2894: smb 1 create andx request does not parse the filename correctly
> Bug #2902: rust/dhcp: panic in dhcp parser
> Bug #2903: mpls: cast of misaligned data leads to undefined behavior
> Bug #2904: rust/ftp: panic in ftp parser
> Bug #2943: rust/nfs: integer underflow
> This release includes Suricata-Update 1.0.5

You even forgot to include half the changes since buster, as you missed
the changes in 4.1.3 (buster has 4.1.2).

> I hope the new version can be included.

Can you please investigate how severe these issues are that are being
fixed. The current delta with buster is big and not in line with the
freeze policy as I can't say that this is a targeted fix. Are all these
issues important or serious?

Can you also please give us a risk assessment for the unblock? If buster
were already released, would you have requested the same update?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#926540: unblock: xorg-server/2:1.20.4-1

[Andreas Boll]

Hi kibi,

On Sat, Apr 06, 2019 at 10:25:31PM +0200, Cyril Brulebois wrote:
> Hi,
> 
> Andreas Boll  (2019-04-06):
> > CCing kibi for unblock-udeb review
> 
> This is coming a little late for RC1 that should be published very soon.
> I've added this to my local todo list but feel free to prod me once RC1
> is published.
> 

Ping :)

Thanks,
Andreas

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

[max . power]

Subject: libapache2-mod-jk: Jk can not find any configured worker
Package: libapache2-mod-jk
Version: 1:1.2.46-1
Severity: important

Dear Maintainer,

any configured worker does not get found, following error messages appearing:

Could not find worker with name ajp13_worker

I found out that the config file for Jk module is not named correctly in 
/etc/apache2/mods-available. Name is httpd-jk.conf where it should have been 
jk.conf. Consequence is, that it does not get linked to mods-enabled directory 
on enabling Jk module. Also the link /etc/libapache2-mod-jk/httpd-jk.conf 
should point to the renamed file /etc/apache2/mods-availabl
e/jk.conf.



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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libapache2-mod-jk depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.38-3
ii  libc6   2.28-10

libapache2-mod-jk recommends no packages.

Versions of packages libapache2-mod-jk suggests:
pn  libapache-mod-jk-doc  
ii  tomcat9   9.0.16-3

-- Configuration Files:
/etc/apache2/mods-available/httpd-jk.conf [Errno 2] Datei oder Verzeichnis 
nicht gefunden: '/etc/apache2/mods-available/httpd-jk.conf'

-- no debconf information

Bug#928764: alsa-utils does not store or restore configuration

[MERLIN Philippe]

Le samedi 11 mai 2019, 16:32:13 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe  [2019-05-11 16:19 +0200]:
> 
> [...]
> 
> > > > > > The result:
> > > > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs
> > > > > > systemctl
> > > > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > > > *●* alsa-state.service - Manage Sound Card State (restore and
> > > > > > store)
> > > > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > > 
> > > > > Please post the output of:
> > > > > 
> > > > > $ ls -al /etc/alsa
> > > > > $ ls -al /etc/alsa/conf.d
> > > > > $ ls -al /var/lib/alsa
> > > > > $ ls -al ~/.asoundrc
> > > > > 
> > > > > Elimar
> > > > 
> > > > s -al /etc/alsa
> > > > export LANG=C| ls -al ~/.asoundrc
> > > 
> > > ?
> > > 
> > > Elimar
> > 
> > Sorry:
> > 
> > export LANG=C| ls -al ~/.asoundrc
> 
> Try as follows ;-)
> 
> $ LC_ALL=C ls -al ~/.asoundrc
> ls: cannot access '/home/users/riesebie/.asoundrc': No such file or
> directory
> 
> Well, it seems that you don't have pulseaudio nor libasound2-plugins
> installed. Otherwise you should have an output of:
> 
> $ ls -al /etc/alsa/conf.d
> drwxr-xr-x 2 root root 335 Feb 16 08:16 ./
> drwxr-xr-x 3 root root  20 Apr 10 14:17 ../
> lrwxrwxrwx 1 root root  44 Jan 26 16:17 10-rate-lav.conf ->
> /usr/share/alsa/alsa.conf.d/10-rate-lav.conf lrwxrwxrwx 1 root root  46 Jan
> 26 16:17 10-samplerate.conf ->
> /usr/share/alsa/alsa.conf.d/10-samplerate.conf lrwxrwxrwx 1 root root  45
> Jan 26 16:17 10-speexrate.conf ->
> /usr/share/alsa/alsa.conf.d/10-speexrate.conf lrwxrwxrwx 1 root root  48
> Jan 26 16:17 50-arcam-av-ctl.conf ->
> /usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf lrwxrwxrwx 1 root root  40
> Jan 26 16:17 50-jack.conf -> /usr/share/alsa/alsa.conf.d/50-jack.conf
> lrwxrwxrwx 1 root root  39 Jan 26 16:17 50-oss.conf ->
> /usr/share/alsa/alsa.conf.d/50-oss.conf lrwxrwxrwx 1 root root  46 Jan 26
> 16:17 50-pulseaudio.conf -> /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
> lrwxrwxrwx 1 root root  47 Jan 26 16:17 60-a52-encoder.conf ->
> /usr/share/alsa/alsa.conf.d/60-a52-encoder.conf lrwxrwxrwx 1 root root  41
> Jan 26 16:17 60-upmix.conf -> /usr/share/alsa/alsa.conf.d/60-upmix.conf
> lrwxrwxrwx 1 root root  44 Jan 26 16:17 60-vdownmix.conf ->
> /usr/share/alsa/alsa.conf.d/60-vdownmix.conf lrwxrwxrwx 1 root root  46 Jan
> 26 16:17 98-usb-stream.conf ->
> /usr/share/alsa/alsa.conf.d/98-usb-stream.conf lrwxrwxrwx 1 root root  38
> Feb 15 00:05 99-pulse.conf -> /usr/share/alsa/alsa.conf.d/pulse.conf
> -rw-r--r-- 1 root root 201 Nov 10 16:29 99-pulseaudio-default.conf.example
> 
> Elimar
Yes , i have removed pulseaudio, i don't like it, i have had too many problems 
with pulseaudio.
For the plugin libasound2-plugins it's important ?
Philippe Merlin

Bug#928812: unblock: xserver-xorg-video-ati/1:19.0.1-1

[Andreas Boll]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package xserver-xorg-video-ati

It forwards the git snapshot upload 1:18.1.99+git20190207-1 to the final
release including additional fixes and another small stable release
with further fixes.

>From the Debian changelog:
xserver-xorg-video-ati (1:19.0.1-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * New bugfix release.
- Use radeon_finish in drmmode_crtc_scanout_update. Fixes a crash if
  using exa acceleration (Closes: #924540).
- Revert "glamor: Avoid glamor_create_pixmap for pixmaps backing
  windows". Fixes visual corruption issues (LP: #1822075).

 -- Andreas Boll   Sat, 06 Apr 2019 21:38:04 +0200

xserver-xorg-video-ati (1:19.0.0-1) unstable; urgency=medium

  * New upstream release.

 -- Timo Aaltonen   Tue, 12 Mar 2019 18:40:57 +0200

xserver-xorg-video-ati (1:18.1.99+git20190207-1) unstable; urgency=medium

I've attached a git-diff with the following command:
  git diff 
xserver-xorg-video-ati-1_18.1.99+git20190207-1..xserver-xorg-video-ati-1_19.0.1-1

Further I've attached the output of git-shortlog to list all commit
titles.

unblock xserver-xorg-video-ati/1:19.0.1-1

Thanks,
Andreas
diff --git a/configure.ac b/configure.ac
index 84f25cfd..49e82fc8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -23,7 +23,7 @@
 # Initialize Autoconf
 AC_PREREQ([2.60])
 AC_INIT([xf86-video-ati],
-[18.1.99],
+[19.0.1],
 [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Driver/Radeon],
 [xf86-video-ati])
 
diff --git a/debian/changelog b/debian/changelog
index 6d2f0e6f..0c3bda3a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+xserver-xorg-video-ati (1:19.0.1-1) unstable; urgency=medium
+
+  [ Timo Aaltonen ]
+  * New bugfix release.
+- Use radeon_finish in drmmode_crtc_scanout_update. Fixes a crash if
+  using exa acceleration (Closes: #924540).
+- Revert "glamor: Avoid glamor_create_pixmap for pixmaps backing
+  windows". Fixes visual corruption issues (LP: #1822075).
+
+ -- Andreas Boll   Sat, 06 Apr 2019 21:38:04 +0200
+
+xserver-xorg-video-ati (1:19.0.0-1) unstable; urgency=medium
+
+  * New upstream release.
+
+ -- Timo Aaltonen   Tue, 12 Mar 2019 18:40:57 +0200
+
 xserver-xorg-video-ati (1:18.1.99+git20190207-1) unstable; urgency=medium
 
   * New upstream snapshot.
diff --git a/src/drmmode_display.c b/src/drmmode_display.c
index 71f3539f..0e9e2474 100644
--- a/src/drmmode_display.c
+++ b/src/drmmode_display.c
@@ -785,7 +785,7 @@ drmmode_crtc_scanout_update(xf86CrtcPtr crtc, DisplayModePtr mode,
 	 screen->GetWindowPixmap(screen->root),
 	 extents)) {
 			RegionEmpty(DamageRegion(drmmode_crtc->scanout_damage));
-			radeon_glamor_finish(scrn);
+			radeon_finish(scrn, drmmode_crtc->scanout[scanout_id].bo);
 
 			if (!drmmode_crtc->flip_pending) {
 radeon_drm_abort_entry(drmmode_crtc->
@@ -1576,6 +1576,51 @@ drmmode_output_mode_valid(xf86OutputPtr output, DisplayModePtr pModes)
 	return MODE_OK;
 }
 
+static void
+drmmode_output_attach_tile(xf86OutputPtr output)
+{
+#if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1, 17, 99, 901, 0)
+	drmmode_output_private_ptr drmmode_output = output->driver_private;
+	drmModeConnectorPtr koutput = drmmode_output->mode_output;
+	RADEONEntPtr pRADEONEnt = RADEONEntPriv(output->scrn);
+	struct xf86CrtcTileInfo tile_info, *set = NULL;
+	int i;
+
+	if (!koutput) {
+		xf86OutputSetTile(output, NULL);
+		return;
+	}
+
+	/* look for a TILE property */
+	for (i = 0; i < koutput->count_props; i++) {
+		drmModePropertyPtr props;
+		props = drmModeGetProperty(pRADEONEnt->fd, koutput->props[i]);
+		if (!props)
+			continue;
+
+		if (!(props->flags & DRM_MODE_PROP_BLOB)) {
+			drmModeFreeProperty(props);
+			continue;
+		}
+
+		if (!strcmp(props->name, "TILE")) {
+			drmModeFreePropertyBlob(drmmode_output->tile_blob);
+			drmmode_output->tile_blob =
+drmModeGetPropertyBlob(pRADEONEnt->fd,
+		   koutput->prop_values[i]);
+		}
+		drmModeFreeProperty(props);
+	}
+	if (drmmode_output->tile_blob) {
+		if (xf86OutputParseKMSTile(drmmode_output->tile_blob->data,
+	   drmmode_output->tile_blob->length,
+	   _info) == TRUE)
+			set = _info;
+	}
+	xf86OutputSetTile(output, set);
+#endif
+}
+
 static int
 koutput_get_prop_idx(int fd, drmModeConnectorPtr koutput,
 int type, const char *name)
@@ -1648,6 +1693,8 @@ drmmode_output_get_modes(xf86OutputPtr output)
 	}
 	xf86OutputSetEDID(output, mon);
 
+	drmmode_output_attach_tile(output);
+
 	/* modes should already be available */
 	for (i = 0; i < koutput->count_modes; i++) {
 		Mode = xnfalloc(sizeof(DisplayModeRec));
@@ -1665,8 +1712,11 @@ drmmode_output_destroy(xf86OutputPtr output)
 	drmmode_output_private_ptr drmmode_output = output->driver_private;
 	int i;
 
-	if (drmmode_output->edid_blob)
-		drmModeFreePropertyBlob(drmmode_output->edid_blob);
+	

Bug#928810: patch: Make debian-watch-uses-insecure-uri more generic

[Dmitry Bogatov]

Package: lintian-brush
Severity: wishlist
Tags: patch

From 2789fed85a6088c85f8f37ba96984eb7f3d8e8ef Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Fri, 10 May 2019 23:32:01 +
Subject: [PATCH] Make debian-watch-uses-insecure-uri more generic

Instead of using hard-coded list of hosts, that are known to support
https new implementation just replace "http://; with "https://; and
makes sure, that uscan report is same.
---
 fixers/debian-watch-uses-insecure-uri.sh | 17 ++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/fixers/debian-watch-uses-insecure-uri.sh 
b/fixers/debian-watch-uses-insecure-uri.sh
index 85136b8..59c1e4f 100755
--- a/fixers/debian-watch-uses-insecure-uri.sh
+++ b/fixers/debian-watch-uses-insecure-uri.sh
@@ -1,6 +1,17 @@
 #!/bin/sh
-perl -p -i -e 
's/http:\/\/code.launchpad.net\//https:\/\/code.launchpad.net\//' debian/watch
-perl -p -i -e 's/http:\/\/launchpad.net\//https:\/\/launchpad.net\//' 
debian/watch
-perl -p -i -e 's/http:\/\/ftp.gnu.org\//https:\/\/ftp.gnu.org\//' debian/watch
+before=$(mktemp)
+after=$(mktemp)
+uscan --dehs > "${before}" 2>&1
+sed -i.bak s,http://,https://,g debian/watch
+uscan --dehs > "${after}" 2>&1
+
+# Make sure that reports are same up to http/https substitution in URL.
+sed -i s,http://,https://,g "${before}" "${after}"
+if cmp -s "${before}" "${after}" ; then
+   rm -f debian/watch.bak
+else
+   mv debian/watch.bak debian/watch
+fi
+rm -f "${before}" "${after}"
 echo "Use secure URI in debian/watch."
 echo "Fixed-Lintian-Tags: debian-watch-uses-insecure-uri"


pgpahziaUrAG9.pgp
Description: PGP signature

Bug#928809: lintian: suggest adding gitlab-ci file

[Dmitry Bogatov]

Package: lintian
Version: 2.13.0
Severity: wishlist

Dear Maintainer,

please add suggestion that if Vcs-Git points to salsa.debian.org,
CI should be used.

While CI config can be located anywhere (ci_config_path property of
project), both Debian Wiki and salsa(1) manpage mention
"debian/.gitlab-ci.yml" path.

So, in pseudo-code I propose following:

  if ($vcs =~ salsa.debian.org && ! -r "debian/.gitlab-ci.yml") {
tag-pedantic "consider useing Gitlab CI"
  }


pgpDDpOYqSppt.pgp
Description: PGP signature

Bug#928811: patch: New fixer: patch-file-present-but-not-mentioned-in-series.sh

[Dmitry Bogatov]

Package: lintian-brush
Severity: wishlist
Tags: patch

From dac3dbdaf7505502a860bb365ccd88da1717dc87 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Sat, 11 May 2019 14:46:44 +
Subject: [PATCH] New fixer: patch-file-present-but-not-mentioned-in-series.sh

Make sure that debian/patches contain only patches, mentioned in series
file.
---
 fixers/index.desc  |  3 +++
 .../patch-file-present-but-not-mentioned-in-series.sh  | 10 ++
 2 files changed, 13 insertions(+)
 create mode 100755 fixers/patch-file-present-but-not-mentioned-in-series.sh

diff --git a/fixers/index.desc b/fixers/index.desc
index 735179f..058889c 100644
--- a/fixers/index.desc
+++ b/fixers/index.desc
@@ -120,6 +120,9 @@ Lintian-Tags:
   package-uses-deprecated-debhelper-compat-version,
   package-uses-old-debhelper-compat-version
 
+Fix-Script: patch-file-present-but-not-mentioned-in-series.sh
+Lintian-Tags: patch-file-present-but-not-mentioned-in-series
+
 Fix-Script: possible-missing-colon-in-closes.sh
 Lintian-Tags: possible-missing-colon-in-closes
 
diff --git a/fixers/patch-file-present-but-not-mentioned-in-series.sh 
b/fixers/patch-file-present-but-not-mentioned-in-series.sh
new file mode 100755
index 000..66ff555
--- /dev/null
+++ b/fixers/patch-file-present-but-not-mentioned-in-series.sh
@@ -0,0 +1,10 @@
+#!/bin/sh -eu
+test -r debian/patches/series || exit 0
+cd debian/patches
+
+for f in * ; do
+   test "${f}" != series || continue
+   grep -q -- "${f}" series || rm "${f}"
+done
+echo "Remove patches missing from debian/patches/series."
+echo "Fixed-Lintian-Tags: patch-file-present-but-not-mentioned-in-series"


pgpfSBQ_qypeg.pgp
Description: PGP signature

Bug#928808: tracker.debian.org: automatic filing bugs

[Dmitry Bogatov]

Package: tracker.debian.org
Severity: wishlist

Dear Maintainer,

would it be possible to automatically file bugs with issues, already
detected by tracker?

Personally, I would be especially interested in auto-reporting bugs
about new upstream releases and lintian warnings/errors.

Sure, this feature must be opt-in, but it would be great improvement to
my workflow.

Question is access-control. Probably, only maintainer/uploader of
package can make decision, whether bugs should be auto-reported.
I see it as something like this:

C: mailto:cont...@tracker.debian.org?subject=autoreport=packagename
S: 
C: 
S: 

Ideally, email, signed with DD/DM key would not require confirmation.


pgpINifVQhT2p.pgp
Description: PGP signature

Bug#927711: CVE-2019-10044

[Коля Гурьев]

Hi,

09.05.2019 23:42, Moritz Mühlenhoff пишет:
> What's the status? Has upstream been contacted for an isolated fix, are
> you planning to address this for buster?


As John Preston said, there was no a special fix of the issue in 1.5.12.
It is mistake that this version is considered to contain the fix.
And as far as I can see, Telegram Desktop has no a fix of this CVE yet.

At least some code[1] in HistoryWebPage checks for hidden URLs. But it
does not always work properly. For example, it shows a confirmation
for https://www.аррӏе.com/ (https://www.xn--80ak6aa92e.com/) but not
for http://blаzeinfosec.com (http://xn--blzeinfosec-zij.com).

 [1]: 
https://sources.debian.org/src/telegram-desktop/1.5.11-1/Telegram/SourceFiles/history/media/history_media_web_page.cpp/#L133

Bug#928418: unblock: preapproval: corekeeper/1.7

[Paul Gevers]

Control: tags -1 confirmed moreinfo

On Sat, 04 May 2019 15:06:10 +0800 Paul Wise  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> I would like to fix some issues in corekeeper reported by Jakub Wilk.
> 
> unblock corekeeper/1.7

Please go ahead and upload to unstable and remove the moreinfo tag when
it's build.

For reference, if you're confident that an upload meets the freeze
policy, i.e. it only fixes release critical bugs (or important bugs for
optional packages), feel free to upload without a pre-approval. Most of
the time it's easier to review when the package is available and it
saves a round-trip. That said, if unsure feel free to ask for pre-approval.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#928807: unblock: mesa/18.3.6-2

[Andreas Boll]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mesa

This unblock request contains a stable upstream release with lots of
bug fixes for mesa's graphics drivers including fixes for driver
crashes and visual corruption. It fixes two RC bugs (#922346,
#926857).

Debian changelog diff:
mesa (18.3.6-2) unstable; urgency=medium

  * Cherry-pick c77acc3ceba (meson: remove meson-created megadrivers
symlinks) from upstream master branch. Removes a broken symlink
(Closes: #926857).

 -- Andreas Boll   Sat, 11 May 2019 15:43:07 +0200

mesa (18.3.6-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * libgl1-mesa-dri: Remove /etc/drirc which isn't installed anymore.
(Closes: #920241)

  [ Andreas Boll ]
  * New upstream release.
- wayland/egl: Ensure EGL surface is resized on DRI
  update_buffers(). Fixes a crash with xwayland (Closes: #922346).
  * Rebase patches/fix-hurd-ftbfs.diff.

 -- Andreas Boll   Sat, 06 Apr 2019 20:58:43 +0200


I've attached a git-diff with the following command:
  git diff mesa-18.3.4-2..mesa-18.3.6-2

Further I've attached the output of git-shortlog to list all commit
titles.

unblock mesa/18.3.6-2

Thanks,
Andreas
diff --git a/VERSION b/VERSION
index 0548779ef21..d63efa719a7 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-18.3.4
+18.3.6
diff --git a/bin/.cherry-ignore b/bin/.cherry-ignore
index d69c2cacb4f..1041997a21e 100644
--- a/bin/.cherry-ignore
+++ b/bin/.cherry-ignore
@@ -36,3 +36,19 @@ cbd1ad6165f0aea7fb7c6fd1b36ad5317dd65cb7 st/mesa: require RGBA2, RGB4, and RGBA4
 
 # stable The commit addresses functionality not present in branch
 1b8983c25be19073c02fe9630e949be55f8280fa radv: fix using LOAD_CONTEXT_REG with old GFX ME firmwares on GFX8
+
+# stable Explicit 19.0 only nominations, require work which did not land in branch
+8ab95b849e66f3221d80a67eef2ec6e3730901a8 anv: Refactor descriptor pushing a bit
+5c30fffeec1732c21d600c036f95f8cdb1bb5487 anv: Take references to push descriptor set layouts
+
+# shaCommit references invalid sha - a offender did not land in branch.
+85ee157283c667372baf7c03259cba08853f0067 gitlab-ci: autotools needs to be told which llvm version to use
+
+# revert The commit was reverted shortly after it was applied on master
+47fc359822494935852de1e70e4d840b2fe6a25c anv: release memory allocated by glsl types during spirv_to_nir
+
+# stable Explicitly 19.0 nomination, seemingly a performance patch
+5ef2b8f1f2ebcdb4ffe5c98b3f4f48e584cb4b22 nir: Add a pass for lowering IO back to vector when possible
+
+# fixes Temporary block perf. fix depending on previous opt. pass
+6d5d89d25a0a4299dbfcbfeca71b6c7e65ef3d45 intel/nir: Vectorize all IO
diff --git a/bin/install_megadrivers.py b/bin/install_megadrivers.py
index d29b1911218..b5ac78887bf 100644
--- a/bin/install_megadrivers.py
+++ b/bin/install_megadrivers.py
@@ -35,7 +35,11 @@ def main():
 args = parser.parse_args()
 
 if os.path.isabs(args.libdir):
-to = os.path.join(os.environ.get('DESTDIR', '/'), args.libdir[1:])
+destdir = os.environ.get('DESTDIR')
+if destdir:
+to = os.path.join(destdir, args.libdir[1:])
+else:
+to = args.libdir
 else:
 to = os.path.join(os.environ['MESON_INSTALL_DESTDIR_PREFIX'], args.libdir)
 
@@ -45,7 +49,6 @@ def main():
 if os.path.lexists(to):
 os.unlink(to)
 os.makedirs(to)
-shutil.copy(args.megadriver, master)
 
 for driver in args.drivers:
 abs_driver = os.path.join(to, driver)
@@ -67,7 +70,14 @@ def main():
 name, ext = os.path.splitext(name)
 finally:
 os.chdir(ret)
+
+# Remove meson-created master .so and symlinks
 os.unlink(master)
+name, ext = os.path.splitext(master)
+while ext != '.so':
+if os.path.lexists(name):
+os.unlink(name)
+name, ext = os.path.splitext(name)
 
 
 if __name__ == '__main__':
diff --git a/debian/changelog b/debian/changelog
index 4d94b368e1f..70ce002e9c5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,25 @@
+mesa (18.3.6-2) unstable; urgency=medium
+
+  * Cherry-pick c77acc3ceba (meson: remove meson-created megadrivers
+symlinks) from upstream master branch. Removes a broken symlink
+(Closes: #926857).
+
+ -- Andreas Boll   Sat, 11 May 2019 15:43:07 +0200
+
+mesa (18.3.6-1) unstable; urgency=medium
+
+  [ Timo Aaltonen ]
+  * libgl1-mesa-dri: Remove /etc/drirc which isn't installed anymore.
+(Closes: #920241)
+
+  [ Andreas Boll ]
+  * New upstream release.
+- wayland/egl: Ensure EGL surface is resized on DRI
+  update_buffers(). Fixes a crash with xwayland (Closes: #922346).
+  * Rebase patches/fix-hurd-ftbfs.diff.
+
+ -- Andreas Boll   Sat, 06 Apr 2019 20:58:43 +0200
+
 mesa (18.3.4-2) unstable; urgency=medium
 
   * Cherry-pick f6556ec7d12 (dri: meson: do not prefix user provided dri-
diff --git a/debian/gbp.conf 

Bug#928764: alsa-utils does not store or restore configuration

[Elimar Riesebieter]

* MERLIN Philippe  [2019-05-11 16:19 +0200]:

[...]

> > > > > The result:
> > > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > 
> > > > Please post the output of:
> > > > 
> > > > $ ls -al /etc/alsa
> > > > $ ls -al /etc/alsa/conf.d
> > > > $ ls -al /var/lib/alsa
> > > > $ ls -al ~/.asoundrc
> > > > 
> > > > Elimar
> > > 
> > > s -al /etc/alsa
> > > export LANG=C| ls -al ~/.asoundrc
> > 
> > ?
> > 
> > Elimar
> Sorry:
> 
> export LANG=C| ls -al ~/.asoundrc 

Try as follows ;-)

$ LC_ALL=C ls -al ~/.asoundrc
ls: cannot access '/home/users/riesebie/.asoundrc': No such file or directory

Well, it seems that you don't have pulseaudio nor libasound2-plugins
installed. Otherwise you should have an output of:

$ ls -al /etc/alsa/conf.d
drwxr-xr-x 2 root root 335 Feb 16 08:16 ./
drwxr-xr-x 3 root root  20 Apr 10 14:17 ../
lrwxrwxrwx 1 root root  44 Jan 26 16:17 10-rate-lav.conf -> 
/usr/share/alsa/alsa.conf.d/10-rate-lav.conf
lrwxrwxrwx 1 root root  46 Jan 26 16:17 10-samplerate.conf -> 
/usr/share/alsa/alsa.conf.d/10-samplerate.conf
lrwxrwxrwx 1 root root  45 Jan 26 16:17 10-speexrate.conf -> 
/usr/share/alsa/alsa.conf.d/10-speexrate.conf
lrwxrwxrwx 1 root root  48 Jan 26 16:17 50-arcam-av-ctl.conf -> 
/usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf
lrwxrwxrwx 1 root root  40 Jan 26 16:17 50-jack.conf -> 
/usr/share/alsa/alsa.conf.d/50-jack.conf
lrwxrwxrwx 1 root root  39 Jan 26 16:17 50-oss.conf -> 
/usr/share/alsa/alsa.conf.d/50-oss.conf
lrwxrwxrwx 1 root root  46 Jan 26 16:17 50-pulseaudio.conf -> 
/usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
lrwxrwxrwx 1 root root  47 Jan 26 16:17 60-a52-encoder.conf -> 
/usr/share/alsa/alsa.conf.d/60-a52-encoder.conf
lrwxrwxrwx 1 root root  41 Jan 26 16:17 60-upmix.conf -> 
/usr/share/alsa/alsa.conf.d/60-upmix.conf
lrwxrwxrwx 1 root root  44 Jan 26 16:17 60-vdownmix.conf -> 
/usr/share/alsa/alsa.conf.d/60-vdownmix.conf
lrwxrwxrwx 1 root root  46 Jan 26 16:17 98-usb-stream.conf -> 
/usr/share/alsa/alsa.conf.d/98-usb-stream.conf
lrwxrwxrwx 1 root root  38 Feb 15 00:05 99-pulse.conf -> 
/usr/share/alsa/alsa.conf.d/pulse.conf
-rw-r--r-- 1 root root 201 Nov 10 16:29 99-pulseaudio-default.conf.example

Elimar
-- 
  355/113: Not the famous irrational number pi,
   but an incredible simulation!
-unknown


signature.asc
Description: PGP signature

Bug#904309: tilda: diff for NMU version 1.4.1-2.1

[Sebastian Geiger]

Hi Niels,

Thanks for the upload. It looks good to me. I think you can push that to the 
repository. 

Best Regards
Mit freundlichen Grüßen
Dipl. Ing. Sebastian Geiger

> On 11. May 2019, at 15:04, Niels Thykier  wrote:
> 
> Control: tags 904309 + patch
> Control: tags 904309 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for tilda (versioned as 1.4.1-2.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> 
> diff -Nru tilda-1.4.1/debian/changelog tilda-1.4.1/debian/changelog
> --- tilda-1.4.1/debian/changelog2018-02-18 20:08:42.0 +
> +++ tilda-1.4.1/debian/changelog2019-05-11 13:04:23.0 +
> @@ -1,3 +1,15 @@
> +tilda (1.4.1-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Import patch from upstream to set ensure tilda is run
> +under the X11 backend.  This prevents crashes when the
> +window manager uses Wayland by default.
> +(Closes: #904309)
> +  * Ret Rules-Requires-Root to no as tilda does not need
> +(fake)root for building the debs.
> +
> + -- Niels Thykier   Sat, 11 May 2019 13:04:23 +
> +
> tilda (1.4.1-2) unstable; urgency=medium
> 
>   [ Sebastian Geiger ]
> diff -Nru tilda-1.4.1/debian/control tilda-1.4.1/debian/control
> --- tilda-1.4.1/debian/control2018-02-18 19:46:04.0 +
> +++ tilda-1.4.1/debian/control2019-05-11 11:30:38.0 +
> @@ -5,6 +5,7 @@
> Build-Depends: debhelper (>= 11), autopoint, pkg-config, libgtk-3-dev, 
> libvte-2.91-dev, libconfuse-dev
> Standards-Version: 4.1.3
> Homepage: http://github.com/lanoxx/tilda
> +Rules-Requires-Root: no
> Vcs-Git: https://salsa.debian.org/debian/tilda.git
> Vcs-Browser: https://salsa.debian.org/debian/tilda
> 
> diff -Nru tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch 
> tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
> --- tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
> 1970-01-01 00:00:00.0 +
> +++ tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
> 2019-05-11 11:29:06.0 +
> @@ -0,0 +1,25 @@
> +From 606b655d8d811f880d610dead7d6943a33199deb Mon Sep 17 00:00:00 2001
> +From: Roman Hoellen 
> +Date: Mon, 30 Apr 2018 09:18:49 +0200
> +Subject: [PATCH] Set supported backend to X11
> +Upstream-Commit: 
> https://github.com/lanoxx/tilda/commit/606b655d8d811f880d610dead7d6943a33199deb.patch
> +Forwarded: Not-needed
> +
> +---
> + src/tilda.c | 3 +++
> + 1 file changed, 3 insertions(+)
> +
> +diff --git a/src/tilda.c b/src/tilda.c
> +index 8aa69828..92ce46c4 100644
> +--- a/src/tilda.c
>  b/src/tilda.c
> +@@ -686,6 +686,9 @@ int main (int argc, char *argv[])
> + g_log_set_default_handler (tilda_log_handler, NULL);
> + #endif
> + 
> ++/* Set supported backend to X11 */
> ++gdk_set_allowed_backends ("x11");
> ++
> + tilda_window tw;
> + /* NULL set the tw pointers so we can get a clean exit on 
> initialization failure */
> + memset(, 0, sizeof(tilda_window));
> diff -Nru tilda-1.4.1/debian/patches/series tilda-1.4.1/debian/patches/series
> --- tilda-1.4.1/debian/patches/series2018-02-18 19:48:15.0 +
> +++ tilda-1.4.1/debian/patches/series2019-05-11 11:30:38.0 +
> @@ -1 +1,2 @@
> 01_install_metadata_in_new_location.patch
> +02_set_supported_backend_to_X11.patch

Bug#928764: alsa-utils does not store or restore configuration

[MERLIN Philippe]

Le samedi 11 mai 2019, 16:12:38 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe  [2019-05-11 16:06 +0200]:
> > Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> > > * MERLIN Philippe  [2019-05-11 14:38 
+0200]:
> > > > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > > > Hi merlin,
> > > > > 
> > > > > * merlin  [2019-05-10 17:59 +0200]:
> > > > > > Package: alsa-utils
> > > > > > Version: 1.1.8-2
> > > > > > Severity: important
> > > > > > 
> > > > > > Dear Maintainer,
> > > > > > 
> > > > > > At each start of the computer the sound function is absent so that
> > > > > > it
> > > > > > works the only method that I found is to launch in a window the
> > > > > > alsamixer
> > > > > > program and to modify a parameter and the sound is restored,the
> > > > > > most
> > > > > > surprising is that the parameters previously saved by alsamixer
> > > > > > are
> > > > > > present.
> > > > > 
> > > > > could you please check the status of alsa's systdemd services?
> > > > > 
> > > > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs
> > > > > systemctl
> > > > > status
> > > > > 
> > > > > 
> > > > > Elimar
> > > > 
> > > > The result:
> > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > 
> > > Please post the output of:
> > > 
> > > $ ls -al /etc/alsa
> > > $ ls -al /etc/alsa/conf.d
> > > $ ls -al /var/lib/alsa
> > > $ ls -al ~/.asoundrc
> > > 
> > > Elimar
> > 
> > s -al /etc/alsa
> > export LANG=C| ls -al ~/.asoundrc
> 
> ?
> 
> Elimar
Sorry it seems that a character cut the message :
export Lang=C| ls -al ~/.asoundrc
ls : cannot access /home/philippe/.asoundrc : No such file or directory

Philippe Merlin

Bug#928806: evince: Printing when viewing dvi file doesn't work: Permission denied

[Manuel Bilderbeek]

Package: evince
Version: 3.30.2-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I viewed a DVI file on with evince and clicked on the Print icon in the menu.
Selected printer and pressed OK. Nothing happend.
Message in terminal:
 Failed to execute child process “dvipdfm” (Permission denied)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

No idea what I could do. But manually running dvipdfm on the file and lpr'ing
it resulted in a good print.

I think this worked fine a few months ago... but I don't know what changed.

Kind regards,
Manuel

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
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)
LSM: AppArmor: enabled

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evince-common3.30.2-3
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libevdocument3-4 3.30.2-3
ii  libevview3-3 3.30.2-3
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgnome-desktop-3-173.30.2.1-1
ii  libgtk-3-0   3.24.5-1
ii  libnautilus-extension1a  3.30.5-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libsecret-1-00.18.7-1
ii  shared-mime-info 1.10-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1

Versions of packages evince suggests:
ii  gvfs 1.38.1-3
ii  nautilus-sendto  3.8.6-3
ii  poppler-data 0.4.9-2
ii  unrar1:5.6.6-1

-- no debconf information

Bug#928764: alsa-utils does not store or restore configuration

[MERLIN Philippe]

Le samedi 11 mai 2019, 16:12:38 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe  [2019-05-11 16:06 +0200]:
> > Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> > > * MERLIN Philippe  [2019-05-11 14:38 +0200]:
> > > > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > > > Hi merlin,
> > > > > 
> > > > > * merlin  [2019-05-10 17:59 +0200]:
> > > > > > Package: alsa-utils
> > > > > > Version: 1.1.8-2
> > > > > > Severity: important
> > > > > > 
> > > > > > Dear Maintainer,
> > > > > > 
> > > > > > At each start of the computer the sound function is absent so that
> > > > > > it
> > > > > > works the only method that I found is to launch in a window the
> > > > > > alsamixer
> > > > > > program and to modify a parameter and the sound is restored,the
> > > > > > most
> > > > > > surprising is that the parameters previously saved by alsamixer
> > > > > > are
> > > > > > present.
> > > > > 
> > > > > could you please check the status of alsa's systdemd services?
> > > > > 
> > > > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs
> > > > > systemctl
> > > > > status
> > > > > 
> > > > > 
> > > > > Elimar
> > > > 
> > > > The result:
> > > > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > 
> > > Please post the output of:
> > > 
> > > $ ls -al /etc/alsa
> > > $ ls -al /etc/alsa/conf.d
> > > $ ls -al /var/lib/alsa
> > > $ ls -al ~/.asoundrc
> > > 
> > > Elimar
> > 
> > s -al /etc/alsa
> > export LANG=C| ls -al ~/.asoundrc
> 
> ?
> 
> Elimar
Sorry:

export LANG=C| ls -al ~/.asoundrc 

Bug#928764: alsa-utils does not store or restore configuration

[Elimar Riesebieter]

* MERLIN Philippe  [2019-05-11 16:06 +0200]:

> Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> > * MERLIN Philippe  [2019-05-11 14:38 +0200]:
> > > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > > Hi merlin,
> > > > 
> > > > * merlin  [2019-05-10 17:59 +0200]:
> > > > > Package: alsa-utils
> > > > > Version: 1.1.8-2
> > > > > Severity: important
> > > > > 
> > > > > Dear Maintainer,
> > > > > 
> > > > > At each start of the computer the sound function is absent so that it
> > > > > works the only method that I found is to launch in a window the
> > > > > alsamixer
> > > > > program and to modify a parameter and the sound is restored,the most
> > > > > surprising is that the parameters previously saved by alsamixer are
> > > > > present.
> > > > 
> > > > could you please check the status of alsa's systdemd services?
> > > > 
> > > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > > status
> > > > 
> > > > 
> > > > Elimar
> > > 
> > > The result:
> > > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > status *●* alsa-restore.service - Save/Restore Sound Card State
> > > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > 
> > Please post the output of:
> > 
> > $ ls -al /etc/alsa
> > $ ls -al /etc/alsa/conf.d
> > $ ls -al /var/lib/alsa
> > $ ls -al ~/.asoundrc
> > 
> > Elimar
> s -al /etc/alsa 
> export LANG=C| ls -al ~/.asoundrc 

?

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


signature.asc
Description: PGP signature

Bug#928718: stretch-pu: groonga/6.1.5-1+deb9u1

[Kentaro Hayashi]

Hi,

It should be stretch-proposed-updates instead stretch.
Here is the updated debdiff just for changing target:

debdiff groonga_6.1.5-1.dsc groonga_6.1.5-1+deb9u1.dsc
diff -Nru groonga-6.1.5/debian/changelog groonga-6.1.5/debian/changelog
--- groonga-6.1.5/debian/changelog  2017-01-23 19:14:09.0 +0900
+++ groonga-6.1.5/debian/changelog  2019-05-11 22:22:01.0 +0900
@@ -1,3 +1,13 @@
+groonga (6.1.5-1+deb9u1) stretch-proposed-updates; urgency=medium
+
+  * debian/groonga-httpd.logrotate
+debian/groonga-server-gqtp.logrotate
+- Mitigate privilege escalation by changing the owner and group of logs
+  with "su" option. Reported by Wolfgang Hotwagner.
+  (Closes: #928304) (CVE-2019-11675)
+
+ -- Kentaro Hayashi   Sat, 11 May 2019 22:22:01 +0900
+
 groonga (6.1.5-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru groonga-6.1.5/debian/groonga-httpd.logrotate 
groonga-6.1.5/debian/groonga-httpd.logrotate
--- groonga-6.1.5/debian/groonga-httpd.logrotate2016-12-10 
15:18:50.0 +0900
+++ groonga-6.1.5/debian/groonga-httpd.logrotate2019-05-09 
23:33:43.0 +0900
@@ -1,11 +1,11 @@
 /var/log/groonga/httpd/*.log {
+su groonga groonga
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
-create 640 groonga groonga
 sharedscripts
 postrotate
 . /etc/default/groonga-httpd
diff -Nru groonga-6.1.5/debian/groonga-server-gqtp.logrotate 
groonga-6.1.5/debian/groonga-server-gqtp.logrotate
--- groonga-6.1.5/debian/groonga-server-gqtp.logrotate  2016-12-10 
15:18:50.0 +0900
+++ groonga-6.1.5/debian/groonga-server-gqtp.logrotate  2019-05-09 
23:33:43.0 +0900
@@ -1,11 +1,11 @@
 /var/log/groonga/*-gqtp.log {
+su groonga groonga
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
-create 640 groonga groonga
 sharedscripts
 postrotate
 . /etc/default/groonga-server-gqtp


Regards,
diff -Nru groonga-6.1.5/debian/changelog groonga-6.1.5/debian/changelog
--- groonga-6.1.5/debian/changelog	2017-01-23 19:14:09.0 +0900
+++ groonga-6.1.5/debian/changelog	2019-05-11 22:22:01.0 +0900
@@ -1,3 +1,13 @@
+groonga (6.1.5-1+deb9u1) stretch-proposed-updates; urgency=medium
+
+  * debian/groonga-httpd.logrotate
+debian/groonga-server-gqtp.logrotate
+- Mitigate privilege escalation by changing the owner and group of logs
+  with "su" option. Reported by Wolfgang Hotwagner.
+  (Closes: #928304) (CVE-2019-11675)
+
+ -- Kentaro Hayashi   Sat, 11 May 2019 22:22:01 +0900
+
 groonga (6.1.5-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru groonga-6.1.5/debian/groonga-httpd.logrotate groonga-6.1.5/debian/groonga-httpd.logrotate
--- groonga-6.1.5/debian/groonga-httpd.logrotate	2016-12-10 15:18:50.0 +0900
+++ groonga-6.1.5/debian/groonga-httpd.logrotate	2019-05-09 23:33:43.0 +0900
@@ -1,11 +1,11 @@
 /var/log/groonga/httpd/*.log {
+su groonga groonga
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
-create 640 groonga groonga
 sharedscripts
 postrotate
 . /etc/default/groonga-httpd
diff -Nru groonga-6.1.5/debian/groonga-server-gqtp.logrotate groonga-6.1.5/debian/groonga-server-gqtp.logrotate
--- groonga-6.1.5/debian/groonga-server-gqtp.logrotate	2016-12-10 15:18:50.0 +0900
+++ groonga-6.1.5/debian/groonga-server-gqtp.logrotate	2019-05-09 23:33:43.0 +0900
@@ -1,11 +1,11 @@
 /var/log/groonga/*-gqtp.log {
+su groonga groonga
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
-create 640 groonga groonga
 sharedscripts
 postrotate
 . /etc/default/groonga-server-gqtp

Bug#928764: alsa-utils does not store or restore configuration

[MERLIN Philippe]

Le samedi 11 mai 2019, 15:33:23 CEST Elimar Riesebieter a écrit :
> * MERLIN Philippe  [2019-05-11 14:38 +0200]:
> > Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > > Hi merlin,
> > > 
> > > * merlin  [2019-05-10 17:59 +0200]:
> > > > Package: alsa-utils
> > > > Version: 1.1.8-2
> > > > Severity: important
> > > > 
> > > > Dear Maintainer,
> > > > 
> > > > At each start of the computer the sound function is absent so that it
> > > > works the only method that I found is to launch in a window the
> > > > alsamixer
> > > > program and to modify a parameter and the sound is restored,the most
> > > > surprising is that the parameters previously saved by alsamixer are
> > > > present.
> > > 
> > > could you please check the status of alsa's systdemd services?
> > > 
> > > # systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > > status
> > > 
> > > 
> > > Elimar
> > 
> > The result:
> > systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > status *●* alsa-restore.service - Save/Restore Sound Card State
> > *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> > *●* alsa-state.service - Manage Sound Card State (restore and store)
> > *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago
> 
> Please post the output of:
> 
> $ ls -al /etc/alsa
> $ ls -al /etc/alsa/conf.d
> $ ls -al /var/lib/alsa
> $ ls -al ~/.asoundrc
> 
> Elimar
s -al /etc/alsa 
export LANG=C| ls -al ~/.asoundrc 

thanks.
Philippe Merlin

Bug#928805: texlive-lang-czechslovak: fails to install: fmtutil failed

[Andreas Beckmann]

Package: texlive-lang-czechslovak
Version: 2019.20190508-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up texlive-lang-czechslovak (2019.20190508-1) ...
  Processing triggers for libc-bin (2.28-10) ...
  Processing triggers for tex-common (6.11) ...
  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
This may take some time... 
  fmtutil failed. Output has been stored in
  /tmp/fmtutil.N6i3uEq3
  Please include this file if you report a bug.
  
  dpkg: error processing package tex-common (--configure):
   installed tex-common package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   tex-common


cheers,

Andreas


texlive-lang-czechslovak_2019.20190508-1.log.gz
Description: application/gzip


fmtutil.XKntgsu4.gz
Description: application/gzip

Bug#928764: alsa-utils does not store or restore configuration

[Elimar Riesebieter]

* MERLIN Philippe  [2019-05-11 14:38 +0200]:

> Le samedi 11 mai 2019, 13:11:23 CEST Elimar Riesebieter a écrit :
> > Hi merlin,
> > 
> > * merlin  [2019-05-10 17:59 +0200]:
> > > Package: alsa-utils
> > > Version: 1.1.8-2
> > > Severity: important
> > > 
> > > Dear Maintainer,
> > > 
> > > At each start of the computer the sound function is absent so that it
> > > works the only method that I found is to launch in a window the alsamixer
> > > program and to modify a parameter and the sound is restored,the most
> > > surprising is that the parameters previously saved by alsamixer are
> > > present.
> > 
> > could you please check the status of alsa's systdemd services?
> > 
> > # systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl
> > status
> > 
> > 
> > Elimar
> The result:
> systemctl -t service | grep alsa | awk '{print $1}' | xargs systemctl status 
> *●* alsa-restore.service - Save/Restore Sound Card State 
> *active (exited)* since Sat 2019-05-11 14:24:23 CEST; 6min ago 
> *●* alsa-state.service - Manage Sound Card State (restore and store) 
> *active (running)* since Sat 2019-05-11 14:24:23 CEST; 6min ago 

Please post the output of:

$ ls -al /etc/alsa
$ ls -al /etc/alsa/conf.d
$ ls -al /var/lib/alsa
$ ls -al ~/.asoundrc

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


signature.asc
Description: PGP signature

Bug#923181: Please add support for reporting mouse button presses to console programs which support mouse trackingo

[Daniel Abrecht]

On 26/04/2019 14.30, Bill Allombert wrote:
> On Thu, Apr 04, 2019 at 06:52:04PM +, Daniel Abrecht wrote:
>> On 22/03/2019 21.33, Bill Allombert wrote:
 I'm not sure what the best course of action is. Some possibilities are:
  * If it isn't too much of a problem, we could just leave it how it is.
  * We could disable selections while mouse tracking is active
>>>
>>> If this can be done on a per tty basis, this might be the best course of
>>> action.
>>
>> Ok, I've now created patch for this. This time, I've based the patch on
>> the current master branch (commit
>> c12a8c2d0cf72a340b13b00e6d4b98bfed57ce01) of the salsa.debian.org git repo.
> 
> This version seems to work much better when reporting.
> Thanks!

I'm glad to hear that. If there is anything left you want me to change,
I'm always happy to help.

Regards,
Daniel Abrecht



signature.asc
Description: OpenPGP digital signature

Bug#925178: closed by Utkarsh Gupta (Bug#925178: fixed in ruby-globalid 0.4.2-1)

[Paul Gevers]

Hi,

On Mon, 29 Apr 2019 21:42:09 +0200 Paul Gevers  wrote:
> As it turned out that the failure was *not* only a failure in the
> autopkgtest, but also in the build, we need a fix for buster. The above
> changes don't qualify, can you please revert the changes and upload the
> old version (version something like 0.4.2+really-...) with only the fix?

Ping. If not fixed in buster, this may lead to the removal of rails from
buster.

Paul

elbrus@respighi:~$ dak rm --no-action -R --suite=testing ruby-globalid
Will remove the following packages from testing:

ruby-globalid |0.3.6-2 | source, all

Maintainer: Debian Ruby Extras Maintainers


--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
rails: ruby-activejob

# Broken Build-Depends:
rails: ruby-globalid (>= 0.3.6)

Dependency problem found.



signature.asc
Description: OpenPGP digital signature

Bug#928804: lxqt-session allocates memory for process output never read

[Alf Gaida]

Package: lxqt-session
Version: 0.14.2~15-g55a59f8-1
Severity: important
Tags: patch

The way is to forward output from these processes to lxqt-session stdout. This 
is discussed in
https://github.com/lxqt/lxqt/issues/442 and 
https://github.com/lxqt/lxqt-session/pull/256

Patch:

Author: Luís Pereira 
Date:   Thu May 9 21:14:08 2019 +0100

Don't throw stderr/stdout to a black hole
Implement the consensus solution achieved described in 
https://github.com/lxqt/lxqt-session/pull/256.
It was, actually, one the alternative proposed by https://github.com/keturn.

diff --git a/lxqt-session/src/lxqtmodman.cpp b/lxqt-session/src/lxqtmodman.cpp
index 2beff61..d11ffc0 100644
--- a/lxqt-session/src/lxqtmodman.cpp
+++ b/lxqt-session/src/lxqtmodman.cpp
@@ -467,6 +467,7 @@ LXQtModule::LXQtModule(const XdgDesktopFile& file, QObject* 
parent) :
 fileName(QFileInfo(file.fileName()).fileName()),
 mIsTerminating(false)
 {
+QProcess::setProcessChannelMode(QProcess::ForwardedChannels);
 connect(this, SIGNAL(stateChanged(QProcess::ProcessState)), 
SLOT(updateState(QProcess::ProcessState)));
 }
 


-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.0.14-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lxqt-session depends on:
ii  libc6   2.28-10
ii  libkf5windowsystem5 5.54.0-1
ii  liblxqt00.14.2~12-ga398a7c-1
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5dbus5 5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-1
ii  libqt5widgets5  5.11.3+dfsg1-1
ii  libqt5x11extras55.11.3-2
ii  libqt5xdg3  3.4.0~13-ga0c8e32-1
ii  libstdc++6  8.3.0-7
ii  libudev1241-3
ii  libx11-62:1.6.7-1
ii  lxqt-qtplugin   0.14.1~8-g02a9e71-1
ii  lxqt-theme-debian [lxqt-theme]  0.14.0.3
ii  lxqt-themes [lxqt-theme]0.14.0-1
ii  x11-xkb-utils   7.7+4

Versions of packages lxqt-session recommends:
ii  lxqt-config   0.14.2~49-ge265219-1
ii  lxqt-notificationd0.14.2~17-ga5ee062-1
ii  lxqt-policykit0.14.1-1
ii  lxqt-powermanagement  0.14.2~14-ge9c8192-1
ii  lxqt-session-l10n 0.14.2~15-g55a59f8-1
ii  lxqt-sudo 0.14.2~9-g544b8d0-1
ii  pcmanfm-qt0.14.2~21-g40e9db1-1
ii  qlipper   1:5.1.2-1
ii  qps   1.10.21~15-gdfd70d8-1
ii  suckless-tools44-1
ii  xscreensaver  5.42+dfsg1-1

lxqt-session suggests no packages.

-- no debconf information

Bug#904309: tilda: diff for NMU version 1.4.1-2.1

[Niels Thykier]

Control: tags 904309 + patch
Control: tags 904309 + pending


Dear maintainer,

I've prepared an NMU for tilda (versioned as 1.4.1-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru tilda-1.4.1/debian/changelog tilda-1.4.1/debian/changelog
--- tilda-1.4.1/debian/changelog2018-02-18 20:08:42.0 +
+++ tilda-1.4.1/debian/changelog2019-05-11 13:04:23.0 +
@@ -1,3 +1,15 @@
+tilda (1.4.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Import patch from upstream to set ensure tilda is run
+under the X11 backend.  This prevents crashes when the
+window manager uses Wayland by default.
+(Closes: #904309)
+  * Ret Rules-Requires-Root to no as tilda does not need
+(fake)root for building the debs.
+
+ -- Niels Thykier   Sat, 11 May 2019 13:04:23 +
+
 tilda (1.4.1-2) unstable; urgency=medium
 
   [ Sebastian Geiger ]
diff -Nru tilda-1.4.1/debian/control tilda-1.4.1/debian/control
--- tilda-1.4.1/debian/control  2018-02-18 19:46:04.0 +
+++ tilda-1.4.1/debian/control  2019-05-11 11:30:38.0 +
@@ -5,6 +5,7 @@
 Build-Depends: debhelper (>= 11), autopoint, pkg-config, libgtk-3-dev, 
libvte-2.91-dev, libconfuse-dev
 Standards-Version: 4.1.3
 Homepage: http://github.com/lanoxx/tilda
+Rules-Requires-Root: no
 Vcs-Git: https://salsa.debian.org/debian/tilda.git
 Vcs-Browser: https://salsa.debian.org/debian/tilda
 
diff -Nru tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch 
tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
--- tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
1970-01-01 00:00:00.0 +
+++ tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
2019-05-11 11:29:06.0 +
@@ -0,0 +1,25 @@
+From 606b655d8d811f880d610dead7d6943a33199deb Mon Sep 17 00:00:00 2001
+From: Roman Hoellen 
+Date: Mon, 30 Apr 2018 09:18:49 +0200
+Subject: [PATCH] Set supported backend to X11
+Upstream-Commit: 
https://github.com/lanoxx/tilda/commit/606b655d8d811f880d610dead7d6943a33199deb.patch
+Forwarded: Not-needed
+
+---
+ src/tilda.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/src/tilda.c b/src/tilda.c
+index 8aa69828..92ce46c4 100644
+--- a/src/tilda.c
 b/src/tilda.c
+@@ -686,6 +686,9 @@ int main (int argc, char *argv[])
+ g_log_set_default_handler (tilda_log_handler, NULL);
+ #endif
+ 
++/* Set supported backend to X11 */
++gdk_set_allowed_backends ("x11");
++
+ tilda_window tw;
+ /* NULL set the tw pointers so we can get a clean exit on initialization 
failure */
+ memset(, 0, sizeof(tilda_window));
diff -Nru tilda-1.4.1/debian/patches/series tilda-1.4.1/debian/patches/series
--- tilda-1.4.1/debian/patches/series   2018-02-18 19:48:15.0 +
+++ tilda-1.4.1/debian/patches/series   2019-05-11 11:30:38.0 +
@@ -1 +1,2 @@
 01_install_metadata_in_new_location.patch
+02_set_supported_backend_to_X11.patch