date:20161207

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

> unmerge 846708 846671
Unknown command or malformed arguments to command.
> reassign 846708 fastqc
Bug #846708 [htsjdk] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Bug #846671 [htsjdk] artemis: FTBFS: BamView.java:115: error: cannot find symbol
Bug reassigned from package 'htsjdk' to 'fastqc'.
Bug reassigned from package 'htsjdk' to 'fastqc'.
Ignoring request to alter found versions of bug #846708 to the same values 
previously set
Ignoring request to alter found versions of bug #846671 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846708 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846671 to the same values 
previously set
> reassign 846671 artemis
Bug #846671 [fastqc] artemis: FTBFS: BamView.java:115: error: cannot find symbol
Bug #846708 [fastqc] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Bug reassigned from package 'fastqc' to 'artemis'.
Bug reassigned from package 'fastqc' to 'artemis'.
Ignoring request to alter found versions of bug #846671 to the same values 
previously set
Ignoring request to alter found versions of bug #846708 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846671 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846708 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#847353: [Pkg-javascript-devel] help with node-grunt-contrib-requirejs

2016-12-07 Thread Pirate Praveen

[adding debian-ruby and #847353]

On വ്യാഴം 08 ഡിസംബര്‍ 2016 10:34 രാവിലെ, Pirate Praveen wrote:
> I think you are only checking for jquery-ui.js and not all the other files 
> like jquery-ui/widgets/datepicker.js
> 
> I did not see any error in gitlab when using the embedded copy of jquery-ui 
> in ruby-jquery-ui-rails (removed .links and installed app directory). So it 
> has to be a bug in the build system.

I just found the root cause, ruby-jquery-ui-rails adds dependency
mapping at the top in addition to embedding the corresponding jquery-ui
files. There is a rake task to generate these files if we symlink
pkg-javascript/jqueryui directory to ruby-jquery-ui-rails/jquery-ui. I
think if we create node-jquery-ui package and add it as a build
dependency of ruby-jquery-ui-rails and symlink /usr/lib/nodejs/jquery-ui
to ruby-jquery-ui-rails/jquery-ui this will solve the problem.

ruby-jquery-ui-rails$ diff -u
app/assets/javascripts/jquery-ui/widgets/draggable.js
/usr/share/javascript/jquery-ui/ui/widgets/draggable.js
--- app/assets/javascripts/jquery-ui/widgets/draggable.js   2016-12-07
11:27:13.193475539 +0530
+++ /usr/share/javascript/jquery-ui/ui/widgets/draggable.js 2016-09-14
22:01:37.0 +0530
@@ -1,12 +1,3 @@
-//= require jquery-ui/widgets/mouse
-//= require jquery-ui/data
-//= require jquery-ui/plugin
-//= require jquery-ui/safe-active-element
-//= require jquery-ui/safe-blur
-//= require jquery-ui/scroll-parent
-//= require jquery-ui/version
-//= require jquery-ui/widget
-
 /*!
  * jQuery UI Draggable 1.12.1
  * http://jqueryui.com





signature.asc
Description: OpenPGP digital signature

Bug#794438: [Pkg-kde-extras] Bug#794438: Partition manager does not launch

2016-12-07 Thread Scott Kitterman

On Thursday, December 08, 2016 11:18:35 AM Boyuan Yang wrote:
> Hello,
> 
> Ping everyone,
> 
> Partition Manager will miss Stretch if we do not solve this problem
> (#794438), which would be a great pity.
> 
> Anyone would like to work on this issue and solve the problem? Maybe we can
> port the new version from Ubuntu to greatly reduce the efforts.

I'm willing to sponsor partition manager if someone has a well put together, 
tested package.

Scott K

Bug#847325: Unable to copy symlinks with copy_file

2016-12-07 Thread Vincent Bernat

 ❦  8 décembre 2016 02:08 GMT, Ben Hutchings  :

> (Annoyingly, I couldn't reproduce this at first because I tried just
> adding nouveau to /etc/initramfs-tools/modules.  Since mkinitramfs does
> *not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was
> not fatal.)

I should have said that I got the error through plymouth hook.
-- 
Civilization is the limitless multiplication of unnecessary necessities.
-- Mark Twain


signature.asc
Description: PGP signature

Bug#847369: Error: Cannot find module 'requirejs' (missing package.json)

2016-12-07 Thread Pirate Praveen

On വ്യാഴം 08 ഡിസംബര്‍ 2016 01:18 രാവിലെ, László Böszörményi (GCS) wrote:
>  Package is upadted and this is fixed.

Thanks for the quick update. Can you check the test failure of
grunt-contrib-requirejs? (same git repo, you need to run quilt push
before running grunt) Full error message here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847367#14

>> Also consider using pkg-javascript alioth repo for this package (there
>> is a repo there, but it is outdated), so we can fix these kind of issues
>> faster.
>  Thanks, will consider it. I try to act fast, package is going to be
> uploaded soon.

It helps when you are away or busy as other team members can take care
of the package. But its your choice, just mentioned it.

signature.asc
Description: OpenPGP digital signature

Bug#846671: [Debian-med-packaging] Bug#846671: Artemis should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))]

2016-12-07 Thread olivier sallou

Le jeu. 8 déc. 2016 01:04, Sascha Steinbiss  a
écrit :

> Hi Andreas and Andrew,
>
> to address this problem I have taken a shot at patching Debian’s Artemis
> to use the new htsjdk API, avoiding SAMFileReader and using the
> SamReaderFactory instead. This fixed the FTBFS for me.
> I tested BAM file reading by opening MAL1.embl.gz from the test/data
> directory and adding MAL1_8h.bam via ‘File->Read BAM/VCF...'. One of the
> genes has some mapped reads that are indeed shown. Comparing the displayed
> pile of mapped reads to the one shown by the recent Artemis version I have
> on Mac OS X, the result seems to be correct, but given my lack of practical
> experience with the BAM/VCF/‘anything-to-do-with-reads' components of
> Artemis I can’t say if I caught everything.
>
If you compile and can view the bam, i would consider the api call is
correct and so your patch

Olivier




> I also updated the Debian version to 16.0.17, the latest release from
> Sanger. This allowed me to drop a couple of patches that I already merged
> earlier with my part-time-upstream hat on.
> For now I have pushed my work into the ’6_0_17’ branch in git and I would
> like to kindly ask for some more testing. I don’t have suitable test data
> here and don’t really feel like an expert to test the right usage patterns.
>
> Cheers
> Sascha
>
> > On 5 Dec 2016, at 15:56, Andrew Page  wrote:
> >
> > Hi Andreas,
> > Thanks for letting us know.  We are actively trying to hire a Java
> developer who will take over the maintenance and development of Artemis. So
> unfortunately it will be at least a few months before we will have anyone
> in post to work on it.  If you happen to know of anyone looking for a job,
> please send them our way!
> > Regards,
> > Andrew
> >
> >
> >
> >> On 5 Dec 2016, at 14:40, Andreas Tille  wrote:
> >>
> >> Hi,
> >>
> >> after uploading htsjdk 2.7.0 Artemis failed to build from source[1].  I
> >> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
> >> was removed from htsjdk source and assumed that this was by accident.
> >> However, upstream has dropped this interface intentionally as you can
> >> read below.  In issue #767[2] an htsjdk author gives advise to use the
> >> new API version.
> >>
> >> Kind regards
> >>
> >>  Andreas.
> >>
> >>
> >> [1] https://bugs.debian.org/846671
> >> [2] https://github.com/samtools/htsjdk/issues/767
> >>
> >>
> >> - Forwarded message from Daniel Gómez-Sánchez <
> notificati...@github.com> -
> >>
> >> Date: Mon, 05 Dec 2016 06:18:16 -0800
> >> From: Daniel Gómez-Sánchez 
> >> To: samtools/htsjdk 
> >> Cc: Andreas Tille , Author  >
> >> Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0
> (#767)
> >>
> >> The file was removed in #699 because it was deprecated. I guess that
> either 1) fastqc/artemis should be updated to use the new API version, or
> 2) the classpath for them in Debian should include an older version.
> >>
> >> --
> >> You are receiving this because you authored the thread.
> >> Reply to this email directly or view it on GitHub:
> >> https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
> >>
> >> - End forwarded message -
> >>
> >> --
> >> http://fam-tille.de
> >>
> >> - End forwarded message -
> >>
> >> --
> >> http://fam-tille.de
> >
> >
> >
> > --
> > The Wellcome Trust Sanger Institute is operated by Genome Research
> > Limited, a charity registered in England with number 1021457 and a
> > company registered in England with number 2742969, whose registered
> > office is 215 Euston Road, London, NW1 2BE.
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>
>

Processed: Also fix tags, severity and title

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

> tags 846019 =
Bug #846019 [pgadmin3] pgadmin3: SIGABRT after fatal error complaint regarding 
libwxgtx ABI mismatch
Removed tag(s) patch.
> severity 846019 serious
Bug #846019 [pgadmin3] pgadmin3: SIGABRT after fatal error complaint regarding 
libwxgtx ABI mismatch
Severity set to 'serious' from 'minor'
> retitle 846019 pgadmin3: SIGABRT during startup
Bug #846019 [pgadmin3] pgadmin3: SIGABRT after fatal error complaint regarding 
libwxgtx ABI mismatch
Changed Bug title to 'pgadmin3: SIGABRT during startup' from 'pgadmin3: SIGABRT 
after fatal error complaint regarding libwxgtx ABI mismatch'.
> thanks
Stopping processing here.

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

Bug#844121: marked as done (maradns: CVE-2016-9300 CVE-2016-9301 CVE-2016-9302)

Your message dated Thu, 8 Dec 2016 06:20:06 +0100
with message-id <20161208052006.ga21...@lorien.valinor.li>
and subject line Re: Bug#844121: CVE-2016-9300, CVE-2016-9301, and 
CVE-2016-9302 are *NOT* valid bug reports
has caused the Debian Bug report #844121,
regarding maradns: CVE-2016-9300 CVE-2016-9301 CVE-2016-9302
to be marked as done.

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

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


-- 
844121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maradns
Severity: grave
Version: 2.0.13-1.2
Tags: security upstream 

Hi,

The following vulnerability was published for MaraDNS:
http://seclists.org/oss-sec/2016/q4/411

No CVE is was assigned yet, but the request was made in that thread.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry, if it is 
assigned soon.

Please adjust the affected versions in the BTS as needed.

Regards,luciano
--- End Message ---
--- Begin Message ---
tags 844121 + wontfix
notfound 844121 2.0.13-1.2
thanks

Hi all

In meanwhile the CVEs were properly rejected by MITRE. I'm closing
this bugreport now.

Regards,
Salvatore--- End Message ---

Processed: Re: Bug#844121: CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are NOT valid bug reports

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

> tags 844121 + wontfix
Bug #844121 [src:maradns] maradns: CVE-2016-9300 CVE-2016-9301 CVE-2016-9302
Added tag(s) wontfix.
> notfound 844121 2.0.13-1.2
Bug #844121 [src:maradns] maradns: CVE-2016-9300 CVE-2016-9301 CVE-2016-9302
No longer marked as found in versions maradns/2.0.13-1.2.
> thanks
Stopping processing here.

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

Bug#844121: CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are NOT valid bug reports

2016-12-07 Thread Salvatore Bonaccorso

tags 844121 + wontfix
notfound 844121 2.0.13-1.2
thanks

Hi all

In meanwhile the CVEs were properly rejected by MITRE. I'm closing
this bugreport now.

Regards,
Salvatore

Bug#846918: interface opens, but no menus and no action on button clicks

2016-12-07 Thread tony mancill

On Wed, Dec 07, 2016 at 10:55:38AM +0100, gregor herrmann wrote:
> On Wed, 07 Dec 2016 09:49:32 +0100, Martin Lutz wrote:
> 
> > Package: jabref
> > Version: 2.10+ds-7
> > Followup-For: Bug #846918
> > 
> > Dear Maintainer,
> > 
> > after an update yesterday, jabref fails to start.
> > ERROR while starting or running JabRef: java.lang.NoSuchFieldError: DIALOG
> > 
> > Searching through the debian bug list, I find bug 846503 with a similar 
> > problem.
> 
> Yup, there seem to be some runtime incompatibilitites with the new
> libjgoodies-*, which were not caught at buildtime. Cf. also the
> thread starting at
> https://lists.debian.org/debian-java/2016/12/msg00010.html
> 
> Probably we'll try with rebuilding the affected packages; for JabRef
> the good news is that we're working on updating to 3.6 which doesn't
> have these problems (but needs some wrinkles ironed out before we can
> upload it).

I attempted a binary rebuild of 2.10+ds using the libraries found in sid
and it didn't change the behavior.  It appears that it might be an issue
with the version of jgoodies-looks (2.7.0) available in Debian.  I will
dig into this more, since it could be affecting other users of
jgoodies-looks similarly, but at the moment, I'm trying to get an
updated JabRef version into the archive before stretch freezes.

Currently we're working on JabRef 3.6, but due to some excellent
assistance from upstream (thanks Oliver!), it could also be 3.7.

Cheers,
tony

signature.asc
Description: PGP signature

Processed: Re: Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

Processing control commands:

> severity -1 normal
Bug #847420 [gitlab] gitlab fails to start (shows only 502) after upgrade of 
ruby-grape-entity
Severity set to 'normal' from 'grave'

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

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

2016-12-07 Thread Pirate Praveen

Control: severity -1 normal

On 2016, ഡിസംബർ 8 8:42:57 AM IST, Johannes Schauer  wrote:
>
>When I now enter my gitlab instance I only get a 502 error with the
>message "Whoops, GitLab is taking too much time to respond".
>
>Since the last time I changed the version of a ruby package you told me
>to run assets:precompile, I ran the following command:
>
>runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat
>/etc/gitlab/gitlab-debian.conf) && rake assets:precompile
>RAILS_ENV=production'
>Could not find grape-entity-0.5.1 in any of the sources
>Run `bundle install` to install missing gems.
>
>Given the error above, I suspect that the new ruby-grape-entity version
>is the culprit here.

I think its just the old Gemfile.lock expecting the older version. We should 
truncate Gemfile.lock in postinst.

>Thanks!
>
>cheers, josch

Bug#844751: marked as done (zulucrypt: build-depends on no longer available libqtkeychain0)

Your message dated Thu, 08 Dec 2016 03:33:42 +
with message-id 
and subject line Bug#844751: fixed in zulucrypt 4.9.0-3
has caused the Debian Bug report #844751,
regarding zulucrypt: build-depends on no longer available libqtkeychain0
to be marked as done.

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

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


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

zulucrypt build-depends on no longer available libqtkeychain0.

Why does it build-depend on that package, in addition to
build-depending on qtkeychain-dev?
--- End Message ---
--- Begin Message ---
Source: zulucrypt
Source-Version: 4.9.0-3

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

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

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

Debian distribution maintenance software
pp.
Marcio de Souza Oliveira  (supplier of updated zulucrypt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Dec 2016 00:08:27 +
Source: zulucrypt
Binary: zulucrypt-cli zulumount-cli zulucrypt-gui zulumount-gui zulusafe-cli 
libzulucrypt-exe1.2.0 libzulucrypt-exe-dev libzulucrypt1.2.0 libzulucrypt-dev 
libzulucryptpluginmanager1.0.0 libzulucryptpluginmanager-dev 
libzulucrypt-plugins
Architecture: source amd64
Version: 4.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Marcio de Souza Oliveira 
Changed-By: Marcio de Souza Oliveira 
Description:
 libzulucrypt-dev - development files for libzulucrypt-1.2.0
 libzulucrypt-exe-dev - development files for the libzulucrypt-exe
 libzulucrypt-exe1.2.0 - provide the main functions of zulucrypt
 libzulucrypt-plugins - collection of plugins for zulucrypt
 libzulucrypt1.2.0 - provide the functions of zulumount
 libzulucryptpluginmanager-dev - development files for libzulucryptpluginmanager
 libzulucryptpluginmanager1.0.0 - provides support for plugins
 zulucrypt-cli - tool for encrypting volumes
 zulucrypt-gui - graphical front end for zulucrypt-cli
 zulumount-cli - tool that manages encrypted volumes
 zulumount-gui - graphical front end for zulumount-cli
 zulusafe-cli - cli that manages encrypted volumes
Closes: 844751
Changes:
 zulucrypt (4.9.0-3) unstable; urgency=medium
 .
   * debian/control:
   - Removed the build-depend libqtkeychain0. Thanks Adrian Bunk.
 (Closes: #844751)
   * debian/patches:
   - Updated patch fix_spelling.
Checksums-Sha1:
 6028761e432e5ee33d5cdf50d3995c5a04c34cbc 2847 zulucrypt_4.9.0-3.dsc
 5525c12432d2afa477bb07a988ede6ca3fc3e727 15128 zulucrypt_4.9.0-3.debian.tar.xz
 93bd1e3b0d50fa3aee4c5b87ce2bc8e8981d77b4 14482 
libzulucrypt-dev_4.9.0-3_amd64.deb
 b44601b1a0a060c267d3960afb3d0e543d7e1dce 11474 
libzulucrypt-exe-dev_4.9.0-3_amd64.deb
 1f077d2fd29d4f4715c39eb3227b08d08d439751 95346 
libzulucrypt-exe1.2.0-dbgsym_4.9.0-3_amd64.deb
 7107b1ec1372249b09c454195a54558881007c37 41376 
libzulucrypt-exe1.2.0_4.9.0-3_amd64.deb
 f9cdefa7574c952033e7f3c965489bb5ac3450e2 13649478 
libzulucrypt-plugins-dbgsym_4.9.0-3_amd64.deb
 758cfe5ce875472303492396c059e8aea7a5d62e 228456 
libzulucrypt-plugins_4.9.0-3_amd64.deb
 12bacdb3e7d088576233665a07c192c522099e4f 204182 
libzulucrypt1.2.0-dbgsym_4.9.0-3_amd64.deb
 4a66a12bdb80db9d0f2099baa2c5bc12800d4138 80408 
libzulucrypt1.2.0_4.9.0-3_amd64.deb
 9697252c7197a3ec9d1d97482d635a9beae7e5ba 10942 
libzulucryptpluginmanager-dev_4.9.0-3_amd64.deb
 0914ab1664356d93fa160489adb5edc1541002f3 48228 
libzulucryptpluginmanager1.0.0-dbgsym_4.9.0-3_amd64.deb
 cca6749e548907dec680c2038c1be57d361015cf 28492 
libzulucryptpluginmanager1.0.0_4.9.0-3_amd64.deb
 66fd9ac87ffad7dd02229df7843049f2f098d8be 15854 
zulucrypt-cli-dbgsym_4.9.0-3_amd64.deb
 164301264247266a53d28f42622f78e240755e9e 18890 zulucrypt-cli_4.9.0-3_amd64.deb
 31c8cae15554f9a964211709fb256b6a69048f3d 7224768 
zulucrypt-gui-dbgsym_4.9.0-3_amd64.deb
 28f34a0c875cbf786d1a5aeafc0b652b70077e6a 373682 zulucrypt-gui_4.9.0-3_amd64.deb

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

2016-12-07 Thread Johannes Schauer

Hi,

On Thu, 08 Dec 2016 04:12:57 +0100 Johannes Schauer  wrote:
> When I now enter my gitlab instance I only get a 502 error with the message
> "Whoops, GitLab is taking too much time to respond".
> 
> Since the last time I changed the version of a ruby package you told me
> to run assets:precompile, I ran the following command:
> 
> runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat 
> /etc/gitlab/gitlab-debian.conf) && rake assets:precompile 
> RAILS_ENV=production'
> Could not find grape-entity-0.5.1 in any of the sources
> Run `bundle install` to install missing gems.
> 
> Given the error above, I suspect that the new ruby-grape-entity version
> is the culprit here.

in the hopes that the gitlab postinst maintainer script would contain something
that fixes this problem, I ran "apt-get install --reinstall gitlab" with the
following result:

Verifying we have all required libraries...
Could not find gem 'grape-entity (~> 0.5.0)' in any of the gem sources listed in
your Gemfile or available on this machine.
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 7
Processing triggers for systemd (232-7) ...
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#794438: Partition manager does not launch

2016-12-07 Thread Boyuan Yang

Hello,

Ping everyone,

Partition Manager will miss Stretch if we do not solve this problem (#794438), 
which would be a great pity.

Anyone would like to work on this issue and solve the problem? Maybe we can 
port the new version from Ubuntu to greatly reduce the efforts.

--
Sincerely,
Boyuan Yang

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

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

2016-12-07 Thread Johannes Schauer

Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable

Hi,

sorry for reporting another RC bug.

Because you were so quick in fixing #846916, I just upgraded my gitlab
chroot. Here are the relevant lines from my "apt-get upgrade" run
(showing all the package versions):

The following packages will be upgraded:
  bundler libjs-jquery-ui libruby2.3 libsqlite3-0 libsystemd0 libudev1 
libustr-1.0-1 msmtp msmtp-mta ruby-bundler ruby-grape-entity ruby-molinillo 
ruby-rubypants ruby-temple ruby-thor ruby2.3 systemd systemd-sysv
18 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7535 kB of archives.
After this operation, 169 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 systemd amd64 
232-7 [2452 kB]
Get:2 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libsystemd0 
amd64 232-7 [273 kB]
Get:3 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 systemd-sysv 
amd64 232-7 [74.6 kB]
Get:4 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libudev1 amd64 
232-7 [118 kB]
Get:5 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libustr-1.0-1 
amd64 1.0.4-6 [76.3 kB]
Get:6 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libsqlite3-0 
amd64 3.15.2-1 [568 kB]
Get:7 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-molinillo 
all 0.5.0-2 [15.1 kB]
Get:8 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-thor all 
0.19.1-3 [46.5 kB]
Get:9 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 bundler all 
1.12.5-4 [35.5 kB]
Get:10 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-bundler 
all 1.12.5-4 [160 kB]
Get:11 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 
libjs-jquery-ui all 1.12.1+dfsg-2 [227 kB]
Get:12 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 
ruby-grape-entity all 0.6.0-1 [24.5 kB]
Get:13 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 
ruby-rubypants all 0.6.0-1 [9232 B]
Get:14 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-temple 
all 0.7.7-1 [29.7 kB]
Get:15 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libruby2.3 
amd64 2.3.3-1 [3104 kB]
Get:16 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 msmtp amd64 
1.6.6-1 [120 kB]
Get:17 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 msmtp-mta all 
1.6.6-1 [15.2 kB]
Get:18 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby2.3 amd64 
2.3.3-1 [186 kB]


When I now enter my gitlab instance I only get a 502 error with the
message "Whoops, GitLab is taking too much time to respond".

Since the last time I changed the version of a ruby package you told me
to run assets:precompile, I ran the following command:

runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat 
/etc/gitlab/gitlab-debian.conf) && rake assets:precompile RAILS_ENV=production'
Could not find grape-entity-0.5.1 in any of the sources
Run `bundle install` to install missing gems.

Given the error above, I suspect that the new ruby-grape-entity version
is the culprit here.

Thanks!

cheers, josch

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

2016-12-07 Thread Ben Hutchings

On Thu, 2016-12-08 at 15:34 +1300, Ben Caradoc-Davies wrote:
> On 08/12/16 15:21, Ben Hutchings wrote:
> > Doesn't apt-listbugs see bugs that 'affect' a package?
> 
> I do not know. Does "affects" provide the version information that 
> apt-listbugs needs to filter bugs?

I don't think there's any way to specify which versions of the affected
package are affected.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



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

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed


On 08/12/16 15:21, Ben Hutchings wrote:

Doesn't apt-listbugs see bugs that 'affect' a package?


I do not know. Does "affects" provide the version information that 
apt-listbugs needs to filter bugs?



(2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
0.125)" which it will need even after #847340 is fixed.

I won't add that Breaks line because:
- Only the combination of the new firmware-misc-nonfree *and* plymouth
  breaks with the unfixed initramfs-tools
- jessie and jessie-backports will never have a version of initramfs-
  tools that satisfies that
- jessie can get a fix for this in a stable update


Yes, that sounds fine to me. The Breaks: I wrote is too broad and this 
will all come out in the wash on unstable.



I agree we need to stop this version of firmware-nonfree going into
testing before initramfs-tools is fixed, so I'm assigning this bug
back.


Thanks very much.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: Re: Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

Processing control commands:

> unmerge -1
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Disconnected #847343 from all other report(s).
> reassign -1 firmware-misc-nonfree 20161130-1
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Bug reassigned from package 'initramfs-tools-core' to 'firmware-misc-nonfree'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #847343 to the same values 
previously set
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Marked as found in versions firmware-nonfree/20161130-1.

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

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

2016-12-07 Thread Ben Hutchings

Control: unmerge -1
Control: reassign -1 firmware-misc-nonfree 20161130-1

On Thu, 2016-12-08 at 14:33 +1300, Ben Caradoc-Davies wrote:
> Ben,
> 
> you reassigned this bug to initramfs-tools and removed the version. As 
> detailed in #847343, I wanted to keep this bug on firmware-misc-nonfree 
> because:
> 
> (1) it protects apt-listbugs users from upgrading firmware-misc-nonfree 
> and being hit by #847340, and

Doesn't apt-listbugs see bugs that 'affect' a package?

> (2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
> 0.125)" which it will need even after #847340 is fixed.

I won't add that Breaks line because:
- Only the combination of the new firmware-misc-nonfree *and* plymouth
  breaks with the unfixed initramfs-tools
- jessie and jessie-backports will never have a version of initramfs-
  tools that satisfies that
- jessie can get a fix for this in a stable update

> If you are sure that you want this bug on initramfs-tools, I will defer 
> to your expertise, but I do not see how this addresses my points above.

I agree we need to stop this version of firmware-nonfree going into
testing before initramfs-tools is fixed, so I'm assigning this bug
back.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


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

Processed: severity of 847325 is serious

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

> severity 847325 serious
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: reassign 847340 to initramfs-tools-core, reassign 847343 to initramfs-tools-core ..., affects 847325 ...

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

> reassign 847340 initramfs-tools-core
Bug #847340 [initramfs-tools] initramfs-tools: fails to copy DRM modules with 
plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug reassigned from package 'initramfs-tools' to 'initramfs-tools-core'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #847340 to the same values 
previously set
> reassign 847343 initramfs-tools-core
Bug #847343 [initramfs-tools] firmware-misc-nonfree: breaks update-initramfs 
(initramfs-tools <= 0.125) if plymouth installed
Bug reassigned from package 'initramfs-tools' to 'initramfs-tools-core'.
Ignoring request to alter found versions of bug #847343 to the same values 
previously set
Ignoring request to alter fixed versions of bug #847343 to the same values 
previously set
> forcemerge 847325 847340 847343
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Severity set to 'normal' from 'serious'
Marked as found in versions initramfs-tools/0.125.
Added tag(s) patch.
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Severity set to 'normal' from 'important'
Marked as found in versions initramfs-tools/0.125.
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Added tag(s) patch.
Merged 847325 847340 847343
> affects 847325 firmware-misc-nonfree
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Added indication that 847325 affects firmware-misc-nonfree
Added indication that 847340 affects firmware-misc-nonfree
Added indication that 847343 affects firmware-misc-nonfree
> affects 847325 plymouth
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Added indication that 847325 affects plymouth
Added indication that 847340 affects plymouth
Added indication that 847343 affects plymouth
> thanks
Stopping processing here.

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

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed


Ben,

you reassigned this bug to initramfs-tools and removed the version. As 
detailed in #847343, I wanted to keep this bug on firmware-misc-nonfree 
because:


(1) it protects apt-listbugs users from upgrading firmware-misc-nonfree 
and being hit by #847340, and


(2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
0.125)" which it will need even after #847340 is fixed.

If you are sure that you want this bug on initramfs-tools, I will defer 
to your expertise, but I do not see how this addresses my points above.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: retitle 847343 to firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

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

> retitle 847343 firmware-misc-nonfree: breaks update-initramfs 
> (initramfs-tools <= 0.125) if plymouth installed
Bug #847343 [initramfs-tools] firmware-misc-nonfree: breaks update-initramfs 
(initramfs-tools <= 0.125) if plymouth installed
Ignoring request to change the title of bug#847343 to the same title
> thanks
Stopping processing here.

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

Processed (with 2 errors): reassign 847340 to initramfs-tools, reassign 847343 to initramfs-tools ..., affects 847325

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

> reassign 847340 initramfs-tools
Bug #847340 [initramfs-tools] initramfs-tools: fails to copy DRM modules with 
plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Ignoring request to reassign bug #847340 to the same package
> reassign 847343 initramfs-tools
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Bug reassigned from package 'firmware-misc-nonfree' to 'initramfs-tools'.
No longer marked as found in versions firmware-nonfree/20161130-1.
Ignoring request to alter fixed versions of bug #847343 to the same values 
previously set
> forcemerge 847325 847340 847343
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Unable to merge bugs because:
package of #847340 is 'initramfs-tools' not 'initramfs-tools-core'
package of #847343 is 'initramfs-tools' not 'initramfs-tools-core'
Failed to forcibly merge 847325: Did not alter merged bugs.

> affects 847325 firmware-misc-nonfree
Failed to mark 847325 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/847325 -- Unable to lock 
/org/bugs.debian.org/spool/lock/847325 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

Grave severity is not justified because this package works fine if 
plymouth is not installed. I have set the severity to serious because 
firmware-misc-nonfree does not declare Breaks: initramfs-tools (<= 
0.125). I expect that adding this relationship is the cleanest way to 
ensure working upgrades.


Serious severity still meets my goal of warning apt-listbugs users, 
because RC bugs are reported by default.


I do not know if it is possible to include a conditional in a Breaks: 
(something like "and plymouth installed"). In any case, this is now a 
bona fide firmware-misc-nonfree bug.  :-)


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#846657: marked as done (ImportError: No module named 'requests')

Your message dated Thu, 08 Dec 2016 00:48:33 +
with message-id 
and subject line Bug#846657: fixed in reportbug 7.0.1
has caused the Debian Bug report #846657,
regarding ImportError: No module named 'requests'
to be marked as done.

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

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


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

$ reportbug
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 43, in 
from reportbug import utils
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 43, in 
from .urlutils import open_url
  File "/usr/lib/python3/dist-packages/reportbug/urlutils.py", line 34, in 

import requests
ImportError: No module named 'requests'
--- End Message ---
--- Begin Message ---
Source: reportbug
Source-Version: 7.0.1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated reportbug package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Dec 2016 19:22:37 -0500
Source: reportbug
Binary: reportbug python3-reportbug
Architecture: source all
Version: 7.0.1
Distribution: experimental
Urgency: medium
Maintainer: Reportbug Maintainers 
Changed-By: Sandro Tosi 
Description:
 python3-reportbug - Python modules for interacting with bug tracking systems
 reportbug  - reports bugs in the Debian distribution
Closes: 846657 846778
Changes:
 reportbug (7.0.1) experimental; urgency=medium
 .
   * debian/control
 - add python3-requests to python3-reportbug Depends; Closes: #846657
   * reportbug/utils.py
 - dont remove the first character from the filename when calling an 
external
   MUA; Closes: #846778
Checksums-Sha1:
 9eb64390de7b1d335a2ee813c3639310ba9141df 1842 reportbug_7.0.1.dsc
 88d7baf6a98d4a5c1a5aca3d783b14e4bd848466 342270 reportbug_7.0.1.tar.bz2
 0fd6ee48b5d0f8ce698a1d6a23dd974e8c975836 125756 python3-reportbug_7.0.1_all.deb
 bb4b7717022ce65e183fb5b9433d7a9b63b4f5d5 125800 reportbug_7.0.1_all.deb
 71aa7ba959cd5b6c80931d29732c08d5363be07c 6067 reportbug_7.0.1_amd64.buildinfo
Checksums-Sha256:
 02a21a8c020b31b2d8de5df6493468bff0e4ce077fcac188c7c959e6aa782ca9 1842 
reportbug_7.0.1.dsc
 b4cf1738157d59aca3138e83987a4137098a6bf734feac3c3b4d58b529cf810e 342270 
reportbug_7.0.1.tar.bz2
 ce8e70b4a11362dce7f0b690d5bb022b15704a894996ba96f48d2b5bb8cc5ba7 125756 
python3-reportbug_7.0.1_all.deb
 4e9c293d106ec481fd33e1dee0b7cbe47293e6690d55d67a4c9ba9e5f6e44b73 125800 
reportbug_7.0.1_all.deb
 5072bd5b3a3169cbf03ad474a78dac8126647dcb30ad0eff7a41aa80540c6102 6067 
reportbug_7.0.1_amd64.buildinfo
Files:
 14262e2f37fb81d6b31629e5c0ef3e40 1842 utils standard reportbug_7.0.1.dsc
 a95d861a1688ae9df90cc90b06919b6a 342270 utils standard reportbug_7.0.1.tar.bz2
 61782de1626d9285b1fd0029879cfb46 125756 python standard 
python3-reportbug_7.0.1_all.deb
 515a493c4aa952bc3fe65797331268cb 125800 utils standard reportbug_7.0.1_all.deb
 12a4ac0e2d7ea4c8d9733652078ee3e6 6067 utils standard 
reportbug_7.0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYSKjiAAoJEIefPJk4AalP6igQAIXiifuj+2M7dEygIO1fVJUx
xnhmCW1epmLT/ZVb8PYveGskwyTRJqhuC6LpNixv2slfsIoe6zDzjV56v+Ehu7Ii
DuMg0hoQLjlIGps3i9YUDfI9DY/plOKnEAOCSTsjEpzaoMMk5d8PI0ta6heY6GLc
SDlD9Axt17CMlF6sqprGxMyfU5DB0nL+kvxNqJWgKn1W+wLl9T6l58QM4RIl1+Fk
oPUsA7uS11NNzD78o4Mv0AkHNVag/1kH9pfTcwyvNNAaQMjPoJtCDeLETdtVaSem
tPYgInDoOOIlcaJNT5hTLk4ic9w2ApbiKDDkOJC8VgdCZnwCWkSkAqAsGQegime3
XE00SzvNSKdBWzuLEN7qP+JLKnH1YxOwbnZSckQFR758KcDIW3wLAKOq2MtkEIAt
4FgAIuOd4d7dqZRm6qZT0cSVSeoxZT+Oz65S+YZlLAee3SpTda7x2+ISTZfyt2zu
Gfy/coDTyEpDqmdZJKgbd/9ScLprKbySyuZMGKkxI/tOhjCx7vrGNZTV+uprqauX
ZhRnn/U+DtKXymlxxqyMNU746CKyrV2OumtpgM0C7Llsrw8tTkpYYLcYbMDsU2Zu
50aEutOJMjhVcXgCycPdzcfBTGnHN9sYd4srpoV90ac/Q/O6kihhbqCiQgqQ4POJ
S41jNiicGCnnig08bXR0
=v2dm

Bug#846228: marked as done (joblib: FTBFS randomly (joblib.test.test_parallel.test_nested_parallel_warnings fails))

Your message dated Thu, 08 Dec 2016 00:34:03 +
with message-id 
and subject line Bug#846228: fixed in joblib 0.10.3+git55-g660fe5d-1
has caused the Debian Bug report #846228,
regarding joblib: FTBFS randomly 
(joblib.test.test_parallel.test_nested_parallel_warnings fails)
to be marked as done.

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

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


-- 
846228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:joblib
Version: 0.10.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=python_distutils --with=python2,python3
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_auto_build -i -O--buildsystem=python_distutils
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
python setup.py build --force
running build
running build_py
creating build

[... snipped ...]

joblib.test.test_parallel.test_dispatch_race_condition({'n_tasks': 25, 
'n_jobs': 4, 'batch_size': 7},) ... ok
joblib.test.test_parallel.test_dispatch_race_condition({'n_tasks': 10, 
'pre_dispatch': '2*n_jobs', 'n_jobs': 4},) ... ok
joblib.test.test_parallel.test_default_mp_context ... ok
joblib.test.test_parallel.test_no_blas_crash_or_freeze_with_multiprocessing ... 
ok
joblib.test.test_parallel.test_parallel_with_interactively_defined_functions 
... ok
joblib.test.test_parallel.test_parallel_with_exhausted_iterator ... ok
joblib.test.test_parallel.test_auto_memmap_on_arrays_from_generator ... ok
joblib.test.test_parallel.test_nested_parallel_warnings ... ERROR
Check that it is possible to reduce a memmap backed array ... ok
joblib.test.test_pool.test_high_dimension_memmap_array_reducing ... ok
Check that subprocess can access and update shared memory memmap ... ok
Check that subprocess can access and update shared memory array ... ok
Check that large arrays are not copied in memory ... ok
Check that large arrays memmaping can be disabled ... ok
Check that MemmapingPool uses /dev/shm when possible ... ok
Check that large arrays are not copied in memory in return ... ok
Check that memmaps with a bad buffer are returned as regular arrays ... ok
joblib.test.test_testing.test_check_subprocess_call ... ok
joblib.test.test_testing.test_check_subprocess_call_non_matching_regex ... ok
joblib.test.test_testing.test_check_subprocess_call_wrong_command ... ok
joblib.test.test_testing.test_check_subprocess_call_non_zero_return_code ... ok
joblib.test.test_testing.test_check_subprocess_call_timeout ... ok
Doctest: joblib ... ok

==
ERROR: joblib.test.test_parallel.test_nested_parallel_warnings
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 198, in runTest
self.test(*self.arg)
  File "/<>/joblib/test/test_parallel.py", line 813, in 
test_nested_parallel_warnings
stderr_regex=regex)
  File "/<>/joblib/testing.py", line 90, in check_subprocess_call
stderr_regex, stderr))
ValueError: Unexpected stderr: 'Multiprocessing-backed parallel loops cannot be 
nested' does not match:
''

--
Ran 840 tests in 18.726s

FAILED (errors=1)
debian/rules:25: recipe for target 'python-test3.5' failed
make[1]: *** [python-test3.5] Error 1
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This happens randomly but very often (approximately half of the time).

In fact, a similar error may be found here:

https://tests.reproducible-builds.org/debian/logs/unstable/amd64/joblib_0.10.3-1.build2.log.gz

If you need full build logs, just ask. I have plenty of them:

Status: failed  joblib_0.10.3-1_amd64-20161129T100059Z
Status:

Processed: [reportbug/master] add python3-requests to python3-reportbug Depends; Closes: #846657

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

> tag 846657 pending
Bug #846657 [reportbug] ImportError: No module named 'requests'
Added tag(s) pending.
> tag 846657 pending
Bug #846657 [reportbug] ImportError: No module named 'requests'
Ignoring request to alter tags of bug #846657 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#846657: [reportbug/master] add python3-requests to python3-reportbug Depends; Closes: #846657

2016-12-07 Thread Sandro Tosi

tag 846657 pending
tag 846657 pending
thanks

Date:   Wed Dec 7 18:43:15 2016 -0500
Author: Sandro Tosi 
Commit ID: 146e5d1049b714f4439150b0aa307c121336a29f
Commit URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=146e5d1049b714f4439150b0aa307c121336a29f
Patch URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=146e5d1049b714f4439150b0aa307c121336a29f

add python3-requests to python3-reportbug Depends; Closes: #846657

Processed: Re: Bug#847357: dpkg: dpkg does not reinstall removed/lost conffiles unless forced to

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

> severity 847357 wishlist
Bug #847357 [src:dpkg] dpkg: dpkg does not reinstall removed/lost conffiles 
unless forced to
Severity set to 'wishlist' from 'serious'
> tags 847357 wontfix
Bug #847357 [src:dpkg] dpkg: dpkg does not reinstall removed/lost conffiles 
unless forced to
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Processed: Re: Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

Processing control commands:

> severity -1 minor
Bug #844486 [src:wxwidgets3.0] wxwidgets3.0 should drop the ABI mismatch message
Bug #846019 [src:wxwidgets3.0] pgadmin3: SIGABRT after fatal error complaint 
regarding libwxgtx ABI mismatch
Severity set to 'minor' from 'serious'
Severity set to 'minor' from 'serious'

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

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

2016-12-07 Thread Olly Betts

Control: severity -1 minor

On Tue, Dec 06, 2016 at 07:26:17PM +0200, Adrian Bunk wrote:
> Control: reassign 846019 src:wxwidgets3.0
> Control: forcemerge -1 846019
> Control: severity -1 serious
> Control: affects -1 pgadmin3
> 
> After looking at #846019 this appears to be pretty RC.

#846019 looks to be something different - it's giving a *FATAL* error there
(it's not obvious to me how or why since the two strings seem to match aside
from the ABI and I've not had time to try to reproduce yet), but that means it
would not be helped by the proposed patch, since it's not invoking the warning
case but dropping through to the fatal error code below.

I also don't have the time right now to work out how to undo the unhelpful
forcemerge you've just done, so for now I'm just setting the severity back to
the appropriate one for #844486.  If you know how to cleanly revert a
forcemerge, please do.

As for the proposed patch, I'm not wild about just removing this warning - the
current patch we're applying downgrades the fatal error to a warning so that
there's a hint as to what's going on if there are problems caused by the
compler ABI change.  Remove that will make it much harder to debug any
such cases, and risks annoying wx upstream with bug reports.  If people
are finding the current wording too scary, we could reword it.

Cheers,
Olly

Bug#847413: gprolog: Debian changelog uncompressed

2016-12-07 Thread Salvador Abreu

Hi; I'll take care of it in the next version (which is needed
for other reasons as well...)

thanks for noting,
-s

> On 07 Dec 2016, at 23h26, Aaron M. Ucko  wrote:
> 
> Package: gprolog
> Version: 1.4.5-1
> Severity: serious
> Justification: Policy 12.7
> 
> gprolog now ships its Debian changelog in uncompressed form, a policy
> violation that turns out to reveal a latent bug in apt-listchanges
> (which I'll report in a moment, so I can't cite a number yet).
> 
> Could you please fix that?
> 
> Thanks!
> 
> -- System Information:
> Debian Release: stretch/sid
>  APT prefers testing
>  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, x32
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages gprolog depends on:
> ii  libc6  2.24-7
> 
> gprolog recommends no packages.
> 
> gprolog suggests no packages.
> 
> -- no debconf information



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#846671: [Debian-med-packaging] Bug#846671: Artemis should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))]

2016-12-07 Thread Sascha Steinbiss

Hi Andreas and Andrew,

to address this problem I have taken a shot at patching Debian’s Artemis to use 
the new htsjdk API, avoiding SAMFileReader and using the SamReaderFactory 
instead. This fixed the FTBFS for me.
I tested BAM file reading by opening MAL1.embl.gz from the test/data directory 
and adding MAL1_8h.bam via ‘File->Read BAM/VCF...'. One of the genes has some 
mapped reads that are indeed shown. Comparing the displayed pile of mapped 
reads to the one shown by the recent Artemis version I have on Mac OS X, the 
result seems to be correct, but given my lack of practical experience with the 
BAM/VCF/‘anything-to-do-with-reads' components of Artemis I can’t say if I 
caught everything.

I also updated the Debian version to 16.0.17, the latest release from Sanger. 
This allowed me to drop a couple of patches that I already merged earlier with 
my part-time-upstream hat on.
For now I have pushed my work into the ’6_0_17’ branch in git and I would like 
to kindly ask for some more testing. I don’t have suitable test data here and 
don’t really feel like an expert to test the right usage patterns. 

Cheers
Sascha

> On 5 Dec 2016, at 15:56, Andrew Page  wrote:
> 
> Hi Andreas,
> Thanks for letting us know.  We are actively trying to hire a Java developer 
> who will take over the maintenance and development of Artemis. So 
> unfortunately it will be at least a few months before we will have anyone in 
> post to work on it.  If you happen to know of anyone looking for a job, 
> please send them our way!
> Regards,
> Andrew
> 
> 
> 
>> On 5 Dec 2016, at 14:40, Andreas Tille  wrote:
>> 
>> Hi,
>> 
>> after uploading htsjdk 2.7.0 Artemis failed to build from source[1].  I
>> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
>> was removed from htsjdk source and assumed that this was by accident.
>> However, upstream has dropped this interface intentionally as you can
>> read below.  In issue #767[2] an htsjdk author gives advise to use the
>> new API version.
>> 
>> Kind regards
>> 
>>  Andreas.
>> 
>> 
>> [1] https://bugs.debian.org/846671
>> [2] https://github.com/samtools/htsjdk/issues/767
>> 
>> 
>> - Forwarded message from Daniel Gómez-Sánchez  
>> -
>> 
>> Date: Mon, 05 Dec 2016 06:18:16 -0800
>> From: Daniel Gómez-Sánchez 
>> To: samtools/htsjdk 
>> Cc: Andreas Tille , Author 
>> Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)
>> 
>> The file was removed in #699 because it was deprecated. I guess that either 
>> 1) fastqc/artemis should be updated to use the new API version, or 2) the 
>> classpath for them in Debian should include an older version.
>> 
>> -- 
>> You are receiving this because you authored the thread.
>> Reply to this email directly or view it on GitHub:
>> https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
>> 
>> - End forwarded message -
>> 
>> -- 
>> http://fam-tille.de
>> 
>> - End forwarded message -
>> 
>> -- 
>> http://fam-tille.de
> 
> 
> 
> -- 
> The Wellcome Trust Sanger Institute is operated by Genome Research 
> Limited, a charity registered in England with number 1021457 and a 
> company registered in England with number 2742969, whose registered 
> office is 215 Euston Road, London, NW1 2BE. 
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#846711: git-build-recipe: FTBFS: Tests failures

2016-12-07 Thread Guillem Jover

Hi!

On Wed, 2016-12-07 at 09:14:36 +, Colin Watson wrote:
> On Tue, Dec 06, 2016 at 10:54:21PM -0500, James McCoy wrote:
> > On Tue, Dec 06, 2016 at 10:39:44AM +, Colin Watson wrote:
> > > git-build-recipe doesn't do anything particular to ask debuild to run
> > > lintian here, and it doesn't expect or require a lintian check.  It used
> > > to be that debuild would check whether lintian was in fact installed,
> > > and not run it if it wasn't; indeed, its documentation still says "then
> > > runs lintian on the .changes file created (assuming that lintian is
> > > installed)", thereby claiming that that's still what it does.  But this
> > > was broken in devscripts 58eb4a4a5e006bf9a2589da0ef2f36aa0d81ed8c when
> > > changing debuild to use dpkg-buildpackage --check-command.
> > 
> > Indeed.  In order to fix this, I either need to move running lintian
> > back into debuild or dpkg needs to not error when the check command
> > isn't present.
> 
> I don't understand why.  Wouldn't something like this (untested) be
> sufficient?
> 
> diff --git a/scripts/debuild.pl b/scripts/debuild.pl
> index 639bbac..afbd1dc 100755
> --- a/scripts/debuild.pl
> +++ b/scripts/debuild.pl
> @@ -988,7 +988,7 @@ else {
>  open STDOUT, ">" or fatal "can't reopen stdout: $!";
>  open STDERR, ">" or fatal "can't reopen stderr: $!";
>  
> -if ($run_lintian) {
> +if ($run_lintian and system("command -v lintian >/dev/null 2>&1") == 0) {
>   push(@dpkg_opts, '--check-command=lintian',
>   map { "--check-option=$_" } @lintian_opts);
>  }

Yes, please. I'da rather not change the current behavior in
dpkg-buildpackage, because I think that if the user explicitly asked
to run a command that that does not exist, the correct thing to do is
to fail stating so. :)

Thanks,
Guillem

Processed: retitle 847343 to firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

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

> retitle 847343 firmware-misc-nonfree: breaks update-initramfs 
> (initramfs-tools <= 0.125) if plymouth installed
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs if plymouth installed
Changed Bug title to 'firmware-misc-nonfree: breaks update-initramfs 
(initramfs-tools <= 0.125) if plymouth installed' from 'firmware-misc-nonfree: 
breaks update-initramfs if plymouth installed'.
> thanks
Stopping processing here.

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

Processed: severity of 847343 is serious

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

> severity 847343 serious
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs if plymouth installed
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#828815: marked as done (pyvows: FTBFS: Expected strings to be equal, but they were different)

Your message dated Wed, 07 Dec 2016 23:49:09 +
with message-id 
and subject line Bug#828815: fixed in pyvows 2.1.0-2
has caused the Debian Bug report #828815,
regarding pyvows: FTBFS: Expected strings to be equal, but they were different
to be marked as done.

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

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


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

pyvows fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  pyvows
   Version:  2.0.6-2
   Build architecture:   amd64
   Date: Tue, 28 Jun 2016 07:44:25 +0200
   Hostname: 5d4680d1283e
   Uname:Linux 5d4680d1283e 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 'pyvows-build-deps' in 
'../pyvows-build-deps_2.0.6-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 pyvows-build-deps.
  (Reading database ... 23073 files and directories currently installed.)
  Preparing to unpack pyvows-build-deps_2.0.6-2_all.deb ...
  Unpacking pyvows-build-deps (2.0.6-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
help2man python-all python-colorama python-coverage python-gevent
python-greenlet python-preggy python-setuptools python-unidecode
  Suggested packages:
python-gevent-doc python-gevent-dbg python-openssl python-greenlet-doc
python-greenlet-dev python-greenlet-dbg python-setuptools-doc
  Recommended packages:
libjs-jquery-hotkeys libjs-jquery-isonscreen libjs-jquery-tablesorter
libjs-jquery
  The following NEW packages will be installed:
help2man python-all python-colorama python-coverage python-gevent
python-greenlet python-preggy python-setuptools python-unidecode
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 1011 kB of archives.
  After this operation, 3956 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 python-setuptools all 
20.10.1-1.1 [203 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-2 [938 B]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 python-colorama all 
0.3.7-1 [25.7 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 python-coverage amd64 
4.1+dfsg.1-2 [124 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 python-greenlet amd64 
0.4.9-2+b1 [19.2 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 python-gevent amd64 
1.1.1-1 [340 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 python-unidecode all 
0.04.19-1 [122 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 python-preggy all 
1.3.0-1 [15.4 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 help2man amd64 1.47.4 
[162 kB]
  Fetched 1011 kB in 0s (2297 kB/s)
  Selecting previously unselected package python-setuptools.
  (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%

Bug#847413: gprolog: Debian changelog uncompressed

2016-12-07 Thread Aaron M. Ucko

"Aaron M. Ucko"  writes:

> (which I'll report in a moment, so I can't cite a number yet).

FTR, the apt-listchanges bug is #847414.

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

Bug#847413: gprolog: Debian changelog uncompressed

2016-12-07 Thread Aaron M. Ucko

Package: gprolog
Version: 1.4.5-1
Severity: serious
Justification: Policy 12.7

gprolog now ships its Debian changelog in uncompressed form, a policy
violation that turns out to reveal a latent bug in apt-listchanges
(which I'll report in a moment, so I can't cite a number yet).

Could you please fix that?

Thanks!

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

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

Versions of packages gprolog depends on:
ii  libc6  2.24-7

gprolog recommends no packages.

gprolog suggests no packages.

-- no debconf information

Processed: Re: Bug#846144: gobject-introspection randomly hangs liferea build

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

> affects 846782 liferea
Bug #846782 [gobject-introspection] gobject-introspection randomly hangs 
liferea build
Added indication that 846782 affects liferea
> thanks
Stopping processing here.

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

Processed: Re: Bug#842753 closed by gregor herrmann <gre...@debian.org> (Bug#842753: fixed in libnet-sip-perl 0.807-1)

Processing control commands:

> reopen -1
Bug #842753 {Done: gregor herrmann } [libnet-sip-perl] 
FTBFS: test failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libnet-sip-perl/0.807-1.

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

Bug#842753: closed by gregor herrmann <gre...@debian.org> (Bug#842753: fixed in libnet-sip-perl 0.807-1)

2016-12-07 Thread gregor herrmann

Control: reopen -1

On Wed, 07 Dec 2016 17:42:13 +, Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the libnet-sip-perl package:
> 
> #842753: FTBFS: test failures
> 
> It has been closed by gregor herrmann .

That was too fast :/

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/libnet-sip-perl.html
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.807-1.rbuild.log


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#841636: [debian-mysql] Processed: Merge duplicates

2016-12-07 Thread Otto Kekäläinen

Have you tried building with MariaDB Connector C/C++ (package
libmariadb-dev) instead of the MySQL Connector C++?

841636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841636
844275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844275
844302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844302
844304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844304
844401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844401
844492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844492
844550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844550
844824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844824
844850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844850
844851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844851
844852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844852
844863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844863
844868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844868
844875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844875
844876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844876
844894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844894
844895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844895
844899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844899
844935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844935
844941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844941
844957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844957
844981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844981
846746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846746

Bug#847343: firmware-misc-nonfree: breaks update-initramfs if plymouth installed


On Wed, 7 Dec 2016 11:57:54 -0500 Zack Weinberg  wrote:

FYI, on a system without plymouth, the package installs without any
complaint, and the computer boots successfully using the new
initramfs.


Thanks, Zack. I have updated the title to indicate that this bug only 
affects systems with plymouth installed.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: retitle 847343 to firmware-misc-nonfree: breaks update-initramfs if plymouth installed

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

> retitle 847343 firmware-misc-nonfree: breaks update-initramfs if plymouth 
> installed
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs
Changed Bug title to 'firmware-misc-nonfree: breaks update-initramfs if 
plymouth installed' from 'firmware-misc-nonfree: breaks update-initramfs'.
> thanks
Stopping processing here.

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

Bug#847343: firmware-misc-nonfree: breaks update-initramfs


This is the same bug reported in #847340 against initramfs-tools:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340

The problem is in initramfs-tools; firmware-misc-nonfree is just the 
trigger. Rather than merging, I would like to leave this bug against 
firmware-misc-nonfree to protect apt-listbugs users from the breakage 
upgrading firmware-misc-nonfree triggers.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#846741: marked as done (rkt: FTBFS: XXX)

Your message dated Wed, 07 Dec 2016 22:21:16 +
with message-id 
and subject line Bug#846741: fixed in rkt 1.20.0+dfsg-1
has caused the Debian Bug report #846741,
regarding rkt: FTBFS: XXX
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/rkt-1.16.0+dfsg/_build/src/github.com/coreos/rkt'
> mkdir -p dist/manpages/
> ls 
> /<>/rkt-1.16.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.16.0/gopath/src/github.com/coreos/rkt/rkt/*.go
>  | \
>   grep -vE '_test.go|main.go|_gen.go|_stub.go' | \
>   GO15VENDOREXPERIMENT=1 GOARCH="amd64" CGO_ENABLED=1 CC="gcc" CXX="g++" 
> GOPATH="/<>/rkt-1.16.0+dfsg/_build/src2" GOARCH=amd64 CC= xargs 
> "go" run 
> /<>/rkt-1.16.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.16.0/gopath/src/github.com/coreos/rkt/rkt/manpages_gen.go
> # github.com/coreos/rkt/api/v1alpha
> ../../../../src2/src/github.com/coreos/rkt/api/v1alpha/api.pb.go:844: 
> undefined: grpc.SupportPackageIsVersion3
> rkt/rkt.mk:37: recipe for target 'manpages' failed
> make[2]: *** [manpages] Error 123

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/rkt_1.16.0+dfsg-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated rkt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Dec 2016 08:47:56 +1100
Source: rkt
Binary: golang-github-coreos-rkt-dev rkt
Architecture: source all amd64
Version: 1.20.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 golang-github-coreos-rkt-dev - rkt API source
 rkt- CLI for running App Containers
Closes: 846741
Changes:
 rkt (1.20.0+dfsg-1) unstable; urgency=medium
 .
   * New upsteram release [November 2016].
   * Removed obsolete "k8s.patch".
   * Added new backported "systemd.patch". Thanks, Luca Bruno.
   * Build-Depends:
 = golang-github-appc-docker2aci-dev (>= 0.14.0~)
 = golang-github-appc-spec-dev (>= 0.8.9~)
 = golang-github-coreos-go-systemd-dev (>= 14~)
 + golang-github-kr-pretty-dev
 + golang-github-puerkitobio-purell-dev
   * rules: re-build .pb.go file(s) (Closes: #846741).
Checksums-Sha1:
 5972f72146eec012ad293fce6fc3cad684372757 3766 rkt_1.20.0+dfsg-1.dsc
 7848863ae1e10e7096bc85103bbfe8ec897481a0 1027456 rkt_1.20.0+dfsg.orig.tar.xz
 d0995c1fe26d0e8d3dd0f256c8a373eececd8d00 7560 rkt_1.20.0+dfsg-1.debian.tar.xz
 7771ab3208292ad81ec35eea5b464042485d3e9f 116214 
golang-github-coreos-rkt-dev_1.20.0+dfsg-1_all.deb
 92c9ce2274b5289a23e4e7a241e3376e69239635 1742100 
rkt-dbgsym_1.20.0+dfsg-1_amd64.deb
 21738b28a974dbb974a8d7ac6a6ab5ed7bb5e776 13839 
rkt_1.20.0+dfsg-1_amd64.buildinfo
 15544f8dfd35adf15a008e529c157805ad17bfbc 36184686 rkt_1.20.0+dfsg-1_amd64.deb
Checksums-Sha256:
 0f86b737f40c8835f8ae63a6924296f99151e9a2b621e6c6c3d17071e04a520a 3766 
rkt_1.20.0+dfsg-1.dsc
 8ec58a0401a97539660ef7a6a3d4fd99dec5f948bd450e2df5081c249ac52526 1027456 
rkt_1.20.0+dfsg.orig.tar.xz

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

2016-12-07 Thread Tony Cook

On Wed, Dec 07, 2016 at 10:27:33PM +0200, Adrian Bunk wrote:
> Source: libimager-perl
> Version: 1.005+dfsg-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=libimager-perl=sid
> 
> ...
> Test Summary Report
> ---
> t/150-type/030-double.t   (Wstat: 10 Tests: 16 Failed: 0)
>   Non-zero wait status: 10
>   Parse errors: Bad plan.  You planned 136 tests but ran 16.

This looks like an unaligned access from the tests that failed,
probably in imgdouble.c.

Would it be possible to get access to this (or similar) hardware to
debug on?

Otherwise a backtrace for a -g build from the crash would be handy:

  perl Makefile.PL OPTIMIZE=-g
  make
  gdb --args perl -Mblib t/150-type/030-double.t
  r

  bt

Thanks,
Tony

Processed: closing 828393

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

> close 828393
Bug #828393 [src:libevent] libevent: FTBFS with openssl 1.1.0
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#828262: cfengine2: FTBFS with openssl 1.1.0

2016-12-07 Thread Petter Reinholdtsen

Given that cfengine2 no longer get any upstream development, as far as I know,
I guess the easiest and most sensible way to fix this is to build with
libssl1.0-dev for now.  If cfengine2 is still needed in Stretch+1 someone should
consider to port the code to openssl 1.1.

Debian Edu still uses cfengine2, and would very much like to see it still
available in Stretch.

If this patch is applied, this BTS report should have its severity lowered to
important or normal.

diff -ur cfengine2-2.2.10/debian/control cfengine2-2.2.10-pere/debian/control
--- cfengine2-2.2.10/debian/control 2016-08-21 08:24:15.0 +
+++ cfengine2-2.2.10-pere/debian/control2016-12-07 22:14:28.911881217 
+
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Antonio Radici 
 Build-Depends: debhelper (>= 7.0.50), autoconf, automake, autotools-dev,
- bison, dh-autoreconf, flex, libdb-dev, libssl-dev, libtool, perl (>= 5),
+ bison, dh-autoreconf, flex, libdb-dev, libssl1.0-dev, libtool, perl (>= 5),
  po-debconf, texinfo, quilt, libselinux1-dev [linux-any]
 Standards-Version: 3.9.8
 Homepage: http://www.cfengine.org/

-- 
Happy hacking
Petter Reinholdtsen

Bug#847338: flight-of-the-amazon-queen: non-free restrictions in license conditions

2016-12-07 Thread Ben Finney

On 07-Dec-2016, Ben Finney wrote:

> The license conditions from the copyright holders restrict
> distributing the work for a fee:
> 
> 2) You may charge a reasonable copying fee for this archive […]
> 
> It is unclear what the copyright holders would consider a “reasonable
> fee”; regardless what that limit would be, it is a restriction on the
> fee that may be charged for redistribution.
> 
> 3) You may not charge a fee for the game itself. This includes
> reselling the game as an individual item.

As has been pointed out to me (thanks, Ansgar Burchardt) the existing
Artistic License terms contain effectively the same restrictions, in §5:

5. You may charge a reasonable copying fee for any distribution of
this Package. […] You may not charge a fee for this Package itself.

That demonstrates that these restrictions are deemed DFSG-free by
Debian's FTP Masters in works prior and subsequent to this one.

Thank you, maintainers, for responding promptly to bug reports :-)

-- 
 \ “If I had known what it would be like to have it all... I might |
  `\ have been willing to settle for less.” —Jane Wagner, via Lily |
_o__)   Tomlin |
Ben Finney 

signature.asc
Description: PGP signature

Bug#845335: bzr issue

2016-12-07 Thread Jelmer Vernooĳ

On Wed, Dec 07, 2016 at 05:47:52PM +, Ben Dooks wrote:
> The "bzr: ERROR: exceptions.TypeError: first argument must be string or
> compiled pattern" is still there after updating.
> 
> bzr is already the newest version (2.7.0+bzr6619-1).
This has been fixed. The latest version of bzr (currently in unstable, doesn't
seem to have made it to testing) is 2.7.0+bzr6619-3.

Bug#847322: flight-of-the-amazon-queen: source package should include complete source

2016-12-07 Thread Ben Finney

On 07-Dec-2016, Markus Koschany wrote:
> On 07.12.2016 11:24, Ben Finney wrote:

> > The source was presumably available to upstream when making this
> > package, see  for
> > example.

I have now responded to ask about the source that message describes
.

> Please read README.Debian. This game is fully DFSG compliant and every
> piece of source, in this case game assets and media files are included
> in this package.

It is because the copyright holder described having the source (which
I take to mean, the source used to generate the binary blob) at the
time of making what became the Debian package, that I am seeking that
source for the Debian source package.

-- 
 \“If one tells the truth, one is sure, sooner or later, to be |
  `\   found out.” —Oscar Wilde, _Phrases and Philosophies for the Use |
_o__)  of the Young_, 1894 |
Ben Finney 

signature.asc
Description: PGP signature

Bug#841257: fixed in sendmail 8.15.2-7

2016-12-07 Thread Andreas Beckmann

On 2016-12-07 17:12, Axel 'the C.L.A.' Müller wrote:
> Seems this change now causes cron to spam like:
> 
> From: root@e560 (Cron Daemon)
> To: root@e560
> Subject: Cron  test -x /etc/init.d/sendmail && test
> -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail
> && /usr/share/sendmail/sendmail cron-msp
> 
> su: Muss von einem Terminal gestartet werden.
> 
> (Translation: "su: Needs to be started from a terminal")
> 

can you try to replace the touch_stamp() method in
/usr/share/sendmail/sendmail with this:


touch_stamp() {
if [ "$(id -nu)" = "smmsp" ]; then
touch "$1"
else
su smmsp -s /bin/sh -c "touch '$1'"
fi
}


That should work at least for the smmsp cronjob ...


Andreas

Bug#820794: [Pkg-samba-maint] Bug#820794: still visible: smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares

2016-12-07 Thread Mathieu Parent

Control: tag -1 + jessie
Control: found -1 2:4.2.14+dfsg-0+deb8u1

2016-12-07 15:07 GMT+01:00 Christian Hilgers :
> Hi,
>
> I tried the fix from proposed updates and sadly I cannot confirm it is
> fixed:

Indeed, the following patch is not applied in the jessie branch:
https://attachments.samba.org/attachment.cgi?id=11971

I've applied the patch, but I've not uploaded. To the team: Are there
other important bugs to handle in jessie before uploading?

Regards
-- 
Mathieu Parent

Processed: Re: [Pkg-samba-maint] Bug#820794: still visible: smbclient: "cli_list: Error: unable to parse name from info level 260" with Windows 10 shares

Processing control commands:

> tag -1 + jessie
Bug #820794 {Done: Jelmer Vernooĳ } [smbclient] smbclient: 
"cli_list: Error: unable to parse name from info level 260" with Windows 10 
shares
Added tag(s) jessie.
> found -1 2:4.2.14+dfsg-0+deb8u1
Bug #820794 {Done: Jelmer Vernooĳ } [smbclient] smbclient: 
"cli_list: Error: unable to parse name from info level 260" with Windows 10 
shares
Marked as found in versions samba/2:4.2.14+dfsg-0+deb8u1; no longer marked as 
fixed in versions samba/2:4.2.14+dfsg-0+deb8u1.

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

Bug#820794: marked as pending

2016-12-07 Thread Philippe Cloutier

Merci d'avance Mathieu.
Note that the link to git.debian.org is broken (404).

> -Message d'origine-
> De : Mathieu Parent [mailto:math.par...@gmail.com]
> Envoyé : 7 décembre 2016 15:46
> À : 820794-submit...@bugs.debian.org
> Objet : Bug#820794: marked as pending
> 
> tag 820794 pending
> thanks
> 
> Hello,
> 
> Bug #820794 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
> 
> http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=68168a5
> 
> ---
> commit 68168a5c57df43425bfe40a69fc28c32a08b63bf
> Author: Mathieu Parent 
> Date:   Wed Dec 7 21:45:45 2016 +0100
> 
> Changelog for previous commit
> 
> diff --git a/debian/changelog b/debian/changelog
> index 2259e6c..edf9c25 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,9 @@
> +samba (2:4.2.14+dfsg-0+deb8u2) UNRELEASED; urgency=medium
> +
> +  * Fix smbclient compatibility with Windows 10 (Closes: #820794)
> +
> + -- Mathieu Parent   Wed, 07 Dec 2016 21:44:28 +0100
> +
>  samba (2:4.2.14+dfsg-0+deb8u1) jessie; urgency=high
> 
>* New upstream release.
> 
> --
> To unsubscribe, send mail to 820794-unsubscr...@bugs.debian.org.

Bug#847369: marked as done (Error: Cannot find module 'requirejs' (missing package.json))

Your message dated Wed, 07 Dec 2016 21:07:27 +
with message-id 
and subject line Bug#847369: fixed in requirejs 2.3.2-1
has caused the Debian Bug report #847369,
regarding Error: Cannot find module 'requirejs' (missing package.json)
to be marked as done.

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

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


-- 
847369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: node-requirejs
version: 2.2.0-1
severity: serious
control: block 847367 by -1
justification: makes the package unusable

The error I get when trying to use it from grunt-contrib-requirejs
(available in
git+ssh://git.debian.org/git/pkg-javascript/node-grunt-contrib-requirejs.git)
is given below

node-grunt-contrib-requirejs$ grunt --verbose
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.
Initializing config...OK

Registering "tasks" tasks.
Loading "requirejs.js" tasks...ERROR
>> Error: Cannot find module 'requirejs'
>>   at Function.Module._resolveFilename (module.js:325:15)
>>   at Function.Module._load (module.js:276:25)
>>   at Module.require (module.js:353:17)
>>   at require (internal/module.js:12:17)
>>   at Object.module.exports
(/home/pravi/forge/debian/git/pkg-javascript/node-grunt-contrib-requirejs/tasks/requirejs.js:12:19)
>>   at loadTask (/usr/lib/nodejs/grunt/lib/grunt/task.js:318:10)
>>   at /usr/lib/nodejs/grunt/lib/grunt/task.js:354:7
>>   at Array.forEach (native)
>>   at loadTasks (/usr/lib/nodejs/grunt/lib/grunt/task.js:353:11)
>>   at Task.task.loadTasks (/usr/lib/nodejs/grunt/lib/grunt/task.js:365:5)
>>   at Object.module.exports
(/home/pravi/forge/debian/git/pkg-javascript/node-grunt-contrib-requirejs/Gruntfile.js:67:9)
>>   at loadTask (/usr/lib/nodejs/grunt/lib/grunt/task.js:318:10)
>>   at Task.task.init (/usr/lib/nodejs/grunt/lib/grunt/task.js:437:5)
>>   at Object.grunt.tasks (/usr/lib/nodejs/grunt/lib/grunt.js:111:8)
>>   at Object.module.exports [as cli]
(/usr/lib/nodejs/grunt/lib/grunt/cli.js:27:9)
>>   at Object. (/usr/lib/nodejs/grunt-cli/bin/grunt:49:20)
>>   at Module._compile (module.js:409:26)
>>   at Object.Module._extensions..js (module.js:416:10)
>>   at Module.load (module.js:343:32)
>>   at Function.Module._load (module.js:300:12)
>>   at Function.Module.runMain (module.js:441:10)
>>   at startup (node.js:139:18)
>>   at node.js:974:3

Also consider using pkg-javascript alioth repo for this package (there
is a repo there, but it is outdated), so we can fix these kind of issues
faster.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: requirejs
Source-Version: 2.3.2-1

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated requirejs 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Dec 2016 19:05:13 +
Source: requirejs
Binary: node-requirejs libjs-requirejs
Architecture: source all
Version: 2.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libjs-requirejs - JavaScript file and module loader
 node-requirejs - JavaScript file and module loader - NodeJS
Closes: 845158 847369
Changes:
 requirejs (2.3.2-1) unstable; urgency=low
 .
   * New upstream release.
   * Install node files to requirejs subdirectory.
   * Symlink r.js as index.js (closes: #845158).
   * Install package.json with the node files (closes: #847369).
   * Update Standards-Version to 3.9.8 .
Checksums-Sha1:
 0f5d7278bd5493e7838a8054141efd8be5a948a4 1850 requirejs_2.3.2-1.dsc
 1e36800c6f254c8ad8ee5860a86d2b9df273a284 8067617 requirejs_2.3.2.orig.tar.gz
 c3044358f25e49b3542e3ae3018bddec3ab0b1fd 5540 requirejs_2.3.2-1.debian.tar.xz
 abf5c9914612c471f1f0b7ae2851cd765c528da9 29586 libjs-requirejs_2.3.2-1_all.deb

Bug#847172: marked as done (sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128))

Your message dated Wed, 07 Dec 2016 21:07:35 +
with message-id 
and subject line Bug#847172: fixed in sagenb-export 2.0-2
has caused the Debian Bug report #847172,
regarding sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode 
characters in position 41-42: ordinal not in range(128)
to be marked as done.

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

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


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

Dear Maintainer,

sagenb-export fails to build from source in unstable/amd64:

  […]

  py27 runtests: PYTHONHASHSEED='256193135'
  py27 runtests: commands[0] | python2.7 -m unittest discover
  ...E..
  ==
  ERROR: test_aleksandra_slapik_44 (test.test_sagenb_writer.ReadSageNB)
  --
  Traceback (most recent call last):
File "«BUILDDIR»/test/test_sagenb_writer.py", line 39, in 
test_aleksandra_slapik_44
  ipynb.write(self.tmp_filename(u'WDI projekt - R\xf3\u017cankowski, 
Kie\u0142pi\u0144ski, Kozok.ipynb'))
File "«BUILDDIR»/sagenb_export/ipynb_writer.py", line 58, in write
  write(ipynb, filename)
File "/usr/lib/python2.7/dist-packages/nbformat/__init__.py", line 163, in 
write
  with io.open(fp, 'w', encoding='utf-8') as f:
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: 
ordinal not in range(128)
  
  --
  Ran 6 tests in 0.028s
  
  FAILED (errors=1)
  ERROR: InvocationError: '«BUILDDIR»/.tox/py27/bin/python2.7 -m unittest 
discover'
  py35 create: «BUILDDIR»/.tox/py35
  py35 inst: «BUILDDIR»/.tox/dist/sagenb_export-2.0.zip
  py35 installed: 
decorator==4.0.6,devscripts==2.16.11,entrypoints==0.2.2.post2,ipykernel==4.5.0,ipython==5.1.0,ipython-genutils==0.1.0,Jinja2==2.8,jsonschema==2.5.1,jupyter-client==4.4.0,jupyter-core==4.2.0,MarkupSafe==0.23,mistune==0.7.3,nbconvert==4.2.0,nbformat==4.1.0,notebook==4.2.3,pexpect==4.2.0,pickleshare==0.7.4,pkg-resources==0.0.0,pluggy==0.4.0,prompt-toolkit==1.0.9,ptyprocess==0.5.1,py==1.4.31,Pygments==2.1.3,pyzmq==15.4.0,sagenb-export==2.0,simplegeneric==0.8.1,six==1.10.0,terminado==0.6,tornado==4.4.2,tox==2.5.0,traitlets==4.3.1,virtualenv==15.1.0,wcwidth==0.1.7
  py35 runtests: PYTHONHASHSEED='256193135'
  py35 runtests: commands[0] | python3.5 -m unittest discover
  E.
  ==
  ERROR: test_aleksandra_slapik_44 (test.test_sagenb_writer.ReadSageNB)
  --
  Traceback (most recent call last):
File "«BUILDDIR»/test/test_sagenb_writer.py", line 39, in 
test_aleksandra_slapik_44
  ipynb.write(self.tmp_filename(u'WDI projekt - R\xf3\u017cankowski, 
Kie\u0142pi\u0144ski, Kozok.ipynb'))
File "«BUILDDIR»/sagenb_export/ipynb_writer.py", line 58, in write
  write(ipynb, filename)
File "/usr/lib/python3/dist-packages/nbformat/__init__.py", line 163, in 
write
  with io.open(fp, 'w', encoding='utf-8') as f:
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 43-44: 
ordinal not in range(128)
  
  --
  Ran 6 tests in 0.020s
  
  FAILED (errors=1)
  ERROR: InvocationError: '«BUILDDIR»/.tox/py35/bin/python3.5 -m unittest 
discover'
  ___ summary 

  ERROR:   py27: commands failed
  ERROR:   py35: commands failed
  debian/rules:23: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


sagenb-export.2.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: sagenb-export
Source-Version: 2.0-2

We believe that the bug you reported is fixed in the latest version

Bug#842443: marked as done (abiword displays documents as black on black with GTK 3.22)

Your message dated Wed, 07 Dec 2016 21:03:37 +
with message-id 
and subject line Bug#842443: fixed in abiword 3.0.2-2
has caused the Debian Bug report #842443,
regarding abiword displays documents as black on black with GTK 3.22
to be marked as done.

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

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


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

Dear Maintainer,

Every time I open a word document in ABIWord it displays as black on
black, and so is unreadable.  Clicking anywhere on the page briefly
shows the text, but only for a fraction of a second.

In the dialogs, the background for the pages is white, as I expect,
but it is displayed as black.

This makes abiword unusable for me.

Libreoffice correctly displays the same documents.


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

Kernel: Linux 4.9.0-rc2+ (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages abiword depends on:
ii  abiword-common  3.0.2-1
ii  gsfonts 1:8.11+urwcyr1.0.7~pre44-4.3
ii  libabiword-3.0  3.0.2-1
ii  libc6   2.24-5
ii  libdbus-1-3 1.10.12-1
ii  libdbus-glib-1-20.108-1
ii  libgcc1 1:6.2.0-9
ii  libgcrypt20 1.7.3-2
ii  libglib2.0-02.50.1-1
ii  libgnutls30 3.5.5-2
ii  libgoffice-0.10-10  0.10.32-1
ii  libgsf-1-1141.14.40-1
ii  libgtk-3-0  3.22.1-1
ii  libjpeg62-turbo 1:1.5.1-2
ii  libloudmouth1-0 1.5.3-2
ii  libots0 0.5.0-2.3
ii  libpng16-16 1.6.25-2
ii  librdf0 1.0.17-1+b1
ii  libreadline77.0-1
ii  librevenge-0.0-00.0.4-6
ii  libsoup2.4-12.56.0-1
ii  libstdc++6  6.2.0-9
ii  libtelepathy-glib0  0.24.1-1.1
ii  libtidy51:5.2.0-2
ii  libwmf0.2-7 0.2.8.4-10.5+b1
ii  libwpd-0.10-10  0.10.1-5
ii  libwpg-0.3-30.3.1-3
ii  libxml2 2.9.4+dfsg1-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages abiword recommends:
ii  abiword-plugin-grammar 3.0.2-1
ii  aspell-en [aspell-dictionary]  2016.06.26-0-0.1
ii  fonts-liberation   1:1.07.4-2
ii  poppler-utils  0.44.0-3

abiword suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: abiword
Source-Version: 3.0.2-2

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated abiword package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2016 15:13:02 -0500
Source: abiword
Binary: abiword-common abiword abiword-plugin-grammar libabiword-3.0 
libabiword-3.0-dev gir1.2-abiword-3.0
Architecture: source
Version: 3.0.2-2
Distribution: sid
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Jeremy Bicha 
Description:
 abiword- efficient, featureful word processor with collaboration
 abiword-common - efficient, featureful word processor with collaboration -- 
common
 abiword-plugin-grammar - grammar checking plugin for AbiWord
 gir1.2-abiword-3.0 - GObject introspection data for libabiword
 libabiword-3.0 - efficient, featureful word processor with collaboration -- 
shared
 libabiword-3.0-dev - efficient, featureful word processor with collaboration 
-- develo
Closes: 842443
Launchpad-Bugs-Fixed: 1637893
Changes:
 abiword (3.0.2-2) sid; urgency=high
 .
   * Add gtk322.patch:
 - Upstream patch to fix black background with GTK 3.22
   (Closes: #842443) (LP: #1637893)
   * Bump dh compat to 10
   * debian/control:

Bug#847355: quagga-core: fails to install, remove, and install again

2016-12-07 Thread Scott Leggett

On 2016-12-07.14:53, Andreas Beckmann wrote:
> Package: quagga-core
> Version: 1.1.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install,
> remove (but not purge), and install again.
> Before the second installation the package is in config-files-remaining
> state. The configuration is remaining from the last version that was
> successfully configured - which is the same version that is going to be
> installed again.
> 
> Like a plain failure on initial install this makes the package too buggy
> for a release, thus the severity.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package quagga-core.
>   (Reading database ... 
> (Reading database ... 4885 files and directories currently installed.)
>   Preparing to unpack .../quagga-core_1.1.0-1_amd64.deb ...
>   addgroup: The group `quaggavty' already exists as a system group. Exiting.
>   addgroup: The group `quagga' already exists as a system group. Exiting.
>   The user `quagga' is already a member of `quaggavty'.
>   Unpacking quagga-core (1.1.0-1) ...
>   Setting up quagga-core (1.1.0-1) ...
>   dpkg-statoverride: error: an override for '/etc/quagga' already exists; 
> aborting
>   dpkg: error processing package quagga-core (--configure):
>subprocess installed post-installation script returned error exit status 2
>   Errors were encountered while processing:
>quagga-core
>  
> 
> cheers,
> 
> Andreas

Hi Andreas,

Thanks for the bug report. I'll upload a fix ASAP.

-- 
Regards,
Scott.


signature.asc
Description: Digital signature

Bug#830540: This is a known binutils regression

Control: reassign -1 binutils 2.26-9
Control: affects -1 src:gitit
Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=20765

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#820794: marked as pending

2016-12-07 Thread Mathieu Parent

tag 820794 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=68168a5

---
commit 68168a5c57df43425bfe40a69fc28c32a08b63bf
Author: Mathieu Parent 
Date:   Wed Dec 7 21:45:45 2016 +0100

Changelog for previous commit

diff --git a/debian/changelog b/debian/changelog
index 2259e6c..edf9c25 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+samba (2:4.2.14+dfsg-0+deb8u2) UNRELEASED; urgency=medium
+
+  * Fix smbclient compatibility with Windows 10 (Closes: #820794)
+
+ -- Mathieu Parent   Wed, 07 Dec 2016 21:44:28 +0100
+
 samba (2:4.2.14+dfsg-0+deb8u1) jessie; urgency=high
 
   * New upstream release.

Processed: Bug#820794 marked as pending

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

> tag 820794 pending
Bug #820794 {Done: Jelmer Vernooĳ } [smbclient] smbclient: 
"cli_list: Error: unable to parse name from info level 260" with Windows 10 
shares
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 846918

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

> tags 846918 + confirmed
Bug #846918 [jabref] interface opens, but no menus and no action on button 
clicks
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#746005: Still FTBFS with lilypond 2.19-50

2016-12-07 Thread Don Armstrong

On Wed, 07 Dec 2016, Antonio Ospite wrote:

> On Tue, 22 Nov 2016 23:01:16 +0100
> Antonio Ospite  wrote:
> 
> [...]
> > The updated patchset is here:
> > https://ao2.it/tmp/lilypond-guile2/patches_2016-11-22/
> >
> 
> Hi, any update on this?
> 
> BTW now there is also a dev/guile-v2-work branch in the upstream
> lilypond repository with the same changes from above.

Hey; I just need to get some time and integrate the patches and make an
upload.

Alternatively, if you're tired of waiting for me, you could create a
fork of the repo somewhere where I can pull it, and integrate the
patches, and I'll build them and test and then make an upload to
experimental.

Sorry. [$DAYJOB and all of the other stuff I'm working on means I have
limited time to hack on this issue.]

-- 
Don Armstrong  https://www.donarmstrong.com

[I]t's true that some of the most terrible things in the world are
done by people who think, genuinely think, that they're doing it for
the best, especially if there is some god involved.
 -- Terry Pratchett _Snuff_ p185

Bug#847398: mahimahi FTBFS: error: 'const SSL_METHOD* TLSv1_client_method()' is deprecated

Source: mahimahi
Version: 0.95-1
Severity: serious

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

...
g++ -DHAVE_CONFIG_H -I. -I../..  -I./../util -I./../http -I../protobufs 
-std=c++11 -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic -Wall -Wextra 
-Weffc++ -Werror -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o secure_socket.o 
secure_socket.cc
secure_socket.cc: In function 'SSL_CTX* initialize_new_context(SSL_MODE)':
secure_socket.cc:80:51: error: 'const SSL_METHOD* TLSv1_client_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );
   ^~~
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1598:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* 
TLSv1.0 */
 ^
secure_socket.cc:80:71: error: 'const SSL_METHOD* TLSv1_client_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );
   ^
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1598:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* 
TLSv1.0 */
 ^
secure_socket.cc:80:75: error: 'const SSL_METHOD* TLSv1_server_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );
   
^~~
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1597:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* 
TLSv1.0 */
 ^
secure_socket.cc:80:95: error: 'const SSL_METHOD* TLSv1_server_method()' is 
deprecated [-Werror=deprecated-declarations]
 SSL_CTX * ret = SSL_CTX_new( type == CLIENT ? TLSv1_client_method() : 
TLSv1_server_method() );

   ^
In file included from /usr/include/openssl/ct.h:13:0,
 from /usr/include/openssl/ssl.h:61,
 from secure_socket.hh:8,
 from secure_socket.cc:8:
/usr/include/openssl/ssl.h:1597:1: note: declared here
 DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* 
TLSv1.0 */
 ^
cc1plus: all warnings being treated as errors
Makefile:408: recipe for target 'secure_socket.o' failed
make[4]: *** [secure_socket.o] Error 1
make[4]: Leaving directory '/«PKGBUILDDIR»/src/httpserver'
Makefile:378: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

Source: libimager-perl
Version: 1.005+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libimager-perl=sid

...
Test Summary Report
---
t/150-type/030-double.t   (Wstat: 10 Tests: 16 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 136 tests but ran 16.
t/150-type/100-masked.t   (Wstat: 10 Tests: 97 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 244 tests but ran 97.
t/250-draw/100-fill.t (Wstat: 10 Tests: 39 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 165 tests but ran 39.
t/250-draw/200-compose.t  (Wstat: 10 Tests: 59 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 120 tests but ran 59.
t/300-transform/010-scale.t   (Wstat: 10 Tests: 9 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 232 tests but ran 9.
t/300-transform/020-combine.t (Wstat: 10 Tests: 27 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 31 tests but ran 27.
t/300-transform/030-copyflip.t (Wstat: 10 Tests: 9 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 95 tests but ran 9.
t/300-transform/050-convert.t (Wstat: 10 Tests: 26 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 31 tests but ran 26.
t/400-filter/010-filters.t(Wstat: 10 Tests: 36 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 124 tests but ran 36.
t/400-filter/020-autolevels.t (Wstat: 10 Tests: 2 Failed: 0)
  Non-zero wait status: 10
  Parse errors: Bad plan.  You planned 4 tests but ran 2.
Files=66, Tests=3818, 409 wallclock secs ( 2.46 usr  0.40 sys + 87.20 cusr 
313.36 csys = 403.42 CPU)
Result: FAIL
Failed 10/66 test programs. 0/3818 subtests failed.
Makefile:1584: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255

Bug#847396: ignition-math2 FTBFS: unit tests fail on all 32bit architectures

Source: ignition-math2
Version: 2.5.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=ignition-math2=sid

Building seems to fail on all 32bit release architectures with one of:

The following tests FAILED:
  9 - UNIT_Helpers_TEST (Timeout)

or

The following tests FAILED:
  3 - UNIT_Box_TEST (Failed)

Processed: Bug#842443 tagged as pending

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

> tag 842443 pending
Bug #842443 [abiword] abiword displays documents as black on black with GTK 3.22
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#842443: tagged as pending

2016-12-07 Thread Jeremy Bicha

tag 842443 pending
--

We believe that the bug #842443 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/abiword.git/diff/?id=245de8b

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 245de8b8964f670ba359b3f3d1b81f7a8175f137
Author: Jeremy Bicha 
Date:   Wed Dec 7 14:16:23 2016 -0500

Add upstream patch to fix black background with GTK 3.22

Closes: #842443
LP: #1637893

Bug#842443: Abiword: patch available

2016-12-07 Thread Jeremy Bicha

On Wed, Dec 7, 2016 at 12:09 PM, Santiago Ruano Rincón
 wrote:
> Upstream proposes a patch to fix this:

Santiago, I confirm that the patch fixes this bug and am doing an
upload to Debian now. Thank you!

Jeremy

Bug#847395: bugwarrior build-depends on removed python-twiggy

Source: bugwarrior
Version: 1.4.0+git2016090101-1
Severity: serious

bugwarrior build-depends on python-twiggy,
which was removed from unstable (see #846831).

Bug#847369: Error: Cannot find module 'requirejs' (missing package.json)

2016-12-07 Thread GCS

Hi Pirate,

On Wed, Dec 7, 2016 at 4:57 PM, Pirate Praveen  wrote:
> The error I get when trying to use it from grunt-contrib-requirejs
> (available in
> git+ssh://git.debian.org/git/pkg-javascript/node-grunt-contrib-requirejs.git)
> is given below
>
> node-grunt-contrib-requirejs$ grunt --verbose
> Initializing
> Command-line options: --verbose
>
> Reading "Gruntfile.js" Gruntfile...OK
>
> Registering Gruntfile tasks.
> Initializing config...OK
>
> Registering "tasks" tasks.
> Loading "requirejs.js" tasks...ERROR
>>> Error: Cannot find module 'requirejs'
 Package is upadted and this is fixed.

> Also consider using pkg-javascript alioth repo for this package (there
> is a repo there, but it is outdated), so we can fix these kind of issues
> faster.
 Thanks, will consider it. I try to act fast, package is going to be
uploaded soon.

Regards,
Laszlo/GCS

Bug#847343: Same here

2016-12-07 Thread Kai Lüke

Hm, also no complaints or error messages with dracut instead of
initramfs-tools.
And plymouth is not installed.

Processed: Re: Bug#847172: sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128)

Processing control commands:

> clone -1 -2 -3
Bug #847172 [src:sagenb-export] sagenb-export: FTBFS: UnicodeEncodeError: 
'ascii' codec can't encode characters in position 41-42: ordinal not in 
range(128)
Bug 847172 cloned as bugs 847393-847394
> reassign -2 src:nbformat
Bug #847393 [src:sagenb-export] sagenb-export: FTBFS: UnicodeEncodeError: 
'ascii' codec can't encode characters in position 41-42: ordinal not in 
range(128)
Bug reassigned from package 'src:sagenb-export' to 'src:nbformat'.
No longer marked as found in versions sagenb-export/2.0-1.
Ignoring request to alter fixed versions of bug #847393 to the same values 
previously set
> retitle -2 Doesn't support non-UTF-8 filepaths
Bug #847393 [src:nbformat] sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' 
codec can't encode characters in position 41-42: ordinal not in range(128)
Changed Bug title to 'Doesn't support non-UTF-8 filepaths' from 'sagenb-export: 
FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 
41-42: ordinal not in range(128)'.
> severity -2 normal
Bug #847393 [src:nbformat] Doesn't support non-UTF-8 filepaths
Severity set to 'normal' from 'serious'
> tags -2 + upstream
Bug #847393 [src:nbformat] Doesn't support non-UTF-8 filepaths
Added tag(s) upstream.
> forwarded -2 https://github.com/jupyter/nbformat/issues/76
Bug #847393 [src:nbformat] Doesn't support non-UTF-8 filepaths
Set Bug forwarded-to-address to 'https://github.com/jupyter/nbformat/issues/76'.
> retitle -3 Fails when LC_CTYPE is not explicitly UTF-8
Bug #847394 [src:sagenb-export] sagenb-export: FTBFS: UnicodeEncodeError: 
'ascii' codec can't encode characters in position 41-42: ordinal not in 
range(128)
Changed Bug title to 'Fails when LC_CTYPE is not explicitly UTF-8' from 
'sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode 
characters in position 41-42: ordinal not in range(128)'.
> severity -3 normal
Bug #847394 [src:sagenb-export] Fails when LC_CTYPE is not explicitly UTF-8
Severity set to 'normal' from 'serious'
> tags -3 + upstream
Bug #847394 [src:sagenb-export] Fails when LC_CTYPE is not explicitly UTF-8
Added tag(s) upstream.
> forwarded -3 https://github.com/vbraun/ExportSageNB/issues/6
Bug #847394 [src:sagenb-export] Fails when LC_CTYPE is not explicitly UTF-8
Set Bug forwarded-to-address to 
'https://github.com/vbraun/ExportSageNB/issues/6'.

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

Bug#847172: sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128)

2016-12-07 Thread Ximin Luo

Control: clone -1 -2 -3
Control: reassign -2 src:nbformat
Control: retitle -2 Doesn't support non-UTF-8 filepaths
Control: severity -2 normal
Control: tags -2 + upstream
Control: forwarded -2 https://github.com/jupyter/nbformat/issues/76
Control: retitle -3 Fails when LC_CTYPE is not explicitly UTF-8
Control: severity -3 normal
Control: tags -3 + upstream
Control: forwarded -3 https://github.com/vbraun/ExportSageNB/issues/6

Instead of patching 2 Debian packages to fix this issue properly, and risking 
the upstreams picking different solutions and having to re-patch those 2 again, 
I will wait for the upstreams to pick the solutions I proposed.

In the meantime, I will work around this FTBFS by overriding LC_CTYPE specially 
for the tests.

X

Ximin Luo:
> I think I narrowed it down, could you try the build again with 
> LC_CTYPE="C.UTF-8" and see how it works?
> 
> X
> 
> Chris Lamb:
>> Ximin Luo wrote:
>>
>>> I can't reproduce this, even when setting the locale to various non-UTF
>>> values
>>
>> Not sure why you were trying this specifically; I don't do anything special
>> by default — or I would mention it! — and build under en_GB.UTF-8 etc. (See
>> the top of the full build log).
>>
>> If it "helps", I can still reproduce this on the today's sid.
>>

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

Bug#834800: libkavorka-perl: depends on libdata-alias-perl, broken with Perl 5.24

2016-12-07 Thread Daniel Dehennin

Hello,

I made an upstream pull request[1] to use the core refaliasing.

Maybe the Debian package could drop the Data::Alias dependency by
integrating this patch?

Regards.

Footnotes: 
[1]  https://github.com/tobyink/p5-kavorka/pull/19

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF


signature.asc
Description: PGP signature

Bug#828362: marked as done (kannel needs binNMU when OpenSSL 1.1.0 enters unstable)

Your message dated Wed, 7 Dec 2016 21:37:52 +0200
with message-id <20161207193752.unesivue573d7...@bunk.spdns.de>
and subject line The 1.4.4-4 upload is as good as a binNMU
has caused the Debian Bug report #828362,
regarding kannel needs binNMU when OpenSSL 1.1.0 enters unstable
to be marked as done.

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

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

--
828362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kannel-sqlbox
Version: 0.7.2-4
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/kannel-sqlbox_0.7.2-4_amd64-20160529-1433

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

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

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

Kurt
--- End Message ---
--- Begin Message ---
Version: 1.4.4-4

The 1.4.4-4 upload is as good as a binNMU.

cu
Adrian

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---

Processed: Proper syntax for version tracking (BTS syntax is confusing)

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

> fixed 846766 1:1.4.4+snapshot20161117-4
Bug #846766 {Done: Arturo Borrero Gonzalez } 
[src:conntrack-tools] conntrack-tools: FTBFS: read_config_lex.l:25:28: fatal 
error: read_config_yy.h: No such file or directory
Marked as fixed in versions conntrack-tools/1:1.4.4+snapshot20161117-4.
> thanks
Stopping processing here.

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

Bug#837845: marked as done (libwnck: FTBFS due to undeclared build dependencies)

Your message dated Wed, 07 Dec 2016 19:19:23 +
with message-id 
and subject line Bug#837845: fixed in libwnck 2.30.7-5.1
has caused the Debian Bug report #837845,
regarding libwnck: FTBFS due to undeclared build dependencies
to be marked as done.

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

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


-- 
837845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libwnck
Version: 2.30.7-5
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package libwnck declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and libwnck
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/libwnck.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   â Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   â Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   â Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   â Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   â Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   â Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: libwnck
Source-Version: 2.30.7-5.1

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

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

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

Debian distribution maintenance software
pp.
Andreas Moog  (supplier of updated libwnck package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Dec 2016 20:27:41 +0100
Source: libwnck
Binary: libwnck22 libwnck-dev libwnck-common libwnck-dbg libwnck-doc 
gir1.2-wnck-1.0
Architecture: source
Version: 2.30.7-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian MATE Packaging Team 
Changed-By: Andreas Moog 
Description:
 gir1.2-wnck-1.0 - GObject introspection data for the WNCK library
 libwnck-common - Window Navigator Construction Kit - common files
 libwnck-dbg - Window Navigator Construction Kit - debugging symbols
 libwnck-dev - Window Navigator Construction Kit - development files
 libwnck-doc - Window Navigator Construction Kit - documentation files
 libwnck22  - Window Navigator Construction Kit - runtime files
Closes: 837845
Changes:
 libwnck (2.30.7-5.1) unstable;

Bug#844819: marked as done (libwnck: FTBFS: /<>/./configure: line 3052: GNOME_MAINTAINER_MODE_DEFINES: command not found)

Your message dated Wed, 07 Dec 2016 19:19:23 +
with message-id 
and subject line Bug#837845: fixed in libwnck 2.30.7-5.1
has caused the Debian Bug report #837845,
regarding libwnck: FTBFS: /<>/./configure: line 3052: 
GNOME_MAINTAINER_MODE_DEFINES: command not found
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> diff: debian/copyright_hints: No such file or directory
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> configure.ac:40: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4158: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5233: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:40: the top level
> configure.ac:40: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4158: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5233: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:40: the top level
> configure.ac:40: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> m4/libtool.m4:4158: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5233: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:40: the top level
> configure.ac:40: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
> in body
> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
> ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
> m4/libtool.m4:4158: _LT_LINKER_SHLIBS is expanded from...
> m4/libtool.m4:5233: _LT_LANG_C_CONFIG is expanded from...
> m4/libtool.m4:138: _LT_SETUP is expanded from...
> m4/libtool.m4:67: LT_INIT is expanded from...
> m4/libtool.m4:103: AM_PROG_LIBTOOL is expanded from...
> configure.ac:40: the top level
> configure.ac:40: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call

Processed: Correct the found version (this time with correct syntax

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

> notfound 846385 8:6.9.9.6+dfsg-1
Bug #846385 [imagemagick] imagemagick: Potential ABI break upstream (without 
SONAME change)
There is no source info for the package 'imagemagick' at version 
'8:6.9.9.6+dfsg-1' with architecture ''
Unable to make a source version for version '8:6.9.9.6+dfsg-1'
No longer marked as found in versions 8:6.9.9.6+dfsg-1.
> found 846385 8:6.9.6.6+dfsg-1
Bug #846385 [imagemagick] imagemagick: Potential ABI break upstream (without 
SONAME change)
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> thanks
Stopping processing here.

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

Bug#818393: marked as done (cpm: FTBFS: cdk.h not found)

Your message dated Wed, 07 Dec 2016 19:03:19 +
with message-id 
and subject line Bug#818393: fixed in cpm 0.32-1.2
has caused the Debian Bug report #818393,
regarding cpm: FTBFS: cdk.h not found
to be marked as done.

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

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


-- 
818393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpm
Version: 0.32-1.1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> checking for compress in -lz... yes
> checking for gettext in -lintl... no
> : using CRACKLIB_DICTPATH=/var/cache/cracklib/cracklib_dict.
> : error: cdk.h not found, try 
> --with-cdk-dir=/path/to/dir/containing/include/cdk
>   "tail -v -n +0 config.log"
> ==> config.log <==
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> It was created by cpm  0.32, which was
> generated by GNU Autoconf 2.69.  Invocation command line was
> 
>   $ ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=${prefix}/include --mandir=${prefix}/share/man 
> --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking 
> --with-cracklib-dict=/var/cache/cracklib/cracklib_dict
> 
> ## - ##
> ## Platform. ##
> ## - ##
> 
> hostname = dl580gen9-02
> uname -m = x86_64
> uname -r = 4.4.1-3-amd64-hlinux
> uname -s = Linux
> uname -v = #hlinux1 SMP Thu Feb 11 16:17:40 UTC 2016
> 
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
> 
> /bin/arch  = unknown
> /usr/bin/arch -k   = unknown
> /usr/convex/getsysinfo = unknown
> /usr/bin/hostinfo  = unknown
> /bin/machine   = unknown
> /usr/bin/oslevel   = unknown
> /bin/universe  = unknown
> 
> PATH: /usr/local/sbin
> PATH: /usr/local/bin
> PATH: /usr/sbin
> PATH: /usr/bin
> PATH: /sbin
> PATH: /bin
> PATH: /usr/games
> 
> 
> ## --- ##
> ## Core tests. ##
> ## --- ##
> 
> :2231: checking for gcc
> :2247: found /usr/bin/gcc
> :2258: result: gcc
> :2487: checking for C compiler version
> :2496: gcc --version >&5
> gcc (Debian 5.3.1-11) 5.3.1 20160307
> Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> :2507: $? = 0
> :2496: gcc -v >&5
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Debian 5.3.1-11' 
> --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs 
> --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
> --program-suffix=-5 --enable-shared --enable-linker-build-id 
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
> --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object 
> --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
> --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home 
> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 
> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 
> --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
> --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-
> abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
> --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu 
> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 5.3.1 20160307 (Debian 5.3.1-11) 
> :2507: $? = 0
> :2496: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> :2507: $? = 1
> :2496: gcc -qversion >&5
> gcc: error: unrecognized command line option '-qversion'
> gcc: fatal error: no input files
> compilation terminated.
> :2507: $? = 1
> :2527: checking whether the C compiler works
> :2549: gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time

Processed: Add an affects

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

> affects 845354 nemo
Bug #845354 [cinnamon] [nemo] Nemo does not mounts partition
Added indication that 845354 affects nemo
> thanks
Stopping processing here.

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

Bug#847172: sagenb-export: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode characters in position 41-42: ordinal not in range(128)

2016-12-07 Thread Ximin Luo

I think I narrowed it down, could you try the build again with 
LC_CTYPE="C.UTF-8" and see how it works?

X

Chris Lamb:
> Ximin Luo wrote:
> 
>> I can't reproduce this, even when setting the locale to various non-UTF
>> values
> 
> Not sure why you were trying this specifically; I don't do anything special
> by default — or I would mention it! — and build under en_GB.UTF-8 etc. (See
> the top of the full build log).
> 
> If it "helps", I can still reproduce this on the today's sid.
> 
> 
> Regards,
> 

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

Bug#846774: marked as done (libp11: FTBFS: eng_front.c:71:25: fatal error: openssl/dso.h: No such file or directory)

Your message dated Wed, 07 Dec 2016 18:06:22 +
with message-id 
and subject line Bug#846774: fixed in libp11 0.4.3-1
has caused the Debian Bug report #846774,
regarding libp11: FTBFS: eng_front.c:71:25: fatal error: openssl/dso.h: No such 
file or directory
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
> -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o pkcs11_la-eng_front.lo `test -f 'eng_front.c' 
> || echo './'`eng_front.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c eng_front.c  -fPIC -DPIC -o 
> .libs/pkcs11_la-eng_front.o
> eng_front.c:71:25: fatal error: openssl/dso.h: No such file or directory
>  #include 
>  ^
> compilation terminated.
> Makefile:676: recipe for target 'pkcs11_la-eng_front.lo' failed
> make[3]: *** [pkcs11_la-eng_front.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/libp11_0.4.2-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Eric Dorland  (supplier of updated libp11 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Dec 2016 00:16:12 -0500
Source: libp11
Binary: libp11-dev libp11-2 libengine-pkcs11-openssl
Architecture: source amd64
Version: 0.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSC Maintainers 
Changed-By: Eric Dorland 
Description:
 libengine-pkcs11-openssl - OpenSSL engine for PKCS#11 modules
 libp11-2   - pkcs#11 convenience library
 libp11-dev - pkcs#11 convenience library - development files
Closes: 846774
Changes:
 libp11 (0.4.3-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #846774)
   * debian/patches/0001-Add-enginesexecdir-use-it-instead-of-enginesdir.patch:
 Drop upstreamed enginesexecdir patch.
   * debian/control: Switch back to libssl 1.0 for the moment.
   * debian/compat, debian/control, debian/rules: Switch to debhelper 10.
   * debian/libp11-2.symbols: Add LIBP11_2 symbol versions.
Checksums-Sha1:
 a4601b713e2d9efb3cd74bc8c9d3bd4c4d59ea8c 2097 libp11_0.4.3-1.dsc
 2eafcd80fcb47b4dc5be8f77993246a34746c7f6 108345 libp11_0.4.3.orig.tar.gz
 71ca410280328d29119182b1a75ea9c981d595fd 6988 libp11_0.4.3-1.debian.tar.xz
 5d1dba9ace1a8cac45e625f46b1a760e07688828 121658 
libengine-pkcs11-openssl-dbgsym_0.4.3-1_amd64.deb
 395118a8655b820a47b705c60a513045da711eb8 30006 
libengine-pkcs11-openssl_0.4.3-1_amd64.deb
 8f0eafb6b9681cb123ee28d0fec279f1c8e5b958 95344 
libp11-2-dbgsym_0.4.3-1_amd64.deb
 b66145bd2d982576a172459436bba987f491fead 22892 libp11-2_0.4.3-1_amd64.deb
 6dcb94514761f57435a4dfd2c8e01e1e3c61adbd 39476 libp11-dev_0.4.3-1_amd64.deb
 3115b4630c554ba2bffb17cc1f399d06164f66fe 6023 libp11_0.4.3-1_amd64.buildinfo
Checksums-Sha256:

Bug#845335: bzr issue

2016-12-07 Thread Ben Dooks

The "bzr: ERROR: exceptions.TypeError: first argument must be string or
compiled pattern" is still there after updating.

bzr is already the newest version (2.7.0+bzr6619-1).

-- 
Ben Dooks, http://www.fluff.org/ben/ bjdo...@googlemail.com

Bug#846774: marked as pending

2016-12-07 Thread Eric Dorland

tag 846774 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-opensc/libp11.git;a=commitdiff;h=d970edf

---
commit d970edfba87abbd49506aa2f2f6b4ab2c87d9abf
Author: Eric Dorland 
Date:   Tue Dec 6 00:01:41 2016 -0500

New upstream release

Closes: 846774

diff --git a/debian/changelog b/debian/changelog
index 86eb1e7..78c2e45 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libp11 (0.4.3-1) unstable; urgency=medium
+
+  * New upstream release. (Closes: #846774)
+
+ --
+
 libp11 (0.4.2-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#846774 marked as pending

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

> tag 846774 pending
Bug #846774 [src:libp11] libp11: FTBFS: eng_front.c:71:25: fatal error: 
openssl/dso.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#846916: marked as done (provide jquery2: jquery3 breaks diaspora)

Your message dated Wed, 7 Dec 2016 23:15:07 +0530
with message-id 
and subject line fixed in 4.2.1-2
has caused the Debian Bug report #846916,
regarding provide jquery2: jquery3 breaks diaspora
to be marked as done.

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

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


-- 
846916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable

Hi,

this issue happens on a vanilla installation of gitlab on a Debian
Stretch system. Since the problem occurs without any custom
configuration from my side, I deemed this issue to happen for all users
of the gitlab package and thus the severity.

Essentially, the dropdown menus stopped working. This includes:

 - the user menu dropdown on the upper-right
 - the project settings dropdown on the right below
 - the repository clone method dropdown
 - the repository dropdown on the upper-left
 - the download option dropdown
 - the notification dropdown

I judge these elements being dysfunctional to render the package
unusable.

To allow you to investigate the problem, I packed up the rootfs of the
machine I installed this onto. This rootfs is freshly generated and will
not be used in production, so there are no secrets in it.

The only gitlab user is root with the password 12345678.

You can also convince yourself of the problem by looking at this system
running live. For this, just enter the following into your /etc/hosts:

62.75.219.30 gitlab.mister-muffin.de

And then browse to https://gitlab.mister-muffin.de

You can log into the gitlab web interface with the credentials given
above.

For log and configuration files, list of installed packages etc, please
consult the tarball of the whole system here:

https://mister-muffin.de/gitlab_vanilla.tar.xz

To create this setup, I ran in a fresh chroot:

apt-get install --no-install-recommends gitlab msmtp-mta

No further configuration was carried out from my side. I used msmtp-mta
to prevent the bloat of postfix as a provider of mail-transport-agent. I
expect this choice to have no influence on the problem at hand.

I suspected that there might be a problem because I installed with
--no-install-recommends but running the following resulted in the same
behaviour:

apt-get install --install-recommends gitlab msmtp-mta certbot-

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
fixed 846916 4.2.1-2



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: fixed in 4.2.1-2

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

> fixed 846916 4.2.1-2
Bug #846916 [ruby-jquery-rails] provide jquery2: jquery3 breaks diaspora
Marked as fixed in versions ruby-jquery-rails/4.2.1-2.
>
End of message, stopping processing here.

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

Bug#842753: marked as done (FTBFS: test failures)

Your message dated Wed, 07 Dec 2016 17:35:30 +
with message-id 
and subject line Bug#842753: fixed in libnet-sip-perl 0.807-1
has caused the Debian Bug report #842753,
regarding FTBFS: test failures
to be marked as done.

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

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


-- 
842753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-sip-perl
Version: 0.690-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

0.690-1 fails to build all over the place with more or less failing
tests:

https://buildd.debian.org/status/fetch.php?pkg=libnet-sip-perl=all=0.690-1=1477852334

https://ci.debian.net/packages/libn/libnet-sip-perl/unstable/amd64/
(ok, doesn't look package specific)

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libnet-sip-perl_0.690-1.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/libnet-sip-perl_0.690-1.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.690-1.rbuild.log


Fascinating that it built for me yesterday …


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYF++FXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG5S8P/0yC0nHsTDRSYT4yY4Bd72k/
sGK3SROoWLZssxcQibtwAYiBCTkbDZ4mJwHMmTMOlLyu3jlUNect3cpctL1Cm1rS
jXDo+jPII2QoWd3QMu7no0fbjsUZdznxTxzsZvLOQKF2DsRqFx4vK8p5k5glzLn3
/nCCKdcxPhTVs7kzcA4v2AQvWp+VMDLQSB4LByDZmHMUhu5V80TLbAzNFUP2/o2a
d7XQncuj9E9LeMUoTinFqfEkG+ueoO70F7wYoOB3Hr54qOxUb+RYmbVK2a9jkeNH
vdcHCVIUig6lk9CH/fljCzv4VynzEilOtNlcQANlLORg6ACIpHfUksLCLJtys0xY
j4lrZ8ZWxpguKmdqcNLSeGcdWpAq9aDndMm01X1WC1TDOscUajg/lFA0PS3Ar+bz
gIf4edMgsdEWQlM/80WvtX3LM27tVvo8CPzERXR2VHidVMlDGG7YEBSB4peF18N9
IQHOccGFl7dj2fLoP5TQ3pdeGHYkNMm+3XByGPcSircezur5Qta/XI6+m8ZOZlkK
rdHMYGfGlqfApUCbOuv797G1yJirhoD6mRtf20WE29beB/wajYkGQTTtX9ZtEvhJ
c0oKbRJvHmadrRE55CHhGrLiQmMebL7sRkk4kkoUzYgzsMlUsn7ngfOmcn9gT5wc
SFY4lCtnMYnVQaGX0GaC
=nZRb
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libnet-sip-perl
Source-Version: 0.807-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnet-sip-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2016 18:10:46 +0100
Source: libnet-sip-perl
Binary: libnet-sip-perl
Architecture: source
Version: 0.807-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 842753
Description: 
 libnet-sip-perl - framework for SIP modules
Changes:
 libnet-sip-perl (0.807-1) unstable; urgency=medium
 .
   * Import upstream versions 0.806, 0.807.
 Fixes "FTBFS: test failures" (Closes: #842753)
   * Drop spelling.patch, applied upstream.
Checksums-Sha1: 
 cbaedf3e6c9b93bae1fbf81347e03987f47d8175 2463 libnet-sip-perl_0.807-1.dsc
 82a433b47eb47d502e1f3161160b2395a37eb3f3 198353 
libnet-sip-perl_0.807.orig.tar.gz
 3d4ae27c22c7b7a0ebe3c65c7b3325a2f2e7718e 6224 
libnet-sip-perl_0.807-1.debian.tar.xz
Checksums-Sha256: 
 0291ff0bc0ef6cd8323864a2b4b133b46b61d1ddea8a6ac76694a017e041ab8e 2463 
libnet-sip-perl_0.807-1.dsc
 99b6ea255df6da37d5c61ff18000dc6e07cc683c5c1c48352faf997f5e9b926c 198353 
libnet-sip-perl_0.807.orig.tar.gz
 4687c4dcf34afd2ae6867b19368e479c7ae6b270a47f5b9d5d56757c73210243 6224 
libnet-sip-perl_0.807-1.debian.tar.xz
Files: 
 af1d877aa60ddcad31983443920de5f1 2463 perl optional libnet-sip-perl_0.807-1.dsc
 a4527536822c034fef771e0d79360f00 198353 perl optional 
libnet-sip-perl_0.807.orig.tar.gz
 c3cf77daf20c3bdb8482a95747177ff1 6224 perl optional 
libnet-sip-perl_0.807-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: Re: Bug#842001: weston: GTK-3.22 apps fail to run under native wayland compositor

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

> notfound 842001 1.11-1
Bug #842001 [weston] weston: GTK-3.22 apps fail to run under native wayland 
compositor
There is no source info for the package 'weston' at version '1.11-1' with 
architecture ''
Unable to make a source version for version '1.11-1'
No longer marked as found in versions 1.11-1.
> found 842001 1.11.0-1
Bug #842001 [weston] weston: GTK-3.22 apps fail to run under native wayland 
compositor
Ignoring request to alter found versions of bug #842001 to the same values 
previously set
> fixed 842001 1.11.94-1
Bug #842001 [weston] weston: GTK-3.22 apps fail to run under native wayland 
compositor
Marked as fixed in versions weston/1.11.94-1.
> close 842001
Bug #842001 [weston] weston: GTK-3.22 apps fail to run under native wayland 
compositor
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

2016-12-07 Thread Hilmar Preuße


Am 06.10.2016 um 22:20 tastete Mattia Rizzolo:

On Thu, Oct 06, 2016 at 06:55:22PM +0200, Hilmar Preuße wrote:


Hi,


I'm not a DD (yet), I can't do upload.

I know we have DD's on that list: could anybody finalize the changelog
in git and then upload the current git state?


I can sponsor the upload if you want, but before I'd like to see more
changes done, meaning:

9) now that you're like this you can reinstate hardening, that you
   removed but not replaced, so just put
   export DEB_BUILD_MAINT_OPTIONS = hardening=+all
   on top, it should just work after the changs above

>
I did not remove any hardening implementation. It is just there as 
before: AFAICT the following code should bring them in:

./configure $(shell dpkg-buildflags --export=configure)
I just removed the test, which checked the presence of the hardening flags.

I'm working on your list to go to compat level 9 and dh_auto_configure.

H.
--
#206401 http://counter.li.org

Bug#842001: weston: GTK-3.22 apps fail to run under native wayland compositor

2016-12-07 Thread Emilio Pozuelo Monfort

notfound 842001 1.11-1
found 842001 1.11.0-1
fixed 842001 1.11.94-1
close 842001
thanks

On 25/10/16 09:22, Telnet wrote:
> Package: weston
> Version: 1.11-1

Wrong version.

> This bug report is related to #841735
> 
> Weston 1.12 includes support for new xdg-shell-v6 unstable protocol, which 
> is required to run GTK-3.22 applications using wayland compositor.
> 
> Without support to xdg-shell-v6, GTK-3.22 applications fail to run under 
> wayland and will try to run under xwayland.
> 
> On currently packaged weston (1.11), GTK-3.22 applications emit warning 
> about missing xdg_shell interface and try to run under xwayland. Here is 
> output from gnome-terminal when launched inside currently packaged weston 
> 1.11.
> 
> ```
> (gnome-terminal:346): Gdk-WARNING **: wayland compositor does not support 
> xdg_shell interface, not using Wayland display.
> ```
> 
> In other word, to make GTK-3.22 applications work under wayland, weston 
> has to be upgraded to version 1.12.

This is fixed in experimental. I'm looking at updating weston to 1.12 and will
upload that to unstable.

Cheers,
Emilio

Bug#844831: marked as done (crash: FTBFS: stdlib.h:427:14: error: conflicting types for 'malloc')