Bug#879988: dijitso: Missing dependency on python-pkg-resources

[Jeremy Bicha]

Source: dijitso
Version: 2017.1.0-2
Severity: serious

The automatic autopkgtest for dijitso detected a missing dependency.

https://ci.debian.net/packages/d/dijitso/unstable/amd64/

Test Case

>From a minimal Debian install, run

sudo apt install python-dijitso
python
>>> import dijitso
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/dijitso/__init__.py", line 19,
in 
from pkg_resources import get_distribution
ModuleNotFoundError: No module named 'pkg_resources'
>>> exit()

Fix
===
Have python-dijitso depend on python-pkg-resources
Have python3-dijitso depend on python3-pkg-resources

Thanks,
Jeremy Bicha

Bug#876632: marked as done (sdpa FTBFS due to hardcoded (non-multiarch) path for libblas.a)

[Debian Bug Tracking System]

Your message dated Sat, 28 Oct 2017 00:49:31 +
with message-id 
and subject line Bug#876632: fixed in sdpa 7.3.10+dfsg-2
has caused the Debian Bug report #876632,
regarding sdpa FTBFS due to hardcoded (non-multiarch) path for libblas.a
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.)


-- 
876632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdpa
Version: 7.3.9+dfsg-1.1
Severity: serious

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

...
cd . && CFLAGS="-g -O2 -fdebug-prefix-map=/<>/sdpa-7.3.9+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -fPIC 
-funroll-all-loops" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>/sdpa-7.3.9+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -fPIC -funroll-all-loops" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
/<>/sdpa-7.3.9+dfsg/./configure --build=x86_64-linux-gnu 
--prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" 
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var 
--libexecdir="\${prefix}/lib/sdpa" --srcdir=. --disable-maintainer-mode 
--disable-dependency-tracking --disable-silent-rules 
--with-lapack="/usr/lib/atlas/liblapack.a" 
--with-blas="/usr/lib/atlas/libblas.a"
...
hecking for pthread_create... yes
checking for dgemm_... no
BLAS function (dgemm) was compiled by
( gcc -g -O2 -fdebug-prefix-map=/<>/sdpa-7.3.9+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -fPIC 
-funroll-all-loops -Wall -fPIC -funroll-all-loops conftest.c  
/usr/lib/atlas/libblas.a  -L/usr/lib/gcc/x86_64-linux-gnu/7 
-L/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu 
-L/usr/lib/gcc/x86_64-linux-gnu/7/../../../../lib -L/lib/x86_64-linux-gnu 
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/x86_64-linux-gnu/7/../../.. -lgfortran -lm -lquadmath -lpthread )
but failed.
(1) Please verify config.log to check whether libraries are linked correctrly
(2) Please install one of your favorite BLAS
OpenBLAS:  http://xianyi.github.com/OpenBLAS/
BLAS:  http://www.netlib.org/blas/
ATLAS: http://math-atlas.sourceforge.net/
configure: error: BLAS link failed
/usr/share/cdbs/1/class/autotools.mk:44: recipe for target 
'debian/stamp-autotools' failed
make: *** [debian/stamp-autotools] Error 1
--- End Message ---
--- Begin Message ---
Source: sdpa
Source-Version: 7.3.10+dfsg-2

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

Debian distribution maintenance software
pp.
Makoto Yamashita  (supplier of updated sdpa 
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, 19 Oct 2017 16:00:00 +0900
Source: sdpa
Binary: sdpa libsdpa-dev sdpam
Architecture: source amd64
Version: 7.3.10+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Makoto Yamashita 
Changed-By: Makoto Yamashita 
Description:
 libsdpa-dev - Callable library and examples of SDPA
 sdpa   - High-performance package for SemiDefinite Programs
 sdpam  - Matlab/Octave interface of SDPA
Closes: 876632
Changes:
 sdpa (7.3.10+dfsg-2) unstable; urgency=low
 .
 * Fix debian/rules (closes: #876632)
 * Change priority from extra to optional
 * Update Standards-Version to 4.1.1
Checksums-Sha1:
 d09dbede5dac2ac7434c79e75d0d819be392ce38 1929 sdpa_7.3.10+dfsg-2.dsc
 feb51ad321e975477640a5bc31ec65e68398c5d0 4324 sdpa_7.3.10+dfsg-2.debian.tar.xz
 d5234138add201d08b09bff59fc7edc7bbe6f056 161900 
libsdpa-dev_7.3.10+dfsg-2_amd64.deb
 d6e80b08fb0158514200cb655f433c7858feb6a6 656096 
sdpa-dbgsym_7.3.10+dfsg-2_amd64.deb
 5d1397e2072e44a1623872899edd5b41912fa17c 14393 
sdpa_7.3.10+dfsg-2_amd64.buildinfo
 ee5dd744a94f0ec419d3ace316ec4f32f1a45060 1553156 sdpa_7.3.10+dfsg-2_amd64.deb
 f1a70758827df6be8e9af160a1d2448bb74f8805 1333512 
sdpam-dbgsym_7.3.10+dfsg-2_amd64.deb

Bug#879984: libgcrypt20: copyright does not mention OCB patent license

[brian m. carlson]

Package: libgcrypt20
Version: 1.7.9-1
Severity: serious

libgcrypt implements OCB, which is patented[0].  The author, Phil
Rogaway, provides three licenses.

* The first license applies to wholly open-source implementations that
  do not contain any closed-source components.
* The second license applies to non-military software implementations.
* The third license applies only to OpenSSL.

Only the first license applies here, since libgcrypt is not derived from
OpenSSL and the second license violates the DFSG.

Because libgcrypt is LGPL and may legally be linked to proprietary code,
it must contain a copy of the first patent license, as the patent
license imposes further restrictions on the way it can legally be used
and distributed.  As a consequence, these terms must be listed in the
copyright file.

Because Debian must avail itself of the first patent license, it is
therefore obligatory that libgcrypt20 not link against any proprietary
code directly or indirectly, and this should be prominently disclosed as
it restricts the text of the LGPL.

If it is not possible for practical purposes that libgcrypt not link to
proprietary software (say, because libgcrypt20 is linked into Xorg and
people might want to use a proprietary graphics driver), then OCB
support will need to be removed.

[0] http://web.cs.ucdavis.edu/~rogaway/ocb/license.htm

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

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

Versions of packages libgcrypt20 depends on:
ii  libc6  2.24-17
ii  libgpg-error0  1.27-3

libgcrypt20 recommends no packages.

Versions of packages libgcrypt20 suggests:
pn  rng-tools  

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#878341: marked as done (librem-dev causes FTBFS in baresip: conflicting types for goertzel_*)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 23:48:49 +
with message-id 
and subject line Bug#878341: fixed in baresip 0.5.6-1
has caused the Debian Bug report #878341,
regarding librem-dev causes FTBFS in baresip: conflicting types for goertzel_*
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.)


-- 
878341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librem-dev
Version: 0.5.2-1
Severity: serious
Control: affects -1 src:baresip

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

...
  CC [M]  build-x86_64/modules/g726/g726.o
gcc -DRELEASE -Wall -Wmissing-declarations -Wmissing-prototypes 
-Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs 
-Wshadow -Waggregate-return -Wcast-align -g -O3   -Wuninitialized 
-Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c99 -pedantic 
-DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS 
-DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS 
-DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H 
-DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG 
-DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL   -DHAVE_INET_PTON 
-DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H 
-DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DHAVE_GAI_STRERROR 
-DVERSION=\"0.5.5\" -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I. -Iinclude 
-I/usr/include/re -I/usr/include -I/include -I/usr/local/include/rem
  -I/usr/include/rem -D_GNU_SOURCE -DUSE_VIDEO=1 -DMODULE_CONF 
-DPREFIX=\"/usr\" -DUSE_AVCODEC -DUSE_AVFORMAT  \
-c modules/g726/g726.c -o build-x86_64/modules/g726/g726.o -MD -MF 
build-x86_64/modules/g726/g726.d -MT build-x86_64/modules/g726/g726.o
In file included from /usr/include/x86_64-linux-gnu/spandsp.h:78:0,
 from modules/g726/g726.c:11:
/usr/include/spandsp/tone_detect.h:84:34: error: conflicting types for 
'goertzel_init'
 SPAN_DECLARE(goertzel_state_t *) goertzel_init(goertzel_state_t *s,
  ^
In file included from /usr/include/rem/rem_audio.h:16:0,
 from /usr/include/rem/rem.h:15,
 from modules/g726/g726.c:8:
/usr/include/rem/rem_goertzel.h:15:7: note: previous declaration of 
'goertzel_init' was here
 void  goertzel_init(struct goertzel *g, double freq, unsigned srate);
   ^
In file included from /usr/include/x86_64-linux-gnu/spandsp.h:78:0,
 from modules/g726/g726.c:11:
/usr/include/spandsp/tone_detect.h:93:20: error: conflicting types for 
'goertzel_reset'
 SPAN_DECLARE(void) goertzel_reset(goertzel_state_t *s);
^~
In file included from /usr/include/rem/rem_audio.h:16:0,
 from /usr/include/rem/rem.h:15,
 from modules/g726/g726.c:8:
/usr/include/rem/rem_goertzel.h:16:7: note: previous declaration of 
'goertzel_reset' was here
 void  goertzel_reset(struct goertzel *g);
   ^~
In file included from /usr/include/x86_64-linux-gnu/spandsp.h:78:0,
 from modules/g726/g726.c:11:
/usr/include/spandsp/tone_detect.h:100:19: error: conflicting types for 
'goertzel_update'
 SPAN_DECLARE(int) goertzel_update(goertzel_state_t *s,
   ^~~
In file included from /usr/include/rem/rem_audio.h:16:0,
 from /usr/include/rem/rem.h:15,
 from modules/g726/g726.c:8:
/usr/include/rem/rem_goertzel.h:26:20: note: previous definition of 
'goertzel_update' was here
 static inline void goertzel_update(struct goertzel *g, int16_t samp)
^~~
In file included from /usr/include/x86_64-linux-gnu/spandsp.h:78:0,
 from modules/g726/g726.c:11:
/usr/include/spandsp/tone_detect.h:113:21: error: conflicting types for 
'goertzel_result'
 SPAN_DECLARE(float) goertzel_result(goertzel_state_t *s);
 ^~~
In file included from /usr/include/rem/rem_audio.h:16:0,
 from /usr/include/rem/rem.h:15,
 from modules/g726/g726.c:8:
/usr/include/rem/rem_goertzel.h:17:8: note: previous declaration of 
'goertzel_result' was here
 double goertzel_result(struct goertzel *g);
^~~
mk/mod.mk:42: recipe for target 'build-x86_64/modules/g726/g726.o' failed
make[1]: *** 

Bug#879983: ruby-cairo: Fails to build with cairo 1.15 (test failures)

[Jeremy Bicha]

Source: ruby-cairo
Version: 1.15.10-1
Severity: serious

ruby-cairo 1.15.10-1 fails to buid from source with cairo 1.15.8 which
was recently uploaded to Debian unstable.

Here's a patch that fixes one of the two test failures:
https://github.com/rcairo/rcairo/commit/d0b125e

Here's the other error:

Error: test_sub_outline(PDFSurfaceTest::#add_outline):
Cairo::TagError: invalid tag name, attributes, or nesting
/<>/test/test_pdf_surface.rb:26:in `add_outline'
/<>/test/test_pdf_surface.rb:26:in `test_sub_outline'
 23:   context.tag(Cairo::Tag::DEST, "name='destination'") do
 24: context.show_text("Destination")
 25:   end
  => 26:   id = surface.add_outline(Cairo::PDFOutline::ROOT,
 27:"top-level",
 28:"destination",
 29:Cairo::PDFOutlineFlags::OPEN)


Thanks,
Jeremy Bicha

Bug#879071: marked as done (0ad FTBFS with on armhf with gcc 7: error: call of overloaded 'abs(unsigned int)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 22:03:59 +
with message-id 
and subject line Bug#879071: fixed in 0ad 0.0.22-2
has caused the Debian Bug report #879071,
regarding 0ad FTBFS with on armhf with gcc 7: error: call of overloaded 
'abs(unsigned int)' is ambiguous
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.)


-- 
879071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 0ad
Version: 0.0.21-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/0ad.html
https://buildd.debian.org/status/fetch.php?pkg=0ad=armhf=0.0.22-1=1508365643=0

...
../../../source/gui/CDropDown.cpp: In member function 'virtual InReaction 
CDropDown::ManuallyHandleEvent(const SDL_Event_*)':
../../../source/gui/CDropDown.cpp:355:94: error: call of overloaded 
'abs(unsigned int)' is ambiguous
   diff = std::abs(pList->m_Items[i].GetRawString().LowerCase()[j] - 
(int)m_InputBuffer[j]);

  ^
In file included from /usr/include/c++/7/cmath:47:0,
 from /usr/include/c++/7/math.h:36,
 from ../../../source/lib/posix/posix_types.h:48,
 from ../../../source/lib/precompiled.h:64,
 from ../../../source/pch/gui/precompiled.h:18:
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
In file included from /usr/include/c++/7/bits/std_abs.h:38:0,
 from /usr/include/c++/7/cmath:47,
 from /usr/include/c++/7/math.h:36,
 from ../../../source/lib/posix/posix_types.h:48,
 from ../../../source/lib/precompiled.h:64,
 from ../../../source/pch/gui/precompiled.h:18:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
gui.make:198: recipe for target 'obj/gui_Release/CDropDown.o' failed
make[3]: *** [obj/gui_Release/CDropDown.o] Error 1
--- End Message ---
--- Begin Message ---
Source: 0ad
Source-Version: 0.0.22-2

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

Debian distribution maintenance software
pp.
Ludovic Rousseau  (supplier of updated 0ad 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: Fri, 27 Oct 2017 16:22:15 +0200
Source: 0ad
Binary: 0ad
Architecture: source amd64
Version: 0.0.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Ludovic Rousseau 
Description:
 0ad- Real-time strategy game of ancient warfare
Closes: 879071
Changes:
 0ad (0.0.22-2) unstable; urgency=medium
 .
   * Fix "0ad FTBFS with on armhf with gcc 7: error: call of overloaded
 'abs(unsigned int)' is ambiguous" by removing support of armhf
 (Closes: #879071)
   * remove support of arm64 because of FTBFS in spidermonkey/mozjs-38.0.0
 
https://buildd.debian.org/status/fetch.php?pkg=0ad=arm64=0.0.22-1=1508351579=0
Checksums-Sha1:
 51d06d4e2cdd04f8cf97440ef8d0ed7421d6da2e 2440 0ad_0.0.22-2.dsc
 15e5c8d497a6bffe1d61f381f1d9c71f2b225dc0 71488 0ad_0.0.22-2.debian.tar.xz
 aa457610b844b0c5f068d7b737181087ac8daf91 95739892 0ad-dbgsym_0.0.22-2_amd64.deb
 

Bug#879980: antlr: FTBFS: dh: unable to load addon maven-repo-helper

[Aaron M. Ucko]

Source: antlr
Version: 2.7.7+dfsg-9
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of antlr in minimal environments geared for building only its
architecture-dependent binary packages (as on the autobuilders) have
started failing with errors along the lines of

  dh clean --with maven-repo-helper --with python2,python3
  dh: unable to load addon maven-repo-helper: Can't locate 
Debian/Debhelper/Sequence/maven_repo_helper.pm in @INC (you may need to install 
the Debian::Debhelper::Sequence::maven_repo_helper module) (@INC contains: 
/etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.26.0 
/usr/local/share/perl/5.26.0 /usr/lib/aarch64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/aarch64-linux-gnu/perl-base) at (eval 12) 
line 1.
  BEGIN failed--compilation aborted at (eval 12) line 1.

  debian/rules:8: recipe for target 'clean' failed
  make: *** [clean] Error 2

Please either conditionalize the usage of --with maven-repo-helper
appropriately or move maven-repo-helper to the main Build-Depends
field.

Thanks!

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

Bug#879910: marked as done (lxqt-panel: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-panel.desktop)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 21:49:32 +
with message-id 
and subject line Bug#879910: fixed in lxqt-panel 0.12.0-2
has caused the Debian Bug report #879910,
regarding lxqt-panel: fails to upgrade from 'sid' - trying to overwrite 
/etc/xdg/autostart/lxqt-panel.desktop
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.)


-- 
879910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxqt-panel
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package lxqt-panel.
  Preparing to unpack .../90-lxqt-panel_0.12.0-1_amd64.deb ...
  Unpacking lxqt-panel (0.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-FKAvKI/90-lxqt-panel_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/xdg/autostart/lxqt-panel.desktop', which is also 
in package lxqt-common 0.11.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-FKAvKI/90-lxqt-panel_0.12.0-1_amd64.deb


cheers,

Andreas


lxqt-common=0.11.2-2_lxqt-panel=0.12.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lxqt-panel
Source-Version: 0.12.0-2

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated lxqt-panel 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, 27 Oct 2017 23:27:44 +0200
Source: lxqt-panel
Binary: lxqt-panel
Architecture: source
Version: 0.12.0-2
Distribution: experimental
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 lxqt-panel - LXQt desktop panel
Closes: 855379 879910
Changes:
 lxqt-panel (0.12.0-2) experimental; urgency=medium
 .
   * Added missed breaks and replaces for lxqt-common << 0.12.0
 (Closes: #879910) - Thanks Andreas Beckmann 
   * Time off fixed upstream (Closes: #855379)
Checksums-Sha1:
 e7a3cfc7be6f204db6e27a10deac7ae456a04450 2512 lxqt-panel_0.12.0-2.dsc
 e35662a49a4d8b99ce51182960468d92fff1e314 6252 lxqt-panel_0.12.0-2.debian.tar.xz
 b5135caee54ed76ea255b101d658aba8d3c08688 13898 
lxqt-panel_0.12.0-2_source.buildinfo
Checksums-Sha256:
 9e5d46959610a2bf633aec3354673b838009ec14e1a125c87b5f682bdf7387d4 2512 
lxqt-panel_0.12.0-2.dsc
 64479c142eedd11071b8a929200ee078746be695cbbe956b6be491f6cd62880f 6252 
lxqt-panel_0.12.0-2.debian.tar.xz
 ce646083ddbbc2e97b98d2efaeb98645bb5b820c24abf8acc30a15c753a989df 13898 
lxqt-panel_0.12.0-2_source.buildinfo
Files:
 116c549f465ccd6c0e953ffc78c5269a 2512 x11 optional lxqt-panel_0.12.0-2.dsc
 51bb8c7ae78a496586890c72bafc646d 6252 x11 optional 
lxqt-panel_0.12.0-2.debian.tar.xz
 a9f1ca372761f3e7592be1593b06f107 13898 x11 optional 
lxqt-panel_0.12.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEvb/GiO+tuolan0ZLzSgKC01ygnwFAlnzpWkACgkQzSgKC01y
gny7AAf+OL6x61BjBpd7BeI6o+gpBDaJQAktWgNElOjYTG2Ktx7Mtv/QAb/Ux3oB
PBBrdo5yCpsRecuSnaDcOKQQINWTRD3BmHHgBxWnA+lpbjyhMZEwvNTJcn0UOsU2
1/zaxFsjgKAfsS2HphmloPjMmBVFW2YHEaZpr843YmKMTqJVeFUCxjWV4mn132Af
jIPBqqXBIs19lbQ06YENcw6XD8rtOfCjyttfZrNRFd6B6EPJWCVhTJmVALnQeTQj
oXGvUMnqP0Mwm+m0mjeqUC6Msyr7S1w/RlMKw8wWHs0nWmvwkuFemA+wk1F1kiA7
fcUWs8xAlDOsORxkgDVZa66mhu4Phg==
=DsOj
-END PGP SIGNATURE End Message ---

Bug#879912: marked as done (lxqt-runner: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-runner.desktop)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 21:26:30 +
with message-id 
and subject line Bug#879912: fixed in lxqt-runner 0.12.0-2
has caused the Debian Bug report #879912,
regarding lxqt-runner: fails to upgrade from 'sid' - trying to overwrite 
/etc/xdg/autostart/lxqt-runner.desktop
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.)


-- 
879912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxqt-runner
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package lxqt-runner.
  Preparing to unpack .../60-lxqt-runner_0.12.0-1_amd64.deb ...
  Unpacking lxqt-runner (0.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-5yHAXI/60-lxqt-runner_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/xdg/autostart/lxqt-runner.desktop', which is also 
in package lxqt-common 0.11.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-5yHAXI/60-lxqt-runner_0.12.0-1_amd64.deb


cheers,

Andreas


lxqt-common=0.11.2-2_lxqt-runner=0.12.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lxqt-runner
Source-Version: 0.12.0-2

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

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

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated lxqt-runner package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Oct 2017 22:44:36 +0200
Source: lxqt-runner
Binary: lxqt-runner
Architecture: source
Version: 0.12.0-2
Distribution: experimental
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 lxqt-runner - LXQt program launcher
Closes: 879912
Changes:
 lxqt-runner (0.12.0-2) experimental; urgency=medium
 .
   * Added missed breaks and replaces for lxqt-common << 0.12.0
 (Closes: #879912) - Thanks Andreas Beckmann 
Checksums-Sha1:
 cadc3e1153004ecd3a59c57cd373ad9e2cfc9efa 2189 lxqt-runner_0.12.0-2.dsc
 bc16422d3dcc1a8ab9eaa0f77da5673bb4d8c793 5520 
lxqt-runner_0.12.0-2.debian.tar.xz
 c83aba3c849ebfcde3b21deac38e91e4d3b9edfa 12923 
lxqt-runner_0.12.0-2_source.buildinfo
Checksums-Sha256:
 1aa566cfb548366cfe3b447c023c9eb95fd0ccaa236d3d7c57ff709e36ff940d 2189 
lxqt-runner_0.12.0-2.dsc
 c6e926c6242cc3a509410cc1ee6f7d5ddcc725f5e1d859910feb37d7cc5e2e59 5520 
lxqt-runner_0.12.0-2.debian.tar.xz
 8325b51b68ea8492915396a3d03358cc0356e5673d1805266c003c5dfe72c065 12923 
lxqt-runner_0.12.0-2_source.buildinfo
Files:
 f3e8327264a11b15f00882fbb0512b75 2189 x11 optional lxqt-runner_0.12.0-2.dsc
 760c00dbd147f1d166a7acb4f4bb500e 5520 x11 optional 
lxqt-runner_0.12.0-2.debian.tar.xz
 a58dd9dac2324cf84806b64ce84f6447 12923 x11 optional 
lxqt-runner_0.12.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEvb/GiO+tuolan0ZLzSgKC01ygnwFAlnzm7sACgkQzSgKC01y
gnzFqAf/dKyg2cewerSFs9PWdQSbDs9jZcZOs0xs76/jTG+E553hDYmTS/SFPmDb
/08X8S8CUdx7rSQJB/k7x9wqRbsxmg/XhZ4Y1niV0Z4RU7fHnm8cGOsC0d0kIAAs
iNhzxZociPO/fTT5kYPEemv1+tNFaQHfR3mx4QS/r/X5F1NS4Vp6hHwt7Wbqtu8L
yI30L27U2lAtY7P9uvjiJMCHw2Iq/GK9Ptz63S0L710DJu2KXrZZX0/yWKlXllRi
7uxPYgiE23QleG+MDi3Tb2pEVAillZJg2XPptNiL6qSB9/+fKs7THkEOYZy33uOU
L1XN/T4RRmRaTj+nB5Of9TjjNiTn4A==
=9bH8
-END PGP SIGNATURE End Message ---

Bug#879911: marked as done (lxqt-powermanagement: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-powermanagement.desktop)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 21:26:23 +
with message-id 
and subject line Bug#879911: fixed in lxqt-powermanagement 0.12.0-2
has caused the Debian Bug report #879911,
regarding lxqt-powermanagement: fails to upgrade from 'sid' - trying to 
overwrite /etc/xdg/autostart/lxqt-powermanagement.desktop
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.)


-- 
879911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxqt-powermanagement
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package lxqt-powermanagement.
  Preparing to unpack .../78-lxqt-powermanagement_0.12.0-1_amd64.deb ...
  Unpacking lxqt-powermanagement (0.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rT9Wgh/78-lxqt-powermanagement_0.12.0-1_amd64.deb 
(--unpack):
   trying to overwrite '/etc/xdg/autostart/lxqt-powermanagement.desktop', which 
is also in package lxqt-common 0.11.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-rT9Wgh/78-lxqt-powermanagement_0.12.0-1_amd64.deb


cheers,

Andreas


lxqt-common=0.11.2-2_lxqt-powermanagement=0.12.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lxqt-powermanagement
Source-Version: 0.12.0-2

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated lxqt-powermanagement 
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, 27 Oct 2017 22:10:31 +0200
Source: lxqt-powermanagement
Binary: lxqt-powermanagement
Architecture: source
Version: 0.12.0-2
Distribution: experimental
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 lxqt-powermanagement - power management module for LXQt
Closes: 879911
Changes:
 lxqt-powermanagement (0.12.0-2) experimental; urgency=medium
 .
   * Added missed breaks and replaces for lxqt-common << 0.12.0
 (Closes: #879911) - Thanks Andreas Beckmann 
Checksums-Sha1:
 407cf93f639ff58326d5adcbdb9a87be5e3e9a7d 2289 lxqt-powermanagement_0.12.0-2.dsc
 583279fbb116cc419f2eb649f7c63109c7784515 5828 
lxqt-powermanagement_0.12.0-2.debian.tar.xz
 106a6a2345b9e4cba0a1e937969302ee45222492 12735 
lxqt-powermanagement_0.12.0-2_source.buildinfo
Checksums-Sha256:
 a4b2e21c54f4d76c42cf8f3fcc51a911a8e7f4246c8eee8937df2d542e977a8f 2289 
lxqt-powermanagement_0.12.0-2.dsc
 15b802993f5f3783bbf60e595de37e0a84b930a2795fe9c0fd014e9f3c4a198d 5828 
lxqt-powermanagement_0.12.0-2.debian.tar.xz
 1b82efb6c5fbc20a02056f540a083406f2570e8ddea1f190b3aa1e385c4cb6fa 12735 
lxqt-powermanagement_0.12.0-2_source.buildinfo
Files:
 b3fca8d5020e916e8a003e536eacb148 2289 x11 optional 
lxqt-powermanagement_0.12.0-2.dsc
 6403c8f4f6768e8ba0d0426bc7d8bea8 5828 x11 optional 
lxqt-powermanagement_0.12.0-2.debian.tar.xz
 eaf59c83e6012a118d26d18cc3aa5de4 12735 x11 optional 
lxqt-powermanagement_0.12.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEvb/GiO+tuolan0ZLzSgKC01ygnwFAlnzk6cACgkQzSgKC01y
gnxa0Af+KlJQHvuRJyNO+08xmOy2GHnXPVo0peD1/2gG/uUmpsRFxuH+j4G81yEP
8a0qqDFSGrCpgzYLR0xuhoPvkosZ7ub+M3x+/ykkx1ykgYsNE7UAjlb4W7Ln2qCP
RXzHDTT5TY/71bnHOn7TycuVMaajoEnRrjo0fduJI2wHzonLE8uiu7hRKfn2+fZq
zkFecAGTxyLp8SXF8sUfQtBrIK8DZjAZruFculrV7VS9Ca4UoY7fE662aaKbWV2O
lYMUjwUcs7P3gjI6ZUbJ71B+a/bn6ggRbVSmaPgxDfeLoKxoWyZludpH7+9iPvgq

Bug#879976: meson: 0.43.0-1 fails to build, test failures

[Jeremy Bicha]

On Fri, Oct 27, 2017 at 5:18 PM, Jussi Pakkanen  wrote:
> We can bump the version requirement of GDC tests to be >= 8. This is
> would be equivalent to what we had before. We're going to have a point
> release soon so this could go in that.

Ok, well feel free to demote this bug to Important if you want the
latest upload to migrate to Testing.

Jeremy

Bug#879976: meson: 0.43.0-1 fails to build, test failures

[Jussi Pakkanen]

On Sat, Oct 28, 2017 at 12:08 AM, Jeremy Bicha  wrote:

>> I think this is because pitti's sbuilder had an issue and it crashed
>> the test runner when trying to determine the number of CPUs in the
>> system. IIRC the same issue was in reproducible build environment ages
>> ago. Under pbuilder the compilation works without issues.
>
> What do you suggest for Ubuntu's builders which do use sbuild and I'm
> guessing gcc-8 is still months away.

Based on the log, the builders are working fine. It just failed on
pitti's machine for some reason we don't know.

We can bump the version requirement of GDC tests to be >= 8. This is
would be equivalent to what we had before. We're going to have a point
release soon so this could go in that.

Bug#879976: meson: 0.43.0-1 fails to build, test failures

[Jeremy Bicha]

On Fri, Oct 27, 2017 at 5:02 PM, Jussi Pakkanen  wrote:
> On Fri, Oct 27, 2017 at 11:37 PM, Jeremy Bicha  wrote:
>> meson 0.43.0-1 fails to build from source in Ubuntu and with Debian
>> Reproducible Builds
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html
>>
>> https://launchpad.net/ubuntu/+source/meson/0.43.0-1/+build/13633070
>
> This is caused by the fact that GDC's standard library is not compiled
> with fPIC even though it should support shared libraries. We skipped
> this test on GCC versions earlier than 7 (because it was known broken,
> but should have started working in 7, and won't be fully fixed until
> GCC 8 IIRC).
>
> I ran the full test suite on packaging on i386 and it passed without errors.
>
>> By the way, I notice that this version was uploaded as a binary upload
>> instead of a source-only upload.
>
> I think this is because pitti's sbuilder had an issue and it crashed
> the test runner when trying to determine the number of CPUs in the
> system. IIRC the same issue was in reproducible build environment ages
> ago. Under pbuilder the compilation works without issues.

What do you suggest for Ubuntu's builders which do use sbuild and I'm
guessing gcc-8 is still months away.

Thanks,
Jeremy Bicha

Bug#879976: meson: 0.43.0-1 fails to build, test failures

[Jussi Pakkanen]

On Fri, Oct 27, 2017 at 11:37 PM, Jeremy Bicha  wrote:

> meson 0.43.0-1 fails to build from source in Ubuntu and with Debian
> Reproducible Builds
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html
>
> https://launchpad.net/ubuntu/+source/meson/0.43.0-1/+build/13633070

This is caused by the fact that GDC's standard library is not compiled
with fPIC even though it should support shared libraries. We skipped
this test on GCC versions earlier than 7 (because it was known broken,
but should have started working in 7, and won't be fully fixed until
GCC 8 IIRC).

I ran the full test suite on packaging on i386 and it passed without errors.

> By the way, I notice that this version was uploaded as a binary upload
> instead of a source-only upload.

I think this is because pitti's sbuilder had an issue and it crashed
the test runner when trying to determine the number of CPUs in the
system. IIRC the same issue was in reproducible build environment ages
ago. Under pbuilder the compilation works without issues.

Bug#879976: meson: 0.43.0-1 fails to build, test failures

[Jeremy Bicha]

Source: meson
Version: 0.43.0-1
Severity: serious
X-Debbugs-CC: mp...@debian.org

meson 0.43.0-1 fails to build from source in Ubuntu and with Debian
Reproducible Builds
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html

https://launchpad.net/ubuntu/+source/meson/0.43.0-1/+build/13633070

By the way, I notice that this version was uploaded as a binary upload
instead of a source-only upload.

https://wiki.debian.org/SourceOnlyUpload

Thanks,
Jeremy Bicha

Bug#879662:

[nicodache]

Hello,

TL:DR ; nanosleep.

I've upgraded to apt 1.6~alpha2 (amd64)and I'm now getting the following
error message.

[21:02]  ~ $ sudo apt-get update
[sudo] Mot de passe de nicodache :
Réception de:1 http://ftp.belnet.be/debian sid InRelease [235 kB]
0% [1 InRelease 2.679 B/235 kB 1%] [Connexion à deb.opera.com
(185.26.183.130)]
 Seccomp prevented execution of syscall 35 on architecture
amd64 
Lecture des listes de paquets... Fait
E: Method http has died unexpectedly!
E: Le sous-processus http a renvoyé un code d'erreur (31)

I've had a look at files https://people.debian.org/~jak/syscalls-trapped.txt,
https://people.debian.org/~jak/syscalls-allowed.txt, and man syscalls, but
didn't find anything called 35 in there...

I've tried to add it into /etc/apt/apt.conf (I just added
APT::Sandbox::Seccomp::Allow { "35";};
to it).

This yields
0% [En cours]EE: : Cannot allow 35: Argument invalide -
aptMethod::Configuration (0: Succès)
Cannot allow 35: Argument invalide - aptMethod::Configuration (0:
Succès)
Lecture des listes de paquets... Fait
E: Method https has died unexpectedly!
E: Le sous-processus https a renvoyé un code d'erreur (100)

I foolishly looked at man 2 syscalls, and using dec/octal/hexa numbering,
tried all the relative syscalls I found in the list presented there, in the
order given by the man page (that is, chroot clone delete_module epoll_wait
fallocate fgetxattr).

Then I got smarter, and I found arch/x86/entry/syscalls/syscall_64.tbl,
which is in a format which made much more sense to me.

[21:44]  /tmp/linux-4.13.10 $ grep ^35
arch/x86/entry/syscalls/syscall_64.tbl
35  common  *nanosleep*   sys_nanosleep

And that now works as expected *\o/*

So you may want to add nanosleep, and maybe also clock_nanosleep to the
default APT seccomp config.

Cheers (and thanks for that ~alpha2 modifications).
-- N

Bug#879880: marked as done (flightgear: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/man/man1/metar.1.gz)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 19:34:47 +
with message-id 
and subject line Bug#879880: fixed in flightgear 1:2017.3.1+dfsg-3
has caused the Debian Bug report #879880,
regarding flightgear: fails to upgrade from 'stable' to 'sid' - trying to 
overwrite /usr/share/man/man1/metar.1.gz
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.)


-- 
879880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flightgear
Version: 1:2017.3.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package flightgear.
  Preparing to unpack .../253-flightgear_1%3a2017.3.1+dfsg-2_amd64.deb ...
  Unpacking flightgear (1:2017.3.1+dfsg-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-4BjngF/253-flightgear_1%3a2017.3.1+dfsg-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man1/metar.1.gz', which is also in 
package metar 20061030.1-2.2+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-4BjngF/253-flightgear_1%3a2017.3.1+dfsg-2_amd64.deb


cheers,

Andreas


metar=20061030.1-2.2+b1_flightgear=1%2017.3.1+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: flightgear
Source-Version: 1:2017.3.1+dfsg-3

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated flightgear 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: Fri, 27 Oct 2017 20:37:34 +0200
Source: flightgear
Binary: flightgear
Architecture: source
Version: 1:2017.3.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FlightGear Crew 
Changed-By: Dr. Tobias Quathamer 
Description:
 flightgear - Flight Gear Flight Simulator
Closes: 879880
Changes:
 flightgear (1:2017.3.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Use wrap-and-sort for debian control files
   * Add Conflicts with package "metar", as we both provide a manpage metar.1.
 Due to the low popcon and dead upstream of metar, a conflict seems
 to be justified instead of more complex solutions like using the
 alternatives system.
 Thanks to Andreas Beckmann  (Closes: #879880)
   * Add --as-needed to the linker call to avoid useless dependencies
Checksums-Sha1:
 85f7e0fc7b6f78454c2d2733ca6edba4ea303fdf 2719 flightgear_2017.3.1+dfsg-3.dsc
 1a3619347d715995290f1c2c93ae4b84da5ac914 27400 
flightgear_2017.3.1+dfsg-3.debian.tar.xz
 faf9991c6b551db6ba007618e030a2a06695b878 17929 
flightgear_2017.3.1+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 90d3b8be906e85443f64c0643de03aad43fb0eaca0d6d7afc46c3f85bf0a8f3d 2719 
flightgear_2017.3.1+dfsg-3.dsc
 8757955b0ea0c4062ceac36772fed5efd3edb9ca07e915e8643953c772be715e 27400 
flightgear_2017.3.1+dfsg-3.debian.tar.xz
 0b579edce07688fb3f9b6f0b10f75070587a8238875904c9fc70110b36aae3c0 17929 
flightgear_2017.3.1+dfsg-3_amd64.buildinfo
Files:
 66687d13ada8b15549b5ad798c1a96a4 2719 games optional 
flightgear_2017.3.1+dfsg-3.dsc
 ea23d4dd953712cdffc0c79d028ea2b1 27400 games optional 
flightgear_2017.3.1+dfsg-3.debian.tar.xz
 a8442a83a53a7655aef3674ad41fc9a8 17929 games optional 
flightgear_2017.3.1+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlnzhGIACgkQEwLx8Dbr

Bug#879974: llvm-defaults: drop libllvm-ocaml-dev (temporarily)

[Andreas Beckmann]

Source: llvm-defaults
Version: 0.36
Severity: serious
Tags: sid buster

With libllvm-3.8-ocaml-dev (temporarily) gone, libllvm-ocaml-dev needs
to be removed as well (or needs to drop the dependency on
libllvm-3.8-ocaml-dev temporarily) to allow the migration of llvm-3.8
(and ocaml) to testing.

Andreas

Processed: Re: Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

[Debian Bug Tracking System]

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

> forwarded 879800 https://trac.ffmpeg.org/ticket/6766
Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/6766'.
> tags 879800 fixed-upstream
Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#863788: oolite: Please drop dependency against mozjs 1.8.5

[Jeremy Bicha]

forwarded -1 https://github.com/OoliteProject/oolite/issues/271

Bug#879637: mariadb-10.1: FTBFS on mips64el due to test failures

[James Cowgill]

Hi,

On 23/10/17 19:48, Bas Couwenberg wrote:
> Source: mariadb-10.1
> Version: 10.1.28-1
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: affects -1 src:gdal
> 
> Dear Maintainer,
> 
> mariadb-10.1 (10.1.28-1) FTBFS on mips64el, and the missing binaries are
> blocking testing migration of mariadb-10.1 and its reverse dependencies.

The failing builds are all related to mariabackup and fail like this:
> CURRENT_TEST: mariabackup.xb_fulltext_encrypted
> mysqltest: At line 17: exec of 
> '/<>/builddir/extra/mariabackup/mariabackup --innobackupex 
> --defaults-file=/<>/builddir/mysql-test/var/4/my.cnf 
> --no-timestamp /<>/builddir/m
> ysql-test/var/4/tmp/backup 2>&1' failed, error: 34304, status: 134, errno: 0
> Output from before failure:
> *** Error in `/<>/builddir/extra/mariabackup/mariabackup': 
> malloc(): memory corruption: 0x00aab1fe43a0 ***

After running that through valgrind, it was pretty easy to find the cause.

The failures are caused by a buffer overflow in a Debian patch
"fix-FTBFS-on-GNU-Hurd.patch" which was applied as a result of #861166.

Relevant extract:
> --- a/extra/mariabackup/backup_copy.cc
> +++ b/extra/mariabackup/backup_copy.cc
> @@ -623,11 +623,13 @@ static
>  int
>  mkdirp(const char *pathname, int Flags, myf MyFlags)
>  {
> - char parent[PATH_MAX], *p;
> + char *parent, *p;
> + int len = strlen(pathname) + 1;
>  
>   /* make a parent directory path */
> - strncpy(parent, pathname, sizeof(parent));
> - parent[sizeof(parent) - 1] = 0;
> + parent = (char *)malloc(len);
> + strncpy(parent, pathname, len);
> + parent[len] = 0;
>  
>   for (p = parent + strlen(parent);
>   !is_path_separator(*p) && p != parent; p--);

"parent[len] = 0" writes past the end of the memory allocated two lines
above. I expect it should be "parent[len - 1] = 0". I've attached a
debdiff which fixes this part.

Unfortunately, after applying this patch the testsuite gets further but
some tests still fail. I am now getting the
"encryption.innodb-checksum-algorithm" test failing with a "Data
structure corruption" error which sounds bad.

Thanks,
James
diff -Nru mariadb-10.1-10.1.28/debian/patches/fix-FTBFS-on-GNU-Hurd.patch 
mariadb-10.1-10.1.28/debian/patches/fix-FTBFS-on-GNU-Hurd.patch
--- mariadb-10.1-10.1.28/debian/patches/fix-FTBFS-on-GNU-Hurd.patch 
2017-10-09 23:07:43.0 +0100
+++ mariadb-10.1-10.1.28/debian/patches/fix-FTBFS-on-GNU-Hurd.patch 
2017-10-27 16:35:29.0 +0100
@@ -59,7 +59,7 @@
 -  parent[sizeof(parent) - 1] = 0;
 +  parent = (char *)malloc(len);
 +  strncpy(parent, pathname, len);
-+  parent[len] = 0;
++  parent[len - 1] = 0;
  
for (p = parent + strlen(parent);
!is_path_separator(*p) && p != parent; p--);

Processed: your mail

[Debian Bug Tracking System]

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

> severity 846950 grave
Bug #846950 [nfs-common] nfs-common: RPCGSSDOPTS not replicated to 
/run/sysconfig/nfs-utils
Bug #849608 [nfs-common] nfs-common: For rpc.gssd, keytab location is hardcoded 
to /etc/krb5.keytab
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: Seems RC to me

[Debian Bug Tracking System]

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

> severity 879961 serious
Bug #879961 [disc-cover] disc-cover: Running disc-cover returns a Perl error 
message: Can't use 'defined(@array)' ...
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#877939: marked as done (FTBFS: t/06-sru.t)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 18:04:07 +
with message-id 
and subject line Bug#877939: fixed in libcatmandu-mab2-perl 0.21-1
has caused the Debian Bug report #877939,
regarding FTBFS: t/06-sru.t
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.)


-- 
877939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcatmandu-mab2-perl
Version: 0.14-1
Severity: serious
Tags: buster sid
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libcatmandu-mab2-perl doesn't build any more, presumably due to
changes in some libcatmandu-* dependencies.

Entity: line 1: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xF4 0x7F 0x00 0x00
can('each')
ok 3
Dubious, test returned 2 (wstat 512, 0x200)
All 3 subtests passed 
t/07-mab-each.t  
ok 1 - use Catmandu::Fix::Bind::mab_each;
ok 2 - require Catmandu::Fix::Bind::mab_each;
ok 3 - created a MAB2 record
ok 4 - created is_ger tag
ok 5 - fields 542 deleted
1..5
ok
t/author-pod-syntax.t .. skipped: these tests are for testing by the author

Test Summary Report
- ---
t/06-sru.t   (Wstat: 512 Tests: 3 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=9, Tests=61,  2 wallclock secs ( 0.04 usr  0.02 sys +  2.09 cusr  0.15 
csys =  2.30 CPU)
Result: FAIL



First seen on ci.debian.net:
https://ci.debian.net/data/autopkgtest/unstable/amd64/libc/libcatmandu-mab2-perl/20171006_154226/log.gz

t/06-sru.t ... 
ok 1 - An object of class 'Catmandu::Importer::SRU' isa 
'Catmandu::Importer::SRU'
ok 2 - Catmandu::Importer::SRU->can('each')
ok 3
Entity: line 1: parser error : error parsing attribute name
--- End Message ---
--- Begin Message ---
Source: libcatmandu-mab2-perl
Source-Version: 0.21-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libcatmandu-mab2-perl 
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, 27 Oct 2017 19:51:49 +0200
Source: libcatmandu-mab2-perl
Binary: libcatmandu-mab2-perl
Architecture: source all
Version: 0.21-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Description:
 libcatmandu-mab2-perl - modules for working with MAB2 data within the Catmandu 
framework
Closes: 877939
Changes:
 libcatmandu-mab2-perl (0.21-1) unstable; urgency=medium
 .
   [ upstream ]
   * New releases.
 Closes: Bug#877939. Thanks to Gregor Herrmann.
 .
   [ Jonas Smedegaard ]
   * Update watch file: Use substitution strings.
   * Modernize Vcs-* fields:
 + Consistently use git (not cgit) in path.
 + Consistently include .git suffix in path.
   * Declare compliance with Debian Policy 4.1.1.
   * Drop obsolete lintian override regarding debhelper 9.
   * Tighten lintian overrides regarding License-Reference.
   * Update copyright info:
 + Use https protocol in file format URL.
 + Extend coverage for myself.
   * Modernize cdbs:
 + Do copyright-check in maintainer script (not during build).
 + Stop build-depend on licensecheck.
 + Relax to build-depend unversioned on cdbs.
   * Update package relations:
 + Tighten build-dependency on libcatmandu-perl and
   libcatmandu-sru-perl.
   * Drop patch fo fix testsuite: Fixed upstream.
Checksums-Sha1:
 e2f1945c031665c6a283938cf6f9e2d32d06cefa 2329 libcatmandu-mab2-perl_0.21-1.dsc
 71e4504aea0a4730338da98bd32224d000f07226 44391 
libcatmandu-mab2-perl_0.21.orig.tar.gz
 14f5d2ef8d44ec2ccba181a48f8141a0f41d6683 4772 
libcatmandu-mab2-perl_0.21-1.debian.tar.xz
 295f89994c2a1055c7ecd04f7aa3ad95527b778a 54612 
libcatmandu-mab2-perl_0.21-1_all.deb
 5f21956b63701f51229b0d825609d3c2902470fc 9677 

Processed: python3-trollius has been removed

[Debian Bug Tracking System]

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

> severity 868203 serious
Bug #868203 [src:python-autobahn] drop depends on python3-trollius
Severity set to 'serious' from 'normal'
> tags 868203 buster sid experimental
Bug #868203 [src:python-autobahn] drop depends on python3-trollius
Added tag(s) sid, buster, and experimental.
> affects 868203 python3-autobahn
Bug #868203 [src:python-autobahn] drop depends on python3-trollius
Added indication that 868203 affects python3-autobahn
> reassign 868202 python3-qtile 0.10.7-2
Bug #868202 [src:qtile] Remove build-depends and depends on python3-trollius
Bug reassigned from package 'src:qtile' to 'python3-qtile'.
No longer marked as found in versions qtile/0.10.7-2.
Ignoring request to alter fixed versions of bug #868202 to the same values 
previously set
Bug #868202 [python3-qtile] Remove build-depends and depends on python3-trollius
Marked as found in versions qtile/0.10.7-2.
> severity 868202 serious
Bug #868202 [python3-qtile] Remove build-depends and depends on python3-trollius
Severity set to 'serious' from 'normal'
> severity 868200 serious
Bug #868200 [src:python-aioeventlet] drop build dependency on python3-trollius
Severity set to 'serious' from 'normal'
> tags 868200 buster sid
Bug #868200 [src:python-aioeventlet] drop build dependency on python3-trollius
Added tag(s) sid and buster.
> affects 868200 python3-aioeventlet
Bug #868200 [src:python-aioeventlet] drop build dependency on python3-trollius
Added indication that 868200 affects python3-aioeventlet
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 878469, affects 878469, usertagging 876608 ...

[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 878469 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 878469 + libjs-of-ocaml
Bug #878469 [src:js-of-ocaml] js-of-ocaml FTBFS: ocamlbuild: Command not found
Added indication that 878469 affects libjs-of-ocaml
> usertags 876608 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 876608 + ruby-compass-core ruby-compass-import-once
Bug #876608 [ruby-compass] ruby-compass (build) depends on ruby-sass (< 3.5), 
but 3.5.1-2 is in unstable
Added indication that 876608 affects ruby-compass-core and 
ruby-compass-import-once
> thanks
Stopping processing here.

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

Bug#879815: marked as done (eclipse-titan not installable on current stretch/amd64)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 19:09:27 +0200
with message-id <27cedce8-70e6-1550-e51d-3c6b05cba...@debian.org>
and subject line Re: Bug#879815: Acknowledgement (eclipse-titan not installable 
on current stretch/amd64)
has caused the Debian Bug report #879815,
regarding eclipse-titan not installable on current stretch/amd64
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.)


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

When trying to install eclipse-titan on a current stetch/amd64,
I get:

The following packages have unmet dependencies:
 eclipse-titan : Depends: libssl-dev but it is not going to be installed

This is with the following (only) line in /etc/apt/sources.list:

deb http://ftp.de.debian.org/debian/ unstable main contrib non-free

and just after "apt-get update".

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

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

Versions of packages eclipse-titan depends on:
ii  default-jdk   2:1.8-59
ii  expect5.45-8
ii  libc6 2.24-17
ii  libgcc1   1:7.2.0-11
ii  libncurses5   6.0+20170902-1
ii  libpcap-dev   1.8.1-5
ii  libpcre3-dev  2:8.39-5
ii  libsctp-dev   1.0.17+dfsg-1+b1
pn  libssl-dev
ii  libssl1.1 1.1.0f-5
ii  libstdc++67.2.0-11
ii  libtinfo5 6.0+20170902-1
ii  libxml2   2.9.4+dfsg1-5
ii  libxml2-dev   2.9.4+dfsg1-5
ii  make  4.1-9.1
ii  perl  5.26.0-8
ii  python2.7.14-1

eclipse-titan recommends no packages.

eclipse-titan suggests no packages.
--- End Message ---
--- Begin Message ---
On Thu, 26 Oct 2017 14:11:32 +0200 Harald Welte 
wrote:
> I'm sorry, this is a bogus report.  I figure out it was a misconfiguration
> on my machine, sorry for the noise. Please close.

Thanks, closing.

Andreas--- End Message ---

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

[Luca Boccassi]

On Thu, 2017-10-26 at 23:37 +0200, Andreas Beckmann wrote:
> On 10/26/2017 11:13 PM, Rafał Olejnik wrote:
> > Guess having amd64 and i386 might be a reason because on my sid i'm
> > getting same error.
> 
> having both :amd64 and :i386 packages installed does not seem to work
> properly with versioned Provides/Breaks in this special case.
> 
> minimal testcase is libgles1-glvnd-nvidia:amd64 +
> libgles1-glvnd-nvidia:i386 in a minimal chroot (without
> --install-recommends) that gets upgraded from buster to sid.
> 
> workaround should be
> 
> dpkg -r libgles1-glvnd-nvidia:amd64 libgles1-glvnd-nvidia:i386
> 
> (the mesa packages already dropped GLESv1 support)

What's GLESv1 used for these days? Can we consider dropping it as well?

-- 
Kind regards,
Luca Boccassi

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

Bug#879951: marked as done (gpsd-clients,gpsd: both ship /usr/share/man/man8/ppscheck.8.gz)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 16:03:54 +
with message-id 
and subject line Bug#879951: fixed in gpsd 3.17-3
has caused the Debian Bug report #879951,
regarding gpsd-clients,gpsd: both ship /usr/share/man/man8/ppscheck.8.gz
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.)


-- 
879951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpsd-clients,gpsd
Version: 3.17-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package gpsd.
  Preparing to unpack .../archives/gpsd_3.17-1_amd64.deb ...
  Unpacking gpsd (3.17-1) ...
  dpkg: error processing archive /var/cache/apt/archives/gpsd_3.17-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man8/ppscheck.8.gz', which is also in 
package gpsd-clients 3.17-1
  Errors were encountered while processing:
   /var/cache/apt/archives/gpsd_3.17-1_amd64.deb


cheers,

Andreas


gpsd-clients=3.17-1_gpsd=3.17-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gpsd
Source-Version: 3.17-3

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated gpsd 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: Fri, 27 Oct 2017 17:26:55 +0200
Source: gpsd
Binary: gpsd gpsd-dbg gpsd-clients python-gps libgps23 libgps-dev libqgpsmm23 
libqgpsmm-dev
Architecture: source
Version: 3.17-3
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Description:
 gpsd   - Global Positioning System - daemon
 gpsd-clients - Global Positioning System - clients
 gpsd-dbg   - Global Positioning System - debugging symbols
 libgps-dev - Global Positioning System - development files
 libgps23   - Global Positioning System - library
 libqgpsmm-dev - Global Positioning System - Qt wrapper for libgps (development)
 libqgpsmm23 - Global Positioning System - Qt wrapper for libgps
 python-gps - Global Positioning System - Python libraries
Closes: 879951
Changes:
 gpsd (3.17-3) unstable; urgency=medium
 .
   * [2638b3e] Avoid duplicate ppscheck installation.
 Thanks to Andreas Beckmann (Closes: #879951)
Checksums-Sha1:
 9d8b517935429fced566f87e4108871cf3f579b3 2547 gpsd_3.17-3.dsc
 4773b6a96b09ccd176ea0ffd6a43345f5ed00424 34704 gpsd_3.17-3.debian.tar.xz
 5d38a9a2332b3d2a3071938621c6416f543b13b6 9089 gpsd_3.17-3_source.buildinfo
Checksums-Sha256:
 6ce1f04e925480b334c033f9e82c7a1078bfdcbd3e713af8ce7108eeb057b2f6 2547 
gpsd_3.17-3.dsc
 b9f450bfff3f481a36b1aacda4aa462b471e3878d4f3a2d90374ed8db30b 34704 
gpsd_3.17-3.debian.tar.xz
 e5eafb79fe7c34d6f9bfa8d87595c069fb2e8fba799b0a12d9d4d669f3c1eb59 9089 
gpsd_3.17-3_source.buildinfo
Files:
 0f8c0d8703a68ba2c22dd73eaab3aecc 2547 misc optional gpsd_3.17-3.dsc
 2db90f9a0e96caaa1737ca509d466e07 34704 misc optional gpsd_3.17-3.debian.tar.xz
 f83e353f565185ea3f29b1ce8706a214 9089 misc optional 
gpsd_3.17-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAlnzVDEACgkQ6zYXGm/5
Q1+WlA//UPefljhfz0t7Rg70axj65juHb0t8e3ykB5+ad0ttIQMoNTNPXxgfgSYq
YTBkEL1kzd5kUwyAyIb0M8cHMkA4IYGwao0qMwAGQCKM/rqpXfJaf6sTkqM046Ej
VQnV10MiPkvBG2/91QC1zlGXu+8NZ73++KNkNv6Hu0wTr78zMIbIYktg0yr/lCsu
wcIk3gmXM1EP8fdm5Frum2bO0xoTMKjgOOq3mxABmY4HF48yyCYbTQDYxpbtfTfo
lLAkxWHs9kSvXuc2OXcX/OuAzsFpaOgIlq4S0o+6FjuBXyLpqy0M02Bd1aTbxjse
fG4i7Atnt2I9c1vxntBEtABUP+Yr+2794/FEQAfTsKEGOYn9ZGyJoHDz4HbW2m15
Vje84OsGcm6fakAqK/imwDoDBarqPmT3YydLT/5X3euBv0cXcrEt0869Dy5eGLnK
+Dh5Dry0/N0nEBYHG/P4iS3awlNkWnrPVc3CE+ViHZau4MPdF49fzg2Yr6G/XG4e
P4B9S9wwggN59tb26HxeToktHAkgPPvaem9DpDvjZK/XWtytflb00f2OXDxARDUj

Processed: Re: Bug#879941: awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/awesomeWM/awesome/issues/2086
Bug #879941 [src:awesome] awesome: FTBFS on s390x: 7 tests fail, all in 
color_spec.lua
Set Bug forwarded-to-address to 
'https://github.com/awesomeWM/awesome/issues/2086'.

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

Bug#879941: awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua

[Reiner Herrmann]

Control: forwarded -1 https://github.com/awesomeWM/awesome/issues/2086

On Fri, Oct 27, 2017 at 09:31:00AM -0400, Aaron M. Ucko wrote:
> The latest build of awesome for s390x failed with seven unit test
> errors, all in color_spec.lua, per the below excerpt from
> https://buildd.debian.org/status/fetch.php?pkg=awesome=s390x=4.2-2=1508945611=0
> 
> Could you please take a look?

Thanks for the report.
I also noticed it already and asked upstream about it.
The problem seems to be in lua-lgi, not in awesome itself.
I'll open a bug against it as well.

Regards,
  Reiner


signature.asc
Description: PGP signature

Processed: found 879521 in 0.8.17-1

[Debian Bug Tracking System]

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

> found 879521 0.8.17-1
Bug #879521 [src:irssi] irssi: multiple vulnerabilities fixed in irssi 1.0.5
Marked as found in versions irssi/0.8.17-1.
> thanks
Stopping processing here.

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

Processed: tagging 879521

[Debian Bug Tracking System]

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

> tags 879521 + upstream fixed-upstream
Bug #879521 [src:irssi] irssi: multiple vulnerabilities fixed in irssi 1.0.5
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: found 879521 in 1.0.4-1

[Debian Bug Tracking System]

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

> found 879521 1.0.4-1
Bug #879521 [src:irssi] irssi: multiple vulnerabilities fixed in irssi 1.0.5
Marked as found in versions irssi/1.0.4-1.
> thanks
Stopping processing here.

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

Bug#867725: found 867725 in 3.99.5+repack1-7, closing 867725

[Salvatore Bonaccorso]

found 867725 3.99.5+repack1-7
# Cf. notes in security-tracker for information about why marked as
# fixed in 3.99.5+repack1-8
close 867725 3.99.5+repack1-8
thanks

Processed: found 867725 in 3.99.5+repack1-7, closing 867725

[Debian Bug Tracking System]

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

> found 867725 3.99.5+repack1-7
Bug #867725 [src:lame] CVE-2017-9869 CVE-2017-9870 CVE-2017-9871 CVE-2017-9872
Marked as found in versions lame/3.99.5+repack1-7.
> # Cf. notes in security-tracker for information about why marked as
> # fixed in 3.99.5+repack1-8
> close 867725 3.99.5+repack1-8
Bug #867725 [src:lame] CVE-2017-9869 CVE-2017-9870 CVE-2017-9871 CVE-2017-9872
Marked as fixed in versions lame/3.99.5+repack1-8.
Bug #867725 [src:lame] CVE-2017-9869 CVE-2017-9870 CVE-2017-9871 CVE-2017-9872
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#871138: marked as done (vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vcdimager
Version: 0.7.24+dfsg-0.2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../include/ -I../lib/
>  -g -O2 -MT info2.o -MD -MP -MF .deps/info2.Tpo -c -o info2.o info2.cpp
> In file included from ../include/libvcd/info.h:37:0,
>  from info2.cpp:34:
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
> iso9660_pvd_s'
>  struct iso9660_pvd_s {
> ^
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:424:20: note: next member 'char 
> iso9660_svd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
> iso9660_svd_s'
>  struct iso9660_svd_s {
> ^
> Makefile:450: recipe for target 'info2.o' failed
> make[3]: *** [info2.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/vcdimager_0.7.24+dfsg-0.2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libcdio 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, 26 Oct 2017 14:19:26 +0200
Source: libcdio
Binary: libcdio-dev libcdio16 libiso9660-dev libiso9660-10 libudf-dev libudf0 
libcdio-utils
Architecture: source amd64
Version: 0.94-0.2
Distribution: experimental
Urgency: medium
Maintainer: Nicolas Boullis 
Changed-By: Matthias Klose 
Description:
 libcdio-dev - library to read and control CD-ROM (development files)
 libcdio-utils - sample applications based on the CDIO libraries
 libcdio16  - library to read and control CD-ROM
 libiso9660-10 - library to work with ISO9660 filesystems
 libiso9660-dev - library to work with ISO9660 filesystems (development files)
 libudf-dev - library to work with UDF filesystems (development files)
 libudf0- library to work with UDF filesystems
Closes: 841556 869516
Changes:
 libcdio (0.94-0.2) experimental; urgency=medium
 .
   

Bug#871121: marked as done (mpd: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding mpd: FTBFS: iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpd
Version: 0.20.9-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
> -DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"'  -DCPPUNIT_HAVE_RTTI=0 
> -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread 
> -Wno-error=deprecated-declarations -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
> -fmerge-all-constants -ffast-math -ftree-vectorize -ffunction-sections 
> -fdata-sections -Wall -Wextra -Wmissing-declarations -Wshadow -Wpointer-arith 
> -Wcast-qual -Wwrite-strings -Wsign-compare -c -o 
> test/test_test_byte_reverse-test_byte_reverse.o `test -f 
> 'test/test_byte_reverse.cxx' || echo './'`test/test_byte_reverse.cxx
> rm -f libmpd.a
> ar cru libmpd.a src/output/libmpd_a-Internal.o src/output/libmpd_a-Registry.o 
> src/output/libmpd_a-MultipleOutputs.o 
> src/output/libmpd_a-SharedPipeConsumer.o src/output/libmpd_a-Source.o 
> src/output/libmpd_a-OutputThread.o src/output/libmpd_a-Domain.o 
> src/output/libmpd_a-OutputControl.o src/output/libmpd_a-OutputState.o 
> src/output/libmpd_a-OutputPrint.o src/output/libmpd_a-OutputCommand.o 
> src/output/libmpd_a-OutputPlugin.o src/output/libmpd_a-Finish.o 
> src/output/libmpd_a-Init.o src/mixer/libmpd_a-MixerControl.o 
> src/mixer/libmpd_a-MixerType.o src/mixer/libmpd_a-MixerAll.o 
> src/libmpd_a-notify.o src/protocol/libmpd_a-Ack.o 
> src/protocol/libmpd_a-ArgParser.o src/protocol/libmpd_a-Result.o 
> src/command/libmpd_a-CommandError.o src/command/libmpd_a-AllCommands.o 
> src/command/libmpd_a-QueueCommands.o src/command/libmpd_a-TagCommands.o 
> src/command/libmpd_a-PlayerCommands.o src/command/libmpd_a-PlaylistCommands.o 
> src/command/libmpd_a-FileCommands.o src/command/libmpd_a-OutputCommands.o 
> src/command/libmpd_a-MessageCommands.o src/command/libmpd_a-OtherCommands.o 
> src/command/libmpd_a-CommandListBuilder.o src/libmpd_a-Idle.o 
> src/libmpd_a-IdleFlags.o src/decoder/libmpd_a-DecoderError.o 
> src/decoder/libmpd_a-DecoderThread.o src/decoder/libmpd_a-DecoderControl.o 
> src/decoder/libmpd_a-Bridge.o src/decoder/libmpd_a-DecoderPrint.o 
> src/filter/libmpd_a-FilterConfig.o src/filter/libmpd_a-FilterPlugin.o 
> src/filter/libmpd_a-FilterRegistry.o src/filter/libmpd_a-Observer.o 
> src/client/libmpd_a-Client.o src/client/libmpd_a-ClientEvent.o 
> src/client/libmpd_a-ClientExpire.o src/client/libmpd_a-ClientGlobal.o 
> src/client/libmpd_a-ClientIdle.o src/client/libmpd_a-ClientList.o 
> src/client/libmpd_a-ClientNew.o src/client/libmpd_a-ClientProcess.o 
> src/client/libmpd_a-ClientRead.o src/client/libmpd_a-ClientWrite.o 
> src/client/libmpd_a-ClientMessage.o src/client/libmpd_a-ClientSubscribe.o 
> src/client/libmpd_a-ClientFile.o src/client/libmpd_a-Response.o 
> src/libmpd_a-Listen.o src/libmpd_a-LogInit.o src/libmpd_a-LogBackend.o 
> src/libmpd_a-Log.o src/libmpd_a-ls.o src/libmpd_a-IOThread.o 
> src/libmpd_a-Instance.o src/win32/libmpd_a-Win32Main.o 
> src/libmpd_a-MusicBuffer.o src/libmpd_a-MusicPipe.o src/libmpd_a-MusicChunk.o 
> src/libmpd_a-Mapper.o src/libmpd_a-Partition.o src/libmpd_a-Permission.o 
> src/player/libmpd_a-CrossFade.o src/player/libmpd_a-Thread.o 
> src/player/libmpd_a-Control.o src/libmpd_a-PlaylistError.o 
> src/libmpd_a-PlaylistPrint.o src/libmpd_a-PlaylistSave.o 
> src/playlist/libmpd_a-PlaylistStream.o src/playlist/libmpd_a-PlaylistMapper.o 
> src/playlist/libmpd_a-PlaylistAny.o src/playlist/libmpd_a-PlaylistSong.o 
> src/playlist/libmpd_a-PlaylistQueue.o src/playlist/libmpd_a-Print.o 
> src/db/libmpd_a-PlaylistVector.o src/queue/libmpd_a-Queue.o 
> src/queue/libmpd_a-QueuePrint.o src/queue/libmpd_a-QueueSave.o 
> src/queue/libmpd_a-Playlist.o src/queue/libmpd_a-PlaylistControl.o 
> src/queue/libmpd_a-PlaylistEdit.o src/queue/libmpd_a-PlaylistTag.o 
> 

Bug#853484: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcdio
Version: 0.83-4.2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libcdio_0.83-4.2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[4]: Leaving directory '/<>/lib/paranoia'
Making all in cdio++
make[4]: Entering directory '/<>/lib/cdio++'
/bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I../../include-g -O2 -MT 
iso9660.lo -MD -MP -MF .deps/iso9660.Tpo -c -o iso9660.lo iso9660.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
-I../../include/ -I../../include -g -O2 -MT iso9660.lo -MD -MP -MF 
.deps/iso9660.Tpo -c iso9660.cpp  -fPIC -DPIC -o .libs/iso9660.o
In file included from ../../include/cdio++/iso9660.hpp:27:0,
 from iso9660.cpp:27:
../../include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
../../include/cdio/iso9660.h:310:20: note: next member 'char 
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
../../include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
iso9660_pvd_s'
 struct iso9660_pvd_s {
^
../../include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
../../include/cdio/iso9660.h:424:20: note: next member 'char 
iso9660_svd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
../../include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
iso9660_svd_s'
 struct iso9660_svd_s {
^
../../include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'class ISO9660::PVD'
   char filename[EMPTY_ARRAY_SIZE];
 ^
../../include/cdio/iso9660.h:310:20: note: next member 'char 
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
In file included from iso9660.cpp:27:0:
../../include/cdio++/iso9660.hpp:41:9: note: in the definition of 'class 
ISO9660::PVD'
   class PVD  // Primary Volume ID
 ^~~
Makefile:545: recipe for target 'iso9660.lo' failed
make[4]: *** [iso9660.lo] Error 1
make[4]: Leaving directory '/<>/lib/cdio++'
Makefile:425: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/lib'
Makefile:584: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:477: recipe for target 'all' failed

Bug#853561: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpd
Version: 0.19.21-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mpd_0.19.21-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize -ffunction-sections -fdata-sections -Wall -Wextra 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings 
-Wsign-compare  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
test/run_avahi src/test_run_avahi-Log.o src/test_run_avahi-LogBackend.o 
src/zeroconf/test_run_avahi-ZeroconfAvahi.o 
src/zeroconf/test_run_avahi-AvahiPoll.o test/test_run_avahi-ShutdownHandler.o 
test/test_run_avahi-run_avahi.o libevent.a libsystem.a libutil.a -lgthread-2.0 
-pthread -lglib-2.0 -lavahi-common -lavahi-client -ldbus-1 -lm 
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize -ffunction-sections -fdata-sections -Wall -Wextra 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings 
-Wsign-compare  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
src/pcm/dsd2pcm/dsd2pcm src/pcm/dsd2pcm/dsd2pcm.o src/pcm/dsd2pcm/noiseshape.o 
src/pcm/dsd2pcm/main.o libutil.a -lm 
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize -ffunction-sections -fdata-sections -Wall -Wextra 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings 
-Wsign-compare  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
test/run_inotify test/run_inotify.o test/ShutdownHandler.o src/Log.o 
src/LogBackend.o src/db/update/InotifyDomain.o src/db/update/InotifySource.o 
libevent.a libsystem.a libutil.a -lgthread-2.0 -pthread -lglib-2.0 -lm 
g++ -pthread -Wno-error=deprecated-declarations -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
-fmerge-all-constants -fno-exceptions -fno-rtti -ffast-math -ftree-vectorize 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare  
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
test/test_icy_parser src/test_test_icy_parser-Log.o 
src/test_test_icy_parser-LogBackend.o 
test/test_test_icy_parser-test_icy_parser.o libtag.a libutil.a -lgthread-2.0 
-pthread -lglib-2.0 -lcppunit -lm 
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize 

Bug#841556: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpd
Version: 0.19.19-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include 
> -DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"'-Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
> -fmerge-all-constants -fno-exceptions -fno-rtti -ffast-math -ftree-vectorize 
> -ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
> -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare -c -o 
> src/archive/plugins/libarchive_a-Iso9660ArchivePlugin.o `test -f 
> 'src/archive/plugins/Iso9660ArchivePlugin.cxx' || echo 
> './'`src/archive/plugins/Iso9660ArchivePlugin.cxx
> In file included from src/archive/plugins/Iso9660ArchivePlugin.cxx:36:0:
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
> iso9660_pvd_s'
>  struct iso9660_pvd_s {
> ^
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:424:20: note: next member 'char 
> iso9660_svd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
> iso9660_svd_s'
>  struct iso9660_svd_s {
> ^
> Makefile:7302: recipe for target 
> 'src/archive/plugins/libarchive_a-Iso9660ArchivePlugin.o' failed
> make[3]: *** [src/archive/plugins/libarchive_a-Iso9660ArchivePlugin.o] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/mpd_0.19.19-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libcdio package)

(This message 

Bug#841624: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcdio
Version: 0.83-4.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I../../include-g -O2 -MT 
> iso9660.lo -MD -MP -MF .deps/iso9660.Tpo -c -o iso9660.lo iso9660.cpp
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
> -I../../include/ -I../../include -g -O2 -MT iso9660.lo -MD -MP -MF 
> .deps/iso9660.Tpo -c iso9660.cpp  -fPIC -DPIC -o .libs/iso9660.o
> In file included from ../../include/cdio++/iso9660.hpp:27:0,
>  from iso9660.cpp:27:
> ../../include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> ../../include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> ../../include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
> iso9660_pvd_s'
>  struct iso9660_pvd_s {
> ^
> ../../include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> ../../include/cdio/iso9660.h:424:20: note: next member 'char 
> iso9660_svd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> ../../include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
> iso9660_svd_s'
>  struct iso9660_svd_s {
> ^
> ../../include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'class ISO9660::PVD'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> ../../include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> In file included from iso9660.cpp:27:0:
> ../../include/cdio++/iso9660.hpp:41:9: note: in the definition of 'class 
> ISO9660::PVD'
>class PVD  // Primary Volume ID
>  ^~~
> Makefile:545: recipe for target 'iso9660.lo' failed
> make[4]: *** [iso9660.lo] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/libcdio_0.83-4.2_unstable.log

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

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

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

Bug#853697: marked as done (vcdimager: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:20 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.2
has caused the Debian Bug report #841556,
regarding vcdimager: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vcdimager
Version: 0.7.24+dfsg-0.2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/vcdimager_0.7.24+dfsg-0.2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
/bin/bash ../libtool  --tag=CC   --mode=link x86_64-linux-gnu-gcc  -g -Wall -O2 
 -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused 
-Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare   -o testvcd 
testvcd.o -liso9660 -lcdio -lm ../lib/libvcdinfo.la ../lib/libvcd.la -lm
libtool: link: x86_64-linux-gnu-gcc -g -Wall -O2 -Wall -Wchar-subscripts 
-Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith 
-Wwrite-strings -Wnested-externs -Wno-sign-compare -o .libs/testvcd testvcd.o  
../lib/.libs/libvcdinfo.so ../lib/.libs/libvcd.a -liso9660 -lcdio -lm
make[3]: Leaving directory '/<>/vcdimager-0.7.24+dfsg/test'
Making all in amiga
make[3]: Entering directory '/<>/vcdimager-0.7.24+dfsg/amiga'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/vcdimager-0.7.24+dfsg/amiga'
Making all in docs
make[3]: Entering directory '/<>/vcdimager-0.7.24+dfsg/docs'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/vcdimager-0.7.24+dfsg/docs'
Making all in example
make[3]: Entering directory '/<>/vcdimager-0.7.24+dfsg/example'
x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include/ -I../lib/ 
-g -Wall -O2  -Wall -Wchar-subscripts -Wmissing-prototypes 
-Wmissing-declarations -Wunused -Wpointer-arith -Wwrite-strings 
-Wnested-externs -Wno-sign-compare -MT info1.o -MD -MP -MF .deps/info1.Tpo -c 
-o info1.o info1.c
mv -f .deps/info1.Tpo .deps/info1.Po
/bin/bash ../libtool  --tag=CC   --mode=link x86_64-linux-gnu-gcc  -g -Wall -O2 
 -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused 
-Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare   -o info1 
info1.o ../lib/libvcdinfo.la ../lib/libvcd.la -liso9660 -lcdio -lm -lm
libtool: link: x86_64-linux-gnu-gcc -g -Wall -O2 -Wall -Wchar-subscripts 
-Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith 
-Wwrite-strings -Wnested-externs -Wno-sign-compare -o .libs/info1 info1.o  
../lib/.libs/libvcdinfo.so ../lib/.libs/libvcd.a -liso9660 -lcdio -lm
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../include/ -I../lib/ 
-g -O2 -MT info2.o -MD -MP -MF .deps/info2.Tpo -c -o info2.o info2.cpp
In file included from ../include/libvcd/info.h:37:0,
 from info2.cpp:34:
/usr/include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
/usr/include/cdio/iso9660.h:310:20: note: next member 'char 
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
/usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
iso9660_pvd_s'
 struct iso9660_pvd_s 

Bug#853561: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpd
Version: 0.19.21-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mpd_0.19.21-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize -ffunction-sections -fdata-sections -Wall -Wextra 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings 
-Wsign-compare  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
test/run_avahi src/test_run_avahi-Log.o src/test_run_avahi-LogBackend.o 
src/zeroconf/test_run_avahi-ZeroconfAvahi.o 
src/zeroconf/test_run_avahi-AvahiPoll.o test/test_run_avahi-ShutdownHandler.o 
test/test_run_avahi-run_avahi.o libevent.a libsystem.a libutil.a -lgthread-2.0 
-pthread -lglib-2.0 -lavahi-common -lavahi-client -ldbus-1 -lm 
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize -ffunction-sections -fdata-sections -Wall -Wextra 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings 
-Wsign-compare  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
src/pcm/dsd2pcm/dsd2pcm src/pcm/dsd2pcm/dsd2pcm.o src/pcm/dsd2pcm/noiseshape.o 
src/pcm/dsd2pcm/main.o libutil.a -lm 
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize -ffunction-sections -fdata-sections -Wall -Wextra 
-Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings 
-Wsign-compare  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
test/run_inotify test/run_inotify.o test/ShutdownHandler.o src/Log.o 
src/LogBackend.o src/db/update/InotifyDomain.o src/db/update/InotifySource.o 
libevent.a libsystem.a libutil.a -lgthread-2.0 -pthread -lglib-2.0 -lm 
g++ -pthread -Wno-error=deprecated-declarations -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
-fmerge-all-constants -fno-exceptions -fno-rtti -ffast-math -ftree-vectorize 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare  
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--gc-sections -o 
test/test_icy_parser src/test_test_icy_parser-Log.o 
src/test_test_icy_parser-LogBackend.o 
test/test_test_icy_parser-test_icy_parser.o libtag.a libutil.a -lgthread-2.0 
-pthread -lglib-2.0 -lcppunit -lm 
g++ -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -fno-exceptions -fno-rtti 
-ffast-math -ftree-vectorize 

Bug#871121: marked as done (mpd: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding mpd: FTBFS: iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpd
Version: 0.20.9-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
> -DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"'  -DCPPUNIT_HAVE_RTTI=0 
> -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread 
> -Wno-error=deprecated-declarations -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
> -fmerge-all-constants -ffast-math -ftree-vectorize -ffunction-sections 
> -fdata-sections -Wall -Wextra -Wmissing-declarations -Wshadow -Wpointer-arith 
> -Wcast-qual -Wwrite-strings -Wsign-compare -c -o 
> test/test_test_byte_reverse-test_byte_reverse.o `test -f 
> 'test/test_byte_reverse.cxx' || echo './'`test/test_byte_reverse.cxx
> rm -f libmpd.a
> ar cru libmpd.a src/output/libmpd_a-Internal.o src/output/libmpd_a-Registry.o 
> src/output/libmpd_a-MultipleOutputs.o 
> src/output/libmpd_a-SharedPipeConsumer.o src/output/libmpd_a-Source.o 
> src/output/libmpd_a-OutputThread.o src/output/libmpd_a-Domain.o 
> src/output/libmpd_a-OutputControl.o src/output/libmpd_a-OutputState.o 
> src/output/libmpd_a-OutputPrint.o src/output/libmpd_a-OutputCommand.o 
> src/output/libmpd_a-OutputPlugin.o src/output/libmpd_a-Finish.o 
> src/output/libmpd_a-Init.o src/mixer/libmpd_a-MixerControl.o 
> src/mixer/libmpd_a-MixerType.o src/mixer/libmpd_a-MixerAll.o 
> src/libmpd_a-notify.o src/protocol/libmpd_a-Ack.o 
> src/protocol/libmpd_a-ArgParser.o src/protocol/libmpd_a-Result.o 
> src/command/libmpd_a-CommandError.o src/command/libmpd_a-AllCommands.o 
> src/command/libmpd_a-QueueCommands.o src/command/libmpd_a-TagCommands.o 
> src/command/libmpd_a-PlayerCommands.o src/command/libmpd_a-PlaylistCommands.o 
> src/command/libmpd_a-FileCommands.o src/command/libmpd_a-OutputCommands.o 
> src/command/libmpd_a-MessageCommands.o src/command/libmpd_a-OtherCommands.o 
> src/command/libmpd_a-CommandListBuilder.o src/libmpd_a-Idle.o 
> src/libmpd_a-IdleFlags.o src/decoder/libmpd_a-DecoderError.o 
> src/decoder/libmpd_a-DecoderThread.o src/decoder/libmpd_a-DecoderControl.o 
> src/decoder/libmpd_a-Bridge.o src/decoder/libmpd_a-DecoderPrint.o 
> src/filter/libmpd_a-FilterConfig.o src/filter/libmpd_a-FilterPlugin.o 
> src/filter/libmpd_a-FilterRegistry.o src/filter/libmpd_a-Observer.o 
> src/client/libmpd_a-Client.o src/client/libmpd_a-ClientEvent.o 
> src/client/libmpd_a-ClientExpire.o src/client/libmpd_a-ClientGlobal.o 
> src/client/libmpd_a-ClientIdle.o src/client/libmpd_a-ClientList.o 
> src/client/libmpd_a-ClientNew.o src/client/libmpd_a-ClientProcess.o 
> src/client/libmpd_a-ClientRead.o src/client/libmpd_a-ClientWrite.o 
> src/client/libmpd_a-ClientMessage.o src/client/libmpd_a-ClientSubscribe.o 
> src/client/libmpd_a-ClientFile.o src/client/libmpd_a-Response.o 
> src/libmpd_a-Listen.o src/libmpd_a-LogInit.o src/libmpd_a-LogBackend.o 
> src/libmpd_a-Log.o src/libmpd_a-ls.o src/libmpd_a-IOThread.o 
> src/libmpd_a-Instance.o src/win32/libmpd_a-Win32Main.o 
> src/libmpd_a-MusicBuffer.o src/libmpd_a-MusicPipe.o src/libmpd_a-MusicChunk.o 
> src/libmpd_a-Mapper.o src/libmpd_a-Partition.o src/libmpd_a-Permission.o 
> src/player/libmpd_a-CrossFade.o src/player/libmpd_a-Thread.o 
> src/player/libmpd_a-Control.o src/libmpd_a-PlaylistError.o 
> src/libmpd_a-PlaylistPrint.o src/libmpd_a-PlaylistSave.o 
> src/playlist/libmpd_a-PlaylistStream.o src/playlist/libmpd_a-PlaylistMapper.o 
> src/playlist/libmpd_a-PlaylistAny.o src/playlist/libmpd_a-PlaylistSong.o 
> src/playlist/libmpd_a-PlaylistQueue.o src/playlist/libmpd_a-Print.o 
> src/db/libmpd_a-PlaylistVector.o src/queue/libmpd_a-Queue.o 
> src/queue/libmpd_a-QueuePrint.o src/queue/libmpd_a-QueueSave.o 
> src/queue/libmpd_a-Playlist.o src/queue/libmpd_a-PlaylistControl.o 
> src/queue/libmpd_a-PlaylistEdit.o src/queue/libmpd_a-PlaylistTag.o 
> 

Bug#871138: marked as done (vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s')

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding vcdimager: FTBFS: iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vcdimager
Version: 0.7.24+dfsg-0.2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../include/ -I../lib/
>  -g -O2 -MT info2.o -MD -MP -MF .deps/info2.Tpo -c -o info2.o info2.cpp
> In file included from ../include/libvcd/info.h:37:0,
>  from info2.cpp:34:
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
> iso9660_pvd_s'
>  struct iso9660_pvd_s {
> ^
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:424:20: note: next member 'char 
> iso9660_svd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
> iso9660_svd_s'
>  struct iso9660_svd_s {
> ^
> Makefile:450: recipe for target 'info2.o' failed
> make[3]: *** [info2.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/vcdimager_0.7.24+dfsg-0.2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libcdio 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, 26 Oct 2017 12:55:26 +0200
Source: libcdio
Binary: libcdio-dev libcdio16 libiso9660-dev libiso9660-10 libudf-dev libudf0 
libcdio-utils
Architecture: source amd64
Version: 0.94-0.1
Distribution: experimental
Urgency: medium
Maintainer: Nicolas Boullis 
Changed-By: Matthias Klose 
Description:
 libcdio-dev - library to read and control CD-ROM (development files)
 libcdio-utils - sample applications based on the CDIO libraries
 libcdio16  - library to read and control CD-ROM
 libiso9660-10 - library to work with ISO9660 filesystems
 libiso9660-dev - library to work with ISO9660 filesystems (development files)
 libudf-dev - library to work with UDF filesystems (development files)
 libudf0- library to work with UDF filesystems
Closes: 841556 869516
Changes:
 libcdio (0.94-0.1) experimental; urgency=medium
 .
   

Bug#853697: marked as done (vcdimager: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding vcdimager: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vcdimager
Version: 0.7.24+dfsg-0.2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/vcdimager_0.7.24+dfsg-0.2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
/bin/bash ../libtool  --tag=CC   --mode=link x86_64-linux-gnu-gcc  -g -Wall -O2 
 -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused 
-Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare   -o testvcd 
testvcd.o -liso9660 -lcdio -lm ../lib/libvcdinfo.la ../lib/libvcd.la -lm
libtool: link: x86_64-linux-gnu-gcc -g -Wall -O2 -Wall -Wchar-subscripts 
-Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith 
-Wwrite-strings -Wnested-externs -Wno-sign-compare -o .libs/testvcd testvcd.o  
../lib/.libs/libvcdinfo.so ../lib/.libs/libvcd.a -liso9660 -lcdio -lm
make[3]: Leaving directory '/<>/vcdimager-0.7.24+dfsg/test'
Making all in amiga
make[3]: Entering directory '/<>/vcdimager-0.7.24+dfsg/amiga'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/vcdimager-0.7.24+dfsg/amiga'
Making all in docs
make[3]: Entering directory '/<>/vcdimager-0.7.24+dfsg/docs'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/vcdimager-0.7.24+dfsg/docs'
Making all in example
make[3]: Entering directory '/<>/vcdimager-0.7.24+dfsg/example'
x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include/ -I../lib/ 
-g -Wall -O2  -Wall -Wchar-subscripts -Wmissing-prototypes 
-Wmissing-declarations -Wunused -Wpointer-arith -Wwrite-strings 
-Wnested-externs -Wno-sign-compare -MT info1.o -MD -MP -MF .deps/info1.Tpo -c 
-o info1.o info1.c
mv -f .deps/info1.Tpo .deps/info1.Po
/bin/bash ../libtool  --tag=CC   --mode=link x86_64-linux-gnu-gcc  -g -Wall -O2 
 -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused 
-Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare   -o info1 
info1.o ../lib/libvcdinfo.la ../lib/libvcd.la -liso9660 -lcdio -lm -lm
libtool: link: x86_64-linux-gnu-gcc -g -Wall -O2 -Wall -Wchar-subscripts 
-Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith 
-Wwrite-strings -Wnested-externs -Wno-sign-compare -o .libs/info1 info1.o  
../lib/.libs/libvcdinfo.so ../lib/.libs/libvcd.a -liso9660 -lcdio -lm
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../include/ -I../lib/ 
-g -O2 -MT info2.o -MD -MP -MF .deps/info2.Tpo -c -o info2.o info2.cpp
In file included from ../include/libvcd/info.h:37:0,
 from info2.cpp:34:
/usr/include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
/usr/include/cdio/iso9660.h:310:20: note: next member 'char 
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
/usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
iso9660_pvd_s'
 struct iso9660_pvd_s 

Bug#841556: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpd
Version: 0.19.19-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include 
> -DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"'-Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pthread -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -fvisibility=hidden -fno-threadsafe-statics 
> -fmerge-all-constants -fno-exceptions -fno-rtti -ffast-math -ftree-vectorize 
> -ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
> -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare -c -o 
> src/archive/plugins/libarchive_a-Iso9660ArchivePlugin.o `test -f 
> 'src/archive/plugins/Iso9660ArchivePlugin.cxx' || echo 
> './'`src/archive/plugins/Iso9660ArchivePlugin.cxx
> In file included from src/archive/plugins/Iso9660ArchivePlugin.cxx:36:0:
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
> iso9660_pvd_s'
>  struct iso9660_pvd_s {
> ^
> /usr/include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> /usr/include/cdio/iso9660.h:424:20: note: next member 'char 
> iso9660_svd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> /usr/include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
> iso9660_svd_s'
>  struct iso9660_svd_s {
> ^
> Makefile:7302: recipe for target 
> 'src/archive/plugins/libarchive_a-Iso9660ArchivePlugin.o' failed
> make[3]: *** [src/archive/plugins/libarchive_a-Iso9660ArchivePlugin.o] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/mpd_0.19.19-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libcdio package)

(This message 

Bug#853484: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcdio
Version: 0.83-4.2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libcdio_0.83-4.2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[4]: Leaving directory '/<>/lib/paranoia'
Making all in cdio++
make[4]: Entering directory '/<>/lib/cdio++'
/bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I../../include-g -O2 -MT 
iso9660.lo -MD -MP -MF .deps/iso9660.Tpo -c -o iso9660.lo iso9660.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
-I../../include/ -I../../include -g -O2 -MT iso9660.lo -MD -MP -MF 
.deps/iso9660.Tpo -c iso9660.cpp  -fPIC -DPIC -o .libs/iso9660.o
In file included from ../../include/cdio++/iso9660.hpp:27:0,
 from iso9660.cpp:27:
../../include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
../../include/cdio/iso9660.h:310:20: note: next member 'char 
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
../../include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
iso9660_pvd_s'
 struct iso9660_pvd_s {
^
../../include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
   char filename[EMPTY_ARRAY_SIZE];
 ^
../../include/cdio/iso9660.h:424:20: note: next member 'char 
iso9660_svd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
../../include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
iso9660_svd_s'
 struct iso9660_svd_s {
^
../../include/cdio/iso9660.h:277:45: error: flexible array member 
'iso9660_dir_s::filename' not at end of 'class ISO9660::PVD'
   char filename[EMPTY_ARRAY_SIZE];
 ^
../../include/cdio/iso9660.h:310:20: note: next member 'char 
iso9660_pvd_s::root_directory_filename' declared here
   char root_directory_filename;  /**< Is '\\0' or root
^~~
In file included from iso9660.cpp:27:0:
../../include/cdio++/iso9660.hpp:41:9: note: in the definition of 'class 
ISO9660::PVD'
   class PVD  // Primary Volume ID
 ^~~
Makefile:545: recipe for target 'iso9660.lo' failed
make[4]: *** [iso9660.lo] Error 1
make[4]: Leaving directory '/<>/lib/cdio++'
Makefile:425: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/lib'
Makefile:584: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:477: recipe for target 'all' failed

Bug#841624: marked as done (libcdio: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:00:18 +
with message-id 
and subject line Bug#841556: fixed in libcdio 0.94-0.1
has caused the Debian Bug report #841556,
regarding libcdio: ftbfs with GCC-7
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.)


-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcdio
Version: 0.83-4.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I../../include-g -O2 -MT 
> iso9660.lo -MD -MP -MF .deps/iso9660.Tpo -c -o iso9660.lo iso9660.cpp
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
> -I../../include/ -I../../include -g -O2 -MT iso9660.lo -MD -MP -MF 
> .deps/iso9660.Tpo -c iso9660.cpp  -fPIC -DPIC -o .libs/iso9660.o
> In file included from ../../include/cdio++/iso9660.hpp:27:0,
>  from iso9660.cpp:27:
> ../../include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> ../../include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> ../../include/cdio/iso9660.h:283:8: note: in the definition of 'struct 
> iso9660_pvd_s'
>  struct iso9660_pvd_s {
> ^
> ../../include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> ../../include/cdio/iso9660.h:424:20: note: next member 'char 
> iso9660_svd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> ../../include/cdio/iso9660.h:392:8: note: in the definition of 'struct 
> iso9660_svd_s'
>  struct iso9660_svd_s {
> ^
> ../../include/cdio/iso9660.h:277:45: error: flexible array member 
> 'iso9660_dir_s::filename' not at end of 'class ISO9660::PVD'
>char filename[EMPTY_ARRAY_SIZE];
>  ^
> ../../include/cdio/iso9660.h:310:20: note: next member 'char 
> iso9660_pvd_s::root_directory_filename' declared here
>char root_directory_filename;  /**< Is '\\0' or root
> ^~~
> In file included from iso9660.cpp:27:0:
> ../../include/cdio++/iso9660.hpp:41:9: note: in the definition of 'class 
> ISO9660::PVD'
>class PVD  // Primary Volume ID
>  ^~~
> Makefile:545: recipe for target 'iso9660.lo' failed
> make[4]: *** [iso9660.lo] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/libcdio_0.83-4.2_unstable.log

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

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

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

Bug#879952: qt3d5-dev-tools: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/qt5/bin/qgltf

[Andreas Beckmann]

Package: qt3d5-dev-tools
Version: 5.9.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package qt3d5-dev-tools.
  Preparing to unpack .../qt3d5-dev-tools_5.9.2+dfsg-2_amd64.deb ...
  Unpacking qt3d5-dev-tools (5.9.2+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/qt3d5-dev-tools_5.9.2+dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/bin/qgltf', which is also 
in package qt3d-assimpsceneio-plugin:amd64 5.7.1+dfsg-2
  Errors were encountered while processing:
   /var/cache/apt/archives/qt3d5-dev-tools_5.9.2+dfsg-2_amd64.deb


cheers,

Andreas


qt3d-assimpsceneio-plugin=5.7.1+dfsg-2_qt3d5-dev-tools=5.9.2+dfsg-2.log.gz
Description: application/gzip

Bug#878834: marked as done (freetype: Upgrade to 2.8.1 breaks font rendering in various applications)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 16:34:56 +0200
with message-id 
and subject line Re: freetype: Upgrade to 2.8.1 breaks font rendering in 
various applications
has caused the Debian Bug report #878834,
regarding freetype: Upgrade to 2.8.1 breaks font rendering in various 
applications
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.)


-- 
878834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freetype
Version: 2.8.1-0.1
Severity: important

Dear Maintainer,

I upgraded freetype from 2.8.0 to 2.8.1 today and font rendering in both 
thunderbird and discord
took a really steep nosedive.

Freetype 2.8.0: https://imgur.com/8QLHYDK
Freetype 2.8.1: https://imgur.com/TtDN0pE

Thanks
Christian


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

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

Hi,

thunderbird has now migrated to testing.

Other broken applications (that are not in the debian archive) are 
atom[0] and visual studio[1]


So I propose to close this bug and let the pkg migrate to testing as 
there are no ETA of when this will be fixed in these programs.


[0] https://github.com/atom/atom/issues/15737
[1] https://github.com/Microsoft/vscode/issues/35675--- End Message ---

Bug#878870: marked as done (freetype 2.8.1 breaks font rendering)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 16:34:56 +0200
with message-id 
and subject line Re: freetype: Upgrade to 2.8.1 breaks font rendering in 
various applications
has caused the Debian Bug report #878834,
regarding freetype 2.8.1 breaks font rendering
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.)


-- 
878834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird,libfreetype6
Version: libfreetype6/2.8.1-0.1
Severity: serious
Tags: patch fixed-upstream upstream
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1409188

Hi,

freetype 2.8.1 breaks fonts when using subpixel rendering.

This is already fixed in firefox[1], the same code is also present in
thunderbird and I guess the same patch can be used there.

Could you please have a look at fixing thunderbird?

Regards,

Laurent Bigonville

[1] https://hg.mozilla.org/releases/mozilla-release/rev/8fe8227e5080
--- End Message ---
--- Begin Message ---

Hi,

thunderbird has now migrated to testing.

Other broken applications (that are not in the debian archive) are 
atom[0] and visual studio[1]


So I propose to close this bug and let the pkg migrate to testing as 
there are no ETA of when this will be fixed in these programs.


[0] https://github.com/atom/atom/issues/15737
[1] https://github.com/Microsoft/vscode/issues/35675--- End Message ---

Bug#879951: gpsd-clients,gpsd: both ship /usr/share/man/man8/ppscheck.8.gz

[Andreas Beckmann]

Package: gpsd-clients,gpsd
Version: 3.17-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package gpsd.
  Preparing to unpack .../archives/gpsd_3.17-1_amd64.deb ...
  Unpacking gpsd (3.17-1) ...
  dpkg: error processing archive /var/cache/apt/archives/gpsd_3.17-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man8/ppscheck.8.gz', which is also in 
package gpsd-clients 3.17-1
  Errors were encountered while processing:
   /var/cache/apt/archives/gpsd_3.17-1_amd64.deb


cheers,

Andreas


gpsd-clients=3.17-1_gpsd=3.17-1.log.gz
Description: application/gzip

Bug#878929: marked as done (libfreetype6: font rendering broken in electron applications)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 16:34:56 +0200
with message-id 
and subject line Re: freetype: Upgrade to 2.8.1 breaks font rendering in 
various applications
has caused the Debian Bug report #878834,
regarding libfreetype6: font rendering broken in electron applications
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.)


-- 
878834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfreetype6
Version: 2.8.1-0.1
Severity: normal

Dear Maintainer,

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

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

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

Font rendering in electron applications is now broken (eg basic electron sample
applications/discord).  Building manually this problem does not exist:

apt-get source libfreetype6
cd freetype-2.8.1/
tar xfj freetype-2.8.1.tar.bz2
cd freetype-2.8.1
./configure --without-bzip2 --without-harfbuzz
make -j4
LD_PRELOAD=./objs/.libs/libfreetype.so ~/discordapp/Discord #or other electron
app



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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---

Hi,

thunderbird has now migrated to testing.

Other broken applications (that are not in the debian archive) are 
atom[0] and visual studio[1]


So I propose to close this bug and let the pkg migrate to testing as 
there are no ETA of when this will be fixed in these programs.


[0] https://github.com/atom/atom/issues/15737
[1] https://github.com/Microsoft/vscode/issues/35675--- End Message ---

Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

[Jonas Smedegaard]

Quoting Andreas Beckmann (2017-10-27 16:03:09)
> On 10/27/2017 03:03 PM, Jonas Smedegaard wrote:
>> Quoting Andreas Beckmann (2017-10-27 11:23:12)
>>> pandoc cannot be built in sid any more since libghc-syb-dev was 
>>> updated.
>>
>> No longer the case with new release of Pandoc.
>>
>> Not really caused by pandoc, however, so closing without setting a 
>> version.
>
> There was a packaging change in pandoc relaxing the dependency: 
> d74578a05

Ah, indeed. Thanks!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Processed: Re: Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.19.2.4~dfsg-1
Bug #879922 {Done: Jonas Smedegaard } [src:pandoc] pandoc: B-D: 
libghc-syb-dev (< 0.7) but 0.7-1 is to be installed
Marked as fixed in versions pandoc/1.19.2.4~dfsg-1.

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

Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

[Andreas Beckmann]

Control: fixed -1 1.19.2.4~dfsg-1

On 10/27/2017 03:03 PM, Jonas Smedegaard wrote:
> Quoting Andreas Beckmann (2017-10-27 11:23:12)
>> pandoc cannot be built in sid any more since libghc-syb-dev was updated.
> 
> No longer the case with new release of Pandoc.
> 
> Not really caused by pandoc, however, so closing without setting a 
> version.

There was a packaging change in pandoc relaxing the dependency: d74578a05

Andreas

Bug#879800: ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)

[Rainer Dorsch]

Package: ffmpeg
Version: 7:3.4-1
Followup-For: Bug #879800

Dear Maintainer,

I just wanted to confirm that applying the patch you proposed fixes the problem 
for me.

Also I enabled v4l2, since the ffmpeg/kodi is making use of v4l2 to decode 
video streams. I have not tested the LD_PRELOAD option you mentined in the 
rules file (I did not understand how that would work exactly).

Many thanks for the support.

Rainer


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.13.0-1-armmp (SMP w/2 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 ffmpeg depends on:
ii  libavcodec577:3.4-1
ii  libavdevice57   7:3.4-1
ii  libavfilter67:3.4-1
ii  libavformat57   7:3.4-1
ii  libavresample3  7:3.4-1
ii  libavutil55 7:3.4-1
ii  libc6   2.24-17
ii  libpostproc54   7:3.4-1
ii  libsdl2-2.0-0   2.0.6+dfsg1-4
ii  libswresample2  7:3.4-1
ii  libswscale4 7:3.4-1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
ii  ffmpeg-doc  7:3.4-1

-- no debconf information

Bug#879886: libhts2: libhts2 needs to handle ABI changes

[Mattia Rizzolo]

On Fri, Oct 27, 2017 at 12:52:31AM -0400, Afif Elghraoui wrote:
> We've been doing this for every htslib suite release and can confirm
> upstream's explanation.

It seems to me the most "interesting" argument in #822701#26 is this:
| What's described in that thread is undocumented internal private
| htslib functions that should always have been static getting made
| static

Well, it should have been made from the very start.  "getting made
static" is something that needs to be done during an ABI bump, otherwise
you break it.

Now, it might not be very interesting now, because indeed most probably
nothing used those symbols indeed, but nonetheless, that's how you are
supposed to handle what de-facto is a public interface.
You can never know that somebody's private code was using that
interface, and suddenly making a function static would break it at
runtime.

> Other packages do not get broken. Upstream has
> made a soname bump as appropriate for the 1.4 release if I remember
> correctly. That's all I can say about this; I don't actually work on the
> htslib packaging myself.

What would have been good to prevent the current breakage that has been
brought to my attention (samtools), what happened is that the newest
version of samtools picked up a symbol that was not in the original
libhts2.  Remember that adding symbols is not an ABI break.  Though,
that requires using a versioned dependency, which in a perfect world
would be provided (forced?) by a proper htslib packaging.

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

Bug#879798: marked as done (FTBFS: testsuite fails with dpkg 1.19, patch attached)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 13:48:48 +
with message-id 
and subject line Bug#879798: fixed in devscripts 2.17.11
has caused the Debian Bug report #879798,
regarding FTBFS: testsuite fails with dpkg 1.19, patch attached
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.)


-- 
879798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: devscripts
Version: 2.17.10
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch



In Ubuntu, the attached patch was applied to achieve the following:

  * test/test_mk-origtargz: Adjust test for dpkg 1.19's ErrorHandling.pm.

Fairly self-explanatory, I'd think.  In dpkg 1.19, ErrorHandling.pm was
normalised to match libdpkg error messages, and this means the expected
error in the mk-origtargz test is now incorrect.  This patch fixes that.

... Adam

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

Kernel: Linux 4.13.0-16-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru devscripts-2.17.10/test/test_mk-origtargz 
devscripts-2.17.10ubuntu1/test/test_mk-origtargz
--- devscripts-2.17.10/test/test_mk-origtargz   2017-09-13 20:08:30.0 
-0600
+++ devscripts-2.17.10ubuntu1/test/test_mk-origtargz2017-10-25 
22:29:09.0 -0600
@@ -540,7 +540,7 @@
"tar: This does not look like a tar archive
 tar: Skipping to next header
 tar: Exiting with failure status due to previous errors
-$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
gave error exit status 2" \
+$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
subprocess returned exit status 2" \
"" \
 ../foo-0.1.tar.gz --repack --compression xz
 }
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.17.11

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated devscripts 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, 27 Oct 2017 14:52:18 +0200
Source: devscripts
Binary: devscripts
Architecture: source
Version: 2.17.11
Distribution: unstable
Urgency: medium
Maintainer: Devscripts Devel Team 
Changed-By: Mattia Rizzolo 
Description:
 devscripts - scripts to make the life of a Debian Package maintainer easier
Closes: 702636 862324 871657 875861 875887 876024 877104 877440 877877 879207 
879798
Changes:
 devscripts (2.17.11) unstable; urgency=medium
 .
   [ James McCoy ]
   * Remove myself from Uploaders.
 .
   [ Osamu Aoki ]
   * debuild:
 + Support newer and long dpkg-buildpackage options --no-sign,
   --unsigned-source, --unsigned-changes, -ui and --unsigned-buildinfo,
   therefore bumping the dpkg-bev dependency to version to 1.18.19.
   Closes: #876024
   * debian/control:
 + Remov Martin Zobel-Helas, Patrick Schoenfeld and Benjamin Drung
   from Uploaders after asking them.
   Thanks for all your contributions!
   * uscan:
 + Auto set --force-download when appropriate to retain the
   previous behaviour.
 + Correct information about the OpenPGP key fingerprints.  Closes: #877104
 .
   [ Chris Lamb ]
   * reproducible-check:
 + Match name of the json file on remote server.
 + Use the restricted JSON file that hides transient issues.  Closes: 
#875861
 + Handle multi-architecture systems.  Closes: #875887
 + Expire cache file after 1 day and base local cache name on the

Bug#879940: virtualbox-dkms: Fail to build

[Christian Marillat]

Package: virtualbox-dkms
Version: 5.2.0-dfsg-1
Severity: serious

Dear Maintainer,

>From /var/lib/dkms/virtualbox/5.2.0/build/make.log

/var/lib/dkms/virtualbox/5.2.0/build/vboxpci/linux/VBoxPci-linux.c:35:10: fatal 
error: VBoxPciInternal.h: No such file or directory
 #include "VBoxPciInternal.h"
  ^~~
compilation terminated.

Christian

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

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

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.2.0-dfsg-1

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#879941: awesome: FTBFS on s390x: 7 tests fail, all in color_spec.lua

[Aaron M. Ucko]

Source: awesome
Version: 4.2-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-s...@lists.debian.org

The latest build of awesome for s390x failed with seven unit test
errors, all in color_spec.lua, per the below excerpt from
https://buildd.debian.org/status/fetch.php?pkg=awesome=s390x=4.2-2=1508945611=0

Could you please take a look?

Thanks!



cd /<> && /usr/bin/busted 
--helper=/<>/spec/preload.lua 
"--lpath=lib/?.lua;lib/?/init.lua;spec/?.lua"
***-
272 successes / 1 failure / 7 errors / 0 pending : 0.217003 seconds

Failure -> spec/gears/color_spec.lua @ 226
gears.color create_opaque_pattern opaque surface pattern
spec/gears/color_spec.lua:230: Pattern (userdata) 'lgi.rec 
0x12239bd40:cairo.SolidPattern' should be opaque, but isn't.

Error -> spec/gears/color_spec.lua @ 121
gears.color linear pattern table description
lib/gears/color.lua:151: cairo.SolidPattern: no `add_color_stop_rgba'

Error -> spec/gears/color_spec.lua @ 138
gears.color linear pattern string description
lib/gears/color.lua:144: cairo.SolidPattern: no `add_color_stop_rgba'

Error -> spec/gears/color_spec.lua @ 156
gears.color radial pattern table description
lib/gears/color.lua:151: cairo.SolidPattern: no `add_color_stop_rgba'

Error -> spec/gears/color_spec.lua @ 173
gears.color radial pattern string description
lib/gears/color.lua:144: cairo.SolidPattern: no `add_color_stop_rgba'

Error -> spec/gears/color_spec.lua @ 211
gears.color create_opaque_pattern transparent linear pattern with transparent 
stops
lib/gears/color.lua:144: cairo.SolidPattern: no `add_color_stop_rgba'

Error -> spec/gears/color_spec.lua @ 215
gears.color create_opaque_pattern transparent linear pattern with NONE repeat
lib/gears/color.lua:144: cairo.SolidPattern: no `add_color_stop_rgba'

Error -> spec/gears/color_spec.lua @ 222
gears.color create_opaque_pattern opaque linear pattern
lib/gears/color.lua:144: cairo.SolidPattern: no `add_color_stop_rgba'
CMakeFiles/check-unit.dir/build.make:60: recipe for target 
'CMakeFiles/check-unit' failed
make[5]: *** [CMakeFiles/check-unit] Error 1

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

Bug#879922: marked as done (pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 15:03:47 +0200
with message-id <150910942700.29663.15989256165967632...@auryn.jones.dk>
and subject line Re: Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 
is to be installed
has caused the Debian Bug report #879922,
regarding pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed
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.)


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

pandoc cannot be built in sid any more since libghc-syb-dev was updated.


Andreas
--- End Message ---
--- Begin Message ---
Quoting Andreas Beckmann (2017-10-27 11:23:12)
> pandoc cannot be built in sid any more since libghc-syb-dev was updated.

No longer the case with new release of Pandoc.

Not really caused by pandoc, however, so closing without setting a 
version.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private--- End Message ---

Bug#871095: Close bug?

[Ole Streicher]

Hi,

since the new version obviously builds on amd64, may this bug be closed?

Cheers

Ole

Bug#878411: gnome-session-bin doesn't set environmental variable of GTK_IM_MODULE

[Takahide Nojima]

> It's unclear from your bug report whether this was working before for
> you ("I can not anymore Japanes language anymore").
> Are you saying that with older gnome-session-bin versions it worked?
> 

 No. 

  I'm saying With current GNOME Desktop, wayland(currently default in
Debian sid) and current and older gnome-session-bin , it doesn't work. 

 After  checking source code of gnome-session-bin, I found it set
QT_IM_MODULE and XMODIFIERS env variable correctly , but it doesn't set
GTK_IM_MODULE (I don't know why). So I supporsed that patch.

 Recently GNOME Desktop, wayland in debian sid doesn't seems to execute
any scripts under /etc/Xsession.d/. Then, there isn't any chance to set
GTK_IM_MODULE env variable when gnome-shell is invoked. This cause 
gnome-shell menu invokes gtk applications without  GTK_IM_MODULE env
variable, they won't communicate to ibus.
(This cause "I can not type Japanese language anymore")

 I guess , refer to main.c of gnome-session-bin, the best place of
setting GTK_IM_MODULE env variable is in gnome-session-bin.

 Would you accept that patch as a temporary resolution?

Takahide Nojima




　

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

[Vincent Lefevre]

Control: retitle -1 libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 
375.82-6 with both :amd64 and :i386 packages installed

On 2017-10-26 23:37:18 +0200, Andreas Beckmann wrote:
> On 10/26/2017 11:13 PM, Rafał Olejnik wrote:
> > Guess having amd64 and i386 might be a reason because on my sid i'm
> > getting same error.
> 
> having both :amd64 and :i386 packages installed does not seem to work
> properly with versioned Provides/Breaks in this special case.

This seems to be the issue, as on my machine with only :amd64 packages,
the upgrade was fine.

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

Processed: Re: Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 
> 375.82-6 with both :amd64 and :i386 packages installed
Bug #879821 [libgles1-glvnd-nvidia] libgles1-glvnd-nvidia, libgles-nvidia1: 
upgrade failure to 375.82-6
Changed Bug title to 'libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure 
to 375.82-6 with both :amd64 and :i386 packages installed' from 
'libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 375.82-6'.

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

Bug#875706: marked as done (edbrowse: please package new upstream version)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 11:33:49 +
with message-id 
and subject line Bug#875706: fixed in edbrowse 3.7.1-1
has caused the Debian Bug report #875706,
regarding edbrowse: please package new upstream version
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.)


-- 
875706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: edbrowse
Version: 3.6.3-1
Severity: wishlist
Control: block -1 by 872040

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

There is a new version of edbrowse available from upstream. Because edbrowse
migrated from the mozjs suite to duktape, packaging is blocked by bug 872040 in
src:duktape. To avoid unnecessary work, I am filing this bug.

Paul

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlm5iLwACgkQnFyZ6wW9
dQpQeQf/XhoTE3nzskrhYVrDGQiT/pkKc7cE3PM7i79y98k+5rmOsBTRHYlzIOh9
NSUrJeWoymqidPakx6Y/wRZzkBQLLtLZrKR9DQIujpxsptBkB0y/+x2NINO1JUyK
ujkPwmOaNC4C3u4BQlFcHXo+bCuwjGub2wdTFmRuKLJTB4JJcNhh6t+W4fzZQjpV
zlsjkJJCHoibQi4nMs3/Ybc6hafsGosP6AnZpXynOh0V6VBRgjOJs2pOESB/3mvs
VY+6ATAGup4xJpgmLPlmpxkQs08IUeqWoPxjuma6o3PP83Ldvs2ua/ftV55stwKG
WHe5ZalC56XKYVlTCe+ntzfVBWe97Q==
=q9VI
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: edbrowse
Source-Version: 3.7.1-1

We believe that the bug you reported is fixed in the latest version of
edbrowse, 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.
Paul Gevers  (supplier of updated edbrowse 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: Fri, 27 Oct 2017 12:52:02 +0200
Source: edbrowse
Binary: edbrowse
Architecture: source
Version: 3.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Paul Gevers 
Description:
 edbrowse   - /bin/ed-alike webbrowser written in C
Closes: 875706
Changes:
 edbrowse (3.7.1-1) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * control: Migrate priority to optional.
   * control: Bump Standards-Version to 4.1.1.
 .
   [ Paul Gevers ]
   * New upstream release (Closes: #875706)
   * Drop fix-spelling-errors.patch (applied upstream)
   * Upstream migrated from libmozjs to duktape
   * Convert packaging from SVN to GIT and move to a11y archive
Checksums-Sha1:
 4cd68d6a9586be1e6dc1771a75412b0129e3c536 1713 edbrowse_3.7.1-1.dsc
 263cec2cc5abf9929d4a3bdd9eaba7760e944e24 598563 edbrowse_3.7.1.orig.tar.gz
 6fcbc7c2d4e9251884c63f5f3b22ca91d452c784 13828 edbrowse_3.7.1-1.debian.tar.xz
Checksums-Sha256:
 bafb8a773f03e5e0f08d8f059c55bf00bbd1eccaa8e7047b2ebb457c3318eea1 1713 
edbrowse_3.7.1-1.dsc
 12edf1834bbfb93335002c222a0f472eb4551a5b3a99d67c8a5e9dc05f97e37a 598563 
edbrowse_3.7.1.orig.tar.gz
 05aff96cdcc5669ea85f8da288db626276c77be545cb03ab57d12cfdd64eba83 13828 
edbrowse_3.7.1-1.debian.tar.xz
Files:
 cec7629075755b762813644d4d221c20 1713 net optional edbrowse_3.7.1-1.dsc
 cbf52656e8373b380dcf8d39a415df02 598563 net optional edbrowse_3.7.1.orig.tar.gz
 5f6bd6821a1796d349a6bc9c7ab29222 13828 net optional 
edbrowse_3.7.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlnzEGIACgkQnFyZ6wW9
dQpsuAf6AxTyQVEbTMTeKxEqmmU1jd4nt5vhyNgKg0YwPaLJPADWRe/TxpmexW0L
id9hDgxG4pH+6Y4uR/LvTeRa1aQ+yUOlVDO0fXUCI1m+5f+t2B/RS+nU3Pz7uahX
bvU6xlBkDKlHu6D3yYWbT7y53fjKaEtXzeWeEwzCllus9O5jE2+x7hHObrKtQomG
8XBlBloCEEoNCvsBqehQOjS8NmePTputCPSfb2Wz51bRV7NHdwp3WUwXn0+9QyuX
0SLM7yuceTl215ncgEBS5QkP5f8Vpx64eiTkrbv/VEtaCdVeBJe//NTCU1fmSEpn
1gcHFr+TxIzZ0nsL5Uxf21pRK7ElAw==
=S6FS
-END PGP SIGNATURE End Message ---

Bug#879905: glee: source for GLee.c and GLee.h is missing

[Ximin Luo]

Steve Cotton:
> Source: glee
> Severity: serious
> Justification: missing source (GLeeGen), missing source (GL ext specs)
> 
> GLee already has serious bug #879123, and the auto-removal email
> for dependencies was sent this morning. Most of the discussion in
> #879123 looks as if a .dsfg tarball would just need to remove the
> configure file, I'm logging a new bug so that this doesn't get
> missed:
> 
> On Thu, 19 Oct 2017 22:47:00, Ximin Luo wrote:
>> Unfortunately we have a bigger problem:
>>
>> -rwxrwxr-x   1,105,245   GLee.c
>> -rwxrwxr-x   955,258 GLee.h
>>
>> * [This file was automatically generated by GLeeGen 7.0
>>
>> These files are clearly not source code. But luckily it should
>> be possible to regenerate them from the git repo I mentioned:
>>
>>> [..] https://github.com/kallisti5/glee
> 
> It seems that repo is also not the complete source, the build
> steps in CMakeLists.txt download specs for the GL extensions from
> http://www.opengl.org/registry/
> 
> The Readme.txt mentions a graball.bat, which no longer exists,
> but seems likely to have grabbed from the same place.
> 
> Steve
> 

Thanks for reporting yes. Looks like the previous discussion went on for almost 
the length of another ./configure file, without CCing me in the process, and 
ignored this much more serious issue.

I'd also like to reiterate my earlier point:

> To re-iterate my first point though, if in the future this issue crops up
> again, you need to supply evidence that ./configure is "preferred source of
> modification" because that contradicts all other experience of autotools 
> files.
> A git history log of the author hand-editing the file *more times* than
> regenerating the file from configure.ac would suffice.

And likewise for other generated text code like this C source code here.

I see some pedantry in the other bug report about "can modify". Obviously you 
"can modify" any file that exists on your computer, you can also modify ELF 
binaries in dirty binary hacks and "I've done this before" as well. (See 
/home/groups/reproducible/htdocs/patched-libs/libapt-inst.so.1.5.0.patched-xz 
on alioth). Source code is "*preferred*-form-of-modification", not 
"form-of-modification".

If one says something like this:

> I have worked with even more configure scripts and I also prefer modifying
> something else.

one already acknowledges that the "something else" is the source code, not the 
configure script.

Agreed that bug reports should be filed to other packages if they have similar 
problems. The packages I am responsible for, do not have this issue.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#879932: haskell-hoauth2: B-D: libghc-aeson-dev (< 1.1) but 1.1.2.0-1 is to be installed

[Andreas Beckmann]

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

haskell-hoauth2 can no longer be built since haskell-aeson was updated
in sid.


Andreas

Bug#879923: marked as done ([!] (commonjs plugin) TypeError: Cannot read property 'parse' of undefined)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 11:04:11 +
with message-id 
and subject line Bug#879923: fixed in node-rollup-plugin-commonjs 8.2.4-2
has caused the Debian Bug report #879923,
regarding [!] (commonjs plugin) TypeError: Cannot read property 'parse' of 
undefined
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.)


-- 
879923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: node-rollup-plugin-commonjs
version: 8.2.4-1
severity: serious

When building rollup using node-rollup-plugin-commonjs, it fails with
error (with npm installed rollup-plugin-commonjs, build succeeds).

src/node-entry.js → dist/rollup.js, dist/rollup.es.js...
[!] (commonjs plugin) TypeError: Cannot read property 'parse' of
undefined in /<>/src/node-entry.js



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-commonjs
Source-Version: 8.2.4-2

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated 
node-rollup-plugin-commonjs 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, 27 Oct 2017 12:53:01 +0200
Source: node-rollup-plugin-commonjs
Binary: node-rollup-plugin-commonjs
Architecture: source all
Version: 8.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 node-rollup-plugin-commonjs - Node.js plugin for rollup to convert CommonJS 
modules to ES6
Closes: 879923
Changes:
 node-rollup-plugin-commonjs (8.2.4-2) unstable; urgency=medium
 .
   * Improve d/rules (Closes: #879923).
Checksums-Sha1:
 f905630d54c4682089b4793c3c15fdb7b5a41c57 2352 
node-rollup-plugin-commonjs_8.2.4-2.dsc
 ca33d204317ea21f3f8acc4f0baef8ecec33bfbb 2440 
node-rollup-plugin-commonjs_8.2.4-2.debian.tar.xz
 ed40f8c3bce8b23ae6c0e818f0c45609b3abe742 13384 
node-rollup-plugin-commonjs_8.2.4-2_all.deb
 e4b2e96db04b81e84556d7f572279c696a664bbe 8526 
node-rollup-plugin-commonjs_8.2.4-2_amd64.buildinfo
Checksums-Sha256:
 60289612175a2d572d445864fa2fc4a94479a19923a7ed3088265aed7a79c443 2352 
node-rollup-plugin-commonjs_8.2.4-2.dsc
 0923ba1d7c9b812419c29a92fe24efe65e26905c448d9d0cae461ba19d1eb921 2440 
node-rollup-plugin-commonjs_8.2.4-2.debian.tar.xz
 de49993baf2a8b9bcef1a390ed46a95d3e65e5682b4f68dbad272cf727fb34a8 13384 
node-rollup-plugin-commonjs_8.2.4-2_all.deb
 0544b39168a7f767fe01a78fa906bb87a75e8441cd4d6ca1d33dae1b1e505acd 8526 
node-rollup-plugin-commonjs_8.2.4-2_amd64.buildinfo
Files:
 ccce0d63faaafdd9e232cd3145dd1e76 2352 javascript optional 
node-rollup-plugin-commonjs_8.2.4-2.dsc
 86d05c5ae807c963728422391c5c426a 2440 javascript optional 
node-rollup-plugin-commonjs_8.2.4-2.debian.tar.xz
 0e9595b00a456fb146578e5521a962c9 13384 javascript optional 
node-rollup-plugin-commonjs_8.2.4-2_all.deb
 7b6aeec7b30f6ce0eb4777ab9048dd2a 8526 javascript optional 
node-rollup-plugin-commonjs_8.2.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlnzEEMZHGp1bGllbi5w
dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUbUwD/9sRgz2uomTxRsWvffeQm0E
Mc5sGybKuStPorMj/+Lz9ogUtUjcCmksPtzA/xvd0oHryHw5XcH8u6wjjdsAGLQ5
0qnKLHhlquCd9dJq4Tx6/yCcSWAPtKrlfRHPLJjEewYAJPriQlKVBNk+zmacC7c4
lqa8GOrQLhg6kINbg+b9MDzY7cNAErsuI9DnYlEq+IR2u//Qc10Cf33wCRermjvx
LBGcLo+n4kag52ow9eB3FECKUbF37uxAEYuDg7FnTfjlePgGU0yqtKv3B1iT9MPF
M3Tod4yT8JTEy6w2pHlSK/Gvt0FTkB6PBRuv/1wGrcwIVyZ4MA6350CG+fK1uOMQ
EN7bMR2KRc3Bwd+1jbrotqyKqb2ZJ3iMAz4bJu7AJ/ECXuItF1JPuP+w/BDkdvTv
Gv4hJJ0BVfjp0/UX7hpvhwYXLw6NWJif8JLPq9gRXKAwvSj8JUbAMszNCDQS+caK
BieFO7IL3Qo3rRZ1yYomCXTZXU0M1a6vY86TlEj5hBK5NQxdV+fh9mzVBiQaLxpE
Ag/dg6hbYUhN5ChEqaY4JBIAwLWmtVs7AXYyzQB/GmQMFs3gDK0KkWpbumry8bjT
pgXyGSereCjR4fJXI7bbfQAw0iA1qYa1vMZhqDw4tml1J08wrQ6rdMs9qZs+8zRu
Sd71ZQNR7kZGHtnQCC+HSw==
=pV69

Bug#879931: vagrant: VirtualBox 5.2 is not supported

[Guillem Jover]

Package: vagrant
Version: 1.9.8+dfsg-1
Severity: serious

Hi!

The current version of virtualbox in sid is 5.2.0-dfsg-1, which is not
supported by the current vagrant, which only got support for it in git
master for which there's been no release yet. Please apply the
upstream patch:

  


Also ideally, vagrant would grow a relationship to declare explicitly
what versions of virtualbox are supported to avoid this kind of silent
breakage, for which the package managers cannot do anything about.
perhaps something like?

  Depends: virtualbox (<< 5.3)

Thanks,
Guillem

Bug#867166: Future of linux-grec in Debian

[Yves-Alexis Perez]

On Fri, 2017-10-27 at 05:58 -0400, Jordan Glover wrote:
> linux-grsec-base[1] is missing from stable-backports and I don't see it
> being prepared for upload there[2]. Other than that this bug can be closed.
> Thanks for your work.
> 
> [1] https://tracker.debian.org/pkg/linux-grsec-base
> [2] https://anonscm.debian.org/git/collab-maint/linux-grsec-base.git

I was waiting for the image itself to be accepted, I'll prepare the linux-
grsec-base backport next.

Regards,
-- 
Yves-Alexis

Bug#875706: edbrowse: please package new upstream version

[Paul Gevers]

Control: owner -1 !

On Wed, 13 Sep 2017 21:36:44 +0200 Paul Gevers  wrote:
> There is a new version of edbrowse available from upstream. Because edbrowse
> migrated from the mozjs suite to duktape, packaging is blocked by bug 872040 
> in
> src:duktape. To avoid unnecessary work, I am filing this bug.

duktape now builds a library. I'll work on edbrowse the coming days.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: edbrowse: please package new upstream version

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #875706 [edbrowse] edbrowse: please package new upstream version
Owner recorded as Paul Gevers .

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

Bug#867166: Future of linux-grec in Debian

[Jordan Glover]

linux-grsec-base[1] is missing from stable-backports and I don't see it being 
prepared for upload there[2]. Other than that this bug can be closed. Thanks 
for your work.

[1] https://tracker.debian.org/pkg/linux-grsec-base
[2] https://anonscm.debian.org/git/collab-maint/linux-grsec-base.git

Bug#879923: [!] (commonjs plugin) TypeError: Cannot read property 'parse' of undefined

[Pirate Praveen]

package: node-rollup-plugin-commonjs
version: 8.2.4-1
severity: serious

When building rollup using node-rollup-plugin-commonjs, it fails with
error (with npm installed rollup-plugin-commonjs, build succeeds).

src/node-entry.js → dist/rollup.js, dist/rollup.es.js...
[!] (commonjs plugin) TypeError: Cannot read property 'parse' of
undefined in /<>/src/node-entry.js



signature.asc
Description: OpenPGP digital signature

Bug#867058: [pkg-golang-devel] Bug#867058: golang-1.8 and mips*

[Michael Hudson-Doyle]

On 27 October 2017 at 22:38, James Cowgill  wrote:

> Hi,
>
> On 26/10/17 20:33, John Paul Adrian Glaubitz wrote:
> > On 10/26/2017 07:12 PM, peter green wrote:
> >> Therefore golang maintainers you have two choices.
> >>
> >> 1. Accept John's changes so that your package can be built on mips*.
> >> 2. File a removal request for the binaries uploaded by John
> >
> > I assume that gccgo on mips is still broken as this situation hasn't
> changed,
> > so I would suggest removing the packages again. I can file a bug for that
> > since I am the one who is responsible that these packages are there in
> the
> > first place.
>
> gccgo was fixed in gcc-7 a few weeks ago and I've filed a bug against
> golang-1.9 already. Since golang-defaults already points to golang-1.9
> in unstable, I am guessing that older versions are now irrelevant for mips.
>
> I suggest:
> - Apply the patch in #879764 to golang-1.9.
>

LGTM.


> - Remove the mips binaries from golang-1.8 (or remove 1.8 entirely).
>

I think we should remove the mips binaries.


> - Enable mips in golang-defaults.
>

+1


> A reply from the golang maintainers would be very helpful in all of this...
>

Sorry for the lack of response. I have to admit that I've found the whole
issue very confusing to follow but I'm very grateful to the people who've
put the effort in to make the simple patch attached to #879764 all that is
required!

Cheers,
mwh

Bug#873675: marked as done (libexecs: FTBFS w/GCC 7: null where non-null expected)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 09:35:17 +
with message-id 
and subject line Bug#873675: fixed in libexecs 1.1-1
has caused the Debian Bug report #873675,
regarding libexecs: FTBFS w/GCC 7: null where non-null expected
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.)


-- 
873675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libexecs
Version: 1.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source

Builds of libexecs with GCC 7 (the default version nowadays) have been
failing:

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c noshell.c  -fPIC 
-DPIC -o .libs/noshell.o
  noshell.c: In function 'coprocess_common':
  noshell.c:82:7: error: argument 1 null where non-null expected 
[-Werror=nonnull]
 execvpe(path, argv, envp);
 ^
  In file included from noshell.c:5:0:
  /usr/include/unistd.h:593:12: note: in a call to function 'execvpe' declared 
here
   extern int execvpe (const char *__file, char *const __argv[],
  ^~~
  cc1: all warnings being treated as errors
  Makefile:512: recipe for target 'noshell.lo' failed

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: libexecs
Source-Version: 1.1-1

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

Debian distribution maintenance software
pp.
Giulia Cantini  (supplier of updated libexecs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 14 Oct 2017 18:00:04 +0200
Source: libexecs
Binary: libexecs-dev libexecs0 libexecs-embedded0
Architecture: source amd64
Version: 1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Giulia Cantini 
Changed-By: Giulia Cantini 
Description:
 libexecs-dev - C library for commands execution - development files
 libexecs-embedded0 - C library for commands execution
 libexecs0  - C library for commands execution
Closes: 873675 875421
Changes:
 libexecs (1.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #873675)
   * Update Standards-Version to 4.1.1.
   * Change package section (libexecs0 and libexecs-embedded0 in libs).
   * Add missing dependency in libexecs-dev. (Closes: #875421)
Checksums-Sha1:
 ba87d6b85ac16ec10fa67e7c0d2def33374d4e2a 1860 libexecs_1.1-1.dsc
 78d5d7c804f224a943513d20bd0cb6b6de9ab22b 163563 libexecs_1.1.orig.tar.gz
 f196a879fbdaf2b156ec6deac2d88c49ef68edb7 2300 libexecs_1.1-1.debian.tar.xz
 34922760fceb198d6afcc66c01de1aaf14cab3b2 14304 libexecs-dev_1.1-1_amd64.deb
 f26f884b0688644cea265c815e8ac295bbeeef51 4868 
libexecs-embedded0-dbgsym_1.1-1_amd64.deb
 9dabfe948eb6de85910f0af8d424804aba3b7f04 5436 
libexecs-embedded0_1.1-1_amd64.deb
 e4551ff1763716e2998051d405c116ae7138932a 9552 libexecs0-dbgsym_1.1-1_amd64.deb
 d37348c6997e69e8fe32bae166ff801c3a45e3e0 8388 libexecs0_1.1-1_amd64.deb
 e7a64590f1cc20bc809dadb462da1419f3ee19a1 6257 libexecs_1.1-1_amd64.buildinfo
Checksums-Sha256:
 4ef5e156f67f84fa6c8a799f6d109001384def221cb8dc6dd59be663d9afe341 1860 
libexecs_1.1-1.dsc
 a3af9bff70218c0355b7c4c1ce1e17f321b0a34144a6d03391a3789e520a605c 163563 
libexecs_1.1.orig.tar.gz
 0f3abd43bc46fbce3ac59d0932a4c71c4f878fb4d60578a64dc95f0f8eab2c86 2300 
libexecs_1.1-1.debian.tar.xz
 557779f8f6eac61e3ba77030829106d909902f0a4bb2c0aad5d3e6d4322299db 14304 
libexecs-dev_1.1-1_amd64.deb
 78f9e148fa0eccdbb3dc6c2e544ac6b41c0a213bd0866a55a479568f19ab5e51 4868 
libexecs-embedded0-dbgsym_1.1-1_amd64.deb
 5299cc0ce237baa631e1697a7ca17a5bec348f35aae026984fba7c553befbf00 5436 
libexecs-embedded0_1.1-1_amd64.deb
 

Bug#867058: golang-1.8 and mips*

[James Cowgill]

Hi,

On 26/10/17 20:33, John Paul Adrian Glaubitz wrote:
> On 10/26/2017 07:12 PM, peter green wrote:
>> Therefore golang maintainers you have two choices.
>>
>> 1. Accept John's changes so that your package can be built on mips*.
>> 2. File a removal request for the binaries uploaded by John
> 
> I assume that gccgo on mips is still broken as this situation hasn't changed,
> so I would suggest removing the packages again. I can file a bug for that
> since I am the one who is responsible that these packages are there in the
> first place.

gccgo was fixed in gcc-7 a few weeks ago and I've filed a bug against
golang-1.9 already. Since golang-defaults already points to golang-1.9
in unstable, I am guessing that older versions are now irrelevant for mips.

I suggest:
- Apply the patch in #879764 to golang-1.9.
- Remove the mips binaries from golang-1.8 (or remove 1.8 entirely).
- Enable mips in golang-defaults.

A reply from the golang maintainers would be very helpful in all of this...

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#875421: marked as done (libexecs-dev: missing Depends: libexecs-embedded0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 09:35:17 +
with message-id 
and subject line Bug#875421: fixed in libexecs 1.1-1
has caused the Debian Bug report #875421,
regarding libexecs-dev: missing Depends: libexecs-embedded0 (= 
${binary:Version})
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.)


-- 
875421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libexecs-dev
Version: 1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m23.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libexecs-embedded.so -> libexecs-embedded.so.0.9.0


cheers,

Andreas


libexecs-dev_1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libexecs
Source-Version: 1.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 14 Oct 2017 18:00:04 +0200
Source: libexecs
Binary: libexecs-dev libexecs0 libexecs-embedded0
Architecture: source amd64
Version: 1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Giulia Cantini 
Changed-By: Giulia Cantini 
Description:
 libexecs-dev - C library for commands execution - development files
 libexecs-embedded0 - C library for commands execution
 libexecs0  - C library for commands execution
Closes: 873675 875421
Changes:
 libexecs (1.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #873675)
   * Update Standards-Version to 4.1.1.
   * Change package section (libexecs0 and libexecs-embedded0 in libs).
   * Add missing dependency in libexecs-dev. (Closes: #875421)
Checksums-Sha1:
 ba87d6b85ac16ec10fa67e7c0d2def33374d4e2a 1860 libexecs_1.1-1.dsc
 78d5d7c804f224a943513d20bd0cb6b6de9ab22b 163563 libexecs_1.1.orig.tar.gz
 f196a879fbdaf2b156ec6deac2d88c49ef68edb7 2300 libexecs_1.1-1.debian.tar.xz
 34922760fceb198d6afcc66c01de1aaf14cab3b2 14304 libexecs-dev_1.1-1_amd64.deb
 f26f884b0688644cea265c815e8ac295bbeeef51 4868 
libexecs-embedded0-dbgsym_1.1-1_amd64.deb
 9dabfe948eb6de85910f0af8d424804aba3b7f04 5436 
libexecs-embedded0_1.1-1_amd64.deb
 e4551ff1763716e2998051d405c116ae7138932a 9552 libexecs0-dbgsym_1.1-1_amd64.deb
 d37348c6997e69e8fe32bae166ff801c3a45e3e0 8388 libexecs0_1.1-1_amd64.deb
 e7a64590f1cc20bc809dadb462da1419f3ee19a1 6257 libexecs_1.1-1_amd64.buildinfo
Checksums-Sha256:
 4ef5e156f67f84fa6c8a799f6d109001384def221cb8dc6dd59be663d9afe341 1860 
libexecs_1.1-1.dsc
 a3af9bff70218c0355b7c4c1ce1e17f321b0a34144a6d03391a3789e520a605c 163563 
libexecs_1.1.orig.tar.gz
 0f3abd43bc46fbce3ac59d0932a4c71c4f878fb4d60578a64dc95f0f8eab2c86 2300 
libexecs_1.1-1.debian.tar.xz
 557779f8f6eac61e3ba77030829106d909902f0a4bb2c0aad5d3e6d4322299db 14304 
libexecs-dev_1.1-1_amd64.deb
 78f9e148fa0eccdbb3dc6c2e544ac6b41c0a213bd0866a55a479568f19ab5e51 4868 
libexecs-embedded0-dbgsym_1.1-1_amd64.deb
 5299cc0ce237baa631e1697a7ca17a5bec348f35aae026984fba7c553befbf00 5436 
libexecs-embedded0_1.1-1_amd64.deb
 5e6b5148aa9f71987c18a583cef922663c6a5d7fb45ac1bd4188060aecba8e22 9552 
libexecs0-dbgsym_1.1-1_amd64.deb
 8bceaa656c207c664cd9e7f365593c8fd00989919e57c07ab62d32da6544d4b4 8388 
libexecs0_1.1-1_amd64.deb
 cb30956a68ea54d53a9f3281d7246adcea0c9f034b3f51a2c25734eb6bf80dcb 6257 
libexecs_1.1-1_amd64.buildinfo
Files:
 ca06f0129eee6de255fbcbe9323f954d 1860 libs optional libexecs_1.1-1.dsc
 ecbf18d1cd224a659bfd62414f6f0208 163563 libs optional libexecs_1.1.orig.tar.gz
 9c431a083c5e04317c3018b5e7a90a5c 2300 libs optional 
libexecs_1.1-1.debian.tar.xz
 0948c606cd40c810c50cd02ced714bc8 14304 libdevel optional 
libexecs-dev_1.1-1_amd64.deb
 45040786cdad0711b825da6c620d0333 4868 

Bug#879922: pandoc: B-D: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed

[Andreas Beckmann]

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

pandoc cannot be built in sid any more since libghc-syb-dev was updated.


Andreas

Bug#879798: FTBFS: testsuite fails with dpkg 1.19, patch attached

[Mattia Rizzolo]

On Fri, Oct 27, 2017 at 04:49:44AM +, Adam Conrad wrote:
> I'd suggest that this commit already makes no-delta backports somewhat
> problematic:
> 
> https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=921696fd6c92c4299accb1e2ef1ae48d13a47b0d

Well, that doesn't stop backports to stretch, which is pretty much what
I'm interested about.

> But ignoring that for a moment, how about this patch instead (tested
> against dpkg 1.18.24ubuntu1 and 1.19.0.4ubuntu1):

That does it.
I committed something very similar now (albeit I haven't tested it, but
why wouldn't it work)

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

Processed: Bug#879798 marked as pending

[Debian Bug Tracking System]

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

> tag 879798 pending
Bug #879798 [devscripts] FTBFS: testsuite fails with dpkg 1.19, patch attached
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#879798: marked as pending

[Mattia Rizzolo]

tag 879798 pending
thanks

Hello,

Bug #879798 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/collab-maint/devscripts.git/commit/?id=96030da

---
commit 96030dac7ca3f9e70ade3970ca30afe3f1df9c14
Author: Mattia Rizzolo 
Date:   Fri Oct 27 11:09:34 2017 +0200

tests/mk-origtargz: fix check with dpkg 1.19.x

The error message changed between 1.18 and 1.19.

Gbp-Dch: Short
Closes: #879798
Thanks: Adam Conrad  for the patch
Signed-off-by: Mattia Rizzolo 

diff --git a/debian/changelog b/debian/changelog
index 758670a..c312f5d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -55,6 +55,9 @@ devscripts (2.17.11) UNRELEASED; urgency=medium
   * uscan:
 + Apply patch from Stephen Kitt  to support https in the
   sf.net special redirector.  Closes: #879207
+  * tests:
++ mk-origtargz: fix check with dpkg 1.19.x.  Thanks to Adam Conrad
+   for the patch.  Closes: #879798
 
  -- Chris Lamb   Wed, 27 Sep 2017 13:24:39 +0100
 

Bug#877412: marked as done (beginend-el FTBFS with elpa-buttercup 1.9)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 09:04:05 +
with message-id 
and subject line Bug#877412: fixed in beginend-el 2.0.0-2
has caused the Debian Bug report #877412,
regarding beginend-el FTBFS with elpa-buttercup 1.9
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.)


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

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

...
   dh_elpa_test
buttercup -L .
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /build/1st/beginend-el-2.0.0/test/test-helper.el (source)...
Cannot open load file: No such file or directory, assess
dh_elpa_test: buttercup -L . returned exit code 255
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 255
--- End Message ---
--- Begin Message ---
Source: beginend-el
Source-Version: 2.0.0-2

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

Debian distribution maintenance software
pp.
Lev Lamberov  (supplier of updated beginend-el 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, 27 Oct 2017 13:17:00 +0500
Source: beginend-el
Binary: elpa-beginend
Architecture: source all
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Lev Lamberov 
Description:
 elpa-beginend - redefine M-< and M-> for some modes to get to meaningful 
location
Closes: 877412
Changes:
 beginend-el (2.0.0-2) unstable; urgency=medium
 .
   * Fix build dependencies (Closes: #877412)
   * Declare Standards-Version 4.1.1 (no changes needed)
   * Remove emacs24 from the Enchances field
Checksums-Sha1:
 f25873643eb55997ccc49065f6a6452a5e26774d 2074 beginend-el_2.0.0-2.dsc
 f0ecf804979e17b0691a5833f4e6b8559bd7d32f 2456 beginend-el_2.0.0-2.debian.tar.xz
 65a9d09139d1f84dcec1696774db8e90452bdaaa 7601 
beginend-el_2.0.0-2_amd64.buildinfo
 62785c62abc40c3e85ce402b05b7fc725f5d35a0 8328 elpa-beginend_2.0.0-2_all.deb
Checksums-Sha256:
 530b0f3853f8646fbb03310f1649d8fb98e7006a3fc803c4d4229e4dc993d2e2 2074 
beginend-el_2.0.0-2.dsc
 6433429251c7c39c62b95864db9d7284c470dca43e1d10aebf6d95abbcfd4a8f 2456 
beginend-el_2.0.0-2.debian.tar.xz
 6b0911df8e4cb5e56d2a97bb68cd159468dbaa287168d3a23b3b34d82b9b8361 7601 
beginend-el_2.0.0-2_amd64.buildinfo
 460f44eb2ba6a965c70ea424bfbdd1c83c74ab35cdeaaeee0e5182594d34d2f1 8328 
elpa-beginend_2.0.0-2_all.deb
Files:
 9fecc73415691b4e78cd027fb4bb6308 2074 lisp optional beginend-el_2.0.0-2.dsc
 77a02ecdc5bc4a26386676a058eeadf0 2456 lisp optional 
beginend-el_2.0.0-2.debian.tar.xz
 33e40f2617da5e4e367c3d4213a17c8d 7601 lisp optional 
beginend-el_2.0.0-2_amd64.buildinfo
 368bab6b1d3113777b70b2bbd22c0530 8328 lisp optional 
elpa-beginend_2.0.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAlny6+YTHGRvZ3NsZWdA
ZGViaWFuLm9yZwAKCRBe527iAhbSpTLXD/4ikLvvvs/a61Iv3IOQeD46181fGRw9
nv+j3H0tU0Xl2ilJSl7veQ/F5IqNFceijErEuVhjtLoIjvFn0y6bGRg9lzJ2G07y
ntmvOX775DGELYpymFUWc3eCmPkCeD77bNonGOI4rQnn4W7tY7H44LHV6WK4482g
iEBzcNy/sc4mlyw5wtcXrAFPhrED3n/vp7uatjDDyyKClzDjmchodoRyWovs3VC4
zdA1K2ilPJk3L2XJcfU/uudjhaiclDMmNb33U0dcKGfknJm6xwNIScuybC7kV82i
OLXymdeJeLFxsWkhZ59uAS7FDnzwXo2CDUtpZgG4NViwG0nrU37EDNevYn9u3QFe
voKwjKTPLarudvgYyBr4UAGZozkcyVANWPLmp9V/AQ+MP0YV0AQAzRRPKfteb+qj
ZJa9GSY9j3B5hDyjHevNQ6Y1PGNpoLRb3idUeBZBaGNWruKyZe3vwUIXEyxkNwfm
l7YlIj9MB4vbVBwEZDhjKE30vEsBjxe+gMYRaI985WXV+JiUTEMUg/ZvTYRn/JDj
wZ9FdYTuWFE6yIklDy2WtoGmzCm/9E0hQhn8RkmUQFitBkLwupZfGOnHW7NMUkV1
vLcyG/YIkIHuinasvLKSq0oQ1wMFn770MleUGARnKG6PK0mKN1cwPAYnG0je4oXn
5YpAIjDkOSbLqQ==
=tvq+
-END PGP SIGNATURE End Message ---

Bug#877523: marked as done (openjdk-9 FTBFS with debhelper 10.9)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 09:00:15 +
with message-id 
and subject line Bug#877523: fixed in openjdk-9 9.0.1+11-1
has caused the Debian Bug report #877523,
regarding openjdk-9 FTBFS with debhelper 10.9
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.)


-- 
877523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b181-4
Severity: serious

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

...
dh_icons -a  -Nopenjdk-9-jre-jamvm -Nopenjdk-9-jre-zero \
|| dh_iconcache -a  -Nopenjdk-9-jre-jamvm -Nopenjdk-9-jre-zero
dh_icons: Unknown package openjdk-9-jre-jamvm given via -N/--no-package, 
expected one of: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
dh_icons: unknown option or error during option parsing; aborting
/bin/bash: line 1: dh_iconcache: command not found
debian/rules:2103: recipe for target 'binary-arch' failed
make: [binary-arch] Error 127 (ignored)
dh_link -a  -Nopenjdk-9-jre-jamvm -Nopenjdk-9-jre-zero
dh_link: Unknown package openjdk-9-jre-jamvm given via -N/--no-package, 
expected one of: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
dh_link: unknown option or error during option parsing; aborting
debian/rules:2103: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9.0.1+11-1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-9 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: Fri, 27 Oct 2017 01:44:31 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
Architecture: source amd64 all
Version: 9.0.1+11-1
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-9-jdk - OpenJDK Development Kit (JDK)
 openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-9-jre - OpenJDK Java runtime, using
 openjdk-9-jre-headless - OpenJDK Java runtime, using  (headless)
 openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero
 openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 868205 874265 874292 875288 876069 877523 878272
Changes:
 openjdk-9 (9.0.1+11-1) unstable; urgency=medium
 .
   * OpenJDK 9.0.1+11 release.
   * Bump standards version.
   * Configure with an empty --with-version-pre setting. LP: #1722410.
   * Remove JamVM packaging bits. Closes: #877523.
   * Remove Shark packaging bits.
   * Fix java/javac/jar lockups on SMP Alpha (Michael Cree). Closes: #875288.
   * Fix crashes in i386 applications using JNI due to Hotspot workaround for
 Exec Shield (Ben Hutchings). Closes: #876069.
   * Re-enable building altzero architectures: Closes: #874292.
   * Update the zero-sparc patch (Adrian Glaubitz). Closes: #874265.
   * Fix recommendation of microhei/zenhei font packages. Closes: #868205.
   * Move jmod files into the openjdk-jdk-headless package. Closes: #878272.
Checksums-Sha1:
 d8a360d7f6947ffbf0ce7013240b694fbafc8c86 4496 openjdk-9_9.0.1+11-1.dsc
 a9dc127c6e0892d083535706a89e3ae00ed71b7a 74610589 
openjdk-9_9.0.1+11.orig.tar.gz
 61b09def75e784a58ad48c28f5ebabcd666ef2ec 174456 
openjdk-9_9.0.1+11-1.debian.tar.xz
 

Bug#879917: libgambit4-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/gambit.h

[Andreas Beckmann]

Package: libgambit4-dev
Version: 4.8.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libgambit4-dev.
  Preparing to unpack .../libgambit4-dev_4.8.8-1_amd64.deb ...
  Unpacking libgambit4-dev (4.8.8-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgambit4-dev_4.8.8-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/gambit.h', which is also in package 
libgambc4-dev 4.2.8-2+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libgambit4-dev_4.8.8-1_amd64.deb


cheers,

Andreas


libgambc4-dev=4.2.8-2+b1_libgambit4-dev=4.8.8-1.log.gz
Description: application/gzip

Bug#879912: lxqt-runner: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-runner.desktop

[Andreas Beckmann]

Package: lxqt-runner
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package lxqt-runner.
  Preparing to unpack .../60-lxqt-runner_0.12.0-1_amd64.deb ...
  Unpacking lxqt-runner (0.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-5yHAXI/60-lxqt-runner_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/xdg/autostart/lxqt-runner.desktop', which is also 
in package lxqt-common 0.11.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-5yHAXI/60-lxqt-runner_0.12.0-1_amd64.deb


cheers,

Andreas


lxqt-common=0.11.2-2_lxqt-runner=0.12.0-1.log.gz
Description: application/gzip

Bug#879911: lxqt-powermanagement: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-powermanagement.desktop

[Andreas Beckmann]

Package: lxqt-powermanagement
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package lxqt-powermanagement.
  Preparing to unpack .../78-lxqt-powermanagement_0.12.0-1_amd64.deb ...
  Unpacking lxqt-powermanagement (0.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rT9Wgh/78-lxqt-powermanagement_0.12.0-1_amd64.deb 
(--unpack):
   trying to overwrite '/etc/xdg/autostart/lxqt-powermanagement.desktop', which 
is also in package lxqt-common 0.11.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-rT9Wgh/78-lxqt-powermanagement_0.12.0-1_amd64.deb


cheers,

Andreas


lxqt-common=0.11.2-2_lxqt-powermanagement=0.12.0-1.log.gz
Description: application/gzip

Bug#879910: lxqt-panel: fails to upgrade from 'sid' - trying to overwrite /etc/xdg/autostart/lxqt-panel.desktop

[Andreas Beckmann]

Package: lxqt-panel
Version: 0.12.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package lxqt-panel.
  Preparing to unpack .../90-lxqt-panel_0.12.0-1_amd64.deb ...
  Unpacking lxqt-panel (0.12.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-FKAvKI/90-lxqt-panel_0.12.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/xdg/autostart/lxqt-panel.desktop', which is also 
in package lxqt-common 0.11.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-FKAvKI/90-lxqt-panel_0.12.0-1_amd64.deb


cheers,

Andreas


lxqt-common=0.11.2-2_lxqt-panel=0.12.0-1.log.gz
Description: application/gzip

Bug#873860: ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: illegal multibyte sequence

[Takatsugu Nokubi]

On Fri, 22 Sep 2017 23:20:39 +0900 Osamu Aoki  wrote:
> On Fri, Sep 22, 2017 at 09:14:22AM +0200, John Paul Adrian Glaubitz wrote:
> > This FTBFS can be easily fixed with:
> >
> > --- ibus-anthy-1.5.9.orig/data/zipcode-textdic.py
> > +++ ibus-anthy-1.5.9/data/zipcode-textdic.py
> > @@ -21,7 +21,7 @@ if len(sys.argv) < 2:
> >  anthy_zipfile = sys.argv[1]
> >
> >  try:
> > -contents = codecs.open(anthy_zipfile, 'r', 'euc_jp').read()
> > +contents = codecs.open(anthy_zipfile, 'r', 'utf-8').read()
> >  except UnicodeDecodeError as e:
> >  print('Your file is not eucJP? %s' % anthy_zipfile, file=sys.stderr)
> >  contents = open(anthy_zipfile).read()

I think it seems right way.

> Question is how to coordinate with other anthy users and the latest
> ibus.

I had to see the upstream code, and the script seems not there.
https://github.com/phuang/ibus-anthy/tree/master/data

I think we can choose the 2 ways:

1. just apply this patch
It seems not come from the upstream, so we don't need to take
care about it.

2. fix to work with both encoding zipfile
When the script get the exception, retry to open as utf-8, it may work
both version of anthy.

Processed: retitle 879907 to python{,3}-tempest: fails to upgrade from sid - trying to overwrite /usr/bin/python[23]-check-uuid

[Debian Bug Tracking System]

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

> retitle 879907 python{,3}-tempest: fails to upgrade from sid - trying to 
> overwrite /usr/bin/python[23]-check-uuid
Bug #879907 [python-tempest,python3-tempest] pythoni{,3}-tempest: fails to 
upgrade from 'sid' - trying to overwrite /usr/bin/python[23]-check-uuid
Changed Bug title to 'python{,3}-tempest: fails to upgrade from sid - trying to 
overwrite /usr/bin/python[23]-check-uuid' from 'pythoni{,3}-tempest: fails to 
upgrade from 'sid' - trying to overwrite /usr/bin/python[23]-check-uuid'.
> thanks
Stopping processing here.

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

Bug#867431: marked as done (python3-hacking: incorrect dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 07:35:41 +
with message-id 
and subject line Bug#867431: fixed in python-hacking 0.11.0-2.1
has caused the Debian Bug report #867431,
regarding python3-hacking: incorrect dependencies
to be marked as done.

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

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


-- 
867431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-hacking
Version: 0.8.1-4
Severity: serious
Tags: patch

Due to a cut'n'paste error the dependencies are incorrect.

Fix:

--- debian/control.old  2017-07-06 16:03:45.0 +
+++ debian/control  2017-07-06 16:10:07.0 +
@@ -55,13 +55,13 @@
 
 Package: python3-hacking
 Architecture: all
-Depends: pyflakes,
+Depends: pyflakes3,
  python3-flake8 (>= 3.0.0),
  python3-pbr (>= 1.8),
  python3-pep8 (>= 1.5.7),
  python3-six (>= 1.9.0),
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
 Recommends: ${python3:Recommends},
 Description: Flake8 OpenStack Hacking Guidelines Enforcement plugins - Python 
3.x
  Hacking is a set of flake8 plugins that test and enforce the OpenStack Style
--- End Message ---
--- Begin Message ---
Source: python-hacking
Source-Version: 0.11.0-2.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated python-hacking package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Oct 2017 09:38:55 +0300
Source: python-hacking
Binary: python-hacking python3-hacking python-hacking-doc
Architecture: source
Version: 0.11.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Adrian Bunk 
Description:
 python-hacking - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
Python
 python-hacking-doc - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
doc
 python3-hacking - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
Python
Closes: 867431
Changes:
 python-hacking (0.11.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix the python3-hacking dependencies. (Closes: #867431)
Checksums-Sha1:
 132676ae72cfc916368413be739f2c61585ea614 2695 python-hacking_0.11.0-2.1.dsc
 8dc5e8911035b190590e04015eb4784939eea6d9 5024 
python-hacking_0.11.0-2.1.debian.tar.xz
Checksums-Sha256:
 042a8c4193af8d18031495a30217a19e245d89e8d55764a2dd91b213d9913a56 2695 
python-hacking_0.11.0-2.1.dsc
 176bae3366e3c8547a12ec5ba090051d2dda66e915bae7c012b4f548b2b2460c 5024 
python-hacking_0.11.0-2.1.debian.tar.xz
Files:
 5d57b8e8677cf8011eba39c7a76bc9dd 2695 python optional 
python-hacking_0.11.0-2.1.dsc
 9da2093816273d03b9a078d441de70ff 5024 python optional 
python-hacking_0.11.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlnlplQACgkQiNJCh6LY
mLGxhQ/9F1kNDA9hJr+dZI8JyAptYCLF+0PeYDu9l178zvWqrX4SZ7arWXHgBQ+z
D5ySXEnpCFKh+9X3ldPNdKKyoVGIww2Nujv918Q77THekEkBmyj5bBQp5hZsMMlr
jANtxod3i7Sl0U1sJdsJyFyBBw0NsYKG0c66H+elkVACjDn/0PCFBwBapTqFb9XG
EUp37F54tz2H+IVDkAMkH2HR//7m/SoRIeHHOh2BLgY7ZngFAgWbkSou31WIFYRx
l7Cib7MrCpG0nsXSSg7hxDPqD+47E+xQbbI7qwoE53Bcn3JgkmqmOulWt09KtDhz
Qbl0BloM9+sHIAS60VQTXIM/6+UgnPJfbf16OCxYFjAJ3akon+RRmZ+IND7K6nU3
zEfeVyuLHWyv2yAaBJETiwOSK1uZnY0hT0SUTwQVT25bRctzvHrNFRDSnUyPaFDM
IGTI+eyxK2sHXuDwzAc5zKtDnlt4t5jk02mJReOwdko490xi0J9J5KfSN6bcg8lD
JosAXXnepIVPHFF8Xyki7/ePqsr6NNk0IJC3noCYa3ih8b1wZdSrq+oe46otCePl
Yjx0/ui7nRYvaFnXkUm03+PcIjUL/6rtAzjMmHvlaByk9e/qFULuJ24uNnOHSzSg
xq/AZqLSx7F4ILLAUUQCyJZOiJAGEkidn9Va5JPvdCuX6sSfo3c=
=e6AV
-END PGP SIGNATURE End Message ---

Bug#877541: marked as done (golang-1.9: Invalid instruction error in i386)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 07:35:10 +
with message-id 
and subject line Bug#877541: fixed in golang-1.9 1.9.2-2
has caused the Debian Bug report #877541,
regarding golang-1.9: Invalid instruction error in i386
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=prometheus=i386=1.7.2%2Bds-1=1506959630=0

...
FAILgithub.com/prometheus/prometheus/storage/local [build failed]
...
dh_auto_test: cd build && go test -v -p 4 -timeout 20m 
github.com/prometheus/prometheus/cmd/prometheus 
github.com/prometheus/prometheus/cmd/promtool 
github.com/prometheus/prometheus/config 
github.com/prometheus/prometheus/discovery 
github.com/prometheus/prometheus/discovery/azure 
github.com/prometheus/prometheus/discovery/consul 
github.com/prometheus/prometheus/discovery/dns 
github.com/prometheus/prometheus/discovery/ec2 
github.com/prometheus/prometheus/discovery/file 
github.com/prometheus/prometheus/discovery/gce 
github.com/prometheus/prometheus/discovery/marathon 
github.com/prometheus/prometheus/discovery/openstack 
github.com/prometheus/prometheus/discovery/triton 
github.com/prometheus/prometheus/discovery/zookeeper 
github.com/prometheus/prometheus/notifier 
github.com/prometheus/prometheus/promql 
github.com/prometheus/prometheus/relabel 
github.com/prometheus/prometheus/retrieval 
github.com/prometheus/prometheus/rules github.com/prometheus/prometheus/storage 
github.com/prometheus/pr
 ometheus/storage/fanin github.com/prometheus/prometheus/storage/local 
github.com/prometheus/prometheus/storage/local/chunk 
github.com/prometheus/prometheus/storage/local/codable 
github.com/prometheus/prometheus/storage/local/index 
github.com/prometheus/prometheus/storage/local/storagetool 
github.com/prometheus/prometheus/storage/metric 
github.com/prometheus/prometheus/storage/remote 
github.com/prometheus/prometheus/template 
github.com/prometheus/prometheus/util/cli 
github.com/prometheus/prometheus/util/flock 
github.com/prometheus/prometheus/util/httputil 
github.com/prometheus/prometheus/util/promlint 
github.com/prometheus/prometheus/util/stats 
github.com/prometheus/prometheus/util/strutil 
github.com/prometheus/prometheus/util/testutil 
github.com/prometheus/prometheus/util/treecache 
github.com/prometheus/prometheus/web 
github.com/prometheus/prometheus/web/api/v1 
github.com/prometheus/prometheus/web/ui returned exit code 2
debian/rules:46: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: golang-1.9
Source-Version: 1.9.2-2

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

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated golang-1.9 
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, 27 Oct 2017 08:55:32 +0200
Source: golang-1.9
Binary: golang-1.9-go golang-1.9-src golang-1.9-doc golang-1.9
Architecture: source
Version: 1.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team 
Changed-By: Michael Stapelberg 
Description:
 golang-1.9 - Go programming language compiler - metapackage
 golang-1.9-doc - Go programming language - documentation
 golang-1.9-go - Go programming language compiler, linker, compiled stdlib
 golang-1.9-src - Go programming language - source files
Closes: 877541
Changes:
 golang-1.9 (1.9.2-2) unstable; urgency=medium
 .
   [ Martín Ferrari ]
   * Add debian/patches/0003-Do-not-use-SP-as-index-reg.patch (Closes: #877541)
Checksums-Sha1:
 81e805a7b734d995efaef6daa588682dd85576be 2453 golang-1.9_1.9.2-2.dsc
 59e5637665ea6a940e6004b4cd7954cdf7fe5ee1 31732 golang-1.9_1.9.2-2.debian.tar.xz
 

Bug#879909: libgtksourceview-4-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/glade/catalogs/gtksourceview.xml

[Andreas Beckmann]

Package: libgtksourceview-4-dev
Version: 3.99.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libgtksourceview-4-dev:amd64.
  Preparing to unpack .../22-libgtksourceview-4-dev_3.99.6-1_amd64.deb ...
  Unpacking libgtksourceview-4-dev:amd64 (3.99.6-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-NTh50W/22-libgtksourceview-4-dev_3.99.6-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/glade/catalogs/gtksourceview.xml', which is 
also in package libgtksourceview-3.0-dev:amd64 3.24.5-1


cheers,

Andreas


libgtksourceview-3.0-dev=3.24.5-1_libgtksourceview-4-dev=3.99.6-1.log.gz
Description: application/gzip

Bug#879907: pythoni{,3}-tempest: fails to upgrade from 'sid' - trying to overwrite /usr/bin/python[23]-check-uuid

[Andreas Beckmann]

Package: python-tempest,python3-tempest
Version: 1:17.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package python-tempest.
  Preparing to unpack .../115-python-tempest_1%3a17.0.0-1_all.deb ...
  Unpacking python-tempest (1:17.0.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-E2XqFN/115-python-tempest_1%3a17.0.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/python2-check-uuid', which is also in package 
python-tempest-lib 0.14.0-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-E2XqFN/115-python-tempest_1%3a17.0.0-1_all.deb

  Selecting previously unselected package python3-tempest.
  Preparing to unpack .../111-python3-tempest_1%3a17.0.0-1_all.deb ...
  Unpacking python3-tempest (1:17.0.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-m5KiMk/111-python3-tempest_1%3a17.0.0-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/python3-check-uuid', which is also in package 
python3-tempest-lib 0.14.0-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-m5KiMk/111-python3-tempest_1%3a17.0.0-1_all.deb


cheers,

Andreas


python-tempest-lib=0.14.0-3_python-tempest=1%17.0.0-1.log.gz
Description: application/gzip

Bug#877541: Pending fixes for bugs in the golang package

[pkg-golang-maintainers]

tag 877541 + pending
thanks

Some bugs in the golang package are closed in revision
a0cd15c626ef6aa48037755d3d577f9c6871d1f0 in branch '  golang-1.9' by
Michael Stapelberg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-golang/golang.git/commit/?id=a0cd15c

Commit message:

Add debian/patches/0003-Do-not-use-SP-as-index-reg.patch (Closes: #877541)

Processed: Pending fixes for bugs in the golang package

[Debian Bug Tracking System]

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

> tag 877541 + pending
Bug #877541 [golang-1.9] golang-1.9: Invalid instruction error in i386
Added tag(s) pending.
> thanks
Stopping processing here.

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