Bug#882141: Problem still happening even after upgrade

[Scott Kitterman]

On Tue, 06 Nov 2018 19:47:34 -0500 Scott Kitterman  
wrote:
> Would someone who is still having this problem please try the attached 
> configure-instance.sh in place of the installed version in /usr/lib/postfix?
> 
> This one avoids postmulti in every case and might actually work, but I have
> a hard time testing it.
> 
> Scott K

OK, tested it as best I could and we'll see if it works.

Scott K

Bug#915136: Follow-up

[Pirate Praveen]

Control: severity -1 important 

On Wed, 5 Dec 2018 13:16:29 +0100 
=?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?=  
wrote:
> There's any new data about this bug?

Since I can't reproduce it in multiple systems, I'm reducing the severity. Did 
you try 11.4.9?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: Re: Follow-up

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #915136 [gitlab] Gitlab: Error 503 loading some projects
Severity set to 'important' from 'grave'

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

Bug#916092: nullmailer: architecture specific test failures

[David Bremner]

Package: nullmailer
Version: 1:2.2-1
Severity: serious
Tags: upstream
Justification: ftbfs

nullmailer 2.2 should not transition to testing until we figure out what is 
going on with the test 

   Testing auth permanent failure with smtp

which seems to fail or hang on various architectures (but not amd64).

It seems possible replicate the hang on plummer (ppc64el
porterbox). This is a bit puzzling because on the pps64el buildd it
actually failed relatively quickly, rather than hanging until killed.

The test is using some tcp sockets on localhost according to netstat,
the connection is ESTABLISHED, but that's all I know at this point.


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

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

Versions of packages nullmailer depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.27-8
ii  libgnutls303.5.19-1+b1
ii  libstdc++6 8.2.0-9
ii  lsb-base   10.2018112800

nullmailer recommends no packages.

nullmailer suggests no packages.

-- debconf information excluded

Processed: Re: Bug#900160 closed by Dimitri John Ledkov (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.2)

[Debian Bug Tracking System]

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

> close 915287 1.0.7-4.2
Bug #915287 [src:ruby-eventmachine] ruby-eventmachine: B-D against libssl1.0-dev
Marked as fixed in versions ruby-eventmachine/1.0.7-4.2.
Bug #915287 [src:ruby-eventmachine] ruby-eventmachine: B-D against libssl1.0-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#915287: Bug#900160 closed by Dimitri John Ledkov (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.2)

[Dimitri John Ledkov]

close 915287 1.0.7-4.2
thanks

On Thu, 6 Dec 2018 14:05:22 +0100 Sebastian Andrzej Siewior
 wrote:
> On 2018-12-06 12:42:50 [+0100], gregor herrmann wrote:
> > On Wed, 05 Dec 2018 13:57:05 +, Debian Bug Tracking System wrote:
> >
> > >  ruby-eventmachine (1.0.7-4.2) unstable; urgency=medium
> > >  .
> > >* Non-maintainer upload.
> > >* Revert below upload and build with OpenSSL 1.1+.
> > >* Add a patch to clamp SSL version to TLS1.2, and allow using small
> > >  keys, as the rest of the codebase is not ready for TLS1.3. (Closes:
> > >  #900160)
> >
> > I guess this should have closes the cloned #915287 and not the
> > original #900160?
>
> I think so, too.
>

Yes!

Hopefully, I got my control commands right!

Bug#909978: marked as done (erlang-cuttlefish FTBFS with Erlang 21.1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 00:49:35 +
with message-id 
and subject line Bug#909978: fixed in erlang-cuttlefish 2.0.11+dfsg-4
has caused the Debian Bug report #909978,
regarding erlang-cuttlefish FTBFS with Erlang 21.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.)


-- 
909978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cuttlefish
Version: 2.0.11+dfsg-3
Severity: serious
Tags: ftbfs

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

...
   dh_auto_build -O--buildsystem=rebar
make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
build
rebar_compile
rebar compile skip_deps=true -vv
DEBUG: Consult config file 
"/build/1st/erlang-cuttlefish-2.0.11+dfsg/rebar.config"
DEBUG: Rebar location: "/usr/bin/rebar"
DEBUG: Consult config file 
"/build/1st/erlang-cuttlefish-2.0.11+dfsg/src/cuttlefish.app.src"
DEBUG: Available deps: []
DEBUG: Missing deps  : []
DEBUG: Plugins requested while processing 
/build/1st/erlang-cuttlefish-2.0.11+dfsg: []
DEBUG: Predirs: []
==> erlang-cuttlefish-2.0.11+dfsg (compile)
DEBUG: Matched required ERTS version: 10.1 -> .*
ERROR: OTP release 21 does not match required regex R16|17|18|19|20
ERROR: compile failed while processing 
/build/1st/erlang-cuttlefish-2.0.11+dfsg: rebar_abort
make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:126: rebar_compile] 
Error 1
--- End Message ---
--- Begin Message ---
Source: erlang-cuttlefish
Source-Version: 2.0.11+dfsg-4

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated erlang-cuttlefish 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 09:07:52 +0900
Source: erlang-cuttlefish
Binary: erlang-cuttlefish
Architecture: source amd64
Version: 2.0.11+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: LeoFS maintainers team 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-cuttlefish - Erlang/OTP library for sysctl-like syntax
Closes: 909978
Changes:
 erlang-cuttlefish (2.0.11+dfsg-4) unstable; urgency=medium
 .
   * Fix FTBFS with Erlang 21.1 (Closes: #909978)
 Update d/patches/remove-warnings_as_errors, and add
 d/patches/support_otp_21.
Checksums-Sha1:
 9721bd69dad6044a4f2a9078eec93a1cc070a380 2210 
erlang-cuttlefish_2.0.11+dfsg-4.dsc
 ed29d30a334e223de7e70cb75418a14fc849202b 3704 
erlang-cuttlefish_2.0.11+dfsg-4.debian.tar.xz
 5577d99588176b8e525262c8daae74c1e652fa4b 9346 
erlang-cuttlefish_2.0.11+dfsg-4_amd64.buildinfo
 a0e38e0d9c98f5713a61f9ae5de93a34731dfac7 151448 
erlang-cuttlefish_2.0.11+dfsg-4_amd64.deb
Checksums-Sha256:
 47b8a1bfae1d3f1e07c46a743e537ef24c7b9e40b9f335a173d73e5ff1167750 2210 
erlang-cuttlefish_2.0.11+dfsg-4.dsc
 e5748ef015f842c64ce2aa80ccc009730a95211fcc0a84523430da2df4ec913c 3704 
erlang-cuttlefish_2.0.11+dfsg-4.debian.tar.xz
 db352f8d2f2ead55a13e8d4c2d230cf84b7beb4d441e05633ac44ee7a27bfd3a 9346 
erlang-cuttlefish_2.0.11+dfsg-4_amd64.buildinfo
 50d3058346d4136452ae08b14af293f310d1987d87f63acfc5a0ae2e2247e7d9 151448 
erlang-cuttlefish_2.0.11+dfsg-4_amd64.deb
Files:
 78817f7fbcf41e3698583929b324e4fa 2210 devel optional 
erlang-cuttlefish_2.0.11+dfsg-4.dsc
 fb28821b41ce525ab204b9406c9d9c3a 3704 devel optional 
erlang-cuttlefish_2.0.11+dfsg-4.debian.tar.xz
 5e8973c8018f7e2d8c985e624e38bf3d 9346 devel optional 
erlang-cuttlefish_2.0.11+dfsg-4_amd64.buildinfo
 f44396fa22d4d819c39018429e3c9015 151448 devel optional 
erlang-cuttlefish_2.0.11+dfsg-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlwNsugACgkQMiR/u0Ct
H6YRzRAAjl52C3OqYjtXzUA2THOUM+8GRxKOcLDLUyQWuldU1w8wl3WtfpRxDER9
9SBeJ2xu1nBvQ/hEKdIRcswNjZXNSmk4AWDHFzS4ux6cXbIP3kQFpRxS0oIsMgtV
ZkGs/JaTI1IuLZ8W3KUK16hmIWsfQQcs/WZHb8A0eMXoV4GMOCIghG5EwrV1YsPb
N4INAO369bzphw5iofh3RW4Wb2HUs4mXlN5tf4Ky5VHhjoNbMn9uGbb1EpsO9bLG

Processed: notfixed 847642 in uglifyjs/2.8.29-2, found 847642 in uglifyjs/2.8.29-2 ...

[Debian Bug Tracking System]

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

> notfixed 847642 uglifyjs/2.8.29-2
Bug #847642 [node-uglify] node-uglify: neither manpage nor --help output useful
Bug #847643 [node-uglify] node-uglify: neither manpage nor --help output useful
Ignoring request to alter fixed versions of bug #847642 to the same values 
previously set
Ignoring request to alter fixed versions of bug #847643 to the same values 
previously set
> found 847642 uglifyjs/2.8.29-2
Bug #847642 [node-uglify] node-uglify: neither manpage nor --help output useful
Bug #847643 [node-uglify] node-uglify: neither manpage nor --help output useful
Marked as found in versions uglifyjs/2.8.29-2.
Marked as found in versions uglifyjs/2.8.29-2.
> notfixed 847642 uglifyjs/2.7.5-2+deb9u1
Bug #847642 [node-uglify] node-uglify: neither manpage nor --help output useful
Bug #847643 [node-uglify] node-uglify: neither manpage nor --help output useful
Ignoring request to alter fixed versions of bug #847642 to the same values 
previously set
Ignoring request to alter fixed versions of bug #847643 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#847642: ‘uglifyjs(1)’ manual page has sections with incorrect content

[Ben Finney]

Control: reopen -1

> The command ‘uglifyjs’ has a manual page ‘uglifyjs(1)’ that does not
> helpfully describe the command:
> 
> NAME
>uglify-js - manual page for uglify-js 2.7.5

This is still the case; the manual page (now for version 2.8.29) does
not contain a useful ‘NAME’ section. The ‘DESCRIPTION’ section also
does not contain the command description.

NAME
   uglify-js - manual page for uglify-js 2.8.29

DESCRIPTION
   bin/uglifyjs input1.js [input2.js ...] [options] Use a single
   dash to read input from the standard input.

   NOTE: by default there is no mangling/compression. […]

The summary of options belongs not in the ‘DESCRIPTION’ section, but
in the ‘SYNOPSIS’ section. This frees the ‘DESCRIPTION’ section to
properly describe the behaviour of the command for a new user.

I am re-opening this bug report, with the original request unresolved:

> The manual page should have the sections described ‘man-pages(7)’ §
> “Sections within a manual page”, with the content as described in that
> document.

-- 
 \  “[Entrenched media corporations will] maintain the status quo, |
  `\   or die trying. Either is better than actually WORKING for a |
_o__)  living.” —ringsnake.livejournal.com, 2007-11-12 |
Ben Finney 


signature.asc
Description: PGP signature

Processed: Bug#847642: ‘uglifyjs(1)’ manual page has sections with incorrect content

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #847642 {Done: Adrian Bunk } [node-uglify] node-uglify: 
neither manpage nor --help output useful
Bug #847643 {Done: Adrian Bunk } [node-uglify] node-uglify: 
neither manpage nor --help output useful
'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 uglifyjs/2.8.29-2 and 
uglifyjs/2.7.5-2+deb9u1.
No longer marked as fixed in versions uglifyjs/2.8.29-2 and 
uglifyjs/2.7.5-2+deb9u1.

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

Bug#909181: Bug #909181 in mariadb-connector-c marked as pending

[Otto Kekäläinen]

Control: tag -1 pending

Hello,

Bug #909181 in mariadb-connector-c 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/mariadb-team/mariadb-connector-c/commit/698dcac50027f099295402dca7467514110e09c4


Add libssl-dev and zlib1g-dev as libmariadb-dev depends (Closes: #909181)

This will match the actual libs emitted by the library:
  % mariadb_config --libs
  -L/usr/lib/x86_64-linux-gnu/ -lmariadb -lz -ldl -lm -lpthread -lssl -lcrypto


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909181

Processed: Bug #909181 in mariadb-connector-c marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909181 [libmariadb-dev] libmariadb-dev: does not depend on zlib1g-dev, 
while mariadb_config reports `-lz`
Added tag(s) pending.

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

Bug#916070: marked as done (rootskel FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 22:51:48 +
with message-id 
and subject line Bug#916070: fixed in rootskel 1.126
has caused the Debian Bug report #916070,
regarding rootskel FTBFS with glibc 2.28
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.)


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

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

...
gcc -Os -Wall get-real-console-linux.c -o get-real-console-linux
get-real-console-linux.c: In function 'main':
get-real-console-linux.c:30:23: warning: implicit declaration of function 
'major' [-Wimplicit-function-declaration]
 printf("%d:%d\n", major(dev), minor(dev));
   ^
get-real-console-linux.c:30:35: warning: implicit declaration of function 
'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration]
 printf("%d:%d\n", major(dev), minor(dev));
   ^
   mknod
/usr/bin/ld: /tmp/cc8kbEaP.o: in function `main':
get-real-console-linux.c:(.text.startup+0x62): undefined reference to `minor'
/usr/bin/ld: get-real-console-linux.c:(.text.startup+0x6f): undefined reference 
to `major'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:24: get-real-console-linux] Error 1
--- End Message ---
--- Begin Message ---
Source: rootskel
Source-Version: 1.126

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated rootskel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 22:31:34 +
Source: rootskel
Binary: rootskel
Architecture: source
Version: 1.126
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Ben Hutchings 
Description:
 rootskel   - Skeleton root filesystem used by debian-installer (udeb)
Closes: 916070
Changes:
 rootskel (1.126) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ben Hutchings ]
   * Include  to get major() and minor() macros
 (Closes: #916070)
Checksums-Sha1:
 decc7672941d5482475227526c5d280b51e72559 1709 rootskel_1.126.dsc
 9bd6777031198f846a60fa3290157e08658d9692 31888 rootskel_1.126.tar.xz
 45b2d7c0d237228fb89adcf5649df641d40cfb36 6054 rootskel_1.126_source.buildinfo
Checksums-Sha256:
 b0bfc03d82172fecf6f3f4e7191f5d98c9c6260b1a239c1fecdf4db6a8b559ad 1709 
rootskel_1.126.dsc
 1ae23d7cc480131e4b1360142281ed9419088a6b4f2579b2e144ce7b1aba14a4 31888 
rootskel_1.126.tar.xz
 983f7cf35541646881c87c7bdca2da526187ce9b2fb3507cb1e7a8a108576d8a 6054 
rootskel_1.126_source.buildinfo
Files:
 c5bb912a31be5a058994c6a59204a366 1709 debian-installer standard 
rootskel_1.126.dsc
 fb6b6612145615d72da0ebde5363ac54 31888 debian-installer standard 
rootskel_1.126.tar.xz
 f1849ea8670255e8fdeffbd59206b7ac 6054 debian-installer standard 
rootskel_1.126_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlwNmGgACgkQ57/I7JWG
EQlY4hAAoMqBGFP+PLy0CIaJCIq2N4wXzUNWgQ66xq25XEmlOV9GpF5G3jhJ0O4c
6FEleB3MHRj/XQbhmypvHmMXfkHhn57W5+toiX6zyvvuAQnvofFcVv2HnV1TuAFT
3lxRnFepjONmUOVX39/8LUEmcsogc/4mVsFUh5tEvVoqMkzaRNtXo0YNW345p80J
rq7HOOjytQ+m75QDFlAxa6rGIGvq03gWxVgl7ZS5IdASYP9G+80TPFfllaYjR4VG
EkPa2spmSr6qeeVMwmYmSu2snrEra8snpdlLlAXCLBbqYvaIoYjWTJ+m/YID+ihK
8YVQ3EtNZiwt0TN9cfHdD7tY0rMyo5nBXq9NYGuJez8oqzG+gupy0G19D1BowhgA
PNucb6UsBeevY+cCxm7YgvftObji3ndRGaCXFquQ+GuB81M6ChW4kuIqQdIL3MsX
UkrfmGYqwRbqZcgGs+dndgpDWSpxXouijnt+XDdJr4/Vo+1Ame09clJiIAYdittq
Z8fNlI+uHRKZ6KgdnbG9XtvZ1oXXqVx7yfziSjziWoSyoPO4xjajcJ+TGvEHcTWb
g9I0I2uV5teYry9aVOZ7qk2G48i4BUGujeYT4n+lHi/kZ9ep6aLgqEzDRWqjh/22
MxC69SAHbzozMcCcbqYiaNAEB/RQRAC2Q/OlZE3zwBcyB+fEENA=
=UUVa
-END PGP SIGNATURE End Message ---

Bug#915256: marked as done (luksmeta FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 22:50:34 +
with message-id 
and subject line Bug#915256: fixed in luksmeta 9-2
has caused the Debian Bug report #915256,
regarding luksmeta 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.)


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

Some recent change in unstable makes luksmeta FTBFS:

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

...
/usr/bin/make  check-TESTS
make[4]: Entering directory '/build/1st/luksmeta-9'
make[5]: Entering directory '/build/1st/luksmeta-9'
PASS: test-crc32c
./test-driver: line 107: 43837 Aborted "$@" > $log_file 2>&1
FAIL: test-lm-assumptions
./test-driver: line 107: 43892 Aborted "$@" > $log_file 2>&1
FAIL: test-lm-init
./test-driver: line 107: 43970 Aborted "$@" > $log_file 2>&1
FAIL: test-lm-one
./test-driver: line 107: 44089 Aborted "$@" > $log_file 2>&1
FAIL: test-lm-two
./test-driver: line 107: 44262 Aborted "$@" > $log_file 2>&1
FAIL: test-lm-big
PASS: test-luksmeta

Testsuite summary for luksmeta 9

# TOTAL: 7
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  5
# XPASS: 0
# ERROR: 0

See ./test-suite.log

make[5]: *** [Makefile:1017: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: luksmeta
Source-Version: 9-2

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

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

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated luksmeta 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 23:31:49 +0100
Source: luksmeta
Binary: libluksmeta0 libluksmeta-dev luksmeta
Architecture: source
Version: 9-2
Distribution: unstable
Urgency: high
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Description:
 libluksmeta-dev - library to access metadata in the LUKSv1 header - 
development fil
 libluksmeta0 - library to access metadata in the LUKSv1 header
 luksmeta   - Utility to access metadata in a LUKSv1 header
Closes: 915256
Changes:
 luksmeta (9-2) unstable; urgency=high
 .
   * Relax content tests in test suite. Closes: #915256
Checksums-Sha1:
 76eae3e7b59a08c9385cb9c889e61c9e93523057 2014 luksmeta_9-2.dsc
 944b1048e00cd4d09ba43785506e2e00d7563cd9 4156 luksmeta_9-2.debian.tar.xz
 05556d74c0b26d9de5c0789af2e5c23ad5d41366 7477 luksmeta_9-2_powerpc.buildinfo
Checksums-Sha256:
 4b15f17151e3af020d6ebf8b99c11b4180f373d4df14bd6cd5a110bfa3eb0b74 2014 
luksmeta_9-2.dsc
 1e5883439c7f265136ffe0a1853464c377e720353288c524f2e3c6d173dacab5 4156 
luksmeta_9-2.debian.tar.xz
 8bf44d6a98fabe9925e65d59b0b4bf2a605445b9bcef5c6a4083c919682f73ce 7477 
luksmeta_9-2_powerpc.buildinfo
Files:
 e81cac6b12f42e0fc32620883bb539d1 2014 net optional luksmeta_9-2.dsc
 b10cebe646c0cce0703ece6c8fe6aa58 4156 net optional luksmeta_9-2.debian.tar.xz
 2e3c454d053a642a75d82de02256b08f 7477 net optional 
luksmeta_9-2_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAlwNmY0ACgkQxCxY61kU
kv0vNg//QdbQnvsTMEXx4kzKoIulqIYeujrNeaTOATz7ygnO4DesCyXZ06hYBXK8
zBreq6B9HNXNwWsxfdZIJ/Spqs61vKXw2LxU5XwvVI2sUKOKi/4xhaKikqTH+mJO
hmfJCy4v3yhzWg9u4+gLzWCKzRcUZYI04DDR8OWZwiZAwu7goAzNdX2ISFudYaC8
tIsbX95GoeGArYipP9lq030AiE5MMAybWbIZ0f5U09xaNSxpDCSwach7l6k5Yekb
bdDG6LzP3WAWduxKorxYy2vyfMDOpiuNlwtgTXd3FF1waE64xmh6mgoqZQKK5zj4
7WRXvMr5q5E/aN+u5Bw9N7q+YqcD4uev5r7oCQ/ycT18s3JtdYIjrgVSfLo2T7dl
d1vbOO6kGaimG3Yogf2Iw9EnwCeRBgM2LKCrKRFDsnuvWlnA5M1eLc9wV/VEJ67F

Processed: Bug #916070 in rootskel marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916070 [src:rootskel] rootskel FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#916070: Bug #916070 in rootskel marked as pending

[Ben Hutchings]

Control: tag -1 pending

Hello,

Bug #916070 in rootskel 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/installer-team/rootskel/commit/2bc1cb993813e6861537dc18f84cdd16106fa1b1


Include  to get major() and minor() macros (Closes: #916070)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916070

Bug#916001: marked as done (partconf FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 22:35:50 +
with message-id 
and subject line Bug#916001: fixed in partconf 1.52
has caused the Debian Bug report #916001,
regarding partconf FTBFS with glibc 2.28
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.)


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

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

...
cc -W -Wall -Os -o find-partitions -DFIND_PARTS_MAIN find-parts.c util.o 
xasprintf.o -lparted
find-parts.c: In function 'is_cdrom':
find-parts.c:129:13: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 switch (major(st.st_rdev)) {
 ^
find-parts.c:137:9: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
 if (minor(st.st_rdev) == 0) {
 ^
 mknod
/usr/bin/ld: /tmp/cc3JcWrE.o: in function `is_cdrom':
find-parts.c:(.text+0x25): undefined reference to `major'
/usr/bin/ld: find-parts.c:(.text+0x3b): undefined reference to `minor'
/usr/bin/ld: find-parts.c:(.text+0x4b): undefined reference to `minor'
/usr/bin/ld: find-parts.c:(.text+0x5e): undefined reference to `major'
/usr/bin/ld: find-parts.c:(.text+0x80): undefined reference to `major'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:12: find-partitions] Error 1
--- End Message ---
--- Begin Message ---
Source: partconf
Source-Version: 1.52

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated partconf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 22:23:50 +
Source: partconf
Binary: partconf-find-partitions partconf-mkfstab
Architecture: source
Version: 1.52
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Ben Hutchings 
Description:
 partconf-find-partitions - debian-installer utility for finding partitions 
(udeb)
 partconf-mkfstab - debian-installer utility for creating fstab file (udeb)
Closes: 717534 916001
Changes:
 partconf (1.52) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ben Hutchings ]
   * Include  to get major() and minor() macros
 (Closes: #916001)
   * Remove reiserfs support (Closes: #717534)
Checksums-Sha1:
 ff106f72be0e0ebcf010c087f480fc6b98c0e9c0 1778 partconf_1.52.dsc
 89d81f85633b2a33d6da360d4bb3ee0a9b100843 20828 partconf_1.52.tar.xz
 7dc8c4966b0719188c4d672b23d8b148e05fb19f 6083 partconf_1.52_source.buildinfo
Checksums-Sha256:
 dc421637b8da49e2bfa78a7f8ffe40ed8aca45bf1a47c2cf42ba607f6bd67277 1778 
partconf_1.52.dsc
 c99cbc18b85e69e5303c21a5409c5c2630f1a6760c8041e385766a5354e0a819 20828 
partconf_1.52.tar.xz
 d0e2db786a2871cba14fcf469c793f1bf6bed755ce716317e03c8ebf480a0f76 6083 
partconf_1.52_source.buildinfo
Files:
 d6b2630f69e7814a3b6e3798b0cac074 1778 debian-installer standard 
partconf_1.52.dsc
 95ed170d51455b6b9a0376ec2a57f913 20828 debian-installer standard 
partconf_1.52.tar.xz
 6f6cb2b54209d085f105012731e364c7 6083 debian-installer standard 
partconf_1.52_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlwNlooACgkQ57/I7JWG
EQmr/Q//Wo6EaAWFZ+1fXRS0OVL5A2AYKqDtiygP5Mqf7LpQl+gMT1+VtHl069/R
cdzUgnU73jsiFbbMRxfHYAduqj6dLqiVWSIZc2B6vJfI3hHLKJSj0IM+2yQC
/YiTuRb6XsyznrSb26uJyamspGdqVxifj9NNaQ7UyezqPZ4I/eggt0Ub5zbOpFJ3
ykDi8qqslzfWnt9AQ24fE43FsvjYEsUJTUtGll+Y9ovEuxuhaNWQvSfoTE4U/e7y
nfNEHRACyV4EEDjxOhrhiOZGN7/UsnpINwhglHS/m+TZjxDmoDUS7KKXd0fXAjah
Hdc2eZgq0lHWZHqEBf0w/gTz6fpXQbhDNUB6zafr1bb9EISHKaJqjUhKvR13KP4w
CXfW2kNi/8NSNPMba5F1hZF1kBIHwsvSRB3PLIMZ8/7HpBunL2cusf1XRdtFinE5
afiqfw0QkHGeUHdJ8r4HHta/GAQpsJXAe28bgsaqnITqGqUH5kU55A5XKaQyoiBb
pLGcNDFnL4ocSMiFu0o/fGP77zq10cKnTnJ7IB+UF9Qsecc6gZ9kOzd9VC8Iu+rF
07Px4BltO/DYAb8mXydPMzJlLrpSe6CNzqAUnSypMVxhvtaM3IGv2ONBPztd6sR6

Bug#915235: marked as done (cypari2 FTBFS with Python 3.7 as default)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 22:34:30 +
with message-id 
and subject line Bug#915235: fixed in cypari2 1.2.1-2
has caused the Debian Bug report #915235,
regarding cypari2 FTBFS with Python 3.7 as default
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.)


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

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

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-ffile-prefix-map=/build/1st/cypari2-1.2.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I./cypari2 
-I/usr/lib/python3/dist-packages/cysignals -I/usr/include/python3.6m -c 
cypari2/closure.c -o build/temp.linux-amd64-3.6/cypari2/closure.o
cypari2/closure.c:29:10: fatal error: Python.h: No such file or directory
 #include "Python.h"
  ^~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.6 setup.py build 
dh_auto_build: pybuild --build -i python{version} -p "3.6 3.7" returned exit 
code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25



The build dependencies include:
  libpython3-dev, libpython3.7-dev

These should be replaced with:
  libpython3-all-dev
--- End Message ---
--- Begin Message ---
Source: cypari2
Source-Version: 1.2.1-2

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

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

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated cypari2 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: Sun, 09 Dec 2018 22:52:21 +0100
Source: cypari2
Binary: python-cypari2 python3-cypari2 python-cypari2-doc
Architecture: source
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 python-cypari2 - Python interface to PARI -- Python 2
 python-cypari2-doc - Python interface to PARI -- documentation
 python3-cypari2 - Python interface to PARI -- Python 3
Closes: 915235
Changes:
 cypari2 (1.2.1-2) unstable; urgency=medium
 .
   * Build-Depend on libpython3.6-dev (Closes: #915235).
Checksums-Sha1:
 15c0c07c0a1b5b0d6cbf8cc12fba6fccb5e6247f 2486 cypari2_1.2.1-2.dsc
 edb5dda1faaee39a5ca5955d5d9a71116f45c8eb 4104 cypari2_1.2.1-2.debian.tar.xz
 3a614aa1b8ca42ed0a92f18e2ddee12d8cae440f 8460 cypari2_1.2.1-2_source.buildinfo
Checksums-Sha256:
 6ed00522051bafc8e894c0dc4f36a23ddf87591286af4a8a2b01fcd155983c3b 2486 
cypari2_1.2.1-2.dsc
 b88c63b480b26ce374c31843677fe7f7ce3933a91e9773f893658c4fb0bb0688 4104 
cypari2_1.2.1-2.debian.tar.xz
 f3220295351842090698dde6373d3923cfee8a203b227a129cf8c0bab86efe10 8460 
cypari2_1.2.1-2_source.buildinfo
Files:
 e8a964f4b1464a7e09731ba0fd3f971e 2486 python optional cypari2_1.2.1-2.dsc
 d7543f926a190271aad561b2619b2103 4104 python optional 
cypari2_1.2.1-2.debian.tar.xz
 9a1bfbd87957e921f714f6beec8e2282 8460 python optional 
cypari2_1.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAlwNkskACgkQjIIWnY7O
zSq2rQ/6A+tfQR7iTzO4AaKE1WqWIZPqkv/Yi86ehZ5d2s7dquuwUDHLSzrtL/9r
aHEJFHEkUoFtoWQHadkc1PxMfu8ppEWoOGN1yodPBHT+EJnzmNBh2bgZoLur4HUj
YmjOvAJ98NrUFgUG7/jeM2Um9apoYlaOThi/BC+PwNq+aoHC2GMQ3MyLZfonjIXd
DxhpQWtoC0UtJ+Q++USRjAbkFexkbZByIed8FPqV1qVpOAi1Brtb+ujg8CtKOnmR
9Om3KMQ0JAQOBFi054lzeDn6JRhIG6YTNAzxzONPK1RS++fBGKH+X64qwrcZbLNA
SftjV/VMOReZIPJjbmxO0VFkHfKklsMR3E4JcA+YLi+tzIU/us44xdak1ZuTv1hr
hQ8ODJd5S1wy+lKxbJZetXdqvmcCrJcuE6DdMqSCyze2NW62aI4fMqrcNtaOPW8j
jHo8c1Ntem3gzzFo76sy/F9X0facPH5aD+KQCjW3clrsVCRqdSeSCwCZOobtKWn0
wV4GZ6WloVehPOhWd8shB7V0cQy7nSB8lcU6aNIXT2rkgBK9rJM3JyIG+rVa15M2
bhmjOyI2gYKKuY0MGPZ3sf1S1cZVDEQk8VKXWbzenrdWh+LQ6DM3BIdMiUajVgj0
G9Y2Dk9MvNMmeLUU3XX+daGCsp7EXRSknVVHAbwcCZJMJagE2CY=
=44tX
-END PGP SIGNATURE End Message ---

Bug#916001: Bug #916001 in partconf marked as pending

[Ben Hutchings]

Control: tag -1 pending

Hello,

Bug #916001 in partconf 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/installer-team/partconf/commit/518399d3a513e5a3e9c08b2c32cd8b95532b8cc1


Include  to get major() and minor() macros

Closes: #916001


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916001

Processed: Bug #916001 in partconf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916001 [src:partconf] partconf FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#916060: tuxmath: Starts and immediately closes

[Bernhard Übelacker]

Dear Maintainer,
I just tried to reproduce and collect some more information,
used a minimal buster amd64 qemu VM.

This issue seems to be more located in libt4k-common0.
It uses "rsvg_handle_get_desc(file_handle)" to retrieve
a char pointer to the description and tries to convert that
into an integer by sscanf [1].

Unfortunately seems librsvg-2.42 [2] the last release that
supported that way of operation. 
librsvg removed that functionality in commit [3].

Therefore in current version just a null pointer [4] is returned
by rsvg_handle_get_desc that leads to the crash in load_svg_sprite:


(gdb) bt
#0  __rawmemchr_sse2 () at ../sysdeps/x86_64/multiarch/../rawmemchr.S:37
#1  0x7febe0ac3342 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffd7b8ad720, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0) at strops.c:41
#2  0x7febe0ab624d in _IO_vsscanf (string=0x0, format=0x7febe0c35c62 "%d", 
args=args@entry=0x7ffd7b8ad850) at iovsscanf.c:40
#3  0x7febe0ab03f4 in __sscanf (s=, 
format=format@entry=0x7febe0c35c62 "%d") at sscanf.c:32
#4  0x7febe0c2c3c9 in load_svg_sprite (file_name=, 
width=width@entry=-1, height=height@entry=-1) at t4k_loaders.c:217
#5  0x7febe0c2d52b in load_sprite (name=name@entry=0x55b6034762a1 
"comets/comet", mode=mode@entry=4, w=w@entry=-1, h=h@entry=-1, 
proportional=proportional@entry=false) at t4k_loaders.c:714
#6  0x7febe0c2d978 in T4K_LoadScaledSprite (name=name@entry=0x55b6034762a1 
"comets/comet", mode=mode@entry=4, width=width@entry=-1, 
height=height@entry=-1) at t4k_loaders.c:651
#7  0x7febe0c2d98c in T4K_LoadSprite (name=name@entry=0x55b6034762a1 
"comets/comet", mode=mode@entry=4) at t4k_loaders.c:646
#8  0x55b60345b961 in load_image_data () at fileops_media.c:213
#9  0x55b603448962 in load_data_files () at setup.c:759
#10 0x55b6034497c5 in setup (argc=1, argv=0x7ffd7b8ae758) at setup.c:139
#11 0x55b603447be9 in main (argc=, argv=) at 
tuxmath.c:40


Kind regards,
Bernhard


[1] https://github.com/tux4kids/t4kcommon/blob/master/src/t4k_loaders.c#L228
[2] 
https://gitlab.gnome.org/GNOME/librsvg/blob/librsvg-2.42/librsvg/rsvg-handle.c#L772
[3] 
https://gitlab.gnome.org/GNOME/librsvg/commit/1006c2001d4775b6d5b20d5f77c5aea9ac280fcb
[4] 
https://gitlab.gnome.org/GNOME/librsvg/blob/master/librsvg/rsvg-handle.c#L1007

# buster amd64 qemu VM

apt update
apt dist-upgrade

apt install mc psmisc devscripts dpkg-dev systemd-coredump strace gdb 
xserver-xorg lightdm openbox tuxmath tuxmath-dbgsym libt4k-common0-dbgsym 
librsvg2-2-dbgsym
apt build-dep t4kcommon


systemctl start lightdm





mkdir libt4k-common0/orig -p
cdlibt4k-common0/orig
apt source libt4k-common0
cd ../..

mkdir librsvg2-2/orig -p
cdlibrsvg2-2/orig
apt source librsvg2-2
cd ../..









export LANG=C
export DISPLAY=:0
tuxmath





root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Sun 2018-12-09 22:02:02 CET8201  1000  1000  11 present   
/usr/lib/tuxmath/tuxmath
root@debian:~# coredumpctl gdb 8201
   PID: 8201 (tuxmath)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Sun 2018-12-09 22:02:02 CET (28s ago)
  Command Line: tuxmath
Executable: /usr/lib/tuxmath/tuxmath
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: b8debb360de74c7698ecca6a9e56eac5
Machine ID: 32f43b50ac8c4b21941bc0b02f8e7811
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.tuxmath.1000.b8debb360de74c7698ecca6a9e56eac5.8201.154438932200.lz4
   Message: Process 8201 (tuxmath) of user 1000 dumped core.

Stack trace of thread 8201:
#0  0x7febe0ad67af __rawmemchr_sse2 (libc.so.6)
#1  0x7febe0ac3342 _IO_str_init_static_internal (libc.so.6)
#2  0x7febe0ab624d _IO_vsscanf (libc.so.6)
#3  0x7febe0ab03f4 __sscanf (libc.so.6)
#4  0x7febe0c2c3c9 load_svg_sprite (libt4k_common.so.0)
#5  0x7febe0c2d52b load_sprite (libt4k_common.so.0)
#6  0x55b60345b961 n/a (tuxmath)
#7  0x55b603448962 n/a (tuxmath)
#8  0x55b6034497c5 n/a (tuxmath)
#9  0x55b603447be9 main (tuxmath)
#10 0x7febe0a67b17 __libc_start_main (libc.so.6)
#11 0x55b603447c2a n/a (tuxmath)

GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for 

Bug#916004: marked as done (makefs FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:50:07 +
with message-id 
and subject line Bug#916004: fixed in makefs 20100306-7
has caused the Debian Bug report #916004,
regarding makefs FTBFS with glibc 2.28
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.)


-- 
916004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: makefs
Version: 20100306-6
Severity: serious
Tags: ftbfs buster sid

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

...
/build/1st/makefs-20100306/builddir/usr.sbin/makefs/nbsrc/sbin/mknod/pack_dev.c:
 In function 'pack_native':
/build/1st/makefs-20100306/builddir/usr.sbin/makefs/nbsrc/sbin/mknod/pack_dev.c:72:9:
 warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   dev = makedev(numbers[0], numbers[1]);
 ^~~
/build/1st/makefs-20100306/builddir/usr.sbin/makefs/nbsrc/sbin/mknod/pack_dev.c:73:15:
 warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
   if ((u_long)major(dev) != numbers[0])
   ^
...
cc -g -O2 -ffile-prefix-map=/build/1st/makefs-20100306=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wformat 
-Wno-unused-but-set-variable -Wno-unused-result -flto=jobserver -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed  -o makefs cd9660.o ffs.o getid.o makefs.o misc.o 
pack_dev.o spec.o walk.o cd9660_strings.o cd9660_debug.o cd9660_eltorito.o 
cd9660_write.o cd9660_conversion.o iso9660_rrip.o cd9660_archimedes.o 
ffs_alloc.o ffs_balloc.o ffs_bswap.o ffs_subr.o ffs_tables.o ufs_bmap.o buf.o 
mkfs.o pwcache.o strsuftoll.o fparseln.o -lbsd
/usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 124
/tmp/ccuOSmWf.ltrans0.ltrans.o: in function `fparseln':
:(.text+0xbfb7): warning: This function cannot be safely ported, 
use getline(3) instead, as it is supported by GNU and POSIX.1-2008.
/usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 124
/tmp/ccuOSmWf.ltrans0.ltrans.o: in function `pack_native':
:(.text+0x4bb1): undefined reference to `makedev'
/usr/bin/ld: :(.text+0x4bbe): undefined reference to `major'
/usr/bin/ld: :(.text+0x4be6): undefined reference to `minor'
collect2: error: ld returned 1 exit status
*** Error code 1
--- End Message ---
--- Begin Message ---
Source: makefs
Source-Version: 20100306-7

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

Debian distribution maintenance software
pp.
James Clarke  (supplier of updated makefs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 21:27:46 +
Source: makefs
Binary: makefs
Architecture: source
Version: 20100306-7
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD Maintainers 
Changed-By: James Clarke 
Description:
 makefs - create a cd9660 or ffs file system image from a directory tree
Closes: 916004
Changes:
 makefs (20100306-7) unstable; urgency=medium
 .
   * Convert to standard patches-unapplied format
   * Fix FTBFS with glibc 2.28 (Closes: #916004)
   * Switch from transitional pmake to bmake
   * Bump debhelper compat level to 11
   * debian/rules: Use dh sequencer and modernise
   * debian/control:
 - Update Vcs-* to point to salsa
 - Bump Standards-Version to 4.2.1; no changes needed
 - Add Rules-Requires-Root: no
 - Run wrap-and-sort -ast
 - Add myself to Uploaders
Checksums-Sha1:
 45b494e6de3877c83ddf3933ddfcf45f68c9 1963 makefs_20100306-7.dsc
 b1dd2cf89034277467302dacd165de8e85cb0564 7920 makefs_20100306-7.debian.tar.xz
 b6b756ed79974822680495c555a11f510705a7c1 5900 makefs_20100306-7_amd64.buildinfo
Checksums-Sha256:
 690319b0a9a5e782c50b26298112350df594665a020b5b707992ee9c57f907c8 1963 
makefs_20100306-7.dsc
 3444c040b0111d599ea4f29bc327167f92357e68afa2cd9e255b1f001bcf44d0 7920 
makefs_20100306-7.debian.tar.xz
 14fc1672d2e2cefbb7f94e1535fdd5a6861df7ca2b41d2aafc6ec71175d962a6 5900 
makefs_20100306-7_amd64.buildinfo
Files:
 

Bug#906094: marked as done (psi4: missing dependency on python3)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:50:53 +
with message-id 
and subject line Bug#906094: fixed in psi4 1:1.1-6
has caused the Debian Bug report #906094,
regarding psi4: missing dependency on python3
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.)


-- 
906094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: psi4
Version: 1:1.1-5
Severity: serious
Tags: patch

psi4 needs a dependency on python3 for /usr/bin/psi4:

--- debian/control.old  2018-08-13 21:58:29.746594942 +
+++ debian/control  2018-08-14 00:15:45.898516395 +
@@ -21,6 +21,7 @@
   libhdf5-dev,
   libint-dev (>= 1.2.0-1),
liblapack-dev,
+   dh-python,
   python3-dev,
python3-numpy,
python3-pybind11,
@@ -34,7 +35,7 @@
 
 Package: psi4
 Architecture: any
-Depends: psi4-data (= ${source:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: psi4-data (= ${source:Version}), ${misc:Depends}, ${shlibs:Depends}, 
${python3:Depends}
 Description: Quantum Chemical Program Suite
  PSI4 is an ab-initio quantum chemistry program.  It is especially designed to
  accurately compute properties of small to medium molecules using highly
--- debian/rules.old2018-08-13 21:58:26.866594969 +
+++ debian/rules2018-08-13 21:58:41.678594828 +
@@ -8,7 +8,7 @@
 export OMPI_MCA_orte_rsh_agent=/bin/false
 
 %: 
-   dh $@ --parallel --builddirectory=builddir
+   dh $@ --parallel --builddirectory=builddir --with python3
 
 override_dh_auto_clean:
dh_auto_clean --builddirectory=builddir
--- End Message ---
--- Begin Message ---
Source: psi4
Source-Version: 1:1.1-6

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated psi4 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: Sun, 09 Dec 2018 19:42:51 +0100
Source: psi4
Binary: psi4 psi4-data
Architecture: source
Version: 1:1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 psi4   - Quantum Chemical Program Suite
 psi4-data  - Quantum Chemical Program Suite (data files)
Closes: 897492 906094
Changes:
 psi4 (1:1.1-6) unstable; urgency=medium
 .
   * debian/patches/support-pybind11-2.2.patch: New patch, fixes build failure
 with pybin11-2.2, by Gilles Filippini (Closes: #897492).
   * debian/control (Build-Depends): Added dh-python.
   * debian/control (psi4/Depends): Added ${python3:Depends}.
   * debian/rules: Added --with python3, thanks to Adrian Bunk (Closes:
 #906094).
   * debian/patches/support-pybind11-2.2.patch: Include upstream commit
 5c0b2ffd and parts of upstream commit 34fec146.
   * debian/psi4.install: Update lib directory.
   * debian/rules (override_dh_auto_configure): Define ENABLE_CheMPS2.
   * debian/control (Build-Depends): Added chemps2.
   * debian/patches/runtests_python3.patch: New patch, sets python3 as
 interpreter for python tests.
Checksums-Sha1:
 f4c7fe213eae67f0c68b49d97db90c802050fd78 2346 psi4_1.1-6.dsc
 e410d01f759c38bf76335cd03e1cee80197db668 65232 psi4_1.1-6.debian.tar.xz
 c86a9dbd6b6b78924d545c1092268ff1ef09162d 9809 psi4_1.1-6_source.buildinfo
Checksums-Sha256:
 13d567c794aeaed330ac38eec63153d7c068aba5478d18c9699c2fd86896f7cd 2346 
psi4_1.1-6.dsc
 e44e569a418c30db1c3797c4ebd56bb6e400068568c8453d9fd261b4fb6c4b16 65232 
psi4_1.1-6.debian.tar.xz
 dbcf839e6ed3ac74d11a03db20c82df724961caa5cfa74d2e7984ed749c6aaf8 9809 
psi4_1.1-6_source.buildinfo
Files:
 9dd7d7c3478657c55db62ec6912fc651 2346 science optional psi4_1.1-6.dsc
 780798f88274d1ffd93da790ed134dc2 65232 science optional 
psi4_1.1-6.debian.tar.xz
 68772dce17d7f2084c4fe5fb521f39b5 9809 science optional 
psi4_1.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAlwNivsACgkQ3GhqJ7Q0

Bug#897492: marked as done (psi4: FTBFS: pybind11.h:1010:105: error: cannot convert 'void (psi::SuperFunctional::*)(int) const' to 'void (psi::Functional::*)(int) const' in return)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:50:53 +
with message-id 
and subject line Bug#897492: fixed in psi4 1:1.1-6
has caused the Debian Bug report #897492,
regarding psi4: FTBFS: pybind11.h:1010:105: error: cannot convert 'void 
(psi::SuperFunctional::*)(int) const' to 'void (psi::Functional::*)(int) const' 
in return
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.)


-- 
897492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi4
Version: 1:1.1-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cd /<>/builddir/psi4-core-prefix/src/psi4-core-build/src && 
> /usr/bin/c++  -Dcore_EXPORTS -I/<>/psi4/include 
> -I/<>/psi4/src -isystem /usr/include/python3.6m  -fopenmp -O2 -g 
> -DNDEBUG -fPIC   -fvisibility=hidden -std=c++11 -std=c++11 -o 
> CMakeFiles/core.dir/export_functional.cc.o -c 
> /<>/psi4/src/export_functional.cc
> In file included from /<>/psi4/include/psi4/pybind11.h:10:0,
>  from /<>/psi4/src/export_functional.cc:29:
> /usr/include/pybind11/pybind11.h: In instantiation of 'Return (Derived::* 
> pybind11::method_adaptor(Return (Class::*)(Args ...) const))(Args ...) const 
> [with Derived = psi::Functional; Return = void; Class = psi::SuperFunctional; 
> Args = {int}]':
> /usr/include/pybind11/pybind11.h:1085:45:   required from 
> 'pybind11::class_& pybind11::class_ options>::def(const char*, Func&&, const Extra& ...) [with Func = void 
> (psi::SuperFunctional::*)(int) const; Extra = {char [10]}; type_ = 
> psi::Functional; options = {std::shared_ptr}]'
> /<>/psi4/src/export_functional.cc:112:74:   required from here
> /usr/include/pybind11/pybind11.h:1010:105: error: cannot convert 'void 
> (psi::SuperFunctional::*)(int) const' to 'void (psi::Functional::*)(int) 
> const' in return
>  auto method_adaptor(Return (Class::*pmf)(Args...) const) -> Return 
> (Derived::*)(Args...) const { return pmf; }
>   
>^~~
> make[6]: *** [src/CMakeFiles/core.dir/build.make:131: 
> src/CMakeFiles/core.dir/export_functional.cc.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/psi4_1.1-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: psi4
Source-Version: 1:1.1-6

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated psi4 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: Sun, 09 Dec 2018 19:42:51 +0100
Source: psi4
Binary: psi4 psi4-data
Architecture: source
Version: 1:1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 psi4   - Quantum Chemical Program Suite
 psi4-data  - Quantum Chemical Program Suite (data files)
Closes: 897492 906094
Changes:
 psi4 (1:1.1-6) unstable; urgency=medium
 .
   * debian/patches/support-pybind11-2.2.patch: New patch, fixes build failure
 with pybin11-2.2, by Gilles Filippini (Closes: #897492).
   * debian/control (Build-Depends): Added dh-python.
   * debian/control (psi4/Depends): Added ${python3:Depends}.
   * debian/rules: Added --with python3, thanks to Adrian Bunk (Closes:
 #906094).
   * debian/patches/support-pybind11-2.2.patch: Include upstream commit
 5c0b2ffd and parts of upstream commit 34fec146.
   * debian/psi4.install: Update lib directory.
   

Bug#911437: marked as done (gitlab-ci-multi-runner: FTBFS with golang-github-prometheus-client-golang/0.9.0-1)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:49:53 +
with message-id 
and subject line Bug#911437: fixed in gitlab-ci-multi-runner 11.2.0+dfsg-2
has caused the Debian Bug report #911437,
regarding gitlab-ci-multi-runner: FTBFS with 
golang-github-prometheus-client-golang/0.9.0-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.)


-- 
911437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab-ci-multi-runner
Version: 11.2.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

When rebuild gitlab-ci-multi-runner, it FTBFS,

# gitlab.com/gitlab-org/gitlab-runner/commands
src/gitlab.com/gitlab-org/gitlab-runner/commands/multi.go:365:54: too
many arguments in call to
"github.com/prometheus/client_golang/prometheus".NewProcessCollector
have (int, string)
want 
("github.com/prometheus/client_golang/prometheus".ProcessCollectorOpts)


-- 
Shengjing Zhu
--- End Message ---
--- Begin Message ---
Source: gitlab-ci-multi-runner
Source-Version: 11.2.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
gitlab-ci-multi-runner, 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.
Dmitry Smirnov  (supplier of updated gitlab-ci-multi-runner 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 07:27:43 +1100
Source: gitlab-ci-multi-runner
Binary: gitlab-runner
Architecture: source amd64
Version: 11.2.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dmitry Smirnov 
Description:
 gitlab-runner - GitLab Runner - runs continuous integration (CI) jobs
Closes: 911437
Changes:
 gitlab-ci-multi-runner (11.2.0+dfsg-2) unstable; urgency=medium
 .
   * New patch to fix FTBFS (Closes: #911437).
 Thanks, Andreas Henriksson.
Checksums-Sha1:
 a7ca31e529b69088700c0bda64f007c10add351f 3942 
gitlab-ci-multi-runner_11.2.0+dfsg-2.dsc
 6f04e50f145a4e9e061d8eb1cb81fc12932d1e33 23564 
gitlab-ci-multi-runner_11.2.0+dfsg-2.debian.tar.xz
 52a2d34f2a84b844d2ab4f81de6be8624b777621 23118 
gitlab-ci-multi-runner_11.2.0+dfsg-2_amd64.buildinfo
 8c7e172c95dab28d300fbbf59df64d3e5a61c730 9242204 
gitlab-runner_11.2.0+dfsg-2_amd64.deb
Checksums-Sha256:
 13d288097681cd9cd6c0134a6713130f7e5200eb7dd9a1041b8b68872002ffc3 3942 
gitlab-ci-multi-runner_11.2.0+dfsg-2.dsc
 49a13ba66aaabe2c6844d56eedeb46f4fb2891197b9c45026b1ee9912c28cc24 23564 
gitlab-ci-multi-runner_11.2.0+dfsg-2.debian.tar.xz
 80575020db92858b783665071c1630c982a92b6539933f8651109dc02d957d78 23118 
gitlab-ci-multi-runner_11.2.0+dfsg-2_amd64.buildinfo
 a2ad6c9ead8f60afb6b5ad7abb872c19396238eb06181f90882d56dd896f2957 9242204 
gitlab-runner_11.2.0+dfsg-2_amd64.deb
Files:
 1ee71e219914034163b8f7a09b22137e 3942 devel optional 
gitlab-ci-multi-runner_11.2.0+dfsg-2.dsc
 154e094446b641652a4bb3774b970cbc 23564 devel optional 
gitlab-ci-multi-runner_11.2.0+dfsg-2.debian.tar.xz
 1d6deac05bffe585a94de551ffb3ec53 23118 devel optional 
gitlab-ci-multi-runner_11.2.0+dfsg-2_amd64.buildinfo
 339959bb2ce90106d899b9bde3a9ffe7 9242204 devel optional 
gitlab-runner_11.2.0+dfsg-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAlwNfmoACgkQUra72VOW
jRslIQ//ZR+v1qJYCVV4ADHaqYyuip3SCBkdOD3ROMtd/CzNaEoBPkXq/k3MDw++
C2J3aelzWuirnldHnUDsLHQ77r+NTZycxAaZt+pSLpXO3ePSr22Oxrqr8ykBwYQR
0/2e+c1l10jMQzeQW4RcLIQO9pWWzTlhoVHMnrs2BEPOHPcGimyz2qbk38DGD83C
TBlTnPfQRCyhVes+U2cepBwIPTbi57d7CqaeBVzbAW3AvrP39CVKcx/KCe6iZ7Oy
Rm3o3oVnGBuzLRJrOm1b7ZjbBe6jGi+t45z1kgUj/u5cWeO2Oli4JuzRJuADXPNN
vNpcyvKBJgTKvv8Of1fMRfMIN55rdWVci7j3fTYZA6HDAswbzTnPGSxFbDIQcLe0
2OBzvCmUrdih0G9tftmuQWKn1sTySUChYfayNLXf1bpy3TIoUBOEDjkybhPIeEwk
jq3e+9CxYyL4cfim0zhKnGKe4Dz7Q9UrK7CoHCKaJyaxsa/2OggmvM2fMNEY/Iow
Iof1mLRleDtrJNxzE5l8bfjsFujXcFSXsWPTmKH6m9jFOMKHnO3rmLe+42feGrjm
X1aBVzavW2QDQKHWKhwNOd3/iUxCs6gYvxMETQweclVPY3HvXcEvpQRKwjaCtS9Q
HyE1yXPoolKrTMbAyaSEN5miJPrFqy73YYHIktOiml+IDF5QhsE=
=uQU9
-END PGP SIGNATURE End Message ---

Bug#916017: pax FTBFS with glibc 2.28

[Thorsten Glaser]

Hi Adrian,

>Tags: ftbfs
>
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pax.html
>
>...
>cpio.c: In function 'vcpio_wr':
>pax.h:261:18: warning: implicit declaration of function 'major' 
>[-Wimplicit-function-declaration]
> #define MAJOR(x) major(x)
>  ^

Thanks, I guess it will need ,
I’ll take care of it in the next couple of days.

bye,
//mirabilos
-- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2

Bug#916004: Bug #916004 in makefs marked as pending

[James Clarke]

Control: tag -1 pending

Hello,

Bug #916004 in makefs 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/bsd-team/makefs/commit/563dfab97012c40a82f1d28607d097e3526b5d85


Fix FTBFS with glibc 2.28

Closes: #916004


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916004

Processed: Bug #916004 in makefs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916004 [src:makefs] makefs FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#915639: marked as done (shibboleth-resolver: FTBFS: missing pkg-config/log4shib/log4cpp)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:27:06 +
with message-id 
and subject line Bug#915639: fixed in shibboleth-resolver 3.0.0-2
has caused the Debian Bug report #915639,
regarding shibboleth-resolver: FTBFS: missing pkg-config/log4shib/log4cpp
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.)


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

Hi,

shibboleth-resolver FTBFS everywhere:
https://buildd.debian.org/status/package.php?p=shibboleth-resolver=unstable

checking for pkg-config... no
checking for log4shib... no
checking for log4cpp... no
configure: error: in `/<>':
configure: error: The pkg-config script could not be found or is too old.  Make 
sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively, you may set the environment variables log4cpp_CFLAGS
and log4cpp_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

To get pkg-config, see .


Andreas
--- End Message ---
--- Begin Message ---
Source: shibboleth-resolver
Source-Version: 3.0.0-2

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

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

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated shibboleth-resolver 
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: Sun, 09 Dec 2018 15:00:22 -0500
Source: shibboleth-resolver
Binary: libshibresolver-dev libshibresolver2 libshibresolver-dbg
Architecture: source amd64
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Shibboleth Packaging 
Changed-By: Sam Hartman 
Description:
 libshibresolver-dbg - Shibboleth SP Attribute Resolver Debugging
 libshibresolver-dev - Shibboleth SP Attribute Resolver library
 libshibresolver2 - Shibboleth SP Attribute Resolver library
Closes: 915639
Changes:
 shibboleth-resolver (3.0.0-2) unstable; urgency=medium
 .
   * Build depend on pkg-config, closes: #915639
Checksums-Sha1:
 305d0ddc466f9c6c9e71f2f6cf60adc904ed3e63 1920 shibboleth-resolver_3.0.0-2.dsc
 de43082df6998f5f46132992beaf384dd2f6be7b 2352 
shibboleth-resolver_3.0.0-2.debian.tar.xz
 7ef3e54e2380f3545d396684d02bd6d400ac4f35 422276 
libshibresolver-dbg_3.0.0-2_amd64.deb
 401d4bfe00fa8715cfd871ecb3ef9c83f6d0a62d 5076 
libshibresolver-dev_3.0.0-2_amd64.deb
 139cc01161abef263c5c26e1657db3301e3668a0 26644 
libshibresolver2_3.0.0-2_amd64.deb
 9b1adccb495799e02c0b601e609bcc2eb1408fef 7449 
shibboleth-resolver_3.0.0-2_amd64.buildinfo
Checksums-Sha256:
 593bd20c85fcb600a085e2f76e125b1587aaee8f00e7d87620e9e5ebe628cb05 1920 
shibboleth-resolver_3.0.0-2.dsc
 ab75c7d24531c79d3ab105f1dbd4a7f205b86ad0910a3def476da8566998fe42 2352 
shibboleth-resolver_3.0.0-2.debian.tar.xz
 062c91b76b187ab15c082921bf21cb4342984bbfc23a535a68754604bff3f696 422276 
libshibresolver-dbg_3.0.0-2_amd64.deb
 79e3a9a47473c518c854a6384c5a7db03040b91d20eb2e6014d093e4d13ac931 5076 
libshibresolver-dev_3.0.0-2_amd64.deb
 e6a35396b449897e03dec865980d7fdc81b2cd014ea82331e559d4c768f94896 26644 
libshibresolver2_3.0.0-2_amd64.deb
 2a962540e877562ba8d57e55f9b7c118f23a4e313da58cfa38ec3871ee650773 7449 
shibboleth-resolver_3.0.0-2_amd64.buildinfo
Files:
 f375825eae77d6e6717a3b552d7f636d 1920 libs optional 
shibboleth-resolver_3.0.0-2.dsc
 886b670263a755fe2b395f5cb5ef3a5c 2352 libs optional 
shibboleth-resolver_3.0.0-2.debian.tar.xz
 ff10eb868e047fa00e2b62c625e19143 422276 debug optional 
libshibresolver-dbg_3.0.0-2_amd64.deb
 c2f039ae6f1bc6f22e9309951eb1d4fe 5076 libdevel optional 
libshibresolver-dev_3.0.0-2_amd64.deb
 86606ba8d620bda290ebae05e4bf891e 26644 libs optional 
libshibresolver2_3.0.0-2_amd64.deb
 056696f99baa5dcbb4c2ef036180b936 7449 libs optional 
shibboleth-resolver_3.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#899837: marked as done (xfce4-datetime-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:27:32 +
with message-id 
and subject line Bug#899837: fixed in xfce4-datetime-plugin 0.7.0-2
has caused the Debian Bug report #899837,
regarding xfce4-datetime-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-datetime-plugin
Version: 0.7.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-datetime-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-datetime-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-datetime-plugin
Source-Version: 0.7.0-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated 
xfce4-datetime-plugin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 21:10:13 +0100
Source: xfce4-datetime-plugin
Binary: xfce4-datetime-plugin
Architecture: source
Version: 0.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-datetime-plugin - date and time plugin for the Xfce4 panel
Closes: 899837
Changes:
 xfce4-datetime-plugin (0.7.0-2) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899837
   * d/gbp.conf added, following DEP-14
   * run wrap-and-sort
   * d/watch: use HTTPS protocol
   * New upstream version 0.7.0
   * d/control: update standards version to 4.2.1
   * d/control: use HTTPS protocol for homepage
   * update debhelper compat to 10
Checksums-Sha1:
 9d27384a02e0e6d4c7244a359ef56a3d8bd36c92 1834 xfce4-datetime-plugin_0.7.0-2.dsc
 09e42fb0e474904aac0e2665f148493ea46273f8 3444 
xfce4-datetime-plugin_0.7.0-2.debian.tar.xz
 0315e2e462e9da1aaa401a31ed2ec677edfe43aa 15064 
xfce4-datetime-plugin_0.7.0-2_amd64.buildinfo
Checksums-Sha256:
 

Bug#904808: libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults

[Rene Luria]

Hello,Here is a patch trying to address that, as suggested by Simon McVittie in https://github.com/stevegrubb/libcap-ng/issues/5and Carlos O'Donell at https://sourceware.org/bugzilla/show_bug.cgi?id=13502Using the package built with this patch also fixes this bug:https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no=915642Sincerly,René

libcap-ng.patch
Description: Binary data

Bug#916037: marked as done (liquidwar FTBFS with allegro4.4 2:4.4.2-13)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:22:18 +
with message-id 
and subject line Bug#916037: fixed in liquidwar 5.6.4-6
has caused the Debian Bug report #916037,
regarding liquidwar FTBFS with allegro4.4 2:4.4.2-13
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.)


-- 
916037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liquidwar
Version: 5.6.4-5
Severity: serious
Tags: ftbfs buster sid

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

...
distor.c: In function 'create_wave_line':
distor.c:197:15: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
   cycle_tmp = fsqrt (fsqrt (cycle_tmp)) / 2;
   ^
   fixsqrt
distor.c:206:8: warning: implicit declaration of function 'fsin'; did you mean 
'fixsin'? [-Wimplicit-function-declaration]
   f0 = fsin (cycle_coef + freq_coef * period2);
^~~~
fixsin
distor.c:207:22: warning: implicit declaration of function 'fcos'; did you mean 
'fixcos'? [-Wimplicit-function-declaration]
   fp0x0 = (PI_1024 * fcos (cycle_coef + freq_coef * period2)) / 1024;
  ^~~~
...
fighter.c: In function 'move_fighters':
fighter.c:338:6: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
  fsqrt (fsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
  ^
...
palette.c: In function 'sqrt255':
palette.c:91:12: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
   result = fsqrt (i * 256) / 256;
^
...
Linking liquidwar (target=default, debug=no, static=no, asm=no)
/usr/bin/ld: random.o: in function `lw_random_generate_map':
random.c:(.text+0x34): warning: the use of `tmpnam' is dangerous, better use 
`mkstemp'
/usr/bin/ld: distor.o: in function `create_wave_line.constprop.0':
distor.c:(.text+0xc6): undefined reference to `fsqrt'
/usr/bin/ld: distor.c:(.text+0xcf): undefined reference to `fsqrt'
/usr/bin/ld: distor.c:(.text+0x130): undefined reference to `fsin'
/usr/bin/ld: distor.c:(.text+0x13e): undefined reference to `fcos'
/usr/bin/ld: distor.c:(.text+0x24e): undefined reference to `fcos'
/usr/bin/ld: fighter.o: in function `move_fighters':
fighter.c:(.text+0x46d): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x476): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x4a5): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x4ae): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x554): undefined reference to `fsqrt'
/usr/bin/ld: fighter.o:fighter.c:(.text+0x55d): more undefined references to 
`fsqrt' follow
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:245: liquidwar] Error 1
--- End Message ---
--- Begin Message ---
Source: liquidwar
Source-Version: 5.6.4-6

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated liquidwar 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: Sun, 09 Dec 2018 21:46:45 +0100
Source: liquidwar
Binary: liquidwar liquidwar-data liquidwar-server
Architecture: source
Version: 5.6.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Andreas Rönnquist 
Description:
 liquidwar  - truly original multiplayer wargame
 liquidwar-data - data files for Liquid War
 liquidwar-server - Liquid War server
Closes: 916037
Changes:
 liquidwar (5.6.4-6) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to build with fix*-functions in Allegro, instead of
 f*-functions, fixes conflict in glibc. (Closes: #916037)
Checksums-Sha1:
 91035d7a67bad92dadc4529c583b9b855901b222 2158 liquidwar_5.6.4-6.dsc
 2b50f8f13de1b65d44010cbba5aadf5be91e6c9c 11796 liquidwar_5.6.4-6.debian.tar.xz
 79e07fd5be7df9726a5a611cff9fd363b708de60 8579 

Bug#914145: marked as done (liborigin2 FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:20:53 +
with message-id 
and subject line Bug#914145: fixed in liborigin2 2:20110117-3
has caused the Debian Bug report #914145,
regarding liborigin2 FTBFS with boost 1.67
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.)


-- 
914145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liborigin2
Version: 2:20110117-2
Severity: serious
Tags: ftbfs

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

...
In file included from Origin800Parser.h:32,
 from Origin610Parser.h:32,
 from Origin600Parser.h:32,
 from Origin600Parser.cpp:29:
Origin750Parser.h: In member function 'boost::posix_time::ptime 
Origin750Parser::doubleToPosixTime(double)':
Origin750Parser.h:74:175: error: no matching function for call to 
'boost::posix_time::seconds::seconds(double)'
   return 
boost::posix_time::ptime(boost::gregorian::date(boost::gregorian::gregorian_calendar::from_julian_day_number(jdt+1)),
 boost::posix_time::seconds((jdt-(int)jdt)*86400));


   ^
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_types.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/time_formatters.hpp:16,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:24,
 from Origin750Parser.h:36,
 from Origin800Parser.h:32,
 from Origin610Parser.h:32,
 from Origin600Parser.h:32,
 from Origin600Parser.cpp:29:
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: note: 
candidate: 'template boost::posix_time::seconds::seconds(const T&, 
typename boost::enable_if >::type*)'
   explicit seconds(T const& s,
^~~
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: note:   
template argument deduction/substitution failed:
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp: In 
substitution of 'template boost::posix_time::seconds::seconds(const 
T&, typename boost::enable_if >::type*) [with T = 
double]':
Origin750Parser.h:74:175:   required from here
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: error: 
no type named 'type' in 'struct boost::enable_if, 
void>'
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: 
candidate: 'boost::posix_time::seconds::seconds(const 
boost::posix_time::seconds&)'
   class BOOST_SYMBOL_VISIBLE seconds : public time_duration
  ^~~
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note:   
no known conversion for argument 1 from 'double' to 'const 
boost::posix_time::seconds&'
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: 
candidate: 'boost::posix_time::seconds::seconds(boost::posix_time::seconds&&)'
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note:   
no known conversion for argument 1 from 'double' to 
'boost::posix_time::seconds&&'
--- End Message ---
--- Begin Message ---
Source: liborigin2
Source-Version: 2:20110117-3

We believe that the bug you reported is fixed in the latest version of
liborigin2, 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.
Anton Gladky  (supplier of updated liborigin2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 21:35:15 +0100
Source: liborigin2
Binary: liborigin2-dev liborigin2-1v5
Architecture: source
Version: 2:20110117-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 liborigin2-1v5 - library for reading OriginLab Origin 7.5 project files 
(runtime)
 liborigin2-dev - library for reading OriginLab Origin 7.5 project files 
(developme
Closes: 914145

Bug#915619: marked as done (golang-gopkg-lxc-go-lxc.v2: not compatible with LXC v3)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:18:45 +
with message-id 
and subject line Bug#915619: fixed in golang-gopkg-lxc-go-lxc.v2 
0.0~git20181101.0aadfc3-1
has caused the Debian Bug report #915619,
regarding golang-gopkg-lxc-go-lxc.v2: not compatible with LXC v3
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.)


-- 
915619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gopkg-lxc-go-lxc.v2
Version: 0.0~git20180119.b964baa-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer, lxc > 3 broke your autopkgtest, and indeed it needs an
updated.

Patches are available upstream, ubuntu already cherry-picked them early
this year:
http://launchpadlibrarian.net/359268942/golang-gopkg-lxc-go-lxc.v2_0.0~git20180119.b964baa-1ubuntu1_0.0~git20180119.b964baa-1ubuntu2.diff.gz

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: golang-gopkg-lxc-go-lxc.v2
Source-Version: 0.0~git20181101.0aadfc3-1

We believe that the bug you reported is fixed in the latest version of
golang-gopkg-lxc-go-lxc.v2, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Clément Hermann  (supplier of updated 
golang-gopkg-lxc-go-lxc.v2 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: Wed, 05 Dec 2018 18:52:55 +0100
Source: golang-gopkg-lxc-go-lxc.v2
Binary: golang-gopkg-lxc-go-lxc.v2-dev
Architecture: source all
Version: 0.0~git20181101.0aadfc3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Clément Hermann 
Description:
 golang-gopkg-lxc-go-lxc.v2-dev - Go bindings for liblxc
Closes: 915619
Changes:
 golang-gopkg-lxc-go-lxc.v2 (0.0~git20181101.0aadfc3-1) unstable; urgency=medium
 .
   [ Alexandre Viau ]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [ Clément Hermann ]
   * New upstream snapshot (Closes: #915619)
   * d/rules: Use DH_GOLANG_EXCLUDES_ALL instead of an override
   * d/control: Bump Standards-Version to 4.2.1 (no change)
   * Switch to debhelper compat level 11
Checksums-Sha1:
 2bc16dff1c530cc123a385b07a8c6b0b2f42390d 2384 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1.dsc
 05d3165c46997be759c86a81b9e8b9e7e583952c 38775 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3.orig.tar.gz
 62625c410b856f48c057ecbe53e348bea819925c 3316 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1.debian.tar.xz
 5db6d02da5bfdcf394163b6b0ed6c7842c44ce69 27844 
golang-gopkg-lxc-go-lxc.v2-dev_0.0~git20181101.0aadfc3-1_all.deb
 e4d350a3b398d21e3c2818be8bf64c1544392d6c 6236 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1_amd64.buildinfo
Checksums-Sha256:
 e098bde17538f7d74d3cf6fa3189c06785ede09396d146407b169277d878e444 2384 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1.dsc
 25e68d0487e7175f2c14305106b03a914a7cb164ca1a34d63d6394f3e58f0507 38775 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3.orig.tar.gz
 427eec943df3ec85d623f53ede8867c51dcda0a68f358096481a251c6d2ee960 3316 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1.debian.tar.xz
 cf97fd6ae75d44d97165805beda38d70ffb87259828623d9d872f51fa9c08020 27844 
golang-gopkg-lxc-go-lxc.v2-dev_0.0~git20181101.0aadfc3-1_all.deb
 5ca4f22cb63ef62c9ef17c848b4f03ca0b1e737b39cc5e4c88aef96088d6ceef 6236 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1_amd64.buildinfo
Files:
 996fd58bafa8af22d6dc114807e63808 2384 devel optional 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3-1.dsc
 d2ac941b3e0bf02882411d627471716b 38775 devel optional 
golang-gopkg-lxc-go-lxc.v2_0.0~git20181101.0aadfc3.orig.tar.gz
 

Bug#916035: marked as done (kraptor FTBFS with allegro4.4 2:4.4.2-13)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:19:32 +
with message-id 
and subject line Bug#916035: fixed in kraptor 0.0.20040403+ds-2
has caused the Debian Bug report #916035,
regarding kraptor FTBFS with allegro4.4 2:4.4.2-13
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.)


-- 
916035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kraptor
Version: 0.0.20040403+ds-1
Severity: serious
Tags: ftbfs

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

...
src/explos.c: In function 'dibujar_explosion':
src/explos.c:129:20: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
   x2 -= fixtoi(fmul(itofix(tmp->spr->w), tmp->r))/2;
^~~~
...
src/enemigo.c: In function 'agregar_disparo_ene':
src/enemigo.c:498:24: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 
3)) );
^~~~
...
gcc obj/linux/azar.o obj/linux/bomba.o obj/linux/captura.o obj/linux/cinema.o 
obj/linux/clima.o obj/linux/combo.o obj/linux/config.o obj/linux/data.o 
obj/linux/datafind.o obj/linux/enemigo.o obj/linux/error.o obj/linux/explos.o 
obj/linux/filedata.o obj/linux/game.o obj/linux/global.o obj/linux/guiprocs.o 
obj/linux/guitrans.o obj/linux/humo.o obj/linux/ia.o obj/linux/joymnu.o 
obj/linux/jugador.o obj/linux/kfbuffer.o obj/linux/krstring.o obj/linux/main.o 
obj/linux/mapa.o obj/linux/menu.o obj/linux/partic.o obj/linux/pmask.o 
obj/linux/premio.o obj/linux/rvideo.o obj/linux/savedlg.o obj/linux/shopping.o 
obj/linux/sombras.o obj/linux/sonido.o obj/linux/wordwrap.o -o 
bin/kraptor_linux.bin -laldmb -ldumb `allegro-config --libs` `dpkg-buildflags 
--get LDFLAGS`
/usr/bin/ld: obj/linux/enemigo.o: undefined reference to symbol 
'fmul@@GLIBC_2.28'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
--- End Message ---
--- Begin Message ---
Source: kraptor
Source-Version: 0.0.20040403+ds-2

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated kraptor 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: Sun, 09 Dec 2018 21:40:38 +0100
Source: kraptor
Binary: kraptor kraptor-data
Architecture: source
Version: 0.0.20040403+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Andreas Rönnquist 
Description:
 kraptor- Classic shoot 'em up scroller game
 kraptor-data - Classic shoot 'em up scroller game -- data files
Closes: 916035
Changes:
 kraptor (0.0.20040403+ds-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to build with allegro fix*-functions, instead
 of f*-functions which conflict with newer glibc.
 (Closes: #916035)
Checksums-Sha1:
 7c6bf1ca0015703670e8f9cc8d7e450a9e898232 2166 kraptor_0.0.20040403+ds-2.dsc
 aaa00c495265e5c7bdc19f9ff4e6980681143736 51884 
kraptor_0.0.20040403+ds-2.debian.tar.xz
 69c67900f740bc42df2084920ea4dcbae70eee80 8338 
kraptor_0.0.20040403+ds-2_source.buildinfo
Checksums-Sha256:
 c47e06bd96aaf06228008813ac643728851860a7658579c924a87984f1d1c685 2166 
kraptor_0.0.20040403+ds-2.dsc
 3d3fda9ad541e10d2f97f2d26e31c76c9adf4eaa7837f1a6d91acae4cf3d58f1 51884 
kraptor_0.0.20040403+ds-2.debian.tar.xz
 ea9d6d05fdba83cc6104272ab4ec0369b85199018200286ce60f65515a102618 8338 
kraptor_0.0.20040403+ds-2_source.buildinfo
Files:
 f9b0f457d1396ceb4c0711edfbf24c9b 2166 games optional 
kraptor_0.0.20040403+ds-2.dsc
 349765a2f39442c42fc50491c4229eef 51884 games optional 
kraptor_0.0.20040403+ds-2.debian.tar.xz
 411db716caf796f9f3f602146c66cd25 8338 games optional 
kraptor_0.0.20040403+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#916033: marked as done (alex4 FTBFS with allegro4.4 2:4.4.2-13)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 21:16:44 +
with message-id 
and subject line Bug#916033: fixed in alex4 1.1-8
has caused the Debian Bug report #916033,
regarding alex4 FTBFS with allegro4.4 2:4.4.2-13
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.)


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

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

...
shooter.c: In function 's_update_object':
shooter.c:503:26: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
  ^~~~
  fixmul
shooter.c:503:46: warning: implicit declaration of function 'fsin'; did you 
mean 'fixsin'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
  ^~~~
  fixsin
shooter.c:508:46: warning: implicit declaration of function 'fcos'; did you 
mean 'feof'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fcos(itofix(o->t;
  ^~~~
  feof
main.c: In function 'draw_custom_ending':
main.c:1215:23: warning: implicit declaration of function 'fcos'; did you mean 
'feof'? [-Wimplicit-function-declaration]
  r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * 
fsin(itofix((int)(game_count / 2.7))) );
   ^~~~
   feof
main.c:1215:60: warning: implicit declaration of function 'fsin'; did you mean 
'fixsin'? [-Wimplicit-function-declaration]
  r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * 
fsin(itofix((int)(game_count / 2.7))) );
^~~~
fixsin
...
cc -Wl,-z,relro -Wl,-z,now -o alex4 actor.o edit.o map.o player.o shooter.o 
unix.o bullet.o hisc.o options.o script.o timer.o control.o main.o particle.o 
scroller.o token.o -laldmb -ldumb `allegro-config --libs`
/usr/bin/ld: shooter.o: undefined reference to symbol 'fmul@@GLIBC_2.28'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:12: alex4] Error 1
--- End Message ---
--- Begin Message ---
Source: alex4
Source-Version: 1.1-8

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated alex4 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: Sun, 09 Dec 2018 21:01:39 +0100
Source: alex4
Binary: alex4 alex4-data
Architecture: source
Version: 1.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Andreas Rönnquist 
Description:
 alex4  - Alex the Allegator 4 - a retro platform game
 alex4-data - Alex the Allegator 4 - game data
Closes: 916033
Changes:
 alex4 (1.1-8) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to build with fix*-functions, for Allegros fixed math,
 instead of f*-functions which conflict with newer glibc.
 (Closes: #916033)
Checksums-Sha1:
 afa6fbe62df47bc1f07ca84deaa3886cb27e31b6 2057 alex4_1.1-8.dsc
 f7b5301fdbd33c6d9fea9dbec3b32998ff98db44 18752 alex4_1.1-8.debian.tar.xz
 8723833bac696b8058cd86b36036d60c96918a52 8207 alex4_1.1-8_source.buildinfo
Checksums-Sha256:
 a0580bed0aeb65001042e3001797eae41d0b873cc76fe41a479c304a2f6aecf3 2057 
alex4_1.1-8.dsc
 3c9342d567c0fae695ff6eb2907c542af957291843f5747e3f46f31e7da11b46 18752 
alex4_1.1-8.debian.tar.xz
 39d3ae4b31ed8219f34117dc297ddd18e5bd54cd5d5f3fcfeb8d73560670ec64 8207 
alex4_1.1-8_source.buildinfo
Files:
 

Bug#911437: gitlab-ci-multi-runner: FTBFS with golang-github-prometheus-client-golang/0.9.0-1

[Dmitry Smirnov]

On Tuesday, 20 November 2018 5:26:02 AM AEDT Andreas Henriksson wrote:
> It seems you've forgot to push upstream/pristine-tar branches
> and tags when you did the last update/upload of the package.
> Could you please push them?

Done. FYI I did not forget to push - I was working in haste and just did not 
import orig.tar at a time: maintaining those useless branches always take 
precious time from something more important...


> I'm attaching a patch to fix the FTBFS bug that seems to have
> just gotten this package removed from testing.

Thank you very much for your help. It is very nice that you've managed to 
find solution to this problem.

-- 
Best wishes,
 Dmitry Smirnov.

---

Journalism is printing what someone else does not want printed: everything
else is public relations.
-- George Orwell


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

Processed: tagging 914556

[Debian Bug Tracking System]

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

> tags 914556 + pending
Bug #914556 [src:linux] linux: FTBFS on arm64: changed ABI
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#916079: hyperic-sigar FTBFS with glibc 2.28

[Adrian Bunk]

Source: hyperic-sigar
Version: 1.6.4+dfsg-2.1
Severity: serious
Tags: ftbfs

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

...
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1148:22: error: 
called object 'major' is not a function or function pointer
   [cc]  #define ST_MAJOR(sb) major((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1237:23: note: 
in expansion of macro 'ST_MAJOR'
   [cc]  if ((major == ST_MAJOR(sb)) &&
   [cc]^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1232:23: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1149:22: error: 
called object 'minor' is not a function or function pointer
   [cc]  #define ST_MINOR(sb) minor((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1238:24: note: 
in expansion of macro 'ST_MINOR'
   [cc]  ((minor == ST_MINOR(sb)) || (minor == 0)))
   [cc] ^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1232:30: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1149:22: error: 
called object 'minor' is not a function or function pointer
   [cc]  #define ST_MINOR(sb) minor((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1289:26: note: 
in expansion of macro 'ST_MINOR'
   [cc]  if (minor == ST_MINOR(sb)) {
   [cc]   ^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1232:30: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]   ^
   [cc] /build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c: In 
function 'get_iostat_procp':
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1148:22: error: 
called object 'major' is not a function or function pointer
   [cc]  #define ST_MAJOR(sb) major((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1340:23: note: 
in expansion of macro 'ST_MAJOR'
   [cc]  if ((major == ST_MAJOR(sb)) && (minor == ST_MINOR(sb))) {
   [cc]^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1335:23: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1149:22: error: 
called object 'minor' is not a function or function pointer
   [cc]  #define ST_MINOR(sb) minor((sb).st_rdev)
   [cc]   ^
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1340:50: note: 
in expansion of macro 'ST_MINOR'
   [cc]  if ((major == ST_MAJOR(sb)) && (minor == ST_MINOR(sb))) {
   [cc]   ^~~~
   [cc] 
/build/1st/hyperic-sigar-1.6.4+dfsg/src/os/linux/linux_sigar.c:1335:30: note: 
declared here
   [cc]  unsigned long major, minor;
   [cc]   ^

Bug#911437: Bug #911437 in gitlab-ci-multi-runner marked as pending

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #911437 in gitlab-ci-multi-runner 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/go-team/packages/gitlab-ci-multi-runner/commit/36462eebc531013bb6d89612b581b1a714e156c1


New patch to fix FTBFS (Closes: #911437). Thanks, Andreas Henriksson.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911437

Processed: Bug #911437 in gitlab-ci-multi-runner marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911437 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS with 
golang-github-prometheus-client-golang/0.9.0-1
Added tag(s) pending.

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

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

On Sun, 9 Dec 2018 20:35:02 +0100
Markus Koschany  wrote:

>Hello Andreas,
>
>
>Am 09.12.18 um 16:07 schrieb Andreas Ronnquist:
>> tags 916037 + patch
>> thanks
>> 
>> Patch attached to fix this build error (Which I am the cause of).  
>
>Please feel free to upload your fix as needed. Since all packages are
>team-maintained and you are a member of the team and know why the
>packages FTBFS, it makes absolutely sense that you handle the uploads
>too.
>

You are right - I'll take care of the uploads. Not doing it is because
I got unsure if I should do it, because I don't want to disturb some
Vcs-migration to salsa - All three of the packages have still SVN in the
Vcs-* fields, and one of them in addition even has a (non-gbp) git
repository on Salsa.

But with that message, I'll take care of it. (Oh, how simple everything
would be if everything was just gbp, and be done with it) :)

/Andreas
mailingli...@gusnan.se
gus...@debian.org


pgpvPwoPe00rf.pgp
Description: OpenPGP digital signatur

Bug#915639: Apologies for shibboleth-resolver FTBFS

[Sam Hartman]

Hi.

I am not sure how I managed to produce the binary package for amd64.  I
*thought* that I used sbuild in a clean sid chroot to do so, but it's
quite clear from trying to reproduce that that I failed.  I'm somewhat
baffled because my work flow makes it hard for something not coming out
of sbuild with a clean chroot to end up in the right place to be
uploaded, but it's certainly the case that the dsc I uploaded simply
does not work.

I regret that the package was so broken and that I managed not to catch
it.  I did intend to avoid the obvious failure of building on my host
system, and I thought I had a work flow that was not vulnerable to
screwing that up.
Anyway, apologies that you had to waste your time on my error.

Bug#916077: virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae

[Andreas Beckmann]

Package: virtualbox-dkms
Version: 5.2.22-dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + virtualbox-guest-additions-iso

Hi,

virtualbox-dkms fails to build a module for 4.18.0-3-686,
4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case
it matters). There are no problems bulding for 4.18.0-3-amd64.
The (attached) make.log starts with:


DKMS make.log for virtualbox-5.2.22 for kernel 4.18.0-3-686 (i686)
Sun Dec  9 20:00:18 UTC 2018
make: Entering directory '/usr/src/linux-headers-4.18.0-3-686'
make[4]: dpkg-architecture: Command not found
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvSem.o
In file included from 
/var/lib/dkms/virtualbox/5.2.22/build/include/VBox/types.h:30:0,
 from 
/var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/../SUPDrvInternal.h:35,
 from 
/var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:280:9: error: 
unknown type name '__uint128_t'
 typedef __uint128_t uint128_t;
 ^~~
/var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:299:9: error: 
unknown type name '__int128_t'
 typedef __int128_t int128_t;
 ^~


Andreas


make.log.gz
Description: application/gzip

Processed: virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + virtualbox-guest-additions-iso
Bug #916077 [virtualbox-dkms] virtualbox-dkms: module FTBFS for 4.18.0-3-686, 
4.18.0-3-686-pae
Added indication that 916077 affects virtualbox-guest-additions-iso

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

Bug#916074: pcc: useless without libpcc-dev

[Sven Joachim]

Package: pcc
Version: 1.2.0~DEVEL+20181202-1
Severity: serious
Control: block -1 by 915633

Without libpcc-dev, pcc cannot compile any but the most trivial C
programs (e.g. #including  causes the preprocessor to complain
about a missing stddef.h) and cannot link any C program because ld fails
to find crtbegin.o.

For this reason I think that libpcc-dev should be bumped from Recommends
to Depends.  Of course this requires pcc-libs to be uploaded to unstable
and to be built on all (release) architectures where pcc is currently
available.  The initial upload to experimental FTBFS everywhere except
on amd64 (see #915633).


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

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

Versions of packages pcc depends on:
ii  libc6  2.28-2

Versions of packages pcc recommends:
ii  libpcc-dev  1.2.0~DEVEL+20180604-1

pcc suggests no packages.

-- no debconf information

Processed: pcc: useless without libpcc-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 915633
Bug #916074 [pcc] pcc: useless without libpcc-dev
916074 was not blocked by any bugs.
916074 was not blocking any bugs.
Added blocking bug(s) of 916074: 915633

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

Bug#916062: Bug #916062 in cowdancer marked as pending

[James Clarke]

Control: tag -1 pending

Hello,

Bug #916062 in cowdancer 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/pbuilder-team/cowdancer/commit/92044b3f09b5085e99ee7361df3798ff5e49c931


Fix FTBFS with glibc 2.28

Closes: #916062


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916062

Processed: Bug #916062 in cowdancer marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916062 [src:cowdancer] cowdancer FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Markus Koschany]

Hello Andreas,


Am 09.12.18 um 16:07 schrieb Andreas Ronnquist:
> tags 916037 + patch
> thanks
> 
> Patch attached to fix this build error (Which I am the cause of).

Please feel free to upload your fix as needed. Since all packages are
team-maintained and you are a member of the team and know why the
packages FTBFS, it makes absolutely sense that you handle the uploads too.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#916053: marked as done (ocfs2-tools FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 19:36:03 +
with message-id 
and subject line Bug#916053: fixed in ocfs2-tools 1.8.5-7
has caused the Debian Bug report #916053,
regarding ocfs2-tools FTBFS with glibc 2.28
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.)


-- 
916053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocfs2-tools
Version: 1.8.5-6
Severity: serious
Tags: ftbfs

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

...
In file included from o2cb_abi.c:52:
../include/ocfs2/ocfs2.h:222:2: error: unknown type name 'loff_t'
  loff_t d_off; /* Offset of structure in the file */
  ^~
make[2]: *** [../Postamble.make:40: o2cb_abi.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ocfs2-tools
Source-Version: 1.8.5-7

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated ocfs2-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 19:58:40 +0100
Source: ocfs2-tools
Binary: ocfs2-tools ocfs2-tools-dev
Architecture: source
Version: 1.8.5-7
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 ocfs2-tools - tools for managing OCFS2 cluster filesystems
 ocfs2-tools-dev - tools for managing OCFS2 cluster filesystems - development 
files
Closes: 916053
Changes:
 ocfs2-tools (1.8.5-7) unstable; urgency=medium
 .
   * debian/patches: fix FTBFS with glibc 2.28 (Closes: #916053)
Checksums-Sha1:
 630c416ebc8ddff95ea37c39335d28818ff0828d 2324 ocfs2-tools_1.8.5-7.dsc
 ea8b09995c8e7bc1f09ae34b7ba33d8db0d29a42 33140 
ocfs2-tools_1.8.5-7.debian.tar.xz
 ac00507ddf534d8117bb1149a338bffbfbeb251c 7607 
ocfs2-tools_1.8.5-7_source.buildinfo
Checksums-Sha256:
 20d508e98eaf51da7bd07afe9f5362ffd4275f7e2616b9c32c5547825b7af4a0 2324 
ocfs2-tools_1.8.5-7.dsc
 564eaf7836d9103bc46c5bd605809364e1a9e805a840588abdba02c3b317f12c 33140 
ocfs2-tools_1.8.5-7.debian.tar.xz
 4306262688a3451c0281f454758be9d240197c25fe0c2479248d3e21f7904f45 7607 
ocfs2-tools_1.8.5-7_source.buildinfo
Files:
 63a1cb68ec2ef3dde850feacd3dbdd53 2324 admin optional ocfs2-tools_1.8.5-7.dsc
 0605e328b270473d23142b757ba6fe47 33140 admin optional 
ocfs2-tools_1.8.5-7.debian.tar.xz
 954290e4d54676a9847af05d7c0ff0bb 7607 admin optional 
ocfs2-tools_1.8.5-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExaW53cM9k/u2PWfIMofYmpfNqHsFAlwNZ/ISHHZ2aWRpY0Bk
ZWJpYW4ub3JnAAoJEDKH2JqXzah79hEQAJ9MHVn+G059RPoBZSqeW16cv9AcdeYh
Pop3Pw1HpKqSovC6ruGsZ3n0CT2Npr8fbCfeQIPvU1dxchQhZXHSN1qlfuOOhzLq
vsQQt0LfF/2cAbpDPbTP3SI59LGORq9hKOVW9L/EsoOA2OQ/2UpAMFa+IjiTybOs
yNssT3TXmypFhjB/g+Fi7h5iE1LlcHafGV62cLwMaiqaqGN+QDUfIZH3Ag4BH3sy
saTL/7oZLFakAroHBP/vW+I5D0/pbx5RF3fpPQ89n/h3by9FA4mXoZImPyEUykdR
eP9sKr3Mn8Q+vcQ92KSOWMin1EXLulq5NHYub7c3duP7wHhiGdHiSiARX0s0VPRR
nYn5V83uJW4mw8TK0nba7Oh10Ul5Yhe2kci/oVEE/C9nfS8Il0AI0Xp9MSAHZ4Qc
KWJLlNe1tJaD+mtz8omEbjkKLBAF5A1h+GvCJistXwoaxrRhPpk3Orgc6v9CNYRr
33RmYJkybs5PCuYnhmv1CwLb2w6OVlGJJ3yJtD+9CRHU0Wt7QSXAs73rFbMCdY9V
QZlPakWrq2QHTPlCW1L0amyW2pgh0IfDC67RXnt0UyOGxoikRjdctg/UikCLFoQb
KS99u0ZeaoTD4HSiASaChiJ8s4urRII8N0BCZGJGYuW9l1CnSs0fylv8/i4HRbQh
3PsGNPHDv9vt
=Z57r
-END PGP SIGNATURE End Message ---

Bug#913371: gnat-gps fails to build on 32-bit kernels, address space exhaustion.

[Nicolas Boulenguez]

Package: src:gnat-gps
Followup-For: Bug #913371

gnat-gps/18 now fails to build on armhf, while 18-3 was succeeding on
the same architecture.

After investigation, the only successful builds of gnat-gps/18 on 32
bits architectures so far (armhf i386 powerpc) were registered with a
32 bits chroot on a 64 bits machine.

I suggest the following architecture list, with only 64 bits
architectures, but any better idea is welcome.

amd64 arm64 mips64el ppc64el s390x alpha ia64 kfreebsd-amd64 ppc64
riscv64 sparc64

Bug#916070: rootskel FTBFS with glibc 2.28

[Adrian Bunk]

Source: rootskel
Version: 1.125
Severity: serious
Tags: ftbfs

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

...
gcc -Os -Wall get-real-console-linux.c -o get-real-console-linux
get-real-console-linux.c: In function 'main':
get-real-console-linux.c:30:23: warning: implicit declaration of function 
'major' [-Wimplicit-function-declaration]
 printf("%d:%d\n", major(dev), minor(dev));
   ^
get-real-console-linux.c:30:35: warning: implicit declaration of function 
'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration]
 printf("%d:%d\n", major(dev), minor(dev));
   ^
   mknod
/usr/bin/ld: /tmp/cc8kbEaP.o: in function `main':
get-real-console-linux.c:(.text.startup+0x62): undefined reference to `minor'
/usr/bin/ld: get-real-console-linux.c:(.text.startup+0x6f): undefined reference 
to `major'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:24: get-real-console-linux] Error 1

Bug#835590: marked as done (libsoundio1: Missing hard dependency on libjack-jackd2-0)

[Debian Bug Tracking System]

Your message dated Sun, 9 Dec 2018 20:08:02 +0100
with message-id <295a3971-6655-315d-b593-410c64d74...@debian.org>
and subject line Re: libsoundio1: Missing hard dependency on libjack-jackd2-0
has caused the Debian Bug report #835590,
regarding libsoundio1: Missing hard dependency on libjack-jackd2-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.)


-- 
835590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjack-jackd2-0
Version: 1.9.10+20150825git1ed50c92~dfsg-2
Severity: wishlist
Control: clone -1 -2
Control: reassign -2 libsoundio1
Control: retitle -2 libsoundio1: Missing hard dependency on libjack-jackd2-0
Control: found -2 1.0.2-1

libsoundio1 depends on jack_set_port_rename_callback, which is provided
by libjack-jackd2-0 only. libjack-jackd2-0 should provide a symbols file
to know if libjack0 (libjack-0.116) is a valid alternative. libsoundio1
could add a manual dependency on libjack-jackd2-0 while waiting for this
symbols file.


smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
On Sat, 27 Aug 2016 12:31:06 +0200 Javier Serrano Polo 
wrote:
> libsoundio1 depends on jack_set_port_rename_callback, which is provided
> by libjack-jackd2-0 only. libjack-jackd2-0 should provide a symbols file
> to know if libjack0 (libjack-0.116) is a valid alternative. libsoundio1
> could add a manual dependency on libjack-jackd2-0 while waiting for this
> symbols file.

This was fixed in src:jackd2 1.9.10+20150825git1ed50c92~dfsg-4 and is
fixed since the 1.0.2-1+b1 binNMU of libsoundio1, which now depends on
  libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125
and libjack0 1:0.125.0-2 (which provides libjack-0.125) also has the
jack_set_port_rename_callback symbol.


Andreas--- End Message ---

Bug#916065: fdutils FTBFS with glibc 2.28

[Adrian Bunk]

Source: fdutils
Version: 5.5-20060227-7
Severity: serious
Tags: ftbfs buster sid

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

...
driveprm.c: In function 'getdrivenum':
driveprm.c:143:6: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  major(buf->st_rdev) != FLOPPY_MAJOR) {
  ^
driveprm.c:148:8: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
  num = minor( buf->st_rdev );
^
...
gcc -Wl,-z,relro -o getfdprm getfdprm.o -L. -lfdutils 
/usr/bin/ld: ./libfdutils.a(driveprm.o): in function `getdrivenum':
./src/driveprm.c:143: undefined reference to `major'
/usr/bin/ld: ./src/driveprm.c:148: undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:102: getfdprm] Error 1

Bug#916064: ext4magic FTBFS with glibc 2.28

[Adrian Bunk]

Source: ext4magic
Version: 0.3.2-10
Severity: serious
Tags: ftbfs

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

...
recover.c: In function 'recover_file':
recover.c:478:35: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
retval = mknod(helpname, type ,makedev(major, minor));
   ^~~
...
libtool: link: gcc -O2 -g -D_FILE_OFFSET_BITS=64 -g -O2 
-ffile-prefix-map=/build/1st/ext4magic-0.3.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ext4magic 
ext4magic-block.o ext4magic-dir_list.o ext4magic-ext4magic.o 
ext4magic-extent_db.o ext4magic-file_type.o ext4magic-hard_link_stack.o 
ext4magic-imap_search.o ext4magic-inode.o ext4magic-journal.o 
ext4magic-lookup_local.o ext4magic-magic_block_scan.o ext4magic-recover.o 
ext4magic-ring_buf.o ext4magic-util.o  -le2p -luuid -lblkid -lz -lbz2 -lmagic 
-lext2fs
/usr/bin/ld: ext4magic-recover.o: in function `recover_file':
./src/recover.c:478: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:449: ext4magic] Error 1

Bug#916067: fuse-umfuse-ext2 FTBFS with glibc 2.28

[Adrian Bunk]

Source: fuse-umfuse-ext2
Version: 0.4-1.1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fuse-umfuse-ext2.html

...
op_create.c: In function 'old_valid_dev':
op_create.c:45:9: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  return major(dev) < 256 && minor(dev) < 256;
 ^
op_create.c:45:29: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
  return major(dev) < 256 && minor(dev) < 256;
 ^
 mknod
op_create.c: In function 'new_encode_dev':
op_create.c:55:19: error: called object 'major' is not a function or function 
pointer
  unsigned major = major(dev);
   ^
op_create.c:55:11: note: declared here
  unsigned major = major(dev);
   ^
op_create.c:56:19: error: called object 'minor' is not a function or function 
pointer
  unsigned minor = minor(dev);
   ^
op_create.c:56:11: note: declared here
  unsigned minor = minor(dev);
   ^
make[3]: *** [Makefile:1014: umfuseext2_la-op_create.lo] Error 1

Processed: Changing severity

[Debian Bug Tracking System]

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

> severity 915390 serious
Bug #915390 [clazy] clazy: Segmentation fault compiling any file
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Processed: tagging 916061

[Debian Bug Tracking System]

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

> tags 916061 + buster sid
Bug #916061 [src:diod] diod FTBFS with glibc 2.28
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#916062: cowdancer FTBFS with glibc 2.28

[Adrian Bunk]

Source: cowdancer
Version: 0.87
Severity: serious
Tags: ftbfs

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

...
qemuarch.c: In function 'qemu_create_arch_serialdevice':
qemuarch.c:60:16: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   consoledev = makedev(204, 64);
^~~
...
./qemuarch.c:60: undefined reference to `makedev'
/usr/bin/ld: ./qemuarch.c:62: undefined reference to `makedev'
/usr/bin/ld: qemubuilder-qemuarch.o: in function `qemu_create_arch_devices':
./qemuarch.c:85: undefined reference to `makedev'
/usr/bin/ld: ./qemuarch.c:87: undefined reference to `makedev'
/usr/bin/ld: ./qemuarch.c:89: undefined reference to `makedev'
/usr/bin/ld: qemubuilder-qemuarch.o:./qemuarch.c:91: more undefined references 
to `makedev' follow
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:996: qemubuilder] Error 1

Bug#913382: marked as done (fbreader FTBFS with curl 7.62.0)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 18:34:33 +
with message-id 
and subject line Bug#913382: fixed in fbreader 0.12.10dfsg2-3
has caused the Debian Bug report #913382,
regarding fbreader FTBFS with curl 7.62.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.)


-- 
913382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fbreader
Version: 0.12.10dfsg2-2
Severity: serious
Tags: ftbfs buster sid

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

...
ZLCurlNetworkManager.cpp: In member function 'virtual std::__cxx11::string 
ZLCurlNetworkManager::perform(const Vector&) const':
ZLCurlNetworkManager.cpp:287:5: error: duplicate case value
 case CURLE_SSL_CACERT:
 ^~~~
ZLCurlNetworkManager.cpp:281:5: note: previously used here
 case CURLE_PEER_FAILED_VERIFICATION:
 ^~~~
make[3]: *** 
[/build/1st/fbreader-0.12.10dfsg2/zlibrary/core/../../makefiles/subdir.mk:14: 
ZLCurlNetworkManager.o] Error 1


For background see
https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
--- End Message ---
--- Begin Message ---
Source: fbreader
Source-Version: 0.12.10dfsg2-3

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

Debian distribution maintenance software
pp.
Eugene V. Lyubimkin  (supplier of updated fbreader 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: Sun, 09 Dec 2018 18:21:31 +0100
Source: fbreader
Binary: fbreader libzlcore0.13 libzlcore-data libzltext0.13 libzltext-data 
libzlui-gtk libzlui-qt4 libzlcore-dev libzltext-dev
Architecture: source amd64 all
Version: 0.12.10dfsg2-3
Distribution: unstable
Urgency: medium
Maintainer: Eugene V. Lyubimkin 
Changed-By: Eugene V. Lyubimkin 
Description:
 fbreader   - e-book reader
 libzlcore-data - ZLibrary cross-platform development library (support files)
 libzlcore-dev - ZLibrary cross-platform development library (development files)
 libzlcore0.13 - ZLibrary cross-platform development library (shared library)
 libzltext-data - ZLibrary text model/viewer part (support files)
 libzltext-dev - ZLibrary text model/viewer part (development files)
 libzltext0.13 - ZLibrary text model/viewer part (shared library)
 libzlui-gtk - GTK+ interface module for ZLibrary
 libzlui-qt4 - Qt4 interface module for ZLibrary
Closes: 861422 913382
Changes:
 fbreader (0.12.10dfsg2-3) unstable; urgency=medium
 .
   * debian/patches:
 - New patch 0011-zlibrary-unix-curl-avoid-duplicate-case-in-a-switch.
   Fixes building with curl 7.62.0. Thanks to Adrian Bunk for the report
   and the libcurl API change hint. (Closes: #913382)
 - New patch 0012-makefiles-use-externally-passed-PKG_CONFIG-if-availa by
   Helmut Grohne.
   * debian/rules:
 - Enable cross-architecture building. Patch by Helmut Grohne.
   (Closes: #861422)
   * debian/control:
 - Updated Standards-Version to 4.2.1, no changes needed.
 - Added Recommends on sensible-utils (as suggested by lintian).
   * debian/source/format:
 - Created (with '1.0' inside).
   * debian/libzlcore-data.lintian-overrides:
 - Removed a false positive override introduced in 0.12.10dfsg2-1,
   apparently fixed in lintian since.
Checksums-Sha1:
 8315a4b57ca734d2b50013e2b00e29a8de4e297d 2369 fbreader_0.12.10dfsg2-3.dsc
 64345401094701b0ccfaa8425d57be1c0b4c05f0 21765 fbreader_0.12.10dfsg2-3.diff.gz
 7aa4bb3b714be29f6122d9bd59af7333dba9c0da 17343608 
fbreader-dbgsym_0.12.10dfsg2-3_amd64.deb
 ff7ffa5a371d30638b309e20dfe2bfc3b2e962c1 14876 
fbreader_0.12.10dfsg2-3_amd64.buildinfo
 5736d0faa9292480247d70e1b3bc38a30bf4964c 737264 
fbreader_0.12.10dfsg2-3_amd64.deb
 311f713cde284a24b8d3f76849ea668a3eefb6b9 348732 
libzlcore-data_0.12.10dfsg2-3_all.deb
 0fd6723a068ba654d52de98ec8f61ee72c61d481 36108 
libzlcore-dev_0.12.10dfsg2-3_amd64.deb
 94c9df5365fb3bb26aed117bada440934afc5f94 4672612 
libzlcore0.13-dbgsym_0.12.10dfsg2-3_amd64.deb
 926231a3cb30f8f091ce859e8708b1669f17e5cd 204728 

Bug#916061: diod FTBFS with glibc 2.28

[Adrian Bunk]

Source: diod
Version: 1.0.24-3
Severity: serious
Tags: ftbfs

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

...
ops.c: In function 'diod_mknod':
ops.c:808:38: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
 if (mknod (path_s (npath), mode, makedev (major, minor)) < 0
  ^~~
gcc -Wall -g -O2 -ffile-prefix-map=/build/1st/diod-1.0.24=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o diod 
diod.o ops.o exp.o ioctx.o fid.o xattr.o ../libdiod/libdiod.a 
../libnpclient/libnpclient.a ../libnpfs/libnpfs.a ../liblsd/liblsd.a -lwrap 
-lpthread -llua5.1  -lm -ldl -lmunge -lcap
/usr/bin/ld: ops.o: in function `diod_mknod':
./diod/ops.c:808: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:460: diod] Error 1

Bug#916060: tuxmath: Starts and immediately closes

[Vangelis Skarmoutsos]

Package: tuxmath
Version: 2.0.3-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to start Tuxmath, it looks like it starts and immediately (msec)
closes.

When run from terminal it shows:

$ tuxmath
Initializing Tux4Kids-Common 0.1.1
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

(process:16281): librsvg-WARNING **: 19:54:36.690: element id="#default" does
not exist
Σφάλμα κατάτμησης (segmentation fault)



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

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

Versions of packages tuxmath depends on:
ii  libc62.27-8
ii  libsdl-image1.2  1.2.12-10
ii  libsdl-mixer1.2  1.2.12-15
ii  libsdl-net1.21.2.8-6
ii  libsdl1.2debian  1.2.15+dfsg2-4
ii  libt4k-common0   0.1.1-4
ii  tuxmath-data 2.0.3-4

tuxmath recommends no packages.

tuxmath suggests no packages.

-- no debconf information

Processed: tagging 914495

[Debian Bug Tracking System]

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

> retitle 914495 linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: linux image installed via 
4.18.0-3 stops gdm starting on T500 and X201
Changed Bug title to 'linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]' from 'linux-image-4.18.0-3-amd64: does not boot here'.
Changed Bug title to 'linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]' from 'linux-image-4.18.0-3-amd64: linux image installed via 
4.18.0-3 stops gdm starting on T500 and X201'.
> notfound 914495 4.19.5-1~exp1
Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Ignoring request to alter found versions of bug #914495 to the same values 
previously set
Ignoring request to alter found versions of bug #914980 to the same values 
previously set
> tags 914495 fixed-upstream
Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> forwarded 914495 https://bugs.freedesktop.org/show_bug.cgi?id=108850
Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
> forcemerge 914495 915178 915641 915674 915954
Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Bug #915178 [src:linux] i915: unable to handle kernel NULL pointer dereference 
at 0008
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Marked as found in versions linux/4.18.20-1.
Added tag(s) fixed-upstream.
Bug #915674 [src:linux] i915 driver crash on kernel 4.18.0-3 (buster/testing)
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Severity set to 'important' from 'normal'
Marked as found in versions linux/4.18.20-1.
Added tag(s) fixed-upstream.
Bug #915641 [src:linux] linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 
chipset.
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Marked as found in versions linux/4.18.20-1.
Added tag(s) fixed-upstream.
Bug #915954 [src:linux] inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Severity set to 'important' from 'serious'
Marked as found in versions linux/4.18.20-1.
Added tag(s) fixed-upstream.
Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 
gen4/gen5]
Merged 914495 914980 915178 915641 915674 915954
> thanks
Stopping processing here.

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

Bug#916054: procmeter3 FTBFS with glibc 2.28

[Adrian Bunk]

Source: procmeter3
Version: 3.6-1
Severity: serious
Tags: ftbfs buster sid

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

...
longrun.c:41:24: error: unknown type name 'loff_t'; did you mean 'off_t'?
 static void read_cpuid(loff_t address, int *eax, int *ebx, int *ecx, int *edx) 
{
^~

Bug#916053: ocfs2-tools FTBFS with glibc 2.28

[Adrian Bunk]

Source: ocfs2-tools
Version: 1.8.5-6
Severity: serious
Tags: ftbfs

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

...
In file included from o2cb_abi.c:52:
../include/ocfs2/ocfs2.h:222:2: error: unknown type name 'loff_t'
  loff_t d_off; /* Offset of structure in the file */
  ^~
make[2]: *** [../Postamble.make:40: o2cb_abi.o] Error 1

Bug#916052: alsa-oss FTBFS with glibc 2.28

[Adrian Bunk]

Source: alsa-oss
Version: 1.1.6-1
Severity: serious
Tags: ftbfs

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

...
In file included from alsa-oss.c:736:
stdioemu.c:40:10: fatal error: libio.h: No such file or directory
 #include 
  ^
compilation terminated.
make[2]: *** [Makefile:517: alsa-oss.lo] Error 1

Bug#916049: cloop FTBFS with glibc 2.28

[Adrian Bunk]

Source: cloop
Version: 3.14.1.2
Severity: serious
Tags: ftbfs buster sid

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

...
cc -Wall -O2 -g -O2 -ffile-prefix-map=/build/1st/cloop-3.14.1.2=. 
-fstack-protector-strong -Wformat -Werror=format-security -flto -Wl,-z,relro 
-Wl,-z,now -flto -o extract_compressed_fs extract_compressed_fs.c -lz
extract_compressed_fs.c: In function 'main':
extract_compressed_fs.c:52:2: error: unknown type name 'loff_t'; did you mean 
'off_t'?
  loff_t *offsets;
  ^~
  off_t
extract_compressed_fs.c:54:2: error: unknown type name 'loff_t'; did you mean 
'off_t'?
  loff_t compressed_bytes, uncompressed_bytes, block_modulo;
  ^~
  off_t
extract_compressed_fs.c:121:40: error: 'loff_t' undeclared (first use in this 
function); did you mean 'off_t'?
  offsets_size = total_offsets * sizeof(loff_t);
^~
off_t
extract_compressed_fs.c:121:40: note: each undeclared identifier is reported 
only once for each function it appears in
extract_compressed_fs.c:122:21: error: expected expression before ')' token
  offsets = (loff_t *)malloc(offsets_size);
 ^
make[2]: *** [Makefile:56: extract_compressed_fs] Error 1

Bug#916048: nwchem FTBFS with glibc 2.28

[Adrian Bunk]

Source: nwchem
Version: 6.8+47+gitdf6c956-3
Severity: serious
Tags: ftbfs

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

...
util_fadvise.c: In function 'util_fadvise':
util_fadvise.c:47:5: error: unknown type name 'loff_t'; did you mean 'off_t'?
 loff_t offset = 0;
 ^~
 off_t
util_fadvise.c:48:5: error: unknown type name 'loff_t'; did you mean 'off_t'?
 loff_t length = fd_stat.st_size;
 ^~
 off_t
make[3]: *** [../config/makefile.h:2699: 
/build/1st/nwchem-6.8+47+gitdf6c956/lib/LINUX64/libnwcutil.a(util_fadvise.o)] 
Error 1

Bug#916046: libsqlite3-0 might need Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)

[Adrian Bunk]

Package: libsqlite3-0
Version: 3.26.0-1
Severity: serious
Control: block -1 by 915938

  Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)
(assuming #915938 will be fixed in version 0.11.0-4)
might be correct to prevent people using testing or stretch-backports
to end up using a problematic combination of packages.

Processed: libsqlite3-0 might need Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 915938
Bug #916046 [libsqlite3-0] libsqlite3-0 might need Breaks: python-migrate (<< 
0.11.0-4~), python3-migrate (<< 0.11.0-4~)
916046 was not blocked by any bugs.
916046 was not blocking any bugs.
Added blocking bug(s) of 916046: 915938

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

Processed: severity of 915938 is serious

[Debian Bug Tracking System]

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

> severity 915938 serious
Bug #915938 [migrate] migrate: Enable compatability with sqlite >= 3.26
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#916000: ncbi-blast+: FTBFS - Makefile.flat: No such file or directory

[Aaron M. Ucko]

Andreas Metzler  writes:

> ncbi-blast+ FTBFS on current sid:

Thanks for the report!  It looks like ncbi-blast+ needs another round of
formal patches for compatibility with current Boost.  The following
upstream changes should collectively take care of it:

https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision=79910
https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision=79926
https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision=79928
https://www.ncbi.nlm.nih.gov/viewvc/v1?view=revision=79929

Olivier, will you have time to integrate these changes, or should I?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#901185: [Debconf-devel] Bug#901185: me too

[Luca Boccassi]

On Tue, 12 Jun 2018 06:22:09 +0100 Colin Watson 
wrote:
> On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> > On 2018-06-11 Colin Watson  wrote:
> > > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > > yes, resetting IFS to its default value in confmodule helps.
> > 
> > > Thanks.  For completeness, could you try this variant patch?  If
shells
> > > are going to be unreliable about setting IFS in this way, then
I'd
> > > rather just separate out the assignments altogether.
> > [snip]
> > 
> > Yes, this variant of the patch also works.
> > 
> > Thanks to your handholding we now have a minimal reproducer for the
> > issue:
> 
> Thanks.  Now that you have a reproducer that doesn't involve debconf
and
> so I won't be interfering with debugging, I've uploaded debconf
1.5.67
> with that confmodule patch.  I know it's a bash5 bug and will
hopefully
> be fixed, but we might as well be conservative in debconf when it's
easy
> to do so.
> 
> -- 
> Colin Watson   [cjwatson@debian.o
rg]

Hi,

FYI, this was fixed in bash 5.0 beta1:

$ ./bash --version
GNU bash, version 5.0.0(1)-beta (x86_64-pc-linux-gnu)
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ ./bash -o posix -c 'v=ok; v=bug read x 

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

Bug#891778: marked as done (zatacka crashes on map selection)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 15:40:26 +
with message-id 
and subject line Bug#891778: fixed in zatacka 0.1.8-5.2
has caused the Debian Bug report #891778,
regarding zatacka crashes on map selection
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.)


-- 
891778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zatacka
Version: 0.1.8-5
Severity: serious

Start the game and press m

Backtrace:
#0  0x76da8a52 in __readdir (dirp=dirp@entry=0x0)
at ../sysdeps/posix/readdir.c:44
#1  0x7084 in menu (screen=0x557a02e0) at fx.cpp:425
#2  0x5628 in main (argc=, argv=)
at main.cpp:40
--- End Message ---
--- Begin Message ---
Source: zatacka
Source-Version: 0.1.8-5.2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated zatacka package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 16:07:27 +0100
Source: zatacka
Binary: zatacka
Architecture: source
Version: 0.1.8-5.2
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Dantas 
Changed-By: Markus Koschany 
Description:
 zatacka- arcade multiplayer game like nibbles
Closes: 891778
Changes:
 zatacka (0.1.8-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix crashing game because of missing maps directory.
 Thanks to Arian Bunk for the report and Bernhard Übelacker for the patch.
 (Closes: #891778)
Checksums-Sha1:
 3db1a497b8f608e20d15229bbc3ebc4c389ed92d 2091 zatacka_0.1.8-5.2.dsc
 610014fef6e477071ef922513eb3e2ea1cc3c09d 12384 zatacka_0.1.8-5.2.debian.tar.xz
 a1dc5a699c6c9084b70daf6f4933fcfb0279f5a5 10394 
zatacka_0.1.8-5.2_amd64.buildinfo
Checksums-Sha256:
 06778bec49eb2244403e8ff89868a8187ac495ef2689c97fd6c30f10330c9bbb 2091 
zatacka_0.1.8-5.2.dsc
 9c41ad8d1cfcc6dfc55239ac26a0c22e79e52a3ea04e145f90b49a9ad6116c04 12384 
zatacka_0.1.8-5.2.debian.tar.xz
 52ba6a34dd9766bb156308284725a9f0d9ce677da52a32435e7f62300ed61e09 10394 
zatacka_0.1.8-5.2_amd64.buildinfo
Files:
 ee3da108c6690e9866a89346ced0188e 2091 games optional zatacka_0.1.8-5.2.dsc
 256ca382e5c237c966e520bee722bbd8 12384 games optional 
zatacka_0.1.8-5.2.debian.tar.xz
 aa0538741e4b735a3507298bdef339b7 10394 games optional 
zatacka_0.1.8-5.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlwNMR1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkxaQP/27dsMac/ELHj/b/ijJn658UorbE4PmcfycN
eUI2DJOsHaFGj7MYgYlPa/X2GUzlm2jnDKuTSqL/ekGyU8gesHuCdg59s5f2NfZW
hmhLNjGczQ0hYAaWBogGd4txxTsLF8Fs1XLa8eiJgX1QR+nbuHzid8tfEI0bymZh
rzSXYJx6zBaIbYvb2NuleRyuR6xwiCkgeQl4la4OO5Lt/faKuWzFpZeHF6GUNoQ4
Jhst3KU7ryae/OVgF4bYsUmr4DYCAO0STVCf3EO66gUnxRhpbyDFCaI/yAHoAOr+
yeaMHpzNcnYa+o9kyU4A1nIv5mv0vl3xyDu3FsbW7EjXX+FKE8i4nIQrxJMdjGiK
KcAB8O7kjlZpSQowlMjW+ZoqMy13Db7oI6XspdlOGbSVnGLbSGDcoveYWAoR5ufN
/t/UrGnqDVV4XorJa161quCtNmGKegMDVYIorHc594ZQm2KhcqqADxZ8mDtv477/
xT9hF2N/P4g6Dt8JUjcURCdz0AepuRod5CIgl1d+xoLcQJDVmtuj7JSQgbthSWQZ
8AJBj3WSJ7mn3mf5DJY3NSk+KAPIiL8rnlbeXq6qgph9RDqDt84128j3mNNp//5m
qwY95T7puPSBI0Kdn8aoCCiDjKMEHsGG9tW9KL4ngywni5WrIGb3j239L4a+f+Xu
OB7JcmWs
=yK70
-END PGP SIGNATURE End Message ---

Bug#915603: Your mail

[Andreas Beckmann]

On Wed, 05 Dec 2018 12:21:05 -0700 Ted Percival  wrote:
> So the solution might just be to add the versioned Build-Depends: g++ (>= 4:7)
> and rebuild to get the old symbols back into the library, rather than bumping
> the soname.

That reminds me of https://bugs.debian.org/911090 where

On 2018-10-22 15:13, Matthias Klose wrote:
> The compat symbol was in GCC 7, and then removed in GCC 8.

So, yes, best do a proper transition ... unless you can easily enumerate
the affected packages and add Breaks against them.

How many more of these time bombs do we have lingering in our packages?


Andreas

Processed: Re: kraptor FTBFS with allegro4.4 2:4.4.2-13

[Debian Bug Tracking System]

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

> tags 916035 + patch
Bug #916035 [src:kraptor] kraptor FTBFS with allegro4.4 2:4.4.2-13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#916035: kraptor FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

tags 916035 + patch
thanks

Attached patch to fix building with fixmul instead of fmul. (I am the
cause of the problem with my allegro4.4 upload)

thanks
-- Andreas Rönnquist
gus...@debian.org
--- a/src/explos.c
+++ b/src/explos.c
@@ -126,10 +126,10 @@
  while (tmp) {
 
   x2 = fixtoi(tmp->x)-x;
-  x2 -= fixtoi(fmul(itofix(tmp->spr->w), tmp->r))/2;
+  x2 -= fixtoi(fixmul(itofix(tmp->spr->w), tmp->r))/2;
 
   y2 = fixtoi(tmp->y)-y;
-  y2 -= fixtoi(fmul(itofix(tmp->spr->h), tmp->r))/2;
+  y2 -= fixtoi(fixmul(itofix(tmp->spr->h), tmp->r))/2;
 
   /* dibujar */
   rotate_scaled_sprite(bmp, tmp->spr, x2, y2, itofix(tmp->rot), tmp->r);
--- a/src/enemigo.c
+++ b/src/enemigo.c
@@ -495,7 +495,7 @@
nueva->dx = ftofix((float)rand_ex(-fixtof(arma_ene[ene->arma_actual].vx)*10.0, fixtof(arma_ene[ene->arma_actual].vx)*10.0) / 10.0);
if (rand()%100 < 10)  nueva->dx = 0;
 
-   nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
+   nueva->dy = fixmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
break;
 
case 2: /* abanico triple */
@@ -527,7 +527,7 @@
if (rand()%100 < 15) // cada tanto, al azar
   {
nueva->dx = ftofix((float)rand_ex(-150, 150) / 10.0);
-   nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
+   nueva->dy = fixmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 3)) );
   }
 
break;

Processed: Re: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Debian Bug Tracking System]

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

> tags 916037 + patch
Bug #916037 [src:liquidwar] liquidwar FTBFS with allegro4.4 2:4.4.2-13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Tagging patch

[Debian Bug Tracking System]

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

> tags 916033 + patch
Bug #916033 [src:alex4] alex4 FTBFS with allegro4.4 2:4.4.2-13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

tags 916037 + patch
thanks

Patch attached to fix this build error (Which I am the cause of).

/Andreas
gus...@debian.org
--- a/src/distor.c
+++ b/src/distor.c
@@ -194,7 +194,7 @@
   cycle_tmp /= 2;
   speed--;
 }
-  cycle_tmp = fsqrt (fsqrt (cycle_tmp)) / 2;
+  cycle_tmp = fixsqrt (fixsqrt (cycle_tmp)) / 2;
   cycle_tmp /= SCREEN_W;
   cycle_tmp *= period;
   if (cycle_tmp <= 0)
@@ -203,8 +203,8 @@
 }
   cycle_coef = sens * 256 * (itofix (GLOBAL_TICKER % cycle_tmp) / cycle_tmp);
 
-  f0 = fsin (cycle_coef + freq_coef * period2);
-  fp0x0 = (PI_1024 * fcos (cycle_coef + freq_coef * period2)) / 1024;
+  f0 = fixsin (cycle_coef + freq_coef * period2);
+  fp0x0 = (PI_1024 * fixcos (cycle_coef + freq_coef * period2)) / 1024;
 
   alphax03 = (ampli_cst / 256) * ((fp0x0 - 2 * f0) / 256);
   betax02 = (ampli_cst / 256) * ((-fp0x0 + 3 * f0) / 256);
@@ -217,7 +217,7 @@
 }
   for (i = period2; i < real_length - period2; ++i)
 {
-  temp = ((ampli_cos) / 256) * (fcos (cycle_coef + freq_coef * i) / 256);
+  temp = ((ampli_cos) / 256) * (fixcos (cycle_coef + freq_coef * i) / 256);
   buffer2[i] = temp / WAVE_SIZE_SCALE;
 }
 
--- a/src/fighter.c
+++ b/src/fighter.c
@@ -335,7 +335,7 @@
   coef += 256;
 
   attack[i] = (coef *
-		   fsqrt (fsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
+		   fixsqrt (fixsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
    + cpu_influence[i] / (256 * 8);
   if (attack[i] >= MAX_FIGHTER_HEALTH)
 	attack[i] = MAX_FIGHTER_HEALTH - 1;
@@ -343,7 +343,7 @@
 	attack[i] = 1;
 
   defense[i] = (coef *
-		fsqrt (fsqrt
+		fixsqrt (fixsqrt
 			   (1 <<
 			(LW_CONFIG_CURRENT_RULES.fighter_defense +
 			 cpu_influence[i] / (256 * 256);
@@ -353,7 +353,7 @@
 	defense[i] = 1;
 
   new_health[i] = (coef *
-		   fsqrt (fsqrt
+		   fixsqrt (fixsqrt
 			  (1 <<
 			   (LW_CONFIG_CURRENT_RULES.fighter_new_health +
 cpu_influence[i] / (256 * 4);
--- a/src/palette.c
+++ b/src/palette.c
@@ -88,7 +88,7 @@
 {
   int result;
 
-  result = fsqrt (i * 256) / 256;
+  result = fixsqrt (i * 256) / 256;
   if (result > 255)
 result = 255;
 

Bug#899739: marked as done (xfce4-messenger-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 14:48:20 +
with message-id 
and subject line Bug#899739: fixed in xfce4-messenger-plugin 0.1.0-7
has caused the Debian Bug report #899739,
regarding xfce4-messenger-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-messenger-plugin
Version: 0.1.0-6
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-messenger-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-messenger-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-messenger-plugin
Source-Version: 0.1.0-7

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated 
xfce4-messenger-plugin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 15:12:50 +0100
Source: xfce4-messenger-plugin
Binary: xfce4-messenger-plugin
Architecture: source
Version: 0.1.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-messenger-plugin - Dbus messages plugin for xfce4-panel
Closes: 899739
Changes:
 xfce4-messenger-plugin (0.1.0-7) unstable; urgency=medium
 .
   [ Yves-Alexis Perez ]
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899739
   * d/gbp.conf added, following DEP-14
   * run wrap-and-sort
   * use HTTPS protocol in addresses
   * d/control: drop Lionel from Uploaders, thanks!
   * d/control: update standards version to 4.2.1
   * d/control: slightly update long description
   * New upstream version 0.1.0
   * update dh compat to 10
Checksums-Sha1:
 6aab1fb626a6175edcf9d3748b944dd5153cb956 1823 
xfce4-messenger-plugin_0.1.0-7.dsc
 adeb68a7a4c22642b9a310174bcdfd810f83a872 2896 
xfce4-messenger-plugin_0.1.0-7.debian.tar.xz
 

Bug#907159: marked as done (mudlet: FTBFS in buster/sid (invalid use of incomplete type 'class QTabBar'))

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 14:46:52 +
with message-id 
and subject line Bug#907159: fixed in mudlet 1:3.7.1-1.1
has caused the Debian Bug report #907159,
regarding mudlet: FTBFS in buster/sid (invalid use of incomplete type 'class 
QTabBar')
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch 
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cd src && qmake \
DATAROOTDIR=/usr/share/games
Info: creating stash file /<>/src/.qmake.stash
Project MESSAGE: mudlet will be installed to /usr/local/bin...
Project MESSAGE: Lua files will be installed to /usr/share/games/mudlet/lua...
Project MESSAGE: Geyser lua files will be installed to 
/usr/share/games/mudlet/lua/geyser...
Project MESSAGE: Lua Code Formatter lua files will be installed to 
/usr/share/games/mudlet/lua/lcf...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes

[... snipped ...]

In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmainwindow.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMainWindow:1,
 from ui_main_window.h:16,
 from mudlet.h:31,
 from TCommandLine.cpp:29:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtabwidget.h:51:7: note: forward 
declaration of 'class QTabBar'
 class QTabBar;
   ^~~
TCommandLine.cpp:154:53: error: invalid use of incomplete type 'class QTabBar'
 int count = mudlet::self()->mpTabBar->count();
 ^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmainwindow.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMainWindow:1,
 from ui_main_window.h:16,
 from mudlet.h:31,
 from TCommandLine.cpp:29:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtabwidget.h:51:7: note: forward 
declaration of 'class QTabBar'
 class QTabBar;
   ^~~
TCommandLine.cpp:156:45: error: invalid use of incomplete type 'class QTabBar'
 mudlet::self()->mpTabBar->setCurrentIndex(currentIndex + 
1);
 ^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmainwindow.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMainWindow:1,
 from ui_main_window.h:16,
 from mudlet.h:31,
 from TCommandLine.cpp:29:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtabwidget.h:51:7: note: forward 
declaration of 'class QTabBar'
 class QTabBar;
   ^~~
TCommandLine.cpp:158:45: error: invalid use of incomplete type 'class QTabBar'
 mudlet::self()->mpTabBar->setCurrentIndex(0);
 ^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmainwindow.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMainWindow:1,
 from ui_main_window.h:16,
 from mudlet.h:31,
 from TCommandLine.cpp:29:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtabwidget.h:51:7: note: forward 
declaration of 'class QTabBar'
 class QTabBar;
   ^~~
make[2]: *** [Makefile:5421: TCommandLine.o] Error 1
make[2]: Leaving directory '/<>/src'
make[1]: *** [debian/rules:37: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:19: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mudlet.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: mudlet

Bug#916003: marked as done (nfswatch FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 14:46:58 +
with message-id 
and subject line Bug#916003: fixed in nfswatch 4.99.11-5
has caused the Debian Bug report #916003,
regarding nfswatch FTBFS with glibc 2.28
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.)


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

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

...
util.c: In function 'setup_nfs_counters':
util.c:557:27: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
nc->nc_dev.Major = major(st.st_dev);
   ^
util.c:558:27: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
nc->nc_dev.Minor = minor(st.st_dev);
   ^
   mknod
...
cc -o nfswatch dlpi.o logfile.o netaddr.o nfswatch.o nit.o pfilt.o pktfilter.o 
rpcfilter.o rpcutil.o screen.o snoop.o util.o xdr.o parsenfsfh.o linux.o -lpcap 
-lncurses -lm
/usr/bin/ld: util.o: in function `setup_nfs_counters':
util.c:(.text+0x6d9): undefined reference to `major'
/usr/bin/ld: util.c:(.text+0x6f6): undefined reference to `minor'
/usr/bin/ld: util.c:(.text+0x910): undefined reference to `major'
/usr/bin/ld: util.c:(.text+0x928): undefined reference to `minor'
/usr/bin/ld: util.o: in function `setup_fil_counters':
util.c:(.text+0xa5c): undefined reference to `major'
/usr/bin/ld: util.c:(.text+0xa74): undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:165: nfswatch] Error 1
--- End Message ---
--- Begin Message ---
Source: nfswatch
Source-Version: 4.99.11-5

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated nfswatch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 14:40:06 +0100
Source: nfswatch
Binary: nfswatch
Architecture: source
Version: 4.99.11-5
Distribution: unstable
Urgency: medium
Maintainer: Salvatore Bonaccorso 
Changed-By: Salvatore Bonaccorso 
Closes: 916003
Description: 
 nfswatch   - Program to monitor NFS traffic for the console
Changes:
 nfswatch (4.99.11-5) unstable; urgency=medium
 .
   * debian/changelog: Remove trailing whitespaces
 bp-Dch: Ignore
   * Add an initial Gitlab CI config file
   * debian/.gitlab-ci.yml: Update image used for Gitlab CI
   * Update .gitlab-ci.yml based on Salsa CI Team's template
   * GitLab CI/Lintian: install dpkg-dev, that ships dpkg-architecture, needed
 to run some Lintian checks
   * Fix build failure ('major'/'minor' undefined) in glibc 2.28.
 Thanks to Adrian Bunk  (Closes: #916003)
   * Declare compliance with Debian policy 4.2.1
Checksums-Sha1: 
 a982805583ced678b03e449b5691c392a76cb03f 2020 nfswatch_4.99.11-5.dsc
 e2cf31c3fccb0a5c5742f9213911735dc68984c6 5260 nfswatch_4.99.11-5.debian.tar.xz
Checksums-Sha256: 
 d42890808d42189ab16796b781b6c95b1095c8d33d38c613470ecce582752caf 2020 
nfswatch_4.99.11-5.dsc
 1e014b638245ab5734f5f0b72195b24eaa656c221d1668eeba68901eea92934c 5260 
nfswatch_4.99.11-5.debian.tar.xz
Files: 
 432107f42276b165acb66ee44629408f 2020 admin optional nfswatch_4.99.11-5.dsc
 8db09719427399d4001633fedc5c2b54 5260 admin optional 
nfswatch_4.99.11-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlwNHUVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E4tYP/iSVO5NtMWt1BnItFU+pg54RtfM4JzmT
ak2xskUiC9SjzRqJ09S9/hUWBl/AkgkguGNdSS2bfNF2+c2C0J8U6KaAEK6n+a+X
mtVygZA541/EbSnH+tg9xbImCnja2HNW6scPvUxFfDbJfB+YOhF+q2bOiRW5YZbG
iU25riSiNKCXgYiak9tQ6H1CguRJiHS+5a93d9n1dc2lsBdnV5L4HCTLUwfW0Gjq

Bug#899732: marked as done (xfce4-cpugraph-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 14:48:13 +
with message-id 
and subject line Bug#899732: fixed in xfce4-cpugraph-plugin 1.0.5-2
has caused the Debian Bug report #899732,
regarding xfce4-cpugraph-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-cpugraph-plugin
Version: 1.0.5-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-cpugraph-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-cpugraph-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-cpugraph-plugin
Source-Version: 1.0.5-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated 
xfce4-cpugraph-plugin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Dec 2018 14:54:47 +0100
Source: xfce4-cpugraph-plugin
Binary: xfce4-cpugraph-plugin
Architecture: source
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-cpugraph-plugin - CPU load graph plugin for the Xfce4 panel
Closes: 899732
Changes:
 xfce4-cpugraph-plugin (1.0.5-2) unstable; urgency=medium
 .
   [ Yves-Alexis Perez ]
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899732
   * d/gbp.conf added, following DEP-14
   * run wrap-and-sort
   * d/watch: use HTTPS protocol
   * New upstream version 1.0.5
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.2.1
   * d/control: use HTTPS protocol for Homepage
   * d/control: slightly update long description
   * update dh compat to 10
Checksums-Sha1:
 695bd4cdae2aa0bb13b3a54f4f439a7a1bea8217 1770 xfce4-cpugraph-plugin_1.0.5-2.dsc
 0191c73634c1ebd0a9a01801a6ba2c1db497659a 3388 

Bug#915577: marked as done (elpa-haskell-mode: missing Breaks+Replaces: haskell-mode (<< 16.1-4))

[Debian Bug Tracking System]

Your message dated Sun, 09 Dec 2018 14:46:06 +
with message-id 
and subject line Bug#915577: fixed in haskell-mode 16.1-5
has caused the Debian Bug report #915577,
regarding elpa-haskell-mode: missing Breaks+Replaces: haskell-mode (<< 16.1-4)
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.)


-- 
915577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-haskell-mode
Version: 16.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../elpa-haskell-mode_16.1-4_all.deb ...
  Unpacking elpa-haskell-mode (16.1-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/elpa-haskell-mode_16.1-4_all.deb (--unpack):
   trying to overwrite '/usr/share/icons/locolor/scalable/logo.svg', which is 
also in package haskell-mode 16.1-3
  Errors were encountered while processing:
   /var/cache/apt/archives/elpa-haskell-mode_16.1-4_all.deb


cheers,

Andreas


haskell-mode=16.1-3_elpa-haskell-mode=16.1-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: haskell-mode
Source-Version: 16.1-5

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

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

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

Debian distribution maintenance software
pp.
Thomas Koch  (supplier of updated haskell-mode 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: Sun, 09 Dec 2018 13:07:09 +
Source: haskell-mode
Binary: elpa-haskell-mode haskell-mode
Architecture: source all
Version: 16.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Thomas Koch 
Description:
 elpa-haskell-mode - major mode for editing Haskell in Emacs
 haskell-mode - transitional package
Closes: 915577
Changes:
 haskell-mode (16.1-5) unstable; urgency=medium
 .
   * correct versions for breaks/replaces in d/control (closes: 915577)
Checksums-Sha1:
 c524ed94b6078473ee5df54487e42eefed398827 2163 haskell-mode_16.1-5.dsc
 5a47b72f23c5fde2e56c33afca017944d52fc300 6272 haskell-mode_16.1-5.debian.tar.xz
 4f1b0aad96f1ff0e0dc8282cdcca1f9cfb2fc294 180700 
elpa-haskell-mode_16.1-5_all.deb
 302cc029960ddae1fad522d41296972749f65576 5828 haskell-mode_16.1-5_all.deb
 f4ec49a79c99835b65c0f45a70dbc0dd02c97ee0 8117 
haskell-mode_16.1-5_amd64.buildinfo
Checksums-Sha256:
 0dacf58332391a43537402bc58dd0acca37da5f8debd32a6a9cd9a4a9d1cf672 2163 
haskell-mode_16.1-5.dsc
 79017de47a220599f125e701feabbac626d2eb4aa441b955f1ec83c649a258aa 6272 
haskell-mode_16.1-5.debian.tar.xz
 3868247f87b134e5194a8b3d20b5f73a5240454b3d3f0e34663ab437aa89dc5f 180700 
elpa-haskell-mode_16.1-5_all.deb
 8199d77db8bad5588acdba81bc10ee28da65647101a77bc1acc341a2ca0f8ee4 5828 
haskell-mode_16.1-5_all.deb
 cedae37275b2802c0ac6db0e8dc856c770eaafd8b72c347905fcee27dbd80465 8117 
haskell-mode_16.1-5_amd64.buildinfo
Files:
 31fd2c7db6fe5eaf0a8022e8fdfa8b4e 2163 lisp optional haskell-mode_16.1-5.dsc
 bc26c017781508d860d382e6fad8691c 6272 lisp optional 
haskell-mode_16.1-5.debian.tar.xz
 e673bd798de7bc678a7c27138f3e9f9f 180700 lisp optional 
elpa-haskell-mode_16.1-5_all.deb
 4c216791e8a68b0c5504a9c7932d433c 5828 oldlibs optional 
haskell-mode_16.1-5_all.deb
 d598685aaf500eaa7e98ae6489f9f6ff 8117 lisp optional 
haskell-mode_16.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdgQCBVl/ppbxMTvKB/xIkQQrploFAlwNHzAACgkQB/xIkQQr
plpotg/9HI0iE7UT3UI3cJDxfsj+KctK+/Pk5mThiNkOI9YDV8eRwLj22ylLW9v7
WNh0Ratdwr0udOTEn52bTiLyOAfNb6TxaQpA+erlD9ie+uXnF7NxHsKnYsZUyWQt
/T6evcVBdWAawn6hsY6C9N5flFjHBB1jbCD8Wup9Hy1klWa2oJlMb4igYGTg3MjI

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Andreas Metzler]

On 2018-12-09 Adrian Bunk  wrote:
> Source: wmhdplop
> Version: 0.9.10-1
[...]

> devnames.c: In function 'device_id_from_name':
> devnames.c:207:13: warning: implicit declaration of function 'major' 
> [-Wimplicit-function-declaration]
>*pmajor = major(stat_buf.st_rdev);
>  ^
[...]

Seems to miss a 
#include 

cu Andreas

Processed: found 913346 in 1.0.27-3

[Debian Bug Tracking System]

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

> # version information lost in reassign
> found 913346 1.0.27-3
Bug #913346 [sane-backends] libsane1: Cannot update libsane1
There is no source info for the package 'sane-backends' at version '1.0.27-3' 
with architecture ''
Unable to make a source version for version '1.0.27-3'
Marked as found in versions 1.0.27-3.
> thanks
Stopping processing here.

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

Bug#916033: alex4 FTBFS with allegro4.4 2:4.4.2-13

[Andreas Ronnquist]

This patch fixes this problem for alex4. (I am the cause of the problem,
and I'll post patches to the other allegro4.4-related failures too).

-- Andreas Rönnquist
gus...@debian.org
--- a/src/shooter.c
+++ b/src/shooter.c
@@ -500,12 +500,12 @@
 			break;
 		case SM_SIN_WAVE:
 			o->x += o->vx;
-			o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
+			o->y = o->d2 + fixtoi(fixmul(ftofix(o->vy), fixsin(itofix(o->t;
 			o->t += o->d1;
 			break;
 		case SM_COS_WAVE:
 			o->x += o->vx;
-			o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fcos(itofix(o->t;
+			o->y = o->d2 + fixtoi(fixmul(ftofix(o->vy), fixcos(itofix(o->t;
 			o->t += o->d1;
 			break;
 		case SM_BOSS_1:
@@ -516,8 +516,8 @@
 o->tx = o->x;
 			}
 			else {
-o->y = o->ty + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
-o->x = o->tx - fixtoi(10 * fsin(itofix(o->t >> 1)));
+o->y = o->ty + fixtoi(fixmul(ftofix(o->vy), fixsin(itofix(o->t;
+o->x = o->tx - fixtoi(10 * fixsin(itofix(o->t >> 1)));
 o->t ++;
 			}
 			break;
@@ -573,7 +573,7 @@
 		else if (o->image == ENEMY15) {
 			int i;
 			for(i = 0; i < 256; i += 32)
-s_make_enemy_bullet((int)o->x + o->bw / 2, (int)o->y + o->bh, fixtof(1 * fcos(itofix(i - 6))), fixtof(1 * fsin(itofix(i - 6;
+s_make_enemy_bullet((int)o->x + o->bw / 2, (int)o->y + o->bh, fixtof(1 * fixcos(itofix(i - 6))), fixtof(1 * fixsin(itofix(i - 6;
 			o->fire_counter = 200 + rand()%50;
 		}
 	
--- a/src/main.c
+++ b/src/main.c
@@ -1212,9 +1212,9 @@
 
 	blit(data[INTRO_BG].dat, bmp, 0, 0, 0, 0, 160, 120);
 
-	r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * fsin(itofix((int)(game_count / 2.7))) );
+	r = 70 + fixtoi(20 * fixcos(itofix(game_count >> 1)) + 20 * fixsin(itofix((int)(game_count / 2.7))) );
 	for(i = 0; i < 256; i += 32) 
-		draw_sprite(bmp, head, 80 - head->w/2 + fixtoi(r * fcos(itofix(game_count + i))), 60 - head->h/2 + fixtoi(r * fsin(itofix(game_count + i;
+		draw_sprite(bmp, head, 80 - head->w/2 + fixtoi(r * fixcos(itofix(game_count + i))), 60 - head->h/2 + fixtoi(r * fixsin(itofix(game_count + i;
 
 	draw_sprite_h_flip(bmp, data[ALEX].dat, 60, 40);
 	draw_sprite(bmp, data[LOLA].dat, 84, 40);
@@ -2545,7 +2545,7 @@
 	textout_ex(bmp, data[THE_FONT].dat, "QUIT", x+1, y+1, 1, -1);
 	textout_ex(bmp, data[THE_FONT].dat, "QUIT", x, y, 4, -1);
 
-	draw_sprite(bmp, data[POINTER].dat, x - 25 + fixtoi(3 * fcos(itofix(tick << 2))), 44 + menu_choice * step);
+	draw_sprite(bmp, data[POINTER].dat, x - 25 + fixtoi(3 * fixcos(itofix(tick << 2))), 44 + menu_choice * step);
 }
 
 

Bug#907159: mudlet: FTBFS in buster/sid (invalid use of incomplete type 'class QTabBar')

[Markus Koschany]

Control: tags -1 patch pending

Dear maintainer,

I've uploaded a new revision of mudlet versioned as 1:3.7.1-1.1.

To fix this issue I had to patch src/TCommandLine.cpp and add the
missing include for QTabBar. I also had to export CCACHE_DIR because
otherwise the build would fail on my system (pbuilder setup). Please
find attached the debdiff.

Regards,

Markus
diff -Nru mudlet-3.7.1/debian/changelog mudlet-3.7.1/debian/changelog
--- mudlet-3.7.1/debian/changelog   2017-12-24 07:49:23.0 +0100
+++ mudlet-3.7.1/debian/changelog   2018-12-09 15:12:05.0 +0100
@@ -1,3 +1,13 @@
+mudlet (1:3.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Export CCACHE_DIR in debian/rules to prevent a FTBFS because of
+a non-writable cache directory.
+  * QTabBar-include.patch: Fix FTBFS by adding the missing include for QTabBar.
+(Closes: #907159)
+
+ -- Markus Koschany   Sun, 09 Dec 2018 15:12:05 +0100
+
 mudlet (1:3.7.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru mudlet-3.7.1/debian/patches/QTabBar-include.patch 
mudlet-3.7.1/debian/patches/QTabBar-include.patch
--- mudlet-3.7.1/debian/patches/QTabBar-include.patch   1970-01-01 
01:00:00.0 +0100
+++ mudlet-3.7.1/debian/patches/QTabBar-include.patch   2018-12-09 
15:12:05.0 +0100
@@ -0,0 +1,22 @@
+From: Markus Koschany 
+Date: Sun, 9 Dec 2018 15:11:33 +0100
+Subject: QTabBar include
+
+Bug-Debian: https://bugs.debian.org/907159
+Forwarded: no
+---
+ src/TCommandLine.cpp | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/TCommandLine.cpp b/src/TCommandLine.cpp
+index 416e9ad..3a69da2 100644
+--- a/src/TCommandLine.cpp
 b/src/TCommandLine.cpp
+@@ -34,6 +34,7 @@
+ #include 
+ #include 
+ #include "post_guard.h"
++#include 
+ 
+ 
+ TCommandLine::TCommandLine(Host* pHost, TConsole* pConsole, QWidget* parent)
diff -Nru mudlet-3.7.1/debian/patches/series mudlet-3.7.1/debian/patches/series
--- mudlet-3.7.1/debian/patches/series  2017-12-24 07:49:23.0 +0100
+++ mudlet-3.7.1/debian/patches/series  2018-12-09 15:11:55.0 +0100
@@ -1,3 +1,4 @@
 project_file
 qrc_removedups
 freebsd_ifdef
+QTabBar-include.patch
diff -Nru mudlet-3.7.1/debian/rules mudlet-3.7.1/debian/rules
--- mudlet-3.7.1/debian/rules   2017-12-24 07:49:23.0 +0100
+++ mudlet-3.7.1/debian/rules   2018-12-09 15:01:48.0 +0100
@@ -9,6 +9,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 export QT_SELECT=5
+export CCACHE_DIR := $(CURDIR)/debian/ccache
 
 PACKAGE=mudlet
 SRC_VERSION:=$(shell dpkg-parsechangelog | sed -ne 's/^Version: 
\(\([0-9]\+\):\)\?\(.*\)-.*/\3/p')


signature.asc
Description: OpenPGP digital signature

Processed: Re: mudlet: FTBFS in buster/sid (invalid use of incomplete type 'class QTabBar')

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #907159 [src:mudlet] mudlet: FTBFS in buster/sid (invalid use of incomplete 
type 'class QTabBar')
Added tag(s) patch and pending.

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

Bug#916026: bootchart2 FTBFS with glibc 2.28

[Riccardo Magliocchetti]

Il 09/12/18 14:10, Adrian Bunk ha scritto:

Source: bootchart2
Version: 0.14.4-3
Severity: serious
Tags: ftbfs buster sid

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

...
collector/collector.c: In function 'enter_environment':
collector/collector.c:633:47: warning: implicit declaration of function 
'makedev' [-Wimplicit-function-declaration]
   if (mknod (TMPFS_PATH "/kmsg", S_IFCHR|0666, makedev(1, 11)) < 0) {
^~~
...
cc -g -Wall -O0  -pthread -Icollector -o bootchart-collector 
collector/collector.o collector/output.o collector/tasks.o 
collector/tasks-netlink.o collector/dump.o
/usr/bin/ld: collector/collector.o: in function `enter_environment':
/build/1st/bootchart2-0.14.4/collector/collector.c:633: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:39: bootchart-collector] Error 1



This has already been fixed upstream here:

commit add58c3b57064afd6f7d2fd5f09006d28a3e770e
Author: Mike Frysinger 
Date:   Thu Apr 21 00:19:32 2016 -0400

include sys/sysmacros.h for major/minor/makedev

These funcs are defined in the sys/sysmacros.h header, not sys/types.h.
Linux C libraries are updating to drop the implicit include, so we need
to include it explicitly.

diff --git a/collector/collector.c b/collector/collector.c
index cfdcb26..2f3ce6b 100644
--- a/collector/collector.c
+++ b/collector/collector.c
@@ -33,6 +33,7 @@
 #include "common.h"

 #include 
+#include 
 #include 
 #include 
 #include 


--
Riccardo Magliocchetti
@rmistaken

http://menodizero.it

Bug#916037: liquidwar FTBFS with allegro4.4 2:4.4.2-13

[Adrian Bunk]

Source: liquidwar
Version: 5.6.4-5
Severity: serious
Tags: ftbfs buster sid

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

...
distor.c: In function 'create_wave_line':
distor.c:197:15: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
   cycle_tmp = fsqrt (fsqrt (cycle_tmp)) / 2;
   ^
   fixsqrt
distor.c:206:8: warning: implicit declaration of function 'fsin'; did you mean 
'fixsin'? [-Wimplicit-function-declaration]
   f0 = fsin (cycle_coef + freq_coef * period2);
^~~~
fixsin
distor.c:207:22: warning: implicit declaration of function 'fcos'; did you mean 
'fixcos'? [-Wimplicit-function-declaration]
   fp0x0 = (PI_1024 * fcos (cycle_coef + freq_coef * period2)) / 1024;
  ^~~~
...
fighter.c: In function 'move_fighters':
fighter.c:338:6: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
  fsqrt (fsqrt (1 << (LW_CONFIG_CURRENT_RULES.fighter_attack
  ^
...
palette.c: In function 'sqrt255':
palette.c:91:12: warning: implicit declaration of function 'fsqrt'; did you 
mean 'fixsqrt'? [-Wimplicit-function-declaration]
   result = fsqrt (i * 256) / 256;
^
...
Linking liquidwar (target=default, debug=no, static=no, asm=no)
/usr/bin/ld: random.o: in function `lw_random_generate_map':
random.c:(.text+0x34): warning: the use of `tmpnam' is dangerous, better use 
`mkstemp'
/usr/bin/ld: distor.o: in function `create_wave_line.constprop.0':
distor.c:(.text+0xc6): undefined reference to `fsqrt'
/usr/bin/ld: distor.c:(.text+0xcf): undefined reference to `fsqrt'
/usr/bin/ld: distor.c:(.text+0x130): undefined reference to `fsin'
/usr/bin/ld: distor.c:(.text+0x13e): undefined reference to `fcos'
/usr/bin/ld: distor.c:(.text+0x24e): undefined reference to `fcos'
/usr/bin/ld: fighter.o: in function `move_fighters':
fighter.c:(.text+0x46d): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x476): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x4a5): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x4ae): undefined reference to `fsqrt'
/usr/bin/ld: fighter.c:(.text+0x554): undefined reference to `fsqrt'
/usr/bin/ld: fighter.o:fighter.c:(.text+0x55d): more undefined references to 
`fsqrt' follow
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:245: liquidwar] Error 1

Processed: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.9.11~20110321-12
Bug #916034 [sl-modem-dkms] sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 
4.9.0-8-amd64
Marked as found in versions sl-modem/2.9.11~20110321-12.

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

Bug#916033: alex4 FTBFS with allegro4.4 2:4.4.2-13

[Adrian Bunk]

Source: alex4
Version: 1.1-7
Severity: serious
Tags: ftbfs buster sid

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

...
shooter.c: In function 's_update_object':
shooter.c:503:26: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
  ^~~~
  fixmul
shooter.c:503:46: warning: implicit declaration of function 'fsin'; did you 
mean 'fixsin'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fsin(itofix(o->t;
  ^~~~
  fixsin
shooter.c:508:46: warning: implicit declaration of function 'fcos'; did you 
mean 'feof'? [-Wimplicit-function-declaration]
o->y = o->d2 + fixtoi(fmul(ftofix(o->vy), fcos(itofix(o->t;
  ^~~~
  feof
main.c: In function 'draw_custom_ending':
main.c:1215:23: warning: implicit declaration of function 'fcos'; did you mean 
'feof'? [-Wimplicit-function-declaration]
  r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * 
fsin(itofix((int)(game_count / 2.7))) );
   ^~~~
   feof
main.c:1215:60: warning: implicit declaration of function 'fsin'; did you mean 
'fixsin'? [-Wimplicit-function-declaration]
  r = 70 + fixtoi(20 * fcos(itofix(game_count >> 1)) + 20 * 
fsin(itofix((int)(game_count / 2.7))) );
^~~~
fixsin
...
cc -Wl,-z,relro -Wl,-z,now -o alex4 actor.o edit.o map.o player.o shooter.o 
unix.o bullet.o hisc.o options.o script.o timer.o control.o main.o particle.o 
scroller.o token.o -laldmb -ldumb `allegro-config --libs`
/usr/bin/ld: shooter.o: undefined reference to symbol 'fmul@@GLIBC_2.28'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:12: alex4] Error 1

Bug#905254: Status of libphp-phpmailer

[Chris Lamb]

Chris Lamb wrote:

> >   However, the git does not seem to have been moved to salsa.
> 
> I fixed a number of CVEs recently and I would love to push my changes
> to suitable branches. Can the PEAR maintainers please migrate this
> repo ASAP?

Gentle ping on this folks? :)



Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb  Debian Project Leader (2017—)
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#915954: inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)

[Benoît Sibaud]

Hi,

same issue here. Deterministic (always fails at boot with -3, and works with 
-2).

below, kernel log of 4.18.0-2 and 4.18.0-3 (with something wrong in 
i915_request_alloc)

kernel log of 4.18.0-2 (the WORKING one) follows:

[0.00] Linux version 4.18.0-2-amd64 (debian-ker...@lists.debian.org) 
(gcc version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.10-2 (2018-11-02)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-2-amd64 
root=/dev/mapper/anthra-root ro
[0.00] Disabled fast string operations
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xaf78] usable
[0.00] BIOS-e820: [mem 0xaf79-0xaf79dfff] ACPI data
[0.00] BIOS-e820: [mem 0xaf79e000-0xaf7d] ACPI NVS
[0.00] BIOS-e820: [mem 0xaf7e-0xaf7f] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xffb0-0x] reserved
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] DMI: System manufacturer System Product Name/P5B-VM, BIOS 0901   
 07/03/2007
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0xaf790 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-D uncachable
[0.00]   E-E write-through
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0BC00 mask FFC00 uncachable
[0.00]   1 base 0C000 mask FC000 uncachable
[0.00]   2 base 0 mask F write-back
[0.00]   3 base 1 mask F8000 write-back
[0.00]   4 base 0AF80 mask FFF80 uncachable
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] e820: update [mem 0xaf80-0xafff] usable ==> reserved
[0.00] e820: update [mem 0xbc00-0x] usable ==> reserved
[0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at 
[(ptrval)]
[0.00] Base memory trampoline at [(ptrval)] 99000 size 24576
[0.00] BRK [0x5344b000, 0x5344bfff] PGTABLE
[0.00] BRK [0x5344c000, 0x5344cfff] PGTABLE
[0.00] BRK [0x5344d000, 0x5344dfff] PGTABLE
[0.00] BRK [0x5344e000, 0x5344efff] PGTABLE
[0.00] BRK [0x5344f000, 0x5344] PGTABLE
[0.00] BRK [0x5345, 0x53450fff] PGTABLE
[0.00] RAMDISK: [mem 0x34e27000-0x3670afff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000FA950 24 (v02 ACPIAM)
[0.00] ACPI: XSDT 0xAF790100 54 (v01 MSTEST OEMXSDT  
07000703 MSFT 0097)
[0.00] ACPI: FACP 0xAF790290 F4 (v03 MSTEST OEMFACP  
07000703 MSFT 0097)
[0.00] ACPI: DSDT 0xAF7905C0 007C09 (v01 A0518  A0518000 
 INTL 20060113)
[0.00] ACPI: FACS 0xAF79E000 40
[0.00] ACPI: FACS 0xAF79E000 40
[0.00] ACPI: APIC 0xAF790390 6C (v01 MSTEST OEMAPIC  
07000703 MSFT 0097)
[0.00] ACPI: MCFG 0xAF790400 3C (v01 MSTEST OEMMCFG  
07000703 MSFT 0097)
[0.00] ACPI: OEMB 0xAF79E040 7B (v01 MSTEST AMI_OEM  
07000703 MSFT 0097)
[0.00] ACPI: HPET 0xAF7981D0 38 (v01 MSTEST OEMHPET  
07000703 MSFT 0097)
[0.00] ACPI: GSCI 0xAF79E0C0 002024 (v01 MSTEST GMCHSCI  
07000703 MSFT 0097)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0xaf78]
[0.00] NODE_DATA(0) allocated [mem 0xaf78b000-0xaf78]
[0.00] tsc: Fast TSC calibration using PIT
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   DMA32[mem 0x0100-0xaf78]
[0.00]   Normal   empty
[0.00]   Device   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0xaf78]
[0.00] Reserved but unavailable: 2258 pages
[0.00] 

Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64

[Andreas Beckmann]

Package: sl-modem-dkms
Version: 2.9.11~20110321-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.9.11~20110321-12

Hi,

sl-modem-dkms fails to build a module for 4.18.0-3-amd64 and 4.9.0-8-amd64

Selecting previously unselected package sl-modem-dkms.
(Reading database ... 33401 files and directories currently installed.)
Preparing to unpack .../sl-modem-dkms_2.9.11~20110321-13_amd64.deb ...
Unpacking sl-modem-dkms (2.9.11~20110321-13) ...
Setting up sl-modem-dkms (2.9.11~20110321-13) ...
Loading new sl-modem-2.9.11~20110321 DKMS files...
grep: /lib/modules/4.9.0-6-amd64/build/.config: No such file or directory
It is likely that 4.9.0-6-amd64 belongs to a chroot's host
Building for 4.18.0-3-amd64
Building initial module for 4.18.0-3-amd64
Error!  Build of slusb.ko failed for: 4.18.0-3-amd64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ for more information.
dpkg: error processing package sl-modem-dkms (--configure):
 installed sl-modem-dkms package post-installation script subprocess returned 
error exit status 7
Errors were encountered while processing:
 sl-modem-dkms

# cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log 
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.18.0-3-amd64 (x86_64)
Sun Dec  9 13:53:21 UTC 2018
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
doing %.o: %.c
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB 
`test -f /lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h && echo 
-DMODVERSIONS --include 
/lib/modules/4.18.0-3-amd64/build/include/linux/modversions.h 
-I/lib/modules/4.18.0-3-amd64/build/include`  -I. -I./../modem   -o 
old_st7554.o -c old_st7554.c
old_st7554.c:49:10: fatal error: linux/init.h: No such file or directory
 #include 
  ^~
compilation terminated.
make: *** [Makefile:129: old_st7554.o] Error 1
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/4.18.0-3-amd64/build 
SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-4.18.0-3-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o
  LD [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.18.0-3-amd64'
make: Leaving directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'

# cat /var/lib/dkms/sl-modem/2.9.11~20110321/build/make.log 
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 4.9.0-8-amd64 (x86_64)
Sun Dec  9 14:02:25 UTC 2018
make: Entering directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
doing %.o: %.c
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB 
`test -f /lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h && echo 
-DMODVERSIONS --include 
/lib/modules/4.9.0-8-amd64/build/include/linux/modversions.h 
-I/lib/modules/4.9.0-8-amd64/build/include`  -I. -I./../modem   -o old_st7554.o 
-c old_st7554.c
old_st7554.c:48:26: fatal error: linux/module.h: No such file or directory
 #include 
  ^
compilation terminated.
Makefile:128: recipe for target 'old_st7554.o' failed
make: *** [old_st7554.o] Error 1
make: Leaving directory '/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers'
make: Entering directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'
make modules -C /lib/modules/4.9.0-8-amd64/build 
SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem
make[1]: Entering directory '/usr/src/linux-headers-4.9.0-8-amd64'
  CC [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.mod.o
  LD [M]  
/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.9.0-8-amd64'
make: Leaving directory 
'/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem'


Andreas

Bug#916035: kraptor FTBFS with allegro4.4 2:4.4.2-13

[Adrian Bunk]

Source: kraptor
Version: 0.0.20040403+ds-1
Severity: serious
Tags: ftbfs

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

...
src/explos.c: In function 'dibujar_explosion':
src/explos.c:129:20: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
   x2 -= fixtoi(fmul(itofix(tmp->spr->w), tmp->r))/2;
^~~~
...
src/enemigo.c: In function 'agregar_disparo_ene':
src/enemigo.c:498:24: warning: implicit declaration of function 'fmul'; did you 
mean 'fixmul'? [-Wimplicit-function-declaration]
nueva->dy = fmul(arma_ene[ene->arma_actual].vy, itofix(rand_ex(1, 
3)) );
^~~~
...
gcc obj/linux/azar.o obj/linux/bomba.o obj/linux/captura.o obj/linux/cinema.o 
obj/linux/clima.o obj/linux/combo.o obj/linux/config.o obj/linux/data.o 
obj/linux/datafind.o obj/linux/enemigo.o obj/linux/error.o obj/linux/explos.o 
obj/linux/filedata.o obj/linux/game.o obj/linux/global.o obj/linux/guiprocs.o 
obj/linux/guitrans.o obj/linux/humo.o obj/linux/ia.o obj/linux/joymnu.o 
obj/linux/jugador.o obj/linux/kfbuffer.o obj/linux/krstring.o obj/linux/main.o 
obj/linux/mapa.o obj/linux/menu.o obj/linux/partic.o obj/linux/pmask.o 
obj/linux/premio.o obj/linux/rvideo.o obj/linux/savedlg.o obj/linux/shopping.o 
obj/linux/sombras.o obj/linux/sonido.o obj/linux/wordwrap.o -o 
bin/kraptor_linux.bin -laldmb -ldumb `allegro-config --libs` `dpkg-buildflags 
--get LDFLAGS`
/usr/bin/ld: obj/linux/enemigo.o: undefined reference to symbol 
'fmul@@GLIBC_2.28'
/usr/bin/ld: //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status

Bug#916030: moria: FTBFS on mips64el

[Markus Koschany]

Package: moria
Version: 5.7.10+20181022-1
Severity: serious

Dear maintainer,

moria fails to build from source on mips64el. This prevents the
package migration to testing. According to the build log the error is
caused by

src/ui_io.cpp:521:31: error: cast from 'int*' to 'fd_set*' increases required 
alignment of target type [-Werror=cast-align]

Another way to work around this problem is to remove the -Werror flag
which is useful for development but causes FTBFS whenever GCC becomes
more strict.

Regards,

Markus