Processed: tk-brief: diff for NMU version 5.10-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 223915 + patch
Bug #223915 [src:tk-brief] tk-brief: Please don't package it as a native package
Bug #733433 [src:tk-brief] tk-brief: FTBFS: dpkg-source: error: can't build 
with source format '3.0 (native)': native package version may not have a 
revision
Added tag(s) patch.
Added tag(s) patch.
> tags 223915 + pending
Bug #223915 [src:tk-brief] tk-brief: Please don't package it as a native package
Bug #733433 [src:tk-brief] tk-brief: FTBFS: dpkg-source: error: can't build 
with source format '3.0 (native)': native package version may not have a 
revision
Added tag(s) pending.
Added tag(s) pending.
> tags 249196 + pending
Bug #249196 [tk-brief] tk-brief: New upstream version available
Added tag(s) pending.

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

Bug#223915: tk-brief: diff for NMU version 5.10-0.1

[Christoph Biedl]

Control: tags 223915 + patch
Control: tags 223915 + pending
Control: tags 249196 + pending

Dear maintainer,

find attached the debdiff (limited to debian/ for an NMU for tk-brief
(versioned as 5.10-0.1), upload to DELAYED/0[*) will follow in a few hours.
Please feel free to tell me if I should delay it longer.

It also switches to the latest upstream version, removes some cruft
from debian/ and makes a few switches in debian/rules.

Regards,

Christoph

[*] For way more than seven days without activity and no indication
that a fix is in progress: 0 daysControl: tags 223915 + patch

Binary files /tmp/XYNCc1rzpn/tk-brief-5.9/dante-article_german.ps.gz and 
/tmp/rjgcX_KHdV/tk-brief-5.10/dante-article_german.ps.gz differ
Binary files /tmp/XYNCc1rzpn/tk-brief-5.9/dante-article-german.ps.gz and 
/tmp/rjgcX_KHdV/tk-brief-5.10/dante-article-german.ps.gz differ
diff -Nru tk-brief-5.9/debian/changelog tk-brief-5.10/debian/changelog
--- tk-brief-5.9/debian/changelog   2010-05-11 06:02:33.0 +0200
+++ tk-brief-5.10/debian/changelog  2017-01-18 07:31:01.0 +0100
@@ -1,3 +1,11 @@
+tk-brief (5.10-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream version. Closes: #249196
+  * Build as a package with orig tarball. Closes: #223915
+
+ -- Christoph Biedl   Wed, 18 Jan 2017 
07:31:01 +0100
+
 tk-brief (5.9-1.1) unstable; urgency=low
 
   [Jari Aalto]
diff -Nru tk-brief-5.9/debian/debhelper.log tk-brief-5.10/debian/debhelper.log
--- tk-brief-5.9/debian/debhelper.log   2010-05-02 00:54:52.0 +0200
+++ tk-brief-5.10/debian/debhelper.log  1970-01-01 01:00:00.0 +0100
@@ -1,16 +0,0 @@
-dh_installdirs
-dh_install
-dh_installman
-dh_installman
-dh_installdocs
-dh_installexamples
-dh_installmenu
-dh_installchangelogs
-dh_link
-dh_compress
-dh_fixperms
-dh_installdeb
-dh_gencontrol
-dh_md5sums
-dh_builddeb
-dh_installdirs
diff -Nru tk-brief-5.9/debian/docs tk-brief-5.10/debian/docs
--- tk-brief-5.9/debian/docs2003-10-25 22:15:52.0 +0200
+++ tk-brief-5.10/debian/docs   2017-01-18 07:24:24.0 +0100
@@ -1 +1 @@
-dante-article_german.ps.gz
+dante99.ps.gz
diff -Nru tk-brief-5.9/debian/rules tk-brief-5.10/debian/rules
--- tk-brief-5.9/debian/rules   2010-05-02 01:04:46.0 +0200
+++ tk-brief-5.10/debian/rules  2017-01-18 07:24:24.0 +0100
@@ -12,7 +12,9 @@
 
touch configure-stamp
 
-build: configure-stamp build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
dh_testdir
 
@@ -36,9 +38,9 @@
dh_installdirs
dh_install tk_Brief usr/bin
mv debian/tk-brief/usr/bin/tk_Brief debian/tk-brief/usr/bin/tk-brief
-   dh_installman debian/tk_Brief-en.1
-   mv debian/tk-brief/usr/share/man/man1/tk_Brief-en.1 
debian/tk-brief/usr/share/man/man1/tk-brief.1
-   dh_installman --language=de tk_Brief.1
+   dh_installman tk-brief-en.1
+   mv debian/tk-brief/usr/share/man/man1/tk-brief-en.1 
debian/tk-brief/usr/share/man/man1/tk-brief.1
+   dh_installman --language=de tk-brief.1
 
 
 # Build architecture-dependent files here.
diff -Nru tk-brief-5.9/debian/source/format tk-brief-5.10/debian/source/format
--- tk-brief-5.9/debian/source/format   2010-05-11 05:59:22.0 +0200
+++ tk-brief-5.10/debian/source/format  2017-01-18 07:22:46.0 +0100
@@ -1 +1 @@
-3.0 (native)
+3.0 (quilt)
diff -Nru tk-brief-5.9/debian/tk_Brief-en.1 tk-brief-5.10/debian/tk_Brief-en.1
--- tk-brief-5.9/debian/tk_Brief-en.1   2010-05-02 01:16:02.0 +0200
+++ tk-brief-5.10/debian/tk_Brief-en.1  1970-01-01 01:00:00.0 +0100
@@ -1,217 +0,0 @@
-'\" t
-.\" Manual page created with latex2man on Mon Nov 13 07:12:56 CET 2000
-.\" NOTE: This file is generated, DO NOT EDIT.
-.TH "TK\\_BRIEF" "1" "13
- November 2000" "tk_Brief "
-.SH NAME
-tk\-Brief is a graphical user interface for writing single or multiple letters 
-with latex. Even begginers are able to use it without a long time of 
-learning. 
-.PP
-.SH
-SYNOPSIS
-tk_Brief
-[
-.BI "\-a" " an"
-]
-[
-.BI "\-N" " name"
-]
-[
-.BI "\-str" " street"
-]
-[
-.BI "\-o" " city"
-]
-[
-.BI "\-dir" " directory"
-]
-[
-.BI "\-fax" " faxnumber"
-]
-[
-.B "\-h"
-]
-[
-.B "filename"
-]
-.PP
-.SH
-DESCRIPTION
-tk_Brief
-generates a .tex file using a .text 
-file and the input from the input fields. There are different letter styles 
-inplemented, e.g. g\-brief. Although it was originally written for the german 
letter 
-norm, it can create an english or durch letter style. The labels can occur in 
English 
-of Dutch language. tk_Brief
-is written in Tcl/Tk and therefor available 
-on many platforms. 
-.PP
-.SH
-OPTIONS
-.TP
-.BR "\-h"
-Short Help for tk_Brief.
-.TP
-.BI "\-a" " to"
-Commandline option for 'to' field. 
-.TP
-.BI "\-N" " name"
-Commandline option for 'name field. 
-.TP
-.BI "\-str" " street"
-Commandline option dor 'street' field. 
-.TP
-.BI "\-o" " city"
-Commandline 

Processed: tk-brief: diff for NMU version 5.10-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 223915 + patch
Bug #223915 [src:tk-brief] tk-brief: Please don't package it as a native package
Bug #733433 [src:tk-brief] tk-brief: FTBFS: dpkg-source: error: can't build 
with source format '3.0 (native)': native package version may not have a 
revision
Ignoring request to alter tags of bug #223915 to the same tags previously set
Ignoring request to alter tags of bug #733433 to the same tags previously set
> tags 223915 + pending
Bug #223915 [src:tk-brief] tk-brief: Please don't package it as a native package
Bug #733433 [src:tk-brief] tk-brief: FTBFS: dpkg-source: error: can't build 
with source format '3.0 (native)': native package version may not have a 
revision
Ignoring request to alter tags of bug #223915 to the same tags previously set
Ignoring request to alter tags of bug #733433 to the same tags previously set
> tags 249196 + pending
Bug #249196 [tk-brief] tk-brief: New upstream version available
Ignoring request to alter tags of bug #249196 to the same tags previously set

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

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Paul Wise]

On Wed, Jan 18, 2017 at 4:49 AM, Fabian Greffrath wrote:

> Please note that the "preferred form for modification" is a term
> exclusive to the GPL, it does not necessarily apply to fonts licensed
> under any other license. Also, I am not sure if this is really exactly
> what is meant by the "missing sources" paragraph of the REJECTS FAQs.

It is definitely not exclusive to the GPL; it is widely used to refer
to the source of FLOSS works.

Please try to submit a git commit to Firacode upstream containing only
changes to the generated files. Then you will see that this phrase has
meaning in any software context, including in the world of fonts and
Firacode in particular.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#848214: marked as done (nfsdcltrack installed to wrong location)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 07:37:40 +0100
with message-id 
and subject line fixed in unstable / stretch
has caused the Debian Bug report #848214,
regarding nfsdcltrack installed to wrong location
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.)


-- 
848214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.2.8-9.2
Severity: serious
Fixed: 1:1.3.4-1

The kernel looks[1] for nfsdcltrack in /sbin

The package released in jessie installs it to /usr/sbin

Fixed in the 1.3.4-1 upload.

This affects jessie users, a stable update may be necessary


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847681#145
--- End Message ---
--- Begin Message ---


As mentioned in the original bug report, this affects jessie users, a
stable update may be necessary--- End Message ---

Bug#851634: Extensions do not load.

[Jean-Francois Pirus]

Also if this option "--enable-remote-extensions" is not specified, no 
extensions load.

Processed: Re: Bug#851710: zoneminder: CVE-2016-10140

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #851710 [src:zoneminder] zoneminder: CVE-2016-10140
Severity set to 'grave' from 'important'

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

Bug#851375: marked as done (s3ql FTBFS: test_retrieve fails on several architectures)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 04:49:49 +
with message-id 
and subject line Bug#851375: fixed in s3ql 2.21+dfsg-3
has caused the Debian Bug report #851375,
regarding s3ql FTBFS: test_retrieve fails on several architectures
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.)


-- 
851375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: s3ql
Version: 2.21+dfsg-2
Severity: serious

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

...
tests/t3_inode_cache.py::cache_tests::test_get PASSED
tests/t3_verify.py::test_retrieve FAILED

=== FAILURES ===
 test_retrieve _
Traceback (most recent call last):
  File "/«BUILDDIR»/s3ql-2.21+dfsg/tests/t3_verify.py", line 96, in 
test_retrieve
thread_count=1, full=False)
  File "/usr/lib/python3.5/contextlib.py", line 66, in __exit__
next(self.gen)
  File "/«BUILDDIR»/s3ql-2.21+dfsg/tests/pytest_checklogs.py", line 71, in 
assert_logs
% (count, pattern, handler.count))
AssertionError: Expected to catch 1 '^Object %d is corrupted' messages, but got 
only 0
- Captured stdout call -

..processed 0 objects (0.00%) so far..
-- Captured log call ---
verify.py  118 INFO Reading all objects...
verify.py  201 DEBUGreading object 22
verify.py  215 WARNING  Backend seems to have lost object 22
verify.py  201 DEBUGreading object 25
verify.py  201 DEBUGreading object 30
verify.py  201 DEBUGreading object 31
verify.py  181 INFO Verified all 3 storage objects.
 pytest-warning summary 
WC1 /«BUILDDIR»/s3ql-2.21+dfsg/tests/t2_block_cache.py cannot collect test 
class 'TestBackendPool' because it has a __init__ constructor
 Interrupted: stopping after 1 failures 
= 1 failed, 242 passed, 1 skipped, 1 pytest-warnings in 96.08 seconds ==
debian/rules:51: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: s3ql
Source-Version: 2.21+dfsg-3

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

Debian distribution maintenance software
pp.
Nikolaus Rath  (supplier of updated s3ql 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: Tue, 17 Jan 2017 20:35:21 -0800
Source: s3ql
Binary: s3ql s3ql-dbg
Architecture: source
Version: 2.21+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Nikolaus Rath 
Description:
 s3ql   - Full-featured file system for online data storage
 s3ql-dbg   - Full-featured file system for online data storage (debugging symb
Closes: 851375
Changes:
 s3ql (2.21+dfsg-3) unstable; urgency=medium
 .
   * Expect test_verify() to fail during build. There is a race
 condition in the test that still needs to be fixed, but this
 should not cause the build to fail. Closes: #851375.
Checksums-Sha1:
 a71abdbba19224fe4f0ccc5d5b6c29bdec2c357b 2822 s3ql_2.21+dfsg-3.dsc
 8e0ec81ed3ca10840e45d4d0d4f750d15ea818f1 21248 s3ql_2.21+dfsg-3.debian.tar.xz
Checksums-Sha256:
 f7d2c3355ad7b4407a16c13514527174721a01ca93fc2f999d83e1bf696361e6 2822 
s3ql_2.21+dfsg-3.dsc
 69e888b4db8364e3eca0ebf05fda34981b856f71c84b710fa420e8fb74eebbc0 21248 
s3ql_2.21+dfsg-3.debian.tar.xz
Files:
 c3d7db479e4216226f5d6ded878c7223 2822 misc optional s3ql_2.21+dfsg-3.dsc
 5e8d150027cb783610b481361332ccbd 21248 misc optional 
s3ql_2.21+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Paul Wise]

On Tue, Jan 17, 2017 at 10:29 PM, Fabian Greffrath wrote:

> But the OTF format itself is just as suitable a source format for fonts as
> any other format. Why is it so important what upstream has chosen? It is
> not that font composition is a human-readable-to-binary-one-way-road like
> compilation C source files into object code or HTML documentation to PDF.

FYI, you are mistaken that C code is always "source". C is sometimes
generated from other forms, via transpilers or lexer generators etc.
It can also be obfuscated C code from the real C source (cf #383465).

Likewise for HTML, it is often generated from templates or simple text
languages like markdown.

So like C, OTF can be source or not source, depending on the upstream project.

C to ELF is not a one-way process, there are disassemblers and decompilers.

Likewise for HTML and PDF. LibreOffice and other software can even edit PDF.

Likewise, the conversion from Glyphs to OTF definitely throws away
information. Even the conversion from Glyphsapp to UFO format (which
is sometimes used as a font source format) throws away information
according to the Glyphsapp documentation:

https://glyphsapp.com/tutorials/working-with-ufo

> Thought experiment: Would it feel more "correct" if I forked the firacode
> upstream project, converted their OTF files into fontforge's SFD format,
> checked these into a GIT repo and then distributed these?

That would be a disingenuous workaround for the choices that Firacode
upstream has made and the reality of the Free Software ecosystem for
fonts in 2017. If you convinced Firacode upstream to switch their
source format then that would be different. Or if FontForge or
FontTools or another piece of Free Software started to support
Glyphsapp format, then their choice would be fine for main.

I have a better thought experiment:

Would Debian put a free Java program in main or contrib in the time
when the official JDK was proprietary and GCJ hadn't been implemented
yet?

> Another thought experiment: We have a fairly prominent example of
> binary-only Type1 fonts available in the gsfonts package. They are
> licensed under the GPL, so there is even a "preferred form for
> modification" term that applies to them. Nobody knows how URW++ created
> these fonts and what tools they used, nevertheless a number of viable
> forks have been developed from them, among them GNU FreeFont and TeX Gyre.
> Now, what would happen if URW++ suddenly revealed that they used
> proprietary software to create the fonts and that the files that we have
> are not the canonical sources. Why should it make a difference at all?

It is unfortunate that the gsfonts upstream didn't ask the right
questions before integrating these files into the project. They really
should have done that. At that point in time we would have to remove
the URW++ fonts from Debian since we would not be in compliance with
the GPL.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

That would have been my guess too, but Bio:: Graphics 2.40 is the right
version. When running build test on a virgin Mint 18.2 system with
Bio::Perl 1.7.1 and Bio::Graphics 2.40 I'm getting 100% test success.  This
is very puzzling.

I'll  take a closer look tonight.

Lincoln

On Tue, Jan 17, 2017 at 6:27 PM gregor herrmann  wrote:

> On Tue, 17 Jan 2017 18:06:02 -0500, Lincoln Stein wrote:
>
>
>
> > Not good! But I believe that Gregor found that all these were caused by
> the
>
> > testing suite not finding the proper data files due to an assumption
> about
>
> > the current working directory. When he fixed this, there were just a
>
> > handful of tests still failing.
>
>
>
> Right, that's when I built from a clone of the debian package git
>
> repo. With your github repo, this was not necessary for reasons I
>
> haven't yet understood.
>
>
>
> > Gregor, is there a patch file that I can
>
> > apply to get up to the same point you got to?
>
>
>
> Oh, scratch what I wrote above, now I get the same with the debian
>
> repo, so no more "Can't find foo in @INC". Good, at least the
>
> failures are consistent now (for whatever reason, maybe the 5.24.1
>
> upload to unstable changed something), and no patch for that part
>
> needed.
>
>
>
> So now we are still at:
>
>
>
>
>
> t/03.render.t .
>
> 1..150
>
> ok 1
>
> ok 2
>
> ok 3
>
> ok 4
>
> ok 5
>
> ok 6
>
> ok 7
>
> ok 8
>
> ok 9
>
> ok 10
>
> ok 11
>
> ok 12
>
> ok 13
>
> ok 14
>
> ok 15
>
> ok 16
>
> ok 17
>
> ok 18
>
> ok 19
>
> ok 20
>
> ok 21
>
> ok 22
>
> ok 23
>
> ok 24
>
> ok 25
>
> ok 26
>
> ok 27
>
> ok 28
>
> ok 29
>
> ok 30
>
> ok 31
>
> ok 32
>
> ok 33
>
> ok 34
>
> ok 35
>
> ok 36
>
> ok 37
>
> ok 38
>
> ok 39
>
> ok 40
>
> ok 41
>
> Dubious, test returned 255 (wstat 65280, 0xff00)
>
> Failed 109/150 subtests
>
> Sometimes this test gets 'stuck'. If this happens, kill the test and Build
> test again.
>
> RenderPanels error:
>
> - EXCEPTION -
>
> MSG: The requested glyph class, ``span'' is not available: Attempt to
> reload Bio/Graphics/Glyph/span.pm aborted.
>
> Compilation failed in require at (eval 138) line 2, <> line 132.
>
>
>
> STACK Bio::Graphics::Glyph::Factory::make_glyph
> /usr/share/perl5/Bio/Graphics/Glyph/Factory.pm:342
>
> STACK Bio::Graphics::Glyph::add_feature
> /usr/share/perl5/Bio/Graphics/Glyph.pm:424
>
> STACK Bio::Graphics::Browser2::RenderPanels::add_features_to_track
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1869
>
> STACK (eval)
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1597
>
> STACK Bio::Graphics::Browser2::RenderPanels::run_local_requests
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1551
>
> STACK Bio::Graphics::Browser2::Render::Slave::render_tracks
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:471
>
> STACK Bio::Graphics::Browser2::Render::Slave::run_operation
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:325
>
> STACK Bio::Graphics::Browser2::Render::Slave::process_request
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:316
>
> STACK Bio::Graphics::Browser2::Render::Slave::process_connection
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:240
>
> STACK Bio::Graphics::Browser2::Render::Slave::request_loop
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:229
>
> STACK Bio::Graphics::Browser2::Render::Slave::run
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:160
>
> STACK toplevel t/04.remoteserver.t:81
>
> -
>
>
>
> Use of uninitialized value in numeric gt (>) at t/04.remoteserver.t line
> 136.
>
> RenderPanels error:
>
> - EXCEPTION -
>
> MSG: The requested glyph class, ``span'' is not available: Attempt to
> reload Bio/Graphics/Glyph/span.pm aborted.
>
> Compilation failed in require at (eval 138) line 2, <> line 132.
>
>
>
> STACK Bio::Graphics::Glyph::Factory::make_glyph
> /usr/share/perl5/Bio/Graphics/Glyph/Factory.pm:342
>
> STACK Bio::Graphics::Glyph::add_feature
> /usr/share/perl5/Bio/Graphics/Glyph.pm:424
>
> STACK Bio::Graphics::Browser2::RenderPanels::add_features_to_track
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1869
>
> STACK (eval)
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1597
>
> STACK Bio::Graphics::Browser2::RenderPanels::run_local_requests
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1551
>
> STACK Bio::Graphics::Browser2::Render::Slave::render_tracks
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:471
>
> STACK Bio::Graphics::Browser2::Render::Slave::run_operation
> /build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:325
>
> STACK Bio::Graphics::Browser2::Render::Slave::process_request
> 

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Scott Kitterman]

On January 17, 2017 3:49:46 PM EST, Fabian Greffrath  wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney:
>> Debian recipients should have equal access to make modifications to
>> the work, build the work from modified source, and install the
>> result.
>
>All these modifications could be made to the OTF files *just as well*,
>there is no advantage in using the same font format as upstream does
>for their development. But I figure we are running in circles now. ;)
>
>> The fact of the matter is the Glyphs data files are the preferred
>> form
>> of the work to make modifications.
>
>Please note that the "preferred form for modification" is a term
>exclusive to the GPL, it does not necessarily apply to fonts licensed
>under any other license. Also, I am not sure if this is really exactly
>what is meant by the "missing sources" paragraph of the REJECTS FAQs.

DFSG #2 requires that "The program must include source code".  Preferred form 
of modification is the definition of source that the FTP team uses.  For Debian 
DFSG purposes it's not exclusively GPL relevant.

Scott K

>
>> It would reveal that Debian recipients do not have equal access to
>> the source, for modifying building, and installing the work.
>
>And thus you would file a bug requesting the removal of this package
>from Debian main? Are you even aware of the vast consequences that this
>overly strict interpretation of the "missing sources" paragraph may
>have?
>
> - Fabian
>-BEGIN PGP SIGNATURE-
>
>iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlh+g2oACgkQy+qOlwzN
>Wd/hVA//X+zpFiwIdA2AUgAuQarC/zLV9RI1SHv4z+ASIvWyALzsLstxinD5fCOY
>M6X6ySeU9ek7O/ZygHg1STgOzcBF42FvEIZscdFF6jMu5eH1zuW+t+8AoEJwMQLK
>Uf50XrN0/ZR5DHHXKqMwfPZ39OOIJ5A9iYlHZEe8bkSYjbwF/HlIcUL53xddwOq9
>bvETmHCeKJYst/QQsmR6sBNtYY2OV0onSoLxVxsbwLmlcKBA5Sg8DpjZBk407MFo
>NGllJACTuEWXZDDypAdohEsln3/yw61F/B3LbakvobEnh4pT9iNiOlOCT5MuIOiu
>yAs0tRFo5sH2rgt3HIlzfHqnCkm4U3+Y4+fHCXJTt5X9HnzC/GuExqP83o21fH3/
>qRFSnx4hDfh/D89HiL/SRhj3mx5xGbjqvYuIuoRpH67loTw73nyv2qblv37eFXUg
>uWTzoc3ln+/AQLaeFmzz8vZM2NPWff9PAKD+0QL9tbbRbAJsNpLZJbxXVC1sLP5Q
>pyjESFt7DinDXPUWUgr1NXiaPJd9+sxcOnOje94B6cZpz3RWKsteTWWjJVmWfrbf
>T5sVcwPo6ALHKX6MVXplO/prLKzvwivpO+U0wq9qKQe0M3PtJ+a6eZxKjOX/9re3
>Qg0zsjagw2V/tYsszATyETAvU9gK21dVAJ8PDPiMduFsXdOV4WE=
>=s0k/
>-END PGP SIGNATURE-

Bug#850077: python-paramiko doesn't work with python-crypto 2.6-4

[Chris Lamb]

Version: 2.6-4+deb7u7

Hi,

> python-paramiko doesn't work with python-crypto 2.6-4

I believe this was fixed in 2.6-4+deb7u7 (or earlier). :)


Regards,

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

Bug#850077: marked as done (python-paramiko doesn't work with python-crypto 2.6-4)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 01:03:55 +
with message-id 
<1484701435.2699191.851084080.0efc4...@webmail.messagingengine.com>
and subject line Re: python-paramiko doesn't work with python-crypto 2.6-4
has caused the Debian Bug report #850077,
regarding python-paramiko doesn't work with python-crypto 2.6-4
to be marked as done.

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

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


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

Dear Maintainer,

Since yesterday's update, backup to a SSH target is broken and leads to this 
stacktrace:

ssh: Unknown exception: CTR mode needs counter parameter, not IV
ssh: Traceback (most recent call last):
ssh:   File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 
1542, in run
ssh: self.kex_engine.parse_next(ptype, m)
ssh:   File "/usr/lib/python2.7/dist-packages/paramiko/kex_group1.py", line 68, 
in parse_next
ssh: return self._parse_kexdh_reply(m)
ssh:   File "/usr/lib/python2.7/dist-packages/paramiko/kex_group1.py", line 
107, in _parse_kexdh_reply
ssh: self.transport._activate_outbound()
ssh:   File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 
1831, in _activate_outbound
ssh: engine = self._get_cipher(self.local_cipher, key_out, IV_out)
ssh:   File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 
1480, in _get_cipher
ssh: return self._cipher_info[name]['class'].new(key, 
self._cipher_info[name]['mode'], iv, counter)
ssh:   File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, 
in new
ssh: return AESCipher(key, *args, **kwargs)
ssh:   File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, 
in __init__
ssh: blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
ssh:   File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 
141, in __init__
ssh: self._cipher = factory.new(key, *args, **kwargs)
ssh: ValueError: CTR mode needs counter parameter, not IV 

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

   * What led up to the situation?

The upgrade of python-crypto from 2.6-4+deb7u3 to 2.6-4+deb7u4

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

I did a downgrade of python-crypto to 2.6-4+deb7u3.

   * What was the outcome of this action?

My backups are working again.

   * What outcome did you expect instead?

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


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

Kernel: Linux 3.10.23--std-ipv6-64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages duplicity depends on:
ii  libc6  2.13-38+deb7u11
ii  librsync1  0.9.7-9
ii  python 2.7.3-4+deb7u1
ii  python-gnupginterface  0.3.2-9.1

Versions of packages duplicity recommends:
ii  python-paramiko  1.7.7.1-3.1
ii  rsync3.0.9-4

Versions of packages duplicity suggests:
pn  lftp   
ii  ncftp  2:3.2.5-1.1
pn  python-boto
pn  python-cloudfiles  
ii  python-gdata   2.0.17+dfsg-1
ii  python-pexpect 2.4-1
pn  tahoe-lafs 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6-4+deb7u7

Hi,

> python-paramiko doesn't work with python-crypto 2.6-4

I believe this was fixed in 2.6-4+deb7u7 (or earlier). :)


Regards,

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

Bug#851726: liggghts: FTBFS on single-CPU machines (not enough slots available)

[Santiago Vila]

Package: src:liggghts
Version: 3.5.0+repack1-8
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/liggghts-3.5.0+repack1/debian/build --parallel
   dh_testdir -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.5.0\+repack1/debian/build 
-O--parallel
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.5.0\+repack1/debian/build 
-O--parallel
   dh_auto_configure -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.5.0\+repack1/debian/build 
-O--parallel
cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 6.2.1
-- The CXX compiler identification is GNU 6.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

cd /<>/liggghts-3.5.0+repack1/debian/build/src && /usr/bin/mpicxx   
-Dlibliggghts_EXPORTS 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/eigen3 
-I/<>/liggghts-3.5.0+repack1 
-I/<>/liggghts-3.5.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.5.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/write_dump.cpp.o -c 
/<>/liggghts-3.5.0+repack1/src/write_dump.cpp
[ 98%] Building CXX object src/CMakeFiles/libliggghts.dir/write_restart.cpp.o
cd /<>/liggghts-3.5.0+repack1/debian/build/src && /usr/bin/mpicxx   
-Dlibliggghts_EXPORTS 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/eigen3 
-I/<>/liggghts-3.5.0+repack1 
-I/<>/liggghts-3.5.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.5.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/write_restart.cpp.o -c 
/<>/liggghts-3.5.0+repack1/src/write_restart.cpp
[ 99%] Linking CXX shared library libliggghts.so
cd /<>/liggghts-3.5.0+repack1/debian/build/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/libliggghts.dir/link.txt --verbose=1
/usr/bin/mpicxx  -fPIC -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.5.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG 
-Wl,-z,relro -Wl,--as-needed  -shared -Wl,-soname,libliggghts.so.3 -o 
libliggghts.so.3.3.1 CMakeFiles/libliggghts.dir/angle.cpp.o 
CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o 
CMakeFiles/libliggghts.dir/atom.cpp.o CMakeFiles/libliggghts.dir/atom_map.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_atomic.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_charge.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_ellipsoid.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_hybrid.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_line.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sph.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sph_var.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sphere.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sphere_w.cpp.o CMakeFiles/libliggghts.dir/
 bond.cpp.o CMakeFiles/libliggghts.dir/bond_hybrid.cpp.o 
CMakeFiles/libliggghts.dir/bounding_box.cpp.o 
CMakeFiles/libliggghts.dir/cfd_datacoupling.cpp.o 
CMakeFiles/libliggghts.dir/cfd_datacoupling_file.cpp.o 
CMakeFiles/libliggghts.dir/cfd_datacoupling_mpi.cpp.o 
CMakeFiles/libliggghts.dir/cfd_regionmodel_none.cpp.o 
CMakeFiles/libliggghts.dir/change_box.cpp.o 
CMakeFiles/libliggghts.dir/citeme.cpp.o CMakeFiles/libliggghts.dir/comm.cpp.o 
CMakeFiles/libliggghts.dir/compute.cpp.o 
CMakeFiles/libliggghts.dir/compute_atom_molecule.cpp.o 
CMakeFiles/libliggghts.dir/compute_bond_local.cpp.o 
CMakeFiles/libliggghts.dir/compute_centro_atom.cpp.o 
CMakeFiles/libliggghts.dir/compute_cluster_atom.cpp.o 
CMakeFiles/libliggghts.dir/compute_cna_atom.cpp.o 
CMakeFiles/libliggghts.dir/compute_com.cpp.o 
CMakeFiles/libliggghts.dir/compute_com_molecule.cpp.o 
CMakeFiles/libliggghts.dir/compute_contact_atom.cpp.o 
CMakeFiles/libliggghts.dir/compute_coord_atom.cpp.o 
CMakeFiles/libliggghts.dir/compute_displace_atom.c
 pp.o CMakeFiles/libliggghts.dir/compute_erotate_multisphere.cpp.o 

Bug#753179: marked as done (festvox-czech-machac: FTBFS: Error reading ESPS file ./lpc/machac0004.lpc)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 00:04:32 +
with message-id 
and subject line Bug#753179: fixed in festvox-czech-machac 1.0.0-3
has caused the Debian Bug report #753179,
regarding festvox-czech-machac: FTBFS: Error reading ESPS file 
./lpc/machac0004.lpc
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.)


-- 
753179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: festvox-czech-machac
Version: 1.0.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 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): 
> WARNING
> No default voice found in ("/usr/share/festival/voices/")
> either no voices unpacked or voice-path is wrong
> Scheme interpreter will work, but there is no voice to speak with.
> WARNING
> 
> Error reading ESPS file ./lpc/machac0004.lpc
> US DB: failed to read coefs file from ./lpc/machac0004.lpc
> -=-=-=-=-=- EST Error -=-=-=-=-=-
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> closing a file left open: make-group.scm
> Makefile:29: recipe for target 'group/machac.group' failed
> make[1]: *** [group/machac.group] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/festvox-czech-machac_1.0.0-2_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: festvox-czech-machac
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Sergio Oller  (supplier of updated festvox-czech-machac 
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, 18 Jan 2017 00:40:41 +0100
Source: festvox-czech-machac
Binary: festvox-czech-machac
Architecture: source all
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian TTS Team 
Changed-By: Sergio Oller 
Description:
 festvox-czech-machac - Czech adult male speaker "machac" for Festival
Closes: 730990 753179
Changes:
 festvox-czech-machac (1.0.0-3) unstable; urgency=medium
 .
   [ Sergio Oller ]
   * Package maintained by the debian tts team. Closes: #730990
   * Switch to dh builds. Closes: #753179
   * Bump Standards-Version to 3.9.8.
   * Update debian/compat to 9.
 .
   [ Samuel Thibault ]
   * Fix build due to missing empty lpc directory.
Checksums-Sha1:
 69c37fd4fe3af251a2b6f923ec6b643d62c3b6b2 2106 festvox-czech-machac_1.0.0-3.dsc
 c2bab1c2f600a3dde37529f8784816c2f7578943 2744 
festvox-czech-machac_1.0.0-3.debian.tar.xz
 cc27a122505d8c1e4f810a784aea3a313fed6db2 5941408 
festvox-czech-machac_1.0.0-3_all.deb
 fe32444ee6973688a40cf0f7d9be3cd39d19fed7 5486 
festvox-czech-machac_1.0.0-3_amd64.buildinfo
Checksums-Sha256:
 b14549bedd0d5d5ac177e35dfba8e60ff6b3024e6c29b357713cf72d7af2a7e1 2106 
festvox-czech-machac_1.0.0-3.dsc
 750f9ea08d3daf9cb4b735907f356ac941d3ae35b8e4922bf8d909335e88e8fc 2744 
festvox-czech-machac_1.0.0-3.debian.tar.xz
 110029c365be2b1444b0a98d6730503436962be74c6ace9d3181e9b490e601c4 5941408 
festvox-czech-machac_1.0.0-3_all.deb
 3287ce2c06ea8d22ff7ce07a2c89d52a356236192d6c5b38c0e2ff705e34bfdd 5486 
festvox-czech-machac_1.0.0-3_amd64.buildinfo
Files:
 19ee8320f95dcbc057a66620fb19a85b 2106 sound optional 
festvox-czech-machac_1.0.0-3.dsc
 dd465adec92b3bde51b29133e4193598 2744 sound optional 
festvox-czech-machac_1.0.0-3.debian.tar.xz
 29d7371dff77fd3ddc295a26479a3076 5941408 sound optional 
festvox-czech-machac_1.0.0-3_all.deb
 

Bug#753189: marked as done (festvox-czech-krb: FTBFS: Error reading ESPS file ./lpc/krb0012.lpc)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 00:04:12 +
with message-id 
and subject line Bug#753189: fixed in festvox-czech-krb 1.0.0-3
has caused the Debian Bug report #753189,
regarding festvox-czech-krb: FTBFS: Error reading ESPS file ./lpc/krb0012.lpc
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.)


-- 
753189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: festvox-czech-krb
Version: 1.0.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 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):
> mkdir -p group
> festival -b make-group.scm
> "Could not find any of these voices:"
> (nitech_us_slt_arctic_hts nitech_us_awb_arctic_hts nitech_us_bdl_arctic_hts 
> nitech_us_clb_arctic_hts nitech_us_jmk_arctic_hts nitech_us_rms_arctic_hts 
> kal_diphone ked_diphone cstr_us_awb_arctic_multisyn 
> cstr_us_jmk_arctic_multisyn)
> 
> WARNING
> No default voice found in ("/usr/share/festival/voices/")
> either no voices unpacked or voice-path is wrong
> Scheme interpreter will work, but there is no voice to speak with.
> WARNING
> 
> Error reading ESPS file ./lpc/krb0012.lpc
> US DB: failed to read coefs file from ./lpc/krb0012.lpc
> -=-=-=-=-=- EST Error -=-=-=-=-=-
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> closing a file left open: make-group.scm
> Makefile:29: recipe for target 'group/krb.group' failed
> make[1]: *** [group/krb.group] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/festvox-czech-krb_1.0.0-2_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: festvox-czech-krb
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Sergio Oller  (supplier of updated festvox-czech-krb 
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, 18 Jan 2017 00:42:44 +0100
Source: festvox-czech-krb
Binary: festvox-czech-krb
Architecture: source all
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian TTS Team 
Changed-By: Sergio Oller 
Description:
 festvox-czech-krb - Czech child male speaker "krb" for Festival
Closes: 730991 753189
Changes:
 festvox-czech-krb (1.0.0-3) unstable; urgency=medium
 .
   [ Sergio Oller ]
   * Package maintained by the debian tts team. Closes: #730991
   * Switch to dh builds. Closes: #753189
   * Bump Standards-Version to 3.9.8.
   * Update debian/compat to 9.
 .
   [ Samuel Thibault ]
   * Fix build due to missing empty lpc directory.
Checksums-Sha1:
 af4ca944b0425e54489ce22c2070bcf68016f05a 2073 festvox-czech-krb_1.0.0-3.dsc
 810e2b5a9c8bd9e773e031363cf3c83ea01d0d9e 2744 
festvox-czech-krb_1.0.0-3.debian.tar.xz
 3ad89a46ad9c05f807832b17b0e5ddc25d50fde7 9283560 
festvox-czech-krb_1.0.0-3_all.deb
 2b7a67c77078c564590fc09049b3bfad559604a8 5459 
festvox-czech-krb_1.0.0-3_amd64.buildinfo
Checksums-Sha256:
 5c3520f415c832ff0840dfc850aff2107e0e4f8d2264a57bd27a8c0ad7ac1c1b 2073 
festvox-czech-krb_1.0.0-3.dsc
 fa6af4fb799d366190a5fd3c74f7b4fa0fa17edddf3be2f718afaf2245182675 2744 
festvox-czech-krb_1.0.0-3.debian.tar.xz
 fbedaf15edccc8e5eec44a47cda7b829d1fc0a6e8b9b547d7255d891d0f30e75 9283560 
festvox-czech-krb_1.0.0-3_all.deb
 4613e93e530a692a2b7dc43a444a7b6c5167cd7f104519f30c6ff9ab3c2d833a 5459 
festvox-czech-krb_1.0.0-3_amd64.buildinfo
Files:
 2f38975c96f8f9b3403a4f6ece303028 

Bug#750344: marked as done (festvox-czech-dita: FTBFS: US DB: failed to read coefs file from ./lpc/dita0001.lpc)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 00:03:50 +
with message-id 
and subject line Bug#750344: fixed in festvox-czech-dita 1.0.0-3
has caused the Debian Bug report #750344,
regarding festvox-czech-dita: FTBFS: US DB: failed to read coefs file from 
./lpc/dita0001.lpc
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.)


-- 
750344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: festvox-czech-dita
Version: 1.0.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 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):
> festival -b make-group.scm
> "Could not find any of these voices:"
> (nitech_us_slt_arctic_hts nitech_us_awb_arctic_hts nitech_us_bdl_arctic_hts 
> nitech_us_clb_arctic_hts nitech_us_jmk_arctic_hts nitech_us_rms_arctic_hts 
> kal_diphone ked_diphone cstr_us_awb_arctic_multisyn 
> cstr_us_jmk_arctic_multisyn)
> 
> WARNING
> No default voice found in ("/usr/share/festival/voices/")
> either no voices unpacked or voice-path is wrong
> Scheme interpreter will work, but there is no voice to speak with.
> WARNING
> 
> Error reading ESPS file ./lpc/dita0001.lpc
> US DB: failed to read coefs file from ./lpc/dita0001.lpc
> -=-=-=-=-=- EST Error -=-=-=-=-=-
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> closing a file left open: make-group.scm
> Makefile:29: recipe for target 'group/dita.group' failed
> make[1]: *** [group/dita.group] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/festvox-czech-dita_1.0.0-2_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: festvox-czech-dita
Source-Version: 1.0.0-3

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

Debian distribution maintenance software
pp.
Sergio Oller  (supplier of updated festvox-czech-dita 
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, 18 Jan 2017 00:39:47 +0100
Source: festvox-czech-dita
Binary: festvox-czech-dita
Architecture: source all
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian TTS Team 
Changed-By: Sergio Oller 
Description:
 festvox-czech-dita - Czech adult female speaker "dita" for Festival
Closes: 730989 750344
Changes:
 festvox-czech-dita (1.0.0-3) unstable; urgency=medium
 .
   [ Sergio Oller ]
   * Package maintained by the debian tts team. Closes: #730989
   * Switch to dh builds. Closes: #750344
   * Bump Standards-Version to 3.9.8.
   * Update debian/compat to 9.
 .
   [ Samuel Thibault ]
   * Fix build due to missing empty lpc directory.
Checksums-Sha1:
 e1785e1e876c6a5f5b3fc166e889629babc98d54 2084 festvox-czech-dita_1.0.0-3.dsc
 6554a110a031c26dbe98ee7e9b727cfed55f4e45 2744 
festvox-czech-dita_1.0.0-3.debian.tar.xz
 10e1d7de0681372cb34956d22e8b8764d9e271ce 7909568 
festvox-czech-dita_1.0.0-3_all.deb
 99c8f7daca777f7025ecefc4560490ca14781028 5468 
festvox-czech-dita_1.0.0-3_amd64.buildinfo
Checksums-Sha256:
 3b3218445dd2ccd12dc26b0940db59433e00711ad6a08e1888154f85d1b74adc 2084 
festvox-czech-dita_1.0.0-3.dsc
 51b56caa2587d086ccba76c1ca7f4086149e02ae50909ac45178075df5e69ff0 2744 
festvox-czech-dita_1.0.0-3.debian.tar.xz
 9be3683ab6f40169de5a50e3ce0a44e1b4e613fe501d476b0457f62276ccd121 7909568 
festvox-czech-dita_1.0.0-3_all.deb
 a0747688696fa5c24b04f13b0b61dff57523dc5250cdb413f2d49fa9e20b8bf1 5468 
festvox-czech-dita_1.0.0-3_amd64.buildinfo
Files:
 

Bug#851724: python-llfuse: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-llfuse
Version: 1.1.1+dfsg-5
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config 
running config
pybuild --configure -i python{version}-dbg -p 2.7
I: pybuild base:184: python2.7-dbg setup.py config 
running config
[88380 refs]
pybuild --configure -i python{version} -p 3.5
I: pybuild base:184: python3.5 setup.py config 

[... snipped ...]

make[1]: Leaving directory '/<>/python-llfuse-1.1.1+dfsg'
   dh_auto_test -i -O--buildsystem=pybuild
pybuild --test -i python{version} -p 2.7
I: pybuild base:184: cd 
/<>/python-llfuse-1.1.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 
-m pytest --installed "/<>/python-llfuse-1.1.1+dfsg/test/"
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.5, py-1.4.32, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ../../../test/.cache
rootdir: /<>/python-llfuse-1.1.1+dfsg/test, inifile: pytest.ini
plugins: catchlog-1.2.2
collecting ... collected 13 items

../../../test/test_api.py::test_inquire_bits PASSED
../../../test/test_api.py::test_listdir PASSED
../../../test/test_api.py::test_sup_groups PASSED
../../../test/test_api.py::test_entry_res PASSED
../../../test/test_api.py::test_xattr PASSED
../../../test/test_examples.py::test_lltest PASSED
../../../test/test_examples.py::test_tmpfs FAILED

=== FAILURES ===
__ test_tmpfs __
Traceback (most recent call last):
  File "/<>/python-llfuse-1.1.1+dfsg/test/pytest_checklogs.py", line 
127, in pytest_runtest_call
check_output(item)
  File "/<>/python-llfuse-1.1.1+dfsg/test/pytest_checklogs.py", line 
119, in check_output
check_test_output(cm._capturing, item)
  File "/<>/python-llfuse-1.1.1+dfsg/test/pytest_checklogs.py", line 
96, in check_test_output
raise AssertionError('Suspicious output to stderr (matched "%s")' % 
hit.group(0))
AssertionError: Suspicious output to stderr (matched "Exception")
- Captured stderr call -
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
  File "/usr/lib/python2.7/threading.py", line 754, in run
  File "src/misc.pxi", line 261, in llfuse._notify_loop (src/llfuse.c:29495)
  File "/usr/lib/python2.7/Queue.py", line 179, in get
  File "/usr/lib/python2.7/threading.py", line 384, in notify
: 'NoneType' object is not callable
 Interrupted: stopping after 1 failures 
== 1 failed, 6 passed in 0.46 seconds ==
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=2: cd 
/<>/python-llfuse-1.1.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 
-m pytest --installed "{dir}/test/"
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/python-llfuse/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine.

I know this is strange because it built fine last time on buildd.debian.org,
but I can reproduce the failure in 7 different machines. In case you need help
to reproduce it, please say so. As a last resort I could offer ssh access
to a machine where this happens.

Thanks.

Bug#844796:

[Richard Ayotte]

Adding /usr/lib/x86_64-linux-gnu/mutter to
/etc/ld.so.conf.d/x86_64-linux-gnu.conf and running ldconfig fixed it
for me. ldconfig doesn't process directories recursively and the
mutter directory was missing.

Here's what the conf looked like before the edit.

# Multiarch support
/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[gregor herrmann]

On Tue, 17 Jan 2017 18:06:02 -0500, Lincoln Stein wrote:

> Not good! But I believe that Gregor found that all these were caused by the
> testing suite not finding the proper data files due to an assumption about
> the current working directory. When he fixed this, there were just a
> handful of tests still failing. 

Right, that's when I built from a clone of the debian package git
repo. With your github repo, this was not necessary for reasons I
haven't yet understood.

> Gregor, is there a patch file that I can
> apply to get up to the same point you got to?

Oh, scratch what I wrote above, now I get the same with the debian
repo, so no more "Can't find foo in @INC". Good, at least the
failures are consistent now (for whatever reason, maybe the 5.24.1
upload to unstable changed something), and no patch for that part
needed.

So now we are still at:
 

t/03.render.t . 
1..150
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33
ok 34
ok 35
ok 36
ok 37
ok 38
ok 39
ok 40
ok 41
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 109/150 subtests 
Sometimes this test gets 'stuck'. If this happens, kill the test and Build test 
again.
RenderPanels error: 
- EXCEPTION -
MSG: The requested glyph class, ``span'' is not available: Attempt to reload 
Bio/Graphics/Glyph/span.pm aborted.
Compilation failed in require at (eval 138) line 2, <> line 132.

STACK Bio::Graphics::Glyph::Factory::make_glyph 
/usr/share/perl5/Bio/Graphics/Glyph/Factory.pm:342
STACK Bio::Graphics::Glyph::add_feature 
/usr/share/perl5/Bio/Graphics/Glyph.pm:424
STACK Bio::Graphics::Browser2::RenderPanels::add_features_to_track 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1869
STACK (eval) 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1597
STACK Bio::Graphics::Browser2::RenderPanels::run_local_requests 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1551
STACK Bio::Graphics::Browser2::Render::Slave::render_tracks 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:471
STACK Bio::Graphics::Browser2::Render::Slave::run_operation 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:325
STACK Bio::Graphics::Browser2::Render::Slave::process_request 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:316
STACK Bio::Graphics::Browser2::Render::Slave::process_connection 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:240
STACK Bio::Graphics::Browser2::Render::Slave::request_loop 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:229
STACK Bio::Graphics::Browser2::Render::Slave::run 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:160
STACK toplevel t/04.remoteserver.t:81
-

Use of uninitialized value in numeric gt (>) at t/04.remoteserver.t line 136.
RenderPanels error: 
- EXCEPTION -
MSG: The requested glyph class, ``span'' is not available: Attempt to reload 
Bio/Graphics/Glyph/span.pm aborted.
Compilation failed in require at (eval 138) line 2, <> line 132.

STACK Bio::Graphics::Glyph::Factory::make_glyph 
/usr/share/perl5/Bio/Graphics/Glyph/Factory.pm:342
STACK Bio::Graphics::Glyph::add_feature 
/usr/share/perl5/Bio/Graphics/Glyph.pm:424
STACK Bio::Graphics::Browser2::RenderPanels::add_features_to_track 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1869
STACK (eval) 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1597
STACK Bio::Graphics::Browser2::RenderPanels::run_local_requests 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1551
STACK Bio::Graphics::Browser2::Render::Slave::render_tracks 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:471
STACK Bio::Graphics::Browser2::Render::Slave::run_operation 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:325
STACK Bio::Graphics::Browser2::Render::Slave::process_request 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:316
STACK Bio::Graphics::Browser2::Render::Slave::process_connection 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:240
STACK Bio::Graphics::Browser2::Render::Slave::request_loop 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:229
STACK Bio::Graphics::Browser2::Render::Slave::run 
/build/gbrowse-2.56+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm:160
STACK toplevel t/04.remoteserver.t:81
-

Use of uninitialized value in numeric gt (>) at t/04.remoteserver.t line 136.
RenderPanels error: 
- EXCEPTION -
MSG: The requested glyph class, ``span'' is not available: Attempt to reload 

Bug#851634: sh -n checks

[積丹尼 Dan Jacobson]

I would add a sh -n test to the build scripts to avoid such errors
getting sent out.

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Not good! But I believe that Gregor found that all these were caused by the
testing suite not finding the proper data files due to an assumption about
the current working directory. When he fixed this, there were just a
handful of tests still failing. Gregor, is there a patch file that I can
apply to get up to the same point you got to?

Lincoln

On Tue, Jan 17, 2017 at 2:07 AM, Andreas Tille  wrote:

> Hi Lincoln,
>
> On Mon, Jan 16, 2017 at 06:14:34PM -0500, Lincoln Stein wrote:
> > I need a little help to reproduce Gregor's failed tests, given that I'm a
> > complete newbie wrt the Debian packaging system. I have cloned gbrowse
> > 2.56+dfsg-1 from the Debian Med repository, but I don't know what command
> > line to use to attempt the build. What is the next step? I'm guessing it
> is
> > some form of dpkg-buildpackage, but the number of options is pretty
> > overwhelming!
>
> If you have installed the devscripts package you can try
>
> debuild
>
> which is a wrapper around dpkg-buildpackage and in principle needs no
> options to reproduce the issue.  Debuild will inform you about missing
> Build-Dependencies you need to install - simply use apt-get install what
> is listed if anything is missing.  When doing so I get
>
> ...
> Test Summary Report
> ---
> t/00.compile.t  (Wstat: 3840 Tests: 90 Failed: 15)
>   Failed tests:  1, 3, 5, 7, 10, 15, 17-18, 29, 31, 33, 35
> 41, 45, 47
>   Non-zero exit status: 15
> t/02.rearchitecture.t   (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 90 tests but ran 0.
> t/03.render.t   (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 150 tests but ran 0.
> t/04.remoteserver.t (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 43 tests but ran 0.
> t/05.deferredrendering.t (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 19 tests but ran 0.
> t/06.featuresearch.t(Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 26 tests but ran 0.
> t/07.karyotype.t(Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 3 tests but ran 0.
> Files=10, Tests=103,  5 wallclock secs ( 0.05 usr  0.01 sys +  4.19 cusr
> 0.30 csys =  4.55 CPU)
> Result: FAIL
> Failed 7/10 test programs. 15/103 subtests failed.
> dh_auto_test: perl Build test --verbose 1 TEST_FILES=t/02.rearchitecture.t
> t/05.deferredrendering.t t/00.compile.t t/01.yeast.t t/07.balancer.t
> t/08.calign.t returned exit code 255
>
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>



-- 
*Lincoln Stein*

Scientific Director (Interim), Ontario Institute for Cancer Research
Director, Informatics and Bio-computing Program, OICR
Senior Principal Investigator, OICR
Professor, Department of Molecular Genetics, University of Toronto


*Ontario Institute for Cancer Research*
MaRS Centre
661 University Avenue
Suite 510
Toronto, Ontario
Canada M5G 0A3

Tel: 416-673-8514
Mobile: 416-817-8240
Email: lincoln.st...@gmail.com
Toll-free: 1-866-678-6427
Twitter: @OICR_news

*Executive Assistant*
*Lisa Duncan*
Tel: 647-260-7970 <(647)%20260-7970>
Email: lisa.dun...@oicr.on.ca 
www.oicr.on.ca

This message and any attachments may contain confidential and/or privileged
information for the sole use of the intended recipient. Any review or
distribution by anyone other than the person for whom it was originally
intended is strictly prohibited. If you have received this message in
error, please contact the sender and delete all copies. Opinions,
conclusions or other information contained in this message may not be that
of the organization.

Processed: tagging 838671

[Debian Bug Tracking System]

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

> tags 838671 + jessie
Bug #838671 [openchangeproxy] openchangeproxy: uninstallable in jessie, broken 
by samba
Added tag(s) jessie.
> thanks
Stopping processing here.

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

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

Control: tags -1 patch

One way to reproduce this bug:
# apt-get install pocl-opencl-icd blender
$ gdb blender
open User Preferences -> System
This promptly crashes; beignet-opencl-icd 1.2.1-1 (LLVM 3.8, like pocl) 
also triggers it, but beignet-opencl-icd 1.2.1-2 and mesa-opencl-icd 
(LLVM 3.9, like the graphics part of mesa) don't.


#0  llvm::cl::Option::setArgStr(llvm::StringRef) ()
at /build/llvm-toolchain-3.9-3.9.1/include/llvm/ADT/SmallPtrSet.h:224
No locals.
#1  0x7fffbbe9aacb in llvm::cl::opt<(anonymous 
namespace)::HelpPrinter, true, llvm::cl::parser >::optllvm::cl::desc, llvm::cl::LocationClass<(anonymous 
namespace)::HelpPrinter>, llvm::cl::OptionHidden, 
llvm::cl::ValueExpected, llvm::cl::cat>(char const (&) [17], 
llvm::cl::desc const&, llvm::cl::LocationClass<(anonymous 
namespace)::HelpPrinter> const&, llvm::cl::OptionHidden const&, 
llvm::cl::ValueExpected const&, llvm::cl::cat const&) [clone 
.constprop.300] ()
at 
/build/llvm-toolchain-3.8-3.8.1/include/llvm/Support/CommandLine.h:1041

No locals.
#2  0x7fffbbe9ad08 in _GLOBAL__sub_I_CommandLine.cpp ()
at /build/llvm-toolchain-3.8-3.8.1/lib/Support/CommandLine.cpp:1661
No locals.
#3  0x77de95da in ?? () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#4  0x77de96eb in ?? () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#5  0x77dedc68 in ?? () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#6  0x77de9484 in ?? () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#7  0x77ded419 in ?? () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#8  0x7fffee0f0ee9 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
No symbol table info available.
#9  0x77de9484 in ?? () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#10 0x7fffee0f1521 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2
No symbol table info available.
#11 0x7fffee0f0f82 in dlopen () from /lib/x86_64-linux-gnu/libdl.so.2
No symbol table info available.
#12 0x7fffbf9f9212 in ?? () from 
/usr/lib/x86_64-linux-gnu/libOpenCL.so.1

No symbol table info available.
#13 0x7fffbf9f9360 in ?? () from 
/usr/lib/x86_64-linux-gnu/libOpenCL.so.1

No symbol table info available.
#14 0x7fffbf9f98d0 in ?? () from 
/usr/lib/x86_64-linux-gnu/libOpenCL.so.1

No symbol table info available.
#15 0x7fffbf9fa0d3 in clGetPlatformIDs ()
   from /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
No symbol table info available.

The relevant lines of the LLVM build log appear to be

Scanning dependencies of target LLVM
make[4]: Leaving directory '/«PKGBUILDDIR»/build-llvm'
/usr/bin/make -f tools/llvm-shlib/CMakeFiles/LLVM.dir/build.make 
tools/llvm-shlib/CMakeFiles/LLVM.dir/build

make[4]: Entering directory '/«PKGBUILDDIR»/build-llvm'
[ 76%] Building CXX object 
tools/llvm-shlib/CMakeFiles/LLVM.dir/libllvm.cpp.o
cd /«PKGBUILDDIR»/build-llvm/tools/llvm-shlib && /usr/bin/g++-6 
-D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS -I/«PKGBUILDDIR»/build-llvm/tools/llvm-shlib 
-I/«PKGBUILDDIR»/tools/llvm-shlib -I/«PKGBUILDDIR»/build-llvm/include 
-I/«PKGBUILDDIR»/include  -std=c++0x -gsplit-dwarf -Wl,-fuse-ld=gold 
-fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic 
-Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor 
-Wno-comment -Werror=date-time -std=c++11 -ffunction-sections 
-fdata-sections -O2 -g -DNDEBUG -fPIC-fno-exceptions -o 
CMakeFiles/LLVM.dir/libllvm.cpp.o -c 
/«PKGBUILDDIR»/tools/llvm-shlib/libllvm.cpp

[ 76%] Linking CXX shared library ../../lib/libLLVM-3.9.so
cd /«PKGBUILDDIR»/build-llvm/tools/llvm-shlib && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/LLVM.dir/link.txt --verbose=1
/usr/bin/g++-6  -fPIC -std=c++0x -gsplit-dwarf -Wl,-fuse-ld=gold -fPIC 
-fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter 
-Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic 
-Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor 
-Wno-comment -Werror=date-time -std=c++11 -ffunction-sections 
-fdata-sections -O2 -g -DNDEBUG  -Wl,-O3 -Wl,--gc-sections -Wl,-z,relro 
-Wl,-z,defs -shared -Wl,-soname,libLLVM-3.9.so.1 -o 
../../lib/libLLVM-3.9.so.1 CMakeFiles/LLVM.dir/libllvm.cpp.o 
-Wl,-rpath,"\$ORIGIN/../lib" -Wl,--whole-archive [big list of 
../../lib/libLLVM(something).a libraries] -lrt -ldl -ltinfo -lpthread 
-lz -lm
cd /«PKGBUILDDIR»/build-llvm/tools/llvm-shlib && /usr/bin/cmake -E 
cmake_symlink_library ../../lib/libLLVM-3.9.so.1 
../../lib/libLLVM-3.9.so.1 ../../lib/libLLVM-3.9.so

make[4]: Leaving directory '/«PKGBUILDDIR»/build-llvm'
[ 76%] Built target LLVM

i.e. the main libLLVM shared library doesn't use a version script at 
all.  (Some of its other libraries do have "version scripts", but these 
are used for their other function of limiting which symbols are public, 

Processed: Re: Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #848368 [src:llvm-toolchain-3.9] llvm-toolchain-3.9: Please add ELF symbols 
versions to the libraries
Added tag(s) patch.

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

Bug#851714: gitlab: Cannot push to gitlab repositories with git >= 2.11.0

[Jason Rhinelander]

Package: gitlab
Version: 8.13.6+dfsg2-2
Severity: grave

Dear Maintainer,

Gitlab repositories will no longer accept remote pushes to protected branches
(which is the default!) with git 2.11.0 installed on the gitlab system, failing
with:

remote: GitLab: You are not allowed to force push code to a protected branch on 
this project.
To (sitename):(user)/(repo).git
 ! [remote rejected] master -> master (pre-receive hook declined)

even for ordinary, non-forced pushes.

This is upstream bug https://gitlab.com/gitlab-org/gitlab-ce/issues/25301

Since gitlab seems pretty useless without the ability to push to a repository
by default, I've marked this grave.


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

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

Versions of packages gitlab depends on:
ii  adduser   3.115
ii  apache2 [httpd]   2.4.25-1
ii  asciidoctor   1.5.4-2
ii  bc1.06.95-9+b2
ii  bundler   1.13.6-2
ii  debconf [debconf-2.0] 1.5.59
ii  git   1:2.11.0-2
ii  gitlab-shell  3.6.6-1
ii  gitlab-workhorse  0.8.5+debian-3
ii  init-system-helpers   1.46
ii  libjs-chartjs 1.0.2-1
ii  libjs-clipboard   1.4.2-1
ii  libjs-fuzzaldrin-plus 0.3.1+git.20161008.da2cb58+dfsg-4
ii  libjs-graphael0.5+dfsg-1
ii  libjs-jquery-cookie   11-3
ii  libjs-jquery-history  11-3
ii  libjs-jquery-nicescroll   3.6.6-1
ii  lsb-base  9.20161125
ii  nodejs4.7.2~dfsg-1
ii  openssh-client1:7.4p1-5
ii  postfix [mail-transport-agent]3.1.3-6
ii  postgresql-client 9.6+178
ii  postgresql-client-9.6 [postgresql-client  9.6.1-2
ii  postgresql-contrib9.6+178
ii  rake  10.5.0-2
pn  redis-server  
ii  ruby  1:2.3.3
ii  ruby-ace-rails-ap 4.1.1-1
ii  ruby-activerecord-session-store   1.0.0-2
ii  ruby-acts-as-taggable-on  4.0.0-2
ii  ruby-addressable  2.4.0-1
ii  ruby-after-commit-queue   1.3.0-1
ii  ruby-akismet  2.0.0-1
ii  ruby-allocations  1.0.3-1+b2
ii  ruby-asana0.4.0-1
ii  ruby-attr-encrypted   3.0.1-2
ii  ruby-babosa   1.0.2-2
ii  ruby-base32   0.3.2-3
ii  ruby-bootstrap-sass   3.3.5.1-3
ii  ruby-browser  2.2.0-2
ii  ruby-cal-heatmap-rails3.6.0+dfsg-1
ii  ruby-carrierwave  0.10.0+gh-4
ii  ruby-charlock-holmes  0.7.3+dfsg-2+b3
ii  ruby-chronic  0.10.2-3
ii  ruby-chronic-duration 0.10.6-1
ii  ruby-coffee-rails 4.1.0-2
ii  ruby-coffee-script-source 1.10.0-1
ii  ruby-connection-pool  2.2.0-1
ii  ruby-creole   0.5.0-2
ii  ruby-d3-rails 3.5.6+dfsg-1
ii  ruby-default-value-for3.0.1-1
ii  ruby-devise   4.2.0-1
ii  ruby-devise-two-factor3.0.0-2
ii  ruby-diffy3.0.6-1
ii  ruby-doorkeeper   4.2.0-3
ii  ruby-dropzonejs-rails 0.7.1-1
ii  ruby-email-reply-parser   0.5.8-1
ii  ruby-fog-aws  0.12.0-1
ii  ruby-fog-azure0.0.2-1
ii  ruby-fog-core 1.42.0-1
ii  ruby-fog-google   0.3.2-1
ii  ruby-fog-local0.3.0-1
ii  ruby-fog-openstack0.1.6-4
ii  ruby-fog-rackspace0.1.1-4
ii  ruby-fogbugz  0.2.1-3
ii  ruby-font-awesome-rails   4.6.3.0-2
ii  ruby-gemnasium-gitlab-service 0.2.6-1
ii  ruby-gemojione3.1.0-2
ii  ruby-github-linguist  4.7.2-2
ii  ruby-github-markup1.5.0+dfsg-4
ii  ruby-gitlab-flowdock-git-hook 1.0.1-2
ii  ruby-gitlab-git  

Bug#851518: cinnamon won't start

[Carsten Kosthorst]

Hi,

I updated today and cinnamon is working again.

Thanks,

Carsten

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Fabian Greffrath]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Oh, I just remembered I once had a short conversation with RMS about
the distribution of the ghostscript fonts in binary Type1 format albeit
being licensed under the terms of the GPL:


Date: Sun, 13 Feb 2011 14:02:32 -0500
From: Richard Stallman 
To: Fabian Greffrath 
Subject: Re: [ghostscript] opentypefont

These fonts, however, are supplied in a binary, though editable, format
called PFB. In our opinion this file format corresponds to object code
and is clearly not "the preferred form of the work for making
modifications to it."

Karl Berry is the GNU expert on fonts.  He thinks that a Type 1 font
is suitable source code.

Could you tell me how you consider it falls short?

 We sure could do the transformations
from the binary font files, but it just felt "wrong". ;)

Would the files made by this transformation be different from the
source files that the developers might release?


Date: Mon, 14 Feb 2011 14:18:57 -0500
From: Richard Stallman 
To: Fabian Greffrath 
Subject: Re: [ghostscript] opentypefont

They are binary files, so you cannot create diffs between two 
versions. That is, the advantage of the openness of the source is void.

I see your point.  That is an aid for maintenance.

At the same time, the Type 1 font contains all the information
and can be converted automatically to the textual format.
So it is a valid source format.

Thus, I think these packages are valid and free as they are.
However, distributing the ASCII source would be an improvement.
So why not add that to your packages?
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlh+iIkACgkQy+qOlwzN
Wd+/ORAAr5M6KHbkBoUDNUkKu9KlKvC0hDJnaieJdxCUtuHH3sHGTmhAcpXbYjZo
VqqkeTkOrwiPvVs/vQcoQTyplE/TjKhLFC0w74PCUuY/dzPYm7kWmTNeyjdR/UCG
R2fsZNdLKu31/m/FEVAm7Cj3pp8o2DIRVNo75QabDJu6K4oIbVB2Okt4XE2BJJT5
nKHWYC+RthTiAUo9nlRJ+l3xm0zNdZngf99HrV654G0etheMoj9m2XPTeCU6pe1Z
VaegO7lb0/uBtnUm2fwhi6WEsIcx4wQqkXSaH1tlYgBqU4WkEKaRi15sXTmGvQV7
vj5c9Knvaz7AEDbB1cYh0a3M32qJ0v4UEUPUYeUxfRAqMy8l0shzZ7prxWDJBQas
CeqJxihL+aWXvRMhI7cUZ+0C953X2nSNuxnJ27na54NHkDzQ9dW62SDYB3fM6VxQ
8+UWjzbtuQBm+LyNe6VG27eu1ewZKovIGsewCl5GGms6ssbrdYbMHyj6wMF/jPqj
lBp15vDdaM72zXLbO2veNGqZ8tDtEWwwIo8kkm36ydx5lz1xYiwdWAgo8J8bF+O9
MK7oq71eEoZBB9HXC/XX2oXVOBcfvL3jVOoBu4lZf3efV6do5T/q0yn5+VTfrVSI
9grvjEl6dCa73GsWu4gkAdWr/NG3KD82Aoh3btOFt/FKS/u0uZ4=
=9XWx
-END PGP SIGNATURE-

Bug#851235: [debian-mysql] Bug#851235: Security fixes from the January 2017 CPU

[Lars Tangvald]

I've built and tested the updates, and will pass debdiffs on to the security 
team once the CVE list is available.

--
Lars
- norvald.ry...@oracle.com wrote:

> Source: mysql-5.7
> Version: 5.7.16-2
> Severity: grave
> Tags: security upstream fixed-upstream
> 
> The Oracle Critical Patch Update for January 2017 will be released on 
> 
> Tuesday, January 17. According to the pre-release announcement [1], it
>  
> will contain information about CVEs fixed in MySQL 5.7.17.
> 
> The CVE numbers will be available when the CPU is released.
> 
> Regards,
> 
> Norvald H. Ryeng
> 
> [1]
> http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> 
> ___
> pkg-mysql-maint mailing list
> pkg-mysql-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Fabian Greffrath]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney:
> Debian recipients should have equal access to make modifications to
> the work, build the work from modified source, and install the
> result.

All these modifications could be made to the OTF files *just as well*,
there is no advantage in using the same font format as upstream does
for their development. But I figure we are running in circles now. ;)

> The fact of the matter is the Glyphs data files are the preferred
> form
> of the work to make modifications.

Please note that the "preferred form for modification" is a term
exclusive to the GPL, it does not necessarily apply to fonts licensed
under any other license. Also, I am not sure if this is really exactly
what is meant by the "missing sources" paragraph of the REJECTS FAQs.

> It would reveal that Debian recipients do not have equal access to
> the source, for modifying building, and installing the work.

And thus you would file a bug requesting the removal of this package
from Debian main? Are you even aware of the vast consequences that this
overly strict interpretation of the "missing sources" paragraph may
have?

 - Fabian
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlh+g2oACgkQy+qOlwzN
Wd/hVA//X+zpFiwIdA2AUgAuQarC/zLV9RI1SHv4z+ASIvWyALzsLstxinD5fCOY
M6X6ySeU9ek7O/ZygHg1STgOzcBF42FvEIZscdFF6jMu5eH1zuW+t+8AoEJwMQLK
Uf50XrN0/ZR5DHHXKqMwfPZ39OOIJ5A9iYlHZEe8bkSYjbwF/HlIcUL53xddwOq9
bvETmHCeKJYst/QQsmR6sBNtYY2OV0onSoLxVxsbwLmlcKBA5Sg8DpjZBk407MFo
NGllJACTuEWXZDDypAdohEsln3/yw61F/B3LbakvobEnh4pT9iNiOlOCT5MuIOiu
yAs0tRFo5sH2rgt3HIlzfHqnCkm4U3+Y4+fHCXJTt5X9HnzC/GuExqP83o21fH3/
qRFSnx4hDfh/D89HiL/SRhj3mx5xGbjqvYuIuoRpH67loTw73nyv2qblv37eFXUg
uWTzoc3ln+/AQLaeFmzz8vZM2NPWff9PAKD+0QL9tbbRbAJsNpLZJbxXVC1sLP5Q
pyjESFt7DinDXPUWUgr1NXiaPJd9+sxcOnOje94B6cZpz3RWKsteTWWjJVmWfrbf
T5sVcwPo6ALHKX6MVXplO/prLKzvwivpO+U0wq9qKQe0M3PtJ+a6eZxKjOX/9re3
Qg0zsjagw2V/tYsszATyETAvU9gK21dVAJ8PDPiMduFsXdOV4WE=
=s0k/
-END PGP SIGNATURE-

Bug#851233: [debian-mysql] Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

I've built and tested the updates, and will pass debdiffs on to the security 
team once the CVE list is available.

--
Lars
- norvald.ry...@oracle.com wrote:

> Source: mysql-5.5
> Version: 5.5.53-0+deb8u1
> Severity: grave
> Tags: security upstream fixed-upstream
> 
> The Oracle Critical Patch Update for January 2017 will be released on 
> 
> Tuesday, January 17. According to the pre-release announcement [1], it
>  
> will contain information about CVEs fixed in MySQL 5.5.54.
> 
> The CVE numbers will be available when the CPU is released.
> 
> Regards,
> 
> Norvald H. Ryeng
> 
> [1]
> http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> 
> ___
> pkg-mysql-maint mailing list
> pkg-mysql-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#851234: [debian-mysql] Bug#851234: Security fixes from the January 2017 CPU

[Lars Tangvald]

I've built and tested the update, and will pass debdiffs on to the security 
team once the CVE list is available.

--
Lars
- norvald.ry...@oracle.com wrote:

> Source: mysql-5.6
> Version: 5.6.34-1
> Severity: grave
> Tags: security upstream fixed-upstream
> 
> The Oracle Critical Patch Update for January 2017 will be released on 
> 
> Tuesday, January 17. According to the pre-release announcement [1], it
>  
> will contain information about CVEs fixed in MySQL 5.6.35.
> 
> The CVE numbers will be available when the CPU is released.
> 
> Regards,
> 
> Norvald H. Ryeng
> 
> [1]
> http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> 
> ___
> pkg-mysql-maint mailing list
> pkg-mysql-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#850970: pvpgn: switch to build depend on the metapackage default-libmysqlclient-dev

[Dmitry Smirnov]

On Tuesday, 17 January 2017 12:54:44 AM AEDT Andreas Beckmann wrote:
> I just uploaded a NMU to DELAYED/2, fixing these issues. Please let me
> know if I should delay it longer.
> 
>  pvpgn (1.8.5-2.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Switch Build-Depends to default-libmysqlclient-dev.  (Closes: #850970)
> * Switch Suggests to default-mysql-* | virtual-mysql-*.  (Closes: #848482)
> * Use secure, canonical Vcs-* URLs.
> 
> Will push commits and tag to the git repo after the upload was accepted
> in the archive.

Thank you very much for your help, Andreas.

-- 
Cheers,
 Dmitry Smirnov.

---

Good luck happens when preparedness meets opportunity.


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

Processed: severity of 794331 is normal

[Debian Bug Tracking System]

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

> severity 794331 normal
Bug #794331 {Done: Holger Levsen } [piuparts] daptup: insane 
amounts of output on upgrades from testing or jessie to sid
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: unblock 851071 with 851041, unblock 851041 with 851071, forcibly merging 851071 851041

[Debian Bug Tracking System]

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

> unblock 851071 with 851041
Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under 
fakeroot
851071 was not blocked by any bugs.
851071 was blocking: 851041
Removed blocking bug(s) of 851071: 851041
> unblock 851041 with 851071
Bug #851041 [debhelper] f-el: FTBFS: test failures
851041 was blocked by: 851071
851041 was not blocking any bugs.
Removed blocking bug(s) of 851041: 851071
> forcemerge 851071 851041
Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under 
fakeroot
Bug #851041 [debhelper] f-el: FTBFS: test failures
Added indication that 851041 affects dh-elpa
Marked as fixed in versions debhelper/10.2.2.
Marked as found in versions debhelper/10.2.3.
Added tag(s) pending.
Merged 851041 851071
> thanks
Stopping processing here.

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

Processed: limit source to debhelper, tagging 851071

[Debian Bug Tracking System]

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

> limit source debhelper
Limiting to bugs with field 'source' containing at least one of 'debhelper'
Limit currently set to 'source':'debhelper'

> tags 851071 + pending
Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under 
fakeroot
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed (with 1 error): reassign 851041 to debhelper, forcibly merging 851071 851041

[Debian Bug Tracking System]

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

> # This is a bug in debhelper - not f-el (affects already set)
> reassign 851041 debhelper
Bug #851041 [src:f-el] f-el: FTBFS: test failures
Bug reassigned from package 'src:f-el' to 'debhelper'.
No longer marked as found in versions f-el/0.19.0-1.
Ignoring request to alter fixed versions of bug #851041 to the same values 
previously set
> forcemerge 851071 851041
Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under 
fakeroot
Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under 
fakeroot
Added tag(s) sid and stretch.
Bug #851041 [debhelper] f-el: FTBFS: test failures
Failed to forcibly merge 851071: It is nonsensical for a bug to block itself 
(or a merged partner): 851041.

> thanks
Stopping processing here.

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

Bug#851702: marked as done (linux-image-amd64: Important (and unacceptable) delay for providing updates for users of signed linux kernels)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 19:54:49 +
with message-id <1484682889.2998.61.ca...@decadent.org.uk>
and subject line Re: Bug#851702: linux-image-amd64: Important (and 
unacceptable) delay for providing updates for users of signed linux kernels
has caused the Debian Bug report #851702,
regarding linux-image-amd64: Important (and unacceptable) delay for providing 
updates for users of signed linux kernels
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.)


-- 
851702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 4.8+77~bpo8+1
Severity: critical
Tags: security
Justification: root security hole

Hi,

As of now two flavours of Linux kernels are released. The default ones are
signed ones while other unsigned kernels are available.

The problem is that there's a significant delay between the release of the
two
flavours, often more than one week, which exposes users of signed kernels to
critical vulnerabilities addressed in the newer kernel releases. The only
possible workaround is to switch on
-unsigned linux kernels, but this is messy and clearly unwanted.

I've raised an issue on BPO mailing list here : https://lists.debian.org
/debian-backports/2017/01/msg00033.html (the issue also applies to testing
and
unstable).

The answer is basically that :
1/ - unsigned kernels are only available for testing purposes
2/ - it is not possible to build simultaneously signed and unsigned kernels.

I'm okay with the latter as long as there's only a couple of hours between
the
two kernel releases. Now if we must wait more than one week to get the
signed
image it clearly reveals there's an issue in the signed image build process
which must be addressed before Stretch release.

Otherwise a possibility would be to use by default -unsigned image and
create
an optional linux-image-amd64-signed metapackage like the one which exists
for
grsec.



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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.8.0-0.bpo.2-amd64-unsigned [linux-image-4.8.
 4.8.15-2~bpo8+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 2017-01-17 at 20:17 +0100, Julien Aubin wrote:
> Package: linux-image-amd64
> Version: 4.8+77~bpo8+1
> Severity: critical
> Tags: security
> Justification: root security hole

Let's not play BTS wars.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert
Camus



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

Processed: Re: Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #850708 [pinentry-gtk2] pinentry-gtk-2 frequently fails to grab the pointer 
under fvwm
Bug 850708 cloned as bug 851707
> retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under awesome
Bug #851707 [pinentry-gtk2] pinentry-gtk-2 frequently fails to grab the pointer 
under fvwm
Changed Bug title to 'pinentry-gtk-2 frequently fails to grab the keyboard 
under awesome' from 'pinentry-gtk-2 frequently fails to grab the pointer under 
fvwm'.

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

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

[Vincent Bernat]

Control: clone -1 -2
Control: retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under 
awesome

<#secure method=pgpmime mode=sign>
 ❦ 17 janvier 2017 20:34 +0100, Vincent Lefevre  :

>> ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not 
>> viewable (3)
>> 
>> ** (pinentry-gtk-2:21583): WARNING **: it took 4097 tries to grab the 
>> keyboard
>> 
>> ** (pinentry-gtk-2:21583): WARNING **: it took 990 tries to grab the pointer
>> ERR 83886179 Operation cancelled 
>
> This is a different bug (or not a bug at all). The problem you have is
> that it cannot grab the keyboard (while this bug was about an incorrect
> test about the pointer grab), and all the expected 4096 tries are done.
> This may not be enough (IMHO the tries should be time-based, with a
> nanosleep between them, until some timeout).

OK, let me clone this bug and continue from here.
-- 
Terminate input by end-of-file or marker, not by count.
- The Elements of Programming Style (Kernighan & Plauger)

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

[Vincent Lefevre]

On 2017-01-17 20:21:05 +0100, Vincent Bernat wrote:
> Here is the output I get:
> 
> OK Pleased to meet you
> 
> ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not viewable 
> (3)
> 
> ** (pinentry-gtk-2:21583): WARNING **: it took 4097 tries to grab the keyboard
> 
> ** (pinentry-gtk-2:21583): WARNING **: it took 990 tries to grab the pointer
> ERR 83886179 Operation cancelled 

This is a different bug (or not a bug at all). The problem you have is
that it cannot grab the keyboard (while this bug was about an incorrect
test about the pointer grab), and all the expected 4096 tries are done.
This may not be enough (IMHO the tries should be time-based, with a
nanosleep between them, until some timeout).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

[Vincent Bernat]

 ❦ 17 janvier 2017 12:13 +0100, Vincent Lefevre  :

>> I have the same behaviour with awesome. My setup didn't change since
>> quite some time but this behaviour is recent while neither awesome nor
>> pinentry-gtk2 has been updated. I got the behavior immediately after
>> rebooting. Applying the patch from Werner doesn't fix the problem for
>> me.
>
> What warning and error messages do you get with the following test?
>
>   echo getpin | pinentry-gtk-2
>
> (This is the one suggested by GI, the easiest way to reproduce the bug
> and get the warning and error messages.)

Here is the output I get:

OK Pleased to meet you

** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not viewable 
(3)

** (pinentry-gtk-2:21583): WARNING **: it took 4097 tries to grab the keyboard

** (pinentry-gtk-2:21583): WARNING **: it took 990 tries to grab the pointer
ERR 83886179 Operation cancelled 
-- 
Identify bad input; recover if possible.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#851702: linux-image-amd64: Important (and unacceptable) delay for providing updates for users of signed linux kernels

[Julien Aubin]

Package: linux-image-amd64
Version: 4.8+77~bpo8+1
Severity: critical
Tags: security
Justification: root security hole

Hi,

As of now two flavours of Linux kernels are released. The default ones are
signed ones while other unsigned kernels are available.

The problem is that there's a significant delay between the release of the
two
flavours, often more than one week, which exposes users of signed kernels to
critical vulnerabilities addressed in the newer kernel releases. The only
possible workaround is to switch on
-unsigned linux kernels, but this is messy and clearly unwanted.

I've raised an issue on BPO mailing list here : https://lists.debian.org
/debian-backports/2017/01/msg00033.html (the issue also applies to testing
and
unstable).

The answer is basically that :
1/ - unsigned kernels are only available for testing purposes
2/ - it is not possible to build simultaneously signed and unsigned kernels.

I'm okay with the latter as long as there's only a couple of hours between
the
two kernel releases. Now if we must wait more than one week to get the
signed
image it clearly reveals there's an issue in the signed image build process
which must be addressed before Stretch release.

Otherwise a possibility would be to use by default -unsigned image and
create
an optional linux-image-amd64-signed metapackage like the one which exists
for
grsec.



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

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.8.0-0.bpo.2-amd64-unsigned [linux-image-4.8.
 4.8.15-2~bpo8+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Bug#850266: marked as done (Missing headers in -dev package)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 19:04:21 +
with message-id 
and subject line Bug#850266: fixed in libsrtp2 2.0.0+20161214-1
has caused the Debian Bug report #850266,
regarding Missing headers in -dev package
to be marked as done.

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

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


-- 
850266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsrtp2-dev
Severity: serious
Version: 2.0.0-1

Hi,

it seems like the headers in the crypto subdirectory should also be
included, at least partially. Without this, constants like
  SRTP_AES_128_ICM
  SRTP_NULL_CIPHER
and others are missing and they seem to be needed for usage of the API.

Also various functions from the srtp_priv.h header that was available
in < 2.0 seem to be needed, at least the software I'm looking at is
using them. For example srtp_get_stream(), for which there seems to be
no alternative.


Best regards,
Sebastian

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: libsrtp2
Source-Version: 2.0.0+20161214-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libsrtp2 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, 17 Jan 2017 19:47:06 +0100
Source: libsrtp2
Binary: libsrtp2-dev libsrtp2-1 libsrtp2-1-dbg libsrtp2-docs
Architecture: source amd64 all
Version: 2.0.0+20161214-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Jonas Smedegaard 
Description:
 libsrtp2-1 - Secure RTP (SRTP) and UST Reference Implementations - shared libr
 libsrtp2-1-dbg - Secure RTP (SRTP) and UST Reference Implementations - 
debugging s
 libsrtp2-dev - Secure RTP (SRTP) and UST Reference Implementations - 
development
 libsrtp2-docs - Secure RTP (SRTP) and UST Reference Implementations - 
documentati
Closes: 850266
Changes:
 libsrtp2 (2.0.0+20161214-1) unstable; urgency=medium
 .
   [ upstream ]
   * Development snapshot from stable git branch.
 Highlights:
 + Make srtp_driver compile for MIPS.
 + Rename srtp_crypto_kernel_replace_cipher_type as
   srtp_replace_cipher_type, and similarly for auth_type.
 + Install cipher.h, auth.h and crypto_types.h.
   Closes: Bug#850266. Thanks to Sebastian Dröge.
 + Changes for OpenSSL 1.1.0 compatibility.
 .
   [ Jonas Smedegaard ]
   * Drop upstream cherry-picked patch since applied.
   * Unfuzz patch 1005.
   * Update copyright info:
 + Extend coverage of autotools files.
 + Extend coverage of Debian packaging.
   * Update watch file:
 + Bump to version 4.
 + Add usage comment.
 + Use github pattern from documentation.
   * Modernize git-buildpackage config: Filter any .git* file.
   * Update symbols: 2 renamed.
Checksums-Sha1:
 72efa58a10f225a14d6c3e8d71fe61fa8c67168a 2338 libsrtp2_2.0.0+20161214-1.dsc
 48d73762561d713b1ba299cedac52228dea04d20 272954 
libsrtp2_2.0.0+20161214.orig.tar.gz
 9aa268fe676c17dccc7daf166e570fd4c7c3a908 15296 
libsrtp2_2.0.0+20161214-1.debian.tar.xz
 9489ba9aac879bad41ea944737d408614e27af3e 103674 
libsrtp2-1-dbg_2.0.0+20161214-1_amd64.deb
 401c262c0ce9604080b5af5b1012624fc33f5361 69122 
libsrtp2-1_2.0.0+20161214-1_amd64.deb
 0859d100e6c52b1b14d5af1eec9e6c8518f8a633 82888 
libsrtp2-dev_2.0.0+20161214-1_amd64.deb
 98d072627b8a121e04320c716ecc6923cb93c575 279988 
libsrtp2-docs_2.0.0+20161214-1_all.deb
 97becdafcd305d8b865927ee8635adabca27a4ac 10570 
libsrtp2_2.0.0+20161214-1_amd64.buildinfo
Checksums-Sha256:
 bba0f2fd26065ede342b00ad17c1db9a997d24c9ff90c6869178f9585d2def90 2338 
libsrtp2_2.0.0+20161214-1.dsc
 d14ba8f5e020ec561e4e2829bf3a4fa771a42d6605061cef41d5c8b767ae5c14 272954 
libsrtp2_2.0.0+20161214.orig.tar.gz
 3a3ba82faf48cda69ae915172611025ee32e73b261cb8fff0c50019a1c302c88 15296 
libsrtp2_2.0.0+20161214-1.debian.tar.xz

Bug#851579: lcdproc: fails to install: post-installation script returned error exit status 10

[Dominique Dumont]

On Monday, 16 January 2017 15:54:36 CET you wrote:
> during a test with piuparts I noticed your package failed to install.

The root cause is now fixed in dh_cme_upgrade with [1]. I will upload 
a new lcdproc package once cme is updated.

All the best

[1] https://anonscm.debian.org/cgit/pkg-perl/packages/cme.git/commit/?id=fb45650

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

Bug#851552: marked as done (cowsay-off: Replaces and Breaks must be updated to 3.03+dfsg2-1 was 3.03+dfsg1-13)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 18:18:54 +
with message-id 
and subject line Bug#851552: fixed in cowsay 3.03+dfsg2-3
has caused the Debian Bug report #851552,
regarding cowsay-off: Replaces and Breaks must be updated to 3.03+dfsg2-1 was 
3.03+dfsg1-13
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.)


-- 
851552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cowsay-off
Version: 3.03+dfsg2-2
Severity: normal

Dear Maintainer,

As you have moved files ( bong.cow and beavis.zen.cow) from cowsay to
cowsay-off you must update the Replaces and Breaks fileds to 3.03+dfsg2-1

Christian

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages cowsay-off depends on:
ii  cowsay  3.03+dfsg2-2

cowsay-off recommends no packages.

cowsay-off suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cowsay
Source-Version: 3.03+dfsg2-3

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

Debian distribution maintenance software
pp.
Tony Maillefaud  (supplier of updated cowsay 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: Mon, 16 Jan 2017 21:23:47 +0100
Source: cowsay
Binary: cowsay cowsay-off
Architecture: source all
Version: 3.03+dfsg2-3
Distribution: unstable
Urgency: high
Maintainer: Tony Maillefaud 
Changed-By: Tony Maillefaud 
Description:
 cowsay - configurable talking cow
 cowsay-off - configurable talking cow (offensive cows)
Closes: 851552
Changes:
 cowsay (3.03+dfsg2-3) unstable; urgency=high
 .
   * Update Depends, Replaces and Breaks version
- bong and beavis owned by cowsay and cowsay-off (closes: #851552)
Checksums-Sha1:
 496039f94e4e5723e144edfa1395965a099e918d 2145 cowsay_3.03+dfsg2-3.dsc
 756bd57c4ace24e45e65d54961425a74f02ac136 12748 
cowsay_3.03+dfsg2-3.debian.tar.xz
 49f81cc7aff9ea52792611dc487046a792c51bb5 7816 cowsay-off_3.03+dfsg2-3_all.deb
 a10df93bfb5c68f6f2e69ebc5f34a7cfee4a291b 20070 cowsay_3.03+dfsg2-3_all.deb
 cac79ecc87328ef8f7510d5b2c7bea8f8db36ed5 4858 
cowsay_3.03+dfsg2-3_amd64.buildinfo
Checksums-Sha256:
 2ee8f85470668fe7a4cc24d5b87a97da0a562e494d80f3a0658f7184434ec94e 2145 
cowsay_3.03+dfsg2-3.dsc
 e2f3768bb5101b4da4fe749ffdf92a03041eff9f6d9cf68bf13c7f26ace8a7e2 12748 
cowsay_3.03+dfsg2-3.debian.tar.xz
 71f6544f5658182b571a996b9e3dd8d915e654faddf41db6541f45209abe1b4c 7816 
cowsay-off_3.03+dfsg2-3_all.deb
 858d5116a60ba2acef9f30e08c057ab18b1bd6df5ca61c233b6b7492fbf6b831 20070 
cowsay_3.03+dfsg2-3_all.deb
 0273cdce7718ecbf59662774e132e119947833cb0d94255b78247d1f707d 4858 
cowsay_3.03+dfsg2-3_amd64.buildinfo
Files:
 902fc6c588734a3e3fd78a31969e3b3f 2145 games optional cowsay_3.03+dfsg2-3.dsc
 953f38f73bf901c1937a772cac59b1ed 12748 games optional 
cowsay_3.03+dfsg2-3.debian.tar.xz
 af312196f4aaf6c0455d0276b3b67472 7816 games optional 
cowsay-off_3.03+dfsg2-3_all.deb
 27967ddb76b2c394a0714480b7072ab3 20070 games optional 
cowsay_3.03+dfsg2-3_all.deb
 82283b4313d7f45b243457ac765c576e 4858 games optional 
cowsay_3.03+dfsg2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAlh+WdJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD
NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8
mNGv2A//WciIAni3GpnJZZIFYNRWqg+j3clIvuRCm1pGAcahVBAQO8nbIgsbMSYF
txBbAL4x6bh+ctwApl67s9SObnTzYEppyI64b6dUSK0KvOwVTUDsVtcoth82gWBb
E06ZARUF+nKecqyU9gJCQ3bWR5cAxlTATdE1qjZO5bfceGT53u7j0jZVKxiBu7qJ
XrwsUp3H02s781yms1PYj8vBsEGeXxMAJdrmrZ3DsI0JoI+L495S916llpsxYL+l
gq4/Htdml4Uxbe86bHL8r07j7jZEiA5+3kEblI4cxgO4f8/LpEhZfkMdFK+zG0+A

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages] [and 1 more messages]

[Josh Triplett]

On Tue, 17 Jan 2017 13:35:14 + Ian Jackson 
 wrote:
> [1] AIUI this is when your laptop suspends to RAM, but after a timeout
> or when the battery is low, wakes up so that it can suspend to disk.

Linux implements hybrid sleep by going ahead and writing the hibernation
image out, then suspending to RAM.  That makes it take longer to sleep,
but it doesn't have to wake up later on a timer (likely in an enclosed
bag).  If you wake it up while still suspended to RAM, it can wake up
fast and ignore the hibernation image; if it runs out of battery and
loses power, then when you power it back on it'll resume from the
hibernation image and still not lose state.

Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code

[Adrian Bunk]

Control: severity -1 normal

On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
> Control: severity -1 grave
>...
> If I understand the test results from 
> https://ci.debian.net/packages/o/ocrad/unstable/amd64/ > correct, the
> library is no longer usable.
>...

That's mostly unrelated, and the error message is misleading.

What is needed to fix these test results is to have the library compiled 
with PIE, and the rebuild triggered by my 0.25-2 QA upload will do the 
job (even a binNMU would have been sufficient).

After that the library is again usable for linking into binaries.

This bug here is about compiling the static library with -fPIC for 
making it suitable for inclusion in shared libraries.

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

Processed: Re: Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable 
code
Severity set to 'normal' from 'grave'

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

Bug#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

[Adrian Bunk]

Control: reopen -1
Control: block 811576 by -1

On Tue, Jan 03, 2017 at 01:24:09PM +, Dimitri John Ledkov wrote:
> On Wed, 30 Nov 2016 00:11:01 +0100 Sebastian Andrzej Siewior
>  wrote:
> > On 2016-11-26 11:31:49 [+0200], Adrian Bunk wrote:
> > > Package: libtspi-dev
> > > Version: 0.3.14+fixed1-1
> > > Severity: serious
> > > Control: block 827061 by -1
> > >
> > > libtspi-dev must not force OpenSSL 1.1 on packages that
> > > are not ready for 1.1
> > >
> > > At least opencryptoki (#828465) and tpm-tools (#828577)
> > > are not even compiling with OpenSSL 1.1
> > >
> > > Options to solve this issue:
> > > - fix all r-(b)deps to compile and work with OpenSSL 1.1, or
> > > - use OpenSSL 1.0.2 in stretch
> >
> > tpm-tools does not build and has hints to solve the openssl issue. So it
> > is actually just opencryptoki.
> >
> > Sebastian
> 
> opencryptoki is also now fine.

Unfortunately tpm-tools is not fine, and even fixing the other trivial 
build error #811576 depends on this.

> Regards,
> 
> Dimitri.

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

Processed: Re: Bug#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #845729 {Done: Dimitri John Ledkov } [libtspi-dev] 
libtspi-dev must not force OpenSSL 1.1 on packages that are not ready
'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 opencryptoki/3.6.1+dfsg-1.
> block 811576 by -1
Bug #811576 [tpm-tools] FTBFS with GCC 6: statement indented as if it were 
guarded by
811576 was not blocked by any bugs.
811576 was not blocking any bugs.
Added blocking bug(s) of 811576: 845729

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

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Ben Finney]

On 17-Jan-2017, Fabian Greffrath wrote:
> Paul Wise wrote:
> > […] The issue is that there is no Free Software in Debian main
> > that can build the OTF from source. […]
> 
> But the OTF format itself is just as suitable a source format for
> fonts as any other format. Why is it so important what upstream has
> chosen?

Debian recipients should have equal access to make modifications to
the work, build the work from modified source, and install the result.

The preferred form of this work for making modifications to it is the
Glyphs data files. So, for Debian recipients to have equal access to
make modifications to this work, Debian must include that form of this
work, and equivalent tools for building the work from that source
form.

> Thought experiment: Would it feel more "correct" if I forked the
> firacode upstream project, converted their OTF files into
> fontforge's SFD format, checked these into a GIT repo and then
> distributed these?

That would not change the fact of what is the source form of this
work.

The fact of the matter is the Glyphs data files are the preferred form
of the work to make modifications.

Whether another series of automated transformations is made from that
source form, does not change the fact that it remains the source form
of the work.

> Now, what would happen if URW++ suddenly revealed that they used
> proprietary software to create the fonts and that the files that we
> have are not the canonical sources. Why should it make a difference
> at all?

It would reveal that Debian recipients do not have equal access to
the source, for modifying building, and installing the work.

-- 
 \   “I went to a general store. They wouldn't let me buy anything |
  `\ specifically.” —Steven Wright |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Processed: Bug does not seem to be limited to latest packages

[Debian Bug Tracking System]

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

> reassign 840931 src:libimobiledevice
Bug #840931 [libimobiledevice6] libimobiledevice4 GnuTLS settings broken with 
iOS 10
Bug #847977 [libimobiledevice6] libimobiledevice6: GnuTLS error: Error in the 
pull function (iOS 10.1.1)
Bug reassigned from package 'libimobiledevice6' to 'src:libimobiledevice'.
Bug reassigned from package 'libimobiledevice6' to 'src:libimobiledevice'.
No longer marked as found in versions libimobiledevice/1.2.0+dfsg-3.
No longer marked as found in versions libimobiledevice/1.2.0+dfsg-3.
Ignoring request to alter fixed versions of bug #840931 to the same values 
previously set
Ignoring request to alter fixed versions of bug #847977 to the same values 
previously set
> affects 840931 libimobiledevice4
Bug #840931 [src:libimobiledevice] libimobiledevice4 GnuTLS settings broken 
with iOS 10
Bug #847977 [src:libimobiledevice] libimobiledevice6: GnuTLS error: Error in 
the pull function (iOS 10.1.1)
Added indication that 840931 affects libimobiledevice4
Added indication that 847977 affects libimobiledevice4
> affects 840931 libimobiledevice6
Bug #840931 [src:libimobiledevice] libimobiledevice4 GnuTLS settings broken 
with iOS 10
Bug #847977 [src:libimobiledevice] libimobiledevice6: GnuTLS error: Error in 
the pull function (iOS 10.1.1)
Added indication that 840931 affects libimobiledevice6
Added indication that 847977 affects libimobiledevice6
> thanks
Stopping processing here.

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

Bug#846422: marked as done (fauhdlc: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 16:04:42 +
with message-id 
and subject line Bug#846422: fixed in fauhdlc 20130704-1.1
has caused the Debian Bug report #846422,
regarding fauhdlc: add libfl-dev to Build-Depends
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.)


-- 
846422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fauhdlc
Severity: important
User: helm...@debian.org
Usertags: libfldep

fauhdlc will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since fauhdlc uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: fauhdlc
Source-Version: 20130704-1.1

We believe that the bug you reported is fixed in the latest version of
fauhdlc, 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.
Adrian Bunk  (supplier of updated fauhdlc 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: Tue, 17 Jan 2017 17:35:42 +0200
Source: fauhdlc
Binary: fauhdlc libfauhdli-dev
Architecture: source
Version: 20130704-1.1
Distribution: unstable
Urgency: medium
Maintainer: FAUmachine Team 
Changed-By: Adrian Bunk 
Description:
 fauhdlc- experimental VHDL compiler and interpreter
 libfauhdli-dev - interpreter library and development files for fauhdli
Closes: 835106 846422
Changes:
 fauhdlc (20130704-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to working maintainer address.
   * Remove the obsolete DM-Upload-Allowed.
   * Add libfl-dev to the build dependencies. (Closes: #846422)
   * Add FTBFS fix from Stefan Potyra. (Closes: #835106)
Checksums-Sha1:
 90f600ebcc5fadc2155d078706c80e7718ba6c5f 1928 fauhdlc_20130704-1.1.dsc
 6f9b495854fa8688a605bafd5e53ed61967dc5eb 4192 
fauhdlc_20130704-1.1.debian.tar.xz
Checksums-Sha256:
 9f6bcdd0a787695e43bed94da9ccf60993c2ae463d063bda1078a2b80044c3b3 1928 
fauhdlc_20130704-1.1.dsc
 ca9820bd973153856f10b6dfffe254132090b1e84e16fca669cb33ed7724285f 4192 
fauhdlc_20130704-1.1.debian.tar.xz
Files:
 0c7dd31a801ad82cf9924ab1b04e 1928 devel optional fauhdlc_20130704-1.1.dsc
 44d26813661d2028b0acdd5253d12f33 4192 devel optional 
fauhdlc_20130704-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh+O2sACgkQiNJCh6LY
mLFm9A//VGuqogrvqMcdZZ/4mggMGRmBhmsVmOaVj2XOpdgqUw9sRlVK5LRTWYqx
G96QEvk1+DdSOAMByrgfpPaKWtECvafQEIMK6QL7bmWFE4b7BgpYWyJ2z4fyOwgp
9mRl96DxBTEfTU2/QygqatThNTcSAjyq20WL8O3J11W0sYTBwG7ewY2HE8+l174/
SAb3Ra0ln+IylvNRmpDs7ssxGNrOFlGFa6SLyxeAXLM32hmmbKxSQtowgs1bRUuL
Ev2cfICYsL99xYJIR/gPDQPfemMKSTovoC3IKqNZQ+Zbb5jcycZxf2SUt4sbslU/
Uk3Vp9VoVXpZNXXvz1xlDqJw0CPQFYumxzwaWLfyoejtQ4E0VZrfx2SxG/tqLIBw
imvSZgQ7ogaOExj6nH9LNdxGjKZfasKF9uZTfvXAp0IaunlqBuaNnQLlfpzPLyRb
b2DqZK9Xm44l9Xd0uE6+D+dmipfkamZq1tDs9NrpUciTlHs1SG5Cy4zy9NLQXHzD
Sd5vqiVUv9VT7Qx8ZfKtQQPqqMU3VqWn2meRdnHFmRmd38NHHY1OUeDUXC9mZvT2
GfRXTUrvYN6jzeROCRWWwPI0EB7JNeSLMxb8Opd0i4Yhfapwq9bKrOd+MHVJhOOO
Uy+UjkZANL44YaLMN3jwMSyxYSSc1Y7QIUwTzrK547vAMYxkaOs=
=N5Ri
-END PGP SIGNATURE End Message ---

Bug#835106: marked as done (fauhdlc: FTBFS: expected ')' before 'istream')

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 16:04:42 +
with message-id 
and subject line Bug#835106: fixed in fauhdlc 20130704-1.1
has caused the Debian Bug report #835106,
regarding fauhdlc: FTBFS: expected ')' before 'istream'
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.)


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

>From my pbuilder build log (on amd64):

...
./gen_parser_gen.py FAUhdlParser.yy.in FAUhdlParser.yy
flex FAUhdlScanner.l
Detect bison version 3.0.4
Generating parser file FAUhdlParser.yy from FAUhdlParser.yy.in
bison FAUhdlParser.yy
FAUhdlParser.yy:13.9-27: warning: %define variable 'parser_class_name'
requires '{...}' values [-Wdeprecated]
 %define "parser_class_name" "FAUhdlParser"
 ^^^
/usr/bin/make  all-am
make[3]: Entering directory '/build/fauhdlc-20130704/frontend/newparser'
g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual
-Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare
-Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast
-U_FORTIFY_SOURCE -DPACKAGE_NAME=\"fauhdlc\"
-DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20130704\"
-DPACKAGE_STRING=\"fauhdlc\ 20130704\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20130704\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I.  -I ../.. -I.
-Wno-conversion -Wno-old-style-cast -Wno-parentheses -g -O2 -MT
libnewparser_a-FAUhdlScanner.o -MD -MP -MF
.deps/libnewparser_a-FAUhdlScanner.Tpo -c -o
libnewparser_a-FAUhdlScanner.o `test -f 'FAUhdlScanner.cpp' || echo
'./'`FAUhdlScanner.cpp
g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual
-Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare
-Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast
-U_FORTIFY_SOURCE -DPACKAGE_NAME=\"fauhdlc\"
-DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20130704\"
-DPACKAGE_STRING=\"fauhdlc\ 20130704\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20130704\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I.  -I ../.. -I.
-Wno-conversion -Wno-old-style-cast -Wno-parentheses -g -O2 -MT
libnewparser_a-FAUhdlParser.tab.o -MD -MP -MF
.deps/libnewparser_a-FAUhdlParser.tab.Tpo -c -o
libnewparser_a-FAUhdlParser.tab.o `test -f 'FAUhdlParser.tab.cc' ||
echo './'`FAUhdlParser.tab.cc
g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual
-Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare
-Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast
-U_FORTIFY_SOURCE -DPACKAGE_NAME=\"fauhdlc\"
-DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20130704\"
-DPACKAGE_STRING=\"fauhdlc\ 20130704\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20130704\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I.  -I ../.. -I.
-Wno-conversion -Wno-old-style-cast -Wno-parentheses -g -O2 -MT
libnewparser_a-ParserDriver.o -MD -MP -MF
.deps/libnewparser_a-ParserDriver.Tpo -c -o
libnewparser_a-ParserDriver.o `test -f 'ParserDriver.cpp' || echo
'./'`ParserDriver.cpp
In file included from ParserDriver.cpp:13:0:
../../frontend/newparser/FAUhdlScanner.hpp:26:12: error: expected ')'
before 'istream'
   FLEX_STD istream* arg_yyin = 0,
^~~
ParserDriver.cpp: In member function 'void
yy::ParserDriver::parse(const string&, const char*)':
ParserDriver.cpp:107:57: error: no matching function for call to
'yy::FAUhdlScanner::FAUhdlScanner(std::ifstream*, std::ostream*)'
  this->scanner = new FAUhdlScanner(, ::cout);
 ^
In file included from ParserDriver.cpp:13:0:
../../frontend/newparser/FAUhdlScanner.hpp:21:7: note: candidate:
yy::FAUhdlScanner::FAUhdlScanner()
 class FAUhdlScanner : public yyFlexLexer {
   ^
../../frontend/newparser/FAUhdlScanner.hpp:21:7: note:   candidate
expects 0 arguments, 2 provided
In file included from 

Bug#847580: util-vserver testing migration is delayed by #850765

[Adrian Bunk]

The util-vserver testing migration is delayed by #850765

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#828524: qterm testing migration is delayed by #851412

[Adrian Bunk]

The qterm testing migration is delayed by #851412

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

Processed: #851412 affects qterm package

[Debian Bug Tracking System]

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

> affects 851412 + qterm
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Added indication that 851412 affects qterm
Added indication that 851505 affects qterm
Added indication that 851549 affects qterm
Added indication that 851642 affects qterm
> affects 851412 - qevercloud
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Removed indication that 851412 affects qevercloud
Removed indication that 851505 affects qevercloud
Removed indication that 851549 affects qevercloud
Removed indication that 851642 affects qevercloud
> thanks
Stopping processing here.

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

Bug#850244: marked as done (reconserver: FTBFS: reConServer.cxx:941:164: error: no matching function for call to 'resip::HEPSipMessageLoggingHandler::HEPSipMessageLoggingHandler(resip::Data&, int&, in

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:54:38 +
with message-id 
and subject line Bug#850244: fixed in reconserver 0.13.3-1
has caused the Debian Bug report #850244,
regarding reconserver: FTBFS: reConServer.cxx:941:164: error: no matching 
function for call to 
'resip::HEPSipMessageLoggingHandler::HEPSipMessageLoggingHandler(resip::Data&, 
int&, int&)'
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.)


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

Your package failed to build on ppc64el (twice), blocking the resiprocate 
transition.

reConServer.cxx: In member function 'virtual int 
recon::ReConServerProcess::main(int, char**)':
reConServer.cxx:941:164: error: no matching function for call to 
'resip::HEPSipMessageLoggingHandler::HEPSipMessageLoggingHandler(resip::Data&, 
int&, int&)'
   
profile->setTransportSipMessageLoggingHandler(SharedPtr(new
 HEPSipMessageLoggingHandler(captureHost, capturePort, captureAgentID)));

Full logs at:

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

Emilio

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

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

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

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated reconserver package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jan 2017 21:45:28 +0100
Source: reconserver
Binary: reconserver
Architecture: source amd64
Version: 0.13.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Daniel Pocock 
Description:
 reconserver - lightweight SIP conferencing service
Closes: 850244
Changes:
 reconserver (0.13.3-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update Build-Deps for reSIProcate 1.11.0~beta1. (Closes: #850244)
Checksums-Sha1:
 c8c1bc46bb6874ce0de0ef0d2a866e694c1fd314 2090 reconserver_0.13.3-1.dsc
 8a40834f7bb467f6ffe1a23309bfdfd3ce177de9 80920 reconserver_0.13.3.orig.tar.bz2
 7085beb0e0a556082c46401d4cbd38dede678e4b 5048 
reconserver_0.13.3-1.debian.tar.xz
 d48607e0e65d7320f4aadbd92b64319023c42c29 1228358 
reconserver-dbgsym_0.13.3-1_amd64.deb
 a1c93bcbbd23195202bc6fec3689c3636451c763 6074 
reconserver_0.13.3-1_amd64.buildinfo
 75230cbfa3175e815def9e083807b1a7f7f8bb23 145014 reconserver_0.13.3-1_amd64.deb
Checksums-Sha256:
 b787aa7ba27a52846ec4921a0a01feaf1da47c3f05ab83f042475da773c31a3f 2090 
reconserver_0.13.3-1.dsc
 5b78ac399459fb3c2f92a0eedc5670b3dd39504ed93dd9816a1338cadf32c2c2 80920 
reconserver_0.13.3.orig.tar.bz2
 1ad8c37ffe21b44e953541b9cd6cadbf5f839d9e282a5fa052d7bc4e4ef017f1 5048 
reconserver_0.13.3-1.debian.tar.xz
 939c4f399298ea77065d1786371326dcfe188b2b5a1ead3b48f15c670921ce05 1228358 
reconserver-dbgsym_0.13.3-1_amd64.deb
 e09e1de017f561e4703ed08c1421ceaff2f8ee16cc3a1b6e885a1e596f189dbb 6074 
reconserver_0.13.3-1_amd64.buildinfo
 df650b7c2c1398e4f665c929a42996ffc39c9002965858638aa7eeb7e446c3ec 145014 
reconserver_0.13.3-1_amd64.deb
Files:
 25357952de0980599ddd73d555443bb5 2090 net extra reconserver_0.13.3-1.dsc
 b2444cb96c16f12efa9b6fe703c8ce47 80920 net extra 
reconserver_0.13.3.orig.tar.bz2
 e029e8e1e9ba9ba987ccc0c9deda354d 5048 net extra 
reconserver_0.13.3-1.debian.tar.xz
 1ee657180dfe3331bc474247a5c6bbf3 1228358 debug extra 
reconserver-dbgsym_0.13.3-1_amd64.deb
 

Processed: #851412 affects dbus (SIGSEGV), thus affects qevercloud build on mips64el

[Debian Bug Tracking System]

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

> affects 851412 + qevercloud
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Added indication that 851412 affects qevercloud
Added indication that 851505 affects qevercloud
Added indication that 851549 affects qevercloud
Added indication that 851642 affects qevercloud
> thanks
Stopping processing here.

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

Processed: Re: Bug#753927: usbredir: Broken patch disallows dpkg-source unpack

[Debian Bug Tracking System]

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

> # already marked as fixed in 0.7-1, in stable and sid
> close 753927
Bug #753927 [src:usbredir] usbredir: Broken patch disallows dpkg-source unpack
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#846771: python-traits: FTBFS randomly

[Debian Bug Tracking System]

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

> severity 846771 important
Bug #846771 [src:python-traits] python-traits: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 2.7 returned exit code 13
Severity set to 'important' from 'serious'
> retitle 846771 python-traits: FTBFS randomly (failing tests)
Bug #846771 [src:python-traits] python-traits: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 2.7 returned exit code 13
Changed Bug title to 'python-traits: FTBFS randomly (failing tests)' from 
'python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 
returned exit code 13'.
> thanks
Stopping processing here.

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

Bug#850948: marked as done (needrestart,piuparts: needrestart hangs -> piupart fails -> debian-design blocked)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:33:40 +
with message-id 
and subject line Bug#850948: fixed in needrestart 2.11-1
has caused the Debian Bug report #850948,
regarding needrestart,piuparts: needrestart hangs -> piupart fails -> 
debian-design blocked
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.)


-- 
850948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: needrestart,piuparts
Severity: serious

This bugreport is tracking debian-design not entering testing.

Background:

 a) needrestart sometimes hangs during install.
 b) Needrestart hanging is caught by piuparts and treated as a failure.
 c) debian-design depends on needrestart and is blocked from testing.

Issue a) is tracked as bug#826044, but as severity important.

This bugreport is tracking the combined issue of a) + b) + c).

Please therefore reassign and/or merge as appropriate, but only as long
as the severity reflects the actual treatment of debian-design.


 - Jonas
--- End Message ---
--- Begin Message ---
Source: needrestart
Source-Version: 2.11-1

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated needrestart 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, 17 Jan 2017 16:03:16 +0100
Source: needrestart
Binary: needrestart
Architecture: source all
Version: 2.11-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 needrestart - check which daemons need to be restarted after library upgrades
Closes: 844283 845996 850948
Changes:
 needrestart (2.11-1) unstable; urgency=high
 .
   * New upstream release.
 - Add display-manager 'lxdm' to override.
   Closes: #845996
 - Fix wrong regex quotation in default configuration file.
   Closes: #844283
   * Remove merged patch 01-spelling-error.
   * Add patch 01-use-invoke-rc-d to honor policy-rc.d.
 Closes: #850948
   * Add a recommend on libpam-systemd to make user session work reliable.
Checksums-Sha1:
 0778908bd019234e4a5b089bdc2085a01781b2cd 1751 needrestart_2.11-1.dsc
 142e9c1346881704fcf83367e93ab0c2f326f023 52156 needrestart_2.11.orig.tar.gz
 9533d323b3abafa4d52ddf0f7ca5ca8676c9834e 6788 needrestart_2.11-1.debian.tar.xz
 ceba02de471c0b4ef63ab2fad71dee2ba708ff63 45866 needrestart_2.11-1_all.deb
 f47700a1cd1554786eec8ce37bb915d64cac6359 4892 
needrestart_2.11-1_amd64.buildinfo
Checksums-Sha256:
 b288c5475866e9c1f6cfdc3859838b60e06d728950075021252650cecea9 1751 
needrestart_2.11-1.dsc
 5c7c322e551ae5de9442ac4915d6c9bc47303a22bc8fb234b953d4a158e65777 52156 
needrestart_2.11.orig.tar.gz
 55151d4f6876058d2ace3d605b3e11684d0adaa00c57baf2aa5f9f36b4d67d89 6788 
needrestart_2.11-1.debian.tar.xz
 54570628f974c87d7e9d12ee75febc882cfd52228c1a3b375854bc45ce3f4b87 45866 
needrestart_2.11-1_all.deb
 2bae54539abb36ec67c305db621751813ec3a71bad0315549cde40a71cd3a2e2 4892 
needrestart_2.11-1_amd64.buildinfo
Files:
 57b61c8ea6d170a18b18ad944dda95aa 1751 admin optional needrestart_2.11-1.dsc
 cd1836542e17e774f47d7ab78398ae05 52156 admin optional 
needrestart_2.11.orig.tar.gz
 862af512ecc27f1252c6a1cea4e7015e 6788 admin optional 
needrestart_2.11-1.debian.tar.xz
 19b8af4205c3a9ac7c2388f8984382dc 45866 admin optional 
needrestart_2.11-1_all.deb
 564f3d9b8b88dea7291d651bb5082fd3 4892 admin optional 
needrestart_2.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfjK/AAoJEBLZsEqQy9jkNBgP/2U+Ygme5q+U7dY848R2I83p
KLVsEnXlOlUyft66Rh+h+Quq2qxHu4nCgJO5MWewFBmZteqi1VRyTE7sA09C49fO
FjhSusYy1zJB1V+kDTmZ2Et7y+5abjdeVa6IyrH4Fc8SkR/K34vSahOtHDzdHnHq
TSwvm7SmATM7kaLUjB4bRQfSyE/3hCxZRjc8rkzfGcBwrmv3Tu8UmdTuXJNRjA8W
41X4KENWtPfhFokJ6BMyx2vSScIcmIJIy9arBA2rUY+cki8RDiH15NOkpTJstG2T
Y5nz+0gVuEUKrcMpH4NXbErkWr3ftxp3TcXZqhPTWBDohoeIWFhq7kpU8+W2pqEV

Bug#850765: marked as done (util-vserver: fails to remove: postrm called with unknown argument `remove')

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:08:10 +
with message-id 
and subject line Bug#850765: fixed in util-vserver 0.30.216-pre3120-1.4
has caused the Debian Bug report #850765,
regarding util-vserver: fails to remove: postrm called with unknown argument 
`remove'
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.)


-- 
850765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-vserver
Version: 0.30.216-pre3120-1.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing util-vserver (0.30.216-pre3120-1.3) ...
  can not change context: migrate kernel feature missing and 'compat' API 
disabled: Function not implemented
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of stop.
  postrm called with unknown argument `remove'
  dpkg: error processing package util-vserver (--remove):
   subprocess installed post-removal script returned error exit status 1


cheers,

Andreas


util-vserver_0.30.216-pre3120-1.3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: util-vserver
Source-Version: 0.30.216-pre3120-1.4

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated util-vserver 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: Tue, 17 Jan 2017 16:03:26 +0200
Source: util-vserver
Binary: util-vserver
Architecture: source
Version: 0.30.216-pre3120-1.4
Distribution: unstable
Urgency: medium
Maintainer: Carlos Alberto Lopez Perez 
Changed-By: Adrian Bunk 
Description:
 util-vserver - user-space tools for Linux-VServer virtual private servers
Closes: 770362 850765
Changes:
 util-vserver (0.30.216-pre3120-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix postrm failure introduced in the previous upload.
 (Closes: #850765)
   * Add Brazilian Portuguese debconf translation
 from Adriano Rafael Gomes. (Closes: #770362)
Checksums-Sha1:
 3e4fc4b542dffee930b93080b2aea99b50381d0f 2258 
util-vserver_0.30.216-pre3120-1.4.dsc
 876d52769e5733fd2cf7201475cfaf7a0611e231 44584 
util-vserver_0.30.216-pre3120-1.4.debian.tar.xz
Checksums-Sha256:
 43cd994ab991d352f68f4f9fb87fd8186539e36e38ee25285dea8d80a4e5f05b 2258 
util-vserver_0.30.216-pre3120-1.4.dsc
 096191dccb9192a09d263c5ce6afb985d4d9eca4fd844f56d8d716c4bea9447c 44584 
util-vserver_0.30.216-pre3120-1.4.debian.tar.xz
Files:
 9da75c6bcdc2d0976c324d6cfd7643c8 2258 net optional 
util-vserver_0.30.216-pre3120-1.4.dsc
 3956ef7af2e21fa99e7581229da31b89 44584 net optional 
util-vserver_0.30.216-pre3120-1.4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh+JpUACgkQiNJCh6LY
mLE+Hw//S+aUdNXJHLS/fAKf9K3yL7WSeQ2bw/hMkO4TQcGErivv5TxG0qXI60Mg
dK5gmALXShFNyiOCL3Q12zkA+lszGxZXzkJIbqBPdfflyruacxp3e9Kp8N2RYV4Z
SlfyMEqAvLEBgDXuQX7wGYpjh64ItydtEd68ijFBpx5Iga9Fi7Wb6stIF48s3VRE
9UtOHgzqZG3XoS0xdAknlix6mtnXN4tHayDLClKMNqwT6az87M67so1sQL2uTb3Y
lM9sTkwKRsLSe2tkUE5fEP6Mw8rG/hKAr9qgWD5g0/mbpuHUyCxZQJ3Uld/eE2xU
1wUSQCQyNWwA/Blct3ptv0l59lxcqQMn7QhciX9nEOmxWFOAmpRWlOhP94H07sl0
D+/q0gFgxxSUmL0BrwHG+p7x4uRc1saNgRz7MKxdpfHvOcqT1oUZ0kDcyvbYLuxK
nq8NlTCUJKPzK8MMM9bplmZosZ2Tgt8GxnmIYGoFD2/j0Kj08TEElcjkkTRwNSOj
wDq/onL9G7rRTtye+Dhr7MqoskUygrqtI+VX/+BoSe5yIdXeUqmJmckYbHggChrS
4K4EjEMjBXVqayCo0SNP9U5mD15vGiVo3acKtVtdfTJqlxiiA4CMlntrECEx0fW+
UNw/V7SrMGdyxtN/FU4yHyGxQdONRiq2uclLBapB7jtOLHj2UxM=
=zz8n
-END PGP SIGNATURE End Message ---

Bug#851063: marked as done (bind9: CVE-2016-9147: An error handling a query response containing inconsistent DNSSEC information could cause an assertion failure)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:00:15 +
with message-id 
and subject line Bug#851063: fixed in bind9 1:9.10.4-P5-1
has caused the Debian Bug report #851063,
regarding bind9: CVE-2016-9147: An error handling a query response containing 
inconsistent DNSSEC information could cause an assertion failure
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.)


-- 
851063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.9.5.dfsg-4
Severity: grave
Tags: upstream security
Justification: user security hole

Hi,

the following vulnerability was published for bind9.

CVE-2016-9147[0]:
|An error handling a query response containing inconsistent DNSSEC
|information could cause an assertion failure

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9147
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9147
[1] https://kb.isc.org/article/AA-01440/0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.4-P5-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 06:04:12 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns165 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export165 libdns-export165-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source amd64 all
Version: 1:9.10.4-P5-1
Distribution: experimental
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export165 - Exported DNS Shared Library
 libdns-export165-udeb - Exported DNS library for debian-installer (udeb)
 libdns165  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 828082 830810 831796 839010 842858 851062 851063 851065
Changes:
 bind9 (1:9.10.4-P5-1) experimental; urgency=medium
 .
   * New upstream: 9.10.4-P5
 - Fixes CVE-2016-2775: crash in lwresd due to a long query name
   (closes: #831796).
 - Fixes CVE-2016-2776: maliciously crafted query can cause named to crash
   (closes: #839010).
 - Fixes CVE-2016-6170: improper zone size limits (closes: 

Bug#851062: marked as done (bind9: CVE-2016-9444: An unusually-formed DS record response could cause an assertion failure)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:00:15 +
with message-id 
and subject line Bug#851062: fixed in bind9 1:9.10.4-P5-1
has caused the Debian Bug report #851062,
regarding bind9: CVE-2016-9444: An unusually-formed DS record response could 
cause an assertion failure
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.)


-- 
851062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.9.5.dfsg-4
Severity: grave
Tags: upstream security
Justification: user security hole

Hi,

the following vulnerability was published for bind9.

CVE-2016-9444[0]:
|An unusually-formed DS record response could cause an assertion
|failure

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9444
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9444
[1] https://kb.isc.org/article/AA-01441/0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.4-P5-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 06:04:12 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns165 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export165 libdns-export165-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source amd64 all
Version: 1:9.10.4-P5-1
Distribution: experimental
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export165 - Exported DNS Shared Library
 libdns-export165-udeb - Exported DNS library for debian-installer (udeb)
 libdns165  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 828082 830810 831796 839010 842858 851062 851063 851065
Changes:
 bind9 (1:9.10.4-P5-1) experimental; urgency=medium
 .
   * New upstream: 9.10.4-P5
 - Fixes CVE-2016-2775: crash in lwresd due to a long query name
   (closes: #831796).
 - Fixes CVE-2016-2776: maliciously crafted query can cause named to crash
   (closes: #839010).
 - Fixes CVE-2016-6170: improper zone size limits (closes: #830810).
 - Fixes CVE-2016-8864: incorrect handling of a DNAME record 

Bug#851065: marked as done (bind9: CVE-2016-9131: A malformed response to an ANY query can cause an assertion failure during recursion)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:00:16 +
with message-id 
and subject line Bug#851065: fixed in bind9 1:9.10.4-P5-1
has caused the Debian Bug report #851065,
regarding bind9: CVE-2016-9131: A malformed response to an ANY query can cause 
an assertion failure during recursion
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.)


-- 
851065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.9.5.dfsg-4
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for bind9.

CVE-2016-9131[0]:
|A malformed response to an ANY query can cause an assertion failure
|during recursion

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9131
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9131
[1] https://kb.isc.org/article/AA-01439/0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.4-P5-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 06:04:12 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns165 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export165 libdns-export165-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source amd64 all
Version: 1:9.10.4-P5-1
Distribution: experimental
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export165 - Exported DNS Shared Library
 libdns-export165-udeb - Exported DNS library for debian-installer (udeb)
 libdns165  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 828082 830810 831796 839010 842858 851062 851063 851065
Changes:
 bind9 (1:9.10.4-P5-1) experimental; urgency=medium
 .
   * New upstream: 9.10.4-P5
 - Fixes CVE-2016-2775: crash in lwresd due to a long query name
   (closes: #831796).
 - Fixes CVE-2016-2776: maliciously crafted query can cause named to crash
   (closes: #839010).
 - Fixes CVE-2016-6170: improper zone size limits (closes: #830810).
 - Fixes CVE-2016-8864: incorrect 

Bug#839010: marked as done (bind9: CVE-2016-2776: Assertion failure in query processing)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:00:15 +
with message-id 
and subject line Bug#839010: fixed in bind9 1:9.10.4-P5-1
has caused the Debian Bug report #839010,
regarding bind9: CVE-2016-2776: Assertion failure in query processing
to be marked as done.

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

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


-- 
839010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.10.3.dfsg.P4-10.1
Tags: security
Severity: grave

ISC has released a security alert at

  

Relevant information from this report follows:

CVE:   CVE-2016-2776
Document Version:  2.0
Posting date:  2016-09-27
Program Impacted:  BIND
Versions affected: 9.0.x -> 9.8.x, 9.9.0->9.9.9-P2, 9.9.3-S1->9.9.9-S3,
   9.10.0->9.10.4-P2, 9.11.0a1->9.11.0rc1
Severity:  High
Exploitable:   Remotely

Description:

   Testing by ISC has uncovered a critical error condition which
   can occur when a nameserver is constructing a response.  A defect
   in the rendering of messages into packets can cause named to
   exit with an assertion failure in buffer.c while constructing a
   response to a query that meets certain criteria.

   This assertion can be triggered even if the apparent source
   address isn't allowed to make queries (i.e. doesn't match
   'allow-query').

Impact:

   All servers are vulnerable if they can receive request packets from
any source.
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.4-P5-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 06:04:12 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns165 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export165 libdns-export165-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source amd64 all
Version: 1:9.10.4-P5-1
Distribution: experimental
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export165 - Exported DNS Shared Library
 libdns-export165-udeb - Exported DNS library for debian-installer (udeb)
 libdns165  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 828082 830810 831796 839010 842858 851062 851063 851065
Changes:
 bind9 (1:9.10.4-P5-1) experimental; 

Bug#842858: marked as done (bind9: CVE-2016-8864: A problem handling responses containing a DNAME answer can lead to an assertion failure)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:00:15 +
with message-id 
and subject line Bug#842858: fixed in bind9 1:9.10.4-P5-1
has caused the Debian Bug report #842858,
regarding bind9: CVE-2016-8864: A problem handling responses containing a DNAME 
answer can lead to an assertion failure
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.)


-- 
842858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.9.5.dfsg-9
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for bind9.

CVE-2016-8864[0]:
|A problem handling responses containing a DNAME answer can lead to an
|assertion failure

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8864
[1] https://kb.isc.org/article/AA-01434

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.4-P5-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 06:04:12 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns165 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export165 libdns-export165-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source amd64 all
Version: 1:9.10.4-P5-1
Distribution: experimental
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export165 - Exported DNS Shared Library
 libdns-export165-udeb - Exported DNS library for debian-installer (udeb)
 libdns165  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 828082 830810 831796 839010 842858 851062 851063 851065
Changes:
 bind9 (1:9.10.4-P5-1) experimental; urgency=medium
 .
   * New upstream: 9.10.4-P5
 - Fixes CVE-2016-2775: crash in lwresd due to a long query name
   (closes: #831796).
 - Fixes CVE-2016-2776: maliciously crafted query can cause named to crash
   (closes: #839010).
 - Fixes CVE-2016-6170: improper zone size limits (closes: #830810).
 - Fixes CVE-2016-8864: incorrect handling of a DNAME record can cause
   named to crash (closes: #842858).
 - Fixes CVE-2016-9131: maliciously crafted response to an ANY query can
   

Bug#828082: marked as done (bind9: FTBFS with openssl 1.1)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 15:00:15 +
with message-id 
and subject line Bug#828082: fixed in bind9 1:9.10.4-P5-1
has caused the Debian Bug report #828082,
regarding bind9: FTBFS with openssl 1.1
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.)


-- 
828082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 9.10.3.dfsg.P4-10
Severity: important
Control: block 827061 by -1

Hi,

Your package is failing to build with openss 1.1:
checking for OpenSSL library... no
yes
checking for using OpenSSL for hash functions... no
[...]
checking for OpenSSL library... using OpenSSL from /usr/lib and /usr/include
checking whether linking with OpenSSL works... yes
[...]
configure: error: OpenSSL has unsupported dynamic loading
no
[...]
BIND 9 is being built without cryptography support. This means it will
not have DNSSEC support. Use --with-openssl, or --with-pkcs11 and
--enable-native-pkcs11 to enable cryptography.


Kurt
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.4-P5-1

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jan 2017 06:04:12 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns165 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export165 libdns-export165-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source amd64 all
Version: 1:9.10.4-P5-1
Distribution: experimental
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export165 - Exported DNS Shared Library
 libdns-export165-udeb - Exported DNS library for debian-installer (udeb)
 libdns165  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 828082 830810 831796 839010 842858 851062 851063 851065
Changes:
 bind9 (1:9.10.4-P5-1) experimental; urgency=medium
 .
   * New upstream: 9.10.4-P5
 - Fixes CVE-2016-2775: crash in lwresd due to a long query name
   (closes: #831796).
 - Fixes CVE-2016-2776: maliciously crafted query can cause named to crash
   (closes: #839010).
 - Fixes CVE-2016-6170: improper zone size limits (closes: #830810).
 - Fixes CVE-2016-8864: incorrect handling of a DNAME record can cause
   named to crash (closes: #842858).
 - Fixes CVE-2016-9131: maliciously crafted response to 

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Fabian Greffrath]

Paul Wise wrote:
> The issue isn't that they currently use proprietary software to
> convert to OTF format. The issue is that there is no Free Software in
> Debian main that can build the OTF from source. This is a clear
> violation of Debian policy and that indicates the package needs to be
> in contrib.

But the OTF format itself is just as suitable a source format for fonts as
any other format. Why is it so important what upstream has chosen? It is
not that font composition is a human-readable-to-binary-one-way-road like
compilation C source files into object code or HTML documentation to PDF.

> In this case, if you look at the commits to the github repo, there is
> a clear canonical source format and that is the proprietary Glyphsapp
> format that can only be converted to OTF by the proprietary Glyphsapp
> software.

Thought experiment: Would it feel more "correct" if I forked the firacode
upstream project, converted their OTF files into fontforge's SFD format,
checked these into a GIT repo and then distributed these?

> I would vastly prefer the correct source of PNG images to be
> distributed in source packages and the PNG images created at build
> time to the current, fairly horrible, situation. Choice of source
> format is up to upstream though.

Another thought experiment: We have a fairly prominent example of
binary-only Type1 fonts available in the gsfonts package. They are
licensed under the GPL, so there is even a "preferred form for
modification" term that applies to them. Nobody knows how URW++ created
these fonts and what tools they used, nevertheless a number of viable
forks have been developed from them, among them GNU FreeFont and TeX Gyre.
Now, what would happen if URW++ suddenly revealed that they used
proprietary software to create the fonts and that the files that we have
are not the canonical sources. Why should it make a difference at all?

 - Fabian

Bug#851412: #851412: libsystemd segfaults on mips64el

[gregor herrmann]

Control: affects -1 src:iodine

On Sun, 15 Jan 2017 14:12:06 +0100, Christian Hofstaedtler wrote:

> Control: affects -1 + pdns pdns-recursor
> 
> pdns and pdns-recursor link against libsystemd, and this bug causes
> both of them to just segfault on startup on mips64el.

I'm pretty sure that the build failure of iodine on mips64el:
https://buildd.debian.org/status/fetch.php?pkg=iodine=mips64el=0.7.0-7=1484496165
is caused by the same issue. ("-l systemd" comes from the `sh ../src/osflags 
Linux link`
in the last line before the segfault.)
 
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
   `-   BOFH excuse #123:  user to computer ratio too high. 

Processed: Re: Bug#851412: #851412: libsystemd segfaults on mips64el

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:iodine
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Added indication that 851412 affects src:iodine
Added indication that 851505 affects src:iodine
Added indication that 851549 affects src:iodine
Added indication that 851642 affects src:iodine

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

Bug#851649: (no subject)

[Barry Warsaw]

I have no objections, but I don't have time right now to do it.  Piotr did the
1.7.0-1 upload so please verify with him.

Processed: Re: Bug#851642: perl: FTBFS on mips64el: dist/threads/t/join.t failure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:systemd
Bug #851642 [perl] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Bug reassigned from package 'perl' to 'src:systemd'.
No longer marked as found in versions perl/5.24.1-1.
Ignoring request to alter fixed versions of bug #851642 to the same values 
previously set
> forcemerge 851412 -1
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Added indication that 851642 affects 
dbus,xvfb,gnome-online-accounts,pdns,postgresql-9.6,src:octave,pdns-recursor,src:psqlodbc,src:neovim,xrdp
Marked as found in versions systemd/232-10.
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Removed indication that 851549 affects pdns, src:psqlodbc, postgresql-9.6, 
dbus, xvfb, xrdp, pdns-recursor, src:octave, src:neovim, and 
gnome-online-accounts
Added indication that 851549 affects 
dbus,xvfb,gnome-online-accounts,pdns,postgresql-9.6,src:octave,pdns-recursor,src:psqlodbc,src:neovim,xrdp
Removed indication that 851412 affects xrdp, xvfb, dbus, postgresql-9.6, pdns, 
src:psqlodbc, gnome-online-accounts, src:neovim, src:octave, and pdns-recursor
Added indication that 851412 affects 
dbus,xvfb,gnome-online-accounts,pdns,postgresql-9.6,src:octave,pdns-recursor,src:psqlodbc,src:neovim,xrdp
Removed indication that 851505 affects src:octave, pdns-recursor, 
gnome-online-accounts, src:neovim, dbus, xvfb, postgresql-9.6, src:psqlodbc, 
pdns, and xrdp
Added indication that 851505 affects 
dbus,xvfb,gnome-online-accounts,pdns,postgresql-9.6,src:octave,pdns-recursor,src:psqlodbc,src:neovim,xrdp
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Merged 851412 851505 851549 851642
> affects 851412 perl procps
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Added indication that 851412 affects perl and procps
Added indication that 851505 affects perl and procps
Added indication that 851549 affects perl and procps
Added indication that 851642 affects perl and procps

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

Bug#851642: perl: FTBFS on mips64el: dist/threads/t/join.t failure

[James Cowgill]

Control: reassign -1 src:systemd
Control: forcemerge 851412 -1
Control: affects 851412 perl procps

Hi,

On 17/01/17 07:37, Niko Tyni wrote:
> Package: perl
> Version: 5.24.1-1
> Severity: serious
> X-Debbugs-Cc: debian-m...@lists.debian.org
> 
> This package failed to build on mips64el:
> 
>  dist/threads/t/join ... Died at 
> t/join.t line 134.
>  FAILED--expected 20 tests, saw 10
> 
> This has now happened twice on different buildds so it doesn't seem to be 
> transient.
> 
>  https://buildd.debian.org/status/logs.php?pkg=perl=mips64el

This is the mips64el systemd bug. Line 134 if dist/threads/t/join.t
causes ps to be invoked, but ps segfaults immediately due to #851412
because it links against libsystemd.so.

Reassigning and merging with the existing bug.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#838671: openchangeproxy: uninstallable in jessie, broken by samba

[Andreas Beckmann]

Followup-For: Bug #838671

openchange also FTBFS in stable:

Compiling mapiproxy/dcesrv_mapiproxy.c with -fPIC
mapiproxy/dcesrv_mapiproxy.c: In function 'mapiproxy_op_connect':
mapiproxy/dcesrv_mapiproxy.c:135:5: error: dereferencing pointer to incomplete 
type
b->assoc_group_id = dce_call->pkt.u.bind.assoc_group_id;
 ^
mapiproxy/dcesrv_mapiproxy.c:138:5: error: dereferencing pointer to incomplete 
type
b->assoc_group_id = dce_call->pkt.u.alter.assoc_group_id;
 ^
mapiproxy/dcesrv_mapiproxy.c:155:55: error: 'struct dcerpc_pipe' has no member 
named 'assoc_group_id'
   dce_call->context->assoc_group->id = private->c_pipe->assoc_group_id;
   ^
mapiproxy/dcesrv_mapiproxy.c:170:55: error: 'struct dcerpc_pipe' has no member 
named 'assoc_group_id'
   dce_call->context->assoc_group->id = private->c_pipe->assoc_group_id;
   ^
Makefile:124: recipe for target 'mapiproxy/dcesrv_mapiproxy.po' failed
make[2]: *** [mapiproxy/dcesrv_mapiproxy.po] Error 1


Andreas

Bug#821530: marked as done (libsparkline-php: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 13:49:15 +
with message-id 
and subject line Bug#821530: fixed in sparkline-php 0.2-6
has caused the Debian Bug report #821530,
regarding libsparkline-php: PHP 7.0 Transition
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.)


-- 
821530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsparkline-php
Version: 0.2-5
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The libsparkline-php package currently depends on php5 php5-gd .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: libsparkline-php -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUqBXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH1sgQANFZYMiq6xkgI+2ByZkE0OaO
iPj1O5wvgOQ0Z+zy6mC4oUnKjPT03DWBnUjTEzQA5JVpyTnAL1bE3wabYUn0qbUv
Fq20lmLjUkP0aWxF+j4jDEZSqIsY/RRnAp0SfF03CNMKuSX/6Fc12NRCEyIvtuNH
9DgIXcrUqZ6OmjPnNiUphg1U6t/fphLKjZ7ZASf52VXCntHcQ5YCqHWu7P4U56h7

Bug#848289: marked as done (ruby-riddle: (build-)depends on mysql-{client,server})

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 13:49:10 +
with message-id 
and subject line Bug#848289: fixed in ruby-riddle 1.5.12-4
has caused the Debian Bug report #848289,
regarding ruby-riddle: (build-)depends on mysql-{client,server}
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.)


-- 
848289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-riddle
Version: 1.5.12-3
Severity: serious

Your package build-depends on mysql-server. Since we're transitioning to
mariadb as the default mysql provider, you should switch your build
dependency to default-mysql-server | virtual-mysql-server.

Cheers,
Emilio

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

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

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

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

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

Debian distribution maintenance software
pp.
Andrew Lee (李健秋)  (supplier of updated ruby-riddle 
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, 17 Jan 2017 09:30:44 +0800
Source: ruby-riddle
Binary: ruby-riddle
Architecture: source all
Version: 1.5.12-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Andrew Lee (李健秋) 
Description:
 ruby-riddle - Ruby API for Sphinx Search
Closes: 841601 848289
Changes:
 ruby-riddle (1.5.12-4) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Use https:// in Vcs-* fields
 .
   [ Christian Hofstaedtler ]
   * Switch to default-mysql-server (Closes: #848289)
   * Bump Standards-Version to 3.9.8 and dh compat level to 10
   * Work around mariadb grant issue (Closes: #841601)
   * Add procps to Build-Depends, tests use "ps"
 .
   [ Andrew Lee (李健秋) ]
   * Releasing debian version 1.5.12-4.
Checksums-Sha1:
 058c3fdcdbccaef472a8af533db80163cd02671e 2158 ruby-riddle_1.5.12-4.dsc
 9168dc78e3032a4b0e38a9dc73154e3bfb5cf3a5 3340 
ruby-riddle_1.5.12-4.debian.tar.xz
 864e0129f5322c40bf7f8ec9fa19f78ea0a85923 27642 ruby-riddle_1.5.12-4_all.deb
 83e2266ecea3cbabfb44e4e92d980a6b59341e17 7324 
ruby-riddle_1.5.12-4_amd64.buildinfo
Checksums-Sha256:
 e5fc5fd4a3893472808fef1fdea89e3aaea791a49f8fa08f3cc03a2c3424a478 2158 
ruby-riddle_1.5.12-4.dsc
 9ca30e63da706d1ba547ec06b65d15e24d7215c573393f9f7663ca7e1b45060b 3340 
ruby-riddle_1.5.12-4.debian.tar.xz
 6ba53d3c96c4325127c0b71a21141d22e4d74af7ea8f63aef1fe96f99ddae0bb 27642 
ruby-riddle_1.5.12-4_all.deb
 e1551b2d4fbc245e9f3311f38544a64cec0ad0915b191f9d93e158b07b7227fd 7324 
ruby-riddle_1.5.12-4_amd64.buildinfo
Files:
 e077c4dd626995115753f1149248606a 2158 ruby optional ruby-riddle_1.5.12-4.dsc
 31c3b25860c5753b60889b6839d5876e 3340 ruby optional 
ruby-riddle_1.5.12-4.debian.tar.xz
 4b72a1097b52ef29e8f4381b15a4a32a 27642 ruby optional 
ruby-riddle_1.5.12-4_all.deb
 d5b7705c7eff4157d00215ffaf8f5cc4 7324 ruby optional 
ruby-riddle_1.5.12-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfXYEAAoJEOfL4VKsF/lzUgQP/0Ip+aOS4S2zfMKcWifx9zU6
pdTj9TFG6YG9KbYFa0rmLxMcCc2qULNHSrXvIqOzhJCObMNn7L3aYQ8PTuoW9OPE
9OS2PS7oMW/dhImdmd5dAOFgXc2/OrMEZLkGIK4kt2TJipIqk6LivcH/lCHtw9+T
GnEoTR7xXfh7lLNTd+uei9FwTC+K4Gx4E+/440MjR+xnh1zclhXiny2r3T5R3izw
8LxVY4NLpg/Qkrd63y3hEg9Vfn2g3cb+zgHzNlCUHCoH5xu3cWMy4Eg9t3yxyAG/
j3CvQOSanstBTt+HJX+CxlGAVzTesmq7TKInj/Xf4D0rQ88EYc8x5KDNe3ygZb+e
8w9VryUGnXKUx5EgYrUk7yaEE82pAfEaGho4ZpwWhAKUp5ZcjDE88NBwlnELXlZM
cEAp6DlbMZu+0MmMKZCTEK/vGRcRf/A3XZL7mrstWV0yI8NfxKX76ST+7KhvVcMk

Bug#841601: marked as done (ruby-riddle: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 13:49:10 +
with message-id 
and subject line Bug#841601: fixed in ruby-riddle 1.5.12-4
has caused the Debian Bug report #841601,
regarding ruby-riddle: FTBFS: ERROR: Test "ruby2.3" failed.
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.)


-- 
841601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-riddle
Version: 1.5.12-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-riddle/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"riddle\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-riddle/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-riddle/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> ./debian/start_mysqld_and_run.sh ruby2.3 -S rspec
> mysql_install_db: [ERROR] unknown option '--force'
> 2016-10-21 01:26:44 [ERROR]   Unrecognized options
> rake aborted!
> Command failed with status (1): [./debian/start_mysqld_and_run.sh ruby2.3 
> -...]
> /<>/debian/ruby-tests.rake:5:in `block in '
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.3" failed.

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/ruby-riddle_1.5.12-3_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: ruby-riddle
Source-Version: 1.5.12-4

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

Debian distribution maintenance software
pp.
Andrew Lee (李健秋)  (supplier of updated ruby-riddle 
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, 17 Jan 2017 09:30:44 +0800
Source: ruby-riddle
Binary: ruby-riddle
Architecture: source all
Version: 1.5.12-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Andrew Lee (李健秋) 
Description:
 ruby-riddle - Ruby API for Sphinx Search
Closes: 841601 848289
Changes:
 ruby-riddle (1.5.12-4) unstable; 

Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

[Arthur de Jong]

Control: found -1 nss-pam-ldapd/0.9.4-2
Control: tags -1 + pending

On Mon, 2017-01-16 at 12:55 +0100, Thomas Wallrafen wrote:
> See the attached ncslcd.conf file (the version before the
> upgrade).

Thanks for providing the info.

I tracked the bug down to a problem in the parsing of the configuration
file. The bug itself was present in nss-pam-ldapd at least since 0.7.13
but it could only be triggerred since 0.9.4-2 if you have a
tls_cacertdir option specified.

This option will most likely be ignored on Debian because I understand
that GnuTLS does not use it. It is also not configured by default which
probably explained why this was not found earlier.

You can probbaly safely remove or comment out the tls_cacertdir option
in nslcd.conf without any ill effects.

This fix is pretty simple and a patch is attached for reference. I will
prepare a fix for unstable and try to get a fix into jessie soon.

Thanks,

-- 
-- arthur - adej...@debian.org - https://people.debian.org/~adejong --
Index: debian/changelog
===
--- debian/changelog	(revision 2159)
+++ debian/changelog	(working copy)
@@ -3,8 +3,10 @@
   * recommend ca-certificate which is needed due to adding tls_cacertfile by
 default (see #750949) and the checking of tls_cacertfile in 0.9.7
 (closes: #836720)
+  * fix parsing of nslcd.conf tls_cacert option in package configuration
+(closes: #851564)
 
- -- Arthur de Jong   Wed, 07 Sep 2016 23:10:45 +0200
+ -- Arthur de Jong   Tue, 17 Jan 2017 14:42:28 +0100
 
 nss-pam-ldapd (0.9.7-1) unstable; urgency=medium
 
Index: debian/nslcd.config
===
--- debian/nslcd.config	(revision 2157)
+++ debian/nslcd.config	(working copy)
@@ -27,7 +27,7 @@
   if [ -z "$RET" ] || [ "$force" = "force" ]
   then
 # the first part avoids getting options that have an optional MAP parameter
-cfgfile_value=`sed -n '/^'"$cfg_param"'[[:space:]]\(aliases\|ethers\|group\|hosts\|netgroup\|networks\|passwd\|protocols\|rpc\|services\|shadow\)[[:space:]]/!s/^'"$cfg_param"'[[:space:]]*\([^[:space:]].*[^[:space:]]\)[[:space:]]*$/\1/ip' "$cfgfile" | head -n 1`
+cfgfile_value=`sed -n '/^'"$cfg_param"'[[:space:]][[:space:]]*\(aliases\|ethers\|group\|hosts\|netgroup\|networks\|passwd\|protocols\|rpc\|services\|shadow\)[[:space:]]/!s/^'"$cfg_param"'[[:space:]][[:space:]]*\([^[:space:]].*[^[:space:]]\)[[:space:]]*$/\1/ip' "$cfgfile" | head -n 1`
 [ -n "$cfgfile_value" ] && db_set "$debconf_param" "$cfgfile_value"
   fi
   # we're done


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

Processed: Re: Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

[Debian Bug Tracking System]

Processing control commands:

> found -1 nss-pam-ldapd/0.9.4-2
Bug #851564 [nslcd] nslcd fails to start: postinst sets tls_cacertdir wrong
Marked as found in versions nss-pam-ldapd/0.9.4-2.
> tags -1 + pending
Bug #851564 [nslcd] nslcd fails to start: postinst sets tls_cacertdir wrong
Added tag(s) pending.

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

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages] [and 1 more messages]

[Ian Jackson]

Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things 
[and 1 more messages]"):
> This seems to solve the problem for me, thank you very much! (And I hope
> you can get this in for stretch!)

Thanks to everyone for their reports.  This is very helpful.

Currently experimental has 10-3~exp2 which also has a patch from
Nikolaus Schulz to support hybrid sleep[1].  I don't use this myself
so reports on that would also be welcome.

I indeed intend to push this to sid in the next few days, with the
plan that it will be in stretch.

Thanks,
Ian.

[1] AIUI this is when your laptop suspends to RAM, but after a timeout
or when the battery is low, wakes up so that it can suspend to disk.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#851598: tex-common: fails to upgrade jessie->stretch (recommends enabled) with cadabra installed

[Norbert Preining]

Hi Andreas,

big thanks for testing!

>   /etc/texmf/owned by: texlive-math-extra, texlive-base, tex-common

Sounds reasonable.

>   /etc/texmf/hyphen.d/   not owned
> 
> not sure who created /etc/texmf/hyphen.d/ (and which file might have
> been in there)
> if that's still in active use, some package should ship it as an empty
> directory
> (and a leftover *owned* empty directory can be blamed to dpkg)

AFAIR there was/ a problem with rm_conffile as it makes backups,
then dpkg cannot remove the directory, and after the rm_conffile
dpkg does not retry removing the directory.

I never tracked it down completely, but AFAIR I cleaned up all
the stuff in hyphen.d.

/etc/texmf should remain as it is also TEXMFSYSCONFIG and files
might be put there.

Thanks a lot

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Processed: Fwd:

[Debian Bug Tracking System]

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

> severity 851003 normal
Bug #851003 [src:python-django-pyscss] python-django-pyscss: FTBFS: Test 
failures
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Processed (with 2 errors): your mail

[Debian Bug Tracking System]

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

> tags 851003 moreinfo unreproducible !
Unknown tag/s: !.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore 
lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie 
jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #851003 [src:python-django-pyscss] python-django-pyscss: FTBFS: Test 
failures
Added tag(s) unreproducible and moreinfo.
> severity 851003 normal !
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#761568: Your printing quotes

[Expert Print]

Good Morning,

I own a medium sized print company based in the UK and I am looking to see if 
we can help you with your  ongoing print requirements.


Your business is really important to us!! Please let us quote on your next 
print job!! You can  request a free sample pack here 
http://www.expertprint.co.uk/request-samples.html.


Following recent investments I'm looking to grow my customer base and hope I 
can save you some money in  the process. If you're in need of leaflets, 
brochures, business cards or posters then why not give us a try.


I look forward to hearing from you and thank you for your time.


Many Thanks,

Barry Pearson
Managing Director

t: 01302 368648
w: www.expertprint.co.uk
a: Unit 1a Churchill Business Park
Churchill Road
Doncaster
DN1 2TF

*If this email has reached you by mistake or if you do not wish to take 
advantage of this great  opportunity, please accept my apology for any 
inconvenience caused and rest assured that you will not be contacted  again.

Bug#845827: marked as done (captagent: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2017 13:18:27 +
with message-id 
and subject line Bug#845827: fixed in captagent 6.1.0.20-3
has caused the Debian Bug report #845827,
regarding captagent: switch to build depend on the metapackage 
default-libmysqlclient-dev
to be marked as done.

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

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


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

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: captagent
Source-Version: 6.1.0.20-3

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

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

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

Debian distribution maintenance software
pp.
Daniel Pocock  (supplier of updated captagent package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jan 2017 21:09:31 +0100
Source: captagent
Binary: captagent
Architecture: source amd64
Version: 6.1.0.20-3
Distribution: unstable
Urgency: high
Maintainer: Debian VoIP Team 
Changed-By: Daniel Pocock 
Description:
 captagent  - HOMER SIP capture agent
Closes: 845827
Changes:
 captagent (6.1.0.20-3) unstable; urgency=high
 .
   * Update Build-Deps for default-libmysqlclient-dev. (Closes: #845827)
Checksums-Sha1:
 18115602e78c5eb4902a68f72361be96ee0a5103 2121 captagent_6.1.0.20-3.dsc
 5e4fa6f0c7a22cc3b8d40a8c7857bf4adf942d38 4786 
captagent_6.1.0.20-3.debian.tar.gz
 802b232ef77a96cdec249db7299717e763da7eaa 318308 
captagent-dbgsym_6.1.0.20-3_amd64.deb
 fb31c09bd0dbc19f3ee16f5472d6dbc938d21fb5 5607 
captagent_6.1.0.20-3_amd64.buildinfo
 b8ad854c13cda929a3a643e26d24fd0660d5ad44 144194 captagent_6.1.0.20-3_amd64.deb
Checksums-Sha256:
 cdd5da62864c29224accd08f89d1385b77b71d28b16e6cdbb62380bba8fe3916 2121 
captagent_6.1.0.20-3.dsc
 1742e4e4b7d09000afd3db078e7322fdeb372bf8334d1d54341ed69e84f9bbc7 4786 
captagent_6.1.0.20-3.debian.tar.gz
 e52b85f684d72c268cb8b6b64895c350e9b18a5b3d402c938b017ef1c6eaf02f 318308 
captagent-dbgsym_6.1.0.20-3_amd64.deb
 7d8de48076e4625254abca69d9503c7470af27526e8482dd0b159d0daed1ef75 5607 
captagent_6.1.0.20-3_amd64.buildinfo
 4b933b7a35b98ef95350ca5706fd5193d23768b98bd6d4a9eca09f7f98ab446d 144194 
captagent_6.1.0.20-3_amd64.deb
Files:
 d97db90f253365d97dad8a932db1c1db 2121 comm optional captagent_6.1.0.20-3.dsc
 55775b1c6d6fe5233dd74c226e854e9b 4786 comm optional 
captagent_6.1.0.20-3.debian.tar.gz
 e49ba6f4ee34a9cf8800a09d57b05024 318308 debug extra 
captagent-dbgsym_6.1.0.20-3_amd64.deb
 953ae4ffe623abd4f6ceab646909126a 5607 comm optional 
captagent_6.1.0.20-3_amd64.buildinfo
 808c97f77915764c3bdf0ae2738cc12c 144194 comm optional 
captagent_6.1.0.20-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfhadAAoJEGxlgOd711bEO8UP/3yTHBelP3kYflx6i1212/ho
QqoLNbZ/Q9U9m3RwNsGBpg0ELJ7yNNebMMOH4Da6P6AWv4sKaCjs9sEAk1XpcmxQ
KY4k8ShD18gmB2J32BxWNpTrkBp2yZLUnivd536k4aSq5Kb0P6VVqkRpkLvyVptC
xDTjxm5UQJQdP3JscNfGZwCSVv8wIrEROIovzlM5WWX3y1t5NG7bS5AFv+mqLDZX
CobBJ5AFT3fbOGfkgna5D/l4rpIoS7xWvvB/t2hlYjDkf862q0W5AjAV67yePUu/
bIzkMMsFYb4pB3O6ipTntC/E+EOp+48/pDaEFfnuYlPzfwanHbp4eBwvXTVPUkpW
a9gO1Dx4A83mxsteYofmvPZJC6f3pQkOTWn2zh4ByMVvqK7HnO4gD5qGfIAYjL2T

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Felipe Sateler]

Hi Yann,

On 17 January 2017 at 06:54, Yann Richard  wrote:
>
> Hi,
>
> We have made a package from fcoe-utils source version 1.0.31 which fix init 
> bug :
>
> https://github.com/DSI-Universite-Rennes2/fcoe-utils
>
> Tested on HP 465c G8 on Ethernet controller: Broadcom Limited BCM57840 
> NetXtreme II 10/20-Gigabit Ethernet (rev 11) in HP C7000 enclosure with
> HP VC FlexFabric-20/40 F8 Module
>
> Any Debian maintainer or developer would like to verify and push this into 
> stretch ?

Could you please post this as a patch against the current debian
package? The linked git repository contains the entire debian
directory as a single commit. Moreover, that commit includes build
artifacts (eg, the scripts generated by debhelper), so that makes
review harder.

-- 

Saludos,
Felipe Sateler

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Paul Wise]

On Tue, Jan 17, 2017 at 7:32 PM, Fabian Greffrath  wrote:

> thank you very much for your bug report. However, I believe you are wrong
> with applying RC severity to this issue and I have added FTP-Masters to CC
> in the hope for clarification.

I agree with Ben on this issue.

> I don't think that it should make a difference if upstream uses
> proprietary software to convert the fonts from some kind of source format
> into the OTF format in which they are distributed. There are many fonts in
> Debian which are only distributed in OTF format, either because upstream
> uses this format to develop the fonts or because upstream simply does not
> tell which other format they use. As long as the license allows for binary
> distribution (and it does) I do not consider this an issue.

The issue isn't that they currently use proprietary software to
convert to OTF format. The issue is that there is no Free Software in
Debian main that can build the OTF from source. This is a clear
violation of Debian policy and that indicates the package needs to be
in contrib.

> Generally, there is no canonical source format for fonts and any of the
> common formats [1] retains the possibility to modify them, e.g. using
> fontforge scripting. The OTF format is not restricted to being an "end
> product". This makes a huge difference to e.g. PDF or PS documents which
> are given as examples in the "Missing Sources" section of the REJECTS FAQs
> that you refer to. Once converted into these formats, it is nearly
> impossible to modify the documents or convert them back into their
> respective source formats.

In this case, if you look at the commits to the github repo, there is
a clear canonical source format and that is the proprietary Glyphsapp
format that can only be converted to OTF by the proprietary Glyphsapp
software.

> [1] Think of e.g. graphics in PNG format of which we have plenty in
> Debian. It wouldn't help if they were distributed in some other format
> that upstream chose to use for creating them.

I would vastly prefer the correct source of PNG images to be
distributed in source packages and the PNG images created at build
time to the current, fairly horrible, situation. Choice of source
format is up to upstream though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#851667: openjdk-8-jre-headless needs Breaks: ca-certificates-java (<< 20160321~)

[Adrian Bunk]

Package: openjdk-8-jre-headless
Severity: serious
Tags: security patch

< Viiru> Hmm. So apparently ca-certificates-java has a hard-coded list of 
 JRE versions.
< Viiru> Thus if one installs JRE 8 from backports to a jessie machine 
 (and removes JRE 7) the trust store will never be updated again.
< Viiru> Somewhat unexpected.


The solution for this bug is a
  Breaks: ca-certificates-java (<< 20160321~)
in openjdk-8-jre-headless
(plus adding ca-certificates-java to backports,
which is outside the scope of this bug).

Bug#851598: tex-common: fails to upgrade jessie->stretch (recommends enabled) with cadabra installed

[Andreas Beckmann]

On 2017-01-17 05:37, Norbert Preining wrote:
>> That worked.
> 
> Thanks for testing.
> 
>> I'll now check the other failures with this new package, but that will
>> take more time - some larger metapackages like med-bio are involved here.
> 
> Do you have a time frame when it will be ready? If it is reasonable I'll
> wait with the upload just in case more things pop up.

med-bio passed (at least beyond texlive, it died later with a well known
issue in a detailed check)

science-physics passed

These are all texlive related failures that I'm aware of at the moment.

But I noticed an unowned leftover directory:

  /etc/texmf/owned by: texlive-math-extra, texlive-base, tex-common
  /etc/texmf/hyphen.d/   not owned

not sure who created /etc/texmf/hyphen.d/ (and which file might have
been in there)
if that's still in active use, some package should ship it as an empty
directory
(and a leftover *owned* empty directory can be blamed to dpkg)


Andreas

Bug#851666: php-sabre-event: PHP 7.0 transition

[Andreas Beckmann]

Package: php-sabre-event
Version: 3.0.0-1
Severity: serious

Hi,

php-sabre-event in experimental still depends on php5.


Andreas

Bug#851665: php-hamcrest: php 7.0 transition

[Andreas Beckmann]

Package: php-hamcrest
Version: 2.0.0-1
Severity: serious

php-hamcrest in experimental still depends on php5 ...


Andreas

Bug#846771: Unable to reproduce

[Santiago Vila]

On Tue, Jan 17, 2017 at 11:20:55AM +0100, Andreas Tille wrote:

> I intentionally ssh-ed into a machine without enabling X and have
> build there in pbuilder.  The build runs fine.

My build history for this package:

Status: successful  python-traits_4.5.0-1_amd64-20161126T172508Z
Status: failed  python-traits_4.6.0-1_amd64-20161204T125412Z
Status: failed  python-traits_4.6.0-1_amd64-20161204T133830Z
Status: successful  python-traits_4.6.0-1_amd64-20170114T160257Z

My guess is that either a build-dependency was to blame and it's now
fixed, or the bug is just random, in which case you would have to try
several times before considering it unreproducible.

Thanks.

Bug#851339: [Pkg-fonts-devel] Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Fabian Greffrath]

Dear Ben,

thank you very much for your bug report. However, I believe you are wrong
with applying RC severity to this issue and I have added FTP-Masters to CC
in the hope for clarification.

Ben Finney wrote:
> I see now that this refers to a proprietary program named Glyphs, as a
> program used in the build procedure.
>
> So the correct description of this bug is that the package must not be
> in Debian until all its build dependencies are also in Debian. See
>  “Non-Main”.
>
> Packages that have a build dependency on a non-Debian package may be
> in the “contrib” archive area.

I don't think that it should make a difference if upstream uses
proprietary software to convert the fonts from some kind of source format
into the OTF format in which they are distributed. There are many fonts in
Debian which are only distributed in OTF format, either because upstream
uses this format to develop the fonts or because upstream simply does not
tell which other format they use. As long as the license allows for binary
distribution (and it does) I do not consider this an issue.

Generally, there is no canonical source format for fonts and any of the
common formats [1] retains the possibility to modify them, e.g. using
fontforge scripting. The OTF format is not restricted to being an "end
product". This makes a huge difference to e.g. PDF or PS documents which
are given as examples in the "Missing Sources" section of the REJECTS FAQs
that you refer to. Once converted into these formats, it is nearly
impossible to modify the documents or convert them back into their
respective source formats.


I hope this all makes sense.

Thank you ,

 - Fabian


[1] Think of e.g. graphics in PNG format of which we have plenty in
Debian. It wouldn't help if they were distributed in some other format
that upstream chose to use for creating them.

Bug#846268: cython: Upstream resolution

[Tobias Hansen]

Hi Yaroslav,

looks like upstream included the fix in cython 0.25.2, so if you don't
wait too long this bug can still be fixed by just uploading the new version.

Best,
Tobias

On Fri, 2 Dec 2016 08:14:24 -0500 Antonio Russo
 wrote:
> tags -1 + patch
> 
> Upstream has posted a patch for this issue. See the github thread:
> 
> https://github.com/cython/cython/issues/1538#issuecomment-263995994
> 
> 

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

[Vincent Lefevre]

On 2017-01-17 10:19:50 +0100, Vincent Bernat wrote:
> I have the same behaviour with awesome. My setup didn't change since
> quite some time but this behaviour is recent while neither awesome nor
> pinentry-gtk2 has been updated. I got the behavior immediately after
> rebooting. Applying the patch from Werner doesn't fix the problem for
> me.

What warning and error messages do you get with the following test?

  echo getpin | pinentry-gtk-2

(This is the one suggested by GI, the easiest way to reproduce the bug
and get the warning and error messages.)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: retitle 848764

[Debian Bug Tracking System]

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

> retitle 848764 theano: test failures with Numpy 1.12
Bug #848764 [src:theano] test failures with Numpy 1.12
Changed Bug title to 'theano: test failures with Numpy 1.12' from 'test 
failures with Numpy 1.12'.
> thanks
Stopping processing here.

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

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

[PICCA Frederic-Emmanuel]

> Ehm, yes. :)

so I just tested an upgrade from jessie to sid of tango-db and it works :)))

Now I have only one concern about the dump.
Since we had a failure with the dump when it ran as user, we discovered that 
our procedures where wrong and necessitate the dbadmin grants in order to works.

Would it be possible to display the error if the dump failed with the user 
grants. So during the upgrade we should see that something was wrong.

This way we should have this interesting information. (from my point of view, 
but you can dis-agreed :)

Fred