Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

[NIIBE Yutaka]

Hello,

I managed to identify the bug and upload the fix.  Thanks.
-- 

Bug#926788: marked as done (gauche-c-wrapper: FTBFS randomly (autobuilder hangs))

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2019 04:18:32 +
with message-id 
and subject line Bug#926788: fixed in gauche-c-wrapper 0.6.1-11
has caused the Debian Bug report #926788,
regarding gauche-c-wrapper: FTBFS randomly (autobuilder hangs)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gauche-c-wrapper
Version: 0.6.1-10
Severity: serious
Tags: ftbfs patch

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure --prefix=/usr --includedir=/usr/include \
--mandir=/usr/share/man --infodir=/usr/share/info \
--sysconfdir=/etc --localstatedir=/var \
--libdir=/usr/lib --libexecdir=/usr/lib
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for gosh... /usr/bin/gosh
checking for gauche-config... /usr/bin/gauche-config
checking for gauche-package... /usr/bin/gauche-package
checking for gauche-install... /usr/bin/gauche-install
checking for gauche-cesconv... /usr/bin/gauche-cesconv
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for bison... no
checking for byacc... no
checking for makeinfo... makeinfo
checking for gzip... gzip
checking for sed... sed
checking for ldconfig... /sbin/ldconfig
sed: can't read s/-f[a-z]*-prefix-map=[^ ]* //: No such file or directory
configure: creating c-wrapper.gpd
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating lib/Makefile
config.status: creating objc/Makefile
config.status: creating testsuite/Makefile
config.status: creating src/cwcompile
config.status: creating lib/c-wrapper/config.scm
config.status: creating lib/c-wrapper/stubgen.scm
config.status: creating doc/Makefile
make[1]: Leaving directory '/<>'
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
cd src; make all
make[2]: Entering directory '/<>/src'
/usr/bin/gauche-package compile --cppflags="-DGAUCHE_API_0_8_8 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE" --ldflags="-Wl,-z,relro " 
--libs="/usr/lib/x86_64-linux-gnu/libffi_pic.a " --verbose c-ffi c-ffi.c 
c-ffilib.stub closure_alloc.c
gcc -c -DGAUCHE_API_0_8_8 -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
'-I/usr/lib/gauche-0.9/0.9.6/include' '-I/usr/lib/gauche-0.9/site/include' -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -o 'c-ffi.o' 'c-ffi.c'
gcc -c -DGAUCHE_API_0_8_8 -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
'-I/usr/lib/gauche-0.9/0.9.6/include' '-I/usr/lib/gauche-0.9/site/include' -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -o 'c-ffilib.o' 'c-ffilib.c'
gcc -c -DGAUCHE_API_0_8_8 -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
'-I/usr/lib/gauche-0.9/0.9.6/include' '-I/usr/lib/gauche-0.9/site/include' -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -o 'closure_alloc.o' 'closure_alloc.c'
gcc -Wl,-z,relro  '-L/usr/lib/gauche-0.9/0.9.6/x86_64-pc-linux-gnu' 
'-L/usr/lib/gauche-0.9/site/x86_64-pc-linux-gnu'  -shared -o c-ffi.so 'c-ffi.o' 
'c-ffilib.o' 'closure_alloc.o' -lgauche-0.9 -ldl -lcrypt -lrt -lm  -lpthread 
/usr/lib/x86_64-linux-gnu/libffi_pic.a 
/usr/bin/gauche-package compile --cppflags="-DGAUCHE_API_0_8_8 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE" --ldflags="-Wl,-z,relro " 
--libs="/usr/lib/x86_64-linux-gnu/libffi_pic.a " --verbose c-lex c-lex.c 
c-lexlib.stub
gcc -c -DGAUCHE_API_0_8_8 -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE 
'-I/usr/lib/gauche-0.9/0.9.6/include' '-I/usr/lib/gauche-0.9/site/include' -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -o 'c-lex.o' 'c-lex.c'
gcc -c -DGAUCHE_API_0_8_8 -Wdate-time -D_FORTIFY_SOURCE=2 

Bug#921232: Tracking it down

[Joseph Shields]

This is fine in master, but I can repro it with an otherwise clean upstream git 
tag w/ our 4 s390x backports. Bisecting.

Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2019 02:35:04 +
with message-id 
and subject line Bug#905929: fixed in sysdig 0.24.1-3
has caused the Debian Bug report #905929,
regarding sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to 
compile
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysdig
Version: 0.22.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=sysdig

...
cd /<>/obj-aarch64-linux-gnu/userspace/libscap && /usr/bin/cc 
-DHAS_CAPTURE -DK8S_DISABLE_THREAD -DPLATFORM_NAME=\"Linux\" 
-I/<>/common  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -ggdb   -o 
CMakeFiles/scap.dir/__/__/driver/fillers_table.c.o   -c 
/<>/driver/fillers_table.c
/<>/driver/syscall_table.c:54:3: error: '__NR_open' undeclared 
here (not in a function); did you mean 'f_sys_open_x'?
  [__NR_open - SYSCALL_TABLE_ID0] =   {UF_USED | 
UF_NEVER_DROP, PPME_SYSCALL_OPEN_E, PPME_SYSCALL_OPEN_X},
   ^
--- End Message ---
--- Begin Message ---
Source: sysdig
Source-Version: 0.24.1-3

We believe that the bug you reported is fixed in the latest version of
sysdig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated sysdig 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Apr 2019 21:55:31 -0400
Source: sysdig
Architecture: source
Version: 0.24.1-3
Distribution: unstable
Urgency: high
Maintainer: Evgeni Golov 
Changed-By: Harlan Lieberman-Berg 
Closes: 905929
Changes:
 sysdig (0.24.1-3) unstable; urgency=high
 .
   * Refresh patch to fix missed #ifdef (Closes: #905929)
Checksums-Sha1:
 716b20f817c0fd8f3a7a1c8e4788a636b5a80a9d 2368 sysdig_0.24.1-3.dsc
 0130a3e3e397ba3ba254dcc3f26b4d3968b10b54 10212 sysdig_0.24.1-3.debian.tar.xz
 7955d2225141b5fa935141b41932ad2a8807eb1a 7695 sysdig_0.24.1-3_amd64.buildinfo
Checksums-Sha256:
 fb711e82611e73bb645088ea4b283d0c92f4222be6f41e1c05f1a6d7ef948e86 2368 
sysdig_0.24.1-3.dsc
 2203e183777677e53e23693bfc8bc4b53d61fcafefe48bcba0cfbc5d9009a606 10212 
sysdig_0.24.1-3.debian.tar.xz
 92c0ac6f61f4ed3d4f0b6440a5748e21ebe704b318ad4dbcf81306a4dde2c638 7695 
sysdig_0.24.1-3_amd64.buildinfo
Files:
 fdaceb877fe79c3e298aaa262ca12218 2368 admin optional sysdig_0.24.1-3.dsc
 49c8bc29985e3a72fc82a814d655ce90 10212 admin optional 
sysdig_0.24.1-3.debian.tar.xz
 757661702328d3692285a72c6a99d6ad 7695 admin optional 
sysdig_0.24.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEE/KMou47jbePTdP3DdSrlQ01xncEFAly1OmJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD
QTMyOEJCOEVFMzZERTNEMzc0RkRDMzc1MkFFNTQzNEQ3MTlEQzEWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRB1KuVDTXGdwcsDD/9Sej7o/X7MVdftgIAdk7MOOo4J
Gj+c8PTXyXieZ8UeQHo2x/X2KtYYABYGL9rMQ+CZMKtSHW8sUTbNn3500Tdwzf7e
wUidooD2ecphKZwT0StTDgzRyOxc9DCVHimcgd//K+S3Ye+Fs1YY6dzE9WarOyMb
D4At+HpVv7/18En2C3BV4KDU2ATjskkpzQs8p2ZCncv2P+W99ktmHYLNXSwf+6d1
RBvZYDb7DDqu8bBruVlp6P4Ei4BvXiYSlfGBtoLZnTM+5E6eAxjm9yUUaQzVC6O5
PpnRS1efsKdfG4W6vaILB1XQ25OzI8V4XhbrGrXL3ql8tWdw7lrYs2hb62l1G0zb
QgpJhG3Al4YSLerfkEesBRJEPBastBtVmdaeC6AmvjkY1ei6GLbo7EBa5ygyhgvA
0wtbWenLnwTGj96wQ6V+NrtM5VHmM4WLED/e1O3lkfYhSv0HjjvqMAhbulr9JjmT
BIG0rVF69wW+uceg8Bjq2A41WszlOjUS0DBzJYjbqJ5lhDSF/sj2mkQWu3f0Cu1o
TpM8qG6fpfhzAYYeDw0Zn9fXTbmm0UIbflonvlqjKjpU8A86ek3UStWHXww4T8BA
zqQcZQZRocycmZqEYe6idMhuP+2mi3D/KKc8rHNlPrs+kwHQmgyWutX40C30Bs5O
rwlJvBHv1FfnW4gxQQ==
=ZipG
-END PGP SIGNATURE End Message ---

Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

[NIIBE Yutaka]

Here is some information.

It is garbage collection + threads bug (possibly + dynamic loading).

When I reproduce the failure (by make check) on my machine, it keeps
running at gauche-c-wrapper/testsuite/cwrappertest.scm.

gauche-c-wrapper/testsuite/test.log having:
---
[...]
Testing c-wrapper (ffi) ===
testing bindings in # ... ok
test dlopen, expects #f ==> ok
test dlsym, expects #f ==> ok
test ffi_prep_cif, expects 0 ==> ok
test ffi_call, expects 3 ==> ok
test ffi_closure, expects #t ==> ok
test call callback, expects 5 ==> 
---

In this situation, here is the GDB trace:
---
Current directory is ~/debian/gauche/src/
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gosh...done.
(gdb) attach 8096
Attaching to program: /home/gniibe/debian/gauche/src/gosh, process 8096
[New LWP 8097]
[New LWP 8098]
[New LWP 8099]
warning: Could not load shared library symbols for 4 libraries, e.g. 
../src/c-ffi.so.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?[Thread debugging using 
libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fc407a35c13 in ?? ()
(gdb) info threads
  Id   Target Id   Frame 
* 1Thread 0x7fc409a14740 (LWP 8096) "gosh" 0x7fc407a35c13 in ?? ()
  2Thread 0x7fc409a13700 (LWP 8097) "gosh" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x7fc40a27db68 ) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  3Thread 0x7fc409082700 (LWP 8098) "gosh" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x7fc40a27db68 ) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
  4Thread 0x7fc4086f1700 (LWP 8099) "gosh" futex_wait_cancelable 
(private=0, expected=0, futex_word=0x7fc40a27db68 ) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
(gdb) bt
#0  0x7fc407a35c13 in ?? ()
#1  0x7fc407a308b5 in ?? ()
#2  0x5613a63c4f90 in ?? ()
#3  0x7fc40a06e29f in GC_invoke_finalizers () at finalize.c:1236
#4  0x7fc409f358c9 in Scm_VMFinalizerRun (vm=vm@entry=0x5613a55a3c00) at 
core.c:305
#5  0x7fc409f38313 in process_queued_requests (vm=0x5613a55a3c00) at 
vm.c:2691
#6  0x7fc409f45d35 in run_loop () at vm.c:909
#7  0x7fc409f4d1dc in user_eval_inner (program=, 
codevec=codevec@entry=0x7ffe3b75b510) at vm.c:1489
#8  0x7fc409f4ee4f in apply_rec (vm=, vm=, 
nargs=2, proc=0x5613a56c6580) at vm.c:1582
#9  Scm_ApplyRec2 (proc=0x5613a56c6580, arg0=arg0@entry=0x5613a63d5cb0, 
arg1=arg1@entry=0x5613a6323f50) at vm.c:1622
#10 0x7fc409f4f412 in Scm_Compile (program=program@entry=0x5613a63d5cb0, 
env=env@entry=0x5613a6323f50) at compaux.c:65
#11 0x7fc409f389f3 in Scm_VMEval (expr=0x5613a63d5cb0, e=0x5613a6323f50) at 
vm.c:1388
#12 0x7fc409ff9010 in libevaleval (SCM_FP=, 
SCM_ARGCNT=, data_=) at libeval.scm:5149
#13 0x7fc409f421cc in run_loop () at ./vmcall.c:193
#14 0x7fc409f4d1dc in user_eval_inner (program=, 
codevec=codevec@entry=0x7ffe3b75b890) at vm.c:1489
#15 0x7fc409f4edc3 in apply_rec (vm=, vm=, 
nargs=1, proc=0x5613a5ca7100) at vm.c:1582
#16 Scm_ApplyRec1 (proc=0x5613a5ca7100, arg0=0x5613a5c7e300) at vm.c:1614
#17 0x7fc407a338f1 in ?? ()
#18 0x0001 in ?? ()
#19 0x5613a55a3c00 in ?? ()
#20 0x7fc40a12bd08 in ccEnvMark () from /lib/libgauche-0.9.so.0
#21 0x7fc409f421cc in run_loop () at ./vmcall.c:193
#22 0x7fc409f4d1dc in user_eval_inner (program=, 
codevec=codevec@entry=0x7ffe3b75bbf0) at vm.c:1489
#23 0x7fc409f4e0e2 in apply_rec (vm=0x5613a55a3c00, vm=0x5613a55a3c00, 
nargs=, proc=0x5613a5626140) at vm.c:1582
#24 Scm_ApplyRec (proc=0x5613a5626140, args=0x20b) at vm.c:1602
#25 0x7fc409fa0794 in Scm_Load (cpath=, flags=, packet=0x7ffe3b75bd30) at load.c:223
#26 0x5613a36c46ce in execute_script (scriptfile=, 
args=0x5613a5743490) at main.c:550
#27 0x5613a36c36f4 in main (ac=, av=) at 
main.c:751
(gdb) thread 2
[Switching to thread 2 (Thread 0x7fc409a13700 (LWP 8097))]
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7fc40a27db68 
) at 

Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

[Harlan Lieberman-Berg]

reopen 905929
notfixed 905929 0.24.1-2
thanks

Unfortunately, the patch was missing an #ifdef.  Correcting with -3

Processed: Re: Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 905929
Bug #905929 {Done: Harlan Lieberman-Berg } [src:sysdig] 
sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sysdig/0.24.1-2.
> notfixed 905929 0.24.1-2
Bug #905929 [src:sysdig] sysdig FTBFS on arm64/mips*/alpha/riscv64: 
syscall_table.c fails to compile
The source 'sysdig' and version '0.24.1-2' do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #905929 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
905929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#905929: marked as done (sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to compile)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2019 01:33:31 +
with message-id 
and subject line Bug#905929: fixed in sysdig 0.24.1-2
has caused the Debian Bug report #905929,
regarding sysdig FTBFS on arm64/mips*/alpha/riscv64: syscall_table.c fails to 
compile
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysdig
Version: 0.22.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=sysdig

...
cd /<>/obj-aarch64-linux-gnu/userspace/libscap && /usr/bin/cc 
-DHAS_CAPTURE -DK8S_DISABLE_THREAD -DPLATFORM_NAME=\"Linux\" 
-I/<>/common  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -ggdb   -o 
CMakeFiles/scap.dir/__/__/driver/fillers_table.c.o   -c 
/<>/driver/fillers_table.c
/<>/driver/syscall_table.c:54:3: error: '__NR_open' undeclared 
here (not in a function); did you mean 'f_sys_open_x'?
  [__NR_open - SYSCALL_TABLE_ID0] =   {UF_USED | 
UF_NEVER_DROP, PPME_SYSCALL_OPEN_E, PPME_SYSCALL_OPEN_X},
   ^
--- End Message ---
--- Begin Message ---
Source: sysdig
Source-Version: 0.24.1-2

We believe that the bug you reported is fixed in the latest version of
sysdig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated sysdig 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Apr 2019 16:56:12 -0400
Source: sysdig
Architecture: source
Version: 0.24.1-2
Distribution: unstable
Urgency: high
Maintainer: Evgeni Golov 
Changed-By: Harlan Lieberman-Berg 
Closes: 905929
Changes:
 sysdig (0.24.1-2) unstable; urgency=high
 .
   * Integrate patch to fix RISC-V and arm64 FTBFS. (Closes: #905929)
Checksums-Sha1:
 965a5d9b1100191f7057d684d7d5edf1adb4d0a4 2368 sysdig_0.24.1-2.dsc
 070dc3b8b5162233722afe4590334f2686613f6e 10152 sysdig_0.24.1-2.debian.tar.xz
 f5a85bda4425841a06c558701f3d3822a9e8b228 7695 sysdig_0.24.1-2_amd64.buildinfo
Checksums-Sha256:
 1c215b1d6bfad3bec7c053152b08f99b7cb85e3e7329151c0cee9635a41c9b33 2368 
sysdig_0.24.1-2.dsc
 ecf4a78b7a654d96ff701fdaa150f43cd66d3c76b1810f3f3d7edcf07a1672f1 10152 
sysdig_0.24.1-2.debian.tar.xz
 662b636f67f9a28ce39a823ce52c5c159fa1aeec49d70ed0e6e1050f7ef3a55e 7695 
sysdig_0.24.1-2_amd64.buildinfo
Files:
 58fecf08f5b4c8daf34c80ffb4fbf91d 2368 admin optional sysdig_0.24.1-2.dsc
 8aa1e6df16b899fff2f6b9dc4b6f2aee 10152 admin optional 
sysdig_0.24.1-2.debian.tar.xz
 038340e5332d71ed2ca0d7b2eead4a43 7695 admin optional 
sysdig_0.24.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEE/KMou47jbePTdP3DdSrlQ01xncEFAly1LYNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD
QTMyOEJCOEVFMzZERTNEMzc0RkRDMzc1MkFFNTQzNEQ3MTlEQzEWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRB1KuVDTXGdwccqD/9FhrzoHCe0Mn+XF2oFneV2fQsY
aU1Z2UF1H8gXgD0KuvDk9e0izj6+VNxR77kD1ehF1QS+B+bmdaiL2s3hx52VUrsM
UiYsrIHRqcbrnzix2zavIJ/fqusswEOUpf2TJAs+Z2tFHncpFZ5StTd2RtluFvfK
DkE187EAF63oNnwFR6imAznUg6XLBlzzhMjU07sD96Unu7fhF+HbKDAzA2BEnpZj
FLYUbM+NzwVf//5zN6unNXP1Tb5BUFN+UYYhqlo4qbawpauUE/Y6Vgk3C6rja5wl
vHTlYyPvauXpWj3xtKHMPHOpvU2PwgLcox/cuk3c53KorGh/4LQ1AhBZYRWSWI5I
7amC+w4IGqaPtRu4pPJLHjkU76ptu3aErsklfIWaVacnCwjq6681E4gwylH6BKQw
XzDdeFljBTytyIF9gWjAEfNJCPts7M9o+AFGtwGcuE1EJxfu2tWDuY4zucunE7da
5+PaPAqAwvCStSFlBJV7lYqcpvwYqUeHtopkpBicRllyvtQI+tK2jbOFXZDnD2MT
DTbCxxeGZ+NIlZM243gKb58qdPzY1uDvcykKmgLXzFvzoK1fej/RO6MDDZvthZtK
HDIQkxVU/LVXiH8l6Xqh9GNaP88uIxxmVnliIPM8uPKanO1h4mU/xj2cTKnxyreY
sv3RXNT/aygGDXaa9A==
=bie4
-END PGP SIGNATURE End Message ---

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Sven Hartge]

Um 01:35 Uhr am 16.04.19 schrieb Vincent Lefevre:
> On 2019-04-15 23:07:02 +0200, Sven Hartge wrote:

>> Could you add "set -x" to the top of
>> /usr/share/initramfs-tools/hooks/plymouth to get a clear picture where
>> exactly the hook fails?
 
> It is also fc-cache that is failing:

> + mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
> + cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts
> + cp -rL /etc/fonts/conf.d/60-latin.conf 
> /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
> + mkdir -p /var/tmp/mkinitramfs_0BRFs9/var/cache/fontconfig
> + mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/local/share/fonts
> + [ -e /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf ]
> + mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
> + cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
> /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
> + cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf 
> /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
> + fc-cache -s -y /var/tmp/mkinitramfs_0BRFs9
> E: /usr/share/initramfs-tools/hooks/plymouth failed with return 134.
> 
> 134 corresponds to SIGABRT, which is not a normal termination
> (even in case of error). Thus I would assume that it is a bug
> in fc-cache.

Try running the following commands as root:

mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts
cp -rL /etc/fonts/conf.d/60-latin.conf 
/var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
mkdir -p /var/tmp/mkinitramfs_0BRFs9/var/cache/fontconfig
mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/local/share/fonts
mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
/var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf 
/var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
fc-cache -v -s -y /var/tmp/mkinitramfs_0BRFs9

It uses the same commands from the bash trace, but added "-v" to the
fc-cache call, to exactly see what it is choking on. This got me to
/usr/X11R6/lib/X11 in my case (which just shows how old the installation
on my workstation is).

If this is inconclusive, add "strace -f" to the fc-cache call, maybe even
gdb, if you know how to use it.

Sidenote here: something is very brittle about fc-cache. I had to debug
and fix more fc-cache and fontconfig issues in the last years using Debian
Sid than I had other issues.

Grüße,
Sven.

Processed: limit source to corekeeper, tagging 924398, tagging 924397

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source corekeeper
Limiting to bugs with field 'source' containing at least one of 'corekeeper'
Limit currently set to 'source':'corekeeper'

> tags 924398 + pending
Bug #924398 [corekeeper] corekeeper can be confused with whitespace in 
exectuable names
Added tag(s) pending.
> tags 924397 + pending
Bug #924397 [corekeeper] corekeeper: insecure use of world-writable /var/crash
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924397
924398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Vincent Lefevre]

On 2019-04-15 23:07:02 +0200, Sven Hartge wrote:
> In my case the reason was fc-cache was failing because of a very very
> old directory /usr/X11R6/lib/X11 containing old left over fonts.

I don't have such a directory. /usr/X11R6 doesn't even exist.
But...

> Could you add "set -x" to the top of
> /usr/share/initramfs-tools/hooks/plymouth to get a clear picture where
> exactly the hook fails?

It is also fc-cache that is failing:

[...]
+ ln -rs /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 
/var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0
+ target=/usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1
+ [ -e /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 ]
+ mkdir -p /var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu
+ [ n = y ]
+ cp -pP /usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1 
/var/tmp/mkinitramfs_0BRFs9//usr/lib/x86_64-linux-gnu/libbsd.so.0.9.1
+ cp -a /usr/share/plymouth/themes/details 
/var/tmp/mkinitramfs_0BRFs9//usr/share/plymouth/themes
+ cp -a /usr/share/plymouth/themes/text 
/var/tmp/mkinitramfs_0BRFs9//usr/share/plymouth/themes
+ [ -f /etc/os-release ]
+ cp /etc/os-release /var/tmp/mkinitramfs_0BRFs9/etc
+ cp /usr/share/plymouth/debian-logo.png 
/var/tmp/mkinitramfs_0BRFs9/usr/share/plymouth
+ mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
+ cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts
+ cp -rL /etc/fonts/conf.d/60-latin.conf 
/var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
+ mkdir -p /var/tmp/mkinitramfs_0BRFs9/var/cache/fontconfig
+ mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/local/share/fonts
+ [ -e /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf ]
+ mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
+ cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
/var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
+ cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf 
/var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
+ fc-cache -s -y /var/tmp/mkinitramfs_0BRFs9
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 134.

134 corresponds to SIGABRT, which is not a normal termination
(even in case of error). Thus I would assume that it is a bug
in fc-cache.

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

Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

[NIIBE Yutaka]

Hello,

Santiago Vila  wrote:
> but the failure rate is extremely high (around 70% here).

Thanks for the number.  When I built, I didn't get failure in such a
rate.  I built it in my machine (a few times), and upload it to Debian,
where it automatically built on several machines, you know.

So far, I have no clue fixing this bug (I have been not able to identify
the cause).

> If the package is useful despite of this, I recommend disabling the
> test suite completely, as in the patch below (there will be plenty
> of time after the release of buster to fix the buggy test suite).

I believe it is useful, that is a reason why I maintain it.

In my opinion, your patch is hiding a problem.  I'm afraid it is against
our social contract #3 (We will not hide problems).  With it, there will
be no information if it build well or not.

I think that a (possibly right) procedure is to downgrade severity, in
this situation.

For me, it's difficult to accept a patch to hide a problem.  If you
claim that it is so severe that it (randomly) FTBFS on your machine
(despite it was successfully built on several Debian machines), that's
unfortunate for potential users of this package.
-- 

Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!

[Hilmar Preuße]

On 15.04.19 21:22, Adam Conrad wrote:
> On Sat, Apr 13, 2019 at 11:34:59PM +0200, Hilmar Preuße wrote:

Hi Adam,

>> The official caffe package builds fine, see [1]. Therefore I suspect
>> that you use a different source package. Please provide the source
>> package anywhere so we can reproduce/investigate the issue.
> 
> I'm not sure what makes you think the official caffe package builds,
> as the docs (arch:all) haven't built in over 130 days.
> 
> I assure you, the testing I did was on sid, with the sid package.
> 
OK, you're right: the package shows an FTBFS, when building the
documentation. For reproduction you may download it from [1] and try to
compile refman. Still I'm convinced that we look at a new issue. So
please close the old bug and open a new one!! Thanks.

Regarding the comment from Jochen: the documentation builds fine when
using the current tabu.sty from github.

@Norbert: can we risk it to upload that new tabu.sty to unstable?

Hilmar

[1] https://freeshell.de/~hille42/latex.tar.xz
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

[Sam Hartman]

Guido let me know if  you need any help or prod me on IRC if I'm needed.
Will certainly test the result, but if you get stuck would be happy to
spend time on this.

Processed: severity of 914517 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 914517 important
Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset 
is set
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

[Magnus Holmgren]

måndag 15 april 2019 kl. 19:46:14 CEST skrev  Andreas Metzler:
> Hello,
> 
> Afaiu basically exim has got a new feature and in that case (CHUNKING)
> the spoolfile looks a little bit differently and sa-exim fails to handle
> this special case properly.

So it has BDAT lines in it?

> Even in version 4.14 exim's documentation said
> 
> | The file is open for reading and writing, but updating it is not
> | recommended
> 
> which I'd read as "you may keep both pieces if it breaks". :-(

Well, now that I look closer (it's been too long since I did that) I realise 
that of couse the headers are available and manipulated through the 
header_line structs in memory and that it's only the body that's read from and 
written to the fd, so there should be no problems if SARewriteBody is set to 0 
in sa-exim.conf (which is the default).

> I have not tested it but I suspect it might break even more when
> spool_wireformat is set.

Isn't it the case that if CHUNKING has been offered AND spool_wireformat is 
set, then the body files are in an alternate format? read_message_bdat_smtp() 
looks like it is like the good old read_message_data_smtp() but for CHUNKING. 
And the documentation for spool_wireformat says "If this option is set, Exim 
may for some messages use an alternative format for data-files in the spool 
which matches the wire format. Doing this permits more efficient message 
reception and transmission. Currently it is only done for messages received 
using the ESMTP CHUNKING option."

So it seems that everything should work unless spool_wireformat=true *and* 
SARewriteBody: 1. How do I detect in sa-exim whether wire format is used for a 
given body file though?

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer 

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

Bug#865967: backport to stretch

[Daniel Kahn Gillmor]

On Fri 2019-04-12 09:41:11 -0400, Jamie McClelland wrote:
> Is it possible to back port this fix to debian stretch, stretch backports?

I've uploaded trac-tags 0.9-3~bpo9+1 to stretch-backports just now.  I
think it has to go through the backports NEW queue before it's easily
available.

I've also pushed the debian/stretch-backports branch to the salsa repo
at https://salsa.debian.org/python-team/applications/trac-tags.git in
case you want to build it yourself on a stretch system.  The backport
was very straightforward.

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Sven Hartge]

On Mon, 15 Apr 2019 18:10:18 +0200 Vincent Lefevre 
wrote:

> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Setting up initramfs-tools (0.133) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.133) ...
> update-initramfs: Generating /boot/initrd.img-4.19.0-4-amd64
> E: /usr/share/initramfs-tools/hooks/plymouth failed with return 134.
> update-initramfs: failed for /boot/initrd.img-4.19.0-4-amd64 with 134.
> dpkg: error processing package initramfs-tools (--configure):
>  installed initramfs-tools package post-installation script subprocess 
> returned error exit status 134
> Errors were encountered while processing:
>  initramfs-tools

I see the same here.

In my case the reason was fc-cache was failing because of a very very
old directory /usr/X11R6/lib/X11 containing old left over fonts.

After removal of /usr/X11R6/lib/X11 the installation of plymouth and
update-initramfs started to work again.

I've archived the directory in case someone wants to play with it and
its contents.

Could you add "set -x" to the top of
/usr/share/initramfs-tools/hooks/plymouth to get a clear picture where
exactly the hook fails?

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#927029: marked as done (graphicsmagick: Multiple heap-based buffer over-reads)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 20:42:15 +
with message-id 
and subject line Bug#927029: fixed in graphicsmagick 1.4~hg15968-1
has caused the Debian Bug report #927029,
regarding graphicsmagick: Multiple heap-based buffer over-reads
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: graphicsmagick
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for graphicsmagick.

CVE-2019-11005[0]:
| In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a stack-based
| buffer overflow in the function SVGStartElement of coders/svg.c, which
| allows remote attackers to cause a denial of service (application
| crash) or possibly have unspecified other impact via a quoted font
| family value.


CVE-2019-11006[1]:
| In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based
| buffer over-read in the function ReadMIFFImage of coders/miff.c, which
| allows attackers to cause a denial of service or information
| disclosure via an RLE packet.


CVE-2019-11007[2]:
| In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based
| buffer over-read in the ReadMNGImage function of coders/png.c, which
| allows attackers to cause a denial of service or information
| disclosure via an image colormap.


CVE-2019-11008[3]:
| In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based
| buffer overflow in the function WriteXWDImage of coders/xwd.c, which
| allows remote attackers to cause a denial of service (application
| crash) or possibly have unspecified other impact via a crafted image
| file.


CVE-2019-11009[4]:
| In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based
| buffer over-read in the function ReadXWDImage of coders/xwd.c, which
| allows attackers to cause a denial of service or information
| disclosure via a crafted image file.


CVE-2019-11010[5]:
| In GraphicsMagick 1.4 snapshot-20190322 Q8, there is a memory leak in
| the function ReadMPCImage of coders/mpc.c, which allows attackers to
| cause a denial of service via a crafted image file.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-11005
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11005
[1] https://security-tracker.debian.org/tracker/CVE-2019-11006
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11006
[2] https://security-tracker.debian.org/tracker/CVE-2019-11007
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11007
[3] https://security-tracker.debian.org/tracker/CVE-2019-11008
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11008
[4] https://security-tracker.debian.org/tracker/CVE-2019-11009
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11009
[5] https://security-tracker.debian.org/tracker/CVE-2019-11010
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11010

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: graphicsmagick
Source-Version: 1.4~hg15968-1

We believe that the bug you reported is fixed in the latest version of
graphicsmagick, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated graphicsmagick 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2019 17:40:12 +
Source: graphicsmagick
Architecture: source
Version: 1.4~hg15968-1
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 927029
Changes:
 graphicsmagick (1.4~hg15968-1) unstable; urgency=high
 .
   * Mercurial snapshot, fixing the following security issues
 (closes: #927029):
 - ReadMATImage(): 

Bug#924847: marked as done (i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:378: error: method write in interface Writer cannot be applied to given types;

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 20:43:11 +
with message-id 
and subject line Bug#924847: fixed in i2p 0.9.38-3.1
has caused the Debian Bug report #924847,
regarding i2p: FTBFS: [javac] 
/<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:378: 
error: method write in interface Writer cannot be applied to given types;
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
924847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: i2p
Version: 0.9.38-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_shlibdeps -llibjbigi-jni debian/libjbigi-jni/usr/lib/jni/*.so
> make[1]: Leaving directory '/<>'
>dh_installdeb -a
>dh_gencontrol -a
>dh_md5sums -a
>dh_builddeb -a
> dpkg-deb: building package 'libjbigi-jni-dbgsym' in 
> '../libjbigi-jni-dbgsym_0.9.38-3_amd64.deb'.
> dpkg-deb: building package 'libjbigi-jni' in 
> '../libjbigi-jni_0.9.38-3_amd64.deb'.
> dh_prep
> mkdir -p /<>/installer/lib/wrapper/all
> ln -sf /usr/share/java/wrapper.jar 
> /<>/installer/lib/wrapper/all/wrapper.jar
> if [ ! -e /<>/debian/routerversion.java.bak ]; then \
>   cp /<>/router/java/src/net/i2p/router/RouterVersion.java 
> /<>/debian/routerversion.java.bak; \
> fi
> sed -e "s/\(.*EXTRA\ =\ \)[^ ]*\"\(.*\)\"/\1\"-$EXTRAPREFIX$DEBIANVERSION\"/" 
> < /<>/router/java/src/net/i2p/router/RouterVersion.java > 
> /<>/router/java/src/net/i2p/router/RouterVersion.java.tmp
> mv -f /<>/router/java/src/net/i2p/router/RouterVersion.java.tmp 
> /<>/router/java/src/net/i2p/router/RouterVersion.java
> mkdir -p /<>/apps/jetty/jettylib
> ln -sf /usr/share/java/jetty9-continuation.jar 
> /<>/apps/jetty/jettylib/jetty-continuation.jar
> ln -sf /usr/share/java/jetty9-deploy.jar 
> /<>/apps/jetty/jettylib/jetty-deploy.jar
> ln -sf /usr/share/java/jetty9-http.jar 
> /<>/apps/jetty/jettylib/jetty-http.jar
> ln -sf /usr/share/java/jetty9-io.jar 
> /<>/apps/jetty/jettylib/jetty-io.jar
> ln -sf /usr/share/java/jetty9-rewrite.jar 
> /<>/apps/jetty/jettylib/jetty-rewrite-handler.jar
> ln -sf /usr/share/java/jetty9-security.jar 
> /<>/apps/jetty/jettylib/jetty-security.jar
> ln -sf /usr/share/java/jetty9-servlet.jar 
> /<>/apps/jetty/jettylib/jetty-servlet.jar
> ln -sf /usr/share/java/jetty9-servlets.jar 
> /<>/apps/jetty/jettylib/jetty-servlets.jar
> ln -sf /usr/share/java/jetty9-start.jar 
> /<>/apps/jetty/jettylib/jetty-start.jar
> ln -sf /usr/share/java/jetty9-util.jar 
> /<>/apps/jetty/jettylib/jetty-util.jar
> ln -sf /usr/share/java/jetty9-webapp.jar 
> /<>/apps/jetty/jettylib/jetty-webapp.jar
> ln -sf /usr/share/java/jetty9-xml.jar 
> /<>/apps/jetty/jettylib/jetty-xml.jar
> ln -sf /usr/share/java/jetty9-server.jar 
> /<>/apps/jetty/jettylib/org.mortbay.jetty.jar
> ln -sf /usr/share/java/jetty9-jmx.jar 
> /<>/apps/jetty/jettylib/org.mortbay.jmx.jar
> ln -sf /usr/share/java/servlet-api-3.1.jar 
> /<>/apps/jetty/jettylib/javax.servlet.jar
> ln -sf /usr/share/java/jsp-api-2.3.jar 
> /<>/apps/jetty/jettylib/jsp-api.jar
> mkdir -p /<>/apps/jetty/jettylib
> ln -sf /usr/share/java/tomcat9-api.jar 
> /<>/apps/jetty/jettylib/tomcat-api.jar
> ln -sf /usr/share/java/tomcat9-coyote.jar 
> /<>/apps/jetty/jettylib/tomcat-coyote.jar
> ln -sf /usr/share/java/tomcat9-el-api.jar 
> /<>/apps/jetty/jettylib/commons-el.jar
> ln -sf /usr/share/java/tomcat9-jasper.jar 
> /<>/apps/jetty/jettylib/jasper-runtime.jar
> ln -sf /usr/share/java/tomcat9-jasper-el.jar 
> /<>/apps/jetty/jettylib/jasper-el.jar
> ln -sf /usr/share/java/tomcat9-juli.jar 
> /<>/apps/jetty/jettylib/commons-logging.jar
> ln -sf /usr/share/java/tomcat9-util.jar 
> /<>/apps/jetty/jettylib/tomcat-util.jar
> ln -sf /usr/share/java/tomcat9-util-scan.jar 
> /<>/apps/jetty/jettylib/tomcat-util-scan.jar
> ln -sf /usr/share/java/taglibs-standard-spec.jar 
> /<>/apps/susidns/src/lib/jstl.jar
> ln -sf /usr/share/java/taglibs-standard-impl.jar 
> /<>/apps/susidns/src/lib/standard.jar
> ln -sf /usr/share/java/taglibs-standard-jstlel.jar 
> /<>/apps/susidns/src/lib/jstlel.jar
> ln -sf /usr/share/java/libintl.jar 
> /<>/core/java/build/libintl.jar
> ln -sf /usr/share/java/gnu-getopt.jar 
> /<>/core/java/build/gnu-getopt.jar
> ln -sf /usr/share/java/json-simple.jar 
> /<>/core/java/build/json-simple.jar
> TZ=UTC 

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

[Guido Günther]

Hi,
On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote:
> Hi Sam
> 
> Am 15.04.2019 um 20:38 schrieb Sam Hartman:
> > control: severity -1 serious
> > 
> > justification: libvirtd upgrades from stretch to buster break causing
> > apt to fail and requiring the admin to get the systemd units into a
> > consistent state before things can continue
> > 
> > 
> > Unfortunately based on discussion so far this is a complex bug to fix.
> > Ubuntu's solution is to drop the sysv scripts and to drop  Also= lines
> > in some of the units.
> > 
> > The systemd maintainers proposed that dropping Also as well as some
> > changes to move toward dh_systemd_start being used even when sysvinit
> > scripts are present would help this situation.  Unfortunately it at
> > least doesn't look like those changes are in debhelper for buster.
> > Systemd folks, do you have any suggestions  on how to approach this for
> > buster?
> 
> Using debhelper compat level 12, you are able to completely decouple
> dh_installinit and dh_installsystemd which would give you the ability to
> implement what you want afaics.

So let's move libvirt from 8 to 12 for stretch? I'm all for it but it'll
be a couple of days until I can set time aside for this.
cheers,
 -- Guido

> 
> Regards,
> Michael
> 
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 




> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#905772: libvirtd upgrade broken stretch->buster

[Michael Biebl]

Am 15.04.19 um 22:18 schrieb Michael Biebl:
> Using debhelper compat level 12, you are able to completely decouple
> dh_installinit and dh_installsystemd which would give you the ability to
> implement what you want afaics.

From debhelper's changelog:


debhelper (12.1) unstable; urgency=medium
[..]
  * dh_installinit: In compat 12, pass --skip-systemd-native to update-rc.d
to make it ignore systemd services.
  * dh_installsystemd: In compat 12, avoid relying on dh_installinit's
shell snippets for starting services.  (Closes: #887904, #887900)


And init-system-helpers:

init-system-helpers (1.52) unstable; urgency=medium
[..]
  * invoke-rc.d: add option to do nothing for native systemd units.
It is useful to simplify maintainer scripts, since it allows executing
this command for sysvinit/openrc
systems, and deb-systemd-invoke for systemd systems



Versions of debhelper and init-system-helpers implementing those bits
are available in buster and stretch-backports.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#927171: boogie: build-dependencies not satisfiable in sid

[Ralf Treinen]

Source: boogie
Version: 2.3.0.61016+dfsg+3.gbp1f2d6c1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

the build-dependencies of boogie are not satisfiable on any architecture
in sid. This is the case since at least 2019-01-12.

On amd64, arm64, armel, armhf, i386, mipsel, ppc64el, s390x, the reason
is that it build-depends both on mono-devel (>= 2.4.2.3) and 
mono-reference-assemblies-4.0. However, mono-devel (5.18.0.240+dfsg-2) 
declares a Breaks with mono-reference-assemblies-4.0 (<< 5.0~).

-Ralf.

Bug#905772: libvirtd upgrade broken stretch->buster

[Michael Biebl]

Hi Sam

Am 15.04.2019 um 20:38 schrieb Sam Hartman:
> control: severity -1 serious
> 
> justification: libvirtd upgrades from stretch to buster break causing
> apt to fail and requiring the admin to get the systemd units into a
> consistent state before things can continue
> 
> 
> Unfortunately based on discussion so far this is a complex bug to fix.
> Ubuntu's solution is to drop the sysv scripts and to drop  Also= lines
> in some of the units.
> 
> The systemd maintainers proposed that dropping Also as well as some
> changes to move toward dh_systemd_start being used even when sysvinit
> scripts are present would help this situation.  Unfortunately it at
> least doesn't look like those changes are in debhelper for buster.
> Systemd folks, do you have any suggestions  on how to approach this for
> buster?

Using debhelper compat level 12, you are able to completely decouple
dh_installinit and dh_installsystemd which would give you the ability to
implement what you want afaics.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#916375: [debian-mysql] Bug#916375: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

[Otto Kekäläinen]

For the record some debug output:

### Stretch before upgrade

# dpkg -S /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy*
libmagic1:amd64: /usr/lib/x86_64-linux-gnu/libmagic.so.1
libmagic1:amd64: /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0
libmailutils5:amd64: /usr/lib/x86_64-linux-gnu/libmailutils.so.5
libmailutils5:amd64: /usr/lib/x86_64-linux-gnu/libmailutils.so.5.0.1
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient.a
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient.so
libmariadbclient18:amd64: /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
libmariadbclient18:amd64: /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18.0.0
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient_r.a
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient_r.so
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient_r.so.18
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient_r.so.18.0.0
libmariadbclient-dev-compat:amd64: /usr/lib/x86_64-linux-gnu/libmysqlclient.so
libmariadbclient-dev-compat:amd64: /usr/lib/x86_64-linux-gnu/libmysqlclient_r.so
libmariadbd-dev:amd64: /usr/lib/x86_64-linux-gnu/libmysqld.a
libmariadbd-dev:amd64: /usr/lib/x86_64-linux-gnu/libmysqld.so
libmariadbd18:amd64: /usr/lib/x86_64-linux-gnu/libmysqld.so.18
libmariadbclient-dev: /usr/lib/x86_64-linux-gnu/libmysqlservices.a

# find /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy* -ls
11878  4 lrwxrwxrwx   1 root root   17 Jun 11
2018 /usr/lib/x86_64-linux-gnu/libmagic.so.1 -> libmagic.so.1.0.0
11869136 -rw-r--r--   1 root root   137448 Jun 11
2018 /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0
43036  4 lrwxrwxrwx   1 root root   21 Dec 25
2016 /usr/lib/x86_64-linux-gnu/libmailutils.so.5 ->
libmailutils.so.5.0.1
43004820 -rw-r--r--   1 root root   836960 Dec 25
2016 /usr/lib/x86_64-linux-gnu/libmailutils.so.5.0.1
14428   5440 -rw-r--r--   1 root root  5570262 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient.a
14439  4 lrwxrwxrwx   1 root root   22 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient.so ->
libmariadbclient.so.18
14078  4 lrwxrwxrwx   1 root root   26 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18 ->
libmariadbclient.so.18.0.0
14071   4068 -rw-r--r--   1 root root  4163048 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18.0.0
14440  4 lrwxrwxrwx   1 root root   18 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient_r.a ->
libmariadbclient.a
14441  4 lrwxrwxrwx   1 root root   19 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient_r.so ->
libmariadbclient.so
14442  4 lrwxrwxrwx   1 root root   19 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient_r.so.18 ->
libmariadbclient.so
14443  4 lrwxrwxrwx   1 root root   19 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmariadbclient_r.so.18.0.0 ->
libmariadbclient.so
14454  4 lrwxrwxrwx   1 root root   19 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmysqlclient.so ->
libmariadbclient.so
14455  4 lrwxrwxrwx   1 root root   21 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmysqlclient_r.so ->
libmariadbclient_r.so
14478  28864 -rw-r--r--   1 root root 29554908 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmysqld.a
14482  4 lrwxrwxrwx   1 root root   15 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmysqld.so -> libmysqld.so.18
14466  16208 -rw-r--r--   1 root root 16593304 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmysqld.so.18
14429 20 -rw-r--r--   1 root root19430 Aug 10
2017 /usr/lib/x86_64-linux-gnu/libmysqlservices.a

# nm -D /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18.0.0 | egrep
'lib(mariadb|mysql)client_'
 A libmariadbclient_16
 A libmariadbclient_18

# ldconfig -p | grep -e mariadb -e mysql
libmysqld.so.18 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libmysqld.so.18
libmysqld.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libmysqld.so
libmariadbclient.so.18 (libc6,x86-64) =>
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
libmariadbclient.so (libc6,x86-64) =>
/usr/lib/x86_64-linux-gnu/libmariadbclient.so

# curl -IL http://localhost/otrs/index.pl?Action=Admin
HTTP/1.1 200 OK
Date: Mon, 15 Apr 2019 19:02:38 GMT
Server: Apache/2.4.25 (Debian)
X-Powered-By: OTRS 5.0.16 (https://www.otrs.com/)
X-UA-Compatible: IE=edge,chrome=1
X-Frame-Options: SAMEORIGIN
Expires: Tue, 1 Jan 1980 12:00:00 GMT
Cache-Control: no-cache
Pragma: no-cache
X-OTRS-Login: /otrs/index.pl?
Set-Cookie: OTRSBrowserHasCookie=1; path=/otrs/; expires=1y
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8;


### Stretch after upgrade

Everything else is identical apart from:
# nm -D /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18.0.0 | egrep

Bug#927169: python-googlecloudapis: unsatisfiable build-dependencies in sid

[Ralf Treinen]

Source: python-googlecloudapis
Version: 0.9.30+debian1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

the build-dependencies of python-googlecloudapis are not installable in
sid on a any architecture. This is the case since at least 2018-08-08:

- It build-depends on python-protorpc-standalone
- It build-depends on python3-all, which depends on python3.7

However, python3.7 version 3.7.3-2 declares a Breaks with
python3-protorpc-standalone (<= 0.9.1-3).

-Ralf.
- 

Processed: [bts-link] source package texlive-extra

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package texlive-extra
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #920459 (http://bugs.debian.org/920459)
> # Bug title: tabu: breaks with color and/or xcolor when spread or negative X 
> coefficients are used
> #  * https://github.com/tabu-fixed/tabu/pull/14
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 920459 + fixed-upstream
Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming 
doxygen 1.8.15
Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when 
xcolor is used
Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921776 [texlive-latex-extra] bliss: FTBFS (LaTeX error)
Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output 
PDF file produced!
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 920459 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #920621 (http://bugs.debian.org/920621)
> # Bug title: texlive-base: breaks build of forthcoming doxygen 1.8.15
> #  * https://github.com/tabu-fixed/tabu/pull/14
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 920621 + fixed-upstream
Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming 
doxygen 1.8.15
Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when 
xcolor is used
Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921776 [texlive-latex-extra] bliss: FTBFS (LaTeX error)
Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when 
spread or negative X coefficients are used
Bug #924829 [texlive-latex-extra] caffe: FTBFS: Fatal error occurred, no output 
PDF file produced!
Ignoring request to alter tags of bug #920621 to the same tags previously set
Ignoring request to alter tags of bug #920459 to the same tags previously set
Ignoring request to alter tags of bug #921272 to the same tags previously set
Ignoring request to alter tags of bug #921299 to the same tags previously set
Ignoring request to alter tags of bug #921776 to the same tags previously set
Ignoring request to alter tags of bug #921779 to the same tags previously set
Ignoring request to alter tags of bug #921783 to the same tags previously set
Ignoring request to alter tags of bug #921789 to the same tags previously set
Ignoring request to alter tags of bug #921802 to the same tags previously set
Ignoring request to alter tags of bug #921838 to the same tags previously set
Ignoring request to alter tags of bug #924829 to the same tags previously set
> usertags 920621 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 920621 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #921272 (http://bugs.debian.org/921272)
> # Bug title: texlive-latex-extra: package tabu broken when xcolor is used
> #  * 

Bug#927166: libbiod0: not installable in sid

[Ralf Treinen]

Package: libbiod0
Version: 0.2.1-1
Severity: serious
User: trei...@debia.org
Usertags: edos-uninstallable

Hi,

libbiod0 is not installable on amd64 or i386 (the only architectures
for which this binary package exists) in sid, at least since
2018-10-30 : it depends on libphobos2-ldc-shared81 which does 
not exist in sid.

-Ralf.

Bug#916375: [debian-mysql] Bug#916375: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

[Otto Kekäläinen]

### Buster

# dpkg -S /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy*
libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadb.so
libmariadb3:amd64: /usr/lib/x86_64-linux-gnu/libmariadb.so.3
libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient.a
libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient.so
libmariadb-dev-compat:amd64: /usr/lib/x86_64-linux-gnu/libmysqlclient.a
libmariadb-dev-compat:amd64: /usr/lib/x86_64-linux-gnu/libmysqlclient.so
libmariadb-dev-compat:amd64: /usr/lib/x86_64-linux-gnu/libmysqlclient_r.a
libmariadb-dev-compat:amd64: /usr/lib/x86_64-linux-gnu/libmysqlclient_r.so
libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmysqlservices.a

# find /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy* -ls
11162  4 lrwxrwxrwx   1 root root   15 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmariadb.so -> libmariadb.so.3
 7973332 -rw-r--r--   1 root root   335984 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmariadb.so.3
11149460 -rw-r--r--   1 root root   467280 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmariadbclient.a
11163  4 lrwxrwxrwx   1 root root   15 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmariadbclient.so -> libmariadb.so.3
11177  4 lrwxrwxrwx   1 root root   18 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmysqlclient.a -> libmariadbclient.a
11178  4 lrwxrwxrwx   1 root root   15 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmysqlclient.so -> libmariadb.so.3
11179  4 lrwxrwxrwx   1 root root   18 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmysqlclient_r.a ->
libmariadbclient.a
11180  4 lrwxrwxrwx   1 root root   15 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmysqlclient_r.so -> libmariadb.so.3
11150 20 -rw-r--r--   1 root root19430 Apr  1
20:05 /usr/lib/x86_64-linux-gnu/libmysqlservices.a

# nm -D /usr/lib/x86_64-linux-gnu/libmariadb.so.3 | egrep 'lib(mariadb|mysql)'
 A libmariadb_3
 A libmariadbclient_18
 A libmysqlclient_18

# ldconfig -p | grep -e mariadb -e mysql
libmariadb.so.3 (libc6,x86-64) => /lib/x86_64-linux-gnu/libmariadb.so.3
libmariadb.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libmariadb.so

Bug#924829: caffe: FTBFS: Fatal error occurred, no output PDF file produced!

[Adam Conrad]

On Sat, Apr 13, 2019 at 11:34:59PM +0200, Hilmar Preuße wrote:
> 
> The official caffe package builds fine, see [1]. Therefore I suspect
> that you use a different source package. Please provide the source
> package anywhere so we can reproduce/investigate the issue.

I'm not sure what makes you think the official caffe package builds,
as the docs (arch:all) haven't built in over 130 days.

I assure you, the testing I did was on sid, with the sid package.

... Adam

Bug#927162: gnome-shell segfaults in libst-1.0.so

[Eloston]

Package: gnome-shell
Version: 3.30.2-3
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

   * What led up to the situation?

Just using GNOME normally causes the crash to happen.

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

It seems to happen randomly, more so on Wayland. I haven't been able to
pinpoint any specific application, extension, or setting.

   * What was the outcome of this action?

GNOME shell segfaults. On Wayland, this causes all the applications to
die, and I get booted back to gdm3 (i.e. data loss). On X11, I see the shell
restart only, keeping my applications intact.

   * What outcome did you expect instead?

No segfaulting.

The stack trace is attached as gnome-shell-journalctl.log
The coredump (35 MB compressed, 1.2 GB raw): https://transfer.sh/WmwCL/gnome-
shell-coredump.xz
(Hash is attached as gnome-shell-coredump.xz.sha256)

I have had this crash happen multiple times on Wayland and X11; this is the
first crash where I was able to get a coredump. Note that the stack trace is a
little different each time the crash occurs, e.g. this is the first time I've
seen TopIcons show up in the trace. Everything else looks the same.



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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER, 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 gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evolution-data-server3.30.5-1
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.30.0-7
ii  gir1.2-freedesktop   1.58.3-2
ii  gir1.2-gcr-3 3.28.1-1
ii  gir1.2-gdesktopenums-3.0 3.28.1-1
ii  gir1.2-gdm-1.0   3.30.2-3
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomebluetooth-1.03.28.2-3
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-1
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-gweather-3.0  3.28.2-2
ii  gir1.2-ibus-1.0  1.5.19-4
ii  gir1.2-mutter-3  3.30.2-6
ii  gir1.2-nm-1.01.14.6-2
ii  gir1.2-nma-1.0   1.8.20-1
ii  gir1.2-pango-1.0 1.42.4-6
ii  gir1.2-polkit-1.00.105-25
ii  gir1.2-rsvg-2.0  2.44.10-1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.10-1
ii  gjs  1.54.3-1
ii  gnome-backgrounds3.30.0-1
ii  gnome-settings-daemon3.30.2-3
ii  gnome-shell-common   3.30.2-3
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-8
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libcanberra0 0.30-7
ii  libcroco30.6.12-3
ii  libecal-1.2-19   3.30.5-1
ii  libedataserver-1.2-233.30.5-1
ii  libgcr-base-3-1  3.28.1-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgirepository-1.0-11.58.3-2
ii  libgjs0g 1.54.3-1
ii  libglib2.0-0 2.58.3-1
ii  libglib2.0-bin   2.58.3-1
ii  libgstreamer1.0-01.14.4-1
ii  libgtk-3-0   3.24.5-1
ii  libical3 3.0.4-3
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-3-03.30.2-6
ii  libnm0   1.14.6-2
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpolkit-agent-1-0  0.105-25
ii  libpolkit-gobject-1-00.105-25
ii  libpulse-mainloop-glib0  12.2-4
ii  libpulse012.2-4
ii  

Processed: libvirtd upgrade broken stretch->buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #905772 [libvirt] virtlogd dependency loop cuaing upgrade failures
Severity set to 'serious' from 'normal'

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

Bug#927159: libqb: Insecure Temporary Files

[Ferenc Wágner]

Source: libqb
Version: 1.0.3-2
Severity: grave
Tags: patch upstream security
Justification: user security hole
Forwarded: https://github.com/ClusterLabs/libqb/issues/338
Control: found -1 0.11.1-2

Libqb creates files in world-writable directories (/dev/shm, /tmp) with
rather predictable file names (for example in case of USBGuard with names
like /dev/shm/qb-usbguard-request-7096-835-12-data). Also O_EXCL flag is
not used when opening the files. This could be exploited by a local
attacker to overwrite privileged system files (if not restricted by
sandboxing, MAC or symlinking policies).

Processed: libqb: Insecure Temporary Files

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.11.1-2
Bug #927159 [src:libqb] libqb: Insecure Temporary Files
Marked as found in versions libqb/0.11.1-2.

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

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

[Andreas Metzler]

On 2019-04-14 Magnus Holmgren  wrote:
> fredag 12 april 2019 kl. 19:23:40 CEST skrev du:
>> The dlopen localscan patch in exim4 has been nonfunctional in unstable
>> for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1
>> unstable/26 Dec and buster/03 Jan). The issue only popped up end of
>> March on the upstream user support ML.

>> At this time I opened a tracking bug in exim #925982 and looked at
>> sa-exim. It is dead upstream since 2006 and buggy:
>> * https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html
>> * #879687

> I've seen reports of bugs, but I didn't realise it was that bad.
> sa-exim hasn't exactly changed; has the way local_scan() is called
> changed? It's supposed to get an fd, read a message from it, and
> possibly write an altered message back (after piping it through
> spamc). What can "Format error in spool file" mean?

Hello,

Afaiu basically exim has got a new feature and in that case (CHUNKING)
the spoolfile looks a little bit differently and sa-exim fails to handle
this special case properly.

Even in version 4.14 exim's documentation said
| The file is open for reading and writing, but updating it is not
| recommended

which I'd read as "you may keep both pieces if it breaks". :-(

I have not tested it but I suspect it might break even more when 
spool_wireformat is set.

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

Processed: tagging 927152, found 927152 in 0.7.2-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 927152 + upstream
Bug #927152 [teeworlds] teeworlds: CVE-2019-10877 CVE-2019-10878 CVE-2019-10879
Added tag(s) upstream.
> # Cf. 
> https://salsa.debian.org/security-tracker-team/security-tracker/commit/1916502afa8ad9ce98cd69e44001e9bbb24d3f3e
> found 927152 0.7.2-3
Bug #927152 [teeworlds] teeworlds: CVE-2019-10877 CVE-2019-10878 CVE-2019-10879
Marked as found in versions teeworlds/0.7.2-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927148: marked as done (python-deprecated: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 16:21:05 +
with message-id 
and subject line Bug#927148: fixed in python-deprecated 1.2.5-2
has caused the Debian Bug report #927148,
regarding python-deprecated: Incomplete debian/copyright?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-deprecated
Version: 1.2.5-1
Severity: serious
Justication: Policy § 12.5
X-Debbugs-CC: Bas Couwenberg , 
ftpmas...@debian.org

Hi,

I just ACCEPTed python-deprecated from NEW but noticed it was missing 
attribution in debian/copyright for at least Marcos Cardoso.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-deprecated
Source-Version: 1.2.5-2

We believe that the bug you reported is fixed in the latest version of
python-deprecated, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-deprecated 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Apr 2019 17:41:24 +0200
Source: python-deprecated
Binary: python3-deprecated
Architecture: source all
Version: 1.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 python3-deprecated - Python decorator for old classes, functions or methods
Closes: 927148
Changes:
 python-deprecated (1.2.5-2) unstable; urgency=medium
 .
   * Update copyright file, changes:
 - Add Marcos CARDOSO
 - Add comment for code origin
 (closes: #927148)
   * Drop unused ${python3:Depends} substvar.
Checksums-Sha1:
 0d1ef4894afba039f0cacad6105401995867898c 2112 python-deprecated_1.2.5-2.dsc
 2b806a3342176679cf07506ec577d8196f79a6cf 2904 
python-deprecated_1.2.5-2.debian.tar.xz
 1ca9569c1bf8857a299594324b45ce3a0c4e3b25 8367 
python-deprecated_1.2.5-2_amd64.buildinfo
 9134b035bd31aee7c637f47b20528d97db9006cd 10372 
python3-deprecated_1.2.5-2_all.deb
Checksums-Sha256:
 6ba026e42236941e9a0067efb173d1d0e8d79c2a1dc3f5afe1e549bacdee8dba 2112 
python-deprecated_1.2.5-2.dsc
 ac055270a1f0ef52e52ff5cae74e86027e3cba3ecb39552df11be5af15fb68f2 2904 
python-deprecated_1.2.5-2.debian.tar.xz
 e5ed344d91b5acc9a0e10f64d65ca4c3d24b7d478d620b48aaa3b6aa594bbfbd 8367 
python-deprecated_1.2.5-2_amd64.buildinfo
 6b9d6118eaa629a4acc0af5c5d7b3e864f103a2a50f9594dafa5e031708dec53 10372 
python3-deprecated_1.2.5-2_all.deb
Files:
 c6a4476b38dd41e7de76d78c3cb8f76f 2112 python optional 
python-deprecated_1.2.5-2.dsc
 54b34f78e1cd71226131f4945faa7d6c 2904 python optional 
python-deprecated_1.2.5-2.debian.tar.xz
 c19e4ac7161a04101bf075dc34641848 8367 python optional 
python-deprecated_1.2.5-2_amd64.buildinfo
 2aac030739b592777ddf72354e67d922 10372 python optional 
python3-deprecated_1.2.5-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAly0qIgACgkQZ1DxCuiN
SvFPJRAAxN2jp7GaKfvQNrfNZJPEd9L6BTeFuijvtiseAML/XijNouaJN5ezHBlR
0GC7voyfc8IBgjpIEXsIEnHf6tpd+KAnsl0IQW4AhM5lsTJqwGmVNRVOR/68RNoT
3tovvGHdkz5X8vNFvGPvchXu09DwXtuqayjakBz5mvM7pSVydUct0TMqj5nOMbug
zQkdzTMirsFfk+MxK6f965W7u9p+GRT1lAGL2AzPfWGnI/vg9mJc5f4/W2DBtpwd
mpPSqY/arm5XoO3/HJppWjHHnyY3twAsVl1HbEUDDh9/hRdMq6vFHKi5NpLClpP+
Ty11qwXKy8T2KJBVr9UAKN8p/OFqD91x47NTRDgGqHOcRboECdKyMlx2ErYEaWzm
4as7iyFDNm5XQQaz9tjnTVj8//Jwqzo9ChuXTeXCzRCkOB2NJDxgRsXHXFoNo6r9
kWHDQu8rzEnm1c5lHMbKGTtJgsSJlgLoWnX/NTcJSUya6ZTuJQUB5PDwCvChRnTG
WB7roJ9ECSn5eu+0ywPrWO6b+RHX2wDijUnOIJomxHQYjPMJxf+pycK+VDCO2vbO
EX1XTT5gCAsiCHoWldKPA3WLR5kO+E063FGecmDcfvxpMTYDpLQAv54k1f45AYRC
nyRBkDroX0H5CC7MmSehTd6/qan2qc9vO7pdd5RIGzHD0Q1lKsQ=
=u5BJ
-END PGP SIGNATURE End Message ---

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Vincent Lefevre]

Package: plymouth
Version: 0.9.4-1.1
Severity: grave
Justification: renders package unusable

I got the following error during upgrade:

[...]
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up initramfs-tools (0.133) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-4-amd64
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 134.
update-initramfs: failed for /boot/initrd.img-4.19.0-4-amd64 with 134.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 134
Errors were encountered while processing:
 initramfs-tools

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

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

Versions of packages plymouth depends on:
ii  init-system-helpers  1.56+nmu1
ih  initramfs-tools  0.133
ii  libc62.28-8
ii  libdrm2  2.4.97-1
ii  libplymouth4 0.9.4-1.1
ii  lsb-base 10.2019031300
ii  systemd  241-3
ii  udev 241-3

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base 10.0.2
pn  plymouth-themes  

-- no debconf information

Bug#927152: teeworlds: CVE-2019-10877 CVE-2019-10878 CVE-2019-10879

[Markus Koschany]

Package: teeworlds
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for teeworlds.

CVE-2019-10877[0]:
| In Teeworlds 0.7.2, there is an integer overflow in CMap::Load() in
| engine/shared/map.cpp that can lead to a buffer overflow, because
| multiplication of width and height is mishandled.


CVE-2019-10878[1]:
| In Teeworlds 0.7.2, there is a failed bounds check in
| CDataFileReader::GetData() and CDataFileReader::ReplaceData() and
| related functions in engine/shared/datafile.cpp that can lead to an
| arbitrary free and out-of-bounds pointer write, possibly resulting in
| remote code execution.


CVE-2019-10879[2]:
| In Teeworlds 0.7.2, there is an integer overflow in
| CDataFileReader::Open() in engine/shared/datafile.cpp that can lead to
| a buffer overflow and possibly remote code execution, because size-
| related multiplications are mishandled.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-10877
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10877
[1] https://security-tracker.debian.org/tracker/CVE-2019-10878
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10878
[2] https://security-tracker.debian.org/tracker/CVE-2019-10879
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10879

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#927148: python-deprecated: Incomplete debian/copyright?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #927148 [src:python-deprecated] python-deprecated: Incomplete 
debian/copyright?
Warning: Unknown package 'src:python-deprecated'
Added tag(s) pending.
Warning: Unknown package 'src:python-deprecated'

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

Bug#927148: python-deprecated: Incomplete debian/copyright?

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 4/15/19 5:27 PM, Chris Lamb wrote:
> I just ACCEPTed python-deprecated from NEW but noticed it was missing 
> attribution in debian/copyright for at least Marcos Cardoso.
> 
> This is in no way exhaustive so please check over the entire package 
> carefully and address these on your next upload.

Thanks for the review and reporting this issue.

The copyright file is fixed in -2 and a new upload to unstable will
follow shortly.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#926194: marked as done (e2wm/emacs-window-layout: unintended dist-upgrade dependency resolution due to missing "emacsen" dependency if installed together with emacs25-lucid)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 15:33:31 +
with message-id 
and subject line Bug#926194: fixed in e2wm 1.4-2
has caused the Debian Bug report #926194,
regarding e2wm/emacs-window-layout: unintended dist-upgrade dependency 
resolution due to missing "emacsen" dependency if installed together with 
emacs25-lucid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2wm
Version: 1.4-1
Severity: serious
Control: affects -1 + emacs-lucid emacs25-lucid
Control: clone -1 -2
Control: reassign -2 emacs-window-layout
Control: found -2 emacs-window-layout/1.4

Dear Maintainer,

if I upgrade a machine with emacs25-lucid and e2wm or
emacs-window-layout installed from e.g. Stretch to Buster, I can't
upgrade emacs25-lucid to emacs-lucid, because e2wm/emacs-window-layout
in Buster only depend on "emacs25-nox | emacs25", but not on any of the
generic virtual emacs packages like "emacs" or "emacsen".

Historically that worked, because emacs25-lucid did provide also
"emacs25" in Stretch, but since it's just a transitional package in
Buster, it no more provides emacs25 but depends on emacs-lucid which
itself only provides the current virtual emacs packages "emacs" and
"emacsen" (plus some other more generic things like "editor" which are
not relevant in this case).

So please change the dependencies to at least include "emacs" or even
better — because backwards compatible — "emacsen".

P.S.: IMHO this is release-critical because there is a dependency
missing which mislead both apt as well as aptitude on dist-upgrades:

* apt wants to replace emacs25-lucid (a lean GUI variant) with
  the non-gui variant emacs25-nox (which is not intended at all), and,

* depending on settings, aptitude suggests to not upgrade emacs25-lucid
  or to replace it with emacs25-nox as first suggestion, too:

  The following packages have unmet dependencies:
   emacs-lucid : Conflicts: emacs-nox but 1:26.1+1-3.2 is to be installed
   emacs-nox : Conflicts: emacs-lucid but 1:26.1+1-3.2 is to be installed
  The following actions will resolve these dependencies:

   Remove the following packages:
  1) emacs25-lucid [25.1+1-4+deb9u1 (now)]

   Keep the following packages at their current version:
  2) emacs-lucid [Not Installed]

On just "apt upgrade" or "aptitude safe-upgrade" both keep back
emacs25-lucid.

All these dependency resolution issues have no real reason except
missing (uptodate alternative) dependencies.
--- End Message ---
--- Begin Message ---
Source: e2wm
Source-Version: 1.4-2

We believe that the bug you reported is fixed in the latest version of
e2wm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
KURASHIKI Satoru  (supplier of updated e2wm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2019 23:54:41 +0900
Source: e2wm
Binary: e2wm
Architecture: source all
Version: 1.4-2
Distribution: unstable
Urgency: medium
Maintainer: KURASHIKI Satoru 
Changed-By: KURASHIKI Satoru 
Description:
 e2wm   - simple window manager for emacs
Closes: 926194
Changes:
 e2wm (1.4-2) unstable; urgency=medium
 .
   * Fix Depends: on emacs (Closes: #926194)
Checksums-Sha1:
 f7d7eb266d8c29095fb9c3d42645efeb85e93c17 1882 e2wm_1.4-2.dsc
 543442b551b8ec8c59c3af6bc5ef86c71afa040f 3692 e2wm_1.4-2.debian.tar.xz
 6c983ed7bfe6d9be513f48de06e0069b16071739 43324 e2wm_1.4-2_all.deb
 ab5c662470c4177c9f84bf246826b93aaa7a12f0 5934 e2wm_1.4-2_amd64.buildinfo
Checksums-Sha256:
 3a3614de3a1b262cd47cd777a97312cd156722ae1d074c3caab62f4fd1597602 1882 
e2wm_1.4-2.dsc
 32c2859df94008565d4a4af59dc134da6ed8f32a06d9543a8cf95e7bde2396f4 3692 
e2wm_1.4-2.debian.tar.xz
 95951b2948e763d093210d6b431341733a3dce2b84f04a99c5a8bbf92331d583 43324 
e2wm_1.4-2_all.deb
 e38523087213ec51aa1206afb5c005fa9295fb8542248271fc5af5b5ef0eac98 5934 
e2wm_1.4-2_amd64.buildinfo
Files:
 87ca2460223b92250ddc4deb4cdf07bd 1882 lisp optional e2wm_1.4-2.dsc
 1ad00125d2f58e6eabff14ad9c961a64 3692 

Bug#917711: marked as done (grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 15:33:50 +
with message-id 
and subject line Bug#917711: fixed in grantlee5 5.1.0-2.1
has caused the Debian Bug report #917711,
regarding grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 
test ARGS\+=-j2 returned exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
917711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grantlee5
Version: 5.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j2
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: testsafestring
>   Start  2: testbuiltins
>  1/12 Test  #1: testsafestring ...   Passed0.00 sec
>   Start  3: testloadertags
>  2/12 Test  #3: testloadertags ...   Passed0.02 sec
>   Start  4: testdefaulttags
>  3/12 Test  #2: testbuiltins .   Passed0.04 sec
>   Start  5: testcachingloader
>  4/12 Test  #5: testcachingloader    Passed0.01 sec
>   Start  6: testfilters
>  5/12 Test  #6: testfilters ..***Failed0.03 sec
> * Start testing of TestFilters *
> Config: Using QtTest library 5.11.3, Qt 5.11.3 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 8.2.0)
> PASS   : TestFilters::initTestCase()
> PASS   : TestFilters::testDateBasedFilters(filter-timesince01)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince02)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince03)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince04)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince05)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince07)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince08)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince09)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince10)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince17)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince18)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil01)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil02)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil03)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil04)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil05)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil06)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil07)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil08)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil09)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil12)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil13)
> FAIL!  : TestFilters::testDateBasedFilters(date01) Compared values are not 
> the same
>Actual   (result): ""
>Expected (output): "01"
>Loc: [/<>/templates/tests/testfilters.cpp(117)]
> FAIL!  : TestFilters::testDateBasedFilters(date02) Compared values are not 
> the same
>Actual   (result): ""
>Expected (output): "Jan. 1, 2008"
>Loc: [/<>/templates/tests/testfilters.cpp(117)]
> PASS   : TestFilters::testDateBasedFilters(date03)
> PASS   : TestFilters::testStringFilters(filter-addslash01)
> PASS   : TestFilters::testStringFilters(filter-addslash02)
> PASS   : TestFilters::testStringFilters(filter-capfirst01)
> PASS   : TestFilters::testStringFilters(filter-capfirst02)
> PASS   : TestFilters::testStringFilters(filter-fix_ampersands01)
> PASS   : TestFilters::testStringFilters(filter-fix_ampersands02)
> PASS   : TestFilters::testStringFilters(filter-floatformat01)
> PASS   : TestFilters::testStringFilters(filter-floatformat02)
> PASS   : TestFilters::testStringFilters(filter-linenumbers01)
> PASS   : TestFilters::testStringFilters(filter-linenumbers02)
> PASS   : TestFilters::testStringFilters(filter-lower01)
> PASS   : TestFilters::testStringFilters(filter-lower02)
> PASS   : TestFilters::testStringFilters(filter-make_list01)
> PASS   : TestFilters::testStringFilters(filter-make_list02)
> PASS   : TestFilters::testStringFilters(filter-make_list03)
> PASS   : TestFilters::testStringFilters(filter-make_list04)
> PASS   : 

Bug#927148: python-deprecated: Incomplete debian/copyright?

[Chris Lamb]

Source: python-deprecated
Version: 1.2.5-1
Severity: serious
Justication: Policy § 12.5
X-Debbugs-CC: Bas Couwenberg , 
ftpmas...@debian.org

Hi,

I just ACCEPTed python-deprecated from NEW but noticed it was missing 
attribution in debian/copyright for at least Marcos Cardoso.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#926381: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-1.1

[Ivo De Decker]

On Mon, Apr 15, 2019 at 03:04:20PM +, Ivo De Decker wrote:
>  ruby-fakeweb (1.3.0+git20170806+dfsg1-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Add patch skip_session_test to fix FTBFS (Closes: #926381)

Merge request with the changes here:

https://salsa.debian.org/ruby-team/ruby-fakeweb/merge_requests/1

Thanks,

Ivo

Bug#926381: marked as done (ruby-fakeweb: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 15:04:20 +
with message-id 
and subject line Bug#926381: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-1.1
has caused the Debian Bug report #926381,
regarding ruby-fakeweb: FTBFS (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-fakeweb
Version: 1.3.0+git20170806+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install -i -O--buildsystem=ruby
dh_ruby --install 
/<>/ruby-fakeweb-1.3.0\+git20170806\+dfsg1/debian/ruby-fakeweb
   dh_ruby --install

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install files   
 │
└──────────────────────────────────────────────────────────────────────────────┘

install -d 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web/registry.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web/registry.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web/utility.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web/utility.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web/responder.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web/responder.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web/response.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web/response.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web/stub_socket.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web/stub_socket.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web/ext/net_http.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web/ext/net_http.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fakeweb.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fakeweb.rb
install -D -m644 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/lib/fake_web.rb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby/fake_web.rb
dh_installchangelogs -pruby-fakeweb 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/CHANGELOG upstream

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata   
 │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at 
/<>/ruby-fakeweb-1.3.0+git20170806+dfsg1/debian/ruby-fakeweb/usr/share/rubygems-integration/all/specifications/fakeweb-1.3.0.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

Bug#926735: marked as done (Include upstream patch for extended partition size)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 15:04:07 +
with message-id 
and subject line Bug#926735: fixed in parted 3.2-25
has caused the Debian Bug report #926735,
regarding Include upstream patch for extended partition size
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libparted2
Version: 3.2-24
src:parted

Please include upstream commit c6dc6e5d from 2015 as additional package
patch because it fixes the unit of the partition resize ioctl.
http://git.savannah.gnu.org/cgit/parted.git/commit/?id=c6dc6e5d0f49a26242d2b28622514814a53d92e1

Currently the extended partitions will be inaccessible until some
program forces the kernel to reread the partition table. See related issues:
https://github.com/storaged-project/udisks/issues/425
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1641308
--- End Message ---
--- Begin Message ---
Source: parted
Source-Version: 3.2-25

We believe that the bug you reported is fixed in the latest version of
parted, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated parted package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2019 15:38:11 +0100
Source: parted
Architecture: source
Version: 3.2-25
Distribution: unstable
Urgency: medium
Maintainer: Parted Maintainer Team 
Changed-By: Colin Watson 
Closes: 926735
Changes:
 parted (3.2-25) unstable; urgency=medium
 .
   * Cherry-pick from upstream:
 - libparted: BLKPG_RESIZE_PARTITION uses bytes, not sectors (closes:
   #926735, LP: #1641308).
Checksums-Sha1:
 9c138561c32a8121545e64848f6a4b315687f72d 2780 parted_3.2-25.dsc
 d1118229cd6585c0fccb1ab1bac365ede1515e6b 88524 parted_3.2-25.debian.tar.xz
 e0385060d6478d64acab82ede6889e926ba2d0ec 6898 parted_3.2-25_source.buildinfo
Checksums-Sha256:
 3649284800b1db0972cf03cde77a711b1af7cebefcfbee11ef6c985d5633bb31 2780 
parted_3.2-25.dsc
 0bc8d0df18b83a806df08c364634fecc474fa24a8b367820bd2315489427b623 88524 
parted_3.2-25.debian.tar.xz
 9ebf9378633d959ceb36116437a6a0d48d654d0a22f89936fdbcac808d68b76e 6898 
parted_3.2-25_source.buildinfo
Files:
 f4206d32f663b20dc83a1f592cc540fd 2780 admin optional parted_3.2-25.dsc
 40781620101be15edb3174391a43a2db 88524 admin optional 
parted_3.2-25.debian.tar.xz
 582cf5ea97b1fe8f3661d754d987ffd7 6898 admin optional 
parted_3.2-25_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAly0mGwACgkQOTWH2X2G
UAudmA/9FtVQSBDGf6LcRAQDjkWNnyu3KF7C74hnJ2ECtAhNnyubbJmJRjWn5ZgU
W9GiKGFPjIWP2ZJA/bhKit2FhktkKfbRohsWMIXaCjXbkjSXt4MmXyJ0GuX5cQ48
hrGQEBd/bxHXEnx3/31uJyHKY8TQ+/SZDQUqHgNYgOu8tSwpF4dgnhQ3I9Ro3Ekm
DbAknXZBB2xv+VpUVoY5P5nlGQa9tJetGqI4fpi3q7mH/1B0O89MbozHWeLxsfru
6uLWx7LKk4cWtwk7JbP57KlW1DAj6PRgOUVQtM2eTLkE0MN8U7bfTYOBRJXJagl2
qbeKM/0UYBlgyFnjJKFciniCoYw9ppbfMFvZHY8uX1RXAt1trbi+7EUlveZQSaCb
GzhjJL0fmk1gXkLFI/eTcJj4mU0VaQ6ErQuhw+k4VCR7vpvtDz8Om5NJ+exqCLG6
dew8iDgHkfsa7p+3o6Mg8xa4PGd16fCXt5CK73Umszpohk0pEQrGvqWRyEAy3nW3
ZMFfnDSKNzA5R8rqsSyHJbdMZ8XQzBWdSy4f1GNjz8p+5NbQ6jMxHy0ZUwbqo0Fj
N/Zho9Jo04E4rp0MRDunKvAE6QqZGlDTZcPYl44kSEl3GtTpxc8qClNAWnEnhZBU
rclQWhL50cqQv382CCIailWoJETlqOY0+Jjml6FySVd/a2khTCc=
=C5nb
-END PGP SIGNATURE End Message ---

Bug#842269: marked as done (parted clobbers in-memory state of extended partitions)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 15:04:07 +
with message-id 
and subject line Bug#926735: fixed in parted 3.2-25
has caused the Debian Bug report #926735,
regarding parted clobbers in-memory state of extended partitions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: parted
Version: 3.2-16+b1

Please see https://bugzilla.redhat.com/show_bug.cgi?id=1135493

Additional information: This bug is probably masked most of the time
because of the asynchronous BLKRRPART done by udev some time later.
However, newer versions of Storaged disable this BLKRRPART.

This has been fixed upstream, but has not been released.  It is probably
best to tickle a release out of upstream...

To reproduce:

  # flock -s /dev/sda sleep infinity &
  # parted /dev/sda mktable msdos
  # parted /dev/sda mkpart extended 1MiB 40MiB
  # parted /dev/sda mkpart logical ext2 2MiB 40MiB
  # blkid -p /dev/sda1
  error: /dev/sda1: No such device or address

  # kill %1
  [1]+  Terminated  flock -s /dev/sda sleep infinity
  # echo >/dev/sda
  # blkid -p /dev/sda1
  /dev/sda1: PTTYPE="dos" PART_ENTRY_SCHEME="dos"
  PART_ENTRY_UUID="a05ee957-01" PART_ENTRY_TYPE="0xf"
  PART_ENTRY_NUMBER="1" PART_ENTRY_OFFSET="2048" PART_ENTRY_SIZE="79872"
  PART_ENTRY_DISK="8:0"

The "flock" prevents udevd from issuing its usual BLKRRPART ioctl.
--- End Message ---
--- Begin Message ---
Source: parted
Source-Version: 3.2-25

We believe that the bug you reported is fixed in the latest version of
parted, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated parted package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2019 15:38:11 +0100
Source: parted
Architecture: source
Version: 3.2-25
Distribution: unstable
Urgency: medium
Maintainer: Parted Maintainer Team 
Changed-By: Colin Watson 
Closes: 926735
Changes:
 parted (3.2-25) unstable; urgency=medium
 .
   * Cherry-pick from upstream:
 - libparted: BLKPG_RESIZE_PARTITION uses bytes, not sectors (closes:
   #926735, LP: #1641308).
Checksums-Sha1:
 9c138561c32a8121545e64848f6a4b315687f72d 2780 parted_3.2-25.dsc
 d1118229cd6585c0fccb1ab1bac365ede1515e6b 88524 parted_3.2-25.debian.tar.xz
 e0385060d6478d64acab82ede6889e926ba2d0ec 6898 parted_3.2-25_source.buildinfo
Checksums-Sha256:
 3649284800b1db0972cf03cde77a711b1af7cebefcfbee11ef6c985d5633bb31 2780 
parted_3.2-25.dsc
 0bc8d0df18b83a806df08c364634fecc474fa24a8b367820bd2315489427b623 88524 
parted_3.2-25.debian.tar.xz
 9ebf9378633d959ceb36116437a6a0d48d654d0a22f89936fdbcac808d68b76e 6898 
parted_3.2-25_source.buildinfo
Files:
 f4206d32f663b20dc83a1f592cc540fd 2780 admin optional parted_3.2-25.dsc
 40781620101be15edb3174391a43a2db 88524 admin optional 
parted_3.2-25.debian.tar.xz
 582cf5ea97b1fe8f3661d754d987ffd7 6898 admin optional 
parted_3.2-25_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAly0mGwACgkQOTWH2X2G
UAudmA/9FtVQSBDGf6LcRAQDjkWNnyu3KF7C74hnJ2ECtAhNnyubbJmJRjWn5ZgU
W9GiKGFPjIWP2ZJA/bhKit2FhktkKfbRohsWMIXaCjXbkjSXt4MmXyJ0GuX5cQ48
hrGQEBd/bxHXEnx3/31uJyHKY8TQ+/SZDQUqHgNYgOu8tSwpF4dgnhQ3I9Ro3Ekm
DbAknXZBB2xv+VpUVoY5P5nlGQa9tJetGqI4fpi3q7mH/1B0O89MbozHWeLxsfru
6uLWx7LKk4cWtwk7JbP57KlW1DAj6PRgOUVQtM2eTLkE0MN8U7bfTYOBRJXJagl2
qbeKM/0UYBlgyFnjJKFciniCoYw9ppbfMFvZHY8uX1RXAt1trbi+7EUlveZQSaCb
GzhjJL0fmk1gXkLFI/eTcJj4mU0VaQ6ErQuhw+k4VCR7vpvtDz8Om5NJ+exqCLG6
dew8iDgHkfsa7p+3o6Mg8xa4PGd16fCXt5CK73Umszpohk0pEQrGvqWRyEAy3nW3
ZMFfnDSKNzA5R8rqsSyHJbdMZ8XQzBWdSy4f1GNjz8p+5NbQ6jMxHy0ZUwbqo0Fj
N/Zho9Jo04E4rp0MRDunKvAE6QqZGlDTZcPYl44kSEl3GtTpxc8qClNAWnEnhZBU
rclQWhL50cqQv382CCIailWoJETlqOY0+Jjml6FySVd/a2khTCc=
=C5nb
-END PGP SIGNATURE End Message ---

Processed: Re: Bug triaged and submitted upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #917711 [src:grantlee5] grantlee5: FTBFS: dh_auto_test: cd 
obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2
Added tag(s) pending and patch.

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

Bug#917711: Bug triaged and submitted upstream

[Ivo De Decker]

Control: tags -1 patch pending

Hi Giovanni,

On Sat, Mar 30, 2019 at 02:12:29PM +0100, Giovanni Mascellani wrote:
> I triaged and submitted upstream this bug:
> 
>   https://github.com/steveire/grantlee/issues/51
> 
> The upstream bug contains my current understanding of the bug and asks
> for help on how to proceed, because I am not really sure on what is the
> best way forward.
> 
> I hope this helps fixing the bug!

It seems upstream came to the same conclusion as you. This patch was committed
upstream:

https://github.com/steveire/grantlee/commit/3cb4bd24e127b7f55d463d934cad27f8c07c4406

I uploaded an NMU based on that patch. Debdiff attached.

Cheers,

Ivo

diff -Nru grantlee5-5.1.0/debian/changelog grantlee5-5.1.0/debian/changelog
--- grantlee5-5.1.0/debian/changelog2016-10-24 09:35:52.0 +
+++ grantlee5-5.1.0/debian/changelog2019-04-15 14:53:13.0 +
@@ -1,3 +1,10 @@
+grantlee5 (5.1.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch datatime-fractional.diff to fix FTBFS (Closes: #917711)
+
+ -- Ivo De Decker   Mon, 15 Apr 2019 14:53:13 +
+
 grantlee5 (5.1.0-2) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru grantlee5-5.1.0/debian/patches/datatime-fractional.diff 
grantlee5-5.1.0/debian/patches/datatime-fractional.diff
--- grantlee5-5.1.0/debian/patches/datatime-fractional.diff 1970-01-01 
00:00:00.0 +
+++ grantlee5-5.1.0/debian/patches/datatime-fractional.diff 2019-04-15 
14:53:13.0 +
@@ -0,0 +1,15 @@
+See
+https://github.com/steveire/grantlee/commit/3cb4bd24e127b7f55d463d934cad27f8c07c4406
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917711
+
+--- a/templates/defaultfilters/datetime.cpp
 b/templates/defaultfilters/datetime.cpp
+@@ -97,7 +97,7 @@
+ {
+   Q_UNUSED(autoescape)
+   auto d = QDateTime::fromString(getSafeString(input),
+- QStringLiteral("-MM-ddThh:mm:ss"));
++ QStringLiteral("-MM-ddThh:mm:ss.zzz"));
+ 
+   auto argString = getSafeString(argument);
+ 
diff -Nru grantlee5-5.1.0/debian/patches/series 
grantlee5-5.1.0/debian/patches/series
--- grantlee5-5.1.0/debian/patches/series   2016-10-24 09:35:52.0 
+
+++ grantlee5-5.1.0/debian/patches/series   2019-04-15 14:53:13.0 
+
@@ -1 +1,2 @@
 variantIsTrue-float-fix.diff
+datatime-fractional.diff

Bug#926195: marked as done (e2wm/emacs-window-layout: unintended dist-upgrade dependency resolution due to missing "emacsen" dependency if installed together with emacs25-lucid)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 15:03:47 +
with message-id 
and subject line Bug#926195: fixed in emacs-window-layout 1.4-2
has caused the Debian Bug report #926195,
regarding e2wm/emacs-window-layout: unintended dist-upgrade dependency 
resolution due to missing "emacsen" dependency if installed together with 
emacs25-lucid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2wm
Version: 1.4-1
Severity: serious
Control: affects -1 + emacs-lucid emacs25-lucid
Control: clone -1 -2
Control: reassign -2 emacs-window-layout
Control: found -2 emacs-window-layout/1.4

Dear Maintainer,

if I upgrade a machine with emacs25-lucid and e2wm or
emacs-window-layout installed from e.g. Stretch to Buster, I can't
upgrade emacs25-lucid to emacs-lucid, because e2wm/emacs-window-layout
in Buster only depend on "emacs25-nox | emacs25", but not on any of the
generic virtual emacs packages like "emacs" or "emacsen".

Historically that worked, because emacs25-lucid did provide also
"emacs25" in Stretch, but since it's just a transitional package in
Buster, it no more provides emacs25 but depends on emacs-lucid which
itself only provides the current virtual emacs packages "emacs" and
"emacsen" (plus some other more generic things like "editor" which are
not relevant in this case).

So please change the dependencies to at least include "emacs" or even
better — because backwards compatible — "emacsen".

P.S.: IMHO this is release-critical because there is a dependency
missing which mislead both apt as well as aptitude on dist-upgrades:

* apt wants to replace emacs25-lucid (a lean GUI variant) with
  the non-gui variant emacs25-nox (which is not intended at all), and,

* depending on settings, aptitude suggests to not upgrade emacs25-lucid
  or to replace it with emacs25-nox as first suggestion, too:

  The following packages have unmet dependencies:
   emacs-lucid : Conflicts: emacs-nox but 1:26.1+1-3.2 is to be installed
   emacs-nox : Conflicts: emacs-lucid but 1:26.1+1-3.2 is to be installed
  The following actions will resolve these dependencies:

   Remove the following packages:
  1) emacs25-lucid [25.1+1-4+deb9u1 (now)]

   Keep the following packages at their current version:
  2) emacs-lucid [Not Installed]

On just "apt upgrade" or "aptitude safe-upgrade" both keep back
emacs25-lucid.

All these dependency resolution issues have no real reason except
missing (uptodate alternative) dependencies.
--- End Message ---
--- Begin Message ---
Source: emacs-window-layout
Source-Version: 1.4-2

We believe that the bug you reported is fixed in the latest version of
emacs-window-layout, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
KURASHIKI Satoru  (supplier of updated emacs-window-layout 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2019 22:11:38 +0900
Source: emacs-window-layout
Binary: emacs-window-layout
Architecture: source all
Version: 1.4-2
Distribution: unstable
Urgency: medium
Maintainer: KURASHIKI Satoru 
Changed-By: KURASHIKI Satoru 
Description:
 emacs-window-layout - window layout manager for emacs
Closes: 926195
Changes:
 emacs-window-layout (1.4-2) unstable; urgency=medium
 .
   * Fix Depends: on emacs. (Closes: #926195)
Checksums-Sha1:
 a1884795155319efffd966bf17c715758fb4a4f6 1966 emacs-window-layout_1.4-2.dsc
 18f78d4862ccd85878930fd69467d24ee0c475c0 3180 
emacs-window-layout_1.4-2.debian.tar.xz
 ba9800f781ec532e29a324449bd7eae2e0e01a44 11540 
emacs-window-layout_1.4-2_all.deb
 b11203129acedc15c025e90adb27a815557e71f5 9843 
emacs-window-layout_1.4-2_amd64.buildinfo
Checksums-Sha256:
 289bf618847674aa8dd8ed807cc3ed7beae43b91468bc896c3796e6916f1c33f 1966 
emacs-window-layout_1.4-2.dsc
 70d4acd2ae467a49c3dbd1dbac3fae7f7ce26d9ef7bbcba87cd114a0aff1cb04 3180 
emacs-window-layout_1.4-2.debian.tar.xz
 e13ff9bf7cefe6e48fff8ec0690a0bb84564f70324f5114d0346cd14cfaea68b 11540 

Processed: reassign 842269 to libparted2, forcibly merging 926735 842269

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 842269 libparted2
Bug #842269 [parted] parted clobbers in-memory state of extended partitions
Bug reassigned from package 'parted' to 'libparted2'.
No longer marked as found in versions parted/3.2-16.
Ignoring request to alter fixed versions of bug #842269 to the same values 
previously set
> forcemerge 926735 842269
Bug #926735 [libparted2] Include upstream patch for extended partition size
Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions
Severity set to 'serious' from 'normal'
Marked as found in versions parted/3.2-24.
Merged 842269 926735
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842269
926735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#926735: Bug #926735 in parted marked as pending

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #926735 in parted reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/parted-team/parted/commit/82a400795e78b08f4cf3fbe11923531059624e0b


libparted: BLKPG_RESIZE_PARTITION uses bytes, not sectors

Closes: #926735
LP: #1641308


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/926735

Processed: Bug #926735 in parted marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #926735 [libparted2] Include upstream patch for extended partition size
Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions
Added tag(s) pending.
Added tag(s) pending.

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

Processed: reassign 926735 to libparted2, forcibly merging 926735 842269

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 926735 libparted2
Bug #926735 [libparted2] Include upstream patch for extended partition size
Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions
Ignoring request to reassign bug #926735 to the same package
Ignoring request to reassign bug #842269 to the same package
> forcemerge 926735 842269
Bug #926735 [libparted2] Include upstream patch for extended partition size
Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions
Bug #842269 [libparted2] parted clobbers in-memory state of extended partitions
Merged 842269 926735
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842269
926735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tags 924976 patch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 924976 patch
Bug #924976 [python-kombu] python3-kombu: Incompatible with python3-redis (>= 3)
Added tag(s) patch.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
924976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 924976 python3-celery

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 924976 python3-celery
Bug #924976 [python-kombu] python3-kombu: Incompatible with python3-redis (>= 3)
Added indication that 924976 affects python3-celery
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
924976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#924976: python3-kombu: Incompatible with python3-redis (>= 3)

[Josue Ortega]

Hi,

python-redis changed its API in version 3 breaking python-kombu. This has been 
fixed
in the latest upstream version. 
I've attached the debdiff with the fix for v4.2.1. If you don'have time to make 
this upload
let me know and I will upload it myself

Regards

Josue
diff -Nru kombu-4.2.1/debian/changelog kombu-4.2.1/debian/changelog
--- kombu-4.2.1/debian/changelog2019-03-01 13:03:25.0 -0600
+++ kombu-4.2.1/debian/changelog2019-04-15 07:11:18.0 -0600
@@ -1,3 +1,11 @@
+kombu (4.2.1-3) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Add debian/patch/0005-Fix-compat-with-redis3.patch to fix compatibility 
with
+python-redis (>= 3) (Closes: #924976).
+
+ -- Josue Ortega   Mon, 15 Apr 2019 07:11:18 -0600
+
 kombu (4.2.1-2) unstable; urgency=high
 
   [ Ond??ej Nov?? ]
diff -Nru kombu-4.2.1/debian/patches/0005-Fix-compat-with-redis3.patch 
kombu-4.2.1/debian/patches/0005-Fix-compat-with-redis3.patch
--- kombu-4.2.1/debian/patches/0005-Fix-compat-with-redis3.patch
1969-12-31 18:00:00.0 -0600
+++ kombu-4.2.1/debian/patches/0005-Fix-compat-with-redis3.patch
2019-04-15 07:11:18.0 -0600
@@ -0,0 +1,41 @@
+Description: Fix compat with redis >= 3
+Author: Josue Ortega 
+Last-Update: 2019-04-15
+
+--- a/kombu/transport/redis.py
 b/kombu/transport/redis.py
+@@ -145,8 +145,14 @@
+ def append(self, message, delivery_tag):
+ delivery = message.delivery_info
+ EX, RK = delivery['exchange'], delivery['routing_key']
++
++# Redis-py changed the format of zadd args in v3.0.0
++zadd_args = [{delivery_tag: time()}]
++if redis.VERSION[0] < 3:
++zadd_args = [time(), delivery_tag]
++
+ with self.pipe_or_acquire() as pipe:
+-pipe.zadd(self.unacked_index_key, time(), delivery_tag) \
++pipe.zadd(self.unacked_index_key, *zadd_args) \
+ .hset(self.unacked_key, delivery_tag,
+   dumps([message._raw, EX, RK])) \
+ .execute()
+--- a/t/unit/transport/test_redis.py
 b/t/unit/transport/test_redis.py
+@@ -75,8 +75,14 @@
+ def sadd(self, key, member, *args):
+ self.sets[key].add(member)
+ 
+-def zadd(self, key, score1, member1, *args):
+-self.sets[key].add(member1)
++def zadd(self, key, *args):
++if redis.redis.VERSION[0] >= 3:
++(mapping,) = args
++for item in mapping:
++self.sets[key].add(item)
++else:
++(score1, member1) = args
++self.sets[key].add(member1)
+ 
+ def smembers(self, key):
+ return self.sets.get(key, set())
diff -Nru kombu-4.2.1/debian/patches/series kombu-4.2.1/debian/patches/series
--- kombu-4.2.1/debian/patches/series   2019-03-01 13:03:25.0 -0600
+++ kombu-4.2.1/debian/patches/series   2019-04-15 07:11:18.0 -0600
@@ -1,3 +1,4 @@
+0005-Fix-compat-with-redis3.patch
 0001-Remove-image-from-remote-donation-site-privacy-issue.patch
 0002-Disable-intershpinx-mapping-for-now.patch
 0003-Remove-pytest-sugar-from-test-requirements.patch


signature.asc
Description: PGP signature

Processed: retitle 924976 python3-kombu: Incompatible with python3-redis (>= 3)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 924976 python3-kombu: Incompatible with python3-redis (>= 3)
Bug #924976 [python-kombu] python3-celery: Incompatible with 
python3-redis/python3-kombu versions
Changed Bug title to 'python3-kombu: Incompatible with python3-redis (>= 3)' 
from 'python3-celery: Incompatible with python3-redis/python3-kombu versions'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
924976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#923906: fixed in snapd-glib 1.45-1.1

[Ivo De Decker]

Hi,

On Mon, Apr 15, 2019 at 01:18:38PM +, Ivo De Decker wrote:
>  snapd-glib (1.45-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Update debian/libsnapd-qt1.symbols to fix FTBFS (Closes: #923906)

I pushed the patches here:

https://salsa.debian.org/ivodd/snapd-glib/commits/buster


Ivo

Processed: reassign 924976 python-kombu

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 924976 python-kombu
Bug #924976 [python3-celery] python3-celery: Incompatible with 
python3-redis/python3-kombu versions
Bug reassigned from package 'python3-celery' to 'python-kombu'.
No longer marked as found in versions celery/4.2.1-3.
Ignoring request to alter fixed versions of bug #924976 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
924976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#923906: marked as done (snapd-glib: FTBFS (dh_makeshlibs fails))

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 13:18:38 +
with message-id 
and subject line Bug#923906: fixed in snapd-glib 1.45-1.1
has caused the Debian Bug report #923906,
regarding snapd-glib: FTBFS (dh_makeshlibs fails)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
923906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:snapd-glib
Version: 1.45-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with gir
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:15: installing './compile'

[... snipped ...]

make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>/doc'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
   dh_installchangelogs -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs -V -- -c4
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libsnapd-qt1/DEBIAN/symbols doesn't match 
completely debian/libsnapd-qt1.symbols
--- debian/libsnapd-qt1.symbols (libsnapd-qt1_1.45-1_amd64)
+++ dpkg-gensymbols9MZ5bz   2019-03-06 21:44:10.066218363 +
@@ -332,11 +332,11 @@
  (c++|regex)"^.*Request::runSync\(\)@Base$" 0
  (c++|regex)"^QMetaTypeIdQObject<.*@Base$" 0
  (c++|regex)"^QtMetaTypePrivate::.*@Base$" 0
- (c++|regex)"^int qRegisterNormalizedMetaType<.*>\(.*\)@Base$" 0
+#MISSING: 1.45-1# (c++|regex)"^int 
qRegisterNormalizedMetaType<.*>\(.*\)@Base$" 0
  (c++|regex)"^typeinfo for .*@Base$" 0
  (c++|regex)"^typeinfo name for .*@Base$" 0
  (c++|regex)"^vtable for .*$" 0
  (c++)"login(QString const&, QString const&)@Base" 1.8
  (c++)"login(QString const&, QString const&, QString const&)@Base" 0
  (optional)stream_wrapper_get_type@Base 1.9
- (c++|optional)"void std::__cxx11::basic_string, 
std::allocator >::_M_construct(char const*, char const*, 
std::forward_iterator_tag)@Base" 1.44
+#MISSING: 1.45-1# (c++|optional)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 1.44
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:12: override_dh_makeshlibs] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B". I would like  
  
to add a reference to reproducible-builds, but it's currently down.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: snapd-glib
Source-Version: 1.45-1.1

We believe that the bug you reported is fixed in the latest version of
snapd-glib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

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

Debian distribution maintenance software
pp.
Ivo De Decker  (supplier of updated snapd-glib package)

(This message was generated automatically at their request; if you
believe that there is a problem 

Bug#824122: marked as done (synaptic: can't open synaptic when using gnome-wayland)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 20:25:29 +0800
with message-id 

and subject line Re: Bug#818366: synaptic: fails to start under Wayland
has caused the Debian Bug report #818366,
regarding synaptic: can't open synaptic when using gnome-wayland
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
818366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.83+b1
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

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

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

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



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.13-1
ii  libapt-inst2.0   1.2.11
ii  libapt-pkg5.01.2.11
ii  libatk1.0-0  2.20.0-1
ii  libc62.22-7
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libept1.5.0  1.1+nmu3
ii  libgcc1  1:6.1.1-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgnutls30  3.4.11-4
ii  libgtk-3-0   3.20.3-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libstdc++6   6.1.1-1
ii  libvte-2.91-00.44.1-1
ii  libx11-6 2:1.6.3-1
ii  libxapian22v51.2.23-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-9
ii  libgtk2-perl   2:1.2498-1
ii  policykit-10.105-15
ii  rarian-compat  0.8.1-6
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.47+nmu2
pn  deborphan
pn  dwww 
pn  menu 
pn  software-properties-gtk  
ii  tasksel  3.34

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: synaptic
Source-Version: 0.84.6

Forget to mention in Changelog, synaptic/0.84.6 can start on wayland
now, but without administrative privileges, which means you can start
synaptic in a read-only mode on wayland.

Although it's not a perfect solution, but "fails to start under
Wayland" is fixed.

Changes:
 synaptic (0.84.6) unstable; urgency=medium
 .
   [ sajolida ]
   * Give visual feedback while starting
 .
   [ Shengjing Zhu ]
   * configure.in: Miss bumping version str to 0.84.5
   * synaptic-pkexec: Do not use pkexec under Wayland; warn users instead
   * gsynaptic: Show possible reason when failed to init gtk
 .
   [ Michael Vogt ]
   * configure.in: Bump version to 0.84.6--- End Message ---

Bug#818366: marked as done (synaptic: fails to start under Wayland)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 20:25:29 +0800
with message-id 

and subject line Re: Bug#818366: synaptic: fails to start under Wayland
has caused the Debian Bug report #818366,
regarding synaptic: fails to start under Wayland
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
818366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.83+b1
Severity: normal

Dear Maintainer,

When attempting to start Synaptic on GNOME Wayland, it fails to start. When
attempting to run as root via sudo from a terminal, the following error
appears:

ryan@ArchibaldColgan:~$ sudo synaptic
No protocol specified
Unable to init server: Could not connect: Connection refused

(synaptic:30717): Gtk-WARNING **: cannot open display: :0



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.13-1
ii  libapt-inst2.0   1.2.6
ii  libapt-pkg5.01.2.6
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-9
ii  libcairo-gobject21.14.6-1
ii  libcairo21.14.6-1
ii  libept1.5.0  1.1+nmu3
ii  libgcc1  1:5.3.1-11
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.46.2-3
ii  libgnutls30  3.4.9-2
ii  libgtk-3-0   3.18.8-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libstdc++6   5.3.1-11
ii  libvte-2.91-00.42.4-1
ii  libx11-6 2:1.6.3-1
ii  libxapian22v51.2.22-3
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-9
ii  libgtk2-perl   2:1.2498-1
ii  policykit-10.105-14.1
ii  rarian-compat  0.8.1-6
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.47+nmu2
pn  deborphan
pn  dwww 
ii  menu 2.1.47
pn  software-properties-gtk  
ii  tasksel  3.34

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: synaptic
Source-Version: 0.84.6

Forget to mention in Changelog, synaptic/0.84.6 can start on wayland
now, but without administrative privileges, which means you can start
synaptic in a read-only mode on wayland.

Although it's not a perfect solution, but "fails to start under
Wayland" is fixed.

Changes:
 synaptic (0.84.6) unstable; urgency=medium
 .
   [ sajolida ]
   * Give visual feedback while starting
 .
   [ Shengjing Zhu ]
   * configure.in: Miss bumping version str to 0.84.5
   * synaptic-pkexec: Do not use pkexec under Wayland; warn users instead
   * gsynaptic: Show possible reason when failed to init gtk
 .
   [ Michael Vogt ]
   * configure.in: Bump version to 0.84.6--- End Message ---

Bug#897348: marked as done (synaptic: Unable to init server: Could not connect: Connection refused)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 20:25:29 +0800
with message-id 

and subject line Re: Bug#818366: synaptic: fails to start under Wayland
has caused the Debian Bug report #818366,
regarding synaptic: Unable to init server: Could not connect: Connection refused
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
818366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.84.3
Severity: grave
Justification: renders package unusable

Dear Maintainer,
Installed debian amd64 from live installed, then upgraded to testing. synaptic
doesn't launch from GUI.
Launching it from terminal displays:
$ sudo synaptic
[sudo] password for user:
No protocol specified
Unable to init server: Could not connect: Connection refused
(synaptic:28704): Gtk-WARNING **: 23:30:27.352: cannot open display: :0

It is fixed by the command
$ xhost +si:localuser:root
localuser:root being added to access control list

Related: bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1712089



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.17-2
ii  libapt-inst2.0   1.6.1
ii  libapt-pkg5.01.6.1
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-3
ii  libcairo-gobject21.15.10-3
ii  libcairo21.15.10-3
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:8-20180425-1
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgnutls30  3.5.18-1
ii  libgtk-3-0   3.22.29-3
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  libpcre2-8-0 10.31-3
ii  libstdc++6   8-20180425-1
ii  libvte-2.91-00.52.0-1
ii  libx11-6 2:1.6.5-1
ii  libxapian30  1.4.5-1
ii  policykit-1  0.105-20
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.24992-1+b1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.2-2

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.43

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: synaptic
Source-Version: 0.84.6

Forget to mention in Changelog, synaptic/0.84.6 can start on wayland
now, but without administrative privileges, which means you can start
synaptic in a read-only mode on wayland.

Although it's not a perfect solution, but "fails to start under
Wayland" is fixed.

Changes:
 synaptic (0.84.6) unstable; urgency=medium
 .
   [ sajolida ]
   * Give visual feedback while starting
 .
   [ Shengjing Zhu ]
   * configure.in: Miss bumping version str to 0.84.5
   * synaptic-pkexec: Do not use pkexec under Wayland; warn users instead
   * gsynaptic: Show possible reason when failed to init gtk
 .
   [ Michael Vogt ]
   * configure.in: Bump version to 0.84.6--- End Message ---

Bug#872553: marked as done (synaptic: Segmentation fault when program starts)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 20:25:29 +0800
with message-id 

and subject line Re: Bug#818366: synaptic: fails to start under Wayland
has caused the Debian Bug report #818366,
regarding synaptic: Segmentation fault when program starts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
818366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.84.2
Severity: grave
Tags: security
Justification: renders package unusable

Segmentation fault



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.5~beta2
ii  libapt-pkg5.01.5~beta2
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-14
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:7.1.0-13
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.4-3
ii  libgnutls30  3.5.14-2
ii  libgtk-3-0   3.22.18-1
ii  libpango-1.0-0   1.40.9-1
ii  libpangocairo-1.0-0  1.40.9-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   7.1.0-13
ii  libvte-2.91-00.46.2-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.4-2
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.24992-1+b1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: synaptic
Source-Version: 0.84.6

Forget to mention in Changelog, synaptic/0.84.6 can start on wayland
now, but without administrative privileges, which means you can start
synaptic in a read-only mode on wayland.

Although it's not a perfect solution, but "fails to start under
Wayland" is fixed.

Changes:
 synaptic (0.84.6) unstable; urgency=medium
 .
   [ sajolida ]
   * Give visual feedback while starting
 .
   [ Shengjing Zhu ]
   * configure.in: Miss bumping version str to 0.84.5
   * synaptic-pkexec: Do not use pkexec under Wayland; warn users instead
   * gsynaptic: Show possible reason when failed to init gtk
 .
   [ Michael Vogt ]
   * configure.in: Bump version to 0.84.6--- End Message ---

Bug#897975: [gdm3]

[rastersoft]

Hi:

I'm compiling it, but is there a way of easily create a .deb package 
with the compiled code? (there seems to be debian/control files, so it 
seems to be something quite straight up...)


El 14/4/19 a las 16:36, Iain Lane escribió:

Hi,

Sorry for the delay. Niels pointed me at this bug, which is suspiciously
similar to one we saw on Ubuntu around the same time ...

On Wed, Jun 13, 2018 at 01:43:18PM +0200, rastersoft wrote:

After several tests, I started to suspect that the problem could be in the
firmware loading: my hypothesis is that when I use my SSD hard disk, the
loading is so fast that the graphic card is still not available when GDM
tries to boot in Wayland mode, so it fails and tries again in X11 mode. At
this moment it has ended loading the firmware as is available, so this mode
succeeds, but without offering Wayland because that failed before. If I
enter a session and exit, GDM is reloaded and this time the Wayland mode
works because the graphics card's firmware is already loaded.

To test this I renamed /usr/sbin/gdm3 to /usr/sbin/gdm3_bin, and created a
little script at /usr/sbin/gdm3 that waits 3 seconds before launching the
true gdm3. With this quick and dirty hack everything works fine: GDM3 is
always shown after booting, and I have Wayland available.

Of course, this is not a true solution: the system should wait until the
graphics card is fully available before continuing loading, and not just
"add a delay". But I think it proofs that there is some kind of race
condition during boot.

Your theory is right - GDM is starting up before the DRM devices that it
needs are available, and it doesn't handle that very well. We have a
workaround in place in Ubuntu which seems to have fixed the bug.  There
is actually a logind boolean property "CanGraphical" for this, that was
introduced so display managers like GDM can wait before they start up.
But the branch to make GDM respect this property[0] isn't yet merged
because it is a bit unreliable so far.

So I cherry-picked the Ubuntu workaround to a branch on salsa. Would you
be able to try it please? (Test built but not tried it myself yet, so
sorry if there's some stupid mistake.)

   https://salsa.debian.org/gnome-team/gdm/commits/wip/gdm-wait-for-drm

I can't test this myself. Apparently none of my machines are capable of
tickling this bug. :(

Cheers,


--
Nos leemos
 RASTER(Linux user #228804)
ras...@rastersoft.com  http://www.rastersoft.com

Bug#927126: aqemu: after updating can't open VMs

[Abhijith PA]

Package: aqemu
Version: 0.9.2-2.1
Severity: grave
Justification: renders package unusable


I recently updated aqemu and ended up in not able to open VMs.

Following is the message is what I get when I open VMs

AQEMU Error [264] >>>
Sender: QEMU return value != 0
Message:


-- 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=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aqemu depends on:
ii  libc62.28-8
ii  libgcc1  1:8.3.0-6
ii  libqt5core5a 5.11.3+dfsg1-1
ii  libqt5dbus5  5.11.3+dfsg1-1
ii  libqt5gui5   5.11.3+dfsg1-1
ii  libqt5network5   5.11.3+dfsg1-1
ii  libqt5printsupport5  5.11.3+dfsg1-1
ii  libqt5test5  5.11.3+dfsg1-1
ii  libqt5widgets5   5.11.3+dfsg1-1
ii  libstdc++6   8.3.0-6
ii  libvncclient10.9.11+dfsg-1.3
ii  qemu 1:3.1+dfsg-7

Versions of packages aqemu recommends:
ii  qemu-kvm  1:3.1+dfsg-7

aqemu suggests no packages.

-- no debconf information

Bug#902190: marked as done (vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 10:47:09 +
with message-id 
and subject line Bug#902190: fixed in vcftools 0.1.14+dfsg-4+deb9u1
has caused the Debian Bug report #902190,
regarding vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
902190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vcftools
Severity: grave
Tags: security

Please see
http://seclists.org/fulldisclosure/2018/May/43
https://github.com/vcftools/vcftools/issues/109

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: vcftools
Source-Version: 0.1.14+dfsg-4+deb9u1

We believe that the bug you reported is fixed in the latest version of
vcftools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated vcftools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Apr 2019 17:49:29 +0200
Source: vcftools
Binary: vcftools
Architecture: source amd64
Version: 0.1.14+dfsg-4+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Dylan Aïssi 
Description:
 vcftools   - Collection of tools to work with VCF files
Closes: 902190
Changes:
 vcftools (0.1.14+dfsg-4+deb9u1) stretch; urgency=medium
 .
   * Team upload.
   * Add patch from upstream to fix CVE-2018-11099, CVE-2018-11129 and
   CVE-2018-11130 (Closes: #902190).
Checksums-Sha1:
 8410efd82e41095df57f48bcd70076b01bd076ec 2164 vcftools_0.1.14+dfsg-4+deb9u1.dsc
 d9923c50cb32cbca6cde00d89fe4160482be1135 13944 
vcftools_0.1.14+dfsg-4+deb9u1.debian.tar.xz
 4f34095dc8b447756d54447daac0f35ef7eff97b 3563928 
vcftools-dbgsym_0.1.14+dfsg-4+deb9u1_amd64.deb
 fa91ac7374e5095c8ff4627e32ba5f0279a0376e 6202 
vcftools_0.1.14+dfsg-4+deb9u1_amd64.buildinfo
 82faa26d930f473a5629cd075eae0223b06fb030 458340 
vcftools_0.1.14+dfsg-4+deb9u1_amd64.deb
Checksums-Sha256:
 f7d67d4e9b4702638ec8a41b9f4fc94e201d5aa87abc84ed9fb716baceb349e7 2164 
vcftools_0.1.14+dfsg-4+deb9u1.dsc
 b56d8f8a575327e8d9d1c3a05d0fab1a21f575830e861bb79e8d9c8562cda5e8 13944 
vcftools_0.1.14+dfsg-4+deb9u1.debian.tar.xz
 c27f04840f636d95516901cbf30270d2432781a814b8cc1aa83c2ab49b5c6d62 3563928 
vcftools-dbgsym_0.1.14+dfsg-4+deb9u1_amd64.deb
 3e6945b3d0c9f29a0a0aa99d56dc79b526bf6e2679616c15b67888dcfb253ad3 6202 
vcftools_0.1.14+dfsg-4+deb9u1_amd64.buildinfo
 9d909c0d0812290af150acbcb753e634d58cee387a7d5ec9a3797f23e10154f4 458340 
vcftools_0.1.14+dfsg-4+deb9u1_amd64.deb
Files:
 726013a576f8ced8c5ab9bed4e83f348 2164 science optional 
vcftools_0.1.14+dfsg-4+deb9u1.dsc
 a391764dfe58bc2e90aa0420dc21d7cf 13944 science optional 
vcftools_0.1.14+dfsg-4+deb9u1.debian.tar.xz
 525f6ffbfa0a2f5f9dff31404c2f0cdd 3563928 debug extra 
vcftools-dbgsym_0.1.14+dfsg-4+deb9u1_amd64.deb
 de4da243000fa45d1b86bebda2658427 6202 science optional 
vcftools_0.1.14+dfsg-4+deb9u1_amd64.buildinfo
 b38fec92c799655c04715a409f97cf95 458340 science optional 
vcftools_0.1.14+dfsg-4+deb9u1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAly0JKESHGRhaXNzaUBk
ZWJpYW4ub3JnAAoJEGEu8WE+BQ9UoqEP/1btaWl908xiCQ8dKwtcuUruf+tDfwIG
gZP6SqgpqOBEEkXjgmDDIn1D7hp5IKaZuvgAFYjSTG4+QiQgSSYzDZ9NdLkHn8x/
rLz3wS2ngwbCFTgA11L+LLan5LagLgwWH6KhfWfuOvKtLpqb2o6yT2nqQ3xptweO
wRFYlLhkov326AHfROTzdOO8cJldqfj9CW4KIXLpCnRhsQN8BG02s4frZW7FR8zS
SiyaN8/UJAdUnRQTIk1y5R5OZT8/SdMaT+xMS3ur8fzi8+I+VVKQRi3c5vW3EvaO
62X6K1vgMt9yJcpfeNICTvvhqSFvXqNO+S0j1ndbzVcNqJl8RI1lTv1lYHolIfAQ
DJDm+07sl56g9pzLwQOfmo/EUJX8dMSXF8wv2vw+qVODvhkx8W9Q5HO1G8JLEPb9
cwAvy8yfsZidxB6jWyF5/U6zr/OGvo6+5D0kXNRWSRaAVaSJsjPF6YLRmWBp9u4c
n+bXQES5fek+Gi0IBnUakT29Gyw3kzo8E6OmrPbJuCQeU4aNQX4i4GUk0l8UX+re
HAJqLfkVtKIo6+fXG/nwe2FEtB9C3GAJFWhP8tQ50LUsxbDrcn9TzgJ10VDzdyTP
kKI4xpEDKw+xi37i+HWw1za9lyeJH+mxz/RWrfBBXw1WRwA/3do6JwWRNebWhU14
WXGHfF9ifFPf
=r8EE
-END PGP SIGNATURE End Message ---

Bug#921772: marked as done (CVE-2018-1000652)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 10:47:08 +
with message-id 
and subject line Bug#921772: fixed in jabref 3.8.1+ds-3+deb9u1
has caused the Debian Bug report #921772,
regarding CVE-2018-1000652
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
921772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jabref
Severity: grave
Tags: security

This was assigned CVE-2018-1000652:
https://github.com/JabRef/jabref/issues/4229
https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e

Cheers,
Moritz
  
--- End Message ---
--- Begin Message ---
Source: jabref
Source-Version: 3.8.1+ds-3+deb9u1

We believe that the bug you reported is fixed in the latest version of
jabref, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated jabref package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Feb 2019 20:25:26 +0100
Source: jabref
Binary: jabref
Architecture: source
Version: 3.8.1+ds-3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: gregor herrmann 
Description:
 jabref - graphical frontend to manage BibTeX and BibLaTeX databases
Closes: 921772
Changes:
 jabref (3.8.1+ds-3+deb9u1) stretch; urgency=medium
 .
   [ gregor herrmann & tony mancill ]
   * Add patch from upstream commit to fix CVE-2018-1000652: XML External
 Entity attack.
 Thanks to Moritz Muehlenhoff for the bug report. (Closes: #921772)
Checksums-Sha1:
 0c99beafca298d3e33cbb2622bdd77a3288f3421 2687 jabref_3.8.1+ds-3+deb9u1.dsc
 402c666fdac33f2010480f9b7fa50d0d4b7dae8b 46968 
jabref_3.8.1+ds-3+deb9u1.debian.tar.xz
 f33d5c897674baccf64937b7ba97c6b238409265 17056 
jabref_3.8.1+ds-3+deb9u1_amd64.buildinfo
Checksums-Sha256:
 0702d0818d255004c630b03e2ec8e5ae54a0567f450b6ffd12efa08b85c3a7fe 2687 
jabref_3.8.1+ds-3+deb9u1.dsc
 64fe6dc86b0a3fc935643984f7c7cc21185ab036ac4bdbb5e8023d5385d0230b 46968 
jabref_3.8.1+ds-3+deb9u1.debian.tar.xz
 4eb5fb999d302e3730f125482046e1ba6bd563acef3f15748f58d6e7608c35df 17056 
jabref_3.8.1+ds-3+deb9u1_amd64.buildinfo
Files:
 cb7a0f25172d6b787b7e1732532ee5ac 2687 tex optional jabref_3.8.1+ds-3+deb9u1.dsc
 a1555d07ddd7a1eab2cadcf8b37d5bbc 46968 tex optional 
jabref_3.8.1+ds-3+deb9u1.debian.tar.xz
 c5bf02ce3d4de71439f732f111cce1b1 17056 tex optional 
jabref_3.8.1+ds-3+deb9u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlyziZsUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpa48Q/9GUWzL/AbCc65IyiydFMHLD9dgfjd
66KfAOBsDSgMwyJrylZUWnD9NViD51ggssvh7zaiN9BhKeVP8ESD8f+y2VKFk9+2
FasAAwWA4EcTnLN8LnwiuStbTYZUi4txT0nLFT7GOzJ9E0e7aC6+K/MEwfpk6qn0
7Bliu8zNOcJuNgkJR9ebzYLOdmOfR1Il/NfkfCaN4EMnJeI6YGLIppN0jWAPbpbO
LL3OVaJhnF9eH2YTn0GhRMZBnynz8lL9JkS6YUvF0nNoYg0CBgfyNJakXwyPpLCD
u+O8w+nxY3MyJVfhF50SfuOlyezxC/DbC5S7v3Tg3SHAmxYY8AjVRw3AAXMJGYjM
Zmy6FBvjiHFWy/tBJcEN9g/dbB9bqyHmCqvasYot92dANC6inAT1gmjLzQLM++S/
rNThdb44OQxSw0ZcVwSSqkUf9wjXG2/c6QBMcg4KteGg5jtr01N5iMpM+JKsM0FZ
UGsG6IC5sIgKqnHD/oJjkgNuB9dnZ5bQRs5NHdKLFB6Mj33bgN+6YMWKc+TfYz7H
Ahh8ExC7a2n+iaWMEUzj17GV5P4EcFkM3IXVDu/4pWt43Wc1HTi9V2en/VUNqGa+
idB79OFuy7aiNHuPfzJuupYpoMPY+/ZuzOPIm6hV9jAGEbNggwMvwcIaNnrcpGwU
RMXt9gI9y2KEgM0=
=2+xn
-END PGP SIGNATURE End Message ---

Bug#911590: marked as done (gocode-auto-complete-el: fails to install: go-autocomplete.el:39:13:Error: Cannot open load file: No such file or directory, auto-complete)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 10:47:08 +
with message-id 
and subject line Bug#911590: fixed in gocode 20150303-3+deb9u1
has caused the Debian Bug report #911590,
regarding gocode-auto-complete-el: fails to install: 
go-autocomplete.el:39:13:Error: Cannot open load file: No such file or 
directory, auto-complete
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
911590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gocode-auto-complete-el
Version: 20150303-3
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 emacs24 (24.5+1-11+deb9u1) ...
  update-alternatives: using /usr/bin/emacs24-x to provide /usr/bin/emacs 
(emacs) in auto mode
  update-alternatives: using /usr/bin/emacs24 to provide /usr/bin/editor 
(editor) in auto mode
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install gocode-auto-complete-el for emacs24
  install/gocode-auto-complete-el: Handling install for emacsen flavor emacs24
  Loading 00debian-vars...
  
  In toplevel form:
  go-autocomplete.el:39:13:Error: Cannot open load file: No such file or 
directory, auto-complete
  ERROR: install script from gocode-auto-complete-el package failed
  dpkg: error processing package emacs24 (--configure):
   subprocess installed post-installation script returned error exit status 1

This problem only occurrs if gocode-auto-complete-el is installed
together with its dependencies in one run. If the dependencies are
installed first and gocode-auto-complete-el afterwards, everything is
fine.

This seems to be a regression introduced in the last point release in
auto-complete-el (1.3.1-2+deb9u1).

Comparing to an older log results in

@@ -1031,8 +908,8 @@
   Preparing to unpack .../151-emacs_46.1_all.deb ...^M
   Unpacking emacs (46.1) ...^M
   Selecting previously unselected package auto-complete-el.^M
-  Preparing to unpack .../152-auto-complete-el_1.3.1-2_all.deb ...^M
-  Unpacking auto-complete-el (1.3.1-2) ...^M
+  Preparing to unpack .../152-auto-complete-el_1.3.1-2+deb9u1_all.deb ...^M
+  Unpacking auto-complete-el (1.3.1-2+deb9u1) ...^M
   Selecting previously unselected package gocode.^M
   Preparing to unpack .../153-gocode_20150303-3+b1_amd64.deb ...^M
   Unpacking gocode (20150303-3+b1) ...^M
@@ -1206,12 +1083,6 @@
   Setting up emacs24 (24.5+1-11+deb9u1) ...^M
   update-alternatives: using /usr/bin/emacs24-x to provide /usr/bin/emacs 
(emacs) in auto mode^M
   update-alternatives: using /usr/bin/emacs24 to provide /usr/bin/editor 
(editor) in auto mode^M
-  Install auto-complete-el for emacs24^M
-  install/auto-complete: Handling install for emacsen flavor emacs24^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/auto-complete-config.elc^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/auto-complete.elc^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/fuzzy.elc^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/popup.elc^M
   Install emacsen-common for emacs24^M
   emacsen-common: Handling install of emacsen flavor emacs24^M
   Wrote /etc/emacs24/site-start.d/00debian-vars.elc^M
@@ -1219,3699 +1090,969 @@
   Install gocode-auto-complete-el for emacs24^M
   install/gocode-auto-complete-el: Handling install for emacsen flavor 
emacs24^M
   Loading 00debian-vars...^M
-  Wrote 
/usr/share/emacs24/site-lisp/gocode-auto-complete-el/go-autocomplete.elc^M
-  Setting up emacs (46.1) ...^M
-  Setting up auto-complete-el (1.3.1-2) ...^M
-  Install auto-complete-el for emacs^M
-  Install auto-complete-el for emacs24^M
-  install/auto-complete: Handling install for emacsen flavor emacs24^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/auto-complete-config.elc^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/auto-complete.elc^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/fuzzy.elc^M
-  Wrote /usr/share/emacs24/site-lisp/auto-complete/popup.elc^M
-  Setting up gocode-auto-complete-el (20150303-3) ...^M
-  ERROR: gocode-auto-complete-el is broken - called emacs-package-install as a 
new-style add-on, but has no compat file.^M
-  Install auto-complete-el for emacs^M
-  Install auto-complete-el for emacs24^M
-  

Bug#927122: ruby2.5: Rinda::TestRingFinger test_make_socket_ipv4_multicast Errno::ENETUNREACH: Network is unreachable

[Ritesh Raj Sarraf]

Package: ruby2.5
Version: 2.5.5-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

The current ruby2.5 package in Buster/Unstable fails to build from
scratch. It fails in some of the tests that depend on network
availability.

The tests are already disabled in
debian/tests/excludes/any/TestRingFinger.rb
debian/tests/excludes/any/TestRingServer.rb

but are not effective.

With this patch, the same tests are disabled in test/excludes/ and they
are effective.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (990, 'testing'), (100, '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_USER, TAINT_WARN, 
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 ruby2.5 depends on:
ii  libc6 2.28-8
ii  libgmp10  2:6.1.2+dfsg-4
ii  libruby2.52.5.5-1
ii  rubygems-integration  1.11

Versions of packages ruby2.5 recommends:
ii  fonts-lato2.0-2
ii  libjs-jquery  3.3.1~dfsg-1

ruby2.5 suggests no packages.

-- no debconf information
The tests are marked excluded in debian/tests/excludes/any/TestRing*.rb
But they still get executed which results in the build failure.

In salsa commit:
https://salsa.debian.org/ruby-team/ruby/commit/2943f7b15ac47c9110b5f8bb5a2346eadefdb83f
the tests were explicitly disabled in tests/excludes/ in the upstream sources,
which works and is exactly this patch does.

There is also an upstream bug report about these tests failing but without any
resolution so far.
https://bugs.ruby-lang.org/issues/13864
Index: ruby2.5-2.5.5/test/excludes/Rinda/TestRingFinger.rb
===
--- /dev/null   1970-01-01 00:00:00.0 +
+++ ruby2.5-2.5.5/test/excludes/Rinda/TestRingFinger.rb 2019-04-15 
14:38:46.343954009 +0530
@@ -0,0 +1,3 @@
+reason = "Network access not allowed during build in Debian"
+exclude :test_make_socket_ipv4_multicast, reason
+exclude :test_make_socket_ipv4_multicast_hops, reason
Index: ruby2.5-2.5.5/test/excludes/Rinda/TestRingServer.rb
===
--- /dev/null   1970-01-01 00:00:00.0 +
+++ ruby2.5-2.5.5/test/excludes/Rinda/TestRingServer.rb 2019-04-15 
14:38:46.343954009 +0530
@@ -0,0 +1,3 @@
+reason = "Network access not allowed during build in Debian"
+exclude :test_make_socket_ipv4_multicast, reason
+exclude :test_ring_server_ipv4_multicast, reason
Index: ruby2.5-2.5.5/test/excludes/TestRinda.rb
===
--- /dev/null   1970-01-01 00:00:00.0 +
+++ ruby2.5-2.5.5/test/excludes/TestRinda.rb2019-04-15 14:38:46.343954009 
+0530
@@ -0,0 +1,5 @@
+reason = "Network access not allowed during build in Debian"
+exclude :test_make_socket_ipv4_multicast, reason
+exclude :test_make_socket_ipv4_multicast_hops, reason
+exclude :test_make_socket_ipv4_multicast, reason
+exclude :test_ring_server_ipv4_multicast, reason

Bug#917688: marked as done (umlet: FTBFS: Baselet/src/com/baselet/control/Main.java:26: error: package org.apache.commons.io.filefilter does not exist)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 09:39:24 +
with message-id 
and subject line Bug#915890: fixed in umlet 13.3-1.2
has caused the Debian Bug report #915890,
regarding umlet: FTBFS: Baselet/src/com/baselet/control/Main.java:26: error: 
package org.apache.commons.io.filefilter does not exist
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
915890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: umlet
Version: 13.3-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> test -d eclipse-plugin-source || mkdir eclipse-plugin-source
> # move unused source code out of the way
> mv Baselet/src/com/baselet/plugin/ eclipse-plugin-source/ || true
> mv Baselet/src/com/baselet/gui/eclipse/ eclipse-plugin-source/ || true
> mv: cannot stat 'Baselet/src/com/baselet/gui/eclipse/': No such file or 
> directory
> jh_build --no-javadoc -o"-encoding utf8"  --main=com.baselet.control.Main 
> umlet.jar Baselet/src BaseletElements/src
> find Baselet/src BaseletElements/src -name *.java -and -type f -print0 | 
> xargs -s 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp 
> /usr/share/java/ecj.jar:/usr/share/java/batik-all.jar:/usr/share/java/fop.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/net.sourceforge.jlibeps.jar:/usr/share/java/javax.mail.jar:/usr/share/java/itext5.jar:/usr/share/java/jsyntaxpane.jar:/usr/share/java/rsyntaxtextarea.jar:/usr/share/java/autocomplete.jar:/usr/share/java/javaparser.jar:/usr/share/java/commons-io-java:debian/_jh_build.umlet
>  -d debian/_jh_build.umlet -source 1.7 -target 1.7 -encoding utf8
> warning: [options] bootstrap class path not set in conjunction with -source 7
> Baselet/src/com/baselet/control/Main.java:26: error: package 
> org.apache.commons.io.filefilter does not exist
> import org.apache.commons.io.filefilter.WildcardFileFilter;
>^
> Baselet/src/com/baselet/generator/java/bcel/BcelMethod.java:3: error: package 
> org.apache.bcel.classfile does not exist
> import org.apache.bcel.classfile.Method;
> ^
> Baselet/src/com/baselet/generator/java/bcel/BcelMethod.java:4: error: package 
> org.apache.bcel.generic does not exist
> import org.apache.bcel.generic.Type;
>   ^
> Baselet/src/com/baselet/generator/java/bcel/BcelAccessible.java:3: error: 
> package org.apache.bcel.classfile does not exist
> import org.apache.bcel.classfile.FieldOrMethod;
> ^
> Baselet/src/com/baselet/generator/java/bcel/BcelMethod.java:8: error: cannot 
> find symbol
>   private final Method method;
> ^
>   symbol:   class Method
>   location: class BcelMethod
> Baselet/src/com/baselet/generator/java/bcel/BcelMethod.java:12: error: cannot 
> find symbol
>   public BcelMethod(Method method, String className) {
> ^
>   symbol:   class Method
>   location: class BcelMethod
> Baselet/src/com/baselet/generator/java/bcel/BcelAccessible.java:11: error: 
> cannot find symbol
>   public BcelAccessible(FieldOrMethod accessible) {
> ^
>   symbol:   class FieldOrMethod
>   location: class BcelAccessible
> Baselet/src/com/baselet/generator/java/bcel/BcelField.java:3: error: package 
> org.apache.bcel.classfile does not exist
> import org.apache.bcel.classfile.Field;
> ^
> Baselet/src/com/baselet/generator/java/bcel/BcelField.java:7: error: cannot 
> find symbol
>   private Field field;
>   ^
>   symbol:   class Field
>   location: class BcelField
> Baselet/src/com/baselet/generator/java/bcel/BcelField.java:9: error: cannot 
> find symbol
>   public BcelField(Field field) {
>^
>   symbol:   class Field
>   location: class BcelField
> Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:3: error: 
> package org.apache.bcel.classfile does not exist
> import org.apache.bcel.classfile.ClassParser;
> ^
> Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:4: error: 
> package org.apache.bcel.classfile does not exist
> import org.apache.bcel.classfile.Field;
> ^
> Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:5: error: 
> package org.apache.bcel.classfile does not 

Bug#915890: marked as done (umlet FTBFS: error: package org.apache.bcel.classfile does not exist)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 09:39:24 +
with message-id 
and subject line Bug#915890: fixed in umlet 13.3-1.2
has caused the Debian Bug report #915890,
regarding umlet FTBFS: error: package org.apache.bcel.classfile does not exist
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
915890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: umlet
Version: 13.3-1.1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/umlet.html

...
 debian/rules build
test -d eclipse-plugin-source || mkdir eclipse-plugin-source
# move unused source code out of the way
mv Baselet/src/com/baselet/plugin/ eclipse-plugin-source/ || true
mv Baselet/src/com/baselet/gui/eclipse/ eclipse-plugin-source/ || true
mv: cannot stat 'Baselet/src/com/baselet/gui/eclipse/': No such file or 
directory
jh_build --no-javadoc -o"-encoding utf8"  --main=com.baselet.control.Main 
umlet.jar Baselet/src BaseletElements/src
find Baselet/src BaseletElements/src -name *.java -and -type f -print0 | xargs 
-s 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/ecj.jar:/usr/share/java/batik-all.jar:/usr/share/java/fop.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/net.sourceforge.jlibeps.jar:/usr/share/java/javax.mail.jar:/usr/share/java/itext5.jar:/usr/share/java/jsyntaxpane.jar:/usr/share/java/rsyntaxtextarea.jar:/usr/share/java/autocomplete.jar:/usr/share/java/javaparser.jar:/usr/share/java/commons-io-java:debian/_jh_build.umlet
 -d debian/_jh_build.umlet -source 1.7 -target 1.7 -encoding utf8
warning: [options] bootstrap class path not set in conjunction with -source 7
Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:3: error: 
package org.apache.bcel.classfile does not exist
import org.apache.bcel.classfile.ClassParser;
^
Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:4: error: 
package org.apache.bcel.classfile does not exist
import org.apache.bcel.classfile.Field;
^
Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:5: error: 
package org.apache.bcel.classfile does not exist
import org.apache.bcel.classfile.JavaClass;
^
Baselet/src/com/baselet/generator/java/bcel/BcelJavaClass.java:6: error: 
package org.apache.bcel.classfile does not exist
import org.apache.bcel.classfile.Method;
^
--- End Message ---
--- Begin Message ---
Source: umlet
Source-Version: 13.3-1.2

We believe that the bug you reported is fixed in the latest version of
umlet, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated umlet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Apr 2019 10:28:06 +0200
Source: umlet
Architecture: source
Version: 13.3-1.2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Mesing 
Changed-By: Emmanuel Bourg 
Closes: 651478 915890 923390
Changes:
 umlet (13.3-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Added the missing dependency on libbcel-java (Closes: #915890)
   * Fixed the inclusion of commons-io.jar in the classpath
   * Replaced the old Debian menu entry with a .desktop file.
 Thanks to Rui Maciel (Closes: #651478, #923390)
   * Fixed the misplaced Homepage field
Checksums-Sha1:
 90b8fecc6584320a6ae41ffbfb0b329fd1805070 1981 umlet_13.3-1.2.dsc
 f43946b420426027086cd5ff171c42d813f83340 7716 umlet_13.3-1.2.debian.tar.xz
 9f6b7d14c23af5996b0c2e61ebb749105fef40da 13540 umlet_13.3-1.2_source.buildinfo
Checksums-Sha256:
 d828459e611b8e328ba0ec301cadbfa32e4215e5116e9d28e347719e6501a5b8 1981 
umlet_13.3-1.2.dsc
 a2ed32810657f77ea3a793dda30c346adad9aeb89c4395168722b1f07e09ee9c 7716 
umlet_13.3-1.2.debian.tar.xz
 9f23148384fe85c00f4be6d895c2edd21801efb83d1c4ad8df1bd01d6c63e86a 13540 
umlet_13.3-1.2_source.buildinfo
Files:
 8da36e4dc11ee7189e8befccf3a836d2 1981 devel extra umlet_13.3-1.2.dsc
 

Bug#927065: marked as done (perlbrew versions before 0.84 don't find perl release tarballs because of URL changes)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 07:59:10 +
with message-id 
and subject line Bug#927065: fixed in perlbrew 0.78-1+deb9u1
has caused the Debian Bug report #927065,
regarding perlbrew versions before 0.84 don't find perl release tarballs 
because of URL changes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perlbrew
Version: 0.71-1
Severity: grave
Tags: patch upstream fixed-upstream
Justification: renders package unusable
Forwarded: https://github.com/gugod/App-perlbrew/pull/618

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


perlbrew downloads and builds perl. Due to changes in the CPAN URLs
this fails for versions before 0.84.

Trivial upstream fix:
https://github.com/gugod/App-perlbrew/commit/0983d7abacbe17180b58e4a37b2332fec86affac


I'm going to prepare an upload for stretch-proposed-upates.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlyzR+tfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaujhAApt6WDZRZmdaLRRIiqoDJ2030CmO+ZN3FXQOGXvOT00r4BUIVFX2WbwWt
oY+2LhBL7wnD0gvK4LKfRmfxZ5tq4jj7mP9nIjyxXrvyD6VFvMraKUFUP8TK//k4
1smReUo5AzCJWkqRgZQyvBaQWQsOCMJXc8xkvWAPnxedSGLt46QWeaK/+kxbtq/6
VhvkCabIUPBumtslqvyVVe5Xgei4XyViHGiEC7YVd9o+fIA/iw8UKQqJisN+P/a4
dzg7XhqAtcLFUPd6GRyESNgYdlkIydxtS/rn+QDag5Qb9ZWg045pUApAEocjFrJz
O6KswR3chteWcnJnnhO9kLqvaNJ3kLdaqovHTUUcZ7x6Kb7J9Fa0rnfJp3xscS8Y
tXM+u9s5pLDyOUNO+4lXmsXATBid5gESelbSWgZ3JpBUcUMBj1dWm32g+T1RLrfg
5yb4ps+MNt7WL4reG/z7ysmIrXw5adwdqgz6oPik0UeM+hjL03Js49E5QksViKu9
2V4W9AHGrmZ74AqNcvpBPddMIWccdrD3We+s1meq1HKNEo2Tuy45Upoo2o5011xe
ytcapQ8p37UzlvkPs6+wbFxRCmbMM3Ee3GuchkuI7qjI3usW6+bWd6lDUoALrw6p
tJp0eM7Bw8gZSXdqL++xmju+K58z1T0aAnSxanTQliJ9xEHDYl4=
=nVI0
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: perlbrew
Source-Version: 0.78-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
perlbrew, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated perlbrew package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Apr 2019 17:08:18 CEST
Source: perlbrew
Binary: 
Architecture: source
Version: 0.78-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
Closes: 927065
Changes:
 perlbrew (0.78-1+deb9u1) stretch; urgency=medium
 .
   * Backport upstream fix for CPAN URLs.
 CPAN URLs have changed to use HTTPS, which makes perlbrew fail to detect
 perl tarballs. This patch changes the regexp to allow both HTTP and HTTPS.
 (Closes: #927065)
Checksums-Sha256: 
 c9ba78059b3bc843cdb912996c1c8f966f71eef7498d202d9dec9fa45e16b84e 2494 
perlbrew_0.78-1+deb9u1.dsc
 a5bb5d7d5187332fe816bb0403d3f6f38c800df463ec7bfafc85898d805b63e1 5740 
perlbrew_0.78-1+deb9u1.debian.tar.xz
 a57d53e47c8dd3e706a02fb4fd09a86a2c583913ca3c80240129ba661990892b 7713 
perlbrew_0.78-1+deb9u1_sourceonly.buildinfo
Checksums-Sha1: 
 12344c3c70c5c88a357d74f19bf771d4863c429d 2494 perlbrew_0.78-1+deb9u1.dsc
 1ca7df25bf0eefc2f8bd5dbaa20502468a634381 5740 
perlbrew_0.78-1+deb9u1.debian.tar.xz
 e115a1077d55f27c083d134f8a1335b9edb384b1 7713 
perlbrew_0.78-1+deb9u1_sourceonly.buildinfo
Files: 
 6f355e881058632b0c37222594a119f0 2494 perl optional perlbrew_0.78-1+deb9u1.dsc
 55515a78b242709d7929a0713a255fbd 5740 perl optional 
perlbrew_0.78-1+deb9u1.debian.tar.xz
 6816403b272c67d821289fbcfa223775 7713 - - 
perlbrew_0.78-1+deb9u1_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlyzTONfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaVCg/7BW3Ta7AxenTxGWMnczz/0ECvXKFziI6uJJgWvrt5kx5TzUSALrOaFeVg
unvwbyvwdCEtLW8LFfPNDUtUz/gXocUBTgZiQjrAsQl7OFhkL/gJDiKvdApi0XTC

Bug#917485: marked as done (ckermit: relax openssl version check or tighten libssl1.x.y dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 07:59:10 +
with message-id 
and subject line Bug#917485: fixed in ckermit 302-5.3+deb9u1
has caused the Debian Bug report #917485,
regarding ckermit: relax openssl version check or tighten libssl1.x.y 
dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
917485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ckermit
Version: 302-5.3
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

Please rebuild C-Kermit against the new OpenSSL in Stretch.  Currently all 
SSL/TLS functionality in C-Kermit is disabled due to detecting mismatching 
libraries.


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

Kernel: Linux 4.9.0-8-arm64 (SMP w/4 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)

Versions of packages ckermit depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3
ii  libcomerr2 1.43.4-2
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libk5crypto3   1.15-1+deb9u1
ii  libkrb5-3  1.15-1+deb9u1
ii  libncurses56.0+20161126-1+deb9u2
ii  libpam0g   1.1.8-3.6
ii  libssl1.0.21.0.2q-1~deb9u1
ii  libtinfo5  6.0+20161126-1+deb9u2

Versions of packages ckermit recommends:
ii  openbsd-inetd [inet-superserver]  0.20160825-2
ii  openssh-client [ssh-client]   1:7.4p1-10+deb9u4

ckermit suggests no packages.

-- debconf information:
  ckermit/iksd-anon: false
  ckermit/iksd-no-inetd:
  ckermit/iksd: false
  ckermit/iksd-anondir: /home/ftp
--- End Message ---
--- Begin Message ---
Source: ckermit
Source-Version: 302-5.3+deb9u1

We believe that the bug you reported is fixed in the latest version of
ckermit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
ckermit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Feb 2019 23:35:55 +0100
Source: ckermit
Architecture: source
Version: 302-5.3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Ian Beckwith 
Changed-By: Sebastian Andrzej Siewior 
Closes: 917485
Changes:
 ckermit (302-5.3+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Drop check openssl compile time version vs runtime version
 (Closes: #917485).
Checksums-Sha1:
 5d9b9d7b15fc1d3f5525e0329b8014db499234dd 1751 ckermit_302-5.3+deb9u1.dsc
 dc64d9c06159adcc64aa93a78ce8c66755491d13 25752 
ckermit_302-5.3+deb9u1.debian.tar.xz
 8c302e253676156553f961525c20162c07c4c058 5081 
ckermit_302-5.3+deb9u1_source.buildinfo
Checksums-Sha256:
 359aab125e3b7b4454487f9c749b23f4b6202be43bc1555df0631aed888ba76e 1751 
ckermit_302-5.3+deb9u1.dsc
 ae4cb6cf5344970ad17c18ed5229e8d8266b4127618e9fb842801b8e75d19177 25752 
ckermit_302-5.3+deb9u1.debian.tar.xz
 83dc741a265174529c61359b71f4d04ae633cf6e0a6307e4f51672c5f694230f 5081 
ckermit_302-5.3+deb9u1_source.buildinfo
Files:
 94432532904b7d8aab34412caa89b073 1751 comm extra ckermit_302-5.3+deb9u1.dsc
 2d628825e0f057b180108fd1e5e00c1f 25752 comm extra 
ckermit_302-5.3+deb9u1.debian.tar.xz
 ee54c053cab9b29a6ddf3260a9bf84fb 5081 comm extra 
ckermit_302-5.3+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHMBAEBCgA2FiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAlyzEBwYHHNlYmFzdGlh
bkBicmVha3BvaW50LmNjAAoJEAVkHxdXEvpbPQEMAInUlw85Jio+yoR6/jDbpAgX
Kw6LNsGjeL1Tgy3b78TtNNoI1qNYiW9Hp0Z2i0tIwfAkBP/MJlDvRUwRmQ1w1enD
gaEUUjsex0IBZnYe4qtW0QyWoJTqrwdajt9iIEnxk7ImNnXhUXRXeE6qDg0pCu20
G691MrKAgM7/GwloAFU/fcqs1D/Gf9wDMzF1zRJKEMPMkv6Y8JqLrBOuEddNB1U0
6Ui2bSKSPhbNiB1gNlDd+fdWq0Uww9i9hfF5BjiIrIcLMvEVns3AcHICR1tAaIiB
4apnr9p1Odvk0BmxXjpCSl/xXXNYgdlkek0wWV1hcWHKD0cHtUvoVrmEiCTPZaFz
ZjET/KHhbu/dVt6N61Hw+1Rq92D5r2CWVI0McUHmUfls7CV31TxbQcBQ30PvTQdo

Bug#922050: marked as done (runc: CVE-2019-5736)

[Debian Bug Tracking System]

Your message dated Mon, 15 Apr 2019 07:59:11 +
with message-id 
and subject line Bug#922050: fixed in runc 0.1.1+dfsg1-2+deb9u1
has caused the Debian Bug report #922050,
regarding runc: CVE-2019-5736
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
922050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: runc
Version: 1.0.0~rc6+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerability was published for runc.

CVE-2019-5736[0]:
runc container breakout

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-5736
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736
[1] 
https://github.com/opencontainers/runc/commit/0a8e4117e7f715d5fbeef398405813ce8e88558b
[2] https://www.openwall.com/lists/oss-security/2019/02/11/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: runc
Source-Version: 0.1.1+dfsg1-2+deb9u1

We believe that the bug you reported is fixed in the latest version of
runc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 922...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated runc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Mar 2019 00:50:07 +0800
Source: runc
Binary: runc golang-github-opencontainers-runc-dev
Architecture: source
Version: 0.1.1+dfsg1-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Shengjing Zhu 
Description:
 golang-github-opencontainers-runc-dev - Open Container Project - develpoment 
files
 runc   - Open Container Project - runtime
Closes: 922050
Changes:
 runc (0.1.1+dfsg1-2+deb9u1) stretch; urgency=medium
 .
   * Team upload.
   * Add patch to address CVE-2019-5736 (Closes: #922050)
Checksums-Sha1:
 97aadeec1841611882ce2534b698d1e8886a 2276 runc_0.1.1+dfsg1-2+deb9u1.dsc
 3d83d5e1531af9a1e6b80efa214b9f59059a21c0 11380 
runc_0.1.1+dfsg1-2+deb9u1.debian.tar.xz
 bcab03775a5aeed93a101f767f80024d7ed19dfc 8274 
runc_0.1.1+dfsg1-2+deb9u1_amd64.buildinfo
Checksums-Sha256:
 408033402b78140618842f52bb921228946823bfa9a17daf63908ea44a77bc33 2276 
runc_0.1.1+dfsg1-2+deb9u1.dsc
 07d7e810466b25196a3a0c1bf4d4c7661dc95eb225d251646873440dc70118fe 11380 
runc_0.1.1+dfsg1-2+deb9u1.debian.tar.xz
 0bb0ca1944b887d37c21b1f8852564ca211510f56635f867e19afe72031cb6a1 8274 
runc_0.1.1+dfsg1-2+deb9u1_amd64.buildinfo
Files:
 51c59877e0a45a9e1e9a74e7eb50f2a3 2276 devel extra runc_0.1.1+dfsg1-2+deb9u1.dsc
 39085bd827deb73cc1f3fef6ded47e65 11380 devel extra 
runc_0.1.1+dfsg1-2+deb9u1.debian.tar.xz
 00a8a765a6122edffdb953a50a98934b 8274 devel extra 
runc_0.1.1+dfsg1-2+deb9u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlyy84YQHHpoc2pAZGVi
aWFuLm9yZwAKCRA40A8AGL4+NQX5B/0btthlL6Ba+uKq+2HG4l/55R1AEaekrl8T
1bAd8eu3hzu3hE5KV+2I7O1krUwVlR5BOt1rDgn3m7F5yEZHKyuYF9JWbKrYS1PK
BcHUgcSEF5kh9jUtW0RY5XN1ipENgrcA6AmiiFRn9w66WQdPyyAERVqOKgcJnHq1
YMFCWx/myTmLtyYv+kHa+YBO0OFk+7zs7UbsaNyji09rj/ioQOmAm7HlDsg5pc8P
cSF5Avab4VmVHQqRAtw5gB5zvhG7XzTJJ4L1lhAvMgZSHV/q8oUcQIZ2L/FqJqti
S1+seF0pg4M9FNB0/xwzKKBHOaeaC5T1NcsBrg5xrdCuqjdMTozT
=QX4f
-END PGP SIGNATURE End Message ---

Bug#919978: diaspora-installer package fails to install

[Pirate Praveen]

On Sat, 13 Apr 2019 16:18:34 +0200 Andreas Beckmann  wrote:
> Control: severity -1 serious
> 
> On Mon, 18 Feb 2019 13:02:56 +0530 Pirate Praveen
>  wrote:
> > > Installing gems with rubygems ...
> > > sh: 1: bundle: not found
> 
> I can reproduce that in piuparts.
> 
> > It seems /usr/local/bin is not in your path when you just start bash. It
> > worked with lxc-attach.
> 
> If it does not work with the default PATH setting ... its RC.

This seems to be happening with bundler 2.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: tagging 921704

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # new mercurial will not be in buster
> tags 921704 + buster-ignore
Bug #921704 [src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
Added tag(s) buster-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fix versions for 925950

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # use source package, as that seems to be what version tracking wants
> notfixed 925950 cross-gcc-dev/230
Bug #925950 {Done: Helmut Grohne } [cross-gcc-dev] patches 
no longer apply for gcc-8 and gcc-9
The source cross-gcc-dev and version 230 do not appear to match any binary 
packages
No longer marked as fixed in versions cross-gcc-dev/230.
> fixed 925950 cross-gcc/230
Bug #925950 {Done: Helmut Grohne } [cross-gcc-dev] patches 
no longer apply for gcc-8 and gcc-9
Marked as fixed in versions cross-gcc/230.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
925950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems