Bug#884403: marked as done (lsh-utils FTBFS with nettle-dev 3.4-1)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jan 2018 07:50:28 +
with message-id 
and subject line Bug#884403: fixed in lsh-utils 2.1-12
has caused the Debian Bug report #884403,
regarding lsh-utils FTBFS with nettle-dev 3.4-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.)


-- 
884403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lsh-utils
Version: 2.1-11
Severity: serious
Tags: buster sid

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

...
In file included from dummy.c:31:0:
dummy.c:115:1: error: conflicting types for 'nettle_base64_encode_update'
 base64_encode_update(struct base64_encode_ctx *ctx UNUSED,
 ^
/usr/include/nettle/base64.h:98:1: note: previous declaration of 
'nettle_base64_encode_update' was here
 base64_encode_update(struct base64_encode_ctx *ctx,
 ^
dummy.c:122:1: error: conflicting types for 'nettle_base64_encode_final'
 base64_encode_final(struct base64_encode_ctx *ctx UNUSED,
 ^
/usr/include/nettle/base64.h:106:1: note: previous declaration of 
'nettle_base64_encode_final' was here
 base64_encode_final(struct base64_encode_ctx *ctx,
 ^
dummy.c:131:1: error: conflicting types for 'nettle_base64_decode_update'
 base64_decode_update(struct base64_decode_ctx *ctx UNUSED,
 ^
/usr/include/nettle/base64.h:158:1: note: previous declaration of 
'nettle_base64_decode_update' was here
 base64_decode_update(struct base64_decode_ctx *ctx,
 ^
Makefile:1034: recipe for target 'dummy.o' failed
make[5]: *** [dummy.o] Error 1
--- End Message ---
--- Begin Message ---
Source: lsh-utils
Source-Version: 2.1-12

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

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

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

Debian distribution maintenance software
pp.
Magnus Holmgren  (supplier of updated lsh-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Jan 2018 21:57:40 +0100
Source: lsh-utils
Binary: lsh-utils lsh-server lsh-client lsh-doc
Architecture: source amd64 all
Version: 2.1-12
Distribution: unstable
Urgency: medium
Maintainer: Magnus Holmgren 
Changed-By: Magnus Holmgren 
Description:
 lsh-client - Secure Shell v2 (SSH2) protocol client
 lsh-doc- Secure Shell v2 (SSH2) documentation
 lsh-server - Secure Shell v2 (SSH2) protocol server
 lsh-utils  - Secure Shell v2 (SSH2) protocol utilities
Closes: 884403
Changes:
 lsh-utils (2.1-12) unstable; urgency=medium
 .
   * nettle3.4.patch: Fix FTBFS with nettle 3.4 due to type changes
 (Closes: #884403).
   * Build-Depend on debhelper (>= 9.20160709) instead of dh-systemd.
   * Priority extra replaced by optional.
   * lsh-server.postinst: Don't call /etc/init.d scripts directly (policy
 9.3.3.2).
   * Standards-Version raised to 4.1.3.
   * Remove Stefan Pfetzing from Uploaders.
Checksums-Sha1:
 2ce576ca6fc63a60f16300f1d543dbc1b87d3afd 2121 lsh-utils_2.1-12.dsc
 2747838167c2c62fa15eb6e38914af6e963cf7aa 37904 lsh-utils_2.1-12.debian.tar.xz
 54180c6f8504004e46b498e57b722da5344a1dab 1267512 
lsh-client-dbgsym_2.1-12_amd64.deb
 193281c327631fd038b2c1bb707056f612c48e7a 266000 lsh-client_2.1-12_amd64.deb
 a89cd2d5623b8faace7d62649cb5a16fbca91b5b 199880 lsh-doc_2.1-12_all.deb
 3d5163e2a93482d53a963f09f8dc605ac07b0b9b 813764 
lsh-server-dbgsym_2.1-12_amd64.deb
 eba366617774ec84da4922f917334aadc7dfc34b 226652 lsh-server_2.1-12_amd64.deb
 5d840b978f104bb6e2ae6a41d71efccde7812041 2012408 
lsh-utils-dbgsym_2.1-12_amd64.deb
 936d95f9c4462037e92d264dfa5ff520ca98d3fb 8615 lsh-utils_2.1-12_amd64.buildinfo
 de5e48c1dff311da4800bf8290709a1dd61c7e4c 269576 lsh-utils_2.1-12_amd64.deb
Checksums-Sha256:
 26638e8679c54e91b10ebb56f6c3f850227720496d53b3a837af02bada2df51b 2121 
lsh-utils_2.1-12.dsc
 c19776166105a1c9897e9d6cb420984dade00c2d73e62b8f1568a09ca6b148b1 37904 
lsh-utils_2.1-12.debian.tar.xz
 4db1babe073d770fe52378d386e06485c778ad869e2f17d198d147de10638260 1267512 
lsh-client-dbgsym_2.1-12_amd64.deb
 

Bug#886093: searx: Fails to start when using Python 3

[Johannes Schauer]

Control: severity -1 normal
Control: tags -1 + unreproducible

On Tue, 2 Jan 2018 11:21:31 +0530 Joseph Nuthalapati  
wrote:
> SearX currently doesn't start up when run with Python 3 as it tries to parse
> the settings.yml file with ASCII codecs. The file has a list of languages
> which are in Unicode characters.

Please provide more proof of your claim.

I have the package installed on a live server. Please find the output of $(dpkg
-l | grep py) at the bottom of this email. You will find that I don't even have
python 2 installed. Thus, searx will definitely run using Python3. Still, I am
unable to reproduce your findings.

The package even Depends on Python3. I don't see any reason why the package
would use Python2 when deployed.

Another proof that this package works fine with Python3 is the continuous
integration data gathered for this package. The package contains an autopkgtest
test which is run regularly on Debian infrastructure and which checks whether
the front page of searx loads successfully.

You can see here what the test script does:

https://sources.debian.org/src/searx/0.13.1+dfsg1-3/debian/tests/general/

You can see here that the test passes:

https://ci.debian.net/packages/s/searx/unstable/amd64/

You can see in the data of the latest test, that *only* python3 packages were
installed:

https://ci.debian.net/data/packages/unstable/amd64/s/searx/20180109_160457.log
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/searx/20180109_160457/log.gz

Thus, there is no way that searx on my own live system or on the CI system
could possibly run with Python2 and not with Python3.

Please provide more support for your theory.

Thanks!

cheers, josch





$ dpkg -l | grep py
ii  dh-python   2.20170125  all  
Debian helper tools for packaging Python libraries and applications
ii  libpython3-stdlib:amd64 3.5.3-1 amd64
interactive high-level object-oriented language (default python3 version)
rc  libpython3.4:amd64  3.4.2-1 amd64
Shared Python runtime library (version 3.4)
rc  libpython3.4-minimal:amd64  3.4.2-1 amd64
Minimal subset of the Python language (version 3.4)
ii  libpython3.5:amd64  3.5.3-1 amd64
Shared Python runtime library (version 3.5)
ii  libpython3.5-minimal:amd64  3.5.3-1 amd64
Minimal subset of the Python language (version 3.5)
ii  libpython3.5-stdlib:amd64   3.5.3-1 amd64
Interactive high-level object-oriented language (standard library, version 3.5)
ii  python-apt-common   1.4.0~beta3 all  
Python interface to libapt-pkg (locales)
ii  python-babel-localedata 2.3.4+dfsg.1-2  all  
tools for internationalizing Python applications - locale data files
ii  python3 3.5.3-1 amd64
interactive high-level object-oriented language (default python3 version)
ii  python3-apt 1.4.0~beta3 amd64
Python 3 interface to libapt-pkg
ii  python3-babel   2.3.4+dfsg.1-2  all  
tools for internationalizing Python applications - Python 3.x
ii  python3-certifi 2016.2.28-1 all  
root certificates for validating SSL certs and verifying TLS hosts (python3)
ii  python3-cffi-backend1.9.1-2 amd64
Foreign Function Interface for Python 3 calling C code - runtime
ii  python3-chardet 2.3.0-2 all  
universal character encoding detector for Python3
ii  python3-click   6.6-1   all  
Simple wrapper around optparse for powerful command line utilities - Python 3.x
ii  python3-colorama0.3.7-1 all  
Cross-platform colored terminal text in Python - Python 3.x
ii  python3-cryptography1.7.1-2 amd64
Python library exposing cryptographic recipes and primitives (Python 3)
ii  python3-dateutil2.5.3-2 all  
powerful extensions to the standard datetime module
ii  python3-flask   0.12-1  all  
micro web framework based on Werkzeug and Jinja2 - Python 3.x
ii  python3-flask-babel 0.11.1-1all  
internationalization and localization support for Flask (Python 3)
ii  python3-idna2.2-1   all  
Python IDNA2008 (RFC 5891) handling (Python 3)
ii  python3-itsdangerous0.24+dfsg1-2all  
Various helpers to pass trusted data to untrusted environment - Python 3.x
ii  python3-jinja2  2.8-1   

Processed: Re: searx: Fails to start when using Python 3

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #886093 [searx] searx: Fails to start when using Python 3
Severity set to 'normal' from 'grave'
> tags -1 + unreproducible
Bug #886093 [searx] searx: Fails to start when using Python 3
Added tag(s) unreproducible.

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

Bug#885010: python-ldap: Incomplete debian/copyright?

[Willem van den Akker]

On Fri, 22 Dec 2017 20:58:39 + Chris Lamb  wrote:
> Source: python-ldap
> Version: 3.0.0~b3-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Willem van den Akker 
> 
> Hi,
> 
> I just ACCEPTed python-ldap from NEW but noticed it was missing 
> attribution in debian/copyright for at least the code copy of
> shutil.which in Lib/ldap/compat.py.
> 
> (This is not exhaustive so please check over the entire package 
> carefully and address these on your next upload.)
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
> 
> 

Chris,

What is the best way to add those embedded source files?
Is the next entry in debian/config sufficient?

Files: Lib/ldap/compat.py
Comment: shutil.py is embedded in compat.py and has its own
 copyright.
Copyright: Python-ldap project
License: Python

/Willem

Bug#865588: [Python-modules-team] Bug#865588: Bug#865588: djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py

[Brian May]

Thijs Kinkhorst  writes:

> We're half a year on, so has this now changed? (I tried to check out the
> git repo and build it, but that had several problems so I might be missing
> one or two pieces to quickly verify it).

I believe Antonio has been looking at fixing the dependancies. I CCed him.

Possibly there are errors in the git packaging that need to be fixed. I
stopped as soon as I encountered problems, because I did not have the
time to fix them.
-- 
Brian May 

Bug#880766: marked as done (dvipng build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jan 2018 05:04:11 +
with message-id 
and subject line Bug#880766: fixed in dvipng 1.15-1
has caused the Debian Bug report #880766,
regarding dvipng build depends on removed libgd2*-dev provides
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.)


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

The following packages have unmet dependencies:
 builddeps:dvipng : Depends: libgd2-noxpm-dev but it is not installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: dvipng
Source-Version: 1.15-1

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

Debian distribution maintenance software
pp.
Varun Hiremath  (supplier of updated dvipng 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, 09 Jan 2018 23:30:45 -0500
Source: dvipng
Binary: dvipng
Architecture: source amd64
Version: 1.15-1
Distribution: unstable
Urgency: medium
Maintainer: Varun Hiremath 
Changed-By: Varun Hiremath 
Description:
 dvipng - convert DVI files to PNG graphics
Closes: 712570 778524 810364 880766
Changes:
 dvipng (1.15-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #810364)
   * New release fixes segfaults (Closes: #778524, #712570)
   * Build-Depends: replace libgd2-noxpm-dev with libgd-dev (Closes: #880766)
   * Update Standards-Version to 4.1.2
Checksums-Sha1:
 ce25b3cbba336f0b868188fc59f69b7524860e0e 1880 dvipng_1.15-1.dsc
 05c3152af62dc178267efbbe5a2ebe9aba9b3078 171529 dvipng_1.15.orig.tar.gz
 9f39f5992fb24a79ee28bb9e9a160498881fe6fe 4428 dvipng_1.15-1.debian.tar.xz
 8b0ce3dc79e43ca0b7cc350554eaf27d5475dc7e 119412 dvipng-dbgsym_1.15-1_amd64.deb
 44ec85b1a9842d027437babf23fb1af03d548505 7276 dvipng_1.15-1_amd64.buildinfo
 38a94316c0cf36da5c89d6dd28aa47931f9c8f03 87052 dvipng_1.15-1_amd64.deb
Checksums-Sha256:
 1bbc2ce8d1990e8366a958bc35361c889ba3addb6b49a3a26246f8306868ccfb 1880 
dvipng_1.15-1.dsc
 197e9fd0f87ede32dc4bc1d39ec2cd72fa5260856f9d0dc2d8e6895130408347 171529 
dvipng_1.15.orig.tar.gz
 ef8a74de7248ac4bc7908b52f7ed6705e40728eabaa34450d0eb330f4f321aa3 4428 
dvipng_1.15-1.debian.tar.xz
 c5b1d793a4bc8b64d3255d65a73f88bf8882d0b78e244f8423dbe0c6b672c75c 119412 
dvipng-dbgsym_1.15-1_amd64.deb
 edb18b315e6efe684b74af53d8494b5cc3bfdc66fb4f4fcd59d52907184caceb 7276 
dvipng_1.15-1_amd64.buildinfo
 830767f18c4329a0df5c82dcc0705d0dc76cc41a4c650c1586d2e11d1453d21a 87052 
dvipng_1.15-1_amd64.deb
Files:
 02ed3e7bfd24209d568443298d19c1ed 1880 utils optional dvipng_1.15-1.dsc
 c82043f4a366a560bb87fd9eafb6ef2f 171529 utils optional dvipng_1.15.orig.tar.gz
 cdc457e213b37e0cc80b7f598561d01b 4428 utils optional 
dvipng_1.15-1.debian.tar.xz
 f701027c0eb9e0be61ca004b6da31ae8 119412 debug optional 
dvipng-dbgsym_1.15-1_amd64.deb
 ca7f42d0950d0e38b77a4592a89806bb 7276 utils optional 
dvipng_1.15-1_amd64.buildinfo
 c944a9706a8b741f28cd89158d6ef07d 87052 utils optional dvipng_1.15-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEDBnIgiN9JdQ7ikG+cDc88SkNuc4FAlpVmzYACgkQcDc88SkN
uc5Hxg/7BSodbzkjpqrl2O4E+WACwBDEpicnnjViWkhuUJMq1sMCG5i4QDncSP31
p+C7cPlxFZNt7xJ/1tF7pQpbtOowndtN922+MM4FmWYmMYFaHFjRPVN03DNZcpTb
Im8g1ewVI5xXMgt/vOj00l0CBHyHuG31+/Ad70oHELsnCLh0h15DP2lv+pc7quJi
RmTas45d1OF4T5AhsNYDoJff5wol5Y6pOA4yvs+CC5z2457767aJZ4DkKyFls5h1
CbmkqIrPLKRbGsk31aHa0kPc/mDu4yiLyMlSliPDjaVVGyUya7UmVJO6xVY3DJVp
LZlBmuU3GJ0Q4nbJ1J1vvXkMsIpfwBoOTEuV+V8QXoO+tbIKH7jUmA7sEX3blKX7
zkLp3XomizVUQJoywjkpZTU2QJnOwQOuZly8uI0SNXsUtLrRgZa6oMVuBC8i9K1A
8kLFOHeu5Dwcahs7v/wJ5LU5TdKJ1JNtpBLVaFr+8/d4wfX9t2zUqWO2lhgoVFb5
Wrxj/BtC7I6PurledWVomNGNFc/nAQPEqyOoofwa8JkMDQsz1tjEgZSTnZwopuyq
X0aE6UI76l2FBjnvvXKVwCzHrDjTPvEiLIm1WWcXsQJyCgrKchIFUBFQhEEFwrUU
Vg7+EvTk/5Y+cpX3gPFi6MBnKK5So0TRq/be5me82oYjyrEc7ck=
=sUzW
-END PGP SIGNATURE End Message ---

Bug#867939: marked as done (smbnetfs: Build-Depends on deprecated libgnome-keyring-dev)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jan 2018 04:19:19 +
with message-id 
and subject line Bug#867939: fixed in smbnetfs 0.6.1-1
has caused the Debian Bug report #867939,
regarding smbnetfs: Build-Depends on deprecated libgnome-keyring-dev
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.)


-- 
867939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smbnetfs
Version: 0.6.0-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome-keyring-removal

Hi,

The libgnome-keyring library is deprecated and its usage is strongly
discouraged [1].

Your package smbnetfs declares a build-dependency on
libgnome-keyring-dev or links against libgnome-keyring0.

Please update your application to use libsecret instead [2].
Such a port should ideally happen with upstream being involved.

On behalf of the Debian GNOME team,
Michael Biebl

[1] https://git.gnome.org/browse/libgnome-keyring/commit/?id=6a5adea4aec93
[2] https://wiki.gnome.org/Projects/Libsecret
--- End Message ---
--- Begin Message ---
Source: smbnetfs
Source-Version: 0.6.1-1

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

Debian distribution maintenance software
pp.
Mikhail Kshevetskiy  (supplier of updated 
smbnetfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 Jan 2018 00:24:15 +0400
Source: smbnetfs
Binary: smbnetfs
Architecture: source amd64
Version: 0.6.1-1
Distribution: unstable
Urgency: low
Maintainer: Mikhail Kshevetskiy 
Changed-By: Mikhail Kshevetskiy 
Description:
 smbnetfs   - User-space filesystem for SMB/NMB (Windows) network servers and s
Closes: 601708 867939
Changes:
 smbnetfs (0.6.1-1) unstable; urgency=low
 .
   [ Mikhail Kshevetskiy ]
   * New upstream release
   * debian/control:
 + Bump up Standards-Version to 4.1.2 (fix lintian warning)
 + add libsecret-1-dev >= 0.18.5 to build depends
 + remove libgnome-keyring-dev from build depends (Closes: #867939)
 .
   [ Varun Hiremath ]
   * Update Vcs fields to new debian git repository (Closes: #601708)
   * Add libattr1-dev to Build-Depends
Checksums-Sha1:
 81bacf69284abc1cf4a43a5b28498cdb59993c3a 2054 smbnetfs_0.6.1-1.dsc
 cb87717a08d35f254574e1ec81bbac680792fd46 171032 smbnetfs_0.6.1.orig.tar.bz2
 744def41c12abda929178be24d07f3c038e916e1 6060 smbnetfs_0.6.1-1.debian.tar.xz
 5bbc881f5caf2fa6a3af8a204a2831fc02e8cd8b 159420 
smbnetfs-dbgsym_0.6.1-1_amd64.deb
 6e98ba471d1ce00c9996a521905f38f6adcd2766 7905 smbnetfs_0.6.1-1_amd64.buildinfo
 20aa37301f8ee26db130623dc207ff3848b75c26 67760 smbnetfs_0.6.1-1_amd64.deb
Checksums-Sha256:
 05ab3639750ffae8c613436fc1fe3902d3cdd6b13586c8dc3466956e61b09b07 2054 
smbnetfs_0.6.1-1.dsc
 848b8ee4c1b5cc4c83ee35736cb28e1ddcd5789cca948f060e8cb76baa95380a 171032 
smbnetfs_0.6.1.orig.tar.bz2
 f0120589240679982cba0621c7cd487b25601bd4074680361da3ee096f898a55 6060 
smbnetfs_0.6.1-1.debian.tar.xz
 6dee0575b0ff499f944dc3a7ba56395ba2819186f65a1501c23f0df74792985c 159420 
smbnetfs-dbgsym_0.6.1-1_amd64.deb
 22b406dce30bf440af5b3e388a02342e38c4d91c683a215cbec86622cc1052a4 7905 
smbnetfs_0.6.1-1_amd64.buildinfo
 b9487bef89132e4f6eb06c39fbc63b0eb933991ce618ffe0a2080f8245ce4d2b 67760 
smbnetfs_0.6.1-1_amd64.deb
Files:
 aa49d31eee3cd9a70baeb427af15fdee 2054 net optional smbnetfs_0.6.1-1.dsc
 478c222be3d0082c86a1e3be5af6bbba 171032 net optional 
smbnetfs_0.6.1.orig.tar.bz2
 8f71f326348be4bba53e89f31b484d0a 6060 net optional 
smbnetfs_0.6.1-1.debian.tar.xz
 1f46f995011358a8402abd781dd7bfbe 159420 debug optional 
smbnetfs-dbgsym_0.6.1-1_amd64.deb
 b9b903ed0339b447131d65309bceade7 7905 net optional 
smbnetfs_0.6.1-1_amd64.buildinfo
 c3ba57d0688181e880816bdad6fbf3d0 67760 net optional smbnetfs_0.6.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEDBnIgiN9JdQ7ikG+cDc88SkNuc4FAlpVjlwACgkQcDc88SkN

Bug#873468: CUDA 9.0 transition

[Andreas Beckmann]

Hi,

CUDA 9.0 finally reached experimental. Did someone get around testing
it, yet?

I'd like to start the transition soon. There are only two rdepends left
in testing (and going to be autorm'ed in 5 days) - both pycuda and
hwloc-contrib seem to be (manually) binNMUable.
I didn't test the other rdepends that are in sid only. But they will
need sourceful uploads anyway for switching the compiler (to gcc-6/g++-6
- not the default, but the best we can get and still better than clang-3.x).


Andreas

Bug#886734: marked as done (libgdk-pixbuf2.0-0: undefined symbol after upgrade (wheezy-security): gdk_pixbuf_calculate_rowstride)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jan 2018 08:55:22 +0530
with message-id 
<1515554722.1247329.1230112896.67cf4...@webmail.messagingengine.com>
and subject line Re: Bug#886721: [SECURITY] [DLA 1234-1] gdk-pixbuf security 
update
has caused the Debian Bug report #886721,
regarding libgdk-pixbuf2.0-0: undefined symbol after upgrade (wheezy-security): 
gdk_pixbuf_calculate_rowstride
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.)


-- 
886721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgdk-pixbuf2.0-0
Version: 2.26.1-1+deb7u7
Severity: important

Dear Maintainer,

after security upgrade i get following eror message due to an undefined symbol:

g_module_open() failed for 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so: 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so: 
undefined symbol: gdk_pixbuf_calculate_rowstride

Maybe related to bug report #886721?

Regards, Robert

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable-updates
  APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgdk-pixbuf2.0-0 depends on:
ii  libc62.13-38+deb7u12
ii  libgdk-pixbuf2.0-common  2.26.1-1+deb7u7
ii  libglib2.0-0 2.33.12+really2.32.4-5
ii  libjasper1   1.900.1-13+deb7u6
ii  libjpeg8 8d-1+deb7u1
ii  libpng12-0   1.2.49-1+deb7u2
ii  libtiff4 3.9.6-11+deb7u8
ii  libx11-6 2:1.5.0-1+deb7u4
ii  multiarch-support2.13-38+deb7u12

libgdk-pixbuf2.0-0 recommends no packages.

libgdk-pixbuf2.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.26.1-1+deb7u8

Hi Simon et al.,

> It looks like GNOME cgit's line-number marking and browser scrolling
> behaviour interacts poorly with the fixed top navigation bar

D'oh!

Note that this was fixed in:

  gdk-pixbuf (2.26.1-1+deb7u8) wheezy-security; urgency=medium

* debian/patches/CVE-2017-1000422.patch: fix undefined reference to
  g_uint64_checked_mul, which is only available in glib since 2.48,
  and to gdk_pixbuf_calculate_rowstride, available in gdk-pixbuf since
  2.36.8. Closes: #886721.

Thanks Emilio!


Best wishes,

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

Bug#886721: marked as done (libgdk-pixbuf2.0-0: undefined symbol after upgrade : g_uint64_checked_mul)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jan 2018 08:55:22 +0530
with message-id 
<1515554722.1247329.1230112896.67cf4...@webmail.messagingengine.com>
and subject line Re: Bug#886721: [SECURITY] [DLA 1234-1] gdk-pixbuf security 
update
has caused the Debian Bug report #886721,
regarding libgdk-pixbuf2.0-0: undefined symbol after upgrade : 
g_uint64_checked_mul
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.)


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

Package: libgdk-pixbuf2.0-0Version: 2.26.1-1+deb7u7Severity: normal
Dear Maintainer,
when upgrading  libgdk-pixbuf2.0   on wheezy i have the following error in the 
upgrade process
[...]Setting up libgdk-pixbuf2.0-common (2.26.1-1+deb7u7) ...Setting up 
libgdk-pixbuf2.0-0:i386 (2.26.1-1+deb7u7) ...g_module_open() failed for 
/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so: 
/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so: 
undefined symbol: g_uint64_checked_mul
I do not know the exact impact of the error
Thanks,
fred


-- System Information:Debian Release: 7.11  APT prefers oldoldstable-updates  
APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')Architecture: 
i386 (i686)
Kernel: Linux 3.2.0-5-686-pae (SMP w/1 CPU core)Locale: LANG=en_US.UTF-8, 
LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)Shell: /bin/sh linked to /bin/dash
Versions of packages libgdk-pixbuf2.0-0 depends on:ii  libc6                    
2.13-38+deb7u12ii  libgdk-pixbuf2.0-common  2.26.1-1+deb7u7ii  libglib2.0-0     
        2.33.12+really2.32.4-5ii  libjasper1               1.900.1-13+deb7u6ii  
libjpeg8                 8d-1+deb7u1ii  libpng12-0               
1.2.49-1+deb7u2ii  libtiff4                 3.9.6-11+deb7u8ii  libx11-6         
        2:1.5.0-1+deb7u4ii  multiarch-support        2.13-38+deb7u12
libgdk-pixbuf2.0-0 recommends no packages.
libgdk-pixbuf2.0-0 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.26.1-1+deb7u8

Hi Simon et al.,

> It looks like GNOME cgit's line-number marking and browser scrolling
> behaviour interacts poorly with the fixed top navigation bar

D'oh!

Note that this was fixed in:

  gdk-pixbuf (2.26.1-1+deb7u8) wheezy-security; urgency=medium

* debian/patches/CVE-2017-1000422.patch: fix undefined reference to
  g_uint64_checked_mul, which is only available in glib since 2.48,
  and to gdk_pixbuf_calculate_rowstride, available in gdk-pixbuf since
  2.36.8. Closes: #886721.

Thanks Emilio!


Best wishes,

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

Bug#886806: intel-microcode: New version 20180108 published

[Karl Kornel]

Package: intel-microcode
Version: 3.20171215.1
Severity: grave
Tags: security

Hello!

In the ancient past (last week…), Mr. Holschuh mentioned, “I expect an official 
release from Intel soon, hopefully with updates for everything.”.

Well, it looks like there has been a release!  The data file version is 
20180108.

The microcode download page is 
https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File

--
A. Karl Kornel | System Administrator
Research Computing | Stanford University

Processed: found 886506 in 4.14.7-1, severity of 886506 is important

[Debian Bug Tracking System]

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

> found 886506 4.14.7-1
Bug #886506 [src:linux] linux-image-4.14.0-3-686-pae: Kernel panic during 
reboot - since 4.14.0-2 - 4.14.0-1 works normal and boots
Marked as found in versions linux/4.14.7-1.
> severity 886506 important
Bug #886506 [src:linux] linux-image-4.14.0-3-686-pae: Kernel panic during 
reboot - since 4.14.0-2 - 4.14.0-1 works normal and boots
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#869994: proposed fix

[Stephen Schmiechen]

Yeah I tend to run several customised instances in lots of locations so
FindBin is less fragile for me and works most like the 'dot' did.
So hopefully it saves someone some time.
Cheers
--turtle

On Mon, Jan 8, 2018 at 12:24 PM, Robert J. Clay  wrote:

> > Greetings all using FindBin and adding the current directory everywhere
> > sql-ledger calls perl should fix the issue in all versions.
>
>I appreciate the example perl script you provided but since it's
> known where the package is installing sql-ledger to, I don't think
> using "FindBin" is necessary.  At least, that's what what I'm assuming
> with the patch I've created for the ITA[1] I've been working on.  I
> originally wrote the patch against sql-ledger 3.0.8 but will be
> updating as necessary for use against the most recent version I
> currently see, which is 3.2.6.
>
>
> --
> Robert J. Clay
> rjc...@gmail.com
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862963
>

Bug#886802: python-uniconvertor: cannot be installed

[Christoph Anton Mitterer]

Package: python-uniconvertor
Version: 1.1.5-4
Severity: grave
Justification: renders package unusable


Hi.

Since python-imaging is gone now, the package can not longer be installed.

Cheers,
Chris.

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

[Russell Klopfer]

Sean,

That worked for me too! Thanks a lot. When this patch is finally 
released by gnome, do I need to worry about removing the patch I just 
intalled? Or will apt properly install over top of it?


Thanks agian,

Russell

On Tue, Jan 9, 2018 at 11:13 AM, Laurent Martelli 
 wrote:

On Tue, 9 Jan 2018 01:44:01 -0600 Sean DuBois  wrote:
> Hey Russel,

Thanks Sean, it saved my day :-)

> ```
> apt-get build-dep network-manager-gnome

You need sudo for this one too :

sudo apt-get build-dep network-manager-gnome

Bests,
Laurent

> apt-get source network-manager-gnome
> cd network-manager-applet-1.8.10/debian/patches/
> curl 
"https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=885525;filename=Fix-segfault-on-vpn-connect.patch;msg=59; 
> Fix-segfault-on-vpn-connect.patch

> echo Fix-segfault-on-vpn-connect.patch >> series
> cd ../..
> dpkg-buildpackage -uc -us
> sudo dpkg -i ../network-manager-gnome_1.8.10-1_amd64.deb
>

--
Laurent Martelli // Service Numérique
Tél : 01 80 48 16 14 / 614

--
To unsubscribe, send mail to 885525-unsubscr...@bugs.debian.org.

Processed: mark as forwarded

[Debian Bug Tracking System]

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

> forwarded 886756 https://jira.mariadb.org/browse/MDEV-14904
Bug #886756 [mariadb-server-10.1] Regression: Specified key was too long; max 
key length is 767 bytes
Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse/MDEV-14904'.
> thanks
Stopping processing here.

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

Bug#886663: marked as done (golang-go-patricia FTBFS: cannot find package "github.com/satori/go.uuid")

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 22:34:32 +
with message-id 
and subject line Bug#886663: fixed in golang-go-patricia 2.2.6-2
has caused the Debian Bug report #886663,
regarding golang-go-patricia FTBFS: cannot find package 
"github.com/satori/go.uuid"
to be marked as done.

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

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


-- 
886663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-go-patricia
Version: 2.2.6-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-go-patricia=all=2.2.6-1=1515263839=0

...
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/tchap/go-patricia/patricia
github.com/tchap/go-patricia/patricia
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -v -p 1 
github.com/tchap/go-patricia/patricia
# github.com/tchap/go-patricia/patricia
src/github.com/tchap/go-patricia/patricia/patricia_dense_test.go:12:2: cannot 
find package "github.com/satori/go.uuid" in any of:
/usr/lib/go-1.9/src/github.com/satori/go.uuid (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/satori/go.uuid 
(from $GOPATH)
FAILgithub.com/tchap/go-patricia/patricia [setup failed]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -v -p 1 
github.com/tchap/go-patricia/patricia returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-go-patricia
Source-Version: 2.2.6-2

We believe that the bug you reported is fixed in the latest version of
golang-go-patricia, 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.
Alexandre Viau  (supplier of updated golang-go-patricia 
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, 09 Jan 2018 15:43:28 -0500
Source: golang-go-patricia
Binary: golang-github-tchap-go-patricia-dev
Architecture: source
Version: 2.2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 golang-github-tchap-go-patricia-dev - golang-go-patricia is a generic patricia 
trie (also called radix
Closes: 886663
Changes:
 golang-go-patricia (2.2.6-2) unstable; urgency=medium
 .
   * Team upload.
   * Depend on golang-github-satori-go.uuid-dev (Closes: #886663)
   * Remove golang-go-patricia-dev from d/control.
Checksums-Sha1:
 bafec2aa80d012af9f389091ddfcc5e7c1a8390f 2261 golang-go-patricia_2.2.6-2.dsc
 d6044b10cb4a73a0cd1a94a6b8e34816b750fc8a 2812 
golang-go-patricia_2.2.6-2.debian.tar.xz
 9db1db8b5137ee1f8a119edae8aa67634ccf1921 5580 
golang-go-patricia_2.2.6-2_source.buildinfo
Checksums-Sha256:
 24e961bbe6e4f57ac45204106b5812eb8d5e0826ea6fed7195f97acb3bbd3577 2261 
golang-go-patricia_2.2.6-2.dsc
 689165eec8cf36743eaa0f3665f8a60d20541bc51f9105c158f2dbf2ea6928ed 2812 
golang-go-patricia_2.2.6-2.debian.tar.xz
 4647eac453c05c1699e80e6dda9e155a537fbcfd966a8208b06d962a31000a98 5580 
golang-go-patricia_2.2.6-2_source.buildinfo
Files:
 7fb2f330e073e24f02a93ca331313c3c 2261 devel optional 
golang-go-patricia_2.2.6-2.dsc
 837abaf912ed3ea13dbc8ea8de471177 2812 devel optional 
golang-go-patricia_2.2.6-2.debian.tar.xz
 97b50156d10e277c29589d19d5a961ea 5580 devel optional 
golang-go-patricia_2.2.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAlpVPj0RHGF2aWF1QGRl
Ymlhbi5vcmcACgkQjysRPGU1xac+pA/9H/NFyagPi9GbBeXXkUpkwHV89DzP227M
GqlhEFtBBoUntPawemj35zzJni4fAj/LvHecuYiEQv39whWy34M4XPBKkbCI77fg
6GEYDAYt3aLJQl5azG1omyQamuH9F7WiHktnJXIqbE2nqVWEkIMip8OMm+UDPEz2
YOFOLhGc8qQIEoRa+e1TaYYc6PlBGnsv1znJVGrhGUUy3YI3N8XYlYrYCwFLT3Eh
Kc2SL1WbTl2MNTsJTNOjY62yBiZXtoMyrnut0v8qoRiyp3OXCXjDAnLHF/Ltpalw

Bug#882292: marked as done (acpica-unix FTBFS on 32bit big endian: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 22:19:15 +
with message-id 
and subject line Bug#882292: fixed in acpica-unix 20180105-1
has caused the Debian Bug report #882292,
regarding acpica-unix FTBFS on 32bit 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.)


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

https://buildd.debian.org/status/package.php?p=acpica-unix=sid

...
Installing ACPICA tools
list of testcases: aslts
Make-install all the provided test cases
Make n32
Running make install from /<>/tests/aslts
Begin compiling test package: [src]
Begin compiling test package: [runtime]
Begin compiling test package: [collections]
Begin compiling test package: [bdemo]
Begin compiling test package: [ACPICA]
Begin compiling test package: [bdemo]
Test path: 
/<>/tests/aslts/src/runtime/collections/bdemo/ACPICA/bdemo
Type: nopt/32 Compile => Removing filesrm: cannot remove 'MAIN.asm': No 
such file or directory
rm: cannot remove 'MAIN.c': No such file or directory
rm: cannot remove 'MAIN.h': No such file or directory
rm: cannot remove 'MAIN.i': No such file or directory
rm: cannot remove 'MAIN.hex': No such file or directory
rm: cannot remove 'MAIN.lst': No such file or directory
rm: cannot remove 'MAIN.map': No such file or directory
rm: cannot remove 'MAIN.nsp': No such file or directory
rm: cannot remove 'MAIN.offset.h': No such file or directory
rm: cannot remove 'MAIN.src': No such file or directory
 => Done 
ls: cannot access 'bdemo.aml': No such file or directory
mv: cannot stat 'bdemo.aml': No such file or directory
Compiled test package: [bdemo]
Begin compiling test package: [bdemof]
Test path: 
/<>/tests/aslts/src/runtime/collections/bdemo/ACPICA/bdemof
Type: nopt/32 Compile => Removing filesrm: cannot remove 'MAIN.asm': No 
such file or directory
rm: cannot remove 'MAIN.c': No such file or directory
rm: cannot remove 'MAIN.h': No such file or directory
rm: cannot remove 'MAIN.i': No such file or directory
rm: cannot remove 'MAIN.hex': No such file or directory
rm: cannot remove 'MAIN.lst': No such file or directory
rm: cannot remove 'MAIN.map': No such file or directory
rm: cannot remove 'MAIN.nsp': No such file or directory
rm: cannot remove 'MAIN.offset.h': No such file or directory
rm: cannot remove 'MAIN.src': No such file or directory
 => Done 
ls: cannot access 'bdemof.aml': No such file or directory
mv: cannot stat 'bdemof.aml': No such file or directory
Compiled test package: [bdemof]
Compiled test package: [ACPICA]
Compiled test package: [bdemo]
Begin compiling test package: [complex]
Begin compiling test package: [misc]
Test path: /<>/tests/aslts/src/runtime/collections/complex/misc
Type: nopt/32 Compile => Removing filesrm: cannot remove 'MAIN.asm': No 
such file or directory
rm: cannot remove 'MAIN.c': No such file or directory
rm: cannot remove 'MAIN.h': No such file or directory
rm: cannot remove 'MAIN.i': No such file or directory
rm: cannot remove 'MAIN.hex': No such file or directory
rm: cannot remove 'MAIN.lst': No such file or directory
rm: cannot remove 'MAIN.map': No such file or directory
rm: cannot remove 'MAIN.nsp': No such file or directory
rm: cannot remove 'MAIN.offset.h': No such file or directory
rm: cannot remove 'MAIN.src': No such file or directory
 => Done 
ls: cannot access 'misc.aml': No such file or directory
mv: cannot stat 'misc.aml': No such file or directory
Compiled test package: [misc]
Begin compiling test package: [provoke]
Test path: /<>/tests/aslts/src/runtime/collections/complex/provoke
Type: nopt/32 Compile => Removing filesrm: cannot remove 'MAIN.asm': No 
such file or directory
rm: cannot remove 'MAIN.c': No such file or directory
rm: cannot remove 'MAIN.h': No such file or directory
rm: cannot remove 'MAIN.i': No such file or directory
rm: cannot remove 'MAIN.hex': No such file or directory
rm: cannot remove 'MAIN.lst': No such file or directory
rm: cannot remove 'MAIN.map': No such file or directory
rm: cannot remove 'MAIN.nsp': No such file or directory
rm: cannot remove 'MAIN.offset.h': No such file or directory
rm: cannot remove 'MAIN.src': No such file or directory
 => Done 
ls: cannot access 'provoke.aml': No such file or directory
mv: cannot stat 'provoke.aml': No such file or directory
Compiled test package: [provoke]
Begin compiling test package: [operand]
Begin compiling test package: [tests]
Begin compiling test package: 

Bug#886780: i2pd: crash with SIGILL on CPUs without avx and aes

[Adam Borowski]

Package: i2pd
Version: 2.17.0-1
Severity: serious
Justification: programs must support baseline arch (w/o a good reason otherwise)

Hi!
I'm afraid that current version of i2pd crashes on startup on processors
that don't support avx and aes, unless the package was built on a machine
without such support (the build system does _compile time_ detection).

The in-archive binary package 2.17.0-1:amd64 is ok as it was built on such a
processor (in fact, the very same machine I'm testing on).  Alas, this is not
the case for :i386 (and presumably :x32), which crashes on daemon's startup:

[37476.565483] traps: i2pd[14112] trap invalid opcode ip:565aeb9d sp:ffd6c0a0 
error:0 in i2pd[56578000+292000]

A rebuild of :amd64 (binNMU, new source-only upload, Ubuntu, ...) would also
crash this way.


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

Kernel: Linux 4.15.0-rc7-debug-00025-g6c558864404f (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages i2pd:i386 depends on:
ii  adduser 3.116
ii  libboost-date-time1.62.01.62.0+dfsg-5
ii  libboost-filesystem1.62.0   1.62.0+dfsg-5
ii  libboost-program-options1.62.0  1.62.0+dfsg-5
ii  libboost-system1.62.0   1.62.0+dfsg-5
ii  libc6   2.26-2
ii  libgcc1 1:7.2.0-19
ii  libssl1.1   1.1.0g-2
ii  libstdc++6  7.2.0-19
ii  lsb-base9.20170808
ii  zlib1g  1:1.2.8.dfsg-5

i2pd:i386 recommends no packages.

i2pd:i386 suggests no packages.

-- no debconf information

Bug#886133: ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out

[Ludovico Cavedon]

Hi,

 I have an update on this: I have a patch for upstream review at
https://github.com/ntop/nDPI/pull/506.
It fixes this issue, but unittests still fail on s90x (and I guess on the
other big endian archs), so no new upload for now, until I debug that.

Ludovico

Bug#801331: marked as done (jdresolve: malformed output in jessie)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 19:20:32 +
with message-id 
and subject line Bug#801331: fixed in jdresolve 0.6.1-5.1
has caused the Debian Bug report #801331,
regarding jdresolve: malformed output in jessie
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.)


-- 
801331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jdresolve
Version: 0.6.1-4
Severity: important

With the latest version of Net::DNS / libnet-dns-perl the output of
jdresolve in jessie is malformed.

Here is a transcript:
$ cat /etc/debian_version
8.2
$ echo "8.8.8.8" | jdresolve -n -
Net::DNS::DomainName1035=HASH(0x1864e50)


In wheezy it is working as expected:
$ cat /etc/debian_version
7.9
$ echo "8.8.8.8" | jdresolve -n -
google-public-dns-a.google.com


A possible fix is described in
https://lists.freebsd.org/pipermail/freebsd-ports/2014-August/094535.html


Klaus Rein.

-- 
levigo systems gmbh  ---  ein unternehmen der levigo gruppe
Bebelsbergstrasse 31   Telefon: 07031 / 4161-10
D-71088 Holzgerlingen  Telefax: 07031 / 4161-11
Geschäftsführer: Oliver Bauschhttp://systems.levigo.de/
Registergericht: Stuttgart HRB 245 180  USt-ID: DE813226078
--- End Message ---
--- Begin Message ---
Source: jdresolve
Source-Version: 0.6.1-5.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated jdresolve 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, 04 Jan 2018 20:21:09 +0200
Source: jdresolve
Binary: jdresolve
Architecture: source
Version: 0.6.1-5.1
Distribution: unstable
Urgency: high
Maintainer: Frederic Peters 
Changed-By: Adrian Bunk 
Description:
 jdresolve  - fast alternative to apache logresolve
Closes: 801331
Changes:
 jdresolve (0.6.1-5.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Fix breakage with libnet-dns-perl in jessie and later,
 thanks to Klaus Rein for reporting the bug and
 Matt Johnston for forwarding the fix. (Closes: #801331)
Checksums-Sha1:
 31ad80d80bbfad4f20279cf1f059652b16ac9f3c 1650 jdresolve_0.6.1-5.1.dsc
 6e97ca42834ac8d596b245dc337e48ad6f55ff6c 2604 jdresolve_0.6.1-5.1.diff.gz
Checksums-Sha256:
 8667782207f9117827f14ac188ffc4c913126ead838b0dc01b5c44aa8cfe44a1 1650 
jdresolve_0.6.1-5.1.dsc
 fc4d3b6f69217f23c70b4d902a73ce3ebc259eef5225ae7d75abf63291fde8bc 2604 
jdresolve_0.6.1-5.1.diff.gz
Files:
 b2ecac409ad7a35b3db08b7c1137efe6 1650 utils extra jdresolve_0.6.1-5.1.dsc
 2adf8eb5da09e81fd6e2e2e147305653 2604 utils extra jdresolve_0.6.1-5.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlpOdEkACgkQiNJCh6LY
mLHDJRAAt8BfuPrE/YBzZb7ncwHp5PAGhMIyBGaWpRY2IxAY96SKPOvpFJDTId30
IlV+gW5Yqmrj9Ia8zzLTSfVAsPF90OV8869E7KswfmvzOxTEz5HGiO8A1cFDkVVV
LVb3rRTXmjWvIzI7dAV24dMWfbo74QFf/u22/V4p+is2PyUmm17gLnZs1LAEgjg6
bMyfDdHIePvOkElAGRGxtNHd6b/H6lKo9kcYnz5R8WImB4sjp0YajR5DH1S0jAJ1
7z/lopgLZ45sVNfAk0rqK+QVVTMRnHQjWS5J2Tc3uYJL7+fbuXKFwfYwxCKTFSuF
yVoCGMA1j2ijOf7H3QOCDTvz69a0S5LlP1mllyLB2P8/0fVqlWjoeyN7DDH1PKhw
qWu6JZRs7b7NDRU4QQKspRs+5s17x/VYDPI/UuTOeejnGu0n1pgj6Ktrg0HCAhoV
NY6dP88suXatdFLF1E1YQLu11G2DleD6Y5Z1Y6Irv3Xe3iOQcNk+gUPTZ7QuZy3P
HVqmKtyJrW7SM2YityAvYfsKQMKYp5w3Xo1/GSGLAmxTXMdLKPbh2vsujse3j6RT
y1r2SdCdkPbyJ5jItWOt/LgVjJDfEMD2Xw/XDPBVtqFfsX3kSXlDaQsSbEq9UxR5
g/Ye1xPhxa91FtkpopUWzFF1qe9u8B57b1cM4MG57xybKqnqFoo=
=laO2
-END PGP SIGNATURE End Message ---

Bug#842023: Tried updating to 11.5.1

[Sruthi Chandran]

Hi,

I tried updating node-jsdom to 11.5.1 but could not complete as there
are some unpackaged dependencies. I pushed what I did to my repo in
salsa[1].

[1] https://salsa.debian.org/srud-guest/node-jsdom



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#884209: nmu: rpy_1.0.3-30

[Debian Bug Tracking System]

Processing control commands:

> block 884134 by -1
Bug #884134 [python-rpy] python-rpy: Incompatible with the version of R in 
stretch
884134 was not blocked by any bugs.
884134 was not blocking any bugs.
Added blocking bug(s) of 884134: 884209
> clone -1 -2
Bug #884209 [release.debian.org] nmu: rpy_1.0.3-30
Bug 884209 cloned as bug 886771
884134 was blocked by: 884209
884134 was not blocking any bugs.
Added blocking bug(s) of 884134: 886771
> tags -1 - stretch
Bug #884209 [release.debian.org] nmu: rpy_1.0.3-30
Removed tag(s) stretch.
> retitle -1 nmu: rpy_1.0.3-30 (sid)
Bug #884209 [release.debian.org] nmu: rpy_1.0.3-30
Changed Bug title to 'nmu: rpy_1.0.3-30 (sid)' from 'nmu: rpy_1.0.3-30'.
> tags -2 - sid
Bug #886771 [release.debian.org] nmu: rpy_1.0.3-30
Removed tag(s) sid.
> retitle -2 nmu: rpy_1.0.3-30 (stretch)
Bug #886771 [release.debian.org] nmu: rpy_1.0.3-30
Changed Bug title to 'nmu: rpy_1.0.3-30 (stretch)' from 'nmu: rpy_1.0.3-30'.

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

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 886756 10.0.20-2
Bug #886756 [mariadb-server-10.1] Regression: Specified key was too long; max 
key length is 767 bytes
There is no source info for the package 'mariadb-server-10.1' at version 
'10.0.20-2' with architecture ''
Unable to make a source version for version '10.0.20-2'
Marked as found in versions 10.0.20-2.
> thanks
Stopping processing here.

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

Processed: tagging 885934, tagging 886721

[Debian Bug Tracking System]

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

> tags 885934 + sid buster
Bug #885934 {Done: Colin Watson } [python-libnacl] 
python-libnacl depends on cruft package libsodium18
Added tag(s) sid and buster.
> tags 886721 + wheezy
Bug #886721 [gdk-pixbuf] libgdk-pixbuf2.0-0: undefined symbol after upgrade : 
g_uint64_checked_mul
Bug #886734 [gdk-pixbuf] libgdk-pixbuf2.0-0: undefined symbol after upgrade 
(wheezy-security): gdk_pixbuf_calculate_rowstride
Added tag(s) wheezy.
Added tag(s) wheezy.
> thanks
Stopping processing here.

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

Processed: found 884417 in 0.7.16-3, found 886161 in 1.3.1-2.1, tagging 885640, tagging 886203, tagging 886209 ...

[Debian Bug Tracking System]

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

> found 884417 0.7.16-3
Bug #884417 [trezor] trezor: fails to upgrade from 'testing' - trying to 
overwrite /usr/bin/trezorctl
Marked as found in versions python-trezor/0.7.16-3.
> found 886161 1.3.1-2.1
Bug #886161 [auto-complete-el] auto-complete-el: extremely outdated, blocks 
packaging of new Emacs packages
Marked as found in versions auto-complete-el/1.3.1-2.1.
> tags 885640 + sid buster
Bug #885640 {Done: Jeremy Bicha } [src:gnome-commander] 
gnome-commander: Fix Build-Depends
Added tag(s) sid and buster.
> tags 886203 + sid buster
Bug #886203 [src:wavbreaker] FTBFS: dh: unable to load addon scour
Added tag(s) sid and buster.
> tags 886209 + sid buster
Bug #886209 [src:php-pecl-http] FTBFS: configure: error: please install and 
enable pecl/raphf
Added tag(s) buster and sid.
> tags 779809 + stretch sid buster
Bug #779809 [dwarves] /usr/bin/pahole: does not support DWARF 4
Added tag(s) buster, sid, and stretch.
> tags 753719 + sid buster
Bug #753719 [ucarp] ucarp: please recommend iproute2 instead of iproute 
transitional package
Bug #862852 [ucarp] ucarp: Please switch to iproute2 package
Added tag(s) sid and buster.
Added tag(s) buster and sid.
> tags 886306 + sid buster
Bug #886306 [src:python-pyocr] python-pyocr: FTBFS: "Unable to parse Tesseract 
version"
Added tag(s) buster and sid.
> found 886432 2016.08.01-1
Bug #886432 {Done: Michael Hudson-Doyle } 
[src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: constant 
9007199254740992 overflows int
Marked as found in versions golang-gopkg-mgo.v2/2016.08.01-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753719
779809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779809
862852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862852
884417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884417
885640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885640
886161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886161
886203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886203
886209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886209
886306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886306
886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Debian Bug Tracking System]

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

> severity 886742 normal
Bug #886742 [postgresql-9.4-postgis-2.1] postgresql-9.4-postgis-2.1 missing in 
stretch
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Processed: Re: Bug#886120: FTBFS: chown: cannot access '..._cgraph.dot': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +moreinfo +unreproducible
Bug #886120 [src:ctpp2] FTBFS: chown: cannot access '..._cgraph.dot': No such 
file or directory
Added tag(s) moreinfo.
Bug #886120 [src:ctpp2] FTBFS: chown: cannot access '..._cgraph.dot': No such 
file or directory
Added tag(s) unreproducible.

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

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

[Dominic Hargreaves]

On Mon, Jan 08, 2018 at 10:40:19PM +0200, Niko Tyni wrote:
> On Sun, Jan 07, 2018 at 05:04:17PM +0200, Niko Tyni wrote:
> 
> > The wasted stats could certainly be fixed by modifying our relevant
> > changes to perl.c
> >  
> > https://sources.debian.org/src/perl/5.26.1-3/debian/patches/debian/mod_paths.diff/
> > but I haven't looked into that properly yet.
> 
> I did this now and pushed to the 'ntyni/inc-version-list'
> branch of the Debian perl git repository.
> 
> The relevant changes are
> 
>  
> https://anonscm.debian.org/cgit/perl/perl.git/diff/debian/patches/debian/mod_paths.diff?h=ntyni/inc-version-list=3885251398d6e2897fa57cafe61134e4e14593ac
> 
>  
> https://anonscm.debian.org/cgit/perl/perl.git/commit/?h=ntyni/inc-version-list=f8e4ea6058a58019e78a5c3225a6ab4a3d0c6700
> 
> A test build fixes the polymake issue and doesn't seem to break anything
> major.
> 
> I'm inclined to reassign this bug to perl and close it with the above
> change unless I hear arguments to the contrary.

This all looks well reasoned and sensible, thanks for digging into
that!

Cheers,
Dominic.

Bug#886761: marked as done (FTBFS[s390x]: textflag.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 16:49:24 +
with message-id 
and subject line Bug#886761: fixed in golang-golang-x-net-dev 
1:0.0+git20170629.c81e7f2+dfsg-2
has caused the Debian Bug report #886761,
regarding FTBFS[s390x]: textflag.h: No such file or directory
to be marked as done.

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

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


-- 
886761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-golang-x-net-dev
Version: 1:0.0+git20170629.c81e7f2+dfsg-1
Severity: serious
Justification: fails to build from source

I noted a few packages failing to build from source on s390x, and tracked down
the cause to this package:

# golang.org/x/net/internal/socket
src/golang.org/x/net/internal/socket/sys_linux_s390x.s:5:10: fatal error: 
textflag.h: No such file or directory
 #include "textflag.h"
  ^~~~
compilation terminated.

It seems the source is meant to be compiled with golang-go (which includes
textflag.h), but we are compiling with gccgo, and thus it fails.


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: golang-golang-x-net-dev
Source-Version: 1:0.0+git20170629.c81e7f2+dfsg-2

We believe that the bug you reported is fixed in the latest version of
golang-golang-x-net-dev, 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.
Martín Ferrari  (supplier of updated golang-golang-x-net-dev 
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, 09 Jan 2018 16:30:51 +
Source: golang-golang-x-net-dev
Binary: golang-golang-x-net-dev golang-go.net-dev
Architecture: source all
Version: 1:0.0+git20170629.c81e7f2+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Go packaging team 

Changed-By: Martín Ferrari 
Description:
 golang-go.net-dev - Transitional package for golang-golang-x-net-dev
 golang-golang-x-net-dev - Supplementary Go networking libraries
Closes: 886761
Changes:
 golang-golang-x-net-dev (1:0.0+git20170629.c81e7f2+dfsg-2) unstable; 
urgency=high
 .
   [ Paul Tagliamonte ]
   * Remove Built-Using from arch:all -dev package
 .
   [ Martín Ferrari ]
   * Automated cme updates.
   * Update Standards-Version.
   * New lintian warnings that need to be overridden.
   * debian/rules: Remove now unneeded targets.
   * Fix builds in s390x. Closes: #886761 (raising urgency).
Checksums-Sha1:
 fc6fa8947f3028fc20e0da9c561a4cf402d543e0 2550 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2.dsc
 5961aba3cbf2cf79e679824a0e57eba17539b6fc 12600 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2.debian.tar.xz
 62bd78de0fca956a0f3773a2c6d659ae109b4b1a 11276 
golang-go.net-dev_0.0+git20170629.c81e7f2+dfsg-2_all.deb
 4b1095907d0079d156e2deffef7ac0282fb14099 603532 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2_all.deb
 bf0e347cf04239c23e4c3e38cb4b4929f9a03bb7 6280 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 06a716c253cad8e39523c02f8b93cacc8830197d0905db1301879aa2d411703f 2550 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2.dsc
 b13b24d19cded13393f3758e91e4e7403e43dbdc0577fa4de172175211b8a0fd 12600 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2.debian.tar.xz
 5ef4f923b1929e1cd8747b7f7264bb03c80949739a28d027615c35945f9da45f 11276 
golang-go.net-dev_0.0+git20170629.c81e7f2+dfsg-2_all.deb
 21c7b787d05f725c007780e9dff154e7b46b037c348a18a7e98f2ce830aa8e96 603532 
golang-golang-x-net-dev_0.0+git20170629.c81e7f2+dfsg-2_all.deb
 

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

[Laurent Martelli]

On Tue, 9 Jan 2018 01:44:01 -0600 Sean DuBois  wrote:
> Hey Russel,

Thanks Sean, it saved my day :-)

> ```
> apt-get build-dep network-manager-gnome

You need sudo for this one too :

sudo apt-get build-dep network-manager-gnome

Bests,
Laurent

> apt-get source network-manager-gnome
> cd network-manager-applet-1.8.10/debian/patches/
> curl 
"https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=885525;filename=Fix-segfault-on-vpn-connect.patch;msg=59; 
> Fix-segfault-on-vpn-connect.patch

> echo Fix-segfault-on-vpn-connect.patch >> series
> cd ../..
> dpkg-buildpackage -uc -us
> sudo dpkg -i ../network-manager-gnome_1.8.10-1_amd64.deb
>

--
Laurent Martelli // Service Numérique
Tél : 01 80 48 16 14 / 614

Bug#886666: marked as done (node-d3-shape FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 9 Jan 2018 21:40:20 +0530
with message-id 
and subject line fixed in node-d3-path
has caused the Debian Bug report #88,
regarding node-d3-shape FTBFS
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.)


-- 
88: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-d3-shape
Version: 1.2.0-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=node-d3-shape=all=1.2.0-2=1515264095=0

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
webpack --config debian/webpack.config.js \
--output-library=d3 \
index.js build/d3-shape.js
Hash: 0edb256ac8d106ecf390
Version: webpack 3.5.6
Time: 3110ms
  Asset Size  Chunks Chunk Names
d3-shape.js  83.8 kB   0  [emitted]  main
   [3] ./src/offset/none.js 432 bytes {0} [built]
   [4] ./src/order/none.js 256 bytes {0} [built]
   [5] ./src/curve/linear.js 922 bytes {0} [built]
   [7] ./src/curve/basis.js 1.61 kB {0} [built]
   [8] ./src/curve/cardinal.js 1.8 kB {0} [built]
   [9] ./src/line.js 1.91 kB {0} [built]
  [11] ./src/curve/catmullRom.js 2.86 kB {0} [built]
  [12] ./src/order/ascending.js 596 bytes {0} [built]
  [13] ./src/area.js 3.46 kB {0} [built]
  [26] ./src/curve/cardinalOpen.js 1.49 kB {0} [built]
  [27] ./index.js 9.83 kB {0} [built]
  [47] ./src/offset/silhouette.js 607 bytes {0} [built]
  [48] ./src/offset/wiggle.js 1.02 kB {0} [built]
  [49] ./src/order/descending.js 406 bytes {0} [built]
  [50] ./src/order/insideOut.js 856 bytes {0} [built]
+ 37 hidden modules

ERROR in /usr/lib/nodejs/d3-path/index.js
Module not found: Error: Can't resolve './src/path' in '/usr/lib/nodejs/d3-path'
 @ /usr/lib/nodejs/d3-path/index.js 7:12-33
 @ ./src/arc.js
 @ ./index.js
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---



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

Bug#886761: FTBFS[s390x]: textflag.h: No such file or directory

[Martín Ferrari]

Source: golang-golang-x-net-dev
Version: 1:0.0+git20170629.c81e7f2+dfsg-1
Severity: serious
Justification: fails to build from source

I noted a few packages failing to build from source on s390x, and tracked down
the cause to this package:

# golang.org/x/net/internal/socket
src/golang.org/x/net/internal/socket/sys_linux_s390x.s:5:10: fatal error: 
textflag.h: No such file or directory
 #include "textflag.h"
  ^~~~
compilation terminated.

It seems the source is meant to be compiled with golang-go (which includes
textflag.h), but we are compiling with gccgo, and thus it fails.


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#886756: Regression: Specified key was too long; max key length is 767 bytes

[Jonas Meurer]

Package: mariadb-server-10.1
Version: 1:10.1.29-6
Severity: serious
Tags: upstream

Control: -1 forwarded https://jira.mariadb.org/browse/MDEV-14904

Hello,

I just discovered that MariaDB 10.1 packages in Sid, Buster and Stretch
break applications that expect a maximum allowed size of 255 characters
for VARCHAR fields. E.g.:

> django.db.utils.OperationalError: (1071, 'Specified key was too long;
> max key length is 767 bytes')

This is due to the fact that MariaDB in Debian has `utf8mb4` set as
default character since version 10.0.20-2 which raises the required
amount of memory per character.

To still allow fields with > 191 < 255 characters, `innodb_large_prefix`
has to be enabled, which in turn requires the following settings:

> innodb_file_format  = Barracuda
> innodb_file_per_table   = On
> innodb_large_prefix = On

Unfortunately even that is not enough. Additionally, the row format for
tables needs to be changed to `dynamic`.

Starting with MariaDB 10.2, `innodb_default_row_format` was introduced,
which allows to set the default row format for the whole MariaDB server.
Unfortunately, this option is not available in MariaDB 10.1 yet. In
other words, there's no way to configure MariaDB 10.1 in Debian in a way
that it works with applications that expect things like VARCHAR(255) to
be possible.

This is a severe regression. I discussed this topic with MariaDB
upstream developer Marko Mäkelä (dr-m) on IRC and he agreed that they
can backport `innodb_default_row_format` for the next upstream release
of MariaDB 10.1. I created an upstream bugreport to track this:

https://jira.mariadb.org/browse/MDEV-14904

I suggest that this fix should be backported to MariaDB 10.1 in Debian
Stable as well as it is a severe regression compared to MySQL and
earlier MariaDB versions (i.e. pre 10.0.20-2).

PS: This problem doesn't exist with MariaDB >= 10.2 or MySQL 5.7 as
both switched to `Barracudea` as default `innodb_file_format` along
with `innodb_large_prefix` and `dynamic` as default row format.

See the following bugreports and discussion threads for further details:

* https://jira.mariadb.org/browse/MDEV-9646
* https://code.djangoproject.com/ticket/18392
* 
https://stackoverflow.com/questions/30761867/mysql-error-the-maximum-column-size-is-767-bytes

Cheers
 jonas

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

Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mariadb-server-10.1 depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.61
pn  galera-3  
ii  gawk  1:4.1.4+dfsg-1
ii  init-system-helpers   1.48
ii  iproute2  4.9.0-1+deb9u1
ii  libaio1   0.3.110-3
ii  libc6 2.24-11+deb9u1
ii  libdbi-perl   1.636-1+b1
ii  libpam0g  1.1.8-3.6
ii  libstdc++66.3.0-18
ii  libsystemd0   232-25+deb9u1
ii  lsb-base  9.20161125
ii  lsof  4.89+dfsg-0.1
ii  mariadb-client-10.1   10.1.26-0+deb9u1
ii  mariadb-common10.1.26-0+deb9u1
pn  mariadb-server-core-10.1  
ii  passwd1:4.4-4.1
ii  perl  5.24.1-3+deb9u2
ii  psmisc22.21-2.1+b2
ii  rsync 3.1.2-1+deb9u1
ii  socat 1.7.3.1-2+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
pn  libhtml-template-perl  

Versions of packages mariadb-server-10.1 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
pn  mariadb-test   
ii  netcat-openbsd 1.130-3
pn  tinyca 

Bug#886163: marked as done (lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: output differs!)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 15:35:31 +
with message-id 
and subject line Bug#886163: fixed in lintian 2.5.68
has caused the Debian Bug report #886163,
regarding lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: 
output differs!
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.)


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

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

...
tests::files-multiarch-foreign-files: diff -u 
t/tests/files-multiarch-foreign-files/tags 
/build/1st/lintian-2.5.67/debian/test-out/tests/files-multiarch-foreign-files/tags.files-multiarch-foreign-files
--- t/tests/files-multiarch-foreign-files/tags  2018-01-01 14:58:24.0 
+
+++ 
/build/1st/lintian-2.5.67/debian/test-out/tests/files-multiarch-foreign-files/tags.files-multiarch-foreign-files
2019-02-04 09:30:53.054375012 +
@@ -1,3 +0,0 @@
-E: libfoo-dev: multiarch-foreign-cmake-file usr/lib/TRIPLET/cmake/foo.cmake
-E: libfoo-dev: multiarch-foreign-pkgconfig usr/lib/TRIPLET/pkgconfig/libfoo.pc
-E: libfoo-dev: multiarch-foreign-static-library usr/lib/TRIPLET/libfoo.a
fail tests::files-multiarch-foreign-files: output differs!


SS..
Skipped/disabled tests:
  [debs]
deb-format-wrong-order: Unmet test dependencies: dpkg (<< 1.17.2)
  [tests]
changelog-file-strange-date: Unmet test dependencies: dpkg (<< 1.18.2)
deb-format-udeb-compression: Unmet test dependencies: dpkg (<< 1.18.11)
debconf-config-not-executable: Unmet test dependencies: dpkg (<< 1.19.0)
debhelper-compat: Unmet test dependencies: debhelper (<< 9.20151101~)
debhelper-compat-empty: Unmet test dependencies: debhelper (<< 9.20151101~)
runtests-arch-amd64: architecture mismatch
upstream-metadata-invalid-yml: (disabled) YAML::XS executes code by default 
and code has not been converted
version-substvars-obsolete: Unmet test dependencies: dpkg (<< 1.17.2)

Failed tests (1)
tests::files-multiarch-foreign-files
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.68

We believe that the bug you reported is fixed in the latest version of
lintian, 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.
Chris Lamb  (supplier of updated lintian 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, 09 Jan 2018 14:33:30 +
Source: lintian
Binary: lintian
Built-For-Profiles: nocheck
Architecture: source all
Version: 2.5.68
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 648755 677870 687141 749202 884142 885974 886057 886101 886163 886210 
886219 886259 886271 886297 886303 886343 886426 886479 886555 886566 886574 
886586
Changes:
 lintian (2.5.68) unstable; urgency=medium
 .
   * Summary of tag changes:
 + Added:
   - dh-quilt-addon-but-quilt-source-format
   - orphaned-package-not-maintained-in-debian-infrastructure
   - package-contains-python-hypothesis-example
   - should-specify-rules-requires-root
   - vcs-deprecated-in-debian-infrastructure
 .
   * checks/changelog-file.pm:
 + [FL] Fix version parsing for hyphen in upstream versions.
   * checks/cruft.pm:
 + [CL] Avoid a false-positive reported by Theppitak Karoonboonyanan
   when matching autotools-pkg-config-macro-not-cross-compilation-safe
   by skipping comment lines.  (Closes: #886297)
 + [FL] Fix version parsing for native packages.
   * checks/control-file.{desc.pm}:
 + [CL] Check for packages that should specify Rules-Require-Root.
 

Processed: fixed 886666 in 1.0.5-3

[Debian Bug Tracking System]

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

> fixed 88 1.0.5-3
Bug #88 [node-d3-path] node-d3-shape FTBFS
Marked as fixed in versions node-d3-path/1.0.5-3.
> thanks
Stopping processing here.

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

Processed: found 886666 in 1.0.5-2

[Debian Bug Tracking System]

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

> found 88 1.0.5-2
Bug #88 [node-d3-path] node-d3-shape FTBFS
Marked as found in versions node-d3-path/1.0.5-2.
> thanks
Stopping processing here.

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

Processed: affects 886666

[Debian Bug Tracking System]

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

> affects 88 node-d3-shape
Bug #88 [node-d3-path] node-d3-shape FTBFS
Added indication that 88 affects node-d3-shape
> thanks
Stopping processing here.

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

Processed: reassign 886666 to node-d3-path

[Debian Bug Tracking System]

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

> reassign 88 node-d3-path
Bug #88 [src:node-d3-shape] node-d3-shape FTBFS
Bug reassigned from package 'src:node-d3-shape' to 'node-d3-path'.
No longer marked as found in versions node-d3-shape/1.2.0-2.
Ignoring request to alter fixed versions of bug #88 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#886742: [INFO] Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Francesco P. Lovergine]

On Tue, Jan 09, 2018 at 02:37:44PM +0100, Jürgen Fuchsberger wrote:
> >> What did you try, and what didn't work?
> > 
> > Probably pg_upgradecluster, and that is not supported for databases with
> > the postgis extension.
> > 
> Exactly. Just wanted to point out that upgrading was no possibility
> either, the actual problem was that the database could not be accessed
> or dumped after the upgrade.

While ideally one could use hook scripts to manage such kind of extensions
I would not try that approach in any case. A Postgis hard upgrade is 
generally a trial-and-error nightmare^Wexperience and it depends on
languages, extensions, encodings. Last time, I had to perform a series
of ad hoc setups before trying the restore. I strongly suggest to 
run both servers and extensions on the host in order to run a successfully shop 
upgrade later. 
That is definitively possible, I have at least one server still running 
both 8.4 and 9.4 with required Postgis extensions.

-- 
Francesco P. Lovergine

Bug#822595: marked as done (caja-extensions: depends on gksu which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 14:49:31 +
with message-id 
and subject line Bug#822595: fixed in caja-extensions 1.18.2-1
has caused the Debian Bug report #822595,
regarding caja-extensions: depends on gksu which is deprecated
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: caja-extensions
Source-Version: 1.18.2-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated caja-extensions 
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, 09 Jan 2018 15:23:02 +0100
Source: caja-extensions
Binary: caja-image-converter caja-open-terminal caja-sendto caja-share 
caja-wallpaper caja-xattr-tags caja-extensions-common
Architecture: source
Version: 1.18.2-1
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 caja-extensions-common - Caja extensions (common files)
 caja-image-converter - Caja extension to mass resize or rotate images
 caja-open-terminal - Caja plugin for opening terminals in arbitrary local paths
 caja-sendto - integrates email clients and Pidgin into the Caja file manager
 caja-share - Allows one to quickly share a folder from the Caja file manager
 caja-wallpaper - Allows one to quickly set a wallpaper from folders
 caja-xattr-tags - Allows one to view extended attributes
Closes: 822595
Changes:
 caja-extensions (1.18.2-1) unstable; urgency=medium
 .
   [ Martin Wimpress ]
   * New upstream release.
 .
   [ Mike Gabriel ]
   * Drop caja-gksu bin:package. The gksu utility is deprecated and will be
 removed from Debian soon. (Closes: #822595).
   * debian/control:
 + Typo fix in LONG_DESCRIPTION of bin:package caja-xattr.
   * debian/control:
 + Bump Standards-Version: to 4.1.3. No changes needed.
   * debian/{control,compat}:
 + Bump to DH version level 11.
   * debian/watch:
 + Use secure URL to obtain upstream sources.
Checksums-Sha1:
 160535e11869dcaf25441cf6704aaa1519b3797e 2767 caja-extensions_1.18.2-1.dsc
 045cc7845799bcab1f386eb9a5d77c9d09f0e6cf 150848 
caja-extensions_1.18.2.orig.tar.xz
 5475c4019f63e6f806223ca5ade3637a15f40b56 5812 
caja-extensions_1.18.2-1.debian.tar.xz
 7558fbe073fb918fe81b07912147dc34e6766f07 15065 
caja-extensions_1.18.2-1_source.buildinfo
Checksums-Sha256:
 b1b17bfff11e20ece55f1b8b0f92f1bb9bc3982ad3de8a13e34aefe373973c20 2767 
caja-extensions_1.18.2-1.dsc
 a3cec5fae81d7b3efe19f66cc71ad04744089b40bc15079280cfaa7930320152 150848 
caja-extensions_1.18.2.orig.tar.xz
 3df71b3597aaa274cd0c1fef82ef29e0b041fa853c875b1566dbcf2cc612b1be 5812 
caja-extensions_1.18.2-1.debian.tar.xz
 10842166f8fde8d876266985402b7ce18228568de52786b66f5e8e1cdb5eb29b 15065 
caja-extensions_1.18.2-1_source.buildinfo
Files:
 c904ff5051fc0bf5f5a78a8f04d0e176 2767 x11 optional caja-extensions_1.18.2-1.dsc
 e85ba68e250f70d87e2b798ebb7fbf98 150848 x11 optional 

Processed: Bug#822595 marked as pending

[Debian Bug Tracking System]

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

> tag 822595 pending
Bug #822595 [src:caja-extensions] caja-extensions: depends on gksu which is 
deprecated
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822595: marked as pending

[Mike Gabriel]

tag 822595 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/pkg-mate/caja-extensions.git/commit/?id=cea8ab6

---
commit cea8ab6a906acafb576dfda826c91e6bb361dcec
Author: Mike Gabriel 
Date:   Tue Jan 9 15:38:23 2018 +0100

upload to unstable (debian/1.18.2-1)

diff --git a/debian/changelog b/debian/changelog
index 0fe5380..cb91e18 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,21 @@
-caja-extensions (1.18.2-1) UNRELEASED; urgency=medium
+caja-extensions (1.18.2-1) unstable; urgency=medium
 
+  [ Martin Wimpress ]
   * New upstream release.
 
- -- Martin Wimpress   Mon, 13 Nov 2017 19:09:32 
+
+  [ Mike Gabriel ]
+  * Drop caja-gksu bin:package. The gksu utility is deprecated and will be
+removed from Debian soon. (Closes: #822595).
+  * debian/control:
++ Typo fix in LONG_DESCRIPTION of bin:package caja-xattr.
+  * debian/control:
++ Bump Standards-Version: to 4.1.3. No changes needed.
+  * debian/{control,compat}:
++ Bump to DH version level 11.
+  * debian/watch:
++ Use secure URL to obtain upstream sources.
+
+ -- Mike Gabriel   Tue, 09 Jan 2018 15:23:02 +0100
 
 caja-extensions (1.18.1-1) unstable; urgency=medium
 

Bug#862899: rsync: insufficient escaping/quoting of arguments

[Olaf van der Spek]

Hi,

Any updates?

-- 
Olaf

Bug#886721: [SECURITY] [DLA 1234-1] gdk-pixbuf security update

[Simon McVittie]

On Tue, 09 Jan 2018 at 11:07:49 +, Chris Lamb wrote:
> Hi Emilio,
> 
> > If you don't have the time now I can take a look at this later today.
> 
> Please, although it's more that my IEEE 754 is pretty rusty… :)

It looks like GNOME cgit's line-number marking and browser scrolling
behaviour interacts poorly with the fixed top navigation bar. Please
scoll up to line 434, which is just above the IEEE 754 stuff.

Knowing the finer details of IEEE 754 floating point isn't going to
help you to avoid integer multiplication overflows, but the code in
GLib just above it can :-)

smcv

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Jürgen Fuchsberger]

On 2018-01-09 14:16, Bas Couwenberg wrote:
> On 2018-01-09 14:08, Christoph Berg wrote:
>> Re: Juergen Fuchsberger 2018-01-09
>> <20180109130149.17725.10545.report...@wegc203058.uni-graz.at>
>>> Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis enabled
>>> database becomes corrupt when upgrading from jessie to stretch since
>>> the required postgis libraries are missing. This can cause serious data
>>> loss, because once upgraded to stretch, the postgis data can't be
>>> accesed nor dumped (Database gives error "could not access file
>>> "$libdir/postgis-2.1": no such file or directory").
>>
>> Could you append the apt output to this bug? Namely, which packages
>> got removed? (/var/log/apt/term.log)
>>
>>> Also upgrading the database to postgresql-9.6 does not work.
>>
>> What did you try, and what didn't work?
> 
> Probably pg_upgradecluster, and that is not supported for databases with
> the postgis extension.
> 
Exactly. Just wanted to point out that upgrading was no possibility
either, the actual problem was that the database could not be accessed
or dumped after the upgrade.

Juergen

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Bas Couwenberg]

On 2018-01-09 14:08, Christoph Berg wrote:

Re: Juergen Fuchsberger 2018-01-09
<20180109130149.17725.10545.report...@wegc203058.uni-graz.at>
Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis 
enabled

database becomes corrupt when upgrading from jessie to stretch since
the required postgis libraries are missing. This can cause serious 
data

loss, because once upgraded to stretch, the postgis data can't be
accesed nor dumped (Database gives error "could not access file
"$libdir/postgis-2.1": no such file or directory").


Could you append the apt output to this bug? Namely, which packages
got removed? (/var/log/apt/term.log)


Also upgrading the database to postgresql-9.6 does not work.


What did you try, and what didn't work?


Probably pg_upgradecluster, and that is not supported for databases with 
the postgis extension.


See my reply to #886738 and 
http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2017-November/064317.html


For more info, see:

 http://blog.cleverelephant.ca/2016/08/postgis-upgrade.html
 
http://www.bostongis.com/blog/index.php?/archives/268-Using-pg_upgrade-to-upgrade-PostGIS-without-installing-an-older-version-of-PostGIS.html


As long as the postgis package is built for a single postgresql version, 
upgrades cannot be supported.


When using postgis on Debian, distribution upgrades involve recreating 
the postgis databases as pg_upgradecluster will fail.


Kind Regards,

Bas

Processed: Re: Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #886742 [postgresql-9.4-postgis-2.1] postgresql-9.4-postgis-2.1 missing in 
stretch
Added tag(s) moreinfo.

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

Bug#866862: marked as done (diaspora-installer: installs world-writable ruby libraries)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 13:04:03 +
with message-id 
and subject line Bug#866862: fixed in diaspora-installer 0.6.6.0+debian2
has caused the Debian Bug report #866862,
regarding diaspora-installer: installs world-writable ruby libraries
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.)


-- 
866862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora-installer
Version: 0.6.6.0+debian1
Severity: grave
Tags: security
Justification: user security hole
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package installs
world-writable files, including a bunch of .rb scripts, allowing
unprivileged local users to "customize" your diaspora experience.

Since this is a downloader package, it needs to sanitize the
stuff it downloads and installs from the net.

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

  ERROR: BAD PERMISSIONS
  -rw-rw-rw- 1 diaspora nogroup 1935 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/configurate-0.3.1/lib/configurate/lookup_chain.rb
  -rw-rw-rw- 1 diaspora nogroup  154 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/.gitignore
  -rw-rw-rw- 1 diaspora nogroup  242 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/.travis.yml
  -rw-rw-rw- 1 diaspora nogroup   98 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/Gemfile
  -rw-rw-rw- 1 diaspora nogroup 1069 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/LICENSE.txt
  -rw-rw-rw- 1 diaspora nogroup 3354 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/README.md
  -rw-rw-rw- 1 diaspora nogroup  233 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/Rakefile
  -rw-rw-rw- 1 diaspora nogroup  918 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store.rb
  -rw-rw-rw- 1 diaspora nogroup  233 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store/middleware.rb
  -rw-rw-rw- 1 diaspora nogroup  785 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store/railtie.rb
  -rw-rw-rw- 1 diaspora nogroup   44 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store/version.rb
  -rw-rw-rw- 1 diaspora nogroup  943 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/request_store.gemspec
  -rw-rw-rw- 1 diaspora nogroup  981 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/test/middleware_test.rb
  -rw-rw-rw- 1 diaspora nogroup 1607 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/test/request_store_test.rb
  -rw-rw-rw- 1 diaspora nogroup  267 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/test/test_helper.rb
  -rw-rw-rw- 1 diaspora nogroup 3255 Jun 29 20:24 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/twitter-text-1.14.5/README.md


cheers,

Andreas


diaspora-installer_0.6.6.0+debian1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: diaspora-installer
Source-Version: 0.6.6.0+debian2

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated diaspora-installer 
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, 08 Jan 2018 20:40:24 +0530
Source: diaspora-installer
Binary: diaspora-installer diaspora-installer-mysql diaspora-common
Architecture: source
Version: 0.6.6.0+debian2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 

Bug#865588: [Python-modules-team] Bug#865588: djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py

[Thijs Kinkhorst]

Hi Brian,

> Currently getting this error building the latest version - as in the
> Debian git package.
>
> Possibly this is because we depend on a package that needs updating -
> mostly likely mkdocs or jinja2 - but wonder which one?  Maybe we should
> just update both anyway.

We're half a year on, so has this now changed? (I tried to check out the
git repo and build it, but that had several problems so I might be missing
one or two pieces to quickly verify it).


Cheers,
Thijs

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Christoph Berg]

Control: tags -1 moreinfo

Re: Juergen Fuchsberger 2018-01-09 
<20180109130149.17725.10545.report...@wegc203058.uni-graz.at>
> Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis enabled
> database becomes corrupt when upgrading from jessie to stretch since
> the required postgis libraries are missing. This can cause serious data
> loss, because once upgraded to stretch, the postgis data can't be
> accesed nor dumped (Database gives error "could not access file
> "$libdir/postgis-2.1": no such file or directory"). 

Could you append the apt output to this bug? Namely, which packages
got removed? (/var/log/apt/term.log)

> Also upgrading the database to postgresql-9.6 does not work. 

What did you try, and what didn't work?

Christoph

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

[Juergen Fuchsberger]

Package: postgresql-9.4-postgis-2.1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis enabled
database becomes corrupt when upgrading from jessie to stretch since
the required postgis libraries are missing. This can cause serious data
loss, because once upgraded to stretch, the postgis data can't be
accesed nor dumped (Database gives error "could not access file
"$libdir/postgis-2.1": no such file or directory"). 
Also upgrading the database to postgresql-9.6 does not work. 

-- System Information:
Debian Release: 8.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

Bug#886506: Kernel panic for 4.14.0-3-686-pae

[Steven Shiau]

I have a similar issue with the same Linux kernel 4.14.0-3-686-pae. It's
reproducible in virtualbox 5.2, VMWare WS 14, or the physical machine
Lenovo T420s.
Attached please find the screenshot about the kernel panic.
While there is _NO_ such issue when using Linux kernel 4.14.0-3-amd64.
Thanks.

Steven

-- 
Steven Shiau 
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5  356C 8E94 C9CD 163E 3FB0

Processed: Re: Bug#886734: libgdk-pixbuf2.0-0: undefined symbol after upgrade (wheezy-security): gdk_pixbuf_calculate_rowstride

[Debian Bug Tracking System]

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

> reassign 886734 gdk-pixbuf
Bug #886734 [libgdk-pixbuf2.0-0] libgdk-pixbuf2.0-0: undefined symbol after 
upgrade (wheezy-security): gdk_pixbuf_calculate_rowstride
Bug reassigned from package 'libgdk-pixbuf2.0-0' to 'gdk-pixbuf'.
No longer marked as found in versions 2.26.1-1+deb7u7.
Ignoring request to alter fixed versions of bug #886734 to the same values 
previously set
> forcemerge 886721 886734
Bug #886721 [gdk-pixbuf] libgdk-pixbuf2.0-0: undefined symbol after upgrade : 
g_uint64_checked_mul
Bug #886734 [gdk-pixbuf] libgdk-pixbuf2.0-0: undefined symbol after upgrade 
(wheezy-security): gdk_pixbuf_calculate_rowstride
Severity set to 'serious' from 'important'
There is no source info for the package 'gdk-pixbuf' at version 
'2.26.1-1+deb7u7' with architecture ''
Unable to make a source version for version '2.26.1-1+deb7u7'
Marked as found in versions 2.26.1-1+deb7u7.
Merged 886721 886734
> thanks
Stopping processing here.

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

Bug#886721: Bug#886734: libgdk-pixbuf2.0-0: undefined symbol after upgrade (wheezy-security): gdk_pixbuf_calculate_rowstride

[Chris Lamb]

forcemerge 886721 886734
thanks

Hi root (ahem!),

> Maybe related to bug report #886721?

Indeed; merging... :)


Regards,

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

Processed (with 1 error): Re: Bug#886734: libgdk-pixbuf2.0-0: undefined symbol after upgrade (wheezy-security): gdk_pixbuf_calculate_rowstride

[Debian Bug Tracking System]

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

> forcemerge 886721 886734
Bug #886721 [gdk-pixbuf] libgdk-pixbuf2.0-0: undefined symbol after upgrade : 
g_uint64_checked_mul
Unable to merge bugs because:
package of #886734 is 'libgdk-pixbuf2.0-0' not 'gdk-pixbuf'
Failed to forcibly merge 886721: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#886721: [SECURITY] [DLA 1234-1] gdk-pixbuf security update

[Chris Lamb]

Hi Emilio,

> If you don't have the time now I can take a look at this later today.

Please, although it's more that my IEEE 754 is pretty rusty… :)


Best wishes,

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

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

[David Bremner]

Niko Tyni  writes:

> I'm inclined to reassign this bug to perl and close it with the above
> change unless I hear arguments to the contrary.

Unsurprisingly, I don't object ;). Feel free to close the binNMU at the
same time if you remember.

d

Bug#886721: [SECURITY] [DLA 1234-1] gdk-pixbuf security update

[Emilio Pozuelo Monfort]

On 09/01/18 11:50, Chris Lamb wrote:
> [adding 886721 to CC]
> 
> Hi Emilio,
> 
>> g_uint64_checked_mul was introduced in glib 2.48, but wheezy has 2.32
> 
> JFTR that is here:
> 
>   
> https://developer.gnome.org/glib/stable/glib-Bounds-checked-integer-arithmetic.html#g-uint64-checked-mul
> 
>> The patch should be updated to do a manual overflow check.
> 
> Indeed. Does anyone have one handy?

You can do what glib does:

https://git.gnome.org/browse/glib/tree/glib/gtypes.h#n434

If you don't have the time now I can take a look at this later today.

Cheers,
Emilio

Bug#886700: marked as done (python-pyasn1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc-base/python-pyasn1)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 10:50:31 +
with message-id 
and subject line Bug#886700: fixed in pyasn1 0.4.2-3
has caused the Debian Bug report #886700,
regarding python-pyasn1-doc: fails to upgrade from 'stable' to 'sid' - trying 
to overwrite /usr/share/doc-base/python-pyasn1
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.)


-- 
886700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyasn1-doc
Version: 0.4.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Selecting previously unselected package python-pyasn1-doc.
  Preparing to unpack .../python-pyasn1-doc_0.4.2-2_all.deb ...
  Unpacking python-pyasn1-doc (0.4.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pyasn1-doc_0.4.2-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/python-pyasn1', which is also in 
package python-pyasn1 0.1.9-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pyasn1-doc_0.4.2-2_all.deb


cheers,

Andreas


python-pyasn1=0.1.9-2_python-pyasn1-doc=0.4.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pyasn1
Source-Version: 0.4.2-3

We believe that the bug you reported is fixed in the latest version of
pyasn1, 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.
Tristan Seligmann  (supplier of updated pyasn1 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, 09 Jan 2018 12:40:05 +0200
Source: pyasn1
Binary: python-pyasn1 python3-pyasn1 pypy-pyasn1 python-pyasn1-doc
Architecture: source
Version: 0.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Jan Lübbe 
Changed-By: Tristan Seligmann 
Description:
 pypy-pyasn1 - ASN.1 library for Python (PyPy module)
 python-pyasn1 - ASN.1 library for Python (Python 2 module)
 python-pyasn1-doc - ASN.1 library for Python (documentation)
 python3-pyasn1 - ASN.1 library for Python (Python 3 module)
Closes: 886700
Changes:
 pyasn1 (0.4.2-3) unstable; urgency=medium
 .
   * Add Replaces/Breaks for python-pyasn1-doc (closes: #886700).
Checksums-Sha1:
 df96bb509f468d71dc2d224304395e7f0f21f289 2233 pyasn1_0.4.2-3.dsc
 97626d43d90d8dee51ec30759dffab45b9aa3b95 5404 pyasn1_0.4.2-3.debian.tar.xz
 95914340aec88908aaddc4cb8a770cbd6e7a7274 7284 pyasn1_0.4.2-3_source.buildinfo
Checksums-Sha256:
 888517922336ade422fa159960d48a58bc2bc971a9242b3b32f531b7ab7bfd3c 2233 
pyasn1_0.4.2-3.dsc
 c4769523a4353d9aabda5728f456c22882c242ff49aa3457595f0685c5d065a2 5404 
pyasn1_0.4.2-3.debian.tar.xz
 ca98b0165338c8cf875dfc45851503ba47eb5f96eab7a251d4c17fe75bb8193a 7284 
pyasn1_0.4.2-3_source.buildinfo
Files:
 d4566595e7b8cae325b1b99aecd760b6 2233 python optional pyasn1_0.4.2-3.dsc
 4aba089816258bab8f1cc298fcc4a805 5404 python optional 
pyasn1_0.4.2-3.debian.tar.xz
 54bdbd61b53b08c446e4490e52267fad 7284 python optional 
pyasn1_0.4.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGpBAEBCgCTFiEEXAZWhXVRbQoz/6ejwImQ+x9jeJMFAlpUnCZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDVD
MDY1Njg1NzU1MTZEMEEzM0ZGQTdBM0MwODk5MEZCMUY2Mzc4OTMVHG1pdGhyYW5k
aUBkZWJpYW4ub3JnAAoJEMCJkPsfY3iTRO4H/33yU2fJnQYce2RtJq5ssmHnxHJ8
0bryrxKsWG80KBF3y35QXw7/6QN/SlTmfNhQAtjMcLkRFpFtl2cxAipIG+67ta7Z
Ax46jLCQ/QTiWbdGvQqWm/Y0bKhoBfC+MjRfiifI4R2jV8jnDYzkbM86gejlvgz2

Bug#886700: marked as pending

[Tristan Seligmann]

tag 886700 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/pyasn1.git/commit/?id=c8e7f71

---
commit c8e7f717e2d8747289989cedca94b61e56aa33bc
Author: Tristan Seligmann 
Date:   Tue Jan 9 12:40:08 2018 +0200

Add Replaces/Breaks for python-pyasn1-doc (closes: #886700).

diff --git a/debian/changelog b/debian/changelog
index 1f06fe7..7437db1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pyasn1 (0.4.2-3) unstable; urgency=medium
+
+  * Add Replaces/Breaks for python-pyasn1-doc (closes: #886700).
+
+ -- Tristan Seligmann   Tue, 09 Jan 2018 12:40:05 +0200
+
 pyasn1 (0.4.2-2) unstable; urgency=medium
 
   * Upload to unstable.

Processed: Bug#886700 marked as pending

[Debian Bug Tracking System]

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

> tag 886700 pending
Bug #886700 [python-pyasn1-doc] python-pyasn1-doc: fails to upgrade from 
'stable' to 'sid' - trying to overwrite /usr/share/doc-base/python-pyasn1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Andreas Tille]

Hi Flavien,

On Tue, Jan 09, 2018 at 09:15:38AM +0100, Flavien Bridault wrote:
> No my GPG key has not been signed by anyone afaik.

I guess somewhere close to you you can find a Debian developer to sign
your key.
 
> Otherwise Andreas proposed me some weeks to apply as a Debian Developer,
> that might be one more good reason to do it ? :)

The first stage is a Debian Maintainer ... and you need to have a key
signed by a Debian Developer to get this status. ;-)

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#885996: marked as done (gnome-shell-extension-show-ip: load fails: TypeError: calling a builtin typed array constructor without new is forbidden)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 10:19:25 +
with message-id 
and subject line Bug#885996: fixed in gnome-shell-extension-show-ip 8-1
has caused the Debian Bug report #885996,
regarding gnome-shell-extension-show-ip: load fails: TypeError: calling a 
builtin typed array constructor without new is forbidden
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.)


-- 
885996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-show-ip
Version: 4.0.1-1
Severity: serious
Tags: buster sid

This extension is not compatible with gnome-shell 3.26 and
this prevents it from being loaded on Debian buster/sid:

$ grep -A2 shell-version 
/usr/share/gnome-shell/extensions/show...@kyle.aims.ac.za/metadata.json
  "shell-version": [
"3.22"
  ],
$ apt policy gnome-shell
gnome-shell:
  Installed: 3.26.2-2
  Candidate: 3.26.2-2
  Version table:
 *** 3.26.2-2 900
900 https://deb.debian.org/debian testing/main amd64 Packages
800 https://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell-extension-show-ip depends on:
ii  gnome-shell  3.26.2-2

gnome-shell-extension-show-ip recommends no packages.

gnome-shell-extension-show-ip suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-show-ip
Source-Version: 8-1

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-show-ip, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated 
gnome-shell-extension-show-ip 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, 09 Jan 2018 11:11:23 +0200
Source: gnome-shell-extension-show-ip
Binary: gnome-shell-extension-show-ip
Architecture: source all
Version: 8-1
Distribution: unstable
Urgency: medium
Maintainer: Kyle Robbertze 
Changed-By: Kyle Robbertze 
Description:
 gnome-shell-extension-show-ip - Shows the current private or public IP address
Closes: 885996
Changes:
 gnome-shell-extension-show-ip (8-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #885996)
   * debian/control: Move to architecture all
 Fixed VCS links
 Bump Standards-Version
   * debian/watch: Add version number to watch file
   Use new upstream
   * debian/copyright: Use new source link
   Fix file location
   * debian/rules: Use new schemas location for compilation
   Remove compiled schemas on clean
   * debian/install: Use new uuid
Checksums-Sha1:
 ac47c5504774ead6bc886719c8c573e2ec57979a 2089 
gnome-shell-extension-show-ip_8-1.dsc
 d4a50f928fcbb81a32fd7459ab085e012e9c6cd8 354788 
gnome-shell-extension-show-ip_8.orig.tar.gz
 cfd68dc73771513cffde507ecc8799725c2e9d1d 2856 
gnome-shell-extension-show-ip_8-1.debian.tar.xz
 e436821c134cce5716c3c75075e6c9f9a61f27d2 9596 
gnome-shell-extension-show-ip_8-1_all.deb
 eb6b68e427570de7a03e30d6ba0ca5cefce82ac3 5497 
gnome-shell-extension-show-ip_8-1_amd64.buildinfo
Checksums-Sha256:
 9be9ae43a7eaf6b3dbe4c8379e1f3437337a68f24a8c234f41de6a917cb8a168 2089 
gnome-shell-extension-show-ip_8-1.dsc
 

Bug#871566: swarmkit FTBFS: cannot find package "github.com/docker/docker/api/types"

[Edmund Grimley Evans]

The build failure quoted above is not reproducible with the current
state of sid, I think. However, it is still not possible to build
swarmkit for a different reason: an indirect dependency on
golang-github-juju-ansiterm. See #886613 and the "Dependency
installability problem for swarmkit" on arm64 and other architectures:
https://buildd.debian.org/status/package.php?p=swarmkit=sid

Bug#886698: marked as done (sollya-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/sollya/AUTHORS)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jan 2018 09:04:18 +
with message-id 
and subject line Bug#886698: fixed in sollya 6.0+ds-6
has caused the Debian Bug report #886698,
regarding sollya-doc: fails to upgrade from 'stretch' - trying to overwrite 
/usr/share/doc/sollya/AUTHORS
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.)


-- 
886698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sollya-doc
Version: 6.0+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' 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 sollya-doc.
  Preparing to unpack .../sollya-doc_6.0+ds-4_all.deb ...
  Unpacking sollya-doc (6.0+ds-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/sollya-doc_6.0+ds-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/sollya/AUTHORS', which is also in 
package sollya 6.0+ds-1
  Errors were encountered while processing:
   /var/cache/apt/archives/sollya-doc_6.0+ds-4_all.deb


cheers,

Andreas


sollya=6.0+ds-1_sollya-doc=6.0+ds-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sollya
Source-Version: 6.0+ds-6

We believe that the bug you reported is fixed in the latest version of
sollya, 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.
Jerome Benoit  (supplier of updated sollya 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, 09 Jan 2018 08:36:36 +
Source: sollya
Binary: sollya libsollya6 libsollya-dev sollya-doc
Architecture: source
Version: 6.0+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 libsollya-dev - library for safe floating-point code development -- libdev
 libsollya6 - library for safe floating-point code development -- lib
 sollya - library for safe floating-point code development -- tool
 sollya-doc - library for safe floating-point code development -- doc
Closes: 886698
Changes:
 sollya (6.0+ds-6) unstable; urgency=medium
 .
   * Debianization:
 - debian/control:
   - Breaks field, sollya-doc, add (Closes: #886698);
 - debian/patch/*:
   - d/p/upstream-reproducibility-doc-date.patch, introduce.
Checksums-Sha1:
 15005cd9838c37fa84bdb47a3159a5696b1c1d8a 3044 sollya_6.0+ds-6.dsc
 5ec5901d221a1fee349a64f26e3ea7da8d1561f2 16868 sollya_6.0+ds-6.debian.tar.xz
 1ddc3a1de6fa123e41e8cd31493bbe830bf391b3 6589 sollya_6.0+ds-6_source.buildinfo
Checksums-Sha256:
 0af9405c81e264f27daed9df18f2082bec4fb7eb0f2bf650c85bba4b14f25d8f 3044 
sollya_6.0+ds-6.dsc
 9bb10b7e49e8a8982181d3225815918a5dfb076e87051b1a08ddd2317fbec3ee 16868 
sollya_6.0+ds-6.debian.tar.xz
 cfe197d189a1e26cc2807c60770110ca812dba03ec1e1e89d351b380d881afa2 6589 
sollya_6.0+ds-6_source.buildinfo
Files:
 5eccec750c4eaedc3fd85651e8cdd025 3044 math optional sollya_6.0+ds-6.dsc
 d538a1a64e1e373fc8a6055443f605f3 16868 math optional 
sollya_6.0+ds-6.debian.tar.xz
 b30502d166e49afa610316df2b1a7888 6589 math optional 
sollya_6.0+ds-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAlpUghAVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLf4sf/inqI9Fgtm+MDVkP01Q2Mj3kEtcj
7yCADBlKNIKDe0M9dHHnDvfc2ogxar18uvz+y65rZA0W/FglgJaXfttnQajLbAX5
oAPwGGFyJUexpXd/PMiW6NtssMkp2hfAMzDJLRqLrPbpQaSIdRE1ZD3uG8Sr8fj2
eENFxR1/O30jakxe9GF4nUV1xD6XdQK6nvI6TD/56cbmwoENJHaI+5kgt3cSPzHa
16BH5dNIJ/LKHoInN1cGWRYRhUW854LCFmnkwvAvmG4KWC48klL4YrsdoFyKxTXD

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

[Patrik Lori]

Hi Felix

Ok, I now understand your points. You have right, with the Firefox case; and 
this is GOOD NEWS for the SECURITY.
AND if you argue with the one direction of microcode updates YOU have also 
right. ;)

But who (which tech.) can/will stop a clever hacker doing forward updates on 
the microcode with his own/bad changes? 
If it is cryptographic (as described) it’s better than nothing, but an 
additional local button/process would secure it in advance.

We will see today HOW now Microsoft & RedHat will PATCH/CHANGE the microcode 
with there Update capabilities!
It’s better they be able to do it, than just an other app from any uncertainty 
sources.

You help me a lot, to feel more secure now. THANKS!

Kind regards
Patrik
 


ifs³ Consulting+Engineering
Patrik Lori
CTO, cert. Computer Engineer & MAS-BA
Panoramastr. 6, 5625 Kallern, Switzerland
 
Web:http://www.ifs3.com 
Email:  patrik.l...@ifs3.com 
Mobile:+41 79 326 75 97
 
CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is 
intended only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Any unauthorised review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message. If you are the intended recipient but do not wish to 
receive communications through this medium, please do advise the sender 
immediately.

> Am 09.01.2018 um 02:25 schrieb Felix Winterhalter :
> 
>> I’m very very sorry, that you think I’m NOT understanding „Spectre" and
>> what this shows. - I understand this very well! ;)
>> 
>> *FOR YOU:*
>> *==
>> *
>> PLEASE look at the possibilities of the new *version 57.0.4 of Firefox*.
>> *With this special created release (of this browser) you can PATCH the
>> Microcode* *AGAINST Spectre
> Let me stop you right there. This is simply not true at all. If you
> would have read up on what exactly they changed in 57.0.4 of Firefox to
> mitigate the Meltdown and Spectre attacks you might have seen that they
> simply changed the resolution of the timing source you can get via the
> javascript function performance.now() to be 20 µs.
> 
> Since both Meltdown and Spectre rely on having accurate high resolution
> timing information available to the process running the attack, this
> effectively leads to those attacks no longer working from within Firefox.
> 
> This has absolutely NOTHING whatsoever to do with microcode patching,
> and so is absolutely irrelevant.
> 
>> But in this case (Spectre) just a "bad website" can be used to reed data 
>> from other areas. This is possible because of some side-effect the current 
>> Microcode has. If we can FIX that with the special version (57.0.4) of 
>> Firefox, a hacker can change it back again with an other program and no one 
>> knows! - After this he just need a "bad website" to get datas AGAIN.
> 
> This also fundamentally shows that you have not understood how microcode
> updates work. You can't just "change it back" as microcode updates only
> work in one direction, that is "the update applied needs to be newer
> than the one already applied", the update revision is included in the
> cryptographic signature of the microcode update. So you cannot just
> apply old updates on top of new ones.

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

No my GPG key has not been signed by anyone afaik.

Otherwise Andreas proposed me some weeks to apply as a Debian Developer,
that might be one more good reason to do it ? :)

Le 08/01/2018 à 18:16, John Paul Adrian Glaubitz a écrit :
> On 01/08/2018 06:13 PM, Flavien Bridault wrote:
> > Ah I see maybe I should email Ben Collins 
>  as stated here
> > https://www.debian.org/ports/sparc/porting.en.html ?
>
> No, that information is unfortunately outdated. We need to ask the webteam
> to update the website. Thanks for the heads-up.
>
> Do you happen to have a GPG key which has been signed by any Debian
> Developer
> or any developer from another large Linux distribution?
>
> Adrian
>

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 





signature.asc
Description: OpenPGP digital signature