Bug#828833: python3-magic: magic file type double encoded

[Mattia Rizzolo]

Hi Christoph,

On Tue, Jun 28, 2016 at 11:28:30PM +0200, Christoph Biedl wrote:
> > It looks like upstream just commited the same fix:
> > https://github.com/file/file/commit/73e043d2a986234b187a00ed0c8d1f7bf83df372
> 
> Great. I'll collect some more stuff that needs attention, shouldn't
> take longer than a few days.

This bug is causing quite some headaches within the reproducible builds
project, as diffoscope relies on python3-magic quite a lot.
Both yesterday and today I downgraded the packages to the previous
versions, but given that the chroot where this runs is recreated at
early morning we have to experience hundreds of failures until I wake up
and paper this over...

Can I ask you to quickly upload the fix as soon as there is a working
py2/py3 patch?

-- 
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#828907: plymouth external firmware error

[Cédric Brandenbourger]

Yes firmware-misc-non-free is installed

when i type:

plymouth-set-default-theme -R details, i don't get any message


with all the other templates i get the error



On Wed, Jun 29, 2016 at 6:01 AM, Laurent Bigonville 
wrote:

> Le 28/06/16 à 22:54, Cedric Brandenbourger a écrit :
>
>> Package: plymouth
>> Version: 0.9.2-3+b1
>> Severity: important
>>
>> Dear Maintainer,
>>
>
> Hello,
>
> * What led up to the situation?
>>
>> I have to use an external firmware for my GK106 graphic card due to this
>> bug:
>> https://bugs.freedesktop.org/show_bug.cgi?id=93629
>> This working quite well, but when i install plymouth and change the theme
>> from
>> "details" to "spinner" i'm getting error when i update initramfs
>>
>>
>> sudo plymouth-set-default-theme -R spinner
>> update-initramfs: Generating /boot/initrd.img-4.6.0-1-amd64
>> W: Possible missing firmware
>> /lib/firmware/nvidia/gm206/gr/sw_method_init.bin
>> for module nouveau
>> W: Possible missing firmware
>> /lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin
>> for module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_nonctx.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_ctx.bin for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_sig.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_sig.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_data.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_inst.bin
>> for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_bl.bin for
>> module nouveau
>> W: Possible missing firmware
>> /lib/firmware/nvidia/gm206/acr/ucode_unload.bin
>> for module nouveau
>> W: Possible missing firmware
>> /lib/firmware/nvidia/gm206/acr/ucode_load.bin for
>> module nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/bl.bin for
>> module
>> nouveau
>> W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_method
>>
>> the package firmware-linux-nonfree and firmware-linux-misc are installed.
>>
>>
>> When i reboot i'm getting the following error message
>>
>> kernel: [1.968430] nouveau :01:00.0: firmware: failed to load
>> nvidia/gk106/fecs_inst.bin (-2)
>> kernel: [1.968434] nouveau :01:00.0: Direct firmware load for
>> nvidia/gk106/fecs_inst.bin failed with error -2
>>
>> * What exactly did you do (or not do) that was effective (or
>>   ineffective)?
>>
>> i installed plymouth
>>
>
> I don't think this is related to plymouth.
>
> Did you try to install firmware-misc-nonfree ?
>
>

Bug#828934: Add newLISP to the list of known interpreters

[Sergio Durigan Junior]

Package: lintian
Version: 2.5.44
Severity: wishlist
Tags: patch

Hi,

newLISP has been recently packaged for Debian:

  

So now it is time to add it to the list of known interpreters, in order
to avoid the 'unusual-interpreter' warning.  The attached patch does
that.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

From 11cc1ccde4fd3cf22dc8860b60daf8ed1f07f08e Mon Sep 17 00:00:00 2001
From: Sergio Durigan Junior 
Date: Wed, 29 Jun 2016 01:21:42 -0400
Subject: [PATCH] Add newLISP to the list of known interpreters

newLISP has been packaged for Debian, so now it should be added to
list of known interpreters.
---
 data/scripts/interpreters | 1 +
 1 file changed, 1 insertion(+)

diff --git a/data/scripts/interpreters b/data/scripts/interpreters
index e569eb5..5eb1a6d 100644
--- a/data/scripts/interpreters
+++ b/data/scripts/interpreters
@@ -58,6 +58,7 @@ make   => /usr/bin, make | build-essential | dpkg-dev
 mawk   => /usr/bin
 mksh   => /bin
 mscgen => /usr/bin
+newlisp=> /usr/bin
 ngraph => /usr/bin, ngraph-gtk
 nickle => /usr/bin
 nodejs => /usr/bin
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#828911: FTBFS on various architectures when generating the gtk-doc documentation

[Pino Toscano]

Hi,

On 2016-06-28 23:17, Michael Biebl wrote:

After applying the change as requested by Pino in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823268
the package FTBFS on various architectures:
https://buildd.debian.org/status/package.php?p=tracker

I suspect gtk-doc is not really safe regarding parallel builds.
This should be investigated or
https://anonscm.debian.org/cgit/collab-maint/tracker.git/commit/?id=5f82b567362c0449f85a8008ba7d1a31735fe93c
reverted.


Sorry for the issue, it was working fine for my in my tests (and it
still does, as I cannot trigger the build failure).

Before disabling the parallel build, what about trying to backport the
upstream commit 8a5ba082959b8439993f4d731445db12a4c5e301 (in tracker)?
It is also included in the new version 1.9.0, so upgrading to that will
provide that commit too.

--
Pino Toscano

Bug#828933: Improve check to determine if the package installs a new interpreter

[Sergio Durigan Junior]

Package: lintian
Version: 2.5.44
Severity: normal
Tags: patch

Hi,

When packaging newlisp, I noticed that lintian was displaying the
'unusual-interpreter' warning.  However, after some research, I learned
that lintian should take into account the fact that a package can
actually install a new interpreter, and in this specific case the
warning should be supressed.

I took the liberty to hack lintian and found that the current check to
see if there is a new interpreter being installed is incomplete, because
it assumes that the executable file will be in the toplevel directory.
The fix is simple: we should check if there is a file name $interpreter
under /usr/bin, because that is where new executables are (usually)
installed.

I decided to extend the check instead of replacing it (i.e., lintian
will still check if there is an executable called $interpreter on the
topleve directory), but my gut feeling is that the old check could be
removed safely.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

From 20f0805afa856eecee39f95eb5e64a321040f71e Mon Sep 17 00:00:00 2001
From: Sergio Durigan Junior 
Date: Wed, 29 Jun 2016 01:08:11 -0400
Subject: [PATCH] Improve check to determine if the package installs a new
 interpreter

The current check to determine if the package installs a new
interpreter is incomplete because it does not take into account the
fact that interpreters are usually installed under '/usr/bin'.  This
patch improves and extends the check to include this case.
---
 checks/scripts.pm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/checks/scripts.pm b/checks/scripts.pm
index a2afaee..f21ffd5 100644
--- a/checks/scripts.pm
+++ b/checks/scripts.pm
@@ -371,7 +371,8 @@ sub run {
 }
 } elsif ($interpreter =~ m,/usr/local/,) {
 script_tag('interpreter-in-usr-local', $filename,"#!$interpreter");
-} elsif ($executable{'.' . $interpreter}) {
+} elsif ($executable{'.' . $interpreter}
+ or $executable{'usr/bin' . $interpreter}) {
  # Package installs the interpreter itself, so it's probably ok.  Don't
  # emit any tag for this.
 } elsif ($interpreter eq '/bin/env') {
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#828830: ITP: licensecheck -- simple license checker for source files

[Adam D. Barratt]

On Tue, 2016-06-28 at 21:21 +0200, Jonas Smedegaard wrote:
> ...speaking of previous authoring: April 20th, 2007, you changed 
> comments from
> 
>   "originally [...] from the KDE SDK"
> 
> to
> 
>   "originally [...] from the KDE SDK (by dfa...@kde.org)"
> 
> ...but it seems from my resurrecting old SVN commits that a) the person 
> referenced is David Faure  (no "d" in email address), and 
> that b) the script was not introduced by David Faure but instead by 
> Stefan Westerfeld  (on Jan 28 2000).
> 
> Does it seem likely that you made a typo in the email?

It's possible. It's been rather a long time and I no longer have any
record of where I extracted the address from.

> Would you agree that it makes better sense to emphasize the _original_ author 
> than the 
> (I guess) later maintainer?

If that's the case, sure. I don't recall seeing any name other than
Faure's at the time however.

Regards,

Adam

Bug#806591: qscintilla2: FTBFS on sparc64 due to mismatched symbols files

[Scott Kitterman]

On Saturday, May 14, 2016 01:39:11 PM John Paul Adrian Glaubitz wrote:
> Hi Scott!
> 
> > c++ symbols files are a paint o deal with and do (particularly in
> > qscintilla's case vary per-architecture.  Updating only one
> > architecture tends to be error prone.  I will include a fix for this
> > with the next new upstream release when all archs need updating.
> 
> Any news on this?
> 
> Looks like you recently uploaded a new upstream release, so I assume
> you forgot to update the symbols file.
> 
> Could you please fix this in the next upload?

I just looked at fixing this, but I see that the build log for the current 
version, qscintilla2_2.9.2+dfsg-2, is not on buildd.d.o.  Due to the new Qt 
version there were some considerable additional changes in the symbols.  If 
you can provide a log with at least the symbols changes for 
qscintilla2_2.9.2+dfsg-2, I should be able to include this in the next upload 
in the next days.

Scott K

Bug#828403: libopkele: FTBFS with openssl 1.1.0

[NIIBE Yutaka]

On 06/26/2016 07:22 PM, Kurt Roeckx wrote:
> Source: libopkele
> Version: 2.0.4-8.1
> Severity: important
> Control: block 827061 by -1
> 
> Hi,
> 
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libopkele_2.0.4-8.1_amd64-20160529-1443
> 
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of 
> the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful 
> information.

Thank you for the notice.  I located the issue.  The following
change of OpenSSL breaks libopkele.


https://github.com/openssl/openssl/commit/0aeddcfa61250a6c474c4f8b3533772a63192f1b

I have a patch for libopkele for this problem (attached below).

So, libopkele is ready for the transition.


Index: libopkele/lib/basic_op.cc
===
--- libopkele.orig/lib/basic_op.cc
+++ libopkele/lib/basic_op.cc
@@ -64,6 +64,8 @@ namespace opkele {
const basic_openid_message& inm) try {
assert(inm.get_field("mode")=="associate");
util::dh_t dh;
+   BIGNUM *p, *g;
+   const BIGNUM *pub_key;
util::bignum_t c_pub;
unsigned char key_digest[SHA256_DIGEST_LENGTH];
size_t d_len = 0;
@@ -73,14 +75,16 @@ namespace opkele {
if(!(dh = DH_new()))
throw exception_openssl(OPKELE_CP_ "failed to DH_new()");
c_pub = util::base64_to_bignum(inm.get_field("dh_consumer_public"));
-   try { dh->p = util::base64_to_bignum(inm.get_field("dh_modulus"));
+   try { p = util::base64_to_bignum(inm.get_field("dh_modulus"));
}catch(failed_lookup&) {
-   dh->p = util::dec_to_bignum(data::_default_p); }
-   try { dh->g = util::base64_to_bignum(inm.get_field("dh_gen"));
+   p = util::dec_to_bignum(data::_default_p); }
+   try { g = util::base64_to_bignum(inm.get_field("dh_gen"));
}catch(failed_lookup&) {
-   dh->g = util::dec_to_bignum(data::_default_g); }
+   g = util::dec_to_bignum(data::_default_g); }
+   DH_set0_pqg(dh, p, NULL, g);
if(!DH_generate_key(dh))
throw exception_openssl(OPKELE_CP_ "failed to 
DH_generate_key()");
+   DH_get0_key(dh, _key, NULL);
vector ck(DH_size(dh)+1);
unsigned char *ckptr = &(ck.front())+1;
int cklen = DH_compute_key(ckptr,c_pub,dh);
@@ -113,7 +117,7 @@ namespace opkele {
if(d_len != secret.size())
throw bad_input(OPKELE_CP_ "Association secret and session MAC 
are
not of the same size");
oum.set_field("session_type",sts);
-   
oum.set_field("dh_server_public",util::bignum_to_base64(dh->pub_key));
+   oum.set_field("dh_server_public",util::bignum_to_base64(pub_key));
string b64; secret.enxor_to_base64(key_digest,b64);
oum.set_field("enc_mac_key",b64);
}else /* TODO: support cleartext over encrypted connection */
Index: libopkele/lib/basic_rp.cc
===
--- libopkele.orig/lib/basic_rp.cc
+++ libopkele/lib/basic_rp.cc
@@ -78,18 +78,22 @@ namespace opkele {

 assoc_t basic_RP::associate(const string& OP) {
util::dh_t dh = DH_new();
+   BIGNUM *p, *g;
+   const BIGNUM *pub_key;
if(!dh)
throw exception_openssl(OPKELE_CP_ "failed to DH_new()");
-   dh->p = util::dec_to_bignum(data::_default_p);
-   dh->g = util::dec_to_bignum(data::_default_g);
+   p = util::dec_to_bignum(data::_default_p);
+   g = util::dec_to_bignum(data::_default_g);
+   DH_set0_pqg(dh, p, NULL, g);
if(!DH_generate_key(dh))
throw exception_openssl(OPKELE_CP_ "failed to DH_generate_key()");
+   DH_get0_key(dh, _key, NULL);
openid_message_t req;
req.set_field("ns",OIURI_OPENID20);
req.set_field("mode","associate");
-   req.set_field("dh_modulus",util::bignum_to_base64(dh->p));
-   req.set_field("dh_gen",util::bignum_to_base64(dh->g));
-   req.set_field("dh_consumer_public",util::bignum_to_base64(dh->pub_key));
+   req.set_field("dh_modulus",util::bignum_to_base64(p));
+   req.set_field("dh_gen",util::bignum_to_base64(g));
+   req.set_field("dh_consumer_public",util::bignum_to_base64(pub_key));
openid_message_t res;
req.set_field("assoc_type","HMAC-SHA256");
req.set_field("session_type","DH-SHA256");
-- 

Bug#828851: RM: libboost-context1.58-dev libboost-context1.58.0 libboost-coroutine1.58-dev libboost-coroutine1.58.0 [s390x] -- RoQA; ANAIS; s390x removed from allowed architecture

[Scott Kitterman]

On Tue, 28 Jun 2016 14:04:05 + Mattia Rizzolo  wrote:
> package: ftp.debian.org
> 
> dannf removed (in version 1.58.0+dfsg-5.1) s390x from the allowed archs
> of those binaries, so they are now obsolete in that architecture, and
> not even detected as cruft.  Nontheless britney see the lack of updated
> version of those binaries as a regression, so they apparently need to be
> RMed.

I went ahead and processed this despite:

Checking reverse dependencies...
# Broken Depends:
boost-defaults: libboost-context-dev
libboost-coroutine-dev


Please ensure the architecture list for boost-defaults is updated too.

Scott K

Bug#828199: RM: python-pysam [armel mipsel] -- ROM; FTBFS (test suite failures)

[Scott Kitterman]

On Sat, 25 Jun 2016 18:52:05 -0700 Afif Elghraoui  wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> 
> Up until the 0.9.1 upstream release, the test suite had spurious failures, 
so they were being ignored.
> Now that the exit status is not ignored, we notice real test failures on 
armel and mipsel, so even though the 0.9.0 package successfully compiled there 
before, the package is probably still failing those tests and should be 
removed from those architectures.

There are a number of rdepends that need to be dealt with:

Checking reverse dependencies...
# Broken Depends:
ariba: ariba
circlator: circlator
pbalign: python-pbalign
pbsuite: pbhoney
 python-pbsuite-utils
python-pbcore: python-pbcore

Please remove the moreinfo tag once that's done.

Scott K

Bug#828700: RFS: twinkle/1.9.0+git20160520.0.be8b8df+dfsg-1 [binNEW] -- Voice over Internet Protocol (VoIP) SIP Phone

[Peter Colberg]

Hi Gianfranco,

Thanks for sponsoring the binNEW upload of twinkle.

I had a closer look at the lintian warning issued by debomatic:

  X: twinkle source: maybe-not-arch-all-binnmuable twinkle -> twinkle-common
  N: 
  N:Tag to attempt to measure the number of packages that might have an
  N:issue with arch:all binNMUs.
  N:
  N:At this time, please do  attempt to "fix" the problem. It is not
  N:clear what the solution is (if any at all). Nor is it clear that this is
  N:something that will be supported.
  N:
  N:Severity: wishlist, Certainty: possible
  N:
  N:Check: version-substvars, Type: source
  N:
  N:This tag is marked experimental, which means that the code that
  N:generates it is not as well-tested as the rest of Lintian and might
  N:still give surprising results. Feel free to ignore experimental tags
  N:that do not seem to make sense, though of course bug reports are always
  N:welcome.
  N: 

This experimental check not only flags twinkle but all packages that
have a "Depends: foo (= ${source:Version})" on an arch:all package.
As stated, there is nothing that can be done to solve that at the
moment, since neither ${binary:Version} nor ${source:Version} would
be appropriate for the case of an arch:all binNMU.

Peter

Bug#828932: TAG: Lantern -- A popular Internet censorship circumvention tool

[2xinagzi]

Package: wnpp
Severity: RFP

Package description:
Lantern is a free desktop application that delivers fast, reliable and
secure access to the open Internet for users in censored regions. It
uses a variety of techniques to stay unblocked, including P2P and domain
fronting. Lantern relies on users in uncensored regions acting as access
points to the open Internet.

Lantern is also one of a few tools that works well in China. Some
projects, such as Lantern-Gateway, rely on it, so it would be great if
someone could maintain it for Debian.

Copyright:https://github.com/getlantern/lantern/blob/devel/LICENSE

URL:https://github.com/getlantern/lantern



signature.asc
Description: OpenPGP digital signature

Bug#828907: plymouth external firmware error

[Laurent Bigonville]

Le 28/06/16 à 22:54, Cedric Brandenbourger a écrit :

Package: plymouth
Version: 0.9.2-3+b1
Severity: important

Dear Maintainer,


Hello,


* What led up to the situation?

I have to use an external firmware for my GK106 graphic card due to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=93629
This working quite well, but when i install plymouth and change the theme from
"details" to "spinner" i'm getting error when i update initramfs


sudo plymouth-set-default-theme -R spinner
update-initramfs: Generating /boot/initrd.img-4.6.0-1-amd64
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_method_init.bin
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_nonctx.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_ctx.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_sig.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_sig.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_data.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_inst.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_bl.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_unload.bin
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_load.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/bl.bin for module
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_method

the package firmware-linux-nonfree and firmware-linux-misc are installed.


When i reboot i'm getting the following error message

kernel: [1.968430] nouveau :01:00.0: firmware: failed to load
nvidia/gk106/fecs_inst.bin (-2)
kernel: [1.968434] nouveau :01:00.0: Direct firmware load for
nvidia/gk106/fecs_inst.bin failed with error -2

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

i installed plymouth


I don't think this is related to plymouth.

Did you try to install firmware-misc-nonfree ?

Bug#811984: qscintilla2: FTBFS with GCC 6: symbol changes

[Scott Kitterman]

On Tuesday, January 19, 2016 08:13:26 PM Martin Michlmayr wrote:
> Package: qscintilla2
> Version: 2.9.1+dfsg-4
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-symbols
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
> 
> Note that only the first error is reported; there might be more.  You
> can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
> you can set CC=gcc-6 CXX=g++-6 explicitly.
> 
> You may be able to find out more about this issue at
> https://gcc.gnu.org/gcc-6/changes.html
> 
> > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> 
> ...
> 
> > dpkg-gensymbols: warning: some new symbols appeared in the symbols file:
> > see diff output below dpkg-gensymbols: warning: some symbols or patterns
> > disappeared in the symbols file: see diff output below dpkg-gensymbols:
> > warning: debian/libqscintilla2-12v5/DEBIAN/symbols doesn't match
> > completely debian/libqscintilla2-12v5.symbols ---
> > debian/libqscintilla2-12v5.symbols
> > (libqscintilla2-12v5_2.9.1+dfsg-4_amd64) +++
> > dpkg-gensymbolsv15vh4   2016-01-19 21:14:51.112125090 +
> > @@ -96,6 +96,13 @@
> > 
> >   _Z5IsEOLi@Base 2.8.4
> >   _Z5issmli@Base 2.8.4
> >   _Z5qRgba@Base 2.8.4
> > 
> > + _Z5qSwapI12QFontPrivateEvR28QExplicitlySharedDataPointerIT_ES4_@Base
> > 2.9.1+dfsg-4 + _Z5qSwapIP12QFontPrivateEvRT_S3_@Base 2.9.1+dfsg-4
> > + _Z5qSwapIP8QMapDataEvRT_S3_@Base 2.9.1+dfsg-4
> > + _Z5qSwapIPN10QByteArray4DataEEvRT_S4_@Base 2.9.1+dfsg-4
> > + _Z5qSwapIPN7QString4DataEEvRT_S4_@Base 2.9.1+dfsg-4
> > + _Z5qSwapIPN9QListData4DataEEvRT_S4_@Base 2.9.1+dfsg-4
> > + _Z5qSwapIjEvRT_S1_@Base 2.9.1+dfsg-4
> > 
> >   _Z6iscamli@Base 2.8.4
> >   _Z6issmldi@Base 2.8.4
> >   _Z6issmlfi@Base 2.8.4
> > 
> > @@ -258,6 +265,7 @@
> > 
> >   _ZN10QByteArrayC2Ev@Base 2.8.4
> >   _ZN10QByteArrayD1Ev@Base 2.8.4
> >   _ZN10QByteArrayD2Ev@Base 2.8.4
> > 
> > + _ZN10QByteArrayaSEOS_@Base 2.9.1+dfsg-4
> > 
> >   _ZN10QByteArraypLEc@Base 2.8.4
> >   _ZN10QDropEvent20acceptProposedActionEv@Base 2.8.4
> >   _ZN10QsciLexerD11qt_metacallEN11QMetaObject4CallEiPPv@Base 2.8.4
> > 
> > @@ -403,12 +411,15 @@
> 
> ...
> 
> The diff was 1.5 MB so I didn't include everything.  I can send you a
> log if you want.
> 
> Martin

Once GCC-6 is default, I'll update the symbols files.  It's premature to do it 
now.

Scott K

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

Bug#828931: llvm-toolchain-3.7: FTBFS on i386 with gcc-6 and glibc 2.23

[Daniel Schepler]

Source: llvm-toolchain-3.7
Version: 1:3.7.1-2
Severity: important

>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:

...
==
ERROR: test_lldbmi_tokens (TestMiSyntax.MiSyntaxTestCase)
   Test that 'lldb-mi --interpreter' prints command tokens.
--
Traceback (most recent call last):
  File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/lldbtest.py", line
483, in wrapper
return func(self, *args, **kwargs)
  File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/lldbtest.py", line
598, in wrapper
func(*args, **kwargs)
  File 
"/build/llvm-toolchain-3.7-3.7.1/lldb/test/tools/lldb-mi/syntax/TestMiSyntax.py",
line 30, in test_lldbmi_tokens
self.expect("\*stopped,reason=\"breakpoint-hit\"")
  File 
"/build/llvm-toolchain-3.7-3.7.1/lldb/test/tools/lldb-mi/lldbmi_testcase.py",
line 48, in expect
return self.child.expect(pattern, *args, **kwargs)
  File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/pexpect-2.4/pexpect.py",
line 1316, in expect
return self.expect_list(compiled_pattern_list, timeout, searchwindowsize)
  File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/pexpect-2.4/pexpect.py",
line 1330, in expect_list
return self.expect_loop(searcher_re(pattern_list), timeout,
searchwindowsize)
  File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/pexpect-2.4/pexpect.py",
line 1414, in expect_loop
raise TIMEOUT (str(e) + '\n' + str(self))
TIMEOUT: Timeout exceeded in read_nonblocking().

version: 2.4 ($Revision: 516 $)
command: /build/llvm-toolchain-3.7-3.7.1/build-llvm/Release/bin/lldb-mi
args: ['/build/llvm-toolchain-3.7-3.7.1/build-llvm/Release/bin/lldb-mi',
'--interpreter']
searcher: searcher_re:
0: re.compile("\*stopped,reason="breakpoint-hit"")
buffer (last 100 chars): mi/syntax/a.out",symbols-loaded="0",loaded_addr="-"
(gdb)
*running,thread-id="all"
(gdb)
(gdb)

before (last 100 chars): mi/syntax/a.out",symbols-loaded="0",loaded_addr="-"
(gdb)
*running,thread-id="all"
(gdb)
(gdb)

after: 
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 29937
child_fd: 4
closed: False
timeout: 30
delimiter: 
logfile: None
logfile_read: 
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
Config=i686-gcc-6
--
RESULT: FAILED (0 passes, 0 failures, 2 errors, 0 skipped, 1 expected
failures, 0 unexpected successes)

 381 out of 388 test suites processed
-- 
Daniel Schepler

Bug#828930: guice: FTBFS: the artifact org.apache.ant:ant:jar:debian has not been downloaded

[Daniel Schepler]

Source: guice
Version: 4.0-2
Severity: serious

>From my pbuilder build log:
...
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Google Guice ... SUCCESS [  0.523 s]
[INFO] Google Guice - Bill of Materials ... SUCCESS [  0.011 s]
[INFO] Google Guice - Core Library  FAILURE [  0.091 s]
[INFO] Google Guice - Extensions .. SKIPPED
[INFO] Google Guice - Extensions - AssistedInject . SKIPPED
[INFO] Google Guice - Extensions - MultiBindings .. SKIPPED
[INFO] Google Guice - Extensions - Grapher  SKIPPED
[INFO] Google Guice - Extensions - JMX  SKIPPED
[INFO] Google Guice - Extensions - JNDI ... SKIPPED
[INFO] Google Guice - Extensions - Servlet  SKIPPED
[INFO] Google Guice - Extensions - Spring . SKIPPED
[INFO] Google Guice - Extensions - ThrowingProviders .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.943 s
[INFO] Finished at: 2016-06-28T17:26:42+00:00
[INFO] Final Memory: 14M/219M
[INFO] 
[ERROR] Failed to execute goal on project guice: Could not resolve
dependencies for project com.google.inject:guice:jar:4.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 :guice
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/guice-4.0
-Dclassworlds.conf=/etc/maven/m2-debian.conf
-Dproperties.file.manual=/build/guice-4.0/debian/maven.properties
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/guice-4.0/debian
-Dmaven.repo.local=/build/guice-4.0/debian/maven-repo package
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true
-Dlocale=en_US returned exit code 1
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#828929: cairocffi: FTBFS with gcc-6 and glibc 2.23

[Daniel Schepler]

Source: cairocffi
Version: 0.7.2-1
Severity: important

>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/cairocffi-0.7.2'
LC_ALL=C.UTF-8 xvfb-run -a --server-args="-screen 0 1024x768x24" dh_auto_test
I: pybuild base:184: cd
/build/cairocffi-0.7.2/.pybuild/pythonX.Y_2.7/build; python2.7 -m
pytest
= test session starts ==
platform linux2 -- Python 2.7.12rc1, pytest-2.9.2, py-1.4.31, pluggy-0.3.1
rootdir: /build/cairocffi-0.7.2, inifile:
collected 44 items

cairocffi/test_cairo.py ..
cairocffi/test_pixbuf.py 
cairocffi/test_xcb.py .Aborted
E: pybuild pybuild:274: test: plugin distutils failed with: exit
code=134: cd /build/cairocffi-0.7.2/.pybuild/pythonX.Y_2.7/build;
python2.7 -m pytest
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/build/cairocffi-0.7.2'
debian/rules:11: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#828928: opencv: FTBFS with gcc-6 and glibc 2.23

[Daniel Schepler]

Source: opencv
Version: 2.4.9.1+dfsg-2
Severity: important

>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:

...
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp: In
member function 'void
cv::ChamferMatcher::Matching::computeDistanceTransform(cv::Mat&,
cv::Mat&, cv::Mat&, float, float, float)':
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp:969:30:
error: the compiler can assume that the address of 'annotate_img' will
never be NULL [-Werror=address]
 if (_img!=NULL) {
  ^
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp:1016:34:
error: the compiler can assume that the address of 'annotate_img' will
never be NULL [-Werror=address]
 if (_img!=NULL) {
  ^
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp: In
member function 'cv::ChamferMatcher::Match*
cv::ChamferMatcher::Matching::localChamferDistance(cv::Point,
cv::Mat&, cv::Mat&, cv::ChamferMatcher::Template*, float)':
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp::25:
error: the compiler can assume that the address of 'orientation_img'
will never be NULL [-Werror=address]
 if (_img!=NULL) {
 ^
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp::5:
warning: nonnull argument 'orientation_img' compared to NULL
[-Wnonnull-compare]
 if (_img!=NULL) {
 ^~
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp: In
member function 'void
cv::ChamferMatcher::Matching::computeDistanceTransform(cv::Mat&,
cv::Mat&, cv::Mat&, float, float, float)':
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp:1016:17:
warning: nonnull argument 'annotate_img' compared to NULL
[-Wnonnull-compare]
 if (_img!=NULL) {
 ^~
/build/opencv-2.4.9.1+dfsg/modules/contrib/src/chamfermatching.cpp:969:13:
warning: nonnull argument 'annotate_img' compared to NULL
[-Wnonnull-compare]
 if (_img!=NULL) {
 ^~
cc1plus: some warnings being treated as errors
modules/contrib/CMakeFiles/opencv_contrib.dir/build.make:377: recipe
for target 
'modules/contrib/CMakeFiles/opencv_contrib.dir/src/chamfermatching.cpp.o'
failed
make[3]: *** 
[modules/contrib/CMakeFiles/opencv_contrib.dir/src/chamfermatching.cpp.o]
Error 1
make[3]: Leaving directory '/build/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:1987: recipe for target
'modules/contrib/CMakeFiles/opencv_contrib.dir/all' failed
make[2]: *** [modules/contrib/CMakeFiles/opencv_contrib.dir/all] Error 2
make[2]: Leaving directory '/build/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu'
Makefile:152: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu'
dh_auto_build: make -j1 returned exit code 2
debian/rules:75: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#828927: strigi: FTBFS with gcc-6 and glibc 2.23

[Daniel Schepler]

Source: strigi
Version: 0.7.8-2.1
Severity: important

>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:

...
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:
In static member function 'static void
CLuceneIndexReader::Private::addField(lucene::document::Field*,
Strigi::IndexedDocument&)':
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:325:37:
error: no matching function for call to
'make_pair(std::__cxx11::string, std::__cxx11::string&)'
 wchartoutf8(name), value));
 ^
In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
 from /usr/include/c++/6/bits/stl_tree.h:63,
 from /usr/include/c++/6/map:60,
 from
/build/strigi-0.7.8/libstreamanalyzer/include/strigi/indexeddocument.h:23,
 from
/build/strigi-0.7.8/libstreamanalyzer/include/strigi/indexreader.h:24,
 from
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.h:24,
 from
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:21:
/usr/include/c++/6/bits/stl_pair.h:425:5: note: candidate:
template constexpr std::pair::__type, typename
std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _T2&&)
 make_pair(_T1&& __x, _T2&& __y)
 ^
/usr/include/c++/6/bits/stl_pair.h:425:5: note:   template argument
deduction/substitution failed:
/build/strigi-0.7.8/libstreamanalyzer/plugins/indexers/clucenengindexer/cluceneindexreader.cpp:325:37:
note:   cannot convert 'value' (type 'std::__cxx11::string {aka
std::__cxx11::basic_string}') to type
'std::__cxx11::basic_string&&'
 wchartoutf8(name), value));
 ^
...
make[3]: Leaving directory '/build/strigi-0.7.8/obj-x86_64-linux-gnu'
[ 85%] Built target perfieldxml
make[2]: Leaving directory '/build/strigi-0.7.8/obj-x86_64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/strigi-0.7.8/obj-x86_64-linux-gnu'
dh_auto_build: make -j8 returned exit code 2
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#828889: RFS: elisp-slime-nav-el/0.9-1 ITP

[Sergio Durigan Junior]

On Tuesday, June 28 2016, Dmitry Bogatov wrote:

> Dear mentors,
>
> I am looking for a sponsor for my package "elisp-slime-nav-el"
>
> * Package name: elisp-slime-nav-el
>   Version : 0.9-1
>   Upstream Author : Steve Purcell 
> * Url : https://github.com/purcell/elisp-slime-nav
> * Licenses: GPL-3+
>   Section : lisp

Hey Dmitry,

Thanks for the package.  Just a quick review because I'm not at my
Debian machine right now.

A few things pop out when I looked at the mentors.d.n for your package.

1) The links listed on the Vcs-* fields are not valid, so perhaps you
may want to (a) push your git repo temporarily at another URL, or (b)
create the repo under collab-maint/ and push your things there.

2) It seems you forgot to set the distribution to 'unstable' on your
debian/changelog file.

3) Any reason why you're using debhelper version 10?  It's still
experimental, so you probably should be using version 9.

For now, that's all I have.  I will try to look at the package later and
see if I have any more comments about it.

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Bug#828926: wxwidgets3.0: FTBFS with gcc-6 and glibc 2.23

[Daniel Schepler]

Source: wxwidgets3.0
Version: 3.0.2+dfsg-1.4
Severity: important

>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:

...
../src/stc/scintilla/src/Editor.cxx: In member function 'long int
Editor::FindText(uptr_t, sptr_t)':
../src/stc/scintilla/src/Editor.cxx:5708:7: warning: 'template
class std::auto_ptr' is deprecated [-Wdeprecated-declarations]
  std::auto_ptr pcf(CaseFolderForEncoding());
   ^~~~
In file included from /usr/include/c++/6/memory:81:0,
 from ../src/stc/scintilla/src/Editor.cxx:18:
/usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
   template class auto_ptr;
^~~~
../src/stc/scintilla/src/Editor.cxx: In function 'bool Close(Point, Point)':
../src/stc/scintilla/src/Editor.cxx:5844:23: error: call of overloaded
'abs(XYPOSITION)' is ambiguous
  if (abs(pt1.x - pt2.x) > 3)
   ^
In file included from /usr/include/c++/6/cstdlib:75:0,
 from /usr/include/c++/6/stdlib.h:36,
 from ../src/stc/scintilla/src/Editor.cxx:8:
/usr/include/stdlib.h:774:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/6/stdlib.h:36:0,
 from ../src/stc/scintilla/src/Editor.cxx:8:
/usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
   ^~~
/usr/include/c++/6/cstdlib:180:3: note: candidate: long long int
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
../src/stc/scintilla/src/Editor.cxx:5846:23: error: call of overloaded
'abs(XYPOSITION)' is ambiguous
  if (abs(pt1.y - pt2.y) > 3)
   ^
...
Makefile:16880: recipe for target 'wxscintilla_Editor.o' failed
make[1]: *** [wxscintilla_Editor.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/build/wxwidgets3.0-3.0.2+dfsg/objs_gtk_sh'
debian/rules:288: recipe for target 'build-gtk-shared-stamp' failed
make: *** [build-gtk-shared-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

Bug#490962: "Me too" for #490962

[Elliott Mitchell]

Control: found -1 1.0.9.8.3

There are many people for whom this would be a rather valuable feature.

I suspect bug #340500 would be considered a blocking bug for #490962
(dpkg does need that feature for #490962 to be implemented).  I also
think #549089 could be merged with #490962; there are differences between
what exactly is being asked for, but they're essentially the same
functionality.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#340500: #340500 would be useful for many things

[Elliott Mitchell]

Control: found -1 1.17.27

>From looking at other bugs, I'd suggest #340500 would be helpful to take
the form of tags for packages.  At which point would be a blocking
feature for #490962.

I agree with the bug submitter, this would be a rather helpful feature.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#828925: warnings upon start

[積丹尼 Dan Jacobson]

Package: qgis
Version: 2.14.3+dfsg-2
Severity: minor

Warning: QCss::Parser - Failed to load file  "/style.qss"
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
Warning: QFileSystemWatcher: failed to add paths: 
/home/jidanni/.qgis2//project_templates
Warning: QMetaObject::connectSlotsByName: No matching signal for 
on_wvDetails_linkClicked(QUrl)

Bug#828147: midori ruined

[Sergio Durigan Junior]

On Saturday, June 25 2016, 積丹尼 Dan Jacobson wrote:

> Downgrading midori from 0.5.11-ds1-100~exp1 to 0.5.11-ds1-2 fixes it.

I've just uploaded midori_0.5.12~wk2 into experimental.  This package is
built from the current development branch of Midori (well, one of them
at least) and contains several bug fixes.  Could you give it a try,
please?

It's worth mentioning that I don't know if this experimental package
will indeed become the official Midori 0.5.12, but it seems that this is
very likely to happen, so that's why I named the package that way.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#828924: Couldn't load plugin 'processing'

[積丹尼 Dan Jacobson]

Package: qgis
Version: 2.14.3+dfsg-2

Couldn't load plugin 'processing'

ImportError: No module named QtWebKit.QWebView
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 281, in loadPlugin
__import__(packageName)
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 572, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File "/usr/share/qgis/python/plugins/processing/__init__.py", line 29, in
from processing.tools.general import *
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 572, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File "/usr/share/qgis/python/plugins/processing/tools/general.py", line 28, in
from processing.core.Processing import Processing
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 572, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File "/usr/share/qgis/python/plugins/processing/core/Processing.py", line 44, 
in
from processing.gui.Postprocessing import handleAlgorithmResults
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 572, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File "/usr/share/qgis/python/plugins/processing/gui/Postprocessing.py", line 
39, in
from processing.gui.ResultsDialog import ResultsDialog
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 572, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File "/usr/share/qgis/python/plugins/processing/gui/ResultsDialog.py", line 
38, in
os.path.join(pluginPath, 'ui', 'DlgResults.ui'))
  File "/usr/lib/python2.7/dist-packages/PyQt4/uic/__init__.py", line 211, in 
loadUiType
exec(code_string.getvalue(), ui_globals)
  File "", line 52, in
  File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 572, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
ImportError: No module named QtWebKit.QWebView


Python version: 2.7.12rc1 (default, Jun 13 2016, 09:20:59) [GCC 5.4.0 20160609]
QGIS version: 2.14.3-Essen Essen, exported

Python Path:
/usr/share/qgis/python
/home/jidanni/.qgis2/python
/home/jidanni/.qgis2/python/plugins
/usr/share/qgis/python/plugins
/usr/lib/python2.7
/usr/lib/python2.7/plat-i386-linux-gnu
/usr/lib/python2.7/lib-tk
/usr/lib/python2.7/lib-old
/usr/lib/python2.7/lib-dynload
/usr/local/lib/python2.7/dist-packages
/usr/lib/python2.7/dist-packages
/usr/lib/python2.7/dist-packages/PILcompat
/usr/lib/python2.7/dist-packages/gtk-2.0
/home/jidanni/.qgis2//python
/home/jidanni/.qgis2/python/plugins/mmqgis/forms
/usr/share/qgis/python/plugins/fTools/tools

Bug#828805: newlisp: FTBFS on non-Linux: Could not discover your OS platform

[Sergio Durigan Junior]

On Monday, June 27 2016, Aaron M. Ucko wrote:

> Builds of newlisp on kFreeBSD and the Hurd have failed with a cascade
> of errors starting with
>
>   ./configure
>   
>   removing old objects and setting correct permissions ...
>   discovering platform and default memory model ...
>   
>   Could not discover your OS platform

BTW, I think I have a patch for this but I'm still waiting for someone
to provide me access to a GNU/kFreeBSD machine in order to test.  I
think I might get a reply tomorrow.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#828147: midori ruined

[積丹尼 Dan Jacobson]

OK I will do all the tests next time I power up that small machine.

Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1

[Henrique de Moraes Holschuh]

On Tue, 28 Jun 2016, Jochen Sprickerhof wrote:
> * Henrique de Moraes Holschuh  [2016-06-28 10:06]:
> > Should a firmware update not be available yet from your system vendor,
> > please request on their support channels a BIOS/UEFI update that has:
> 
> There is no update available, I've send them a mail.

Can you send to this bug report the "microcode: ... sig=..., pf=..."
line logged by the kernel that does boot, please?

ARCH Linux also got a report similar to this:
https://bugs.archlinux.org/task/49806

Relevant information from the ArchLinux report:
Same processor as in this report (i7-6500U), even older microcode: 0x49,
failed to boot.

An i3-6100T Skylake-S updated fine from revision 0x39 to 0x8A (506e3)
An m3-6y30  Skylake-Y updated fine from revision 0x74 to 0x8A (406e3)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Bug#779077: apache2-bin: crash with segmentation fault if gracefully reloaded twice too quickly

[Damien Norris]

This problem has started for me across the board since upgrading to Jessie. 

I believe it is this upstream bug:  
https://bz.apache.org/bugzilla/show_bug.cgi?id=48769 

The patch mentioned in Comment #7 might solve the problem?  I will work on 
reproducing the problem and then see if that patch helps.  The upstream bug 
also has a great method for reproducing the problem.

Bug#817778: info-beamer: nmu 1.0~pre3+dfsg-0.1

[James Cowgill]

Control: tags -1 pending

Hi,

I have uploaded an NMU to DELAYED/10 to fix the following bugs. Please
tell me if I should cancel / delay it.
 #817778 silkscreen font is not DFSG compliant
 #826288 info-beamer: please use glfw3

The NMU debdiff is attached. As part of the upload, the .git directory
from the original tarball was removed (since it will also contain a
non-dfsg copy of silkscreen). To avoid loads of cruft appearing in the
debdiff, I generated it using --exclude='\.git'

I have also uploaded it to mentors so you can get a copy of the new
orig tarball if you want.
https://mentors.debian.net/debian/pool/main/i/info-beamer/info-beamer_1.0~pre3+dfsg-0.1.dsc

Thanks,
Jamesdiff -Nru --exclude '\.git' info-beamer-1.0~pre3/debian/changelog info-beamer-1.0~pre3+dfsg/debian/changelog
--- info-beamer-1.0~pre3/debian/changelog	2016-03-06 21:31:10.0 +
+++ info-beamer-1.0~pre3+dfsg/debian/changelog	2016-06-29 01:48:16.0 +0100
@@ -1,3 +1,15 @@
+info-beamer (1.0~pre3+dfsg-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove non-free silkscreen.ttf font. (Closes: #817778)
+- Also remove .git folder from upstream tarball which is likely to
+  contain copy of the font.
+  * Remove use of git from the build system.
+- It no longer works after the .git directory was removed.
+  * Port to GLFW 3. (Closes: #826288)
+
+ -- James Cowgill   Wed, 29 Jun 2016 01:46:17 +0100
+
 info-beamer (1.0~pre3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru --exclude '\.git' info-beamer-1.0~pre3/debian/control info-beamer-1.0~pre3+dfsg/debian/control
--- info-beamer-1.0~pre3/debian/control	2015-01-16 10:56:16.0 +
+++ info-beamer-1.0~pre3+dfsg/debian/control	2016-06-29 00:39:23.0 +0100
@@ -2,7 +2,7 @@
 Section: misc
 Priority: optional
 Maintainer: Noël Köthe 
-Build-Depends: debhelper (>= 9), liblua5.1-dev, libevent-dev, libglfw-dev, libglew1.5-dev, libftgl-dev, libavcodec-dev, libswscale-dev, libavformat-dev, libdevil-dev, lua5.1, git
+Build-Depends: debhelper (>= 9), liblua5.1-dev, libevent-dev, libglfw3-dev, libglew1.5-dev, libftgl-dev, libavcodec-dev, libswscale-dev, libavformat-dev, libdevil-dev, lua5.1
 Standards-Version: 3.9.5
 Homepage: https://info-beamer.com/opensource
 
diff -Nru --exclude '\.git' info-beamer-1.0~pre3/debian/copyright info-beamer-1.0~pre3+dfsg/debian/copyright
--- info-beamer-1.0~pre3/debian/copyright	2015-01-16 12:30:02.0 +
+++ info-beamer-1.0~pre3+dfsg/debian/copyright	2016-06-28 23:49:02.0 +0100
@@ -1,6 +1,9 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: info-beamer
 Source: https://github.com/dividuum/info-beamer
+Files-Excluded:
+ samples/hello/README.silkscreen.txt
+ samples/hello/silkscreen.ttf
 
 Files: *
 Copyright: 2013,2014 Florian Wesch 
diff -Nru --exclude '\.git' info-beamer-1.0~pre3/debian/patches/glfw3.patch info-beamer-1.0~pre3+dfsg/debian/patches/glfw3.patch
--- info-beamer-1.0~pre3/debian/patches/glfw3.patch	1970-01-01 01:00:00.0 +0100
+++ info-beamer-1.0~pre3+dfsg/debian/patches/glfw3.patch	2016-06-29 00:26:31.0 +0100
@@ -0,0 +1,143 @@
+Description: Port to GLFW 3
+ Backported from upstream. Unnessesary X11 dependencies removed.
+Origin: backport, https://github.com/dividuum/info-beamer/commit/721e66ad96145452b048e4c9a8395e858ebd2f7f
+Bug: https://github.com/dividuum/info-beamer/issues/16
+Bug-Debian: https://bugs.debian.org/826288
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/font.c
 b/font.c
+@@ -5,7 +5,6 @@
+ #include 
+ 
+ #include 
+-#include 
+ #include 
+ #include 
+ #include 
+--- a/main.c
 b/main.c
+@@ -23,7 +23,7 @@
+ #include 
+ #include 
+ #include 
+-#include 
++#include 
+ #include 
+ #include 
+ #include 
+@@ -1155,23 +1155,25 @@ static void check_inotify() {
+ /* GUI ===*/
+ 
+ static int win_w, win_h;
++static GLFWwindow *window;
+ 
+-static void GLFWCALL reshape(int width, int height) {
++static void reshape(GLFWwindow* window, int width, int height) {
+ win_w = width;
+ win_h = height;
+ fprintf(stderr, INFO("resized to %dx%d\n"), width, height);
+ }
+ 
+-static void GLFWCALL keypressed(int key, int action) {
+-if (action == GLFW_PRESS) {
+-switch (key) {
+-case GLFW_KEY_SPACE:
+-node_profiler();
+-break;
+-case GLFW_KEY_ESC:
+-running = 0;
+-break;
+-}
++static void keypressed(GLFWwindow* window, int key, int scancode, int action, int mods) {
++if (action != GLFW_PRESS)
++return;
++
++switch (key) {
++case GLFW_KEY_SPACE:
++node_profiler();
++break;
++case GLFW_KEY_ESCAPE:
++running = 0;
++break;
+ }
+ }
+ 
+@@ -1435,11 +1437,12 @@ static void tick() {
+ 

Bug#827186: Fwd: Bug#827186: links2: Setting "-only-proxies 1" also sets "-http.fake-firefox 1" unconditionally

[Mikulas Patocka]

On Tue, 28 Jun 2016, Axel Beckert wrote:

> Hi Mikulas,
> 
> Mikulas Patocka wrote:
> > On Tue, 28 Jun 2016, Axel Beckert wrote:
> > > while we're at it, this bug report about -only-proxies recently came
> > > in, too, at https://bugs.debian.org/827186. Citing the relevants parts
> > > of the mail with most details:
> > 
> > It is not a bug, it is a feature.
> 
> As mentioned below, I'm aware of that intention. I though still think
> that there is a bug in it:
> 
> > The "only proxies" option is intended to be used when Links is used with 
> > tor.
> [...]
> > > According to the changelog it's a feature since 2.9:
> > > 
> > >   An option to fake Firefox in the HTTP header. It modifies User-Agent and
> > >   several other options to be more Firefox-like. This option is also
> > >   automatically turned on when "Connect only via proxies or Socks (useful
> > >   for tor)" is selected. It makes it safer to use Links with tor.
> > >
> > > But it seems that the name of the "-only-proxies" feature is confusing
> > > people as they don't expect that the User-Agent string is modified by
> > > it and not overridable anymore afterwards. Maybe it's currently a
> > > little bit too overzealous?
> 
> Given your confirmation that the behaviour itself is intended, I think
> the "-only-proxies" option is definitely misnamed as it does not have
> "tor" in its name anywhere and its current name suggests something
> different than it does..
> 
>   Regards, Axel

The fact that this option is for tor is mentioned in the dialog box:
  "[X] Connect only via proxies or Socks (useful for tor)"
and in the manual page:
  -only-proxies <0>/<1>
 (default 0)
  "1" causes that Links won't initiate any non-proxy connection.
  It is useful for anonymization with tor or similar networks.

Command line options should be small, I don't think it's necessary to 
extend the option name to be longer.

Mikulas

Bug#828920: courier-ssl: mkdhparams ignores environment variable BITS

[Fred Drueck]

Inspection of mkdhaparams, reveals to me that it's just a shell script and
that the "bug" is that the environment variable in the shell script is
actually:

$DH_BITS

because the script sets:

BITS="$DH_BITS"

if test "@ssllib@" = "openssl"

then

if test "$BITS" = ""

then

BITS=768

fi

So one way to fix the problem would be to correct the man page.

-Fred

Bug#828923: kde-l10n-he: current version incompatible with old kdenlive-data

[Shai Berger]

Package: kde-l10n-he
Version: 4:16.04.2-2
Severity: important
Tags: l10n

Dear Maintainer,

I am now upgrading a system after a very long time. During the installation, I 
ran
into this error:

Unpacking kde-l10n-he (4:16.04.2-2) over (4:4.14.0-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/kde-l10n-he_4%3a16.04.2-2_all.deb (--unpack):
 trying to overwrite '/usr/share/locale/he/LC_MESSAGES/kdenlive.mo', which is 
also in package kdenlive-data 0.9.10-2

I am guessing that this means the incompatibility between kde-l10n-he 
4:16.04.2-2 and
kdenlive-data 0.9.10-2 is not recorded, or else apt would have found the 
correct order
for doing things (it needed to upgrade kdenlive anyway).

While this is in itself a minor issue, the only way I found to overcome it was 
to remove
kdenlive using dpkg; so, it essentially breaks the upgrade tools. Hence I 
marked it important.
If this is wrong, accept my apologies.

Thanks,
Shai.

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

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

Versions of packages kde-l10n-he depends on:
iu  libkdecore5  4:4.14.21-1
iu  libkf5i18n5  5.23.0-1

kde-l10n-he recommends no packages.

Versions of packages kde-l10n-he suggests:
ii  kde-standard  5:84

-- no debconf information

Bug#827411: piuparts: FTBFS on jessie: 'wheezy' != 'squeeze'

[Andreas Beckmann]

Control: tag -1 - jessie

On 2016-06-16 12:18, Holger Levsen wrote:
> On Thu, Jun 16, 2016 at 11:06:28AM +0100, Dominic Hargreaves wrote:
>>> I'm not sure how to deal with this bug report :-( Maybe this is actually
>>> a bug in distro-info in jessie and this bug should be reassigned there?
>>> (+"affects piuparts")
>>
>> That sounds quite appropriate. JFTR, python-distro-info (0.14).

Are you sure that this isn't a bug in piuparts?
There is a hardcoded mapping from codenames to releases ...

This is from 0.62:

def testConfStdDistroNames(self):
self.assertEqual(self.oldstable, 'squeeze')
self.assertEqual(self.stable, 'wheezy')
self.assertEqual(self.testing, 'jessie')
self.assertEqual(self.unstable, 'sid')
self.assertEqual(self.experimental, 'experimental')

which is incorrect since jessie was released ...

I'm not sure about what this unittest is supposed to accomplish ...

And the bug will manifest again once stretch gets released, therefore
clearing the jessie tag.


Andreas

Bug#828922: Needs to unload loaded FS modules after probing

[Elliott Mitchell]

Package: grub2-common
Version: 2.02~beta2-22+deb8u1
Severity: minor

When `update-grub` is run, it causes *all* filesystem modules present in
/lib/modules for the currently running kernel to be loaded.  None of
these is ever unloaded.

Perhaps this isn't too troublesome for desktops, but depending upon the
machine the additional resource consumption could be troublesome.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#828921: nethogs: cui.cpp:497: void do_refresh(): Assertion `pwuid != __null' failed.

[Ben Longbons]

Package: nethogs
Version: 0.8.1-1
Severity: important

Dear Maintainer,

Whenever I try to run nethogs, it just aborts.

Presumably this is because I have users with no name (because they're
from a separate user_namespace(7) and their name only makes sense for
the id within it).

At the very least `nethogs` should not crash. Possibly, it could also
look up the user *within* that namespace, though care would have to be
taken to avoid confusion with the current namespace's names.

Relevant bits:
/proc/$PID/uidmap (note that in the nested case, this is relative to its
parent - so I'm not sure it is feasible to use correctly)
/proc/$PID/ns/user (for use with setns(2) - needs to be done in a separate
process, but is relatively simple to use)
/proc/$PID/root (to look up /etc/ relative to - or just chroot)
nsenter(1), setns(2)
unshare(1), unshare(2)
subuid(5), newuidmap(1)

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

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

Versions of packages nethogs depends on:
ii  libc62.22-11
ii  libgcc1  1:6.1.1-7
ii  libncurses5  6.0+20160319-1
ii  libpcap0.8   1.7.4-2
ii  libstdc++6   6.1.1-7
ii  libtinfo56.0+20160319-1

nethogs recommends no packages.

nethogs suggests no packages.

-- no debconf information

Bug#764678: dh-systemd: Please support systemd user services

[Michael Biebl]

Am 29.06.2016 um 00:11 schrieb Daniel Kahn Gillmor:
> On Fri 2014-10-10 03:30:07 -0400, Michael Vogt  wrote:
>> It would be very nice if dh-systemd would support systemd user
>> units (both for detecting them during build time and to add
>> something like "systemctl --global enable my-user-unit" to the
>> debian/postinst).
>>
>> My use case is that the package installs a unit that
>> should run at login time for all users. In the past this was 
>> done via the upstart session support. 
> 
> fwiw, i'd like to see this capability for dh-systemd as well.
> 
> One alternative available now is to have the package manually ship a
> symlink in /etc/systemd/user/default.target.wants/$PKGNAME.service
> (pointing to /usr/lib/systemd/user/$PKGNAME.service, assuming the user

Shipping a static symlink in /etc is ugly, I would recommend against
doing that.

Daniel, which service do you have in mind which already requires a
systemd user session and systemd user services?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#828920: courier-ssl: mkdhparams ignores environment variable BITS

[Fred Drueck]

Package: courier-ssl
Version: 0.73.1-1.6
Severity: normal

Dear Maintainer,

according to the mkdhparams man page:

ENVIRONMENT VARIABLES
   BITS Customize the DH parameter bit size. The
  default value depends on whether this script uses OpenSSL or
  GnuTLS libraries. For OpenSSL the default number of bits is
  768. GnuTLS uses a security level setting, rather than the
  number of bits, and the default security level is "high".

However, if I run

export BITS=2048 # also tried 1024 as the value
rm /etc/courier/dhparms.pem
mkdhparams

I still get a 768 bit key.  Which cause problems because some verions of 
OpenSSL will refuse to deliver mail via SSL/STARTTLS if the the smtp server 
uses a DH key less than 1024.

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

Versions of packages courier-ssl depends on:
ii  courier-base   0.73.1-1.6
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18+deb8u4
ii  libssl1.0.01.0.1t-1+deb8u2
ii  openssl1.0.1t-1+deb8u2

courier-ssl recommends no packages.

courier-ssl suggests no packages.

-- debconf information:
* courier-ssl/certnotice:

Bug#759604: Any problem with making auditd log readable by the adm group?

[Nicolas Braud-Santoni]

Control: tags -1 patch

On Tue, Jun 28, 2016 at 11:06:57AM +0200, Nicolas Braud-Santoni wrote:
> 
> It seems to me we have two issues at play here:
> - auditd violating the adm group convention;
> - apparmor-notify using a suboptimal mechanism to stream auditd logs.
> 
> Could we fix the permissions on /var/log/auditd and open an issue
> upstream for apparmor-notify to use the unix socket plugin, esp.
> since no-one finds the permissions change problematic?

Regarding the first part, I pushed to the packaging repo, in the
nicoo/debian branch, a patch for this issue along with various
other fixes:

  https://anonscm.debian.org/cgit/collab-maint/audit.git/log/?h=nicoo/debian


Best,

  nicoo

Bug#828833: python3-magic: magic file type double encoded

[Christoph Biedl]

Iago wrote...

> The reason i proposed the patch was that the testsuit of Debsources
> (www.sources.debian.net) was reaching the str(r, 'utf-8'). Here's a log
> of the incident https://travis-ci.org/Debian/debsources/builds/102972221

Can you reduce that to a reproducer? Also, travis-ci is down and/or
they are incapable of presenting something as a log file simply as
plain text. In other words: I'd like to understand what went wrong but
cannot even see it. 

Sorry for the inconvenience,

Christoph

Bug#828919: O: omnievents

[W. Martin Borgert]

Package: wnpp
Severity: normal

Neither Thomas nor I do care enough to fix a (probably) trivial build bug.
The package should be maintained by someone else.
If nobody steps in within some weeks, I will file an RM (remove) bug.
Note, that the software has not been updated by upstream since many years.
The upstream source code is maintained in CVS.

Bug#828177: jessie-pu: package unbound/1.4.22-3+deb8u2

[Robert Edmonds]

Julien Cristau wrote:
> May I take the opportunity to ask you to also fix the 'stop' action from
> the init script?
> 
> We've been using this patch on the debian.org hosts for a year now.
> Previously restarting the service would quite often result in no running
> unbound, because (AIUI) systemd doesn't use the init script 'restart'
> action (uses stop && start instead), the 'stop' action would not wait
> for the process to actually die before returning, and then 'start' would
> say "I'm already running, nothing to do".

Wow, thanks for pointing that out. Yes, I'd be happy to fix that one too
in a stable update.

> --- /tmp/unbound-1.4.22/debian/unbound.init 2016-02-22 01:43:22.0 
> +0200
> +++ modules/unbound/files/unbound.init  2015-05-17 16:50:09.699383800 +0200
> @@ -121,7 +121,7 @@
>  stop)
>  if $UNBOUND_ENABLE; then
>  log_daemon_msg "Stopping $DESC" "$NAME"
> -if start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE 
> --name $NAME; then
> +if start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE 
> --name $NAME --retry 5; then
>  do_resolvconf_stop
>  log_end_msg 0
>  else
> 
> Cheers,
> Julien

-- 
Robert Edmonds
edmo...@debian.org

Bug#828872: devscripts: Please drop licensecheck (moved to separate package)

[Jonas Smedegaard]

Quoting Dominique Dumont (2016-06-28 21:23:58)
> On Tuesday 28 June 2016 20:27:54 Jonas Smedegaard wrote:
> > To acknowledge my takeover, please drop licensecheck and its
> > bash-completion + tests from devscripts, and instead recommend/suggest
> > licensecheck.
> 
> As one of the latest contributors to licensecheck, I'm fine with this 
> takeover.
> 
> On my side, I'll change the libconfig-model-dpkg-perl's dependency from 
> devscript to the new package.
> 
> Jonas, please give me a heads-up if you plan to change licensecheck output 
> when used with -m option.

Sure, will do.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#828917: pysph: FTBFS in testing (other math package is already loaded)

[Santiago Vila]

Package: src:pysph
Version: 0~20160514.git91867dc-3
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
make doc
make[2]: Entering directory '/<>'
cd docs; make html
make[3]: Entering directory '/<>/docs'
sphinx-build -b html -d build/doctrees   source build/html
Running Sphinx v1.4.4
making output directory...
WARNING: sphinx.ext.pngmath has been deprecated. Please use sphinx.ext.imgmath 
instead.

Extension error:
sphinx.ext.mathjax: other math package is already loaded
Makefile:45: recipe for target 'html' failed
make[3]: *** [html] Error 1


A full build log is available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/pysph_0~20160514.git91867dc-3.rbuild.log

Thanks.

Bug#828918: php-sabredav: fix autopkgtest failure

[Nishanth Aravamudan]

Package: php-sabredav
Version: 1.8.12-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to fix autopkgtest failures
(which also are occurring with Debian).

- d/p/DEP-8/Use-installed-class-for-DEP-8-tests.patch: fix
  include_path (LP #1568026).

Thanks for considering the patch.

*** /tmp/tmpj8mrZ8/php-sabredav_1.8.12-3ubuntu1.debdiff
diff -Nru 
php-sabredav-1.8.12/debian/patches/DEP-8/Use-installed-class-for-DEP-8-tests.patch
 
php-sabredav-1.8.12/debian/patches/DEP-8/Use-installed-class-for-DEP-8-tests.patch
--- 
php-sabredav-1.8.12/debian/patches/DEP-8/Use-installed-class-for-DEP-8-tests.patch
  2016-05-06 05:29:31.0 -0700
+++ 
php-sabredav-1.8.12/debian/patches/DEP-8/Use-installed-class-for-DEP-8-tests.patch
  2016-06-16 17:53:22.0 -0700
@@ -16,7 +16,7 @@
  define('SABRE_MYSQLPASS','');
  
 -set_include_path(__DIR__ . '/../lib/' . PATH_SEPARATOR . __DIR__ . 
PATH_SEPARATOR . get_include_path());
-+set_include_path(get_include_path() . __DIR__ . '/../lib/' . PATH_SEPARATOR . 
__DIR__ . PATH_SEPARATOR);
++set_include_path(get_include_path() . PATH_SEPARATOR . __DIR__ . '/../lib/' . 
PATH_SEPARATOR . __DIR__ . PATH_SEPARATOR);
  
  include 'Sabre/autoload.php';
  include 'Sabre/TestUtil.php';


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

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

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#809362: Willing to take over

[Tomasz Buchert]

On 29/06/16 00:10, Alexandre Viau wrote:
> Hello Tomasz,
> 
> On 27/06/16 10:57 PM, Tomasz Buchert wrote:
> > I'll be at Debconf, btw, we can work on that together, if you want.
> 
> I would be happy to meet you at DebConf! However I am already done
> packaging and uploading OpenDHT :). It is currently sitting in NEW
> before it can make it to Experimental.

Hi Alexandre,
very nice! Docracy FTW.

> There is a dependency on a version of msgpack that is only available in
> Experimental.

Ah, yes, that was it! :)

> 
> My work can be found here:
>  - https://anonscm.debian.org/cgit/collab-maint/opendht.git
> 
> I had the chance[1] to sit with an OpenDHT developper at DebCamp and
> work with him for the packaging. He even wrote a man page for us:
>  -
> https://github.com/savoirfairelinux/opendht/commit/29834b714eff792d6b2f1164f8db93988026ed84

Upstream that one can only wish for!

> 1. I guess "had the chance" is a bit far fetched because me and Simon
> work in the same building in Montreal :o)

Oh, then I see that it makes much more sense for you to do it.

> 
> Cheers,
> 
> -- 
> Alexandre Viau
> av...@debian.org
> 

Cheers and see you in a few days,
Tomasz


signature.asc
Description: PGP signature

Bug#828032: pax-britannica: port to glfw3

[James Cowgill]

Control: found -1 1.0.0-2
Control: tags -1 pending

On Fri, 24 Jun 2016 07:33:53 +0100 James Cowgill  wrote:
> Source: pax-britannica
> Version: 1.0.0-2
> Severity: important
> Tags: sid stretch patch
> 
> Hi,
> 
> At some point before the stretch release, I'd like to remove glfw2 from
> the archive. The library has been dead upstream since 2013 and has been
> superseded by glfw3.
> 
> I've attached a patch which ports pax-britannica to glfw3. It only
> touches the backend C code, translating called to the old GLFW 2
> bindings API into (roughly) equivalent GLFW 3 calls. I haven't bothered
> porting some APIs which are not used by pax-britannia.

I've uploaded the attached patch fixing this to DELAYED/10. Please tell
me if you want me to cancel it / delay it longer.

Thanks,
Jamesdiff -Nru pax-britannica-1.0.0/debian/changelog pax-britannica-1.0.0/debian/changelog
--- pax-britannica-1.0.0/debian/changelog	2012-09-03 04:26:35.0 +0100
+++ pax-britannica-1.0.0/debian/changelog	2016-06-28 23:04:43.0 +0100
@@ -1,3 +1,11 @@
+pax-britannica (1.0.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Port to glfw 3. (Closes: #828032)
+  * Build-depend directly on GLU which glfw3 does not depend on.
+
+ -- James Cowgill   Tue, 28 Jun 2016 23:02:52 +0100
+
 pax-britannica (1.0.0-2) unstable; urgency=low
 
   * fix desktop entry, closes: #685743.
diff -Nru pax-britannica-1.0.0/debian/control pax-britannica-1.0.0/debian/control
--- pax-britannica-1.0.0/debian/control	2012-08-10 04:41:37.0 +0100
+++ pax-britannica-1.0.0/debian/control	2016-06-24 00:51:33.0 +0100
@@ -2,8 +2,8 @@
 Section: games
 Priority: optional
 Maintainer: Joe Nahmias 
-Build-Depends: debhelper (>= 9.0.0), liblua5.1-0-dev, libglfw-dev,
- libasound2-dev, libxrandr-dev
+Build-Depends: debhelper (>= 9.0.0), liblua5.1-0-dev, libglfw3-dev,
+ libasound2-dev, libxrandr-dev, libglu1-mesa-dev | libglu-dev
 Standards-Version: 3.9.3
 Homepage: http://paxbritannica.henk.ca/
 
diff -Nru pax-britannica-1.0.0/debian/patches/glfw3.patch pax-britannica-1.0.0/debian/patches/glfw3.patch
--- pax-britannica-1.0.0/debian/patches/glfw3.patch	1970-01-01 01:00:00.0 +0100
+++ pax-britannica-1.0.0/debian/patches/glfw3.patch	2016-06-24 02:13:41.0 +0100
@@ -0,0 +1,978 @@
+Description: Port to GLFW3
+ This is a very basic port of the dokidoki-support sub-module to GLFW3. I've
+ left a number of functions which are not used by pax-britannica unimplemented
+ which simplifies the patch. The new versions of some of these functions do not
+ match with the current API. The correct way to do this would probably be a full
+ rewrite of luaglfw.c with a new API, but on the basis that pax-britannica seems
+ to be dead upstream, I think this is acceptable for the time being.
+Author: James Cowgill 
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/dokidoki-support/mixer.c
 b/dokidoki-support/mixer.c
+@@ -455,33 +455,30 @@ do \
+ } while(0)
+ 
+ #include 
+-#include 
++#include 
++#include 
+ 
+ static snd_pcm_t * sound_device = NULL;
+ 
+-static GLFWthread audio_thread = 0;
+-static volatile int running = 0;
+-static GLFWmutex running_mutex = NULL;
++static pthread_t audio_thread;
++static volatile atomic_flag running = ATOMIC_FLAG_INIT;
+ 
+-static GLFWCALL void audio_loop(void *data)
++static void* audio_loop(void *data)
+ {
+ sample_t buffer[BUFFER_SIZE*2];
+ 
+-glfwLockMutex(running_mutex);
+-while(running)
++while(atomic_flag_test_and_set())
+ {
+-glfwUnlockMutex(running_mutex);
+-
+ mix_into(buffer, BUFFER_SIZE);
+ int err = snd_pcm_writei(sound_device, buffer, BUFFER_SIZE);
+ if(err < 0)
+ err = snd_pcm_recover(sound_device, err, 0);
+ 
+-glfwLockMutex(running_mutex);
+ if(err < 0)
+ break;
+ }
+-glfwUnlockMutex(running_mutex);
++
++return NULL;
+ }
+ 
+ static int init()
+@@ -498,20 +495,16 @@ static int init()
+ 
+ ALSA_CHECK(snd_pcm_prepare(sound_device));
+ 
+-CHECK(running_mutex = glfwCreateMutex(),
+-  "audio mutex creation failed");
+-running = 1;
+-audio_thread = glfwCreateThread(audio_loop, NULL);
++atomic_flag_test_and_set();
++CHECK(pthread_create(_thread, NULL, audio_loop, NULL) == 0, "error creating alsa thread");
+ 
+ return 1;
+ }
+ 
+ static int uninit()
+ {
+-glfwLockMutex(running_mutex);
+-running = 0;
+-glfwUnlockMutex(running_mutex);
+-glfwWaitThread(audio_thread, GLFW_WAIT);
++atomic_flag_clear();
++pthread_join(audio_thread, NULL);
+ 
+ ALSA_CHECK(snd_pcm_close(sound_device));
+ sound_device = NULL;
+--- a/dokidoki-support/luaglfw.c
 b/dokidoki-support/luaglfw.c
+@@ -29,9 +29,12 @@
+ //
+ 
+ #include 
+-#include 
++#include 
++#include 
++#include 

Bug#820026: icedove crashes suddenly

[TIMSONET John-Arthur]

Dear Maintainer,

I do too confirm we are having this bug regularly on every Icedove 45. 
Even with the recently updated 1:45.1.0-1~deb8u1.
Icedove randomly crashes during normal use and we can't find a way to 
provoke it for audit.
For some colleagues it happens 4 times a morning and for me it's 1 time 
ever 2 days.


Cheers,


John-Arthur


On Tue, 21 Jun 2016 23:51:53 +0200 Philipp Pilhofer 
 wrote:

> Am 21.06.2016 um 07:49 schrieb Laurent:
> > I have a problem those days with Icedove : when running (writting 
an email, searching in a list or any simple operation), it crashes. This 
never happened before.

> >
>
> I do have the same/a similar issue. It seems to happen since the 
latest icedove update (to
> 45.1.0-1~deb8u1). For me it happens randomly when clicking on any 
mail, about 10 times today. After
> starting icedove again, there's no problem when opening the mail 
clicked on before.

>
> The only installed addon is enigmail (from jessie repo: 1.8.2-4~deb8u1).
>
> I'm using icedove on two other systems in very similar configuration, 
I did not experience crashes

> there so far (but I wasn't using them too much lately).
>
> Using thunderbird/icedove for more than a decade now, never had a 
similar problem so far.

>
>
> Cheers,
> Philipp
>
>
>
>
>

--

John-Arthur TIMSONET
Support informatique ECOLO - etopia_
081/242.366 - helld...@ecolo.be 

Bug#809362: Willing to take over

[Alexandre Viau]

Hello Tomasz,

On 27/06/16 10:57 PM, Tomasz Buchert wrote:
> I'll be at Debconf, btw, we can work on that together, if you want.

I would be happy to meet you at DebConf! However I am already done
packaging and uploading OpenDHT :). It is currently sitting in NEW
before it can make it to Experimental.

There is a dependency on a version of msgpack that is only available in
Experimental.

My work can be found here:
 - https://anonscm.debian.org/cgit/collab-maint/opendht.git

I had the chance[1] to sit with an OpenDHT developper at DebCamp and
work with him for the packaging. He even wrote a man page for us:
 -
https://github.com/savoirfairelinux/opendht/commit/29834b714eff792d6b2f1164f8db93988026ed84

1. I guess "had the chance" is a bit far fetched because me and Simon
work in the same building in Montreal :o)

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#764678: dh-systemd: Please support systemd user services

[Daniel Kahn Gillmor]

On Fri 2014-10-10 03:30:07 -0400, Michael Vogt  wrote:
> It would be very nice if dh-systemd would support systemd user
> units (both for detecting them during build time and to add
> something like "systemctl --global enable my-user-unit" to the
> debian/postinst).
>
> My use case is that the package installs a unit that
> should run at login time for all users. In the past this was 
> done via the upstart session support. 

fwiw, i'd like to see this capability for dh-systemd as well.

One alternative available now is to have the package manually ship a
symlink in /etc/systemd/user/default.target.wants/$PKGNAME.service
(pointing to /usr/lib/systemd/user/$PKGNAME.service, assuming the user
service wants to be installed in default.target), but shipping this
symlink as a config file seems a little bit strange, and wouldn't be
safely undoable by "systemctl --global disable my-user-unit" (it'd just
get re-added on upgrade, i think).

It'd be nice to have something more generalized, which can be safely and
cleanly overridden by both the admin and by individual users.

--dkg


signature.asc
Description: PGP signature

Bug#828914: 3.16.7-ckt25-2+deb8u2 can no longer configure ebtables

[Ben Hutchings]

Control: tag -1 patch

On Tue, 2016-06-28 at 14:31 -0700, Jacob Lundberg wrote:
> Package: src:linux
> Version: 3.16.7-ckt25-2+deb8u2
> Severity: important
> 
> We upgraded linux-image-3.16.0-4-amd64 from 3.16.7-ckt25-2 to 
> 3.16.7-ckt25-2+deb8u2 on some servers today and could no longer use 
> the ebtables utility to configure the kernel's ebtables.
> 
> Start-Date: 2016-06-28  11:35:27
> Commandline: apt-get dist-upgrade
> Upgrade: linux-image-3.16.0-4-amd64:amd64 (3.16.7-ckt25-2, 
> 3.16.7-ckt25-2+deb8u2)
> End-Date: 2016-06-28  11:35:53
> 
> arithon:~# ebtables -t nat -A OUTPUT -p IPv4 --ip-src 10.1.2.3 --ip-proto tcp 
> --ip-sport 8080 -j dnat --to-dst 02:e0:11:22:33:44 --dnat-target ACCEPT
> Unable to update the kernel. Two possible causes:
> 1. Multiple ebtables programs were executing simultaneously. The ebtables
>    userspace tool doesn't by default support multiple ebtables programs 
> running
>    concurrently. The ebtables option --concurrent or a tool like flock can be
>    used to support concurrent scripts that update the ebtables kernel tables.
> 2. The kernel doesn't support a certain ebtables extension, consider
>    recompiling your kernel or insmod the extension.
> .
> 
> Reverting to 3.16.7-ckt25-2 allows ebtables to function once more.
> 
> No log messages appear to be generated when ebtables fails.
> 
> This is somewhat remniscent of netfilter commit 
> ebd3d550701d6a3304e57e356a9418f1a73a998f
> https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.73

Yes, thanks for that.  I thought I had picked all the same netfilter
fixes that went into 3.14.73, but I missed that one.

Ben.

-- 

Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.


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

Bug#828833: python3-magic: magic file type double encoded

[Iago]

Hello,

Thanks for including me in the loop

On Tue, 28 Jun 2016 19:48:08 +0200 Reiner Herrmann 
wrote:
> On Tue, Jun 28, 2016 at 11:42:35AM +0200, Christoph Biedl wrote:
> > Still, even after applying your patch a test script works when
> > using python2.7, and now I'm confused. Since my python knowledge is
> > rather limited, could you please check for both versions, too - and
> > perhaps shed some light on it?
> 
> It looks like upstream just commited the same fix:
> https://github.com/file/file/commit/73e043d2a986234b187a00ed0c8d1f7bf83df372

Well this is going to break the python2 support again :/

I hadn't notice the fix i proposed was breaking python3 support. Wasn't
my intention.

The reason i proposed the patch was that the testsuit of Debsources
(www.sources.debian.net) was reaching the str(r, 'utf-8'). Here's a log
of the incident https://travis-ci.org/Debian/debsources/builds/102972221

It's a pity that they merged this so quickly. unfortunately i don't have
the time before next week to work on a patch that will actually support
both Python version correctly.

Cheers,

Orestis

Bug#828916: kde-telepathy is missing a stop button

[Hans-J. Ullrich]

Package: kde-telepathy
Severity: wishlist

Dear Maintainer,

maybe I am wrong, but I found no option to end kde telepathy, when it is 
started.
When I click on the icon in the taskbar, a lot of options are shown, but I 
found no way, to stop the whole process.

Of course I can stop it by using commands like kill or by tools like ksysguard.

It would be cool, if you could add a stop-button into the GUI.

However, if one exists and I missed it somehow, I will be happy, if you could 
point me to it.

Thank you very much for your help.

Best regards

Hans


-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#826843: Calls to notmuch_database_add_message() after notmuch_database_close() crash

[David Bremner]

David Bremner  writes:

>
> Reading the docs again more carefully, it doesn't actually suggest that
> you can call functions on the database itself, but only documents the
> behaviour on derived objects like messages. I agree the docs could be
> more explicit, and I'll probably apply something like the attached
> upstream.

this doc patch is present in upstream commit 0.22+54-g38f0d44

Bug#828915: dracut: on package setup, complains it cannot copy console-setup-dir/bin

[Matteo Settenvini]

Package: dracut
Version: 044+105-2
Severity: normal

Dear Maintainer,

since several months now (maybe a year?), whenever the trigger for
dracut on package update is fired, I see a couple of times errors like
the following:

cp: cannot overwrite non-directory '/var/tmp/dracut.NWphxq/initramfs/bin' with 
directory '/var/lib/dracut/console-setup-dir/bin

Probably related, at boot I see the following error:

dracut-initqueue[210]: /lib/udev/console-setup: line 3: setupcon: command not 
found

It seems there are some problems in the inclusion of setupcon in the initramfs?

Thanks for any help,
Matteo


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

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

Versions of packages dracut depends on:
ii  dracut-core  044+105-2

dracut recommends no packages.

Versions of packages dracut suggests:
pn  dracut-network  

-- no debconf information

Bug#328498:

[Wandee]

Water

Bug#828913: ITP: install-mimic -- overwrite files and preserve their ownership

[Peter Pentchev]

Package: wnpp
Severity: wishlist
Owner: Peter Pentchev 

* Package name: install-mimic
  Version : 0.1.1
  Upstream Author : Peter Pentchev 
* URL : https://devel.ringlet.net/misc/install-mimic/
* License : BSD-2-clause
  Programming Lang: Perl
  Description : overwrite files and preserve their ownership

The install-mimic utility copies the specified files to the specified
destination (file or directory) similarly to install(1), but it preserves
the ownership and access mode of the destination files.  This is useful when
updating files that have already been installed with locally modified copies
that may be owned by the current user and not by the desired owner of the
destination file (e.g. root).


signature.asc
Description: PGP signature

Bug#828914: 3.16.7-ckt25-2+deb8u2 can no longer configure ebtables

[Jacob Lundberg]

Package: src:linux
Version: 3.16.7-ckt25-2+deb8u2
Severity: important

We upgraded linux-image-3.16.0-4-amd64 from 3.16.7-ckt25-2 to 
3.16.7-ckt25-2+deb8u2 on some servers today and could no longer use 
the ebtables utility to configure the kernel's ebtables.

Start-Date: 2016-06-28  11:35:27
Commandline: apt-get dist-upgrade
Upgrade: linux-image-3.16.0-4-amd64:amd64 (3.16.7-ckt25-2, 
3.16.7-ckt25-2+deb8u2)
End-Date: 2016-06-28  11:35:53

arithon:~# ebtables -t nat -A OUTPUT -p IPv4 --ip-src 10.1.2.3 --ip-proto tcp 
--ip-sport 8080 -j dnat --to-dst 02:e0:11:22:33:44 --dnat-target ACCEPT
Unable to update the kernel. Two possible causes:
1. Multiple ebtables programs were executing simultaneously. The ebtables
   userspace tool doesn't by default support multiple ebtables programs running
   concurrently. The ebtables option --concurrent or a tool like flock can be
   used to support concurrent scripts that update the ebtables kernel tables.
2. The kernel doesn't support a certain ebtables extension, consider
   recompiling your kernel or insmod the extension.
.

Reverting to 3.16.7-ckt25-2 allows ebtables to function once more.

No log messages appear to be generated when ebtables fails.

This is somewhat remniscent of netfilter commit 
ebd3d550701d6a3304e57e356a9418f1a73a998f
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.73

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=7c78f9bb-08fd-4a0c-8ada-d24d7c84c2d8 ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[5.487713] uhci_hcd :00:1d.1: irq 17, io base 0xff60
[5.487748] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[5.487750] usb usb7: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[5.487751] usb usb7: Product: UHCI Host Controller
[5.487752] usb usb7: Manufacturer: Linux 3.16.0-4-amd64 uhci_hcd
[5.487754] usb usb7: SerialNumber: :00:1d.1
[5.487876] hub 7-0:1.0: USB hub found
[5.487881] hub 7-0:1.0: 2 ports detected
[5.488362] uhci_hcd :00:1d.2: UHCI Host Controller
[5.488367] uhci_hcd :00:1d.2: new USB bus registered, assigned bus 
number 8
[5.488372] uhci_hcd :00:1d.2: detected 2 ports
[5.488396] uhci_hcd :00:1d.2: irq 18, io base 0xff40
[5.488432] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[5.488433] usb usb8: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[5.488435] usb usb8: Product: UHCI Host Controller
[5.488436] usb usb8: Manufacturer: Linux 3.16.0-4-amd64 uhci_hcd
[5.488437] usb usb8: SerialNumber: :00:1d.2
[5.488561] hub 8-0:1.0: USB hub found
[5.488566] hub 8-0:1.0: 2 ports detected
[5.520325] PTP clock support registered
[5.547495] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[5.578678] tg3.c:v3.137 (May 11, 2014)
[5.608054] tg3 :05:00.0 eth0: Tigon3 [partno(BCM95761) rev 5761100] 
(PCI Express) MAC address 00:24:e8:40:e8:15
[5.608057] tg3 :05:00.0 eth0: attached PHY is 5761 (10/100/1000Base-T 
Ethernet) (WireSpeed[1], EEE[0])
[5.608058] tg3 :05:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] 
TSOcap[1]
[5.608060] tg3 :05:00.0 eth0: dma_rwctrl[7618] dma_mask[64-bit]
[5.620206] iTCO_vendor_support: vendor-support=0
[5.813409] usb 3-1: new low-speed USB device number 2 using uhci_hcd
[5.876120] input: Dell WMI hotkeys as /devices/virtual/input/input6
[5.884497] ppdev: user-space parallel port driver
[5.959578] kvm: disabled by bios
[5.971186] kvm: disabled by bios
[5.982329] kvm: disabled by bios
[5.990204] usb 3-1: New USB device found, idVendor=046d, idProduct=c01e
[5.990207] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[5.990209] usb 3-1: Product: USB-PS/2 Optical Mouse
[5.990210] usb 3-1: Manufacturer: Logitech
[6.006312] kvm: disabled by bios
[6.037169] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[6.037194] iTCO_wdt: Found a ICH10R TCO device (Version=2, TCOBASE=0x0860)
[6.037301] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[6.101494] usb 3-2: new low-speed USB device number 3 using uhci_hcd
[6.183334] snd_hda_intel :00:1b.0: irq 67 for MSI/MSI-X
[6.284273] usb 3-2: New USB device found, idVendor=413c, idProduct=2003
[6.284278] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[6.284281] usb 3-2: Product: Dell USB Keyboard
[6.284283] usb 3-2: Manufacturer: Dell
[6.544549] hidraw: raw HID events driver (C) Jiri Kosina
[6.695984] sound hdaudioC0D0: autoconfig: line_outs=1 
(0x12/0x0/0x0/0x0/0x0) type:line
[6.695986] sound hdaudioC0D0:speaker_outs=1 

Bug#828833: python3-magic: magic file type double encoded

[Christoph Biedl]

tags 828833 pending
thanks

Reiner Herrmann wrote...

> It looks like upstream just commited the same fix:
> https://github.com/file/file/commit/73e043d2a986234b187a00ed0c8d1f7bf83df372

Great. I'll collect some more stuff that needs attention, shouldn't
take longer than a few days.

Christoph


signature.asc
Description: Digital signature

Bug#828912: keystone: /etc/cron.hourly/keystone doesn't work unless "provider" is uncommented

[Turbo Fredriksson]

Package: keystone
Version: 2:9.0.2-1
Severity: minor

The code say

grep -E '^[ \t]*provider[ \t]*=' /etc/keystone/keystone.conf

but if 'provider' is commented out (as in, "use default value")

#provider = uuid

then this will match nothing, not run the token_flush and the
script will exit with '1', which is an error, and the mailbox
will be 'spammed' with

 run-parts: /etc/cron.hourly/keystone exited with return code 1

Removing the dash in the config file make it work, so the correct
fix for this would (probably) be something like:

- s n i p -
--- /etc/cron.hourly/keystone~  2016-06-21 10:01:26.0 +0100
+++ /etc/cron.hourly/keystone   2016-06-28 22:24:23.180502167 +0100
@@ -4,9 +4,9 @@
 
 if [ -x /usr/bin/keystone-manage ] ; then
# We should only run token_flush if we're using uuid tokens.
-   PROVIDER=$(grep -E '^[ \t]*provider[ \t]*=' /etc/keystone/keystone.conf)
+   PROVIDER=$(grep -E '^[ \t#]*provider[ \t]*=' 
/etc/keystone/keystone.conf)
if [ -n "${PROVIDER}" ] ; then
-   PROVIDER=$(grep -E '^[ \t]*provider[ \t]*=' 
/etc/keystone/keystone.conf | sed -e 's/[ \t]*provider[ \t]*=//' | awk '{print 
$1}')
+   PROVIDER=$(grep -E '^[ \t#]*provider[ \t]*=' 
/etc/keystone/keystone.conf | sed -e 's/[ \t#]*provider[ \t]*=//' | awk '{print 
$1}')
else
PROVIDER=uuid
fi
- s n i p -

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

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

Versions of packages keystone depends on:
ii  adduser 3.114
ii  dbconfig-common 2.0.4
ii  debconf [debconf-2.0]   1.5.59
ii  init-system-helpers 1.35
ii  lsb-base9.20160601
ii  python-keystone 2:9.0.2-1
ii  python-q-text-as-data [q-text-as-data]  1.4.0-1
pn  python:any  
ii  sqlite3 3.13.0-1
ii  ssl-cert1.0.38

keystone recommends no packages.

Versions of packages keystone suggests:
pn  apparmor  

Bug#828911: FTBFS on various architectures when generating the gtk-doc documentation

[Michael Biebl]

Source: tracker
Version: 1.8.0-3
Severity: serious

After applying the change as requested by Pino in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823268
the package FTBFS on various architectures:
https://buildd.debian.org/status/package.php?p=tracker

I suspect gtk-doc is not really safe regarding parallel builds.
This should be investigated or
https://anonscm.debian.org/cgit/collab-maint/tracker.git/commit/?id=5f82b567362c0449f85a8008ba7d1a31735fe93c
reverted.



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

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

-- no debconf information

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

[Karsten Hilbert]

On Mon, Jun 27, 2016 at 11:03:36AM +0200, Sébastien Jodogne wrote:

> > - I would not have guessed that adding --upgrade might have made
> >   a difference to a failure that tells me "stack smashing detected"
> >   at the console :-)
> 
> Just to be sure: Is your issue an immediate crash with "stack smashing 
> detected", or is your issue a failure while executing the "--upgrade"?

Both are (were) issues for me.

I have attempted to solve the upgrade issue by
dropping/re-creating the database in PostgreSQL
because the database did not hold production data.

However, Orthanc-on-PG does not start anymore because the PG
plugin now crashes with "stack smashing detected" so I cannot
verify whether it would properly start with the new empty
database ...

> In the former case, couldn't it be possible that the
> version of some shared library does not match its version of
> the headers, maybe because of an unstable Debian?

That is surely possible. That is why I offered to provide
more information if told how to do so.


> > Would you mind adding a line to the log indicating that
> > --upgrade might be needed when Orthanc detects that situation
> > at startup ?
> 
> This is already the case; Here is a sample log of Orthanc 1.0.0 asking an 
> upgrade with the PostgreSQL plugins 2.0 (notice the line starting with "E"):

I figured that out. It didn't have that line in the log when
I first attempted the upgrade.

Thanks,
Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Bug#828910: ftp.debian.org: tidy and tidy-html5 produce the same binary

[Adam Majer]

Package: ftp.debian.org
Severity: normal

The crux of the problem is tidy-html5 is suppose superseed tidy, and
tidy maintainer prepared new tidy package based on tidy-html5. Then
someone from tidy-html5 upstream uploaded it to archive as source package
without contacting old maintainer. The people that approve the NEW
queue then didn't catch conflicting binaries and accepted the new
package.

So now we have,

  https://packages.debian.org/search?keywords=tidy

I propose that the new package should be removed and old package (tidy)
updated. Or the other way around. But at least one should be removed.

- Adam

Bug#823268: tracker: please enable parallel building

[Michael Biebl]

Hi Pino,

On Mon, 02 May 2016 21:23:16 +0200 Pino Toscano  wrote:
> 
> tracker seems to build fine with multiple build jobs when building.
> Thus, my suggestion is to enable the parallel build (with the
> --parallel option of dh) to speed up the compilation when requested
> (see also Policy §4.9.1).

After enabling parallel building I see several build failures at

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

Could you please look into that? Otherwise I'll have to revert that
change again.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

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

[Chris Lamb]

[FYI, you missed a CC to 828634-submit...@bugs.debian.org]

Hi,

> Could you please give details on how you rebuilt, because I can't
> reproduce it.

Hm. So I can still reproduce. I am just building within a Docker container. 
Nothing "weird" and network is enabled.

> For example, the things you're using to do reproducible
> built, etc.

No special reproducible things were enabled for this build.


Regards,

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

Bug#828909: qtruby: please make the build reproducible

[Reiner Herrmann]

Source: qtruby
Version: 4:4.14.3-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering timestamps umask
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that qtruby could not be built reproducibly.
A tarball generated during build is unsorted, its files have the current
time as timestamps and the permissions vary with the umask.

The attached patch fixes those issues.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/control b/debian/control
index 9fc9321..5b35a07 100644
--- a/debian/control
+++ b/debian/control
@@ -17,7 +17,8 @@ Build-Depends: cmake,
pkg-kde-tools (>= 0.6.8),
ruby,
ruby-dev,
-   smoke-dev-tools (>= 4:4.11)
+   smoke-dev-tools (>= 4:4.11),
+   tar (>= 1.28)
 Build-Conflicts: libqtwebkit-dev
 Standards-Version: 3.9.6
 Homepage: http://projects.kde.org/projects/kde/kdebindings/ruby/qtruby
diff --git a/debian/rules b/debian/rules
index 2e222a0..c16b5f6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,7 +27,7 @@ override_dh_compress:
 
 override_dh_installexamples-arch:
 	dh_installexamples -a
-	tar cvzf $(CURDIR)/debian/ruby-qt4/usr/share/doc/ruby-qt4/examples.tar.gz examples
+	tar cvzf $(CURDIR)/debian/ruby-qt4/usr/share/doc/ruby-qt4/examples.tar.gz examples --clamp-mtime --mtime="@$(SOURCE_DATE_EPOCH)" --sort=name --mode=go=rX,u+rw,a-s --owner=root --group=root --numeric-owner
 
 override_dh_makeshlibs:
 	dh_makeshlibs -V


signature.asc
Description: Digital signature

Bug#828908: apt: destroys "auto" marks when /var is full

[Simon Richter]

Package: apt
Version: 1.0.9.8.3
Severity: normal

Hi,

when /var runs full during installation, apt still tries to write the list
of automatically installed packages, but does so in an unsafe way that
clears the list instead. As a result, all packages are then marked as
manually installed.

I'm not even sure the list needs to be rewritten after dpkg has run, but in
any case it is better to leave the list untouched if it cannot be written
rather than destroy it.

Simon

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/sources.list present, but not submitted) --


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

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

Versions of packages apt depends on:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.18-7+deb8u1
ii  libapt-pkg4.12  1.0.9.8.3
ii  libc6   2.19-18+deb8u4
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.6.11-1+b1
ii  dpkg-dev1.17.27
ii  python-apt  0.9.3.12

-- no debconf information

Bug#828869: [php-maint] Bug#828869: src:php7.0: run tests during build

[Ondřej Surý]

Cool stuff, I was actually preparing to enable the test suite myself.
Nish, you still don't have an alioth account? I could give you direct
access to commit such important stuff. Or you can submit PRs over at the
github mirror: github.com/pkg-php/php

It would be easier for me than to pick it up from the email ;).

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Tue, Jun 28, 2016, at 19:19, Nishanth Aravamudan wrote:
> Package: php7.0
> Version: 7.0.8-2
> Severity: wishlist
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu yakkety ubuntu-patch
> 
> Dear Maintainer,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * Re-enable test suite, thanks to Marc Deslauriers
> 
> - debian/rules, debian/setup-mysql.sh: updated for new MySQL version
>   and new layout.
> 
> Thanks for considering the patch.
> 
> *** /tmp/tmpTBf45P/php7.0_7.0.8-2ubuntu1.debdiff
> diff -Nru php7.0-7.0.8/debian/rules php7.0-7.0.8/debian/rules
> --- php7.0-7.0.8/debian/rules   2016-06-24 04:42:02.0 -0700
> +++ php7.0-7.0.8/debian/rules   2016-06-28 08:54:49.0 -0700
> @@ -90,7 +90,7 @@
>  LIBTOOL_VERSION := $(shell dpkg-query -f'$${Version}' -W libtool)
>  
>  # Disable the test now
> -RUN_TESTS := no
> +RUN_TESTS := yes
>  ifeq (nocheck,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
>$(warning Disabling checks due DEB_BUILD_OPTIONS)
>RUN_TESTS := no
> @@ -101,12 +101,12 @@
>  endif
>  
>  ifeq (yes,$(RUN_TESTS))
> -  MYSQL_PORT ?= $(shell for i in $$(seq 1025 3600 | sort -R); do nc -z
> localhost $$i || { echo $$i; exit; } ; done)
> -  MYSQL_DATA_DIR ?= $(shell readlink -f mysql_db)
> +  MYSQL_PORT := $(shell for i in $$(seq 1025 3600 | sort -R); do nc -z
> localhost $$i || { echo $$i; exit; } ; done)
> +  MYSQL_DATA_DIR := $(shell readlink -f mysql_db)
>ifeq (,$(MYSQL_PORT))
>$(error Could not find available port for mysql server)
>endif
> -  MYSQL_SOCKET ?= $(MYSQL_DATA_DIR)/mysql.sock
> +  MYSQL_SOCKET := $(MYSQL_DATA_DIR)/mysql.sock
>  endif
>  
>  ifeq (linux,$(DEB_HOST_ARCH_OS))
> @@ -343,7 +343,7 @@
>   # start our own mysql server for the tests
>   $(SHELL) -x debian/setup-mysql.sh $(MYSQL_PORT) $(MYSQL_DATA_DIR)
>   extensions=""; \
> -   for f in $(CURDIR)/apache2-build/modules/*.so; do \
> +   for f in $(CURDIR)/ext-build/modules/*.so; do \
>   ext=`basename "$$f"`; \
>   test -d "$(CURDIR)/ext/$${ext%.so}/tests" || continue; \
>   test "$$ext" != "imap.so" || continue; \
> @@ -357,11 +357,15 @@
>   test "$$ext" != "pdo_pgsql.so" || continue; \
>   test "$$ext" != "snmp.so" || continue; \
>   test "$$ext" != "opcache.so" || continue; \
> +   test "$$ext" != "mysqlnd.so" || continue; \
> +   test "$$ext" != "mysqli.so" || continue; \
> +   test "$$ext" != "pdo_mysql.so" || continue; \
> +   test "$$ext" != "wddx.so" || continue; \
>   extensions="$$extensions -d extension=$$ext"; \
>   done; \
>   [ "$$extensions" ] || { echo "extensions list is empty"; exit 1; }; \
> -   env MYSQL_TEST_HOST=127.0.0.1 MYSQL_TEST_PORT=$(MYSQL_PORT)
> MYSQL_TEST_SOCKET=$(MYSQL_SOCKET) PDO_MYSQL_TEST_HOST=127.0.0.1
> PDO_MYSQL_TEST_PORT=$(MYSQL_PORT) PDO_MYSQL_TEST_SOCKET=$(MYSQL_SOCKET)
> NO_INTERACTION=1
> TEST_PHP_CGI_EXECUTABLE=$(CURDIR)/cgi-build/sapi/cgi/cgi-bin.php$(PHP_NAME_VERSION)
> TEST_PHP_EXECUTABLE=$(CURDIR)/cli-build/sapi/cli/php \
> -   $(CURDIR)/cli-build/sapi/cli/php run-tests.php -n -d
> mysql.default_host=127.0.0.1 -d mysql.default_socket=$(MYSQL_SOCKET) -d
> mysqli.default_socket=$(MYSQL_SOCKET) -d
> extension_dir=$(CURDIR)/apache2-build/modules/ $$extensions| tee
> test-results.txt
> +   env MYSQL_TEST_HOST=127.0.0.1 MYSQL_TEST_PORT=$(MYSQL_PORT)
> MYSQL_TEST_SOCKET=$(MYSQL_SOCKET) PDO_MYSQL_TEST_HOST=127.0.0.1
> PDO_MYSQL_TEST_PORT=$(MYSQL_PORT) PDO_MYSQL_TEST_SOCKET=$(MYSQL_SOCKET)
> NO_INTERACTION=1 TEST_PHP_CGI_EXECUTABLE=$(CURDIR)/cgi-build/sapi/php-cgi
> TEST_PHP_EXECUTABLE=$(CURDIR)/cli-build/sapi/cli/php \
> +   $(CURDIR)/cli-build/sapi/cli/php run-tests.php -n -d
> mysql.default_host=127.0.0.1 -d mysql.default_socket=$(MYSQL_SOCKET) -d
> mysqli.default_socket=$(MYSQL_SOCKET) -d
> extension_dir=$(CURDIR)/ext-build/modules/ $$extensions| tee
> test-results.txt
>   rm -rf temp_session_store
>   @for test in `find . -name '*.log' -a '!' -name 'config.log' -a '!' 
> -name 'bootstrap.log' -a '!' -name 'run.log'`; do \
>   echo; \
> diff -Nru php7.0-7.0.8/debian/setup-mysql.sh
> php7.0-7.0.8/debian/setup-mysql.sh
> --- php7.0-7.0.8/debian/setup-mysql.sh  2016-06-24 04:42:02.0
> -0700
> +++ 

Bug#828907: plymouth external firmware error

[Cedric Brandenbourger]

Package: plymouth
Version: 0.9.2-3+b1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

I have to use an external firmware for my GK106 graphic card due to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=93629
This working quite well, but when i install plymouth and change the theme from
"details" to "spinner" i'm getting error when i update initramfs


sudo plymouth-set-default-theme -R spinner
update-initramfs: Generating /boot/initrd.img-4.6.0-1-amd64
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_method_init.bin
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_nonctx.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_ctx.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_sig.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_sig.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_data.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_inst.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_bl.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_unload.bin
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_load.bin for
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/bl.bin for module
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_method

the package firmware-linux-nonfree and firmware-linux-misc are installed.


When i reboot i'm getting the following error message

kernel: [1.968430] nouveau :01:00.0: firmware: failed to load
nvidia/gk106/fecs_inst.bin (-2)
kernel: [1.968434] nouveau :01:00.0: Direct firmware load for
nvidia/gk106/fecs_inst.bin failed with error -2

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

i installed plymouth

   * What was the outcome of this action?

  * What outcome did you expect instead?




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

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

Versions of packages plymouth depends on:
ii  init-system-helpers  1.35
ii  initramfs-tools  0.125
ii  libc62.22-11
ii  libdrm2  2.4.68-1
ii  libplymouth4 0.9.2-3+b1

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base 8.0.2
ii  plymouth-themes  0.9.2-3+b1

-- Configuration Files:
/etc/plymouth/plymouthd.conf changed:
[Daemon]
Theme=details


-- no debconf information

Bug#828906: mailfilter: please make the build reproducible

[Reiner Herrmann]

Source: mailfilter
Version: 0.8.4-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering umask
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that mailfilter could not be built reproducibly.
A tarball generated during build is unsorted and has varying permissions
depending on umask. A Makefile inside also varies with different shells.

The attached patch fixes those issues.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/rules b/debian/rules
index d93b262..44d2fa1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,12 +1,13 @@
 #!/usr/bin/make -f
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
-BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date)
+export CONFIG_SHELL=/bin/bash
 
 %:
 	dh $@ --with autotools-dev
 
 override_dh_auto_install:
 	dh_auto_install
-	LC_ALL=C tar -cf - ./contrib --mtime="$(BUILD_DATE)" | gzip -n -9  > ./debian/mailfilter/usr/share/doc/mailfilter/contrib.tar.gz
+	LC_ALL=C tar -cf - ./contrib --sort=name --clamp-mtime --mtime="@$(SOURCE_DATE_EPOCH)" --mode=go=rX,u+rw,a-s --owner=root --group=root --numeric-owner \
+		   | gzip -n -9  > ./debian/mailfilter/usr/share/doc/mailfilter/contrib.tar.gz
 


signature.asc
Description: Digital signature

Bug#828905: youtube-dl: FTBFS: /bin/sh: 1: zip: not found

[Chris Lamb]

Source: youtube-dl
Version: 2016.06.25-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,

youtube-dl fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  youtube-dl
   Version:  2016.06.25-1
   Build architecture:   amd64
   Date: Tue, 28 Jun 2016 22:29:30 +0200
   Hostname: 0990dc296c77
   Uname:Linux 0990dc296c77 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 'youtube-dl-build-deps' in 
'../youtube-dl-build-deps_2016.06.25-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package youtube-dl-build-deps.
  (Reading database ... 23073 files and directories currently installed.)
  Preparing to unpack youtube-dl-build-deps_2016.06.25-1_all.deb ...
  Unpacking youtube-dl-build-deps (2016.06.25-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up youtube-dl-build-deps (2016.06.25-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=0990dc296c77
  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.20160628222929.OWeCoxWrxz.youtube-dl/youtube-dl-2016.06.25
  OLDPWD=/home/lamby/temp/cdt.20160628222929.OWeCoxWrxz.youtube-dl
  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 youtube-dl 2016.06.25-1 on amd64  
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package youtube-dl
  dpkg-buildpackage: info: source version 2016.06.25-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Rogrio Brito 
   dpkg-source --before-build youtube-dl-2016.06.25
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with python2 --buildsystem=python_distutils
 dh_testdir -O--buildsystem=python_distutils
 dh_auto_clean -O--buildsystem=python_distutils
python setup.py clean -a
  setup.py:73: UserWarning: Skipping file youtube-dl.bash-completion since it 
is not present. Type  make  to build all automatically generated files.
warnings.warn('Skipping file %s since it is not present. Type  make  to 
build all automatically generated files.' % fn)
  setup.py:73: UserWarning: Skipping file youtube-dl.fish since it is not 
present. Type  make  to build all automatically generated files.
warnings.warn('Skipping file %s since it is not present. Type  make  to 
build all automatically generated files.' % fn)
  setup.py:73: UserWarning: Skipping file README.txt since it is not present. 
Type  make  to build all automatically generated files.
warnings.warn('Skipping file %s since it is not present. Type  make  to 
build all automatically generated files.' % fn)
  setup.py:73: UserWarning: 

Bug#828904: FTBFS on GNU/Hurd

[James Clarke]

Package: src:mailutils
Version: 1:2.99.99-1
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
X-Debbugs-CC: debian-h...@lists.debian.org

Hi,
Currently mailutils FTBFS on GNU/Hurd due to missing rpl_strerror when
linking clexer[1]. This is because the configure script detected that
strerror should be replaced[2] (rightly or wrongly), but clexer doesn't
link against libgnu, despite using strerror (and thus needs its
replacement). The attached patch adds the missing dependency, and is
sufficient to make the package build on hurd-i386.

James

[1] 
https://buildd.debian.org/status/fetch.php?pkg=mailutils=hurd-i386=1%3A2.99.99-1=1462345727
[2] See the 's|@''REPLACE_STRERROR''@|1|g' command given to sed in the
log above
--- a/gint/Makefile.am
+++ b/gint/Makefile.am
@@ -28,6 +28,8 @@
 else
 noinst_PROGRAMS = clexer
 clexer_SOURCES = clexer.l
+clexer_DEPENDENCIES = ../lib/gnu/libgnu.la
+clexer_LDADD = ../lib/gnu/libgnu.la
 AM_CPPFLAGS = @GINT_INCLUDES@
 LDADD = @GINT_LDADD@
 endif


signature.asc
Description: PGP signature

Bug#828903: auditd embeds a copy of libev

[Nicolas Braud-Santoni]

Source: audit
Severity: normal


Dear Maintainer,

The audit source package ships a (custom, patched) copy of libev.

Moreover, it is not listed in the security team's list of code copies:


https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?view=markup


I discovered the issue while preparing a DEP5 copyright file for
the audit source package, and more generally fixing all Lintian
warnings while preparing a patch for #759604.


Best,

  nicoo

Bug#828902: utidylib: please update for new tidy-html5

[Gianfranco Costamagna]

Source: utidylib
Severity: serious
Justification: breaks ongoing transition
Tags: patch

Hi,

please update the runtime dependency to the new tidy lib, I hope the binding 
will still work

diff -Nru utidylib-0.2/debian/changelog utidylib-0.2/debian/changelog
--- utidylib-0.2/debian/changelog   2014-02-23 13:54:41.0 +
+++ utidylib-0.2/debian/changelog   2016-06-28 20:18:06.0 +
@@ -1,3 +1,9 @@
+utidylib (0.2-9.1) unstable; urgency=medium
+
+  * Use libtidy5 as runtime dependency.
+
+ -- Gianfranco Costamagna   Tue, 28 Jun 2016 
22:04:19 +0200
+
utidylib (0.2-9build1) trusty; urgency=medium

* Rebuild to drop files installed into /usr/share/pyshared.
diff -Nru utidylib-0.2/debian/control utidylib-0.2/debian/control
--- utidylib-0.2/debian/control 2013-10-31 09:05:33.0 +
+++ utidylib-0.2/debian/control 2016-06-28 20:16:58.0 +
@@ -12,7 +12,7 @@

Package: python-utidylib
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, libtidy-0.99-0 (>= 20051018)
+Depends: ${python:Depends}, ${misc:Depends}, libtidy5
Provides: ${python:Provides}
Breaks: ${python:Breaks}
Description: Python wrapper for TidyLib

I'll NMU/Team upload shortly if this blocks the transition.

thanks!

Gianfranco

Bug#828901: python-websockets: FTBFS: AssertionError: Expected 'get_extra_info' to be called once. Called 2 times.

[Chris Lamb]

Source: python-websockets
Version: 3.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

  creating 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/uri.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/__init__.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/py35_client.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/server.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/test_framing.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/protocol.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/version.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/test_client_server.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/http.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/test_handshake.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/py35_test_client_server.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/compatibility.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/exceptions.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/test_uri.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/client.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/framing.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/test_http.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/test_protocol.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
  copying websockets/handshake.py -> 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build/websockets
 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20160628222159.su8xae1XGK.python-websockets/python-websockets-3.0/.pybuild/pythonX.Y_3.5/build;
 python3.5 -m unittest discover -v 
  test_basic (websockets.test_client_server.ClientServerContextManagerTests) 
... ok
  test_checking_lack_of_origin_succeeds 
(websockets.test_client_server.ClientServerOriginTests) ... ok
  test_checking_origin_fails 
(websockets.test_client_server.ClientServerOriginTests) ... ok
  test_checking_origin_succeeds 
(websockets.test_client_server.ClientServerOriginTests) ... ok
  test_basic (websockets.test_client_server.ClientServerTests) ... ok
  test_client_receives_malformed_response 
(websockets.test_client_server.ClientServerTests) ... ok
  test_client_sends_invalid_handshake_request 
(websockets.test_client_server.ClientServerTests) ... ok
  test_explicit_event_loop (websockets.test_client_server.ClientServerTests) 
... ok
  test_no_subprotocol (websockets.test_client_server.ClientServerTests) ... ok
  test_protocol_attributes (websockets.test_client_server.ClientServerTests) 
... ok
  test_protocol_custom_request_headers_dict 
(websockets.test_client_server.ClientServerTests) ... ok
  test_protocol_custom_request_headers_list 
(websockets.test_client_server.ClientServerTests) ... ok
  test_protocol_custom_response_headers_callable_dict 

Bug#828900: python-tidylib: FTBFS: ! LaTeX Error: File `iftex.sty' not found.

[Chris Lamb]

Source: python-tidylib
Version: 0.2.4~dfsg-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]

  Unpacking texlive-pictures (2016.20160623-1) ...
  Selecting previously unselected package preview-latex-style.
  Preparing to unpack .../preview-latex-style_11.88-1.1_all.deb ...
  Unpacking preview-latex-style (11.88-1.1) ...
  Selecting previously unselected package texlive-latex-extra.
  Preparing to unpack .../texlive-latex-extra_2016.20160623-1_all.deb ...
  Unpacking texlive-latex-extra (2016.20160623-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-13) ...
  Processing triggers for systemd (230-3) ...
  Processing triggers for mime-support (3.60) ...
  Setting up python-all (2.7.11-2) ...
  Setting up python3-all (3.5.1-4) ...
  Setting up python3-six (1.10.0-3) ...
  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 python3-markupsafe (0.23-2+b2) ...
  Setting up python3-jinja2 (2.8-1) ...
  Setting up python-babel-localedata (2.3.4+dfsg.1-2) ...
  Setting up python3-pkg-resources (20.10.1-1.1) ...
  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) ...
  Setting up libtidy-0.99-0 (20091223cvs-1.5) ...
  Setting up ucf (3.0036) ...
  Setting up tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  Setting up libkpathsea6:amd64 (2016.20160513.41080-4) ...
  Setting up libptexenc1:amd64 (2016.20160513.41080-4) ...
  Setting up libsynctex1:amd64 (2016.20160513.41080-4) ...
  Setting up libtexlua52:amd64 (2016.20160513.41080-4) ...
  Setting up libtexluajit2:amd64 (2016.20160513.41080-4) ...
  Setting up libpng16-16:amd64 (1.6.23-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libcups2:amd64 (2.1.4-1) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libtiff5:amd64 (4.0.6-1) ...
  Setting up libijs-0.35:amd64 (0.35-12) ...
  Setting up libjbig2dec0:amd64 (0.13-2) ...
  Setting up liblcms2-2:amd64 (2.7-1) ...
  Setting up libopenjp2-7:amd64 (2.1.0-2.1+b1) ...
  Setting up libpaper1:amd64 (1.1.24+nmu4) ...
  
  Creating config file /etc/papersize with new version
  Setting up poppler-data (0.4.7-7) ...
  Setting up libgs9-common (9.19~dfsg-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.6-2) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.6-2) ...
  Setting up x11-common (1:7.7+15) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libnspr4:amd64 (2:4.12-2) ...
  Setting up libnss3:amd64 (2:3.23-2) ...
  Setting up libpoppler61:amd64 (0.44.0-3) ...
  Setting up libpotrace0 (1.13-2) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libxpm4:amd64 (1:3.5.11-1+b1) ...
  Setting up libxaw7:amd64 (2:1.0.13-1) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up libzzip-0-13:amd64 (0.13.62-3) ...
  Setting up xdg-utils (1.1.1-1) ...
  Setting up libpaper-utils (1.1.24+nmu4) ...
  Setting up preview-latex-style (11.88-1.1) ...
  update-language: texlive-base not installed and configured, doing nothing!
  Regenerating 

Bug#828899: prayer: FTBFS: html_secure_tidy.c:15:20: fatal error: buffio.h: No such file or directory

[Chris Lamb]

Source: prayer
Version: 1.3.5-dfsg1-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,

prayer fails to build from source in unstable/amd64:

  [..]

  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.142 
[80.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 comerr-dev amd64 
2.1-1.43.1-1 [38.5 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libgssrpc4 amd64 
1.14.2+dfsg-1 [88.1 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libkdb5-8 amd64 
1.14.2+dfsg-1 [69.6 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libkadm5srv-mit10 
amd64 1.14.2+dfsg-1 [84.9 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libkadm5clnt-mit10 
amd64 1.14.2+dfsg-1 [70.3 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 krb5-multidev amd64 
1.14.2+dfsg-1 [148 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libpam0g-dev amd64 
1.1.8-3.3 [182 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
1:1.2.8.dfsg-2+b1 [206 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libssl-dev amd64 
1.0.2h-1 [1544 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 mlock amd64 
8:2007f~dfsg-4+b1 [34.4 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libc-client2007e 
amd64 8:2007f~dfsg-4+b1 [606 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libc-client2007e-dev 
amd64 8:2007f~dfsg-4+b1 [528 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 libldap2-dev amd64 
2.4.42+dfsg-2+b2 [326 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 libdb5.3-dev amd64 
5.3.28-11 [741 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 libdb-dev amd64 
5.3.1 [2344 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 libtidy5 amd64 
1:5.2.0-1 [174 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 libtidy-dev amd64 
1:5.2.0-1 [192 kB]
  Fetched 5116 kB in 0s (99.4 MB/s)
  Selecting previously unselected package cdbs.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23077 files and directories currently installed.)
  Preparing to unpack .../archives/cdbs_0.4.142_all.deb ...
  Unpacking cdbs (0.4.142) ...
  Selecting previously unselected package comerr-dev.
  Preparing to unpack .../comerr-dev_2.1-1.43.1-1_amd64.deb ...
  Unpacking comerr-dev (2.1-1.43.1-1) ...
  Selecting previously unselected package libgssrpc4:amd64.
  Preparing to unpack .../libgssrpc4_1.14.2+dfsg-1_amd64.deb ...
  Unpacking libgssrpc4:amd64 (1.14.2+dfsg-1) ...
  Selecting previously unselected package libkdb5-8:amd64.
  Preparing to unpack .../libkdb5-8_1.14.2+dfsg-1_amd64.deb ...
  Unpacking libkdb5-8:amd64 (1.14.2+dfsg-1) ...
  Selecting previously unselected package libkadm5srv-mit10:amd64.
  Preparing to unpack .../libkadm5srv-mit10_1.14.2+dfsg-1_amd64.deb ...
  Unpacking libkadm5srv-mit10:amd64 (1.14.2+dfsg-1) ...
  Selecting previously unselected package libkadm5clnt-mit10:amd64.
  Preparing to unpack .../libkadm5clnt-mit10_1.14.2+dfsg-1_amd64.deb ...
  Unpacking libkadm5clnt-mit10:amd64 (1.14.2+dfsg-1) ...
  Selecting previously unselected package krb5-multidev.
  Preparing to unpack .../krb5-multidev_1.14.2+dfsg-1_amd64.deb ...
  Unpacking krb5-multidev (1.14.2+dfsg-1) ...
  Selecting previously unselected package libpam0g-dev:amd64.
  Preparing to unpack .../libpam0g-dev_1.1.8-3.3_amd64.deb ...
  Unpacking libpam0g-dev:amd64 (1.1.8-3.3) ...
  Selecting previously unselected package zlib1g-dev:amd64.
  Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2+b1_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Selecting previously unselected package libssl-dev:amd64.
  Preparing to unpack .../libssl-dev_1.0.2h-1_amd64.deb ...
  Unpacking libssl-dev:amd64 (1.0.2h-1) ...
  Selecting previously unselected package mlock.
  Preparing to unpack .../mlock_8%3a2007f~dfsg-4+b1_amd64.deb ...
  Unpacking mlock (8:2007f~dfsg-4+b1) ...
  Selecting previously unselected package libc-client2007e.
  Preparing to unpack .../libc-client2007e_8%3a2007f~dfsg-4+b1_amd64.deb ...
  Unpacking libc-client2007e (8:2007f~dfsg-4+b1) ...
  Selecting previously unselected package libc-client2007e-dev.
  Preparing to unpack .../libc-client2007e-dev_8%3a2007f~dfsg-4+b1_amd64.deb ...
  Unpacking 

Bug#828898: lordsawar: please make the build reproducible

[Reiner Herrmann]

Source: lordsawar
Version: 0.3.0-2
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps username umask
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that lordsawar could not be built reproducibly.
The gama data archives, which are just tarballs, have files with the
current time, the build user and varying permissions (depending on
umask).

The attached patch fixes this.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch
new file mode 100644
index 000..7f4bafb
--- /dev/null
+++ b/debian/patches/reproducible-build.patch
@@ -0,0 +1,18 @@
+Author: Reiner Herrmann 
+Description: Make tarball reproducible
+ - sort file order
+ - clamp mtime at $SOURCE_DATE_EPOCH
+ - set owner/group to root
+ - fix permissions
+
+--- a/create-lw-file
 b/create-lw-file
+@@ -13,7 +13,7 @@
+   for f in $files; do
+   tmpfiles="$tmpfiles `basename $f`"
+   done
+-  tar -cvf $tarball $tmpfiles
++  tar -cvf $tarball $tmpfiles --sort=name --clamp-mtime --mtime="@${SOURCE_DATE_EPOCH:-$(date +%s)}" --mode=go=rX,u+rw,a-s --owner=root --group=root --numeric-owner
+   cd $origdir
+   cp -f $tmpdir/$tarball $1
+   rm -f $tmpdir/*
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..55077d0
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+reproducible-build.patch


signature.asc
Description: Digital signature

Bug#734237: btrfs-tools: btrfs lockup with RT kernel

[Nicholas D Steeves]

Hi Osamu,

Is this bug still present in linux-image-4.6.0-1-rt-amd64=4.6.2-2?

Cheers,
Nicholas

Bug#828006: systemd: "quiet" kernel boot parameter overrides LogLevel= in /etc/systemd/system.conf

[Michael Biebl]

Control: tags -1 = patch

Hi Brian,

Am 28.06.2016 um 03:09 schrieb Brian Kroth:
> Hi, I've done a little bit of testing with the patch and it does indeed
> appear to fix the issue.  Here's the resulting diff for the package I
> built.  Let me know if you need anything else.

Thanks for that. This should be sufficient, I guess. I've marked your
bug report as patch available and tagged it so it shows up at [1]
I'll plan to cherry-pick this patch for the next Debian stable release (8.6)

Regards,
Michael
[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintain...@lists.alioth.debian.org;tag=jessie-backport
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#827983: libva1: upgrade to va 1.7.1 breaks intel graphics

[Nicholas D Steeves]

Hi,

For another data point, I've attached the output to the following:
lsb_release -a > graphics-stack.txt && echo >> graphics-stack.txt &&
dpkg -l linux-image-4.4.14.20160627 *drm* xserver-xorg-video-intel
*mesa* libva* i965-va-driver | sed '//d' >> graphics-stack.txt

As Sebastian notes, I also think it's unlikely that the libva
subsystem is exclusively at fault.  Norbert, does your system exhibit
this behaviour if you install libva.*=1.7.1, but use an older version
of i965-va-driver?  To provide more useful debugging info, could you
please install the following: linux-image-4.6.0-1-amd64=4.6.2-2,
xserver-xorg-video-intel-dbg, and i965-va-driver-dbg?

Then boot linux-4.6.2 with drm.debug=0xe.  Please specify which
applications exhibit the corruption.  What compositing window manager
are you using, and what CPU and GPU ?  Also, please attach your "dmesg
> ~/dmesg.log" and "lspci -nn | grep -e "\[03..\]: > ~/gpu.info &&
echo && cat /proc/mtrr >> ~/gpu.info"

What Norbert describes as " * redrawing of applications full of
failures (no redrawing in many cases!)" reminds me of when Kwin is
configured to "Re-use screen content".  Also, a long time ago I had
similar symptoms on my Sandybridge (2000-series i5) Thinkpad.  I
believe it only affected Iceweasel/Firefox, but it was so long ago I'm
not sure...  It might have been caused by an interaction between
kernel version and i965-va-driver version I was using.

Cheers,
Nicholas
Distributor ID: Debian
Description:Debian GNU/Linux 8.5 (jessie)
Release:8.5
Codename:   jessie

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture 
Description
+++--===--==
ii  i965-va-driver:amd64 1.4.1-2 amd64
VAAPI driver for Intel G45 & HD Graphics family
ii  i965-va-driver:i386  1.4.1-2 i386 
VAAPI driver for Intel G45 & HD Graphics family
ii  libdrm-amdgpu1:amd64 2.4.68-1~bpo8+1 amd64
Userspace interface to amdgpu-specific kernel DRM services -- runtime
ii  libdrm-amdgpu1:i386  2.4.68-1~bpo8+1 i386 
Userspace interface to amdgpu-specific kernel DRM services -- runtime
ii  libdrm-dev:amd64 2.4.68-1~bpo8+1 amd64
Userspace interface to kernel DRM services -- development files
ii  libdrm-intel1:amd64  2.4.68-1~bpo8+1 amd64
Userspace interface to intel-specific kernel DRM services -- runtime
ii  libdrm-intel1:i386   2.4.68-1~bpo8+1 i386 
Userspace interface to intel-specific kernel DRM services -- runtime
ii  libdrm-nouveau2:amd642.4.68-1~bpo8+1 amd64
Userspace interface to nouveau-specific kernel DRM services -- runtime
ii  libdrm-nouveau2:i386 2.4.68-1~bpo8+1 i386 
Userspace interface to nouveau-specific kernel DRM services -- runtime
ii  libdrm-radeon1:amd64 2.4.68-1~bpo8+1 amd64
Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm-radeon1:i386  2.4.68-1~bpo8+1 i386 
Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm2:amd642.4.68-1~bpo8+1 amd64
Userspace interface to kernel DRM services -- runtime
ii  libdrm2:i386 2.4.68-1~bpo8+1 i386 
Userspace interface to kernel DRM services -- runtime
ii  libegl1-mesa:amd64   11.1.3-1~bpo8+1 amd64
free implementation of the EGL API -- runtime
ii  libegl1-mesa-dev:amd64   11.1.3-1~bpo8+1 amd64
free implementation of the EGL API -- development files
ii  libegl1-mesa-drivers:amd64   11.1.3-1~bpo8+1 amd64
transitional dummy package
ii  libgl1-mesa-dev:amd6411.1.3-1~bpo8+1 amd64
free implementation of the OpenGL API -- GLX development files
ii  libgl1-mesa-dri:amd6411.1.3-1~bpo8+1 amd64
free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-dri:i386 11.1.3-1~bpo8+1 i386 
free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd6411.1.3-1~bpo8+1 amd64
free implementation of the OpenGL API -- GLX runtime
ii  libgl1-mesa-glx:i386 11.1.3-1~bpo8+1 i386 
free implementation of the OpenGL API -- GLX runtime
ii  libglapi-mesa:amd64  11.1.3-1~bpo8+1 amd64
free implementation of the GL API -- shared 

Bug#828892: apache-directory-api: FTBFS: Could not resolve dependencies for project org.apache.directory.api:api-ldap-model:jar

[Chris Lamb]

Source: apache-directory-api
Version: 1.0.0~M20-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,

apache-directory-api fails to build from source in unstable/amd64:

  [..]

/usr/bin/make -f debian/rules patch-poms; \
  fi
  cd . && /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
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-i18n:jar:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-util:jar:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-asn1-api:jar:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-asn1-ber:jar:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-asn1-parent:pom:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-all:jar:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-ldap-model:jar:1.0.0-M20
  [WARNING] 
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
 must be unique: org.osgi:org.osgi.core:jar -> duplicate declaration of version 
debian @ org.apache.directory.api:api-parent:1.0.0-M20, 
/home/lamby/temp/cdt.20160628210709.ymP6nguDmT.apache-directory-api/apache-directory-api-1.0.0~M20/pom.xml,
 line 283, column 16
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.directory.api:api-ldap-codec-core:jar:1.0.0-M20
  [WARNING] 

Bug#828897: ironic-common: ironic.conf is missing auth_* and admin_* templates

[Turbo Fredriksson]

Package: ironic-common
Version: 1:5.1.2-1
Severity: important

I had to add the following to the [keystone_authtoken] section
to get Ironic to "boot up" (or at least have it respond to queries):

auth_host=
auth_protocol=http
admin_user=
admin_password=
admin_tenant_name=
auth_port=

All other services have this, so I had expected Ironic to have
it as well (and my setup script(s) depend on it existing).

PS. This should probably be setup by the postinst/config, like
it's done in all the other Openstack packages.

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

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

Versions of packages ironic-common depends on:
ii  adduser3.114
ii  dbconfig-common2.0.4
ii  debconf [debconf-2.0]  1.5.59
ii  ipmitool   1.8.17-1
ii  lsb-base   9.20160601
ii  python-ironic  1:5.1.2-1
pn  python:any 
ii  sqlite33.13.0-1
ii  sudo   1.8.15-1.1

ironic-common recommends no packages.

ironic-common suggests no packages.

-- debconf information:
* ironic/admin-password: (password omitted)
* ironic-common/app-password-confirm: (password omitted)
* ironic-common/mysql/app-pass: (password omitted)
* ironic-common/pgsql/app-pass: (password omitted)
* ironic-common/mysql/admin-pass: (password omitted)
* ironic-common/password-confirm: (password omitted)
* ironic-common/pgsql/admin-pass: (password omitted)
* ironic/rabbit_password: (password omitted)
* ironic/admin-password-confirm: (password omitted)
* ironic-common/dbconfig-remove: true
* ironic-common/db/app-user: ironic
  ironic-common/db/basepath:
* ironic-common/remote/port:
* ironic-common/remote/host: controller
  ironic-common/pgsql/no-empty-passwords:
  ironic-common/pgsql/authmethod-user: password
* ironic-common/mysql/method: TCP/IP
* ironic-common/dbconfig-reinstall: true
* ironic-common/purge: true
  ironic-common/pgsql/admin-user: postgres
* ironic-common/mysql/admin-user: root
* ironic/admin-tenant-name: service
* ironic/admin-user: ironic
* ironic/rabbit_host: controller
  ironic-common/passwords-do-not-match:
  ironic-common/pgsql/changeconf: false
  ironic-common/pgsql/authmethod-admin: ident
  ironic-common/pgsql/method: TCP/IP
* ironic/enabled_drivers: pxe_ipmitool, pxe_ipminative, pxe_ssh, pxe_seamicro, 
pxe_iboot, pxe_ilo, pxe_drac, pxe_snmp
* ironic-common/internal/reconfiguring: false
* ironic-common/dbconfig-install: true
* ironic-common/dbconfig-upgrade: true
* ironic/configure_db: true
* ironic/rabbit_userid: openstack
* ironic/auth-host: 10.0.4.1
* ironic-common/upgrade-error: abort
* ironic-common/db/dbname: ironic
* ironic-common/database-type: mysql
* ironic-common/missing-db-package-error: abort
* ironic-common/install-error: abort
* ironic-common/remove-error: abort
* ironic-common/remote/newhost: controller
* ironic-common/upgrade-backup: true
  ironic-common/pgsql/manualconf:
* ironic-common/internal/skip-preseed: true

Bug#828890: libsdl2-gfx: please make the build reproducible

[Gianfranco Costamagna]

control: tags -1 pending

>While working on the "reproducible builds" effort [1], we have noticed
>that libsdl2-gfx could not be built reproducibly.>The example tarball still 
>has time and order variations.
>
>The attached patch fixes this by telling tar to sort the file list and
>clamp the mtime at SOURCE_DATE_EPOCH.



*thanks* :)
uploaded with some other changes!
thanks again for the great help!

Gianfranco

Bug#828895: jless: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: jless
Version: 382-iso262-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,

jless fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  jless
   Version:  382-iso262-3
   Build architecture:   amd64
   Date: Tue, 28 Jun 2016 21:27:47 +0200
   Hostname: 9c4a8f99e799
   Uname:Linux 9c4a8f99e799 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 'jless-build-deps' in 
'../jless-build-deps_382-iso262-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 jless-build-deps.
  (Reading database ... 23073 files and directories currently installed.)
  Preparing to unpack jless-build-deps_382-iso262-3_all.deb ...
  Unpacking jless-build-deps (382-iso262-3) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
cdbs dpatch libncurses5-dev libtinfo-dev
  Suggested packages:
curl ncurses-doc
  The following NEW packages will be installed:
cdbs dpatch libncurses5-dev libtinfo-dev
  0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 421 kB of archives.
  After this operation, 1932 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.142 
[80.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 dpatch all 2.0.38 
[89.6 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160319-2+b1 [77.1 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libncurses5-dev amd64 
6.0+20160319-2+b1 [174 kB]
  Fetched 421 kB in 0s (2885 kB/s)
  Selecting previously unselected package cdbs.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23077 files and directories currently installed.)
  Preparing to unpack .../archives/cdbs_0.4.142_all.deb ...
  Unpacking cdbs (0.4.142) ...
  Selecting previously unselected package dpatch.
  Preparing to unpack .../archives/dpatch_2.0.38_all.deb ...
  Unpacking dpatch (2.0.38) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../libtinfo-dev_6.0+20160319-2+b1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160319-2+b1) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack .../libncurses5-dev_6.0+20160319-2+b1_amd64.deb ...
  Unpacking libncurses5-dev:amd64 (6.0+20160319-2+b1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up cdbs (0.4.142) ...
  Setting up dpatch (2.0.38) ...
  Setting up libtinfo-dev:amd64 (6.0+20160319-2+b1) ...
  Setting up libncurses5-dev:amd64 (6.0+20160319-2+b1) ...
  Setting up jless-build-deps (382-iso262-3) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=9c4a8f99e799
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  

Bug#828896: libopenraw: FTBFS: dh_strip: debug package libopenrawgnome1v5-dbg is not listed in the control file

[Chris Lamb]

Source: libopenraw
Version: 0.0.9-3.9
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,

libopenraw fails to build from source in unstable/amd64:

  [..]

 ^
  pixbufload.c:71:4: warning: 'gdk_pixbuf_unref' is deprecated: Use 
'g_object_unref' instead [-Wdeprecated-declarations]
  gdk_pixbuf_unref(pixbuf);
  ^
  In file included from 
/usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:33:0,
   from ../gnome/include/libopenraw-gnome/gdkpixbuf.h:30,
   from pixbufload.c:27:
  /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:228:12: note: 
declared here
   void   gdk_pixbuf_unref(GdkPixbuf *pixbuf);
  ^
  /bin/bash ../libtool --tag=CC --mode=link /bin/bash ../shave cc gcc -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wextra -pedantic -g 
-Wall -L../gnome -static -Wl,-z,relro -Wl,-z,defs -o pixbufload pixbufload.o 
../gnome/libopenrawgnome.la -lstdc++ -ljpeg -lgdk_pixbuf-2.0 -lgobject-2.0 
-lglib-2.0 --shave-mode=link
  libtool: link: /bin/bash ../shave cc gcc -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wextra -pedantic -g -Wall -Wl,-z -Wl,relro 
-Wl,-z -Wl,defs -o pixbufload pixbufload.o --shave-mode=link  -L../gnome 
../gnome/.libs/libopenrawgnome.a 
/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib/.libs/libopenraw.a
 -lstdc++ -ljpeg -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra 
-pedantic -g -Wall -Wl,-z -Wl,relro -Wl,-z -Wl,defs -o pixbufload pixbufload.o 
-L../gnome ../gnome/.libs/libopenrawgnome.a 
/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib/.libs/libopenraw.a
 -lstdc++ -ljpeg -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/demo'
  Making all in tools
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/tools'
  g++ -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra -ansi 
-pedantic -g -Wall -Wshadow -c -o ordiag.o ordiag.cpp
  /bin/bash ../libtool --tag=CXX --mode=link /bin/bash ../shave cxx g++ -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wextra -ansi 
-pedantic -g -Wall -Wshadow -L../lib -static -Wl,-z,relro -Wl,-z,defs -o ordiag 
ordiag.o ../lib/libopenraw.la -lstdc++ -ljpeg --shave-mode=link
  libtool: link: /bin/bash ../shave cxx g++ -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wextra -ansi -pedantic -g -Wall -Wshadow 
-Wl,-z -Wl,relro -Wl,-z -Wl,defs -o ordiag ordiag.o --shave-mode=link  -L../lib 
../lib/.libs/libopenraw.a -lstdc++ -ljpeg
  g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wextra 
-ansi -pedantic -g -Wall -Wshadow -Wl,-z -Wl,relro -Wl,-z -Wl,defs -o ordiag 
ordiag.o -L../lib ../lib/.libs/libopenraw.a -lstdc++ -ljpeg
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/tools'
  Making all in include
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/include'
  Making all in libopenraw
  Making all in libopenraw++
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/include'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
 dh_auto_test
make -j1 check VERBOSE=1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9'
  Making check in lib
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib'
  Making check in io
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib/io'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160628213359.kMg2569Uvt.libopenraw/libopenraw-0.0.9/lib/io'
  g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include -I./.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wextra -ansi -pedantic -g -Wall -Wshadow -c -o 
teststream.o teststream.cpp
  /bin/bash ../../libtool --tag=CXX --mode=link /bin/bash ../../shave cxx g++ 
-g -O2 -fstack-protector-strong -Wformat 

Bug#828893: epic4-help: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Chris Lamb]

Source: epic4-help
Version: 1:2.0+20050315-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

epic4-help fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  epic4-help
   Version:  2.0+20050315-2
   Build architecture:   amd64
   Date: Tue, 28 Jun 2016 21:18:40 +0200
   Hostname: ef3d6f3c38d0
   Uname:Linux ef3d6f3c38d0 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 'epic4-help-build-deps' in 
'../epic4-help-build-deps_2.0+20050315-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package epic4-help-build-deps.
  (Reading database ... 23073 files and directories currently installed.)
  Preparing to unpack epic4-help-build-deps_2.0+20050315-2_all.deb ...
  Unpacking epic4-help-build-deps (1:2.0+20050315-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up epic4-help-build-deps (1:2.0+20050315-2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=ef3d6f3c38d0
  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.20160628211838.BnS7CqtsWh.epic4-help/epic4-help-2.0+20050315
  OLDPWD=/home/lamby/temp/cdt.20160628211838.BnS7CqtsWh.epic4-help
  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 epic4-help 2.0+20050315-2 on amd64
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package epic4-help
  dpkg-buildpackage: info: source version 1:2.0+20050315-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Kurt Roeckx 
   dpkg-source --before-build epic4-help-2.0+20050315
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  rm -f build
  rm -rf debian/epic4-help debian/files* core debian/substvars
   debian/rules build
  dh_testdir
  touch build
   fakeroot debian/rules binary
  dh_testdir
  dh_testroot
  dh_clean
  dh_clean: Please specify the compatibility level in debian/compat
  debian/rules:18: recipe for target 'binary-indep' failed
  make: *** [binary-indep] Error 2

  [..]

The full build log is attached.


Regards,

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


epic4-help.1:2.0+20050315-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#828894: gdb-avr: FTBFS: dh_movefiles: debian/tmp/usr/share/man/ not found (supposed to put it in gdb-avr)

[Chris Lamb]

Source: gdb-avr
Version: 7.7-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gdb-avr fails to build from source in unstable/amd64:

  [..]

  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/libiberty/testsuite'
  if test -n ""; then \
/bin/bash ../../src/libiberty/../mkinstalldirs 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib/`gcc
 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-print-multi-os-directory`; \
/usr/bin/install -c -m 644 ./libiberty.a 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib/`gcc
 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-print-multi-os-directory`/./libiberty.an; \
( cd 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib/`gcc
 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-print-multi-os-directory` ; chmod 644 ./libiberty.an ;x86_64-linux-gnu-ranlib 
./libiberty.an ); \
mv -f 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib/`gcc
 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-print-multi-os-directory`/./libiberty.an 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib/`gcc
 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-print-multi-os-directory`/./libiberty.a; \
case "" in \
  /*)thd=;; \
  *) 
thd=/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/include/;;
 \
esac; \
/bin/bash ../../src/libiberty/../mkinstalldirs ${thd}; \
for h in ../../src/libiberty/../include/ansidecl.h 
../../src/libiberty/../include/demangle.h 
../../src/libiberty/../include/dyn-string.h 
../../src/libiberty/../include/fibheap.h 
../../src/libiberty/../include/floatformat.h 
../../src/libiberty/../include/hashtab.h 
../../src/libiberty/../include/libiberty.h 
../../src/libiberty/../include/objalloc.h 
../../src/libiberty/../include/partition.h 
../../src/libiberty/../include/safe-ctype.h 
../../src/libiberty/../include/sort.h 
../../src/libiberty/../include/splay-tree.h 
../../src/libiberty/../include/timeval-utils.h; do \
  /usr/bin/install -c -m 644 $h ${thd}; \
done; \
  fi
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/libiberty/testsuite'
  make[4]: Nothing to be done for 'install'.
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/libiberty/testsuite'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/libiberty'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/readline'
  make[3]: Nothing to be done for 'install'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/readline'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/sim'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/sim/avr'
  /bin/bash ../../../src/sim/avr/../../mkinstalldirs 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/bin
  mkdir -p -- 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/bin
  /bin/bash ../../../src/sim/avr/../../mkinstalldirs 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib
  mkdir -p -- 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib
  n=`echo run | sed 's&^&'`; \
  /usr/bin/install -c run 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/bin/$n
  n=`echo libsim.a | sed s/libsim.a/libavr-sim.a/`; \
  /usr/bin/install -c -m 644 libsim.a 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib/$n
 ; \
  ( cd 
/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/debian/tmp/usr/lib
 ; x86_64-linux-gnu-ranlib $n )
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/sim/avr'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/sim/testsuite'
  make[4]: Nothing to be done for 'install'.
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/sim/testsuite'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160628212030.O5sbdZpmuG.gdb-avr/gdb-avr-7.7/build/sim'
  make[3]: Entering directory 

Bug#828535: ruby2.3: FTBFS with openssl 1.1.0

[Antonio Terceiro]

Control: forwarded -1 https://bugs.ruby-lang.org/issues/12324

On Sun, Jun 26, 2016 at 12:24:00PM +0200, Kurt Roeckx wrote:
> Source: ruby2.3
> Version: 2.3.1-1
> Severity: important
> Control: block 827061 by -1
> 
> Hi,
> 
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/ruby2.3_2.3.1-1_amd64-20160529-1533
> 
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of 
> the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful 
> information.
> 
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
> 
> If you have problems making things work, feel free to contact us.

upstream already has support for OpenSSL 1.1.0 in trunk for Ruby 2.4;
see upstream bug linked above. given the current state of afairs, we
will need to either backport that for Ruby 2.3 ourselves, or disable the
openssl extension bundled with the interpreter and use a standalone
ruby-openssl package.


signature.asc
Description: PGP signature

Bug#828846: kmail: After upgrading kmail this morning it looked empty. All mail folders removed from mailserver

[Tom Zander]

Quite unexpected, another cause showed itself. The email provider
had done something to loose all folders and it took responsibility
when I asked if they made backups (they did).

So this bug can be closed. Apologies for blaming the innocent!


On 2016-06-28 15:29, Tom Zander wrote:

Package: kmail
Version: 4:4.14.10-2
Severity: important

Dear Maintainer,

I've done an aptitude upgrade this morning which meant I received the
newest kmail.
I don't think there was an akonodi upgrade in there.
Afterwards I started kontact and in my kmail view I no longer saw my 
imap /

kolab folders.
My todos was also empty and my calendar from caldav (owncloud) was not
showing in the calendar app.

Some time later I rebooted my laptop and logged back in.
I noticed that still everything was missing, but the account was still
present in the overview of kmail configure screen.

Just now I logged into mykolab.com via webmail only to find out that
everything except my inbox is gone. All folders have been removed.

I can only blame this on kontact/kmail somehow.  Although I don't know
what happened.

I hope this report can somehow avoid others losing all the emails too.


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IM.UTF-8, LC_CTYPE=en_IM.UTF-8 (charmap=locale: Cannot
set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or 
directory

locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmail depends on:
ii  kde-runtime   4:16.04.2-1
ii  kdepim-runtime4:4.14.10-2
ii  kdepimlibs-kio-plugins4:4.14.10-3
ii  libakonadi-calendar4  4:4.14.10-3
ii  libakonadi-contact4   4:4.14.10-3
ii  libakonadi-kde4   4:4.14.10-3
ii  libakonadi-kmime4 4:4.14.10-3
ii  libakonadiprotocolinternals1  1.13.0-8
ii  libc6 2.22-11
ii  libcalendarsupport4   4:4.14.10-2
ii  libfollowupreminder4  4:4.14.10-2
ii  libgcc1   1:6.1.1-7
ii  libgpgme++2v5 4:4.14.10-3
ii  libgrantlee-core0 0.4.0-3
ii  libincidenceeditorsng44:4.14.10-2
ii  libkabc4  4:4.14.10-3
ii  libkalarmcal2 4:4.14.10-3
ii  libkcalcore4  4:4.14.10-3
ii  libkcalutils4 4:4.14.10-3
ii  libkcmutils4  4:4.14.21-1
ii  libkdecore5   4:4.14.21-1
ii  libkdepim44:4.14.10-2
ii  libkdeui5 4:4.14.21-1
ii  libkio5   4:4.14.21-1
ii  libkleo4  4:4.14.10-2
ii  libkmanagesieve4  4:4.14.10-2
ii  libkmime4 4:4.14.10-3
ii  libknotifyconfig4 4:4.14.21-1
ii  libkontactinterface4a 4:4.14.10-3
ii  libkparts44:4.14.21-1
ii  libkpimidentities44:4.14.10-3
ii  libkpimtextedit4  4:4.14.10-3
ii  libkpimutils4 4:4.14.10-3
ii  libkprintutils4   4:4.14.21-1
ii  libksieveui4  4:4.14.10-2
ii  libmailcommon44:4.14.10-2
ii  libmailimporter4  4:4.14.10-2
ii  libmailtransport4 4:4.14.10-3
ii  libmessagecomposer4   4:4.14.10-2
ii  libmessagecore4   4:4.14.10-2
ii  libmessagelist4   4:4.14.10-2
ii  libmessageviewer4 4:4.14.10-2
ii  libpimcommon4 4:4.14.10-2
ii  libqt4-dbus   4:4.8.7+dfsg-8
ii  libqt4-network4:4.8.7+dfsg-8
ii  libqt4-xml4:4.8.7+dfsg-8
ii  libqtcore44:4.8.7+dfsg-8
ii  libqtgui4 4:4.8.7+dfsg-8
ii  libqtwebkit4  2.3.4.dfsg-8
ii  libsendlater4 4:4.14.10-2
ii  libsolid4 4:4.14.21-1
ii  libstdc++66.1.1-7
ii  libtemplateparser44:4.14.10-2
ii  perl  5.22.2-1

Versions of packages kmail recommends:
ii  gnupg-agent 2.1.11-7
ii  gnupg2  2.1.11-7
ii  kdepim-doc  4:4.14.10-2
pn  kdepim-themeditors  
ii  ktnef   4:4.14.10-2
ii  pinentry-qt [pinentry-x11]  0.9.7-5
ii  pinentry-qt40.9.7-5

Versions of packages kmail suggests:
pn  clamav
ii  kaddressbook  4:4.14.10-2
ii  kleopatra 4:4.14.10-2
pn  procmail  
ii  spamassassin  3.4.1-4

-- debconf information excluded

Bug#828889: RFS: elisp-slime-nav-el/0.9-1 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "elisp-slime-nav-el"

* Package name: elisp-slime-nav-el
  Version : 0.9-1
  Upstream Author : Steve Purcell 
* Url : https://github.com/purcell/elisp-slime-nav
* Licenses: GPL-3+
  Section : lisp

It builds those binary packages:

elpa-elisp-slime-nav -- Emacs extension that provide Emacs Lisp code 
navigation

To access futher information about this package, visit the following URL:

http://mentors.debian.net/package/elisp-slime-nav-el

Alternatively, one can download the package with dget using this command:


http://mentors.debian.net/debian/pool/main/e/elisp-slime-nav-el/elisp-slime-nav-el_0.9-1.dsc

Alternatively, you can access package debian/ directory via git from URL:

https://anonscm.debian.org/git/pkg-emacsen/pkg/elisp-slime-nav.git

More information about elisp-slime-nav-el can be obtained from 
https://github.com/purcell/elisp-slime-nav

Changes since last upload:

  * Initial release (Closes: #828885)

Regards,
  Dmitry Bogatov

Bug#828890: libsdl2-gfx: please make the build reproducible

[Reiner Herrmann]

Source: libsdl2-gfx
Version: 1.0.1+dfsg-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that libsdl2-gfx could not be built reproducibly.
The example tarball still has time and order variations.

The attached patch fixes this by telling tar to sort the file list and
clamp the mtime at SOURCE_DATE_EPOCH.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/control b/debian/control
index 2e710d7..1a0beeb 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Build-Depends: autoconf,
dh-autoreconf,
libsdl2-dev,
libtool,
+   tar (>= 1.28),
pkg-config
 Build-Depends-Indep: doxygen
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-sdl/packages/libsdl2-gfx.git
diff --git a/debian/rules b/debian/rules
index f6272fe..b4f2b2a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -31,7 +31,7 @@ override_dh_install:
 
 override_dh_auto_build:
 	dh_auto_build
-	tar -cvz --transform='s,^test,examples,' -f debian/examples.tar.gz --mode=go=rX,u+rw,a-s --owner=root --group=root --numeric-owner test
+	tar -cvz --transform='s,^test,examples,' -f debian/examples.tar.gz --clamp-mtime --mtime="@$(SOURCE_DATE_EPOCH)" --sort=name --mode=go=rX,u+rw,a-s --owner=root --group=root --numeric-owner test
 
 override_dh_auto_build-indep:
 	doxygen Docs/html.doxyfile


signature.asc
Description: Digital signature

Bug#828634: Cannot reproduce

[Thomas Goirand]

Hi,

I just tried building python-oauth2client, and it worked without any
problem. I tried in a plain sid, and another time with sbuild in a clean
chroot.

Could you please give details on how you rebuilt, because I can't
reproduce it. For example, the things you're using to do reproducible
built, etc.

I'm downgrading this bug severity therefore, until I know further.
Hopefully, we'll find out what's going on.

Cheers,

Thomas Goirand (zigo)

Bug#828891: bbdb: please make the build reproducible

[Reiner Herrmann]

Source: bbdb
Version: 2.36-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering timestamps username
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that bbdb could not be built reproducibly.
An included tarball contains files with the current build date, the
build user/group and is unsorted.

The attached patch fixes this.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/control b/debian/control
index 1968d30..87967e6 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Uploaders: Barak A. Pearlmutter 
 Build-Depends: debhelper (>= 9),
 dh-autoreconf
 Build-Depends-Indep: texinfo, texi2html, ghostscript,
-texlive-base, texlive-latex-base,
+texlive-base, texlive-latex-base, tar (>= 1.28),
 emacs24-nox | emacs24 | emacs23-nox | emacs23 | emacs
 Standards-Version: 3.9.5
 Vcs-Git: git://github.com/barak/BBDB.git
diff --git a/debian/rules b/debian/rules
index 1407bdb..86119c5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,4 +23,4 @@ override_dh_install:
 
 bits.tar.gz:
 	tar -cf - extern/*/* | tar -C bits -xvf -
-	tar -czf bits.tar.gz bits/
+	tar -czf bits.tar.gz bits/ --sort=name --clamp-mtime --mtime="@${SOURCE_DATE_EPOCH}" --mode=go=rX,u+rw,a-s --owner=root --group=root --numeric-owner


signature.asc
Description: Digital signature

Bug#827716: Non-maintainer upload to fix RC bugs

[Ludovic Rousseau]

Le 28/06/2016 à 20:55, Ondřej Surý a écrit :

It was not in the d/control, so I pushed imported package to 
collab-maint/tidy-html5.

I'll import my and LoB patches on top of tidy.git and push it tomorrow.


OK.
Daniel James already closed some of the bugs in 
https://anonscm.debian.org/cgit/collab-maint/tidy.git/
Your merge may not be easy.

I already asked [1] Daniel to do the merge. Since there is no urgency now I 
propose to let Daniel integrate your changes.

Bye

[1] https://github.com/htacg/tidy-html5/issues/354#issuecomment-229114742

--
Dr. Ludovic Rousseau

Bug#828838: [git-buildpackage/master] import_orig: Recover from import errors

[Guido Günther]

tag 828838 pending
thanks

Date:   Tue Jun 28 17:03:33 2016 +0200
Author: Guido Günther 
Commit ID: ebc6b918ff885fa206910afb81dd5b49b9bb69b0
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage/;a=commitdiff;h=ebc6b918ff885fa206910afb81dd5b49b9bb69b0
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage/;a=commitdiff_plain;h=ebc6b918ff885fa206910afb81dd5b49b9bb69b0

import_orig: Recover from import errors

by winding back branches and tags to their pre-error states

Closes: #828838

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/
  

Bug#828630: jessie-pu: package libbusiness-creditcard-perl/0.33-1+deb8u1

[Adam D. Barratt]

On Tue, 2016-06-28 at 11:26 -0700, Ivan Kohler wrote:
> On Sun, Jun 26, 2016 at 06:18:55PM +0200, gregor herrmann wrote:
> > On Sun, 26 Jun 2016 17:00:36 +0100, Adam D. Barratt wrote:
> > 
> > > On Sun, 2016-06-26 at 15:10 +0200, gregor herrmann wrote:
> > > > I've prepared an update for libbusiness-creditcard-perl in
> > > > jessie{,-updates} which fixes #814479 for stable users. The issue at
> > > > hand is that the credit card ranges of several providers need to be
> > > > updated.
> > > That bug report says "[t]he most important change in this release is
> > > recognition of new MasterCard ranges which will be issued starting in
> > > October 2016". Given that (I'd really hope that) the next point release
> > > will be well before October, are any of the other changes sufficiently
> > > urgent to need a -updates release?
[...]
> I do have concerns that we are "really hoping" a point release will be 
> in a specific timeframe.  I'm not saying that it won't be or anything 
> bad about the release folks - I'm just concerned about _relying_ on such 
> a thing.

I sense things may have got slightly lost in translation there - the
"really hope" wasn't an suggestion that it wouldn't have happened, more
that if it hasn't happened well before then, then something has gone
quite wrong.

In practical terms, given that the 8.5 point release was early this
month, 8.6 should be some time during August.

Regards,

Adam

Bug#828888: aspell-en: please make the build reproducible

[Reiner Herrmann]

Source: aspell-en
Version: 2016.01.19-0-0.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that aspell-en could not be built reproducibly.
Files and file contents are sorted differently depending on the locale.

The attached patch fixes this by setting LC_ALL (instead of LC_COLLATE)
to C.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/rules b/debian/rules
index 67ac205..9bc3191 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,7 +12,7 @@ DEB_DH_MD5SUMS_ARGS += -Xvar/lib/aspell
 makebuilddir/aspell-en:: extrawords-stamp
 
 extrawords-stamp:
-	mv en-common.cwl en-common.cwl.orig && (prezip-bin -d < en-common.cwl.orig ; cat debian/extrawords.txt) | LC_COLLATE=C sort -u | prezip-bin -z > en-common.cwl
+	mv en-common.cwl en-common.cwl.orig && (prezip-bin -d < en-common.cwl.orig ; cat debian/extrawords.txt) | LC_ALL=C sort -u | prezip-bin -z > en-common.cwl
 	touch extrawords-stamp
 
 cleanbuilddir/aspell-en::
@@ -20,7 +20,7 @@ cleanbuilddir/aspell-en::
 	rm -f extrawords-stamp
 
 install/aspell-$(DICT_LANG)::
-	for f in *.cwl; do \
+	for f in `LC_ALL=C ls *.cwl`; do \
 	gzip -9 -n -c "$$f" > "$(DEB_DESTDIR)/usr/share/aspell/"$$f".gz"; \
 	WL=`echo $$f | sed 's/\.cwl$$//'`; \
 	touch "$(DEB_DESTDIR)/var/lib/aspell/$$WL.rws"; \

Bug#828887: gnu-efi headers for ARM don't work for non-EFI applications

[Ben Hutchings]

Package: gnu-efi
Version: 3.0.3-2
Tags: upstream patch

- Forwarded message from Ard Biesheuvel  -

Date: Tue, 28 Jun 2016 17:17:57 +0200
From: Ard Biesheuvel 
To: nigel.cro...@hpe.com, leif.lindh...@linaro.org, b...@decadent.org.uk
Cc: Ard Biesheuvel 
Subject: [PATCH] ARM: hide 'hidden' pragma for hosted build
Message-Id: <1467127077-31859-1-git-send-email-ard.biesheu...@linaro.org>
X-Mailer: git-send-email 2.7.4

The hidden visibility #pragma in inc/arm/efibind.h was meant to inform
the compiler that symbols with external linkage are never exported from
shared libraries [and thus never preempted] when executing in UEFI context
(since UEFI does not support shared libraries). This allows the compiler to
generate relative symbol references instead of GOT entries, which is much more
efficient since the latter need to be relocated before invoking the entry
point of the UEFI app.

However, as it turns out, this pragma is leaking into other code that does
not run in UEFI context, but simply needs to access data structures that
UEFI defines. So make the pragma dependent on whether we are building with
-ffreestanding, which is only used for bare metal code such as UEFI.

Signed-off-by: Ard Biesheuvel 
---
 inc/arm/efibind.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/inc/arm/efibind.h b/inc/arm/efibind.h
index 0978079b0f89..4609d116ffa0 100644
--- a/inc/arm/efibind.h
+++ b/inc/arm/efibind.h
@@ -36,7 +36,7 @@ typedef signed char int8_t;   // unqualified 'char' 
is unsigned on ARM
  * This prevents GCC from emitting GOT based relocations, and use R_ARM_REL32
  * relative relocations instead, which are more suitable for static binaries.
  */
-#ifdef __GNUC__
+#if defined(__GNUC__) && !__STDC_HOSTED__
 #pragma GCC visibility push (hidden)
 #endif
 
-- 
2.7.4


- End forwarded message -

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.


signature.asc
Description: Digital signature