Bug#890859: Bug #890859 in tempest marked as pending

[thomas]

Control: tag -1 pending

Hello,

Bug #890859 in tempest 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/openstack-team/libs/tempest/commit/015b7eef50b674a29815c5d4a07d3d1dae8bff70


Cleans properly (Closes: #890859).



(this message was generated automatically)
-- 
Greetings

Processed: Bug #890859 in tempest marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890859 [src:tempest] tempest: fails to clean after build: rm: cannot 
remove '.testrepository': Is a directory
Added tag(s) pending.

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

Processed: Bug #890859 in tempest marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890859 [src:tempest] tempest: fails to clean after build: rm: cannot 
remove '.testrepository': Is a directory
Ignoring request to alter tags of bug #890859 to the same tags previously set

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

Bug#890859: Bug #890859 in tempest marked as pending

[thomas]

Control: tag -1 pending

Hello,

Bug #890859 in tempest 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/openstack-team/libs/tempest/commit/015b7eef50b674a29815c5d4a07d3d1dae8bff70


Cleans properly (Closes: #890859).



(this message was generated automatically)
-- 
Greetings

Bug#890856: marked as done (python-saharaclient: FTBFS: fails during override_dh_auto_test)

[Debian Bug Tracking System]

Your message dated Tue, 20 Feb 2018 07:49:28 +
with message-id 
and subject line Bug#890856: fixed in python-saharaclient 1.5.0-2
has caused the Debian Bug report #890856,
regarding python-saharaclient: FTBFS: fails during override_dh_auto_test
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.)


-- 
890856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-saharaclient
Version: 1.5.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-saharaclient/experimental FTBFS in a current minimal sid+experimental 
environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-saharaclient-1.5.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pkgos-dh_auto_test 'saharaclient\.tests\.unit.*'
+ PKGOS_USE_PY2=yes
+ PKGOS_USE_PY3=yes
+ PYTHONS=disabled
+ PYTHON3S=disabled
+ [ yes = yes ]
+ PYTHONS=2.7
+ [ yes = yes ]
+ py3versions -vr
+ PYTHON3S=3.6
+ [ 2.7 = disabled ]
+ cut -d. -f1
+ echo 2.7
+ PYMAJOR=2
+ echo ===> Testing with python (python2)
===> Testing with python (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.XWGlAn70HN
+ subunit2pyunit
+ tee /tmp/tmp.XWGlAn70HN
+ pwd
+ PYTHONPATH=/build/python-saharaclient-1.5.0 PYTHON=python2.7 testr-python2 
run --subunit saharaclient\.tests\.unit.*
No .testr.conf config file

--
Ran 0 tests in 0.033s

OK
+ cat /tmp/tmp.XWGlAn70HN
+ subunit-filter -s --no-passthrough
+ subunit-stats
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.XWGlAn70HN
+ testr-python2 slowest
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 3
make[1]: Leaving directory '/build/python-saharaclient-1.5.0'
make: *** [debian/rules:6: build] Error 2


Andreas


python-saharaclient_1.5.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-saharaclient
Source-Version: 1.5.0-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Feb 2018 07:30:38 +
Source: python-saharaclient
Binary: python-saharaclient python-saharaclient-doc python3-saharaclient
Architecture: source all
Version: 1.5.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-saharaclient - Client library for Openstack Sahara API server - Python 
2.7 modul
 python-saharaclient-doc - Client library for Openstack Sahara API server - 
documentation
 python3-saharaclient - Client library for Openstack Sahara API server - Python 
3.x modul
Closes: 890856
Changes:
 python-saharaclient (1.5.0-2) experimental; urgency=medium
 .
   * Fixed minimum version of openstack-pkg-tools to 66~ to support stestr,
 as this is what saharaclient uses now (Closes: #890856).
   * Bumped debhelper to 10.
Checksums-Sha1:
 0d94960f2fa12f15c46ff643ed3fb94cc6ac4ab8 3445 python-saharaclient_1.5.0-2.dsc
 9a8860947410c81caa8d114a5bc2433f3b635e70 3728 
python-saharaclient_1.5.0-2.debian.tar.xz
 fd41424cb7d99b9f8a807d4b775203f776446926 943276 
python-saharaclient-doc_1.5.0-2_all.deb
 163de1820ac52dcb08a2f6b8baf2722667ebdd01 65012 
python-saharaclient_1.5.0-2_all.deb
 6937f88afdf0e4b8e05c5a043574273655e86103 16724 
python-saharaclient_1.5.0-2_amd64.buildinfo
 85aa8f45fcca0c8a2ac748f614464767b3210cd3 53536 
python3-saharaclient_1.5.0-2_all.deb
Checksums-Sha256:
 

Processed: Bug #890856 in python-saharaclient marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890856 {Done: Thomas Goirand } [src:python-saharaclient] 
python-saharaclient: FTBFS: fails during override_dh_auto_test
Ignoring request to alter tags of bug #890856 to the same tags previously set

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

Bug#890856: Bug #890856 in python-saharaclient marked as pending

[thomas]

Control: tag -1 pending

Hello,

Bug #890856 in python-saharaclient 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/openstack-team/clients/python-saharaclient/commit/7047621ca6625ec4731dfcbfa353521fb95009f9


  * Fixed minimum version of openstack-pkg-tools to 66~ to support stestr,
as this is what saharaclient uses now (Closes: #890856).
  * Bumped debhelper to 10.



(this message was generated automatically)
-- 
Greetings

Processed: Bug#889872: show-ip: load fails: TypeError: Object is NM.IPAddress.prototype, not an object instance - cannot convert to a boxed instance

[Debian Bug Tracking System]

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

> severity 889872 important
Bug #889872 [gnome-shell-extension-show-ip] show-ip: load fails: TypeError: 
Object is NM.IPAddress.prototype, not an object instance - cannot convert to a 
boxed instance
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#890856: python-saharaclient: FTBFS: fails during override_dh_auto_test

[Thomas Goirand]

On 02/19/2018 11:28 PM, Andreas Beckmann wrote:
> Source: python-saharaclient
> Version: 1.5.0-1
> Severity: serious
> Justification: fails to build from source
> 
> Hi,
> 
> python-saharaclient/experimental FTBFS in a current minimal sid+experimental 
> environment:
> 
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/python-saharaclient-1.5.0'
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test 'saharaclient\.tests\.unit.*'
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + [ yes = yes ]
> + PYTHONS=2.7
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.6
> + [ 2.7 = disabled ]
> + cut -d. -f1
> + echo 2.7
> + PYMAJOR=2
> + echo ===> Testing with python (python2)
> ===> Testing with python (python2)
> + rm -rf .testrepository
> + testr-python2 init
> + mktemp -t
> + TEMP_REZ=/tmp/tmp.XWGlAn70HN
> + subunit2pyunit
> + tee /tmp/tmp.XWGlAn70HN
> + pwd
> + PYTHONPATH=/build/python-saharaclient-1.5.0 PYTHON=python2.7 testr-python2 
> run --subunit saharaclient\.tests\.unit.*
> No .testr.conf config file

Hi Andreas,

The build log above shows that you've built python-saharaclient with an
outdated version of openstack-pkg-tools, which doesn't support stestr
(but only testr).

I'll bumped the minimum version in build-depends and re-upload.

Cheers,

Thomas Goirand (zigo)

Processed: Bug #890856 in python-saharaclient marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890856 {Done: Thomas Goirand } [src:python-saharaclient] 
python-saharaclient: FTBFS: fails during override_dh_auto_test
Added tag(s) pending.

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

Bug#890856: Bug #890856 in python-saharaclient marked as pending

[thomas]

Control: tag -1 pending

Hello,

Bug #890856 in python-saharaclient 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/openstack-team/clients/python-saharaclient/commit/7047621ca6625ec4731dfcbfa353521fb95009f9


  * Fixed minimum version of openstack-pkg-tools to 66~ to support stestr,
as this is what saharaclient uses now (Closes: #890856).
  * Bumped debhelper to 10.



(this message was generated automatically)
-- 
Greetings

Processed (with 1 error): Bug#889872: show-ip: load fails: TypeError: Object is NM.IPAddress.prototype, not an object instance - cannot convert to a boxed instance

[Debian Bug Tracking System]

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

> tags 889872 + unreproducible
Bug #889872 [gnome-shell-extension-show-ip] show-ip: load fails: TypeError: 
Object is NM.IPAddress.prototype, not an object instance - cannot convert to a 
boxed instance
Added tag(s) unreproducible.
> tags 889872 + moreinfo
Bug #889872 [gnome-shell-extension-show-ip] show-ip: load fails: TypeError: 
Object is NM.IPAddress.prototype, not an object instance - cannot convert to a 
boxed instance
Added tag(s) moreinfo.
> severity 88972 important
Failed to set severity of Bug 88972 to important: Not altering archived bugs; 
see unarchive.

> thanks
Stopping processing here.

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

Bug#889872: show-ip: load fails: TypeError: Object is NM.IPAddress.prototype, not an object instance - cannot convert to a boxed instance

[Kyle Robbertze]

I am unable to reproduce this in a clean unstable VM with the extension
shown in the application bar and when it is in the dropdown menu.

What version of libnm are you using?

Cheers
Kyle

Bug#890517: killer's CRON logs out users once per hour

[Petter Reinholdtsen]

[Wolfgang Schweer]
> IIRC, for connections to a system that runs Nomachine technology (not
> part of Debian) the utmp/wtmp files are not used by design (on the
> system running NX server). Instead, NX keeps track of the forwarded
> sessions itself.

Updating utmp/wtmp is not only for 'keeping track of sessions', it is
also used by shutdown and other systems to know who to notify when
taking down a host or notify logged in users in other cases.  If NX do
not update utmp/wtmp for logged in users, I would claim that NX is
broken, and if it is by design, then NX is broken by design.

-- 
Happy hacking
Petter Reinholdtsen

Bug#888072: marked as done (volume-key FTBFS with cryptsetup 2:2.0.0-1)

[Debian Bug Tracking System]

Your message dated Tue, 20 Feb 2018 03:37:46 +
with message-id 
and subject line Bug#888072: fixed in volume-key 0.3.9-2
has caused the Debian Bug report #888072,
regarding volume-key FTBFS with cryptsetup 2:2.0.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.)


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

https://buildd.debian.org/status/package.php?p=volume-key=sid

...
lib/volume_luks.c: In function 'error_from_cryptsetup':
lib/volume_luks.c:72:3: warning: implicit declaration of function 
'crypt_get_error'; did you mean 'crypt_get_dir'? 
[-Wimplicit-function-declaration]
   crypt_get_error (crypt_msg, sizeof (crypt_msg));
   ^~~
...
/bin/bash ./libtool --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wall -W -Wcast-align -Wmissing-noreturn 
-Wnested-externs -Wpointer-arith -Wshadow -Wundef -Wwrite-strings  -Wl,-z,relro 
-o src/volume_key src/src_volume_key-volume_key.o lib/libvolume_key.la 
-lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 
libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -W -Wcast-align 
-Wmissing-noreturn -Wnested-externs -Wpointer-arith -Wshadow -Wundef 
-Wwrite-strings -Wl,-z -Wl,relro -o src/.libs/volume_key 
src/src_volume_key-volume_key.o  lib/.libs/libvolume_key.so 
-L/usr/lib/x86_64-linux-gnu -lblkid -lgpgme -lassuan 
/usr/lib/x86_64-linux-gnu/libgpg-error.so -lcryptsetup -lglib-2.0 -lnss3 
-lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4
lib/.libs/libvolume_key.so: undefined reference to `crypt_get_error'
collect2: error: ld returned 1 exit status
Makefile:664: recipe for target 'src/volume_key' failed
make[3]: *** [src/volume_key] Error 1
--- End Message ---
--- Begin Message ---
Source: volume-key
Source-Version: 0.3.9-2

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated volume-key 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: Mon, 19 Feb 2018 22:10:33 -0500
Source: volume-key
Binary: libvolume-key1 libvolume-key-dev python-volume-key volume-key
Architecture: source
Version: 0.3.9-2
Distribution: unstable
Urgency: high
Maintainer: Utopia Maintenance Team 

Changed-By: Jeremy Bicha 
Description:
 libvolume-key-dev - Library for manipulating storage encryption keys and 
passphrases
 libvolume-key1 - Utility for manipulating storage encryption keys and 
passphrases
 python-volume-key - Python bindings for libvolume_key
 volume-key - Utility for manipulating storage encryption keys and passphrases
Closes: 888072
Changes:
 volume-key (0.3.9-2) unstable; urgency=high
 .
   [ Andreas Henriksson ]
   * Remove myself from uploaders
   * Add upstream patch to fix build with cryptsetup 2.x (Closes: #888072)
   * Fix lintian warning about autotools-dev
 .
   [ Jeremy Bicha ]
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Bump debhelper compat to 11
   * Bump Standards-Version to 4.1.3
   * Add symbols file
Checksums-Sha1:
 14d583f97aa82d6718cec13fdd0a749e24fa43e3 2208 volume-key_0.3.9-2.dsc
 49e9d8b3fa454c6c99917443f5d14b35057b6937 6736 volume-key_0.3.9-2.debian.tar.xz
 1c5e7d1d380e2af873cc263f1121129d8224d935 8045 
volume-key_0.3.9-2_source.buildinfo
Checksums-Sha256:
 c97ae1fd62b54a084b9acdf69e8d7899c83642cc442416350d08dc9625c8c651 2208 
volume-key_0.3.9-2.dsc
 47480bc9d77d5d8cb0d00ec24da1aee2c0029da6796b17d4ed9c225e8ac8bba7 6736 
volume-key_0.3.9-2.debian.tar.xz
 b472b0faf23ee4cb198e30f1cc87e0a4a6f703625692c89323a509937470f4c5 8045 
volume-key_0.3.9-2_source.buildinfo
Files:
 71f4ce02b732c8b402d27a1e9afe5507 2208 utils optional volume-key_0.3.9-2.dsc
 

Bug#887865: marked as done (shimdandy FTBFS with libclojure-java 1.9.0~alpha15-1)

[Debian Bug Tracking System]

Your message dated Tue, 20 Feb 2018 03:14:34 +
with message-id 
and subject line Bug#887865: fixed in shimdandy 1.2.0-2
has caused the Debian Bug report #887865,
regarding shimdandy FTBFS with libclojure-java 1.9.0~alpha15-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.)


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

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

...
[WARNING] The POM for org.clojure:clojure:jar:1.8.x is missing, no dependency 
information available
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] shimdandy-api .. SUCCESS [  2.595 s]
[INFO] shimdandy-impl . FAILURE [  0.013 s]
[INFO] shimdandy-parent ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.847 s
[INFO] Finished at: 2019-02-18T00:38:30-12:00
[INFO] Final Memory: 17M/591M
[INFO] 
[ERROR] Failed to execute goal on project shimdandy-impl: Could not resolve 
dependencies for project org.projectodd.shimdandy:shimdandy-impl:jar:1.2.0: 
Cannot access central (https://repo.maven.apache.org/maven2) in offline mode 
and the artifact org.clojure:clojure:jar:1.8.x has not been downloaded from it 
before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :shimdandy-impl
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/shimdandy-1.2.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/shimdandy-1.2.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/shimdandy-1.2.0/debian 
-Dmaven.repo.local=/build/1st/shimdandy-1.2.0/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Source: shimdandy
Source-Version: 1.2.0-2

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

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

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

Debian distribution maintenance software
pp.
Tom Marble  (supplier of updated shimdandy 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: Mon, 19 Feb 2018 14:39:55 -0600
Source: shimdandy
Binary: libshimdandy-java
Architecture: source all
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Tom Marble 
Description:
 libshimdandy-java - Shim wrapping multiple Clojure runtimes into the same JVM
Closes: 887865
Changes:
 shimdandy (1.2.0-2) unstable; urgency=medium
 .
   [ Tom Marble ]
   * Update Clojure support to 1.9 in unstable (Closes: #887865)
 .
   [ tony mancill ]
   * Update build-dep on libclojure-java to require 1.9
   * Use debhelper 11
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 ff4fea05dbfded3a3be6bf794284d53bdc3ccede 2040 

Bug#890621: python3-keyrings.alt 2.2-2 module.__file__ is None, causing regrtest.py to fail

[Ron Lovell]

If I'm following correctly, it appears the issue with python3-keyrings.alt
and libpython3.6-testsuite could be resolved with this change to
libregrtest/setup.py:

60c60
< if hasattr(module, '__file__'):
---
> if getattr(module, '__file__', None):

That works as before for missing __file__, and it works as desired for
module object 'keyrings' where __file__ == None when imported to python3.6.

Currently for python3.7 (beta 1) in Sid, no fix is needed in
libpython3.7-testsuite, since module object 'keyrings' has no __file__
attribute when imported to python3.7 beta 1. But to simplify and to handle
future cases, I think you will want to modify the 3.7 regression tests
setup.py as well.

Thanks all for the great work on this.
Ron
-- 
James Ronald Lovell 
Huntsville, AL, USA

Processed: bug 880276 is forwarded to https://github.com/attr-encrypted/encryptor/issues/31

[Debian Bug Tracking System]

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

> forwarded 880276 https://github.com/attr-encrypted/encryptor/issues/31
Bug #880276 [src:ruby-encryptor] test using GCM with IV option fails after fix 
for CVE-2016-7798
Set Bug forwarded-to-address to 
'https://github.com/attr-encrypted/encryptor/issues/31'.
> thanks
Stopping processing here.

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

Processed: tagging 880276

[Debian Bug Tracking System]

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

> tags 880276 + upstream
Bug #880276 [src:ruby-encryptor] test using GCM with IV option fails after fix 
for CVE-2016-7798
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#890859: tempest: fails to clean after build: rm: cannot remove '.testrepository': Is a directory

[Andreas Beckmann]

Source: tempest
Version: 1:17.2.0-1
Severity: serious
Justification: fails to build from source

Hi,

tempest/experimental FTBFS twice in a row since 'debian/rules clean'
fails after the first (and successful) build:

 fakeroot debian/rules clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --buildsystem=python_distutils --with python2,python3,sphinxdoc
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/tempest-17.2.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh_auto_clean -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py clean -a
running clean
removing 'build/lib.linux-x86_64-2.7' (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
find . -name \*.pyc -exec rm {} \+
rm -f .testrepository
rm: cannot remove '.testrepository': Is a directory
make[1]: *** [debian/rules:18: override_dh_auto_clean] Error 1
make[1]: Leaving directory '/build/tempest-17.2.0'
make: *** [debian/rules:14: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


Andreas


tempest_1%17.2.0-1_twice.log.gz
Description: application/gzip

Processed: node-source-map has been downgraded to 0.6.1 for now

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #888943 [node-concat-with-sourcemaps] node-concat-with-sourcemaps FTBFS 
with node-source-map 0.7
Severity set to 'important' from 'serious'

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

Bug#889608: Continuing to get core dumps with man-db

[John Sivak]

I can confirm that removing the ESET antivirus software eliminates the
error with man.

Also, I saw this text in the ESET user guide at
https://download.eset.com/com/eset/apps/home/eav/linux/latest/eset_eav_lin_4_userguide_enu.pdf:

NOTE:  SELINUX  AND  APPARMOR  ARE  NOT  SUPPORTED.  THEY
HAVE  TO  BE  DISABLED  PRIOR  TO  INSTALLING  ESET  NOD32
ANTIVIRUS.

Let me know if you want to continue debugging this or close the issue
since it seems to be caused by the ESET software.

Thanks for your help and assistance with this issue.

John

On 02/19/2018 05:34 PM, John Sivak wrote:
> On 02/19/2018 05:59 AM, Colin Watson wrote:
>> On Mon, Feb 19, 2018 at 10:15:47AM +, Colin Watson wrote:
>>> Do you have an unusual libc or a modified libpipeline or something?  The
>>> sequence of system calls that your trace shows at the point where
>>> libpipeline should be calling execvp for nroff doesn't correspond to any
>>> libc implementation I can find, and the failure comes when it tries to
>>> open a Unix-domain socket in the middle of the execvp sequence which is
>>> just weird.
>> Ah, you're using an antivirus program.  Do mention that in bug reports
>> in future, since I spent a non-trivial amount of time digging to find
>> this out!  Please try git master, which has this patch:
>>
>>   
>> https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=6ed6c9f92ab8f981aa1aa664f7e607bcd540ad44
>>
> Many apologies; hadn't thought about Antivirus being a factor.
>
> I've build the man-db package you linked to using the Archlinux package
> script and am still getting the error.
>
> New stack trace is attached.  I will also remove the ESET antivirus to
> see if that is causing the conflict as well.

Processed: node-source-map has been downgraded to 0.6.1 for now

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #888944 [node-css] node-css FTBFS with node-source-map 0.7
Severity set to 'important' from 'serious'

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

Bug#888846: node-source-map has been downgraded to 0.6.1 for now

[Adrian Bunk]

Control: severity -1 important

node-source-map has been downgraded to 0.6.1 for now,
lowering the severity.

cu
Adrian

-- 

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

Processed: node-source-map has been downgraded to 0.6.1 for now

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #46 [node-webpack-sources] node-webpack-sources FTBFS with 
node-source-map 0.7.0+dfsg-1
Severity set to 'important' from 'serious'

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

Processed: node-source-map has been downgraded to 0.6.1 for now

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #888945 [ruby-uglifier] ruby-uglifier FTBFS with node-source-map 0.7
Severity set to 'important' from 'serious'

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

Bug#890857: libosmo-sigtran-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/osmocom/sigtran/m2ua_types.h

[Andreas Beckmann]

Package: libosmo-sigtran-dev
Version: 0.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libosmo-sigtran-dev:amd64.
  Preparing to unpack .../19-libosmo-sigtran-dev_0.8.1-1_amd64.deb ...
  Unpacking libosmo-sigtran-dev:amd64 (0.8.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-LyBakM/19-libosmo-sigtran-dev_0.8.1-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/osmocom/sigtran/m2ua_types.h', which is 
also in package libosmo-sccp-dev:amd64 0.7.0-4
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-LyBakM/19-libosmo-sigtran-dev_0.8.1-1_amd64.deb


cheers,

Andreas


libosmo-sccp-dev=0.7.0-4_libosmo-sigtran-dev=0.8.1-1.log.gz
Description: application/gzip

Bug#890856: python-saharaclient: FTBFS: fails during override_dh_auto_test

[Andreas Beckmann]

Source: python-saharaclient
Version: 1.5.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-saharaclient/experimental FTBFS in a current minimal sid+experimental 
environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-saharaclient-1.5.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pkgos-dh_auto_test 'saharaclient\.tests\.unit.*'
+ PKGOS_USE_PY2=yes
+ PKGOS_USE_PY3=yes
+ PYTHONS=disabled
+ PYTHON3S=disabled
+ [ yes = yes ]
+ PYTHONS=2.7
+ [ yes = yes ]
+ py3versions -vr
+ PYTHON3S=3.6
+ [ 2.7 = disabled ]
+ cut -d. -f1
+ echo 2.7
+ PYMAJOR=2
+ echo ===> Testing with python (python2)
===> Testing with python (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.XWGlAn70HN
+ subunit2pyunit
+ tee /tmp/tmp.XWGlAn70HN
+ pwd
+ PYTHONPATH=/build/python-saharaclient-1.5.0 PYTHON=python2.7 testr-python2 
run --subunit saharaclient\.tests\.unit.*
No .testr.conf config file

--
Ran 0 tests in 0.033s

OK
+ cat /tmp/tmp.XWGlAn70HN
+ subunit-filter -s --no-passthrough
+ subunit-stats
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.XWGlAn70HN
+ testr-python2 slowest
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 3
make[1]: Leaving directory '/build/python-saharaclient-1.5.0'
make: *** [debian/rules:6: build] Error 2


Andreas


python-saharaclient_1.5.0-1.log.gz
Description: application/gzip

Bug#890854: libctl: FTBFS during binary-indep-only build: cp: cannot create regular file 'debian/libctl-dev/usr/share/doc/libctl-dev/README': No such file or directory

[Andreas Beckmann]

Source: libctl
Version: 4.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libctl/experimental FTBFS during a binary-indep only build:

   debian/rules override_dh_installdocs
make[1]: Entering directory '/build/libctl-4.0.0'
dh_installdocs
mkdir -p debian/libctl-doc/usr/share/doc/libctl-doc
cp AUTHORS debian/libctl-doc/usr/share/doc/libctl-doc/AUTHORS
cp NEWS.md debian/libctl-doc/usr/share/doc/libctl-doc/NEWS
cp README.md debian/libctl-dev/usr/share/doc/libctl-dev/README
cp: cannot create regular file 
'debian/libctl-dev/usr/share/doc/libctl-dev/README': No such file or directory
make[1]: *** [debian/rules:22: override_dh_installdocs] Error 1
make[1]: Leaving directory '/build/libctl-4.0.0'
make: *** [debian/rules:12: binary-indep] Error 2

You probably need to split override_dh_installdocs into
override_dh_installdocs-arch and override_dh_installdocs-indep


Andreas


libctl_4.0.0-1_indep.log.gz
Description: application/gzip

Processed: Re: Bug#885744: mdbtools-gmdb: Depends on libgnomeui

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +help
Bug #885744 [mdbtools-gmdb] mdbtools-gmdb: Depends on libgnomeui
Added tag(s) help.

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

Bug#885744: mdbtools-gmdb: Depends on libgnomeui

[Jean-Michel Vourgère]

Control: tags -1 +help

I'm unable to port gmdb to gtk-3. Mostly by lack of knowledge.

If someone propose a patch, I can very probably push it upstream, that would 
be nice.

My plan is to remove gmdb package and to package only the drivers and command 
line tools. Honestly, I boldly guess most people are using the gui to export 
the data to another free database system, and that can be accomplished using 
the command line.

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

Bug#890853: mssh FTBFS: error: 'gtk_font_button_get_font_name' is deprecated

[Adrian Bunk]

Source: mssh
Version: 2.2-4
Severity: serious

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

...
gcc -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I..  -pthread 
-I/usr/include/vte-2.91 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/gtk-3.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/gio-unix-2.0/ -I/usr/include/p11-kit-1 
-I/usr/include/gconf/2 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wall -Wfatal-errors -Wwrite-strings -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o mssh-pref.o mssh-pref.c
mssh-pref.c: In function 'mssh_pref_font_select':
mssh-pref.c:34:5: error: 'gtk_font_button_get_font_name' is deprecated 
[-Werror=deprecated-declarations]
 font = gtk_font_button_get_font_name(GTK_FONT_BUTTON(widget));
 ^~~~
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors
make[3]: *** [Makefile:378: mssh-pref.o] Error 1

Bug#890852: direnv FTBFS with golang-1.10-go: Printf format %/ has unknown verb /

[Adrian Bunk]

Source: direnv
Version: 2.14.0-1
Severity: serious

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

...
   dh_auto_test
make -j16 test
make[1]: Entering directory '/build/1st/direnv-2.14.0'
go test
go: disabling cache (/nonexistent/first-build/.cache/go-build) due to 
initialization failure: mkdir /nonexistent: permission denied
# _/build/1st/direnv-2.14.0
./cmd_stdlib.go:17: Printf format %/ has unknown verb /
FAIL_/build/1st/direnv-2.14.0 [build failed]
make[1]: *** [Makefile:51: test] Error 2

Bug#890851: lambda-align FTBFS on 32bit and big endian: 80 tests failed out of 80

[Adrian Bunk]

Source: lambda-align
Version: 1.0.3-1
Severity: serious

https://buildd.debian.org/status/package.php?p=lambda-align=sid

...
0% tests passed, 80 tests failed out of 80



It seems running the unit tests revealed that the package
currently only works on 64bit little endian.

Bug#890811: marked as done (lynx: FTBFS: msgfmt errors)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 21:36:19 +
with message-id 
and subject line Bug#890811: fixed in lynx 2.8.9dev16-3
has caused the Debian Bug report #890811,
regarding lynx: FTBFS: msgfmt errors
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.)


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

>From my pbuilder build log:

...
   dh_auto_build
   make -j8
make[1]: Entering directory '/build/lynx-2.8.9dev16'
/bin/sh -c 'SHELL=/bin/sh /bin/sh ./scripts/cfg_defs.sh .'
Constructing sed-script help_files.sed
echo 
's!''http://lynx.invisible-island.net/release/breakout'/lynx_help/'alphatoc.html!alphatoc.html!g'
>> help_files.tmp
echo 
's!''http://lynx.invisible-island.net/release/breakout'/lynx_help/'cattoc.html!cattoc.html!g'
>> help_files.tmp
echo 's!alphatoc\.html!alphatoc.html.gz!g' >> help_files.tmp
echo 's!cattoc\.html!cattoc.html.gz!g' >> help_files.tmp
echo 's!body\.html!body.html.gz!g' >> help_files.tmp
sed -e '/^#/d' -e '/^$/d' \
   -e 's%\(.*\)=\(.*\@.*\)$%s=@\1@=\2=g%' \
   -e 's%\(.*\)=\(http:.*\)$%s=@\1@=\2=g%' \
   -e 's%\(.*\)=\(ftp:.*\)$%s=@\1@=\2=g%' \
   -e 's%\(.*\)=\(.*\.html\)$%s=@\1@=\2.gz=g%' \
   help_files.tmp | tr '=' '"' > help_files.sed
Appending interim-fix for existing html files to help_files.sed
sed -e '/^#/d' -e '/[:@]/d' -e '/^$/d' \
   -e 's%\(.*\)=\(.*\.html\)$%s=\2=\2.gz=g%' \
   -e 's%\.html=%\\.html=%' \
   help_files.tmp | tr '=' '"' >> help_files.sed
if test -n ".gz"; then echo "s%\\(\.gz\\)*\.gz%.gz%g" >> help_files.sed; fi
Creating LYHelp.h
**

  Help links point to compressed files
  To access them properly you have to type
make install-help

**
/bin/sh ./scripts/fixtext.sh ./LYMessages_en.h >LYMessages.c
cd ./po && make -w -j8 --jobserver-auth=3,4 DESTDIR="" CC="gcc"
make[2]: Entering directory '/build/lynx-2.8.9dev16/po'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
translating ca.po to ca.gmo
translating cs.po to cs.gmo
translating da.po to da.gmo
translating de.po to de.gmo
translating eo.po to eo.gmo
translating et.po to et.gmo
translating fi.po to fi.gmo
translating fr.po to fr.gmo
...updated homepage URL
...updated homepage URL
...updated homepage URL
...updated homepage URL
...updated homepage URL
...updated homepage URL
pass1.tmp:243: keyword "Champ" unknown
pass1.tmp:243: missing 'msgstr' section
pass1.tmp:243:22: syntax error
pass1.tmp:243: keyword "texte" unknown
pass1.tmp:243: keyword "NON" unknown
pass1.tmp:243: keyword "MODIFIABLE" unknown
pass1.tmp:139:38: invalid multibyte sequence
pass1.tmp:243: keyword "D" unknown
pass1.tmp:243: keyword "placez" unknown
pass1.tmp:243: keyword "vous" unknown
pass1.tmp:139:38: invalid multibyte sequencepass1.tmp:243: keyword
"avec" unknown
pass1.tmp:143: duplicate message definition...

pass1.tmp:139: ...this is the location of the first definition
pass1.tmp:243: keyword "haut" unknown
pass1.tmp:243: keyword "bas" unknown
pass1.tmp:243: keyword "tab" unknown
pass1.tmp:244: end-of-line within string
pass1.tmp:143: duplicate message definition...
pass1.tmp:139: ...this is the location of the first definition
pass1.tmp:247: duplicate message definition...
pass1.tmp:238: ...this is the location of the first definition
...no change made to homepage URL
...updated homepage URL
msgmerge: found 2 fatal errors
...workaround without merging against ./lynx.pot
msgmerge: found 2 fatal errors
...workaround without merging against ./lynx.pot
file=./`echo ca | sed 's,.*/,,'`.gmo \
 && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file pass2.tmp
msgmerge: found 15 fatal errors
...workaround without merging against ./lynx.pot
...file=./`echo
cs | sed 's,.*/,,'`.gmo \
 && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file pass2.tmp
..file=./`echo de | sed 's,.*/,,'`.gmo \
 && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file pass2.tmp
.
.. done.
..pass2.tmp:1241: end-of-file 

Bug#890593: marked as done (androguard FTBFS on big endian: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 21:34:40 +
with message-id 
and subject line Bug#890593: fixed in androguard 3.1.0~rc1-2
has caused the Debian Bug report #890593,
regarding androguard FTBFS on big endian: test failures
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.)


-- 
890593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: androguard
Version: 3.1.0~rc1-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nosetests3 --with-timer --timer-top-n 50
.EE.E..FFFFF.EE.E.EEESEE..EEE.S
==
ERROR: testAPK (test_analysis.AnalysisTest)
--
Traceback (most recent call last):
  File "/<>/tests/test_analysis.py", line 19, in testAPK
a, d, dx = AnalyzeAPK("examples/tests/a2dp.Vol_137.apk")
  File "/<>/androguard/misc.py", line 52, in AnalyzeAPK
digest = session.add(filename, data)
  File "/<>/androguard/session.py", line 166, in add
_, d, dx = self.addDEX(filename, dex, dx)
  File "/<>/androguard/session.py", line 100, in addDEX
d = DalvikVMFormat(data)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7525, in 
__init__
self._load(buff)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7536, in _load
self.map_list = MapList(self.CM, self.__header.map_off, self)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7406, in 
__init__
self.size = unpack("=I", buff.read(4))[0]
struct.error: unpack requires a buffer of 4 bytes
 >> begin captured logging << 
root: INFO: Generating grammar tables from 
/usr/lib/python3.6/lib2to3/Grammar.txt
root: INFO: Generating grammar tables from 
/usr/lib/python3.6/lib2to3/PatternGrammar.txt
androguard.misc: DEBUG: AnalyzeAPK
androguard.session: DEBUG: add 
APK:fb913cccb0957c5b52caea48c3ef7a3ce1d616219b47eed65482097920fe8cc5
androguard.session: DEBUG: added 
APK:fb913cccb0957c5b52caea48c3ef7a3ce1d616219b47eed65482097920fe8cc5
androguard.session: DEBUG: add 
DEX:1f2ca89075a9b985f9f8209eae7bc4d160b4502ff45352c517f3565bebe18738
androguard.session: DEBUG: Parsing format ...
- >> end captured logging << -

==
ERROR: testDex (test_analysis.AnalysisTest)
--
Traceback (most recent call last):
  File "/<>/tests/test_analysis.py", line 14, in testDex
d = dvm.DalvikVMFormat(fd.read())
  File "/<>/androguard/core/bytecodes/dvm.py", line 7525, in 
__init__
self._load(buff)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7536, in _load
self.map_list = MapList(self.CM, self.__header.map_off, self)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7406, in 
__init__
self.size = unpack("=I", buff.read(4))[0]
struct.error: unpack requires a buffer of 4 bytes

==
ERROR: testAPKActivitiesAreString (test_apk.APKTest)
--
Traceback (most recent call last):
  File "/<>/tests/test_apk.py", line 181, in 
testAPKActivitiesAreString
self.assertTrue(isinstance(activities[0], str), 'activities[0] is not of 
type str')
IndexError: list index out of range

==
ERROR: testAPKWrapper (test_apk.APKTest)
--
Traceback (most recent call last):
  File "/<>/tests/test_apk.py", line 20, in testAPKWrapper
a, d, dx = 
AnalyzeAPK("examples/android/TestsAndroguard/bin/TestActivity.apk")
  File "/<>/androguard/misc.py", line 52, in AnalyzeAPK
digest = session.add(filename, data)
  File "/<>/androguard/session.py", line 166, in add
_, d, dx = self.addDEX(filename, dex, dx)
  File "/<>/androguard/session.py", line 100, in addDEX
d = DalvikVMFormat(data)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7525, in 
__init__
self._load(buff)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7536, in _load
self.map_list = MapList(self.CM, self.__header.map_off, self)
  File "/<>/androguard/core/bytecodes/dvm.py", line 7406, in 
__init__
self.size = unpack("=I", 

Bug#890850: ruby-redcarpet FTBFS on 32bit: test failures with ruby 2.3

[Adrian Bunk]

Source: ruby-redcarpet
Version: 3.4.0-3
Severity: serious

https://buildd.debian.org/status/package.php?p=ruby-redcarpet=sid

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/<>/debian/ruby-redcarpet/usr/lib/i386-linux-gnu/ruby/vendor_ruby/2.3.0:/<>/debian/ruby-redcarpet/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-redcarpet/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/i386-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -I"lib:lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/custom_render_test.rb" "test/html5_test.rb" "test/html_render_test.rb" 
"test/html_toc_render_test.rb" "test/markdown_test.rb" 
"test/pathological_inputs_test.rb" "test/redcarpet_bin_test.rb" 
"test/redcarpet_compat_test.rb" "test/safe_render_test.rb" 
"test/smarty_html_test.rb" "test/smarty_pants_test.rb" 
"test/stripdown_render_test.rb" 
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
...F
===
Failure: test_utf8_only_header_anchors(HTMLRenderTest)
/<>/test/html_render_test.rb:259:in `test_utf8_only_header_anchors'
 256: markdown = "# 見出し"
 257: html = "見出し"
 258: 
  => 259: assert_equal html, render(markdown, with: [:with_toc_data])
 260:   end
 261: 
 262:   def test_escape_entities_removal_from_anchor
<"見出し"> expected but was
<"見出し">

diff:
? 見出し
===
.F
===
Failure:
   was expected to be =~
  <"\n\nA title\n\n\nA nice subtitle\n\n\nAnother one\n\n\nA sub-sub-title\n\n\n見出し\n\n\n\n\n\n">.
test_toc_heading_id(HTMLTOCRenderTest)
/<>/test/html_toc_render_test.rb:43:in `test_toc_heading_id'
 40: assert_match /a-nice-subtitle/, output
 41: assert_match /another-one/, output
 42: assert_match /a-sub-sub-title/, output
  => 43: assert_match /part-37870bfa194139f/, output
 44:   end
 45: 
 46:   def test_toc_heading_with_hyphen_and_equal
===
...
.

Finished in 0.586179711 seconds.
--
126 tests, 178 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
98.4127% passed
--
214.95 tests/s, 303.66 assertions/s
rake aborted!
Command failed with status (1): [ruby -I"lib:lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/custom_render_test.rb" "test/html5_test.rb" "test/html_render_test.rb" 
"test/html_toc_render_test.rb" "test/markdown_test.rb" 
"test/pathological_inputs_test.rb" "test/redcarpet_bin_test.rb" 
"test/redcarpet_compat_test.rb" "test/safe_render_test.rb" 
"test/smarty_html_test.rb" "test/smarty_pants_test.rb" 
"test/stripdown_render_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-redcarpet 
returned exit code 1
debian/rules:6: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 1

Processed: Bug #890593 in androguard marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890593 [src:androguard] androguard FTBFS on big endian: test failures
Added tag(s) pending.

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

Processed: affects 888193

[Debian Bug Tracking System]

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

> affects 888193 src:ruby-gruff
Bug #888193 [src:ruby-rmagick] ruby-rmagick: FTBFS on ruby2.5: 
)>
Added indication that 888193 affects src:ruby-gruff
> thanks
Stopping processing here.

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

Bug#890593: Bug #890593 in androguard marked as pending

[hans]

Control: tag -1 pending

Hello,

Bug #890593 in androguard 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/androguard/commit/e0a573fabf5fe46e9c5f07d3c7b8c3d7ac18296f


disable big-endian arches (Closes: #890593)



(this message was generated automatically)
-- 
Greetings

Processed: bug 889813 is forwarded to https://bitbucket.org/cffi/cffi/issues/358/segfaults-in-testing-embedding

[Debian Bug Tracking System]

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

> forwarded 889813 
> https://bitbucket.org/cffi/cffi/issues/358/segfaults-in-testing-embedding
Bug #889813 [src:python-cffi] python-cffi: FTBFS and Debci failure with 
python2.7 >= 2.7.14-5
Set Bug forwarded-to-address to 
'https://bitbucket.org/cffi/cffi/issues/358/segfaults-in-testing-embedding'.
> thanks
Stopping processing here.

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

Bug#890593: things never worked on big-endian

[Hans-Christoph Steiner]

Unfortunately, it looks like androguard never worked on big-endian
arches.  For now, the thing to do is just disable those arches.  I'm
sure upstream would welcome patches to port it.  Upstream is currently
focused on getting things polished up on the popular arches.

Bug#890621: this needs to be fixed for 3.7 (and apparently now for 3.6)

[Matthias Klose]

>> This is https://bugs.python.org/issue32305, apparently intentional and will
>> be in 3.7.  So better fix the packages itself. Not sure if that really should
>> be backported.

> Thanks for the forward.  The fix is for third party packages to use
> `getattr(module, ‘__file__’, None)` instead of `hasattr(module, ‘__file__’)`.
> I think gunicorn has already fixed this in their upstream.

Processed: reassign back to the original packages, keep a bug open in python3.6

[Debian Bug Tracking System]

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

> unmerge 890754
Bug #890754 [python3.6] python3.6 3.6.4-4 makes typecatcher FTBFS
Bug #890621 [python3.6] python3-keyrings.alt 2.2-2 module.__file__ is None, 
causing regrtest.py to fail
Disconnected #890754 from all other report(s).
> clone 890621 -1
Bug #890621 [python3.6] python3-keyrings.alt 2.2-2 module.__file__ is None, 
causing regrtest.py to fail
Bug 890621 cloned as bug 890844
> reassign 890621 src:typecatcher
Bug #890621 [python3.6] python3-keyrings.alt 2.2-2 module.__file__ is None, 
causing regrtest.py to fail
Bug reassigned from package 'python3.6' to 'src:typecatcher'.
No longer marked as found in versions python3.6/3.6.4-4.
Ignoring request to alter fixed versions of bug #890621 to the same values 
previously set
> reassign 890754 src:python3-keyrings.alt
Bug #890754 [python3.6] python3.6 3.6.4-4 makes typecatcher FTBFS
Bug reassigned from package 'python3.6' to 'src:python3-keyrings.alt'.
Warning: Unknown package 'src:python3-keyrings.alt'
Warning: Unknown package 'src:python3-keyrings.alt'
No longer marked as found in versions python3.6/3.6.4-4.
Warning: Unknown package 'src:python3-keyrings.alt'
Warning: Unknown package 'src:python3-keyrings.alt'
Ignoring request to alter fixed versions of bug #890754 to the same values 
previously set
Warning: Unknown package 'src:python3-keyrings.alt'
> thanks
Stopping processing here.

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

Bug#783346: Direktoriaus kontaktai - tai Jūsų klientas

[Gautas pranešimas]

Laba diena,


Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos 
įmonių bazės 2018 metų sausio vidurio.
Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys 
veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą.
 
Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, 
transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje.
 
Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis.
 
 
Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis:
 
1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė 
tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai 
bendrausite su direktoriais, komercijos vadovais.
 
2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus 
kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės 
skolingos Sodrai.
 
3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus 
galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių 
siunčiate elektroninius laiškus.
Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas.
 
 
Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia.
( Sąrašas prisegtas laiške excel faile )
 
Parašykite, kurias veiklas išsirinkote 
ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti



Pagarbiai,
Tadas Giedraitis
Tel. nr. +37067881041


Veiklos.xlsx
Description: Binary data

Bug#874420: Testing migration of the fixed node-babel depends on nodejs migration

[Adrian Bunk]

Testing migration of the fixed node-babel depends on nodejs migration.

cu
Adrian

-- 

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

Bug#890809: gnome-shell crash with gir1.2-gnomedesktop-3.0:amd64==3.27.90-1

[Jeremy Bicha]

On Mon, Feb 19, 2018 at 1:47 PM, Abhijit Hoskeri
 wrote:
> If you consider these bugs as spurious, is there a better way to upgrade
> gnome early and still report bugs that are useful?

"Experimental" being difficult to use is one reason why the Debian
GNOME team has pushed some previous GNOME releases before they've
actually reached their .0 release.

I think for 3.28, we'll be pushing many components at the 3.27.92 "RC"
release (in two weeks), although many of the apps work fine even at
their .90 releases.

I am waiting on upstream to bump the soname for mutter (a release
tarball would be cool too) because the new version of mutter is not
compatible with at least GNOME Shell 3.26 (I haven't tried Budgie with
it yet).

Thanks,
Jeremy Bicha

Bug#890809: gnome-shell crash with gir1.2-gnomedesktop-3.0:amd64==3.27.90-1

[Abhijit Hoskeri]

Thanks for the response - I am aware of the dangers - my goal is to help catch 
bugs and contribute to debian.



If you consider these bugs as spurious, is there a better way to upgrade gnome 
early and still report bugs that are useful?



Thanks, Abhijit.

On Feb 19, 2018, at 06:41 AM, Simon McVittie  wrote:


Control: reassign -1 gir1.2-gnomedesktop-3.0 3.27.90-1

On Sun, 18 Feb 2018 at 20:57:05 -0800, Abhijit Hoskeri wrote:

gnome-shell crashes on startup with the new version of
gir1.2-gnomedesktop-3.0 is installed. I worked around the problem by
holding the package to 3.26.x.

I think this is better represented as a libgnome-desktop bug: the new
libgnome-desktop from experimental is not yet ready for full-stack
testing.

When I saw this crash, it was because the same process had both
libgnome-desktop-3-12 (via libmutter) and libgnome-desktop-3-17 (via
gir1.2-gnomedesktop-3.0) in the same process space, and they fight.

gir1.2-gnomedesktop-3.0 (>= 3.27) should probably have a Breaks
on libmutter-1-0 (<< 3.27) to prevent the broken situation from
being installable. However, Mutter 3.27 has not yet been uploaded to
experimental, so if that was done, there is no version that would be
co-installable with libgnome-desktop-3-17 yet.


ii libc6 2.27-0experimental0
ii libpolkit-gobject-1-0 0.113-6

You appear to be installing all available packages from experimental. This
is almost certainly a bad idea. If they were ready for general use,
they wouldn't be in experimental.

smcv

Bug#890747: clang-4.0: scan-{build,view}-4.0 are missing

[Adrian Bunk]

On Mon, Feb 19, 2018 at 07:36:09PM +0100, Sylvestre Ledru wrote:
> Hello
> 
> Sorry but I am not planning to fix that in clang either. The goal of
> creating the clang tools package was to have a Clang compiler with a
> minimal package size.  So, I won't have a dependency from clang to
> Clang-tools
> 
> Httpping should be updated instead.

How? By adding a build dependency on clang-tools-4.0 (sic) and
switching to use -4.0 versioned programs?

A clang-tools package for these symlinks would be a prerequisite for any 
sane change in httping.

> Cheers
> Sylvestre

cu
Adrian

-- 

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

Bug#890747: clang-4.0: scan-{build,view}-4.0 are missing

[Sylvestre Ledru]

Hello

Sorry but I am not planning to fix that in clang either. The goal of
creating the clang tools package was to have a Clang compiler with a
minimal package size.  So, I won't have a dependency from clang to
Clang-tools

Httpping should be updated instead.

Cheers
Sylvestre

Le 18 févr. 2018 21:22, "Adrian Bunk"  a écrit :

Control: reopen -1
Control: reassign -1 clang 1:4.0-40
Control: clang: missing dependency on clang-tools-4.0

On Sun, Feb 18, 2018 at 09:05:14PM +0100, Sylvestre Ledru wrote:
>
> Le 18/02/2018 à 12:19, Adrian Bunk a écrit :
> > Package: clang-4.0
> > Version: 1:4.0.1-10
> > Severity: serious
> > Control: affects -1 src:httping
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/
unstable/amd64/httping.html
> >
> > ...
> > scan-build make
> > make[1]: scan-build: Command not found
> > make[1]: *** [Makefile:155: check] Error 127
> >
> >
> > The root cause is that the following symlinks are
> > dangling due to the binaries missing in clang-4.0:
> >
> >   /usr/bin/scan-build -> scan-build-4.0
> >   /usr/bin/scan-view -> scan-view-4.0
> >
> The feature has been moved to clang-tools-4.0.
>
> See bug #836397 for more information.

So the root cause of the httping FTBFS is actually a missing dependency
in clang.

Thanks for the information, reassigning.

> Sylvestre

cu
Adrian

--

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

Processed: tagging 890811

[Debian Bug Tracking System]

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

> tags 890811 + pending confirmed
Bug #890811 [src:lynx] lynx: FTBFS: msgfmt errors
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.

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

Bug#768843: fetchmail: Improved TLS support

[Graham Cobb]

Package: fetchmail
Version: 6.3.26-3
Followup-For: Bug #768843

I note that this bug appears to have caused fetchmail to be removed
from debian testing.

I have used fetchmail for many years, and continue to rely on it.
In fact it is working fine for me on my testing system, with the version
of fetchmail that was previously in testing (and is currently in unstable).

Is there anything I can do to assist in getting this fixed so that fetchmail
will be in buster when released? For example, testing a version based on
current upstream or something?



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

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

Versions of packages fetchmail depends on:
ii  adduser   3.117
ii  debianutils   4.8.4
ii  libc6 2.26-6
ii  libcomerr21.43.9-1
ii  libgssapi-krb5-2  1.16-2
ii  libk5crypto3  1.16-2
ii  libkrb5-3 1.16-2
ii  libssl1.1 1.1.0g-2
ii  lsb-base  9.20170808

Versions of packages fetchmail recommends:
ii  ca-certificates  20170717

Versions of packages fetchmail suggests:
pn  fetchmailconf   
ii  postfix [mail-transport-agent]  3.2.5-1
pn  resolvconf  

-- Configuration Files:
/etc/default/fetchmail changed [not included]

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

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

> severity 890600 normal
Bug #890600 [gtkterm] gtkterm: No prompt
Severity set to 'normal' from 'grave'
> notfound 890600 0.99.7~rc1-0.3
Bug #890600 [gtkterm] gtkterm: No prompt
No longer marked as found in versions gtkterm/0.99.7~rc1-0.3.
>
End of message, stopping processing here.

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

Bug#890811: lynx: FTBFS: msgfmt errors

[Axel Beckert]

Hi Adrian,

Adrian Bunk wrote:
> Debian packages default to parallel building,

Yes, and I also prefer that and don't like to have to pin a package to
-j1 due to such issues.

> a fix for this build failure is attached.

So thanks for the patch. Will check what else should (and can be done)
for a quick upload and will do that then.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE?

Bug#890600: gtkterm: No prompt

[Willem van den Akker]

On Sun, 2018-02-18 at 01:59 +, Pelle Hjek wrote:
> Hi
> 
> I may have misunderstood the purpose of gtkterm, as there is another program 
> with the same name, described like this:
> "GTKTerm is a small graphical shell like XTerm."
> https://sourceforge.net/projects/gtkterm/
> 
> I was mistakenly expecting GTKTerm to be a terminal emulator and was 
> expecting it to show a prompt.
> 
> Something that may have contributed to my confusion is the fact that GTKTerm 
> segfaults when clicking in the "Help" menu, and that the service, on which 
> the project web site in listed the GTKTerm man page ( 
> https://fedorahosted.org/gtkterm/ ) is hosted, has been discontinued.
> 

Hi,

I understand the mixup. 2 projects with the same name but different
functions are confusing. 

The segfaults in the help is a known problem and fixed in the latest
version in testing. 

Thanks for you clarification.

/Willem

Bug#890621: forwarded python3.6 issue (bpo-32305 causing regressions)

[Barry Warsaw]

On Feb 19, 2018, at 04:08, Matthias Klose  wrote:
> 
> This is https://bugs.python.org/issue32305, apparently intentional and will be
> in 3.7.  So better fix the packages itself. Not sure if that really should be
> backported.

Thanks for the forward.  The fix is for third party packages to use 
`getattr(module, ‘__file__’, None)` instead of `hasattr(module, ‘__file__’)`.  
I think gunicorn has already fixed this in their upstream.



signature.asc
Description: Message signed with OpenPGP

Processed: Re: Bug#890811: lynx: FTBFS: msgfmt errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #890811 [src:lynx] lynx: FTBFS: msgfmt errors
Added tag(s) patch.

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

Bug#890811: lynx: FTBFS: msgfmt errors

[Adrian Bunk]

Control: tags -1 patch

On Mon, Feb 19, 2018 at 06:38:54AM -0500, Thomas Dickey wrote:
> On Sun, Feb 18, 2018 at 10:45:51PM -0800, Daniel Schepler wrote:
>...
> >dh_auto_build
> >make -j8
> 
> take out the -j8, for a start.
>...

Debian packages default to parallel building,
a fix for this build failure is attached.

cu
Adrian

-- 

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

Description: po/makefile.inn: Use unique names for temporary files
 Fixes parallel build FTBFS.
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/890811

--- lynx-2.8.9dev16.orig/po/makefile.inn
+++ lynx-2.8.9dev16/po/makefile.inn
@@ -89,23 +89,23 @@ INSTOBJ		= $(NLS_TEXTDOMAIN)$(INSTOBJEXT
 	@echo "translating $< to $@"
 	@$(SHELL) -c 'LC_ALL=C \
 	sed	-e s,http://lynx.browser.org/,@HOMEPAGE_URL@,g \
-		-e s,http://lynx.isc.org/,@HOMEPAGE_URL@,g $< >pass1.tmp;\
-	if cmp -s $< pass1.tmp; \
+		-e s,http://lynx.isc.org/,@HOMEPAGE_URL@,g $< >pass1.$@.tmp;\
+	if cmp -s $< pass1.$@.tmp; \
 	then \
 		echo ...no change made to homepage URL; \
 	else \
 		echo ...updated homepage URL;\
 	fi; \
-	if $(MSGMERGE) -w 132 pass1.tmp $(srcdir)/$(PACKAGE).pot -o pass2.tmp; \
+	if $(MSGMERGE) -w 132 pass1.$@.tmp $(srcdir)/$(PACKAGE).pot -o pass2.$@.tmp; \
 	then \
 		echo "...merged against $(srcdir)/$(PACKAGE).pot";\
 	else \
 		echo "...workaround without merging against $(srcdir)/$(PACKAGE).pot";\
-		cat  $< >pass2.tmp; \
+		cat  $< >pass2.$@.tmp; \
 	fi '
 	@ECHO_CC@file=$(srcdir)/`echo $* | sed 's,.*/,,'`.gmo \
-	  && rm -f $$file && $(GMSGFMT) -o $$file pass2.tmp
-	@-rm -f pass*.tmp
+	  && rm -f $$file && $(GMSGFMT) -o $$file pass2.$@.tmp
+	@-rm -f pass*.$@.tmp
 
 .po.cat:
 	@echo "translating $< to $@"

Processed: Re: Bug#890811: lynx: FTBFS: msgfmt errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #890811 [src:lynx] lynx: FTBFS: msgfmt errors
Ignoring request to alter tags of bug #890811 to the same tags previously set

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

Processed: fixed 879483 in 1.1+git20171228.f2ec36a-1

[Debian Bug Tracking System]

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

> fixed 879483 1.1+git20171228.f2ec36a-1
Bug #879483 [src:golang-github-ugorji-go-codec] golang-github-ugorji-go-codec 
FTBFS: rm: cannot remove 
'/<>/debian//*/usr/share/gocode/src/github.com/ugorji/go/codec/prebuild.sh':
 No such file or directory
The source 'golang-github-ugorji-go-codec' and version 
'1.1+git20171228.f2ec36a-1' do not appear to match any binary packages
Marked as fixed in versions 
golang-github-ugorji-go-codec/1.1+git20171228.f2ec36a-1.
> thanks
Stopping processing here.

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

Processed: Fixed upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #888166 [src:ruby-rabl] ruby-rabl: FTBFS on ruby2.5: BSON:Module serialize
Added tag(s) fixed-upstream.

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

Bug#888166: Fixed upstream

[debian]

Control: tags -1 + fixed-upstream

https://github.com/nesquena/rabl/pull/704/commits/78f83e8dc3681a289900925d99b9a5b2fa4c48e9

Bug#886287: marked as done (node-coveralls: FTBFS: makes assumptions about build path)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 17:20:21 +
with message-id 
and subject line Bug#886287: fixed in node-coveralls 3.0.0-2
has caused the Debian Bug report #886287,
regarding node-coveralls: FTBFS: makes assumptions about build path
to be marked as done.

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

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


-- 
886287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-coveralls
Version: 3.0.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-coveralls fails to build from source in amd64/unstable if you
rename the build directory. I see you patch the upstream function
but the whole thing is too brittle IMHO.

eg.

  $ cd $(mktemp -d)
  $ apt-get source node-coveralls
  $ mv node-coveralls*/ renamed
  $ cd renamed
  $ dpkg-buildpackage -uc -us

  […]

2) detectLocalGit
 "after all" hook:
   Error: Tried to clean a temp git directory that did not match path: 
node-coveralls/test
at _deleteFolderRecursive (test/detectLocalGit.js:61:11)
at _cleanTempGitDir (test/detectLocalGit.js:55:5)
at Context. (test/detectLocalGit.js:19:9)
at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
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)
  
  
  
  debian/rules:30: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/build/node-coveralls-3.0.0/2nd'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  I: copying local configuration
  E: Failed autobuilding of package

  […]


Regards,

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


node-coveralls.3.0.0-1.logs.unstable.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: node-coveralls
Source-Version: 3.0.0-2

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

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

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated node-coveralls 
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: Mon, 19 Feb 2018 00:13:57 +0100
Source: node-coveralls
Binary: node-coveralls
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Description:
 node-coveralls - input json-cov output and posts to coveralls.io
Closes: 886287
Changes:
 node-coveralls (3.0.0-2) unstable; urgency=medium
 .
   * Fix lintian warnings
   * Bump compat and policy (no changes)
   * FTBFS: makes assumptions about build path (Closes: #886287)
   * Fix cli testsuite
Checksums-Sha1:
 5480cf4c8084e49740d92409e6ec104ed5c17e51 2459 node-coveralls_3.0.0-2.dsc
 7d1d3913d75f6620993f2152d3b9a20df369c028 6564 
node-coveralls_3.0.0-2.debian.tar.xz
 fe3715037a5dd2593f7d4923ca6a1d03dcb026c3 10757 
node-coveralls_3.0.0-2_amd64.buildinfo
Checksums-Sha256:
 63906652a728260480be90af1e9759279fdb8ed3f58c0e2b668f23ad94015518 2459 
node-coveralls_3.0.0-2.dsc
 9f509ee6bc66ed57cd85e5487d9f19699372934293ca23b3ffa0ae47deb75fd6 6564 
node-coveralls_3.0.0-2.debian.tar.xz
 5b1c753f79284d47cf578960383f7f7888f94de75f03ca43490495c47b8ca4e1 10757 
node-coveralls_3.0.0-2_amd64.buildinfo
Files:
 7310292a3448170f25a5074a64e102aa 2459 javascript optional 
node-coveralls_3.0.0-2.dsc
 658dbf206ab9c9024234a77c8474338b 6564 javascript optional 
node-coveralls_3.0.0-2.debian.tar.xz
 b8f2c8e850f4d9e2f8fad91db96f94f3 10757 javascript optional 

Processed: [bts-link] source package src:salt-formula-keystone

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:salt-formula-keystone
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #889929 (http://bugs.debian.org/889929)
> # Bug title: salt-formula-keyston: FTBFS and Debci failure with salt 2017.7.2
> #  * https://github.com/salt-formulas/salt-formula-keystone/pull/21
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 889929 + fixed-upstream
Bug #889929 [src:salt-formula-keystone] salt-formula-keyston: FTBFS and Debci 
failure with salt 2017.7.2
Added tag(s) fixed-upstream.
> usertags 889929 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:salt-formula-kubernetes

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:salt-formula-kubernetes
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #889932 (http://bugs.debian.org/889932)
> # Bug title: salt-formula-kubernetes: FTBFS and Debci failure with salt 
> 2017.7.2
> #  * https://github.com/salt-formulas/salt-formula-kubernetes/pull/12
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 889932 + fixed-upstream
Bug #889932 [src:salt-formula-kubernetes] salt-formula-kubernetes: FTBFS and 
Debci failure with salt 2017.7.2
Added tag(s) fixed-upstream.
> usertags 889932 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:salt-formula-glance

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:salt-formula-glance
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #889933 (http://bugs.debian.org/889933)
> # Bug title: salt-formula-glance: FTBFS and Debci failure with salt 2017.7.2
> #  * https://github.com/salt-formulas/salt-formula-glance/pull/23
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 889933 + fixed-upstream
Bug #889933 [src:salt-formula-glance] salt-formula-glance: FTBFS and Debci 
failure with salt 2017.7.2
Added tag(s) fixed-upstream.
> usertags 889933 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package milkytracker

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package milkytracker
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #890407 (http://bugs.debian.org/890407)
> # Bug title: milkytracker: various buffer overflows possibly leading to 
> remote code execution
> #  * https://github.com/milkytracker/MilkyTracker/issues/35
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 890407 + fixed-upstream
Bug #890407 [milkytracker] milkytracker: various buffer overflows possibly 
leading to remote code execution
Added tag(s) fixed-upstream.
> usertags 890407 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:salt-formula-cinder

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:salt-formula-cinder
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #889928 (http://bugs.debian.org/889928)
> # Bug title: salt-formula-cinder: FTBFS and Debci failure with salt 2017.7.2
> #  * https://github.com/salt-formulas/salt-formula-cinder/pull/23
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 889928 + fixed-upstream
Bug #889928 [src:salt-formula-cinder] salt-formula-cinder: FTBFS and Debci 
failure with salt 2017.7.2
Added tag(s) fixed-upstream.
> usertags 889928 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#888168: marked as done (ruby-redcarpet: FTBFS on ruby2.5: incompatible library version)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 17:07:07 +
with message-id 
and subject line Bug#888168: fixed in ruby-redcarpet 3.4.0-3
has caused the Debian Bug report #888168,
regarding ruby-redcarpet: FTBFS on ruby2.5: incompatible library version
to be marked as done.

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

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


-- 
888168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-redcarpet
Version: 3.4.0-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition


It seems to build then fail to load its extension? Not seen this on
other packages.


Build log excerpt:


┌──┐
│ Build native extensions for ruby2.5  │
└──┘

/usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
/build/ruby-redcarpet-3.4.0 debian/ruby-redcarpet
"make clean"
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
make[1]: Leaving directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
"make clean"
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
make[1]: Leaving directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
current directory: /build/ruby-redcarpet-3.4.0/ext/redcarpet
/usr/bin/ruby2.5 -r ./siteconf20180123-308-zr9kz6.rb extconf.rb
creating Makefile
current directory: /build/ruby-redcarpet-3.4.0/ext/redcarpet
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
rm -f 
rm -f redcarpet.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
current directory: /build/ruby-redcarpet-3.4.0/ext/redcarpet
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-redcarpet-3.4.0/ext/redcarpet'
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o autolink.o -c autolink.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o buffer.o -c buffer.c
buffer.c: In function 'bufcstr':
buffer.c:111:45: warning: passing argument 1 of 'bufgrow' discards 'const' 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  if (buf->size + 1 <= buf->asize || bufgrow(buf, buf->size + 1) == BUF_OK) {
 ^~~
buffer.c:60:1: note: expected 'struct buf *' but argument is of type 'const 
struct buf *'
 bufgrow(struct buf *buf, size_t neosz)
 ^~~
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o houdini_href_e.o -c houdini_href_e.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o houdini_html_e.o -c houdini_html_e.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=hidden  -o html.o -c html.c
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 

Bug#890781: marked as done (environment-modules: MODULESHOME initialized wrong)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 17:06:15 +
with message-id 
and subject line Bug#890781: fixed in modules 4.1.1-1
has caused the Debian Bug report #890781,
regarding environment-modules: MODULESHOME initialized wrong
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.)


-- 
890781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: environment-modules
Version: 4.1.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm completely locked out of my modules.

   * What led up to the situation?
   Upgrade from 3.2.10-10 (probably) to 4.1.0-1 when pulling in buster.
   However, I don't think it is upgrade-dependent.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   I tried to list my modules with "module avail"

   * What was the outcome of this action?
   No output at all. No module is found.

   * What outcome did you expect instead?
   A list of at least the default modules provided by the package

I tried to track the bug. The script /usr/lib/modulecmd.tcl is setting 
MODULESHOME to /usr and tries to read /usr/init/.modulespath and 
usr/init/modulerc in several places. However, these files are installed 
to /usr/share/modules/init.

Checking the upstream-repository, it seems that PREFIX somehow does not
match the installation directory.

Thanks and best regards,
emanuel



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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages environment-modules depends on:
ii  debhelper  11.1.3
ii  libc6  2.26-4
ii  libtcl8.6  8.6.8+dfsg-2
ii  tcl8.6.0+9
ii  tcl8.6 8.6.8+dfsg-2

environment-modules recommends no packages.

environment-modules suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: modules
Source-Version: 4.1.1-1

We believe that the bug you reported is fixed in the latest version of
modules, 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.
Alastair McKinstry  (supplier of updated modules 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: Mon, 19 Feb 2018 16:47:47 +
Source: modules
Binary: environment-modules
Architecture: source amd64
Version: 4.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 environment-modules - Modular system for handling environment variables
Closes: 865118 890781
Changes:
 modules (4.1.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Set VCS to point to salsa.debian.org
   * Ack. and close old bug on bash completion: Closes: #865118
   * Delete obsolete patches:
 - compiler_fixes.patch
 - debian/patches/fix_paths.patch
 - debian/patches/format.patch
   * Update  testsuite-fix.patch
   * Set mandir, etcdir in ./rules to configure site.exp correctly
   * set initdir. Closes: #890781
   * Add procps as a build-dep / runtime dependency
Checksums-Sha1:
 ab098b7b8c1840c7235f4be445589e91df57a19b 1904 modules_4.1.1-1.dsc
 d4fc29c44d7e544675d81de11457f45e8e4e251b 983616 modules_4.1.1.orig.tar.xz
 5ab739c4e0f8b24fffef5853f25fcf8d76c8 5616 modules_4.1.1-1.debian.tar.xz
 c77edf041f37808524e55e908488c56328e1f80f 543304 
environment-modules-dbgsym_4.1.1-1_amd64.deb
 3aa67f9a8ee79674f3e190d8cd4b89aee45fd85b 343512 
environment-modules_4.1.1-1_amd64.deb
 fa652251ccd477415cd8dc1d17453d4bf939ee26 6027 modules_4.1.1-1_amd64.buildinfo
Checksums-Sha256:
 

Processed: [bts-link] source package make-dfsg

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package make-dfsg
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #890430 (http://bugs.debian.org/890430)
> # Bug title: make: warning: -jN forced in submake: disabling jobserver mode.
> #  * http://savannah.gnu.org/bugs/?func=detailitem_id=48274
> #  * remote status changed: (?) -> Closed
> #  * remote resolution changed: (?) -> Fixed
> #  * closed upstream
> tags 890430 + fixed-upstream
Bug #890430 [make] make: warning: -jN forced in submake: disabling jobserver 
mode.
Added tag(s) fixed-upstream.
> usertags 890430 + status-Closed resolution-Fixed
There were no usertags set.
Usertags are now: status-Closed resolution-Fixed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:salt-formula-ceilometer

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:salt-formula-ceilometer
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #889927 (http://bugs.debian.org/889927)
> # Bug title: salt-formula-ceilometer: FTBFS and Debci failure with salt 
> 2017.7.2
> #  * https://github.com/salt-formulas/salt-formula-ceilometer/pull/6
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 889927 + fixed-upstream
Bug #889927 [src:salt-formula-ceilometer] salt-formula-ceilometer: FTBFS and 
Debci failure with salt 2017.7.2
Added tag(s) fixed-upstream.
> usertags 889927 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: affects 890809

[Debian Bug Tracking System]

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

> affects 890809 gnome-shell
Bug #890809 [gir1.2-gnomedesktop-3.0] gnome-shell crash with 
gir1.2-gnomedesktop-3.0:amd64==3.27.90-1
Added indication that 890809 affects gnome-shell
> thanks
Stopping processing here.

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

Processed: Bug #888168 in ruby-redcarpet marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888168 [src:ruby-redcarpet] ruby-redcarpet: FTBFS on ruby2.5: incompatible 
library version
Added tag(s) pending.

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

Bug#888168: Bug #888168 in ruby-redcarpet marked as pending

[balint . reczey]

Control: tag -1 pending

Hello,

Bug #888168 in ruby-redcarpet 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-redcarpet/commit/473a6926c3924eb3e1fec6b89f486bd86968d4ea


Fix Ruby 2.5 test failure when Ruby 2.3 is installed as default

Closes: #888168



(this message was generated automatically)
-- 
Greetings

Processed: tagging 884973

[Debian Bug Tracking System]

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

> tags 884973 + buster sid
Bug #884973 [tp-smapi-dkms] tp-smapi-dkms: build failure with 4.15.0
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#887931: marked as done (gazebo FTBFS with libtinyxml2-dev 6.0.0+dfsg-1)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 15:00:14 +
with message-id 
and subject line Bug#887931: fixed in gazebo 9.0.0+dfsg5-1
has caused the Debian Bug report #887931,
regarding gazebo FTBFS with libtinyxml2-dev 6.0.0+dfsg-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.)


-- 
887931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gazebo
Version: 7.8.1+dfsg-4
Severity: serious

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

...
/<>/gazebo-7.8.1+dfsg/gazebo/util/LogPlay.cc: In member function 
'void gazebo::util::LogPlay::Open(const string&)':
/<>/gazebo-7.8.1+dfsg/gazebo/util/LogPlay.cc:121:51: error: 'class 
tinyxml2::XMLDocument' has no member named 'GetErrorStr1'; did you mean 
'ErrorStr'?
 const char *errorStr1 = this->dataPtr->xmlDoc.GetErrorStr1();
   ^~~~
   ErrorStr
/<>/gazebo-7.8.1+dfsg/gazebo/util/LogPlay.cc:122:51: error: 'class 
tinyxml2::XMLDocument' has no member named 'GetErrorStr2'; did you mean 
'ErrorStr'?
 const char *errorStr2 = this->dataPtr->xmlDoc.GetErrorStr2();
   ^~~~
   ErrorStr
gazebo/util/CMakeFiles/gazebo_util.dir/build.make:89: recipe for target 
'gazebo/util/CMakeFiles/gazebo_util.dir/LogPlay.cc.o' failed
make[3]: *** [gazebo/util/CMakeFiles/gazebo_util.dir/LogPlay.cc.o] Error 1
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 9.0.0+dfsg5-1

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated gazebo 
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, 15 Feb 2018 02:49:23 +
Source: gazebo
Binary: gazebo9-common gazebo9 libgazebo9 libgazebo9-dev gazebo9-plugin-base 
gazebo9-doc
Architecture: source all amd64
Version: 9.0.0+dfsg5-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 gazebo9- Open Source Robotics Simulator - Binaries
 gazebo9-common - Open Source Robotics Simulator - Shared files
 gazebo9-doc - Open Source Robotics Simulator - Documentation
 gazebo9-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo9 - Open Source Robotics Simulator - shared library
 libgazebo9-dev - Open Source Robotics Simulator - Development Files
Closes: 874898 887931
Changes:
 gazebo (9.0.0+dfsg5-1) experimental; urgency=medium
 .
   * Added patch to use roboto system fonts
   * Added patch to use system qtpropertybrowser
   * Missing pieces in the copyright file
   * Remove duplicate dependency on simbody
   * Do not restrict desktops where gazebo is shown
   * Fix lintian errors related to copyright
   * Change to salsa. Break/Replace gazebo7 version
   * Remove gazebo.menu
 (https://www.debian.org/doc/debian-policy/#version-4-0-1)
   * Remove all the SSE logic from rules file
   * Update TODO file with info about the ode packaging exception
   * Simplify and improve the README file: move licenses to its own section and
 use wildcards for listing files when possible
   * Missing font dependencies
   * Remove embedded libraries present in code
   * Added clang-format
   * Update the way of getting sources
   * Imported Upstream version 9.0.0+dfsg
 (Closes: #887931, #874898, #874898)
   * Use system ccd
   * Fix watch file
   * Remove fonts copyright
   * New upstream version 9.0.0+dfsg5
Checksums-Sha1:
 a8db0b8fdd608c8476422546e41342a08aa75dc1 3254 gazebo_9.0.0+dfsg5-1.dsc
 531ab6901586d9d97ba73ea8aa6ea0cbbd271c35 51816789 
gazebo_9.0.0+dfsg5.orig.tar.gz
 36217f0dfb6ba76b098b6ec8341fa5f9c3c77a1f 13384 
gazebo_9.0.0+dfsg5-1.debian.tar.xz
 

Processed: Re: Bug#890809: gnome-shell crash with gir1.2-gnomedesktop-3.0:amd64==3.27.90-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gir1.2-gnomedesktop-3.0 3.27.90-1
Bug #890809 [gnome-shell] gnome-shell crash with 
gir1.2-gnomedesktop-3.0:amd64==3.27.90-1
Bug reassigned from package 'gnome-shell' to 'gir1.2-gnomedesktop-3.0'.
No longer marked as found in versions gnome-shell/3.26.2-5.
Ignoring request to alter fixed versions of bug #890809 to the same values 
previously set
Bug #890809 [gir1.2-gnomedesktop-3.0] gnome-shell crash with 
gir1.2-gnomedesktop-3.0:amd64==3.27.90-1
Marked as found in versions gnome-desktop3/3.27.90-1.

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

Bug#890809: gnome-shell crash with gir1.2-gnomedesktop-3.0:amd64==3.27.90-1

[Simon McVittie]

Control: reassign -1 gir1.2-gnomedesktop-3.0 3.27.90-1

On Sun, 18 Feb 2018 at 20:57:05 -0800, Abhijit Hoskeri wrote:
> gnome-shell crashes on startup with the new version of
> gir1.2-gnomedesktop-3.0 is installed. I worked around the problem by
> holding the package to 3.26.x.

I think this is better represented as a libgnome-desktop bug: the new
libgnome-desktop from experimental is not yet ready for full-stack
testing.

When I saw this crash, it was because the same process had both
libgnome-desktop-3-12 (via libmutter) and libgnome-desktop-3-17 (via
gir1.2-gnomedesktop-3.0) in the same process space, and they fight.

gir1.2-gnomedesktop-3.0 (>= 3.27) should probably have a Breaks
on libmutter-1-0 (<< 3.27) to prevent the broken situation from
being installable. However, Mutter 3.27 has not yet been uploaded to
experimental, so if that was done, there is no version that would be
co-installable with libgnome-desktop-3-17 yet.

> ii  libc62.27-0experimental0
> ii  libpolkit-gobject-1-00.113-6

You appear to be installing all available packages from experimental. This
is almost certainly a bad idea. If they were ready for general use,
they wouldn't be in experimental.

smcv

Processed: limit source to node-coveralls, tagging 886287

[Debian Bug Tracking System]

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

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

> tags 886287 + pending
Bug #886287 [src:node-coveralls] node-coveralls: FTBFS: makes assumptions about 
build path
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#890517: killer's CRON logs out users once per hour

[Wolfgang Schweer]

On Thu, Feb 15, 2018 at 03:21:41PM +, Mike Gabriel wrote:
> On  Do 15 Feb 2018 15:23:46 CET, Petter Reinholdtsen wrote:
> 
> > [Mike Gabriel]
> > > We never came to the point to investigate this closer, but personally,
> > > I think that killer on a Debian Edu system with MATE desktop env has
> > > not been usable at least since jessie.

I'm unable to reproduce the reported issue (Debian Edu Jessie, Stretch, 
Buster; tested LightDM, GDM, SDDM).

> > The only way I can think of that this can happen, is if the display
> > manager is broken and fail to register logged in users in the utmp/wtmp
> > files.  You can verify this by running 'w' or 'who' after login to see
> > if the user is registered as logged in.  If this is the case, the fatal
> > bug is in the login service you are using, not killer.
> 
> Output of "who" looks good, if MATE gets launched locally (vt7). Display
> Manager is LightDM with Arctica Greeter on top.

> However, I noticed that X2Go does not register the logged in user in
> utmp/wtmp.
 
Mike, could you provide some details?

IIRC, for connections to a system that runs Nomachine technology (not 
part of Debian) the utmp/wtmp files are not used by design (on the 
system running NX server). Instead, NX keeps track of the 
forwarded sessions itself.

IMO killer shouldn't be installed on a system running NX technology 
because the reported failure will show up for sure.
 
Wolfgang


signature.asc
Description: PGP signature

Bug#890289: libmbedtls

[Teus Benschop]

Yes, you are right that embedding this library presents a security risk, in
particular when the package plus its embedded library gets older and new
security issues are found in mbedtls.
The segmentation fault now caused by mbedtls was the reason this code was
embedded, it didn't have a segmentation fault then.
Upstream is looking into this how to solve this.

Bug#890811: lynx: FTBFS: msgfmt errors

[Thomas Dickey]

On Sun, Feb 18, 2018 at 10:45:51PM -0800, Daniel Schepler wrote:
> Source: lynx
> Version: 2.8.9dev16-2
> Severity: serious
> 
> >From my pbuilder build log:

hmm - where is that?

By the way, since your log is incomplete, there's insufficient information
to comment further.

>dh_auto_build
>make -j8

take out the -j8, for a start.

> translating ca.po to ca.gmo
> translating cs.po to cs.gmo
> translating da.po to da.gmo
> translating de.po to de.gmo
> translating eo.po to eo.gmo
> translating et.po to et.gmo
> translating fi.po to fi.gmo
> translating fr.po to fr.gmo
> ...updated homepage URL
> ...updated homepage URL
> ...updated homepage URL
> ...updated homepage URL
> ...updated homepage URL
> ...updated homepage URL
> pass1.tmp:243: keyword "Champ" unknown

This appears to be a problem with your script, which you should solve
before opening a bug report.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#760660: Direktoriaus kontaktai - tai Jūsų klientas

[Gautas pranešimas]

Laba diena,


Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos 
įmonių bazės 2018 metų sausio vidurio.
Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys 
veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą.
 
Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, 
transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje.
 
Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis.
 
 
Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis:
 
1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė 
tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai 
bendrausite su direktoriais, komercijos vadovais.
 
2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus 
kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės 
skolingos Sodrai.
 
3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus 
galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių 
siunčiate elektroninius laiškus.
Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas.
 
 
Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia.
( Sąrašas prisegtas laiške excel faile )
 
Parašykite, kurias veiklas išsirinkote 
ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti



Pagarbiai,
Tadas Giedraitis
Tel. nr. +37067881041


Veiklos.xlsx
Description: Binary data

Processed: mbedtls transition blockers

[Debian Bug Tracking System]

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

> # for charybdis
> block 890448 by 890411
Bug #890448 [release.debian.org] transition: mbedtls
890448 was not blocked by any bugs.
890448 was not blocking any bugs.
Added blocking bug(s) of 890448: 890411
> # for neko
> block 890448 by 888095
Bug #890448 [release.debian.org] transition: mbedtls
890448 was blocked by: 890411
890448 was not blocking any bugs.
Added blocking bug(s) of 890448: 888095
> affects 888095 src:neko
Bug #888095 [src:mariadb-connector-c] mariadb-connector-c: ships libmariadb3 
version 3.0.3-1, which is lower than the one in mariadb-10.[23]
Added indication that 888095 affects src:neko
> thanks
Stopping processing here.

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

Bug#887789: marked as done (gitlint: package should depend on python3-sh)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 11:21:27 +
with message-id 
and subject line Bug#887789: fixed in gitlint 0.9.0-2
has caused the Debian Bug report #887789,
regarding gitlint: package should depend on python3-sh
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.)


-- 
887789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlint
Version: 0.9.0-1
Severity: important

Dear Maintainer,

after installing gitlab and running it for the first time, i get the
following backtrace:

~~~
$ gitlint 
Traceback (most recent call last):
  File "/usr/bin/gitlint", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3144, 
in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3128, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3157, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 666, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 984, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 870, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'sh==1.11' distribution was not found 
and is required by gitlint
$
~~~

it seems like a Depends on 'python3-sh' is missing
(after installing that package the error went away)


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

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

Versions of packages gitlint depends on:
ii  git1:2.15.1-3
ii  python33.6.4-1
ii  python3-arrow  0.10.0-1
ii  python3-click  6.7-3

gitlint recommends no packages.

gitlint suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gitlint
Source-Version: 0.9.0-2

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

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

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

Debian distribution maintenance software
pp.
Patrik Hagedorn  (supplier of updated gitlint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Feb 2018 22:48:41 +0100
Source: gitlint
Binary: gitlint
Architecture: source
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Patrik Hagedorn 
Changed-By: Patrik Hagedorn 
Description:
 gitlint- Git commit message linter written in Python
Closes: 887789
Changes:
 gitlint (0.9.0-2) unstable; urgency=medium
 .
   * Add missing dependency python3-sh (Closes: #887789)
Checksums-Sha1:
 6783e121b111aaa5c62a9e9644869b4e4179ef2f 1819 gitlint_0.9.0-2.dsc
 3add6b05577bda48cd9470f0b9b50971fe82c052 5044 gitlint_0.9.0-2.debian.tar.xz
 08941c3a788a68b6d5866ee12e47730e5614721b 8401 gitlint_0.9.0-2_source.buildinfo
Checksums-Sha256:
 156ada8dc1c01bfd213b88c58bb9e10bf6fd0569165304f006976f050f138d66 1819 
gitlint_0.9.0-2.dsc
 1f8629a6f7564e46249dc96b821b3be9c6c1bef563d64f57237e6273acce6443 5044 
gitlint_0.9.0-2.debian.tar.xz
 fa4694efc9a7d30de4bd3786d0bc69539858e65749add1051c60a6e82b24cbb8 8401 
gitlint_0.9.0-2_source.buildinfo
Files:
 25d71a0f48b5c38a9ededf24930152a9 1819 utils optional gitlint_0.9.0-2.dsc
 c3ef2a2af1e73ee2278e28a41956730d 5044 utils optional 
gitlint_0.9.0-2.debian.tar.xz
 e988f5541fee2aca492809c132549d1d 8401 utils optional 
gitlint_0.9.0-2_source.buildinfo

Bug#890748: marked as done (python-pysam: autopkgtest failures in pbsuite, python-pbcore)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 11:08:38 +
with message-id 
and subject line Bug#890748: fixed in python-pysam 0.14+ds-2
has caused the Debian Bug report #890748,
regarding python-pysam: autopkgtest failures in pbsuite, python-pbcore
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.)


-- 
890748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysam
Version: 0.14+ds-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
Affects: pbsuite python-pbcore

Hi Maintainer

Since the upload of python-pysam 0.14+ds-1, autopkgtests of pbsuite
[1] and python-pbcore [2] have been failing with error messages
similar to the following (and others):

ImportError: libchtslib.so: cannot open shared object file: No such
file or directory

Regards
Graham


[1] https://ci.debian.net/packages/p/pbsuite/unstable/amd64/
[2] https://ci.debian.net/packages/p/python-pbcore/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.14+ds-2

We believe that the bug you reported is fixed in the latest version of
python-pysam, 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.
Graham Inggs  (supplier of updated python-pysam 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: Mon, 19 Feb 2018 10:11:17 +
Source: python-pysam
Binary: python-pysam python3-pysam python-pysam-tests
Architecture: source
Version: 0.14+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Graham Inggs 
Description:
 python-pysam - interface for the SAM/BAM sequence alignment and mapping format 
(
 python-pysam-tests - interface for the SAM/BAM sequence alignment and mapping 
format (
 python3-pysam - interface for the SAM/BAM sequence alignment and mapping 
format (
Closes: 890748
Changes:
 python-pysam (0.14+ds-2) unstable; urgency=medium
 .
   * Team upload
   * Add Python 2.7 compatibility symlink for libchtslib.so (Closes: #890748)
   * Update Vcs-* URIs for move to salsa.debian.org
   * Remove trailing whitespace from debian/changelog
Checksums-Sha1:
 2f1963aa8c242d8729b10d7d4ed96d7bee8158cf 2459 python-pysam_0.14+ds-2.dsc
 68173f245b6950daee71ad722f314416e563927f 10632 
python-pysam_0.14+ds-2.debian.tar.xz
Checksums-Sha256:
 4e9f55ed7ab5ac513c1b008f6e3dcc6205cfdd7805aff34b6b55cbd9678dbaf6 2459 
python-pysam_0.14+ds-2.dsc
 e10402a8d01601fa431ebf2f67e0132bc6233a6ed38c4a8fd2cd20175c8571eb 10632 
python-pysam_0.14+ds-2.debian.tar.xz
Files:
 56832af85bd1cca327fd7269650d26cb 2459 python optional 
python-pysam_0.14+ds-2.dsc
 89cccfd003fad5fc2b50142c5e89ab2b 10632 python optional 
python-pysam_0.14+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaiqYJAAoJEK/P7I5mnOHCmEQP/0UlM6JUB0V+oFWAKH3IF77f
TBsBu7LN1fetLHuKLl/XMVZAWvtEbk+RJaz1zSBcOcC3rPlVg2CRAKB1UqBzbWsj
E/ylFp1B1kecg8ghVlzIPyY7M3ZkIEYV1sUqQRFo47eo4V7weLDSNKHrOzjm8/+j
SHiviv7xez0cL51GnnMXg7+aYeO45QwFB5v+wYMgJ/HObLeMeyVSs7ft7nlcQVpA
tNpdWZZ3+VDz1TF5Vyi//3+yiAEYL5gsiw7VZ6aTyYD5Upjo8unaQ+SfmM4PyY41
Bz7DLU7juUepIn6oeruMIx7Snt7e7Kcxh0UiBuffiq5qenREi45p60nMFWqketNS
relNy4J/8yN+xR1NsKTZxJ0Vwk0wcNq48Z0rUe2P2c9AsOyOlpQnZPQCDi3qN6T9
DZK5F/p3eZawMWrELe8UjWlv3/roDAKAqG+67ApllGyeDy+47kuKpsPeC1B38Hz5
w5sGGritGBkKDRe9jsL/jwpxGxjq5dtX9RrQxZm6iO83FYrcgUW6MBMwQ4wSLEQQ
9e5QVxuWNIithb1Z0ii6UYbZTyNv+3JzPI9vOsgSuQLJlmoyQlq4uy4jKbANg9os
pN7aPgy4oULv5T9Dwy9BuVLavAoew6jeC6tdseUICf6Ig2yifAjuW5cvcEHfzcfI
h6XjHBrN7yFcxJA8fzaF
=npkh
-END PGP SIGNATURE End Message ---

Bug#889608: Continuing to get core dumps with man-db

[Colin Watson]

On Mon, Feb 19, 2018 at 10:15:47AM +, Colin Watson wrote:
> Do you have an unusual libc or a modified libpipeline or something?  The
> sequence of system calls that your trace shows at the point where
> libpipeline should be calling execvp for nroff doesn't correspond to any
> libc implementation I can find, and the failure comes when it tries to
> open a Unix-domain socket in the middle of the execvp sequence which is
> just weird.

Ah, you're using an antivirus program.  Do mention that in bug reports
in future, since I spent a non-trivial amount of time digging to find
this out!  Please try git master, which has this patch:

  
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=6ed6c9f92ab8f981aa1aa664f7e607bcd540ad44

-- 
Colin Watson   [cjwat...@debian.org]

Bug#884023: marked as done (bibledit: Installs same file as bibledit-gtk)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 10:50:02 +
with message-id 
and subject line Bug#884023: fixed in bibledit 5.0.446-1
has caused the Debian Bug report #884023,
regarding bibledit: Installs same file as bibledit-gtk
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.)


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

Both bibledit-gtk and bibledit ship the same file:
/usr/share/pixmaps/bibledit.xpm

See § 7.6.1 of Debian Policy which recommends that you use Breaks/Replaces here.
https://www.debian.org/doc/debian-policy/#document-ch-relationships

Also, I highly recommend that you add a transitional package so that
people using bibledit-gtk will be upgraded to bibledit.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: bibledit
Source-Version: 5.0.446-1

We believe that the bug you reported is fixed in the latest version of
bibledit, 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.
Teus Benschop  (supplier of updated bibledit 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: Mon, 19 Feb 2018 10:36:08 +0100
Source: bibledit
Binary: bibledit bibledit-data
Architecture: source all amd64
Version: 5.0.446-1
Distribution: unstable
Urgency: low
Maintainer: CrossWire Packaging Team 

Changed-By: Teus Benschop 
Description:
 bibledit   - Bible editor
 bibledit-data - Data for bibledit
Closes: 884023
Changes:
 bibledit (5.0.446-1) unstable; urgency=low
 .
   * new upstream version
   * debian/postrm: better package purge
   * debian/postrm: better package purge
   * debian/bibledit.lintian-overrides: remove some comments
   * debian/control:
  added libmbedtls-dev to Build-Depends
  added Breaks/Replaces bibledit-gtk
   * Closes: #884023
Checksums-Sha1:
 c49d1fc869403457f90042ce008dfbb2372ed50c 2639 bibledit_5.0.446-1.dsc
 737fb1c8e55debd4d59d936d7327d859c6299dd7 60961532 bibledit_5.0.446.orig.tar.gz
 9ba167daa2bc44f72808ea1d07cd54bd9c8f92cd 833 bibledit_5.0.446.orig.tar.gz.asc
 b6cab538cfeade25f57d7589ccdf8a8a0302c302 11888 bibledit_5.0.446-1.debian.tar.xz
 842d3569ba881ce91881068cb4c6d6f883bdbbb4 38883660 
bibledit-data_5.0.446-1_all.deb
 29ac963f9fdcf149710439a57c1b057f9644501b 20785780 
bibledit-dbgsym_5.0.446-1_amd64.deb
 fe42ae5b1aed23494cff40962594bdc297715206 15216 
bibledit_5.0.446-1_amd64.buildinfo
 a6bc44e959d572b703ca928a82906b02d41b22bd 2514036 bibledit_5.0.446-1_amd64.deb
Checksums-Sha256:
 70c28b8b9fa3af06bdbe9149bcf2a53601e84fd3030df9b97bdf6e77daa677e5 2639 
bibledit_5.0.446-1.dsc
 0619f2481f244c8dcd3df389f28b648310ad907e9e1207e736d846ae357392a4 60961532 
bibledit_5.0.446.orig.tar.gz
 b3f9682426870decdbd9db97612f910ff19cb3a2185454239a14ebdfe56c11d9 833 
bibledit_5.0.446.orig.tar.gz.asc
 15f20c5dbb497c96cbbae512760a50e89a2da40f72a31ca18e05afa5b25f 11888 
bibledit_5.0.446-1.debian.tar.xz
 597632a6d31de2ffd3989af4b5b76479a21932ec4f569c95a38145169f49130e 38883660 
bibledit-data_5.0.446-1_all.deb
 7a821cf64dec14dbb24922a31f74c170f8886802c1e72c1756e8246aa7b03554 20785780 
bibledit-dbgsym_5.0.446-1_amd64.deb
 16fde05efc2675f516e9c2b259d842acc8e7a01fcb8af4d5d2e2c3876020d44c 15216 
bibledit_5.0.446-1_amd64.buildinfo
 91cb1482190f5c5ed02f296ab73a6b95e5510f1b1fb4cb9820bff35996ecc0b4 2514036 
bibledit_5.0.446-1_amd64.deb
Files:
 d37d094ab3733f0e99d638915b8a7b3f 2639 editors optional bibledit_5.0.446-1.dsc
 16ee51ab6517c62437f503582b97a289 60961532 editors optional 
bibledit_5.0.446.orig.tar.gz
 a2754300533e296b5e42e458cb4e57fc 833 editors optional 
bibledit_5.0.446.orig.tar.gz.asc
 436b723523062f92a16d227a40865116 11888 editors optional 
bibledit_5.0.446-1.debian.tar.xz
 06ca117cbd4ed6b54db8a2d7cfff4917 38883660 editors optional 
bibledit-data_5.0.446-1_all.deb
 0f6e9e5a58f2a7b362126e00484674f7 20785780 debug optional 
bibledit-dbgsym_5.0.446-1_amd64.deb
 

Bug#884973: tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?

[Elimar Riesebieter]

* Evgeni Golov  [2017-12-22 12:34 +0100]:

> control: severity -1 important
> 
> On Fri, Dec 22, 2017 at 10:03:17AM +0100, Elimar Riesebieter wrote:
> > Package: tp-smapi-dkms
> > Version: 0.42-1
> > Severity: serious
> > Justification: fails to build from source
> 
> Nope. 4.15 is not in Debian (not even experimental), so it can't be serious.

4.15 has been arrived in sid..

Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

Bug#889608: Continuing to get core dumps with man-db

[Colin Watson]

On Sun, Feb 18, 2018 at 07:22:01PM -0500, John Sivak wrote:
> On 02/18/2018 04:50 PM, Colin Watson wrote:
> > Any information at all would be good. :-)  Could you start by running
> > the relevant man command line under "strace -f -o man.trace -s 1024" and
> > attaching the resulting man.trace file?
> 
> Attached is the trace for the command "strace -f -o man.trace -s 1024
> man man".

(For the record, this is entirely unrelated to the original report
#889608.)

Do you have an unusual libc or a modified libpipeline or something?  The
sequence of system calls that your trace shows at the point where
libpipeline should be calling execvp for nroff doesn't correspond to any
libc implementation I can find, and the failure comes when it tries to
open a Unix-domain socket in the middle of the execvp sequence which is
just weird.

-- 
Colin Watson   [cjwat...@debian.org]

Processed: forwarded python3.6 issue (bpo-32305 causing regressions)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugs.python.org/issue32872
Bug #890621 [python3.6] python3-keyrings.alt 2.2-2 module.__file__ is None, 
causing regrtest.py to fail
Bug #890754 [python3.6] python3.6 3.6.4-4 makes typecatcher FTBFS
Set Bug forwarded-to-address to 'https://bugs.python.org/issue32872'.
Set Bug forwarded-to-address to 'https://bugs.python.org/issue32872'.
> tags -1 + upstream
Bug #890621 [python3.6] python3-keyrings.alt 2.2-2 module.__file__ is None, 
causing regrtest.py to fail
Bug #890754 [python3.6] python3.6 3.6.4-4 makes typecatcher FTBFS
Added tag(s) upstream.
Added tag(s) upstream.

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

Bug#890621: forwarded python3.6 issue (bpo-32305 causing regressions)

[Matthias Klose]

Control: forwarded -1 https://bugs.python.org/issue32872
Control: tags -1 + upstream

This is https://bugs.python.org/issue32305, apparently intentional and will be
in 3.7.  So better fix the packages itself. Not sure if that really should be
backported.

Bug#887696: marked as done (likwid FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 09:10:19 +
with message-id 
and subject line Bug#887696: fixed in likwid 4.3.1+dfsg1-1
has caused the Debian Bug report #887696,
regarding likwid FTBFS with glibc 2.26
to be marked as done.

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

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


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

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

...
In file included from ./hwloc/bind.c:11:0:
./include/private/private.h:249:10: fatal error: xlocale.h: No such file or 
directory
 #include "xlocale.h"
  ^~~
compilation terminated.
Makefile:52: recipe for target 'GCC/bind.o' failed
make[3]: *** [GCC/bind.o] Error 1
--- End Message ---
--- Begin Message ---
Source: likwid
Source-Version: 4.3.1+dfsg1-1

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

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

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated likwid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 30 Jan 2018 09:34:19 +0100
Source: likwid
Binary: likwid
Architecture: source amd64
Version: 4.3.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Christoph Martin 
Description:
 likwid - toolsuite for performance oriented programmers
Closes: 887696
Changes:
 likwid (4.3.1+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 4.3.1+dfsg1
   * fix build problem with newer libc (closes: #887696)
Checksums-Sha1:
 e178707477f95cbe08210a908ebc7d3bdf5164bc 1935 likwid_4.3.1+dfsg1-1.dsc
 f2419589ad321732e8cc11089a785ce5e0a8a775 1340345 likwid_4.3.1+dfsg1.orig.tar.gz
 03fcefc8e6f30e86540eccae26b1f59088e8a66b 53948 
likwid_4.3.1+dfsg1-1.debian.tar.xz
 99e3dfd4e3cb2102c9144921e6623a3c6f130204 534616 
likwid-dbgsym_4.3.1+dfsg1-1_amd64.deb
 fb8ddbdda83879845412103f8804efc93e6413ef 6724 
likwid_4.3.1+dfsg1-1_amd64.buildinfo
 9c057208dac286f7d6e20441491033f6c287ab56 697212 likwid_4.3.1+dfsg1-1_amd64.deb
Checksums-Sha256:
 c1613ed8552b7d49005abfb4f04332e5418c4d34a8ae337af3bb351257c9df20 1935 
likwid_4.3.1+dfsg1-1.dsc
 75caa92819f92eb8576ca1241cf67f61b9445cdab520236d2eba46de775284e7 1340345 
likwid_4.3.1+dfsg1.orig.tar.gz
 80f86637439b7ec78d1e0dd3077398193124c774f5a82624db32a16294d0310c 53948 
likwid_4.3.1+dfsg1-1.debian.tar.xz
 068159e5652257dbe40e3af950cc70daa0e1518e0a44854ab7ca078f97e6e5e4 534616 
likwid-dbgsym_4.3.1+dfsg1-1_amd64.deb
 0bd615bf67987077bc8f3704184cc31ac3b608cb40ccc9ebb46aaeba44a7f599 6724 
likwid_4.3.1+dfsg1-1_amd64.buildinfo
 98c870f44c8487399a42feaea694e7a88581b4d4a785dc57a9b7c93a60ecccd2 697212 
likwid_4.3.1+dfsg1-1_amd64.deb
Files:
 ac221fed2ca36c3898f52cb26a09ef73 1935 misc optional likwid_4.3.1+dfsg1-1.dsc
 bbc60e269fa2299c7fb194bedd58a329 1340345 misc optional 
likwid_4.3.1+dfsg1.orig.tar.gz
 0a4029fe9de18c062af10a66d0429b9b 53948 misc optional 
likwid_4.3.1+dfsg1-1.debian.tar.xz
 a1e1a60d2d7805184cb459b1fdf10d4b 534616 debug optional 
likwid-dbgsym_4.3.1+dfsg1-1_amd64.deb
 afb25fd3158689d99d61f0d4da654510 6724 misc optional 
likwid_4.3.1+dfsg1-1_amd64.buildinfo
 4143b233e0060a65af827d8a30956853 697212 misc optional 
likwid_4.3.1+dfsg1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOfrwsFcJT/ueFKkqgMEJ8ujseQEFAlpwM/QACgkQgMEJ8ujs
eQG6zhAAr0uug65jJOU+C2HN3fW9TmiPpeCe8DD3hSDZuS9j8bYoGOvQoz2EMQyz
++UepRlsXaGuCn+2tl9LjnIZhDqUU0HVzjRp8zaV5zrQd5AMD9ZC0OvweneMjwjo
Ng6WeokVt1Afy9KCk9/Ava8SfW4TIRPq+uW23oiHF2JGbMecfT9nykim+PuWeQwP
iHcU0kPg3R8uRvM5Eu9odrxOFYX5QVinfdsHT9MW+UjIKGPiXFEAK47ilZRjws6X
06N2FPxlzz8kLH4jKoTALFKBNzQ65k3TuVvjZIn3q2+w7xiY4OvN4tOhAxTQtqIi
T3nOUFUHv6VdsaczcClGPKXTPMQ1xs25TlMQZ3Sk+dqz/3IosJLKiYGFC9DRXelH
ejN42Oq+ykCcuC9+U980HyhoasUQ8uAeRst1PoBu1HAf9422IoocN1LuhvwFlmso
eJP72Np9EiJO+YVP2wpg+WxEZaMEPma6FPNL2tiydUSOX07zMUKAOh3NCcccGdWB

Bug#857496: marked as done (rollup: doesn't work but works when I set NODE_PATH to external non-Debian node install)

[Debian Bug Tracking System]

Your message dated Mon, 19 Feb 2018 14:19:14 +0530
with message-id 
and subject line this is fixed in current versions
has caused the Debian Bug report #857496,
regarding rollup: doesn't work but works when I set NODE_PATH to external 
non-Debian node install
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.)


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

Dear Maintainer,

Thanks for packaging rollup. However, it doesn't work at the moment:

$ rollup -c
[TypeError: Cannot read property 'id' of undefined]

However this works:

$ NODE_PATH=xxx/rollup/node_modules rollup -c
# successfully builds three.js without error

xxx/rollup is where I cloned https://github.com/rollup/rollup
xxx/rollup/node_modules is the directory created after running "npm install"

You should be able to reproduce this by checking out

https://anonscm.debian.org/cgit/pkg-javascript/three.js.git/

and running the above commands, in a clean chroot after installing 
build-dependencies (plus rollup)

X

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (300, 'unstable'), (100, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #884973 [tp-smapi-dkms] tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?
Severity set to 'serious' from 'important'
> retitle -1 tp-smapi-dkms: build failure with 4.15.0
Bug #884973 [tp-smapi-dkms] tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?
Changed Bug title to 'tp-smapi-dkms: build failure with 4.15.0' from 
'tp-smapi-dkms: tp-smapi doesn't build for 4.15.0-rc?'.

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

Processed: your mail

[Debian Bug Tracking System]

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

> block 731340 by 862373
Bug #731340 [lintian] lintian: Check if debian/upstream files are valid YAML
731340 was not blocked by any bugs.
731340 was not blocking any bugs.
Added blocking bug(s) of 731340: 862373
>
End of message, stopping processing here.

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