Bug#861840:

[Michael Mbaka]

[image: Inline image 1]

Bug#887686: brisk-menu: frequent parallel FTBFS

[Mike Gabriel]

HI,

On  Fr 19 Jan 2018 05:08:29 CET, Adrian Bunk wrote:


Source: brisk-menu
Version: 0.5.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=brisk-menu=sid

...
FAILED: src/frontend/brisk-frontend@sta/category-button.c.o
cc  -Isrc/frontend/brisk-frontend@sta -Isrc/frontend  
-I../src/frontend -Isrc/lib -I../src/lib -Isrc/backend  
-I../src/backend -Isrc -I../src -Isrc/session -I../src/session  
-I/usr/include/mate-menus -I/usr/include/glib-2.0  
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include  
-I/usr/include/gio-unix-2.0/ -I/usr/include/gtk-3.0  
-I/usr/include/harfbuzz -I/usr/include/pango-1.0  
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo  
-I/usr/include/pixman-1 -I/usr/include/freetype2  
-I/usr/include/libpng16 -I/usr/include/at-spi2-atk/2.0  
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0  
-I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include  
-I/usr/include/atk-1.0 -fdiagnostics-color=always -pipe  
-D_FILE_OFFSET_BITS=64 -std=c11 -fstack-protector -Wall -pedantic  
-Wstrict-prototypes -Wundef -fno-common  
-Werror-implicit-function-declaration -Wformat -Wformat-security  
-Werror=format-security -Wconversion -Wunused-variable  
-Wunreachable-code -W -DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_18  
-DGDK_VERSION_MI

 N_REQUIR
 ED=GDK_VERSION_3_18 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_44  
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_44 -g -O2  
-fdebug-prefix-map=/<>=. -fstack-protector-strong  
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  
-fPIC -pthread -MMD -MQ  
'src/frontend/brisk-frontend@sta/category-button.c.o' -MF  
'src/frontend/brisk-frontend@sta/category-button.c.o.d' -o  
'src/frontend/brisk-frontend@sta/category-button.c.o' -c  
../src/frontend/category-button.c

In file included from ../src/frontend/category-button.c:18:0:
../src/frontend/menu-private.h:18:10: fatal error: libsaver-glue.h:  
No such file or directory

 #include "libsaver-glue.h"
  ^
compilation terminated.


funnily, I saw this on attempts to backport to strech-backports, never  
seen this for unstable builds locally, so far.


Will take a look...

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpGGA_p9DFtN.pgp
Description: Digitale PGP-Signatur

Bug#887625: gmime-bin: Illegal seek

[Daniel Kahn Gillmor]

Control: tags 887625 + confirmed
Control: severity 887625 normal
Control: found 887625 3.0.0-1
Control: forwarded 887625 https://github.com/jstedfast/gmime/issues/43

On Thu 2018-01-18 15:37:41 +0100, Cristian Ionescu-Idbohrn wrote:
> Package: gmime-bin
> Version: 3.0.5-1
> Severity: grave
> Justification: renders package unusable
>
> $ strace -f gmime-uuencode file.jpg
> ...
> openat(AT_FDCWD, "/proc/filesystems", O_RDONLY|O_CLOEXEC) = 3
> fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tr"..., 1024) = 370
> read(3, "", 1024)   = 0
> close(3)= 0
> access("/etc/selinux/config", F_OK) = -1 ENOENT (No such file or 
> directory)
> futex(0x7fe06805ee28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
> futex(0x7fe06805ee28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
> dup(0)  = 3
> fstat(3, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
> fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
> write(1, "begin 600 file.jpg\n", 22begin 600 file.jpg
> ) = 22
> lseek(3, 0, SEEK_CUR)   = -1 ESPIPE (Illegal seek)
> lseek(3, 0, SEEK_SET)   = -1 ESPIPE (Illegal seek)
> openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/charset.alias", O_RDONLY) = -1 
> ENOENT (No such file or directory)
> open("/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache", O_RDONLY) = 4
> fstat(4, {st_mode=S_IFREG|0644, st_size=26258, ...}) = 0
> mmap(NULL, 26258, PROT_READ, MAP_SHARED, 4, 0) = 0x7fe068eeb000
> close(4)= 0
> futex(0x7fe0670889e8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
> write(2, "gmime-uuencode: Illegal seek\n", 29gmime-uuencode: Illegal seek
> ) = 29
> close(3)= 0
> exit_group(1)   = ?
> +++ exited with 1 +++

Hi Cristian!  I can confirm that this happens to me as well when i
invoke gmime-uuencode and leave its stdin coming from the terminal or
from a pipe.

however, i get no failures when reading from a file or a here-string.
e.g.:

$ echo test > test.txt
$ gmime-uuencode bananas.txt < test.txt
begin 644 bananas.txt
%=&5S=`H`
`
end
$ echo test | gmime-uuencode test.txt 
begin 600 test.txt
gmime-uuencode: Illegal seek
+++ exited (status 1) +++
$

Using ltrace, it looks like the failure is happening inside
g_mime_stream_write_to_stream().  interestingly, it doesn't seem to
happen in gmime 2.6 :/ -- but it looks like this goes as far back as
gmime 3.0.0-1 at least.

I've dropped the severity because the package is not unusable -- it's
only unusable if the input is coming from a pipe.

I've forwarded the issue upstream.

 --dkg


signature.asc
Description: PGP signature

Processed: Re: Bug#887625: gmime-bin: Illegal seek

[Debian Bug Tracking System]

Processing control commands:

> tags 887625 + confirmed
Bug #887625 [gmime-bin] gmime-bin: Illegal seek
Added tag(s) confirmed.
> severity 887625 normal
Bug #887625 [gmime-bin] gmime-bin: Illegal seek
Severity set to 'normal' from 'grave'
> found 887625 3.0.0-1
Bug #887625 [gmime-bin] gmime-bin: Illegal seek
Marked as found in versions gmime/3.0.0-1.
> forwarded 887625 https://github.com/jstedfast/gmime/issues/43
Bug #887625 [gmime-bin] gmime-bin: Illegal seek
Set Bug forwarded-to-address to 'https://github.com/jstedfast/gmime/issues/43'.

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

Bug#887696: likwid FTBFS with glibc 2.26

[Adrian Bunk]

Source: likwid
Version: 4.2.1+dfsg1-1
Severity: serious

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

...
In file included from ./hwloc/bind.c:11:0:
./include/private/private.h:249:10: fatal error: xlocale.h: No such file or 
directory
 #include "xlocale.h"
  ^~~
compilation terminated.
Makefile:52: recipe for target 'GCC/bind.o' failed
make[3]: *** [GCC/bind.o] Error 1

Bug#883502: marked as done (diffpdf: depends on libpoppler-qt4 which is about to be removed)

[Debian Bug Tracking System]

Your message dated Fri, 19 Jan 2018 16:24:26 +1100
with message-id <8474858.TIYKUArTYA@simurgh>
and subject line Re: Bug#883502: libpoppler-qt4 dependency removed
has caused the Debian Bug report #883502,
regarding diffpdf: depends on libpoppler-qt4 which is about to be removed
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.)


-- 
883502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diffpdf
Severity: serious
Tags: sid stretch
User: pkg-freedesktop-maintain...@lists.alioth.debian.org
Usertags: oldlibs poppler-qt4

Control: block 875096 with -1

Hi,

diffpdf (build-)depends on Poppler Qt4 bindings, which have been
removed upstream in Poppler 0.62.0. They will be gone from Debian
soon, once we update to that version.

diffpdf should switch to the Qt5 bindings, or disable Poppler support
if the former is not possible.

If you have any question don't hesitate to ask.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Version: 2.1.3-1.2

This bug was also closed by the NMU but I left the bug number out of the 
changelog ;(

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 18 Jan 2018 22:42:45 +1100
Source: diffpdf
Binary: diffpdf
Architecture: source
Version: 2.1.3-1.2
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 
Changed-By: Stuart Prescott 
Description:
 diffpdf- compare two PDF files textually or visually
Closes: 874854
Changes:
 diffpdf (2.1.3-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch build to Qt5 with thanks to Sune Vuorela for the patch
 (Closes: 874854).
Checksums-Sha1:
 4759b46440fde57f0d27d35e1c1af4b4c9e8bd2b 1938 diffpdf_2.1.3-1.2.dsc
 77ad36471cb0ee59708e4b7d12fd7321493c0b98 6760 diffpdf_2.1.3-1.2.debian.tar.xz
 e938c7916244f804c6d089d3f65f9df4b3e421da 10793 
diffpdf_2.1.3-1.2_source.buildinfo
Checksums-Sha256:
 4c3f5bd1208014fa644d2822d95a42ac52954567c8d76424a55f186da58993e5 1938 
diffpdf_2.1.3-1.2.dsc
 ccd26089aebe6a4a0e7c9db0a804d5d715e977a1d8920e6abfb9df8315d3068a 6760 
diffpdf_2.1.3-1.2.debian.tar.xz
 4d1701e6e2efff960b24c162ae06c009c6a79c55106393cbcde776a639a468fd 10793 
diffpdf_2.1.3-1.2_source.buildinfo
Files:
 3076c31e815e69daf3d541da59663a90 1938 utils optional diffpdf_2.1.3-1.2.dsc
 cb02174aa9aa90f3a15467e9c7d6b448 6760 utils optional 
diffpdf_2.1.3-1.2.debian.tar.xz
 cbc970fabec797ccff07d6197934f3c7 10793 utils optional 
diffpdf_2.1.3-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlpgkFsSHHN0dWFydEBk
ZWJpYW4ub3JnAAoJELvBfrsTlvL3xLEP/01U8/TpsQEWTYBmiHPafkyBIUSdWB68
uFM++/tSxu57I7qbFDRa8JGQobZqTiPcXQcmCRzMhZ+19ZBUVRYwi28siDJutkqP
SJnz8bX9129sv5QpCZ4hx8B2kYoLTPW+JqQbCzyS57L7Giv+33Ti5FEnY9WcaASP
6B+Gqx69yXtBlsVbnm0azvIB/pj2lZY5kN1cq1UopRkpkanYhzLskXWESucdvC8O
A4Iz9e+fhYZXKI4zP7vOHU0fCRt7pNsZMw4sbjkubP0yDpOnu2NDSYatPWCOqYJu
WCP2wbrsxUJ/JjGZuAv0ni6wxU6serwg5ZltGk0dVe4dtsWrqJ7AhGZQmFW5/iGZ
NdwrOIWdrnNOvlf2JnAygn2b9N5OqqOFgisB+VbJVmVknyQV2nt+3dwfTelJRos4
Grz5U0Me4QS2ytb+HmF3dONcz+8MYAikR/vp894g2uB15Ssu9pZn/Ckwpex/9Lxk
nNJCXXpGRhoUqrkH8UuFMGFI81vinaMoCTO4vX4JH1Cjlp40bZVbqahZ48P8H/H5
mAl2Ubqe6yvicfyxL8cx4v0K1Wsnwwb5GKu6OoqR9zKH88R3yGn9TObo1ofRH59j
3QmO8PH/Kv5JPjxP2lzkx7N54cNS6ec61ltM630cUBC5AWdaCi8EDmtiAaP0J6fc
zNePYpwoY437
=4G5d
-END PGP SIGNATURE-

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---

Bug#883496: marked as done (comparepdf: depends on libpoppler-qt4 which is about to be removed)

[Debian Bug Tracking System]

Your message dated Fri, 19 Jan 2018 16:22:23 +1100
with message-id <3747735.8duni2nbo0@simurgh>
and subject line Re: Bug#883496: libpoppler-qt4 dependency removed
has caused the Debian Bug report #883496,
regarding comparepdf: depends on libpoppler-qt4 which is about to be removed
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.)


-- 
883496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comparepdf
Severity: serious
Tags: sid stretch
User: pkg-freedesktop-maintain...@lists.alioth.debian.org
Usertags: oldlibs poppler-qt4

Control: block 875096 with -1

Hi,

comparepdf (build-)depends on Poppler Qt4 bindings, which have been
removed upstream in Poppler 0.62.0. They will be gone from Debian
soon, once we update to that version.

comparepdf should switch to the Qt5 bindings, or disable Poppler
support if the former is not possible.

If you have any question don't hesitate to ask.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Version: 1.0.1-1.1

Also closed in this NMU but I left the bug number out of the changelog :(

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 18 Jan 2018 22:47:16 +1100
Source: comparepdf
Binary: comparepdf
Architecture: source
Version: 1.0.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 
Changed-By: Stuart Prescott 
Description:
 comparepdf - command line tool for comparing two PDF files
Closes: 874846
Changes:
 comparepdf (1.0.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update package to Qt5 (Closes: #874846).
   * Bump to debhelper compat 11.
   * Update Standards-Version to 4.1.1 (no changes required).
   * Fix copyright format declaration.
   * Update Vcs headers to standard https values.
   * Pass build flags through to compiler to harden build.
Checksums-Sha1:
 f02bfe1f6eb6d45284377110edd4cfd170ad92b6 1923 comparepdf_1.0.1-1.1.dsc
 b116a539907390cb7143642ce421c3d495b363d1 3264 
comparepdf_1.0.1-1.1.debian.tar.xz
 130f023bb3ac1d2d076b68f4173fe49863004ef8 10371 
comparepdf_1.0.1-1.1_amd64.buildinfo
Checksums-Sha256:
 4b6a547c219684a1ae9d608eab6876fcfa72920384c66f404ca0110135a22a5a 1923 
comparepdf_1.0.1-1.1.dsc
 2333112b03edc11588b258e62bc80fc48bfeaca294af40592a61ba957aa5ac77 3264 
comparepdf_1.0.1-1.1.debian.tar.xz
 15e2f1e0477443bee5f9b8f49955b13d0ed34ea9315d9262c2ed96fd50441eb8 10371 
comparepdf_1.0.1-1.1_amd64.buildinfo
Files:
 8311e5cec1df87cf7affcfaae1922d52 1923 utils optional comparepdf_1.0.1-1.1.dsc
 fad33402891b822e0b020d9dbc53a043 3264 utils optional 
comparepdf_1.0.1-1.1.debian.tar.xz
 388d62ef9d56af9e54157c13dd5a0c3b 10371 utils optional 
comparepdf_1.0.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlpgkqsACgkQu8F+uxOW
8vf4URAAoGq8CqMQrkgVUMGvXaqYnMVLo7gz+bGW/lUskPr6nyP35HERU8+lrFEC
NS2Ue5YjywgQtYWX2PZxDUGtTrvHhwgqbHzgf1T1Dvh/RyxJH+ADZZwVUI5pubcu
TVcI8wawZqnFxEeLDp2v/kNC6LaR1Z3OJjLK+tmyuKpl6wEFrnGbsfPcZnoWUUjz
L8V0ZQ/24e1pv5QAAESiTrxqJnUghllqQQNTVRi4MKgq7DED9nXoJtGBW4+oUi3w
5Iy4sJ41+N5zA51Gq57FsH87ibiGv/QBHDEng7M1uIaXsLlcUhgJF5ZmgOk/H/PB
A+glNxNFbf/6Z7VGIJXz4QHLuA5fWdQJd3vKsiluAt2v7DyKEj0enOiL258bNlYb
SdALLXk9vPS6ai7CvsGmXEe147ZeOumUfO+13WuFFF9D4V2EU36lVA1qHDttg/Mw
hwfVSyzXiSKCl90qG8Wd699ZhrbG4ZmKU0iJtD7JsTmwwk4vxGjZqirkObVJ3ZYt
r5JK3dh+WPrA9i2QLxc12MUIWv34xaHxiqY8AQFi5ckHlikcqpQjOOVFPMNrWWPl
nHnTy6hS+TMadkY6zSl3jnzxts6ZX/O/znaGCa7OugyBbZyi2bOT94JGveJehj6u
3+EbHB/N/Gjhonly5RnLnJm0HoS6cVf07ptLZ5ipNE8cpnvPE1Q=
=czBe
-END PGP SIGNATURE-


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---

Bug#887695: nfs-utils FTBFS with glibc 2.26

[Adrian Bunk]

Source: nfs-utils
Version: 1:1.3.4-2.1
Severity: serious
Tags: buster sid

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

...
rpc.c: In function 'nsm_recv_getport':
rpc.c:469:13: error: 'UINT16_MAX' undeclared (first use in this function); did 
you mean 'UINT_MAX'?
  if (port > UINT16_MAX) {
 ^~
 UINT_MAX
rpc.c:469:13: note: each undeclared identifier is reported only once for each 
function it appears in
rpc.c: In function 'nsm_recv_getaddr':
rpc.c:506:25: error: 'UINT16_MAX' undeclared (first use in this function); did 
you mean 'UINT_MAX'?
  if (port < 0 || port > UINT16_MAX) {
 ^~
 UINT_MAX

Bug#883496: marked as done (comparepdf: depends on libpoppler-qt4 which is about to be removed)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 12:49:28 +
with message-id 
and subject line Bug#874846: fixed in comparepdf 1.0.1-1.1
has caused the Debian Bug report #883496,
regarding comparepdf: depends on libpoppler-qt4 which is about to be removed
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.)


-- 
883496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comparepdf
Severity: serious
Tags: sid stretch
User: pkg-freedesktop-maintain...@lists.alioth.debian.org
Usertags: oldlibs poppler-qt4

Control: block 875096 with -1

Hi,

comparepdf (build-)depends on Poppler Qt4 bindings, which have been
removed upstream in Poppler 0.62.0. They will be gone from Debian
soon, once we update to that version.

comparepdf should switch to the Qt5 bindings, or disable Poppler
support if the former is not possible.

If you have any question don't hesitate to ask.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: comparepdf
Source-Version: 1.0.1-1.1

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated comparepdf 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: Thu, 18 Jan 2018 22:47:16 +1100
Source: comparepdf
Binary: comparepdf
Architecture: source
Version: 1.0.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 
Changed-By: Stuart Prescott 
Description:
 comparepdf - command line tool for comparing two PDF files
Closes: 874846
Changes:
 comparepdf (1.0.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update package to Qt5 (Closes: #874846).
   * Bump to debhelper compat 11.
   * Update Standards-Version to 4.1.1 (no changes required).
   * Fix copyright format declaration.
   * Update Vcs headers to standard https values.
   * Pass build flags through to compiler to harden build.
Checksums-Sha1:
 f02bfe1f6eb6d45284377110edd4cfd170ad92b6 1923 comparepdf_1.0.1-1.1.dsc
 b116a539907390cb7143642ce421c3d495b363d1 3264 
comparepdf_1.0.1-1.1.debian.tar.xz
 130f023bb3ac1d2d076b68f4173fe49863004ef8 10371 
comparepdf_1.0.1-1.1_amd64.buildinfo
Checksums-Sha256:
 4b6a547c219684a1ae9d608eab6876fcfa72920384c66f404ca0110135a22a5a 1923 
comparepdf_1.0.1-1.1.dsc
 2333112b03edc11588b258e62bc80fc48bfeaca294af40592a61ba957aa5ac77 3264 
comparepdf_1.0.1-1.1.debian.tar.xz
 15e2f1e0477443bee5f9b8f49955b13d0ed34ea9315d9262c2ed96fd50441eb8 10371 
comparepdf_1.0.1-1.1_amd64.buildinfo
Files:
 8311e5cec1df87cf7affcfaae1922d52 1923 utils optional comparepdf_1.0.1-1.1.dsc
 fad33402891b822e0b020d9dbc53a043 3264 utils optional 
comparepdf_1.0.1-1.1.debian.tar.xz
 388d62ef9d56af9e54157c13dd5a0c3b 10371 utils optional 
comparepdf_1.0.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlpgkqsACgkQu8F+uxOW
8vf4URAAoGq8CqMQrkgVUMGvXaqYnMVLo7gz+bGW/lUskPr6nyP35HERU8+lrFEC
NS2Ue5YjywgQtYWX2PZxDUGtTrvHhwgqbHzgf1T1Dvh/RyxJH+ADZZwVUI5pubcu
TVcI8wawZqnFxEeLDp2v/kNC6LaR1Z3OJjLK+tmyuKpl6wEFrnGbsfPcZnoWUUjz
L8V0ZQ/24e1pv5QAAESiTrxqJnUghllqQQNTVRi4MKgq7DED9nXoJtGBW4+oUi3w
5Iy4sJ41+N5zA51Gq57FsH87ibiGv/QBHDEng7M1uIaXsLlcUhgJF5ZmgOk/H/PB
A+glNxNFbf/6Z7VGIJXz4QHLuA5fWdQJd3vKsiluAt2v7DyKEj0enOiL258bNlYb
SdALLXk9vPS6ai7CvsGmXEe147ZeOumUfO+13WuFFF9D4V2EU36lVA1qHDttg/Mw
hwfVSyzXiSKCl90qG8Wd699ZhrbG4ZmKU0iJtD7JsTmwwk4vxGjZqirkObVJ3ZYt
r5JK3dh+WPrA9i2QLxc12MUIWv34xaHxiqY8AQFi5ckHlikcqpQjOOVFPMNrWWPl
nHnTy6hS+TMadkY6zSl3jnzxts6ZX/O/znaGCa7OugyBbZyi2bOT94JGveJehj6u
3+EbHB/N/Gjhonly5RnLnJm0HoS6cVf07ptLZ5ipNE8cpnvPE1Q=
=czBe
-END PGP SIGNATURE End Message ---

Bug#886990: marked as done (transmission: rpc session-id mechanism design flaw results in RCE)

[Debian Bug Tracking System]

Your message dated Fri, 19 Jan 2018 05:04:51 +
with message-id 
and subject line Bug#886990: fixed in transmission 2.92-3
has caused the Debian Bug report #886990,
regarding transmission: rpc session-id mechanism design flaw results in RCE
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.)


-- 
886990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transmission
Version: 2.92-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/transmission/transmission/pull/468

Hi

See the post on oss-security for details:
http://www.openwall.com/lists/oss-security/2018/01/11/1

Upstream: https://github.com/transmission/transmission/pull/468

Proposed patch: 
https://patch-diff.githubusercontent.com/raw/transmission/transmission/pull/468.diff

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: transmission
Source-Version: 2.92-3

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated transmission 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: Thu, 18 Jan 2018 23:34:22 -0500
Source: transmission
Binary: transmission transmission-common transmission-cli transmission-gtk 
transmission-qt transmission-daemon
Architecture: source amd64 all
Version: 2.92-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 transmission - lightweight BitTorrent client
 transmission-cli - lightweight BitTorrent client (command line programs)
 transmission-common - lightweight BitTorrent client (common files)
 transmission-daemon - lightweight BitTorrent client (daemon)
 transmission-gtk - lightweight BitTorrent client (GTK+ interface)
 transmission-qt - lightweight BitTorrent client (Qt interface)
Closes: 771164 885151 886990
Changes:
 transmission (2.92-3) unstable; urgency=medium
 .
   * debian/patches/transmission-fix-dns-rebinding-vuln.patch
 - fix RCE execution via dns rebinding attach; fixes CVE-2018-5702;
   Closes: #886990
   * debian/patches/bts885151_fix_ftcbfs_ac_run_ifelse.patch
 - fix a FTCBFS due to use of AC_RUN_IFELSE; Closes: #885151
   * debian/{rules, transmission-qt.install}
 - fix translation load in Qt frontend; patch by Rohan Garg; Closes: #771164
   * debian/control
 - bump Standards-Version t0 4.1.3 (no changes needed)
 - update versioned b-d on debhelper, so that we can drop dh-systemd
   * debian/copyright
 - extend packaging copyright years
Checksums-Sha1:
 940b92e25f6153352bb3396277885c2038728295 2598 transmission_2.92-3.dsc
 299aef23d76c974b3c742c988cebd9ad614573ec 25316 
transmission_2.92-3.debian.tar.xz
 15c866fc94ddfc35b239aa9f0e26b77da3cd71ed 4899832 
transmission-cli-dbgsym_2.92-3_amd64.deb
 6e294b4fb776a79cd3dd7a648ab520655e764d25 403752 
transmission-cli_2.92-3_amd64.deb
 c290b1c1fcc1780defedcfff3e68650d2a0a4042 287512 
transmission-common_2.92-3_all.deb
 135d86270f24fa71cb1c681f2cca6ac20e181c32 1016784 
transmission-daemon-dbgsym_2.92-3_amd64.deb
 ba1ac416c9e69d85be829ccbb70c3b2a60f6ec94 219840 
transmission-daemon_2.92-3_amd64.deb
 dadfbceaf548029159b91b0c1744437c8913cc23 1599260 
transmission-gtk-dbgsym_2.92-3_amd64.deb
 e9180038e481c55437c6704a47d8ae364e3e9cd1 704076 
transmission-gtk_2.92-3_amd64.deb
 6a979c48018e73949822792d3a7195da2fa2c789 10489616 
transmission-qt-dbgsym_2.92-3_amd64.deb
 b786530ff48e9d0ef0e9a7a2a0abc66fa53833d9 665348 
transmission-qt_2.92-3_amd64.deb
 3ac94ba355fe9b205642e89a16a8134acdf79270 1236 transmission_2.92-3_all.deb
 6080f3794ace0f3467c9b40ad5f9e7a34e2c7166 20292 
transmission_2.92-3_amd64.buildinfo
Checksums-Sha256:
 2f2383b883774f0b593562badac753b5756410027afa509505f659d39ccc22f9 2598 
transmission_2.92-3.dsc
 d653eb13d8436afaf5e333f0c93d5e7a3f6ca9fed43870c1ccd79302ffe994df 25316 
transmission_2.92-3.debian.tar.xz
 

Processed: glibc 2.26 is now in unstable

[Debian Bug Tracking System]

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

> severity 882881 serious
Bug #882881 [src:silx] silx: Fails to build with glibc 2.26
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#887694: vpcs FTBFS with glibc 2.26

[Adrian Bunk]

Source: vpcs
Version: 0.5b2-1
Severity: serious
Tags: buster sid

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

...
gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -DLinux -Wall -I. -DTAP -DHV -Wno-strict-aliasing -c 
hv.c
In file included from hv.c:45:0:
./getopt.h:53:5: error: conflicting types for 'getopt'
 int getopt(int argc, char** argv, char* optstr);
 ^~
In file included from /usr/include/x86_64-linux-gnu/bits/getopt_posix.h:27:0,
 from /usr/include/unistd.h:872,
 from hv.c:33:
/usr/include/x86_64-linux-gnu/bits/getopt_core.h:91:12: note: previous 
declaration of 'getopt' was here
 extern int getopt (int ___argc, char *const *___argv, const char *__shortopts)
^~
Makefile.linux:36: recipe for target 'hv.o' failed
make[3]: *** [hv.o] Error 1

Bug#887693: ipe FTBFS with glibc 2.26

[Adrian Bunk]

Source: ipe
Version: 7.2.7-2
Severity: serious
Tags: buster sid

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

...
Compiling ipeplatform.cpp...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-Wall -Wno-sign-conversion -Wno-inconsistent-missing-override -g -O2 -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2 -DIPEUI_QT -fPIC -std=c++11 -I../include 
-I/usr/include/libpng16  -c -o ../../build/obj/ipelib/ipeplatform.o 
ipeplatform.cpp
ipeplatform.cpp:41:10: fatal error: xlocale.h: No such file or directory
 #include 
  ^~~
compilation terminated.
../common.mak:246: recipe for target '../../build/obj/ipelib/ipeplatform.o' 
failed
make[3]: *** [../../build/obj/ipelib/ipeplatform.o] Error 1

Bug#887692: casync: FTBFS and Debci failure with glibc 2.26

[Adrian Bunk]

Source: casync
Version: 2-1
Severity: serious

https://ci.debian.net/packages/c/casync/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/casync.html

...
FAILED: src/shared@sta/caremote.c.o 
cc  -Isrc/shared@sta -Isrc -I../src -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Werror=format=2 
-Wformat-security -Wformat-nonliteral -Wlogical-op -Wmissing-include-dirs 
-Werror=old-style-definition -Werror=pointer-arith -Winit-self 
-Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=missing-declarations -Werror=return-type 
-Werror=incompatible-pointer-types -Werror=shadow -Wstrict-prototypes 
-Wredundant-decls -Wmissing-noreturn -Wendif-labels -Wstrict-aliasing=2 
-Wwrite-strings -Wno-unused-parameter -Wno-missing-field-initializers 
-Wno-unused-result -Werror=overflow -Werror=sign-compare -Wdate-time 
-Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option 
-fno-strict-aliasing -fvisibility=hidden -fstack-protector 
-fstack-protector-strong -fPIE --param=ssp-buffer-size=4 -include config.h -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -MMD -MQ 'src/shared@sta/caremote.c.o' -MF 
'src/shared@sta/caremote.c.o.d' -o 'src/shared@sta/caremote.c.o' -c 
../src/caremote.c
In file included from ../src/caformat-util.h:7:0,
 from ../src/caremote.c:8:
../src/caremote.c: In function ‘ca_remote_forget_chunk’:
../src/util.h:471:13: error: argument 1 null where non-null expected 
[-Werror=nonnull]
 if (strncmp(s, prefix, l) == 0)
 ^
In file included from ../src/util.h:12:0,
 from ../src/caformat-util.h:7,
 from ../src/caremote.c:8:
/usr/include/string.h:139:12: note: in a call to function ‘strncmp’ declared 
here
 extern int strncmp (const char *__s1, const char *__s2, size_t __n)
^~~
cc1: some warnings being treated as errors

Bug#887690: unattended-upgrades: FTBFS and Debci failure after testpackage was removed from Ubuntu server

[Adrian Bunk]

Source: unattended-upgrades
Version: 0.98
Severity: serious

https://ci.debian.net/packages/u/unattended-upgrades/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unattended-upgrades.html

...
==
ERROR: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 100, in test_remove_unused_dependencies
options, rootdir="./root.unused-deps")
  File "/build/1st/unattended-upgrades-0.98/test/unattended_upgrade.py", line 
1462, in main
sys.exit(1)
SystemExit: 1

==
ERROR: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 122, in 
test_remove_unused_dependencies_new_unused_only
options, rootdir="./root.unused-deps")
  File "/build/1st/unattended-upgrades-0.98/test/unattended_upgrade.py", line 
1462, in main
sys.exit(1)
SystemExit: 1

--
Ran 2 tests in 0.486s

FAILED (errors=2)
The URI 'http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' failed to 
download, aborting
The URI 'http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' failed to 
download, aborting
Makefile:6: recipe for target 'check' failed
make[2]: *** [check] Error 1

Bug#887689: vdr-plugin-satip FTBFS with glibc 2.26

[Adrian Bunk]

Source: vdr-plugin-satip
Version: 2.3.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-satip.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"satip"'  -o satip.o satip.c
satip.c: In member function 'virtual cString cPluginSatip::SVDRPCommand(const 
char*, const char*, int&)':
satip.c:462:25: error: 'isspace' was not declared in this scope
  while (*option && !isspace(*option))
 ^~~

Bug#887688: debhelper: empty build of src:ck

[Adrian Bunk]

Package: debhelper
Version: 11.1.2
Severity: serious
Control: affects -1 src:ck

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

...
dh clean
   dh_clean
 debian/rules build
make: Nothing to be done for 'build'.
 fakeroot debian/rules binary
dh binary
   debian/rules build
make[1]: Entering directory '/build/1st/ck-0.6.0'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/build/1st/ck-0.6.0'
   dh_testroot
   dh_prep
   dh_install
dh_install: Cannot find (any matches for) "usr/lib/*/lib*.so.*" (tried in ., 
debian/tmp)

dh_install: libck0 missing files: usr/lib/*/lib*.so.*
dh_install: Cannot find (any matches for) "usr/include" (tried in ., debian/tmp)

dh_install: libck-dev missing files: usr/include
dh_install: Cannot find (any matches for) "usr/lib/*/lib*.so" (tried in ., 
debian/tmp)

dh_install: libck-dev missing files: usr/lib/*/lib*.so
dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig" (tried in ., 
debian/tmp)

dh_install: libck-dev missing files: usr/lib/*/pkgconfig
dh_install: Cannot find (any matches for) "usr/share/man" (tried in ., 
debian/tmp)

dh_install: libck-dev missing files: usr/share/man
dh_install: missing files, aborting
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 25


Works after downgrading to debhelper 11

Processed: debhelper: empty build of src:ck

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ck
Bug #887688 [debhelper] debhelper: empty build of src:ck
Added indication that 887688 affects src:ck

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

Processed: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:qt4-perl
Bug #887687 [libsmokeqt4-dev] libsmokeqt4-dev: broken symlinks and causes  
qt4-perl FTBFS
Added indication that 887687 affects src:qt4-perl

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

Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

[Adrian Bunk]

Package: libsmokeqt4-dev
Version: 4:4.14.3-1.2
Severity: serious
Control: affects -1 src:qt4-perl

qt4-perl FTBFS:

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

...
make[3]: *** No rule to make target '/usr/lib/libsmokeqt3support.so', needed by 
'blib/arch/auto/Qt3Support4/Qt3Support4.so'.  Stop.
make[3]: Leaving directory '/build/1st/qt4-perl-4.8.4/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:473: recipe for target 
'qt3support/src/CMakeFiles/perl_qt3support4.dir/all' failed
make[2]: *** [qt3support/src/CMakeFiles/perl_qt3support4.dir/all] Error 2
make[2]: Leaving directory '/build/1st/qt4-perl-4.8.4/obj-x86_64-linux-gnu'
Makefile:143: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/1st/qt4-perl-4.8.4/obj-x86_64-linux-gnu'


/usr/lib/libsmokeqt3support.so and several other .so
links are broken.

Bug#887686: brisk-menu: frequent parallel FTBFS

[Adrian Bunk]

Source: brisk-menu
Version: 0.5.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=brisk-menu=sid

...
FAILED: src/frontend/brisk-frontend@sta/category-button.c.o 
cc  -Isrc/frontend/brisk-frontend@sta -Isrc/frontend -I../src/frontend 
-Isrc/lib -I../src/lib -Isrc/backend -I../src/backend -Isrc -I../src 
-Isrc/session -I../src/session -I/usr/include/mate-menus 
-I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/gtk-3.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include 
-I/usr/include/atk-1.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-std=c11 -fstack-protector -Wall -pedantic -Wstrict-prototypes -Wundef 
-fno-common -Werror-implicit-function-declaration -Wformat -Wformat-security 
-Werror=format-security -Wconversion -Wunused-variable -Wunreachable-code -W 
-DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_3_18 -DGDK_VERSION_MIN_REQUIR
 ED=GDK_VERSION_3_18 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_44 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_44 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MMD -MQ 
'src/frontend/brisk-frontend@sta/category-button.c.o' -MF 
'src/frontend/brisk-frontend@sta/category-button.c.o.d' -o 
'src/frontend/brisk-frontend@sta/category-button.c.o' -c 
../src/frontend/category-button.c
In file included from ../src/frontend/category-button.c:18:0:
../src/frontend/menu-private.h:18:10: fatal error: libsaver-glue.h: No such 
file or directory
 #include "libsaver-glue.h"
  ^
compilation terminated.

Bug#887685: praat FTBFS and Debci failure

[Adrian Bunk]

Source: praat
Version: 6.0.36-3
Severity: serious

Some recent change in unstable makes praat FTBFS and Debci fail:

https://ci.debian.net/packages/p/praat/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/praat.html

...
117 tests passed, 104 ok
Failed test(s):

dwtools/Discriminant.praat
fon/Spectrum_draw.praat
fon/resample16_8.praat
fon/resample22_8.praat
fon/resample44_8.praat
sys/graphics.praat
sys/graphicsText.praat
sys/graphicsTextSpeed.praat
speechsynthesizer_test.praat
test_Sound_draw_where.praat
test_Sound_paint_where.praat
test_sigma_ellipse.praat
test_spectrogramTypes.praat
debian/rules:90: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#887684: psychtoolbox-3 FTBFS with glibc 2.26

[Adrian Bunk]

Source: psychtoolbox-3
Version: 3.0.14.20170103+git6-g605ff5c.dfsg1-1
Severity: serious
Tags: buster sid

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

...
Common/Screen/SCREENDrawText.c:1817:10: fatal error: xlocale.h: No such file or 
directory
 #include 
  ^~~
compilation terminated.

Bug#887633: marked as done (xymon FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Fri, 19 Jan 2018 02:52:45 +
with message-id 
and subject line Bug#887633: fixed in xymon 4.3.28-3
has caused the Debian Bug report #887633,
regarding xymon FTBFS with glibc 2.26
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.)


-- 
887633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xymon
Version: 4.3.28-2
Severity: serious

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

...
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wall -Wno-unused 
-Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-DLINUX -I/build/1st/xymon-4.3.28/include  -o logfetch logfetch.c 
../lib/libxymonclient.a
logfetch.c: In function 'logdata':
logfetch.c:210:105: error: 'intmax_t' undeclared (first use in this function); 
did you mean '__intmax_t'?
   errprintf("logfetch: %s delta %jd bytes exceeds max buffer size %u; skipping 
some data\n", filename, (intmax_t)bufsz, MAXCHECK);

 ^~~~

 __intmax_t
logfetch.c:210:105: note: each undeclared identifier is reported only once for 
each function it appears in
logfetch.c:210:114: error: expected ')' before 'bufsz'
   errprintf("logfetch: %s delta %jd bytes exceeds max buffer size %u; skipping 
some data\n", filename, (intmax_t)bufsz, MAXCHECK);

  ^
Makefile:41: recipe for target 'logfetch' failed
make[2]: *** [logfetch] Error 1
--- End Message ---
--- Begin Message ---
Source: xymon
Source-Version: 4.3.28-3

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated xymon 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: Fri, 19 Jan 2018 02:45:18 +0100
Source: xymon
Binary: xymon xymon-client
Architecture: source amd64
Version: 4.3.28-3
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg 
Changed-By: Axel Beckert 
Description:
 xymon  - monitoring system for systems, networks and applications
 xymon-client - client for the Xymon network monitor
Closes: 887633
Changes:
 xymon (4.3.28-3) unstable; urgency=medium
 .
   * Switch from prename/perl to file-rename/rename in
 debian/xymon.postinst and debian/control.
   * Downgrade rename usage to Suggests as the migration from "hobbit" to
 "xymon" in path names won't show up in normal setups and is guarded by
 an existence check.
   * Declare compliance with Debian Policy 4.1.3.
 + Switch debian/copyright DEP5 format URL to HTTPS.
 + Change Priority to optional.
   * Drop several spelling-error-in-binary lintian-overrides. (No more
 emitted.)
   * Remove trailing whitespace from debian/rules.
   * Set "Rules-Requires-Root: no".
   * Change debian/rules to the minimal "dh $@" style.
   * Bump debhelper compatibility level to 11.
 + Update versioned debhelper build-dependency accordingly.
 + Drop MAKEFLAGS=-j1 from debian/rules, parallel building seems to
   work now.
   * Fix lintian warning command-with-path-in-maintainer-script by using
 "if which …" instead of "if [ -x /usr/bin/…".
   * Fix FTBFS with glibc 2.26 by adding "#include " to
 client/logfetch.c. (Closes: #887633)
   * Update lintian overrides of apache2-deprecated-auth-config for
 additional parameter. Merge them into one override with wildcard for
 the Apache directive.
Checksums-Sha1:
 b8399f3334fd97b01a506266f5b4b5a00dda03de 2091 xymon_4.3.28-3.dsc
 fa42b31248c724139e147b02742fe6fb06be6044 43528 

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Michael Biebl]

On Fri, 19 Jan 2018 02:24:35 +0100 Cyril Brulebois  wrote:
> Getting back to src:vte2.91 though, that's not sufficient, as the
> resulting udeb depends (right now or after a rebuild against a patched
> pcre2) on libstdc++6. We don't do c++ in d-i.

That's going to be hard:
https://git.gnome.org/browse/vte/commit/?id=958859d14ef4d94fc4735c700f550b57739f31ac

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



signature.asc
Description: OpenPGP digital signature

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Michael Biebl]

On Thu, 18 Jan 2018 19:11:36 -0500 Jeremy Bicha  wrote:
> Control: block -1 by 887674
> 
> On Thu, Jan 18, 2018 at 6:51 PM, Cyril Brulebois  wrote:
> >  - vte2.91 needs to build an installable udeb; I think I've reported a
> >few issues already, but I don't tend to do so in a timely fashion
> >since it's not used yet. Right now, libpcre2-8-0 is the issue.
> 
> Ok, I filed a bug asking for a pcre2 udeb.

What about gnutls28?
objdump -x /usr/lib/x86_64-linux-gnu/libvte-2.91.so.0.5000.2 | grep NEEDED
lists

  NEEDED   libgnutls.so.30

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



signature.asc
Description: OpenPGP digital signature

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Michael Biebl]

Am 19.01.2018 um 03:02 schrieb Michael Biebl:
> On Thu, 18 Jan 2018 19:11:36 -0500 Jeremy Bicha  wrote:
>> Control: block -1 by 887674
>>
>> On Thu, Jan 18, 2018 at 6:51 PM, Cyril Brulebois  wrote:
>>>  - vte2.91 needs to build an installable udeb; I think I've reported a
>>>few issues already, but I don't tend to do so in a timely fashion
>>>since it's not used yet. Right now, libpcre2-8-0 is the issue.
>>
>> Ok, I filed a bug asking for a pcre2 udeb.
> 
> What about gnutls28?
> objdump -x /usr/lib/x86_64-linux-gnu/libvte-2.91.so.0.5000.2 | grep NEEDED
> lists
> 
>   NEEDED   libgnutls.so.30
> 

nvm...

CONFFLAGS_udeb = \
   --disable-gtk-doc \
   --without-gnutls


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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Debian Bug Tracking System]

Processing control commands:

> severity 887674 important
Bug #887674 [src:pcre2] pcre2: Please add udeb package
Severity set to 'important' from 'serious'
> tag 887674 patch
Bug #887674 [src:pcre2] pcre2: Please add udeb package
Ignoring request to alter tags of bug #887674 to the same tags previously set
> tag 887649 - patch
Bug #887649 [cdebconf-gtk-terminal] cdebconf-gtk-terminal: Please don't depend 
on unmaintained vte
Removed tag(s) patch.

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

Processed: Re: Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Debian Bug Tracking System]

Processing control commands:

> severity 887674 important
Bug #887674 [src:pcre2] pcre2: Please add udeb package
Ignoring request to change severity of Bug 887674 to the same value.
> tag 887674 patch
Bug #887674 [src:pcre2] pcre2: Please add udeb package
Ignoring request to alter tags of bug #887674 to the same tags previously set
> tag 887649 - patch
Bug #887649 [cdebconf-gtk-terminal] cdebconf-gtk-terminal: Please don't depend 
on unmaintained vte
Ignoring request to alter tags of bug #887649 to the same tags previously set

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

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Cyril Brulebois]

Control: severity 887674 important
Control: tag 887674 patch
Control: tag 887649 - patch

Cyril Brulebois  (2018-01-19):
> Control: severity -1 887674
> Control: tag -1 patch

Wow, that was incredibly stupid, sorry. (Blaming this on headache.)

> No need to have a serious bug there, adjusting severity; the attached
> patch seems to do the job for src:pcre2. An extra one makes it build
> way faster (tested on 8 cores without stumbling upon any issues).
> 
> Getting back to src:vte2.91 though, that's not sufficient, as the
> resulting udeb depends (right now or after a rebuild against a patched
> pcre2) on libstdc++6. We don't do c++ in d-i.

I meant to add this: for some reason dose-debcheck doesn't detect this
issue, I only happened to stumble upon it when checking the updated
Depends line. :(


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


signature.asc
Description: PGP signature

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Cyril Brulebois]

Control: severity -1 887674
Control: tag -1 patch

Hi,

Jeremy Bicha  (2018-01-18):
> On Thu, Jan 18, 2018 at 6:51 PM, Cyril Brulebois  wrote:
> >  - vte2.91 needs to build an installable udeb; I think I've reported a
> >few issues already, but I don't tend to do so in a timely fashion
> >since it's not used yet. Right now, libpcre2-8-0 is the issue.
> 
> Ok, I filed a bug asking for a pcre2 udeb.

No need to have a serious bug there, adjusting severity; the attached
patch seems to do the job for src:pcre2. An extra one makes it build
way faster (tested on 8 cores without stumbling upon any issues).

Getting back to src:vte2.91 though, that's not sufficient, as the
resulting udeb depends (right now or after a rebuild against a patched
pcre2) on libstdc++6. We don't do c++ in d-i.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
From 7b92f426899bf42311546d898c37e83ff9806389 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Fri, 19 Jan 2018 01:03:32 +
Subject: [PATCH 1/2] Add a libpcre2-8-0-udeb, needed by vte2.91 (Closes:
 #887674)

---
 debian/changelog | 6 ++
 debian/control   | 8 
 debian/libpcre2-8-0-udeb.install | 1 +
 debian/rules | 3 +++
 4 files changed, 18 insertions(+)
 create mode 100644 debian/libpcre2-8-0-udeb.install

diff --git a/debian/changelog b/debian/changelog
index b0de24f..0afc8f8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pcre2 (10.22-6) UNRELEASED; urgency=medium
+
+  * Add a libpcre2-8-0-udeb, needed by vte2.91 (Closes: #887674)
+
+ -- Cyril Brulebois   Fri, 19 Jan 2018 01:00:12 +
+
 pcre2 (10.22-5) unstable; urgency=medium
 
   * Add Vcs-{Git,Browser} fields to debian/control
diff --git a/debian/control b/debian/control
index db57fd3..5478f42 100644
--- a/debian/control
+++ b/debian/control
@@ -22,6 +22,14 @@ Description: New Perl Compatible Regular Expression Library- 8 bit runtime files
  .
  This package contains the 8 bit runtime library.
 
+Package: libpcre2-8-0-udeb
+Package-Type: udeb
+Section: debian-installer
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: New Perl Compatible Regular Expression Library- 8 bit runtime files (udeb)
+ This package contains the 8 bit runtime library, for the Debian Installer.
+
 Package: libpcre2-16-0
 Section: libs
 Architecture: any
diff --git a/debian/libpcre2-8-0-udeb.install b/debian/libpcre2-8-0-udeb.install
new file mode 100644
index 000..1a38dd6
--- /dev/null
+++ b/debian/libpcre2-8-0-udeb.install
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*/libpcre2-8.so.*
diff --git a/debian/rules b/debian/rules
index 66c4b28..07bd4b3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -25,5 +25,8 @@ endif
 override_dh_auto_configure:
 	dh_auto_configure -- $(deb_maint_conf_args)
 
+override_dh_makeshlibs:
+	dh_makeshlibs -V --add-udeb=libpcre2-8-0-udeb
+
 override_dh_strip:
 	dh_strip --dbg-package=libpcre2-dbg
-- 
2.11.0

From 74b118609c5715d6ec913c3a610cbaedc936693d Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Fri, 19 Jan 2018 02:23:44 +0100
Subject: [PATCH 2/2] Enable parallel building.

---
 debian/changelog | 1 +
 debian/rules | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 0afc8f8..0ffbc97 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 pcre2 (10.22-6) UNRELEASED; urgency=medium
 
   * Add a libpcre2-8-0-udeb, needed by vte2.91 (Closes: #887674)
+  * Enable parallel building.
 
  -- Cyril Brulebois   Fri, 19 Jan 2018 01:00:12 +
 
diff --git a/debian/rules b/debian/rules
index 07bd4b3..614ac4a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,7 +20,7 @@ deb_maint_conf_args +=--disable-jit
 endif
 
 %:
-	dh $@
+	dh $@ --parallel
 
 override_dh_auto_configure:
 	dh_auto_configure -- $(deb_maint_conf_args)
-- 
2.11.0



signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Debian Bug Tracking System]

Processing control commands:

> severity -1 887674
Severity level `887674' is not known.
Recognized are: critical, grave, serious, important, normal, minor, wishlist, 
fixed.

> tag -1 patch
Bug #887674 [src:pcre2] pcre2: Please add udeb package
Added tag(s) patch.

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

Processed (with 1 error): Re: Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Debian Bug Tracking System]

Processing control commands:

> severity -1 887674
Severity level `887674' is not known.
Recognized are: critical, grave, serious, important, normal, minor, wishlist, 
fixed.

> tag -1 patch
Bug #887649 [cdebconf-gtk-terminal] cdebconf-gtk-terminal: Please don't depend 
on unmaintained vte
Added tag(s) patch.

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

Bug#886998: regressions also possible on Skylake

[Henrique de Moraes Holschuh]

Updated information from Intel:
https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088

---8<---

Recommendations: 

Status

Intel has made significant progress in our investigation into the
customer reboot sightings that we confirmed publicly last week
Intel has reproduced these issues internally and has developed a
test method that allows us to do so in a predictable manner
Initial sightings were reported on Broadwell and Haswell based
platforms in some configurations. During due diligence we determined
that similar behavior occurs on other products including Ivy Bridge,
Sandy Bridge, Skylake, and Kaby Lake based platforms in some
configurations
We are working toward root cause
While our root cause analysis continues, we will start making beta
microcode updates available to OEMs, Cloud service providers, system
manufacturers and Software vendors next week for internal evaluation
purposes
In all cases, the existing and any new beta microcode updates
continue to provide protection against the exploit (CVE-2017-5715) also
known as “Spectre Variant 2”
Variants 1 (Spectre) and Variant 3 (Meltdown) continue to be
mitigated through system software changes from operating system and
virtual machine vendors
As we gather feedback from our customers we will continue to provide
updates that improve upon performance and usability

Intel recommendations to OEMs, Cloud service providers, system
manufacturers and software vendors

Intel recommends that these partners maintain availability of
existing microcode updates already released to end users. Intel does not
recommend pulling back any updates already made available to end users
NEW - Intel recommends that these partners, at their discretion,
continue development and release of updates with existing microcode to
provide protection against these exploits, understanding that the
current versions may introduce issues such as reboot in some
configurations
NEW - We further recommend that OEMs, Cloud service providers,
system manufacturers and software vendors begin evaluation of Intel beta
microcode update releases in anticipation of definitive root cause and
subsequent production releases suitable for end users

---8<---


As such, current plans are to _not_ distributed updated microcode
packages to Debian stable users, until a new batch of microcode updates
are released by Intel.

"Beta" microcode updates will be initially uploaded to experimental (if
such updates are made available to Debian): do *not* assume that beta
updates "can't be worse than the current ones".

-- 
  Henrique Holschuh

Bug#887571: marked as done (debhelper: dh lies about what it does, breaks builds by creating new files, etc)

[Debian Bug Tracking System]

Your message dated Fri, 19 Jan 2018 09:15:08 +0900
with message-id <20180119001506.qptjmri3zv54i...@bulldog.preining.info>
and subject line Re: [debhelper-devel] Bug#887571: debhelper: dh lies about 
what it does, breaks builds by creating new files, etc
has caused the Debian Bug report #887571,
regarding debhelper: dh lies about what it does, breaks builds by creating new 
files, etc
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.)


-- 
887571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.2
Severity: serious
Justification: breaks other packages

Dear DebHelper developers,

thanks for your efforts, but it would be very helpful if debhelper/dh
would stick to what itself says it is doing.

I am trying to build texlive-bin, and somewhere at/around the configure
stage files
  configure.lineno
are created, which break building:
  checking whether g++ accepts -g... no
  checking dependency style of g++... none
  checking what warning flags to pass to the Objective C++ compiler...
  ../../../texk/web2c/configure: 20010: ./configure.lineno: Syntax error: Bad 
fd number
  === configuring in web2c failed

I confirmed the following:
* doing the same invocation of configure manually does NOT create
  configure.lineno and the build succeeds.
* what dh says it is doing with 
dh binary --no-act ...
  is *different* from what is actually happening, since doing the exact
  same things as listed by dh binary --no-act immediately breaks

Example for this (the reautoconf stage has already been done):
  $ dh binary --no-act --with autoreconf --builddirectory Work
  debian/rules override_dh_auto_configure
  dh_auto_build -O--builddirectory=Work
  dh_auto_test -O--builddirectory=Work

But doing
  $ debian/rules override_dh_auto_configure
breaks becasue it does not change into Work before calling configure.

Adding the obviously necessary
  DH_INTERNAL_BUILDFLAGS=1
  DH_INTERNAL_OPTIONS=-O--builddirectory=Work
  DH_INTERNAL_OVERRIDE=dh_auto_configure
make the above command work, but somewhere/somehow starts creating
configure.lineno files, while doing the configure.

Calling make -f debian/rules binary I see the following:
$ make -f debian/rules binary
dh binary --with autoreconf --builddirectory Work
   debian/rules override_dh_auto_configure
make[1]: Entering directory 
'/home/norbert/Development/TeX/debian/git/build-area/texlive-bin-2018.20180118.46355'
# we have to make sure that the mendex test case that is added
# by a patch is executable
chmod 0755 texk/mendexk/tests/mendex.test
# run out configure script
dh_auto_configure -- -C --prefix=/usr   \
--datarootdir=/usr/share/texlive\
--disable-native-texlive-build  \
 OTHER configure args
--enable-ipc
cd Work && ../configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdi
  
configure: creating cache config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc

and at this time
  configure.lineno
is already existing, and propagated down the tree and breaking the build
builds.

But doing by hand, EVEN with the above three env variables set, doing
only the
  cd Work && ../configure --build=x86_64-lin ...
part does NOT create configure.lineno.


Also running
  dh_auto_configure -- -C --prefix=/usr \
--datarootdir=/usr/share/texlive\
  
does NOT create configure.lineno.

As a consequence, the only remaining candidate is that 
  dh
does *something*else* before calling the targets or setting env vars.

This is extremely difficult to debug without a proper documentation and
completely unreproducible behaviour from dh.

It is hard to guess what happens here, and I would be very grateful for
an expanation what else dh is doing before calling the actual things it
says it is calling.

Best

Norbert

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

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

Versions of packages debhelper depends on:
ii  autotools-dev20171216.1
ii  

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Jeremy Bicha]

Control: block -1 by 887674

On Thu, Jan 18, 2018 at 6:51 PM, Cyril Brulebois  wrote:
>  - vte2.91 needs to build an installable udeb; I think I've reported a
>few issues already, but I don't tend to do so in a timely fashion
>since it's not used yet. Right now, libpcre2-8-0 is the issue.

Ok, I filed a bug asking for a pcre2 udeb.

Thanks,
Jeremy Bicha

Processed: Re: Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 887674
Bug #887649 [cdebconf-gtk-terminal] cdebconf-gtk-terminal: Please don't depend 
on unmaintained vte
887649 was not blocked by any bugs.
887649 was not blocking any bugs.
Added blocking bug(s) of 887649: 887674

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

Bug#887674: pcre2: Please add udeb package

[Jeremy Bicha]

Source: pcre2
Version: 10.22-5
Severity: serious

Please add a udeb package for use by cdebconf-gtk-terminal. I see that
pcre3 has a udeb package so maybe that can be used as a template for
how the pcre2 udeb would work.

I'm filing this as serious since this issue is blocking the removal of
the unmaintained vte library and I believe we want to try to switch
the debian-installer from gtk2 to gtk3 for Debian 10 "Buster". pcre2
is a "key package" so it will not be auto-removed.

Thanks,
Jeremy Bicha

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Cyril Brulebois]

Hi,

Jeremy Bicha  (2018-01-18):
> Package: cdebconf-gtk-terminal
> Version: 0.31
> Severity: serious
> Tags: sid buster
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs vte
> 
> cdebconf-gtk-terminal Depends and Build-Depends on vte. In fact, it's
> now the only package keeping vte in Debian Testing. The Debian GNOME
> team does not intend to release Debian 10 "Buster" with vte since the
> old 0.28 series has not had a release since GNOME3's release in 2011.

OK. I've considered switching a couple of times since 2012, but I've
been hitting various issues. But now that we have (almost, see below)
all components in place for gtk3 (including at-spi* and friends), and
now that old libraries are to be gotten rid of, I guess it's reasonable
for us to finally bite the bullet.

> Please port to the vte2.91 source. That also means porting to gtk3.
> gtk3 was declared stable over a year ago with the 3.22 series. (There
> also have not been any gtk2 maintenance releases
> since that time, although I guess someone will do a gtk2 maintenance
> release eventually this year.)

A few things need to happen, besides porting cdebconf to gtk3 (there
have been preliminary patches for many years already):
 - vte2.91 needs to build an installable udeb; I think I've reported a
   few issues already, but I don't tend to do so in a timely fashion
   since it's not used yet. Right now, libpcre2-8-0 is the issue.
 - theme support needs to be ported to gtk3.


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


signature.asc
Description: PGP signature

Bug#886506: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Cyril Brulebois]

Raphael Hertzog  (2018-01-17):
> On Wed, 17 Jan 2018, Aurelien Jarno wrote:
> > busybox is compiled with -mpreferred-stack-boundary=2 on i386 which has
> > the same effect of reducing the default stack alignment from 16 bytes to
> > 2 bytes. This comes from arch/i386/Makefile:
> > 
> > |  # -mpreferred-stack-boundary=2 is essential in preventing gcc 4.2.x
> > |  # from aligning stack to 16 bytes. (Which is gcc's way of supporting 
> > SSE).
> > |  CFLAGS += $(call cc-option,-march=i386 -mpreferred-stack-boundary=2,)
> > 
> > I don't really get why it is essential to prevent gcc from aligning
> > stack to 16 bytes, anyway this is a bad idea. Removing this option just
> > fixes the issue.

Oh wow, that's an old commit:
| commit 65b8cfb2a0b6854271dbd8baf5203896223cd4ce
| Author: Denis Vlasenko 
| Date:   Mon Jul 23 21:05:06 2007 +
| 
| add comment why preferred stack boundary is 4 on i386

> I confirm that rebuilding busybox with this option dropped fixed the issue
> for me. I uploaded a fixed busybox to Kali. I'm happy to do the same for
> Debian if it can help the current maintainers.

Fixing it ASAP would look good to me (unless you here differently from
Chris or Christoph); it would be great to ping upstream to propagate
Aurélien's comments too.


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


signature.asc
Description: PGP signature

Bug#887664: openal-soft: FTBFS: nothing is built

[Simon McVittie]

Control: retitle -1 openal-soft: FTBFS with dpkg-buildpackage --build=any,all

On Thu, 18 Jan 2018 at 22:28:15 +0100, Guus Sliepen wrote:
> Source: openal-soft
> Version: 1:1.18.2-1
> Severity: serious
> Justification: Policy 4.9
> 
> Building openal-soft from source in a pbuilder environment fails.

It looks like it succeeds if you build Architecture: all and
Architecture: any separately (which is what the buildds do, and what
anyone who is deliberately mimicking the buildds will do), because that
invokes "debian/rules build-arch" and "debian/rules build-indep"; but
fails if you build both in the same dpkg-buildpackage, because that
invokes "debian/rules build".

This is the first time I've seen a failure mode unique to building all
and any together - normally building all and any separately is the more
fragile mode, in my experience.

> It seems like it thinks there is nothing to build

This appears to be caused by the presence of a build/ directory (containing
an empty file named .empty) in the upstream tarball. Andres Mejia added
the solution that I was about to suggest,

.PHONY: build

in debian/rules, in 2009; I wonder why that's no longer enough to make
it work?

Perhaps this

.PHONY: build
build: build-arch

or this

.PHONY: build
build:
dh $@ --builddirectory=$(BUILD_TREE)

would work better?

smcv

Processed: Re: Bug#887664: openal-soft: FTBFS: nothing is built

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 openal-soft: FTBFS with dpkg-buildpackage --build=any,all
Bug #887664 [src:openal-soft] openal-soft: FTBFS: nothing is built
Changed Bug title to 'openal-soft: FTBFS with dpkg-buildpackage 
--build=any,all' from 'openal-soft: FTBFS: nothing is built'.

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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[David Kalnischkies]

Hi,

On Thu, Jan 18, 2018 at 09:45:51PM +0100, Aurelien Jarno wrote:
> > > > [...]
> > > >   Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
> > > >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> > > > not found (required by /lib/i386-linux-gnu/libexpat.so.1)
> > > >   dpkg: warning: subprocess old pre-removal script returned error exit 
> > > > status 1
> > > >   dpkg: trying script from the new package instead ...
> > > >   dpkg: error processing archive 
> > > > /tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb 
> > > > (--unpack):
> > > >there is no script in the new version of the package - giving up
> > > >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> > > > not found (required by /lib/i386-linux-gnu/libexpat.so.1)
> > > 
> > > This failure is normal given libexpat1 requires the new libc which has
> > > not been unpacked yet.
> > 
> > Yeah, well, it needs to Pre-Depend on it then I guess, if it's being used
> > in preinst actions. The thing is that Depends only after postinst ordering,
> > not unpack ordering.
> 
> Well it's not the preinst script, but the prerm script. The problem is
> unpacking libexpat1 before libc6 breaks libexpat1 and not usable
> anymore.

prerm is the very first script being called (see §6.6) and usually it is
the script of the version installed (only in error cases the script from
the version being upgraded to will be tried as detailed in the dpkg
messages) so I would argue that the dependencies (maybe) satisfied are
the dependencies of the installed version, not the one being installed
(argueably the dependency set of v1 and v2 could conflict with each
other, so if dependencies of v2 would be satisfied that means v1 script
would be bound to explode). But thats perhaps just the fear talking as
going with dependencies of v2 would probably result in a lot of hard
coding problems for apt & dpkg (and other low package managers).

In any case, the unpack of these packages is in the same dpkg call, so
if dpkg would have wanted it could have reordered them & apt has no idea
about maintainerscript in general, so I would say this isn't an apt bug.

(Althrough, if we decide on v2, I guess apt needs to change anyhow as
that same call thing might be just dumb luck in this case. Not even sure
if v1 is in any way "guaranteed" to be perfectly honest…)

Can't stop the feeling that we had issues with python begin called from
prerm before and the general advice was: "don't – stick to essential".


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#887621: marked as done (libvlc-bin: trigger problem after upgrade from stretch: find: '/usr/lib/x86_64-linux-gnu/vlc/plugins': No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 22:09:00 +
with message-id 
and subject line Bug#887621: fixed in vlc 3.0.0~rc6-1
has caused the Debian Bug report #887621,
regarding libvlc-bin: trigger problem after upgrade from stretch: find: 
'/usr/lib/x86_64-linux-gnu/vlc/plugins': No such file or directory
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.)


-- 
887621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vlc
Version: 3.0.0~rc5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up libvlc-bin:amd64 (3.0.0~rc5-1) ...
  Processing triggers for libc-bin (2.26-2) ...
  Processing triggers for libvlc-bin:amd64 (3.0.0~rc5-1) ...
  find: '/usr/lib/x86_64-linux-gnu/vlc/plugins': No such file or directory
  dpkg: error processing package libvlc-bin:amd64 (--configure):
   installed libvlc-bin:amd64 package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   libvlc-bin:amd64


cheers,

Andreas


libvlc-bin_3.0.0~rc5-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: vlc
Source-Version: 3.0.0~rc6-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated vlc 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: Thu, 18 Jan 2018 22:31:56 +0100
Source: vlc
Binary: vlc libvlc-dev libvlc5 libvlccore-dev libvlccore9 libvlc-bin vlc-bin 
vlc-data vlc-l10n vlc-plugin-base vlc-plugin-access-extra 
vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization 
vlc-plugin-skins2 vlc-plugin-qt vlc-plugin-fluidsynth vlc-plugin-jack 
vlc-plugin-notify vlc-plugin-svg vlc-plugin-samba vlc-plugin-zvbi
Architecture: source
Version: 3.0.0~rc6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 libvlc-bin - tools for VLC's base library
 libvlc-dev - development files for libvlc
 libvlc5- multimedia player and streamer library
 libvlccore-dev - development files for libvlccore
 libvlccore9 - base library for VLC and its modules
 vlc- multimedia player and streamer
 vlc-bin- binaries from VLC
 vlc-data   - common data for VLC
 vlc-l10n   - translations for VLC
 vlc-plugin-access-extra - multimedia player and streamer (extra access plugins)
 vlc-plugin-base - multimedia player and streamer (base plugins)
 vlc-plugin-fluidsynth - FluidSynth plugin for VLC
 vlc-plugin-jack - JACK audio plugins for VLC
 vlc-plugin-notify - LibNotify plugin for VLC
 vlc-plugin-qt - multimedia player and streamer (Qt plugin)
 vlc-plugin-samba - Samba plugin for VLC
 vlc-plugin-skins2 - multimedia player and streamer (Skins2 plugin)
 vlc-plugin-svg - SVG plugin for VLC
 vlc-plugin-video-output - multimedia player and streamer (video output plugins)
 vlc-plugin-video-splitter - multimedia player and streamer (video splitter 
plugins)
 vlc-plugin-visualization - multimedia player and streamer (visualization 
plugins)
 vlc-plugin-zvbi - transitional dummy package
Closes: 887440 887621
Changes:
 vlc (3.0.0~rc6-1) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * debian/control: Annotate Build-Depends: python3 with :native. (Closes:
 #887440)
 .
   [ Sebastian Ramacher ]
   * New upstream release candidate.
   * debian/rules:
 - Handle vendor consistently.
 - Remove workaround for some resources.
   * debian/vlc-plugin-base.install: Install lua byte code.
   * debian/libvlc-bin.postinst.in: Exit early if plugins directory does not
 exist. 

Bug#887062: [Pkg-raspi-maintainers] Bug#887062: raspi3-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/

[Michael Stapelberg]

Thanks for the additional details.

Given that the package’s only purpose is to populate /boot/firmware, may I
ask why it’s being installed in your builds at all? I’d like to understand
the use-case before adding code to deal with it.

On Mon, Jan 15, 2018 at 12:42 PM, Raphael Hertzog 
wrote:

> On Sat, 13 Jan 2018, Michael Stapelberg wrote:
> > The only change that seems in any way related to me is
> > https://anonscm.debian.org/cgit/pkg-raspi/raspi3-
> firmware.git/commit/?id=c977f0210ab5c577b9d5296e4e4391225a7f85ca
>
> This change is not the cause of the regression. The package fails at
> initial installation, not on upgrade. I have added "set -x" and I get
> this:
>
> # dpkg --configure raspi3-firmware
> Setting up raspi3-firmware (1.20171201-2) ...
> + ischroot
> + basename /usr/lib/raspi3-firmware/bootcode.bin
> + file=bootcode.bin
> + cp /usr/lib/raspi3-firmware/bootcode.bin /boot/firmware/bootcode.bin
> cp: cannot create regular file '/boot/firmware/bootcode.bin': No such file
> or directory
> dpkg: error processing package raspi3-firmware (--configure):
>  installed raspi3-firmware package post-installation script subprocess
> returned error exit status 1
> Errors were encountered while processing:
>  raspi3-firmware
>
> I wonder how it worked before. Maybe the package shipped /boot/firmware or
> another package supplied that directory and it now fails because no
> package is creating it.
>
> In any case, you should probably not attempt to copy the files there if the
> directory is not existing.
>
> Something like this:
>
> --- /tmp/postinst   2018-01-15 11:35:43.223477268 +
> +++ /var/lib/dpkg/info/raspi3-firmware.postinst 2018-01-15
> 11:40:31.818918341 +
> @@ -13,19 +13,23 @@
>fi
>  fi
>
> -for file in /usr/lib/raspi3-firmware/*
> -do
> -  file=$( basename "$file" )
> -  cp "/usr/lib/raspi3-firmware/$file" "/boot/firmware/$file"
> -  # sync might fail when running under qemu, which, as of version 2.7,
> -  # has not implemented the syncfs syscall.
> -  sync -f "/boot/firmware/$file" || true
> -done
> +if [ -d /boot/firmware ]; then
> +   for file in /usr/lib/raspi3-firmware/*
> +   do
> + file=$( basename "$file" )
> + cp "/usr/lib/raspi3-firmware/$file" "/boot/firmware/$file"
> + # sync might fail when running under qemu, which, as of version
> 2.7,
> + # has not implemented the syncfs syscall.
> + sync -f "/boot/firmware/$file" || true
> +   done
>
> -# Manually trigger the kernel postinst hook when raspi3-firmware is
> first
> -# installed (or upgraded), as the kernel package might already be
> installed
> -# (or not upgraded) and hence the hook would not get triggered
> otherwise.
> -DEB_MAINT_PARAMS="configure" /etc/kernel/postinst.d/raspi3-firmware
> +   # Manually trigger the kernel postinst hook when raspi3-firmware
> is first
> +   # installed (or upgraded), as the kernel package might already be
> installed
> +   # (or not upgraded) and hence the hook would not get triggered
> otherwise.
> +   DEB_MAINT_PARAMS="configure" /etc/kernel/postinst.d/raspi3-
> firmware
> +else
> +   echo "Warning: not copying firmwares as /boot/firmware does not
> exist." >&2
> +fi
>  ;;
>  esac
>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Support Debian LTS: https://www.freexian.com/services/debian-lts.html
> Learn to master Debian: https://debian-handbook.info/get/
>



-- 
Best regards,
Michael

Bug#887666: jh_linkjars: Invalid option: N

[Niels Thykier]

Control: reassign -1 javahelper

On Thu, 18 Jan 2018 23:41:19 +0200 Adrian Bunk  wrote:
> Package: debhelper
> Version: 11.1.2
> Severity: serious
> Control: affects -1 javahelper src:zabbix
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zabbix.html
> 
> ...
>jh_linkjars -O--max-parallel=4 -Nzabbix-frontend-php -Nzabbix-java-gateway
> Invalid option: N
> Usage: jh_linkjars [options] [target] 
> Options:
>   -h --help: show this text
>   -V --version: show the version
>   -v --verbose: show more information while running
>   -t --transitive: transitively link jars
>   -n --no-act: don't actually do anything, just print the results
>   -u --unlink: remove the links instead of adding them
> debian/rules:77: recipe for target 'binary' failed
> make: *** [binary] Error 1
> 
> 
> Works after downgrading to debhelper 11
> 
> 


The -N option is a basic "shared" debhelper option required by any
dh-like tool added to the debhelper sequence (similar to -p/-s/-i).  The
solution here is to have javahelper support that option.

Thanks,
~Niels

Processed: Re: jh_linkjars: Invalid option: N

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 javahelper
Bug #887666 [debhelper] jh_linkjars: Invalid option: N
Bug reassigned from package 'debhelper' to 'javahelper'.
No longer marked as found in versions debhelper/11.1.2.
Ignoring request to alter fixed versions of bug #887666 to the same values 
previously set

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

Bug#825501: CVE-2016-4434

[Faidon Liambotis]

On Thu, Jan 18, 2018 at 10:36:24PM +0100, Salvatore Bonaccorso wrote:
> > > That link says:
> > >   Versions Affected: 
> > >   Apache Tika 0.10 to 1.12
> > > 
> > > So perhaps 1.5 isn't affected after all? I tried to find the relevant
> > > commit in the upstream git but failed :(
> > 
> > Commit 
> > https://github.com/apache/tika/commit/f444fd784b99b181cd7bd54cdec9fbd132b4ef93
> > in 1.17 added a test case, so this might be related to changes in Xerces/J
> > which are possibly bundled by Tika downloads? Might be worth clarifying with
> > Tim Allison .
> 
> Above, you said "so perhaps 1.5 isn't affected after all?". But why
> this conclusion? 1.5 as currently in unstable and oldstable present
> falls within the affected range of 0.15 and 1.12.

s/0.15/0.10/ in what you said just above, but yes, you're obviously
right and I misread the range. Apologies for the confusion -- I guess I
was too enthusiastic in trying to figure out an easy way out of this :)

> So yes, maybe Tim Allison can help identify which are the required
> commits, but best course might just to try to update to the newest
> upstream version for unstable.

Indeed! (but note that I'm not the maintainer)

Thanks,
Faidon

Bug#887666: jh_linkjars: Invalid option: N

[Adrian Bunk]

Package: debhelper
Version: 11.1.2
Severity: serious
Control: affects -1 javahelper src:zabbix

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

...
   jh_linkjars -O--max-parallel=4 -Nzabbix-frontend-php -Nzabbix-java-gateway
Invalid option: N
Usage: jh_linkjars [options] [target] 
Options:
-h --help: show this text
-V --version: show the version
-v --verbose: show more information while running
-t --transitive: transitively link jars
-n --no-act: don't actually do anything, just print the results
-u --unlink: remove the links instead of adding them
debian/rules:77: recipe for target 'binary' failed
make: *** [binary] Error 1


Works after downgrading to debhelper 11

Processed: jh_linkjars: Invalid option: N

[Debian Bug Tracking System]

Processing control commands:

> affects -1 javahelper src:zabbix
Bug #887666 [debhelper] jh_linkjars: Invalid option: N
Added indication that 887666 affects javahelper and src:zabbix

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

Processed: found 885835 in 7.2+dfsg-1

[Debian Bug Tracking System]

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

> found 885835 7.2+dfsg-1
Bug #885835 [src:awstats] awstats: CVE-2017-1000501: path traversals in config 
and migrate parameter
Marked as found in versions awstats/7.2+dfsg-1.
> thanks
Stopping processing here.

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

Bug#825501: CVE-2016-4434

[Salvatore Bonaccorso]

Hi Faidon,

On Fri, Jan 12, 2018 at 07:54:58PM +0100, Moritz Muehlenhoff wrote:
> On Thu, Jan 11, 2018 at 02:03:23PM +0200, Faidon Liambotis wrote:
> > On Fri, May 27, 2016 at 11:58:33AM +0200, Moritz Muehlenhoff wrote:
> > > please see http://seclists.org/oss-sec/2016/q2/413  for details.
> > 
> > That link says:
> >   Versions Affected: 
> >   Apache Tika 0.10 to 1.12
> > 
> > So perhaps 1.5 isn't affected after all? I tried to find the relevant
> > commit in the upstream git but failed :(
> 
> Commit 
> https://github.com/apache/tika/commit/f444fd784b99b181cd7bd54cdec9fbd132b4ef93
> in 1.17 added a test case, so this might be related to changes in Xerces/J
> which are possibly bundled by Tika downloads? Might be worth clarifying with
> Tim Allison .

Above, you said "so perhaps 1.5 isn't affected after all?". But why
this conclusion? 1.5 as currently in unstable and oldstable present
falls within the affected range of 0.15 and 1.12.

The issue is claimed to be fixed in upstream 1.13 (and as Moritz
pointed out a test was added. Comparing commits between 1.12 and 1.13
I was unable to isolate the relevant commit(s), but there are some
touching the code for "OOXML files and XMP in PDF and other file
formats".

So yes, maybe Tim Allison can help identify which are the required
commits, but best course might just to try to update to the newest
upstream version for unstable.

Regards,
Salvatore

Bug#887664: openal-soft: FTBFS: nothing is built

[Guus Sliepen]

Source: openal-soft
Version: 1:1.18.2-1
Severity: serious
Justification: Policy 4.9

Building openal-soft from source in a pbuilder environment fails. It
seems like it thinks there is nothing to build:

> sudo pbuilder build openal-soft_1.18.2-1.dsc
[...]
I: Running cd /build/openal-soft-1.18.2/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us 
-uc -rfakeroot
dpkg-buildpackage: info: source package openal-soft
dpkg-buildpackage: info: source version 1:1.18.2-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Markus Koschany 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build openal-soft-1.18.2
 fakeroot debian/rules clean
dh clean --builddirectory=/build/openal-soft-1.18.2/build-tree
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/openal-soft-1.18.2'
rm -rf /build/openal-soft-1.18.2/build-tree
make[1]: Leaving directory '/build/openal-soft-1.18.2'
   dh_clean -O--builddirectory=/build/openal-soft-1.18.2/build-tree
 dpkg-source -b openal-soft-1.18.2
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building openal-soft using existing 
./openal-soft_1.18.2.orig.tar.gz
dpkg-source: info: building openal-soft in openal-soft_1.18.2-1.debian.tar.xz
dpkg-source: info: building openal-soft in openal-soft_1.18.2-1.dsc
 debian/rules build
make: Nothing to be done for 'build'.
 fakeroot debian/rules binary
dh binary --builddirectory=/build/openal-soft-1.18.2/build-tree
   debian/rules build
make[1]: Entering directory '/build/openal-soft-1.18.2'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/build/openal-soft-1.18.2'
   dh_testroot -O--builddirectory=/build/openal-soft-1.18.2/build-tree
   dh_prep -O--builddirectory=/build/openal-soft-1.18.2/build-tree
   debian/rules override_dh_auto_install
make[1]: Entering directory '/build/openal-soft-1.18.2'
dh_auto_install
install -d debian/tmp/etc/openal
[...lots of errors about missing files...]
dh_install: libopenal-data missing files: usr/share/openal/hrtf
dh_install: missing files, aborting
debian/rules:34: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
I: copying local configuration
E: Failed autobuilding of package


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

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

Bug#887575: [Pkg-pascal-devel] Bug#887575: Bug#887575: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Michalis Kamburelis]

2018-01-18 20:56 GMT+01:00 Michalis Kamburelis :
> So, we should get to the point where CGE (or any other package
> using fpmake) can be compiled by simple
>
> ~~~
> unset FPCDIR
> fpc fpmake.pp
> ./fpmake # without any additional options like --globalunitdir
> ~~~
>

I created a "simplest possible example of using fpmake", so that you
can test it all without dealing with (unrelated) Castle Game Engine
code and Makefiles:

- Get https://github.com/michaliskambi/simplest-fpmake-test .
- Run "./testme.sh", that just calls "./fpmake".
- I think that we should make it "just work" if user installed FPC
from a Debian package. Without the need to set $FPCDIR, without the
need to pass --globalunitdir .

Right now, it will not work. Right now, you need to use
--globalunitdir pointing to the proper location when invoking fpmake
(see testme.sh comments).

(In the previous FPC versions, setting environment variable FPCDIR was
also enough, without the need for --globalunitdir . It doesn't work
for me now, although I see that the code reading $FPCDIR is in
TFPCDefaults.CompilerDefaults. As far as I observed, this was broken
in FPC 3.x upstream, unrelated to Debian.)

Regards,
Michalis

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 785044 buster sid
Bug #785044 [src:stardict] stardict: Should build-dep on libestools-dev instead 
of libestools2.0-dev
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#887662: gvpe FTBFS with glibc 2.26

[Adrian Bunk]

Source: gvpe
Version: 3.0-1
Severity: serious

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

...
In file included from /usr/include/x86_64-linux-gnu/bits/getopt_posix.h:27:0,
 from /usr/include/unistd.h:872,
 from gvpectrl.C:46:
/usr/include/x86_64-linux-gnu/bits/getopt_core.h:91:12: error: declaration of 
'int getopt(int, char* const*, const char*) throw ()' has a different exception 
specifier
 extern int getopt (int ___argc, char *const *___argv, const char *__shortopts)
^~
In file included from gvpectrl.C:42:0:
../lib/getopt.h:108:12: note: from previous declaration 'int getopt(int, char* 
const*, const char*)'
 extern int getopt (int argc, char *const *argv, const char *shortopts);
^~

Processed: tagging 887330

[Debian Bug Tracking System]

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

> tags 887330 + upstream fixed-upstream
Bug #887330 [src:civicrm] civicrm: Multiple XSS vulnerabilities were found in 
CiviCRM <4.7.26
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#887558: marked as done (wine-development FTBFS on armel: selected processor does not support `strd r4,[sp]' in ARM mode)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 21:00:42 +
with message-id 
and subject line Bug#887558: fixed in wine-development 3.0~rc5-1
has caused the Debian Bug report #887558,
regarding wine-development FTBFS on armel: selected processor does not support 
`strd r4,[sp]' in ARM mode
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.)


-- 
887558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine-development
Version: 3.0~rc3-2
Severity: serious
Forwarded: https://bugs.winehq.org/show_bug.cgi?id=44365
Tags: upstream


gcc -c -o relay.o relay.c -I. -I../../include -D__WINESRC__ -D_NTSYSTEM_
-D_REENTRANT -fPIC -Wall \
  -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers \
  -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes
-Wtype-limits \
  -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith
-Wlogical-op -gdwarf-2 \
  -gstrict-dwarf -Werror -Wdate-time -g -O2
-fdebug-prefix-map=/<>=.
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong
-Wformat -Werror=format-security -march=armv5t -Wno-error -marm
-mfloat-abi=soft
[...]
{standard input}: Assembler messages:
{standard input}:51: Error: selected processor does not support `strd
r4,[sp]' in ARM mode
Makefile:521: recipe for target 'relay.o' failed
make[2]: *** [relay.o] Error 1
make[2]: Leaving directory '/<>/dlls/ntdll'
Makefile:13147: recipe for target 'dlls/ntdll' failed
make[1]: *** [dlls/ntdll] Error 2


I hope upstream fixes this soon.  Otherwise we'd have to remove armel
from the architecture list and file an RM bug against ftp.debian.org for
removal of the stale old armel packages (advice copied from #881446).

Previously I had mistaken a change in 3.0-rc3 to fix this, therefore the
wrong changelog entry in that version.

Greets
jre
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 3.0~rc5-1

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

Debian distribution maintenance software
pp.
Jens Reyer  (supplier of updated wine-development 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 18 Jan 2018 17:38:02 +0100
Source: wine-development
Binary: wine-development wine32-development wine64-development 
wine32-development-preloader wine64-development-preloader 
wine32-development-tools wine64-development-tools libwine-development 
libwine-development-dev
Architecture: source
Version: 3.0~rc5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Jens Reyer 
Description:
 libwine-development - Windows API implementation - library
 libwine-development-dev - Windows API implementation - development files
 wine-development - Windows API implementation - standard suite
 wine32-development - Windows API implementation - 32-bit binary loader
 wine32-development-preloader - Windows API implementation - prelinked 32-bit 
binary loader
 wine32-development-tools - Windows API implementation - 32-bit developer tools
 wine64-development - Windows API implementation - 64-bit binary loader
 wine64-development-preloader - Windows API implementation - prelinked 64-bit 
binary loader
 wine64-development-tools - Windows API implementation - 64-bit developer tools
Closes: 887558
Changes:
 wine-development (3.0~rc5-1) unstable; urgency=medium
 .
   * New upstream release 3.0-rc5, released Jan 5, 2018.
 - Bug fixes only, we are in code freeze.
   * Update copyright years.
   * Add patch by upstream to fix armel build failure (closes: #887558).
Checksums-Sha1:
 49c20ab57d37df344319d0e61f9217b6d9785047 4016 wine-development_3.0~rc5-1.dsc
 a7bddf1e3268e1a7319ed69aa6c82f07a978b8cc 19767752 
wine-development_3.0~rc5.orig.tar.xz
 4d7632183b0fe7fc6e433ae698603177d2bbf7f2 180920 
wine-development_3.0~rc5-1.debian.tar.xz
 

Bug#875929: marked as done (acetoneiso: should it be removed from Debian)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 20:50:15 +
with message-id 
and subject line Bug#875929: fixed in acetoneiso 2.4-3
has caused the Debian Bug report #875929,
regarding acetoneiso: should it be removed from Debian
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.)


-- 
875929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acetoneiso
Version: 2.4-2
Severity: serious

Hi,

this package has long standing RC bugs (even if only recently rised to
RC level), without any input from the maintainer for years.
Also, it hasn't seen an upload in the last 3 years, that —whilst being
no indicator as is— feels kind of strange for an application aiming at
dealing with CD stuff.

I belive the best course of action would be to remove the package from
the archive, and I'll ask ftp-masters to do as such in the next few
weeks.

If you disagree with me, please take action to fix the outstanding bugs,
and closing this one.

-- 
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: acetoneiso
Source-Version: 2.4-3

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

Debian distribution maintenance software
pp.
Nick Andrik  (supplier of updated acetoneiso 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: Sat, 25 Nov 2017 21:14:29 +0100
Source: acetoneiso
Binary: acetoneiso
Architecture: source
Version: 2.4-3
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: Nick Andrik 
Description:
 acetoneiso - feature-rich application to mount and manage CD and DVD images
Closes: 609526 784449 874814 875929
Changes:
 acetoneiso (2.4-3) unstable; urgency=medium
 .
   * Port code to Qt 5 (Closes: #784449, #875929, #874814)
   * Internationalization
 - d/p/update_forms: Cleanup of translatable strings for UI forms
 - Update po translation files
 - Update translations from Launchpad (2017-03-22)
   + Updated English (United Kingdom)
   + Updated Polish
   + Updated Russian
   + Updated Ukrainian
   + Added Indonesian
   + Added Japanese
   + Added Norwegian Nynorsk
   + Added Occitan (post 1500)
   + Added Serbian
   * Dependency cleanup of external programs
 - Move general CD/DVD handling related packages to Recommends
 - Move extra format related packages to Suggests
 - d/p/youtube_dl_system: Try to use system wide youtube-dl
 - d/p/replace_poweriso: Do not automatically download and install
   PowerISO (Closes: #609526)
   * d/p/add_desktop_keywords: Add Keywords entry for provided .desktop file
   * General package maintenance
 - Add d/source/options to exclude non-release files
 - Bump standards version to 4.1.1
 - Use secure URLs for d/watch
 - Update lintian overrides
Checksums-Sha1:
 a9151a9618394deee30a6a67d7acecbfc00e8f74 1852 acetoneiso_2.4-3.dsc
 eb8bb0eed90a58266f47e2dfb9b0015a6cb95463 243956 acetoneiso_2.4-3.debian.tar.xz
 1ed42b3fbfffc6c78220bb449f80e4d2645213e4 10980 acetoneiso_2.4-3_amd64.buildinfo
Checksums-Sha256:
 34048d2976e325a9fbac84a8f61ee7d4af81dcacd6180578be082d69d2ee7b49 1852 
acetoneiso_2.4-3.dsc
 d460d370bb2ba0243cc4c194d453f271c5f6620154e4bc974b099024dabe5b64 243956 
acetoneiso_2.4-3.debian.tar.xz
 84a542a76f1dfb036b9201e9d150ee972af36591384769247f8f81a26a5a8b51 10980 
acetoneiso_2.4-3_amd64.buildinfo
Files:
 eb30c0f5927c75ec190483aa3f22582f 1852 otherosfs optional acetoneiso_2.4-3.dsc
 37f6ff4c9486c7f5e28364029dbd0f2c 243956 otherosfs optional 

Bug#609526: marked as done (Please avoid resorting to poweriso, prefer daa2iso instead)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 20:50:15 +
with message-id 
and subject line Bug#609526: fixed in acetoneiso 2.4-3
has caused the Debian Bug report #609526,
regarding Please avoid resorting to poweriso, prefer daa2iso instead
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.)


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

Hi,
I've recently noticed that acetoneiso is currently suggesting,
downloading and installing poweriso (under my home directory),
in order to handle DAA files.

This seems quite an unfortunate choice for a free software program,
in particular when free alternative exist and are already packaged in
Debian. See in particular the daa2iso package, which does exactly that.

Note that this may also be in violation of policy §2.2.1, as
"wrapper packages or other sorts of free accessories for non-free programs"
are better suited for contrib section, not main (but the categorization here
is not so clear, so I'm not raising the severity).

As such, please consider switching ASAP to daa2iso, and suggest upstream to do
the same avoiding poweriso.

Cheers, Luca



-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages acetoneiso depends on:
ii  cdrdao  1:1.2.3-0.1  records CDs in Disk-At-Once (DAO) 
ii  fuse-utils  2.8.4-1.1Filesystem in USErspace (utilities
ii  fuseiso 20070708-2   FUSE module to mount ISO filesyste
ii  genisoimage 9:1.1.11-1   Creates ISO-9660 CD-ROM filesystem
ii  gnupg-agent 2.0.14-2 GNU privacy guard - password agent
ii  gnupg2  2.0.14-2 GNU privacy guard - a free PGP rep
ii  libc6   2.11.2-7 Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.5-20100227-1 GCC support library
ii  libphonon4  4:4.6.0really4.4.2-1 the core library of the Phonon mul
ii  libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module
ii  libqt4-webkit   4:4.6.3-4Qt 4 WebKit module
ii  libqtcore4  4:4.6.3-4Qt 4 core module
ii  libqtgui4   4:4.6.3-4Qt 4 GUI module
ii  libstdc++6  4.5-20100227-1   The GNU Standard C++ Library v3
ii  p7zip-full  9.04~dfsg.1-17z and 7za file archivers with hig
ii  phonon  4:4.6.0really4.4.2-1 metapackage for the Phonon multime
ii  pinentry-qt40.8.0-1  Qt-4-based PIN or pass-phrase entr

acetoneiso recommends no packages.

Versions of packages acetoneiso suggests:
ii  mencoder  2:1.0~rc3++svn20100804-0.1 MPlayer's Movie Encoder
ii  nautilus  2.30.1-2   file manager and graphical shell f

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: acetoneiso
Source-Version: 2.4-3

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

Debian distribution maintenance software
pp.
Nick Andrik  (supplier of updated acetoneiso 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: Sat, 25 Nov 2017 21:14:29 +0100
Source: acetoneiso
Binary: acetoneiso
Architecture: source
Version: 2.4-3
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: Nick Andrik 
Description:
 acetoneiso - feature-rich application to mount and manage CD and DVD images
Closes: 609526 784449 874814 875929
Changes:
 acetoneiso (2.4-3) unstable; urgency=medium
 .
   * Port code to Qt 5 (Closes: #784449, #875929, #874814)
   * Internationalization
 - 

Bug#784449: marked as done ([acetoneiso] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 20:50:15 +
with message-id 
and subject line Bug#784449: fixed in acetoneiso 2.4-3
has caused the Debian Bug report #784449,
regarding [acetoneiso] Qt4's WebKit removal
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.)


-- 
784449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acetoneiso
Version: 2.4-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Nick Andrik ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: acetoneiso
Source-Version: 2.4-3

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

Debian distribution maintenance software
pp.
Nick Andrik  (supplier of updated acetoneiso 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: Sat, 25 Nov 2017 21:14:29 +0100
Source: acetoneiso
Binary: acetoneiso
Architecture: source
Version: 2.4-3
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: Nick Andrik 
Description:
 acetoneiso - feature-rich application to mount and manage CD and DVD images
Closes: 609526 784449 874814 875929
Changes:
 acetoneiso (2.4-3) unstable; urgency=medium
 .
   * Port code to Qt 5 (Closes: #784449, #875929, #874814)
   * Internationalization
 - d/p/update_forms: Cleanup of translatable strings for UI forms
 - Update po translation files
 - Update translations from Launchpad (2017-03-22)
   + Updated English (United Kingdom)
   + Updated Polish
   + Updated Russian
   + Updated Ukrainian
   + Added Indonesian
   + Added Japanese
   + Added Norwegian Nynorsk
   + Added Occitan (post 1500)
   + Added Serbian
   * Dependency cleanup of external programs
 - Move general CD/DVD handling related packages to Recommends
 - Move extra format related packages to Suggests
 - d/p/youtube_dl_system: Try to use system wide youtube-dl
 - d/p/replace_poweriso: Do not automatically download and install
   PowerISO (Closes: #609526)
   * d/p/add_desktop_keywords: Add Keywords entry for provided .desktop 

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Aurelien Jarno]

On 2018-01-18 20:38, Julian Andres Klode wrote:
> On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote:
> > control: reassign -1 apt,dpkg
> > control: affects -1 libc6
> > control: affects -1 libexpat1
> > 
> > On 2018-01-18 15:53, Andreas Beckmann wrote:
> > > Package: libc6
> > > Version: 2.26-2
> > > Severity: serious
> > > User: debian...@lists.debian.org
> > > Usertags: piuparts
> > > 
> > > Hi,
> > > 
> > > during a test with piuparts I noticed your package fails to upgrade from
> > > 'stretch'.
> > > It installed fine in 'stretch', then the upgrade to 'buster' fails.
> > > 
> > > >From the attached log (scroll to the bottom...):
> > > 
> > > [...]
> > >   Preparing to unpack .../libexpat1-dev_2.2.5-3_i386.deb ...
> > >   Unpacking libexpat1-dev:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
> > >   Preparing to unpack .../libexpat1_2.2.5-3_i386.deb ...
> > >   Unpacking libexpat1:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
> > 
> > $ apt-cache show libexpat1
> > Package: libexpat1
> > Source: expat
> > Version: 2.2.5-3
> > Installed-Size: 429
> > Maintainer: Laszlo Boszormenyi (GCS) 
> > Architecture: i386
> > Depends: libc6 (>= 2.25)
> > 
> > So libexpat1 correctly depends on libc6 (>= 2.25), which is not
> > even unpacked at that point.
> > 
> > > [...]
> > >   Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
> > >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> > > not found (required by /lib/i386-linux-gnu/libexpat.so.1)
> > >   dpkg: warning: subprocess old pre-removal script returned error exit 
> > > status 1
> > >   dpkg: trying script from the new package instead ...
> > >   dpkg: error processing archive 
> > > /tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb 
> > > (--unpack):
> > >there is no script in the new version of the package - giving up
> > >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> > > not found (required by /lib/i386-linux-gnu/libexpat.so.1)
> > 
> > This failure is normal given libexpat1 requires the new libc which has
> > not been unpacked yet.
> 
> Yeah, well, it needs to Pre-Depend on it then I guess, if it's being used
> in preinst actions. The thing is that Depends only after postinst ordering,
> not unpack ordering.

Well it's not the preinst script, but the prerm script. The problem is
unpacking libexpat1 before libc6 breaks libexpat1 and not usable
anymore.

From what I understand from the debian-policy, a prerm script might
consider that all the dependencies have been at least unpacked when
called:

| "The package whose prerm is being called will be at least
| “Half-Installed”. All package dependencies will at least be
| “Half-Installed” and will have previously been configured and not
| removed. If there was no error, all dependencies will at least be
| “Unpacked”, but these actions may be called in various error
| states where dependencies are only “Half-Installed” due to a
| partial upgrade.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#887655: mariadb-10.1: FTBFS with liblz4-dev installed

[Daniel Schepler]

Source: mariadb-10.1
Version: 1:10.1.29-6
Severity: serious

>From my pbuilder build log:

...
-- Looking for compress in z
-- Looking for compress in z - found
-- Checking for module 'liblz4'
--   Found liblz4, version 131
-- Checking for module 'kytea'
--   No package 'kytea' found
...
CMake Error: The following variables are used in this project, but
they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
LZ4_LIBS
linked by target "libgroonga" in directory
/home/daniel/src/debian/mariadb-10.1/mariadb-10.1-10.1.29/storage/mroonga/vendor/groonga/lib

-- Configuring incomplete, errors occured!
See also 
"/home/daniel/src/debian/mariadb-10.1/mariadb-10.1-10.1.29/builddir/CMakeFiles/CMakeOutput.log".
See also 
"/home/daniel/src/debian/mariadb-10.1/mariadb-10.1-10.1.29/builddir/CMakeFiles/CMakeError.log".
debian/rules:73: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory
'/home/daniel/src/debian/mariadb-10.1/mariadb-10.1-10.1.29'
debian/rules:177: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Removing liblz4-dev seems to work around the issue.
-- 
Daniel Schepler

Processed: Re: stardict: Should build-dep on libestools-dev instead of libestools2.0-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #785044 [src:stardict] stardict: Should build-dep on libestools-dev instead 
of libestools2.0-dev
Severity set to 'serious' from 'normal'

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

Bug#887575: [Pkg-pascal-devel] Bug#887575: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Michalis Kamburelis]

2018-01-18 14:44 GMT+01:00 Abou Al Montacir :
> Doing
>
>   ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
>
> Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we
> need to explicitly pass this?
>

Hi Abou,

I think you're very right here -- the option "--globalunitdir XXX"
should not be needed at all. Specifying $FPCDIR / --globalunitdir
should only be necessary when the FPC is installed in some custom,
user-owned location. But when the FPC is installed system-wide (like
from a Debian package), then nothing (including CGE build script)
should need to define $FPCDIR or use "--globalunitdir" anymore -- it
should be picked up by the fpmake system automatically. That's how it
should work in the upstream FPC, and I know there's an auto-detection
in fpmkunit for these paths. So, it would be best to fix this issue,
by fixing that auto-detection mechanism.

To be clear: It's not just a matter of having correct /etc/fpc.cfg --
the fpmake also needs to know the root location of FPC units. (You
would have to ask fpmake authors why they did it like this.) But that
is why we have this complication with $FPCDIR or --globalunitdir or
auto-detecting it.

So, we should get to the point where CGE (or any other package
using fpmake) can be compiled by simple

~~~
unset FPCDIR
fpc fpmake.pp
./fpmake # without any additional options like --globalunitdir
~~~

Looking in the FPC sources, the auto-detection is inside
packages/fpmkunit/src/fpmkunit.pp , in TFPCDefaults.CompilerDefaults ,
I'm quoting the relevant lines below. So, someone should adjust it (in
Debian package) to follow the Debian path conventions :)

That's a much better solution than both of my previous suggestions -- thanks!

~~~
procedure TFPCDefaults.CompilerDefaults;
var
  BD : String;
begin
  inherited CompilerDefaults;

  // Use the same algorithm as the compiler, see options.pas
{$ifdef Unix}
  BD:=FixPath(GetEnvironmentVariable('FPCDIR'), False);
  if BD='' then
begin
  BD:='/usr/local/lib/fpc/'+FCompilerVersion;
  if not DirectoryExists(BD) and
 DirectoryExists('/usr/lib/fpc/'+FCompilerVersion) then
BD:='/usr/lib/fpc/'+FCompilerVersion;
end;
{$else unix}
...
~~~

Regards,
Michalis

Processed: tagging 887488

[Debian Bug Tracking System]

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

> tags 887488 + upstream security
Bug #887488 {Done: Jonathan McDowell } [openocd] openocd: 
CVE-2018-5704 cross protocol scripting attack
Added tag(s) upstream and security.
> thanks
Stopping processing here.

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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Julian Andres Klode]

On Thu, Jan 18, 2018 at 08:38:02PM +0100, Julian Andres Klode wrote:
> On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote:
> > control: reassign -1 apt,dpkg
> > control: affects -1 libc6
> > control: affects -1 libexpat1
> > 
> > On 2018-01-18 15:53, Andreas Beckmann wrote:
> > > Package: libc6
> > > Version: 2.26-2
> > > Severity: serious
> > > User: debian...@lists.debian.org
> > > Usertags: piuparts
> > > 
> > > Hi,
> > > 
> > > during a test with piuparts I noticed your package fails to upgrade from
> > > 'stretch'.
> > > It installed fine in 'stretch', then the upgrade to 'buster' fails.
> > > 
> > > >From the attached log (scroll to the bottom...):
> > > 
> > > [...]
> > >   Preparing to unpack .../libexpat1-dev_2.2.5-3_i386.deb ...
> > >   Unpacking libexpat1-dev:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
> > >   Preparing to unpack .../libexpat1_2.2.5-3_i386.deb ...
> > >   Unpacking libexpat1:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
> > 
> > $ apt-cache show libexpat1
> > Package: libexpat1
> > Source: expat
> > Version: 2.2.5-3
> > Installed-Size: 429
> > Maintainer: Laszlo Boszormenyi (GCS) 
> > Architecture: i386
> > Depends: libc6 (>= 2.25)
> > 
> > So libexpat1 correctly depends on libc6 (>= 2.25), which is not
> > even unpacked at that point.
> > 
> > > [...]
> > >   Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
> > >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> > > not found (required by /lib/i386-linux-gnu/libexpat.so.1)
> > >   dpkg: warning: subprocess old pre-removal script returned error exit 
> > > status 1
> > >   dpkg: trying script from the new package instead ...
> > >   dpkg: error processing archive 
> > > /tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb 
> > > (--unpack):
> > >there is no script in the new version of the package - giving up
> > >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' 
> > > not found (required by /lib/i386-linux-gnu/libexpat.so.1)
> > 
> > This failure is normal given libexpat1 requires the new libc which has
> > not been unpacked yet.
> 
> Yeah, well, it needs to Pre-Depend on it then I guess, if it's being used
> in preinst actions. The thing is that Depends only after postinst ordering,
> not unpack ordering.
> 

To be more precise: I guess libglib2.0-dev needs to predepend on python3 or on
libexpat1.

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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Julian Andres Klode]

On Thu, Jan 18, 2018 at 06:41:52PM +0100, Aurelien Jarno wrote:
> control: reassign -1 apt,dpkg
> control: affects -1 libc6
> control: affects -1 libexpat1
> 
> On 2018-01-18 15:53, Andreas Beckmann wrote:
> > Package: libc6
> > Version: 2.26-2
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> > 
> > Hi,
> > 
> > during a test with piuparts I noticed your package fails to upgrade from
> > 'stretch'.
> > It installed fine in 'stretch', then the upgrade to 'buster' fails.
> > 
> > >From the attached log (scroll to the bottom...):
> > 
> > [...]
> >   Preparing to unpack .../libexpat1-dev_2.2.5-3_i386.deb ...
> >   Unpacking libexpat1-dev:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
> >   Preparing to unpack .../libexpat1_2.2.5-3_i386.deb ...
> >   Unpacking libexpat1:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
> 
> $ apt-cache show libexpat1
> Package: libexpat1
> Source: expat
> Version: 2.2.5-3
> Installed-Size: 429
> Maintainer: Laszlo Boszormenyi (GCS) 
> Architecture: i386
> Depends: libc6 (>= 2.25)
> 
> So libexpat1 correctly depends on libc6 (>= 2.25), which is not
> even unpacked at that point.
> 
> > [...]
> >   Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
> >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' not 
> > found (required by /lib/i386-linux-gnu/libexpat.so.1)
> >   dpkg: warning: subprocess old pre-removal script returned error exit 
> > status 1
> >   dpkg: trying script from the new package instead ...
> >   dpkg: error processing archive 
> > /tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb (--unpack):
> >there is no script in the new version of the package - giving up
> >   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' not 
> > found (required by /lib/i386-linux-gnu/libexpat.so.1)
> 
> This failure is normal given libexpat1 requires the new libc which has
> not been unpacked yet.

Yeah, well, it needs to Pre-Depend on it then I guess, if it's being used
in preinst actions. The thing is that Depends only after postinst ordering,
not unpack ordering.

> 
> >   dpkg: error while cleaning up:
> >subprocess installed post-installation script returned error exit status 
> > 1
> > [...]
> >   Preparing to unpack .../9-libc6_2.26-2_i386.deb ...
> >   Unpacking libc6:i386 (2.26-2) over (2.24-11+deb9u1) ...
> >   Errors were encountered while processing:
> >/tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb
> 
> And libc6 2.26-2 is only unpacked afterwards.

does not matter.

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

Bug#887488: marked as done (openocd: CVE-2018-5704 cross protocol scripting attack)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 19:35:15 +
with message-id 
and subject line Bug#887488: fixed in openocd 0.10.0-4
has caused the Debian Bug report #887488,
regarding openocd: CVE-2018-5704 cross protocol scripting attack
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.)


-- 
887488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openocd
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: important

Hi,

the following vulnerability was published for openocd.

CVE-2018-5704[0]:
| Open On-Chip Debugger (OpenOCD) 0.10.0 does not block attempts to use
| HTTP POST for sending data to 127.0.0.1 port , which allows remote
| attackers to conduct cross-protocol scripting attacks, and consequently
| execute arbitrary commands, via a crafted web site.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-5704
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5704

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: openocd
Source-Version: 0.10.0-4

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated openocd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 18 Jan 2018 19:19:47 +
Source: openocd
Binary: openocd
Architecture: source amd64
Version: 0.10.0-4
Distribution: sid
Urgency: high
Maintainer: Debian Electronics Packaging Team 

Changed-By: Jonathan McDowell 
Description:
 openocd- Open on-chip JTAG debug solution for ARM and MIPS systems
Closes: 887488
Changes:
 openocd (0.10.0-4) unstable; urgency=high
 .
   * Bind to localhost by default
   * Prevent some forms of Cross Protocol Scripting attacks (CVE-2018-5704)
 (Closes: #887488)
Checksums-Sha1:
 14a425a8cb92ed3f2ba08d31c086ac3f402b124e 2063 openocd_0.10.0-4.dsc
 9cf3862782d6102db455c52ff146d337fb6a6e9e 19808 openocd_0.10.0-4.debian.tar.xz
 a84a2a9bd3c66772632ce86a9bf169737256d122 2855268 
openocd-dbgsym_0.10.0-4_amd64.deb
 dab3d3b0a2e1bfaa0fd434dabd3b90de4fe26353 8720 openocd_0.10.0-4_amd64.buildinfo
 c779841a48bbf6739d8a06e39f6e4247c80433eb 2454552 openocd_0.10.0-4_amd64.deb
Checksums-Sha256:
 3c21fb8da7fdf9785926697908bd5074932fe4f69e030b41aca59880784848bd 2063 
openocd_0.10.0-4.dsc
 e2fd7be99a0a8ccc1444cf90562bcdfead3056b03132d9ebd84e1b80832800d5 19808 
openocd_0.10.0-4.debian.tar.xz
 7617ebbf547e3b26a1e7bbbccec3911f634345731cd6a0555dac1ae3db4c2696 2855268 
openocd-dbgsym_0.10.0-4_amd64.deb
 994a3e826ec27407350f51ce0973a34e1b6d9f68cff2eb629aedcb18ea0b066f 8720 
openocd_0.10.0-4_amd64.buildinfo
 00f03d246087d24ccc5c24bebd8d50a397b798463fa092ed55d08597e7d2943d 2454552 
openocd_0.10.0-4_amd64.deb
Files:
 e82243fa3300f67b263d56eef323b001 2063 embedded optional openocd_0.10.0-4.dsc
 377009b0326b627b61ece1a226030bea 19808 embedded optional 
openocd_0.10.0-4.debian.tar.xz
 48302ac2cc0d44e324a8dbba8e393ea4 2855268 debug optional 
openocd-dbgsym_0.10.0-4_amd64.deb
 a432ddc826d3d7949a49c50e517b5777 8720 embedded optional 
openocd_0.10.0-4_amd64.buildinfo
 15f2fc24c1e3fc4e7f88054c55c8a422 2454552 embedded optional 
openocd_0.10.0-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERUuPEyEc/2gMWDpQ/xYvxc8/utEFAlpg9MYACgkQ/xYvxc8/
utGsNA/+O9PCQQqjwPoNIaZS52kBrjYHf9RZodg/y9C6bJ+F0J0WPCgWn4TKdX4o
Xsr1uu8nmHViGC4gj5l4DLa8C1/5ZohBccKVfNyAL5Z/rsHofWTPulxraQ8nWJIU
/lk9CByPxqJLfUVMZYwfjGhWmRvb3yJ989yIuP0VEmTn4letyxkl+vB9jTcrea9k
fG6OcA2mm6H5KkROKiOJsqFDW3hrH9jUfutLz2t/Dac7j+pQJCVqR/EMj++wbvCa
hkEjqGUhM66grgz8Y1YKAbUmkxWNLGsBsL2OISho37FER4vjNJ6s/FpTDJvZrSqa

Processed: Re: Processed (with 1 error): Re: [Pkg-pascal-devel] Processed (with 1 error): Re: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Debian Bug Tracking System]

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

> # Last try
> reassign  887652 src:fpc
Bug #887652 [src:castle-game-engine] fpc MA setup breaks some reverse 
dependency builds
Bug reassigned from package 'src:castle-game-engine' to 'src:fpc'.
No longer marked as found in versions castle-game-engine/3.0.4+dfsg-13 and 
castle-game-engine/6.2+dfsg1-1.
Ignoring request to alter fixed versions of bug #887652 to the same values 
previously set
> found 887652 3.0.4+dfsg-13
Bug #887652 [src:fpc] fpc MA setup breaks some reverse dependency builds
Marked as found in versions fpc/3.0.4+dfsg-13.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: [Pkg-pascal-devel] Processed (with 1 error): Re: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Debian Bug Tracking System]

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

> # oops
> reassing 887652 src:fpc
Unknown command or malformed arguments to command.
> found 887652 3.0.4+dfsg-13
Bug #887652 [src:castle-game-engine] fpc MA setup breaks some reverse 
dependency builds
The source 'castle-game-engine' and version '3.0.4+dfsg-13' do not appear to 
match any binary packages
Ignoring request to alter found versions of bug #887652 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 877918, affects 877918

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 877918 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 877918 + live-task-gnome
Bug #877918 [uim] uim: circular dependency hell
Added indication that 877918 affects live-task-gnome
> thanks
Stopping processing here.

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

Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Paul Gevers]

clone 887575 -1
assign -1 src:fpc
retitle -1 fpc MA setup breaks some reverse dependency builds
found -1 3.0.4+dfsg-13
block 887575 by -1
thanks

Hi

On 18-01-18 14:44, Abou Al Montacir wrote:
> On Thu, 2018-01-18 at 06:43 +0100, Michalis Kamburelis wrote:
>> The problem is caused by the different directories used by new FPC
>> 3.0.4 packages (compared to previous versions of FPC in Debian).
> I must admit that I was expecting many packages to break as the change
> is too big.
> But I assume this is worth the pain as now we can install multiple
> architecture units on the same host.

But I think this must be fixed in fpc (therefore the clone of the bug),
not in all the packages that build using it.

>> Doing
>>
>>   ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
> Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do
> we need to explicitly pass this?
>> doesn't work, since /usr/lib/fpc/3.0.4 does not exist. This works:
>>
>>   ./fpmake --globalunitdir="/usr/lib/x86_64-linux-gnu/fpc/3.0.4"
> I would use
> 
> DEB_HOST_MULTIARCH=$(dpkg-architecture -qDEB_HOST_MULTIARCH)

So, /etc/fpc.cfg should be fixed, no? Can that be done in a MA manner?
If not, I consider the whole fpc/MA design broken.

>> To fix this, I suggest to
>>
>> - Change / define the $FPCDIR variable inside Debian build scripts, to
>> point to the new correct directory.
> I would try to avoid this if possible but indeed seems correct solution

I disagree. I think a solution where every package needs to define this
is wrong.

>> - Or create a symlink /usr/lib/fpc/3.0.4 ->
>> /usr/lib/x86_64-linux-gnu/fpc/3.0.4 .
> This brings us back to pre-MA epoch. Let's avoid it. Also not possible
> in the Debian auto-builder daemon.

The first sentence is what I also thought, but what do you mean by the last?

Paul



signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): Re: Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Debian Bug Tracking System]

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

> clone 887575 -1
Bug #887575 [src:castle-game-engine] castle-game-engine FTBFS with fpc 3.0.4
Bug 887575 cloned as bug 887652
> assign -1 src:fpc
Unknown command or malformed arguments to command.
> retitle -1 fpc MA setup breaks some reverse dependency builds
Bug #887652 [src:castle-game-engine] castle-game-engine FTBFS with fpc 3.0.4
Changed Bug title to 'fpc MA setup breaks some reverse dependency builds' from 
'castle-game-engine FTBFS with fpc 3.0.4'.
> found -1 3.0.4+dfsg-13
Bug #887652 [src:castle-game-engine] fpc MA setup breaks some reverse 
dependency builds
The source 'castle-game-engine' and version '3.0.4+dfsg-13' do not appear to 
match any binary packages
Marked as found in versions castle-game-engine/3.0.4+dfsg-13.
> block 887575 by -1
Bug #887575 [src:castle-game-engine] castle-game-engine FTBFS with fpc 3.0.4
887575 was not blocked by any bugs.
887575 was not blocking any bugs.
Added blocking bug(s) of 887575: 887652
> thanks
Stopping processing here.

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

Processed: Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 apt,dpkg
Bug #887629 [libc6] libc6: bad upgrade path: libexpat1 unpacked and python3 
called before libc6 unpacked
Bug reassigned from package 'libc6' to 'apt,dpkg'.
No longer marked as found in versions glibc/2.26-2.
Ignoring request to alter fixed versions of bug #887629 to the same values 
previously set
> affects -1 libc6
Bug #887629 [apt,dpkg] libc6: bad upgrade path: libexpat1 unpacked and python3 
called before libc6 unpacked
Added indication that 887629 affects libc6
> affects -1 libexpat1
Bug #887629 [apt,dpkg] libc6: bad upgrade path: libexpat1 unpacked and python3 
called before libc6 unpacked
Added indication that 887629 affects libexpat1

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

Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

[Aurelien Jarno]

control: reassign -1 apt,dpkg
control: affects -1 libc6
control: affects -1 libexpat1

On 2018-01-18 15:53, Andreas Beckmann wrote:
> Package: libc6
> Version: 2.26-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails.
> 
> >From the attached log (scroll to the bottom...):
> 
> [...]
>   Preparing to unpack .../libexpat1-dev_2.2.5-3_i386.deb ...
>   Unpacking libexpat1-dev:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...
>   Preparing to unpack .../libexpat1_2.2.5-3_i386.deb ...
>   Unpacking libexpat1:i386 (2.2.5-3) over (2.2.0-2+deb9u1) ...

$ apt-cache show libexpat1
Package: libexpat1
Source: expat
Version: 2.2.5-3
Installed-Size: 429
Maintainer: Laszlo Boszormenyi (GCS) 
Architecture: i386
Depends: libc6 (>= 2.25)

So libexpat1 correctly depends on libc6 (>= 2.25), which is not
even unpacked at that point.

> [...]
>   Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ...
>   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' not 
> found (required by /lib/i386-linux-gnu/libexpat.so.1)
>   dpkg: warning: subprocess old pre-removal script returned error exit status 
> 1
>   dpkg: trying script from the new package instead ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb (--unpack):
>there is no script in the new version of the package - giving up
>   /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' not 
> found (required by /lib/i386-linux-gnu/libexpat.so.1)

This failure is normal given libexpat1 requires the new libc which has
not been unpacked yet.

>   dpkg: error while cleaning up:
>subprocess installed post-installation script returned error exit status 1
> [...]
>   Preparing to unpack .../9-libc6_2.26-2_i386.deb ...
>   Unpacking libc6:i386 (2.26-2) over (2.24-11+deb9u1) ...
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-wfemKS/3-libglib2.0-dev_2.54.3-1_i386.deb

And libc6 2.26-2 is only unpacked afterwards.

> This was a test in an i386 chroot with --install-recommends enabled,
> the package tested was multimedia-devel.
> Note that this runs with apt from stretch since this is an upgrade test ...
> 
> Something (I don't know what) probably needs to get stricter dependencies.

I disagree. The dependencies of libexpat1 are correct, libexpat1 needs a
new libc6 and correctly depends on it. Therefore it's not a bug of libc6
nor libexpat1. It looks to me like a bug in apt or dpkg. I am therefore
reassigning the bug to these packages, so the maintainers can have a
look at the issue.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

[Jeremy Bicha]

Package: cdebconf-gtk-terminal
Version: 0.31
Severity: serious
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte

cdebconf-gtk-terminal Depends and Build-Depends on vte. In fact, it's
now the only package keeping vte in Debian Testing. The Debian GNOME
team does not intend to release Debian 10 "Buster" with vte since the
old 0.28 series has not had a release since GNOME3's release in 2011.

Please port to the vte2.91 source. That also means porting to gtk3.
gtk3 was declared stable over a year ago with the 3.22 series. (There
also have not been any gtk2 maintenance releases
since that time, although I guess someone will do a gtk2 maintenance
release eventually this year.)

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#887648: xview FTBFS with glibc 2.26

[Adrian Bunk]

Source: xview
Version: 3.2p1.4-28.2
Severity: serious

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

...
filter.c: In function 'xv_free_filter_table':
filter.c:205:2: warning: implicit declaration of function 'cfree'; did you mean 
'free'? [-Wimplicit-function-declaration]
  cfree((char *) table[i]->call);
  ^
  free
...
gcc -o clock -g -O2 -fno-strict-aliasing 
-L/build/1st/xview-3.2p1.4/lib/libolgx -L/build/1st/xview-3.2p1.4/lib/libxview  
-L/usr/lib   clock.o -L/usr/lib -lxview -L/usr/lib -lolgx -lXext  -lX11-lm  
  
/build/1st/xview-3.2p1.4/lib/libxview/libxview.so: undefined reference to 
`cfree'
collect2: error: ld returned 1 exit status
Makefile:1178: recipe for target 'clock' failed
make[4]: *** [clock] Error 1

Processed: The new pyasn1 is now in usntable

[Debian Bug Tracking System]

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

> severity 886115 serious
Bug #886115 [python-keyczar] python-keyczar: FTBFS with new pyasn1
Severity set to 'serious' from 'important'
> tags 886115 buster sid
Bug #886115 [python-keyczar] python-keyczar: FTBFS with new pyasn1
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 887633

[Debian Bug Tracking System]

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

> # Does not affect Stretch
> tags 887633 + sid buster
Bug #887633 [src:xymon] xymon FTBFS with glibc 2.26
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#887646: spass FTBFS with glibc 2.26

[Adrian Bunk]

Source: spass
Version: 3.7-4
Severity: serious
Tags: buster sid

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

...
In file included from ./SPASS/strings.h:49:0,
 from /usr/include/string.h:431,
 from SPASS/misc.h:52,
 from SPASS/memory.h:49,
 from SPASS/description.h:27,
 from SPASS/description.c:21:
./SPASS/list.h:57:3: error: unknown type name 'POINTER'
   POINTER   car;
   ^~~


The root problem is that SPASS/strings.h gets included
instead of /usr/include/strings.h.

Bug#886476: marked as done (caja-seahorse: Depends on deprecated libgnome-keyring)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 16:20:23 +
with message-id 
and subject line Bug#886476: fixed in caja-seahorse 1.18.4-1
has caused the Debian Bug report #886476,
regarding caja-seahorse: Depends on deprecated libgnome-keyring
to be marked as done.

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

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


-- 
886476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caja-seahorse
Version: 1.18.3-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome-keyring-removal

Hi,

The libgnome-keyring library is deprecated and its usage is strongly
discouraged [1].

Your package caja-seahorse declares a build-dependency on
libgnome-keyring-dev or links against libgnome-keyring0.

Please update your application to use libsecret instead [2].
Such a port should ideally happen with upstream being involved.

On behalf of the Debian GNOME team,
Jeremy Bicha

[1] https://git.gnome.org/browse/libgnome-keyring/commit/?id=6a5adea4aec93
[2] https://wiki.gnome.org/Projects/Libsecret
--- End Message ---
--- Begin Message ---
Source: caja-seahorse
Source-Version: 1.18.4-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated caja-seahorse 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: Thu, 18 Jan 2018 17:02:19 +0100
Source: caja-seahorse
Binary: caja-seahorse
Architecture: source
Version: 1.18.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 caja-seahorse - Caja extension to encrypt/decrypt OpenPGP files using GnuPG
Closes: 886476
Changes:
 caja-seahorse (1.18.4-1) unstable; urgency=medium
 .
   [ Vangelis Mouhtsis ]
   * debian/control:
 + Rename pretty name of our team -> Debian+Ubuntu MATE Packaging Team.
 + Update Maintainer: field to debian-mate ML on lists.debian.org.
 + Temporarily have pkg-mate-team ML under Uploaders:.
 + Add myself to Uploaders: field.
 .
   [ Mike Gabriel ]
   * New upstream release.
   * debian/control:
 + Ease backporting to stretch, B-D on debhelper (>= 11~).
 + Drop B-D libgnome-keyring-dev. No required by this upstream release
   anymore. (Closes: #886476).
Checksums-Sha1:
 44936dba84751061eeaf6ad11d991a0e4d435918 2397 caja-seahorse_1.18.4-1.dsc
 8c55d794f891bc50ea5c856cf370f302a2881294 229823 
caja-seahorse_1.18.4.orig.tar.gz
 42d1e7a317459a877731c61bae68d682569a5283 2500 
caja-seahorse_1.18.4-1.debian.tar.xz
 686a85e44bf40e94c2d66c16a5a30bccf1ffaa6d 15864 
caja-seahorse_1.18.4-1_source.buildinfo
Checksums-Sha256:
 9c0fc62a5aad824578ff8395703fbc06e99132023a7bdd9cc68afb45b5314f6b 2397 
caja-seahorse_1.18.4-1.dsc
 2ee3fc97a43e20fcef411e29b786946eeb03fc477b23b79b78b51a9db7e0cca6 229823 
caja-seahorse_1.18.4.orig.tar.gz
 aa5cbc0c9c4df91bb26d2cd080a38418e9a6ae8fc4a9925d6936e7f3dc5119eb 2500 
caja-seahorse_1.18.4-1.debian.tar.xz
 6054be348e0c841eb4f0ee29a0a29e1927d42bfa73fb3b6a32f05237b48f0b82 15864 
caja-seahorse_1.18.4-1_source.buildinfo
Files:
 f7f234edf5c92dfbf23db6f81b6ac4a4 2397 x11 optional caja-seahorse_1.18.4-1.dsc
 c0e9d630bf879a9e3b8718c8671199ac 229823 x11 optional 
caja-seahorse_1.18.4.orig.tar.gz
 361d5eb578d450a81763dff89ead51f1 2500 x11 optional 
caja-seahorse_1.18.4-1.debian.tar.xz
 04491d1cceaef0c1a1df5268b7bc54ec 15864 x11 optional 
caja-seahorse_1.18.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlpgxVUVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxovAP/3S3W6ljmQ1BNQ0XEvHs63aD0PX4
lPp5Zkw/cI+UlcsjFdQMELEAHVq2nczDLEqlBBcl+1otX7U1blm8buNvO2pk9NbK
J3evyANScwjB4F7XhmEgVkn9AgNZXzmZI6aMAI0fBxOwRsQXV5wT3Dc9XZ5RtBWF
nouShYfRS3dTeuPLIWN7eQ4novAdLHoQ9OMEtZleFuFhlnTMzfguEYHIkDWS4z0w
4QfnJkOPNdVxI7tFaPGNkbQ9HISrFA/UGomV7Pe9ZCwVdGbGR97a58Sa2xKj4zMB

Processed: Re: Bug#887633: xymon FTBFS with glibc 2.26

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 http://lists.xymon.com/archive/2017-February/044369.html
Bug #887633 [src:xymon] xymon FTBFS with glibc 2.26
Set Bug forwarded-to-address to 
'http://lists.xymon.com/archive/2017-February/044369.html'.
> tag -1 + patch pending
Bug #887633 [src:xymon] xymon FTBFS with glibc 2.26
Added tag(s) patch and pending.

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

Bug#887633: xymon FTBFS with glibc 2.26

[Axel Beckert]

Control: forwarded -1 http://lists.xymon.com/archive/2017-February/044369.html
Control: tag -1 + patch pending

Hi,

Adrian Bunk wrote:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xymon.html
> 
> ...
> gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wall -Wno-unused 
> -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -DLINUX -I/build/1st/xymon-4.3.28/include  -o logfetch logfetch.c 
> ../lib/libxymonclient.a
> logfetch.c: In function 'logdata':
> logfetch.c:210:105: error: 'intmax_t' undeclared (first use in this 
> function); did you mean '__intmax_t'?
>errprintf("logfetch: %s delta %jd bytes exceeds max buffer size %u; 
> skipping some data\n", filename, (intmax_t)bufsz, MAXCHECK);
>   
>^~~~
>   
>__intmax_t
> logfetch.c:210:105: note: each undeclared identifier is reported only once 
> for each function it appears in
> logfetch.c:210:114: error: expected ')' before 'bufsz'
>errprintf("logfetch: %s delta %jd bytes exceeds max buffer size %u; 
> skipping some data\n", filename, (intmax_t)bufsz, MAXCHECK);
>   
> ^
> Makefile:41: recipe for target 'logfetch' failed
> make[2]: *** [logfetch] Error 1

This issue seems to be known upstream for about a year now, just not
related to glibc 2.26 but related to OpenBSD:

http://lists.xymon.com/archive/2017-February/044369.html

The patch suggested there is just to add "#include " to
logfetch.c. And doing so also fixes this issue here.

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

Processed: tagging 887596

[Debian Bug Tracking System]

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

> tags 887596 + upstream fixed-upstream
Bug #887596 [src:wordpress] wordpress: XSS vulnerability in MediaElement
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 887633

[Debian Bug Tracking System]

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

> tags 887633 + confirmed
Bug #887633 [src:xymon] xymon FTBFS with glibc 2.26
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#887635: dms binary-any FTBFS

[Adrian Bunk]

Source: dms
Version: 1.0.8.1-1
Severity: serious

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

...
dh_install
make[1]: Leaving directory '/<>'
   dh_installdocs -a
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
dh_sphinxdoc -X searchtools.js -X translations.js
dh_sphinxdoc: Sphinx documentation not found
dh_sphinxdoc /usr/share/doc/dms-doc/html/
dh_sphinxdoc: Path /usr/share/doc/dms-doc/html/ not found in any built package
(searched in: dms-core dms-wsgi dms-dr dms)
debian/rules:52: recipe for target 'override_dh_sphinxdoc' failed
make[1]: *** [override_dh_sphinxdoc] Error 2


Can be reproduced with "dpkg-buildpackage -B".

Bug#887633: xymon FTBFS with glibc 2.26

[Adrian Bunk]

Source: xymon
Version: 4.3.28-2
Severity: serious

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

...
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wall -Wno-unused 
-Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-DLINUX -I/build/1st/xymon-4.3.28/include  -o logfetch logfetch.c 
../lib/libxymonclient.a
logfetch.c: In function 'logdata':
logfetch.c:210:105: error: 'intmax_t' undeclared (first use in this function); 
did you mean '__intmax_t'?
   errprintf("logfetch: %s delta %jd bytes exceeds max buffer size %u; skipping 
some data\n", filename, (intmax_t)bufsz, MAXCHECK);

 ^~~~

 __intmax_t
logfetch.c:210:105: note: each undeclared identifier is reported only once for 
each function it appears in
logfetch.c:210:114: error: expected ')' before 'bufsz'
   errprintf("logfetch: %s delta %jd bytes exceeds max buffer size %u; skipping 
some data\n", filename, (intmax_t)bufsz, MAXCHECK);

  ^
Makefile:41: recipe for target 'logfetch' failed
make[2]: *** [logfetch] Error 1

Bug#887632: progressivemauve FTBFS with glibc 2.26

[Adrian Bunk]

Source: progressivemauve
Version: 1.2.0+4713-3
Severity: serious

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

...
In file included from /usr/include/x86_64-linux-gnu/bits/getopt_posix.h:27:0,
 from /usr/include/unistd.h:872,
 from /usr/include/boost/config/stdlib/libstdcpp3.hpp:78,
 from /usr/include/boost/config.hpp:48,
 from /usr/include/boost/iostreams/device/mapped_file.hpp:14,
 from /usr/include/libMems-1.6/libMems/FileSML.h:22,
 from /usr/include/libMems-1.6/libMems/DNAFileSML.h:16,
 from mauveAligner.cpp:20:
/usr/include/x86_64-linux-gnu/bits/getopt_core.h:91:12: error: declaration of 
'int getopt(int, char* const*, const char*) throw ()' has a different exception 
specifier
 extern int getopt (int ___argc, char *const *___argv, const char *__shortopts)
^~
In file included from mauveAligner.cpp:14:0:
getopt.h:149:12: note: from previous declaration 'int getopt(int, char* const*, 
const char*)'
 extern int getopt (int ___argc, char *const *___argv, const char *__shortopts);
^~

Processed: Re: uim: circular dependency hell

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #877918 [uim] uim: circular dependency hell
Severity set to 'serious' from 'important'

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

Bug#887631: ocfs2-tools FTBFS with glibc 2.26

[Adrian Bunk]

Source: ocfs2-tools
Version: 1.8.5-3
Severity: serious

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

...
In file included from /usr/include/string.h:431:0,
 from ../include/ocfs2/ocfs2.h:41,
 from pass4.c:32:
include/strings.h:37:1: error: unknown type name 'errcode_t'; did you mean 
'mode_t'?
 errcode_t o2fsck_strings_insert(o2fsck_strings *strings, char *string,
 ^
 mode_t
../Postamble.make:40: recipe for target 'pass4.o' failed
make[2]: *** [pass4.o] Error 1

Bug#887630: wget2 FTBFS with glibc 2.26

[Adrian Bunk]

Source: wget2
Version: 0.0.20170806-1
Severity: serious

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

...
  CC   libwget_la-ssl_gnutls.lo
ssl_gnutls.c: In function '_ssl_writev':
ssl_gnutls.c:1253:9: warning: implicit declaration of function 'writev'; did 
you mean 'write'? [-Wimplicit-function-declaration]
   ret = writev(tcp->sockfd, (struct iovec *) iov, iovcnt);
 ^~
 write
ssl_gnutls.c:1265:132: error: 'writev' undeclared (first use in this function); 
did you mean 'write'?
  gnutls_transport_set_vec_push_function(tcp->ssl_session, (ssize_t (*) 
(gnutls_transport_ptr_t, const giovec_t * iov, int iovcnt)) writev);

^~

write
ssl_gnutls.c:1265:132: note: each undeclared identifier is reported only once 
for each function it appears in
Makefile:1889: recipe for target 'libwget_la-ssl_gnutls.lo' failed
make[3]: *** [libwget_la-ssl_gnutls.lo] Error 1

Bug#866454: plastex: depends on obsolete python-imaging (replace with python3-pil or python-pil)

[Stuart Prescott]

Dear maintainers of plastex,

On Monday, 8 January 2018 23:40:14 AEDT Stuart Prescott wrote:
> Control: tags -1 patch
> 
> The attached patch does the minimum that is required to update the package.
> 
> There's a lot more that could be done with this package (including a new
> upstream release from a few years ago) but this is a start...

The attached is a patch series that I intend to include in an NMU shortly 
unless someone else beats me to it. 

The patches sit on top of the current DMPT git and I would include the changes 
that are sitting there but never uploaded. The source in git does not 
currently build at all (the patches get applied twice which fails) and so this 
is also fixed.

The main objective is, of course, to fix bug #866454.

regards
Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7From 84611432fe2081b5ea59ae9d68413fbba20f8f81 Mon Sep 17 00:00:00 2001
From: Stuart Prescott 
Date: Fri, 19 Jan 2018 01:03:18 +1100
Subject: [PATCH 1/4] Re-add lost changelog from NMU 0.9.2-1.1

---
 debian/changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 8db1d89..3f03e1a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -15,6 +15,13 @@ plastex (0.9.2-2) UNRELEASED; urgency=low
 
  -- Jakub Wilk   Sun, 05 May 2013 16:01:31 +0200
 
+plastex (0.9.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build using dh-python. Closes: #786244.
+
+ -- Matthias Klose   Sat, 22 Aug 2015 15:00:53 +0200
+
 plastex (0.9.2-1) unstable; urgency=low
 
   [ Carl Fürstenberg ]
-- 
2.11.0

>From 8c29d2d44c1f33853d523c0c926deff14e25a33b Mon Sep 17 00:00:00 2001
From: Stuart Prescott 
Date: Fri, 19 Jan 2018 00:17:19 +1100
Subject: [PATCH 2/4] Switch from python-imaging to python-pil

---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 77323ef..c8d21d6 100644
--- a/debian/control
+++ b/debian/control
@@ -16,13 +16,13 @@ Build-Depends-Indep: xsltproc (>= 1.1.21),
  libxml-libxml-perl, 
  texlive-base-bin, 
  dvipng, 
- python-imaging
+ python-pil
 Standards-Version: 3.8.3
 Homepage: http://plastex.sourceforge.net/
 
 Package: python-plastex
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, texlive-latex-base, dvipng, python-imaging
+Depends: ${python:Depends}, ${misc:Depends}, texlive-latex-base, dvipng, python-pil
 Recommends: python-kid, python-genshi, python-cheetah
 Description: LaTeX document processing framework in Python
  plasTeX is a collection of Python frameworks that allow you to process LaTeX 
-- 
2.11.0

>From 1904950f89895650f1f96c81dda498d4ae2aeef3 Mon Sep 17 00:00:00 2001
From: Stuart Prescott 
Date: Fri, 19 Jan 2018 00:42:53 +1100
Subject: [PATCH 3/4] Switch to 3.0 (quilt) source format

Patches were being double-applied and so FTBFS
---
 debian/rules | 1 -
 debian/source/format | 2 +-
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/debian/rules b/debian/rules
index a159263..cc91a1d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,7 +2,6 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/python-distutils.mk
-include /usr/share/cdbs/1/rules/patchsys-quilt.mk
 include $(CURDIR)/debian/mk/docbook-xml-manpage.mk
 
 DOCBOOKXML_MANPAGE_SOURCES = debian/xml-man/plastex.xml
diff --git a/debian/source/format b/debian/source/format
index d3827e7..163aaf8 100644
--- a/debian/source/format
+++ b/debian/source/format
@@ -1 +1 @@
-1.0
+3.0 (quilt)
-- 
2.11.0

From a037eb632de18c5ee9ac69f2368044df6dde187d Mon Sep 17 00:00:00 2001
From: Stuart Prescott 
Date: Fri, 19 Jan 2018 00:17:46 +1100
Subject: [PATCH 4/4] Finalise changelog for upload

---
 debian/changelog | 10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 3f03e1a..0cb60d3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,10 @@
-plastex (0.9.2-2) UNRELEASED; urgency=low
+plastex (0.9.2-1.2) unstable; urgency=low
+
+  [ Stuart Prescott ]
+  * Non-maintainer upload.
+  * Replace python-imaging dependencies with python-pil (Closes: #866454).
+  * Switch to source format 3.0 (quilt) so that the package actually builds
+following the svn to git-dpm conversion.
 
   [ Carl Fürstenberg ]
   * override lintian warning wrong-section-according-to-package-name, we stick
@@ -13,7 +19,7 @@ plastex (0.9.2-2) UNRELEASED; urgency=low
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 
- -- Jakub Wilk   Sun, 05 May 2013 16:01:31 +0200
+ -- Stuart Prescott   Fri, 19 Jan 2018 00:17:25 +1100
 
 plastex (0.9.2-1.1) unstable; urgency=medium
 
-- 
2.11.0

Bug#887625: gmime-bin: Illegal seek

[Cristian Ionescu-Idbohrn]

Package: gmime-bin
Version: 3.0.5-1
Severity: grave
Justification: renders package unusable

$ strace -f gmime-uuencode file.jpg
...
openat(AT_FDCWD, "/proc/filesystems", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tr"..., 1024) = 370
read(3, "", 1024)   = 0
close(3)= 0
access("/etc/selinux/config", F_OK) = -1 ENOENT (No such file or directory)
futex(0x7fe06805ee28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7fe06805ee28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
dup(0)  = 3
fstat(3, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
write(1, "begin 600 file.jpg\n", 22begin 600 file.jpg
) = 22
lseek(3, 0, SEEK_CUR)   = -1 ESPIPE (Illegal seek)
lseek(3, 0, SEEK_SET)   = -1 ESPIPE (Illegal seek)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/charset.alias", O_RDONLY) = -1 
ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=26258, ...}) = 0
mmap(NULL, 26258, PROT_READ, MAP_SHARED, 4, 0) = 0x7fe068eeb000
close(4)= 0
futex(0x7fe0670889e8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(2, "gmime-uuencode: Illegal seek\n", 29gmime-uuencode: Illegal seek
) = 29
close(3)= 0
exit_group(1)   = ?
+++ exited with 1 +++


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

Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968), LANGUAGE= 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages gmime-bin depends on:
ii  libassuan0  2.5.1-1
ii  libc6   2.26-2
ii  libglib2.0-02.54.3-1
ii  libgmime-3.0-0  3.0.5-1
ii  libgpg-error0   1.27-5
ii  libgpgme11  1.10.0-1
ii  zlib1g  1:1.2.8.dfsg-5

gmime-bin recommends no packages.

gmime-bin suggests no packages.

-- no debconf information


Cheers,

-- 
Cristian

Bug#887623: fastnetmon FTBFS with libndpi-dev 2.2-1

[Adrian Bunk]

Source: fastnetmon
Version: 1.1.3+dfsg-4
Severity: serious

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

...
/usr/bin/c++  -DENABLE_DPI -DENABLE_LUA_HOOKS -DFASTNETMON_ENABLE_AFPACKET 
-DMONGO -DNETMAP_PLUGIN -DREDIS -I/usr/include/libndpi-2.2.0 
-I/usr/include/luajit-2.1 
-I/build/1st/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_includes 
-I/usr/include/libmongoc-1.0 -I/usr/include/libbson-1.0  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -o CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o -c 
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp: In function 'void 
produce_dpi_dump_for_pcap_dump(std::__cxx11::string, std::stringstream&, 
std::__cxx11::string)':
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3635:85: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 char* protocol_name = ndpi_get_proto_name(my_ndpi_struct, 
detected_protocol.protocol);

 ^~~~

 app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3638:31: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 if (detected_protocol.protocol == NDPI_PROTOCOL_DNS) {
   ^~~~
   app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3644:38: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 } else if (detected_protocol.protocol == NDPI_PROTOCOL_NTP) {
  ^~~~
  app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3649:38: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 } else if (detected_protocol.protocol == NDPI_PROTOCOL_SSDP) {
  ^~~~
  app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3652:38: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 } else if (detected_protocol.protocol == NDPI_PROTOCOL_SNMP) {
  ^~~~
  app_protocol
CMakeFiles/fastnetmon.dir/build.make:65: recipe for target 
'CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o' failed
make[3]: *** [CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o] Error 1

Bug#887621: libvlc-bin: trigger problem after upgrade from stretch: find: '/usr/lib/x86_64-linux-gnu/vlc/plugins': No such file or directory

[Andreas Beckmann]

Package: src:vlc
Version: 3.0.0~rc5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up libvlc-bin:amd64 (3.0.0~rc5-1) ...
  Processing triggers for libc-bin (2.26-2) ...
  Processing triggers for libvlc-bin:amd64 (3.0.0~rc5-1) ...
  find: '/usr/lib/x86_64-linux-gnu/vlc/plugins': No such file or directory
  dpkg: error processing package libvlc-bin:amd64 (--configure):
   installed libvlc-bin:amd64 package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   libvlc-bin:amd64


cheers,

Andreas


libvlc-bin_3.0.0~rc5-1.log.gz
Description: application/gzip

Processed: severity of 886939 is serious

[Debian Bug Tracking System]

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

> # rising severity, since this blocks many upgrade paths from being tested 
> with piuparts
> severity 886939 serious
Bug #886939 [klibc-utils] klibc-utils: leaves diversion after upgrade from 
stretch
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#856092: marked as done (xemacs21: Please drop the (build-)dependency against esound)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 13:56:21 +
with message-id 
and subject line Bug#856092: fixed in xemacs21 21.4.24-4.1
has caused the Debian Bug report #856092,
regarding xemacs21: Please drop the (build-)dependency against esound
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.)


-- 
856092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21
Version: 21.4.22-14
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal

Dear maintainer,

Your package is {build-}depending against esound which is deprecated
for quite some times now.

We are planning to remove esound for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: xemacs21
Source-Version: 21.4.24-4.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated xemacs21 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: Thu, 18 Jan 2018 13:17:38 +0100
Source: xemacs21
Binary: xemacs21 xemacs21-mule xemacs21-nomule xemacs21-mule-canna-wnn 
xemacs21-bin xemacs21-support xemacs21-supportel
Architecture: source amd64 all
Version: 21.4.24-4.1
Distribution: unstable
Urgency: medium
Maintainer: Mark Brown 
Changed-By: Laurent Bigonville 
Description:
 xemacs21   - highly customizable text editor -- metapackage
 xemacs21-bin - highly customizable text editor -- support binaries
 xemacs21-mule - highly customizable text editor -- Mule binary
 xemacs21-mule-canna-wnn - highly customizable text editor -- Mule binary 
compiled with Cann
 xemacs21-nomule - highly customizable text editor -- Non-mule binary
 xemacs21-support - highly customizable text editor -- architecture independent 
suppo
 xemacs21-supportel - highly customizable text editor -- non-required library 
files
Closes: 856092
Changes:
 xemacs21 (21.4.24-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Drop libesd0-dev from the build-dependencies, this is some
 leftover as esd support has been disabled since 2001 (Closes: #856092)
   * debian/control: Explicitly state in the short description that xemacs21
 package is a metapackage to avoid being auto-rejected by dak
   * debian/PackagesMakefile.in: Make the manpages reproducible by removing
 timestamps when gzip'ing (-n) the files
Checksums-Sha1:
 617acf4d31dcfdc6d5bd1922e74a4313e579ce53 2150 xemacs21_21.4.24-4.1.dsc
 d3ebc0855da74fb067cdd7eb94503279bdaa6fd7 32732 
xemacs21_21.4.24-4.1.debian.tar.xz
 3cc3445f9110ea359336e76f811dc2def5112716 210412 
xemacs21-bin-dbgsym_21.4.24-4.1_amd64.deb
 c19cdc9f33f48dc73a25749945d1667c2d097f3f 397908 
xemacs21-bin_21.4.24-4.1_amd64.deb
 012d09c38ff31da73f7446d3fe45c09e53087984 3083228 
xemacs21-mule-canna-wnn-dbgsym_21.4.24-4.1_amd64.deb
 7a8abed6269c9c2290bf849ec4119df90364475e 1745064 
xemacs21-mule-canna-wnn_21.4.24-4.1_amd64.deb
 f2f5b5d154d6f5414045637bcfbce49fa2f7108f 3027704 
xemacs21-mule-dbgsym_21.4.24-4.1_amd64.deb
 969bd247b265a7a9278219db50ea7fd5acd5730f 1666396 
xemacs21-mule_21.4.24-4.1_amd64.deb
 04faad8e5be86e932ae886dfd37131e0f60ba8a4 2765956 
xemacs21-nomule-dbgsym_21.4.24-4.1_amd64.deb
 eb8cd91a1e5a393f27252367445e0c9d1a260f88 1516180 
xemacs21-nomule_21.4.24-4.1_amd64.deb
 2561ded3b90d3211a78a7758cba7b01601b4df97 4180568 
xemacs21-support_21.4.24-4.1_all.deb
 3e1457a5c452b26c8507e47fa93deb1b83bfa910 1309264 
xemacs21-supportel_21.4.24-4.1_all.deb
 d3c89f5f866a499e02bb822750bfd45368e2783c 16932 xemacs21_21.4.24-4.1_all.deb
 7f4bbc65cf55a7f3ab76083aff51aa5c4666f9cd 10513 
xemacs21_21.4.24-4.1_amd64.buildinfo
Checksums-Sha256:
 

Bug#887575: [Pkg-pascal-devel] Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Abou Al Montacir]

Hi Michalis,
On Thu, 2018-01-18 at 06:43 +0100, Michalis Kamburelis wrote:
> The problem is caused by the different directories used by new FPC
> 3.0.4 packages (compared to previous versions of FPC in Debian).
I must admit that I was expecting many packages to break as the change is too
big.But I assume this is worth the pain as now we can install multiple
architecture units on the same host.
> Doing
> 
>   ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we need
to explicitly pass this?
> doesn't work, since /usr/lib/fpc/3.0.4 does not exist. This works:
> 
>   ./fpmake --globalunitdir="/usr/lib/x86_64-linux-gnu/fpc/3.0.4"
I would use DEB_HOST_MULTIARCH=$(dpkg-architecture -qDEB_HOST_MULTIARCH)
> To fix this, I suggest to
> 
> - Change / define the $FPCDIR variable inside Debian build scripts, to
> point to the new correct directory.
I would try to avoid this if possible but indeed seems correct solution
> - Or create a symlink /usr/lib/fpc/3.0.4 ->
> /usr/lib/x86_64-linux-gnu/fpc/3.0.4 .
This brings us back to pre-MA epoch. Let's avoid it. Also not possible in the
Debian auto-builder daemon.
-- 
Cheers,
Abou Al Montacir

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

Bug#887618: libgetfem++-dev: needs Depends: libgmm++-dev (= ${source:Version})

[Andreas Beckmann]

Package: libgetfem++-dev
Version: 5.2+dfsg1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable.
Since libgmm++-dev is an arch:all package, the (= ${binary:Version}) is
incorrect and no longer satisfiable after the recent binNMU.

Andreas