Bug#883795: marked as done (dms-core: dms-core.postrm removes /var/lib/bind9 on purge)

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 07:49:27 +
with message-id 
and subject line Bug#883795: fixed in dms 1.0.8.1-1
has caused the Debian Bug report #883795,
regarding dms-core: dms-core.postrm removes /var/lib/bind9 on purge
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.)


-- 
883795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.10.6+dfsg-5
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge.
According to policy 7.2 you cannot rely on the depends being available
during purge, only the essential packages are available for sure.

Filing this as important because a.) it's a clear policy violation (to
not clean up at purge) b.) having a piuparts clean archive is a release
goal since lenny and c.) this package being piuparts buggy blocks
packages depending on it from being tested by piuparts (and thus
possibly the detection of more severe problems).

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

  Purging configuration files for bind9 (1:9.10.6+dfsg-5) ...
  rmdir: failed to remove '/var/lib/bind': No such file or directory
  dpkg: error processing package bind9 (--purge):
   installed bind9 package post-removal script subprocess returned error exit 
status 1

This was observed while testing the dms-wsgi package, nut just bind9
itself. So a certain package combination seems to trigger it.
Anyway, postrm should not assume the stuff it wants to delete
must exist.


cheers,

Andreas


dms-wsgi_1.0.8-1.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dms
Source-Version: 1.0.8.1-1

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

Debian distribution maintenance software
pp.
Matthew Grant  (supplier of updated dms 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, 18 Jan 2018 20:14:22 +1300
Source: dms
Binary: dms-core dms-wsgi dms-dr dms dms-doc
Architecture: source amd64 all
Version: 1.0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: DMS Maintainers 
Changed-By: Matthew Grant 
Description:
 dms- bind9 DNS Management System, master server meta-package
 dms-core   - bind9 DNS Management System, core system
 dms-doc- bind9 DNS Management System, HTML documentation
 dms-dr - bind9 DNS Management System, DR scripts and setup.
 dms-wsgi   - bind9 DNS Management System, WSGI JSON http RPC backend.
Closes: 883795
Changes:
 dms (1.0.8.1-1) unstable; urgency=medium
 .
   * Add creation of /var/lib/bind/ds directory for DS
   * Fix removing /var/lib/bind on purge. (Closes: #883795)
Checksums-Sha1:
 5e4824142bfb4f1335217dc023acaf3fdd80b6d0 2118 dms_1.0.8.1-1.dsc
 56acfdd462891d863e17456c8bb77da8e036c8f9 2551693 dms_1.0.8.1.orig.tar.gz
 155f84d7f93498654a7dac63fa86c2343b86bff4 30096 dms_1.0.8.1-1.debian.tar.xz
 50c5d85c595b971a594bbf2251423acd4d148e0f 174184 dms-core_1.0.8.1-1_amd64.deb
 414ad5d9b5ed32419b7b1a50d564232fe7aed515 804148 dms-doc_1.0.8.1-1_all.deb
 062d6b94034a2cf3a56ade983062b578d253eda8 19920 dms-dr_1.0.8.1-1_amd64.deb
 f3e1e59fb75a061504a36668ab303efdc4a10117 15188 dms-wsgi_1.0.8.1-1_amd64.deb
 ddc06b160164d1cce74857214636d46a530845b1 8024 dms_1.0.8.1-1_amd64.buildinfo
 c75e69c0fca1a86e33d77eb888dbf8efcf372ce3 12602 dms_1.0.8.1-1_amd64.deb
Checksums-Sha256:
 1fd3ce3226bbfd1b22ea835a9acdebc5fd9aaa078a2398167c8e4421b54a12c2 2118 
dms_1.0.8.1-1.dsc
 9ff132bd600279d34b4d15faa6c9aeb8feee6212905e77442f3507a80cf2453a 2551693 
dms_1.0.8.1.orig.tar.gz
 387f58c4651d8e63cc2473e95aec2d053c70b82d718a8aba39d92799fd9e6d94 30096 
dms_1.0.8.1-1.debian.tar.xz
 cc7e686ce149c3b5f70adaad9c56681a184a3fe147996b23201d9591ddc8a8e0 174184 
dms-core_1.0.8.1-1_amd64.deb
 4bbde368534790079bb25ef421d88ad05fc276145d5f99ec0b53cc74fffa1e11 804148 
dms-doc_1.0.8.1-1_all.deb
 

Bug#887585: stealth: missing build dependency on texlive-latex-extra

[Adrian Bunk]

Source: stealth
Version: 4.01.09-1
Severity: serious

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

...
No post-processing required for this latex conversion
cp stealth.sty ../../tmp/manual/LaTeX
latex stealth.latex
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./stealth.latex
LaTeX2e <2017-04-15>
Babel <3.16> and hyphenation patterns for 3 language(s) loaded.
Original Yodl file: ../../release.yo
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.sty
This is `epsf.tex' v2.7.4 <14 February 2011>
) (./stealth.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)

Package hyperref Warning: Values of option `pdfpagemode':
(hyperref)* `UseNone'
(hyperref)* `UseOutlines'
(hyperref)* `UseThumbs'
(hyperref)* `FullScreen'
(hyperref)* `UseOC' (PDF 1.5)
(hyperref)* `UseAttachments' (PDF 1.6)
(hyperref)* An empty value disables the option.
(hyperref)Unknown value `None' on input line 4374.

(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))

Package hyperref Message: Driver (default): hdvips.

(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hdvips.def
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pdfmark.def
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))

! LaTeX Error: File `makecell.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name: 
! Emergency stop.
 
 
l.23 ^^M

Bug#887581: c++-annotations FTBFS with yodl 4.02.00-2

[Frank B. Brokken]

Dear Adrian Bunk, you wrote:
> 
> Source: c++-annotations
> Version: 10.9.0-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/c++-annotations.html
> 
> ...
> yodl2txt --no-warnings -o ../tmp/docs/txt/cplusplus.txt -l3 cplusplus
> Yodl2html 4.02.00
> Yodl: including file preamble
> preamble.yo:208: DEFINEMACRO: `nbsp' multiply defined

Oops... Thanks: I'll fix that later today.

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3

[Adrian Bunk]

Source: libjs-fetch
Version: 2.0.3-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/libjs-fetch-2.0.3'
xvfb-run -a -s "-screen 0 640x480x16" ./script/test
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pbuilder1'
Error loading resource http://localhost:3901/node_modules/mocha/mocha.css 
(203). Details: Error transferring 
http://localhost:3901/node_modules/mocha/mocha.css - server replied: Not Found
Error loading resource 
http://localhost:3901/node_modules/url-search-params/build/url-search-params.js 
(203). Details: Error transferring 
http://localhost:3901/node_modules/url-search-params/build/url-search-params.js 
- server replied: Not Found
Error loading resource http://localhost:3901/node_modules/mocha/mocha.js (203). 
Details: Error transferring http://localhost:3901/node_modules/mocha/mocha.js - 
server replied: Not Found
ReferenceError: Can't find variable: Mocha
ReferenceError: Can't find variable: suite
TypeError: mocha.run is not a function. (In 'mocha.run()', 'mocha.run' is 
undefined)
Likely due to external resource loading and timing, your tests require calling 
`window.initMochaPhantomJS()` before calling any mocha setup functions. See 
https://github.com/nathanboktae/mocha-phantomjs-core/issues/12
TypeError: Attempting to change the setter of an unconfigurable property.
TypeError: Attempting to change the setter of an unconfigurable property.
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pbuilder1'
Error loading resource http://localhost:3901/node_modules/mocha/mocha.css 
(203). Details: Error transferring 
http://localhost:3901/node_modules/mocha/mocha.css - server replied: Not Found
Error loading resource 
http://localhost:3901/node_modules/url-search-params/build/url-search-params.js 
(203). Details: Error transferring 
http://localhost:3901/node_modules/url-search-params/build/url-search-params.js 
- server replied: Not Found
Error loading resource http://localhost:3901/node_modules/mocha/mocha.js (203). 
Details: Error transferring http://localhost:3901/node_modules/mocha/mocha.js - 
server replied: Not Found
ReferenceError: Can't find variable: Mocha
Likely due to external resource loading and timing, your tests require calling 
`window.initMochaPhantomJS()` before calling any mocha setup functions. See 
https://github.com/nathanboktae/mocha-phantomjs-core/issues/12
TypeError: Attempting to change the setter of an unconfigurable property.
TypeError: Attempting to change the setter of an unconfigurable property.
debian/rules:28: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#887571: [debhelper-devel] Bug#887571: debhelper: dh lies about what it does, breaks builds by creating new files, etc

[Norbert Preining]

Hi Niels,

> I suspect it might be the shell.  Make resets SHELL to /bin/sh AFAIR and
> the error smells like a bashism with a non-bash shell.

> export CONFIG_SHELL=/bin/sh

This has been there since around 6 years ... so I am a bit surprised
that this might have an influence, but I am retesting just now ...

Thanks

Norbert

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

Bug#887582: FTBFS: test suite failures on 32-bit arches

[Tristan Seligmann]

Source: fish
Version: 2.7.1-2
Severity: serious
Tags: upstream
Justification: FTBFS

The test suite is failing on 32-bit arches in a somewhat inscrutable way. I am
investigating this but filing a bug to track the status so long.

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

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

-- no debconf information

Bug#887571: [debhelper-devel] Bug#887571: debhelper: dh lies about what it does, breaks builds by creating new files, etc

[Niels Thykier]

Niels Thykier:
> Control: tags -1 moreinfo
> 
> Norbert Preining:
>> Package: debhelper
>> Version: 11.1.2
>> Severity: serious
>> Justification: breaks other packages
>>
>> Dear DebHelper developers,
>>
>> thanks for your efforts, but it would be very helpful if debhelper/dh
>> would stick to what itself says it is doing.
>>
>> I am trying to build texlive-bin, and somewhere at/around the configure
>> stage files
>>   configure.lineno
>> are created, which break building:
>>   checking whether g++ accepts -g... no
>>   checking dependency style of g++... none
>>   checking what warning flags to pass to the Objective C++ compiler...
>>   ../../../texk/web2c/configure: 20010: ./configure.lineno: Syntax error: 
>> Bad fd number
>>   === configuring in web2c failed
>>
>> I confirmed the following:
>> * doing the same invocation of configure manually does NOT create
>>   configure.lineno and the build succeeds.
> 
> I suspect it might be the shell.  Make resets SHELL to /bin/sh AFAIR and
> the error smells like a bashism with a non-bash shell.
> 
> Could you please retest with "export SHELL=/bin/bash" set in your
> debian/rules (or a SHELL=/bin/bash in front of the dh_auto_configure call).
> 

Ah, just noticed you have the following in top of the rules file which
makes my above statement redundant.

"""
#!/usr/bin/make -f
# debian/rules file for texlive-bin

export SHELL=/bin/bash
export CONFIG_SHELL=/bin/sh
"""

 * When you test manually, do you also set CONFIG_SHELL to /bin/sh?
   (Just to eliminate a source of error/difference)

Thanks,
~Niels

Bug#887571: [debhelper-devel] Bug#887571: debhelper: dh lies about what it does, breaks builds by creating new files, etc

[Niels Thykier]

Control: tags -1 moreinfo

Norbert Preining:
> Package: debhelper
> Version: 11.1.2
> Severity: serious
> Justification: breaks other packages
> 
> Dear DebHelper developers,
> 
> thanks for your efforts, but it would be very helpful if debhelper/dh
> would stick to what itself says it is doing.
> 
> I am trying to build texlive-bin, and somewhere at/around the configure
> stage files
>   configure.lineno
> are created, which break building:
>   checking whether g++ accepts -g... no
>   checking dependency style of g++... none
>   checking what warning flags to pass to the Objective C++ compiler...
>   ../../../texk/web2c/configure: 20010: ./configure.lineno: Syntax error: Bad 
> fd number
>   === configuring in web2c failed
> 
> I confirmed the following:
> * doing the same invocation of configure manually does NOT create
>   configure.lineno and the build succeeds.

I suspect it might be the shell.  Make resets SHELL to /bin/sh AFAIR and
the error smells like a bashism with a non-bash shell.

Could you please retest with "export SHELL=/bin/bash" set in your
debian/rules (or a SHELL=/bin/bash in front of the dh_auto_configure call).

> * what dh says it is doing with 
> dh binary --no-act ...
>   is *different* from what is actually happening, since doing the exact
>   same things as listed by dh binary --no-act immediately breaks
> 
> Example for this (the reautoconf stage has already been done):
>   $ dh binary --no-act --with autoreconf --builddirectory Work
>   debian/rules override_dh_auto_configure
>   dh_auto_build -O--builddirectory=Work
>   dh_auto_test -O--builddirectory=Work
> > [...]
> 
> Best
> 
> Norbert
> 
> [...]

The missing options/incomplete cmd-line is related to #552276.

Thanks,
~Niels

Processed: Re: [debhelper-devel] Bug#887571: debhelper: dh lies about what it does, breaks builds by creating new files, etc

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #887571 [debhelper] debhelper: dh lies about what it does, breaks builds by 
creating new files, etc
Added tag(s) moreinfo.

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

Bug#887581: c++-annotations FTBFS with yodl 4.02.00-2

[Adrian Bunk]

Source: c++-annotations
Version: 10.9.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/c++-annotations.html

...
yodl2txt --no-warnings -o ../tmp/docs/txt/cplusplus.txt -l3 cplusplus
Yodl2html 4.02.00
Yodl: including file preamble
preamble.yo:208: DEFINEMACRO: `nbsp' multiply defined
Yodl: including file abstract
Yodl is processing a(n) report
Document title: C++ Annotations
Version 10.9.0
Yodl: including file overview
Yodl: including file intro
Yodl: including file intro/intro
Yodl: including file whatsnew
Yodl: including file intro/history
Yodl: including file intro/annohistory
Yodl: including file intro/cascpp
Yodl: including file intro/compiling
Yodl: including file intro/mswindows
Yodl: including file intro/compilesources
Yodl: including file intro/advantage
Yodl: including file intro/object
Yodl: including file intro/differences
Yodl: including file intro/main
Yodl: including file intro/eoln
Yodl: including file intro/type
Yodl: including file intro/overload
Yodl: including file intro/default
Yodl: including file intro/null
Yodl: including file intro/void
Yodl: including file intro/cplus
Yodl: including file intro/cfunc
Yodl: including file intro/header
Yodl: including file intro/local
Yodl: including file intro/typedef
Yodl: including file intro/struct
Yodl: including file intro/evaluation
Yodl: including file intro/attributes
Yodl: including file first
Yodl: including file first/first
Yodl: including file first/extensions
Yodl: including file first/const
Yodl: including file first/namespaces
Yodl: including file first/scope
Yodl: including file first/cout
Yodl: including file first/structs
Yodl: including file first/public
Yodl: including file first/cvscpp
Yodl: including file first/references
Yodl: including file first/rvalueref
Yodl: including file first/lvalues
Yodl: including file first/stronglytyped
Yodl: including file first/initializer
Yodl: including file first/auto
Yodl: including file first/binding
Yodl: including file first/using
Yodl: including file first/rangebased
Yodl: including file first/rawstring
Yodl: including file first/binary
Yodl: including file first/selectinit
Yodl: including file first/attributes
Yodl: including file first/datatypes
Yodl: including file first/bool
Yodl: including file first/wchar
Yodl: including file first/unicode
Yodl: including file first/longlongint
Yodl: including file first/sizet
Yodl: including file first/separators
Yodl: including file first/cast
Yodl: including file first/staticcast
Yodl: including file first/constcast
Yodl: including file first/reinterpretcast
Yodl: including file first/dynamiccast
Yodl: including file first/sharedcast
Yodl: including file first/keywords
Yodl: including file namespaces
Yodl: including file namespaces/intro
Yodl: including file namespaces/defining
Yodl: including file namespaces/declaring
Yodl: including file namespaces/closed
Yodl: including file namespaces/referring
Yodl: including file namespaces/directive
Yodl: including file namespaces/koenig
Yodl: including file namespaces/std
Yodl: including file namespaces/nesting
Yodl: including file namespaces/outside
Yodl: including file string
Yodl: including file string/string
Yodl: including file string/ops
Yodl: including file string/overview
Yodl: including file string/initializers
Yodl: including file string/iterators
Yodl: including file string/operators
Yodl: including file string/members
Yodl: including file string/convertors
Yodl: including file iostreams
Yodl: including file iostreams/intro
Yodl: including file iostreams/headers
Yodl: including file iostreams/iosbase
Yodl: including file iostreams/ios
Yodl: including file iostreams/conditions
Yodl: including file iostreams/formatting
Yodl: including file iostreams/formatmembers
Yodl: including file iostreams/flags
Yodl: including file iostreams/output
Yodl: including file iostreams/ostream
Yodl: including file iostreams/ostreamwrite
Yodl: including file iostreams/ostreamseek
Yodl: including file iostreams/ostreamflush
Yodl: including file iostreams/ofstream
Yodl: including file iostreams/outmodes
Yodl: including file iostreams/ostringstream
Yodl: including file iostreams/input
Yodl: including file iostreams/istream
Yodl: including file iostreams/istreamread
Yodl: including file iostreams/istreamseek
Yodl: including file iostreams/ifstream
Yodl: including file iostreams/istringstream
Yodl: including file iostreams/copying
Yodl: including file iostreams/coupling
Yodl: including file iostreams/moving
Yodl: including file iostreams/redirection
Yodl: including file iostreams/readwrite
Yodl: including file classes
Yodl: including file classes/intro
Yodl: including file classes/construc
Yodl: including file classes/application
Yodl: including file classes/arguments
Yodl: including file classes/order
Yodl: including file classes/ambiguity
Yodl: including file classes/types
Yodl: including file classes/parentheses
Yodl: including file classes/existingtypes
Yodl: 

Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Michalis Kamburelis]

The problem is caused by the different directories used by new FPC
3.0.4 packages (compared to previous versions of FPC in Debian).

Doing

  ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"

doesn't work, since /usr/lib/fpc/3.0.4 does not exist. This works:

  ./fpmake --globalunitdir="/usr/lib/x86_64-linux-gnu/fpc/3.0.4"

To fix this, I suggest to

- Change / define the $FPCDIR variable inside Debian build scripts, to
point to the new correct directory.

- Or create a symlink /usr/lib/fpc/3.0.4 ->
/usr/lib/x86_64-linux-gnu/fpc/3.0.4 .

Regards,
Michalis

Bug#887572: marked as done (libkres-dev: missing Depends: libkres4 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Thu, 18 Jan 2018 04:34:24 +
with message-id 
and subject line Bug#887572: fixed in knot-resolver 1.5.1-2
has caused the Debian Bug report #887572,
regarding libkres-dev: missing Depends: libkres4 (= ${binary:Version})
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.)


-- 
887572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkres-dev
Version: 1.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m23.7s ERROR: FAIL: Broken symlinks:
  /usr/lib/libkres.so -> libkres.so.4


cheers,

Andreas


libkres-dev_1.5.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 1.5.1-2

We believe that the bug you reported is fixed in the latest version of
knot-resolver, 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.
Daniel Kahn Gillmor  (supplier of updated knot-resolver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jan 2018 23:23:45 -0500
Source: knot-resolver
Binary: knot-resolver knot-resolver-module-http knot-resolver-doc libkres4 
libkres-dev
Architecture: source
Version: 1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Daniel Kahn Gillmor 
Description:
 knot-resolver - caching, DNSSEC-validating DNS resolver
 knot-resolver-doc - Documentation for Knot Resolver
 knot-resolver-module-http - HTTP/2 module for Knot Resolver
 libkres-dev - caching, DNSSEC-validating DNS resolver (shared library developme
 libkres4   - caching, DNSSEC-validating DNS resolver (shared library)
Closes: 887572
Changes:
 knot-resolver (1.5.1-2) unstable; urgency=medium
 .
   * libkres-dev Depends on libkres4 (Closes: #887572)
   * Standards-Version: bump to 4.1.3 (no changes needed)
   * move Vcs-* to salsa.debian.org
Checksums-Sha1:
 53c1c7cd042bb98ea3d03fcf2264510c03456580 2850 knot-resolver_1.5.1-2.dsc
 edad232f3f4a7222e90842b3d78d314af9e20d71 407620 
knot-resolver_1.5.1-2.debian.tar.xz
 99d4d6e27a2c63c982708d6f710d6e32ed7cc1ea 10902 
knot-resolver_1.5.1-2_amd64.buildinfo
Checksums-Sha256:
 9008d19a30ebc17afa1d37ac8bc9169c2a5c6736ead78b114d14fc34e738b23b 2850 
knot-resolver_1.5.1-2.dsc
 4bb839330bdae56aa904578e4aa4236cc6ecef5839281d14f6c057d2509ffe8d 407620 
knot-resolver_1.5.1-2.debian.tar.xz
 0934630f0763a4c8d61cf0d98eec98d8c4666a00fad80d05383474ec12d1e8cc 10902 
knot-resolver_1.5.1-2_amd64.buildinfo
Files:
 a8225daff3b9ac66c995509fb7634cf6 2850 net optional knot-resolver_1.5.1-2.dsc
 bc9dd2f9e6d36036fe8a098128dbe151 407620 net optional 
knot-resolver_1.5.1-2.debian.tar.xz
 1993fa05c1228ee81df27d697dc253de 10902 net optional 
knot-resolver_1.5.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEzicvlOwymaWlnoHjyu+ogyFnUzMFAlpgIk8ACgkQyu+ogyFn
UzMjsw/7BD9yyYy1svoE2AgfEXfdZKl25EOmeblAU8re54rk2AZXgOT3nJ9gHHCc
BYVZ8MivMOCMpHnVv1b8IPWJTkhjLdAGmju8E06mxv5tFX47YFapLpF3F1F5IGzu
28nV1RdtKG60q84PKVajlN44HKylxjTvamB8vPTdJeOWpyyI/UzpYVDEH+3G9dTQ
tLU1zEdALWCR5Q99ChoyRihGPxdeLMzD92cfl8TBSrPxRGclSmvRWQKEM0X8VPfd
uXFiry4IX83JMYtfpLRDJpRaOWYui5UQt+g6+35qsTIgsXD7PRIiwTVJm/wjw0n6
FgBAbKTs3i46zIwt7mVnGjpDphZi6fNAKLTJEJ20XSoA08v54BFG6Dbo+jC4Q0GP
CtsRdzVkkbNtSOkyZGU0aILTwl0Cqpj45RqUIXcIK6AmQaaSqBwg5oUNqEJLmbz9
+0kWiguGftOCW6t4uG4ZBkabbrm4sjlu8/oS6GTyPTuywtMxVjQCXN11jjZSy354
pWRdbc3DB9hyb+RwHu5hVjoeLlxCUyiAW9iXHGLdl/dbyCx0UMRnbTW5rlB+zUzn
lrXJM8ydyNx/abcLZagWTIsSBxZOYQyFaUnqJ/ESIqiLropMxiblCTZkaX4dpHHR
s6PKBN8/Rb87dGDnM2g6aUEY4uMJaLBrpldanTochBJqWnMRVFc=
=dRGI
-END PGP SIGNATURE End Message ---

Bug#887580: gmime2.6 FTBFS with gtk-doc-tools 1.27-1

[Adrian Bunk]

Source: gmime2.6
Version: 2.6.23+dfsg1-1
Severity: serious

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

...
gtkdoc-mkdb --module=gmime --output-format=xml --expand-content-files="" 
--main-sgml-file=gmime-docs.sgml ${_source_dir} --sgml-mode --output-format=xml 
--ignore-files=trio
Traceback (most recent call last):
  File "/usr/bin/gtkdoc-mkdb", line 61, in 
mkdb.Run(options)
  File "/usr/share/gtk-doc/python/gtkdoc/mkdb.py", line 282, in Run
ReadSourceDocumentation(sdir, suffix_list, source_dirs, ignore_files)
  File "/usr/share/gtk-doc/python/gtkdoc/mkdb.py", line 3641, in 
ReadSourceDocumentation
ScanSourceFile(fname, ignore_files)
  File "/usr/share/gtk-doc/python/gtkdoc/mkdb.py", line 3682, in ScanSourceFile
for line in SRCFILE:
  File "/usr/lib/python2.7/codecs.py", line 701, in next
return self.reader.next()
  File "/usr/lib/python2.7/codecs.py", line 632, in next
line = self.readline()
  File "/usr/lib/python2.7/codecs.py", line 547, in readline
data = self.read(readsize, firstline=True)
  File "/usr/lib/python2.7/codecs.py", line 494, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xad in position 0: invalid 
start byte
Makefile:730: recipe for target 'sgml-build.stamp' failed
make[5]: *** [sgml-build.stamp] Error 1

Bug#887579: binaryornot FTBFS with python-hypothesis 3.44.1-1

[Adrian Bunk]

Source: binaryornot
Version: 0.4.4+dfsg-1
Severity: serious

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

...
==
ERROR: test_never_crashes (tests.test_check.TestDetectionProperties)
--
Traceback (most recent call last):
  File "/build/1st/binaryornot-0.4.4+dfsg/tests/test_check.py", line 214, in 
test_never_crashes
def test_never_crashes(self, data):
  File "/usr/lib/python2.7/dist-packages/hypothesis/core.py", line 1002, in 
wrapped_test
state.run()
  File "/usr/lib/python2.7/dist-packages/hypothesis/core.py", line 727, in run
runner.run()
  File 
"/usr/lib/python2.7/dist-packages/hypothesis/internal/conjecture/engine.py", 
line 470, in run
self._run()
  File 
"/usr/lib/python2.7/dist-packages/hypothesis/internal/conjecture/engine.py", 
line 868, in _run
self.generate_new_examples()
  File 
"/usr/lib/python2.7/dist-packages/hypothesis/internal/conjecture/engine.py", 
line 760, in generate_new_examples
HealthCheck.large_base_example
  File "/usr/lib/python2.7/dist-packages/hypothesis/internal/healthcheck.py", 
line 38, in fail_health_check
raise FailedHealthCheck(message, label)
FailedHealthCheck: The smallest natural example for your test is extremely 
large. This makes it difficult for Hypothesis to generate good examples, 
especially when trying to reduce failing ones at the end. Consider reducing the 
size of your data if it is of a fixed size. You could also fix this by 
improving how your data shrinks (see 
https://hypothesis.readthedocs.io/en/latest/data.html#shrinking for details), 
or by introducing default values inside your strategy. e.g. could you replace 
some arguments with their defaults by using one_of(none(), 
some_complex_strategy)?
See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more 
information about this. If you want to disable just this health check, add 
HealthCheck.large_base_example to the suppress_health_check settings for this 
test.

--
Ran 44 tests in 0.985s

FAILED (errors=1, expected failures=1)
Test failed: 
You can add @seed(221414468027289032423022124386177593491) to this test to 
reproduce this failure.
error: Test failed: 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25

Bug#887578: bioperl-run FTBFS: t/Bowtie.t failures

[Adrian Bunk]

Source: bioperl-run
Version: 1.7.2-2
Severity: serious

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

...
Test Summary Report
---
t/Bowtie.t  (Wstat: 512 Tests: 61 Failed: 2)
  Failed tests:  43, 45
  Non-zero exit status: 2
Files=72, Tests=1690, 314 wallclock secs ( 0.57 usr  0.21 sys + 243.57 cusr 
10.84 csys = 255.19 CPU)
Result: FAIL
Failed 1/72 test programs. 2/1690 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
debian/rules:32: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2

Bug#887577: ocamlnet FTBFS with nettle 3.4-1

[Adrian Bunk]

Source: ocamlnet
Version: 4.1.2-2
Severity: serious

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

...
In file included from nettls_nettle_bindings_stubs.c:24:0:
nettls_nettle_bindings_stubs.c:120:36: error: 'nettle_get_ciphers' declared as 
function returning an array
 const struct nettle_cipher * const nettle_ciphers[] = {
^
nettls_nettle_bindings_stubs.c:120:14: error: function 'nettle_get_ciphers' is 
initialized like a variable
 const struct nettle_cipher * const nettle_ciphers[] = {
  ^
In file included from nettls_nettle_bindings_stubs.c:24:0:
nettls_nettle_bindings_stubs.c:120:36: error: conflicting types for 
'nettle_get_ciphers'
 const struct nettle_cipher * const nettle_ciphers[] = {
^
/usr/include/nettle/nettle-meta.h:73:1: note: previous declaration of 
'nettle_get_ciphers' was here
 nettle_get_ciphers (void);
 ^~
nettls_nettle_bindings_stubs.c:121:3: error: invalid initializer
   _aes128,
   ^

Bug#887576: mupen64plus-qt FTBFS with libquazip5-headers 0.7.3-3

[Adrian Bunk]

Source: mupen64plus-qt
Version: 1.10-2
Severity: serious

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

...
src/emulation/emulatorhandler.cpp:42:10: fatal error: quazip/quazip.h: No such 
file or directory
 #include 
  ^
compilation terminated.
Makefile:608: recipe for target 'emulatorhandler.o' failed
make[1]: *** [emulatorhandler.o] Error 1

Bug#887575: castle-game-engine FTBFS with fpc 3.0.4

[Adrian Bunk]

Source: castle-game-engine
Version: 6.2+dfsg1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/castle-game-engine.html

...
--- Building
dh_testdir
# Build the real engine
/usr/bin/make all
make[1]: Entering directory '/build/1st/castle-game-engine-6.2+dfsg1'
/usr/bin/make --no-print-directory build-using-fpmake
fpc fpmake.pp
Free Pascal Compiler version 3.0.4+dfsg-13 [2018/01/12] for x86_64
Copyright (c) 1993-2017 by Florian Klaempfl and others
Target OS: Linux for x86-64
Compiling fpmake.pp
Linking fpmake
/usr/bin/ld.bfd: warning: link.res contains output sections; did you forget -T?
351 lines compiled, 0.4 sec
Running fpmake. If this fails saying that "rtl" is not found, remember to set 
FPCDIR environment variable, see http://wiki.freepascal.org/FPMake .
if [ '(' -n "/usr/lib/fpc/3.0.4" ')' -a \
 '(' 3.0.4 '!=' '2.6.4' ')' -a \
 '(' 3.0.4 '!=' '2.6.2' ')' ]; then \
   ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4" -v -o -Ur; \
else \
   ./fpmake -v -o -Ur; \
fi
The installer encountered the following error:
Could not find unit directory for dependency package "rtl"
Makefile:60: recipe for target 'build-using-fpmake' failed
make[2]: *** [build-using-fpmake] Error 1

Bug#887573: pytest-pylint: FTBFS and Debci failure with python3-astroid 1.6.0-1

[Adrian Bunk]

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

Bug#887572: libkres-dev: missing Depends: libkres4 (= ${binary:Version})

[Andreas Beckmann]

Package: libkres-dev
Version: 1.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m23.7s ERROR: FAIL: Broken symlinks:
  /usr/lib/libkres.so -> libkres.so.4


cheers,

Andreas


libkres-dev_1.5.1-1.log.gz
Description: application/gzip

Bug#887571: debhelper: dh lies about what it does, breaks builds by creating new files, etc

[Norbert Preining]

Package: debhelper
Version: 11.1.2
Severity: serious
Justification: breaks other packages

Dear DebHelper developers,

thanks for your efforts, but it would be very helpful if debhelper/dh
would stick to what itself says it is doing.

I am trying to build texlive-bin, and somewhere at/around the configure
stage files
  configure.lineno
are created, which break building:
  checking whether g++ accepts -g... no
  checking dependency style of g++... none
  checking what warning flags to pass to the Objective C++ compiler...
  ../../../texk/web2c/configure: 20010: ./configure.lineno: Syntax error: Bad 
fd number
  === configuring in web2c failed

I confirmed the following:
* doing the same invocation of configure manually does NOT create
  configure.lineno and the build succeeds.
* what dh says it is doing with 
dh binary --no-act ...
  is *different* from what is actually happening, since doing the exact
  same things as listed by dh binary --no-act immediately breaks

Example for this (the reautoconf stage has already been done):
  $ dh binary --no-act --with autoreconf --builddirectory Work
  debian/rules override_dh_auto_configure
  dh_auto_build -O--builddirectory=Work
  dh_auto_test -O--builddirectory=Work

But doing
  $ debian/rules override_dh_auto_configure
breaks becasue it does not change into Work before calling configure.

Adding the obviously necessary
  DH_INTERNAL_BUILDFLAGS=1
  DH_INTERNAL_OPTIONS=-O--builddirectory=Work
  DH_INTERNAL_OVERRIDE=dh_auto_configure
make the above command work, but somewhere/somehow starts creating
configure.lineno files, while doing the configure.

Calling make -f debian/rules binary I see the following:
$ make -f debian/rules binary
dh binary --with autoreconf --builddirectory Work
   debian/rules override_dh_auto_configure
make[1]: Entering directory 
'/home/norbert/Development/TeX/debian/git/build-area/texlive-bin-2018.20180118.46355'
# we have to make sure that the mendex test case that is added
# by a patch is executable
chmod 0755 texk/mendexk/tests/mendex.test
# run out configure script
dh_auto_configure -- -C --prefix=/usr   \
--datarootdir=/usr/share/texlive\
--disable-native-texlive-build  \
 OTHER configure args
--enable-ipc
cd Work && ../configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdi
  
configure: creating cache config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc

and at this time
  configure.lineno
is already existing, and propagated down the tree and breaking the build
builds.

But doing by hand, EVEN with the above three env variables set, doing
only the
  cd Work && ../configure --build=x86_64-lin ...
part does NOT create configure.lineno.


Also running
  dh_auto_configure -- -C --prefix=/usr \
--datarootdir=/usr/share/texlive\
  
does NOT create configure.lineno.

As a consequence, the only remaining candidate is that 
  dh
does *something*else* before calling the targets or setting env vars.

This is extremely difficult to debug without a proper documentation and
completely unreproducible behaviour from dh.

It is hard to guess what happens here, and I would be very grateful for
an expanation what else dh is doing before calling the actual things it
says it is calling.

Best

Norbert

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

Kernel: Linux 4.14.13 (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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debhelper depends on:
ii  autotools-dev20171216.1
ii  binutils 2.29.1-13
ii  dh-autoreconf15
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.4
ii  dpkg-dev 1.19.0.4
ii  file 1:5.32-1
ii  libdpkg-perl 1.19.0.4
ii  man-db   2.7.6.1-4
ii  perl 5.26.1-4
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  
pn  dwz  

-- no debconf information

Bug#887570: libsuitesparse-dev: missing Depends: libgraphblas1 (= ${binary:Version})

[Andreas Beckmann]

Package: libsuitesparse-dev
Version: 1:5.1.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m26.2s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libgraphblas.so -> libgraphblas.so.1


cheers,

Andreas


libsuitesparse-dev_1:5.1.2-1.log.gz
Description: application/gzip

Bug#887569: lldpad-dev: missing Depends: lldpad (= ${binary:Version})

[Andreas Beckmann]

Package: lldpad-dev
Version: 1.0.1+git20150824.036e314-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m23.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/liblldp_clif.so -> liblldp_clif.so.1.0.0


I'm only slightly questioning the package names ...


cheers,

Andreas


lldpad-dev_1.0.1+git20150824.036e314-1.log.gz
Description: application/gzip

Processed: Re: redis-sentinel: Please remove dependency on redis-server

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #884321 {Done: Chris Lamb } [redis-sentinel] 
redis-sentinel: Please remove dependency on redis-server
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions redis/5:4.0.6-2.
> severity -1 serious
Bug #884321 [redis-sentinel] redis-sentinel: Please remove dependency on 
redis-server
Severity set to 'serious' from 'wishlist'

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

Bug#887567: node-node-uuid: broken symlink: /usr/lib/nodejs/node-uuid/index.js -> ../../../share/javascript/node-uuid/node-uuid.js

[Andreas Beckmann]

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

Processed: node-node-uuid: broken symlink: /usr/lib/nodejs/node-uuid/index.js -> ../../../share/javascript/node-uuid/node-uuid.js

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + node-sqlite3
Bug #887567 [node-node-uuid] node-node-uuid: broken symlink: 
/usr/lib/nodejs/node-uuid/index.js -> 
../../../share/javascript/node-uuid/node-uuid.js
Added indication that 887567 affects node-sqlite3

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

Processed: affects 886847, found 857659 in 8.1.9+dfsg-7

[Debian Bug Tracking System]

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

> affects 886847 + python3-lib389
Bug #886847 [python3-ldap,python3-pyldap] python3-ldap,python3-pyldap: error 
when trying to install together
Added indication that 886847 affects python3-lib389
> found 857659 8.1.9+dfsg-7
Bug #857659 [gridengine-client] gridengine-client: broken symlink: 
/var/lib/gridengine/jobsbin -> /usr/lib/gridengine/jobsbin
Marked as found in versions gridengine/8.1.9+dfsg-7.
> thanks
Stopping processing here.

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

Bug#887566: r-cran-rhandsontable: broken symlink: /usr/lib/R/site-library/rhandsontable/htmlwidgets/lib/jquery/jquery.min.js -> usr/share/javascript/jquery/jquery.min.js

[Andreas Beckmann]

Package: r-cran-rhandsontable
Version: 0.3.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

1m2.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/R/site-library/rhandsontable/htmlwidgets/lib/jquery/jquery.min.js -> 
usr/share/javascript/jquery/jquery.min.js

That target should probably have been absolute ...


Assuming the missing jquery breaks functionality, I'm setting the severity to 
serious.



cheers,

Andreas


r-cran-rhandsontable_0.3.4+dfsg-1.log.gz
Description: application/gzip

Processed: reassign 887454 to console-bridge, tagging 887161, tagging 887364

[Debian Bug Tracking System]

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

> reassign 887454 console-bridge
Bug #887454 [console_bridge] console_bridge: Update console_bridge package to 
version 0.4.0
Warning: Unknown package 'console_bridge'
Bug reassigned from package 'console_bridge' to 'console-bridge'.
Ignoring request to alter found versions of bug #887454 to the same values 
previously set
Ignoring request to alter fixed versions of bug #887454 to the same values 
previously set
> tags 887161 + sid buster
Bug #887161 [src:llvm-toolchain-3.8] llvm-toolchain-3.8: keep out of testing
Added tag(s) sid and buster.
> tags 887364 + sid buster pending
Bug #887364 {Done: Nicholas Breen } [src:votca-csg] 
votca-csg FTBFS with gromacs 2018-1
Added tag(s) buster, pending, and sid.
> thanks
Stopping processing here.

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

Bug#873417: pocl: Please update to llvm-toolchain 4.0 or, better, 5.0

[Andreas Beckmann]

On 2018-01-17 06:31, Andreas Beckmann wrote:
> Looks like we need to move to pocl 1.0 and llvm 4.0, unfortunately
> that will need another pass through NEW, since the SOVERSION was bumped.

1.0 is in experimental/NEW, still using llvm 3.9 to avoid the build
failure on i386

0.14 has been switched to llvm 4.0 in sid, the failure on i386 is
expected, primarily this was to test whether any other architecture
builds pocl with 4.0 (and collect symbols)

next upload will be pocl-1.0+llvm-4.0 once 1.0 has cleared NEW and I did
something against this single failure (probably by ignoring it)

The repository is now on salsa.debian.org, the old one on alioth is locked.

https://salsa.debian.org/opencl-team/pocl.git
g...@salsa.debian.org:opencl-team/pocl.git


Andreas

Bug#884294: Anyone looking at this bug?

[olivier sallou]

This bug introduce reverse dependency package issues that will lead to
their removal.
For some packages in debianmed, i could patch to remove python influxdb use
(which makes use of pandas). This would remove some features but would keep
packages in the meanwhile
 But this may not be so simple for other packages.

Thanks

Olivier

Bug#887479: marked as done (libpdfbox2-java FTBFS: dh_installexamples fails)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 21:35:10 +
with message-id 
and subject line Bug#887479: fixed in libpdfbox2-java 2.0.8-2
has caused the Debian Bug report #887479,
regarding libpdfbox2-java FTBFS: dh_installexamples fails
to be marked as done.

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

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


-- 
887479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdfbox2-java
Version: 2.0.8-1
Severity: serious

Some recent change in unstable makes libpdfbox2-java FTBFS:

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

...
dh_installexamples
find /build/1st/libpdfbox2-java-2.0.8/debian/libpdfbox2-java-doc/ -type d 
-empty -delete
rm 
/build/1st/libpdfbox2-java-2.0.8/debian/libpdfbox2-java-doc/usr/share/doc/libpdfbox2-java-doc/examples/pom.xml.save
rm: cannot remove 
'/build/1st/libpdfbox2-java-2.0.8/debian/libpdfbox2-java-doc/usr/share/doc/libpdfbox2-java-doc/examples/pom.xml.save':
 No such file or directory
debian/rules:10: recipe for target 'override_dh_installexamples' failed
make[1]: *** [override_dh_installexamples] Error 1
--- End Message ---
--- Begin Message ---
Source: libpdfbox2-java
Source-Version: 2.0.8-2

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libpdfbox2-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jan 2018 21:59:20 +0100
Source: libpdfbox2-java
Binary: libpdfbox2-java libpdfbox2-java-doc libfontbox2-java 
libfontbox2-java-doc
Architecture: source
Version: 2.0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libfontbox2-java - Java font library
 libfontbox2-java-doc - Java font library (Documentation)
 libpdfbox2-java - PDF library for Java
 libpdfbox2-java-doc - PDF library for Java (documentation)
Closes: 887479
Changes:
 libpdfbox2-java (2.0.8-2) unstable; urgency=medium
 .
   * Use compat level 11.
   * Remove obsolete rm command in debian/rules.
 Thanks to Adrian Bunk for the report. (Closes: #887479)
   * Declare compliance with Debian Policy 4.1.3.
Checksums-Sha1:
 192ea19d045387d7d21e62c525c2872b13a2a274 2555 libpdfbox2-java_2.0.8-2.dsc
 42d6336a165f888fdf05e23e68dd8707cabac4c6 8996 
libpdfbox2-java_2.0.8-2.debian.tar.xz
 1b20ae65aa84949abf33fe1b3eae934806edf996 16892 
libpdfbox2-java_2.0.8-2_amd64.buildinfo
Checksums-Sha256:
 87ac5b0dc39ea793a5f60ffd1e9e7e50f72c8a431f7cf58c65a7f688e324fe4b 2555 
libpdfbox2-java_2.0.8-2.dsc
 d8808ddb466003515bd109be69650d734eca3c7ff0d8299fb216bfdef9b63809 8996 
libpdfbox2-java_2.0.8-2.debian.tar.xz
 cd6ac2da3d35bffc0cbeef2ca068813213cbe4a7dbef1022513df5b70cf75e21 16892 
libpdfbox2-java_2.0.8-2_amd64.buildinfo
Files:
 de3a9026dd959341d06a483be80b24c1 2555 java optional libpdfbox2-java_2.0.8-2.dsc
 8dba3020fb7d302587fb9971e0144281 8996 java optional 
libpdfbox2-java_2.0.8-2.debian.tar.xz
 f6e6e04963c9728be297da104a0e3938 16892 java optional 
libpdfbox2-java_2.0.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlpfu21fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkuqcP/1FO8JNt0S7ExZym1tbF6l/C8+wjMB92JNqA
M+/8obX4qWu0ZD9x0L0vBU6rSO6+LtV963Ut1XRaYbx3JcYI/5tMhTrVtgrSjdLL
Nvq8223A7gH4qkFw0jbSCFgqLYNErblBEf62h+W00ANhSJUoqtoBO5XFTZxrKu6p
NGRYZwQxiX/oSnpIliHIwtqyV5pJ1+81yuVklVGwKgZiuOS+ch5Ct6LtyT4qJrlY
dO2HnlYMoFvMLXnKBOUHlKTmn2gA1DBpc+2AGxH30GjI9S1LrRuxCZbqlTncwmEv
KcElzINit0V5+APDRJQvPGsJmQB83pXPuICu21EOt94C13u/PWhLkVlC6/qY4pwi
O3KgM+i0w8trOrCy+fJcpFVa9mraADVCjCwXQvuDm5wOdvJWOXCHPKfvuuY7wEVX

Bug#886852: marked as done (nvidia-graphics-drivers: CVE-2017-5753/CVE-2017-5715 (spectre), CVE-2017-5754 (meltdown))

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 21:11:15 +
with message-id 
and subject line Bug#886852: fixed in nvidia-graphics-drivers-legacy-340xx 
340.106-1
has caused the Debian Bug report #886852,
regarding nvidia-graphics-drivers: CVE-2017-5753/CVE-2017-5715 (spectre), 
CVE-2017-5754 (meltdown)
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.)


-- 
886852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 375.82-1~deb9u1
Severity: critical

Hi,

NVidia upgraded their blob to version 384.111 in order to fix Spectre /
Meltdown vulnerability. It turns out that the 375.xx branch is no longer
supported, so we cannot expect getting driver patches for the current
stretch drivers.

More details on this bulletin :
https://nvidia.custhelp.com/app/answers/detail/a_id/4611

What I suggest is first to put the 384.111 driver in BPO, and then once
we've checked it is good enough put it in the next p-u so that users are no
longer vulnerable.

What do you think of it ?

Rgds,
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-340xx
Source-Version: 340.106-1

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-340xx, 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.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-340xx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Jan 2018 20:50:05 +0100
Source: nvidia-graphics-drivers-legacy-340xx
Binary: nvidia-legacy-340xx-driver nvidia-legacy-340xx-driver-bin 
nvidia-legacy-340xx-driver-libs nvidia-legacy-340xx-driver-libs-i386 
xserver-xorg-video-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx 
libnvidia-legacy-340xx-glcore libegl1-nvidia-legacy-340xx 
libgles1-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx 
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-cfg1 
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-kernel-support 
nvidia-legacy-340xx-kernel-dkms nvidia-legacy-340xx-kernel-source 
nvidia-legacy-340xx-vdpau-driver nvidia-legacy-340xx-smi 
libnvidia-legacy-340xx-cuda1 libnvidia-legacy-340xx-cuda1-i386 
libnvidia-legacy-340xx-compiler libnvidia-legacy-340xx-nvcuvid1 
libnvidia-legacy-340xx-encode1 libnvidia-legacy-340xx-ifr1 
libnvidia-legacy-340xx-fbc1 libnvidia-legacy-340xx-ml1 
nvidia-legacy-340xx-opencl-icd
Architecture: source
Version: 340.106-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libegl1-nvidia-legacy-340xx - NVIDIA binary EGL library
 libgl1-nvidia-legacy-340xx-glx - NVIDIA binary OpenGL/GLX library
 libgles1-nvidia-legacy-340xx - NVIDIA binary OpenGL|ES 1.x library
 libgles2-nvidia-legacy-340xx - NVIDIA binary OpenGL|ES 2.x library
 libnvidia-legacy-340xx-cfg1 - NVIDIA binary OpenGL/GLX configuration library
 libnvidia-legacy-340xx-compiler - NVIDIA runtime compiler library
 libnvidia-legacy-340xx-cuda1 - NVIDIA CUDA Driver Library
 libnvidia-legacy-340xx-cuda1-i386 - NVIDIA CUDA 32-bit runtime library
 libnvidia-legacy-340xx-eglcore - NVIDIA binary EGL core libraries
 libnvidia-legacy-340xx-encode1 - NVENC Video Encoding runtime library
 libnvidia-legacy-340xx-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime 
library
 libnvidia-legacy-340xx-glcore - NVIDIA binary OpenGL/GLX core libraries
 libnvidia-legacy-340xx-ifr1 - NVIDIA OpenGL-based Inband Frame Readback 
runtime library
 libnvidia-legacy-340xx-ml1 - NVIDIA Management Library (NVML) runtime library
 libnvidia-legacy-340xx-nvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 nvidia-legacy-340xx-alternative - allows the selection of NVIDIA as GLX 
provider
 nvidia-legacy-340xx-driver - NVIDIA metapackage
 nvidia-legacy-340xx-driver-bin - NVIDIA driver support binaries
 nvidia-legacy-340xx-driver-libs - NVIDIA metapackage (OpenGL/GLX/EGL/GLES 

Bug#887558: wine-development FTBFS on armel: selected processor does not support `strd r4,[sp]' in ARM mode

[Jens Reyer]

Source: wine-development
Version: 3.0~rc3-2
Severity: serious
Forwarded: https://bugs.winehq.org/show_bug.cgi?id=44365
Tags: upstream


gcc -c -o relay.o relay.c -I. -I../../include -D__WINESRC__ -D_NTSYSTEM_
-D_REENTRANT -fPIC -Wall \
  -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers \
  -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes
-Wtype-limits \
  -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith
-Wlogical-op -gdwarf-2 \
  -gstrict-dwarf -Werror -Wdate-time -g -O2
-fdebug-prefix-map=/<>=.
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong
-Wformat -Werror=format-security -march=armv5t -Wno-error -marm
-mfloat-abi=soft
[...]
{standard input}: Assembler messages:
{standard input}:51: Error: selected processor does not support `strd
r4,[sp]' in ARM mode
Makefile:521: recipe for target 'relay.o' failed
make[2]: *** [relay.o] Error 1
make[2]: Leaving directory '/<>/dlls/ntdll'
Makefile:13147: recipe for target 'dlls/ntdll' failed
make[1]: *** [dlls/ntdll] Error 2


I hope upstream fixes this soon.  Otherwise we'd have to remove armel
from the architecture list and file an RM bug against ftp.debian.org for
removal of the stale old armel packages (advice copied from #881446).

Previously I had mistaken a change in 3.0-rc3 to fix this, therefore the
wrong changelog entry in that version.

Greets
jre

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

[Debian Bug Tracking System]

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

> tag 887479 + pending
Bug #887479 [src:libpdfbox2-java] libpdfbox2-java FTBFS: dh_installexamples 
fails
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#887479: Pending fixes for bugs in the libpdfbox2-java package

[pkg-java-maintainers]

tag 887479 + pending
thanks

Some bugs in the libpdfbox2-java package are closed in revision
5851ceda4cdf927b9d575b213152d8e3fd7c4823 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libpdfbox2-java.git/commit/?id=5851ced

Commit message:

Remove obsolete rm command in debian/rules.

Closes: #887479
Thanks: Adrian Bunk for the report.

Processed: closing 886474

[Debian Bug Tracking System]

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

> close 886474 4.15~rc8-1~exp1
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Bug #886510 [linux-headers-4.14.0-3-amd64] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Bug #886629 [linux-headers-4.14.0-3-amd64] virtualbox-dkms: missing dependency 
libelf-dev
Bug #886662 [linux-headers-4.14.0-3-amd64] wireguard-dkms should depend on 
libelf-dev
Bug #886743 [linux-headers-4.14.0-3-amd64] virtualbox-dkms now requires package 
libelf-dev to work
There is no source info for the package 'linux-headers-4.14.0-3-amd64' at 
version '4.15~rc8-1~exp1' with architecture ''
Unable to make a source version for version '4.15~rc8-1~exp1'
Marked as fixed in versions 4.15~rc8-1~exp1.
Marked as fixed in versions 4.15~rc8-1~exp1.
Marked as fixed in versions 4.15~rc8-1~exp1.
Marked as fixed in versions 4.15~rc8-1~exp1.
Marked as fixed in versions 4.15~rc8-1~exp1.
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Bug #886510 [linux-headers-4.14.0-3-amd64] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Bug #886629 [linux-headers-4.14.0-3-amd64] virtualbox-dkms: missing dependency 
libelf-dev
Bug #886662 [linux-headers-4.14.0-3-amd64] wireguard-dkms should depend on 
libelf-dev
Bug #886743 [linux-headers-4.14.0-3-amd64] virtualbox-dkms now requires package 
libelf-dev to work
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#822596: marked as done (gdebi: depends on gksu which is deprecated)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 15:46:07 -0500
with message-id 

and subject line Re: Uploading NMU to port gdebi away from gksu
has caused the Debian Bug report #822596,
regarding gdebi: depends on gksu which is deprecated
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.)


-- 
822596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdebi
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gksu

Hi,

gdebi depends on gksu, which is deprecated and unmaintained. Thus we
want to remove it from the archive.

gdebi should switch to a supported and securer way to become root,
particularly one that doesn't mean running your whole application as
root (including the GUI), e.g. using polkit.

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

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing gksu completely.

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

https://www.freedesktop.org/wiki/Software/polkit/
https://wiki.debian.org/PolicyKit

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Version: 0.9.5.7+nmu2

gdebi (0.9.5.7+nmu2) unstable; urgency=medium

  [ Julien Lavergne ]
  * Add a gdebi-gtk-pkexec executable to launch without gksu (LP: #189617).
  * debian/control:
   - Make gdebi depends on policykit-1 | gksu.

  [ Simon Quigley ]
  * Finish the policykit port:
- gdebi-gtk-pkexec isn't needed, root access is only needed for the
  package installation and removal.
- Install the policykit file (create debian/gdebi-gtk.install).
- Modify the gksu commands in GDebi/GDebiGtk.py to call pksu instead.
- Drop the dependency on gksu and only depend on policykit-1.
- Thanks for the initial work, Julien!

  [ Jeremy Bicha ]
  * Upload to unstable (LP: #1719746)
  * Stop building gdebi-kde since gdebi-kde is the last package in Testing
depending on the unmaintained pykde4 (Closes: #864963)

 -- Jeremy Bicha   Sun, 31 Dec 2017 11:00:13 -0500--- End Message ---

Processed: Re: Bug#886163 closed by Chris Lamb <la...@debian.org> (Bug#886163: fixed in lintian 2.5.68)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #886163 {Done: Chris Lamb } [src:lintian] lintian FTBFS 
on i386: fail tests::files-multiarch-foreign-files: output differs!
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions lintian/2.5.68.

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

Bug#886163: closed by Chris Lamb <la...@debian.org> (Bug#886163: fixed in lintian 2.5.68)

[Adrian Bunk]

Control: reopen -1

On Tue, Jan 09, 2018 at 03:39:22PM +, Debian Bug Tracking System wrote:
>...
>* t/tests/files-multiarch-foreign-files:
>  + [CL] Ensure that we install to a multiarch directory on all
>architectures to prevent a FTBFS on, for example, i386.
>(Closes: #886163)
>...

This seems to have only moved the test failure:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/lintian.html

...
-E: libfoo-dev: multiarch-foreign-cmake-file usr/lib/TRIPLET/cmake/foo.cmake
-E: libfoo-dev: multiarch-foreign-pkgconfig usr/lib/TRIPLET/pkgconfig/libfoo.pc
-E: libfoo-dev: multiarch-foreign-static-library usr/lib/TRIPLET/libfoo.a
+E: libfoo-dev: triplet-dir-and-architecture-mismatch usr/lib/TRIPLET/ is for 
amd64
...

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#886506: Installing busybox-static worked

[Gerhard Hellmann]

Can confirm that installing busybox-static allowed me to boot the
kernel. Thanks for the suggestion and the analysis.


signature.asc
Description: PGP signature

Bug#887534: plume-creator FTBFS with libquazip5-headers 0.7.3-3

[Adrian Bunk]

Source: plume-creator
Version: 0.66+dfsg1-3.1
Severity: serious
Tags: buster sid

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

...
g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DVERSIONSTR=\"0.67\" 
-DDATADIR=\"/usr/share/plume-creator\" -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB 
-DQT_WIDGETS_LIB -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_NETWORK_LIB 
-DQT_CORE_LIB -I. -I. -Isrc -Iexternals/qtsingleapplication/src -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o main.o src/main.cpp
In file included from src/zipper/zipchecker.h:28:0,
 from src/zipper/zipper.h:25,
 from src/hub.h:33,
 from src/mainwindow.h:28,
 from src/main.cpp:27:
src/common/utils.h:25:10: fatal error: quazip/JlCompress.h: No such file or 
directory
 #include 
  ^
compilation terminated.
Makefile:2631: recipe for target 'main.o' failed
make[1]: *** [main.o] Error 1

Bug#887523: marked as done (giada FTBFS on several architectures: error: 'args' is used uninitialized in this function)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 19:56:03 +0100 (CET)
with message-id <1ku.7kci.m6f5nwqdrh.1qn...@seznam.cz>
and subject line 
has caused the Debian Bug report #887523,
regarding giada FTBFS on several architectures: error: 'args' is used 
uninitialized in this function
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.)


-- 
887523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giada
Version: 0.14.5~dfsg1-1
Severity: serious

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

...
src/utils/string.cpp: In function 'std::__cxx11::string gu_format(const char*, 
...)':
src/utils/string.cpp:111:25: error: 'args' is used uninitialized in this 
function [-Werror=uninitialized]
  size_t size = vsnprintf(nullptr, 0, format, args);
~^~
cc1plus: all warnings being treated as errors
Makefile:3859: recipe for target 'src/utils/giada-string.o' failed
make[1]: *** [src/utils/giada-string.o] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.14.5~dfsg1-2

Thank you
mira--- End Message ---

Bug#887482: xorg-server: FTBFS: dh_autoreconf can only be run once

[Sven Joachim]

On 2018-01-17 00:40 -0800, Daniel Schepler wrote:

> Source: xorg-server
> Version: 2:1.19.5-1
> Severity: serious
>
> From my pbuilder build log:
>
> ...
> make[6]: Leaving directory
> '/build/xorg-server-1.19.5/debian/build/udeb/test/xi2'
> make[5]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test'
> make[4]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test'
> make[4]: Entering directory '/build/xorg-server-1.19.5/debian/build/udeb'
> make[4]: Nothing to be done for 'all-am'.
> make[4]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb'
> make[3]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb'
> make[2]: Leaving directory '/build/xorg-server-1.19.5'
>   debian/rules override_dh_auto_test
> make[2]: Entering directory '/build/xorg-server-1.19.5'
> dh_auto_test -- -j1 VERBOSE=1
> make[2]: Leaving directory '/build/xorg-server-1.19.5'
> make[1]: Leaving directory '/build/xorg-server-1.19.5'
>   dh_quilt_patch -O--parallel -Nxserver-common -Nxorg-server-source
> File series fully applied, ends at patch 06_use-intel-only-on-pre-gen4.diff
>   dh_update_autotools_config -O--parallel -Nxserver-common 
> -Nxorg-server-source
>   dh_autoreconf -O--parallel -Nxserver-common -Nxorg-server-source
> dh_autoreconf: Can only be run once, see dh-autoreconf(7)
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
>
> On further testing, it seems that on a freshly unpacked source, either
> "dpkg-buildpackage -B" or "dpkg-buildpackage -A" separately will work;
> but "dpkg-buildpackage -b" will fail with the above error.

This seems to have been triggered by the sequence handling rewrite in
debhelper 11.1, at least I was not able to reproduce it anymore after
downgrading debhelper to version 11.

In debhelper 11, the sequence of commands dh runs is this:

,
| $ dh build --no-act
|dh_testdir
|dh_update_autotools_config
|debian/rules override_dh_auto_configure
|debian/rules override_dh_auto_build
|debian/rules override_dh_auto_test
|debian/rules build-indep
`

Whereas in 11.1.2 dh runs the following sequence:

,
| $ dh build --no-act
|debian/rules build-indep
|dh_testdir -Nxserver-common -Nxorg-server-source
|dh_update_autotools_config -Nxserver-common -Nxorg-server-source
|debian/rules override_dh_auto_configure
|debian/rules override_dh_auto_build
|debian/rules override_dh_auto_test
`

This causes dh_autoreconf to be run twice, first via the build-indep
rule and then as part of the standard dh sequence.  Some advice from the
debhelper maintainer (CC'ed) would be appreciated.

Cheers,
   Sven

Bug#887531: python-asdf FTBFS: test failures

[Adrian Bunk]

Source: python-asdf
Version: 1.3.1-1
Severity: serious

Some recent change in unstable makes python-asdf FTBFS:

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

...
=== FAILURES ===
_ test_urlopen[tree0] __

tree = {'not_shared': array([10,  9,  8,  7,  6,  5,  4,  3,  2,  1], 
dtype=uint8), 'science_data': array([ 0.,  1.,  2.,  3.,  4.,  5.,  6.,  7.,  
8.,  9.]), 'skipping': array([ 0.,  2.,  4.,  6.,  8.]), 'subset': array([ 3.,  
4.,  5.,  6.])}
httpserver = 

@pytest.mark.skipif(INTERNET_OFF, reason="Astropy has disabled internet 
access")
@pytest.mark.skipif(sys.platform.startswith('win'),
reason="Windows firewall prevents test")
def test_urlopen(tree, httpserver):
path = os.path.join(httpserver.tmpdir, 'test.asdf')

def get_write_fd():
return generic_io.get_file(open(path, 'wb'), mode='w')

def get_read_fd():
return generic_io.get_file(
urllib_request.urlopen(
httpserver.url + "test.asdf"))

>   with _roundtrip(tree, get_write_fd, get_read_fd) as ff:

asdf/tests/test_generic_io.py:270: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
asdf/tests/test_generic_io.py:72: in _roundtrip
with get_read_fd() as fd:
asdf/tests/test_generic_io.py:268: in get_read_fd
httpserver.url + "test.asdf"))
/usr/lib/python2.7/urllib2.py:154: in urlopen
return opener.open(url, data, timeout)
/usr/lib/python2.7/urllib2.py:429: in open
response = self._open(req, data)
/usr/lib/python2.7/urllib2.py:447: in _open
'_open', req)
/usr/lib/python2.7/urllib2.py:407: in _call_chain
result = func(*args)
/usr/lib/python2.7/urllib2.py:1228: in http_open
return self.do_open(httplib.HTTPConnection, req)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
http_class = 
req = , http_conn_args = {}
host = '127.0.0.1:9', h = 
err = error(111, 'Connection refused')

def do_open(self, http_class, req, **http_conn_args):
"""Return an addinfourl object for the request, using http_class.

http_class must implement the HTTPConnection API from httplib.
The addinfourl return value is a file-like object.  It also
has methods and attributes including:
- info(): return a mimetools.Message object for the headers
- geturl(): return the original request URL
- code: HTTP status code
"""
host = req.get_host()
if not host:
raise URLError('no host given')

# will parse host:port
h = http_class(host, timeout=req.timeout, **http_conn_args)
h.set_debuglevel(self._debuglevel)

headers = dict(req.unredirected_hdrs)
headers.update(dict((k, v) for k, v in req.headers.items()
if k not in headers))

# We want to make an HTTP/1.1 request, but the addinfourl
# class isn't prepared to deal with a persistent connection.
# It will try to read all remaining data from the socket,
# which will block while the server waits for the next request.
# So make sure the connection gets closed after the (only)
# request.
headers["Connection"] = "close"
headers = dict(
(name.title(), val) for name, val in headers.items())

if req._tunnel_host:
tunnel_headers = {}
proxy_auth_hdr = "Proxy-Authorization"
if proxy_auth_hdr in headers:
tunnel_headers[proxy_auth_hdr] = headers[proxy_auth_hdr]
# Proxy-Authorization should not be sent to origin
# server.
del headers[proxy_auth_hdr]
h.set_tunnel(req._tunnel_host, headers=tunnel_headers)

try:
h.request(req.get_method(), req.get_selector(), req.data, headers)
except socket.error, err: # XXX what error?
h.close()
>   raise URLError(err)
E   URLError: 

/usr/lib/python2.7/urllib2.py:1198: URLError
_ test_urlopen[tree1] __

tree = {'more': array([[[ 0.5047124 ,  0.67230725,  0.54438082, ...,  0.6181783 
,
  0.86328092,  0.20516376, ...,...738, ...,  0.77406934,
 0.85... 0.98452297,  0.2701272 , ...,  0.70554981,
 0.99484383,  0.83053795]])}
httpserver = 

@pytest.mark.skipif(INTERNET_OFF, reason="Astropy has disabled internet 
access")
@pytest.mark.skipif(sys.platform.startswith('win'),
reason="Windows firewall prevents test")
def test_urlopen(tree, httpserver):
path = 

Bug#878633: python-pgpy FTBFS with more than one supported Python3 version

[Michael Greene]

I haven't tried this in the rules file myself, but these commands
should work:
# python 3  LC_ALL=C.UTF-8 py.test-3 tests/
# python 2LC_ALL=C.UTF-8 py.test tests/
On Fri, 2018-01-12 at 14:18 -0500, Daniel Kahn Gillmor wrote:
> On Sun 2017-10-15 13:50:56 +0300, Adrian Bunk wrote:
> > ...
> >debian/rules override_dh_auto_test
> > make[1]: Entering directory '/build/1st/python-pgpy-0.4.3'
> > LC_ALL=C.UTF-8 dh_auto_test -O--buildsystem=pybuild
> > I: pybuild base:184: cd /build/1st/python-pgpy-
> > 0.4.3/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest tests
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/_pytest/config.py", line
> > 342, in _getconftestmodules
> > return self._path2confmods[path]
> > KeyError: local('/build/1st/python-pgpy-
> > 0.4.3/.pybuild/pythonX.Y_3.5/build/tests')
> > 
> > During handling of the above exception, another exception occurred:
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/_pytest/config.py", line
> > 373, in _importconftest
> > return self._conftestpath2mod[conftestpath]
> > KeyError: local('/build/1st/python-pgpy-
> > 0.4.3/.pybuild/pythonX.Y_3.5/build/tests/conftest.py')
> > 
> > During handling of the above exception, another exception occurred:
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/gpg/gpgme.py", line 14, in
> > swig_import_helper
> > return importlib.import_module(mname)
> >   File "/usr/lib/python3.5/importlib/__init__.py", line 126, in
> > import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> >   File "", line 985, in _gcd_import
> >   File "", line 968, in _find_and_load
> >   File "", line 955, in
> > _find_and_load_unlocked
> > ImportError: No module named 'gpg._gpgme'
> > 
> > During handling of the above exception, another exception occurred:
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/_pytest/config.py", line
> > 379, in _importconftest
> > mod = conftestpath.pyimport()
> >   File "/usr/lib/python3/dist-packages/py/_path/local.py", line
> > 662, in pyimport
> > __import__(modname)
> >   File "/usr/lib/python3/dist-
> > packages/_pytest/assertion/rewrite.py", line 212, in load_module
> > py.builtin.exec_(co, mod.__dict__)
> >   File "/build/1st/python-pgpy-
> > 0.4.3/.pybuild/pythonX.Y_3.5/build/tests/conftest.py", line 5, in
> > 
> > import gpg
> >   File "/usr/lib/python3/dist-packages/gpg/__init__.py", line 101,
> > in 
> > from . import core
> >   File "/usr/lib/python3/dist-packages/gpg/core.py", line 34, in
> > 
> > from . import gpgme
> >   File "/usr/lib/python3/dist-packages/gpg/gpgme.py", line 17, in
> > 
> > _gpgme = swig_import_helper()
> >   File "/usr/lib/python3/dist-packages/gpg/gpgme.py", line 16, in
> > swig_import_helper
> > return importlib.import_module('_gpgme')
> >   File "/usr/lib/python3.5/importlib/__init__.py", line 126, in
> > import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> > ImportError: No module named '_gpgme'
> > ERROR: could not load /build/1st/python-pgpy-
> > 0.4.3/.pybuild/pythonX.Y_3.5/build/tests/conftest.py
> > 
> > E: pybuild pybuild:283: test: plugin distutils failed with: exit
> > code=4: cd /build/1st/python-pgpy-
> > 0.4.3/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest tests
> > dh_auto_test: pybuild --test --test-pytest -i python{version} -p
> > "3.5 3.6" returned exit code 13
> > debian/rules:13: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 25
> > 
> > Either #866555 needs fixing or as workaround the tests
> > should run only with the default python3 version.
> 
> this does indeed seem to be related to #866555, which doesn't seem
> like
> it will be fixed upstream, and i don't want to carry a diff for.  so
> i
> suppose we should limit python-pgpy  to only run the tests against
> the
> default python3 version.  If there's a canonical way to do that, i'd
> be
> happy to see the pointers to it, otherwise i'll just blunder along
> and
> see what i can figure out.
> 
> --dkg

-- 
Michael Greene
Software Engineer
mgre...@securityinnovation.com

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

Bug#887523: marked as done (giada FTBFS on several architectures: error: 'args' is used uninitialized in this function)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 20:39:16 +0200
with message-id <20180117183916.GA12000@localhost>
and subject line Fixed in 0.14.5~dfsg1-2
has caused the Debian Bug report #887523,
regarding giada FTBFS on several architectures: error: 'args' is used 
uninitialized in this function
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.)


-- 
887523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giada
Version: 0.14.5~dfsg1-1
Severity: serious

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

...
src/utils/string.cpp: In function 'std::__cxx11::string gu_format(const char*, 
...)':
src/utils/string.cpp:111:25: error: 'args' is used uninitialized in this 
function [-Werror=uninitialized]
  size_t size = vsnprintf(nullptr, 0, format, args);
~^~
cc1plus: all warnings being treated as errors
Makefile:3859: recipe for target 'src/utils/giada-string.o' failed
make[1]: *** [src/utils/giada-string.o] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.14.5~dfsg1-2

Changed-By: Jaromír Mikeš 
Description:
 giada  - Hardcore Loop Machine
Changes:
 giada (0.14.5~dfsg1-2) unstable; urgency=medium
 .
   * Add patch to fix build on some archs.

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

cu
Adrian

-- 

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

Bug#885749: marked as done (pegsolitaire: Depends on libgnomeui)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 18:35:50 +
with message-id 
and subject line Bug#885749: fixed in pegsolitaire 0.1.1-1
has caused the Debian Bug report #885749,
regarding pegsolitaire: 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.)


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

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 depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[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: pegsolitaire
Source-Version: 0.1.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jan 2018 16:01:47 +0200
Source: pegsolitaire
Binary: pegsolitaire
Architecture: source
Version: 0.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Juhani Numminen 
Description:
 pegsolitaire - education game similar to Hi-Q
Closes: 885749
Changes:
 pegsolitaire (0.1.1-1) unstable; urgency=medium
 .
   * New upstream version 0.1.1.
 - No longer depends on libgnome, libgnomeui or libglade. (Closes: #885749)
   * Remove manpage, desktop file and xpm icon. They are integrated upstream.
   * debian/control:
 - New Build-Dependencies autoconf-archive, libgtk2.0-dev, librsvg2-dev.
 - Drop unneeded Build-Depends libxml-parser-perl, pkg-config.
 - Add myself to Uploaders.
 - New homepage.
 - VCS has been migrated from svn to git.
 - Add Rules-Requires-Root: no.
   * Bump Standards-Version to 4.1.3.
 - Remove debian/menu as required by Debian Policy >= 4.0.1.
   * Update to compat level 11. Now autoreconf and parallel are the default.
   * debian/rules:
 - Enable all hardening options.
 - Do not add -Wl,--as-needed, it was integrated upstream.
 - Install game data in /usr/share/games. Simplify debian/rules.
   * debian/watch, debian/upstream/signing-key.asc: New watch file with gpg
 verification.
   * debian/clean: Added to clean the po/ directory.
   * debian/copyright: New copyright holders and years. Change http to https.
   * wrap-and-sort -s.
Checksums-Sha1:
 061fb1b938296277f8afa5f849df1435f0fe1373 2187 pegsolitaire_0.1.1-1.dsc
 112a18df300e0cb41fd0d5f072f962c04b10475e 34555 pegsolitaire_0.1.1.orig.tar.gz
 8f0a6572ccd8248c30918fe1e151abbe5ba9b26f 4160 
pegsolitaire_0.1.1-1.debian.tar.xz
 982abfcd33374f3446d6975d41df05402ce89d43 10603 
pegsolitaire_0.1.1-1_amd64.buildinfo
Checksums-Sha256:
 7f77cdcdedc9106505812909e40885103369375e6033f15c6db7f8bcee8ee8c2 2187 
pegsolitaire_0.1.1-1.dsc
 4ed41b497f4636ad16ed3d32cc5a7d50374d0ecce9f8751eba0a20ecf06c6cf6 34555 
pegsolitaire_0.1.1.orig.tar.gz
 448cff98f0198f06c4e04474224ffd2134c109db2424d49cb96abfc437f28d24 4160 
pegsolitaire_0.1.1-1.debian.tar.xz
 ff8bb8ae038ba899b75d0d0e6e5f88513d470934c1779e6d4452f307a20ff111 10603 
pegsolitaire_0.1.1-1_amd64.buildinfo
Files:
 105c4a0fd80dc9bb3587ceb3e347ef23 2187 games optional pegsolitaire_0.1.1-1.dsc
 f70d22e9b048db2f912d335d15e945d9 34555 games optional 
pegsolitaire_0.1.1.orig.tar.gz
 28f941ee4476dedab7c654c0043c4569 4160 games optional 
pegsolitaire_0.1.1-1.debian.tar.xz
 

Bug#887530: cen64-qt FTBFS with libquazip5-headers 0.7.3-3

[Adrian Bunk]

Source: cen64-qt
Version: 20160829-alpha-1
Severity: serious

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

...
g++ -c -pipe -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB 
-DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o common.o src/common.cpp
src/common.cpp:43:10: fatal error: quazip/quazip.h: No such file or directory
 #include 
  ^
compilation terminated.
Makefile:554: recipe for target 'common.o' failed
make[1]: *** [common.o] Error 1

Bug#887529: aiohttp-cors FTBFS: test errors

[Adrian Bunk]

Source: aiohttp-cors
Version: 0.5.3-1
Severity: serious

Some recent change in unstable makes aiohttp-cors FTBFS:

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

...
 ERRORS 
_ ERROR at teardown of TestMain.test_preflight_default _

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
__ ERROR at teardown of TestMain.test_simple_default ___

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
___ ERROR at teardown of TestMain.test_simple_expose_headers ___

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
__ ERROR at teardown of TestMain.test_simple_with_credentials __

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
=== FAILURES ===
__ TestMain.test_dummy_setup ___

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
_ TestMain.test_dummy_setup_roundtrip __

Processed: libgctp0d: broken dependency in symbols file

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:hdf-eos4 src:hdf-eos5 src:ncl src:ruby-hdfeos5
Bug #887528 [libgctp0d] libgctp0d: broken dependency in symbols file
Added indication that 887528 affects src:hdf-eos4, src:hdf-eos5, src:ncl, and 
src:ruby-hdfeos5

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

Bug#887528: libgctp0d: broken dependency in symbols file

[Adrian Bunk]

Package: libgctp0d
Version: 2.0-3
Severity: serious
Control: affects -1 src:hdf-eos4 src:hdf-eos5 src:ncl src:ruby-hdfeos5

The syntax of the dependency in the new symbols file is not correct:

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

...
dpkg-shlibdeps: error: invalid dependency got generated: libhdf5-100, libgctp0d 
2.0-1, libhe5-hdfeos0, libruby2.3 (>= 2.3.0~preview2), libc6 (>= 2.14), 
libgmp10 
dh_shlibdeps: dpkg-shlibdeps -Tdebian/ruby-hdfeos5.substvars 
debian/ruby-hdfeos5/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/numru/hdfeos5raw.so
 returned exit code 255
dh_shlibdeps: Aborting due to earlier error
debian/rules:17: recipe for target 'binary' failed
make: *** [binary] Error 25

Bug#887524: marked as done (fish FTBFS: install-translations fails)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 18:19:24 +
with message-id 
and subject line Bug#887524: fixed in fish 2.7.1-2
has caused the Debian Bug report #887524,
regarding fish FTBFS: install-translations fails
to be marked as done.

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

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


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

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

...
Installing translations...
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/en/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/nn/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/nb/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/sv/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/fr/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/de/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/pt_BR/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/pl/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/zh_CN/LC_MESSAGES/fish.mo': No such file or directory
Makefile:775: recipe for target 'install-translations' failed
make[2]: *** [install-translations] Error 1
--- End Message ---
--- Begin Message ---
Source: fish
Source-Version: 2.7.1-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jan 2018 20:06:59 +0200
Source: fish
Binary: fish fish-common
Architecture: source
Version: 2.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Tristan Seligmann 
Description:
 fish   - friendly interactive shell
 fish-common - friendly interactive shell (architecture-independent files)
Closes: 887524
Changes:
 fish (2.7.1-2) unstable; urgency=medium
 .
   * Replace $(PWD) with $(CURDIR) in Makefile.am (closes: #887524)
 (hopefully!)
Checksums-Sha1:
 ed9cdc3ab0cb3f1deac4f8e87c43e2d8476a3937 1784 fish_2.7.1-2.dsc
 e44e510f8d744181bd4d6df894d1326f4cc6e4ec 20204 fish_2.7.1-2.debian.tar.xz
 08fde9823b1b65ba56d4b45200e3224c562aefc6 6068 fish_2.7.1-2_source.buildinfo
Checksums-Sha256:
 ab21eda99a03f2bc86d252685361bba0f891be09f4c56cd19744cbc4e4dc96b1 1784 
fish_2.7.1-2.dsc
 736d3008f0afe5ac0c60fa19d5f9bdfafc370deb7d7e9255720a4efdf6862c68 20204 
fish_2.7.1-2.debian.tar.xz
 4ac0dc4a5bfd8c07bcaa8def7f8aa5a65f741e956e1c0366f9826082a7a7da23 6068 
fish_2.7.1-2_source.buildinfo
Files:
 85a8c3105f0ddc63127e8dea6067435c 1784 shells optional fish_2.7.1-2.dsc
 3e43415cb0ed67d52348962458e03e92 20204 shells optional 
fish_2.7.1-2.debian.tar.xz
 5e17ba4ba3eb52b0807d24e17168212d 6068 shells optional 

Bug#873417: marked as done (pocl: Please update to llvm-toolchain 4.0 or, better, 5.0)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 18:04:37 +
with message-id 
and subject line Bug#873417: fixed in pocl 0.14-7
has caused the Debian Bug report #873417,
regarding pocl: Please update to llvm-toolchain 4.0 or, better, 5.0
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.)


-- 
873417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pocl
Severity: normal

Hello,

Currently, we have 6 versions of the llvm toolchain in the archive.
I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)

Could you please update your package to use 4.0 (or, better, 5.0 which will be 
released very 
soon)?

I will update the severity of this bug at the end of September

Thanks
Sylvestre
--- End Message ---
--- Begin Message ---
Source: pocl
Source-Version: 0.14-7

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pocl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Jan 2018 18:36:08 +0100
Source: pocl
Binary: pocl-opencl-icd libpocl1-common libpocl1 libpoclu1 libpoclu-dev 
libpocl-dev pocl-doc
Architecture: source
Version: 0.14-7
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libpocl-dev - development files for the pocl library
 libpocl1   - Portable Computing Language library
 libpocl1-common - common files for the pocl library
 libpoclu-dev - development files for the pocl utility library
 libpoclu1  - utility library for writing OpenCL programs
 pocl-doc   - documentation for the pocl library
 pocl-opencl-icd - pocl ICD
Closes: 873417
Changes:
 pocl (0.14-7) unstable; urgency=medium
 .
   * Switch to llvm 4.0.  (Closes: #873417)
   * Update symbols files for amd64 and i386.
Checksums-Sha1:
 a59ae93e9949aa57b7c427e19fda8a0d61e13648 2490 pocl_0.14-7.dsc
 69527e4cae31e4f97f4b19398c6c4de0b0c8915d 21576 pocl_0.14-7.debian.tar.xz
 78ff08ce800148a1166c1ebe5734e90c23e97f27 7511 pocl_0.14-7_source.buildinfo
Checksums-Sha256:
 7783be4497d9dfd77c61585a1372952fd0d873c61cf20ae28e43628f62fe2432 2490 
pocl_0.14-7.dsc
 d95525046470c50e087887a034c4f721a49d64d8b33aca6eee18d199f83160c3 21576 
pocl_0.14-7.debian.tar.xz
 6270fae38a264d13e6f2d083e9bb1cc3974bea4d8307be4761f42672638e848e 7511 
pocl_0.14-7_source.buildinfo
Files:
 521d5f621fbddf4c571020e6ffd93fe4 2490 libs optional pocl_0.14-7.dsc
 e9219ea60e0c5436f44377e7ea5145d1 21576 libs optional pocl_0.14-7.debian.tar.xz
 1d02c8b28a5ef758950454350ea375a9 7511 libs optional 
pocl_0.14-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpfjEIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCKDSD/wLW189rdvxcdKa0es4rMx8roT4kVvKhWvu
U10+j80xjb+VgMZAdBMaNqxLs50xNurjY50U8A6swe+jeRbrEO/lMhHZRPfAyFId
S40mUVw8hree3z1711aSvWylO57GYS9+3zWy2UF+X2tZLxDfzirRNGXAwH2EIssf
qKmlaht9J3RlEBRFAYeE0TE0qZCkscpQIoo+fKg+prEXme+EygS2xzhx89FJZ5p2
7MiNb7iaEPHcvjFGMJIxdxzcCgi7qq/K5hRfXLVsDGnOKur7bfPYkeqpxSXKuzV3
cE2gyz8yVNSKFODewYhPwCZOwW9PAcb6d1rVMkj3bDQPOIFIelcj8u9cBLyN0l/H
MboD02Im/ONPUwCeDsTPJEeWjRTX/HdchIJpy3krhUs3J9cjOyvK+IKV1HASqvmJ
NnqAygReZ4CW3D/fu39Uc8paXn111Rc/LABiRPvnM+dchqlklzhExHRraOggiCqS
UUSwA1bgnCBiLMRq4O4U3McxoHIZj12VDF84hy8N1r2WlAOrrHzhirwe0697R3bs
psEzNkhENqzB8VL4EahBzVkqZnPA+Wqc/2Qc+gPNyVARi3mTMH+wwWBgv3rK7GWM
I2DeDyT9Yse+9UJwEddQ3HoegiAQ5XTwYdg/qH5fem00CRvowkJudh1PQx9DznGV
l7cb+lbs8w==
=CD7O
-END PGP SIGNATURE End Message ---

Bug#887526: nuget: Nuget does not install packages

[Simon Heath]

Package: nuget
Version: 2.8.7+md510+dhx1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Upon trying to use nuget to install a package I get a message along the lines 
of:

$ nuget install nunit
> X already has a dependency defined for Y.

The exact X and Y vary depending on the package I'm trying to build, but I've 
been
unable to install any packages at all.

This appears to be the same bug described here:

https://stackoverflow.com/questions/25725545/nuget-x-already-has-a-dependency-defined-for-y#25844391

Running `nuget update -self` resolves the problem.

Thank you,
Simon Heath


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

Kernel: Linux 4.14.0-2-amd64 (SMP w/16 CPU cores)
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)
LSM: AppArmor: enabled

Versions of packages nuget depends on:
ii  libmono-corlib4.5-cil 4.6.2.7+dfsg-1
ii  libmono-microsoft-build-engine4.0-cil 4.6.2.7+dfsg-1
ii  libmono-microsoft-build-framework4.0-cil  4.6.2.7+dfsg-1
ii  libmono-microsoft-build4.0-cil4.6.2.7+dfsg-1
ii  libmono-microsoft-csharp4.0-cil   4.6.2.7+dfsg-1
ii  libmono-system-componentmodel-composition4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system-core4.0-cil4.6.2.7+dfsg-1
ii  libmono-system-xml-linq4.0-cil4.6.2.7+dfsg-1
ii  libmono-system4.0-cil 4.6.2.7+dfsg-1
ii  libnuget-core-cil 2.8.7+md510+dhx1-1
ii  mono-runtime  4.6.2.7+dfsg-1

nuget recommends no packages.

nuget suggests no packages.

-- no debconf information

Bug#887525: poppler FTBFS with gtk-doc-tools 1.27-1

[Adrian Bunk]

Source: poppler
Version: 0.61.1-2
Severity: serious

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

...
make[3]: Entering directory '/build/1st/poppler-0.61.1/obj-x86_64-linux-gnu'
cd /build/1st/poppler-0.61.1/obj-x86_64-linux-gnu && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /build/1st/poppler-0.61.1 
/build/1st/poppler-0.61.1/qt5/tests 
/build/1st/poppler-0.61.1/obj-x86_64-linux-gnu 
/build/1st/poppler-0.61.1/obj-x86_64-linux-gnu/qt5/tests 
/build/1st/poppler-0.61.1/obj-x86_64-linux-gnu/qt5/tests/CMakeFiles/check_qt5_search.dir/DependInfo.cmake
 --color=
WARNING:root:Running scanner failed: [Errno 2] No such file or directory, 
command: LD_LIBRARY_PATH=/build/1st/poppler-0.61.1/obj-x86_64-linux-gnu/glib 
./poppler-scan
Traceback (most recent call last):
  File "../../../make-glib-api-docs", line 66, in 
gtkdoc.generate(not args.skip_html)
  File "/build/1st/poppler-0.61.1/gtkdoc.py", line 143, in generate
self._run_gtkdoc_scangobj()
  File "/build/1st/poppler-0.61.1/gtkdoc.py", line 338, in _run_gtkdoc_scangobj
env=env, cwd=self.output_dir)
  File "/build/1st/poppler-0.61.1/gtkdoc.py", line 209, in _run_command
% (args[0], process.returncode))
Exception: gtkdoc-scangobj produced a non-zero return code 1
glib/reference/CMakeFiles/glib-docs.dir/build.make:63: recipe for target 
'glib/reference/glib-docs-build.stamp' failed
make[3]: *** [glib/reference/glib-docs-build.stamp] Error 1

Bug#887458: marked as done (shelxle FTBFS on armel/armhf: fatal error: GL/glu.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 17:34:43 +
with message-id 
and subject line Bug#887458: fixed in shelxle 1.0.888-1
has caused the Debian Bug report #887458,
regarding shelxle FTBFS on armel/armhf: fatal error: GL/glu.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.)


-- 
887458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shelxle
Version: 1.0.886-2
Severity: serious

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

...
In file included from molecule.cpp:19:0:
./molecule.h:37:10: fatal error: GL/glu.h: No such file or directory
 #include 
  ^~
compilation terminated.
Makefile:738: recipe for target 'molecule.o' failed
make[1]: *** [molecule.o] Error 1


Different from all other architectures, Qt5 is on armel/armhf
(and arm64 on Ubuntu) built with OpenGL ES.

Ideally it should be made working to build when Qt is using
OpenGL ES, but if that is not possible:
- avoid the FTBFS by changing the build dependency from
  libqt5opengl5-dev to libqt5opengl5-desktop-dev, and
- submit a bug against ftp.debian.org asking for removal
  of the old armel/armhf binaries
--- End Message ---
--- Begin Message ---
Source: shelxle
Source-Version: 1.0.888-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jan 2018 17:11:02 +0100
Source: shelxle
Binary: shelxle
Architecture: source amd64
Version: 1.0.888-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Daniel Leidert 
Description:
 shelxle- graphical user interface for SHELXL
Closes: 887458
Changes:
 shelxle (1.0.888-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control (Build-Depends): Use libqt5opengl5-desktop-dev instead of
 libqt5opengl5-dev (closes: #887458). Removed qt5-default to fix
 build-depends-on-metapackage.
   * debian/rules: Set QT_SELECT.
   * debian/patches/qt5.patch: Patch removed (merged into upstream).
   * debian/patches/series: Adjusted.
Checksums-Sha1:
 37097fad9690ef7bd0a9e66ce5ab48721afc7873 1966 shelxle_1.0.888-1.dsc
 64f05152143cd378eec82d53ff6b98f9739e0add 3019234 shelxle_1.0.888.orig.tar.bz2
 1f576464f55c75f98b582e83817b645acf6637d1 9556 shelxle_1.0.888-1.debian.tar.xz
 b194cf58c92ad1a161c5ce9184b4e59d4f683851 8169468 
shelxle-dbgsym_1.0.888-1_amd64.deb
 57d8a85d06315d3d7e5c1196863538a15a1b4744 9968 shelxle_1.0.888-1_amd64.buildinfo
 6e4fb99a9e5d0e9f70da1cfd3448854a2939159c 4034120 shelxle_1.0.888-1_amd64.deb
Checksums-Sha256:
 ebfbab5d0b5023f0db90e9daf40f52e47ee31de29aa0b05b43348c3c169ca57d 1966 
shelxle_1.0.888-1.dsc
 f9f3b097bba7735195ea5360c36750623af5f98b6f8e02ae430efdb1722803ae 3019234 
shelxle_1.0.888.orig.tar.bz2
 c38629a16587bb7ae793a8c2612f1c6a8fc89c07e488c24432d84bb293c30ca0 9556 
shelxle_1.0.888-1.debian.tar.xz
 48d082567484a8ae5a2432d4de56b7ef5c98c9141ab1198e4304483b6e5f4108 8169468 
shelxle-dbgsym_1.0.888-1_amd64.deb
 3de4e77116d24288b2138087ca58003e0a97fdde5159f20d50d7bf32d2c5dd76 9968 
shelxle_1.0.888-1_amd64.buildinfo
 b71ba4ba5a52249afd39980a96b30df79ee087bfd451946c4e05c910a22480f5 4034120 
shelxle_1.0.888-1_amd64.deb
Files:
 b80262a3edd35da4fb7fdb614769db98 1966 science optional shelxle_1.0.888-1.dsc
 6efc7ed86d1ff0dbb14ffa5b2b70a80d 3019234 science optional 
shelxle_1.0.888.orig.tar.bz2
 33f2ef807527d63394ebaeb6fb7594a9 9556 science optional 
shelxle_1.0.888-1.debian.tar.xz
 9bd57fb2ef0e271563096999e69ccb99 8169468 debug optional 
shelxle-dbgsym_1.0.888-1_amd64.deb
 49b323fe7031b8c0f9b2d2eaa900b033 9968 science optional 
shelxle_1.0.888-1_amd64.buildinfo
 160c4490b8a6f5e4ee207fd108e98de3 4034120 science optional 
shelxle_1.0.888-1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#880246: marked as done (magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 17:34:31 +
with message-id 
and subject line Bug#880246: fixed in magic-wormhole 0.10.3-1
has caused the Debian Bug report #880246,
regarding magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 3.6 returned exit code 13
to be marked as done.

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

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


-- 
880246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: magic-wormhole
Version: 0.9.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python3.6 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/wordlist.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/wormhole.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/timing.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/_version.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/transit.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/errors.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/ipaddrs.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/channel_monitor.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/util.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/xfer_util.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/codes.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> copying src/wormhole/tor_manager.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole
> creating /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> copying src/wormhole/cli/cmd_receive.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> copying src/wormhole/cli/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> copying src/wormhole/cli/cmd_send.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> copying src/wormhole/cli/public_relay.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> copying src/wormhole/cli/cmd_ssh.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> copying src/wormhole/cli/cli.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/cli
> creating /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/runner.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/cmd_server.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/database.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/cmd_usage.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/rendezvous_websocket.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/server.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/transit_server.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/cli.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> copying src/wormhole/server/rendezvous.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/server
> creating /<>/.pybuild/pythonX.Y_3.6/build/wormhole/test
> copying src/wormhole/test/common.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/test
> copying src/wormhole/test/test_wormhole.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/test
> copying src/wormhole/test/test_hkdf.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/test
> copying src/wormhole/test/test_xfer_util.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/test
> copying src/wormhole/test/test_transit.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/wormhole/test
> copying src/wormhole/test/test_transit_server.py -> 
> 

Bug#887524: fish FTBFS: install-translations fails

[Adrian Bunk]

Source: fish
Version: 2.7.1-1
Severity: serious

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

...
Installing translations...
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/en/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/nn/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/nb/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/sv/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/fr/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/de/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/pt_BR/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/pl/LC_MESSAGES/fish.mo': No such file or directory
/usr/bin/install: cannot create directory ‘/test’: Permission denied
/usr/bin/install: cannot create regular file 
'/test/root/./share/locale/zh_CN/LC_MESSAGES/fish.mo': No such file or directory
Makefile:775: recipe for target 'install-translations' failed
make[2]: *** [install-translations] Error 1

Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

[Antoine Beaupré]

On 2018-01-16 20:35:25, Harlan Lieberman-Berg wrote:
> tag 880246 +pending
> thanks
>
> Hi Antoine,
>
> I talked with the Privacy Tools team, and they've taken the patch.
> 0.10.3-1 now builds successfully and works fine!  It's waiting for
> your upload.

Awesome, thanks!

I've reviewed your work, and it looks generally good.

However, I noticed you added a new patch to remove the `ipaddress`
dependency. That's fine: we want the thing to build. However, I think we
should strive to avoid debian-specific patches in general, unless
absolutely necessary.

In this case, I think we should find a way to make the `ipaddress`
dependency only apply on Python 2 installs. I think there's a way to
specify dependencies like this. Someone submitted a py3 patch to another
project i'm maintaining, but i can't find it right now... :(

Could you look into this to improve the patch and send it upstream? I
don't think it's a blocker for this upload, but I'd like to see this
fixed in the long term.

I made minor changes to the package (added more docs and moved to salsa)
and changed the changelog to make the upload my own (keeping credits).

I note that your email address was incorrect in the changelog, but that
was fixed by rewriting it. Next time, something to keep an eye on.

I uploaded the package to unstable and both alioth and salsa. That
should be the last upload to alioth, where i archived the repository by
setting a pre-receive hook to error and put a warning in the description
as well.

a.

-- 
Software gets slower faster than hardware gets faster.
 - Wirth's law

Bug#887523: giada FTBFS on several architectures: error: 'args' is used uninitialized in this function

[Adrian Bunk]

Source: giada
Version: 0.14.5~dfsg1-1
Severity: serious

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

...
src/utils/string.cpp: In function 'std::__cxx11::string gu_format(const char*, 
...)':
src/utils/string.cpp:111:25: error: 'args' is used uninitialized in this 
function [-Werror=uninitialized]
  size_t size = vsnprintf(nullptr, 0, format, args);
~^~
cc1plus: all warnings being treated as errors
Makefile:3859: recipe for target 'src/utils/giada-string.o' failed
make[1]: *** [src/utils/giada-string.o] Error 1

Bug#883523: xpdf: FTBFS with poppler 0.61.1

[Adrian Bunk]

On Thu, Dec 14, 2017 at 01:14:24PM +, peter green wrote:
>...
> Unfortunately the build then goes on to fail in another file
> 
> build/XPDFParams.cc: In member function ‘void 
> XPDFParams::parseScreenType(GooList*, GooString*, int)’:
> build/XPDFParams.cc:1631:19: error: ‘class GlobalParams’ has no member named 
> ‘setScreenType’; did you mean ‘setEnableFreeType’?
>  globalParams->setScreenType(screenDispersed);
>^
>setEnableFreeType
> compilation terminated due to -Wfatal-errors.
> : recipe for target 'build/XPDFParams.o' failed
> 
> Any thoughts?
>...

The attached patch is a big hammer that disables the non-compling code.

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

Description: Hacks to compile with poppler 0.61
 - disable screenType setting
 - disable Movie action
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/883523

--- xpdf-3.04.orig/xpdf/GlobalParams.cc
+++ xpdf-3.04/xpdf/GlobalParams.cc
@@ -1174,8 +1174,8 @@ void GlobalParams::parseLine(char *buf,
 /*
 } else if (!cmd->cmp("strokeAdjust")) {
   parseYesNo("strokeAdjust", , tokens, fileName, line);
-} else if (!cmd->cmp("screenType")) {
-  parseScreenType(tokens, fileName, line);
+//} else if (!cmd->cmp("screenType")) {
+//  parseScreenType(tokens, fileName, line);
 } else if (!cmd->cmp("screenSize")) {
   parseInteger("screenSize", , tokens, fileName, line);
 } else if (!cmd->cmp("screenDotRadius")) {
@@ -1617,6 +1617,7 @@ void GlobalParams::parseInitialZoom(GLis
   initialZoom = ((GString *)tokens->get(1))->copy();
 }
 
+/*
 void GlobalParams::parseScreenType(GList *tokens, GString *fileName,
    int line) {
   GString *tok;
@@ -1638,6 +1639,7 @@ void GlobalParams::parseScreenType(GList
 	  fileName, line);
   }
 }
+*/
 
 
 void GlobalParams::parseBind(GList *tokens, GString *fileName, int line) {
--- xpdf-3.04.orig/xpdf/XPDFCore.cc
+++ xpdf-3.04/xpdf/XPDFCore.cc
@@ -684,6 +684,8 @@ void XPDFCore::doAction(LinkAction *acti
 
   // Movie action
   case actionMovie:
+
+/*
 if (!(cmd = xpdfParams->getMovieCommand())) {
   error(errConfig, -1, "No movieCommand defined in config file");
   break;
@@ -732,6 +734,8 @@ void XPDFCore::doAction(LinkAction *acti
   }
 }
 movieAnnot.free();
+*/
+error(errSyntaxError, -1, "Movie action needs fixing");
 break;
 
   // unsupported action types

Processed: Re: Bug#887506: notification-daemon: The notification-daemon binary moved to a different location

[Debian Bug Tracking System]

Processing control commands:

> clone 887506 -2
Bug #887506 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Bug 887506 cloned as bug 887515
> severity -2 important
Bug #887515 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Severity set to 'important' from 'serious'
> clone -2 -3
Bug #887515 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Bug 887515 cloned as bug 887516
> clone -2 -4
Bug #887515 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Bug 887515 cloned as bug 887517
> reassign -2 python-notify2
Bug #887515 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Bug reassigned from package 'notification-daemon' to 'python-notify2'.
No longer marked as found in versions notification-daemon/3.20.0-2.
Ignoring request to alter fixed versions of bug #887515 to the same values 
previously set
> retitle -2 python-notify2: Don't rely on location of notification-daemon
Bug #887515 [python-notify2] notification-daemon: The notification-daemon 
binary moved to a different location
Changed Bug title to 'python-notify2: Don't rely on location of 
notification-daemon' from 'notification-daemon: The notification-daemon binary 
moved to a different location'.
> reassign -3 libgtk2-notify-perl
Bug #887516 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Bug reassigned from package 'notification-daemon' to 'libgtk2-notify-perl'.
No longer marked as found in versions notification-daemon/3.20.0-2.
Ignoring request to alter fixed versions of bug #887516 to the same values 
previously set
> retitle -3 libgtk2-notify-perl: Don't rely on location of notification-daemon
Bug #887516 [libgtk2-notify-perl] notification-daemon: The notification-daemon 
binary moved to a different location
Changed Bug title to 'libgtk2-notify-perl: Don't rely on location of 
notification-daemon' from 'notification-daemon: The notification-daemon binary 
moved to a different location'.
> reassign -4 golang-github-thecreeper-go-notify
Bug #887517 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Bug reassigned from package 'notification-daemon' to 
'golang-github-thecreeper-go-notify'.
No longer marked as found in versions notification-daemon/3.20.0-2.
Ignoring request to alter fixed versions of bug #887517 to the same values 
previously set
> retitle -4 golang-github-thecreeper-go-notify: Don't rely on location of 
> notification-daemon
Bug #887517 [golang-github-thecreeper-go-notify] notification-daemon: The 
notification-daemon binary moved to a different location
Changed Bug title to 'golang-github-thecreeper-go-notify: Don't rely on 
location of notification-daemon' from 'notification-daemon: The 
notification-daemon binary moved to a different location'.

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

Bug#887506: notification-daemon: The notification-daemon binary moved to a different location

[Simon McVittie]

Control: clone 887506 -2
Control: severity -2 important
Control: clone -2 -3
Control: clone -2 -4
Control: reassign -2 python-notify2
Control: retitle -2 python-notify2: Don't rely on location of 
notification-daemon
Control: reassign -3 libgtk2-notify-perl
Control: retitle -3 libgtk2-notify-perl: Don't rely on location of 
notification-daemon
Control: reassign -4 golang-github-thecreeper-go-notify
Control: retitle -4 golang-github-thecreeper-go-notify: Don't rely on location 
of notification-daemon

On Wed, 17 Jan 2018 at 17:47:03 +0200, Adrian Bunk wrote:
> debian/runtests.sh: 5: debian/runtests.sh: 
> /usr/lib/notification-daemon/notification-daemon: not found

The exact location of the notification daemon shouldn't be treated as API:
the entry point is /usr/share/applications/notification-daemon.desktop.
It's ${libexecdir}/notification-daemon, and the default ${libexecdir}
changed between debhelper compat levels (which is what happened here),
and might well change again in future (for example to /usr/libexec when
Debian Policy picks up a newer FHS version).

python-notify2's runtests.sh should launch the desktop file instead,
for example with gtk-launch from libgtk3-bin:

-/usr/lib/notification-daemon/notification-daemon &
+gtk-launch notification-daemon.desktop

The same is true for other packages that launch notification-daemon for
their tests.

> This is caused by the following unintentional
> change in notification-daemon 3.20.0-2:
> -/usr/lib/notification-daemon/notification-daemon
> +/usr/lib/x86_64-linux-gnu/notification-daemon

It would be straightforward to change this back by passing
--libexecdir=/usr/lib/notification-daemon to configure, and that's
probably the most expedient short-term answer (which is why I haven't
closed this bug, and why I reduced the severity of its clones).

smcv

Bug#885556: multipath-udeb: depends on a non-udeb package: liburcu6

[Cyril Brulebois]

Hi,

Michael Jeanson  (2018-01-15):
> I've uploaded 0.10.0-3 with the included patch and some other minor
> packaging fixes, it's sitting in the NEW queue because of the added
> udeb.

It seems my ftp-ping did the trick, and it's now built on all archs.

multipath-tools maintainers, do you have any pending changes you'd
like to upload, or should I request a binNMU of your package to fix
this installability issue for the udeb?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#887506: notification-daemon: The notification-daemon binary moved to a different location

[Adrian Bunk]

Package: notification-daemon
Version: 3.20.0-2
Severity: serious
Control: affects -1 src:python-notify2

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

...
rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-notify2-0.3'
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
PYTHONS="2.7 3.6" dbus-run-session -- xvfb-run -a debian/runtests.sh
debian/runtests.sh: 5: debian/runtests.sh: 
/usr/lib/notification-daemon/notification-daemon: not found
test_notify2.py:11: PyGIWarning: GdkPixbuf was imported without specifying a 
version first. Use gi.require_version('GdkPixbuf', '2.0') before import to 
ensure that the right version gets loaded.
  from gi.repository import GdkPixbuf
E
==
ERROR: test_get_server_caps (__main__.ModuleTests)
--
Traceback (most recent call last):
  File "test_notify2.py", line 17, in setUp
notify2.init("notify2 test suite")
  File "/build/1st/python-notify2-0.3/notify2.py", line 96, in init
'/org/freedesktop/Notifications')
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Notifications was not provided by any .service files
...


This is caused by the following unintentional
change in notification-daemon 3.20.0-2:
-/usr/lib/notification-daemon/notification-daemon
+/usr/lib/x86_64-linux-gnu/notification-daemon

Processed: notification-daemon: The notification-daemon binary moved to a different location

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python-notify2
Bug #887506 [notification-daemon] notification-daemon: The notification-daemon 
binary moved to a different location
Added indication that 887506 affects src:python-notify2

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

Bug#887503: trafficserver FTBFS on architectures where LuaJIT isn't used

[Adrian Bunk]

Source: trafficserver
Version: 7.1.1-1
Severity: serious

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

...
checking for lzma location... /usr
checking for lzma_code in -llzma... yes
checking lzma.h usability... yes
checking lzma.h presence... yes
checking for lzma.h... yes
checking for LUAJIT... no
checking for LUALIB... no
configure: error: Neither LuaJIT nor Lua package available

Bug#852578: marked as done (scsitools: Update udevadm path)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 14:52:35 +
with message-id 
and subject line Bug#852578: fixed in scsitools 0.12-3
has caused the Debian Bug report #852578,
regarding scsitools: Update udevadm path
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.)


-- 
852578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scsitools
Version: 0.12-2.3
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package scsitools does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Source: scsitools
Source-Version: 0.12-3

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated scsitools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jan 2018 15:11:13 +0100
Source: scsitools
Binary: scsitools
Architecture: source amd64
Version: 0.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Henriksson 
Description:
 scsitools  - Collection of tools for SCSI hardware management
Closes: 852578 887253
Changes:
 scsitools (0.12-3) unstable; urgency=medium
 .
   * QA upload.
   * Orphan package, no maintainer activity in 5+ years.
   * Add debian/patches/udevadm-use-PATH.patch (Closes: #852578)
   * Add Recommends e2fsprogs (Closes: #887253)
 - possibly used by tk_scsiformat and also init scripts.
   * Bump to debhelper compat 9, since anything before is deprecated.
   * Drop manual quilt usage in debian/rules (and build-dep)
 - package already is using source format '3.0 (quilt)'.
   * Modernize/simplify debian/rules
 - use dh override_* style overrides.
 - use debian/clean, debian/manpages, debian/docs instead of command
   line overrides.
   * Fix 'in in' typo in debian/README.Debian as pointed out by lintian.
Checksums-Sha1:
 3322d8ceede5dd141ab865c8fc72a0ebe35b6b5c 1706 scsitools_0.12-3.dsc
 73cff2d78726522868c8c4b6f302d095cc1972b1 30136 scsitools_0.12-3.debian.tar.xz
 b53b94a814709e71fdd4d9a419cd645782828302 10 
scsitools-dbgsym_0.12-3_amd64.deb
 9bea008ae096543944b41c1fdadf0af944f053fd 6176 scsitools_0.12-3_amd64.buildinfo
 e60dd313d1d45ccc820495204c67555c2250428b 119700 scsitools_0.12-3_amd64.deb
Checksums-Sha256:
 183a3292eda6a6478bea484cc2346a4108ee1bfba68dc79f297d782ef4d3fd79 1706 
scsitools_0.12-3.dsc
 6abbe069c5327ce56c97301a0c1203167667f81c70c60223082fb237d7d50c61 30136 
scsitools_0.12-3.debian.tar.xz
 07923decae73c255cafdb7ce4f5034799c727b035ff9c8c390bb8294d38d3453 10 
scsitools-dbgsym_0.12-3_amd64.deb
 5cd0b0a14da438597022557aca5057dadc6a53b31d5a6b553d84ed5726d04c28 6176 
scsitools_0.12-3_amd64.buildinfo
 402e4c52d2b100db67fa0c78aa03e6a276f9000dbac3124fbbad3bbb87cc4ada 119700 
scsitools_0.12-3_amd64.deb
Files:
 40c6a19f4af8bafb654ed98a1d0a6f87 1706 utils optional scsitools_0.12-3.dsc
 a4c5cf9ccd8fd5aa2b421310339b3c73 30136 utils optional 
scsitools_0.12-3.debian.tar.xz
 cd1a31a056e1dd0c718bbcc868453e1b 10 debug optional 
scsitools-dbgsym_0.12-3_amd64.deb
 5d17d58d8c4a1b1dd7905eb826b14391 6176 utils optional 
scsitools_0.12-3_amd64.buildinfo
 e7424214043adad7a73c7255ba446ef1 119700 utils optional 
scsitools_0.12-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlpfWbgRHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwbZ6g//W4vTkUdCFMaMzuPGjDVgKrrw0W7iQKr2

Bug#886990: transmission: rpc session-id mechanism design flaw results in RCE

[Vincent Lefevre]

On 2018-01-14 23:20:39 +0530, Abhijith PA wrote:
> Why isn't this vulnerability have CVE id ?. The security-tracker[1]
> shows a temporary id.

This is CVE-2018-5702:

  https://security-tracker.debian.org/tracker/CVE-2018-5702

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

Bug#887488: [Pkg-electronics-devel] Bug#887488: openocd: CVE-2018-5704 cross protocol scripting attack

[Jonathan McDowell]

On Wed, Jan 17, 2018 at 10:50:44AM +0100, Guido Günther wrote:
> the following vulnerability was published for openocd.
> 
> CVE-2018-5704[0]:
> | Open On-Chip Debugger (OpenOCD) 0.10.0 does not block attempts to use
> | HTTP POST for sending data to 127.0.0.1 port , which allows remote
> | attackers to conduct cross-protocol scripting attacks, and consequently
> | execute arbitrary commands, via a crafted web site.
> 
> 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-2018-5704
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5704
> 
> Please adjust the affected versions in the BTS as needed.

I see Salvatore has marked this as affecting 0.10.0-3, I'm not sure
there's any reason to believe 0.9.0-1 isn't affected as well but I will
need to check later today. Upstream still seem to be discussing the best
fix but I think at least:

http://openocd.zylin.com/#/c/4335/
and
http://openocd.zylin.com/#/c/4331/

seem appropriate pending anything more complete.

J.

-- 
Revd Jonathan McDowell, ULC | I've got a trigger inside.

Bug#886506: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Raphael Hertzog]

Hello,

On Wed, 17 Jan 2018, Aurelien Jarno wrote:
> busybox is compiled with -mpreferred-stack-boundary=2 on i386 which has
> the same effect of reducing the default stack alignment from 16 bytes to
> 2 bytes. This comes from arch/i386/Makefile:
> 
> |  # -mpreferred-stack-boundary=2 is essential in preventing gcc 4.2.x
> |  # from aligning stack to 16 bytes. (Which is gcc's way of supporting SSE).
> |  CFLAGS += $(call cc-option,-march=i386 -mpreferred-stack-boundary=2,)
> 
> I don't really get why it is essential to prevent gcc from aligning
> stack to 16 bytes, anyway this is a bad idea. Removing this option just
> fixes the issue.

I confirm that rebuilding busybox with this option dropped fixed the issue
for me. I uploaded a fixed busybox to Kali. I'm happy to do the same for
Debian if it can help the current maintainers.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Processed: found 887488 in 0.10.0-3

[Debian Bug Tracking System]

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

> # present in at last 0.10.0 source wise
> found 887488 0.10.0-3
Bug #887488 [openocd] openocd: CVE-2018-5704 cross protocol scripting attack
Marked as found in versions openocd/0.10.0-3.
> thanks
Stopping processing here.

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

Bug#886506: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Aurelien Jarno]

control: reassign -1 busybox
control: retitle -1 busybox: wrongly compiled with -mpreferred-stack-boundary=2 
on i386

On 2018-01-17 12:08, Raphael Hertzog wrote:
> Control: reassign -1 src:glibc 2.26-1
> Control: retitle -1 busybox sh broken on i386 with glibc 2.26, leads to 
> kernel panic
> Control: severity -1 serious
> Control: affects -1 + busybox src:linux
> 
> Hello,
> 
> on i386 with glibc 2.26-4, busybox sh is broken:
> 
> $ busybox sh
> [...]
> BusyBox v1.27.2 (Debian 1:1.27.2-2) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> Segmentation fault
> 
> In the kernel messages, you see this:
> [1097712.640730] traps: busybox[3288] general protection ip:f7e9a51d 
> sp:ff8da68c error:0 in libc-2.26.so[f7d48000+1cd000]
> 
> There's a work-around (the same as the one described in
> #887169):
> 
> $ GLIBC_TUNABLES=glibc.tune.hwcaps=-SSE4_2 busybox sh
> [...]
> BusyBox v1.27.2 (Debian 1:1.27.2-2) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> ~ $
> 
> Given that busybox's sh is used in the initrd and that the init
> command is a shell script, this will lead to the kernel panic
> shown earlier in this bug report.
> 
> Possible work-arounds in the mean time:
> - disable busybox in the initrd by setting BUSYBOX=n in
>   /etc/initramfs-tools/initramfs.conf (but this is not
>   possible if you use cryptsetup)
> - you can add the "GLIBC_TUNABLES=glibc.tune.hwcaps=-SSE4_2" to the kernel
>   command line so that it's set in the environment of the init script
>   (this will at least let you boot once to fix it permanently)
> - install busybox-static instead of busybox (since it was built with
>   an earlier version of glibc) and rebuild your initrd.
> 
> Aurélien Jaron commented on IRC that this was strange that busybox
> was affected by this bug since the analysis made in #887169 lead to
> believe that only binaries compiled with -mstack-align=4 would be
> affected.

busybox is compiled with -mpreferred-stack-boundary=2 on i386 which has
the same effect of reducing the default stack alignment from 16 bytes to
2 bytes. This comes from arch/i386/Makefile:

|  # -mpreferred-stack-boundary=2 is essential in preventing gcc 4.2.x
|  # from aligning stack to 16 bytes. (Which is gcc's way of supporting SSE).
|  CFLAGS += $(call cc-option,-march=i386 -mpreferred-stack-boundary=2,)

I don't really get why it is essential to prevent gcc from aligning
stack to 16 bytes, anyway this is a bad idea. Removing this option just
fixes the issue.

I am therefore reassigning the bug to busybox.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Re: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 busybox
Bug #886506 [src:glibc] busybox sh broken on i386 with glibc 2.26, leads to 
kernel panic
Bug reassigned from package 'src:glibc' to 'busybox'.
No longer marked as found in versions glibc/2.26-1.
Ignoring request to alter fixed versions of bug #886506 to the same values 
previously set
> retitle -1 busybox: wrongly compiled with -mpreferred-stack-boundary=2 on i386
Bug #886506 [busybox] busybox sh broken on i386 with glibc 2.26, leads to 
kernel panic
Changed Bug title to 'busybox: wrongly compiled with 
-mpreferred-stack-boundary=2 on i386' from 'busybox sh broken on i386 with 
glibc 2.26, leads to kernel panic'.

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

Processed: busybox sh broken on i386 with glibc 2.26, leads to kernel panic

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:glibc 2.26-1
Bug #886506 [src:linux] linux-image-4.14.0-3-686-pae: Kernel panic during 
reboot - since 4.14.0-2 - 4.14.0-1 works normal and boots
Bug reassigned from package 'src:linux' to 'src:glibc'.
No longer marked as found in versions linux/4.14.12-2 and linux/4.14.7-1.
Ignoring request to alter fixed versions of bug #886506 to the same values 
previously set
Bug #886506 [src:glibc] linux-image-4.14.0-3-686-pae: Kernel panic during 
reboot - since 4.14.0-2 - 4.14.0-1 works normal and boots
Marked as found in versions glibc/2.26-1.
> retitle -1 busybox sh broken on i386 with glibc 2.26, leads to kernel panic
Bug #886506 [src:glibc] linux-image-4.14.0-3-686-pae: Kernel panic during 
reboot - since 4.14.0-2 - 4.14.0-1 works normal and boots
Changed Bug title to 'busybox sh broken on i386 with glibc 2.26, leads to 
kernel panic' from 'linux-image-4.14.0-3-686-pae: Kernel panic during reboot - 
since 4.14.0-2 - 4.14.0-1 works normal and boots'.
> severity -1 serious
Bug #886506 [src:glibc] busybox sh broken on i386 with glibc 2.26, leads to 
kernel panic
Severity set to 'serious' from 'important'
> affects -1 + busybox src:linux
Bug #886506 [src:glibc] busybox sh broken on i386 with glibc 2.26, leads to 
kernel panic
Added indication that 886506 affects busybox and src:linux

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

Processed: bug 887488 is forwarded to https://sourceforge.net/p/openocd/mailman/message/36188041/

[Debian Bug Tracking System]

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

> forwarded 887488 https://sourceforge.net/p/openocd/mailman/message/36188041/
Bug #887488 [openocd] openocd: CVE-2018-5704 cross protocol scripting attack
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/openocd/mailman/message/36188041/'.
> thanks
Stopping processing here.

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

Bug#887488: openocd: CVE-2018-5704 cross protocol scripting attack

[Guido Günther]

Package: openocd
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: important

Hi,

the following vulnerability was published for openocd.

CVE-2018-5704[0]:
| Open On-Chip Debugger (OpenOCD) 0.10.0 does not block attempts to use
| HTTP POST for sending data to 127.0.0.1 port , which allows remote
| attackers to conduct cross-protocol scripting attacks, and consequently
| execute arbitrary commands, via a crafted web site.

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-2018-5704
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5704

Please adjust the affected versions in the BTS as needed.

Bug#873328: marked as done (trafficserver FTBFS with luajit 2.1)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 09:38:05 +
with message-id 
and subject line Bug#873328: fixed in trafficserver 7.1.1-1
has caused the Debian Bug report #873328,
regarding trafficserver FTBFS with luajit 2.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.)


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

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

...
In file included from repl.cc:25:0:
bindings.h:65:67: error: 'luaL_reg' does not name a type; did you mean 
'luaL_ref'?
   static void register_metatable(lua_State *, const char *, const luaL_reg *);
   ^~~~
   luaL_ref
Makefile:716: recipe for target 'repl.lo' failed
make[4]: *** [repl.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 7.1.1-1

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

Debian distribution maintenance software
pp.
Jean Baptiste Favre  (supplier of updated trafficserver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Jan 2018 13:30:43 +0100
Source: trafficserver
Binary: trafficserver trafficserver-experimental-plugins trafficserver-dev
Architecture: source amd64
Version: 7.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Aron Xu 
Changed-By: Jean Baptiste Favre 
Description:
 trafficserver - fast, scalable and extensible HTTP/1.1 compliant caching proxy 
se
 trafficserver-dev - Apache Traffic Server Software Developers Kit (SDK)
 trafficserver-experimental-plugins - experimental plugins for Apache Traffic 
Server
Closes: 859750 873328 877457
Changes:
 trafficserver (7.1.1-1) unstable; urgency=medium
 .
   * Fix trafficserver-dev dependencies. (Closes: #877457)
   * Fix d/gbp.conf. Remove duplicate filter option
   * Update standards version in d/control
   * Fix debian-rules-sets-dpkg-architecture-variable lintian warning
   * Fix debian-watch-uses-insecure-uri lintian info
   * Update d/patches
   * Update d/rules to reflect healthcheck being managed as a stable plugin
   * Add a patch to fix kfreebsd build
   * Add a patch to fix arm build
   * New upstream version 7.1.0
   * Remove broken 0008-fix_build_armel patch
   * Patches refresh for 7.1.0
   * Add new patch to fix build with luajit 2.1 (Closes: #873328)
   * Update experimental modules list
   * Update Debian Standards-Version & d/compat
   * Update Vcs-* fields to use secure communication
   * Lintian fix for d/NEWS
   * Add new build option to use system luajit
   * Update build dependencies (Closes: #859750)
   * Fix lintian warning in d/copyright
   * New upstream version 7.1.1
   * Patches refresh for 7.1.1
Checksums-Sha1:
 389a29b6b9fe6b3d35d10cfb81d0ef54a91f865e 2722 trafficserver_7.1.1-1.dsc
 05d32314de2045b2fedd60707d8afe0e7c1d66cd 9036381 
trafficserver_7.1.1.orig.tar.bz2
 1f2ec349361e11b74c5af0c2a82bc7f3f06fe2c7 1179964 
trafficserver_7.1.1-1.debian.tar.xz
 56c9f33ef5cf4d7ee3b58177fccfbc10c8ee5f6c 42881204 
trafficserver-dbgsym_7.1.1-1_amd64.deb
 3cd67a8acf884524d872b5203ceb4f506b954764 5309904 
trafficserver-dev_7.1.1-1_amd64.deb
 63b232b44ffbad53989302c9ff3caf185a0c05b0 2352504 
trafficserver-experimental-plugins-dbgsym_7.1.1-1_amd64.deb
 a2a41a5078e668b25aef2cd57f294c3ca6d697f2 289524 
trafficserver-experimental-plugins_7.1.1-1_amd64.deb
 7f56bbc2f6a31bd159cf88824f1390d7a06855ce 14841 
trafficserver_7.1.1-1_amd64.buildinfo
 20ad2ae1b8af18a361188c7a153216a507048e35 2816632 
trafficserver_7.1.1-1_amd64.deb
Checksums-Sha256:
 1a53b5940717bf575f07068817a4e3d4044fe58253ab5d0e7fa50c25f4ac7ffa 2722 
trafficserver_7.1.1-1.dsc
 2c7ec32ef1460a76e5ee0e7caf95e9b6ca6b7c9612f135d280171bb2166ded36 9036381 

Bug#859750: marked as done (trafficserver: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 09:38:05 +
with message-id 
and subject line Bug#859750: fixed in trafficserver 7.1.1-1
has caused the Debian Bug report #859750,
regarding trafficserver: Please migrate to openssl1.1 in Buster
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.)


-- 
859750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trafficserver
Version: 7.0.0-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
control: forwarded -1 https://issues.apache.org/jira/browse/TS-5059

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828578. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/trafficserver_6.1.1-1_amd64-20160529-1545

Sebastian
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 7.1.1-1

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

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

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

Debian distribution maintenance software
pp.
Jean Baptiste Favre  (supplier of updated trafficserver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Jan 2018 13:30:43 +0100
Source: trafficserver
Binary: trafficserver trafficserver-experimental-plugins trafficserver-dev
Architecture: source amd64
Version: 7.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Aron Xu 
Changed-By: Jean Baptiste Favre 
Description:
 trafficserver - fast, scalable and extensible HTTP/1.1 compliant caching proxy 
se
 trafficserver-dev - Apache Traffic Server Software Developers Kit (SDK)
 trafficserver-experimental-plugins - experimental plugins for Apache Traffic 
Server
Closes: 859750 873328 877457
Changes:
 trafficserver (7.1.1-1) unstable; urgency=medium
 .
   * Fix trafficserver-dev dependencies. (Closes: #877457)
   * Fix d/gbp.conf. Remove duplicate filter option
   * Update standards version in d/control
   * Fix debian-rules-sets-dpkg-architecture-variable lintian warning
   * Fix debian-watch-uses-insecure-uri lintian info
   * Update d/patches
   * Update d/rules to reflect healthcheck being managed as a stable plugin
   * Add a patch to fix kfreebsd build
   * Add a patch to fix arm build
   * New upstream version 7.1.0
   * Remove broken 0008-fix_build_armel patch
   * Patches refresh for 7.1.0
   * Add new patch to fix build with luajit 2.1 (Closes: #873328)
   * Update experimental modules list
   * Update Debian Standards-Version & d/compat
   * Update Vcs-* fields to use secure communication
   * Lintian fix for d/NEWS
   * Add new build option to use system luajit
   * Update build dependencies (Closes: #859750)
   * Fix lintian warning in d/copyright
   * New upstream version 7.1.1
   * Patches refresh for 7.1.1
Checksums-Sha1:
 389a29b6b9fe6b3d35d10cfb81d0ef54a91f865e 2722 trafficserver_7.1.1-1.dsc
 05d32314de2045b2fedd60707d8afe0e7c1d66cd 9036381 
trafficserver_7.1.1.orig.tar.bz2
 1f2ec349361e11b74c5af0c2a82bc7f3f06fe2c7 1179964 
trafficserver_7.1.1-1.debian.tar.xz
 56c9f33ef5cf4d7ee3b58177fccfbc10c8ee5f6c 42881204 
trafficserver-dbgsym_7.1.1-1_amd64.deb
 3cd67a8acf884524d872b5203ceb4f506b954764 5309904 
trafficserver-dev_7.1.1-1_amd64.deb
 63b232b44ffbad53989302c9ff3caf185a0c05b0 2352504 
trafficserver-experimental-plugins-dbgsym_7.1.1-1_amd64.deb
 a2a41a5078e668b25aef2cd57f294c3ca6d697f2 289524 
trafficserver-experimental-plugins_7.1.1-1_amd64.deb
 7f56bbc2f6a31bd159cf88824f1390d7a06855ce 14841 
trafficserver_7.1.1-1_amd64.buildinfo
 20ad2ae1b8af18a361188c7a153216a507048e35 2816632 
trafficserver_7.1.1-1_amd64.deb
Checksums-Sha256:
 1a53b5940717bf575f07068817a4e3d4044fe58253ab5d0e7fa50c25f4ac7ffa 2722 
trafficserver_7.1.1-1.dsc
 2c7ec32ef1460a76e5ee0e7caf95e9b6ca6b7c9612f135d280171bb2166ded36 9036381 
trafficserver_7.1.1.orig.tar.bz2
 9108e03cd6277151750a62bacacfe08f473f369d47defa4ed695c1bdd7870138 

Bug#877457: marked as done (trafficserver-dev: missing Depends: trafficserver (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2018 09:38:05 +
with message-id 
and subject line Bug#877457: fixed in trafficserver 7.1.1-1
has caused the Debian Bug report #877457,
regarding trafficserver-dev: missing Depends: trafficserver (= 
${binary:Version})
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.)


-- 
877457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trafficserver-dev
Version: 7.0.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m23.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/trafficserver/libtsutil.so -> libtsutil.so.7.0.0
  /usr/lib/trafficserver/libtsmgmt.so -> libtsmgmt.so.7.0.0
  /usr/lib/trafficserver/libtsconfig.so -> libtsconfig.so.7.0.0
  /usr/lib/trafficserver/libatscppapi.so -> libatscppapi.so.7.0.0


Given that these are in a package subdirectory, maybe they are not intended
to be used by other packages and should not have .so links in the -dev
package at all.

Otherwise if would probably be useful to split out to shared libraries
into (a) separate package(s).


cheers,

Andreas


trafficserver-dev_7.0.0-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 7.1.1-1

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

Debian distribution maintenance software
pp.
Jean Baptiste Favre  (supplier of updated trafficserver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Jan 2018 13:30:43 +0100
Source: trafficserver
Binary: trafficserver trafficserver-experimental-plugins trafficserver-dev
Architecture: source amd64
Version: 7.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Aron Xu 
Changed-By: Jean Baptiste Favre 
Description:
 trafficserver - fast, scalable and extensible HTTP/1.1 compliant caching proxy 
se
 trafficserver-dev - Apache Traffic Server Software Developers Kit (SDK)
 trafficserver-experimental-plugins - experimental plugins for Apache Traffic 
Server
Closes: 859750 873328 877457
Changes:
 trafficserver (7.1.1-1) unstable; urgency=medium
 .
   * Fix trafficserver-dev dependencies. (Closes: #877457)
   * Fix d/gbp.conf. Remove duplicate filter option
   * Update standards version in d/control
   * Fix debian-rules-sets-dpkg-architecture-variable lintian warning
   * Fix debian-watch-uses-insecure-uri lintian info
   * Update d/patches
   * Update d/rules to reflect healthcheck being managed as a stable plugin
   * Add a patch to fix kfreebsd build
   * Add a patch to fix arm build
   * New upstream version 7.1.0
   * Remove broken 0008-fix_build_armel patch
   * Patches refresh for 7.1.0
   * Add new patch to fix build with luajit 2.1 (Closes: #873328)
   * Update experimental modules list
   * Update Debian Standards-Version & d/compat
   * Update Vcs-* fields to use secure communication
   * Lintian fix for d/NEWS
   * Add new build option to use system luajit
   * Update build dependencies (Closes: #859750)
   * Fix lintian warning in d/copyright
   * New upstream version 7.1.1
   * Patches refresh for 7.1.1
Checksums-Sha1:
 389a29b6b9fe6b3d35d10cfb81d0ef54a91f865e 2722 trafficserver_7.1.1-1.dsc
 05d32314de2045b2fedd60707d8afe0e7c1d66cd 9036381 
trafficserver_7.1.1.orig.tar.bz2
 1f2ec349361e11b74c5af0c2a82bc7f3f06fe2c7 1179964 
trafficserver_7.1.1-1.debian.tar.xz
 56c9f33ef5cf4d7ee3b58177fccfbc10c8ee5f6c 42881204 
trafficserver-dbgsym_7.1.1-1_amd64.deb
 3cd67a8acf884524d872b5203ceb4f506b954764 5309904 
trafficserver-dev_7.1.1-1_amd64.deb
 63b232b44ffbad53989302c9ff3caf185a0c05b0 2352504 
trafficserver-experimental-plugins-dbgsym_7.1.1-1_amd64.deb
 a2a41a5078e668b25aef2cd57f294c3ca6d697f2 289524 
trafficserver-experimental-plugins_7.1.1-1_amd64.deb
 

Bug#887482: xorg-server: FTBFS: dh_autoreconf can only be run once

[Daniel Schepler]

Source: xorg-server
Version: 2:1.19.5-1
Severity: serious

>From my pbuilder build log:

...
make[6]: Leaving directory
'/build/xorg-server-1.19.5/debian/build/udeb/test/xi2'
make[5]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test'
make[4]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test'
make[4]: Entering directory '/build/xorg-server-1.19.5/debian/build/udeb'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb'
make[3]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb'
make[2]: Leaving directory '/build/xorg-server-1.19.5'
  debian/rules override_dh_auto_test
make[2]: Entering directory '/build/xorg-server-1.19.5'
dh_auto_test -- -j1 VERBOSE=1
make[2]: Leaving directory '/build/xorg-server-1.19.5'
make[1]: Leaving directory '/build/xorg-server-1.19.5'
  dh_quilt_patch -O--parallel -Nxserver-common -Nxorg-server-source
File series fully applied, ends at patch 06_use-intel-only-on-pre-gen4.diff
  dh_update_autotools_config -O--parallel -Nxserver-common -Nxorg-server-source
  dh_autoreconf -O--parallel -Nxserver-common -Nxorg-server-source
dh_autoreconf: Can only be run once, see dh-autoreconf(7)
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

On further testing, it seems that on a freshly unpacked source, either
"dpkg-buildpackage -B" or "dpkg-buildpackage -A" separately will work;
but "dpkg-buildpackage -b" will fail with the above error.
-- 
Daniel Schepler

Bug#865497: support status of check-mk-agent

[Bastian Blank]

Hi

Is the agent still supported outside that "OMD environment"?

Bastian

-- 
Another Armenia, Belgium ... the weak innocents who always seem to be
located on a natural invasion route.
-- Kirk, "Errand of Mercy", stardate 3198.4