Processed: notfound 857301 in 1.0.4+nmu2

[Debian Bug Tracking System]

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

> notfound 857301 1.0.4+nmu2
Bug #857301 [iptables-persistent] Subject: iptables-persistent: 
netfilter-persistent save fails if run from cron because full paths are not 
given in scripts.
Bug #857304 [iptables-persistent] Subject: iptables-persistent: 
netfilter-persistent save fails if run from cron because full paths are not 
given in scripts.
Ignoring request to alter found versions of bug #857301 to the same values 
previously set
Ignoring request to alter found versions of bug #857304 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#857897: marked as done (qtads FTBFS on 32bit: error: exception cleanup for this placement new selects non-placement operator delete)

[Debian Bug Tracking System]

Your message dated Fri, 24 Mar 2017 03:08:42 +
with message-id 
and subject line Bug#857897: fixed in qtads 2.1.6-1.1
has caused the Debian Bug report #857897,
regarding qtads FTBFS on 32bit: error: exception cleanup for this placement new 
selects non-placement operator delete
to be marked as done.

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

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


-- 
857897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtads
Version: 2.1.6-1
Severity: serious

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

...
In file included from tads3/tcprs.cpp:39:0:
tads3/vmbignum.h: In static member function 'static vm_obj_id_t 
CVmObjBigNum::create(int, const bignum_t*)':
tads3/vmbignum.h:585:45: error: exception cleanup for this placement new 
selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum(vmg_ prec);
...
Makefile:3344: recipe for target 'obj/tcprs.o' failed
make[1]: *** [obj/tcprs.o] Error 1
--- End Message ---
--- Begin Message ---
Source: qtads
Source-Version: 2.1.6-1.1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Mar 2017 02:41:27 +0100
Source: qtads
Binary: qtads
Architecture: source
Version: 2.1.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Schepler 
Changed-By: Andreas Beckmann 
Description:
 qtads  - Qt HTML interpreter for TADS
Closes: 857897
Changes:
 qtads (2.1.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build with -std=c++11. qtads is not ready for C++14.  (Closes: #857897)
Checksums-Sha1:
 b57225fb93e6ec601990828c2cb64601f8a74072 1734 qtads_2.1.6-1.1.dsc
 4c486131ddf696b74fdca3c6dcedd32e7b4468d9 4132 qtads_2.1.6-1.1.debian.tar.xz
 d5a5510bf1aefbed3eea2fb6e94d15a6efbb20e2 9471 qtads_2.1.6-1.1_source.buildinfo
Checksums-Sha256:
 b709ecc528e13ac430938197b26f95bf17ddb27a16e791f2388a3007f0fbd26d 1734 
qtads_2.1.6-1.1.dsc
 7ab7448c1e932634a271dac79100318ddfcc02279a0d00fdec2597923b2e8297 4132 
qtads_2.1.6-1.1.debian.tar.xz
 cccbc883170869f88db75e36de89d69709ff7258f77d98d1a426166776bcb867 9471 
qtads_2.1.6-1.1_source.buildinfo
Files:
 df9e665fa664a07668fbf6a10bdcfdb2 1734 games optional qtads_2.1.6-1.1.dsc
 66cca5804770578c65ec18136aa18201 4132 games optional 
qtads_2.1.6-1.1.debian.tar.xz
 4c4cc7af9f4978c337981afedc918b36 9471 games optional 
qtads_2.1.6-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYzeMjAAoJEF+zP5NZ6e0IhhsP/3mugqQ6N5BiQxvTfb0wJRt0
XhmOljZnkkKmoaXkREXdfVQ6h+v8lJg5p+TGFkcAKIz8DnIupthWamd3gqG5g7mN
rCbg75f6a3vwtEhwF6DMrRxOcfc0wEQSCTu0QnXKmJdryeB0LxmGZ3yB7BOgAapa
E8jww3CaWZwH0JwpRs8fvmkMegxQ+ZVUpWP1Sau8qGQL75wOsZLntWs0efF5+nJ9
LZjlgvgQbygYawa6eRXesfRVpUUnDcRqUOQPnaphFSiRaFfBWTRHab9qdBNAZ/ak
+rS+CiE06nYJR+L4s9D5pnlkRW/6XklNWqlcsj0d57b5JMNZYnkn4kxCEelyujmv
45nw7N6UnOHKe7kyKDqCWiVpU7V01HOFWLbVCPlt4yRHYwaOwHLz7xPFy9RX4oUV
lMhIDWGRYrZSB4FpICTdy9ZNnl0hHmWa4yP/eLSihGsRxft93ENLXwZRhjrkKtgB
Bjz/kVGSzOjtslQGfauX6fXt0d7abk1uBvD/z6lj/BcJ4n9iaGew/owURAqOg6ws
/DsbeiqW+FLdxUS5DvkeLXk+dOl0QKWAV82aKKUo7XeoIZBsYg1SIMXZChSZoZ6v
jlafeWhRQK1jo0ILJ+i9g5d3HzTKbIajsNKJT3UDGMG/kv6O62Ccgtvm+q3K4cW9
XK5ggCEiDQ13zgWKwnfp
=sWk4
-END PGP SIGNATURE End Message ---

Bug#858556: Bug #858556 as you reported on #801564

[Andreas Beckmann]

On 2017-03-24 01:19, Santiago Garcia Mantinan wrote:
> Hi!
> 
> Just to be able to replicate your setup, as our initial tests didn't catch
> this one:
> 
> what packages did you have on jessie (I'm assuming squid3 + squid3-common
> from jessie, or did you have any other installed?

installed packages and versions are available in the logfile I posted

> The package did have the default config files or where they modified in some
> way?

piuparts does installation tests with DEBIAN_FRONTEND=noninteractive, it
does not touch configuration files (but the maintainer scripts could do
nasty stuff)

> Did you have any config stuff left from previous squid 2.7 from wheezy
> around?

not in this test ... but I'll file more bugs if I find some problems
upgrading step by step from older releases :-)

> Any other info you consider special on your setup?

I don't think so ...

If you need more information I could enter the chroot after piuparts
noticed the failure and collect anythign you need.


Andreas
(currently travelling)

Bug#812002: marked as done (smokeqt: FTBFS with GCC 6: deleted function)

[Debian Bug Tracking System]

Your message dated Fri, 24 Mar 2017 01:49:00 +
with message-id 
and subject line Bug#812002: fixed in smokeqt 4:4.14.3-1.1
has caused the Debian Bug report #812002,
regarding smokeqt: FTBFS with GCC 6: deleted function
to be marked as done.

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

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


-- 
812002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smokeqt
Version: 4:4.14.3-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> cd /<>/obj-x86_64-linux-gnu/qtscript && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/smokeqtscript.dir/link.txt --verbose=1
> /usr/bin/c++  -fPIC -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  
> -Wno-deprecated-declarations  -Wl,-z,relro -shared 
> -Wl,-soname,libsmokeqtscript.so.3 -o libsmokeqtscript.so.3.0.0 
> CMakeFiles/smokeqtscript.dir/smokedata.cpp.o 
> CMakeFiles/smokeqtscript.dir/x_1.cpp.o ../qtcore/libsmokeqtcore.so.3.0.0 
> -lQtCore -lQtScript -lsmokebase 
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu/qtcore: 
> cd /<>/obj-x86_64-linux-gnu/qtscript && /usr/bin/cmake -E 
> cmake_symlink_library libsmokeqtscript.so.3.0.0 libsmokeqtscript.so.3 
> libsmokeqtscript.so
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 30%] Built target smokeqtscript
> /<>/obj-x86_64-linux-gnu/qtdbus/x_1.cpp:1594:7: error: deleted 
> function 'virtual 
> __smokeqtdbus::x_QDBusConnectionInterface::~x_QDBusConnectionInterface()'
>  class x_QDBusConnectionInterface : public QDBusConnectionInterface {
>^~
> 
> In file included from /usr/include/qt4/QtDBus/QtDBus:8:0,
>  from /<>/qtdbus/qtdbus_includes.h:2,
>  from /<>/obj-x86_64-linux-gnu/qtdbus/x_1.cpp:2:
> /usr/include/qt4/QtDBus/qdbusconnectioninterface.h:73:5: error: overriding 
> non-deleted function 'virtual 
> QDBusConnectionInterface::~QDBusConnectionInterface()'
>  ~QDBusConnectionInterface();
>  ^
> 
> /<>/obj-x86_64-linux-gnu/qtdbus/x_1.cpp:1594:7: note: 'virtual 
> __smokeqtdbus::x_QDBusConnectionInterface::~x_QDBusConnectionInterface()' is 
> implicitly deleted because the default definition would be ill-formed:
>  class x_QDBusConnectionInterface : public QDBusConnectionInterface {
>^~
> 
> /<>/obj-x86_64-linux-gnu/qtdbus/x_1.cpp:1594:7: error: 'virtual 
> QDBusConnectionInterface::~QDBusConnectionInterface()' is private within this 
> context
> In file included from /usr/include/qt4/QtDBus/QtDBus:8:0,
>  from /<>/qtdbus/qtdbus_includes.h:2,
>  from /<>/obj-x86_64-linux-gnu/qtdbus/x_1.cpp:2:
> /usr/include/qt4/QtDBus/qdbusconnectioninterface.h:73:5: note: declared 
> private here
>  ~QDBusConnectionInterface();
>  ^
> 
> qtdbus/CMakeFiles/smokeqtdbus.dir/build.make:98: recipe for target 
> 'qtdbus/CMakeFiles/smokeqtdbus.dir/x_1.cpp.o' failed
> make[3]: *** [qtdbus/CMakeFiles/smokeqtdbus.dir/x_1.cpp.o] Error 1

...

>  from /<>/obj-x86_64-linux-gnu/qtgui/x_13.cpp:2:
> /usr/include/qt4/QtGui/qsessionmanager.h:65:5: error: overriding non-deleted 
> function 'virtual QSessionManager::~QSessionManager()'
>  ~QSessionManager();
>  ^
> 
> /<>/obj-x86_64-linux-gnu/qtgui/x_13.cpp:3572:7: note: 'virtual 
> __smokeqtgui::x_QSessionManager::~x_QSessionManager()' is implicitly deleted 
> because the default definition would be ill-formed:
>  class x_QSessionManager : public QSessionManager {
>^
> 
> /<>/obj-x86_64-linux-gnu/qtgui/x_13.cpp:3572:7: error: 'virtual 
> QSessionManager::~QSessionManager()' is private within this context
> In file included from /usr/include/qt4/QtGui/QtGui:213:0,
>  from /<>/qtgui/qtgui_includes.h:2,
>  from /<>/obj-x86_64-linux-gnu/qtgui/x_13.cpp:2:
> /usr/include/qt4/QtGui/qsessionmanager.h:65:5: note: declared private here
>  ~QSessionManager();

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- 

Processed: Re: Bug#858567: mssh: local files installed to /usr/@DATADIRNAME@/locale

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #858567 [mssh] mssh: local files installed to /usr/@DATADIRNAME@/locale
Added tag(s) patch.

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

Bug#858567: mssh: local files installed to /usr/@DATADIRNAME@/locale

[Axel Beckert]

Control: tag -1 + patch

Hi Jorge and Hector,

Jorge Moraleda wrote:
> mssh incorrectly installs local files to /usr/@DATADIRNAME@/locale

Jorge: Thanks for spotting and reporting this issue!

Hector: Attached a patch to fix this.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
Description: Reimplement no more supported @DATADIRNAME@ substitution
 Based on Andriy Grytsenko's fix for the same issue in gnome-system-tools.
Author: Axel Beckert 
Bug-Debian: https://bugs.debian.org/858567

--- a/configure.ac
+++ b/configure.ac
@@ -26,6 +26,9 @@
   AC_MSG_ERROR([gconftool-2 executable not found in your path - should be installed with GConf])
 fi
 
+test -n "$DATADIRNAME" || DATADIRNAME=share
+AC_SUBST(DATADIRNAME)
+
 AM_GCONF_SOURCE_2
 
 AC_OUTPUT( po/Makefile.in


signature.asc
Description: Digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> tag 858241 +pending
Bug #858241 [src:etcd] Dependency on  golang-github-coreos-pkg not strict enough
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#857842: [pkg-go] Bug#857842: Fails to build -- test errors

[Potter, Tim]

On 16 Mar 2017, at 2:07 AM, Sjoerd Simons  wrote:
> 
> Source: etcd
> Version: 3.1.2+dfsg
> Severity: serious
> Justification: fails to build from source
> 
> Hey,
> 
> When trying to build etcd i get:

[...]

> debian/rules:9: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 1
> make[1]: Leaving directory '/build/etcd-3.1.2+dfsg'
> debian/rules:6: recipe for target 'binary' failed
> make: *** [binary] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2


Hi Sjoerd.  Is there any more output available here?  Running "go test" should 
display
a lot more info which would help narrow things down.

One question - are you building inside a container?  There's something to do 
with the
length of socket files under Docker that causes it to fail for me when building 
inside
Docker so I need to run pbuilder on bare metal.


Tim.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#858540: [Python-modules-team] Bug#858540: barbican: FTBFS: ImportError: No module named vine.five

[Brian May]

On 2017-03-24 08:36, Chris Lamb wrote:

> Oh, did I mark it as such? Apologies if so :)

No, the bug was absolutely correct - the error was my brain :-). 
  

Bug#858556: Bug #858556 as you reported on #801564

[Santiago Garcia Mantinan]

Hi!

Just to be able to replicate your setup, as our initial tests didn't catch
this one:

what packages did you have on jessie (I'm assuming squid3 + squid3-common
from jessie, or did you have any other installed?

The package did have the default config files or where they modified in some
way?

Did you have any config stuff left from previous squid 2.7 from wheezy
around?

Any other info you consider special on your setup?

Regards...
-- 
Manty/BestiaTester -> http://manty.net

Bug#857795: Bug#858567: Bug#857795: /usr/@DATADIRNAME@/ only showed up with the recent -fPIE rebuilds: Maybe a debhelper or build system bug?

[Axel Beckert]

Hi Andriy,

Andriy Grytsenko wrote:
> >the two bug https://bugs.debian.org/858567 (just fixed in a very
> >recent upload) and https://bugs.debian.org/857795 are not present in
> >the initial upload of the according package version, only in the
> >recent BinNMUs. So I wonder if these issues might stem from a recent
> >build toolchain, e.g. debhelper or autotools issue:
> 
> Since the issue is a result of some gettext/intltool variable deprecation
> (probably over a decade ago), I suppose that some never autotools script
> (autopoint probably) just dropped it, so problem appeared.

Thanks for the insight and hints! And for the prompt fix of
gnome-system-tools!

autopoint is indeed an indirect build dependency of both, mssh and
gnome-system-tools. But then again, the last upload of a new upstream
version of gettext (autopoint's source package) was back in June 2016,
so that doesn't seem to fit:

https://packages.qa.debian.org/g/gettext.html
https://packages.qa.debian.org/g/gettext/news/20160612T234857Z.html

autoconf hasn't had a new upstream release for about 5 years (at least
not uploaded to Debian), and automake hasn't seen much changes since
2015 either. Strange.

At least autotools-dev has been synced with upstream git in
mid-November. Nothing about DATADIRNAME in
/usr/share/doc/autotools-dev/changelog.gz though.

But if that variable is deprecated for so long already, it's probably
indeed better to fix the affected packages instead of looking into the
build toolchain as it's an intended change in the toolchain.

(I'm though still curious which change actually triggered these
issues. :-)

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

Bug#854739: patch for CVE-2017-5591

[W. Martin Borgert]

Identical fix is now also in new upstream release 1.3.2.

Bug#857795: /usr/@DATADIRNAME@/ only showed up with the recent -fPIE rebuilds: Maybe a debhelper or build system bug?

[Andriy Grytsenko]

Hello!

>the two bug https://bugs.debian.org/858567 (just fixed in a very
>recent upload) and https://bugs.debian.org/857795 are not present in
>the initial upload of the according package version, only in the
>recent BinNMUs. So I wonder if these issues might stem from a recent
>build toolchain, e.g. debhelper or autotools issue:

Since the issue is a result of some gettext/intltool variable deprecation
(probably over a decade ago), I suppose that some never autotools script
(autopoint probably) just dropped it, so problem appeared.

Bug#857795: /usr/@DATADIRNAME@/ only showed up with the recent -fPIE rebuilds: Maybe a debhelper or build system bug?

[Axel Beckert]

Hi,

the two bug https://bugs.debian.org/858567 (just fixed in a very
recent upload) and https://bugs.debian.org/857795 are not present in
the initial upload of the according package version, only in the
recent BinNMUs. So I wonder if these issues might stem from a recent
build toolchain, e.g. debhelper or autotools issue:

→ debdiff mssh_2.2-1.1_amd64.deb mssh_2.2-1.1+b1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/@DATADIRNAME@/locale/es/LC_MESSAGES/mssh.mo
-rw-r--r--  root/root   /usr/share/doc/mssh/changelog.Debian.amd64.gz

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/share/locale/es/LC_MESSAGES/mssh.mo

Control files: lines which differ (wdiff format)

Installed-Size: [-90-] {+92+}
{+Source: mssh (2.2-1.1)+}
Version: [-2.2-1.1-] {+2.2-1.1+b1+}
→ debdiff gnome-system-tools_3.0.0-5_amd64.deb 
gnome-system-tools_3.0.0-5+b1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/af/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/am/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/ar/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/as/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/ast/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/az/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/be/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/be@latin/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/bg/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/bn/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/bn_IN/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/br/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/ca/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/ca@valencia/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/cs/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/cy/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/da/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/de/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/dz/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/el/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/en@shaw/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/en_CA/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/en_GB/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/eo/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/es/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/et/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/eu/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/fa/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/fi/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/fr/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/ga/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/gl/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/gu/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/he/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/hi/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/hr/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/hu/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/id/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/is/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/it/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   
/usr/@DATADIRNAME@/locale/ja/LC_MESSAGES/gnome-system-tools.mo
-rw-r--r--  root/root   

Processed: Re: patch for CVE-2017-5591

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #854739 [src:sleekxmpp] CVE-2017-5591
Added tag(s) patch.

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

Bug#857795: marked as done ([gnome-system-tools] local files installed to /usr/@DATADIRNAME@/locale)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 22:49:55 +
with message-id 
and subject line Bug#857795: fixed in gnome-system-tools 3.0.0-6
has caused the Debian Bug report #857795,
regarding [gnome-system-tools] local files installed to 
/usr/@DATADIRNAME@/locale
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.)


-- 
857795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-system-tools
Version: 3.0.0-5+b1
Severity: normal

gnome-system-tools install local files to /usr/@DATADIRNAME@/locale

$ dpkg -L gnome-system-tools
/.
/etc
/etc/gnome-system-tools
/etc/gnome-system-tools/user-profiles.conf
/usr
/usr/@DATADIRNAME@
/usr/@DATADIRNAME@/locale
/usr/@DATADIRNAME@/locale/af
/usr/@DATADIRNAME@/locale/af/LC_MESSAGES
/usr/@DATADIRNAME@/locale/af/LC_MESSAGES/gnome-system-tools.mo
/usr/@DATADIRNAME@/locale/am
/usr/@DATADIRNAME@/locale/am/LC_MESSAGES
/usr/@DATADIRNAME@/locale/am/LC_MESSAGES/gnome-system-tools.mo
/usr/@DATADIRNAME@/locale/ar
/usr/@DATADIRNAME@/locale/ar/LC_MESSAGES
/usr/@DATADIRNAME@/locale/ar/LC_MESSAGES/gnome-system-tools.mo
/usr/@DATADIRNAME@/locale/as
/usr/@DATADIRNAME@/locale/as/LC_MESSAGES
/usr/@DATADIRNAME@/locale/as/LC_MESSAGES/gnome-system-tools.mo




-- 
Thanks and Regards,
--
Liang Guo


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnome-system-tools
Source-Version: 3.0.0-6

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

Debian distribution maintenance software
pp.
Andriy Grytsenko  (supplier of updated gnome-system-tools 
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, 24 Mar 2017 00:16:27 +0200
Source: gnome-system-tools
Binary: gnome-system-tools
Architecture: source amd64
Version: 3.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Andriy Grytsenko 
Changed-By: Andriy Grytsenko 
Description:
 gnome-system-tools - Cross-platform configuration utilities for GNOME
Closes: 857795
Changes:
 gnome-system-tools (3.0.0-6) unstable; urgency=medium
 .
   * Adding 00_fix-missing-DATADIRNAME.patch (Closes: #857795).
Checksums-Sha1:
 f2ebe65e841b34cce89d06876d066d9905c06a48 2116 gnome-system-tools_3.0.0-6.dsc
 20c69724b428b61db28362040473762f347c2063 27868 
gnome-system-tools_3.0.0-6.debian.tar.xz
 51cf56175f493b24b1cf670ad6814ea7c441127a 680988 
gnome-system-tools-dbgsym_3.0.0-6_amd64.deb
 b263fcb6c16523862c5e426ee0fd44cb361a050b 13804 
gnome-system-tools_3.0.0-6_amd64.buildinfo
 c1aa473da8d89d197c51e11880a5c85569206d3e 4185510 
gnome-system-tools_3.0.0-6_amd64.deb
Checksums-Sha256:
 a2b9ea66689c9ec47ac49375121b3f5bfedceb8c1809737180b4cce0035e4c6f 2116 
gnome-system-tools_3.0.0-6.dsc
 20379f1ede507245384ca78c7315c91b54d1a73978f8b52fc28fe31304fec0d9 27868 
gnome-system-tools_3.0.0-6.debian.tar.xz
 587d13104ab01b410ba01a5de069affba3cc7b83dc9895a4de28d7dfa5858655 680988 
gnome-system-tools-dbgsym_3.0.0-6_amd64.deb
 eb0ddb676e44ecb752f9aa06d65dfb1c0dc7d37076865222387856b8a1d263f0 13804 
gnome-system-tools_3.0.0-6_amd64.buildinfo
 35d8132bf8c8ffe01fc8cc1ff10a5dcb64facd2a8bfccf59af92cf603fcede69 4185510 
gnome-system-tools_3.0.0-6_amd64.deb
Files:
 d159224c921166eb43deb82c39af6474 2116 gnome optional 
gnome-system-tools_3.0.0-6.dsc
 3a2856c586dd4df1f5f49f1963bc1e47 27868 gnome optional 
gnome-system-tools_3.0.0-6.debian.tar.xz
 e00176c0611be6382cd9859f605d942c 680988 debug extra 
gnome-system-tools-dbgsym_3.0.0-6_amd64.deb
 02cb132aa9c17f2af4b50eb29a4cfddb 13804 gnome optional 
gnome-system-tools_3.0.0-6_amd64.buildinfo
 21d6ba26cbbc837475e4b7c8c1753321 4185510 gnome optional 
gnome-system-tools_3.0.0-6_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCgAGBQJY1EtmAAoJEAV2MC/hidTSgFYP/0ET/3JWlMmS0SnVV+povZtL
2QQQhIfCsRUnMLCN3CcbkHTxSYClKkbh6+opIN6rcHB2z4Elkxj4xcshrLlz20E3
maQEsXsJiV1CenTJV67wldUQEBKGjK4FmLf1eefkOZEbkt8G3XCxGM9IdyhXi0qk

Bug#854739: patch for CVE-2017-5591

[W. Martin Borgert]

Control: tag -1 + patch

The patch seems to be OK for sleekxmpp, too.

Bug#857385: jablicator: should it be removed from the archive?

[Mattia Rizzolo]

On Thu, Mar 23, 2017 at 12:10:24PM -0700, Jeff Breidenbach wrote:
> If you know who to ask and are willing, I appreciate it.
> 
> Otherwise, I'll figure it out eventually.

It's only about opening a bug against ftp.debian.org with the
appropriate subject, in this case I'd say
RM: jablicator -- ROM; RC-buggy; unused; low popcon
and an appropriate text describing in few words why the package should
be removed.
See
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#removing-pkgs

Also reportbug has a template for this, IIRC.


Anyhow, I can do if you prefer so.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#858497: marked as done (mocha: missing Depends: libjs-mocha)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 21:49:13 +
with message-id 
and subject line Bug#858497: fixed in node-mocha 1.20.1-3
has caused the Debian Bug report #858497,
regarding mocha: missing Depends: libjs-mocha
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.)


-- 
858497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mocha
Version: 1.20.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

1m6.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/nodejs/mocha/mocha.css -> ../../../share/javascript/mocha/mocha.css
  /usr/lib/nodejs/mocha/mocha.js -> ../../../share/javascript/mocha/mocha.js

I assume this breaks the package functionality ...


cheers,

Andreas


mocha_1.20.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-mocha
Source-Version: 1.20.1-3

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated node-mocha package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Mar 2017 22:01:16 +0100
Source: node-mocha
Binary: mocha libjs-mocha
Architecture: source
Version: 1.20.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paul Gevers 
Description:
 libjs-mocha - simple, flexible, fun test framework - JavaScript library
 mocha  - simple, flexible, fun test framework - Node.js module
Closes: 858497
Changes:
 node-mocha (1.20.1-3) unstable; urgency=medium
 .
   * Team upload
   * Add dependency in mocha on libjs-mocha (Closes: #858497)
Checksums-Sha1:
 48704c7dd8627e95f02eb5e62e870f801c43be87 1810 node-mocha_1.20.1-3.dsc
 25e659f96892efd6b5883a820ce2817cd0a8b919 4976 node-mocha_1.20.1-3.debian.tar.xz
Checksums-Sha256:
 c5bb07a973958e67c2f1158e4e8ab428b763544d4f1877830f42da638079f271 1810 
node-mocha_1.20.1-3.dsc
 52701a92bb93a0f36ab3ecc100939e5c8414dc087f0344218fb04aaf4cc2becf 4976 
node-mocha_1.20.1-3.debian.tar.xz
Files:
 5d2993215bdd9205ef72385b7fa88b2d 1810 web extra node-mocha_1.20.1-3.dsc
 09649ebfe66dbbda486b0e9207fbcc27 4976 web extra 
node-mocha_1.20.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAljUPcoACgkQnFyZ6wW9
dQrXFgf8DQW2uGVV0DO/13g8Uzn3wkW3Rcj60WrH1iYx823vsarDWAyub7YJ72F2
nTCvCm64Ccp/LbHhdUGV3nt9VN24290P6mBJjyf+bRyUaH2ksRJg6G1g01nY2Xm7
8K/SXZy8tshEiGYvSUPv0og0pFEBd8JvPYEb0s5104mmDWsGtEC6be7+HR6h07we
BnYRgkIiQYqUQanyja3v1MWXouh6m7dGPFgE2gm8RuTQ3u1fg4GW2NAS+U7OVITO
HnklU2f7Di5Ebj8XXSb3Xk2agA/Natm6KmJDefaySoU1DMNCZEjrs05eVfeQnYIL
71OgInELrHs4aIVwaxrCjJOGMWuOvg==
=RIXJ
-END PGP SIGNATURE End Message ---

Bug#854739: patch for CVE-2017-5591

[W. Martin Borgert]

slixmpp has a simple patch:

slixmpp/plugins/xep_0280/carbons.py
@@ -61,10 +61,12 @@ def session_bind(self, jid):
 self.xmpp.plugin['xep_0030'].add_feature('urn:xmpp:carbons:2')
 
 def _handle_carbon_received(self, msg):
-self.xmpp.event('carbon_received', msg)
+if msg['from'].bare == self.xmpp.boundjid.bare:
+self.xmpp.event('carbon_received', msg)
 
 def _handle_carbon_sent(self, msg):
-self.xmpp.event('carbon_sent', msg)
+if msg['from'].bare == self.xmpp.boundjid.bare:
+self.xmpp.event('carbon_sent', msg)
 
 def enable(self, ifrom=None, timeout=None, callback=None,
timeout_callback=None):

Maybe it works for sleekxmpp, too. Will try soon.

Bug#858540: barbican: FTBFS: ImportError: No module named vine.five

[Chris Lamb]

Brian May wrote:

> Just for the record, this does *not* affect the version in testing.

Oh, did I mark it as such? Apologies if so :)


Regards,

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

Processed: Bug#858540 marked as pending

[Debian Bug Tracking System]

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

> tag 858540 pending
Bug #858540 [python-kombu] barbican: FTBFS: ImportError: No module named 
vine.five
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#858540: marked as pending

[Brian May]

tag 858540 pending
thanks

Hello,

Bug #858540 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/kombu.git/commit/?id=5850e20

---
commit 5850e207f04d0abac535ceb94e0b66457d80d53b
Author: Brian May 
Date:   Fri Mar 24 08:25:20 2017 +1100

Add missing build depends on python-vine and python3-vine. Closes: #858540.

diff --git a/debian/changelog b/debian/changelog
index 4d08da1..4d8c416 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+kombu (4.0.2+dfsg-2) UNRELEASED; urgency=medium
+
+  * Add missing build depends on python-vine and python3-vine.
+Closes: #858540.
+
+ -- Brian May   Fri, 24 Mar 2017 08:24:14 +1100
+
 kombu (4.0.2+dfsg-1) experimental; urgency=medium
 
   * Refresh patches after git-dpm to gbp pq conversion

Bug#858540: barbican: FTBFS: ImportError: No module named vine.five

[Brian May]

On Thu, Mar 23, 2017 at 08:02:30PM +, Chris Lamb wrote:
> This appears to affect more than src:barbican (eg. src:designate) and is
> probably a bug in Kombu instead:
> 
> File "/usr/lib/python2.7/dist-packages/kombu/five.py", line 6, in 
>   import vine.five
>   ImportError: No module named vine.five

Just for the record, this does *not* affect the version in testing.

(which initially had me concerned because vine is not in testing)
-- 
Brian May 

Bug#858576: python3-seaborn: Missing dependency on python3-tk

[Nicolas Braud-Santoni]

Package: python3-seaborn
Version: 0.7.1-2
Severity: serious

Dear Maintainer,

In a Python 3 interpreter, with python3-seaborn freshly installed,
`import seaborn` simply fails:

> >>> import seaborn
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/tkinter/__init__.py", line 36, in 
> import _tkinter
> ImportError: No module named '_tkinter'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python3/dist-packages/seaborn/__init__.py", line 6, in 
> 
> from .rcmod import *
>   File "/usr/lib/python3/dist-packages/seaborn/rcmod.py", line 8, in 
> from . import palettes, _orig_rc_params
>   File "/usr/lib/python3/dist-packages/seaborn/palettes.py", line 12, in 
> 
> from .utils import desaturate, set_hls_values, get_color_cycle
>   File "/usr/lib/python3/dist-packages/seaborn/utils.py", line 12, in 
> import matplotlib.pyplot as plt
>   File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 115, in 
> 
> _backend_mod, new_figure_manager, draw_if_interactive, _show = 
> pylab_setup()
>   File "/usr/lib/python3/dist-packages/matplotlib/backends/__init__.py", line 
> 32, in pylab_setup
> globals(),locals(),[backend_name],0)
>   File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_tkagg.py", 
> line 6, in 
> from six.moves import tkinter as Tk
>   File "/usr/lib/python3/dist-packages/six.py", line 92, in __get__
> result = self._resolve()
>   File "/usr/lib/python3/dist-packages/six.py", line 115, in _resolve
> return _import_module(self.mod)
>   File "/usr/lib/python3/dist-packages/six.py", line 82, in _import_module
> __import__(name)
>   File "/usr/lib/python3.5/tkinter/__init__.py", line 38, in 
> raise ImportError(str(msg) + ', please install the python3-tk package')
> ImportError: No module named '_tkinter', please install the python3-tk package


Installing python3-tk solves the issue.


Filing as serious, as I believe this is a missing dependency (hence,
a severe policy violation).  Feel free to readjust this.


Best,

  nicoo


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 python3-seaborn depends on:
ii  python3-matplotlib  2.0.0+dfsg1-2
ii  python3-numpy   1:1.12.0-2
ii  python3-pandas  0.19.2-5
ii  python3-scipy   0.18.1-2
pn  python3:any 

Versions of packages python3-seaborn recommends:
pn  python3-bs4
pn  python3-patsy  

python3-seaborn suggests no packages.

-- no debconf information

Bug#818558: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 20:55:38 +
with message-id 
and subject line Bug#858120: Removed package(s) from unstable
has caused the Debian Bug report #818558,
regarding Useless in Debian
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.)


-- 
818558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-jquery-minicolors
Version: 1.2.1-1
Severity: serious
Tag: sid stretch

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing. ]

I packaged libjs-jquery-minicolors as used by owncloud, but owncloud is
going away, see #816376. There is a priori little point to ship
libjs-jquery-minicolors in the next Debian stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.1-1+rm

Dear submitter,

as the package jquery-minicolors has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/858120

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#858553: [Pkg-pascal-devel] Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files

[Paul Gevers]

Reproducible in Ubuntu, the package is empty there, and in my pbuilder
environment. Looks like build_lcl_docs is broken somehow.

@Abou, can you take this up with upstream or shine your own light on it?
I have now idea what to do next. Also, do you have any idea what an
Exception isn't returning an error value as exit code? Seems like a
serious fpc or build_lcl_docs issue if you ask me. (I added the
--warnings to avoid any doubt what useful warnings were hidden).

$ ./build_lcl_docs --outfmt html --warnings
Warning! No corresponding xml file for unit customdrawn_mac.pas
Warning! No corresponding xml file for unit forms/calcform.pas
Warning! No corresponding xml file for unit forms/calendarpopup.pas
Warning! No corresponding xml file for unit forms/finddlgunit.pas
Warning! No corresponding xml file for unit forms/replacedlgunit.pas
Warning! No corresponding xml file for unit forms/timepopup.pas
Warning! No corresponding xml file for unit fpmake.pp
Warning! No corresponding xml file for unit
interfaces/cocoa/alllclintfunits.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoacaret.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoagdiobjects.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoaint.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoaprivate.pp
Warning! No corresponding xml file for unit interfaces/cocoa/cocoaproc.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoathemes.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoautils.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawsbuttons.pp
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawschecklst.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawscomctrls.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawscommon.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawsdialogs.pp
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawsextctrls.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawsfactory.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoawsforms.pp
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawsmenus.pas
Warning! No corresponding xml file for unit interfaces/cocoa/cocoawsspin.pas
Warning! No corresponding xml file for unit
interfaces/cocoa/cocoawsstdctrls.pp
Warning! No corresponding xml file for unit interfaces/cocoa/cocoa_extra.pas
Warning! No corresponding xml file for unit interfaces/cocoa/interfaces.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/alllclintfunits.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/android_native_app_glue.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/android_sockets.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/asset_manager.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/bitmap.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/configuration.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/egl.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/gles.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/input.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/jni.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/keycodes.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/log.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/looper.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/native_activity.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/native_window.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/android/rect.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/cocoagdiobjects.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/cocoautils.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnint.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnprivate.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnproc.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnthemes.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnwsbuttons.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnwscomctrls.pas
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnwscontrols.pp
Warning! No corresponding xml file for unit
interfaces/customdrawn/customdrawnwsdialogs.pas
Warning! No corresponding xml file for unit

Processed: Bug #511645: xtrs: Can hang on startup: marking grave

[Debian Bug Tracking System]

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

> package xtrs
Limiting to bugs with field 'package' containing at least one of 'xtrs'
Limit currently set to 'package':'xtrs'

> retitle 511645 xtrs: hangs on startup due to use of SIGIO
Bug #511645 [xtrs] Can hang on startup
Changed Bug title to 'xtrs: hangs on startup due to use of SIGIO' from 'Can 
hang on startup'.
> severity 511645 grave
Bug #511645 [xtrs] xtrs: hangs on startup due to use of SIGIO
Severity set to 'grave' from 'normal'
> tags 511645 - pending
Bug #511645 [xtrs] xtrs: hangs on startup due to use of SIGIO
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#511645: Bug #511645: xtrs: Can hang on startup: marking grave

[G. Branden Robinson]

package xtrs
retitle 511645 xtrs: hangs on startup due to use of SIGIO
severity 511645 grave
tags 511645 - pending
thanks

xtrs 4.9c no longer works at all on modern Linux systems, so it should
not be part of the next Debian stable release until this problem is
fixed.

Tim Mann's 4.9d release fixed this SIGIO issue and several other
problems.  (Having just built it, I see there are fresh compiler
warnings that need to be quieted.)

I wondered with some irritation what jackass had marked this bug as
pending.

Turns out it was me, back in 2009.  :-|

Ahem, well.

I'm clearing the pending tag because I need to, ah, generate a fresh GPG
key pair and get myself back in the ranks of active Debian developers.
That may take time, and Stretch should not ship with this nonfunctional
package.

Regards,
Branden

Processed: Re: barbican: FTBFS: ImportError: No module named vine.five

[Debian Bug Tracking System]

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

> reassign 858540 python-kombu
Bug #858540 [kombu] barbican: FTBFS: ImportError: No module named vine.five
Bug reassigned from package 'kombu' to 'python-kombu'.
No longer marked as found in versions 4.0.2+dfsg-1.
Ignoring request to alter fixed versions of bug #858540 to the same values 
previously set
> found 858540 4.0.2+dfsg-1
Bug #858540 [python-kombu] barbican: FTBFS: ImportError: No module named 
vine.five
Marked as found in versions kombu/4.0.2+dfsg-1.
> affects 858540 + barbican designate
Bug #858540 [python-kombu] barbican: FTBFS: ImportError: No module named 
vine.five
Ignoring request to set affects of bug 858540 to the same value previously set
> thanks
Stopping processing here.

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

Bug#858540: barbican: FTBFS: ImportError: No module named vine.five

[Chris Lamb]

reassign 858540 kombu
found 858540 4.0.2+dfsg-1
affects 858540 + barbican designate
thanks

Hi,

> barbican: FTBFS: ImportError: No module named vine.five

This appears to affect more than src:barbican (eg. src:designate) and is
probably a bug in Kombu instead:

File "/usr/lib/python2.7/dist-packages/kombu/five.py", line 6, in 
  import vine.five
  ImportError: No module named vine.five


Regards,

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

Processed: Re: barbican: FTBFS: ImportError: No module named vine.five

[Debian Bug Tracking System]

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

> reassign 858540 kombu
Bug #858540 [src:barbican] barbican: FTBFS: ImportError: No module named 
vine.five
Bug reassigned from package 'src:barbican' to 'kombu'.
No longer marked as found in versions barbican/1:3.0.0-2.
Ignoring request to alter fixed versions of bug #858540 to the same values 
previously set
> found 858540 4.0.2+dfsg-1
Bug #858540 [kombu] barbican: FTBFS: ImportError: No module named vine.five
There is no source info for the package 'kombu' at version '4.0.2+dfsg-1' with 
architecture ''
Unable to make a source version for version '4.0.2+dfsg-1'
Marked as found in versions 4.0.2+dfsg-1.
> affects 858540 + barbican designate
Bug #858540 [kombu] barbican: FTBFS: ImportError: No module named vine.five
Added indication that 858540 affects barbican and designate
> thanks
Stopping processing here.

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

Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files

[Paul Gevers]

On 23-03-17 12:33, Abou Al Montacir wrote:
> The package lazarus-doc-1.6 does not ship any documentation file.

Not sure if it explains anything, but I see two Exceptions in the build
log¹. I suspect these are the root cause, but I would have expected the
build to fail if that was considered fatal though:

...
/interfaces/gtk/gtkwsstdctrls.pp -Fi../../../lcl/include"FPDoc - Free
Pascal Documentation Tool
Version 3.0.0 [2016/09/12]
(c) 2000 - 2003 Areca Systems GmbH / Sebastian Guenther, s...@freepascal.org
(c) 2005 - 2012 various FPC contributors

Exception at 004BDB6C: EDOMError:
EDOMError in DOMDocument.CreateElement.

Writing 21499 pages...
274 Warnings hidden. Use --warnings to see them all.
./build_lcl_docs --outfmt chm
...

and

...
Version 3.0.0 [2016/09/12]
(c) 2000 - 2003 Areca Systems GmbH / Sebastian Guenther, s...@freepascal.org
(c) 2005 - 2012 various FPC contributors

Exception at 004BDB6C: EDOMError:
EDOMError in DOMDocument.CreateElement.

Writing 21499 pages...
274 Warnings hidden. Use --warnings to see them all.

Somewhat later we have:
/usr/bin/make -C docs/html htmlinstall
INSTALL_PREFIX=/«BUILDDIR»/lazarus-1.6.2+dfsg/debian/tmp2/usr
INSTALL_DOCDIR=/«BUILDDIR»/lazarus-1.6.2+dfsg/debian/tmp2/usr/share/doc/lazarus/1.6.2

Which is the install command from lazarus. That looks all right, except
apparently there were no files to install, because several lines later...
Now scanning
"/«BUILDDIR»/lazarus-1.6.2+dfsg/debian/tmp2/usr/share/doc/lazarus/1.6.2",
found 5 files.

Paul

¹
https://buildd.debian.org/status/fetch.php?pkg=lazarus=all=1.6.2%2Bdfsg-1=1481146459=0



signature.asc
Description: OpenPGP digital signature

Processed (with 2 errors): merge #750541 #858405 attempt 3...

[Debian Bug Tracking System]

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

> unarchive 750541
Bug #750541 {Done: Ivo De Decker } [src:samba] samba: 
FTBFS on various architectures, uninstallable
Bug #750796 {Done: Ivo De Decker } [src:samba] libldb1: 
aptitude upgrade on sid runs into trouble with libldb1 versioning
Unarchived Bug 750541
Unarchived Bug 750796
> unarchive 750796
> unarchive 763163
Bug #763163 {Done: Jelmer Vernooij } [src:samba] samba: 
FTBFS: recipe for target 'override_dh_install' failed
Unarchived Bug 763163
> forcemerge 750593 858405
Bug #750593 [xsltproc] xsltproc: bus error on some architectures
Bug #858405 [xsltproc] xmlto: intermittent Segmentation fault when building 
manpages for libreswan on mips64el
750541 was blocked by: 750593
750541 was not blocking any bugs.
Added blocking bug(s) of 750541: 858405
750796 was blocked by: 750593
750796 was not blocking any bugs.
Added blocking bug(s) of 750796: 858405
763163 was blocked by: 750593
763163 was not blocking any bugs.
Added blocking bug(s) of 763163: 858405
750796 was blocked by: 750593 858405
750796 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #750796 to the same blocks 
previously set
750541 was blocked by: 750593 858405
750541 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #750541 to the same blocks 
previously set
Removed indication that 858405 affects libreswan
Marked as found in versions libxslt/1.1.28-2.
Added tag(s) jessie-ignore.
Merged 750593 858405
> retitle 750593 xsltproc: bus error on some arches with linux < 4.1
Bug #750593 [xsltproc] xsltproc: bus error on some architectures
Bug #858405 [xsltproc] xmlto: intermittent Segmentation fault when building 
manpages for libreswan on mips64el
Changed Bug title to 'xsltproc: bus error on some arches with linux < 4.1' from 
'xsltproc: bus error on some architectures'.
Changed Bug title to 'xsltproc: bus error on some arches with linux < 4.1' from 
'xmlto: intermittent Segmentation fault when building manpages for libreswan on 
mips64el'.
> archive 750541
Bug #750541 {Done: Ivo De Decker } [src:samba] samba: 
FTBFS on various architectures, uninstallable
Bug #750796 {Done: Ivo De Decker } [src:samba] libldb1: 
aptitude upgrade on sid runs into trouble with libldb1 versioning
archived 750541 to archive/41 (from 750541)
archived 750796 to archive/96 (from 750541)
> archive 750796
> archive 763163
Bug #763163 {Done: Jelmer Vernooij } [src:samba] samba: 
FTBFS: recipe for target 'override_dh_install' failed
archived 763163 to archive/63 (from 763163)
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
750541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750541
750593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593
750796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750796
763163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763163
858405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#857385: jablicator: should it be removed from the archive?

[Jeff Breidenbach]

If you know who to ask and are willing, I appreciate it.

Otherwise, I'll figure it out eventually.

Bug#857922: marked as done (Uses cache dir under /usr (instead of /var/cache) violating FHS)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 19:04:04 +
with message-id 
and subject line Bug#857922: fixed in jython 2.5.3-16
has caused the Debian Bug report #857922,
regarding Uses cache dir under /usr (instead of /var/cache) violating FHS
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.)


-- 
857922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jython
Version: 2.5.3-15
Severity: serious

The (system) Jython cache dir is in /usr/share/jython/Cache, while the
FHS wants to have it in /var/cache/.

This is problematic, since the cache may tend to be filled by the
installation of Jython packages or by other Jython invocations as root,
but is never cleaned up explicitely.

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: jython
Source-Version: 2.5.3-16

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated jython 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, 20 Mar 2017 21:18:22 +0100
Source: jython
Binary: jython jython-doc
Architecture: source
Version: 2.5.3-16
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Gilles Filippini 
Description:
 jython - Python seamlessly integrated with Java
 jython-doc - Jython documentation including API docs
Closes: 857921 857922
Changes:
 jython (2.5.3-16) unstable; urgency=medium
 .
   * Improve 03-default-cachedir.patch to consider cachedir relative to
 $HOME when it isn't an absolute path (closes: #857921, #857922)
   * Set default cachedir in global registry as '.jython-cache' instead
 of 'cachedir'
Checksums-Sha1:
 20d8833dac2cf95a7432399f864fc6485f95455e 2057 jython_2.5.3-16.dsc
 e704022a45c2b9edf39764c63de3015a21ae4a68 19952 jython_2.5.3-16.debian.tar.xz
 c50c7d7808b061e497dcc238d39e97fd99b42086 6656 jython_2.5.3-16_source.buildinfo
Checksums-Sha256:
 06417ff02ec8c8e5a0badd8f0415a6d8ec14ea7cae0e538f0b5d49c078b2c318 2057 
jython_2.5.3-16.dsc
 55f29d724b84f8f573cfd498bd709dfc6cf15e37e6ef6a0b3a7d03198c48614a 19952 
jython_2.5.3-16.debian.tar.xz
 0cbfccf3dbecb1a4e8edac59e8a01191d1683485eaf7e57108ebb739a029d2b5 6656 
jython_2.5.3-16_source.buildinfo
Files:
 580fb8db2c9e6a2ec515b9ea73008265 2057 python optional jython_2.5.3-16.dsc
 19c3978424230858adf6d51d4f4d682c 19952 python optional 
jython_2.5.3-16.debian.tar.xz
 38e5050d78584a66097e3cc0f09d5bc3 6656 python optional 
jython_2.5.3-16_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFEBAEBCAAuFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAljUGNsQHHBpbmlAZGVi
aWFuLm9yZwAKCRDv6Gxsf/7PgyYQB/9fsoueua50vkDur4wo2jzKnSunF099nu6l
oViokEotX/hmHdkb0grJeiakr/ZQg0e+pmtedj3+pfoDeJudsc754G2h6dMiuHfn
IvOQIIxTzYyLbi+XC0pJKu2y5bMNfJYtpAmj0K7rCckITwxDNNI7cp054yH+ATB7
YGSDDytIHAWECGT7f0XlI3UqNoLOdQXxot31YErsgLJODT9hIjpPQF51Nc7txBY9
wulXZFwmLyXh0uv5Y4oiSBJFrWALrOunCFS4T1GdCwFDPngfO8DKn8m7ClE2NIxR
XFxaM2pqntAvF6OsORmWTzCsPKlzH/ALIDiw5PmUSKX0IbC4Ms8/
=qhNj
-END PGP SIGNATURE End Message ---

Bug#857795: Correct location for installed files is /usr/share/locale/

[Andriy Grytsenko]

Thank you for reminding on that, will look at it ASAP.

Processed: tagging 858564

[Debian Bug Tracking System]

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

> tags 858564 + moreinfo
Bug #858564 [samba] samba: Since 8u4, Samba does not allow files not in root 
directory of share
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: found 858564 in 2:4.2.14+dfsg-0+deb8u4

[Debian Bug Tracking System]

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

> # according to reporter
> found 858564 2:4.2.14+dfsg-0+deb8u4
Bug #858564 [samba] samba: Since 8u4, Samba does not allow files not in root 
directory of share
Marked as found in versions samba/2:4.2.14+dfsg-0+deb8u4.
> thanks
Stopping processing here.

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

Processed: notfound 858564 in 2:4.2.14+dfsg-0+deb8u2

[Debian Bug Tracking System]

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

> notfound 858564 2:4.2.14+dfsg-0+deb8u2
Bug #858564 [samba] samba: Since 8u4, Samba does not allow files not in root 
directory of share
No longer marked as found in versions samba/2:4.2.14+dfsg-0+deb8u2.
> thanks
Stopping processing here.

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

Bug#857795: Correct location for installed files is /usr/share/locale/

[Jorge Moraleda]

Dear Mantainer,

All files installed in /usr/@DATADIRNAME@/locale/ should instead be
installed to /usr/share/locale.

One other packet, mssh, also incorrectly installs files to
/usr/@DATADIRNAME@/locale. This has been reported separately as bug #858567

Best regards,

Jorge Moraleda

Processed: severity of 858546 is grave

[Debian Bug Tracking System]

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

> # mark as RC, fix should go to stretch before release
> severity 858546 grave
Bug #858546 [src:libxslt] CVE-2017-5029: Integer overflow in xsltAddTextString
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 858567 is serious, severity of 857795 is serious

[Debian Bug Tracking System]

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

> # An unexpanded /usr/@DATADIRNAME@/ as path is clearly a severe bug and an 
> FHS violation
> severity 858567 serious
Bug #858567 [mssh] mssh: local files installed to /usr/@DATADIRNAME@/locale
Severity set to 'serious' from 'normal'
> severity 857795 serious
Bug #857795 [gnome-system-tools] [gnome-system-tools] local files installed to 
/usr/@DATADIRNAME@/locale
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#858564: samba: Since 8u4, Samba does not allow files not in root directory of share

[James Bellinger]

Package: samba
Version: 2:4.2.14+dfsg-0+deb8u2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
I upgraded to 8u4 through unattended upgrades.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
(1) I attempt to create a file not in the root directory of the share.
(2) I try to write to files not in the root directory of the share.
   * What was the outcome of this action?
(1) Windows Explorer freezes entirely until I end task it.
(2) It says permission denied.
   * What outcome did you expect instead?
(1) Normally I can create files.
(2) Normally I can access files.

I have reverted back to 8u2 and am no longer experiencing problems.
Access to the root directory of the share works fine.

My smb.conf is as follows:
(start)
[global]
server string = Server
workgroup = WORKGROUP
log level = 1

interfaces = eth0 eth0:0 eth0:1 eth0:2 eth0:3
bind interfaces only = yes
socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=65536 SO_RCVBUF=65536

server role = standalone server
disable netbios = yes
disable spoolss = yes
csc policy = disable
oplocks = no
server min protocol = NT1

passdb backend = tdbsam
encrypt passwords = yes
invalid users = root fsadmin
disable netbios = yes
disable spoolss = yes
csc policy = disable
oplocks = no
server min protocol = NT1

passdb backend = tdbsam
encrypt passwords = yes
invalid users = root fsadmin

follow symlinks = no
hide dot files = no
wide links = no

create mask = 660
directory mask = 770

vfs objects = acl_xattr streams_xattr full_audit
full_audit:prefix = %S|%u|%I
follow symlinks = no
hide dot files = no
wide links = no

create mask = 660
directory mask = 770

vfs objects = acl_xattr streams_xattr full_audit
full_audit:prefix = %S|%u|%I
full_audit:success = mkdir open opendir rename rmdir unlink
full_audit:failure = all !getxattr !removexattr !is_offline !readdir_att$
full_audit:facility = LOCAL7
full_audit:priority = ALERT

map acl inherit = yes
store dos attributes = yes

browseable = no
writeable = yes

include = /etc/samba/smb.conf.%i
(end)

As an example of the IP-address specific file, here's one:
(start)
[hr$]
comment = HR Server
path = /mnt/data/hr
force group = +AccessHR
valid users = @AccessHR
(end)

Permissions are absolutely fine. They are essentially 770.
AppArmor is enabled, but I disabled it and the problem still exists in 8u4.
It does not exist in 8u2.

*** End of the template - remove these template lines ***


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

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

Versions of packages samba depends on:
ii  adduser  3.113+nmu3
ii  dpkg 1.17.27
ii  libbsd0  0.7.0-2
ii  libc62.19-18+deb8u7
ii  libhdb9-heimdal [heimdal-hdb-api-8]  1.6~rc2+dfsg-9
ii  libldb1  2:1.1.20-0+deb8u1
ii  libpam-modules   1.1.8-3.1+deb8u2
ii  libpam-runtime   1.1.8-3.1+deb8u2
ii  libpopt0 1.16-10
ii  libpython2.7 2.7.9-2+deb8u1
ii  libtalloc2   2.1.2-0+deb8u1
ii  libtdb1  1.3.6-0+deb8u1
ii  libtevent0   0.9.28-0+deb8u1
ii  lsb-base 4.1+Debian13+nmu1
ii  multiarch-support2.19-18+deb8u7
ii  procps   2:3.3.9-9
ii  python   2.7.9-1
ii  python-dnspython 1.12.0-1
ii  python-ntdb  1.0-5
ii  python-samba 2:4.2.14+dfsg-0+deb8u2
pn  python2.7:any
ii  samba-common 2:4.2.14+dfsg-0+deb8u2
ii  samba-common-bin 2:4.2.14+dfsg-0+deb8u2
ii  samba-dsdb-modules   2:4.2.14+dfsg-0+deb8u2
ii  samba-libs   2:4.2.14+dfsg-0+deb8u2
ii  tdb-tools1.3.6-0+deb8u1
ii  update-inetd 4.43

Versions of packages samba recommends:
ii  attr   1:2.4.47-2
ii  logrotate  3.8.7-1+b1
ii  samba-vfs-modules  2:4.2.14+dfsg-0+deb8u2

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
pn  ldb-tools  
pn  ntp
pn  smbldap-tools  
pn  winbind

-- no debconf information

Bug#832510: marked as done (skalibs: FTBFS when built with dpkg-buildpackage -A (Missing build-indep target))

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 16:34:54 +
with message-id 
and subject line Bug#832510: fixed in skalibs 0.47-1.1
has caused the Debian Bug report #832510,
regarding skalibs: FTBFS when built with dpkg-buildpackage -A (Missing 
build-indep target)
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.)


-- 
832510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:skalibs
Version: 0.47-1
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
make: *** No rule to make target 'build-indep'.  Stop.
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build-arch and build-indep targets are mandatory.

Previously, dpkg had a hack to make this work, but the hack has been recently
removed and this is now considered a serious bug.

Fortunately, this is easy to fix. The following patch should suffice.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -30,6 +30,8 @@ configure-stamp:
echo 'diet -v -Os gcc' >diet/skalibs/conf-compile/conf-ld
touch configure-stamp
 
+build-arch: build
+build-indep: build
 build: deb-checkdir build-stamp
 build-stamp: configure-stamp
(cd skalibs && package/compile)
@@ -89,7 +91,7 @@ binary-arch: install-arch skalibs-dev.deb
 
 binary: binary-indep binary-arch
 
-.PHONY: configure build clean install-indep install-arch install binary-indep \
+.PHONY: configure build build-arch build-indep clean install-indep 
install-arch install binary-indep \
  binary-arch binary
 
 include debian/implicit
--- End Message ---
--- Begin Message ---
Source: skalibs
Source-Version: 0.47-1.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated skalibs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Mar 2017 16:24:06 +0100
Source: skalibs
Binary: skalibs-dev skalibs-doc
Architecture: source
Version: 0.47-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Mattia Rizzolo 
Description:
 skalibs-dev - Public domain general-purpose libraries
 skalibs-doc - Public domain general-purpose libraries (documentation)
Closes: 832510 847030
Changes:
 skalibs (0.47-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/rules: add missing build-arch and build-indep targets.
 Thanks to Santiago Vila for the patch.  Closes: #832510
   * Make the build reproducible by sorting the md5sums file.
 Thanks to Valerie R Young for the patch.  Closes: #847030
   * d/control: move the homepage to the Homepage field.
Checksums-Sha1:
 a0b3237d4842e82d6ae39f7810b0b5468ba5da7a 1957 skalibs_0.47-1.1.dsc
 f282e0446f73b42c7ba4e793884c0700b7a84868 3595 skalibs_0.47-1.1.diff.gz
Checksums-Sha256:
 2c9d750ec9b1999090248ebb7405f78a11019529d2cbafac9616718836fa6baf 1957 
skalibs_0.47-1.1.dsc
 dd6ca52e0c2eff82cf628e40e6e031dc80800871ad6c065acc13944f72f8d8f0 3595 
skalibs_0.47-1.1.diff.gz
Files:
 2cf7dbc2c5587b64eea12c361469c5fa 1957 devel optional skalibs_0.47-1.1.dsc
 ed6668964f03562acffc0f404a56bc74 3595 devel optional skalibs_0.47-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAljAI+YSHG1hdHRpYUBk
ZWJpYW4ub3JnAAoJEAgWueGMdiut0VMP/iMoA9UKu+pAG7fahRelKW+Me9zgloGm
9Xxt1rFAtByyOkzQxJzMVxKxJjO8AjpZ1Yd81JEcZ6yVs3WsNkfdacPb2NNCzowD
xm96krZ8zF5sdjKk7cH+uMnnbIEFNVF7BVhDDuOEgD7ZmzhyUgqyo2pmAgL5/qfY
ALYNgkraIb35yrxFodTltnCaVnE70HpKGV08BwSad++EibzjzFXI6EOb3vR5euEN
93gL73VI/8ABW3s5y7J2pWI0YTZbq8A6beymXSPWVyipEKAbu2ahKAI37N9QTKqE

Bug#831943: marked as done (cvs-mailcommit: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 15:34:18 +
with message-id 
and subject line Bug#831943: fixed in cvs-mailcommit 1.19-2.1
has caused the Debian Bug report #831943,
regarding cvs-mailcommit: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: 
error: binary build with no binary artifacts found; cannot distribute
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.)


-- 
831943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cvs-mailcommit
Version: 1.19-2
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> make: Nothing to be done for 'binary-indep'.
>  dpkg-genchanges --build=all >../cvs-mailcommit_1.19-2_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/cvs-mailcommit_1.19-2_unstable_archallonly.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: cvs-mailcommit
Source-Version: 1.19-2.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated cvs-mailcommit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Mar 2017 15:26:26 +0100
Source: cvs-mailcommit
Binary: cvs-mailcommit
Architecture: source
Version: 1.19-2.1
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze 
Changed-By: Mattia Rizzolo 
Description:
 cvs-mailcommit - Send CVS commitments via mail
Closes: 776940 831943
Changes:
 cvs-mailcommit (1.19-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/rules: make the build reproducible by passing -n to gzip.
 Thanks to Chris Lamb for the patch.  Closes: #776940
   * d/rules: fix build with dpkg-buildpackage -A.
 Thanks to Santiago Vila for the patch.  Closes: #831943
   * Use source format 3.0 (quilt).
Checksums-Sha1:
 6f0ff5fc1dc5564826c8a74c5ec08ae4393c80b3 1829 cvs-mailcommit_1.19-2.1.dsc
 ed2ee2bb3a9debea4991ca9ce3bf2b13f58c53d4 2748 
cvs-mailcommit_1.19-2.1.debian.tar.xz
Checksums-Sha256:
 d6cc9477d6f5f2750ed080d5ea6a44c4d316b6c597d5d81d3f3774c72428aefc 1829 
cvs-mailcommit_1.19-2.1.dsc
 11db56cc79a7714f2c56610f804615f6b6c5f82b00ca7a1d5a80db54a1225fe1 2748 

Bug#858486: marked as done (python-mne: broken symlink: /usr/lib/python2.7/dist-packages/mne/html/d3.v3.min.js -> ../../../../../share/javascript/d3/d3.min.js)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 15:04:45 +
with message-id 
and subject line Bug#858486: fixed in python-mne 0.13.1+dfsg-3
has caused the Debian Bug report #858486,
regarding python-mne: broken symlink: 
/usr/lib/python2.7/dist-packages/mne/html/d3.v3.min.js -> 
../../../../../share/javascript/d3/d3.min.js
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.)


-- 
858486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mne
Version: 0.13.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

3m14.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/python2.7/dist-packages/mne/html/d3.v3.min.js -> 
../../../../../share/javascript/d3/d3.min.js

Looks like a missing Depends: libjs-d3

Feel free to downgrade the severity and use Recommends/Suggests
instead of Depends if this *only* affects documentation.


cheers,

Andreas


python-mne_0.13.1+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-mne
Source-Version: 0.13.1+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-mne package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Mar 2017 15:14:07 +0100
Source: python-mne
Binary: python-mne
Architecture: source all
Version: 0.13.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-mne - Python modules for MEG and EEG data analysis
Closes: 858486
Changes:
 python-mne (0.13.1+dfsg-3) unstable; urgency=medium
 .
   * Depends: libjs-d3
 Closes: #858486
Checksums-Sha1:
 e4f3fb74bbb3b4302522d92bea1f6fbb2c0e77b4 2387 python-mne_0.13.1+dfsg-3.dsc
 9af482ddcef261b98dabc4321a1d832689977a26 31988 
python-mne_0.13.1+dfsg-3.debian.tar.xz
 571a62794df3051514f0a887b7a3b28f378b2092 4506342 
python-mne_0.13.1+dfsg-3_all.deb
 64a77b09e00d6bec369d52bd15635b719169772c 17301 
python-mne_0.13.1+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 07f6042070c673a675ac6ca70f51e16d57f3822ed11a45be1b6b330e8651d075 2387 
python-mne_0.13.1+dfsg-3.dsc
 2d41749f9228bd52cef1d51040f3614596880a3b2e231994a07301f7773e6c9e 31988 
python-mne_0.13.1+dfsg-3.debian.tar.xz
 552c0fd6d9904cedea9d0043f6b0df3506b595e02b04dbb178b033f51ec7c6ae 4506342 
python-mne_0.13.1+dfsg-3_all.deb
 02edf773c81fe480934601314290ed17ff1cd4ea9696cb8b3d8797b4f306e808 17301 
python-mne_0.13.1+dfsg-3_amd64.buildinfo
Files:
 75ea2249d4e4153880cf8deca16086f6 2387 python optional 
python-mne_0.13.1+dfsg-3.dsc
 5e60b016af88377fccee76dc93b6eeb0 31988 python optional 
python-mne_0.13.1+dfsg-3.debian.tar.xz
 a01088cd283014b129109b64be9692ff 4506342 python optional 
python-mne_0.13.1+dfsg-3_all.deb
 8d9636513362e14dcf1ff67b2d78ba4b 17301 python optional 
python-mne_0.13.1+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAljT3rIOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEN6g//R1BopDZVCKTiEZk8LC0pNeyNrawdrQaU43TH
DknOghcb5SV0oOeyUm5/Un15l5rtUeTRBwhpEx7S1a7FT/gKnjIfIt/iXVBkPKOA
eWPa4jp+xUg97+RLFkmq47EKGLC4ankI8f2zJw4I6mdJELJyi04bVeT/wZ9ohKEw
7JjhCx6u+H1OXYSHGi+f6R6n7HdDISLf5ytpSb3UDTw7gnTvAcmUpsOhBQMrjWBu
M3JizHEBnfaTFNjhX7D4IuwjT6gg8Db8iI5ufr2cmF5HZ0BpC2AX4Re2VQcLMEog
L18U3dkTzFzmoWld2Xj/I2HGyjeq+89QNc8ugPblxP1ufWe73LXQVIepGGcO1FHm
m4p45N2WnNBzDni2V5brYCqvfeHkb/ZUwQ0H5cfKG0eQMnGZ9OPpayBgCSAO7dMj
yPWIt2N0Cq8excyCKETLuOOg+CgYMoYZl0/EdrLf8O3TRXCXXhdjIectcG7vIT+e
AP5LqvLW9N7gbsq3G9xfTfRDLWAYDg+Zzk69I1HYCc7CI4XmOQvQEVr2+v5y/1nF
Vl0v8Xh1s7UJQVE4sAU/JqVW95ASonuZ0x8iFx5Vgbpevch+EUFIVk40Dx7cY77s
AS01KIMPeHBmtSXAvhZZlupVwv5N/6N6qS9z3GH112tHuqZXrcrgvIyfXAtMUx59
Qamq5JI=
=MNWg
-END PGP 

Bug#827199: marked as done (hfst: FTBFS: twolc test fails on big-endian systems)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 15:04:24 +
with message-id 
and subject line Bug#827199: fixed in hfst 3.10.0~r2798-3
has caused the Debian Bug report #827199,
regarding hfst: FTBFS: twolc test fails on big-endian systems
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.)


-- 
827199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hfst
Version: 3.10.0~r2798-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Thanks for taking care of the twolc errors I reported in #826659.  The
twolc test now succeeds on little-endian systems, and no longer hangs
anywhere, but still fails on big-endian architectures (mips, powerpc,
s390x, and several non-release architectures).  I don't have further
details, but perhaps you can reproduce the problem on a porterbox.
Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: hfst
Source-Version: 3.10.0~r2798-3

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated hfst package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Mar 2017 18:48:47 +0530
Source: hfst
Binary: hfst libhfst45 libhfst45-dev python-libhfst python3-libhfst
Architecture: source amd64
Version: 3.10.0~r2798-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 hfst   - Helsinki Finite-State Transducer Technology
 libhfst45  - Helsinki Finite-State Transducer Technology Libraries
 libhfst45-dev - Helsinki Finite-State Transducer Technology Development files
 python-libhfst - Helsinki Finite-State Transducer Technology (Python2 module)
 python3-libhfst - Helsinki Finite-State Transducer Technology (Python3 module)
Closes: 827199
Changes:
 hfst (3.10.0~r2798-3) unstable; urgency=medium
 .
   [ Tino Didriksen ]
   * Workaround tests failing on big-endian (Closes: #827199)
 + Not solved, but not needed because hfst-ospell fixed the end-user case
Checksums-Sha1:
 cdfffe695c56527d7dfff0a55a2cb754b0d1de01 2445 hfst_3.10.0~r2798-3.dsc
 aeb7908d51963660d9973bd7e76840404949f0a1 7372 hfst_3.10.0~r2798-3.debian.tar.xz
 c0201679f9911d87f75a030a79e660e169251e6b 47671968 
hfst-dbgsym_3.10.0~r2798-3_amd64.deb
 da7c0f2d791552a429c061681cb3cf0c67e8d361 8640 
hfst_3.10.0~r2798-3_amd64.buildinfo
 da4f39fc865fcd38e072f0991cbe549809c0299d 1154122 hfst_3.10.0~r2798-3_amd64.deb
 959fb2735f3f0a87bcb9d7701a080f4c134bf6f7 22304226 
libhfst45-dbgsym_3.10.0~r2798-3_amd64.deb
 e42dfb6bad45e7dcda83e93ca719af2e9964d550 185244 
libhfst45-dev_3.10.0~r2798-3_amd64.deb
 d12fbc7c4f8771605236391f5c998779d576e2ef 1535824 
libhfst45_3.10.0~r2798-3_amd64.deb
 345ba78098b19cdac33e071b7e133c0141681d57 91778 
python-libhfst_3.10.0~r2798-3_amd64.deb
 1cb1c2b29369df5be5f1c87e9a57de5eab9be0c6 451308 
python3-libhfst_3.10.0~r2798-3_amd64.deb
Checksums-Sha256:
 d7b516b8acea229e34c20ef65090bf6b1e9414afc6aadfff4501f538d18b793a 2445 
hfst_3.10.0~r2798-3.dsc
 9f27e96ad644950036005a7318282a4aecc4fcc77a2f704aa65bd9dd7acff994 7372 
hfst_3.10.0~r2798-3.debian.tar.xz
 68a6ac4fa9fc3756b4d87ad5b04766821673947b84c337cc86d0e03d5ae11da1 47671968 
hfst-dbgsym_3.10.0~r2798-3_amd64.deb
 ea2ad24df6f42b8926a511eabb530293efef750241ceebf9aa4548d69cb32480 8640 
hfst_3.10.0~r2798-3_amd64.buildinfo
 03247bee24a9f970095c203a9c763628c03b60b2768c286e733746be8106c106 1154122 
hfst_3.10.0~r2798-3_amd64.deb
 0be8e5fcdb04c097e6be9c7abdea16edf160a1b2d50f59bec5d98f6e26af773d 22304226 
libhfst45-dbgsym_3.10.0~r2798-3_amd64.deb
 03e3d8f592abb0600a9c9366575179c75915bf59c0b4b5c5f2152358eb35fc45 185244 
libhfst45-dev_3.10.0~r2798-3_amd64.deb
 9ae5247379f577d681aa769515295139a197b4cace6c909522a1a8eb7ee8 1535824 
libhfst45_3.10.0~r2798-3_amd64.deb
 

Bug#857909: [libc6-dev] getpid() in child process created using clone(CLONE_VM) returns parent's pid

[Florian Weimer]

* John Paul Adrian Glaubitz:

> I would suggest filing a bug report to glibc upstream or posting on
> their mailing list to ask for feedback.

Upstream has since removed the PID cache:

  
  

Bug#839218: nama: FTBFS: Failed 1/7 test programs. 0/91 subtests failed.Bad plan. You planned 126 tests but ran 57.

[Balint Reczey]

Hi Niko,

On Wed, Mar 22, 2017 at 8:53 PM, Niko Tyni  wrote:
> On Tue, Mar 21, 2017 at 04:05:43PM +0100, Balint Reczey wrote:
>
>> It looks like not all regression are fixed after the re-implementation
>> and the one affecting nama is one of them.
>
> Some effort on a reduced test case would have been appreciated; the nama
> code base is rather big.

I worked on reducing the test, but I could not reach reasonable size and
thought someone familiar with Perl internals could potentially spot the
problem easily from the segfault/assert.

I just found a perl test reducer, I'll give it a try:
https://github.com/blekko/perl-reduce

>
> While I haven't made it to the bottom of this yet, I note that there's
> this code in lib/Audio/Nama/Effect.pm:
>
> my $perl_version = $^V;
> my ($minor_version) = $perl_version =~ /^v5\.(\d+)/;
> my @new_list = grep  { $_ ne $id  } @ops_list;
> #say "new_list: @new_list";
> if ($minor_version <= 14)
>  {$track->{ops}   = [ @new_list  ] }
> else { @{ $track->{ops} } =   @new_list}
>
> and if I patch that to take the <= 14 code path, the segfault goes away
> here and all tests pass. What's the history behind this version check?

Funny story, it was added to work around a segfault in older perl:
https://github.com/bolangi/nama/commit/8ecdbd5ad0b8ac67b7e4adab2ee1100fbf29aa1f

The line you found looks very much like a corner case for the assignment
reimplementation.

Should I forward it to Perl upstream?

Cheers,
Balint

Processed: fixed in diaspora-installer/0.6.3.0+debian4

[Debian Bug Tracking System]

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

> fixed 858521 diaspora-installer/0.6.3.0+debian4
Bug #858521 {Done: Pirate Praveen } [diaspora-common] 
diaspora-common: does 'rm -rf /' on purge
Marked as fixed in versions diaspora-installer/0.6.3.0+debian4.
>
End of message, stopping processing here.

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

Bug#858521: marked as done (diaspora-common: does 'rm -rf /' on purge)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 20:05:58 +0530
with message-id <3a791a76-6926-277d-bfef-ae8aaf287...@onenetbeyond.org>
and subject line fixed in diaspora-installer/0.6.3.0+debian4
has caused the Debian Bug report #858521,
regarding diaspora-common: does 'rm -rf /' on purge
to be marked as done.

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

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


-- 
858521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora-common
Version: 0.6.3.0+debian3
Severity: critical
Justification: breaks the whole system
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package makes havoc in the
chroot.

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

1m47.3s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpOwZDY2', 'dpkg', 
'--purge', 'diaspora-common']
1m48.1s DUMP: 
  (Reading database ... 4707 files and directories currently installed.)
  Purging configuration files for diaspora-common (0.6.3.0+debian3) ...
  /var/lib/dpkg/info/diaspora-common.postrm: 63: 
/var/lib/dpkg/info/diaspora-common.postrm: rm: not found
  dpkg: error processing package diaspora-common (--purge):
   subprocess installed post-removal script returned error exit status 127
  Errors were encountered while processing:
   diaspora-common
1m48.1s DEBUG: Command failed (status=1), but ignoring error: ['chroot', 
'/tmp/piupartss/tmpOwZDY2', 'dpkg', '--purge', 'diaspora-common']
1m48.1s INFO: Running scripts post_purge
1m48.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpOwZDY2', 
'tmp/scripts/post_purge_exceptions']
1m48.1s DUMP: 
  chroot: failed to run command 'tmp/scripts/post_purge_exceptions': No such 
file or directory
1m48.1s ERROR: Command failed (status=127): ['chroot', 
'/tmp/piupartss/tmpOwZDY2', 'tmp/scripts/post_purge_exceptions']


This very much looks like an 'rm -rf /' in the chroot ... rm is gone, sh is 
gone, ...


cheers,

Andreas


diaspora-common_0.6.3.0+debian3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
fixed -1 diaspora-installer/0.6.3.0+debian4



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

Bug#858486: [Debian-med-packaging] Bug#858486: python-mne: broken symlink: /usr/lib/python2.7/dist-packages/mne/html/d3.v3.min.js -> ../../../../../share/javascript/d3/d3.min.js

[Alexandre Gramfort]

hi,

python-mne does need the d3 package so yes one should have the:

Depends: libjs-d3

can someone help me fixing this?

thanks a lot

Best,
Alex


On Wed, Mar 22, 2017 at 9:04 PM, Andreas Beckmann  wrote:
> Package: python-mne
> Version: 0.13.1+dfsg-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
>
> >From the attached log (scroll to the bottom...):
>
> 3m14.3s ERROR: FAIL: Broken symlinks:
>   /usr/lib/python2.7/dist-packages/mne/html/d3.v3.min.js -> 
> ../../../../../share/javascript/d3/d3.min.js
>
> Looks like a missing Depends: libjs-d3
>
> Feel free to downgrade the severity and use Recommends/Suggests
> instead of Depends if this *only* affects documentation.
>
>
> cheers,
>
> Andreas
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

Processed: Re: Bug#858527: samtools: uninstallable in experimental: unsatisfiable Depends: libhts1 (>= 1.4-1)

[Debian Bug Tracking System]

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

> reassign 858527 release.debian.org
Bug #858527 [samtools] samtools: uninstallable in experimental: unsatisfiable 
Depends: libhts1 (>= 1.4-1)
Bug reassigned from package 'samtools' to 'release.debian.org'.
No longer marked as found in versions samtools/1.4-1.
Ignoring request to alter fixed versions of bug #858527 to the same values 
previously set
> severity 858527 normal
Bug #858527 [release.debian.org] samtools: uninstallable in experimental: 
unsatisfiable Depends: libhts1 (>= 1.4-1)
Severity set to 'normal' from 'serious'
> retitle 858527 nmu: samtools_1.4-1
Bug #858527 [release.debian.org] samtools: uninstallable in experimental: 
unsatisfiable Depends: libhts1 (>= 1.4-1)
Changed Bug title to 'nmu: samtools_1.4-1' from 'samtools: uninstallable in 
experimental: unsatisfiable Depends: libhts1 (>= 1.4-1)'.
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was a...@debian.org).
> usertag 858527 binnmu
There were no usertags set.
Usertags are now: binnmu.
> thanks
Stopping processing here.

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

Bug#858527: samtools: uninstallable in experimental: unsatisfiable Depends: libhts1 (>= 1.4-1)

[Andreas Beckmann]

reassign 858527 release.debian.org
severity 858527 normal
retitle 858527 nmu: samtools_1.4-1
user release.debian@packages.debian.org
usertag 858527 binnmu
thanks

On 2017-03-23 11:15, Andreas Tille wrote:
> Hi Andreas,
> 
> the issue occured unfortunately since I forgot to rename the binary
> package in libhts from libhts1 to libhts2.  I compiled samtools against
> the old (not yet renamed libhts1) and accidentially run dput on it.
> 
> The bug can be fixed by a simply rebuild (binNMU?) of samtools.  How
> can I trigger this?

nmu samtools_1.4-1 . amd64 . experimental . -m "Rebuild against libhts2."

Andreas

Bug#858486: Bug#858486: python-mne: broken symlink: /usr/lib/python2.7/dist-packages/mne/html/d3.v3.min.js -> ../../../../../share/javascript/d3/d3.min.js

[Andreas Tille]

Hi Alexandre,

On Thu, Mar 23, 2017 at 03:17:15PM +0100, Alexandre Gramfort wrote:
> python-mne does need the d3 package so yes one should have the:
> 
> Depends: libjs-d3
> 
> can someone help me fixing this?

I'm just building a package with this fix.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#858430: marked as done (seer: Not all scripts are installed in the binary package)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 14:51:55 +0100
with message-id <20170323135155.gd6...@an3as.eu>
and subject line Closing bug
has caused the Debian Bug report #858430,
regarding seer: Not all scripts are installed in the binary package
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.)


-- 
858430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seer
Severity: grave
Tags: patch
Justification: renders package unusable

Hi,

the seer source contains a set of Perl scripts/*.pl which are only
partially installed into the binary package.  This uselessly restricts
the usefulness of the package for several applications.  Please install
all scripts in the scripts/ dir.

Kind regards

   Andreas.

PS: This is tagged patch since the patch will be propagated right to
the packaging Git.

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

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

for some reason the upload of seer 1.1.2-2 that was intended to
close this bug was lost.  So I'm hereby manually closing the bug.

Sorry for the mess

 Andreas.

- Forwarded message from Debian FTP Masters 
 -

Date: Thu, 23 Mar 2017 13:49:00 +
From: Debian FTP Masters 
To: Debian Med Packaging Team , 
Andreas Tille 
Subject: seer_1.1.2-3_amd64.changes ACCEPTED into unstable



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Mar 2017 14:33:36 +0100
Source: seer
Binary: seer
Architecture: source amd64
Version: 1.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 seer   - genomic sequence element (kmer) enrichment analysis
Changes:
 seer (1.1.2-3) unstable; urgency=medium
 .
   * Better documentation of scripts
Checksums-Sha1:
 da6bd2bd364fa5a0428c5e88b557ae433cfb2236 2033 seer_1.1.2-3.dsc
 80ccc3c7b179eb2de6167f6a1f8768589050ef7d 6868 seer_1.1.2-3.debian.tar.xz
 a72df1d84461e71235dc290effcbe4e1edd94891 7766616 seer-dbgsym_1.1.2-3_amd64.deb
 8304520e4c288c7b56187edc109338a46c2156c3 6760 seer_1.1.2-3_amd64.buildinfo
 f206c747cbf80353bceed00169f70039032f3d1c 397804 seer_1.1.2-3_amd64.deb
Checksums-Sha256:
 06a339be0eff00f62678b528513b02af69354998c710f7f915da86a653a4bd45 2033 
seer_1.1.2-3.dsc
 abfeec77cdbb7ba16454b93e6d6d8bdb4592c7f20dcc2187fbfdea033430da17 6868 
seer_1.1.2-3.debian.tar.xz
 44da37daf0ec92c8e7b2f176a982e6096a8175c9be83ba3a3ddd175f4baf7b13 7766616 
seer-dbgsym_1.1.2-3_amd64.deb
 267671e7315bca1c2e039466c201a5e168830523a04f5682597e81a69f7a9cd5 6760 
seer_1.1.2-3_amd64.buildinfo
 e0677a17be7ae698f5503bfb3189c3e7a277345f9882a637b8cbf7c770bf8515 397804 
seer_1.1.2-3_amd64.deb
Files:
 daf844ada2212ecf9bb475a816d72280 2033 science optional seer_1.1.2-3.dsc
 605901f9ff32ba3052b20cb7e1419ab4 6868 science optional 
seer_1.1.2-3.debian.tar.xz
 b6c9b4370ca6c1e3f1d092c54aa5273d 7766616 debug extra 
seer-dbgsym_1.1.2-3_amd64.deb
 18ffcfcf13b25548965ff5d00803be80 6760 science optional 
seer_1.1.2-3_amd64.buildinfo
 bdf39721735a98887993b117c4d75c05 397804 science optional seer_1.1.2-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAljTz3YRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEeFRAAjCkCTpfKArbqxVijEoayTZDSmC4jrnS8
V7u9I28EKHAS4RR0BAdSjgMzVE55RaG+QUZyw9BHvHDmxVi8jOucqlV40R2iietP
GtrYL13WuDj6I28R88q8jWrdkG8DmqGp9kePJJsLOM9UA+jNGDwfVAfVerQ/GdfY
+PU109LKxNhwR3eVBGUMrc8d4sVN68Aqe3463cYgMLyDe82OHDGBnZaNJcERPCMM
OduDgZ779N7tnoZjIkpwEZU8XWlBsQcUelhd2Qstr/GtcHxiR4G21jwQ28AFXErf
UP8fJui/VerJMr6sk1I8nzKRB86qCps8hXp2ZlpoE0OAJic4s8qSJDyC8Qp6Gq6p
zjJHtmv8j7+FgzCRTZPXpMkRY46+feUYAgOi0HAUWK3sM6pZYG6v4T2+3sQRUpvu
kDY7t7rRXajj3IJ/p95UeKGhD+88SIC5PCAOR/cv4KM2Q8fvVq0cyjEmt/JJOHqr
XRSmyezcLZeU+KvbbZ2So+wsWOcvNdTuUioUy9fcvSFsqa/wr3PuM3TLQLD7G2VD
emMCb3KhY/DM240x7bsxEQ6gsz7cAICDy6Z9A5hLhuYuMucubtTYr5DyGH57qeXK
4zp/cB2eYr6XCfkWGWjTd4Smc3RLU5IanSLYQSMVe6wS31tnlIxexr6ZqZIgi1t2
L9bZBi9Bk1Y=
=A9nE
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___

Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

[Radovan Birdic]

Hi,

I tried to run tests from chroot and all tests executed successfully but 
execution takes a long time:

> real  804m47.257s
> user  43m32.480s
> sys   760m33.150s

On 21/03/17 11:47, Dejan Latinovic wrote:

> One solution could be to blacklist atlc on boards without FPU,
> the other solution could be to disable benchmark.test on MIPS.

I have created and attached a patch which disables this tests.
With this patch package builds successfully, without benchmark.test execution.

Regards,
Radovan--- atlc-4.6.1_orig/debian/rules	2011-12-26 07:50:12.0 +
+++ atlc-4.6.1/debian/rules	2017-03-23 08:40:37.763877641 +
@@ -7,7 +7,7 @@
 # from having to guess our platform (since we know it already)
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-
+DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
 
 CFLAGS = -Wall -g
 
@@ -21,6 +21,10 @@
 endif
 
 config.status: configure
+ifeq ($(DEB_HOST_ARCH_CPU), $(filter $(DEB_HOST_ARCH_CPU), mips mipsel))
+	sed -e '/s*\tbenchmark.test/d' -i tests/Makefile.in
+	sed -e 's/\tWARNING-The-next-test-is-a-benchmark-and-takes-a-long-while.test \\//g' -i tests/Makefile.in
+endif
 	dh_testdir
 	cp -f /usr/share/misc/config.sub config.sub
 	cp -f /usr/share/misc/config.guess config.guess

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

[Kartik Mistry]

On Thu, Mar 23, 2017 at 5:29 PM, Tino Didriksen  wrote:
> On 23 March 2017 at 12:28, Mattia Rizzolo  wrote:
>>
>> > Yes, it will be fixed this month. We've got a strategy that'll work for
>> > the
>> > primary usecases - using little-endian everywhere.
>>
>> Progress?
>>
>> At this point this has been the last package stuck in a library
>> transition (ignoring openssl), and we are in deep freeze.
>>
>> I think a fix is highly overdue.
>
> So sorry, I completely forgot there was a dependency bug. I've committed a
> simple test disabler, because we don't need HFST to pass those tests any
> longer.
>
> The actual issue was fixed in https://bugs.debian.org/824119 - since
> hfst-ospell no longer depends on HFST, HFST doesn't need to run tests.
>
> Kartik, can you push it onwards?

If I understand correctly, I need to push hfst-ospell, right?

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com

Bug#858528: grub-coreboot: fails to upgrade from jessie to stretch if init-select was installed

[Colin Watson]

reassign -1 init-select

On Thu, Mar 23, 2017 at 04:45:33AM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

Your log shows no indication of any file-overwriting problem.  I'm
assuming that this must have been an accident from some analysis script?

> >From the attached log (scroll to the bottom...):
>
>   Setting up grub-coreboot (2.02~beta3-5) ...
>   Installing new version of config file /etc/kernel/postinst.d/zz-update-grub 
> ...
>   Installing new version of config file /etc/kernel/postrm.d/zz-update-grub 
> ...
>   /var/lib/dpkg/info/grub-coreboot.config: 1: 
> /etc/default/grub.d/init-select.cfg: /usr/lib/init-select/get-init: not found
>   dpkg: error processing package grub-coreboot (--configure):
>subprocess installed post-installation script returned error exit status 
> 127

This is a bug in init-select, not in GRUB.
/etc/default/grub.d/init-select.cfg needs to check whether
/usr/lib/init-select/get-init exists before trying to invoke it, because
the package might have been removed but not purged.

(Fixing this properly for upgrades from jessie to stretch may require
updating the package in jessie as well.)

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

Bug#801564: marked as done (squid: prompting due to modified conffiles which were not modified by the user: /etc/squid/squid.conf)

[Debian Bug Tracking System]

Your message dated Fri, 24 Mar 2017 01:45:43 +1300
with message-id 
and subject line Re: squid: prompting due to modified conffiles which were not 
modified by the user: /etc/squid/squid.conf
has caused the Debian Bug report #801564,
regarding squid: prompting due to modified conffiles which were not modified by 
the user: /etc/squid/squid.conf
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.)


-- 
801564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid
Version: 3.5.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Preparing to unpack .../squid-langpack_20150704-1_all.deb ...
  Unpacking squid-langpack (20150704-1) over (20140506-1) ...
  Preparing to unpack .../squid-common_3.5.10-1_all.deb ...
  Unpacking squid-common (3.5.10-1) over (2.7.STABLE9-4.1+deb7u1) ...
  Preparing to unpack .../squid_3.5.10-1_amd64.deb ...
  Unpacking squid (3.5.10-1) over (2.7.STABLE9-4.1+deb7u1) ...

  Setting up squid (3.5.10-1) ...
  Installing new version of config file /etc/init.d/squid ...
  Installing new version of config file /etc/logrotate.d/squid ...
  Installing new version of config file /etc/resolvconf/update-libc.d/squid ...
  
  Configuration file '/etc/squid/squid.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** squid.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
squid (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.19-22) ...
  Processing triggers for systemd (226-4) ...
  Errors were encountered while processing:
   squid


This was observed on the upgrade path wheezy -> jessie -> stretch.
There was no squid package in jessie, so this is effectively
an upgrade from 2.7 to 3.5.

Which also means there is no automatic upgrade path from squid 2.7 in wheezy
to squid3 in jessie!


cheers,

Andreas


squid_3.5.10-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Control: notfixed -1 3.5.12-1
Control: fixed -1 3.5.23-2
Control: notfound -1 3.5.23-2
thanks

This is a new bug, it has never happened before - therefore no
regression. I have opened bug 858556 for tracking the new issue.

It is not involving dpkg prompting the user about config files,
therefore not the same bug. Re-closing.

Amos--- End Message ---

Bug#858556: squid 3.5.23-2: upgrade from jesse squid3 fails

[Amos Jeffries]

Package: squid
Version: 3.5.23-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
stop

From: Andreas Beckmann
Date: Thu, 23 Mar 2017 04:04:15 +0100

Hi,

the last upload introduced a regression:

  Selecting previously unselected package squid.
  (Reading database ...
(Reading database ... 12210 files and directories currently installed.)
  Preparing to unpack .../squid_3.5.23-2_amd64.deb ...
  mv: cannot stat '/etc/squid/squid.conf': No such file or directory
  dpkg: error processing archive
/var/cache/apt/archives/squid_3.5.23-2_amd64.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   /var/cache/apt/archives/squid_3.5.23-2_amd64.deb

This was observed on a jessie -> sid upgrade.

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

[Tino Didriksen]

On 23 March 2017 at 12:28, Mattia Rizzolo  wrote:

> > Yes, it will be fixed this month. We've got a strategy that'll work for
> the
> > primary usecases - using little-endian everywhere.
>
> Progress?
>
> At this point this has been the last package stuck in a library
> transition (ignoring openssl), and we are in deep freeze.
>
> I think a fix is highly overdue.


So sorry, I completely forgot there was a dependency bug. I've committed a
simple test disabler, because we don't need HFST to pass those tests any
longer.

The actual issue was fixed in https://bugs.debian.org/824119 - since
hfst-ospell no longer depends on HFST, HFST doesn't need to run tests.

Kartik, can you push it onwards?

-- Tino Didriksen

Bug#858553: [lazarus-doc-1.6] Package lazarus-doc-1.6 is empty and does not ship documentation files

[Abou Al Montacir]

Package: lazarus-doc-1.6
Version: 1.6.2+dfsg-1
Severity: grave

--- Please enter the report below this line. ---

The package lazarus-doc-1.6 does not ship any documentation file.Running "dpkg
-L lazarus-doc-1.6" (see below) shows that almost nothing was packaged.This
makes this package completely useless and thus the severity grave.
The same command ran on 1.4.4 shows all html files required by Lazarus to
display help when one presses F1 key.
$dpkg -L lazarus-doc-
1.6/./usr/usr/share/usr/share/doc/usr/share/doc/lazarus/usr/share/doc/lazarus/1.
6.2/usr/share/doc/lazarus/1.6.2/images/usr/share/doc/lazarus/1.6.2/images/laztit
le.png/usr/share/doc/lazarus/1.6.2/index.html/usr/share/doc/lazarus/1.6.2/lcl/us
r/share/doc/lazarus/1.6.2/lcl/index-
8.html/usr/share/doc/lazarus/1.6.2/lcl/index.html/usr/share/doc/lazarus/1.6.2/lc
l/inputfile.txt.gz/usr/share/doc/lazarus-doc-1.6/usr/share/doc/lazarus-doc-
1.6/changelog.Debian.gz/usr/share/doc/lazarus-doc-1.6/copyright/usr/share/doc-
base/usr/share/doc-base/lazarus-doc-
1.6/usr/share/lintian/usr/share/lintian/overrides/usr/share/lintian/overrides/la
zarus-doc-1.6
--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-2-amd64

Debian Release: 9.0
  500 unstableriot.im 
  500 testing ftp.fr.debian.org 
  500 stable  repo.skype.com 
  500 stable  dl.google.com 
  500 sid linux.dropbox.com 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
lazarus-ide-1.6| 1.6.2+dfsg-1
-- 
Cheers,
Abou Al Montacir


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

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

[Mattia Rizzolo]

On Sat, Nov 05, 2016 at 12:49:37AM +0100, Tino Didriksen wrote:
> On 4 November 2016 at 20:49, Jonathan Wiltshire  wrote:
> 
> > > > While it did successfully build in the past, that was only because the
> > test
> > > > suite was disabled until recently. The tests revealed the unsigned char
> > > > issue which was easy to fix, and now the endian issue which will not
> > be as
> > > > easy.
> >
> > Any news?
> 
> 
> Yes, it will be fixed this month. We've got a strategy that'll work for the
> primary usecases - using little-endian everywhere.

Progress?

At this point this has been the last package stuck in a library
transition (ignoring openssl), and we are in deep freeze.

I think a fix is highly overdue.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#857995: respawn loop due to insufficient permissions

[Jeremy Bicha]

By the way, the constant respawn is really annoying when I install
stretch on VirtualBox.

I use the latest stretch testing netboot iso to install. Then I need
to boot to a command line with Internet so I can install
virtualbox-guest-x11 from sid (in order to be able to use a graphical
desktop because Debian Security doesn't want VirtualBox in stretch).
But first I have to wait 5 minutes for gdm to stop trying to load
(effectively a Denial of Service) before I can use a virtual terminal.

Thanks,
Jeremy Bicha

Bug#858523: marked as done (libbiod-dev: missing Depends: libbiod0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 10:19:06 +
with message-id 
and subject line Bug#858523: fixed in libbiod 0.1.0-2
has caused the Debian Bug report #858523,
regarding libbiod-dev: missing Depends: libbiod0 (= ${binary:Version})
to be marked as done.

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

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


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

Hi,

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

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

0m27.8s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libbiod.so -> libbiod.so.0


cheers,

Andreas


libbiod-dev_0.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbiod
Source-Version: 0.1.0-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libbiod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Mar 2017 10:47:42 +0100
Source: libbiod
Binary: libbiod0 libbiod-dev
Architecture: source amd64
Version: 0.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libbiod-dev - bioinformatics library in D (development files)
 libbiod0   - bioinformatics library in D
Closes: 858523
Changes:
 libbiod (0.1.0-2) unstable; urgency=medium
 .
   * Add missing Depends: libbiod0 (= ${binary:Version})
 Closes: #858523
Checksums-Sha1:
 9d9f5a4083ec2dccdc140d580b9d0fb8b0ffe492 2056 libbiod_0.1.0-2.dsc
 42f3c7eb04c307acad03c790d56c9b8c7fdd15c0 21148 libbiod_0.1.0-2.debian.tar.xz
 8d35ab72bdd731492d4931f9bec6b6c7fa7cd54a 137238 libbiod-dev_0.1.0-2_amd64.deb
 d0501d968e9b644855986c6460d06ea2db6f2afd 1559764 
libbiod0-dbgsym_0.1.0-2_amd64.deb
 e8982bb806fcf9d64edbedd031acf605c4915abc 450314 libbiod0_0.1.0-2_amd64.deb
 66cb92531e311d83f97335d1262eef10529f4f9a 6540 libbiod_0.1.0-2_amd64.buildinfo
Checksums-Sha256:
 b02439177458025484e1e81cb21f0f465e32b571296a22719c6d26a9b9f4ca50 2056 
libbiod_0.1.0-2.dsc
 6b94bebd74e61166f6c882f34eb37e18316ae04e96d646e73e8151b6bba50608 21148 
libbiod_0.1.0-2.debian.tar.xz
 e60f5b1088e614f8c9a61b84f8d2de4c7139ba56049222920f6c25fe050f4537 137238 
libbiod-dev_0.1.0-2_amd64.deb
 e8f29df7d5399b78dd4e5baa8a48ccc45c40d6b66320e419652f1bdbeeb2bf44 1559764 
libbiod0-dbgsym_0.1.0-2_amd64.deb
 c71df138e34623e13de6fc19794a2197443640a3ccb314dc02b058557dbe4fe2 450314 
libbiod0_0.1.0-2_amd64.deb
 17a0fb1d3c137c8bf8e1824d11dbbfa45a7612a1b71c225fbf4e0ce62bb3d8f2 6540 
libbiod_0.1.0-2_amd64.buildinfo
Files:
 8e7fa30d4945b60cf11b6fe9fae87fd9 2056 science optional libbiod_0.1.0-2.dsc
 1c2792aee03b214f96919acbb47012bd 21148 science optional 
libbiod_0.1.0-2.debian.tar.xz
 d174e34077acbb4bf8acd2c832c1f6f3 137238 libdevel optional 
libbiod-dev_0.1.0-2_amd64.deb
 a717acfc064c93404a8e1c7bbcca63b3 1559764 debug extra 
libbiod0-dbgsym_0.1.0-2_amd64.deb
 e5eeb28d13cb1a686763fb6191b7f737 450314 science optional 
libbiod0_0.1.0-2_amd64.deb
 e90f1d798482b4b752091d8e209f20a7 6540 science optional 
libbiod_0.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAljTnswOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEqhg//bFnGnC+kWBclPyEV7RZ9XZoc6UxG8L5TBkyx
Q7VaxA/OzZ809+iwbJvfR2H+bIN54xYSyjaOSYka/9qdZbt20SbRkQzWbI33G1sm
7yclE2PQxGdW+FAZ7aj74R1q8w4o07qXY/YFy8EQbv+jQgcRZsz6NOUhEzYF7xRR
uxIEwN7SNQfuCHyL9QFR0fE/ipSbpYHrIgBMSivIzY+KVm8FwFjp5Uv3E1ZS6eht
UM5mTUuS409BzxRpmBZtTUCvm8eCGwJ78bKN/ngl5lrGue/AZbrA/Bd5moEvh5Nf
1CkmWPige0UcB0xqz3E1QQFHxwUxOBflwCDBYOnST+wNVZ6vC2fOP79008pc9/Px
eYJbzpZv2+ppNpTPwZf0X42cmYjGEnGT4+c/pFT1ALbk2KeDplLIC5mKInuXOJzv
bVAuiD5rgZ6pI+7fEf2zxmUbEnagTzJ+DS2cYlSr0JJ6/V1JB5y1f0BcgrCNgXIU

Bug#858527: samtools: uninstallable in experimental: unsatisfiable Depends: libhts1 (>= 1.4-1)

[Andreas Tille]

Hi Andreas,

the issue occured unfortunately since I forgot to rename the binary
package in libhts from libhts1 to libhts2.  I compiled samtools against
the old (not yet renamed libhts1) and accidentially run dput on it.

The bug can be fixed by a simply rebuild (binNMU?) of samtools.  How
can I trigger this?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#858537: marked as done (apt: Cannot install openjdk-8-jre-headless b/c breaks ca-certificates-java. Sec update?)

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 11:08:13 +0100
with message-id <20170323100813.w3tae7j5u7lt36j7@crossbow>
and subject line Re: Bug#858537: apt: Cannot install openjdk-8-jre-headless b/c 
breaks ca-certificates-java. Sec update?
has caused the Debian Bug report #858537,
regarding apt: Cannot install openjdk-8-jre-headless b/c breaks 
ca-certificates-java. Sec update?
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.)


-- 
858537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.0.9.8.4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Attempting to install openjdk-8-jre

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Ran the command "sudo apt install openjdk-8-jre"

   * What was the outcome of this action?
The following packages have unmet dependencies:
 openjdk-8-jre : Depends: openjdk-8-jre-headless (= 
8u121-b13-1~bpo8+1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


In an attempt to diagnose the issue, I manually attempted installation of unmet 
dependencies until I reached the bottom
of the 'stack', so to speak. I received the following error which I beleive 
concisely explains the issue:

The following packages have unmet dependencies:
 openjdk-8-jre-headless : Breaks: ca-certificates-java (< 
20160321~) but 20140324 is to be installed
E: Unable to correct problems, you have held broken packages.

So I'm guessing there was a security or otherwise major update, only two days 
ago, and the repository hasn't caught up yet.
I apologize if this bug report is at all misconfigured, this is my first.
I would assume a simple workaround would be to manually install 
ca-certificates-java v20160321 but I have not tried that myself.

Thanks for the awesome distro!

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.16\.0-4-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged 

Bug#857343: (no subject)

[Fabrice Dagorn]

Dear Maintainer,
it's a serious security bug IMO, feel free to switch back to important 
if you disagree.

Processed: update dependency, version

[Debian Bug Tracking System]

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

> block 857360 by 858163
Bug #857360 [gitlab] gitlab: Fails to install in Stretch
857360 was blocked by: 854658
857360 was not blocking any bugs.
Added blocking bug(s) of 857360: 858163
> retitle 858163 unblock: gitlab/8.13.11+dfsg-7
Bug #858163 [release.debian.org] unblock: gitlab/8.13.11+dfsg-6
Changed Bug title to 'unblock: gitlab/8.13.11+dfsg-7' from 'unblock: 
gitlab/8.13.11+dfsg-6'.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 857343 serious
Bug #857343 [liblogback-java] liblogback-java: logback < 1.2.0 has a 
vulnerability in SocketServer and ServerSocketReceiver
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#858494: marked as done (open-vm-tools-dev: missing Depends: open-vm-tools (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Thu, 23 Mar 2017 09:04:08 +
with message-id 
and subject line Bug#858494: fixed in open-vm-tools 2:10.1.5-5055683-2
has caused the Debian Bug report #858494,
regarding open-vm-tools-dev: missing Depends: open-vm-tools (= 
${binary:Version})
to be marked as done.

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

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


-- 
858494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-vm-tools-dev
Version: 2:10.1.5-5055683-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m22.9s ERROR: FAIL: Broken symlinks:
  /usr/lib/libvmtools.so -> libvmtools.so.0.0.0
  /usr/lib/libvgauth.so -> libvgauth.so.0.0.0
  /usr/lib/libhgfs.so -> libhgfs.so.0.0.0
  /usr/lib/libguestlib.so -> libguestlib.so.0.0.0
  /usr/lib/libDeployPkg.so -> libDeployPkg.so.0.0.0

BTW, why aren't these libraries in one (or more) lib* packages?

Please check the reverse build-depends of open-vm-tools-dev,
these will have linked against the static libraries and need binNMUs.


cheers,

Andreas


open-vm-tools-dev_2:10.1.5-5055683-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: open-vm-tools
Source-Version: 2:10.1.5-5055683-2

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated open-vm-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Mar 2017 09:35:16 +0100
Source: open-vm-tools
Binary: open-vm-tools open-vm-tools-desktop open-vm-tools-dev open-vm-tools-dkms
Architecture: source amd64 all
Version: 2:10.1.5-5055683-2
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Description:
 open-vm-tools - Open VMware Tools for virtual machines hosted on VMware (CLI)
 open-vm-tools-desktop - Open VMware Tools for virtual machines hosted on 
VMware (GUI)
 open-vm-tools-dev - Open VMware Tools for virtual machines hosted on VMware 
(developm
 open-vm-tools-dkms - Open VMware Tools vmxnet kernel module (deprecated)
Closes: 856569 858494
Changes:
 open-vm-tools (2:10.1.5-5055683-2) unstable; urgency=medium
 .
   * [651cdfe] Depend on iproute2.
 Necessary for /etc/vmware-tools/scripts/vmware/network.
   * [ed95c1d] Depend on libssl1.0-dev | libssl-dev.
 Thanks to Tiago Daitx (Closes: #856569)
 Makes building the package in Ubuntu easier.
   * [2750700] Add o-v-t as dependency of o-v-t-dev.
 Thanks to Andreas Beckmann (Closes: #858494)
Checksums-Sha1:
 af83e666b7ac998f6478061df55b5576f33ef0d8 2502 
open-vm-tools_10.1.5-5055683-2.dsc
 0aec64f3e63cd90709d099973a7be52a04e38815 25072 
open-vm-tools_10.1.5-5055683-2.debian.tar.xz
 ce0583988d0aee002c4e5f44a3e98733afe56545 1999848 
open-vm-tools-dbgsym_10.1.5-5055683-2_amd64.deb
 8dd8d58a64eb4e38273c0ef833848d722a03cb61 197600 
open-vm-tools-desktop-dbgsym_10.1.5-5055683-2_amd64.deb
 1b3c5e8245f2096f500ca57c8992cb5466e15d8a 165458 
open-vm-tools-desktop_10.1.5-5055683-2_amd64.deb
 5a7ffa31419e6255988663c71de47a326f1f0244 498156 
open-vm-tools-dev_10.1.5-5055683-2_amd64.deb
 c309eb7bdbe8533dce8231b6f279ae64c3d348c6 417872 
open-vm-tools-dkms_10.1.5-5055683-2_all.deb
 d09d1c21ae88a3522dc69ad74726c48102e00e33 13717 
open-vm-tools_10.1.5-5055683-2_amd64.buildinfo
 5d370947eb915fed374a5eb145dac6a4db4ae3bc 560766 
open-vm-tools_10.1.5-5055683-2_amd64.deb
Checksums-Sha256:
 5f8e8a7f1441540f414818172139e1e07a2318088bf9c23f0741b063b45ebbe5 2502 
open-vm-tools_10.1.5-5055683-2.dsc
 7477e02cf2650d3268a3ca61530579764b04877b7321b8018a7a76395856d067 25072 
open-vm-tools_10.1.5-5055683-2.debian.tar.xz
 d98f786160a8b185f2f084836d19bdb34ad896cc21ded8c4d52c29bc453792d2 1999848 
open-vm-tools-dbgsym_10.1.5-5055683-2_amd64.deb
 

Bug#858540: barbican: FTBFS: ImportError: No module named vine.five

[Chris Lamb]

Source: barbican
Version: 1:3.0.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

barbican fails to build from source in unstable/amd64:

  […]
  
  ==
  FAIL: 
barbican.tests.queue.test_keystone_listener.WhenUsingMessageServer.test_keystone_notification_config_used
  
barbican.tests.queue.test_keystone_listener.WhenUsingMessageServer.test_keystone_notification_config_used
  --
  _StringException: Empty attachments:
pythonlogging:''
stderr
stdout
  
  Traceback (most recent call last):
File "barbican/tests/queue/test_keystone_listener.py", line 267, in setUp
  queue.init(self.conf)
File "barbican/queue/__init__.py", line 51, in init
  TRANSPORT = messaging.get_transport(conf, allowed_remote_exmods=exmods)
File "/usr/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 
192, in get_transport
  invoke_kwds=kwargs)
File "/usr/lib/python2.7/dist-packages/stevedore/driver.py", line 46, in 
__init__
  verify_requirements=verify_requirements,
File "/usr/lib/python2.7/dist-packages/stevedore/named.py", line 69, in 
__init__
  verify_requirements)
File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 171, 
in _load_plugins
  self._on_load_failure_callback(self, ep, err)
File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 163, 
in _load_plugins
  verify_requirements,
File "/usr/lib/python2.7/dist-packages/stevedore/named.py", line 146, in 
_load_one_plugin
  verify_requirements,
File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 191, 
in _load_one_plugin
  plugin = ep.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2297, in resolve
  module = __import__(self.module_name, fromlist=['__name__'], level=0)
File 
"/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 
30, in 
  import kombu.connection
File "/usr/lib/python2.7/dist-packages/kombu/connection.py", line 15, in 

  from kombu import exceptions
File "/usr/lib/python2.7/dist-packages/kombu/exceptions.py", line 8, in 

  from kombu.five import python_2_unicode_compatible
File "/usr/lib/python2.7/dist-packages/kombu/five.py", line 6, in 
  import vine.five
  ImportError: No module named vine.five
  
  
  ==
  FAIL: 
barbican.tests.queue.test_keystone_listener.WhenUsingMessageServer.test_keystone_notification_pool_size_used
  
barbican.tests.queue.test_keystone_listener.WhenUsingMessageServer.test_keystone_notification_pool_size_used
  --
  _StringException: Empty attachments:
pythonlogging:''
stderr
stdout
  
  Traceback (most recent call last):
File "barbican/tests/queue/test_keystone_listener.py", line 267, in setUp
  queue.init(self.conf)
File "barbican/queue/__init__.py", line 51, in init
  TRANSPORT = messaging.get_transport(conf, allowed_remote_exmods=exmods)
File "/usr/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 
192, in get_transport
  invoke_kwds=kwargs)
File "/usr/lib/python2.7/dist-packages/stevedore/driver.py", line 46, in 
__init__
  verify_requirements=verify_requirements,
File "/usr/lib/python2.7/dist-packages/stevedore/named.py", line 69, in 
__init__
  verify_requirements)
File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 171, 
in _load_plugins
  self._on_load_failure_callback(self, ep, err)
File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 163, 
in _load_plugins
  verify_requirements,
File "/usr/lib/python2.7/dist-packages/stevedore/named.py", line 146, in 
_load_one_plugin
  verify_requirements,
File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 191, 
in _load_one_plugin
  plugin = ep.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2297, in resolve
  module = __import__(self.module_name, fromlist=['__name__'], level=0)
File 
"/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 
30, in 
  import kombu.connection
File "/usr/lib/python2.7/dist-packages/kombu/connection.py", line 15, in 

  from kombu import exceptions
File "/usr/lib/python2.7/dist-packages/kombu/exceptions.py", line 8, in 

  from kombu.five import python_2_unicode_compatible
File "/usr/lib/python2.7/dist-packages/kombu/five.py", line 6, in 
  import vine.five
  ImportError: No module named vine.five
  
  
  

Bug#858537: apt: Cannot install openjdk-8-jre-headless b/c breaks ca-certificates-java. Sec update?

[D. Scott Boggs]

Package: apt
Version: 1.0.9.8.4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Attempting to install openjdk-8-jre

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Ran the command "sudo apt install openjdk-8-jre"

   * What was the outcome of this action?
The following packages have unmet dependencies:
 openjdk-8-jre : Depends: openjdk-8-jre-headless (= 
8u121-b13-1~bpo8+1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


In an attempt to diagnose the issue, I manually attempted installation of unmet 
dependencies until I reached the bottom
of the 'stack', so to speak. I received the following error which I beleive 
concisely explains the issue:

The following packages have unmet dependencies:
 openjdk-8-jre-headless : Breaks: ca-certificates-java (< 
20160321~) but 20140324 is to be installed
E: Unable to correct problems, you have held broken packages.

So I'm guessing there was a security or otherwise major update, only two days 
ago, and the repository hasn't caught up yet.
I apologize if this bug report is at all misconfigured, this is my first.
I would assume a simple workaround would be to manually install 
ca-certificates-java v20160321 but I have not tried that myself.

Thanks for the awesome distro!

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.16\.0-4-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "3";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-9";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: 

Processed: Bug#857651 marked as pending

[Debian Bug Tracking System]

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

> tag 857651 pending
Bug #857651 {Done: Sebastian Ramacher } [src:audiofile] 
Multiple security issues
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#857651: marked as pending

[Sebastian Ramacher]

tag 857651 pending
thanks

Hello,

Bug #857651 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:


http://anonscm.debian.org/git/pkg-multimedia/audiofile.git/commit/?id=242f019

---
commit 242f0192363e1c3148116d58942ad2624a311425
Author: Salvatore Bonaccorso 
Date:   Sat Mar 18 19:28:56 2017 +0100

Import Debian changes 0.3.6-2+deb8u2

audiofile (0.3.6-2+deb8u2) jessie-security; urgency=high

  * Non-maintainer upload by the Security Team.
  * Address several vulnerabilities (Closes: #857651)
- Always check the number of coefficients (CVE-2017-6827 CVE-2017-6828
  CVE-2017-6832 CVE-2017-6833 CVE-2017-6835 CVE-2017-6837)
- clamp index values to fix index overflow in IMA.cpp (CVE-2017-6829)
- Check for multiplication overflow in sfconvert (CVE-2017-6830
  CVE-2017-6834 CVE-2017-6836 CVE-2017-6838)
- Actually fail when error occurs in parseFormat (CVE-2017-6831)
- Check for multiplication overflow in MSADPCM decodeSample
  (CVE-2017-6839)
  * Fix signature of multiplyCheckOverflow. It returns a bool, not an int
  * Check for division by zero in BlockCodec::runPull

diff --git a/debian/changelog b/debian/changelog
index 9f9f1f2..9819ae1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+audiofile (0.3.6-2+deb8u2) jessie-security; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * Address several vulnerabilities (Closes: #857651)
+- Always check the number of coefficients (CVE-2017-6827 CVE-2017-6828
+  CVE-2017-6832 CVE-2017-6833 CVE-2017-6835 CVE-2017-6837)
+- clamp index values to fix index overflow in IMA.cpp (CVE-2017-6829)
+- Check for multiplication overflow in sfconvert (CVE-2017-6830
+  CVE-2017-6834 CVE-2017-6836 CVE-2017-6838)
+- Actually fail when error occurs in parseFormat (CVE-2017-6831)
+- Check for multiplication overflow in MSADPCM decodeSample
+  (CVE-2017-6839)
+  * Fix signature of multiplyCheckOverflow. It returns a bool, not an int
+  * Check for division by zero in BlockCodec::runPull
+
+ -- Salvatore Bonaccorso   Sat, 18 Mar 2017 19:28:56 +0100
+
 audiofile (0.3.6-2+deb8u1) jessie; urgency=high
 
   * Team upload.

Bug#858521: diaspora-common: does 'rm -rf /' on purge

[Andreas Henriksson]

Hello!

On Thu, Mar 23, 2017 at 02:17:28AM +0100, Andreas Beckmann wrote:
> Package: diaspora-common
> Version: 0.6.3.0+debian3
> Severity: critical
> Justification: breaks the whole system
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package makes havoc in the
> chroot.
[...]
> This very much looks like an 'rm -rf /' in the chroot ... rm is gone, sh is 
> gone, ...

Looks like it does 'rm -rf /bin' to me.

Here's a completely untested patch which should hopefully prevent
disaster. Testing help welcome.

The package is still very likely RC buggy though. This patch just tries
to avoid the disaster of hosing the system.

(Consider for example the case where you already have a user named
"diaspora", making the install fail and then disaster again strikes
when you try to remove/purge your way out of the failed install removing
the user and all its data. Just one example out of many. Nowhere does it
seem to account for conffiles having been removed by the admin as another
example. These maintainer scripts are just waay to buggy/unreliable.)

HTH

Regards,
Andreas Henriksson
diff -uri diaspora-installer-0.6.3.0+debian3.orig/debian/diaspora-common.postrm diaspora-installer-0.6.3.0+debian3/debian/diaspora-common.postrm
--- diaspora-installer-0.6.3.0+debian3.orig/debian/diaspora-common.postrm	2017-03-20 14:15:32.0 +0100
+++ diaspora-installer-0.6.3.0+debian3/debian/diaspora-common.postrm	2017-03-23 08:42:46.277478171 +0100
@@ -6,6 +6,9 @@
 # Abort if any command returns an error value
 set -e
 
+# Abort if any unbound variables are used
+#set -u
+
 # This script is called twice during the removal of the package; once
 # after the removal of the package's files from the system, and as
 # the final step in the removal of this package, after the package's
@@ -13,6 +16,17 @@
 
 # Ensure the menu system is updated
 
+# defaults as shipped in /etc/diaspora/diaspora-common.conf
+diaspora_home=/usr/share/diaspora
+diaspora_user=diaspora
+#diaspora_user_home="$(getent passwd ${diaspora_user} | cut -d: -f6)"
+diaspora_user_home=/var/lib/diaspora
+
+# Source variables (if conffile still exists)
+if [ -f /etc/diaspora/diaspora-common.conf ]; then
+  . /etc/diaspora/diaspora-common.conf
+fi
+
 case "$1" in
   remove)
 # This package is being removed, but its configuration has not yet
@@ -52,6 +66,11 @@
 	ucf --purge /etc/dbconfig-common/diaspora-common.conf
 	ucfr --purge diaspora-common /etc/dbconfig-common/diaspora-common.conf
 	fi
+
+# safety check
+[ "${diaspora_user_home}" != "" ] || exit 1
+[ "${diaspora_home}" != "" ] || exit 1
+
 rm -rf ${diaspora_user_home}/public
 rm -rf ${diaspora_user_home}/app-assets
 rm -rf ${diaspora_user_home}/Gemfile.lock
@@ -61,8 +80,8 @@
 rm -rf ${diaspora_home}/db
 rm -rf ${diaspora_home}/bin
 rm -rf /var/cache/diaspora /var/log/diaspora
-echo "Removing user: diaspora"
-id -u diaspora && userdel -r diaspora
+echo "Removing user: ${diaspora_user}"
+id -u ${diaspora_user} && userdel -r ${diaspora_user}
   fi
 
   # Remove my changes to the db.

Processed: tor: time bomb in unit tests

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugs.torproject.org/21799
Bug #858534 [tor] tor: time bomb in unit tests
Set Bug forwarded-to-address to 'https://bugs.torproject.org/21799'.

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

Bug#858534: tor: time bomb in unit tests

[Peter Palfrader]

Package: tor
Version: 0.3.0.4-rc-1
Severity: serious
Control: forwarded -1 https://bugs.torproject.org/21799

There is a time-bomb in the Tor unit tests that make them fail
as of a few days ago, causing the package to FTBFS.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#857748: [request-tracker-maintainers] Bug#857748: Please package current version - 1.02

[Satoru KURASHIKI]

hi,

Release team,

In the later stage of freeze, are there any chance to upload newer
upstream version (into testing) to fix RC bugs?
If it can, I will finish staged git chages as soon as I can.

(This package is leaf plugin for request-tracker, so any other
r/depeds will not affect.)

regards,

On Fri, Mar 17, 2017 at 7:12 AM, Dominic Hargreaves  wrote:
> Control: severity -1 serious
>
> On Tue, Mar 14, 2017 at 07:25:32PM +0300, Max Kosmach wrote:
>> X-Debbugs-CC: pkg-request-tracker-maintain...@lists.alioth.debian.org
>> Package: rt4-extension-customfieldsonupdate
>> Version: 0.01-1.1
>>
>> Please package current version (1.02) which is compatible with RT 4.2 and RT 
>> 4.4
>
> Hi Max,
>
> Thanks for raising this issue. From the changelog I take it that 0.0.1
> doesn't support 4.2 or 4.4 at all. Is that your understanding too?
>
> As such this is RC for both jessie and stretch, so raising the
> severity appropriately.
>
> Dominic.



-- 
KURASHIKI Satoru