Bug#817694: marked as done (tinymux: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 23:48:55 -0600
with message-id 

Bug#825701: should osptoolkit be removed from Debian?

['Mattia Rizzolo']

On Mon, Jun 27, 2016 at 09:07:31AM +0800, Di-Shi Sun wrote:
> Hi Mattia,
> 
> We went through the list and met one issue,
> 
> dpkg-genchanges: warning: package osptoolkit-dbgsym listed in files list but
> not in control info
> dpkg-genchanges: warning: package libosptk4-dbgsym listed in files list but
> not in control info

this one is a red herring.  FYI this is already fixed in dpkg's git (not
publically).

> All others look fine.

yep indeed)

> The updated packages have been uploaded to mentors.

I tweaked d/changelog to keep only one paragraph, as the others refers
to non-uploaded versions, see the attached diff.
And uploaded :)
I'll make sure to close this bug by myself once accepted (as it has to
go through NEW

> BTW, we believe #555877 have been fixed in 3.4.2-1.1 by explicitly linking
> external libraries.

ok, I'm closing it, then.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#828624: [Pkg-samba-maint] Bug#828624: samba: Service fails to install and start

[Christian PERRIER]

Quoting Marc J. Driftmeyer (m...@reanimality.com):

> Gotta love when testing isn't thorough.


What exactly was your intention when adding this information to this
already reported bug?




signature.asc
Description: PGP signature

Processed: forcibly merging 828137 828624

[Debian Bug Tracking System]

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

> forcemerge 828137 828624
Bug #828137 [samba] samba does not install and fails to start
Bug #828624 [samba] samba: samba-ad-dc.service shouldn't be enabled by default
Severity set to 'grave' from 'serious'
Added tag(s) confirmed.
Merged 828137 828624
> thanks
Stopping processing here.

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

Bug#817694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817694

[brazilofmux]

Regarding tinymux: Removal of debhelper compat 4, the 2.6.5.34-1.1 version of 
TinyMUX in testing is at compact level 9. It should be not be flagged for 
autoremoval.


Thanks,

Stephen Dennis

Processed: Re: [Pkg-gridengine-devel] Bug#826113: bugfix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #826113 [gridengine-common] gridengine-common: postinst uses /usr/share/doc 
content (Policy 12.3): 
/usr/share/doc/gridengine-common/examples/gridengine.default
Added tag(s) pending.

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

Bug#826113: [Pkg-gridengine-devel] Bug#826113: bugfix

[Afif Elghraoui]

Control: tag -1 + pending

Hello,

على الأحد 26 حزيران 2016 ‫19:45، كتب Carl Pupa:
> 
> When I applied your patch, did debuild, and then ran piuparts -d stretch 
> on the gridengine-common*.deb, I got the following, indicating that it 
> was still looking for the gridengine.default file:

Yeah, I noticed that while running piuparts earlier today. Fortunately,
I fixed it before upload.

> 
>update-alternatives: using /bin/tcsh to provide /bin/csh (csh) in 
> auto mode
>Setting up gridengine-common (8.1.8+dfsg-6) ...
>ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
>sed: can't read /usr/share/gridengine-common/gridengine.default: No 
> such file or directory

I needed to have /usr/share/gridengine/..., instead of
/usr/share/gridengine-common/... here

[...]

Anyway, thanks for taking a look! I uploaded the package earlier today
with the corrected patch. The latest changes should already be in git,
but the package itself needs ftpmaster approval before it can enter the
archive because I added a new binary package (gridengine-dev).


Thanks and regards
Afif

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

Bug#826113: [Pkg-gridengine-devel] Bug#826113: bugfix

[Carl Pupa]

Hello Afif,

When I applied your patch, did debuild, and then ran piuparts -d stretch 
on the gridengine-common*.deb, I got the following, indicating that it 
was still looking for the gridengine.default file:


  update-alternatives: using /bin/tcsh to provide /bin/csh (csh) in 
auto mode

  Setting up gridengine-common (8.1.8+dfsg-6) ...
  ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be 
preloaded (cannot open shared object file): ignored.
  sed: can't read /usr/share/gridengine-common/gridengine.default: No 
such file or directory

  dpkg: error processing package gridengine-common (--configure):
   subprocess installed post-installation script returned error exit 
status 2

  Processing triggers for libc-bin (2.22-11) ...
  Errors were encountered while processing:
   gridengine-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)

--Carl

On 6/25/16 8:25 PM, Afif Elghraoui wrote:


على السبت 25 حزيران 2016 ‫16:35، كتب Carl Pupa:

In that case I agree it doesn't really matter whether gridengine.default
is in examples or not.  I've attached a patch that simply change the
postinst script so that it takes the copy from
/usr/share/gridengine-common/ instead of /usr/share/doc/gridengine-common/.

This is close. Attached is what I had in mind as a complete solution. It
installs gridengine.default into /usr/share/gridengine-common/, does not
install it into /usr/share/doc/gridengine-common/examples/, and adjusts
the postinst script (like your patch did).

The debian/*examples and debian/*install files are used by
dh_installexamples(1) and dh_install(1), respectively, during the
package build. debhelper(7) has a list of similar commands.

Does this look good to you? I haven't tested it, but it looks ok to me.

Many thanks and regards
Afif

Bug#825701: should osptoolkit be removed from Debian?

[Di-Shi Sun]

Hi Mattia,

We went through the list and met one issue,

dpkg-genchanges: warning: package osptoolkit-dbgsym listed in files list but
not in control info
dpkg-genchanges: warning: package libosptk4-dbgsym listed in files list but
not in control info

All others look fine. 

The updated packages have been uploaded to mentors.

BTW, we believe #555877 have been fixed in 3.4.2-1.1 by explicitly linking
external libraries.

Thanks,

Di-Shi Sun.

-Original Message-
From: 'Mattia Rizzolo' [mailto:mat...@debian.org] 
Sent: Thursday, June 23, 2016 6:47 PM
To: Di-Shi Sun
Cc: 825...@bugs.debian.org; 'Support of Transnexus'
Subject: Re: Bug#825701: should osptoolkit be removed from Debian?

On Thu, Jun 23, 2016 at 05:26:12PM +0800, Di-Shi Sun wrote:
> Sorry for the delay. We just fixed the upload issues on 
> mentors.debian.net. You can find it at 
> https://mentors.debian.net/package/osptoolkit
> 
> There are several thing about the warning messages on 
> mentors.debian.net 1. no-upstream-changelog. The upstream source package
includes RELNOTES.txt for its changes. I am not sure if we must put all the
change info into debian/changelog.

https://www.debian.org/doc/debian-policy/ch-docs.html#s-changelogs
There is a dh_installchangelog utility, you should use it to install
RELNOTES.txt
*but* that file clearly has not been updated in a long time, so it's
probably more harmful than anything to ship it, so ignore that message.

> 3. A watch file is present but doesn't work. We tested the watch file on
our boxes. I do not know why mentors.debian.net thought it does not work.

Because mentors.d.n runs on wheezy, and there uscan is not newer enough to
work with version=4 files.

> BTW, we did not see any of these warning when we run lintian on our boxes.

Depends on level of "pendicness" you ask lintian.

> Please let us know if there is anything should be modified.

I'd like to ask you a few things, following newer best practise in debian
packaging:

* drop the -dbg package: nowdays debhelper automatically builds -dbgsym
  packages (though they are not installed in the main debian archive,
  but in a separate "debug archive")
  https://wiki.debian.org/AutomaticDebugPackages
* try dropping all the debian/*dirs files: they are usually useless, as
  debhelper tools take care of creating needed directories before
  installing files; is my personal belief that if you need such files
  thare are good chances your build system is buggy.  I tried and it
  fails to build, so I suggest you to put on your todo to make your
  build system more clever and create the needed directories.
* d/patches/test_app.c.patch: I can't think why that would be
  'Forwarded: not-needed', why can't you apply that upstream?
* please rename d/docs to d/osptoolkit.docs: d/docs is a very confusing
  file name because it makes you think that it install the docs in all
  produced binaries, while instead it only install them in the first
  package list in d/control... (I had a lot of people thinking it wrong,
  so I now advocate for renaming)
* versioned -dev packages usually bring only pain during transitions, as
  they require source changes to all reverse-dependency to change
  build-depends.  I appreciate that you don't have this problem as you
  don't have reverse-depends, but I wonder if you can take this occasion
  to rename the -dev package to just 'libosptk-dev'.  BTW, in both cases
  you should add a Conflicts: against the old -dev package, as both ship
  the same files, and so can't be installed toghether (I prefer a
  Conflicts (or Conflicts+Replace) in this occasion, rather than a
  Breaks+Replaces, since you should prefer the removal of the old binary
  before installing this).  See
  https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts
  (and §7.6).
* do you think you can close #555877 too?
* in d/rules:
  + that `ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))`... is not
 needed: with a new enough dpkg and if you obeys dpkg-buildflags
 (which you do) is obsolete
  + can you convert your d/rules to use the dh sequencer instead?
  + please just remove the .la file.  I'm sure it's not used inside
debian.  Do you instead have any use for it?  (as a OS developer I
dislike static libraries by a great deal)
* d/*.install: they are all useless: thanks to that different sequence
  of `make install` in d/rules files are already installed in their
  final location, so dh_install (the program that reads those files)
  has nothing to do.  So, they can go away.

I appreciate that's quite some list of things, so I've done some of them,
attached a debdiff.


Please ping me as soon as you have an updated package, following my
suggestions :)

--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA 

Bug#814723: marked as done (antlr3: FTBFS with locally rebuilt packages: Missing Build-Depends on ant)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 22:19:04 +
with message-id 
and subject line Bug#814723: fixed in antlr3 3.5.2-5
has caused the Debian Bug report #814723,
regarding antlr3: FTBFS with locally rebuilt packages: Missing Build-Depends on 
ant
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.)


-- 
814723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: antlr3
Version: 3.5.2-4
Severity: important

>From my pbuilder build log, using a setup with apt pointed to a repository of
locally rebuilt packages:

...
touch debian/stamp-maven-doc
# Generate OSGi metadata
bnd wrap --properties debian/antlr3.bnd --output 
tool/target/antlr-3.5.2.jar.tmp \
tool/target/antlr-3.5.2.jar
bnd wrap --properties debian/antlr3-runtime.bnd --output 
runtime/Java/target/antlr-runtime-3.5.2.jar.tmp \
runtime/Java/target/antlr-runtime-3.5.2.jar
mv tool/target/antlr-3.5.2.jar.tmp tool/target/antlr-3.5.2.jar
mv runtime/Java/target/antlr-runtime-3.5.2.jar.tmp 
runtime/Java/target/antlr-runtime-3.5.2.jar
# Build the Ant task
javac -source 7 -target 7 -encoding ISO-8859-1 -g -cp /usr/share/java/ant.jar 
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java
warning: [options] bootstrap class path not set in conjunction with -source 1.7
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:45:
 error: cannot find symbol
import org.apache.tools.ant.BuildException;
   ^
  symbol:   class BuildException
  location: package org.apache.tools.ant
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:46:
 error: cannot find symbol
import org.apache.tools.ant.DirectoryScanner;
   ^
  symbol:   class DirectoryScanner
  location: package org.apache.tools.ant
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:47:
 error: cannot find symbol
import org.apache.tools.ant.Project;
   ^
  symbol:   class Project
  location: package org.apache.tools.ant
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:48:
 error: cannot find symbol
import org.apache.tools.ant.Task;
   ^
  symbol:   class Task
  location: package org.apache.tools.ant
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:49:
 error: package org.apache.tools.ant.taskdefs does not exist
import org.apache.tools.ant.taskdefs.Execute;
^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:50:
 error: package org.apache.tools.ant.taskdefs does not exist
import org.apache.tools.ant.taskdefs.LogOutputStream;
^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:51:
 error: package org.apache.tools.ant.taskdefs does not exist
import org.apache.tools.ant.taskdefs.PumpStreamHandler;
^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:52:
 error: package org.apache.tools.ant.taskdefs does not exist
import org.apache.tools.ant.taskdefs.Redirector;
^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:53:
 error: package org.apache.tools.ant.types does not exist
import org.apache.tools.ant.types.Commandline;
 ^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:54:
 error: package org.apache.tools.ant.types does not exist
import org.apache.tools.ant.types.CommandlineJava;
 ^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:55:
 error: package org.apache.tools.ant.types does not exist
import org.apache.tools.ant.types.Path;
 ^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:56:
 error: package org.apache.tools.ant.util does not exist
import org.apache.tools.ant.util.JavaEnvUtils;
^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:57:
 error: package org.apache.tools.ant.util does not exist
import org.apache.tools.ant.util.LoaderUtils;
^
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java:58:
 error: package org.apache.tools.ant.util does not exist
import org.apache.tools.ant.util.TeeOutputStream;

Bug#821347: libsecret porting for s390x

[Andreas Henriksson]

Hello Debian s390x porters!

I'd like to ask for your help with looking at the problems building
libsecret on s390x. It's currently the only (release-)architecture
not building and blocking testing migration for a long time. :(

It seems the testsuite somehow gets stuck on your arch/buildd

https://buildd.debian.org/status/fetch.php?pkg=libsecret=s390x=0.18.5-1=1462961523
https://tracker.debian.org/pkg/libsecret
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821347

Regards,
Andreas Henriksson

Processed: Re: Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 sshuttle/0.78.0-1
Bug #823647 [sshuttle] sshuttle package in stretch/sid builds only 
documentation, no executable
No longer marked as found in versions sshuttle/0.78.0-1.
> tags -1 - moreinfo
Bug #823647 [sshuttle] sshuttle package in stretch/sid builds only 
documentation, no executable
Removed tag(s) moreinfo.
> close -1
Bug #823647 [sshuttle] sshuttle package in stretch/sid builds only 
documentation, no executable
Marked Bug as done

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

Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

[Axel Beckert]

Control: notfound -1 sshuttle/0.78.0-1
Control: tags -1 - moreinfo
Control: close -1

Hi Robert,

Robert Lange wrote:
> You are correct. I have Python 3.4 installed. Rebuilding on a system
> with Python 3.5 worked as expected.

Thanks for the confirmation.

> Apparently if the X-Python-Version is not satisfied, the build gives
> no fatal errors and appears to work, while not actually building the
> package properly. But that's a bug for the build system, not this
> package.

Indeed. Not sure which part of the buildsystem is the culprit here.
Maybe it's also partially wanted if e.g. multiple python versions are
listed, but it shouldn't bail out if not all of them can be found.

Anyways, closing this bug report against sshuttle now.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#828624: samba: Service fails to install and start

[Marc J. Driftmeyer]

Package: samba
Version: 2:4.4.4+dfsg-1
Followup-For: Bug #828624

Dear Maintainer,

Selecting previously unselected package samba.
(Reading database ... 704294 files and directories currently installed.)
Preparing to unpack .../samba_2%3a4.4.4+dfsg-1_amd64.deb ...
Unpacking samba (2:4.4.4+dfsg-1) ...
Processing triggers for libc-bin (2.23-0experimental2) ...
Processing triggers for systemd (230-3) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up samba (2:4.4.4+dfsg-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → 
/lib/systemd/system/nmbd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/samba-ad-dc.service 
→ /lib/systemd/system/samba-ad-dc.service.
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → 
/lib/systemd/system/smbd.service.
Job for samba-ad-dc.service failed because the control process exited with 
error code.
See "systemctl status samba-ad-dc.service" and "journalctl -xe" for details.
invoke-rc.d: initscript samba-ad-dc, action "start" failed.
dpkg: error processing package samba (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.23-0experimental2) ...
Processing triggers for systemd (230-3) ...
Errors were encountered while processing:
 samba
E: Sub-process /usr/bin/dpkg returned an error code (1)

Gotta love when testing isn't thorough.

 Marc J. Driftmeyer

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 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 samba depends on:
ii  adduser  3.114
ii  dpkg 1.18.7
ii  init-system-helpers  1.35
ii  libbsd0  0.8.3-1
ii  libc62.23-0experimental2
ii  libldb1  2:1.1.26-1
ii  libpam-modules   1.1.8-3.3
ii  libpam-runtime   1.1.8-3.3
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.12~rc1-2
ii  libtalloc2   2.1.6-1
ii  libtdb1  1.3.9-1
ii  libtevent0   0.9.28-1
ii  libwbclient0 2:4.4.4+dfsg-1
ii  lsb-base 9.20160601
ii  procps   2:3.3.11-3
ii  python   2.7.11-2
ii  python-dnspython 1.14.0-1
ii  python-samba 2:4.4.4+dfsg-1
pn  python2.7:any
ii  samba-common 2:4.4.4+dfsg-1
ii  samba-common-bin 2:4.4.4+dfsg-1
ii  samba-libs   2:4.4.4+dfsg-1
ii  tdb-tools1.3.9-1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr1:2.4.47-2
ii  logrotate   3.8.7-2
ii  samba-dsdb-modules  2:4.4.4+dfsg-1
ii  samba-vfs-modules   2:4.4.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.10.3.dfsg.P4-10
ii  bind9utils 1:9.10.3.dfsg.P4-10
pn  ctdb   
pn  ldb-tools  
ii  ntp1:4.2.8p8+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.4.4+dfsg-1

-- no debconf information

Processed: Re: Bug#828633: mount in testing/unstable should conflict with old bash-completion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = moreinfo
Bug #828633 [mount] mount in testing/unstable should conflict with old 
bash-completion
Added tag(s) moreinfo; removed tag(s) pending.

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

Bug#828633: mount in testing/unstable should conflict with old bash-completion

[Andreas Henriksson]

Control: tags -1 = moreinfo

Hello!

Apparently I'm stressing this too much as well being short on time
currently...

On Sun, Jun 26, 2016 at 08:12:26PM +0200, Sven Joachim wrote:
> On 2016-06-26 23:22 +1000, Russell Coker wrote:
> 
> > Below is the results of "apt-get dist-upgrade" to upgrade from Jessie to
> > testing.  If I manually upgrade bash-completion first then mount can be
> > upgraded without problems.
> >
> > Preparing to unpack .../mount_2.28-5_amd64.deb ...
> > Unpacking mount (2.28-5) over (2.27.1-3.1) ...
> > dpkg: error processing archive 
> > /var/cache/apt/archives/mount_2.28-5_amd64.deb (--unpack):
> >  trying to overwrite '/usr/share/bash-completion/completions/mount', which 
> > is also in package bash-completion 1:2.1-4.3
> 
> How could that happen, considering that bash-completion 1:2.1-4.3 is
> precisely the version which dropped the file in question, and there is
> not even a newer version in the archive?  Did you have a local
> bash-completion package with the same version as the official one and
> different contents installed?

I also find this peculiar when looking closer at it. That version
of bash-completion should not have the mount completion file.

> 
> On 2016-06-26 19:01 +0200, Sven Joachim wrote:
> 
> > On 2016-06-26 18:42 +0200, Andreas Henriksson wrote:
> >
> >> Thanks for your bug report. I apparently forgot to bump the version
> >> of the already existing Breaks/Replaces statements in previous upload.
> >> Fixed in git, will be part of next upload.
> >
> > The fix in git is wrong (at least not sufficient), though.
> 
> Or at least unrelated, since changes to the util-linux package will not
> fix file conflicts in the mount package.

Thanks for catching my mistake. I pushed a revert

> 
> > You bumped the Breaks/Replaces combination in util-linux, but really
> > it needs to be changed in mount, removing the spurious tilde:
> >
> > --8<---cut here---start->8---
> > diff --git a/debian/control b/debian/control
> > index cef4980..61f66ba 100644
> > --- a/debian/control
> > +++ b/debian/control
> > @@ -78,8 +78,8 @@ Section: admin
> >  Pre-Depends: ${misc:Pre-Depends}, ${shlibs:Depends}
> >  Depends: ${misc:Depends}
> >  Suggests: nfs-common (>=1:1.1.0-13)
> > -Breaks: bash-completion (<< 1:2.1-4.3~)
> > -Replaces: bash-completion (<< 1:2.1-4.3~)
> > +Breaks: bash-completion (<< 1:2.1-4.3)
> > +Replaces: bash-completion (<< 1:2.1-4.3)

This change makes no sense to me. When declaring relationships against
specific debian revisions including a trailing tilde is recommended
to enable backports for example.

> >  Multi-Arch: foreign
> >  Description: tools for mounting and manipulating filesystems
> >   This package provides the mount(8), umount(8), swapon(8),
> > --8<---cut here---end--->8---
> 
> Scratch that, this does not make any sense.  I should not comment on bug
> reports during football half-time breaks.

I guess we agree. not sure what change is needed here really.

Russel could you please enlighten us how this could happen?

(I'll try to find time during debconf to set up a chroot and test upgrade
to verify..)

Regards,
Andreas Henriksson

Bug#828633: mount in testing/unstable should conflict with old bash-completion

[Sven Joachim]

On 2016-06-26 23:22 +1000, Russell Coker wrote:

> Below is the results of "apt-get dist-upgrade" to upgrade from Jessie to
> testing.  If I manually upgrade bash-completion first then mount can be
> upgraded without problems.
>
> Preparing to unpack .../mount_2.28-5_amd64.deb ...
> Unpacking mount (2.28-5) over (2.27.1-3.1) ...
> dpkg: error processing archive /var/cache/apt/archives/mount_2.28-5_amd64.deb 
> (--unpack):
>  trying to overwrite '/usr/share/bash-completion/completions/mount', which is 
> also in package bash-completion 1:2.1-4.3

How could that happen, considering that bash-completion 1:2.1-4.3 is
precisely the version which dropped the file in question, and there is
not even a newer version in the archive?  Did you have a local
bash-completion package with the same version as the official one and
different contents installed?

On 2016-06-26 19:01 +0200, Sven Joachim wrote:

> On 2016-06-26 18:42 +0200, Andreas Henriksson wrote:
>
>> Thanks for your bug report. I apparently forgot to bump the version
>> of the already existing Breaks/Replaces statements in previous upload.
>> Fixed in git, will be part of next upload.
>
> The fix in git is wrong (at least not sufficient), though.

Or at least unrelated, since changes to the util-linux package will not
fix file conflicts in the mount package.

> You bumped the Breaks/Replaces combination in util-linux, but really
> it needs to be changed in mount, removing the spurious tilde:
>
> --8<---cut here---start->8---
> diff --git a/debian/control b/debian/control
> index cef4980..61f66ba 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -78,8 +78,8 @@ Section: admin
>  Pre-Depends: ${misc:Pre-Depends}, ${shlibs:Depends}
>  Depends: ${misc:Depends}
>  Suggests: nfs-common (>=1:1.1.0-13)
> -Breaks: bash-completion (<< 1:2.1-4.3~)
> -Replaces: bash-completion (<< 1:2.1-4.3~)
> +Breaks: bash-completion (<< 1:2.1-4.3)
> +Replaces: bash-completion (<< 1:2.1-4.3)
>  Multi-Arch: foreign
>  Description: tools for mounting and manipulating filesystems
>   This package provides the mount(8), umount(8), swapon(8),
> --8<---cut here---end--->8---

Scratch that, this does not make any sense.  I should not comment on bug
reports during football half-time breaks.

Cheers,
   Sven

Bug#828633: mount in testing/unstable should conflict with old bash-completion

[Sven Joachim]

On 2016-06-26 18:42 +0200, Andreas Henriksson wrote:

> Control: tags -1 + pending
> Control: severity -1 serious
>
> Hello!
>
> Thanks for your bug report. I apparently forgot to bump the version
> of the already existing Breaks/Replaces statements in previous upload.
> Fixed in git, will be part of next upload.

The fix in git is wrong (at least not sufficient), though.  You bumped
the Breaks/Replaces combination in util-linux, but really it needs to be
changed in mount, removing the spurious tilde:

--8<---cut here---start->8---
diff --git a/debian/control b/debian/control
index cef4980..61f66ba 100644
--- a/debian/control
+++ b/debian/control
@@ -78,8 +78,8 @@ Section: admin
 Pre-Depends: ${misc:Pre-Depends}, ${shlibs:Depends}
 Depends: ${misc:Depends}
 Suggests: nfs-common (>=1:1.1.0-13)
-Breaks: bash-completion (<< 1:2.1-4.3~)
-Replaces: bash-completion (<< 1:2.1-4.3~)
+Breaks: bash-completion (<< 1:2.1-4.3)
+Replaces: bash-completion (<< 1:2.1-4.3)
 Multi-Arch: foreign
 Description: tools for mounting and manipulating filesystems
  This package provides the mount(8), umount(8), swapon(8),
--8<---cut here---end--->8---

Cheers,
   Sven

Bug#814726: marked as done (cglib: FTBFS with locally rebuilt packages: Missing Build-Depends on ant)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 16:49:52 +
with message-id 
and subject line Bug#814726: fixed in cglib 3.2.3-2
has caused the Debian Bug report #814726,
regarding cglib: FTBFS with locally rebuilt packages: Missing Build-Depends on 
ant
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.)


-- 
814726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cglib
Version: 3.2.0-2
Severity: important

>From my pbuilder build log, using a setup with apt pointed to a repository of
locally rebuilt packages:

...
[INFO] 
[INFO] Skipping Code Generation Library
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Code Generation Library  SUCCESS [  0.478 s]
[INFO] cglib .. FAILURE [  0.022 s]
[INFO] cglib-nodep  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.760 s
[INFO] Finished at: 2016-02-12T16:55:21+00:00
[INFO] Final Memory: 11M/150M
[INFO] 
[ERROR] Failed to execute goal on project cglib: Could not resolve dependencies 
for project cglib:cglib:jar:3.2.0: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.ant:ant:jar:debian has not been downloaded from it before. -> [Help 
1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :cglib
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/cglib-3.2.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/cglib-3.2.0/debian 
-Dmaven.repo.local=/build/cglib-3.2.0/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit 
code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Upon investigation, the reason apt was pulled in before was because velocity
currently depends on it.  However, a rebuilt velocity package will no longer
have this dependency - and according to the commentary on #814679 the
smaller set of dependencies for velocity is actually the correct one.
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: cglib
Source-Version: 3.2.3-2

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated cglib 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, 26 Jun 2016 16:13:44 +0200
Source: cglib
Binary: libcglib-java libcglib-nodep-java libcglib-java-doc
Architecture: source all
Version: 3.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: 

Processed: Re: Bug#828633: mount in testing/unstable should conflict with old bash-completion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #828633 [mount] mount in testing/unstable should conflict with old 
bash-completion
Added tag(s) pending.
> severity -1 serious
Bug #828633 [mount] mount in testing/unstable should conflict with old 
bash-completion
Severity set to 'serious' from 'normal'

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

Bug#828634: python-oauth2client: FTBFS: error: [Errno 110] Connection timed out

[Chris Lamb]

Source: python-oauth2client
Version: 2.0.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,

python-oauth2client fails to build from source in unstable/amd64:

  [..]

  test_get_environment_variable_file_error 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_get_well_known_file_on_windows 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_get_well_known_file_with_custom_config_dir 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_parse_expiry (tests.test_client.GoogleCredentialsTests) ... ok
  test_raise_exception_for_missing_fields 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_raise_exception_for_reading_json 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_save_to_well_known_file_authorized_user 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_save_to_well_known_file_service_account 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_save_well_known_file_with_non_existent_config_dir 
(tests.test_client.GoogleCredentialsTests) ... ok
  test_to_from_json_authorized_user (tests.test_client.GoogleCredentialsTests) 
... ok
  test_to_from_json_service_account (tests.test_client.GoogleCredentialsTests) 
... ok
  test_get_set_delete (tests.test_client.MemoryCacheTests) ... ok
  test_construct_authorize_url (tests.test_client.OAuth2WebServerFlowTest) ... 
ok
  test_exchange_dictlike (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_fails_if_no_code (tests.test_client.OAuth2WebServerFlowTest) 
... ok
  test_exchange_failure (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_failure_with_json_error 
(tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_id_token (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_id_token_fail (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_no_expires_in (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_success (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_exchange_using_authorization_header 
(tests.test_client.OAuth2WebServerFlowTest) ... ok
  Passing kwargs to override defaults. ... ok
  test_scope_is_required (tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_urlencoded_exchange_failure (tests.test_client.OAuth2WebServerFlowTest) 
... ok
  test_urlencoded_exchange_no_expires_in 
(tests.test_client.OAuth2WebServerFlowTest) ... ok
  test_urlencoded_exchange_success (tests.test_client.OAuth2WebServerFlowTest) 
... ok
  test_urlencoded_expires_param (tests.test_client.OAuth2WebServerFlowTest) ... 
ok
  test_assertion_body (tests.test_client.TestAssertionCredentials) ... ok
  test_assertion_refresh (tests.test_client.TestAssertionCredentials) ... ok
  test_sign_blob_abstract (tests.test_client.TestAssertionCredentials) ... ok
  test_token_revoke_failure (tests.test_client.TestAssertionCredentials) ... ok
  test_token_revoke_success (tests.test_client.TestAssertionCredentials) ... ok
  test_existing (tests.test_client.Test__save_private_file) ... ok
  test_new (tests.test_client.Test__save_private_file) ... ok
  test_update_query_params_existing_params 
(tests.test_client.UpdateQueryParamsTest) ... ok
  test_update_query_params_no_params (tests.test_client.UpdateQueryParamsTest) 
... ok
  test_cache_hit (tests.test_clientsecrets.CachedClientsecretsTests) ... ok
  test_cache_miss (tests.test_clientsecrets.CachedClientsecretsTests) ... ok
  test_validation (tests.test_clientsecrets.CachedClientsecretsTests) ... ok
  test_without_cache (tests.test_clientsecrets.CachedClientsecretsTests) ... ok
  test_load_by_filename_missing_file 
(tests.test_clientsecrets.OAuth2CredentialsTests) ... ok
  test_validate_error (tests.test_clientsecrets.OAuth2CredentialsTests) ... ok
  test_bad_json (tests.test_clientsecrets.Test__loadfile) ... ok
  test_non_existent (tests.test_clientsecrets.Test__loadfile) ... ok
  test_success (tests.test_clientsecrets.Test__loadfile) ... ok
  test_invalid_client_type 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_missing_required_type_installed 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_missing_required_type_web 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_string_not_configured_type_installed 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_string_not_configured_type_web 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_success_type_installed 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_success_type_web (tests.test_clientsecrets.Test__validate_clientsecrets) 
... ok
  test_with_non_dictionary 
(tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_with_none (tests.test_clientsecrets.Test__validate_clientsecrets) ... ok
  test_with_other_than_one_key 

Bug#789381: libpoe-api-peek-perl: FTBFS with perl 5.22: test failures

[intrigeri]

Hi,

Niko Tyni wrote (21 May 2016 16:03:54 GMT) :
> There's been no reaction to this upstream in more than a year.
> We discussed this package at the Debian Perl Team Sprint in Zürich,
> and we think it should be removed from Debian.

FWIW, I concur.

> However, it has a reverse
> dependency chain to webgui through libpoe-component-ikc-perl.

Also, libpoe-component-server-http-perl Build-Depends on
libpoe-api-peek-perl, that itself has very low popcon (vote: 2) and no
{build,runtime} reverse dependencies, so IMO this reveres-build-dep
should not block removal.

Cheers,
--
intrigeri

Bug#789381: libpoe-api-peek-perl: FTBFS with perl 5.22: test failures

[intrigeri]

Hi,

Prof. Ernesto Hernández-Novich wrote (23 May 2016 11:49:55 GMT) :
> On Sat, 21 May 2016 19:03:54 +0300 Niko Tyni  wrote:
> webgui has never been part of any stable release. WebGUI's upstream has
> been very slow for the last year or so, with only a couple of releases.
> The latest release, about a month and a half ago, still lists
> POE::Component::IKC as a dependency and it's used for a core workflow
> component -- it requires 0.2001

> I've written upstream about their thoughts on the issue.

Did you get any feedback from them yet?

> I've no particular opinion on what to do with libpoe-api-peek-perl --
> I certainly don't know how to fix it. If removal is the sane choice, go
> ahead and remove both.

OK, thank you!

Cheers,
--
intrigeri

Bug#828165: marked as done (kwalify: FTBFS: E: cannot load gemspec kwalify.gemspec (RuntimeError))

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 13:20:58 +
with message-id 
and subject line Bug#828165: fixed in kwalify 0.7.2-4
has caused the Debian Bug report #828165,
regarding kwalify: FTBFS: E: cannot load gemspec kwalify.gemspec (RuntimeError)
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.)


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

kwalify fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  kwalify
   Version:  0.7.2-3
   Build architecture:   amd64
   Date: Sat, 25 Jun 2016 18:03:21 +0200
   Hostname: 4a456fbe3d4a
   Uname:Linux 4a456fbe3d4a 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'kwalify-build-deps' in 
'../kwalify-build-deps_0.7.2-3_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 kwalify-build-deps.
  (Reading database ... 23074 files and directories currently installed.)
  Preparing to unpack kwalify-build-deps_0.7.2-3_all.deb ...
  Unpacking kwalify-build-deps (0.7.2-3) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
ca-certificates docbook-xsl-ns docbook5-xml gem2deb gem2deb-test-runner
libgmp-dev libgmpxx4ldbl libruby2.3 libxslt1.1 libyaml-0-2 openssl rake ruby
ruby-all-dev ruby-did-you-mean ruby-minitest ruby-net-telnet
ruby-power-assert ruby-setup ruby-test-unit ruby2.3 ruby2.3-dev
rubygems-integration sgml-base xml-core xsltproc
  Suggested packages:
dbtoepub docbook-xsl-doc-html | docbook-xsl-doc-pdf | docbook-xsl-doc-text
| docbook-xsl-doc docbook-xsl-saxon fop libsaxon-java libxalan2-java
libxslthl-java xalan docbook5-defguide gmp-doc libgmp10-doc libmpfr-dev ri
ruby-dev bundler sgml-base-doc
  Recommended packages:
apt-file python3-debian zip fonts-lato libjs-jquery
  The following NEW packages will be installed:
ca-certificates docbook-xsl-ns docbook5-xml gem2deb gem2deb-test-runner
libgmp-dev libgmpxx4ldbl libruby2.3 libxslt1.1 libyaml-0-2 openssl rake ruby
ruby-all-dev ruby-did-you-mean ruby-minitest ruby-net-telnet
ruby-power-assert ruby-setup ruby-test-unit ruby2.3 ruby2.3-dev
rubygems-integration sgml-base xml-core xsltproc
  0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 8792 kB of archives.
  After this operation, 44.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 openssl amd64 
1.0.2h-1 [681 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 ca-certificates all 
20160104 [200 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 rubygems-integration 
all 1.10 [4882 B]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 ruby-did-you-mean all 
1.0.0-2 [11.2 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 ruby-minitest all 
5.9.0-1 [51.1 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 ruby-net-telnet all 
0.1.1-2 [12.5 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 ruby-power-assert all 
0.3.0-1 [7902 B]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 ruby-test-unit 

Bug#749357: libmakefile-parser-perl: FTBFS - tests fail

[intrigeri]

FTR: no reply from upstream since 2 years, despite some pings and
preliminary patches sent by other pkg-perl team members.

Given the popcon (installed = 22, vote = 2) and no reverse dependency,
this package satisfies our team criteria for removal from the archive.

Processed: Re: FTBFS: AttributeError: 'module' object has no attribute 'SubfieldBase'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #828207 [src:python-django-extensions] FTBFS: AttributeError: 'module' 
object has no attribute 'SubfieldBase'
Severity set to 'important' from 'serious'

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

Bug#828207: FTBFS: AttributeError: 'module' object has no attribute 'SubfieldBase'

[Raphael Hertzog]

Control: severity -1 important

On Sun, 26 Jun 2016, Brian May wrote:
> Guessing this might be a Django issue with 1.10~beta1-1:

Yes, SubfieldBase was deprecated since 1.8 and it's removed in 1.10.
1.10 is not yet in sid, so reducing severity.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Bug#818204: marked as done (libraw: Jasper removal)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 12:34:27 +
with message-id 
and subject line Bug#818204: fixed in libraw 0.17.2-2
has caused the Debian Bug report #818204,
regarding libraw: Jasper removal
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.)


-- 
818204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libraw
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: libraw
Source-Version: 0.17.2-2

We believe that the bug you reported is fixed in the latest version of
libraw, 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.
Matteo F. Vescovi  (supplier of updated libraw 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, 26 Jun 2016 14:22:59 +0200
Source: libraw
Binary: libraw15 libraw-bin libraw-dev libraw-doc
Architecture: source
Version: 0.17.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 libraw-bin - raw image decoder library (tools)
 libraw-dev - raw image decoder library (development files)
 libraw-doc - raw image decoder library (documentation)
 libraw15   - raw image decoder library
Closes: 818204
Changes:
 libraw (0.17.2-2) unstable; urgency=medium
 .
   * debian/control: libjasper-dev b-dep dropped (Closes: #818204)
Checksums-Sha1:
 fccd4e2351a5d1011f759527ec10029935ac7ffc 2295 libraw_0.17.2-2.dsc
 7b729bee326266bde56a7e8ab6d9b6932c20b227 26024 libraw_0.17.2-2.debian.tar.xz
Checksums-Sha256:
 4952167eeb0f14457c8105c340f496c7dde9459ccaea9f84709564ba9144d224 2295 
libraw_0.17.2-2.dsc
 1d5142a84187308e0ba797c50b691844921ac0961a3509e1978b2fc95168 26024 
libraw_0.17.2-2.debian.tar.xz
Files:
 8513136785019b417b5e26957e69664d 2295 libs optional libraw_0.17.2-2.dsc
 fe3b65afbbcc17826938f8fd72a53433 26024 libs optional 
libraw_0.17.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJXb8k/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1a34gP/0z5j1JnihNEHl6vrOB+/CJf
Fr+UfJym0zlkPE/gVE61HVXuoINjiBauXsy9cb7jBZylr9A8lXlEmqGnw72MR7hc
S7RqrpziQmhfaN6jl6pdDp0vDg6atU8THXjRf374njoWcYwJ/FdiMsM4KVlRRj79
K7ancCfwRjYWrwKEksQbsYBD2WAkWndZY5/tnIzN+UKbJTqQXPgDS8iB+aYihV1B
GOZQbSE8v3WTj6tHyzEApMvYpVI2ykVTxKsnSjDX3i7i9HmJuBNtDWcPnMuPLT6K
i+KGRRqlw21aNpMpPm6bXgWvpq0I6Cgz1HbFhcRUCzBfgORLDYrkm3fhsat8vvjq
LpRKB0J0tGxHO+8A+7pVXRZRBJvemwLjkV2IlyaGa5CE3We+pvawnGLUkxRoIFEq
PDduEX7HOkM59wgNDoI4p246V0t5vAZaA0qnIx6T6+xTlDEQLv8qjFgaPeZUNVox
dMdxH0PadfS8ovXpY+ru1XvuDs6m7WxbE05ECtwKD8199a2IJznrivEaOLLlntS+
nMyKjzG/7qWCIPw4v/D8eaGlHOLQttIfR1j9uSVZIMjCdv6dTr4EzbDwc8TOwVXw
eOOGxRHNmYDcpcptg4FnHRzO/+5cYCJHz1wL+5eIXpIE6dZE8ZExVlnxcDkyx2Ya
mKn2cIF/+NJwDbzkqoG5
=xvof
-END PGP SIGNATURE End Message ---

Processed: Bug forwarded to upstream

[Debian Bug Tracking System]

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

> forwarded 828172 https://github.com/spacetelescope/asdf/issues/205
Bug #828172 [src:python-asdf] python-asdf: FTBFS: 
asdf/tags/transform/tests/test_transform.py:57: AssertionError
Set Bug forwarded-to-address to 
'https://github.com/spacetelescope/asdf/issues/205'.
> thanks
Stopping processing here.

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

Bug#818200: marked as done (gegl: Jasper removal)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 12:19:15 +
with message-id 
and subject line Bug#818200: fixed in gegl 0.3.8-3
has caused the Debian Bug report #818200,
regarding gegl: Jasper removal
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.)


-- 
818200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gegl
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: gegl
Source-Version: 0.3.8-3

We believe that the bug you reported is fixed in the latest version of
gegl, 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.
Matteo F. Vescovi  (supplier of updated gegl 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, 26 Jun 2016 14:02:45 +0200
Source: gegl
Binary: gegl libgegl-0.3-0 libgegl-dev libgegl-doc libgegl-0.3-0-dbg
Architecture: source
Version: 0.3.8-3
Distribution: unstable
Urgency: medium
Maintainer: Matteo F. Vescovi 
Changed-By: Matteo F. Vescovi 
Description:
 gegl   - Generic Graphics Library Test Program
 libgegl-0.3-0 - Generic Graphics Library
 libgegl-0.3-0-dbg - Generic Graphics Library (debugging symbols)
 libgegl-dev - Generic Graphics Library (development files)
 libgegl-doc - Generic Graphics Library (documentation)
Closes: 818200
Changes:
 gegl (0.3.8-3) unstable; urgency=medium
 .
   * debian/control: libjasper-dev b-dep dropped (Closes: #818200)
Checksums-Sha1:
 f5b16fd5159fc9d2d8485f9d4efc98ac5424888b 2711 gegl_0.3.8-3.dsc
 dba7879c57c66ad14a6e9a07fe054842a1a7e110 13384 gegl_0.3.8-3.debian.tar.xz
Checksums-Sha256:
 ff3d004c30ec52310513bef2815f0ccae4fff6fdcfd78089b6bb46b1604d9731 2711 
gegl_0.3.8-3.dsc
 81efc964d5fc4b4606ed4199c62de503ce69243ade9ed5a866781db8917b76fe 13384 
gegl_0.3.8-3.debian.tar.xz
Files:
 c645704a079daccebb020a814e9d3d8d 2711 devel optional gegl_0.3.8-3.dsc
 301d9f85952c301b89e9aabd6b37c94d 13384 devel optional 
gegl_0.3.8-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJXb8SlXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1aO5oQAJcs+tZcIbTBPY1ZtB2JcoJL
y9PjxiZ4U2O57BZ1UVnOGLjKxloXmkND9yyHo2BPe8iz0Pok928AM3RRLvvnFkTA
YF3ELTa0ZvJpBf44YXrFPoUTGKyxr95MCvfcMh9e+rVXRgSqe8zn5d8uLI6xSSH1
C94gndkYMIAyDvXT5J9cKU1QC5wtXU+q0apFJnE1CSUU6QVvvatEAEK8luUxyAnH
ag/hGOn4+JRQho7XBKZ2d2JnD+VdsMY5U73tSyNuWtyiu1kkduC+3LwIIQJ6w9k9
PZ148EzLtUhv1MWOWUxxTTTF0Tq7A0AChktTnfUGqij8cLHmoM9/y1Caaxy/iyHz
2UCxigMcoKQ1k1xY3Nx7T0olSunfX2AT5Ey0WTmboo4knQeQPArJPlo+Qq3SOAyT
U/Sm09wbXuhCKGZM2L3o/EuPvqdNUNTzfkha+w7dh6Yne/3Px6tgWxkkwT/inUwn
W4rrlA91MltTKXsihJ0uAN1uDlzxUDMjEzUxbuvM6UDnW1Rf4nUGGRjIQy1g3bHP
BeJdiwDPFCOTzpr5XDrWM292zAq4ZHxV0QAzsvLxy6ea2gQY+Bjr3H1Zzkml+9JI
X4acO6FS7xCvLZzCuGOvGM2/G2nyXFCmZs9xu+29u0CpNCJ0hMTrpDHHqndQ9sXu
174SixwdTej7Tm05OdoN
=08QG
-END PGP SIGNATURE End Message ---

Bug#828626: phpmyadmin: doesn't install

[Mircea Toader]

Package: phpmyadmin
Version: 4:4.6.2-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

The phpmyadmin package won't install and kind of breaks apt, using dpkg 
--configure -a to revert it.
This is how the attempt to install it looks like. If it's worth mentioning, I'm 
using mariadb 10.1 with their sid repo. 
But things worked out well so far, the previous version is still up and running.

Preparing to unpack .../phpmyadmin_4%3a4.6.3-1_all.deb ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dpkg: warning: subprocess old pre-removal script returned error exit status 10
dpkg: trying script from the new package instead ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dpkg: error processing archive 
/var/cache/apt/archives/phpmyadmin_4%3a4.6.3-1_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 10
dbconfig-common: flushing administrative password
*** Error in `/usr/bin/dpkg': munmap_chunk(): invalid pointer: 
0x55dd69942005 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x71fc5)[0x7fba8d86afc5]
/lib/x86_64-linux-gnu/libc.so.6(+0x77966)[0x7fba8d870966]
/usr/bin/dpkg(+0x1ffb0)[0x55dd674d0fb0]
/usr/bin/dpkg(+0x20409)[0x55dd674d1409]
/usr/bin/dpkg(+0x2774a)[0x55dd674d874a]
/usr/bin/dpkg(+0x16a37)[0x55dd674c7a37]
/usr/bin/dpkg(+0x16c35)[0x55dd674c7c35]
/usr/bin/dpkg(+0x16e7d)[0x55dd674c7e7d]
/usr/bin/dpkg(+0xa207)[0x55dd674bb207]
/usr/bin/dpkg(+0x1feeb)[0x55dd674d0eeb]
/usr/bin/dpkg(+0x200f1)[0x55dd674d10f1]
/usr/bin/dpkg(+0x9c88)[0x55dd674bac88]
/usr/bin/dpkg(+0x6659)[0x55dd674b7659]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fba8d8195f0]
/usr/bin/dpkg(+0x6769)[0x55dd674b7769]
=== Memory map: 
55dd674b1000-55dd674f5000 r-xp  08:05 655675 
/usr/bin/dpkg
55dd676f5000-55dd676f8000 r--p 00044000 08:05 655675 
/usr/bin/dpkg
55dd676f8000-55dd676f9000 rw-p 00047000 08:05 655675 
/usr/bin/dpkg
55dd676f9000-55dd6790d000 rw-p  00:00 0 
55dd697f2000-55dd6bd1a000 rw-p  00:00 0  [heap]
7fba8c714000-7fba8c72a000 r-xp  08:05 5902353
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fba8c72a000-7fba8c929000 ---p 00016000 08:05 5902353
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fba8c929000-7fba8c92a000 rw-p 00015000 08:05 5902353
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fba8c92a000-7fba8c935000 r-xp  08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8c935000-7fba8cb34000 ---p b000 08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8cb34000-7fba8cb35000 r--p a000 08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8cb35000-7fba8cb36000 rw-p b000 08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8cb36000-7fba8cb3c000 rw-p  00:00 0 
7fba8cb3c000-7fba8cb46000 r-xp  08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cb46000-7fba8cd46000 ---p a000 08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cd46000-7fba8cd47000 r--p a000 08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cd47000-7fba8cd48000 rw-p b000 08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cd48000-7fba8cd5d000 r-xp  08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cd5d000-7fba8cf5c000 ---p 00015000 08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cf5c000-7fba8cf5d000 r--p 00014000 08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cf5d000-7fba8cf5e000 rw-p 00015000 08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cf5e000-7fba8cf6 rw-p  00:00 0 
7fba8cf6-7fba8cf67000 r-xp  08:05 5898681
/lib/x86_64-linux-gnu/libnss_compat-2.22.so
7fba8cf67000-7fba8d166000 ---p 7000 08:05 5898681
/lib/x86_64-linux-gnu/libnss_compat-2.22.so
7fba8d166000-7fba8d167000 r--p 6000 08:05 5898681
/lib/x86_64-linux-gnu/libnss_compat-2.22.so
7fba8d167000-7fba8d168000 rw-p 7000 08:05 5898681
/lib/x86_64-linux-gnu/libnss_compat-2.22.so
7fba8d168000-7fba8d18 r-xp  08:05 5898688
/lib/x86_64-linux-gnu/libpthread-2.22.so
7fba8d18-7fba8d37f000 ---p 00018000 08:05 5898688
/lib/x86_64-linux-gnu/libpthread-2.22.so
7fba8d37f000-7fba8d38 r--p 00017000 08:05 5898688
/lib/x86_64-linux-gnu/libpthread-2.22.so
7fba8d38-7fba8d381000 rw-p 00018000 08:05 5898688
/lib/x86_64-linux-gnu/libpthread-2.22.so
7fba8d381000-7fba8d385000 rw-p  00:00 0 
7fba8d385000-7fba8d387000 r-xp  

Bug#817711: uudeview: Removal of debhelper compat 4

[Andreas Metzler]

Control: tags -1 patch

On 2016-03-09 ni...@thykier.net wrote:
> Source: uudeview
> Severity: important
> Usertags: compat-4-removal

> Hi,

> The package uudeview 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.
[...]

There is a trivial fix ...

echo 5 > debian/compat

... generates a identical package.

I have also locally upgraded the packaging to compat 9 (with dh wrapper)
but will not upload as NMU. Afaiu the package might be orphaned, then
this would be eligible for a QA upload.

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

Processed: Re: Bug#817711: uudeview: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#828624: samba: samba-ad-dc.service shouldn't be enabled by default

[Laurent Bigonville]

Package: samba
Version: 2:4.4.4+dfsg-1
Severity: serious
File: /lib/systemd/system/samba-ad-dc.service

Hi,

With the newest version the installation of samba package is failing
because of the samba-ad-dc.service service.

In the logs I see the following message:

[2016/06/26 13:15:32.377822,  0] ../source4/smbd/server.c:373(binary_smbd_main)
  samba version 4.4.4-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2016
[2016/06/26 13:15:32.414489,  0] ../source4/smbd/server.c:472(binary_smbd_main)
  At this time the 'samba' binary should only be used for either:
  'server role = active directory domain controller' or to access the ntvfs 
file server with 'server services = +smb' or the rpc proxy with 'dcerpc 
endpoint servers = remote'
  You should start smbd/nmbd/winbindd instead for domain member and standalone 
file server tasks
[2016/06/26 13:15:32.414586,  0] ../lib/util/become_daemon.c:111(exit_daemon)
  STATUS=daemon failed to start: Samba detected misconfigured 'server role' and 
exited. Check logs for details, error code 22

IMVO, the service shouldn't be enabled and started in default
installations. That would probably require some extra documentation in
the README.Debian too

Regards,

Laurent Bigonville

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

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

Versions of packages samba depends on:
ii  adduser  3.114
ii  dpkg 1.18.7
ii  init-system-helpers  1.35
ii  libbsd0  0.8.3-1
ii  libc62.22-12
ii  libldb1  2:1.1.26-1
ii  libpam-modules   1.1.8-3.3
ii  libpam-runtime   1.1.8-3.3
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.12~rc1-2
ii  libtalloc2   2.1.6-1
ii  libtdb1  1.3.9-1
ii  libtevent0   0.9.28-1
ii  libwbclient0 2:4.4.4+dfsg-1
ii  lsb-base 9.20160601
ii  procps   2:3.3.11-3
ii  python   2.7.11-2
ii  python-dnspython 1.14.0-1
ii  python-samba 2:4.4.4+dfsg-1
pn  python2.7:any
ii  samba-common 2:4.4.4+dfsg-1
ii  samba-common-bin 2:4.4.4+dfsg-1
ii  samba-libs   2:4.4.4+dfsg-1
ii  tdb-tools1.3.9-1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr1:2.4.47-2
ii  logrotate   3.8.7-2
ii  samba-dsdb-modules  2:4.4.4+dfsg-1
ii  samba-vfs-modules   2:4.4.4+dfsg-1

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
ii  ntp1:4.2.8p8+dfsg-1
pn  smbldap-tools  
pn  ufw
pn  winbind

-- no debconf information

Bug#828117: marked as done (r-cran-gss: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 11:19:44 +
with message-id 
and subject line Bug#828117: fixed in r-cran-gss 2.1-5-2
has caused the Debian Bug report #828117,
regarding r-cran-gss: FTBFS: dh_clean: Please specify the compatibility level 
in debian/compat
to be marked as done.

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

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


-- 
828117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-gss
Version: 2.1-5-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,

r-cran-gss fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../x11-common_1%3a7.7+15_all.deb ...
  Unpacking x11-common (1:7.7+15) ...
  Selecting previously unselected package libice6:amd64.
  Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../libjpeg62-turbo_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package liblapack3.
  Preparing to unpack .../liblapack3_3.6.0-2_amd64.deb ...
  Unpacking liblapack3 (3.6.0-2) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libthai-data.
  Preparing to unpack .../libthai-data_0.1.24-2_all.deb ...
  Unpacking libthai-data (0.1.24-2) ...
  Selecting previously unselected package libdatrie1:amd64.
  Preparing to unpack .../libdatrie1_0.2.10-2_amd64.deb ...
  Unpacking libdatrie1:amd64 (0.2.10-2) ...
  Selecting previously unselected package libthai0:amd64.
  Preparing to unpack .../libthai0_0.1.24-2_amd64.deb ...
  Unpacking libthai0:amd64 (0.1.24-2) ...
  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../libtcl8.6_8.6.5+dfsg-2_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../libtk8.6_8.6.5-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.5-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package r-base-core.
  Preparing to unpack 

Bug#828223: mvtnorm: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Dirk Eddelbuettel]

On 26 June 2016 at 06:00, Dirk Eddelbuettel wrote:
| 
| On 26 June 2016 at 10:37, Chris Lamb wrote:
| | Source: mvtnorm
| | Version: 1.0-5-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,
| | 
| | mvtnorm fails to build from source in unstable/amd64:
| 
| Already fixed in 1.0-5-2.

Which I prepared yesterday, along with a bunch of others, but not uploaded by
oversight.  Now corrected.

Dirk
 

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

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

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 06:00:48 -0500
with message-id <22383.46560.95005.60...@max.nulle.part>
and subject line Re: Bug#828223: mvtnorm: FTBFS: dh_clean: Please specify the 
compatibility level in debian/compat
has caused the Debian Bug report #828223,
regarding mvtnorm: FTBFS: dh_clean: Please specify the compatibility level in 
debian/compat
to be marked as done.

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

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


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

mvtnorm fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../x11-common_1%3a7.7+15_all.deb ...
  Unpacking x11-common (1:7.7+15) ...
  Selecting previously unselected package libice6:amd64.
  Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../libjpeg62-turbo_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package liblapack3.
  Preparing to unpack .../liblapack3_3.6.0-2_amd64.deb ...
  Unpacking liblapack3 (3.6.0-2) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libthai-data.
  Preparing to unpack .../libthai-data_0.1.24-2_all.deb ...
  Unpacking libthai-data (0.1.24-2) ...
  Selecting previously unselected package libdatrie1:amd64.
  Preparing to unpack .../libdatrie1_0.2.10-2_amd64.deb ...
  Unpacking libdatrie1:amd64 (0.2.10-2) ...
  Selecting previously unselected package libthai0:amd64.
  Preparing to unpack .../libthai0_0.1.24-2_amd64.deb ...
  Unpacking libthai0:amd64 (0.1.24-2) ...
  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../libtcl8.6_8.6.5+dfsg-2_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../libtk8.6_8.6.5-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.5-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package 

Bug#814711: Garbled graphics in Renoise application

[vitaminx]

Problem seems to be fixed at some point before 1.18.3-1
Please close this bug.

Bug#828622: xul-ext-greasemonkey: unable to manage scripts since Iceweasel -> Firefox ESR transition

[carandraug]

Package: xul-ext-greasemonkey
Version: 2.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The greasemonkey plugin has suddenly stopped working.  I believe this to
have happened after upgrading to debian 8.5 where Iceweasel was upgraded
and is now Firefox ESR.

How it does not work:

* its menu "Manage user scripts..." opens "about:addons instead
* its menu "New user script" does nothing
* button to install on websites with scripts to install, such as
greasyfork.org, no longer works and firefox displays the source
of the script instead.

In addition, previously enabled scripts have been disabled (or
just no longer work but since the script manager is not accessible
I can't check the issue).

Carnë


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

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

Versions of packages xul-ext-greasemonkey depends on:
ii  iceweasel  45.2.0esr-1~deb8u1

xul-ext-greasemonkey recommends no packages.

xul-ext-greasemonkey suggests no packages.

-- no debconf information

Bug#828621: opencolorio: FTBFS: ! Undefined control sequence.

[Chris Lamb]

Source: opencolorio
Version: 1.0.9~dfsg0-5
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,

opencolorio fails to build from source in unstable/amd64:

  [..]

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:119:
 WARNING: autodoc: failed to import function u'SetCurrentConfig' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:121:
 WARNING: autodoc: failed to import function u'SetLoggingLevel' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:126:
 WARNING: autodoc: failed to import class u'Config' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:133:
 WARNING: autodoc: failed to import class u'ColorSpace' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:140:
 WARNING: autodoc: failed to import class u'Look' from module u'PyOpenColorIO'; 
the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:147:
 WARNING: autodoc: failed to import class u'Processor' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:154:
 WARNING: autodoc: failed to import class u'Context' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonTransforms.rst:17:
 WARNING: autodoc: failed to import class u'Transform' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonTransforms.rst:30:
 WARNING: autodoc: failed to import class u'AllocationTransform' from module 
u'PyOpenColorIO'; the following exception was raised:
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in 
import_object
  __import__(self.modname)
  ImportError: No module named PyOpenColorIO
  
/home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonTransforms.rst:48:
 WARNING: autodoc: failed to import 

Bug#828224: nose: FTBFS: FAIL: runTest (test_coverage_plugin.TestCoveragePlugin) [..] AssertionError: False is not true

[Chris Lamb]

Source: nose
Version: 1.3.7-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,

nose fails to build from source in unstable/amd64:

  [..]

  test_function_test_case_fixtures (test_cases.TestNoseCases) ... ok
  test_method_test_case (test_cases.TestNoseCases) ... ok
  test_method_test_case_fixtures (test_cases.TestNoseCases) ... ok
  test_method_test_case_with_metaclass (test_cases.TestNoseCases) ... ok
  test_address (test_cases.TestNoseTestWrapper) ... ok
  test_case_fixtures_called (test_cases.TestNoseTestWrapper)
  Instance fixtures are properly called for wrapped tests ... ok
  test_context (test_cases.TestNoseTestWrapper) ... ok
  test_result_proxy_used (test_cases.TestNoseTestWrapper)
  A result proxy is used to wrap the result for all tests ... ok
  test_short_description (test_cases.TestNoseTestWrapper) ... ok
  test_unrepresentable_shortDescription (test_cases.TestNoseTestWrapper) ... ok
  test_defaults (test_config.TestNoseConfig) ... ok
  test_ignore_files_default (test_config.TestNoseConfig)
  The default configuration should have several ignore file settings. ... ok
  test_ignore_files_multiple (test_config.TestNoseConfig)
  Multiple ignore-files flags should be appended together, overriding ... ok
  test_ignore_files_single (test_config.TestNoseConfig)
  A single ignore-files flag should override the default settings. ... ok
  test_multiple_include (test_config.TestNoseConfig) ... ok
  test_pickle_configured (test_config.TestNoseConfig) ... ok
  test_pickle_empty (test_config.TestNoseConfig) ... ok
  test_plugins (test_config.TestNoseConfig) ... ok
  test_progname_looks_like_option (test_config.TestNoseConfig) ... ok
  test_reset (test_config.TestNoseConfig) ... ok
  test_single_include (test_config.TestNoseConfig) ... ok
  test_testnames (test_config.TestNoseConfig) ... ok
  test_update (test_config.TestNoseConfig) ... ok
  test_where (test_config.TestNoseConfig) ... ok
  test_restore_stdout (test_core.TestAPI_run) ... ok
  test_getAllConfigFiles (test_core.TestProgramConfigs) ... ok
  test_getAllConfigFiles_ignore_configs (test_core.TestProgramConfigs) ... ok
  test_makeConfig (test_core.TestProgramConfigs) ... ok
  test_from_directory (test_core.TestUsage) ... ok
  test_from_zip (test_core.TestUsage) ... ok
  test_cover_plugin.TestCoveragePlugin.test_cover_packages_option ... ok
  test_api_present (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_can_be_disabled (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_deprecated_output (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_deprecated_output_verbose (test_deprecated_plugin.TestDeprecatedPlugin) 
... ok
  test_enabled_by_default (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_patched_result_handles_deprecated 
(test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_patches_only_when_needed (test_deprecated_plugin.TestDeprecatedPlugin) 
... ok
  test_prepare_patches_result (test_deprecated_plugin.TestDeprecatedPlugin) ... 
ok
  test_err_doctests_raises_exception 
(test_doctest_error_handling.TestDoctestErrorHandling) ... ok
  test_no_doctests_in_file 
(test_doctest_error_handling.TestDoctestErrorHandling) ... ok
  test_no_name (test_doctest_no_name.TestDoctestErrorHandling) ... ok
  test_default_id_file_is_in_working_dir (test_id_plugin.TestTestIdPlugin) ... 
ok
  test_add_paths (test_importer.TestImporter) ... ok
  test_import (test_importer.TestImporter) ... ok
  test_module_init_prefix (test_importer.TestImporter) ... ok
  test_module_no_file (test_importer.TestImporter) ... ok
  test_bug_95 (test_inspector.TestExpander)
  Test that inspector can handle multi-line docstrings ... ok
  test_get_tb_source_func (test_inspector.TestExpander) ... ok
  test_get_tb_source_simple (test_inspector.TestExpander) ... ok
  test_inspect_traceback_continued (test_inspector.TestExpander) ... ok
  test_pick_tb_lines (test_inspector.TestExpander) ... ok
  test_simple_inspect_frame (test_inspector.TestExpander) ... ok
  test_isolation_plugin.test_lint ... ok
  test_issue135 (test_issue135.TestIssue135) ... ok
  test_load_nested_generator (test_issue_006.TestIssue006) ... ok
  test_issue_064.test_is_generator_alias ... ok
  test_dict_wrapper_instance_not_loaded (test_issue_065.TestIssue065) ... ok
  test_string_exception_not_masked 
(test_issue_101.TestErrorClassWithStringException) ... ok
  test_issue_227.test_unicode ... ok
  test_generator_yield_value (test_issue_230.TestIssue230) ... ok
  test_issue_786.Test.test_evens ... ok
  test_issue_786.test_evens ... ok
  test_basic_iteration (test_lazy_suite.TestLazySuite) ... ok
  test_cases_from_testcase_are_wrapped (test_loader.TestTestLoader) ... ok
  test_lint (test_loader.TestTestLoader)
  Test that main API functions exist ... ok
  test_load_from_name_dir_abs (test_loader.TestTestLoader) ... ok
  

Bug#828223: mvtnorm: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: mvtnorm
Version: 1.0-5-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,

mvtnorm fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../x11-common_1%3a7.7+15_all.deb ...
  Unpacking x11-common (1:7.7+15) ...
  Selecting previously unselected package libice6:amd64.
  Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../libjpeg62-turbo_1%3a1.5.0-1_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Selecting previously unselected package liblapack3.
  Preparing to unpack .../liblapack3_3.6.0-2_amd64.deb ...
  Unpacking liblapack3 (3.6.0-2) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../fontconfig_2.11.0-6.4_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.4) ...
  Selecting previously unselected package libthai-data.
  Preparing to unpack .../libthai-data_0.1.24-2_all.deb ...
  Unpacking libthai-data (0.1.24-2) ...
  Selecting previously unselected package libdatrie1:amd64.
  Preparing to unpack .../libdatrie1_0.2.10-2_amd64.deb ...
  Unpacking libdatrie1:amd64 (0.2.10-2) ...
  Selecting previously unselected package libthai0:amd64.
  Preparing to unpack .../libthai0_0.1.24-2_amd64.deb ...
  Unpacking libthai0:amd64 (0.1.24-2) ...
  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../libharfbuzz0b_1.2.6-2_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.6-2) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../libtcl8.6_8.6.5+dfsg-2_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../libtk8.6_8.6.5-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.5-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package r-base-core.
  Preparing to unpack .../r-base-core_3.3.1-1_amd64.deb ...
  Unpacking r-base-core (3.3.1-1) ...
  Selecting previously unselected package libgfortran-5-dev:amd64.
  Preparing to unpack .../libgfortran-5-dev_5.4.0-4_amd64.deb ...
  Unpacking libgfortran-5-dev:amd64 (5.4.0-4) ...
  Selecting previously unselected package gfortran-5.
  Preparing to unpack .../gfortran-5_5.4.0-4_amd64.deb ...
  Unpacking gfortran-5 (5.4.0-4) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../gfortran_4%3a5.3.1-3_amd64.deb ...
  Unpacking gfortran (4:5.3.1-3) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../libblas-dev_3.6.0-2_amd64.deb ...
  Unpacking libblas-dev (3.6.0-2) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../liblapack-dev_3.6.0-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.0-2) ...
  Selecting previously unselected package 

Processed: Re: Downgrading severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #128745 [libstroke0-dev] libstroke0-dev: aclocal is confused by libstroke 
.m4 files 
Bug #302907 [libstroke0-dev] Need more quoting of autoconf macro files.
Severity set to 'critical' from 'important'
Severity set to 'critical' from 'important'

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

Bug#828212: marked as done (pyinfra: FTBFS: Theme error: sphinx_rtd_theme is no longer a hard dependency since version 1.4.0. Please install it manually.(pip install sphinx_rtd_theme))

[Debian Bug Tracking System]

Your message dated Sun, 26 Jun 2016 09:47:37 +0200
with message-id 
and subject line pyinfra: FTBFS: Theme error: sphinx_rtd_theme is no longer a 
hard dependency since version 1.4.0. Please install it manually.(pip install 
sphinx_rtd_theme)
has caused the Debian Bug report #828212,
regarding pyinfra: FTBFS: Theme error:   sphinx_rtd_theme is no longer a hard 
dependency since version 1.4.0. Please install it manually.(pip install 
sphinx_rtd_theme)
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.)


-- 
828212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyinfra
Version: 0.1~dev24-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,

pyinfra fails to build from source in unstable/amd64:

  [..]

  Setting up python3-dateutil (2.4.2-1) ...
  Setting up python3-roman (2.0.0-2) ...
  Setting up sgml-base (1.28) ...
  Setting up xml-core (0.13+nmu2) ...
  Setting up python3-pygments (2.1.3+dfsg-1) ...
  Setting up python-babel-localedata (2.3.4+dfsg.1-2) ...
  Setting up python3-tz (2015.7+dfsg-0.1) ...
  Setting up python3-babel (2.3.4+dfsg.1-2) ...
  update-alternatives: using /usr/bin/pybabel-python3 to provide 
/usr/bin/pybabel (pybabel) in auto mode
  Setting up python3-alabaster (0.7.8-1) ...
  Setting up python3-imagesize (0.7.1-1) ...
  Setting up libjs-jquery (1.12.4-1) ...
  Setting up libjs-underscore (1.7.0~dfsg-1) ...
  Setting up libjs-sphinxdoc (1.4.4-2) ...
  Setting up sphinx-common (1.4.4-2) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docutils-common (0.12+dfsg-1) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up python3-docutils (0.12+dfsg-1) ...
  update-alternatives: using /usr/share/docutils/scripts/python3/rst-buildhtml 
to provide /usr/bin/rst-buildhtml (rst-buildhtml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2html to 
provide /usr/bin/rst2html (rst2html) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2latex to 
provide /usr/bin/rst2latex (rst2latex) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2man to 
provide /usr/bin/rst2man (rst2man) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2odt to 
provide /usr/bin/rst2odt (rst2odt) in auto mode
  update-alternatives: using 
/usr/share/docutils/scripts/python3/rst2odt_prepstyles to provide 
/usr/bin/rst2odt_prepstyles (rst2odt_prepstyles) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2pseudoxml 
to provide /usr/bin/rst2pseudoxml (rst2pseudoxml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2s5 to 
provide /usr/bin/rst2s5 (rst2s5) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2xetex to 
provide /usr/bin/rst2xetex (rst2xetex) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2xml to 
provide /usr/bin/rst2xml (rst2xml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rstpep2html to 
provide /usr/bin/rstpep2html (rstpep2html) in auto mode
  Setting up python3-sphinx (1.4.4-2) ...
  Setting up pyinfra-build-deps (0.1~dev24-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=94623d1b10b3
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160626081125.r8OWGRV9Am.pyinfra/pyinfra-0.1~dev24
  OLDPWD=/home/lamby/temp/cdt.20160626081125.r8OWGRV9Am.pyinfra
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building 

Processed: Re: ots: Removal of debhelper compat 4

[Debian Bug Tracking System]

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

> tags 817612 + pending
Bug #817612 [src:ots] ots: Removal of debhelper compat 4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828212: pyinfra: FTBFS: Theme error: sphinx_rtd_theme is no longer a hard dependency since version 1.4.0. Please install it manually.(pip install sphinx_rtd_theme)

[Chris Lamb]

Source: pyinfra
Version: 0.1~dev24-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,

pyinfra fails to build from source in unstable/amd64:

  [..]

  Setting up python3-dateutil (2.4.2-1) ...
  Setting up python3-roman (2.0.0-2) ...
  Setting up sgml-base (1.28) ...
  Setting up xml-core (0.13+nmu2) ...
  Setting up python3-pygments (2.1.3+dfsg-1) ...
  Setting up python-babel-localedata (2.3.4+dfsg.1-2) ...
  Setting up python3-tz (2015.7+dfsg-0.1) ...
  Setting up python3-babel (2.3.4+dfsg.1-2) ...
  update-alternatives: using /usr/bin/pybabel-python3 to provide 
/usr/bin/pybabel (pybabel) in auto mode
  Setting up python3-alabaster (0.7.8-1) ...
  Setting up python3-imagesize (0.7.1-1) ...
  Setting up libjs-jquery (1.12.4-1) ...
  Setting up libjs-underscore (1.7.0~dfsg-1) ...
  Setting up libjs-sphinxdoc (1.4.4-2) ...
  Setting up sphinx-common (1.4.4-2) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docutils-common (0.12+dfsg-1) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up python3-docutils (0.12+dfsg-1) ...
  update-alternatives: using /usr/share/docutils/scripts/python3/rst-buildhtml 
to provide /usr/bin/rst-buildhtml (rst-buildhtml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2html to 
provide /usr/bin/rst2html (rst2html) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2latex to 
provide /usr/bin/rst2latex (rst2latex) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2man to 
provide /usr/bin/rst2man (rst2man) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2odt to 
provide /usr/bin/rst2odt (rst2odt) in auto mode
  update-alternatives: using 
/usr/share/docutils/scripts/python3/rst2odt_prepstyles to provide 
/usr/bin/rst2odt_prepstyles (rst2odt_prepstyles) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2pseudoxml 
to provide /usr/bin/rst2pseudoxml (rst2pseudoxml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2s5 to 
provide /usr/bin/rst2s5 (rst2s5) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2xetex to 
provide /usr/bin/rst2xetex (rst2xetex) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rst2xml to 
provide /usr/bin/rst2xml (rst2xml) in auto mode
  update-alternatives: using /usr/share/docutils/scripts/python3/rstpep2html to 
provide /usr/bin/rstpep2html (rstpep2html) in auto mode
  Setting up python3-sphinx (1.4.4-2) ...
  Setting up pyinfra-build-deps (0.1~dev24-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=94623d1b10b3
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160626081125.r8OWGRV9Am.pyinfra/pyinfra-0.1~dev24
  OLDPWD=/home/lamby/temp/cdt.20160626081125.r8OWGRV9Am.pyinfra
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building pyinfra 0.1~dev24-1 on amd64  
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package pyinfra
  dpkg-buildpackage: info: source version 0.1~dev24-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Daniel Stender 
   dpkg-source --before-build pyinfra-0.1~dev24
  dpkg-buildpackage: info: host architecture amd64
  dpkg-source: info: using options from 
pyinfra-0.1~dev24/debian/source/options: --extend-diff-ignore=^[^/]+\.egg-info/
   fakeroot debian/rules clean
  dh clean --with python3,sphinxdoc --buildsystem=pybuild
 dh_testdir -O--buildsystem=pybuild
 dh_auto_clean -O--buildsystem=pybuild
  I: pybuild base:184: python3.5 setup.py clean 
  running clean
  removing 
'/home/lamby/temp/cdt.20160626081125.r8OWGRV9Am.pyinfra/pyinfra-0.1~dev24/.pybuild/pythonX.Y_3.5/build'
 (and everything under it)
  'build/bdist.linux-x86_64' does not