Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Andreas Tille]

Hi Ole,

> the attached patch fixes the FTBFS. What is the schedule to fix the
> other problems with statsimage -- especially pandas?

I learned that NeuroDebian is happy about team uploads / NMUs - so
I think its fine if you upload your patch.

Kind regards

Andreas.

PS: If you are not convinced and there is no response from Yaroslav or
Michael in the next 24 hours - well, people are occupied by real life
these days, yust tell me and I'd upload.

-- 
http://fam-tille.de

Bug#849308: wireguard: Wireguard should not transition to stable yet

[Daniel Kahn Gillmor]

Source: wireguard
Version: 0.0.20161223-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Wireguard appears to be stable and reliable enough to distribute in
debian unstable, to get more widespread testing than would arise from
distribution in experimental alone.

However, the on-wire format might still change, leading to potential
interop issues, and upstream isn't yet willing to maintain a stable
branch in the face of security issues (which is understandable given
the age of the project.

So this bug report is a placeholder to keep it from migration.  Feel
free to comment here!

   --dkg

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 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)

Bug#844034: Any intend to fix this soon

[Andreas Tille]

Hi Afif,

On Sat, Dec 24, 2016 at 09:47:56PM -0800, Afif Elghraoui wrote:
> > Its no real problem.  I think it will not happen to frequently since the
> > situation to save package for upcoming releases is only every second
> > year - perhaps posting the fact you are working in a separate branch
> > would help in such cases.
> 
> Fair enough. I thought it might have been sufficient to post updates to
> the upstream tracker since the bug was marked as forwarded.

I admit I'm not happy about the BTS feature which moves "Forwarded bugs
-- Serious" below "Outstanding bugs -- Wishlist items".  I would prefer
if these would stay on top of the bugs page.  Since I forget this all
the time I was stumbling about this quite late in our bug squashing
effort.  So I most probably over reacted yesterday a bit without diving
more into the details of the issue.
 
> >  Feel free to replace everything I did by your
> > probably more advanced changes since you know the internals way better.
> > I also do not consider my time terribly wasted since I now have some
> > insight into these packages.
> 
> Thanks.

I should explicitly say "also cme formating changes". ;-)
 
> As a quick update (also posted to the upstream tracker), some changes in
> blasr 5's handling of SAM/BAM files is causing the main problems now.
> Fixing it in pbhoney would require some more intrusive changes, which I
> could probably handle, but I don't think it would be a good idea to
> proceed without upstream's cooperation on this. It's possible that
> pbsuite will not be released with Stretch because of this.

That's OK.  We will manage to get several new packages into Stretch and
others are just missing.  Backports will help users until Stretch+1. :-)
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#844034: Any intend to fix this soon

[Afif Elghraoui]

Hi, Andreas,

على السبت 24 كانون الأول 2016 ‫11:34، كتب Andreas Tille:
> On Sat, Dec 24, 2016 at 07:24:22AM -0800, Afif Elghraoui wrote:
>> I'm really sad to see the duplication of effort when I was so
>> particular to make sure my work was pushed :(. Is there a way we can
>> avoid this in the future?
> 
> Its no real problem.  I think it will not happen to frequently since the
> situation to save package for upcoming releases is only every second
> year - perhaps posting the fact you are working in a separate branch
> would help in such cases.

Fair enough. I thought it might have been sufficient to post updates to
the upstream tracker since the bug was marked as forwarded.

>  Feel free to replace everything I did by your
> probably more advanced changes since you know the internals way better.
> I also do not consider my time terribly wasted since I now have some
> insight into these packages.
> 

Thanks.

As a quick update (also posted to the upstream tracker), some changes in
blasr 5's handling of SAM/BAM files is causing the main problems now.
Fixing it in pbhoney would require some more intrusive changes, which I
could probably handle, but I don't think it would be a good idea to
proceed without upstream's cooperation on this. It's possible that
pbsuite will not be released with Stretch because of this.

Thanks and regards
Afif

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

Bug#733422: marked as done (hyde: FTBFS: dpkg-buildpackage: dpkg-source: error: unrepresentable changes to source)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 05:33:25 +
with message-id 
and subject line Bug#733422: fixed in hyde 0.8.5a1-4.1
has caused the Debian Bug report #733422,
regarding hyde: FTBFS: dpkg-buildpackage: dpkg-source: error: unrepresentable 
changes to source
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.)


-- 
733422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hyde
Version: 0.8.5a1-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_clean
> rm -rf hyde.egg-info
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>  dpkg-source -b hyde-0.8.5a1
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building hyde using existing ./hyde_0.8.5a1.orig.tar.gz
> dpkg-source: error: cannot represent change to distribute-0.6.14-py2.7.egg: 
> binary file contents changed
> dpkg-source: error: add distribute-0.6.14-py2.7.egg in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to distribute-0.6.14.tar.gz: 
> binary file contents changed
> dpkg-source: error: add distribute-0.6.14.tar.gz in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b hyde-0.8.5a1 gave error exit status 2
> 
> Build finished at 20131227-0319

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/12/26/hyde_0.8.5a1-4_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated hyde 
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, 23 Dec 2016 02:46:43 -0200
Source: hyde
Binary: hyde
Architecture: source
Version: 0.8.5a1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Julien Danjou 
Changed-By: Joao Eriberto Mota Filho 
Description:
 hyde   - static website generator with the power of Django templates
Closes: 733422
Changes:
 hyde (0.8.5a1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10.
   * Bumped Standards-Version to 3.9.8.
   * Don't use the deprecated python-distribute module, use setuptools
 directly. This fixes a FTBFS. Thanks to Andreas Moog
 . (Closes: #733422)
   * debian/watch: created.
Checksums-Sha1:
 f26a319b5a4a29a47de706549ffa937c710ae46b 1937 hyde_0.8.5a1-4.1.dsc
 ebda92c0ba98da6c8404a0a2ae70fd1edb184d4b 763744 hyde_0.8.5a1-4.1.debian.tar.xz
Checksums-Sha256:
 198926052461002ee21061ecaf5ebf7cd1aec7c7130a3e571a9b3d7ae8b4c2d3 1937 
hyde_0.8.5a1-4.1.dsc
 27d9dc44981d818aca45427860e81463d3f31e7cd03fc9cd8c5f53c9f8cc6379 763744 
hyde_0.8.5a1-4.1.debian.tar.xz
Files:
 2fdb3de4c1538040c3962a89fb44c7bc 1937 web extra hyde_0.8.5a1-4.1.dsc
 3fe3e2fb1daadcbce1d453f1aab3228b 763744 web extra 
hyde_0.8.5a1-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcrx8ACgkQ3mO5xwTr

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Andres Salomon]

On December 24, 2016 7:24:00 PM PST, Paul Wise  wrote:
>On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote:
>
>> Thanks for the patch.  Given that OLPC isn't really alive any more,
>> I'm thinking the OLPC packages should probably just be removed from
>the
>> archive for Stretch.  Popcon shows exactly 1 installation of this
>> package.. https://qa.debian.org/popcon.php?package=olpc-xo1
>
>I think you will find that OLPC is still active and recently made a
>release:
>
>http://lists.laptop.org/pipermail/devel/2016-December/thread.html
>
>They also have a Debian derivative:
>
>https://wiki.debian.org/Derivatives/Census/OLPC
>
>I've asked James to respond to your mail.
>


I meant OLPC the hardware organization. I'm glad to see James is still 
producing Fedora-based images for legacy hardware.  I'm pretty sure they 
haven't produced XO-1s in close to a decade, and that us what my packages are 
for.  XO-1.5 and XO-4 were never supported without additional hacks.

That said, I can orphan the packages; I just don't see much point with such old 
hardware and the lack of package users.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#828583: marked as done (uhub: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 05:04:33 +
with message-id 
and subject line Bug#828583: fixed in uhub 0.4.1-3.1
has caused the Debian Bug report #828583,
regarding uhub: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uhub
Version: 0.4.1-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/uhub_0.4.1-3_amd64-20160529-1547

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: uhub
Source-Version: 0.4.1-3.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated uhub 
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, 23 Dec 2016 02:27:45 -0200
Source: uhub
Binary: uhub
Architecture: source
Version: 0.4.1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Boris Pek 
Changed-By: Joao Eriberto Mota Filho 
Description:
 uhub   - High performance Advanced Direct Connect p2p hub
Closes: 828583
Changes:
 uhub (0.4.1-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10.
   * Bumped Standards-Version to 3.9.8.
   * patches/openssl1.1.patch: added to provide compatibility with OpenSSL 1.1.
 Thanks to Reiner Herrmann . (Closes: #828583)
Checksums-Sha1:
 e605a923fef04d3759d7c878dcd944d602b7b4cd 1818 uhub_0.4.1-3.1.dsc
 dd42c56afefaad764d74f094a824bd0b2d67b339 6240 uhub_0.4.1-3.1.debian.tar.xz
Checksums-Sha256:
 e3088abd6e951ac870b1e22caf928173cff54a3fe4b9acd7fdf979c1cb391df4 1818 
uhub_0.4.1-3.1.dsc
 d51603d17c0e19131ebb948bef3402f9c62ac527dcfde301c9f6547ed90201fe 6240 
uhub_0.4.1-3.1.debian.tar.xz
Files:
 ba02b60b3a5a116839e7818a0b0cd352 1818 net optional uhub_0.4.1-3.1.dsc
 d9fc5fde4f9ef01ebd91d8f51343f729 6240 net optional uhub_0.4.1-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcqWgACgkQ3mO5xwTr
6e9aQA/8D2NfMhxsoGczznM2It426uIHFWBBAl1vzuHfw+dGihAKFkTpBOAW4v8X
L6w76400ADUq7/5qCAEtdFbDjNS/rT/pjLvx0uZ17cmbg41PKnb0psR5Gd6arwGV
eWJWF8mj7o44kgqATbTXuEWHpacaz+R5VZDvbjXBV4+B3S3so8664L5AEb0G1bqU
3/pQn2hrFyM2IUbyzmQN0TzoYe+dNCSokQzHg1waWQHFHx/xMJeN6PgiZnFqhBsg
t62165Uwkszfmj7oGNs9PXUNd9RiK0ILJiZeecJsqlkwolaEio0JUTllxL1u5HcK
b05uTwWdenAa4IKRFlUAmNqP2QzVHtGSkNnyLSBcA1zUeYwLwCya8b00oyWh9cOe
pYExf5E3hygmlCeT6OQIuNdPztb7JBoc2XeOk7i0QxkmMEl/KGN/4foIR6yDkGnY
SuowcwdzDELg02mZHGlhmsXJJ805bDoQNoPWabPoXksPZS/LvirzsC8LEHnD6bUw
0NU+YIoeNqbmWS87J/Z7RvAUIesjphAi2PTI1xPXurS6TUbjKlcjqsK1dOSMlwqC
fMdRO37jp923pFh8oYu3/IHmhYBujmDy5eh0nZJta7ng3nz2dOhKQKoAnO8TM92i
LsUxoIlrSCET/krhgi5tiOdvXnCL7YT/u6SXc2aq0axt5ezaU0k=
=avXv
-END PGP SIGNATURE End Message ---

Bug#817722: marked as done (whereami: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 04:36:25 +
with message-id 
and subject line Bug#817722: fixed in whereami 0.3.34-0.4
has caused the Debian Bug report #817722,
regarding whereami: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: whereami
Severity: important
Usertags: compat-4-removal

Hi,

The package whereami uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: whereami
Source-Version: 0.3.34-0.4

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated whereami 
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, 23 Dec 2016 02:00:16 -0200
Source: whereami
Binary: whereami
Architecture: source
Version: 0.3.34-0.4
Distribution: unstable
Urgency: medium
Maintainer: Andrew McMillan 
Changed-By: Joao Eriberto Mota Filho 
Description:
 whereami   - Automatically reconfigure your (laptop) system for a new location
Closes: 817722
Changes:
 whereami (0.3.34-0.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817722)
   * debian/control: bumped Standards-Version to 3.9.8.
   * debian/rules: disabled the DH_VERBOSE option.
Checksums-Sha1:
 df7b3680120cc5d72a288840f3304365c8c43ff1 1684 whereami_0.3.34-0.4.dsc
 f97a199c6073c939cda2dd61843fdac97e5ba4d8 70571 whereami_0.3.34.orig.tar.gz
 d3af2a60d9f414c7d7be384a5059ce0420252a4b 570 whereami_0.3.34-0.4.diff.gz
Checksums-Sha256:
 421de2aa3b8f9ac3732e4c01f419af7743c8b0d18be4ce9be2124231fbaa6d71 1684 
whereami_0.3.34-0.4.dsc
 f204281dc8a807200e72cb778d223cb60afd214305b3690166fb949bfc1e20d5 70571 
whereami_0.3.34.orig.tar.gz
 bbd1a22f34aac8944f51441d86712dfec167eaab8f8b5f04642ffd305cf7fdbd 570 
whereami_0.3.34-0.4.diff.gz
Files:
 ca0a880ba82c40cbdcc16fc457a0ab36 1684 net extra whereami_0.3.34-0.4.dsc
 51472d9b4ded49d6bd6fe37a6457bf61 70571 net extra whereami_0.3.34.orig.tar.gz
 594df51338b691a1ff39ae3af43dabff 570 net extra whereami_0.3.34-0.4.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhco54ACgkQ3mO5xwTr
6e8BVQ//eQbh7irUT3rIxxqR+SLvTKSJpAVv66mfuVR58i9Y70fm31emd1gjcfin
9mE8HzAUTPoCW+mLIl7dtyjYfYbh7KbNay6xV+1XRSLKLiSHhYm40tOidFwJ5IHM
fl981Ia8doTh5YDFxXfEhZV3ao8QUnTiquia3mduLbvVYQewoTIpB/rQ4gS2c1IM
ekpk2qX40FghbKLY4+PTF7s6TV+HfQAMczBbUvhQZMLIPpqYa67kD8ua1+0sGFHl
1DBEr221lNfCjTsyBIHGPtVYatBoJ1AwuD2b87qwWteTf5A5LGC8oJBP0KYsFRIt
1t6iorXLAQsnCpLFj+Qi6eDRUhDUR+j1J8NMJLBPQnWDYC8DaqluyQSxrEMrfss2
P7Wze1hzHTKGNHsFjStL5FS7Bms4oHFLOMuyD2DtAVopsEfPL96Yjt3plGsMfzLq
hTwTLVxEiQnhffsiZy1+251DsxdXPNE2s7qOFi9bGTwRz8AhQQ0ka0c0sheXBWME
YFXbG2OHmhDtHVLJJU6S2OqxJ3QDTrLdwvlyytejNEFghnM88hbqyrf5FN1IOkYt
xfvhdW2UGg9fHZ3Db3M0KaEhfvG/uuKvL8kIlhukljNmEYISJZSgiYxCcXeCeajb
GsJk/wRWmVgjqA0QEkjr/R4QRRLqmCbGVMq1UmnJjo94cit2z9o=
=c8Ul
-END PGP SIGNATURE End Message ---

Bug#849303: rear: FTBFS: asciidoc: Command not found

[Aaron M. Ucko]

Source: rear
Version: 1.19+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of rear in minimal environments geared for building only the
architecture-dependent rear binary package (as on the autobuilders)
have been failing:

  asciidoc -b docbook -d manpage rear.8.adoc
  make[3]: asciidoc: Command not found
  Makefile:34: recipe for target 'rear.8.xml' failed
  make[3]: *** [rear.8.xml] Error 127
  make[3]: Leaving directory '/«BUILDDIR»/rear-1.19+dfsg/doc'
  Makefile:90: recipe for target 'man' failed
  make[2]: *** [man] Error 2
  make[2]: Leaving directory '/«BUILDDIR»/rear-1.19+dfsg'
  debian/rules:13: recipe for target 'override_dh_auto_build-arch' failed
  make[1]: *** [override_dh_auto_build-arch] Error 2
  make[1]: Leaving directory '/«BUILDDIR»/rear-1.19+dfsg'
  debian/rules:5: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Please move asciidoc from Build-Depends-Indep to Build-Depends, since
the man page (correctly) goes in the main rear package.

Thanks!

FTR, I'm reporting this bug as a regression because it would affect binNMUs.

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

Bug#817684: marked as done (syrep: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 04:04:11 +
with message-id 
and subject line Bug#817684: fixed in syrep 0.9-4.3
has caused the Debian Bug report #817684,
regarding syrep: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syrep
Severity: important
Usertags: compat-4-removal

Hi,

The package syrep uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: syrep
Source-Version: 0.9-4.3

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated syrep 
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, 23 Dec 2016 01:26:31 -0200
Source: syrep
Binary: syrep
Architecture: source
Version: 0.9-4.3
Distribution: unstable
Urgency: medium
Maintainer: Marvin Stark 
Changed-By: Joao Eriberto Mota Filho 
Description:
 syrep  - A generic file repository synchronization tool
Closes: 817684
Changes:
 syrep (0.9-4.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817684)
   * debian/control:
   - Added the ${misc:Depends} variable to Depends field.
   - Bumped Standards-Version to 3.9.8.
   - Moved Homapage field to source block.
   * debian/watch: created.
Checksums-Sha1:
 2b1eff37ce5b3c69a447899664bbfeb9d3eef961 1792 syrep_0.9-4.3.dsc
 c51f5769f7d29d51b89f19707d6e4ec5efbb17ef 113432 syrep_0.9-4.3.diff.gz
Checksums-Sha256:
 fb4cbf36c324886598c5140276733e90b2f229a767127837afadcf5c481032b0 1792 
syrep_0.9-4.3.dsc
 f1df66aada63003d7f52a1c89a6145870133a2d8546f55f07d7980826dc92212 113432 
syrep_0.9-4.3.diff.gz
Files:
 ad35de7a58b6520af4513f2fed15588a 1792 utils optional syrep_0.9-4.3.dsc
 ab232ad35043b6791f65348837307f60 113432 utils optional syrep_0.9-4.3.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcm0gACgkQ3mO5xwTr
6e8g3A/+L/0Js50Dv4T0Qfq2KRpG66ZbDEXMvoQJ9Of2tzaKruJSQk32YF1OXcGq
8V+Z4yHMP4SQomrcE/RZjKvvmVRqhtDu91QmSD9C+2HiZe0OFGJ571rGq1uzy35x
39G96eH/5N3GXpd4CU/JtNwQftIaKx/CAJtdfh7DlY7JhAPdZ/ieKCnRWMdWRFJb
Yl+085G+ALaPkQl02Cb25L6sanKLDpT9+MRrQW2FOfxm4SZiCtWJXTZtoi71q1im
hcoLIq/SSzxM9KLXaFeqF4hYxizQCkUpQkTq4K2mKdK2dvI59j4S8OJL4/zQBjCA
3vAh4vp6RG03l9iKVGHfJtSQ1CbWJWCTvB0//ufBLdX9iDJ4hrTSz555PKVZ0F0V
GsKGwd1WVH9hOo6lxQc9gIjK6uCD1wsnS/QLK8ZAOJTAMDW36VlhtCCXlMdS1/qE
MvJmo7QVVI79L5ss9RlVvTPxklU4y6pJAXMlL1BmMFTqx3nKc9GdjlKPZCCO8+/r
wgUbjLp7huJbSzDmmcjmFfkgNo94iswyIptEKDVLe8YsuYJUx2JE0D06BSSLKscY
rBXnF7slkOq3edQ0mMqapVBhewjz65LbVu1Z95i6/bckCeUvzeUq+hligjqeEem4
rc/zLTq4frmqV+VYGmxv/1+KeaTMR5uC0cUXgsO62FPmKBSHlrs=
=KS//
-END PGP SIGNATURE End Message ---

Bug#817714: marked as done (vdk-doc: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 03:49:46 +
with message-id 
and subject line Bug#817714: fixed in vdk-doc 1.2.4-4.1
has caused the Debian Bug report #817714,
regarding vdk-doc: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdk-doc
Severity: important
Usertags: compat-4-removal

Hi,

The package vdk-doc uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: vdk-doc
Source-Version: 1.2.4-4.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated vdk-doc 
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, 23 Dec 2016 00:56:07 -0200
Source: vdk-doc
Binary: vdk-doc
Architecture: source
Version: 1.2.4-4.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt 
Changed-By: Joao Eriberto Mota Filho 
Description:
 vdk-doc- The Visual Development Kit C++ library
Closes: 817714
Changes:
 vdk-doc (1.2.4-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817714)
   * debian/control:
   - Added a Homepage field.
   - Added the ${misc:Depends} variable to Depends field.
   - Bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 7bbcd250b2947d1911a6b1cf932dd0df5b02e8bf 1679 vdk-doc_1.2.4-4.1.dsc
 efec4e218b9968da22771dd358ab8e71278e84f9 1650 vdk-doc_1.2.4-4.1.diff.gz
Checksums-Sha256:
 e665ef2605d13fe169178208b5c3420640633afc8ee4fbdbe9707b1128097255 1679 
vdk-doc_1.2.4-4.1.dsc
 f412ef7cc6c1fca8320618502e5671d395c7022185721de65548c2e7558fe83d 1650 
vdk-doc_1.2.4-4.1.diff.gz
Files:
 bf4014dacf325be7f9d69daf8dbd6411 1679 - optional vdk-doc_1.2.4-4.1.dsc
 c41510bdb328c03efdc6b92c4a15885d 1650 - optional vdk-doc_1.2.4-4.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhclZUACgkQ3mO5xwTr
6e+BChAArAqbcvPeyREDVhTrY+6SUwW3YptQq0yzDqDxXMy+zSDh4Tiptsmem3OZ
255Led7w93gFrk+J2b1I1PuHsPUJ7Pa2kaTMAhhKWCVnpcfCLQQ/2S7BoRqeNN9+
qfwhGi7jVREp1iC21F+tGdgHOqYrRaZwgDoJ1y+ypFT+mhjX3TOtnJ+ajHuFu+su
9CL0PppwmPYekg2o8QkGrfdPkmY5wBZeihJ7Busbteuf7GP7e4mDevjCsnsiyGY6
yDbA2+i+LliH7LAODiXZ0V4Dw7u66TEFh3W2LcsLFEwa2DLpQ7Wtxsjs0iumZI9x
yJ2moQj3RzehIM/ooACWkuibZWO5P9+pcwkRUvsaumVaLRGqf8MktcribBP1wJNK
9SculasbUcajKvK1Zr6zQkx8G2vqyXpaU19hO4niGGjFF9OtwFomqvnDbt5Lw6K8
pb8w7IUkeXZhkb5QpL6MxACCimV+yW2kMFXYe/iVg48H7OgEy1HQT7XHPB/Dfug6
llhnPuwBiuIItnbTp6hbGbpcEMSjr7a6ZTo8GrAIQlu5w0FT6qTiQmlpejPkg19Y
AhBX8Ma0tIEsi5i0OO9r1h/o7U5bXLZJ62u4SfgL1S7xKZO2wqt/Zf/b7xN8KYLy
lHVJ4P69jTji1/XxxX/4po6L1guNWDqTK+UdlnbloDssDI3Ze1I=
=ngNc
-END PGP SIGNATURE End Message ---

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Paul Wise]

On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote:

> Thanks for the patch.  Given that OLPC isn't really alive any more,
> I'm thinking the OLPC packages should probably just be removed from the
> archive for Stretch.  Popcon shows exactly 1 installation of this
> package.. https://qa.debian.org/popcon.php?package=olpc-xo1

I think you will find that OLPC is still active and recently made a release:

http://lists.laptop.org/pipermail/devel/2016-December/thread.html

They also have a Debian derivative:

https://wiki.debian.org/Derivatives/Census/OLPC

I've asked James to respond to your mail.

I expect most OLPC XO1 devices exist in offline mode and couldn't
submit to popcon even if they were configured to.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Andres Salomon]

On Sat, 24 Dec 2016 20:26:06 -0500
Logan Rosen  wrote:

> Control: tags -1 patch
> 
> Dear Maintainer,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * debian/compat: Bump to 10.
>   * debian/control:
> - Build-depend on debhelper (>= 10).
> - Depend on ${misc:Depends}.
> 
> Thanks for considering the patch.
> 
> Logan Rosen


Thanks for the patch.  Given that OLPC isn't really alive any more,
I'm thinking the OLPC packages should probably just be removed from the
archive for Stretch.  Popcon shows exactly 1 installation of this
package.. https://qa.debian.org/popcon.php?package=olpc-xo1

Bug#817639: python-tcpwrap: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * debian/compat: Bump to 10.
  * debian/control: Build-depend on debhelper (>= 10) and dh-python.
  * debian/rules: Use dh_prep instead of dh_clean -k.

Thanks for considering the patch.

Logan Rosen
diff -u python-tcpwrap-0.2/debian/compat python-tcpwrap-0.2/debian/compat
--- python-tcpwrap-0.2/debian/compat
+++ python-tcpwrap-0.2/debian/compat
@@ -1 +1 @@
-4
+10
diff -u python-tcpwrap-0.2/debian/rules python-tcpwrap-0.2/debian/rules
--- python-tcpwrap-0.2/debian/rules
+++ python-tcpwrap-0.2/debian/rules
@@ -27,13 +27,13 @@
 install-indep:
 	dh_testdir
 	dh_testroot
-	dh_clean -k -i
+	dh_prep
 	dh_installdirs -i
 
 install-arch: build-arch
 	dh_testdir
 	dh_testroot
-	dh_clean -k -s
+	dh_prep
 	dh_installdirs -s
 	set -e; \
 	for v in $(PYVERS); do \
diff -u python-tcpwrap-0.2/debian/control python-tcpwrap-0.2/debian/control
--- python-tcpwrap-0.2/debian/control
+++ python-tcpwrap-0.2/debian/control
@@ -2,7 +2,7 @@
 Section: python
 Priority: optional
 Maintainer: Brian Sutherland 
-Build-Depends: debhelper (>= 5.0.37.2), python-all-dev (>= 2.6.6-3~), libwrap0-dev
+Build-Depends: debhelper (>= 10), python-all-dev (>= 2.6.6-3~), libwrap0-dev, dh-python
 Standards-Version: 3.6.1
 
 Package: python-tcpwrap

Processed: Re: python-tcpwrap: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #817639 [src:python-tcpwrap] python-tcpwrap: Removal of debhelper compat 4
Added tag(s) patch.

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

Bug#817619: piwi: Removal of debhelper compat 4

[Logan Rosen]

Package: piwi
Version: 0.8+20041206-3
Followup-For: Bug #817619
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,

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

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.
  * debian/rules:
- Use dh_prep instead of dh_clean -k.
- Add recommended build-arch and build-indep targets.

Thanks for considering the patch.

Logan Rosen
diff -u piwi-0.8+20041206/debian/compat piwi-0.8+20041206/debian/compat
--- piwi-0.8+20041206/debian/compat
+++ piwi-0.8+20041206/debian/compat
@@ -1 +1 @@
-4
+10
diff -u piwi-0.8+20041206/debian/rules piwi-0.8+20041206/debian/rules
--- piwi-0.8+20041206/debian/rules
+++ piwi-0.8+20041206/debian/rules
@@ -28,7 +28,9 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir
@@ -52,7 +54,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k 
+	dh_prep
 	dh_installdirs
 	dh_install 
 
diff -u piwi-0.8+20041206/debian/control piwi-0.8+20041206/debian/control
--- piwi-0.8+20041206/debian/control
+++ piwi-0.8+20041206/debian/control
@@ -2,12 +2,12 @@
 Section: admin
 Priority: optional
 Maintainer: Mickael Profeta 
-Build-Depends-Indep: debhelper (>= 4.0.0)
+Build-Depends: debhelper (>= 10)
 Standards-Version: 3.6.1.0
 
 Package: piwi
 Architecture: all
-Depends: ${perl:Depends}, apache | apache-ssl | apache-perl | httpd, mysql-client | postgresql-client, libapache-dbi-perl, libdbd-mysql-perl| libdbd-pg-perl, libdate-calc-perl
+Depends: ${misc:Depends}, ${perl:Depends}, apache | apache-ssl | apache-perl | httpd, mysql-client | postgresql-client, libapache-dbi-perl, libdbd-mysql-perl| libdbd-pg-perl, libdate-calc-perl
 Suggests:  libgd-gd2-perl, geoip-bin
 Description: P(erl|relude) IDS Web Interface - A frontend to your Prelude database
  Providing a complete web front-end for the Prelude-Intrusion Detection System

Bug#834654: marked as done (heimdal: FTBFS: test suite errors)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 01:33:59 +
with message-id 
and subject line Bug#834654: fixed in heimdal 7.1.0+dfsg-1
has caused the Debian Bug report #834654,
regarding heimdal: FTBFS: test suite errors
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.)


-- 
834654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heimdal
Severity: serious

There have been no upstream releases of Heimdal in over 4 years and there is no 
current
release management or QA upstream. After 1.6RC2, prior to which releases were
fairly frequent (every month or so), no new releases have happened.

The last full feature release was 1.5 (September 2011). 

Debian has packaged snapshots of Heimdal for a while, mostly because Samba
(which bundles Heimdal) uses it, and it needs specific features to be
compatible with AD. However, Samba turned out too be too closely coupled
to a specific Heimdal version; using a different Heimdal snapshot than what
upstream Samba was using caused subtle bugs, in part because the extensive
QA that happened upstream didn't happen in Debian. Since then, the Samba
package has changed to use the bundled Heimdal. 
See also 
https://lists.alioth.debian.org/pipermail/pkg-samba-maint/2015-April/017277.html

Upstream Heimdal is still somewhat active; most contributors just seem
to run Git snapshots in their own environments. There is a long open bug
in master that makes Heimdal unusable on 32 bit platforms (#822749) and
at the moment of writing, ./configure doesn't run in master on Debian unstable.

At this point it seems very unlikely that upstream will release a 1.7 before
Debians next soft freeze. As maintainers, we don't want to package a 4 year old
Heimdal 1.5 or have Debian support a git snapshot for the next couple of years.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: heimdal
Source-Version: 7.1.0+dfsg-1

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated heimdal 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, 16 Dec 2016 01:46:37 +
Source: heimdal
Binary: heimdal-docs heimdal-kdc heimdal-multidev heimdal-dev heimdal-clients 
heimdal-kcm heimdal-servers heimdal-dbg libheimbase1-heimdal libasn1-8-heimdal 
libkrb5-26-heimdal libhdb9-heimdal libkadm5srv8-heimdal libkadm5clnt7-heimdal 
libgssapi3-heimdal libkafs0-heimdal libroken18-heimdal libotp0-heimdal 
libsl0-heimdal libkdc2-heimdal libhx509-5-heimdal libheimntlm0-heimdal 
libwind0-heimdal libhcrypto4-heimdal
Architecture: source amd64 all
Version: 7.1.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Brian May 
Changed-By: Jelmer Vernooij 
Description:
 heimdal-clients - Heimdal Kerberos - clients
 heimdal-dbg - Heimdal Kerberos - debugging symbols
 heimdal-dev - Heimdal Kerberos - development files
 heimdal-docs - Heimdal Kerberos - documentation
 heimdal-kcm - Heimdal Kerberos - KCM daemon
 heimdal-kdc - Heimdal Kerberos - key distribution center (KDC)
 heimdal-multidev - Heimdal Kerberos - Multi-implementation Development
 heimdal-servers - Heimdal Kerberos - server programs
 libasn1-8-heimdal - Heimdal Kerberos - ASN.1 library
 libgssapi3-heimdal - Heimdal Kerberos - GSSAPI support library
 libhcrypto4-heimdal - Heimdal Kerberos - crypto library
 libhdb9-heimdal - Heimdal Kerberos - kadmin server library
 libheimbase1-heimdal - Heimdal Kerberos - Base library
 libheimntlm0-heimdal - Heimdal Kerberos - NTLM support library
 libhx509-5-heimdal - Heimdal Kerberos - X509 support 

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen
diff -Nru olpc-xo1-0.3/debian/compat olpc-xo1-0.3ubuntu1/debian/compat
--- olpc-xo1-0.3/debian/compat	2009-02-15 16:37:40.0 -0500
+++ olpc-xo1-0.3ubuntu1/debian/compat	2016-12-24 20:18:25.0 -0500
@@ -1 +1 @@
-4
+10
diff -Nru olpc-xo1-0.3/debian/control olpc-xo1-0.3ubuntu1/debian/control
--- olpc-xo1-0.3/debian/control	2009-02-15 16:43:07.0 -0500
+++ olpc-xo1-0.3ubuntu1/debian/control	2016-12-24 20:18:47.0 -0500
@@ -2,11 +2,12 @@
 Section: admin
 Priority: extra
 Maintainer: Andres Salomon 
-Build-Depends: debhelper (>= 4.1.0), cdbs
+Build-Depends: debhelper (>= 10), cdbs
 Standards-Version: 3.8.0
 
 Package: olpc-xo1-hw
 Architecture: all
+Depends: ${misc:Depends}
 Description: Support for OLPC XO-1 hardware
  This package contains necessary scripts and other things to support OLPC's
  XO-1 hardware.  This hardware is a mix between a laptop and an embedded

Processed: Re: olpc-xo1: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #817602 [src:olpc-xo1] olpc-xo1: Removal of debhelper compat 4
Added tag(s) patch.

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

Processed: Re: eficas: FTBFS: dh_listpackages: Compatibility levels before 5 are no longer supported (level 1 requested)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #830424 [src:eficas] eficas: FTBFS: dh_listpackages: Compatibility levels 
before 5 are no longer supported (level 1 requested)
Added tag(s) patch.

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

Bug#830424: eficas: FTBFS: dh_listpackages: Compatibility levels before 5 are no longer supported (level 1 requested)

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * debian/compat: Indicate compatibility level of 10.
  * debian/control: Build-depend on debhelper (>= 10) and dh-python.
  * debian/eficas.install: Remove executable bit.

Thanks for considering the patch.

Logan Rosen
diff -Nru eficas-6.4.0-1/debian/compat eficas-6.4.0-1/debian/compat
--- eficas-6.4.0-1/debian/compat	1969-12-31 19:00:00.0 -0500
+++ eficas-6.4.0-1/debian/compat	2016-12-24 20:08:55.0 -0500
@@ -0,0 +1 @@
+10
diff -Nru eficas-6.4.0-1/debian/control eficas-6.4.0-1/debian/control
--- eficas-6.4.0-1/debian/control	2012-04-29 04:40:03.0 -0400
+++ eficas-6.4.0-1/debian/control	2016-12-24 20:09:08.0 -0500
@@ -3,9 +3,9 @@
 Priority: optional
 Maintainer: Debian Science Team 
 Uploaders: Christophe Trophime 
-Build-Depends: debhelper (>= 5.0.38), cdbs (>= 0.4.90~), 
+Build-Depends: debhelper (>= 10), cdbs (>= 0.4.90~), 
  python-all (>= 2.6.6-3~), python-qt4-dev, quilt,
- python-openturns
+ python-openturns, dh-python
 Standards-Version: 3.9.3
 X-Python-Version: all
 Homepage: http://www.code-aster.org/

Bug#846753: marked as done (erlang-cherly: FTBFS: ERROR: OTP release 19 does not match required regex R14B04|R15B02|R15B03|R16B|17|18)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 00:49:02 +
with message-id 
and subject line Bug#846753: fixed in erlang-cherly 0.12.8+dfsg-6
has caused the Debian Bug report #846753,
regarding erlang-cherly: FTBFS: ERROR: OTP release 19 does not match required 
regex R14B04|R15B02|R15B03|R16B|17|18
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.)


-- 
846753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cherly
Version: 0.12.8+dfsg-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_update_autotools_config -O--buildsystem=rebar
>dh_auto_configure -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> configure
> make[1]: Nothing to be done for 'configure'.
>dh_auto_build -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> build
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-cherly-0.12.8+dfsg/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file 
> "/<>/erlang-cherly-0.12.8+dfsg/src/cherly.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps  : []
> DEBUG: Plugins requested while processing 
> /<>/erlang-cherly-0.12.8+dfsg: []
> DEBUG: Predirs: []
> ==> erlang-cherly-0.12.8+dfsg (compile)
> DEBUG: Matched required ERTS version: 8.1.1 -> .*
> ERROR: OTP release 19 does not match required regex 
> R14B04|R15B02|R15B03|R16B|17|18
> ERROR: compile failed while processing 
> /<>/erlang-cherly-0.12.8+dfsg: rebar_abort
> /usr/share/dh-rebar/make/dh-rebar.Makefile:125: recipe for target 
> 'rebar_compile' failed
> make[1]: *** [rebar_compile] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/erlang-cherly_0.12.8+dfsg-5_unstable.log

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Dec 2016 22:13:33 +0900
Source: erlang-cherly
Binary: erlang-cherly
Architecture: source amd64
Version: 0.12.8+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: LeoFS maintainers team 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-cherly - Cherly (sher-lee) is an in-VM caching library for Erlang
Closes: 846753
Changes:
 erlang-cherly (0.12.8+dfsg-6) unstable; urgency=medium
 .
   * Update patches/add_support_r17_and_r18.
   * Add patches/using-crypto_strong_rand_bytes. (Closes: #846753)
   * Update Standards-Version to 3.9.8.
Checksums-Sha1:
 fc5956213fc1ee07a3cf4c9c572fedc4a0cd58d7 2135 erlang-cherly_0.12.8+dfsg-6.dsc
 923f3ee977c25d0fb361d33b318a75b5325e9af9 3900 
erlang-cherly_0.12.8+dfsg-6.debian.tar.xz
 56baf5d737bee9e0acabc1cd2909fc8d45782f48 35000 
erlang-cherly-dbgsym_0.12.8+dfsg-6_amd64.deb
 63dbc8f31b9219edcc1b2ebafe05a5dc4f07be20 8316 
erlang-cherly_0.12.8+dfsg-6_amd64.buildinfo
 c3615d5f7267007f26bee37a1f5dbbbff60143a0 25316 
erlang-cherly_0.12.8+dfsg-6_amd64.deb
Checksums-Sha256:
 

Bug#848761: ovito: FTBFS: Test failures, now fixed upstream

[Ghislain Vaillant]

On Fri, 23 Dec 2016 19:28:09 + Ghislain Vaillant  wrote:
> I have forwarded the issue upstream with a build log on the latest
> upstream version done on debomatic.

Alright, upstream claims the issue is fixed on `master`. I intend to
cherry-pick the fix onto 2.8.1, unless upstream decides to release a
new version as suggested.

Ghis

Bug#849285: marked as done (kodi-pvr-mythtv: FTBFS: src/client.cpp:1202:6: error: conflicting declaration of C function 'bool SeekTime(int, bool, double*)')

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 00:05:20 +
with message-id 
and subject line Bug#849285: fixed in kodi-pvr-mythtv 4.12.7+git20161219-2
has caused the Debian Bug report #849285,
regarding kodi-pvr-mythtv: FTBFS: src/client.cpp:1202:6: error: conflicting 
declaration of C function 'bool SeekTime(int, bool, double*)'
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.)


-- 
849285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi-pvr-mythtv
Version: 4.7.2+git20160820-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

kodi-pvr-mythtv fails to build from source in unstable/amd64:

  […]

  dh build
 dh_testdir
 dh_update_autotools_config
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '«BUILDDIR»'
  # USE_LTO breaks build
  dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 
-DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu/kodi
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_BUILD_TYPE=Release 
-DBUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu/kodi
  -- The C compiler identification is GNU 6.2.1
  -- The CXX compiler identification is GNU 6.2.1
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Checking to see if CXX compiler accepts flag -flto
  -- Checking to see if CXX compiler accepts flag -flto - yes
  -- Looking for __atomic_fetch_add_4 in atomic
  -- Looking for __atomic_fetch_add_4 in atomic - found
  -- Performing Test HAS_BUILTIN_SYNC_ADD_AND_FETCH
  -- Performing Test HAS_BUILTIN_SYNC_ADD_AND_FETCH - Success
  -- Performing Test HAS_BUILTIN_SYNC_SUB_AND_FETCH
  -- Performing Test HAS_BUILTIN_SYNC_SUB_AND_FETCH - Success
  -- Performing Test HAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP
  -- Performing Test HAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP - Success
  -- Looking for pthread.h
  -- Looking for pthread.h - found
  -- Looking for pthread_create
  -- Looking for pthread_create - not found
  -- Looking for pthread_create in pthreads
  -- Looking for pthread_create in pthreads - not found
  -- Looking for pthread_create in pthread
  -- Looking for pthread_create in pthread - found
  -- Found Threads: TRUE  
  -- Looking for timegm
  -- Looking for timegm - found
  -- Looking for localtime_r
  -- Looking for localtime_r - found
  -- Looking for gmtime_r
  -- Looking for gmtime_r - found
  -- Performing Test HAVE_INLINE
  -- Performing Test HAVE_INLINE - Success
  -- Performing Test HAVE___INLINE
  -- Performing Test HAVE___INLINE - Success
  -- Performing Test HAVE___INLINE__
  -- Performing Test HAVE___INLINE__ - Success
  -- Performing Test COMPILER_SUPPORTS_CXX11
  -- Performing Test COMPILER_SUPPORTS_CXX11 - Success
  -- MYTHTV_VERSION=4.7.2
  -- Configuring done
  -- Generating done
  CMake Warning:
Manually-specified variables were not used by the project:
  
  CMAKE_INSTALL_LOCALSTATEDIR
  CMAKE_INSTALL_SYSCONFDIR
  
  
  -- Build files have been written to: «BUILDDIR»/obj-x86_64-linux-gnu
  make[1]: Leaving directory '«BUILDDIR»'
 dh_auto_build
make -j1
  make[1]: Entering directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  /usr/bin/cmake -H«BUILDDIR» 
-B/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu
 --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake -E cmake_progress_start 
«BUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
  make -f CMakeFiles/Makefile2 all
  make[2]: Entering directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  make -f lib/cppmyth/CMakeFiles/cppmyth.dir/build.make 
lib/cppmyth/CMakeFiles/cppmyth.dir/depend
  

Processed: Bug#849285 marked as pending

[Debian Bug Tracking System]

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

> tag 849285 pending
Bug #849285 [src:kodi-pvr-mythtv] kodi-pvr-mythtv: FTBFS: 
src/client.cpp:1202:6: error: conflicting declaration of C function 'bool 
SeekTime(int, bool, double*)'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#849285: marked as pending

[Balint Reczey]

tag 849285 pending
thanks

Hello,

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


http://git.debian.org/?p=pkg-multimedia/kodi-pvr-mythtv.git;a=commitdiff;h=704202d

---
commit 704202d27717ff2f1b34be2afd2d73b15f12ecb7
Author: Balint Reczey 
Date:   Sat Dec 24 23:25:29 2016 +0100

Update changelog

diff --git a/debian/changelog b/debian/changelog
index 654f22c..35bf794 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+kodi-pvr-mythtv (4.12.7+git20161219-2) unstable; urgency=medium
+
+  * Build-depend on zlib1g-dev (Closes: #849285)
+
+ -- Balint Reczey   Sun, 25 Dec 2016 00:37:24 +0100
+
 kodi-pvr-mythtv (4.12.7+git20161219-1) unstable; urgency=medium
 
   * Update d/control using cme fix

Bug#817330: marked as done (fookb: Mandatory debian/compat for debhelper)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 23:33:21 +
with message-id 
and subject line Bug#817330: fixed in fookb 3.0-3.1
has caused the Debian Bug report #817330,
regarding fookb: Mandatory debian/compat for debhelper
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.)


-- 
817330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fookb
Severity: important
Usertags: mandatory-debian-compat

Hi,

The package fookb uses debhelper but does not have a debian/compat
file.

 * Please add a debian/compat file at your earliest convenience.

 * This will become mandatory in the first debhelper upload after
   15th of April.

If your package is *also* affected by any of the following debhelper
related deprecations, please consider fixing them at the same time:

 * debhelper compat 4 is deprecated and is expected to be removed
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: fookb
Source-Version: 3.0-3.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated fookb 
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, 22 Dec 2016 21:01:26 -0200
Source: fookb
Binary: fookb-plainx fookb-wmaker
Architecture: source
Version: 3.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Wartan Hachaturow 
Changed-By: Joao Eriberto Mota Filho 
Description:
 fookb-plainx - Xkb state indicator -- plain X version
 fookb-wmaker - Xkb state indicator -- WindowMaker version
Closes: 817330 817456
Changes:
 fookb (3.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817456)
   * debian/compat: created. (Closes: #817330)
   * debian/control:
   - Added the ${misc:Depends} variable to Depends field.
   - Bumped Standards-Version to 3.9.8.
   - Fixed the short descriptions.
Checksums-Sha1:
 b22aa6dfccc1efe9df6cebc12f34fc756b44ff57 1762 fookb_3.0-3.1.dsc
 e48a5eca32a7960cdf7d891b3d0e833d12065f79 3908 fookb_3.0-3.1.diff.gz
Checksums-Sha256:
 b53230fd378dadb612ce1599724fefcc9c501452acecef0539957251e7061f95 1762 
fookb_3.0-3.1.dsc
 cd19ac67ec0bb5fee8eec849cc780b321ef532c7d5e245dd9acdd4b36356d3cc 3908 
fookb_3.0-3.1.diff.gz
Files:
 a65fe224813c3fa5c687a5dc6d822988 1762 x11 optional fookb_3.0-3.1.dsc
 962c9b6ab0a6f32aaf0dcacdddc8152e 3908 x11 optional fookb_3.0-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcXLsACgkQ3mO5xwTr
6e9DJBAAiuiprfjBlFYB07FoP7imVpfiMjEBf/GJQkUoHbTScwmaGK8hEZjhVJ+y
tMEwCg7POhDtsFf+aV/UbDjW1r0I8UiTz1JRE7lADpOL/26XL5rviw2UfL6prn4p
DnadF/kwQdCxhYpI9U8AeZEl1kh/Y5u/fuvbzzelO+h9NuZGwK5D9OmyoxllPaQR
iZFirZgtIwxuHBl8o1TGH9wccHrx8UxuSPNt18RePo/3vDvQC7ee9BiK2W8pxWMD
O3mZqKxbyXWHppkf2ldUTuBMkfSyWZQ9uhPagAmudCR3rlmEu5Go0pubEsg+1V4i
E4v4slKRRzY84iYiwPsoLIv7YCSejTqrrrSfjdfYSqUSb/7QtIBfJQqAyf3n0t06
fm24ILAYuHlbktLdnYs7AC3kjF0SwZ2izf619t2En2EP3JrSTbMl4J2RU4nBpnvN
uAS4gTIE7RGINMpMSSHY0Y2R6pQmRYUju0ZV3sYgnGmFRHtRq4R5JvqyLN2REmoF
pKjvnL8pWeugYDlQ5gUqauu75EhnOiPrLDjmU8MRVEUF4zoGad8hLOCIFSBiaZxn
xSU69/0ww8FRaDUL/lRAiwmNd7rf3YjYvYd2nS0UEXfI2cqBceCE9SwLxQSIxTOa
/Vgf+WB9dmdLb3GcbBvpG7GWClfD1VM04vUPkzz9fCSuIVAp92A=
=6OrW
-END PGP SIGNATURE End Message ---

Bug#817456: marked as done (fookb: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 23:33:21 +
with message-id 
and subject line Bug#817456: fixed in fookb 3.0-3.1
has caused the Debian Bug report #817456,
regarding fookb: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fookb
Severity: important
Usertags: compat-4-removal

Hi,

The package fookb uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: fookb
Source-Version: 3.0-3.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated fookb 
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, 22 Dec 2016 21:01:26 -0200
Source: fookb
Binary: fookb-plainx fookb-wmaker
Architecture: source
Version: 3.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Wartan Hachaturow 
Changed-By: Joao Eriberto Mota Filho 
Description:
 fookb-plainx - Xkb state indicator -- plain X version
 fookb-wmaker - Xkb state indicator -- WindowMaker version
Closes: 817330 817456
Changes:
 fookb (3.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817456)
   * debian/compat: created. (Closes: #817330)
   * debian/control:
   - Added the ${misc:Depends} variable to Depends field.
   - Bumped Standards-Version to 3.9.8.
   - Fixed the short descriptions.
Checksums-Sha1:
 b22aa6dfccc1efe9df6cebc12f34fc756b44ff57 1762 fookb_3.0-3.1.dsc
 e48a5eca32a7960cdf7d891b3d0e833d12065f79 3908 fookb_3.0-3.1.diff.gz
Checksums-Sha256:
 b53230fd378dadb612ce1599724fefcc9c501452acecef0539957251e7061f95 1762 
fookb_3.0-3.1.dsc
 cd19ac67ec0bb5fee8eec849cc780b321ef532c7d5e245dd9acdd4b36356d3cc 3908 
fookb_3.0-3.1.diff.gz
Files:
 a65fe224813c3fa5c687a5dc6d822988 1762 x11 optional fookb_3.0-3.1.dsc
 962c9b6ab0a6f32aaf0dcacdddc8152e 3908 x11 optional fookb_3.0-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcXLsACgkQ3mO5xwTr
6e9DJBAAiuiprfjBlFYB07FoP7imVpfiMjEBf/GJQkUoHbTScwmaGK8hEZjhVJ+y
tMEwCg7POhDtsFf+aV/UbDjW1r0I8UiTz1JRE7lADpOL/26XL5rviw2UfL6prn4p
DnadF/kwQdCxhYpI9U8AeZEl1kh/Y5u/fuvbzzelO+h9NuZGwK5D9OmyoxllPaQR
iZFirZgtIwxuHBl8o1TGH9wccHrx8UxuSPNt18RePo/3vDvQC7ee9BiK2W8pxWMD
O3mZqKxbyXWHppkf2ldUTuBMkfSyWZQ9uhPagAmudCR3rlmEu5Go0pubEsg+1V4i
E4v4slKRRzY84iYiwPsoLIv7YCSejTqrrrSfjdfYSqUSb/7QtIBfJQqAyf3n0t06
fm24ILAYuHlbktLdnYs7AC3kjF0SwZ2izf619t2En2EP3JrSTbMl4J2RU4nBpnvN
uAS4gTIE7RGINMpMSSHY0Y2R6pQmRYUju0ZV3sYgnGmFRHtRq4R5JvqyLN2REmoF
pKjvnL8pWeugYDlQ5gUqauu75EhnOiPrLDjmU8MRVEUF4zoGad8hLOCIFSBiaZxn
xSU69/0ww8FRaDUL/lRAiwmNd7rf3YjYvYd2nS0UEXfI2cqBceCE9SwLxQSIxTOa
/Vgf+WB9dmdLb3GcbBvpG7GWClfD1VM04vUPkzz9fCSuIVAp92A=
=6OrW
-END PGP SIGNATURE End Message ---

Bug#848754: marked as done (snapd: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 23:34:25 +
with message-id 
and subject line Bug#848754: fixed in snapd 2.20-1
has caused the Debian Bug report #848754,
regarding snapd: FTBFS: Test failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> ? github.com/snapcore/snapd/vendor/golang.org/x/crypto/xtea   [no 
> test files]
> ? github.com/snapcore/snapd/vendor/golang.org/x/crypto/xts[no 
> test files]
> ? github.com/snapcore/snapd/vendor/golang.org/x/net/context   [no 
> test files]
> ? github.com/snapcore/snapd/vendor/golang.org/x/net/context/ctxhttp   
> [no test files]
> ? github.com/snapcore/snapd/vendor/gopkg.in/check.v1  [no test files]
> ? github.com/snapcore/snapd/vendor/gopkg.in/macaroon.v1   [no test files]
> ? github.com/snapcore/snapd/vendor/gopkg.in/tomb.v2   [no test files]
> ? github.com/snapcore/snapd/vendor/gopkg.in/tylerb/graceful.v1[no 
> test files]
> ? github.com/snapcore/snapd/vendor/gopkg.in/yaml.v2   [no test files]
> === RUN   TestWrappers
> OK: 25 passed
> --- PASS: TestWrappers (0.74s)
> PASS
> okgithub.com/snapcore/snapd/wrappers  0.751s
> dh_auto_test: go test -v -p 1 github.com/snapcore/snapd/arch 
> github.com/snapcore/snapd/asserts 
> github.com/snapcore/snapd/asserts/assertstest 
> github.com/snapcore/snapd/asserts/signtool 
> github.com/snapcore/snapd/asserts/snapasserts 
> github.com/snapcore/snapd/asserts/sysdb 
> github.com/snapcore/snapd/asserts/systestkeys github.com/snapcore/snapd/boot 
> github.com/snapcore/snapd/boot/boottest github.com/snapcore/snapd/client 
> github.com/snapcore/snapd/cmd github.com/snapcore/snapd/cmd/snap 
> github.com/snapcore/snapd/cmd/snap-exec github.com/snapcore/snapd/cmd/snapctl 
> github.com/snapcore/snapd/cmd/snapd github.com/snapcore/snapd/coreconfig 
> github.com/snapcore/snapd/daemon github.com/snapcore/snapd/dirs 
> github.com/snapcore/snapd/firstboot github.com/snapcore/snapd/i18n 
> github.com/snapcore/snapd/i18n/xgettext-go github.com/snapcore/snapd/image 
> github.com/snapcore/snapd/interfaces 
> github.com/snapcore/snapd/interfaces/apparmor 
> github.com/snapcore/snapd/interfaces/backends 
> github.com/snapcore/snapd/interfaces/backendtest 
> github.com/snapcore/snapd/interfaces/builtin 
> github.com/snapcore/snapd/interfaces/dbus 
> github.com/snapcore/snapd/interfaces/kmod 
> github.com/snapcore/snapd/interfaces/mount 
> github.com/snapcore/snapd/interfaces/seccomp 
> github.com/snapcore/snapd/interfaces/udev github.com/snapcore/snapd/logger 
> github.com/snapcore/snapd/notifications github.com/snapcore/snapd/osutil 
> github.com/snapcore/snapd/overlord 
> github.com/snapcore/snapd/overlord/assertstate 
> github.com/snapcore/snapd/overlord/auth 
> github.com/snapcore/snapd/overlord/boot 
> github.com/snapcore/snapd/overlord/configstate 
> github.com/snapcore/snapd/overlord/devicestate 
> github.com/snapcore/snapd/overlord/hookstate 
> github.com/snapcore/snapd/overlord/hookstate/ctlcmd 
> github.com/snapcore/snapd/overlord/hookstate/hooktest 
> github.com/snapcore/snapd/overlord/ifacestate 
> github.com/snapcore/snapd/overlord/patch 
> github.com/snapcore/snapd/overlord/snapstate 
> github.com/snapcore/snapd/overlord/snapstate/backend 
> github.com/snapcore/snapd/overlord/state github.com/snapcore/snapd/partition 
> github.com/snapcore/snapd/policy github.com/snapcore/snapd/progress 
> github.com/snapcore/snapd/provisioning github.com/snapcore/snapd/release 
> github.com/snapcore/snapd/snap github.com/snapcore/snapd/snap/snapdir 
> github.com/snapcore/snapd/snap/snapenv 
> github.com/snapcore/snapd/snap/snaptest 
> github.com/snapcore/snapd/snap/squashfs github.com/snapcore/snapd/store 
> github.com/snapcore/snapd/strutil github.com/snapcore/snapd/systemd 
> github.com/snapcore/snapd/testutil github.com/snapcore/snapd/timeout 
> github.com/snapcore/snapd/vendor/github.com/cheggaaa/pb 
> github.com/snapcore/snapd/vendor/github.com/coreos/go-systemd/activation 
> github.com/snapcore/snapd/vendor/github.com/gorilla/context 
> github.com/snapcore/snapd/vendor/github.com/gorilla/mux 
> 

Bug#831965: marked as done (asciidoc: FTBFS with dpkg-buildpackage -A: doc/testasciidoc.1: No such file or directory at /usr/bin/dh_installman line 131.)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 23:00:11 +
with message-id 
and subject line Bug#831965: fixed in asciidoc 8.6.9-4
has caused the Debian Bug report #831965,
regarding asciidoc: FTBFS with dpkg-buildpackage -A: doc/testasciidoc.1: No 
such file or directory at /usr/bin/dh_installman line 131.
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.)


-- 
831965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asciidoc
Version: 8.6.9-3
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.

If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now. If not, debian/rules
should be modified so that the build-indep and binary-indep target generates
the architecture independent packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
>   cp --reflink=auto -a ./asciidoc.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./docbook45.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./help.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./html4.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./html5.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-cs.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-de.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-el.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-en.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-es.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-fr.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-hu.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-it.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-nl.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-pt-BR.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-ro.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-ru.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./lang-uk.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./latex.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./slidy.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./text.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./xhtml11-quirks.conf 
> debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./xhtml11.conf debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./tests/data/ debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a .//images/icons 
> debian/asciidoc//usr/share/asciidoc/
>   cp --reflink=auto -a ./asciidocapi.py 
> debian/asciidoc//usr/share/asciidoc/
>   cp --reflink=auto -a ./dblatex debian/asciidoc//etc/asciidoc//
>   install -d debian/asciidoc//usr/share/vim/registry
>   cp --reflink=auto -a ./debian/asciidoc.yaml 
> debian/asciidoc//usr/share/vim/registry/
>   cp --reflink=auto -a ./docbook-xsl debian/asciidoc//etc/asciidoc//
>   cp --reflink=auto -a ./docbook-xsl/chunked.xsl 
> debian/asciidoc//etc/asciidoc/docbook-xsl//
>   cp --reflink=auto -a ./docbook-xsl/common.xsl 
> debian/asciidoc//etc/asciidoc/docbook-xsl//
>   cp --reflink=auto -a ./docbook-xsl/epub.xsl 
> debian/asciidoc//etc/asciidoc/docbook-xsl//
>   cp --reflink=auto -a ./docbook-xsl/fo.xsl 
> debian/asciidoc//etc/asciidoc/docbook-xsl//
>   cp --reflink=auto -a ./docbook-xsl/htmlhelp.xsl 
> debian/asciidoc//etc/asciidoc/docbook-xsl//
>   cp --reflink=auto -a 

Bug#817461: freepwing: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * debian/compat: Bump to 10.
  * debian/control: Build-depend on debhelper (>= 10).

Thanks for considering the patch.

Logan Rosen
diff -u freepwing-1.5/debian/compat freepwing-1.5/debian/compat
--- freepwing-1.5/debian/compat
+++ freepwing-1.5/debian/compat
@@ -1 +1 @@
-4
+10
diff -u freepwing-1.5/debian/control freepwing-1.5/debian/control
--- freepwing-1.5/debian/control
+++ freepwing-1.5/debian/control
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Masayuki Hatta (mhatta) 
-Build-Depends: debhelper (>= 4.0.0), perl
+Build-Depends: debhelper (>= 10), perl
 Standards-Version: 3.8.0
 
 Package: freepwing

Bug#817637: marked as done (pygdchart2: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 22:50:15 +
with message-id 
and subject line Bug#817637: fixed in pygdchart2 0.beta1-3.7
has caused the Debian Bug report #817637,
regarding pygdchart2: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygdchart2
Severity: important
Usertags: compat-4-removal

Hi,

The package pygdchart2 uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: pygdchart2
Source-Version: 0.beta1-3.7

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

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

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated pygdchart2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 22 Dec 2016 20:02:15 -0200
Source: pygdchart2
Binary: python-gdchart2 python-gdchart2-doc
Architecture: source
Version: 0.beta1-3.7
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Joao Eriberto Mota Filho 
Description:
 python-gdchart2 - Python OO interface to GDChart
 python-gdchart2-doc - Python OO interface to GDChart - docs
Closes: 817637
Changes:
 pygdchart2 (0.beta1-3.7) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817637)
   * debian/control: bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 6b17bd42f9a66b34aa55786b814e2dc22ef6f6d5 1912 pygdchart2_0.beta1-3.7.dsc
 1fc273387ee4505c3436101b3fc6216291ea6836 4697 pygdchart2_0.beta1-3.7.diff.gz
Checksums-Sha256:
 bc41fa4f985ad10ec59d13c54baad4bdc994131af22478f79bd4734e770832e7 1912 
pygdchart2_0.beta1-3.7.dsc
 508f28405ef272387003482797a473a0f486451ba38e22bad3665b75314e4c23 4697 
pygdchart2_0.beta1-3.7.diff.gz
Files:
 ed283977c08c6db6b37221781ab1829e 1912 python optional 
pygdchart2_0.beta1-3.7.dsc
 6e69e5f9c9e95654fa4643a45ef9fc94 4697 python optional 
pygdchart2_0.beta1-3.7.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcT8wACgkQ3mO5xwTr
6e8tlhAAqLDxIU/1IfaR4KQbCkHRFfn8uz+wnzQQjutthGSTASB4dRnpOpqxtSpV
5N65rGUlI9MlIB+dDGWuUKzDrt1djYb833qEIn8c7gM+59GF/lVtO3XVd0J59xPC
jj+oj3T5m49QkprOns90IRNPcyBnuatN7knerDoxJQdY91y3DyhOB9htJ6i0BkFY
gwq4xSfjoRxBcOmZC0uDggq6JBRPy4bqe07b4Xg35MGQjUA+XwBDnQyN+AAspsTc
H/un1PXs0jWACJDiX5K7l3D/Cp46ywmg27jyH6VylTbqZ/jiI1s8WFgqS78uFVX3
V/Rm8tAuUFdW3F6Lm0PGk2MtO1iYUn9x+A/1Y3eHeatdpeKjuTeTk2rltlCckqEJ
4Yn581uviDGi7QX1v0q3osS6exl3yrqGDkiDRtC+0s3Yw53UCvfAiY/gS2kTuwP6
S4Kav9RQx5bkNNgPkyEbO2YMA+Z6BfRKnNins1WcGFzKuRtAJKs3TZjOBgq6I6CI
9tV0x0OJXPnqyNXq+YvcuVn6Gb/HgT7lwbQQIOwdQDlxd2GQN2iP5R7Rv71QNLDx
2XevpIi7cW9v6r4eL43r1/xp2S109YhKTpF7EuKUhLOLClYShSTMNMHZkS28YkWY
HRYtYahGiuqofj8V8Wo6xQLvKBtD+4E+sgcoxyWwr+6pWwVLMq8=
=+PjJ
-END PGP SIGNATURE End Message ---

Processed: Re: freepwing: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #817461 [src:freepwing] freepwing: Removal of debhelper compat 4
Added tag(s) patch.

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

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

[Chris Lamb]

Daniel Shahaf wrote:

> > +if subprocess.call(
> > +('python3', '-c', 'import enjarify.typeinference'),
> 
> Use sys.executable instead of hardcoding 'python3', to handle the case
> that there's more than one python3 binary on the system?

I deliberately used python3 to match the behaviour of what the
/usr/bin/enjarify script does.

Besides, sys.executable could be the virtualenv's python which we don't
want to call :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: Re: duma: FTBFS with GCC 6: declaration of ... has a different exception specifier

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #811887 [duma] duma: FTBFS with GCC 6: declaration of ... has a different 
exception specifier
Added tag(s) patch.

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

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

[Ximin Luo]

Chris Lamb:
> Ximin Luo wrote:
> 
>> I still haven't managed to reproduce this myself but I'll just note
>> for the record we have seen this on jenkins before
> 
> My guess is that one of the third-party Python extension modules that
> we import does not correctly reference count Py_None. Someone did a
> good writeup here:
> 
>   http://stackoverflow.com/a/15288194
> 
> Now, we just need to narrow down which one… and then fix it.  >.>
> 

For all you people that already have single-CPU KVM VMs set up, can you please 
try to reduce your test cases that still reproduce the bug?

For example, can you still reproduce it with `debian/rules clean build`? What 
about `python3 -m pytest`? Then, does it reproduce when you start manually 
disabling various tests? What about when running only 1 test case?

X

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

Bug#811887: duma: FTBFS with GCC 6: declaration of ... has a different exception specifier

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * dumapp.{cpp,h}: Apply patch from Buildroot (thanks, Yann E. MORIN!) to fix
FTBFS with C++14.

Thanks for considering the patch. It was found here:
https://github.com/maximeh/buildroot/blob/master/package/duma/0003-fix-C%2B%2B14.patch

Logan Rosen
--- duma-2.5.15.orig/dumapp.cpp
+++ duma-2.5.15/dumapp.cpp
@@ -190,7 +190,9 @@
  * (11) = (a) ; ASW
  */
 void * DUMA_CDECL operator new( DUMA_SIZE_T size )
+#ifdef DUMA_EXCEPTION_SPECS
 throw(std::bad_alloc)
+#endif
 {
   return duma_new_operator(size, EFA_NEW_ELEM, true  DUMA_PARAMS_UK);
 }
@@ -254,7 +256,9 @@
  * (21) = (a) ; AAW
  */
 void * DUMA_CDECL operator new[]( DUMA_SIZE_T size )
+#ifdef DUMA_EXCEPTION_SPECS
 throw(std::bad_alloc)
+#endif
 {
   return duma_new_operator(size, EFA_NEW_ARRAY, true  DUMA_PARAMS_UK);
 }
--- duma-2.5.15.orig/dumapp.h
+++ duma-2.5.15/dumapp.h
@@ -35,6 +35,10 @@
 
 #include "duma.h"
 
+#if __cplusplus < 201103L
+  #define DUMA_EXCEPTION_SPECS 1
+#endif
+
 /* remove previous macro definitions */
 #include "noduma.h"
 

Bug#811655: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 22:21:21 +
with message-id 
and subject line Bug#811655: fixed in starplot 0.95.5-8.2
has caused the Debian Bug report #811655,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: starplot
Version: 0.95.5-8.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I. -I..-Wall -DDOCDIR=\"/usr/share/doc/starplot\" 
> -DSTARPLOT_VERSION=\"0.95.5\" -DDATADIR=\"/usr/share/starplot\" 
> -DLOCALEDIR=\"/usr/share/locale\" -Wall -pedantic -O2 -g -MT 
> starconvert-convert.o -MD -MP -MF .deps/starconvert-convert.Tpo -c -o 
> starconvert-convert.o `test -f 'convert/convert.cc' || echo 
> './'`convert/convert.cc
> convert/convert.cc: In function 'void parse_star_file(std::istream&, 
> std::ostream&, const parsedata&, bool, bool)':
> convert/convert.cc:67:48: error: cannot convert 'std::basic_istream' to 
> 'bool' in assignment
>  moredata = infile.getline(record, 999, '\n');
> ^
> 
> Makefile:700: recipe for target 'starconvert-convert.o' failed
> make[3]: *** [starconvert-convert.o] Error 1
> make[3]: Leaving directory '/<>/src'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: starplot
Source-Version: 0.95.5-8.2

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated starplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 22:59:59 +0100
Source: starplot
Binary: starplot
Architecture: source
Version: 0.95.5-8.2
Distribution: unstable
Urgency: low
Maintainer: Francisco Manuel Garcia Claramonte 
Changed-By: Petter Reinholdtsen 
Description:
 starplot   - 3-dimensional perspective star map viewer
Closes: 811655
Changes:
 starplot (0.95.5-8.2) unstable; urgency=low
 .
   * Non-maintainer upload to fix RC bug.
 .
   [ Andrea Claudi ]
   * Fix FTBFS in convert.cc for gcc-6 (Closes: #811655).
Checksums-Sha1:
 78a213bff87c23c18e4cd1d78b4ea68586179d8e 1871 starplot_0.95.5-8.2.dsc
 0190cf792273ec813a607db129d2ac86fd7f6615 13384 
starplot_0.95.5-8.2.debian.tar.xz
Checksums-Sha256:
 8a217f20bbf13c66042e9daaded2a59963d9ae738d26c81b8c6097e7b4c96522 1871 
starplot_0.95.5-8.2.dsc
 1d314ba3fec7795a08e9ad9330552e95f01fbffb4ead8114a9f8237c9805a67d 13384 
starplot_0.95.5-8.2.debian.tar.xz
Files:
 11e68f731a6b706bd162481b38606124 1871 science optional starplot_0.95.5-8.2.dsc
 61b2550f7092eb1b8991f92b66b2a13f 13384 science optional 
starplot_0.95.5-8.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlhe8OYACgkQgSgKoIe6
+w5oOw//bZqHUJU0IBPtm+J230LEOyD8SA5RXHix7PdDoS4JPoVZCaUFh7OIOEP2
QK9xUWDv5xQpbMe7WZ2JFcuZGlwCBxrx9PIs8giS+tNq4jfg4GVBaVrWYawVVk4h
6S0AFuHIYswTtCGGXQNhd5lfByrOeGNteQn3MqIE5s+FgEhNBZI9i5ptBDHksS3Q
ROvfc6mA2pxaKOaVzOwi9nd9SKVDxHTpAe7XCVHc22FYPw5ZRrxBVOPBhYyJh9Z4
6vtIBj4H6plc2JkTxyNVLZlsKv/3tdbragCBAkRHA5Sjr4Aj6oOXyQZ2ZXTeWsma
vMvLNF2BHamnt1T8TXZYAWDxiA6mMHAvWkBJEn+wKgipqB8sOqL0kQVajmlwnId/
7OAm05XDeX3uYp9YDjdtrJbn6oqerm1XEKOdeo2IMCAd2wVl7X+7OA7TlGRlinap
3686gd/bZOqvsXx7AGc5h6S1bpSkeN3rky9/V2oGRA6r1dTBGeSnoVQMudfcpaKH
gdjctv+7RlYqgYRZPa2lY4zDKYI+5XWA9E4g9eJ9rkLAl2vXrbIpuyMlyxzt8+pL

Bug#817390: marked as done (chuck: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 22:19:34 +
with message-id 
and subject line Bug#817390: fixed in chuck 1.2.0.8.dfsg-1.5
has caused the Debian Bug report #817390,
regarding chuck: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chuck
Severity: important
Usertags: compat-4-removal

Hi,

The package chuck uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: chuck
Source-Version: 1.2.0.8.dfsg-1.5

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated chuck 
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, 22 Dec 2016 19:41:01 -0200
Source: chuck
Binary: chuck
Architecture: source
Version: 1.2.0.8.dfsg-1.5
Distribution: unstable
Urgency: medium
Maintainer: Paul Brossier 
Changed-By: Joao Eriberto Mota Filho 
Description:
 chuck  - Concurrent, On-the-fly Audio Programming Language
Closes: 817390
Changes:
 chuck (1.2.0.8.dfsg-1.5) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817390)
   * debian/control:
   - Added a Homepage field.
   - Bumped Standards-Version to 3.9.8.
   * debian/watch:
   - Bumped to version 4.
   - Fixed to ignore the 'dfsg' suffix.
Checksums-Sha1:
 954561aaf557d861e126940b8b02c612f76ec693 1786 chuck_1.2.0.8.dfsg-1.5.dsc
 83d3f645e6a406a543e556e1dbc4017ba33fb557 11322 chuck_1.2.0.8.dfsg-1.5.diff.gz
Checksums-Sha256:
 717247e758329def05d2fc267a36aebda42173446e1d40a7153be41f519bfb7d 1786 
chuck_1.2.0.8.dfsg-1.5.dsc
 162d875def5420aa56c6c0303a31b5f65c3574667aac3131cc9cbbd5679aac57 11322 
chuck_1.2.0.8.dfsg-1.5.diff.gz
Files:
 41a95663010624ef5170f5365db916f8 1786 sound optional chuck_1.2.0.8.dfsg-1.5.dsc
 fceeff65cf4a123499637ff61206d919 11322 sound optional 
chuck_1.2.0.8.dfsg-1.5.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcS74ACgkQ3mO5xwTr
6e8p/w//eRFz62FCMnQvUocpiYgTsVrhmPFxO3ob2k0DOZOEQP5lfbCD7B/VAiTW
SfFsWYVdzfL28MVE+/HGB2W/Jn20yBPeclfZiDvSCkvXz2wBwI9YtIHN+JylPAfv
xZMd8nd+2nRTrlAmxnenzY2nZSZhehDaH6v0siAZdRzOVuOn+XIsjanlwL4O51/P
ToprVtVYH5GbwIVrsBvHEiUFMABsqy7RaCJguEG1mbc7KlPnwiaq7TOzOF2Sjt4A
jCpMFBdHePgb3aNRqzOCGZqv8z+UFYrMWqGkaVYv/a4l6xTX6ZFTGWbWi5+95l6V
fkhwO/pebosmdCCdtpjAeMS7hjzWz+c9RadChNbHlAIS4FEe0w9tmVPcc+IKJtqY
Qhaz7XivblJg2G2xiLHpdMv+2kqkm5MJZJS537mPc+lE22m1UTcWwCcA6goz09vN
5bvNf+UZc5hmvHuwQbi94yQVzy53pGVe8fls/RHw+/oGrSpYQHTMR6MBFObj21qg
aqLi0FjxmzWEf/5DSiDyx6n8dsq6XI0eDOJAc74dGf+aP2onxz7nMWttUm7kCdss
Ng3biTQMqw5mZdIddkLikbfg68YpnF/qCQnNWLDikq0BpwpuHSoNBhDunfDCS4TR
ZI1hdwjm5hDqJZBk6CdfXvoiqsoEVjTIFqmq2EhgPG8jS14uiFI=
=5bcs
-END PGP SIGNATURE End Message ---

Bug#811655: Patch for Debian bug #811655

[Petter Reinholdtsen]

[Andrea Claudi]
> This simple patch fix the build issue with gcc-6.
> Please, let me know if it needs improvements.

Thank you for the patch.  I just NMUed the package to fix this RC bug
using this patch.

Once the package upload is registered and this bug is closed, the bug
should be reopened and renamed to a NMU patch bug with severity wishlist.

-- 
Happy hacking
Petter Reinholdtsen

Bug#822034: marked as done (vdk2: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 22:04:23 +
with message-id 
and subject line Bug#822034: fixed in vdk2 2.4.0-5.4
has caused the Debian Bug report #822034,
regarding vdk2: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vdk2
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package vdk2 builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that vdk2 builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to vdk2 at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, vdk2 will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: vdk2
Source-Version: 2.4.0-5.4

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated vdk2 
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, 22 Dec 2016 19:11:49 -0200
Source: vdk2
Binary: libvdk2-2c2 libvdk2-doc libvdk2-dev libvdk2-dbg
Architecture: source
Version: 2.4.0-5.4
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt 
Changed-By: Joao Eriberto Mota Filho 
Description:
 libvdk2-2c2 - Visual Development Kit C++ library version 2
 libvdk2-dbg - debugging static library for the VDK C++ library version 2
 libvdk2-dev - header files and static libraries for VDK library version 2
 libvdk2-doc - documentation for VDK library version 2
Closes: 817712 822034
Changes:
 vdk2 (2.4.0-5.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817712)
   * debian/control:
   - Added a Homepage field.
   - Bumped Standards-Version to 3.9.8.
   * debian/rules: fix missing targets. Thanks to Santiago Vila
 . (Closes: #822034)
   * debian/watch: created.
Checksums-Sha1:
 6577e334dbfd6ce681dab739a3975b7cc898a17b 1990 vdk2_2.4.0-5.4.dsc
 bc7a7c9b49f6054ca4e78acd391a7415b2c4662c 98537 vdk2_2.4.0-5.4.diff.gz
Checksums-Sha256:
 664c09ebeb6aa9e815d6b2dd3274ef90c9c1a08f4e996bd74c64ab99c613 1990 
vdk2_2.4.0-5.4.dsc
 c492ea99557e28103c2452ae576bede9b494318b952b92dbd1e625a4460f082d 98537 
vdk2_2.4.0-5.4.diff.gz
Files:
 724827421b13f66a78af5dafb4294bb0 1990 libs optional vdk2_2.4.0-5.4.dsc
 97225efed30a48d02fdbf56f2ee37239 98537 libs optional vdk2_2.4.0-5.4.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcRrgACgkQ3mO5xwTr
6e+isg/+IwWzbsFDIpK0bTSVe2ONvWQVZS57J/VeDENAyy8+LDV3dH7I3M2gViBf
oBYLDyq9/IprjvFcPnIogUXp+pG4+Y8qw1SMOOmsNZ7jVs9xBlGf2EnFzMsGP++8
hUYkTvUPP2osi2HVfB2jd6Ss8o7GgdbKApV4dRwXrqIUCUhvGElMi00MZ1xZXzHw
OP6QgtjwBsmE3i3SCGxrm3GHKK66y47yUNANZafh7wdhI/LwPXf2nuTKhBnxvHia
Be+gWLPXXaacBDUomX18dGwv17WyJL/97bbpEaYO9LVaeLvBdKFIPSRU14wxgWyL
/8DIo+We8JOqEmaABfSkBmkVbUurFSZL5karhaKRFUE60MIyDMWZvtxzO6edhm9X
E3YEvlyoeVdISFRNil2WQc2jrYoYj5fTY4A3Tgqgk3xQfNujIn5tO4gPVv+7hBk4
Xfff5Nn/lc7bPql+YFCtb7muubEiBSSqSG45ROfGQFI7McfoI0pp3Z0mDT01N2lT
x+pGDPcmbikrcgIcUGeABFDXrkfBrWQFfqo9CQnvU4LAf1+13rcFmYTwZr1Jty0Z
sR731YEiDO2sv1meUqcumSNMfWtCHfe/aplK4usGvsCK60rqefOndi7Uly8Tyb7z
Lu8Sn9HOBoEGdFa59f390anOOm5rcOpmYd1JonwpB+WdxgJoOVk=
=sW8O
-END PGP SIGNATURE End Message ---

Bug#817712: marked as done (vdk2: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 22:04:23 +
with message-id 
and subject line Bug#817712: fixed in vdk2 2.4.0-5.4
has caused the Debian Bug report #817712,
regarding vdk2: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdk2
Severity: important
Usertags: compat-4-removal

Hi,

The package vdk2 uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: vdk2
Source-Version: 2.4.0-5.4

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated vdk2 
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, 22 Dec 2016 19:11:49 -0200
Source: vdk2
Binary: libvdk2-2c2 libvdk2-doc libvdk2-dev libvdk2-dbg
Architecture: source
Version: 2.4.0-5.4
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt 
Changed-By: Joao Eriberto Mota Filho 
Description:
 libvdk2-2c2 - Visual Development Kit C++ library version 2
 libvdk2-dbg - debugging static library for the VDK C++ library version 2
 libvdk2-dev - header files and static libraries for VDK library version 2
 libvdk2-doc - documentation for VDK library version 2
Closes: 817712 822034
Changes:
 vdk2 (2.4.0-5.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817712)
   * debian/control:
   - Added a Homepage field.
   - Bumped Standards-Version to 3.9.8.
   * debian/rules: fix missing targets. Thanks to Santiago Vila
 . (Closes: #822034)
   * debian/watch: created.
Checksums-Sha1:
 6577e334dbfd6ce681dab739a3975b7cc898a17b 1990 vdk2_2.4.0-5.4.dsc
 bc7a7c9b49f6054ca4e78acd391a7415b2c4662c 98537 vdk2_2.4.0-5.4.diff.gz
Checksums-Sha256:
 664c09ebeb6aa9e815d6b2dd3274ef90c9c1a08f4e996bd74c64ab99c613 1990 
vdk2_2.4.0-5.4.dsc
 c492ea99557e28103c2452ae576bede9b494318b952b92dbd1e625a4460f082d 98537 
vdk2_2.4.0-5.4.diff.gz
Files:
 724827421b13f66a78af5dafb4294bb0 1990 libs optional vdk2_2.4.0-5.4.dsc
 97225efed30a48d02fdbf56f2ee37239 98537 libs optional vdk2_2.4.0-5.4.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhcRrgACgkQ3mO5xwTr
6e+isg/+IwWzbsFDIpK0bTSVe2ONvWQVZS57J/VeDENAyy8+LDV3dH7I3M2gViBf
oBYLDyq9/IprjvFcPnIogUXp+pG4+Y8qw1SMOOmsNZ7jVs9xBlGf2EnFzMsGP++8
hUYkTvUPP2osi2HVfB2jd6Ss8o7GgdbKApV4dRwXrqIUCUhvGElMi00MZ1xZXzHw
OP6QgtjwBsmE3i3SCGxrm3GHKK66y47yUNANZafh7wdhI/LwPXf2nuTKhBnxvHia
Be+gWLPXXaacBDUomX18dGwv17WyJL/97bbpEaYO9LVaeLvBdKFIPSRU14wxgWyL
/8DIo+We8JOqEmaABfSkBmkVbUurFSZL5karhaKRFUE60MIyDMWZvtxzO6edhm9X
E3YEvlyoeVdISFRNil2WQc2jrYoYj5fTY4A3Tgqgk3xQfNujIn5tO4gPVv+7hBk4
Xfff5Nn/lc7bPql+YFCtb7muubEiBSSqSG45ROfGQFI7McfoI0pp3Z0mDT01N2lT
x+pGDPcmbikrcgIcUGeABFDXrkfBrWQFfqo9CQnvU4LAf1+13rcFmYTwZr1Jty0Z
sR731YEiDO2sv1meUqcumSNMfWtCHfe/aplK4usGvsCK60rqefOndi7Uly8Tyb7z
Lu8Sn9HOBoEGdFa59f390anOOm5rcOpmYd1JonwpB+WdxgJoOVk=
=sW8O
-END PGP SIGNATURE End Message ---

Processed (with 1 error): forcibly merging 848422 848596

[Debian Bug Tracking System]

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

> forcemerge 848422 848596
Bug #848422 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: error: dpkg: error: version '' has bad syntax: version 
string is empty
Bug #848413 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: error: dpkg: error: version '' has bad syntax: version 
string is empty
Bug #848511 {Done: Guillem Jover } [dpkg] dirmngr: fails to 
install: dpkg-maintscript-helper: error: dpkg: error: version '' has bad 
syntax: version string is empty
Bug #848580 {Done: Guillem Jover } [dpkg] 
dpkg-maintscript-helper: fails if optional version is not given
Bug #848696 {Done: Guillem Jover } [dpkg] valgrind: prerm 
fails: dpkg-maintscript-helper: error: dpkg: error: version '' has bad syntax: 
version string is empty
Unable to merge bugs because:
package of #848596 is 'dirmngr' not 'dpkg'
Failed to forcibly merge 848422: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
848413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848413
848422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848422
848511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848511
848580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848580
848596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848596
848696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Tag #848771 as pending

[Debian Bug Tracking System]

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

> tags 848771 + pending
Bug #848771 [src:numexpr] numexpr: FTBFS: Test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#827810: marked as done (scanlogd: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 21:10:21 +
with message-id 
and subject line Bug#827810: fixed in scanlogd 2.2.5-3.3
has caused the Debian Bug report #827810,
regarding scanlogd: FTBFS: dh_clean: Please specify the compatibility level in 
debian/compat
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.)


-- 
827810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scanlogd
Version: 2.2.5-3.2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

scanlogd fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  scanlogd
   Version:  2.2.5-3.2
   Build architecture:   amd64
   Date: Tue, 21 Jun 2016 10:50:16 +0100
   Hostname: fb14883e52d8
   Uname:Linux fb14883e52d8 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'scanlogd-build-deps' in 
'../scanlogd-build-deps_2.2.5-3.2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package scanlogd-build-deps.
  (Reading database ... 23077 files and directories currently installed.)
  Preparing to unpack scanlogd-build-deps_2.2.5-3.2_all.deb ...
  Unpacking scanlogd-build-deps (2.2.5-3.2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up scanlogd-build-deps (2.2.5-3.2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=fb14883e52d8
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160621105014.ihdkOKXbow.scanlogd/scanlogd-2.2.5
  OLDPWD=/home/lamby/temp/cdt.20160621105014.ihdkOKXbow.scanlogd
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building scanlogd 2.2.5-3.2 on amd64   
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package scanlogd
  dpkg-buildpackage: info: source version 2.2.5-3.2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Andreas Beckmann 
   dpkg-source --before-build scanlogd-2.2.5
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -f build-stamp configure-stamp
  # Add here commands to clean up after the build process.
  /usr/bin/make clean
  make[1]: Entering directory 

Bug#848493: marked as done (squid3: CVE-2016-10002: SQUID-2016:11: Information disclosure in HTTP Request processing)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 21:02:20 +
with message-id 
and subject line Bug#848493: fixed in squid3 3.4.8-6+deb8u4
has caused the Debian Bug report #848493,
regarding squid3: CVE-2016-10002: SQUID-2016:11: Information disclosure in HTTP 
Request processing
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.)


-- 
848493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squid3
Version: 3.4.8-6
Severity: important
Tags: security upstream patch fixed-upstream

Hi

>From http://www.squid-cache.org/Advisories/SQUID-2016_11.txt

> Problem Description:
> 
>  Due to incorrect HTTP conditional request handling Squid can
>  deliver responses containing private data to clients it should
>  not have reached.

A CVE has been requested in 
http://www.openwall.com/lists/oss-security/2016/12/17/1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: squid3
Source-Version: 3.4.8-6+deb8u4

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2016 11:47:19 +0100
Source: squid3
Binary: squid3 squid3-dbg squid3-common squidclient squid-cgi squid-purge
Architecture: all source
Version: 3.4.8-6+deb8u4
Distribution: jessie-security
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Salvatore Bonaccorso 
Closes: 819563 848493
Description: 
 squid-cgi  - Full featured Web Proxy cache (HTTP proxy) - control CGI
 squid-purge - Full featured Web Proxy cache (HTTP proxy) - control utility
 squid3 - Full featured Web Proxy cache (HTTP proxy)
 squid3-common - Full featured Web Proxy cache (HTTP proxy) - common files
 squid3-dbg - Full featured Web Proxy cache (HTTP proxy) - Debug symbols
 squidclient - Full featured Web Proxy cache (HTTP proxy) - control utility
Changes:
 squid3 (3.4.8-6+deb8u4) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix cache_peer login=PASS(THRU) after CVE-2015-5400.
 Thanks to Amos Jeffries  (Closes: #819563)
   * CVE-2016-10002: Information disclosure in HTTP Request processing
 (Closes: #848493)
Checksums-Sha1: 
 aea9d693617d9060f03d73e9ac97ce742459b4de 2501 squid3_3.4.8-6+deb8u4.dsc
 f69b769ed103871e6ab767328713e8cb2585405a 41124 
squid3_3.4.8-6+deb8u4.debian.tar.xz
 fc9aa7470097df32de7aaf487ea9dc3b2179cb20 258548 
squid3-common_3.4.8-6+deb8u4_all.deb
Checksums-Sha256: 
 3c19984d630de12dc191189c59255a15c70f86df5874fb56e812bb483d3648ae 2501 
squid3_3.4.8-6+deb8u4.dsc
 cd12f31bfd2d4ef5519cafb683713f5c63f25331bd64be6ce930fdd64b5d7a46 41124 
squid3_3.4.8-6+deb8u4.debian.tar.xz
 202e3452e24b057512b061001ba2970398540ce56fc56db978b5860343d00561 258548 
squid3-common_3.4.8-6+deb8u4_all.deb
Files: 
 d8881b2709492ca294568e41a89dffab 2501 web optional squid3_3.4.8-6+deb8u4.dsc
 1e8f56bc5c08232a0ba63d69f8ff262e 41124 web optional 
squid3_3.4.8-6+deb8u4.debian.tar.xz
 f75d5c6ec82390569e0e98f7534971af 258548 web optional 
squid3-common_3.4.8-6+deb8u4_all.deb

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlhWa/1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EiNwP/069vEzhVduLvDjmTf8my5DqJa+YH1oz
Dwu33jWhhwiEhgo6MD3/f9miItj0yE2NfvhEyc2xF0OwA30gw0ZjyUqdSSiR7uD4
ZB3WPdg0iRZ9Yt7bEDjjB//U7P3GfnIsrRPvn5G2qhIAq3kTSWEjvwOC6FXCCPKq
tejwDcFwmShJrNd5Ra2XB5lpUYnfp7xjp1caQnDOPLla1ACxrLFAKKW3m1MrDF2N
c8kzYvNVBo2JR6G5UTq4Ik/JZxAfN/uha+KTPLSQiRkeMmExjHxM21lVnJmKRHFa
K+41LcJHPwMj322J9SK+4snjvjkQ+RdDWO67sliGIfye4t/aOpCqTAyAkGRFY8aM
EJI/mhfXvtfSEAzWB+eVwZXYLdCO81Lcq41o07bwthN8YbCueAevHARtzupF+jO8
SjSQYrB82LGH0WKAqhDZIpXQijJtqzyMOMOsGoqiCwvJKSUNv/Sx9bC3RjKuJWrG

Bug#787398: marked as done (evolution-data-server: SMTP connection lost while reading message data)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 21:02:11 +
with message-id 
and subject line Bug#787398: fixed in evolution-data-server 
3.12.9~git20141128.5242b0-2+deb8u3
has caused the Debian Bug report #787398,
regarding evolution-data-server: SMTP connection lost while reading message data
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.)


-- 
787398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evolution-data-server
Version: 3.12.9~git20141128.5242b0-2+deb8u2
Severity: critical
Tags: patch
Justification: causes serious data loss

Hi there,

there is a serious bug in libcamel 3.12.3. This bug is not fixed in
3.12.11 and since 3.12.11 is the last upstream release of that
branch, it will not get fixed in any 3.12.x version ever.

It happens that you when send a mail in Evolution, the program reports no
error message at all and moves your mail to the Sent folder, whereas
the mail has not been sent at all! On the SMTP server side an error
like "SMTP connection lost while reading message data" is logged.
This happens especially with mails with attachments. The bug has been
identified upstream and is fixed in the 3.16 series, but not in 3.12 as
mentioned before:

https://bugzilla.gnome.org/show_bug.cgi?id=749292

The patch is simple and replaces a call to g_output_stream_write()
aith one to g_output_stream_write_all(). I have applied this patch to
a local copy I rebuilt of e-d-s and confirm that it fixes the issue
for me.

Since this issue caused silent loss of important data for me, I'd like
to ask for the patch to get applied to the 3.12 version in unstable
ASAP. Also, I believe this must definitely get applied to the version
in stable as well.

Thank you very much already,

 - Fabian


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

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

Versions of packages evolution-data-server depends on:
ii  evolution-data-server-common  3.12.9~git20141128.5242b0-2+deb8u2
ii  gnome-keyring 3.16.0-2
ii  libc6 2.19-18
ii  libcamel-1.2-49   3.12.9~git20141128.5242b0-2+deb8u2
ii  libdb5.3  5.3.28-9
ii  libebackend-1.2-7 3.12.9~git20141128.5242b0-2+deb8u2
ii  libebook-1.2-14   3.12.9~git20141128.5242b0-2+deb8u2
ii  libebook-contacts-1.2-0   3.12.9~git20141128.5242b0-2+deb8u2
ii  libecal-1.2-163.12.9~git20141128.5242b0-2+deb8u2
ii  libedata-book-1.2-20  3.12.9~git20141128.5242b0-2+deb8u2
ii  libedata-cal-1.2-23   3.12.9~git20141128.5242b0-2+deb8u2
ii  libedataserver-1.2-18 3.12.9~git20141128.5242b0-2+deb8u2
ii  libgcr-base-3-1   3.14.0-2
ii  libgcr-ui-3-1 3.14.0-2
ii  libgdata190.16.1-1
ii  libglib2.0-0  2.45.1-2
ii  libgoa-1.0-0b 3.14.2-1
ii  libgtk-3-03.14.5-1
ii  libgweather-3-6   3.16.1-1
ii  libical1a 1.0-1.3
ii  libldap-2.4-2 2.4.40+dfsg-1
ii  libpango-1.0-01.36.8-3
ii  libsecret-1-0 0.18.2-1
ii  libsoup2.4-1  2.48.0-1
ii  libxml2   2.9.1+dfsg1-5

evolution-data-server recommends no packages.

Versions of packages evolution-data-server suggests:
ii  evolution  3.12.9~git20141130.241663-1+b1
pn  evolution-data-server-dbg  

-- no debconf information
>From bae0c643978a67f5368b6b0e5638b97687ee443a Mon Sep 17 00:00:00 2001
From: Milan Crha 
Date: Mon, 9 Feb 2015 12:58:09 +0100
Subject: Make camel_stream_write() try to write all bytes at once

The default implementation of CamelStream::write() used
g_output_stream_write() method, which could write only a partial
content, returning how many bytes had been actually written. That's
fine, but not each caller counted with this, thus for example
a CamelStreamFilter::write() failed when only partial buffer had
been written, which could cause a silent failure on message send.
Easier than taking care of the not-whole-buffer-written state
at each place of the usage is to use g_output_stream_write_all()
function instead, which fails only on errors.

This had 

Bug#840553: marked as done (libxml2: CVE-2016-4658)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 21:02:12 +
with message-id 
and subject line Bug#840553: fixed in libxml2 2.9.1+dfsg1-5+deb8u4
has caused the Debian Bug report #840553,
regarding libxml2: CVE-2016-4658
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.)


-- 
840553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.4+dfsg1-2
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for libxml2.

CVE-2016-4658[0]:
| libxml2 in Apple iOS before 10, OS X before 10.12, tvOS before 10, and
| watchOS before 3 allows remote attackers to execute arbitrary code or
| cause a denial of service (memory corruption) via a crafted XML
| document.

Although the MITRE description at the moment explicitly mention that
as Apple related, the upstream commit is now know as [1].

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-2016-4658
[1] 
https://git.gnome.org/browse/libxml2/commit/?id=c1d1f7121194036608bf555f08d3062a36fd344b

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.1+dfsg1-5+deb8u4

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2016 19:42:58 +0100
Source: libxml2
Binary: libxml2 libxml2-utils libxml2-utils-dbg libxml2-dev libxml2-dbg 
libxml2-doc python-libxml2 python-libxml2-dbg
Architecture: all source
Version: 2.9.1+dfsg1-5+deb8u4
Distribution: jessie-security
Urgency: high
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 840553 840554
Description: 
 libxml2- GNOME XML library
 libxml2-dbg - Debugging symbols for the GNOME XML library
 libxml2-dev - Development files for the GNOME XML library
 libxml2-doc - Documentation for the GNOME XML library
 libxml2-utils - XML utilities
 libxml2-utils-dbg - XML utilities (debug extension)
 python-libxml2 - Python bindings for the GNOME XML library
 python-libxml2-dbg - Python bindings for the GNOME XML library (debug 
extension)
Changes:
 libxml2 (2.9.1+dfsg1-5+deb8u4) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix comparison with root node in xmlXPathCmpNodes
   * Fix XPointer paths beginning with range-to (CVE-2016-5131)
(Closes: #840554)
   * Disallow namespace nodes in XPointer ranges (CVE-2016-4658)
 (Closes: #840553)
   * Fix more NULL pointer derefs in xpointer.c
Checksums-Sha1: 
 efa2de3e0b0661c49d703e910cbb6da3641e1e17 2760 libxml2_2.9.1+dfsg1-5+deb8u4.dsc
 e27c423442c4d8fc2aae872da630510e93fda912 66756 
libxml2_2.9.1+dfsg1-5+deb8u4.debian.tar.xz
 04dff14d8a76e6eee670540c854b8af236130901 814770 
libxml2-doc_2.9.1+dfsg1-5+deb8u4_all.deb
Checksums-Sha256: 
 23f9a9935227718fd2921abb484c129617325e1306d8525b3dcec1611df01096 2760 
libxml2_2.9.1+dfsg1-5+deb8u4.dsc
 cda8374910db4e2a06b2515123dbe0b714f7f647532dc305f03c2a094175e706 66756 
libxml2_2.9.1+dfsg1-5+deb8u4.debian.tar.xz
 077cae3381c2ebfe6537190bf9204d953c3c96ce181474f4027cc8ead9ba8fc4 814770 
libxml2-doc_2.9.1+dfsg1-5+deb8u4_all.deb
Files: 
 f98c7d9f59e95b354ac6c443f0df4425 2760 libs optional 
libxml2_2.9.1+dfsg1-5+deb8u4.dsc
 baae4e43fa95061a79014dd525078545 66756 libs optional 
libxml2_2.9.1+dfsg1-5+deb8u4.debian.tar.xz
 3cb06339d607acd3d8a1e763ea3065d9 814770 doc optional 
libxml2-doc_2.9.1+dfsg1-5+deb8u4_all.deb

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlhViIdfFIAALgAo

Bug#840554: marked as done (libxml2: CVE-2016-5131)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 21:02:12 +
with message-id 
and subject line Bug#840554: fixed in libxml2 2.9.1+dfsg1-5+deb8u4
has caused the Debian Bug report #840554,
regarding libxml2: CVE-2016-5131
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.)


-- 
840554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.4+dfsg1-2
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for libxml2.

CVE-2016-5131[0]:
| Use-after-free vulnerability in libxml2 through 2.9.4, as used in
| Google Chrome before 52.0.2743.82, allows remote attackers to cause a
| denial of service or possibly have unspecified other impact via
| vectors related to the XPointer range-to function.

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-2016-5131
[1] 
https://git.gnome.org/browse/libxml2/commit/?id=9ab01a277d71f54d3143c2cf333c5c2e9aaedd9e
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1358641#c3
[3] https://bugzilla.gnome.org/show_bug.cgi?id=768428 (not public)

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.1+dfsg1-5+deb8u4

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2016 19:42:58 +0100
Source: libxml2
Binary: libxml2 libxml2-utils libxml2-utils-dbg libxml2-dev libxml2-dbg 
libxml2-doc python-libxml2 python-libxml2-dbg
Architecture: all source
Version: 2.9.1+dfsg1-5+deb8u4
Distribution: jessie-security
Urgency: high
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 840553 840554
Description: 
 libxml2- GNOME XML library
 libxml2-dbg - Debugging symbols for the GNOME XML library
 libxml2-dev - Development files for the GNOME XML library
 libxml2-doc - Documentation for the GNOME XML library
 libxml2-utils - XML utilities
 libxml2-utils-dbg - XML utilities (debug extension)
 python-libxml2 - Python bindings for the GNOME XML library
 python-libxml2-dbg - Python bindings for the GNOME XML library (debug 
extension)
Changes:
 libxml2 (2.9.1+dfsg1-5+deb8u4) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix comparison with root node in xmlXPathCmpNodes
   * Fix XPointer paths beginning with range-to (CVE-2016-5131)
(Closes: #840554)
   * Disallow namespace nodes in XPointer ranges (CVE-2016-4658)
 (Closes: #840553)
   * Fix more NULL pointer derefs in xpointer.c
Checksums-Sha1: 
 efa2de3e0b0661c49d703e910cbb6da3641e1e17 2760 libxml2_2.9.1+dfsg1-5+deb8u4.dsc
 e27c423442c4d8fc2aae872da630510e93fda912 66756 
libxml2_2.9.1+dfsg1-5+deb8u4.debian.tar.xz
 04dff14d8a76e6eee670540c854b8af236130901 814770 
libxml2-doc_2.9.1+dfsg1-5+deb8u4_all.deb
Checksums-Sha256: 
 23f9a9935227718fd2921abb484c129617325e1306d8525b3dcec1611df01096 2760 
libxml2_2.9.1+dfsg1-5+deb8u4.dsc
 cda8374910db4e2a06b2515123dbe0b714f7f647532dc305f03c2a094175e706 66756 
libxml2_2.9.1+dfsg1-5+deb8u4.debian.tar.xz
 077cae3381c2ebfe6537190bf9204d953c3c96ce181474f4027cc8ead9ba8fc4 814770 
libxml2-doc_2.9.1+dfsg1-5+deb8u4_all.deb
Files: 
 f98c7d9f59e95b354ac6c443f0df4425 2760 libs optional 
libxml2_2.9.1+dfsg1-5+deb8u4.dsc
 baae4e43fa95061a79014dd525078545 66756 libs optional 
libxml2_2.9.1+dfsg1-5+deb8u4.debian.tar.xz
 3cb06339d607acd3d8a1e763ea3065d9 814770 doc optional 
libxml2-doc_2.9.1+dfsg1-5+deb8u4_all.deb

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlhViIdfFIAALgAo

Processed: astropy bug affects many affiliated packages

[Debian Bug Tracking System]

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

> found 849271 python-astropy/1.3-1
Bug #849271 [python-astropy] version comparison fails with numpy 1.12.0b1
Marked as found in versions python-astropy/1.3-1.
>
End of message, stopping processing here.

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

Processed: Re: jupyter-nbextension-jupyter-js-widgets: fails to configure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 jupyter-notebook 4.2.3-2
Bug #849204 [jupyter-nbextension-jupyter-js-widgets] 
jupyter-nbextension-jupyter-js-widgets: fails to configure
Bug reassigned from package 'jupyter-nbextension-jupyter-js-widgets' to 
'jupyter-notebook'.
No longer marked as found in versions ipywidgets/5.2.2-2.
Ignoring request to alter fixed versions of bug #849204 to the same values 
previously set
Bug #849204 [jupyter-notebook] jupyter-nbextension-jupyter-js-widgets: fails to 
configure
Marked as found in versions jupyter-notebook/4.2.3-2.
> severity -1 normal
Bug #849204 [jupyter-notebook] jupyter-nbextension-jupyter-js-widgets: fails to 
configure
Severity set to 'normal' from 'grave'
> close -1 4.2.3-3
Bug #849204 [jupyter-notebook] jupyter-nbextension-jupyter-js-widgets: fails to 
configure
Marked as fixed in versions jupyter-notebook/4.2.3-3.
Bug #849204 [jupyter-notebook] jupyter-nbextension-jupyter-js-widgets: fails to 
configure
Marked Bug as done
> merge -1 847917
Bug #849204 {Done: Ximin Luo } [jupyter-notebook] 
jupyter-nbextension-jupyter-js-widgets: fails to configure
Bug #847917 {Done: Ximin Luo } [jupyter-notebook] 
jupyter-notebook: Unhandled error in API request
Merged 847917 849204

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

Bug#848801: marked as done (strace: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 20:33:51 +
with message-id <20161224203351.ga7...@einval.com>
and subject line Re: Bug#848801: strace: FTBFS: Test failures
has caused the Debian Bug report #848801,
regarding strace: FTBFS: Test failures
to be marked as done.

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

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


-- 
848801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strace
Version: 4.13-0.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[8]: Entering directory '/<>/build/tests'
> make[8]: Nothing to be done for 'all-am'.
> make[8]: Leaving directory '/<>/build/tests'
> make[7]: Leaving directory '/<>/build/tests'
> ===
>strace 4.13: tests/test-suite.log
> ===
> 
> # TOTAL: 313
> # PASS:  263
> # SKIP:  47
> # XFAIL: 0
> # FAIL:  3
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> SKIP: _newselect
> 
> 
> + ../strace -V
> + TIMEOUT=timeout -s 9 60
> + timeout -s 9 60 true
> + exec timeout -s 9 60 ../../tests/_newselect.test
> + run_strace_match_diff -a36
> + args=-a36
> + [ -n -a36 -a -z -a36 ]
> + set -- -e trace=_newselect -a36
> + run_prog
> + [ 0 -eq 0 ]
> + set -- ./_newselect
> + args=./_newselect
> + ./_newselect
> undefined: __NR__newselect
> + [ 77 -eq 77 ]
> + skip_ ./_newselect exited with code 77
> + warn_ _newselect.test: skipped test: ./_newselect exited with code 77
> + printf %s\n _newselect.test: skipped test: ./_newselect exited with code 77
> _newselect.test: skipped test: ./_newselect exited with code 77
> + exit 77
> 
> SKIP: btrfs-w
> =
> 
> + ../strace -V
> + TIMEOUT=timeout -s 9 60
> + timeout -s 9 60 true
> + exec timeout -s 9 60 ../../tests/btrfs-w.test
> + [ -z  ]
> + skip_ $BTRFS_MOUNTPOINT not set
> + warn_ btrfs-w.test: skipped test: $BTRFS_MOUNTPOINT not set
> + printf %s\n btrfs-w.test: skipped test: $BTRFS_MOUNTPOINT not set
> btrfs-w.test: skipped test: $BTRFS_MOUNTPOINT not set
> + exit 77
> 
> SKIP: btrfs-vw
> ==
> 
> + ../strace -V
> + TIMEOUT=timeout -s 9 60
> + timeout -s 9 60 true
> + exec timeout -s 9 60 ../../tests/btrfs-vw.test
> + [ -z  ]
> + skip_ $BTRFS_MOUNTPOINT not set
> + warn_ btrfs-vw.test: skipped test: $BTRFS_MOUNTPOINT not set
> + printf %s\n btrfs-vw.test: skipped test: $BTRFS_MOUNTPOINT not set
> btrfs-vw.test: skipped test: $BTRFS_MOUNTPOINT not set
> + exit 77
> 
> SKIP: chown32
> =
> 
> + ../strace -V
> + TIMEOUT=timeout -s 9 60
> + timeout -s 9 60 true
> + exec timeout -s 9 60 ../../tests/chown32.test
> + run_strace_match_diff -a31
> + args=-a31
> + [ -n -a31 -a -z -a31 ]
> + set -- -e trace=chown32 -a31
> + run_prog
> + [ 0 -eq 0 ]
> + set -- ./chown32
> + args=./chown32
> + ./chown32
> undefined: __NR_chown32
> + [ 77 -eq 77 ]
> + skip_ ./chown32 exited with code 77
> + warn_ chown32.test: skipped test: ./chown32 exited with code 77
> + printf %s\n chown32.test: skipped test: ./chown32 exited with code 77
> chown32.test: skipped test: ./chown32 exited with code 77
> + exit 77
> 
> SKIP: fchown32
> ==
> 
> + ../strace -V
> + TIMEOUT=timeout -s 9 60
> + timeout -s 9 60 true
> + exec timeout -s 9 60 ../../tests/fchown32.test
> + run_strace_match_diff -a18
> + args=-a18
> + [ -n -a18 -a -z -a18 ]
> + set -- -e trace=fchown32 -a18
> + run_prog
> + [ 0 -eq 0 ]
> + set -- ./fchown32
> + args=./fchown32
> + ./fchown32
> undefined: __NR_fchown32
> + [ 77 -eq 77 ]
> + skip_ ./fchown32 exited with code 77
> + warn_ fchown32.test: skipped test: ./fchown32 exited with code 77
> + printf %s\n fchown32.test: skipped test: ./fchown32 exited with code 77
> fchown32.test: skipped test: ./fchown32 exited with code 77
> + exit 77
> 
> SKIP: fcntl64
> =
> 
> + ../strace -V
> + TIMEOUT=timeout -s 9 60
> + timeout -s 9 60 true
> + exec timeout -s 9 60 ../../tests/fcntl64.test
> + run_strace_match_diff -a8
> + args=-a8
> + [ -n -a8 -a -z -a8 ]
> + set -- -e trace=fcntl64 -a8
> + run_prog
> + [ 0 -eq 0 ]
> + set -- ./fcntl64
> + args=./fcntl64
> + ./fcntl64
> undefined: __NR_fcntl64
> + [ 77 -eq 77 ]
> + skip_ ./fcntl64 exited with code 77
> + warn_ fcntl64.test: skipped test: ./fcntl64 exited with code 77
> + printf %s\n fcntl64.test: skipped test: ./fcntl64 exited with code 77
> fcntl64.test: skipped test: ./fcntl64 exited with code 77
> + 

Bug#849204: jupyter-nbextension-jupyter-js-widgets: fails to configure

[Ximin Luo]

Control: reassign -1 jupyter-notebook 4.2.3-2
Control: severity -1 normal
Control: close -1 4.2.3-3
Control: merge -1 847917

Hi Norbert, this is due to a bug in jupyter-notebook 4.2.3-2. You can fix it 
locally by removing any empty files matching /etc/jupyter/nbconfig/*.json, then 
reinstalling/reconfiguring ipywidgets.

Because 4.2.3-2 was only in unstable for about 3 days, I didn't think it was 
worth the effort trying to add logic to handle this case specifically. For more 
details see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847917

Please reopen/reassign the bug if my diagnosis was incorrect, and the error is 
caused by some other reason.

X

On Fri, 23 Dec 2016 22:02:28 +0900 Norbert Preining  wrote:
> Package: jupyter-nbextension-jupyter-js-widgets
> Version: 5.2.2-2
> Severity: grave
> Justification: renders package unusable
> 
> Hi all,
> 
> thanks for taking up the incredible complex job of packaging sagemath,
> that is very much appreciated.
> 
> Unforunately, the above package does not configure:
> Unpacking sagemath-jupyter (7.4-3) ...
> Setting up jupyter-nbextension-jupyter-js-widgets (5.2.2-2) ...
> /usr/lib/python3.5/runpy.py:125: RuntimeWarning: 'notebook.nbextensions' 
> found in sys.modules after import of package 'notebook', but prior to 
> execution of 'notebook.nbextensions'; this may result in unpredictable 
> behaviour
>   warn(RuntimeWarning(msg))
> Enabling notebook extension jupyter-js-widgets/extension...
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/runpy.py", line 193, in _run_module_as_main
> "__main__", mod_spec)
>   File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
> exec(code, run_globals)
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 1176, 
> in 
> main()
>   File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 
> 267, in launch_instance
> return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
>   File "/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
> 658, in launch_instance
> app.start()
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 961, 
> in start
> super(NBExtensionApp, self).start()
>   File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 
> 256, in start
> self.subapp.start()
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 871, 
> in start
> self.toggle_nbextension(self.extra_args[0])
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 861, 
> in toggle_nbextension
> logger=self.log)
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 407, 
> in enable_nbextension
> logger=logger)
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 345, 
> in _set_nbextension_state
> cm.update(section, {"load_extensions": {require: state}})
>   File "/usr/lib/python3/dist-packages/traitlets/config/manager.py", line 85, 
> in update
> data = self.get(section_name)
>   File "/usr/lib/python3/dist-packages/traitlets/config/manager.py", line 63, 
> in get
> return json.load(f)
>   File "/usr/lib/python3.5/json/__init__.py", line 268, in load
> parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
>   File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
> return _default_decoder.decode(s)
>   File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>   File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
> raise JSONDecodeError("Expecting value", s, err.value) from None
> json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
> dpkg: error processing package jupyter-nbextension-jupyter-js-widgets 
> (--configure):
>  subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of sagemath-jupyter:
>  sagemath-jupyter depends on jupyter-nbextension-jupyter-js-widgets; however:
>   Package jupyter-nbextension-jupyter-js-widgets is not configured yet.
> 
> Thanks
> 

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

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

[Daniel Shahaf]

Chris Lamb wrote on Sat, Dec 24, 2016 at 18:57:38 +:
> @@ -30,6 +31,17 @@ from test_java import javap_version
> +def enjarify_version():
> +# Module enjarify.typeinference appeared in enjarify 1.0.3.  We use a 
> call
> +# directly to the python3 binary over importing with this module to 
> escape
> +# virtualenvs, etc.
> +if subprocess.call(
> +('python3', '-c', 'import enjarify.typeinference'),

Use sys.executable instead of hardcoding 'python3', to handle the case
that there's more than one python3 binary on the system?

(This would be correct for straight python3; is it also correct with
virtualenvs at play?)

Cheers,

Daniel

> +stderr=subprocess.PIPE,
> +) == 0:
> +return '1.0.3'
> +return '1.0.2'

Processed: tagging 831128

[Debian Bug Tracking System]

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

> tags 831128 + pending
Bug #831128 [src:quickfix] quickfix: FTBFS with GCC 6
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#849216: Packages which FTBFS with AssertionError about len(context)

[Niko Tyni]

On Fri, Dec 23, 2016 at 06:41:20PM +0100, Santiago Vila wrote:
> Package: checkbox-ng,dhcpcanon,ipywidgets,nbsphinx,pylibmc
> Severity: serious
 
> The following packages currently FTBFS in testing:
> 
> checkbox-ng
> dhcpcanon
> ipywidgets
> nbsphinx
> pylibmc
> 
> with an AssertionError like this:

>   File "/usr/lib/python2.7/dist-packages/docutils/writers/_html_base.py", 
> line 671, in depart_document
> assert not self.context, 'len(context) = %s' % len(self.context)
> AssertionError: len(context) = 1

Seems to be https://github.com/sphinx-doc/sphinx/issues/3212
which should be fixed in sphinx_1.4.9-2, migrated to testing today or so.
-- 
Niko Tyni   nt...@debian.org

Bug#849142: marked as done (test regression in test_dex.test_differences with enjarify >= 1.0.3)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 19:48:23 +
with message-id 
and subject line Bug#849142: fixed in diffoscope 66
has caused the Debian Bug report #849142,
regarding test regression in test_dex.test_differences with enjarify >= 1.0.3
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.)


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

current version: git HEAD 8dde15f9200094882c26a1cf422556c43ec5d5dc

The test_differences test case fails in the test_dex module when using
enjarify 1.0.3. A downgrade of enjarify to 1.0.2 makes the test pass
again. As enjarify 1.0.3 itself seems to do what its supposed to do, i
think the test diff/output is just too strictly tied to the 1.0.2 output.

If the guess above is actually the case, a possible workaround may be to
expect enjarify to be 1.0.2 and skip the test otherwise.
However we start ending up with too many tests strictly tight to a very
specific toolset version, making a more general approach for multiple
sets more and more important.

cheers,
Levente

Logs:
=== FAILURES
===
___ test_differences
___

differences = [, ]>]>]

@skip_unless_tools_exist('enjarify', 'zipinfo', 'javap')
@skip_unless_tool_is_at_least('javap', javap_version, '1.8')
def test_differences(differences):
assert differences[0].source1 == 'test1.jar'
assert differences[0].source2 == 'test2.jar'
zipinfo = differences[0].details[0]
classdiff = differences[0].details[1]
assert zipinfo.source1 == 'zipinfo -v {}'
assert zipinfo.source2 == 'zipinfo -v {}'
assert classdiff.source1 == 'com/example/MainActivity.class'
assert classdiff.source2 == 'com/example/MainActivity.class'
expected_diff = open(data('dex_expected_diffs')).read()
found_diff = zipinfo.unified_diff +
classdiff.details[0].unified_diff
>   assert expected_diff == found_diff
E   assert '@@ -54,15 +5...args_size=1\n' == '@@ -54,15
+54...args_size=1\n'
E Skipping 500 identical leading characters in diff, use -v to show
E Skipping 1284 identical trailing characters in diff, use -v to
show
E -   fc227a58
E +   bc28236e
E - +  32-bit CRC value (hex): 19c9f64e
E ?^  ^ ^^^
E + +  32-bit CRC value (hex): 59c3af78
E ?^  ^^ ^^
E  compr

tests/comparators/test_dex.py:57: AssertionError
--- End Message ---
--- Begin Message ---
Source: diffoscope
Source-Version: 66

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated diffoscope package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 19:18:30 +
Source: diffoscope
Binary: diffoscope
Architecture: source
Version: 66
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Chris Lamb 
Description:
 diffoscope - in-depth comparison of files, archives, and directories
Closes: 848049 849142
Changes:
 diffoscope (66) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Update dex_expected_diffs and test requirement to ensure test compatibility
 with enjarify >= 1.0.3. (Closes: #849142)
   * Print the detected version in @skip_unless_tool_is_at_least test utility.
 .
   [ Maria Glukhova ]
   * Add detection of order-only difference in plain text format. (Closes: 
#848049)
 .
   [ anthraxx ]
   * Add OpenSSH Arch package to Recommends.
Checksums-Sha1:
 90f5202c59082bfa9f446c9cb61f785b82537c98 2923 diffoscope_66.dsc
 

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

[Chris Lamb]

Ximin Luo wrote:

> I still haven't managed to reproduce this myself but I'll just note
> for the record we have seen this on jenkins before

My guess is that one of the third-party Python extension modules that
we import does not correctly reference count Py_None. Someone did a
good writeup here:

  http://stackoverflow.com/a/15288194

Now, we just need to narrow down which one… and then fix it.  >.>


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

[Ximin Luo]

I still haven't managed to reproduce this myself but I'll just note for the 
record we have seen this on jenkins before:

https://jenkins.debian.net/job/reproducible_diffoscope_from_git_master/63/console

Santiago Vila:
> Package: src:diffoscope
> Version: 63
> Severity: serious
> 
> Hello folks.
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with python3 --with bash-completion --buildsystem=pybuild
>dh_testdir -i -O--buildsystem=pybuild
>dh_update_autotools_config -i -O--buildsystem=pybuild
>dh_autoreconf -i -O--buildsystem=pybuild
>dh_auto_configure -i -O--buildsystem=pybuild
> I: pybuild base:184: python3.5 setup.py config 
> running config
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> register-python-argcomplete diffoscope > debian/diffoscope.bash-completion
> rst2man debian/trydiffoscope.1.rst debian/trydiffoscope.1
> rst2man debian/diffoscope.1.rst debian/diffoscope.1
> 
> [... snipped ...]
> 
> diffoscope/comparators/squashfs.py144 1987%   75, 91, 
> 105, 111, 114, 126, 134, 154, 159-160, 163-164, 167-168, 181, 210-213, 227
> diffoscope/comparators/symlink.py  28  196%   35
> diffoscope/comparators/tar.py  13  0   100%
> diffoscope/comparators/text.py 25  292%   52-54
> diffoscope/comparators/utils.py   224 2390%   67, 
> 132-135, 182-183, 188-191, 195, 199, 300, 304, 308, 312, 320, 323, 326, 335, 
> 345, 348, 353
> diffoscope/comparators/xz.py   27  0   100%
> diffoscope/comparators/zip.py  90  397%   64, 70, 73
> diffoscope/config.py   24  292%   49, 57
> diffoscope/difference.py  327 2393%   75, 108, 
> 163, 305, 311, 321-325, 335, 353, 411, 426-428, 446-450, 456-461
> diffoscope/exc.py  15  847%   23-24, 
> 210-217
> diffoscope/main.py170 3281%   44-45, 160, 
> 162, 164-165, 189, 198-203, 209, 224, 229, 240, 253, 258, 264-267, 273, 279, 
> 284, 295, 297-301, 306
> diffoscope/presenters/__init__.py   0  0   100%
> diffoscope/presenters/html.py 42411373%   253, 282, 
> 367, 372, 374-376, 406, 409, 411, 437, 451, 456, 493-497, 506-509, 513-519, 
> 536-560, 576-577, 580-581, 593-594, 597-601, 609-612, 622-625, 640, 653-656, 
> 666-667, 672-673, 681-683, 713-715, 722, 739, 744-746, 752-753, 766-798
> diffoscope/presenters/icon.py   1  0   100%
> diffoscope/presenters/text.py  36  489%   34, 61-63
> diffoscope/progress.py 68 2169%   39-44, 47, 
> 52, 57, 61, 66, 70, 95-104, 107-109, 112, 116, 119, 122
> -
> TOTAL379359984%
> Coverage HTML written to dir htmlcov
> 
> === short test summary info 
> 
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:80: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_fsimage.py:79: 
> guestfs not working on the system
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_fsimage.py:61: 
> guestfs not working on the system
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:87: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_utils.py:49: 
> requires /missing
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_utils.py:45: 
> requires
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:75: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:64: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:60: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:56: 
> requires cbfstool
> SKIP [1] 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/comparators/test_haskell.py:33:
>  mismatch between system ghc and fixture
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_macho.py:50: 
> requires otool and lipo
> SKIP [1] 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/comparators/test_haskell.py:47:
>  mismatch between system ghc and fixture
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_fsimage.py:50: 
> guestfs not working on the system
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_macho.py:43: 
> requires otool and lipo
> 
> === 233 passed, 15 skipped in 237.38 seconds 
> ===
> Fatal Python error: 

Bug#849293: marked as done (virt-manager is uninstallable: virtinst binary package went missing)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 19:34:31 +
with message-id 
and subject line Bug#849293: fixed in virt-manager 1:1.4.0-5
has caused the Debian Bug report #849293,
regarding virt-manager is uninstallable: virtinst binary package went missing
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.)


-- 
849293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virt-manager
Version: 1:1.4.0-4
Severity: grave
Justification: renders package unusable

virt-manager Depends on virtinst. Both are produced by src:virt-manager
and are Architecture: all, but the 1:1.4.0-4 upload somehow includes
virt-manager_*_all.deb but not virtinst_*_all.deb.
 says:

> Files: 
>  120ff4558a7c16d7ce34e819c4443658 2167 admin optional virt-manager_1.4.0-4.dsc
>  6845af224bda02baf0224d337d019f18 15208 admin optional 
> virt-manager_1.4.0-4.debian.tar.xz
>  245d8408f4a1242ab2d26b8fed725467 913498 admin optional 
> virt-manager_1.4.0-4_all.deb

I don't know how this happened, but when I rebuilt it in a clean sid chroot
with sbuild, I correctly got both binary packages produced.

I would suggest making source-only uploads so that the Architecture: all
buildd will do the build in a predictable environment (this worked in my
sbuild when I tried it, so hopefully it will work equally well on buildds).

Regards,
S

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: virt-manager
Source-Version: 1:1.4.0-5

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated virt-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 19:56:55 +0100
Source: virt-manager
Binary: virt-manager virtinst
Architecture: source
Version: 1:1.4.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Closes: 849293
Description: 
 virtinst   - Programs to create and clone virtual machines
 virt-manager - desktop application for managing virtual machines
Changes:
 virt-manager (1:1.4.0-5) unstable; urgency=medium
 .
   * Reupload with virtinst (Closes: #849293)
Checksums-Sha1: 
 535247092551573891dece988d6b84948ab12273 2167 virt-manager_1.4.0-5.dsc
 d7541a3fda38c40e79880d0c884539ef0645bd24 15224 
virt-manager_1.4.0-5.debian.tar.xz
Checksums-Sha256: 
 39c1cd4d3ee120e1856e5a7dd8af653ce772cc531c0f8a49339bb8e2997e4787 2167 
virt-manager_1.4.0-5.dsc
 2e074d1ad1163c8dc0054121117b5f2eb3f85168b2c240d49cc99d6365433d11 15224 
virt-manager_1.4.0-5.debian.tar.xz
Files: 
 bc9db4d9cf3611f19c3430d08815d525 2167 admin optional virt-manager_1.4.0-5.dsc
 3cb0a9f9813ad77551cd9b3eccff8da1 15224 admin optional 
virt-manager_1.4.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAlheyk8ACgkQB7i3sOqY
EgsvEBAApoHPZlEX3B8niBHGj8XmJ6qIUSuVJCidijFeBTZE10oFFAhYSoWIBeNo
QA/g2rxpBk92vzFC4/HltV0kT5WvBJeFdlBWLavBK5WRpIOmFyXYSSPnirwTyH7g
VhDZ56xWEkCWdnVsJ3QlCKl9IqlrYpOFLBpYLyrdNfb5KbNkAwx9OV9eqDG8rVTP
E6ILt5SOHfjW1fH8fxwIbuZpHqG/gj0zeCFtJoCKQdb6VyI/VDxEoUWRvroWTg04
kEIz2JIa3KtjPJ6cjlzpIMaoTI6FmkVsxZdS/qtjKNQzNJn2ZhVcEUQSxAusZAOG
WuqmtEnrkA65myq/r4HnRn7bo+IzNFbq8+Gt4WzslGYa2cenV8HfSQ+jBj0FHRTp
RYOduiGJpVd4KNI7Gd5Xx+L0489eGwjw7r2XPJMohGGVumZlPEkvVYCF7B3Kvl77

Bug#715569: marked as done (Official mod_vroot lib broken, lib built from source works)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 19:34:19 +
with message-id 
and subject line Bug#715569: fixed in proftpd-mod-vroot 0.9.4-1
has caused the Debian Bug report #715569,
regarding Official mod_vroot lib broken, lib built from source works
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.)


-- 
715569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-mod-vroot
Version: 0.9.2-2+b2
Severity: grave

We are currently using the amd64 Debian Squeeze version of mod_vroot
for ProFTPD on some of our servers and wanted to upgrade to Wheezy,
however we encountered problems - the Wheezy Version of mod_vroot
did not seem to work at all, it verifiably gets loaded, but something
is broken, so the modules vroot restrictions do not apply at all.

We tried to debug the issue and ran into an oddity regarding the
current official Debian package for proftpd-mod-vroot:

If we build the package 1:1 from Debian sources via dpkg-buildpackage,
we get a slightly different/larger binary than the official binary, and
this self-built binary then works as expected.

Our steps to build the package (on a plain Wheezy amd64 box with installed/
up-to-date proftpd-dev package):

wget 
http://ftp.de.debian.org/debian/pool/main/p/proftpd-mod-vroot/proftpd-mod-vroot_0.9.2-2.dsc
 
http://ftp.de.debian.org/debian/pool/main/p/proftpd-mod-vroot/proftpd-mod-vroot_0.9.2.orig.tar.gz
 
http://ftp.de.debian.org/debian/pool/main/p/proftpd-mod-vroot/proftpd-mod-vroot_0.9.2-2.debian.tar.gz
dpkg-source -x *.dsc; cd proftpd-mod-vroot-0.9.2
dpkg-buildpackage -us -uc -rfakeroot

The resulting binary size of mod_vroot.so is 28160, current official
(0.9.2-2+b2) binary size: 28080

Is it possible that the officially shipped binary is broken or was built
with an older ProFTPD version?


-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (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/bash

Versions of packages proftpd-mod-vroot depends on:
ii  libc6   2.13-38
ii  proftpd-basic [proftpd-abi-1.3.4a]  1.3.4a-4+nmu1

proftpd-mod-vroot recommends no packages.

proftpd-mod-vroot suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: proftpd-mod-vroot
Source-Version: 0.9.4-1

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-mod-vroot 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: SHA1

Format: 1.8
Date: Sat, 24 Dec 2016 19:42:04 +0100
Source: proftpd-mod-vroot
Binary: proftpd-mod-vroot
Architecture: source amd64
Version: 0.9.4-1
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-mod-vroot - ProFTPD module mod_vroot
Closes: 715569 732660 759936
Changes:
 proftpd-mod-vroot (0.9.4-1) unstable; urgency=medium
 .
   [ Mahyuddin Susanto ]
   * Team upload.
   * New Upstream release 0.9.3.
 -> It has a fix for erroneous function vroot_lookup_path (Closes: #759936)
   * Bump Standard Version to 3.9.5.
   * d/changelog: fix previous release pocket, already uploaded but
 still unreleased.
   * d/watch: upstream moved to github (Closes: #732660)
   * Rebuild against latest proftpd (Closes: #715569)
 .
   [Hilmar Preuße]
   * d/control: Remove "DM-Upload-Allowed" field
   * d/rules: add --without python-support to dh call
   * d/rules: overhaul clean target to make it work
 .
   [ Francesco Paolo Lovergine ]
   * New upstream release.
   * Policy bumped to 3.9.8.
Checksums-Sha1:
 3f8966443bea06146a116c00cfd10d74651114f7 2112 

Bug#800711: marked as done (proftpd-basic: Chroot with and without mod_vroot fails silently dropping, clients to /)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 19:34:19 +
with message-id 
and subject line Bug#715569: fixed in proftpd-mod-vroot 0.9.4-1
has caused the Debian Bug report #715569,
regarding proftpd-basic: Chroot with and without mod_vroot fails silently 
dropping, clients to /
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.)


-- 
715569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-basic
Version: 1.3.4a-5+deb7u3
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
I upgraded proftpd-basic from 1.3.3a-6squeeze7 to the version
mentioned and installed proftpd-mod-vroot. The configs were unchanged.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I commented the line "Include /etc/proftpd/modules.conf" but it was
ineffective. Setting "VRootEngine off" was ineffective as well.
   * What was the outcome of this action?
There are two outcomes depending on whether an authenticated system
user logs in or an anonymous user:
 
Authenticated:
User is dropped to root-level (/) where he has no permissions.
(Chroot fails silently)
Anonymous:
The proftpd process prints a lot of failured to root wall. User
is not able to log in anonymously.

Wall output is ATTACHED.



   * What outcome did you expect instead?
1. I expect an authenticated user to be chrooted to his home
directory or at least get some error message about why chrooting failed.
2. I expect an anonymous user to be chrooted into his home directory
and being able to log in.


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

Kernel: Linux 3.2.0-0.bpo.4-rt-amd64 (SMP w/22 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages proftpd-basic depends on:
ii  adduser 3.113+nmu3
ii  debconf 1.5.49
ii  debianutils 4.3.2
ii  libacl1 2.2.51-8
ii  libattr11:2.4.46-8
ii  libc6   2.13-38+deb7u8
ii  libcap2 1:2.22-1.2
ii  libncurses5 5.9-10
ii  libpam-runtime  1.1.3-7.1
ii  libpam0g1.1.3-7.1
ii  libssl0.9.8 0.9.8o-4squeeze21
ii  libwrap07.6.q-24
ii  netbase 5.0
ii  sed 4.2.1-10
ii  ucf 3.0025+nmu3
ii  update-inetd4.43
ii  zlib1g  1:1.2.7.dfsg-13

proftpd-basic recommends no packages.

Versions of packages proftpd-basic suggests:
ii  openssl1.0.1e-2+deb7u17
pn  proftpd-doc
pn  proftpd-mod-ldap   
pn  proftpd-mod-mysql  
pn  proftpd-mod-odbc   
pn  proftpd-mod-pgsql  
pn  proftpd-mod-sqlite 
ii  xinetd [inet-superserver]  1:2.3.14-7.1+deb7u1

-- Configuration Files:
/etc/default/proftpd changed:
RUN="yes"
OPTIONS="-DANONYMOUS_FTP"

/etc/logrotate.d/proftpd-basic changed:
/home/user/logs/ftp.xferlog
{
weekly
missingok
rotate 8
compress
delaycompress
notifempty
create 640 user user
sharedscripts
prerotate
endscript
postrotate
# reload could be not sufficient for all logs, a restart is safer
invoke-rc.d proftpd restart 2>/dev/null >/dev/null #|| true
# run ftpstats on past transfer log
ftpstats -a -r -l 2 -d -h -f /home/user/logs/ftp.xferlog.1
2>/dev/null >/var/log/proftpd/xferreport || true
touch /tmp/testfile
endscript
}
/var/log/proftpd/auth_log {
daily
missingok
rotate 7
delaycompress
notifempty
nocreate
sharedscripts
prerotate
endscript
postrotate
# reload could be not sufficient for all logs, a restart is safer
invoke-rc.d proftpd restart 2>/dev/null >/dev/null # || true
#service proftpd restart 2>/dev/null >/dev/null || true
endscript
}


-- debconf information:
* shared/proftpd/inetd_or_standalone: standalone
Message from syslogd@web at Sep 26 14:46:30 ...
 * glibc detected *** proftpd: ftp - 1.2.3.4: anonymous/anon@localhost: MLSD: 
munmap_chunk(): invalid pointer: 0x0168d110 ***

Message from syslogd@web at Sep 26 14:46:30 ...
 = Backtrace: =

Message from syslogd@web at Sep 26 14:46:30 ...
 ib/x86_64-linux-gnu/libc.so.6(+0x75be6)[0x7f948f660be6]

Message from syslogd@web at Sep 26 14:46:30 ...
 

Bug#844034: Any intend to fix this soon

[Andreas Tille]

Hi Afif,

On Sat, Dec 24, 2016 at 07:24:22AM -0800, Afif Elghraoui wrote:
> 
> I have actually been working on this over the past few days. I keep
> works-in-progress out of the master branch, so my work is in the branch
> topic/blasr-5 [1] and I've been posting updates to the upstream bug
> tracker to avoid duplication of efforts between here and upstream. I
> hoped anyone taking a look here would first check the upstream bug
> tracker. I'm really sad to see the duplication of effort when I was so
> particular to make sure my work was pushed :(. Is there a way we can
> avoid this in the future?

Its no real problem.  I think it will not happen to frequently since the
situation to save package for upcoming releases is only every second
year - perhaps posting the fact you are working in a separate branch
would help in such cases.  Feel free to replace everything I did by your
probably more advanced changes since you know the internals way better.
I also do not consider my time terribly wasted since I know have some
insight into these packages.

> The reason I made a blasr upload yesterday was because I was advised
> that it might fix a problem that was affecting pbhoney (after correcting
> the command-line flags). I was going to continue testing today, now that
> the upload has been installed in the archive, and report back to the
> blasr upstream.

That's fine. 

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#759936: marked as done (proftpd-mod-vroot: Module is broken because of erroneous function vroot_lookup_path)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 19:34:19 +
with message-id 
and subject line Bug#759936: fixed in proftpd-mod-vroot 0.9.4-1
has caused the Debian Bug report #759936,
regarding proftpd-mod-vroot: Module is broken because of erroneous function 
vroot_lookup_path
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.)


-- 
759936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-mod-vroot
Version: 0.9.2-2+b2
Severity: grave
 
The proftpd module mod_vroot is broken, because the alias string
processing is erroneous. The result of the function vroot_lookup_path
may look like this without the attached patch:
static int vroot_lstat(pr_fs_t *fs, const char *orig_path, struct stat
*st) {
...
  if (vroot_lookup_path(NULL, vpath, sizeof(vpath)-1, path, 0, NULL) < 0) {
destroy_pool(tmp_pool);
return -1;
  }
(void) pr_log_writefile(vroot_logfd, MOD_VROOT_VERSION, "(lstat) ==>
path '%s'", path);
(void) pr_log_writefile(vroot_logfd, MOD_VROOT_VERSION, "(lstat) ==>
vpath '%s'", vpath);
  if ((vroot_opts & VROOT_OPT_ALLOW_SYMLINKS) ||
  vroot_is_alias(path) == 0) {
...
)
Aug 22 21:06:18 mod_vroot/0.9.2[8919]: (lstat) ==> path '/folder1/test.sh'
Aug 22 21:06:18 mod_vroot/0.9.2[8919]: (lstat) ==> vpath
'/media/b464f0f6-0ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/ebc-426f-b5cf-4f4324ccf906/folder1/eb
Using the following patch makes the module working. The code changes has
been taken from the original GIT
repositoryhttps://github.com/Castaglia/proftpd-mod_vroot
.
--- proftpd-mod-vroot-0.9.2.orig/mod_vroot.c
+++ proftpd-mod-vroot-0.9.2/mod_vroot.c
@@ -225,7 +225,7 @@ loop:
 
   } else if (*bufp != '\0') {
 size_t buflen, tmplen;
-char *ptr;
+char *ptr = NULL;
 
 ptr = strstr(bufp, "..");
 if (ptr != NULL) {
@@ -280,9 +280,14 @@ loop:
 if (vroot_aliastab != NULL) {
   char *start_ptr = NULL, *end_ptr = NULL, *src_path = NULL;
 
+  /* buf is used here for storing the "suffix", to be appended
later when
+   * aliases are found.
+   */
+  bufp = buf;
+
   start_ptr = path;
   while (start_ptr != NULL) {
-char *ptr;
+char *ptr = NULL;
 
 pr_signals_handle();
 
@@ -312,8 +317,8 @@ loop:
   sstrncpy(path, src_path, pathlen);
 
   if (end_ptr != NULL) {
-sstrcat(path, "/", pathlen);
-sstrcat(path, end_ptr + 1, pathlen);
+/* Now tack on our suffix from the scratchpad. */
+sstrcat(path, bufp, pathlen);
   }
 
   break;
@@ -334,6 +339,8 @@ loop:
   break;
 }
 
+/* Store the suffix in the buf scratchpad. */
+sstrncpy(buf, ptr, sizeof(buf));
 end_ptr = ptr;
 *end_ptr = '\0';
   }

Regards
Volker
--- End Message ---
--- Begin Message ---
Source: proftpd-mod-vroot
Source-Version: 0.9.4-1

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-mod-vroot package)

(This message was generated automatically at their request; if you
believe that there is a problem 

Bug#849216: Packages which FTBFS with AssertionError about len(context)

[Chris Lamb]

Hi Santiago,

> Packages which FTBFS with AssertionError about len(context)

Haven't tested this but python-docutils 0.13.1+dfsg-1 migrated to
testing just a few days ago so that seems the most likely culprit:

  https://tracker.debian.org/news/826060


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#849293: [Pkg-libvirt-maintainers] Bug#849293: virt-manager is uninstallable: virtinst binary package went missing

[Guido Günther]

Hi Simon,
On Sat, Dec 24, 2016 at 06:25:26PM +, Simon McVittie wrote:
> Package: virt-manager
> Version: 1:1.4.0-4
> Severity: grave
> Justification: renders package unusable
> 
> virt-manager Depends on virtinst. Both are produced by src:virt-manager
> and are Architecture: all, but the 1:1.4.0-4 upload somehow includes
> virt-manager_*_all.deb but not virtinst_*_all.deb.
>  says:
> 
> > Files: 
> >  120ff4558a7c16d7ce34e819c4443658 2167 admin optional 
> > virt-manager_1.4.0-4.dsc
> >  6845af224bda02baf0224d337d019f18 15208 admin optional 
> > virt-manager_1.4.0-4.debian.tar.xz
> >  245d8408f4a1242ab2d26b8fed725467 913498 admin optional 
> > virt-manager_1.4.0-4_all.deb
> 
> I don't know how this happened, but when I rebuilt it in a clean sid chroot
> with sbuild, I correctly got both binary packages produced.

mergechanges -i virt-manager_1.4.0-4_amd64.changes 
virt-manager_1.4.0-4_amd64.changes > virt-manager_1.4.0-4_source+all.changes

is buggy in 2.16.10 and reliably drops virtinstall - if the cowbuilder
build would have missed the package already the autopkgtests would have
failed. devscripts  2.16.13 looks fixed.

> I would suggest making source-only uploads so that the Architecture: all
> buildd will do the build in a predictable environment (this worked in my
> sbuild when I tried it, so hopefully it will work equally well on buildds).

Not uploading binary packages was the whole point of the above (althogh
did not yet switch to -S instead of -i for unstable which I've done
now).

Cheers and sorry for the inconvenience,
 -- Guido

> 
> Regards,
> S
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
> (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> -- no debconf information
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
> 

Bug#847135: marked as done (openconnect: vpn connection mtu too big)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 19:20:32 +
with message-id 
and subject line Bug#847135: fixed in openconnect 7.08-1
has caused the Debian Bug report #847135,
regarding openconnect: vpn connection mtu too big
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.)


-- 
847135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openconnect
Version: 7.07-1
Severity: important

Dear Maintainer,

* What led up to the situation?
Connecting to the VPN
Any connection sending large amounds of data fails
http downloads of any non trivial file, opening a remote desktop connection

* What exactly did you do (or not do) that was effective (or ineffective)?
connections fail when sending large data as the packet size is too bug

* What was the outcome of this action?
Connections seem to hand or fail

* What outcome did you expect instead?
Successful data transfer

Please see this for discussion of the problem:
https://bbs.archlinux.org/viewtopic.php?id=200183

Adding the script as proposed at the top of the thread works well as does just
setting the MTU to a lower value after connecting

ip link set vpn0 mtu 1186

please could we fix this, it took a little tracking down and I imagine others
might find this harder to find.

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



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

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

Versions of packages openconnect depends on:
ii  libc62.24-5
ii  libgnutls30  3.5.6-7
ii  libopenconnect5  7.07-1
ii  libproxy1v5  0.4.13-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  vpnc-scripts 0.1~git20150318-1

openconnect recommends no packages.

openconnect suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openconnect
Source-Version: 7.08-1

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

Debian distribution maintenance software
pp.
Mike Miller  (supplier of updated openconnect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 10:50:15 -0800
Source: openconnect
Binary: openconnect openconnect-dbg libopenconnect-dev libopenconnect5 
libopenconnect5-dbg
Architecture: source
Version: 7.08-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Mike Miller 
Description:
 libopenconnect-dev - open client for Cisco AnyConnect VPN - development files
 libopenconnect5 - open client for Cisco AnyConnect VPN - shared library
 libopenconnect5-dbg - debugging symbols for the libopenconnect5 shared library
 openconnect - open client for Cisco AnyConnect VPN
 openconnect-dbg - debugging symbols for the OpenConnect VPN client
Closes: 847135
Changes:
 openconnect (7.08-1) unstable; urgency=medium
 .
   * New upstream version 7.08
 - Fix MTU detection (Closes: #847135)
   * d/libopenconnect5.{shlibs,symbols}: Update for new release
   * d/p/juniper-content-length.patch: Drop, applied upstream
   * d/p/fix-tests-shell-syntax.patch: Fix test suite shell bashisms
   * d/p/softhsm2-module-workaround.patch: Hard-code Debian location of
 libsofthsm2.so
   * d/control:
 - Add Build-Depends: libsocket-wrapper, libuid-wrapper, ocserv, openssl, 
and
   softhsm2 for test suite
 - Add Build-Depends: libpcsclite-dev to enable Yubikey support
   (LP: #1649227)
 - Add Build-Depends: dpkg-dev (>= 1.17.14) for build profiles support
 - Drop obsolete Build-Depends: liboath-dev
 - Reorder fields according to "cme fix dpkg-control"
   * Bump debhelper compatibility level to 10
   * Drop explicit dependency on dh-autoreconf and disabling silent rules, now
 

Bug#849277: A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading

[Barak A. Pearlmutter]

Thanks for the report.
Just pushed a fix.
(This issue was not upstream, just in the debian packaging goo.)

Bug#847135: marked as pending

[Mike Miller]

tag 847135 pending
thanks

Hello,

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

http://git.debian.org/?p=collab-maint/openconnect.git;a=commitdiff;h=85a5d81

---
commit 85a5d81b70e96ec3a5adc868650145f36da54882
Author: Mike Miller 
Date:   Sat Dec 24 10:58:11 2016 -0800

Changelog entry for 7.08-1

Signed-off-by: Mike Miller 

diff --git a/debian/changelog b/debian/changelog
index 0a33e16..b9015e8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,26 @@
+openconnect (7.08-1) unstable; urgency=medium
+
+  * New upstream version 7.08
+- Fix MTU detection (Closes: #847135)
+  * d/libopenconnect5.{shlibs,symbols}: Update for new release
+  * d/p/juniper-content-length.patch: Drop, applied upstream
+  * d/p/fix-tests-shell-syntax.patch: Fix test suite shell bashisms
+  * d/p/softhsm2-module-workaround.patch: Hard-code Debian location of
+libsofthsm2.so
+  * d/control:
+- Add Build-Depends: libsocket-wrapper, libuid-wrapper, ocserv, openssl, 
and
+  softhsm2 for test suite
+- Add Build-Depends: libpcsclite-dev to enable Yubikey support
+  (LP: #1649227)
+- Add Build-Depends: dpkg-dev (>= 1.17.14) for build profiles support
+- Drop obsolete Build-Depends: liboath-dev
+- Reorder fields according to "cme fix dpkg-control"
+  * Bump debhelper compatibility level to 10
+  * Drop explicit dependency on dh-autoreconf and disabling silent rules, now
+enabled by default
+
+ -- Mike Miller   Sat, 24 Dec 2016 10:50:15 -0800
+
 openconnect (7.07-2) unstable; urgency=medium
 
   * d/rules: Build with --as-needed to remove indirect lib dependencies

Bug#817638: pyode: diff for NMU version 1.2.0-4+cvs20090320.2

[Christoph Biedl]

Christoph Biedl wrote...

> Find below the debdiff for a NMU I've prepared for pyode (versioned as
> 1.2.0-4+cvs20090320.2)

Upon review I realized the correct version number for an NMU should have
been 1.2.0-4+cvs20090320.1.1 instead. Indulge me.

Christoph



signature.asc
Description: Digital signature

Processed: Bug#847135 marked as pending

[Debian Bug Tracking System]

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

> tag 847135 pending
Bug #847135 [openconnect] openconnect: vpn connection mtu too big
Ignoring request to alter tags of bug #847135 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#845623: marked as done (golang-github-aelsabbahy-gonetstat-dev depends on nonexisting package golang-github-drael-gonetstat-dev)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 18:48:27 +
with message-id 
and subject line Bug#845623: fixed in golang-github-aelsabbahy-gonetstat 
0.0~git20160428.0.edf89f7-2
has caused the Debian Bug report #845623,
regarding golang-github-aelsabbahy-gonetstat-dev depends on nonexisting package 
golang-github-drael-gonetstat-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.)


-- 
845623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-aelsabbahy-gonetstat-dev
Version: 0.0~git20160428.0.edf89f7-1
Severity: serious

The following packages have unmet dependencies:
 golang-github-aelsabbahy-gonetstat-dev : Depends: 
golang-github-drael-gonetstat-dev but it is not installable
--- End Message ---
--- Begin Message ---
Source: golang-github-aelsabbahy-gonetstat
Source-Version: 0.0~git20160428.0.edf89f7-2

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated 
golang-github-aelsabbahy-gonetstat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 13:08:32 -0500
Source: golang-github-aelsabbahy-gonetstat
Binary: golang-github-aelsabbahy-gonetstat-dev
Architecture: source all
Version: 0.0~git20160428.0.edf89f7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Andrew Starr-Bochicchio 
Description:
 golang-github-aelsabbahy-gonetstat-dev - Netstat implementation in Go
Closes: 845623
Changes:
 golang-github-aelsabbahy-gonetstat (0.0~git20160428.0.edf89f7-2) unstable; 
urgency=medium
 .
   * Rebuild to remove errant depends on golang-github-drael-gonetstat-dev
 (Closes: #845623).
   * Bump Standards-Version to 3.9.8, no changes.
   * Bump compat to 10.
Checksums-Sha1:
 a57dbba82feea6098dad86873a44381c97c6cf89 2442 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2.dsc
 aa1d834aecc66126f7dfa0da7bcea42cba76e504 1936 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2.debian.tar.xz
 37c6379962eb65b6d2b379c32ab9a6fd9b248422 5002 
golang-github-aelsabbahy-gonetstat-dev_0.0~git20160428.0.edf89f7-2_all.deb
 e351bf34ea6db9e55a1c71ecdbd152f86a84dc5b 7130 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2_amd64.buildinfo
Checksums-Sha256:
 2645574499e364f8a78d171f35498e096e7d47ef788475c877d4364ea6645f2f 2442 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2.dsc
 55affb4119c6930119a638a5aa89de29eed4b80b9cf7103b4e07b6bcf944117b 1936 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2.debian.tar.xz
 5c11a13f0f04a502ef4eacf9631a42336a85eca42b47bd7c6a0c5cc881b40471 5002 
golang-github-aelsabbahy-gonetstat-dev_0.0~git20160428.0.edf89f7-2_all.deb
 b2c443a3d65bef409d92e8cc19d07611f8796e0808be9be3f35696f64e0f98db 7130 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2_amd64.buildinfo
Files:
 37f2cd22aecd0ca9ddcc9a846d9f72e8 2442 devel extra 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2.dsc
 79e1261f04cf73ab4fb604c37849f57e 1936 devel extra 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2.debian.tar.xz
 453f0d9412024922998f3877b3f3e377 5002 devel extra 
golang-github-aelsabbahy-gonetstat-dev_0.0~git20160428.0.edf89f7-2_all.deb
 e06e2766549e27256e71bfcb67594014 7130 devel extra 
golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYXrzBAAoJEDtW4rvVP9yx7ckQAMSjM4ufUsiGWJekC6qyyZ/0
AueGDpB6qZNGdANAzsE5t9xlNtLuT2KHX1tLkFWXZgoigR8IeCvua6fgYgextPXy
apngn/bhw5Mplup8t0dOh8SxSM8Y+m66OWyuSB8Jr4C+zGnkK3Gz7UMo88nNLBFk
6PEjE81UPB4N/TWY9ERUshnLEKVmJvF773eWHASti6LPGS+fuqWsmhGphyQSCZBf
hsty4WdLmkXAvq25P+DSdYBqSDoBYGO1S4zPmVPeP9fBSFMhjXc3VygumWPW2rNa
n0AyEIf5ox/6EcutU39nd19BRN7SJ38ILIP0hm1YaPBW2rtN7p4bwLY2dhDO/CVR

Processed: package unusable in its current state

[Debian Bug Tracking System]

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

> severity 847655 grave
Bug #847655 [fritzing] fritzing does not find core.fzb
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#849063: src:haskell-mode: maintainer address bounces

[Barak A. Pearlmutter]

> Barak, can you do the necessary upload? You seem to be most involved
> with the package these days, so feel free to "promote" yourself to
> maintainer.

Will do.

> http://pkg-emacsen.alioth.debian.org/

https://.  And even better: I'll do that!

Two other minor matters.

(a) For this or any of my other packages, please feel free to just
push a change to collab-maint git or whatever, or even to do an NMU,
for stuff like this. I really don't mind!

(b) Um, Ansgar, the "Severity: Important" for an issue like this seems
overly strident to me. I'd classify this as "minor" or at worst
"normal", since it has zero actual effect on the package's
functionality to users.

Processed: Pending fixes for bugs in the golang-github-aelsabbahy-gonetstat package

[Debian Bug Tracking System]

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

> tag 845623 + pending
Bug #845623 [golang-github-aelsabbahy-gonetstat-dev] 
golang-github-aelsabbahy-gonetstat-dev depends on nonexisting package 
golang-github-drael-gonetstat-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#849293: virt-manager is uninstallable: virtinst binary package went missing

[Simon McVittie]

Package: virt-manager
Version: 1:1.4.0-4
Severity: grave
Justification: renders package unusable

virt-manager Depends on virtinst. Both are produced by src:virt-manager
and are Architecture: all, but the 1:1.4.0-4 upload somehow includes
virt-manager_*_all.deb but not virtinst_*_all.deb.
 says:

> Files: 
>  120ff4558a7c16d7ce34e819c4443658 2167 admin optional virt-manager_1.4.0-4.dsc
>  6845af224bda02baf0224d337d019f18 15208 admin optional 
> virt-manager_1.4.0-4.debian.tar.xz
>  245d8408f4a1242ab2d26b8fed725467 913498 admin optional 
> virt-manager_1.4.0-4_all.deb

I don't know how this happened, but when I rebuilt it in a clean sid chroot
with sbuild, I correctly got both binary packages produced.

I would suggest making source-only uploads so that the Architecture: all
buildd will do the build in a predictable environment (this worked in my
sbuild when I tried it, so hopefully it will work equally well on buildds).

Regards,
S

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

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

-- no debconf information

Bug#845623: Pending fixes for bugs in the golang-github-aelsabbahy-gonetstat package

[pkg-go-maintainers]

tag 845623 + pending
thanks

Some bugs in the golang-github-aelsabbahy-gonetstat package are
closed in revision ff4abffd16a1fd4f1dfa08af0157468d0e7758d7 in branch
'master' by Andrew Starr-Bochicchio

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-aelsabbahy-gonetstat.git/commit/?id=ff4abff

Commit message:

Rebuild to remove errant depends on golang-github-drael-gonetstat-dev 
(Closes: #845623).

Processed: Re: Bug#849142: test regression in test_dex.test_differences with enjarify >= 1.0.3

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #849142 [diffoscope] test regression in test_dex.test_differences with 
enjarify >= 1.0.3
Severity set to 'serious' from 'normal'
> found -1 65
Bug #849142 [diffoscope] test regression in test_dex.test_differences with 
enjarify >= 1.0.3
There is no source info for the package 'diffoscope' at version '65' with 
architecture ''
Unable to make a source version for version '65'
Marked as found in versions 65.

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

Bug#814656: marked as done (manpages-posix-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 17:20:22 +
with message-id 
and subject line Bug#814656: fixed in manpages-posix 2013a-2
has caused the Debian Bug report #814656,
regarding manpages-posix-dev: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
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.)


-- 
814656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-posix-dev
Version: 2013a-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  jessie -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

2m18.5s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/manpages-posix-dev/changelog.Debian.gz (manpages-posix-dev) != 
/usr/share/doc/manpages-posix/changelog.Debian.gz (manpages-posix)
/usr/share/doc/manpages-posix-dev -> manpages-posix
  /usr/share/doc/manpages-posix-dev/copyright (manpages-posix-dev) != 
/usr/share/doc/manpages-posix/copyright (manpages-posix)
/usr/share/doc/manpages-posix-dev -> manpages-posix


cheers,

Andreas


manpages-posix-dev_2013a-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: manpages-posix
Source-Version: 2013a-2

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
manpages-posix 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: SHA1

Format: 1.8
Date: Sat, 24 Dec 2016 17:41:56 +0100
Source: manpages-posix
Binary: manpages-posix manpages-posix-dev
Architecture: source all
Version: 2013a-2
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 manpages-posix - Manual pages about using POSIX system
 manpages-posix-dev - Manual pages about using a POSIX system for development
Closes: 814656
Changes:
 manpages-posix (2013a-2) unstable; urgency=medium
 .
   * Now /usr/share/doc/manpages-posix-dev is not more a link to 
/usr/share/doc/manpages-posix.
 So a pre-depends has been introduced to use the dpkg-maintscript-helper
 and convert from previous situation to the current one.
 (Closes: #814656)
Checksums-Sha1:
 be60040e5e290a6682a2a5b674b60515b38fffd3 1870 manpages-posix_2013a-2.dsc
 d850422162d0cffaef064affb65cc06d640cc965 3876 
manpages-posix_2013a-2.debian.tar.xz
 

Bug#849285: kodi-pvr-mythtv: FTBFS: src/client.cpp:1202:6: error: conflicting declaration of C function 'bool SeekTime(int, bool, double*)'

[Chris Lamb]

Source: kodi-pvr-mythtv
Version: 4.7.2+git20160820-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

kodi-pvr-mythtv fails to build from source in unstable/amd64:

  […]

  dh build
 dh_testdir
 dh_update_autotools_config
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '«BUILDDIR»'
  # USE_LTO breaks build
  dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 
-DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu/kodi
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_BUILD_TYPE=Release 
-DBUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu/kodi
  -- The C compiler identification is GNU 6.2.1
  -- The CXX compiler identification is GNU 6.2.1
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Checking to see if CXX compiler accepts flag -flto
  -- Checking to see if CXX compiler accepts flag -flto - yes
  -- Looking for __atomic_fetch_add_4 in atomic
  -- Looking for __atomic_fetch_add_4 in atomic - found
  -- Performing Test HAS_BUILTIN_SYNC_ADD_AND_FETCH
  -- Performing Test HAS_BUILTIN_SYNC_ADD_AND_FETCH - Success
  -- Performing Test HAS_BUILTIN_SYNC_SUB_AND_FETCH
  -- Performing Test HAS_BUILTIN_SYNC_SUB_AND_FETCH - Success
  -- Performing Test HAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP
  -- Performing Test HAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP - Success
  -- Looking for pthread.h
  -- Looking for pthread.h - found
  -- Looking for pthread_create
  -- Looking for pthread_create - not found
  -- Looking for pthread_create in pthreads
  -- Looking for pthread_create in pthreads - not found
  -- Looking for pthread_create in pthread
  -- Looking for pthread_create in pthread - found
  -- Found Threads: TRUE  
  -- Looking for timegm
  -- Looking for timegm - found
  -- Looking for localtime_r
  -- Looking for localtime_r - found
  -- Looking for gmtime_r
  -- Looking for gmtime_r - found
  -- Performing Test HAVE_INLINE
  -- Performing Test HAVE_INLINE - Success
  -- Performing Test HAVE___INLINE
  -- Performing Test HAVE___INLINE - Success
  -- Performing Test HAVE___INLINE__
  -- Performing Test HAVE___INLINE__ - Success
  -- Performing Test COMPILER_SUPPORTS_CXX11
  -- Performing Test COMPILER_SUPPORTS_CXX11 - Success
  -- MYTHTV_VERSION=4.7.2
  -- Configuring done
  -- Generating done
  CMake Warning:
Manually-specified variables were not used by the project:
  
  CMAKE_INSTALL_LOCALSTATEDIR
  CMAKE_INSTALL_SYSCONFDIR
  
  
  -- Build files have been written to: «BUILDDIR»/obj-x86_64-linux-gnu
  make[1]: Leaving directory '«BUILDDIR»'
 dh_auto_build
make -j1
  make[1]: Entering directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  /usr/bin/cmake -H«BUILDDIR» 
-B/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu
 --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake -E cmake_progress_start 
«BUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
  make -f CMakeFiles/Makefile2 all
  make[2]: Entering directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  make -f lib/cppmyth/CMakeFiles/cppmyth.dir/build.make 
lib/cppmyth/CMakeFiles/cppmyth.dir/depend
  make[3]: Entering directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  cd «BUILDDIR»/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix 
Makefiles" 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820
 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/lib/cppmyth
 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu/lib/cppmyth
 
/home/lamby/temp/cdt.20161224170851.r1weVQvyF1.db.kodi-pvr-mythtv/kodi-pvr-mythtv-4.7.2+git20160820/obj-x86_64-linux-gnu/lib/cppmyth/CMakeFiles/cppmyth.dir/DependInfo.cmake
 --color=
  Scanning dependencies of target cppmyth
  make[3]: Leaving directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  make -f 

Bug#849286: leap-cli: FTBFS: Could not find 'capistrano' (~> 2.15) - did find: [capistrano-3.4.0] (Gem::LoadError)

[Chris Lamb]

Source: leap-cli
Version: 1.9-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

leap-cli fails to build from source in unstable/amd64:

  […]

  Unpacking openssl (1.1.0c-2) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../01-ca-certificates_20161130_all.deb ...
  Unpacking ca-certificates (20161130) ...
  Selecting previously unselected package rubygems-integration.
  Preparing to unpack .../02-rubygems-integration_1.11_all.deb ...
  Unpacking rubygems-integration (1.11) ...
  Selecting previously unselected package ruby-did-you-mean.
  Preparing to unpack .../03-ruby-did-you-mean_1.0.0-2_all.deb ...
  Unpacking ruby-did-you-mean (1.0.0-2) ...
  Selecting previously unselected package ruby-minitest.
  Preparing to unpack .../04-ruby-minitest_5.9.0-1_all.deb ...
  Unpacking ruby-minitest (5.9.0-1) ...
  Selecting previously unselected package ruby-net-telnet.
  Preparing to unpack .../05-ruby-net-telnet_0.1.1-2_all.deb ...
  Unpacking ruby-net-telnet (0.1.1-2) ...
  Selecting previously unselected package ruby-power-assert.
  Preparing to unpack .../06-ruby-power-assert_0.3.0-1_all.deb ...
  Unpacking ruby-power-assert (0.3.0-1) ...
  Selecting previously unselected package ruby-test-unit.
  Preparing to unpack .../07-ruby-test-unit_3.1.7-2_all.deb ...
  Unpacking ruby-test-unit (3.1.7-2) ...
  Selecting previously unselected package libssl1.0.2:amd64.
  Preparing to unpack .../08-libssl1.0.2_1.0.2j-4_amd64.deb ...
  Unpacking libssl1.0.2:amd64 (1.0.2j-4) ...
  Selecting previously unselected package libyaml-0-2:amd64.
  Preparing to unpack .../09-libyaml-0-2_0.1.7-2_amd64.deb ...
  Unpacking libyaml-0-2:amd64 (0.1.7-2) ...
  Selecting previously unselected package libruby2.3:amd64.
  Preparing to unpack .../10-libruby2.3_2.3.3-1_amd64.deb ...
  Unpacking libruby2.3:amd64 (2.3.3-1) ...
  Selecting previously unselected package ruby2.3.
  Preparing to unpack .../11-ruby2.3_2.3.3-1_amd64.deb ...
  Unpacking ruby2.3 (2.3.3-1) ...
  Selecting previously unselected package ruby.
  Preparing to unpack .../12-ruby_1%3a2.3.3_amd64.deb ...
  Unpacking ruby (1:2.3.3) ...
  Selecting previously unselected package rake.
  Preparing to unpack .../13-rake_10.5.0-2_all.deb ...
  Unpacking rake (10.5.0-2) ...
  Selecting previously unselected package ruby-i18n.
  Preparing to unpack .../14-ruby-i18n_0.7.0-2_all.deb ...
  Unpacking ruby-i18n (0.7.0-2) ...
  Selecting previously unselected package ruby-colorize.
  Preparing to unpack .../15-ruby-colorize_0.8.1-1_all.deb ...
  Unpacking ruby-colorize (0.8.1-1) ...
  Selecting previously unselected package ruby-net-ssh.
  Preparing to unpack .../16-ruby-net-ssh_1%3a3.2.0-1_all.deb ...
  Unpacking ruby-net-ssh (1:3.2.0-1) ...
  Selecting previously unselected package ruby-net-scp.
  Preparing to unpack .../17-ruby-net-scp_1.2.1-4_all.deb ...
  Unpacking ruby-net-scp (1.2.1-4) ...
  Selecting previously unselected package ruby-sshkit.
  Preparing to unpack .../18-ruby-sshkit_1.9.0-1_all.deb ...
  Unpacking ruby-sshkit (1.9.0-1) ...
  Selecting previously unselected package capistrano.
  Preparing to unpack .../19-capistrano_3.4.0-1_all.deb ...
  Unpacking capistrano (3.4.0-1) ...
  Selecting previously unselected package gem2deb-test-runner.
  Preparing to unpack .../20-gem2deb-test-runner_0.33.1_amd64.deb ...
  Unpacking gem2deb-test-runner (0.33.1) ...
  Selecting previously unselected package libgmpxx4ldbl:amd64.
  Preparing to unpack .../21-libgmpxx4ldbl_2%3a6.1.2+dfsg-1_amd64.deb ...
  Unpacking libgmpxx4ldbl:amd64 (2:6.1.2+dfsg-1) ...
  Selecting previously unselected package libgmp-dev:amd64.
  Preparing to unpack .../22-libgmp-dev_2%3a6.1.2+dfsg-1_amd64.deb ...
  Unpacking libgmp-dev:amd64 (2:6.1.2+dfsg-1) ...
  Selecting previously unselected package ruby2.3-dev:amd64.
  Preparing to unpack .../23-ruby2.3-dev_2.3.3-1_amd64.deb ...
  Unpacking ruby2.3-dev:amd64 (2.3.3-1) ...
  Selecting previously unselected package ruby-all-dev:amd64.
  Preparing to unpack .../24-ruby-all-dev_1%3a2.3.3_amd64.deb ...
  Unpacking ruby-all-dev:amd64 (1:2.3.3) ...
  Selecting previously unselected package ruby-setup.
  Preparing to unpack .../25-ruby-setup_3.4.1-9_all.deb ...
  Unpacking ruby-setup (3.4.1-9) ...
  Selecting previously unselected package gem2deb.
  Preparing to unpack .../26-gem2deb_0.33.1_amd64.deb ...
  Unpacking gem2deb (0.33.1) ...
  Selecting previously unselected package ruby-gli.
  Preparing to unpack .../27-ruby-gli_2.14.0-1_all.deb ...
  Unpacking ruby-gli (2.14.0-1) ...
  Selecting previously unselected package ruby-json.
  Preparing to unpack .../28-ruby-json_2.0.1+dfsg-3_amd64.deb ...
  Unpacking ruby-json (2.0.1+dfsg-3) ...
  Selecting previously unselected package ruby-ya2yaml.
  Preparing to unpack .../29-ruby-ya2yaml_0.31-1_all.deb ...
  Unpacking ruby-ya2yaml 

Bug#849281: marked as done (node-domutils: Missing Build-Depends: node-htmlparser2 )

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 16:48:27 +
with message-id 
and subject line Bug#849281: fixed in node-domutils 1.5.1-2
has caused the Debian Bug report #849281,
regarding node-domutils: Missing Build-Depends: node-htmlparser2 
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.)


-- 
849281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-domutils
Version: 1.5.1-1
Severity: serious

node-domutils fails to build from source in a clean sid chroot. Since
Ubuntu fails at the same spot, you can see the full build log at
https://launchpad.net/ubuntu/+source/node-domutils/1.5.1-1
Click amd64

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha test/tests/**.js -R spec
module.js:327
throw err;
^

Error: Cannot find module 'htmlparser2'

Since the dependency appears to only be needed by dh_auto_test, add
this to Build-Depends:

 , node-htmlparser2 

(although https://bugs.debian.org/568897 means that nocheck doesn't
work with override_dh_auto_test currently)

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: node-domutils
Source-Version: 1.5.1-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 21:48:44 +0530
Source: node-domutils
Binary: node-domutils
Architecture: source
Version: 1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-domutils - utilities for working with htmlparser2's DOM
Closes: 849281
Changes:
 node-domutils (1.5.1-2) unstable; urgency=medium
 .
   * Team upload
   * Add node-htmlparser2 to build deps (Closes: #849281)
Checksums-Sha1:
 5fc1bb268f992bcb140c17e3b36d0a85f1454d61 2128 node-domutils_1.5.1-2.dsc
 ede24271266ccf1e1ca981bf067b192527b619ec 2724 
node-domutils_1.5.1-2.debian.tar.xz
Checksums-Sha256:
 4b96486d75e28e3bf4489172498660dfb7ea8542eed4d659032b3bb74c1928b4 2128 
node-domutils_1.5.1-2.dsc
 aa399bf0b7baaaf044ba50dc2c228d78d468a2272e4bb391a5cdd7b7a88e7d38 2724 
node-domutils_1.5.1-2.debian.tar.xz
Files:
 ec76e8b36b22d3023e68db7ffd4516e8 2128 web optional node-domutils_1.5.1-2.dsc
 e27e5474d93cdbde658db4d51c4ddebd 2724 web optional 
node-domutils_1.5.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlheoaAACgkQzh+cZ0US
wipcTBAAl3zhZ1kt+CqCoUaDkfvxkDvRaQ66hk7ZIeKrJ1SW6NJX0lzxCATmenEh
SqQ5ZAojveD5B8DXCLHlhSQZtjIRWzyLwgGfCu5ggL8nyaSxVinWCM3ymPAMxA4O
SSYPll/cH4nOoDed1DopdXf6pDbnUemvqRqFE14zFWTUvnEwA5iDkNKfI+1i3lUt
YOMesmOJTV57PPnS70a88O2HqcImB6bl6lj4rKWXIO3YjSN7oUU/hOu47ha4is3E
NRM3bVRuALQhm7NRs08yQAEZkTtZpXdbBHLslJPFR/Z+46fSeDLjljDq1Qlm6fWS
1tjSWtQtUeMzZvxdY69k2b3PwwF2+f8F7Zb7zLRJuW1Jdrwpg3peTEU6UUWO+fQ4
LKyvRA3QHtFCOfbKnSm0lspUdyCsu0unQYRdLTGMtWHqMfxNGnopvaWZ6Ru6MOCz
rqcXkIpE08ozvPiqL/dNILmbDn8esRza4JprQRyTIwrRfhXrhkKEkr673b3t22ss
lhxxiDfQenjpCJpos3CakEkzJ4gkUt0XxZkvZhX3wvqS+w16Vh8X9Q1QWSZsB01y
WSHQ5REyvMvN4nn6gsswIsqc3nKIcBJ6ZK1sjye2wRXcMBXJLBSgc72zBHIA3AiN
/+Ku4JgYm5sFHlnSkaWeOwzo71E52gVPJ0s/JFGQib0HLnzeIGQ=
=/TDN
-END PGP SIGNATURE End Message ---

Bug#849219: marked as done (metview: FTBFS in testing (cannot find -lgrib_api))

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 15:44:58 +
with message-id <011a12d0-f0d3-ac81-1b54-c9072371b...@sceal.ie>
and subject line Re: Bug#849219: metview: FTBFS in testing (cannot find 
-lgrib_api)
has caused the Debian Bug report #849219,
regarding metview: FTBFS in testing (cannot find -lgrib_api)
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.)


-- 
849219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:metview
Version: 4.8.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/debian/build
   dh_testdir -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   dh_autoreconf -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
chmod +x ./scripts/*.mv
# Hack. how to do this via ecbuild?
cp scripts/metview_base.in scripts/metview_base.in.bak
sed -e 's%@DEB_HOST_MULTIARCH@%x86_64-linux-gnu%g' < scripts/metview_base.in \
> scripts/tmpx && mv scripts/tmpx scripts/metview_base.in
dh_auto_configure -- \

[... snipped ...]

[ 78%] Building CXX object 
src/uPlot/CMakeFiles/GeoTool.dir/MvQPlaceMarkWidget.cc.o
cd /<>/debian/build/src/uPlot && /usr/bin/c++   
-DGRIB_HANDLING_PACKAGE=ecCodes -DH_INCLUDES_CC -DLITTLE_END -DMAGICS_QT5 
-DMETVIEW -DMETVIEW_QT5 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
-DQT_XMLPATTERNS_LIB -DQT_XML_LIB -DR64 -DUSE_NEW_IO 
-I/<>/debian/build/module -I/<>/src/libMvQtUtil 
-I/<>/src/libMvQtGui -I/<>/src/libMetview 
-I/<>/src/libUtil -I/<>/src/libMarsClient 
-I/<>/src/libMars -I/<>/debian/build/src/libMars 
-I/<>/src -I/<>/src/libFTimeUtil 
-I/<>/src/libMvNetCDF -I/<>/src/libMvQtGui/../uPlot 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I/usr/include/x86_64-linu
 x-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -I/usr/include/magics 
-I/usr/include/terralib -I/usr/include/terralib/kernel -I/usr/lib/include 
-I/usr/include/hdf5/serial -I/usr/include/python3.5m 
-I/usr/include/openjpeg-2.1 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/X11R6/include 
-I/usr/lib/python3/dist-packages/numpy/core/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -std=c++11 
-Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fpermissive -Wno-write-strings 
-Wno-deprecated -O3 -DNDEBUG -fPIE   -fPIC -std=gnu++11 -o 
CMakeFiles/GeoTool.dir/MvQPlaceMarkWidget.cc.o -c 
/<>/src/uPlot/MvQPlaceMarkWidget.cc
[ 78%] Building CXX object 
src/uPlot/CMakeFiles/GeoTool.dir/MvQPlaceMarkModel.cc.o
cd /<>/debian/build/src/uPlot && /usr/bin/c++   
-DGRIB_HANDLING_PACKAGE=ecCodes -DH_INCLUDES_CC -DLITTLE_END -DMAGICS_QT5 
-DMETVIEW -DMETVIEW_QT5 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
-DQT_XMLPATTERNS_LIB -DQT_XML_LIB -DR64 -DUSE_NEW_IO 
-I/<>/debian/build/module -I/<>/src/libMvQtUtil 
-I/<>/src/libMvQtGui -I/<>/src/libMetview 
-I/<>/src/libUtil -I/<>/src/libMarsClient 
-I/<>/src/libMars -I/<>/debian/build/src/libMars 
-I/<>/src -I/<>/src/libFTimeUtil 
-I/<>/src/libMvNetCDF -I/<>/src/libMvQtGui/../uPlot 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I/usr/include/x86_64-linu
 x-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -I/usr/include/magics 
-I/usr/include/terralib -I/usr/include/terralib/kernel -I/usr/lib/include 

Processed: astropy bug affects many affiliated packages

[Debian Bug Tracking System]

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

> reassign 849271 python-astropy
Bug #849271 [astropy] version comparison fails with numpy 1.12.0b1
Warning: Unknown package 'astropy'
Bug reassigned from package 'astropy' to 'python-astropy'.
No longer marked as found in versions 1.3-1.
Ignoring request to alter fixed versions of bug #849271 to the same values 
previously set
> affects 849271 aplpy astroplan astroquery astroscrappy ginga
Bug #849271 [python-astropy] version comparison fails with numpy 1.12.0b1
Added indication that 849271 affects aplpy, astroplan, astroquery, 
astroscrappy, and ginga
> affects 849271 montage-wrapper photutils pymoc pyregion
Bug #849271 [python-astropy] version comparison fails with numpy 1.12.0b1
Added indication that 849271 affects montage-wrapper, photutils, pymoc, and 
pyregion
> affects 849271 reproject spectral-cube specutils
Bug #849271 [python-astropy] version comparison fails with numpy 1.12.0b1
Added indication that 849271 affects reproject, spectral-cube, and specutils
>
End of message, stopping processing here.

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

Bug#849210: marked as done (ntopng: fails to start)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 15:34:53 +
with message-id 
and subject line Bug#849210: fixed in ntopng 2.4+dfsg1-2
has caused the Debian Bug report #849210,
regarding ntopng: fails to start
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.)


-- 
849210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntopng
Version: 2.4+dfsg1-1
Severity: important

As of version 2.4, ntopng fails to start on my system.  I'm not sure
what specifically is going wrong; all I see in ntopng.log is

23/Dec/2016 10:38:43 [Ntop.cpp:1121] Setting local networks to 127.0.0.0/8
23/Dec/2016 10:38:43 [Redis.cpp:92] Successfully connected to redis 
127.0.0.1:6379@0
23/Dec/2016 10:38:43 [Ntop.cpp:1095] Parent process is exiting (this is normal)

System logs additionally show the ndpi "INTERNAL ERROR" from
https://github.com/ntop/ntopng/issues/638, but AFAICT this error
shouldn't be fatal, and rebuilding ndpi with upstream's patch applied
made no difference.

Could you please take a look?

Thanks!

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 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 ntopng depends on:
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libcurl3-gnutls  7.50.1-1
ii  libgcc1  1:6.2.1-5
ii  libgeoip11.6.9-4
ii  libhiredis0.13   0.13.3-2
ii  libjson-c3   0.12.1-1.1
ii  libluajit-5.1-2  2.0.4+dfsg-1
ii  libmariadbclient18   10.0.28-2
ii  libndpi4 1.8-1
ii  libpcap0.8   1.8.1-3
ii  librrd8  1.6.0-1+b1
ii  libsqlite3-0 3.15.2-1
ii  libstdc++6   6.2.1-5
ii  libzmq5  4.1.5-2
ii  lsb-base 9.20161125
ii  ntopng-data  2.4+dfsg1-1
ii  redis-server 3:3.2.6-1
ii  zlib1g   1:1.2.8.dfsg-4

ntopng recommends no packages.

Versions of packages ntopng suggests:
pn  geoip-database-contrib  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ntopng
Source-Version: 2.4+dfsg1-2

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

Debian distribution maintenance software
pp.
Ludovico Cavedon  (supplier of updated ntopng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Dec 2016 16:04:10 +0100
Source: ntopng
Binary: ntopng ntopng-data
Architecture: source all amd64
Version: 2.4+dfsg1-2
Distribution: unstable
Urgency: high
Maintainer: Ludovico Cavedon 
Changed-By: Ludovico Cavedon 
Description:
 ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool
 ntopng-data - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d
Closes: 848152 849210
Changes:
 ntopng (2.4+dfsg1-2) unstable; urgency=high
 .
   * Let systemd guess the main PID of ntopng (Closes: #849210).
   * Add Multi-Arch: foreign to ntopng-data (Closes: #848152).
Checksums-Sha1:
 9dce410f7a32bb39eb144033f44c2d29865ec8a9 2208 ntopng_2.4+dfsg1-2.dsc
 80b29953bec0e9e22f782a6100201a231a3c1a78 25088 ntopng_2.4+dfsg1-2.debian.tar.xz
 548d13aad7649d39fae48565d57520c4af97e26b 1273946 
ntopng-data_2.4+dfsg1-2_all.deb
 8c00b6fadceab5303c8e4df1fecca8db66221831 2116262 
ntopng-dbgsym_2.4+dfsg1-2_amd64.deb
 2ace04da14fe3be439d470f1b817c05d2c766513 7636 
ntopng_2.4+dfsg1-2_amd64.buildinfo
 eae83b1308f98abe8529e5c4324cee5d38919347 241792 ntopng_2.4+dfsg1-2_amd64.deb
Checksums-Sha256:
 762bf0e693f3d350d80222334256450c9a262b1cdf57c6a9ce59826e7bbcbb4f 2208 
ntopng_2.4+dfsg1-2.dsc
 2f24408308f04f3d4e37bf95a498f47243c54d438716424de2b49ff87d4344c4 25088 
ntopng_2.4+dfsg1-2.debian.tar.xz
 

Bug#844034: Any intend to fix this soon

[Afif Elghraoui]

Hi, Andreas,

على السبت 24 كانون الأول 2016 ‫01:30، كتب Andreas Tille:
> Hi Afif,
> 
> pbhoney is marked for autoremoval due to this bug.  I'm guessing from
> the description of the problem that it should be easy to fix (without
> having checked).  Do you intend to upload soon or should somebody
> else step in here?
> 

I have actually been working on this over the past few days. I keep
works-in-progress out of the master branch, so my work is in the branch
topic/blasr-5 [1] and I've been posting updates to the upstream bug
tracker to avoid duplication of efforts between here and upstream. I
hoped anyone taking a look here would first check the upstream bug
tracker. I'm really sad to see the duplication of effort when I was so
particular to make sure my work was pushed :(. Is there a way we can
avoid this in the future?

The reason I made a blasr upload yesterday was because I was advised
that it might fix a problem that was affecting pbhoney (after correcting
the command-line flags). I was going to continue testing today, now that
the upload has been installed in the archive, and report back to the
blasr upstream.

Thanks and regards
Afif

1. https://anonscm.debian.org/git/debian-med/pbsuite.git/log/?h=topic/blasr5

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

Bug#849281: node-domutils: Missing Build-Depends: node-htmlparser2

[Jeremy Bicha]

Package: node-domutils
Version: 1.5.1-1
Severity: serious

node-domutils fails to build from source in a clean sid chroot. Since
Ubuntu fails at the same spot, you can see the full build log at
https://launchpad.net/ubuntu/+source/node-domutils/1.5.1-1
Click amd64

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha test/tests/**.js -R spec
module.js:327
throw err;
^

Error: Cannot find module 'htmlparser2'

Since the dependency appears to only be needed by dh_auto_test, add
this to Build-Depends:

 , node-htmlparser2 

(although https://bugs.debian.org/568897 means that nocheck doesn't
work with override_dh_auto_test currently)

Thanks,
Jeremy Bicha

Bug#849277: A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading

[積丹尼 Dan Jacobson]

X-Debbugs-Cc: wink...@gnu.org
Package: bbdb3
Version: 3.1.2-6
Severity: grave
File: /etc/emacs/site-start.d/50bbdb3.el

A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading.

--- 50bbdb3.el  2016-07-21 15:21:11.0 +0800
+++ 50bbdb3.NEW.el  2016-12-24 21:07:24.969515584 +0800
@@ -14,7 +14,7 @@
 ;; installed in a subdirectory of the respective site-lisp directory.
 ;; We have to add this to the load-path:
 (let ((package-dir (concat "/usr/share/"
-  (symbol-name flavor)
+  "emacs"
   "/site-lisp/bbdb3")))
   ;; If package-dir does not exist the bbdb3 package must have been
   ;; removed but not purged, and we should skip the setup.

Bug#848744: marked as done (python-ase: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 15:10:55 +
with message-id 
and subject line Bug#848744: fixed in python-ase 3.12.0-2
has caused the Debian Bug report #848744,
regarding python-ase: FTBFS: Test failures
to be marked as done.

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

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


-- 
848744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ase
Version: 3.12.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> Traceback (most recent call last):
>   File "/<>/.pybuild/pythonX.Y_2.7/build/ase/test/__init__.py", 
> line 53, in testfile
> {'display': self.display})
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/ase/test/franck_condon.py", 
> line 38, in 
> assert(fco.direct(n, m, S) == fco.direct(m, n, S))
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/ase/vibrations/franck_condon.py",
>  line 41, in direct
> s += (-1)**(n - k) * S**(-k) / (
> ValueError: Integers to negative integer powers are not allowed.
> 
> --
> Ran 177 tests in 84.400s
> 
> FAILED (errors=1)
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: cd 
> ase/test; python2.7 -m ase.test
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:11: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/python-ase_3.12.0-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated python-ase package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Dec 2016 16:20:40 +0200
Source: python-ase
Binary: python-ase python3-ase python-ase-doc
Architecture: source
Version: 3.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Graham Inggs 
Description:
 python-ase - Atomic Simulation Environment (Python 2)
 python-ase-doc - Atomic Simulation Environment (common documentation)
 python3-ase - Atomic Simulation Environment (Python 3)
Closes: 848744
Changes:
 python-ase (3.12.0-2) unstable; urgency=medium
 .
   * Fix FTBFS with NumPy 1.12 (Closes: #848744)
Checksums-Sha1:
 ed6a939bc7ecc2edf8c8313ee37270b7532ce00d 2201 python-ase_3.12.0-2.dsc
 da761b4a72a028a853f5197861327ddd01340a94 7916 python-ase_3.12.0-2.debian.tar.xz
Checksums-Sha256:
 9fd0f8797344502b80b87c89b32f3d8118b7c6a3e5d3f092a9530a254f08d512 2201 
python-ase_3.12.0-2.dsc
 209a02bc07620b55438ed099ad8ac25e522f2aa38e8aff0250162b72981f648c 7916 
python-ase_3.12.0-2.debian.tar.xz
Files:
 df0911429f8095f8f26428c01e8ab656 2201 python optional python-ase_3.12.0-2.dsc
 71606a5a02f45313e0b9b4a1493d0668 7916 python optional 
python-ase_3.12.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIvBAEBCgAZBQJYXoTTEhxnaW5nZ3NAZGViaWFuLm9yZwAKCRCvz+yOZpzhwjHX
EACI438xZF2LkYTUT4hbNgQie08tXv8yRqtYAxwdu50l9lKQjErQQmAog3zluowR
ZC5dCMfpD5Gu9cA0mmgapfaCoAIi03GRM2aN64Qwrtnpc7KkSac6CS1+MIIWVPP5
K4fSActnqXHeoCqAZPbin+YW12sApPUmIMlwmOZUIEJVAQ/eEQiiXrw4ojVLd8U5
T65WrxtTSN5FgVqfgQs3L2MBCHLK4PWadM9blqIcAIqSe+kT1+mH3jRIz1ZaHkx+
vwDWm4j4wtjSPtjWnIIY8oWb2oZETlfeR6TCIc/Wd+gt3N2i7zvPNKOorMyYvaQ3

Bug#808737: marked as done (nagios-plugin-check-multi: FTBFS: 10_check_multi.t (Wstat: 512 Tests: 94 Failed: 2))

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 15:10:23 +
with message-id 
and subject line Bug#808737: fixed in nagios-plugin-check-multi 0.26-3
has caused the Debian Bug report #808737,
regarding nagios-plugin-check-multi: FTBFS: 10_check_multi.t (Wstat: 
512 Tests: 94 Failed: 2)
to be marked as done.

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

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


-- 
808737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nagios-plugin-check-multi
Version: 0.26-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

nagios-plugin-check-multi fails to build from source in unstable/amd64:

  [..]

  Test Summary Report
  ---
  10_check_multi.t (Wstat: 512 Tests: 94 Failed: 2)
Failed tests:  56, 58
Non-zero exit status: 2
  Files=3, Tests=154, 10 wallclock secs ( 0.04 usr  0.01 sys +  6.24 cusr  0.40 
csys =  6.69 CPU)
  Result: FAIL
  Failed 1/3 test programs. 2/154 subtests failed.
  Makefile:33: recipe for target 'test' failed
  make[2]: *** [test] Error 255
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151222120727.e7OURkc7JD/nagios-plugin-check-multi-0.26/plugins/t'
  Makefile:96: recipe for target 'test' failed
  make[1]: *** [test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151222120727.e7OURkc7JD/nagios-plugin-check-multi-0.26'
  dh_auto_test: make -j1 test returned exit code 2
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


nagios-plugin-check-multi.0.26-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: nagios-plugin-check-multi
Source-Version: 0.26-3

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated 
nagios-plugin-check-multi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Dec 2016 14:24:12 +0100
Source: nagios-plugin-check-multi
Binary: nagios-plugin-check-multi
Architecture: source all
Version: 0.26-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Description:
 nagios-plugin-check-multi - run nagios checks as a group
Closes: 808737
Changes:
 nagios-plugin-check-multi (0.26-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to add test script directory perl search path.
   * Add patch to fix 'Unescaped left brace in regex is deprecated' warning.
   * Add patch to fix 10_check_multi.t failure.
 (closes: #808737)
   * Include patches from separate patch branches.
   * Restructure control file with cme.
   * Update Vcs-* URLs to use HTTPS.
   * Update copyright file using copyright-format 1.0.
   * Fix unknown & unused substitution variables.
   * Improve extended description.
   * Drop build dependency on autotools-dev, pulled in via dh-autoreconf.
   * Drop unused build dependency on dctrl-tools.
   * Bump debhelper compatibility to 9.
   * Bump Standards-Version to 3.9.8, changes: copyright-format 1.0.
   * Update configure options for icinga paths.
   * Update watch file to handle common issues.
Checksums-Sha1:
 3fe3a8511e3853bc95c6ea90462f29b6feda7037 2114 
nagios-plugin-check-multi_0.26-3.dsc
 de4a6c77434eae6afec148a334c618c60d734b15 5040 
nagios-plugin-check-multi_0.26-3.debian.tar.xz
 9acd5ef0781ec97dc4835299e059b2ba61692174 50710 
nagios-plugin-check-multi_0.26-3_all.deb
 fe57c1c6cd9b30c6610ed7a205eaf1515e352304 5072 
nagios-plugin-check-multi_0.26-3_amd64.buildinfo
Checksums-Sha256:
 

Bug#849031: marked as done (ceph: FTBFS on non-amd64: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sat, 24 Dec 2016 15:07:15 +
with message-id 
and subject line Bug#849031: fixed in ceph 10.2.5-2
has caused the Debian Bug report #849031,
regarding ceph: FTBFS on non-amd64: dh_install: missing files, aborting
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.)


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

Builds of ceph for architectures other than amd64 have been failing, mostly
with errors along the lines of

  dh_install --fail-missing
  dh_install: lib/systemd/system/rbdmap.service exists in debian/tmp but is not 
installed to anywhere
  dh_install: lib/systemd/system/ceph-disk@.service exists in debian/tmp but is 
not installed to anywhere
  dh_install: lib/systemd/system/ceph-rbd-mirror@.service exists in debian/tmp 
but is not installed to anywhere
  [...]
  dh_install: lib/systemd/system/ceph.target exists in debian/tmp but is not 
installed to anywhere
  dh_install: usr/lib/i386-linux-gnu/libcephfs_jni.a exists in debian/tmp but 
is not installed to anywhere
  dh_install: usr/lib/i386-linux-gnu/ceph/compressor/libceph_example.a exists 
in debian/tmp but is not installed to anywhere
  dh_install: usr/lib/i386-linux-gnu/ceph/compressor/libceph_snappy.a exists in 
debian/tmp but is not installed to anywhere
  [...]
  dh_install: usr/lib/i386-linux-gnu/ceph/compressor/libceph_zlib.so.2.0.0 
exists in debian/tmp but is not installed to anywhere
  dh_install: missing files, aborting
  debian/rules:66: recipe for target 'override_dh_install' failed
  make[1]: *** [override_dh_install] Error 255

(Builds on a few architectures failed earlier, due to errors I'll report
separately.)

I'm not sure offhand what's up with the lib/systemd paths -- perhaps a
systemd update while ceph was in NEW?  As for the files under /usr/lib, the
issue appears to be the presence of hardcoded /usr/lib/x86_64-linux-gnu
paths in debian/not-installed, which is documented not to support
wildcards. :-/ I suppose you could, prior to running dh_install, arrange
either to generate debian/not-installed or to remove up the unwanted files
altogether.

Could you please take a look?

Thanks!

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

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated ceph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Dec 2016 13:14:28 +0100
Source: ceph
Binary: ceph ceph-base rbd-mirror rbd-nbd ceph-common ceph-mds ceph-mon 
ceph-osd ceph-fuse rbd-fuse ceph-fs-common ceph-resource-agents librados2 
librados-dev libradosstriper1 libradosstriper-dev librbd1 librbd-dev libcephfs1 
libcephfs-dev librgw2 librgw-dev radosgw ceph-test python-ceph python-rados 
python-rbd python-cephfs libcephfs-java libcephfs-jni
Architecture: source amd64 all
Version: 10.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Ceph Maintainers 
Changed-By: Gaudenz Steinlin 
Description:
 ceph   - distributed storage and file system
 ceph-base  - common ceph daemon libraries and management tools
 ceph-common - common utilities to mount and interact with a ceph storage cluste
 ceph-fs-common - common utilities to mount and interact with a ceph file system
 ceph-fuse  - FUSE-based client for the Ceph distributed file system
 ceph-mds   - metadata server for the ceph distributed file system
 ceph-mon   - monitor server for the ceph storage system
 ceph-osd   - OSD server for the ceph storage system
 ceph-resource-agents - OCF-compliant resource agents 

Processed: tagging 847698

[Debian Bug Tracking System]

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

> tags 847698 + fixed-upstream
Bug #847698 [sbcl] pgloader FTBFS on arm64: The value 64 is not of type 
(INTEGER -32 63)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#849271: version comparison fails with numpy 1.12.0b1

[Ole Streicher]

package: astropy
version: 1.3-1
severity: serious
forwarded: https://github.com/astropy/astropy/issues/5643

With astropy 1.3 and numpy 1.12.0b1, many affiliated packages now fail
in the tests when the numpy version number is compared. For example aplpy:

Traceback (most recent call last):
  File "debian/tests/python3-aplpy", line 7, in 
import aplpy
  File "/usr/lib/python3/dist-packages/aplpy/__init__.py", line 9, in

from ._astropy_init import *
  File "/usr/lib/python3/dist-packages/aplpy/_astropy_init.py", line
116, in 
from astropy import config
  File "/usr/lib/python3/dist-packages/astropy/__init__.py", line 116,
in 
_check_numpy()
  File "/usr/lib/python3/dist-packages/astropy/__init__.py", line 104,
in _check_numpy
from .utils import minversion
  File "/usr/lib/python3/dist-packages/astropy/utils/__init__.py", line
20, in 
from .compat.odict import OrderedDict
  File
"/usr/lib/python3/dist-packages/astropy/utils/compat/__init__.py", line
14, in 
from .numpycompat import *
  File
"/usr/lib/python3/dist-packages/astropy/utils/compat/numpycompat.py",
line 24, in 
NUMPY_LT_1_12 = not minversion('numpy', '1.12dev')
  File "/usr/lib/python3/dist-packages/astropy/utils/introspection.py",
line 159, in minversion
return parse_version(have_version) >= parse_version(version)
  File "/usr/lib/python3.5/distutils/version.py", line 70, in __ge__
c = self._cmp(other)
  File "/usr/lib/python3.5/distutils/version.py", line 337, in _cmp
if self.version < other.version:
TypeError: unorderable types: int() < str()

Bug#848063: fixed in ri-li 2.0.1+ds-4

[Markus Koschany]

Control: severity -1 important

On 24.12.2016 11:50, Santiago Vila wrote:
> found 848063 2.0.1+ds-4
> thanks
> 
> Hello. Sorry for the reopening but this issue is still happening in
> this version.
> 
> (Also, sorry for not noticing it before, I usually build packages in
> testing because there are too many broken packages in unstable).
> 
> This time I only built it once, and it failed. Build log attached.

Thanks for working on the reproducible build project. However this is
not a release critical issue because the last version builds fine on all
release architectures. [1]

It would be useful to know in which way the reproducible builds
environments differs from the official buildd servers. Apparently the
build cannot open a display server but xvfb-run should ensure that they
are automatically found and used. So this is probably a regression in
xvfb-run or some kind of race condition because nothing has changed in
ri-li for a long time.

[1] https://buildd.debian.org/status/package.php?p=ri-li=unstable




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#848063: fixed in ri-li 2.0.1+ds-4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #848063 [src:ri-li] ri-li: FTBFS randomly (Impossible d'initialiser 
SDL:Couldn't open X11 display)
Severity set to 'important' from 'serious'

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

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Ole Streicher]

Control: tags -1 patch

Hi,

the attached patch fixes the FTBFS. What is the schedule to fix the
other problems with statsimage -- especially pandas?

best regards

Ole
>From 5c6f9ffecf8e53c32edc14326042bb4d5ca6a641 Mon Sep 17 00:00:00 2001
From: Ole Streicher 
Date: Sat, 24 Dec 2016 14:56:07 +0100
Subject: [PATCH] Fix index type in `reshape` to be integer

---
 debian/changelog  |  6 ++
 debian/patches/fix_wrong_index_type.patch | 15 +++
 debian/patches/series |  1 +
 3 files changed, 22 insertions(+)
 create mode 100644 debian/patches/fix_wrong_index_type.patch

diff --git a/debian/changelog b/debian/changelog
index febebbe..bbd71aa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+statsmodels (0.8.0~rc1+git59-gef47cd9-2) UNRELEASED; urgency=medium
+
+  * Fix index type in `reshape` to be integer. Closes: #848782
+
+ -- Ole Streicher   Sat, 24 Dec 2016 14:56:22 +0100
+
 statsmodels (0.8.0~rc1+git59-gef47cd9-1) unstable; urgency=medium
 
   * Fresh upstream rc snapshot which hopefully addresses some
diff --git a/debian/patches/fix_wrong_index_type.patch b/debian/patches/fix_wrong_index_type.patch
new file mode 100644
index 000..ca284b9
--- /dev/null
+++ b/debian/patches/fix_wrong_index_type.patch
@@ -0,0 +1,15 @@
+Author: Ole Streicher 
+Descrption: Fix index type in `reshape` to be integer.
+
+This will avoid FTBFS with numpy >= 1.12 beta
+--- a/statsmodels/genmod/generalized_estimating_equations.py
 b/statsmodels/genmod/generalized_estimating_equations.py
+@@ -2392,7 +2392,7 @@
+ exog_names = [x.split("[")[0] for x in exog_names]
+ 
+ params = np.reshape(self.params,
+-(ncut, len(self.params) / ncut))
++(ncut, len(self.params) // ncut))
+ 
+ for ev in exog_values:
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 0f4a162..649de9c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -5,3 +5,4 @@ up_reduce_test_precision
 deb_skip_test_ons390
 deb_no_nbformat_for_now
 up_3239.patch
+fix_wrong_index_type.patch
-- 
2.10.2

Processed: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #848782 [src:statsmodels] statsmodels: FTBFS: TypeError: 'float' object 
cannot be interpreted as an index
Added tag(s) patch.

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

Bug#844034: Any intend to fix this soon

[Andreas Tille]

Somehow I was too fast in my previous mail ...

> When trying the first command from the test suite I get:

$ /usr/bin/Honey pie filtered_subreads.fastq lambda_modified.fasta -o 
mappingFinal.sam

Please Cite: English, Adam C., William J. Salerno, Jeffery G.
 Reid. "PBHoney: identyfying genomic variants via
 long-read discordance and interrupted mapping."
 BMC Bioinformatics 2014, 15:180 (June 10, 2014).
 doi:10.1186/1471-2105-15-180

2016-12-24 14:45:05,910 [INFO] Running /usr/bin/Honey pie 
filtered_subreads.fastq lambda_modified.fasta -o mappingFinal.sam
2016-12-24 14:45:05,910 [INFO] Running Blasr
2016-12-24 14:45:52,277 [INFO] [0, '[INFO] 2016-12-24T14:45:05 [blasr] 
started.\n[INFO] 2016-12-24T14:45:52 [blasr] ended.\n', None]
2016-12-24 14:45:52,277 [INFO] Mapping Tails
2016-12-24 14:45:52,278 [INFO] Extracting tails
2016-12-24 14:45:52,407 [INFO] Parsed 433 reads
2016-12-24 14:45:52,407 [INFO] Found 278 tails
2016-12-24 14:45:52,407 [INFO] 21 reads had double tails
2016-12-24 14:45:52,407 [INFO] Running Blasr
2016-12-24 14:45:52,470 [ERROR] blasr mapping failed!
2016-12-24 14:45:52,471 [ERROR] RETCODE 255
2016-12-24 14:45:52,471 [ERROR] STDOUT [INFO] 2016-12-24T14:45:52 [blasr] 
started.
ERROR, can not convert non-pacbio reads to pbbam record.

2016-12-24 14:45:52,471 [ERROR] STDERR None
2016-12-24 14:45:52,471 [ERROR] Exiting


I think I need to stop here.  The only thing I'm wondering about is
whether this is a critical sign for pbhoney / pbsuite or whether this
should be qualified as severity normal.  I'll leave the decision to
those who are more familiar with this software.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#844034: Any intend to fix this soon

[Andreas Tille]

On Sat, Dec 24, 2016 at 02:39:03PM +0100, Andreas Tille wrote:
> Hi again,

once more.  I just noticed that blasr 5.3-2 is properly linked and bhoney
test suite works now ...
 
> On Sat, Dec 24, 2016 at 10:30:48AM +0100, Andreas Tille wrote:
> > pbhoney is marked for autoremoval due to this bug.  I'm guessing from
> > the description of the problem that it should be easy to fix (without
> > having checked).  Do you intend to upload soon or should somebody
> > else step in here?
> 
> I've spent some time to work on this.  I admit its pretty confusing to
> parse blasr code what options are really used.  I've tried some trial
> and error approach and I think I've got the options now somehow working.
> However, when trying the first command from the test suite I get:
> 
> 
> $ /usr/bin/Honey pie filtered_subreads.fastq lambda_modified.fasta -o 
> mappingFinal.sam
> 
> Please Cite: English, Adam C., William J. Salerno, Jeffery G.
>  Reid. "PBHoney: identyfying genomic variants via
>  long-read discordance and interrupted mapping."
>  BMC Bioinformatics 2014, 15:180 (June 10, 2014).
>  doi:10.1186/1471-2105-15-180
> 
> 2016-12-24 14:29:32,478 [INFO] Running /usr/bin/Honey pie 
> filtered_subreads.fastq lambda_modified.fasta -o mappingFinal.sam
> 2016-12-24 14:29:32,478 [INFO] Running Blasr
> 2016-12-24 14:29:32,489 [ERROR] blasr mapping failed!
> 2016-12-24 14:29:32,489 [ERROR] RETCODE 134
> 2016-12-24 14:29:32,489 [ERROR] STDOUT [INFO] 2016-12-24T14:29:32 [blasr] 
> started.
> blasr: iblasr/MappingParameters.h:584: void MappingParameters::MakeSane(): 
> Assertion `"blasr must be compiled with lib pbbam to perform IO on bam." == 
> 0' failed.
> Aborted
> 
> 2016-12-24 14:29:32,489 [ERROR] STDERR None
> 2016-12-24 14:29:32,489 [ERROR] Exiting
> 
> 
> To verify whether blasr is linked against libpbbam I did:
> 
>   $ ldd /usr/bin/blasr | grep libpbbam
> 
> I'm not really sure how to continue from here.
> 
> Kind regards
> 
>Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Bug#844034: Any intend to fix this soon

[Andreas Tille]

Hi again,

On Sat, Dec 24, 2016 at 10:30:48AM +0100, Andreas Tille wrote:
> pbhoney is marked for autoremoval due to this bug.  I'm guessing from
> the description of the problem that it should be easy to fix (without
> having checked).  Do you intend to upload soon or should somebody
> else step in here?

I've spent some time to work on this.  I admit its pretty confusing to
parse blasr code what options are really used.  I've tried some trial
and error approach and I think I've got the options now somehow working.
However, when trying the first command from the test suite I get:


$ /usr/bin/Honey pie filtered_subreads.fastq lambda_modified.fasta -o 
mappingFinal.sam

Please Cite: English, Adam C., William J. Salerno, Jeffery G.
 Reid. "PBHoney: identyfying genomic variants via
 long-read discordance and interrupted mapping."
 BMC Bioinformatics 2014, 15:180 (June 10, 2014).
 doi:10.1186/1471-2105-15-180

2016-12-24 14:29:32,478 [INFO] Running /usr/bin/Honey pie 
filtered_subreads.fastq lambda_modified.fasta -o mappingFinal.sam
2016-12-24 14:29:32,478 [INFO] Running Blasr
2016-12-24 14:29:32,489 [ERROR] blasr mapping failed!
2016-12-24 14:29:32,489 [ERROR] RETCODE 134
2016-12-24 14:29:32,489 [ERROR] STDOUT [INFO] 2016-12-24T14:29:32 [blasr] 
started.
blasr: iblasr/MappingParameters.h:584: void MappingParameters::MakeSane(): 
Assertion `"blasr must be compiled with lib pbbam to perform IO on bam." == 0' 
failed.
Aborted

2016-12-24 14:29:32,489 [ERROR] STDERR None
2016-12-24 14:29:32,489 [ERROR] Exiting


To verify whether blasr is linked against libpbbam I did:

  $ ldd /usr/bin/blasr | grep libpbbam

I'm not really sure how to continue from here.

Kind regards

   Andreas.

-- 
http://fam-tille.de