Bug#836536: ruby-concurrent: FTBFS too much often (failed examples)

[Balasankar C]

On Sat, 3 Sep 2016 21:49:13 +0200 (CEST) Santiago Vila  wrote:
>   BTW: I think the "Randomized with seed xxx" above is a bad idea.
> Maintainers often ask bug reporters for "a way to reproduce the error".
> But if the build is based on random variables, this becomes an
> impossible task. Please consider modifying the build system so that
> those random things are always the same.

I believe I have fixed this in the latest upload, in which I specified the
order to run the tests. I tried building it 5 times in a cowbuilder environment
and didn't hit any failures. Please reopen the bug if this problem persists.

Thank you.


-- 
Balasankar C
http://balasankarc.in

Bug#837025: marked as done (pyasn1: FTBFS: debian/rules:16: *** target file 'debian/python-module-stampdir/pypy-pyasn1' has both : and :: entries. Stop.)

[Debian Bug Tracking System]

Your message dated Mon, 12 Sep 2016 05:35:39 +
with message-id 
and subject line Bug#837025: fixed in pyasn1 0.1.9-2
has caused the Debian Bug report #837025,
regarding pyasn1: FTBFS: debian/rules:16: *** target file 
'debian/python-module-stampdir/pypy-pyasn1' has both : and :: entries.  Stop.
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.)


-- 
837025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyasn1
Version: 0.1.9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 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):
>  fakeroot debian/rules clean
> py3versions: no X-Python3-Version in control file, using supported versions
> debian/rules:16: *** target file 'debian/python-module-stampdir/pypy-pyasn1' 
> has both : and :: entries.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> 
> Build finished at 2016-09-06T23:08:12Z

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/pyasn1_0.1.9-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: pyasn1
Source-Version: 0.1.9-2

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

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated pyasn1 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, 10 Sep 2016 14:22:55 +0200
Source: pyasn1
Binary: python-pyasn1 python3-pyasn1 pypy-pyasn1
Architecture: source all
Version: 0.1.9-2
Distribution: unstable
Urgency: medium
Maintainer: Jan Lübbe 
Changed-By: Vincent Bernat 
Description:
 pypy-pyasn1 - ASN.1 library for Python (PyPy module)
 python-pyasn1 - ASN.1 library for Python (Python 2 module)
 python3-pyasn1 - ASN.1 library for Python (Python 3 module)
Closes: 837025
Changes:
 pyasn1 (0.1.9-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 .
   [ Vincent Bernat ]
   * Switch to pybuild for build. It's far easier to get proper pypy
 support this way.  This happens to closes: #837025 (FTBFS).
Checksums-Sha1:
 f676c05b7ec11c5b210249b9a5efb5a255b996bf 2299 pyasn1_0.1.9-2.dsc
 609543f4bc4c66e900cf6a0ff023b89b27cec78c 4356 pyasn1_0.1.9-2.debian.tar.xz
 5643e8e371fcc6219c3f309cc9b5203852b799d6 34468 pypy-pyasn1_0.1.9-2_all.deb
 a35002caa66a08f43caf42e2404674109b60ac4e 51812 python-pyasn1_0.1.9-2_all.deb
 2a0e99cbba769dee5bd4c4f25e6b370bcbd6a979 34534 python3-pyasn1_0.1.9-2_all.deb
Checksums-Sha256:
 2136d96b3f94e702b57202589e3dfdc2d470255bb0f7292f41f1966699198247 2299 
pyasn1_0.1.9-2.dsc
 5c23055bff1716fea109b2590a83aafe37a6f6a46f0145b561783d305425c019 4356 
pyasn1_0.1.9-2.debian.tar.xz
 a15ef311be0fcaf14488853e4a45e0689ed0dd34696812ca188d3c6ba351bbfd 34468 
pypy-pyasn1_0.1.9-2_all.deb
 7bb8b22c8cd8b06ec0984bbaed33e336b55541171aebbeee76fb85b6adff6193 51812 
python-pyasn1_0.1.9-2_all.deb
 1ca17a959c1076e2a3f3952cf1894b7bfcb5994682b7be4b4b0c3665a1c49cba 34534 
python3-pyasn1_0.1.9-2_all.deb
Files:
 44bc1882a27d1225f53f4a21c2195494 2299 python optional pyasn1_0.1.9-2.dsc
 efac9a78a4b36eb7b6053142358cbfe9 4356 python optional 
pyasn1_0.1.9-2.debian.tar.xz
 f9c88502151eaa10ee6aa3d3603d9305 34468 python optional 
pypy-pyasn1_0.1.9-2_all.deb
 f1ce7c09cad2adbfe5a09d2a410e8c23 51812 python optional 
python-pyasn1_0.1.9-2_all.deb
 

Bug#823803: marked as done (libint2: FTBFS: build_libint.cc:34:34: fatal error: boost/preprocessor.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 12 Sep 2016 05:35:29 +
with message-id 
and subject line Bug#823803: fixed in libint2 2.1.0-1.1
has caused the Debian Bug report #823803,
regarding libint2: FTBFS: build_libint.cc:34:34: fatal error: 
boost/preprocessor.hpp: No such file or directory
to be marked as done.

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

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


-- 
823803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libint2
Version: 2.1.0-1
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,

libint2 fails to build from source in unstable/amd64:

  [..]

  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 'libint2-build-deps' in 
'../libint2-build-deps_2.1.0-1_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 libint2-build-deps.
  (Reading database ... 23072 files and directories currently installed.)
  Preparing to unpack libint2-build-deps_2.1.0-1_all.deb ...
  Unpacking libint2-build-deps (2.1.0-1) ...
  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 libint2-build-deps (2.1.0-1) ...
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package libint2
  dpkg-buildpackage: info: source version 2.1.0-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Michael Banck 
   dpkg-source --before-build libint2-2.1.0
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean
 dh_testdir
 debian/rules override_dh_auto_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0'
  dh_auto_clean
make -j1 distclean
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0'
  for dir in src tests/eri tests/hartree-fock doc tests/eri tests/hartree-fock; 
\
do \
  (cd ${dir} && make "DODEPEND=no" distclean) || exit 1; \
done
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src'
  for dir in bin lib; \
do \
  (cd ${dir} && make  distclean) || exit 1; \
done
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin'
  for dir in libint test_eri profile; \
do \
  (cd ${dir} && make  distclean) || exit 1; \
done
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/libint'
  rm -f *.o
  rm -f libINT.a test build_libint
  rm -f *.d
  rm -f *.dot
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/libint'
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/test_eri'
  rm -rf generate_eri_code test_eri time_eri test_eri_rys *.o *.d *.dot *.log
  rm -rf Make.compute_eri libint2_init.cc libint2_static_init.cc 
libint2_static_cleanup.cc  libint2_init.o libint2_static_init.o 
libint2_static_cleanup.o test_eri_conf.h libint2_types.h libint2_params.h 
libint2_iface.h libint2_iface_internal.h libint2_init.h libint2_static_init.h 
libint2_static_cleanup.h 
  rm -rf run_time_eri.pl run_timing_suite.pl stdtests.pl test_eri.pl time_eri.pl
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/test_eri'
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/profile'
  rm -rf generate_t0g12_code profile_Gm *.o *.d
  rm -rf *.dot *.log
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin/profile'
  rm -rf MakeVars
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160509094424.Pspk4sElY1.libint2/libint2-2.1.0/src/bin'
  make[4]: Entering directory 

Bug#811432: Krita no longer part of Calligra

[Pino Toscano]

Hi people,

TL;DR: there is currently krita 3.0.1 currently in NEW, and calligra
2.9.11 reaching NEW soon.

In data domenica 4 settembre 2016 13:02:30 CEST, 
juichenieder-deb...@yahoo.co.uk ha scritto:
> > My guess is that most of these bugs will fix themselves once 2.9 is
> > packaged. I think there were some attempts to fix these before, but the
> > package was rejected by the ftpmasters on copyright grounds - so they'll
> > need to be some work to sort that out.
> 
> Yes, pretty much my philosophy.  Why put time and energy into fixing something
> that you plan to discard for a newer version shortly after you have fixed it.
> When for all one knows, the upgraded package might auto-fix the problems you
> were trying to fix.
> 
> That said, the copyright grounds don't seem too severe... I guess the file 
> that
> they object to appeared in the build before, as they do not upload a new 
> version,
> thus it must also appear in Jessie and Sid ports, and only one file that could
> get downloaded seperately.

It seems the issues that caused the reject of the latest NMU for 2.8.x
are gone in newer calligra versions. Reviewing the licenses of all the
files in calligra, and writing a copyright file for them, has never
been an easy task (more than 22000 files!) -- different approaches to
do this basically caused the friction between a couple of contributors
last year, causing both of them to eventually more their efforts
elsewhere.

> How much of a task goes into packaging something like Calligra?  I see that
> calligra-2.9.10 went into the debian VCS on 2015-12-31 (last entry).  I have
> no experience in packaging, slowly as time goes on I learn more and more about
> this dark art, until I reach the point where I feel ready to take the plunge.

Excluding the copyright parts, IMHO the packaging parts are not too
difficult: it's mostly building, putting the files installed by upstream
in the right packages, checking that the package relationships
(depends/recommends/etc) are correct, and stuff like that (including
testing, of course).

A potentially problematic part is the size of calligra itself: lots of
sources and libraries/executables, which take at least even 2 hours on
not-super-fast machines: this means that if you want to test a new
split package, or move files from package to package, and so on, it's
a "issue build + take a pause" cycle much longer than a cup of
$beverage...

> > I was thinking about helping packaging Krita, but I haven't found the
> > time as of yet.
> 
> I would consider packaging it myself, but as I say, I don't feel quite ready
> to take the plunge just yet, and the time commitment puts me of a bit.  I have
> reached the stage where ${misc:Depends} and ${shlibs:Depends} now pique my
> curiosity as that seems part of the initial problem here in this bug.  That
> debian autodetects the wrong library (to link against?).  As far as I 
> understand.

I've took the time yesterday to work on the new krita 3.x, based on
Qt5+Frameworks; you can find its packaging among the rest of the pkg-kde
repositories [1]. Packaging itself didn't take much, but as usual
copyright took quite a lot. Anyway, I deemed it acceptable for now, so
built and uploaded it to NEW. If you have any improvements for it,
please reach me directly so I can queue them until krita is in NEW.

Regarding calligra: first of all, I dropped entirely krita from there
(because of src:krita), then cleaned up the rest of the packaging work
done already. Right now it's building on my machine, and will be
uploaded to NEW afterwards. As above, please do reach me directly for
any change until it's accepted in unstable again.

[1] https://anonscm.debian.org/cgit/pkg-kde/kde-std/krita.git

Regards,
-- 
Pino Toscano

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

Bug#775541: tests of new packages

[Vincent McIntyre]

On Mon, Sep 12, 2016 at 02:38:32PM +1000, Vincent McIntyre wrote:

A brief note on the client side of things.

At step 3, after installing your packages but before tweaking
nfs-server.service, the critical chain for the client mount is

usr-local.mount +1.145s
└─remote-fs-pre.target @7.493s
  └─nfs-client.target @2.362s

After (step 4.x) it is somewhat different

usr-local.mount +1.141s
└─remote-fs-pre.target @10.207s
  └─nfs-server.service @10.193s +12ms
└─rpc-statd.service @10.342s +18ms
  └─nss-lookup.target @10.340s

The 'list-dependencies' output is the same for both
Dependencies for usr-local.mount
usr-local.mount
● ├─-.mount
● ├─system.slice
● ├─usr.mount
● └─network-online.target

Not sure why nfs-client has dopped out of the picture.
Nonetheless, the mount works fine.

Cheers
Vince

Bug#775541: tests of new packages

[Vincent McIntyre]

On Fri, Sep 09, 2016 at 10:22:25AM +0200, Andreas Henriksson wrote:
> Hello Vincent McIntyre.
> 
> Thanks for your thurough testing and useful feedback.
> 
> Let me start with a disclaimer: I'm not maintaining nfs (and I'm
> not even using it myself so my knowledge is very limited). My only
> involvement here is trying to squash some RC bugs and unblocking
> work elsewhere by importing native systemd units.

That is fine with me and highly appreciated.

> On Fri, Sep 09, 2016 at 11:57:34AM +1000, Vincent McIntyre wrote:
> > 
> > Thanks Andreas for those new packages.
> > I did some testing of the 1.2.8-9.2 packages on a clean jessie install.
> > They are pretty close but I found an issue with NFS exports in one case.
> > 
> > I used the attached check.sh script to show the state of various targets
> > as I changed things. The attached results.tar shows the output from it.
> > Between each major stage below, the system is rebooted.
> > Then I log in and run check.sh before doing anything else.
> > Throughout, /etc/network/interfaces contained:
> >   source /etc/network/interfaces.d/*
> >   auto lo
> >   iface lo inet loopback
> >   allow-hotplug eth0
> 
> I think this  is problematic and unfortunately spoils my interest
> in the rest of your testing.
> 
> From what I've been told one of the main differences between "auto"
> and "allow-hotplug" is that allow-hotplug will not block your bootup
> so services will run wild and start up ASAP. This means they can and
> likely will start up before your network connection is up. Specially
> if using dhcp which takes time to configure the interface and extra
> so if you're using a network device (eg. usb dongle) which takes a
> long time to initialize.
> 
> I assume eth0 was involved in your tests, and if so it would be
> very useful to know what difference it makes if you use auto
> instead.
> 

Thanks for that. I've repeated with a slightly different numbering.
The short version is that the client mounts and exports all work
with your packages and 'auto eth0' BUT one change is needed to make
exports work at boot time:

  /lib/systemd/system/nfs-mountd.service

 - After=network.target local-fs.target   
 + After=rpcbind.target network.target local-fs.target

There might be a more elegant way to this but this seems to work.

I did a quick check of your packages with 'auto eth0' and a static
address setup in /etc/network/interfaces. That worked also but
to get the exports working at boot the change above was required.

Detailed results:

step 1 - jessie system with nfs packages 1.2.8-9
 one fstab mount, no exports. no changes to /etc/default/nfs-*
 The fstab mount works ok; it politely waits for dhcp to finish
 before trying to mount. It works in all the other tests so
 I won't mention it further.

step 2 - as above but export one filesystem.
 Tried a few different ways to do the exports
   - wildcard host (step2.1)
   - point the export at a single host (step2.2)
   - point the export at a netgroup (step2.3)
  All of these work with no problem.
   
step 3 - jessie system with nfs packages 1.2.8-9.2
 one fstab mount, one exported directory.
 
 rpc.mountd fails to start because it wants rpcbind to be there,
 but rpcbind has not been started yet. showmount -e fails:
 # showmount -e
 clnt_create: RPC: Program not registered
 
step3.1 - modify  /lib/systemd/system/nfs-mountd.service,
- After=network.target local-fs.target
+ After=rpcbind.target network.target local-fs.target
   run systemd daemon-reload
   but don't reboot.
   The exports are still not there
   # showmount -e
   clnt_create: RPC: Program not registered
 
   re run exports, it fails
   # exportfs -rav
   exporting @all_hosts:/data/INSTALL_1
   # showmount -e
   clnt_create: RPC: Program not registered
   #

step 4 - reboot after step3.1:
 All of the exports work now.
 I don't need to insert any 30s waits anywhere, yay.
 

Without the tweak to nfs-mountd.service, the critical chain is:
nfs-mountd.service +33ms
└─network.target @7.453s
  └─networking.service @2.349s +5.103s
└─local-fs.target @2.345s
  └─data-INSTALL_1.mount @2.212s +132ms
└─systemd-fsck@dev-mapper-libra\x2ddata.service @2.193s +16ms
  └─dev-mapper-libra\x2ddata.device @2.192s

With the tweak in place
nfs-mountd.service +19ms
└─rpcbind.target @10.169s
  └─rpcbind.service @10.126s +42ms
└─network-online.target @10.123s
  └─network.target @10.123s
└─networking.service @1.289s +8.833s
  └─local-fs.target @1.285s
└─data-INSTALL_1.mount @1.061s +223ms
  └─systemd-fsck@dev-mapper-libra\x2ddata.service @1.043s +14ms
└─dev-mapper-libra\x2ddata.device @1.042s

Active config in 

Bug#837123: [anna] segfault in wheezy installer

[Vincent McIntyre]

On Mon, Sep 12, 2016 at 12:28:55PM +1000, Vincent McIntyre wrote:
> 
> >  - make sure all ipv6 related options are disabled
> >and no ipv6 DNS entries exist for the target host
> 
>Didn't try it. The failure happens really early, before the
>preseed file is downloaded.

Incorrect. The preseed is downloaded ok but it doesn't matter, as far
as I can see, the fault happens before any network configuration
directives in the preseed file can be used.

Vince

Bug#837123: [anna] segfault in wheezy installer

[Vincent McIntyre]

On Sat, Sep 10, 2016 at 11:30:32AM +1000, Vincent McIntyre wrote:
> 
> You've given me a few things to try out
>  - tell DHCP to supply different DNS servers (running bind)

   Makes no difference. These servers are not configured for v6,
   while the first ones I used were. There are no v6 entries for
   the host in any case.

>  - make sure all ipv6 related options are disabled
>and no ipv6 DNS entries exist for the target host

   Didn't try it. The failure happens really early, before the
   preseed file is downloaded.

>  - make sure all ipv6 related options are enabled
>and valid ipv6 DNS entries exist for the target host
 
   Didn't try
 
> Also I can try installing oldstable with the jessie installer.
  
  This worked. Even with mirror/udeb/suite set to 'stable'.
  For anyone who comes along later, the udeb versions were
anna 1.52
base-installer 1.154
libc6-udeb 2.19-18+deb8u4
netcfg 1.131+deb8u1

I think this bug can probably be downgraded until someone else can
reproduce it, or at least marked as 'not found' in the later version
of libc6-udeb. If I get time I will try with the daily installer and
report on that.

Vince

Bug#836642: Processed: severity of 836642 is serious

[Benjamin Kaduk]

On Sat, 10 Sep 2016, Debian Bug Tracking System wrote:

> Processing commands for cont...@bugs.debian.org:
>
> > severity 836642 serious
> Bug #836642 [openafs] openafs: please drop the build dependency on 
> hardening-wrapper
> Severity set to 'serious' from 'important'

That was a bit sooner than I expected, but I guess we can go ahead and try
dumping them all in $(CC) now-ish, then.

-Ben

Bug#837468: csoundqt: FTBFS: Project ERROR: A valid csound library was not found.

[Felipe Sateler]

Control: forcemerge 837273 -1

Hi,

On 11 September 2016 at 16:42, Chris Lamb  wrote:
> Source: csoundqt
> Version: 0.9.2.1-3
> 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,
>
> csoundqt fails to build from source in unstable/amd64:

Thanks for reporting! This bug is actually in src:csound, and was
filed a few days ago. I'm merging the bugs.

-- 

Saludos,
Felipe Sateler

Processed (with 1 error): Re: Bug#837468: csoundqt: FTBFS: Project ERROR: A valid csound library was not found.

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 837273 -1
Bug #837273 {Done: Felipe Sateler } [libcsound64-dev] 
libcsound64-dev: missing .so symlink
Unable to merge bugs because:
package of #837468 is 'src:csoundqt' not 'libcsound64-dev'
Failed to forcibly merge 837273: Did not alter merged bugs.


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

Bug#836815: marked as done (php-php-gettext (after rename) doesn't ship the actual code)

[Debian Bug Tracking System]

Your message dated Mon, 12 Sep 2016 01:03:44 +
with message-id 
and subject line Bug#836815: fixed in php-gettext 1.0.11-4
has caused the Debian Bug report #836815,
regarding php-php-gettext (after rename) doesn't ship the actual code
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.)


-- 
836815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-php-gettext
Version: 1.0.11-3

When php-gettext was renamed to php-php-gettext, the actual code files
were left as part of php-gettext:

$ dpkg -L php-gettext
...
/usr/share/php/php-gettext/gettext.inc
/usr/share/php/php-gettext/gettext.php
/usr/share/php/php-gettext/streams.php

However, php-gettext is described as a "transitional dummy package"
which "can be safely removed".

I suspect the files should have been moved to php-php-gettext too.
However, if that is going to happen, do they need to still live at the
old path, or should php-gettext ship symlinks?

-- 
Richard
--- End Message ---
--- Begin Message ---
Source: php-gettext
Source-Version: 1.0.11-4

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

Debian distribution maintenance software
pp.
Marcelo Jorge Vieira  (supplier of updated php-gettext 
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, 10 Sep 2016 20:27:12 -0300
Source: php-gettext
Binary: php-php-gettext php-gettext
Architecture: source all
Version: 1.0.11-4
Distribution: unstable
Urgency: high
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Marcelo Jorge Vieira 
Description:
 php-gettext - transitional dummy package for php-php-gettext
 php-php-gettext - read gettext MO files directly, without requiring anything 
other
Closes: 830699 830702 836815
Changes:
 php-gettext (1.0.11-4) unstable; urgency=high
 .
   * php-php-gettext (after rename) doesn't ship the actual code
 (Closes: #836815)
   * Depend on php-mbstring (LP: #1600612) (Closes: #830702)
 Thanks Richard Laager 
   * Fix deprecated constructors to avoid warnings (Closes: #830699)
 (LP: #1522900); Thanks Richard Laager 
   * Remove debian/README.source (3.0 (quilt) source package)
Checksums-Sha1:
 26d7ecd4e7851fef094a3cbde3bce2667bcfab66 1999 php-gettext_1.0.11-4.dsc
 6f29ccd808b63e8e14b323372b2c44393e9da0ea 4056 
php-gettext_1.0.11-4.debian.tar.xz
 b2a1f337c890c98ca93a37a8995c81b4a182635a 3330 php-gettext_1.0.11-4_all.deb
 4cbab3a2b7713435901c7475d65bfbe4cc2617eb 16066 php-php-gettext_1.0.11-4_all.deb
Checksums-Sha256:
 945a1cf134b7b338c8ef08b3527282005d72f3916baadeef8ddeef73fe528d36 1999 
php-gettext_1.0.11-4.dsc
 13954c78a9d6ac0fbd3968d8e2ff44e27091c4040bd2be54109b3bbcc1238d70 4056 
php-gettext_1.0.11-4.debian.tar.xz
 d50f448bb9c62ca9451878f7607e5b1d17e1ca514914a67d3cb76c499377bc4d 3330 
php-gettext_1.0.11-4_all.deb
 4932b211ecd599a290a8b51786857ca815a7fe5835dbb548bdcb5c9007511073 16066 
php-php-gettext_1.0.11-4_all.deb
Files:
 446d05e53f2fa6109ca38191a3fa3fee 1999 php optional php-gettext_1.0.11-4.dsc
 b282422bacf55fc1eb67a3b877bdf7ed 4056 php optional 
php-gettext_1.0.11-4.debian.tar.xz
 4935d0feffe1a4c641053f3a04fbf39d 3330 oldlibs extra 
php-gettext_1.0.11-4_all.deb
 b7a04c6bfc85b1ca32de3f32a0742407 16066 php optional 
php-php-gettext_1.0.11-4_all.deb

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJX1fxGERxtZXRhbEBkZWJpYW4ub3JnAAoJEFuSTuMQBVzT3mIP
/i0GE+eg9mcE61F/ymqFQbFtgrGIhqWL+sg5yYLa3f6q1mlOuaQG4e8zkV35LXeo
seYElLWlhWfYOWqOBAhAaivkTW0knkI7ePTAPmkcauFH8LIV4vRlwAxWLkMOBGOg
iSbOPJplcU7LbIV1DCJJzEZKkrd8MihigIKzFUT0l+kFia0PlAm2PB1tWh426jQS
h/KeAVdNPm2h79t0lovN7wkLNipE7ByWXxeDCANKnS6tTunxx1NQl9s2Xj6+uYj7
nRQzvoJuwEAWkebBAM0ye1G3G48pVhZGRXmjsHN3rtHolSNkvD8RKmShe5yYvISE
pdWhGCGg4wCCdH8tdtPi1TeS7Hh/R8YS4sSl94EugyaCBF78sQH4+Q8nPcl4R3+g
36a0DcmDAC2J+cRKbuPyyZqMPydoXgDzFVSLzzTMrNC3h+GtojrX5fVpigOJ5vwm

Bug#837501: greylistd: fails to install in testing: invoke-rc.d: unknown initscript, /etc/init.d/exim4 not found.

[Andreas Beckmann]

Package: greylistd
Version: 0.8.8.6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

[...]
  Setting up exim4-config (4.87-3) ...
  Adding system-user for exim (v4)
  Setting up greylistd (0.8.8.6) ...
  Adding system user `greylist' (UID 151) ...
  Adding new group `greylist' (GID 151) ...
  Adding new user `greylist' (UID 151) with group `greylist' ...
  Not creating home directory `/var/lib/greylistd'.
  Adding user `Debian-exim' to group `greylist' ...
  Adding user Debian-exim to group greylist
  Done.
  invoke-rc.d: unknown initscript, /etc/init.d/exim4 not found.
  dpkg: error processing package greylistd (--configure):
   subprocess installed post-installation script returned error exit status 100
[...]
  Setting up exim4-base (4.87-3) ...
  exim: DB upgrade, deleting hints-db
[...]
  Setting up exim4-daemon-light (4.87-3) ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libgssapi-krb5-2:i386 (1.14.3+dfsg-1) ...
  Setting up exim4 (4.87-3) ...
[...]


This was a piuparts test in stretch/i386 with --install-recommends enabled.


cheers,

Andreas


greylistd_0.8.8.6.log.gz
Description: application/gzip

Processed: tagging 836505

[Debian Bug Tracking System]

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

> # Got a new upstream release to sponsor. :-)
> tags 836505 + pending
Bug #836505 [src:elog] elog: CVE-2016-6342: posting entry as arbitrary username 
by improper authentication
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837496: mopidy-podcast-gpodder: needs to be updated for mopidy-podcast 2.x

[Andreas Beckmann]

Package: mopidy-podcast-gpodder
Version: 1.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

mopidy-podcast 2.x has added a Breaks: mopidy-podcast-gpodder (<< 2.0)


Cheers,

Andreas

Bug#837495: gnome-shell-extension-suspend-button: uninstallable in sid: Depends: gnome-shell (< 3.21) but 3.21.91-2 is to be installed

[Andreas Beckmann]

Package: gnome-shell-extension-suspend-button
Version: 0~git20160525-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

  The following packages have unmet dependencies:
 gnome-shell-extension-suspend-button : Depends: gnome-shell (< 3.21) but 
3.21.91-2 is to be installed


Cheers,

Andreas

Processed: Re: gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.

[Debian Bug Tracking System]

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

> reopen 837121
Bug #837121 {Done: Anton Gladky } [gazebo] gazebo: please 
restrict libkido-dev (build-)dependency to architectures where it is available.
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gazebo/7.3.0+dfsg-4.
>
End of message, stopping processing here.

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

Bug#836660: marked as done (vzctl: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:24:14 +
with message-id 
and subject line Bug#836660: fixed in vzctl 4.9.4-3
has caused the Debian Bug report #836660,
regarding vzctl: please drop the build dependency on hardening-wrapper
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.)


-- 
836660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vzctl
Version: 4.9.4-2
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: vzctl
Source-Version: 4.9.4-3

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

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated vzctl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 21:54:34 +0200
Source: vzctl
Binary: vzctl
Architecture: source amd64
Version: 4.9.4-3
Distribution: unstable
Urgency: high
Maintainer: Ola Lundqvist 
Changed-By: Ola Lundqvist 
Description:
 vzctl  - server virtualization solution - control tools
Closes: 836660
Changes:
 vzctl (4.9.4-3) unstable; urgency=high
 .
   * Removed depdendency on hardening wrapper. Closes: #836660.
Checksums-Sha1:
 8d44f8abb6763e91309da7fc1fba8bbf2c41 1745 vzctl_4.9.4-3.dsc
 407e2f01d065410e72cda84cafd20f77fead43c7 15224 vzctl_4.9.4-3.debian.tar.xz
 82c8c4913b05bb0a4682066ada9d95144849e67f 274958 vzctl_4.9.4-3_amd64.deb
Checksums-Sha256:
 2e387d2826d10ed71200395730ee396c10bc870a298b1e3e58427d258ec3090d 1745 
vzctl_4.9.4-3.dsc
 2cb34c0aa20e72dec08b4f6541bd6d00aae8119b88ec0edc8e67ac164294f9ec 15224 
vzctl_4.9.4-3.debian.tar.xz
 6fb09086bfdebdc27d483a74cf5e5a6647393a216b9ddbbeb19e4fe93e640665 274958 
vzctl_4.9.4-3_amd64.deb
Files:
 95ad1c86f28adf5e24c7e16adc82f673 1745 admin optional vzctl_4.9.4-3.dsc
 ad9f089804f03c97ff83e6be97fd8496 15224 admin optional 
vzctl_4.9.4-3.debian.tar.xz
 5d32033df5d70080620f9a287b166690 274958 admin optional vzctl_4.9.4-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX1blQAAoJEF6Q3PqUJodv0SgP/07kcaWqzgk8DAHjC5wM77NC
TuT//rAlrJqZyDdKExrGPOJCDs837buTbYCjOHb+zPGoY7ssn005iHL0G1gJp5fc
7TpLsG4cu7kfzlk1qcNH4OZoo8F1WQ+3GcCQjFVPGlKa4LVPhTa60e0pvk9NQ+BM
ccipUXNeASK6hE4v2C/NJNc+mzmZPRTDLN/lpvXMkgBP8Glb6YQW3csF00w2QTEb
9YwOXkFu4UjNBtHxhvnDVo6qZjgzuFPTFwfiXwA9LdFuSYIo52Lc5TkPfVjfReQB
vh2RJdp4huuhzodpOrx5tezxn3shKkHerjkNSdN2KOYfPdyw98THtw18Ja5pfnFt
vEQ/ducv0PYQtV+Dn0WV0jnfESzKii9nS8WW6sOGEoxI5ULk2GKrAlhxg9Iv8DaU
cusyXSyiqIiWf6JP/G0xbSVE8lsuobpfCPe5EE/nNF/6tkKZ6W0nm1otoueXV8AG
gSLNWZX9SwYJFk2+pDi2qljlclIm+BRoyqQOY29SNIdo06NT4yb6vm+eB931soeM
JPkxfJSHMh1ImL/Xyxp+KzTdA+5RVaGAJRizYWnmRArtWgIvsTB/9sdNF5F5R1WS
I7aGDJt6crROc70VYtdUHtVLWqSX2xmt4kkO5nivj0QmlRA8KtnjsPLowVj4FxKw
4p9QQo5UHdmVLniWCkLh
=zukC
-END PGP SIGNATURE End Message ---

Bug#836661: marked as done (vzquota: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:24:25 +
with message-id 
and subject line Bug#836661: fixed in vzquota 3.1-2
has caused the Debian Bug report #836661,
regarding vzquota: please drop the build dependency on hardening-wrapper
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.)


-- 
836661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vzquota
Version: 3.1-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: vzquota
Source-Version: 3.1-2

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

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated vzquota package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 22:08:41 +0200
Source: vzquota
Binary: vzquota
Architecture: source amd64
Version: 3.1-2
Distribution: unstable
Urgency: high
Maintainer: Ola Lundqvist 
Changed-By: Ola Lundqvist 
Description:
 vzquota- server virtualization solution - quota tools
Closes: 836661
Changes:
 vzquota (3.1-2) unstable; urgency=high
 .
   * Removed depdendency on hardening wrapper. Closes: #836661.
   * Simplified rules file significantly.
Checksums-Sha1:
 56a1dd4752a59f2a8b1701d6cee1b56845f7717a 1650 vzquota_3.1-2.dsc
 d761e55aa9f2414a45c8db5a5420e2fccd78c287 3636 vzquota_3.1-2.diff.gz
 8e4ffbed36735e33b711157920f1f63f9fb6fd8a 46430 vzquota_3.1-2_amd64.deb
Checksums-Sha256:
 f86fcbff3730b260e7182b382d7d84dd5f492765652e16d568eb6e11226855f2 1650 
vzquota_3.1-2.dsc
 dc1eb9f9664569d71d8c59b1c77e9abf8a74aba8bc76be4791c36c4bacbde563 3636 
vzquota_3.1-2.diff.gz
 b0d0152bd474bd056de3362926723e7b07bd5afa2655780b38acf4271d2fd0af 46430 
vzquota_3.1-2_amd64.deb
Files:
 05da474b10d87200dcd259b558e1c6fb 1650 admin optional vzquota_3.1-2.dsc
 e766646039ad23c4ad8318d5d0b8c9b3 3636 admin optional vzquota_3.1-2.diff.gz
 aeacc24fcfd41a1fe5a137193eff7804 46430 admin optional vzquota_3.1-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX1bqrAAoJEF6Q3PqUJodv1joQAL368TWizTfR4wsW1Rdo5kZF
zXIEo/bdwzKbIpBckmE2ZT4rfzwios1ysnM3jB7TzmtKQVYDi6kNDJFj0FkP2S4g
bQBeTwKtyjbx9aYoBXkAZWx/3bXhWHBz+vR3IxDkDjHQc9INQ3IUDMh1pqHrnn/e
/GaXTextAw+jefj7tOmX1eMpdlSK2Xw2yPQafWfpcAdYwUaTad8lMrFVr5M5pTEr
GW197+HTEnTmnF6CpXdm8H4mu+LP0RI7/uKkl1cz4wz/RFmj/Kc/Cs5YBVp46qEc
P7axuCUC0VHtBUAaB7mUS+uYCeqEcWycybe9HBG8kPaVl3aiJAPCh5D8h5zR9+tp
4e1gaNmXMAcNpdgLy0D5nvHpyNrikajoY3XM6DvEAJu2V4emqcj/s2Eym6U+ZkHY
4EoU8fqeJmc4OuElRVjZgSlSjaftkIjC5Pt4X4Unxl2bjnid6Iew8Izi1sfIoiKw
ahjZw8Qod/cdbTaDabQRQ16TafMXe3xf42Z7xal4q4FHyDW5hESCTGAsF0TjSV+V
OSUQWMuR4o0uKSymd5Amf2FUj5LwiSA72fyqXEhG2i+ycdwGsBx45gRD53z0kGbv
pdKrgnwJUUTFEG+XzHKSEPDuelTxeB6JesvE/Y27qm9rjFjuFOfw4qaWmDBFNM0m
fb5jlanUGMFcmJUpVQfR
=F5EL
-END PGP SIGNATURE End Message ---

Bug#837382: marked as done (strip-nondeterminism: Tests fail when TZ != "UTC")

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:24:02 +
with message-id 
and subject line Bug#837382: fixed in strip-nondeterminism 0.027-1
has caused the Debian Bug report #837382,
regarding strip-nondeterminism: Tests fail when TZ != "UTC"
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.)


-- 
837382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strip-nondeterminism
Version: 0.026-1
Severity: serious

See 


HW42 wrote:

 > The problem is TZ != "UTC". The strip-nondeterminism and
 > dh_strip_nondeterminism tools set TZ to "UTC" so it doesn't show up in
 > regular use. But the test doesn't do this.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: strip-nondeterminism
Source-Version: 0.027-1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated strip-nondeterminism package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 23:10:35 +0100
Source: strip-nondeterminism
Binary: libfile-stripnondeterminism-perl strip-nondeterminism 
dh-strip-nondeterminism
Architecture: source
Version: 0.027-1
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Chris Lamb 
Description:
 dh-strip-nondeterminism - file non-deterministic information stripper — 
Debhelper add-on
 libfile-stripnondeterminism-perl - file non-deterministic information stripper 
— Perl module
 strip-nondeterminism - file non-deterministic information stripper — 
stand-alone tool
Closes: 837382
Changes:
 strip-nondeterminism (0.027-1) unstable; urgency=medium
 .
   * Add a File::StripNondeterminism::init method to avoid tzset DRY violation.
 - Also set timezone in tests. (Closes: #837382)
Checksums-Sha1:
 84b853ad1bfca8ad38ebb8fac27badd88befcb88 2393 strip-nondeterminism_0.027-1.dsc
 5c8c87ea9ac3175580bed6f7ce8e4796ba865b72 168676 
strip-nondeterminism_0.027.orig.tar.gz
 a1514d2a6341ba90f7d87f99aa43dbb1cec0aceb 6076 
strip-nondeterminism_0.027-1.debian.tar.xz
Checksums-Sha256:
 187e941d7e9d43dace954b8588637533e1463724c7096def597d49dfe7538039 2393 
strip-nondeterminism_0.027-1.dsc
 d909af98b98cdc3965627012c7d1efcbacc0fbfe2133004bcabca520f3844eef 168676 
strip-nondeterminism_0.027.orig.tar.gz
 6f8015daae0e97d947b112270d9c0099e1f11c0dde1646f4019ff48c3e56aa64 6076 
strip-nondeterminism_0.027-1.debian.tar.xz
Files:
 e706f4aa056030fce242d2d9a67331bb 2393 devel optional 
strip-nondeterminism_0.027-1.dsc
 ad76fb914065e7826daa5cc16c36821a 168676 devel optional 
strip-nondeterminism_0.027.orig.tar.gz
 f48364042e29d2a23c04b76eb8b154f1 6076 devel optional 
strip-nondeterminism_0.027-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX1dZ4AAoJEB6VPifUMR5Ye8gP/iQAM1wBaSeBCraW5jtbFcvG
g8oZc0DtAepDuSQJnVJ0NpeLprf5dR6lDA8pMH265xAW5ki5hwLOHb5rTcmZp8YW
ADQasut2wC6ozxCJvLW2il1iqsORoaCAKjyWoo562NZINIJA0Pz9EWv5z2aFP5GW
yNTxnhnJ936a8tbdedSeqJUW6XU7sAWRzXdRFI4FLx14dBh3ro8dKuaTilxgBuH7
t9IQWVTJWwOx2w612sWNhiFCCJtuj1n8FzUIR7nBTe8dgKUy12C6gytFE5hV163A
CKUrlDFrDrTquoitKF/6LlQeJA/pmK/81ywHVy7iaMZxC3qRgdmg7h/m741zZlbh
Vc9zrAGK9WKzz9MKxRKdChz09AzsnmEG0KU8XCjR0FVfbSLe4Y9jQNnlmcQydQQD
c0szINAgRhk4LDpSs73bz4ZcNHEIff3TjtogCuqZC90iBQNz6EPmmAQMLppZ7kih
JT/tZwrWMDEaVTH4ojNdRuYp7BxCyOZd89FQQCXJ80nyMEzZ4TIlbaMReqrJ7EMM
ouNe7TBv0dJeWKO/n3t6oECyKVY05rV6MfUGpjuw5gCGkEx+hkkFe7CpJhq0BNtZ
DN4F9nMcOVV5n4yU62OfJgNPqj1uilFLyvCOmIvH9lYwFzeNCelgO5OUa5a2Uk+p
cidmkeGA6hyFazBdepMa
=8VQL
-END PGP SIGNATURE End Message ---

Bug#822787: marked as done (quagga: CVE-2016-4049: Missing size check in bgp_dump_routes_func in bgpd/bgp_dump.c allowing DoS)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:23:03 +
with message-id 
and subject line Bug#822787: fixed in quagga 1.0.20160315-2
has caused the Debian Bug report #822787,
regarding quagga: CVE-2016-4049: Missing size check in bgp_dump_routes_func in 
bgpd/bgp_dump.c allowing DoS
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.)


-- 
822787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quagga
Version: 0.99.23.1-1
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for quagga.

CVE-2016-4049[0]:
Missing size check in bgp_dump_routes_func in bgpd/bgp_dump.c allowing DoS

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-4049
[1] https://lists.quagga.net/pipermail/quagga-dev/2016-January/014699.html
[2] https://lists.quagga.net/pipermail/quagga-dev/2016-April/015241.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: quagga
Source-Version: 1.0.20160315-2

We believe that the bug you reported is fixed in the latest version of
quagga, 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.
Hugo Lefeuvre  (supplier of updated quagga 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, 11 Sep 2016 21:37:00 +0200
Source: quagga
Binary: quagga quagga-dbg quagga-doc
Architecture: source amd64 all
Version: 1.0.20160315-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Hugo Lefeuvre 
Description:
 quagga - BGP/OSPF/RIP routing daemon
 quagga-dbg - BGP/OSPF/RIP routing daemon (debug symbols)
 quagga-doc - documentation files for quagga
Closes: 822787 835223
Changes:
 quagga (1.0.20160315-2) unstable; urgency=high
 .
   * QA upload.
   * Run wrap-and-sort.
   * debian/control:
 - Set QA group as maintainer, as Christian orphaned the package (see
   #837358).
 - Bump Standards-Version to 3.9.8.
   * SECURITY:
 - CVE-2016-4049: Missing size check in bgp_dump_routes_func in
   bgpd/bgp_dump.c allowing DoS (Closes: #822787).
 - CVE-2016-4036: World readable sensitive files in /etc/quagga
   (Closes: #835223).
Checksums-Sha1:
 15c0abffd54cf65a5ed1a8d4718f0bff89d10784 2181 quagga_1.0.20160315-2.dsc
 bc6eb71017282a18d7f5986fae54f51d1e90990b 36096 
quagga_1.0.20160315-2.debian.tar.xz
 2d49815d8b42e93171fffabde887eb7aa201bca1 2122804 
quagga-dbg_1.0.20160315-2_amd64.deb
 8e0f5ed4c5fadb418ce9623b47b2149508e3aedc 977248 
quagga-doc_1.0.20160315-2_all.deb
 ad6fac6d6675737c2078c6b0fbe27351e949e2d7 1364846 
quagga_1.0.20160315-2_amd64.deb
Checksums-Sha256:
 c926a904660da820139cc6e13896516a68d62fc1826d698cc776fe47607ef962 2181 
quagga_1.0.20160315-2.dsc
 3884b9e9cbf4da1b214882fcf43a066f294323cb6b9133238d5bb586945d8807 36096 
quagga_1.0.20160315-2.debian.tar.xz
 faff85f2eebea341b34be27864c5882e163d5a3a1a27a18c938834cecd3565c8 2122804 
quagga-dbg_1.0.20160315-2_amd64.deb
 a9332039b6308b17ce8eb8dfd470e0c8fb5108a46366e7463eb3b493444039dc 977248 
quagga-doc_1.0.20160315-2_all.deb
 0b69e8704a75bd8c5c2ef4fc08d2eb1cb6067fb7a31ce6950a573b47303b200b 1364846 
quagga_1.0.20160315-2_amd64.deb
Files:
 25f6651aaec6751863a354874011f8ff 2181 net optional quagga_1.0.20160315-2.dsc
 da754a7a4234bdfa69bc667fbdb7462f 36096 net optional 
quagga_1.0.20160315-2.debian.tar.xz
 d946682fa60a9130882d29a18eafae94 2122804 debug extra 
quagga-dbg_1.0.20160315-2_amd64.deb
 6956843578185d5db80547cc046f3452 977248 net optional 
quagga-doc_1.0.20160315-2_all.deb
 40275e739c338f257fbf4bff6b81b5a3 1364846 net optional 
quagga_1.0.20160315-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJX1bYWAAoJEKyQrD7FJAZe8ykP/imZHwbldTqcbbtR6EmlDZ4R

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

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:23:38 +
with message-id 
and subject line Bug#822021: fixed in scalapack 1.8.0-13
has caused the Debian Bug report #822021,
regarding scalapack: 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.)


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

Hi,

The package scalapack 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 scalapack builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to scalapack 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, scalapack 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: scalapack
Source-Version: 1.8.0-13

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Sep 2016 23:48:13 +0200
Source: scalapack
Binary: libscalapack-openmpi1 libscalapack-mpich1 libscalapack-mpi-dev 
scalapack-mpi-test libscalapack-pvm1 libscalapack-pvm-dev scalapack-pvm-test 
scalapack-test-common
Architecture: source amd64 all
Version: 1.8.0-13
Distribution: unstable
Urgency: medium
Maintainer: Muammar El Khatib 
Changed-By: Muammar El Khatib 
Description:
 libscalapack-mpi-dev - Scalable Linear Algebra Package - Dev. files for MPICH
 libscalapack-mpich1 - Scalable Linear Algebra Package - Shared libs. for MPICH
 libscalapack-openmpi1 - Scalable Linear Algebra Package - Shared libs. for 
OpenMPI
 libscalapack-pvm-dev - Scalable Linear Algebra Package - Dev. files for PVM
 libscalapack-pvm1 - Scalable Linear Algebra Package - Shared libs. for PVM
 scalapack-mpi-test - Scalable Linear Algebra Package - Test files for MPICH
 scalapack-pvm-test - Scalable Linear Algebra Package - Test files for PVM
 scalapack-test-common - Test data for ScaLAPACK testers
Closes: 822021 834182
Changes:
 scalapack (1.8.0-13) unstable; urgency=medium
 .
   * Added missing build-{arch,indep} targets. Thanks to Santiago Vila for
 providing a patch. Closes: #822021.
   * hppa architecture switched to openmpi. Closes: #834182.
Checksums-Sha1:
 8e5824f967543040efa544c93c199968d05c9a8e 2771 scalapack_1.8.0-13.dsc
 fb2e5224414840df64ddc903f67da60f352d8998 13852 scalapack_1.8.0-13.debian.tar.xz
 1052adfbc9f92aa9aa2354a8c7930c0c41951d99 2142566 
libscalapack-mpi-dev_1.8.0-13_amd64.deb
 a7714aa8e16c9cf3b3c809443c2a8bdbae60934b 19836 
libscalapack-openmpi1-dbgsym_1.8.0-13_amd64.deb
 24ebe6c4cb27ed91f0834f7104400954a321b8fd 2209130 
libscalapack-openmpi1_1.8.0-13_amd64.deb
 11baeca367ccb83a5350ac7c9eee334cb5e80ab5 2142742 
libscalapack-pvm-dev_1.8.0-13_amd64.deb
 abc86d208a7040172f6448c8ccb83b11487fee52 19896 
libscalapack-pvm1-dbgsym_1.8.0-13_amd64.deb
 45d66c02b8747a8d5e5e63d21737a0ed182abab6 2207482 
libscalapack-pvm1_1.8.0-13_amd64.deb
 cec2d858c7a94ce88f84510b80b7597e74196788 70850 
scalapack-mpi-test-dbgsym_1.8.0-13_amd64.deb
 bceb6f9aedb3ffd48d7cf15d5512136c7b7b9284 1285052 
scalapack-mpi-test_1.8.0-13_amd64.deb
 162393f771afbb3c461f973454e5ce25a722efec 70730 
scalapack-pvm-test-dbgsym_1.8.0-13_amd64.deb
 103381ef1404e3ea99a56540d3d643ed84934b25 1287798 
scalapack-pvm-test_1.8.0-13_amd64.deb
 

Bug#836646: marked as done (ploop: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:21:55 +
with message-id 
and subject line Bug#836646: fixed in ploop 1.15-2
has caused the Debian Bug report #836646,
regarding ploop: please drop the build dependency on hardening-wrapper
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.)


-- 
836646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ploop
Version: 1.15-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: ploop
Source-Version: 1.15-2

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

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated ploop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 22:01:27 +0200
Source: ploop
Binary: ploop libploop-dev libploop1
Architecture: source amd64
Version: 1.15-2
Distribution: unstable
Urgency: high
Maintainer: Ola Lundqvist 
Changed-By: Ola Lundqvist 
Description:
 libploop-dev - ploop API development library
 libploop1  - ploop API library
 ploop  - tools to work with ploop devices and images
Closes: 836646
Changes:
 ploop (1.15-2) unstable; urgency=high
 .
   * Removed depdendency on hardening wrapper. Closes: #836646.
   * Removed vcs listing from control file as that is for upstream vcs.
Checksums-Sha1:
 69ee8b80ca38c3feec4bb29b4ddfbc76c11fee3f 1867 ploop_1.15-2.dsc
 9a75bb5db558a91c2ae202d46fffd26e6216454a 3852 ploop_1.15-2.debian.tar.xz
 2428a732a362964604acd776d2f8ed38b3308cb5 32386 ploop_1.15-2_amd64.deb
 3e446ea292f88337341fa8ac9d8b5fd8417603c8 113832 libploop-dev_1.15-2_amd64.deb
 a981617217a46671fae39178842e9668a8b7cf90 91068 libploop1_1.15-2_amd64.deb
Checksums-Sha256:
 9b6b5f2e304067e66cbcc2085042403cbb817a97c3972aa468d53f3db89527d7 1867 
ploop_1.15-2.dsc
 c8f58d645fc161d662b288693068af68b9fa60ef0db42f42198a98464f1d11b8 3852 
ploop_1.15-2.debian.tar.xz
 160c3c8ba44fedf9bc27309bf62f2c5c6a76776506a5b00e40361078cd453a84 32386 
ploop_1.15-2_amd64.deb
 2aa0815ab50a5d05b44a95b8a86124bc559dbcf185b740904252c8edceeea44b 113832 
libploop-dev_1.15-2_amd64.deb
 6ff452859abc620b77d7242b3f1095f852f81f20f26da0f41b456d6c8236fd50 91068 
libploop1_1.15-2_amd64.deb
Files:
 fb05b48933d10ff41e6fd1f4821a265f 1867 libs extra ploop_1.15-2.dsc
 1f46cc3220218863b11b36148fc143aa 3852 libs extra ploop_1.15-2.debian.tar.xz
 c9a667e39437b9ca36a8be0adf141e34 32386 libs extra ploop_1.15-2_amd64.deb
 c23605ce69da1e576b25d7b745d0a2b3 113832 libdevel extra 
libploop-dev_1.15-2_amd64.deb
 3497692730160bb628795c763c2c27de 91068 libs extra libploop1_1.15-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX1bjnAAoJEF6Q3PqUJodvUj4P/2mIYrJITZoV7ZRRCH0qD1xq
Q4Y8397aFDD8/Ziq8Vam+qzH3VU16ur3iA9M0gQkNesmB5I5+MfSVvVPFs4jXvtJ
1dGM0UdpJq9e0RkXSqpFW6trKznZoPlbdim7d09aVzvrXhZdnT/8rUEqH4Dq94my
6FWdYCPsu3L+T2Pd3tKWIAXpdQQyFo7l2c7d26WMyuepVf+G570J60itik3QFFPh
AaLzkAFFNFNWkf9/1zHtveYCNCL67yDuNLnIxRoA0XwRjPD9QhRVeqtBp7UCEa+C
UsrBIcuRloOMjSp6L8PebRYY6qCbfhMPFVHqiDTkuwdoDpPO5P0fgax6pf5ac6tq
h1GPTNCUksbbirsfVbVI4uf/Oz6rbs8EwWIHUhZOU4j5NkJklcr0/DDtvHSiZfo4
6Xd5kLMY5e699lRtNJWHLULtPjNZk0jdV/SVq248KM/j/vA0zzqs8Wwo7gHVfgzx
lSbgeQNXQUzM6YcSOKapt0wolTXmG9BBCdG4bALYNW2W3mRIp9nS6zNNw7ygLRte
our/lKpCo8hR5jlRmuL0FdjNzNSESpDokr734N2ssdehJiRInuWNXtpC1qbQfQeW

Bug#836824: marked as done (python-pyotp: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 22:22:22 +
with message-id 
and subject line Bug#836824: fixed in python-pyotp 2.2.1-1
has caused the Debian Bug report #836824,
regarding python-pyotp: FTBFS in testing (failing tests)
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.)


-- 
836824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pyotp
Version: 2.1.1-2
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 --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/pyotp
copying src/pyotp/utils.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyotp
copying src/pyotp/hotp.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyotp
copying src/pyotp/otp.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyotp
copying src/pyotp/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyotp
copying src/pyotp/totp.py -> /<>/.pybuild/pythonX.Y_2.7/build/pyotp
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/pyotp
copying src/pyotp/utils.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyotp
copying src/pyotp/hotp.py -> /<>/.pybuild/pythonX.Y_3.5/build/pyotp
copying src/pyotp/otp.py -> /<>/.pybuild/pythonX.Y_3.5/build/pyotp
copying src/pyotp/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyotp
copying src/pyotp/totp.py -> /<>/.pybuild/pythonX.Y_3.5/build/pyotp
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m unittest discover -v -s /<>/ -p "test.py"
test_counter_offset (test.CounterOffsetTest) ... ok
test_match_rfc (test.HOTPExampleValuesFromTheRFC) ... ok
test_other_secret (test.HOTPExampleValuesFromTheRFC) ... ok
test_provisioning_uri (test.HOTPExampleValuesFromTheRFC) ... ok
test_verify_otp_reuse (test.HOTPExampleValuesFromTheRFC) ... ok
test_comparisons (test.StringComparisonTest) ... ok
test_fullwidth_input (test.StringComparisonTest) ... ok
test_match_google_authenticator_output (test.TOTPExampleValuesFromTheRFC) ... ok
test_match_rfc (test.TOTPExampleValuesFromTheRFC) ... FAIL
test_match_rfc_digit_length (test.TOTPExampleValuesFromTheRFC) ... FAIL
test_provisioning_uri (test.TOTPExampleValuesFromTheRFC) ... ok
test_random_key_generation (test.TOTPExampleValuesFromTheRFC) ... ok
test_validate_totp (test.TOTPExampleValuesFromTheRFC) ... ok
test_validate_totp_with_digit_length (test.TOTPExampleValuesFromTheRFC) ... ok
test_valid_window (test.ValidWindowTest) ... ok

==
FAIL: test_match_rfc (test.TOTPExampleValuesFromTheRFC)
--
Traceback (most recent call last):
  File "/<>/test.py", line 102, in test_match_rfc
self.assertEqual(value, str(code), msg)
AssertionError: 25693528 != 38618901 (sha512, time=20)

==
FAIL: test_match_rfc_digit_length (test.TOTPExampleValuesFromTheRFC)
--
Traceback (most recent call last):
  File "/<>/test.py", line 108, in test_match_rfc_digit_length
self.assertEqual(totp.at(20), '279037')
AssertionError: '573438' != u'279037'

--
Ran 15 tests in 0.004s

FAILED (failures=2)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover 
-v -s {dir}/ -p "test.py"
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

Bug#837477: xbacklight doesn't do anything at all

[nickpontillo]

Package: xbacklight
Version: 1.2.1-1
Followup-For: Bug #837477

Disregard this bug report. It is actually the same bug as this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833508#20



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

Kernel: Linux 4.6.0-1-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 xbacklight depends on:
ii  libc6  2.23-5
ii  libxcb-randr0  1.11.1-1.1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.11.1-1.1

xbacklight recommends no packages.

xbacklight suggests no packages.

-- no debconf information

Bug#837477: xbacklight doesn't do anything at all

[nickpontillo]

Package: xbacklight
Version: 1.2.1-1
Followup-For: Bug #837477

Disregard my bug report. I think it is actually the same bug as this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833508#20

The workaround found by o...@bluemonk.de in that thread (which works for me) is
to put:

Section "Device"
Identifier "Intel"
Driver "intel"
#   Option "AccelMethod" "uxa"
EndSection

in /etc/X11/xorg.conf



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

Kernel: Linux 4.6.0-1-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 xbacklight depends on:
ii  libc6  2.23-5
ii  libxcb-randr0  1.11.1-1.1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.11.1-1.1

xbacklight recommends no packages.

xbacklight suggests no packages.

-- no debconf information

Bug#837382: strip-nondeterminism: Tests fail when TZ != "UTC"

[Chris Lamb]

tags 837382 + pending
thanks

See:

  
https://anonscm.debian.org/git/reproducible/strip-nondeterminism.git/commit/?h=master=1303f18fba0134a01be7cc384afcf514b5fbd936


Regards,

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

Processed: Re: strip-nondeterminism: Tests fail when TZ != "UTC"

[Debian Bug Tracking System]

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

> tags 837382 + pending
Bug #837382 [src:strip-nondeterminism] strip-nondeterminism: Tests fail when TZ 
!= "UTC"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837477: xbacklight doesn't do anything at all

[nickpontillo]

Package: xbacklight
Version: 1.2.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

In Debian Testing, none of the commands or options with xbacklight do anything
or give any output whatsoever, EXCEPT if I type an invalid command, then it
gives me the help stuff about basic usage:

"""
usage: xbacklight [options]
  where options are:
  -display  or -d 
  -help
  -set  or = 
  -inc  or + 
  -dec  or - 
  -get
  -time 
  -steps 
"""

but it doesn't do anything if I actually use one of those valid commands.

 I think I have this bug:
https://bugs.launchpad.net/ubuntu/+source/xbacklight/+bug/1060431

I am on an acer c720 chromebook, if that matters.

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

Kernel: Linux 4.6.0-1-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 xbacklight depends on:
ii  libc6  2.23-5
ii  libxcb-randr0  1.11.1-1.1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.11.1-1.1

xbacklight recommends no packages.

xbacklight suggests no packages.

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 833501 837461
Bug #833501 {Done: Michael Gilbert } [chromium] Aw snap 
while using Facebook
Bug #833506 {Done: Michael Gilbert } [chromium] chromium: 
Crashes when browsing Google Maps
Bug #833524 {Done: Michael Gilbert } [chromium] chromium: 
Aw Snap! after update to new in sid / even when purged and installed as clean
Bug #833542 {Done: Michael Gilbert } [chromium] chromium: 
Crashes all the time after last update
Bug #837461 [chromium] chromium: aw snap
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions chromium-browser/53.0.2785.92-3 and 
chromium-browser/52.0.2743.116-2.
Marked as found in versions chromium-browser/52.0.2743.116-1.
Added tag(s) upstream and confirmed.
Bug #833506 {Done: Michael Gilbert } [chromium] chromium: 
Crashes when browsing Google Maps
Bug #833524 {Done: Michael Gilbert } [chromium] chromium: 
Aw Snap! after update to new in sid / even when purged and installed as clean
Bug #833542 {Done: Michael Gilbert } [chromium] chromium: 
Crashes all the time after last update
Merged 833501 833506 833524 833542 837461
> thanks
Stopping processing here.

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

Processed: block 788513 with 832451

[Debian Bug Tracking System]

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

> block 788513 with 832451
Bug #788513 [src:aufs-tools] aufs-tools: FTBFS: linux/aufs_type.h: No such file 
or directory
788513 was not blocked by any bugs.
788513 was not blocking any bugs.
Added blocking bug(s) of 788513: 832451
> thanks
Stopping processing here.

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

Bug#836824: python-pyotp: FTBFS in testing (failing tests)

[Hugo Lefeuvre]

> Please try to improve the changelog a little bit.

Fixed. Thanks for the hint.

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature

Bug#837268: bzr: FTBFS: Tests failures

[Santiago Vila]

On Sun, Sep 11, 2016 at 09:53:34PM +0200, Lucas Nussbaum wrote:
> Hi,
> 
> On 11/09/16 at 12:33 +0200, Santiago Vila wrote:
> > > Tags: stretch sid
> > 
> > This bug should not happen in stretch (yet) because diffutils 3.5
> > has not entered stretch (yet), are you sure it's correct to tag
> > it stretch in those cases?
> 
> What 'stretch sid' really means is "this doesn't affect stable". There's
> no better way to express that.

Ah, ok.

> Even if the bug is tagged "stretch sid", normal BTS version-tracking is
> still applied, so if the affected version isn't in stretch, it won't
> be seen as affecting stretch.

That's precisely the little problem I wanted to point out:

The "affected" version (bzr 2.7.0+bzr6619-1) was both in stretch and sid,
but the bug could not be reproduced in stretch because diffutils 3.5
(the package triggering this bug) was not in stretch yet.

How would I ask the BTS if this was a bug in stretch?

Assuming for a while that diffutils 3.5 did not enter testing yet,
would the BTS give the correct answer?

I agree that this is a minor issue, I just wanted to know if this is
something which has been raised before or not, and how it would be
solved.

For the purposes of excluding "stable", using "stretch sid" makes
every sense, of course.

Thanks.

Bug#836824: python-pyotp: FTBFS in testing (failing tests)

[Santiago Vila]

On Fri, Sep 09, 2016 at 09:07:01PM +0200, Hugo Lefeuvre wrote:
> Hi Santiago,
> 
> It looks like packaging the new upstream release fixes the issue.
> If you want, you can try to build the version on the repository[0]
> before I upload it.
> 
> Regards,
>  Hugo
> 
> [0] https://anonscm.debian.org/git/python-modules/packages/python-pyotp.git/

Sorry for the late reply.

Please try to improve the changelog a little bit. I see:

 * New upstream release (Closes: #836824).

While this version may certaily fix the bug I reported, anybody
reading that would think that the bug was about packaing a new
upstream release.

It is usually better to write a description (even if it's short)
of the bug being fixed.

 * Fix failing tests. Closes: #836824.

Thanks.

Bug#836660: vzctl: please drop the build dependency on hardening-wrapper

[Ola Lundqvist]

Hi

Correction uploaded now. Also for vzctl and ploop.

// Ola

On Wed, Sep 7, 2016 at 9:25 PM, Ola Lundqvist  wrote:
> Hi
>
> That is very good news!
>
> Sent from a phone
>
>
> Den 7 sep 2016 21:00 skrev "Moritz Mühlenhoff" :
>>
>> On Sun, Sep 04, 2016 at 01:17:01PM +, Matthias Klose wrote:
>> > Package: vzctl
>> > Version: 4.9.4-2
>> > Severity: important
>> > Tags: sid stretch
>> > User: debian-...@lists.debian.org
>> > Usertags: hardening-wrapper
>> >
>> > This package builds using the hardening-wrapper package, which
>> > is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.
>> >
>> > Please consider dropping the build dependency of hardening-wrapper
>> > and use the DEB_BUILD_MAINT_OPTIONS settings.
>> >
>> > The goal is to remove hardening-wrapper for the stretch release.
>> > Discussion about the removal is tracked in
>> > https://bugs.debian.org/836162
>> >
>> > The severity of this report is likely to be raised before the release,
>> > so that the hardening-wrapper package can be removed for the release.
>>
>> The build dep on hardening-wrapper is spurious, the rules file
>> already passes hardened build flags via dh/compat 9 and I've
>> confirmed that simply removing hardening-wrapper still
>> results in a hardened build.
>>
>> Cheers,
>> Moritz

Processed: Bug#836824 marked as pending

[Debian Bug Tracking System]

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

> tag 836824 pending
Bug #836824 [src:python-pyotp] python-pyotp: FTBFS in testing (failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#836824: marked as pending

[Hugo Lefeuvre]

tag 836824 pending
thanks

Hello,

Bug #836824 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=python-modules/packages/python-pyotp.git;a=commitdiff;h=43aee16

---
commit 43aee16edc28ebbe90922b6ac67b274f168a5f74
Author: Hugo Lefeuvre 
Date:   Sun Sep 11 22:16:04 2016 +0200

Close #836824.

diff --git a/debian/changelog b/debian/changelog
index 9cf7a1b..a6536ef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 python-pyotp (2.2.1-1) unstable; urgency=medium
 
-  * New upstream release.
+  * New upstream release (Closes: #836824).
   * Remove debian/patches/timedelta-ingest-timestamp.patch: Integrated in new
 upstream version.
   * Remove useless PYBUILD_TEST_ARGS line in debian/rules.

Bug#837130: marked as done (vim package cannot be installed because of missing dependency)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 20:00:11 +
with message-id 
and subject line Bug#837130: fixed in vim 2:7.4.2347-1
has caused the Debian Bug report #837130,
regarding vim package cannot be installed because of missing dependency
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.)


-- 
837130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vim
Version: 2:7.4.2330-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * I upgraded my packages via apt-get update/dist-upgrade as usual. vim got 
uninstalled because a new vim package was released but one of its dependencies 
could not be installed due to not being available in the repos: vim-runtime (= 
2:7.4.2330-1).

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

   * What was the outcome of this action?
   * vim does not exist on my system anymore, which is a tool I use constantly.

   * What outcome did you expect instead?
   * I expected a newer version of vim to be installed, not to be removed :)

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


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

Kernel: Linux 4.7.0-1-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)
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:7.4.2347-1

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated vim 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, 10 Sep 2016 23:35:08 -0400
Source: vim
Binary: vim-common vim-gui-common vim-runtime vim-doc vim-tiny vim vim-gtk 
vim-gtk3 vim-nox vim-athena vim-gnome xxd
Architecture: source amd64 all
Version: 2:7.4.2347-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Description:
 vim- Vi IMproved - enhanced vi editor
 vim-athena - Vi IMproved - enhanced vi editor - with Athena GUI
 vim-common - Vi IMproved - Common files
 vim-doc- Vi IMproved - HTML documentation
 vim-gnome  - Vi IMproved - enhanced vi editor (dummy package)
 vim-gtk- Vi IMproved - enhanced vi editor - with GTK2 GUI
 vim-gtk3   - Vi IMproved - enhanced vi editor - with GTK3 GUI
 vim-gui-common - Vi IMproved - Common GUI files
 vim-nox- Vi IMproved - enhanced vi editor - with scripting languages suppo
 vim-runtime - Vi IMproved - Runtime files
 vim-tiny   - Vi IMproved - enhanced vi editor - compact version
 xxd- tool to make (or reverse) a hex dump
Closes: 837130
Changes:
 vim (2:7.4.2347-1) unstable; urgency=medium
 .
   [ upstream ]
   * Fix test failure due to relying on modelines.  (Closes: #837130)
 .
   [ James McCoy ]
   * Move xxd into its own package.  This allows other packages to express a
 relationship on xxd itself, rather than vim-common, and also enables
 turning vim-common into an Arch: all package.
   * Remove dpkg-dev Build-Depends, since the version is satisifed prior to
 oldstable.
Checksums-Sha1:
 fca936661c1f702c2ae669511b7c9258300ff779 2932 vim_7.4.2347-1.dsc
 40b41dfee812aebc555301d85e8481ab4bcd8672 12914916 vim_7.4.2347.orig.tar.gz
 3ee013be933158489e3b85be1a5e4b36e19d10d5 189864 vim_7.4.2347-1.debian.tar.xz
 5f1a8d831d53fd1a1e6e148bb8fabd571f49615a 3786356 
vim-athena-dbgsym_7.4.2347-1_amd64.deb
 4420a41e500f9e1dcb72f3d6284024f7673e2bbf 1248240 
vim-athena_7.4.2347-1_amd64.deb
 cf685913bae0da76077fba0698c6802559146e99 204006 vim-common_7.4.2347-1_all.deb
 d0fb647416c3ede6fe99da3cf706e34ebc7860f8 2931426 

Bug#837217: marked as done (vim-runtime (= 2:7.4.2330-1) does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 20:00:11 +
with message-id 
and subject line Bug#837130: fixed in vim 2:7.4.2347-1
has caused the Debian Bug report #837130,
regarding vim-runtime (= 2:7.4.2330-1) does not exist
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.)


-- 
837130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-runtime
Version: 2:7.4.1829-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

$ apt dist-upgrade

   * What was the outcome of this action?

> Remove: vim:amd64 (2:7.4.1829-1)

Trying to install vim again ends here:

vim : Depends: vim-runtime (= 2:7.4.2330-1) but 2:7.4.1829-1 is to be installed

So, please place a copy of vim-runtime=2:7.4.2330-1 on your download servers.
:)

Kind regards,
Aiko

PS.: reportbug spawns mutt and mutt fires up vim. No no. :)



-- 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/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

vim-runtime depends on no packages.

Versions of packages vim-runtime recommends:
ii  vim-tiny  2:7.4.2330-1

vim-runtime suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:7.4.2347-1

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated vim 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, 10 Sep 2016 23:35:08 -0400
Source: vim
Binary: vim-common vim-gui-common vim-runtime vim-doc vim-tiny vim vim-gtk 
vim-gtk3 vim-nox vim-athena vim-gnome xxd
Architecture: source amd64 all
Version: 2:7.4.2347-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Description:
 vim- Vi IMproved - enhanced vi editor
 vim-athena - Vi IMproved - enhanced vi editor - with Athena GUI
 vim-common - Vi IMproved - Common files
 vim-doc- Vi IMproved - HTML documentation
 vim-gnome  - Vi IMproved - enhanced vi editor (dummy package)
 vim-gtk- Vi IMproved - enhanced vi editor - with GTK2 GUI
 vim-gtk3   - Vi IMproved - enhanced vi editor - with GTK3 GUI
 vim-gui-common - Vi IMproved - Common GUI files
 vim-nox- Vi IMproved - enhanced vi editor - with scripting languages suppo
 vim-runtime - Vi IMproved - Runtime files
 vim-tiny   - Vi IMproved - enhanced vi editor - compact version
 xxd- tool to make (or reverse) a hex dump
Closes: 837130
Changes:
 vim (2:7.4.2347-1) unstable; urgency=medium
 .
   [ upstream ]
   * Fix test failure due to relying on modelines.  (Closes: #837130)
 .
   [ James McCoy ]
   * Move xxd into its own package.  This allows other packages to express a
 relationship on xxd itself, rather than vim-common, and also enables
 turning vim-common into an Arch: all package.
   * Remove dpkg-dev Build-Depends, since the version is satisifed prior to
 oldstable.
Checksums-Sha1:
 fca936661c1f702c2ae669511b7c9258300ff779 2932 vim_7.4.2347-1.dsc
 40b41dfee812aebc555301d85e8481ab4bcd8672 12914916 vim_7.4.2347.orig.tar.gz
 3ee013be933158489e3b85be1a5e4b36e19d10d5 189864 vim_7.4.2347-1.debian.tar.xz
 5f1a8d831d53fd1a1e6e148bb8fabd571f49615a 3786356 
vim-athena-dbgsym_7.4.2347-1_amd64.deb
 4420a41e500f9e1dcb72f3d6284024f7673e2bbf 1248240 
vim-athena_7.4.2347-1_amd64.deb
 cf685913bae0da76077fba0698c6802559146e99 204006 vim-common_7.4.2347-1_all.deb
 d0fb647416c3ede6fe99da3cf706e34ebc7860f8 2931426 
vim-dbgsym_7.4.2347-1_amd64.deb
 d436b761ad083ba768e57fc795e0ad6500aff988 1956708 vim-doc_7.4.2347-1_all.deb
 a81694d5bc0c51512a06cf4d3cd2a6493f17f265 145814 

Bug#837215: marked as done (vim-runtime (= 2:7.4.2330-1) does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 20:00:11 +
with message-id 
and subject line Bug#837130: fixed in vim 2:7.4.2347-1
has caused the Debian Bug report #837130,
regarding vim-runtime (= 2:7.4.2330-1) does not exist
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.)


-- 
837130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-runtime
Version: 2:7.4.1829-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

$ apt dist-upgrade

   * What was the outcome of this action?

> Remove: vim:amd64 (2:7.4.1829-1)

Trying to install vim again ends here:

vim : Depends: vim-runtime (= 2:7.4.2330-1) but 2:7.4.1829-1 is to be installed

So, please place a copy of vim-runtime=2:7.4.2330-1 on your download servers.
:)

Kind regards,
Aiko

PS.: reportbug spawns mutt and mutt fires up vim. No no. :)



-- 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/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

vim-runtime depends on no packages.

Versions of packages vim-runtime recommends:
ii  vim-tiny  2:7.4.2330-1

vim-runtime suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:7.4.2347-1

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated vim 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, 10 Sep 2016 23:35:08 -0400
Source: vim
Binary: vim-common vim-gui-common vim-runtime vim-doc vim-tiny vim vim-gtk 
vim-gtk3 vim-nox vim-athena vim-gnome xxd
Architecture: source amd64 all
Version: 2:7.4.2347-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Description:
 vim- Vi IMproved - enhanced vi editor
 vim-athena - Vi IMproved - enhanced vi editor - with Athena GUI
 vim-common - Vi IMproved - Common files
 vim-doc- Vi IMproved - HTML documentation
 vim-gnome  - Vi IMproved - enhanced vi editor (dummy package)
 vim-gtk- Vi IMproved - enhanced vi editor - with GTK2 GUI
 vim-gtk3   - Vi IMproved - enhanced vi editor - with GTK3 GUI
 vim-gui-common - Vi IMproved - Common GUI files
 vim-nox- Vi IMproved - enhanced vi editor - with scripting languages suppo
 vim-runtime - Vi IMproved - Runtime files
 vim-tiny   - Vi IMproved - enhanced vi editor - compact version
 xxd- tool to make (or reverse) a hex dump
Closes: 837130
Changes:
 vim (2:7.4.2347-1) unstable; urgency=medium
 .
   [ upstream ]
   * Fix test failure due to relying on modelines.  (Closes: #837130)
 .
   [ James McCoy ]
   * Move xxd into its own package.  This allows other packages to express a
 relationship on xxd itself, rather than vim-common, and also enables
 turning vim-common into an Arch: all package.
   * Remove dpkg-dev Build-Depends, since the version is satisifed prior to
 oldstable.
Checksums-Sha1:
 fca936661c1f702c2ae669511b7c9258300ff779 2932 vim_7.4.2347-1.dsc
 40b41dfee812aebc555301d85e8481ab4bcd8672 12914916 vim_7.4.2347.orig.tar.gz
 3ee013be933158489e3b85be1a5e4b36e19d10d5 189864 vim_7.4.2347-1.debian.tar.xz
 5f1a8d831d53fd1a1e6e148bb8fabd571f49615a 3786356 
vim-athena-dbgsym_7.4.2347-1_amd64.deb
 4420a41e500f9e1dcb72f3d6284024f7673e2bbf 1248240 
vim-athena_7.4.2347-1_amd64.deb
 cf685913bae0da76077fba0698c6802559146e99 204006 vim-common_7.4.2347-1_all.deb
 d0fb647416c3ede6fe99da3cf706e34ebc7860f8 2931426 
vim-dbgsym_7.4.2347-1_amd64.deb
 d436b761ad083ba768e57fc795e0ad6500aff988 1956708 vim-doc_7.4.2347-1_all.deb
 a81694d5bc0c51512a06cf4d3cd2a6493f17f265 145814 

Bug#837268: bzr: FTBFS: Tests failures

[Lucas Nussbaum]

Hi,

On 11/09/16 at 12:33 +0200, Santiago Vila wrote:
> > Tags: stretch sid
> 
> This bug should not happen in stretch (yet) because diffutils 3.5
> has not entered stretch (yet), are you sure it's correct to tag
> it stretch in those cases?

What 'stretch sid' really means is "this doesn't affect stable". There's
no better way to express that.

Even if the bug is tagged "stretch sid", normal BTS version-tracking is
still applied, so if the affected version isn't in stretch, it won't
be seen as affecting stretch.

Lucas

Bug#837468: csoundqt: FTBFS: Project ERROR: A valid csound library was not found.

[Chris Lamb]

Source: csoundqt
Version: 0.9.2.1-3
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,

csoundqt fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../155-libdouble-conversion1_2.0.1-3_amd64.deb ...
  Unpacking libdouble-conversion1:amd64 (2.0.1-3) ...
  Selecting previously unselected package libqt5qml5:amd64.
  Preparing to unpack .../156-libqt5qml5_5.6.1-7_amd64.deb ...
  Unpacking libqt5qml5:amd64 (5.6.1-7) ...
  Selecting previously unselected package libqt5quick5:amd64.
  Preparing to unpack .../157-libqt5quick5_5.6.1-7_amd64.deb ...
  Unpacking libqt5quick5:amd64 (5.6.1-7) ...
  Selecting previously unselected package libqt5quickparticles5:amd64.
  Preparing to unpack .../158-libqt5quickparticles5_5.6.1-7_amd64.deb ...
  Unpacking libqt5quickparticles5:amd64 (5.6.1-7) ...
  Selecting previously unselected package libqt5quicktest5:amd64.
  Preparing to unpack .../159-libqt5quicktest5_5.6.1-7_amd64.deb ...
  Unpacking libqt5quicktest5:amd64 (5.6.1-7) ...
  Selecting previously unselected package libqt5quickwidgets5:amd64.
  Preparing to unpack .../160-libqt5quickwidgets5_5.6.1-7_amd64.deb ...
  Unpacking libqt5quickwidgets5:amd64 (5.6.1-7) ...
  Selecting previously unselected package qt5-qmltooling-plugins:amd64.
  Preparing to unpack .../161-qt5-qmltooling-plugins_5.6.1-7_amd64.deb ...
  Unpacking qt5-qmltooling-plugins:amd64 (5.6.1-7) ...
  Selecting previously unselected package qtdeclarative5-dev:amd64.
  Preparing to unpack .../162-qtdeclarative5-dev_5.6.1-7_amd64.deb ...
  Unpacking qtdeclarative5-dev:amd64 (5.6.1-7) ...
  Setting up cdbs (0.4.146) ...
  Setting up x11proto-dri2-dev (2.8-2) ...
  Setting up libasyncns0:amd64 (0.8-6) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libwacom-common (0.19-1) ...
  Setting up libdouble-conversion1:amd64 (2.0.1-3) ...
  Setting up libevdev2:amd64 (1.5.4+dfsg-1) ...
  Setting up libpng16-16:amd64 (1.6.25-1) ...
  Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
  Setting up fonts-dejavu-core (2.37-1) ...
  Setting up libjson-c3:amd64 (0.12.1-1) ...
  Setting up libasound2-data (1.1.2-1) ...
  Setting up libxshmfence1:amd64 (1.2-1) ...
  Setting up xorg-sgml-doctools (1:1.11-1) ...
  Setting up libwayland-client0:amd64 (1.11.0-2) ...
  Setting up xkb-data (2.17-1) ...
  Setting up qtchooser (58-gfab25f1-1) ...
  Setting up libproxy1v5:amd64 (0.4.11-5) ...
  Setting up x11proto-xf86vidmode-dev (2.3.1-2) ...
  Setting up x11proto-kb-dev (1.0.7-1) ...
  Setting up libglapi-mesa:amd64 (12.0.2-1) ...
  Setting up libinput-bin (1.4.1-1) ...
  Setting up ucf (3.0036) ...
  Setting up libopus0:amd64 (1.1.2-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libasound2:amd64 (1.1.2-1) ...
  Setting up libdrm2:amd64 (2.4.70-1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libogg0:amd64 (1.3.2-1) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up csound-data (1:6.07.0~dfsg-3) ...
  Processing triggers for libc-bin (2.24-2) ...
  Processing triggers for udev (231-5) ...
  Setting up libportmidi0 (1:184-2.2) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Processing triggers for systemd (231-5) ...
  Setting up libpython2.7:amd64 (2.7.12-3) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libxkbcommon0:amd64 (0.6.1-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up liblua5.1-0:amd64 (5.1.5-8.1) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-2) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up liblo7:amd64 (0.28-5) ...
  Setting up libsamplerate0:amd64 (0.1.8-8) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.10-1) ...
  Setting up libwrap0:amd64 (7.6.q-25) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libwacom2:amd64 (0.19-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.70-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up libgbm1:amd64 (12.0.2-1) 

Bug#834683: fixed in mini-buildd 1.0.17

[Santiago Vila]

On Sun, Sep 11, 2016 at 07:40:31PM +0200, Stephan Sürken wrote:

> > The error message:
> (...)
> > suggests to me that there is not enough entropy to generate a key.
> 
> If entropy actually is the problem, it should have always been there
> for all 1.0.x versions (having that doctest).

Well, maybe the problem has always been there.

Maybe official autobuilders have a lot of entropy and we have never
found the problem there, but IMHO we should not take that for granted
in the general case.

> > This time I only tried to build it once, but since the problem was
> > not
> > supposed to always happen, it is probably correct to say that the
> > FTBFS-randomness has not been eliminated.
>
> Ok, agree, this does add some randomness [which I usually mitigate
> running something like haveged on the builder host].> I guess this
> generally means automated tests depending on some entropy must be
> avoided?

If they make the build to fail, or they make the build to take an
unreasonable amount of time, yes, I would think so.

But I really don't know. A quick search on gnupg and /dev/random
led me to the "haveged" package you mention.

This is the kind of "entropy helper" package I believed it "had" to exist,
but I have never used any of them really.

Would be possible to have haveged as a build-dependency of this
package so that it works automatically and avoids the problem in a
generic way for every kind of autobuilder trying to build the package?

Maybe we should ask dkg and the other people maintaining gnupg about
what it's usually done in cases like this (package needing a lot of
entropy in its build system).

I'm Cc:ing them.

Thanks.

Bug#833573: [Monotone-debian] Bug#833573: monotone: FTBFS on mipsel (Error: value of 0200000000002210 too large for field of 4 bytes at 0000000000015d15)

[Markus Wanner]

Control: tags -1 + unreproducible moreinfo
Control: severity -1 normal

On 06.08.2016 10:56, Julien Cristau wrote:
> the latest monotone security upload failed to build on mipsel

Thanks for your report. However, I could not reproduce this failure on
eller.debian.org (a porter machine, Cavium Octeon III according to cpuinfo).

Is this reproducible? Unfortunately, I don't have access to a Loongson
3A processor, which mipsel-aql-01.debian.org seems to be.

Given this failure first occurred after a security update, which
certainly didn't change the failing source file test/unit/tests/paths.cc
in any way, I strongly suspect this is related to the build machine.

Kind Regards

Markus Wanner




signature.asc
Description: OpenPGP digital signature

Processed: Re: [Monotone-debian] Bug#833573: monotone: FTBFS on mipsel (Error: value of 0200000000002210 too large for field of 4 bytes at 0000000000015d15)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible moreinfo
Bug #833573 [src:monotone] monotone: FTBFS on mipsel (Error: value of 
02002210 too large for field of 4 bytes at 00015d15)
Added tag(s) moreinfo and unreproducible.
> severity -1 normal
Bug #833573 [src:monotone] monotone: FTBFS on mipsel (Error: value of 
02002210 too large for field of 4 bytes at 00015d15)
Severity set to 'normal' from 'serious'

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

Bug#833573: [Monotone-debian] Bug#833573: monotone: FTBFS on mipsel (Error: value of 0200000000002210 too large for field of 4 bytes at 0000000000015d15)

[Julien Cristau]

On Sun, Sep 11, 2016 at 21:19:50 +0200, Markus Wanner wrote:

> Control: tags -1 + unreproducible moreinfo
> Control: severity -1 normal
> 
> On 06.08.2016 10:56, Julien Cristau wrote:
> > the latest monotone security upload failed to build on mipsel
> 
> Thanks for your report. However, I could not reproduce this failure on
> eller.debian.org (a porter machine, Cavium Octeon III according to cpuinfo).
> 
> Is this reproducible? Unfortunately, I don't have access to a Loongson
> 3A processor, which mipsel-aql-01.debian.org seems to be.
> 
> Given this failure first occurred after a security update, which
> certainly didn't change the failing source file test/unit/tests/paths.cc
> in any way, I strongly suspect this is related to the build machine.
> 
Looks like it did build on mipsel-aql-02 a week ago.

Cheers,
Julien

Bug#837133: libconfig-model-itself-perl: FTBFS: t/load_write_itself.t failure

[Dominique Dumont]

On Fri, 9 Sep 2016 09:37:54 +0300 Niko Tyni  wrote:
>   Load command error:
>   command: 'upstream_default=#'
>   Syntax error: spurious char at command end: '=#'. Did you forget 
double quotes ?

This is a bug in Config::Model::Loader which is now trapped since 
Config::Model v2.089.

This bug is fixed in Config::Model 2.090 that will be packaged soon.

Thanks for the report

All the best
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Processed: tagging 797389, tagging 806454, tagging 818395

[Debian Bug Tracking System]

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

> tags 797389 + pending
Bug #797389 [src:calligra] calligra: FTBFS, missing build-dep on libsoprano-dev
Added tag(s) pending.
> tags 806454 + pending
Bug #806454 [calligra-libs] calligrastage not installable
Bug #808920 [calligra-libs] [calligra-libs] not installable
Bug #817945 [calligra-libs] Depends: libilmbase6 (>= 1.0.1) which is a virtual 
package and is not provided by any available package
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 818395 + pending
Bug #818395 [calligra] FTBFS: missing files, aborting
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 787033, tagging 762305, tagging 785653, tagging 826808

[Debian Bug Tracking System]

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

> tags 787033 + pending
Bug #787033 [calligra] [calligra] New release 2.9.4 available upstream
Added tag(s) pending.
> tags 762305 + pending
Bug #762305 [calligraflow] calligra: homepage address changed slightly
Ignoring request to alter tags of bug #762305 to the same tags previously set
> tags 785653 + pending
Bug #785653 [src:calligra] calligra: test suites times out on ci.debian.net, 
generates huge logs
Added tag(s) pending.
> tags 826808 + pending
Bug #826808 [src:calligra] calligra: OpenJPEG removal
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837261: libconfig-model-dpkg-perl: FTBFS: Tests failures

[Dominique Dumont]

On Sat, 10 Sep 2016 09:44:10 +0200 Lucas Nussbaum  wrote:
> Relevant part (hopefully):
> > Test Summary Report
> > ---
> > t/model_tests.t(Wstat: 65280 Tests: 814 Failed: 0)
> >   Non-zero exit status: 255

This means that  t/model_tests.t exited on error.

The logs contains:

# Beginning subtest dpkg pan-copyright-upgrade-update
ok 813 - Copied dpkg example pan-copyright-upgrade-update
ok 814 - Read configuration and created instance with init() method without 
warning check
# updating config with quiet 1 in t/scanner/examples/pan.in
writing back cache file
Dubious, test returned 255 (wstat 65280, 0xff00)
All 814 subtests passed 

The last line here is a bit confusing, it means all tests were fine before the 
program crashed.

This is due to an error in the test which is now trapped by Config::Model 
since v2.089. 

This is fixed in git and will be uploaded quite soon.

Thanks for the report

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#817501: marked as done (imgtex: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:49:07 +
with message-id 
and subject line Bug#817501: fixed in imgtex 0.20050123-9
has caused the Debian Bug report #817501,
regarding imgtex: 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.)


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

Hi,

The package imgtex 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: imgtex
Source-Version: 0.20050123-9

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 20:30:02 +0200
Source: imgtex
Binary: imgtex
Architecture: source
Version: 0.20050123-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 imgtex - provides yet another math-on-the-web solution
Closes: 817501
Changes:
 imgtex (0.20050123-9) unstable; urgency=medium
 .
   * QA upload.
   * Switch to dh.
   * Switch to "3.0 (quilt)" source format.
   * Raise debhelper compat level to 9. Closes: #817501.
   * Package is orphaned (Bug #780557), set Maintainer to "Debian QA Group".
Checksums-Sha1:
 78d09e9505ea43773ef4f3ccc8ca633de5a5ab2f 1328 imgtex_0.20050123-9.dsc
 9514d86001b064c5c52eed970ddc8fc12cfd848c 3792 imgtex_0.20050123-9.debian.tar.xz
Checksums-Sha256:
 0930833b89b06d67978861fa575c34898b9bbc9fff3bd26bfc9c0fe2dea9b983 1328 
imgtex_0.20050123-9.dsc
 f16aaf3754699749572ff6938513dab1737242a081023ae2c4021a669d9a6b7a 3792 
imgtex_0.20050123-9.debian.tar.xz
Files:
 f7b4cac40600d09fb8d535e723e23d35 1328 contrib/utils optional 
imgtex_0.20050123-9.dsc
 e7fdd7a4ed13a0f20ef1ccf27128975e 3792 contrib/utils optional 
imgtex_0.20050123-9.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJX1aNdAAoJEEHOfwufG4syXC8IAKJPr+JgKXxECOolHZci0Odo
0Q98C/NQ9lYhgcUb7b6fnZ/eEkIxi+QoZvCS00xDnC5Yrck3Vbft8bGqz0OZdzi3
roDvDXlqOuvc+N8v5xNgeU/YgJj1lnG4VBXmrFYODRd0t6JH17Ho3zRg5qLQCKWf
porROEzodi/RCcUDFmJYCZYfIIQqJEwGvqkAiURXwWByNlbfNMMRJF3nNELT16yy
PGv2QNV/ukheSbC+buOiq4JxHYWzwaLyispyNnq8idNtwuyO+PzOFdxANlbVysPo
ow1RVC/5K+9yEOyQEVqz8ieVL4Cr2mgJSFnodBv72CL9TtiHBWWCy+GXGusGhdA=
=Ixk1
-END PGP SIGNATURE End Message ---

Bug#833506: marked as done (chromium: Crashes when browsing Google Maps)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:37:43 +
with message-id 
and subject line Bug#833501: fixed in chromium-browser 53.0.2785.92-3
has caused the Debian Bug report #833501,
regarding chromium: Crashes when browsing Google Maps
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.)


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

Chromium is crashing all the time with Google Maps. Just go to
maps.google.com and start typing a city name in the input text:

Received signal 11 SEGV_MAPERR 0020
#0 0x5603e3710a1e 
#1 0x5603e3710dd9 
#2 0x7fd46fbfced0 
#3 0x5603e58f4f85 
[...]

This happened after upgrading to 52.0.2743.116-1. Downgrading to
52.0.2743.82-4 solves the problem for me.

Regards,

Berto

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.1-2
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.1.1-3
ii  libavformat577:3.0.2-4
ii  libavutil55  7:3.1.1-3
ii  libc62.23-4
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.4-1
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.1.1-3
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-9
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.20.6-1
ii  libharfbuzz0b1.2.6-2
ii  libjpeg62-turbo  1:1.5.0-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libnss3-1d   2:3.23-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libpulse08.0-2+b2
ii  libspeechd2  0.8.4-2
ii  libstdc++6   6.1.1-9
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.3+dfsg1-1.2
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-4
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1.07.4-1

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 53.0.2785.92-3

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 11 Sep 2016 14:47:55 +
Source: chromium-browser
Binary: chromium chromium-l10n chromedriver
Architecture: source
Version: 53.0.2785.92-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Maintainers 

Changed-By: Michael Gilbert 
Description:
 chromedriver - web browser - WebDriver support
 chromium   - web browser
 chromium-l10n - web browser - language packs
Closes: 833501
Changes:
 chromium-browser (53.0.2785.92-3) unstable; urgency=medium
 .
   * Add -fno-delete-null-pointer checks to the build flags (closes: #833501).
Checksums-Sha1:
 

Bug#833501: marked as done (Aw snap while using Facebook)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:37:43 +
with message-id 
and subject line Bug#833501: fixed in chromium-browser 53.0.2785.92-3
has caused the Debian Bug report #833501,
regarding Aw snap while using Facebook
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.)


-- 
833501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 52.0.2743.116-1
Severity: normal

After upgrading chromium this morning
[UPGRADE] chromium:amd64 52.0.2743.82-4 -> 52.0.2743.116-1
I've been getting frequent Aw snap crashes in Facebook, usually within a minute
of starting to use it.  Downgrading seems to fix the problem.

Following the advice in https://wiki.debian.org/Chromium/Debugging (which
appears to be out of date with respect to chromium-dbg) I installed -dbg and
-dbgsym packages for Chromium and its direct dependencies and then reproduced
the problem in chromium --debug:

# Env:
# LD_LIBRARY_PATH=
#PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
#GTK_PATH=
#  CHROMIUM_FLAGS= --show-component-extension-options 
--ignore-gpu-blacklist --disable-background-networking 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=21.0.0.242
/usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.m39soN
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium/chromium...Reading symbols from 
/usr/lib/debug/.build-id/f4/11584ae3d6b2ccff8656208d0e886b9718c66d.debug...(no 
debugging symbols found)...done.
(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/lib/chromium/chromium --show-component-extension-options 
--ignore-gpu-blacklist --disable-background-networking 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=21.0.0.242 --single-process 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdd09d700 (LWP 9359)]
[New Thread 0x7fffdc89c700 (LWP 9364)]
[New Thread 0x7fffd798c700 (LWP 9365)]
[New Thread 0x7fffd718b700 (LWP 9366)]
[New Thread 0x7fffd5a30700 (LWP 9367)]
[New Thread 0x7fffd521d700 (LWP 9368)]
[New Thread 0x7fffd4a1c700 (LWP 9369)]
[New Thread 0x7fffc3fff700 (LWP 9370)]
[New Thread 0x7fffc37fe700 (LWP 9371)]
[New Thread 0x7fffd421b700 (LWP 9372)]
[New Thread 0x7fffc2ffd700 (LWP 9373)]
[New Thread 0x7fffc155a700 (LWP 9374)]
[New Thread 0x7fffc0d59700 (LWP 9375)]
[New Thread 0x7fff9700 (LWP 9376)]
[New Thread 0x7fff9f7fe700 (LWP 9377)]
[New Thread 0x7fff9effd700 (LWP 9378)]
[New Thread 0x7fff9e7fc700 (LWP 9379)]
[New Thread 0x7fff9dffb700 (LWP 9380)]
[New Thread 0x7fff9d7fa700 (LWP 9381)]
[New Thread 0x7fff9cff9700 (LWP 9382)]
[New Thread 0x7fff97fff700 (LWP 9383)]
[New Thread 0x7fff977fe700 (LWP 9384)]
[New Thread 0x7fff96ffd700 (LWP 9385)]
[New Thread 0x7fff967fc700 (LWP 9386)]
[9355:9381:0805/102349:ERROR:nss_util.cc(842)] After loading Root Certs, 
loaded==false: NSS error code: -8018
[New Thread 0x7fff95ffb700 (LWP 9425)]
[New Thread 0x7fff957fa700 (LWP 9427)]
[9355:9381:0805/102349:ERROR:proxy_service_factory.cc(128)] Cannot use V8 Proxy 
resolver in single process mode.
[New Thread 0x7fff875a9700 (LWP 9428)]
[9355:9381:0805/102349:ERROR:proxy_service_factory.cc(128)] Cannot use V8 Proxy 
resolver in single process mode.
[New Thread 0x7fff84a96700 (LWP 9430)]
[New Thread 0x7fff85297700 (LWP 9429)]
[New Thread 0x7fff84295700 (LWP 9433)]
[New Thread 0x7fff83a94700 (LWP 9434)]
[New Thread 0x7fff83293700 (LWP 9435)]
[Thread 0x7fff83293700 (LWP 9435) exited]
[Thread 

Bug#833524: marked as done (chromium: Aw Snap! after update to new in sid / even when purged and installed as clean)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:37:43 +
with message-id 
and subject line Bug#833501: fixed in chromium-browser 53.0.2785.92-3
has caused the Debian Bug report #833501,
regarding chromium: Aw Snap! after update to new in sid / even when purged and 
installed as clean
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.)


-- 
833501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 52.0.2743.116-1
Severity: normal
Tags: upstream

Dear Maintainer,

1. open browser
2. go to google 
3. enter map 
4 . aw snap 

for most sites that load i get aw snap ( it's rendering only simple pages ) 

no addons no plugins i clear cache, setting (purged all data which belongs to 
chromium ) still no efect 

-- 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/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.1.1-4
ii  libavformat577:3.1.1-4
ii  libavutil55  7:3.1.1-4
ii  libc62.23-4
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.4-4
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-11
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-2
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.20.7-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.0-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.25-1
ii  libnss3-1d   2:3.25-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-1.1
ii  libspeechd2  0.8.4-2
ii  libstdc++6   6.1.1-11
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.4+dfsg1-1+b1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-4
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
pn  fonts-liberation  

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 53.0.2785.92-3

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 11 Sep 2016 14:47:55 +
Source: chromium-browser
Binary: chromium chromium-l10n chromedriver
Architecture: source
Version: 53.0.2785.92-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Maintainers 

Changed-By: Michael Gilbert 
Description:
 chromedriver - web browser - WebDriver support
 chromium   - web browser
 chromium-l10n - web browser - language packs
Closes: 833501
Changes:
 chromium-browser (53.0.2785.92-3) unstable; urgency=medium
 .
   * Add -fno-delete-null-pointer checks to the build flags (closes: #833501).
Checksums-Sha1:
 3c3aa786b8ffaf99edc863fce12cfd80af911174 3948 
chromium-browser_53.0.2785.92-3.dsc
 8342ba3f442461c9d5d43073d45a48373f25df4d 123104 

Bug#833542: marked as done (chromium: Crashes all the time after last update)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:37:43 +
with message-id 
and subject line Bug#833501: fixed in chromium-browser 53.0.2785.92-3
has caused the Debian Bug report #833501,
regarding chromium: Crashes all the time after last update
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.)


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

Dear Maintainer,
after the last update, I am getting the "aw snap!" page all
the time.

I see on the changelog that security fixes were made, but
at the moment it became rather unusable for me.

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.1.1-4
ii  libavformat577:3.1.1-4
ii  libavutil55  7:3.1.1-4
ii  libc62.23-4
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.4-4
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-11
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-2
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.20.7-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.0-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.25-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-1.1
ii  libspeechd2  0.8.4-2
ii  libstdc++6   6.1.1-11
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.4+dfsg1-1+b1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-4
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
pn  fonts-liberation  

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 53.0.2785.92-3

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 11 Sep 2016 14:47:55 +
Source: chromium-browser
Binary: chromium chromium-l10n chromedriver
Architecture: source
Version: 53.0.2785.92-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Maintainers 

Changed-By: Michael Gilbert 
Description:
 chromedriver - web browser - WebDriver support
 chromium   - web browser
 chromium-l10n - web browser - language packs
Closes: 833501
Changes:
 chromium-browser (53.0.2785.92-3) unstable; urgency=medium
 .
   * Add -fno-delete-null-pointer checks to the build flags (closes: #833501).
Checksums-Sha1:
 3c3aa786b8ffaf99edc863fce12cfd80af911174 3948 
chromium-browser_53.0.2785.92-3.dsc
 8342ba3f442461c9d5d43073d45a48373f25df4d 123104 
chromium-browser_53.0.2785.92-3.debian.tar.xz
Checksums-Sha256:
 

Bug#817368: marked as done (audiolink: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:18:30 +
with message-id 
and subject line Bug#817368: fixed in audiolink 0.05-2
has caused the Debian Bug report #817368,
regarding audiolink: 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.)


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

Hi,

The package audiolink 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: audiolink
Source-Version: 0.05-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 20:09:38 +0200
Source: audiolink
Binary: audiolink
Architecture: source
Version: 0.05-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 audiolink  - makes managing and searching for music easier
Closes: 817368
Changes:
 audiolink (0.05-2) unstable; urgency=medium
 .
   * QA upload.
   * Switch to dh.
   * Switch to "3.0 (quilt)" source format.
   * Raise debhelper compat level to 9. Closes: #817368.
   * Package is "Arch: all", put everything in Build-Depends.
   * Package is orphaned (Bug #831544), set Maintainer to "Debian QA Group".
Checksums-Sha1:
 6724653f201d2ecd485aced5b59f3e201c3435d2 1325 audiolink_0.05-2.dsc
 d44a0bd7ad6f00bb86d8a1c7c4b843296e0c90c1 3116 audiolink_0.05-2.debian.tar.xz
Checksums-Sha256:
 e8a7c81dbd53ffc4d2f843f5d78d6d43021606dbbf624fb16d131c3b1bac27d8 1325 
audiolink_0.05-2.dsc
 0a79482306ea4f3a0d4759358f34858fae96194eb2b8274f2af915954b8ff6b8 3116 
audiolink_0.05-2.debian.tar.xz
Files:
 f2bebd02b6a9ea606b4909eee5e80845 1325 sound optional audiolink_0.05-2.dsc
 be86ea7885e1ef666064282cc4262f61 3116 sound optional 
audiolink_0.05-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJX1Z3vAAoJEEHOfwufG4syyt0IAKk8jCByMKv4bD3udkYQtHcz
sv5TxsCOq27lT3A5FE71D6IIm1anf3lygO7Ju+RRJGY4tVbCaGSHMO+BwaLw6KZQ
kxjwL/2gUBlLeUq/rEhR1g2SHyRSoMuiL/b/qhx0EJODkSr7Cu/LvgByJxikT/p+
X47v5khA5KDns9rtu8bpBfXX5p1biZ+WHGouHFIXOwbCBiuodu572nuFzSClCcFf
gfdYgvTh+uZ+DXkbe6+ugI76JhhU3wyfMtbIaw7cX/hMIWf5VOEnQNbvxhoVCbbz
BQa2i+EYwwriknewZ3V+BGiBOLnGOBUJ3vl0q4aN82MsUuXqa5e1KBzesuaoPuc=
=023h
-END PGP SIGNATURE End Message ---

Bug#837268: marked as done (bzr: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 18:18:45 +
with message-id 
and subject line Bug#837268: fixed in bzr 2.7.0+bzr6619-2
has caused the Debian Bug report #837268,
regarding bzr: FTBFS: Tests 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.)


-- 
837268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bzr
Version: 2.7.0+bzr6619-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 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 
> "/<>/bzr-2.7.0+bzr6619/build/lib.linux-x86_64-2.7/bzrlib/tests/test_diff.py",
>  line 317, in test_external_diff_binary
> self.assertEqual(2, pipe.returncode)
>   File 
> "/<>/bzr-2.7.0+bzr6619/build/lib.linux-x86_64-2.7/bzrlib/tests/__init__.py",
>  line 1370, in assertEqual
> pprint.pformat(a), pprint.pformat(b)))
> AssertionError: not equal:
> a = 2
> b = 1
> 
> --
> Ran 28545 tests in 922.702s
> 
> FAILED (failures=1, known_failure_count=59)
> 2810 tests skipped
> debian/rules:21: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/bzr_2.7.0+bzr6619-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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: bzr
Source-Version: 2.7.0+bzr6619-2

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

Debian distribution maintenance software
pp.
Vincent Ladeuil  (supplier of updated bzr 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, 09 Sep 2016 16:00:49 +0200
Source: bzr
Binary: bzr python-bzrlib python-bzrlib-dbg python-bzrlib.tests bzr-doc
Architecture: source all amd64
Version: 2.7.0+bzr6619-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Vincent Ladeuil 
Description:
 bzr- easy to use distributed version control system
 bzr-doc- easy to use distributed version control system (documentation)
 python-bzrlib - distributed version control system - python library
 python-bzrlib-dbg - distributed version control system - debug extension
 python-bzrlib.tests - distributed version control system - testsuite
Closes: 837268
Changes:
 bzr (2.7.0+bzr6619-2) unstable; urgency=medium
 .
   * Add 18_diff_binaries: With diffutils > 3.5, diff stop exiting with '2'
 on binary files. LP: #1622039
 Closes: #837268
 .
   * Add 19_fix_long_creds: Fix http Basic auth with credentials longer
 than ~57 characters. LP: #1606203
Checksums-Sha1:
 9c6fedf63f538e3891ef31af211c8c4255f60052 2811 bzr_2.7.0+bzr6619-2.dsc
 524854306b3d5e24d511630d787f41de15afc85c 66348 
bzr_2.7.0+bzr6619-2.debian.tar.xz
 e498e09e75782b0e872c9a54c1358f31b89dd245 4487922 
bzr-doc_2.7.0+bzr6619-2_all.deb
 4451f79118e4ad65200d1172d26fb943f2a5f6a0 55032 bzr_2.7.0+bzr6619-2_all.deb
 d95f0ccce27c867fd3655e05d7b33d23c9fa562d 2176962 
python-bzrlib-dbg_2.7.0+bzr6619-2_amd64.deb
 9c4ced5a06dc5f50e9112d7b9f0d38ae2087fba7 1025836 
python-bzrlib.tests_2.7.0+bzr6619-2_all.deb
 32c3b5c535b89831b28df501465419abf136f7fd 1664092 
python-bzrlib_2.7.0+bzr6619-2_amd64.deb
Checksums-Sha256:
 ae5603f5568ce8c67c75ae65042fcdd2eb132d31f2baef6fad258ad05e6e57f0 2811 

Processed: reopening 832931

[Debian Bug Tracking System]

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

> reopen 832931
Bug #832931 {Done: Otto Kekäläinen } [src:mariadb-10.0] 
mariadb-10.0: FTBFS on powerpc
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mariadb-10.0/10.0.27-0+deb8u1.
> thanks
Stopping processing here.

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

Bug#834683: fixed in mini-buildd 1.0.17

[Stephan Sürken]

Hi Santiago,

On So, 2016-09-11 at 11:37 +0200, Santiago Vila wrote:
(...)
> This is the changelog entry you wrote:
> 
> >    * [8ee94bc] gnupg.py: Add extra method to get sec user id. Fixes
> doctest
> >  for GPG 2.1. Thanks to Santiago Vila (Closes: 834683)
> 
> If this is only intended to work with gnupg 2, please add
> Build-Depends: gnupg (>= 2) so that autobuilders testing packages in
> stretch do not even try to build it with gnupg version 1.

no, this should work for both, 1.4 and 2.1.

> OTOH, if this is intended to work with both gnupg 1 and gnupg 2
> (for example, if you intend this to be backported to jessie),
> then the problem is still here.

Yes, I do ;). And I did test it under jessie, and also the package
build under stretch.

> The error message:
(...)
> suggests to me that there is not enough entropy to generate a key.

If entropy actually is the problem, it should have always been there
for all 1.0.x versions (having that doctest).

> (I don't know how to fix that, sorry, maybe an additional
> build-depends on some package which wraps accesses to /dev/random to
> make them faster, if such package exists).
> 
> The full build log is attached.
> 
> This time I only tried to build it once, but since the problem was
> not
> supposed to always happen, it is probably correct to say that the
> FTBFS-randomness has not been eliminated.

Ok, agree, this does add some randomness [which I usually mitigate
running something like haveged on the builder host]. I guess this
generally means automated tests depending on some entropy must be
avoided?

Anyway, I don't have a good solution either right now; maybe someone
already has? Will look around eventually ;)

Thx,

S

Bug#837268: Please upload bzr 2.7.0+bzr6619-2

[Vincent Ladeuil]

The attached patch fixes:

- the test failure caused by diff not exiting '2' on binary files
  anymore (the test was too eager, no other part of bzr relies on this
  behavior), 

- http basic auth was broken when the base64 encoding for the auth
  header become too long.

The former being encountered while fixing the later.

Tested locally with

autopkgtest .// -U -- lxd autopkgtest/debian/sid/amd64


Pushed to
https://anonscm.debian.org/bzr/pkg-bazaar/bzr/2.7/

Thanks in advance,

   Vincent

=== modified file 'debian/changelog'
--- debian/changelog	2016-07-02 16:18:18 +
+++ debian/changelog	2016-09-11 16:43:13 +
@@ -1,3 +1,14 @@
+bzr (2.7.0+bzr6619-2) unstable; urgency=medium
+
+  * Add 18_diff_binaries: With diffutils > 3.5, diff stop exiting with '2'
+on binary files. LP: #1622039
+Closes: #837268
+
+  * Add 19_fix_long_creds: Fix http Basic auth with credentials longer
+than ~57 characters. LP: #1606203
+
+ -- Vincent Ladeuil   Fri, 09 Sep 2016 16:00:49 +0200
+
 bzr (2.7.0+bzr6619-1) unstable; urgency=medium
 
   * Bump standards version to 3.9.8 (no changes).

=== added file 'debian/patches/18_diff_binaries'
--- debian/patches/18_diff_binaries	1970-01-01 00:00:00 +
+++ debian/patches/18_diff_binaries	2016-09-11 16:39:56 +
@@ -0,0 +1,17 @@
+Description: diff doesn't exit with 2 anymore on binary files.
+Author: Vincent Ladeuil 
+
+
+=== modified file 'bzrlib/tests/test_diff.py'
+--- unstable.orig/bzrlib/tests/test_diff.py	2016-02-01 18:06:32 +
 unstable/bzrlib/tests/test_diff.py	2016-09-11 16:32:54 +
+@@ -313,8 +313,6 @@
+ pipe = subprocess.Popen(cmd, stdout=subprocess.PIPE,
+  stdin=subprocess.PIPE)
+ out, err = pipe.communicate()
+-# Diff returns '2' on Binary files.
+-self.assertEqual(2, pipe.returncode)
+ # We should output whatever diff tells us, plus a trailing newline
+ self.assertEqual(out.splitlines(True) + ['\n'], lines)
+ 
+

=== added file 'debian/patches/19_fix_long_creds'
--- debian/patches/19_fix_long_creds	1970-01-01 00:00:00 +
+++ debian/patches/19_fix_long_creds	2016-09-09 14:03:49 +
@@ -0,0 +1,49 @@
+Description: http Basic auth was broken
+ When a long (>57) user/pass combination was used, a spurious '\n' ended up in the header value, crashing httplib.
+.
+Author: Vincent Ladeuil 
+
+
+
+=== modified file 'bzrlib/tests/test_http.py'
+--- unstable.orig/bzrlib/tests/test_http.py	2016-02-01 18:06:32 +
 unstable/bzrlib/tests/test_http.py	2016-09-09 12:57:44 +
+@@ -260,6 +260,16 @@
+ self.assertEqual('basic', scheme)
+ self.assertEqual('realm="Thou should not pass"', remainder)
+ 
++def test_build_basic_header_with_long_creds(self):
++handler = _urllib2_wrappers.BasicAuthHandler()
++user = 'user' * 10  # length 40
++password = 'password' * 5  # length 40
++header = handler.build_auth_header(
++dict(user=user, password=password), None)
++# https://bugs.launchpad.net/bzr/+bug/1606203 was caused by incorrectly
++# creating a header value with an embedded '\n'
++self.assertFalse('\n' in header)
++
+ def test_basic_extract_realm(self):
+ scheme, remainder = self.parse_header(
+ 'Basic realm="Thou should not pass"',
+
+=== modified file 'bzrlib/transport/http/_urllib2_wrappers.py'
+--- unstable.orig/bzrlib/transport/http/_urllib2_wrappers.py	2016-01-31 12:55:31 +
 unstable/bzrlib/transport/http/_urllib2_wrappers.py	2016-09-09 12:58:12 +
+@@ -48,6 +48,7 @@
+ # actual code more or less do that, tests should be written to
+ # ensure that.
+ 
++import base64
+ import errno
+ import httplib
+ import os
+@@ -1491,7 +1492,7 @@
+ 
+ def build_auth_header(self, auth, request):
+ raw = '%s:%s' % (auth['user'], auth['password'])
+-auth_header = 'Basic ' + raw.encode('base64').strip()
++auth_header = 'Basic ' + base64.b64encode(raw)
+ return auth_header
+ 
+ def extract_realm(self, header_value):
+

=== modified file 'debian/patches/series'
--- debian/patches/series	2016-07-02 16:15:17 +
+++ debian/patches/series	2016-09-11 16:38:05 +
@@ -5,3 +5,5 @@
 15_autodoc_source_epoch
 16_paramiko_compat
 17_reproducible_makefile
+18_diff_binaries
+19_fix_long_creds

Processed: tagging 837327

[Debian Bug Tracking System]

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

> tags 837327 + pending
Bug #837327 [src:console-setup] Randomly FTBFS: Races in parallel build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822021: scalapack: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Sebastiaan Couwenberg]

On 09/11/2016 07:00 PM, Sebastiaan Couwenberg wrote:
> On 09/11/2016 06:53 PM, Muammar El Khatib wrote:
>> On Sun, Sep 11, 2016 at 04:25:26PM +0200, Sebastiaan Couwenberg wrote:
>> I had already applied this patch:
>>
>> scalapack (1.8.0-13) unstable; urgency=medium
>>
>>   * Added missing build-{arch,indep} targets. Thanks to Santiago Vila for
>> providing a patch. Closes: #822021.
>>   * hppa architecture switched to openmpi. Closes: #834182.
>>
>>  -- Muammar El Khatib   Mon, 05 Sep 2016 23:48:13 
>> +0200
>>
>> I am waiting for the openmpi upload of today that closes #837062 to proceed.

PS, in case you hadn't yet, don't forget to incorporate the changes from
the last three NMUS:

 scalapack (1.8.0-12.3) https://tracker.debian.org/news/747399
 scalapack (1.8.0-12.2) https://tracker.debian.org/news/746047
 scalapack (1.8.0-12.1) https://tracker.debian.org/news/675073

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: scalapack: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #822021 [src:scalapack] scalapack: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added tag(s) pending.

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

Bug#822021: scalapack: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Muammar,

On 09/11/2016 06:53 PM, Muammar El Khatib wrote:
> On Sun, Sep 11, 2016 at 04:25:26PM +0200, Sebastiaan Couwenberg wrote:
>> On Tue, 26 Jul 2016 16:17:49 +0200 (CEST) Santiago Vila  wrote:
>>> tags 822021 + patch
>>> thanks
>>>
>>> I also recommend switching to dh, but in the meantime, the attached
>>> patch should work.
>>
>> Muammar, please apply this patch and upload a new scalapack revision to
>> unstable as soon as possible.
>>
>> scalapack binNMUes for the ongoing openmpi transition are failing
>> because of this issue, and prevent building its many reverse dependencies.
>>
> 
> I had already applied this patch:
> 
> scalapack (1.8.0-13) unstable; urgency=medium
> 
>   * Added missing build-{arch,indep} targets. Thanks to Santiago Vila for
> providing a patch. Closes: #822021.
>   * hppa architecture switched to openmpi. Closes: #834182.
> 
>  -- Muammar El Khatib   Mon, 05 Sep 2016 23:48:13 
> +0200
> 
> I am waiting for the openmpi upload of today that closes #837062 to proceed.

Thanks, that's excellent news. Let's tag this bugreport accordingly.

openmpi (2.0.1-4) should be available on the mirrors in about 4 hours.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#822021: scalapack: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Muammar El Khatib]

Hi Sebastiaan,

On Sun, Sep 11, 2016 at 04:25:26PM +0200, Sebastiaan Couwenberg wrote:
> On Tue, 26 Jul 2016 16:17:49 +0200 (CEST) Santiago Vila  wrote:
> > tags 822021 + patch
> > thanks
> >
> > I also recommend switching to dh, but in the meantime, the attached
> > patch should work.
>
> Muammar, please apply this patch and upload a new scalapack revision to
> unstable as soon as possible.
>
> scalapack binNMUes for the ongoing openmpi transition are failing
> because of this issue, and prevent building its many reverse dependencies.
>

I had already applied this patch:

scalapack (1.8.0-13) unstable; urgency=medium

  * Added missing build-{arch,indep} targets. Thanks to Santiago Vila for
providing a patch. Closes: #822021.
  * hppa architecture switched to openmpi. Closes: #834182.

 -- Muammar El Khatib   Mon, 05 Sep 2016 23:48:13 +0200

I am waiting for the openmpi upload of today that closes #837062 to proceed.


Cheers,
--
Muammar El Khatib.
Linux user: 403107.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Processed: second attempt at merging

[Debian Bug Tracking System]

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

> forcemerge 835639 812630
Bug #835639 [ftp.debian.org] RM: jasper -- RoQA; dead upstrem, replaced by 
openjpeg
Bug #812630 [ftp.debian.org] RM: jasper -- RoQA; dead upstrem, replaced by 
openjpeg
812630 was not blocked by any bugs.
812630 was not blocking any bugs.
Added blocking bug(s) of 812630: 818201
Added tag(s) moreinfo.
Merged 812630 835639
> thanks
Stopping processing here.

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

Bug#818448: marked as done (imapcopy: FTBFS: Error: identifier idents no member)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 16:20:05 +
with message-id 
and subject line Bug#818448: fixed in imapcopy 1.04-2.1
has caused the Debian Bug report #818448,
regarding imapcopy: FTBFS: Error: identifier idents no member
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.)


-- 
818448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imapcopy
Version: 1.04-2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> Compiling imaptools.pas
> Compiling inet.pp
> Compiling logfile.pas
> imaptools.pas(238,8) Error: identifier idents no member "family"
> imaptools.pas(239,8) Error: identifier idents no member "port"
> imaptools.pas(241,8) Error: identifier idents no member "addr"
> imaptools.pas(1671) Fatal: There were 3 errors compiling module, stopping
> Fatal: Compilation aborted
> Error: /usr/bin/ppcx64 returned an error exitcode
> Makefile:7: recipe for target 'imapcopy' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: imapcopy
Source-Version: 1.04-2.1

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated imapcopy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Sep 2016 11:31:36 +
Source: imapcopy
Binary: imapcopy
Architecture: source
Version: 1.04-2.1
Distribution: unstable
Urgency: medium
Maintainer: Gergely Risko 
Changed-By: Peter Michael Green 
Description:
 imapcopy   - IMAP backup, copy and migration tool
Closes: 818448
Changes:
 imapcopy (1.04-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build with fpc 3.0.0 (Closes: 818448)
Checksums-Sha1:
 b313931467ead6d2b5e14180d51d7c2a6eb22036 1680 imapcopy_1.04-2.1.dsc
 7a437957aefb4cb2076bd614d1ca6bfcdeac33aa 5900 imapcopy_1.04-2.1.debian.tar.xz
Checksums-Sha256:
 fc909e5fdec438d0dfe89547e68c316d1c3eb4c7c04fa657347c42af81509eff 1680 
imapcopy_1.04-2.1.dsc
 a33385ee18291110f7b93e3216684f24bbfc2c62335111c407e1479944c99f30 5900 
imapcopy_1.04-2.1.debian.tar.xz
Files:
 11d2ed60cb5340f993d2eb35d24baede 1680 mail optional imapcopy_1.04-2.1.dsc
 fe12c7f4bffa4383c4ab3a7702f5a72b 5900 mail optional 
imapcopy_1.04-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX1Xg2AAoJEPNPCXROn13ZY2MP/RSHtz4JuH9Kx9S9uyq0+prL
TGaCg3+7GwOwh5FXtM/sBqGC/hhFb3y+OOTOZu6k+SeUrhaKDmYHWqUMJ2AiPIOc
jm+S3EspQPYF6BvLncM06XTQ6EpqubgDgEHzkjVrqLyYwdGucfgViCcBV06HNnMp
iAtDc7WV1VHPNgjIyqFG/cHKNePbI7dggP/pcqBnGfVKUVSE1/yfYOCKqznhfB71
JEA8LrygWW8rwQQn8jd5Kuze/ioRlVoFa8lZ1fBUyMX+J1HhrCvNeSBomt/7iJsV
9H5JTLmaZ4K3YoIREohMLAGU+Ag2UfIC+wQU6e5skhQLxGp8ssVFz5JYTQJGanNv
p+ctM8/pBFq+nVC1YAyTWLXGaU4kr9ykfCg46doWJO6jA3HNLgxJQ1uGXCNpkQp1
Z8joWvfJY7oHQ76BF7PGswCUmltZtEyHKu/ha+sUE0WxWNWevKChDrRB7MdcqEJA
cVMkBYVUh0McPMo8aoyrmYI7u3r4pMM+EIN438LPZiXtqIxbfLP6xD8jApzoblb2
nXxa3X44E5xNC4rxIKaj9sFwkx91MN0A3s9DhpTugmpfO4Jvqj4Ix/IvTOLORcnG
Cbph9hFo3foZzwpaxbzSw3+UXFYaFai6vFx4minzBWE1HhSWcFSiBW8TT6SAJZsL
i/oRIaTbR1EkWr5KBzNh
=8fpH
-END PGP SIGNATURE End Message ---

Bug#832285: Symlink /usr/lib/libompitrace.so.0 pointing to wrong file

[Guus Sliepen]

I'm writing a tool called debsyscheck that tries to find and repair
problems with a debian installation. It found this problem on one of my
systems:

[guus@haplo]~/debsyscheck>sudo ./debsyscheck
STAGE 1: gathering information about installed packages
STAGE 2: checking for missing files
[...]
Missing file /usr/lib/libompitrace.so.0 from package libopenmpi2

Reinstalling libopenmpi2 does not fix the problem. After some digging,
it looks like the package does contain this file, but it links to
libompitrace.so.0.0.0, which is wrong. During the postinst phase,
ldconfig notices the dangling symlink in /usr/lib and removes it.

This symlink should not be in the package at all; ldconfig normally will
create such symlinks automatically, and indeed it creates the correct
symlink (libompitrace.so.20 -> libompitrace.so.20.0.0).

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#835075: [PATCH] use fake-pinentry (Closes: #835075)

[gregor herrmann]

On Tue, 06 Sep 2016 10:56:15 -0400, Daniel Kahn Gillmor wrote:

> On Sat 2016-09-03 03:58:34 -0400, gregor herrmann wrote:
> > 1) After the build finishes there are 6 instances of gpg-agent
> >   running. In my cowbuilder setup this doesn't cause any issues and
> >   they time out after some time (1 minute I guess).
> right, those processes should time out after their temporary home
> directories are removed.  I'm working with upstream on making that
> timeout happen faster than a 1 minute delay, but it's not done yet.

Sounds good, thanks!
 
> > 3) This is in schroot-on-lvm. And here unmounting fails because of the
> >running gpg-agents leaving my schroot/lvm setup in a sad state.
> right, but this is a different issue, related to gpg-agent not.
> terminating rapidly enough when its socket is removed (same as (1)).
> I'm happy to track this as an issue, but it is a different issue than
> 835075.

True, I'm just a bit hesitant to upload a package which (at least in
my autopkgtest setup) fails autopkgtests and leaves a broken schroot
session and an orphaned lvm snapshot lying around. My fear is that
the same happens on the buildds and on ci.debian.net.
 
> > Another question is if we could have a fake-pinentry in some central
> > place (gnupg binary package?) to be used from all packages instead of
> > adding it everywhere?
> I am happy to ship something like fake-pinentry.pl (a pinentry that
> always returns "passphrase" and gamely accepts anything else) in a
> separate package, or even in gnupg as /usr/lib/gnupg/fake-pinentry, 

Cool, thanks.

> but
> it seems more important for me to get these fixes upstreamed.

Right, and I've asked David on IRC to look into this issue.
 
> I could even ship upstream's ./tests/openpgp/fake-pinentry.c there,
> though i worry that it now has too many features, which might actually
> encourage people to try to use it in non-dev environments; i think that
> would be a bad outcome.

Good point.
 
> Also, for language-specific libraries like lib*-perl, upstream will want
> this stuff to work on all platforms, and we can't guarantee that any
> gnupg binary package on other platforms will ship a fake-pinentry.

Good point as well :)
 
> So i think we should go ahead with this patch, as well as submitting it
> upstream.  I'm happy to try to replicate it on the other lib*-perl
> gnupg-related packages too if you're ok with this.

You're more than welcome to take a look at the other perl packages :)

TTBOMK we have:
#834522 libgnupg-perl
#835075 libmail-gnupg-perl
#834281 libgnupg-interface-perl
#835711 libconfig-identity-perl


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Nick Drake: 'Cello Song


signature.asc
Description: Digital Signature

Processed: affects 837062

[Debian Bug Tracking System]

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

> affects 837062 = src:scalapack
Bug #837062 {Done: Alastair McKinstry } [libopenmpi-dev] 
pkgincludedir undefined in openmpi pkgconfig files
Removed indication that 837062 affects src:espresso, src:freefem++, src:aster, 
src:elpa, src:petsc, src:mumps, src:nwchem, and src:cp2k
Added indication that 837062 affects src:scalapack
> thanks
Stopping processing here.

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

Bug#822021: scalapack: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Sebastiaan Couwenberg]

On Tue, 26 Jul 2016 16:17:49 +0200 (CEST) Santiago Vila  wrote:
> tags 822021 + patch
> thanks
> 
> I also recommend switching to dh, but in the meantime, the attached
> patch should work.

Muammar, please apply this patch and upload a new scalapack revision to
unstable as soon as possible.

scalapack binNMUes for the ongoing openmpi transition are failing
because of this issue, and prevent building its many reverse dependencies.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#837273:

[Santiago Vila]

affects 837273 src:csoundqt
thanks

The affects keyword helps to avoid duplicate bugs in the affected
packages (in fact, this bug was first reported against csoundqt
and then reassigned, and I was close to report it again).

Thanks.

Processed: Bug#837273

[Debian Bug Tracking System]

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

> affects 837273 src:csoundqt
Bug #837273 {Done: Felipe Sateler } [libcsound64-dev] 
libcsound64-dev: missing .so symlink
Added indication that 837273 affects src:csoundqt
> thanks
Stopping processing here.

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

Processed: block 836917 with 822021

[Debian Bug Tracking System]

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

> block 836917 with 822021
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 835680 831164 817690 811907 830440 837059 837061 837062 
837058 837055 825934 812036 811651 837012 837109 837030
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 822021
> thanks
Stopping processing here.

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

Processed: affects 822021

[Debian Bug Tracking System]

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

> affects 822021 src:aster src:cp2k src:elpa src:espresso src:freefem++ 
> src:mumps src:nwchem src:petsc
Bug #822021 [src:scalapack] scalapack: Build arch:all+arch:any but is missing 
build-{arch,indep} targets
Added indication that 822021 affects src:aster, src:cp2k, src:elpa, 
src:espresso, src:freefem++, src:mumps, src:nwchem, and src:petsc
> thanks
Stopping processing here.

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

Bug#837392: marked as done (libopenmpi-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/openmpi/lib/mpi.mod)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 13:49:12 +
with message-id 
and subject line Bug#837392: fixed in openmpi 2.0.1-4
has caused the Debian Bug report #837392,
regarding libopenmpi-dev: fails to upgrade from 'jessie' - trying to overwrite 
/usr/lib/openmpi/lib/mpi.mod
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.)


-- 
837392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi-dev
Version: 2.0.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libparmetis-dev parmetis-test

Hi,

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

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

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

  Preparing to unpack .../3-libopenmpi-dev_2.0.1-3_amd64.deb ...
  Unpacking libopenmpi-dev (2.0.1-3) over (1.6.5-9.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-YV9ZDR/3-libopenmpi-dev_2.0.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/openmpi/lib/mpi.mod', which is also in package 
libopenmpi1.6 1.6.5-9.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libparmetis-dev_4.0.3-4+b2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 2.0.1-4

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 11:32:28 +0100
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi2 openmpi-common openmpi-doc
Architecture: source amd64 all
Version: 2.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi2 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Closes: 837062 837392
Changes:
 openmpi (2.0.1-4) unstable; urgency=medium
 .
   * Fixes for build_hurd. Also, don't run tests on hurd
   * Remove buggy ${pkgincludedir} references from pkgconfig files.
 Closes: #837062.
   * Add Breaks/Replaces for libopenmpi1.6 to -dev. Closes: #837392
Checksums-Sha1:
 1b5af9a2a7df62d03fe7f27d590bc9bbe55a4b48 2630 openmpi_2.0.1-4.dsc
 d43eb8250bcd8fbf492defd2af0e05c9ded3 62216 openmpi_2.0.1-4.debian.tar.xz
 a1f5c62546f8d4ceb63e256e5ee1e30459caf731 18936 
libopenmpi-dev-dbgsym_2.0.1-4_amd64.deb
 980b6b8e0eb8e5506606cb39803bf4c15f2d57cb 996824 
libopenmpi-dev_2.0.1-4_amd64.deb
 7e6ff2c341cb9c766c265b8f561b78e614e8aab8 18835846 
libopenmpi2-dbgsym_2.0.1-4_amd64.deb
 93def1392be503b908186d2ce0e476f9c2409cec 1862742 libopenmpi2_2.0.1-4_amd64.deb
 dd43312bfaed482b68484106bb86e162a50820b9 204896 
openmpi-bin-dbgsym_2.0.1-4_amd64.deb
 16673018c058707a34d5533dad9b6537faf958e7 198064 openmpi-bin_2.0.1-4_amd64.deb
 931d1c56d05b4b609e592e53f1fe8f102a6eb782 146428 openmpi-common_2.0.1-4_all.deb
 d9dec0b6c9a2aba2faa39c64c76ba583145d66b2 698638 openmpi-doc_2.0.1-4_all.deb
Checksums-Sha256:
 3bbf3edd96baf6200c70d9b53dacb86b8769546171d61e608f9a02bd2f15d006 2630 
openmpi_2.0.1-4.dsc
 43ac612d6cf11525efd42594de6a9cfbc86d2c70a368caba8921bf69d36994b7 62216 
openmpi_2.0.1-4.debian.tar.xz
 dfe6fd9d8aace9370fd6fd5bec42a547594420431f5c1402067117ff7fcf7537 18936 
libopenmpi-dev-dbgsym_2.0.1-4_amd64.deb
 

Processed: request-tracker4 uninstallable

[Debian Bug Tracking System]

Processing control commands:

> block 837223 by -1
Bug #837223 [src:rt-extension-calendar] rt-extension-calendar: FTBFS: 
unsatisfiable build-dependencies: request-tracker4, libmodule-install-rtx-perl
837223 was not blocked by any bugs.
837223 was not blocking any bugs.
Added blocking bug(s) of 837223: 837422
> block 837287 by -1
Bug #837287 [src:rt-extension-jsgantt] rt-extension-jsgantt: FTBFS: 
unsatisfiable build-dependencies: request-tracker4, libmodule-install-rtx-perl
837287 was not blocked by any bugs.
837287 was not blocking any bugs.
Added blocking bug(s) of 837287: 837422
> block 837269 by -1
Bug #837269 [src:rt-extension-nagios] rt-extension-nagios: FTBFS: 
build-dependency not installable: libmodule-install-rtx-perl (>= 0.37-3~)
837269 was not blocked by any bugs.
837269 was not blocking any bugs.
Added blocking bug(s) of 837269: 837422
> block 837279 by -1
Bug #837279 [src:rt-extension-smsnotify] rt-extension-smsnotify: FTBFS: 
build-dependency not installable: libmodule-install-rtx-perl (>= 0.37-3~)
837279 was not blocked by any bugs.
837279 was not blocking any bugs.
Added blocking bug(s) of 837279: 837422

-- 
837223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837223
837269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837269
837279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837279
837287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837287
837422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837397: broke SSH to HP devices

[Roland Rosenfeld]

Hi Steinar!

On Sun, 11 Sep 2016, Steinar H. Gunderson wrote:

> Since the upgrade, SSH to all of our HP switches have been broken:
> 
>   rancid@pannekake:~$ hrancid -d duskalhoremye.samfundet.no
>   executing hlogin -t 90 -c"show version;show flash;show 
> system-information;show system information;show module;show stack;show tech 
> transceivers;show config files;show config status;write term" 
> duskalhoremye.samfundet.no
>   duskalhoremye.samfundet.no clogin error: Error: Couldn't login
>   duskalhoremye.samfundet.no clogin error: Error: Couldn't login
>   duskalhoremye.samfundet.no: missed cmd(s): all commands
>   duskalhoremye.samfundet.no: End of run not found
>   ;

This should be fixed by 3.5.1-1 version, which I uploaded to sid two
days ago.

The upstream changelog for 3.5.1 reads:
| 3.5.1
|   hlogin: missed an ssh -c option among the clean-up - Mark Felder

I also prepared a backports version, but I wait until 3.5.1-1 touched
testing before uploading this to the archive.  If you like, you'll
find the backports version on
http://www.spinnaker.de/debian/unoff/rancid.html alternatively you can
install the sid version on jessie, which is also installable.

Please tell me, whether this really fixes this issue, since I don't
have any HP switches available and cannot try this myself...

Greetings

Roland


signature.asc
Description: Digital signature

Bug#837397: marked as done (broke SSH to HP devices)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 14:38:57 +0200
with message-id <20160911123857.ga13...@sesse.net>
and subject line Re: Bug#837397: broke SSH to HP devices
has caused the Debian Bug report #837397,
regarding broke SSH to HP devices
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.)


-- 
837397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rancid
Version: 3.5.0-1
Severity: grave

Hi,

We're running this through the jessie backport (3.5.0-1~bpo8+1), but given that
there are no changes (just a straight rebuild), I guess it should apply to the
base, too.

Since the upgrade, SSH to all of our HP switches have been broken:

  rancid@pannekake:~$ hrancid -d duskalhoremye.samfundet.no
  executing hlogin -t 90 -c"show version;show flash;show 
system-information;show system information;show module;show stack;show tech 
transceivers;show config files;show config status;write term" 
duskalhoremye.samfundet.no
  duskalhoremye.samfundet.no clogin error: Error: Couldn't login
  duskalhoremye.samfundet.no clogin error: Error: Couldn't login
  duskalhoremye.samfundet.no: missed cmd(s): all commands
  duskalhoremye.samfundet.no: End of run not found
  ;

It seems that somehow, it's picking up an empty cipher type and tries to
authenticate with that:

  rancid@pannekake:~$ hlogin -t 90 -c"show version;show flash;show 
system-information;show system information;show module;show stack;show tech 
transceivers" duskalhoremye.samfundet.no 
  duskalhoremye.samfundet.no
  spawn hpuifilter -- ssh -c  -x -l admin duskalhoremye.samfundet.no
  Unknown cipher type ''

  Error: Couldn't login

The only workaround I've found is to force one in .cloginrc for the given
device (nothing else has cyphertype):

  add cyphertype *.samfundet.no3des

But this is highly suboptimal -- it precludes negotiation of the strongest
possible cipher depending on the device.

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

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

Versions of packages rancid depends on:
ii  adduser 3.113+nmu3
ii  cvs 2:1.12.13+real-15
ii  debconf [debconf-2.0]   1.5.56
ii  expect  5.45-6
ii  git 1:2.8.0~rc3+next.20160316-1
ii  iputils-ping [ping] 3:20121221-5+b2
ii  libc6   2.19-18+deb8u4
ii  libperl4-corelibs-perl  0.003-1
ii  openssh-client  1:6.7p1-5+deb8u3
ii  passwd  1:4.2-3+deb8u1
ii  perl5.20.2-3+deb8u6
ii  ssh 1:6.7p1-5+deb8u3

rancid recommends no packages.

Versions of packages rancid suggests:
ii  diffstat  1.58-1

-- Configuration Files:
/etc/rancid/rancid.conf changed [not included]

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 3.5.1-1

On Sun, Sep 11, 2016 at 02:31:33PM +0200, Roland Rosenfeld wrote:
> I also prepared a backports version, but I wait until 3.5.1-1 touched
> testing before uploading this to the archive.  If you like, you'll
> find the backports version on
> http://www.spinnaker.de/debian/unoff/rancid.html alternatively you can
> install the sid version on jessie, which is also installable.
> 
> Please tell me, whether this really fixes this issue, since I don't
> have any HP switches available and cannot try this myself...

3.5.1-1 from sid (running on jessie) does indeed fix the problem.
Marking as such so that BTS versioning has all the right info.

/* Steinar */
-- 
Homepage: https://www.sesse.net/--- End Message ---

Processed: Re: Merge new bug into existing

[Debian Bug Tracking System]

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

> affects 837410 src:python-astropy
Bug #837410 [src:python-scipy] python-astropy: FTBFS in testing (failing tests)
Bug #837008 [src:python-scipy] python-astropy: FTBFS: test failure
Added indication that 837410 affects src:python-astropy
Added indication that 837008 affects src:python-astropy
> thanks
Stopping processing here.

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

Bug#837410: Merge new bug into existing

[Santiago Vila]

affects 837410 src:python-astropy
thanks

On Sun, 11 Sep 2016, Ole Streicher wrote:

> reassign 837410 src:python-scipy
> forcemerge 837008 837410
> thanks

This is fine, but please let's use "affects" as well.

Now the bug will show in the web page for python-astropy and hopefully
nobody else will report it again.

Thanks.

Bug#835774: marked as done (parcimonie: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 12:04:58 +
with message-id 
and subject line Bug#835774: fixed in parcimonie 0.10.2-2
has caused the Debian Bug report #835774,
regarding parcimonie: FTBFS: Tests 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.)


-- 
835774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: parcimonie
Version: 0.10.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> t/91-gpgRecvKeys.t  skipped: these tests are for 
> release candidate testing
> t/author-critic.t . skipped: these tests are for 
> testing by the author
> t/author-eol.t  skipped: these tests are for 
> testing by the author
> t/author-no-tabs.t  skipped: these tests are for 
> testing by the author
> t/author-pod-syntax.t . skipped: these tests are for 
> testing by the author
> 
> Test Summary Report
> ---
> t/32-keyserver_defined_on_command_line.t (Wstat: 256 Tests: 0 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 4 tests but ran 0.
> Files=11, Tests=24,  2 wallclock secs ( 0.02 usr  0.02 sys +  1.71 cusr  0.12 
> csys =  1.87 CPU)
> Result: FAIL
> Failed 1/11 test programs. 0/24 subtests failed.
> dh_auto_test: perl Build test --verbose 1 returned exit code 255
> debian/rules:19: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/parcimonie_0.10.2-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: parcimonie
Source-Version: 0.10.2-2

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated parcimonie 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, 11 Sep 2016 11:28:05 +
Source: parcimonie
Binary: parcimonie
Architecture: source
Version: 0.10.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: intrigeri 
Closes: 835774 836984
Description: 
 parcimonie - privacy-friendly helper to refresh a GnuPG keyring
Changes:
 parcimonie (0.10.2-2) unstable; urgency=medium
 .
   * Add {build,runtime} dependency on gnupg2, that provides
 the /usr/bin/gpg2 alias (Closes: #836984).
   * Add {build,runtime} dependency on dirmngr, that's needed
 for network operations with GnuPG 2.1+.
   * New patch: honor custom GnuPG homedir in a few places
 that did not so far (Closes: #835774).
Checksums-Sha1: 
 3ea998db3ed8653f49402cbfea89d6150611c81d 2680 parcimonie_0.10.2-2.dsc
 21f4a8c762c4ebc3105a4d1857f8c5726d8514f9 69432 
parcimonie_0.10.2-2.debian.tar.xz
Checksums-Sha256: 
 827e8fa393a712afe220dd03ce3189c50a607b09c0b9dba5285108aa22b73aa1 2680 
parcimonie_0.10.2-2.dsc
 8dc5ebc3052541fa0747cb48b5f3b27406ba8e10e338ae98a6acea9a9f7cd803 69432 
parcimonie_0.10.2-2.debian.tar.xz
Files: 
 18c0024146aefbfbe768dfe843a12b1c 2680 net optional parcimonie_0.10.2-2.dsc
 363595a97893a15184b1a67aa959b40e 69432 net optional 
parcimonie_0.10.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX1UXkAAoJEOxtg78p/CqOG8EQAJgjNHx2LnxXc/eQW/vTcNZn

Bug#836984: marked as done (parcimonie unable to call "gpg2" since sid switch to using gpg2 as main "gpg" command)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 12:04:58 +
with message-id 
and subject line Bug#836984: fixed in parcimonie 0.10.2-2
has caused the Debian Bug report #836984,
regarding parcimonie unable to call "gpg2" since sid switch to using gpg2 as 
main "gpg" command
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.)


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

Hi there,

Ever since gnupg 2.1 was set to be the main "gpg" command in sid, parcimonie 
has been unable to do its bidding.

>From the process list, we can see the following:

gabster   6219  0.1  1.2 129352 48700 pts/1S+   15:07   0:00  \_ 
/usr/bin/perl /usr/bin/parcimonie --with-dbus
gabster   6220  0.0  0.0  0 0 pts/1Z+   15:07   0:00  \_ 
[gpg] 

and it just hangs there.

If I call the command manually I get the following output:

$ /usr/bin/parcimonie --with-dbus
gpgconf: warning: can not open list file 
/home/gabster/.gnupg/dirmngr_ldapservers.conf: No such file or directory
dirmngr:Key Acquirer:/usr/bin/dirmngr:1:1:
Can't exec "gpg2": No such file or directory at 
/usr/share/perl5/GnuPG/Interface.pm line 301.
exec() error: No such file or directory at /usr/share/perl5/GnuPG/Interface.pm 
line 301.
No public key was found. at /usr/share/perl5/App/Parcimonie/Daemon.pm line 420.

So apparently it's trying to call a gpg2 binary which doesn't exist anymore:

$ find /usr/bin/ -name gpg\*
/usr/bin/gpgconf
/usr/bin/gpgsplit
/usr/bin/gpgsm
/usr/bin/gpg
/usr/bin/gpg-connect-agent
/usr/bin/gpg-agent
/usr/bin/gpgparsemail
/usr/bin/gpg-zip
/usr/bin/gpgv
/usr/bin/gpg1

So I guess we either need to call "gpg" directly or somehow get the "gpg2"
alias to come back. Or maybe there's an even better solution that I'm not
thinking about since I don't know much about the code base and used libraries.

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

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

Versions of packages parcimonie depends on:
ii  libclone-perl0.38-2
ii  libconfig-general-perl   2.63-1
ii  libfile-homedir-perl 1.00-1
ii  libfile-which-perl   1.21-1
ii  libgnupg-interface-perl  0.52-3
ii  libipc-system-simple-perl1.25-3
ii  liblist-moreutils-perl   0.416-1
ii  libmoo-perl  2.002004-1
ii  libmoox-late-perl0.015-2
ii  libmoox-options-perl 4.022-2
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.094-1
ii  libtime-duration-parse-perl  0.13-1
ii  libtry-tiny-perl 0.27-1
ii  libtype-tiny-perl1.05-1
ii  libtypes-path-tiny-perl  0.005-1
ii  perl 5.22.2-4
ii  torsocks 2.1.0-2

Versions of packages parcimonie recommends:
ii  gnupg-curl  1.4.20-6
ii  libglib-perl3:1.321-1
ii  libgtk3-perl0.028-1
ii  liblocale-gettext-perl  1.07-3
ii  libnet-dbus-glib-perl   0.33.0-2
ii  libnet-dbus-perl1.1.0-4
ii  libpango-perl   1.227-1
ii  libtime-duration-perl   1.20-1
ii  tor 0.2.8.7-1

parcimonie suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: parcimonie
Source-Version: 0.10.2-2

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated parcimonie 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, 11 Sep 2016 11:28:05 +
Source: parcimonie
Binary: parcimonie
Architecture: 

Processed: Merge new bug into existing

[Debian Bug Tracking System]

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

> reassign 837410 src:python-scipy
Bug #837410 [src:python-astropy] python-astropy: FTBFS in testing (failing 
tests)
Bug reassigned from package 'src:python-astropy' to 'src:python-scipy'.
No longer marked as found in versions python-astropy/1.2.1-1.
Ignoring request to alter fixed versions of bug #837410 to the same values 
previously set
> forcemerge 837008 837410
Bug #837008 [src:python-scipy] python-astropy: FTBFS: test failure
Bug #837410 [src:python-scipy] python-astropy: FTBFS in testing (failing tests)
Set Bug forwarded-to-address to 'https://github.com/scipy/scipy/issues/6420'.
Added indication that 837410 affects python-astropy
Marked as found in versions python-scipy/0.18.0-1.
Added tag(s) stretch, patch, and sid.
Merged 837008 837410
> thanks
Stopping processing here.

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

Bug#837410: python-astropy: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:python-astropy
Version: 1.2.1-1
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
debian/rules:31: warning: overriding recipe for target 'override_dh_auto_build'
debian/rules:22: warning: ignoring old recipe for target 
'override_dh_auto_build'
dh build-indep --with python2,python3,sphinxdoc
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
debian/rules:31: warning: overriding recipe for target 'override_dh_auto_build'
debian/rules:22: warning: ignoring old recipe for target 
'override_dh_auto_build'
python2.7 setup.py build --use-system-libraries
/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py:273: UserWarning: 
Matplotlib is building the font cache using fc-list. This may take a moment.

[... snipped ...]

../docs/utils/iers.rst PASSED
../docs/utils/index.rst PASSED
../docs/utils/numpy.rst PASSED
../docs/visualization/histogram.rst PASSED
../docs/visualization/index.rst PASSED
../docs/visualization/normalization.rst PASSED
../docs/vo/index.rst PASSED
../docs/vo/conesearch/client.rst PASSED
../docs/vo/conesearch/index.rst PASSED
../docs/vo/conesearch/validator.rst PASSED
../docs/vo/samp/advanced_embed_samp_hub.rst PASSED
../docs/vo/samp/example_clients.rst PASSED
../docs/vo/samp/example_hub.rst PASSED
../docs/vo/samp/example_table_image.rst PASSED
../docs/vo/samp/index.rst PASSED
../docs/wcs/history.rst PASSED
../docs/wcs/index.rst PASSED
../docs/wcs/relax.rst PASSED
../docs/whatsnew/0.1.rst PASSED
../docs/whatsnew/0.2.rst PASSED
../docs/whatsnew/0.3.rst PASSED
../docs/whatsnew/0.4.rst PASSED
../docs/whatsnew/1.0.rst PASSED
../docs/whatsnew/1.1.rst PASSED
../docs/whatsnew/1.2.rst PASSED
../docs/whatsnew/index.rst PASSED

=== FAILURES ===
_ test_circmean_against_scipy __

@pytest.mark.skipif('not HAS_SCIPY')
def test_circmean_against_scipy():
# testing against scipy.stats.circmean function
data = np.random.uniform(-np.pi, np.pi, size=(100, 5))
answer = scipy.stats.circmean(data, np.pi, -np.pi)
>   assert_equal(np.around(answer, 2), np.around(circmean(data), 2))
E   AssertionError: 
E   Items are not equal:
EACTUAL: -4.3096
EDESIRED: 1.97

astropy/stats/tests/test_circstats.py:45: AssertionError
= 1 failed, 11041 passed, 225 skipped, 43 xfailed, 2 xpassed in 180.25 seconds =
debian/rules:56: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 1
make[1]: Leaving directory '/<>'
debian/rules:14: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I assume that using -A has nothing to do with this, because there are
also failed build logs in the reproducible builds autobuilders:

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

This used to build in the past in stretch but now it always fails for me:

Status: successful  python-astropy_1.2.1-1_amd64-20160812T1540Z
Status: successful  python-astropy_1.2.1-1_amd64-20160817T0957Z
Status: successful  python-astropy_1.2.1-1_amd64-20160823T020145Z
Status: successful  python-astropy_1.2.1-1_amd64-20160901T134940Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T031848Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T104211Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T104219Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T104235Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T104741Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T104800Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T104818Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T105319Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T105344Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T105356Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T105846Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T105919Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T105930Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T110411Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T110453Z
Status: failed  python-astropy_1.2.1-1_amd64-20160911T110506Z

So maybe some build-dependency is breaking python-astropy.
(I hope it's not diffutils, which I also added to the stretch
chroot as an exception even if it did not reach testing yet).

I attach my own full build log, but you can get more 

Bug#836587: Additional Info on bug

[Vince Barwinski]

Hi there

I recently tried to compile mysql-workbench. However, I was unsuccessful.

About 10 or so minutes into executing the "make" command after executing
"cmake -DCMAKE_INSTALL_PREFIX=/usr/local", I got the following error output:

/home/vince/backup_files/linux/debian/mysql_gui/mysql-workbench-community-6.3.7-src/library/grt/src/grtpp_undo_manager.h:358:57:
note: in C++11 destructors default to noexcept
[ 51%] Building CXX object
backend/wbpublic/CMakeFiles/wbpublic.dir/objimpl/workbench.physical/workbench_physical_ViewFigure.cpp.o
[ 51%] Building CXX object
backend/wbpublic/CMakeFiles/wbpublic.dir/objimpl/workbench.logical/workbench_logical_Model.cpp.o
[ 51%] Building CXX object
backend/wbpublic/CMakeFiles/wbpublic.dir/objimpl/workbench.logical/workbench_logical_Diagram.cpp.o
[ 51%] Building CXX object
backend/wbpublic/CMakeFiles/wbpublic.dir/objimpl/db.query/db_query_Resultset.cpp.o
/home/vince/backup_files/linux/debian/mysql_gui/mysql-workbench-community-6.3.7-src/backend/wbpublic/objimpl/db.query/db_query_Resultset.cpp:
In constructor
‘CPPResultsetResultset::CPPResultsetResultset(db_query_ResultsetRef,
boost::shared_ptr)’:
/home/vince/backup_files/linux/debian/mysql_gui/mysql-workbench-community-6.3.7-src/backend/wbpublic/objimpl/db.query/db_query_Resultset.cpp:364:14:
error: ‘JSON’ is not a member of ‘sql::DataType’
 case sql::DataType::JSON:
  ^~~
backend/wbpublic/CMakeFiles/wbpublic.dir/build.make:2798: recipe for target
'backend/wbpublic/CMakeFiles/wbpublic.dir/objimpl/db.query/db_query_Resultset.cpp.o'
failed
make[2]: ***
[backend/wbpublic/CMakeFiles/wbpublic.dir/objimpl/db.query/db_query_Resultset.cpp.o]
Error 1
CMakeFiles/Makefile2:359: recipe for target
'backend/wbpublic/CMakeFiles/wbpublic.dir/all' failed
make[1]: *** [backend/wbpublic/CMakeFiles/wbpublic.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2

I think the critical error message here (if any) is:

Resultset.cpp:364:14: error: ‘JSON’ is not a member of ‘sql::DataType’.

I hope this helps in some way.

Cheers

Processed: Re: Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: 
rename involves overwriting `/usr/bin/qgis'
Added tag(s) pending.

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

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 09/11/2016 01:59 AM, Andreas Beckmann wrote:
> looks like you are doing a more complicated diversion transition ...

Yes. And a lovely mess it has created now that we don't need it any
more. The situation is complicated by the fact that upstream moved the
diversion around in non-LTRs which were never in Debian. Fortunately we
don't have to care about the upstream use-case in Debian.


The jessie version (2.4.0-1) added the diversion in
qgis-plugin-grass.preinst:

 if [ "$1" = "install" -o "$1" = "upgrade" ]; then
 dpkg-divert --package qgis-plugin-grass --add --rename \
 --divert /usr/bin/qgis.bin /usr/bin/qgis
 dpkg-divert --package qgis-plugin-grass --add --rename \
 --divert /usr/bin/qbrowser.bin /usr/bin/qbrowser
 fi

And removed it qgis-plugin-grass.postrm:

 if [ "$1" = "remove" ]; then
 dpkg-divert --package qgis-plugin-grass --remove --rename \
 --divert /usr/bin/qgis.bin /usr/bin/qgis
 dpkg-divert --package qgis-plugin-grass --remove --rename \
 --divert /usr/bin/qbrowser.bin /usr/bin/qbrowser
 fi


The sid version (2.14.6+dfsg-1) just removed it in qgis.preinst:

 if [ "$1" = "install" -o "$1" = "upgrade" ]; then
 # Remove obsolete diversions
 for i in /usr/bin/qgis /usr/bin/qbrowser; do
 pkg=$(dpkg-divert --listpackage $i)
 if [ -n "$pkg" -a "$pkg" = qgis-plugin-grass -o \
   "$pkg" = qgis-provider-grass ]; then
 dpkg-divert --package $pkg --rename --remove $i
 fi
 done
 fi

The above has been moved in -2 to postinst, which doesn't get called
with the install or upgrade arguments, which I've not fixed by checking
for the configure argument.

It seems the underlaying issue was not removing the diversion in prerm
as well, I've now added that too. If that is still not sufficient to fix
this issue, I guess we need the removals in qgis-plugin-grass package too.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#836384: marked as done (ignition-transport: breaks with new protobuf3, and link failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 10:55:10 + (UTC)
with message-id <1711172147.5515436.1473591310...@mail.yahoo.com>
and subject line Re: Bug#836384: Info received (Bug#836384 closed by Jose Luis 
Rivero  (Bug#836384: fixed in ignition-transport 
1.3.0-4))
has caused the Debian Bug report #836384,
regarding ignition-transport: breaks with new protobuf3, and link 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.)


-- 
836384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ignition-transport
Version: 1.3.0-2
Severity: serious

Hi, the latest protobuf3 broke ignition-transport testsuite and package, lets 
analyze the issues:
(based on the main on debian/tests
#include 

int main()
{
// Create a transport node.
ignition::transport::Uuid uuid;
return 0;
}



first issue:
./build 
In file included from 
/usr/include/ignition/transport1/ignition/transport/NodeShared.hh:40:0,
from /usr/include/ignition/transport1/ignition/transport/Node.hh:41,
from /usr/include/ignition/transport1/ignition/transport.hh:9,
from igntest.c:1:
/usr/include/ignition/transport1/ignition/transport/RepHandler.hh:38:41: fatal 
error: google/protobuf/stubs/casts.h: No such file or directory
#include 
^


this file has been deleted in new protobuf I guess
(removing that line from the hh file works a little better)

that said, the second issue is:
pkg-config --cflags --libs ignition-transport1
-std=c++11 -I/usr/include/ignition/transport1 -lignition-transport1 -l1


that -l1 breaks the build, lets see:
./build 
/usr/bin/ld: cannot find -l1



g++ -o igntest igntest.c `pkg-config --cflags --libs ignition-transport1`
/usr/bin/ld: cannot find -l1
collect2: error: ld returned 1 exit status



removing it works:
g++ -o igntest igntest.c -std=c++11 -I/usr/include/ignition/transport1 
-lignition-transport1
./igntest
echo $?


As usual, please let me know if you have a fix or you need further details

thanks,
G.
--- End Message ---
--- Begin Message ---


Seems that the testsuite is incompatible with the old protobuf 2,
closing

G.--- End Message ---

Bug#837020: marked as done (liblightify: FTBFS: doxygen-include.am:47: error: DX_COND_doc does not appear in AM_CONDITIONAL)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 10:50:11 +
with message-id 
and subject line Bug#837020: fixed in liblightify 0~git20160911-1
has caused the Debian Bug report #837020,
regarding liblightify: FTBFS: doxygen-include.am:47: error: DX_COND_doc does 
not appear in AM_CONDITIONAL
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.)


-- 
837020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblightify
Version: 0~git20160607-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 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  --with autoreconf
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
> aclocal: warning: couldn't open directory 'm4': No such file or directory
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> libtoolize: copying file 'build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:24: installing 'build-aux/compile'
> configure.ac:86: installing 'build-aux/config.guess'
> configure.ac:86: installing 'build-aux/config.sub'
> configure.ac:11: installing 'build-aux/install-sh'
> configure.ac:11: installing 'build-aux/missing'
> configure.ac:9: installing 'build-aux/tap-driver.sh'
> doxygen-include.am:47: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:53: error: DX_COND_html does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:63: error: DX_COND_chm does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:67: error: DX_COND_chi does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:79: error: DX_COND_man does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:89: error: DX_COND_rtf does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:99: error: DX_COND_xml does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:109: error: DX_COND_ps does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:138: error: DX_COND_pdf does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:167: error: DX_COND_latex does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> Makefile.am:4: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:18: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am: installing 'build-aux/depcomp'
> parallel-tests: installing 'build-aux/test-driver'
> autoreconf: automake failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/liblightify_0~git20160607-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: liblightify
Source-Version: 0~git20160911-1

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

Debian distribution maintenance software
pp.
Tobias Frost  

Processed: Re: bzr: FTBFS: Tests failures

[Debian Bug Tracking System]

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

> tags 837268 + patch
Bug #837268 [src:bzr] bzr: FTBFS: Tests failures
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#837268: bzr: FTBFS: Tests failures

[Santiago Vila]

tags 837268 + patch
thanks

On Sat, 10 Sep 2016, Lucas Nussbaum wrote:

> Traceback (most recent call last):
>   File 
> "/<>/bzr-2.7.0+bzr6619/build/lib.linux-x86_64-2.7/bzrlib/tests/test_diff.py",
>  line 317, in test_external_diff_binary
> self.assertEqual(2, pipe.returncode)
>   File 
> "/<>/bzr-2.7.0+bzr6619/build/lib.linux-x86_64-2.7/bzrlib/tests/__init__.py",
>  line 1370, in assertEqual
> pprint.pformat(a), pprint.pformat(b)))
> AssertionError: not equal:
> a = 2
> b = 1

The reason this happens may be found in the changelog for
diffutils 1:3.5-1: diff now exit with status 1 when binary files
differ (as mandated by POSIX).

The attached patch might fix this, but I have not tested it.

> Tags: stretch sid

This bug should not happen in stretch (yet) because diffutils 3.5
has not entered stretch (yet), are you sure it's correct to tag
it stretch in those cases?

Thanks.diff --git a/bzrlib/tests/test_diff.py b/bzrlib/tests/test_diff.py
index 0811aca..bfa68b1 100644
--- a/bzrlib/tests/test_diff.py
+++ b/bzrlib/tests/test_diff.py
@@ -313,8 +313,8 @@ class TestDiffFiles(tests.TestCaseInTempDir):
 pipe = subprocess.Popen(cmd, stdout=subprocess.PIPE,
  stdin=subprocess.PIPE)
 out, err = pipe.communicate()
-# Diff returns '2' on Binary files.
-self.assertEqual(2, pipe.returncode)
+# Diff from diffutils >= 3.5 returns '1' on Binary files.
+self.assertEqual(1, pipe.returncode)
 # We should output whatever diff tells us, plus a trailing newline
 self.assertEqual(out.splitlines(True) + ['\n'], lines)
 
diff --git a/debian/control b/debian/control
index 9d54e83..59245b0 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends: bash-completion,
ca-certificates,
cython-dbg | python-pyrex,
debhelper (>= 9),
+   diffutils (>= 1:3.5),
fdupes,
python (>= 2.6.6-3),
python-all-dbg (>= 2.6.6-3),

Bug#837397: broke SSH to HP devices

[Steinar H. Gunderson]

Package: rancid
Version: 3.5.0-1
Severity: grave

Hi,

We're running this through the jessie backport (3.5.0-1~bpo8+1), but given that
there are no changes (just a straight rebuild), I guess it should apply to the
base, too.

Since the upgrade, SSH to all of our HP switches have been broken:

  rancid@pannekake:~$ hrancid -d duskalhoremye.samfundet.no
  executing hlogin -t 90 -c"show version;show flash;show 
system-information;show system information;show module;show stack;show tech 
transceivers;show config files;show config status;write term" 
duskalhoremye.samfundet.no
  duskalhoremye.samfundet.no clogin error: Error: Couldn't login
  duskalhoremye.samfundet.no clogin error: Error: Couldn't login
  duskalhoremye.samfundet.no: missed cmd(s): all commands
  duskalhoremye.samfundet.no: End of run not found
  ;

It seems that somehow, it's picking up an empty cipher type and tries to
authenticate with that:

  rancid@pannekake:~$ hlogin -t 90 -c"show version;show flash;show 
system-information;show system information;show module;show stack;show tech 
transceivers" duskalhoremye.samfundet.no 
  duskalhoremye.samfundet.no
  spawn hpuifilter -- ssh -c  -x -l admin duskalhoremye.samfundet.no
  Unknown cipher type ''

  Error: Couldn't login

The only workaround I've found is to force one in .cloginrc for the given
device (nothing else has cyphertype):

  add cyphertype *.samfundet.no3des

But this is highly suboptimal -- it precludes negotiation of the strongest
possible cipher depending on the device.

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

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

Versions of packages rancid depends on:
ii  adduser 3.113+nmu3
ii  cvs 2:1.12.13+real-15
ii  debconf [debconf-2.0]   1.5.56
ii  expect  5.45-6
ii  git 1:2.8.0~rc3+next.20160316-1
ii  iputils-ping [ping] 3:20121221-5+b2
ii  libc6   2.19-18+deb8u4
ii  libperl4-corelibs-perl  0.003-1
ii  openssh-client  1:6.7p1-5+deb8u3
ii  passwd  1:4.2-3+deb8u1
ii  perl5.20.2-3+deb8u6
ii  ssh 1:6.7p1-5+deb8u3

rancid recommends no packages.

Versions of packages rancid suggests:
ii  diffstat  1.58-1

-- Configuration Files:
/etc/rancid/rancid.conf changed [not included]

-- debconf-show failed

Bug#836945: marked as done (python-taurus: missing copyright file)

[Debian Bug Tracking System]

Your message dated Sun, 11 Sep 2016 10:09:49 +
with message-id 
and subject line Bug#836945: fixed in taurus 4.0.1+dfsg-2
has caused the Debian Bug report #836945,
regarding python-taurus: missing copyright file
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.)


-- 
836945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-taurus
Version: 4.0.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package misses the
/usr/share/doc/python-taurus/copyright file.


Andreas


python-taurus_4.0.1+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: taurus
Source-Version: 4.0.1+dfsg-2

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated taurus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Sep 2016 09:39:56 +0200
Source: taurus
Binary: python-taurus python-taurus-doc
Architecture: source
Version: 4.0.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 python-taurus - Framework for scientific/industrial CLIs and GUIs - Python2
 python-taurus-doc - Framework for scientific/industrial CLIs and GUIs - 
Documentation
Closes: 836945
Changes:
 taurus (4.0.1+dfsg-2) unstable; urgency=medium
 .
   * Updated debian/rules to avoid missing copyright file (Closes: #836945)
Checksums-Sha1:
 6a4583b00a5e45da80f4d8fc309051cc6c151696 2349 taurus_4.0.1+dfsg-2.dsc
 6f7b1bdf5495ced50cfabe37cb7874c97fc83f37 17212 
taurus_4.0.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 a046581778810258e46a68c8ad75ab9560328f001df09bef0d230b27e9df578b 2349 
taurus_4.0.1+dfsg-2.dsc
 ebc97902894ac64d94976f7bf109d8ab33c7eb4be3fa841b09347b569556398a 17212 
taurus_4.0.1+dfsg-2.debian.tar.xz
Files:
 fc3168be21e80596e7abf8797ce47eeb 2349 science extra taurus_4.0.1+dfsg-2.dsc
 cf0f09715316927adf4934eb40df14f8 17212 science extra 
taurus_4.0.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX1RSeAAoJEFYykG9GluAVL8EP/3IyG1urEWZvQUR39kpAJxhG
yuMA2XLxytsQ6ayn3tLFfGBUuSc7kvXLf9MwTM7VJOKi/qrAE0RFg3FANGJWVG23
/zqzNS+YsfwjBLBvruuCoWKbU6q3WRNZgn8WJ8apnzQVenj53Zto08B8RSdWRwlP
ajVcqwdpkc9vpJPqIHHetkx475PMO0jtBj6Ag/DEC7/Jm634d6hi6xHR+O6N2z27
0Pk0D956EExccpCi/jpfIghVXQhfrj4gzKoAZ/LcDin69DuarSypUNaZWOHCxV7j
/oc4K7BLJjwxi/PmPhKuhECj8U7U2IOaa2I2z1brYAtbdhbJiqCtrfti240dVpNl
QsJx08g8y2NF6Xzf4H9zM+yk2ws1dKeTfR1Dnklmx6ITjilHgHHXGNGPWVhl2rIx
gtOoKlxCZpfEd5b5kOEB4QAjqW/Ohm3eFbSHGt3rEFkd7VDYz6aZlSLhTpb+BM+k
aG2yR1cgqBjZ+NbfbNyBY7daF6LbmII38RVAmGQC4LgBqzIeYaet+JgBM8Mq0XgC
5FDTx5+RyprIChu3dBvRKz7blkaOFxR91svB7rPJrx8ZJLvkhvlfFCE9Tif6Wl2v
UfIU8FSgFufjnY35qh4DLz67HjPeZih+7u8PE0FkG+yOCtCRSW7/ejPGQu382LDp
O3zysVt1YnixNABgIju0
=1mJD
-END PGP SIGNATURE End Message ---

Processed: user debian...@lists.debian.org, usertagging 835903, found 832338 in 3:9.0.1-2, usertagging 835992 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 835903 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 832338 3:9.0.1-2
Bug #832338 [openstack-dashboard] FTBFS & runtime crash with Django 1.10
Marked as found in versions horizon/3:9.0.1-2.
> usertags 835992 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 837116 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 837116 + nvidia-legacy-304xx-kernel-source 
> nvidia-legacy-340xx-kernel-source
Bug #837116 [nvidia-kernel-source] nvidia-kernel-source: cannot be installed 
from jessie-backports due to make:any dependency
Added indication that 837116 affects nvidia-legacy-304xx-kernel-source and 
nvidia-legacy-340xx-kernel-source
> found 837116 304.131-8~bpo8+1
Bug #837116 [nvidia-kernel-source] nvidia-kernel-source: cannot be installed 
from jessie-backports due to make:any dependency
There is no source info for the package 'nvidia-kernel-source' at version 
'304.131-8~bpo8+1' with architecture ''
Unable to make a source version for version '304.131-8~bpo8+1'
Marked as found in versions 304.131-8~bpo8+1.
> found 837116 340.96-9~bpo8+1
Bug #837116 [nvidia-kernel-source] nvidia-kernel-source: cannot be installed 
from jessie-backports due to make:any dependency
There is no source info for the package 'nvidia-kernel-source' at version 
'340.96-9~bpo8+1' with architecture ''
Unable to make a source version for version '340.96-9~bpo8+1'
Marked as found in versions 340.96-9~bpo8+1.
> thanks
Stopping processing here.

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

Processed: Re: mpi4py 2.0.0 test failure in Debian

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #830440 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe
Added tag(s) patch.

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

Bug#830440: mpi4py 2.0.0 test failure in Debian

[Sebastiaan Couwenberg]

Control: tags -1 patch

Hi Lisandro,

Thanks for the feedback.

On 09/11/2016 10:38 AM, Lisandro Dalcin wrote:
> I've got this issue report, look at my comment for a link to the patch.
> 
> https://bitbucket.org/mpi4py/mpi4py/issues/50/is-new-release-210-coming

I don't think your suggested patch is going to fix the issue, because
the Debian package already contains a patch to use libm.so.6 instead:

 https://sources.debian.net/src/mpi4py/2.0.0-2/debian/patches/up_libm/

The nosetests simply hang in schroot build environment as used on the
Debian build daemons and porterboxes. I addded a patch to tag all test
classes and skip them in schroot environments, and the python nosetests
command still hung.

I think that for now the tests should be skipped in schroot
environments, to fix the build failure on the Debian build daemons and
unblock the rebuilds of the mpi4py reverse dependencies. As I mentioned
in the Debian bugreport, the tests succeed in cowbuilder chroots, so I
chose to only skip the tests in schroot.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


mpi4py_2.0.0-2_skip-tests-in-schroot.patch
Description: inode/symlink

Processed: your mail

[Debian Bug Tracking System]

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

> tags 837282 + pending - help
Bug #837282 [src:pagekite] pagekite: FTBFS: AttributeError: 'module' object has 
no attribute 'Handler'
Added tag(s) pending.
Bug #837282 [src:pagekite] pagekite: FTBFS: AttributeError: 'module' object has 
no attribute 'Handler'
Removed tag(s) help.
> thanks
Stopping processing here.

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

Processed: libopenmpi-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/openmpi/lib/mpi.mod

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libparmetis-dev parmetis-test
Bug #837392 [libopenmpi-dev] libopenmpi-dev: fails to upgrade from 'jessie' - 
trying to overwrite /usr/lib/openmpi/lib/mpi.mod
Added indication that 837392 affects libparmetis-dev and parmetis-test

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

Processed: tagging 835774

[Debian Bug Tracking System]

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

> tags 835774 + confirmed
Bug #835774 [src:parcimonie] parcimonie: FTBFS: Tests failures
Added tag(s) confirmed.
> thanks
Stopping processing here.

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