Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel

[vic...@gmail.com]

filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916255 for dash

vic...@gmail.com  於 2018年12月12日 週三 下午1:56寫道：
>
> It's dash. dash source src/expand.c, function expmeta calls to
> readdir(), which may throw EOVERFLOW when some field size doesn't fit,
> and add AC_SYS_LARGEFILE to configure.ac fixes this problem.
>
> === BEGIN dash TRACE ===
> Tracing started.
> waitforjob(%0) called
> pid 15608, evaltree(0xfffef918: 0, 1) called
> evalcommand(0xfffef918, 1) called
> expandmeta(0xfffef948, 3) called
> expandmeta(0xfffef968, 3) called
> expandmeta str: /usr/share/vim/*
> expmeta(/usr/share/vim/*, 16, 0) called
> expmeta metaflag 1
> expmeta opendir(/usr/share/vim/)
> expmeta begin loop
> expmeta break loop: readdir error, errno 75
> expmeta end loop
> evalcommand arg: ls
> evalcommand arg: /usr/share/vim/*
> searchexec "ls" returns "/usr/bin/ls"
> === END dash TRACE ===
>
> You-Sheng Yang

Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel

[vic...@gmail.com]

It's dash. dash source src/expand.c, function expmeta calls to
readdir(), which may throw EOVERFLOW when some field size doesn't fit,
and add AC_SYS_LARGEFILE to configure.ac fixes this problem.

=== BEGIN dash TRACE ===
Tracing started.
waitforjob(%0) called
pid 15608, evaltree(0xfffef918: 0, 1) called
evalcommand(0xfffef918, 1) called
expandmeta(0xfffef948, 3) called
expandmeta(0xfffef968, 3) called
expandmeta str: /usr/share/vim/*
expmeta(/usr/share/vim/*, 16, 0) called
expmeta metaflag 1
expmeta opendir(/usr/share/vim/)
expmeta begin loop
expmeta break loop: readdir error, errno 75
expmeta end loop
evalcommand arg: ls
evalcommand arg: /usr/share/vim/*
searchexec "ls" returns "/usr/bin/ls"
=== END dash TRACE ===

You-Sheng Yang

Bug#915484: marked as done (openrocket is an installer that must move to contrib)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 22:35:41 -0700 (MST)
with message-id <20181212053541.2a0941b62...@rover.gag.com>
and subject line closed in 15.03.4
has caused the Debian Bug report #915484,
regarding openrocket is an installer that must move to contrib
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.)


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

openrocket was turned into an installer that downloads
the actual softare during package installation.

In this state it mustn't be in main.
--- End Message ---
--- Begin Message ---
This bug was closed in the 15.03.4 upload, which marked the wrong bug in
its changelog...

Bdale--- End Message ---

Bug#915777: marked as done (mumble: B-D libg15daemon-client-dev is no longer available)

[Debian Bug Tracking System]

Your message dated Wed, 12 Dec 2018 05:20:00 +
with message-id 
and subject line Bug#915777: fixed in mumble 1.3.0~2868~g44b9004+dfsg-2
has caused the Debian Bug report #915777,
regarding mumble: B-D libg15daemon-client-dev is no longer available
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.)


-- 
915777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mumble
Version: 1.2.19-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.3.0~2868~g44b9004+dfsg-1

Hi,

the build dependency libg15daemon-client-dev is no longer available in
sid.


Andreas
--- End Message ---
--- Begin Message ---
Source: mumble
Source-Version: 1.3.0~2868~g44b9004+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mumble 
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: Wed, 12 Dec 2018 04:26:17 +
Source: mumble
Binary: mumble mumble-server
Architecture: source
Version: 1.3.0~2868~g44b9004+dfsg-2
Distribution: experimental
Urgency: medium
Maintainer: Christopher Knadle 
Changed-By: Christopher Knadle 
Description:
 mumble - Low latency encrypted VoIP client
 mumble-server - Low latency encrypted VoIP server
Closes: 915777
Changes:
 mumble (1.3.0~2868~g44b9004+dfsg-2) experimental; urgency=medium
 .
   * debian/backports:
 - Remove directory and files as they're long out of date
   * debian/control:
 - Add Depends: lsb-base for mumble-server pacakge, as init script uses
   lsb init-functions utility
 - Remove Build-Depends: libg15daemon-client-dev due to g15daemon package
   removal (see #914888) (Closes: #915777)
   Thanks to Andreas Beckmann  for reporting the bug.
   * debian/rules:
 - Remove DEB_BUILD_HARDENING since hardening-wrapper has been removed
 - Add CONFIG*=no-g15 to remove G15 keyboard features due to g15daemon
   package removal
   * debian/upstream/metadata:
 - Add metadata file to appease Lintian
Checksums-Sha1:
 d8bbcd5be521f903af142257e9e8bcc7eaf0a717 2275 
mumble_1.3.0~2868~g44b9004+dfsg-2.dsc
 20418f5eb109b31014b2d1d1f79b2ff8bc0d3532 9549893 
mumble_1.3.0~2868~g44b9004+dfsg.orig.tar.gz
 ea5e9d6e1600f944c45eab28d66168521a9d933f 34728 
mumble_1.3.0~2868~g44b9004+dfsg-2.debian.tar.xz
 af46e8bb23260c57060bf46038355053f67a6a45 5771 
mumble_1.3.0~2868~g44b9004+dfsg-2_source.buildinfo
Checksums-Sha256:
 614ee805a559bb8c1ee62587af34867443797a7ce4a6a116eaabec503dbb0f47 2275 
mumble_1.3.0~2868~g44b9004+dfsg-2.dsc
 ea7e05e24b7b708357bf27b30f3fc839acf517e8edbce4f1969b4b620b2ee9ac 9549893 
mumble_1.3.0~2868~g44b9004+dfsg.orig.tar.gz
 31d4890fce8e7c61ee8c542bf136853b6e608e52a2ab0b70f6a4c733b5478b4e 34728 
mumble_1.3.0~2868~g44b9004+dfsg-2.debian.tar.xz
 556d6bf141dc55b8dd3c2c5e1fcfa7a2f5a00abb490e4bcec2135b93658fe288 5771 
mumble_1.3.0~2868~g44b9004+dfsg-2_source.buildinfo
Files:
 629b297570f11575fc646b74daa2e946 2275 sound optional 
mumble_1.3.0~2868~g44b9004+dfsg-2.dsc
 8721a48f0e4428d9d0ac09ba05cc3424 9549893 sound optional 
mumble_1.3.0~2868~g44b9004+dfsg.orig.tar.gz
 4e0784818e21d808dbbc1f8603c4ab35 34728 sound optional 
mumble_1.3.0~2868~g44b9004+dfsg-2.debian.tar.xz
 0bda61f3ff0671654dedd1765b91103c 5771 sound optional 
mumble_1.3.0~2868~g44b9004+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe1KzyGmRW/4DhtV6ieLKD9m6RHAFAlwQkXYACgkQieLKD9m6
RHAZ/A/8CTDJA7EgXJypgfT2nviGiywTiSGjsBx7GrMjYHHYBL2e2Xdm4vz248Sq
MUWlqGnCWqHgDCI0d17yEDymP98Gh2tYHQqPkH0YQlqWhTv+OFkF0bPTR+AEaZ5J
PFt0agxRv9m5j1Jvzg3S5JBGKbjei+8TLcrB25OSTdEZHyKVwcypsTaApubeo4dc
ESZG1t8TwLMNXrQvRYxK7hekQDDIXS7dZ/kPtdSCzXWFjI+pdDd5CSYAGYqjyK0I
0Py4gS+ss+0cn6p529JJflFgJUYtNOkPDUDn81RQj7vjpPpLpeNlak8MWQPro5PE
YCXOi8crX3GqDWENHbnoUNtDycZ8OpwtdiJ0WLsZJeqBNcUTOnDLt8ArxE1D+2tR
/7OtddtbSMEx2cdMAk5gKVMa0ph6q6USd3x803Ucj6QPP520chcBEjz683BoMYF8
eUnyNwjylSfZ89xPO/hOQeEpQ2qXKP3k/yIxngAoA4bNRSgrWfJzRekBDjtAuBHP

Bug#916251: dvd+rw-tools: FTBFS with glibc 2.28

[Logan Rosen]

Source: dvd+rw-tools
Version: 7.1-13
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

dvd+rw-tools currently fails to build from source with glibc 2.28
because they changed the way the 'major' and 'minor' macros can be
accessed. [1] Specifically:

* The macros 'major', 'minor', and 'makedev' are now only available from
  the header ; not from  or various other
  headers that happen to include .  These macros are rarely
  used, not part of POSIX nor XSI, and their names frequently collide with
  user code; see https://sourceware.org/bugzilla/show_bug.cgi?id=19239 for
  further explanation.

   is a GNU extension.  Portable programs that require
  these macros should first include , and then include
   if __GNU_LIBRARY__ is defined.

We saw the following errors while building in Ubuntu accordingly:
growisofs.o growisofs_mmc.o  -lpthread -o growisofs
/usr/bin/ld: growisofs.o: in function `find_raw_device':
./growisofs.c:658: undefined reference to `major'
/usr/bin/ld: ./growisofs.c:659: undefined reference to `minor'
/usr/bin/ld: growisofs.o: in function `grab_sg':
./growisofs.c:704: undefined reference to `minor'
collect2: error: ld returned 1 exit status

This is reproducible in sid as well.

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

  * debian/patches/glibc-2.28.patch: Fix FTBFS with glibc >= 2.28.

Thanks for considering the patch.

Logan Rosen

[1] https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-12-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch 
dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch
--- dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch1969-12-31 
19:00:00.0 -0500
+++ dvd+rw-tools-7.1/debian/patches/glibc-2.28.patch2018-12-11 
23:42:00.0 -0500
@@ -0,0 +1,26 @@
+--- a/growisofs.c
 b/growisofs.c
+@@ -444,6 +444,10 @@
+ #include 
+ #include "mp.h"
+ 
++#if defined(__GNU_LIBRARY__)
++# include 
++#endif
++
+ #if defined(__unix) || defined(__unix__)
+ # include 
+ # include 
+--- a/transport.hxx
 b/transport.hxx
+@@ -53,6 +53,10 @@
+ #define ENV_LOCALE".OCP"
+ #endif
+ 
++#if defined(__GNU_LIBRARY__)
++# include 
++#endif
++
+ #include "asctable.h"
+ 
+ #define CREAM_ON_ERRNO_NAKED(s)   \
diff -Nru dvd+rw-tools-7.1/debian/patches/series 
dvd+rw-tools-7.1/debian/patches/series
--- dvd+rw-tools-7.1/debian/patches/series  2018-10-09 10:05:01.0 
-0400
+++ dvd+rw-tools-7.1/debian/patches/series  2018-12-11 23:38:51.0 
-0500
@@ -10,3 +10,4 @@
 ignore_pseudo_overwrite.patch
 10-blue-ray-bug713016.patch
 fix_burning_bd-r_discs.patch
+glibc-2.28.patch

Bug#865851: Info received (drf-extensions FTBFS with Django 1.11)

[Wookey]

On 2018-12-07 04:03 +, Debian Bug Tracking System wrote:

I have now uploaded drf-extensions 0.4.0-1.1 to delayed/10, so this
should become sorted in due course if everyone is happy with that.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel

[vic...@gmail.com]

Simon McVittie  於 2018年12月12日 週三 上午4:22寫道：
>
> Control: tags -1 + moreinfo
>
> On Wed, 12 Dec 2018 at 00:45:34 +0800, You-Sheng Yang wrote:
> > Somehow dash failed to expand /usr/share/docutils/scripts/python3/*, so
> > that exec variable is simply '/usr/share/docutils/scripts/python3/*',
> > which is later expanded as extra dozens of update-alternatives'
> > arguments. To be more detailed, at the time executed, dash path
> > expansion still worked as it's able to expand /usr/share/* and
> > /usr/share/docutils*, but it failed to expand /usr/share/docutils/* and
> > any other pattern with a /usr/share/docutils/ prefix. Files has been
> > installed correctly and accessible, but dash simply unable to expand
> > such globs.
>
> The obvious question is: why don't basic operations like glob() work
> on the system in question?
>
> Is there something unusual on the system where these expansions failed,
> like a non-standard filesystem or kernel, or weird permissions
> (directories not 0755 or files not 0755 or 0644) anywhere under
> /usr/share/docutils?

They have been correctly installed. Only expanding /usr/share/docutils/* and
any other expanding attempt with a /usr/share/docutils/ prefix failed.
Actually many other directories under /usr/share has the same problem in dash.
Not just /usr/share/docutils.

> You mentioned Docker containers. What is the host system and how are
> these Docker containers configured? If /usr is an overlayfs or similar,
> failing to evaluate a glob might be a bug in the overlay implementation?

I was running docker images from docker.io/vicamo/debian:sid- on the
same host, so the same host configuration applies to all available Debian Sid
images. Other paths have the same issue, with or without python3-docutils
installed. I think the root cause should be in dash, but since ptrace is not
available inside a qemu-based foreign arch container, it would probably take
some time to hunt for the root cause.

> (Since 32-bit ARM and MIPS are not exactly fast machines, I would
> suggest building your kernels with dpkg-buildpackage -B and using an
> x86_64 machine to build documentation, which would maybe sidestep this
> by not needing docutils at all.)

Just like you, I don't like work-arounds, either. Anyway, the problem is
python3-docutils fails to install on container based Sid
armel/armhf/mips/mipsel environments. I don't own a real arm32/MIPS board, so
I cannot verify if this also happens outside a qemu jail. But while many
debian installations today are actually container images, I'd still say this
is critical enough that I would recommend a quick fix to unblock all other
people while the issue being investigated.

> > Replace that path glob with a `find ... -type f` fixes the problem.
>
> Sorry, I don't think python3-docutils can be expected to swap a path
> expansion for a subprocess that ought to be equivalent to work around
> whatever is going on with these systems - and definitely not without
> understanding what it is that's going wrong and why.
>
> smcv

You-Sheng Yang

Bug#908160: Delayed NMU, diff

[Hilko Bengen]

Dear maintainer,

I have just NMU'd open-iscsi/2.0.874-7.1, delayed by 5 days. Relevant
diffs are attached to this mail. Feel free to reschedule or cancel my
upload as you see fit.

Cheers,
-Hilko
>From 38db62d2cae88adb9f5c9d9622cb7ef9fdb9728a Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Wed, 12 Dec 2018 01:01:21 +0100
Subject: [PATCH 1/2] Update patch for missing macro (Closes: #908160)

---
 ...lude-sys-sysmacros.h-to-properly-define-minor.patch | 18 --
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/debian/patches/include-sys-sysmacros.h-to-properly-define-minor.patch b/debian/patches/include-sys-sysmacros.h-to-properly-define-minor.patch
index f6322c7..857acd2 100644
--- a/debian/patches/include-sys-sysmacros.h-to-properly-define-minor.patch
+++ b/debian/patches/include-sys-sysmacros.h-to-properly-define-minor.patch
@@ -1,8 +1,10 @@
 Description: Include  to properly define minor()
 Origin: upstream, https://github.com/open-iscsi/open-iscsi/commit/6d68ef5871c94c6ebbbe6e6b1fe0bc2dce711052
 
 a/iscsiuio/src/unix/libs/bnx2x.c
-+++ b/iscsiuio/src/unix/libs/bnx2x.c
+Index: open-iscsi/iscsiuio/src/unix/libs/bnx2x.c
+===
+--- open-iscsi.orig/iscsiuio/src/unix/libs/bnx2x.c
 open-iscsi/iscsiuio/src/unix/libs/bnx2x.c
 @@ -50,6 +50,7 @@
  #include 
  #include 
@@ -11,3 +13,15 @@ Origin: upstream, https://github.com/open-iscsi/open-iscsi/commit/6d68ef5871c94c
  
  #include "config.h"
  
+Index: open-iscsi/iscsiuio/src/unix/libs/bnx2.c
+===
+--- open-iscsi.orig/iscsiuio/src/unix/libs/bnx2.c
 open-iscsi/iscsiuio/src/unix/libs/bnx2.c
+@@ -46,6 +46,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "config.h"
+ 
-- 
2.11.0

>From 73195ad1bfc267f112045f1d722783dc992400c7 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Wed, 12 Dec 2018 01:06:25 +0100
Subject: [PATCH 2/2] Debian release 2.0.874-7.1

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

diff --git a/debian/changelog b/debian/changelog
index 2ceddc1..1c4b15d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+open-iscsi (2.0.874-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * [38db62d] Update patch for missing macro (Closes: #908160)
+
+ -- Hilko Bengen   Wed, 12 Dec 2018 01:05:19 +0100
+
 open-iscsi (2.0.874-7) unstable; urgency=medium
 
   * [eeda27c] Enable back pristine-tar as we have now committed it
-- 
2.11.0

Processed: Re: lsof FTBFS with glibc 2.28

[Debian Bug Tracking System]

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

> tags 916160 + patch
Bug #916160 [src:lsof] lsof FTBFS with glibc 2.28
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#916017: marked as done (pax FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 23:50:31 +
with message-id 
and subject line Bug#916017: fixed in pax 1:20171021-3
has caused the Debian Bug report #916017,
regarding pax FTBFS with glibc 2.28
to be marked as done.

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

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


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

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

...
cpio.c: In function 'vcpio_wr':
pax.h:261:18: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 #define MAJOR(x) major(x)
  ^
cpio.c:777:53: note: in expansion of macro 'MAJOR'
  t_major = (anonarch & ANON_INODES) ? 0UL : (u_long)MAJOR(arcn->sb.st_dev);
 ^
pax.h:262:18: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
 #define MINOR(x) minor(x)
  ^
cpio.c:778:53: note: in expansion of macro 'MINOR'
  t_minor = (anonarch & ANON_INODES) ? 0UL : (u_long)MINOR(arcn->sb.st_dev);
 ^
In file included from gen_subs.c:55:
gen_subs.c: In function 'ls_list':
pax.h:261:18: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
 #define MAJOR(x) major(x)
  ^
gen_subs.c:123:50: note: in expansion of macro 'MAJOR'
   (void)fprintf(fp, "%4lu,%4lu ", (unsigned long)MAJOR(sbp->st_rdev),
  ^
...
/usr/bin/ld: /tmp/cc4cCtFm.o: in function `vcpio_rd':
./cpio.c:628: undefined reference to `makedev'
/usr/bin/ld: ./cpio.c:631: undefined reference to `makedev'
/usr/bin/ld: /tmp/cc4cCtFm.o: in function `vcpio_wr':
./cpio.c:777: undefined reference to `major'
/usr/bin/ld: ./cpio.c:778: undefined reference to `minor'
/usr/bin/ld: ./cpio.c:850: undefined reference to `major'
/usr/bin/ld: ./cpio.c:852: undefined reference to `minor'
/usr/bin/ld: /tmp/ccSVOR4l.o: in function `ls_list':
./gen_subs.c:124: undefined reference to `minor'
/usr/bin/ld: ./gen_subs.c:123: undefined reference to `major'
/usr/bin/ld: /tmp/cc0rXSax.o: in function `ustar_rd':
./tar.c:842: undefined reference to `makedev'
/usr/bin/ld: /tmp/cc0rXSax.o: in function `ustar_wr':
./tar.c:992: undefined reference to `major'
/usr/bin/ld: ./tar.c:994: undefined reference to `minor'
collect2: error: ld returned 1 exit status
make: *** [debian/rules:55: debian/.build_stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: pax
Source-Version: 1:20171021-3

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

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

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

Debian distribution maintenance software
pp.
Thorsten Glaser  (supplier of updated pax 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: SHA384

Format: 1.8
Date: Wed, 12 Dec 2018 00:19:19 +0100
Source: pax
Binary: pax
Architecture: source i386
Version: 1:20171021-3
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser 
Changed-By: Thorsten Glaser 
Description:
 pax- Portable Archive Interchange (cpio, pax, tar)
Closes: 890810 916017
Changes:
 pax (1:20171021-3) unstable; urgency=low
 .
   [ Jonathan de Boyne Pollard ]
   * Fix timestamp setting (#890810)
 .
   [ Thorsten Glaser ]
   * Policy 4.2.1.5
 - R³: no
 - terse build option
   * Use Linux libc5  also for glibc 2.28+ (Closes: #916017)
   * Quell a compiler warnung about restrict qualifier in sigaction use
 (passing a NULL third argument, when not interested in the result)
   * Update lintian overrides
   * Add UMEGAYA metadata
   * Handle deferred symlinks correctly (Closes: #890810)
Checksums-Sha1:
 6d703a3329644ce9b0e0478c7f63f97310486356 1902 pax_20171021-3.dsc
 8e193912f7a046439032517a4d12926c5cc0dc81 10768 pax_20171021-3.debian.tar.xz
 97d95d69b6f51b1b718c06590a9bfc954d91dfcf 127052 pax-dbgsym_20171021-3_i386.deb
 78b334c8e2fc82e0b1048cf270cdbf634db72bd3 4513 

Processed: severity of 916243 is serious

[Debian Bug Tracking System]

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

> severity 916243 serious
Bug #916243 [gitlab] gitlab installation failure
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#916160: lsof FTBFS with glibc 2.28

[Andres Salomon]

Hi,

Just FYI, this build failure is already fixed in the latest version of 
lsof (4.91).


I've attached a backport of the upstream fix.  I (or someone else) could
NMU 4.89, but given that we're still a month away from the transition
freeze I'd much rather see lsof updated to the new version.  Norbert, 
are

you looking for a co-maintainer or someone to take this package?

Thanks,
Andres




--- lsof-4.89+dfsg/tests/LsofTest.h	2008-07-05 09:21:17.0 -0700
+++ lsof_4.91_src/tests/LsofTest.h	2018-02-14 06:21:50.0 -0800
@@ -31,7 +31,7 @@
 
 
 /*
- * $Id: LsofTest.h,v 1.12 2008/07/05 16:21:07 abe Exp $
+ * $Id: LsofTest.h,v 1.13 2018/02/14 14:21:44 abe Exp $
  */
 
 
@@ -77,6 +77,12 @@
 #include 
 
 #include 
+
+#if	defined(LT_DIAL_linux) && LT_VERS>=414014
+#undef	major
+#include 
+#endif	/* defined(LT_DIAL_linux) && LT_VERS>=414014 */
+
 #include 
 #include 
 

Processed: severity of 916236 is serious

[Debian Bug Tracking System]

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

> severity 916236 serious
Bug #916236 [golang-golang-x-net-dev] golang-golang-x-net-dev: FTBFS on s390x - 
rawconn.go undefined: getsockopt
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#916223: moonshot-gss-eap: FTBFS against xmltooling 3

[Sam Hartman]

Fixing moonshot-gss-eap and getting a new moonshot-ui is next up for me
for Debian weekend tasks.

Bug#910577: marked as done (gdb-multiarch: libbabeltrace1 dependency not tight enough)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 23:04:16 +
with message-id 
and subject line Bug#910577: fixed in babeltrace 1.5.6-2
has caused the Debian Bug report #910577,
regarding gdb-multiarch: libbabeltrace1 dependency not tight enough
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.)


-- 
910577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb-multiarch
Version: 8.1-4
Severity: important

gdb-multiarch requires libbabeltrace-ctf1.

  --\ Versions of libbabeltrace-ctf1 (3)

p1.5.1-1
i1.5.6-1
i A  libbabeltrace1 1.5.6-1

Apparently the build process picks up the fact that libbabeltrace-1.5.6-1
contains the -ctf sub-library, but then doesn't depend on >=1.5.6.
Thus 1.5.1 ends up being installed, which doesn't contain the plugin.

Manually updating libbabeltrace1 to 1.5.6-1 fixes the problem.

-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (800, 'stable'), (750, 'testing'), (700, 'unstable'), (650, 
'oldstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.17.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 gdb-multiarch depends on:
ii  gdb 7.12-6+b2
pn  libbabeltrace-ctf1  
ii  libbabeltrace1  1.5.6-1
ii  libc6   2.27-3
ii  libexpat1   2.2.5-3
pn  libipt2 
ii  liblzma55.2.2-1.3
ii  libncurses5 6.1+20180714-1
ii  libncursesw66.1+20180210-4
ii  libpython2.72.7.15-1
pn  libpython3.5
ii  libpython3.63.6.6-1
ii  libreadline66.3-9
ii  libreadline77.0-5
ii  libtinfo5   6.1+20180714-1
ii  libtinfo6   6.1+20180210-4
ii  zlib1g  1:1.2.11.dfsg-1

gdb-multiarch recommends no packages.

gdb-multiarch suggests no packages.
--- End Message ---
--- Begin Message ---
Source: babeltrace
Source-Version: 1.5.6-2

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

Debian distribution maintenance software
pp.
Michael Jeanson  (supplier of updated babeltrace 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, 11 Dec 2018 16:52:03 -0500
Source: babeltrace
Binary: babeltrace libbabeltrace1 libbabeltrace-ctf1 libbabeltrace-dev 
libbabeltrace-ctf-dev python3-babeltrace
Architecture: source
Version: 1.5.6-2
Distribution: unstable
Urgency: medium
Maintainer: Jon Bernard 
Changed-By: Michael Jeanson 
Description:
 babeltrace - Trace conversion program
 libbabeltrace-ctf-dev - Babeltrace development files (transitional package)
 libbabeltrace-ctf1 - Babeltrace conversion libraries (transitional package)
 libbabeltrace-dev - Babeltrace development files
 libbabeltrace1 - Babeltrace conversion libraries
 python3-babeltrace - Babeltrace Python 3 bindings
Closes: 910577
Changes:
 babeltrace (1.5.6-2) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * [8be51d5] Remove unnecessary X-Python{,3}-Version field in debian/control.
 .
   [ Michael Jeanson ]
   * [55f7b4a] Force shlibs depends on >=1.5.3-2 (Closes: #910577)
   * [9ba4f13] Add Build-Depends-Package to symbols file
   * [d96442e] Bump standards version to 4.2.1
Checksums-Sha1:
 9426eaf89a2e2d00611b9de4697f2cd82b63cc9a 2670 babeltrace_1.5.6-2.dsc
 bb272d5857f48b85dae1e0ee7f90833640c48f64 11344 babeltrace_1.5.6-2.debian.tar.xz
 01fecfe4a9790fe4910da4f3abc6d647bb36cde2 7676 
babeltrace_1.5.6-2_source.buildinfo
Checksums-Sha256:
 5c162e436e23881c0dcf1eaf6a250c671fa8972b4d4161e9629ca551457b95ab 2670 
babeltrace_1.5.6-2.dsc
 e127121d7e96451b7189b4599fd951812d037e94cee2cdabb20a6c7d991dfc2f 11344 
babeltrace_1.5.6-2.debian.tar.xz
 3071230ebec4557a5c9b5f3ec274b7d08532831007efeef966d0a3459a28bd79 7676 
babeltrace_1.5.6-2_source.buildinfo
Files:

Bug#915059: RM: fuji -- RoQA; low popcon, RC buggy

[Dr. Tobias Quathamer]

control: reassign -1 ftp.debian.org
control: retitle -1 RM: fuji -- RoQA; low popcon, RC buggy
control: severity -1 normal
control: tags -1 - buster sid

Dear FTP team,

please remove the package fuji from unstable. It has been RC buggy for
over a year (#876827) without a maintainer response. I've tried to
contact the maintainer to ask about removal of this package (see this
bug), also without a response. The package has a low popcon value of 3.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Processed: RM: fuji -- RoQA; low popcon, RC buggy

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #915059 [src:fuji] fuji: Should the package be removed?
Bug reassigned from package 'src:fuji' to 'ftp.debian.org'.
No longer marked as found in versions fuji/1.0.2-1.
Ignoring request to alter fixed versions of bug #915059 to the same values 
previously set
> retitle -1 RM: fuji -- RoQA; low popcon, RC buggy
Bug #915059 [ftp.debian.org] fuji: Should the package be removed?
Changed Bug title to 'RM: fuji -- RoQA; low popcon, RC buggy' from 'fuji: 
Should the package be removed?'.
> severity -1 normal
Bug #915059 [ftp.debian.org] RM: fuji -- RoQA; low popcon, RC buggy
Severity set to 'normal' from 'serious'
> tags -1 - buster sid
Bug #915059 [ftp.debian.org] RM: fuji -- RoQA; low popcon, RC buggy
Removed tag(s) sid and buster.

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

Bug#915734: marked as done (ghdl still uses GCC 7)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 22:43:24 +
with message-id 
and subject line Bug#915734: fixed in ghdl 0.35+git20181129+dfsg-1
has caused the Debian Bug report #915734,
regarding ghdl still uses 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.)


-- 
915734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ghdl
Version: 0.35+git20180503+dfsg-2
Severity: serious
Tags: sid buster

Please use the default GCC for the package so that we can remove GCC 7 for the
buster release.
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.35+git20181129+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated ghdl 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, 11 Dec 2018 20:16:23 +
Source: ghdl
Binary: ghdl ghdl-mcode ghdl-gcc ghdl-llvm
Architecture: source amd64
Version: 0.35+git20181129+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Description:
 ghdl   - VHDL compiler/simulator
 ghdl-gcc   - VHDL compiler/simulator (GCC backend)
 ghdl-llvm  - VHDL compiler/simulator (LLVM backend)
 ghdl-mcode - VHDL compiler/simulator (mcode backend)
Closes: 912564 913945 915734
Changes:
 ghdl (0.35+git20181129+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
 * Refresh modify-install-paths
 * Allow builds with LLVM 7+ (Closes: #912564)
   * Switch to GCC 8 (Closes: #915734)
   * Add dependency on zlib1g-dev for gcc and LLVM backends (Closes: #913945)
Checksums-Sha1:
 4bc8cfea50a418d5be267eeeac4e23e9f2906ec9 2555 ghdl_0.35+git20181129+dfsg-1.dsc
 1cb1b53988ec574bf52df9353a4496fe73627179 2502348 
ghdl_0.35+git20181129+dfsg.orig.tar.xz
 6215658b5791c86fb7bd80eda04decee6368c863 16880 
ghdl_0.35+git20181129+dfsg-1.debian.tar.xz
 4dd69ccac87652b997414143c6f6b7e615a2a06d 71852088 
ghdl-gcc-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 61df3faed624ee5e96ef643ed151c769475b7624 7498412 
ghdl-gcc_0.35+git20181129+dfsg-1_amd64.deb
 1f0b228ffef903200c48a4cd24122fff924cd7e0 644044 
ghdl-llvm-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 7cfdca37be2eed5400f1f3448e4243a2f2d40be7 1385620 
ghdl-llvm_0.35+git20181129+dfsg-1_amd64.deb
 a45e354c58072b6ea94cca24fa0415d69e6696f6 1357084 
ghdl-mcode-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 bbdda52a23fc4c032cb8c4785d0c33a71e19684b 1058680 
ghdl-mcode_0.35+git20181129+dfsg-1_amd64.deb
 6557d9f07498175d439e9eb8e39fefaf4b532076 8375 
ghdl_0.35+git20181129+dfsg-1_amd64.buildinfo
 aa25c72e01969d3a5539ebb3b3d0732660956e67 69644 
ghdl_0.35+git20181129+dfsg-1_amd64.deb
Checksums-Sha256:
 e34ff8a099af0baca121b5a85ab6154660f4b781b0d694b1393f227c2be855c3 2555 
ghdl_0.35+git20181129+dfsg-1.dsc
 eb3f74e0bc13f824c48939f5b65cb24e8f11b60501ca66f3214bf06bdaaa7945 2502348 
ghdl_0.35+git20181129+dfsg.orig.tar.xz
 025ef27e5dacd1f1ae0f5df9091e60b4cc6d9f5612707e3e200a77c967f5162a 16880 
ghdl_0.35+git20181129+dfsg-1.debian.tar.xz
 5467d97d711ab4baf5a7acccbc57889e689bad5fe2077be90cd607bcd02b994c 71852088 
ghdl-gcc-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 2c59c67e3c836adc1f132911546ff99ad82cda3777b952ff4a30b9eed1554ffb 7498412 
ghdl-gcc_0.35+git20181129+dfsg-1_amd64.deb
 67fac2aacd57c57fe5ba75fb617d3c809c841ea9fe14a86eb8117acb71c9c701 644044 
ghdl-llvm-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 42021224277a39968d7e2becb19df2e80d5526421ab278f339446edb1f8be0bf 1385620 
ghdl-llvm_0.35+git20181129+dfsg-1_amd64.deb
 9ca9bdd64d81c625e1c903d8b45132b252be136d6a53078af3a6d0c4284a18d5 1357084 
ghdl-mcode-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 3d1855d8ce301364102c1bf66aaefeabc14a7801a00070b43f0464f4d42ad140 1058680 
ghdl-mcode_0.35+git20181129+dfsg-1_amd64.deb
 c7865ffdce5def418fd7bcd37cd0d5cc13423738b17945de8418fa473ed8b0b1 8375 
ghdl_0.35+git20181129+dfsg-1_amd64.buildinfo
 9165e82bafff95cac11b4c412ecfc76d9e73c4a3ffd44c6af5397e5bd6d2f98c 69644 

Bug#912564: marked as done (ghdl FTBFS with llvm/clang 7)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 22:43:24 +
with message-id 
and subject line Bug#912564: fixed in ghdl 0.35+git20181129+dfsg-1
has caused the Debian Bug report #912564,
regarding ghdl FTBFS with llvm/clang 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.)


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

Dear Maintainer,

We updated llvm-defaults to llvm-toolchain-7.

This package FTBFS using this version:
dpkg-source: info: using options from 
ghdl-0.35+git20180503+dfsg/debian/source/options: --compression=xz
dpkg-checkbuilddeps: error: Unmet build dependencies: llvm-dev (<< 1:7.0~) 
clang (<< 1:7.0~)
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)

Cheers,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.35+git20181129+dfsg-1

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated ghdl 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, 11 Dec 2018 20:16:23 +
Source: ghdl
Binary: ghdl ghdl-mcode ghdl-gcc ghdl-llvm
Architecture: source amd64
Version: 0.35+git20181129+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Description:
 ghdl   - VHDL compiler/simulator
 ghdl-gcc   - VHDL compiler/simulator (GCC backend)
 ghdl-llvm  - VHDL compiler/simulator (LLVM backend)
 ghdl-mcode - VHDL compiler/simulator (mcode backend)
Closes: 912564 913945 915734
Changes:
 ghdl (0.35+git20181129+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
 * Refresh modify-install-paths
 * Allow builds with LLVM 7+ (Closes: #912564)
   * Switch to GCC 8 (Closes: #915734)
   * Add dependency on zlib1g-dev for gcc and LLVM backends (Closes: #913945)
Checksums-Sha1:
 4bc8cfea50a418d5be267eeeac4e23e9f2906ec9 2555 ghdl_0.35+git20181129+dfsg-1.dsc
 1cb1b53988ec574bf52df9353a4496fe73627179 2502348 
ghdl_0.35+git20181129+dfsg.orig.tar.xz
 6215658b5791c86fb7bd80eda04decee6368c863 16880 
ghdl_0.35+git20181129+dfsg-1.debian.tar.xz
 4dd69ccac87652b997414143c6f6b7e615a2a06d 71852088 
ghdl-gcc-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 61df3faed624ee5e96ef643ed151c769475b7624 7498412 
ghdl-gcc_0.35+git20181129+dfsg-1_amd64.deb
 1f0b228ffef903200c48a4cd24122fff924cd7e0 644044 
ghdl-llvm-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 7cfdca37be2eed5400f1f3448e4243a2f2d40be7 1385620 
ghdl-llvm_0.35+git20181129+dfsg-1_amd64.deb
 a45e354c58072b6ea94cca24fa0415d69e6696f6 1357084 
ghdl-mcode-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 bbdda52a23fc4c032cb8c4785d0c33a71e19684b 1058680 
ghdl-mcode_0.35+git20181129+dfsg-1_amd64.deb
 6557d9f07498175d439e9eb8e39fefaf4b532076 8375 
ghdl_0.35+git20181129+dfsg-1_amd64.buildinfo
 aa25c72e01969d3a5539ebb3b3d0732660956e67 69644 
ghdl_0.35+git20181129+dfsg-1_amd64.deb
Checksums-Sha256:
 e34ff8a099af0baca121b5a85ab6154660f4b781b0d694b1393f227c2be855c3 2555 
ghdl_0.35+git20181129+dfsg-1.dsc
 eb3f74e0bc13f824c48939f5b65cb24e8f11b60501ca66f3214bf06bdaaa7945 2502348 
ghdl_0.35+git20181129+dfsg.orig.tar.xz
 025ef27e5dacd1f1ae0f5df9091e60b4cc6d9f5612707e3e200a77c967f5162a 16880 
ghdl_0.35+git20181129+dfsg-1.debian.tar.xz
 5467d97d711ab4baf5a7acccbc57889e689bad5fe2077be90cd607bcd02b994c 71852088 
ghdl-gcc-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 2c59c67e3c836adc1f132911546ff99ad82cda3777b952ff4a30b9eed1554ffb 7498412 
ghdl-gcc_0.35+git20181129+dfsg-1_amd64.deb
 67fac2aacd57c57fe5ba75fb617d3c809c841ea9fe14a86eb8117acb71c9c701 644044 
ghdl-llvm-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 42021224277a39968d7e2becb19df2e80d5526421ab278f339446edb1f8be0bf 1385620 
ghdl-llvm_0.35+git20181129+dfsg-1_amd64.deb
 9ca9bdd64d81c625e1c903d8b45132b252be136d6a53078af3a6d0c4284a18d5 1357084 
ghdl-mcode-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 

Bug#913945: marked as done (should depend on zlib1g-dev 8and build-essential?))

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 22:43:24 +
with message-id 
and subject line Bug#913945: fixed in ghdl 0.35+git20181129+dfsg-1
has caused the Debian Bug report #913945,
regarding should depend on zlib1g-dev 8and build-essential?)
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.)


-- 
913945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghdl-gcc
Version: 0.35+git20180503+dfsg-2
Severity: grave

Dear maintainer,

I installed ghdl{,-gcc,-mcode} build-essential, but ''ghdl-gcc -e'' gives an 
error:

$ ghdl-gcc -a hello_world
$ ghdl-gcc -e hello_world
/usr/bin/ld: cannot find -lz
collect2: error: ld returned 1 exit status
ghdl-gcc:error: compilation error

Installing zlib1g-dev fixes that. Moreover, should ghdl-gcc also depend on 
build-essential or gcc?

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages ghdl-gcc depends on:
ii  ghdl   0.35+git20180503+dfsg-2
ii  libc6  2.27-8
ii  libgcc11:8.2.0-9
ii  libgmp10   2:6.1.2+dfsg-3
ii  libgnat-7  7.3.0-30
ii  libmpc31.1.0-1
ii  libmpfr6   4.0.1-1
ii  zlib1g 1:1.2.11.dfsg-1

ghdl-gcc recommends no packages.

ghdl-gcc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ghdl
Source-Version: 0.35+git20181129+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated ghdl 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, 11 Dec 2018 20:16:23 +
Source: ghdl
Binary: ghdl ghdl-mcode ghdl-gcc ghdl-llvm
Architecture: source amd64
Version: 0.35+git20181129+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Jonathan McDowell 
Description:
 ghdl   - VHDL compiler/simulator
 ghdl-gcc   - VHDL compiler/simulator (GCC backend)
 ghdl-llvm  - VHDL compiler/simulator (LLVM backend)
 ghdl-mcode - VHDL compiler/simulator (mcode backend)
Closes: 912564 913945 915734
Changes:
 ghdl (0.35+git20181129+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
 * Refresh modify-install-paths
 * Allow builds with LLVM 7+ (Closes: #912564)
   * Switch to GCC 8 (Closes: #915734)
   * Add dependency on zlib1g-dev for gcc and LLVM backends (Closes: #913945)
Checksums-Sha1:
 4bc8cfea50a418d5be267eeeac4e23e9f2906ec9 2555 ghdl_0.35+git20181129+dfsg-1.dsc
 1cb1b53988ec574bf52df9353a4496fe73627179 2502348 
ghdl_0.35+git20181129+dfsg.orig.tar.xz
 6215658b5791c86fb7bd80eda04decee6368c863 16880 
ghdl_0.35+git20181129+dfsg-1.debian.tar.xz
 4dd69ccac87652b997414143c6f6b7e615a2a06d 71852088 
ghdl-gcc-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 61df3faed624ee5e96ef643ed151c769475b7624 7498412 
ghdl-gcc_0.35+git20181129+dfsg-1_amd64.deb
 1f0b228ffef903200c48a4cd24122fff924cd7e0 644044 
ghdl-llvm-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 7cfdca37be2eed5400f1f3448e4243a2f2d40be7 1385620 
ghdl-llvm_0.35+git20181129+dfsg-1_amd64.deb
 a45e354c58072b6ea94cca24fa0415d69e6696f6 1357084 
ghdl-mcode-dbgsym_0.35+git20181129+dfsg-1_amd64.deb
 bbdda52a23fc4c032cb8c4785d0c33a71e19684b 1058680 
ghdl-mcode_0.35+git20181129+dfsg-1_amd64.deb
 6557d9f07498175d439e9eb8e39fefaf4b532076 8375 
ghdl_0.35+git20181129+dfsg-1_amd64.buildinfo
 aa25c72e01969d3a5539ebb3b3d0732660956e67 69644 
ghdl_0.35+git20181129+dfsg-1_amd64.deb
Checksums-Sha256:
 e34ff8a099af0baca121b5a85ab6154660f4b781b0d694b1393f227c2be855c3 2555 
ghdl_0.35+git20181129+dfsg-1.dsc
 eb3f74e0bc13f824c48939f5b65cb24e8f11b60501ca66f3214bf06bdaaa7945 2502348 
ghdl_0.35+git20181129+dfsg.orig.tar.xz
 025ef27e5dacd1f1ae0f5df9091e60b4cc6d9f5612707e3e200a77c967f5162a 16880 

Processed: tagging 915337

[Debian Bug Tracking System]

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

> tags 915337 + moreinfo
Bug #915337 [src:rr] rr: baseline violation on i386
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 21:48:56 +
with message-id 
and subject line Bug#899745: fixed in xfce4-systemload-plugin 1.2.2-1
has caused the Debian Bug report #899745,
regarding xfce4-systemload-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of xfce4-systemload-plugin,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-systemload-plugin
Source-Version: 1.2.2-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Dec 2018 22:08:47 +0100
Source: xfce4-systemload-plugin
Binary: xfce4-systemload-plugin
Architecture: source
Version: 1.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-systemload-plugin - system load monitor plugin for the Xfce4 panel
Closes: 899745
Changes:
 xfce4-systemload-plugin (1.2.2-1) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899745
   * d/gbp.conf added, following DEP-14
   * d/control: run wrap-and-sort
   * d/watch: use HTTPS protocol
   * New upstream version 1.2.2
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.2.1
   * d/control: use HTTPS for homepage field
   * d/control: update build-deps for new upstream version
   * d/control: drop duplicate section field
   * d/copyright: update source url
   * update debhelper compat to 10
Checksums-Sha1:
 9d27108c8e1db26ccedf3855193f92600a707fcc 1871 

Bug#916219: marked as done (nixnote2: Non-free icon)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 21:46:12 +
with message-id 
and subject line Bug#916219: fixed in nixnote2 2.1.1+git20181211-1
has caused the Debian Bug report #916219,
regarding nixnote2: Non-free icon
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.)


-- 
916219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nixnote2
Version: 2.1.1-1
Severity: serious

Nixnote2 before 2.1.1 (including 2.1.1) is using a CC-BY-ND icon,
which is incompatible with DFSG.

This problem has been fixed by using a GPL-3-licensed icon to replace
the old one in git trunk. We should consider uploading the git trunk
version (or the next upstream release) before Buster freeze.

--
Thanks,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Source: nixnote2
Source-Version: 2.1.1+git20181211-1

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated nixnote2 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, 11 Dec 2018 16:02:23 -0500
Source: nixnote2
Binary: nixnote2
Architecture: source
Version: 2.1.1+git20181211-1
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang 
Changed-By: Boyuan Yang 
Description:
 nixnote2   - Open Source Evernote client
Closes: 916219
Changes:
 nixnote2 (2.1.1+git20181211-1) unstable; urgency=medium
 .
   * New upstream git snapshot 20181211.
 + Replace non-free icon with a GPL-3-licensed one.
   (Closes: #916219)
   * debian/patches:
 - Drop merged patches.
   * debian/copyright:
 + Update copyright for icons.
Checksums-Sha1:
 26b6e19d22d00d774be97ca6482f6cc0d454a497 2172 nixnote2_2.1.1+git20181211-1.dsc
 7d882dfa13a4c5727d7ab9bbf3ba708cbd0f7c08 3245312 
nixnote2_2.1.1+git20181211.orig.tar.gz
 e20d62044a1fe70e93e8b2651a65bcddb6fd085f 5044 
nixnote2_2.1.1+git20181211-1.debian.tar.xz
 52aaff3d9461a1930d5b4a145771199fee0adebc 13623 
nixnote2_2.1.1+git20181211-1_amd64.buildinfo
Checksums-Sha256:
 0cbc6fa426555738ecfa691adc039845a8ff86f49d6aa5d8d7d6c3bd927ed30b 2172 
nixnote2_2.1.1+git20181211-1.dsc
 7d139043b16db9dc103129dbaa1cbc938bb2a2433b2091c325066a44ce4e7f4b 3245312 
nixnote2_2.1.1+git20181211.orig.tar.gz
 dbce53d02879ab9172461d55a1a8380d47c8493cc0e48583ff54399db6bebab9 5044 
nixnote2_2.1.1+git20181211-1.debian.tar.xz
 c402280dfa67c3ed1ab92e8e60216dd2bd0a4caf6b4eaa7fc62b680cc41c15e9 13623 
nixnote2_2.1.1+git20181211-1_amd64.buildinfo
Files:
 c9067bffb698dc441af85d4fed3c9f99 2172 utils optional 
nixnote2_2.1.1+git20181211-1.dsc
 36d942759c66f52095b5fd1af10fd639 3245312 utils optional 
nixnote2_2.1.1+git20181211.orig.tar.gz
 76d8b764cbcb1a367fa0c082f8271885 5044 utils optional 
nixnote2_2.1.1+git20181211-1.debian.tar.xz
 75bd46d56bb627151122746c993f5d2e 13623 utils optional 
nixnote2_2.1.1+git20181211-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlwQKF8ACgkQwpPntGGC
Ws5Agw/6A4oagwSeWa5498u/I5qxW8S/vy7AL1jhSyf/9nTRr7UThu8ASOfPgjEc
d1b+WkRVMyiiJKprpT3hWrOp7IrmaC9M+qzOitC0+0kK0/DiD6x1IQkNY+Nhu/6H
s4O2nW3qUM1qDfGF23mRILpRnh+2pPNvuDtbTUlD4K06fTbzfN6/vF+ZI7hmXmjb
1YTa+nUUUfOZ4ttjvjTqTke6SYVE3AG60+zXnWfmN8Mx+3S5AWTP9hjCmlEP2e/U
tnRzkfcTauSSn20AUTBRQAH6QDxgm1oPZBHLLVoenBaLQpVII4kzEKPUOuh1ydW+
6MeKrYegeUfFxVWF7N3Nx9vRRxj38N+5SyH92oxbqkkh7YpAKJLtbfPpIutnbOb3
wr9juUAUPuoK4KLnGdti8MqfpgwqLzfp9TzP2ZeVw7Pd6OqGK5ryHBdofuwMqLii
ZFJ7OgYxYf1+SfG9vySybMrV0hEyKWQ0sg/JQ8kMX8zCLE00+r2f0k2DgHhA7iXR
l7bMhOLzMGfZqSeXGZOpSNjRdNBLo1J0feMq2cLn19WB/3ItKKk4aURnSk5TurkA
z88DuKkN5XBDmAuuYsU172T0aGItv74gzFiOzx/WrqYuc+WP/rdXviZWgvDMaYZ4
+uIEhU5S9K1RxQmp4aFN5t+tbcI91P9KgOBRllZ5pHDJC+SiRzk=
=GSWz
-END PGP SIGNATURE End Message ---

Bug#915334: marked as done (icon FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 21:45:51 +
with message-id 
and subject line Bug#915334: fixed in icon 9.4.3-7
has caused the Debian Bug report #915334,
regarding icon FTBFS with glibc 2.28
to be marked as done.

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

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


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

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

...
gcc -Wall -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC -c fpoll.c
fpoll.c: In function 'fpoll':
fpoll.c:66:9: error: 'FILE' {aka 'struct _IO_FILE'} has no member named '__bufp'
if (f->__bufp < f->__get_limit)
 ^~
fpoll.c:66:21: error: 'FILE' {aka 'struct _IO_FILE'} has no member named 
'__get_limit'
if (f->__bufp < f->__get_limit)
 ^~
make[4]: *** [Makefile:15: fpoll.o] Error 1
--- End Message ---
--- Begin Message ---
Source: icon
Source-Version: 9.4.3-7

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

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

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated icon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 11 Dec 2018 22:14:40 +0100
Source: icon
Binary: icont iconx icon-ipl
Architecture: source
Version: 9.4.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 icon-ipl   - Libraries for Icon, a high-level programming language
 icont  - Interpreter for Icon, a high-level programming language
 iconx  - Executor for Icon, a high-level programming language
Closes: 915334
Changes:
 icon (9.4.3-7) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with glibc 2.28. Closes: #915334.
Checksums-Sha1:
 0dfd05d304a6fd57667d6adea85d6fe76943e2fe 1392 icon_9.4.3-7.dsc
 e0b9d4e0ed7db6769d210d866882eab4f6036c09 8696 icon_9.4.3-7.debian.tar.xz
 45710f49cdead4c8d0136c419fc7e736034d45b3 4293 icon_9.4.3-7_source.buildinfo
Checksums-Sha256:
 f5507a33c1f78188efe72deb38a27aa59042cdc6f294ddab8251d675ae4f12db 1392 
icon_9.4.3-7.dsc
 61bbf281dbf4fa1b358f91da0b68b35ccfdbacabdc95c3ce0911c109eca301ed 8696 
icon_9.4.3-7.debian.tar.xz
 29a26a35110c8b945ec380c869bccee37569c1d36232eaddeb2710c2292f391d 4293 
icon_9.4.3-7_source.buildinfo
Files:
 6c96d94392d311004df8812667763c25 1392 devel optional icon_9.4.3-7.dsc
 5b36202b12bf9d39444c19397359c5a5 8696 devel optional icon_9.4.3-7.debian.tar.xz
 6c2de8345e8ae63d1b83b5e7ff5041dc 4293 devel optional 
icon_9.4.3-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlwQKRwACgkQQc5/C58b
izLwmAf9F27+XADbOvC7wTLQUkchVE165OYTuxCqXqs5+sqTviHhbsHtfxFIXvcS
eEMgFxbk8GkhKnsTXPhFheE31DWQYIz0UmVlNUSf2Vf3H8VUFjUTk7pLvMpAq0Wc
v9k6V/U6axLYJYBv+flcjfJpwWjwBoEZL1HBXHLN/d4qYXRFk3NrDkyU1c7FvZ3Y
nG1/um8G5UwEGAFMKsSjQVhQ+LfeqA1tk26yrnYUEjjJG4gy2qU2G9qPT8jvhF35
qP5a5KXcoMXFkFY31/JHvRRdsTfAr3iQZHy6t+8wRJWy1flbhZjeSjh/UiLX2IBD
/qahn7M7AH//BhL9VCHaKCRO9rQ58A==
=qIMj
-END PGP SIGNATURE End Message ---

Bug#915334: Upstream icon 3.5.1 seems to have this fixed

[Santiago Vila]

Étienne Mollier  wrote:

> On Mon, 10 Dec 2018 19:02:28 +0100 =?UTF-8?Q?=c3=89tienne_Mollier?= 
>  wrote:
> > Please disregard this patch, it seems the proper change has been
> > brought upstream, in icon version 3.5.1, to take in account the
> > necessary change for GlibC 2.28:
> > 
> > http://www2.cs.arizona.edu/icon/current/
> 
> I'm wrong, it will be part of the next version probably, but not
> icon 3.5.1.  The patch may help finally.

Thanks a lot for testing the patch.

I've just made a QA upload to fix this.

Processed: fixed in pdftk/2.02-5

[Debian Bug Tracking System]

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

> fixed 892539 pdftk/2.02-5
Bug #892539 [src:pdftk] pdftk: Depends on GCJ which is going away
Marked as fixed in versions pdftk/2.02-5.
> fixed 901761 pdftk/2.02-5
Bug #901761 [pdftk] Not installable at amd64 because of libgcj17 dependency
Marked as fixed in versions pdftk/2.02-5.
> fixed 906011 pdftk/2.02-5
Bug #906011 [pdftk] pdftk does not properly attribute iText, may violate GPL
Marked as fixed in versions pdftk/2.02-5.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 20:45:03 +
with message-id 
and subject line Bug#899874: fixed in xfce4-mpc-plugin 0.5.1-1
has caused the Debian Bug report #899874,
regarding xfce4-mpc-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of xfce4-mpc-plugin,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-mpc-plugin
Source-Version: 0.5.1-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Dec 2018 21:35:51 +0100
Source: xfce4-mpc-plugin
Binary: xfce4-mpc-plugin
Architecture: source
Version: 0.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-mpc-plugin - Xfce panel plugin which serves as client for MPD music 
player
Closes: 899874
Changes:
 xfce4-mpc-plugin (0.5.1-1) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899874
   * d/gbp.conf added, following DEP-14
   * run wrap-and-sort
   * d/watch: use HTTPS protocol
   * New upstream version 0.5.1
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.2.1
   * d/control: use HTTPS protocol for Homepage
   * update debhelper compat to 10
Checksums-Sha1:
 7aa780039af4dc6bba0348192ed2708fa57058ff 1805 xfce4-mpc-plugin_0.5.1-1.dsc
 35260beb986599423d4bbbf00dbfe37144c7efeb 290830 
xfce4-mpc-plugin_0.5.1.orig.tar.bz2
 cf0be35ef407fcf259c4b0998ced650805b1b512 3692 
xfce4-mpc-plugin_0.5.1-1.debian.tar.xz
 

Processed: found 915666 in 4.19~rc2-1~exp1

[Debian Bug Tracking System]

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

> found 915666 4.19~rc2-1~exp1
Bug #915666 [src:linux] linux: data corruption with blk-mq
Marked as found in versions linux/4.19~rc2-1~exp1.
> thanks
Stopping processing here.

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

Bug#910577: gdb-multiarch: libbabeltrace1 dependency not tight enough

[Michael Jeanson]

On 2018-12-11 2:54 p.m., Adrian Bunk wrote:
> Most important is to fix the root cause:
> 
> $ cat /var/lib/dpkg/info/libbabeltrace1\:amd64.shlibs 
> libbabeltrace-ctf-metadata 1 libbabeltrace1
> libbabeltrace-ctf-text 1 libbabeltrace1
> libbabeltrace-ctf 1 libbabeltrace1
> ...
> $ 
> 
> Reverse dependencies could then be fixed for buster by binNMU.

Ok, so if I understand correctly.

Either, "libbabeltrace-ctf1" should be added to the dependencies of the
3 ctf shared objects in the shlibs file. That way packages that link
with any of theses libs will have an explicit dependency on
"libbabeltrace-ctf1", which will work with both old and new babeltrace
packages.

Or the dependency on "libbabeltrace1" should be versioned to explicitly
pull a package that includes the ctf sub-library.

Do you have an opinion on which of these solutions is preferable.

Thanks,

Michael

Bug#915326: ksh FTBFS with glibc 2.28

[Juhani Numminen]

Control: tags -1 patch

On Sun, 02 Dec 2018 22:01:31 +0200 Adrian Bunk  wrote:
> Source: ksh
> Version: 93u+20120801-3.3
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ksh.html
> 
> ...
> /build/1st/ksh-93u+20120801/src/lib/libast/string/fmtdev.c: In function 
> 'fmtdev':
> /build/1st/ksh-93u+20120801/src/lib/libast/string/fmtdev.c:44:16: error: 
> expected expression before ';' token
>   ma = major(mm);
> ^
> /build/1st/ksh-93u+20120801/src/lib/libast/string/fmtdev.c:45:16: error: 
> expected expression before ';' token
>   mi = minor(mm);
> ^
> mamake [lib/libast]: *** exit code 1 making fmtdev.o

Hi,

I've attached a patch that gets rid of the FTBFS.
I did not test the resulting built package.

This fix is from upstream,
https://github.com/att/ast/commit/0d9d80e91c3b1bdb7ab037a25dbe8e01f81b18a6

--
Juhani
Description: Include  for major/minor on glibc
Origin: https://github.com/att/ast/commit/0d9d80e91c3b1bdb7ab037a25dbe8e01f81b18a6
Bug-Debian: https://bugs.debian.org/915326
Last-Update: 2018-12-11

--- a/src/lib/libast/string/fmtdev.c
+++ b/src/lib/libast/string/fmtdev.c
@@ -30,6 +30,7 @@
 #include 
 #include 
 #include 
+#include 
 
 char*
 fmtdev(struct stat* st)

Processed: Re: Bug#915326: ksh FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #915326 [src:ksh] ksh FTBFS with glibc 2.28
Added tag(s) patch.

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

Bug#910577: gdb-multiarch: libbabeltrace1 dependency not tight enough

[Adrian Bunk]

On Tue, Dec 11, 2018 at 02:47:01PM -0500, Michael Jeanson wrote:
> On 2018-11-26 3:51 p.m., Adrian Bunk wrote:
> > Control: reassign -1 libbabeltrace1 1.5.3-2
> > Control: severity -1 serious
> > Control: affects -1 gdb-multiarch
> > 
> > On Mon, Oct 08, 2018 at 11:35:10AM +0200, Matthias Urlichs wrote:
> >> Package: gdb-multiarch
> >> Version: 8.1-4
> >> Severity: important
> >>
> >> gdb-multiarch requires libbabeltrace-ctf1.
> >>
> >>   --\ Versions of libbabeltrace-ctf1 (3)   
> >>  
> >> p1.5.1-1
> >> i1.5.6-1
> >> i A  libbabeltrace1 1.5.6-1
> >>
> >> Apparently the build process picks up the fact that libbabeltrace-1.5.6-1
> >> contains the -ctf sub-library, but then doesn't depend on >=1.5.6.
> >> Thus 1.5.1 ends up being installed, which doesn't contain the plugin.
> >> ...
> > 
> > Reassigning to libbabeltrace1 where this bug should be fixed.
> > 
> > cu
> > Adrian
> > 
> 
> Hi,
> 
> I'm quite unsure how to fix this properly. I understand the problem but
> every solution I come up with involves modifying already released
> packages. I'm open to any suggestion.

Most important is to fix the root cause:

$ cat /var/lib/dpkg/info/libbabeltrace1\:amd64.shlibs 
libbabeltrace-ctf-metadata 1 libbabeltrace1
libbabeltrace-ctf-text 1 libbabeltrace1
libbabeltrace-ctf 1 libbabeltrace1
...
$ 

Reverse dependencies could then be fixed for buster by binNMU.

> Michael

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#910577: gdb-multiarch: libbabeltrace1 dependency not tight enough

[Michael Jeanson]

On 2018-11-26 3:51 p.m., Adrian Bunk wrote:
> Control: reassign -1 libbabeltrace1 1.5.3-2
> Control: severity -1 serious
> Control: affects -1 gdb-multiarch
> 
> On Mon, Oct 08, 2018 at 11:35:10AM +0200, Matthias Urlichs wrote:
>> Package: gdb-multiarch
>> Version: 8.1-4
>> Severity: important
>>
>> gdb-multiarch requires libbabeltrace-ctf1.
>>
>>   --\ Versions of libbabeltrace-ctf1 (3) 
>>
>> p1.5.1-1
>> i1.5.6-1
>> i A  libbabeltrace1 1.5.6-1
>>
>> Apparently the build process picks up the fact that libbabeltrace-1.5.6-1
>> contains the -ctf sub-library, but then doesn't depend on >=1.5.6.
>> Thus 1.5.1 ends up being installed, which doesn't contain the plugin.
>> ...
> 
> Reassigning to libbabeltrace1 where this bug should be fixed.
> 
> cu
> Adrian
> 

Hi,

I'm quite unsure how to fix this properly. I understand the problem but
every solution I come up with involves modifying already released
packages. I'm open to any suggestion.

Michael

Processed: Re: Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #916225 [python3-docutils] python3-docutils doesn't install on Sid 
armel/armhf/mips/mipsel
Added tag(s) moreinfo.

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

Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel

[Simon McVittie]

Control: tags -1 + moreinfo

On Wed, 12 Dec 2018 at 00:45:34 +0800, You-Sheng Yang wrote:
> Somehow dash failed to expand /usr/share/docutils/scripts/python3/*, so
> that exec variable is simply '/usr/share/docutils/scripts/python3/*',
> which is later expanded as extra dozens of update-alternatives'   
> arguments. To be more detailed, at the time executed, dash path   
> expansion still worked as it's able to expand /usr/share/* and
> /usr/share/docutils*, but it failed to expand /usr/share/docutils/* and
> any other pattern with a /usr/share/docutils/ prefix. Files has been
> installed correctly and accessible, but dash simply unable to expand
> such globs.

The obvious question is: why don't basic operations like glob() work
on the system in question?

Is there something unusual on the system where these expansions failed,
like a non-standard filesystem or kernel, or weird permissions
(directories not 0755 or files not 0755 or 0644) anywhere under
/usr/share/docutils?

You mentioned Docker containers. What is the host system and how are
these Docker containers configured? If /usr is an overlayfs or similar,
failing to evaluate a glob might be a bug in the overlay implementation?

(Since 32-bit ARM and MIPS are not exactly fast machines, I would
suggest building your kernels with dpkg-buildpackage -B and using an
x86_64 machine to build documentation, which would maybe sidestep this
by not needing docutils at all.)

> Replace that path glob with a `find ... -type f` fixes the problem.

Sorry, I don't think python3-docutils can be expected to swap a path
expansion for a subprocess that ought to be equivalent to work around
whatever is going on with these systems - and definitely not without
understanding what it is that's going wrong and why.

smcv

Bug#916234: depending software build failure (arm64, armel, mips)

[Anton Gladky]

Hello,

#915934 can be related. Please forward to GCC.

Anton
Am Di., 11. Dez. 2018 um 19:54 Uhr schrieb Filippo Rusconi :
>
> Package: libeigen3-dev
> Version: 3.3.5-2
> Severity: serious
>
>
> Greetings,
>
> when building libpwiz on the arm64, armel, mips architectures, the build fails
> with the following error:
>
> In file included from /usr/include/eigen3/Eigen/SparseCore:50,
>  from /usr/include/eigen3/Eigen/Sparse:26,
>  from /usr/include/eigen3/Eigen/Eigen:2,
>  from pwiz/analysis/demux/DemuxTypes.hpp:24,
>  from pwiz/analysis/demux/DemuxDebugWriter.hpp:23,
>  from pwiz/analysis/demux/DemuxDebugWriter.cpp:20:
> /usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h: In member function 
> 'Eigen::internal::sparse_matrix_block_impl BlockCols>::BlockType& 
> Eigen::internal::sparse_matrix_block_impl BlockCols>::operator=(const BlockType&)':
> /usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h:216:33: error: 
> expected primary-expression before '>' token
>return operator=(other);
>  ^
>
> Please, see
>
> https://buildd.debian.org/status/fetch.php?pkg=libpwiz=arm64=3.0.18342-1=1544522661=log
> https://buildd.debian.org/status/fetch.php?pkg=libpwiz=armel=3.0.18342-1=1544523773=log
> https://buildd.debian.org/status/fetch.php?pkg=libpwiz=mips=3.0.18342-1=1544524240=log
>
> I am not positively sure that this package is guilty, but I cannot see another
> bug reporting route at the moment.
>
> Sincerely,
> Filippo
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.18.0-2-amd64 (SMP w/8 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)
> LSM: AppArmor: enabled
>
> Versions of packages libeigen3-dev depends on:
> ii  pkg-config  0.29-4+b1
>
> libeigen3-dev recommends no packages.
>
> Versions of packages libeigen3-dev suggests:
> pn  libeigen3-doc   
> pn  libmpfrc++-dev  
>
> -- no debconf information
>
> --
>
> ⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
> ⣾⠁⢠⠒⠀⣿⡁   Scientist at CNRS
> ⢿⡄⠘⠷⠚⠋⠀   Debian Developer
> ⠈⠳⣄  http://msxpertsuite.org
>   http://www.debian.org
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: Re: Bug#916234: depending software build failure (arm64, armel, mips)

[Debian Bug Tracking System]

Processing control commands:

> reassign 916234 gcc-8
Bug #916234 [libeigen3-dev] depending software build failure (arm64, armel, 
mips)
Bug reassigned from package 'libeigen3-dev' to 'gcc-8'.
No longer marked as found in versions eigen3/3.3.5-2.
Ignoring request to alter fixed versions of bug #916234 to the same values 
previously set
> forcemerge 915934 916234
Bug #915934 {Done: Matthias Klose } [gcc-8] gcc fails to 
compile Eigen code
Bug #915980 {Done: Matthias Klose } [gcc-8] gudhi: FTBFS with 
"expected primary-expression before '>' token"
Bug #916234 [gcc-8] depending software build failure (arm64, armel, mips)
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87531'.
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 916234 affects 
src:digikam,src:movit,src:r-cran-ranger,src:lammps,libeigen3-dev,src:step,src:dune-pdelab,src:odb-api,src:gudhi,src:higan,src:dolfin,src:openms
Marked as fixed in versions gcc-8/8.2.0-12.
Marked as found in versions gcc-8/8.2.0-11.
Added tag(s) ftbfs.
Bug #915980 {Done: Matthias Klose } [gcc-8] gudhi: FTBFS with 
"expected primary-expression before '>' token"
Removed indication that 915980 affects src:odb-api, src:openms, libeigen3-dev, 
src:dune-pdelab, src:lammps, src:gudhi, src:digikam, src:r-cran-ranger, 
src:step, src:higan, src:movit, and src:dolfin
Added indication that 915980 affects 
src:digikam,src:movit,src:r-cran-ranger,src:lammps,libeigen3-dev,src:step,src:dune-pdelab,src:odb-api,src:gudhi,src:higan,src:dolfin,src:openms
Removed indication that 915934 affects src:digikam, src:r-cran-ranger, 
src:step, src:higan, src:dolfin, src:movit, src:openms, src:odb-api, 
libeigen3-dev, src:lammps, src:dune-pdelab, and src:gudhi
Added indication that 915934 affects 
src:digikam,src:movit,src:r-cran-ranger,src:lammps,libeigen3-dev,src:step,src:dune-pdelab,src:odb-api,src:gudhi,src:higan,src:dolfin,src:openms
Merged 915934 915980 916234
> affects 915934 src:libpwiz
Bug #915934 {Done: Matthias Klose } [gcc-8] gcc fails to 
compile Eigen code
Bug #915980 {Done: Matthias Klose } [gcc-8] gudhi: FTBFS with 
"expected primary-expression before '>' token"
Bug #916234 {Done: Matthias Klose } [gcc-8] depending software 
build failure (arm64, armel, mips)
Added indication that 915934 affects src:libpwiz
Added indication that 915980 affects src:libpwiz
Added indication that 916234 affects src:libpwiz

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

Bug#882944: marked as done (php-monolog FTBFS with phpunit 6.4.4-2)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 19:20:07 +
with message-id 
and subject line Bug#882944: fixed in php-monolog 2.0.0~beta1-1
has caused the Debian Bug report #882944,
regarding php-monolog FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


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

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-monolog-1.23.0'
phpunit --bootstrap autoload.php --include-path src
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-monolog-1.23.0/tests/Monolog/ErrorHandlerTest.php on line 16
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-monolog
Source-Version: 2.0.0~beta1-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-monolog package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 17:31:42 -1000
Source: php-monolog
Binary: php-monolog
Architecture: source
Version: 2.0.0~beta1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 php-monolog - send logs to various destination and web services
Closes: 882944
Changes:
 php-monolog (2.0.0~beta1-1) experimental; urgency=medium
 .
   * Upload beta to experimental
   * Use debhelper-compat 11
   * Drop versioned dependencies satisfied in stable
   * Drop get-orig-source target
   * Use https in Format
   * Move Vcs-* to salsa.d.o
   * Use Standards-Version 4.2.1
   * Make preview handling more generic
   * Update copyright (years)
   * Install upgrade instructions
   * Drop upstream documentation not provided anymore
   * Drop tests removed upstream (Closes: #882944)
Checksums-Sha1:
 f1416385bd16c06c2828d57066d07a05135106c7 1685 php-monolog_2.0.0~beta1-1.dsc
 1919d148b104d7ce78f4399149eaa5eb0a160dd7 86541 
php-monolog_2.0.0~beta1.orig.tar.gz
 9c195132d7fa1258306c58b46a32326f54aa2788 5068 
php-monolog_2.0.0~beta1-1.debian.tar.xz
 620b76cb945616e1d513c24e582891f9f658bee9 5662 
php-monolog_2.0.0~beta1-1_amd64.buildinfo
Checksums-Sha256:
 ca306eac2ac33e7466bd6b4d4ff27cff0eec44042b588183ec47b437d09ded3c 1685 
php-monolog_2.0.0~beta1-1.dsc
 860772b43d8497b31d43fbf7f5a96b5abfd8dd0a9ccc4db3e7a2f51ef8b8ddb6 86541 
php-monolog_2.0.0~beta1.orig.tar.gz
 afdf119574a52af906a0d05abff36006f050b58692bcadd71b4dd8fc32c7f373 5068 
php-monolog_2.0.0~beta1-1.debian.tar.xz
 dac5a37bc4b923fe88438ecbd02864ca18714579a2d2329a76db8e6955b1a32e 5662 
php-monolog_2.0.0~beta1-1_amd64.buildinfo
Files:
 bc1132352945d0489abb8aeb25720777 1685 php optional 
php-monolog_2.0.0~beta1-1.dsc
 dfd5442d48de1e430cab650efa3716d9 86541 php optional 
php-monolog_2.0.0~beta1.orig.tar.gz
 47e666d58d2ca6d03eb4b3cd6e9f45c2 5068 php optional 
php-monolog_2.0.0~beta1-1.debian.tar.xz
 4cd7bceedec1cd65f57987d2b38a5c96 5662 php optional 
php-monolog_2.0.0~beta1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAlwPcjQSHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08OvcH/0DBp+1bmkvSICrwEekDzViyb/ds0lIA
RQrt+V4BxXaM6TnPWvUJXh8gl70FCkxK6+yCFPOJRkwmARvxVTNiaGSA8x+b/Xmb
AlYK0l3p97OUFkK7oM1jKYQEA2U3BYHohp+C/xdvcS4QeCyUFf1sNFbsJSOCK6aP
ZHTeMMqUMS1b6TZX17982MkU+9Kk1Trg45Te7zlZJapPFwPwS41mBanXhAzqjpMS
2zVTER9MsJyFGbUYLG9bEFmoneJv/Orj0Abyx6Of/eHUcbgyvbIhMA+z6XZ+TK3K
QHn6qcZ063bRE0R9iaFETVtTeoPMf5OtcadPuCai5BMwjJ8w7fuJMTw=
=cQgB
-END PGP SIGNATURE End Message ---

Bug#916234: depending software build failure (arm64, armel, mips)

[Juhani Numminen]

Control: reassign 916234 gcc-8
Control: forcemerge 915934 916234
Control: affects 915934 src:libpwiz

Hello,

On Tue, 11 Dec 2018 19:49:59 +0100 Filippo Rusconi  wrote:

> Greetings, 
> 
> when building libpwiz on the arm64, armel, mips architectures, the build fails
> with the following error:
[...]

> 
> I am not positively sure that this package is guilty, but I cannot see another
> bug reporting route at the moment.

The error message is the same as with #915934, reassigning.

--
Juhani

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Andreas Metzler]

On 2018-12-11 "Torrance, Douglas"  wrote:
> On 12/10/2018 08:54 PM, Doug Torrance wrote:
[...]
> > Indeed.  This (and a couple other commits) hadn't been included in an 
> > official release yet.  I just fixed this, and version 0.9.11 is now 
> > available [1].  I'll prepare a new Debian package soon.

> The new package is ready and pushed to git [1]. 

Great, thanks.

> Andreas, are you able to review and sponsor?

Might take a little bit of time - weekend.

cu Andreas


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

Bug#916234: depending software build failure (arm64, armel, mips)

[Filippo Rusconi]

Package: libeigen3-dev
Version: 3.3.5-2
Severity: serious


Greetings, 


when building libpwiz on the arm64, armel, mips architectures, the build fails
with the following error:

In file included from /usr/include/eigen3/Eigen/SparseCore:50,
from /usr/include/eigen3/Eigen/Sparse:26,
from /usr/include/eigen3/Eigen/Eigen:2,
from pwiz/analysis/demux/DemuxTypes.hpp:24,
from pwiz/analysis/demux/DemuxDebugWriter.hpp:23,
from pwiz/analysis/demux/DemuxDebugWriter.cpp:20:
/usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h: In member function 
'Eigen::internal::sparse_matrix_block_impl::BlockType& Eigen::internal::sparse_matrix_block_impl::operator=(const BlockType&)':
/usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h:216:33: error: expected 
primary-expression before '>' token
  return operator=(other);
^

Please, see 


https://buildd.debian.org/status/fetch.php?pkg=libpwiz=arm64=3.0.18342-1=1544522661=log
https://buildd.debian.org/status/fetch.php?pkg=libpwiz=armel=3.0.18342-1=1544523773=log
https://buildd.debian.org/status/fetch.php?pkg=libpwiz=mips=3.0.18342-1=1544524240=log

I am not positively sure that this package is guilty, but I cannot see another
bug reporting route at the moment.

Sincerely,
Filippo

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 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)
LSM: AppArmor: enabled

Versions of packages libeigen3-dev depends on:
ii  pkg-config  0.29-4+b1

libeigen3-dev recommends no packages.

Versions of packages libeigen3-dev suggests:
pn  libeigen3-doc   
pn  libmpfrc++-dev  

-- no debconf information

--

⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Scientist at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄  http://msxpertsuite.org
 http://www.debian.org

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

[Helmut Grohne]

Source: osspd
Version: 1.3.2-9
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

While trying to cross build osspd for mips, I ran into a failure that I
could reproduce natively on minkus.d.o, but not on amd64. I suspect this
is related to glibc/2.28. A build ends with:

| gcc -Wall -pthread -g -O2 -fdebug-prefix-map=/home/helmutg/osspd-1.3.2=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse 
-DSLAVE_DEFAULT_PATH=\"/usr/lib/osspd\" -o osspd osspd.c -lfuse -pthread -L. 
-lossp -pthread -Wl,-z,relro
| osspd.c:41:2: warning: #warning mmap support disabled for now [-Wcpp]
|  #warning mmap support disabled for now
|   ^~~
| In file included from /usr/include/mips-linux-gnu/sys/soundcard.h:1,
|  from osspd.c:29:
| osspd.c: In function 'mixer_do_ioctl':
| osspd.c:769:15: error: 'IOC_IN' undeclared (first use in this function); did 
you mean 'SIOC_IN'?
|   if (!(cmd & (SIOC_IN | SIOC_OUT)))
|^~~
| osspd.c:769:15: note: each undeclared identifier is reported only once for 
each function it appears in
| osspd.c:769:25: error: 'IOC_OUT' undeclared (first use in this function); did 
you mean 'SIOC_OUT'?
|   if (!(cmd & (SIOC_IN | SIOC_OUT)))
|  ^~~~
| osspd.c: In function 'notify_poller':
| osspd.c:1842:1: warning: no return statement in function returning non-void 
[-Wreturn-type]
|  }
|  ^
| osspd.c: In function 'ossp_daemonize':
| osspd.c:1923:3: warning: ignoring return value of 'chdir', declared with 
attribute warn_unused_result [-Wunused-result]
|chdir("/");
|^~
| At top level:
| osspd.c:1978:39: warning: 'adsp_ops' defined but not used 
[-Wunused-const-variable=]
|  static const struct cuse_lowlevel_ops adsp_ops = {
|^~~~
| make[2]: *** [Makefile:56: osspd] Error 1
| make[2]: Leaving directory '/home/helmutg/osspd-1.3.2'
| dh_auto_build: make V=1 -j1 SLAVESDIR=/usr/lib/osspd 
UDEVDIR=/lib/udev/rules.d returned exit code 2
| make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/home/helmutg/osspd-1.3.2'
| make: *** [debian/rules:7: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#916225: List folders dash cannot expand under /usr/share

[vic...@gmail.com]

for d in $(ls -1 /usr/share); do (/bin/sh -c "ls /usr/share/$d/*"
&>/dev/null) || echo $d; done

This gives a list of folders that `ls /usr/share//*` fails
under dash. So /usr/share/docutils is just one of them.

Bug#916225: Additional info

[vic...@gmail.com]

-- System Information (Debian Sid armel running inside docker container):
Debian Release: buster/sid
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: armel (armv7l)

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages python3-docutils depends on:
ii  docutils-common  0.14+dfsg-3
ii  python3  3.7.1-2
ii  python3-roman2.0.0-3

Versions of packages python3-docutils recommends:
pn  libpaper-utils
pn  python3-pil   
pn  python3-pygments  

Versions of packages python3-docutils suggests:
pn  docutils-doc
pn  fonts-linuxlibertine | ttf-linux-libertine  
pn  texlive-lang-french 
pn  texlive-latex-base  
pn  texlive-latex-recommended   

Bug#916225: python3-docutils doesn't install on Sid armel/armhf/mips/mipsel

[You-Sheng Yang]

Package: python3-docutils
Version: 0.14+dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

While trying to install build-deps for linux kernel package,
python3-docutils failed to install on Sid armel/armhf/mips/mipsel and
passed on other official Sid architectures. The postinst script failed
with following error messages:

Setting up python3-docutils (0.14+dfsg-3) ...
update-alternatives: priority must be an integer
Use 'update-alternatives --help' for program usage information.
dpkg: error processing package python3-docutils (--configure):
 installed python3-docutils package post-installation script
 subprocess returned error exit status 2

With some more inspection into the postinst script, the for-loop inside
is to be blamed:

for exe in /usr/share/docutils/scripts/python3/*
do
update-alternatives --install /usr/bin/${exe##*/} ${exe##*/}
$exe 20
done

Somehow dash failed to expand /usr/share/docutils/scripts/python3/*, so
that exec variable is simply '/usr/share/docutils/scripts/python3/*',
which is later expanded as extra dozens of update-alternatives'   
arguments. To be more detailed, at the time executed, dash path   
expansion still worked as it's able to expand /usr/share/* and
/usr/share/docutils*, but it failed to expand /usr/share/docutils/* and
any other pattern with a /usr/share/docutils/ prefix. Files has been
installed correctly and accessible, but dash simply unable to expand
such globs.

Replace that path glob with a `find ... -type f` fixes the problem.

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

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

Versions of packages python3-docutils depends on:
ii  docutils-common  0.14+dfsg-3
ii  python3  3.7.1-2
ii  python3-roman2.0.0-3

Versions of packages python3-docutils recommends:
ii  libpaper-utils1.1.24+nmu5
ii  python3-pil   5.3.0-1
ii  python3-pygments  2.2.0+dfsg-2

Versions of packages python3-docutils suggests:
pn  docutils-doc   
ii  fonts-linuxlibertine   5.3.0-4
pn  texlive-lang-french
ii  texlive-latex-base 2018.20181116-1
pn  texlive-latex-recommended  

-- no debconf information

Bug#916223: moonshot-gss-eap: FTBFS against xmltooling 3

[Andreas Beckmann]

Package: moonshot-gss-eap
Version: 1.0.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

moonshot-gss-eap/experimental FTBFS against the new xmltooling and
friends stack:

util_saml.cpp:46:10: fatal error: xmltooling/util/DateTime.h: No such file or 
directory
 #include 

It's probably time to upload the package to sid once this got fixed.


Andreas


moonshot-gss-eap_1.0.1-3.log.gz
Description: application/gzip

Bug#915777: marked as done (mumble: B-D libg15daemon-client-dev is no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 16:34:17 +
with message-id 
and subject line Bug#915777: fixed in mumble 1.2.19-3
has caused the Debian Bug report #915777,
regarding mumble: B-D libg15daemon-client-dev is no longer available
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.)


-- 
915777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mumble
Version: 1.2.19-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.3.0~2868~g44b9004+dfsg-1

Hi,

the build dependency libg15daemon-client-dev is no longer available in
sid.


Andreas
--- End Message ---
--- Begin Message ---
Source: mumble
Source-Version: 1.2.19-3

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

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

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mumble 
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, 11 Dec 2018 15:58:57 +
Source: mumble
Binary: mumble mumble-server
Architecture: source
Version: 1.2.19-3
Distribution: unstable
Urgency: medium
Maintainer: Christopher Knadle 
Changed-By: Christopher Knadle 
Description:
 mumble - Low latency encrypted VoIP client
 mumble-server - Low latency encrypted VoIP server
Closes: 912779 915777
Changes:
 mumble (1.2.19-3) unstable; urgency=medium
 .
   * debian/control:
 - Add Vcs-Browser and Vcs-Git links pointing to repository on Salsa
 - Remove Suggests: mumble-django package from mumble-server (deprecated)
 - Remove Build-Depends: libg15daemon-client-dev due to g15daemon package
   removal (see #914888) (Closes: #915777)
   Thanks to Andreas Beckmann  for reporting the bug.
 - Upgrade Standards-Version to 4.2.1
   Changes:
 - Update debian/rules to enable DH_VERBOSE=1 to increase build
   verbosity as requested in Debian Policy § 4.9
   * debian/patches:
 - Add 54-fix-boost-ftbfs.diff to fix FTBFS bug with boost1.67
   (Closes: #912779)
   Thanks to Giovanni Mascellani  for reporting the bug and
   providing a patch.  Thanks to Adrian Bunk  for finding
   and reporting the upstream commit used to fix this.
- Re-enable 07-use-embedded-celt-baseline.diff in series file.  Without the
  patch celt 0.11.0 was built but then not shipped.
   * debian/rules:
 - Enable DH_VERBOSE=1 to increase build verbosity
 - Add CONFIG*=no-g15 to remove G15 keyboard features due to g15daemon
   package removal
   * debian/upstream/metadata:
 - Add metadata file to appease Lintian
Checksums-Sha1:
 55e56c23948f0be64b9b898318cf6402253bad3a 2497 mumble_1.2.19-3.dsc
 8ea9dafad14e6c730da72ae9b4625778e499d94f 3210865 mumble_1.2.19.orig.tar.gz
 83e71e5f52eb622878e7589bb62d535aaa44b054 836 mumble_1.2.19.orig.tar.gz.asc
 46bf27f13a57fe955df5d91574cf53ef9e416dac 42500 mumble_1.2.19-3.debian.tar.xz
 9f26384f3c2c5339dc30b9a6cbb2d49c92c54fc8 5699 mumble_1.2.19-3_source.buildinfo
Checksums-Sha256:
 95a3ff0a6fdc1abc79a74b3d5a7cb116725fee78534b2d6f1e4aa156b1def073 2497 
mumble_1.2.19-3.dsc
 f047fb707ad93948b0bc913ec0a89cd5480d87e840c4ff2519608fc8a2dac0e8 3210865 
mumble_1.2.19.orig.tar.gz
 3529e4235e3d9db0862cb536172bb76f31571daed5458d2319ec0de0251f7942 836 
mumble_1.2.19.orig.tar.gz.asc
 440bf8b57567ae7d4208ba3c722da3b085705080d8251ec0b6ed31090cb587ba 42500 
mumble_1.2.19-3.debian.tar.xz
 dacc147e698656de5c89e72d58717cdd9dff233de1cd8d3d6d18f93f9028a79f 5699 
mumble_1.2.19-3_source.buildinfo
Files:
 9be314e83c56791ce1fa9622d8a1570c 2497 sound optional mumble_1.2.19-3.dsc
 d101068ed27ce119effdb3765a8cf8e4 3210865 sound optional 
mumble_1.2.19.orig.tar.gz
 df2b4766c66edb64561a9b64e3cc62d5 836 sound optional 
mumble_1.2.19.orig.tar.gz.asc
 d710160578a9c826ec831642acd31196 42500 sound optional 
mumble_1.2.19-3.debian.tar.xz
 5b0022958f2a3f1c1f85f65c3f23e91b 5699 sound optional 
mumble_1.2.19-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe1KzyGmRW/4DhtV6ieLKD9m6RHAFAlwP36IACgkQieLKD9m6

Processed: Raising severity of open bugs related to gnustep-make

[Debian Bug Tracking System]

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

> # Raising severity as gnustep-make/2.7.0-4 is in the archive now.
> severity 897586 serious
Bug #897586 [src:sogo] src:sogo: FTBFS with gnustep-make in strict v2 mode: 
specified prefix is not a GNUstep root: '/usr/System'
Severity set to 'serious' from 'important'
> tags 897586 + ftbfs
Bug #897586 [src:sogo] src:sogo: FTBFS with gnustep-make in strict v2 mode: 
specified prefix is not a GNUstep root: '/usr/System'
Added tag(s) ftbfs.
> severity 897623 serious
Bug #897623 [src:fortunate.app] src:fortunate.app: FTBFS with gs_make removed
Severity set to 'serious' from 'important'
> tags 897623 + ftbfs
Bug #897623 [src:fortunate.app] src:fortunate.app: FTBFS with gs_make removed
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 16:32:52 +
with message-id 
and subject line Bug#916175: Removed package(s) from unstable
has caused the Debian Bug report #899774,
regarding xfce4-radio-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of xfce4-radio-plugin,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.5.1-4+rm

Dear submitter,

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

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

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

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

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

Bug#910126: marked as done (atdgen FTBFS: Error: Unbound module Atd_ast)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 16:32:15 +
with message-id 
and subject line Bug#915974: Removed package(s) from unstable
has caused the Debian Bug report #910126,
regarding atdgen FTBFS: Error: Unbound module Atd_ast
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.)


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

atdgen fails to build from source in unstable on amd64. A build log ends
with:

| /usr/bin/make atdgen.cma atdgen.run
| make[4]: Entering directory '/<>/src'
| ocamlfind ocamlc -dtypes -g -c -package "str atd biniou yojson" ag_version.ml
| ocamlfind ocamlc -dtypes -g -c -package "str atd biniou yojson" ag_error.ml
| File "ag_error.ml", line 5, characters 31-52:
| Error: Unbound module Atd_ast
| make[4]: *** [Makefile:150: ag_error.cmi] Error 2
| make[4]: Leaving directory '/<>/src'
| make[3]: *** [Makefile:101: all] Error 2
| make[3]: Leaving directory '/<>/src'
| make[2]: *** [Makefile:13: default] Error 2
| make[2]: Leaving directory '/<>'
| make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:18: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.9.1-2+rm

Dear submitter,

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

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

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

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

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

Bug#916221: node-prismjs: Unable to install due to missing node-clipboard

[Andreas Tille]

Package: node-prismjs
Severity: grave
Justification: renders package unusable

Hi,

$ sudo apt-get install node-prismjs
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 node-prismjs : Depends: node-clipboard (>= 1.7.1) but it is not installable


There is no package node-clipboard available in Debian.

Kind regards

   Andreas.


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

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

Processed: 893723

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + upstream
Bug #893723 [nagvis] nagvis: PHP Fatal error: Redefinition of parameter 
$_unused_flag
Added tag(s) upstream.
> forwarded -1 https://github.com/NagVis/nagvis/issues/79
Bug #893723 [nagvis] nagvis: PHP Fatal error: Redefinition of parameter 
$_unused_flag
Set Bug forwarded-to-address to 'https://github.com/NagVis/nagvis/issues/79'.

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

Bug#893723: 893723

[Sébastien Delafond]

Control: tag -1 + upstream
Control: forwarded -1 https://github.com/NagVis/nagvis/issues/79

This has apparently been closed in "recent releases", although upstream
doesn't mention when that happened exactly. Scouring through git log, it
appears to be in this commit:

  commit da8746985d21b517a66ec8795a672192e4551b49
  Author: Lars Michelsen 
  Date:   Fri Apr 22 13:18:48 2016 +0200

FIX: Fixed some compatibility issues with PHP 7. NagVis should work with it.

This would make 1.9b7 the first release containing the fix.

Cheers,

-- 
Seb

Bug#916211: marked as done (jfsutils FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 16:09:14 +
with message-id 
and subject line Bug#916211: fixed in jfsutils 1.1.15-4
has caused the Debian Bug report #916211,
regarding jfsutils FTBFS with glibc 2.28
to be marked as done.

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

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


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

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

...
devices.c: In function 'ujfs_flush_dev':
devices.c:469:6: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  if (major(buf.st_rdev) != RAMDISK_MAJOR)
  ^
...
gcc -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 
-ffile-prefix-map=/build/1st/jfsutils-1.1.15=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-z,relro -o jfs_fsck fsckbmap.o 
fsckconn.o fsckdire.o fsckdtre.o fsckea.o fsckimap.o fsckino.o fsckmeta.o 
fsckpfs.o dirindex.o fsckwsp.o fsckxtre.o xchkdsk.o fsckruns.o fsck_message.o 
../libfs/libfs.a -luuid 
/usr/bin/ld: ../libfs/libfs.a(devices.o): in function `ujfs_flush_dev':
./libfs/devices.c:469: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:267: jfs_fsck] Error 1
--- End Message ---
--- Begin Message ---
Source: jfsutils
Source-Version: 1.1.15-4

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 11 Dec 2018 14:40:40 +
Source: jfsutils
Binary: jfsutils jfsutils-udeb
Architecture: source
Version: 1.1.15-4
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 jfsutils   - utilities for managing the JFS filesystem
 jfsutils-udeb - stripped-down version of jfsutils, for debian-installer (udeb)
Closes: 916211
Changes:
 jfsutils (1.1.15-4) unstable; urgency=medium
 .
   * Include sys/sysmacros.h for recent glibc (closes: #916211).
   * Update Standards-Version to 4.2.1 .
   * Update debhelper level to 10 .
Checksums-Sha1:
 4398cca870f45b6eb11b5241ee4a7c4c83e38cdd 1803 jfsutils_1.1.15-4.dsc
 426623b0c8eb2d3e53ae6e105b79e5522428011d 6280 jfsutils_1.1.15-4.debian.tar.xz
 af4f18a0c75befe00f86a73f8918de63b1a5ec67 6955 jfsutils_1.1.15-4_amd64.buildinfo
Checksums-Sha256:
 7bedbf03b11de9cf5cfae43cbea91b9b9c684d97c37f37d5c80d19722b8465ab 1803 
jfsutils_1.1.15-4.dsc
 a68eee2ac94caee2a3b9c8cce71eeef15ce1515080c79fb79153b94f3aa29dac 6280 
jfsutils_1.1.15-4.debian.tar.xz
 2dfd184365547cba524d7db1c84d02afde74e15c693b1257f863deb8d08f5e70 6955 
jfsutils_1.1.15-4_amd64.buildinfo
Files:
 39137560251360f9d09b17186a0f0c06 1803 admin optional jfsutils_1.1.15-4.dsc
 02dfbac28524c30c450074d3a063dc6c 6280 admin optional 
jfsutils_1.1.15-4.debian.tar.xz
 f642e83070756f2f5050b9bad3bbb2dc 6955 admin optional 
jfsutils_1.1.15-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlwP17sACgkQ3OMQ54ZM
yL8cSw/+P8gdyMr90ShFR+LOu64pG1nQozjQ8eu3lxDgERGnWZFy56q0wLZmfF/x
8L7Z0SO/qXjm50m2uCtmr/FigYOLzWb/Ro/UEhAPaeGi0AyaTHp3v0hwjUbdnSf6
KvlU1SSg+HfwmkpiPNtJh4N31o56QO8RXi8vOmT+lLLIfJaXrxliBT+J8nWCDqwA
5ax/xLTyFOh2yxI4k5lQAJcO81Ui7S+KzWvMxUUT9MdUBJojNan9pnjjaUsLzO05
t0ntidJhL441EMdP2GzQhNqBV/bUyUM0vrWH1sX3CWSKksL3OECc/bQYzTb0RLmj
6EByuCaz+wAz7Ps+ClF16WAwEDW1W3lAyqYC96wEqDNKF/MCJPTTu4P3dEjbyACw
lKXtpJ68/RCbvGkgKNlkps053gaPDG0aWJFnX7ctNhK2/kS6jTS5yvkvM333+U9H
fZU+rFTZfhtwdU/fIdwdpvR6zyWAzGRZvM/gbn6umlxarNApLNBtxs9Izj1es/4r
k1Rh7upRZM/0m4nLe5UZJ4wHiDIg+vdOE3IttJiA7PGTMnvoAz5ujTg8WJF7tSAE
1S1lvuaPYFRbEX6w+UIiTSQ+Gx+KVXryNZKA6tC19yZYtfzItzzM83En0hBmbiA4
3upPRMR7ZF+I3jLUy+QxKo2+vZWcScYNQE8hKwNxnUmExWHy1gU=
=jHMS
-END PGP SIGNATURE End Message ---

Bug#916219: nixnote2: Non-free icon

[Boyuan Yang]

Package: nixnote2
Version: 2.1.1-1
Severity: serious

Nixnote2 before 2.1.1 (including 2.1.1) is using a CC-BY-ND icon,
which is incompatible with DFSG.

This problem has been fixed by using a GPL-3-licensed icon to replace
the old one in git trunk. We should consider uploading the git trunk
version (or the next upstream release) before Buster freeze.

--
Thanks,
Boyuan Yang

Bug#911324: ITP?

[Cyrille Bollu]

Hi Gregor,

Do you think I should go ahead and create packages for the missing
dependencies?

Shall I send ITP before?

Cyrille

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Torrance, Douglas]

On 12/10/2018 08:54 PM, Doug Torrance wrote:
> On 12/10/18 6:29 AM, Juhani Numminen wrote:
>> Control: tags -1 + fixed-upstream
>>
>> On Sun, 9 Dec 2018 15:43:14 +0100 Andreas Metzler  
>> wrote:
>>> On 2018-12-09 Adrian Bunk  wrote:
 Source: wmhdplop
 Version: 0.9.10-1
>>> [...]
>>>
 devnames.c: In function 'device_id_from_name':
 devnames.c:207:13: warning: implicit declaration of function 'major' 
 [-Wimplicit-function-declaration]
     *pmajor = major(stat_buf.st_rdev);
   ^
>>> [...]
>>>
>>> Seems to miss a
>>> #include 
>>
>> Looks like that was indeed added in the upstream repo.
>> https://repo.or.cz/dockapps.git/commitdiff/7cf2e5406b9bc98054404c4c0145c2db0c0ef1e8
>>  
>>
> 
> Indeed.  This (and a couple other commits) hadn't been included in an 
> official release yet.  I just fixed this, and version 0.9.11 is now 
> available [1].  I'll prepare a new Debian package soon.

The new package is ready and pushed to git [1].  Andreas, are you able 
to review and sponsor?

Thanks!
Doug

[1] https://salsa.debian.org/wmaker-team/wmhdplop

Bug#892859: marked as done (paramiko: CVE-2018-7750: Server implementation does not check for auth before serving later requests)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 15:16:06 +
with message-id 
and subject line Bug#892859: fixed in paramiko 2.4.2-0.1
has caused the Debian Bug report #892859,
regarding paramiko: CVE-2018-7750: Server implementation does not check for 
auth before serving later requests
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.)


-- 
892859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paramiko
Version: 1.15.1-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/paramiko/paramiko/issues/1175

Hi,

the following vulnerability was published for paramiko.

CVE-2018-7750[0]:
| transport.py in the SSH server implementation of Paramiko before
| 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5,
| 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not
| properly check whether authentication is completed before processing
| other requests, as demonstrated by channel-open. A customized SSH
| client can simply skip the authentication step.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-7750
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7750
[1] https://github.com/paramiko/paramiko/issues/1175

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: paramiko
Source-Version: 2.4.2-0.1

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated paramiko 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, 01 Dec 2018 14:30:29 +0100
Source: paramiko
Binary: paramiko-doc python-paramiko python3-paramiko
Architecture: source all
Version: 2.4.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jeremy T. Bouse 
Changed-By: Gaudenz Steinlin 
Description:
 paramiko-doc - Make ssh v2 connections with Python (Documentation)
 python-paramiko - Make ssh v2 connections (Python 2)
 python3-paramiko - Make ssh v2 connections (Python 3)
Closes: 892859 904635
Changes:
 paramiko (2.4.2-0.1) unstable; urgency=medium
 .
   * New upstream version 2.4.2 (Closes: #892859)
   * Fix autopkgtests (switch to pytest) (Closes: #904635)
Checksums-Sha1:
 82081108fd00b101967a9ab5f496acfea88f7fc4 2397 paramiko_2.4.2-0.1.dsc
 7ab1e9aaf0b6eedb2098661d283f4d6f6d9c8963 1207299 paramiko_2.4.2.orig.tar.gz
 856d2eb12d4f326cf7e39c463552abb8ac4e450b 455 paramiko_2.4.2.orig.tar.gz.asc
 081a0df6221497691018b32cd02eb623cb646e1e 7516 paramiko_2.4.2-0.1.debian.tar.xz
 079cfeb44daabb6b2a0f69118ff959c44a56c46c 23196 paramiko-doc_2.4.2-0.1_all.deb
 fcf6669fa93fef0d1071c2293edf169c25a8f17b 8013 
paramiko_2.4.2-0.1_amd64.buildinfo
 94414af3560251b86b96e6d72cb56b2bab5e8214 120068 
python-paramiko_2.4.2-0.1_all.deb
 7e6f99d12ddd101183082bed289d719867df046e 120164 
python3-paramiko_2.4.2-0.1_all.deb
Checksums-Sha256:
 d1f70c364d5ddae1508f47669ad21bfc94dcee7bd756ae99bcfe32abc370f8ff 2397 
paramiko_2.4.2-0.1.dsc
 a8975a7df3560c9f1e2b43dc54ebd40fd00a7017392ca5445ce7df409f900fcb 1207299 
paramiko_2.4.2.orig.tar.gz
 572a99af43a17cbd53bf5a56e1ab1cbeef2ea46a71e04d544282f96d69cd3f31 455 
paramiko_2.4.2.orig.tar.gz.asc
 6d3580171c81829593c5dee45310c6e87d2a5b239f46fe0aa124efbebc6a947f 7516 
paramiko_2.4.2-0.1.debian.tar.xz
 762c7cb1611e60eb34cc7abd59f919dabbb52908130efd4c83a538d1716c1817 23196 
paramiko-doc_2.4.2-0.1_all.deb
 65e616219f71a143e0cb9ff0962588e4f86735b2cedc884cfc0a262e636b727d 8013 
paramiko_2.4.2-0.1_amd64.buildinfo
 a7850329d12f23389b643cae9a0d790dff6541a7108440157a66741947edd70f 120068 
python-paramiko_2.4.2-0.1_all.deb
 dff1b8f7c1614e8833104832b0c257538b720710af6750cf16bde178104e55ad 120164 
python3-paramiko_2.4.2-0.1_all.deb
Files:
 f1c6c18a70e7c581708622c1f15fa037 2397 python optional paramiko_2.4.2-0.1.dsc
 a476ea106177fe22e797428d54811aed 1207299 python optional 

Bug#904635: marked as done (paramiko requires pytest << 3.6, and autopkg tests require pytest)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 15:16:06 +
with message-id 
and subject line Bug#904635: fixed in paramiko 2.4.2-0.1
has caused the Debian Bug report #904635,
regarding paramiko requires pytest << 3.6, and autopkg tests require pytest
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.)


-- 
904635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:paramiko
Version: 2.4.0-1
Severity: serious
Tags: sid buster patch

According to
https://bugzilla.redhat.com/show_bug.cgi?id=1594896
paramiko needs an update for pytest 3.6.

Also the debian autopkg tests need an update to use pytest. patch at
http://launchpadlibrarian.net/380090902/paramiko_2.4.0-1_2.4.0-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: paramiko
Source-Version: 2.4.2-0.1

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated paramiko 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, 01 Dec 2018 14:30:29 +0100
Source: paramiko
Binary: paramiko-doc python-paramiko python3-paramiko
Architecture: source all
Version: 2.4.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jeremy T. Bouse 
Changed-By: Gaudenz Steinlin 
Description:
 paramiko-doc - Make ssh v2 connections with Python (Documentation)
 python-paramiko - Make ssh v2 connections (Python 2)
 python3-paramiko - Make ssh v2 connections (Python 3)
Closes: 892859 904635
Changes:
 paramiko (2.4.2-0.1) unstable; urgency=medium
 .
   * New upstream version 2.4.2 (Closes: #892859)
   * Fix autopkgtests (switch to pytest) (Closes: #904635)
Checksums-Sha1:
 82081108fd00b101967a9ab5f496acfea88f7fc4 2397 paramiko_2.4.2-0.1.dsc
 7ab1e9aaf0b6eedb2098661d283f4d6f6d9c8963 1207299 paramiko_2.4.2.orig.tar.gz
 856d2eb12d4f326cf7e39c463552abb8ac4e450b 455 paramiko_2.4.2.orig.tar.gz.asc
 081a0df6221497691018b32cd02eb623cb646e1e 7516 paramiko_2.4.2-0.1.debian.tar.xz
 079cfeb44daabb6b2a0f69118ff959c44a56c46c 23196 paramiko-doc_2.4.2-0.1_all.deb
 fcf6669fa93fef0d1071c2293edf169c25a8f17b 8013 
paramiko_2.4.2-0.1_amd64.buildinfo
 94414af3560251b86b96e6d72cb56b2bab5e8214 120068 
python-paramiko_2.4.2-0.1_all.deb
 7e6f99d12ddd101183082bed289d719867df046e 120164 
python3-paramiko_2.4.2-0.1_all.deb
Checksums-Sha256:
 d1f70c364d5ddae1508f47669ad21bfc94dcee7bd756ae99bcfe32abc370f8ff 2397 
paramiko_2.4.2-0.1.dsc
 a8975a7df3560c9f1e2b43dc54ebd40fd00a7017392ca5445ce7df409f900fcb 1207299 
paramiko_2.4.2.orig.tar.gz
 572a99af43a17cbd53bf5a56e1ab1cbeef2ea46a71e04d544282f96d69cd3f31 455 
paramiko_2.4.2.orig.tar.gz.asc
 6d3580171c81829593c5dee45310c6e87d2a5b239f46fe0aa124efbebc6a947f 7516 
paramiko_2.4.2-0.1.debian.tar.xz
 762c7cb1611e60eb34cc7abd59f919dabbb52908130efd4c83a538d1716c1817 23196 
paramiko-doc_2.4.2-0.1_all.deb
 65e616219f71a143e0cb9ff0962588e4f86735b2cedc884cfc0a262e636b727d 8013 
paramiko_2.4.2-0.1_amd64.buildinfo
 a7850329d12f23389b643cae9a0d790dff6541a7108440157a66741947edd70f 120068 
python-paramiko_2.4.2-0.1_all.deb
 dff1b8f7c1614e8833104832b0c257538b720710af6750cf16bde178104e55ad 120164 
python3-paramiko_2.4.2-0.1_all.deb
Files:
 f1c6c18a70e7c581708622c1f15fa037 2397 python optional paramiko_2.4.2-0.1.dsc
 a476ea106177fe22e797428d54811aed 1207299 python optional 
paramiko_2.4.2.orig.tar.gz
 95b71d53960359b70511c7eb5cc7f32e 455 python optional 
paramiko_2.4.2.orig.tar.gz.asc
 25e7a17c327741b4724723fdcc24b1ad 7516 python optional 
paramiko_2.4.2-0.1.debian.tar.xz
 6f0f1ae824afc8215e840c3f09eebb99 23196 doc optional 
paramiko-doc_2.4.2-0.1_all.deb
 9eef7ce26f50cd36e9b0a1343068d5c1 8013 python optional 
paramiko_2.4.2-0.1_amd64.buildinfo
 fdc263890ac7f815827e2fdf1f58845c 120068 python optional 
python-paramiko_2.4.2-0.1_all.deb
 f4796e62908ccd3f28c85b2cd52b565e 120164 python optional 
python3-paramiko_2.4.2-0.1_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEXtjbd32AqFIO1HzsOrL5guAQm9UFAlwClQUACgkQOrL5guAQ

Bug#880780: marked as done (pygdchart2 build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 15:16:12 +
with message-id 
and subject line Bug#880780: fixed in pygdchart2 0.beta1-3.8
has caused the Debian Bug report #880780,
regarding pygdchart2 build depends on removed libgd2*-dev provides
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.)


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

The following packages have unmet dependencies:
 builddeps:pygdchart2 : Depends: libgd2-noxpm-dev but it is not installable or
 libgd2-xpm-dev but it is not installable


Please update the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: pygdchart2
Source-Version: 0.beta1-3.8

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated pygdchart2 
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, 11 Dec 2018 12:27:18 -0200
Source: pygdchart2
Binary: python-gdchart2 python-gdchart2-doc
Architecture: source
Version: 0.beta1-3.8
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Joao Eriberto Mota Filho 
Description:
 python-gdchart2 - Python OO interface to GDChart
 python-gdchart2-doc - Python OO interface to GDChart - docs
Closes: 880780
Changes:
 pygdchart2 (0.beta1-3.8) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Run wrap-and-sort.
   * debian/control: changed build dependency 'libgd2-noxpm-dev | 
libgd2-xpm-dev'
 to libgd-dev, avoiding a FTBFS. Thanks to Adrian Bunk .
 (Closes: #880780)
Checksums-Sha1:
 ca3c09c96c1be0f5155b7d0646d63d2592ce0441 1888 pygdchart2_0.beta1-3.8.dsc
 5d57829ef370573b551b1a63abcbe940818cbed9 4812 pygdchart2_0.beta1-3.8.diff.gz
 57a891623faad31e6c0d25299c61846ddba43e4d 7578 
pygdchart2_0.beta1-3.8_source.buildinfo
Checksums-Sha256:
 d5af391a307d98fccfa2b2e6d9cd3e16e64e8ca1d30d89fe0b1dae1a39c6fa40 1888 
pygdchart2_0.beta1-3.8.dsc
 ed5ad1b1f46fb832265fac84d6c9ef70d890011bebc2b51ef630ca4568405a80 4812 
pygdchart2_0.beta1-3.8.diff.gz
 e978dd1eb2c9961d3313c9a5bae0997606aafbbf60fa2e45410609cf90f6dbab 7578 
pygdchart2_0.beta1-3.8_source.buildinfo
Files:
 df8ba45f0a67bb60f1c95a08e40bbf0b 1888 python optional 
pygdchart2_0.beta1-3.8.dsc
 7d9ea6baf2cada08eb77900c3338b0d7 4812 python optional 
pygdchart2_0.beta1-3.8.diff.gz
 2f41bfbc4250bd326f122c31a7d205f2 7578 python optional 
pygdchart2_0.beta1-3.8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlwPy7YACgkQ3mO5xwTr
6e/8ZQ//eG1Xc6c4naINKPxyk1g+fazatPnxP0SciI+tLSo2nkMXqjh14AL/P4OV
jxCXJ4ZXg0jobALOK31OP0ir0EhE03E8QEWtT7sKjGClae5I4Pq2cqv7FQ9wusXv
FH5FPqsBYmUUYTsExHt2Oq8nr1cQ3sQgfi+4Pb4gKjpYPrBptInCK9tm0eX5wWNw
ngWbQ5c3T6ZeQ0nGURBnihudzkrJXOhJrecS3lktYoHCkU0W6+nPHiev6h3EY3GK
b8KAMrBL2gAse0BFt3V/d2P7tB1axVvqKCrEbJRwHvvF9ytnO8NuRwphnCxPCpkU
F6oitwYnsRT83WENmCnQxiBF9G/TJZxYfYLLJHqL7r/At/t/hzcauCtxL6zyW8o/
eRykj4ulkDIr7C+KUxyHXU8lUKF4jowE6F9YuxKZ5LT9JBSSHoMB1qBgpL4PNean
0oIegXuphGT407HZLSa1a6V+NrzZEPOMorICFwPovPVJuyQolUDF6Q8eBouP3pMk
muY0F9j7kvuFNwOtRFmc/66JIuPQlFhhg3cCs/b5UFNBqj++68B6R3SEonmDr4tj
wCzXmrjRY6cXtnuAnW8RY5wDwSeJgd/Gmw2FDSM9AyrNv/7TweAQcWFo2yVRcd+3
jWNtEGuvzaR3Dk0FqWnRLZtz9J6R3Z5ZWzSqJ+aEd1EXxxQJR5E=
=i19/
-END PGP SIGNATURE End Message ---

Bug#912682: usefulness of this package?

[Dominic Hargreaves]

On Tue, Dec 11, 2018 at 10:06:45AM +0100, Cyrille Bollu wrote:
> From its debian/control file:
> 
> >This module is already included as part of Perl's core distribution, so
> this
> > package is only beneficial when newer features or bug fixes are required.
> 
> I don't understand how

The perl package provides the same package via a Provides entry:
libextutils-parsexs-perl (= 3.39). This is newer than the version
in the separate package (against which this bug is filed) so this 
package will never be selected for installation.

This could change if a newer version is uploaded, but until then,
the separate package should not be released.

Dominic.

Bug#916213: libpolyclipping FTBFS on 32bit: symbol differences

[Adrian Bunk]

Source: libpolyclipping
Version: 6.4.2-4
Severity: serious
Tags: ftbfs

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

...
dpkg-gensymbols -plibpolyclipping22 -Idebian/libpolyclipping22.symbols 
-Pdebian/libpolyclipping22 
-edebian/libpolyclipping22/usr/lib/i386-linux-gnu/libpolyclipping.so.22.0.0
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpolyclipping22/DEBIAN/symbols doesn't match 
completely debian/libpolyclipping22.symbols
--- debian/libpolyclipping22.symbols (libpolyclipping22_6.4.2-4_i386)
+++ dpkg-gensymbolsU6Y5df   2018-12-10 22:51:17.966224771 +
@@ -65,7 +65,7 @@
  (c++)"ClipperLib::ClipperBase::DeleteFromAEL(ClipperLib::TEdge*)@Base" 6.4.2
  (c++)"ClipperLib::ClipperBase::DisposeAllOutRecs()@Base" 6.4.2
  (c++)"ClipperLib::ClipperBase::DisposeLocalMinimaList()@Base" 6.4.2
- (c++)"ClipperLib::ClipperBase::DisposeOutRec(unsigned long)@Base" 6.4.2
+#MISSING: 6.4.2-4# (c++)"ClipperLib::ClipperBase::DisposeOutRec(unsigned 
long)@Base" 6.4.2
  (c++)"ClipperLib::ClipperBase::GetBounds()@Base" 6.4.2
  (c++)"ClipperLib::ClipperBase::InsertScanbeam(long long)@Base" 6.4.2
  (c++)"ClipperLib::ClipperBase::LocalMinimaPending()@Base" 6.4.2
@@ -159,16 +159,33 @@
  (c++)"ClipperLib::operator<<(std::basic_ostream 
>&, std::vector > 
const&)@Base" 6.4.2
  (c++)"ClipperLib::operator<<(std::basic_ostream 
>&, std::vector >, 
std::allocator > > > const&)@Base" 6.4.2
  (c++)"VTT for ClipperLib::Clipper@Base" 6.4.2
+ _ZN10ClipperLib11ClipperBase13DisposeOutRecEj@Base 6.4.2-4
+ _ZNSt6vectorIN10ClipperLib11DoublePointESaIS1_EE7reserveEj@Base 6.4.2-4
+ _ZNSt6vectorIN10ClipperLib8IntPointESaIS1_EE17_M_default_appendEj@Base 6.4.2-4
+ 
_ZNSt6vectorIN10ClipperLib8IntPointESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 6.4.2-4
+ _ZNSt6vectorIN10ClipperLib8IntPointESaIS1_EE7reserveEj@Base 6.4.2-4
+ _ZNSt6vectorIPN10ClipperLib4JoinESaIS2_EE17_M_default_appendEj@Base 6.4.2-4
+ _ZNSt6vectorIPN10ClipperLib8PolyNodeESaIS2_EE17_M_default_appendEj@Base 
6.4.2-4
+ _ZNSt6vectorIPN10ClipperLib8PolyNodeESaIS2_EE7reserveEj@Base 6.4.2-4
+ 
_ZNSt6vectorIS_IN10ClipperLib8IntPointESaIS1_EESaIS3_EE17_M_default_appendEj@Base
 6.4.2-4
+ _ZNSt6vectorIS_IN10ClipperLib8IntPointESaIS1_EESaIS3_EE7reserveEj@Base 6.4.2-4
+ 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_iS3_NS0_5__ops15_Iter_comp_iterINS2_12LocMinSortervT_T0_SE_T1_T2_@Base
 6.4.2-4
+ 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPPN10ClipperLib13IntersectNodeESt6vectorIS4_SaIS4_iS4_NS0_5__ops15_Iter_comp_iterIPFbS4_S4_vT_T0_SG_T1_T2_@Base
 6.4.2-4
+ 
_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPxSt6vectorIxSaIxixNS0_5__ops15_Iter_comp_iterISt4lessIxvT_T0_SD_T1_T2_@Base
 6.4.2-4
+ 
_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_iNS0_5__ops15_Iter_comp_iterINS2_12LocMinSortervT_SD_T0_T1_@Base
 6.4.2-4
+ 
_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPPN10ClipperLib13IntersectNodeESt6vectorIS4_SaIS4_iNS0_5__ops15_Iter_comp_iterIPFbS4_S4_vT_SF_T0_T1_@Base
 6.4.2-4
+ 
_ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_NS0_5__ops15_Iter_comp_iterINS2_12LocMinSortervT_SD_SD_SD_T0_@Base
 6.4.2-4
+ 
_ZSt25__unguarded_linear_insertIN9__gnu_cxx17__normal_iteratorIPN10ClipperLib12LocalMinimumESt6vectorIS3_SaIS3_NS0_5__ops14_Val_comp_iterINS2_12LocMinSortervT_T0_@Base
 6.4.2-4
  (c++)"std::__cxx11::list 
>::merge(std::__cxx11::list >&&)@Base" 
6.4.2
  (c++)"std::__cxx11::list >::sort()@Base" 
6.4.2
- (c++)"std::vector 
>::_M_default_append(unsigned long)@Base" 6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector >::_M_default_append(unsigned long)@Base" 
6.4.2
  (c++)"std::vector 
>::operator=(std::vector > const&)@Base" 6.4.2
- (c++)"std::vector 
>::reserve(unsigned long)@Base" 6.4.2
- (c++)"std::vector 
>::_M_default_append(unsigned long)@Base" 6.4.2
- (c++)"std::vector >::_M_default_append(unsigned long)@Base" 
6.4.2
- (c++)"std::vector >::reserve(unsigned long)@Base" 6.4.2
- (c++)"std::vector >, 
std::allocator > > >::_M_default_append(unsigned 
long)@Base" 6.4.2
- (c++)"std::vector >, 
std::allocator > > >::reserve(unsigned long)@Base" 6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector >::reserve(unsigned long)@Base" 6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector >::_M_default_append(unsigned long)@Base" 
6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector >::_M_default_append(unsigned long)@Base" 
6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector >::reserve(unsigned long)@Base" 6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector >, 
std::allocator > > >::_M_default_append(unsigned 
long)@Base" 6.4.2
+#MISSING: 6.4.2-4# (c++)"std::vector 

Bug#915431: marked as done (dc3dd FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 14:44:21 +
with message-id 
and subject line Bug#915431: fixed in dc3dd 7.2.646-3
has caused the Debian Bug report #915431,
regarding dc3dd FTBFS with glibc 2.28
to be marked as done.

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

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


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

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

...
freadahead.c: In function 'freadahead':
freadahead.c:69:3: error: #error "Please port gnulib freadahead.c to your 
platform! Look at the definition of fflush, fread, ungetc on your system, then 
report this to bug-gnulib."
  #error "Please port gnulib freadahead.c to your platform! Look at the 
definition of fflush, fread, ungetc on your system, then report this to 
bug-gnulib."
   ^
gcc  -I.   -Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
-ffile-prefix-map=/build/1st/dc3dd-7.2.646=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o full-read.o full-read.c
make[4]: *** [Makefile:1470: freadahead.o] Error 1


See #915151 for background.
--- End Message ---
--- Begin Message ---
Source: dc3dd
Source-Version: 7.2.646-3

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

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

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated dc3dd 
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, 11 Dec 2018 11:11:57 -0200
Source: dc3dd
Binary: dc3dd
Architecture: source
Version: 7.2.646-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Joao Eriberto Mota Filho 
Description:
 dc3dd  - patched version of GNU dd with forensic features
Closes: 915431
Changes:
 dc3dd (7.2.646-3) unstable; urgency=medium
 .
   [ Joao Eriberto Mota Filho ]
   * Team upload.
   * debian/copyright:
   - Added rights for Raphaël Hertzog.
   - Updated packaging copyright years.
   - Using https in Format field.
   * debian/patches/30_fix-FTBFS-with-glibc-2.28.patch: added to fix a FTBFS
 with glibc 2.28. Thanks to mschlenker. (Closes: #915431)
   * debian/source/options: added po/bg.po to allow dc3dd build twice.
   * debian/tests/*: added to perform a trivial test.
   * debian/watch: use https.
 .
   [ Raphaël Hertzog ]
   * Drop Christophe Monniez from Uploaders
Checksums-Sha1:
 a48e593f44ee08399683cf9974ab18ce7c2d8881 1898 dc3dd_7.2.646-3.dsc
 f1a59cbf4fa18e62570b8a167ea8c5d929bfb68b 12272 dc3dd_7.2.646-3.debian.tar.xz
 885df6427b9623dc4db0bf5c49f755a976516eb6 5014 dc3dd_7.2.646-3_source.buildinfo
Checksums-Sha256:
 4f4482f783f0a07833c47167420b3558a9ba9a53b899a75c3ebbc9f832f2c760 1898 
dc3dd_7.2.646-3.dsc
 e31d6a8a4c93ff48984fa3729a9ad21aa186c023df17df2eb43092670a8fa3a6 12272 
dc3dd_7.2.646-3.debian.tar.xz
 1ddc9694d58284d3455bf88fe009ae8a83d760dcccbbe26c2ceee844f2d4fffd 5014 
dc3dd_7.2.646-3_source.buildinfo
Files:
 777470288c1ae7eb25abb190fba26540 1898 utils optional dc3dd_7.2.646-3.dsc
 9ebe20933a8fbf319530af03f7f5b682 12272 utils optional 
dc3dd_7.2.646-3.debian.tar.xz
 04243c668568a629243afabaef97cd29 5014 utils optional 
dc3dd_7.2.646-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlwPyDcACgkQ3mO5xwTr
6e+foA/8CjNMtheadONEVPGqjimZXvsXKQ5YobLtZAZp3835+EVYQ6ouWQmr42Jt
zeigbuxUSN3cCMOBQMsmGeo3JsJ2U/LB6Gwd2KVxRUvqbWgzrq/eWDaZFs0NPwzm
2pc24Cv7EILv5TC0T54muHMj4rbHPNz0SUb2PMXTTrZ39ipAe0urUTWPq08AEao5
JE9uiIN92Lfzu18KsBSitNUIR+WrCkvibdGcCPfWSYEs7Rqdb2h8Cd6KmQhuJexM
Vnta6kU4bPZCWtiveNuw45jCZUwgUofVKFA8sn8w/T/7HBQ9j7PWyUiJZKljvvfI
WlDGwf+pnRx3tArNeWloqC7Dbod9L3P+4wdmwNC/Y3bDqyqlunQejAOQppjG0nGn
2LFEq7V5xnWX7IQDqQidwz0HDBB+iOgvpJac7JBTM2zV48KxGIlTLbCqYtrwRp4j
ieEAe3eEimjDj7Xc4LjQdaHUjA3zFpG+VlaG6n0mdh1liqsBCRrbNm5HcTzKGsoK
9y6/XITQ6DVUBX0p/lWVTzM+/IYor/CaAUle6CgfMW1CtccR3PusSNaZP56Ni/jh
merO5G/7tVMySv9ECSeUA5kSj6jVGXCyZ7QtquLkim0QLOhXX8OjaDK3yRtwTbcJ

Bug#877469: NMU diff for 1.0.23-3.1

[Sam Hartman]

Uploaded to delayed/5

diff --git a/debian/changelog b/debian/changelog
index 3f9833c..76020bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+node-websocket (1.0.23-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't run dh_nodejs against libjs-websocket, because that is an arch
+all package with no ABI dependencies.  We don't want shared library
+dependencies on an arch all package because it breaks the ability to
+do binary NMUs for library transitions, Closes: #877469
+
+ -- Sam Hartman   Tue, 11 Dec 2018 08:50:44 -0500
+
 node-websocket (1.0.23-3) unstable; urgency=medium
 
   * Team Upload
diff --git a/debian/rules b/debian/rules
index e347699..a49f49e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -16,6 +16,9 @@ export DH_OPTIONS
 override_dh_auto_test-arch:
tap test/unit
 
+# We do not need abi dependencies for a source all package
+override_dh_nodejs:
+   dh_nodejs -pnode-websocket
 override_dh_install-arch:
dh_install
chmod 644 
$(CURDIR)/debian/node-websocket/usr/lib/nodejs/websocket/build/Release/*.node


signature.asc
Description: PGP signature

Bug#916211: jfsutils FTBFS with glibc 2.28

[Adrian Bunk]

Source: jfsutils
Version: 1.1.15-3
Severity: serious
Tags: ftbfs

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

...
devices.c: In function 'ujfs_flush_dev':
devices.c:469:6: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  if (major(buf.st_rdev) != RAMDISK_MAJOR)
  ^
...
gcc -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 
-ffile-prefix-map=/build/1st/jfsutils-1.1.15=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-z,relro -o jfs_fsck fsckbmap.o 
fsckconn.o fsckdire.o fsckdtre.o fsckea.o fsckimap.o fsckino.o fsckmeta.o 
fsckpfs.o dirindex.o fsckwsp.o fsckxtre.o xchkdsk.o fsckruns.o fsck_message.o 
../libfs/libfs.a -luuid 
/usr/bin/ld: ../libfs/libfs.a(devices.o): in function `ujfs_flush_dev':
./libfs/devices.c:469: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:267: jfs_fsck] Error 1

Bug#912682: usefulness of this package?

[Cyrille Bollu]

>From its debian/control file:

>This module is already included as part of Perl's core distribution, so
this
> package is only beneficial when newer features or bug fixes are required.

I don't understand how

Bug#916209: britney: handling of binNMUs in tpu broken

[Ivo De Decker]

Package: release.debian.org
Severity: serious
User: release.debian@packages.debian.org
Usertags: britney


When {testing,stable}-proposed-updates has a binary-only item (binNMU or
missing build that arrived later), britney will use the binaries from unstable
instead, possibly migrating them even if they are from a different source and
should not be a candidate. During the freeze, a binNMU in tpu would cause the
binaries from a newer (blocked) source in unstable to show up in testing. As
this causes britney to potentially migrate random unwanted binaries, I filed
this bug as serious.

This is caused by wrong parsing of MigrationItem and can be fixed by the
attached patch.

Please note that the root cause of this issue is that the excuses calculation
uses detailed information about the binaries and sources involved, but this
information isn't passed on. Only the 'name' of the migration item is passed
on, and later on, britney tries to calculate the set of binaries and sources
again based on the info gathered from parsing this name.

With the attached patch, however, other issues with binNMUs in tpu show up:

When both a new source from unstable and a binNMU from tpu are candidates,
britney might migrate the new source first and then accept the binNMU. This
causes the architecture of the binNMU to have the older binaries from the
binNMU, while other architectures have the newer once. If there are no rdeps,
the older binaries are removed because they are considered old binaries from
smooth updates (because they are built by a different source version).

Allow the binNMU to migrate is clearly wrong, because after the migration of
the new source, the binNMU of the old source should no longer be considered.

Some of this is tested by the following tests in the testsuite:

binnmu-tpu
binnmu-tpu-rdeps
bug-unfiled-2

Additional tests could be useful for combinations with arch: all packages (on
some/all architectures) and binary takeovers (arch: all/any, on some/all
architectures, ...).


As a 'temporary' workaround, it might be good to disable binary-only items
from *pu completely for now, to avoid this issue.

More targeted workarounds could include:

- Only allow binNMUs from *pu with an explicit hint (which would have to be
  used with care).
- Disable binary-only items that contain binaries that are also built by
  source items that are a candidate. This would mean that a new source from
  unstable must be blocked explicitly if you want to allow a binNMU from *pu
  to migrate.
- Always try binary-only items before source items. I don't really know how
  this could be enforced when multiple easy hints are tried or during a hint
  run.

More ideas welcome...

Ivo

>From 67628b80ad208f0eca2262e79eb0d5fd5372b8c8 Mon Sep 17 00:00:00 2001
From: Ivo De Decker 
Date: Tue, 11 Dec 2018 12:37:45 +
Subject: [PATCH] Fix parsing of migration item name for binNMU in tpu

The parsing of migration items should also look for the suite name in the
architecture part. This fixes the parsing for migration items like
some-src/amd64_tpu and some-src/amd64_tpu/1.0-1

Signed-off-by: Ivo De Decker 
---
 britney2/migrationitem.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/britney2/migrationitem.py b/britney2/migrationitem.py
index 1122852..f6b1090 100644
--- a/britney2/migrationitem.py
+++ b/britney2/migrationitem.py
@@ -97,6 +97,9 @@ class MigrationItem(object):
 else:
 self._architecture = 'source'
 
+if '_' in self._architecture:
+self._architecture, suite_name = self._architecture.split('_', 2)
+
 if self._version in self.__class__.get_architectures():
 (self._architecture, self._version) = \
 (self._version, self._architecture)
-- 
2.11.0

Processed: Delayed NMU, debdiff

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#915431: dc3dd FTBFS with glibc 2.28

[Eriberto Mota]

Em seg, 3 de dez de 2018 às 18:42, Adrian Bunk  escreveu:
>
> Source: dc3dd
> Version: 7.2.646-2
> Severity: serious
> Tags: ftbfs
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dc3dd.html
>
> ...
> freadahead.c: In function 'freadahead':
> freadahead.c:69:3: error: #error "Please port gnulib freadahead.c to your 
> platform! Look at the definition of fflush, fread, ungetc on your system, 
> then report this to bug-gnulib."
>   #error "Please port gnulib freadahead.c to your platform! Look at the 
> definition of fflush, fread, ungetc on your system, then report this to 
> bug-gnulib."
>^
> gcc  -I.   -Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
> -ffile-prefix-map=/build/1st/dc3dd-7.2.646=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o full-read.o full-read.c
> make[4]: *** [Makefile:1470: freadahead.o] Error 1
>
>
> See #915151 for background.
>


Hi all,

I will apply the patch available here[1].

[1] https://aur.archlinux.org/packages/dc3dd/

Regards,

Eriberto

Bug#914616: Fixed by latest binNMU

[Bernhard Übelacker]

Control: notfixed 914616 20181001.4.a99aaec~ds6-2+b1

Hello Petter Reinholdtsen,
in another bug I got told that BTS is not handling
binNMU versions, therefore ending up with fixed+found
versions being the same (915364).

Maybe that is also the case here why the autoremoval stays.
Let's try to just remove the fixed and see if the autoremoval
is removed tomorrow?

Kind regards,
Bernhard

Processed: Re: Bug#914616: Fixed by latest binNMU

[Debian Bug Tracking System]

Processing control commands:

> notfixed 914616 20181001.4.a99aaec~ds6-2+b1
Bug #914616 {Done: Bruno Kleinert } [ring-daemon] 
[ring-daemon] Crashes because of segmentation fault
No longer marked as fixed in versions 20181001.4.a99aaec~ds6-2+b1.

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

Bug#915462: marked as done (libnitrokey FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Tue, 11 Dec 2018 13:19:42 +
with message-id 
and subject line Bug#915462: fixed in libnitrokey 3.4.1-2
has caused the Debian Bug report #915462,
regarding libnitrokey FTBFS: symbol differences
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.)


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

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

...
   dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libnitrokey3/DEBIAN/symbols doesn't match 
completely debian/libnitrokey3.symbols
--- debian/libnitrokey3.symbols (libnitrokey3_3.3-2_amd64)
+++ dpkg-gensymbolsoA6e6E   2020-01-05 16:41:01.351092338 -1200
@@ -380,7 +380,7 @@
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE39ERKNS0_14DeviceResponseILS2_39ENS0_12EmptyPayload7dissectB5cxx11ES7_@Base
 3.1
  (optional=templinst|arch=amd64 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE39ERKNS0_14DeviceResponseILS2_39ENS0_12EmptyPayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE3ERKNS0_14DeviceResponseILS2_3ENS0_7stick108ReadSlot15ResponsePayload7dissectB5cxx11ES9_@Base
 3.1
- (optional=templinst|arch=amd64 hppa 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE3ERKNS0_14DeviceResponseILS2_3ENS0_7stick108ReadSlot15ResponsePayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
+#MISSING: 3.3-2# (optional=templinst|arch=amd64 hppa 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE3ERKNS0_14DeviceResponseILS2_3ENS0_7stick108ReadSlot15ResponsePayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE41ERKNS0_14DeviceResponseILS2_41ENS0_12EmptyPayload7dissectB5cxx11ES7_@Base
 3.1
  (optional=templinst|arch=amd64 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE41ERKNS0_14DeviceResponseILS2_41ENS0_12EmptyPayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE42ERKNS0_14DeviceResponseILS2_42ENS0_12EmptyPayload7dissectB5cxx11ES7_@Base
 3.1
@@ -428,7 +428,7 @@
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE8ERKNS0_14DeviceResponseILS2_8ENS0_12EmptyPayload7dissectB5cxx11ES7_@Base
 3.1
  (optional=templinst|arch=amd64 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE8ERKNS0_14DeviceResponseILS2_8ENS0_12EmptyPayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE96ERKNS0_14DeviceResponseILS2_96ENS0_7stick1025GetPasswordSafeSlotStatus15ResponsePayload7dissectB5cxx11ES9_@Base
 3.1
- (optional=templinst|arch=amd64 hppa 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE96ERKNS0_14DeviceResponseILS2_96ENS0_7stick1025GetPasswordSafeSlotStatus15ResponsePayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
+#MISSING: 3.3-2# (optional=templinst|arch=amd64 hppa 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE96ERKNS0_14DeviceResponseILS2_96ENS0_7stick1025GetPasswordSafeSlotStatus15ResponsePayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE97ERKNS0_14DeviceResponseILS2_97ENS0_7stick1023GetPasswordSafeSlotName15ResponsePayload7dissectB5cxx11ES9_@Base
 3.1
  (optional=templinst|arch=amd64 hppa 
s390x)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE97ERKNS0_14DeviceResponseILS2_97ENS0_7stick1023GetPasswordSafeSlotName15ResponsePayload8to_upperENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.3
  
(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE98ERKNS0_14DeviceResponseILS2_98ENS0_7stick1027GetPasswordSafeSlotPassword15ResponsePayload7dissectB5cxx11ES9_@Base
 3.1
@@ -491,13 +491,15 @@
  _ZNK8nitrokey15NitrokeyManager33get_internal_slot_number_for_totpEh@Base 3.1
  

Bug#904396: closed by Kartik Mistry (Bug#904396: fixed in foma 1:0.9.18+r243-4)

[Andreas Beckmann]

Control: found -1  1:0.9.18+r243-4

Even with a transitional package added, you will need

Package: foma
Breaks: foma-bin (<< 1:0)
Replaces: foma-bin (<< 1:0)

since the unpacking order cannot be guaranteed.
The currently existing Breaks+Replaces seem to miss the epoch.


Andreas

Bug#915428: libpmount FTBFS with glibc 2.28

[Guillem Jover]

Hi!

On Mon, 2018-12-03 at 22:09:06 +0200, Adrian Bunk wrote:
> Source: libpmount
> Version: 0.0.17-3
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpmount.html
> 
> ...
> linux.c: In function '__findloop':
> linux.c:97:9: warning: implicit declaration of function 'major' 
> [-Wimplicit-function-declaration]
>  if (major(st.st_rdev) != 7)
>  ^
> ...
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/kerndep.o .libs/mtab.o 
> .libs/pmount.o-O2 -Wl,-z -Wl,defs -Wl,--version-script=./libpmount.map 
> -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname -Wl,libpmount.so.0 -o 
> .libs/libpmount.so.0.0.17
> /usr/bin/ld: .libs/kerndep.o: in function `__findloop':
> ./src/linux.c:97: undefined reference to `major'
> collect2: error: ld returned 1 exit status
> make[3]: *** [Makefile:422: libpmount.la] Error 1

Ugh, it seems I lost track of this. Was reminded today due to the
autoremoval mail. Will upload later today.

Thanks,
Guillem

Processed: Re: Bug#904396 closed by Kartik Mistry (Bug#904396: fixed in foma 1:0.9.18+r243-4)

[Debian Bug Tracking System]

Processing control commands:

> found -1  1:0.9.18+r243-4
Bug #904396 {Done: Kartik Mistry } [foma] foma: fails to 
upgrade from 'sid' - trying to overwrite /usr/bin/cgflookup
Marked as found in versions foma/1:0.9.18+r243-4; no longer marked as fixed in 
versions foma/1:0.9.18+r243-4 and reopened.

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

Processed: Re: Bug#915857: radare2: 3.1 fails to build on mipsel, ppc64el, s390x

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending fixed-upstream
Bug #915857 [src:radare2] radare2: 3.1 fails to build on mipsel, ppc64el, s390x
Added tag(s) pending and fixed-upstream.
> forwarded -1 https://github.com/radare/radare2/pull/12455
Bug #915857 [src:radare2] radare2: 3.1 fails to build on mipsel, ppc64el, s390x
Set Bug forwarded-to-address to 'https://github.com/radare/radare2/pull/12455'.

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

Bug#915857: radare2: 3.1 fails to build on mipsel, ppc64el, s390x

[Iain Lane]

Control: tags -1 + pending fixed-upstream
Control: forwarded -1 https://github.com/radare/radare2/pull/12455

> io.c: In function 'r_io_ptrace_func':
> io.c:680:2: error: unknown type name 'ptrace_wrap_instance'
>   ptrace_wrap_instance *wrap = io_ptrace_wrap_instance (io);
>   ^~~~

It was a problem with --disable-debugger. I submitted a fix upstream and
uploaded to DELAYED/5 - feel free to reschedule/cancel/upload
yourself/whatever. Also on
https://salsa.debian.org/pkg-security-team/radare2/merge_requests/1/ for
merging convenience (signed tag in my fork too).

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Bug#887601: libcamlimages-ocaml: Detect freetype using pkg-config

[Hideki Yamane]

Hi,

On Thu, 18 Jan 2018 11:19:18 + Hugh McMaster  
wrote:
> Package: libcamlimages-ocaml
> Version: 1:4.2.0-1.1+b3
> Severity: important
> 
> Dear Maintainer,
> 
> The next version of libfreetype6-dev will *not* ship the 'freetype-config'
> script.
> 
> Please use pkg-config to detect the freetype headers and libraries instead.

 I've prepared patches (and more update) at
 https://salsa.debian.org/ocaml-team/camlimages/merge_requests/2

 I'm not sure why but I cannot detect freetype header files with
 Check_header_library, so just specified pkg-config checks returns
 "true".

 Anyway, please check it.
 

-- 
Hideki Yamane 

Processed: merging 916197 916198

[Debian Bug Tracking System]

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

> merge 916197 916198
Bug #916197 [libpaper1] libpaper1: postrm fails, uses ucf unconditionally
Bug #916198 [libpaper1] [piuparts] libpaper1 fails to purge: ucf not found
Merged 916197 916198
> thanks
Stopping processing here.

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

Bug#911364: firefox-esr: Master password lost after update from ESR v52.9.0 to ESR v60.2.2 (along with all user certificates and saved passwords)

[Bernie Elbourn]

I have a terminal served system but I am unsure who might have the issue.

Is there a way to scan the users firefox settings to see how many users have the 
"master password" set?

Huge thanks,

Bernie

Processed: your mail

[Debian Bug Tracking System]

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

> tag 915859 upstream
Bug #915859 [onionshare] uses a fixed filename in /tmp
Added tag(s) upstream.
> forwarded 915859 https://github.com/micahflee/onionshare/issues/837
Bug #915859 [onionshare] uses a fixed filename in /tmp
Set Bug forwarded-to-address to 
'https://github.com/micahflee/onionshare/issues/837'.
> thanks
Stopping processing here.

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

Bug#916198: [piuparts] libpaper1 fails to purge: ucf not found

[Didier 'OdyX' Raboud]

Package: libpaper1
Version: 1.1.25
Severity: serious

piuparts detected that libpaper1 fails to purge, because its postrm
doesn't check that ucf is available during purge.

https://piuparts.debian.org/sid/fail/libpaper1_1.1.25.log

  Purging configuration files for libpaper1:amd64 (1.1.25) ...
  /var/lib/dpkg/info/libpaper1:amd64.postrm: 16: 
/var/lib/dpkg/info/libpaper1:amd64.postrm: ucf: not found
  dpkg: error processing package libpaper1:amd64 (--purge):
   installed libpaper1:amd64 package post-removal script subprocess returned 
error exit status 127
  Errors were encountered while processing:
   libpaper1:amd64
  
It should test for ucf's presence, for example as openssh does:

if which ucf >/dev/null 2>&1; then
ucf --purge /etc/ssh/sshd_config
fi

(This is serious as it affects all reverse dependencies of libpaper1 in their 
piuparts logs too)

Cheers,
OdyX

Bug#916197: libpaper1: postrm fails, uses ucf unconditionally

[Carsten Leonhardt]

Package: libpaper1
Version: 1.1.25
Severity: serious

Dear Maintainer,

the postrm fails because it uses ucf unconditionally. When executing the
postrm, dependencies are not guaranteed to be installed.

Please see /usr/share/doc/ucf/examples/postrm on how to do it corretly.

See also https://piuparts.debian.org/sid/fail/libpaper1_1.1.25.log

Regards,

Carsten

Processed: skipping all tests, non-critical

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #905648 [ruby-parallel] ruby-parallel: FTBFS - test failures
Severity set to 'normal' from 'serious'

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

Processed: retitle 916192 to foma ftbfs from source

[Debian Bug Tracking System]

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

> retitle 916192 foma ftbfs from source
Bug #916192 [src:foma] defoma ftbfs from source
Changed Bug title to 'foma ftbfs from source' from 'defoma ftbfs from source'.
> thanks
Stopping processing here.

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

Bug#905648: skipping all tests, non-critical

[Cédric Boutillier]

Control: severity -1 normal


As per upstream's advice,
https://github.com/grosser/parallel/issues/227

tests are now skipped entirely (except naive library loading) since
1.12.1-2.

The test failures are still present, but are not critical anymore
because they don't lead to build failure.
I am therefore lowering the severity

Cedric



signature.asc
Description: PGP signature

Bug#916194: lizardfs FTBFS with glibc 2.28

[Adrian Bunk]

Source: lizardfs
Version: 3.12.0+dfsg-2
Severity: serious
Tags: ftbfs

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

...
In file included from 
/build/1st/lizardfs-3.12.0+dfsg/src/chunkserver/hddspacemgr.cc:69:
/build/1st/lizardfs-3.12.0+dfsg/src/chunkserver/iostat.h: In member function 
'uint8_t IoStat::getLoadFactor()':
/build/1st/lizardfs-3.12.0+dfsg/src/chunkserver/iostat.h:112:26: error: 
'makedev' was not declared in this scope
auto it = stats_.find(makedev(major, minor));
  ^~~
...

Bug#915831: zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure

[Petter Reinholdtsen]

[Rich Ercolani]
> Setting up zfsutils-linux (0.7.12-1) ...
> insserv: Service zfs-zed has to be enabled to start service zfs-share
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header

An alternative to dropping the boot order relation is to change the
order the scripts are registered into the boot sequence.  Is it possible
to ensure zfs-zed is registered before zfs-share on installation, and
unregistered after on package uninstallation?

-- 
Happy hacking
Petter Reinholdtsen

Processed: reassign 916192 to src:foma

[Debian Bug Tracking System]

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

> reassign 916192 src:foma
Bug #916192 [src:defoma] defoma ftbfs from source
Warning: Unknown package 'src:defoma'
Bug reassigned from package 'src:defoma' to 'src:foma'.
No longer marked as found in versions defoma/1:0.9.18+r243-4.
Ignoring request to alter fixed versions of bug #916192 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#916192: defoma ftbfs from source

[Matthias Klose]

Package: src:defoma
Version: 1:0.9.18+r243-4
Severity: serious

defoma ftbfs from source, at least on armhf and s390x (also on amd64 and i386 in
Ubuntu with the same failure):

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

gcc -g -O2 -fdebug-prefix-map=/<>/foma-0.9.18+r243=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -D_GNU_SOURCE
-std=c99 -fvisibility=hidden -fPIC -Wl,-z,relro -c regex.c -o regex.o
gcc -g -O2 -fdebug-prefix-map=/<>/foma-0.9.18+r243=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -D_GNU_SOURCE
-std=c99 -fvisibility=hidden -fPIC -Wl,-z,relro -c foma.c -o foma.o
regex.c: In function 'yyparse':
regex.c:2779:3: error: unterminated comment
   /* User semantic actions sometimes alter yychar, and that requires
   ^
regex.c:2778:5: error: expected declaration or statement at end of input
 }
 ^
regex.y:406:5: error: label 'yyerrorlab' used but not defined
 { if (($$ = function_apply(defined_nets, defined_funcs)) == NULL) YYERROR;}
 ^
regex.c:1950:5: error: label 'yyerrlab' used but not defined
 goto yyerrlab;
 ^~~~
regex.c:1874:5: error: label 'yyacceptlab' used but not defined
 YYACCEPT;
 ^~~~
regex.c:1868:9: error: label 'yyabortlab' used but not defined
 YYABORT;
 ^~~
regex.c:1849:11: error: label 'yyexhaustedlab' used but not defined
   goto yyexhaustedlab;
   ^~~~
regex.c:1746:7: warning: unused variable 'yyresult' [-Wunused-variable]
   int yyresult;
   ^~~~
regex.c:1741:13: warning: variable 'yyerror_range' set but not used
[-Wunused-but-set-variable]
 YYLTYPE yyerror_range[3];
 ^
regex.c:1711:9: warning: variable 'yynerrs' set but not used
[-Wunused-but-set-variable]
 int yynerrs;
 ^~~
regex.c:2778:5: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
At top level:
regex.c:1666:1: warning: 'yydestruct' defined but not used [-Wunused-function]
 yydestruct (const char *yymsg, int yytype, YYSTYPE *yyvaluep, YYLTYPE
*yylocationp, void *scanner, struct defined_networks *defined_nets, struct
defined_functions *defined_funcs)
 ^~
regex.c:1147:27: warning: 'yyr1' defined but not used [-Wunused-const-variable=]
 static const yytype_uint8 yyr1[] =
   ^~~~
regex.c:1112:27: warning: 'yystos' defined but not used 
[-Wunused-const-variable=]
 static const yytype_uint8 yystos[] =
   ^~
regex.c:854:27: warning: 'yydefgoto' defined but not used 
[-Wunused-const-variable=]
 static const yytype_int16 yydefgoto[] =
   ^
regex.c:846:26: warning: 'yypgoto' defined but not used 
[-Wunused-const-variable=]
 static const yytype_int8 yypgoto[] =
  ^~~
make[1]: *** [Makefile:92: regex.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>/foma-0.9.18+r243'
dh_auto_build: make V=1 -j4 "INSTALL=install --strip-program=true" returned exit
code 2
make: *** [debian/rules:10: build-arch] Error 2