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

[Adam Conrad]

On Thu, Oct 26, 2017 at 08:59:23PM +0200, Mattia Rizzolo wrote:
> On Wed, Oct 25, 2017 at 10:40:20PM -0600, Adam Conrad wrote:
> 
> We like to backport devscripts, and I'd rather not have backports deltas
> if possible...

I'd suggest that this commit already makes no-delta backports somewhat
problematic:

https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=921696fd6c92c4299accb1e2ef1ae48d13a47b0d

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

diff -Nru devscripts-2.17.10/test/test_mk-origtargz 
devscripts-2.17.10ubuntu2/test/test_mk-origtargz
--- devscripts-2.17.10/test/test_mk-origtargz   2017-09-13 20:08:30.0 
-0600
+++ devscripts-2.17.10ubuntu2/test/test_mk-origtargz2017-10-26 
22:38:49.0 -0600
@@ -26,6 +26,12 @@
 PROGNAME="mk-origtargz.pl"
 fi
 
+if dpkg --compare-versions $(dpkg-query -W -f='${Version}' libdpkg-perl) lt 
1.19.0~; then
+SUBPROCESS_ERROR="gave error exit status 2"
+else
+SUBPROCESS_ERROR="subprocess returned exit status 2"
+fi
+
 cleanup(){
rm -rf $TMPDIR
unset LC_ALL
@@ -540,7 +546,7 @@
"tar: This does not look like a tar archive
 tar: Skipping to next header
 tar: Exiting with failure status due to previous errors
-$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
gave error exit status 2" \
+$PROGNAME: error: tar --list --auto-compress --file ../foo_0.1.orig.tar.xz 
$SUBPROCESS_ERROR" \
"" \
 ../foo-0.1.tar.gz --repack --compression xz
 }

... Adam

Bug#879886: [Debian-med-packaging] Bug#879886: Bug#879886: libhts2: libhts2 needs to handle ABI changes

[Afif Elghraoui]

Hi, Mattia and all,

على الخميس 26 تشرين الأول 2017 ‫15:44، كتب Mattia Rizzolo:
> On Thu, Oct 26, 2017 at 12:12:05PM -0700, Diane Trout wrote:
>> libhts2 introduced an ABI change which broke python-pysam, and a new
>> version of python-pysam needed to be released to update to the new ABI.
> 
> FTR, this is what changed between the symbols of the version 1.4.1-5 and
> 1.5-1:
> 
[...]
> 
>> libhts2 probably needs a proper symbols file to make it easier to see
>> when the ABI is changing. https://wiki.debian.org/UsingSymbolsFiles
>>
>> Mattia Rizzolo, also suggests other methods of dealing with managing ABI
>> changes.
> 
> In pysam's case, it is looking for hts_log, if you had properly checked
> the symbols of your package before uploading you should have at least
> tweaked the dh_shlibdeps invocation to force a version, or introduced a
> .symbols file (very recommended for a case like hstlib where the symbols
> seems to be simple).
> 
> But then, the ABI is broken, so just nicest symbols handling is not
> enough for your case, you need
>> Such as bumping soname, changing the package name and use Conflicts, or
>> adding versioned Breaks against broken packages
> 
> 

Please see #822701; specifically:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822701#26
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822701#41 (and
subsequent replies)
and
https://lists.alioth.debian.org/pipermail/debian-med-packaging/2016-January/038827.html
(which is linked from one of the replies to the above)

We've been doing this for every htslib suite release and can confirm
upstream's explanation. Other packages do not get broken. Upstream has
made a soname bump as appropriate for the 1.4 release if I remember
correctly. That's all I can say about this; I don't actually work on the
htslib packaging myself.

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#879879: marked as done (python3-monajat: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/locale/ar/LC_MESSAGES/monajat.mo)

[Debian Bug Tracking System]

Your message dated Fri, 27 Oct 2017 01:49:10 +
with message-id 
and subject line Bug#879879: fixed in monajat 4.1-2
has caused the Debian Bug report #879879,
regarding python3-monajat: fails to upgrade from 'stable' to 'sid' - trying to 
overwrite /usr/share/locale/ar/LC_MESSAGES/monajat.mo
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.)


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

Hi,

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

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

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

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

  Selecting previously unselected package python3-monajat.
  Preparing to unpack .../python3-monajat_4.1-1_all.deb ...
  Unpacking python3-monajat (4.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-monajat_4.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/monajat.mo', which is 
also in package python-monajat 2.6.5-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-monajat_4.1-1_all.deb


cheers,

Andreas


python-monajat=2.6.5-1_python3-monajat=4.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: monajat
Source-Version: 4.1-2

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

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

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

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated monajat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Oct 2017 03:17:51 +0200
Source: monajat
Binary: python3-monajat monajat-data monajat-applet monajat-mod 
monajat-screenlet
Architecture: source
Version: 4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Islamic Maintainers 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Description:
 monajat-applet - Islamic supplications tray applet
 monajat-data - Islamic supplications database
 monajat-mod - Islamic supplications console utility
 monajat-screenlet - Islamic supplications screenlet
 python3-monajat - Islamic supplications backend
Closes: 879879
Changes:
 monajat (4.1-2) unstable; urgency=medium
 .
   * Add Breaks/Replaces: python-monajat for python3-monajat (Closes: #879879)
Checksums-Sha1:
 c51ca18d43e21e710af7e490c2e77ed591fdc393 1966 monajat_4.1-2.dsc
 6b9b05d95530c4db0568687c28fbb89b93a3bcac 5124 monajat_4.1-2.debian.tar.xz
Checksums-Sha256:
 228eafab24446962e99b557717d337d82254af1fc28e305697cca271373189b3 1966 
monajat_4.1-2.dsc
 b63f6eb36075ade33cbfa919a10ac0bbc8a83d511feda1ac15e262d100f3db86 5124 
monajat_4.1-2.debian.tar.xz
Files:
 5c74d760ed6e70975c90c9adde834e46 1966 utils optional monajat_4.1-2.dsc
 acd36c571209b9da2aa09f3d8a13d57a 5124 utils optional 
monajat_4.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJZ8omYAAoJELwZapTt3aG3UVQH/2htFhPYXkAxYlKbfiP13OXo
K1L5kfOc9ONKxas9lTNjj73jUbFiylrqIIQvGmwBxyDbGTEp0oczPoFFdfjsr+yK
//JYIc7ZAq561RTj38lHmG5MonAd1Fdge828Gr2pP2Mwa7/v4aHLAc1ios7APt5m
RScTws8kXuRlTVI9aMSP0ZfVpS3thVihW+tcTlnAiH1/3t5urBFuYVxqueQbtea9
BIwBz26kaT8tN9wSZVOk2lXpXZHcQOw9aqWNk447utSjWZriEMGsdG2EDgWCgx4G
6SiOXOwr8zuFrLhEfep6DFRFAjk/isl0/glo/E6CoBWA00INvnJeQfM7FRHFETA=
=yi74
-END PGP SIGNATURE End Message ---

Bug#879224: marked as done (websockify: missing dependency on python-pkg-resources)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 22:37:17 +
with message-id 
and subject line Bug#879224: fixed in websockify 0.8.0+dfsg1-9
has caused the Debian Bug report #879224,
regarding websockify: missing dependency on python-pkg-resources
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.)


-- 
879224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: websockify
Version: 0.6.0+dfsg1-1
Severity: serious
Control: affects -1 python-websockify python3-websockify

$ websockify 
Traceback (most recent call last):
  File "/usr/bin/websockify", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
$ 
--- End Message ---
--- Begin Message ---
Source: websockify
Source-Version: 0.8.0+dfsg1-9

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated websockify package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Oct 2017 03:15:54 +
Source: websockify
Binary: python-websockify python3-websockify websockify websockify-common
Architecture: source amd64 all
Version: 0.8.0+dfsg1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-websockify - WebSockets support for any application/server - Python 2
 python3-websockify - WebSockets support for any application/server - Python 3
 websockify - WebSockets support for any application/server
 websockify-common - WebSockets support for any application/server - shared 
files
Closes: 879224
Changes:
 websockify (0.8.0+dfsg1-9) unstable; urgency=medium
 .
   * Add runtime depends on python{3,}-pkg-resources (Closes: #879224).
   * Removed old Breaks+Replaces.
   * Using pkgos-dh_auto_install.
Checksums-Sha1:
 60f0926656068ec695335035a70561d554ad55ea 2398 websockify_0.8.0+dfsg1-9.dsc
 d46aa4ed9fca1e23fa457f737c9ffb970933e133 11852 
websockify_0.8.0+dfsg1-9.debian.tar.xz
 a4c42fa3ecbd41cc4b3bcbdd8ce45241125c2901 31964 
python-websockify_0.8.0+dfsg1-9_amd64.deb
 28260087a06eb7d1ab50e2b585cc7ec5ac6a4d2e 32040 
python3-websockify_0.8.0+dfsg1-9_amd64.deb
 d13ebf55b4acab73edf6b33b75cca9989521019b 29192 
websockify-common_0.8.0+dfsg1-9_all.deb
 c1f39dab6a405a5c6a5b85018e702c5b90b97149 5200 
websockify-dbgsym_0.8.0+dfsg1-9_amd64.deb
 16a525991a19b0cfc772434178cf6e3110d50e6e 10383 
websockify_0.8.0+dfsg1-9_amd64.buildinfo
 f185b818975c2b4526adc1a907e6b014c6783438 24264 
websockify_0.8.0+dfsg1-9_amd64.deb
Checksums-Sha256:
 6fcd7ab5601a05b7682a83030a886ee972c821a570270e6a0bd07fa0a09245d6 2398 
websockify_0.8.0+dfsg1-9.dsc
 02752ee17fcf72e26b89acc0c817a7db3b09641b8290a3fe562ee5a4f6ef4dec 11852 
websockify_0.8.0+dfsg1-9.debian.tar.xz
 897bdfd7e6a428b89be8a5ab3f98915cd9b097a429cda64b1eb3993867d4b383 31964 
python-websockify_0.8.0+dfsg1-9_amd64.deb
 f6716bceb662a5677ec1d3c72f661294fa6fe6ec51f9e2ce8fe29bfe150d0206 32040 
python3-websockify_0.8.0+dfsg1-9_amd64.deb
 f17528609f5961f775e51b21508821593687b9590c50e6ffda0056aa6a3fc420 29192 
websockify-common_0.8.0+dfsg1-9_all.deb
 2306dc99c2d5d4e605cd37b13534471d94473e535a3237ffb3248cb33b692ea1 5200 
websockify-dbgsym_0.8.0+dfsg1-9_amd64.deb
 a6202b26919aac6e9008a74f1dc7292614796b471ceb3a1a4a46068d33eac049 10383 
websockify_0.8.0+dfsg1-9_amd64.buildinfo
 b52f5d7767828fd38397ae6c04f1f4a23fb3141304038f69584efb94af1a5781 24264 
websockify_0.8.0+dfsg1-9_amd64.deb
Files:
 1498073673971134797e99e892233673 2398 python optional 
websockify_0.8.0+dfsg1-9.dsc
 d1f62b7df7ce4a343c6819059db68a62 11852 python optional 
websockify_0.8.0+dfsg1-9.debian.tar.xz
 d3a73b7bed5a155511b43aa689df9e34 31964 python optional 
python-websockify_0.8.0+dfsg1-9_amd64.deb
 bfefe742bbe7bff7d51a92a4ce3ca527 32040 python optional 
python3-websockify_0.8.0+dfsg1-9_amd64.deb
 df204baff69aaec57404c21cc8273d0c 29192 python optional 

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

[Paddy Steed]

Why do I keep on getting these emails, please for the love of God someone
tell me how to unsubscribe from whatever nightmare list this is.

On 26 Oct 2017 11:57, "Vincent Lefevre"  wrote:

Package: libgles1-glvnd-nvidia
Version: 375.82-6
Severity: grave
Justification: renders package unusable

In the upgrade to 375.82-6:

Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb ...
Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-6_i386.deb ...
Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5) ...
Processing triggers for mime-support (3.60) ...
Setting up libnvidia-eglcore:amd64 (375.82-6) ...
Setting up libnvidia-eglcore:i386 (375.82-6) ...
Processing triggers for desktop-file-utils (0.23-2) ...
Setting up libnvidia-glcore:amd64 (375.82-6) ...
Setting up libnvidia-glcore:i386 (375.82-6) ...
Processing triggers for libc-bin (2.24-17) ...
Setting up nvidia-egl-common (375.82-6) ...
Setting up nvidia-vulkan-common (375.82-6) ...
Setting up nvidia-legacy-check (375.82-6) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up nvidia-alternative (375.82-6) ...
Processing triggers for nvidia-alternative (375.82-6) ...
Setting up libglx-nvidia0:amd64 (375.82-6) ...
Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
Setting up nvidia-kernel-support (375.82-6) ...
Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
Setting up libegl-nvidia0:amd64 (375.82-6) ...
Setting up libegl-nvidia0:i386 (375.82-6) ...
Setting up libgles-nvidia2:i386 (375.82-6) ...
Setting up libgles-nvidia2:amd64 (375.82-6) ...
Setting up libnvidia-cfg1:amd64 (375.82-6) ...
Setting up libnvidia-cfg1:i386 (375.82-6) ...
dpkg: dependency problems prevent configuration of
libgles1-glvnd-nvidia:amd64:
 libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
unpacked but not configured.
  libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of
libgles1-glvnd-nvidia:i386:
 libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and is
unpacked but not configured.
  libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:i386 (--configure):
 dependency problems - leaving unconfigured
Setting up nvidia-kernel-dkms (375.82-6) ...
[...]
Setting up libnvidia-ml1:amd64 (375.82-6) ...
dpkg: dependency problems prevent configuration of libgles-nvidia1:amd64:
 libgles-nvidia1:amd64 depends on libgles1 (>= 0.2.999) |
libgles1-glvnd-nvidia; however:
  Package libgles1 is not installed.
  Package libgles1-glvnd-nvidia:amd64 which provides libgles1 is not
configured yet.
  Package libgles1-glvnd-nvidia:amd64 is not configured yet.

dpkg: error processing package libgles-nvidia1:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgles-nvidia1:i386:
 libgles-nvidia1:i386 depends on libgles1 (>= 0.2.999) |
libgles1-glvnd-nvidia; however:
  Package libgles1-glvnd-nvidia:i386 which provides libgles1 is not
configured yet.
  Package libgles1-glvnd-nvidia:i386 is not configured yet.

dpkg: error processing package libgles-nvidia1:i386 (--configure):
 dependency problems - leaving unconfigured
Setting up libgl1-nvidia-glvnd-glx:amd64 (375.82-6) ...
Setting up xserver-xorg-video-nvidia (375.82-6) ...
Setting up nvidia-driver-bin (375.82-6) ...
Setting up libglx-nvidia0:i386 (375.82-6) ...
Setting up nvidia-vulkan-icd:i386 (375.82-6) ...
Setting up nvidia-egl-icd:i386 (375.82-6) ...
Setting up nvidia-egl-icd:amd64 (375.82-6) ...
Setting up libgl1-nvidia-glvnd-glx:i386 (375.82-6) ...
Setting up nvidia-driver-libs:amd64 (375.82-6) ...
Setting up nvidia-driver-libs:i386 (375.82-6) ...
Setting up nvidia-driver (375.82-6) ...
Setting up nvidia-driver-libs-i386:i386 (375.82-6) ...
Processing triggers for glx-alternative-nvidia (0.8.0) ...
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for update-glx (0.8.0) ...
Processing triggers for glx-alternative-nvidia (0.8.0) ...
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-1-amd64
Errors were encountered while processing:
 libgles1-glvnd-nvidia:amd64
 libgles1-glvnd-nvidia:i386
 libgles-nvidia1:amd64
 libgles-nvidia1:i386
[...]
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of
libgles1-glvnd-nvidia:amd64:
 libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
unpacked but not configured.
  libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:amd64 (--configure):
 dependency problems - leaving 

Processed: Re: munin-c: FTBFS: threads.c:62:30: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 250 [-Werror=format-truncation=]

[Debian Bug Tracking System]

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

> package src:munin-c
Limiting to bugs with field 'package' containing at least one of 'src:munin-c'
Limit currently set to 'package':'src:munin-c'

> tags 871108 + confirmed fixed-upstream
Bug #871108 [src:munin-c] munin-c: FTBFS: threads.c:62:30: error: '%s' 
directive output may be truncated writing up to 255 bytes into a region of size 
250 [-Werror=format-truncation=]
Added tag(s) fixed-upstream and confirmed.
> thanks
Stopping processing here.

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

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

[Andreas Beckmann]

On 10/26/2017 11:13 PM, Rafał Olejnik wrote:
> Guess having amd64 and i386 might be a reason because on my sid i'm
> getting same error.

having both :amd64 and :i386 packages installed does not seem to work
properly with versioned Provides/Breaks in this special case.

minimal testcase is libgles1-glvnd-nvidia:amd64 +
libgles1-glvnd-nvidia:i386 in a minimal chroot (without
--install-recommends) that gets upgraded from buster to sid.

workaround should be

dpkg -r libgles1-glvnd-nvidia:amd64 libgles1-glvnd-nvidia:i386

(the mesa packages already dropped GLESv1 support)


Andreas

Bug#871108: munin-c: FTBFS: threads.c:62:30: error: '%s' directive output may be truncated writing up to 255 bytes into a region of size 250 [-Werror=format-truncation=]

[Matthias Schmitz]

package munin-c
tags 871108 + confirmed fixed-upstream
thanks


On Sun, 6 Aug 2017 17:31:20 -0400 Lucas Nussbaum 
wrote:
> Source: munin-c
> Version: 0.0.9-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170805 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks for the report. The issue is already fixed upstream. I'll check
if upstream releases a new version soon and if not i'll add a patch to
the actual package. 

Best wishes,
Matthias


pgp6DN_IRtND6.pgp
Description: Digitale Signatur von OpenPGP

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

[Rafał Olejnik]

On Thu, 26 Oct 2017 21:57:40 +0100 Luca Boccassi  wrote:
> On Thu, 2017-10-26 at 12:55 +0200, Vincent Lefevre wrote:
> > Package: libgles1-glvnd-nvidia
> > Version: 375.82-6
> > Severity: grave
> > Justification: renders package unusable
> >
> > In the upgrade to 375.82-6:
> >
> > Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
> > Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb ...
> > Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
> > Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-6_i386.deb
> > ...
> > Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5) ...
> > Processing triggers for mime-support (3.60) ...
> > Setting up libnvidia-eglcore:amd64 (375.82-6) ...
> > Setting up libnvidia-eglcore:i386 (375.82-6) ...
> > Processing triggers for desktop-file-utils (0.23-2) ...
> > Setting up libnvidia-glcore:amd64 (375.82-6) ...
> > Setting up libnvidia-glcore:i386 (375.82-6) ...
> > Processing triggers for libc-bin (2.24-17) ...
> > Setting up nvidia-egl-common (375.82-6) ...
> > Setting up nvidia-vulkan-common (375.82-6) ...
> > Setting up nvidia-legacy-check (375.82-6) ...
> > Processing triggers for man-db (2.7.6.1-2) ...
> > Setting up nvidia-alternative (375.82-6) ...
> > Processing triggers for nvidia-alternative (375.82-6) ...
> > Setting up libglx-nvidia0:amd64 (375.82-6) ...
> > Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
> > Setting up nvidia-kernel-support (375.82-6) ...
> > Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
> > Setting up libegl-nvidia0:amd64 (375.82-6) ...
> > Setting up libegl-nvidia0:i386 (375.82-6) ...
> > Setting up libgles-nvidia2:i386 (375.82-6) ...
> > Setting up libgles-nvidia2:amd64 (375.82-6) ...
> > Setting up libnvidia-cfg1:amd64 (375.82-6) ...
> > Setting up libnvidia-cfg1:i386 (375.82-6) ...
> > dpkg: dependency problems prevent configuration of libgles1-glvnd-
> > nvidia:amd64:
> >  libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
> > unpacked but not configured.
> >   libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.
> >
> > dpkg: error processing package libgles1-glvnd-nvidia:amd64 (
> > --configure):
> >  dependency problems - leaving unconfigured
> > dpkg: dependency problems prevent configuration of libgles1-glvnd-
> > nvidia:i386:
> >  libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and is
> > unpacked but not configured.
> >   libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.
> >
> > dpkg: error processing package libgles1-glvnd-nvidia:i386 (
> > --configure):
> >  dependency problems - leaving unconfigured
> > Setting up nvidia-kernel-dkms (375.82-6) ...
> > [...]
> > Setting up libnvidia-ml1:amd64 (375.82-6) ...
> > dpkg: dependency problems prevent configuration of libgles-
> > nvidia1:amd64:

Guess having amd64 and i386 might be a reason because on my sid i'm 
getting same error.

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

[quentin . caillard]

Same bug here

dpkg: des problèmes de dépendances empêchent la configuration de
libgles1-glvnd-nvidia:i386 :
 libgles1-glvnd-nvidia:amd64 (375.82-6) casse libgles1 (>> 0) et est
dépaqueté mais non configuré.
libgles1-glvnd-nvidia:i386 (375.82-6) fournit libgles1.

dpkg: erreur de traitement du paquet libgles1-glvnd-nvidia:i386 (
--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de
libgles1-glvnd-nvidia:amd64 :
 libgles1-glvnd-nvidia:i386 (375.82-6) casse libgles1 (>> 0) et est
dépaqueté mais non configuré.
libgles1-glvnd-nvidia:amd64 (375.82-6) fournit libgles1.

dpkg: erreur de traitement du paquet libgles1-glvnd-nvidia:amd64 (
--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de
libgles-nvidia1:i386 :
 libgles-nvidia1:i386 dépend de libgles1 (>= 0.2.999) | libgles1-glvnd-
nvidia ; cependant :
  Le paquet libgles1-glvnd-nvidia:i386 qui fournit libgles1 n'est pas
encore configuré.
 Le paquet libgles1-glvnd-nvidia:i386 n'est pas encore configuré.

dpkg: erreur de traitement du paquet libgles-nvidia1:i386 (
--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de
libgles-nvidia1:amd64 :
 libgles-nvidia1:amd64 dépend de libgles1 (>= 0.2.999) | libgles1-
glvnd-nvidia ; cependant :
  Le paquet libgles1 n'est pas installé.
  Le paquet libgles1-glvnd-nvidia:amd64 qui fournit libgles1 n'est pas
encore configuré.
 Le paquet libgles1-glvnd-nvidia:amd64 n'est pas encore configuré.

dpkg: erreur de traitement du paquet libgles-nvidia1:amd64 (
--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 libgles1-glvnd-nvidia:i386
 libgles1-glvnd-nvidia:amd64
 libgles-nvidia1:i386
 libgles-nvidia1:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have i386 packages installed.

On Thu, 26 Oct 2017 21:57:40 +0100 Luca Boccassi 
wrote:
> On Thu, 2017-10-26 at 12:55 +0200, Vincent Lefevre wrote:
> > Package: libgles1-glvnd-nvidia
> > Version: 375.82-6
> > Severity: grave
> > Justification: renders package unusable
> > 
> > In the upgrade to 375.82-6:
> > 
> > Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
> > Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb
...
> > Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
> > Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-
6_i386.deb
> > ...
> > Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5)
...
> > Processing triggers for mime-support (3.60) ...
> > Setting up libnvidia-eglcore:amd64 (375.82-6) ...
> > Setting up libnvidia-eglcore:i386 (375.82-6) ...
> > Processing triggers for desktop-file-utils (0.23-2) ...
> > Setting up libnvidia-glcore:amd64 (375.82-6) ...
> > Setting up libnvidia-glcore:i386 (375.82-6) ...
> > Processing triggers for libc-bin (2.24-17) ...
> > Setting up nvidia-egl-common (375.82-6) ...
> > Setting up nvidia-vulkan-common (375.82-6) ...
> > Setting up nvidia-legacy-check (375.82-6) ...
> > Processing triggers for man-db (2.7.6.1-2) ...
> > Setting up nvidia-alternative (375.82-6) ...
> > Processing triggers for nvidia-alternative (375.82-6) ...
> > Setting up libglx-nvidia0:amd64 (375.82-6) ...
> > Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
> > Setting up nvidia-kernel-support (375.82-6) ...
> > Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
> > Setting up libegl-nvidia0:amd64 (375.82-6) ...
> > Setting up libegl-nvidia0:i386 (375.82-6) ...
> > Setting up libgles-nvidia2:i386 (375.82-6) ...
> > Setting up libgles-nvidia2:amd64 (375.82-6) ...
> > Setting up libnvidia-cfg1:amd64 (375.82-6) ...
> > Setting up libnvidia-cfg1:i386 (375.82-6) ...
> > dpkg: dependency problems prevent configuration of libgles1-glvnd-
> > nvidia:amd64:
> >  libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and
is
> > unpacked but not configured.
> >   libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.
> > 
> > dpkg: error processing package libgles1-glvnd-nvidia:amd64 (
> > --configure):
> >  dependency problems - leaving unconfigured
> > dpkg: dependency problems prevent configuration of libgles1-glvnd-
> > nvidia:i386:
> >  libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and
is
> > unpacked but not configured.
> >   libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.
> > 
> > dpkg: error processing package libgles1-glvnd-nvidia:i386 (
> > --configure):
> >  dependency problems - leaving unconfigured
> > Setting up nvidia-kernel-dkms (375.82-6) ...
> > [...]
> > Setting up libnvidia-ml1:amd64 (375.82-6) ...
> > dpkg: dependency problems prevent configuration of libgles-
> > nvidia1:amd64:

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

[Luca Boccassi]

On Thu, 2017-10-26 at 12:55 +0200, Vincent Lefevre wrote:
> Package: libgles1-glvnd-nvidia
> Version: 375.82-6
> Severity: grave
> Justification: renders package unusable
> 
> In the upgrade to 375.82-6:
> 
> Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
> Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb ...
> Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
> Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-6_i386.deb
> ...
> Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5) ...
> Processing triggers for mime-support (3.60) ...
> Setting up libnvidia-eglcore:amd64 (375.82-6) ...
> Setting up libnvidia-eglcore:i386 (375.82-6) ...
> Processing triggers for desktop-file-utils (0.23-2) ...
> Setting up libnvidia-glcore:amd64 (375.82-6) ...
> Setting up libnvidia-glcore:i386 (375.82-6) ...
> Processing triggers for libc-bin (2.24-17) ...
> Setting up nvidia-egl-common (375.82-6) ...
> Setting up nvidia-vulkan-common (375.82-6) ...
> Setting up nvidia-legacy-check (375.82-6) ...
> Processing triggers for man-db (2.7.6.1-2) ...
> Setting up nvidia-alternative (375.82-6) ...
> Processing triggers for nvidia-alternative (375.82-6) ...
> Setting up libglx-nvidia0:amd64 (375.82-6) ...
> Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
> Setting up nvidia-kernel-support (375.82-6) ...
> Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
> Setting up libegl-nvidia0:amd64 (375.82-6) ...
> Setting up libegl-nvidia0:i386 (375.82-6) ...
> Setting up libgles-nvidia2:i386 (375.82-6) ...
> Setting up libgles-nvidia2:amd64 (375.82-6) ...
> Setting up libnvidia-cfg1:amd64 (375.82-6) ...
> Setting up libnvidia-cfg1:i386 (375.82-6) ...
> dpkg: dependency problems prevent configuration of libgles1-glvnd-
> nvidia:amd64:
>  libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
> unpacked but not configured.
>   libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.
> 
> dpkg: error processing package libgles1-glvnd-nvidia:amd64 (
> --configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of libgles1-glvnd-
> nvidia:i386:
>  libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and is
> unpacked but not configured.
>   libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.
> 
> dpkg: error processing package libgles1-glvnd-nvidia:i386 (
> --configure):
>  dependency problems - leaving unconfigured
> Setting up nvidia-kernel-dkms (375.82-6) ...
> [...]
> Setting up libnvidia-ml1:amd64 (375.82-6) ...
> dpkg: dependency problems prevent configuration of libgles-
> nvidia1:amd64:
>  libgles-nvidia1:amd64 depends on libgles1 (>= 0.2.999) | libgles1-
> glvnd-nvidia; however:
>   Package libgles1 is not installed.
>   Package libgles1-glvnd-nvidia:amd64 which provides libgles1 is not
> configured yet.
>   Package libgles1-glvnd-nvidia:amd64 is not configured yet.
> 
> dpkg: error processing package libgles-nvidia1:amd64 (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of libgles-
> nvidia1:i386:
>  libgles-nvidia1:i386 depends on libgles1 (>= 0.2.999) | libgles1-
> glvnd-nvidia; however:
>   Package libgles1-glvnd-nvidia:i386 which provides libgles1 is not
> configured yet.
>   Package libgles1-glvnd-nvidia:i386 is not configured yet.
> 
> dpkg: error processing package libgles-nvidia1:i386 (--configure):
>  dependency problems - leaving unconfigured
> Setting up libgl1-nvidia-glvnd-glx:amd64 (375.82-6) ...
> Setting up xserver-xorg-video-nvidia (375.82-6) ...
> Setting up nvidia-driver-bin (375.82-6) ...
> Setting up libglx-nvidia0:i386 (375.82-6) ...
> Setting up nvidia-vulkan-icd:i386 (375.82-6) ...
> Setting up nvidia-egl-icd:i386 (375.82-6) ...
> Setting up nvidia-egl-icd:amd64 (375.82-6) ...
> Setting up libgl1-nvidia-glvnd-glx:i386 (375.82-6) ...
> Setting up nvidia-driver-libs:amd64 (375.82-6) ...
> Setting up nvidia-driver-libs:i386 (375.82-6) ...
> Setting up nvidia-driver (375.82-6) ...
> Setting up nvidia-driver-libs-i386:i386 (375.82-6) ...
> Processing triggers for glx-alternative-nvidia (0.8.0) ...
> Processing triggers for libc-bin (2.24-17) ...
> Processing triggers for update-glx (0.8.0) ...
> Processing triggers for glx-alternative-nvidia (0.8.0) ...
> Processing triggers for libc-bin (2.24-17) ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.13.0-1-amd64
> Errors were encountered while processing:
>  libgles1-glvnd-nvidia:amd64
>  libgles1-glvnd-nvidia:i386
>  libgles-nvidia1:amd64
>  libgles-nvidia1:i386
> [...]
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> dpkg: dependency problems prevent configuration of libgles1-glvnd-
> nvidia:amd64:
>  libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is
> unpacked but not configured.
>   libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.
> 
> dpkg: error processing package 

Processed: tagging 841250, tagging 872040, found 879002 in 1.4-2, tagging 879002, tagging 879733, tagging 879734 ...

[Debian Bug Tracking System]

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

> tags 841250 + sid buster
Bug #841250 {Done: Mathieu Parent } [src:php-facedetect] 
php-facedetect: FTBFS: error with opencv 3.1
Added tag(s) sid and buster.
> tags 872040 + sid buster
Bug #872040 {Done: Thorsten Alteholz } [src:duktape] 
duktape: please ship a duktape library
Added tag(s) sid and buster.
> found 879002 1.4-2
Bug #879002 [src:libpam4j] Should the package be removed?
Marked as found in versions libpam4j/1.4-2.
> tags 879002 + sid buster
Bug #879002 [src:libpam4j] Should the package be removed?
Added tag(s) sid and buster.
> tags 879733 + sid buster
Bug #879733 [libemail-sender-transport-smtp-tls-perl] Deprecated upstream; 
Email::Sender::Transport::SMTP is a replacement
Added tag(s) sid and buster.
> tags 879734 + sid buster
Bug #879734 [libemail-sender-transport-smtps-perl] deprecated upstream; drop-in 
replacement exists
Added tag(s) sid and buster.
> tags 879827 + sid
Bug #879827 [libcommon-sense-perl] libcommon-sense-perl is no longer 
installable with perl 5.26.1-2
Added tag(s) sid.
> found 879827 3.74-2
Bug #879827 [libcommon-sense-perl] libcommon-sense-perl is no longer 
installable with perl 5.26.1-2
Marked as found in versions libcommon-sense-perl/3.74-2.
> thanks
Stopping processing here.

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

Bug#879878: marked as done (libgeronimo-validation-1.1-spec-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libgeronimo-validation-1.0-spec-java/api/allclasses-frame.htm

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 19:49:02 +
with message-id 
and subject line Bug#879878: fixed in geronimo-validation-1.1-spec 1.0-2
has caused the Debian Bug report #879878,
regarding libgeronimo-validation-1.1-spec-java-doc: fails to upgrade from 
'stretch' - trying to overwrite 
/usr/share/doc/libgeronimo-validation-1.0-spec-java/api/allclasses-frame.html
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.)


-- 
879878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgeronimo-validation-1.1-spec-java-doc
Version: 1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package 
libgeronimo-validation-1.1-spec-java-doc.
  Preparing to unpack 
.../libgeronimo-validation-1.1-spec-java-doc_1.0-1_all.deb ...
  Unpacking libgeronimo-validation-1.1-spec-java-doc (1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgeronimo-validation-1.1-spec-java-doc_1.0-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/libgeronimo-validation-1.0-spec-java/api/allclasses-frame.html',
 which is also in package libgeronimo-validation-1.0-spec-java-doc 1.1-2
  Errors were encountered while processing:
   
/var/cache/apt/archives/libgeronimo-validation-1.1-spec-java-doc_1.0-1_all.deb


Looks like the files are installed in the wrong path ...


cheers,

Andreas


libgeronimo-validation-1.0-spec-java-doc=1.1-2_libgeronimo-validation-1.1-spec-java-doc=1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: geronimo-validation-1.1-spec
Source-Version: 1.0-2

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
geronimo-validation-1.1-spec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Oct 2017 21:33:17 +0200
Source: geronimo-validation-1.1-spec
Binary: libgeronimo-validation-1.1-spec-java 
libgeronimo-validation-1.1-spec-java-doc
Architecture: source
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libgeronimo-validation-1.1-spec-java - Geronimo JSR-349 Bean Validation Spec 
API
 libgeronimo-validation-1.1-spec-java-doc - Documentation for 
libgeronimo-validation-1.1-spec-java
Closes: 879878
Changes:
 geronimo-validation-1.1-spec (1.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the install path of the javadoc (Closes: #879878)
   * Standards-Version updated to 4.1.1
Checksums-Sha1:
 6e208bac3c7b90aa6e7a2f744703f91cd26a9f0d 2428 
geronimo-validation-1.1-spec_1.0-2.dsc
 c0b41c11ec7fa4a9672bdadcb89e7cf502cb3da9 3440 
geronimo-validation-1.1-spec_1.0-2.debian.tar.xz
 ce72af7a9ea0b2f0f0126041df50610f4ca93692 15578 
geronimo-validation-1.1-spec_1.0-2_source.buildinfo
Checksums-Sha256:
 fc650f2c089094e12a0bb654d0fcd4b178eaa893db573c978fd5ce3871e83eba 2428 
geronimo-validation-1.1-spec_1.0-2.dsc
 865cfd25119a576953568fe3fd4b805d60e60354868cf0631ecafcbc9bdee0cb 3440 
geronimo-validation-1.1-spec_1.0-2.debian.tar.xz
 85e3ebce63b926fa59c67c3fa4d615c5043a62b11507ed7632ad15ecdda9444f 15578 
geronimo-validation-1.1-spec_1.0-2_source.buildinfo
Files:
 a7eac48381859089fb7710eae410ac09 2428 java optional 
geronimo-validation-1.1-spec_1.0-2.dsc
 e0cae38f27e3d820b1e68876382191e6 3440 java optional 
geronimo-validation-1.1-spec_1.0-2.debian.tar.xz
 

Bug#871964: marked as done (swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 19:49:48 +
with message-id 
and subject line Bug#871964: fixed in swt-gtk 3.8.2-4.1
has caused the Debian Bug report #871964,
regarding swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated
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.)


-- 
871964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swt-gtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

swt-gtk Build-Depends on libwebkitgtk-dev, which is deprecated in favor of
libwebkit2gtk-4.0-dev (provided in Debian by webkit2gtk). Please drop
this Build-Depends so that we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

The package does build successfully without the libwebkitgtk-dev
build-dependency.

It feels to me like the libswt-webkit-gtk-3-jni was already broken
since it doesn't have a dependency on any webkitgtk library (I think
the correct one would be libwebkitgtk-3.0-0 but that is still part of
the deprecated libraries which are being removed.)

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: swt-gtk
Source-Version: 3.8.2-4.1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated swt-gtk 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, 24 Oct 2017 15:18:42 -0400
Source: swt-gtk
Binary: libswt-gtk-3-java libswt-gtk-3-jni libswt-gnome-gtk-3-jni 
libswt-cairo-gtk-3-jni libswt-glx-gtk-3-jni libswt-webkit-gtk-3-jni
Architecture: source
Version: 3.8.2-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Jeremy Bicha 
Description:
 libswt-cairo-gtk-3-jni - Standard Widget Toolkit for GTK+ Cairo JNI library
 libswt-glx-gtk-3-jni - Standard Widget Toolkit for GTK+ GLX JNI library
 libswt-gnome-gtk-3-jni - Standard Widget Toolkit for GTK+ GNOME JNI library
 libswt-gtk-3-java - Standard Widget Toolkit for GTK+ Java library
 libswt-gtk-3-jni - Standard Widget Toolkit for GTK+ JNI library
 libswt-webkit-gtk-3-jni - Standard Widget Toolkit for GTK+ WebKit JNI library
Closes: 871964
Changes:
 swt-gtk (3.8.2-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop unnecessary Build-Depends on libwebkitgtk-dev (Closes: #871964)
Checksums-Sha1:
 9ad1e0dcd84a30d541034b912bb591f2c8d25e24 2633 swt-gtk_3.8.2-4.1.dsc
 4abe0d160b95044cc9a4326a33564bc87824b726 263428 swt-gtk_3.8.2-4.1.debian.tar.xz
 ff5b7b16cc4b6caebd59f83258a4982b8b285115 7872 
swt-gtk_3.8.2-4.1_source.buildinfo
Checksums-Sha256:
 9edd450b042525b182ed4a6a4ad38734d10b352306e76cdda0b03772f594a159 2633 
swt-gtk_3.8.2-4.1.dsc
 dcde87980ffa0226d3afe6ee4490b1effed7da3bc3d8ced3559248778c58c8a0 263428 
swt-gtk_3.8.2-4.1.debian.tar.xz
 80cec7bf43754c425bff40e5ab37a83ae5271229388e99e69bfd61af6b6b59f2 7872 
swt-gtk_3.8.2-4.1_source.buildinfo
Files:
 7dcda967e98dbf69e4cf7b7ac278cbd3 2633 libs optional swt-gtk_3.8.2-4.1.dsc
 7f8ccf39ef9c57c133c9952f44714f2b 263428 libs optional 
swt-gtk_3.8.2-4.1.debian.tar.xz
 4e5300570c8a4f92682e9b196ac349fc 7872 libs optional 
swt-gtk_3.8.2-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZ75P4AAoJEOZsd1rr/mx9IpMP/2XK4rvK0kEn84c+4E9cxXhf
yzKxBBO5QB/DTPMj1tI/BKJUR/R1ofPMBKM3OAW2/0fb1RBdR4fBh/DIOJZtic4s
X2x1tSP/sDt96ZAiK5kxa+6fQHRLEGIzQNhmrIbXk7mKwjfdUgVkWLU4Fl/ffOgR
j4LbEYI8kJXAsZ+wogPhzch77AzAHVGYKmJol2H9Too6SiSaIGf7L/FtbFBS610K
nraRkkkDXuhsMuD2a4ZSQRQlrCew88tNyysn1H2lTui0AWeHRMrHSW5B0zEZxw6O

Bug#879886: [Debian-med-packaging] Bug#879886: libhts2: libhts2 needs to handle ABI changes

[Mattia Rizzolo]

On Thu, Oct 26, 2017 at 12:12:05PM -0700, Diane Trout wrote:
> libhts2 introduced an ABI change which broke python-pysam, and a new
> version of python-pysam needed to be released to update to the new ABI.

FTR, this is what changed between the symbols of the version 1.4.1-5 and
1.5-1:

--- 1.4.1-5
+++ dpkg-gensymbolsIEaASY
@@ -178,6 +178,7 @@
  bgzf_flush_try@Base 1.4.1
  bgzf_getc@Base 1.4.1
  bgzf_getline@Base 1.4.1
+ bgzf_hfile@Base 1.5
  bgzf_hopen@Base 1.4.1
  bgzf_index_add_block@Base 1.4.1
  bgzf_index_build_init@Base 1.4.1
@@ -395,7 +396,7 @@
  file_size@Base 1.4.1
  find_file_url@Base 1.4.1
  find_path@Base 1.4.1
- flen@Base 1.4.1
+#MISSING: 1.5# flen@Base 1.4.1
  grp_create_key@Base 1.4.1
  hclose@Base 1.4.1
  hclose_abruptly@Base 1.4.1
@@ -411,6 +412,7 @@
  hfile_plugin_init_libcurl@Base 1.4.1
  hfile_plugin_init_net@Base 1.4.1
  hfile_plugin_init_s3@Base 1.4.1
+ hfile_set_blksize@Base 1.5
  hflush@Base 1.4.1
  hgetc2@Base 1.4.1
  hgetdelim@Base 1.4.1
@@ -436,6 +438,7 @@
  hts_format_file_extension@Base 1.4.1
  hts_get_bgzfp@Base 1.4.1
  hts_get_format@Base 1.4.1
+ hts_get_log_level@Base 1.5
  hts_getline@Base 1.4.1
  hts_hopen@Base 1.4.1
  hts_idx_destroy@Base 1.4.1
@@ -460,6 +463,7 @@
  hts_json_fskip_value@Base 1.4.1
  hts_json_snext@Base 1.4.1
  hts_json_sskip_value@Base 1.4.1
+ hts_log@Base 1.5
  hts_md5_destroy@Base 1.4.1
  hts_md5_final@Base 1.4.1
  hts_md5_hex@Base 1.4.1
@@ -480,6 +484,7 @@
  hts_realloc_or_die@Base 1.4.1
  hts_set_cache_size@Base 1.4.1
  hts_set_fai_filename@Base 1.4.1
+ hts_set_log_level@Base 1.5
  hts_set_opt@Base 1.4.1
  hts_set_thread_pool@Base 1.4.1
  hts_set_threads@Base 1.4.1
@@ -588,7 +593,7 @@
  mfgets@Base 1.4.1
  mfmmap@Base 1.4.1
  mfopen@Base 1.4.1
- mfprintf@Base 1.4.1
+#MISSING: 1.5# mfprintf@Base 1.4.1
  mfread@Base 1.4.1
  mfrecreate@Base 1.4.1
  mfreopen@Base 1.4.1
@@ -704,13 +709,13 @@
  vcf_read@Base 1.4.1
  vcf_write@Base 1.4.1
  vcf_write_line@Base 1.4.1
- vflen@Base 1.4.1
- zfclose@Base 1.4.1
- zfeof@Base 1.4.1
- zfgets@Base 1.4.1
- zfopen@Base 1.4.1
- zfpeek@Base 1.4.1
- zfputs@Base 1.4.1
- zfseeko@Base 1.4.1
- zftello@Base 1.4.1
+#MISSING: 1.5# vflen@Base 1.4.1
+#MISSING: 1.5# zfclose@Base 1.4.1
+#MISSING: 1.5# zfeof@Base 1.4.1
+#MISSING: 1.5# zfgets@Base 1.4.1
+#MISSING: 1.5# zfopen@Base 1.4.1
+#MISSING: 1.5# zfpeek@Base 1.4.1
+#MISSING: 1.5# zfputs@Base 1.4.1
+#MISSING: 1.5# zfseeko@Base 1.4.1
+#MISSING: 1.5# zftello@Base 1.4.1
  zlib_mem_inflate@Base 1.4.1

> libhts2 probably needs a proper symbols file to make it easier to see
> when the ABI is changing. https://wiki.debian.org/UsingSymbolsFiles
> 
> Mattia Rizzolo, also suggests other methods of dealing with managing ABI
> changes.

In pysam's case, it is looking for hts_log, if you had properly checked
the symbols of your package before uploading you should have at least
tweaked the dh_shlibdeps invocation to force a version, or introduced a
.symbols file (very recommended for a case like hstlib where the symbols
seems to be simple).

But then, the ABI is broken, so just nicest symbols handling is not
enough for your case, you need
> Such as bumping soname, changing the package name and use Conflicts, or
> adding versioned Breaks against broken packages

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: Pending fixes for bugs in the geronimo-validation-1.1-spec package

[Debian Bug Tracking System]

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

> tag 879878 + pending
Bug #879878 [libgeronimo-validation-1.1-spec-java-doc] 
libgeronimo-validation-1.1-spec-java-doc: fails to upgrade from 'stretch' - 
trying to overwrite 
/usr/share/doc/libgeronimo-validation-1.0-spec-java/api/allclasses-frame.html
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#879878: Pending fixes for bugs in the geronimo-validation-1.1-spec package

[pkg-java-maintainers]

tag 879878 + pending
thanks

Some bugs in the geronimo-validation-1.1-spec package are closed in
revision fcc08dc6c2f45a876c89bd15d76c120a6de14ac3 in branch 'master'
by Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/geronimo-validation-1.1-spec.git/commit/?id=fcc08dc

Commit message:

Fixed the install path of the javadoc (Closes: #879878)

Bug#867058: golang-1.8 and mips*

[John Paul Adrian Glaubitz]

On 10/26/2017 07:12 PM, peter green wrote:
> Therefore golang maintainers you have two choices.
> 
> 1. Accept John's changes so that your package can be built on mips*.
> 2. File a removal request for the binaries uploaded by John

I assume that gccgo on mips is still broken as this situation hasn't changed,
so I would suggest removing the packages again. I can file a bug for that
since I am the one who is responsible that these packages are there in the
first place.

>> > I was under the impression that the golang maintainers want all 
>> > architectures
>> > bootstrapped from gccgo? This was the reason mips64el support was not in 
>> > stretch despite upstream support for it. If a normal bootstrap would have 
>> > been acceptable,
>> > I would have done it ages ago.
>>
>> Why? What difference does it make? If a different bootstrapping compiler
>> results in a different golang compiler after a second rebuild, there is
>> something wrong with the compiler anyway.
> Self-bootstrapping compilers create a maintenance burden. When things go
> wrong they sometimes can't be fixed through source package changes alone.

Correct me if I'm wrong, but most compilers I know of in Debian are self-
bootstrapping. I recently started working on rustc and that one needs itself
to be built, the same applies for fpc - which you co-maintain - GHC, and 
OpenJDK,
for example. So, I am confident to say that the build system for the golang
packages is not the norm but an exception.

Also, since gccgo is apparently known to produce broken code, I am not sure
I would consider it a good idea to use it as the compiler to build the golang
packages.

> Porterboxes are also of limited utility because you can't install non-archive
> packages on them.

That's correct. But you are forgetting that there is the possibility that
compilers can be cross-compiled on amd64 and for most compilers, that
works pretty well. In fact, there are efforts by people like Helmut Grohne,
whom I support in this effort, to make Debian as a whole more cross-buildable.

> Then there are derivatives to consider, if a self-bootstrapping compiler
> gets broken in a derivative that rebuilds everything then finding someone
> who can un-jam it can be a pain.

I'm not really sure whether I want to accept this argument. I am developing
for Debian and in Debian and I don't see why my work should be limited by
any derivative.

> Whether to take on that burden should be a decision for the maintainers of
> the package, not for some flyby contributer.

That "flyby contributor" you are talking about is maintaining most ports
architectures and has already fixed tons of issues on the various architectures
in Debian. So while I sometimes make mistakes like these, my net contributions
to Debian are hugely positive.

And, as we say in German, "Wo gehobelt wird, da fallen Späne" or, as you
would say in English, "You can't make an omelette without breaking eggs".

In short, if you are touching lots of things in Debian and helping out
at many fronts, you will make such mistakes from time to time. I admit
it was a mistake and I apologize for that. But that still doesn't give
you the right to call me a "flyby contributor".

>> Odd. Last time I did this for fpc [1], you were actually very happy. Now
>> you're getting upset despite the only changes actually necessary are
>> two lines changed in debian/control.in and debian/helpers/goenv.sh.
>>
>> What's the difference now?
> 
> We are happy that you are working on getting packages ported to your 
> architecture.

Who is "we"?

> What we are not happy about is how you are doing it. You need to ensure
> that source goes to the archive either before or at the same time as the 
> binaries and
> you need to either coordinate with maintainers or (if the maintainers are 
> unresponsive)
> follow the normal NMU guidelines.

If it wasn't for me, FPC would still probably not bootstrapped on mips* and m68k
yet and FPC upstream wouldn't have had the possibility to work on the SPARC64
port which they did on hardware that I helped to provide. Again, I am doing so
much for Debian, that I find it a bit unfair that you are preaching me like 
this.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: severity of 879886 is serious

[Debian Bug Tracking System]

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

> severity 879886 serious
Bug #879886 [libhts2] libhts2: libhts2 needs to handle ABI changes
Severity set to 'serious' from 'critical'
> thanks
Stopping processing here.

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

Bug#879762: marked as done (debhelper: fails to parse debian/control files with leading blank lines)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 19:18:53 +
with message-id 
and subject line Bug#879762: fixed in debhelper 10.10.5
has caused the Debian Bug report #879762,
regarding debhelper: fails to parse debian/control files with leading blank 
lines
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.)


-- 
879762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debhelper
Version: 10.10
Severity: serious
Control: found -1 10.10.4

Hi,

As of debhelper 10.10, debhelper cannot parse debian/control files with
blank lines before the first paragraph. I originally noticed this when
attemping (and failing) to build golang-1.9 which has a comment at the
top of its debian/control file.

Example running on the debhelper source itself:

$ sed -i '1i\\' debian/control
$ dpkg-buildpackage -T clean
dpkg-buildpackage: info: source package debhelper
dpkg-buildpackage: info: source version 10.10.4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Niels Thykier 
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
./run dh clean --without autoreconf --with build-stamp
dh: could not find Source: line in control file.
debian/rules:13: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2

I bisected it to this commit:
commit 087be1a300581b989aa38227693a8a6f112408f9 (refs/bisect/bad)
Author: Niels Thykier 
Date:   Sat Sep 16 14:51:53 2017 +

Add minimal R³ support for debhelper

Signed-off-by: Niels Thykier 

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 10.10.5

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

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

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Oct 2017 19:10:51 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 10.10.5
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 879762
Changes:
 debhelper (10.10.5) unstable; urgency=medium
 .
   * meson.pm: Add missing import of generated_file that broke
 cross building.
   * Dh_Lib: Fix regression where an empty line before the source
 paragraph in d/control would cause parse error.
 (Closes: #879762)
Checksums-Sha1:
 ec13d1406e9ab7dd7f2cb2ce5ac2a3fe63d13cf5 1795 debhelper_10.10.5.dsc
 afd3c5f0a6240f88912598dcd259771f91eee849 429752 debhelper_10.10.5.tar.xz
 cf5e328fbf8bfc41a1ad6279510c4e1eaf298daa 4506 
debhelper_10.10.5_source.buildinfo
Checksums-Sha256:
 be4459c2fdd80f007cd44f90b53f433d63169e2d6e42a1188074e35a88c3a1f9 1795 
debhelper_10.10.5.dsc
 930cb5bd922149e797a2b90c7bec55bf8c819b275698abdf52d8290bafd801c5 429752 
debhelper_10.10.5.tar.xz
 7b0b1e0659978ab81fb721a9cbfa801efc22e9563975c12180dbca481feb5463 4506 
debhelper_10.10.5_source.buildinfo
Files:
 7d3a04ce8c0fb343767d4630684ce1bc 1795 devel optional debhelper_10.10.5.dsc
 1e424737bbe2ff56742e71d1113e7117 429752 devel optional debhelper_10.10.5.tar.xz
 b5306cbe4aa13fb7644f243cec8ba2a6 4506 devel optional 
debhelper_10.10.5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlnyM+AACgkQBUu7n32A
ZEKw3g//Trs38EJLoYndZKT65x1I+/mzbk/dLIi5J2Q8PzwunZ1WW43nDKKu7Ia/
4GKCe4JxSS0E0zHtGleoRflEuxC8VYS21KSDH6968uxRyH3cy4bgyDA5pRNx9hI/
bRU4u2+o1ESSSTDdLY+tix/BU7oidPOcvDejUIzCmx4Ddir81ZGNPxHewJ/3P8h3
JK03EHhGDdvP9BC4obDlh6NTRfcjQr5jANtQ+/xTxcgsR1qY1Ty5IcRXejQnJ48T

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

[Diane Trout]

Package: libhts2
Version: 1.5-1
Severity: critical

Dear Maintainer,

libhts2 introduced an ABI change which broke python-pysam, and a new
version of python-pysam needed to be released to update to the new ABI.

libhts2 probably needs a proper symbols file to make it easier to see
when the ABI is changing. https://wiki.debian.org/UsingSymbolsFiles

Mattia Rizzolo, also suggests other methods of dealing with managing ABI
changes.

Such as bumping soname, changing the package name and use Conflicts, or
adding versioned Breaks against broken packages

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

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

Versions of packages libhts2 depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-17
ii  libcurl3-gnutls  7.55.1-1
ii  liblzma5 5.2.2-1.3
ii  libssl1.11.1.0f-5
ii  zlib1g   1:1.2.8.dfsg-5

libhts2 recommends no packages.

libhts2 suggests no packages.

-- no debconf information

Bug#879883: libx32stdc++6-8-dbg: missing Conflicts: libx32stdc++6-7-dbg

[Andreas Beckmann]

Package: libx32stdc++6-8-dbg
Version: 8-20171023-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi doko,

the last round of adding Conflicts seems to have missed this one:

  Selecting previously unselected package libx32stdc++6-8-dbg.
  Preparing to unpack .../15-libx32stdc++6-8-dbg_8-20171023-1_amd64.deb ...
  Unpacking libx32stdc++6-8-dbg (8-20171023-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ntuDRD/15-libx32stdc++6-8-dbg_8-20171023-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/libx32/debug/libstdc++.a', which is also in 
package libx32stdc++6-7-dbg 7.2.0-12
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ntuDRD/15-libx32stdc++6-8-dbg_8-20171023-1_amd64.deb


cheers,

Andreas

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

[Mattia Rizzolo]

On Wed, Oct 25, 2017 at 10:40:20PM -0600, Adam Conrad wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * test/test_mk-origtargz: Adjust test for dpkg 1.19's ErrorHandling.pm.
> 
> Fairly self-explanatory, I'd think.  In dpkg 1.19, ErrorHandling.pm was
> normalised to match libdpkg error messages, and this means the expected
> error in the mk-origtargz test is now incorrect.  This patch fixes that.

We like to backport devscripts, and I'd rather not have backports deltas
if possible...

But yes, a bug damn :)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

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

[Andreas Beckmann]

Package: flightgear
Version: 1:2017.3.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

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


cheers,

Andreas


metar=20061030.1-2.2+b1_flightgear=1%2017.3.1+dfsg-2.log.gz
Description: application/gzip

Processed: Bug#879814 in apt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 879814 pending
Bug #879814 [apt] apt: debian-installer FTBFS: missing syscalls for seccomp 
[mips,mipsel,ppc64el]
Added tag(s) pending.

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

Bug#879814: in apt marked as pending

[Julian Andres Klode]

Control: tag 879814 pending

Hello,

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

https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=b514128

(this message was generated automatically based on the git commit message)
---
commit b514128890d5cf96a76393e8d261d79e0be7f0e4
Author: Julian Andres Klode 
Date:   Thu Oct 26 17:42:58 2017 +0200

seccomp: Allow ipc() for fakeroot, and allow sysinfo() for sort

Sorting apparently calls sysconf() which calls sysinfo() to get
free pages or whatever.

Closes: #879814, #879826

Bug#879879: python3-monajat: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/locale/ar/LC_MESSAGES/monajat.mo

[Andreas Beckmann]

Package: python3-monajat
Version: 4.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Selecting previously unselected package python3-monajat.
  Preparing to unpack .../python3-monajat_4.1-1_all.deb ...
  Unpacking python3-monajat (4.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-monajat_4.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/monajat.mo', which is 
also in package python-monajat 2.6.5-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-monajat_4.1-1_all.deb


cheers,

Andreas


python-monajat=2.6.5-1_python3-monajat=4.1-1.log.gz
Description: application/gzip

Bug#879878: libgeronimo-validation-1.1-spec-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libgeronimo-validation-1.0-spec-java/api/allclasses-frame.html

[Andreas Beckmann]

Package: libgeronimo-validation-1.1-spec-java-doc
Version: 1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package 
libgeronimo-validation-1.1-spec-java-doc.
  Preparing to unpack 
.../libgeronimo-validation-1.1-spec-java-doc_1.0-1_all.deb ...
  Unpacking libgeronimo-validation-1.1-spec-java-doc (1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgeronimo-validation-1.1-spec-java-doc_1.0-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/libgeronimo-validation-1.0-spec-java/api/allclasses-frame.html',
 which is also in package libgeronimo-validation-1.0-spec-java-doc 1.1-2
  Errors were encountered while processing:
   
/var/cache/apt/archives/libgeronimo-validation-1.1-spec-java-doc_1.0-1_all.deb


Looks like the files are installed in the wrong path ...


cheers,

Andreas


libgeronimo-validation-1.0-spec-java-doc=1.1-2_libgeronimo-validation-1.1-spec-java-doc=1.0-1.log.gz
Description: application/gzip

Processed: limit source to debhelper, tagging 879762

[Debian Bug Tracking System]

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

> limit source debhelper
Limiting to bugs with field 'source' containing at least one of 'debhelper'
Limit currently set to 'source':'debhelper'

> tags 879762 + pending
Bug #879762 [src:debhelper] debhelper: fails to parse debian/control files with 
leading blank lines
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#879858: marked as done (duktape-dev: Dangling symlink to library)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 18:34:32 +
with message-id 
and subject line Bug#879858: fixed in duktape 2.2.0-2
has caused the Debian Bug report #879858,
regarding duktape-dev: Dangling symlink to library
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.)


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

duktape-dev has this symlink:

/usr/lib/libduktape.so -> libduktape.so.202

but libduktape202 ships this file (as seen in the i386 build)
/usr/lib/i386-linux-gnu/libduktape.so.202

https://buildd.debian.org/status/fetch.php?pkg=duktape=i386=2.2.0-1=1509011601

It looks like you need to make sure to use multi-arch for duktape-dev too.

I noticed this while trying to build edbrowse 3.7.1

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: duktape
Source-Version: 2.2.0-2

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated duktape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Oct 2017 19:23:21 +0200
Source: duktape
Binary: duktape duktape-dev libduktape202
Architecture: source amd64
Version: 2.2.0-2
Distribution: sid
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 duktape- embeddable Javascript engine
 duktape-dev - embeddable Javascript engine, development files
 libduktape202 - embeddable Javascript engine, library
Closes: 879858
Changes:
 duktape (2.2.0-2) unstable; urgency=medium
 .
   * add correct library link to dev-package (Closes: #879858)
Checksums-Sha1:
 24c6f4f5d135113a36a1e0df609707790df9114e 2199 duktape_2.2.0-2.dsc
 059d8f6ce4537bfca5689da693225802bb482706 969136 duktape_2.2.0.orig.tar.xz
 8142af7d2a536dd19d9ba8808e377027344be9b4 4740 duktape_2.2.0-2.debian.tar.xz
 4d8319633371aed4d553b7c4db12b05acfdc180f 419696 
duktape-dbgsym_2.2.0-2_amd64.deb
 20fb722eb45bc7a4483db229b17f692d482b5c5b 575880 duktape-dev_2.2.0-2_amd64.deb
 80bf582789c3fe62ff30e020528e00970a476c7f 6621 duktape_2.2.0-2_amd64.buildinfo
 432c6542a498d06e01dac5a5eb0a0afe15cf6a1e 123400 duktape_2.2.0-2_amd64.deb
 3f30b263f9c230a8a3a4a9c28d147d3f64af739b 13132 
libduktape202-dbgsym_2.2.0-2_amd64.deb
 cb824542f376b144805aa37adc701304cfac7f56 122276 libduktape202_2.2.0-2_amd64.deb
Checksums-Sha256:
 78b59a3f0384f34bf0ee99d1f732e3df7ca50c8ae48ff5b8afdcb5cc02398528 2199 
duktape_2.2.0-2.dsc
 62f72206427633077cb02e7ccd2599ace4d254db409334593b86d262c0d50c14 969136 
duktape_2.2.0.orig.tar.xz
 cef99f699add5044d4af713d3d8e6c34d1d8e701581a03e97817b036c74339aa 4740 
duktape_2.2.0-2.debian.tar.xz
 cdfe7e4e5e7cc7e166b3d22028722f6e698bc9737e0b5e463a4101651d442bce 419696 
duktape-dbgsym_2.2.0-2_amd64.deb
 21e46969d45ff32364adebfd4ce9f7f981bcee3925d23ae882505ba4b1ed857d 575880 
duktape-dev_2.2.0-2_amd64.deb
 a9883261e88797e2c6d780cb9601094daf2909cfb7a4048f646cc225805da5f0 6621 
duktape_2.2.0-2_amd64.buildinfo
 56007be4d5297a9db9c06925968cbe38549d3d543804efbb8007618f9b510cab 123400 
duktape_2.2.0-2_amd64.deb
 ed7d626f72459a30c8779fce770626873be8ad801d22a016dd96647d561e728d 13132 
libduktape202-dbgsym_2.2.0-2_amd64.deb
 e752954b88fc0b616e889bca134e6f5165390bb5d02eb7696da65f0ad521e384 122276 
libduktape202_2.2.0-2_amd64.deb
Files:
 e3f01c693583f715e1d570df059a2279 2199 interpreters optional duktape_2.2.0-2.dsc
 0f7c9fac5547f7f3fc1c671fc90b2ccf 969136 interpreters optional 
duktape_2.2.0.orig.tar.xz
 0ca7b0118e6393d6b14d53e43798ce57 4740 interpreters optional 
duktape_2.2.0-2.debian.tar.xz
 77e6db1449edf4bcdadaa6af3ba9515b 419696 debug optional 
duktape-dbgsym_2.2.0-2_amd64.deb
 9b5db7dd244ee3f2227c4d8793f1931c 575880 libdevel optional 
duktape-dev_2.2.0-2_amd64.deb
 a40b5bffa33aa22ca09604322ba79d12 6621 interpreters optional 

Processed: affects 841556

[Debian Bug Tracking System]

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

> affects 841556 src:kodi
Bug #841556 [src:libcdio] libcdio: ftbfs with GCC-7
Bug #841624 [src:libcdio] libcdio: ftbfs with GCC-7
Bug #853484 [src:libcdio] libcdio: ftbfs with GCC-7
Bug #853561 [src:libcdio] libcdio: ftbfs with GCC-7
Bug #853697 [src:libcdio] vcdimager: ftbfs with GCC-7
Bug #871121 [src:libcdio] mpd: FTBFS: iso9660.h:277:45: error: flexible array 
member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
Bug #871138 [src:libcdio] vcdimager: FTBFS: iso9660.h:277:45: error: flexible 
array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
Added indication that 841556 affects src:kodi
Added indication that 841624 affects src:kodi
Added indication that 853484 affects src:kodi
Added indication that 853561 affects src:kodi
Added indication that 853697 affects src:kodi
Added indication that 871121 affects src:kodi
Added indication that 871138 affects src:kodi
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
841556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841556
841624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841624
853484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853484
853561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853561
853697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853697
871121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871121
871138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871314: [Debian-med-packaging] Bug#871314: pysam 0.12 depends on libhts2 1.5

[Afif Elghraoui]

Hi, Diane,

On October 26, 2017 1:41:30 PM EDT, "Trout, Diane E."  wrote:
>The new version of pysam 0.12 requires libhts2 1.5.
>
>Unfortunately pysam 0.12 just migrated to testing, and libhts2 was
>blocked from migrating by this bug because it breaks pysam 0.11
>
>
Oh, yeah, that should be closed. There is a similar bug holding up samtools 1.5 
for the same reason that can also be closed. And bcftools 1.5 is held up for 
portability regressions on exotic architectures that nobody has time/interest 
for...

regards
Afif

Bug#871314: marked as done (htslib: new version break python-pysam)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 20:07:59 +0200
with message-id 

Bug#871315: marked as done (samtools: new version breaks python-pysam)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 20:07:59 +0200
with message-id 

Bug#871314: pysam 0.12 depends on libhts2 1.5

[Trout, Diane E.]

The new version of pysam 0.12 requires libhts2 1.5.

Unfortunately pysam 0.12 just migrated to testing, and libhts2 was
blocked from migrating by this bug because it breaks pysam 0.11


Diane

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

Bug#867588: buildbot: application fails at runtime requiring sqlalchemy-migrate==0.7.2

[José Carlos]

Bump. Any updates for this bug?

-- 
José Carlos Capurro
(595) 994 40 0144

Processed: Re: Bug#849832: icedove: contains JSHint work under non-free licence

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #849832 [icedove] firefox: contains JSHint work under non-free licence
Added tag(s) pending.

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

Bug#849832: icedove: contains JSHint work under non-free licence

[Carsten Schoenert]

Control: tags -1 pending

Dear FTP Team,

could you please remove the following as 'found in version' icedove
packages by Ben Finney and also the respectively source tarballs from
the archive?
As Ben pointed out the marked versions containing a non-free files and
thus the the source tarballs are not DFSG clean.
The affected versions are quite older now and a removal doesn't affect
existing user installations due the up2date security versions in all
releases.

On Tue, Apr 12, 2016 at 03:58:34PM +1000, Ben Finney wrote:

> Control: found -1 icedove/31.5.0-1~deb7u1
> Control: found -1 icedove/31.8.0-1~deb7u1
> Control: found -1 icedove/31.8.0-1~deb8u1
> Control: found -1 icedove/40.0~b1-1
> Control: found -1 icedove/42.0~b2-1

> 
> On 28-Jan-2016, Bastien ROUCARIES wrote:
> > mozilla/dom/system/gonk/tests/marionette/ril_jshint/jshint.js
> > 
> > is licenced under evil licence...
> 
> This is (not an identical copy, but clearly derived from) JSHint
> version 2.1.3 .
> 
> Receipients do not have free-software license in this work. The only
> license granted has the non-free “Good, not Evil” restriction.
> 
> > Please repack and notify archive.debian.org in order to remove old
> > package.
> 
> This same content is found (according to sources.debian.net) in:
> 
> * firefox
> * firefox-esr
> * iceweasel
> * icedove
> 
> 
> 
> Maintainer, should we make separate bug reports for each of those?

PS: Maybe this email comes as double to you (wrongly addressed to
#813054, that's the bug report for firefox-esr), bugs.debian.org was a
bit 'tenacious' yesterday.
I already have written yesterday a email to the BTS but I haven't got a
feedback mail from the system about processing.

Regards and thanks!
Carsten

Processed: Needs node-get-func-name currently in NEW

[Debian Bug Tracking System]

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

> block 872533 by 879782
Bug #872533 [src:node-chai] node-chai FTBFS with nodejs 6.11.2
872533 was not blocked by any bugs.
872533 was not blocking any bugs.
Added blocking bug(s) of 872533: 879782
>
End of message, stopping processing here.

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

Processed: block 879867 with 871314

[Debian Bug Tracking System]

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

> block 879867 with 871314
Bug #879867 [python3-pysam] python3-pysam: import pysam throws ImportError 
undefined symbol: hts_log
879867 was not blocked by any bugs.
879867 was not blocking any bugs.
Added blocking bug(s) of 879867: 871314
> thanks
Stopping processing here.

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

Processed: tagging 813054

[Debian Bug Tracking System]

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

> tags 813054 - pending
Bug #813054 [src:firefox] firefox: contains JSHint work under non-free licence
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867058: golang-1.8 and mips*

[peter green]

severity 867058 serious
severity 867059 serious
severity 867062 serious
thanks

Hi golang maintainers.

Some time ago John Paul Adrian Glaubitz uploaded some golang binaries for mips, 
mipsel and mips64el to the Debian archive which were not built from slightly 
modified Debian source packages. At the same time he posted a description of 
the changes needed (but no actual machine-readable patches) he used as bug 
reports. These bug reports received no maintainer response. His binaries 
migrated to testing.

Having binaries that were not built from the unmodified Debian sources is a 
serious policy violation. Furthermore these now-outdated binaries are 
preventing any newer versions of the golang-1.8 package migrating to testing.

Therefore golang maintainers you have two choices.

1. Accept John's changes so that your package can be built on mips*.
2. File a removal request for the binaries uploaded by John

The remainder of this mail addresses some questions asked by John in response 
to statements from James Cowgill


> I was under the impression that the golang maintainers want all architectures 
bootstrapped from gccgo? This was the reason mips64el support was not in
> stretch despite upstream support for it. If a normal bootstrap would have 
been acceptable, I would have done it ages ago.

Why? What difference does it make? If a different bootstrapping compiler
results in a different golang compiler after a second rebuild, there is
something wrong with the compiler anyway.

Self-bootstrapping compilers create a maintenance burden. When things go wrong 
they sometimes can't be fixed through source package changes alone. Porterboxes 
are also of limited utility because you can't install non-archive packages on 
them. Then there are derivatives to consider, if a self-bootstrapping compiler 
gets broken in a derivative that rebuilds everything then finding someone who 
can un-jam it can be a pain.

Whether to take on that burden should be a decision for the maintainers of the 
package, not for some flyby contributer.


> Please can you actually discuss this with the package maintainers and mips 
porters _before_ you do anything like this again. You should also read the mips
> related go bugs filed against various golang packages.

Odd. Last time I did this for fpc [1], you were actually very happy. Now
you're getting upset despite the only changes actually necessary are
two lines changed in debian/control.in and debian/helpers/goenv.sh.

What's the difference now?


We are happy that you are working on getting packages ported to your 
architecture.

What we are not happy about is how you are doing it. You need to ensure that 
source goes to the archive either before or at the same time as the binaries 
and you need to either coordinate with maintainers or (if the maintainers are 
unresponsive) follow the normal NMU guidelines.

Processed: golang-1.8 and mips*

[Debian Bug Tracking System]

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

> severity 867058 serious
Bug #867058 [src:golang-1.8] golang-1.8: Please enable mips64el in debian/ 
directory
Severity set to 'serious' from 'normal'
> severity 867059 serious
Bug #867059 [src:golang-1.8] golang-1.8: Please enable mips in debian/ directory
Severity set to 'serious' from 'normal'
> severity 867062 serious
Bug #867062 [src:golang-1.8] golang-1.8: Please enable mipsel in debian/ 
directory
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#853348: marked as done (clementine: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 16:33:55 +
with message-id 
and subject line Bug#853348: fixed in clementine 
1.3.1+git276-g3485bbe43+dfsg-1.1
has caused the Debian Bug report #853348,
regarding clementine: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
[ 44%] Building CXX object src/CMakeFiles/clementine_lib.dir/analyzers/fht.cpp.o
cd 
/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/obj-x86_64-linux-gnu/src 
&& /usr/bin/c++   -DBOOST_BIND_NO_PLACEHOLDERS -DQT_CORE_LIB -DQT_DBUS_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
-DQT_NO_URL_CAST_FROM_STRING -DQT_OPENGL_LIB -DQT_SQL_LIB -DQT_STRICT_ITERATORS 
-DQT_USE_QSTRINGBUILDER -DQT_XML_LIB -I/usr/include/taglib -isystem 
/usr/include/qt4 -isystem /usr/include/qt4/QtCore -I/usr/include/gstreamer-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libxml2 -isystem /usr/include/qt4/QtOpenGL -isystem 
/usr/include/qt4/QtGui -isystem /usr/include/qt4/QtDBus -isystem 
/usr/include/qt4/QtXml -isystem /usr/include/qt4/QtSql -isystem 
/usr/include/qt4/QtNetwork 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/3rdparty/qsqlite 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/obj-x86_64-linux-gnu/src
 -I/<>/clementine-1.3.1+git276-g3485b
 be43+dfsg/src 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/src/../3rdparty/gmock/gtest/include
 -I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/obj-x86_64-linux-gnu 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/3rdparty/qtsingleapplication
 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/3rdparty/qtiocompressor 
-I/usr/include/qxt/QxtCore -I/usr/include/qxt/QxtGui 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/3rdparty/sha2 
-I/usr/include/mygpo-qt 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/ext/libclementine-common
 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/ext/libclementine-tagreader
 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/obj-x86_64-linux-gnu/ext/libclementine-tagreader
 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/ext/libclementine-remote
 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/obj-x86_64-linux-gnu/ext/libclementine-remote
 -I/<>/clementine-1.3.1+git276-g3485bbe4
 3+dfsg/ext/libclementine-spotifyblob 
-I/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/obj-x86_64-linux-gnu/ext/libclementine-spotifyblob
 -I/usr/include/gpod-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/p11-kit-1 -I/usr/include/libusb-1.0  -g -O2 
-fdebug-prefix-map=/<>/clementine-1.3.1+git276-g3485bbe43+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_WARNING_OUTPUT -Wdate-time -D_FORTIFY_SOURCE=2 -Woverloaded-virtual 
-Wall -Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs 
--std=c++0x -U__STRICT_ANSI__ -Werror   -o 
CMakeFiles/clementine_lib.dir/analyzers/fht.cpp.o -c 
/<>/clementine-1.3.1+git276-g3485bbe43+dfsg/src/analyzers/fht.cpp
[ 44%] Building CXX object 
src/CMakeFiles/clementine_lib.dir/core/appearance.cpp.o
cd 

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

[Cyril Brulebois]

Cyril Brulebois  (2017-10-26):
> Following the bump from alpha1 to alpha2, the situation improved quite a
> bit for the d-i daily builds (see #879662 for context). I've triggered a
> manual build for all archs, and if my copying/pasting is correct, the
> results are as follows:
> 
> armel:alpha2, OK
> armhf:alpha1, KO ← the apt alpha2 build came in late, wasn't 
> available yet.
> arm64:alpha2, OK

armhf is also confirmed OK with alpha2.


KiBi.


signature.asc
Description: PGP signature

Bug#873088: git-annex security issue backports

[Sébastien Delafond]

On Oct/26, Antoine Beaupré wrote:
> Right, how does that look then?
> 
> https://gitlab.com/anarcat/git-annex/commit/b21ccd25ecd4cad0efcc8f4f0c94ad99ce32cd04

Nah, +deb8u1 ;)

> Then I can just upload this to security-master?

Yep.

Cheers,

--Seb

Bug#879055: marked as done (mupdf: CVE-2017-15587)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 15:37:10 +
with message-id 
and subject line Bug#879055: fixed in mupdf 1.11+ds1-2
has caused the Debian Bug report #879055,
regarding mupdf: CVE-2017-15587
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.)


-- 
879055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mupdf
Version: 1.5-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=698605

Hi,

the following vulnerability was published for mupdf.

CVE-2017-15587[0]:
| An integer overflow was discovered in pdf_read_new_xref_section in
| pdf/pdf-xref.c in Artifex MuPDF 1.11.

base64 encoded reproducer for verifying:

JVBERi0wMDAwMDAgMCBvYmo8PC9bXS9JbmRleFsyMTQ3NDgzNjQ3IDFdLyAwIDAgUi8gMC9TaXpl
IDAvV1tdPj5zdHJlYW0Nc3RhcnR4cmVmMTAK

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-2017-15587
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15587
[1] https://bugs.ghostscript.com/show_bug.cgi?id=698605
[2] 
http://git.ghostscript.com/?p=mupdf.git;h=82df2631d7d0446b206ea6b434ea609b6c28b0e8
[3] https://nandynarwhals.org/CVE-2017-15587/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mupdf
Source-Version: 1.11+ds1-2

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

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

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

Debian distribution maintenance software
pp.
Kan-Ru Chen (陳侃如)  (supplier of updated mupdf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Oct 2017 22:28:43 +0800
Source: mupdf
Binary: libmupdf-dev mupdf mupdf-tools
Architecture: source amd64
Version: 1.11+ds1-2
Distribution: unstable
Urgency: high
Maintainer: Kan-Ru Chen (陳侃如) 
Changed-By: Kan-Ru Chen (陳侃如) 
Description:
 libmupdf-dev - development files for the MuPDF viewer
 mupdf  - lightweight PDF viewer
 mupdf-tools - command line tools for the MuPDF viewer
Closes: 879055
Changes:
 mupdf (1.11+ds1-2) unstable; urgency=high
 .
   * Acknowledge NMU. Thanks, Salvatore.
   * Renumber patches
   * Fixes CVE-2017-15587 (Closes: 879055)
   * Sort files in static library to make the build reproducible.
   * Bump Standards-Version to 4.1.1. No changes needed.
Checksums-Sha1:
 bffb0aa02a36ce322bd4f91257a8f6dfd8d9115d 2153 mupdf_1.11+ds1-2.dsc
 c3770ee899a86c163ab8f0c931858d2dc3324176 26824 mupdf_1.11+ds1-2.debian.tar.xz
 ec448e6fe9632e2f137944757350b0588595424f 21127648 
libmupdf-dev_1.11+ds1-2_amd64.deb
 9b1376cb28b07ce264fee713680b637723fa28da 19088912 
mupdf-tools_1.11+ds1-2_amd64.deb
 3b93ba673c84d85653e3d2c37978d7211543af38 8029 mupdf_1.11+ds1-2_amd64.buildinfo
 7a5f7595521c715795d63f26e7d857ce12478098 18915888 mupdf_1.11+ds1-2_amd64.deb
Checksums-Sha256:
 fe0fc8bda547129a808eaa46367eca8a018c4208c34dd71040996a71245ef2d5 2153 
mupdf_1.11+ds1-2.dsc
 da7445a8063d7c81b97d2c373aa112df69d3ad29989b67621387e88d9c38b668 26824 
mupdf_1.11+ds1-2.debian.tar.xz
 4d2fb8421d4f4cadfeb579a9b8762908128478b1acbd2653e153953535f16a6a 21127648 
libmupdf-dev_1.11+ds1-2_amd64.deb
 08fb6279f2dc3cb4225cc13a7bc6a87c08bf0c770822cd9aeb6daefc18beadca 19088912 
mupdf-tools_1.11+ds1-2_amd64.deb
 e1dec8ffc670839b48c5831a266b076be6f6db27e24e99fea5000bb0cd3952bc 8029 
mupdf_1.11+ds1-2_amd64.buildinfo
 ac5044edb10e9accfb033f06248a93cdfb6b17264a793dd50bc01e117705402d 18915888 
mupdf_1.11+ds1-2_amd64.deb
Files:
 3de8c76f8313e0a18039ee621998d2bd 2153 text optional mupdf_1.11+ds1-2.dsc
 378192c7b2489e04704bf3061123a6ba 26824 text optional 
mupdf_1.11+ds1-2.debian.tar.xz
 9a8eefc38adea1a4319869ae530b5e26 21127648 libdevel optional 
libmupdf-dev_1.11+ds1-2_amd64.deb
 c4d2a4ad4ded92b9136fbb2fb51d093e 19088912 text optional 
mupdf-tools_1.11+ds1-2_amd64.deb
 5d51562c253b3c9fa5c320a3cef85dfe 8029 text optional 

Bug#873088: git-annex security issue backports

[Antoine Beaupré]

On 2017-10-26 11:14:34, Sébastien Delafond wrote:
> On Oct/26, Antoine Beaupré wrote:
>> I have also backported joey's patch to jessie. It was simpler than
>> wheezy because the code is much more similar. The resulting patch is
>> available here:
>> 
>> https://gitlab.com/anarcat/git-annex/commit/58daf6cbe4c1ea1cf71f3a538a0e27b5075c7265
>> 
>> As expected, the patch Joey provided applies fine on stretch and
>> should be applied and uploaded as-is. This time, it's in
>> debian/patches because the package is non-native since stretch:
>> 
>> https://gitlab.com/anarcat/git-annex/commit/115585df48dce16aa702663dab220de625b9de7d
>> 
>> I can do the upload if you authorize me. The above are not *exactly*
>> debdiffs, but they are pretty close, so I hope that's sufficient for
>> review.
>
> Thank you for backporting those.
>
> For the jessie debdiff, please change the version to 5.20141125+deb8u1,
> and target jessie-security. The stretch one looks good as is.
>
> Make sure you build both with -sa, and then you can upload.

Right, how does that look then?

https://gitlab.com/anarcat/git-annex/commit/b21ccd25ecd4cad0efcc8f4f0c94ad99ce32cd04

Then I can just upload this to security-master?

A.
-- 
In god we trust, others pay cash.
- Richard Desjardins, Miami

Bug#873088: git-annex security issue backports

[Sébastien Delafond]

On Oct/26, Antoine Beaupré wrote:
> I have also backported joey's patch to jessie. It was simpler than
> wheezy because the code is much more similar. The resulting patch is
> available here:
> 
> https://gitlab.com/anarcat/git-annex/commit/58daf6cbe4c1ea1cf71f3a538a0e27b5075c7265
> 
> As expected, the patch Joey provided applies fine on stretch and
> should be applied and uploaded as-is. This time, it's in
> debian/patches because the package is non-native since stretch:
> 
> https://gitlab.com/anarcat/git-annex/commit/115585df48dce16aa702663dab220de625b9de7d
> 
> I can do the upload if you authorize me. The above are not *exactly*
> debdiffs, but they are pretty close, so I hope that's sufficient for
> review.

Thank you for backporting those.

For the jessie debdiff, please change the version to 5.20141125+deb8u1,
and target jessie-security. The stretch one looks good as is.

Make sure you build both with -sa, and then you can upload.

Cheers,

--Seb

Bug#879858: duktape-dev: Dangling symlink to library

[Jeremy Bicha]

Package: duktape-dev
Version: 2.2.0-1
Severity: serious

duktape-dev has this symlink:

/usr/lib/libduktape.so -> libduktape.so.202

but libduktape202 ships this file (as seen in the i386 build)
/usr/lib/i386-linux-gnu/libduktape.so.202

https://buildd.debian.org/status/fetch.php?pkg=duktape=i386=2.2.0-1=1509011601

It looks like you need to make sure to use multi-arch for duktape-dev too.

I noticed this while trying to build edbrowse 3.7.1

Thanks,
Jeremy Bicha

Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch

[Ferdinand Rau]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20161206-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

I am affected by this issue on a Wortmann/Terra Mobile N360-11 notebook 
computer with an Intel i915 graphics chipset.

Every time I use the suspend or hibernate sleep states, the system boots and 
resumes as expected (I can see the screen exactly the way before I pressed the 
hibernate button). After one or two seconds, however, the display manager is 
restarted and I am presented with a blac screen briefly, followed by the 
regular login screen. I use Xfce4 with lightdm, btw.
On the login screen, I can immediately log in as the same user that triggered 
the hibernation, and use the computer just fine.
After logging in, however, all applications are closed and all unsaved data is 
lost.
The consoles (TTY1, TTY2) are not affected.
The behaviour is reproducible every time I suspend or hibernate, also when 
hibernation is triggered automatically, e.g. by a low battery level.

After such a "failed" resume, I can find the following error message in the 
output of dmesg:
> [drm] GPU HANG: ecode 8:0:0x5fa3bf07, in Xorg [641], reason: Hang on render 
> ring, action: reset
> [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, 
> including userspace.
> [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> 
> DRM/Intel
> [drm] drm/i915 developers can then reassign to the right component if it's 
> not a kernel issue.
> [drm] The gpu crash dump is required to analyze gpu hangs, so please always 
> attach it.
> [drm] GPU crash dump saved to /sys/class/drm/card0/error
> drm/i915: Resetting chip after gpu hang
> drm/i915: Resetting chip after gpu hang

uname -a:
> Linux N360-11 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 
> GNU/Linux

Further information:
Note that I have a Debian testing live CD at hand, running kernel 4.11. The 
live CD is not affected by this issue.
I have read the description of bug #637511 and while this is an old bug, it is 
similar in the way that the system is not affected at all after a display 
manager restart.
Also, the error message reported here ist very similar to what I see: 
https://bugs.freedesktop.org/show_bug.cgi?id=93510

Please let me know what further information you require to investigate this 
issue, if any.

Best regards,
Ferdinand


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics 
Controller [8086:22b1] (rev 35)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 32263 Oct 22 02:55 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 38483 Oct 26 16:06 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  1688.281] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[  1688.281] X Protocol Version 11, Revision 0
[  1688.281] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[  1688.281] Current Operating System: Linux N360-11 4.9.0-4-amd64 #1 SMP 
Debian 4.9.51-1 (2017-09-28) x86_64
[  1688.281] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 
root=/dev/sda2 ro quiet
[  1688.281] Build Date: 16 October 2017  08:19:45AM
[  1688.281] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) 
[  1688.281] Current version of pixman: 0.34.0
[  1688.281]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1688.281] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1688.281] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 26 15:46:30 
2017
[  1688.281] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1688.282] (==) No Layout section.  Using the first Screen section.
[  1688.282] (==) No screen section available. Using defaults.
[  1688.282] (**) |-->Screen "Default Screen Section" (0)
[  1688.282] (**) |   |-->Monitor ""
[  1688.282] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  1688.282] (==) Automatically adding devices
[  1688.282] (==) Automatically enabling devices
[  1688.282] (==) Automatically adding GPU devices
[  1688.282] 

Bug#873088: git-annex security issue backports

[Antoine Beaupré]

On 2017-10-23 09:26:28, Antoine Beaupré wrote:
>> What's the status?
>
> I'm resuming work on this now, and I'll see how I can backport this to
> wheezy, which should helpfully give some help/nudge to the jessie
> version as well.

Hi,

I have pushed DLA-1144-1 for git-annex in wheezy after summary tests.

I have also backported joey's patch to jessie. It was simpler than
wheezy because the code is much more similar. The resulting patch is
available here:

https://gitlab.com/anarcat/git-annex/commit/58daf6cbe4c1ea1cf71f3a538a0e27b5075c7265

As expected, the patch Joey provided applies fine on stretch and should
be applied and uploaded as-is. This time, it's in debian/patches because
the package is non-native since stretch:

https://gitlab.com/anarcat/git-annex/commit/115585df48dce16aa702663dab220de625b9de7d

I can do the upload if you authorize me. The above are not *exactly*
debdiffs, but they are pretty close, so I hope that's sufficient for
review.

A.

-- 
In serious work commanding and discipline are of little avail.
 - Peter Kropotkin

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

[Julian Andres Klode]

On Thu, Oct 26, 2017 at 01:52:40PM +0200, Julian Andres Klode wrote:
> On Thu, Oct 26, 2017 at 12:59:20PM +0200, joel hansson wrote:
> > Package: apt
> > Followup-For: Bug #879814
> > 
> > Dear Maintainer,
> > 
> >  I have a similar issue, but on arch: amd64 but on another syscall.
> > 
> > 
> >  --- snip ---
> >  $ sudo apt-get update
> >  [sudo] password for user:
> >  Hit:1 http://ftp.se.debian.org/debian unstable InRelease
> >  Get:2 http://ftp.se.debian.org/debian unstable/main amd64 Packages
> >  [7,745 kB]
> >  18% [2 Packages store 0 B] [Waiting for headers]
> >   Seccomp prevented execution of syscall 41 on
> >  architecture amd64 
> >  Reading package lists... Done
> >  E: Method store has died unexpectedly!
> >  E: Sub-process store returned an error code (31)
> >  $
> >  --- snip 
> > 
> > 
> > 
> > 
> >* What led up to the situation?
> > 
> >-alpha1 of apt was installed during an upgrade.
> > 
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > 
> >-alpha1 had the issue.
> >Upgraded to -alpha2 manually, but it has the same issue.
> 
> That's the socket syscall being used by a method only supposed to
> operate on local files. Could you run with APT::Sandbox::Seccomp::Print
> set to false and get a backtrace (you need to let it dump core, and
> then run gdb on the core; for example, by installing systemd-coredump
> and then running coredumpctl gdb after executing apt).

In order to identify which other syscalls might be missing for your system,
install seccomp, 
(1) run scmp_sys_resolver with the number in the error message. Here, that would
print socket.

(2) Add that to an apt.conf(.d) file in APT::Sandbox::Seccomp::Allow

APT::Sandbox::Seccomp::Allow {
"socket";
};

(3) run again

repeat the steps until it works.

It would also be good to know if you have any special nss modules
installed.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  speaks English, German

Bug#879848: cappuccino: missing dependency on gir1.2-gtk-3.0

[Reiner Herrmann]

Source: cappuccino
Version: 0.5.1-6
Severity: serious

Dear Maintainer,

I installed and tried to start cappuccino, but it didn't launch:

$ cappuccino 
Traceback (most recent call last):
  File "/usr/bin/cappuccino", line 11, in 
gi.require_version('Gtk', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

After installing gir1.2-gtk-3.0 it successfully starts, so this should
be added to the dependencies.

Kind regards,
  Reiner


signature.asc
Description: PGP signature

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

[Harald Welte]

I'm sorry, this is a bogus report.  I figure out it was a misconfiguration
on my machine, sorry for the noise. Please close.
-- 
- Harald Welte    http://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)

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

[James Cowgill]

Hi,

On 26/10/17 11:25, Rainer Dorsch wrote:
> Hi James,
> 
> thanks for your immediate reply.
> 
> On Donnerstag, 26. Oktober 2017 09:47:30 CEST James Cowgill wrote:
> [...]
>> On 26/10/17 07:37, Rainer Dorsch wrote:
>>> Package: ffmpeg
>>> Version: 7:3.3.4-2+b1
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> I tried to build ffmpeg 3.4 from source using
>>
>> Just to clarify. You are building *3.4* here right? I ask because you
>> have given two different versions above.
>>
> 
> yes, I am building for *3.4*. Since 7:3.3.4-2+b1 is installed, that was 
> automatically scanned by reportbug and inserted in the report, I could have 
> changed that manually, I think.

Thanks. I've adjusted the version number so it's tracked properly.

>> There is a known build issue with ffmpeg 3.4 on armhf at the moment
>> which I have asked upstream about. They have applied the following
>> commit which tries to fix it. Could you try applying this patch to see
>> if it helps?
>>
>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/587fadaef1e8163b3e56043e
>> 500a3724e7fc5379
> 
> Thanks, I will give it a try.
>> If that doesn't help, can you provide: the contents of /proc/cpuinfo,
[...]
>> the full build log
> 
> do I get that with 
> 
> dpkg-buildpackage -us -uc 2>&1 >build.log

Yes something like this should work. You should switch the order of the
redirections so that stderr is redirected to the log:
 dpkg-buildpackage -us -uc >build.log 2>&1

>> , and the contents of the .err file of the failing
>> test. 
> rd@xbian:/mnt/tmp/rd/debian/ffmpeg$ find -name *.err
> ./ffmpeg-3.4/debian/standard/tests/data/fate/checkasm-float_dsp.err

Yes that's the file.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

[Julian Andres Klode]

On Thu, Oct 26, 2017 at 12:59:20PM +0200, joel hansson wrote:
> Package: apt
> Followup-For: Bug #879814
> 
> Dear Maintainer,
> 
>  I have a similar issue, but on arch: amd64 but on another syscall.
> 
> 
>  --- snip ---
>  $ sudo apt-get update
>  [sudo] password for user:
>  Hit:1 http://ftp.se.debian.org/debian unstable InRelease
>  Get:2 http://ftp.se.debian.org/debian unstable/main amd64 Packages
>  [7,745 kB]
>  18% [2 Packages store 0 B] [Waiting for headers]
>   Seccomp prevented execution of syscall 41 on
>  architecture amd64 
>  Reading package lists... Done
>  E: Method store has died unexpectedly!
>  E: Sub-process store returned an error code (31)
>  $
>  --- snip 
> 
> 
> 
> 
>* What led up to the situation?
> 
>-alpha1 of apt was installed during an upgrade.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>-alpha1 had the issue.
>Upgraded to -alpha2 manually, but it has the same issue.

That's the socket syscall being used by a method only supposed to
operate on local files. Could you run with APT::Sandbox::Seccomp::Print
set to false and get a backtrace (you need to let it dump core, and
then run gdb on the core; for example, by installing systemd-coredump
and then running coredumpctl gdb after executing apt).

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  speaks English, German

Bug#879827: libcommon-sense-perl is no longer installable with perl 5.26.1-2

[Vincent Lefevre]

Package: libcommon-sense-perl
Severity: grave
Justification: renders package unusable

It is no longer possible to install libcommon-sense-perl:

 libcommon-sense-perl : Depends: perl (< 5.26.1~) but 5.26.1-2 is to be 
installed
E: Unable to correct problems, you have held broken packages.

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

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

Versions of packages libcommon-sense-perl depends on:
ii  perl5.26.1-2
ii  perl-base [perlapi-5.26.0]  5.26.1-2
pn  perlapi-5.24.1  

libcommon-sense-perl recommends no packages.

libcommon-sense-perl suggests no packages.

Bug#879821: libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 375.82-6

[Vincent Lefevre]

And note that this is not fixable with "apt install -f".

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

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

[Debian Bug Tracking System]

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

> retitle 879821 libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure to 
> 375.82-6
Bug #879821 [libgles1-glvnd-nvidia] libgles1-glvnd-nvidia:amd64: upgrade 
failure to 375.82-6
Changed Bug title to 'libgles1-glvnd-nvidia, libgles-nvidia1: upgrade failure 
to 375.82-6' from 'libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6'.
>
End of message, stopping processing here.

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

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

[joel hansson]

Package: apt
Followup-For: Bug #879814

Dear Maintainer,

 I have a similar issue, but on arch: amd64 but on another syscall.


 --- snip ---
 $ sudo apt-get update
 [sudo] password for user:
 Hit:1 http://ftp.se.debian.org/debian unstable InRelease
 Get:2 http://ftp.se.debian.org/debian unstable/main amd64 Packages
 [7,745 kB]
 18% [2 Packages store 0 B] [Waiting for headers]
  Seccomp prevented execution of syscall 41 on
 architecture amd64 
 Reading package lists... Done
 E: Method store has died unexpectedly!
 E: Sub-process store returned an error code (31)
 $
 --- snip 




   * What led up to the situation?

   -alpha1 of apt was installed during an upgrade.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   -alpha1 had the issue.
   Upgraded to -alpha2 manually, but it has the same issue.




   * What was the outcome of this action?

   Same issue

   * What outcome did you expect instead?

   That the issue with the prevented execution of syscall 41
   would be fixed.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.13\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.12\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.13\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";

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

[Vincent Lefevre]

Package: libgles1-glvnd-nvidia
Version: 375.82-6
Severity: grave
Justification: renders package unusable

In the upgrade to 375.82-6:

Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb ...
Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-6_i386.deb ...
Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5) ...
Processing triggers for mime-support (3.60) ...
Setting up libnvidia-eglcore:amd64 (375.82-6) ...
Setting up libnvidia-eglcore:i386 (375.82-6) ...
Processing triggers for desktop-file-utils (0.23-2) ...
Setting up libnvidia-glcore:amd64 (375.82-6) ...
Setting up libnvidia-glcore:i386 (375.82-6) ...
Processing triggers for libc-bin (2.24-17) ...
Setting up nvidia-egl-common (375.82-6) ...
Setting up nvidia-vulkan-common (375.82-6) ...
Setting up nvidia-legacy-check (375.82-6) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up nvidia-alternative (375.82-6) ...
Processing triggers for nvidia-alternative (375.82-6) ...
Setting up libglx-nvidia0:amd64 (375.82-6) ...
Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
Setting up nvidia-kernel-support (375.82-6) ...
Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
Setting up libegl-nvidia0:amd64 (375.82-6) ...
Setting up libegl-nvidia0:i386 (375.82-6) ...
Setting up libgles-nvidia2:i386 (375.82-6) ...
Setting up libgles-nvidia2:amd64 (375.82-6) ...
Setting up libnvidia-cfg1:amd64 (375.82-6) ...
Setting up libnvidia-cfg1:i386 (375.82-6) ...
dpkg: dependency problems prevent configuration of libgles1-glvnd-nvidia:amd64:
 libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is unpacked 
but not configured.
  libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgles1-glvnd-nvidia:i386:
 libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and is unpacked 
but not configured.
  libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:i386 (--configure):
 dependency problems - leaving unconfigured
Setting up nvidia-kernel-dkms (375.82-6) ...
[...]
Setting up libnvidia-ml1:amd64 (375.82-6) ...
dpkg: dependency problems prevent configuration of libgles-nvidia1:amd64:
 libgles-nvidia1:amd64 depends on libgles1 (>= 0.2.999) | 
libgles1-glvnd-nvidia; however:
  Package libgles1 is not installed.
  Package libgles1-glvnd-nvidia:amd64 which provides libgles1 is not configured 
yet.
  Package libgles1-glvnd-nvidia:amd64 is not configured yet.

dpkg: error processing package libgles-nvidia1:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgles-nvidia1:i386:
 libgles-nvidia1:i386 depends on libgles1 (>= 0.2.999) | libgles1-glvnd-nvidia; 
however:
  Package libgles1-glvnd-nvidia:i386 which provides libgles1 is not configured 
yet.
  Package libgles1-glvnd-nvidia:i386 is not configured yet.

dpkg: error processing package libgles-nvidia1:i386 (--configure):
 dependency problems - leaving unconfigured
Setting up libgl1-nvidia-glvnd-glx:amd64 (375.82-6) ...
Setting up xserver-xorg-video-nvidia (375.82-6) ...
Setting up nvidia-driver-bin (375.82-6) ...
Setting up libglx-nvidia0:i386 (375.82-6) ...
Setting up nvidia-vulkan-icd:i386 (375.82-6) ...
Setting up nvidia-egl-icd:i386 (375.82-6) ...
Setting up nvidia-egl-icd:amd64 (375.82-6) ...
Setting up libgl1-nvidia-glvnd-glx:i386 (375.82-6) ...
Setting up nvidia-driver-libs:amd64 (375.82-6) ...
Setting up nvidia-driver-libs:i386 (375.82-6) ...
Setting up nvidia-driver (375.82-6) ...
Setting up nvidia-driver-libs-i386:i386 (375.82-6) ...
Processing triggers for glx-alternative-nvidia (0.8.0) ...
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for update-glx (0.8.0) ...
Processing triggers for glx-alternative-nvidia (0.8.0) ...
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-1-amd64
Errors were encountered while processing:
 libgles1-glvnd-nvidia:amd64
 libgles1-glvnd-nvidia:i386
 libgles-nvidia1:amd64
 libgles-nvidia1:i386
[...]
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libgles1-glvnd-nvidia:amd64:
 libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and is unpacked 
but not configured.
  libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.

dpkg: error processing package libgles1-glvnd-nvidia:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgles1-glvnd-nvidia:i386:
 libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and is unpacked 
but not configured.
  

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

[Rainer Dorsch]

Hi James,

thanks for your immediate reply.

On Donnerstag, 26. Oktober 2017 09:47:30 CEST James Cowgill wrote:
[...]
> On 26/10/17 07:37, Rainer Dorsch wrote:
> > Package: ffmpeg
> > Version: 7:3.3.4-2+b1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I tried to build ffmpeg 3.4 from source using
> 
> Just to clarify. You are building *3.4* here right? I ask because you
> have given two different versions above.
> 

yes, I am building for *3.4*. Since 7:3.3.4-2+b1 is installed, that was 
automatically scanned by reportbug and inserted in the report, I could have 
changed that manually, I think.

> [...]
> 
> > -- System Information:
> > Debian Release: buster/sid
> > 
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (500, 'testing'), (70, 'experimental')
> > 
> > Architecture: armhf (armv7l)
> 
> There is a known build issue with ffmpeg 3.4 on armhf at the moment
> which I have asked upstream about. They have applied the following
> commit which tries to fix it. Could you try applying this patch to see
> if it helps?
> 
> https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/587fadaef1e8163b3e56043e
> 500a3724e7fc5379

Thanks, I will give it a try.
> If that doesn't help, can you provide: the contents of /proc/cpuinfo,

rd@xbian:~$ cat /proc/cpuinfo 
processor   : 0
model name  : ARMv7 Processor rev 10 (v7l)
BogoMIPS: 6.00
Features: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part: 0xc09
CPU revision: 10

processor   : 1
model name  : ARMv7 Processor rev 10 (v7l)
BogoMIPS: 6.00
Features: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part: 0xc09
CPU revision: 10

Hardware: Freescale i.MX6 Quad/DualLite (Device Tree)
Revision: 
Serial  : 
rd@xbian:~$ 

> the full build log

do I get that with 

dpkg-buildpackage -us -uc 2>&1 >build.log

or is that created automatically? If yes, what is the filename?

> , and the contents of the .err file of the failing
> test. 
rd@xbian:/mnt/tmp/rd/debian/ffmpeg$ find -name *.err
./ffmpeg-3.4/debian/standard/tests/data/fate/checkasm-float_dsp.err
rd@xbian:/mnt/tmp/rd/debian/ffmpeg$

Thanks
Rainer

> The test log should tell you what err file you need to look at.
> 
> Thanks,
> James


-- 
Rainer Dorsch
http://bokomoko.de/

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

[James Cowgill]

Hi,

On 26/10/17 10:53, Cyril Brulebois wrote:
> Package: apt
> Version: 1.6~alpha2
> Severity: serious
> Tags: d-i
> Justification: FTBFS
> 
> [ X-D-Cc: debian-boot@, debian-mips@, debian-powerpc@ ]
> 
> Hi,
> 
> Following the bump from alpha1 to alpha2, the situation improved quite a
> bit for the d-i daily builds (see #879662 for context). I've triggered a
> manual build for all archs, and if my copying/pasting is correct, the
> results are as follows:
> 
> armel:alpha2, OK
> armhf:alpha1, KO ← the apt alpha2 build came in late, wasn't 
> available yet.
> arm64:alpha2, OK
> amd64:alpha2, OK
> i386: alpha2, OK
> mips: alpha2,  Seccomp prevented execution of syscall 004117 
> on architecture mips 
> mipsel:   alpha2,  Seccomp prevented execution of syscall 004117 
> on architecture mipsel 
> mips64el: alpha2, OK
> powerpc:  alpha2, OK
> ppc64el:  alpha2,  Seccomp prevented execution of syscall 000117 
> on architecture ppc64el 
> s390x:alpha2, OK

Syscall 4117 on 32-bit mips, and syscall 117 on ppc64el is the sysv IPC
syscall. On these architectures there is one syscall for all sysv IPC
instead of individual syscalls for each operation.

This is probably needed for fakeroot like the other syscalls in #879662.

James



signature.asc
Description: OpenPGP digital signature

Bug#879815: eclipse-titan not installable on current stretch/amd64

[Harald Welte]

Package: eclipse-titan
Severity: grave

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

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

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

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

and just after "apt-get update".

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

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

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

eclipse-titan recommends no packages.

eclipse-titan suggests no packages.

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]

[Cyril Brulebois]

Package: apt
Version: 1.6~alpha2
Severity: serious
Tags: d-i
Justification: FTBFS

[ X-D-Cc: debian-boot@, debian-mips@, debian-powerpc@ ]

Hi,

Following the bump from alpha1 to alpha2, the situation improved quite a
bit for the d-i daily builds (see #879662 for context). I've triggered a
manual build for all archs, and if my copying/pasting is correct, the
results are as follows:

armel:alpha2, OK
armhf:alpha1, KO ← the apt alpha2 build came in late, wasn't available 
yet.
arm64:alpha2, OK
amd64:alpha2, OK
i386: alpha2, OK
mips: alpha2,  Seccomp prevented execution of syscall 004117 on 
architecture mips 
mipsel:   alpha2,  Seccomp prevented execution of syscall 004117 on 
architecture mipsel 
mips64el: alpha2, OK
powerpc:  alpha2, OK
ppc64el:  alpha2,  Seccomp prevented execution of syscall 000117 on 
architecture ppc64el 
s390x:alpha2, OK

Porters: Julian mentioned it would be best if one could look at allowing
extra syscalls through a config file[1], so as to detect other syscalls
that might be needed as well (as it stands, the first offender triggers
a failure, so we don't get a full list).

 1. https://bugs.debian.org/879662#39


KiBi.

Bug#872040: marked as done (duktape: please ship a duktape library)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:22 +
with message-id 
and subject line Bug#872040: fixed in duktape 2.2.0-1
has caused the Debian Bug report #872040,
regarding duktape: please ship a duktape library
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As discussed on the mailinglist¹², there is a use-case for using a duktape
library in Debian: the upstream of the edbrowse package shifted to it. So
please provide a duktape library that edbrowse could use.

Paul

PS: I'll try to figure out if edbrowse works with the default config, but
haven't done that yet.

¹ 
https://lists.alioth.debian.org/pipermail/debian-iot-maintainers/Week-of-Mon-20170807/000197.html
² 
https://lists.debian.org/msgid-search/fb3e250e-67d6-ec8f-aa71-5935296d6...@debian.org

- -- System Information:
Debian Release: 9.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (200, 'stable'), (50, 
'stable')
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlmQlUUACgkQnFyZ6wW9
dQqrXAgAiF2pIWr7w98zGZQw8OkZxfcpl7ak5yi+hdFnUdcXUetBbAOGCWGDLs+8
PZ9c63sAZe5HggicX92mGvYMDvZW/9LN0pmItf1VuFOhtzDcHvi/LpCOWtr2Mhs4
YgdPrAqoYz0nSN69WD59R+7F3FZ8hS71MIS4usUheUQPBOODF9DeBxfc509DQFxN
vLfk5zZZ+B7N4tna6NPYNrAuMIaXcYKw0cJTCrRRDMPa9zzgtJF4Q5CRL26lddXI
cOI6VxszwQttu6h2U/d22YSQ1ONe5AUl2kXWgK/m1SFru2XB2zzYf4xfwhtqRieB
oH7NtYZYHDg1ynrUnRy34/ktae2iuA==
=pVuE
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: duktape
Source-Version: 2.2.0-1

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated duktape 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, 25 Oct 2017 19:16:35 +0200
Source: duktape
Binary: duktape duktape-dev libduktape202
Architecture: source amd64
Version: 2.2.0-1
Distribution: sid
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 duktape- embeddable Javascript engine
 duktape-dev - embeddable Javascript engine, development files
 libduktape202 - embeddable Javascript engine, library
Closes: 872040
Changes:
 duktape (2.2.0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/control: set standard to 4.1.1 (no changes)
   * debian/control: use dh10
   * add library package (Closes: #872040)
Checksums-Sha1:
 222b0c9fe37d9d44f6c57704573fb72dbe646a50 2199 duktape_2.2.0-1.dsc
 059d8f6ce4537bfca5689da693225802bb482706 969136 duktape_2.2.0.orig.tar.xz
 56c63db033646a90e41df5af75388af8e837ea0a 4712 duktape_2.2.0-1.debian.tar.xz
 a43752dc5d2bf324c07d52d24f30a424aa520d3d 419680 
duktape-dbgsym_2.2.0-1_amd64.deb
 a61b4a931e3f75a8fe9d87e219daf6dc19f18892 576600 duktape-dev_2.2.0-1_amd64.deb
 9a0ee2408249d8e41bc5b2a3917762db51ba390e 6621 duktape_2.2.0-1_amd64.buildinfo
 d5b725ed5003d544f7597d2e4e824efa0cd5296f 123348 duktape_2.2.0-1_amd64.deb
 94f1f6513a9d11d8025d7fa93ea086fab55de570 13116 
libduktape202-dbgsym_2.2.0-1_amd64.deb
 c98d0f3d82f301408af892fac1e1ff604428ed54 122132 libduktape202_2.2.0-1_amd64.deb
Checksums-Sha256:
 1ddb22d56f905bf4134767f520a43dfae32d1107f37ed8614e5b6f56acf26435 2199 
duktape_2.2.0-1.dsc
 62f72206427633077cb02e7ccd2599ace4d254db409334593b86d262c0d50c14 969136 
duktape_2.2.0.orig.tar.xz
 5e5fc73ecd3f7b93854b9b4ee8a993870cbd38111fd6eae0f163e044af053097 4712 
duktape_2.2.0-1.debian.tar.xz
 

Bug#877216: marked as done (d3-timer: B-D npm not available in testing)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:31 +
with message-id 
and subject line Bug#877216: fixed in node-d3-timer 1.0.7-2
has caused the Debian Bug report #877216,
regarding d3-timer: B-D npm not available in testing
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.)


-- 
877216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-d3-color
Version: 1.0.3-1
Severity: serious
Justification: Build-Depends not satisfiable in testing
Control: block -1 with 857986
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 node-d3-format 1.2.0-1
Control: retitle -2 node-d3-format: B-D npm not available in testing
Control: block -2 with 857986
Control: reassign -3 node-d3-queue 3.0.7-1
Control: retitle -3 node-d3-queue: B-D npm not available in testing
Control: block -3 with 857986
Control: reassign -4 node-d3-selection 1.1.0-1
Control: retitle -4 node-d3-selection: B-D npm not available in testing
Control: block -4 with 857986
Control: reassign -5 d3-timer 1.0.7-1
Control: retitle -5 d3-timer: B-D npm not available in testing
Control: block -5 with 857986
Control: reassign -6  node-filesize 3.5.10+dfsg-1
Control: retitle -6 node-filesize: B-D npm not available in testing
Control: block -6 with 857986
Control: reassign -7 node-gulp-babel 7.0.0-1
Control: retitle -7 node-gulp-babel: B-D npm not available in testing
Control: block -7 with 857986
Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1
Control: retitle -8 node-babel-plugin-transform-define: B-D npm not available 
in testing
Control: block -8 with 857986
Control: reassign -9 node-babel 6.25.0+dfsg-8
Control: retitle -9 node-babel: B-D npm not available in testing
Control: block -9 with 857986
Control: reassign -10 node-babylon 6.18.0-1
Control: retitle -10 node-babylon: B-D npm not available in testing
Control: block -10 with 857986


Hi,

with npm not available in testing (and according to #857986 this will
not change in the near future), these node-* packages must be kept
out of testing, since they cannot be rebuilt in testing (regardless of
any external resources they might need additionally).


Andreas
--- End Message ---
--- Begin Message ---
Source: node-d3-timer
Source-Version: 1.0.7-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-d3-timer 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, 02 Oct 2017 10:19:26 +0530
Source: node-d3-timer
Binary: node-d3-timer
Architecture: source all
Version: 1.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-d3-timer - efficient queue to manage thousands of concurrent animations
Closes: 877216
Changes:
 node-d3-timer (1.0.7-2) unstable; urgency=medium
 .
   * Build using babel and move to main (Closes: #877216)
Checksums-Sha1:
 3258b5281b2127947989e8d69dfc89cea3d54f13 2135 node-d3-timer_1.0.7-2.dsc
 6a5fb733cad78ded3bb85bd5424c3f621c017001 2840 
node-d3-timer_1.0.7-2.debian.tar.xz
 62cf98446530d19a25e5d4306253546576d91210 7050 node-d3-timer_1.0.7-2_all.deb
 aea65aad07b7cf42a53438084502b6c4ffd3c798 9698 
node-d3-timer_1.0.7-2_amd64.buildinfo
Checksums-Sha256:
 d930cea0e8548296b98b815c49725b88b09db4541304a1cc78c8e7bdb09cab53 2135 
node-d3-timer_1.0.7-2.dsc
 8a944602fd73078f4d341c0f2d5d42964d54a89bc8a534b6bcaa14c0f808a192 2840 
node-d3-timer_1.0.7-2.debian.tar.xz
 4344f7094231dbe2d04e3134ba2d25edd3f027a4e3c7f330f1214a1b13d6c6a4 7050 
node-d3-timer_1.0.7-2_all.deb
 0831db123fd8aded62302cd091cbfe8b1aa975717a2ddc29826c239b28e2c57f 9698 
node-d3-timer_1.0.7-2_amd64.buildinfo
Files:
 e11598ea0dc7a0b0e02bc79c8539abcc 2135 javascript optional 
node-d3-timer_1.0.7-2.dsc
 a3ef609cbe0ae138880276f99ff7e903 2840 javascript optional 

Bug#877215: marked as done (node-d3-selection: B-D npm not available in testing)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:31 +
with message-id 
and subject line Bug#877215: fixed in node-d3-selection 1.1.0-2
has caused the Debian Bug report #877215,
regarding node-d3-selection: B-D npm not available in testing
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.)


-- 
877215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-d3-color
Version: 1.0.3-1
Severity: serious
Justification: Build-Depends not satisfiable in testing
Control: block -1 with 857986
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 node-d3-format 1.2.0-1
Control: retitle -2 node-d3-format: B-D npm not available in testing
Control: block -2 with 857986
Control: reassign -3 node-d3-queue 3.0.7-1
Control: retitle -3 node-d3-queue: B-D npm not available in testing
Control: block -3 with 857986
Control: reassign -4 node-d3-selection 1.1.0-1
Control: retitle -4 node-d3-selection: B-D npm not available in testing
Control: block -4 with 857986
Control: reassign -5 d3-timer 1.0.7-1
Control: retitle -5 d3-timer: B-D npm not available in testing
Control: block -5 with 857986
Control: reassign -6  node-filesize 3.5.10+dfsg-1
Control: retitle -6 node-filesize: B-D npm not available in testing
Control: block -6 with 857986
Control: reassign -7 node-gulp-babel 7.0.0-1
Control: retitle -7 node-gulp-babel: B-D npm not available in testing
Control: block -7 with 857986
Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1
Control: retitle -8 node-babel-plugin-transform-define: B-D npm not available 
in testing
Control: block -8 with 857986
Control: reassign -9 node-babel 6.25.0+dfsg-8
Control: retitle -9 node-babel: B-D npm not available in testing
Control: block -9 with 857986
Control: reassign -10 node-babylon 6.18.0-1
Control: retitle -10 node-babylon: B-D npm not available in testing
Control: block -10 with 857986


Hi,

with npm not available in testing (and according to #857986 this will
not change in the near future), these node-* packages must be kept
out of testing, since they cannot be rebuilt in testing (regardless of
any external resources they might need additionally).


Andreas
--- End Message ---
--- Begin Message ---
Source: node-d3-selection
Source-Version: 1.1.0-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-d3-selection 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Oct 2017 17:12:46 +0530
Source: node-d3-selection
Binary: node-d3-selection
Architecture: source all
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-d3-selection - select elements and join them to data
Closes: 877215
Changes:
 node-d3-selection (1.1.0-2) unstable; urgency=medium
 .
   * Use babel to transpile and move to main (Closes: #877215)
Checksums-Sha1:
 27fd11afad94a73b454175f13126f386e63cd2ad 2122 node-d3-selection_1.1.0-2.dsc
 d4a2f0e12ced7b34a57bb3ecf58505bfed28ac82 36363 
node-d3-selection_1.1.0.orig.tar.gz
 03a59662a8830a326c4e3b2e3da25f2dc9eab8bb 2764 
node-d3-selection_1.1.0-2.debian.tar.xz
 8eb33fe04e697ef6a15a6c861749862b34e36b15 26198 
node-d3-selection_1.1.0-2_all.deb
 d33475d928c55ff3ffb90d5d608772e6a8e75943 9404 
node-d3-selection_1.1.0-2_amd64.buildinfo
Checksums-Sha256:
 ee4480d8d22bcbf9778217193534917e847c133ebcff8bd6fa3d61bb81f7251d 2122 
node-d3-selection_1.1.0-2.dsc
 70a0bb8581d6baa2dea5039d39b4f96bd7a03467f3bcd34107090f16f284be86 36363 
node-d3-selection_1.1.0.orig.tar.gz
 2de061ea1e38b626e3a793490fbd8360fa567c221b4a609b844884e95850af1b 2764 
node-d3-selection_1.1.0-2.debian.tar.xz
 9c2867e9aaf4f1ed03686c08fa3655ab84b1c76ba0398daa51c62131065d7497 26198 
node-d3-selection_1.1.0-2_all.deb
 

Processed: update ffmpeg #879800

[Debian Bug Tracking System]

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

> # *sigh* binnmus
> notfound 879800 7:3.3.4-2
Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
No longer marked as found in versions ffmpeg/7:3.3.4-2.
> thanks
Stopping processing here.

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

Bug#877213: marked as done (node-d3-format: B-D npm not available in testing)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:30 +
with message-id 
and subject line Bug#877213: fixed in node-d3-format 1.2.0-2
has caused the Debian Bug report #877213,
regarding node-d3-format: B-D npm not available in testing
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.)


-- 
877213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-d3-color
Version: 1.0.3-1
Severity: serious
Justification: Build-Depends not satisfiable in testing
Control: block -1 with 857986
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 node-d3-format 1.2.0-1
Control: retitle -2 node-d3-format: B-D npm not available in testing
Control: block -2 with 857986
Control: reassign -3 node-d3-queue 3.0.7-1
Control: retitle -3 node-d3-queue: B-D npm not available in testing
Control: block -3 with 857986
Control: reassign -4 node-d3-selection 1.1.0-1
Control: retitle -4 node-d3-selection: B-D npm not available in testing
Control: block -4 with 857986
Control: reassign -5 d3-timer 1.0.7-1
Control: retitle -5 d3-timer: B-D npm not available in testing
Control: block -5 with 857986
Control: reassign -6  node-filesize 3.5.10+dfsg-1
Control: retitle -6 node-filesize: B-D npm not available in testing
Control: block -6 with 857986
Control: reassign -7 node-gulp-babel 7.0.0-1
Control: retitle -7 node-gulp-babel: B-D npm not available in testing
Control: block -7 with 857986
Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1
Control: retitle -8 node-babel-plugin-transform-define: B-D npm not available 
in testing
Control: block -8 with 857986
Control: reassign -9 node-babel 6.25.0+dfsg-8
Control: retitle -9 node-babel: B-D npm not available in testing
Control: block -9 with 857986
Control: reassign -10 node-babylon 6.18.0-1
Control: retitle -10 node-babylon: B-D npm not available in testing
Control: block -10 with 857986


Hi,

with npm not available in testing (and according to #857986 this will
not change in the near future), these node-* packages must be kept
out of testing, since they cannot be rebuilt in testing (regardless of
any external resources they might need additionally).


Andreas
--- End Message ---
--- Begin Message ---
Source: node-d3-format
Source-Version: 1.2.0-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-d3-format package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Oct 2017 16:52:50 +0530
Source: node-d3-format
Binary: node-d3-format
Architecture: source all
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-d3-format - Format numbers for human consumption
Closes: 877213
Changes:
 node-d3-format (1.2.0-2) unstable; urgency=medium
 .
   * Build with babel and move to main (Closes: #877213)
Checksums-Sha1:
 4c3386ddaa5aa35fbc3e621b383f334d8779b4a4 2157 node-d3-format_1.2.0-2.dsc
 d635f690a463bc37674528db09be35a07fd04699 20233 node-d3-format_1.2.0.orig.tar.gz
 9adc8d07b61f88f2a04287c119291ad878634027 2880 
node-d3-format_1.2.0-2.debian.tar.xz
 2bd246e66498d53901a3e744b2484464e1a36dd9 14922 node-d3-format_1.2.0-2_all.deb
 7ef51f0a6a35b1b89ee15a86006b9c941ebc592b 9701 
node-d3-format_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
 6baca84547e70cf55d8a289153a858c45a1daa8d4ee8c78a11a47ee3859c0c6a 2157 
node-d3-format_1.2.0-2.dsc
 20dcd7f92dcd433e9093432d13fa7f4b8b67c7ec9fe106c011a0a9d397e0b7ce 20233 
node-d3-format_1.2.0.orig.tar.gz
 3d9e0a1a35816f5976f36fd6e73c329de88d1f901bc4161c6efff0112849dbfb 2880 
node-d3-format_1.2.0-2.debian.tar.xz
 002d2a735c436a550e30cbfccdcdd052b6172411eccbe536e0a8f987a9c45b92 14922 
node-d3-format_1.2.0-2_all.deb
 b5a1573b8339039f961d3bbad8b54e44ab0b8d66e78b254b6b3deb16c4550999 9701 

Bug#877217: marked as done (node-filesize: B-D npm not available in testing)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:32 +
with message-id 
and subject line Bug#877217: fixed in node-filesize 3.5.10+dfsg-2
has caused the Debian Bug report #877217,
regarding node-filesize: B-D npm not available in testing
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.)


-- 
877217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-d3-color
Version: 1.0.3-1
Severity: serious
Justification: Build-Depends not satisfiable in testing
Control: block -1 with 857986
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 node-d3-format 1.2.0-1
Control: retitle -2 node-d3-format: B-D npm not available in testing
Control: block -2 with 857986
Control: reassign -3 node-d3-queue 3.0.7-1
Control: retitle -3 node-d3-queue: B-D npm not available in testing
Control: block -3 with 857986
Control: reassign -4 node-d3-selection 1.1.0-1
Control: retitle -4 node-d3-selection: B-D npm not available in testing
Control: block -4 with 857986
Control: reassign -5 d3-timer 1.0.7-1
Control: retitle -5 d3-timer: B-D npm not available in testing
Control: block -5 with 857986
Control: reassign -6  node-filesize 3.5.10+dfsg-1
Control: retitle -6 node-filesize: B-D npm not available in testing
Control: block -6 with 857986
Control: reassign -7 node-gulp-babel 7.0.0-1
Control: retitle -7 node-gulp-babel: B-D npm not available in testing
Control: block -7 with 857986
Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1
Control: retitle -8 node-babel-plugin-transform-define: B-D npm not available 
in testing
Control: block -8 with 857986
Control: reassign -9 node-babel 6.25.0+dfsg-8
Control: retitle -9 node-babel: B-D npm not available in testing
Control: block -9 with 857986
Control: reassign -10 node-babylon 6.18.0-1
Control: retitle -10 node-babylon: B-D npm not available in testing
Control: block -10 with 857986


Hi,

with npm not available in testing (and according to #857986 this will
not change in the near future), these node-* packages must be kept
out of testing, since they cannot be rebuilt in testing (regardless of
any external resources they might need additionally).


Andreas
--- End Message ---
--- Begin Message ---
Source: node-filesize
Source-Version: 3.5.10+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-filesize package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Oct 2017 19:42:21 +0530
Source: node-filesize
Binary: node-filesize
Architecture: source all
Version: 3.5.10+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-filesize - generate a human readable String describing the file size
Closes: 876873 877217
Changes:
 node-filesize (3.5.10+dfsg-2) unstable; urgency=medium
 .
   * Move to main (babel is in main now) (Closes: #877217)
   * Remove npm2deb templates from description (Closes: #876873)
Checksums-Sha1:
 b70be4efabcb0f37e5eed7227bf77676d5c251be 2292 node-filesize_3.5.10+dfsg-2.dsc
 a80c9df65d5c02ef57882280cc00b772873922cc 8064 
node-filesize_3.5.10+dfsg.orig.tar.xz
 9c8fc68b0c5edac437472540251748a711fa3b68 2908 
node-filesize_3.5.10+dfsg-2.debian.tar.xz
 e54e2e7d800e79ca4b9ae61feb40d13964f0fcd3 8508 
node-filesize_3.5.10+dfsg-2_all.deb
 1945c6bc992dff4452c48ab1e343ceb5583b5a1d 15052 
node-filesize_3.5.10+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 71d2c9e972b718cda09afb24fc0f63cf1ff48f4b9bc77784c262032cd8263ff7 2292 
node-filesize_3.5.10+dfsg-2.dsc
 6f2d916c7055f717cd108573a799938a3ce961b2182bdc4833496dfd5f35d9f7 8064 
node-filesize_3.5.10+dfsg.orig.tar.xz
 0156ca5d997883e741c80feaf08b9a0e4294b50dd5716d4edc20ba785c481400 2908 
node-filesize_3.5.10+dfsg-2.debian.tar.xz
 

Bug#877214: marked as done (node-d3-queue: B-D npm not available in testing)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:30 +
with message-id 
and subject line Bug#877214: fixed in node-d3-queue 3.0.7-2
has caused the Debian Bug report #877214,
regarding node-d3-queue: B-D npm not available in testing
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.)


-- 
877214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-d3-color
Version: 1.0.3-1
Severity: serious
Justification: Build-Depends not satisfiable in testing
Control: block -1 with 857986
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 node-d3-format 1.2.0-1
Control: retitle -2 node-d3-format: B-D npm not available in testing
Control: block -2 with 857986
Control: reassign -3 node-d3-queue 3.0.7-1
Control: retitle -3 node-d3-queue: B-D npm not available in testing
Control: block -3 with 857986
Control: reassign -4 node-d3-selection 1.1.0-1
Control: retitle -4 node-d3-selection: B-D npm not available in testing
Control: block -4 with 857986
Control: reassign -5 d3-timer 1.0.7-1
Control: retitle -5 d3-timer: B-D npm not available in testing
Control: block -5 with 857986
Control: reassign -6  node-filesize 3.5.10+dfsg-1
Control: retitle -6 node-filesize: B-D npm not available in testing
Control: block -6 with 857986
Control: reassign -7 node-gulp-babel 7.0.0-1
Control: retitle -7 node-gulp-babel: B-D npm not available in testing
Control: block -7 with 857986
Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1
Control: retitle -8 node-babel-plugin-transform-define: B-D npm not available 
in testing
Control: block -8 with 857986
Control: reassign -9 node-babel 6.25.0+dfsg-8
Control: retitle -9 node-babel: B-D npm not available in testing
Control: block -9 with 857986
Control: reassign -10 node-babylon 6.18.0-1
Control: retitle -10 node-babylon: B-D npm not available in testing
Control: block -10 with 857986


Hi,

with npm not available in testing (and according to #857986 this will
not change in the near future), these node-* packages must be kept
out of testing, since they cannot be rebuilt in testing (regardless of
any external resources they might need additionally).


Andreas
--- End Message ---
--- Begin Message ---
Source: node-d3-queue
Source-Version: 3.0.7-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-d3-queue package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Oct 2017 16:35:51 +0530
Source: node-d3-queue
Binary: node-d3-queue
Architecture: source all
Version: 3.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-d3-queue - Evaluate asynchronous tasks with configurable concurrency
Closes: 877214
Changes:
 node-d3-queue (3.0.7-2) unstable; urgency=medium
 .
   * Use babel to transpile and move to main (Closes: #877214)
Checksums-Sha1:
 352494193a817db5540d86a9d326721a9a96ee89 2112 node-d3-queue_3.0.7-2.dsc
 397ef616819ff6dd8fdfb48766997d921431ed80 8540 node-d3-queue_3.0.7.orig.tar.gz
 a4382aa7daf09a4e08e140bd12d4009521701c21 2916 
node-d3-queue_3.0.7-2.debian.tar.xz
 cf2c65119eafb78d1701258fb280074e6b732f5c 7830 node-d3-queue_3.0.7-2_all.deb
 8eafb470cfd446fea8d57e2202df2988f4b03a4b 9662 
node-d3-queue_3.0.7-2_amd64.buildinfo
Checksums-Sha256:
 cdeb9d7e7017093bcf91a7d66af1c1b9068aec8078ea5e27d55daa779609a12e 2112 
node-d3-queue_3.0.7-2.dsc
 54afc4a4aa02904450e48426e5d7266dffaa9a9516d3f92d8d4509fd2bc14159 8540 
node-d3-queue_3.0.7.orig.tar.gz
 bae61d2f2c7445e0f0254aba40ffd3af6166888b3058d63d148d9d7ead544210 2916 
node-d3-queue_3.0.7-2.debian.tar.xz
 993e2449bc7f3a201e9c27da5efa3bb8c1d70060670862e8126e574033e317f6 7830 
node-d3-queue_3.0.7-2_all.deb
 ee0fd6f62c3ac1d026dc145b4cc381b228fb531cf1003b31e6ec7ffb07051eac 9662 

Bug#877212: marked as done (node-d3-color: B-D npm not available in testing)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:30 +
with message-id 
and subject line Bug#877212: fixed in node-d3-color 1.0.3-2
has caused the Debian Bug report #877212,
regarding node-d3-color: B-D npm not available in testing
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.)


-- 
877212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-d3-color
Version: 1.0.3-1
Severity: serious
Justification: Build-Depends not satisfiable in testing
Control: block -1 with 857986
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 node-d3-format 1.2.0-1
Control: retitle -2 node-d3-format: B-D npm not available in testing
Control: block -2 with 857986
Control: reassign -3 node-d3-queue 3.0.7-1
Control: retitle -3 node-d3-queue: B-D npm not available in testing
Control: block -3 with 857986
Control: reassign -4 node-d3-selection 1.1.0-1
Control: retitle -4 node-d3-selection: B-D npm not available in testing
Control: block -4 with 857986
Control: reassign -5 d3-timer 1.0.7-1
Control: retitle -5 d3-timer: B-D npm not available in testing
Control: block -5 with 857986
Control: reassign -6  node-filesize 3.5.10+dfsg-1
Control: retitle -6 node-filesize: B-D npm not available in testing
Control: block -6 with 857986
Control: reassign -7 node-gulp-babel 7.0.0-1
Control: retitle -7 node-gulp-babel: B-D npm not available in testing
Control: block -7 with 857986
Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1
Control: retitle -8 node-babel-plugin-transform-define: B-D npm not available 
in testing
Control: block -8 with 857986
Control: reassign -9 node-babel 6.25.0+dfsg-8
Control: retitle -9 node-babel: B-D npm not available in testing
Control: block -9 with 857986
Control: reassign -10 node-babylon 6.18.0-1
Control: retitle -10 node-babylon: B-D npm not available in testing
Control: block -10 with 857986


Hi,

with npm not available in testing (and according to #857986 this will
not change in the near future), these node-* packages must be kept
out of testing, since they cannot be rebuilt in testing (regardless of
any external resources they might need additionally).


Andreas
--- End Message ---
--- Begin Message ---
Source: node-d3-color
Source-Version: 1.0.3-2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-d3-color package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Oct 2017 16:20:09 +0530
Source: node-d3-color
Binary: node-d3-color
Architecture: source all
Version: 1.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-d3-color - Color spaces! RGB, HSL, Cubehelix, Lab and HCL (Lch)
Closes: 877212
Changes:
 node-d3-color (1.0.3-2) unstable; urgency=medium
 .
   * Use babel to transpile (move to main section) (Closes: #877212)
Checksums-Sha1:
 64a391ac125fc1958545a59c6da15bb21698e431 2115 node-d3-color_1.0.3-2.dsc
 4356a9a1f192a220f8cd94bd7b6243cd160a323e 16729 node-d3-color_1.0.3.orig.tar.gz
 d6212916c99e6e919646cdb65b4fab51d5ef84c2 2848 
node-d3-color_1.0.3-2.debian.tar.xz
 4967a2ce04bc5712efc0579235204557a80cf604 10740 node-d3-color_1.0.3-2_all.deb
 b6ceab07e066bbf29376dab9b6d542e5479d24f0 9665 
node-d3-color_1.0.3-2_amd64.buildinfo
Checksums-Sha256:
 b3ba41db061258f33069c9d24253d7eedd61888c0fc2cd0b0b648008a2955841 2115 
node-d3-color_1.0.3-2.dsc
 dc3d7563f5ac8c7bd0c99897a7c9c12ce15b5a5dc422d18900ad2ad8caa8dcc0 16729 
node-d3-color_1.0.3.orig.tar.gz
 f6e605c7d6ae52623a374985c5688f58ef3fd8813fa7f0a3b4c13d3dcf61f146 2848 
node-d3-color_1.0.3-2.debian.tar.xz
 70ee8c17ae6472213153975a2e6fffaeba0d8c3b0b9702fd0408854a337ffcec 10740 
node-d3-color_1.0.3-2_all.deb
 7289aec778229588d97a2f408d6e388047cb027306031ef5196611e753ed9cd0 9665 

Bug#878757: marked as done (Openvswitch must started before networking servise)

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 09:00:34 +
with message-id 
and subject line Bug#878757: fixed in openvswitch 2.8.1+dfsg1-1
has caused the Debian Bug report #878757,
regarding Openvswitch must started before networking servise
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.)


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

Package: openvswitch-switch
Version: 2.6.2~pre+git20161223-3
Priority: critical

The Openvswitch daemon must be started before the network.service. 
Because when the initiation of the network started interfaces from the 
options should exist, or if you try to configure openvswitch in 
/etc/network/interfaces, then the ovs daemon must be running to execute 
commands.
Please create a systemd configuration with the option "Before: 
networking.service" for a stable version of debian.
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.8.1+dfsg1-1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openvswitch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Oct 2017 22:06:41 +0200
Source: openvswitch
Binary: openvswitch-common openvswitch-dbg openvswitch-dev openvswitch-ipsec 
openvswitch-pki openvswitch-switch openvswitch-testcontroller openvswitch-vtep 
ovn-central ovn-controller-vtep ovn-host python-openvswitch python3-openvswitch
Architecture: source amd64 all
Version: 2.8.1+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 openvswitch-common - Open vSwitch common components
 openvswitch-dbg - Debug symbols for Open vSwitch packages
 openvswitch-dev - Open vSwitch development package
 openvswitch-ipsec - Open vSwitch GRE-over-IPsec support
 openvswitch-pki - Open vSwitch public key infrastructure dependency package
 openvswitch-switch - Open vSwitch switch implementations
 openvswitch-testcontroller - Simple controller for testing OpenFlow setups
 openvswitch-vtep - Open vSwitch VTEP utilities
 ovn-central - OVN central components
 ovn-controller-vtep - OVN vtep controller
 ovn-host   - OVN host components
 python-openvswitch - Python bindings for Open vSwitch
 python3-openvswitch - Python 3 bindings for Open vSwitch
Closes: 771507 863228 863655 863661 863662 877543 878249 878757
Changes:
 openvswitch (2.8.1+dfsg1-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #878249):
 - Fixes CVE-2017-9214 (Closes: #863228).
 - Fixes CVE-2017-14970 (Closes: #877543).
 - Fixes CVE-2017-9263 (Closes: #863655).
 - Fixes CVE-2017-9264 (Closes: #863661).
 - Fixes CVE-2017-9265 (Closes: #863662).
   * Ran wrap-and-sort -bast.
   * Add libopenvswitch and libopenvswitch-dev.
   * Updated VCS URLs.
   * Switched to debhelper 10.
   * Added openstack-pkg-tools as build-depends.
   * Standards-Version is now 4.1.1.
   * Added dh-python as build-depends.
   * Added 2 debian/*.service files (Closes: #878757, #771507).
   * Added Python 3 support.
   * Added debian/README.source explaining why we're marking the version as
 +dfsg1 (ie: because we remove the upstream debian folder).
   * Removed patches.
   * Patch upstream Makefile.am to not include debian/automake.mk.
   * Remove openvswitch-test package.
   * Simplify packaging by installing all binaries in openvswitch-common.
   * Removed build-depends on dh-autoreconf, satisfied by debhelper >= 10.
   * Fixed build-depends on automake.
   * Fixed runtime depends on openvswitch-common in openvswitch-pki.
   * Removed openvswitch-test package, now provided by openvswitch-common.
   * Switch debian/copyright to parsable format.
   * Add export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow in debian/rules.
   * Removed ovn-docker package, now provided 

Bug#862837: xrdp: Package install failure - dpkg: error processing package xrdp (--configure)

[Stefan Seidel]

Package: xrdp
Version: 0.9.1-9~bpo8+1
Followup-For: Bug #862837

Hi,

upon upgrading xrdp from xrdp/0.9.1-4 to xrdp/0.9.1-9 (jessie backports), xrdp
still doesn't start. I get these errors in the journal:

Failed at step RUNTIME_DIRECTORY spawning /bin/sh: File exists
xrdp.service: control process exited, code=exited status=233

I believe there are two issues that prevent the start:

1. /var/run/xrdp needs to be chgrp'd to xrdp, otherwise xrdp will never be able
to start (that bug is actually present for a long time, I've always worked
around it using a Puppet rule)
2. I needed to apply the workaround mentioned in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=854548;msg=30 to finally make it start up

I hope this is helpful.

Stefan



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

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

Versions of packages xrdp depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u10
ii  libfuse2 2.9.3-15+deb8u2
ii  libjpeg62-turbo  1:1.3.1-12
ii  libopus0 1.1-2
ii  libpam0g 1.1.8-3.1+deb8u2+b1
ii  libssl1.0.0  1.0.1t-1+deb8u6
ii  libx11-6 2:1.6.2-3
ii  libxfixes3   1:5.0.1-2+b2
ii  libxrandr2   2:1.4.2-1+b1
ii  lsb-base 4.1+Debian13+nmu1
ii  ssl-cert 1.0.35

Versions of packages xrdp recommends:
pn  fuse  
ii  xorgxrdp  0.9.1-9~bpo8+1

Versions of packages xrdp suggests:
pn  guacamole  

Versions of packages xorgxrdp depends on:
ii  libc6  2.19-18+deb8u10
pn  xorg-input-abi-21  
ii  xserver-xorg-core [xorg-video-abi-18]  2:1.16.4-1+deb8u2

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+7

Versions of packages xrdp is related to:
pn  vnc-server   
pn  xserver-xorg-legacy  

-- Configuration Files:
/etc/pam.d/xrdp-sesman changed [not included]

-- debconf-show failed

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
Severity set to 'serious' from 'normal'
> notfound -1 7:3.3.4-2+b1
Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
Ignoring request to alter found versions of bug #879800 to the same values 
previously set
> found -1 7:3.4-1
Bug #879800 [ffmpeg] ffmpeg: Test fails for ffmpeg 3.4 in imx6 (cubox-i)
Marked as found in versions ffmpeg/7:3.4-1.

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

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Raphael Hertzog]

Hello Kurt,

On Fri, 22 Sep 2017, Kurt Roeckx wrote:
> I have to admit that I didn't consider derivatives that take a
> snapshot of testing, and we also seem to have a large amount of
> people that do use testing. My intention was to target the more
> advanced users, and having it in testing might be affecting more
> people than I thought.
> 
> So I am considering to only disable it in unstable and not in
> testing.

Any progress on this?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Processed: your mail

[Debian Bug Tracking System]

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

> block 866335 by 813083 867028 866504 866555 866700 799635 867010 800709
Bug #866335 [release.debian.org] transition: python3-defaults
866335 was blocked by: 872052 862431 866575
866335 was not blocking any bugs.
Added blocking bug(s) of 866335: 867010, 867028, 866504, 866700, 800709, 
866555, 813083, and 799635
> thanks
Stopping processing here.

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

Bug#871232: marked as done (caffe-contrib: FTBFS with GCC-7: bits/std_abs.h:101:3: error: unknown type name '__float128')

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 07:04:03 +
with message-id 
and subject line Bug#871232: fixed in caffe-contrib 1.0.0-4
has caused the Debian Bug report #871232,
regarding caffe-contrib: FTBFS with GCC-7: bits/std_abs.h:101:3: error: unknown 
type name '__float128'
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.)


-- 
871232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffe-contrib
Version: 1.0.0-3
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

caffe-contrib FTBFS since GCC-7 was made the default compiler:

[...]
[  0%] Building CXX object 
src/caffe/CMakeFiles/caffeproto.dir/__/__/include/caffe/proto/caffe.pb.cc.o
cd /build/caffe-contrib-1.0.0/caffe_cuda_build/src/caffe && 
/usr/bin/clang++-3.8  -DCAFFE_VERSION=1.0.0 
-I/build/caffe-contrib-1.0.0/caffe_cuda_build/include -I/usr/include/opencv 
-I/build/caffe-contrib-1.0.0/caffe
_cuda_build  -g -O2 -fdebug-prefix-map=/build/caffe-contrib-1.0.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall  -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Wall -Wno-sign-compare -Wno-uninitialized 
-O3 -DNDEBUG   -o 
CMakeFiles/caffeproto.dir/__/__/include/caffe/proto/caffe.pb.cc.o -c 
/build/caffe-contrib-1.0.0/caffe_cuda_build/include/caffe/proto/caffe.pb.cc
In file included from 
/build/caffe-contrib-1.0.0/caffe_cuda_build/include/caffe/proto/caffe.pb.cc:5:
In file included from 
/build/caffe-contrib-1.0.0/caffe_cuda_build/include/caffe/proto/caffe.pb.h:9:
In file included from /usr/include/google/protobuf/stubs/common.h:40:
In file included from /usr/include/google/protobuf/stubs/port.h:35:
In file included from 
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/stdlib.h:36:
In file included from 
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/cstdlib:77:
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/bits/std_abs.h:101:3:
 error: unknown type name '__float128'
  __float128
  ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.1.0/../../../../include/c++/7.1.0/bits/std_abs.h:102:7:
 error: unknown type name '__float128'
  abs(__float128 __x)
  ^
2 errors generated.
src/caffe/CMakeFiles/caffeproto.dir/build.make:77: recipe for target 
'src/caffe/CMakeFiles/caffeproto.dir/__/__/include/caffe/proto/caffe.pb.cc.o' 
failed
make[5]: *** 
[src/caffe/CMakeFiles/caffeproto.dir/__/__/include/caffe/proto/caffe.pb.cc.o] 
Error 1


This looks related to #871011 in clang-3.8 (clang-3.9 is fine).


Cheers,

Andreas


caffe-contrib_1.0.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: caffe-contrib
Source-Version: 1.0.0-4

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated caffe-contrib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Oct 2017 05:07:43 +
Source: caffe-contrib
Binary: caffe-cuda caffe-tools-cuda libcaffe-cuda1 libcaffe-cuda-dev 
python3-caffe-cuda
Architecture: source amd64
Version: 1.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 caffe-cuda - Fast, open framework for Deep Learning (Meta)
 caffe-tools-cuda - Tools for fast, open framework for Deep Learning (CUDA)
 libcaffe-cuda-dev - development files for Caffe (CUDA)
 libcaffe-cuda1 - library of Caffe, deep leanring framework (CUDA)
 python3-caffe-cuda - Python3 interface of Caffe (CUDA)
Closes: 871232 873405
Changes:
 caffe-contrib (1.0.0-4) unstable; urgency=medium
 .
   * Change compiler from Clang-3.8 back to GCC-5. (Closes: #871232, #873405)
 Although the GCC-5 removal will trigger a new RC bug, however at
 least this change makes the package buildable.
   * Update my name in 

Bug#877541: [pkg-go] Bug#877541: prometheus FTBFS on i386: FAIL github.com/prometheus/prometheus/storage/local [build failed]

[Martín Ferrari]

Upstream has already provided a patch, and I can confirm it solves the
issue:

diff --git a/src/cmd/compile/internal/x86/387.go
b/src/cmd/compile/internal/x86/387.go
index cdac000..7a36224 100644
--- a/src/cmd/compile/internal/x86/387.go
+++ b/src/cmd/compile/internal/x86/387.go
@@ -46,6 +46,9 @@
case ssa.Op386MOVSSloadidx1, ssa.Op386MOVSDloadidx1:
p.From.Scale = 1
p.From.Index = v.Args[1].Reg()
+   if p.From.Index == x86.REG_SP {
+   p.From.Reg, p.From.Index = p.From.Index, 
p.From.Reg
+   }
case ssa.Op386MOVSSloadidx4:
p.From.Scale = 4
p.From.Index = v.Args[1].Reg()
@@ -95,6 +98,9 @@
case ssa.Op386MOVSSstoreidx1, ssa.Op386MOVSDstoreidx1:
p.To.Scale = 1
p.To.Index = v.Args[1].Reg()
+   if p.To.Index == x86.REG_SP {
+   p.To.Reg, p.To.Index = p.To.Index, p.To.Reg
+   }
case ssa.Op386MOVSSstoreidx4:
p.To.Scale = 4
p.To.Index = v.Args[1].Reg()


On 24/10/17 19:44, Martín Ferrari wrote:
> forwarded 877541 https://github.com/golang/go/issues/22429
> thanks
> 
> I have opened an issue in upstream's tracker:
> https://github.com/golang/go/issues/22429
> 


-- 
Martín Ferrari (Tincho)

Bug#879791: marked as done (golang-etcd-server-dev: New build dependency does not exist in Debian (golang-github-x-sys-dev))

[Debian Bug Tracking System]

Your message dated Thu, 26 Oct 2017 06:48:47 +
with message-id 
and subject line Bug#879791: fixed in etcd 3.2.9+dfsg-2
has caused the Debian Bug report #879791,
regarding golang-etcd-server-dev: New build dependency does not exist in Debian 
(golang-github-x-sys-dev)
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.)


-- 
879791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-etcd-server-dev
Version: 3.2.9+dfsg-1
Justification: fails to build from source (but built successfully in the past)
Severity: serious

While attempting to do some package maintenance, I ran into the
following problem:

The following packages have unmet dependencies:
   golang-etcd-server-dev : Depends: golang-github-x-sys-dev which is a
   virtual package and is not provided by any available package

It seems a new build dependency was added to etcd which does not currently exist
in Debian. I also noticed that there are unpushed commits (pristine-tar).


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

Kernel: Linux 4.11.0-1-amd64 (SMP w/16 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 golang-etcd-server-dev depends on:
ii  dh-golang  1.23
ii  golang-any 2:1.8~3
pn  golang-github-bgentry-speakeasy-dev
pn  golang-github-boltdb-bolt-dev  
pn  golang-github-cockroachdb-cmux-dev 
pn  golang-github-coreos-go-semver-dev 
pn  golang-github-coreos-go-systemd-dev
pn  golang-github-coreos-pkg-dev   
pn  golang-github-dgrijalva-jwt-go-v3-dev  
pn  golang-github-dustin-go-humanize-dev   
pn  golang-github-ghodss-yaml-dev  
pn  golang-github-gogo-protobuf-dev
pn  golang-github-golang-groupcache-dev
pn  golang-github-google-btree-dev 
pn  golang-github-grpc-ecosystem-go-grpc-prom  
pn  golang-github-grpc-ecosystem-grpc-gateway  
pn  golang-github-jonboulle-clockwork-dev  
pn  golang-github-kr-pty-dev   
pn  golang-github-mattn-go-runewidth-dev   
pn  golang-github-olekukonko-tablewriter-dev   
pn  golang-github-prometheus-client-golang-de  
pn  golang-github-prometheus-common-dev
pn  golang-github-spf13-cobra-dev  
pn  golang-github-spf13-pflag-dev  
pn  golang-github-ugorji-go-codec-dev  
pn  golang-github-urfave-cli-dev   
pn  golang-github-x-sys-dev
pn  golang-github-xiang90-probing-dev  
pn  golang-golang-x-crypto-dev 
ii  golang-golang-x-net-dev1:0.0+git20170629.c81e7f2+dfsg-1
pn  golang-golang-x-time-dev   
pn  golang-google-grpc-dev 
pn  golang-gopkg-cheggaaa-pb.v1-dev
pn  golang-goprotobuf-dev  
pn  golang-procfs-dev  

golang-etcd-server-dev recommends no packages.

golang-etcd-server-dev suggests no packages.
--- End Message ---
--- Begin Message ---
Source: etcd
Source-Version: 3.2.9+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Michael Lustfield  (supplier of updated etcd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Oct 2017 17:48:26 -0500
Source: etcd
Binary: etcd etcd-server etcd-client golang-etcd-server-dev
Architecture: source
Version: 3.2.9+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Michael Lustfield 
Description:
 etcd   - Transitional package for etcd-client and