Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 888190 buster sid
Bug #888190 [src:ruby-mustermann19] ruby-mustermann19: FTBFS on ruby2.5: 
TypeError: Integer
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#889048: [node-source-map] FTBFS: lib/mappings.wasm

[Bastien ROUCARIÈS]

Package: node-source-map
Version: 0.7.0+dfsg-1
Severity: serious

Please give me pointer how to compile this file

Bastien

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

Bug#888953: gobby accesses the network during the build

[Simon McVittie]

On Thu, 01 Feb 2018 at 12:40:16 +0100, Philipp Kern wrote:
> I'll note that I was told to stop build-depending on rarian-compat in
> #885642, which then introduced this bug.

That request was less clear than it could have been, but the intention
was to stop using the deprecated documentation toolchain, not just stop
build-depending on parts of it.

> > (For context, Scrollkeeper is very obsolete, rarian-compat is an
> > obsolete
> > compatibility shim for Scrollkeeper, and gnome-doc-utils has itself
> > been superseded by yelp-tools; it's deprecations all the way down.
> 
> Well, I suppose it'd help if there would be some guidance on how to do
> things today. I'm (somewhat) happy to fix it upstream if needed.

Here's upstream's migration guide, with links to the commits used to
migrate an example package:
https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure
(I'll try to follow up to the other bugs from the same MBF as #885642 at
some point with a reference to this.)

smcv

Bug#889046: ruby2.5 FTBFS with tzdata 2018c-1

[Adrian Bunk]

Source: ruby2.5
Version: 2.5.0-4
Severity: serious

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

...
  1) Failure:
TestTimeTZ#test_asia_tokyo [/<>/test/ruby/test_time_tz.rb:129]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 2, 0, 0).
<"1951-05-06 03:00:00 +1000"> expected but was
<"1951-05-06 02:00:00 +1000">.

  2) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_24 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 5, 5, 16, 59, 59).localtime.
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 02:59:59 +1000">.

  3) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_27 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 9, 7, 16, 0, 0).localtime.
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 02:00:00 +1000">.

  4) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_69 
[/<>/test/ruby/test_time_tz.rb:277]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 1, 59, 59).
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 01:59:59 +1000">.

  5) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_72 
[/<>/test/ruby/test_time_tz.rb:295]:
TZ=Asia/Tokyo Time.local(0, 0, 1, 8, 9, 1951, nil, nil, false, nil).
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 01:00:00 +1000">.

Finished tests in 384.583156s, 44.7940 tests/s, 5880.9466 assertions/s.
17227 tests, 2261713 assertions, 5 failures, 0 errors, 60 skips

ruby -v: ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux-gnu]
uncommon.mk:698: recipe for target 'yes-test-almost' failed
make[2]: *** [yes-test-almost] Error 5



http://mm.icann.org/pipermail/tz-announce/2018-January/48.html

   Changes to past time stamps

 Japanese DST transitions (1948-1951) were Sundays at 00:00, not
 Saturdays or Sundays at 02:00.  (Thanks to Takayuki Nikai.)

Bug#889045: [node-source-map] Need not available nodejs > 8

[Bastien ROUCARIÈS]

Package: node-source-map
Version: 0.7.0+dfsg-1
Severity: serious

Need nodejs > 8 that is not available under debian

Give me on reverse dep:
ReferenceError: WebAssembly is not defined
at readWasm.then.buffer (/usr/lib/nodejs/source-map/lib/wasm.js:26:14)
{ name: 'TAP', type: 'ReferenceError', test: 'TAP' }
ReferenceError: WebAssembly is not defined
at readWasm.then.buffer (/usr/lib/nodejs/source-map/lib/wasm.js:26:14)
{ name: 'TAP', type: 'ReferenceError', test: 'TAP' }
ReferenceError: WebAssembly is not defined
at readWasm.then.buffer (/usr/lib/nodejs/source-map/lib/wasm.js:26:14)
{ name: 'TAP', type: 'ReferenceError', test: 'TAP' }
ReferenceError: WebAssembly is not defined
at readWasm.then.buffer (/usr/lib/nodejs/source-map/lib/wasm.js:26:14)
{ name: 'TAP', type: 'ReferenceError', test: 'TAP' }


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

Bug#888201: mailman: CVE-2018-5950

[Thijs Kinkhorst]

>> I plan to release Mailman 2.1.26 along with a patch for older releases
>> to fix this issue on Feb 4, 2018. At that time, full details of the
>> vulnerability will be public.

I've reserved time on Sunday to in any case to sid when the fix is
released, and depending on the details/severity look into a security
upload.


Thijs

Bug#889048: [node-source-map] FTBFS: lib/mappings.wasm

[Jérémy Lal]

2018-02-01 13:39 GMT+01:00 Bastien ROUCARIÈS :

> Package: node-source-map
> Version: 0.7.0+dfsg-1
> Severity: serious
>
> Please give me pointer how to compile this file
>

It's generated by another project:
https://github.com/fitzgen/source-map-mappings/blob/master/source-map-mappings-wasm-api/build.py

Processed: Upstream bug

[Debian Bug Tracking System]

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

> forwarded 889023 https://github.com/SciRuby/rb-gsl/issues/56
Bug #889023 [src:ruby-gsl] ruby-gsl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared
Set Bug forwarded-to-address to 'https://github.com/SciRuby/rb-gsl/issues/56'.
> thanks
Stopping processing here.

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

Bug#888953: gobby accesses the network during the build

[Simon McVittie]

On Thu, 01 Feb 2018 at 11:23:28 +0200, Adrian Bunk wrote:
> On Wed, Jan 31, 2018 at 03:53:11PM +0100, Matthias Klose wrote:
> > While seen on a launchpad build, it looks like a missing build dependency,
> > because it tries to access the docbookx.dtd from the network:

My understanding is that it's currently up to the package being built
(e.g. gobby, not gnome-doc-utils) to build-depend on the appropriate
package to get the DTDs of its XML documentation to be registered
in the xml-core catalog and available without hitting the network:
docbook-xml for docbookx.dtd, rarian-compat for scrollkeeper-omf.dtd,
and possibly others.

If GNOME-2-style documentation always includes both Docbook and
Scrollkeeper/Rarian OMF format (I'm not clear on the details) then perhaps
gnome-doc-utils should have Depends on both of those. If they are not
always needed, then it probably shouldn't.

(For context, Scrollkeeper is very obsolete, rarian-compat is an obsolete
compatibility shim for Scrollkeeper, and gnome-doc-utils has itself
been superseded by yelp-tools; it's deprecations all the way down. I've
asked the ftp team to override gnome-doc-utils from gnome to oldlibs,
and pushed a better package description to gnome-team git for inclusion
in the next upload.)

> There is also the related issue that 
> /usr/share/gnome-doc-utils/gnome-doc-utils.make
> shouldn't call xmllint without --nonet

I'm not sure that this would be a good idea to do
unconditionally. gnome-doc-utils.make gets copied into source packages
by gnome-doc-prepare (analogous to autoconf, automake, libtoolize) so
by making this change, we would be imposing Debian policy on upstream
packages that happen to have been prepared by a `make dist` on a Debian
system.

In Debian, accessing the network during build is forbidden (for good
reason), and we have the xml-core catalog as a way to get DTDs without
doing so. However, when packages whose upstream release happens to have
been made on a Debian system are built on less enlightened distributions
that don't have (or want) that policy, and that don't necessarily even
have an equivalent of xml-core, they still need to build successfully.

Is there a canonical way to detect that we are in a Debian package build,
that could be used to add --nonet to the xmllint command-line if and only
if this is a Debian package build?

smcv

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 888119 buster sid
Bug #888119 [src:ruby-awesome-print] ruby-awesome-print: FTBFS on ruby2.5: test 
failure: colorization default
Added tag(s) buster and sid.
> tags 888147 buster sid
Bug #888147 [src:ruby-backports] ruby-backports: FTBFS on ruby2.5: tests: 
encoding change
Added tag(s) buster and sid.
> tags 888117 buster sid
Bug #888117 [src:ruby-beautify] ruby-beautify: FTBFS on ruby2.5: tests fail: .. 
got: "EXPR_BEG
Added tag(s) buster and sid.
> tags 888120 buster sid
Bug #888120 [src:ruby-dalli] ruby-dalli: FTBFS on ruby2.5: "File does not 
exist:"
Added tag(s) buster and sid.
> tags 888149 buster sid
Bug #888149 [src:ruby-escape-utils] ruby-escape-utils: FTBFS on ruby2.5: 
property file encoding: UTF-8
Added tag(s) buster and sid.
> tags 888186 buster sid
Bug #888186 [src:ruby-fakefs] ruby-fakefs: FTBFS on ruby2.5: pread method is 
not available in File :(
Added tag(s) buster and sid.
> tags 888124 buster sid
Bug #888124 [src:ruby-fakeweb] ruby-fakeweb: FTBFS on ruby2.5: undefined method 
`close' for #
Added tag(s) buster and sid.
> tags 888187 buster sid
Bug #888187 [src:ruby-ffaker] ruby-ffaker: FTBFS on ruby2.5: 
test_paragraphsLoremFR
Added tag(s) buster and sid.
> tags 889021 buster sid
Bug #889021 [src:ruby-ffi-yajl] ruby-ffi-yajl: FTBFS with ruby2.5: 'rb_cFixnum' 
undeclared
Added tag(s) buster and sid.
> tags 888127 buster sid
Bug #888127 [src:ruby-grape-entity] ruby-grape-entity: FTBFS on ruby2.5: syntax 
error, unexpected '{'
Added tag(s) buster and sid.
> tags 888150 buster sid
Bug #888150 [src:ruby-graphviz] ruby-graphviz: FTBFS on ruby2.5:  undefined 
method `graph' for nil
Added tag(s) sid and buster.
> tags 889023 buster sid
Bug #889023 [src:ruby-gsl] ruby-gsl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared
Added tag(s) sid and buster.
> tags 889024 buster sid
Bug #889024 [src:ruby-hamlit] ruby-hamlit: FTBFS with ruby2.5: several test 
failures
Added tag(s) sid and buster.
> tags 888188 buster sid
Bug #888188 [src:ruby-hashie] ruby-hashie: FTBFS on ruby2.5: stack overflow 
around Integer
Added tag(s) buster and sid.
> tags 888189 buster sid
Bug #888189 [src:ruby-innertube] ruby-innertube: FTBFS on ruby2.5: undefined 
method mock
Added tag(s) buster and sid.
> tags 888129 buster sid
Bug #888129 [src:ruby-json-spec] ruby-json-spec: FTBFS on ruby2.5: 
Fixnum/Integer
Added tag(s) buster and sid.
> tags 888135 buster sid
Bug #888135 [src:ruby-lapack] ruby-lapack: FTBFS on ruby2.5: `dirname': no 
implicit conversion of nil into String
Added tag(s) sid and buster.
> tags 888151 buster sid
Bug #888151 [src:ruby-logging] ruby-logging: FTBFS on ruby2.5: warning: 
constant ::Fixnum is deprecated
Added tag(s) buster and sid.
> tags 888160 buster sid
Bug #888160 [src:ruby-memfs] ruby-memfs: FTBFS on ruby2.5: No such file or 
directory - /test-file
Added tag(s) sid and buster.
> tags 888161 buster sid
Bug #888161 [src:ruby-multimap] ruby-multimap: FTBFS on ruby2.5: error: void 
value not ignored as it ought to be
Added tag(s) buster and sid.
> tags 888130 buster sid
Bug #888130 [src:ruby-net-http-persistent] ruby-net-http-persistent: FTBFS on 
ruby2.5: ssl verification fails
Added tag(s) sid and buster.
> tags 889025 buster sid
Bug #889025 [src:ruby-odbc] ruby-odbc: FTBFS with ruby2.5: invalid operands to 
binary / (have 'char *' and 'char *')
Added tag(s) buster and sid.
> tags 888131 buster sid
Bug #888131 [src:ruby-oj] ruby-oj: FTBFS on ruby2.5: too many arguments to 
function 'rb_struct_ptr'
Added tag(s) buster and sid.
> tags 888164 buster sid
Bug #888164 [src:ruby-packable] ruby-packable: FTBFS on ruby2.5: Illegal seek @ 
rb_io_tell
Added tag(s) buster and sid.
> tags 888191 buster sid
Bug #888191 [src:ruby-powerpack] ruby-powerpack: FTBFS on ruby2.5: Error: 
expect([].sum).to be_nil
Added tag(s) buster and sid.
> tags 888192 buster sid
Bug #888192 [src:ruby-prof] ruby-prof: FTBFS on ruby2.5: ArgumentError: 
incomplete format specifier; use %%
Added tag(s) sid and buster.
> tags 888166 buster sid
Bug #888166 [src:ruby-rabl] ruby-rabl: FTBFS on ruby2.5: BSON:Module serialize
Added tag(s) buster and sid.
> tags 888170 buster sid
Bug #888170 [src:ruby-redcloth] ruby-redcloth: FTBFS on ruby2.5: undefined 
method `load_documents' for Psych:Module
Added tag(s) buster and sid.
> tags 888171 buster sid
Bug #888171 [src:ruby-riot] ruby-riot: FTBFS on ruby2.5: expected "\"hope\"", 
not "hope"
Added tag(s) buster and sid.
> tags 888193 buster sid
Bug #888193 [src:ruby-rmagick] ruby-rmagick: FTBFS on ruby2.5: 
)>
Added tag(s) buster and sid.
> tags 888172 buster sid
Bug #888172 [src:ruby-rspec-its] ruby-rspec-its: FTBFS on ruby2.5: 
Fixnum/Integer
Added tag(s) buster and sid.
> tags 888194 buster sid
Bug #888194 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS on ruby2.5: 
uninitialized constant SafeYAML::Parse::Date::DateTime
Added tag(s) sid and buster.
> tags 888196 buster sid
Bug #888196 

Bug#888989: marked as done (Error: Cannot find module 'node-uuid')

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 12:21:31 +
with message-id 
and subject line Bug#887069: fixed in node-uuid 1.4.7-2
has caused the Debian Bug report #887069,
regarding Error: Cannot find module 'node-uuid'
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.)


-- 
887069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: npm2deb
Version: 0.2.7-6
Severity: normal

https://wiki.debian.org/Javascript/Nodejs/Npm2Deb suggests that we ought 
to be able to do "npm2deb search monocle".

here's what happens:

0 dkg@sid:~$ npm2deb search monocle
npm reports errors about monocle module:
module.js:538
throw err;
^

Error: Cannot find module 'node-uuid'
at Function.Module._resolveFilename (module.js:536:15)
at Function.Module._load (module.js:466:25)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at Object. (/usr/lib/nodejs/request/index.js:29:12)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
1 dkg@sid:~$ 

fwiw, i have node-uuid installed:

0 dkg@sid:~$ COLUMNS=85 dpkg -l | grep node-uuid
ii  libjs-node-uuid 1.4.7-1  all  simple and fast RFC4122 UUID 
genera
ii  node-node-uuid  1.4.7-1  all  simple and fast RFC4122 UUID 
genera
0 dkg@sid:~$ 

I don't know enough about node or javascript to know how to resolve this 
problem myself so it doesn't look like i can fix it easily.

--dkg

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages npm2deb depends on:
ii  devscripts2.17.12
ii  node-github-url-from-git  1.4.0-1
ii  npm   1.4.21+ds-2
ii  python3   3.6.4-1
ii  python3-dateutil  2.6.1-1

npm2deb recommends no packages.

npm2deb suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-uuid
Source-Version: 1.4.7-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-uuid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Feb 2018 13:04:59 +0100
Source: node-uuid
Binary: libjs-node-uuid node-node-uuid
Architecture: source all
Version: 1.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 libjs-node-uuid - simple and fast RFC4122 UUID generation - JavaScript library
 node-node-uuid - simple and fast RFC4122 UUID generation - Node.js module
Closes: 887069
Changes:
 node-uuid (1.4.7-2) unstable; urgency=medium
 .
   * Fix symlink.
 Closes: Bug#887069. Thanks to Pirate Praveen and others.
Checksums-Sha1:
 a6bc09f447dd6536f7de450995724f99236294c5 2022 node-uuid_1.4.7-2.dsc
 1895c5da43ccb5fa2f5c32fe417149aa3798ae54 4956 node-uuid_1.4.7-2.debian.tar.xz
 32a37240157629788fd7f9ef4842d9a33df680b5 11636 libjs-node-uuid_1.4.7-2_all.deb
 902bcf2324c4a72f6a9e3f85e3eb6b37e5423371 8444 node-node-uuid_1.4.7-2_all.deb
 7d8e274bee34c74f8dc1083f4bc78b90d86a99c4 7080 node-uuid_1.4.7-2_amd64.buildinfo
Checksums-Sha256:
 e64a28c38267162f8fd8f4764ed255fb5e53f0803f40a7aa50e51b36dcf79462 2022 
node-uuid_1.4.7-2.dsc
 eda02b84daf089d1eac8eab5282fc7cc45bee17589b5bfa357979b89c057b7ff 4956 

Bug#889050: dateutils FTBFS with tzdata >= 2018b-1

[Adrian Bunk]

Source: dateutils
Version: 0.4.1-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dateutils.html

...
FAIL: dzone.007
===

$ dzone --next Asia/Singapore 2014-02-22
--- "expected output  5c83cb99" 2019-03-06 07:12:58.247403471 -1200
+++ "actual output  5c83cb99"   2019-03-06 07:12:58.247403471 -1200
@@ -1 +1 @@
-never -> never Asia/Singapore
+never -> 1901-12-15T37:42:47+08:00 Asia/Singapore
$? 1
FAIL dzone.007.clit (exit status: 1)


Testsuite summary for dateutils 0.4.1

# TOTAL: 808
# PASS:  807
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://github.com/hroptatyr/dateutils/issues

Makefile:1160: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1

Bug#889028: minissdpd: Fails to install on Debian unstable

[John Paul Adrian Glaubitz]

Source: minissdpd
Version: 1.5.20161216-1
Severity: serious
Justification: renders package unusable

Hello!

Trying to install minissdpd 1.5.20161216-1 on Debian unstable fails:

root@z6:~> apt install minissdpd
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libgltf-0.1-1 liborcus-0.12-0
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  minissdpd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/26.7 kB of archives.
After this operation, 75.8 kB of additional disk space will be used.
Selecting previously unselected package minissdpd.
(Reading database ... 637745 files and directories currently installed.)
Preparing to unpack .../minissdpd_1.5.20161216-1_amd64.deb ...
Unpacking minissdpd (1.5.20161216-1) ...
Setting up minissdpd (1.5.20161216-1) ...
Job for minissdpd.service failed because of unavailable resources or another 
system error.
See "systemctl status minissdpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript minissdpd, action "start" failed.
● minissdpd.service - keep memory of all UPnP devices that announced themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; disabled; vendor 
preset: enabled)
   Active: failed (Result: resources) since Thu 2018-02-01 11:28:53 CET; 3min 
0s ago
 Docs: man:minissdpd(1)
 Main PID: 27104 (code=exited, status=0/SUCCESS)

Feb 01 11:28:53 z6 minissdpd[15296]:   192.168.1.42/255.255.255.0, or an 
interface name such as eth0.
Feb 01 11:28:53 z6 minissdpd[15296]:   By default, socket will be open as 
/var/run/minissdpd.sock
Feb 01 11:28:53 z6 minissdpd[15296]:   and pid written to file 
/var/run/minissdpd.pid
Feb 01 11:28:53 z6 systemd[1]: minissdpd.service: Control process exited, 
code=exited status=1
Feb 01 11:28:53 z6 systemd[1]: minissdpd.service: Failed with result 
'exit-code'.
Feb 01 11:28:53 z6 systemd[1]: Failed to start keep memory of all UPnP devices 
that announced themselves.
Feb 01 11:31:53 z6 systemd[1]: minissdpd.service: Failed to load environment 
files: No such file or directory
Feb 01 11:31:53 z6 systemd[1]: minissdpd.service: Failed to run 'start' task: 
No such file or directory
Feb 01 11:31:53 z6 systemd[1]: minissdpd.service: Failed with result 
'resources'.
Feb 01 11:31:53 z6 systemd[1]: Failed to start keep memory of all UPnP devices 
that announced themselves.
dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess returned error 
exit status 1
Processing triggers for systemd (237-1) ...
Processing triggers for man-db (2.7.6.1-4) ...
Errors were encountered while processing:
 minissdpd
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@z6:~>

I don't have any particular configuration for minissdpd installed as I
never intentionally installed the package. It was installed as a recommended
package by transmission-gtk.

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

Processed: reopening 887942, forcibly merging 887069 887567 888989 887942

[Debian Bug Tracking System]

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

> reopen 887942
Bug #887942 {Done: Adrian Bunk } [node-node-uuid] 
node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling symlink
Bug reopened
Ignoring request to alter fixed versions of bug #887942 to the same values 
previously set
> forcemerge 887069 887567 888989 887942
Bug #887069 [node-node-uuid] node-node-uuid installs a broken link and making 
dependencies like npm broken
Bug #887567 [node-node-uuid] node-node-uuid: broken symlink: 
/usr/lib/nodejs/node-uuid/index.js -> 
../../../share/javascript/node-uuid/node-uuid.js
Severity set to 'grave' from 'serious'
Removed indication that 887567 affects node-sqlite3
Added indication that 887567 affects gitlab
Bug #887942 [node-node-uuid] node-node-uuid: /usr/lib/nodejs/node-uuid/index.js 
is a dangling symlink
Severity set to 'grave' from 'serious'
Removed indication that 887942 affects src:node-npmrc
Added indication that 887942 affects gitlab
Bug #888989 [node-node-uuid] Error: Cannot find module 'node-uuid'
Severity set to 'grave' from 'normal'
787774 was blocked by: 888989
787774 was blocking: 97
Removed blocking bug(s) of 787774: 888989
Removed indication that 888989 affects npm2deb
Added indication that 888989 affects gitlab
Marked as found in versions node-uuid/1.4.7-1.
Merged 887069 887567 887942 888989
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787774
887069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887069
887567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887567
887942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887942
888989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887069: marked as done (node-node-uuid installs a broken link and making dependencies like npm broken)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 12:21:31 +
with message-id 
and subject line Bug#887069: fixed in node-uuid 1.4.7-2
has caused the Debian Bug report #887069,
regarding node-node-uuid installs a broken link and making dependencies like 
npm broken
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.)


-- 
887069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: node-node-uuid
version: 1.4.7-1
severity: grave

it also breaks packages that depend on it like npm.


node -e "require('node-uuid');"
module.js:538
throw err;
^

Error: Cannot find module 'node-uuid'
at Function.Module._resolveFilename (module.js:536:15)
at Function.Module._load (module.js:466:25)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at [eval]:1:1
at ContextifyScript.Script.runInThisContext (vm.js:50:33)
at Object.runInThisContext (vm.js:139:38)
at Object. ([eval]-wrapper:6:22)
at Module._compile (module.js:635:30)
at evalScript (bootstrap_node.js:462:27)


It is installing a broken link. Adding a simple require test can find
such errors (npm2deb adds such tests by default).

ls -l /usr/lib/nodejs/node-uuid/index.js lrwxrwxrwx 1 root root 48 Jan
11 01:54 /usr/lib/nodejs/node-uuid/index.js ->
../../../share/javascript/node-uuid/node-uuid.js



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-uuid
Source-Version: 1.4.7-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-uuid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Feb 2018 13:04:59 +0100
Source: node-uuid
Binary: libjs-node-uuid node-node-uuid
Architecture: source all
Version: 1.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 libjs-node-uuid - simple and fast RFC4122 UUID generation - JavaScript library
 node-node-uuid - simple and fast RFC4122 UUID generation - Node.js module
Closes: 887069
Changes:
 node-uuid (1.4.7-2) unstable; urgency=medium
 .
   * Fix symlink.
 Closes: Bug#887069. Thanks to Pirate Praveen and others.
Checksums-Sha1:
 a6bc09f447dd6536f7de450995724f99236294c5 2022 node-uuid_1.4.7-2.dsc
 1895c5da43ccb5fa2f5c32fe417149aa3798ae54 4956 node-uuid_1.4.7-2.debian.tar.xz
 32a37240157629788fd7f9ef4842d9a33df680b5 11636 libjs-node-uuid_1.4.7-2_all.deb
 902bcf2324c4a72f6a9e3f85e3eb6b37e5423371 8444 node-node-uuid_1.4.7-2_all.deb
 7d8e274bee34c74f8dc1083f4bc78b90d86a99c4 7080 node-uuid_1.4.7-2_amd64.buildinfo
Checksums-Sha256:
 e64a28c38267162f8fd8f4764ed255fb5e53f0803f40a7aa50e51b36dcf79462 2022 
node-uuid_1.4.7-2.dsc
 eda02b84daf089d1eac8eab5282fc7cc45bee17589b5bfa357979b89c057b7ff 4956 
node-uuid_1.4.7-2.debian.tar.xz
 3c8b45ef388df2c9312f8bc92ee1ef38d4ef586efe18c3256a9d05dedc5f7bcc 11636 
libjs-node-uuid_1.4.7-2_all.deb
 6d263e65824d415b1f77c6682d7ff5cc10ce2477e5b93a56196740c675edf6e1 8444 
node-node-uuid_1.4.7-2_all.deb
 42335180847aa00e9bf1dfc9be89a66c99eaf5e04e23887fe7bc2c53eb0e2702 7080 
node-uuid_1.4.7-2_amd64.buildinfo
Files:
 221ee4b9d96932df759da604f8640eb1 2022 javascript optional node-uuid_1.4.7-2.dsc
 27e11cb66c10d0cbaf643e8b1b7d0eae 4956 javascript optional 
node-uuid_1.4.7-2.debian.tar.xz
 b723c7dc6c7a697d31c7c9db460628aa 11636 javascript optional 
libjs-node-uuid_1.4.7-2_all.deb
 3042be6273b7c473802777bd4f37b099 8444 javascript optional 
node-node-uuid_1.4.7-2_all.deb
 0089a8fc82d27796fe0ab82ca7b410b1 7080 javascript optional 
node-uuid_1.4.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlpzA9AACgkQLHwxRsGg
ASHWHRAArFsVgnvyOPagFt09dvY0QFBBgPTTwR/u37+4ewcfF9c4gYXoLy9gN+8V

Bug#887942: marked as done (node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling symlink)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 12:21:31 +
with message-id 
and subject line Bug#887069: fixed in node-uuid 1.4.7-2
has caused the Debian Bug report #887069,
regarding node-node-uuid: /usr/lib/nodejs/node-uuid/index.js is a dangling 
symlink
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.)


-- 
887069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-node-uuid
Version: 1.4.7-1
Severity: serious
Control: affects -1 src:node-npmrc

/usr/lib/nodejs/node-uuid/index.js is a dangling symlink.
--- End Message ---
--- Begin Message ---
Source: node-uuid
Source-Version: 1.4.7-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-uuid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Feb 2018 13:04:59 +0100
Source: node-uuid
Binary: libjs-node-uuid node-node-uuid
Architecture: source all
Version: 1.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 libjs-node-uuid - simple and fast RFC4122 UUID generation - JavaScript library
 node-node-uuid - simple and fast RFC4122 UUID generation - Node.js module
Closes: 887069
Changes:
 node-uuid (1.4.7-2) unstable; urgency=medium
 .
   * Fix symlink.
 Closes: Bug#887069. Thanks to Pirate Praveen and others.
Checksums-Sha1:
 a6bc09f447dd6536f7de450995724f99236294c5 2022 node-uuid_1.4.7-2.dsc
 1895c5da43ccb5fa2f5c32fe417149aa3798ae54 4956 node-uuid_1.4.7-2.debian.tar.xz
 32a37240157629788fd7f9ef4842d9a33df680b5 11636 libjs-node-uuid_1.4.7-2_all.deb
 902bcf2324c4a72f6a9e3f85e3eb6b37e5423371 8444 node-node-uuid_1.4.7-2_all.deb
 7d8e274bee34c74f8dc1083f4bc78b90d86a99c4 7080 node-uuid_1.4.7-2_amd64.buildinfo
Checksums-Sha256:
 e64a28c38267162f8fd8f4764ed255fb5e53f0803f40a7aa50e51b36dcf79462 2022 
node-uuid_1.4.7-2.dsc
 eda02b84daf089d1eac8eab5282fc7cc45bee17589b5bfa357979b89c057b7ff 4956 
node-uuid_1.4.7-2.debian.tar.xz
 3c8b45ef388df2c9312f8bc92ee1ef38d4ef586efe18c3256a9d05dedc5f7bcc 11636 
libjs-node-uuid_1.4.7-2_all.deb
 6d263e65824d415b1f77c6682d7ff5cc10ce2477e5b93a56196740c675edf6e1 8444 
node-node-uuid_1.4.7-2_all.deb
 42335180847aa00e9bf1dfc9be89a66c99eaf5e04e23887fe7bc2c53eb0e2702 7080 
node-uuid_1.4.7-2_amd64.buildinfo
Files:
 221ee4b9d96932df759da604f8640eb1 2022 javascript optional node-uuid_1.4.7-2.dsc
 27e11cb66c10d0cbaf643e8b1b7d0eae 4956 javascript optional 
node-uuid_1.4.7-2.debian.tar.xz
 b723c7dc6c7a697d31c7c9db460628aa 11636 javascript optional 
libjs-node-uuid_1.4.7-2_all.deb
 3042be6273b7c473802777bd4f37b099 8444 javascript optional 
node-node-uuid_1.4.7-2_all.deb
 0089a8fc82d27796fe0ab82ca7b410b1 7080 javascript optional 
node-uuid_1.4.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlpzA9AACgkQLHwxRsGg
ASHWHRAArFsVgnvyOPagFt09dvY0QFBBgPTTwR/u37+4ewcfF9c4gYXoLy9gN+8V
kqUbZSILXWvr4GS2P/mtJ5t+VDojA4WhErEjhRNrXX5oFSIG8as/HdIF4GVHgrwL
cI9SvUdd3VqNaNRi33xZVVxuZChQFJXOg2OlK+zU1gmKWAV2kSqSGUVOE30eEINM
MYD0p40GhgpCAsOdtxNZ7bc7vX1hp6moRDKuQLXlxszQCjrXm9V6iaMlQwE9P98T
JmRSx3zcgl+tG1Je/4B10phTtgRP/XZK3AwmADuT2ei7ve62tLOu4MXBaZQtqcWy
vxL7Mf8MOBSJWjyi9v9IJ9MDg3sKJcz2VirNJwJJnVifaQni5+h2jWjD24zgLHVV
YSna9DJ/46VuEr/q3/x67Eru0ImkQheguPYZ+0NS4DhLP4WaiDi5o72hM6kcJP1f
sSbgezndB4Lq7yV58/wSfx3/Mf01ADpGq3EtXRMKpXgEWwCU+v+g3Yg72rOM0qhh
MdTkr+kjGvTBPOsgxJ7YoO3D+Kx54ycSHEnd7CWDDovcDjDe9gS+3F2sopNyqnyY
C+LtDg59sGs3RwwK0ICUuByBhQDeOXS+f4svsJ9aymNzXlEQxMfSmSNroyZTIOwk
WL/Fi3uIiLvyW8Ppz5iwGKYVjnhMuln5aOpt20fqCEmYiBAKcDQ=
=c2NR
-END PGP SIGNATURE End Message ---

Bug#887567: marked as done (node-node-uuid: broken symlink: /usr/lib/nodejs/node-uuid/index.js -> ../../../share/javascript/node-uuid/node-uuid.js)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 12:21:31 +
with message-id 
and subject line Bug#887069: fixed in node-uuid 1.4.7-2
has caused the Debian Bug report #887069,
regarding node-node-uuid: broken symlink: /usr/lib/nodejs/node-uuid/index.js -> 
../../../share/javascript/node-uuid/node-uuid.js
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.)


-- 
887069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-node-uuid
Version: 1.4.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + node-sqlite3

Hi,

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

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

0m34.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/nodejs/node-uuid/index.js -> 
../../../share/javascript/node-uuid/node-uuid.js


libjs-node-uuid only ships /usr/share/javascript/node-uuid/uuid.js


cheers,

Andreas


node-sqlite3_3.1.8+ds1-2+b2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-uuid
Source-Version: 1.4.7-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-uuid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Feb 2018 13:04:59 +0100
Source: node-uuid
Binary: libjs-node-uuid node-node-uuid
Architecture: source all
Version: 1.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 libjs-node-uuid - simple and fast RFC4122 UUID generation - JavaScript library
 node-node-uuid - simple and fast RFC4122 UUID generation - Node.js module
Closes: 887069
Changes:
 node-uuid (1.4.7-2) unstable; urgency=medium
 .
   * Fix symlink.
 Closes: Bug#887069. Thanks to Pirate Praveen and others.
Checksums-Sha1:
 a6bc09f447dd6536f7de450995724f99236294c5 2022 node-uuid_1.4.7-2.dsc
 1895c5da43ccb5fa2f5c32fe417149aa3798ae54 4956 node-uuid_1.4.7-2.debian.tar.xz
 32a37240157629788fd7f9ef4842d9a33df680b5 11636 libjs-node-uuid_1.4.7-2_all.deb
 902bcf2324c4a72f6a9e3f85e3eb6b37e5423371 8444 node-node-uuid_1.4.7-2_all.deb
 7d8e274bee34c74f8dc1083f4bc78b90d86a99c4 7080 node-uuid_1.4.7-2_amd64.buildinfo
Checksums-Sha256:
 e64a28c38267162f8fd8f4764ed255fb5e53f0803f40a7aa50e51b36dcf79462 2022 
node-uuid_1.4.7-2.dsc
 eda02b84daf089d1eac8eab5282fc7cc45bee17589b5bfa357979b89c057b7ff 4956 
node-uuid_1.4.7-2.debian.tar.xz
 3c8b45ef388df2c9312f8bc92ee1ef38d4ef586efe18c3256a9d05dedc5f7bcc 11636 
libjs-node-uuid_1.4.7-2_all.deb
 6d263e65824d415b1f77c6682d7ff5cc10ce2477e5b93a56196740c675edf6e1 8444 
node-node-uuid_1.4.7-2_all.deb
 42335180847aa00e9bf1dfc9be89a66c99eaf5e04e23887fe7bc2c53eb0e2702 7080 
node-uuid_1.4.7-2_amd64.buildinfo
Files:
 221ee4b9d96932df759da604f8640eb1 2022 javascript optional node-uuid_1.4.7-2.dsc
 27e11cb66c10d0cbaf643e8b1b7d0eae 4956 javascript optional 
node-uuid_1.4.7-2.debian.tar.xz
 b723c7dc6c7a697d31c7c9db460628aa 11636 javascript optional 
libjs-node-uuid_1.4.7-2_all.deb
 3042be6273b7c473802777bd4f37b099 8444 javascript optional 
node-node-uuid_1.4.7-2_all.deb
 0089a8fc82d27796fe0ab82ca7b410b1 7080 javascript optional 
node-uuid_1.4.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlpzA9AACgkQLHwxRsGg
ASHWHRAArFsVgnvyOPagFt09dvY0QFBBgPTTwR/u37+4ewcfF9c4gYXoLy9gN+8V
kqUbZSILXWvr4GS2P/mtJ5t+VDojA4WhErEjhRNrXX5oFSIG8as/HdIF4GVHgrwL
cI9SvUdd3VqNaNRi33xZVVxuZChQFJXOg2OlK+zU1gmKWAV2kSqSGUVOE30eEINM
MYD0p40GhgpCAsOdtxNZ7bc7vX1hp6moRDKuQLXlxszQCjrXm9V6iaMlQwE9P98T
JmRSx3zcgl+tG1Je/4B10phTtgRP/XZK3AwmADuT2ei7ve62tLOu4MXBaZQtqcWy
vxL7Mf8MOBSJWjyi9v9IJ9MDg3sKJcz2VirNJwJJnVifaQni5+h2jWjD24zgLHVV
YSna9DJ/46VuEr/q3/x67Eru0ImkQheguPYZ+0NS4DhLP4WaiDi5o72hM6kcJP1f

Bug#882540: marked as done (libnfs FTBFS with glibc 2.25)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 10:43:14 +
with message-id 
and subject line Bug#882540: fixed in libnfs 1.11.0-3
has caused the Debian Bug report #882540,
regarding libnfs FTBFS with glibc 2.25
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.)


-- 
882540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnfs
Version: 1.11.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnfs.html

...
libnfs.c: In function 'specdata3_to_rdev':
libnfs.c:1777:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
  return makedev(rdev->specdata1, rdev->specdata2);
 ^~ 



   
libnfs.c: In function 'nfs_mknod_async':
libnfs.c:3664:13: error: In the GNU C Library, "major" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "major", include 
 directly. If you did not intend to use a system-defined macro
 "major", you should undefine it after including . [-Werror]
  cb_data->major = major(dev);
 ^  



 
libnfs.c:3665:13: error: In the GNU C Library, "minor" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "minor", include 
 directly. If you did not intend to use a system-defined macro
 "minor", you should undefine it after including . [-Werror]
  cb_data->minor = minor(dev);
 ^
--- End Message ---
--- Begin Message ---
Source: libnfs
Source-Version: 1.11.0-3

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated libnfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Feb 2018 11:00:46 +0100
Source: libnfs
Binary: libnfs-dev libnfs8
Architecture: source
Version: 1.11.0-3
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Balint Reczey 
Description:
 libnfs-dev - NFS client library (development files)
 libnfs8- NFS client library (shared library)
Closes: 882540
Changes:
 libnfs (1.11.0-3) unstable; urgency=medium
 .
   * Include sys/sysmacros.h on platforms that have it to fix FTBFS
 (Closes: #882540)
   * Use my @ubuntu.com email address in Maintainer field
Checksums-Sha1:
 69be7628e680ffc10bbf8894364472a88bafea9e 1992 libnfs_1.11.0-3.dsc
 44c3ee49f6312eeb97e894d9571c709efcc789fb 8376 libnfs_1.11.0-3.debian.tar.xz
 5a81c4b601845b5a242dd31370c90684a0a5a911 6316 libnfs_1.11.0-3_source.buildinfo
Checksums-Sha256:
 c4ec2dcb2c48c35a5143ad6f08394c53fd08266311fefa89786af94e7802a001 1992 
libnfs_1.11.0-3.dsc
 ccb57784bbb6eec0b8f9985a494c74da71a3052ed805664ea2cbaa51f439c863 8376 
libnfs_1.11.0-3.debian.tar.xz
 e240bfd82c6090e052f7ab5c9dee4430a8518ef28d6d09433070c0d774cad69f 6316 
libnfs_1.11.0-3_source.buildinfo
Files:
 

Processed: Re: ruby2.3: ruby2.3_2.3.1-5 does not build with latest gdbm

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #832020 [src:ruby2.3] ruby2.3: ruby2.3_2.3.1-5 does not build with latest 
gdbm
Severity set to 'serious' from 'important'

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

Bug#888953: gobby accesses the network during the build

[Philipp Kern]

On 2018-02-01 11:38, Simon McVittie wrote:

On Thu, 01 Feb 2018 at 11:23:28 +0200, Adrian Bunk wrote:

On Wed, Jan 31, 2018 at 03:53:11PM +0100, Matthias Klose wrote:
> While seen on a launchpad build, it looks like a missing build dependency,
> because it tries to access the docbookx.dtd from the network:


My understanding is that it's currently up to the package being built
(e.g. gobby, not gnome-doc-utils) to build-depend on the appropriate
package to get the DTDs of its XML documentation to be registered
in the xml-core catalog and available without hitting the network:
docbook-xml for docbookx.dtd, rarian-compat for scrollkeeper-omf.dtd,
and possibly others.


I'll note that I was told to stop build-depending on rarian-compat in 
#885642, which then introduced this bug.


[...]
(For context, Scrollkeeper is very obsolete, rarian-compat is an 
obsolete

compatibility shim for Scrollkeeper, and gnome-doc-utils has itself
been superseded by yelp-tools; it's deprecations all the way down. I've
asked the ftp team to override gnome-doc-utils from gnome to oldlibs,
and pushed a better package description to gnome-team git for inclusion
in the next upload.)


Well, I suppose it'd help if there would be some guidance on how to do 
things today. I'm (somewhat) happy to fix it upstream if needed.


Kind regards and thanks
Philipp Kern

Bug#885753: marked as done (network-manager-strongswan: Drop Build-Depends on libgnomeui)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 13:35:10 +
with message-id 
and subject line Bug#885753: fixed in network-manager-strongswan 1.4.2-2
has caused the Debian Bug report #885753,
regarding network-manager-strongswan: Drop Build-Depends on libgnomeui
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.)


-- 
885753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-strongswan
Version: 1.4.2-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package build-depends on libgnomeui-dev but this shouldn't be
needed anymore. (No patch attached but this should be a trivial fix.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: network-manager-strongswan
Source-Version: 1.4.2-2

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

Debian distribution maintenance software
pp.
Harald Dunkel  (supplier of updated network-manager-strongswan 
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, 27 Jan 2018 06:08:36 +0100
Source: network-manager-strongswan
Binary: network-manager-strongswan
Architecture: source
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Harald Dunkel 
Changed-By: Harald Dunkel 
Description:
 network-manager-strongswan - network management framework (strongSwan plugin)
Closes: 885753
Changes:
 network-manager-strongswan (1.4.2-2) unstable; urgency=medium
 .
   * drop build-depends upon libgnomeui-dev (Closes: #885753)
   * use https in debian/{copyright,nm-strongswan-service.conf}
Checksums-Sha1:
 a7cfc4dbc5e6b0c4e3c75a9fde28de3cf4f5ca62 1966 
network-manager-strongswan_1.4.2-2.dsc
 3b42b240fff098877f84d967a1512afc2aa480a5 2788 
network-manager-strongswan_1.4.2-2.debian.tar.xz
Checksums-Sha256:
 2f4959f389aac419a1e5200c9db5bce99c86fb39ba0b64b829404b24edeef5ae 1966 
network-manager-strongswan_1.4.2-2.dsc
 12c917b3950119a1067af0f8954338d31826c64588157c2de22ae500f946eee8 2788 
network-manager-strongswan_1.4.2-2.debian.tar.xz
Files:
 2bdefa952004be53b6093b89d2c2a056 1966 net extra 
network-manager-strongswan_1.4.2-2.dsc
 41653f5447c21c5acc8c8209308dfbe0 2788 net extra 
network-manager-strongswan_1.4.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAlpzE+sACgkQ4+M5I0i1
DTnuoQf/TScht7eDS4bWAYRjiT4CSFiMBT7e7zveHY7xibxmz72H5RBbzaCSejfO
jOb3Ljqw6p+R+OgQIH4fVupi9SqeNRmFxftnfj9FKWt2JCgIouJaa7AzPjdYogmZ
FSE71mmGInLAVRlkKpN3kaAmZfAYRWxpRXgtFO09oQxNIZUYIx+3owCUg59GSuKS
NsBYdByTsB6U+jaFp/FZI3y6xLtuB5PhFt+Vj9/GYtW/1F8ojHENY/ZJHM8BGitk
uE6B7oQXBkgx3ZmEYibrOUQKLRrllFm2WFQNAESHAM9FcbZ1Chhe71BYjbQ0pFP2
MPLx6eOc9aJPnGfHZsyIlrGrk4hMEw==
=GBNr
-END PGP SIGNATURE End Message ---

Processed: bump ruby2.5 to severity serious

[Debian Bug Tracking System]

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

> severity 888117 serious
Bug #888117 [src:ruby-beautify] ruby-beautify: FTBFS on ruby2.5: tests fail: .. 
got: "EXPR_BEG
Severity set to 'serious' from 'important'
> severity 888118 serious
Bug #888118 [src:homesick] homesick: FTBFS on ruby2.5: test fail: got: 
("GEM_SKIP")
Severity set to 'serious' from 'important'
> severity 888119 serious
Bug #888119 [src:ruby-awesome-print] ruby-awesome-print: FTBFS on ruby2.5: test 
failure: colorization default
Severity set to 'serious' from 'important'
> severity 888120 serious
Bug #888120 [src:ruby-dalli] ruby-dalli: FTBFS on ruby2.5: "File does not 
exist:"
Severity set to 'serious' from 'important'
> severity 888121 serious
Bug #888121 [src:ruby-delayed-job-active-record] 
ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined 
method `yaml_as'
Severity set to 'serious' from 'important'
> severity 888123 serious
Bug #888123 [src:ruby-crack] ruby-crack: FTBFS on ruby2.5: uninitialized 
constant SafeYAML::Parse::Date::DateTime
Severity set to 'serious' from 'important'
> severity 888124 serious
Bug #888124 [src:ruby-fakeweb] ruby-fakeweb: FTBFS on ruby2.5: undefined method 
`close' for #
Severity set to 'serious' from 'important'
> severity 888127 serious
Bug #888127 [src:ruby-grape-entity] ruby-grape-entity: FTBFS on ruby2.5: syntax 
error, unexpected '{'
Severity set to 'serious' from 'important'
> severity 888129 serious
Bug #888129 [src:ruby-json-spec] ruby-json-spec: FTBFS on ruby2.5: 
Fixnum/Integer
Severity set to 'serious' from 'important'
> severity 888130 serious
Bug #888130 [src:ruby-net-http-persistent] ruby-net-http-persistent: FTBFS on 
ruby2.5: ssl verification fails
Severity set to 'serious' from 'important'
> severity 888131 serious
Bug #888131 [src:ruby-oj] ruby-oj: FTBFS on ruby2.5: too many arguments to 
function 'rb_struct_ptr'
Severity set to 'serious' from 'important'
> severity 888132 serious
Bug #888132 [src:ruby-state-machines-activerecord] 
ruby-state-machines-activerecord: FTBFS on ruby2.5: "File does not exist:"
Severity set to 'serious' from 'important'
> severity 888135 serious
Bug #888135 [src:ruby-lapack] ruby-lapack: FTBFS on ruby2.5: `dirname': no 
implicit conversion of nil into String
Severity set to 'serious' from 'important'
> severity 888145 serious
Bug #888145 [src:r10k] r10k: FTBFS on ruby2.5: undefined method `features' for 
Rugged:Module
Severity set to 'serious' from 'important'
> severity 888146 serious
Bug #888146 [src:ruby-autoparse] ruby-autoparse: FTBFS on ruby2.5: undefined 
method `[]' for 3.14:Float
Severity set to 'serious' from 'important'
> severity 888147 serious
Bug #888147 [src:ruby-backports] ruby-backports: FTBFS on ruby2.5: tests: 
encoding change
Severity set to 'serious' from 'important'
> severity 888148 serious
Bug #888148 [src:ruby-certificate-authority] ruby-certificate-authority: FTBFS 
on ruby2.5: CSR varies?
Severity set to 'serious' from 'important'
> severity 888149 serious
Bug #888149 [src:ruby-escape-utils] ruby-escape-utils: FTBFS on ruby2.5: 
property file encoding: UTF-8
Severity set to 'serious' from 'important'
> severity 888150 serious
Bug #888150 [src:ruby-graphviz] ruby-graphviz: FTBFS on ruby2.5:  undefined 
method `graph' for nil
Severity set to 'serious' from 'important'
> severity 888151 serious
Bug #888151 [src:ruby-logging] ruby-logging: FTBFS on ruby2.5: warning: 
constant ::Fixnum is deprecated
Severity set to 'serious' from 'important'
> severity 888160 serious
Bug #888160 [src:ruby-memfs] ruby-memfs: FTBFS on ruby2.5: No such file or 
directory - /test-file
Severity set to 'serious' from 'important'
> severity 888161 serious
Bug #888161 [src:ruby-multimap] ruby-multimap: FTBFS on ruby2.5: error: void 
value not ignored as it ought to be
Severity set to 'serious' from 'important'
> severity 888163 serious
Bug #888163 [src:ruby-net-ssh] ruby-net-ssh: FTBFS on ruby2.5: 
OpenSSL::Digest::DSS1
Severity set to 'serious' from 'important'
> severity 888164 serious
Bug #888164 [src:ruby-packable] ruby-packable: FTBFS on ruby2.5: Illegal seek @ 
rb_io_tell
Severity set to 'serious' from 'important'
> severity 888165 serious
Bug #888165 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS on ruby2.5: 
OpenSSL::ASN1::ASN1Error: oid exists
Severity set to 'serious' from 'important'
> severity 888166 serious
Bug #888166 [src:ruby-rabl] ruby-rabl: FTBFS on ruby2.5: BSON:Module serialize
Severity set to 'serious' from 'important'
> severity 888167 serious
Bug #888167 [src:ruby-recursive-open-struct] ruby-recursive-open-struct: FTBFS 
on ruby2.5:  indifferent access overwriting values
Severity set to 'serious' from 'important'
> severity 888168 serious
Bug #888168 [src:ruby-redcarpet] ruby-redcarpet: FTBFS on ruby2.5: incompatible 
library version
Severity set to 'serious' from 'important'
> severity 888170 serious
Bug #888170 [src:ruby-redcloth] ruby-redcloth: FTBFS on ruby2.5: undefined 
method `load_documents' for 

Processed: forcibly merging 887069 888989

[Debian Bug Tracking System]

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

> forcemerge 887069 888989
Bug #887069 [node-node-uuid] node-node-uuid installs a broken link and making 
dependencies like npm broken
Bug #887567 [node-node-uuid] node-node-uuid: broken symlink: 
/usr/lib/nodejs/node-uuid/index.js -> 
../../../share/javascript/node-uuid/node-uuid.js
Bug #887942 [node-node-uuid] node-node-uuid: /usr/lib/nodejs/node-uuid/index.js 
is a dangling symlink
Bug #888989 [node-node-uuid] Error: Cannot find module 'node-uuid'
Bug #887567 [node-node-uuid] node-node-uuid: broken symlink: 
/usr/lib/nodejs/node-uuid/index.js -> 
../../../share/javascript/node-uuid/node-uuid.js
Bug #887942 [node-node-uuid] node-node-uuid: /usr/lib/nodejs/node-uuid/index.js 
is a dangling symlink
Bug #888989 [node-node-uuid] Error: Cannot find module 'node-uuid'
Merged 887069 887567 887942 888989
> thanks
Stopping processing here.

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

Bug#888929: Bug #888929 in libetonyek marked as pending

[rene]

Control: tag -1 pending

Hello,

Bug #888929 in libetonyek reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/libreoffice-team/document-liberation/libetonyek/commit/7632232b74bd37536383033f4e99cbcc94a09483


define -DGLM_ENABLE_EXPERIMENTAL in src/test/Makefile.in to fix test build with 
glm 0.9.9 (closes: #888929)



(this message was generated automatically)
-- 
Greetings

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 889070 buster sid
Bug #889070 [src:am-utils] am-utils silently drops gdbm support with 
libgdbm-dev 1.14.1-2
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#889006: [debhelper-devel] Bug#889006: dh-autoreconf is run before patching

[Niels Thykier]

Sven Joachim:
> [ CC'ing dpatch maintainer. ]
> 
> On 2018-02-01 08:56 +0200, Adrian Bunk wrote:
> 
>> [...]
> 
> The dansguardian package uses dpatch:
> 
> ,
> | %:
> | dh $@ --with dpatch,autotools_dev,autoreconf
> `
> 
> And /usr/share/perl5/Debian/Debhelper/Sequence/dpatch.pm has this line:
> 
> insert_before("dh_auto_configure", "dh_dpatch_patch");
> 
> I think this should be changed to
> 
> insert_before("dh_update_autotools_config", "dh_dpatch_patch");
> 
> as is the case in quilt.pm (since quilt 0.63-8.2).  Haven't tested it,
> though.
> 
> Cheers,
>Sven
> 

Hi Sven,

Thanks for forwarding the issue to dpatch.

Indeed, from my PoV we would ideally fix this issue in dpatch.  However,
we need to handle backports as well and that puts quilt back the table
as well.  I am not quite sure that I want to backport quilt and dpatch
to provide further debhelper backports.

Thanks,
~Niels

Bug#879516: marked as done (rrdtool: Mailing list rejects mail from debian BTS)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 19:55:09 +0100
with message-id <2366324.AxaTdXOcqz@deimos>
and subject line Re: Bug#879516: rrdtool: Mailing list rejects mail from debian 
BTS
has caused the Debian Bug report #879516,
regarding rrdtool: Mailing list rejects mail from debian BTS
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.)


-- 
879516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rrdtool
Severity: serious
Justification: Policy 3.3 

As per policy:
The email address given in the Maintainer control field must accept
mail from those role accounts in Debian used to send automated mails
regarding the package. 

See attached original email. It seems so that the signing a email with
the GPG key does cause the rejection, but I did not check if this was
the cause. It happened when reporting bug #879511.

--
tobi--- Begin Message ---
The message's content type was not explicitly allowed

--- Begin Message ---
Source: rrdtool
Version: 1.6.0-1
Severity: minor

Sebastian Harl  wishes no longer to be uploader of rrdtool.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.


signature.asc
Description: PGP signature
--- End Message ---
--- End Message ---
--- End Message ---
--- Begin Message ---
Hi Tobias

I added multipart/signed to the list of authorized content-types at
https://lists.alioth.debian.org/mailman/admin/pkg-rrdtool-maint/contentfilter

Previous (default) content types were only:
multipart/mixed
multipart/alternative
text/plain

That should do the trick.

Thank you for repporting the issue!

Cheers

On Sunday, 22 October 2017 15:27:25 CET you wrote:
> Package: rrdtool
> Severity: serious
> Justification: Policy 3.3
> 
> As per policy:
> The email address given in the Maintainer control field must accept
> mail from those role accounts in Debian used to send automated mails
> regarding the package.
> 
> See attached original email. It seems so that the signing a email with
> the GPG key does cause the rejection, but I did not check if this was
> the cause. It happened when reporting bug #879511.
> 
> --
> tobi



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

Bug#889073: Permission denied on /run/munin/munin-node.pid

[Jörg Frings-Fürst]

Package: munin-node
Version: 2.0.34-3
Severity: grave

Hello,

on a fresh installed buster I get the message

[quote]
Initializing plugins..done.
Restarting munin-node..Created symlink /etc/systemd/system/multi-
user.target.wants/munin-node.service → /lib/systemd/system/munin-node.service.

Job for munin-node.service failed because a timeout was exceeded.
See "systemctl status munin-node.service" and "journalctl -xe" for details.
invoke-rc.d: initscript munin-node, action "start" failed.
● munin-node.service - Munin Node
   Loaded: loaded (/lib/systemd/system/munin-node.service; enabled; vendor
preset: enabled)
   Active: activating (auto-restart) (Result: timeout) since Thu 2018-02-01
18:59:58 CET; 11ms ago
 Docs: man:munin-node(1)
   http://munin.readthedocs.org/en/stable-2.0/reference/munin-node.html
  Process: 4460 ExecStart=/usr/sbin/munin-node $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
dpkg: Fehler beim Bearbeiten des Paketes munin-node (--configure):
 installed munin-node package post-installation script subprocess returned
error exit status 1
Trigger für systemd (237-1) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 munin-node
E: Sub-process /usr/bin/dpkg returned an error code (1)
[/quote]

Journalctl give this output:
[quote]
$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
No journal files were opened due to insufficient permissions.
jff@merkur:/data/entwicklung/linux/debian$ sudo journalctl -xe
Feb 01 18:58:21 merkur chfn[3897]: changed user 'munin' information
Feb 01 18:58:21 merkur systemd[1]: Reloading.
Feb 01 18:58:25 merkur kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 01 18:58:27 merkur systemd[1]: Reloading.
Feb 01 18:58:27 merkur systemd[1]: Reloading.
Feb 01 18:58:28 merkur systemd[1]: Reloading.
Feb 01 18:58:28 merkur systemd[1]: Starting Munin Node...
-- Subject: Unit munin-node.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit munin-node.service has begun starting up.
Feb 01 18:58:28 merkur systemd[1]: munin-node.service: Permission denied while
opening PID file or unsafe symlink chain: /run/munin/munin-node.pid
Feb 01 18:59:58 merkur systemd[1]: munin-node.service: Start operation timed
out. Terminating.
Feb 01 18:59:58 merkur systemd[1]: munin-node.service: Failed with result
'timeout'.
Feb 01 18:59:58 merkur systemd[1]: Failed to start Munin Node.
-- Subject: Unit munin-node.service has failed
[/quote]

Output of ls -l /run
[quote]
$ ls -l /run
insgesamt 32
[...]
drwxr-xr-x  2 rootroot  60 Feb  1 18:37 mount
drwxr-xr-x  2 munin   root  60 Feb  1 19:15 munin
drwxr-xr-x  2 rootroot 100 Feb  1 18:37 network
[...]
[/quote]


CU
Jörg



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

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

Versions of packages munin-node depends on:
ii  gawk1:4.1.4+dfsg-1+b1
ii  libnet-server-perl  2.008-4
ii  lsb-base9.20170808
ii  munin-common2.0.34-3
ii  munin-plugins-core  2.0.34-3
ii  perl5.26.1-4
ii  procps  2:3.3.12-3

Versions of packages munin-node recommends:
ii  libnet-snmp-perl 6.0.1-3
ii  munin-plugins-extra  2.0.34-3

Versions of packages munin-node suggests:
pn  default-mysql-client  
pn  ethtool   
ii  hdparm9.53+ds-1
pn  libcrypt-ssleay-perl  
pn  libdbd-pg-perl
pn  liblwp-useragent-determined-perl  
pn  libnet-irc-perl   
pn  libtext-csv-xs-perl   
ii  libwww-perl   6.31-1
ii  libxml-simple-perl2.24-1
ii  lm-sensors1:3.4.0-4
ii  logtail   1.3.18
pn  munin 
pn  munin-plugins-java
pn  net-tools 
ii  python2.7.14-4
pn  ruby  
ii  smartmontools 6.5+svn4324-1

-- no debconf information

Processed: Re: Bug#871077: gnu-smalltalk: FTBFS: configure: error: Synchronization primitives not found, please use a newer compiler.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #871077 [src:gnu-smalltalk] gnu-smalltalk: FTBFS: configure: error: 
Synchronization primitives not found, please use a newer compiler.
Added tag(s) patch.

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

Bug#871077: gnu-smalltalk: FTBFS: configure: error: Synchronization primitives not found, please use a newer compiler.

[Adrian Bunk]

Control: tags -1 patch

On Sun, Aug 06, 2017 at 05:59:50PM -0400, Lucas Nussbaum wrote:
>...
> > checking for LIBFFI... yes
> > checking for sigsegv_install_handler in -lsigsegv... no
> > 
> > Platform environment:
> > checking whether the host supports __sync_fetch_and_add... no
> > configure: error: Synchronization primitives not found, please use a newer 
> > compiler.
> > debian/rules:16: recipe for target 'configure-stamp' failed
>...

The actual error is according to config.log:
cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

Fix:

--- debian/rules.old2018-02-01 14:55:54.960603766 +
+++ debian/rules2018-02-01 14:58:04.752602528 +
@@ -8,6 +8,7 @@
 QUILT_STAMPFN = patch-stamp
 include /usr/share/quilt/quilt.make
 
+export DEB_BUILD_MAINT_OPTIONS = hardening=-format
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 

There is now also a second build failure later related to Tcl 8.6,
upstream fix for that is attached.


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

>From 84fc8a50f692624921d4233dec1a3c8796f5b5da Mon Sep 17 00:00:00 2001
From: Holger Hans Peter Freyther 
Date: Mon, 26 May 2014 07:53:05 +0200
Subject: blox: Direct usage of result is deprecated and stops working

Use Tcl_GetStringResult(interp) instead of interp->result on
newer versions of Tcl. It looks like Tcl_GetStringResult has
been present in the entire 8.0 series.

2014-05-26  Holger Hans Peter Freyther  

	* BloxTK.c: Use Tcl_GetStringResult to access the result.
---
 packages/blox/tk/BloxTK.c  | 4 ++--
 packages/blox/tk/ChangeLog | 4 
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/packages/blox/tk/BloxTK.c b/packages/blox/tk/BloxTK.c
index 2ba40b81..2f06b7f0 100644
--- a/packages/blox/tk/BloxTK.c
+++ b/packages/blox/tk/BloxTK.c
@@ -173,12 +173,12 @@ tclInit (void)
 
   if (Tcl_Init (interp) == TCL_ERROR)
 {
-  fprintf (stderr, "Tcl_Init failed: %s\n", interp->result);
+  fprintf (stderr, "Tcl_Init failed: %s\n",  Tcl_GetStringResult(interp));
   exit (1);
 }
   if (Tk_Init (interp) == TCL_ERROR)
 {
-  fprintf (stderr, "Tk_Init failed: %s\n", interp->result);
+  fprintf (stderr, "Tk_Init failed: %s\n", Tcl_GetStringResult(interp));
   exit (1);
 }
   Tcl_CreateCommand (interp, "callback", doCallback, NULL, NULL);
diff --git a/packages/blox/tk/ChangeLog b/packages/blox/tk/ChangeLog
index aefd2dcb..159b1776 100644
--- a/packages/blox/tk/ChangeLog
+++ b/packages/blox/tk/ChangeLog
@@ -1,3 +1,7 @@
+2014-05-26  Holger Hans Peter Freyther  
+
+	* BloxTK.c: Use Tcl_GetStringResult to access the result.
+
 2010-12-04  Paolo Bonzini  
 
 	* package.xml: Remove now superfluous  tags.
-- 
2.11.0

Bug#886198: marked as done (streamtuner: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 15:51:02 +
with message-id 
and subject line Bug#886198: fixed in streamtuner2 2.2.0+dfsg-1
has caused the Debian Bug report #886198,
regarding streamtuner: Depends on unmaintained pygtk
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.)


-- 
886198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: streamtuner2
Version: 2.2.0-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: streamtuner2
Source-Version: 2.2.0+dfsg-1

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

Debian distribution maintenance software
pp.
TANIGUCHI Takaki  (supplier of updated streamtuner2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Feb 2018 00:40:40 +0900
Source: streamtuner2
Binary: streamtuner2
Architecture: source all
Version: 2.2.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: TANIGUCHI Takaki 
Description:
 streamtuner2 - Browser for Internet Radio Stations
Closes: 866483 886198
Changes:
 streamtuner2 (2.2.0+dfsg-1) unstable; urgency=medium
 .
   * Migrate to Python3
 - Use python3-pil (Closes: #866483)
 - Replace python-keybinder, python-gtk2 and python-glade from Depends
   and add python3-gi to Depends. (Closes: #886198)
   * debian/compat: Update to 11.
   * debian/control: Change Priority to optional.
   * Move Vcs-* to salsa.debian.org.
   * debian/control: Drop dh-exec from B-D.
   * New upstream version 2.2.0+dfsg
   * debian/watch: Add dversionmangle option.
   * debian/rules: Set shebang manually.
Checksums-Sha1:
 554d185f45464dbfb1a78dfe420bcf7a28dc2d33 2049 streamtuner2_2.2.0+dfsg-1.dsc
 797ff4aa89089c9efac9a1145cb776d8fc2e0fa0 494808 
streamtuner2_2.2.0+dfsg.orig.tar.xz
 8b328b186b540b914322cfff855deefb3b0bf9f2 3800 
streamtuner2_2.2.0+dfsg-1.debian.tar.xz
 dc91fe2bdb7e1a4044c20632b471410df33b30c2 414872 
streamtuner2_2.2.0+dfsg-1_all.deb
 d5e0c48eabdf357caac3dfce4590b06dda4b12ae 7438 
streamtuner2_2.2.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 e9cc69bc52acb8b940f22d7037436bedd9fc2cd2e0f110b2d092243eb9046e5d 2049 
streamtuner2_2.2.0+dfsg-1.dsc
 42cf569aa04a65cf5dbed733fb9004a0b64c552cfdc9753d7e846db9d5b87d0c 494808 
streamtuner2_2.2.0+dfsg.orig.tar.xz
 9b1f85f9a7155c33f8481896f57bfa0f9243edf2e5826ffc707404e9ec973a41 3800 
streamtuner2_2.2.0+dfsg-1.debian.tar.xz
 4eb7d99b1a55c2ac78ae7d909718b43be3a95f777c74030caf4bf26eeaa03f72 414872 
streamtuner2_2.2.0+dfsg-1_all.deb
 19e7372bf28648f48de39b06a2e7e25954bbc8146817ef5bd2aa334fda4e36f2 7438 
streamtuner2_2.2.0+dfsg-1_amd64.buildinfo
Files:
 706b45697f508da3f2763d64e25dc3c9 2049 sound optional 
streamtuner2_2.2.0+dfsg-1.dsc
 b7125cd3d3d52a7c4dbb50f99242d613 494808 sound optional 
streamtuner2_2.2.0+dfsg.orig.tar.xz
 8296b43e3db49a55fa2e50837159956a 3800 sound optional 
streamtuner2_2.2.0+dfsg-1.debian.tar.xz
 d564c234ae8b2fd60e2ce35c61bdd325 414872 sound optional 
streamtuner2_2.2.0+dfsg-1_all.deb
 21643d68d6d9d907f287ffcd88038e83 7438 sound optional 
streamtuner2_2.2.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0kq/0SfNJVahPGx5zBSfbCil4lcFAlpzNdkACgkQzBSfbCil

Processed: Bug #888929 in libetonyek marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888929 [src:libetonyek] libetonyek FTBFS with libglm-dev 0.9.9~a2-1
Added tag(s) pending.

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

Bug#876611: marked as done (farstream-0.2 FTBFS with gtk-doc-tools 1.26: gtkdoc-common.pl is no longer available)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 15:50:11 +
with message-id 
and subject line Bug#876611: fixed in farstream-0.2 0.2.8-4
has caused the Debian Bug report #876611,
regarding farstream-0.2 FTBFS with gtk-doc-tools 1.26: gtkdoc-common.pl is no 
longer available
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.)


-- 
876611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: farstream-0.2
Version: 0.2.8-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/farstream-0.2.html

...
Making all in plugins
make[4]: Entering directory '/build/1st/farstream-0.2-0.2.8/docs/plugins'
  DOC   Introspecting gobjects
Can't locate gtkdoc-common.pl in @INC (@INC contains: /usr/share/gtk-doc/data 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 
/usr/local/share/perl/5.26.0 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
../../common/gstdoc-scangobj line 38.
Makefile:823: recipe for target 'scanobj-build.stamp' failed
make[4]: *** [scanobj-build.stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: farstream-0.2
Source-Version: 0.2.8-4

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated farstream-0.2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Feb 2018 16:26:57 +0100
Source: farstream-0.2
Binary: libfarstream-0.2-5 libfarstream-0.2-dev libfarstream-0.2-doc 
gir1.2-farstream-0.2
Architecture: source amd64 all
Version: 0.2.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Laurent Bigonville 
Description:
 gir1.2-farstream-0.2 - Audio/Video communications framework: 
GObject-Introspection
 libfarstream-0.2-5 - Audio/Video communications framework: core library
 libfarstream-0.2-dev - Audio/Video communications framework: development files
 libfarstream-0.2-doc - Audio/Video communications framework: documentation
Closes: 876611
Changes:
 farstream-0.2 (0.2.8-4) unstable; urgency=medium
 .
   * debian/patches/doc-update-common.patch: Fix installation of .devhelp2
 files
 .
 farstream-0.2 (0.2.8-3) unstable; urgency=medium
 .
   * debian/control: Bump Standards-Version to 4.1.3 (no further changes)
   * debian/patches/doc-update-common.patch: Update the common/ directory again
 to fix documentation build (Closes: #876611)
Checksums-Sha1:
 e204056b5ebca3313edfd0aec088fffd586d5571 2235 farstream-0.2_0.2.8-4.dsc
 e0aaa68aba17ca88184bd34ff3e2ff16e3bec826 65108 
farstream-0.2_0.2.8-4.debian.tar.xz
 43632aa1de27256f59a184f3e662785a0ff8a80f 11256 
farstream-0.2_0.2.8-4_amd64.buildinfo
 794db45247db40d1fc01fdd668b6f0f33a011d44 213496 
gir1.2-farstream-0.2_0.2.8-4_amd64.deb
 e36c8205a38aaf644c6a9cd9bc766c580a07 780748 
libfarstream-0.2-5-dbgsym_0.2.8-4_amd64.deb
 324215abc74c049ac7a3d5e3ca13c2966289ba20 397120 
libfarstream-0.2-5_0.2.8-4_amd64.deb
 be23b44610b4e3b89229aa0145806eb153bb259d 234684 
libfarstream-0.2-dev_0.2.8-4_amd64.deb
 c05e5bf8f1deb5d9ba6ade89defd7753050516b5 255408 
libfarstream-0.2-doc_0.2.8-4_all.deb
Checksums-Sha256:
 1bbb7e94f501ef092d30c6986b90d0bf4084b525df251413a98e92ea227247dd 2235 
farstream-0.2_0.2.8-4.dsc
 b9168f74e4dbd49015d6772b18ba2a2cc8007933ed9d778f0a289f9001956c60 65108 
farstream-0.2_0.2.8-4.debian.tar.xz
 7f4f1d9665d7bc7193f876095602e03840d0efc22b95b9f232f3117a43e5d0ab 11256 
farstream-0.2_0.2.8-4_amd64.buildinfo
 813734ffd71e6d2b338c26c2fb19724a690529681b20c3db910743a5f50a338d 213496 
gir1.2-farstream-0.2_0.2.8-4_amd64.deb
 48a552e96d7b279672219d910af1370bdd7bc1a601ea83872204a4547574b7b6 780748 
libfarstream-0.2-5-dbgsym_0.2.8-4_amd64.deb
 

Bug#884197: marked as done (php-apcu-bc FTBFS: php_apc.c:34:10: fatal error: ext/apcu/php_apc.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 1 Feb 2018 16:51:42 +0100
with message-id <4e0acb51-f381-458d-bd38-d91629e64...@sury.org>
and subject line Re: [Pkg-php-pecl] Bug#884197: Bug#884197: php-apcu-bc FTBFS: 
php_apc.c:34:10: fatal error: ext/apcu/php_apc.h: No such file or directory
has caused the Debian Bug report #884197,
regarding php-apcu-bc FTBFS: php_apc.c:34:10: fatal error: ext/apcu/php_apc.h: 
No such file or directory
to be marked as done.

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

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


-- 
884197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-apcu-bc
Version: 1.0.3-2
Severity: serious

Some recent change in unstable makes php-apcu-bc FTBFS:

https://tests.reproducible-builds.org/debian/history/php-apcu-bc.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-apcu-bc.html

...
   dh_auto_build -O--sourcedirectory=apcu_bc-1.0.3
cd apcu_bc-1.0.3 && make -j1
make[1]: Entering directory '/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3'
/bin/bash /build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/libtool --mode=compile cc 
-DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I. 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -DPHP_ATOM_INC 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/include 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/main 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -I/usr/include/php/20160303 
-I/usr/include/php/20160303/main -I/usr/include/php/20160303/TSRM 
-I/usr/include/php/20160303/Zend -I/usr/include/php/20160303/ext 
-I/usr/include/php/20160303/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security   -c 
/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/php_apc.c -o php_apc.lo 
libtool: compile:  cc -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I. 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -DPHP_ATOM_INC 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/include 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/main 
-I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -I/usr/include/php/20160303 
-I/usr/include/php/20160303/main -I/usr/include/php/20160303/TSRM 
-I/usr/include/php/20160303/Zend -I/usr/include/php/20160303/ext 
-I/usr/include/php/20160303/ext/date/lib -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c /build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/php_apc.c 
 -fPIC -DPIC -o .libs/php_apc.o
/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/php_apc.c:34:10: fatal error: 
ext/apcu/php_apc.h: No such file or directory
 #include "ext/apcu/php_apc.h"
  ^~~~
compilation terminated.
Makefile:193: recipe for target 'php_apc.lo' failed
make[1]: *** [php_apc.lo] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.0.3-2+b1

Fixed with binNMU

--
Ondřej Surý
ond...@sury.org



> On 15 Dec 2017, at 15:04, Ondřej Surý  wrote:
> 
> It needs php-apc binNMU, but basically we are waiting for PHP 7.2 to hit
> unstable to schedule them all.
> 
> Ondrej
> -- 
> Ondřej Surý 
> 
> On Tue, Dec 12, 2017, at 17:23, Adrian Bunk wrote:
>> Source: php-apcu-bc
>> Version: 1.0.3-2
>> Severity: serious
>> 
>> Some recent change in unstable makes php-apcu-bc FTBFS:
>> 
>> https://tests.reproducible-builds.org/debian/history/php-apcu-bc.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-apcu-bc.html
>> 
>> ...
>>   dh_auto_build -O--sourcedirectory=apcu_bc-1.0.3
>>  cd apcu_bc-1.0.3 && make -j1
>> make[1]: Entering directory '/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3'
>> /bin/bash /build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/libtool
>> --mode=compile cc -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I.
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -DPHP_ATOM_INC
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/include
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/main
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -I/usr/include/php/20160303
>> -I/usr/include/php/20160303/main -I/usr/include/php/20160303/TSRM
>> -I/usr/include/php/20160303/Zend -I/usr/include/php/20160303/ext
>> -I/usr/include/php/20160303/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2
>> -DHAVE_CONFIG_H  -g -O2 -fstack-protector-strong -Wformat
>> -Werror=format-security   -c
>> /build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/php_apc.c -o php_apc.lo 
>> libtool: compile:  cc -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I.
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3 -DPHP_ATOM_INC
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/include
>> -I/build/1st/php-apcu-bc-1.0.3/apcu_bc-1.0.3/main
>> 

Bug#866483: marked as done (streamtuner2: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 15:51:02 +
with message-id 
and subject line Bug#866483: fixed in streamtuner2 2.2.0+dfsg-1
has caused the Debian Bug report #866483,
regarding streamtuner2: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
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.)


-- 
866483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:streamtuner2
Version: 2.2.0-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: streamtuner2
Source-Version: 2.2.0+dfsg-1

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

Debian distribution maintenance software
pp.
TANIGUCHI Takaki  (supplier of updated streamtuner2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Feb 2018 00:40:40 +0900
Source: streamtuner2
Binary: streamtuner2
Architecture: source all
Version: 2.2.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: TANIGUCHI Takaki 
Description:
 streamtuner2 - Browser for Internet Radio Stations
Closes: 866483 886198
Changes:
 streamtuner2 (2.2.0+dfsg-1) unstable; urgency=medium
 .
   * Migrate to Python3
 - Use python3-pil (Closes: #866483)
 - Replace python-keybinder, python-gtk2 and python-glade from Depends
   and add python3-gi to Depends. (Closes: #886198)
   * debian/compat: Update to 11.
   * debian/control: Change Priority to optional.
   * Move Vcs-* to salsa.debian.org.
   * debian/control: Drop dh-exec from B-D.
   * New upstream version 2.2.0+dfsg
   * debian/watch: Add dversionmangle option.
   * debian/rules: Set shebang manually.
Checksums-Sha1:
 554d185f45464dbfb1a78dfe420bcf7a28dc2d33 2049 streamtuner2_2.2.0+dfsg-1.dsc
 797ff4aa89089c9efac9a1145cb776d8fc2e0fa0 494808 
streamtuner2_2.2.0+dfsg.orig.tar.xz
 8b328b186b540b914322cfff855deefb3b0bf9f2 3800 
streamtuner2_2.2.0+dfsg-1.debian.tar.xz
 dc91fe2bdb7e1a4044c20632b471410df33b30c2 414872 
streamtuner2_2.2.0+dfsg-1_all.deb
 d5e0c48eabdf357caac3dfce4590b06dda4b12ae 7438 
streamtuner2_2.2.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 e9cc69bc52acb8b940f22d7037436bedd9fc2cd2e0f110b2d092243eb9046e5d 2049 
streamtuner2_2.2.0+dfsg-1.dsc
 42cf569aa04a65cf5dbed733fb9004a0b64c552cfdc9753d7e846db9d5b87d0c 494808 
streamtuner2_2.2.0+dfsg.orig.tar.xz
 9b1f85f9a7155c33f8481896f57bfa0f9243edf2e5826ffc707404e9ec973a41 3800 
streamtuner2_2.2.0+dfsg-1.debian.tar.xz
 4eb7d99b1a55c2ac78ae7d909718b43be3a95f777c74030caf4bf26eeaa03f72 414872 
streamtuner2_2.2.0+dfsg-1_all.deb
 19e7372bf28648f48de39b06a2e7e25954bbc8146817ef5bd2aa334fda4e36f2 7438 
streamtuner2_2.2.0+dfsg-1_amd64.buildinfo
Files:
 706b45697f508da3f2763d64e25dc3c9 2049 sound optional 
streamtuner2_2.2.0+dfsg-1.dsc
 b7125cd3d3d52a7c4dbb50f99242d613 494808 sound optional 
streamtuner2_2.2.0+dfsg.orig.tar.xz
 8296b43e3db49a55fa2e50837159956a 3800 sound optional 
streamtuner2_2.2.0+dfsg-1.debian.tar.xz
 d564c234ae8b2fd60e2ce35c61bdd325 414872 sound optional 
streamtuner2_2.2.0+dfsg-1_all.deb
 21643d68d6d9d907f287ffcd88038e83 7438 sound optional 
streamtuner2_2.2.0+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0kq/0SfNJVahPGx5zBSfbCil4lcFAlpzNdkACgkQzBSfbCil
4ldkzg//VYXvCqXHLAZ+4prqoZgmQTmyRT3i5zvGdF1Wm9rLTYAUbU6k1ge96WkY
GFrZD1cO4cHIGblJ2gRdN938E+kgUiqrla41xn+hZEKZ4xAl08iMt/DCNvgyv/1H

Bug#889006: dh-autoreconf is run before patching

[Sven Joachim]

[ CC'ing dpatch maintainer. ]

On 2018-02-01 08:56 +0200, Adrian Bunk wrote:

> Package: debhelper,dh-autoreconf
> Severity: serious
> Control: found -1 16
> Control: affects -1 src:dansguardian
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dansguardian.html
>
> ...
>dh_autoreconf
> configure.ac:14: installing './compile'
> src/Makefile.am:13: warning: source file 'contentscanners/clamav.cpp' is in a 
> subdirectory,
> src/Makefile.am:13: but option 'subdir-objects' is disabled
> automake: warning: possible forward-incompatibility.
> automake: At least a source file is in a subdirectory, but the 
> 'subdir-objects'
> automake: automake option hasn't been enabled.  For now, the corresponding 
> output
> automake: object file(s) will be placed in the top-level directory.  However,
> automake: this behaviour will change in future Automake versions: they will
> automake: unconditionally cause object files to be placed in the same 
> subdirectory
> automake: of the corresponding sources.
> automake: You are advised to start using 'subdir-objects' option throughout 
> your
> automake: project, to avoid future incompatibilities.
> src/Makefile.am:31: warning: source file 'contentscanners/icapscan.cpp' is in 
> a subdirectory,
> src/Makefile.am:31: but option 'subdir-objects' is disabled
> src/Makefile.am:39: warning: source file 'contentscanners/kavdscan.cpp' is in 
> a subdirectory,
> src/Makefile.am:39: but option 'subdir-objects' is disabled
> src/Makefile.am:25: warning: source file 'contentscanners/clamdscan.cpp' is 
> in a subdirectory,
> src/Makefile.am:25: but option 'subdir-objects' is disabled
> src/Makefile.am:43: warning: source file 
> 'contentscanners/commandlinescan.cpp' is in a subdirectory,
> src/Makefile.am:43: but option 'subdir-objects' is disabled
> src/Makefile.am:48: warning: source file 'downloadmanagers/default.cpp' is in 
> a subdirectory,
> src/Makefile.am:48: but option 'subdir-objects' is disabled
> src/Makefile.am:53: warning: source file 'downloadmanagers/fancy.cpp' is in a 
> subdirectory,
> src/Makefile.am:53: but option 'subdir-objects' is disabled
> src/Makefile.am:57: warning: source file 'downloadmanagers/trickle.cpp' is in 
> a subdirectory,
> src/Makefile.am:57: but option 'subdir-objects' is disabled
> src/Makefile.am:62: warning: source file 'authplugins/proxy.cpp' is in a 
> subdirectory,
> src/Makefile.am:62: but option 'subdir-objects' is disabled
> src/Makefile.am:63: warning: source file 'authplugins/ident.cpp' is in a 
> subdirectory,
> src/Makefile.am:63: but option 'subdir-objects' is disabled
> src/Makefile.am:64: warning: source file 'authplugins/ip.cpp' is in a 
> subdirectory,
> src/Makefile.am:64: but option 'subdir-objects' is disabled
> src/Makefile.am:70: warning: source file 'authplugins/ntlm.cpp' is in a 
> subdirectory,
> src/Makefile.am:70: but option 'subdir-objects' is disabled
> src/Makefile.am:65: warning: source file 'authplugins/digest.cpp' is in a 
> subdirectory,
> src/Makefile.am:65: but option 'subdir-objects' is disabled
>dh_dpatch_patch
> applying patch 03_add_unconfigures to ./ ... ok.
> applying patch 07_fix_config_paths to ./ ... ok.
> applying patch 11_FixOptionContainer.cpp_on_arm to ./ ... ok.
> applying patch 50_clamav095_support to ./ ... ok.
> applying patch 60_add_gcc4.4_support to ./ ... ok.
> applying patch 65-fix_clamdsocket to ./ ... ok.
> applying patch 70-gcc4.6 to ./ ... ok.
> applying patch 70_fix_clamav_detection to ./ ... ok.
> applying patch 80_fix_libcre3_max_sub_expression_allocation to ./ ... ok.
> ...
> checking for CLAMAV... no
> configure: error: Package requirements (libclamav >= 4) were not met:
>
> Requested 'libclamav >= 4' but version of libclamav is 0.99.3-beta2
>
>
> This is caused by:
>
>
> dh-autoreconf (16) unstable; urgency=medium
> ...
>   * Run dh_autoreconf after dh_update_autotools_config,
> not before dh_auto_configure

The dansguardian package uses dpatch:

,
| %:
|   dh $@ --with dpatch,autotools_dev,autoreconf
`

And /usr/share/perl5/Debian/Debhelper/Sequence/dpatch.pm has this line:

insert_before("dh_auto_configure", "dh_dpatch_patch");

I think this should be changed to

insert_before("dh_update_autotools_config", "dh_dpatch_patch");

as is the case in quilt.pm (since quilt 0.63-8.2).  Haven't tested it,
though.

Cheers,
   Sven

Bug#889062: FTBFS

[Thomas Goirand]

Package: swift-im
Version: 3.0.4-1
Severity: serious

Hi,

I've rebuilt all reverse build dependency for libminiupnpc-dev, which
I intend to upload to Sid after it clears the NEW queue and I get
authorization from the release team.

Rebuilding swift-im with libminiupnpc-dev 2.0.20171212 (that I have just
uploaded to Experimental) fails:

Creating 'Swift/QtUI/COPYING'
scons: *** [Swift/QtUI/COPYING] UnicodeEncodeError : 'ascii' codec can't encode 
character u'\xe7' in position 73: ordinal not in range(128)
Traceback (most recent call last):
  File "/usr/lib/scons/SCons/Action.py", line 1197, in execute
result = self.execfunction(target=target, source=rsources, env=env)
  File 
"/home/zigo/sources/miniupnp/rev-build-dep/swift-im/swift-im-3.0.4/BuildTools/SCons/Tools/textfile.py",
 line 116, in _action
fd.write(_do_subst(s, subs))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe7' in position 
73: ordinal not in range(128)
scons: building terminated because of errors.

This seems, however, to be unrelated to libminiupnpc.

Cheers,

Thomas Goirand (zigo)

Bug#878445: marked as done (streamtuner2: crashes at shoutcast-option)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 23:33:55 +0900
with message-id <87o9l8srsc.wl-tak...@asis.media-as.org>
and subject line Re: streamtuner2: crashes at shoutcast-option
has caused the Debian Bug report #878445,
regarding streamtuner2: crashes at shoutcast-option
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.)


-- 
878445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: streamtuner2
Version: 2.1.9-1
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



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

Kernel: Linux 4.9.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages streamtuner2 depends on:
ii  python2.7.13-2
ii  python-glade2 2.24.0-5.1
ii  python-gtk2   2.24.0-5.1
ii  python-imaging4.0.0-4
ii  python-keybinder  0.3.1-1
ii  python-lxml   3.7.1-1
ii  python-pyquery1.2.9-2
ii  python-requests   2.12.4-1

streamtuner2 recommends no packages.

Versions of packages streamtuner2 suggests:
ii  audacious  3.7.2-1+b1
pn  totem  
ii  vlc2.2.6-1~deb9u1

-- no debconf information
Hi , I try it in english . I used streamtuner for a year on different 
debian-derivates without Problems , but since this spring it crashed on all 
installations the moment , i chosed shoutcast . So i searched alternatives and 
installed different libraries and suddenly it worked and i installed it on 
debian 9.1  too today . Here's the libraries - maybe you know the precise way : 
 libass , libdiracencoder , libgcrypt , libgnutls , librtmp , libsoundtouch , 
libvpx . 
--- End Message ---
--- Begin Message ---
This bug report does not contains any information.--- End Message ---

Bug#888929: libetonyek FTBFS with libglm-dev 0.9.9~a2-1

[Rene Engelhard]

Hi,

On Wed, Jan 31, 2018 at 11:24:47AM +0200, Adrian Bunk wrote:
> ...
> In file included from /usr/include/glm/gtx/quaternion.hpp:20:0,
>  from /usr/include/glm/gtx/io.hpp:24,
>  from IWORKTransformationTest.cpp:13:
> /usr/include/glm/gtx/norm.hpp:21:3: error: #error "GLM: GLM_GTX_norm is an 
> experimental extension and may change in the future. Use #define 
> GLM_ENABLE_EXPERIMENTAL before including it, if you really want to use it."
>  # error "GLM: GLM_GTX_norm is an experimental extension and may change in 
> the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you 
> really want to use it."
>^

The straightforward fix is

$ cat debian/patches/GLM_ENABLE_EXPERIMENTAL.diff 
diff --git a/src/test/Makefile.am b/src/test/Makefile.am
index f71ee6d..5d054c9 100644
--- a/src/test/Makefile.am
+++ b/src/test/Makefile.am
@@ -14,6 +14,7 @@ test_CPPFLAGS = \
$(CPPUNIT_CFLAGS) \
$(XML_CFLAGS) \
$(GLM_CFLAGS) \
+   -DGLM_ENABLE_EXPERIMENTAL \
$(MDDS_CFLAGS) \
$(LANGTAG_LIBS) \
$(DEBUG_CXXFLAGS)

but that causes

FAIL: test
===
   libetonyek 0.1.7: src/test/test-suite.log
===

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test
==

test::IWAFieldTest::testEmpty : OK
test::IWAFieldTest::testParse : OK
test::IWAFieldTest::testParsePacked : OK
test::IWAFieldTest::testOptional : OK
test::IWAFieldTest::testRepeated : OK
test::IWAMessageTest::testSimple : OK
test::IWAMessageTest::testNestedMessage : OK
test::IWAMessageTest::testMessageSimpleAccess : OK
test::IWAMessageTest::testMissingFields : OK
test::IWAMessageTest::testRepeated : OK
test::IWAMessageTest::testPacked : OK
test::IWAMessageTest::testInvalidInput : OK
test::IWAMessageTest::testNestedMessageWithTrailingData : OK
test::IWAMessageTest::testEmptyMessage : OK
test::IWAMessageTest::testEmptyString : OK
test::IWAReaderTest::testString : OK
test::IWAReaderTest::testBytes : OK
test::IWASnappyStreamTest::testBlock : OK
test::IWASnappyStreamTest::testInvalid : OK
test::IWASnappyStreamTest::testFull : OK
test::IWORKChainedTokenizerTest::testNormal : OK
test::IWORKChainedTokenizerTest::testQualified : OK
test::IWORKFormulaTest::testNumbers : OK
test::IWORKFormulaTest::testStrings : OK
test::IWORKFormulaTest::testCellReferences : OK
test::IWORKFormulaTest::testOperators : OK
test::IWORKFormulaTest::testFunctions : OK
test::IWORKFormulaTest::testExpressions : OK
test::IWORKFormulaTest::testInvalid : OK
test::IWORKPathTest::testConstruction : OK
test::IWORKPathTest::testConversion : OK
test::IWORKPropertyMapTest::testLookup : OK
test::IWORKPropertyMapTest::testLookupWithParent : OK
test::IWORKShapeTest::testMakePolygonPath : OK
test::IWORKShapeTest::testMakeRoundedRectanglePath : OK
test::IWORKShapeTest::testMakeArrowPath : OK
test::IWORKShapeTest::testMakeDoubleArrowPath : OK
test::IWORKShapeTest::testMakeStarPath : OK
test::IWORKShapeTest::testMakeConnectionPath : OK
test::IWORKShapeTest::testMakeCalloutPath : OK
test::IWORKShapeTest::testMakeQuoteBubblePath : OK
test::IWORKStyleTest::testLink : OK
test::IWORKStyleTest::testFlatten : OK
test::IWORKStyleTest::testLookup : OK
test::IWORKStyleStackTest::testLookup : OK
test::IWORKTokenizerBaseTest::testNormal : OK
test::IWORKTokenizerBaseTest::testQualified : OK
test::IWORKTransformationTest::testConstruction : OK
test::IWORKTransformationTest::testConstructionIdentity : assertion
test::IWORKTransformationTest::testConstructionFromGeometry : assertion
test::IWORKTransformationTest::testIdentities : OK
test::IWORKTransformationTest::testInverseOperations : assertion
test::LibetonyekUtilsTest::testReadSVar : OK
test::LibetonyekUtilsTest::testReadUVar : OK
test::IWORKLanguageManagerTest::testTagToProps : OK
test::IWORKLanguageManagerTest::testLanguageToProps : OK
IWORKTransformationTest.cpp:112:Assertion
Test name: test::IWORKTransformationTest::testConstructionIdentity
equality assertion failed
- Expected: 
[[0.000,0.000,0.000]
 [0.000,0.000,0.000]
 [0.000,0.000,0.000]]
- Actual  : 
[[1.000,0.000,0.000]
 [0.000,1.000,0.000]
 [0.000,0.000,1.000]]

IWORKTransformationTest.cpp:136:Assertion
Test name: test::IWORKTransformationTest::testConstructionFromGeometry
equality assertion failed
- Expected: 
[[1.000,0.000,0.000]
 [0.000,1.000,0.000]
 [0.000,0.000,1.000]]
- Actual  : 
[[0.000,0.000,0.000]
 [0.000,0.000,0.000]
 [0.000,0.000,0.000]]

IWORKTransformationTest.cpp:226:Assertion
Test name: test::IWORKTransformationTest::testInverseOperations
equality assertion failed
- Expected: 
[[2.000,0.000,0.000]
 [4.000,2.000,0.000]
 [1.000,0.000,2.000]]
- Actual  : 
[[1.000,0.000,

Bug#889070: am-utils silently drops gdbm support with libgdbm-dev 1.14.1-2

[Adrian Bunk]

Source: am-utils
Version: 6.2+rc20110530-3.2
Severity: serious

https://buildd.debian.org/status/package.php?p=am-utils

...
checking gdbm/ndbm.h usability... no
checking gdbm/ndbm.h presence... no
checking for gdbm/ndbm.h... no
...

Processed: bug 888929 is forwarded to David Tardon <dtar...@redhat.com>

[Debian Bug Tracking System]

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

> forwarded 888929 David Tardon 
Bug #888929 [src:libetonyek] libetonyek FTBFS with libglm-dev 0.9.9~a2-1
Set Bug forwarded-to-address to 'David Tardon '.
> thanks
Stopping processing here.

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

Bug#888297: p7zip: CVE-2017-17969: ZIP Shrink: Heap Buffer Overflow

[Antoine Beaupre]

On Fri, Jan 26, 2018 at 04:10:54PM -0500, Antoine Beaupre wrote:
> Control: tags -1 +patch
> 
> Since a fix was published in upstream 18.00-beta, I looked at the source
> there and was able to produce a simple patch for wheezy, which should be
> trivial to port to jessie and easy to port to stretch:
> 
> https://sourceforge.net/p/p7zip/bugs/_discuss/thread/0920f369/c296/attachment/CVE-2017-17969.patch
> 
> Attached as well.
> 
> Looks good?

It does not, at all, look good: that doesn't even compile...

I've submitted a new patch upstream:

https://sourceforge.net/p/p7zip/bugs/_discuss/thread/0920f369/#2de7

And will leave the discussion happening there.

This one builds, at least, and as far as I can tell, doesn't introduce
regressions in the normal code paths that I could test. I've asked the
original researcher for a reproducer to see if this fixes the issue as
well, so I'll wait a little longer for feedback before issuing an
advisory on that one.

A.


signature.asc
Description: PGP signature

Processed: tagging 888929

[Debian Bug Tracking System]

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

> tags 888929 - pending
Bug #888929 [src:libetonyek] libetonyek FTBFS with libglm-dev 0.9.9~a2-1
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#889028: minissdpd: Fails to install on Debian unstable

[Ara Keary]

Package: minissdpd
Version: 1.5.20161216-1
Followup-For: Bug #889028

Hi,

same here ; reverting to 1.2.20130907-4.1 fixes the issue.

The output of

journalctl -xe

is


Feb 01 17:48:25 host-32-141 systemd[1]: Starting keep memory of all UPnP
devices that announced themselves...
-- Subject: Unit minissdpd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit minissdpd.service has begun starting up.
Feb 01 17:48:25 host-32-141 minissdpd[15437]: Error: please specify LAN network
interface by name instead of IPv4 address : 0.0.0.0
Feb 01 17:48:25 host-32-141 minissdpd[15437]: can't parse "0.0.0.0" as a valid
address or interface name
Feb 01 17:48:25 host-32-141 minissdpd[15437]: Usage: /usr/sbin/minissdpd [-d]
[-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i  [-i
] ...
Feb 01 17:48:25 host-32-141 minissdpd[15437]:is either an IPv4
address with mask such as
Feb 01 17:48:25 host-32-141 minissdpd[15437]:   192.168.1.42/255.255.255.0, or
an interface name such as eth0.
Feb 01 17:48:25 host-32-141 minissdpd[15437]:   By default, socket will be open
as /var/run/minissdpd.sock
Feb 01 17:48:25 host-32-141 minissdpd[15437]:   and pid written to file
/var/run/minissdpd.pid
Feb 01 17:48:25 host-32-141 systemd[1]: minissdpd.service: Control process
exited, code=exited status=1
Feb 01 17:48:25 host-32-141 systemd[1]: minissdpd.service: Failed with result
'exit-code'.
Feb 01 17:48:25 host-32-141 systemd[1]: Failed to start keep memory of all UPnP
devices that announced themselves.
-- Subject: Unit minissdpd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit minissdpd.service has failed.
--
-- The result is RESULT.


Best,

Ara



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

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minissdpd depends on:
ii  libc6  2.26-6
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   9.20170808

minissdpd recommends no packages.

minissdpd suggests no packages.

-- no debconf information

Bug#889071: magicrescue silently drops gdbm support with libgdbm-dev 1.14.1-2

[Adrian Bunk]

Source: magicrescue
Version: 1.1.9-4
Severity: serious
Tags: buster sid

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

...
Checking for ndbm.h... no
...

Bug#871142: Pending fixes for bugs in the commons-httpclient package

[pkg-java-maintainers]

tag 871142 + pending
thanks

Some bugs in the commons-httpclient package are closed in revision
80c2869b6f62682a120f7c48f5fe3344c20ac620 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/commons-httpclient.git/commit/?id=80c2869

Commit message:

Fix Manifest file and add missing OSGi metadata.

Closes: #871142

Processed: Re: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.j

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 commons-httpclient
Bug #871142 [src:eclipse] eclipse: FTBFS: /<>/build.xml:413: Could 
not find suitable system JAR for 
org.apache.commons.httpclient_3.1.0.v201012070820.jar.  Tried:  
/usr/share/java/commons-httpclient.jar
Bug reassigned from package 'src:eclipse' to 'commons-httpclient'.
No longer marked as found in versions eclipse/3.8.1-10.
Ignoring request to alter fixed versions of bug #871142 to the same values 
previously set
> retitle -1 Missing OSGi metadata breaks Eclipse
Bug #871142 [commons-httpclient] eclipse: FTBFS: 
/<>/build.xml:413: Could not find suitable system JAR for 
org.apache.commons.httpclient_3.1.0.v201012070820.jar.  Tried:  
/usr/share/java/commons-httpclient.jar
Changed Bug title to 'Missing OSGi metadata breaks Eclipse' from 'eclipse: 
FTBFS: /<>/build.xml:413: Could not find suitable system JAR for 
org.apache.commons.httpclient_3.1.0.v201012070820.jar.  Tried:  
/usr/share/java/commons-httpclient.jar'.
> tags -1 pending
Bug #871142 [commons-httpclient] Missing OSGi metadata breaks Eclipse
Added tag(s) pending.
> affects -1 src:eclipse
Bug #871142 [commons-httpclient] Missing OSGi metadata breaks Eclipse
Added indication that 871142 affects src:eclipse

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

Processed: Pending fixes for bugs in the commons-httpclient package

[Debian Bug Tracking System]

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

> tag 871142 + pending
Bug #871142 [commons-httpclient] Missing OSGi metadata breaks Eclipse
Ignoring request to alter tags of bug #871142 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#871142: marked as done (Missing OSGi metadata breaks Eclipse)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 22:35:13 +
with message-id 
and subject line Bug#871142: fixed in commons-httpclient 3.1-14
has caused the Debian Bug report #871142,
regarding Missing OSGi metadata breaks Eclipse
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.)


-- 
871142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse
Version: 3.8.1-10
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> dh_auto_build -- provision.cvs
>   ant -Duser.name debian provision.cvs
> Buildfile: /<>/build.xml
>  [echo] Build log is available in build_20161025231644.log
>  [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.
> 
> fetch:
> 
> setLib64Dir:
> 
> setLibDir:
> 
> symlinkBuildFeature:
> 
> symlinkBuildConfig:
> 
> unpack:
> [mkdir] Created dir: /<>/build
> [mkdir] Created dir: /<>/home
> [mkdir] Created dir: /<>/baseworkspace
> [mkdir] Created dir: /<>/buildworkspace
>  [echo] Build log is available in build_20161025231644.log
>  [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.
> 
> extractSource:
>  [echo] Build log is available in build_20161025231644.log
>  [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.
> 
> copySource:
>  [echo] Copy SDK source (cp -rd --not-target-directory eclipse 
> /<>/build/eclipse-3.8.1-src)
>  [echo] Build log is available in build_20161025231644.log
>  [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.
> 
> extractBuildXmls:
> [untar] Expanding: 
> /<>/debian/eclipse-build-generatedScripts.tar.bz2 into 
> /<>/build/eclipse-3.8.1-src
> [mkdir] Created dir: /<>/build/eclipse-3.8.1-src/buildConfigs
>  [echo] Copying eclipse-build main feature source
>  [copy] Copying 20 files to 
> /<>/build/eclipse-3.8.1-src/buildConfigs/eclipse-build-config
>  [echo] Copying eclipse-build builder
>  [copy] Copying 4 files to 
> /<>/build/eclipse-3.8.1-src/features/eclipse-build-feature
>  [echo] Build log is available in build_20161025231644.log
>  [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.
> 
> generateSecondaryFragments:
>  [copy] Copying 1 file to /<>/build/eclipse-3.8.1-src/plugins
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.filesystem.linux.alpha
>  [copy] Copying 9 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.net.linux.alpha
>  [copy] Copying 8 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.launcher.gtk.linux.alpha
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.filesystem.linux.arm
>  [copy] Copying 10 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.net.linux.arm
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.launcher.gtk.linux.arm
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.filesystem.linux.aarch64
>  [copy] Copying 10 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.net.linux.aarch64
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.launcher.gtk.linux.aarch64
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.filesystem.linux.ia64
>  [copy] Copying 9 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.net.linux.ia64
>  [copy] Copying 8 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.launcher.gtk.linux.ia64
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.filesystem.linux.mips
>  [copy] Copying 9 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.net.linux.mips
>  [copy] Copying 8 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.launcher.gtk.linux.mips
>  [copy] Copying 7 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.filesystem.linux.mipsel
>  [copy] Copying 9 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.core.net.linux.mipsel
>  [copy] Copying 8 files to 
> /<>/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.launcher.gtk.linux.mipsel
>  [copy] Copying 7 files to 
> 

Bug#790196: Please help porting rasmol to latest vte (Was: Bug#790196: rasmol: depends on vte which is deprecated)

[Emilio Pozuelo Monfort]

On 15/01/18 09:14, Andreas Tille wrote:
> Hi Jeremy,
> 
> On Sun, Jan 14, 2018 at 11:03:27PM -0500, Jeremy Bicha wrote:
>> I see that you pushed a commit to Build-Depend on libvte-2.91-dev. But
>> vte2.91 is gtk3 only so this bug is also a request to port rasmol to
>> gtk3.
> 
> Would you be able to give any better replacement for the deprecated
> libvte9 which does not require a gtk3 port?  Sorry for my very naive
> attempt but I simply have no idea about GTK porting issues.

There is a GTK+ 2 -> GTK+ 3 porting guide:

https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html

Maybe that helps.

Cheers,
Emilio

Bug#889006: [debhelper-devel] Bug#889006: dh-autoreconf is run before patching

[Mattia Rizzolo]

On Thu, Feb 01, 2018 at 07:01:00PM +, Niels Thykier wrote:
> Indeed, from my PoV we would ideally fix this issue in dpatch.  However,
> we need to handle backports as well and that puts quilt back the table
> as well.  I am not quite sure that I want to backport quilt and dpatch
> to provide further debhelper backports.

Can't we instead:
 * ignore this bug
 * have packages move away from dpatch (I believe now lintian even warns
   about quilt packages using it?  at least for 3.0 which is not this
   case but still)
 * don't worry about backports: new dh-autoreconf/debhelper won't be
   pulled automatically, and if a package from sid doesn't build in bpo
   isn't really a problem (this is of course different if a package
   already in bpo already pulling a bpo debhelper/dh-autoreconf would
   fail)

There are only 82 packages with a build-dep on dpatch, and I doubt there
are many that uses the dh addon AND autoreconf AND have a patch that
modifies the configure script.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#871142: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.jar

[Emmanuel Bourg]

Le 01/02/2018 à 23:02, Markus Koschany a écrit :

> This issue was caused by commons-httpclient due to the switch from Ant
> to Maven in version 3.1-13. The OSGi metadata is currently missing in
> the Manifest file. The data that is added by the 05_osgi_metadata patch
> is overridden by Maven later. I fixed this bug by using javahelper's
> jh_manifest tool. Eclipse builds fine from source again.

Good catch! Thank you for fixing this.

Emmanuel

Bug#887573: marked as done (pytest-pylint: FTBFS and Debci failure with python3-astroid 1.6.0-1)

[Debian Bug Tracking System]

Your message dated Thu, 01 Feb 2018 23:05:07 +
with message-id 
and subject line Bug#887573: fixed in pytest-pylint 0.7.1-2
has caused the Debian Bug report #887573,
regarding pytest-pylint: FTBFS and Debci failure with python3-astroid 1.6.0-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.)


-- 
887573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-pylint
Version: 0.7.1-1
Severity: serious

https://ci.debian.net/packages/p/pytest-pylint/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/pytest-pylint.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pytest-pylint.html

...
I: pybuild base:184: python3.6 -m pytest -v -x --ignore debian
= test session starts ==
platform linux -- Python 3.6.4, pytest-3.2.1, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python3.6
cachedir: .cache
rootdir: /build/1st/pytest-pylint-0.7.1, inifile: tox.ini
plugins: pylint-0.7.1
collecting ... collected 10 items
-
Linting files
-

pytest_pylint.py FAILED

=== FAILURES ===
__ [pylint] pytest_pylint.py ___
W: 25, 0: Unused variable '__class__' (unused-variable)
W: 25, 0: Unused variable '__class__' (unused-variable)
W:160, 0: Unused variable '__class__' (unused-variable)
W:160, 0: Unused variable '__class__' (unused-variable)
W:160, 0: Unused variable '__class__' (unused-variable)
W:160, 0: Unused variable '__class__' (unused-variable)
 Interrupted: stopping after 1 failures 
=== 1 failed in 4.42 seconds ===
Unable to create directory /nonexistent/first-build/.pylint.d
Unable to create file /nonexistent/first-build/.pylint.d/pytest_pylint1.stats: 
[Errno 2] No such file or directory: 
'/nonexistent/first-build/.pylint.d/pytest_pylint1.stats'
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python3.6 
-m pytest -v -x --ignore debian
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned 
exit code 13
debian/rules:12: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 25
--- End Message ---
--- Begin Message ---
Source: pytest-pylint
Source-Version: 0.7.1-2

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated pytest-pylint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Feb 2018 23:38:58 +0100
Source: pytest-pylint
Binary: python-pytest-pylint python3-pytest-pylint
Architecture: source
Version: 0.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Benjamin Drung 
Description:
 python-pytest-pylint - pytest plugin to check source code with pylint - Python 
2.x
 python3-pytest-pylint - pytest plugin to check source code with pylint - 
Python 3.x
Closes: 887573
Changes:
 pytest-pylint (0.7.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix inconsistent-return-statements pylint error (Closes: #887573)
   * Bump Standards-Version to 4.1.3 (no changes needed)
Checksums-Sha1:
 e5996a17693afa1e4be527d9edd9b639eaeb 2402 pytest-pylint_0.7.1-2.dsc
 633f9ea3ccb296111c94788d7c48a49154d4ed9d 6808 
pytest-pylint_0.7.1-2.debian.tar.xz
 974084db83948f3eba81ded978130fbf2ec93da1 7836 
pytest-pylint_0.7.1-2_source.buildinfo
Checksums-Sha256:
 9197e6ea226307a514dcc79ece1f55b480e99dcf892c1972186a3a00386c53c7 2402 
pytest-pylint_0.7.1-2.dsc
 86943ee73f99f618c329aa4040a5c876cc13ca5bd6b4c77cc9d68f53da24bd29 6808 

Bug#888271: Acknowledgement (libpanel-applet-dev,libpanel-applet-doc: both ship /usr/share/doc/libpanel-applet-dev/AUTHORS)

[Andreas Beckmann]

This is probably fixed in latest debhelper, #888294

Andreas

Bug#889100: fizmo-sdl2: Segfaults on start-up

[Peter De Wachter]

Package: fizmo-sdl2
Version: 0.8.5-2
Severity: serious
Justification: package doesn't work at all

I just installed fizmo-sdl2. When I start it, it shows a black window
and then it segfaults. I tried it with a bunch of different z5 files.
(These crashes don't occur with fizmo-ncurses, that version works.)

Here's a backtrace:

$ gdb -q fizmo-sdl2
Reading symbols from fizmo-sdl2...Reading symbols from 
/usr/lib/debug/.build-id/40/bb3b897ba214fc701762c7b91c8715c1eec2d2.debug...done.
done.
(gdb) run curses.z5 
Starting program: /usr/games/fizmo-sdl2 curses.z5
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecf6a700 (LWP 18815)]
[New Thread 0x7fffd96d2700 (LWP 18817)]
[New Thread 0x7fffd8cdf700 (LWP 18818)]

Thread 4 "fizmo-sdl2" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd8cdf700 (LWP 18818)]
0x5557b6e1 in tt_get_glyph_size ()
(gdb) bt
#0  0x5557b6e1 in tt_get_glyph_size ()
#1  0x55579e5a in link_interface_to_story ()
#2  0xec7c in fizmo_start ()
#3  0xace4 in interpreter_thread_function 
(UNUSED_ptr=UNUSED_ptr@entry=0x0) at fizmo-sdl2.c:1143
#4  0x77b3518c in SDL_RunThread (data=0x55c72f80) at 
./src/thread/SDL_thread.c:283
#5  0x77b8ba19 in RunThread (data=) at 
./src/thread/pthread/SDL_systhread.c:74
#6  0x771aa51a in start_thread (arg=0x7fffd8cdf700) at 
pthread_create.c:465
#7  0x75fbe3ef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95



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

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

Versions of packages fizmo-sdl2 depends on:
ii  libc6  2.26-6
ii  libdrilbo-common   0.2.11-2
ii  libfizmo-common0.7.15-2
ii  libfreetype6   2.8.1-1
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libpixelif-common  0.8.4-2
ii  libpng16-161.6.34-1
ii  libsdl2-2.0-0  2.0.7+dfsg1-3
ii  libsndfile11.0.28-4
ii  libx11-6   2:1.6.4-3
ii  libxml22.9.4+dfsg1-6.1
ii  zlib1g 1:1.2.8.dfsg-5

fizmo-sdl2 recommends no packages.

fizmo-sdl2 suggests no packages.

-- no debconf information

Bug#871142: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.jar

[Markus Koschany]

Control: reassign -1 commons-httpclient
Control: retitle -1 Missing OSGi metadata breaks Eclipse
Control: tags -1 pending
Control: affects -1 src:eclipse

On Sun, 6 Aug 2017 17:55:36 -0400 Lucas Nussbaum  wrote:
> Source: eclipse
> Version: 3.8.1-10
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170805 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

[...]

This issue was caused by commons-httpclient due to the switch from Ant
to Maven in version 3.1-13. The OSGi metadata is currently missing in
the Manifest file. The data that is added by the 05_osgi_metadata patch
is overridden by Maven later. I fixed this bug by using javahelper's
jh_manifest tool. Eclipse builds fine from source again.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#885548: winetricks: Don't recommend gksu

[Jens Reyer]

control: forwarded -1 https://github.com/Winetricks/winetricks/issues/912

> I won't be able to fix upstream for a few weeks, but I've filled a bug in
> the meantime:
> 
> https://github.com/Winetricks/winetricks/issues/912

There have been a few patches upstream, so I guess we'll have a solution
soon.

Greets
jre

Processed: Re: Bug#885548: winetricks: Don't recommend gksu

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/Winetricks/winetricks/issues/912
Bug #885548 [winetricks] winetricks: Don't recommend gksu
Set Bug forwarded-to-address to 
'https://github.com/Winetricks/winetricks/issues/912'.

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

Bug#887912: Acknowledgement (python-parted-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/python-parted/HACKING.gz)

[Andreas Beckmann]

This is probably fixed in latest debhelper, #888294

Andreas

Bug#888301: Acknowledgement (appstream-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/appstream/NEWS.gz)

[Andreas Beckmann]

This is probably fixed in latest debhelper, #888294

Andreas

Bug#888816: Acknowledgement (libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS)

[Andreas Beckmann]

This is probably fixed in latest debhelper, #888294

Andreas

Bug#888556: Acknowledgement (libetsf-io-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libetsf-io-dev/AUTHORS)

[Andreas Beckmann]

This is probably fixed in latest debhelper, #888294

Andreas

Processed: Bug#887573 marked as pending

[Debian Bug Tracking System]

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

> tag 887573 pending
Bug #887573 [src:pytest-pylint] pytest-pylint: FTBFS and Debci failure with 
python3-astroid 1.6.0-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871142: eclipse: FTBFS: /<>/build.xml:413: Could not find suitable system JAR for org.apache.commons.httpclient_3.1.0.v201012070820.jar. Tried: /usr/share/java/commons-httpclient.jar

[Markus Koschany]

Am 01.02.2018 um 23:29 schrieb Emmanuel Bourg:
> Le 01/02/2018 à 23:02, Markus Koschany a écrit :
> 
>> This issue was caused by commons-httpclient due to the switch from Ant
>> to Maven in version 3.1-13. The OSGi metadata is currently missing in
>> the Manifest file. The data that is added by the 05_osgi_metadata patch
>> is overridden by Maven later. I fixed this bug by using javahelper's
>> jh_manifest tool. Eclipse builds fine from source again.
> 
> Good catch! Thank you for fixing this.
> 
> Emmanuel

No problem. But now starts the real challenge... Let's see if it is
possible to split the package in smaller parts so that we can

a) remove swt-gtk from Debian
b) keep all reverse-dependencies that depend on eclipse-rcp,
eclipse-platform and eclipse-jdt in Debian

Hahaha, and after that squaring the circle should be a piece of cake.



signature.asc
Description: OpenPGP digital signature

Bug#887573: marked as pending

[Benjamin Drung]

tag 887573 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/pytest-pylint.git/commit/?id=543a086

---
commit 543a086613a27a0501b41fb9775c8dc6ce69bb71
Author: Benjamin Drung 
Date:   Thu Feb 1 23:39:28 2018 +0100

Release pytest-pylint 0.7.1-2

diff --git a/debian/changelog b/debian/changelog
index 1057983..0c1e6bb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pytest-pylint (0.7.1-2) unstable; urgency=medium
+
+  * Team upload.
+  * Fix inconsistent-return-statements pylint error (Closes: #887573)
+  * Bump Standards-Version to 4.1.3 (no changes needed)
+
+ -- Benjamin Drung   Thu, 01 Feb 2018 23:38:58 +0100
+
 pytest-pylint (0.7.1-1) unstable; urgency=medium
 
   [ Ondřej Nový ]

Bug#888816: Acknowledgement (libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS)

[Simon McVittie]

On Fri, 02 Feb 2018 at 00:27:23 +0100, Andreas Beckmann wrote:
> This is probably fixed in latest debhelper, #888294

Thanks, but I think the dbus-glib one was actually my fault: I
bumped debhelper compat to 11, but didn't add Breaks/Replaces for the
documentation having moved around as a result. It seems fixed now, so
unless piuparts is still sad, I'm hoping not to touch dbus-glib again
for a while.

smcv

Processed: your mail

[Debian Bug Tracking System]

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

> severity 883872 serious
Bug #883872 [src:bitlbee] bitlbee: Extremely incomplete d/copyright
Severity set to 'serious' from 'minor'
> thanks
Stopping processing here.

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

Bug#889105: chezscheme: Fails to build from source with glibc 2.26

[Jeremy Bicha]

Source: chezscheme
Version: 9.5+dfsg-1
Severity: serious

chezscheme fails to build from source with glibc 2.26.

Specifically, #include  won't work starting with that
version of glibc.

This can be clearly seen in the reproducible builds logs:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chezscheme.html

Thanks,
Jeremy Bicha

Bug#885835: marked as done (awstats: CVE-2017-1000501: path traversals in config and migrate parameter)

[Debian Bug Tracking System]

Your message dated Fri, 02 Feb 2018 01:34:48 +
with message-id 
and subject line Bug#885835: fixed in awstats 7.6+dfsg-2
has caused the Debian Bug report #885835,
regarding awstats: CVE-2017-1000501: path traversals in config and migrate 
parameter
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.)


-- 
885835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: awstats
Version: 7.6+dfsg-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for awstats.

CVE-2017-1000501[0]:
Path traversal flaws

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-1000501
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000501
[1] http://www.openwall.com/lists/oss-security/2017/12/29/1
[2] 
https://github.com/eldy/awstats/commit/cf219843a74c951bf5986f3a7fffa3dcf99c3899
[3] 
https://github.com/eldy/awstats/commit/06c0ab29c1e5059d9e0279c6b64d573d619e1651

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: awstats
Source-Version: 7.6+dfsg-2

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated awstats 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: Fri, 02 Feb 2018 02:21:35 +0100
Source: awstats
Binary: awstats
Architecture: source
Version: 7.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 awstats- powerful and featureful web server log analyzer
Closes: 885835
Changes:
 awstats (7.6+dfsg-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to the QA team.
   * Import fixes from Ubuntu.
 + CVE-2017-1000501, closes: #885835
 + but the fix for #858461 is incomplete
   * Drop ancient versioned Recommends on an essential package.
Checksums-Sha1:
 3bffe5ebc97835440f8c3f07976ac1947d3b40ba 1928 awstats_7.6+dfsg-2.dsc
 41a5922390afb173565a09139b7f8f1a6ccafd6d 38052 awstats_7.6+dfsg-2.debian.tar.xz
 f8a51ce8e1b05d51dbbeaf0ec191aba95e483af3 5341 
awstats_7.6+dfsg-2_source.buildinfo
Checksums-Sha256:
 4eb251227293203aed33e540a103bb96b9248385517b566b1f756b9770a7a27e 1928 
awstats_7.6+dfsg-2.dsc
 4499a730c0bd682d65e6dc712069218761ee6fd6c0614e758fb035c592cc49c7 38052 
awstats_7.6+dfsg-2.debian.tar.xz
 4be145aa32cbeacac8a31fd3ec420abc37d09785864c8d428bb8429f4351e2f9 5341 
awstats_7.6+dfsg-2_source.buildinfo
Files:
 f9409597dac443b175511d8a81576382 1928 web optional awstats_7.6+dfsg-2.dsc
 e1a20dc076885bbcce800947addb3569 38052 web optional 
awstats_7.6+dfsg-2.debian.tar.xz
 abb7790c49535c3567ac6a547ff92dc8 5341 web optional 
awstats_7.6+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlpzvS4UHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH5n1g//ayV1JDIwGyBqyXqAvyIWUe5Z8JJd
XlxFPA5/j31+/lcmI4gGg46V5NFz+kdxQXLJGKC8TlHWIzbCQ0WQp7L8s05/7Djs
7sZA1Yt7VmrqgL0peBQbYxZXSkJwplPAJazj4OF4N8CaKIbUPGDk7OL9x4woD8Qa
+wA96NCOqa7Z6y8Fg+s8TCgEiqb7fnLDIQUQZhTLXON8CAX93Kgc6UL31rnTlRBM
dXzrufna6dCXEbkXsAgMjyjU57sKbF66RMhUtZdKEnflu5OW0eEsgqDEAKm26fMV
uSiKPMnJ01IgdRh9cGfqDbl5+uSqMw3w07torAzzSibjULEVZknz64XPk4rI5utv
8MyBcdNuQBGP5/fw/z8yzuYAMtTKr4fBulCEbWozhxLfZnCbXIgyhR+Pev3RwOlD
eJSuwuWzrdVh8+qWrfyvxwgGgU87siTh1Xt7YNyritm+FoBGZJ13n604TMjH9vPV
zaIqfMCrW+SKP+B01Qcs320MuF6xgVNXe/nReAOXySdeqEv5I9JUCi4FcP6VYMhI
2yk4bHJvjdZGUlDC50mNJXLpjPHYY6XbTgcboxVkHAoXIWmozS+lYcFNDrieKFYp
fFcrd1ydgxAbuUeTHUt1lSBEblmSu+TQFcD1wFC+9VsYhvW7TGZhfj9qYGODkfXT
MkTUnaHH8UYjACo=
=y+LT
-END PGP SIGNATURE End Message ---

Processed: off to doxygen we go

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 makes ctpp2 randomly FTBFS, syntax errors, hides problems
Bug #886120 [src:ctpp2] FTBFS: chown: cannot access '..._cgraph.dot': No such 
file or directory
Changed Bug title to 'makes ctpp2 randomly FTBFS, syntax errors, hides 
problems' from 'FTBFS: chown: cannot access '..._cgraph.dot': No such file or 
directory'.
> tags -1 -moreinfo unreproducible
Bug #886120 [src:ctpp2] makes ctpp2 randomly FTBFS, syntax errors, hides 
problems
Removed tag(s) moreinfo and unreproducible.
> reassign -1 doxygen
Bug #886120 [src:ctpp2] makes ctpp2 randomly FTBFS, syntax errors, hides 
problems
Bug reassigned from package 'src:ctpp2' to 'doxygen'.
No longer marked as found in versions ctpp2/2.8.3-23.
Ignoring request to alter fixed versions of bug #886120 to the same values 
previously set
> affects 818379 + ctpp2
Bug #818379 [doxygen] doxygen: Does not properly trap for errors when calling 
dot
Added indication that 818379 affects ctpp2

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

Bug#886120: off to doxygen we go

[Adam Borowski]

Control: retitle -1 makes ctpp2 randomly FTBFS, syntax errors, hides problems
Control: tags -1 -moreinfo unreproducible
Control: reassign -1 doxygen
Control: affects 818379 + ctpp2

As I don't see anything obvious in the way ctpp2 calls doxygen + graphviz,
there's no point in having the bug stay here.  The culprit here is doxygen
as it's where the syntax errors come from.

Generating calError: 
/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.dot: 
syntax error in line 67 near '-'
error: Problems running dot: exit code=1, command='dot', 
arguments='"/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.dot"
 -Tsvg -o 
"/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.svg"'
Running Error: 
/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.dot: 
syntax error in line 8 near '-'
error: Problems running dot: exit code=1, command='dot', 
arguments='"/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.dot"
 -Tsvg -o 
"/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.svg"'
... and many others.

The other bug, succeeding most of the time due to usually ignoring errors is
obviously RC; but that's already filed as #818379 (severity: important).


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?

Bug#889107: libgdbm-compat-dev: missing Breaks: libgdbm-dev (<< 1.12-1) due to typo

[Andreas Beckmann]

Package: libgdbm-compat-dev
Version: 1.14.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.
...

The Breaks is actually intended to be there, but has a mistyped package
name (missing 'm').

This allows some broken partial upgrades + partial removals from stretch ...


Andreas

Bug#883872: (no subject)

[Wilmer van der Gaast]

Severity: 883872 minor
stop

Please quote the part of
https://www.debian.org/doc/debian-policy/#copyright-information that
says "every single file must be mentioned in the copyright file". I
don't see it there nor would I see the point as per-file info is best
off stored in those very files.

Let me know if there's something actually serious like a *licence* not
being accounted for, or a (significant) author or group of authors (that
is not the currently mentioned me/dx/BitlBee team or Gaim team) not
mentioned.

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> severity 883872 minor
Bug #883872 [src:bitlbee] bitlbee: Extremely incomplete d/copyright
Severity set to 'minor' from 'serious'
> tyvm
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: ot a problem in stretch

[Debian Bug Tracking System]

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

> tags 832020 buster sid
Bug #832020 [src:ruby2.3] ruby2.3: ruby2.3_2.3.1-5 does not build with latest 
gdbm
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#889122: phpdox FTBFS with PHP 7.2

[Adrian Bunk]

Source: phpdox
Version: 0.10.1-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phpdox.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/phpdox-0.10.1'
ant test
Unable to locate tools.jar. Expected to find it in 
/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar
Buildfile: /build/1st/phpdox-0.10.1/build.xml

phpunit:
 [exec] PHPUnit 6.5.5 by Sebastian Bergmann and contributors.
 [exec] 
 [exec] Runtime:   PHP 7.2.1-1
 [exec] Configuration: /build/1st/phpdox-0.10.1/phpunit.xml.dist
 [exec] Error: No code coverage driver is available
 [exec] 
 [exec] E 
65 / 85 ( 76%)
 [exec]   
85 / 85 (100%)
 [exec] 
 [exec] Time: 4.59 seconds, Memory: 6.00MB
 [exec] 
 [exec] There was 1 error:
 [exec] 
 [exec] 1) 
TheSeer\phpDox\GlobalConfigTest::testGetCustomBootstrapFilesReturnsEmptyCollectionByDefault
 [exec] count(): Parameter must be an array or an object that implements 
Countable
 [exec] 
 [exec] /build/1st/phpdox-0.10.1/src/shared/FileInfoCollection.php:67
 [exec] /build/1st/phpdox-0.10.1/tests/Unit/config/GlobalConfigTest.php:127
 [exec] 
 [exec] ERRORS!
 [exec] Tests: 85, Assertions: 129, Errors: 1.

BUILD FAILED
/build/1st/phpdox-0.10.1/build.xml:28: exec returned: 2

Total time: 14 seconds
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889123: phpunit FTBFS with PHP 7.2

[Adrian Bunk]

Source: phpunit
Version: 6.5.5-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phpunit.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/phpunit-6.5.5'
# Build static classloader for shipping
phpab --output src/Autoload.php \
--template debian/Autoload.php.tpl src
phpab %development% - Copyright (C) 2009 - 2017 by Arne Blankerts and 
Contributors

Scanning directory src

Autoload file src/Autoload.php generated.

# Build classloader for tests
mkdir --parents vendor
phpab \
--output vendor/autoload.php \
--template debian/autoload.test.php.tpl \
--exclude tests/_files/BankAccountTest2.php \
--exclude tests/Regression/Trac/783/OneTest.php \
tests
phpab %development% - Copyright (C) 2009 - 2017 by Arne Blankerts and 
Contributors

Scanning directory tests

Autoload file vendor/autoload.php generated.

# Workaround to ensure the local class takes precedence during tests.
ln -s src PHPUnit
make[1]: Leaving directory '/build/1st/phpunit-6.5.5'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/phpunit-6.5.5'
./phpunit
Class 'DOMDocument' not found
debian/rules:28: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889124: symfony FTBFS with PHP 7.2

[Adrian Bunk]

Source: symfony
Version: 3.4.3+dfsg-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/symfony.html

...
There was 1 skipped test:

1) Symfony\Bridge\Doctrine\Tests\ManagerRegistryTest
proxy-manager-bridge is not yet compatible with namespaced phpunit versions.

/build/1st/symfony-3.4.3+dfsg/src/Symfony/Bridge/Doctrine/Tests/ManagerRegistryTest.php:23

OK, but incomplete, skipped, or risky tests!
Tests: 215, Assertions: 471, Skipped: 
1.

Legacy deprecation notices (5)
debian/rules:70: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889111: bluez: Causes extreme non-stop CPU usage leading to notebook overheating quickly

[Alex Henry]

Package: bluez
Version: 5.47-1+b1
Severity: critical
Justification: breaks the whole system

Hello, I initially reported this as a bug to udev/systemd but it resolved after 
removing the "bluez" package from my system,
with no other changes besides that. The original report has all the pertinent 
information:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889110

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bluez depends on:
ii  dbus  1.12.2-1
ii  kmod  25-1
ii  libasound21.1.3-5
ii  libc6 2.26-4
ii  libdbus-1-3   1.12.2-1
ii  libdw10.170-0.2
ii  libglib2.0-0  2.54.3-2
ii  libreadline7  7.0-3
ii  libudev1  236-3
ii  lsb-base  9.20170808
ii  udev  236-3

bluez recommends no packages.

Versions of packages bluez suggests:
pn  pulseaudio-module-bluetooth  

Bug#889117: ruby2.3 FTBFS with tzdata 2018c-1

[Adrian Bunk]

Source: ruby2.3
Version: 2.3.3-1
Severity: serious

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

...
  5) Failure:
TestTimeTZ#test_asia_tokyo [/<>/test/ruby/test_time_tz.rb:129]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 2, 0, 0).
<"1951-05-06 03:00:00 +1000"> expected but was
<"1951-05-06 02:00:00 +1000">.

  6) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_24 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 5, 5, 16, 59, 59).localtime.
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 02:59:59 +1000">.

  7) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_27 
[/<>/test/ruby/test_time_tz.rb:259]:
TZ=Asia/Tokyo Time.utc(1951, 9, 7, 16, 0, 0).localtime.
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 02:00:00 +1000">.

  8) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_69 
[/<>/test/ruby/test_time_tz.rb:277]:
TZ=Asia/Tokyo Time.local(1951, 5, 6, 1, 59, 59).
<"1951-05-06 01:59:59 +0900"> expected but was
<"1951-05-06 01:59:59 +1000">.

  9) Failure:
TestTimeTZ#test_gen_Asia_Tokyo_72 
[/<>/test/ruby/test_time_tz.rb:295]:
TZ=Asia/Tokyo Time.local(0, 0, 1, 8, 9, 1951, nil, nil, false, nil).
<"1951-09-08 01:00:00 +0900"> expected but was
<"1951-09-08 01:00:00 +1000">.
...


The same FTBFS in ruby2.5 was reported as #889046.

Additional unrelated failures in unstable caused by the
gdbm transition are handled in #832020.

I have reproduced this FTBFS with tzdata 2018c-1 in stretch,
and it is expected that tzdata >= 2018c will enter stretch.

Bug#889119: php-console-table FTBFS with PHP 7.2

[Adrian Bunk]

Source: php-console-table
Version: 1.3.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-console-table.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-console-table-1.3.0'
pear run-tests Console_Table-*/tests
Running 15 tests
FAIL [ 1/15] Header and data as associative 
arrays.[Console_Table-1.3.0/tests/assoziative_arrays.phpt]
PASS [ 2/15] Border: default ASCII 
mode[Console_Table-1.3.0/tests/border-ascii.phpt]
PASS [ 3/15] Border: new custom 
mode[Console_Table-1.3.0/tests/border-custom.phpt]
PASS [ 4/15] Border: new custom mode, alternative 
style[Console_Table-1.3.0/tests/border-custom2.phpt]
PASS [ 5/15] Border: disable it[Console_Table-1.3.0/tests/border-disable.phpt]
PASS [ 6/15] Border: custom border 
character[Console_Table-1.3.0/tests/border-dot.phpt]
PASS [ 7/15] Border: empty 
character[Console_Table-1.3.0/tests/border-empty.phpt]
PASS [ 8/15] Bug #20181: setAlign() on non-zero 
column[Console_Table-1.3.0/tests/bug20181.phpt]
SKIP Data with ANSI color codes[Console_Table-1.3.0/tests/colors.phpt](reason: 
Console_Color2 not installed)

Warning: count(): Parameter must be an array or an object that implements 
Countable in PEAR/RunTest.php on line 346
PHP Warning:  count(): Parameter must be an array or an object that implements 
Countable in /usr/share/php/PEAR/RunTest.php on line 346
FAIL [10/15] Callback filters[Console_Table-1.3.0/tests/filters.phpt]
FAIL [11/15] Multibyte strings[Console_Table-1.3.0/tests/multibyte.phpt]
FAIL [12/15] Multiline table cells[Console_Table-1.3.0/tests/multiline.phpt]
FAIL [13/15] Table without header[Console_Table-1.3.0/tests/no_header.phpt]
PASS [14/15] Table without data[Console_Table-1.3.0/tests/no_rows.phpt]
FAIL [15/15] Horizontal rules[Console_Table-1.3.0/tests/rules.phpt]
wrote log to "/build/1st/php-console-table-1.3.0/run-tests.log"
TOTAL TIME: 00:10
8 PASSED TESTS
1 SKIPPED TESTS
6 FAILED TESTS:
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/assoziative_arrays.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/filters.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/multibyte.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/multiline.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/no_header.phpt
/build/1st/php-console-table-1.3.0/Console_Table-1.3.0/tests/rules.phpt
Some tests failed
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889121: php-mail-mime FTBFS with PHP 7.2

[Adrian Bunk]

Source: php-mail-mime
Version: 1.10.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-mail-mime.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-mail-mime-1.10.0'
cd Mail_Mime-* && pear run-tests tests
Running 39 tests
SKIP Test class filename (bug #24)[tests/class-filename.phpt](reason: This will 
be broken until Mail_Mime2)

Warning: count(): Parameter must be an array or an object that implements 
Countable in PEAR/RunTest.php on line 346
PHP Warning:  count(): Parameter must be an array or an object that implements 
Countable in /usr/share/php/PEAR/RunTest.php on line 346
PASS [ 2/39] Bug #2364   Tabs in 
Mail_mimePart::quotedPrintableEncode()[tests/encoding_case.phpt]
PASS [ 3/39] Multi-test for headers encoding using base64 and 
quoted-printable[tests/headers_with_mbstring.phpt]
SKIP Multi-test for headers encoding using base64 and 
quoted-printable[tests/headers_without_mbstring.phpt](reason: mbstring 
functions found!)

Warning: count(): Parameter must be an array or an object that implements 
Countable in PEAR/RunTest.php on line 346
PHP Warning:  count(): Parameter must be an array or an object that implements 
Countable in /usr/share/php/PEAR/RunTest.php on line 346
FAIL [ 5/39] Bug #3488   Sleep/Wakeup EOL Consistency - Part 
1[tests/sleep_wakeup_EOL-bug3488-part1.phpt]
FAIL [ 6/39] Bug #3488   Sleep/Wakeup EOL Consistency - Part 
2[tests/sleep_wakeup_EOL-bug3488-part2.phpt]
FAIL [ 7/39] Bug #3513   Support of RFC2231 in header fields. 
(ISO-8859-1)[tests/test_Bug_3513_1.phpt]
FAIL [ 8/39] Bug #3513   Support of RFC2231 in header fields. 
(UTF-8)[tests/test_Bug_3513_2.phpt]
FAIL [ 9/39] Bug #3513   Support of RFC2231 in header fields. 
(ISO-2022-JP)[tests/test_Bug_3513_3.phpt]
PASS [10/39] Bug #7561   Mail_mimePart::quotedPrintableEncode() misbehavior 
with mbstring overload[tests/test_Bug_7561_1.phpt]
FAIL [11/39] Bug #8386   HTML body not correctly encoded if attachments 
present[tests/test_Bug_8386_1.phpt]
PASS [12/39] Bug #8541   mimePart.php line delimiter is 
\r[tests/test_Bug_8541_1.phpt]
PASS [13/39] Bug #9722   quotedPrintableEncode does not encode dot at start of 
line on Windows platform[tests/test_Bug_9722_1.phpt]
FAIL [14/39] Bug #10596  Incorrect handling of text and html '0' 
bodies[tests/test_Bug_10596_1.phpt]
FAIL [15/39] Bug #10816  Unwanted linebreak at the end of 
output[tests/test_Bug_10816_1.phpt]
FAIL [16/39] Bug #10999  Bad Content-ID(cid) format[tests/test_Bug_10999_1.phpt]
FAIL [17/39] Bug #11381  Domain name is attached to content-id, trailing 
greater-than sign is not removed[tests/test_Bug_11381.phpt]
FAIL [18/39] Bug #11731  Full stops after soft line breaks are not 
encoded[tests/test_Bug_11731.phpt]
FAIL [19/39] Bug #12165  Dot at the end of the line 
disappeared[tests/test_Bug_12165.phpt]
FAIL [20/39] Bug #12385  Bad regex when replacing css style 
attachments[tests/test_Bug_12385_1.phpt]
FAIL [21/39] Bug #12411  RFC2047 encoded attachment 
filenames[tests/test_Bug_12411.phpt]
FAIL [22/39] Bug #12466  Content-Transfer-Encoding 
checking[tests/test_Bug_12466.phpt]
FAIL [23/39] Bug #13032  Proper (different) boundary for nested 
parts[tests/test_Bug_13032.phpt]
FAIL [24/39] Bug #9725   multipart/related & alternative wrong 
order[tests/test_Bug_13444.phpt]
PASS [25/39] Bug #13962  Multiple header support[tests/test_Bug_13962.phpt]
FAIL [26/39] Bug #14529  basename() workaround[tests/test_Bug_14529.phpt]
FAIL [27/39] Bug #14779  Proper header-body separator for empty 
attachment[tests/test_Bug_14779.phpt]
FAIL [28/39] Bug #14780  Invalid Content-Type when headers() is called before 
get()[tests/test_Bug_14780.phpt]
FAIL [29/39] Bug #15320  Charset parameter in Content-Type of mail 
parts[tests/test_Bug_15320.phpt]
PASS [30/39] Bug #16539  Headers longer than 998 
characters[tests/test_Bug_16539.phpt]
PASS [31/39] Bug #16539  Headers longer than 998 
characters[tests/test_Bug_17025.phpt]
FAIL [32/39] Bug #17175  Content-Description 
support+ecoding[tests/test_Bug_17175.phpt]
FAIL [33/39] Bug #18083  Separate charset for attachment's content and 
headers[tests/test_Bug_18083.phpt]
FAIL [34/39] Bug #18772  Text/calendar message[tests/test_Bug_18772.phpt]
FAIL [35/39] Bug #19497  Attachment filenames with a slash 
character[tests/test_Bug_19497.phpt]
PASS [36/39] Bug #20226  Mail_mimePart::encodeHeader() and ISO-2022-JP 
encoding[tests/test_Bug_20226.phpt]
PASS [37/39] Bug #20273  Mail_mimePart::encodeHeader() and TAB 
character[tests/test_Bug_20273.phpt]
PASS [38/39] Bug #20563   isMultipart() method tests[tests/test_Bug_20563.phpt]
PASS [39/39] Bug #20564   Unsetting headers[tests/test_Bug_20564.phpt]
wrote log to "/build/1st/php-mail-mime-1.10.0/Mail_Mime-1.10.0/run-tests.log"
TOTAL TIME: 00:07
12 PASSED TESTS
2 SKIPPED TESTS
25 FAILED TESTS:
/build/1st/php-mail-mime-1.10.0/Mail_Mime-1.10.0/tests/sleep_wakeup_EOL-bug3488-part1.phpt

Bug#889120: php-crypt-chap FTBFS with PHP 7.2

[Adrian Bunk]

Source: php-crypt-chap
Version: 1.5.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-crypt-chap.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-crypt-chap-1.5.0'
pear run-tests Crypt_CHAP-*/tests
Running 1 tests
FAIL Crypt_CHAP: simple test[Crypt_CHAP-1.5.0/tests/Crypt_CHAP.phpt]
wrote log to "/build/1st/php-crypt-chap-1.5.0/run-tests.log"
TOTAL TIME: 00:00
0 PASSED TESTS
0 SKIPPED TESTS
1 FAILED TESTS:
/build/1st/php-crypt-chap-1.5.0/Crypt_CHAP-1.5.0/tests/Crypt_CHAP.phpt
Some tests failed
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889127: ggcov FTBFS: test failures

[Adrian Bunk]

Source: ggcov
Version: 0.9-19
Severity: serious

Some recent change in unstable makes ggcov FTBFS:

https://tests.reproducible-builds.org/debian/history/ggcov.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ggcov.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/ggcov-0.9'
(cd test && ./runtest)
Running tests
hostname: "profitbricks-build1-amd64"
date: "20180201T144325"
uname -s: "Linux"
uname -m: "x86_64"
uname -r: "4.9.0-5-amd64"
head -1 /etc/os-release: "PRETTY_NAME="Debian GNU/Linux buster/sid""
which gcc: "/usr/bin/gcc"
gcc --version: "gcc (Debian 7.3.0-5+really1.0~reproducible1) 7.3.0"
which g++: "/usr/bin/g++"
g++ --version: "g++ (Debian 7.3.0-5+really1.0~reproducible1) 7.3.0"
PASS: (test000) unit tests
ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test002) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test004) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test005.1) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test006) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test007) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test008.0) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test009) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test010) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test011.1) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test013) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test014) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test015.a001) tggcov failed, see log or re-run with -D all,verbose 
--no-log
ERROR: (test016.1) tggcov failed, see log or re-run with -D all,verbose --no-log
PASS: (test021) unit test for libpopt / fakepopt.c
ERROR: (test029) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test030) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test033) tggcov failed, see log or re-run with -D all,verbose --no-log
ERROR: (test034) tggcov failed, see log or re-run with -D all,verbose --no-log
Total: 2/20 tests passed
debian/rules:34: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#889028: minissdpd: Fails to install on Debian unstable

[Awtul]

Package: minissdpd
Version: 1.5.20161216-1
Followup-For: Bug #889028

Dear Maintainer,

I just wanted to confirm the bug. 
So, upgrading from minissdpd:amd64 1.2.20130907-4.1 to  1.5.20161216-1 I got 
"Error: Sub-process /usr/bin/dpkg returned an error code (1)". Same error after 
purging the buggy pkg
and reinstalling it.
systemctl status minissdpd 
"Loaded: loaded (/lib/systemd/system/minissdpd.service; disabled; vendor 
preset: enabled)Active: inactive (dead)"

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_ES:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minissdpd depends on:
ii  libc6  2.26-6
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   9.20170808

minissdpd recommends no packages.

minissdpd suggests no packages.

-- no debconf information

Bug#889115: pnetcdf FTBFS on 32bit: Building of Parallel NetCDF cannot continue due to the size of MPI_Offset being less than 8 bytes

[Adrian Bunk]

Source: pnetcdf
Version: 1.9.0-1
Severity: serious

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

...
checking for MPI_Offset... yes
checking size of MPI_Offset... 4
configure: error: 
   ---
 Building of Parallel NetCDF cannot continue due to the size of
 MPI_Offset being less than 8 bytes. Please use an MPI library that
 supports large files. Abort.
   ---

Bug#889125: comidi-clojure FTBFS: test failure

[Adrian Bunk]

Source: comidi-clojure
Version: 0.3.1-1
Severity: serious

Some recent change in unstable makes comidi-clojure FTBFS:

https://tests.reproducible-builds.org/debian/history/comidi-clojure.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/comidi-clojure.html

...
dh_auto_test
(cd test && find . -name "*.clj" | \
xargs --verbose clojure -cp 
/build/1st/comidi-clojure-0.3.1/comidi.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/bidi.jar:/usr/share/java/compojure.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/kitchensink.jar)
clojure -cp 
/build/1st/comidi-clojure-0.3.1/comidi.jar:/usr/share/java/clojure.jar:/usr/share/java/clj-time.jar:/usr/share/java/bidi.jar:/usr/share/java/compojure.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/kitchensink.jar
 ./puppetlabs/comidi_test.clj 
Exception in thread "main" clojure.lang.ExceptionInfo: Call to clojure.core/ns 
did not conform to spec:
In: [1] val: ((require [clojure.test :refer :all] [puppetlabs.comidi :as comidi 
:refer :all] [schema.test :as schema-test] [schema.core :as schema] 
[clojure.zip :as zip] [bidi.bidi :as bidi])) fails at: [:args] predicate: (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses),  Extra input
:clojure.spec/args  (puppetlabs.comidi-test (require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi]))
 #:clojure.spec{:problems [{:path [:args], :reason "Extra input", :pred (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses), :val ((require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi])), :via [], 
:in [1]}], :args (puppetlabs.comidi-test (require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi]))}, 
compiling:(/build/1st/comidi-clojure-0.3.1/test/./puppetlabs/comidi_test.clj:1:1)
at clojure.lang.Compiler.load(Compiler.java:7442)
at clojure.lang.Compiler.loadFile(Compiler.java:7368)
at clojure.main$load_script.invokeStatic(main.clj:277)
at clojure.main$script_opt.invokeStatic(main.clj:337)
at clojure.main$script_opt.invoke(main.clj:332)
at clojure.main$main.invokeStatic(main.clj:423)
at clojure.main$main.doInvoke(main.clj:386)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at clojure.lang.Var.applyTo(Var.java:700)
at clojure.main.main(main.java:37)
Caused by: clojure.lang.ExceptionInfo: Call to clojure.core/ns did not conform 
to spec:
In: [1] val: ((require [clojure.test :refer :all] [puppetlabs.comidi :as comidi 
:refer :all] [schema.test :as schema-test] [schema.core :as schema] 
[clojure.zip :as zip] [bidi.bidi :as bidi])) fails at: [:args] predicate: (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses),  Extra input
:clojure.spec/args  (puppetlabs.comidi-test (require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi]))
 {:clojure.spec/problems [{:path [:args], :reason "Extra input", :pred (cat 
:docstring (? string?) :attr-map (? map?) :clauses 
:clojure.core.specs/ns-clauses), :val ((require [clojure.test :refer :all] 
[puppetlabs.comidi :as comidi :refer :all] [schema.test :as schema-test] 
[schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as bidi])), :via [], 
:in [1]}], :clojure.spec/args (puppetlabs.comidi-test (require [clojure.test 
:refer :all] [puppetlabs.comidi :as comidi :refer :all] [schema.test :as 
schema-test] [schema.core :as schema] [clojure.zip :as zip] [bidi.bidi :as 
bidi]))}
at clojure.core$ex_info.invokeStatic(core.clj:4725)
at clojure.spec$macroexpand_check.invokeStatic(spec.clj:697)
at clojure.spec$macroexpand_check.invoke(spec.clj:686)
at clojure.lang.AFn.applyToHelper(AFn.java:156)
at clojure.lang.AFn.applyTo(AFn.java:144)
at clojure.lang.Var.applyTo(Var.java:700)
at clojure.lang.Compiler.macroexpand1(Compiler.java:6816)
at clojure.lang.Compiler.macroexpand(Compiler.java:6888)
at clojure.lang.Compiler.eval(Compiler.java:6962)
at clojure.lang.Compiler.load(Compiler.java:7430)
... 9 more
debian/rules:32: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 123

Bug#889006: [debhelper-devel] Bug#889006: dh-autoreconf is run before patching

[Adrian Bunk]

On Thu, Feb 01, 2018 at 07:01:00PM +, Niels Thykier wrote:
>...
> Indeed, from my PoV we would ideally fix this issue in dpatch.  However,
> we need to handle backports as well and that puts quilt back the table
> as well.  I am not quite sure that I want to backport quilt and dpatch
> to provide further debhelper backports.

Why not?

dpatch is a mostly obsolete Debian native package,
most recent upload 2015.

quilt still has some upstream development, but nothing big.

It might still be easier to revert the change in dh-autoreconf,
but dpatch and quilt are not packages where I would see any
potential problems with making and supporting a backport.

> Thanks,
> ~Niels

cu
Adrian

-- 

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

Bug#889118: bitcoin FTBFS with gcc-7 7.3.0-1: symbols disappeared

[Adrian Bunk]

Source: bitcoin
Version: 0.15.1~dfsg-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bitcoin.html

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/bitcoin-0.15.1~dfsg'
dh_makeshlibs -- 
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbitcoinconsensus0/DEBIAN/symbols doesn't 
match completely debian/libbitcoinconsensus0.symbols
--- debian/libbitcoinconsensus0.symbols 
(libbitcoinconsensus0_0.15.1~dfsg-1_amd64)
+++ dpkg-gensymbolsk5YxNq   2019-03-05 21:13:06.499223011 -1200
@@ -38,7 +38,7 @@
  _Z14ArithToUint256RK13arith_uint256@Base 0.14.2~dfsg
 #MISSING: 0.15.0~~# _Z14GetBlockWeightRK6CBlock@Base 0.14.2~dfsg
  
_Z14SanitizeStringRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 
0.14.2~dfsg
- 
(optional=templinst|arch-bits=64)_Z14Serialize_implI13CSizeComputer5CTxInSaIS1_ES1_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
 0.15.0~~
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst|arch-bits=64)_Z14Serialize_implI13CSizeComputer5CTxInSaIS1_ES1_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
 0.15.0~~
  (arch-bits=64)_Z14SipHashUint256mmRK7uint256@Base 0.14.2~dfsg
  (arch-bits=32)_Z14SipHashUint256yyRK7uint256@Base 0.14.2~dfsg
  _Z14UintToArith256RK7uint256@Base 0.14.2~dfsg
@@ -47,7 +47,7 @@
  
(arch-bits=64)_Z15FormatParagraphRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmm@Base
 0.14.2~dfsg
  
(arch-bits=64)_Z15ParseFixedPointRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiPl@Base
 0.14.2~dfsg
  
(arch-bits=32)_Z15ParseFixedPointRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiPx@Base
 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z16GetSerializeSizeI6CBlockE{size_t}RKT_ii@Base 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z16GetSerializeSizeI6CBlockE{size_t}RKT_ii@Base 0.14.2~dfsg
  _Z16SHA256AutoDetectB5cxx11v@Base 0.15.0~~
  
(optional=templinst|arch-bits=64)_Z16WriteCompactSizeI11CHashWriterEvRT_m@Base 
0.14.2~dfsg
  
(optional=templinst|arch-bits=32)_Z16WriteCompactSizeI11CHashWriterEvRT_y@Base 
0.14.2~dfsg
@@ -58,8 +58,8 @@
  _Z19ComputeMerkleBranchRKSt6vectorI7uint256SaIS0_EEj@Base 0.14.2~dfsg
  (subst)_Z19SipHashUint256Extra{uint64_t}{uint64_t}RK7uint256j@Base 0.15.0~~
 #MISSING: 0.15.0~~# _Z20GetTransactionWeightRK12CTransaction@Base 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z20SerializeTransactionI11CHashWriter12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z20SerializeTransactionI13CSizeComputer12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z20SerializeTransactionI11CHashWriter12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z20SerializeTransactionI13CSizeComputer12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
  _Z22BlockWitnessMerkleRootRK6CBlockPb@Base 0.14.2~dfsg
  _Z22CheckSignatureEncodingRKSt6vectorIhSaIhEEjP13ScriptError_t@Base 
0.14.2~dfsg
  _Z27ComputeMerkleRootFromBranchRK7uint256RKSt6vectorIS_SaIS_EEj@Base 
0.14.2~dfsg
@@ -247,8 +247,8 @@
  (optional=templinst)_ZN9base_uintILj256EEmLERKS0_@Base 0.14.2~dfsg
  (optional=templinst)_ZN9base_uintILj256EEmLEj@Base 0.14.2~dfsg
  (optional=templinst)_ZN9base_uintILj256EErSEj@Base 0.14.2~dfsg
-#MISSING: 0.15.0~~# (optional=templinst)_ZN9prevectorILj28EhjiED1Ev@Base 
0.14.2~dfsg
-#MISSING: 0.15.0~~# (optional=templinst)_ZN9prevectorILj28EhjiED2Ev@Base 
0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# (optional=templinst)_ZN9prevectorILj28EhjiED1Ev@Base 
0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# (optional=templinst)_ZN9prevectorILj28EhjiED2Ev@Base 
0.14.2~dfsg
  _ZNK10CExtPubKey6DeriveERS_j@Base 0.11.0
  _ZNK10CExtPubKey6EncodeEPh@Base 0.11.0
  _ZNK10CSipHasher8FinalizeEv@Base 0.14.2~dfsg
@@ -314,14 +314,14 @@
  
(optional=templinst|arch-bits=32)_ZNSt6vectorI7uint256SaIS0_EE17_M_default_appendEj@Base
 0.14.2~dfsg
  
(optional=templinst|arch-bits=64)_ZNSt6vectorI7uint256SaIS0_EE17_M_default_appendEm@Base
 0.14.2~dfsg
  
_ZNSt6vectorI7uint256SaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.15.1~dfsg
- 
(optional=templinst)_ZNSt6vectorI7uint256SaIS0_EE19_M_emplace_back_auxIJRKS0_EEEvDpOT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_ZNSt6vectorI7uint256SaIS0_EE19_M_emplace_back_auxIJRKS0_EEEvDpOT_@Base
 0.14.2~dfsg
  
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE12emplace_backIJS1_EEEvDpOT_@Base
 0.14.2~dfsg
- 
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE13_M_insert_auxIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.14.2~dfsg
- 
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE13_M_insert_auxIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_ZNSt6vectorIS_IhSaIhEESaIS1_EE13_M_insert_auxIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.14.2~dfsg
+#MISSING: 

Bug#889126: fswatch FTBFS with gcc-7 7.3.0-1: symbol differences

[Adrian Bunk]

Source: fswatch
Version: 1.11.2+repack-5
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fswatch.html

...
   dh_makeshlibs -O--as-needed
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libfswatch9/DEBIAN/symbols doesn't match 
completely debian/libfswatch9.symbols
--- debian/libfswatch9.symbols (libfswatch9_1.11.2+repack-5_amd64)
+++ dpkg-gensymbolsqymY37   2018-02-01 18:10:24.164928689 -1200
@@ -1,15 +1,23 @@
 libfswatch.so.9 libfswatch9 #MINVER#
  FSW_ALL_EVENT_FLAGS@Base 1.11.2
+ 
_ZNSt5dequeINSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcSaIS5_EE17_M_reallocate_mapEmb@Base
 1.11.2+repack-5
+ 
_ZSteqIcEN9__gnu_cxx11__enable_ifIXsrSt9__is_charIT_E7__valueEbE6__typeERKNSt7__cxx1112basic_stringIS3_St11char_traitsIS3_ESaIS3_EEESE_@Base
 1.11.2+repack-5
+ 
_ZZNKSt7__cxx1112regex_traitsIcE16lookup_classnameIPKcEENS1_10_RegexMaskET_S6_bE12__classnames@Base
 1.11.2+repack-5
+ 
_ZZNKSt7__cxx1112regex_traitsIcE18lookup_collatenameIPKcEENS_12basic_stringIcSt11char_traitsIcESaIcEEET_SA_E14__collatenames@Base
 1.11.2+repack-5
+ 
_ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base
 1.11.2+repack-5
+ 
_ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base
 1.11.2+repack-5
+ 
_ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base
 1.11.2+repack-5
+ 
_ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base
 1.11.2+repack-5
  (c++|arch=!amd64 !armhf !kfreebsd-amd64 !x32 
)"__gnu_cxx::__enable_if::__type 
std::operator==(std::__cxx11::basic_string const&, std::__cxx11::basic_string const&)@Base" 1.10.0
  (c++)"__gnu_cxx::__normal_iterator > std::__unique<__gnu_cxx::__normal_iterator >, 
__gnu_cxx::__ops::_Iter_equal_to_iter>(__gnu_cxx::__normal_iterator >, __gnu_cxx::__normal_iterator >, 
__gnu_cxx::__ops::_Iter_equal_to_iter)@Base" 1.10.0
  (c++)"__gnu_cxx::__normal_iterator const*, 
std::vector, std::allocator > > > 
std::__find_if<__gnu_cxx::__normal_iterator const*, 
std::vector, std::allocator > > >, 
__gnu_cxx::__ops::_Iter_equals_val const> 
>(__gnu_cxx::__normal_iterator const*, 
std::vector, std::allocator, std::allocator > > 
> >, __gnu_cxx::__normal_iterator const*, 
std::vector, std::allocator > > >, 
__gnu_cxx::__ops::_Iter_equals_val const>, 
std::random_access_iterator_tag)@Base" 1.10.0
- (c++)"bool std::__detail::_Compiler::_M_expression_term(std::pair&, 
std::__detail::_BracketMatcher&)::{lambda(char)#1}::operator()(char) const@Base" 1.10.0
+#MISSING: 1.11.2+repack-5# (c++)"bool 
std::__detail::_Compiler::_M_expression_term(std::pair&, 
std::__detail::_BracketMatcher&)::{lambda(char)#1}::operator()(char) const@Base" 1.10.0
  (c++)"bool std::__detail::_Compiler::_M_expression_term(std::pair&, 
std::__detail::_BracketMatcher&)@Base" 1.10.0
- (c++)"bool std::__detail::_Compiler::_M_expression_term(std::pair&, 
std::__detail::_BracketMatcher

Bug#889073: Permission denied on /run/munin/munin-node.pid

[Jörg Frings-Fürst]

Hello,

I think systemd sets the pid file with root:root, but requested is
munin:root.


:/run/munin$ ls -l
insgesamt 4
-rw-r--r-- 1 root root 6 Feb  2 07:49 munin-node.pid



CU 
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.

Bug#887774: nmu: ace_6.4.5+dfsg-1

[Adrian Bunk]

Control: reassign -1 release.debian.org
Control: retitle -1 nmu: ace_6.4.5+dfsg-1
Control: notfound 701300 1.2.11a1-9
Control: close 701300
Control: close 888621

On Sat, Jan 27, 2018 at 08:53:30PM +, Barak A. Pearlmutter wrote:
> This is a recurrence of https://bugs.debian.org/701300 which was
> caused by libace being compiled with a different version of the
> compiler than ivtools, and these two versions mangling a particular
> symbol differently.

It is actually a different issue, caused by an ABI-breaking change
in glibc 2.26:

11:55 < aurel32> bunk: i am afraid so, it's mentionned in section 4.2 of the 
wiki
11:55 < aurel32> https://sourceware.org/glibc/wiki/Release/2.26

ACE already changed so-name after stretch and is expected to do so again,
so at least there won't be any stretch -> buster upgrade issues due to this
(but backporting ACE to stretch would be problematic).

> If libace (src:pkg-ace) could be tickled into a rebuild against the
> latest sid toolchain, that might solve the problem.

Correct, turning this into a binNMU request for
  nmu: ace_6.4.5+dfsg-1 . ANY . unstable . -m "Rebuild with glibc 2.26 ABI"

cu
Adrian

-- 

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

Processed: nmu: ace_6.4.5+dfsg-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #887774 [src:ivtools] ivtools FTBFS: libComTerp.so: undefined reference to 
`ACE_Event_Handler::handle_signal(int, siginfo_t*, ucontext_t*)'
Bug reassigned from package 'src:ivtools' to 'release.debian.org'.
No longer marked as found in versions ivtools/1.2.11a1-9 and ivtools/1.2.10a1-1.
No longer marked as fixed in versions ivtools/1.2.11a1-1.
> retitle -1 nmu: ace_6.4.5+dfsg-1
Bug #887774 [release.debian.org] ivtools FTBFS: libComTerp.so: undefined 
reference to `ACE_Event_Handler::handle_signal(int, siginfo_t*, ucontext_t*)'
Changed Bug title to 'nmu: ace_6.4.5+dfsg-1' from 'ivtools FTBFS: 
libComTerp.so: undefined reference to `ACE_Event_Handler::handle_signal(int, 
siginfo_t*, ucontext_t*)''.
> notfound 701300 1.2.11a1-9
Bug #701300 [src:ivtools] ivtools: ftbfs with GCC-4.8
No longer marked as found in versions ivtools/1.2.11a1-9.
> close 701300
Bug #701300 [src:ivtools] ivtools: ftbfs with GCC-4.8
Marked Bug as done
> close 888621
Bug #888621 [libace-dev] Regression, Please Rebuild
Marked Bug as done

-- 
701300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701300
887774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887774
888621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888080: Debdiff for the fix, delayed/2 NMU

[Thomas Goirand]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Since it's been a few days that this issue has been reassigned to your
package, and that there's no sign of activity, I have pushed the
attached fix into collab-maint, and uploaded the NMU to DELAYED/2.

If you do not agree with the fix, please let me know soon enough so that
I can dcut the upload.

I hope this helps,
Cheers,

Thomas Goirand (zigo)

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlpy2C4ACgkQq1PlA1ho
d6YBbBAAvC3GfuJi8SANDaw02WaoAkVWltEW18koJpHCMAeufAbRnn/c3y2LHDao
2kMnnifI1jQKheib6a0VnujYAo0PbsjZJdF40XeaV2/3cGZVAJhE/lyMF9qVyS1z
cegs6VUbYMJfktPLik2So/ugHgF1yloHUOYW5AtpLsQSrCgsjaIDO4SZBpB6Lz6G
5lc6/6tisJq9Wwqr1HZfJXJZ6iMhAym4fnCE3hi8iHAzFk8zmsvybtC+34XB4Yth
l6ZhkEvnROIRBRbW8IVkZOJDCfWM36+lFeqcYtlh+rdo9WYriG6/TOhXaagxxmSS
Hg+6cs23JTyc1SsJ8GqPuzOLzlQv6OPuoJWaqvY0YEKQB1wYnutf3u0B2D4SlaN9
DOOy7A6p9VZ9YU+JImj0EllHq0q4K1iagdnGPhIj2QIn5lpoM/nDsMcnl6m6Qz7r
Q8K0Sa7Jwf1B+M2p586lOCqTWlTng6Rhseirp5nKdIJ2P7Sy4MhX19tq4vm3XJJO
0tKTxShLMhTG55UxO7XQ4eKDjzk8q3P6PXVXzb7F5GB2Lt3jJSy1dnQ+QXLh6KD4
GOTEXIvFS5kGbjG4lnfsjMft+45NbG+nnn2yHGLcpYH3OadSaAL2DglfCLG6x6HJ
dfhBkk/4XxXO42yec/Ikav2P5ScLReblsAcbv8ast4TFBrmdZPo=
=PYpp
-END PGP SIGNATURE-
diff -Nru cmd2-0.7.7/debian/changelog cmd2-0.7.7/debian/changelog
--- cmd2-0.7.7/debian/changelog 2017-08-27 12:30:40.0 +
+++ cmd2-0.7.7/debian/changelog 2018-02-01 08:57:32.0 +
@@ -1,3 +1,10 @@
+cmd2 (0.7.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Added patch to make cmd2 work with newer pyperclip (Closes: #888080).
+
+ -- Thomas Goirand   Thu, 01 Feb 2018 08:57:32 +
+
 cmd2 (0.7.7-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru 
cmd2-0.7.7/debian/patches/fix-cmd2-not-working-with-newer-pyperclip.patch 
cmd2-0.7.7/debian/patches/fix-cmd2-not-working-with-newer-pyperclip.patch
--- cmd2-0.7.7/debian/patches/fix-cmd2-not-working-with-newer-pyperclip.patch   
1970-01-01 00:00:00.0 +
+++ cmd2-0.7.7/debian/patches/fix-cmd2-not-working-with-newer-pyperclip.patch   
2018-02-01 08:57:32.0 +
@@ -0,0 +1,35 @@
+Description: Fix cmd2 not working with newer pyperclip
+ Fixed bug due to pyperclip dependency radically changing its project structure
+ in latest version. This was cherry-picked form an upstream commit (ie: a patch
+ that was merged) on Github:
+  
https://github.com/python-cmd2/cmd2/pull/231/commits/5027f7cbcf2575dfc5a0c67068951c9ea4b9d7dd
+Author: Thomas Goirand 
+Bug-Debian: https://bugs.debian.org/888080
+Forwarded: not-needed
+Last-Update: 2018-02-01
+
+--- cmd2-0.7.7.orig/cmd2.py
 cmd2-0.7.7/cmd2.py
+@@ -46,6 +46,13 @@ from optparse import make_option
+ import pyparsing
+ import pyperclip
+ 
++# Newer versions of pyperclip are released as a single file, but older 
versions had a more complicated structure
++try:
++from pyperclip.exceptions import PyperclipException
++except ImportError:
++# noinspection PyUnresolvedReferences
++from pyperclip import PyperclipException
++
+ # On some systems, pyperclip will import gtk for its clipboard functionality.
+ # The following code is a workaround for gtk interfering with printing from a 
background
+ # thread while the CLI thread is blocking in raw_input() in Python 2 on Linux.
+@@ -330,7 +337,7 @@ try:
+ else:
+ # Try getting the contents of the clipboard
+ _ = pyperclip.paste()
+-except pyperclip.exceptions.PyperclipException:
++except PyperclipException:
+ can_clip = False
+ else:
+ can_clip = True
diff -Nru cmd2-0.7.7/debian/patches/series cmd2-0.7.7/debian/patches/series
--- cmd2-0.7.7/debian/patches/series2017-08-27 12:30:40.0 +
+++ cmd2-0.7.7/debian/patches/series2018-02-01 08:57:32.0 +
@@ -0,0 +1 @@
+fix-cmd2-not-working-with-newer-pyperclip.patch

Processed: Merge duplicates and add more affected packages

[Debian Bug Tracking System]

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

> reassign 888994 src:javacc-maven-plugin
Bug #888994 [libjavacc-maven-plugin-java] libjavacc-maven-plugin-java: plugin 
fails at runtime after jtb 1.4.12-1 update
Bug reassigned from package 'libjavacc-maven-plugin-java' to 
'src:javacc-maven-plugin'.
Ignoring request to alter found versions of bug #888994 to the same values 
previously set
Ignoring request to alter fixed versions of bug #888994 to the same values 
previously set
> forcemerge 887785 888994
Bug #887785 [src:javacc-maven-plugin] javacc-maven-plugin and build-rdeps FTBFS 
with jtb 1.4.12-1
Bug #888994 [src:javacc-maven-plugin] libjavacc-maven-plugin-java: plugin fails 
at runtime after jtb 1.4.12-1 update
Severity set to 'serious' from 'grave'
Added indication that 888994 affects 
src:activemq,src:commons-configuration,src:libcommons-jexl2-java,src:openjpa,src:cssparser,src:apache-mime4j,src:surefire,src:commons-configuration2,src:cobertura,src:javaparser,src:activemq-protobuf
Marked as found in versions javacc-maven-plugin/2.6-4.
Merged 887785 888994
> affects 887785 src:avro-java src:csvjdbc src:hawtbuf
Bug #887785 [src:javacc-maven-plugin] javacc-maven-plugin and build-rdeps FTBFS 
with jtb 1.4.12-1
Bug #888994 [src:javacc-maven-plugin] libjavacc-maven-plugin-java: plugin fails 
at runtime after jtb 1.4.12-1 update
Added indication that 887785 affects src:avro-java, src:csvjdbc, and src:hawtbuf
Added indication that 888994 affects src:avro-java, src:csvjdbc, and src:hawtbuf
> thanks
Stopping processing here.

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

Processed: Re: Bug#888953: gobby accesses the network during the build

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #888953 [src:gobby] gobby accesses the network during the build
Bug 888953 cloned as bug 889017
> reassign -2 gnome-doc-utils
Bug #889017 [src:gobby] gobby accesses the network during the build
Bug reassigned from package 'src:gobby' to 'gnome-doc-utils'.
No longer marked as found in versions gobby/0.6.0~20170204~e5c2d1-2.
Ignoring request to alter fixed versions of bug #889017 to the same values 
previously set
> retitle -2 gnome-doc-utils.make should forbid accessing the network
Bug #889017 [gnome-doc-utils] gobby accesses the network during the build
Changed Bug title to 'gnome-doc-utils.make should forbid accessing the network' 
from 'gobby accesses the network during the build'.

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

Processed: Re: Bug#888878: fails to restore signed backup

[Debian Bug Tracking System]

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

> tags 78 + unreproducible moreinfo
Bug #78 [duplicity] fails to restore signed backup
Added tag(s) moreinfo and unreproducible.
> severity 78 normal
Bug #78 [duplicity] fails to restore signed backup
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#888953: gobby accesses the network during the build

[Adrian Bunk]

Control: clone -1 -2
Control: reassign -2 gnome-doc-utils
Control: retitle -2 gnome-doc-utils.make should forbid accessing the network

On Wed, Jan 31, 2018 at 03:53:11PM +0100, Matthias Klose wrote:
> Package: src:gobby
> Version: 0.6.0~20170204~e5c2d1-2
> Severity: serious
> Tags: sid buster
> 
> While seen on a launchpad build, it looks like a missing build dependency,
> because it tries to access the docbookx.dtd from the network:
> 
> make[3]: Leaving directory '/<>/po'
> Making check in help
> make[3]: Entering directory '/<>/help'
> xmllint --noout --noent --path C:./C --xinclude --postvalid ./C/gobby.xml
> xmllint --noout --xinclude --dtdvalid
> 'http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd'
> gobby-C.omf
>...

There is also the related issue that 
/usr/share/gnome-doc-utils/gnome-doc-utils.make
shouldn't call xmllint without --nonet,
cloning a second bug for that.

cu
Adrian

-- 

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

Bug#885920: [firefox] Firefox window doesn't show under wayland

[Patrik Flykt]

I think I see the very same issue that affects also firefox 58.0.1-1.

To make matters more complex, Firefox starts with GNOME/wayland on an
laptop with an integrated Intel graphics chip just fine, but fails to
show a window on an desktop with AMD graphics card (Oland, Radeon R7
240/340) just as described in this bug. Poking with gdb on the second
process/thread on the desktop where the firefox window is not shown
gives the following output:

$ gdb -p 3414
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 3414
[New LWP 3429]
[New LWP 3430]
[New LWP 3431]
[New LWP 3432]
[New LWP 3433]
[New LWP 3434]
[New LWP 3435]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
38  ../sysdeps/unix/sysv/linux/x86_64/syscall.S: No such file or directory.
(gdb) where
#0  0x7f551369ce19 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f54fec7ebca in xshmfence_await () at 
/usr/lib/x86_64-linux-gnu/libxshmfence.so.1
#2  0x7f54ff6e522b in dri3_fence_await (buffer=0x7f54f619d4c0, 
draw=0x7f54fe103e98, c=)
at ../../../src/loader/loader_dri3_helper.c:187
#3  0x7f54ff6e522b in dri3_get_buffer (format=format@entry=4098, 
buffer_type=buffer_type@entry=
loader_dri3_buffer_front, draw=draw@entry=0x7f54fe103e98, 
driDrawable=)
at ../../../src/loader/loader_dri3_helper.c:1463
#4  0x7f54ff6e5f3d in loader_dri3_get_buffers (driDrawable=, 
format=4098, stamp=0x7f551308b800, loaderPrivate=0x7f54fe103e98, buffer_mask=2, 
buffers=0x7ffe3932ccb0) at ../../../src/loader/loader_dri3_helper.c:1578
#5  0x7f54fd61e976 in dri_image_drawable_get_buffers 
(statts_count=, statts=, images=, 
drawable=) at 
../../../../../src/gallium/state_trackers/dri/dri2.c:466
#6  0x7f54fd61e976 in dri2_allocate_textures (ctx=0x7f54fe11ce20, 
drawable=0x7f551308b800, statts=
0x7f54fe144c60, statts_count=1) at 
../../../../../src/gallium/state_trackers/dri/dri2.c:590
#7  0x7f54fd619e5c in dri_st_framebuffer_validate (stctx=, 
stfbi=, statts=
0x7f54fe144c60, count=1, out=0x7ffe3932ce50) at 
../../../../../src/gallium/state_trackers/dri/dri_drawable.c:85
#8  0x7f54fd4c03c9 in st_framebuffer_validate (stfb=0x7f54fe144800, 
st=st@entry=0x7f54f61c)
at ../../../src/mesa/state_tracker/st_manager.c:197
#9  0x7f54fd4c18a0 in st_api_make_current (stapi=, 
stctxi=0x7f54f61c, stdrawi=0x7f551308b800, streadi=0x7f551308b800) at 
../../../src/mesa/state_tracker/st_manager.c:995
#10 0x7f54fd6198f6 in dri_make_current (cPriv=, 
driDrawPriv=0x7f54f61ae840, driReadPriv=0x7f54f61ae840)
at ../../../../../src/gallium/state_trackers/dri/dri_context.c:280
#11 0x7f54fd618786 in driBindContext (pcp=, pdp=, prp=)
at ../../../../../../src/mesa/drivers/dri/common/dri_util.c:564
#12 0x7f54ff6df346 in dri3_bind_context (context=0x7f54fe103b40, 
old=, draw=35651586, read=35651586)
at ../../../src/glx/dri3_glx.c:199
#13 0x7f54ff6b21d9 in MakeContextCurrent (dpy=0x7f55130ca000, 
draw=35651586, read=35651586, gc_user=0x7f54fe103b40)
at ../../../src/glx/glxcurrent.c:228
#14 0x7f54ffbc21dd in  () at /usr/lib/x86_64-linux-gnu/libGLX.so.0
#15 0x7f54ffbc2bd5 in  () at /usr/lib/x86_64-linux-gnu/libGLX.so.0
#16 0x7f54ffbc41d6 in  () at /usr/lib/x86_64-linux-gnu/libGLX.so.0
#17 0x7f550752715c in  () at /usr/lib/firefox/libxul.so
#18 0x7f5507527377 in  () at /usr/lib/firefox/libxul.so
#19 0x7f550751ccee in  () at /usr/lib/firefox/libxul.so
#20 0x7f550752233f in  () at /usr/lib/firefox/libxul.so
#21 0x7f5507522b32 in  () at /usr/lib/firefox/libxul.so
#22 0x564ce39fb72c in  ()
#23 0x564ce39fae99 in  ()
#24 0x7f55135cdf2a in __libc_start_main (main=
0x564ce39fae30, argc=1, argv=0x7ffe3932eb28, init=, 
fini=, rtld_fini=, stack_end=0x7ffe3932eb18) at 
../csu/libc-start.c:310
#25 0x564ce39fb1aa in _start ()

Hope this helps a bit.

Bug#888917: ocrmypdf fails to run it's testsuite

[Matthias Klose]

Control: severity -1 important

On 01.02.2018 06:06, Sean Whitton wrote:
> control: tag -1 +moreinfo
> 
> Dear Matthias,
> 
> On Wed, Jan 31 2018, Matthias Klose wrote:
> 
>> The recent changelog reads:
>>
>>   * Disable test suite at package build time.
>> It now takes a prohibitively long time to run, so we are relying on
>> autopkgtest instead.
>>
>> Sorry, but this is one of the most lame excuses I have ever seen. Trying to 
>> run
>> it on my laptop in unstable needs 30 seconds.  However re-enabling it and
>> running it reveals
>>
>>   === 122 failed, 24 passed, 4 skipped in 33.92 seconds 
>>
>> these results are after adding tesseract-ocr qpdf unpaper as build 
>> dependencies.
> 
> Looking at the errors, I strongly suspect that this is because you are
> running the test suite on a tmpfs -- we have seen these permission
> errors before under those conditions.  Could you try running the test
> suite on a totally ordinary file system, please?

I tried running these in a chroot created with debootstrap, and manually
entering the chroot.

[sid]
type=directory
description=debian (sid)
directory=/srv/chroot/sid
users=doko
groups=sbuild

so this should be on an ordinary file system? unless the testsuite uses /tmp
mounted on a /tmpfs?

> I further suspect that the test suite took 30 seconds only because so
> many tests failed early.  In recent upstream versions, the test suite
> has never finished running on my laptop after leaving it for multiple
> hours.  When you run the test suite on a totally ordinary file system,
> please report how long it takes, and whether your laptop is very
> new/high spec.

well, it's a new one, two cores.

> I note that Policy does not require that a package be buildable under a
> tmpfs, and certainly does not require that its test suite run under a
> tmpfs.
> 
>> doubting that the primary reason for this change was build time ...
> 
> Several things:
> 
> 1) I ran the test suite using deb-o-matic[1] before uploading.  Needless
>to say, I would not have uploaded had there been failures.

which only runs on amd64 afaik.

> 2) I should have mentioned in the changelog that another reason for this
>change was to reduce the number of heavy build dependencies.
> 
>A further reason is that it reduces the amount of fragile code in
>d/rules needed to get the test suite running -- upstream's test suite
>is designed to be run on the installed package.
> 
> 3) I am of the view that very heavy test suites are better run under
>autopkgtest.  We will soon have testing migration gating on
>autopkgtest, and it is not clear to me that it makes sense for the
>process of stitching the .deb to abort when a single integration test
>fails.

I'm not sure about that.  I dislike packages like the whole KDE which disables
testing during the build and then rebuilds and runs tests in the autopkg tests.
It doesn't hinder broken packages into the archive.

>(Ideally tests would be separated into those that should abort the
>build and those that should not, but in the absence of this work
>being done, it is reasonable not to run any of them.)

I'm a bit biased here, because I saw the autopkg test failures first in 
launchpad:
http://autopkgtest.ubuntu.com/packages/o/ocrmypdf/bionic/amd64

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/ocrmypdf/20180130_155249_1faa5@/log.gz

but yes, there seem to be less failures

> 4) Your implicit comment that I lied in the changelog and disabled the
>test suite because I knew it would fail is entirely uncalled for.
>Please do not treat fellow package maintainers like that.

well, looking at the changelog is the way to see what is changed, and sometimes
why. I didn't see that in 2). But yes, I was feeling that you didn't tell
everything.

Now reduced the severity. Feel free to close it if you think that any tests
during the build is not necessary.