Bug#921363: marked as done (Not suitable for buster, package unmaintained)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 07:52:23 +
with message-id 
and subject line Bug#921363: fixed in ejs.js 1.0.0+dfsg1-2
has caused the Debian Bug report #921363,
regarding Not suitable for buster, package unmaintained
to be marked as done.

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

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


-- 
921363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ejs.js
Version: 1.0.0+dfsg1-1
Severity: serious

Dear all,

In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.

Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by someone with more involvement in
Javascript packaging than me. Thanks!

light+love,
Mike


-- System Information:
Debian Release: 9.7
  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: ejs.js
Source-Version: 1.0.0+dfsg1-2

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

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

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated ejs.js package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Feb 2019 07:51:53 +0530
Source: ejs.js
Binary: libjs-ejs node-ejs
Architecture: source
Version: 1.0.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 921363
Description: 
 libjs-ejs  - Embedded JavaScript templates (client support)
 node-ejs   - Embedded JavaScript templates for Node.js
Changes:
 ejs.js (1.0.0+dfsg1-2) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Add myself as an uploader (Closes: #921363)
   * Bump debhelper compatibility level to 11
   * Bump Standards-Version to 4.3.0
   * Add d/upstream/metadata
   * Update d/copyright
   * Add package.json in d/*.install
   * Re-write d/rules
   * Switch test to pkg-js-tools
 .
   [ Xavier Guimard ]
   * Add patches to fix test and Makefile
   * Add "Multi-Arch: foreign"
Checksums-Sha1: 
 ca04796abf5fe36810a80060141d0a803c4f0a02 2084 ejs.js_1.0.0+dfsg1-2.dsc
 e36553a5452d86277670e57f7da5bf462b8d02bc 3988 
ejs.js_1.0.0+dfsg1-2.debian.tar.xz
Checksums-Sha256: 
 0c5aee8ba31c09d33da84014f4c0b9de3dbafda4d3b69279e8b69fd4f0004118 2084 
ejs.js_1.0.0+dfsg1-2.dsc
 d2e590b4a070d0ba251ccc6531108933da2775e1ba0f895910ee80f685c69706 3988 
ejs.js_1.0.0+dfsg1-2.debian.tar.xz
Files: 
 2dd2fc53d400f1693249648ba2d0f2bc 2084 javascript optional 
ejs.js_1.0.0+dfsg1-2.dsc
 ee9d1ac14b93d365312b2339b73fc6e4 3988 javascript optional 
ejs.js_1.0.0+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxmWMQACgkQ9tdMp8mZ
7ulayQ//TzJd6HFtWXKX/5G3aPsGK/l4c0lhf+rvv+HjjBUmyH7QEHSxocN9ksly
7T1VpFV6GGzRhdFPgd4UpfWKGLvqMzyAzVPg1Qv0hq+NqUQqQciGWv1kNxbly9g+
YT99rsN8KPUcvtXREaa8QGKZvAmxNDcexhzZSBr9PcE+yq8JuAnx09BFgDp4khno
I+3HfVfFL4sDF9lvVDIt41/s4qZ1LsXIchm1xxktM6X4XvZXy2A3FaOEIYeJ5i40
GhOlSYy1eY9J9vDrT4E6MfzvcXrp0pCTg1/wIuaUcAA12TIu+UNXcNbo/rs03PbP
sMahWxB9sfa5oZDPcsqAVEyR+XSluZGDXkSNnz0PaowAC9CZCaOLLoWlpXvFt1Bu
sX+rEv/uLazgWrozmiZDzje0yWitbcq/mbM5BQaLhVYB6SC5ezRBJoKrgi+44jwe
/06QY1Km3Hhn9zTwPu2525ZobdEuklRUXskEIcMP63SxUGyKX2eXAAQVENyJZJCP
kohCsKCHSKAe01Ti/F69m2AsJXadEiwmWTo+BrESH/stF2MOVtiwTU+dv71x/mPv
VI5s9tAcclQHk6IDTqHfgRO86utZTejh3S4jlSaMAise2uGBVIrh3wBkv0l5cDAZ
3oSAJMNHKyUp5KVdw3BmnLwXw+c1dmo6npBaYWV/dKO3lbY+/aY=
=SF0U
-END PGP SIGNATURE End Message ---

Bug#921365: marked as done (Not suitable for buster, package probably unmaintained)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 07:55:03 +
with message-id 
and subject line Bug#921365: fixed in node-async-stacktrace 0.0.2-3
has caused the Debian Bug report #921365,
regarding Not suitable for buster, package probably unmaintained
to be marked as done.

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

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


-- 
921365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-async-stacktrace
Version: 0.0.2-2
Severity: serious

Dear all,

In 2016/12 I removed my name from this package's Uploaders: field. It
hasn't been touch sinced then and seems unmaintained.

Due to this, the package might not be suitable for the Debian buster
release. This needs to be checked by someone with more involvement in
Javascript packaging than me. Thanks!

light+love,
Mike


-- System Information:
Debian Release: 9.7
  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)

Versions of packages node-async-stacktrace depends on:
ii  nodejs  4.8.2~dfsg-1

node-async-stacktrace recommends no packages.

node-async-stacktrace suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-async-stacktrace
Source-Version: 0.0.2-3

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated 
node-async-stacktrace 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, 14 Feb 2019 22:51:58 +0100
Source: node-async-stacktrace
Binary: node-async-stacktrace
Architecture: source
Version: 0.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 921365
Description: 
 node-async-stacktrace - Improve Node.js stacktraces and make it easier to 
handle errors
Changes:
 node-async-stacktrace (0.0.2-3) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Add myself as an uploader (Closes: #921365)
   * Bump Standards-Version to 4.3.0
   * Bump debhelper compatibility level to 11
   * Add d/upstream/metadata
   * Add d/tests/*
   * Add minimal test
   * Fix URL in d/copyright
 .
   [ Xavier Guimard ]
   * Switch test to pkg-js-tools
Checksums-Sha1: 
 9ef2583b88408aa00c79024ab990580c8bbad632 2123 node-async-stacktrace_0.0.2-3.dsc
 fee03430570b9b6bcd82b5f3563197dda619c81d 2604 
node-async-stacktrace_0.0.2-3.debian.tar.xz
Checksums-Sha256: 
 2a3915c121975c33e6a52ad1435faecaa6cac4425f510e8c84a572777ca387cc 2123 
node-async-stacktrace_0.0.2-3.dsc
 ad31a8966ecb083c3925b3624dd4a4df755ab6b4ff5b0d2d520843d268658e93 2604 
node-async-stacktrace_0.0.2-3.debian.tar.xz
Files: 
 51b8cb91fd1dbb007fb283df3f883d40 2123 javascript optional 
node-async-stacktrace_0.0.2-3.dsc
 f96ed748b9187722f9eb7ccd25aa4112 2604 javascript optional 
node-async-stacktrace_0.0.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxmUMkACgkQ9tdMp8mZ
7unPGxAAh2+3sqdCA3MI4/9eLW9PJlmmXeP9PrvY14s8OHEcKiRNzB4i0YRRXAD7
B5jTVyVYGr6noLJtAYYQveYlNcrRhbZNyrZTo6Jxg62P8p8hETKQMPleCX7t0+tK
uWQTIK75u0z+pOdv3rAsR7dn5Oz6QYKR8SFTuckuA/Dog9ZnkZTdc4mJUVl29Ryq
elS95goy8QeutK5NKYht9i9NsepqIIByPa79G2nzhcelRss9I2IzQt42pqC7vWfM
KxCceQ5Rapx6fBQNEUQq9casSebwy7UKsMlhbqry+FFrOavOumNZBBziP8GgHuoO
AUn79jKoWvKwz4YDcSUkSCYo4pyvt5FKh8/7bdFtysv8f7Hs1BOhd1fcFo7vA1kK
L9YeccTXy0id+dUER/AqNGca+kWjMjAcPeXlozB08BmZKjsX4fL6l7buobgJxuks
zstD8J1HR4iGQr0iQpQJSsS+ZzTjSFj2AaYXg3763PRAqgrrSNMj7TAmPMudk+7/
716ITy1bNuzUEgmzGW3kQpnVzCkjyoq9OL1qqivjTMoN+CTnVOBUlGj7Q95J3RYq
pV5XD63eyZnfO+Oq97B2SBzrPPQjt6mlpwk7G0PMrUOHZQF5R0KzTHY2ErxtinqA
s2IvjMD1ERafy1BJ15OstY/IlkUOE7Yd4h505Qi04TcR/jRGGn0=
=xq8G
-END PGP SIGNATURE End Message ---

Bug#920709: distcc: fails to upgrade from 'testing': causes dpkg trigger loop

[Christian Marillat]

On 28 janv. 2019 15:07, Andreas Beckmann  wrote:

> Hi Guillem,
>
> do you have any recommendations for this trigger loop?
> I think at this point it is already dpkg 1.19.4 that is running
> (dpkg is being upgraded during the same run).

Guillem ? Would be nice to have your advice on this bug.

Christian

Bug#922350: udevd does not start after reboot

[Vincent Danjean]

Le 15/02/2019 à 08:01, Vincent Danjean a écrit :
> Le 14/02/2019 à 22:59, Felipe Sateler a écrit :
>> Is udev by any chance i386 instead of amd64?
> 
> I don't think so:
> vdanjean@eyak:~$ apt-cache policy udev:i386
> udev:i386:
>   Installé : (aucun)

However, systemd was installed as i386:
vdanjean@eyak:~$ apt-cache policy systemd:i386
systemd:i386:
  Installé : 240-5
  Candidat : 240-5
 Table de version :
 *** 240-5 500
500 http://ftp.fr.debian.org/debian testing/main i386 Packages
500 http://ftp.fr.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status
 239-12~bpo9+1 100
100 http://ftp.fr.debian.org/debian stretch-backports/main i386 Packages
 232-25+deb9u8 500
500 http://security.debian.org stretch/updates/main i386 Packages
 232-25+deb9u6 500
500 http://ftp.fr.debian.org/debian stretch/main i386 Packages
vdanjean@eyak:~$ apt-cache policy systemd:amd64
systemd:
  Installé : (aucun)
  Candidat : 240-5
 Table de version :
 240-5 500
500 http://ftp.fr.debian.org/debian testing/main amd64 Packages
500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages
 239-12~bpo9+1 100
100 http://ftp.fr.debian.org/debian stretch-backports/main amd64 
Packages
 232-25+deb9u8 500
500 http://security.debian.org stretch/updates/main amd64 Packages
 232-25+deb9u6 500
500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages

It probably comes from the fact that:
1) using apt-listbugs, I blocked the upgrade of systemd due to
   919231
2) the upgrade fails due to another package. So I've to go with
   'apt install -f'
3) 'apt install -f' alone was removing packages I would like to keep
   (such as digikam), so I forced some packages on the command line
4) due to (1), apt probably solved some problem by selecting the
   i386 version of systemd (I did not remark anything during the
   installation)

  So, the severity can be lowered and I will test with a reboot
as soon as possible.

  Regards,
Vincent

-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#922350: udevd does not start after reboot

[Vincent Danjean]

Le 14/02/2019 à 22:59, Felipe Sateler a écrit :
> Is udev by any chance i386 instead of amd64?

I don't think so:
vdanjean@eyak:~$ apt-cache policy udev:i386
udev:i386:
  Installé : (aucun)
  Candidat : 240-5
 Table de version :
 240-5 500
500 http://ftp.fr.debian.org/debian testing/main i386 Packages
500 http://ftp.fr.debian.org/debian unstable/main i386 Packages
 239-12~bpo9+1 100
100 http://ftp.fr.debian.org/debian stretch-backports/main i386 Packages
 232-25+deb9u8 500
500 http://security.debian.org stretch/updates/main i386 Packages
 232-25+deb9u6 500
500 http://ftp.fr.debian.org/debian stretch/main i386 Packages
vdanjean@eyak:~$ apt-cache policy udev:amd64
udev:
  Installé : 240-5
  Candidat : 240-5
 Table de version :
 *** 240-5 500
500 http://ftp.fr.debian.org/debian testing/main amd64 Packages
500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 239-12~bpo9+1 100
100 http://ftp.fr.debian.org/debian stretch-backports/main amd64 
Packages
 232-25+deb9u8 500
500 http://security.debian.org stretch/updates/main amd64 Packages
 232-25+deb9u6 500
500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages

  Regards,
Vincent


> -- 
> 
> Saludos,
> Felipe Sateler


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Processed: Bug #922271 in camomile marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #922271 [src:camomile] camomile: ocaml-gettext build still fails, due to 
wrong search path caused by camomile build
Added tag(s) pending.

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

Bug#922271: Bug #922271 in camomile marked as pending

[Kyle Robbertze]

Control: tag -1 pending

Hello,

Bug #922271 in camomile 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/ocaml-team/camomile/commit/2b02b05d0234af24bf1c6ecb41a11cdb1dc03620


Remove build path in compiled artifacts (Closes: #922271)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/922271

Bug#922369: javamail: FTBFS on Buster/Sid

[Ritesh Raj Sarraf]

Source: javamail
Severity: serious
Tags: ftbfs
Justification: fails to build from source


You can also see the same build failure from the reproducible builds
projects efforts.

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

[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/index-all.html...
[  254s] Building index for all classes...
[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/allclasses-index.html...
[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/allpackages-index.html...
[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/deprecated-list.html...
[  254s] Building index for all classes...
[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/allclasses.html...
[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/allclasses.html...
[  254s] Generating /usr/src/packages/BUILD/mail/target/apidocs/index.html...
[  254s] Generating 
/usr/src/packages/BUILD/mail/target/apidocs/overview-summary.html...
[  254s] Generating /usr/src/packages/BUILD/mail/target/apidocs/help-doc.html...
[  254s] 1 error
[  254s] 1 warning
[  254s] [[1;34mINFO[m] 
[  254s] [[1;34mINFO[m] 
[1m[m
[  254s] [[1;34mINFO[m] [1mSkipping JavaMail API distribution[m
[  254s] [[1;34mINFO[m] This project has been banned from the build due to 
previous failures.
[  254s] [[1;34mINFO[m] 
[1m[m
[  254s] [[1;34mINFO[m] 
[1m[m
[  254s] [[1;34mINFO[m] [1mReactor Summary for JavaMail API distribution 
1.6.2:[m
[  254s] [[1;34mINFO[m] 
[  254s] [[1;34mINFO[m] JavaMail API distribution .. 
[1;32mSUCCESS[m [  2.080 s]
[  254s] [[1;34mINFO[m] JavaMail API ... 
[1;31mFAILURE[m [ 21.766 s]
[  254s] [[1;34mINFO[m] JavaMail API (no providers)  
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API jar ... 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API smtp provider . 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API imap provider . 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API Gmail IMAP provider ... 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API pop3 provider . 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API dsn support ... 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] JavaMail API logging handler ... 
[1;33mSKIPPED[m
[  254s] [[1;34mINFO[m] 
[1m[m
[  254s] [[1;34mINFO[m] [1;31mBUILD FAILURE[m
[  254s] [[1;34mINFO[m] 
[1m[m
[  254s] [[1;34mINFO[m] Total time:  24.522 s
[  254s] [[1;34mINFO[m] Finished at: 2019-02-15T04:59:59Z
[  254s] [[1;34mINFO[m] 
[1m[m
[  254s] [[1;31mERROR[m] Failed to execute goal 
[32morg.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar[m 
[1m(default-cli)[m on project [36mjavax.mail[m: [1;31mMavenReportException: 
Error while generating Javadoc: [m
[  254s] [[1;31mERROR[m] [1;31mExit code: 1 - javadoc: error - The code being 
documented uses modules but the packages defined in 
https://docs.oracle.com/javase/7/docs/api/ are in the unnamed module.[m
[  254s] [[1;31mERROR[m] 
[1;31m/usr/src/packages/BUILD/mail/src/main/java/com/sun/mail/util/package.html:60:
 warning - Tag @link: reference not found: java.util.logging[m
[  254s] [[1;31mERROR[m] [1;31m[m
[  254s] [[1;31mERROR[m] [1;31mCommand line was: 
/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc @options @argfile[m
[  254s] [[1;31mERROR[m] [1;31m[m
[  254s] [[1;31mERROR[m] [1;31mRefer to the generated Javadoc files in 
'/usr/src/packages/BUILD/mail/target/apidocs' dir.[m
[  254s] [[1;31mERROR[m] [1;31m[m
[  254s] [[1;31mERROR[m] -> [1m[Help 1][m
[  254s] [[1;31mERROR[m] 
[  254s] [[1;31mERROR[m] To see the full stack trace of the errors, re-run 
Maven with the [1m-e[m switch.
[  254s] [[1;31mERROR[m] Re-run Maven using the [1m-X[m switch to enable full 
debug logging.
[  254s] [[1;31mERROR[m] 
[  254s] [[1;31mERROR[m] For more information about the errors and possible 
solutions, please read the following articles:
[  254s] [[1;31mERROR[m] [1m[Help 1][m 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[  254s] [[1;31mERROR[m] 
[  254s] [[1;31mERROR[m] After correcting the problems, you can resume the 
build with the command
[  254s] [[1;31mERROR[m]   [1mmvn  -rf :javax.mail[m
[  255s] dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 

Processed: limit source to php-zeta-base, tagging 917744, tagging 882917

[Debian Bug Tracking System]

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

> limit source php-zeta-base
Limiting to bugs with field 'source' containing at least one of 'php-zeta-base'
Limit currently set to 'source':'php-zeta-base'

> tags 917744 + pending
Bug #917744 [src:php-zeta-base] php-zeta-base: FTBFS: PHP Fatal error:  
Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in 
/usr/share/php/ezc/UnitTest/test/case.php:33
Added tag(s) pending.
> tags 882917 + pending
Bug #882917 [src:php-zeta-base] php-zeta-base FTBFS with phpunit 6.4.4-2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to php-zeta-console-tools, tagging 917760

[Debian Bug Tracking System]

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

> limit source php-zeta-console-tools
Limiting to bugs with field 'source' containing at least one of 
'php-zeta-console-tools'
Limit currently set to 'source':'php-zeta-console-tools'

> tags 917760 + pending
Bug #917760 [src:php-zeta-console-tools] php-zeta-console-tools: FTBFS: PHP 
Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in 
/usr/share/php/ezc/UnitTest/test/case.php:33
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#921895: marked as done (bitlbee: does not build all binary packages by default)

[Debian Bug Tracking System]

Your message dated Fri, 15 Feb 2019 00:49:33 +
with message-id 
and subject line Bug#921895: fixed in bitlbee 3.5.1-1.2
has caused the Debian Bug report #921895,
regarding bitlbee: does not build all binary packages by default
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.)


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

Hello,

This source package's rules file does not build all the binary packages
listed in d/control unless special environment variable values are
present.  As a result, bin:skyped and bin:bitlbee-plugin-skype are not
in the archive.

This caused my source-only NMU of this package to be rejected, because
dak wanted to put it in binNEW because of skyped and
bitlbee-plugin-skype, but source-only uploads to binNEW are not allowed.

I think this is a bug of RC-severity because it is a highly irregular
use of the Debian source package format which is confusing to people
trying to do NMUs.  Perhaps the maintainer will disagree; a downgrade
of the severity of this bug would make sense if it turns out I'm not
aware of some workflow that not building all the binary packages by
default enables.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: bitlbee
Source-Version: 3.5.1-1.2

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated bitlbee 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, 09 Feb 2019 17:03:38 -0700
Source: bitlbee
Binary: bitlbee bitlbee-libpurple bitlbee-common bitlbee-dev bitlbee-plugin-otr
Architecture: all amd64 source
Version: 3.5.1-1.2
Distribution: unstable
Urgency: medium
Maintainer: Wilmer van der Gaast 
Changed-By: Sean Whitton 
Closes: 816200 921895
Description: 
 bitlbee-common - IRC to other chat networks gateway (common files/docs)
 bitlbee-dev - IRC to other chat networks gateway (dev files)
 bitlbee- IRC to other chat networks gateway (default version)
 bitlbee-libpurple - IRC to other chat networks gateway (using libpurple)
 bitlbee-plugin-otr - IRC to other chat networks gateway (OTR plugin)
Changes:
 bitlbee (3.5.1-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Comment out bitlbee-plugin-skype and skyped in d/control (Closes: #921895).
 These binary packages are not built by d/rules by default, and as such
 they are not currently in the archive.  Commenting them out in order
 to avoid my NMU hitting binNEW; this caused the -1.1 source-only
 upload to fail.
 Thank you to Mattia Rizzolo for suggesting this fix.
 .
 bitlbee (3.5.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add existence check to chmod call in bitlbee-common.postinst
 (Closes: #816200).
Checksums-Sha1: 
 a58edb53c83701908f3e76c0e65e05254ca21fea 2361 bitlbee_3.5.1-1.2.dsc
 fd6e574edda61156d3f96714fc018981fa758146 15466 bitlbee_3.5.1-1.2.diff.gz
 e708017e218b63706dc7fdeadcaf1a11dba4d2c2 78460 bitlbee-common_3.5.1-1.2_all.deb
 3d9fd58af41cb286f40013120527951e514018c5 1057492 
bitlbee-dbgsym_3.5.1-1.2_amd64.deb
 a80e12a9930144d048f41e03c0625068e9c55d16 29724 bitlbee-dev_3.5.1-1.2_all.deb
 82023d154414fcbf9e0bcefe7f197f7efddac3cb 626164 
bitlbee-libpurple-dbgsym_3.5.1-1.2_amd64.deb
 b8a0add2354861a60a014f905d8de1fe4b988645 132312 
bitlbee-libpurple_3.5.1-1.2_amd64.deb
 b8bcad3b2fd8da3b46d08eec70c22d1317b8e22d 46692 
bitlbee-plugin-otr-dbgsym_3.5.1-1.2_amd64.deb
 9bc310ecd7d84723b9bd565c4346c1deeec0bd32 17352 
bitlbee-plugin-otr_3.5.1-1.2_amd64.deb
 d382a795ea99a01145e32861f1e59df26fc82720 16944 
bitlbee_3.5.1-1.2_amd64.buildinfo
 20a07692d2f2d5cfe36433932e2d1d4892634145 211284 bitlbee_3.5.1-1.2_amd64.deb
Checksums-Sha256: 
 130697ba3273534cfbf4d663c37ef1b88a70eaa158b03187b117f84705baeac5 2361 
bitlbee_3.5.1-1.2.dsc
 781d5c61481c66f1ce75c13c018ef51a55bd57c0c50a2be7903f531655b44fb6 

Bug#920018: Memory Leak in journald? Failed to write entry (23 items, 500 bytes), ignoring: Cannot allocate memory

[John David Anglin]

I still seeing this bug on hppa with systemd 240-5.  Started with 240-4.

Regards,
Dave

-- 
John David Anglin  dave.ang...@bell.net

Bug#922356: nbd: FTBFS in sid (rm: cannot remove 'gitstatus': No such file or directory)

[Santiago Vila]

Package: src:nbd
Version: 1:3.19-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
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
test -f nbd.h
if [ -d .git ]; then if [ $(git status --porcelain | tee gitstatus | wc -l) -ne 
1 ]; then echo "GIT STATUS:"; echo "==="; cat gitstatus; exit 1; fi; fi
rm gitstatus
rm: cannot remove 'gitstatus': No such file or directory
make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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/nbd.html

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#922355: vmdb2: FTBFS in sid (LaTeX Error: File `lmodern.sty' not found)

[Santiago Vila]

Package: src:vmdb2
Version: 0.13.2+git20190214-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with=python3 --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 '/<>/vmdb2-0.13.2+git20190214'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/step_list.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/__init__.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/step_list_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/tags_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/spec.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/runcmd.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/unmount.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/unmount_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/version.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/state.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/spec_tests.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/app.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
copying vmdb/tags.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb
creating 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/chroot_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/qemudebootstrap_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/__init__.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/lvm2_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/debootstrap_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/rootfs_cache_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/luks_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/grub_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/error_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/mkimg_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/apt_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/mount_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/mkfs_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/virtuals_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/partition_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/ansible_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
copying vmdb/plugins/echo_plugin.py -> 
/<>/vmdb2-0.13.2+git20190214/.pybuild/cpython3_3.7_vmdb2/build/vmdb/plugins
running build_scripts
creating build
creating build/scripts-3.7
copying and adjusting vmdb2 -> build/scripts-3.7
changing mode of build/scripts-3.7/vmdb2 from 664 to 775
building yarns
./format.sh
Error producing PDF.
! LaTeX Error: File `lmodern.sty' not found.

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

Enter file name: 
! Emergency stop.
 
 
l.6 \usepackage

make[1]: *** [debian/rules:10: override_dh_auto_build] Error 43
make[1]: Leaving directory '/<>/vmdb2-0.13.2+git20190214'
make: *** [debian/rules:6: build-indep] 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"
and it also fails here:

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

[Sebastian Andrzej Siewior]

On 2019-02-02 14:46:54 [+0100], Andreas Beckmann wrote:
> I'm not going to touch that package, please go ahead with preparing a
> NMU (or probably rather QA upload if it is gone from sid) to stretch,
> since you seem to know how to properly fix this bug once and for all :-)

I'm proposing this attached debdiff.
For testing I compiled it against libssl1.0-dev 1.0.2j-5 and then
upgraded to the version provided by the security repository. No error
message. I expect it work - it would be awesome if the reporter could
confirm this (I can provided the binary packages if required).

> Andreas

Sebastian
diff -Nru ckermit-302/debian/changelog ckermit-302/debian/changelog
--- ckermit-302/debian/changelog	2017-01-12 09:18:27.0 +0100
+++ ckermit-302/debian/changelog	2019-02-14 23:35:55.0 +0100
@@ -1,3 +1,11 @@
+ckermit (302-5.3+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop check openssl compile time version vs runtime version
+(Closes: #917485).
+
+ -- Sebastian Andrzej Siewior   Thu, 14 Feb 2019 23:35:55 +0100
+
 ckermit (302-5.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ckermit-302/debian/patches/ckermit-drop-the-version-for-openssl.patch ckermit-302/debian/patches/ckermit-drop-the-version-for-openssl.patch
--- ckermit-302/debian/patches/ckermit-drop-the-version-for-openssl.patch	1970-01-01 01:00:00.0 +0100
+++ ckermit-302/debian/patches/ckermit-drop-the-version-for-openssl.patch	2019-02-14 23:31:55.0 +0100
@@ -0,0 +1,110 @@
+From: Sebastian Andrzej Siewior 
+Date: Thu, 14 Feb 2019 22:13:40 +0100
+Subject: [PATCH] ckermit: drop the version for openssl
+
+ckermit checks at runtime the version of the libssl it was compiled
+against the libssl library it is running. The comment says that it is
+required because the ABI is not stable at the 1.0.0 version and may
+change so it is better to abort.
+Meanwhile, openssl has a stable ABI and if something changes in a
+non-compatible way then the so name changes.
+
+Remove the check if the version of libssl changed between compile time
+and run time because it is outdated / not required anymore.
+
+BTS: https://bugs.debian.org/917485
+
+Signed-off-by: Sebastian Andrzej Siewior 
+---
+ ck_ssl.c | 68 +---
+ 1 file changed, 1 insertion(+), 67 deletions(-)
+
+diff --git a/ck_ssl.c b/ck_ssl.c
+index 3640d8f07fa86..75e2875c7fe91 100644
+--- a/ck_ssl.c
 b/ck_ssl.c
+@@ -1362,15 +1362,7 @@ ssl_once_init()
+ 
+ if ( !ck_ssleay_is_installed() )
+ return;
+-/*
+-  OpenSSL does not provide for ABI compatibility between releases prior
+-  to version 1.0.0.  If the version does not match, it is not safe to
+-  assume that any function you call takes the same parameters or does
+-  the same thing with them.  Removing this test prior to the OpenSSL 1.0.0
+-  release will result in an increase in unexplained or incorrect behaviors.
+-  The test should be revised once OpenSSL 1.0.0 is released and we see what
+-  its claims are as to ABI compatibility.
+-*/
++
+ debug(F111,"Kermit built for OpenSSL",OPENSSL_VERSION_TEXT,SSLEAY_VERSION_NUMBER);
+ #ifndef OS2ONLY
+ debug(F111,"OpenSSL Library",SSLeay_version(SSLEAY_VERSION),
+@@ -1380,64 +1372,6 @@ ssl_once_init()
+ debug(F110,"OpenSSL Library",SSLeay_version(SSLEAY_PLATFORM),0);
+ 
+ /* The following test is suggested by Richard Levitte */
+-if (((OPENSSL_VERSION_NUMBER ^ SSLeay()) & 0xff0f) 
+-#ifdef OS2
+- || ckstrcmp(OPENSSL_VERSION_TEXT,(char *)SSLeay_version(SSLEAY_VERSION),-1,1)
+-#endif /* OS2 */
+- ) {
+-ssl_installed = 0;
+-debug(F111,"OpenSSL Version does not match.  Built with",
+-   SSLeay_version(SSLEAY_VERSION),SSLEAY_VERSION_NUMBER);
+-printf("?OpenSSL libraries do not match required version:\r\n");
+-printf("  . C-Kermit built with %s\r\n",OPENSSL_VERSION_TEXT);
+-printf("  . Version found  %s\r\n",SSLeay_version(SSLEAY_VERSION));
+-printf("  OpenSSL versions prior to 1.0.0 must be the same.\r\n");
+-
+-	s = "R";
+-#ifdef SOLARIS
+-	printf("  Set CD_LIBRARY_PATH for %s.\r\n",OPENSSL_VERSION_TEXT);
+-	s = " Or r";
+-#endif	/* SOLARIS */
+-
+-#ifdef HPUX
+-	printf("  Set SHLIB_PATH for %s.\r\n",OPENSSL_VERSION_TEXT);
+-	s = " Or r";
+-#endif	/* HPUX */
+-
+-#ifdef AIX
+-	printf("  Set LIBPATH for %s.\r\n",OPENSSL_VERSION_TEXT);
+-	s = " Or r";
+-#endif	/* AIX */
+-
+-#ifdef LINUX
+-	printf("  Set LD_LIBRARY_PATH for %s.\r\n",OPENSSL_VERSION_TEXT);
+-	s = " Or r";
+-#endif	/* LINUX */
+-
+-printf(" %sebuild C-Kermit from source on this computer to make \
+-versions agree.\r\n",s);
+-
+-#ifdef KTARGET
+-	{
+-	char * s;
+-	s = KTARGET;
+-	if (!s) s = "";
+-	if (!*s) s = "(unknown)";
+-	printf("  C-Kermit makefile target: %s\r\n",s);
+-	}
+-#endif	/* KTARGET */
+-printf("  Or if that is what you did then try to find out why\r\n");
+-

Bug#864657: marked as done (ca-certificates-java has circular Depends on openjdk-8-jre-headless)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 22:22:37 +
with message-id 
and subject line Bug#864657: fixed in ca-certificates-java 20190214
has caused the Debian Bug report #864657,
regarding ca-certificates-java has circular Depends on openjdk-8-jre-headless
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.)


-- 
864657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-java
Version: 20170531
Severity: important

Hello Debian Java Maintainers,

There is a circular dependency between ca-certificates-java and
openjdk-8-jre-headless:

ca-certificates-java:Depends: openjdk-8-jre-headless | 
java7-runtime-headless
openjdk-8-jre-headless  :Depends: ca-certificates-java

Circular dependencies are known to cause problems during upgrade between
stable releases, so we should try to avoid them.

Also see bug #864597.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 
--- End Message ---
--- Begin Message ---
Source: ca-certificates-java
Source-Version: 20190214

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Feb 2019 22:21:15 +0100
Source: ca-certificates-java
Architecture: source
Version: 20190214
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 864657
Changes:
 ca-certificates-java (20190214) unstable; urgency=medium
 .
   * Team upload.
   * Declare compliance with Debian Policy 4.3.0.
   * ca-certificates-java: Depend on default-jre-headless to avoid a circular 
dependency on
 a specific OpenJDK package. (Closes: #864657)
Checksums-Sha1:
 b171cbf3692dd8583e1ff74b6b58185376577e0f 1916 ca-certificates-java_20190214.dsc
 bbbd4b1e732273666b08d1842b558740ee6dfd0a 16840 
ca-certificates-java_20190214.tar.xz
 c47fd0a6bd2f845b20183ff287105ce1f1c722fc 12721 
ca-certificates-java_20190214_amd64.buildinfo
Checksums-Sha256:
 4b3deb354f65f5b5da9e6aaa60d651953ca7b82bed1720274dd8b84d7748316e 1916 
ca-certificates-java_20190214.dsc
 1037ff64b262c401b7e63188ec86d0b23db52126262a1e1917dcd63f9c85ee5d 16840 
ca-certificates-java_20190214.tar.xz
 c89022a7361b707745064add5be5a09753ca631baaec48d4285832bde8f6d88b 12721 
ca-certificates-java_20190214_amd64.buildinfo
Files:
 de225649a9e2b258f44674e43bee3022 1916 java optional 
ca-certificates-java_20190214.dsc
 be091ded7da17661b7859b779b91433a 16840 java optional 
ca-certificates-java_20190214.tar.xz
 22b02dcf03d9527a62d5615b67ebed0a 12721 java optional 
ca-certificates-java_20190214_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlxl3OlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkwG0P/RTH5d8iBKknF1u+IDs2xYq6cg6f4H9TuIXt
cnZmhcaz6x1xP17DC85lgeEYnX3N0lTDkNZSqxkhkM5nRcM1KScdLVovQBlQmMSy
lWx4p3roxImdM0HgUgq8DmFBSbC3wNmG0nKNCDc/JRIHROmWEM+oKbs3R632itw4
cA0qhEHEXY5xcijnvg7EymtP6zyjAo6rzvd7vnTKDQEyDO86mcjNG7HAanAxUr/D
d+3f06cwhX783vQ7lGE5cijhipZR8MDdqpoUGQWUl7d7wREM0ghVJHfePMI6HLKQ
lMF8RYOVGTDkJrX4juLn3odo3dEdtR2ec9nvgLrY7O9yTQ2MJwptwnY1lGozHKNb
YrGIWnYCNTttzDse095UgddYbLiINSiM+JZy/WsS2IjhLgDWRzveceES+sz8SmbT
DJ6x3yq7gAagskFlLXOgZgYo1+TAan719sLNZWXc3gF/RIr7go6V9TgIwFpx1nrb
nAc9oDFpGu3BAHHT/YxQa2GUwwQ/bExiyIrwhsxNDT73zv6zrRFxqYek/IblbUR8
gEappKcr3e1dDUEX4Jf3edPUDxZm9FqQKUqo9mWyY+If5pg5lwrL4LZE+TpDTTjP
ePP+w9vMa5U4C2uqdoBo91Pf7B34wtYTeweDKJ4y9i7fEFYlKJVD8GEH+lOdlzbc
/vQOKOc1
=V5wZ
-END PGP SIGNATURE End Message ---

Bug#917739: lucene-solr: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "svnversion" (in directory "/<>/lucene-solr-3.6.2+dfsg/solr/contrib/dataimporthandler"): error=

[Markus Koschany]

On Sat, 29 Dec 2018 23:26:49 +0100 Lucas Nussbaum  wrote:
> Source: lucene-solr
> Version: 3.6.2+dfsg-16
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
> Usertags: ftbfs-20181229 ftbfs-buster
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

[...]

This issue is related to the recent javadoc change. I am opting for the
removal of liblucene3-java-doc right now. That "solves" the build
failure but there is another one later one, something about

java.io.FileNotFoundException: Could not resolve XML resource [null]
with public ID [-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN],
system ID [http://java.sun.com/dtd/web-app_2_3.dtd] and base URI
[file:/build/lucene-solr-3.6.2+dfsg/solr/webapp/web/WEB-INF/web.xml] to
a known, local entity.

I'm just looking into it.





signature.asc
Description: OpenPGP digital signature

Bug#922350: udevd does not start after reboot

[Felipe Sateler]

On Thu, Feb 14, 2019 at 6:39 PM Vincent Danjean  wrote:

> Package: udev
> Version: 240-5
> Severity: serious
> Justification: render the system unbootable
>
>   Hi,
>
>   After a major upgrade to unstable (the system was not upgraded
> during a few months) and after a reboot, udevd refuse to start. This leads
> to
> LVs (of LVM) to not appear in /dev (but the LV where the root FS is
> stored). I
> was offered to type the root password to go to an emergency shell.
>
>   Trying to restart the systemd-udevd service failed.
> Looking to log with journalctl give me very few info:
> févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager...
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process
> exited, code=killed, status=31/SYS
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with
> result 'signal'.
> févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device
> Manager.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no
> hold-off time (RestartSec=0), scheduli
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled
> restart job, restart counter is at 1.
> févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager.
> févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager...
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process
> exited, code=killed, status=31/SYS
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with
> result 'signal'.
> févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device
> Manager.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no
> hold-off time (RestartSec=0), scheduli
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled
> restart job, restart counter is at 2.
> févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager.
> févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager...
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process
> exited, code=killed, status=31/SYS
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with
> result 'signal'.
> févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device
> Manager.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no
> hold-off time (RestartSec=0), scheduli
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled
> restart job, restart counter is at 3.
> févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager.
> févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager...
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process
> exited, code=killed, status=31/SYS
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with
> result 'signal'.
> févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device
> Manager.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no
> hold-off time (RestartSec=0), scheduli
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled
> restart job, restart counter is at 4.
> févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager.
> févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager...
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process
> exited, code=killed, status=31/SYS
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with
> result 'signal'.
> févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device
> Manager.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no
> hold-off time (RestartSec=0), scheduli
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled
> restart job, restart counter is at 5.
> févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Start request
> repeated too quickly.
> févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with
> result 'signal'.
> févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device
> Manager.
>
>   Then, I looked at the service file and tried to manually start
> systemd-udevd. It seems to work. So, I stopped it and
> comment-out most of systemd features in the service file. In
> /lib/systemd/system/systemd-udevd.service I have now:
> #PrivateMounts=yes
> #MemoryDenyWriteExecute=yes
> #RestrictRealtime=yes
> #RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
> #SystemCallArchitectures=native
> #LockPersonality=yes
> #IPAddressDeny=any
>
>   It worked (systemd-udevd started with systemctl and also after
> a reboot)
>
>   I did not try to find the specific feature that was problematic
> as I quickly needed the computer for (long) production. If you need
> more info or tests, I should be able to reboot the system in a few
> days.
>
>   Regards,
> Vincent
>
> -- Package-specific info:
>
> -- System Information:
> 

Bug#873016: A way to fix node-lodash-packages ?

[Xavier]

https://salsa.debian.org/js-team/node-lodash/blob/master/.travis.yml
shows the way to build lodash-packages from lodash :

$ yarn
$ git clone --depth=10 --branch=master
git://github.com/lodash/lodash-cli ./node_modules/lodash-cli
$ mkdir -p ./node_modules/lodash-cli/node_modules/lodash
$ cd $_
$ cp ../../../../lodash.js ./lodash.js
$ cp ../../../../package.json ./package.json
$ cd ../../
$ npm i --production
$ cd ../../
$ node ./node_modules/lodash-cli/bin/lodash core \
   -o ./dist/lodash.core.js
$ npm run build

... But last step does not work...

Bug#864657: Bug #864657 in ca-certificates-java marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #864657 in ca-certificates-java 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/ca-certificates-java/commit/463e86236ea3f64f522e219e426ecf164a6c7000


ca-certificates-java: Depend on default-jre-headless to avoid a circular 
dependency on

a specific OpenJDK package.

Closes: #864657


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/864657

Processed: Bug #864657 in ca-certificates-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #864657 [ca-certificates-java] ca-certificates-java has circular Depends on 
openjdk-8-jre-headless
Added tag(s) pending.

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

Bug#922027: python-django: Django security release

[Chris Lamb]

Hi Moritz,

> > Security team, may I upload this to stretch-security? Diff attached.
> 
> This doesn't warrant a DSA, let's postpone this until more severe comes up.

Noted. Can you update data/CVE/list?


Regards,

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

Bug#922027: python-django: Django security release

[Moritz Mühlenhoff]

On Mon, Feb 11, 2019 at 03:07:36PM +0100, Chris Lamb wrote:
> [Adding t...@security.debian.org to CC]
> 
> Chris Lamb wrote:
> 
> > retitle 922027 CVE-2019-6975: Memory exhaustion in 
> > django.utils.numberformat.format()
> > severity 922027 grave
> > found 922027 1:1.10.7-2+deb9u3
> > tags 922027 + security
> > thanks
> 
> Security team, may I upload this to stretch-security? Diff attached.

This doesn't warrant a DSA, let's postpone this until more severe comes up.

Cheers,
Moritz

Bug#922133: marked as done (src:marionnet: build-depends/depends on cruft packages)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 22:14:41 +0100
with message-id <20190214211441.gb25...@seneca.home.org>
and subject line Re: Bug#922133: src:marionnet: build-depends/depends on cruft 
packages
has caused the Debian Bug report #922133,
regarding src:marionnet: build-depends/depends on cruft packages
to be marked as done.

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

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


-- 
922133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:marionnet
Version: 0.90.6+bzr508-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

liblablgtksourceview2-ocaml and liblablgtksourceview2-ocaml-dev are no longer
built by lablgtk2 and will be removed.  Marionnet build-depends on
liblablgtksourceview2-ocaml-dev and as a result depends on
liblablgtksourceview2-ocaml, which lablgtk2 no longer provides.

The lablgtk2 maintainers have been asked to put it back, but in the mean time,
it's a serious issue with this package.  You may want to take it up with them.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677

Scott K
--- End Message ---
--- Begin Message ---
closing this bug as liblablgtksourceview2-ocaml[-dev] is back in sid
with the upload of lablgtk 2.18.5+dfsg-3.

-Ralf.--- End Message ---

Bug#922286: marked as done (python-apptools-doc: missing Breaks+Replaces: python-apptools (<< 4.4.0))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 21:04:26 +
with message-id 
and subject line Bug#922286: fixed in python-apptools 4.4.0-2
has caused the Debian Bug report #922286,
regarding python-apptools-doc: missing Breaks+Replaces: python-apptools (<< 
4.4.0)
to be marked as done.

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

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


-- 
922286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-apptools-doc
Version: 4.4.0-1
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 .../python-apptools-doc_4.4.0-1_all.deb ...   

   Unpacking 
python-apptools-doc (4.4.0-1) ...   

   dpkg: error processing archive 
/var/cache/apt/archives/python-apptools-doc_4.4.0-1_all.deb (--unpack): 

   trying to overwrite 
'/usr/share/doc/python-apptools/examples/appscripting/example.py', which is 
also in package python-apptools 4.3.0-1 
dpkg-deb: error: subprocess paste was 
killed by signal (Broken pipe)  

   Errors were encountered while processing:

 
/var/cache/apt/archives/python-apptools-doc_4.4.0-1_all.deb 

  

cheers,

Andreas


python-apptools=4.3.0-1_python-apptools-doc=4.4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-apptools
Source-Version: 4.4.0-2

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

Debian distribution maintenance software
pp.
Stewart Ferguson  (supplier of updated python-apptools 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, 14 Feb 2019 21:19:20 +0100
Source: python-apptools
Architecture: source
Version: 4.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Stewart Ferguson 
Closes: 922286
Changes:
 python-apptools (4.4.0-2) unstable; urgency=medium
 .
   * Adding Breaks and Replaces to new doc package (Closes: #922286)
Checksums-Sha1:
 8c446aefbae0ecee4066867e951fbe4a633a86c4 2448 python-apptools_4.4.0-2.dsc
 a399c649ca82103f065d23ca142c9beeb3a1d0ef 7140 
python-apptools_4.4.0-2.debian.tar.xz
 4cc46a2abc02fdeef60e14d8d23f05eb100641b7 8798 
python-apptools_4.4.0-2_amd64.buildinfo
Checksums-Sha256:
 a3e7456a325a64a94fdf137b95bc7b8fb733ab64d432d07d7a43c1e85d025508 2448 
python-apptools_4.4.0-2.dsc
 6bc0ffb93b1f4b80956783066f800770d1e2479c85dd9a62594a7a8b9aa8f98b 7140 
python-apptools_4.4.0-2.debian.tar.xz
 41413c9e78b2d3eb26d80265609d37c5d11aa91cbab44ae777e57c05937ca9d1 8798 
python-apptools_4.4.0-2_amd64.buildinfo
Files:
 965379de61b22974886e2d642f6c02f5 2448 python optional 
python-apptools_4.4.0-2.dsc
 38f256c22ccb640a93a67741f424512c 7140 python 

Bug#922346: eog: Opened an image and my display server crashed

[Michel Le Bihan]

Le jeudi 14 février 2019 à 20:31 +, Simon McVittie a écrit :
> Control: reassign -1 libgl1-mesa-dri
> Control: tags -1 + moreinfo
> 
> On Thu, 14 Feb 2019 at 21:18:42 +0100, Michel Le Bihan wrote:
> > I opened a png file in eog and my display server crashed.
> 
> eog shouldn't be able to cause this, even if it wanted to, so this is
> a bug in the display server or some library it uses.
> 
> From the backtrace you provided, I think this is most likely to be an
> assertion failure in /usr/lib/x86_64-linux-gnu/dri/i965_dri.so, so
> I'm
> reassigning this.
> 
> The Mesa maintainers will want to know more details of your system.
> The output of `reportbug --template libgl1-mesa-dri` would presumably
> be useful information.
> 
> Was the file that you opened in eog particularly large, or otherwise
> unusual?

No. It was only 1,5MB. It didn't appear to be unusual in any way, but I
don't know if it was a fully valid PNG file.

Michel Le Bihan

Processed: Taking ownership of python-apptools bug

[Debian Bug Tracking System]

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

> owner 922286 !
Bug #922286 [python-apptools-doc] python-apptools-doc: missing Breaks+Replaces: 
python-apptools (<< 4.4.0)
Owner recorded as Stewart Ferguson .
> thank you
Stopping processing here.

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

Processed: Re: Bug#922346: eog: Opened an image and my display server crashed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgl1-mesa-dri
Bug #922346 [eog] eog: Opened an image and my display server crashed
Bug reassigned from package 'eog' to 'libgl1-mesa-dri'.
No longer marked as found in versions eog/3.28.4-2.
Ignoring request to alter fixed versions of bug #922346 to the same values 
previously set
> tags -1 + moreinfo
Bug #922346 [libgl1-mesa-dri] eog: Opened an image and my display server crashed
Added tag(s) moreinfo.

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

Bug#922346: eog: Opened an image and my display server crashed

[Simon McVittie]

Control: reassign -1 libgl1-mesa-dri
Control: tags -1 + moreinfo

On Thu, 14 Feb 2019 at 21:18:42 +0100, Michel Le Bihan wrote:
> I opened a png file in eog and my display server crashed.

eog shouldn't be able to cause this, even if it wanted to, so this is
a bug in the display server or some library it uses.

>From the backtrace you provided, I think this is most likely to be an
assertion failure in /usr/lib/x86_64-linux-gnu/dri/i965_dri.so, so I'm
reassigning this.

The Mesa maintainers will want to know more details of your system.
The output of `reportbug --template libgl1-mesa-dri` would presumably
be useful information.

Was the file that you opened in eog particularly large, or otherwise
unusual?

Thanks,
smcv

> Here is the relevant part of my syslog:
> 
> Feb 14 20:44:45 debian org.gnome.Shell.desktop[1414]: Window manager warning:
> Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for
> 0x187 (Visionneur)
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: Xwayland:
> src/intel/genxml/gen7_pack.h:72: __gen_uint: Assertion `v <= max' failed.
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) Backtrace:
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 0: 
> /usr/bin/Xwayland
> (OsLookupColor+0x139) [0x55b8e2f27e09]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 1:
> /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fba70a3372f]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 2:
> /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x10b) [0x7fba708978bb]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 3:
> /lib/x86_64-linux-gnu/libc.so.6 (abort+0x121) [0x7fba70882535]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) unw_get_proc_name
> failed: no unwind info found [-10]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 4:
> /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fba70882400]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 5:
> /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) [0x7fba708900f2]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 6:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_nouveau_vieux+0x416573) [0x7fba6fb6c503]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 7:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_nouveau_vieux+0x416dd5) [0x7fba6fb6cd95]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 8:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_i915+0x136b7b) [0x7fba6f402d8b]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 9:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_i915+0x1370e7) [0x7fba6f403ab7]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 10:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_i915+0x12f041) [0x7fba6f3f3711]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 11:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_i915+0x11a2dc) [0x7fba6f3c952c]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 12:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_nouveau_vieux+0x1ccc7a) [0x7fba6f6d929a]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 13:
> /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
> (__driDriverGetExtensions_nouveau_vieux+0x1ccfea) [0x7fba6f6d999a]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 14:
> /usr/bin/Xwayland (glamor_create_gc+0xd535) [0x55b8e2df1a05]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 15:
> /usr/bin/Xwayland (DamageRegionAppend+0x19f8) [0x55b8e2e98eb8]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 16:
> /usr/bin/Xwayland (glamor_pixmap_exchange_fbos+0x7b7) [0x55b8e2deef57]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 17:
> /usr/bin/Xwayland (glamor_pixmap_exchange_fbos+0x67e) [0x55b8e2dee9be]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 18:
> /usr/bin/Xwayland (AddTraps+0x3551) [0x55b8e2e8aad1]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 19:
> /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55b8e2ef1e6e]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 20:
> /usr/bin/Xwayland (InitFonts+0x3b6) [0x55b8e2ef5df6]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 21:
> /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fba7088409b]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 22:
> /usr/bin/Xwayland (_start+0x2a) [0x55b8e2dc71ea]
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: Fatal server error:
> Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) Caught signal 6
> (Aborted). Server aborting
> Feb 14 20:44:46 

Bug#922286: Bug #922286 in python-apptools marked as pending

[Stewart Ferguson]

Control: tag -1 pending

Hello,

Bug #922286 in python-apptools 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/python-team/modules/python-apptools/commit/c721dd14b0b5b5f3db5aafdf3517eb0ce525f068


Adding Breaks and Replaces to new doc package (Closes: #922286)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/922286

Processed: Bug #922286 in python-apptools marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #922286 [python-apptools-doc] python-apptools-doc: missing Breaks+Replaces: 
python-apptools (<< 4.4.0)
Added tag(s) pending.

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

Bug#922346: eog: Opened an image and my display server crashed

[Michel Le Bihan]

Package: eog
Version: 3.28.4-2+b1
Severity: critical
Justification: breaks the whole system

I opened a png file in eog and my display server crashed. Here is the relevant
part of my syslog:

Feb 14 20:44:45 debian org.gnome.Shell.desktop[1414]: Window manager warning:
Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for
0x187 (Visionneur)
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: Xwayland:
src/intel/genxml/gen7_pack.h:72: __gen_uint: Assertion `v <= max' failed.
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) Backtrace:
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 0: /usr/bin/Xwayland
(OsLookupColor+0x139) [0x55b8e2f27e09]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fba70a3372f]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 2:
/lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x10b) [0x7fba708978bb]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 3:
/lib/x86_64-linux-gnu/libc.so.6 (abort+0x121) [0x7fba70882535]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) unw_get_proc_name
failed: no unwind info found [-10]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 4:
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fba70882400]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 5:
/lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) [0x7fba708900f2]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_nouveau_vieux+0x416573) [0x7fba6fb6c503]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 7:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_nouveau_vieux+0x416dd5) [0x7fba6fb6cd95]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 8:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_i915+0x136b7b) [0x7fba6f402d8b]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 9:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_i915+0x1370e7) [0x7fba6f403ab7]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 10:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_i915+0x12f041) [0x7fba6f3f3711]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 11:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_i915+0x11a2dc) [0x7fba6f3c952c]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 12:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_nouveau_vieux+0x1ccc7a) [0x7fba6f6d929a]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 13:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(__driDriverGetExtensions_nouveau_vieux+0x1ccfea) [0x7fba6f6d999a]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 14:
/usr/bin/Xwayland (glamor_create_gc+0xd535) [0x55b8e2df1a05]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 15:
/usr/bin/Xwayland (DamageRegionAppend+0x19f8) [0x55b8e2e98eb8]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 16:
/usr/bin/Xwayland (glamor_pixmap_exchange_fbos+0x7b7) [0x55b8e2deef57]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 17:
/usr/bin/Xwayland (glamor_pixmap_exchange_fbos+0x67e) [0x55b8e2dee9be]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 18:
/usr/bin/Xwayland (AddTraps+0x3551) [0x55b8e2e8aad1]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 19:
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55b8e2ef1e6e]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 20:
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55b8e2ef5df6]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 21:
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fba7088409b]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) 22:
/usr/bin/Xwayland (_start+0x2a) [0x55b8e2dc71ea]
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: Fatal server error:
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE) Caught signal 6
(Aborted). Server aborting
Feb 14 20:44:46 debian org.gnome.Shell.desktop[1414]: (EE)



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 
'stable')
Architecture: amd64 (x86_64)

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

Versions of packages eog depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-peas-1.0  1.22.0-4
ii  gsettings-desktop-schemas 

Bug#922345: msmtp: CVE-2019-8337

[Salvatore Bonaccorso]

Source: msmtp
Version: 1.8.2-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for msmtp.

CVE-2019-8337[0]:
| In msmtp 1.8.2, when tls_trust_file has its default configuration,
| certificate-verification results are not properly checked.

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-8337
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8337
[1] https://marlam.de/msmtp/news/
[2] 
https://gitlab.marlam.de/marlam/msmtp/commit/a81d0a5126304f9f8b29a75d058044dc67d07663

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#922297: marked as done (rxvt-unicode: *blink* *blink* *blink*)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 17:50:11 +
with message-id 
and subject line Bug#922297: fixed in rxvt-unicode 9.22-6
has caused the Debian Bug report #922297,
regarding rxvt-unicode: *blink* *blink* *blink*
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.)


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

Package: rxvt-unicode
Version: 9.22-5
Severity: grave
Justification: makes my head hurt

The terminal screen blinks all the time.


-- System Information:
Architecture: i386

Versions of packages rxvt-unicode depends on:
ii  libc6 2.28-7
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-20
ii  libgdk-pixbuf2.0-02.38.0+dfsg-7
ii  libglib2.0-0  2.58.3-1
ii  libperl5.28   5.28.1-4
ii  libstartup-notification0  0.12-6
ii  libx11-6  2:1.6.7-1
ii  libxft2   2.3.2-2
ii  libxrender1   1:0.9.10-1
ii  base-passwd   3.5.46
ii  ncurses-base  6.1+20181013-2
ii  ncurses-term  6.1+20181013-2

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: rxvt-unicode
Source-Version: 9.22-6

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

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated rxvt-unicode 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, 14 Feb 2019 12:00:54 -0500
Source: rxvt-unicode
Binary: aterm aterm-ml rxvt rxvt-ml rxvt-unicode rxvt-unicode-256color 
rxvt-unicode-dbgsym rxvt-unicode-lite
Architecture: source all amd64
Version: 9.22-6
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description:
 aterm  - dummy transitional package for rxvt-unicode
 aterm-ml   - dummy transitional package for rxvt-unicode
 rxvt   - dummy transitional package for rxvt-unicode
 rxvt-ml- dummy transitional package for rxvt-unicode
 rxvt-unicode - RXVT-like terminal emulator with Unicode and 256-color support
 rxvt-unicode-256color - dummy transitional package for rxvt-unicode
 rxvt-unicode-lite - dummy transitional package for rxvt-unicode
Closes: 922268 922289 922297 922298 922299
Changes:
 rxvt-unicode (9.22-6) unstable; urgency=medium
 .
   * Revert the 24bit colour patch. Though no issues seem to arise when using
 the default resource values, it seems to cause many issues if changes are
 made to resources related to colour.
 (Closes: #922268, #922289, #922297, #922298, #922299)
Checksums-Sha1:
 106b7efc3679e3bd099c57728faff1096e95d5fb 3511 rxvt-unicode_9.22-6.dsc
 103fbc747cfa0da63ebcce8897bca692591a3cdf 33236 
rxvt-unicode_9.22-6.debian.tar.xz
 635a7df870c985cf607eea73b892f627299da69b 52680 aterm-ml_9.22-6_all.deb
 457824a5d0cd1942e270a0181b7b1390e4428cd5 52676 aterm_9.22-6_all.deb
 e0decd50b253e8877de62499655ca9de72ecb5fb 52636 
rxvt-ml_2.7.10-7.1+urxvt9.22-6_all.deb
 a2c7445c6841861aedcf5b04749bb4f830ff5b02 52316 
rxvt-unicode-256color_9.22-6_all.deb
 572ac97bcf3d486b742abb4aeaba91caa2c1f917 2451848 
rxvt-unicode-dbgsym_9.22-6_amd64.deb
 48c12ffc22aab9cdefe8f4a4f9d9df3b441f6009 52312 rxvt-unicode-lite_9.22-6_all.deb
 87dbef83a879bbc5157851e76eb5fdeb4d2a59dd 13556 
rxvt-unicode_9.22-6_amd64.buildinfo
 06af8b7ec9b6bcefc08d5a79ab8b4c192656a468 776580 rxvt-unicode_9.22-6_amd64.deb
 9515369ba3a5c5934491bd2e41a9830b7975bb3d 52776 
rxvt_2.7.10-7.1+urxvt9.22-6_all.deb
Checksums-Sha256:
 58ed5d35c082479e6e7a6ca1668228b580e32f923a0120db01c4a229625fbf5d 3511 
rxvt-unicode_9.22-6.dsc
 3a1e92a6126ed206ebe66fc96d38411684d2c828a172667cc93006532cfee375 33236 
rxvt-unicode_9.22-6.debian.tar.xz
 b48b511828dbdb32679d0a901f1f229c79dbc195d6028651d18d37435383554b 52680 
aterm-ml_9.22-6_all.deb
 bd6de4ecc3e5715b1d0ae116a98c4c4b26055c58099a5bbe059605948ebdeb86 52676 
aterm_9.22-6_all.deb
 50a2b1576c91016385bd43f7bae8fe1b27cf9d4463b32fda39929aef5dfeae05 52636 

Bug#892661: marked as done (node-static-extend: FTBFS and Debci failure)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 17:49:17 +
with message-id 
and subject line Bug#892661: fixed in node-static-extend 0.1.2-2
has caused the Debian Bug report #892661,
regarding node-static-extend: FTBFS and Debci failure
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.)


-- 
892661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-static-extend
Version: 0.1.2-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes node-static-extend FTBFS and Debci fail:

https://ci.debian.net/packages/n/node-static-extend/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-static-extend.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-static-extend.html

...
  9 passing (18ms)
  2 failing

  1) extend
   should add `Parent.prototype` to `Ctor` instances as `_parent_`:

  AssertionError [ERR_ASSERTION]: { configurable: true,
  set: [Function: set],
  get: [Function: get] } deepEqual Parent { a: [Function], b: [Function], c: 
[Function] }
  + expected - actual

   {
  -  "configurable": true
  -  "get": [Function]
  -  "set": [Function]
  +  "a": [Function]
  +  "b": [Function]
  +  "c": [Function]
   }
  
  at Context. (test.js:38:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  2) extend
   should access `Parent` methods through `_parent_`:
 TypeError: this._parent_.upper is not a function
  at Ctor.instance.upper (test.js:58:28)
  at Context. (test.js:60:27)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: node-static-extend
Source-Version: 0.1.2-2

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-static-extend 
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, 14 Feb 2019 18:00:15 +0100
Source: node-static-extend
Binary: node-static-extend
Architecture: source
Version: 0.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 892661
Description: 
 node-static-extend - Adds a static `extend` method to a class, to simplify 
inheritance
Changes:
 node-static-extend (0.1.2-2) unstable; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 11
   * Declare 

Processed: bug 922333 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=128513

[Debian Bug Tracking System]

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

> forwarded 922333 https://rt.cpan.org/Ticket/Display.html?id=128513
Bug #922333 [libmail-message-perl] libmail-message-perl 3.008 breaks (the 
testsuite of) libmail-box-perl
Ignoring request to change the forwarded-to-address of bug#922333 to the same 
value
> thanks
Stopping processing here.

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

Bug#922287: marked as done (msxpertsuite-massxpert: missing Breaks+Replaces: massxpert)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 17:35:05 +
with message-id 
and subject line Bug#922287: fixed in msxpertsuite 5.8.6-1
has caused the Debian Bug report #922287,
regarding msxpertsuite-massxpert: missing Breaks+Replaces: massxpert
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', 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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../msxpertsuite-massxpert_5.8.5-1_amd64.deb ...  

   Unpacking 
msxpertsuite-massxpert (5.8.5-1) ...

   dpkg: error processing archive 
/var/cache/apt/archives/msxpertsuite-massxpert_5.8.5-1_amd64.deb (--unpack):

   trying to overwrite '/usr/bin/massxpert', which is also 
in package massxpert 3.6.1-1

dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

 Errors were encountered 
while processing:   

  
/var/cache/apt/archives/msxpertsuite-massxpert_5.8.5-1_amd64.deb

  


cheers,

Andreas


massxpert=3.6.1-1_msxpertsuite-massxpert=5.8.5-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: msxpertsuite
Source-Version: 5.8.6-1

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated msxpertsuite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Feb 2019 17:08:52 +0100
Source: msxpertsuite
Binary: msxpertsuite msxpertsuite-massxpert msxpertsuite-massxpert-data-doc 
msxpertsuite-minexpert msxpertsuite-minexpert-data-doc
Architecture: source
Version: 5.8.6-1
Distribution: unstable
Urgency: low
Maintainer: The Debichem Group 
Changed-By: Filippo Rusconi 
Description:
 msxpertsuite - mass spectrometry software suite - metapackage
 msxpertsuite-massxpert - mass spectrometry software suite - massXpert
 msxpertsuite-massxpert-data-doc - mass spectrometry software suite - massXpert 
- data and doc
 msxpertsuite-minexpert - mass spectrometry software suite - mineXpert
 msxpertsuite-minexpert-data-doc - mass spectrometry software suite - mineXpert 
- data and doc
Closes: 922287
Changes:
 msxpertsuite (5.8.6-1) unstable; urgency=low
 .
   * Reinstate partially all the conflicts/breaks/replaces statements for the
 mspxertsuite-massxpert binary package. This ensures that upgrade of
 massxpert from stable's version to 

Processed: bug 922333 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=128513

[Debian Bug Tracking System]

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

> forwarded 922333 https://rt.cpan.org/Ticket/Display.html?id=128513
Bug #922333 [libmail-message-perl] libmail-message-perl 3.008 breaks (the 
testsuite of) libmail-box-perl
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=128513'.
> thanks
Stopping processing here.

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

Processed: limit source to rxvt-unicode, tagging 922268, tagging 922289, tagging 922297, tagging 922299 ...

[Debian Bug Tracking System]

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

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

> tags 922268 + pending
Bug #922268 [rxvt-unicode] rxvt-unicode: tabbed extension segfaults
Added tag(s) pending.
> tags 922289 + pending
Bug #922289 [rxvt-unicode] rxvt-unicode: missing bright colors (and cursor 
color, too)
Added tag(s) pending.
> tags 922297 + pending
Bug #922297 [rxvt-unicode] rxvt-unicode: *blink* *blink* *blink*
Added tag(s) pending.
> tags 922299 + pending
Bug #922299 [rxvt-unicode] rxvt-unicode: laggy cursor
Added tag(s) pending.
> tags 922298 + pending
Bug #922298 [rxvt-unicode] rxvt-unicode: invisible selection
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#922333: libmail-message-perl 3.008 breaks (the testsuite of) libmail-box-perl

[gregor herrmann]

Package: libmail-message-perl
Version: 3.008-1
Severity: serious
Tags: upstream sid
Justification: breaks other package

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, libmail-message-perl 3.008-1 breaks
libmail-box-perl's test suite (which causes a build failure):

https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmail-box-perl/1925858/log.gz

Also locally:

#   Failed test 'begin 1'
#   at t/100mbox-read.t line 73.
#  got: 2973
# expected: 2974
#   Failed test 'begin 2'
#   at t/100mbox-read.t line 73.
#  got: 6953
# expected: 6954
#   Failed test 'begin 3'
#   at t/100mbox-read.t line 73.
#  got: 10871
# expected: 10872
#   Failed test 'begin 4'
#   at t/100mbox-read.t line 73.
#  got: 13775
# expected: 13776
#   Failed test 'begin 5'
#   at t/100mbox-read.t line 73.
#  got: 17767
# expected: 17768
#   Failed test 'begin 6'
#   at t/100mbox-read.t line 73.
#  got: 22665
# expected: 22666
#   Failed test 'begin 7'
#   at t/100mbox-read.t line 73.
#  got: 29863
# expected: 29864
#   Failed test 'begin 8'
#   at t/100mbox-read.t line 73.
#  got: 38796
# expected: 38797
#   Failed test 'begin 9'
#   at t/100mbox-read.t line 73.
#  got: 40538
# expected: 40539
#   Failed test 'begin 10'
#   at t/100mbox-read.t line 73.
#  got: 44810
# expected: 44811
#   Failed test 'begin 11'
#   at t/100mbox-read.t line 73.
#  got: 46327
# expected: 46328
#   Failed test 'begin 12'
#   at t/100mbox-read.t line 73.
#  got: 49339
# expected: 49340
#   Failed test 'begin 13'
#   at t/100mbox-read.t line 73.
#  got: 52673
# expected: 52674
#   Failed test 'begin 14'
#   at t/100mbox-read.t line 73.
#  got: 54352
# expected: 54353
#   Failed test 'begin 15'
#   at t/100mbox-read.t line 73.
#  got: 57547
# expected: 57548
#   Failed test 'begin 16'
#   at t/100mbox-read.t line 73.
#  got: 59213
# expected: 59214
#   Failed test 'begin 17'
#   at t/100mbox-read.t line 73.
#  got: 61534
# expected: 61535
#   Failed test 'begin 18'
#   at t/100mbox-read.t line 73.
#  got: 65036
# expected: 65037
#   Failed test 'begin 19'
#   at t/100mbox-read.t line 73.
#  got: 66386
# expected: 66387
#   Failed test 'begin 20'
#   at t/100mbox-read.t line 73.
#  got: 68334
# expected: 68335
#   Failed test 'begin 21'
#   at t/100mbox-read.t line 73.
#  got: 70568
# expected: 70569
#   Failed test 'begin 22'
#   at t/100mbox-read.t line 73.
#  got: 71836
# expected: 71837
#   Failed test 'begin 23'
#   at t/100mbox-read.t line 73.
#  got: 73183
# expected: 73184
#   Failed test 'begin 24'
#   at t/100mbox-read.t line 73.
#  got: 74555
# expected: 74556
#   Failed test 'begin 25'
#   at t/100mbox-read.t line 73.
#  got: 77122
# expected: 77123
#   Failed test 'begin 26'
#   at t/100mbox-read.t line 73.
#  got: 82226
# expected: 82227
#   Failed test 'begin 27'
#   at t/100mbox-read.t line 73.
#  got: 84092
# expected: 84093
#   Failed test 'begin 28'
#   at t/100mbox-read.t line 73.
#  got: 87420
# expected: 87421
#   Failed test 'begin 29'
#   at t/100mbox-read.t line 73.
#  got: 89463
# expected: 89464
#   Failed test 'begin 30'
#   at t/100mbox-read.t line 73.
#  got: 90624
# expected: 90625
#   Failed test 'begin 31'
#   at t/100mbox-read.t line 73.
#  got: 93511
# expected: 93512
#   Failed test 'begin 32'
#   at t/100mbox-read.t line 73.
#  got: 96480
# expected: 96481
#   Failed test 'begin 33'
#   at t/100mbox-read.t line 73.
#  got: 99700
# expected: 99701
#   Failed test 'begin 34'
#   at t/100mbox-read.t line 73.
#  got: 102318
# expected: 102319
#   Failed test 'begin 35'
#   at t/100mbox-read.t line 73.
#  got: 102710
# expected: 102711
#   Failed test 'begin 36'
#   at t/100mbox-read.t line 73.
#  got: 103354
# expected: 103355
#   Failed test 'begin 37'
#   at t/100mbox-read.t line 73.
#  got: 105260
# expected: 105261
#   Failed test 'begin 38'
#   at t/100mbox-read.t line 73.
#  got: 117599
# expected: 117600
#   Failed test 'begin 39'
#   at t/100mbox-read.t line 73.
#  got: 120412
# expected: 120413
#   Failed test 'begin 40'
#   at t/100mbox-read.t line 73.
#  got: 123699
# expected: 123700
#   Failed test 'begin 41'
#   at t/100mbox-read.t line 73.
#  got: 125122
# expected: 125123
#   Failed test 'begin 42'
#   at t/100mbox-read.t line 73.
#  got: 127335
# expected: 127336
#   Failed test 'begin 43'
#   at t/100mbox-read.t line 73.
#  got: 128970
# expected: 128971
#   Failed test 'begin 44'
#   at t/100mbox-read.t line 73.
#  got: 132533
# expected: 132534
#   

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

[Ryan Kavanagh]

On Thu, Feb 14, 2019 at 06:05:03PM +0100, Jakub Wilk wrote:
> I can reproduce the issue without any custom settings or extensions
> The effect is quite subtle, so I can imagine some people might not
> notice it.

Even after clearing out all resources, I'm unable to reproduce it on
either of my monitors. I'll revert the patch for now and hopefully it
won't be an issue whenever the next upstream release containing it gets
released.

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Processed: [bts-link] source package src:borgbackup

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:borgbackup
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #922080 (http://bugs.debian.org/922080)
> # Bug title: borgbackup: fuse mount exposes backup to unauthorized users
> #  * https://github.com/borgbackup/borg/issues/3903
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 922080 + fixed-upstream
Bug #922080 [src:borgbackup] borgbackup: fuse mount exposes backup to 
unauthorized users
Added tag(s) fixed-upstream.
> usertags 922080 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package systemd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #918764 (http://bugs.debian.org/918764)
> # Bug title: udev: "udevadm control --reload-rules" kills all processes 
> except init
> #  * https://github.com/systemd/systemd/issues/11645
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 918764 + fixed-upstream
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Added tag(s) fixed-upstream.
> usertags 918764 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 918764 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#879642: fixed in simple-cdd 0.6.6

[Vagrant Cascadian]

On 2019-02-11, Alexandre Belgrand wrote:
> The bug does not seem to be fixed.

While similar in end result, I believe the bug you are experiencing is
more similar to:

  https://bugs.debian.org/919572


> I am still getting this error:
>
> 2019-02-11 15:45:44 ERROR verify gpg signature exited with code 2
> 2019-02-11 15:45:44 ERROR Last 5 lines of standard error:
> 2019-02-11 15:45:44 ERROR verify gpg signature:
> gpg:avec la clef RSA
> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500
> 2019-02-11 15:45:44 ERROR verify gpg signature: gpg: Bonne signature de
> « Debian Stable Release Key (9/stretch) <
> debian-rele...@lists.debian.org> » [inconnu]
> 2019-02-11 15:45:44 ERROR verify gpg signature: gpg: Attention : cette
> clef n'est pas certifiée avec une signature de confiance.
> 2019-02-11 15:45:44 ERROR verify gpg signature: gpg: Rien
> n'indique que la signature appartient à son propriétaire.
> 2019-02-11 15:45:44 ERROR verify gpg signature: Empreinte de clef
> principale : 067E 3C45 6BAE 240A CEE8  8F6F EF0F 382A 1A7B 6500
> Traceback (most recent call last):
>   File "/usr/bin/build-simple-cdd", line 678, in 
> scdd.build_mirror()
>   File "/usr/bin/build-simple-cdd", line 290, in build_mirror
> self.run_tool("mirror", tool)
>   File "/usr/bin/build-simple-cdd", line 387, in run_tool
> tool.run()
>   File "/usr/lib/python3/dist-
> packages/simple_cdd/tools/mirror_download.py", line 107, in run
> self.gnupg.verify_detached_sig(release_file, release_file + ".gpg")
>   File "/usr/lib/python3/dist-packages/simple_cdd/gnupg.py", line 58,
> in verify_detached_sig
> return self.verify_gpg_sig("--verify", sigpathname, pathname)
>   File "/usr/lib/python3/dist-packages/simple_cdd/gnupg.py", line 55,
> in verify_gpg_sig
> raise Fail("Signature verification failed on %s", pathname)
> NameError: name 'pathname' is not defined

It would also be helpful to me if you could reproduce the errors with
LC_ALL=C.UTF-8 or an english locale. I can guess at the meaning, but
with my limited language skills, I'd rather have confidence!


I'll try to confirm and test a fix for this soon.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

[Jakub Wilk]

* Ryan Kavanagh , 2019-02-14, 09:01:

The terminal screen blinks all the time.


What resources do you have set for URxvt? (See output of "appres 
URxvt".) What perl extensions are you using?


I can reproduce the issue without any custom settings or extensions, 
that is:


  $ appres URxvt
  *customization:   -color

(The "customization" line comes from /etc/X11/Xresources/x11-common.)

The effect is quite subtle, so I can imagine some people might not 
notice it.


--
Jakub Wilk

Bug#892661: Bug #892661 in node-static-extend marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #892661 in node-static-extend 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/node-static-extend/commit/de8b9d0c0c1cda2bc2e921b913f2d2383a0447fe


Switch tests to pkg-js-tools and update timeout

Closes: #892661


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892661

Processed: Bug #892661 in node-static-extend marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892661 [src:node-static-extend] node-static-extend: FTBFS and Debci failure
Added tag(s) pending.

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

Bug#802350: Package unusable

[Xavier]

Control: forwarded -1 https://github.com/andrewrk/node-yawl/issues/5
Control: tags -1 + upstream confirmed

Upstream tests fail even using a fresh "npm install".

Processed: Package unusable

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/andrewrk/node-yawl/issues/5
Bug #802350 [src:node-yawl] node-yawl: FTBFS: "yawl buffered messages" times out
Set Bug forwarded-to-address to 
'https://github.com/andrewrk/node-yawl/issues/5'.
> tags -1 + upstream confirmed
Bug #802350 [src:node-yawl] node-yawl: FTBFS: "yawl buffered messages" times out
Added tag(s) confirmed and upstream.

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

Bug#915175: marked as done (oath-toolkit FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 16:36:35 +
with message-id 
and subject line Bug#915175: fixed in oath-toolkit 2.6.1-1.3
has caused the Debian Bug report #915175,
regarding oath-toolkit FTBFS with glibc 2.28
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.)


-- 
915175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oath-toolkit
Version: 2.6.1-1.2
Severity: serious
Tags: ftbfs

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

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-fvisibility=hidden -g -O2 -ffile-prefix-map=/build/1st/oath-toolkit-2.6.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c fseeko.c  -fPIC 
-DPIC -o .libs/fseeko.o
fseeko.c: In function 'rpl_fseeko':
fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! 
Look at the code in fseeko.c, then report this to bug-gnulib."
   #error "Please port gnulib fseeko.c to your platform! Look at the code in 
fseeko.c, then report this to bug-gnulib."
^
make[7]: *** [Makefile:1402: fseeko.lo] Error 1


See #915151 for background.
--- End Message ---
--- Begin Message ---
Source: oath-toolkit
Source-Version: 2.6.1-1.3

We believe that the bug you reported is fixed in the latest version of
oath-toolkit, 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.
Sascha Steinbiss  (supplier of updated oath-toolkit 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, 09 Feb 2019 16:39:41 +0100
Source: oath-toolkit
Binary: liboath-dev liboath0 libpam-oath oath-dbg oathtool
Architecture: source amd64
Version: 2.6.1-1.3
Distribution: unstable
Urgency: medium
Maintainer: OATH Toolkit Team 
Changed-By: Sascha Steinbiss 
Description:
 liboath-dev - Development files for the OATH Toolkit Liboath library
 liboath0   - OATH Toolkit Liboath library
 libpam-oath - OATH Toolkit libpam_oath PAM module
 oath-dbg   - OATH Toolkit debugging symbols
 oathtool   - OATH Toolkit oathtool command line tool
Closes: 915175
Changes:
 oath-toolkit (2.6.1-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use _IO_EOF_SEEN as GNU libc indicator.
 Closes: #915175
Checksums-Sha1:
 a152d7240cb16ae2575a867ab822399aeddec5ff 2265 oath-toolkit_2.6.1-1.3.dsc
 a6ea87709ad57980d1701a4e87cffd34ea94fd95 20404 
oath-toolkit_2.6.1-1.3.debian.tar.xz
 f7acc6df3e1692475083ed779da09a5310d29438 83572 liboath-dev_2.6.1-1.3_amd64.deb
 22f000ce5097a74d720661bffae8251b0fa288f5 78484 liboath0_2.6.1-1.3_amd64.deb
 7d8481eaf8c6d612b5d44ddf25bb9f940e90498a 48328 libpam-oath_2.6.1-1.3_amd64.deb
 07446a7284fa760d95fc796f4781615aa9bf03ea 161468 oath-dbg_2.6.1-1.3_amd64.deb
 38c156cbe14d7d1d2c204e980cf25cd79bf3f666 12022 
oath-toolkit_2.6.1-1.3_amd64.buildinfo
 744a810d6e16cd6503fca483d03afb7b33ae74b3 65952 oathtool_2.6.1-1.3_amd64.deb
Checksums-Sha256:
 fe1d7e23b2561f90cd6f94aa5b5ce6cb5ee81ce7d576a08fdf055fcb03060e1d 2265 
oath-toolkit_2.6.1-1.3.dsc
 5d17b72fa632576cc9bac8fae2513c5e00c6b14bf31889cd1a2c9ab5c5c5743c 20404 
oath-toolkit_2.6.1-1.3.debian.tar.xz
 be3f7140e94fee5cc20e7c2132e5c2d5344778ef2fafc70649f586f6fc1ee8c0 83572 
liboath-dev_2.6.1-1.3_amd64.deb
 ad3749cba25594e8568ff351f2313fffd8cee4c6016f1eedd3e4a9534ee6ae7f 78484 
liboath0_2.6.1-1.3_amd64.deb
 62dcc585552c5c9840cc3c15444320246afd0cb8726e8812c03f0a313fbe4cf1 48328 
libpam-oath_2.6.1-1.3_amd64.deb
 6cfeea0eaf8822c2feec984a95564d77ff943a92d28f2935b01e9201b2c6a922 161468 
oath-dbg_2.6.1-1.3_amd64.deb
 199e24a8e13000fd9baa97bca4d1211e1638544a549defd5a9886e8bd47ff4d3 12022 
oath-toolkit_2.6.1-1.3_amd64.buildinfo
 698bf1d9924a16c932e73b3d11ee718dec07ec7d0c1018604b1522ae59c59a37 65952 
oathtool_2.6.1-1.3_amd64.deb
Files:
 2485792f92d6219700335dfd5657fa65 2265 devel optional oath-toolkit_2.6.1-1.3.dsc
 c26cd0d63d1f657802053a4e67a41e27 20404 devel optional 
oath-toolkit_2.6.1-1.3.debian.tar.xz
 97a36143022cd160db94084b7ff957b1 83572 libdevel optional 
liboath-dev_2.6.1-1.3_amd64.deb
 

Bug#922328: libblockdev-swap2: Swap seems to freeze the system

[MMnbJEE]

Package: libblockdev-swap2
Version: 2.20-6
Severity: grave
Tags: a11y
Justification: renders package unusable


Dear Maintainer,

Not sure if I choose the right package.
 
   * What led up to the situation?

When loading a tif image with feh of 100MB or (which was the next image) 749MB 
the system (Intel Pentium G630 with 4GB DDR3) freezes.

/etc/sysctl.conf
# swappines
vm.swappiness = 10
 
   * What exactly did you do (or not do) that was effective (or ineffective)?

I presume it has something to do with swapping. I experience the same when
I have 15+ tabs open in Firefox (latest version)
When after a long wait the system comes out of the freeze and is usable again 
the
system remains slower than before the view attempt of the image.
When touching a 100MB tif image in Thunar the system freezes. It does not 
recover
anymore -> hit the reset button
 
   * What was the outcome of this action?
 
Waiting a long time or even hitting the reset button

   * What outcome did you expect instead?
 
   No system freezes or slugginess
   Release swap when it is not needed anymore so the system stayes responsive 
even after heavy swapping
Some ideas for a solution:
  Get a message with a choice that swap can not handle the amount of data
  Make swap abandon the operation
  Give the user some sort of control. Do not let him get in a freeze / 
sluggines situation without recovery in an acceptable time

   * Some thoughts
Maybe I did something wrong.


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

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

Versions of packages libblockdev-swap2 depends on:
ii  libblockdev-utils2  2.20-6
ii  libc6   2.28-6
ii  libglib2.0-02.58.3-1

libblockdev-swap2 recommends no packages.

libblockdev-swap2 suggests no packages.

-- no debconf information

Bug#922218: marked as done (gnome-shell fills up logs with an stack trace)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 16:13:24 +
with message-id <20190214161324.ga31...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#922218: gnome-shell fills up logs with an stack trace
has caused the Debian Bug report #922218,
regarding gnome-shell fills up logs with an stack trace
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.)


-- 
922218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.30.1-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

gnome-shell is making my system unusable by completelly filling up the /var 
partition due to the errors it spits into several log files like syslog, 
user.log and messages. All three of them are Gigabytes of size. The issue that 
is reported by gnome-shell (hundreds of times per second!) is the 
following:

Feb 12 14:54:25 dori gnome-shell[5179]: Object St.Icon (0x556220576a40), has 
been already finalized. Impossible to set any property to it.
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: == Stack trace for context 
0x55621f7d6340 ==
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #0 0x55621fc4b2b0 i   
resource:///org/gnome/shell/ui/osdWindow.js:223 (0x7f055c6c9b38 @ 231)
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #1 0x7ffc616fdf90 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f057c0b5de0 @ 71)
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #2 0x7ffc616fe710 b   
self-hosted:916 (0x7f057c0f1230 @ 367)
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #3 0x7ffc616fe800 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f057c0d2230 @ 386)
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #4 0x55621fc4b228 i   
resource:///org/gnome/shell/ui/layout.js:530 (0x7f055c603230 @ 127)
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #5 0x55621fc4b180 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f057c0b5de0 @ 71)
Feb 12 14:54:25 dori org.gnome.Shell.desktop[5179]: #6 0x55621fc4b0c0 i   
self-hosted:916 (0x7f057c0f1230 @ 367)

I'm setting a critical severity because as you might imagine, once the var 
partition is full several unrelated software starts to break. Also for 
non technical users rebooting wouldn't be a solution as the logs will persist.

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evolution-data-server3.30.4-1
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.30.0-5
ii  gir1.2-freedesktop   1.58.3-2
ii  gir1.2-gcr-3 3.28.0-4
ii  gir1.2-gdesktopenums-3.0 3.28.1-1
ii  gir1.2-gdm-1.0   3.30.1-1
ii  gir1.2-geoclue-2.0   2.5.2-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomebluetooth-1.03.28.2-3
ii  gir1.2-gnomedesktop-3.0  3.30.2-4
ii  gir1.2-gtk-3.0   3.24.3-1
ii  gir1.2-gweather-3.0  3.28.2-2
ii  gir1.2-ibus-1.0  1.5.19-1
ii  gir1.2-mutter-3  3.30.2-4
ii  gir1.2-nm-1.01.14.4-4
ii  gir1.2-nma-1.0   1.8.18-2
ii  gir1.2-pango-1.0 1.42.4-6
ii  gir1.2-polkit-1.00.105-25
ii  gir1.2-rsvg-2.0  2.44.10-1
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.9-2
ii  gjs  1.52.4-1
ii  gnome-backgrounds3.30.0-1
ii  gnome-settings-daemon3.30.2-1
ii  gnome-shell-common   3.30.1-2
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk-bridge2.0-0   2.30.0-2
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-5
ii  

Processed: tagging 922218, block 922218 with 906016

[Debian Bug Tracking System]

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

> tags 922218 - moreinfo
Bug #922218 [gnome-shell] gnome-shell fills up logs with an stack trace
Removed tag(s) moreinfo.
> block 922218 with 906016
Bug #922218 [gnome-shell] gnome-shell fills up logs with an stack trace
922218 was not blocked by any bugs.
922218 was not blocking any bugs.
Added blocking bug(s) of 922218: 906016
> thanks
Stopping processing here.

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

Bug#915995: marked as done (nfs-utils FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 15:50:13 +
with message-id 
and subject line Bug#915995: fixed in nfs-utils 1:1.3.4-2.4
has caused the Debian Bug report #915995,
regarding nfs-utils FTBFS with glibc 2.28
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.)


-- 
915995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfs-utils
Version: 1:1.3.4-2.3
Severity: serious
Tags: ftbfs

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

...
device-discovery.c: In function 'bl_add_disk':
device-discovery.c:156:28: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  } else if (dm_is_dm_major(major(dev)))
^
...
libtool: link: gcc -Wall -Wextra -Wstrict-prototypes -pipe 
-D_LARGEFILE64_SOURCE -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\" 
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -Wl,-z -Wl,relro -o blkmapd 
device-discovery.o device-inq.o device-process.o dm-device.o  -ldevmapper 
../../support/nfs/libnfs.a
/usr/bin/ld: device-discovery.o: in function `bl_add_disk':
/build/1st/nfs-utils-1.3.4/utils/blkmapd/device-discovery.c:156: undefined 
reference to `major'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:506: blkmapd] Error 1
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:1.3.4-2.4

We believe that the bug you reported is fixed in the latest version of
nfs-utils, 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.
Hilko Bengen  (supplier of updated nfs-utils 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, 09 Feb 2019 15:26:27 +0100
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source
Version: 1:1.3.4-2.4
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Hilko Bengen 
Description:
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 915995
Changes:
 nfs-utils (1:1.3.4-2.4) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * debian/control: Downgrade the priority to optional to match the override
 file
 .
   [ Hilko Bengen ]
   * Add missing include, fixing FTBFS with glibc 2.28 (Closes: #915995)
Checksums-Sha1:
 d49e1a462a8170e5f6aab8b64186bf924c0db179 2353 nfs-utils_1.3.4-2.4.dsc
 72a09496327a44b119df2e6b0eebb6d94d694063 47488 
nfs-utils_1.3.4-2.4.debian.tar.xz
 e56dc6f70bacaffc087e4317bcddf240e812e77b 7148 
nfs-utils_1.3.4-2.4_source.buildinfo
Checksums-Sha256:
 3bdc37d7649b8a4a21f5c9105decab4666816a04afdc353a192db7f62bb245d9 2353 
nfs-utils_1.3.4-2.4.dsc
 4df38ad918abc8327ba21f85e14923475d9bf3d9ac443d8e7027bdfde60722d7 47488 
nfs-utils_1.3.4-2.4.debian.tar.xz
 889485af4ebf0e455cba138b737a48b597feed35b5680938c71f21e11fe32208 7148 
nfs-utils_1.3.4-2.4_source.buildinfo
Files:
 88ee8528f8ad8bffea29a1250233c961 2353 net optional nfs-utils_1.3.4-2.4.dsc
 02caeb93619ebc6fa513ac658d98ff8f 47488 net optional 
nfs-utils_1.3.4-2.4.debian.tar.xz
 62d3c62374e0ee382270a9a6e50fa477 7148 net optional 
nfs-utils_1.3.4-2.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlxe7ToSHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+tp8P/jdZA39befeU58WjehdyZxJMktx4DR1X
5NGLI8b9B0aMBSbAe9hRaXwhhi9rfTLJBBzwZDVcQHKDhffokK8aut853y6SEad8
PqSnZte7/VqVAUiI9xpcZtbXas5upN5HInntVwIY5OQux45Z6HtaFGmS3U3Pk2HU
GmSTllSzyopRrGCeY/iDkQdfiDzVWEI6zwbh/ZHBVrqKpsO4mMAm/8F6hfO6dGUY
8l4E/6YGC1UO/sdHlwep7Lt6MjFlO8sklBK8WIYJnrTY19YXcQyaKZuzAX/ZUxTr
wKnW6mi4BDMd9/JYq3Y4jAI9OINmoPU8Tx9Yio5PPOrOtIz5U8iwFPJWRuTmgSd2
D/p67S33IFK2E8WR7EST8oy1eK7T3MVFjkA2O+tWhSXnrW2Ds+sTJVcxa3I+mPN9
sAG5AENli+7yxVBgGYBnZoH8N5K/3lZ5ZCNNMf4MfmpkPQFR8I0d/g36NtaHZkYE
Q0eAHFta7Zq0wNJ7feJQRQCXRZ5sz5DgwiTgfIh7Sl4+t0upeAnhaYXFYN4Q67eG
N1BGbFV3343ll+9068L/tPqSfzjHE6fEGeMs2uuDw3ItvSFKmqNUBzjpF39XrgD6
Lj5ORUKSLmJv1dpzHnizF6mh598znSOhzTvRLOU3GfPFg5NrTWgkAO9cp4hO2cLo
VdMuaLdmu0gX
=cnQn
-END PGP SIGNATURE End Message ---

Bug#919340: marked as done (fenix-plugins: FTBFS: configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 15:49:28 +
with message-id 
and subject line Bug#919340: fixed in fenix-plugins 0.0.20070803-8
has caused the Debian Bug report #919340,
regarding fenix-plugins: FTBFS: configure.ac:36: error: possibly undefined 
macro: AC_CHECK_FT2
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.)


-- 
919340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fenix-plugins
Version: 0.0.20070803-7
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

fenix-plugins cannot be rebuilt any longer in a current pbuilder sid
environment:

 debian/rules build
dh build --with autoreconf
   dh_update_autotools_config
   dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:14: installing './compile'
configure.ac:11: installing './missing'
Makefile.am: installing './depcomp'
libtoolize: putting auxiliary files in '.'.
[...]
configure.ac:11: installing './missing'
Makefile.am: installing './depcomp'
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:36: error: possibly undefined macro: AC_CHECK_FT2
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: autoreconf -f -i agua-1.0 exec-0.4a fgfx-1.0 fire-1.0 fsock-1.0 
image-1.0 mixer-1.0 mpeg-1.0 net-1.0 tcpsock-2.0 ttf-1.0 returned exit code 1
make: *** [debian/rules:31: build] Error 2


Cheers,

Andreas


fenix-plugins_0.0.20070803-7.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fenix-plugins
Source-Version: 0.0.20070803-8

We believe that the bug you reported is fixed in the latest version of
fenix-plugins, 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.
Peter Pentchev  (supplier of updated fenix-plugins 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, 14 Feb 2019 17:28:40 +0200
Source: fenix-plugins
Architecture: source
Version: 0.0.20070803-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Peter Pentchev 
Closes: 892343 919340
Changes:
 fenix-plugins (0.0.20070803-8) unstable; urgency=medium
 .
   * Add the 02-pkg-config-freetype patch to fix a FTBFS.
 Closes: #892343, #919340
   * Remove the obsolete Lintian override about the armhf architecture.
   * Bring up to compliance with Debian Policy 4.3.0:
 - point the Vcs-* fields to the Salsa repository
 - switch some upstream and Debian URLs to the HTTPS scheme
 - switch priority to "optional" from "extra"
 - add "Rules-Requires-Root: no" to the source control stanza
   * Add a trivial git-buildpackage config file.
   * Remove some trailing whitespace from the changelog file.
   * Use my Debian e-mail address.
   * Add the year 2019 to my debian/* copyright notice.
   * Update to debhelper compatibility level 12:
 - let debhelper handle autoreconf
 - disable the parallel build
 - use the debhelper-compat (= 12) method
   * Add a simple autopkgtest running the upstream tests.
   * Add the 03-cppcheck patch to fix some memory leaks.
Checksums-Sha1:
 244d69c6d93455594ffce2e8d1317c29d80f1aa0 2749 fenix-plugins_0.0.20070803-8.dsc
 ceb4a68589ad1d6c9bbfa540bfdd9ffbca9f7fa7 6336 
fenix-plugins_0.0.20070803-8.debian.tar.xz
 a1107550708ae05d2febeea81e27d625c948c930 12639 
fenix-plugins_0.0.20070803-8_i386.buildinfo
Checksums-Sha256:
 

Processed: bug 922265 is forwarded to https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/commit/77ccc9bbc3ac70f9c71c527e6062eebec41be57d

[Debian Bug Tracking System]

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

> forwarded 922265 
> https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/commit/77ccc9bbc3ac70f9c71c527e6062eebec41be57d
Bug #922265 {Done: Xavier Guimard } [src:lemonldap-ng] 
lemonldap-ng: FTBFS in sid (failing tests)
Set Bug forwarded-to-address to 
'https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/commit/77ccc9bbc3ac70f9c71c527e6062eebec41be57d'.
> thanks
Stopping processing here.

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

Processed: found 922265 in 2.0.2+ds-3, notfound 922265 in 2.0.2+ds-4

[Debian Bug Tracking System]

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

> found 922265 2.0.2+ds-3
Bug #922265 {Done: Xavier Guimard } [src:lemonldap-ng] 
lemonldap-ng: FTBFS in sid (failing tests)
The source 'lemonldap-ng' and version '2.0.2+ds-3' do not appear to match any 
binary packages
Marked as found in versions lemonldap-ng/2.0.2+ds-3; no longer marked as fixed 
in versions lemonldap-ng/2.0.2+ds-3.
> notfound 922265 2.0.2+ds-4
Bug #922265 {Done: Xavier Guimard } [src:lemonldap-ng] 
lemonldap-ng: FTBFS in sid (failing tests)
Ignoring request to alter found versions of bug #922265 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#922306: linux: btrfs corruption (compressed data + hole data)

[Christoph Anton Mitterer]

Here's the "proper" patch:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85515.html

Bug#922262: marked as done (ripe-atlas-tools: FTBFS (Could not import extension sphinx.ext.pngmath))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 15:19:32 +
with message-id 
and subject line Bug#922262: fixed in ripe-atlas-tools 2.3.0-2
has caused the Debian Bug report #922262,
regarding ripe-atlas-tools: FTBFS (Could not import extension 
sphinx.ext.pngmath)
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.)


-- 
922262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ripe-atlas-tools
Version: 2.3.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=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/build/ripe

[... snipped ...]

copying ripe/atlas/tools/renderers/raw.py -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/ssl_consistency.py -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/sslcert.py -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/traceroute.py -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/traceroute_aspath.py -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers
creating 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers/templates
creating 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/aggregate_ping.txt -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/dns.txt -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/ssl_consistency.txt -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/sslcert.txt -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/renderers/templates/reports
creating /<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/settings
copying ripe/atlas/tools/settings/__init__.py -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/settings
creating 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/settings/templates
copying ripe/atlas/tools/settings/templates/base.yaml -> 
/<>/.pybuild/cpython3_3.7/build/ripe/atlas/tools/settings/templates
running build_scripts
creating build
creating build/scripts-3.7
copying and adjusting scripts/aping -> build/scripts-3.7
copying and adjusting scripts/atraceroute -> build/scripts-3.7
copying and adjusting scripts/adig -> build/scripts-3.7
copying and adjusting scripts/asslcert -> build/scripts-3.7
copying and adjusting scripts/ahttp -> build/scripts-3.7
copying and adjusting scripts/antp -> build/scripts-3.7
copying and adjusting scripts/ripe-atlas -> build/scripts-3.7
changing mode of build/scripts-3.7/aping from 664 to 775
changing mode of build/scripts-3.7/atraceroute from 664 to 775
changing mode of build/scripts-3.7/adig from 664 to 775
changing mode of build/scripts-3.7/asslcert from 664 to 775
changing mode of build/scripts-3.7/ahttp from 664 to 775
changing mode of build/scripts-3.7/antp from 664 to 775
changing mode of build/scripts-3.7/ripe-atlas from 664 to 775
/usr/bin/make -C docs html
make[2]: Entering directory '/<>/docs'
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v1.8.3

Extension error:
Could not import extension sphinx.ext.pngmath (exception: No module named 
'sphinx.ext.pngmath')
make[2]: *** [Makefile:53: html] Error 2
make[2]: Leaving directory '/<>/docs'
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 

Bug#912051: marked as done (rsyncrypto: FTBFS: aclocal-1.15: command not found)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 15:19:43 +
with message-id 
and subject line Bug#912051: fixed in rsyncrypto 1.14-1.1
has caused the Debian Bug report #912051,
regarding rsyncrypto: FTBFS: aclocal-1.15: command not found
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.)


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

>From my pbuilder build log:

...
   dh_auto_build
   make -j1
make[1]: Entering directory '/build/rsyncrypto-1.14'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash
/build/rsyncrypto-1.14/missing aclocal-1.15
/build/rsyncrypto-1.14/missing: line 81: aclocal-1.15: command not found
WARNING: 'aclocal-1.15' is missing on your system.
You should only need it if you modified 'acinclude.m4' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'aclocal' program is part of the GNU Automake package:

It also requires GNU Autoconf, GNU m4 and Perl in order to run:



make[1]: *** [Makefile:361: aclocal.m4] Error 127
make[1]: Leaving directory '/build/rsyncrypto-1.14'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:19: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: rsyncrypto
Source-Version: 1.14-1.1

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated rsyncrypto 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, 09 Feb 2019 15:11:50 +0100
Source: rsyncrypto
Binary: rsyncrypto rsyncrypto-dbgsym
Architecture: source amd64
Version: 1.14-1.1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh 
Changed-By: Sascha Steinbiss 
Description:
 rsyncrypto - rsync friendly encryption
Closes: 884721 912051
Changes:
 rsyncrypto (1.14-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add explicit build dependency on automake-1.15.
 Closes: #912051
   * Fix segfault with --delete. Thanks to Chris Boot for the patch.
 Closes: #884721
Checksums-Sha1:
 8fa473d52a2309d8670bc6b982cded2898601a3c 2054 rsyncrypto_1.14-1.1.dsc
 34f34b27f9e5165b79e32cc83def402069f905ff 29764 
rsyncrypto_1.14-1.1.debian.tar.xz
 9c7113d1dc11f9760110c9bb5cb7de5cfbadd9fc 620380 
rsyncrypto-dbgsym_1.14-1.1_amd64.deb
 8d8ea8343ea0e173f0d298cbaa141c9419cbb6b3 5673 
rsyncrypto_1.14-1.1_amd64.buildinfo
 70b6a087d4977575060ae7fa746ed4d9f47e4c29 302816 rsyncrypto_1.14-1.1_amd64.deb
Checksums-Sha256:
 50a9d944502b85abe3d508c6d922ddb713d5eccedf3b5e497d1c593c2cc123bc 2054 
rsyncrypto_1.14-1.1.dsc
 6feb6becf8000347dcb2aff2663c11a9037b897a3cff53ca9109ecadfaae3fb4 29764 
rsyncrypto_1.14-1.1.debian.tar.xz
 4e6ca49d6611832a64d983b135a4d8f99021d134191df0dad4224c17653b65fa 620380 
rsyncrypto-dbgsym_1.14-1.1_amd64.deb
 5d43962096683b3d26b7be6d243de99c46c19b616c37e994c0113e451c47abd9 5673 
rsyncrypto_1.14-1.1_amd64.buildinfo
 df1cf1874756655da67a7d2228e9129cfb842211c2733024a629f819c8517e2b 302816 
rsyncrypto_1.14-1.1_amd64.deb
Files:
 e3002957caa7ad1f29abbd64b4e1a4bd 2054 utils optional rsyncrypto_1.14-1.1.dsc
 eef5de5e8a8187c5888914a24568c45f 29764 utils optional 
rsyncrypto_1.14-1.1.debian.tar.xz
 3f73eb7eb8fc1dfb26b2ac1fb2eb8b02 620380 debug optional 
rsyncrypto-dbgsym_1.14-1.1_amd64.deb
 880c51b8be643938ef9b89b504ddc045 5673 utils optional 
rsyncrypto_1.14-1.1_amd64.buildinfo
 c25995c55f2e62255aa5576c8e20eecd 302816 utils optional 
rsyncrypto_1.14-1.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAlxe5ysACgkQ6NN64vCf
SHL1EQ//SLzJiTthSGLszTWHkqf5vuvgoVVQSG+dIDelqD07PrZ+KbBVVsgrw7gJ

Bug#884721: marked as done (rsyncrypto: Segmentation fault with --delete)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 15:19:43 +
with message-id 
and subject line Bug#884721: fixed in rsyncrypto 1.14-1.1
has caused the Debian Bug report #884721,
regarding rsyncrypto: Segmentation fault with --delete
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.)


-- 
884721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rsyncrypto
Version: 1.13-1
Severity: serious
Tags: patch upstream
Justification: crash on basic functionality

Dear maintainer,

I have recently been exposed to rsyncrypto through a client of my
work's, and have encountered a crash when using rsyncrypto to refresh an
encrypted directory tree with --delete enabled.

This happens because of an infinite recursion in autofd::unlink():

https://sources.debian.org/src/rsyncrypto/1.13-1/autofd.h/#L217

static int unlink(const char *pathname)
{
bool success=unlink( pathname )==0;
[...]
}

I came up with the following patch which simply calls unlink() in the
top scope. This seems to fix the problem for me:

--- rsyncrypto-1.14.orig/autofd.h
+++ rsyncrypto-1.14/autofd.h
@@ -216,7 +216,7 @@ public:
 // unless it failed with ENOENT - the file already doesn't exist
 static int unlink(const char *pathname)
 {
-bool success=unlink( pathname )==0;
+bool success=::unlink( pathname )==0;
 if( !success && errno!=ENOENT )
 throw rscerror("Erasing file", errno, pathname );
 

This affects 1.13-1 and 1.14-1 in Debian in the same way. Please let me
know if you would like any further information.

Best regards,
Chris

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

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

Versions of packages rsyncrypto depends on:
ii  gzip1.6-5+b1
pn  libargtable2-0  
ii  libc6   2.25-3
ii  libgcc1 1:7.2.0-17
ii  libssl1.1   1.1.0g-2
ii  libstdc++6  7.2.0-17

Versions of packages rsyncrypto recommends:
ii  rsync  3.1.2-2

rsyncrypto suggests no packages.
--- End Message ---
--- Begin Message ---
Source: rsyncrypto
Source-Version: 1.14-1.1

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated rsyncrypto 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, 09 Feb 2019 15:11:50 +0100
Source: rsyncrypto
Binary: rsyncrypto rsyncrypto-dbgsym
Architecture: source amd64
Version: 1.14-1.1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh 
Changed-By: Sascha Steinbiss 
Description:
 rsyncrypto - rsync friendly encryption
Closes: 884721 912051
Changes:
 rsyncrypto (1.14-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add explicit build dependency on automake-1.15.
 Closes: #912051
   * Fix segfault with --delete. Thanks to Chris Boot for the patch.
 Closes: #884721
Checksums-Sha1:
 8fa473d52a2309d8670bc6b982cded2898601a3c 2054 rsyncrypto_1.14-1.1.dsc
 34f34b27f9e5165b79e32cc83def402069f905ff 29764 
rsyncrypto_1.14-1.1.debian.tar.xz
 9c7113d1dc11f9760110c9bb5cb7de5cfbadd9fc 620380 
rsyncrypto-dbgsym_1.14-1.1_amd64.deb
 8d8ea8343ea0e173f0d298cbaa141c9419cbb6b3 5673 
rsyncrypto_1.14-1.1_amd64.buildinfo
 70b6a087d4977575060ae7fa746ed4d9f47e4c29 302816 rsyncrypto_1.14-1.1_amd64.deb
Checksums-Sha256:
 50a9d944502b85abe3d508c6d922ddb713d5eccedf3b5e497d1c593c2cc123bc 2054 
rsyncrypto_1.14-1.1.dsc
 6feb6becf8000347dcb2aff2663c11a9037b897a3cff53ca9109ecadfaae3fb4 29764 
rsyncrypto_1.14-1.1.debian.tar.xz
 4e6ca49d6611832a64d983b135a4d8f99021d134191df0dad4224c17653b65fa 620380 
rsyncrypto-dbgsym_1.14-1.1_amd64.deb
 

Bug#922218: gnome-shell fills up logs with an stack trace

[Sergio Villar Senin]

O Mér, 13-02-2019 ás 11:30 +, Simon McVittie escribiu:
> Control: tags -1 + moreinfo
> 
> On Wed, 13 Feb 2019 at 11:51:08 +0100, Sergio Villar wrote:
> > gnome-shell is making my system unusable by completelly filling up
> > the /var partition due to the errors it spits into several log
> > files
> > like syslog, user.log and messages.
> 
> Are you using any GNOME Shell extensions?
> 
> If you are, does this problem persist if you disable them?
> 
> Does this problem persist if you upgrade gnome-shell, mutter and gjs
> to the versions in unstable? (These versions should have migrated to
> testing a while ago, but are being held up by uninstallability on
> s390x;
> the release team assure me that they intend to get these versions
> into
> buster before the release.)

That made it. I upgraded gnome-shell to unstable version and the
problem is gone.

BR

Bug#921779: Bug#919413: cascade of FTBFS

[Andreas Tille]

On Thu, Feb 14, 2019 at 03:16:22PM +0100, Dominique Dumont wrote:
> On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote:
> > I'm
> > not sure how to deal with the jquery.js one since this is potentially an
> > issue with lots of dependencies - I remember discussions about this
> > which I did not followed.
> 
> Fortunately, jquery is available as a Debian package.

Sure it is.  I simply remember some discussions about why doxygen needs its
own jquery.  I'd be really happy if this is not the case any more.
 
Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#921779: Bug#919413: cascade of FTBFS

[Paolo Greppi]

Hi Dominique, see below

Il 14/02/2019 15:16, Dominique Dumont ha scritto:

On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote:

I'm
not sure how to deal with the jquery.js one since this is potentially an
issue with lots of dependencies - I remember discussions about this
which I did not followed.

Fortunately, jquery is available as a Debian package.

We had a similar issue with libmojolicious-perl. This package now:
- removes jquery from source tarball [1] using debian/copyright Files-excluded 
parameter
- depends on libjs-jquery
- provides a symlink to Debian's query instead of the regular jquery file using
   debian/libmojolicious-perl.links file [2]

HTH

[1] 
https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/copyright#L7
[2] 
https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/libmojolicious-perl.links


I 'm afraid we will not be able to avoid embedding jquery in doxygen, 
because it makes a weird use of it.

The matter has been nicely put down by the former maintaners, see:
https://salsa.debian.org/paolog-guest/doxygen/blob/master/debian/README.jquery

Paolo

Bug#920953: marked as done (ruby-haml-rails FTBFS: invalid byte sequence in US-ASCII (ArgumentError))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 14:47:18 +
with message-id 
and subject line Bug#920953: fixed in ruby-haml-rails 1.0.0-2
has caused the Debian Bug report #920953,
regarding ruby-haml-rails FTBFS: invalid byte sequence in US-ASCII 
(ArgumentError)
to be marked as done.

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

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


-- 
920953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-haml-rails
Version: 1.0.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-haml-rails=all=1.0.0-1=1548295203=0

...
┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

Invalid gemspec in [haml-rails.gemspec]: No such file or directory - git
/usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:145:in `gsub!': invalid byte 
sequence in US-ASCII (ArgumentError)
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:145:in `block in 
load_modified_gemspec'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:144:in `each'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:144:in 
`load_modified_gemspec'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:121:in `load_gemspec'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:34:in `block in 
initialize'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `chdir'
from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `initialize'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in `new'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in 
`do_check_dependencies'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:67:in `run_tests'
from /usr/bin/gem2deb-test-runner:61:in `'
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-haml-rails 
returned exit code 1
make: *** [debian/rules:18: binary-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-haml-rails
Source-Version: 1.0.0-2

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-haml-rails 
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, 14 Feb 2019 15:04:16 +0100
Source: ruby-haml-rails
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 920953
Changes:
 ruby-haml-rails (1.0.0-2) unstable; urgency=medium
 .
   * Team upload
   * Don't use git in gemspec (Closes: #920953)
Checksums-Sha1:
 066237059b8e18868a8e022ce133b8cafd53c325 1900 ruby-haml-rails_1.0.0-2.dsc
 49cb842bc8c9f0d16b1c0dd8bc3ded7288b25939 3212 
ruby-haml-rails_1.0.0-2.debian.tar.xz
 386408537928cd3d531f2e0fa3cff449ba3f168a 15035 
ruby-haml-rails_1.0.0-2_source.buildinfo
Checksums-Sha256:
 088cc30ca51189d87b11a76cd2514cf500f7745e233080efda90afaa73accd55 1900 
ruby-haml-rails_1.0.0-2.dsc
 06629d698bf320a3a55e8aab73b80794aac054d00647d1eccae80687c27ff1c9 3212 
ruby-haml-rails_1.0.0-2.debian.tar.xz
 8cae914c351c2bcd8b6f2c88d6e74bcbc574101e14261b8253200fa469429c7e 15035 
ruby-haml-rails_1.0.0-2_source.buildinfo
Files:
 80fcd026a16a5753388166bf3c1b0e8d 1900 ruby optional ruby-haml-rails_1.0.0-2.dsc
 99b1917cfd171b9a7859ca4640cb734a 3212 ruby optional 
ruby-haml-rails_1.0.0-2.debian.tar.xz
 cf239475a7cbac0357d650dd72173c97 15035 ruby optional 
ruby-haml-rails_1.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlxleAcACgkQia+CtznN
IXr5Tgf/ecaF/F3P2oQ+lDbVYzmtcZPA0P53ay17zlarqdS63oNba9EOJJ0VFZa1
d5nVG0UJ2/KkD7f5GNvQli3A8EeJaJ29TMTOPLnv3X9E03cbQcDdesKHIodlQuWE
H5aNYphJbrye1FrGFwOKbZ632sJ+XrPz4fEFYkkH0hZNdRMWe9QThYLHbvBQrYsb
FgY1W4witVk2DNVm19eaBIaD8ht09u5M9SUVINUgXGKohkUL2wffYrx0rVNg+wca

Bug#922252: marked as done (ganeti-2.15: FTBFS (ImportError: cannot import name Directive))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 14:45:08 +
with message-id 
and subject line Bug#922252: fixed in ganeti-2.15 2.15.2-14
has caused the Debian Bug report #922252,
regarding ganeti-2.15: FTBFS (ImportError: cannot import name Directive)
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.)


-- 
922252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ganeti-2.15
Version: 2.15.2-13
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 python2,sphinxdoc,bash_completion
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf /<>/autogen.sh
configure.ac:15: installing 'autotools/install-sh'
configure.ac:15: installing 'autotools/missing'
Makefile.am:443: installing 'autotools/py-compile'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dpkg-parsechangelog -Sversion > vcs-version
./configure \

[... snipped ...]

cat /<>/lib/_constants.py.in > lib/_constants.py
src/hs2py --constants >> lib/_constants.py
set -e; \
VCSVER=`cat /<>/vcs-version`; \
{ echo '# This file is automatically generated, do not edit!'; \
  echo '#'; \
  echo ''; \
  echo '"""Build-time VCS version number for Ganeti.'; \
  echo '';\
  echo 'This file is autogenerated by the build process.'; \
  echo 'For any changes you need to re-run ./configure (and'; \
  echo 'not edit by hand).'; \
  echo ''; \
  echo '"""'; \
  echo ''; \
  echo '# pylint: disable=C0301,C0324'; \
  echo '# because this is autogenerated, we do not want'; \
  echo '# style warnings' ; \
  echo ''; \
  echo "VCS_VERSION = '$VCSVER'"; \
} > lib/_vcsversion.py
cat /<>/lib/opcodes.py.in_before > lib/opcodes.py
src/hs2py --opcodes >> lib/opcodes.py
cat /<>/lib/opcodes.py.in_after >> lib/opcodes.py
src/hs2py --wconfd-rpc > lib/rpc/stub/wconfd.py
src/hs2py --metad-rpc > lib/rpc/stub/metad.py
PYTHONPATH=. ./autotools/run-in-tempdir /<>/./autotools/build-rpc 
lib/rpc_defs.py > lib/_generated_rpc.py
Checking man/ganeti-cleaner.rst for hardcoded paths...
set -e ; \
trap 'echo auto-removing man/ganeti-cleaner.gen; rm man/ganeti-cleaner.gen' 
EXIT; \
PYTHONPATH=. ./autotools/run-in-tempdir /<>/./autotools/docpp < 
man/ganeti-cleaner.rst > man/ganeti-cleaner.gen ;\
./autotools/check-man-references man/ganeti-cleaner.gen; \
trap - EXIT
Traceback (most recent call last):
  File "/<>/./autotools/docpp", line 39, in 
from ganeti.build import sphinx_ext
  File "/tmp/gntbuild.rQlbNdFI/ganeti/build/sphinx_ext.py", line 47, in 
from sphinx.directives import Directive
ImportError: cannot import name Directive
auto-removing man/ganeti-cleaner.gen
make[1]: *** [Makefile:4455: man/ganeti-cleaner.gen] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:21: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ganeti-2.15.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 ---
Source: ganeti-2.15
Source-Version: 2.15.2-14

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti-2.15 
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-

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

[Diederik de Haas]

nvm, doing another 'aptitude safe-upgrade' right after made the problem go 
away again.

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

Bug#921779: Bug#919413: cascade of FTBFS

[Dominique Dumont]

On Tuesday, 12 February 2019 16:54:12 CET Andreas Tille wrote:
> I'm
> not sure how to deal with the jquery.js one since this is potentially an
> issue with lots of dependencies - I remember discussions about this
> which I did not followed.

Fortunately, jquery is available as a Debian package.

We had a similar issue with libmojolicious-perl. This package now:
- removes jquery from source tarball [1] using debian/copyright Files-excluded 
parameter
- depends on libjs-jquery
- provides a symlink to Debian's query instead of the regular jquery file using 
  debian/libmojolicious-perl.links file [2]



HTH

[1] 
https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/copyright#L7
[2] 
https://salsa.debian.org/perl-team/modules/packages/libmojolicious-perl/blob/master/debian/libmojolicious-perl.links

Bug#922145: closed by Rhonda D'Vine (Bug#922145: fixed in irssi 1.2.0-2)

[Diederik de Haas]

On woensdag 13 februari 2019 15:51:04 CET you wrote:
> #922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is
> also in package irssi-plugin-otr
> 
> It has been closed by Rhonda D'Vine .

I think it's not actually fixed as I just got the error again.
Now with version 1.2.0-2, but 'the other way around'.

Unpacking irssi-plugin-otr (1.2.0-2) over (1.2.0-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-y16KCS/03-irssi-plugin-otr_1.2.0-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/irssi/help/otr', which is also in package 
irssi 1.2.0-1

I always thought Breaks+Replaces were needed with these kind of changes.

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

Bug#920953: Bug #920953 in ruby-haml-rails marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #920953 in ruby-haml-rails 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/ruby-team/ruby-haml-rails/commit/c54d8d010649c781ebfdf46ad9b182023cb8a485


Don't use git in gemspec (Closes: #920953)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/920953

Processed: Bug #920953 in ruby-haml-rails marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #920953 [src:ruby-haml-rails] ruby-haml-rails FTBFS: invalid byte sequence 
in US-ASCII (ArgumentError)
Added tag(s) pending.

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

Processed: Re: Bug#922297: rxvt-unicode: *blink* *blink* *blink*

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible moreinfo
Bug #922297 [rxvt-unicode] rxvt-unicode: *blink* *blink* *blink*
Added tag(s) unreproducible and moreinfo.

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

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

[Ryan Kavanagh]

Control: tags -1 unreproducible moreinfo

On Thu, Feb 14, 2019 at 12:02:27PM +0100, Jakub Wilk wrote:
> The terminal screen blinks all the time.

What resources do you have set for URxvt? (See output of "appres
URxvt".) What perl extensions are you using?

I'll try to debug this bug (and all of the others that appeared after
applying the 24bit colour patch) today, but failing that, I'll just
revert the patch.

Thanks,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#918850: marked as done (libmypaint: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath')

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 13:50:24 +
with message-id 
and subject line Bug#918850: fixed in libmypaint 1.3.0-2.1
has caused the Debian Bug report #918850,
regarding libmypaint: FTBFS with Sphinx 1.8: No module named 
'sphinx.ext.pngmath'
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.)


-- 
918850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmypaint
Version: 1.3.0-2
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.8

Dear Maintainer,

libmypaint fails to build with Sphinx 1.8, currently available in
experimental:

  sphinx-build source/ build/
  Running Sphinx v1.8.3

  Extension error:
  Could not import extension sphinx.ext.pngmath (exception: No module named 
'sphinx.ext.pngmath')

The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1]
in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which
also has SVG support in addition to PNG.

To me it looks like this extension is unused anyway: there are no “.. math::”
directives or “:math:” roles, and libmypaint-doc does not have any generated
PNG images. So this extension can be simply removed from extensions in
conf.py.

[1]: https://github.com/sphinx-doc/sphinx/pull/4702
[2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libmypaint
Source-Version: 1.3.0-2.1

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated libmypaint 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, 09 Feb 2019 12:22:40 +0100
Source: libmypaint
Binary: gir1.2-mypaint-1.3 libmypaint-1.3-0 libmypaint-1.3-0-dbgsym 
libmypaint-common libmypaint-dev libmypaint-doc
Architecture: source amd64 all
Version: 1.3.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sascha Steinbiss 
Description:
 gir1.2-mypaint-1.3 - GObject introspection data for libmypaint
 libmypaint-1.3-0 - brush library for mypaint
 libmypaint-common - brush library for mypaint - common files
 libmypaint-dev - brush library for mypaint - development files
 libmypaint-doc - brush library for mypaint - documentation
Closes: 895401 895402 918850
Changes:
 libmypaint (1.3.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove unused Sphinx extension. Thanks to Dmitry Shachnev for the hint.
 Closes: #918850
   * Make build reproducible. Thanks to Chris Lamb for the patch.
 Closes: #895401
   * Reference correct homepage. Thanks to Chris Lamb for the patch.
 Closes: #895402
Checksums-Sha1:
 a58967aafddab9670e0909822e51748da1305952 2527 libmypaint_1.3.0-2.1.dsc
 466e63fe1207ec1bf1147b9da32eeab35a40558c 4952 
libmypaint_1.3.0-2.1.debian.tar.xz
 b2cc6e16d64ff616065b4f4c541d0e8939987108 6160 
gir1.2-mypaint-1.3_1.3.0-2.1_amd64.deb
 a60479eb5e3cd9870cbd5690e22b1c560e415551 79064 
libmypaint-1.3-0-dbgsym_1.3.0-2.1_amd64.deb
 ba7037138e0e9140fb5ba2207aaf14bbb9ebe473 31896 
libmypaint-1.3-0_1.3.0-2.1_amd64.deb
 eb6025358c733b0e0c1259c94a977208edfb4c88 80332 
libmypaint-common_1.3.0-2.1_all.deb
 019458f88d33c0a2055331dc823dda7628ee6ea0 11376 
libmypaint-dev_1.3.0-2.1_amd64.deb
 b4214bf091118b095b9cda4970d71cfc962a83aa 62548 libmypaint-doc_1.3.0-2.1_all.deb
 20b55c23b0af3c95bf9cbadad4f3eeb8a64fe3ac 10332 
libmypaint_1.3.0-2.1_amd64.buildinfo
Checksums-Sha256:
 c52b75b9e64d6953f8ebc200f6dcc6c0e7e339b90c9f4ff8d3743abd3a16fde4 2527 
libmypaint_1.3.0-2.1.dsc
 4730ba516efa3394904a9deb71b93277c2cacfd5e5992eca515c1afe1503fe07 4952 
libmypaint_1.3.0-2.1.debian.tar.xz
 e079103db746b8a1cf69123dde6e3ddab20e282211a17c9b9aa774ea30db29d5 6160 
gir1.2-mypaint-1.3_1.3.0-2.1_amd64.deb
 bc65bb61caff309b4263332f61f668653acf47d91def1ed3140571785f0c31b3 79064 
libmypaint-1.3-0-dbgsym_1.3.0-2.1_amd64.deb
 

Bug#922265: marked as done (lemonldap-ng: FTBFS in sid (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 13:50:09 +
with message-id 
and subject line Bug#922265: fixed in lemonldap-ng 2.0.2+ds-4
has caused the Debian Bug report #922265,
regarding lemonldap-ng: FTBFS in sid (failing tests)
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.)


-- 
922265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lemonldap-ng
Version: 2.0.2+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/lemonldap-ng-2.0.2+ds'
/usr/bin/make configure STORAGECONFFILE=/etc/lemonldap-ng/lemonldap-ng.ini \
PERLOPTIONS="INSTALLDIRS=vendor"
make[2]: Entering directory '/<>/lemonldap-ng-2.0.2+ds'
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Lemonldap::NG::Common
Writing MYMETA.yml and MYMETA.json

[... snipped ...]

t/61-GrantSession.t ... ok
t/61-Session-ActivityTimeout.t  ok
t/61-Session-Timeout.t  ok
t/62-SingleSession.t .. ok
t/63-History.t  ok
t/64-StayConnected.t .. ok
t/65-AutoSignin.t . ok
t/66-CDA-already-auth.t ... ok
t/66-CDA-with-REST.t .. ok
t/66-CDA-with-SOAP.t .. ok
t/66-CDA.t  ok
t/70-2F-TOTP-with-HISTORY.t ... ok
t/70-2F-TOTP.t  ok
t/70-2F-TOTP_8.t .. ok
t/71-2F-U2F-with-HISTORY.t  ok
t/71-2F-U2F.t . ok
t/72-2F-REST-with-HISTORY.t ... ok
t/73-2F-UTOTP-TOTP-and-U2F-with-HISTORY.t . ok
t/73-2F-UTOTP-TOTP-and-U2F.t .. ok
t/73-2F-UTOTP-TOTP-only-with-HISTORY.t  ok
t/73-2F-UTOTP-TOTP-only.t . ok
t/74-2F-Required.t  ok
t/75-2F-Registers.t ... ok
t/76-2F-Ext-with-BruteForce.t . ok
t/76-2F-Ext-with-GrantSession.t ... ok
t/76-2F-Ext-with-HISTORY.t  ok
t/77-2F-Mail.t  ok
t/90-Translations.t ... ok
t/99-pod.t  ok

Test Summary Report
---
t/29-AuthGPG.t  (Wstat: 512 
Tests: 13 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=119, Tests=4738, 158 wallclock secs ( 1.38 usr  0.40 sys + 97.22 cusr 
16.18 csys = 115.18 CPU)
Result: FAIL
Failed 1/119 test programs. 0/4738 subtests failed.
make[2]: *** [Makefile:1062: test_dynamic] Error 255
make[2]: Leaving directory 
'/<>/lemonldap-ng-2.0.2+ds/lemonldap-ng-portal'
make[1]: *** [Makefile:371: portal_test] Error 2
make[1]: Leaving directory '/<>/lemonldap-ng-2.0.2+ds'
dh_auto_test: make -j1 test returned exit code 2
make: *** [debian/rules:20: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 -A"
and it also fails here:

https://buildd.debian.org/status/package.php?p=lemonldap%2dng

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 

Bug#890117: marked as done (bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 13:49:21 +
with message-id 
and subject line Bug#890117: fixed in bedtools 2.27.1+dfsg-4
has caused the Debian Bug report #890117,
regarding bedtools FTBFS on big endian: Tools failing:  bamtobed bamtofastq 
coverage genomecov groupby intersect jaccard map merge multicov negativecontrol
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.)


-- 
890117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bedtools
Version: 2.27.1+dfsg-1
Severity: serious

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

...
--
 Test Results 
--
Tools passing:  bed12tobed6 closest cluster complement expand fisher flank 
general getfasta makewindows reldist sample shift shuffle slop sort spacing 
split subtract
Tools failing:  bamtobed bamtofastq coverage genomecov groupby intersect 
jaccard map merge multicov negativecontrol
NB: the 'negativecontrol' test is supposed to fail. If it wasn't caught, 
something went wrong with this test script.
Makefile:196: recipe for target 'test' failed
make[1]: *** [test] Error 1
--- End Message ---
--- Begin Message ---
Source: bedtools
Source-Version: 2.27.1+dfsg-4

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

Debian distribution maintenance software
pp.
Charles Plessy  (supplier of updated bedtools 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, 14 Feb 2019 22:11:21 +0900
Source: bedtools
Binary: bedtools bedtools-test
Architecture: source
Version: 2.27.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Charles Plessy 
Description:
 bedtools   - suite of utilities for comparing genomic features
 bedtools-test - test data for the bedtools package
Closes: 890117
Changes:
 bedtools (2.27.1+dfsg-4) unstable; urgency=medium
 .
   * Disable the shuffle test on other 32-bit architectures.
   * Restrict build to little-endian release architectures. Closes: #890117
   * QA-build with Salsa.
Checksums-Sha1:
 66e1d643cd84463760c3961af71144e884a1f1eb 2244 bedtools_2.27.1+dfsg-4.dsc
 27fb51ccc6d30f2ce71d73321464119d4a27fa98 12164 
bedtools_2.27.1+dfsg-4.debian.tar.xz
 b486720a7ddac72dc71c9f337d413099c3fa24b7 7197 
bedtools_2.27.1+dfsg-4_source.buildinfo
Checksums-Sha256:
 964e9344a4caebbb3dd6b0eeb60874fd420499a3422293c4103630a096728005 2244 
bedtools_2.27.1+dfsg-4.dsc
 1d271ae0819175b24e86651a4d8edfba8adc0d46d261241d712ae07b73821087 12164 
bedtools_2.27.1+dfsg-4.debian.tar.xz
 ed77a12c1c555c5098d397bbd40f50a93e35ae2571666d1f5753204f6df86418 7197 
bedtools_2.27.1+dfsg-4_source.buildinfo
Files:
 82f6c61f98cb0c97cec803c0108318da 2244 science optional 
bedtools_2.27.1+dfsg-4.dsc
 0771088ea68eef745728eac3b41cb9e1 12164 science optional 
bedtools_2.27.1+dfsg-4.debian.tar.xz
 7da7043b4ce1b3a47d4de07f1d59b090 7197 science optional 
bedtools_2.27.1+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc0cUmcxg7Z7ugFlGxb1sjyKV1QIFAlxlaacACgkQxb1sjyKV
1QK3zQ//UAVJEywSgLKnCWsI2WnFu7o31spyDcOPa72ySHBRgA45U2Y6KYl2BiDM
wlZ8IT0/zlCoVP1SyT+6R73i3yBGMWUEpLfw0lLUFpG+Xgp/8R1S6mp3KWueOPF4
ixDB44OmKHiGytYXwK+URuYKImdj3S8u18w9L2G96UFKYX6jLLneXz3Vp/Oq9Bar
Megbaod7m96cOKTr9FquA/KehFx5WvMPK+AjLL+8Qolgf3DR65vSmKtRYDi6oAIL
r9b7ZkmwNGFeOYoYtVdIA2rexXUTXlLJzF7Q/k7bha2JT/+Ooh+/8Ie2x6rCnOv6
x/8IthNGYwI52/EnkFUqmYpS7E3UInnMBjLO7Bm1AO3NMj90tvu4mDgtko19O6Kj
mU/uuEO+rdqqIQPseeg9Y5AghJXwDQBVbjyZ1Uzj7OtBybH+ktD1uFDydOCvcqus
r2NhYrU6x5gj86pvaK6JpFCWPLHU1z2WekaDVCrRlmtZ+NRnf7/H7bYbjPhHjTm2
U5Add6cRdtIvB/7Io9CW+R01Rw6g8Nr0zpCzQGhVK6JXc5ssEpYEHqKP5e287dtR
UrVWkPKhiCcmm8FvqLbJT5h0wJYl1TSsQsuAJwZoEhBpy7Vo7BNum+1neltJlsPQ
8/cY65HJMMCryDJUeWFfib0U1k0bbJcPwRMwUIl/BAbwih9At4o=
=/Yhv
-END PGP SIGNATURE End Message ---

Bug#922313: kopano-search: missing an end of line character in /etc/apparmor.d/usr.sbin.kopano-search

[Louis van Belle]

Package: kopano-search
Version: 8.7.0-1
Severity: serious
Justification: 2

Hello, 

The kopano-search gives a parser error on the apparmor profile. 

Setting up kopano-search (8.7.0-1) ...
AppArmor parser error for /etc/apparmor.d/usr.sbin.kopano-search in 
/etc/apparmor.d/usr.sbin.kopano-search at line 39: missing an end of line 
character? (entry: /etc/ssl/openssl.cnf)
Created symlink 
/etc/systemd/system/multi-user.target.wants/kopano-search.service → 
/lib/systemd/system/kopano-search.service.
Setting up kopano-core (8.7.0-1) ...

The solution is simple. 
edit /etc/apparmor.d/usr.sbin.kopano-search
add a "," behind the line: 
  /etc/ssl/openssl.cnf r

Thank you for porting kopano. 

Best regards, 

Louis



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

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

Versions of packages kopano-search depends on:
ii  catdoc   1:0.95-4.1
ii  file 1:5.35-2
ii  gawk 1:4.2.1+dfsg-1
ii  init-system-helpers  1.56+nmu1
ii  kopano-common8.7.0-1
ii  lsb-base 10.2018112800
ii  poppler-utils0.71.0-2
ii  python3  3.7.2-1
ii  python3-bsddb3   6.2.6-3
ii  python3-dateutil 2.7.3-3
ii  python3-kopano   8.7.0-1
ii  python3-magic2:0.4.15-2
ii  python3-xapian   1.4.9-1
ii  unzip6.0-21
ii  w3m  0.5.3-37
ii  xsltproc 1.1.32-2

kopano-search recommends no packages.

kopano-search suggests no packages.

-- Configuration Files:
/etc/apparmor.d/usr.sbin.kopano-search changed:
/usr/sbin/kopano-search flags=(attach_disconnected) {
  #include 
  #include 
  #include 
  #include 
  capability chown,
  capability dac_override,
  capability dac_read_search,
  capability setgid,
  capability setuid,
  @{PROC}/@{pid}/cmdline r,
  @{PROC}/@{pid}/fd r,
  @{PROC}/@{pid}/mounts r,
  @{PROC}/@{pid}/status r,
  @{PROC}/@{pid}/task/@{tid}/comm rw,
  deny /usr/lib/python{3,2.?}/dist-packages/kopano_search/*.pyc w,
  /bin/dash Pix,
  /bin/rm Pix,
  # FIXME: it would be nice if search would use search- like pa
  /dev/shm/* rwl,
  /etc/gss/mech.d/ r,
  /etc/gss/mech.d/*.conf r,
  /etc/kopano/search.cfg r,
  /etc/magic r,
  /etc/mapi/ r,
  /etc/mapi/kopano.inf r,
  /etc/mapi/zcontacts.inf r,
  /etc/ssl/openssl.cnf r,
  /lib/@{multiarch}/ld-*.so mr,
  /sbin/ldconfig Pix,
  /run/kopano/search.pid rw,
  /run/kopano/search.pid.lock lrw,
  /run/kopano/search.sock rw,
  /run/kopano/*.*-* rw,
  /usr/bin/python{2,3}.? ix,
  /usr/sbin/kopano-search r,
  /var/lib/kopano/search/** rwlk,
  /var/log/kopano/search.log rw,
}


-- no debconf information

Bug#890117: Bug #890117 in bedtools marked as pending

[Charles Plessy]

Control: tag -1 pending

Hello,

Bug #890117 in bedtools 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/med-team/bedtools/commit/c0e8d812e70e59a4268e69fcdd2c77d0c7bf5aae


bedtools (2.27.1+dfsg-4) unstable; urgency=medium

  * Disable the shuffle test on other 32-bit architectures.
  * Restrict build to little-endian release architectures. Closes: #890117
  * QA-build with Salsa.

 -- Charles Plessy   Thu, 14 Feb 2019 22:11:21 +0900


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/890117

Bug#871105: Status of debian-faq

[Dr. Tobias Quathamer]

Dear FTP Masters,

the package "debian-faq" has been uploaded three months ago and contains
various important fixes. It's currently stuck in BYHAND.

Is there any chance that we can get this package into buster?

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Processed: Bug #890117 in bedtools marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890117 [src:bedtools] bedtools FTBFS on big endian: Tools failing:  
bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge 
multicov negativecontrol
Ignoring request to alter tags of bug #890117 to the same tags previously set

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

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Kanstrup, Mikael]

>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2
>>> WPA: IGTK - hexdump(len=16): [REMOVED]
>>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 
>>> key_idx=1024 set_tx=0 seq_len=6 key_len=16
>>
>> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to
>> think it's a fault of the AP which sends an invalid key index.

>Just wondering, any updates on this? Is there any workaround I can
>apply to make that work for most users?

We've seen a couple of misbehaving routers when using PMF. A workaround that 
has proven successful is to byte swap the IGTK key index. 1024 happens to be 
index 4 in big endian. Not sure what Jouni thinks about working around faulty 
APs. Would of course be better if this was caught in certification tests but 
these APs are already out on the market. Anyway, I've just sent an RFC patch 
with the workaround to the mailing list:

"[RFC] PMF: Allow Key ID in big endian format to workaround faulty APs"
?
/Mikael

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Kanstrup, Mikael]

>>> wlp5s0: WPA: IGTK keyid 1024 pn d0caa82e44b2
>>> WPA: IGTK - hexdump(len=16): [REMOVED]
>>> wpa_driver_nl80211_set_key: ifindex=3 (wlp5s0) alg=4 addr=0x55e7e55d2909 
>>> key_idx=1024 set_tx=0 seq_len=6 key_len=16
>>
>> A key_idx=1024 looks wrong, it should be 4 or 5 for IGTK. I tend to
>> think it's a fault of the AP which sends an invalid key index.

>Just wondering, any updates on this? Is there any workaround I can
>apply to make that work for most users?

We've seen a couple of misbehaving routers when using PMF. A workaround that 
has proven successful is to byte swap the IGTK key index. 1024 happens to be 
index 4 in big endian. Not sure what Jouni thinks about working around faulty 
APs. Would of course be better if this was caught in certification tests but 
these APs are already out on the market. Anyway, I've just sent an RFC patch 
with the workaround to the mailing list:

?"[RFC] PMF: Allow Key ID in big endian format to workaround faulty APs"
?
/Mikael?

Bug#922265: marked as done (lemonldap-ng: FTBFS in sid (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 12:49:16 +
with message-id 
and subject line Bug#922265: fixed in lemonldap-ng 2.0.2+ds-3
has caused the Debian Bug report #922265,
regarding lemonldap-ng: FTBFS in sid (failing tests)
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.)


-- 
922265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lemonldap-ng
Version: 2.0.2+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/lemonldap-ng-2.0.2+ds'
/usr/bin/make configure STORAGECONFFILE=/etc/lemonldap-ng/lemonldap-ng.ini \
PERLOPTIONS="INSTALLDIRS=vendor"
make[2]: Entering directory '/<>/lemonldap-ng-2.0.2+ds'
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Lemonldap::NG::Common
Writing MYMETA.yml and MYMETA.json

[... snipped ...]

t/61-GrantSession.t ... ok
t/61-Session-ActivityTimeout.t  ok
t/61-Session-Timeout.t  ok
t/62-SingleSession.t .. ok
t/63-History.t  ok
t/64-StayConnected.t .. ok
t/65-AutoSignin.t . ok
t/66-CDA-already-auth.t ... ok
t/66-CDA-with-REST.t .. ok
t/66-CDA-with-SOAP.t .. ok
t/66-CDA.t  ok
t/70-2F-TOTP-with-HISTORY.t ... ok
t/70-2F-TOTP.t  ok
t/70-2F-TOTP_8.t .. ok
t/71-2F-U2F-with-HISTORY.t  ok
t/71-2F-U2F.t . ok
t/72-2F-REST-with-HISTORY.t ... ok
t/73-2F-UTOTP-TOTP-and-U2F-with-HISTORY.t . ok
t/73-2F-UTOTP-TOTP-and-U2F.t .. ok
t/73-2F-UTOTP-TOTP-only-with-HISTORY.t  ok
t/73-2F-UTOTP-TOTP-only.t . ok
t/74-2F-Required.t  ok
t/75-2F-Registers.t ... ok
t/76-2F-Ext-with-BruteForce.t . ok
t/76-2F-Ext-with-GrantSession.t ... ok
t/76-2F-Ext-with-HISTORY.t  ok
t/77-2F-Mail.t  ok
t/90-Translations.t ... ok
t/99-pod.t  ok

Test Summary Report
---
t/29-AuthGPG.t  (Wstat: 512 
Tests: 13 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=119, Tests=4738, 158 wallclock secs ( 1.38 usr  0.40 sys + 97.22 cusr 
16.18 csys = 115.18 CPU)
Result: FAIL
Failed 1/119 test programs. 0/4738 subtests failed.
make[2]: *** [Makefile:1062: test_dynamic] Error 255
make[2]: Leaving directory 
'/<>/lemonldap-ng-2.0.2+ds/lemonldap-ng-portal'
make[1]: *** [Makefile:371: portal_test] Error 2
make[1]: Leaving directory '/<>/lemonldap-ng-2.0.2+ds'
dh_auto_test: make -j1 test returned exit code 2
make: *** [debian/rules:20: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 -A"
and it also fails here:

https://buildd.debian.org/status/package.php?p=lemonldap%2dng

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 

Bug#922272: marked as done (irssi-plugin-otr: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi 1.2.0-1)

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 13:35:31 +0100
with message-id 
and subject line Re: Bug#922272: irssi-plugin-otr: trying to overwrite 
'/usr/share/irssi/help/otr', which is also in package irssi 1.2.0-1
has caused the Debian Bug report #922272,
regarding irssi-plugin-otr:  trying to overwrite '/usr/share/irssi/help/otr', 
which is also in package irssi 1.2.0-1
to be marked as done.

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

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


-- 
922272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: irssi-plugin-otr
Version: 1.2.0-1
Severity: serious

Hi Rhonda,

unfortunately the file moving between irssi and irssi-plugin-otr doesn't
seem to completely fixed yet. When upgrading them from 1.2.0-1 to
1.2.0-2, I get:

Preparing to unpack .../04-irssi-plugin-otr_1.2.0-2_amd64.deb ...
Unpacking irssi-plugin-otr (1.2.0-2) over (1.2.0-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-dVLCdE/04-irssi-plugin-otr_1.2.0-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/irssi/help/otr', which is also in package 
irssi 1.2.0-1
Preparing to unpack .../05-irssi_1.2.0-2_amd64.deb ...
Unpacking irssi (1.2.0-2) over (1.2.0-1) ...

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

Kernel: Linux 4.19.0-2-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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages irssi-plugin-otr depends on:
ii  irssi1.2.0-2
ii  libc62.28-7
ii  libgcrypt20  1.8.4-5
ii  libotr5  4.1.1-3

irssi-plugin-otr recommends no packages.

irssi-plugin-otr suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Tags: wontfix

   Hey,

On 2/14/19 9:34 AM, Axel Beckert wrote:
> Rhonda D'Vine wrote:
>>  you are right, but: This issue exists only with upgrade from the broken
>> 1.2.0-1 package.  Which isn't available anymore, it was there for way
>> less than a day.  I am much more leaning towards a "wontfix" than doing
>> the Replaces & Conflicts dance and carry that for ... when would then be
>> practical to remove it again?  It doesn't affect upgrades from anything
>> available right now already.
>>
>>  Are you fine with ignoring this [...]
> 
> If that's the case, I'm totally fine with ignoring it. Feel free to
> close.

 alright, doing that then. :)
Rhonda--- End Message ---

Bug#922306: linux: btrfs corruption (compressed data + hole data)

[Christoph Anton Mitterer]

Source: linux
Version: 4.19.20-1
Severity: critical
Tags: upstream patch
Justification: causes serious data loss

Hi.

Apparently there was a longer existing data corruption bug in btrfs[0],
AFAIU it happened when compression was used together with holes in data
and there was *no* recognition by checksumming.

Seems some movement got into this the last days and a patch[1] may have
been found fixing the issue.


Due to potential silent data corruptpion it makes perhaps sense to
cherry pick that fix (maybe waiting for confirmation from upstream
whether it's the final one) instead of waiting for it being released
in some upcoming stable release?

Cheers,
Chris.


[0] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85407.html
[1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85492.html


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

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

Bug#907766: marked as done (node-chokidar: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 12:19:06 +
with message-id 
and subject line Bug#907766: fixed in node-chokidar 1.7.0-3
has caused the Debian Bug report #907766,
regarding node-chokidar: FTBFS in buster/sid (failing tests)
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.)


-- 
907766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-chokidar
Version: 1.7.0-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
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha --exit --reporter spec


  chokidar
✓ should expose public API methods
fs.watch (non-polling)
  watch a directory
✓ should produce an instance of chokidar.FSWatcher
✓ should expose public API methods
✓ should emit `add` event when file was added (57ms)
✓ should emit `addDir` event when directory was added (56ms)
✓ should emit `change` event when file was changed
✓ should emit `unlink` event when file was removed (104ms)
✓ should emit `unlinkDir` event when a directory was removed (53ms)
✓ should emit `unlink` and `add` events when a file is renamed (156ms)
✓ should emit `add`, not `change`, when previously deleted file is 
re-added (161ms)
✓ should not emit `unlink` for previously moved files (404ms)
✓ should survive ENOENT for missing subdirectories
✓ should notice when a file appears in a new directory
✓ should watch removed and re-added directories (1514ms)
  watch individual files
✓ should detect changes
✓ should detect unlinks (156ms)
✓ should detect unlink and re-add (257ms)
✓ should ignore unwatched siblings (55ms)
  renamed directory
✓ should emit `add` for a file in a renamed directory (1017ms)
  watch non-existent paths
✓ should watch non-existent file and detect add (56ms)
✓ should watch non-existent dir and detect addDir/add (106ms)
  watch glob patterns
✓ should correctly watch and emit based on glob input (62ms)
✓ should respect negated glob patterns (156ms)
✓ should traverse subdirs to match globstar patterns (216ms)
✓ should resolve relative paths with glob patterns (72ms)
✓ should correctly handle conflicting glob patterns (158ms)
✓ should correctly handle intersecting glob patterns (58ms)
✓ should not confuse glob-like filenames with globs (103ms)
✓ should treat glob-like directory names as literal directory names 
when globbing is disabled (64ms)
✓ should treat glob-like filenames as literal filenames when globbing 
is disabled (51ms)
✓ should not prematurely filter dirs against complex globstar 
patterns (62ms)
✓ should emit matching dir events
  watch symlinks
✓ should watch symlinked dirs
✓ should watch symlinked files
✓ should follow symlinked files within a normal dir
✓ should watch paths with a symlinked parent
✓ should not recurse indefinitely on circular symlinks
✓ should recognize changes following symlinked dirs
✓ should follow newly created symlinks (57ms)
✓ should watch symlinks as files when followSymlinks:false
✓ should watch symlinks within a watched dir as files when 
followSymlinks:false (310ms)
✓ should not reuse watcher when following a symlink to elsewhere 
(115ms)
✓ should properly match glob patterns that include a symlinked dir
  watch arrays of paths/globs
✓ should watch all paths in an array
✓ should accommodate nested arrays in input
✓ should throw if provided any non-string paths
  watch options
ignoreInitial
  false
✓ should emit `add` events for preexisting files
✓ should emit `addDir` event for watched dir
✓ should emit `addDir` events for preexisting dirs
  true
✓ should ignore inital add events (51ms)
✓ should ignore add events on a subsequent .add() (1002ms)
✓ should notice when a file appears in an empty directory
✓ should emit a change on a 

Bug#906390: marked as done (node-vhost: FTBFS in buster/sid (autobuilder hangs))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 12:04:14 +
with message-id 
and subject line Bug#906390: fixed in node-vhost 3.0.2-1
has caused the Debian Bug report #906390,
regarding node-vhost: FTBFS in buster/sid (autobuilder hangs)
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.)


-- 
906390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-vhost
Version: 3.0.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
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -C --reporter spec --bail --check-leaks test/


  vhost(hostname, server)
✓ should route by Host (57ms)
✓ should ignore port in Host
✓ should support IPv6 literal in Host
✓ should 404 unless matched
✓ should 404 without Host header
arguments
  hostname
✓ should be required
✓ should accept string
✓ should accept RegExp
  handle
✓ should be required
✓ should accept function
✓ should reject plain object
with string hostname
  ✓ should support wildcards
  ✓ should restrict wildcards to single part
  ✓ should treat dot as a dot
  ✓ should match entire string
  ✓ should populate req.vhost
with RegExp hostname
  ✓ should match using RegExp
  ✓ should match entire hostname
  ✓ should populate req.vhost


  19 passing (88ms)

E: Build killed with signal TERM after 60 minutes of inactivity


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-vhost.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 ---
Source: node-vhost
Source-Version: 3.0.2-1

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-vhost 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, 14 Feb 2019 12:36:54 +0100
Source: node-vhost
Binary: node-vhost
Architecture: source
Version: 3.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 906390
Description: 
 node-vhost - connect middleware for domain request matching - Node.js module
Changes:
 node-vhost (3.0.2-1) unstable; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 11
   * Declare compliance with policy 4.3.0
   * Change section to javascript
   * Change priority to optional
   * Update VCS fields to salsa
   * Fix debian/copyright format
   * New upstream version 3.0.2
   * Update d/copy
   * Add patch to clean test (Closes: #906390)
   * Add upstream/metadata
   * Switch tests to pkg-js-tools
   * Add "Multi-Arch: foreign"
Checksums-Sha1: 
 728572a852ce0a842a5748694125aa07917880dd 2037 node-vhost_3.0.2-1.dsc
 dceaa408e0bfe683bf229799dcf2c3e7cfbd35df 5497 node-vhost_3.0.2.orig.tar.gz
 275c515b9c0bb3b84523100963a760f8a588a026 2920 node-vhost_3.0.2-1.debian.tar.xz
Checksums-Sha256: 
 86a2b017d65d49ab6ca857495a53e9707012ad4ef8b09854b5b4ca5a737d9297 2037 
node-vhost_3.0.2-1.dsc
 0d8e089181103c68a7134a489531983e5b23d08096c60a2e2bb447f0c1846014 5497 
node-vhost_3.0.2.orig.tar.gz
 e4da885ca24fc5256e2994457582ae2fe8756f0165b452b0465500711e03b756 2920 
node-vhost_3.0.2-1.debian.tar.xz
Files: 
 

Bug#907766: Bug #907766 in node-chokidar marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #907766 in node-chokidar 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/node-chokidar/commit/ac24aaaf7cb5f866343cb5aca303f92d899eddf3


Switch test to pkg-js-tools and increase timeout

Closes: #907766


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/907766

Processed: Bug #907766 in node-chokidar marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #907766 [src:node-chokidar] node-chokidar: FTBFS in buster/sid (failing 
tests)
Added tag(s) pending.

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

Bug#906390: Bug #906390 in node-vhost marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #906390 in node-vhost 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/node-vhost/commit/578af473adc21ebec706163c7b5e6965a3c1143f


Add patch to clean test

Closes: #906390


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906390

Processed: Bug #906390 in node-vhost marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906390 [src:node-vhost] node-vhost: FTBFS in buster/sid (autobuilder hangs)
Added tag(s) pending.

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

Bug#877202: Bug #877202 in pyxdg marked as pending

[Simon McVittie]

On Mon, 30 Apr 2018 at 02:35:03 +, a...@debian.org wrote:
> New upstream release.
>  - Add support for Scale and ScaledDirectories keys (Closes: #877202).
>  - DesktopEntry: New method findTryExec() (Closes: #618514).
> * Drop patches applied upstream: fix-DesktopEntry-docstring.patch
>   prefer-first-glob-for-finding-mimetype.patch, and
>   fix-insecure-use-of-tmp.patch.

Is there anything that makes this version unsuitable for buster? If the
only reason it hasn't been uploaded yet is lack of time, I can look into
doing a team upload for it.

There seem to be significant changes to the menu code, so it should
probably be tested with mate-menu or ukui-menu before uploading.

Alternatively, uploading a version closely resembling the one in Ubuntu
would be a low-risk option with a minimal fix for this bug.

Thanks,
smcv

Bug#922297: rxvt-unicode: *blink* *blink* *blink*

[Jakub Wilk]

Package: rxvt-unicode
Version: 9.22-5
Severity: grave
Justification: makes my head hurt

The terminal screen blinks all the time.


-- System Information:
Architecture: i386

Versions of packages rxvt-unicode depends on:
ii  libc6 2.28-7
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-20
ii  libgdk-pixbuf2.0-02.38.0+dfsg-7
ii  libglib2.0-0  2.58.3-1
ii  libperl5.28   5.28.1-4
ii  libstartup-notification0  0.12-6
ii  libx11-6  2:1.6.7-1
ii  libxft2   2.3.2-2
ii  libxrender1   1:0.9.10-1
ii  base-passwd   3.5.46
ii  ncurses-base  6.1+20181013-2
ii  ncurses-term  6.1+20181013-2

--
Jakub Wilk

Bug#922254: marked as done (jsxgraph: FTBFS (ERROR: module path does not exist))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 10:49:24 +
with message-id 
and subject line Bug#922254: fixed in jsxgraph 1.3.5+dfsg1-2
has caused the Debian Bug report #922254,
regarding jsxgraph: FTBFS (ERROR: module path does not exist)
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.)


-- 
922254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jsxgraph
Version: 1.3.5+dfsg1-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 apache2 --with python2
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>/jsxgraph-1.3.5+dfsg1'
# add symlinks to replace node_modules utilities
#
# replace almond
mkdir -p node_modules/almond
ln -s /usr/lib/nodejs/node-almond/almond.js node_modules/almond/
mkdir -p node_modules/requirejs/bin
#ln -s /usr/lib/nodejs/r.js node_modules/requirejs/bin
mkdir -p build/bin
nodejs ./node_modules/bin/r.js -o build/core.build.json
Error: Error: ERROR: module path does not exist: 
/<>/jsxgraph-1.3.5+dfsg1/src/../node_modules/almond/almond.js for 
module named: ../node_modules/almond/almond. Path is relative to: 
/<>/jsxgraph-1.3.5+dfsg1
at /<>/jsxgraph-1.3.5+dfsg1/node_modules/bin/r.js:30214:35

make[1]: *** [Makefile:72: core] Error 1
make[1]: Leaving directory '/<>/jsxgraph-1.3.5+dfsg1'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:13: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jsxgraph.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 ---
Source: jsxgraph
Source-Version: 1.3.5+dfsg1-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated jsxgraph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Feb 2019 11:12:16 +0100
Source: jsxgraph
Binary: jsxcompressor jsxgraph
Architecture: source all
Version: 1.3.5+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 jsxcompressor - Pure Javascript implementation of deflate, unzip, base64_decode
 jsxgraph   - Interactive Geometry with JavaScript
Closes: 922254
Changes:
 jsxgraph (1.3.5+dfsg1-2) unstable; urgency=medium
 .
   * adapted the Makefile to take in account in the dependency node-almond.
 Closes: #922254
Checksums-Sha1:
 44ce104b6cbece0df0af3507e28b247a43cfe586 2102 jsxgraph_1.3.5+dfsg1-2.dsc
 3ab7bf42f873988b8e04fa4b233875f5d3eae451 204904 
jsxgraph_1.3.5+dfsg1-2.debian.tar.xz
 90c5fea72941b8c4395a985e4b5e4d40aa03ae05 342572 
jsxcompressor_1.3.5+dfsg1-2_all.deb
 d987092eb3e44cc3fffd6a8bbb934f9570a59781 6218184 jsxgraph_1.3.5+dfsg1-2_all.deb
 8ea3c8b8ba16632b73e20f33d1df12d24c3bf020 9917 
jsxgraph_1.3.5+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 7cc4a7cb7ddcf12f1b2b18fdab8fc7b472f34eb8f2c27bb75fb31df8600223ba 2102 
jsxgraph_1.3.5+dfsg1-2.dsc
 f079679d5bbb7e673a076f21af06b08bff4f79f3edc5e1ecf586badb0bd8abfa 204904 
jsxgraph_1.3.5+dfsg1-2.debian.tar.xz
 adf079565ee29e13ac8d18de6015dcacdcdabe52c9959f56c600e96fbf311f74 342572 
jsxcompressor_1.3.5+dfsg1-2_all.deb
 

Bug#921796: marked as done (node-libnpx: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 14 Feb 2019 10:49:39 +
with message-id 
and subject line Bug#921796: fixed in node-libnpx 10.2.0+repack-1
has caused the Debian Bug report #921796,
regarding node-libnpx: FTBFS (failing tests)
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.)


-- 
921796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-libnpx
Version: 10.2.0-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
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tail -n +2 README.md | marked-man --manual 'User Commands' --version 
libnpx@$(dpkg-parsechangelog -S version) > libnpx.1
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir node_modules
ln -s /usr/lib/nodejs/npm node_modules
ln -s .. node_modules/libnpx

[... snipped ...]

1..10
ok 15 - treats directory-type commands specially # time=39.876ms

# Subtest: -n and --node-arg special parsing rules
ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - should match pattern provided
ok 4 - should match pattern provided
ok 5 - should match pattern provided
ok 6 - should match pattern provided
ok 7 - should match pattern provided
ok 8 - should match pattern provided
ok 9 - should match pattern provided
ok 10 - should match pattern provided
1..10
ok 16 - -n and --node-arg special parsing rules # time=75.918ms

1..16
# time=708.137ms
ok 5 - test/parse-args.js # time=2287.591ms

# Subtest: test/util.js
# Subtest: promisify with existing util.promisify
ok 1 - used existing promisify fn
1..1
ok 1 - promisify with existing util.promisify # time=33.67ms

# Subtest: promisify without existing util.promisify
ok 1 - got a thenable
ok 2 - value passed through successfully
ok 3 - got the error!
1..3
ok 2 - promisify without existing util.promisify # time=22.968ms

1..2
# time=109.629ms
ok 6 - test/util.js # time=1657.342ms

1..6
# failed 1 of 6 tests
# time=49363.288ms
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 123
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-libnpx.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 ---
Source: node-libnpx
Source-Version: 10.2.0+repack-1

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-libnpx 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, 14 Feb 2019 11:13:16 +0100
Source: node-libnpx
Binary: node-libnpx
Architecture: source
Version: 10.2.0+repack-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 920468 921796
Description: 
 node-libnpx - support library for npx
Changes:
 node-libnpx (10.2.0+repack-1) unstable; urgency=medium
 .
   * Team upload
   * Repack to embed components
   * Add 

Bug#908815: [libdmtx0a] Structs in dmtx.h have changed without new ABI number

[Simon McVittie]

On Fri, 14 Sep 2018 at 12:24:52 +0200, Sven Schmidt wrote:
> In header file dmtx.h the structs and enumeration in version 0.7.5 have
> changed to insert a new varible "fnc1" representing undefinded state. 
> 
> When loading older DMTX binary linked against new libdmtx.so the program
> will crash with SIGSEGV. Same happens when loading newly compiled binary
> with DMTX library version < 0.7.5.
> 
> Both versions 0.7.4 and 0.7.5 are using the same ABI number for
> their library version: libdmtx.so -> libdmtx.so.0.0.0 
> 
> I think it is a good idea to increase ABI number of DMTX version 0.7.5
> to prevent loading wrong library version of libdmtx.so. 

Has there been any progress on resolving this for the buster release?

If the SONAME is not increased upstream (which doesn't seem likely to
happen soon), then the ABI break should be worked around in Debian by
renaming libdmtx0a to libdmtx0b with Conflicts: libdmtx0a, similar to
what was done for the transition from libdmtx0 to libdmtx0a. After doing
this, the release team will need to trigger rebuilds for everything that
depends on libdmtx0a.

Thanks,
smcv

Bug#921299: It is not caffe that is broken

[Andreas Tille]

Control: tags -1 moreinfo
Control: reassign -1 doxygen
Control: retitle -1 "Doxygen breaks caffe"

Hi,

I've build caffe with latest doxygen and can not confirm the result you
wrote.  The Build-Depends: doxygen-latex ensures that the style file
`listofitems.sty' is available.  I rather get a different error:

...
[40] [41]
! Improper \prevdepth.
\tabu@verticalspacing ...tempdimc \the \prevdepth 
  \@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
  

? 
! Emergency stop.
\tabu@verticalspacing ...tempdimc \the \prevdepth 
  \@tempdima \dimexpr \ht \t...
l.136 \end{DoxyParams}
  

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[2]: *** [Makefile:8: refman.pdf] Error 1


So yes, caffe is broken by doxygen but as far as I can see this is since
doxygen is breaking *lots* of other packages and it is always in the
same manner.  Thus I'm reassigning this bug to doxygen.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: It is not caffe that is broken

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #921299 [src:caffe] caffe: FTBFS with upcoming doxygen 1.8.15
Added tag(s) moreinfo.
> reassign -1 doxygen
Bug #921299 [src:caffe] caffe: FTBFS with upcoming doxygen 1.8.15
Bug reassigned from package 'src:caffe' to 'doxygen'.
No longer marked as found in versions caffe/1.0.0+git20180821.99bd997-2.
Ignoring request to alter fixed versions of bug #921299 to the same values 
previously set
> retitle -1 "Doxygen breaks caffe"
Bug #921299 [doxygen] caffe: FTBFS with upcoming doxygen 1.8.15
Changed Bug title to '"Doxygen breaks caffe"' from 'caffe: FTBFS with upcoming 
doxygen 1.8.15'.

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

Bug#896596: poppler-glib always returns 0 length for PopplerInputStream

[Simon McVittie]

Control: tags -1 + patch

On Sat, 28 Apr 2018 at 20:59:16 +0900, d...@debian.org wrote:
> original bug report: https://bugs.debian.org/896596
> previous forwarded: https://github.com/ruby-gnome2/ruby-gnome2/issues/1159
> 
> below comments and patch by Kouhei Sutou .
> 
> > Poppler adds getLength() check at
> > https://cgit.freedesktop.org/poppler/poppler/commit/?id=a59f61641fcb36859b625749afb4561557e419f6
> > for https://bugs.freedesktop.org/show_bug.cgi?id=103552 .
> > But PopplerInputStream created by poppler-glib always returns 0 for 
> > getLength():
> > https://cgit.freedesktop.org/poppler/poppler/tree/glib/poppler-document.cc#n301

Thanks for this diagnosis. It seems correct.

> > Ah, we can just use the length passed by argument:
> -str = new PopplerInputStream(stream, cancellable, 0, gFalse, 0, 
> Object(objNull));
> +str = new PopplerInputStream(stream, cancellable, 0, gFalse, length, 
> Object(objNull));

That doesn't actually work, because the function is documented to accept
-1 as a length (meaning "find the length automatically").

> > We'll be able to compute length by g_seekable_seek(0, G_SEEK_END) and
> > g_seekable_tell().

That's what I've done in the case where the caller used -1. The function
already requires that the stream is seekable, so it seems safe to assume
that this works.

Proposed patches attached. I've included a fairly minimal reproducer for
the bug, as a patch to the existing autopkgtest.

Also available as a merge request, here:
https://salsa.debian.org/freedesktop-team/poppler/merge_requests/1

Patch proposed upstream here:
https://gitlab.freedesktop.org/poppler/poppler/merge_requests/189

smcv
>From 739c81306bf0d58c857d6d664f63eaaa8d4c7317 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 14 Feb 2019 09:45:52 +
Subject: [PATCH 1/3] Add patch to fix poppler_document_new_from_stream()
 regression

Closes: #896596
---
 ...ate-PopplerInputStream-with-length-0.patch | 36 +++
 debian/patches/series |  1 +
 2 files changed, 37 insertions(+)
 create mode 100644 debian/patches/glib-Don-t-create-PopplerInputStream-with-length-0.patch

diff --git a/debian/patches/glib-Don-t-create-PopplerInputStream-with-length-0.patch b/debian/patches/glib-Don-t-create-PopplerInputStream-with-length-0.patch
new file mode 100644
index 000..c59de03
--- /dev/null
+++ b/debian/patches/glib-Don-t-create-PopplerInputStream-with-length-0.patch
@@ -0,0 +1,36 @@
+From: Simon McVittie 
+Date: Thu, 14 Feb 2019 09:43:32 +
+Subject: glib: Don't create PopplerInputStream with length 0
+
+Since commit a59f6164, PopplerInputStream requires a nonzero length.
+
+Loosely based on an earlier patch by Kouhei Sutou. This version adds
+support for length == -1, which is documented to work.
+
+Bug: https://gitlab.freedesktop.org/poppler/poppler/issues/414
+Bug-Debian: https://bugs.debian.org/896596
+Forwarded: https://gitlab.freedesktop.org/poppler/poppler/merge_requests/189
+---
+ glib/poppler-document.cc | 9 -
+ 1 file changed, 8 insertions(+), 1 deletion(-)
+
+diff --git a/glib/poppler-document.cc b/glib/poppler-document.cc
+index ed37da4c..e04c8b42 100644
+--- a/glib/poppler-document.cc
 b/glib/poppler-document.cc
+@@ -309,7 +309,14 @@ poppler_document_new_from_stream (GInputStream *stream,
+   }
+ 
+   if (stream_is_memory_buffer_or_local_file(stream)) {
+-str = new PopplerInputStream(stream, cancellable, 0, false, 0, Object(objNull));
++if (length == (goffset)-1) {
++  if (!g_seekable_seek(G_SEEKABLE(stream), 0, G_SEEK_END, cancellable, error)) {
++g_prefix_error(error, "Unable to determine length of stream: ");
++return nullptr;
++  }
++  length = g_seekable_tell(G_SEEKABLE(stream));
++}
++str = new PopplerInputStream(stream, cancellable, 0, false, length, Object(objNull));
+   } else {
+ CachedFile *cachedFile = new CachedFile(new PopplerCachedFileLoader(stream, cancellable, length), new GooString());
+ str = new CachedFileStream(cachedFile, 0, false, cachedFile->getLength(), Object(objNull));
diff --git a/debian/patches/series b/debian/patches/series
index d3a4373..6fed9f7 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
+glib-Don-t-create-PopplerInputStream-with-length-0.patch
 #qt-visibility.diff
-- 
2.20.1

>From ebfd76c4664b43ba19185d2109532395724c7ff9 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 14 Feb 2019 09:35:58 +
Subject: [PATCH 2/3] d/tests/glib: Add a test for #896596

---
 debian/tests/glib|  2 ++
 debian/tests/test-glib.c | 45 
 2 files changed, 47 insertions(+)

diff --git a/debian/tests/glib b/debian/tests/glib
index 7ad9ce4..5113160 100755
--- a/debian/tests/glib
+++ b/debian/tests/glib
@@ -5,3 +5,5 @@ SRCDIR=$(dirname $(realpath $0))
 cd $ADTTMP
 gcc -Wall -Werror -std=c99 -o poppler-glib-test $SRCDIR/test-glib.c `pkg-config --cflags --libs poppler-glib`
 

Processed: Re: Bug#896596: poppler-glib always returns 0 length for PopplerInputStream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #896596 [libpoppler-glib8] poppler-glib always returns 0 length for 
PopplerInputStream
Bug #897464 [libpoppler-glib8] ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: 
Error: test: time(PDFSurfaceTest::#set_metadata::modified date): 
Poppler::Error::Invalid: Failed to load document
Added tag(s) patch.
Added tag(s) patch.

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