Bug#892784: marked as done (zaqar FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 09:01:32 +0100
with message-id <5602a94f-2175-5986-0769-f713069a6...@debian.org>
and subject line Done
has caused the Debian Bug report #892784,
regarding zaqar FTBFS: test failures
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.)


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

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

...
==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_2___
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_2___
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_4__fail_
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_4__fail_
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_get_claim_nonexistent_queue
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_get_claim_nonexistent_queue
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_3__
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_3__
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_messages.MessagesBaseTest.test_post_invalid_ttl
zaqar.t

Processed: Re: Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Debian Bug Tracking System]

Processing control commands:

> found -1 239-15
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Marked as found in versions systemd/239-15.

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

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Axel Beckert]

Control: found -1 239-15

Hi Michael,

Michael Biebl wrote:
> Am 12.01.19 um 01:02 schrieb Axel Beckert:
> > Control: reopen -1
> > Control: found -1 240-3
> 
> > *sigh* I'm sorry to say, but it just happened again with udev 240-3
> > and kernel 4.20-1~exp1.
> 
> Would be good to know, if it also happens with 239-15 or if it's caused
> by some other update.

I just downloaded udev and libudev1 239-15 from
https://snapshot.debian.org/, installed it and immediately afterwards
ran "udevadm control --reload-rules" and everything was gone again.
(Was running under kernel 4.20-1~exp1.)

After that I rebooted into 4.20-1~exp1 with the downgraded udev again,
ran "udevadm control --reload-rules" directly after reboot and nothing
(unexpected) happened.

Then I started to write this mail, doing not much more than logging in
on the text console (despite X was running) using zsh, running
ssh-agent, ssh-add and then ssh via autossh to connect to a screen
session on some other host to write the mail with mutt.

After about 20 minutes of uptime I was about to send that mail and
thought, I should just try running "udevadm control --reload-rules"
once again: And it killed all processes again -- systemd-udevd has
been started again, too:

~ # ps auxwww | fgrep udev
root 10696  0.0  0.0  13152  3592 ?S08:27   0:00 
/lib/systemd/systemd-udevd
root 11582  0.0  0.0   8144   892 tty1 R+   08:33   0:00 grep -F 
--color=auto udev
~ # uptime
 08:33:49 up 25 min,  2 users,  load average: 0.07, 0.15, 0.34

Unfortunately there is not much in the syslog (had to start rsyslog
first again, too):

Jan 15 08:37:16 c6 kernel: [ 1717.930890] printk: systemd-udevd: 159 output 
lines suppressed due to ratelimiting

I though didn't get rsyslog to drop the rate-limiting and I'm a little
bit in a hurry at the moment.

Will report back later.

I must admit that I also had one crash/process killing yesterday where
I can't say what triggered it. aptitude just finished starting up in
TUI mode (inside screen started via ssh from remote) and I was
starting to browse through the package list while the connection
suddenly was lost (likely due to a killed sshd).

Some other facts gathered recently:

* With udev 239-15 the bootup lag is gone even without the "sleep 5".

* The "sleep 5" helped on another box (EeePC 900A with sysvinit) where
  drivers weren't loaded anymore and had to be specified manually in
  /etc/modules until the "sleep 5" was added.
* memtest86 and memtest86+ just show an empty screen. Will try again
  with grub's graphical mode disabled just to make sure the issue is
  not triggered by some memory fault. Question would be then why I
  could (within a reboot where it happened) reliably reproduce the
  issue again and again. Will report any findings on this front.
* As alternative I ran memtester for one night, no issues found. (Not
  sure if it was able to test everything as the affected box has 64 GB
  of RAM.)
* If the issue happens while using X, there's no chance to switch back
  to the text console with the getty to login again. The machine needs
  a hard reboot via reset or power button then.

> Tbh, udevd or udevadm control --reload killing all processes, sounds
> pretty strange.

Definitely.

> Can you also try to run udevd in debug mode to get a log from udevd (see
> /etc/udev/udev.conf) and also an strace of the udevadm command.

I think I alread sent the strace, but forgot the debug mode. Enabled
that when starting to write this mail, but it's currently caught by
rsyslogd's rate-limiting, see above.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Petter Reinholdtsen]

Steinar Gunderson suggested to me the pthreads message from cmake is
misleading, and the real problem is that libxrandr-dev is not installed.
Can you try again with this library installed to see if it solve the
problem for you?

-- 
Happy hacking
Petter Reinholdtsen

Bug#919356: dwarves-dfsg: Copyright/licensing is unclear

[Domenico Andreoli]

Package: dwarves-dfsg
Severity: grave

This file is without license info:

 - hash.h

These are also without copyright info:

 - btf_encoder.c
 - btf_encoder.h
 - ctf.h
 - libbtf.c
 - libbtf.h
 - libctf.c
 - libctf.h

Though the detailed analysis is not yet complete, it's clear that the
copyright/licensing situation does not satisfy DFSG.

-- 
3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13


signature.asc
Description: PGP signature

Bug#913649: should not ship with buster

[Sébastien Villemot]

Dear Ivo,

Le samedi 12 janvier 2019 à 15:51 +0100, Ivo De Decker a écrit :

> On Tue, Nov 13, 2018 at 03:42:02PM +0100, Sébastien Villemot wrote:
> > common-lisp-controller is obsolete, and should not ship with
> > buster. It has
> > been superseded by ASDF.
> 
> There are still quite some packages that depend on common-lisp-
> controller, so
> this will probably have to wait till after buster.

Thanks. I am aware of that. Quite a few reverse dependencies have
already been fixed (either by the maintainer or by myself).

The remaining ones have very low popcon, have not been uploaded for
ages, and their maintainers did not respond to my emails.

So my intention is to let the autoremovals from buster happen
automatically. Removals from sid will indeed have to wait until later.

P.S.: I'm surprised that cl-speech-dispatcher pops up in your list of
broken reverse depends, because it has been fixed.

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#919362: lua5.3 ftbfs in unstable

[Matthias Klose]

Package: src:lua5.3
Version: 5.3.3-1.1
Severity: serious
Tags: sid buster

lua5.3 ftbfs in unstable (amd64 only apparently):

dh binary
   dh_testroot
   dh_prep
   debian/rules override_dh_auto_install
make[1]: Entering directory '/home/packages/tmp/lua5.3-5.3.3'
# pkgconfig
mkdir -p
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig
echo "prefix=/usr" >
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3.pc
echo "major_version=5.3" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3.pc
echo "version=5.3.3" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3.pc
echo "lib_name_include=lua5.3" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3.pc
echo "deb_host_multiarch=x86_64-linux-gnu" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3.pc
cat debian/lua.pc.in >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3.pc
ln -s lua5.3.pc
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua-5.3.pc
ln -s lua5.3.pc
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua53.pc
echo "prefix=/usr" >
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-c++.pc
echo "major_version=5.3" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-c++.pc
echo "version=5.3.3" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-c++.pc
echo "lib_name_include=lua5.3" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-c++.pc
echo "deb_host_multiarch=x86_64-linux-gnu" >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-c++.pc
cat debian/lua-c++.pc.in >>
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-c++.pc
ln -s lua5.3-c++.pc
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua-5.3-c++.pc
ln -s lua5.3-c++.pc
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/lua53-c++.pc
# manpage
cat doc/lua.1  | sed 's/TH LUA 1/TH LUA5.3 1/' > doc/lua5.3.1
cat doc/luac.1 | sed 's/TH LUAC 1/TH LUAC5.3 1/' > doc/luac5.3.1
# multiarch
mkdir -p 
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/include/x86_64-linux-gnu/
cp src/lua5.3-deb-multiarch.h
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/include/x86_64-linux-gnu/
/usr/bin/make install
make[2]: Entering directory '/home/packages/tmp/lua5.3-5.3.3'
cd src && mkdir -p /home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/bin
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/include/lua5.3/
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/share/man/man1
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/share/lua/5.3
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/lib/x86_64-linux-gnu/lua/5.3
cd src && install -p -m 0755 lua5.3 luac5.3
/home/packages/tmp/lua5.3-5.3.3/debian/tmp/usr/bin
install: cannot stat 'lua5.3': No such file or directory
install: cannot stat 'luac5.3': No such file or directory
make[2]: *** [Makefile:65: install] Error 1
make[2]: Leaving directory '/home/packages/tmp/lua5.3-5.3.3'
make[1]: *** [debian/rules:66: override_dh_auto_install] Error 2
make[1]: Leaving directory '/home/packages/tmp/lua5.3-5.3.3'
make: *** [debian/rules:29: binary] Error 2

Bug#919364: lua5.1 ftbfs in unstable

[Matthias Klose]

Package: src:lua5.1
Version: 5.1.5-8.1
Severity: serious
Tags: sid buster

lua5.1 ftbfs in unstable:

libtool --quiet --tag=CXX --mode=link g++ -version-info 0:0:0 \
-rpath  -Wl,--version-script,../debian/version-script -o
liblua5.1-c++.la lapi-c++.lo lcode-c++.lo ldebug-c++.lo ldo-c++.lo ldump-c++.lo
lfunc-c++.lo lgc-c++.lo llex-c++.lo lmem-c++.lo lobject-c++.lo lopcodes-c++.lo
lparser-c++.lo lstate-c++.lo lstring-c++.lo ltable-c++.lo ltm-c++.lo
lundump-c++.lo lvm-c++.lo lzio-c++.lo lauxlib-c++.lo lbaselib-c++.lo
ldblib-c++.lo liolib-c++.lo lmathlib-c++.lo loslib-c++.lo ltablib-c++.lo
lstrlib-c++.lo loadlib-c++.lo linit-c++.lo -lm -ldl
libtool --quiet --tag=CC --mode=compile gcc -c -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/home/packages/tmp/lua5.1-5.1.5=.
-fstack-protector-strong -Wformat -Werror=format-security -DLUA_USE_LINUX lua.c
libtool --quiet --tag=CC --mode=link gcc
-Wl,--version-script,../debian/version-script -static -Wl,-E -o lua5.1 lua.o
liblua5.1.la -lreadline -Wl,-z,relro
libtool --quiet --tag=CC --mode=compile gcc -c -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/home/packages/tmp/lua5.1-5.1.5=.
-fstack-protector-strong -Wformat -Werror=format-security -DLUA_USE_LINUX luac.c
libtool --quiet --tag=CC --mode=compile gcc -c -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/home/packages/tmp/lua5.1-5.1.5=.
-fstack-protector-strong -Wformat -Werror=format-security -DLUA_USE_LINUX 
print.c
libtool --quiet --tag=CC --mode=link gcc -static -o luac5.1 luac.o print.o
liblua5.1.la
make[3]: Leaving directory '/home/packages/tmp/lua5.1-5.1.5/src'
src/lua5.1 test/hello.lua
make[2]: src/lua5.1: Command not found
make[2]: *** [Makefile:142: debian_test] Error 127
make[2]: Leaving directory '/home/packages/tmp/lua5.1-5.1.5'
make[1]: *** [debian/rules:53: override_dh_auto_test] Error 2
make[1]: Leaving directory '/home/packages/tmp/lua5.1-5.1.5'
make: *** [debian/rules:28: build] Error 2

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

[Emilio Pozuelo Monfort]

Package: lintian
Version: 2.5.121

Hi lintian maintainers,

On 15/01/2019 06:03, Cyril Brulebois wrote:
> Control: severity -1 grave
> Control: tag -1 patch
> 
> Cyril Brulebois  (2019-01-15):
>> For some reasons, libtool and its manpage (from the libtool-bin binary)
>> are “sanitized” in binary-indep, which might explain why it's only
>> showing up on the maintainer build which was likely using “-b”.
>>
>>> $ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
>>> -rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool
>>> -rw-r--r-- root/root20 2019-01-12 09:10 
>>> ./usr/share/man/man1/libtool.1.gz
>>
>> The manpage is a gzipped empty file.
> 
> I'm afraid the situation is pretty bad, as an empty executable doesn't
> do anything but also produces no errors; so I fear any packages having
> been built using this version of libtool-bin on amd64 has likely missed
> a step or two without that getting noticed…

Could we add a lintian tag for empty executables, particularly in PATH? Then we
could turn that into an autoreject (after analysing the results when
lintian.debian.org is updated) and help prevent this kind of brokenness in the
future.

Thanks,
Emilio

Processed: block 919029 with 478281

[Debian Bug Tracking System]

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

> block 919029 with 478281
Bug #919029 [grub-pc] grub-pc: meaningless message "RUB boot loader was 
previously installed..."
919029 was not blocked by any bugs.
919029 was not blocking any bugs.
Added blocking bug(s) of 919029: 478281
> thanks
Stopping processing here.

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

Processed: dupe

[Debian Bug Tracking System]

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

> reassign 918439 libssh-4
Bug #918439 [src:cockpit] cockpit: FTBFS (failing tests)
Bug reassigned from package 'src:cockpit' to 'libssh-4'.
No longer marked as found in versions cockpit/184-1.
Ignoring request to alter fixed versions of bug #918439 to the same values 
previously set
> forcemerge 918892 918439
Bug #918892 [libssh-4] libssh-4: 0.8.6 breaks server-side host key algorithm 
negotiation
Bug #918892 [libssh-4] libssh-4: 0.8.6 breaks server-side host key algorithm 
negotiation
918439 was blocked by: 918892
918439 was not blocking any bugs.
Removed blocking bug(s) of 918439: 918892
Added tag(s) ftbfs.
Bug #918439 [libssh-4] cockpit: FTBFS (failing tests)
Marked as found in versions libssh/0.8.6-1.
Added tag(s) patch and fixed-upstream.
Merged 918439 918892
> thanks
Stopping processing here.

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

Bug#918933: marked as done (sbd FTBFS with pacemaker 2.0)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 11:19:07 +0100
with message-id <87fttui5pg@lant.ki.iif.hu>
and subject line Re: #918933: sbd FTBFS with pacemaker 2.0
has caused the Debian Bug report #918933,
regarding sbd FTBFS with pacemaker 2.0
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.)


-- 
918933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbd
Version: 1.3.1-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=sbd&suite=sid

...
sbd-pacemaker.c: In function 'mon_timer_notify':
sbd-pacemaker.c:125:18: error: implicit declaration of function 'get_cib_copy'; 
did you mean 'g_list_copy'? [-Werror=implicit-function-declaration]
current_cib = get_cib_copy(cib);
  ^~~~
  g_list_copy
sbd-pacemaker.c:125:16: error: assignment to 'xmlNode *' {aka 'struct _xmlNode 
*'} from 'int' makes pointer from integer without a cast 
[-Werror=int-conversion]
current_cib = get_cib_copy(cib);
^
sbd-pacemaker.c: In function 'cib_connect':
sbd-pacemaker.c:166:15: error: assignment to 'xmlNode *' {aka 'struct _xmlNode 
*'} from 'int' makes pointer from integer without a cast 
[-Werror=int-conversion]
   current_cib = get_cib_copy(cib);
   ^
sbd-pacemaker.c: In function 'crm_diff_update':
sbd-pacemaker.c:311:15: error: assignment to 'xmlNode *' {aka 'struct _xmlNode 
*'} from 'int' makes pointer from integer without a cast 
[-Werror=int-conversion]
   current_cib = get_cib_copy(cib);
   ^
sbd-cluster.c: In function 'notify_timer_cb':
sbd-cluster.c:241:14: error: 'pcmk_cluster_classic_ais' undeclared (first use 
in this function); did you mean 'pcmk_cluster_corosync'?
 case pcmk_cluster_classic_ais:
  ^~~~
  pcmk_cluster_corosync
sbd-cluster.c:241:14: note: each undeclared identifier is reported only once 
for each function it appears in
sbd-cluster.c:242:31: error: 'crm_class_quorum' undeclared (first use in this 
function); did you mean 'crm_have_quorum'?
 send_cluster_text(crm_class_quorum, NULL, TRUE, NULL, crm_msg_ais);
   ^~~~
   crm_have_quorum
sbd-cluster.c:246:14: error: 'pcmk_cluster_cman' undeclared (first use in this 
function); did you mean 'pcmk_cluster_corosync'?
 case pcmk_cluster_cman:
  ^
  pcmk_cluster_corosync
cc1: all warnings being treated as errors
make[3]: *** [Makefile:407: sbd-cluster.o] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.4.0-1

The fresh upstream release builds with Pacemaker 2 just fine.
-- 
Thanks,
Feri--- End Message ---

Bug#916065: patch to fix fdutils ftbfs

[Matteo Cypriani]

On Thu, 10 Jan 2019 22:53:28 +0100
Andreas Henriksson  wrote:
> Please see attached patch that makes sure config.h gets included
> before HAVE_SYS_SYSMACROS_H is checked, so that major and minor
> macros gets properly defined.

Thank you so much Andreas, I will upload that shortly.

Cheers,
  Matteo


pgpPnc_qEXUdj.pgp
Description: PGP signature

Bug#918892: marked as done (libssh-4: 0.8.6 breaks server-side host key algorithm negotiation)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 10:23:02 +
with message-id 
and subject line Bug#918892: fixed in libssh 0.8.6-2
has caused the Debian Bug report #918892,
regarding libssh-4: 0.8.6 breaks server-side host key algorithm negotiation
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.)


-- 
918892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssh-4
Version: 0.8.6-1
Severity: normal

Dear Maintainer,

Server-side libssh-0.8.6 breaks cockpit unit tests by not negotiating a host 
key algo. 

Libssh already has a fix, and depending on how far away .7 is, it might be 
worth backporting:

https://git.libssh.org/projects/libssh.git/commit/?id=27fe60954c

Thank you,
Sanne

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

Kernel: Linux 4.19.0-1-amd64 (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)
LSM: AppArmor: enabled

Versions of packages libssh-4 depends on:
ii  libc6 2.28-2
ii  libgssapi-krb5-2  1.16.2-1
ii  libssl1.1 1.1.1a-1
ii  zlib1g1:1.2.11.dfsg-1

libssh-4 recommends no packages.

libssh-4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libssh
Source-Version: 0.8.6-2

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

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated libssh 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: Tue, 15 Jan 2019 09:51:01 +
Source: libssh
Binary: libssh-4 libssh-gcrypt-4 libssh-dev libssh-gcrypt-dev libssh-doc
Architecture: source
Version: 0.8.6-2
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Martin Pitt 
Description:
 libssh-4   - tiny C SSH library (OpenSSL flavor)
 libssh-dev - tiny C SSH library - Development files (OpenSSL flavor)
 libssh-doc - tiny C SSH library - Documentation files
 libssh-gcrypt-4 - tiny C SSH library (gcrypt flavor)
 libssh-gcrypt-dev - tiny C SSH library - Development files (gcrypt flavor)
Closes: 918892
Changes:
 libssh (0.8.6-2) unstable; urgency=medium
 .
   * 0001-dh-uninitialized-memory.patch: dh: Make sure we do not access
 uninitialized memory.  Patch taken from upstream stable-0.8 branch.
   * 0002-server-extensions.patch: server: Correctly handle extensions.
 Fixes a regression introduced in 0.8.6 that breaks server-side host key
 algorithm negotiation.  Patch taken from upstream stable-0.8 branch.
 (Closes: #918892)
   * Add Martin Pitt as co-maintainer, with Laurent's permission.
   * Add autopkgtest: Add a mock ssh server implementation using libssh, and
 test the OpenSSH client against it. This covers password and pubkey
 authentication.
Checksums-Sha1:
 3698aa18f402b5d76cf65d964bcb75868d519f8c 2426 libssh_0.8.6-2.dsc
 d6fcdd19482395e3b3819d070acee7e303b814ff 27024 libssh_0.8.6-2.debian.tar.xz
 9cd1e7688f758e1d87b914ceb3b43f9d0a5e723c 7036 libssh_0.8.6-2_source.buildinfo
Checksums-Sha256:
 8a2b44e5f0565113ed7ffaa5202016ea39adb3cd2f864486514594c3208864d4 2426 
libssh_0.8.6-2.dsc
 e1aa70c93ba8dcc07448db2578a1e99eb143c80f4cb100a73e0701bf824a9ca7 27024 
libssh_0.8.6-2.debian.tar.xz
 842251b4964779069c204d408fc703afab0adea0cee28a056d684fa4fbe4bba5 7036 
libssh_0.8.6-2_source.buildinfo
Files:
 e1ebfa5d3481a39aad1b875295506b28 2426 libs optional libssh_0.8.6-2.dsc
 788e84e02275a28f596692f6e674c485 27024 libs optional 
libssh_0.8.6-2.debian.tar.xz
 55ed0dd62163db9e6ff29ee1a1be087f 7036 libs optional 
libssh_0.8.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlw9rtIACgkQxrkYDUvY
t66OiQ//UbT5qv1QGkspni48cAPzPQVfvwvgTiasvdBqsRnVwl2J5NT+l+rXORca
9qo60KXpwbmlpHUlf7FhkJyrhpWmudpR+E1hchWIeyeY+LUVIax+SYHR2N47i2OZ
ZRg6glSaPXECr6yT91xRREJsz5A

Bug#919370: deal.ii: FTBFS on s390x: p4est.debug test fails

[Graham Inggs]

Source: deal.ii
Version: 9.0.1-1
Severity: serious
Tags: ftbfs

Hi Maintainer

Recent rebuilds of deal.ii on s390x have been failing with the following 
errors:


Test project /<>/obj-s390x-linux-gnu/tests/quick_tests
  Start  1: step.debug
 1/19 Test  #1: step.debug ...   Passed   21.48 sec
  Start  2: step.release
 2/19 Test  #2: step.release .   Passed   19.35 sec
  Start  3: affinity.debug
 3/19 Test  #3: affinity.debug ...   Passed8.94 sec
  Start  4: mpi.debug
 4/19 Test  #4: mpi.debug    Passed9.87 sec
  Start  5: tbb.debug
 5/19 Test  #5: tbb.debug    Passed8.52 sec
  Start  6: p4est.debug
 6/19 Test  #6: p4est.debug ..***Failed   11.98 sec

...

p4est.debug: RUN failed. Output:
[zani:21379] *** Process received signal ***
[zani:21379] Signal: Segmentation fault (11)
[zani:21379] Signal code: Address not mapped (1)
[zani:21379] Failing at address: 0x3ff7400
[zani:21379] [ 0] [0x3ffcf1fc300]
[zani:21379] [ 1] 
/usr/lib/s390x-linux-gnu/pmix/lib/pmix/mca_gds_ds21.so(+0x20c8)[0x3ff6fe020c8]
[zani:21379] [ 2] 
/usr/lib/s390x-linux-gnu/libmca_common_dstore.so.1(pmix_common_dstor_init+0x9f8)[0x3ff6fd0a570]
[zani:21379] [ 3] 
/usr/lib/s390x-linux-gnu/pmix/lib/pmix/mca_gds_ds21.so(+0x1d44)[0x3ff6fe01d44]
[zani:21379] [ 4] 
/usr/lib/s390x-linux-gnu/libpmix.so.2(pmix_gds_base_select+0x124)[0x3ff742d8f34]
[zani:21379] [ 5] 
/usr/lib/s390x-linux-gnu/libpmix.so.2(pmix_rte_init+0x626)[0x3ff7428e73e]
[zani:21379] [ 6] 
/usr/lib/s390x-linux-gnu/libpmix.so.2(PMIx_Init+0xfa)[0x3ff7424aafa]
[zani:21379] [ 7] 
/usr/lib/s390x-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext2x.so(ext2x_client_init+0xe2)[0x3ff7440c152]
[zani:21379] [ 8] 
/usr/lib/s390x-linux-gnu/openmpi/lib/openmpi3/mca_ess_pmi.so(+0x1ccc)[0x3ff74d01ccc]
[zani:21379] [ 9] 
/usr/lib/s390x-linux-gnu/libopen-rte.so.40(orte_init+0x2da)[0x3ff7bf1b962]
[zani:21379] [10] 
/usr/lib/s390x-linux-gnu/libmpi.so.40(ompi_mpi_init+0x2fe)[0x3ff8494c3d6]
[zani:21379] [11] 
/usr/lib/s390x-linux-gnu/libmpi.so.40(PMPI_Init_thread+0x6c)[0x3ff8497b214]
[zani:21379] [12] 
/<>/obj-s390x-linux-gnu/lib/s390x-linux-gnu/libdeal.ii.g.so.9.0.1(_ZN6dealii9Utilities3MPI16MPI_InitFinalizeC2ERiRPPcj+0x82)[0x3ff8cb4cae2]

[zani:21379] [13] ./p4est.debug(main+0x40)[0x11a2a37b0]
[zani:21379] [14] 
/lib/s390x-linux-gnu/libc.so.6(__libc_start_main+0x10e)[0x3ff84524176]

[zani:21379] [15] ./p4est.debug(+0x23614)[0x11a2a3614]
[zani:21379] [16] [0x0]
[zani:21379] *** End of error message ***
--
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--
[zani:21385] *** Process received signal ***
[zani:21385] Signal: Segmentation fault (11)
[zani:21385] Signal code: Address not mapped (1)
[zani:21385] Failing at address: 0x3ff8c00
[zani:21385] [ 0] [0x3ffebd7c180]
[zani:21385] [ 1] 
/usr/lib/s390x-linux-gnu/pmix/lib/pmix/mca_gds_ds21.so(+0x20c8)[0x3ff8c0820c8]
[zani:21385] [ 2] 
/usr/lib/s390x-linux-gnu/libmca_common_dstore.so.1(pmix_common_dstor_init+0x9f8)[0x3ff87f0a570]
[zani:21385] [ 3] 
/usr/lib/s390x-linux-gnu/pmix/lib/pmix/mca_gds_ds21.so(+0x1d44)[0x3ff8c081d44]
[zani:21385] [ 4] 
/usr/lib/s390x-linux-gnu/libpmix.so.2(pmix_gds_base_select+0x124)[0x3ff8c4d8f34]
[zani:21385] [ 5] 
/usr/lib/s390x-linux-gnu/libpmix.so.2(pmix_rte_init+0x626)[0x3ff8c48e73e]
[zani:21385] [ 6] 
/usr/lib/s390x-linux-gnu/libpmix.so.2(PMIx_Init+0xfa)[0x3ff8c44aafa]
[zani:21385] [ 7] 
/usr/lib/s390x-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext2x.so(ext2x_client_init+0xe2)[0x3ff8c60c152]
[zani:21385] [ 8] 
/usr/lib/s390x-linux-gnu/openmpi/lib/openmpi3/mca_ess_pmi.so(+0x1ccc)[0x3ff8cf01ccc]
[zani:21385] [ 9] 
/usr/lib/s390x-linux-gnu/libopen-rte.so.40(orte_init+0x2da)[0x3ff9411b962]
[zani:21385] [10] 
/usr/lib/s390x-linux-gnu/libmpi.so.40(ompi_mpi_init+0x2fe)[0x3ff9cb4c3d6]
[zani:21385] [11] 
/usr/lib/s390x-linux-gnu/libmpi.so.40(PMPI_Init_thread+0x6c)[0x3ff9cb7b214]
[zani:21385] [12] 
/<>/obj-s390x-linux-gnu/lib/s390x-linux-gnu/libdeal.ii.g.so.9.0.1(_ZN6dealii9Utilities3MPI16MPI_InitFinalizeC2ERiRPPcj+0x82)[0x3ffa4d4cae2]

[zani:21385] [13] ./p4est.debug(main+0x40)[0x10ea237b0]
[zani:21385] [14] 
/lib/s390x-linux-gnu/libc.so.6(__libc_start_main+0x10e)[0x3ff9c724176]

[zani:21385] [15] ./p4est.debug(+0x23614)[0x10ea23614]
[zani:21385] [16] [0x0]
[zani:21385] *** End of error message ***
[zani:21386] *** Process received signal ***
[zani:21386] Signal: Segmentation fault (11)
[zani:21386] Signal code: Address not mapped (1)
[zani:21386] Failing at address: 0x3ff7000
[zani:21386] [ 0] [0x3ffe8bfada0]
[zani:21386] [ 1] 
/usr/lib/s390x-linux-gnu/pmix/lib/pmix/mca_gds_ds21.so(+0x20c8)[0x3ff6be820c8]
[zani:21386] [ 2] 
/usr/lib/s390x-linux-gnu/libmca_co

Bug#918439: marked as done (cockpit: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 10:23:02 +
with message-id 
and subject line Bug#918892: fixed in libssh 0.8.6-2
has caused the Debian Bug report #918892,
regarding cockpit: 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.)


-- 
918892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cockpit
Version: 184-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
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
set -ex; if [ -d debian/git-patches ]; then \
git init; \
git config user.email "unu...@example.com"; git config user.name 
"Unused"; \
git config core.autocrlf false; git config core.safecrlf false && git 
config gc.auto 0; \
git add -f . && git commit -a -q -m "Base" && git tag -a initial 
--message="initial"; \
git am --whitespace=nowarn debian/git-patches/*.patch; \
touch -r $(git diff --name-only initial..HEAD) .git; \
fi

[... snipped ...]


# ./tools/tap-driver --test-name dist/kubernetes/scripts/test-volumes.html 
--log-file dist/kubernetes/scripts/test-volumes.log --trs-file 
dist/kubernetes/scripts/test-volumes.trs --color-tests no --enable-hard-errors 
yes --expect-failure no -- /usr/bin/python3 ./test/common/tap-cdp --strip=./ -- 
./test-server ./dist/kubernetes/scripts/test-volumes.html
1..0 # skip web browser not found

SKIP: dist/machines/test-machines
=

# ./tools/tap-driver --test-name dist/machines/test-machines.html --log-file 
dist/machines/test-machines.log --trs-file dist/machines/test-machines.trs 
--color-tests no --enable-hard-errors yes --expect-failure no -- 
/usr/bin/python3 ./test/common/tap-cdp --strip=./ -- ./test-server 
./dist/machines/test-machines.html
1..0 # skip web browser not found

SKIP: dist/networkmanager/test-utils


# ./tools/tap-driver --test-name dist/networkmanager/test-utils.html --log-file 
dist/networkmanager/test-utils.log --trs-file 
dist/networkmanager/test-utils.trs --color-tests no --enable-hard-errors yes 
--expect-failure no -- /usr/bin/python3 ./test/common/tap-cdp --strip=./ -- 
./test-server ./dist/networkmanager/test-utils.html
1..0 # skip web browser not found

SKIP: dist/storaged/test-util
=

# ./tools/tap-driver --test-name dist/storaged/test-util.html --log-file 
dist/storaged/test-util.log --trs-file dist/storaged/test-util.trs 
--color-tests no --enable-hard-errors yes --expect-failure no -- 
/usr/bin/python3 ./test/common/tap-cdp --strip=./ -- ./test-server 
./dist/storaged/test-util.html
1..0 # skip web browser not found


Testsuite summary for Cockpit 184

# TOTAL: 882
# PASS:  806
# SKIP:  45
# XFAIL: 0
# FAIL:  31
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to de...@lists.cockpit-project.org

make[4]: *** [Makefile:8135: test-suite.log] Error 1
make[4]: Leaving directory '/<>'
make[3]: *** [Makefile:8243: check-TESTS] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:8805: check-am] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:8807: check] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:18: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

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: libssh
Source-Version: 0.8.6-2

We believe that the bug you reported is fixed in the latest version of

Bug#917332: marked as done (FTBFS: quick test gmsh.debug fails)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 12:28:53 +0200
with message-id <8a702ad9-a45a-6c41-f51a-50b0b83eb...@debian.org>
and subject line Re: Bug#917332: FTBFS: quick test gmsh.debug fails
has caused the Debian Bug report #917332,
regarding FTBFS: quick test gmsh.debug 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.)


-- 
917332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deal.ii
Version: 9.0.1-1
Severity: serious
Justification: FTBFS

deal.ii is unhappy about something. It fails to build against petsc
3.10 (the current build log used petsc 3.10.2+dfsg1-2).  

PETSc 3.10 doesn't seem to be the problem directly. The build succeeds
but quick test gmsh.debug fails:

   [100%] Built target gmsh.debug
   /usr/bin/make -f tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/build.make 
tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/depend
   make[9]: Entering directory '/<>/obj-x86_64-linux-gnu'
   cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/tests/quick_tests 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/tests/quick_tests 
/<>/obj-x86_64-linux-gnu/tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/DependInfo.cmake
 --color=
   Scanning dependencies of target gmsh.debug.run
   make[9]: Leaving directory '/<>/obj-x86_64-linux-gnu'
   /usr/bin/make -f tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/build.make 
tests/quick_tests/CMakeFiles/gmsh.debug.run.dir/build
   make[9]: Entering directory '/<>/obj-x86_64-linux-gnu'
   cd /<>/obj-x86_64-linux-gnu/tests/quick_tests && ./gmsh.debug > 
gmsh.debug-OK 2>&1 || ( echo gmsh.debug:\ RUN\ failed.\ Output: && cat 
gmsh.debug-OK && rm gmsh.debug-OK && exit 1 )
   gmsh.debug: RUN failed. Output:
   
   
   An error occurred in line <52> of file 
>/tests/quick_tests/gmsh.cc> in function
   int main()
   The violated condition was: 
   ierr==0
   Additional information: 
   This exception -- which is used in many places in the library -- usually 
indicates that some condition which the author of the code thought must be 
satisfied at a certain point in an algorithm, is not fulfilled. An example 
would be that the first part of an algorithm sorts elements of an array in 
ascending order, and a second part of the algorithm later encounters an element 
that is not larger than the previous one.
   
   There is usually not very much you can do if you encounter such an exception 
since it indicates an error in deal.II, not in your own program. Try to come up 
with the smallest possible program that still demonstrates the error and 
contact the deal.II mailing lists with it to obtain help.
   
   Stacktrace:
   ---
   #0  ./gmsh.debug: main
   
   
   Aborted
   make[9]: Leaving directory '/<>/obj-x86_64-linux-gnu'
   make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu'
   make[7]: Leaving directory '/<>/obj-x86_64-linux-gnu'
   make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu'
   
   
   gmsh.debug: **RUN failed***
   
   ===OUTPUT END   
===
   Expected stage PASSED - aborting
   CMake Error at /<>/cmake/scripts/run_test.cmake:140 (MESSAGE):
 *** abort
   
   
   
   
   95% tests passed, 1 tests failed out of 19





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

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

On 2019/01/01 17:31, Graham Inggs wrote:

Should be fixed now, since the uploads of med-fichier 4.0.0+repack-3
and gmsh 3.0.6+dfsg1-4.1 to unstable.


Recent builds on buildds [1] and reproducible builds [2] have been 
successful.



[1] https://buildd.debian.org/status/logs.php?pkg=deal.ii&arch=amd64
[2] https://tests.reproducible-builds.org/debian/history/amd64/deal.ii.html--- End Message ---

Bug#915805: Should this package be removed?

[Kevin Smith]

On 27 Dec 2018, at 22:52, Moritz Mühlenhoff  wrote:
> 
> On Fri, Dec 07, 2018 at 01:41:47PM +, Kevin Smith wrote:
>> Apologies, I’d forgotten that we’d prepared an update from upstream and not 
>> gotten it submitted. We’ll try to address this in the next week or so.
> 
> What's the status :-)

I’m sitting with packages in front of me, I need to test them, and then 
remember what to do next :)

/K

Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)

[Andreas Tille]

Hi Séverin,

I stumbled upon dlib since I maintain some rdepends (plastimatch) of
this lib and due to #918567 I've got a warning about testing removal.
Since machine learning is definitely a topic that is covered by
Debian Science I'd consider it really appropriate to maintain this
software inside the Debian Science team, which means the repository
would be moved to

https://salsa.debian.org/science-team/dlib

and the maintainer would be set to

Debian Science Maintainers 


while your ID would be added as Uploader.  Would this course of action
be OK for you?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#919371: mono won't migrate to testing, still b-d on gcc-5

[Matthias Klose]

Package: src:mono
Version: 5.16.0.220+dfsg3-2
Severity: serious
Tags: sid buster

mono won't migrate to testing, still b-d on gcc-5 on s390x.

Bug#919373: kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared

[Andreas Beckmann]

Source: kannel
Version: 1.4.5-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

kannel FTBFS against mariadb-10.3:

gcc -D_REENTRANT=1 -I. -Igw -g -O2 -fdebug-prefix-map=/build/kannel-1.4.5=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_XOPEN_SOURCE=600 
-D_BSD_SOURCE -D_DEFAULT_SOURCE -D_FILE_OFFSET_BITS=64 -D_
LARGE_FILES= -I/usr/include/libxml2  -Wall -Wmissing-prototypes 
-Wmissing-declarations -Wnested-externs -Winline -Wformat -Wformat-security 
-Wmissing-format-attribute -I/usr/include -I/usr/include/mariadb -I/usr/
include/mariadb/mysql -I/usr/include/postgresql -I/usr/include/hiredis 
-I/usr/include -o gwlib/utils.o -c gwlib/utils.c
In file included from gwlib/utils.c:98:
/usr/include/mariadb/mysql_version.h:3:2: warning: #warning This file should 
not be included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
gwlib/utils.c: In function 'version_report_string':
gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared (first use in 
this function); did you mean 'MYSQL_PS_CONVERSION'?
  MYSQL_SERVER_VERSION, mysql_get_client_info(),
  ^~~~
  MYSQL_PS_CONVERSION
gwlib/utils.c:602:14: note: each undeclared identifier is reported only once 
for each function it appears in
gwlib/utils.c:622:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
make[1]: *** [Makefile:226: gwlib/utils.o] Error 1


Cheers,

Andreas


kannel_1.4.5-2.log.gz
Description: application/gzip

Bug#892784: Done

[Ivo De Decker]

Hi Thomas,

On 01/15/2019 09:01 AM, Thomas Goirand wrote:

I don't see any worries in reproducible-builds.org with version 7.0.0-1
in Unstable. Could you elaborate where you see the FTBFS?


The amd64 build for 7.0.0-1 is listed as failed on
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zaqar.html

It seems to succeed on the other architectures listed.

The failing log is here:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/zaqar_7.0.0-1.rbuild.log.gz

Maybe the build should be retried (as it succeeds on the other 
architectures).


Cheers,

Ivo

Bug#784479: [kde4libs] Qt4's WebKit removal

[Scott Kitterman]

On January 15, 2019 7:17:36 AM UTC, Pino Toscano  wrote:
>In data lunedì 14 gennaio 2019 12:22:52 CET, Scott Kitterman ha
>scritto:
>> On Thu, 01 Nov 2018 14:04:12 -0300 Lisandro 
>> =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer
> wrote:
>> > On Wed, 17 Oct 2018 15:57:25 +0200 Ivo De Decker 
>wrote:
>> > > Hi,
>> > > 
>> > > On Fri, Nov 24, 2017 at 04:59:58PM -0300, Lisandro Damián Nicanor
>Pérez 
>> > Meyer wrote:
>> > > > Control: tag -1 patch
>> > > > 
>> > > > There is patch available for this at 
>> > > > >
>packages.git/tree/trunk/kdelibs-no-kdewebkit.patch?h=packages/kdelibs>
>> > > > 
>> > > > We might want to wait for the last tandem of KF5 apps though.
>> > > 
>> > > Is there anything still blocking this?
>> > 
>> > Yes, at least one co maintainer believes the kde-runtime patch is
>not 
>> > appropriate.
>> 
>> That patch no longer seems to be available, so I made my own. 
>Patches for 
>> kde4libs and kde-runtime attached.  I looked at the KDE4 packages
>still in 
>> Buster and I don't believe this interferes with anything.  This also
>fixes the 
>> FTBFS with Samba 4.9 by dropping the KDE4 kio_smb.
>
>The samba compatibility issue is a different story, and it can be fixed
>by just disabling kio_smb (in case it requires non-trivial work to make
>it work again).
>
>> I think we should move forward on these (or some improved version if
>someone 
>> has suggestions).
>> 
>> Even though there are separate bugs for kde-runtime, since the patch
>for it 
>> was already discussed in this bug, I thought we might as well keep
>them 
>> together.
>
>Did you check that all the packages using kde4libs still build fine?
>
>The removal of kio_thumbnail from kde-runtime is definitely not
>appropriate, since it will break the thunbnail support for any
>kdelibs 4.x application.
>
>Again: something worth to mention, since apparently it is not clear:
>removing bits from either kde4libs or kde-runtime has consequences,
>either build time or runtime ones. Randomly chopping pieces without
>checking what changes, and potentially what breaks, is generally a
>big no-no from me. I do not see how "remove qtwebkit" is an excuse to
>start messing up with packages, just for the sake of package removal.

I didn't do rebuild tests, but I did search using codesearch to see if any of 
the dropped headers or functions are used.  I didn't find anything.

I think rebuilding the rdepends is a reasonable next step.  I'll try that and 
see if anything is affected.

I understand your concern, but I don't think realeasing with a known pile of 
security vulnerabilities such as Qt4's WebKit is doing anyone any favors if it 
can be avoided.

Scott K

Bug#919374: libodb-mysql: FTBFS with mariadb-10.3: ../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such file or directory

[Andreas Beckmann]

Source: libodb-mysql
Version: 2.4.0-3
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

libodb-mysql FTBFS with mariadb-10.3 in sid:

libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c connection-factory.cxx  -fPIC -DPIC -o 
.libs/connection-factory.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c database.cxx  -fPIC -DPIC -o .libs/database.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c enum.cxx  -fPIC -DPIC -o .libs/enum.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c connection.cxx  -fPIC -DPIC -o .libs/connection.o
In file included from ../../odb/mysql/mysql.hxx:10,
 from connection-factory.cxx:17:
../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such 
file or directory
 #  include 
^~~~
compilation terminated.
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_REENTRANT -c prepared-query.cxx  -fPIC 
-DPIC -o .libs/prepared-query.o
make[3]: *** [Makefile:540: connection-factory.lo] Error 1


Cheers,

Andreas


libodb-mysql_2.4.0-3.log.gz
Description: application/gzip

Bug#913649: should not ship with buster

[Ivo De Decker]

Hi,

On 01/15/2019 09:43 AM, Sébastien Villemot wrote:

Dear Ivo,

Le samedi 12 janvier 2019 à 15:51 +0100, Ivo De Decker a écrit :


On Tue, Nov 13, 2018 at 03:42:02PM +0100, Sébastien Villemot wrote:

common-lisp-controller is obsolete, and should not ship with
buster. It has
been superseded by ASDF.


There are still quite some packages that depend on common-lisp-
controller, so
this will probably have to wait till after buster.


Thanks. I am aware of that. Quite a few reverse dependencies have
already been fixed (either by the maintainer or by myself).

The remaining ones have very low popcon, have not been uploaded for
ages, and their maintainers did not respond to my emails.

So my intention is to let the autoremovals from buster happen
automatically. Removals from sid will indeed have to wait until later.


Currently common-lisp-controller is a key package, because at least one 
of its reverse (build-)dependencies is. So autoremoval will not happen. 
If you want it to be removed, the remaining key packages will have to be 
fixed. It's probably best to file bugs against the other ones.



P.S.: I'm surprised that cl-speech-dispatcher pops up in your list of
broken reverse depends, because it has been fixed.


cl-speech-dispatcher in testing and unstable has
Depends: cl-regex, common-lisp-controller

Cheers,

Ivo

Bug#900154: marked as done (pion: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 11:09:29 +
with message-id 
and subject line Bug#919319: Removed package(s) from unstable
has caused the Debian Bug report #900154,
regarding pion: FTBFS against openssl 1.1.1
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.)


-- 
900154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pion
Version: 5.0.7+dfsg-4
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

The Error
|unknown location(0): fatal error: in 
"WebServerTests_S/checkSendRequestsAndReceiveResponsesUsingSSL": 
boost::exception_detail::clone_impl
 >: use_certificate_file: ee key too small

is due to:
1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/pion_5.0.7%2Bdfsg-4_amd64-2018-05-01T20%3A49%3A03Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/pion_5.0.7%2Bdfsg-4_amd64-2018-05-02T18%3A47%3A26Z

Sebastian
--- End Message ---
--- Begin Message ---
Version: 5.0.7+dfsg-5+rm

Dear submitter,

as the package pion has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/919319

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#919375: monitoring-plugins: FTBFS with mariadb-10.3: check_mysql.c:61:24: error: 'MYSQL_PORT' undeclared

[Andreas Beckmann]

Source: monitoring-plugins
Version: 2.2-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

monitoring-plugins FTBFS with mariadb-10.3 in sid:

i686-linux-gnu-gcc -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I..  
-I.. -I../lib -I../gl -I../intl -I/usr/include/ldap -I/usr/include/postgresql 
-I/usr/include -I/usr/include/mariadb -I/usr/include/ma
riadb/mysql -Wdate-time -D_FORTIFY_SOURCE=2 -DNP_VERSION='"2.2"' 
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
-fdebug-prefix-map=/build/monitoring-plugins-2.2=. -fstack-protector-strong 
-Wformat -We
rror=format-security -Wall -Wl,-z,now -MT check_mysql-check_mysql.o -MD -MP -MF 
.deps/check_mysql-check_mysql.Tpo -c -o check_mysql-check_mysql.o `test -f 
'check_mysql.c' || echo './'`check_mysql.c
check_mysql.c:61:24: error: 'MYSQL_PORT' undeclared here (not in a function); 
did you mean 'MYSQL_STMT'?
 unsigned int db_port = MYSQL_PORT;
^~
MYSQL_STMT
make[3]: *** [Makefile:1869: check_mysql-check_mysql.o] Error 1


Cheers,

Andreas


monitoring-plugins_2.2-4.log.gz
Description: application/gzip

Bug#919376: ncmpc: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:ncmpc
Version: 0.33-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid with "dpkg-buildpackage -A" but it failed:


[...]
 debian/rules build-indep
dh build-indep --with sphinxdoc
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-Dartist_screen=true \
-Dasync_connect=true \
-Dcolors=true \
-Dchat_screen=true \
-Dcurses=ncursesw \
-Ddocumentation=auto \
-Dkey_screen=true \

[... snipped ...]

Installing /<>/doc/keys.sample to 
/<>/debian/tmp/usr/share/doc/ncmpc
Installing /<>/doc/ncmpc.lirc to 
/<>/debian/tmp/usr/share/doc/ncmpc
Running custom install script '/usr/bin/meson --internal gettext install 
--subdir=po --localedir=share/locale --pkgname=ncmpc'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# Remove useless doc files
rm -rf debian/ncmpc/usr/share/doc/ncmpc/COPYING
rm -rf debian/ncmpc/usr/share/doc/ncmpc/NEWS
#TODO: move mkdir to dh *.dirs files?
mkdir -p debian/ncmpc/usr/share/doc/ncmpc/examples
mv  debian/ncmpc/usr/share/doc/ncmpc/*sample \
debian/ncmpc/usr/share/doc/ncmpc/*.lirc \
debian/ncmpc/usr/share/doc/ncmpc/examples
mv: cannot stat 'debian/ncmpc/usr/share/doc/ncmpc/*sample': No such file or 
directory
mv: cannot stat 'debian/ncmpc/usr/share/doc/ncmpc/*.lirc': No such file or 
directory
make[1]: *** [debian/rules:42: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-arch and
override_dh_install-indep.

Please consider uploading in source-only form (dpkg-buildpackage -S) so that 
these
kind of bugs are less likely to propagate to testing.

Thanks.

Bug#919377: mysql++: FTBFS with mariadb-10.3: dbdriver.cpp:260:10: error: 'CLIENT_LONG_PASSWORD' was not declared in this scope

[Andreas Beckmann]

Source: mysql++
Version: 3.2.2+pristine-2
Severity: serious
Tags: sid buster
Justification: fails to build from source

Hi,

mysql++ FTBFS with mariadb-10.3 in sid:

g++ -c -o mysqlpp_dbdriver.o -I. -fPIC -DPIC  -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/mysql -g -O2 -fdebug-prefix-map=/build/mysql++-3.2.2+pristine=. 
-fstack-protector-strong -Wformat -Werror=format-security ./lib/dbdriver.cpp
In file included from ./lib/common.h:133,
 from ./lib/dbdriver.h:31,
 from ./lib/dbdriver.cpp:27:
/usr/include/mysql/mysql_version.h:3:2: warning: #warning This file should not 
be included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
./lib/dbdriver.cpp: In member function 'bool 
mysqlpp::DBDriver::set_option(unsigned int, bool)':
./lib/dbdriver.cpp:260:10: error: 'CLIENT_LONG_PASSWORD' was not declared in 
this scope
(o >= CLIENT_LONG_PASSWORD) &&
  ^~~~
./lib/dbdriver.cpp:260:10: note: suggested alternative: 'CLIENT_LONG_FLAG'
(o >= CLIENT_LONG_PASSWORD) &&
  ^~~~
  CLIENT_LONG_FLAG
./lib/dbdriver.cpp: In member function 'bool 
mysqlpp::DBDriver::set_option_impl(mysqlpp::Option*)':
./lib/dbdriver.cpp:303:7: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
  std::auto_ptr cleanup(o);
   ^~~~
In file included from /usr/include/c++/8/memory:80,
 from ./lib/dbdriver.cpp:32:
/usr/include/c++/8/bits/unique_ptr.h:53:28: note: declared here
   template class auto_ptr;
^~~~
./lib/dbdriver.cpp: In member function 'bool 
mysqlpp::DBDriver::set_option(unsigned int, bool)':
./lib/dbdriver.cpp:282:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
make[1]: *** [Makefile:797: mysqlpp_dbdriver.o] Error 1


Cheers,

Andreas


mysql++_3.2.2+pristine-2.log.gz
Description: application/gzip

Processed: Re: please remove dependency on common-lisp-controller

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #911526 {Done: Samuel Thibault } 
[cl-speech-dispatcher] please remove dependency on common-lisp-controller
'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 speech-dispatcher/0.8.8-7.
> found -1 0.8.8-8
Bug #911526 [cl-speech-dispatcher] please remove dependency on 
common-lisp-controller
Marked as found in versions speech-dispatcher/0.8.8-8.
> severity -1 serious
Bug #911526 [cl-speech-dispatcher] please remove dependency on 
common-lisp-controller
Severity set to 'serious' from 'important'
> block 913649 by -1
Bug #913649 [common-lisp-controller] should not ship with buster
913649 was blocked by: 915507 914701 911527 914700
913649 was not blocking any bugs.
Added blocking bug(s) of 913649: 911526

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

Bug#913649: should not ship with buster

[Sébastien Villemot]

Le mardi 15 janvier 2019 à 12:07 +0100, Ivo De Decker a écrit :
> On 01/15/2019 09:43 AM, Sébastien Villemot wrote:
> > Le samedi 12 janvier 2019 à 15:51 +0100, Ivo De Decker a écrit :
> > 
> > > On Tue, Nov 13, 2018 at 03:42:02PM +0100, Sébastien Villemot wrote:
> > > > common-lisp-controller is obsolete, and should not ship with
> > > > buster. It has
> > > > been superseded by ASDF.
> > > 
> > > There are still quite some packages that depend on common-lisp-
> > > controller, so
> > > this will probably have to wait till after buster.
> > 
> > Thanks. I am aware of that. Quite a few reverse dependencies have
> > already been fixed (either by the maintainer or by myself).
> > 
> > The remaining ones have very low popcon, have not been uploaded for
> > ages, and their maintainers did not respond to my emails.
> > 
> > So my intention is to let the autoremovals from buster happen
> > automatically. Removals from sid will indeed have to wait until later.
> 
> Currently common-lisp-controller is a key package, because at least one 
> of its reverse (build-)dependencies is. So autoremoval will not happen. 
> If you want it to be removed, the remaining key packages will have to be 
> fixed. It's probably best to file bugs against the other ones.
> 
> > P.S.: I'm surprised that cl-speech-dispatcher pops up in your list of
> > broken reverse depends, because it has been fixed.
> 
> cl-speech-dispatcher in testing and unstable has
> Depends: cl-regex, common-lisp-controller

Ok, this is because the dependency has been reintroduced by mistake in
the latest upload of cl-speech-dispatcher (which is a key package).
Tracking this in #911526.

Thanks for noticing,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#914524: marked as done (sogo: SSL problem(?) causes 'An error occurred during object publishing' in webmail)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 11:36:49 +
with message-id 
and subject line Bug#914524: fixed in sogo 4.0.5-2
has caused the Debian Bug report #914524,
regarding sogo: SSL problem(?) causes 'An error occurred during object 
publishing' in webmail
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.)


-- 
914524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sogo
Version: 4.0.4-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
 New installation of sogo on a clean debian buster machine

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Configured sogo with ldap backend and mail capabilities.
 When opening ghe wemail interface sogo replies with 'An error occurred 
during object publishing - the requested object could not be found!'
 In the log there are error messages:
   Error 
(objc-load):/usr/lib/GNUstep/SOGo/MailPartViewers.SOGo/MailPartViewers: 
undefined symbol: SSL_load_error_strings
   Error (objc-load):/usr/lib/GNUstep/SOGo/MailerUI.SOGo/MailerUI: 
undefined symbol: __objc_class_name_UIxMailSizeFormatter

   Nov 16 04:08:48 sogod [18909]: [so-product-registry] could not load 
product: MailPartViewers
   Nov 16 04:08:48 sogod [18909]: [so-product-registry] could not load 
product: MailerUI


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sogo depends on:
ii  adduser   3.118
ii  gnustep-base-runtime  1.25.1-4+b1
ii  libc6 2.27-8
ii  libcurl3-gnutls   7.61.0-1
ii  libgcc1   1:8.2.0-9
ii  libglib2.0-0  2.58.1-2
ii  libgnustep-base1.25   1.25.1-4+b1
ii  libgnutls30   3.5.19-1+b1
ii  liblasso3 2.6.0-2+b2
ii  libmemcached111.0.18-4.2
ii  libobjc4  8.2.0-9
ii  libsbjson2.3  2.3.2-3+b1
ii  libsope1  4.0.4-1
ii  lsb-base  9.20170808
ii  memcached 1.5.6-1
ii  sogo-common   4.0.4-1
ii  systemd   239-13
ii  zip   3.0-11+b1

sogo recommends no packages.

Versions of packages sogo suggests:
ii  postgresql  11+197

-- Configuration Files:
/etc/cron.d/sogo changed [not included]
/etc/sogo/sogo.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sogo
Source-Version: 4.0.5-2

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

Debian distribution maintenance software
pp.
Jeroen Dekkers  (supplier of updated sogo 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: Tue, 15 Jan 2019 10:14:20 +0100
Source: sogo
Binary: sogo sogo-common
Architecture: source
Version: 4.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian SOGo Maintainers 

Changed-By: Jeroen Dekkers 
Description:
 sogo   - Scalable groupware server
 sogo-common - Scalable groupware server - common files
Closes: 914524
Changes:
 sogo (4.0.5-2) unstable; urgency=medium
 .
   * Add patch to not use OpenSSL when we are configured to use GnuTLS
 (closes: #914524).
   * Add patch to unset MAKEFLAGS and MFLAGS in configure.
Checksums-Sha1:
 66a64e591e88a6ab50e27cb76bbab8f57ee4541e 1964 sogo_4.0.5-2.dsc
 6a1ff179513b24960694cb5b054095409ebc7157 15124 sogo_4.0.5-2.debian.tar.xz
 8631a42e28c53cfff3993cab784bc812c837382f 8624 sogo_4.0.5-2_source.buildinfo
Checksums-Sha256:
 a52e98f2d1df8deddda0b1c829ad0b1f6614ccb29419ffe37fd3fac7e9850f90 1964 
sogo_4.0.5-2.dsc
 6ad89b054b5b4e3a83fd6f74fdb2fa7415f348ae624c8d275a18adb3e74e8010 15124 
sogo_4.0.5-2.debian.tar.xz
 3b4def21af5f86b333ad0845e681a576b9d4a3e86c14a1934aeebc35b6f75a5e 8624 
sogo_4.0.5-2_source.buildinfo
Files:
 4

Processed: Re: [Tts-project] Bug#911526: please remove dependency on common-lisp-controller

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #911526 [cl-speech-dispatcher] please remove dependency on 
common-lisp-controller
Added tag(s) pending.

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

Bug#911526: [Tts-project] Bug#911526: please remove dependency on common-lisp-controller

[Samuel Thibault]

Control: tags -1 + pending

Sébastien Villemot, le mar. 15 janv. 2019 12:18:52 +0100, a ecrit:
> The dependency on common-lisp-controller had been dropped in 0.8.8-7,
> but it has been reintroduced in 0.8.8-8.
> 
> Please remove it again. Indeed, as you noticed, you should also remove
> the calls to {,un}register-common-lisp-source in the maintainer
> scripts.

Ah, sorry, I indeed didn't realize that it was removed for a reason (but
wasn't completely fixed).  I'll fix this.

Samuel

Bug#919379: pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'

[Andreas Beckmann]

Source: pmacct
Version: 1.7.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

pmacct FTBFS with mariadb-10.3 in sid:

btool: compile:  gcc -DPACKAGE_NAME=\"pmacct\" -DPACKAGE_TARNAME=\"pmacct\" 
-DPACKAGE_VERSION=\"1.7.0\" "-DPACKAGE_STRING=\"pmacct 1.7.0\"" 
-DPACKAGE_BUGREPORT=\"pa...@pmacct.net\" -DPACKAGE_URL=\"\" -DPACKAGE=
\"pmacct\" -DVERSION=\"1.7.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNIST
D_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DLINUX=1 -DPROGNAME=1 
-DIM_LITTLE_ENDIAN=1 -DHAVE_L2=1 -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 
-DENABLE_IPV6=1 -DENABLE_PLABEL=1 -DHAVE_PCAP_H=1 -DHAVE_LIBPCAP=1 -DPCA
P_NOBPF=1 -DPCAP_TYPE_linux=1 -DWITH_MYSQL=1 -DWITH_PGSQL=1 -DWITH_SQLITE3=1 
-DWITH_RABBITMQ=1 -DWITH_ZMQ=1 -DWITH_KAFKA=1 -DWITH_GEOIPV2=1 -DWITH_JANSSON=1 
-DHAVE_LIBJANSSON=1 -DHAVE_JSON_OBJECT_UPDATE_MISSING=1
 -DHAVE_DLOPEN=1 -DHAVE_ZLIB=1 -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 
-DHAVE_GETOPT_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_U_INT64_T=1 
-DHAVE_U_INT32_T=1 -DHAVE_U_INT16_T=1 -DHAVE_U_INT8_T=1 -DHAVE_UI
NT64_T=1 -DHAVE_UINT32_T=1 -DHAVE_UINT16_T=1 -DHAVE_UINT8_T=1 
-DHAVE_64BIT_COUNTERS=1 -DENABLE_THREADS=1 -D_XOPEN_SOURCE=600 -D_GNU_SOURCE=1 
-DWITH_NFLOG=1 -DHAVE_TRAFFIC_BINS=1 -DHAVE_BGP_BINS=1 -DHAVE_BMP_BINS=
1 -DHAVE_ST_BINS=1 -DRETSIGTYPE=void -DHAVE_VSNPRINTF=1 -DHAVE_MALLOPT=1 
-DHAVE_TDESTROY=1 "-DCOMPILE_ARGS=\" '--build=i686-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/
man' '--infodir=\${prefix}/share/info' '--sysconfdir=/etc' 
'--localstatedir=/var' '--disable-silent-rules' 
'--libdir=\${prefix}/lib/i386-linux-gnu' 
'--libexecdir=\${prefix}/lib/i386-linux-gnu' '--disable-maintain
er-mode' '--disable-dependency-tracking' 
'--with-pgsql-includes=/usr/include/postgresql' '--enable-l2' '--enable-ipv6' 
'--enable-plabel' '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' 
'--enable-rabbitmq' '-
-enable-zmq' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' 
'--enable-64bit' '--enable-threads' '--enable-traffic-bins' '--enable-bgp-bins' 
'--enable-bmp-bins' '--enable-st-bins' '--enable-nflog' 'build_a
lias=i686-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/pmacct-1.7.0=. 
-fstack-protector-strong -Wformat -Werror=format-security' 
'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'\"" -I. -Wd
ate-time -D_FORTIFY_SOURCE=2 -I/usr/include/mariadb 
-I/usr/include/mariadb/mysql -I/usr/include/postgresql -isystem 
/usr/include/mit-krb5 -I/usr/include/pgm-5.2 
-I/usr/lib/i386-linux-gnu/pgm-5.2/include -I/usr/in
clude/i386-linux-gnu -I/usr/include/mariadb -I/usr/include/mariadb/mysql 
-I/usr/include/postgresql -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.2 
-I/usr/lib/i386-linux-gnu/pgm-5.2/include -O2 -g -O2 -fdebu
g-prefix-map=/build/pmacct-1.7.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -c mysql_plugin.c  -fPIC -DPIC -o 
.libs/libdaemons_la-mysql_plugin.o
In file included from mysql_plugin.c:30:
sql_common_m.c: In function 'SQL_SetENV_child':
sql_common_m.c:261:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->elap_time);
  ~^   
  %lu
sql_common_m.c:294:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->basetime);
  ~^   ~~~
  %lu
sql_common_m.c:305:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->timeslot);
  ~^   ~~~
  %lu
mysql_plugin.c: In function 'MY_DB_Connect':
mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member 
named 'reconnect'
 dbptr->reconnect = TRUE;
  ^~
mysql_plugin.c: In function 'MY_mysql_get_version':
mysql_plugin.c:771:24: error: 'MYSQL_SERVER_VERSION' undeclared (first use in 
this function); did you mean 'MYSQL_PS_CONVERSION'?
   printf("MySQL %s\n", MYSQL_SERVER_VERSION);
^~~~
MYSQL_PS_CONVERSION
mysql_plugin.c:771:24: note: each undeclared identifier is reported only once 
for each function it appears in
make[3]: *** [Makefile:1039: libdaemons_la-mysql_plugin.lo] Error 1


Cheers,

Andreas


pmacct_1.7.0-1.log.gz
Description: application/gzip

Bug#911526: marked as done (please remove dependency on common-lisp-controller)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 11:52:16 +
with message-id 
and subject line Bug#911526: fixed in speech-dispatcher 0.8.8-9
has caused the Debian Bug report #911526,
regarding please remove dependency on common-lisp-controller
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.)


-- 
911526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-speech-dispatcher
Version: 0.8.8-6
Severity: important
Tags: patch

Dear Maintainer,

Please drop the dependency on common-lisp-controller. This package is obsolete,
and ideally it will not ship with Buster. It has been superseded by ASDF, which
is shipped by all Common Lisp implementations in Debian.

Dropping the dependency should be enough. ASDF is able to locate the files
where they are installed (i.e. under /usr/share/common-lisp/).

The severity of this bug report may be raised before the Buster freeze.

Best,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org
--- End Message ---
--- Begin Message ---
Source: speech-dispatcher
Source-Version: 0.8.8-9

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated speech-dispatcher 
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, 15 Jan 2019 12:42:41 +0100
Source: speech-dispatcher
Binary: speech-dispatcher libspeechd2 libspeechd-dev cl-speech-dispatcher 
python3-speechd speech-dispatcher-festival speech-dispatcher-doc-cs 
speech-dispatcher-audio-plugins speech-dispatcher-flite 
speech-dispatcher-cicero speech-dispatcher-espeak speech-dispatcher-espeak-ng
Architecture: source
Version: 0.8.8-9
Distribution: unstable
Urgency: medium
Maintainer: Debian TTS Team 
Changed-By: Samuel Thibault 
Description:
 cl-speech-dispatcher - Common Lisp interface to Speech Dispatcher
 libspeechd-dev - Speech Dispatcher: Development libraries and header files
 libspeechd2 - Speech Dispatcher: Shared libraries
 python3-speechd - Python interface to Speech Dispatcher
 speech-dispatcher - Common interface to speech synthesizers
 speech-dispatcher-audio-plugins - Speech Dispatcher: Audio output plugins
 speech-dispatcher-cicero - Speech Dispatcher: Cicero output module
 speech-dispatcher-doc-cs - Speech Dispatcher documentation in Czech
 speech-dispatcher-espeak - Speech Dispatcher: Espeak output module
 speech-dispatcher-espeak-ng - Speech Dispatcher: Espeak-ng output module
 speech-dispatcher-festival - Festival support for Speech Dispatcher
 speech-dispatcher-flite - Speech Dispatcher: Flite output module
Closes: 911526
Changes:
 speech-dispatcher (0.8.8-9) unstable; urgency=medium
 .
   * cl-speech-dispatcher.{postinst,prerm}: Remove calls to
 {,un}register-common-lisp-source.
   * debian/control: Remove cl-speech-dispatcher's dependency on
 common-lisp-controller for real (Closes: Bug#911526).
Checksums-Sha1:
 cbede14aa9fa3745561e4c2f62d245ae1aaf805d 3213 speech-dispatcher_0.8.8-9.dsc
 1087a968b79c221af02beca5bf6dc0102abb5768 22460 
speech-dispatcher_0.8.8-9.debian.tar.xz
Checksums-Sha256:
 f2cb6b4dbfb3c50e245c4bd08bd4343797e24835b87d259fdcb8f3136ba711e3 3213 
speech-dispatcher_0.8.8-9.dsc
 a67d19ac082c4c839d88d517a823b749d1accff9035361454f979ef4d8600891 22460 
speech-dispatcher_0.8.8-9.debian.tar.xz
Files:
 2c57eed9d75261269d2fcc76ef646fb2 3213 sound optional 
speech-dispatcher_0.8.8-9.dsc
 f9f70774cb6a99708a2dd673d4987b7a 22460 sound optional 
speech-dispatcher_0.8.8-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM/p7ZGGVAfjOnI+X4/ZanpVg20wFAlw9x/IACgkQ4/ZanpVg
20zpbRAAwLNq33QyIddIP4KYV/LKGGdQkykFYKfrE2c/cCeNK8qV9VMZNOiqpnaO
8JfZvroiPXlbSYD/AjOqnE/Ehm3e6X4xLH+4XJPd2rRiBtRtARWcyTdM6juWVfgB
xK20XX5GWUQ/VPupLIB9locQQucGlmWN07MoBCs30z9Yi11I86SZA724Z8f41z+2
iR3Fhm8c/3hCLRPL3sTtTuQFJZru1z4R2Trm3U/Vj1lNAwLkCxVy8byfVlSzR+u4
6JXX9vwRjFl5t8LqAQ0ZM0wBXdPReKl9LwQ7YD1hXxRrQfc1oQVS6fV69Gi86Hhq
Fu

Bug#909032: Additional build failures

[Reinhard Tartler]

Seems that additional issues have shown up:

dh_auto_configure
make[1]: Leaving directory '/<>/cadvisor-0.27.1+dfsg2'
   dh_auto_build -a -O--buildsystem=golang -O--builddirectory=_build
cd _build && go install 
-gcflags=all=\"-trimpath=/<>/cadvisor-0.27.1\+dfsg2/_build/src\" 
-asmflags=all=\"-trimpath=/<>/cadvisor-0.27.1\+dfsg2/_build/src\" -v 
-p 4 github.com/google/cadvisor github.com/google/cadvisor/api 
github.com/google/cadvisor/cache github.com/google/cadvisor/cache/memory 
github.com/google/cadvisor/client 
github.com/google/cadvisor/client/clientexample 
github.com/google/cadvisor/client/v2 github.com/google/cadvisor/collector 
github.com/google/cadvisor/container 
github.com/google/cadvisor/container/common 
github.com/google/cadvisor/container/crio 
github.com/google/cadvisor/container/docker 
github.com/google/cadvisor/container/libcontainer 
github.com/google/cadvisor/container/raw 
github.com/google/cadvisor/container/rkt 
github.com/google/cadvisor/container/systemd 
github.com/google/cadvisor/container/testing 
github.com/google/cadvisor/devicemapper 
github.com/google/cadvisor/devicemapper/fake github.com/google/cadvisor/events 
github.com/google/c
 advisor/fs github.com/google/cadvisor/healthz github.com/google/cadvisor/http 
github.com/google/cadvisor/http/mux github.com/google/cadvisor/info/v1 
github.com/google/cadvisor/info/v1/test github.com/google/cadvisor/info/v2 
github.com/google/cadvisor/integration/framework 
github.com/google/cadvisor/integration/runner 
github.com/google/cadvisor/integration/tests/api 
github.com/google/cadvisor/integration/tests/healthz 
github.com/google/cadvisor/machine github.com/google/cadvisor/manager 
github.com/google/cadvisor/manager/watcher 
github.com/google/cadvisor/manager/watcher/raw 
github.com/google/cadvisor/manager/watcher/rkt 
github.com/google/cadvisor/metrics github.com/google/cadvisor/pages 
github.com/google/cadvisor/pages/static github.com/google/cadvisor/storage 
github.com/google/cadvisor/storage/bigquery 
github.com/google/cadvisor/storage/bigquery/client 
github.com/google/cadvisor/storage/bigquery/client/example 
github.com/google/cadvisor/storage/elasticsearch github.com/google/cadvi
 sor/storage/influxdb github.com/google/cadvisor/storage/kafka 
github.com/google/cadvisor/storage/redis 
github.com/google/cadvisor/storage/statsd 
github.com/google/cadvisor/storage/statsd/client 
github.com/google/cadvisor/storage/stdout 
github.com/google/cadvisor/storage/test github.com/google/cadvisor/summary 
github.com/google/cadvisor/utils github.com/google/cadvisor/utils/cloudinfo 
github.com/google/cadvisor/utils/container 
github.com/google/cadvisor/utils/cpuload 
github.com/google/cadvisor/utils/cpuload/netlink 
github.com/google/cadvisor/utils/cpuload/netlink/example 
github.com/google/cadvisor/utils/docker 
github.com/google/cadvisor/utils/oomparser 
github.com/google/cadvisor/utils/oomparser/oomexample 
github.com/google/cadvisor/utils/procfs github.com/google/cadvisor/utils/sysfs 
github.com/google/cadvisor/utils/sysfs/fakesysfs 
github.com/google/cadvisor/utils/sysinfo github.com/google/cadvisor/utils/tail 
github.com/google/cadvisor/validate github.com/google/cadvisor/version githu
 b.com/google/cadvisor/zfs
src/github.com/google/cadvisor/container/common/inotify_watcher.go:20:2: cannot 
find package "golang.org/x/exp/inotify" in any of:

/<>/cadvisor-0.27.1+dfsg2/_build/src/github.com/google/cadvisor/vendor/golang.org/x/exp/inotify
 (vendor tree)
/usr/lib/go-1.11/src/golang.org/x/exp/inotify (from $GOROOT)
/<>/cadvisor-0.27.1+dfsg2/_build/src/golang.org/x/exp/inotify 
(from $GOPATH)
dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/<>/cadvisor-0.27.1\+dfsg2/_build/src\" 
-asmflags=all=\"-trimpath=/<>/cadvisor-0.27.1\+dfsg2/_build/src\" -v 
-p 4 github.com/google/cadvisor github.com/google/cadvisor/api 
github.com/google/cadvisor/cache github.com/google/cadvisor/cache/memory 
github.com/google/cadvisor/client 
github.com/google/cadvisor/client/clientexample 
github.com/google/cadvisor/client/v2 github.com/google/cadvisor/collector 
github.com/google/cadvisor/container 
github.com/google/cadvisor/container/common 
github.com/google/cadvisor/container/crio 
github.com/google/cadvisor/container/docker 
github.com/google/cadvisor/container/libcontainer 
github.com/google/cadvisor/container/raw 
github.com/google/cadvisor/container/rkt 
github.com/google/cadvisor/container/systemd 
github.com/google/cadvisor/container/testing 
github.com/google/cadvisor/devicemapper 
github.com/google/cadvisor/devicemapper/fake github.com/google/cadvisor/events 
githu
 b.com/google/cadvisor/fs github.com/google/cadvisor/healthz 
github.com/google/cadvisor/http github.com/google/cadvisor/http/mux 
github.com/google/cadvisor/info/v1 github.com/google/cadvisor/info/v1/test 
github.com/google/cadvisor/info/v2 
github.com/google/cadvisor/integration/framework 
github.com/google/cadvisor/integration/runner 
gith

Bug#919000: marked as done (Missing distribution 'keyring')

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 12:19:48 +
with message-id 
and subject line Bug#919000: fixed in spyder 3.3.2+dfsg1-2
has caused the Debian Bug report #919000,
regarding Missing distribution 'keyring'
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.)


-- 
919000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spyder3
Version: 3.3.2+dfsg1-1
Severity: critical

pkg_resources.DistributionNotFound: The 'keyring' distribution was not found 
and is required by spyderpkg_resources.DistributionNotFound: The 'keyring' 
distribution was not found and is required by spyder

-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.155-94.50-default (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
de_DE.UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect

Versions of packages spyder3 depends on:
ii  python3-spyder  3.3.2+dfsg1-1
ii  python3.7   3.7.2~rc1-1

spyder3 recommends no packages.

spyder3 suggests no packages.

Versions of packages python3-spyder depends on:
ii  libjs-jquery3.2.1-1
ii  libjs-mathjax   2.7.4+dfsg-1
ii  pylint3 2.1.1-2
ii  python3 3.7.1-2
ii  python3-chardet 3.0.4-1
ii  python3-cloudpickle 0.5.6-1
ii  python3-jedi0.12.0-1.1
ii  python3-nbconvert   5.3.1-1
ii  python3-numpydoc0.7.0-1
ii  python3-pickleshare 0.7.5-1
ii  python3-psutil  5.4.8-1
ii  python3-pycodestyle 2.4.0-2
ii  python3-pyflakes2.0.0-1
ii  python3-pygments2.2.0+dfsg-2
ii  python3-qtawesome   0.4.4+ds1-1
ii  python3-qtconsole   4.3.1-1
ii  python3-qtpy1.3.1-1
ii  python3-rope0.10.5-3
ii  python3-sphinx  1.7.9-1
ii  python3-spyder-kernels  1.0.1+really0.2.4-1
ii  python3-zmq 17.1.2-1
ii  spyder-common   3.3.2+dfsg1-1

Versions of packages python3-spyder suggests:
pn  cython3 
pn  python3-matplotlib  
ii  python3-numpy   1:1.15.4-2
ii  python3-pandas  0.23.3-1
pn  python3-pil 
ii  python3-scipy   1.1.0-2
pn  python3-sympy   

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.28-2
ii  libgcc1   1:8.2.0-12
ii  libpython3.7  3.7.2~rc1-1
ii  libqt5core5a [qtbase-abi-5-11-2]  5.11.2+dfsg-7
ii  libqt5dbus5   5.11.2+dfsg-7
ii  libqt5designer5   5.11.2-5
ii  libqt5gui55.11.2+dfsg-7
ii  libqt5help5   5.11.2-5
ii  libqt5network55.11.2+dfsg-7
ii  libqt5printsupport5   5.11.2+dfsg-7
ii  libqt5test5   5.11.2+dfsg-7
ii  libqt5widgets55.11.2+dfsg-7
ii  libqt5xml55.11.2+dfsg-7
ii  libstdc++68.2.0-12
ii  python3   3.7.1-2
ii  python3-sip [sip-py3api-12.5] 4.19.13+dfsg-1

Versions of packages python3-pyqt5 suggests:
pn  python3-pyqt5-dbg  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: spyder
Source-Version: 3.3.2+dfsg1-2

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated spyder 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: Tue, 15 Jan 2019 12:23:41 +0100
Source: spyder
Binary: spyder python-spyderlib python-spyder spyder3 python3-spyderlib 
python3-spyder spyder-common
Architecture: source
Version: 3.3.2+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 python-spyder - public modules for spyder (Python 2)
 python-spyderlib - transitional dummy package for python-spyder
 python3-spyder - publ

Bug#919383: supercollider: unbuildable on several architectures due to qtwebengine5-dev

[Emilio Pozuelo Monfort]

Source: supercollider
Version: 1:3.10.0+repack-0.1
Severity: serious

Hi,

supercollider is bd-uninstallable on several architectures where it was
built in the past, preventing testing migration:

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

The way to fix this is to either only build-depend on qtwebengine on the
architectures where it is available (assuming supercollider can be built
without that), or otherwise get the outdated supercollider binary packages
removed from unstable via a RM bug against ftp.debian.org.

Cheers,
Emilio

Bug#877228: marked as done (maliit-framework: FTBFS with GCC 7: symbols have changed)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 13:37:03 +0100
with message-id <8e461a7d-ca3d-e0df-bcad-79222d549...@debian.org>
and subject line maliit-framework was removed from experimental
has caused the Debian Bug report #877228,
regarding maliit-framework: FTBFS with GCC 7: symbols have changed
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.)


-- 
877228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maliit-framework
Version: 0.94.1-2
Severity: serious
Justification: fails to build from source

Hi,

maliit-framework FTBFS in a current sid/experimental environment (at
least) since GCC 7 was made the default compiler.

   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/maliit-framework-0.94.1'
dh_makeshlibs -- -c4
rm -f debian/maliit-framework/DEBIAN/shlibs
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 7 in use)
install -d debian/maliit-framework/DEBIAN
echo 'libmaliit-connection 0 maliit-framework' 
>>debian/maliit-framework/DEBIAN/shlibs
echo 'libmaliit-plugins-quick 0 maliit-framework' 
>>debian/maliit-framework/DEBIAN/shlibs
echo 'libmaliit-plugins 0 maliit-framework' 
>>debian/maliit-framework/DEBIAN/shlibs
chmod 0644 -- debian/maliit-framework/DEBIAN/shlibs
chown 0:0 -- debian/maliit-framework/DEBIAN/shlibs
mv debian/.debhelper/generated/maliit-framework/triggers.new 
debian/.debhelper/generated/maliit-framework/triggers
rm -f debian/maliit-framework-dev/DEBIAN/shlibs
rm -f debian/maliit-framework-dbg/DEBIAN/shlibs
install -d debian/maliit-framework-dbg/DEBIAN
rm -f debian/maliit-inputcontext-gtk2/DEBIAN/shlibs
install -d debian/maliit-inputcontext-gtk2/DEBIAN
rm -f debian/maliit-inputcontext-gtk3/DEBIAN/shlibs
install -d debian/maliit-inputcontext-gtk3/DEBIAN
rm -f debian/maliit-inputcontext-qt4/DEBIAN/shlibs
install -d debian/maliit-inputcontext-qt4/DEBIAN
rm -f debian/libmaliit0/DEBIAN/shlibs
install -d debian/libmaliit0/DEBIAN
echo 'libmaliit-settings 0 libmaliit0' >>debian/libmaliit0/DEBIAN/shlibs
echo 'libmaliit 0 libmaliit0' >>debian/libmaliit0/DEBIAN/shlibs
chmod 0644 -- debian/libmaliit0/DEBIAN/shlibs
chown 0:0 -- debian/libmaliit0/DEBIAN/shlibs
dpkg-gensymbols -plibmaliit0 -Idebian/libmaliit0.symbols 
-Pdebian/libmaliit0 -c4
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libmaliit0/DEBIAN/symbols doesn't match 
completely debian/libmaliit0.symbols
--- debian/libmaliit0.symbols (libmaliit0_0.94.1-2_amd64)
+++ dpkg-gensymbolsS4E70o   2017-09-20 05:06:56.542779000 +
@@ -1,7 +1,7 @@
 libmaliit-settings.so.0 libmaliit0 #MINVER#
  
_Z20validateSettingValueN6Maliit16SettingEntryTypeE4QMapI7QString8QVariantERKS3_@Base
 0.94.1
- _ZN10QByteArrayD1Ev@Base 0.94.1
- _ZN10QByteArrayD2Ev@Base 0.94.1
+#MISSING: 0.94.1-2# _ZN10QByteArrayD1Ev@Base 0.94.1
+#MISSING: 0.94.1-2# _ZN10QByteArrayD2Ev@Base 0.94.1
  
(optional=templinst|arch=powerpc)_ZN14QScopedPointerIN6Maliit20SettingsEntryPrivateE21QScopedPointerDeleterIS1_EED1Ev@Base
 0.94.1
  
(optional=templinst|arch=powerpc)_ZN14QScopedPointerIN6Maliit20SettingsEntryPrivateE21QScopedPointerDeleterIS1_EED2Ev@Base
 0.94.1
  
(optional=templinst|arch=powerpc)_ZN14QScopedPointerIN6Maliit21PluginSettingsPrivateE21QScopedPointerDeleterIS1_EED1Ev@Base
 0.94.1
@@ -18,13 +18,13 @@
  _ZN15QtSharedPointer20ExternalRefCountDataD0Ev@Base 0.94.1
  _ZN15QtSharedPointer20ExternalRefCountDataD1Ev@Base 0.94.1
  _ZN15QtSharedPointer20ExternalRefCountDataD2Ev@Base 0.94.1
- _ZN21MImPluginSettingsInfoD1Ev@Base 0.94.1
- _ZN21MImPluginSettingsInfoD2Ev@Base 0.94.1
+#MISSING: 0.94.1-2# _ZN21MImPluginSettingsInfoD1Ev@Base 0.94.1
+#MISSING: 0.94.1-2# _ZN21MImPluginSettingsInfoD2Ev@Base 0.94.1
  
(optional=templinst)_ZN21QScopedPointerDeleterIN6Maliit20SettingsEntryPrivateEE7cleanupEPS1_@Base
 0.94.1-2
  
(optional=templinst)_ZN21QScopedPointerDeleterIN6Maliit21PluginSettingsPrivateEE7cleanupEPS1_@Base
 0.94.1-2
  
(optional=templinst)_ZN21QScopedPointerDeleterIN6Maliit22SettingsManagerPrivateEE7cleanupEPS1_@Base
 0.94.1-2
- _ZN22MImPluginSettingsEntryD1Ev@Base 0.94.1
- _ZN22MImPluginSettingsEntryD2Ev@Base 0.94.1
+#MISSING: 0.94.1-2# _ZN22MImPluginSettingsEntryD1Ev@Base 0.94.1
+#MISSING: 0

Bug#919371: mono won't migrate to testing, still b-d on gcc-5

[Jo Shields]

Thanks for the tracking bug. I spotted this last night and am working on 
zelenka to convince the damn thing to build - it's something to do with PIE, 
and only shows up as a problem with the Runtime crashing in the literal last 30 
seconds of the build step 

Sent from my iPhone

> On 15 Jan 2019, at 05:45, Matthias Klose  wrote:
> 
> Package: src:mono
> Version: 5.16.0.220+dfsg3-2
> Severity: serious
> Tags: sid buster
> 
> mono won't migrate to testing, still b-d on gcc-5 on s390x.
> 

Bug#919388: ubertooth: Replace pyside dependencies by pyside2 dependencies

[Raphaël Hertzog]

Source: ubertooth
Version: 2018.12.R1-1
Severity: serious
User: de...@kali.org
Usertags: origin-kali

The last release of ubertooth updated /usr/bin/ubertooth-specan-ui to use
PySide2 instead of PySide but the Recommends field has not been updated
accordingly:
$ apt-cache show ubertooth|grep Recommends
Recommends: ubertooth-firmware, python-pyside.qtcore, python-pyside.qtgui
$ grep PySide2 /usr/bin/ubertooth-specan-ui
from PySide2 import QtCore, QtGui, QtWidgets
from PySide2.QtCore import Qt, QPointF, QLineF

Please recommend "python-pyside2.qtcore, python-pyside2.qtgui,
python-pyside2.qtwidgets".

Thank you.

This bug report is triggered by Kali's work to get rid of pyside 1.x:
https://bugs.kali.org/view.php?id=4978

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

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

Processed (with 3 errors): Merge duplicates and move to the package where it was fixed

[Debian Bug Tracking System]

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

> reassign 919223 ruby-haml 5.0.4-1
Bug #919223 {Done: Cédric Boutillier } [ruby-rack] 
ruby-haml-contrib: missing build dependency on ruby-temple
Bug reassigned from package 'ruby-rack' to 'ruby-haml'.
Ignoring request to alter found versions of bug #919223 to the same values 
previously set
No longer marked as fixed in versions ruby-rack/5.0.4-2.
Bug #919223 {Done: Cédric Boutillier } [ruby-haml] 
ruby-haml-contrib: missing build dependency on ruby-temple
Marked as found in versions ruby-haml/5.0.4-1.
> fixed 919223 5.0.4-3
Bug #919223 {Done: Cédric Boutillier } [ruby-haml] 
ruby-haml-contrib: missing build dependency on ruby-temple
Marked as fixed in versions ruby-haml/5.0.4-3.
> reassign 919205
Unknown command or malformed arguments to command.
> forcemerge 919223 919205
Bug #919223 {Done: Cédric Boutillier } [ruby-haml] 
ruby-haml-contrib: missing build dependency on ruby-temple
Unable to merge bugs because:
package of #919205 is 'src:ruby-html2haml' not 'ruby-haml'
Failed to forcibly merge 919223: Did not alter merged bugs.

> affects 919223 src:ruby-html2haml src:ruby-haml-contrib
Failed to mark 919223 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/919223 -- Unable to lock 
/org/bugs.debian.org/spool/lock/919223 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/919223 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> thanks
Stopping processing here.

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

Bug#919393: python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'

[Andreas Beckmann]

Package: python-mysqldb
Version: 1.3.10-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

python-mysqldb FTBFS with mariadb-10.3 in sid:

building '_mysql' extension
creating build
creating build/temp.linux-i386-2.7
i686-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/python-mysqldb-1.3.10=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Dversion_info=(1,3,10,'final',0) 
-D__version__=1.3.10 -I/usr/include/mariadb -I/usr/include/mariadb/mysql 
-I/usr/include/python2.7 -c _mysql.c -o build/temp.linux-i386-2.7/_mysql.o
In file included from _mysql.c:29:
/usr/include/mariadb/my_config.h:3:2: warning: #warning This file should not be 
included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
In file included from _mysql.c:30:
/usr/include/mariadb/mysql.h:440:3: warning: function declaration isn't a 
prototype [-Wstrict-prototypes]
   MYSQL_CLIENT_PLUGIN_HEADER
   ^~
_mysql.c: In function '_mysql_ConnectionObject_ping':
_mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 
'reconnect'
  if ( reconnect != -1 ) self->connection.reconnect = reconnect;
 ^
error: command 'i686-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 


Cheers,

Andreas


python-mysqldb_1.3.10-1.log.gz
Description: application/gzip

Processed: Really merge

[Debian Bug Tracking System]

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

> reassign 919205 ruby-haml 5.0.4-1
Bug #919205 [src:ruby-html2haml] ruby-html2haml: missing build dependency on 
ruby-temple
Bug reassigned from package 'src:ruby-html2haml' to 'ruby-haml'.
No longer marked as found in versions ruby-html2haml/2.2.0-1.
Ignoring request to alter fixed versions of bug #919205 to the same values 
previously set
Bug #919205 [ruby-haml] ruby-html2haml: missing build dependency on ruby-temple
Marked as found in versions ruby-haml/5.0.4-1.
> forcemerge 919223 919205
Bug #919223 {Done: Cédric Boutillier } [ruby-haml] 
ruby-haml-contrib: missing build dependency on ruby-temple
Bug #919205 [ruby-haml] ruby-html2haml: missing build dependency on ruby-temple
Marked Bug as done
Marked as fixed in versions ruby-haml/5.0.4-3.
Merged 919205 919223
> affects 919223 src:ruby-html2haml src:ruby-haml-contrib
Bug #919223 {Done: Cédric Boutillier } [ruby-haml] 
ruby-haml-contrib: missing build dependency on ruby-temple
Bug #919205 {Done: Cédric Boutillier } [ruby-haml] 
ruby-html2haml: missing build dependency on ruby-temple
Added indication that 919223 affects src:ruby-html2haml and 
src:ruby-haml-contrib
Added indication that 919205 affects src:ruby-html2haml and 
src:ruby-haml-contrib
> thanks
Stopping processing here.

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

Processed: transition: mariadb-10.3

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://release.debian.org/transitions/html/mysql-default.html
Bug #919395 [release.debian.org] transition: mariadb-10.3
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/mysql-default.html'.
> block -1 with 917758 919373 918387 919374 919375 918393 919379 919393
Bug #919395 [release.debian.org] transition: mariadb-10.3
919395 was not blocked by any bugs.
919395 was not blocking any bugs.
Added blocking bug(s) of 919395: 919379, 919375, 919393, 918387, 917758, 
918393, 919374, and 919373

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

Bug#918409: Bug #918409 in node-merge-descriptors marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #918409 in node-merge-descriptors 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/js-team/node-merge-descriptors/commit/26d545e635ec6ca2fb6a17d23c8224de963966ff


Add patch to update error strings in test

Closes: #918409


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918409

Processed: Bug #918409 in node-merge-descriptors marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918409 [src:node-merge-descriptors] node-merge-descriptors FTBFS with 
nodejs 10.15.0
Added tag(s) pending.

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

Processed: Re: Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Severity set to 'important' from 'critical'

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

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Michael Biebl]

Control: severity -1 important


I'm downgrading this to non-RC, as I'm not convinced this is actually a
bug in udev

Am 15.01.19 um 09:08 schrieb Axel Beckert:
> Control: found -1 239-15
> 
> Hi Michael,
> 
> Michael Biebl wrote:
>> Am 12.01.19 um 01:02 schrieb Axel Beckert:
>>> Control: reopen -1
>>> Control: found -1 240-3
>>
>>> *sigh* I'm sorry to say, but it just happened again with udev 240-3
>>> and kernel 4.20-1~exp1.
>>
>> Would be good to know, if it also happens with 239-15 or if it's caused
>> by some other update.
> 
> I just downloaded udev and libudev1 239-15 from
> https://snapshot.debian.org/, installed it and immediately afterwards
> ran "udevadm control --reload-rules" and everything was gone again.
> (Was running under kernel 4.20-1~exp1.)
> 
> After that I rebooted into 4.20-1~exp1 with the downgraded udev again,
> ran "udevadm control --reload-rules" directly after reboot and nothing
> (unexpected) happened.
> 
> Then I started to write this mail, doing not much more than logging in
> on the text console (despite X was running) using zsh, running
> ssh-agent, ssh-add and then ssh via autossh to connect to a screen
> session on some other host to write the mail with mutt.
> 
> After about 20 minutes of uptime I was about to send that mail and
> thought, I should just try running "udevadm control --reload-rules"
> once again: And it killed all processes again -- systemd-udevd has
> been started again, too:
> 
> ~ # ps auxwww | fgrep udev
> root 10696  0.0  0.0  13152  3592 ?S08:27   0:00 
> /lib/systemd/systemd-udevd
> root 11582  0.0  0.0   8144   892 tty1 R+   08:33   0:00 grep -F 
> --color=auto udev
> ~ # uptime
>  08:33:49 up 25 min,  2 users,  load average: 0.07, 0.15, 0.34
> 
> Unfortunately there is not much in the syslog (had to start rsyslog
> first again, too):
> 
> Jan 15 08:37:16 c6 kernel: [ 1717.930890] printk: systemd-udevd: 159 output 
> lines suppressed due to ratelimiting
> 
> I though didn't get rsyslog to drop the rate-limiting and I'm a little
> bit in a hurry at the moment.
> 
> Will report back later.
> 
> I must admit that I also had one crash/process killing yesterday where
> I can't say what triggered it. aptitude just finished starting up in
> TUI mode (inside screen started via ssh from remote) and I was
> starting to browse through the package list while the connection
> suddenly was lost (likely due to a killed sshd).


This all sounds, like udevd is not the root cause of all this, tbh,
especially since you also reproduced it with 239.
I think "udevadm trigger" trigger something when then causes another
component of your system to act this way.

> Some other facts gathered recently:
> 
> * With udev 239-15 the bootup lag is gone even without the "sleep 5".
> 
> * The "sleep 5" helped on another box (EeePC 900A with sysvinit) where
>   drivers weren't loaded anymore and had to be specified manually in
>   /etc/modules until the "sleep 5" was added.
> * memtest86 and memtest86+ just show an empty screen. Will try again
>   with grub's graphical mode disabled just to make sure the issue is
>   not triggered by some memory fault. Question would be then why I
>   could (within a reboot where it happened) reliably reproduce the
>   issue again and again. Will report any findings on this front.
> * As alternative I ran memtester for one night, no issues found. (Not
>   sure if it was able to test everything as the affected box has 64 GB
>   of RAM.)
> * If the issue happens while using X, there's no chance to switch back
>   to the text console with the getty to login again. The machine needs
>   a hard reboot via reset or power button then.
> 
>> Tbh, udevd or udevadm control --reload killing all processes, sounds
>> pretty strange.
> 
> Definitely.
> 
>> Can you also try to run udevd in debug mode to get a log from udevd (see
>> /etc/udev/udev.conf) and also an strace of the udevadm command.
> 
> I think I alread sent the strace, but forgot the debug mode. Enabled
> that when starting to write this mail, but it's currently caught by
> rsyslogd's rate-limiting, see above.

It's the kernel, which does the rate limiting. Add
log_buf_len=1M printk.devkmsg=on
to the kernel command line to turn off the ratelimiting and increase the
ring buffer.



-- 
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#916286: traverso: baseline violation on i386

[Remon Sijrier]

Hello,

By default Traverso has DETECT_HOST_CPU_FEATURES set to ON, will update
this to OFF, should fix the issue.

Will post updated tarball soon on traverso website, thanks

Remon

Bug#918409: marked as done (node-merge-descriptors FTBFS with nodejs 10.15.0)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 13:35:06 +
with message-id 
and subject line Bug#918409: fixed in node-merge-descriptors 1.0.1-2
has caused the Debian Bug report #918409,
regarding node-merge-descriptors FTBFS with nodejs 10.15.0
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.)


-- 
918409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-merge-descriptors
Version: 1.0.1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-merge-descriptors.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-merge-descriptors-1.0.1'
mocha --reporter spec --bail --check-leaks test/


  merge(dest, src)
arguments
  dest
1) should be required


  0 passing (52ms)
  1 failing

  1) merge(dest, src)
   arguments
 dest
   should be required:
 TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is 
ambiguous. The error message "argument dest is required" is identical to the 
message.
  at expectsError (assert.js:629:15)
  at Function.throws (assert.js:690:3)
  at Context. (test/merge.js:19:16)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-merge-descriptors
Source-Version: 1.0.1-2

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-merge-descriptors 
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, 15 Jan 2019 14:14:22 +0100
Source: node-merge-descriptors
Binary: node-merge-descriptors
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 918409
Description: 
 node-merge-descriptors - merge objects using descriptors
Changes:
 node-merge-descriptors (1.0.1-2) unstable; urgency=medium
 .
   * Team upload
   * Add gbp.conf
   * Add patch to update error strings in test (Closes: #918409)
   * Declare compliance with policy 4.3.0
   * Fix debian/copyright format url
   * Skip tests if "nocheck" is set
   * Add upstream/metadata file
Checksums-Sha1: 
 50cbf6d9f940c696f45a54695b7969bbcd3c9859 2166 
node-merge-descriptors_1.0.1-2.dsc
 080d32929b0f44fac9c7deabec468251d8018008 3080 
node-merge-descriptors_1.0.1-2.debian.tar.xz
Checksums-Sha256: 
 8bde7f7d0a9e7d685215ca2fb68156c287048d28427a1daf1143ea66c582fb24 2166 
node-merge-descriptors_1.0.1-2.dsc
 f2b79b202b71ad02a817b4b93be0ffab618d13fcacd876eb6b652a862dafb872 3080 
node-merge-descriptors_1.0.1-2.debian.tar.xz
Files: 
 d9cb1bf5a563a29888712ed7fb3355de 2166 javascript optional 
node-merge-descriptors_1.0.1-2.dsc
 2edbf6a7616fbd1c25fb44ed0f814bdd 3080 javascript optional 
node-merge-descriptors_1.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlw93icQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6V/TEACUcgSGGq9wHZkYtzvcgJw4c8/3dg4ZA2gV
bNYjtTkGS5tbrd3UfYUdVrnAvEZdO0rm1oiZYsd+r8y7zDty31YT+cLvE4WC0Hlx
Hfm5HoyarlE5OR0EZMpfS/ddYOGbwtfAfbyMootJBPV17d7TVS64wpb2rqHT7Efm
Djzfr5p01edkEqB+IWgoz5XKD7s2WoF0KQWdq+ocFq6amsHN3kjKJVQ+KXaG8+Mb
9vBKUSl3vBA9EBDHoJiQzYtuJmlTMRkMiI8oR8gLDewgqIiexZJQD8ghpamFpKvu
tjXqPY46IFt4CqKp7GAtnkP8DeXL1lZXSKpLK6m+caVdIzzjgjNotsWfMEQuTMaK
lfMPfw1F+/3sYQU2hguCPMPHNTj26l8WpQmfdBYoPNqsaiyNQLGGfO2X88WW8baf
Qg/dlUCKltdw0D9w7rG4Fr0Qli4pyniXui9qzHtPrIJhN5dUbaSBD

Bug#916286:

[Remon Sijrier]

New tarball link: http://traverso-daw.org/traverso-0.49.6.tar.gz

Bug#902945: marked as done (igraph: FTBFS with ARPACK 3.6)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 14:47:01 +
with message-id 
and subject line Bug#902760: fixed in igraph 0.7.1-4
has caused the Debian Bug report #902760,
regarding igraph: FTBFS with ARPACK 3.6
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.)


-- 
902760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: igraph
Version: 0.7.1-2.1
Severity: serious
Tags: ftbfs

Hi maintainer

Since the upload of arpack 3.6.0-1 to unstable, igraph FTBFS [1] with
the following test failures:

BLAS, LAPACK and ARPACK based functions

191: Basic BLAS functions (igraph_blas_*):   ok
192: Dense symmetric eigenvalues and eigenvectors (igraph_lapack_dsyevr): ok
193: Dense non-symmetric eigenvalues and eigenvectors (igraph_lapack_dgeev): ok
194: Dense non-symmetric eigenvalues and eigenvectors (igraph_lapack_dgeevx): ok
195: Solving linear systems with LU factorization (igraph_lapack_dgesv): ok
196: Upper Hessenberg transformation (igraph_lapack_dgehrd): ok
197: Eigenvector centrality (igraph_eigenvector_centrality): FAILED
(arpack.at:59)
198: Non-symmetric ARPACK solver (igraph_arpack_rnsolve): FAILED (arpack.at:66)

Bipartite graphs

199: Create bipartite graphs (igraph_create_bipartite): ok
200: Projection of bipartite graphs (igraph_bipartite_projection): ok

Centralization

201: Centralization (igraph_centralization_*):   FAILED
(centralization.at:26)

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/igraph.html
--- End Message ---
--- Begin Message ---
Source: igraph
Source-Version: 0.7.1-4

We believe that the bug you reported is fixed in the latest version of
igraph, 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.
Andreas Tille  (supplier of updated igraph 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: Tue, 15 Jan 2019 15:10:32 +0100
Source: igraph
Binary: libigraph0v5 libigraph0-dev
Architecture: source
Version: 0.7.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libigraph0-dev - library for creating and manipulating graphs - development 
files
 libigraph0v5 - library for creating and manipulating graphs
Closes: 902760
Changes:
 igraph (0.7.1-4) unstable; urgency=medium
 .
   * use a different starting vector for
 igraph_community_leading_eigenvector() to prevent errors
 with ARPACK 3.6.3 (Thanks for the patch to Tamás Nepusz)
 Closes: #902760
   * Drop Tamás Nepusz  from uploaders (Tamás, thanks
 for your previous work on the Debian package and the support you
 provide on upstream code)
   * debhelper 12
   * Standards-Version: 4.3.0
Checksums-Sha1:
 b9b915651287f1047c3b7fa3ca7a57d9083dd1a5 2101 igraph_0.7.1-4.dsc
 9815a35f54c4ef94601a06b0624a6e0e0b82a473 13024 igraph_0.7.1-4.debian.tar.xz
Checksums-Sha256:
 c079947c402bba1ac9e9e6c52c2a927cffd45810f544d510d265b02935c128f9 2101 
igraph_0.7.1-4.dsc
 8c890d7f6165480654b45f091680e409182e09ba2abece2467e9f32b08ca7812 13024 
igraph_0.7.1-4.debian.tar.xz
Files:
 6f35cd744dac72806a41432ae3c04c6c 2101 libs optional igraph_0.7.1-4.dsc
 9bc16c8b3da3926dc896fc47c19a1dc8 13024 libs optional 
igraph_0.7.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlw97JMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGyshAAgFmS8A3IAIHDXQ3y/tU+pP2fvdHW1KPX
stucNUNI64tuTYgYlNWhlRzpMHrCsat9i/ixcMAU2f0oCTUwAaG3eKsz8ch2axQR
dxxC30Vy0iHAihq3hUEvPuhNdZp4msHmZksA/zSafqWSuy3jTMClDhMX+SiulAXH
o6EQsEJK+5mC5lcaEg0f5EMqQTzlkG7hIUALC6Pw961feuIGCDkK0STW93f/ghYK
7u6b4knFA2ev2/jeNUgDIVKNLWiw3jdvC228ctsw3NOlBaTaAlAvOd7Xwc2Af/Jc
0S1qjPNojvUt73SwAzMfYjAk4aYcdxmOqunTz4Fyre/K9cLaD7Ad1PjOSOYWfMGc
qkUImiKtCZWVWIaIWwg5Q4pFbMvQa5kM1xNdVf3qInTZoJBEcryiNpl6CeDnw3IZ
9khnQaF6OaZlOtlariT+uf3j3jgf7zOPbdVdHuGzEGYfk0123PLCFB/y7j0XaMeF
60R+5fAtjzSSDRyu/7/RedM/dbdj+kVFjfUlWNGsVmnTEhjhzQKMtEgBXMxEgZCp
0XPZWocVu7AVJKt1HU1R8hW+1XT+kERxM/qGjfHM8zIL0st0jEoqfnrID7mitEPs
942yqtwFPfRoAqC3VBEITrhhaXVJ6+CiwQKJLO63CwMeQzdT4X0qi4SK6Z1+Uc9Q

Bug#902760: marked as done (python-igraph FTBFS with ARPACK 3.6)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 14:47:01 +
with message-id 
and subject line Bug#902760: fixed in igraph 0.7.1-4
has caused the Debian Bug report #902760,
regarding python-igraph FTBFS with ARPACK 3.6
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.)


-- 
902760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-igraph
Version: 0.7.1.post6-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-igraph&suite=sid

...
==
ERROR: testEigenvectorCentrality (igraph.test.structural.CentralityTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/structural.py", line 301, in 
testEigenvectorCentrality
cent = g.evcent()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testAuthorityScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testHubScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testAuthorityScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testHubScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
FAIL: testEigenvectorCentrality (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 35, in 
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for 
graph #%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #5: Error at 
arpack.c:944: ARPACK error, Could not build an Arnoldi factorization

==
FAIL: testEigenvectorCentrality (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 35, in 
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for 
graph #%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #3: Error at 
arpack.c:1174: ARPACK error, Could not build an Arnoldi factorization

--
Ran 307 tests in 9.738s

FAILED (failures=2, errors=5, skipped=3)
Test failed: 
error: Test failed: 
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: igraph
Source-Version: 0.7.1-4

We believe that the bug you reported is fixed in the latest version of
igraph, 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 commen

Bug#919379: marked as done (pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect')

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 15:04:46 +
with message-id 
and subject line Bug#919379: fixed in pmacct 1.7.2-1
has caused the Debian Bug report #919379,
regarding pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 
'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
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.)


-- 
919379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmacct
Version: 1.7.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

pmacct FTBFS with mariadb-10.3 in sid:

btool: compile:  gcc -DPACKAGE_NAME=\"pmacct\" -DPACKAGE_TARNAME=\"pmacct\" 
-DPACKAGE_VERSION=\"1.7.0\" "-DPACKAGE_STRING=\"pmacct 1.7.0\"" 
-DPACKAGE_BUGREPORT=\"pa...@pmacct.net\" -DPACKAGE_URL=\"\" -DPACKAGE=
\"pmacct\" -DVERSION=\"1.7.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNIST
D_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DLINUX=1 -DPROGNAME=1 
-DIM_LITTLE_ENDIAN=1 -DHAVE_L2=1 -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 
-DENABLE_IPV6=1 -DENABLE_PLABEL=1 -DHAVE_PCAP_H=1 -DHAVE_LIBPCAP=1 -DPCA
P_NOBPF=1 -DPCAP_TYPE_linux=1 -DWITH_MYSQL=1 -DWITH_PGSQL=1 -DWITH_SQLITE3=1 
-DWITH_RABBITMQ=1 -DWITH_ZMQ=1 -DWITH_KAFKA=1 -DWITH_GEOIPV2=1 -DWITH_JANSSON=1 
-DHAVE_LIBJANSSON=1 -DHAVE_JSON_OBJECT_UPDATE_MISSING=1
 -DHAVE_DLOPEN=1 -DHAVE_ZLIB=1 -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 
-DHAVE_GETOPT_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_U_INT64_T=1 
-DHAVE_U_INT32_T=1 -DHAVE_U_INT16_T=1 -DHAVE_U_INT8_T=1 -DHAVE_UI
NT64_T=1 -DHAVE_UINT32_T=1 -DHAVE_UINT16_T=1 -DHAVE_UINT8_T=1 
-DHAVE_64BIT_COUNTERS=1 -DENABLE_THREADS=1 -D_XOPEN_SOURCE=600 -D_GNU_SOURCE=1 
-DWITH_NFLOG=1 -DHAVE_TRAFFIC_BINS=1 -DHAVE_BGP_BINS=1 -DHAVE_BMP_BINS=
1 -DHAVE_ST_BINS=1 -DRETSIGTYPE=void -DHAVE_VSNPRINTF=1 -DHAVE_MALLOPT=1 
-DHAVE_TDESTROY=1 "-DCOMPILE_ARGS=\" '--build=i686-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/
man' '--infodir=\${prefix}/share/info' '--sysconfdir=/etc' 
'--localstatedir=/var' '--disable-silent-rules' 
'--libdir=\${prefix}/lib/i386-linux-gnu' 
'--libexecdir=\${prefix}/lib/i386-linux-gnu' '--disable-maintain
er-mode' '--disable-dependency-tracking' 
'--with-pgsql-includes=/usr/include/postgresql' '--enable-l2' '--enable-ipv6' 
'--enable-plabel' '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' 
'--enable-rabbitmq' '-
-enable-zmq' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' 
'--enable-64bit' '--enable-threads' '--enable-traffic-bins' '--enable-bgp-bins' 
'--enable-bmp-bins' '--enable-st-bins' '--enable-nflog' 'build_a
lias=i686-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/pmacct-1.7.0=. 
-fstack-protector-strong -Wformat -Werror=format-security' 
'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'\"" -I. -Wd
ate-time -D_FORTIFY_SOURCE=2 -I/usr/include/mariadb 
-I/usr/include/mariadb/mysql -I/usr/include/postgresql -isystem 
/usr/include/mit-krb5 -I/usr/include/pgm-5.2 
-I/usr/lib/i386-linux-gnu/pgm-5.2/include -I/usr/in
clude/i386-linux-gnu -I/usr/include/mariadb -I/usr/include/mariadb/mysql 
-I/usr/include/postgresql -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.2 
-I/usr/lib/i386-linux-gnu/pgm-5.2/include -O2 -g -O2 -fdebu
g-prefix-map=/build/pmacct-1.7.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -c mysql_plugin.c  -fPIC -DPIC -o 
.libs/libdaemons_la-mysql_plugin.o
In file included from mysql_plugin.c:30:
sql_common_m.c: In function 'SQL_SetENV_child':
sql_common_m.c:261:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->elap_time);
  ~^   
  %lu
sql_common_m.c:294:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->basetime);
  ~^   ~~~
  %lu
sql_common_m.c:305:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->timeslot);
   

Bug#919398: nim FTBFS on big endian

[Adrian Bunk]

Source: nim
Version: 0.19.2-1
Severity: serious
Tags: ftbfs

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

...
Hint:  [Link]
Hint: operation successful (30380 lines compiled; 8.532 sec total; 31.883MiB 
peakmem; Debug Build) [SuccessX]
Hint: /<>/.cache/nim/times_d/runnableExamples/times_examples6  
[Exec]
times_examples6.nim(5)   times_examples6
system.nim(3877) failedAssertImpl
system.nim(3870) raiseAssert
system.nim(2916) sysFatal
Error: unhandled exception: 
/<>/.cache/nim/times_d/runnableExamples/times_examples6.nim(5, 12) 
`$utc(fromUnix(0)) == "1970-01-01T00:00:00Z"`  [AssertionError]
Error: execution of an external program failed: 
'/<>/.cache/nim/times_d/runnableExamples/times_examples6 '
[Examples] failed: see 
/<>/.cache/nim/times_d/runnableExamples/times_examples6.nim

make[1]: *** [debian/rules:30: override_dh_auto_build] Error 1

Bug#919397: apcalc FTBFS on 32bit big endian

[Adrian Bunk]

Source: apcalc
Version: 2.12.7.2-1
Severity: serious
Tags: ftbfs

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

...
In file included from qmath.h:32,
 from cmath.h:32,
 from value.h:33,
 from calc.h:33,
 from file.c:39:
file.c: In function 'filepos2z':
zmath.h:85:46: error: incompatible types when assigning to type 'HALF' {aka 
'long unsigned int'} from type 'FILEPOS' {aka 'struct _G_fpos_t'}
 #define SWAP_HALF_IN_B32(dest, src) (*(dest) = *(src))
  ^
fposval.h:15:42: note: in expansion of macro 'SWAP_HALF_IN_B32'
 #define SWAP_HALF_IN_FILEPOS(dest, src)  SWAP_HALF_IN_B32(dest, src)
  ^~~~
file.c:1370:2: note: in expansion of macro 'SWAP_HALF_IN_FILEPOS'
  SWAP_HALF_IN_FILEPOS(ret.v, &pos);
  ^~~~
make[1]: *** [Makefile:2364: file.o] Error 1

Bug#919399: FTBFS: undefined reference to makedev

[Ritesh Raj Sarraf]

Source: cowdancer
Version: 0.87
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Content-Type: multipart/mixed; boundary="===1317036836604284426=="
MIME-Version: 1.0
From: Ritesh Raj Sarraf 
To: Debian Bug Tracking System 
Subject: FTBFS: undefined reference to makedev
Message-ID: 
<154756077354.13753.2447109323940488229.report...@priyasi.researchut.com>
X-Mailer: reportbug 7.5.1
Date: Tue, 15 Jan 2019 19:29:33 +0530
X-Debbugs-Cc: r...@debian.org

This is a multi-part MIME message sent by reportbug.


--===1317036836604284426==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

U291cmNlOiBjb3dkYW5jZXIKVmVyc2lvbjogMC44NwpTZXZlcml0eTogc2VyaW91cwpUYWdzOiBw
YXRjaApKdXN0aWZpY2F0aW9uOiBmYWlscyB0byBidWlsZCBmcm9tIHNvdXJjZSAoYnV0IGJ1aWx0
IHN1Y2Nlc3NmdWxseSBpbiB0aGUgcGFzdCkKCgpsaWJ0b29sOiBjb21waWxlOiAgZ2NjIC1EUEFD
S0FHRV9OQU1FPVwiY293ZGFuY2VyXCIgLURQQUNLQUdFX1RBUk5BTUU9XCJjb3dkYW5jZXJcIiAt
RFBBQ0tBR0VfVkVSU0lPTj1cIjAuODdcIiAiLURQQUNLQUdFX1NUUklORz1cImNvd2RhbmNlciAw
Ljg3XCIiIC1EUEFDS0FHRV9CVUdSRVBPUlQ9XCJcIiAtRFBBQ0tBR0VfVVJMPVwiXCIgLURQQUNL
QUdFPVwiY293ZGFuY2VyXCIgLURWRVJTSU9OPVwiMC44N1wiIC1EU1REQ19IRUFERVJTPTEgLURI
QVZFX1NZU19UWVBFU19IPTEgLURIQVZFX1NZU19TVEFUX0g9MSAtREhBVkVfU1RETElCX0g9MSAt
REhBVkVfU1RSSU5HX0g9MSAtREhBVkVfTUVNT1JZX0g9MSAtREhBVkVfU1RSSU5HU19IPTEgLURI
QVZFX0lOVFRZUEVTX0g9MSAtREhBVkVfU1RESU5UX0g9MSAtREhBVkVfVU5JU1REX0g9MSAtREhB
VkVfRExGQ05fSD0xIC1ETFRfT0JKRElSPVwiLmxpYnMvXCIgLUkuIC1XZGF0ZS10aW1lIC1EX0ZP
UlRJRllfU09VUkNFPTIgLWZuby1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNy
L2xpYi9jb3dkYW5jZXIvbGliY293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1h
cD0vYnVpbGQvY293ZGFuY2VyLTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3Jt
YXQgLVdlcnJvcj1mb3JtYXQtc2VjdXJpdHkgLWMgY293ZGFuY2VyLmMgLW8gbGliY293ZGFuY2Vy
X2xhLWNvd2RhbmNlci5vID4vZGV2L251bGwgMj4mMQpsaWJ0b29sOiBsaW5rOiBnY2MgLWZuby1z
dHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGliY293
ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2VyLTAu
ODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQtc2Vj
dXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBjb3didWlsZGVyIGNvd2J1
aWxkZXIubyBwYXJhbWV0ZXIubyBmb3JrZXhlYy5vIGlsaXN0Y3JlYXRlLm8gbWFpbi5vIGNvd2J1
aWxkZXJfdXRpbC5vIGxvZy5vICAtbGRsIC1sbmN1cnNlcwpsaWJ0b29sOiBsaW5rOiBnY2MgLWZu
by1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGli
Y293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2Vy
LTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQt
c2VjdXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBxZW11YnVpbGRlciBx
ZW11YnVpbGRlci1xZW11YnVpbGRlci5vIHFlbXVidWlsZGVyLXBhcmFtZXRlci5vIHFlbXVidWls
ZGVyLWZvcmtleGVjLm8gcWVtdWJ1aWxkZXItcWVtdWlwc2FuaXRpemUubyBxZW11YnVpbGRlci1x
ZW11YXJjaC5vIHFlbXVidWlsZGVyLWZpbGUubyBxZW11YnVpbGRlci1tYWluLm8gcWVtdWJ1aWxk
ZXItbG9nLm8gIC1sZGwgLWxuY3Vyc2VzCi91c3IvYmluL2xkOiBxZW11YnVpbGRlci1xZW11YXJj
aC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJjaF9zZXJpYWxkZXZpY2UnOgouL3FlbXVh
cmNoLmM6NjA6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmluL2xkOiAu
L3FlbXVhcmNoLmM6NjI6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmlu
L2xkOiBxZW11YnVpbGRlci1xZW11YXJjaC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJj
aF9kZXZpY2VzJzoKLi9xZW11YXJjaC5jOjg1OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRvIGBtYWtl
ZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg3OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRv
IGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg5OiB1bmRlZmluZWQgcmVmZXJl
bmNlIHRvIGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogcWVtdWJ1aWxkZXItcWVtdWFyY2gubzouL3Fl
bXVhcmNoLmM6OTE6IG1vcmUgdW5kZWZpbmVkIHJlZmVyZW5jZXMgdG8gYG1ha2VkZXYnIGZvbGxv
dwpjb2xsZWN0MjogZXJyb3I6IGxkIHJldHVybmVkIDEgZXhpdCBzdGF0dXMKbWFrZVsxXTogKioq
IFtNYWtlZmlsZTo5OTY6IHFlbXVidWlsZGVyXSBFcnJvciAxCm1ha2VbMV06ICoqKiBXYWl0aW5n
IGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCm1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5ICcvYnVp
bGQvY293ZGFuY2VyLTAuODcnCmRoX2F1dG9fYnVpbGQ6IG1ha2UgLWo0IHJldHVybmVkIGV4aXQg
Y29kZSAyCm1ha2U6ICoqKiBbZGViaWFuL3J1bGVzOjY6IGJpbmFyeV0gRXJyb3IgMgpkcGtnLWJ1
aWxkcGFja2FnZTogZXJyb3I6IGRlYmlhbi9ydWxlcyBiaW5hcnkgc3VicHJvY2VzcyByZXR1cm5l
ZCBleGl0IHN0YXR1cyAyCkk6IGNvcHlpbmcgbG9jYWwgY29uZmlndXJhdGlvbgpFOiBGYWlsZWQg
YXV0b2J1aWxkaW5nIG9mIHBhY2thZ2UKSTogdW5tb3VudGluZyAvdmFyL2NhY2hlL2FwdC9hcmNo
aXZlcy8gZmlsZXN5c3RlbQpJOiB1bm1vdW50aW5nIGRldi9wdG14IGZpbGVzeXN0ZW0KSTogdW5t
b3VudGluZyBkZXYvcHRzIGZpbGVzeXN0ZW0KSTogdW5tb3VudGluZyBkZXYvc2htIGZpbGVzeXN0
ZW0KSTogdW5tb3VudGluZyBwcm9jIGZpbGVzeXN0ZW0KSTogdW5tb3VudGluZyBzeXMgZmlsZXN5
c3RlbQpJOiBjbGVhbmluZyB0aGUgYnVpbGQgZW52IApJOiByZW1vdmluZyBkaXJlY3RvcnkgL3Rt
cC8vOTUxNCBhbmQgaXRzIHN1YmRpcmVjdG9yaWVzCjE5OjE5IOKZkuKZkuKZkiAgICDimLkg8J+Y
nz0+IDEgIAoKCgoKCi0tIFN5c3RlbSBJbmZvcm1hdGlvbjoKRGViaWFuIFJlbGVhc2U6IGJ1c3Rl
ci9zaWQKICBBUFQgcHJlZmVycyB0ZXN0aW5nCiAgQVBUIHBvbGljeTogKDkwMCwgJ3Rlc3Rpbmcn
KSwgKDUwMCwgJ3Vuc3RhYmxlJyksICgxLCAnZXhwZXJpbWVudGFsJykKQXJjaGl0ZWN0dXJlOiBh
bWQ2NCAoeDg2XzY0KQpGb3

Processed: Re: Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #919390 [udev] udev: network interface gets ID_NET_NAME even when NAME has 
been set by /etc/udev/rules.d/70-persistent-net.rules
Severity set to 'serious' from 'normal'
> forwarded -1 https://github.com/systemd/systemd/issues/11436
Bug #919390 [udev] udev: network interface gets ID_NET_NAME even when NAME has 
been set by /etc/udev/rules.d/70-persistent-net.rules
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/11436'.

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

Processed: tagging 919379

[Debian Bug Tracking System]

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

> tags 919379 + pending
Bug #919379 {Done: Bernd Zeimetz } [src:pmacct] pmacct: FTBFS 
with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct 
st_mysql'} has no member named 'reconnect'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug #919393 in python-mysqldb marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919393 [python-mysqldb] python-mysqldb: FTBFS with mariadb-10.3: 
_mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 
'reconnect'
Added tag(s) pending.

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

Bug#919393: Bug #919393 in python-mysqldb marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #919393 in python-mysqldb 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/python-team/modules/python-mysqldb/commit/e5f0fb5d9f68dc1ecd248b53490bc3e508bda64d


Add upstream patch to avoid FTBFS with recent MariaDB (Closes: #919393).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919393

Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

[Michael Biebl]

Am 15.01.19 um 14:59 schrieb Michal Hocko:

> [3.563937] e1000e :00:1f.6 lan0: renamed from eth0
> 

Seems I can reproduce the issue, so there is no need on your side to
further debug debug this.
Will forward this to the upstream bug tracker.

-- 
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

Processed: affects 918439

[Debian Bug Tracking System]

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

> affects 918439 src:cockpit
Bug #918439 {Done: Martin Pitt } [libssh-4] cockpit: FTBFS 
(failing tests)
Bug #918892 {Done: Martin Pitt } [libssh-4] libssh-4: 0.8.6 
breaks server-side host key algorithm negotiation
Added indication that 918439 affects src:cockpit
Added indication that 918892 affects src:cockpit
> thanks
Stopping processing here.

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

Bug#919393: marked as done (python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect')

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 16:20:33 +
with message-id 
and subject line Bug#919393: fixed in python-mysqldb 1.3.10-2
has caused the Debian Bug report #919393,
regarding python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 
'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
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.)


-- 
919393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mysqldb
Version: 1.3.10-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

python-mysqldb FTBFS with mariadb-10.3 in sid:

building '_mysql' extension
creating build
creating build/temp.linux-i386-2.7
i686-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/python-mysqldb-1.3.10=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Dversion_info=(1,3,10,'final',0) 
-D__version__=1.3.10 -I/usr/include/mariadb -I/usr/include/mariadb/mysql 
-I/usr/include/python2.7 -c _mysql.c -o build/temp.linux-i386-2.7/_mysql.o
In file included from _mysql.c:29:
/usr/include/mariadb/my_config.h:3:2: warning: #warning This file should not be 
included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
In file included from _mysql.c:30:
/usr/include/mariadb/mysql.h:440:3: warning: function declaration isn't a 
prototype [-Wstrict-prototypes]
   MYSQL_CLIENT_PLUGIN_HEADER
   ^~
_mysql.c: In function '_mysql_ConnectionObject_ping':
_mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 
'reconnect'
  if ( reconnect != -1 ) self->connection.reconnect = reconnect;
 ^
error: command 'i686-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 


Cheers,

Andreas


python-mysqldb_1.3.10-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-mysqldb
Source-Version: 1.3.10-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-mysqldb 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: Tue, 15 Jan 2019 16:56:13 +0100
Source: python-mysqldb
Binary: python-mysqldb python-mysqldb-dbg python3-mysqldb python3-mysqldb-dbg
Architecture: source amd64
Version: 1.3.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python-mysqldb - Python interface to MySQL
 python-mysqldb-dbg - Python interface to MySQL (debug extension)
 python3-mysqldb - Python interface to MySQL
 python3-mysqldb-dbg - Python interface to MySQL (debug extension)
Closes: 919393
Changes:
 python-mysqldb (1.3.10-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/changelog: Remove trailing whitespaces
 .
   [ Thomas Goirand ]
   * Update Standards-Version to 4.3.0.
   * Ran wrap-and-sort -bast.
   * Add upstream patch to avoid FTBFS with recent MariaDB (Closes: #919393).
Checksums-Sha1:
 a55e42e608d835a08860a4dbf9e9a7eb8cb69bd1 2420 python-mysqldb_1.3.10-2.dsc
 6f75fc8e0107a612d5c814760c09e5af5f0917c5 9592 
python-mysqldb_1.3.10-2.debian.tar.xz
 ff1a486f37f98f68d3d684f5f24524e2790e2ece 2 
python-mysqldb-dbg_1.3.10-2_amd64.deb
 361c7fa8be26fbc274b779a72a31f8802ffcb5a4 8379 
python-mysqldb_1.3.10-2_amd64.buildinfo
 d3021af41686035c6f5bbaf7532378270e7fa070 59112 
python-mysqldb_1.3.10-2_amd64.deb
 55f478413eef91d5a11c44d9b989d09d6afea988 33492 
python3-mysqldb-dbg_1.3.10-2_amd64.deb
 a8bc371912e8715bf357cbc65ad9a6d4d5d

Processed: forcibly merging 916062 919399

[Debian Bug Tracking System]

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

> forcemerge 916062 919399
Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] 
cowdancer FTBFS with glibc 2.28
Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] 
cowdancer FTBFS with glibc 2.28
Added tag(s) patch.
Bug #919399 [src:cowdancer] FTBFS: undefined reference to makedev
Marked Bug as done
Marked as fixed in versions cowdancer/0.88.
Added tag(s) ftbfs.
Merged 916062 919399
> thanks
Stopping processing here.

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

Processed: severity 919348 serious (Keep xfce4-screensaver out of testing)

[Debian Bug Tracking System]

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

> severity 919348 serious
Bug #919348 [xfce4-screensaver] xfce4-screensaver: Accidental upload to 
unstable while fixing bug #919151
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Santiago Vila]

Version: 2.2.0+dfsg-2

This version builds ok.

Thanks.

Bug#918503: glusterfs-common: support files not separated from shared library

[Patrick Matthäi]

tag #918503 + pending
thanks

Am 06.01.2019 um 20:46 schrieb Helmut Grohne:
> Package: glusterfs-common
> Version: 5.2-1
> Severity: serious
> Justification: 8.2
> Tags: patch
> Control: block 881526 by -1
>
> glusterfs-common combines shared libraries with a lot of other files and
> even a glusterfs user. Doing so violates the Debian policy section 8.2:
>
> | If your package contains files whose names do not change with each
> | change in the library shared object version, you must not put them in
> | the shared library package.
>
> It is quite evident that the python module, firewalld integration,
> logrotate.d snippet and many other files will not change with an soname
> bump. Given that other packages (e.g. fio) link libglusterfs0, it is
> evident that libglusterfs0 is not a private shared library. Therefore
> glusterfs-common violates a policy must.
>
> The attached patch fixes that. I'm filing it as a separate bug, because
> the policy violation is much narrower in scope than #881526 is.
>
> Helmut

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#919332: marked as done (casparcg-server: FTBFS in sid (cannot find -lpthreads))

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 17:20:06 +0100
with message-id <20190115162006.k5ynwpbg7zmdixod@nucold>
and subject line Re: Bug#919332: casparcg-server: FTBFS in sid (cannot find 
-lpthreads)
has caused the Debian Bug report #919332,
regarding casparcg-server: FTBFS in sid (cannot find -lpthreads)
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.)


-- 
919332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:casparcg-server
Version: 2.2.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --sourcedirectory=src --buildsystem=cmake
   dh_update_autotools_config -a -O--sourcedirectory=src -O--buildsystem=cmake
   dh_autoreconf -a -O--sourcedirectory=src -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/casparcg-server-2.2.0+dfsg'
dh_auto_configure -- -DENABLE_HTML=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DENABLE_HTML=OFF ../src
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_43642.dir/build.make:87: cmTC_43642] Error 1
make[3]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_43642/fast] Error 2
make[2]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

File 
/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include 

int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(&pthread_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}

Determining if the function pthread_create exists in the pthreads failed with 
the following output:
Change Dir: 
/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_24c32/fast"
make[2]: Entering directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_24c32.dir/build.make 
CMakeFiles/cmTC_24c32.dir/build
make[3]: Entering directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/casparcg-server-2.2.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.13/Modules/CheckFunctionExists.c
Linking C executable cmTC_24c32
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_24c32.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/casparcg-server-2.2.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-z,relro  
-rdynamic CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o  -o cmTC_24c32 
-lpthreads 
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_24c32.dir/build.make:87: cmTC_24c32] Error 1
make[3]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_24c32/fast] Error 2
make[2]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAK

Processed: Re: Bug#918503: glusterfs-common: support files not separated from shared library

[Debian Bug Tracking System]

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

> tag #918503 + pending
Bug #918503 [glusterfs-common] glusterfs-common: support files not separated 
from shared library
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: stardict: FTBFS with mariadb-10.3: wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope

[Debian Bug Tracking System]

Processing control commands:

> block 919395 with -1 918394
Bug #919395 [release.debian.org] transition: mariadb-10.3
919395 was blocked by: 919393 918387 917758 918393 919374 919373 919379 919375
919395 was not blocking any bugs.
Added blocking bug(s) of 919395: 918394 and 919408

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

Bug#919408: stardict: FTBFS with mariadb-10.3: wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope

[Andreas Beckmann]

Source: stardict
Version: 3.0.6-0.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 919395 with -1 918394

Hi,

stardict FTBFS with mariadb-10.3 in sid:

g++ -DHAVE_CONFIG_H -I. -I..  -Wall -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/us
r/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/libpn
g16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid 
-I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I.. -I.. 
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -Wdate-time -D
_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/build/stardict-3.0.6=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
wikipediaImage-wikipediaImage.o `test -f 'wikipediaImage.cpp' || echo './'`wiki
pediaImage.cpp
wikipediaImage.cpp: In function 'void dump_file()':
wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope
  if (!mysql_real_connect(&mysql, CONN_HOST , CONN_USER , CONN_PASS, NULL , 
MYSQL_PORT, NULL, 0))

^~
wikipediaImage.cpp:34:76: note: suggested alternative: 'MYSQL_STMT'
  if (!mysql_real_connect(&mysql, CONN_HOST , CONN_USER , CONN_PASS, NULL , 
MYSQL_PORT, NULL, 0))

^~

MYSQL_STMT
make[5]: *** [Makefile:2162: wikipediaImage-wikipediaImage.o] Error 1


Cheers,

Andreas


stardict_3.0.6-0.2.log.gz
Description: application/gzip

Bug#919406: kdiff3 FTBFS: missing -latomic

[Helmut Grohne]

Source: kdiff3
Version: 1.7.90-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

While conducting cross build tests, I found that kdiff3 fails to build
from source natively on armel, mips and mipsel due to missing symbols
that are present in -latomic, e.g.:

| cd /<>/obj-mipsel-linux-gnu/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/kdiff3.dir/link.txt --verbose=1
| /usr/bin/mipsel-linux-gnu-g++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-exceptions -Wall 
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -Wall -Wduplicated-cond 
-Wduplicated-branches -Wshadow  -Wl,--enable-new-dtags -Wl,-z,relro 
-Wl,--as-needed -rdynamic CMakeFiles/kdiff3.dir/main.cpp.o 
CMakeFiles/kdiff3.dir/kdiff3_shell.cpp.o 
CMakeFiles/kdiff3.dir/kdiff3_part.cpp.o CMakeFiles/kdiff3.dir/kdiff3.cpp.o 
CMakeFiles/kdiff3.dir/directorymergewindow.cpp.o 
CMakeFiles/kdiff3.dir/merger.cpp.o CMakeFiles/kdiff3.dir/pdiff.cpp.o 
CMakeFiles/kdiff3.dir/difftextwindow.cpp.o CMakeFiles/kdiff3.dir/diff.cpp.o 
CMakeFiles/kdiff3.dir/optiondialog.cpp.o 
CMakeFiles/kdiff3.dir/mergeresultwindow.cpp.o 
CMakeFiles/kdiff3.dir/fileaccess.cpp.o 
CMakeFiles/kdiff3.dir/gnudiff_analyze.cpp.o 
CMakeFiles/kdiff3.dir/gnudiff_io.cpp.o 
CMakeFiles/kdiff3.dir/gnudiff_xmalloc.cpp.o CMakeFiles/kdiff3.dir/common.cpp.o 
CMakeFiles/kdiff3.dir/smalldialogs.cpp.o CMakeFiles/kdiff3.dir/progress.cpp.o 
CMakeFiles/kdiff3.dir/ProgressProxyExtender.cpp.o 
CMakeFiles/kdiff3.dir/PixMapUtils.cpp.o 
CMakeFiles/kdiff3.dir/MergeFileInfos.cpp.o CMakeFiles/kdiff3.dir/Utils.cpp.o 
CMakeFiles/kdiff3.dir/selection.cpp.o CMakeFiles/kdiff3.dir/cvsignorelist.cpp.o 
CMakeFiles/kdiff3.dir/kdiff3_autogen/mocs_compilation.cpp.o  -o kdiff3 
/usr/lib/mipsel-linux-gnu/libKF5Parts.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5KIOWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5KIOCore.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Crash.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5JobWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5Concurrent.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5XmlGui.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5PrintSupport.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libQt5Network.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5TextWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5IconThemes.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Service.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Completion.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5ConfigWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5ConfigGui.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5ConfigCore.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5Xml.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5I18n.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5WidgetsAddons.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Codecs.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Auth.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5CoreAddons.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5DBus.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5SonnetUi.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5Widgets.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libQt5Gui.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libQt5Core.so.5.11.3 
| /usr/lib/gcc-cross/mipsel-linux-gnu/8/../../../../mipsel-linux-gnu/bin/ld: 
CMakeFiles/kdiff3.dir/progress.cpp.o: undefined reference to symbol 
'__atomic_load_8@@LIBATOMIC_1.0'
| /usr/lib/gcc-cross/mipsel-linux-gnu/8/../../../../mipsel-linux-gnu/bin/ld: 
//usr/lib/mipsel-linux-gnu/libatomic.so.1: error adding symbols: DSO missing 
from command line
| collect2: error: ld returned 1 exit status
| make[3]: *** [src/CMakeFiles/kdiff3.dir/build.make:447: src/kdiff3] Error 1
| make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:309: src/CMakeFiles/kdiff3.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-mipsel-linux-gnu'
| make[1]: *** [Makefile:144: all] Error 2
| make[1]: Leaving directory '/<>/obj-mipsel-linux-gnu'
| make: *** [/usr/share/cdbs/1/class/makefile.mk:77: 
debian/stamp-makefile-build] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut

Processed: severity of 919363 is serious

[Debian Bug Tracking System]

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

> severity 919363 serious
Bug #919363 [src:lua5.2] lua5.2 ftbfs in unstable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#919341: marked as done (libtool-bin: amd64 /usr/bin/libtool is a zero byte file)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 16:50:59 +
with message-id 
and subject line Bug#919341: fixed in libtool 2.4.6-8
has caused the Debian Bug report #919341,
regarding libtool-bin: amd64 /usr/bin/libtool is a zero byte file
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.)


-- 
919341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtool-bin
Version: 2.4.6-7
Severity: serious
File: /usr/bin/libtool

The amd64 package, the only one not built on a buildd, contains a
zero-byte /usr/bin/libtool.  This makes it completely non-functional.

$ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
drwxr-xr-x root/root 0 2019-01-12 09:10 ./
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/
-rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/doc/libtool-bin/
-rw-r--r-- root/root  9329 2019-01-12 09:10 
./usr/share/doc/libtool-bin/changelog.Debian.gz
-rw-r--r-- root/root342562 2015-02-15 12:15 
./usr/share/doc/libtool-bin/changelog.gz
-rw-r--r-- root/root  1976 2019-01-12 09:10 
./usr/share/doc/libtool-bin/copyright
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/man/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/man/man1/
-rw-r--r-- root/root20 2019-01-12 09:10 
./usr/share/man/man1/libtool.1.gz

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

Kernel: Linux 4.19.0-1-amd64 (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)
LSM: AppArmor: enabled

Versions of packages libtool-bin depends on:
ii  libtool  2.4.6-7

libtool-bin recommends no packages.

libtool-bin suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libtool
Source-Version: 2.4.6-8

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated libtool 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: Tue, 15 Jan 2019 13:42:46 +
Source: libtool
Binary: libtool libtool-bin libtool-doc libltdl7 libltdl-dev
Architecture: source amd64 all
Version: 2.4.6-8
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libltdl-dev - System independent dlopen wrapper for GNU libtool
 libltdl7   - System independent dlopen wrapper for GNU libtool
 libtool- Generic library support script
 libtool-bin - Generic library support script (libtool binary)
 libtool-doc - Generic library support script
Closes: 918588 919341
Changes:
 libtool (2.4.6-8) unstable; urgency=medium
 .
   * Fix Typos in sed expressions in d/rules. Closes: #919341
   * Close bug fixed in previous release. Closes: #918588
Checksums-Sha1:
 f96b48f56caf66250db55725360dfe03e73b171e 2479 libtool_2.4.6-8.dsc
 42aefb476baff9ba2816bbff4d8ac709a66e0722 48384 libtool_2.4.6-8.debian.tar.xz
 3ec42758329ccaa75e89ad5dba7b84555db41064 161960 libltdl-dev_2.4.6-8_amd64.deb
 7436b9c3cef2acfa9601f7fe217542a46f1f2012 46820 
libltdl7-dbgsym_2.4.6-8_amd64.deb
 32a89c9878e58948a317f6951ee764b9e0a95466 389928 libltdl7_2.4.6-8_amd64.deb
 e3737e4e8bf9c60700f0c34ea37626d02f0d4912 431308 libtool-bin_2.4.6-8_amd64.deb
 f8f1a55c77e48aafccd43fb17c219425b348beef 582288 libtool-doc_2.4.6-8_all.deb
 fa54656deca22eb74f1b2484167f725d30533bf6 546744 libtool_2.4.6-8_all.deb
 62d3af3127fb81409c72f7cf8c3259332015ed82 7138 libtool_2.4.6-8_amd64.buildinfo
Checksums-Sha256:
 a11bd465bcb30ae

Bug#918588: marked as done (libtool: generated libtool script is broken, affecting build on AIX)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 16:50:59 +
with message-id 
and subject line Bug#918588: fixed in libtool 2.4.6-8
has caused the Debian Bug report #918588,
regarding libtool: generated libtool script is broken, affecting build on AIX
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.)


-- 
918588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtool
Version: 2.4.6-6
Severity: serious

There's a major quoting issue in a recent change of libtool.
This makes the MPFR build fail on AIX:

$ make
Making all in doc
Target "all" is up to date.
Making all in src
make  all-am
/bin/sh ../libtool  --tag=CC--mode=compile 
/tmp/mpfrtests-vinc17-11403832/mpfr-4.0.2-rc1/compile gcc -DMPFR_WANT_ASSERT=2 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DLT_OBJDIR=\".libs/\" 
-DHAVE_DOUBLE_IEEE_BIG_ENDIAN=1 -DHAVE_BIG_ENDIAN=1 -DTIME_WITH_SYS_TIME=1 
-DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 
-DHAVE_STRUCT_LCONV_DECIMAL_POINT=1 -DHAVE_STRUCT_LCONV_THOUSANDS_SEP=1 
-DHAVE_ALLOCA_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 
-DHAVE_SIGNAL=1 -DHAVE_SIGACTION=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 
-DMPFR_HAVE_INTMAX_MAX=1 -DMPFR_PRINTF_MAXLM=\"j\" -DMPFR_HAVE_NORETURN=1 
-DMPFR_HAVE_BUILTIN_UNREACHABLE=1 -DMPFR_HAVE_CONSTRUCTOR_ATTR=1 
-DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DMPFR_HAVE_FESETROUND=1 
-DHAVE_DENORMS=1 -DHAVE_DENORMS_FLT=1 -DHAVE_SIGNEDZ=1 -DHAVE_ROUND=1 
-DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 
-DHAVE_LDOUBLE_IS_DOUBLE=1 -DMPFR_USE_STATIC_ASSERT=1 -DHAVE_CLOCK_GETTIME=1 
-DHAVE_ATTRIBUTE_MODE=1 -DPRINTF_L=1 -DPRINTF_T=1 -DPRINTF_GROUPFLAG=1 
-DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -DHAVE___GMPN_INVERT_LIMB=1 
-DMPFR_LONG_WITHIN_LIMB=1 -DHAVE_GETRUSAGE=1  -I. -I../../mpfr-4.0.2-rc1/src   
-I/opt/cfarm/gmp-latest/include   -Wall -Wmissing-prototypes -Wpointer-arith 
-O2 -pedantic -maix64 -mpowerpc64 -mtune=power8 -MT exceptions.lo -MD -MP -MF 
.deps/exceptions.Tpo -c -o exceptions.lo ../../mpfr-4.0.2-rc1/src/exceptions.c
libtool: compile:  /tmp/mpfrtests-vinc17-11403832/mpfr-4.0.2-rc1/compile gcc 
-DMPFR_WANT_ASSERT=2 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 "" 
-DHAVE_DOUBLE_IEEE_BIG_ENDIAN=1 -DHAVE_BIG_ENDIAN=1 -DTIME_WITH_SYS_TIME=1 
-DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 
-DHAVE_STRUCT_LCONV_DECIMAL_POINT=1 -DHAVE_STRUCT_LCONV_THOUSANDS_SEP=1 
-DHAVE_ALLOCA_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 
-DHAVE_SIGNAL=1 -DHAVE_SIGACTION=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 
-DMPFR_HAVE_INTMAX_MAX=1 "" -DMPFR_HAVE_NORETURN=1 
-DMPFR_HAVE_BUILTIN_UNREACHABLE=1 -DMPFR_HAVE_CONSTRUCTOR_ATTR=1 
-DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DMPFR_HAVE_FESETROUND=1 
-DHAVE_DENORMS=1 -DHAVE_DENORMS_FLT=1 -DHAVE_SIGNEDZ=1 -DHAVE_ROUND=1 
-DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 
-DHAVE_LDOUBLE_IS_DOUBLE=1 -DMPFR_USE_STATIC_ASSERT=1 -DHAVE_CLOCK_GETTIME=1 
-DHAVE_ATTRIBUTE_MODE=1 -DPRINTF_L=1 -DPRINTF_T=1 -DPRINTF_GROUPFLAG=1 
-DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -DHAVE___GMPN_INVERT_LIMB=1 
-DMPFR_LONG_WITHIN_LIMB=1 -DHAVE_GETRUSAGE=1 -I. -I../../mpfr-4.0.2-rc1/src 
-I/opt/cfarm/gmp-latest/include -Wall -Wmissing-prototypes -Wpointer-arith -O2 
-pedantic -maix64 -mpowerpc64 -mtune=power8 -MT exceptions.lo -MD -MP -MF 
.deps/exceptions.Tpo -c ../../mpfr-4.0.2-rc1/src/exceptions.c  -fPIC -DPIC -o 
.libs/exceptions.o
gcc: error: : No such file or directory
gcc: error: : No such file or directory

See, the -DLT_OBJDIR=\".libs/\" and -DMPFR_PRINTF_MAXLM=\"j\" have
been transformed to "".

When I do a diff on the libtool script between a working version
(based on 2.4.6-2) and a buggy version (based on 2.4.6-6), I can
see a new function func_quote. This might be related. I've attached
the diff.

In the changelog, I can see:

libtool (2.4.6-6) unstable; urgency=medium

  * Undo broken patch inclusion. Closes: #910076
  * Disable refactor patch 0012-funclib-refactor-quoting-methods-a-bit.patch
that breaks pkgs  on AIX (no bash optimization). Closes: #900276
  * Add build-dep on libltdl-dev for test 102

but apparently that wasn't enough.

-- 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.18.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UT

Processed: scikit-learn: binary-any FTBFS

[Debian Bug Tracking System]

Processing control commands:

> block 907806 by -1
Bug #907806 {Done: Yangfl } [src:scikit-learn] 
scikit-learn: FTBFS in buster/sid (could not import 'distributed')
907806 was blocked by: 911830
907806 was not blocking any bugs.
Added blocking bug(s) of 907806: 919409

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

Bug#919409: scikit-learn: binary-any FTBFS

[Adrian Bunk]

Source: scikit-learn
Version: 0.20.1+dfsg-2
Severity: serious
Tags: ftbfs
Control: block 907806 by -1

https://buildd.debian.org/status/package.php?p=scikit-learn&suite=sid

...
python3.7 -m sphinx -j 4 -D mathjax_path=MathJax.js -b html -d _build/doctrees  
  . _build/html/stable
/usr/bin/python3.7: No module named sphinx
make[1]: *** [Makefile:47: html] Error 1


Seems some package(s) have to move from Build-Depends-Indep
to Build-Depends.

Processed: Re: Bug#919399: FTBFS: undefined reference to makedev

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 916062 -1
Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] 
cowdancer FTBFS with glibc 2.28
Bug #919399 {Done: Mattia Rizzolo } [src:cowdancer] FTBFS: 
undefined reference to makedev
Bug #919399 {Done: Mattia Rizzolo } [src:cowdancer] FTBFS: 
undefined reference to makedev
Merged 916062 919399

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

Bug#919399: FTBFS: undefined reference to makedev

[James Clarke]

Control: forcemerge 916062 -1

> On 15 Jan 2019, at 14:05, Ritesh Raj Sarraf  wrote:
> 
> Source: cowdancer
> Version: 0.87

This was already reported as the bug mentioned above and fixed in the 0.88
upload a week ago. Also please don't forward raw multi-part MIME messages; you
end up with the horrendous mess that you can see below.

James

> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
> 
> Content-Type: multipart/mixed; boundary="===1317036836604284426=="
> MIME-Version: 1.0
> From: Ritesh Raj Sarraf 
> To: Debian Bug Tracking System 
> Subject: FTBFS: undefined reference to makedev
> Message-ID: 
> <154756077354.13753.2447109323940488229.report...@priyasi.researchut.com>
> X-Mailer: reportbug 7.5.1
> Date: Tue, 15 Jan 2019 19:29:33 +0530
> X-Debbugs-Cc: r...@debian.org
> 
> This is a multi-part MIME message sent by reportbug.
> 
> 
> --===1317036836604284426==
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: base64
> Content-Disposition: inline
> 
> U291cmNlOiBjb3dkYW5jZXIKVmVyc2lvbjogMC44NwpTZXZlcml0eTogc2VyaW91cwpUYWdzOiBw
> YXRjaApKdXN0aWZpY2F0aW9uOiBmYWlscyB0byBidWlsZCBmcm9tIHNvdXJjZSAoYnV0IGJ1aWx0
> IHN1Y2Nlc3NmdWxseSBpbiB0aGUgcGFzdCkKCgpsaWJ0b29sOiBjb21waWxlOiAgZ2NjIC1EUEFD
> S0FHRV9OQU1FPVwiY293ZGFuY2VyXCIgLURQQUNLQUdFX1RBUk5BTUU9XCJjb3dkYW5jZXJcIiAt
> RFBBQ0tBR0VfVkVSU0lPTj1cIjAuODdcIiAiLURQQUNLQUdFX1NUUklORz1cImNvd2RhbmNlciAw
> Ljg3XCIiIC1EUEFDS0FHRV9CVUdSRVBPUlQ9XCJcIiAtRFBBQ0tBR0VfVVJMPVwiXCIgLURQQUNL
> QUdFPVwiY293ZGFuY2VyXCIgLURWRVJTSU9OPVwiMC44N1wiIC1EU1REQ19IRUFERVJTPTEgLURI
> QVZFX1NZU19UWVBFU19IPTEgLURIQVZFX1NZU19TVEFUX0g9MSAtREhBVkVfU1RETElCX0g9MSAt
> REhBVkVfU1RSSU5HX0g9MSAtREhBVkVfTUVNT1JZX0g9MSAtREhBVkVfU1RSSU5HU19IPTEgLURI
> QVZFX0lOVFRZUEVTX0g9MSAtREhBVkVfU1RESU5UX0g9MSAtREhBVkVfVU5JU1REX0g9MSAtREhB
> VkVfRExGQ05fSD0xIC1ETFRfT0JKRElSPVwiLmxpYnMvXCIgLUkuIC1XZGF0ZS10aW1lIC1EX0ZP
> UlRJRllfU09VUkNFPTIgLWZuby1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNy
> L2xpYi9jb3dkYW5jZXIvbGliY293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1h
> cD0vYnVpbGQvY293ZGFuY2VyLTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3Jt
> YXQgLVdlcnJvcj1mb3JtYXQtc2VjdXJpdHkgLWMgY293ZGFuY2VyLmMgLW8gbGliY293ZGFuY2Vy
> X2xhLWNvd2RhbmNlci5vID4vZGV2L251bGwgMj4mMQpsaWJ0b29sOiBsaW5rOiBnY2MgLWZuby1z
> dHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGliY293
> ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2VyLTAu
> ODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQtc2Vj
> dXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBjb3didWlsZGVyIGNvd2J1
> aWxkZXIubyBwYXJhbWV0ZXIubyBmb3JrZXhlYy5vIGlsaXN0Y3JlYXRlLm8gbWFpbi5vIGNvd2J1
> aWxkZXJfdXRpbC5vIGxvZy5vICAtbGRsIC1sbmN1cnNlcwpsaWJ0b29sOiBsaW5rOiBnY2MgLWZu
> by1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGli
> Y293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2Vy
> LTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQt
> c2VjdXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBxZW11YnVpbGRlciBx
> ZW11YnVpbGRlci1xZW11YnVpbGRlci5vIHFlbXVidWlsZGVyLXBhcmFtZXRlci5vIHFlbXVidWls
> ZGVyLWZvcmtleGVjLm8gcWVtdWJ1aWxkZXItcWVtdWlwc2FuaXRpemUubyBxZW11YnVpbGRlci1x
> ZW11YXJjaC5vIHFlbXVidWlsZGVyLWZpbGUubyBxZW11YnVpbGRlci1tYWluLm8gcWVtdWJ1aWxk
> ZXItbG9nLm8gIC1sZGwgLWxuY3Vyc2VzCi91c3IvYmluL2xkOiBxZW11YnVpbGRlci1xZW11YXJj
> aC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJjaF9zZXJpYWxkZXZpY2UnOgouL3FlbXVh
> cmNoLmM6NjA6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmluL2xkOiAu
> L3FlbXVhcmNoLmM6NjI6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmlu
> L2xkOiBxZW11YnVpbGRlci1xZW11YXJjaC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJj
> aF9kZXZpY2VzJzoKLi9xZW11YXJjaC5jOjg1OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRvIGBtYWtl
> ZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg3OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRv
> IGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg5OiB1bmRlZmluZWQgcmVmZXJl
> bmNlIHRvIGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogcWVtdWJ1aWxkZXItcWVtdWFyY2gubzouL3Fl
> bXVhcmNoLmM6OTE6IG1vcmUgdW5kZWZpbmVkIHJlZmVyZW5jZXMgdG8gYG1ha2VkZXYnIGZvbGxv
> dwpjb2xsZWN0MjogZXJyb3I6IGxkIHJldHVybmVkIDEgZXhpdCBzdGF0dXMKbWFrZVsxXTogKioq
> IFtNYWtlZmlsZTo5OTY6IHFlbXVidWlsZGVyXSBFcnJvciAxCm1ha2VbMV06ICoqKiBXYWl0aW5n
> IGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCm1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5ICcvYnVp
> bGQvY293ZGFuY2VyLTAuODcnCmRoX2F1dG9fYnVpbGQ6IG1ha2UgLWo0IHJldHVybmVkIGV4aXQg
> Y29kZSAyCm1ha2U6ICoqKiBbZGViaWFuL3J1bGVzOjY6IGJpbmFyeV0gRXJyb3IgMgpkcGtnLWJ1
> aWxkcGFja2FnZTogZXJyb3I6IGRlYmlhbi9ydWxlcyBiaW5hcnkgc3VicHJvY2VzcyByZXR1cm5l
> ZCBleGl0IHN0YXR1cyAyCkk6IGNvcHlpbmcgbG9jYWwgY29uZmlndXJhdGlvbgpFOiBGYWlsZWQg
> YXV0b2J1aWxkaW5nIG9mIHBhY2thZ2UKSTogdW5tb3VudGluZyAvdmFyL2NhY2hlL2FwdC9hcmNo
> aXZlcy8gZmlsZXN5c3RlbQpJOiB1bm1vdW50aW5nIGRldi9wdG14IGZpbGVzeXN0ZW0KSTogdW5t
> b3VudGluZyBkZXYvcHRzIGZpbGVzeXN0ZW0KSTogdW5tb3VudGluZyBkZXYvc2htIGZpbGVzeXN0
> ZW0KSTogdW5tb3VudGluZyBwc

Bug#919356: Licensing of include/linux/hash.h

[Domenico Andreoli]

Hi Nadia,

  As part of the licensing assessment on pahole [0] that I am making for
Debian, I realized that file hash.h in both pahole [1] and the kernel
[2] comes without any licensing specification.

Could you please make an explicit choice and maybe provide patches?

Kind regards,
Domenico

[0] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/
[1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tree/hash.h
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/hash.h

-- 
3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13


signature.asc
Description: PGP signature

Bug#919326: msmtp: account default not found: no configuration file available

[Simon Deziel]

On 2019-01-14 6:03 p.m., Sergio Mendoza wrote:
>   Yes.  I have now checked and I have .msmtprc as a symlink.  If it is not
> a symlink then I have no problems and everything runs smooth.

Great, thanks Sergio.

>  In any case
> this is the output you asked for:
> 
> root@quetzalli:~# dmesg | grep apparmor | tail -n 20
> [1064151.025521] audit: type=1400 audit(1547506707.004:157): 
> apparmor="DENIED" operation="open" profile="/usr/bin/msmtp" 
> name="/home/sergio/Private/.msmtprc" pid=14560 comm="msmtp" 
> requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

This should eventually work even when ~/.msmtprc will be a symlink to
~/Private/.msmtprc. I hope the fix will land in the next package update [*].

> [1064177.994021] audit: type=1400 audit(1547506733.971:158): 
> apparmor="DENIED" operation="open" profile="/usr/bin/msmtp" 
> name="/home/sergio/mail/msmtp/log.txt" pid=14580 comm="msmtp" 
> requested_mask="ac" denied_mask="ac" fsuid=1000 ouid=1000
> [1064281.325901] audit: type=1400 audit(1547506837.302:159): 
> apparmor="DENIED" operation="open" profile="/usr/bin/msmtp" 
> name="/home/sergio/mail/msmtp/log.txt" pid=14656 comm="msmtp" 
> requested_mask="ac" denied_mask="ac" fsuid=1000 ouid=1000

This shows that msmtp was denied logging to ~/mail/msmtp/log.txt.

Unfortunately, this isn't a common location to for logs so it likely
won't be supported by the default base Apparmor profile. You have few
options to make it work though:

1) you can have it log to more usual locations like one of those:
  ~/.msmtp.log
  ~/.cache/msmtp/*.log
2) add this local override rule to /etc/apparmor.d/local/usr.bin.msmtp:
  owner @{HOME}/mail/msmtp/log.txt wk,
3) disable the Apparmor profile

1 would be preferable but for 2 and 3, please refer to the README.Debian
file for detailed instructions.

Regards,
Simon


*: https://salsa.debian.org/kolter/msmtp/merge_requests/3

Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

[Michal Hocko]

On Tue, Jan 15, 2019 at 02:36:46PM +0100, Michael Biebl wrote:
> Am 15.01.19 um 14:32 schrieb Michal Hocko:
> > On Tue, Jan 15, 2019 at 02:28:55PM +0100, Michael Biebl wrote:
[...]
> >> Have you made sure to rebuild the initramfs after changing the udev rule?
> > 
> > Hmm, I haven't but is this really important? My eth driver is built in
> > CONFIG_E1000E=y
> 
> Yes, you must update the initramfs so it contains
> /etc/udev/rules.d/70-persistent-net.rules,

I have checked my initrd and it seems to have that rule under
lib/udev/rules.d/70-persistent-net.rules

Besides that there is apparatently renaming from eth0->lan0 happening as
per kernel log mentioned earlier:

[3.563937] e1000e :00:1f.6 lan0: renamed from eth0

Anyway, I will try to regenerate and reboot later just to be sure.
Thanks!
-- 
Michal Hocko

Bug#919412: rng-tools: Build-Depends on cruft package libgcrypt11-dev

[Andreas Beckmann]

Source: rng-tools
Version: 5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

rng-tools/sid build-depends on libgcrypt11-dev. This was a
transitional package, please use libgcrypt20-dev instead.


Cheers,

Andreas

Bug#822586: Upstream status update

[Raphael Hertzog]

Hello,

just FYI since upstream was unable to port the code to the GObject
Introspection bindings, he started to rewrite the application in
C++ using GTKmm. This is happening in the "future" directory of the
upstream git repository (master branch) and the author shares
some progress information here:
https://www.giuspen.com/topic/status-of-the-development/

As of today, it seems that the C++ rewrite is able to display
content in read-only mode so it's not finished yet.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Processed: Re: Bug#919058: mate-utils: frequent parallel FTBFS

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #919058 {Done: Mike Gabriel } [src:mate-utils] 
mate-utils: frequent parallel FTBFS
'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 mate-utils/1.20.2-2.

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

Bug#919058: mate-utils: frequent parallel FTBFS

[Jeremy Bicha]

Control: reopen -1

Sadly, --no-parallel didn't work.

https://buildd.debian.org/status/package.php?p=mate-utils

Thanks,
Jeremy Bicha

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Andreas Beckmann]

Followup-For: Bug #919332
Control: retitle -1 casparcg-server: FTBFS: Xrandr library not found - required 
for GLFW


The relevant part from the build log seems to be

-- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so
CMake Error at CMakeModules/FindGLFW.cmake:146 (message):
  Xrandr library not found - required for GLFW
Call Stack (most recent call first):
  CMakeModules/Bootstrap_Linux.cmake:44 (FIND_PACKAGE)
  CMakeLists.txt:18 (INCLUDE)


-- Configuring incomplete, errors occurred!


Andreas

Processed: Re: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 casparcg-server: FTBFS: Xrandr library not found - required for 
> GLFW
Bug #919332 {Done: Santiago Vila } [src:casparcg-server] 
casparcg-server: FTBFS in sid (cannot find -lpthreads)
Changed Bug title to 'casparcg-server: FTBFS: Xrandr library not found - 
required for GLFW' from 'casparcg-server: FTBFS in sid (cannot find 
-lpthreads)'.

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

Bug#864178: marked as done (fsl-5.0-core: depends on no longer available fslview)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 17:34:38 +
with message-id 
and subject line Bug#864178: fixed in fsl 5.0.8-6
has caused the Debian Bug report #864178,
regarding fsl-5.0-core: depends on no longer available fslview
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.)


-- 
864178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fsl-5.0-core
Version: 5.0.8-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 fsl-5.0-core : Depends: fslview but it is not installable

fslview has been removed from the archive, see
https://bugs.debian.org/861330 for details.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: fsl
Source-Version: 5.0.8-6

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated fsl 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: Tue, 15 Jan 2019 16:42:15 +0100
Source: fsl
Binary: fsl fsl-5.0 fsl-core fsl-5.0-core
Architecture: source amd64 all
Version: 5.0.8-6
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 fsl- transitional dummy package
 fsl-5.0- transitional dummy package
 fsl-5.0-core - analysis tools for FMRI, MRI and DTI brain imaging
 fsl-core   - metapackage for the latest version of FSL
Closes: 804881 837361 864178
Changes:
 fsl (5.0.8-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yaroslav Halchenko ]
   * Add 'file' to Depends of fsl-5.0-core. Required by fslFixText utility
   * debian/fsl.sh - place FSL's bin path first (not the last) within adjusted
 $PATH (Closes: #804881)
   * debian/patches/up_in_compar to fix FTBFS of melodic on 17.04
 Closes: #837361
 .
   [ Michael Hanke ]
   * Move 'fslview' from a dependency into suggests. It can no longer be
 built in Debian unstable.
 Closes: #864178
 .
   [ Andreas Tille ]
   * Replace watch line pointing to alioth which does not exist any more
 by fake watch file
   * debhelper 9
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Fix call of overloaded 'round(float)' is ambiguous
   * Silence lintian about false positive spelling
   * fsl-5.0-core Depends: sensible-utils
   * Drop Encoding key from desktop file
   * Drop Debian menu file (since there is a desktop file)
   * hardening=+all
Checksums-Sha1:
 6e8a1fb0f0cc2a1558a1b7fa8bd00b1627bc6a8c 2421 fsl_5.0.8-6.dsc
 370cf2cb97ebb6d0a2b47a725054a5c411b068ea 42616 fsl_5.0.8-6.debian.tar.xz
 f539df5deca892fae38eaacee33dc9fead684c3a 153645380 
fsl-5.0-core-dbgsym_5.0.8-6_amd64.deb
 17300011f64f941bdd5c3ed27def50658dc888e2 8365888 fsl-5.0-core_5.0.8-6_amd64.deb
 2811268688cb53b220c2acf8cb1ef60720cb0f48 20028 fsl-5.0_5.0.8-6_all.deb
 3ef31da705273ee0880e6f04ca59b5fdc2358cfb 21192 fsl-core_5.0.8-6_all.deb
 edba08409ceabe90ecd0dec4c5837d259cf83dbd 21560 fsl_5.0.8-6_all.deb
 d4a008c2509ff77e7db0268520bb8d06f42bd560 14675 fsl_5.0.8-6_amd64.buildinfo
Checksums-Sha256:
 2de76e045a975189b5d44d229cd1130edba9b18621f74be1084a8e8a7dbada20 2421 
fsl_5.0.8-6.dsc
 53f61a818589f95b21db5997ae992fc895c1d1cd1d89ba01ffcc769e06d6a93f 42616 
fsl_5.0.8-6.debian.tar.xz
 5deef18a26980a6c5857e6d27dacf313f0757457787e44b26c9942738b7ca9ce 153645380 
fsl-5.0-core-dbgsym_5.0.8-6_amd64.deb
 fe5123e06e43d9b1206e65444773a15949f98c25bdfde913995f1a0cda89ca0e 8365888 
fsl-5.0-core_5.0.8-6_amd64.deb
 f1d10bcf8c859ce45852c378f7c523a53d4c8904cae548e920dbe79a54322c66 20028 
fsl-5.0_5.0.8-6_all.deb
 0d95b08f1e5a5b8a6b7a6e124e4d354b53205c0b00a11e89af3b1e3512f9a865 21192 
fsl-core_5.0.8-6_all.deb
 33e298e6ce439eb319a0ddb0395ef8ddb3f4c0695b9c8025280d78108a254f04 21560 
fsl_5.0.8-6_all.deb
 1d76a785f1c6091c8bef793c51a73e8cb4d58d6f50d758de2dd080588a3d3018 14675 
fsl_5.0.8-6_amd64.buildinfo
Files:
 d672af48

Bug#837361: marked as done (fsl: FTBFS with GCC 6: error: no match for 'operator>' (operand types are 'std::ifstream' and 'int'))

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 17:34:37 +
with message-id 
and subject line Bug#837361: fixed in fsl 5.0.8-6
has caused the Debian Bug report #837361,
regarding fsl: FTBFS with GCC 6: error: no match for 'operator>' (operand types 
are 'std::ifstream' and 'int')
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.)


-- 
837361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fsl
Version: 5.0.8-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

fsl FTBFS since the default compiler was switched to GCC 6:

[...]
g++ -g -O2 -fdebug-prefix-map=/build/fsl-5.0.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_LIBFREETYPE -fPIC -I/usr/include/nifti -I/usr/include/gifti -I/usr/i
nclude/newmat -I/build/fsl-5.0.8/extras/src/libprob 
-I/build/fsl-5.0.8/extras/src/libcprob -I/build/fsl-5.0.8/src   -O3 
-Wno-deprecated -ggdb -I/usr/include/newmat 
-I/build/fsl-5.0.8/extras/include/libprob -I/u
sr/include -I/usr/include -I/usr/include/libpng -I/usr/include -I. 
-I/build/fsl-5.0.8/include -I/build/fsl-5.0.8/include   -c -o meldata.o 
meldata.cc
meldata.cc: In member function 'void Melodic::MelodicData::est_smoothness()':
meldata.cc:997:12: error: no match for 'operator>' (operand types are 
'std::ifstream {aka std::basic_ifstream}' and 'int')
   if(in>0){
  ~~^~
[...]

(full log attached)

Andreas


fsl_5.0.8-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fsl
Source-Version: 5.0.8-6

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated fsl 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: Tue, 15 Jan 2019 16:42:15 +0100
Source: fsl
Binary: fsl fsl-5.0 fsl-core fsl-5.0-core
Architecture: source amd64 all
Version: 5.0.8-6
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 fsl- transitional dummy package
 fsl-5.0- transitional dummy package
 fsl-5.0-core - analysis tools for FMRI, MRI and DTI brain imaging
 fsl-core   - metapackage for the latest version of FSL
Closes: 804881 837361 864178
Changes:
 fsl (5.0.8-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yaroslav Halchenko ]
   * Add 'file' to Depends of fsl-5.0-core. Required by fslFixText utility
   * debian/fsl.sh - place FSL's bin path first (not the last) within adjusted
 $PATH (Closes: #804881)
   * debian/patches/up_in_compar to fix FTBFS of melodic on 17.04
 Closes: #837361
 .
   [ Michael Hanke ]
   * Move 'fslview' from a dependency into suggests. It can no longer be
 built in Debian unstable.
 Closes: #864178
 .
   [ Andreas Tille ]
   * Replace watch line pointing to alioth which does not exist any more
 by fake watch file
   * debhelper 9
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Fix call of overloaded 'round(float)' is ambiguous
   * Silence lintian about false positive spelling
   * fsl-5.0-core Depends: sensible-utils
   * Drop Encoding key from desktop file
   * Drop Debian menu file (since there is a desktop file)
   * hardening=+all
Checksums-Sha1:
 6e8a1fb0f0cc2a1558a1b7fa8bd00b1627bc6a8c 2421 fsl_5.0.8-6.dsc
 370cf2cb97ebb6d0a2b47a725054a5c411b068ea 42616 fsl_5.0.8-6.debian.tar.xz
 f539df5deca892fae38eaacee33dc9fead684c3a 153645380 
fsl-5.0-core-dbgsym_5.0.8-6_amd64.deb
 17300011f64f941bdd5c3ed27def50658dc888e2 8365888 fsl-5.0-core_5.0.8-6_amd64.deb
 2811268688cb53b220c2acf8cb1ef60720cb0f48 20028 fsl-5.0_5.0.8-6_all.deb
 3ef31da705273ee0880e6f04ca59b5fdc2358cfb 21192 fsl-core_5.0.8-6_all.deb
 edba08409ceabe90ecd0dec4c5837d259cf83dbd 21560 fsl_5.0.8-6_all.deb
 d4a008c2509ff77e7db0268520bb8d06f42bd560 14675 fsl_5.0.8-6_amd64.buildinfo
Checksums-Sha256:
 2de76e045a975189b5d44d229cd1130edba9b18621f74be1084a8e8a7dbada20 2421 
fsl

Processed: Re: Bug#919289: [Pkg-kde-extras] Bug#919289: kile: After upgrade, kile will not open until okular installed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #919289 [kile] kile: After upgrade, kile will not open until okular 
installed
Severity set to 'serious' from 'normal'

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

Processed: severity of 919291 is serious

[Debian Bug Tracking System]

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

> severity 919291 serious
Bug #919291 [crash] crash: invalid kernel virtual address / crash: cannot 
allocate any more memory!
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 919277 is serious

[Debian Bug Tracking System]

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

> severity 919277 serious
Bug #919277 [uucp] postinst failed on the recent upgrade because it required 
update-inetd
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Severity serious (keep xfce4-screensaver out of testing)

[Debian Bug Tracking System]

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

> severity 919348 serious
Bug #919348 [xfce4-screensaver] xfce4-screensaver: Accidental upload to 
unstable while fixing bug #919151
Ignoring request to change severity of Bug 919348 to the same value.
> thanks
Stopping processing here.

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

Bug#919415: isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev

[Andreas Beckmann]

Source: isight-firmware-tools
Version: 1.6-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

isight-firmware-tools build-depends on libgcrypt11-dev. This was a
transitional package, please use libgcrypt20-dev instead.

Andreas

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Ben Greear]

You might try adding this patch and disabling the oper-class IE:

http://lists.infradead.org/pipermail/hostap/2018-August/038792.html

I'd be curious to know if it fixes the problem.

Thanks,
Ben

On 1/14/19 4:35 PM, Different55 wrote:

On Monday, January 14, 2019 10:37 AM, Ben Greear  
wrote:


What is the model number of your home AP?

Thanks,
Ben


It is a Comtrend VR-3033




--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com

Bug#919103: fixed in libreoffice 1:6.1.4-4

[Cyril Brulebois]

Hi Rene,

Rene Engelhard  (2019-01-15):
>  libreoffice (1:6.1.4-4) unstable; urgency=medium
>  .
>* debian/control.in: bump recommends for apparmor to >= 2.13.1 and conflict
>  against apparmor (<< 2.13.1~) (closes: #918499)
>* debian/control.in, debian/rules: make apparmor recommends/conflicts
>  dependant on ENABLE_APPARMOR_PROFILES=y
>* debian/control.transitonals.in: add missing {misc:Depends} for -ogltrans
>* debian/control.kde*.in: Replaces: libreoffice-kde (<< 1:6.1.0~alpha1-1)
>  (closes: #919103)

FWIW, I've just confirmed that this makes the dist-upgrade successful
(trying an upgrade from stretch to unstable, instead of one from stretch
to buster, since libreoffice will need some time to build everywhere and
become a candidate for migration):

Result: KO RC=100 for 
cmd=/home/kibi/work/release-checks.git/scripts/upgrade-desktop-task stretch 
buster kde
Result: OK RC=0 for 
cmd=/home/kibi/work/release-checks.git/scripts/upgrade-desktop-task stretch 
unstable kde


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


signature.asc
Description: PGP signature