Bug#860225: bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

[Jan Sechovec (skudlik)]

Hello,

Debian Jessie, bind9  9:1:9.9.5.dfsg-9+deb8u10

Same problem, bind gets down after few hours... something has started 
abusing this vulnerability.


24-Apr-2017 23:21:22.592 resolver.c:4350: INSIST(fctx->type == 
((dns_rdatatype_t)dns_rdatatype_any) || fctx->type == 
((dns_rdatatype_t)dns_rdatatype_rrsig) || fctx->type == 
((dns_rdatatype_t)dns_rdatatype_sig)) failed, back trace

24-Apr-2017 23:21:22.592 #0 0x7eff74c11a00 in ??
24-Apr-2017 23:21:22.592 #1 0x7eff72ded8ea in ??
24-Apr-2017 23:21:22.592 #2 0x7eff744d314e in ??
24-Apr-2017 23:21:22.592 #3 0x7eff72e0fd5b in ??
24-Apr-2017 23:21:22.592 #4 0x7eff727c0064 in ??
24-Apr-2017 23:21:22.592 #5 0x7eff7218e62d in ??
24-Apr-2017 23:21:22.592 exiting (due to assertion failure)

The problem is for us really critical.

Thanks in advance,

Jan

Processed: severity of 861121 is grave

[Debian Bug Tracking System]

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

> severity 861121 grave
Bug #861121 [src:weechat] weechat: CVE-2017-8073
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#861021: marked as done (spin: missing Breaks+Replaces: staden (<< 2.0.0+b11))

[Debian Bug Tracking System]

Your message dated Tue, 25 Apr 2017 03:49:10 +
with message-id 
and subject line Bug#861021: fixed in spin 6.4.5+dfsg-2
has caused the Debian Bug report #861021,
regarding spin: missing Breaks+Replaces: staden (<< 2.0.0+b11)
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.)


-- 
861021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: staden,spin
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package spin.
  Preparing to unpack .../spin_6.4.5-1_amd64.deb ...
  Unpacking spin (6.4.5-1) ...
  dpkg: error processing archive /var/cache/apt/archives/spin_6.4.5-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/spin', which is also in package staden 
2.0.0+b10-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/spin_6.4.5-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/spin
  usr/share/man/man1/spin.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html
--- End Message ---
--- Begin Message ---
Source: spin
Source-Version: 6.4.5+dfsg-2

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated spin 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, 24 Apr 2017 07:59:27 -0700
Source: spin
Binary: spin
Architecture: source amd64
Version: 6.4.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Tom Lee 
Changed-By: tony mancill 
Description:
 spin   - formal software verification tool
Closes: 861021
Changes:
 spin (6.4.5+dfsg-2) unstable; urgency=medium
 .
   * Declare Breaks with staden (<< 2.0.0+b11) (Closes: #861021)
Checksums-Sha1:
 ca0b98f7f0abbf4c9c17322c011850992c967c76 1868 spin_6.4.5+dfsg-2.dsc
 9949b507b4b4c3177627d810074e38e3529cb719 4000 spin_6.4.5+dfsg-2.debian.tar.xz
 d4e037a205211b8a08018fc483963ff5fc6c4395 349830 
spin-dbgsym_6.4.5+dfsg-2_amd64.deb
 53990b29c71fdb9803fdb4ba61d24dc759eb6abf 5701 spin_6.4.5+dfsg-2_amd64.buildinfo
 5e6edf3a84fbc59f695bb49f7ca6cf23ed396e46 556278 spin_6.4.5+dfsg-2_amd64.deb
Checksums-Sha256:
 b3dfa4c89e5c5b805cece0d55e53f86b5af85662b1f333f6cb3369f5d951afb9 1868 
spin_6.4.5+dfsg-2.dsc
 777c9df36be6f32aab29c066d0691a517f8c6f1f8afc1188fe804361d7ff93ae 4000 
spin_6.4.5+dfsg-2.debian.tar.xz
 330f4f5a0993a9b4a918eec5a9b8c52268c273f32e028df33e6df1bdccaad8fe 349830 
spin-dbgsym_6.4.5+dfsg-2_amd64.deb
 c2a38d66a4eb41f848037a68c317c1830f4f4e61ef3ce1be5355c073538b29d2 5701 

Bug#859655: (no subject)

[Michael Lustfield]

unblock request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860429
(with more discussion)

Bug#861152: nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made.

[Paul Wise]

Package: nagstamon
Version: 2.0.1-1
Severity: serious
Tags: security

When I run nagstamon from a terminal against the Debian nagios I get a
warning about unverified and thus insecure HTTPS requests being made:

https://nagios.debian.org/icinga/
https://dsa.debian.org/ (see here for guest login)

$ nagstamon 
...
/usr/lib/python3/dist-packages/urllib3/connectionpool.py:845: 
InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
certificate verification is strongly advised. See: 
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 
'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 
'buildd-experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages nagstamon depends on:
ii  libqt5multimedia5-plugins5.7.1~20161021-2
ii  python3-bs4  4.5.3-1
ii  python3-dbus.mainloop.pyqt5  5.7+dfsg-5
ii  python3-pkg-resources33.1.1-1
ii  python3-psutil   5.0.1-1
ii  python3-pyqt55.7+dfsg-5
ii  python3-pyqt5.qtmultimedia   5.7+dfsg-5
ii  python3-pyqt5.qtsvg  5.7+dfsg-5
ii  python3-requests 2.12.4-1
pn  python3:any  

nagstamon recommends no packages.

nagstamon suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#861131: marked as done (xandikos: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 22:49:21 +
with message-id 
and subject line Bug#861131: fixed in xandikos 0.0.4-2
has caused the Debian Bug report #861131,
regarding xandikos: Incomplete debian/copyright?
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.)


-- 
861131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xandikos
Version: 0.0.4-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Jelmer Vernooij 

Hi,

I just ACCEPTed xandikos from NEW but noticed it was missing 
attribution in debian/copyright for at least compat/serverinfo.xml.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: xandikos
Source-Version: 0.0.4-2

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated xandikos 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, 24 Apr 2017 22:28:42 +
Source: xandikos
Binary: xandikos
Architecture: source all
Version: 0.0.4-2
Distribution: experimental
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Description:
 xandikos   - Git-backed CalDAV/CardDAV server
Closes: 861131
Changes:
 xandikos (0.0.4-2) experimental; urgency=medium
 .
   * Document license for compat/serverinfo.xml. Closes: #861131
Checksums-Sha1:
 d639d3b320ded1fa7ee1f52c07c6544a6622aef2 1736 xandikos_0.0.4-2.dsc
 52c4ce637702283e9874fac79cb04d6a30759dce 536216 xandikos_0.0.4-2.debian.tar.xz
 1073f8ab066bbe9f2fabb39c24ccc68b8bcf9f24 39854 xandikos_0.0.4-2_all.deb
 2a351261694e534f7b2ac47f05a2ad427a1fd389 6223 xandikos_0.0.4-2_amd64.buildinfo
Checksums-Sha256:
 a13e705d33a216dcad1bb6919e21f8140f8b06aee003c8aa9b2d52332ccebd07 1736 
xandikos_0.0.4-2.dsc
 139ed5c0ee85d70c1efac466a833be36e1e565ca1b91570edace1b4434f09eb1 536216 
xandikos_0.0.4-2.debian.tar.xz
 25a7af2d11f60565b58938feaf2b113dd6df0e0f189b132899a66af701aa4a85 39854 
xandikos_0.0.4-2_all.deb
 371bf6e04f6f4c025ff9df59ebdc2257579daa1479959ffa2295176e9b2a1e81 6223 
xandikos_0.0.4-2_amd64.buildinfo
Files:
 26621bef229abddb18d317881c69d823 1736 python optional xandikos_0.0.4-2.dsc
 9e21e7f113023ca393816c5a7c925d5e 536216 python optional 
xandikos_0.0.4-2.debian.tar.xz
 d2dd9166bb878e22f948cdca1ad74ec8 39854 python optional xandikos_0.0.4-2_all.deb
 34b774a7b3833377970b6d0ba3d2c875 6223 python optional 
xandikos_0.0.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEoX1YPWJ8eQgrAMsfmi0kpQTR6fgFAlj+fKgSHGplbG1lckBk
ZWJpYW4ub3JnAAoJEJotJKUE0en4FAoH/3iMxYP5uYKlr01/fBZUVCVznOyIGvqT
0eM0TqWSW06rvCvjAyoEK1Qk1bsaZYQr02XFc4oVorUqVNRZQTjHfgITFxrQxt0O
QWaQfQq3hgLIteWiUhkIt7qJ2zEqkCr0pwp33RTautuexhdxJfq5zCifKU4msf3z
W+W9vIQNwsh5anw6dWk3+k6Homg41mDwGc2IlEuP4Y1dGtl1Us5rIvnLcKCBiIK6
gZaPZyMQ+ZKXlwLerzCJbiOej+zA8s9M8D1Oz1Z9SVCweaWbNbShdCgGU5hWu7fr
c74MxP2KqpxUVFhQX6M8sjSsldHjUxqHiphY9TGGTTaKNXTNU7qL79c=
=3ZWR
-END PGP SIGNATURE End Message ---

Bug#860686: [Android-tools-devel] Bug#860686: android-platform-external-doclava: FTBFS on i386: java.lang.StackOverflowError

[Hans-Christoph Steiner]

my guess is that this rebuild was done with limited RAM, since the
failure is:

"The system is out of resources."

Bug#858633: closed by Innocent De Marchi <tangram.pe...@gmail.com> (Bug#858633: fixed in dmaths 4.3.0.0+dfsg1-1)

[Gianfranco Costamagna]

Hello,

>This fixed the bug for unstable, but the new upstream version won't be 
>acceptable for fixing the bug in stretch.
>
>Please make an additional upload to stretch only fixing #858633
>on top of 3.7.0.0+dfsg1-1


before uploading I tried hard to make a patch being extracted, avoiding
this version in unstable.
Unfortunately seems that fixing this issue is equivalent than updating to a new
release, so having the package out of Stretch is the only "fix" we can provide.

Sad, but I don't know if the situation has changed.
The new libreoffice seems to have changed too much for a "fix-only upload"

G.

Bug#859560: fixed in xen 4.8.1-1

[Ivar Smolin]

On Tue, 18 Apr 2017 17:34:15 + Ian Jackson 
 wrote:

Source: xen
Source-Version: 4.8.1-1

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


Thanks for fixing!

This bug affects also Xen 4.4.x, Jessie is still vulnerable.

--
Ivar

Bug#861131: xandikos: Incomplete debian/copyright?

[Chris Lamb]

Source: xandikos
Version: 0.0.4-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Jelmer Vernooij 

Hi,

I just ACCEPTed xandikos from NEW but noticed it was missing 
attribution in debian/copyright for at least compat/serverinfo.xml.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#861112: xsane: always crashes on start

[Aaro Koskinen]

Hi,

On Mon, Apr 24, 2017 at 10:21:47PM +0200, John Paul Adrian Glaubitz wrote:
> Control: tags -1 moreinfo
> 
> Hi Aaro!
> 
> > xsane with 1 network scanner defined in /etc/sane.d/net.conf
> > crashes always on start:
> 
> Would you mind sharing your net.conf file with this bug report so
> that we can try to reproduce the problem?

---8<---
# This is the net backend config file.

## net backend options
# Timeout for the initial connection to saned. This will prevent the backend
# from blocking for several minutes trying to connect to an unresponsive
# saned host (network outage, host down, ...). Value in seconds.
# connect_timeout = 60

## saned hosts
# Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend.  Going through the net backend
# may be necessary to access devices that need special privileges.
# localhost
192.168.1.100
--->8---

A.

Bug#791770: dhelp: Depends on obsolete ruby-bdb

[Коля Гурьев]

Control: owner -1 !

Please don't remove this package. I already work on patch to fix this 
bug. I think I can perform migration from a module for Berkley DB to DBM 
class from the Ruby standard library. I'm attaching my current draft. 
Now I going to write migration scripts and test them.


By the way, can I check a previously installed version of the package in 
postinst script?
=== modified file 'debian/changelog'
--- debian/changelog	2014-12-12 22:02:20 +
+++ debian/changelog	2017-04-24 20:23:36 +
@@ -1,3 +1,10 @@
+dhelp (0.6.21+nmu6ubuntu1) UNRELEASED; urgency=medium
+
+  * Migrate to a module from the standard library
+- Remove ruby-bdb dependency
+
+ -- Nicholas Guriev   Mon, 24 Apr 2017 23:21:54 +0300
+
 dhelp (0.6.21+nmu6) unstable; urgency=medium
 
   * Non-maintainer upload.

=== modified file 'debian/control'
--- debian/control	2014-05-18 13:18:39 +
+++ debian/control	2017-04-24 20:20:58 +
@@ -11,7 +11,7 @@
 Package: dhelp
 Depends: perl-modules, libtemplate-perl, libhtml-parser-perl,
  liburi-perl, liblocale-gettext-perl, libdata-page-perl,
- ruby | ruby-interpreter, ruby-bdb, ruby-debian, ruby-gettext,
+ ruby | ruby-interpreter, ruby-debian, ruby-gettext,
  doc-base, swish++, pstotext, poppler-utils, ucf (>= 0.8),
  ${misc:Depends}
 Recommends: www-browser | html2text

=== modified file 'devtools/list-dirs.rb'
--- devtools/list-dirs.rb	2012-06-12 21:50:00 +
+++ devtools/list-dirs.rb	2017-04-24 19:50:51 +
@@ -2,7 +2,7 @@
 
 path = ARGV.shift || Dhelp::DOC_DIR_DATABASE
 puts "Opening #{path}"
-ddd = Dhelp::DocDirDatabase.open(BDB::RDONLY, path)
+ddd = Dhelp::DocDirDatabase.open(DBM::READER, path)
 ddd.each do |dir, doc_id, title|
   puts "#{dir} -> #{doc_id} (#{title})"
 end

=== modified file 'lib/dhelp.rb'
--- lib/dhelp.rb	2014-05-18 13:18:39 +
+++ lib/dhelp.rb	2017-04-24 19:57:08 +
@@ -18,7 +18,7 @@
 Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA
 =end
 
-require 'bdb'
+require 'dbm'
 require 'pathname'
 require 'fileutils'
 
@@ -239,23 +239,18 @@
 
   # Database for doc-base directories. It contains base directories associated
   # with the corresponding doc-base doc id and the document title.
-  class DocDirDatabase < BDB::Hash
-def self.open(flags   = BDB::RDONLY,
+  class DocDirDatabase < DBM
+def self.open(flags   = DBM::READER,
   name= DOC_DIR_DATABASE,
   options = {},
   mode= 0644)
-  default_options = {"ffactor"   => 8,
- "nelem" => 1,
- "cachesize" => 5000,
- "hash"  => nil,
- "lorder"=> 0}
-  super(name, nil, flags, mode, default_options.merge(options))
+  super(name, mode, flags)
 end
 
 # Traverse entire BD, passing directory, doc_id and title of each item to
 # the block
 def each
-  super do |k,v|
+  each_pair do |k,v|
 value = DocDirDatabaseValue.new(v)
 yield DocDirDatabaseKey.new(k).dir, value.doc_id, value.title
   end
@@ -266,19 +261,19 @@
 def add(dir, doc_id, title)
   key = DocDirDatabaseKey.new(:dir => dir)
   value = DocDirDatabaseValue.new(:doc_id => doc_id, :title => title)
-  put(key.to_raw_data, value.to_raw_data)
+  self[key.to_raw_data] = value.to_raw_data
 end
 
 def include?(dir)
   key = DocDirDatabaseKey.new(:dir => dir)
-  return super(key.to_raw_data)
+  return has_key?(key.to_raw_data)
 end
 
 # Returns an array with two elements, doc_id and title, for the registered
 # doc-base document in the given directory
 def info_for_path(dir)
   key = DocDirDatabaseKey.new(:dir => dir)
-  raw_value = get(key.to_raw_data)
+  raw_value = self[key.to_raw_data]
   if raw_value.nil?
 raise KeyNotFoundError, "Can't find information for path #{dir}"
   end
@@ -448,10 +443,11 @@
 # Registers a list of doc-base documents as part of Dhelp
 def _register_docs(doc_list, user_opts={})
   register_opts = {:regenerate_index => false}.merge(user_opts)
-  open_flag = register_opts[:regenerate_index] ? (BDB::CREATE|
-  BDB::TRUNCATE) :
- BDB::CREATE
-  doc_dir_db = DocDirDatabase.open(open_flag, @doc_dir_database)
+  if register_opts[:regenerate_index]
+doc_dir_db = DocDirDatabase.open(DBM::NEWDB, @doc_dir_database)
+  else
+doc_dir_db = DocDirDatabase.open(DBM::WRCREAT, @doc_dir_database)
+  end
   index_paths = []
   doc_list.each do |doc|
 doc.formats.each do |format|

=== modified file 'test/tc_dhelpdocumentpool.rb'
--- test/tc_dhelpdocumentpool.rb	2014-05-18 13:18:39 +
+++ test/tc_dhelpdocumentpool.rb	2017-04-24 20:19:29 +
@@ -1,6 +1,7 @@
 require 'test/unit'
 require 'dhelp'
 require 'fileutils'
+require 'set'

Processed: Re: dhelp: Depends on obsolete ruby-bdb

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #791770 [dhelp] dhelp: Depends on obsolete ruby-bdb
Owner recorded as Коля Гурьев .

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

Processed: Re: xsane: always crashes on start

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #861112 [xsane] xsane: always crashes on start
Added tag(s) moreinfo.

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

Bug#861112: xsane: always crashes on start

[John Paul Adrian Glaubitz]

Control: tags -1 moreinfo

Hi Aaro!

> xsane with 1 network scanner defined in /etc/sane.d/net.conf
> crashes always on start:

Would you mind sharing your net.conf file with this bug report so
that we can try to reproduce the problem?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#859101: marked as done (regression: net: security update makes `net ads join` freeze when run a second time)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 19:32:57 +
with message-id 
and subject line Bug#859101: fixed in samba 2:4.2.14+dfsg-0+deb8u5
has caused the Debian Bug report #859101,
regarding regression: net: security update makes `net ads join` freeze when run 
a second time
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.)


-- 
859101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-common-bin
Version: 2:4.2.10+dfsg-0+deb8u1
Severity: serious
File: /usr/bin/net
Control: found -1 2:4.2.14+dfsg-0+deb8u4
X-Debbugs-CC: secur...@debian.org

The jessie security upgrade from samba 2:4.1.17+dfsg-2+deb8u2 to
2:4.2.10+dfsg-0+deb8u1 causes the `net ads join` command to freeze when
run on a system that has already been joined to the domain.

I've confirmed that the freeze does not happen on samba 4.1 using
snapshot.d.o. The issue still occurs with 2:4.2.14+dfsg-0+deb8u4.

When I increase the debug level to 15, it appears that it freezes while
trying to remove old keytab entries.

The command doesn't use much CPU so it appears to be a deadlock.

$ sudo apt install samba-common-bin smbclient
$ grep -A13 \\[global /etc/samba/smb.conf 
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = TEST
   realm = TEST.LOCAL
   dedicated keytab file = /etc/krb5.keytab
   kerberos method = secrets and keytab
   preferred master = no
   domain master = No
   password server = *
   security = ADS
   ldap timeout = 300
$ sudo net ads join -d15 -UAdministrator
...
Enter Administrator's password:
...
$ sudo net ads join -d15 -UAdministrator
...
Enter Administrator's password:
...
../source3/libads/kerberos_keytab.c:65: Will try to delete old keytab entries
../source3/libads/kerberos_keytab.c:139: Found old entry for principal: 
host/test46.test.local@TEST.LOCAL (kvno 6) - trying to remove it.
^C
$ sudo smbclient -Utester -L //testsbs01
Enter Indexer's password: 
Domain=[TEST] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows 
Server 2003 5.2]
$ cat /etc/apt/sources.d/snapshot.list
deb http://snapshot.debian.org/archive/debian/20160103T163148Z/ jessie main
deb http://snapshot.debian.org/archive/debian-security/20160413T203215Z/ 
jessie/updates main
deb http://snapshot.debian.org/archive/debian/20160314T035958Z/ jessie main
deb http://snapshot.debian.org/archive/debian-security/20160312T072202Z/ 
jessie/updates main

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

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

Versions of packages samba-common-bin depends on:
ii  libbsd00.7.0-2
ii  libc6  2.19-18+deb8u7
ii  libldap-2.4-2  2.4.40+dfsg-1+deb8u2
ii  libncurses55.9+20140913-1+b1
ii  libpopt0   1.16-10
ii  libreadline6   6.3-8+b3
ii  libtalloc2 2.1.2-0+deb8u1
ii  libtdb11.3.6-0+deb8u1
ii  libtevent0 0.9.28-0+deb8u1
ii  libtinfo5  5.9+20140913-1+b1
ii  libwbclient0   2:4.2.14+dfsg-0+deb8u4
ii  python 2.7.9-1
ii  python-samba   2:4.2.14+dfsg-0+deb8u4
pn  python2.7:any  
ii  samba-common   2:4.2.14+dfsg-0+deb8u4
ii  samba-libs 2:4.2.14+dfsg-0+deb8u4

samba-common-bin recommends no packages.

Versions of packages samba-common-bin suggests:
pn  heimdal-clients  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.2.14+dfsg-0+deb8u5

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

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated samba 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 

Bug#858564: marked as done (Cannot access anything under a subdirectory if symlinks are disallowed)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 19:32:57 +
with message-id 
and subject line Bug#858564: fixed in samba 2:4.2.14+dfsg-0+deb8u5
has caused the Debian Bug report #858564,
regarding Cannot access anything under a subdirectory if symlinks are disallowed
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.)


-- 
858564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.2.14+dfsg-0+deb8u2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
I upgraded to 8u4 through unattended upgrades.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
(1) I attempt to create a file not in the root directory of the share.
(2) I try to write to files not in the root directory of the share.
   * What was the outcome of this action?
(1) Windows Explorer freezes entirely until I end task it.
(2) It says permission denied.
   * What outcome did you expect instead?
(1) Normally I can create files.
(2) Normally I can access files.

I have reverted back to 8u2 and am no longer experiencing problems.
Access to the root directory of the share works fine.

My smb.conf is as follows:
(start)
[global]
server string = Server
workgroup = WORKGROUP
log level = 1

interfaces = eth0 eth0:0 eth0:1 eth0:2 eth0:3
bind interfaces only = yes
socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=65536 SO_RCVBUF=65536

server role = standalone server
disable netbios = yes
disable spoolss = yes
csc policy = disable
oplocks = no
server min protocol = NT1

passdb backend = tdbsam
encrypt passwords = yes
invalid users = root fsadmin
disable netbios = yes
disable spoolss = yes
csc policy = disable
oplocks = no
server min protocol = NT1

passdb backend = tdbsam
encrypt passwords = yes
invalid users = root fsadmin

follow symlinks = no
hide dot files = no
wide links = no

create mask = 660
directory mask = 770

vfs objects = acl_xattr streams_xattr full_audit
full_audit:prefix = %S|%u|%I
follow symlinks = no
hide dot files = no
wide links = no

create mask = 660
directory mask = 770

vfs objects = acl_xattr streams_xattr full_audit
full_audit:prefix = %S|%u|%I
full_audit:success = mkdir open opendir rename rmdir unlink
full_audit:failure = all !getxattr !removexattr !is_offline !readdir_att$
full_audit:facility = LOCAL7
full_audit:priority = ALERT

map acl inherit = yes
store dos attributes = yes

browseable = no
writeable = yes

include = /etc/samba/smb.conf.%i
(end)

As an example of the IP-address specific file, here's one:
(start)
[hr$]
comment = HR Server
path = /mnt/data/hr
force group = +AccessHR
valid users = @AccessHR
(end)

Permissions are absolutely fine. They are essentially 770.
AppArmor is enabled, but I disabled it and the problem still exists in 8u4.
It does not exist in 8u2.

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


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

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

Versions of packages samba depends on:
ii  adduser  3.113+nmu3
ii  dpkg 1.17.27
ii  libbsd0  0.7.0-2
ii  libc62.19-18+deb8u7
ii  libhdb9-heimdal [heimdal-hdb-api-8]  1.6~rc2+dfsg-9
ii  libldb1  2:1.1.20-0+deb8u1
ii  libpam-modules   1.1.8-3.1+deb8u2
ii  libpam-runtime   1.1.8-3.1+deb8u2
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.9-2+deb8u1
ii  libtalloc2   2.1.2-0+deb8u1
ii  libtdb1  1.3.6-0+deb8u1
ii  libtevent0   0.9.28-0+deb8u1
ii  lsb-base 4.1+Debian13+nmu1
ii  multiarch-support2.19-18+deb8u7
ii  procps   2:3.3.9-9
ii  python   2.7.9-1
ii  python-dnspython 1.12.0-1
ii  python-ntdb  1.0-5
ii  python-samba 2:4.2.14+dfsg-0+deb8u2
pn  

Bug#858366: marked as done (libwhy-coq: sourceful upload needed to update coq dependency)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 19:18:58 +
with message-id 
and subject line Bug#858366: fixed in why 2.38-1
has caused the Debian Bug report #858366,
regarding libwhy-coq: sourceful upload needed to update coq dependency
to be marked as done.

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

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


-- 
858366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwhy-coq
Version: 2.36-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

The following packages have unmet dependencies:
 libwhy-coq : Depends: coq-8.5+4.02.3 but it is not installable

A binNMU is not possible since libwhy-coq is arch:all.

Please also consider relaxing the frama-c-base dependency to not
require a binNMU for every frama-c upload.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: why
Source-Version: 2.38-1

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated why package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Apr 2017 08:25:31 +0200
Source: why
Binary: why libwhy-coq
Architecture: source
Version: 2.38-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 libwhy-coq - Why library for Coq
 why- Software verification tool for C and Java
Closes: 858366
Changes:
 why (2.38-1) unstable; urgency=medium
 .
   * New upstream version (closes: #858366)
 - refreshed patches bprintf, edge
 - dropped hunks of patch reproducible_build that have been applied
   by upstream.
   * Bump build-dependency on frama-c-base to 20161101+silicon+dfsg
   * debian/why.install: install Jessie.o
   * Restrict Architecture of the why package to architectures having a
 native-code compiler for ocaml, since upstream ceased to maintain
 the why package for bytecode-only architectures.
Checksums-Sha1:
 4d7284212c5de6f55c31efaa65ea83b6f4a4f80c 2428 why_2.38-1.dsc
 1c421cdde44021424195c9426365a5173695a161 1728736 why_2.38.orig.tar.gz
 0d385a4c049f176a3d4bf5c72ae7708647f949c0 11600 why_2.38-1.debian.tar.xz
 9aa2d01b4fd71040e4f2e44709345a34d7c5d607 8635 why_2.38-1_source.buildinfo
Checksums-Sha256:
 e47f35d717925497d41289ecabffa36bfe6b4b08a0b416aab1c399d09734d0d8 2428 
why_2.38-1.dsc
 16e174b4190352b229259f2ea47628f9ca4f33053c28c531536f6d350231db12 1728736 
why_2.38.orig.tar.gz
 c29d7a2e5b0cae856ed21c97868b6cb5788456d65221e02b0a5d07d66d8633eb 11600 
why_2.38-1.debian.tar.xz
 cea4775098f01de94e9b99c18713e653870d1843be52c1ef7bd10ab79a586897 8635 
why_2.38-1_source.buildinfo
Files:
 f55748f9af36c2e3fb431d4914b3e2b8 2428 math optional why_2.38-1.dsc
 3add4408954b07a23629b14d74a0a16e 1728736 math optional why_2.38.orig.tar.gz
 42215888c0c54ee479b16d689c40610e 11600 math optional why_2.38-1.debian.tar.xz
 53aa26793979568d46b26b7ea1ad61dd 8635 math optional why_2.38-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAlj+SmsACgkQdFxHZtTK
zf9ywBAAgUcAkgOBRZIbzFjo7KNc5ZgfmoBbhN4hnZO/l8EHCb8ngPjpGPNp9/SO
WjiVkJpX6lLSz5Cod1shSBLoSLTummg2xBOS6dSOXf15KpE+OdC65rg8FsqQPIWX
dojZTrJ9w2TPtA0nYrQQW3DrWRuSlHyX468zV0vBAFnGaFYUqYn76Pw1frh+EEJ1
eeqOBzbsw1aecr0vOYSnLS8zIEf7ofnq/XgYuXobk7wlJXFLk8GaIOcpkAhxzGxP
94BLAPpN8qCuqDat6N7wCj7OlVA7YlixOW3avq+agNZ+7DRJyCs/5+9mWVYooJBM
oJsGkf7OtFWPQix3LL77HzF9vHt/rHhhHDOuUNVR9WhmsDQG2Z0Qdsou3vZpijmJ
R5+nbGkSjRY6PcjQjxgH24ng9mvua9jvJgAU4jX8s4KnRG4gmNQWzuT44wHmtL4G
1+tNr87NRRPR9U2x/gOOADtXG/2PZPL2uSqWqZmmo/dniHtsNT36KQjSxlYTQBUa
lEENxxMLYMl/eUF5cNxI5tHvEEX8LNDVkQ4tPfqZM4DcIGVYZZu/QiuvvW3S8LKJ
0g1pgClM83FYXVZkwWaN1zFTehM7I9GbRSJ8sNP19rfzPMtbKNiYQXpAXkbq+8ab
CTM572frC+ihFperdpecVknENughXIv7Nuoxf/0jsMK/XapBYzg=
=3DDV
-END PGP SIGNATURE End Message ---

Bug#861030: marked as done (gfsview: broken symlink: /usr/share/gfsview/fonts/Garuda.ttf -> ../../fonts/opentype/tlwg/Garuda.otf)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 19:04:31 +
with message-id 
and subject line Bug#861030: fixed in gfsview 20121130+dfsg-3
has caused the Debian Bug report #861030,
regarding gfsview: broken symlink: /usr/share/gfsview/fonts/Garuda.ttf -> 
../../fonts/opentype/tlwg/Garuda.otf
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.)


-- 
861030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gfsview
Version: 20121130+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m28.0s ERROR: FAIL: Broken symlinks:
  /usr/share/gfsview/fonts/Garuda.ttf -> ../../fonts/opentype/tlwg/Garuda.otf


gfsview has Depends: fonts-tlwg-garuda, but that is the wrong
package, since it is only a metapackage:

  Package: fonts-tlwg-garuda
  Depends: fonts-tlwg-garuda-ttf | fonts-tlwg-garuda-otf

which is not suitable if you want a specific file to exist.
So depend on fonts-tlwg-garuda-otf instead. (Or switch the symlink
target to the corresponding .ttf and depend on the -ttf package.)


cheers,

Andreas


gfsview_20121130+dfsg-2+b3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gfsview
Source-Version: 20121130+dfsg-3

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gfsview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Apr 2017 20:56:01 +0200
Source: gfsview
Binary: gfsview gfsview-batch libgfsgl0 libgfsgl-dev
Architecture: source
Version: 20121130+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gfsview- graphical viewer for Gerris simulation files
 gfsview-batch - batch-version of viewer for Gerris simulation files
 libgfsgl-dev - graphical viewer for Gerris simulation files. Development files
 libgfsgl0  - graphical viewer for Gerris simulation files. Shared library
Closes: 861030
Changes:
 gfsview (20121130+dfsg-3) unstable; urgency=medium
 .
   * [2452eff] Depend on fonts-tlwg-garuda-otf not on virtual analogue.
   (Closes: #861030)
Checksums-Sha1:
 49e4840ef042dcc3d6bf6f0b1c3301e1040896b5 2408 gfsview_20121130+dfsg-3.dsc
 d48b5fdb660f4529e052de33564eb5cedaf3cf3f 8212 
gfsview_20121130+dfsg-3.debian.tar.xz
 5f8ea76358071502538fc313462e34a57cb75e44 15498 
gfsview_20121130+dfsg-3_source.buildinfo
Checksums-Sha256:
 8a82aa084faff9b796a39582f30b8cfe9fad8a60a5539468cf381a2609a1fff3 2408 
gfsview_20121130+dfsg-3.dsc
 10bd6262142ce12ba77bca0e451dcdb52f50127b6eef736d844274f8665929f1 8212 
gfsview_20121130+dfsg-3.debian.tar.xz
 f5b945153d336d0a5dbe59fc4bd8050e2b98bafe2fba1ef9107cef9fdc5cc0d4 15498 
gfsview_20121130+dfsg-3_source.buildinfo
Files:
 36f20e0dcdf9f74dff2aa0645810784f 2408 science optional 
gfsview_20121130+dfsg-3.dsc
 75421d548ac984b595e5c1acf18162dc 8212 science optional 
gfsview_20121130+dfsg-3.debian.tar.xz
 2ea4d9d7e29eee8960e5e7e45ed7b31b 15498 science optional 
gfsview_20121130+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlj+Sl8ACgkQ0+Fzg8+n
/wbTpA//cRteyEbiwjawqzz6juq3iVyI595UjG8EacQAzXDfJjXjg0F64GqWyHKi
kEXwoIcubvhxsRduEh4S7ZAGPTaQxsKSV2cymGH1iYm1uDziAgPMPLlS6CQP8ePw
tY0aeGBGzrosY7H2TWS20y08ZtV4lCJX0TGL1vta65xEJVIA8BxHr8FVO4F6BVqH
K8eoB6dRlXvG7IdXSv3MNZjO0knCeTqwsrknNkL8mG5UX6EGBa4y/0dPIexh3n6E
WTCVn1TRzpwLebIRM8Q9vrEuUUyLJfnlP1S/aKJAc1z+pwhz4U8RmYTPKSfeEk5j
iX/miRroRVA98MhGRYme75TDlbrXlv786JNyGktXQAqA1xW35HDg0CvRStwsnk5+
tAhd3d7IRgaBbPM3+w3P6HhoC9fQpm0x4NT2sscedPpmOCf2CR0MdYUS3ychzFDa
t26IcT+vG9cUFn+C0Lh3OyNzaEtRmlCRjs8eAYtUgsJzpwzDrBi4j8eJ0ThCUNHG

Bug#861024: marked as done (gerris: broken symlinks: /usr/lib/gerris/(m4.awk|gfs2tex.py) -> ../../share/gerris/lib/$1)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 19:04:26 +
with message-id 
and subject line Bug#861024: fixed in gerris 20131206+dfsg-14
has caused the Debian Bug report #861024,
regarding gerris: broken symlinks: /usr/lib/gerris/(m4.awk|gfs2tex.py) -> 
../../share/gerris/lib/$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.)


-- 
861024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gerris
Version: 20131206+dfsg-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m52.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/gerris/m4.awk -> ../../share/gerris/lib/m4.awk
  /usr/lib/gerris/gfs2tex.py -> ../../share/gerris/lib/gfs2tex.py

The gerris package ships instead
  /usr/share/gerris/m4.awk
  /usr/share/gerris/gfs2tex.py
which are probably the intended targets.


cheers,

Andreas


gerris_20131206+dfsg-13.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gerris
Source-Version: 20131206+dfsg-14

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gerris package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Apr 2017 20:43:51 +0200
Source: gerris
Binary: gerris libgfs-1.3-2 libgfs-dev
Architecture: source
Version: 20131206+dfsg-14
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gerris - Fluid Flow Solver
 libgfs-1.3-2 - Fluid Flow Solver -- shared libraries
 libgfs-dev - Fluid Flow Solver -- development libraries and headers
Closes: 861024
Changes:
 gerris (20131206+dfsg-14) unstable; urgency=medium
 .
   * [51edbdb] Fix brokin symlinks. (Closes: #861024)
Checksums-Sha1:
 ac2c2e74ab4e8fc3a81f2f2ddeb6789a1b135918 2419 gerris_20131206+dfsg-14.dsc
 c5f62635a6d65c1402942b720a5654dfb2cf3e95 16632 
gerris_20131206+dfsg-14.debian.tar.xz
 2e494ce55dde5c7d66b93f8d72a818f03c9b4f52 8600 
gerris_20131206+dfsg-14_source.buildinfo
Checksums-Sha256:
 2b64bf060e39819204bea2e80b5a7c62d2c03b0607920e6282947e92938c09d6 2419 
gerris_20131206+dfsg-14.dsc
 8e482972a78ce7700c6acacb609af53013df436f6fbd2430bd098388d51051c7 16632 
gerris_20131206+dfsg-14.debian.tar.xz
 a1718e64e7e57fc8e0f1291f648933c6fbe117ea2f555dc5df415d8a2ca17db5 8600 
gerris_20131206+dfsg-14_source.buildinfo
Files:
 340868ed3daa32efbc6be2d247a75ef8 2419 science optional 
gerris_20131206+dfsg-14.dsc
 cceb8152d82ed0f1bd28cde98d3737e3 16632 science optional 
gerris_20131206+dfsg-14.debian.tar.xz
 6c7294a6e2874f0d8693f2712dae322d 8600 science optional 
gerris_20131206+dfsg-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlj+R4MACgkQ0+Fzg8+n
/wb4iw/8DqPSj5GogUgboIt91Ug8jDPPQK/+ddd9HukI2aaLs0bE/VVgqn1iSwQv
Oogb/v9KESfsCLXduTXt2C57SfMjyUJfL8fgFDOOKX2xokmHo5CTW/ctyM2m2q0q
wEkc/eefnLPXji5N8zfAHZN0jCn2i4amFsNJhJm9bT9IfFWWpydlooksITpDzYWN
hvtpXqpm3lNEH8zTLIY38sOiSeuyYPGIDCJm4S55kHnXWQihmp8sRec++2b9zhFl
dieskeX4dtJxCAcjIbUWONOKxeQRwFte0HJptgE1J+rixSAGyFvyOPwi2Hy+VRIc
CyWmglu+XEYqHqjioZ9uIXeTrE4YBIpVLuBq9NgrGo33bL3dYI/H3fEKgaLspT1i
8fQU26bk/qXJnqSC3V+QNsF0OsT1ltr/TJ2mZGrMaM+blQJiB8wTLPvLOV1zjnAP
9UIinnj+fxPkS50i+W5hB9nNTFcvv0pPm5XyGnuIGg2qq6DkHV2DDzHWtnH92x9U
f05pYO//ioHVx5XezNuYZSYTqtKjFO/lhyKRBfquDuX1Udc6/ezr8U+zvOToPRfz
l5LrVmIPBXYWj7YhBD8i1WhaqXu7lMb3sGwW1nRrjvTivddtAdONH6eFLcTMMRJH
DJ43T+XA78calAgZhG/0K+be62cqT2fMg2Oz8x049Sdb0eR6urw=
=11yz
-END PGP SIGNATURE End Message ---

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Mon, Apr 24, 2017 at 10:44:52AM +0200, Lars Tangvald wrote:
> 
> 
> On 04/24/2017 10:27 AM, Salvatore Bonaccorso wrote:
> > Hi Lars,
> > 
> > On Mon, Apr 24, 2017 at 07:59:36AM +0200, Lars Tangvald wrote:
> > > 
> > > On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote:
> > > > Hi Lars,
> > > > 
> > > > On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:
> > > > > Hi,
> > > > > 
> > > > > I lost internet connectivity where I am right now, so probably unable 
> > > > > to get
> > > > > this done until Monday. Could maybe use the previous debdiff for 
> > > > > Jessie if
> > > > > you're ok with closing the bug manually.
> > > > > Also, I think we still don't have any active members in the 
> > > > > maintainer team
> > > > > with upload access for 5.5
> > > > Okay, I will look if I can take care of the upload for
> > > > jessie-security.
> > > > 
> > > > Regards,
> > > > Salvatore
> > > Thanks! I was just about to push the update to git, but I see you already
> > > did. Do you need anything more from us on this? Working with the LTS team
> > > for wheezy-security.
> > No, it's fine at the moment. I'm still waiting for two builds. armhf
> > furthermore failed. Checking if that was temprary.
> Was it a test failure?
> There are some unstable tests I think we should identify (in unstable we've
> started disabling them and reporting upstream bug for each).

Seems it was temporary, we have now as well the builds for armhf and
ppc64el.

Regards,
Salvatore

Bug#861119: nanoc: FTBFS under some timezones (eg. GMT-14)

[Chris Lamb]

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

Dear Maintainer,

nanoc fails to build from source in unstable/amd64 under 
some timezones (eg. TZ="/usr/share/zoneinfo/Etc/GMT-14"):

  […]

  Nanoc::DataSources::FilesystemTest#test_parse_embedded_no_meta = 0.02 s = .
  
Nanoc::DataSources::FilesystemTest#test_all_split_files_in_allowing_periods_in_identifiers
 = 0.02 s = .
  
Nanoc::DataSources::FilesystemTest#test_all_split_files_in_disallowing_periods_in_identifiers
 = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_identifier_for_filename_allowing_periods_in_identifiers
 = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_utf8_bom = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_all_split_files_in_with_same_extensions 
= 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_ext_of_allowing_periods_in_identifiers 
= 0.02 s = .
  
Nanoc::DataSources::FilesystemTest#test_identifier_for_filename_with_index_filenames_allowing_periods_in_identifier
 = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_external_bad_metadata = 0.02 s 
= .
  
Nanoc::DataSources::FilesystemTest#test_ext_of_disallowing_periods_in_identifiers
 = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_basename_of_allowing_periods_in_identifiers
 = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_load_objects = 0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_embedded_meta_only_1 = 0.03 s = 
.
  
Nanoc::DataSources::FilesystemTest#test_parse_embedded_separators_but_not_metadata
 = 0.02 s = .
  
Nanoc::DataSources::FilesystemTest#test_all_split_files_in_with_multiple_content_files
 = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_embedded_full_meta = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_external = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_all_split_files_in_with_multiple_dirs 
= 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_identifier_for_filename_disallowing_periods_in_identifiers
 = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_basename_of_disallowing_periods_in_identifiers
 = 0.02 s = .
  
Nanoc::DataSources::FilesystemTest#test_load_objects_correct_identifier_with_separate_yaml_file
 = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_identifier_for_filename_with_full_style_identifier
 = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_embedded_diff = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_embedded_empty_meta = 0.02 s = .
  Nanoc::DataSources::FilesystemTest#test_load_layouts_with_nil_dir_name = 0.02 
s = .
  Nanoc::DataSources::FilesystemTest#test_compile_iso_8859_1_site = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_identifier_for_filename_with_index_filenames_disallowing_periods_in_identifier
 = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_identifier_for_filename_with_subfilename_allowing_periods_in_identifiers
 = 0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_embedded_with_extra_spaces = 
0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_compile_iso_8859_1_site_with_explicit_encoding
 = 0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_load_objects_with_same_extensions = 
0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_filename_for = 0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_load_binary_layouts = 0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_embedded_invalid_2 = 0.03 s = .
  
Nanoc::DataSources::FilesystemTest#test_load_objects_disallowing_periods_in_identifiers
 = 0.03 s = .
  Nanoc::DataSources::FilesystemTest#test_parse_internal_bad_metadata = 0.03 s 
= .
  Nanoc::Checking::DSLTest#test_from_file = 0.03 s = .
  Nanoc::Checking::DSLTest#test_has_absolute_path = 0.03 s = .
  Nanoc::Checking::DSLTest#test_has_base_path = 0.03 s = .
  Nanoc::Filters::RedClothTest#test_filter = 0.03 s = .
  Nanoc::Filters::RedClothTest#test_filter_with_options = 0.03 s = .
  Nanoc::Helpers::XMLSitemapTest#test_filter = 0.03 s = .
  Nanoc::Helpers::XMLSitemapTest#test_sorted = 0.03 s = .
  Nanoc::Helpers::XMLSitemapTest#test_xml_sitemap = 0.03 s = .
  Nanoc::Helpers::XMLSitemapTest#test_sitemap_with_items_as_param = 0.03 s = .
  Array#__nanoc_symbolize_keys_recursively#test_0001_should convert keys to 
symbols = 0.00 s = .
  Nanoc::DataSourceTest#test_new_item = 0.03 s = .
  Nanoc::DataSourceTest#test_new_layout = 0.02 s = .
  Nanoc::DataSourceTest#test_loading = 0.03 s = .
  Nanoc::DataSourceTest#test_not_implemented = 0.02 s = .
  Nanoc::DataSourceTest#test_new_item_with_checksums = 0.02 s = .
  Nanoc::DataSourceTest#test_new_layout_with_checksums = 0.03 s = .
  Nanoc::Helpers::CapturingTest#test_content_for_recursively = 0.03 s = .
  Nanoc::Helpers::CapturingTest#test_dependencies = 0.07 s = .
  Nanoc::Helpers::CapturingTest#test_dependency_without_item_variable = 0.09 s 
= .
  

Bug#861112: xsane: always crashes on start

[Aaro Koskinen]

Package: xsane
Version: 0.999-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

xsane with 1 network scanner defined in /etc/sane.d/net.conf
crashes always on start:

$ xsane
xsane: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed.
Aborted

Before the crash a window appears briefly telling "scanning for devices".

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

Kernel: Linux 4.9.0-2-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages xsane depends on:
ii  libc62.24-9
ii  libgimp2.0   2.8.18-1
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libjpeg62-turbo  1:1.5.1-2
ii  liblcms2-2   2.8-4
ii  libpng16-16  1.6.28-1
ii  libsane  1.0.25-3
ii  libtiff5 4.0.7-6
ii  xsane-common 0.999-5
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages xsane recommends:
pn  cups-client
ii  firefox-esr [www-browser]  45.8.0esr-1
ii  lynx [www-browser] 2.8.9dev11-1

Versions of packages xsane suggests:
pn  gimp  
pn  gocr | cuneiform | tesseract-ocr | ocrad  
pn  gv
pn  hylafax-client | mgetty-fax   

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

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

> tag 857085 + help
Bug #857085 [src:ldc] terminix FTBFS on armhf: Error executing /usr/bin/ldc2: 
Segmentation fault
Added tag(s) help.
>
End of message, stopping processing here.

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

Bug#857085: terminix FTBFS on armhf: Error executing /usr/bin/ldc2: Segmentation fault

[Matthias Klumpp]

Hi!

Here is a short summary on the bug:

1) It only happens on Debian buildds, Fedora and Arch are not
affected. I examined the build logs and the environments are
relatively similar, with a notable difference for Fedora being that
they build with GCC 7

2) The issue itself is an infinite loop in
`TemplateInstance::needsCodegen` which shouldn't be possible, and
upstream has no idea why it happens. Debugging the issue is really
hard.

3) Suddenly we started to get the same bug reproducibly on i386
buildds as well for LDC itself, see[1]. There, the bug is in the
bootstrap process, which uses an older compiler that worked fine
already for many Debian releases. This suggests that the actual issue
might be in a different portion of the code, or something else has
changed that is now triggering the issue.

4) Compiling LDC in a i386 chroot on an arm64 host always works
without any issues - the problem appears only on the buildd (which
itself is an amd64 host...).

5) The same applied to the crash on armhf which never happens when
cross-compiling, but only on a real armhf machine.

6) The problem is not LDC being miscompiled during bootstrap, nor does
compiling with LLVM 3.8 instead of 3.9 change anything.

7) The crash disappears when running in GDB (or valgrind)

I am really out of ideas on this - upstream suggested some valgrinding
and gdb-ing, but doing that is very cumbersome as the only place where
I can reproduce this bug that isn't a Debian buildd is an armhf
porterbox (and armhf is really slow...), and as soon as you run the
application in gdb the crash vanishes.

Creating a minimized testcase would take multiple weeks on armhf, and
ultimately failed a few weeks back - but we uncovered another bug in
the process, which was resolved meanwhile, so at least something good
came out of it.

Any help would be highly appreciated!
Cheers,
Matthias Klumpp

[1]: 
https://buildd.debian.org/status/fetch.php?pkg=ldc=i386=1%3A1.1.1-3=1493055455=0

Bug#861108: live-build: stretch image produced with default configuration does not boot

[Antonio Terceiro]

Package: live-build
Version: 1:20170213
Severity: grave
Justification: renders package unusable

Hi,

The image was built with:

$ lb config
$ sudo http_proxy=http://localhost:3142 lb build

And I tried to boot it in KVM with

$ kvm -cdrom live-image-amd64.hybrid.iso mydisk.img

I get the boot menu, but whether I select Live or Live (failsafe), it
hangs in a kernel panic saying the following:

  Kernel panic - not syncing: No working init found. Try passing init=
  option to kernel. See Linux Documentation/init.txt for guidance.

-- Package-specific info:

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

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

Versions of packages live-build depends on:
ii  debootstrap  1.0.90

Versions of packages live-build recommends:
ii  apt-utils   1.4
ii  cpio2.11+dfsg-6
ii  live-boot-doc   1:20170112
ii  live-config-doc 5.20170316
ii  live-manual-html [live-manual]  2:20151217.1
ii  wget1.19.1-3

live-build suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#859805: Patch proposal

[Scott Kitterman]

On Saturday, April 22, 2017 03:54:05 PM Scott Kitterman wrote:
> On Saturday, April 22, 2017 07:28:00 PM Niels Thykier wrote:
> > On Sat, 15 Apr 2017 00:39:56 + JC  wrote:
> > > Hi Scott,
> > > 
> > > Le ven. 14 avr. 2017 Ã  19:59, Scott Kitterman  a
> > > 
> > > écrit :
> > > > Thanks for the patch.
> > > > I still need to review the underlying issue.  I suspect it is user
> > > > error.
> > > > Scott K
> > > 
> > > Well, I was not sure myself, so I did install postfix into new jessie
> > > and
> > > stretch VMs and I've seen myself the same differences between the
> > > dynamicmaps.cf.
> > > 
> > > The thing is: when you upgrade, the file is already created and
> > > provisioned
> > > with the map entries; but they are just not valid anymore with a stretch
> > > postfix installation, since the pathnames changed from
> > > /usr/lib/postfix/dict_XXX.so to postfix-XXX.so (notice the full path
> > > removal _and_ the file name change).
> > > 
> > > I did compare the addmap function from the debian/functions file between
> > > jessie and stretch and they _do_ differ in the map line generated.
> > > 
> > > So the map lines already there _do_ need to get updated, either by the
> > > user
> > > itself (in such case we should announce it in a README.upgrade or
> > > equivalent) or by Debian. My opinion here is that the postinst script
> > > could
> > > manage this upgrade here without much "conffile" modification conflict.
> > > 
> > > :-)
> > 
> > Hey Scott,
> > 
> > Did you have any comments to the above?
> > 
> > (FTR, "dynamicmaps.cf" can't be a conffile unless the original postinst
> > is RC buggy as it seems to generate dynamicmaps.cf - or are you talking
> > about a different file?)
> > 
> > Thanks
> > ~Niels
> 
> I do not think it's the correct fix for the problem.  I hope to work on this
> in the next day or three.  This may mask an issue, but it's not a fix.
> 
> Scott K

Testing in a small chroot:

Jessie:
# apt-get install postfix-ldap
Install postfix and postfix-ldap 2.11.3-1

# cat /etc/postfix/dynamicmaps.cf
# Postfix dynamic maps configuration file.
#
#type   location of .so fileopen function   (mkmap func)
#   =   
tcp /usr/lib/postfix/dict_tcp.sodict_tcp_open
sqlite  /usr/lib/postfix/dict_sqlite.so dict_sqlite_open
ldap/usr/lib/postfix/dict_ldap.so   dict_ldap_open

This is correct for postfix 2.11.

Update sources.list to stretch and upgrade.  Upgrades postfix and postfix-ldap 
to 3.1.4-1.

# cat /etc/postfix/dynamicmaps.cf
# Postfix dynamic maps configuration file.
#
#type   location of .so fileopen function   (mkmap func)
#   =   
tcp /usr/lib/postfix/dict_tcp.sodict_tcp_open
sqlite  /usr/lib/postfix/dict_sqlite.so dict_sqlite_open
ldap/usr/lib/postfix/dict_ldap.so   dict_ldap_open

Upgrade problem confirmed.

New install on stretch:

# cat /etc/postfix/dynamicmaps.cf
sqlite  postfix-sqlite.so   dict_sqlite_open
ldappostfix-ldap.so dict_ldap_open

Restart on jessie, but add delmap to prerm in jessie.  After upgrade to 
stretch with 3.1.4:

# cat /etc/postfix/dynamicmaps.cf
# Postfix dynamic maps configuration file.
#
#type   location of .so fileopen function   (mkmap func)
#   =   
ldappostfix-ldap.so dict_ldap_open
sqlite  postfix-sqlite.so   dict_sqlite_open

Which is correct.

I think this is the more correct way to solve the problem.  I'll pursue a 
stable update to fix it there (debdiff attached for reference).

Scott Kdiff -u postfix-2.11.3/debian/changelog postfix-2.11.3/debian/changelog
--- postfix-2.11.3/debian/changelog
+++ postfix-2.11.3/debian/changelog
@@ -1,3 +1,11 @@
+postfix (2.11.3-1+deb8u1) stable; urgency=medium
+
+  * Add delmap to .prerm for all packages that contain map data types exposed
+through external .so files so that upgrades to stretch (where the
+associated files have moved) will be functional (Closes: #859805)
+
+ -- Scott Kitterman   Mon, 24 Apr 2017 13:15:36 -0400
+
 postfix (2.11.3-1) unstable; urgency=medium
 
   [Wietse Venema]
diff -u postfix-2.11.3/debian/postfix-cdb.prerm postfix-2.11.3/debian/postfix-cdb.prerm
--- postfix-2.11.3/debian/postfix-cdb.prerm
+++ postfix-2.11.3/debian/postfix-cdb.prerm
@@ -15,8 +15,11 @@
 #   
 # for details, see /usr/share/doc/packaging-manual/
 
+. /usr/share/postfix/postinst.functions
+
 case "$1" in
 remove|upgrade|deconfigure)
+delmap cdb
 #   install-info --quiet --remove /usr/info/#PACKAGE#.info.gz
 ;;
 failed-upgrade)
diff -u postfix-2.11.3/debian/postfix-ldap.prerm postfix-2.11.3/debian/postfix-ldap.prerm
--- postfix-2.11.3/debian/postfix-ldap.prerm
+++ 

Processed: Re: Bug#859926: breaks with pulse-audio as output when spawned by speechd-up from init system

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.8.6-4
Bug #859926 [speech-dispatcher] breaks with pulse-audio as output when spawned 
by speechd-up from init system
Marked as found in versions speech-dispatcher/0.8.6-4.

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

Bug#859926: breaks with pulse-audio as output when spawned by speechd-up from init system

[Cobra]

Control: found -1 0.8.6-4
thanks

Hi,

did another test:
The installation and start/stop/restart of speechd-up work when
changing /etc/speech-dispatcher/speechd.conf from

# AudioOutputMethod "pulse"
to
AudioOutputMethod "pulse,alsa"

But doing so will break pulseaudio for users. There will be no audio
output from applications like vlc or firefox until speechd-up is
stopped. vlc is showing only "dummy output" instead of the usual
"Built-in Audio Analog Stereo" in Audio/Audio Device when speechd-up is
running.
Starting speechd-up after stopping it and using pulse as a user fails
until the running pulseaudio daemon is killed.
Switching vlc to use only alsa (both output module and device) works
with speechd-up running.

This whole issue looks very similar to #521675 (pulseaudio), note the
mention of speech-dispatcher which turned out to be the cause for one
user.
There are also #625235 and #670740 in speech-dispatcher.
A solution might be running pulseaudio as system-wide daemon. But I
don't know whether this is desirable or not, because there are some
downsides, including security implications.

Bug#861102: gnome-media: missing Breaks: gnome-media-common (<< 2.91.0), libgnome-media-dev (<< 2.91.0), libgnome-media0 (<< 2.91.0)

[Andreas Beckmann]

Package: gnome-media
Version: 3.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by another package.
This is causes by having Replaces without matching Breaks.

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

5m14.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/gnome-sound-recorder/ui/ui.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/fr/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/fr/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/ca/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/ca/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/es/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/es/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/da/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/it/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/it/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/cs/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/cs/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/sv/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/sv/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/ru/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/uk/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/uk/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/en_GB/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/C/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/C/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file /usr/share/gnome/help/gnome-sound-recorder/C/legal.xml 
(from gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/zh_CN/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/de/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/de/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/el/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/el/figures/grecord_window.png (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/gnome/help/gnome-sound-recorder/oc/gnome-sound-recorder.xml (from 
gnome-media-common package)
  debsums: missing file /usr/share/gconf/schemas/gnome-sound-recorder.schemas 
(from gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-en_GB.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-sv.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-uk.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-ca.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-it.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-cs.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-C.omf (from 
gnome-media-common package)
  debsums: missing file 
/usr/share/omf/gnome-sound-recorder/gnome-sound-recorder-fr.omf (from 

Bug#809669: unattended-upgrades: files got created under /var/ mountpoint

[Louis Bouchard]

Hello,

Here is the patch for this issue that I uploaded to Ubuntu. It is slightly
adapted to take into account the possibility of being install on a non-systemd
installation.

I tried to make the changelog entry as explicit as possible but here are some
details.

As outlined previously, the systemd unit is changed to be an ExecStart instead
of an ExecStop. RequiresMountsFor= are added for /var/log, /var/run, /var/lib &
/boot. Disabling DefaultDependencies is removed so, as outlined previously,
local-fs.target might be superfluous.  RemainAfterExit is set to Yes so the unit
is seen as started. WantedBy is set to multi-user.target

This introduces a problem since Bug #797108[1] is causing the unit not to be
enabled upon upgrade. The following is done to work around this issue:

1) On systemd enabled system, postinst forces the unattended-upgrades service to
be disabled before deb-systemd-helper is executed so the previous
shutdown.target symlink does not remain.

2) At the end of the postinst script, after the deb-systemd-helper has been run,
manually enable and start the service. This will leave the service correctly
configured, as if the deb-systemd-helper had no bug.

3) systemctl enable requires the SysV init script to have a Default-Start
statement in the header otherwise it fails. Add the header in the script.

4) Remove the override_dh_installinit since it uses the 'stop' option which is
no longer available hence switching to 'default' which is the normal installinit
behavior. The postinst script also needs to cleanup the faulty stop symlink
created previously otherwise the systemclt enable fails.

5) Add DEP8 tests to verify that the unit is correctly started and that
InstallOnShutdown works as expected.

I have only tested the upgrade from 0.93.1 to 0.93.2 on Debian/Sid but I have
done extensive testing on Ubuntu which includes :

 * do-release-upgrade from Trusty(upstart) to Xenial(systemd)
 * upgrade on Xenial, Yakkety, Zesty & Artful

Please let me know if I can help with any more testing.

Kind regards,

...Louis

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797108
--
Louis Bouchard
Software engineer,
Ubuntu Developer / Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61
@@ -1,3 +1,34 @@
+unattended-upgrades (0.93.2) unstable; urgency=medium
+
+  [ Louis Bouchard ]
+  * Fix the unattended-upgrades.service unit not correctly working:
+- d/rules : Remove the override_dh_installinit. The stop option is no 
longer
+  available so the command falls back to default. This is the normal
+  behavior so the override is not required
+- d/unattended-upgrades.init : Add Default-Start runlevels, otherwise the
+  unattended-upgrades.service unit cannot be enabled on boot
+- d/postinst : Cleanup the stop symlinks created by the wrong
+  override_dh_installinit. Without that, the systemd unit cannot be
+  enabled correctly.
+  Force disable the service before deb-systemd-helper runs so the old
+  symlink is not left dangling (workaround for Debian Bug #797108).
+  Force enable and start of the systemd unit to work around Debian Bug 
#797108
+  which fails to enable systemd units correctly when WantedBy= statement
+  is changed which is the case here.
+- d/unattended-upgrades.service : Fix the service so it runs correctly on
+  shutdown :
+Remove DefaultDependencies=no : Breaks normal shutdown dependencies
+Set After= to network.target and local-fs.target. Since our service is
+now ExecStop, it will run before network and local-fs become 
unavailable.
+Add RequiresMountsFor=/var/log /var/run /var/lib /boot : Necessary if
+/var is a separate file system. Set WantedBy= to multi-user.target
+- Add DEP8 tests to verify the following :
+  Verify that the unattended-upgrades.service unit is enabled and started.
+  Verify that InstallOnShutdown works when configured.
+(Closes: #809669)
+
+ -- Louis Bouchard   Mon, 24 Apr 2017 14:42:01 +0200
+
 unattended-upgrades (0.93.1) unstable; urgency=medium
 
   [ Brian Murray ]
diff -Nru unattended-upgrades-0.93.1/debian/postinst 
unattended-upgrades-0.93.2/debian/postinst
--- unattended-upgrades-0.93.1/debian/postinst  2016-12-11 11:31:26.0 
+0100
+++ unattended-upgrades-0.93.2/debian/postinst  2017-04-24 14:42:01.0 
+0200
@@ -61,6 +61,20 @@
 && [ -f /etc/rc6.d/S[0-9][0-9]unattended-upgrades ] ; then
 update-rc.d -f unattended-upgrades remove
 fi
+# Recover from broken dh_installinit override in versions < 0.93.2
+if dpkg --compare-versions "$2" lt "0.93.2"; then
+if [ -f /etc/rc0.d/K[0-9][0-9]unattended-upgrades ] \
+&& [ -f /etc/rc6.d/K[0-9][0-9]unattended-upgrades ] ; then
+   update-rc.d -f unattended-upgrades remove
+   fi
+   # If running systemd, explicitely disable the service otherwise
+ 

Bug#858942: closed by Hans-Christoph Steiner <h...@eds.org> (Bug#858942: fixed in android-platform-system-core 1:7.0.0+r33-1)

[Axel Beckert]

Hi Hans,

Debian Bug Tracking System wrote:
> #858942: android-tools-adb + android-tools-fastboot: Uninstallable due to 
> Depends/Conflicts chain
[...]
>* New upstream release (Closes: #858177, #859081, #858942)

I really wonder how a new a new upstream release can fix such a
pure packaging issue...

So the next time, please add proper changelog items, which also relate
to the bug report they're closing. Thanks in advance!

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

Bug#859081: marked as done (API change in utf16_to_utf8 breaking other packages)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 15:04:42 +
with message-id 
and subject line Bug#859081: fixed in android-platform-system-core 1:7.0.0+r33-1
has caused the Debian Bug report #859081,
regarding API change in utf16_to_utf8 breaking other packages
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.)


-- 
859081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-frameworks-base
Version: 1:7.0.0+r1-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

android-platform-frameworks-base fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
 debian/rules override_dh_auto_build-arch
  make[1]: Entering directory '«BUILDDIR»'
  make -f debian/libandroidfw.mk
  make[2]: Entering directory '«BUILDDIR»'
  mkdir --parents debian/out
  g++ libs/androidfw/Asset.cpp libs/androidfw/AssetDir.cpp 
libs/androidfw/AssetManager.cpp libs/androidfw/LocaleData.cpp 
libs/androidfw/misc.cpp libs/androidfw/ObbFile.cpp 
libs/androidfw/ResourceTypes.cpp libs/androidfw/StreamingZipInflater.cpp 
libs/androidfw/TypeWrappers.cpp libs/androidfw/ZipFileRO.cpp 
libs/androidfw/ZipUtils.cpp -o debian/out/libandroidfw.so.0 -g -O2 
-fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -DSTATIC_ANDROIDFW_FOR_TOOLS -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -I/usr/include/android -Iinclude -Wl,-z,relro 
-fPIC -shared -Wl,-soname,libandroidfw.so.0 
-Wl,-rpath=/usr/lib/x86_64-linux-gnu/android -lz 
-L/usr/lib/x86_64-linux-gnu/android -lziparchive -lutils -lcutils -llog
  In file included from /usr/include/android/cutils/log.h:1:0,
   from /usr/include/android/utils/Log.h:31,
   from include/androidfw/ByteBucketArray.h:20,
   from libs/androidfw/ResourceTypes.cpp:32:
  libs/androidfw/ResourceTypes.cpp: In member function 'ssize_t 
android::ResTable::Theme::getAttribute(uint32_t, android::Res_value*, 
uint32_t*) const':
  /usr/include/android/log/log.h:618:39: warning: format '%zd' expects argument 
of type 'signed size_t', but argument 4 has type 'uint32_t {aka unsigned int}' 
[-Wformat=]
   __android_log_print(prio, tag, fmt)
 ^
  /usr/include/android/log/log.h:461:5: note: in expansion of macro 
'android_printLog'
   android_printLog(priority, tag, __VA_ARGS__)
   ^~~~
  /usr/include/android/log/log.h:453:5: note: in expansion of macro 'LOG_PRI'
   LOG_PRI(ANDROID_##priority, tag, __VA_ARGS__)
   ^~~
  /usr/include/android/log/log.h:128:27: note: in expansion of macro 'ALOG'
   #define ALOGI(...) ((void)ALOG(LOG_INFO, LOG_TAG, __VA_ARGS__))
 ^~~~
  libs/androidfw/ResourceTypes.cpp:3542:21: note: in expansion of macro 'ALOGI'
   ALOGI("Desired type index is %zd in avail %zu", t, 
Res_MAXTYPE + 1);
   ^
  ln -s libandroidfw.so.0 debian/out/libandroidfw.so
  make[2]: Leaving directory '«BUILDDIR»'
  make -f debian/libaapt.mk
  make[2]: Entering directory '«BUILDDIR»'
  mkdir --parents debian/out
  g++ tools/aapt/AaptAssets.cpp tools/aapt/AaptConfig.cpp 
tools/aapt/AaptUtil.cpp tools/aapt/AaptXml.cpp tools/aapt/ApkBuilder.cpp 
tools/aapt/Command.cpp tools/aapt/CrunchCache.cpp tools/aapt/FileFinder.cpp 
tools/aapt/Images.cpp tools/aapt/Package.cpp tools/aapt/pseudolocalize.cpp 
tools/aapt/Resource.cpp tools/aapt/ResourceFilter.cpp 
tools/aapt/ResourceIdCache.cpp tools/aapt/ResourceTable.cpp 
tools/aapt/SourcePos.cpp tools/aapt/StringPool.cpp tools/aapt/WorkQueue.cpp 
tools/aapt/XMLNode.cpp tools/aapt/ZipEntry.cpp tools/aapt/ZipFile.cpp -o 
debian/out/libaapt.so.0 -g -O2 -fdebug-prefix-map=«BUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -I/usr/include/android 
-DSTATIC_ANDROIDFW_FOR_TOOLS -DAAPT_VERSION=\"24.0.0\" -Iinclude -Wl,-z,relro 
-fPIC -shared -Wl,-soname,libaapt.so.0 
-Wl,-rpath=debian/out:/usr/lib/x86_64-linux-gnu/android -lpng -lexpat -lz 
-Ldebian/out -landroidfw -L/usr/lib/x86_64-linux-gnu/android -llog -lutils
  ln -s libaapt.so.0 debian/out/libaapt.so
  make[2]: Leaving directory '«BUILDDIR»'
  make -f debian/aapt.mk
  make[2]: Entering directory '«BUILDDIR»'
  mkdir --parents debian/out
  g++ tools/aapt/Main.cpp -o debian/out/aapt -g -O2 

Bug#858942: marked as done (android-tools-adb + android-tools-fastboot: Uninstallable due to Depends/Conflicts chain)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 15:04:42 +
with message-id 
and subject line Bug#858942: fixed in android-platform-system-core 1:7.0.0+r33-1
has caused the Debian Bug report #858942,
regarding android-tools-adb + android-tools-fastboot: Uninstallable due to 
Depends/Conflicts chain
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.)


-- 
858942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: android-tools-adb,android-tools-fastboot
Severity: serious
Version: android-platform-system-core/1:7.0.0+r1-4

android-tools-adb and android-tools-fastboot both depend on a package
(adb respectively fastboot) which again Replaces/Breaks
android-tools-adb respectively android-tools-fastboot:

Package: android-tools-adb
Version: 1:7.0.0+r1-4
Depends: adb

Package: adb
Version: 1:7.0.0+r1-4
Replaces: android-tools-adb
Provides: android-tools-adb
Breaks: android-tools-adb

Package: android-tools-fastboot
Version: 1:7.0.0+r1-4
Depends: fastboot

Package: fastboot
Version: 1:7.0.0+r1-4
Replaces: android-tools-fastboot
Provides: android-tools-fastboot
Breaks: android-tools-fastboot

Hence both transitional packages are not installable as they
transitively conflict with themselves.

The Replaces and Breaks headers above likely need to be versioned
instead of the current unversioned restrictions.

Issue found by Arian Sanusi and reported on IRC.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: android-platform-system-core
Source-Version: 1:7.0.0+r33-1

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated 
android-platform-system-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Apr 2017 15:53:07 +0200
Source: android-platform-system-core
Binary: android-liblog android-liblog-dev android-libcutils 
android-libcutils-dev adb android-libsparse android-libsparse-dev 
android-libutils android-libutils-dev android-libziparchive 
android-libziparchive-dev android-platform-system-core-headers 
android-libbacktrace android-libbacktrace-dev android-libadb android-libadb-dev 
android-libbase android-libbase-dev fastboot simg2img img2simg append2simg 
android-tools-adb android-tools-fastboot
Architecture: source amd64 all
Version: 1:7.0.0+r33-1
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Hans-Christoph Steiner 
Description:
 adb- Android Debug Bridge
 android-libadb - Library for Android Debug Bridge
 android-libadb-dev - Library for Android Debug Bridge - Development files
 android-libbacktrace - Android backtrace library
 android-libbacktrace-dev - Android backtrace library - Development files
 android-libbase - Android base library
 android-libbase-dev - Android base library - Development files
 android-libcutils - Android utils library for C
 android-libcutils-dev - Android utils library for C - Development files
 android-liblog - Android NDK logger interfaces
 android-liblog-dev - Android NDK logger interfaces - Development files
 android-libsparse - Library for sparse files
 android-libsparse-dev - Library for sparse files - Development files
 android-libutils - Android Utility Function Library
 android-libutils-dev - Android Utility Function Library - Development files
 android-libziparchive - Library for ZIP archives
 android-libziparchive-dev - 

Bug#860879: [Packaging] Bug#860879: closed by Holger Levsen <hol...@debian.org> (Bug#860879: fixed in munin 2.999.6-2)

[Holger Levsen]

On Mon, Apr 24, 2017 at 10:29:26AM +0200, Frederik Himpe wrote:
> Ouch, apparently I made a typo in the title of my bug report: the
> package name is libio-string-perl, not libo-string-perl

thanks, fixed by uploading -3


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: owner 861021

[Debian Bug Tracking System]

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

> owner 861021 tmanc...@debian.org
Bug #861021 [spin] spin: missing Breaks+Replaces: staden (<< 2.0.0+b11)
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Bug#858794: marked as done (gmime: Tests contain a MIME message with a (presumably non-free) Playboy/Hustler/something photo)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 13:33:49 +
with message-id 
and subject line Bug#858794: fixed in gmime 2.6.22+dfsg1-1
has caused the Debian Bug report #858794,
regarding gmime: Tests contain a MIME message with a (presumably non-free) 
Playboy/Hustler/something photo
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.)


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

With package 'ripmime' installed:


$ apt-get source gmime-bin
$ cd gmime-2.6.22/tests/
$ mkdir attachments
$ cd attachments
$ cat ../message-partial.* ../*.eml |ripmime -i -
$ ls -l *.jpg
-rw--- 1 sliedes sliedes 115113 Mar 26 22:45 2377h003.jpg
-rw--- 1 sliedes sliedes  17527 Mar 26 22:45 leonc.jpg
-rw--- 1 sliedes sliedes  45064 Mar 26 22:45 SkipStone-Banner.jpg


The file 2377h003.jpg is a photograph of a scantily clad model
apparently taken by a pornographer named Suze Randall. The photograph,
which "ripmime" unfortunately does not extract fully from the
multipart message (you can build gmime and use tests/test-partial
message-partial.* to combine the parts; the size should be 117415
bytes), contains the copyright notice "(c) 2001 Suze Randall" in the
lower right corner.

The file leonc.jpg is apparently part of a movie poster of the movie
Leon: The Professional and depicts the character "Mathilda", a 12-year
old girl played by Natalie Portman, with a huge gun in her hand.

SkipStone-Banner appears to be a partial banner of an old web browser
("Gtk+ only browser"; I did not inspect what its license is, but did
find a source download link).

Sami


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

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gmime
Source-Version: 2.6.22+dfsg1-1

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gmime 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, 24 Apr 2017 09:04:52 -0400
Source: gmime
Binary: libgmime-2.6-dev gir1.2-gmime-2.6 libgmime-2.6-doc libgmime-2.6-0 
gmime-bin libgmime2.6-cil libgmime2.6-cil-dev monodoc-gmime2.6-manual
Architecture: source
Version: 2.6.22+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Description:
 gir1.2-gmime-2.6 - MIME message parser and creator library - GObject 
introspection d
 gmime-bin  - MIME message parser and creator library - runtime binaries
 libgmime-2.6-0 - MIME message parser and creator library
 libgmime-2.6-dev - MIME message parser and creator library - development files
 libgmime-2.6-doc - MIME message parser and creator library - documentation
 libgmime2.6-cil - CLI binding for the GMime library
 libgmime2.6-cil-dev - CLI binding for the GMime library -- development files
 monodoc-gmime2.6-manual - compiled XML documentation for GMime
Closes: 858794
Changes:
 gmime (2.6.22+dfsg1-1) unstable; urgency=medium
 .
   * new dfsg-free upstream tarball of non-free attachments (Closes:
 #858794)
   * swap maintainer and uploader
   * use dversionmangle in debian/watch to adjust for repacked dfsg orig.tgz
Checksums-Sha1:
 0881fe6fd06addb9ddc46d082550cccb19e7aab7 2808 gmime_2.6.22+dfsg1-1.dsc
 ae68e8b89746098547415c2c65c9b070d385be7c 5144636 gmime_2.6.22+dfsg1.orig.tar.xz
 

Processed: severity of 851604 is serious

[Debian Bug Tracking System]

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

> severity 851604 serious
Bug #851604 [emacs24] emacs24: missing Breaks: prom-mew (<= 2.00+3.2am01-1)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#861040: [DRE-maint] Bug#861040: camping: broken symlink: /usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> ../../../../fonts/truetype/lato/Lato-RegularItalic.ttf

[Christian Hofstaedtler]

* Chris Lamb  [170424 11:45]:
> > The fonts-lato ships /usr/share/fonts/truetype/lato/Lato-Italic.ttf
> > instead.
> 
> Indeed. Patch attached.

> - ln -s /usr/share/fonts/truetype/lato/Lato-RegularItalic.ttf 
> debian/camping/usr/share/doc/camping/rdoc/fonts/
> + ln -s /usr/share/fonts/truetype/lato/Lato-Italic.ttf 
> debian/camping/usr/share/doc/camping/rdoc/fonts/

Note that rdoc really expects a file named Lato-RegularItalic.ttf
in that place.

  C.

Bug#860684: [pkg-go] Bug#860684: golang-github-streadway-amqp: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/streadway/amqp returned exit code 1

[Sascha Steinbiss]

Hi all,

[...]
>> === RUN   TestGoFuzzCrashers
>> --- FAIL: TestGoFuzzCrashers (0.00s)
>> panic: runtime error: makeslice: len out of range [recovered]
>>  panic: runtime error: makeslice: len out of range
>>
>> goroutine 3445 [running]:
>> panic(0x8249520, 0x18a0e0a8)
>>  /usr/lib/go-1.7/src/runtime/panic.go:500 +0x331
>> testing.tRunner.func1(0x193c6280)
>>  /usr/lib/go-1.7/src/testing/testing.go:579 +0x14f
>> panic(0x8249520, 0x18a0e0a8)
>>  /usr/lib/go-1.7/src/runtime/panic.go:458 +0x40b
>> github.com/streadway/amqp.readLongstr(0x8343dc0, 0x190500c0, 0x0, 0x0, 0x0, 
>> 0x0)
>>  
>> /<>/obj-i686-linux-gnu/src/github.com/streadway/amqp/read.go:112
>>  +0xeb
>> github.com/streadway/amqp.readTable(0x8343dc0, 0x190500c0, 0x0, 0x0, 0x0)
>>  
>> /<>/obj-i686-linux-gnu/src/github.com/streadway/amqp/read.go:269
>>  +0x7e
>> github.com/streadway/amqp.(*reader).parseHeaderFrame(0x18664f2c, 0x19051610, 
>> 0xefbfbd5b, 0x0, 0x0, 0x0, 0x0)
>>  
>> /<>/obj-i686-linux-gnu/src/github.com/streadway/amqp/read.go:359
>>  +0x3cc
>> github.com/streadway/amqp.(*reader).ReadFrame(0x18664f2c, 0x0, 0x0, 0x0, 0x0)
>>  
>> /<>/obj-i686-linux-gnu/src/github.com/streadway/amqp/read.go:64 
>> +0x2f0
>> github.com/streadway/amqp.TestGoFuzzCrashers(0x193c6280)
>>  
>> /<>/obj-i686-linux-gnu/src/github.com/streadway/amqp/read_test.go:17
>>  +0x150
>> testing.tRunner(0x193c6280, 0x829a294)
>>  /usr/lib/go-1.7/src/testing/testing.go:610 +0x8c
>> created by testing.(*T).Run
>>  /usr/lib/go-1.7/src/testing/testing.go:646 +0x2a5
>> exit status 2
>> FAIL github.com/streadway/amqp   2.576s
>> dh_auto_test: go test -v -p 1 github.com/streadway/amqp returned exit code 1

This seems to be related to this particular test case trying to create a
slice with a length exceeding a 32-bit signed integer, which is a limit
for slices in Go. Let's see what upstream says, there's a GitHub issue
in for that now.

Kind regards
Sascha



signature.asc
Description: OpenPGP digital signature

Bug#861077: icinga-idoutils: fails to upgrade squeeze -> wheezy -> jessie -> stretch

[Andreas Beckmann]

Package: icinga-idoutils
Version: 1.13.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze' to 'wheezy' to 'jessie'.
It installed fine in 'squeeze', and upgraded to 'wheezy' and 'jessie'
successfully, but then the upgrade to 'stretch' failed.

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

  Setting up icinga-idoutils (1.13.4-1) ...
  Installing new version of config file 
/etc/icinga/objects/ido2db_check_proc.cfg ...
  Installing new version of config file /etc/init.d/ido2db ...
  dbconfig-common: writing config to /etc/dbconfig-common/icinga-idoutils.conf
  Replacing config file /etc/dbconfig-common/icinga-idoutils.conf with new 
version
  Replacing config file /etc/icinga/ido2db.cfg with new version
  creating database backup in 
/var/cache/dbconfig-common/backups/icinga-idoutils_1.11.6-1+b4.2017-04-22-08.58.42.
  applying upgrade sql for 1.11.6-1+b4 -> 1.12.0.
  applying upgrade sql for 1.11.6-1+b4 -> 1.13.0.
  error encountered processing 
/usr/share/dbconfig-common/data/icinga-idoutils/upgrade/pgsql/1.13.0:
  ERROR: constraint "uq_servicedependencies" of relation 
"icinga_servicedependencies" does not exist
  dbconfig-common: icinga-idoutils configure: aborted.
  dbconfig-common: flushing administrative password
  dpkg: error processing package icinga-idoutils (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


icinga-idoutils_1.13.4-1.log.gz
Description: application/gzip

Bug#859655: Status update?

[Dr. Tobias Quathamer]

Hi Michael,

how is the status of this bug? There has not been visible activity in 
the bug log for about 10 days ...


Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#839358: marked as done (jd: FTBFS: drawareabase.h:333:51: error: cannot convert 'Glib::RefPtr' to 'const bool' in return)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 14:50:17 +0300
with message-id <20170424115017.irmqk25ex2eaufgc@localhost>
and subject line Already fixed in unstable
has caused the Debian Bug report #839358,
regarding jd: FTBFS: drawareabase.h:333:51: error: cannot convert 
'Glib::RefPtr' to 'const bool' in return
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.)


-- 
839358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jd
Version: 1:2.8.9-150226-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 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):
> g++ -DHAVE_CONFIG_H -I. -I../..  -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 
> -pthread -I/usr/include/gtkmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include -I/usr/include/atkmm-1.6 
> -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 
> -I/usr/include/gdkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include 
> -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
> -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include 
> -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
> -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -ggdb -Wall -c -o 
> drawareabase.o drawareabase.cpp
> In file included from drawareabase.cpp:9:0:
> drawareabase.h: In member function 'const bool 
> ARTICLE::DrawAreaBase::is_drawarea_realized()':
> drawareabase.h:333:51: error: cannot convert 'Glib::RefPtr' to 
> 'const bool' in return
>  const bool is_drawarea_realized(){ return m_window; }
>^~~~
> Makefile:464: recipe for target 'drawareabase.o' failed
> make[4]: *** [drawareabase.o] Error 1

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

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/jd_2.8.9-150226-5_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 ---
jd (1:2.8.9-150226-6) unstable; urgency=medium
...
  * debian/patches
- add fix-build-failure-with-newer-lib.patch to fix FTBFS
...
 -- Hideki Yamane   Mon, 24 Apr 2017 07:21:46 +0900

(Marking as fixed did not close the bug.)

cu
Adrian

-- 

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

Bug#860692: gopacket: FTBFS on i386: XXX

[Sascha Steinbiss]

tags 860692 patch
thanks


Hi all,

[...]
> # Copy test files to build dir
> cp pcap/*.pcap obj-i386-linux-gnu/src/github.com/google/gopacket/pcap/
> cp: target 'obj-i386-linux-gnu/src/github.com/google/gopacket/pcap/'
is not a directory
> debian/rules:19: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1

I have fixed this issue by constructing the target directory name using
DEB_HOST_GNU_TYPE instead of DEB_HOST_MULTIARCH, which correctly yields
'obj-i686-linux-gnu'. After applying attached patch, I was able to
correctly build gopacket on i386 stretch.

Best regards
Sascha
diff --git a/debian/rules b/debian/rules
index a51674b..723de78 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ override_dh_auto_configure:
 	dh_auto_configure
 	rm -rf $(patsubst %,obj-*/src/$(DH_GOPKG)/%,$(NOBUILD))
 	# Copy test files to build dir
-	cp pcap/*.pcap obj-$(DEB_HOST_MULTIARCH)/src/$(DH_GOPKG)/pcap/
+	cp pcap/*.pcap obj-$(DEB_HOST_GNU_TYPE)/src/$(DH_GOPKG)/pcap/
 
 override_dh_install:
 	dh_install --fail-missing


signature.asc
Description: OpenPGP digital signature

Processed: Re: gopacket: FTBFS on i386: XXX

[Debian Bug Tracking System]

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

> tags 860692 patch
Bug #860692 [src:gopacket] gopacket: FTBFS on i386: XXX
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#860986: python-iptables library did not work

[Chris Lamb]

retitle 860986 python-iptables: import raises AttributeError: 'NoneType' object 
has no attribute 'throw_exception'
thanks


I think the problem is actually deeper. Even after I "fix" the custom
library loading code with something like:

--- a/iptc/util.py
+++ b/iptc/util.py
@@ -78,7 +78,8 @@ def _find_library(*names):
 if version_info > (3, ):
 ext = get_config_var("EXT_SUFFIX")
 else:
-ext = get_config_var('SO')
+import imp
+ext = [x for x, y, z in imp.get_suffixes() if z == 
imp.C_EXTENSION][0]
 for name in names:
 libnames = [name, "lib" + name, name + ext, "lib" + name + ext]
 libdir = os.environ.get('IPTABLES_LIBDIR', None)

… then I end up with:

 Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/iptc/__init__.py", line 10, in 
from iptc.ip4tc import (is_table_available, Table, Chain, Rule, Match, 
Target,
  File "/usr/lib/python2.7/dist-packages/iptc/ip4tc.py", line 36, in 
xtables(NFPROTO_IPV4)
  File "/usr/lib/python2.7/dist-packages/iptc/xtables.py", line 814, in __new__
obj._xtinit(proto)
  File "/usr/lib/python2.7/dist-packages/iptc/xtables.py", line 829, in _xtinit
(xtables_version))
iptc.xtables.XTablesError: unknown xtables version 12



Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/iptc/util.py b/iptc/util.py
index a587e7e..43f5ca8 100644
--- a/iptc/util.py
+++ b/iptc/util.py
@@ -78,7 +78,8 @@ def _find_library(*names):
 if version_info > (3, ):
 ext = get_config_var("EXT_SUFFIX")
 else:
-ext = get_config_var('SO')
+import imp
+ext = [x for x, y, z in imp.get_suffixes() if z == imp.C_EXTENSION][0]
 for name in names:
 libnames = [name, "lib" + name, name + ext, "lib" + name + ext]
 libdir = os.environ.get('IPTABLES_LIBDIR', None)

Processed: Re: python-iptables library did not work

[Debian Bug Tracking System]

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

> retitle 860986 python-iptables: import raises AttributeError: 'NoneType' 
> object has no attribute 'throw_exception'
Bug #860986 [python-iptables] python-iptables library did not work
Changed Bug title to 'python-iptables: import raises AttributeError: 'NoneType' 
object has no attribute 'throw_exception'' from 'python-iptables library did 
not work'.
> thanks
Stopping processing here.

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

Bug#860984: marked as done (khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 10:18:42 +
with message-id 
and subject line Bug#860984: fixed in khal 0.9.5-2
has caused the Debian Bug report #860984,
regarding khal: Please reference 
debian/patches/0002-Reference-license-from-copyright-file.patch in 
debian/copyright
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.)


-- 
860984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khal
Version: 0.9.5-1
Severity: serious
X-Debbugs-CC: Filip Pytloun 

Hi,

I just ACCEPTed khal from NEW but noticed it wasn't 100% obvious
from debian/copyright that the 0002-Reference-license-from-copyright-file.patch
patch existed.

Please update your debian/copyright file, at least to point someone
in the above file's direction. your next upload.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: khal
Source-Version: 0.9.5-2

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

Debian distribution maintenance software
pp.
Filip Pytloun  (supplier of updated khal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Apr 2017 09:45:57 +0200
Source: khal
Binary: khal khal-doc
Architecture: source
Version: 0.9.5-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Filip Pytloun 
Description:
 khal   - Standards based CLI and terminal calendar program
 khal-doc   - Standards based CLI and terminal calendar program - documentation
Closes: 860984
Changes:
 khal (0.9.5-2) unstable; urgency=medium
 .
   * d/copyright: mention presence of
 0002-Reference-license-from-copyright-file.patch (Closes: #860984)
   * d/copyright: add upstream contact
   * d/copyright: update copyright year
Checksums-Sha1:
 b23f3ab9aac6348061611d1e1da5c62f64335ca9 2389 khal_0.9.5-2.dsc
 fef7e59da396e15fde9b0540409cf848722e872a 6628 khal_0.9.5-2.debian.tar.xz
 a00e38a58546e955eaf02c59623908110321ade8 7207 khal_0.9.5-2_source.buildinfo
Checksums-Sha256:
 ed4dd1c3f2eccfe947d50f1fa406a09541101326cdc79046c2ca0f7f09c81850 2389 
khal_0.9.5-2.dsc
 5424e9e2e574de955b922555cdde2814178b448e6ceb8054d12963b242aab28d 6628 
khal_0.9.5-2.debian.tar.xz
 fd0d1152379f0068ab90383241ca1dd82435ef2f15ccf69265a6ec87f74971f4 7207 
khal_0.9.5-2_source.buildinfo
Files:
 2e6b43921839023d19fe4a2ef084aa7c 2389 utils optional khal_0.9.5-2.dsc
 a089f64c7c4d82d3cf5ef53e3e76b21c 6628 utils optional khal_0.9.5-2.debian.tar.xz
 bfe91abb182716ebb5d699cd1e29eea9 7207 utils optional 
khal_0.9.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEOAKTsWyox6BpW4soaAgjm5xy5hsFAlj9zMoRHGZpbGlwQHB5
dGxvdW4uY3oACgkQaAgjm5xy5hvS0w//Qy1Kv0PcMijHqFu3Q2NPaMbYx0e1tN9b
34uWE6i90G/wlclDAkBpzN8zO6N5Ocz3n7D9+oJdmC8KbTVO2wpxP22azoTNEww0
wsPNVw8CgMyfoog2MVP9F/NZ9gJnqDBwJ+nd6xDGQC2U/0U7ihzl85JTOZi7fh0P
gj6BbXTc0C/H12xcW+K1X2FPqi+Zb+kZKMsdeob9AlhmBcIEt7TKCGLtWg7h0Ewe
C3LekDD71/HHg097KENFBXp4ezIbnqrn6mgWvpXFPKvISr7fEp3xi/avuHbV1Xy0
N1Kd0AI1pqh2jc95VN/yMjsF6yvIIMeSCB2+rRL9MQUxSSjDJdk7/VZsgkVX2UhO
0Y8k47zbJgC7bsM7DKIlv2RblkIQmnY5ex1CuW7HWSHV86ZvNfD9KrnoRW0c0aRS
dky7gn3xidfLGP371Py7fK1lGAT6fw2e0U1gbtDVjOniCQ66e2E5TKIQiFqCvDP+
AG61uVZJTYvJPFugZSkoBnRQwX7SsTcpoXNwOfXrVD11VOYgHomSSMdG/Jrpb5wO
azzmyDiwbV7Hva+hQHzTnnxn8InB8vBTgwTKlauHHM72FG95JSDQ1yoRSGQOiRRr
+zkV0ZOUhCwuMrj493j3/6pS7mcvHYx9rAvzaFHqtgBVCYcnRffN93t53iS10/6B
h3KPyt6ea1Q=
=OJNa
-END PGP SIGNATURE End Message ---

Processed: Re: Patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #856720 [diaspora-installer] diaspora{, -installer}: fails to install: 
Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp
Added tag(s) pending.

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

Bug#856720: Patch

[Pirate Praveen]

Control: tags -1 pending

On Sun, 23 Apr 2017 17:20:21 +0530 Pirate Praveen  wrote:
> Shamil who got the same error was running in docker. I will add creating
> this directory in postinstas well
> 

Now postinst will create this directory so systems without systemd like docker 
also works well.

Bug#856720: Patch

[Shanavas]

Good, now works fine.

Seems like this is a global issue with docker (or any non-systemd virtual envs) 
which affects most of the packages.

On April 23, 2017 2:50:21 PM GMT+03:00, Pirate Praveen  
wrote:
>On Mon, 17 Apr 2017 14:07:45 + shana...@disroot.org wrote:
>> Package: diaspora-common
>> Followup-For: Bug #856720
>> Tags: patch
>> 
>> attaching patch
>> Shanavas M
>
>This is supposed to be created by debian/tmpfiles.d/diaspora.conf and
>works well with systemd. Hence I could not reproduce locally (host and
>lxc both had systemd)
>
>Shamil who got the same error was running in docker. I will add
>creating
>this directory in postinstas well

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#861040: camping: broken symlink: /usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> ../../../../fonts/truetype/lato/Lato-RegularItalic.ttf

[Chris Lamb]

tags 861040 + patch
thanks

> The fonts-lato ships /usr/share/fonts/truetype/lato/Lato-Italic.ttf
> instead.

Indeed. Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/rules b/debian/rules
index 815ac32..d3dba6f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,7 +34,7 @@ override_dh_installdocs:
ln -s /usr/share/fonts/truetype/lato/Lato-Light.ttf 
debian/camping/usr/share/doc/camping/rdoc/fonts/
ln -s /usr/share/fonts/truetype/lato/Lato-LightItalic.ttf 
debian/camping/usr/share/doc/camping/rdoc/fonts/
ln -s /usr/share/fonts/truetype/lato/Lato-Regular.ttf 
debian/camping/usr/share/doc/camping/rdoc/fonts/
-   ln -s /usr/share/fonts/truetype/lato/Lato-RegularItalic.ttf 
debian/camping/usr/share/doc/camping/rdoc/fonts/
+   ln -s /usr/share/fonts/truetype/lato/Lato-Italic.ttf 
debian/camping/usr/share/doc/camping/rdoc/fonts/
 
 override_dh_auto_clean:
dh_auto_clean

Processed: Re: camping: broken symlink: /usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> ../../../../fonts/truetype/lato/Lato-RegularItalic.ttf

[Debian Bug Tracking System]

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

> tags 861040 + patch
Bug #861040 [camping] camping: broken symlink: 
/usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> 
../../../../fonts/truetype/lato/Lato-RegularItalic.ttf
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#860662: mlucas: FTBFS on i386: dh_auto_test: make -j64 check VERBOSE=1 returned exit code 2

[Alex Vong]

Hello,


A RC bug was reported by Lucas Nussbaum last week. I tried to reproduce it
in a QEMU VM with 64 cores but was unable to reproduce it precisely
(pthread_create() dies with EAGAIN instead of ENOMEM).

Recently, I find a similar bug[0], which will be fixed in the future by
splitting big test into smaller ones (the temporary fix is to disable
the test).

So I try to split a big test into 24 smaller ones and pthread_create()
doesn't die with EAGAIN anymore. However, I am not sure if the bug is
really fixed since I don't have a physical machine with 64 cores to test
on it.

The new version is now on mentors
,
what should I do now?


Thanks,
Alex


[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860664


signature.asc
Description: PGP signature

Bug#861063: marked as done (libxmlenc-java-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 09:33:52 +
with message-id 
and subject line Bug#861063: fixed in libxmlenc-java 0.52+dfsg-5
has caused the Debian Bug report #861063,
regarding libxmlenc-java-doc: unhandled symlink to directory conversion: 
/usr/share/doc/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.)


-- 
861063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxmlenc-java-doc
Version: 0.52+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  squeeze -> wheezy -> jessie -> stretch

(there was no libxmlenc-java-doc in wheezy and jessie, so the
squeeze version was kept installed)

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m26.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libxmlenc-java-doc/changelog.Debian.gz (libxmlenc-java-doc) != 
/usr/share/doc/libxmlenc-java/changelog.Debian.gz (libxmlenc-java)
/usr/share/doc/libxmlenc-java-doc -> libxmlenc-java
  /usr/share/doc/libxmlenc-java-doc/changelog.gz (libxmlenc-java-doc) != 
/usr/share/doc/libxmlenc-java/changelog.gz (libxmlenc-java)
/usr/share/doc/libxmlenc-java-doc -> libxmlenc-java
  /usr/share/doc/libxmlenc-java-doc/copyright (libxmlenc-java-doc) != 
/usr/share/doc/libxmlenc-java/copyright (libxmlenc-java)
/usr/share/doc/libxmlenc-java-doc -> libxmlenc-java


cheers,

Andreas


libxmlenc-java-doc_0.52+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libxmlenc-java
Source-Version: 0.52+dfsg-5

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated libxmlenc-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 24 Apr 2017 11:13:08 +0200
Source: libxmlenc-java
Binary: libxmlenc-java
Architecture: source
Version: 0.52+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libxmlenc-java - Fast stream-based XML output library for java
Closes: 861063
Changes:
 libxmlenc-java (0.52+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
   * Removed the libxmlenc-java-doc package (Closes: #861063)
   * Simplified debian/rules
   * Use a secure Vcs-Git URL
Checksums-Sha1:
 92681f374689baa6b743e5838561f60fa8ab8757 2066 

Bug#861063: Pending fixes for bugs in the libxmlenc-java package

[pkg-java-maintainers]

tag 861063 + pending
thanks

Some bugs in the libxmlenc-java package are closed in revision
3d1f49921d12de78db07bca47dc0ebcd63ed0a0c in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libxmlenc-java.git/commit/?id=3d1f499

Commit message:

Removed the libxmlenc-java-doc package (Closes: #861063)

Processed: Pending fixes for bugs in the libxmlenc-java package

[Debian Bug Tracking System]

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

> tag 861063 + pending
Bug #861063 [libxmlenc-java-doc] libxmlenc-java-doc: unhandled symlink to 
directory conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#803204: libiksemel: GNUTLS settings & ejabberd

[Mike Rhyner]

Hello guys

I'm using ejabberd XMPP server, and one fine day, debian has pushed a 
security update (package 2.1.10-4+deb7u2) that disables all old and 
insecure TLS/SSL protocols (TLS < 1.2, SSLv3). With that configuration, 
the patch from Duck was not enough to bring things back working again. 
So I investigated quite intensively and then finally got it to work by 
changing the priority string variable to that one:


SECURE256:-VERS-TLS-ALL:+VERS-TLS1.2:+SIGN-ALL

Explanation of the changes:
* removed "+SECURE192" as that isn't working at least with GnuTLS lib 
version (3.0.22) I've installed (tried with gnutls-cli, has thrown a 
"Syntax error" msg.). To be more precise, "+SECURE192" isn't valid with 
GnuTLS version shipped with Debian Wheezy, and it also seems that only 
one SECURE "preset" flag may be used (another one with +/- won't work).
* added "+SIGN-ALL" that enables every public key signatures (introduced 
with TLS 1.2, and is necessary when using that protocol against ejabberd 
at least)


Find my version of the patch attached...

Regards,
Mike Rhyner
Index: libiksemel-1.2/src/stream.c
===
--- src/stream.c
+++ src/stream.c
@@ -63,11 +63,7 @@ tls_pull (iksparser *prs, char *buffer,
 static int
 handshake (struct stream_data *data)
 {
-   const int protocol_priority[] = { GNUTLS_TLS1, GNUTLS_SSL3, 0 };
-   const int kx_priority[] = { GNUTLS_KX_RSA, 0 };
-   const int cipher_priority[] = { GNUTLS_CIPHER_3DES_CBC, GNUTLS_CIPHER_ARCFOUR, 0};
-   const int comp_priority[] = { GNUTLS_COMP_ZLIB, GNUTLS_COMP_NULL, 0 };
-   const int mac_priority[] = { GNUTLS_MAC_SHA, GNUTLS_MAC_MD5, 0 };
+   const char *priority_string = "SECURE256:-VERS-TLS-ALL:+VERS-TLS1.2:+SIGN-ALL";
int ret;

if (gnutls_global_init () != 0)
@@ -80,11 +76,7 @@ handshake (struct stream_data *data)
gnutls_certificate_free_credentials (data->cred);
return IKS_NOMEM;
}
-   gnutls_protocol_set_priority (data->sess, protocol_priority);
-   gnutls_cipher_set_priority(data->sess, cipher_priority);
-   gnutls_compression_set_priority(data->sess, comp_priority);
-   gnutls_kx_set_priority(data->sess, kx_priority);
-   gnutls_mac_set_priority(data->sess, mac_priority);
+   gnutls_priority_set_direct(data->sess, priority_string, NULL);
gnutls_credentials_set (data->sess, GNUTLS_CRD_CERTIFICATE, data->cred);

gnutls_transport_set_push_function (data->sess, (gnutls_push_func) tls_push);

Bug#861063: libxmlenc-java-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libxmlenc-java-doc
Version: 0.52+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  squeeze -> wheezy -> jessie -> stretch

(there was no libxmlenc-java-doc in wheezy and jessie, so the
squeeze version was kept installed)

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m26.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libxmlenc-java-doc/changelog.Debian.gz (libxmlenc-java-doc) != 
/usr/share/doc/libxmlenc-java/changelog.Debian.gz (libxmlenc-java)
/usr/share/doc/libxmlenc-java-doc -> libxmlenc-java
  /usr/share/doc/libxmlenc-java-doc/changelog.gz (libxmlenc-java-doc) != 
/usr/share/doc/libxmlenc-java/changelog.gz (libxmlenc-java)
/usr/share/doc/libxmlenc-java-doc -> libxmlenc-java
  /usr/share/doc/libxmlenc-java-doc/copyright (libxmlenc-java-doc) != 
/usr/share/doc/libxmlenc-java/copyright (libxmlenc-java)
/usr/share/doc/libxmlenc-java-doc -> libxmlenc-java


cheers,

Andreas


libxmlenc-java-doc_0.52+dfsg-4.log.gz
Description: application/gzip

Bug#860984: khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright

[Chris Lamb]

Hi Filip,

> Sorry I misunderstood what you meant, I would then add it as a comment
> like this:
[…]
>  License: Expat
> +Comment:
> +  Original license file in khal-doc is replaced by
> +  0002-Reference-license-from-copyright-file.patch to reference this 
> copyright
> +  file instead.

Yep; that way someone looking at debian/copyright (ie. someone who cares
about the copyright situation...) is aware of all the copyright-related
stuff in the package.

Previous to this, it was not obvious that the file under debian/patches
even existed!


Regards,

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

Bug#860984: khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright

[Filip Pytloun]

Sorry I misunderstood what you meant, I would then add it as a comment
like this:

Index: debian/copyright
===
--- debian/copyright(revision 13916)
+++ debian/copyright(working copy)
@@ -1,13 +1,18 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: khal
+Upstream-Contact: Christian Geier 
 Source: https://github.com/pimutils/khal

 Files: *
-Copyright: 2013-2016 Christian Geier et al.
+Copyright: 2013-2017 Christian Geier et al.
 License: Expat
+Comment:
+  Original license file in khal-doc is replaced by
+  0002-Reference-license-from-copyright-file.patch to reference this copyright
+  file instead.

 Files: debian/*
-Copyright: 2016 Filip Pytloun 
+Copyright: 2016-2017 Filip Pytloun 
 License: Expat

 License: Expat

On 2017/04/24 08:57, Chris Lamb wrote:
> Filip Pytloun wrote:
> 
> > thank you for letting me know. Patch only points to location where
> > debian/copyright is installed.
> > Is this change what you were thinking about?
> 
> No, sorry. What I am after is the *presence* of the
> 0002-Reference-license-from-copyright-file.patch to be at least
> *mentioned* in debian/copyright.
> 
> Not sure why you updated any of the below...
> 
>  
> > Index: debian/copyright
> > ===
> > --- debian/copyright(revision 13916)
> > +++ debian/copyright(working copy)
> > @@ -1,13 +1,14 @@
> >  Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> >  Upstream-Name: khal
> > +Upstream-Contact: Christian Geier 
> >  Source: https://github.com/pimutils/khal
> > 
> >  Files: *
> > -Copyright: 2013-2016 Christian Geier et al.
> > +Copyright: 2013-2017 Christian Geier et al.
> >  License: Expat
> > 
> >  Files: debian/*
> > -Copyright: 2016 Filip Pytloun 
> > +Copyright: 2016-2017 Filip Pytloun 
> >  License: Expat
> > 
> >  License: Expat
> > @@ -28,3 +29,6 @@
> >LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
> > FROM,
> >OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
> >THE SOFTWARE.
> > +  .
> > +  On Debian systems, text of this license can be found in
> > +  /usr/share/doc/khal/copyright
> > 
> > 
> > Thank you,
> > Filip
> > 
> > On 2017/04/23 09:05, Chris Lamb wrote:
> > > Source: khal
> > > Version: 0.9.5-1
> > > Severity: serious
> > > X-Debbugs-CC: Filip Pytloun 
> > > 
> > > Hi,
> > > 
> > > I just ACCEPTed khal from NEW but noticed it wasn't 100% obvious
> > > from debian/copyright that the 
> > > 0002-Reference-license-from-copyright-file.patch
> > > patch existed.
> > > 
> > > Please update your debian/copyright file, at least to point someone
> > > in the above file's direction. your next upload.
> 
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-


signature.asc
Description: PGP signature

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

[Lars Tangvald]

On 04/24/2017 10:27 AM, Salvatore Bonaccorso wrote:

Hi Lars,

On Mon, Apr 24, 2017 at 07:59:36AM +0200, Lars Tangvald wrote:


On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote:

Hi Lars,

On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:

Hi,

I lost internet connectivity where I am right now, so probably unable to get
this done until Monday. Could maybe use the previous debdiff for Jessie if
you're ok with closing the bug manually.
Also, I think we still don't have any active members in the maintainer team
with upload access for 5.5

Okay, I will look if I can take care of the upload for
jessie-security.

Regards,
Salvatore

Thanks! I was just about to push the update to git, but I see you already
did. Do you need anything more from us on this? Working with the LTS team
for wheezy-security.

No, it's fine at the moment. I'm still waiting for two builds. armhf
furthermore failed. Checking if that was temprary.

Was it a test failure?
There are some unstable tests I think we should identify (in unstable 
we've started disabling them and reporting upstream bug for each).


--
Lars

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 839358 1:2.8.9-150226-6
Bug #839358 [src:jd] jd: FTBFS: drawareabase.h:333:51: error: cannot convert 
'Glib::RefPtr' to 'const bool' in return
Marked as fixed in versions jd/1:2.8.9-150226-6.
> thanks
Stopping processing here.

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

Bug#860879: closed by Holger Levsen <hol...@debian.org> (Bug#860879: fixed in munin 2.999.6-2)

[Frederik Himpe]

Ouch, apparently I made a typo in the title of my bug report: the
package name is libio-string-perl, not libo-string-perl

This leads to this error when upgrading:

 munin : Depends: libo-string-perl but it is not installable

My apologies for the confusion...

-- 
Frederik Himpe 
Vrije Universiteit Brussel

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Mon, Apr 24, 2017 at 07:59:36AM +0200, Lars Tangvald wrote:
> 
> 
> On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote:
> >Hi Lars,
> >
> >On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:
> >>Hi,
> >>
> >>I lost internet connectivity where I am right now, so probably unable to get
> >>this done until Monday. Could maybe use the previous debdiff for Jessie if
> >>you're ok with closing the bug manually.
> >>Also, I think we still don't have any active members in the maintainer team
> >>with upload access for 5.5
> >Okay, I will look if I can take care of the upload for
> >jessie-security.
> >
> >Regards,
> >Salvatore
> 
> Thanks! I was just about to push the update to git, but I see you already
> did. Do you need anything more from us on this? Working with the LTS team
> for wheezy-security.

No, it's fine at the moment. I'm still waiting for two builds. armhf
furthermore failed. Checking if that was temprary.

Regards,
Salvatore

Bug#860225: assertion failure

[Jan Korbel]

Hello.

Our bind9 in jessie exited due to assertion failure today. On bind-user
i found it was because CVE-2017-3137. Please apply upstream patches. Thx.

links:

https://www.mail-archive.com/bind-users@lists.isc.org/msg24356.html
https://security-tracker.debian.org/tracker/CVE-2017-3137

logs:

Apr 24 08:41:31 server named[20579]: resolver.c:4350: INSIST(fctx->type == 
((dns_rdatatype_t)dns_rdatatype_any) ||
  fctx->type == ((dns_rdatatype_t)dns_rdatatype_rrsig) || fctx->type == 
((dns_rdatatype_t)dns_rdatatype_sig)) failed, back trace
Apr 24 08:41:31 server named[20579]: #0 0xb7789ec3 in ??
Apr 24 08:41:31 server named[20579]: #1 0xb71207e5 in ??
Apr 24 08:41:31 server named[20579]: #2 0xb75e47be in ??
Apr 24 08:41:31 server named[20579]: #3 0xb7143a7c in ??
Apr 24 08:41:31 server named[20579]: #4 0xb70f3ee2 in ??
Apr 24 08:41:31 server named[20579]: #5 0xb6ea9afe in ??
Apr 24 08:41:31 server named[20579]: exiting (due to assertion failure)

Regards,

jc

Bug#860984: khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright

[Chris Lamb]

Filip Pytloun wrote:

> thank you for letting me know. Patch only points to location where
> debian/copyright is installed.
> Is this change what you were thinking about?

No, sorry. What I am after is the *presence* of the
0002-Reference-license-from-copyright-file.patch to be at least
*mentioned* in debian/copyright.

Not sure why you updated any of the below...

 
> Index: debian/copyright
> ===
> --- debian/copyright(revision 13916)
> +++ debian/copyright(working copy)
> @@ -1,13 +1,14 @@
>  Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>  Upstream-Name: khal
> +Upstream-Contact: Christian Geier 
>  Source: https://github.com/pimutils/khal
> 
>  Files: *
> -Copyright: 2013-2016 Christian Geier et al.
> +Copyright: 2013-2017 Christian Geier et al.
>  License: Expat
> 
>  Files: debian/*
> -Copyright: 2016 Filip Pytloun 
> +Copyright: 2016-2017 Filip Pytloun 
>  License: Expat
> 
>  License: Expat
> @@ -28,3 +29,6 @@
>LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
> FROM,
>OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
>THE SOFTWARE.
> +  .
> +  On Debian systems, text of this license can be found in
> +  /usr/share/doc/khal/copyright
> 
> 
> Thank you,
> Filip
> 
> On 2017/04/23 09:05, Chris Lamb wrote:
> > Source: khal
> > Version: 0.9.5-1
> > Severity: serious
> > X-Debbugs-CC: Filip Pytloun 
> > 
> > Hi,
> > 
> > I just ACCEPTed khal from NEW but noticed it wasn't 100% obvious
> > from debian/copyright that the 
> > 0002-Reference-license-from-copyright-file.patch
> > patch existed.
> > 
> > Please update your debian/copyright file, at least to point someone
> > in the above file's direction. your next upload.


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

Bug#860984: khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright

[Filip Pytloun]

Hello,

thank you for letting me know. Patch only points to location where
debian/copyright is installed.
Is this change what you were thinking about?

Index: debian/copyright
===
--- debian/copyright(revision 13916)
+++ debian/copyright(working copy)
@@ -1,13 +1,14 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: khal
+Upstream-Contact: Christian Geier 
 Source: https://github.com/pimutils/khal

 Files: *
-Copyright: 2013-2016 Christian Geier et al.
+Copyright: 2013-2017 Christian Geier et al.
 License: Expat

 Files: debian/*
-Copyright: 2016 Filip Pytloun 
+Copyright: 2016-2017 Filip Pytloun 
 License: Expat

 License: Expat
@@ -28,3 +29,6 @@
   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
   THE SOFTWARE.
+  .
+  On Debian systems, text of this license can be found in
+  /usr/share/doc/khal/copyright


Thank you,
Filip

On 2017/04/23 09:05, Chris Lamb wrote:
> Source: khal
> Version: 0.9.5-1
> Severity: serious
> X-Debbugs-CC: Filip Pytloun 
> 
> Hi,
> 
> I just ACCEPTed khal from NEW but noticed it wasn't 100% obvious
> from debian/copyright that the 
> 0002-Reference-license-from-copyright-file.patch
> patch existed.
> 
> Please update your debian/copyright file, at least to point someone
> in the above file's direction. your next upload.
> 
> 
> Best wishes,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-


signature.asc
Description: PGP signature

Bug#860603: marked as done (debian-design: FTBFS: unsatisfiable build-dependency: boxer-data (>= 10.5.18) but 10.5.15 is to be installed)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 10:12:46 +0300
with message-id <20170424071246.2npt5pulq776o32l@localhost>
and subject line boxer-data 10.5.20 migrated to stretch
has caused the Debian Bug report #860603,
regarding debian-design: FTBFS: unsatisfiable build-dependency: boxer-data (>= 
10.5.18) but 10.5.15 is to be installed
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.)


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

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, licensecheck, debhelper, dh-buildinfo, boxer (>= 
> 0.004~), dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), 
> boxer-data (<< 10.6)
> Filtered Build-Depends: cdbs, licensecheck, debhelper, dh-buildinfo, boxer 
> (>= 0.004~), dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), 
> boxer-data (<< 10.6)
> dpkg-deb: building package 'sbuild-build-depends-debian-design-dummy' in 
> '/<>/resolver-T8fHSe/apt_archive/sbuild-build-depends-debian-design-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-debian-design-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-T8fHSe/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-T8fHSe/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-T8fHSe/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-T8fHSe/apt_archive ./ Sources [556 B]
> Get:5 copy:/<>/resolver-T8fHSe/apt_archive ./ Packages [643 B]
> Fetched 2162 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install debian-design build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-debian-design-dummy : Depends: boxer-data (>= 10.5.18) 
> but 10.5.15 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/debian-design_3.0.6_testing.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 ---
boxer-data 10.5.20 migrated to stretch.

cu
Adrian

-- 

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

Bug#860612: marked as done (debian-parl: FTBFS: unsatisfiable build-dependency: boxer-data (>= 10.5.18) but 10.5.15 is to be installed)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2017 10:12:46 +0300
with message-id <20170424071246.2npt5pulq776o32l@localhost>
and subject line boxer-data 10.5.20 migrated to stretch
has caused the Debian Bug report #860612,
regarding debian-parl: FTBFS: unsatisfiable build-dependency: boxer-data (>= 
10.5.18) but 10.5.15 is to be installed
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.)


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

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper, dh-buildinfo, boxer (>= 0.004~), 
> dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), boxer-data (<< 
> 10.6)
> Filtered Build-Depends: cdbs, debhelper, dh-buildinfo, boxer (>= 0.004~), 
> dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), boxer-data (<< 
> 10.6)
> dpkg-deb: building package 'sbuild-build-depends-debian-parl-dummy' in 
> '/<>/resolver-MTSFkl/apt_archive/sbuild-build-depends-debian-parl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-debian-parl-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MTSFkl/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MTSFkl/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-MTSFkl/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MTSFkl/apt_archive ./ Sources [548 B]
> Get:5 copy:/<>/resolver-MTSFkl/apt_archive ./ Packages [632 B]
> Fetched 2143 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install debian-parl build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-debian-parl-dummy : Depends: boxer-data (>= 10.5.18) 
> but 10.5.15 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/debian-parl_1.9.10_testing.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 ---
boxer-data 10.5.20 migrated to stretch.

cu
Adrian

-- 

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

Bug#859660: Bug#859660: artemis running issue

[Andreas Tille]

Hi Java developers,

is there any known issue with running JARs via symlink to /usr/bin?

I suspect this is the problem with this bug but I wonder what might be
the recommended way from Java team about this way to start Java programs
that used to work but is not always relieable.

Kind regards

  Andreas.

On Fri, Apr 07, 2017 at 12:43:42PM +0200, Andreas Tille wrote:
> Hi,
> 
> On Fri, Apr 07, 2017 at 12:17:08PM +0200, Sascha Steinbiss wrote:
> > Hi,
> > 
> > > على الأربعاء  5 نيسـان 2017 ‫12:32، كتب Jerome:
> > >> When running artemis package, get this issue :
> > >>
> > >> $ art
> > >> bash: /usr/bin/art: cannot execute binary file: Exec format error
> > 
> > Probably something to do with jarwrapper? I remember running into
> > something similar quite some time ago.
> 
> I'd assume the same.  I can confirm that I can not reproduce here as
> well but the problem sounds like jarwrapper connected.  I do not
> remember what package I had in the past with a similar issue but
> providing a shell wrapper calling java with some options and the jar
> file solved the issue.
> 
> It seems that jarwrapper is not really reliable - as far as I know
> specifically if users are using a self compiled kernel where this
> feature can be switched of.
> 
> Hope this helps
> 
>  Andreas.

-- 
http://fam-tille.de

Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU

[Lars Tangvald]

On 04/21/2017 08:04 AM, Salvatore Bonaccorso wrote:

Hi Lars,

On Fri, Apr 21, 2017 at 06:07:40AM +0200, Lars Tangvald wrote:

Hi,

I lost internet connectivity where I am right now, so probably unable to get
this done until Monday. Could maybe use the previous debdiff for Jessie if
you're ok with closing the bug manually.
Also, I think we still don't have any active members in the maintainer team
with upload access for 5.5

Okay, I will look if I can take care of the upload for
jessie-security.

Regards,
Salvatore


Thanks! I was just about to push the update to git, but I see you 
already did. Do you need anything more from us on this? Working with the 
LTS team for wheezy-security.


--
Lars