Bug#861480: marked as done (ImportError: No module named QtWebKit)

[Debian Bug Tracking System]

Your message dated Wed, 17 May 2017 05:53:20 +
with message-id 
and subject line Bug#862665: Removed package(s) from unstable
has caused the Debian Bug report #861480,
regarding ImportError: No module named QtWebKit
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.)


-- 
861480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: series60-remote
Version: 0.4.80+dfsg.1-2
Severity: critical



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

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

Versions of packages series60-remote depends on:
ii  libqt4-sql-mysql   4:4.8.7+dfsg-11
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-11
ii  python 2.7.13-2
ii  python-bluez   0.22-1
ii  python-qt4 4.11.4+dfsg-2+b1
ii  python-qt4-sql 4.11.4+dfsg-2+b1

Versions of packages series60-remote recommends:
ii  python-matplotlib  2.0.0+dfsg1-2
ii  python-obexftp 0.24-5+b1

series60-remote suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.4.80+dfsg.1-2+rm

Dear submitter,

as the package series60-remote has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/862665

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#829497: marked as done (ruby-bdb: unmaintained)

[Debian Bug Tracking System]

Your message dated Wed, 17 May 2017 05:50:31 +
with message-id 
and subject line Bug#862537: Removed package(s) from unstable
has caused the Debian Bug report #829497,
regarding ruby-bdb: unmaintained
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.)


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

ruby-bdb has a dead upstream and we do not really want it to be in
stretch.

Filing this bug to cause a testing removal, and follow up with an RM
bug in a while.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Version: 0.6.6-2+rm

Dear submitter,

as the package ruby-bdb has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/862537

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#822506: marked as done (ruby-bluecloth: FTBFS: `split': invalid byte sequence in US-ASCII (ArgumentError))

[Debian Bug Tracking System]

Your message dated Wed, 17 May 2017 05:51:11 +
with message-id 
and subject line Bug#862539: Removed package(s) from unstable
has caused the Debian Bug report #822506,
regarding ruby-bluecloth: FTBFS: `split': invalid byte sequence in US-ASCII 
(ArgumentError)
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.)


-- 
822506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-bluecloth
Version: 2.2.0-6
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> /usr/lib/ruby/vendor_ruby/rspec/core/source.rb:23:in `split': invalid byte 
> sequence in US-ASCII (ArgumentError)
>   from /usr/lib/ruby/vendor_ruby/rspec/core/source.rb:23:in `lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/snippet_extractor.rb:50:in 
> `expression_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/snippet_extractor.rb:33:in 
> `extract_expression_lines_at'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:209:in 
> `read_failed_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:160:in 
> `failure_slash_error_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:147:in 
> `block in failure_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:146:in 
> `tap'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:146:in 
> `failure_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:32:in 
> `colorized_message_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:231:in 
> `formatted_message_and_backtrace'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:84:in 
> `fully_formatted_lines'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:76:in 
> `fully_formatted'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:200:in 
> `fully_formatted'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:114:in 
> `block in fully_formatted_failed_examples'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:113:in `each'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:113:in 
> `each_with_index'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:113:in 
> `fully_formatted_failed_examples'
>   from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/base_text_formatter.rb:33:in 
> `dump_failures'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:189:in `block in 
> notify'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:188:in `each'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:188:in `notify'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:160:in `block in 
> finish'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:175:in 
> `close_after'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:156:in `finish'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:79:in `report'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:117:in `run_specs'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:93:in `run'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:78:in `run'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:38:in 
> `perform_at_exit'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:24:in `block in 
> autorun'
> ERROR: Test "ruby2.3" failed. Exiting.
> dh_auto_install: dh_ruby --install /<>/debian/ruby-bluecloth 
> returned exit code 1
> debian/rules:18: recipe for target 'binary' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 2.2.0-6+rm

Dear submitter,

as the package ruby-bluecloth has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/862539

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe 

Bug#823178: marked as done (ruby-bluecloth: obsolete)

[Debian Bug Tracking System]

Your message dated Wed, 17 May 2017 05:51:11 +
with message-id 
and subject line Bug#862539: Removed package(s) from unstable
has caused the Debian Bug report #823178,
regarding ruby-bluecloth: obsolete
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.)


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

Bluecloth is no longer developed or maintained upstream. While we
may keep this package around for a bit longer, dependencies on it
need to be removed over time.

New packages certainly must not depend on ruby-bluecloth.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Version: 2.2.0-6+rm

Dear submitter,

as the package ruby-bluecloth has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/862539

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#860979: in package dpkg marked as pending

[Guillem Jover]

Control: tag 860979 pending

Hi!

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

https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=31f9819

---
commit 31f98198278ae0a70b5594680e05454a383ac175
Author: Guillem Jover 
Date:   Sun Apr 23 04:51:58 2017 +0200

dpkg-shlibdeps: Preserve the order when scanning symbols/shlibs files

The code was getting all the possible shared library pathnames for the
wanted SONAME, but was not preserving the order carefully constructed
in find_library(), so we were overwriting symbols/shlibs information
when parsing multiple entries, and selecting the symbols/shlibs files
randomly based on the perl hash order.

This causes regressions when multiple packages provide the same
SONAME on different directories. An example would be libc6:amd64
and libc6-amd64:i386.

Fixes: commit a927295c93fb7a17742441aa863aaffcf4a351b5
Closes: #860979
Reported-by: Helmut Grohne 

diff --git a/debian/changelog b/debian/changelog
index cf9b5cc..92b2b27 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,10 @@ dpkg (1.18.24) UNRELEASED; urgency=medium
 
   [ Guillem Jover ]
   * Add missing symbols to the libdpkg map file.
+  * Fix dpkg-shlibdeps to preserve the Dpkg::Shlibs::find_library() order
+when scanning symbols/shlibs files. This was causing generation of bogus
+dependencies when multiple packages provide the same SONAME on different
+directories. Regression introduced in dpkg 1.18.17. Closes: #860979
   * Architecture support:
 - Add support for ARM64 ILP32. Closes: #824742
   Thanks to Wookey .

Processed: Bug#860979 in package dpkg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 860979 pending
Bug #860979 [dpkg-dev] dpkg-dev: dpkg-shlibdeps regression due to the 
/usr-merge changes
Added tag(s) pending.

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

Processed: unblock 847493 with 744741

[Debian Bug Tracking System]

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

> unblock 847493 with 744741
Bug #847493 [yubikey-piv-manager] pkg_resources.DistributionNotFound: The 
'PySide' distribution was not found and is required by yubikey-piv-manager
847493 was blocked by: 744741
847493 was not blocking any bugs.
Removed blocking bug(s) of 847493: 744741
> thanks
Stopping processing here.

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

Bug#862787: debconf: Passwords do not match.

[Christian PERRIER]

reassign 862787 ddclient
severity 862787 normal
thanks

Quoting luciano (fran...@modula.net):
> Package: debconf
> Version: 1.5.56
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> During the installation of ddclient, Debconf display the error "Passwords do 
> not match. The two passwords you entered where not the same. Please try 
> again". If I try again then the password is accepted. Always the same 
> message, after more than 10 install/uninstall attemps using two different 
> computers.


If this happens during the installation of ddclient, then this bug
belongs to that package, not debconf. And is indeed of normal severity
(or "important" but certainly not grave).




signature.asc
Description: PGP signature

Processed: Re: Bug#862787: debconf: Passwords do not match.

[Debian Bug Tracking System]

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

> reassign 862787 ddclient
Bug #862787 [debconf] debconf: Passwords do not match.
Bug reassigned from package 'debconf' to 'ddclient'.
No longer marked as found in versions debconf/1.5.56.
Ignoring request to alter fixed versions of bug #862787 to the same values 
previously set
> severity 862787 normal
Bug #862787 [ddclient] debconf: Passwords do not match.
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: yubikey-piv-manager: diff for NMU version 1.3.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 847493 + patch
Bug #847493 [yubikey-piv-manager] pkg_resources.DistributionNotFound: The 
'PySide' distribution was not found and is required by yubikey-piv-manager
Added tag(s) patch.
> tags 847493 + pending
Bug #847493 [yubikey-piv-manager] pkg_resources.DistributionNotFound: The 
'PySide' distribution was not found and is required by yubikey-piv-manager
Added tag(s) pending.

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

Bug#847493: yubikey-piv-manager: diff for NMU version 1.3.0-1.1

[Luke W Faraone]

Control: tags 847493 + patch
Control: tags 847493 + pending

Dear maintainer,

I've prepared an NMU for yubikey-piv-manager (versioned as 1.3.0-1.1)
and uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru yubikey-piv-manager-1.3.0/debian/changelog 
yubikey-piv-manager-1.3.0/debian/changelog
--- yubikey-piv-manager-1.3.0/debian/changelog  2016-08-23 00:37:18.0 
-0700
+++ yubikey-piv-manager-1.3.0/debian/changelog  2017-05-16 19:08:22.0 
-0700
@@ -1,3 +1,11 @@
+yubikey-piv-manager (1.3.0-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Re-add PySide patch.
+  * Remove requires.txt requiring PySide (Closes: #847493)
+
+ -- Luke W Faraone   Wed, 17 May 2017 02:08:22 +
+
 yubikey-piv-manager (1.3.0-1) unstable; urgency=low
 
   [ Simon Josefsson ]
diff -Nru yubikey-piv-manager-1.3.0/debian/patches/fix-pyside.diff 
yubikey-piv-manager-1.3.0/debian/patches/fix-pyside.diff
--- yubikey-piv-manager-1.3.0/debian/patches/fix-pyside.diff1969-12-31 
16:00:00.0 -0800
+++ yubikey-piv-manager-1.3.0/debian/patches/fix-pyside.diff2017-05-16 
18:43:02.0 -0700
@@ -0,0 +1,13 @@
+--- a/setup.py
 b/setup.py
+@@ -42,8 +42,8 @@
+ entry_points={
+ 'gui_scripts': ['pivman=pivman.__main__:main']
+ },
+-install_requires=['PySide'],
+-yc_requires=['ctypes', 'qt'],
++yc_requires=['ctypes'],
++packages=['pivman', 'pivman.view', 'pivman.yubicommon', 
'pivman.yubicommon.setup', 'pivman.yubicommon.ctypes', 'pivman.yubicommon.qt'],
+ test_suite='test',
+ tests_require=[''],
+ cmdclass={'executable': executable, 'qt_resources': 
qt_resources('pivman')},
diff -Nru yubikey-piv-manager-1.3.0/debian/patches/series 
yubikey-piv-manager-1.3.0/debian/patches/series
--- yubikey-piv-manager-1.3.0/debian/patches/series 1969-12-31 
16:00:00.0 -0800
+++ yubikey-piv-manager-1.3.0/debian/patches/series 2017-05-16 
18:43:02.0 -0700
@@ -0,0 +1 @@
+fix-pyside.diff
diff -Nru yubikey-piv-manager-1.3.0/debian/rules 
yubikey-piv-manager-1.3.0/debian/rules
--- yubikey-piv-manager-1.3.0/debian/rules  2016-08-23 00:36:56.0 
-0700
+++ yubikey-piv-manager-1.3.0/debian/rules  2017-05-16 19:08:22.0 
-0700
@@ -2,3 +2,7 @@
 
 %:
dh $@ --with python2 --buildsystem=python_distutils
+
+override_dh_auto_clean:
+   dh_clean
+   rm -f yubikey_piv_manager.egg-info/requires.txt


signature.asc
Description: OpenPGP digital signature

Bug#862508: marked as done (openjdk-8-jre: libatk-wrapper-java-jni dependency should be raised to (>= 0.33.3-9~))

[Debian Bug Tracking System]

Your message dated Tue, 16 May 2017 22:19:20 +
with message-id 
and subject line Bug#862508: fixed in openjdk-8 8u131-b11-2
has caused the Debian Bug report #862508,
regarding openjdk-8-jre: libatk-wrapper-java-jni dependency should be raised to 
(>= 0.33.3-9~)
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.)


-- 
862508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-8-jre
Version: 8u131-b11-1
Severity: serious

Due to #824226 (observed by several people) openjdk-8-jre should
raise the libatk-wrapper-java-jni dependency to (>= 0.33.3-9~).
--- End Message ---
--- Begin Message ---
Source: openjdk-8
Source-Version: 8u131-b11-2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 May 2017 14:38:22 -0700
Source: openjdk-8
Binary: openjdk-8-jdk-headless openjdk-8-jre-headless openjdk-8-jdk 
openjdk-8-jre openjdk-8-demo openjdk-8-source openjdk-8-doc openjdk-8-dbg 
openjdk-8-jre-zero
Architecture: source
Version: 8u131-b11-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-8-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-8-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-8-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-8-jdk - OpenJDK Development Kit (JDK)
 openjdk-8-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-8-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-8-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-8-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-8-source - OpenJDK Development Kit (JDK) source files
Closes: 862508
Changes:
 openjdk-8 (8u131-b11-2) unstable; urgency=medium
 .
   * Tighten dependency on libatk-wrapper-java-jni. Closes: #862508.
Checksums-Sha1:
 362f402e1b42795904e52aff81e44b5aa97e2761 4483 openjdk-8_8u131-b11-2.dsc
 bb7662daf5636e9b30b28210a87fd72d272486a1 242212 
openjdk-8_8u131-b11-2.debian.tar.xz
 574a686e71324cdb8eb8becacf3b98e68fcecb50 16027 
openjdk-8_8u131-b11-2_source.buildinfo
Checksums-Sha256:
 be3295cde619d6a15bb42fe4e5e409169e477a79c63a9933a43433a08640a4af 4483 
openjdk-8_8u131-b11-2.dsc
 0f28306314a55384b68b5513e20c33ebb18d7e14e8c94693bd4568f49d0eb5bc 242212 
openjdk-8_8u131-b11-2.debian.tar.xz
 2dbd135d4f810267241a7309c4c7125e50876b907dd0dc26e332a7a3e37792e4 16027 
openjdk-8_8u131-b11-2_source.buildinfo
Files:
 6db8abf68347dd293d8ad503768f54f9 4483 java optional openjdk-8_8u131-b11-2.dsc
 c84cece4ff9b47c562e29065a6dd0e11 242212 java optional 
openjdk-8_8u131-b11-2.debian.tar.xz
 cedc2972b5b5bcac52c96a2c61f16b2a 16027 java optional 
openjdk-8_8u131-b11-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlkbdcIQHGRva29AdWJ1
bnR1LmNvbQAKCRC9fqpgd4+m9XRhD/97Q6DSQdT2GBx4KVcHunwl7eseTXmUWyhr
IXuaGA7xlHfiTMtBSz54zPvsjNTWeTc2w4C1jBHpbtrdxt/0u2oG4OGWyKsXWOBJ
Ntk3fe+8fzOF2R4h4mMvQr3hVj9wbt3fUKl8BzWj+O4nKbpmmb9P2kF+3rJnZM3C
4KXkZyxhWdXTVqhBMgCuivbP/QzRFMdU2VnykcYANnhn+0++JXEeWZBpsh4NYMmD
6yb+zOgcRA3ivDvnqr0lCz2cWtNcroQ7RxCTvxaYmj2gDzZAlvIevq52qJJmeJFL
m6hG3B9MGCrIyGHrFDvhzeMadTpcYAnPoRMp5rL9uuAy5Bdjk11cDnm823HrMlro
q0zsTBFQimvXTiiFkAgz/mAobBiX5RcQLBvBW0zRjm2796KPnMFADhmWxvCHbKJ6
iLZCdd1JP3O/geiQCPk49+BchSjeBmMeKzrfRSlGxfRYB3ja7Y7TvDp6k6sZdFsJ
eS/EWWLUBPHZWzNJnG8RAYwoKO+7QMCJMvCf0IeIyBfB2n3iBoK8f8U9qeIWVDPo
tGD4f2zJErRBY7k7O49xNozGRX6ByhG7NWs7XRsgt9tq39wMnIo/VZzuDcMqRBcI
HPufNJXBIMOiox1eY1h/rr+l/nGQSPi4xRxqS9s+z+2YO0+BJdkoCTydpqbFgnmL
+E14msj7lw==
=T60d
-END PGP SIGNATURE End Message ---

Bug#861994: [PATCH 1/2] Add a dependency on python-pycurl, needed by lwr (closes: #861994)

[Florian Schlichting]

---
 debian/changelog | 7 +++
 setup.py | 1 +
 2 files changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 6c30e45..80292bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+live-wrapper (0.6+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add a dependency on python-pycurl, needed by lwr (closes: #861994)
+
+ -- Florian Schlichting   Tue, 16 May 2017 23:06:46 +0200
+
 live-wrapper (0.6) unstable; urgency=medium
 
   [ Ana C. Custura ]
diff --git a/setup.py b/setup.py
index 761f609..e573266 100644
--- a/setup.py
+++ b/setup.py
@@ -41,6 +41,7 @@ setup(
 'cliapp >= 1.20150829',
 'vmdebootstrap',
 'requests',
+'pycurl',
 'python-apt'
 ],
 entry_points={
-- 
2.11.0

Bug#861994: [PATCH 2/2] add Build-Dep's needed for building the lwr autodoc

[Florian Schlichting]

---
 debian/changelog | 6 --
 debian/control   | 5 -
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 80292bd..a21b45a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,11 @@
-live-wrapper (0.6+nmu1) UNRELEASED; urgency=medium
+live-wrapper (0.6+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
   * Add a dependency on python-pycurl, needed by lwr (closes: #861994)
+  * Add Build-Depends: python-apt, python-cliapp, vmdebootstrap needed to
+completely build the lwr autodoc
 
- -- Florian Schlichting   Tue, 16 May 2017 23:06:46 +0200
+ -- Florian Schlichting   Tue, 16 May 2017 23:31:36 +0200
 
 live-wrapper (0.6) unstable; urgency=medium
 
diff --git a/debian/control b/debian/control
index a77c9bc..32297c3 100644
--- a/debian/control
+++ b/debian/control
@@ -6,8 +6,11 @@ Priority: optional
 Build-Depends: debhelper (>= 9),
dh-python,
python-all,
+   python-apt,
+   python-cliapp,
python-setuptools,
-   python-sphinx
+   python-sphinx,
+   vmdebootstrap
 Standards-Version: 3.9.8
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-live/live-wrapper.git
 Vcs-Git: https://anonscm.debian.org/git/debian-live/live-wrapper.git
-- 
2.11.0

Processed: live-wrapper: diff for NMU version 0.6+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 861994 + patch
Bug #861994 [live-wrapper] live-wrapper: Lacks dependency on python-pycurl
Added tag(s) patch.
> tags 861994 + pending
Bug #861994 [live-wrapper] live-wrapper: Lacks dependency on python-pycurl
Added tag(s) pending.

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

Bug#861994: live-wrapper: diff for NMU version 0.6+nmu1

[Florian Schlichting]

Control: tags 861994 + patch
Control: tags 861994 + pending

Dear maintainer,

I've prepared an NMU for live-wrapper (versioned as 0.6+nmu1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru live-wrapper-0.6/debian/changelog live-wrapper-0.6+nmu1/debian/changelog
--- live-wrapper-0.6/debian/changelog	2017-01-23 03:39:31.0 +0100
+++ live-wrapper-0.6+nmu1/debian/changelog	2017-05-16 23:31:36.0 +0200
@@ -1,3 +1,12 @@
+live-wrapper (0.6+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add a dependency on python-pycurl, needed by lwr (closes: #861994)
+  * Add Build-Depends: python-apt, python-cliapp, vmdebootstrap needed to
+completely build the lwr autodoc
+
+ -- Florian Schlichting   Tue, 16 May 2017 23:31:36 +0200
+
 live-wrapper (0.6) unstable; urgency=medium
 
   [ Ana C. Custura ]
diff -Nru live-wrapper-0.6/debian/control live-wrapper-0.6+nmu1/debian/control
--- live-wrapper-0.6/debian/control	2017-01-22 23:30:58.0 +0100
+++ live-wrapper-0.6+nmu1/debian/control	2017-05-16 23:31:36.0 +0200
@@ -6,8 +6,11 @@
 Build-Depends: debhelper (>= 9),
dh-python,
python-all,
+   python-apt,
+   python-cliapp,
python-setuptools,
-   python-sphinx
+   python-sphinx,
+   vmdebootstrap
 Standards-Version: 3.9.8
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-live/live-wrapper.git
 Vcs-Git: https://anonscm.debian.org/git/debian-live/live-wrapper.git
diff -Nru live-wrapper-0.6/live_wrapper.egg-info/dependency_links.txt live-wrapper-0.6+nmu1/live_wrapper.egg-info/dependency_links.txt
--- live-wrapper-0.6/live_wrapper.egg-info/dependency_links.txt	2017-01-23 01:56:29.0 +0100
+++ live-wrapper-0.6+nmu1/live_wrapper.egg-info/dependency_links.txt	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-
diff -Nru live-wrapper-0.6/live_wrapper.egg-info/entry_points.txt live-wrapper-0.6+nmu1/live_wrapper.egg-info/entry_points.txt
--- live-wrapper-0.6/live_wrapper.egg-info/entry_points.txt	2017-01-23 01:56:29.0 +0100
+++ live-wrapper-0.6+nmu1/live_wrapper.egg-info/entry_points.txt	1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-[console_scripts]
-lwr = lwr.run:main
-
diff -Nru live-wrapper-0.6/live_wrapper.egg-info/PKG-INFO live-wrapper-0.6+nmu1/live_wrapper.egg-info/PKG-INFO
--- live-wrapper-0.6/live_wrapper.egg-info/PKG-INFO	2017-01-23 01:56:29.0 +0100
+++ live-wrapper-0.6+nmu1/live_wrapper.egg-info/PKG-INFO	1970-01-01 01:00:00.0 +0100
@@ -1,18 +0,0 @@
-Metadata-Version: 1.1
-Name: live-wrapper
-Version: 0.6
-Summary: Create a Debian live image based on vmdebootstrap
-Home-page: https://anonscm.debian.org/cgit/debian-live/live-wrapper.git
-Author: Iain R. Learmonth
-Author-email: i...@debian.org
-License: UNKNOWN
-Description: UNKNOWN
-Platform: UNKNOWN
-Classifier: Development Status :: 3 - Alpha
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: Intended Audience :: System Administrators
-Classifier: License :: OSI Approved :: BSD License
-Classifier: Programming Language :: Python
-Classifier: Programming Language :: Python :: 2.7
-Classifier: Topic :: System :: Installation/Setup
diff -Nru live-wrapper-0.6/live_wrapper.egg-info/requires.txt live-wrapper-0.6+nmu1/live_wrapper.egg-info/requires.txt
--- live-wrapper-0.6/live_wrapper.egg-info/requires.txt	2017-01-23 01:56:29.0 +0100
+++ live-wrapper-0.6+nmu1/live_wrapper.egg-info/requires.txt	1970-01-01 01:00:00.0 +0100
@@ -1,4 +0,0 @@
-cliapp >= 1.20150829
-vmdebootstrap
-requests
-python-apt
diff -Nru live-wrapper-0.6/live_wrapper.egg-info/SOURCES.txt live-wrapper-0.6+nmu1/live_wrapper.egg-info/SOURCES.txt
--- live-wrapper-0.6/live_wrapper.egg-info/SOURCES.txt	2017-01-23 01:56:29.0 +0100
+++ live-wrapper-0.6+nmu1/live_wrapper.egg-info/SOURCES.txt	1970-01-01 01:00:00.0 +0100
@@ -1,19 +0,0 @@
-README
-setup.py
-live_wrapper.egg-info/PKG-INFO
-live_wrapper.egg-info/SOURCES.txt
-live_wrapper.egg-info/dependency_links.txt
-live_wrapper.egg-info/entry_points.txt
-live_wrapper.egg-info/requires.txt
-live_wrapper.egg-info/top_level.txt
-lwr/__init__.py
-lwr/apt_udeb.py
-lwr/bootloader.py
-lwr/cdroot.py
-lwr/disk.py
-lwr/grub.py
-lwr/isolinux.py
-lwr/run.py
-lwr/utils.py
-lwr/vm.py
-lwr/xorriso.py
\ No newline at end of file
diff -Nru live-wrapper-0.6/live_wrapper.egg-info/top_level.txt live-wrapper-0.6+nmu1/live_wrapper.egg-info/top_level.txt
--- live-wrapper-0.6/live_wrapper.egg-info/top_level.txt	2017-01-23 01:56:29.0 +0100
+++ live-wrapper-0.6+nmu1/live_wrapper.egg-info/top_level.txt	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-lwr
diff -Nru live-wrapper-0.6/setup.py live-wrapper-0.6+nmu1/setup.py
--- live-wrapper-0.6/setup.py	2017-01-08 00:44:10.0 +0100
+++ live-wrapper-0.6+nmu1/setup.py	2017-05-16 23:31:36.0 

Bug#862787: debconf: Passwords do not match.

[luciano]

Package: debconf
Version: 1.5.56
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
During the installation of ddclient, Debconf display the error "Passwords do 
not match. The two passwords you entered where not the same. Please try again". 
If I try again then the password is accepted. Always the same message, after 
more than 10 install/uninstall attemps using two different computers.

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


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

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

Versions of packages debconf depends on:
ii  perl-base  5.20.2-3+deb8u6

Versions of packages debconf recommends:
ii  apt-utils 1.0.9.8.4
ii  debconf-i18n  1.5.56

Versions of packages debconf suggests:
pn  debconf-doc
pn  debconf-utils  
ii  libgtk2-perl   2:1.2492-4
pn  libnet-ldap-perl   
ii  libqtcore4-perl4.8.4-1.2
ii  libqtgui4-perl 4.8.4-1.2
pn  libterm-readline-gnu-perl  
ii  perl   5.20.2-3+deb8u6
ii  whiptail   0.52.17-1+b1

-- debconf information:
  debconf-apt-progress/preparing:
  debconf-apt-progress/info:
  debconf-apt-progress/media-change:
  debconf/frontend: Dialog
  debconf-apt-progress/title:
  debconf/priority: high

Bug#862786: pdmenu depends on the obsolete Debian menu

[Adrian Bunk]

Package: pdmenu
Version: 1.3.4
Severity: serious

pdmenu heavily uses the obsolete Debian menu.

Since many packages already dropped their Debian menu entries,
the selection of programs offered has become pretty random.

Bug#862779: ghostscript: Regression caused by CVE-2017-8291 fix: breaks pstoedit when using DELAYBIND feature

[Salvatore Bonaccorso]

FTR, "reproducer"

$ pstoedit -f plot-svg foo.pdf foo.svg -dt -ssp -psarg -r9600x9600 -pta

Regards,
Salvatore

Bug#862779: ghostscript: Regression caused by CVE-2017-8291 fix: breaks pstoedit when using DELAYBIND feature

[Salvatore Bonaccorso]

Package: ghostscript
Version: 9.20~dfsg-3.1
Severity: serious
Tags: patch security upstream fixed-upstream
Justification: regression
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=697846

Hi

The update in unstable for ghostscript breaks pstoedit when using
DELAYBIND feature.

Details: https://bugs.ghostscript.com/show_bug.cgi?id=697846

and originally reported in Ubuntu as:

https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1687614

Fix:
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=57f20719

AFAICT, this does only apply to stretch/sid, but not to jessie (but
needs another review).

Regards,
Salvatore

Bug#862769: libbloom FTBFS on amd64: error: expected error 0.100000 but observed 0.200000

[Adrian Bunk]

Source: libbloom
Version: 1.4-6
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libbloom=amd64=1.4-6=1494930635=0

...
/«PKGBUILDDIR»/build/test-libbloom
- Running basic tests -
- basic -
bloom at 0x7ffc4a988c30 not initialized!
bloom at 0x7ffc4a988c30 not initialized!
bloom at 0x7ffc4a988c30
 ->entries = 102
 ->error = 0.10
 ->bits = 488
 ->bits per elem = 4.792529
 ->bytes = 61
 ->hash functions = 4
- add_random(10, 0.10, 10, 0, 1, 32, 1) -
bloom at 0x7ffc4a988b20
 ->entries = 10
 ->error = 0.10
 ->bits = 47
 ->bits per elem = 4.792529
 ->bytes = 6
 ->hash functions = 4
entries: 10, error: 0.10, count: 10, coll: 2, error: 0.20, bytes: 6
error: expected error 0.10 but observed 0.20
Makefile:124: recipe for target 'test' failed
make[2]: *** [test] Error 1

Bug#862075: tagged as pending

[Gaudenz Steinlin]

tag 862075 pending
--

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

http://anonscm.debian.org/cgit/pkg-ceph/ceph.git/diff/?id=a12798a

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit a12798af80d903bbaa18d174a98ac5c6ae8b1204
Author: Gaudenz Steinlin 
Date:   Thu May 11 23:09:24 2017 +0200

Add fix-init-system-detection.patch

This replaces the static init system detection by more appropriate
runtime detection which also works if a Debian system is running with
sysvinit.

Closes: #862075

Processed: Bug#862075 tagged as pending

[Debian Bug Tracking System]

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

> tag 862075 pending
Bug #862075 {Done: Gaudenz Steinlin } [ceph-base] 
ceph-detect-init: Platform is not supported.: debian  9.0
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#830363: marked as done (sciplot: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Tue, 16 May 2017 15:07:29 +
with message-id 
and subject line Bug#830363: fixed in sciplot 1.36-17
has caused the Debian Bug report #830363,
regarding sciplot: FTBFS: dh_install: missing files, aborting
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> install in . done
> make[1]: Leaving directory '/«PKGBUILDDIR»'
>dh_install
> dh_install: Cannot find (any matches for) "libsciplot.so.1.36" (tried in "." 
> and "debian/tmp")
> dh_install: sciplot1 missing files: libsciplot.so.1.36
> dh_install: missing files, aborting
> make: *** [binary] Error 255

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/sciplot_1.36-16_unstable_reb.normal.log

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

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

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated sciplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 May 2017 15:00:44 +0100
Source: sciplot
Binary: sciplot1 sciplot-dev
Architecture: source amd64
Version: 1.36-17
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 sciplot-dev - Development library and header files for SciPlot
 sciplot1   - widget for scientific plotting
Closes: 830363
Changes:
 sciplot (1.36-17) unstable; urgency=medium
 .
   * update so version string extraction snippet (closes: #830363)
   * dh 10
   * bump standards version
Checksums-Sha1:
 b9d2bd33c163b40b52d7ef163bdb5cefb0ccc793 1906 sciplot_1.36-17.dsc
 bad4655ec7ad3db1c0f8565feea71f03637e758b 5836 sciplot_1.36-17.debian.tar.xz
 bf421f8d4f87113709d449535e603ec4734d4721 83106 sciplot-dev_1.36-17_amd64.deb
 bc729403c031b9fd7aaea8e6a01ed1ed93c927a6 37310 sciplot1_1.36-17_amd64.deb
 9279c2a3cb9bd8fc2e35468502bfee4db69c78ec 7448 sciplot_1.36-17_amd64.buildinfo
Checksums-Sha256:
 8e5659543338a0a0e6cbb0131dc69ba8614f3a90a7c0d4b3879f94d45526a9eb 1906 
sciplot_1.36-17.dsc
 b3b9d77553cadbd355e9866bfc453579b6a796a9673bdf5689d55ef40349566d 5836 
sciplot_1.36-17.debian.tar.xz
 52474b0694139cc3b0637208c1beba595893587cc667573a14c0198ddf638079 83106 
sciplot-dev_1.36-17_amd64.deb
 5a148a40a96e780ec6f6d0e8b90465b9e9c719a73679982ed320cc0861a0dc06 37310 
sciplot1_1.36-17_amd64.deb
 ce108167fb0091599a1fdb9434b0c9634214792508c94578475ea9ed01632f93 7448 
sciplot_1.36-17_amd64.buildinfo
Files:
 9566a12404dae8dd092c39cdb8c14cb4 1906 science extra sciplot_1.36-17.dsc
 48dd82129484d97507a2c3b963268ed0 5836 science extra 
sciplot_1.36-17.debian.tar.xz
 da9731693491e20778f677c9dc62d7e7 83106 libdevel extra 
sciplot-dev_1.36-17_amd64.deb
 93b6c967e855a0397c5a93e33dbaf0bb 37310 libs extra sciplot1_1.36-17_amd64.deb
 74fb4f324b4e6d7326ceeaf84c4633f6 7448 science extra 
sciplot_1.36-17_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAlkbC9UACgkQEltXR14Z
DRixrw/7Bv8NtPB95awm8HMcsIqFV34wxn+THpAf33fz9pgGKst6IE7Y5x5g+W6+
EX68P4v/CBnK+YqIP6d+YQOs7Y2oCD3BQ7ptyp9OGRwv0z7qOJ5bgQ/n1WORYUcb

Bug#862742: filetea: Wrong version of jQuery gets installed

[Rahul De]

Package: filetea
Version: 0.1.16-3+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The package uses the function live which has been removed in jQuery 1.9.
The source in the upstream depends on 1.7.2 and no version has been
mentioned in the control file of the packaging for libjs-jquery. Hence
the latest version(3.1.1) is fetched which breaks it and makes it unusable
for everyone.

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

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

Processed: found 862611 in 1.3.3-2, fixed 862611 in 1.3.3-2+nmu1+deb7u2

[Debian Bug Tracking System]

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

> found 862611 1.3.3-2
Bug #862611 {Done: Andrew Starr-Bochicchio } [deluge-webui] 
deluge-webui: directory traversal attack vulnerability
Marked as found in versions deluge/1.3.3-2.
> fixed 862611 1.3.3-2+nmu1+deb7u2
Bug #862611 {Done: Andrew Starr-Bochicchio } [deluge-webui] 
deluge-webui: directory traversal attack vulnerability
There is no source info for the package 'deluge-webui' at version 
'1.3.3-2+nmu1+deb7u2' with architecture ''
Unable to make a source version for version '1.3.3-2+nmu1+deb7u2'
Marked as fixed in versions 1.3.3-2+nmu1+deb7u2.
> thanks
Stopping processing here.

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

Bug#862741: python3-iptables: rule.create_match() raises MemoryError

[Alexander Barinov]

Package: python3-iptables
Version: 0.11.0-3
Severity: grave
Justification: renders package unusable

The following sample code raises MemoryError on all my Debian systems:

Python 3.5.3 (default, Jan 19 2017, 14:11:04)
[GCC 6.3.0 20170118] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import iptc
>>> iptc.Rule().create_match('udp')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/iptc/ip4tc.py", line 959, in create_match
match = Match(self, name=name, revision=revision)
  File "/usr/lib/python3/dist-packages/iptc/ip4tc.py", line 558, in __init__
self.reset()
  File "/usr/lib/python3/dist-packages/iptc/ip4tc.py", line 635, in reset
udata_buf = (ct.c_ubyte * udata_size)()
MemoryError

Using any other method to create a match (iptc.Match(rule, 'tcp')) or
any other match type ('tcp', 'owner', etc) and other kernels (4.9.0
from testing, old 4.6.0 from testing) gives the same results. This bug
makes it impossible to construct any iptable rule as matches are the
core of it - and this pretty much defeats the purpose of the package.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (1000, 'testing'), (50, 'unstable'), (20, 'stable'), (1,
'experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages python3-iptables depends on:
ii  iptables 1.6.0+snapshot20161117-6
ii  libc62.24-10
ii  python3  3.5.3-1
pn  python3:any  

python3-iptables recommends no packages.

Versions of packages python3-iptables suggests:
pn  python-iptables-doc  

-- no debconf information

Processed: Found in unstable/testing/stable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u8
Bug #862690 {Done: Bastien Roucariès } [src:imagemagick] 
imagemagick: Built-Using field with binary version
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u8.
> found -1 8:6.7.7.10-5+deb7u13
Bug #862690 {Done: Bastien Roucariès } [src:imagemagick] 
imagemagick: Built-Using field with binary version
The source 'imagemagick' and version '8:6.7.7.10-5+deb7u13' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u13.
> found -1 8:6.7.7.10-5+deb7u4
Bug #862690 {Done: Bastien Roucariès } [src:imagemagick] 
imagemagick: Built-Using field with binary version
Marked as found in versions imagemagick/8:6.7.7.10-5+deb7u4.

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

Bug#862690: Found in unstable/testing/stable

[Bastien ROUCARIES]

control: found -1 8:6.8.9.9-5+deb8u8
control: found -1 8:6.7.7.10-5+deb7u13
control: found -1 8:6.7.7.10-5+deb7u4

Bug#854708: marked as done (tpm_sealdata -> segmentation fault)

[Debian Bug Tracking System]

Your message dated Tue, 16 May 2017 12:34:44 +
with message-id 
and subject line Bug#854708: fixed in tpm-tools 1.3.9.1-0.1
has caused the Debian Bug report #854708,
regarding tpm_sealdata -> segmentation fault
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.)


-- 
854708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tpm-tools
Version: 1.3.9-0.1

$ echo hello | tpm_sealdata
Enter SRK password:
-BEGIN TSS-
-TSS KEY-
.
.. ==
-ENC KEY-
Symmetric Key: AES-256-CBC
.
.
.==
-ENC DAT-
segmentation fault

$ cat /proc/version
Linux version 4.9.0-1-686-pae (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3
(2017-01-28)
--- End Message ---
--- Begin Message ---
Source: tpm-tools
Source-Version: 1.3.9.1-0.1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated tpm-tools 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: Sat, 13 May 2017 13:55:08 +0200
Source: tpm-tools
Binary: tpm-tools tpm-tools-dbg libtpm-unseal1 libtpm-unseal-dev
Architecture: source amd64
Version: 1.3.9.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: Laurent Bigonville 
Description:
 libtpm-unseal-dev - Management tools for the TPM hardware (development)
 libtpm-unseal1 - Management tools for the TPM hardware (library)
 tpm-tools  - Management tools for the TPM hardware (tools)
 tpm-tools-dbg - Management tools for the TPM hardware (debug)
Closes: 854708
Changes:
 tpm-tools (1.3.9.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release
 - Fix segfault in tpm_sealdata (Closes: #854708)
   * debian/control: Use ${misc:Pre-Depends} instead of (Pre-) depending on
 multiarch-support explicitly
Checksums-Sha1:
 5587063e3637f26b859e4fc3d56f6036569ba607 1701 tpm-tools_1.3.9.1-0.1.dsc
 c35cb031c6b5220dd1c8a03995654fdd12aa3031 482859 tpm-tools_1.3.9.1.orig.tar.gz
 8909f2dc9509ade529633e737c6d34448eff1d3b 9564 
tpm-tools_1.3.9.1-0.1.debian.tar.xz
 19a627172daac0a866cd8e8e08fccf884d0ba8dd 8984 
libtpm-unseal-dev_1.3.9.1-0.1_amd64.deb
 63deb9eee9ac92483ee49491efb19258cf84ee65 19720 
libtpm-unseal1_1.3.9.1-0.1_amd64.deb
 9fa884ce932f3688f3d21367a6b91cbe01a981ff 641988 
tpm-tools-dbg_1.3.9.1-0.1_amd64.deb
 c8c868a71b033a2bebd275f23c8d5d56befb89ed 6356 
tpm-tools_1.3.9.1-0.1_amd64.buildinfo
 b3fe16fc877daf82b1bdb1974e88a22fb5adfbdc 137722 tpm-tools_1.3.9.1-0.1_amd64.deb
Checksums-Sha256:
 6eb95dcb500d1c1871b9bbbfb80580da8ac2f0f5a56efdd5f412b7d7c93ffb4f 1701 
tpm-tools_1.3.9.1-0.1.dsc
 9cb714e2650826e2e932f65bc0ba9d61b927dc5fea47f2c2a2b64f0fdfcbfa68 482859 
tpm-tools_1.3.9.1.orig.tar.gz
 4bdef45ec2b7816662a46a28d9572349829f426c9e3e0ff1eee56f0c015191a7 9564 
tpm-tools_1.3.9.1-0.1.debian.tar.xz
 aab8958198ddff702531d971b2b31928114b578ad3dc95e864df89dcf79f2ca4 8984 
libtpm-unseal-dev_1.3.9.1-0.1_amd64.deb
 a636cea320676a03c760d88c8a7f756934cd105da51f400abc91eb33a9450513 19720 
libtpm-unseal1_1.3.9.1-0.1_amd64.deb
 3551546e3fe57cb903653ef36dbca0982c17ace543fe02c606e4accaeee9fa8e 641988 
tpm-tools-dbg_1.3.9.1-0.1_amd64.deb
 a00f6d54a70376a85f79c47a1a3958cfec4a1ab392eec61eb155057ff8684ed4 6356 
tpm-tools_1.3.9.1-0.1_amd64.buildinfo
 8df8ec10d5b688bc607a730d6d6e2925c7008cfaa70495a8b79a3a42b7a06892 137722 
tpm-tools_1.3.9.1-0.1_amd64.deb
Files:
 8adf65390f467826932414087b278fcd 1701 admin optional tpm-tools_1.3.9.1-0.1.dsc
 1532293aa632a0eaa7e60df87c779855 482859 admin optional 
tpm-tools_1.3.9.1.orig.tar.gz
 bbbfa68078b5896db9c7467423010fa4 9564 admin optional 
tpm-tools_1.3.9.1-0.1.debian.tar.xz
 1d40f84e6ed019fba026dded6b6d3977 8984 libdevel optional 
libtpm-unseal-dev_1.3.9.1-0.1_amd64.deb
 40774f1e5c2e7dd9d537fd29e94f21d1 19720 libs optional 

Bug#862570: libmenu-cache: menu-cached socket may be blocked by another user.

[Andriy Grytsenko]

Thank you very much!

Bug#771790: marked as done (dirty.js 0.9.6 doesn't work properly with recent nodejs)

[Debian Bug Tracking System]

Your message dated Tue, 16 May 2017 09:03:55 +
with message-id 
and subject line Bug#771790: fixed in dirty.js 1.0.0-0.1
has caused the Debian Bug report #771790,
regarding dirty.js 0.9.6 doesn't work properly with recent nodejs
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.)


-- 
771790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dirty.js
Version: 0.9.6-1


dirty.js 0.9.6 doesn't work properly with nodejs 0.10, which is now on
debian testing.
One example: 
https://github.com/felixge/node-dirty/commit/434764a2411a7de89e2886152f03a7e24495aa48

This can be fixed by packaging a more recent version of dirty.js.


Thanks,
-- 
Marcos Marado
--- End Message ---
--- Begin Message ---
Source: dirty.js
Source-Version: 1.0.0-0.1

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

Debian distribution maintenance software
pp.
Val Markovic  (supplier of updated dirty.js package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 May 2017 20:51:02 -0700
Source: dirty.js
Binary: node-dirty
Architecture: source
Version: 1.0.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Val Markovic 
Description:
 node-dirty - tiny and fast key-value store for Node
Closes: 771790
Changes:
 dirty.js (1.0.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Gianfranco Costamagna ]
   * Switch to compat level 10
   * Fix unsecure VCS fields
   * Fix copyright format link
 .
   [ Val Markovic ]
   * New upstream version 1.0.0 (Closes: #771790)
   * Update std-version to 3.9.8, no changes required.
   * Fix watch file
Checksums-Sha1:
 d8357e9d25a8d322d13f3ee32c9bcfd77e0c3766 1940 dirty.js_1.0.0-0.1.dsc
 2b0303e92bd97b0d307d2f974d69c5c0ff243e6f 8501 dirty.js_1.0.0.orig.tar.gz
 0e5256a2f3d2f9600887755c985e73932717d6a8 2232 dirty.js_1.0.0-0.1.debian.tar.xz
Checksums-Sha256:
 bce62c5fe0ae2e0a7848b95d3badedf80ca401204b5cf33c546587af5dcb257b 1940 
dirty.js_1.0.0-0.1.dsc
 5f9ccaa53a09949234537396e1166293bb354def104b475f2edd4eac7f383b1f 8501 
dirty.js_1.0.0.orig.tar.gz
 3397411aae4e9cf95a1a8088dc09a5254e2cdc20ed15456a6085b598299c8d64 2232 
dirty.js_1.0.0-0.1.debian.tar.xz
Files:
 41ab7ff8558024d5b56ab2bbd5c31e00 1940 web optional dirty.js_1.0.0-0.1.dsc
 01dc1cfa543e004f72c1f8aa0d3cb26f 8501 web optional dirty.js_1.0.0.orig.tar.gz
 f61bd4a2d9e8ce3b56426fa286f10708 2232 web optional 
dirty.js_1.0.0-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZGr4tAAoJEPNPCXROn13ZAZYP/iaHSMWLLj3hnLOlGO5zwC5M
kYllHIXsjLsj42mUwFVEGTXdikjIbGLffHqeXKcNliMle/rRgW5Kt1T4NmU8+0tB
RWsf1IW5pAo3V4Qj2lPBbG+/Lxk2QSGLrlf308DpqAkp1FiLO1i3SfyKQ+qLYqvv
Z4gfhj9SsQym5TZsF0Hp6NVfuuNtug1RAanbQgi5fkOg5Tydi6LYY1sYt9+JOhcP
eCSrL+E2J+YdhDMQc1IdJK0UpTwb5OPZcGIQPaYCxiN1COvFcNV1DrAgDlTt220O
EFdQIsgrUJRAIEW/Wnzpsy8w2LCaJ+vm5qmPvRh+YL4KRvlBV5w2GfiuoZoTS+mS
yP8/65OalOYALVN6xoqksHdqvJ06fXkKLHGOwPoQW2/F91cifFcEKC+H0KS5oT+C
SzyTbhqRoeeU+4g4gx/nDpiU0vhbHYvm6zdp0S1qxwS3So4bd0zMPYxCBqhH0QoN
d8YCT5bSJK/BC0U85iLKaTGG7KXqllmDFW9687cA86FBx4hHeWyIDNeuDeR+3pdO
RIc6nMzr6BpYP77TlxhWhQcb+/zju71DuBxyuzDgaMGTzPz05WLxUyVCpkdnLC11
ne3HrCHN6ulVJbyKJ5pVPDni1/kZrBPfFXv+ng3yk3KQKC85UBG5rCq5vd9v8yaM
M4A3xc7mNsr9l3cuTRZd
=yS/3
-END PGP SIGNATURE End Message ---

Bug#771790: marked as done (dirty.js 0.9.6 doesn't work properly with recent nodejs)

[Debian Bug Tracking System]

Your message dated Tue, 16 May 2017 10:58:27 +0200
with message-id 
and subject line Re: Bug#771790: Fixed with 1.0.0
has caused the Debian Bug report #771790,
regarding dirty.js 0.9.6 doesn't work properly with recent nodejs
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.)


-- 
771790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dirty.js
Version: 0.9.6-1


dirty.js 0.9.6 doesn't work properly with nodejs 0.10, which is now on
debian testing.
One example: 
https://github.com/felixge/node-dirty/commit/434764a2411a7de89e2886152f03a7e24495aa48

This can be fixed by packaging a more recent version of dirty.js.


Thanks,
-- 
Marcos Marado
--- End Message ---
--- Begin Message ---
Hi,

nmu attached (and committed on git)

G.
diff -Nru dirty.js-0.9.6/benchmark/dirty/for-each.js 
dirty.js-1.0.0/benchmark/dirty/for-each.js
--- dirty.js-0.9.6/benchmark/dirty/for-each.js  2012-02-05 23:30:33.0 
+0100
+++ dirty.js-1.0.0/benchmark/dirty/for-each.js  2017-05-15 04:12:04.0 
+0200
@@ -1,23 +1,22 @@
-require('../../test/common');
+var config = require('../../test/config');
 var COUNT = 1e6,
-dirty = require('dirty')(),
+dirty = require(config.LIB_DIRTY)(),
 util = require('util');
 
 for (var i = 0; i < COUNT; i++) {
   dirty.set(i, i);
 }
 
-var start = +new Date, i = 0;
+var start = Date.now(), i = 0;
 dirty.forEach(function(key, doc) {
   if (!key && key !== 0) {
 throw new Error('implementation fail');
   }
 });
 
-var ms = +new Date - start,
+var ms = Date.now() - start,
 mhz = ((COUNT / (ms / 1000)) / 1e6).toFixed(2),
 million = COUNT / 1e6;
 
 // Can't use console.log() since since I also test this in ancient node 
versions
 util.log(mhz+' Mhz ('+million+' million in '+ms+' ms)');
-
diff -Nru dirty.js-0.9.6/benchmark/dirty/get.js 
dirty.js-1.0.0/benchmark/dirty/get.js
--- dirty.js-0.9.6/benchmark/dirty/get.js   2012-02-05 23:30:33.0 
+0100
+++ dirty.js-1.0.0/benchmark/dirty/get.js   2017-05-15 04:12:04.0 
+0200
@@ -1,20 +1,20 @@
-require('../../test/common');
+var config = require('../../test/config');
 var COUNT = 1e6,
-dirty = require('dirty')(),
+dirty = require(config.LIB_DIRTY)(),
 util = require('util');
 
 for (var i = 0; i < COUNT; i++) {
   dirty.set(i, i);
 }
 
-var start = +new Date;
+var start = Date.now();
 for (var i = 0; i < COUNT; i++) {
   if (dirty.get(i) !== i) {
 throw new Error('implementation fail');
   }
 }
 
-var ms = +new Date - start,
+var ms = Date.now() - start,
 mhz = ((COUNT / (ms / 1000)) / 1e6).toFixed(2),
 million = COUNT / 1e6;
 
diff -Nru dirty.js-0.9.6/benchmark/dirty/load.js 
dirty.js-1.0.0/benchmark/dirty/load.js
--- dirty.js-0.9.6/benchmark/dirty/load.js  2012-02-05 23:30:33.0 
+0100
+++ dirty.js-1.0.0/benchmark/dirty/load.js  2017-05-15 04:12:04.0 
+0200
@@ -1,7 +1,7 @@
-require('../../test/common');
+var config = require('../../test/config');
 var COUNT = 1e4,
-DB_FILE = __dirname+'/../../test/tmp/benchmark-set-drain.dirty',
-dirty = require('dirty')(DB_FILE),
+DB_FILE = config.TMP_PATH + '/benchmark-set-drain.dirty',
+dirty = require(config.LIB_DIRTY)(DB_FILE),
 util = require('util'),
 loaded = false;
 
@@ -10,9 +10,9 @@
 }
 
 dirty.on('drain', function() {
-  var start = +new Date;
+  var start = Date.now();
   require('dirty')(DB_FILE).on('load', function(length) {
-var ms = +new Date - start,
+var ms = Date.now() - start,
 mhz = ((COUNT / (ms / 1000)) / 1e3).toFixed(2),
 million = COUNT / 1e6;
 
diff -Nru dirty.js-0.9.6/benchmark/dirty/set-drain-256-bytes-per-doc.js 
dirty.js-1.0.0/benchmark/dirty/set-drain-256-bytes-per-doc.js
--- dirty.js-0.9.6/benchmark/dirty/set-drain-256-bytes-per-doc.js   
2012-02-05 23:30:33.0 +0100
+++ dirty.js-1.0.0/benchmark/dirty/set-drain-256-bytes-per-doc.js   
2017-05-15 04:12:04.0 +0200
@@ -1,16 +1,16 @@
-require('../../test/common');
+var config = require('../../test/config');
 var COUNT = 1e5,
-dirty = 
require('dirty')(__dirname+'/../../test/tmp/benchmark-set-drain.dirty'),
+dirty = require(config.LIB_DIRTY)(config.TMP_PATH + 
'/benchmark-set-drain.dirty'),
 util = require('util'),
 drained = false;
 
-var start = +new Date;
+var start = Date.now();
 for (var i = 0; i < COUNT; i++) {
   dirty.set(i, 'This string has 256 bytes. This string has 256 bytes. This 
string has 256 bytes. This string has 256 bytes.  

Bug#862400: several bios updates exist since 2007

[Arturo Borrero Gonzalez]

On Mon, 15 May 2017 13:56:24 +0200 Arturo Borrero Gonzalez
 wrote:

>
> But the question remains, is this some kind of kernel regression?
>
>

BTW, I can give ssh access to the machine, running 4.7, for testing pourposes.

Bug#860608: [pkg-golang-devel] Bug#860608: Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Michael Stapelberg]

On Tue, May 16, 2017 at 6:46 AM, Steve Langasek  wrote:

> On Mon, May 15, 2017 at 03:17:03PM -0700, Steve Langasek wrote:
> > On Mon, May 15, 2017 at 08:56:08AM +0200, Michael Stapelberg wrote:
> > > >> Package: golang-github-gosexy-gettext-dev
>
> > > > vorlon, can we file for removal of this package? It wasn’t touched
> since
> > > > 2013 and has no rdepends.
>
> > > Done: https://bugs.debian.org/862612
>
> > Thanks for filing, 100% agreed.
>
> So, I double checked and:
>
> $ dak rm -R -n -s unstable golang-github-gosexy-gettext
> Will remove the following packages from unstable:
>
> golang-github-gosexy-gettext | 0~git20130221-1 | source
> golang-github-gosexy-gettext-dev | 0~git20130221-1 | all
>
> Maintainer: Steve Langasek 
>
> --- Reason ---
>
> --
>
> Checking reverse dependencies...
> # Broken Build-Depends:
> snapd: golang-github-gosexy-gettext-dev
>

Thanks for checking. I just realized I only checked using “apt rdepends”,
which of course won’t consider build-deps. Doh.


>
> Dependency problem found.
>
> $
>
> It certainly appears that we are still using this package, so I'm closing
> the bug report.  (I wouldn't expect the ftpmasters to act on it in its
> current state anyway.)
>
> And I've uploaded a no-change rebuild of golang-github-gosexy-gettext-dev.
>
> --
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developerhttp://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org
>



-- 
Best regards,
Michael