Bug#918848: Really bad regression

[Nye Liu]

https://github.com/systemd/systemd/issues/11502

Bug#918841: Really bad regression

[Nye Liu]

https://github.com/systemd/systemd/issues/11502 

Bug#919002: Really bad regression

[Nye Liu]

https://github.com/systemd/systemd/issues/11502

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

[Ximin Luo]

Control: severity -1 important
Control: tag -1 + moreinfo unreproducible

I can't reproduce this, can you install cargo-dbgsym rustc-dbgsym rust-gdb 
libstd-rust-1.31-dbgsym libllvm7-dbgsym libc6-dbg and provide a backtrace?

X

Josh Triplett:
> Package: cargo
> Version: 0.31.1-1
> Severity: grave
> 
> Any time I try to update the crates.io index with the currently packaged
> version of cargo, I get a segfault:
> 
> $ cargo update
> Updating crates.io index
> Segmentation fault
> 
> I can reproduce this in a brand new project (`cargo new foo`) by adding
> any dependency to `Cargo.toml` (e.g. `strsim = "*"`) and then running
> `cargo update`.
> 
> libgit2 was just updated recently; that might potentially be related.
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages cargo depends on:
> ii  binutils2.31.1-11
> ii  gcc 4:8.2.0-2
> ii  gcc-7 [c-compiler]  7.4.0-2
> ii  gcc-8 [c-compiler]  8.2.0-14
> ii  libc6   2.28-4
> ii  libcurl3-gnutls 7.62.0-1
> ii  libgcc1 1:8.2.0-14
> ii  libgit2-27  0.27.7+dfsg.1-0.1
> ii  libssh2-1   1.8.0-2
> ii  libssl1.1   1.1.1a-1
> ii  rustc   1.31.0+dfsg1-2
> ii  zlib1g  1:1.2.11.dfsg-1
> 
> cargo recommends no packages.
> 
> Versions of packages cargo suggests:
> pn  cargo-doc  
> ii  python33.7.1-3
> 
> -- no debconf information
> 
> ___
> Pkg-rust-maintainers mailing list
> pkg-rust-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Processed: Re: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #918854 [cargo] segfault updating crates.io index
Severity set to 'important' from 'grave'
> tag -1 + moreinfo unreproducible
Bug #918854 [cargo] segfault updating crates.io index
Added tag(s) unreproducible and moreinfo.

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

Bug#919064: scala FTBFS: java.lang.NoClassDefFoundError: com/tonicsystems/jarjar/asm/commons/ModuleHashesAttribute

[Andreas Tille]

Hi Java team,

I realised that there is no comment on this bug yet.  Since several of
my packages got a "removal from testing warning": Can I help somehow?
Not that I had the slightest idea what to do about this bug but may be
you have some idea I could test?  I've seen that there is a new upstream
version (2.12.8) - may be I should give it a try but I have no idea
about consequences of exchanging a package that has lots or rdepends
currently and whether this would qualify as "transition".

Any ideas?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#919855: s390x executables crash

[Ben Hutchings]

Source: klibc
Version: 2.0.5-1
Severity: serious

While investigating some test failures on klibc upstream, I found that
the new Debian version crashes on s390x.  It looks like this is due to
an address collision between the build ID in the shared library and
the code in the executables.  The addition of build IDs is not (yet)
part of an upstream release.

Ben.

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

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

Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Ying-Chun Liu (PaulLiu)]

Santiago Vila 於 2019/1/20 上午1:35 寫道:
> Package: src:libjstun-java
> Version: 0.7.3+dfsg-1
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with javahelper
>dh_update_autotools_config -i
>jh_linkjars -i
>jh_build -i
> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
> /usr/lib/jvm/default-java/bin/javac -g -cp 
> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
>  -d debian/_jh_build.libjstun-java -source 1.7 -target 1.7 -encoding ISO8859-1
> warning: [options] bootstrap class path not set in conjunction with -source 7
> Note: src/de/javawi/jstun/test/demo/ice/ICENegociator.java uses unchecked or 
> unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 1 warning
> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
> /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
> /usr/share/doc/default-jdk-doc/api -link 
> /usr/share/doc/default-jre-headless/api -classpath 
> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
>  -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
> -source 1.7
> Creating destination directory: "debian/_jh_build.javadoc/api/"
> javadoc: error - The code being documented uses packages in the unnamed 
> module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are 
> in named modules.
> javadoc: error - The code being documented uses packages in the unnamed 
> module, but the packages defined in /usr/share/doc/default-jre-headless/api/ 
> are in named modules.
> 2 errors
> make: *** [debian/rules:11: build-indep] Error 123
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 
> 
> (The above is just how the builds ends and not necessarily the most relevant 
> part)
> 
> The build was made in my autobuilder with "dpkg-buildpackage -A"
> and it also fails here:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjstun-java.html
> 
> where you can get a full build log if you need it.
> 
> If this is really a bug in one of the build-depends, please use reassign and 
> affects,
> so that this is still visible in the BTS web page for this package.
> 
> Thanks.
> 

Hi Santiago,

It seems to me that this line causes the problem.
find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link
/usr/share/doc/default-jdk-doc/api -link
/usr/share/doc/default-jre-headless/api -classpath
/usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
-d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp
-source 1.7

But if remove "-link /usr/share/doc/default-jdk-doc/api -link
/usr/share/doc/default-jre-headless/api", then it will pass.

I'm wondering if javahelper needs to call javadoc in different way.

Yours,
Paul

-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) 



signature.asc
Description: OpenPGP digital signature

Bug#919850: python3-link-grammar: broken symlink: /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> _clinkgrammar.so.5.5.1

[Andreas Beckmann]

Package: python3-link-grammar
Version: 5.5.1-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...):

1m41.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> 
_clinkgrammar.so.5.5.1 (python3-link-grammar)

But there is 

  /usr/lib/python3/dist-packages/linkgrammar/_clinkgrammar.so.5.5.1

so this seems to be a site-packages/dist-packages mixup.


cheers,

Andreas


python3-link-grammar_5.5.1-5.log.gz
Description: application/gzip

Bug#919848: tclxml-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtclxmlstub.a -> libtclxmlstub3.2.a

[Andreas Beckmann]

Package: tclxml-dev
Version: 1:3.2.7-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m28.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libtclxmlstub.a -> libtclxmlstub3.2.a (tclxml-dev)

The static library does not seem to be available in any package in the archive.


cheers,

Andreas


tclxml-dev_1:3.2.7-2.log.gz
Description: application/gzip

Bug#919847: ruby-rails-assets-markdown-it: missing Depends: libjs-markdown-it

[Andreas Beckmann]

Package: ruby-rails-assets-markdown-it
Version: 8.4.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...):

0m28.5s ERROR: FAIL: Broken symlinks:
  
/usr/share/ruby-rails-assets-markdown-it/app/assets/javascripts/markdown-it/markdown-it.js
 -> ../../../../../javascript/markdown-it/markdown-it.js 
(ruby-rails-assets-markdown-it)


cheers,

Andreas


ruby-rails-assets-markdown-it_8.4.2-1.log.gz
Description: application/gzip

Bug#919846: ruby-rails-assets-highlightjs: missing Depends: libjs-highlight.js

[Andreas Beckmann]

Package: ruby-rails-assets-highlightjs
Version: 9.12.0-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...):

0m30.0s ERROR: FAIL: Broken symlinks:
  
/usr/share/ruby-rails-assets-highlightjs/app/assets/javascripts/highlightjs/highlight.pack.js
 -> ../../../../../javascript/highlight.js/highlight.min.js 
(ruby-rails-assets-highlightjs)


cheers,

Andreas


ruby-rails-assets-highlightjs_9.12.0-1.log.gz
Description: application/gzip

Bug#919843: lirc-doc: broken symlinks: /usr/share/doc/lirc/lirc.org/* -> /build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/*

[Andreas Beckmann]

Package: lirc-doc
Version: 0.10.1-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...):

0m24.4s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/lirc/plugindocs/var -> /var/lib/lirc/plugins (lirc-doc)
  /usr/share/doc/lirc/plugindocs/lirc.css -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/html/lirc.css 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/marb18.jpg -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/marb18.jpg 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/lirc.gif -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/lirc.gif 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/favicon.ico -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/favicon.ico
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/diode.gif -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/diode.gif 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/atwf83.jpg -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/atwf83.jpg 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/html/table.html -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/html/table.html 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/html/plugins-index.html -> 
/var/lib/lirc/plugins/index.html (lirc-doc)
  /usr/share/doc/lirc/lirc.org/html/lirc.css -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/html/lirc.css 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/variables_4.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_5.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/groups_4.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_13.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/functions_12.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_15.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/defines_a.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_16.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/classes_e.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_14.js
 (lirc-doc)


The targets are absolute build-time paths ...


cheers,

Andreas


lirc-doc_0.10.1-5.log.gz
Description: application/gzip

Bug#919841: node-istanbul: broken symlinks: /usr/lib/nodejs/istanbul/lib/assets/vendor/prettify.{css,js} -> ../../../../../../share/javascript/prettify.{css,js}

[Andreas Beckmann]

Package: node-istanbul
Version: 0.4.5+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

1m33.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/nodejs/istanbul/lib/assets/vendor/prettify.js  -> 
../../../../../../share/javascript/prettify.js (node-istanbul)
  /usr/lib/nodejs/istanbul/lib/assets/vendor/prettify.css -> 
../../../../../../share/javascript/prettify.css (node-istanbul)

  ^^^

libjs-prettify would provide /usr/share/javascript/prettify/prettify.js
 

cheers,

Andreas


node-istanbul_0.4.5+ds-2.log.gz
Description: application/gzip

Bug#919840: sqwebmail: leaves broken symlink after purge: /etc/apache2/conf-available/sqwebmail.conf -> ../../sqwebmail/apache24.conf

[Andreas Beckmann]

Package: sqwebmail
Version: 6.0.0+1.0.5-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...):

0m54.4s ERROR: FAIL: Broken symlinks:
  /etc/apache2/conf-available/sqwebmail.conf -> ../../sqwebmail/apache24.conf


cheers,

Andreas


sqwebmail_6.0.0+1.0.5-1.log.gz
Description: application/gzip

Bug#919836: jupyter-sphinx-theme-common: broken symlinks: /usr/share/jupyter_sphinx_theme/jupyter/static/boots{trap,watch}-2

[Andreas Beckmann]

Package: jupyter-sphinx-theme-common
Version: 0.0.6+ds1-4
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...):

0m30.4s ERROR: FAIL: Broken symlinks:
  /usr/share/jupyter_sphinx_theme/jupyter/static/bootswatch-2 -> 
../../../../lib/python2.7/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootswatch-2.3.2
 (jupyter-sphinx-theme-common)
  /usr/share/jupyter_sphinx_theme/jupyter/static/bootstrap-2 -> 
../../../../lib/python2.7/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootstrap-2.3.2
 (jupyter-sphinx-theme-common)

Since jupyter-sphinx-theme-common depends on python3-sphinx-bootstrap-theme,
the targets probably need to be adjusted to point into the python3 package
instead.


cheers,

Andreas


jupyter-sphinx-theme-common_0.0.6+ds1-4.log.gz
Description: application/gzip

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

[積丹尼 Dan Jacobson]

Thanks but one still must forbid
# aptitude search ~U
iFA libilmbase23
iFA libopenexr23
if gimp is to start on experimental.

Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

[Jérémy Lal]

Le dim. 20 janv. 2019 à 02:12, Andreas Beckmann  a écrit :

> Followup-For: Bug #905415
> Control: reopen -1
> Control: reassign -1 libnode-dev 10.15.0~dfsg-8
> Control: retitle -1 libnode-dev: broken symlinks:
> /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
>
> Hi,
>
> the package reorganisation changed th eissue but did not completely
> resolve it.
>
> From the attached log (scroll to the bottom...):
>
> 0m36.7s ERROR: FAIL: Broken symlinks:
>   /usr/include/nodejs/deps/uv/include/uv.h -> ../../../../uv.h
> (libnode-dev)
>   /usr/include/nodejs/deps/uv/include/uv -> ../../../../uv (libnode-dev)
>
> Is libnode-dev missing a Depends: libuv1-dev ?
>

Yes, it looks so it is missing libuv1-dev

Jérémy

Processed: limit source to nodejs, tagging 905415

[Debian Bug Tracking System]

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

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

> tags 905415 + pending
Bug #905415 [libnode-dev] libnode-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
Ignoring request to alter tags of bug #905415 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#905415: Bug #905415 in nodejs marked as pending

[Jérémy Lal]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/nodejs/commit/c57aaadcde0715b0b383c037382b310c8f2d2298


libnode-dev depends libuv1-dev (Closes: #905415)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905415

Processed: Bug #905415 in nodejs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905415 [libnode-dev] libnode-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
Added tag(s) pending.

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

Processed: reassign 919422 to firebird3.0-server, fixed 919422 in 3.0.5.33086.ds4-2 ...

[Debian Bug Tracking System]

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

> reassign 919422 firebird3.0-server 3.0.1.32609.ds4-14
Bug #919422 {Done: Damyan Ivanov } 
[firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb] 
firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb: When installing I get an error
Warning: Unknown package 'firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb'
Bug reassigned from package 'firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb' 
to 'firebird3.0-server'.
Ignoring request to alter found versions of bug #919422 to the same values 
previously set
No longer marked as fixed in versions firebird3.0/3.0.5.33086.ds4-2.
Bug #919422 {Done: Damyan Ivanov } [firebird3.0-server] 
firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb: When installing I get an error
Marked as found in versions firebird3.0/3.0.1.32609.ds4-14.
> fixed 919422 3.0.5.33086.ds4-2
Bug #919422 {Done: Damyan Ivanov } [firebird3.0-server] 
firebird3.0-server_3.0.1.32609.ds4-14_amd64.deb: When installing I get an error
Marked as fixed in versions firebird3.0/3.0.5.33086.ds4-2.
> reassign 901297 src:nodejs 10.4.0~dfsg-1
Bug #901297 {Done: Jérémy Lal } [libnode64-dev] 
libnode64-dev: rename to libnode-dev
Warning: Unknown package 'libnode64-dev'
Bug reassigned from package 'libnode64-dev' to 'src:nodejs'.
No longer marked as found in versions nodejs/10.4.0~dfsg-1.
No longer marked as fixed in versions nodejs/10.13.0~dfsg-1 and 
nodejs/10.12.0~dfsg-1.
Bug #901297 {Done: Jérémy Lal } [src:nodejs] libnode64-dev: 
rename to libnode-dev
Marked as found in versions nodejs/10.4.0~dfsg-1.
> fixed 901297 10.12.0~dfsg-1
Bug #901297 {Done: Jérémy Lal } [src:nodejs] libnode64-dev: 
rename to libnode-dev
Marked as fixed in versions nodejs/10.12.0~dfsg-1.
> fixed 875822 0.25-1.1+rm
Bug #875822 {Done: Adrian Bunk } [certmaster] certmaster: 
FTBFS: dh_installman: failed to read certmaster-request.1.gz
Warning: Unknown package 'certmaster'
There is no source info for the package 'certmaster' at version '0.25-1.1+rm' 
with architecture ''
Unable to make a source version for version '0.25-1.1+rm'
Marked as fixed in versions 0.25-1.1+rm.
Warning: Unknown package 'certmaster'
> fixed 876214 0.1.1-4+rm
Bug #876214 {Done: Adrian Bunk } [src:pond] pond: FTBFS  
cannot find package "appengine" "appengine/datastore" 
"github.com/agl/go-gtk/gdk" ...
Warning: Unknown package 'src:pond'
The source 'pond' and version '0.1.1-4+rm' do not appear to match any binary 
packages
Marked as fixed in versions pond/0.1.1-4+rm.
Warning: Unknown package 'src:pond'
> notfound 917867 2.6.1-1
Bug #917867 {Done: Afif Elghraoui } [singularity-container] 
singularity-container: not supportable for Stable
No longer marked as found in versions singularity-container/2.6.1-1.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 876231 ..., affects 903762

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 876231 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 905282 python-lldb-8/1:8~svn350193-1~exp1
Bug #905282 [python-lldb-6.0] python-lldb-6.0: broken symlinks: 
/usr/lib/llvm-6.0/lib/python2.7/site-packages/lldb/*
The source python-lldb-8 and version 1:8~svn350193-1~exp1 do not appear to 
match any binary packages
Marked as found in versions python-lldb-8/1:8~svn350193-1~exp1.
> found 857653 python-lldb-8/1:8~svn350193-1~exp1
Bug #857653 [liblld-6.0] liblld-4.0: missing liblld-4.0.so.1
The source python-lldb-8 and version 1:8~svn350193-1~exp1 do not appear to 
match any binary packages
Marked as found in versions python-lldb-8/1:8~svn350193-1~exp1.
> found 857680 python-lldb-8/1:8~svn350193-1~exp1
Bug #857680 [llvm-6.0-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source python-lldb-8 and version 1:8~svn350193-1~exp1 do not appear to 
match any binary packages
Marked as found in versions python-lldb-8/1:8~svn350193-1~exp1.
> affects 903762 + boinc-app-examples
Bug #903762 [boinc-server-maker] boinc-server-maker: fails to install: 
SyntaxError in /usr/lib/boinc-server-maker/sched/pymw_assimilator.py
Added indication that 903762 affects boinc-app-examples
> thanks
Stopping processing here.

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

Processed: Re: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #905415 {Done: Jérémy Lal } [libnode64-dev] 
libnode64-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/uv*.h -> 
../../../../uv*.h
Warning: Unknown package 'libnode64-dev'
'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
Warning: Unknown package 'libnode64-dev'
Warning: Unknown package 'libnode64-dev'
No longer marked as fixed in versions nodejs/10.12.0~dfsg-1 and 
nodejs/10.13.0~dfsg-1.
Warning: Unknown package 'libnode64-dev'
> reassign -1 libnode-dev 10.15.0~dfsg-8
Bug #905415 [libnode64-dev] libnode64-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/uv*.h -> ../../../../uv*.h
Warning: Unknown package 'libnode64-dev'
Bug reassigned from package 'libnode64-dev' to 'libnode-dev'.
No longer marked as found in versions nodejs/10.4.0~dfsg-1.
Ignoring request to alter fixed versions of bug #905415 to the same values 
previously set
Bug #905415 [libnode-dev] libnode64-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/uv*.h -> ../../../../uv*.h
Marked as found in versions nodejs/10.15.0~dfsg-8.
> retitle -1 libnode-dev: broken symlinks: 
> /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
Bug #905415 [libnode-dev] libnode64-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/uv*.h -> ../../../../uv*.h
Changed Bug title to 'libnode-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}' from 
'libnode64-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/uv*.h -> 
../../../../uv*.h'.

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

Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

[Andreas Beckmann]

Followup-For: Bug #905415
Control: reopen -1
Control: reassign -1 libnode-dev 10.15.0~dfsg-8
Control: retitle -1 libnode-dev: broken symlinks: 
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}

Hi,

the package reorganisation changed th eissue but did not completely
resolve it.

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

0m36.7s ERROR: FAIL: Broken symlinks:
  /usr/include/nodejs/deps/uv/include/uv.h -> ../../../../uv.h (libnode-dev)
  /usr/include/nodejs/deps/uv/include/uv -> ../../../../uv (libnode-dev)

Is libnode-dev missing a Depends: libuv1-dev ?


Andreas


libnode-dev_10.15.0~dfsg-8.log.gz
Description: application/gzip

Bug#919831: libcds-moc-java: FTBFS (The code being documented uses packages in the unnamed module)

[Santiago Vila]

Package: src:libcds-moc-java
Version: 5.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   jh_linkjars -i
   debian/rules override_jh_build
make[1]: Entering directory '/<>'
jh_build --javacopts="-encoding ISO-8859-15" --javadoc-opts="-encoding 
ISO-8859-15"
find cds -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/healpix.jar:debian/_jh_build.cds.moc -d 
debian/_jh_build.cds.moc -source 1.7 -target 1.7 -encoding ISO-8859-15
warning: [options] bootstrap class path not set in conjunction with -source 7
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
find cds -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
/usr/share/doc/default-jdk-doc/api -link 
/usr/share/doc/default-jre-headless/api -classpath 
/usr/share/java/healpix.jar:debian/_jh_build.cds.moc -d 
debian/_jh_build.javadoc/api -quiet -notimestamp -source 1.7 -encoding 
ISO-8859-15
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named 
modules.
javadoc: error - The code being documented uses packages in the unnamed module, 
but the packages defined in /usr/share/doc/default-jre-headless/api/ are in 
named modules.
cds/moc/HealpixMoc.java:517: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:518: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:519: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:520: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:982: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:982: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:974: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:990: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:307: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:307: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:377: warning - @param argument "npixs" is not a 
parameter name.
cds/moc/HealpixMoc.java:417: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:418: warning - @param argument "testHierarchy" is not a 
parameter name.
cds/moc/HealpixMoc.java:517: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:518: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:519: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:520: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:622: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:647: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:693: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:974: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:982: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:982: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:990: warning - invalid usage of tag <
cds/moc/IntArray.java:91: warning - invalid usage of tag >
cds/moc/IntArray.java:91: warning - invalid usage of tag >
cds/moc/LongArray.java:90: warning - invalid usage of tag >
cds/moc/LongArray.java:90: warning - invalid usage of tag >
cds/moc/MocIO.java:136: warning - invalid usage of tag &
cds/moc/MocIO.java:136: warning - invalid usage of tag &
cds/moc/MocIO.java:152: warning - invalid usage of tag >
cds/moc/ShortArray.java:92: warning - invalid usage of tag >
cds/moc/ShortArray.java:92: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:517: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:518: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:519: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:520: warning - invalid usage of tag >
cds/moc/IntArray.java:91: warning - invalid usage of tag >
cds/moc/LongArray.java:90: warning - invalid usage of tag >
cds/moc/ShortArray.java:92: warning - invalid usage of tag >
cds/moc/MocIO.java:136: warning - invalid usage of tag &
cds/moc/HealpixMoc.java:982: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:982: warning - invalid usage of tag <
cds/moc/HealpixMoc.java:974: warning - invalid usage of tag >
cds/moc/HealpixMoc.java:990: warning - invalid usage of tag <
2 errors
45 warnings
make[1]: *** [debian/rules:10: override_jh_build] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with 

Bug#917482: marked as done (jhove: FTBFS in buster at least since 2018-12-07)

[Debian Bug Tracking System]

Your message dated Sun, 20 Jan 2019 00:35:01 +
with message-id 
and subject line Bug#917482: fixed in jhove 1.20.1-5
has caused the Debian Bug report #917482,
regarding jhove: FTBFS in buster at least since 2018-12-07
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.)


-- 
917482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jhove
Version: 1.20.1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -pjhove --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...

[... snipped ...]

[INFO] JHOVE - JSTOR/Harvard Object Validation Environment  SUCCESS [  0.009 s]
[INFO] JHOVE Core . SUCCESS [  4.465 s]
[INFO] JHOVE Validation Modules ... FAILURE [  2.348 s]
[INFO] JHOVE Applications . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  7.061 s
[INFO] Finished at: 2018-12-25T23:16:10Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jhove-modules: Compilation failure: Compilation failure: 
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[13,22]
 package javax.xml.bind does not exist
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[13,22]
 package javax.xml.bind does not exist
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[216,29]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class 
edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[219,29]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class 
edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[261,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[265,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[269,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[273,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class 

Processed: reassign 919826 to src:linux, severity of 919826 is important

[Debian Bug Tracking System]

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

> reassign 919826 src:linux 4.19.12-1
Bug #919826 [linux-image-4.19.0-1-arm64] linux-image-4.19.0-1-arm64: Loading 
Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic
Bug reassigned from package 'linux-image-4.19.0-1-arm64' to 'src:linux'.
Ignoring request to alter found versions of bug #919826 to the same values 
previously set
Ignoring request to alter fixed versions of bug #919826 to the same values 
previously set
Bug #919826 [src:linux] linux-image-4.19.0-1-arm64: Loading Linux 
4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic
Marked as found in versions linux/4.19.12-1.
> severity 919826 important
Bug #919826 [src:linux] linux-image-4.19.0-1-arm64: Loading Linux 
4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: tagging 919829

[Debian Bug Tracking System]

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

> tags 919829 + buster sid
Bug #919829 [src:libatteanx-store-sparql-perl] libatteanx-store-sparql-perl: 
FTBFS (failing tests)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#919829: libatteanx-store-sparql-perl: FTBFS (failing tests)

[Santiago Vila]

Package: src:libatteanx-store-sparql-perl
Version: 0.010-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
8 combinations of copyright and licensing found.
WARNING:New or changed notices discovered:

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
License: Artistic-1.0 and/or GPL-1

To fix the situation please do the following:

[... snipped ...]

t/triplestore.t .. 
# Subtest: testing with main
# Subtest: get_triples
ok 1
ok 2
1..2
ok 1 - get_triples
# Subtest: count_triples
ok 1 - unexpected IRI
ok 2 - expected subject
ok 3 - expected predicate
ok 4 - expected object
ok 5 - expected object (2)
ok 6 - expected subject/object
ok 7 - expected predicate with variable
ok 8 - expected object with variable
ok 9 - expected object (2) with variable
ok 10 - expected subject/object with variable
ok 11 - count_triples_estimate
1..11
ok 2 - count_triples
# Subtest: size
ok 1
ok 2
ok 3
ok 4
1..4
ok 3 - size
1..3
ok 1 - testing with main
1..1
ok

Test Summary Report
---
t/plan.t   (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=2, Tests=1,  7 wallclock secs ( 0.05 usr  0.01 sys +  5.78 cusr  0.51 
csys =  6.35 CPU)
Result: FAIL
Failed 1/2 test programs. 0/1 subtests failed.
make[1]: *** [Makefile:871: test_dynamic] Error 255
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libatteanx-store-sparql-perl.html

where you can get a full build log if you need it.

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

Thanks.

Bug#919827: asterisk-espeak: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM)

[Santiago Vila]

Package: src:asterisk-espeak
Version: 5.0~1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-arch
test -x debian/rules
dh_testroot
dh_prep 
dh_installdirs -A 
mkdir -p "."
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -Wall 
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT 
-D_GNU_SOURCE" CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>'
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pipe -fPIC -Wall -Wstrict-prototypes 
-Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE -g -O2 
-c -o app_espeak.o app_espeak.c
In file included from app_espeak.c:34:
/usr/include/asterisk.h:232:2: error: #error "Externally compiled modules must 
declare AST_MODULE_SELF_SYM."
 #error "Externally compiled modules must declare AST_MODULE_SELF_SYM."
  ^
In file included from app_espeak.c:43:
app_espeak.c: In function 'load_module':
app_espeak.c:414:9: error: 'AST_MODULE_SELF' undeclared (first use in this 
function); did you mean 'AST_MODULE_INFO'?
  return ast_register_application(app, espeak_exec, synopsis, descrip) ?
 ^~~~
app_espeak.c:414:9: note: each undeclared identifier is reported only once for 
each function it appears in
app_espeak.c:416:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
make[1]: *** [Makefile:36: app_espeak.o] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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

Thanks.

Bug#919828: asterisk-opus: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM)

[Santiago Vila]

Package: src:asterisk-opus
Version: 13.7+20171009-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-arch
test -x debian/rules
dh_testroot
dh_prep 
dh_installdirs -A 
mkdir -p "."
/usr/bin/make -C . CFLAGS="-g -O2 
-fdebug-prefix-map=/<>/asterisk-opus-13.7+20171009=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC" CXXFLAGS="-g 
-O2 -fdebug-prefix-map=/<>/asterisk-opus-13.7+20171009=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>/asterisk-opus-13.7+20171009'
gcc -o codecs/codec_opus_open_source.so  
-DAST_MODULE=\"codec_opus_open_source\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/asterisk-opus-13.7+20171009=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -g3 -O3 -lopus 
-shared -Wl,-z,relro codecs/codec_opus_open_source.c
In file included from codecs/codec_opus_open_source.c:39:
/usr/include/asterisk.h:232:2: error: #error "Externally compiled modules must 
declare AST_MODULE_SELF_SYM."
 #error "Externally compiled modules must declare AST_MODULE_SELF_SYM."
  ^
In file included from codecs/codec_opus_open_source.c:56:
codecs/codec_opus_open_source.c: In function 'load_module':
codecs/codec_opus_open_source.c:833:8: error: 'AST_MODULE_SELF' undeclared 
(first use in this function); did you mean 'AST_MODULE_INFO'?
  res = ast_register_translator();
^~~
codecs/codec_opus_open_source.c:833:8: note: each undeclared identifier is 
reported only once for each function it appears in
make[1]: *** [Makefile:50: codecs/codec_opus_open_source.so] Error 1
make[1]: Leaving directory '/<>/asterisk-opus-13.7+20171009'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

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

Thanks.

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

[tony mancill]

On Sat, Jan 19, 2019 at 04:51:02PM -0500, Abdelhakim Qbaich wrote:
> Hi,
> 
> I've attached a patch and made an upstream pull request.

Hello Abdelhakim Qbaich,

Thank you for the patch.  I have applied it and a few other misc
packaging changes and uploaded to the archive.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#919826: linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic

[Andy Simpkins]

Package: linux-image-4.19.0-1-arm64
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
upgrading kernel in Buster from 4.18.0-3-arm64 via apt-get dist-upgrade

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
root@sally:~# uname -a
Linux sally 4.18.0-3-arm64 #1 SMP Debian 4.18.20-2 (2018-11-23) aarch64 
GNU/Linux
root@sally:~# ## update apt/sources to point to a mirror (was DVD)
root@sally:~# apt-get update
Hit:1 http://ftp.uk.debian.org/debian buster InRelease
Hit:2 http://security.debian.org/debian-security buster/updates InRelease
Reading package lists... Done 
root@sally:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libhunspell-1.6-0 liblvm2app2.2 liblvm2cmd2.02 libpython3.6-minimal 
libpython3.6-stdlib python3.6 python3.6-minimal
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  apparmor firmware-linux-free irqbalance libaio1 libdns-export1104 
libhunspell-1.7-0 libisc-export1100 liblvm2cmd2.03 libnftables0 libnftnl11 
libnuma1
  libpython3.7-minimal libpython3.7-stdlib libuchardet0 
linux-image-4.19.0-1-arm64 nftables python3.7 python3.7-minimal
The following packages will be upgraded:
  adwaita-icon-theme apt apt-utils bash-completion bind9-host bsdutils dash 
dbus dbus-user-session dconf-gsettings-backend dconf-service dmeventd
  dmsetup e2fsprogs enchant fdisk file gcc-8-base gir1.2-atk-1.0 
gir1.2-freedesktop gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-gtk-3.0 
gir1.2-pango-1.0
  gir1.2-vte-2.91 glib-networking glib-networking-common 
glib-networking-services gpgv grep groff-base grub-common grub-efi-arm64 
grub-efi-arm64-bin
  grub-efi-arm64-signed grub2-common gtk-update-icon-cache gzip init 
init-system-helpers iproute2 iptables isc-dhcp-client isc-dhcp-common 
klibc-utils
  krb5-locales libapparmor1 libapt-inst2.0 libapt-pkg5.0 libatk1.0-0 
libatk1.0-data libbind9-161 libblkid1 libc-bin libc-l10n libc6 libcairo-gobject2
  libcairo2 libcap-ng0 libcom-err2 libcroco3 libcryptsetup12 libcups2 
libdbus-1-3 libdconf1 libdebconfclient0 libdevmapper-event1.02.1
  libdevmapper1.02.1 libdns1104 libedit2 libefiboot1 libefivar1 libelf1 
libenchant1c2a libext2fs2 libfdisk1 libfribidi0 libfstrm0 libfuse2 libgcc1
  libgcrypt20 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common 
libgirepository-1.0-1 libglib2.0-0 libglib2.0-data libgmp10 libgnutls30
  libgpg-error0 libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin 
libgtk-3-common libharfbuzz0b libhogweed4 libicu63 libip4tc0 libip6tc0 libiptc0
  libisc1100 libisccc161 libisccfg163 libjansson4 libjson-glib-1.0-0 
libjson-glib-1.0-common libk5crypto3 libklibc libkrb5-3 libkrb5support0
  libldap-2.4-2 libldap-common liblwres161 liblz4-1 libmagic-mgc libmagic1 
libmount1 libnettle6 libnghttp2-14 libpam-modules libpam-modules-bin
  libpam-runtime libpam-systemd libpam0g libpango-1.0-0 libpangocairo-1.0-0 
libpangoft2-1.0-0 libpangoxft-1.0-0 libperl5.28 libpixman-1-0 libpng16-16
  libproxy1v5 libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib 
librsvg2-2 librsvg2-common libsemanage-common libsemanage1 libsmartcols1
  libsoup-gnome2.4-1 libsoup2.4-1 libsqlite3-0 libss2 libstdc++6 libsystemd0 
libudev1 libuuid1 libvte-2.91-0 libvte-2.91-common libxcb-render0
  libxcb-shm0 libxcb1 libxml2 libxtables12 libzstd1 linux-image-arm64 locales 
lvm2 man-db mount openssh-client openssh-server openssh-sftp-server
  os-prober perl perl-base perl-modules-5.28 publicsuffix python3 
python3-chardet python3-debianbts python3-gi python3-gi-cairo python3-minimal
  python3-pkg-resources python3-pycurl python3-pysimplesoap python3-six 
python3.6 python3.6-minimal rsyslog sed systemd systemd-sysv sysvinit-utils tar
  task-english task-ssh-server tasksel tasksel-data telnet tzdata ucf udev 
util-linux util-linux-locales vim-common vim-tiny wget xdg-user-dirs xxd
203 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
Need to get 144 MB of archives.
After this operation, 260 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

--- 8< ---
  
Get:207 http://ftp.uk.debian.org/debian buster/main arm64 
linux-image-4.19.0-1-arm64 arm64 4.19.12-1 [39.7 MB]
   
Get:208 http://ftp.uk.debian.org/debian buster/main arm64 linux-image-arm64 
arm64 4.19+101 [7,952 B]  

--- 8< ---

Processing triggers for systemd (240-4) ...
Setting up grub-efi-arm64 (2.02+dfsg1-10) ...
Installing for arm64-efi platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.19.0-1-arm64
Found initrd 

Bug#910627: closed by Louis-Philippe Véronneau (Bug#910627: fixed in nostalgy 0.2.36-1.1)

[Daniel Reichelt]

On 19.01.19 22:06, Debian Bug Tracking System wrote:
> It has been closed by Louis-Philippe Véronneau .

Thanks, Louis-Philippe,
one less package I have to take care about in a private repository.
Great work. Thanks so much!!!

Best,
Daniel



signature.asc
Description: OpenPGP digital signature

Bug#825501: marked as done (CVE-2016-4434)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 23:35:47 +
with message-id 
and subject line Bug#825501: fixed in tika 1.18-1
has caused the Debian Bug report #825501,
regarding CVE-2016-4434
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.)


-- 
825501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tika
Severity: grave
Tags: security

Hi,
please see http://seclists.org/oss-sec/2016/q2/413  for details.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: tika
Source-Version: 1.18-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated tika package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Jan 2019 00:08:04 +0100
Source: tika
Binary: libtika-java
Architecture: source
Version: 1.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libtika-java - Apache Tika - content analysis toolkit
Closes: 825501 90
Changes:
 tika (1.18-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes CVE-2016-4434: XML External Entity vulnerability (Closes: #825501)
 - Fixes CVE-2018-1339: Infinite loop in the CHM parser (Closes: #90)
 - Refreshed the patches
 - Ignore the new dl, eval, langdetect and nlp modules
 - New dependencies on libcommons-exec-java, libjackson2-annotations-java,
   libjackson2-core-java, libjackson2-databind-java, libhttpmime-java,
   libjsoup-java, libuima-core-java, libandroid-json-org-java
   and libjson-simple-java
 - Depend on libpdfbox2-java instead of libpdfbox-java
 - Depend on librome-java (>= 1.6)
 - Depend on libapache-mime4j-java (>= 0.8.1)
 - Depend on libapache-poi-java (>= 3.17)
 - Ignore the new parsers with missing dependencies
   * Enabled the mp4 parser
   * Fixed the build failure with Java 11
Checksums-Sha1:
 575e3b998aa917b405dc0d860d9254055ed35a9b 2668 tika_1.18-1.dsc
 5e3296e786017f6c48e5b037119e67def2b7b108 2460536 tika_1.18.orig.tar.xz
 7fa2e01a7b678acd0028c6f39ca57fc6ac76366c 7320 tika_1.18-1.debian.tar.xz
 1921c9105f2727a8094a9d2d906b0334f3598307 16596 tika_1.18-1_source.buildinfo
Checksums-Sha256:
 64eaa3dedec4a74f16b9d4b753aff226f671fa3399817e137dceb74e1828b84b 2668 
tika_1.18-1.dsc
 b107c1519f69cc041185984a765cc210d84063a77376ff7d726b504284be24d7 2460536 
tika_1.18.orig.tar.xz
 ef44ba42e64edd844bc4c410039278a2e49e904026d979f23a07e9e9f0c5a676 7320 
tika_1.18-1.debian.tar.xz
 b4c7d09d00afdb25f263a7f9fa78e4a911d2009e4bd79a5f1bd033615ce81284 16596 
tika_1.18-1_source.buildinfo
Files:
 76ece2170ee72d09da4f0a28e64b7156 2668 java optional tika_1.18-1.dsc
 8a059ae0583ee590437b70cbddcb1473 2460536 java optional tika_1.18.orig.tar.xz
 36aadb1079dfa3e34c4bb767b39eed56 7320 java optional tika_1.18-1.debian.tar.xz
 3fd0aaefd99a576a824db645f2da4892 16596 java optional 
tika_1.18-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlxDrmESHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs2MYQAKv03Susi/IF0UkPZ6noCfvtzDewzewe
dNG7p6izgZd01FNPc+Tv4glLHbsN0LpU/OGVZgf4UJFld6pwmVPQr0msy171tjmr
A+UkQKeARq4zMPAAbs0tbtENEkTo2tNK6KfYil/Zu6fWkC4fy0aDgCwgubux0xoW
p1wrSxQ4IiSioNkI0abE/P5QguwSCiuX89rj0Y+VGcKuIrTm8tu2l33bvpgHDHXJ
m2iyB7EtvwlaEdSjkH8sPusAuutb/1d4gofCNwV5OoVsKBKv8RN73yxExeDf7K9e
mdFDMh1LnLx+7tCRwH1kEN1vwvKviuv60SLKcnfp9JyQ8g76fZn0WQCpo6HGMrij
lIgXvDE94O2+R09CqpJJVl7fe6GjVJo7DUnHOLnqHX7wx+qtuxoSGavQptSoOvGf
/6ITBu6TljTutEWNENcVYqZ1vEoDiODa2cmbYGkxHpjrLl1esnfQdrgGRh/1vKU1
20AvYyFwHDdfqC6T3Cg+cMLDZtnsAiyPkrkrjmCFbMF4u1LJYZ8Luon8uC+vm0Db
a03aSS5Y4FY7xDlNPa5iY9ZZWpiAuadezw11riUIqeXPIBur0xJQvLuW4/cWMGAt
mGRkHXeN44M1F+Qy4EPhX/t13GPkJ4tF4eiEoNWd0LTbrDPgBP6tXdRoOoY7xc4D
D1rUqW6jxCq8
=l2eo
-END PGP SIGNATURE End Message ---

Bug#825501: Bug #825501 in tika marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/tika/commit/da8f564f02250bc904da8c03c45d2fa4c8f9c147


The new release fixes CVE-2016-4434 (Closes: #825501)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/825501

Processed: Bug #825501 in tika marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #825501 [src:tika] CVE-2016-4434
Added tag(s) pending.

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

Bug#904657: voltron: fails to install with Python 3.7 (was: Re: update)

[Andreas Beckmann]

On 2019-01-19 21:55, Kienan Stewart wrote:
> I tested a proposed patch from the upstream github repository which allows 
> the package to build and run : https://github.com/snare/voltron/pull/243
> 
> I'm not sure if there are other side-effects to the patch, since the async 
> (now asynchronous) variable is not directly used but could be referred to 
> elsewhere.

voltron has no rdepends in the archive. So if that was the only "async"
in the package, this patch should be fine.


Andreas

PS: please try to use an informative subject, e.g. retain bug number and
bug title. Your subject and body did not provide any useful context for
a high volume bug reporter like me.  Even the content in my SPAM folder
usually has better subjects :-)

OTOH, if I had seen from the subject that this was one of these boring
python3.7 async bugs, I would not have looked in detail and replied at
all :-)

Bug#865955: marked as done (odin: FTBFS with dcmtk 3.6.1~20170228-2)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 22:49:46 +
with message-id 
and subject line Bug#865955: fixed in odin 2.0.3-1
has caused the Debian Bug report #865955,
regarding odin: FTBFS with dcmtk 3.6.1~20170228-2
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.)


-- 
865955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: odin
Version: 2.0.3-0.1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

The odin package FTBFS in unstable with the new dcmtk:

/usr/bin/make  check-TESTS
make[4]: Entering directory '/tmp/odin-2.0.3'
make[5]: Entering directory '/tmp/odin-2.0.3'
FAIL: cmdline-utils/odintestsuite

Testsuite summary for odin 2.0.3

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

See ./test-suite.log

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

And test-suite.log shows:

E: DcmDataDictionary: Cannot open file: /usr/share/libdcmtk8/dicom.dic
FileIO|ERROR: DicomFormat.DicomFormat::write : No data dictionary loaded, 
check environment variable DCMDICTPATH
UnitTest  |ERROR: FileIO dcm.check : simple autowrite failed
UnitTest  |ERROR: check_all : Test of FileIO dcm failed

Unfortunately, the path to the dictionary changes for each upstream ABI
change; where it was previously in /usr/share/libdcmtk8, it's now in
/usr/share/libdcmtk11.  

I've applied the attached patch to odin in Ubuntu, which, provided dcmtk
continues to follow the same convention for its dictionary paths, should be
future proof against further changes.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru odin-2.0.3/debian/rules odin-2.0.3/debian/rules
--- odin-2.0.3/debian/rules 2016-07-04 09:40:03.0 -0700
+++ odin-2.0.3/debian/rules 2017-06-25 19:27:02.0 -0700
@@ -3,6 +3,8 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
+DCMMAJOR := $(shell readlink -f /usr/lib/libdcmimgle.so | cut -f3 -d.)
+
 # one ring to rule them all ...
 %:
dh $@ --with autoreconf
@@ -28,7 +30,7 @@
 
 # there is also a 'test' target that doesn't do the right thing
 override_dh_auto_test:
-   DCMDICTPATH=/usr/share/libdcmtk8/dicom.dic $(MAKE) check
+   DCMDICTPATH=/usr/share/libdcmtk$(DCMMAJOR)/dicom.dic $(MAKE) check
 
 # shared libs in odin package a only for private use
 override_dh_makeshlibs:
--- End Message ---
--- Begin Message ---
Source: odin
Source-Version: 2.0.3-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated odin 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: Sat, 19 Jan 2019 18:18:18 +0100
Source: odin
Binary: odin mitools libodin-dev
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 libodin-dev - static libraries and header for ODIN sequences
 mitools- view, convert and perform basic maths with medical image datasets
 odin   - develop, simulate and run magnetic resonance sequences
Closes: 865955 909363
Changes:
 odin (2.0.3-1) unstable; urgency=medium
 .
   * Team upload.
   * debhelper 9
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target
   

Processed: Re: Bug#919806: sbcl: FTBFS randomly (failing tests)

[Debian Bug Tracking System]

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

> retitle 919806 sbcl: FTBFS randomly (failing tests)
Bug #919806 [src:sbcl] sbcl: FTBFS (failing tests)
Changed Bug title to 'sbcl: FTBFS randomly (failing tests)' from 'sbcl: FTBFS 
(failing tests)'.
> severity 919806 important
Bug #919806 [src:sbcl] sbcl: FTBFS randomly (failing tests)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#916977: snoopy w/ ld preload enabled breaks "apt upgrade" jessie-to-buster

[Marcos Fouces]

Hello,

I use testing and updated hundreds of package without any trouble.

Please, could you give an example of a package that fails to upgrade?

Greetings,

Marcos.

On 11/1/19 18:52, Adrian Bunk wrote:
> On Thu, Dec 20, 2018 at 05:26:25PM -0500, deb...@mailinator.com wrote:
>> Package: snoopy
>> Version: 2.4.6-4
>> Severity: critical
>> Justification: breaks unrelated software
>>
>> Dear Maintainer,
>>
>> With snoopy installed and enabled on jessie, apt upgrade to buster will 
>> break the upgrade process, as the snoopy library goes missing while the ld 
>> preload setting persists.  This causes every command invocation to trigger 
>> an error message concerning the missing library.  
>> ...
> Hw did you upgrade from jessie to buster?
>
> Skipping a release when upgrading is not supported,
> only jessie -> stretch -> buster is supported.
>
> cu
> Adrian
>

Bug#919806: sbcl: FTBFS randomly (failing tests)

[Santiago Vila]

retitle 919806 sbcl: FTBFS randomly (failing tests)
severity 919806 important
thanks

The build does not always fail.

Thanks.

Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

[Santiago Vila]

tags 919737 - unreproducible moreinfo
thanks

Based on the last message by Jonas, I'm removing those tags
which do not apply here.

Thanks.

Processed: Re: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

[Debian Bug Tracking System]

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

> tags 919737 - unreproducible moreinfo
Bug #919737 {Done: Jonas Smedegaard } [src:underscore] 
underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)
Removed tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#919823: harp: FTBFS in sid (ERROR: CODA library and/or header file not found)

[Santiago Vila]

Package: src:harp
Version: 1.5+data-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch  --with python3
   dh_update_autotools_config -a
   dh_autoreconf -a
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' 
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'

[... snipped ...]

checking for floor... yes
checking for pread... yes
checking for stat... yes
checking for memmove... yes
checking for bcopy... yes
checking for strerror... yes
checking for strdup... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for vsnprintf... yes
checking build IDL interface... no
checking build MATLAB interface... no
checking use HDF4... yes
checking for compress in -lz... yes
checking for jpeg_start_compress in -ljpeg... yes
checking for SZ_encoder_enabled in -lsz... yes
checking hdf.h usability... yes
checking hdf.h presence... yes
checking for hdf.h... yes
checking netcdf.h usability... yes
checking netcdf.h presence... yes
checking for netcdf.h... yes
checking mfhdf.h usability... yes
checking mfhdf.h presence... yes
checking for mfhdf.h... yes
checking for Hopen in -ldfalt... yes
checking for SDstart in -lmfhdfalt... yes
checking for HDF4 installation... yes
checking coda.h usability... yes
checking coda.h presence... yes
checking for coda.h... yes
checking for coda_init in -lcoda... no
checking for CODA installation... no
configure: error: 


ERROR: CODA library and/or header file not found.
Try setting the CODA_LIB and CODA_INCLUDE environment variables to the
location of your CODA library and include file.


make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>/harp-1.5+data'
make: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here with plain "dpkg-buildpackage":

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

where you can get a full build log if you need it.

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

Thanks.

Bug#919289: marked as done (kile: After upgrade, kile will not open until okular installed)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 22:20:19 +
with message-id 
and subject line Bug#919289: fixed in kile 4:2.9.92-2
has caused the Debian Bug report #919289,
regarding kile: After upgrade, kile will not open until okular installed
to be marked as done.

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

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


-- 
919289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kile
Version: 4:2.9.92-1
Severity: normal

Dear Maintainer,

After upgrading kile from 4:2.1.3-4+b1 to 4:2.9.92-1, kile would not
open, giving an error along the lines of missing libokular. Okular was
installed on my system, but was an older version. I suspect there is a
missing depends on libokular5core8, or something along these lines

Manually installing okular fixes the problem .

The installation steps were as follows :

Upgrading Kile:

Start-Date: 2019-01-14  15:09:15
Commandline: apt install kile
Requested-By: USER
Install: libx265-165:amd64 (2.9-3, automatic), libavformat58:amd64 (7:4.1-1, 
automatic), libkf5texteditor5:amd64 (5.51.0-3, automatic), 
libqt5texttospeech5:amd64 (5.11.3-2, automatic), libmbedtls12:amd64 (2.16.0-1, 
automatic), libcom-err2:amd64 (1.44.5-1, automatic), libcom-err2:i386 
(1.44.5-1, automatic), gnupg-utils:amd64 (2.2.12-1, automatic), 
ktexteditor-katepart:amd64 (5.51.0-3, automatic), gpg-wks-client:amd64 
(2.2.12-1, automatic), libkf5pty5:amd64 (5.51.0-1, automatic), libllvm7:amd64 
(1:7.0.1-4, automatic), gnupg-l10n:amd64 (2.2.12-1, automatic), 
libmbedcrypto3:amd64 (2.16.0-1, automatic), va-driver-all:amd64 (2.3.0-2, 
automatic), libswresample3:amd64 (7:4.1-1, automatic), libkf5kiogui5:amd64 
(5.51.0-1, automatic), gcc-8-base:i386 (8.2.0-14, automatic), 
libkf5kirigami2-5:amd64 (5.51.0-1, automatic), libqt5quicktemplates2-5:amd64 
(5.11.3+dfsg-2, automatic), gpg-wks-server:amd64 (2.2.12-1, automatic), 
gpg:amd64 (2.2.12-1, automatic), qml-module-qtquick-controls2:amd64 (5.11.3+
 dfsg-2, automatic), qml-module-qtqml-models2:amd64 (5.11.3-2, automatic), 
libkf5khtml-bin:amd64 (5.51.0-1, automatic), libkf5js5:amd64 (5.51.0-1, 
automatic), libvpx5:amd64 (1.7.0-3, automatic), libqt5quickcontrols2-5:amd64 
(5.11.3+dfsg-2, automatic), ktexteditor-data:amd64 (5.51.0-3, automatic), 
libaom0:amd64 (1.0.0-3, automatic), libkf5pty-data:amd64 (5.51.0-1, automatic), 
libkf5syntaxhighlighting5:amd64 (5.51.0-1, automatic), libva2:amd64 (2.3.0-2, 
automatic), libva2:i386 (2.3.0-2, automatic), libeditorconfig0:amd64 
(0.12.1-1.1, automatic), libx264-155:amd64 (2:0.155.2917+git0a84d98-2, 
automatic), libhttp-parser2.8:amd64 (2.8.1-1, automatic), 
qml-module-org-kde-newstuff:amd64 (5.51.0-1, automatic), libavcodec58:amd64 
(7:4.1-1, automatic), libmbedx509-0:amd64 (2.16.0-1, automatic), 
keditbookmarks:amd64 (17.08.3-2, automatic), libavutil56:amd64 (7:4.1-1, 
automatic), libwebpmux3:amd64 (0.6.1-2, automatic), 
qml-module-qtquick-templates2:amd64 (5.11.3+dfsg-2, automatic), libkf5newstuff
 core5:amd64 (5.51.0-1, automatic), libkf5khtml-data:amd64 (5.51.0-1, 
automatic), konsole-kpart:amd64 (4:18.04.0-1, automatic), libva-x11-2:amd64 
(2.3.0-2, automatic), libva-drm2:amd64 (2.3.0-2, automatic), 
libkf5texteditor-bin:amd64 (5.51.0-3, automatic), libkf5doctools5:amd64 
(5.51.0-1, automatic), i965-va-driver:amd64 (2.2.0+dfsg1-2, automatic), 
gpg-agent:amd64 (2.2.12-1, automatic), libgit2-27:amd64 (0.27.7+dfsg.1-0.1, 
automatic), libkf5syntaxhighlighting-data:amd64 (5.51.0-1, automatic), 
libbluray2:amd64 (1:1.0.2-3, automatic), gpgconf:amd64 (2.2.12-1, automatic), 
libkf5khtml5:amd64 (5.51.0-1, automatic), mesa-va-drivers:amd64 (18.2.8-2, 
automatic), libcodec2-0.8.1:amd64 (0.8.1-2, automatic), gpgsm:amd64 (2.2.12-1, 
automatic), qml-module-org-kde-kirigami2:amd64 (5.51.0-1, automatic)
Upgrade: libkf5kiowidgets5:amd64 (5.28.0-2, 5.51.0-1), libcomerr2:amd64 
(1.43.4-2, 1.44.5-1), libcomerr2:i386 (1.43.4-2, 1.44.5-1), libgpgmepp6:amd64 
(1.8.0-3+b2, 1.12.0-4), libkf5attica5:amd64 (5.28.0-1, 5.51.0-1), 
comerr-dev:amd64 (2.1-1.43.4-2, 2.1-1.44.5-1), libkf5xmlgui-bin:amd64 
(5.28.0-1, 5.51.0-1+b1), kinit:amd64 (5.28.0-1, 5.51.0-2), 
libkwalletbackend5-5:amd64 (5.28.0-3, 5.51.0-1), gnupg-agent:amd64 
(2.1.18-8~deb9u3, 2.2.12-1), libgnutls-openssl27:amd64 (3.5.8-5+deb9u4, 
3.6.5-2), libkf5kiofilewidgets5:amd64 (5.28.0-2, 5.51.0-1), gcc-8-base:amd64 
(8.2.0-13, 8.2.0-14), libkf5bookmarks-data:amd64 (5.28.0-1, 5.51.0-1), 
libkf5service-bin:amd64 (5.28.0-1, 5.51.0-1), libgpgme11:amd64 (1.8.0-3+b2, 
1.12.0-4), libopenmpt0:amd64 (0.2.7386~beta20.3-3+deb9u3, 0.4.1-1), 

Bug#919737: marked as done (underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option))

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 23:14:24 +0100
with message-id <154793606424.5603.7578120566150068...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#919737: underscore: FTBFS 
(ERROR: `underscore.min.map` is not a supported option)
has caused the Debian Bug report #919737,
regarding underscore: FTBFS (ERROR: `underscore.min.map` is not a supported 
option)
to be marked as done.

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

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


-- 
919737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:underscore
Version: 1.8.3~dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
9 combinations of copyright and licensing found.
WARNING:New or changed notices discovered:

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Copyright: NONE
Copyright: 2009-2015, Jeremy Ashkenas, DocumentCloud and Investigative
Files: docs/images/background.png
Copyright: 
…R…W…r…g…2…n…0f…X[E…p…O…8…y$)…F…d…X…1=…-…l-…r…n…
  …!…U…|…}…zQ…6'…N…Ij…dO…Q…C…WR…5…
  b,UE.…O…kz…~…1…kk…J….…;…%N…o…?~…"…[B…T…hd.
  e…"n|…|…4…/…9pwb…"…
  …w`…u…j…r…mt"…!…6(…v
License: UNKNOWN
 FIXME

Files: underscore.js
Copyright: 2009-2015, Jeremy Ashkenas, DocumentCloud and Investigative 
Reporters & Editors
License: UNKNOWN
 FIXME

Copyright: 2009-.
Files: docs/images/underscore.png
Copyright: …PA?2…J…P…{…   
…$…}c…6)…=…R<…,q……e…|…%z…J…1…Zf…1…G…D…
  …4…2…X=…J;U…Q…9…U6…K:…"-*…"…ch…

To fix the situation please do the following:
  1) Examine debian/copyright_* and referenced files
  2) Update debian/copyright as needed
  3) Replace debian/copyright_hints with debian/copyright_newhints
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
uglifyjs --source-map underscore.min.map -o underscore.min.js underscore.js
Supported options:
  content null
  filenamenull
  includeSources  false
  rootnull
  url null
ERROR: `underscore.min.map` is not a supported option
at DefaultsError.get (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :71:23)
at fatal (/usr/lib/nodejs/uglify-js/bin/uglifyjs:291:53)
at run (/usr/lib/nodejs/uglify-js/bin/uglifyjs:235:9)
at Object. (/usr/lib/nodejs/uglify-js/bin/uglifyjs:160:5)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
make: *** [debian/rules:35: underscore.min.js] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Version: 1.8.3~dfsg-2

Hi Kienan,

Quoting Kienan Stewart (2019-01-19 22:54:45)
> I tried building this package (underscore-1.8.3~dfsg) in a clean 
> buster chroot (with sbuild) and a clean unstable chroot (also with 
> sbuild), and it worked in both cases.

Great that you want to help chasing this bug.

Unfortunately (for your efforts, not for the package), I already fixed 
this issue, just made a typo in the changelog entry so this bugreport 
didn't get automatically closed.  Sorry!

...or at least that is my guess as to why you cannot reproduce, since 
you mention only the upstream part of the version number: If you tested 
against 1.8.3~dfsg-1 and could not 

Bug#910627: marked as done (xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 22:04:26 +
with message-id 
and subject line Bug#910627: fixed in nostalgy 0.2.36-1.1
has caused the Debian Bug report #910627,
regarding xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible 
with TB 60+
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.)


-- 
910627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-nostalgy
Version: 0.2.34-1
Severity: important

Hi,

please update to the latest version available at [1] so it can be used again
with the version of Thunderbird (60+) shipped in Stretch.

Thanks!
Daniel

[1] https://addons.thunderbird.net/en-US/thunderbird/addon/nostalgy/
--- End Message ---
--- Begin Message ---
Source: nostalgy
Source-Version: 0.2.36-1.1

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated nostalgy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 19 Jan 2019 14:09:34 -0500
Source: nostalgy
Binary: xul-ext-nostalgy
Architecture: source
Version: 0.2.36-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Louis-Philippe Véronneau 
Description:
 xul-ext-nostalgy - keyboard shortcut extension for Thunderbird
Closes: 910627
Changes:
 nostalgy (0.2.36-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release, fixing TB 60 support. (Closes: #910627)
   * Fix outdated VCS entries in debian/control
Checksums-Sha1:
 dfc66bfd09743f21a051350d8a9e7af94e4f8fbc 1629 nostalgy_0.2.36-1.1.dsc
 1328db6eb19119441d61f037699bb14cd3fef8b3 34514 nostalgy_0.2.36.orig.tar.gz
 79983d7a326633b8b6c1d8c8e720ea378a92916c 4008 nostalgy_0.2.36-1.1.debian.tar.xz
 250c3ad62d696c693179ad5ded4a41a39d672614 6749 
nostalgy_0.2.36-1.1_amd64.buildinfo
Checksums-Sha256:
 3e1de96e4e0548aaec61bcef8d65d4c488b20473ed3d529291f1a19a794659b3 1629 
nostalgy_0.2.36-1.1.dsc
 4aba1cf15272d083dcd09514a7040aa6490f344905d72908ff9cd983ad8e2c7a 34514 
nostalgy_0.2.36.orig.tar.gz
 6e58776d579558bd77457cdf2c9a060daec17348d94b8e3caaf83fd1daf89383 4008 
nostalgy_0.2.36-1.1.debian.tar.xz
 c3caeee5bfb14524bd8807db62e22db51fd1b998b7daefc99e4a6a12ec9ba28f 6749 
nostalgy_0.2.36-1.1_amd64.buildinfo
Files:
 e56a979f2cae9fb059df73de9b9d46b2 1629 mail optional nostalgy_0.2.36-1.1.dsc
 555cc9b66c4b534ba3d53258662cf618 34514 mail optional 
nostalgy_0.2.36.orig.tar.gz
 a02e5e6799f659b9d2369d7649671794 4008 mail optional 
nostalgy_0.2.36-1.1.debian.tar.xz
 d350846e18c99b7788a7bed6f942e1bb 6749 mail optional 
nostalgy_0.2.36-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlxDnFUACgkQPqHd3bJh
2XtBSAf/bXT6KzXAyLqFZnAsprdNLErDOWs1P75KkAAWtGxAAKbWe8o1Zutb4z83
43W/SElAWCtVDk6RGL+UEznk1Md4GtWs0V6YpUX2uOE8e3Gu7l/Jf8wqcD+w5S4F
tifTzYAzyR6EhuoxblHz0H9bVh2gQ2bNe56iIWQJTSstaNTe4QdNUZnz1EN0/RXQ
uOWikPvCXWKZeJKucUdg9NMCVyDQgnepfuAyAAEEszxx854//iYl7kBSox/1nDGO
Ft8kqBfVVozm6vQf+uU110PHtrqDIrAnK67C9n5oLyOGD823/zm+SlkHdvUPqaEt
49RXErLVdhIBQbSNDJDM8KYbUtZa6g==
=5kvF
-END PGP SIGNATURE End Message ---

Processed: tagging 919006

[Debian Bug Tracking System]

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

> # does not affect buster yet as libdbd-sqlite3-perl 1.62-1 is blocked from 
> migrating by #919773
> tags 919006 - buster
Bug #919006 [src:libclass-dbi-plugin-type-perl] FTBFS: test failure with new 
DBD::SQLite
Removed tag(s) buster.
> thanks
Stopping processing here.

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

Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

[Kienan Stewart]

user debian-rele...@lists.debian.org
usertag 919737 + bsp-2019-01-ca-montreal
tags 919737 + unreproducible moreinfo
thank you

Hi,

I tried building this package (underscore-1.8.3~dfsg) in a clean buster chroot 
(with sbuild) and a clean unstable chroot (also with sbuild), and it worked in 
both cases.

Thanks,
Kienan


signature.asc
Description: PGP signature

Processed: Re: jhove: FTBFS in buster at least since 2018-12-07

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #917482 [src:jhove] jhove: FTBFS in buster at least since 2018-12-07
Added tag(s) patch.

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

Bug#919822: gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import

[Salvatore Bonaccorso]

Source: gitlab
Version: 11.5.6+dfsg-1
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole

Hi,

The following vulnerability was published for gitlab, and fixed in
11.6.4, 11.5.7, and 11.4.14.

CVE-2019-6240[0]:
RESERVED

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-2019-6240
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6240
[1] 
https://about.gitlab.com/2019/01/16/critical-security-release-gitlab-11-dot-6-dot-4-released/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

[Abdelhakim Qbaich]

Control: tags -1 +patch

On Sat, 19 Jan 2019 16:51:02 -0500
Abdelhakim Qbaich  wrote:

> Hi,
> 
> I've attached a patch and made an upstream pull request.
> 
> On Thu, 27 Dec 2018 22:52:58 + Santiago Vila 
> wrote:
> > Package: src:jhove
> > Version: 1.20.1-4
> > Severity: serious
> > Tags: ftbfs
> > 
> > Dear maintainer:
> > 
> > I tried to build this package in buster but it failed:
> > 
> > 
> > [...]
> >  debian/rules build-indep
> > dh build-indep
> >dh_update_autotools_config -i
> >dh_autoreconf -i
> >dh_auto_configure -i
> > mh_patchpoms -pjhove --debian-build --keep-pom-version
> > --maven-repo=/<>/debian/maven-repo dh_auto_build -i
> > /usr/lib/jvm/default-java/bin/java -noverify
> > -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar
> > -Dmaven.home=/usr/share/maven
> > -Dmaven.multiModuleProjectDirectory=/<>
> > -Dclassworlds.conf=/etc/maven/m2-debian.conf
> > -Dproperties.file.manual=/<>/debian/maven.properties
> > org.codehaus.plexus.classworlds.launcher.Launcher
> > -s/etc/maven/settings-debian.xml
> > -Ddebian.dir=/<>/debian
> > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode
> > package -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An
> > illegal reflective access operation has occurred WARNING: Illegal
> > reflective access by
> > com.google.inject.internal.cglib.core.$ReflectUtils$1
> > (file:/usr/share/maven/lib/guice.jar) to method
> > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> > WARNING: Please consider reporting this to the maintainers of
> > com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use
> > --illegal-access=warn to enable warnings of further illegal
> > reflective access operations WARNING: All illegal access operations
> > will be denied in a future release [INFO] Scanning for projects...
> > 
> > [... snipped ...]
> > 
> > [INFO] JHOVE - JSTOR/Harvard Object Validation Environment  SUCCESS
> > [  0.009 s] [INFO] JHOVE
> > Core . SUCCESS [  4.465 s]
> > [INFO] JHOVE Validation Modules ... FAILURE
> > [  2.348 s] [INFO] JHOVE
> > Applications . SKIPPED [INFO]
> > 
> > [INFO] BUILD FAILURE [INFO]
> > 
> > [INFO] Total time:  7.061 s [INFO] Finished at: 2018-12-25T23:16:10Z
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> > (default-compile) on project jhove-modules: Compilation failure:
> > Compilation failure:
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[13,22]
> > package javax.xml.bind does not exist
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[13,22]
> > package javax.xml.bind does not exist
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[216,29]
> > cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> > [ERROR]   location: class
> > edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[219,29]
> > cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> > [ERROR]   location: class
> > edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[261,21]
> > cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> > [ERROR]   location: class
> > edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[265,21]
> > cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> > [ERROR]   location: class
> > edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[269,21]
> > cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> > [ERROR]   location: class
> > edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[273,21]
> > cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> > [ERROR]   location: class
> > edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> > [ERROR] 
> > /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[277,21]
> > cannot find symbol
> 

Processed: Re: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was kie...@koumbit.org).
> usertag 919737 + bsp-2019-01-ca-montreal
There were no usertags set.
Usertags are now: bsp-2019-01-ca-montreal.
> tags 919737 + unreproducible moreinfo
Bug #919737 [src:underscore] underscore: FTBFS (ERROR: `underscore.min.map` is 
not a supported option)
Added tag(s) moreinfo and unreproducible.
> thank you
Stopping processing here.

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

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

[Abdelhakim Qbaich]

Hi,

I've attached a patch and made an upstream pull request.

On Thu, 27 Dec 2018 22:52:58 + Santiago Vila 
wrote:
> Package: src:jhove
> Version: 1.20.1-4
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep
>dh_update_autotools_config -i
>dh_autoreconf -i
>dh_auto_configure -i
>   mh_patchpoms -pjhove --debian-build --keep-pom-version
> --maven-repo=/<>/debian/maven-repo dh_auto_build -i
>   /usr/lib/jvm/default-java/bin/java -noverify
> -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar
> -Dmaven.home=/usr/share/maven
> -Dmaven.multiModuleProjectDirectory=/<>
> -Dclassworlds.conf=/etc/maven/m2-debian.conf
> -Dproperties.file.manual=/<>/debian/maven.properties
> org.codehaus.plexus.classworlds.launcher.Launcher
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode
> package -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An
> illegal reflective access operation has occurred WARNING: Illegal
> reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> (file:/usr/share/maven/lib/guice.jar) to method
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of
> com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use
> --illegal-access=warn to enable warnings of further illegal
> reflective access operations WARNING: All illegal access operations
> will be denied in a future release [INFO] Scanning for projects...
> 
> [... snipped ...]
> 
> [INFO] JHOVE - JSTOR/Harvard Object Validation Environment  SUCCESS
> [  0.009 s] [INFO] JHOVE
> Core . SUCCESS [  4.465 s]
> [INFO] JHOVE Validation Modules ... FAILURE
> [  2.348 s] [INFO] JHOVE
> Applications . SKIPPED [INFO]
> 
> [INFO] BUILD FAILURE [INFO]
> 
> [INFO] Total time:  7.061 s [INFO] Finished at: 2018-12-25T23:16:10Z
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project jhove-modules: Compilation failure:
> Compilation failure:
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[13,22]
> package javax.xml.bind does not exist
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[13,22]
> package javax.xml.bind does not exist
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[216,29]
> cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> [ERROR]   location: class
> edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[219,29]
> cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> [ERROR]   location: class
> edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[261,21]
> cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> [ERROR]   location: class
> edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[265,21]
> cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> [ERROR]   location: class
> edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[269,21]
> cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> [ERROR]   location: class
> edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[273,21]
> cannot find symbol [ERROR]   symbol:   variable DatatypeConverter
> [ERROR]   location: class
> edu.harvard.hul.ois.jhove.module.wave.FormatChunk
> [ERROR] 
> /<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[277,21]
> cannot find symbol

-- 
Abdelhakim Qbaich


javax
Description: Binary data

Processed: mysql-connector-python: CVE-2019-2435

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.1.6-1
Bug #919820 [src:mysql-connector-python] mysql-connector-python: CVE-2019-2435
Marked as found in versions mysql-connector-python/2.1.6-1.

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

Bug#919820: mysql-connector-python: CVE-2019-2435

[Salvatore Bonaccorso]

Source: mysql-connector-python
Version: 8.0.11-1
Severity: grave
Tags: security upstream
Control: found -1 2.1.6-1

Hi,

The following vulnerability was published for mysql-connector-python.

CVE-2019-2435[0]:
| Vulnerability in the MySQL Connectors component of Oracle MySQL
| (subcomponent: Connector/Python). Supported versions that are affected
| are 8.0.13 and prior and 2.1.8 and prior. Easily exploitable
| vulnerability allows unauthenticated attacker with network access via
| TLS to compromise MySQL Connectors. Successful attacks require human
| interaction from a person other than the attacker. Successful attacks
| of this vulnerability can result in unauthorized creation, deletion or
| modification access to critical data or all MySQL Connectors
| accessible data as well as unauthorized access to critical data or
| complete access to all MySQL Connectors accessible data. CVSS 3.0 Base
| Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector:
| (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

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-2019-2435
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2435
[1] 
http://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#CVE-2019-2435

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#919529: CVE-2019-6256

[Salvatore Bonaccorso]

Hey!

On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote:
> Control: found -1 2016.11.28-1
> 
> On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote:
> > Source: liblivemedia
> > Severity: grave
> > Tags: security
> > 
> > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256
> > 
> > Cheers,
> > Moritz
> 
> Not sure if I'm missing something, but the PoC does not seem to work on
> buster/sid. On stretch I get segfaults, but only if I abort the PoC. So 
> marking
> as found in stable and closing for sid.

Not having a poc triggering does not necessarly mean the issue needs
to be fixed. Do we know something on the actual fix? Skimming (but
only superficial) in the git repository I have not found something
obvious, but possible I only missed it.

Regards,
Salvatore

Bug#887750: marked as done (pam-python FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 21:35:22 +
with message-id 
and subject line Bug#887750: fixed in pam-python 1.0.6-1.1
has caused the Debian Bug report #887750,
regarding pam-python FTBFS with glibc 2.26
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.)


-- 
887750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pam-python
Version: 1.0.6-1
Severity: serious
Tags: buster sid

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

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -Wall -Wextra -Wundef -Wshadow -Wpointer-arith 
-Wbad-function-cast -Wsign-compare -Waggregate-return -Wstrict-prototypes 
-Wmissing-prototypes -Wmissing-declarations -Werror -I/usr/local/lib/ 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DLIBPYTHON_SO="libpython2.7.so.1.0" 
-I/usr/include/python2.7 -c pam_python.c -o 
build/temp.linux-x86_64-2.7/pam_python.o
pam_python.c: In function 'call_handler':
pam_python.c:2229:19: error: argument 1 null where non-null expected 
[-Werror=nonnull]
   if (dot != 0 || strcmp(dot, ".py") == 0)
   ^~
In file included from /usr/include/security/_pam_macros.h:13:0,
 from pam_python.c:33:
/usr/include/string.h:136:12: note: in a call to function 'strcmp' declared here
 extern int strcmp (const char *__s1, const char *__s2)
^~
cc1: all warnings being treated as errors
--- End Message ---
--- Begin Message ---
Source: pam-python
Source-Version: 1.0.6-1.1

We believe that the bug you reported is fixed in the latest version of
pam-python, 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.
Antoine Beaupré  (supplier of updated pam-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 19 Jan 2019 15:14:26 -0500
Source: pam-python
Binary: libpam-python libpam-python-doc
Architecture: source
Version: 1.0.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Russell Stuart 
Changed-By: Antoine Beaupré 
Description:
 libpam-python - Enables PAM modules to be written in Python
 libpam-python-doc - Documentation for the bindings provided by libpam-python
Closes: 887750
Changes:
 pam-python (1.0.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build with glibc 2.26, thanks to Adrian Bunk (Closes: #887750).
   * Fix build with GCC 8
Checksums-Sha1:
 06ad5db56e4d2431fd8ffa127f416877a9a993a1 1570 pam-python_1.0.6-1.1.dsc
 a262835c2807bbb24ba69da56c4103db41c41b85 15864 
pam-python_1.0.6-1.1.debian.tar.xz
 16735c15cbd65b620abbd7eef3b6c695ae05a7a9 6672 
pam-python_1.0.6-1.1_source.buildinfo
Checksums-Sha256:
 b5761f9cf741d68b147edd41c26c4a4694a44e9ef7672647d5397b70115e922e 1570 
pam-python_1.0.6-1.1.dsc
 ecb115acf20f50c04e206342599035b113eec769af054684410f0ecba892fa17 15864 
pam-python_1.0.6-1.1.debian.tar.xz
 0f1835b5d568179c02db8792da6b40bbeecb48af02ad0d5cdc8743fe6ab9b953 6672 
pam-python_1.0.6-1.1_source.buildinfo
Files:
 f21ba2a20a500610152b61afe10d063e 1570 python extra pam-python_1.0.6-1.1.dsc
 2a1722cc7ae7d9d9347d1cc12b5132f3 15864 python extra 
pam-python_1.0.6-1.1.debian.tar.xz
 b81ac437e59ccdac77422fdc0b694cd0 6672 python extra 
pam-python_1.0.6-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlxDkwoACgkQPqHd3bJh
2XupFQgAmgYERnVirXaKKq4v3Vsf6d8lGoLqO+eWks+DOZzQzKBgTmngseAjKIIf
NRIpsbNTcF+m6SkN9iL8bPuZPegaHHRQGa2E98WXsx3SUAYE8q+6+oESQzJ2hzHo
SPLUD3UdRq9H6Rw/THK9lrFMGURXTKm2cLBtysUVUHYvXCZde5Ep0X5GaOaoLXig
KJ38zt5//sr/iGWb2sBRsB05QSV+LyZTLRFsk9md1VS3P9H5pKmDRISmvzyDULC2
DGLqbsQ0WxoevM2bdzttj672Kw3HKb724Vq7kRAatD+A515XRQhvVq2EnhRfGfCG
IOFCbdByu7156++ZEIp7fAa2bvzO9A==
=2kvt
-END PGP SIGNATURE End Message ---

Processed: tagging 919529, bug 919529 is forwarded to https://github.com/rgaufman/live555/issues/19

[Debian Bug Tracking System]

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

> tags 919529 + upstream
Bug #919529 {Done: Sebastian Ramacher } 
[src:liblivemedia] CVE-2019-6256
Added tag(s) upstream.
> forwarded 919529 https://github.com/rgaufman/live555/issues/19
Bug #919529 {Done: Sebastian Ramacher } 
[src:liblivemedia] CVE-2019-6256
Set Bug forwarded-to-address to 'https://github.com/rgaufman/live555/issues/19'.
> thanks
Stopping processing here.

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

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

[Louis-Philippe Véronneau]

Hello from the Montreal BSP!

I tested the latest release of the upstream version (0.2.36) and it
worked fine for me on the latest Thunderbird in testing.

I migrated the nostalgy VCS from the Alioth archive to Salsa and updated
it to the latest release: https://salsa.debian.org/webext-team/nostalgy

After testing it, everything seems to work for me. I asked
anar...@debian.org to upload it to the archive.

Cheers!

-- 
  ,''`.
 : :'  : Louis-Philippe Véronneau
 `. `'`  po...@debian.org / veronneau.org
   `-

On Tue, 09 Oct 2018 00:22:01 +0200 Daniel Reichelt
 wrote:
> Package: xul-ext-nostalgy
> Version: 0.2.34-1
> Severity: important
> 
> Hi,
> 
> please update to the latest version available at [1] so it can be used again
> with the version of Thunderbird (60+) shipped in Stretch.
> 
> Thanks!
> Daniel
> 
> [1] https://addons.thunderbird.net/en-US/thunderbird/addon/nostalgy/
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#887750: pam-python: diff for NMU version 1.0.6-1.1

[anarcat]

Dear maintainer,

I've prepared an NMU for pam-python (versioned as 1.0.6-1.1) and
uploaded it to DELAYED/0. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
diff -Nru pam-python-1.0.6/debian/changelog pam-python-1.0.6/debian/changelog
--- pam-python-1.0.6/debian/changelog	2016-08-27 07:37:03.0 -0400
+++ pam-python-1.0.6/debian/changelog	2019-01-19 15:14:26.0 -0500
@@ -1,3 +1,11 @@
+pam-python (1.0.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build with glibc 2.26, thanks to Adrian Bunk (Closes: #887750).
+  * Fix build with GCC 8
+
+ -- Antoine Beaupré   Sat, 19 Jan 2019 15:14:26 -0500
+
 pam-python (1.0.6-1) unstable; urgency=low
 
   * New upstream.
diff -Nru pam-python-1.0.6/debian/patches/fix-function-types.patch pam-python-1.0.6/debian/patches/fix-function-types.patch
--- pam-python-1.0.6/debian/patches/fix-function-types.patch	1969-12-31 19:00:00.0 -0500
+++ pam-python-1.0.6/debian/patches/fix-function-types.patch	2019-01-19 15:14:26.0 -0500
@@ -0,0 +1,96 @@
+From 12869142411f7a85d438971792cd75095f140f28 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
+Date: Sat, 19 Jan 2019 16:00:52 -0500
+Subject: [PATCH] fix build with -Wcast-function-type -Werror on gcc8
+
+New versions of gcc8 will fail to build from source on Python
+declarations because of the hairy cast we're doing there, example:
+
+pam_python.c:1355:19: error: cast between incompatible function types from 'PyObject * (*)(PyObject *, PyObject *, PyObject *)' {aka 'struct _object * (*)(struct _object *, struct _object *, struct _object *)'} to 'PyObject * (*)(PyObject *, PyObject *)' {aka 'struct _object * (*)(struct _object *, struct _object *)'} [-Werror=cast-function-type]
+
+This fix comes form the upstream cpython implementation:
+
+https://github.com/python/cpython/commit/62be74290aca26d16f3f55ece7ff6dad14e60e8d#diff-c3cf251f16d5a03a9e7d4639f2d6f998
+---
+ src/pam_python.c | 30 +++---
+ 1 file changed, 15 insertions(+), 15 deletions(-)
+
+diff --git a/src/pam_python.c b/src/pam_python.c
+index e01ee68..654f0aa 100644
+--- a/src/pam_python.c
 b/src/pam_python.c
+@@ -317,7 +317,7 @@ static PyMethodDef SyslogFile_Methods[] =
+ {
+   {
+ "write",
+-(PyCFunction)SyslogFile_write,
++(PyCFunction)(void(*)(void))SyslogFile_write,
+ METH_VARARGS|METH_KEYWORDS,
+ 0
+   },
+@@ -1349,16 +1349,16 @@ static PyObject* PamEnv_values(
+ 
+ static PyMethodDef PamEnv_Methods[] =
+ {
+-  {"__contains__",  (PyCFunction)PamEnv_has_key,METH_VARARGS|METH_KEYWORDS, 0},
+-  {"__getitem__",   (PyCFunction)PamEnv_getitem,METH_VARARGS|METH_KEYWORDS, 0},
+-  {"get",	(PyCFunction)PamEnv_get,	METH_VARARGS|METH_KEYWORDS, 0},
+-  {"has_key",	(PyCFunction)PamEnv_has_key,METH_VARARGS|METH_KEYWORDS, 0},
+-  {"items",	(PyCFunction)PamEnv_items,	METH_VARARGS|METH_KEYWORDS, 0},
+-  {"iteritems",	(PyCFunction)PamEnv_iteritems,METH_VARARGS|METH_KEYWORDS, 0},
+-  {"iterkeys",	(PyCFunction)PamEnv_iterkeys,METH_VARARGS|METH_KEYWORDS, 0},
+-  {"itervalues",(PyCFunction)PamEnv_itervalues,METH_VARARGS|METH_KEYWORDS, 0},
+-  {"keys",	(PyCFunction)PamEnv_keys,	METH_VARARGS|METH_KEYWORDS, 0},
+-  {"values",	(PyCFunction)PamEnv_values,	METH_VARARGS|METH_KEYWORDS, 0},
++  {"__contains__",  (PyCFunction)(void(*)(void))PamEnv_has_key,METH_VARARGS|METH_KEYWORDS, 0},
++  {"__getitem__",   (PyCFunction)(void(*)(void))PamEnv_getitem,METH_VARARGS|METH_KEYWORDS, 0},
++  {"get",	(PyCFunction)(void(*)(void))PamEnv_get,	METH_VARARGS|METH_KEYWORDS, 0},
++  {"has_key",	(PyCFunction)(void(*)(void))PamEnv_has_key,METH_VARARGS|METH_KEYWORDS, 0},
++  {"items",	(PyCFunction)(void(*)(void))PamEnv_items,	METH_VARARGS|METH_KEYWORDS, 0},
++  {"iteritems",	(PyCFunction)(void(*)(void))PamEnv_iteritems,METH_VARARGS|METH_KEYWORDS, 0},
++  {"iterkeys",	(PyCFunction)(void(*)(void))PamEnv_iterkeys,METH_VARARGS|METH_KEYWORDS, 0},
++  {"itervalues",(PyCFunction)(void(*)(void))PamEnv_itervalues,METH_VARARGS|METH_KEYWORDS, 0},
++  {"keys",	(PyCFunction)(void(*)(void))PamEnv_keys,	METH_VARARGS|METH_KEYWORDS, 0},
++  {"values",	(PyCFunction)(void(*)(void))PamEnv_values,	METH_VARARGS|METH_KEYWORDS, 0},
+   {0,0,0,0}	/* Sentinel */
+ };
+ 
+@@ -2029,7 +2029,7 @@ static PyMethodDef PamHandle_Methods[] =
+ {
+   {
+ "conversation",
+-(PyCFunction)PamHandle_conversation,
++(PyCFunction)(void(*)(void))PamHandle_conversation,
+ METH_VARARGS|METH_KEYWORDS,
+ MODULE_NAME "." PAMHANDLE_NAME "." "conversation(prompts)\n"
+ "  Ask the application to issue the prompts to the user and return the\n"
+@@ -2039,7 +2039,7 @@ static PyMethodDef PamHandle_Methods[] =
+   },
+   {
+ "fail_delay",
+-(PyCFunction)PamHandle_fail_delay,
++(PyCFunction)(void(*)(void))PamHandle_fail_delay,
+ METH_VARARGS|METH_KEYWORDS,
+ MODULE_NAME "." PAMHANDLE_NAME "." "fail_delay(micro_sec)\n"
+  

Bug#919817: mysql-5.7: Security fixes from the January 2019 CPU

[Salvatore Bonaccorso]

Source: mysql-5.7
Version: 5.7.24-3
Severity: grave
Tags: security upstream
Justification: user security hole

Hi

Details at
https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#AppendixMSQL

Regards,
Salvatore

Bug#904657: update

[Kienan Stewart]

user debian-rele...@lists.debian.org
usertags 904657 + bsp-2019-01-ca-montreal
tags 904657 + patch
thank you

Hi,

I tested a proposed patch from the upstream github repository which allows the 
package to build and run : https://github.com/snare/voltron/pull/243

I'm not sure if there are other side-effects to the patch, since the async (now 
asynchronous) variable is not directly used but could be referred to elsewhere.

Thanks,
Kienan

Processed: update

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was kie...@koumbit.org).
> usertags 904657 + bsp-2019-01-ca-montreal
There were no usertags set.
Usertags are now: bsp-2019-01-ca-montreal.
> tags 904657 + patch
Bug #904657 [voltron] voltron: fails to install with Python 3.7
Added tag(s) patch.
> thank you
Stopping processing here.

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

Bug#855958: marked as done (xserver-xorg-video-nv: FTBFS with current Xorg: nv_driver.c:1181:6: error: too many arguments to function 'pScreen->BlockHandler')

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 20:46:55 +
with message-id 
and subject line Bug#855958: fixed in xserver-xorg-video-nv 1:2.1.21-1
has caused the Debian Bug report #855958,
regarding xserver-xorg-video-nv: FTBFS with current Xorg: nv_driver.c:1181:6: 
error: too many arguments to function 'pScreen->BlockHandler'
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.)


-- 
855958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-nv
Version: 1:2.1.20-3
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hello,

xserver-xorg-video-nv is not installable in sid on any of the three
architectures where it is available. The reason is that it depends on
xorg-video-abi-18, which does not exist in sid.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: xserver-xorg-video-nv
Source-Version: 1:2.1.21-1

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

Debian distribution maintenance software
pp.
James Clarke  (supplier of updated xserver-xorg-video-nv 
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: Sat, 19 Jan 2019 20:07:06 +
Source: xserver-xorg-video-nv
Binary: xserver-xorg-video-nv
Architecture: source
Version: 1:2.1.21-1
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD Maintainers 
Changed-By: James Clarke 
Description:
 xserver-xorg-video-nv - X.Org X server -- NV display driver
Closes: 855958
Changes:
 xserver-xorg-video-nv (1:2.1.21-1) unstable; urgency=medium
 .
   * New upstream release.  (Closes: #855958)
   * debian/gbp.conf: Add basic config.
   * 00_git_update.diff: Drop (applied usptream)
   * Bump debhelper compat to 12 and modernise
   * Bump Standards-Version to 4.3.0; no changes needed
   * Update Vcs-* to point to Salsa
Checksums-Sha1:
 eb7775a5c3ec3158e722fb8bdf907648a4e0a8df 2268 
xserver-xorg-video-nv_2.1.21-1.dsc
 e355c6aff05b3f4b17c45e0871a5703b9f6ef281 517880 
xserver-xorg-video-nv_2.1.21.orig.tar.gz
 4736761ec3af0514036f60474c3ffde573a2b2bb 7198 
xserver-xorg-video-nv_2.1.21-1.diff.gz
 584492e0f313dd0e5bde8b2fc732a11b60942794 7518 
xserver-xorg-video-nv_2.1.21-1_kfreebsd-amd64.buildinfo
Checksums-Sha256:
 53189e95bb369f21b0a2e3e718af79485886d5b95bd522f3cfe3b2c2dcbe8b70 2268 
xserver-xorg-video-nv_2.1.21-1.dsc
 12d5a3d1e19e9c3197a9344fc1a62bc6693a81dd6f7d7756f5028ff28ba7f61b 517880 
xserver-xorg-video-nv_2.1.21.orig.tar.gz
 1cf55c8d1a3efed27c7b143b6c8c4bdbc28792029b663c609b0b66d88f9a6d2d 7198 
xserver-xorg-video-nv_2.1.21-1.diff.gz
 b1c93580aa087809df45a0459f62ae0bdc1d58f3ca74bf9848bbd82ec4b778aa 7518 
xserver-xorg-video-nv_2.1.21-1_kfreebsd-amd64.buildinfo
Files:
 28956f6c3d1f90bc72e5e14a10afaa0a 2268 non-free/x11 optional 
xserver-xorg-video-nv_2.1.21-1.dsc
 d2de3fc4990249bac07123ea3614b56e 517880 non-free/x11 optional 
xserver-xorg-video-nv_2.1.21.orig.tar.gz
 285a73b052e6f02f6ad85344819691dc 7198 non-free/x11 optional 
xserver-xorg-video-nv_2.1.21-1.diff.gz
 1a45762b93730ed248971cf59263ab78 7518 non-free/x11 optional 
xserver-xorg-video-nv_2.1.21-1_kfreebsd-amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEj1g0K+q+HvQ3lVH7sZN3DBhqHH0FAlxDhAASHGpydGMyN0Bk
ZWJpYW4ub3JnAAoJELGTdwwYahx9HDEP/3+Sp6UrG00A/jlH63aecjK59bKjPQKY
Bhh/wIFv65fSazwmZ1U5r2vWn/ow3uKjku+k9ui9gcikfbvQFXvHdgiluC+NCuwO
pleJMTWB06UijDNk+u6SfW2eF61/SkeKiZOx1wWjm9onKNcCqeNB6Wzs+n4aRsRm
qPYdw0QqKGEk+MkDvbIEQfYpb0m34Dacx5eqvQ4Ka5aDhk5L9ZVu72uTYvHvxCkH
xZiWzxH8iVUUmtuCsg2eCPx2rfcR7gbZyoscDZYURJvJ1+pgMr91uwznScuSYxlW
T+F6b2vjrvQv9cbVW7LKfvHsbA6JNI7OGBGHCD0LsTknkbWq7vwzMfr4k0S0uVxt
CrbXTJXX5Qtt6sG353BMbigr4Ra5GFZG2jSGfzGblI8fa+AsPEr0EPwz54akdFKS
fTIaAQ9GvNsnhmqtWpH1Lq7k+YC88Npy7kpiTKvUydiZAPgg8mqUznryT/GpZieA
o3IDvwLWTIxT0LT3DlTMoz7uSYAnrrBUdSshstjWS2hE95kqKzP3m5Gv6P9H/mIN
EHRcVQ0YuNWBFwxfdC2fM2nKjD8AdQH6XLnFzLxKVUIBxTYzhWxU74xpEGTnylfr
GbYJx5icYWrtfjlc4R2LxBCGqmcDoC0+1ZPcz28scqZlpAoanwEU67UBTvHQCv2A
Umrh971YGUK+
=TsIO
-END PGP SIGNATURE End Message ---

Processed: Pending

[Debian Bug Tracking System]

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

> tag 919289 pending
Bug #919289 [kile] kile: After upgrade, kile will not open until okular 
installed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: set patch tag

[Debian Bug Tracking System]

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

> tags 890689 + patch
Bug #890689 [src:ruby-rgen] ruby-rgen FTBFS with ruby 2.5
Added tag(s) patch.
> thank you
Stopping processing here.

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

Bug#919289: [Pkg-kde-extras] Bug#919289: kile: After upgrade, kile will not open until okular installed

[Lisandro Damián Nicanor Pérez Meyer]

I have checked the code and Kile is trying to open the plugin and not the 
library:

From src/kileviewmanager.cpp::1088

void Manager::createViewerPart(KActionCollection *actionCollection)
{
m_viewerPart = Q_NULLPTR;

KPluginLoader pluginLoader(OKULAR_LIBRARY_NAME);
KPluginFactory *factory = pluginLoader.factory();
if(!factory) {
KILE_DEBUG_MAIN << "Could not find the Okular library.";
m_viewerPart = Q_NULLPTR;
return;
}

The plugin is currently shipped in the okular package itself, so I'll go 
forward and make okular an strict dependency.

*Maybe* in the future we could look at splitting the plugin into it's own 
package, but I don't know if that's just too much. After all I guess most of 
the people using Kile are using okular too (the sole fact that this took so 
long to find points me to that).

Cheers, Lisandro.

-- 
4: Que es un icono
* Un caballono
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: not important

[Debian Bug Tracking System]

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

> owner 910627 po...@debian.org
Bug #910627 [xul-ext-nostalgy] xul-ext-nostalgy: Please update to upstream 
0.2.36 to be compatible with TB 60+
Owner recorded as po...@debian.org.
>
End of message, stopping processing here.

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

Processed: user debian-rele...@lists.debian.org, usertagging 887750, tagging 887750

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was anar...@debian.org).
> usertags 887750 + bsp-2019-01-ca-montreal
Usertags were: bsp-2019-01-ca-montreal.
Usertags are now: bsp-2019-01-ca-montreal.
> tags 887750 + pending
Bug #887750 [src:pam-python] pam-python FTBFS with glibc 2.26
Ignoring request to alter tags of bug #887750 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: user debian-rele...@lists.debian.org, usertagging 887750, tagging 887750

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was anar...@debian.org).
> usertags 887750 + bsp-2019-01-ca-montreal
There were no usertags set.
Usertags are now: bsp-2019-01-ca-montreal.
> tags 887750 + pending
Bug #887750 [src:pam-python] pam-python FTBFS with glibc 2.26
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#919773: libdbd-sqlite3-perl FTBFS on mips: test failure

[gregor herrmann]

On Sat, 19 Jan 2019 20:25:44 +0100, Xavier wrote:

> There is a difference earlier between mips and amd64: the first writes:
> 
>   # current DEFENSIVE value: 0
> 
> while the second has "1"

Hm, I don't see "1" in any logs on the buildds and also not in my
local amd64 build log.
 
> So it seems that these tests should be disabled for mips but it seems
> that SQLITE_DBCONFIG_DEFENSIVE is badly set to a true value.

I'm not sure ... The previous section ('# DEFENSIVE') which queries
SQLITE_DBCONFIG_DEFENSIVE and then turns it on and off, seems to work
fine. Just the last section ('# DEFENSIVE at connection'), where
sqlite_defensive is already set in connect_ok() fails.

Why this set-sqlite_defensive-at-connection-time only fails on mips
is the interesting question …


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Simon And Garfunkel: Sound Of Silence


signature.asc
Description: Digital Signature

Bug#919721: [Pkg-fonts-devel] Bug#919721: fonts-firacode: looks broken on at least kitty and hexchat

[Fabian Greffrath]

Control: severity -1 normal

Hi Antonio,

thanks for the report, but I fail to see how a change in vertical
spacing could justify grave severity for a font package.

 - Fabian



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

Processed: Re: [Pkg-fonts-devel] Bug#919721: fonts-firacode: looks broken on at least kitty and hexchat

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #919721 [fonts-firacode] fonts-firacode: looks broken on at least kitty and 
hexchat
Severity set to 'normal' from 'grave'

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

Bug#890689: ruby-rgen FTBFS with ruby 2.5

[Kienan Stewart]

Hi,

These errors happen in ruby >= 2.4 since Fixnum and Bignum were merged into 
Integer.

The following upstream commit fixes the issue: 
https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf

Attached is a patch to the debian source from 
https://salsa.debian.org/ruby-team/ruby-rgen which applies the above commit.

Thanks,
Kienan
diff --git a/debian/patches/fix-test-for-ruby-2.4 b/debian/patches/fix-test-for-ruby-2.4
new file mode 100644
index 000..bb94b79
--- /dev/null
+++ b/debian/patches/fix-test-for-ruby-2.4
@@ -0,0 +1,52 @@
+Description: Fix tests for ruby 2.4
+ This applies commit 1124f4303db52973967e78d93512a1c1b64f23cf which
+ lets the tests pass. In ruby 2.4 Fixnum and Bignum were merged into
+ Integer
+ .
+ ruby-rgen (0.8.0-1) unstable; urgency=medium
+ .
+   [ Cédric Boutillier ]
+   * Bump debhelper compatibility level to 9
+   * Remove version in the gem2deb build-dependency
+   * Use https:// in Vcs-* fields
+   * Bump Standards-Version to 3.9.7 (no changes needed)
+   * Run wrap-and-sort on packaging files
+ .
+   [ Stig Sandbeck Mathisen ]
+   * Declare compliance with Debian policy 3.9.8
+   * Imported upstream release 0.8.0
+Author: Stig Sandbeck Mathisen 
+
+Origin: https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf
+Bug-Debian: https://bugs.debian.org/890689
+Last-Update: 2019-01-19
+
+--- ruby-rgen-0.8.0.orig/test/metamodel_builder_test.rb
 ruby-rgen-0.8.0/test/metamodel_builder_test.rb
+@@ -186,7 +186,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise StandardError do
+   sc.name = 5
+ end
+-assert_match /In (\w+::)+SimpleClass : Can not use a Fixnum where a String is expected/, err.message
++assert_match /In (\w+::)+SimpleClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
+ assert_equal "EString", mm::SimpleClass.ecore.eAttributes.find{|a| a.name=="name"}.eType.name
+ 
+ assert_equal "xtest", sc.stringWithDefault
+@@ -288,7 +288,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise(StandardError) do
+   o.addLiterals(1)
+ end
+-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a String is expected/, err.message
++assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
+ 
+ assert_equal [], o.literals
+ o.addLiterals("a")
+@@ -323,7 +323,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise(StandardError) do
+   o.literals = 1
+ end
+-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a Enumerable is expected/, err.message
++assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a Enumerable is expected/, err.message
+  
+ o.bools = [true, false, true, false]
+ assert_equal [true, false, true, false], o.bools
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..ae45377
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+fix-test-for-ruby-2.4
diff --git a/test/metamodel_builder_test.rb b/test/metamodel_builder_test.rb
index 4567a86..2ce7d2f 100644
--- a/test/metamodel_builder_test.rb
+++ b/test/metamodel_builder_test.rb
@@ -186,7 +186,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
 err = assert_raise StandardError do
   sc.name = 5
 end
-assert_match /In (\w+::)+SimpleClass : Can not use a Fixnum where a String is expected/, err.message
+assert_match /In (\w+::)+SimpleClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
 assert_equal "EString", mm::SimpleClass.ecore.eAttributes.find{|a| a.name=="name"}.eType.name
 
 assert_equal "xtest", sc.stringWithDefault
@@ -288,7 +288,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
 err = assert_raise(StandardError) do
   o.addLiterals(1)
 end
-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a String is expected/, err.message
+assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
 
 assert_equal [], o.literals
 o.addLiterals("a")
@@ -323,7 +323,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
 err = assert_raise(StandardError) do
   o.literals = 1
 end
-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a Enumerable is expected/, err.message
+assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a Enumerable is expected/, err.message
  
 o.bools = [true, false, true, false]
 assert_equal [true, false, true, false], o.bools

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Dmitry Bogatov]

[2019-01-16 14:49] Dmitry Bogatov 
> So, should I propose you patch (in 7 days), that merges
> bin:git-daemon-run into bin:git-daemon, would you be able to review
> and apply/upload it before hard freeze?

Probably, even better would be to merge `git-daemon-run' and
`git-daemon-sysvinit'. What do you think?

Bug#919804: marked as done (ndcube: FTBFS (No module named 'sphinx_astropy'))

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 19:34:07 +
with message-id 
and subject line Bug#919804: fixed in astropy-helpers 3.1-2
has caused the Debian Bug report #919804,
regarding ndcube: FTBFS (No module named 'sphinx_astropy')
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.)


-- 
919804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ndcube
Version: 1.0.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7_ndcube/build/ndcube
copying ndcube/_sunpy_init.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube
copying ndcube/__init__.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube
copying ndcube/ndcube_sequence.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube
copying ndcube/ndcube.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube
copying ndcube/version.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube
creating 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/visualization
copying ndcube/visualization/__init__.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/visualization
copying ndcube/visualization/animation.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/visualization
creating /<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils
copying ndcube/utils/wcs.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils
copying ndcube/utils/__init__.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils
copying ndcube/utils/cube.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils
copying ndcube/utils/sequence.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils
creating /<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/test_ndcubesequence.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/test_utils_cube.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/test_utils_wcs.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/setup_package.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/test_utils_sequence.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/helpers.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
copying ndcube/tests/test_ndcube.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
creating /<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/mixins
copying ndcube/mixins/plotting.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/mixins
copying ndcube/mixins/__init__.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/mixins
copying ndcube/mixins/ndslicing.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/mixins
creating /<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils/tests
copying ndcube/utils/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/utils/tests
creating /<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/data
copying ndcube/data/README.rst -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/data
copying ndcube/tests/coveragerc -> 
/<>/.pybuild/cpython3_3.7_ndcube/build/ndcube/tests
PYTHONPATH=. sphinx-build -D html_last_updated_fmt="November 19, 2018" -D 
html_show_copyright=0 -N -bhtml docs/ build/html # HTML generator
Running Sphinx v1.7.9

Configuration error:
There is a programable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
  File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in 
execfile_
exec_(code, _globals)
  File "conf.py", line 42, in 
from astropy_helpers.sphinx.conf import *
  File "/usr/lib/python3/dist-packages/astropy_helpers/sphinx/conf.py", line 3, 
in 
from sphinx_astropy.conf import *
ModuleNotFoundError: No module named 'sphinx_astropy'

make[1]: *** 

Bug#919217: marked as done (Missing dependency on devscripts)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 19:35:04 +
with message-id 
and subject line Bug#919217: fixed in lintian-brush 0.11
has caused the Debian Bug report #919217,
regarding Missing dependency on devscripts
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.)


-- 
919217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian-brush
Version: 0.10
Severity: serious

Lintian-brush must depend on devscripts because it calls dch to update
the changelog.

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 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)
--- End Message ---
--- Begin Message ---
Source: lintian-brush
Source-Version: 0.11

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated lintian-brush 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: Sat, 19 Jan 2019 19:11:40 +
Source: lintian-brush
Binary: lintian-brush
Architecture: source
Version: 0.11
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Description:
 lintian-brush - automatically fix lintian problems
Closes: 919217
Changes:
 lintian-brush (0.11) unstable; urgency=medium
 .
   [ Jeroen Dekkers ]
   * Add dependency on devscripts. Closes: #919217
Checksums-Sha1:
 4f6292f52a8baf8046b50670a3569ca094780a02 1805 lintian-brush_0.11.dsc
 2d06c140b880a617517f63b1bb7ebfa9fd8f 626892 lintian-brush_0.11.tar.xz
 c99445c21f8bddbfd17cac88ae93cdca96e5a266 6601 
lintian-brush_0.11_amd64.buildinfo
Checksums-Sha256:
 86cfe479af09614076db70f578337d5b6f12e8d4e2b74959372d887a1868b629 1805 
lintian-brush_0.11.dsc
 c8af5ff537dcebb1e26cbe120645236441f285ccba1f81835506c0abb82d7375 626892 
lintian-brush_0.11.tar.xz
 8f61430e52c88faa380fce3312c8993db95312666edd30764617aa6e5631de8d 6601 
lintian-brush_0.11_amd64.buildinfo
Files:
 b344428d2e987535bdf10d07c00657b7 1805 devel optional lintian-brush_0.11.dsc
 a1c36edeeb19865fbe1c1a509313f943 626892 devel optional 
lintian-brush_0.11.tar.xz
 340eafdf3f322ce502614f3218e36c4c 6601 devel optional 
lintian-brush_0.11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAlxDdqIACgkQV5wWDUye
I+i51w//fVZYRD8KSLASQAWOHEA6zbA90NhFWXsmmAREth5XDTOqjZMJNuUGcEYa
EQt+nNVGf5fou3Hxku6p9bIvfc393lCHqke2d41kAYrZ+F0cnSBk3XLktnA/GLyh
+IdtElx0St84+IQop1wWb1XXSn6SzqScgEh5w8aFUamiS1NKNDIOlYcv2B/0ZSt5
snTwPIDoJGzACVWo4zRCluE0jWy6nT7nAuBzPBSUBlQ7gvIUF8BWebCdFm03HbIF
bzB8Wb96GGfqJT2b++iqhN6Rl+b23RIivj/SVG1Fi/FL509KyrxW0+wj0SPGVY1t
TICODFeyvy8s5WCbwrqkjk7enVFqKnLKHH93iVmsGqAIXj9nR8WnPAC3qNaIqJVc
SpoysGJiWxM00JkkXLGCkN7PPB6HRaUIhbjhMr9aJ3FooZ1t7vbgG8mWH/qJQ/8R
kuMZn3ub6MLSZ/p0F89N3WyDwJvOMu6mlf7GihtefL7AvRaDTBvXQ5lHNNH3yX6w
xLtLVV8jc2MlvghFnZ0hvfdA7yvYl29cdj88slYNXKmZrUht7EzaCj7IOALvHQSd
ZK4HbiCgw6YBNrN0AxZxeVR1y+arJmoiBJALcOEYZi6qGbvUo6Di/8yKOHobebVK
fMWBiM4wounaid7jLAYZTYY6oj1Smz8MP9aifVdNovbWgOVrtvE=
=xU1g
-END PGP SIGNATURE End Message ---

Bug#919773: libdbd-sqlite3-perl FTBFS on mips: test failure

[Xavier]

Le 19/01/2019 à 20:16, gregor herrmann a écrit :
> On Sat, 19 Jan 2019 15:03:24 +0100, Xavier wrote:
> 
>>> https://buildd.debian.org/status/fetch.php?pkg=libdbd-sqlite3-perl=mips=1.62-1=1546291045=0
>>>
>>> ...
>>> t/65_db_config.t .. 
>>> 1..79
> ...
>>> ok 76 - sql not found
>>> Failed 3/79 subtests
>>> ...
>>> Test Summary Report
>>> ---
>>> t/65_db_config.t(Wstat: 11 Tests: 76 
>>> Failed: 0)
>>>   Non-zero wait status: 11
>>>   Parse errors: Bad plan.  You planned 79 tests but ran 76.
>>> Files=111, Tests=3794, 61 wallclock secs ( 2.80 usr  0.48 sys + 48.42 cusr  
>>> 4.10 csys = 55.80 CPU)
>>> Result: FAIL
>>
>> I think the failure is here. I'm testing
>>
>> diff --git a/t/65_db_config.t b/t/65_db_config.t
>> index 6820736..1e336cf 100644
>> --- a/t/65_db_config.t
>> +++ b/t/65_db_config.t
>> @@ -211,7 +211,7 @@ for my $func (@CALL_FUNCS) {
>>
>>  # DEFENSIVE at connection
>>  SKIP: {
>> -skip 'DEFENSIVE is not supported', 8 if !SQLITE_DBCONFIG_DEFENSIVE;
>> +skip 'DEFENSIVE is not supported', 3 if !SQLITE_DBCONFIG_DEFENSIVE;
>>  my $dbh = connect_ok(RaiseError => 1, PrintError => 0,
>> sqlite_defensive => 1);
>>
>>  my $sql = 'CREATE TABLE foo (id, text)';
> 
> While the '8' here is obviously wrong, I think this fix is not
> enough. For starters, I don't see anything about "skipped DEFENSIVE is not
> supported" in the log.
> 
> I've now tried on minkus (the mips porterbox) and I get the same test
> failure as on the buildd, with or without the patch. The last test
> block is not skipped, it looks (with some diag() sprinkled it) like
> it just fails quietly in the first statement ('my $dbh =
> connect_ok(...)') and never reaches the 3 tests.
> 
> So with the following code:
> 
> #v+
> # DEFENSIVE at connection
> SKIP: {
> skip 'DEFENSIVE is not supported', 3 if !SQLITE_DBCONFIG_DEFENSIVE;
> diag "We don't skip this section";
> my $dbh = connect_ok(RaiseError => 1, PrintError => 0, sqlite_defensive 
> => 1);
> diag "We have dbh";
> 
> my $sql = 'CREATE TABLE foo (id, text)';
> $dbh->do($sql);
> diag "do sql done";
> $dbh->do('PRAGMA writable_schema=ON');
> diag "do pragma done";
> eval { $dbh->do('UPDATE sqlite_master SET name = ? WHERE name = ?', 
> undef, 'bar', 'foo'); };
> diag "evald";
> ok $@, "updating sqlite_master is prohibited";
> like $@ => qr/table sqlite_master may not be modified/;
> } 
> 
> #v-
> 
> I get
> 
> $ prove --blib --verbose t/65_db_config.t
> t/65_db_config.t .. 
> 1..79
> ...
> ok 76 - sql not found
> # We don't skip this section
> Failed 3/79 subtests 
> 
> Test Summary Report
> ---
> t/65_db_config.t (Wstat: 11 Tests: 76 Failed: 0)
>   Non-zero wait status: 11
>   Parse errors: Bad plan.  You planned 79 tests but ran 76.
> Files=1, Tests=76,  1 wallclock secs ( 0.20 usr  0.04 sys +  0.70 cusr  0.18 
> csys =  1.12 CPU)
> Result: FAIL

There is a difference earlier between mips and amd64: the first writes:

  # current DEFENSIVE value: 0

while the second has "1"

So it seems that these tests should be disabled for mips but it seems
that SQLITE_DBCONFIG_DEFENSIVE is badly set to a true value.

Processed: Re: sphinxbase: build appears broken for multiple python3 versions

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch - moreinfo
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Added tag(s) patch.
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Removed tag(s) moreinfo.

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

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Control: tags -1 + patch - moreinfo

Hello,

anarcat, le sam. 19 janv. 2019 12:42:44 -0500, a ecrit:
> On Thu, Jan 03, 2019 at 10:16:13AM +0100, Samuel Thibault wrote:
> > Oops, this bug was erroneously closed because its mention was remaining
> > in the sphinxbase changelog.
>
> So after reviewing this bug during the montreal BSP, I'm a little
> confused - it shows up in the "sponsor" UDD dashboard because it's
> marked as affecting buster and sid but with a patch.
>
> Yet, I don't see a recent patch that will fix the issue in dh-python.
> I'm not even sure there *is* an issue in dh-python at all anymore...
>
> Could someone summarize the current state of this bug report?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903698#140 , attached
here, contains the proper information and patch.

Basically, the issue is that dh_python3's handling depends on the
order in which the installed files are processed in the for i in
os.listdir(srcdir): loop. When the target of a symlink is processed
before the symlink, the symlink is considered as non-existing,
because exists(fpath1) returns False in that case. Changing that into
lexists(fpath1), which does return True in that case, fixes things, and
I believe that's should just be done.

Samuel
--- Begin Message ---
Control: reassign -1 dh-python
Control: tags -1 + patch

Samuel Thibault, le mar. 16 oct. 2018 22:13:59 +0200, a ecrit:
> Samuel Thibault, le mar. 16 oct. 2018 03:04:16 +0200, a ecrit:
> > This is driving me crazy :)
> > 
> > I have uploaded the VM images on
> > https://people.debian.org/~sthibault/tmp/fails.img.gz
> > https://people.debian.org/~sthibault/tmp/works.img.gz
> > 
> > Booting one or the other does not matter. What does matter is the
> > disk image used to store the chroot. Each VM image has its own
> > /var/cache/pbuilder/sphinxbase-build directory (almost exactly the
> > same), and it does not matter which of the two I copy, if I copy it
> > inside the fails.img disk I'm getting the lintian issue, and if it's
> > inside the works.img disk I'm not getting it (there's a fresh checkout
> > of sphinbase in /tmp/sphinxbase inside the chroots). And of course my
> > own main system is in the fails case, thus preventing me from building
> > the package :) tune2fsk does not show any difference between the two
> > filesystem options, just creation time, mount count & such.
> > 
> > Any other idea of what could be different between the two filesystems?
> 
> It could very well be e.g. the resulting inode numbers and such, thus my
> hypothesis at the top of the quotes above. Python people can have a look
> at the fails.img.gz image, where the issue is notably reproducible from
> the chroot in /var/cache/pbuilder/sphinxbase-build , building for
> instance in /tmp/sphinxbase.

I overrided dh_python3 into /bin/false to catch the result just before
running dh_python3, the two build trees are similar except the .pyc
timestamps which are a few seconds apart in the 2.7 and 3.6 trees.

I then tried to pass -v to dh_python3, and got differing results,
as attached.  It seems in the failure case it indeed doesn't do
everything for 3.6: there are 4 lines less which rename the .so to a 36
variant.  I looked deeper in fs.py, and I found that in the succeeding
case, the main loop inside share_files sees _sphinbase.so before
_sphinxbase.so.0.0.0, and thus renames it, and in the failing case, that
loop sees _sphinxbase.so.0.0.0 before _sphinxbase.so.0, and when it
looks at _sphinxbase.so.0, exits() fails, because the target was moved,
and thus the symlink is now broken. I changed that exists() call into
lexists() to allow for broken symlinks, as the attached patch does, and
things got fixed. This seems like a logical thing to do, and possibly
needed in a few other places in fs.py

Samuel
D: dh_python3 dh_python3:161: version: 3.20180927
D: dh_python3 dh_python3:162: argv: ['/usr/bin/dh_python3', '-v']
D: dh_python3 dh_python3:163: options: {'guess_deps': True, 'skip_private': 
False, 'verbose': True, 'arch': None, 'package': None, 'no_package': None, 
'compile_all': False, 'vrange': None, 'regexpr': None, 
'accept_upstream_versions': False, 'depends': None, 'depends_section': None, 
'recommends': None, 'recommends_section': None, 'suggests': None, 
'suggests_section': None, 'requires': None, 'shebang': None, 'ignore_shebangs': 
False, 'clean_dbg_pkg': True, 'no_ext_rename': False, 'no_shebang_rewrite': 
False, 'O': None}
D: dh_python3 dh_python3:164: args: []
D: dh_python3 dh_python3:166: supported Python versions: 3.6,3.7 (default=3.6)
D: dh_python3 debhelper:100: skipping package libsphinxbase-doc (missing 
${python3:Depends} in Depends)
D: dh_python3 debhelper:100: skipping package libsphinxbase-dev (missing 
${python3:Depends} in Depends)
D: dh_python3 debhelper:100: skipping package sphinxbase-utils (missing 
${python3:Depends} in Depends)
D: dh_python3 debhelper:100: skipping package libsphinxbase3 (missing 
${python3:Depends} in Depends)
D: dh_python3 

Bug#919617: python-gpiozero file conflict with python3-gpiozero

[Ben Nuttall]

On Fri, 18 Jan 2019 01:42:55 + Peter Green 
wrote:
> Package: python-gpiozero
> Version: 1.4.1-1
> Severity: serious
>
> The 1.4.1-1 upload of gpiozero added the "pinout" utility, unfortunately
it added it to both the python-gpiozero and python3-gpiozero packages. The
result is a file conflict between the two packages.

Agreed

>
> I see two possible solutions.
>
> 1. Drop the utility from one of the packages, if going down this road I
would probablly drop it from the python-gpiozero package since python 2 is
deprecated.
> 2. Install the utility with a different name or path in each package and
then use the alternatives mechanism to select between them.

We do 1) in RPF Raspbian. I think this is the correct approach.

Bug#919773: libdbd-sqlite3-perl FTBFS on mips: test failure

[gregor herrmann]

On Sat, 19 Jan 2019 15:03:24 +0100, Xavier wrote:

> > https://buildd.debian.org/status/fetch.php?pkg=libdbd-sqlite3-perl=mips=1.62-1=1546291045=0
> > 
> > ...
> > t/65_db_config.t .. 
> > 1..79
...
> > ok 76 - sql not found
> > Failed 3/79 subtests
> > ...
> > Test Summary Report
> > ---
> > t/65_db_config.t(Wstat: 11 Tests: 76 
> > Failed: 0)
> >   Non-zero wait status: 11
> >   Parse errors: Bad plan.  You planned 79 tests but ran 76.
> > Files=111, Tests=3794, 61 wallclock secs ( 2.80 usr  0.48 sys + 48.42 cusr  
> > 4.10 csys = 55.80 CPU)
> > Result: FAIL
> 
> I think the failure is here. I'm testing
> 
> diff --git a/t/65_db_config.t b/t/65_db_config.t
> index 6820736..1e336cf 100644
> --- a/t/65_db_config.t
> +++ b/t/65_db_config.t
> @@ -211,7 +211,7 @@ for my $func (@CALL_FUNCS) {
> 
>  # DEFENSIVE at connection
>  SKIP: {
> -skip 'DEFENSIVE is not supported', 8 if !SQLITE_DBCONFIG_DEFENSIVE;
> +skip 'DEFENSIVE is not supported', 3 if !SQLITE_DBCONFIG_DEFENSIVE;
>  my $dbh = connect_ok(RaiseError => 1, PrintError => 0,
> sqlite_defensive => 1);
> 
>  my $sql = 'CREATE TABLE foo (id, text)';

While the '8' here is obviously wrong, I think this fix is not
enough. For starters, I don't see anything about "skipped DEFENSIVE is not
supported" in the log.

I've now tried on minkus (the mips porterbox) and I get the same test
failure as on the buildd, with or without the patch. The last test
block is not skipped, it looks (with some diag() sprinkled it) like
it just fails quietly in the first statement ('my $dbh =
connect_ok(...)') and never reaches the 3 tests.

So with the following code:

#v+
# DEFENSIVE at connection
SKIP: {
skip 'DEFENSIVE is not supported', 3 if !SQLITE_DBCONFIG_DEFENSIVE;
diag "We don't skip this section";
my $dbh = connect_ok(RaiseError => 1, PrintError => 0, sqlite_defensive => 
1);
diag "We have dbh";

my $sql = 'CREATE TABLE foo (id, text)';
$dbh->do($sql);
diag "do sql done";
$dbh->do('PRAGMA writable_schema=ON');
diag "do pragma done";
eval { $dbh->do('UPDATE sqlite_master SET name = ? WHERE name = ?', undef, 
'bar', 'foo'); };
diag "evald";
ok $@, "updating sqlite_master is prohibited";
like $@ => qr/table sqlite_master may not be modified/;
}   
  
#v-

I get

$ prove --blib --verbose t/65_db_config.t
t/65_db_config.t .. 
1..79
...
ok 76 - sql not found
# We don't skip this section
Failed 3/79 subtests 

Test Summary Report
---
t/65_db_config.t (Wstat: 11 Tests: 76 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 79 tests but ran 76.
Files=1, Tests=76,  1 wallclock secs ( 0.20 usr  0.04 sys +  0.70 cusr  0.18 
csys =  1.12 CPU)
Result: FAIL



Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Red Hot Chili Peppers: Death Of A Martian


signature.asc
Description: Digital Signature

Bug#917492: marked as done (fam: FTBFS ('minor' was not declared in this scope))

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 19:19:07 +
with message-id 
and subject line Bug#917492: fixed in fam 2.7.0-17.3
has caused the Debian Bug report #917492,
regarding fam: FTBFS ('minor' was not declared in this scope)
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.)


-- 
917492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fam
Version: 2.7.0-17.2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
CDBS: parsing fam-2.7.0.tar.gz ...
CDBS WARNING:tarball.mk is deprecated since 0.4.85 - please use source 
format 3.0 instead
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
test -x debian/rules
mkdir -p "build-tree/fam-2.7.0"
CDBS WARNING:DEB_UPDATE_RCD_PARAMS is deprecated since 0.4.85
tar -C build-tree  -x -z -f fam-2.7.0.tar.gz
touch debian/stamp-fam-2.7.0.tar.gz
if test -e /usr/share/misc/config.guess ; then \
for i in fam-2.7.0/config.guess ; do \
cp --remove-destination /usr/share/misc/config.guess \
build-tree/$i ; \
done ; \

[... snipped ...]

 ^
DNotify.c++:536:32: error: 'minor' was not declared in this scope
 major(status->st_dev), minor(status->st_dev),
^
DNotify.c++:536:32: note: suggested alternative: 'mknod'
 major(status->st_dev), minor(status->st_dev),
^
mknod
DNotify.c++:486:9: warning: unused variable 'res' [-Wunused-variable]
 int res;
 ^~~
DNotify.c++: In static member function 'static void DNotify::read_handler(int, 
void*)':
DNotify.c++:641:11: error: 'major' was not declared in this scope
   major(dw->dir_dev), minor(dw->dir_dev), dw->dir_ino);
   ^
DNotify.c++:641:31: error: 'minor' was not declared in this scope
   major(dw->dir_dev), minor(dw->dir_dev), dw->dir_ino);
   ^
DNotify.c++:641:31: note: suggested alternative: 'mknod'
   major(dw->dir_dev), minor(dw->dir_dev), dw->dir_ino);
   ^
   mknod
DNotify.c++:602:16: warning: unused variable 'fw' [-Wunused-variable]
 FileWatch *fw;
^~
DNotify.c++: In static member function 'static void 
DNotify::overflow_signal_handler(int, siginfo_t*, void*)':
DNotify.c++:233:11: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
 write (STDERR_FILENO, str, strlen(str));
 ~~^
DNotify.c++:239:12: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   write(pipe_write_fd, , 1);
   ~^~
DNotify.c++: In static member function 'static void 
DNotify::signal_handler(int, siginfo_t*, void*)':
DNotify.c++:260:8: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
  write (STDERR_FILENO, str, strlen(str));
  ~~^
DNotify.c++:270:12: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   write(pipe_write_fd, , 1);
   ~^~
make[3]: *** [Makefile:453: DNotify.o] Error 1
make[3]: Leaving directory '/<>/build-tree/fam-2.7.0/src'
make[2]: *** [Makefile:327: all-recursive] Error 1
make[2]: Leaving directory '/<>/build-tree/fam-2.7.0'
make[1]: *** [Makefile:258: all] Error 2
make[1]: Leaving directory '/<>/build-tree/fam-2.7.0'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web 

Bug#919788: marked as done (libqxmpp1: missing Breaks+Replaces: libqxmpp0 (>= 1))

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 19:19:57 +
with message-id 
and subject line Bug#919788: fixed in qxmpp 1.0.0-4
has caused the Debian Bug report #919788,
regarding libqxmpp1: missing Breaks+Replaces: libqxmpp0 (>= 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.)


-- 
919788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqxmpp1
Version: 1.0.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libqxmpp1_1.0.0-3_amd64.deb ...
  Unpacking libqxmpp1:amd64 (1.0.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libqxmpp1_1.0.0-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libqxmpp.so.1.0.0', which is 
also in package libqxmpp0:amd64 1.0.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libqxmpp1_1.0.0-3_amd64.deb


cheers,

Andreas


libqxmpp0=1.0.0-1_libqxmpp1=1.0.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qxmpp
Source-Version: 1.0.0-4

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

Debian distribution maintenance software
pp.
Boris Pek  (supplier of updated qxmpp 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: Sat, 19 Jan 2019 21:56:20 +0300
Source: qxmpp
Binary: libqxmpp1 libqxmpp-dev libqxmpp-doc
Architecture: source
Version: 1.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: Boris Pek 
Description:
 libqxmpp-dev - Development files for the QXmpp library
 libqxmpp-doc - Documentation for the QXmpp library
 libqxmpp1  - QXmpp library for XMPP client and server applications
Closes: 919788
Changes:
 qxmpp (1.0.0-4) unstable; urgency=medium
 .
   * Update debian/control:
 - package libqxmpp1 now Breaks and Replaces package libqxmpp0
   (Closes: #919788)
 - remove Pre-Depends field from package libqxmpp1
Checksums-Sha1:
 136e2cb1395985b7e3a93551bc66f6926ca9dbf2 2151 qxmpp_1.0.0-4.dsc
 4b68d569494e7daf3035c383bbafbd312986b63d 259635 qxmpp_1.0.0.orig.tar.gz
 534e38137cb716ef66c5dbb8e21800279ca77b60 4692 qxmpp_1.0.0-4.debian.tar.xz
Checksums-Sha256:
 e03e1da79c22e340ec4d0ba5377500733addf9f5b85bbb367ecd62a929860319 2151 
qxmpp_1.0.0-4.dsc
 bf62ac8d0b5741b3cb07ea92780b279d5c34d000dc7401d6c20a9b77865a5c1e 259635 
qxmpp_1.0.0.orig.tar.gz
 43dc73de56a9351f5548508272b14f233038099a59291911a568e8101b644118 4692 
qxmpp_1.0.0-4.debian.tar.xz
Files:
 bebd1a42ff04905bccd12960f9a783e8 2151 libs optional qxmpp_1.0.0-4.dsc
 539c4c4ad3a6efa123d94dbc22e4b520 259635 libs optional qxmpp_1.0.0.orig.tar.gz
 68662e61969ec47e918d834ea07409fc 4692 libs optional qxmpp_1.0.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE74NZeBI5qRlNLX9Z0AFb0SjzkngFAlxDcu8THHRlaG5pY2tA
ZGViaWFuLm9yZwAKCRDQAVvRKPOSeNc5D/9GhFqjF/vZ8czTfkCGA+hydfw3AoCL
5eD/rv/Pjgve76GvAdk5Tyh0XqgaWRzqLdFwACwjJkzkcnJ9JwXyUWHdwK1HY0DT
/REgH+J4ABXxPBOjq1/nUCRdFA3AI0PGXPffgWZo5Mg2GNecqY6AxTqzzI5LcYIy
1+Ut8W3o/hYsOf+UVZ4r29lcc+QTqt0C5aRieF4Nb++zp4O9KfIQ0hUO1ebCplr9
JDeTslVD2X1Df1hjwm1wSgAXDfFhB5OwQxu5XYtRO0JKDiI0I/bj11ozaGvzAw9R
kgJDothNRYYsizY7Ym2rK/FhYfZG4xsMiZCQulFXRrbW5qr24/w/FIMMV7DyUxUR
G5VHFWGh76tgoiOgWbzs+3NSOiq/ocLP3P+xsrddd7ftqC/xxovVnaG13+54jS2/
IFbDffEIctKGhDXhahcpkmaVJbjfuqy3nm/SyU9kofLJPb93NdsrRM8+7fPcuoUj
YJfUT0ajOzFr/jA1ax1CQsq53AXVtez2aQZYDO4fOpIqaC0gxNbo8Y4rOMg6BNSq
CTP7RpBpGp/7d9MKlbuJisIPceXZW+kJWkBYdSdtQdRH+m2IoqW9gl6YdS1p0q5u

Processed: fam: diff for NMU version 2.7.0-17.3

[Debian Bug Tracking System]

Processing control commands:

> tags 917492 + pending
Bug #917492 [src:fam] fam: FTBFS ('minor' was not declared in this scope)
Added tag(s) pending.

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

Bug#917492: fam: diff for NMU version 2.7.0-17.3

[anarcat]

Control: tags 917492 + pending

Dear maintainer,

I've prepared an NMU for fam (versioned as 2.7.0-17.3) and
uploaded it to DELAYED/0. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
diff -u fam-2.7.0/debian/changelog fam-2.7.0/debian/changelog
--- fam-2.7.0/debian/changelog
+++ fam-2.7.0/debian/changelog
@@ -1,3 +1,11 @@
+fam (2.7.0-17.3) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix build failure with recent glibc ('minor' was not declared in this
+scope), thanks to Logan Rosen (Closes: #917492).
+
+ -- Antoine Beaupré   Sat, 19 Jan 2019 13:58:08 -0500
+
 fam (2.7.0-17.2) unstable; urgency=medium
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- fam-2.7.0.orig/.pc/.quilt_patches
+++ fam-2.7.0/.pc/.quilt_patches
@@ -0,0 +1 @@
+debian/patches
only in patch2:
unchanged:
--- fam-2.7.0.orig/.pc/.quilt_series
+++ fam-2.7.0/.pc/.quilt_series
@@ -0,0 +1 @@
+series
only in patch2:
unchanged:
--- fam-2.7.0.orig/.pc/.version
+++ fam-2.7.0/.pc/.version
@@ -0,0 +1 @@
+2
only in patch2:
unchanged:
--- fam-2.7.0.orig/debian/patches/19_glibc_2.28.patch
+++ fam-2.7.0/debian/patches/19_glibc_2.28.patch
@@ -0,0 +1,17 @@
+## Description: Fix FTBFS against glibc 2.28
+## Origin/Author: Logan Rosen 
+## Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917492
+diff -Nur -x '*.orig' -x '*~' fam-2.7.0/build-tree/fam-2.7.0/src/DNotify.c++ fam-2.7.0.new/build-tree/fam-2.7.0/src/DNotify.c++
+--- fam-2.7.0/src/DNotify.c++	2019-01-08 23:35:20.513574095 -0500
 fam-2.7.0/src/DNotify.c++	2019-01-08 23:36:37.568605429 -0500
+@@ -36,6 +36,10 @@
+ #include 
+ #include 
+ 
++#ifdef __GNU_LIBRARY__
++#include 
++#endif
++
+ #include "DNotify.h"
+ 
+ #include "Interest.h"


signature.asc
Description: PGP signature

Processed: Re-assign to correct package

[Debian Bug Tracking System]

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

> reassign 919804 python3-astropy-helpers 3.1-1
Bug #919804 [src:ndcube] ndcube: FTBFS (No module named 'sphinx_astropy')
Bug reassigned from package 'src:ndcube' to 'python3-astropy-helpers'.
No longer marked as found in versions ndcube/1.0.1-2.
Ignoring request to alter fixed versions of bug #919804 to the same values 
previously set
Bug #919804 [python3-astropy-helpers] ndcube: FTBFS (No module named 
'sphinx_astropy')
Marked as found in versions astropy-helpers/3.1-1.
> affects 919804 src:ndcube
Bug #919804 [python3-astropy-helpers] ndcube: FTBFS (No module named 
'sphinx_astropy')
Added indication that 919804 affects src:ndcube
> thanks
Stopping processing here.

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

Processed: tagging 919217

[Debian Bug Tracking System]

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

> tags 919217 + pending
Bug #919217 [lintian-brush] Missing dependency on devscripts
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#869896: Bug#909974: backports.ssl-match-hostname should be removed for buster

[Felipe Sateler]

Control: severity 909974 important

On Fri, Jan 11, 2019 at 10:15 AM Felipe Sateler  wrote:

>
>
> On Tue, Oct 2, 2018 at 4:22 PM Felipe Sateler  wrote:
>
>> Hi Matthias, Ivo,
>>
>> On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker 
>> wrote:
>> > clone 869896 -1
>> > retitle -1 remove unneeded dependency on backports.ssl-match-hostname
>> > block 869896 by -1
>> > clone -1 -2 -3 -4 -5
>> > reassign -1 libcloud
>> > reassign -2 python-docker
>> > reassign -3 websocket-client
>> > reassign -4 docker-compose
>> > reassign -5 sagemath
>> > thanks
>>
>
> Turns out the version of match_hostname in py2 does not accept ip
> addresses:
>
> py2:
> ssl.match_hostname = match_hostname(cert, hostname)
> Verify that *cert* (in decoded format as returned by
> SSLSocket.getpeercert()) matches the *hostname*.  RFC 2818 and RFC 6125
> rules are followed, but IP addresses are not accepted for *hostname*.
>
> CertificateError is raised on failure. On success, the function
> returns nothing.
>
> py3
> ssl.match_hostname = match_hostname(cert, hostname)
> Verify that *cert* (in decoded format as returned by
> SSLSocket.getpeercert()) matches the *hostname*.  RFC 2818 and RFC 6125
> rules are followed.
>
> The function matches IP addresses rather than dNSNames if hostname is a
> valid ipaddress string. IPv4 addresses are supported on all platforms.
> IPv6 addresses are supported on platforms with IPv6 support (AF_INET6
> and inet_pton).
>
> CertificateError is raised on failure. On success, the function
> returns nothing.
>
> So, if python2 backport of match_hostname does not match behavior of
> python3.5, I cannot drop the dependency. I have reverted the change and
> reopened this bug.
>
> I urge you to reconsider if the py2 version really needs to be dropped.
>
>
I'm downgrading severity to prevent autoremoval. I don't think
ssl-match-hostname can be dropped from buster.
-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#909974: backports.ssl-match-hostname should be removed for buster

[Debian Bug Tracking System]

Processing control commands:

> severity 909974 important
Bug #909974 [docker-compose] remove unneeded dependency on 
backports.ssl-match-hostname
Severity set to 'important' from 'serious'

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

Processed (with 1 error): Re: Bug#919217: Acknowledgement (Missing dependency on devscripts)

[Debian Bug Tracking System]

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

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

Bug #919217 [lintian-brush] Missing dependency on devscripts
Requested to add no tags; doing nothing.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was anar...@orangeseeds.org).
> usertag 919217 + bsp-2019-01-ca-montreal
There were no usertags set.
Usertags are now: bsp-2019-01-ca-montreal.
> thanks
Stopping processing here.

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

Bug#919217: Acknowledgement (Missing dependency on devscripts)

[anarcat]

tags 919217 +pendingo
user debian-rele...@lists.debian.org
usertag 919217 + bsp-2019-01-ca-montreal   
thanks

On Mon, Jan 14, 2019 at 09:27:08PM +0100, Jeroen Dekkers wrote:
> Control: tag -1 +patch
> 
> https://salsa.debian.org/jelmer/lintian-brush/merge_requests/1

That MR was accepted and jelmer will upload the package this weekend.

A.

Bug#915768: marked as done (mangler: B-D libg15-dev libg15daemon-client-dev are no longer available)

[Debian Bug Tracking System]

Your message dated Sat, 19 Jan 2019 18:34:38 +
with message-id 
and subject line Bug#915768: fixed in mangler 1.2.5-4.1
has caused the Debian Bug report #915768,
regarding mangler: B-D libg15-dev libg15daemon-client-dev are no longer 
available
to be marked as done.

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

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


-- 
915768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mangler
Version: 1.2.5-4
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libventrilo3-0

Hi,

the
  Build-Depends: libg15-dev, libg15daemon-client-dev
and the
  Depends: libg15daemon-client1
are no longer available in sid.


Andreas
--- End Message ---
--- Begin Message ---
Source: mangler
Source-Version: 1.2.5-4.1

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mangler 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Jan 2019 17:56:52 +
Source: mangler
Binary: mangler libventrilo3-0 libventrilo-dev
Architecture: source
Version: 1.2.5-4.1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Cheng 
Changed-By: Christopher Knadle 
Description:
 libventrilo-dev - library for communicating with Ventrilo servers (development)
 libventrilo3-0 - library for communicating with Ventrilo servers
 mangler- Ventrilo compatible client for Linux
Closes: 915768
Changes:
 mangler (1.2.5-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ William Panlener ]
   * debian/control:
 - Remove libg15 Build-Depends (g15 library has been removed)
   (Closes: #915768)
   * debian/rules:
 - Disable g15 in dh_auto_configure
Checksums-Sha1:
 02dc65c7612ef7c217f2b7e0ae2670455867737b 2154 mangler_1.2.5-4.1.dsc
 94b0a309a03449bb9899681f3f502fe269faa48c 2108367 mangler_1.2.5.orig.tar.gz
 15759113adee09361fad38b63ebcb929e7ba39e0 4872 mangler_1.2.5-4.1.debian.tar.xz
 dc8e757ad53e277f64050ac348c53b148525b6ca 6874 
mangler_1.2.5-4.1_source.buildinfo
Checksums-Sha256:
 4b5403f5c334a2313a29d1872fe55f5f7356af024aef7b4bdbba8fb08dfe64b9 2154 
mangler_1.2.5-4.1.dsc
 53fcce24d7e1e28a41784204a8f946ecd131eec82bf1db10f8d552a06b6ceb67 2108367 
mangler_1.2.5.orig.tar.gz
 59ebba1f354bd0ce93c65b21fe01b3a7606bb6ef5e6d06640d8a8fd2c175fe3b 4872 
mangler_1.2.5-4.1.debian.tar.xz
 11a0a4d14242abb39d1621c63928c2a5165b46410027b5fe23664ae55ef50d3b 6874 
mangler_1.2.5-4.1_source.buildinfo
Files:
 d0004647626ac972c7f75dcbd150e975 2154 net optional mangler_1.2.5-4.1.dsc
 c1d23c6e4b1d3eef48fb2cc34da1329c 2108367 net optional mangler_1.2.5.orig.tar.gz
 0c733b7b5d6d674163548fed88eb3c4a 4872 net optional 
mangler_1.2.5-4.1.debian.tar.xz
 9efe72ba6a32f9346687d800050fd941 6874 net optional 
mangler_1.2.5-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe1KzyGmRW/4DhtV6ieLKD9m6RHAFAlxAwlkACgkQieLKD9m6
RHCO1Q/+NrU+PZ/QDOf1OmFIfVqyq0j1ir3gHnek1SfbUtxkQgBsl7kxFBtqTqus
0a+cTcWTGFWUXKgDpB2k/IgJgqISYcPri7UW4qJTFzsU1kCmyTZOoj1snteapt+3
sv+DLzICLbNsgrr9clwFX6OoSZn4ISc9+sZL/EXSTZP4G8PlH2EKvytB/m2UfyIN
WdIz0j8XmQ7HP+zaz+DHkY2f1bIujce2xpgYRSoWpaj+8lWu9TiBsl2fKJDgkCL6
CjydJKOXhRk7G8jsuwIIAeSgzm1pxZ6Sv+ggbhV6VfjnPlNGskvUAo3uN06h4IMZ
qPzfnG9s2hvhEtnjIpM3O1zsP+HM3fPbRToLzHmx4RQMqsJnaF3g7gaJtJ3V+AjY
Jb4lSoN6lKZG3+i/1eFGi4/vZU7LfmreA/9Wfa33xSkliIBfPv7yZZ3TT8nIThbm
rb/+DNZENucjkK6FLBCs0hle7t5k/QextUjBYgxLfhQmITnagTACV/RWUo54TJlA
bauGmJXlPJxy4Zvwr6GCymfdYQKech1PkJz5RsaYO0mmxaHqv9kCD8Bb05pZKawr
IAu9FOQSHqH8bXn36Vdm1bKYrn1P2Y3EBzOZhiJv+Ff7hYGsAaYzCP7xxvuY4n2g
JrZPdRgxX/UQUtqHIN4HoreTzLfsN3T+7ulZd/79onI3xb44Cp0=
=CYzG
-END PGP SIGNATURE End Message ---

Processed: 903698 correction

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was b...@sourcerer.ca).
> usertag 903698 + bsp-2019-01-ca-montreal
There were no usertags set.
Usertags are now: bsp-2019-01-ca-montreal.
> tags 903698 -patch +moreinfo
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Removed tag(s) patch.
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Added tag(s) moreinfo.
> thank you
Stopping processing here.

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

Processed: Re: xserver-xorg-video-nv: not installable in sid, on any architecture

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 xserver-xorg-video-nv: FTBFS with current Xorg: 
> nv_driver.c:1181:6: error: too many arguments to function 
> 'pScreen->BlockHandler'
Bug #855958 [xserver-xorg-video-nv] xserver-xorg-video-nv: not installable in 
sid, on any architecture
Changed Bug title to 'xserver-xorg-video-nv: FTBFS with current Xorg: 
nv_driver.c:1181:6: error: too many arguments to function 
'pScreen->BlockHandler'' from 'xserver-xorg-video-nv: not installable in sid, 
on any architecture'.
> tags -1 ftbfs
Bug #855958 [xserver-xorg-video-nv] xserver-xorg-video-nv: FTBFS with current 
Xorg: nv_driver.c:1181:6: error: too many arguments to function 
'pScreen->BlockHandler'
Added tag(s) ftbfs.

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

Bug#855958: xserver-xorg-video-nv: not installable in sid, on any architecture

[Andreas Beckmann]

Followup-For: Bug #855958
Control: retitle -1 xserver-xorg-video-nv: FTBFS with current Xorg: 
nv_driver.c:1181:6: error: too many arguments to function 
'pScreen->BlockHandler'
Control: tags -1 ftbfs

Hi,

  CC   nv_driver.lo
In file included from ../../src/nv_include.h:19,
 from ../../src/nv_driver.c:31:
/usr/include/xorg/xf86PciInfo.h:50:2: warning: #warning "xf86PciInfo.h is 
deprecated.  For greater compatibility, drivers should include necessary PCI 
IDs locally rather than relying on this file from xorg-server
." [-Wcpp]
 #warning "xf86PciInfo.h is deprecated.  For greater compatibility, drivers 
should include necessary PCI IDs locally rather than relying on this file from 
xorg-server."
  ^~~
In file included from ../../src/nv_include.h:34,
 from ../../src/nv_driver.c:31:
../../src/nv_driver.c: In function 'NVPciProbe':
../../src/nv_const.h:5:17: warning: format '%x' expects argument of type 
'unsigned int', but argument 4 has type 'CARD32' {aka 'const long unsigned 
int'} [-Wformat=]
 #define NV_NAME "NV"
 ^~~~
../../src/nv_driver.c:916:20: note: in expansion of macro 'NV_NAME'
NV_NAME ": The PCI device 0x%x (%s) at 
%2.2d@%2.2d:%2.2d:%1.1d has a kernel module claiming it.\n",
^~~
../../src/nv_driver.c:916:49: note: format string is defined here
NV_NAME ": The PCI device 0x%x (%s) at 
%2.2d@%2.2d:%2.2d:%1.1d has a kernel module claiming it.\n",
~^
%lx
In file included from ../../src/nv_include.h:34,
 from ../../src/nv_driver.c:31:
../../src/nv_const.h:5:17: warning: format '%x' expects argument of type 
'unsigned int', but argument 4 has type 'CARD32' {aka 'const long unsigned 
int'} [-Wformat=]
 #define NV_NAME "NV"
 ^~~~
../../src/nv_driver.c:929:24: note: in expansion of macro 'NV_NAME'
NV_NAME ": Ignoring unsupported device 0x%x (%s) at 
%2.2d@%2.2d:%2.2d:%1.1d\n",
^~~
../../src/nv_driver.c:929:66: note: format string is defined here
NV_NAME ": Ignoring unsupported device 0x%x (%s) at 
%2.2d@%2.2d:%2.2d:%1.1d\n",
 ~^
 %lx
In file included from ../../src/nv_include.h:34,
 from ../../src/nv_driver.c:31:
../../src/nv_const.h:5:17: warning: format '%x' expects argument of type 
'unsigned int', but argument 4 has type 'CARD32' {aka 'const long unsigned 
int'} [-Wformat=]
 #define NV_NAME "NV"
 ^~~~
../../src/nv_driver.c:933:24: note: in expansion of macro 'NV_NAME'
NV_NAME ": Ignoring unsupported device 0x%x at 
%2.2d@%2.2d:%2.2d:%1.1d\n",
^~~
../../src/nv_driver.c:933:66: note: format string is defined here
NV_NAME ": Ignoring unsupported device 0x%x at 
%2.2d@%2.2d:%2.2d:%1.1d\n",
 ~^
 %lx
../../src/nv_driver.c: In function 'NVBlockHandler':
../../src/nv_driver.c:1181:6: error: too many arguments to function 
'pScreen->BlockHandler'
 (*pScreen->BlockHandler) (BLOCKHANDLER_ARGS);
 ~^~~
../../src/nv_driver.c:1182:27: warning: assignment to 
'ScreenBlockHandlerProcPtr' {aka 'void (*)(struct _Screen *, void *)'} from 
incompatible pointer type 'void (*)(struct _Screen *, void *, void *)' 
[-Wincompatible-pointer-types]
 pScreen->BlockHandler = NVBlockHandler;
   ^
../../src/nv_driver.c: In function 'NVScreenInit':
../../src/nv_driver.c:2593:16: warning: implicit declaration of function 
'xf86DisableRandR'; did you mean 'xf86DisableIO'? 
[-Wimplicit-function-declaration]
xf86DisableRandR();
^~~~
xf86DisableIO
../../src/nv_driver.c:2620:27: warning: assignment to 
'ScreenBlockHandlerProcPtr' {aka 'void (*)(struct _Screen *, void *)'} from 
incompatible pointer type 'void (*)(struct _Screen *, void *, void *)' 
[-Wincompatible-pointer-types]
 pScreen->BlockHandler = NVBlockHandler;
   ^
make[3]: *** [Makefile:582: nv_driver.lo] Error 1


Andreas

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[anarcat]

user debian-rele...@lists.debian.org
usertag nn + bsp-2019-01-ca-montreal   
tags -1 -patch +moreinfo
thank you

On Thu, Jan 03, 2019 at 10:16:13AM +0100, Samuel Thibault wrote:
> Oops, this bug was erroneously closed because its mention was remaining
> in the sphinxbase changelog.

So after reviewing this bug during the montreal BSP, I'm a little
confused - it shows up in the "sponsor" UDD dashboard because it's
marked as affecting buster and sid but with a patch.

Yet, I don't see a recent patch that will fix the issue in dh-python.
I'm not even sure there *is* an issue in dh-python at all anymore...

Could someone summarize the current state of this bug report?

Thanks!

-- 
Be yourself. Everyone else is already taken!
- Oscar Wilde


signature.asc
Description: PGP signature