Processed: Fixed!

[Debian Bug Tracking System]

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

> tag 870775 + fixed-upstream
Bug #870775 [boxbackup] boxbackup: Please migrate to openssl1.1 in Buster
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Processed: tagging 886119

[Debian Bug Tracking System]

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

> tags 886119 + pending
Bug #886119 [src:e2fsprogs] e2fsprogs: FTBFS on big-endian architectures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882934: pcb-gtk crash

[Dima Kogan]

Hi.

Let's try to get to the bottom of this. Are you still experiencing the
crash?

My suspicion is that you have some shared library installed that's
incompatible with some other component. You say you upgrade the whole
system regularly?

I'd like to see the list of shared libraries your pcb-gtk is depending
on. What does this say:

  ldd /usr/bin/pcb-gtk

It'd also be interesting to get the list of all the packages that
provide those dependencies. What does this say:

  ldd /usr/bin/pcb-gtk | awk '{print $3}' | sort | uniq | xargs dpkg -S | awk 
-F: '!/diversion/ {print $1}' | xargs dpkg -l

Past that, I'd like to get a core. If that doesn't work, we can bring
out bigger guns, but hopefully this would be enough. Please do this:

1. ulimit -c unlimited
2. cat /proc/sys/kernel/core_pattern
   This should be "core" or "core.something". If it isn't, please write
   "core" into that file, as root. This is non-permanent and would be
   reset to whatever it was when you reboot.
3. In the same shell, invoke pcb-gtk, and trigger the crash

The kernel should dump a file named "core" into your current directory.
If I could get a copy of that file, that'd be very useful. It might be
quite large so maybe emailing that wouldn't be ideal. Maybe hold off on
this, and just send me the output of the two ldd commands above.

Thanks much for helping us debug!

dima

Bug#880036: avahi: FTBFS: dh_systemd_start: Could not open avahai-daemon.socket

[Steve Langasek]

Package: avahi
Followup-For: Bug #880036
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Hello,

I agree with the analysis given at .

The fix for this build failure is straightforward; just drop the Also= line,
which is not needed and has wrong side-effects.

The attached patch, which implements this, has been uploaded to Ubuntu. 
Please consider applying it to Debian as well.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru avahi-0.7/debian/patches/no-systemd-also.patch 
avahi-0.7/debian/patches/no-systemd-also.patch
--- avahi-0.7/debian/patches/no-systemd-also.patch  1969-12-31 
16:00:00.0 -0800
+++ avahi-0.7/debian/patches/no-systemd-also.patch  2018-01-02 
17:27:56.0 -0800
@@ -0,0 +1,18 @@
+Description: Don't use 'Also=' in dnsconfd systemd unit
+ 'Also=avahi-daemon.socket' means that 'systemctl disable avahi-dnsconfd'
+ will also disable avahi-daemon.socket, which is definitely not what we
+ want, and it also causes debhelper to throw an error.  Just drop this entry
+ from the configuration.
+Author: Steve Langasek 
+Last-Modified: 2018-01-02 20:30:00 -0800
+Bug-Debian: https://bugs.debian.org/878911
+
+Index: avahi-0.7-3ubuntu1/avahi-dnsconfd/avahi-dnsconfd.service.in
+===
+--- avahi-0.7-3ubuntu1.orig/avahi-dnsconfd/avahi-dnsconfd.service.in
 avahi-0.7-3ubuntu1/avahi-dnsconfd/avahi-dnsconfd.service.in
+@@ -26,4 +26,3 @@
+ 
+ [Install]
+ WantedBy=multi-user.target
+-Also=avahi-daemon.socket
diff -Nru avahi-0.7/debian/patches/series avahi-0.7/debian/patches/series
--- avahi-0.7/debian/patches/series 2017-09-18 14:25:27.0 -0700
+++ avahi-0.7/debian/patches/series 2018-01-02 17:27:56.0 -0800
@@ -1,3 +1,4 @@
 fix-manpage-install-conditions.patch
 man-add-missing-bshell.1-symlink.patch
 man-fix-reference-to-avahi-autoipd.action-8-in-avahi-auto.patch
+no-systemd-also.patch

Processed: tagging 885295

[Debian Bug Tracking System]

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

> tags 885295 + pending
Bug #885295 [src:gpodder] gpodder: Depends on unmaintained pygtk
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 885295

[Debian Bug Tracking System]

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

> tags 885295 + fixed-upstream
Bug #885295 [src:gpodder] gpodder: Depends on unmaintained pygtk
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#862799: marked as done (torbrowser-launcher: missing dependencies on libasound2 libdbus-glib-1-2 and libevent-2.0-5)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 04:04:24 +
with message-id 
and subject line Bug#862799: fixed in torbrowser-launcher 0.2.8-6
has caused the Debian Bug report #862799,
regarding torbrowser-launcher: missing dependencies on libasound2 
libdbus-glib-1-2 and libevent-2.0-5
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.)


-- 
862799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.6-3.1
Severity: normal

rjc@stretch386:~/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser$ 
./firefox --class 'Tor Browser' -profile TorBrowser/Data/Browser/profile.default
XPCOMGlueLoad error for file 
/home/rjc/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser/libxul.so:
libasound.so.2: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

I got the above error trying to load firefox from the torbrowser (latest
version just downloaded), I had to install libasound2 to fix it.

rjc@stretch386:~/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser$ 
./firefox --class 'Tor Browser' -profile TorBrowser/Data/Browser/profile.default
XPCOMGlueLoad error for file 
/home/rjc/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser/libxul.so:
libdbus-glib-1.so.2: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

Then I got the above error and needed to install libdbus-glib-1-2.

rjc@stretch386:~/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser$ 
./firefox --class 'Tor Browser' -profile TorBrowser/Data/Browser/profile.default
1495008967200   addons.xpi-utilsERROR   Unable to read anything useful 
from the database
/home/rjc/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser/TorBrowser/Tor/tor:
 error while loading shared libraries: libevent-2.0.so.5: cannot open shared 
object file: No such file or directory

Then I got the above and needed to install libevent-2.0-5.

These errors won't be apparent when running torbrowser on a system with a full
GUI desktop environment.  But if you want to run "ssh -X minimalsystem" to run
it then it happens.  So I think that the torbrowser-launched package should
depend on those packages.

After installing those packages I get the following error, so it still doesn't
work.  But at least adding these dependencies should stop breakage in some
situations and give users less problems to debug.

jc@stretch386:~/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser$ 
./firefox --class 'Tor Browser' -profile TorBrowser/Data/Browser/profile.default
/home/rjc/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser/TorBrowser/Tor/tor:
 symbol lookup error: 
/home/rjc/.local/share/torbrowser/tbb/i686/tor-browser_en-US/Browser/TorBrowser/Tor/tor:
 undefined symbol: SSL_CIPHER_find


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386
 (i686)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates  20161130
ii  gnupg2.1.18-6
ii  python-gtk2  2.24.0-5.1
ii  python-lzma  0.5.3-3
ii  python-parsley   1.2-1
ii  python-psutil5.0.1-1
ii  python-twisted   16.6.0-2
ii  python-txsocksx  1.15.0.2-1
pn  python:any   
ii  wmctrl   1.07-7+b1

Versions of packages torbrowser-launcher recommends:
pn  tor  

Versions of packages torbrowser-launcher suggests:
pn  apparmor   
pn  python-pygame  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: torbrowser-launcher
Source-Version: 0.2.8-6

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated torbrowser-launcher 
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, 03 Jan 2018 12:38:

Bug#885626: QScintilla2 Transition Started

[Scott Kitterman]

Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, so 
I've just raised the bug to severity serious.  If you haven't already, please 
let me know if you intend to upload, otherwise I'll NMU in the next few days.

Scott K

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

Processed: severity of 885647 is serious

[Debian Bug Tracking System]

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

> severity 885647 serious
Bug #885647 [src:universalindentgui] src:universalindentgui: Will FTBFS with 
new qscintilla2 in experimental
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: severity of 885631 is serious

[Debian Bug Tracking System]

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

> severity 885631 serious
Bug #885631 [src:juffed] src:juffed: Will FTBFS with new qscintilla2
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: severity of 885626 is serious

[Debian Bug Tracking System]

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

> severity 885626 serious
Bug #885626 [src:sonic-pi] src:sonic-pi: Will FTBFS with new qscintilla2
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: severity of 885635 is serious

[Debian Bug Tracking System]

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

> severity 885635 serious
Bug #885635 [src:sqlitebrowser] src:sqlitebrowser: Will FTBFS with new 
qscintilla2
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: severity of 885644 is serious

[Debian Bug Tracking System]

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

> severity 885644 serious
Bug #885644 [src:ovito] src:ovito: Configure failure with new qscintilla2 in 
experimental
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: severity of 885643 is serious

[Debian Bug Tracking System]

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

> severity 885643 serious
Bug #885643 [src:tora] src:tora: Will FTBFS with qscintilla2 in experimental
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#886209: FTBFS: configure: error: please install and enable pecl/raphf

[Adam Borowski]

Source: php-pecl-http
Version: 3.1.0+2.6.0-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build on current unstable:

checking whether ext/raphf is enabled... no
configure: error: please install and enable pecl/raphf
cd build-7.1 && tail -v -n \+0 config.log
==> config.log <==

Tried on armhf amd64.  Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


php-pecl-http_armhf.build
Description: inode/symlink

Bug#886204: FTBFS: Vector.h:251:64: error: no matching function for call

[Adam Borowski]

Source: android-platform-build
Version: 1:7.0.0+r33-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build on current unstable:

In file included from tools/zipalign/ZipFile.h:24:0,
 from tools/zipalign/ZipAlign.cpp:20:
/usr/include/android/utils/Vector.h: In member function 'const 
android::Vector& android::Vector::operator=(const 
android::Vector&) const':
/usr/include/android/utils/Vector.h:251:64: error: no matching function for 
call to 'android::Vector::operator=(const android::VectorImpl&) const'
 VectorImpl::operator = (static_cast(rhs));
^
See also https://bugs.debian.org/886122 in android-platform-frameworks-base

Tried on armhf amd64.  Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


android-platform-build_armhf.build
Description: inode/symlink

Bug#886203: FTBFS: dh: unable to load addon scour

[Adam Borowski]

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

Hi!
I'm afraid that your package fails to build on current unstable:

dh clean --parallel --with=autotools_dev,scour
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh: The autotools-dev sequence is deprecated and replaced by dh in debhelper 
(>= 9.20160115)
dh: This feature will be removed in compat 12.
dh: unable to load addon scour: Can't locate Debian/Debhelper/Sequence/scour.pm 
in @INC (you may need to install t
he Debian::Debhelper::Sequence::scour module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.
26.1 /usr/local/share/perl/5.26.1 /usr/lib/arm-linux-gnueabihf/perl5/5.26 
/usr/share/perl5 /usr/lib/arm-linux-gnue
abihf/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl 
/usr/lib/arm-linux-gnueabihf/perl-base) at (eval 3) 
line 1.
BEGIN failed--compilation aborted at (eval 3) line 1.

Tried on armhf amd64.  Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


wavbreaker_armhf.build
Description: inode/symlink

Bug#886202: FTBFS: chown: cannot access '.../fcoll_8cpp__incl.dot': No such file or directory

[Adam Borowski]

Source: zipios++
Version: 0.1.5.9+cvs.2007.04.28-10
Severity: serious
Justification: fails to build from source

Hi!
I'm afraid your package fails to build on current unstable:

   dh_fixperms
chown: cannot access 
'debian/libzipios++-doc/usr/share/doc/libzipios++-doc/html/fcoll_8cpp__incl.dot':
 No such file or directory
dh_fixperms: find debian/libzipios++-doc -true -print0 2>/dev/null | xargs -0r 
chown --no-dereference 0:0 returned exit code 123
dh_fixperms: Aborting due to earlier error

Tried on armhf amd64.  Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#886200: FTBFS: XPA$ERROR: invalid host name specified: $host:$port.

[Adam Borowski]

Source: xpa
Version: 2.1.18-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build on current unstable:

debian/tests/xpa_test_build
XPA$ERROR: invalid host name specified: $host:$port.
XPA$ERROR no 'xpaset' access points match template: xpa
debian/rules:17: recipe for target 'override_dh_auto_test' failed

Tried on armhf amd64.  Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


xpa_armhf.build
Description: inode/symlink

Bug#886024: split off anything-el related part

[H.-Dirk Schmitt]

On Mi, 2018-01-03 at 02:06 +0200, era eriksson wrote:
> Code outline for an emacs batch wrapper
   

I do not insist on bash – you are free to fix it in any programming
language ;-)



-- 




  
  

  Signature H.-Dirk Schmitt



  

  

  H.-Dirk Schmitt
  

  Dipl.Math.

  eMail:dirk.schm...@computer42.org
  

  mobile:+49 177 616 8564
  

  phone: +49 2642 99 41 14
  

  fax: +49 2642 99 41 15
  

  Schillerstr. 42, D-53489 Sinzig

  pgp: http://www.computer42.org/~dirk/OpenPGP-fingerprint.html

Bug#886198: streamtuner: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: streamtuner2
Version: 2.2.0-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

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

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Re: guake: depends on vte which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/Guake/guake/issues/1009
Bug #790176 [src:guake] guake: depends on vte which is deprecated
Set Bug forwarded-to-address to 'https://github.com/Guake/guake/issues/1009'.

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

Bug#790176: guake: depends on vte which is deprecated

[Jeremy Bicha]

Control: forwarded -1 https://github.com/Guake/guake/issues/1009

Processed: reassign 886153 to emacs25, severity of 886153 is important

[Debian Bug Tracking System]

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

> reassign 886153 emacs25
Bug #886153 [anything-el] anything-el:  A stale file lock of 
anything-c-adaptive-history breaks emacs batch processing
Bug reassigned from package 'anything-el' to 'emacs25'.
No longer marked as found in versions anything-el/1.287-2.1.
Ignoring request to alter fixed versions of bug #886153 to the same values 
previously set
> severity 886153 important
Bug #886153 [emacs25] anything-el:  A stale file lock of 
anything-c-adaptive-history breaks emacs batch processing
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: bug 886153 is forwarded to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29955

[Debian Bug Tracking System]

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

> forwarded 886153 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29955
Bug #886153 [anything-el] anything-el:  A stale file lock of 
anything-c-adaptive-history breaks emacs batch processing
Set Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29955'.
> thanks
Stopping processing here.

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

Bug#864337: marked as done (python-blessed: Non-determistically FTBFS due to unreliable timing in tests)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 00:50:09 +
with message-id 
and subject line Bug#864337: fixed in python-blessed 1.14.2-2
has caused the Debian Bug report #864337,
regarding python-blessed: Non-determistically FTBFS due to unreliable timing in 
tests
to be marked as done.

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

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


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

Dear Maintainer,

python-blessed's testsuite appears to use method timing/benchmarking in such 
a way that it will non-deterministically FTBFS:

  […]
   test_esc_delay_cbreak_timout_0 

  
  def test_esc_delay_cbreak_timout_0():
  """esc_delay still in effect with timeout of 0 ("nonblocking")."""
  pid, master_fd = pty.fork()
  if pid == 0:  # child
  cov = init_subproc_coverage('test_esc_delay_cbreak_timout_0')
  term = TestTerminal()
  os.write(sys.__stdout__.fileno(), SEMAPHORE)
  with term.cbreak():
  stime = time.time()
  inp = term.inkey(timeout=0)
  measured_time = (time.time() - stime) * 100
  os.write(sys.__stdout__.fileno(), (
  '%s %i' % (inp.name, measured_time,)).encode('ascii'))
  sys.stdout.flush()
  if cov is not None:
  cov.stop()
  cov.save()
  os._exit(0)
  
  with echo_off(master_fd):
  os.write(master_fd, u'\x1b'.encode('ascii'))
  read_until_semaphore(master_fd)
  stime = time.time()
  key_name, duration_ms = read_until_eof(master_fd).split()
  
  pid, status = os.waitpid(pid, 0)
  assert key_name == u'KEY_ESCAPE'
  assert os.WEXITSTATUS(status) == 0
  assert math.floor(time.time() - stime) == 0.0
  >   assert 34 <= int(duration_ms) <= 45, int(duration_ms)
  E   AssertionError: 71
  E   assert 71 <= 45
  E+  where 71 = int('71')
  
  blessed/tests/test_keyboard.py:528: AssertionError
   1 failed, 305 passed in 75.27 seconds 
=
  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-blessed-1.14.1/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
pytest 
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2
  I: copying local configuration
  E: Failed autobuilding of package

  […]

The full build log is attached or can be viewed here:


https://tests.reproducible-builds.org/debian/logs/unstable/amd64/python-blessed_1.14.1-1.build1.log.gz


Regards,

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


python-blessed.1.14.1-1.logs.unstable.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-blessed
Source-Version: 1.14.2-2

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

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

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated python-blessed 
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, 03 Jan 2018 01:18:43 +0100
Source: python-blessed
Binary: python-blessed python3-blessed
Architecture: source
Version: 1.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Pierre-Elliott Bécue 
Description:
 python-blessed - Thin, practical wrapper around terminal capabilities in 
Python2
 python3-blessed - Thin, practical wrap

Bug#885875: marked as done (seelablet: Depends on python-appindicator)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 00:40:05 +
with message-id 
and subject line Bug#886047: Removed package(s) from unstable
has caused the Debian Bug report #885875,
regarding seelablet: Depends on python-appindicator
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.)


-- 
885875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seelablet
Version: 1.0.6-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs
Tags: sid buster

python-seelablet depends on python-appindicator but python3-seelablet
depends on gir1.2-appindicator3-0.1

The gir dependency is wrong since as far as I can tell seelablet
doesn't use GObject Introspection at all. I *think* the python-
appindicator dependency is wrong too because I thought python-
appindicator required gtk and this doesn't use gtk at all.

(I can't actually tell if it works because I can't get the app to run.
Filing a separate bug for that.)

I'm filing this bug as Serious since this is the last package keeping
python-appindicator from being removable in Testing.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.0.6-2+rm

Dear submitter,

as the package seelablet 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/886047

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#885876: marked as done (seelablet: wrong dependencies, app won't run)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 00:40:05 +
with message-id 
and subject line Bug#886047: Removed package(s) from unstable
has caused the Debian Bug report #885876,
regarding seelablet: wrong dependencies, app won't run
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.)


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

seelablet depends on python-seelablet (and not python3-seelablet)
although /usr/bin/Experiments has a python3 shebang.

When I tried to run /usr/bin/Experiments in a default Ubuntu 17.10
install (so using GNOME), I got

  $ Experiments 
  Traceback (most recent call last):
File "/usr/bin/Experiments", line 17, in 
  import sip
  ModuleNotFoundError: No module named 'sip'

Ok, so python3-seelablet needs to depend on python3-sip. After
installing that, I got

  $ Experiments 
  Traceback (most recent call last):
File "/usr/bin/Experiments", line 21, in 
  from PyQt4 import QtWebKit
  ImportError: cannot import name 'QtWebKit'

And that's where I stopped because it doesn't look like that's
available in Debian.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.0.6-2+rm

Dear submitter,

as the package seelablet 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/886047

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 ---

Processed: your mail

[Debian Bug Tracking System]

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

> block 884018 by 885407
Bug #884018 [src:yamcha] yamcha: FTBFS with debhelper >= 10.9.2: 
dh_systemd_enable is no longer used in compat >= 11, please use 
dh_installsystemd instead
884018 was not blocked by any bugs.
884018 was not blocking any bugs.
Added blocking bug(s) of 884018: 885407
>
End of message, stopping processing here.

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

Bug#886153: anything-el: A stale file lock of anything-c-adaptive-history breaks emacs batch processing

[David Bremner]

David Bremner  writes:

>> At this point the emacs is hanging.
>> Trying to answer the „lock“ prompt is not possible. You have to terminate 
>> the processing *SIGINT* (Ctrl+C) or killing it.
>
> Following your recipe, I can't duplicate this behaviour with emacs24 or 
> emacs25.

On the other hand, if I uncomment the (require 'anything-startup) in
/etc/emacs/site-start.d/50anything-el.el, then I can duplicate the
hanging of emacs -q -batch. I suspect this is actually an emacs bug, and
mostly unrelated to anything.el (except that it writes the same file
every time emacs exits, thus triggering the emacs bug).

Bug#886024: split off anything-el related part

[era eriksson]

Your emacs-batch script seems to have some issues. I have not reviewed
it properly, but e.g. your prevalent use of the declare keyword is
definitely a bashism.
More generally, making Emacs package compilation more robust  is
absolutely not a bad idea; but introducing new requirements should also
be reflected in the Emacs policy (though honestly not sure what its
current status is?)
On Tue, Jan 2, 2018, at 22:34, H.-Dirk Schmitt wrote:
> Here a simple wrapper script would help to :
> - avoid copy and paste errors
> - simplify the fix of this bug
> - simple reuse
>
>
> Code outline for an emacs batch wrapper
> 
>
> Assume a bash script *emacs_batch* replacing the `-q --batch` options.> It 
> should take as 1st option the emacs flavour (e.g. emacs25) and pass> trough 
> all other options except `-q`,
> `--no-init-file` (alias to `-q`)  and `--batch`.
>
> The emacs call could be implemented in this way:
>
> ```
> declare -r catchFile=$(mktemp)  # create temporary
> file> for output

Exit on failure; $(mktemp) || exit

> trap rm --force ${catchFile}#   and ensure cleanup
The trap declaration  seems to be wrong (the trap code needs to be a
single string and you need to specify which signals and conditions
to trap on).
> ${FLAVOUR} --batch "${cmdlineOptions[@]}" &>"${catchFile}" & #
> fork> declare -i emacsPid=$!  # and remember
> sleep ${emacsTimeOut} & # fork timeout watch
> declare -i sleepPid=$!  # and remember
> wait -n ${emacsPid} ${sleepPid} # -n  → wait for the
> next ending job
> declare -r rc=$?# don't forget the
> exit> code
> if ! $(kill ${sleepPid})

The command substitution is fishy too.I guess you mean simply

if ! kill $sleepPid

or do you actually expect kill to print something?

> then# oops run in timeout>
> … add error handling here
> else# emacs terminates
> without timeout
>cat ${catchFile} # forward console
>output>exit ${rc}   # rc is 
> originating
>from> emacs
> fi
> ```
>
> 

/* era */

--
If this were a real .signature, it would suck less.  Well, maybe not.

Bug#885733: marked as done (coriander: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:32:02 +
with message-id 
and subject line Bug#886158: Removed package(s) from unstable
has caused the Debian Bug report #885733,
regarding coriander: Depends on old GNOME libraries
to be marked as done.

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

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


-- 
885733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coriander
Version: 2.0.2-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.0.2-4+rm

Dear submitter,

as the package coriander 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/886158

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#807347: marked as done (txaws: FTBFS: twisted.trial.unittest.FailTest: '500' != 500)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:28:07 +
with message-id 
and subject line Bug#886118: Removed package(s) from unstable
has caused the Debian Bug report #807347,
regarding txaws: FTBFS: twisted.trial.unittest.FailTest: '500' != 500
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.)


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

Dear Maintainer,

txaws fails to build from source in unstable/amd64:

  [..]
  
  txaws.ec2.tests.test_client.QueryTestCase.test_submit_non_EC2_400
  
===
  [FAIL]
  Traceback (most recent call last):
File

"/home/lamby/temp/cdt.20151207215711.OLxXnJQQOq/txaws-0.2.3/txaws/tests/test_exception.py",
line 18, in test_creation
  self.assertEquals(error.status, 500)
File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py",
line 437, in assertEqual
  super(_Assertions, self).assertEqual(first, second, msg)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
  assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 506, in
_baseAssertEqual
  raise self.failureException(msg)
  twisted.trial.unittest.FailTest: '500' != 500
  
  txaws.tests.test_exception.AWSErrorTestCase.test_creation
  
---
  Ran 437 tests in 0.633s
  
  FAILED (skips=56, failures=9, successes=372)
  debian/rules:14: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151207215711.OLxXnJQQOq/txaws-0.2.3'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


txaws.0.2.3-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 0.2.3-1+rm

Dear submitter,

as the package txaws 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/886118

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#790141: marked as done (txaws: depends on python-gnomekeyring which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:28:07 +
with message-id 
and subject line Bug#886118: Removed package(s) from unstable
has caused the Debian Bug report #790141,
regarding txaws: depends on python-gnomekeyring which is deprecated
to be marked as done.

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

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


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

Hi,

txaws depends on python-gnomekeyring, which is long deprecated and
going to be removed from the archive. txaws should switch to using
the GObject Introspection bindings for gnome-keyring,
gir1.2-gnomekeyring-1.0.

This would mean switching to GObject Introspection for other bindings
as well, e.g. GLib and GTK+, so making the switch to GTK+ 3 at the
same time would make a lot of sense.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.2.3-1+rm

Dear submitter,

as the package txaws 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/886118

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#885134: marked as done (gnome-icon-theme-extras: Don't include in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:25:26 +
with message-id 
and subject line Bug#886008: Removed package(s) from unstable
has caused the Debian Bug report #885134,
regarding gnome-icon-theme-extras: Don't include 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.)


-- 
885134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-icon-theme-extras
Version: 3.12.0-1
Severity: serious

This theme has been unmaintained upstream since March 2014. While
arguably, an icon theme may not need much maintainance…

- It provides some additional icons for the GNOME icon theme but the
GNOME icon theme is unmaintained and deprecated. The replacement is
the Adwaita icon theme, but upstream intentionally does not have
Adwaita inherit from the GNOME theme (so these icons won't be usable
by default).

- Many of the icons are in the Adwaita theme now.

- Several icons are not. But some of these are for ancient phones like
the Nexus One.

- In general, I think that if there are important missing icons, they
should be requested to be moved to the Adwaita icon theme directly.
Alternatively, someone could make an adwaita-icon-theme-extras package
but be careful about 2 packages shipping the same file if upstream
does eventually adopt some of the icon names.

- No reverse depends. However, 'gnome-core' used to Depend on it
before Stretch, which explains its lingering high popcon.

I am filing this bug to allow a bit of comment and notice with the
auto-removal before requesting that gnome-icon-theme-extras be
complete removed from Debian.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 3.12.0-1+rm

Dear submitter,

as the package gnome-icon-theme-extras 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/886008

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#885133: marked as done (gnome-search-tool: Don't include in Buster)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:24:36 +
with message-id 
and subject line Bug#885975: Removed package(s) from unstable
has caused the Debian Bug report #885133,
regarding gnome-search-tool: Don't include in Buster
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.)


-- 
885133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-search-tool
Version: 3.6.0-2
Severity: serious

gnome-search-tool has had to releases since September 2012, over 5 years ago.

It provides basic search functionality that is built in to every
modern file browser.

It has no reverse dependencies and doesn't seem to be a very popular app at all.

Unless someone has a strong objection, I propose that we not include
gnome-search-tool in Buster and remove it from Debian.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 3.6.0-2+rm

Dear submitter,

as the package gnome-search-tool 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/885975

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#822588: marked as done (dreampie: depends on python-gtksourceview2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:24:57 +
with message-id 
and subject line Bug#885977: Removed package(s) from unstable
has caused the Debian Bug report #822588,
regarding dreampie: depends on python-gtksourceview2 which is deprecated
to be marked as done.

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

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


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

Hi,

dreampie depends on python-gtksourceview2, which is long deprecated
and going to be removed from the archive. dreampie should switch to
using the GObject Introspection bindings for gtksourceview,
gir1.2-gtksource-3.0.

This would mean switching to GObject Introspection for other bindings
as well, e.g. GLib and GTK+ 3.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 1.2.1-2+rm

Dear submitter,

as the package dreampie 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/885977

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#790605: marked as done (specto: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:26:28 +
with message-id 
and subject line Bug#886054: Removed package(s) from unstable
has caused the Debian Bug report #790605,
regarding specto: depends on python-gnome2 which is deprecated
to be marked as done.

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

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


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

Hi,

specto depends on python-gnome2, which is long deprecated and going
to be removed from the archive. specto should be ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.2.2-3.3+rm

Dear submitter,

as the package specto 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/886054

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#790162: marked as done (winswitch: depends on python-rsvg which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:25:48 +
with message-id 
and subject line Bug#886011: Removed package(s) from unstable
has caused the Debian Bug report #790162,
regarding winswitch: depends on python-rsvg which is deprecated
to be marked as done.

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

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


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

Hi,

winswitch depends on python-rsvg, which is long deprecated and going
to be removed from the archive. winswitch should switch to using the
GObject Introspection bindings for gnome-keyring, gir1.2-rsvg-2.0.

This would mean switching to GObject Introspection for other bindings
as well, e.g. GLib and GTK+, so making the switch to GTK+ 3 at the
same time would make a lot of sense.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.12.21+dfsg-1+rm

Dear submitter,

as the package winswitch 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/886011

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#822585: marked as done (gvrng: depends on python-gtksourceview2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:24:13 +
with message-id 
and subject line Bug#885966: Removed package(s) from unstable
has caused the Debian Bug report #822585,
regarding gvrng: depends on python-gtksourceview2 which is deprecated
to be marked as done.

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

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


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

Hi,

gvrng depends on python-gtksourceview2, which is long deprecated and
going to be removed from the archive. gvrng should switch to using
the GObject Introspection bindings for gtksourceview,
gir1.2-gtksource-3.0.

This would mean switching to GObject Introspection for other bindings
as well, e.g. GLib and GTK+ 3.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 4.4-3+rm

Dear submitter,

as the package gvrng 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/885966

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#868410: marked as done (yarssr: Please drop the (build-)dependency against gnome-vfs)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:21:11 +
with message-id 
and subject line Bug#885911: Removed package(s) from unstable
has caused the Debian Bug report #868410,
regarding yarssr: Please drop the (build-)dependency against gnome-vfs
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.)


-- 
868410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yarssr
Version: 0.2.2-9
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Version: 0.2.2-9+rm

Dear submitter,

as the package yarssr 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/885911

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#790182: marked as done (lcrt: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:23:51 +
with message-id 
and subject line Bug#885964: Removed package(s) from unstable
has caused the Debian Bug report #790182,
regarding lcrt: depends on vte which is deprecated
to be marked as done.

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

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


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

Hi,

lcrt depends on python-vte / libvte9, which are deprecated in favor
of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove src:vte
from the archive. lcrt should switch to the new vte version.

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

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

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

Emilio 
--- End Message ---
--- Begin Message ---
Version: 1.1.2-2+rm

Dear submitter,

as the package lcrt 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/885964

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#822593: marked as done (aptoncd: depends on gksu which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:22:05 +
with message-id 
and subject line Bug#885946: Removed package(s) from unstable
has caused the Debian Bug report #822593,
regarding aptoncd: depends on gksu which is deprecated
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Version: 0.1.98+bzr117-1.4+rm

Dear submitter,

as the package aptoncd 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/885946

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#845960: marked as done (x-tile: depends on python-gnome2 which deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:23:19 +
with message-id 
and subject line Bug#885956: Removed package(s) from unstable
has caused the Debian Bug report #845960,
regarding x-tile: depends on python-gnome2 which deprecated
to be marked as done.

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

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


-- 
845960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x-tile
Version: 2.5-3
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

x-tile depends on python-gnome2 or python-gconf, or has a
build-dependency on one those packages. Those are built from
gnome-python which is long deprecated and going to be removed from
the archive. x-tile should be ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

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

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

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 2.5-3+rm

Dear submitter,

as the package x-tile 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/885956

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#790573: marked as done (aptoncd: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:22:05 +
with message-id 
and subject line Bug#885946: Removed package(s) from unstable
has caused the Debian Bug report #790573,
regarding aptoncd: depends on python-gnome2 which is deprecated
to be marked as done.

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

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


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

Hi,

aptoncd depends on python-gnome2, which is long deprecated and going
to be removed from the archive. aptoncd should be ported away from
it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.1.98+bzr117-1.4+rm

Dear submitter,

as the package aptoncd 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/885946

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#790586: marked as done (gnome-btdownload: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:22:28 +
with message-id 
and subject line Bug#885948: Removed package(s) from unstable
has caused the Debian Bug report #790586,
regarding gnome-btdownload: depends on python-gnome2 which is deprecated
to be marked as done.

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

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


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

Hi,

gnome-btdownload depends on python-gnome2, which is long deprecated
and going to be removed from the archive. gnome-btdownload should be
ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

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

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

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.0.32-5+rm

Dear submitter,

as the package gnome-btdownload 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/885948

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#787344: marked as done ([RC][cc-by-nc-sa] Please clarify license of data/icons/scalable/apps/aptoncd.svg)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:22:05 +
with message-id 
and subject line Bug#885946: Removed package(s) from unstable
has caused the Debian Bug report #787344,
regarding [RC][cc-by-nc-sa] Please clarify license of 
data/icons/scalable/apps/aptoncd.svg
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.)


-- 
787344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptoncd
Severity: serious
version: 0.1.98+bzr117-1.4 
user: lintian-ma...@debian.org
usertags: license-problem-cc-by-nc-sa.html


Hi,

Could you please clarify the license of data/icons/scalable/apps/aptoncd.svg, 
claimed on source to be cc-by-nc-sa, thus non free.

If it is really a non free image please purge data/icons/ png image (BTW it is 
a good idea to recreate at build time using imagemagick).

If it is a false positive please override like in 
http://sources.debian.net/src/freecad/0.14.3702%2Bdfsg-3/debian/source/lintian-overrides/
and add a changelog entry and a full explanation on debian/copyright. You may 
ask upstream to remove this cc-by-sa-nc tag on the svg file




signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 0.1.98+bzr117-1.4+rm

Dear submitter,

as the package aptoncd 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/885946

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#885053: marked as done (gnome-subtitles: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:20:42 +
with message-id 
and subject line Bug#885901: Removed package(s) from unstable
has caused the Debian Bug report #885053,
regarding gnome-subtitles: Depends on old GNOME libraries
to be marked as done.

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

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


-- 
885053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-subtitles
Version: 1.3-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf libgnome
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- gconf
- libgconf2.0-cil
- libgnome2.24-cil

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.3-2+rm

Dear submitter,

as the package gnome-subtitles 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/885901

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#883503: marked as done (prerex: depends on libpoppler-qt4 which is about to be removed)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 22:00:12 +
with message-id 
and subject line Bug#883503: fixed in vprerex 1:6.5.1-1
has caused the Debian Bug report #883503,
regarding prerex: depends on libpoppler-qt4 which is about to be removed
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.)


-- 
883503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prerex
Severity: serious
Tags: sid stretch
User: pkg-freedesktop-maintain...@lists.alioth.debian.org
Usertags: oldlibs poppler-qt4

Control: block 875096 with -1

Hi,

prerex (build-)depends on Poppler Qt4 bindings, which have been
removed upstream in Poppler 0.62.0. They will be gone from Debian
soon, once we update to that version.

prerex should switch to the Qt5 bindings, or disable Poppler support
if the former is not possible.

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

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: vprerex
Source-Version: 1:6.5.1-1

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

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated vprerex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Jan 2018 12:47:02 -0500
Source: vprerex
Binary: vprerex
Architecture: source amd64
Version: 1:6.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description:
 vprerex- Qt interface to prerex, a course prerequisite chart editor
Closes: 875104 883503
Changes:
 vprerex (1:6.5.1-1) unstable; urgency=medium
 .
   * New upstream release: this marks a fork from the prerex source package
 into two source packages. Because prerex used to provide the vprerex
 package under the prerex version (which is greater than the vprerex
 version), we need to bump the epoch.
   * Switch to Qt5 (Closes: #875104, #883503)
   * Bump standards version to 4.1.3
   * Dropped menu files
   * Make Vcs-* URLs secure
   * Updated copyright file
   * Drop MimeType from desktop files
   * Install and use vprerex icon
   * Completely turn on hardening flags
   * Update the watch file to point to CTAN.
   * Build-depend on debhelper >= 11, bump compat level to 11, and drop
 dh-autoreconf because debhelper runs it for us under compat >= 10.
Checksums-Sha1:
 e99b2dc5d120951d5c5f51ac8138f1e8ed5a9cb1 2969 vprerex_6.5.1-1.dsc
 67cbd1a92bd488f5f3b5812666d381fdde54da97 19127 vprerex_6.5.1.orig.tar.gz
 67fea67baa29e0883f2073892e8bf514eb090980 4616 vprerex_6.5.1-1.debian.tar.xz
 a3e75d409ca14fc5f024956c468f574d986fff39 851200 
vprerex-dbgsym_6.5.1-1_amd64.deb
 0f83db37ad49a240074500b25108d9171ad7e91b 11401 vprerex_6.5.1-1_amd64.buildinfo
 062acd7776d7eec6d74c24062f5e06d110c030ee 30560 vprerex_6.5.1-1_amd64.deb
Checksums-Sha256:
 894d03a59fc77be0ae2eb9de5a51da5e5b63482b57f90fcd8f06a0ec0e75b4ec 2969 
vprerex_6.5.1-1.dsc
 fef226574a214d39d4f09017b29167b4efc24bc9f592d69f56127d7e0d33245b 19127 
vprerex_6.5.1.orig.tar.gz
 c2bace30cd4c71d243162559a0b36beefc13e1d555954cb0685935a268a900a0 4616 
vprerex_6.5.1-1.debian.tar.xz
 50c406ccbea9ed95d445af23c23c7317f9409ac7d0eb395971ee7f40c5b979fe 851200 
vprerex-dbgsym_6.5.1-1_amd64.deb
 3d2aef236b48c070eab0e917c4a1d31dc3faa9273855b98e86578f0c30d81e0b 11401 
vprerex_6.5.1-1_amd64.buildinfo
 4a5f746b16afccdfa837e1fdb38b78fa3924cc00fbfb179483370b620871afa3 30560 
vprerex_6.5.1-1_amd64.deb
Files:
 86c303ae39edb1d05892bd3c3fec6b6b 2969 tex optional vprerex_6.5.1-1.dsc
 fe50e09ded7930c2b1f2c9ffaf4ab0fa 19127 tex optional vprerex_6.5.1.orig.tar.gz
 5acbde39ef87c9733296097bf3c4a5ba 4616 tex optional 
vprerex_6.5.1-1.debian.tar.xz
 53982c907ad85993db2836f28d9abeb5 851200 debug optional 
vprerex-dbgsym_6.5.1-1_amd64.deb
 d53a43641fcdf250a8bc13d51cd92ee3 11401 tex optional 
vprerex_6.5.1-1_amd64.buildinfo
 b4405a93a222a3ea095637ea875d949e 30560 tex optional vprerex_6.5.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQVDBAEBCgAtFiEETkaVGe1ndzQmj72Vj3v4/EoRyXoFAlpLxycPHHJha0BkZWJp
YW4ub3JnAAoJ

Bug#886153: anything-el: A stale file lock of anything-c-adaptive-history breaks emacs batch processing

[David Bremner]

H.-Dirk Schmitt  writes:


>
> Without the stale lock this command will finish after a short time.
> With the lock, you will see the following output:
>
[snip]
>> Loading 95c42_defaults (compiled; note, source file is newer)...

What's that? it doesn't look like a debian package. Does your problem
persist if you remove it?

>> Loading log-edit...
>> Trailing whitespace highlighting is now ON.
>> TAB highlighting is now ON.
>> Loading /home/dschmi/.recentf...

I guess you ran this as your user, rather than as root? It also seems odd to
me that recentf is being invoked at all.

>> Cleaning up the recentf list...
>> Cleaning up the recentf list...done (0 removed)
>> Loading /usr/local/share/emacs/site-lisp/ob-eukleides.el (source)...
>> Loading /home/dschmi/.emacs.d/anything-c-adaptive-history...

I can't understand what is loading that. The standard startup file for
anything-el just sets the load-path

>> [yas] Prepared just-in-time loading of snippets successfully.
>> Loading systemd...
>> Loading crontab-mode...
>> Loading json-mode...
>> Loading ldap-mode...
>> Loading nagios-mode...
>> Loading org-journal...
>> Loading 99c42_keymap...
>> Local Ispell dictionary set to british
>> Starting new Ispell process aspell with british dictionary...
>> ...ing-c-adaptive-history locked by xx@xx... (pid 5423): (s, q, p, 
>> ?)?
>
> At this point the emacs is hanging.
> Trying to answer the „lock“ prompt is not possible. You have to terminate the 
> processing *SIGINT* (Ctrl+C) or killing it.

Following your recipe, I can't duplicate this behaviour with emacs24 or emacs25.

Processed: cloning 883386, reassign -1 to php-markdown, retitle -1 to php-apigen/php-markdown is going away

[Debian Bug Tracking System]

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

> clone 883386 -1
Bug #883386 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug 883386 cloned as bug 886184
> reassign -1 php-markdown
Bug #886184 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug reassigned from package 'php-apigen' to 'php-markdown'.
No longer marked as found in versions php-apigen/4.1.2-2.
Ignoring request to alter fixed versions of bug #886184 to the same values 
previously set
> retitle -1 php-apigen/php-markdown is going away
Bug #886184 [php-markdown] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Changed Bug title to 'php-apigen/php-markdown is going away' from 'php-apigen 
depends on php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be installed'.
> thanks
Stopping processing here.

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

Processed: cloning 883386, reassign -1 to php-fshl, retitle -1 to php-apigen/php-fshl is going away

[Debian Bug Tracking System]

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

> clone 883386 -1
Bug #883386 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug 883386 cloned as bug 886183
> reassign -1 php-fshl
Bug #886183 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug reassigned from package 'php-apigen' to 'php-fshl'.
No longer marked as found in versions php-apigen/4.1.2-2.
Ignoring request to alter fixed versions of bug #886183 to the same values 
previously set
> retitle -1 php-apigen/php-fshl is going away
Bug #886183 [php-fshl] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Changed Bug title to 'php-apigen/php-fshl is going away' from 'php-apigen 
depends on php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be installed'.
> thanks
Stopping processing here.

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

Processed: cloning 883386, reassign -1 to php-tokenreflection ...

[Debian Bug Tracking System]

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

> clone 883386 -1
Bug #883386 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug 883386 cloned as bug 886185
> reassign -1 php-tokenreflection
Bug #886185 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug reassigned from package 'php-apigen' to 'php-tokenreflection'.
No longer marked as found in versions php-apigen/4.1.2-2.
Ignoring request to alter fixed versions of bug #886185 to the same values 
previously set
> retitle -1 php-apigen/php-tokenreflection is going away
Bug #886185 [php-tokenreflection] php-apigen depends on php-symfony-* (< 3~~) 
but 3.4.0+dfsg-1 is to be installed
Changed Bug title to 'php-apigen/php-tokenreflection is going away' from 
'php-apigen depends on php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be 
installed'.
> thanks
Stopping processing here.

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

Processed: cloning 883386, reassign -1 to php-nette, retitle -1 to php-apigen/php-nette is going away

[Debian Bug Tracking System]

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

> clone 883386 -1
Bug #883386 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug 883386 cloned as bug 886180
> reassign -1 php-nette
Bug #886180 [php-apigen] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Bug reassigned from package 'php-apigen' to 'php-nette'.
No longer marked as found in versions php-apigen/4.1.2-2.
Ignoring request to alter fixed versions of bug #886180 to the same values 
previously set
> retitle -1 php-apigen/php-nette is going away
Bug #886180 [php-nette] php-apigen depends on php-symfony-* (< 3~~) but 
3.4.0+dfsg-1 is to be installed
Changed Bug title to 'php-apigen/php-nette is going away' from 'php-apigen 
depends on php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be installed'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#885055: timeline: don't depend only on iceowl-extension without lightning

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885055 [src:timeline] timeline: don't depend only on iceowl-extension 
without lightning
Severity set to 'serious' from 'important'

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

Processed: affects 886177

[Debian Bug Tracking System]

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

> affects 886177 + src:thunderbird
Bug #886177 [xul-ext-sieve] xul-ext-sieve: Please depend on thunderbird | 
icedove
Added indication that 886177 affects src:thunderbird
> thanks
Stopping processing here.

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

Bug#886177: xul-ext-sieve: Please depend on thunderbird | icedove

[Carsten Schoenert]

Package: xul-ext-sieve
Severity: serious

Dear Maintainer of xul-ext-sieve,

starting with uploading src:thunderbird 1:52.5.0-1 there no transitional
packages like icedove* or iceowl* are built anymore. So the package
xul-ext-sieve is depending on a binary package icedove which isn't
existing any longer in unstable.

I raised the severity for xul-ext-sieve to serious as this prevents now
the migration of thunderbird packages to testing. Please upload a
rebuilded package.

Regards
Carsten

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

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

Processed: Re: Bug#867722: xul-ext-imap-acl: please depend on icedove | thunderbird

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #867722 [xul-ext-imap-acl] xul-ext-imap-acl: please depend on icedove | 
thunderbird
Severity set to 'serious' from 'normal'
> affects -1 src:thunderbird
Bug #867722 [xul-ext-imap-acl] xul-ext-imap-acl: please depend on icedove | 
thunderbird
Added indication that 867722 affects src:thunderbird

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

Bug#886178: An extra trailing slash is added to ZFS root pool and it's not bootable

[Fejes József]

Package: grub-common
Version: 2.02-2
Severity: grave

I have my root filesystem on ZFS. I'm using a ZFS pool's root dataset
(rpool) as opposed to a sub-dataset (eg. rpool/foo or rpool/foo/bar).

update-grub calls calls /etc/grub.d/10_linux which sets the root=ZFS=
parameter for grub/initrd. In this case, it sets it as
root=ZFS=rpool/. Note the trailing slash. This is invalid and makes
the system unbootable.

I already filed this bug at https://savannah.gnu.org/bugs/?52746 . But
that bugtracker looks completely abandoned for months. I'm pretty sure
it only needs a small fix to remove extra trailing slashes.

Processed: change summary 886024

[Debian Bug Tracking System]

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

> summary 886024 30
Summary recorded from message bug 886024 message 30
>
End of message, stopping processing here.

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

Processed: severity of 886121 is important

[Debian Bug Tracking System]

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

> severity 886121 important
Bug #886121 [nullmailer] nullmailer: cannot be installed: Broken 
nullmailer:amd64 Depends on systemd-sysv:amd64
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: split off anything-el related part

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 emacsen-addon package installation may never comes to an end
Bug #886024 [emacsen-common, markdown-mode] emacs deb package install is 
hanging forever (locked file)
Changed Bug title to 'emacsen-addon package installation may never comes to an 
end' from 'emacs deb package install is hanging forever (locked file)'.
> severity -1 critical
Bug #886024 [emacsen-common, markdown-mode] emacsen-addon package installation 
may never comes to an end
Severity set to 'critical' from 'important'
> affects -1 = emacsen-common, elpa-company, elpa-js2-mode, elpa-markdown-mode, 
> elpa-systemd, elpa-yasnippet
Bug #886024 [emacsen-common, markdown-mode] emacsen-addon package installation 
may never comes to an end
Added indication that 886024 affects elpa-yasnippet, elpa-markdown-mode, 
emacsen-common, elpa-systemd, elpa-company, and elpa-js2-mode

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

Bug#885996: gnome-shell-extension-show-ip: not compatible with gnome-shell 3.26

[Kyle Robbertze]

I am busy packaging the new release and should have it uploaded to sid by the 
end of next week. I will check if it fixes this bug

On 01 Jan 2018, 13:39, at 13:39, Paul Wise  wrote:
>On Mon, 01 Jan 2018 19:27:47 +0800 Paul Wise wrote:
>
>> This extension is not compatible with gnome-shell 3.26 and
>> this prevents it from being loaded on Debian buster/sid:
>
>Actually, it looks like the incorrect metadata issue is irrelevant to
>the loading of gnome-shell extensions, but this extension is still not
>being loaded by gnome-shell 3.26 on Debian buster/sid.
>
>--
>bye,
>pabs
>
>https://wiki.debian.org/PaulWise

Bug#886119: e2fsprogs: FTBFS on big-endian architectures

[Theodore Ts'o]

Hi, thanks for sending me a patch!  I had noted the build failures and
it was on my todo list to debug and fix today; you saved me a bunch of
time.

I will apply this and get an updated release out quickly.

Cheers,

- Ted

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

[Aaron M. Ucko]

> It so happens that I was having a brief look already :)

Great, thanks!

> The hang occurs inside the above while loop. Notice that the value
> loaded into "label" inside the loop never changes and this is the only
> variable the loop condition depends on. Therefore, if the initial loop
> condition is true, the program will loop forever.

So I see.  Perhaps the intent was to update mpls after bumping ip_offset.

> Firstly, the order of fields in a bitfield is ABI dependent so any
> architecture could legitimately rearrange all the fields giving wrong
> results. I also don't really understand what the programmer intended to
> happen when invoking ntohl on a bitfield.

Excellent question, though it's ironic that these failures are occurring
on architectures for which ntohl is a no-op. ;-) Please note that the
autobuilders for m68k and powerpcspe, the (non-release) big-endian
architectures on which this ndpi version nominally built fine, both run
with nocheck in DEB_BUILD_OPTIONS, so we shouldn't read too much into
those successes.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#886163: lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: output differs!

[Chris Lamb]

tags 886163 + pending
thanks

Thanks Adrian. This should be fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=95a56b3e3210a36c996a98d0aa1e6cfafad6bcb7


Regards,

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

Processed: Re: lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: output differs!

[Debian Bug Tracking System]

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

> tags 886163 + pending
Bug #886163 [src:lintian] lintian FTBFS on i386: fail 
tests::files-multiarch-foreign-files: output differs!
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#885640: marked as done (gnome-commander: Fix Build-Depends)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 19:49:03 +
with message-id 
and subject line Bug#885640: fixed in gnome-commander 1.4.8-1.1
has caused the Debian Bug report #885640,
regarding gnome-commander: Fix Build-Depends
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.)


-- 
885640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-commander
Version: 1.4.8-1
Severity: serious
Tags: patch pending
X-Debbugs-CC: ales...@debian.org

scrollkeeper has been deprecated and unmaintained for years. Its
replacement, rarian has been deprecated for years too. More
importantly, it doesn't seem to be needed at all. yelp can easily
display Docbook help files without any .omf files.

We do not intend to ship rarian in Debian 10 "Buster". Therefore, we
should drop rarian-compat from gnome-commander's Build-Depends.

I also noticed that gnome-commander now fails to build with scour 0.36
since python3-scour provides dh_scour instead of python-scour.

I am uploading an NMU to the DELAYED/5 queue to fix both these issues.
Please let me know if I should delay or speed up the upload.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnome-commander
Source-Version: 1.4.8-1.1

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-commander package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Dec 2017 14:12:57 -0500
Source: gnome-commander
Binary: gnome-commander gnome-commander-data gnome-commander-dbg
Architecture: source
Version: 1.4.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt 
Changed-By: Jeremy Bicha 
Description:
 gnome-commander - nice and fast file manager for the GNOME desktop
 gnome-commander-data - Data files for GNOME Commander
 gnome-commander-dbg - Debugging symbols for gnome-commander
Closes: 879561 885640
Launchpad-Bugs-Fixed: 1691867
Changes:
 gnome-commander (1.4.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-Depend on python3-scour to fix build failure with latest scour
   * Drop obsolete Build-Depends on rarian-compat (Closes: #885640)
   * Don't suggest gnome-user-guide (Closes: #879561) (LP: #1691867)
Checksums-Sha1:
 95a272e65e2f520d9c577c00660c9d7ba867a63a 2407 gnome-commander_1.4.8-1.1.dsc
 9ac7883e72db8621cca61ec63b330fbcee69fd78 7104 
gnome-commander_1.4.8-1.1.debian.tar.xz
 ccba954393ab35e586541ae00ea986981da53040 8313 
gnome-commander_1.4.8-1.1_source.buildinfo
Checksums-Sha256:
 5502bfaef14b14fd87dba067e90d037a1212f3953076c152168076334c88e09d 2407 
gnome-commander_1.4.8-1.1.dsc
 3d94d9f1a2348aa6def4cc26cb0743f36cbf23106e7332957da264b529c7a4d1 7104 
gnome-commander_1.4.8-1.1.debian.tar.xz
 111cc45d11e58ac420886307974b57c08267c2d8352c65e2a88bd0ddd0ecedbd 8313 
gnome-commander_1.4.8-1.1_source.buildinfo
Files:
 a1068d349a7cd6f32ed1f991d1e14142 2407 gnome optional 
gnome-commander_1.4.8-1.1.dsc
 c57846d86805c5e87f1061fdfe6db822 7104 gnome optional 
gnome-commander_1.4.8-1.1.debian.tar.xz
 e099d357a4f528634c3721b599704ec7 8313 gnome optional 
gnome-commander_1.4.8-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaRUJmAAoJEOZsd1rr/mx9p0UP/31UKWMK60C+apRvawFWdBrY
Pv+usa7Xe+3N/3wm3Eed4u+BR5wrzL8zoFp2g//1itf6NcrZ45hatL1xRIYtl7t3
o++jZyKEyeaMhSEtAY51PAZuvTLvKGkWO6Vk6/ZIs4OGfQ5+amqa80HAtQ0Q7u92
wmB/H4VUdYEPBIXFlKGHGUsKA05KtCW7cbiWi4RnPBRMFiTwk0gY85DoPVMX1naU
4uU2cpTEVJHkMsRqSWJ88bzSXOHUIKQ8sFcEE2PGxp0nfeEACnWa6ff+9EQIFklc
deMqHYu7hak58HTqFIVfyA1dppcED/TvY+3lQ8XxZw9IcmsrQ2r5athIkh2i4bpX
M2noBxc7pBwhxmpaKfDI12RsyEbQD5yrxYScxAmdf/j2PipO+PMWbrLXxYiSuZuF
yC57PB+eHQAi78UrtDoRKKc9FLaZOPbUCcZ1V5eRWHbNuifBiJLVcdo4DVzuqCLp
E4Hw7YkUkbwLmOndNseVXFgoE7oQ1+4l1t7kwPNwsI6wMl014r0ZkaN/6bm5ras1
fAfHsE8n46GQynGBxDC0w2WaItIAwPoPkkUHLWgVQP87tXEhXONuhNnCP0Emvno2
HaC0JIMWfaDh+eZMvkFGao1o0uJSwg4NMtJVo87BZbsumYkpgqdYfTBlCGSGj7YL
67HP4oTNdF+x/YnXV38i
=nZFJ
-END PGP SIGNATURE End Messag

Bug#885091: marked as done (patchage: Drop unnecessary Build-Depends on old gnome libraries)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 19:34:49 +
with message-id 
and subject line Bug#885091: fixed in patchage 1.0.0~dfsg0-0.2
has caused the Debian Bug report #885091,
regarding patchage: Drop unnecessary Build-Depends on old gnome libraries
to be marked as done.

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

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


-- 
885091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ladish
Version: 3.0-3.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libglade
Tags: sid buster patch
X-Debbugs-CC: ales...@debian.org

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package has apparently unnecessary Build-Depends on
libgnomecanvasmm-2.6-dev and libglademm-2.4-dev. Both of those
libraries will be removed from Debian soon.

I have uploaded a fix for this issue to the DELAYED/10 queue (plus a
few other packaging updates). Please let me know if I should delay (or
speed up) the upload. I will attach the debdiff in a follow-up email.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: patchage
Source-Version: 1.0.0~dfsg0-0.2

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated patchage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Dec 2017 13:28:15 -0500
Source: patchage
Binary: patchage
Architecture: source
Version: 1.0.0~dfsg0-0.2
Distribution: unstable
Urgency: medium
Maintainer: Paul Brossier 
Changed-By: Jeremy Bicha 
Description:
 patchage   - modular patch bay for Jack audio and Alsa Midi
Closes: 885091
Changes:
 patchage (1.0.0~dfsg0-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop unnecessary Build-Depends on libgnomecanvasmm-2.6-dev and
 libglademm-2.4-dev (Closes: #885091)
   * Drop obsolete menu file and .xpm
   * Bump debhelper compat to 11
   * Bump Standards-Version to 4.1.2
Checksums-Sha1:
 4d0e3fee0b0e4d9350f33c3c01ec900d768f10b1 1960 patchage_1.0.0~dfsg0-0.2.dsc
 7d635f5ed7fe4ab6253cf6dfbffcef773f5e649d 4796 
patchage_1.0.0~dfsg0-0.2.debian.tar.xz
 1d4e3970e578abe2d355d6d1e861a998745884d7 6837 
patchage_1.0.0~dfsg0-0.2_source.buildinfo
Checksums-Sha256:
 f0015cde26ba9e40199cddb384e2a436e6bbc33e53d0edb444ca2dda8ca86f33 1960 
patchage_1.0.0~dfsg0-0.2.dsc
 c6140e66910cf17818889ffe11e2992ddbb684adbe0008a67c7f205aa36a7593 4796 
patchage_1.0.0~dfsg0-0.2.debian.tar.xz
 76426365a9d1c064797768e8a5a6a8e86a69f7177ee2fa47f247f45dc9a20895 6837 
patchage_1.0.0~dfsg0-0.2_source.buildinfo
Files:
 796af2c818a041b8b11080e62d0388bc 1960 sound optional 
patchage_1.0.0~dfsg0-0.2.dsc
 eb359f194095d1e6f14e7e6999d880c7 4796 sound optional 
patchage_1.0.0~dfsg0-0.2.debian.tar.xz
 e47415d82653997745627c8f2c91f7bf 6837 sound optional 
patchage_1.0.0~dfsg0-0.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaPqQ+AAoJEOZsd1rr/mx9JVoP/3i4rMTb6771+7p4ilAYsMcH
ZjpfglfHi8F0BX+cUIoVKUEThsK48aI+1DKwcZ3eMaqn2/lu6dOxSs6msNAvcp0H
A/K925Ccpwt0ZjVdUBuqu5pNGXnYvOJbmpxrelkahQTt2yqC0pb6LrYkznAMf7Fl
a1/9Kk+5/CS4VBoC1RdsS5KZrmsMQhJNGpdr4UPDf/9D2+/AWxc2mbfewCSNIvXA
dqJ6Vu5F52geUtzvWh+zbjCyjfeR8qJlFN8i+lALpZLx8IFIE++gF3Mam+HFQbvN
Jfzh5FmkjTmPuhJS22WoCtROIKxATf2fCBkngI/m+eZ1Ldi7nPEYLq62dfngvOKL
+qErak8sh0CJgx0T/iMsYJB5mnNs8t5gJsOVFxqhYa0bJkXlWycfQiV9D8/d/hCx
QM7lhGoPU4ru/28kC3j+4Eums9NITI62KTRw2R5xyWVCgEgz7gL21cWYadd1sA23
WqVfchCK8m8BCMB0wuSaC7wVBD48124AOo+THXDXgG0tz3pnBJTVCXYeyblY2V6J
tJI8Nc+DU9lZCXZ6r8YwtA4HEk8D9Fziof89xSoQABHyLcFvuq9STq6K94j8xeTd
D+/Co5KTlxlV4xoitLdht5n4NZV2/qvoJC0sfcEziYIrkgGyYA/hgCDnqzN8v0sx
c1XDSdy+BaZRJAb8gope
=mAJa
-END PGP SIGNATURE End Message ---

Bug#883938: Updated 3.16.51-3 kernel for debian-installer images

[Salvatore Bonaccorso]

Hi Erik,

On Tue, Jan 02, 2018 at 11:09:03AM -0800, E Barker wrote:
> Hello,
> 
> Just wondering when we can expect an update to the linux and initrd
> images within the netboot debian-installer tree?

See https://lists.debian.org/debian-stable-announce/2017/12/msg2.html

The netboot images will only be updated in the next point release, so
until then for the installer the workaround needs to be applied
passing the kernel parameter numa=off (just for the installation).

Regards,
Salvatore

Bug#883938: Updated 3.16.51-3 kernel for debian-installer images

[E Barker]

Hello,

Just wondering when we can expect an update to the linux and initrd
images within the netboot debian-installer tree?

I had to apply the numa=off workaround for PXE installs but the
date/time stamp for the files still show 12/5/17, 7:51:00 AM:

ftp://ftp.ca.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/debian-installer/amd64/

Thanks,

Erik

Bug#886164: libspring-java: FTBFS MockServerContainer.java method does not override or implement a method from a supertype

[Hans Joachim Desserud]

Source: libspring-java
Version: 4.3.13-1
Severity: serious
Tags: patch

Dear Maintainer,

The package currently fails to build from source with the following 
error message:


All input files are considered out-of-date for incremental task 
':spring-test:compileJava'.

Compiling with JDK Java compiler API.
/build/1st/libspring-java-4.3.13/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java:56: 
warning: [deprecation] setAsyncSendTimeout(long) in WebSocketContainer 
has been deprecated

public void setAsyncSendTimeout(long timeout) {
^
/build/1st/libspring-java-4.3.13/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java:60: 
error: method does not override or implement a method from a supertype

@Override
^
1 error
1 warning
:spring-test:compileJava FAILED

For more details see
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libspring-java.html
I first spotted this issue when the package was synced to Ubuntu, but 
was able to

reproduce it on my Sid system.

The issue itself seems to be related to a method which used to(?) be 
part of an
interface, but is now causing this error. Surprisingly enough, the 
method was
added by one of the Debian patches. The attached patch modifies the 
original
patch a bit and resolves the FTBFS. I must admit I don't have the full 
overview

over what's going on here, so there might be a better way to fix this :)



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

Kernel: Linux 4.14.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/patches/0041-servlet-api-compatibility.patch b/debian/patches/0041-servlet-api-compatibility.patch
index 55887129..0f2e3280 100644
--- a/debian/patches/0041-servlet-api-compatibility.patch
+++ b/debian/patches/0041-servlet-api-compatibility.patch
@@ -100,17 +100,3 @@ Forwarded: no
 +		throw new UnsupportedOperationException();
 +	}
  }
 a/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java
-+++ b/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java
-@@ -58,6 +58,11 @@
- 	}
- 
- 	@Override
-+	public void setDefaultAsyncSendTimeout(long timeout) {
-+		this.defaultAsyncSendTimeout = timeout;
-+	}
-+
-+	@Override
- 	public long getDefaultMaxSessionIdleTimeout() {
- 		return this.defaultMaxSessionIdleTimeout;
- 	}

Bug#886163: lintian FTBFS on i386: fail tests::files-multiarch-foreign-files: output differs!

[Adrian Bunk]

Source: lintian
Version: 2.5.66
Severity: serious

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

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


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

Failed tests (1)
tests::files-multiarch-foreign-files

Bug#886161: auto-complete-el: extremely outdated, blocks packaging of new Emacs packages

[Lev Lamberov]

Package: auto-complete-el
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Debian ships auto-complete-el package version 1.3.1. It was firstly
uploaded in July 6th, 2010. The package was not anyway significantly
updated for more than 7 years. Since 2010 upstream moved development
of auto-complete to GitHub [0] and released three new versions (the
latest version for now is 1.5.1, released on March 30th, 2016).
Moreover two of these versions (1.4.0 and 1.5.0) contained significant
changes, that break backwards compatibility with 1.3.0 branch.

Most of the Emacs packages which depend on auto-complete and are
available on MELPA require auto-complete version >1.4.0. It makes
auto-complete in Debian completely useless, it may also introduce
conflicts and unexpected behavior on the systems with auto-complete
installed from the Debian archive together with auto-complete
installed from, say, MELPA.

Having outdated version of auto-complete in Debian makes integration
of new Emacs packages (which depend on auto-complete) impossible or at
least troublesome. The most notable examples are jedi [1], ein [2],
and spacemacs [3], which was requested to be packaged for Debian.
Since the mentioned Emacs packages depend on auto-complete version
>1.4.0, having outdated auto-complete package in Debian blocks the
whole process of their integration.

Moreover auto-complete package in Debian uses the obsolete
installation mechanisms, where better mechanisms are available with
the help of dh_elpa and dh_elpa_test [4]. The package uses deprecated
debhelper compat version [5]; has outdated (and non-working) watch
file [6]; depends on Emacs versions, which are unavailable anymore in
Debian versions (emacs22, emacs23) [7], which previously caused
problems with the removal of these versions of Emacs (see referenced
bugreport).

The version of auto-complete in the Debian archive may work for some
outdated and/or obsolete code (Emacs configurations and Emacs
packages), but not for the new and modern one. I have not went through
the commit history of the auto-complete upstream, but notably that
GitHub Issues contains information on more than 200 closed issues
(remember, that migration to GitHub happend after the upload of
auto-complete 1.3.1 to the Debian archive). Even in the case that only
25% of these issues were real bugs we have about 50 bugs non-fixed in
the Debian package. Which is a grave, so to speak.

With regards,
Lev Lamberov

[0] https://github.com/auto-complete/auto-complete/

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829589

[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695278

[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828154

[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872616

[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873389

[6] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872614

[7] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689312

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

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

Versions of packages auto-complete-el depends on:
ii  emacs  47.0

auto-complete-el recommends no packages.

auto-complete-el suggests no packages.

Bug#885556: udeb uninstallability trend: worse (+20/-0)

[Cyril Brulebois]

Don Armstrong  (2018-01-01):
> OK. Found the issue. Apparently, packages in the */debian-installer
> components were being skipped when the BTS was figuring out what was
> in which distribution. I've fixed that now, and the versions
> database is being updated with that information.
> 
> The underlying issue should show up as fixed once the version graph
> for this bug looks sane. [Probably in another 10-20 minutes.]

Yes, that's looking good now; many thanks for the swift replies and
bug fixes in debbugs.git! I suppose we haven't been noticing that
earlier because I've been keeping a close eye on udeb-producing
packages, and freezing them when releases were close; we might have
dodged a few bullets in the process without even realizing it. :)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#856096: marked as done (zapping: Please drop the (build-)dependency against esound)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 18:21:51 +
with message-id 
and subject line Bug#856096: fixed in zapping 0.10~cvs6-12
has caused the Debian Bug report #856096,
regarding zapping: Please drop the (build-)dependency against esound
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.)


-- 
856096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zapping
Version: 0.10~cvs6-11
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal

Dear maintainer,

Your package is {build-}depending against esound which is deprecated
for quite some times now.

We are planning to remove esound for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: zapping
Source-Version: 0.10~cvs6-12

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

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated zapping package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Dec 2017 00:03:52 +0200
Source: zapping
Binary: zapping
Architecture: source
Version: 0.10~cvs6-12
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Yavor Doganov 
Description:
 zapping- television viewer for the GNOME environment
Closes: 716640 829824 856096 868412
Changes:
 zapping (0.10~cvs6-12) unstable; urgency=medium
 .
   * QA upload.
   * debian/compat: Bump to 11.
   * debian/control (Priority): Set to optional.
 (Build-Depends): Remove libesd0-dev (Closes: #856096).  Require
 debhelper >= 11.  Remove dh-autoreconf and automake.  Add
 autoconf-archive for the AX_COMPILER_FLAGS macro.  Remove ancient
 version requirements for libgnomeui-dev, libgtk2.0-dev, libzvbi-dev.
 Add freebsd-glue [hurd-any] in an attempt to fix FTBFS on GNU/Hurd.
 (Vcs-Git, Vcs-Browser): Use secure/canonical URIs.
 (zapping-dbg): Remove in favor of automatic -dbgsym.
 (Standards-Version): Claim compliance with 4.1.3 as of this release.
   * debian/rules: Simplify -- remove unused variables, use standard
 targets, order overrides sequentially.  Remove trailing whitespace.
 Enable all hardening flags.  Don't invoke dh_autoreconf.  Don't
 install the .xpm icon.
 (override_dh_strip): Pass --dbgsym-migration.
   * debian/gnome-television.xpm:
   * debian/menu: Delete as per Policy requirement.
   * debian/zapping.install:
   * debian/preinst: Delete, no longer necessary.
   * debian/README.Debian: Fix two typos.
   * debian/patches/03-Desktop.patch: Add Keywords field.
   * debian/patches/08-Spelling-typos.patch: Fix yet another typo.
   * debian/patches/15-Misc-warnings.patch: Fix more warnings.
   * debian/patches/19-zapping_setup_fb_crash.patch: New; fix a segfault
 when zapping_setup_fb is invoked with an invalid display name.  Thanks
 Alexandre Rebert / Mayhem Team for the report (Closes: #716640).
   * debian/patches/20-Check-return-value.patch: New; fix compiler warnings
 [-Wunused-result] which popped up due to the hardened CPPFLAGS.
   * debian/patches/21-GnomeVFS-to-GIO.patch: New; port to GIO, hopefully
 done right (Closes: #868412).
   * debian/patches/22-gnome-common-deprecate.patch: New; don't use
 deprecated gnome-common macro (Closes: #829824).
   * debian/patches/series: Update.
   * debian/changelog: Whitespace cleanup.
   * debian/copyright: Rewrite to adhere to copryight-format 1.0.
Checksums-Sha1:
 8602a803ef7d3a71fcda46acf8e3dfc344fed78a 2220 zapping_0.10~cvs6-12.dsc
 bcc040af4806336405751ecce07eb7ca4ceca35d 32724 
zapping_0.10~cvs6-12.debian.tar.xz
 9931cb264706c63a57cd7501d020138cda752644 13507 
zapping_0.10~cvs6-12_source.buildinfo
Checksums-Sha256:
 c1e070707450d8249c03646bebd46409aa276ac03296190a8fad5c528b51c48d 2220 

Bug#886121: nullmailer: cannot be installed: Broken nullmailer:amd64 Depends on systemd-sysv:amd64

[Thorsten Glaser]

David Bremner dixit:

>I assume you have systemd-sysv held somehow and don't want to install
>it?

Exactly.

>The current state of nullmailer 2.x is that it requires systemd for
>support of the daemon functionality.
>
>Please see #884980, and #885537. Discussion of missing sysvinit support
>should go to the latter.

This is ridiculous. I guess I’ll just have to switch to sendmail
and accept Debian going even further down in niveau / functionality.

Why, in three devils’ names, would a “simple” mail forwarder require
systemd out of a sudden?


Even worse: my usual nullmailer use case is within a(n init-less)
chroot, so this is completely obliterating the *one* environment
in which one’d want to run it.


Not amused,
//mirabilos
-- 
21:49⎜ I have a question guys,
 ⎜Can I use my PC as SMTP server, I use Windows 7 .
 ⎜Already googled and Installed IIS
 ⎜but Still I can't send E-mail

Bug#864337: marked as pending

[Pierre-Elliott Bécue]

tag 864337 pending
thanks

Hello,

Bug #864337 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/python-blessed.git/commit/?id=1c34af6

---
commit 1c34af6a5e7446c356fa145ee55d12810b8e5b8d
Author: Pierre-Elliott Bécue 
Date:   Tue Jan 2 19:06:12 2018 +0100

Update d/changelog

diff --git a/debian/changelog b/debian/changelog
index 2c62c5c..2ecde1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-blessed (1.14.2-2) unstable; urgency=medium
+
+  * Team upload.
+  * d/patches/0001: Remove all time-based to the millisecond assertions in
+test_keyboard.py. (Closes: #864337)
+
+ -- Pierre-Elliott Bécue   Tue, 02 Jan 2018 19:01:24 +0100
+
 python-blessed (1.14.2-1) unstable; urgency=medium
 
   * Team upload

Processed: Bug#864337 marked as pending

[Debian Bug Tracking System]

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

> tag 864337 pending
Bug #864337 [src:python-blessed] python-blessed: Non-determistically FTBFS due 
to unreliable timing in tests
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#886153: anything-el: A stale file lock of anything-c-adaptive-history breaks emacs batch processing

[H . -Dirk Schmitt]

Package: anything-el
Version: 1.287-2.1
Severity: critical

Problem description
---
If for some unknown reason an emacs file lock of the file 
`~/.emacsd/anything-c-adaptive-history` existing, batch
operation of emacs will never be finished.


Reproducing the lock issue
--
I don't know what has cause the stale lock on my machine, but it can be easily 
recreated as described below.

```
pkill emacs # ensure that emacs is not running
cd /root/.emacs.d
ln -s  ${USER}@${HOSTNAME}.${DOMAIN}.5423:1487632643 
.#anything-c-adaptive-history
```

Resulting problems
---

Now start emacs. Everything seems to be fine, but on quitting emacs you will 
see the question concerning the lock
waiting for any user input.

This seems in normal cases a minor malaise, but the impact if emacs is used for 
batch processing.
Please try the following with and without the stale lock.
`emacs  --no-init-file --batch`

Without the stale lock this command will finish after a short time.
With the lock, you will see the following output:

> Loading 00debian-vars...
> Loading 20apel...
> Loading 50a2ps...
> Loading 50anything-el...
> Loading 50auctex...
> Loading /usr/share/emacs/site-lisp/auctex.el (source)...
> Loading /usr/share/emacs/site-lisp/preview-latex.el (source)...
> Loading 50auto-complete-el...
> Loading 50auto-install-el...
> Loading 50autoconf...
> Loading 50develock-el...
> Loading 50devscripts-el...
> Loading 50dictionaries-common...
> Loading debian-ispell...
> Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...
> Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...
> Loading 50dictionary-el...
> Loading dictionary-init...
> Loading 50dpkg-dev-el...
> Loading 50emacs-goodies-el...
> Loading 50erlang-mode...
> Loading 50flim...
> Loading 50gnuplot-mode...
> Loading 50oneliner-el...
> Loading 50org-mode...
> Loading 50php-elisp...
> Loading 50psvn...
> Loading 50pymacs...
> Loading 50python-docutils...
> Loading 50python-mode...
> Loading 50texlive-lang-english...
> Loading 51debian-el...
> Loading 51mu-cite...
> Loading 51oneliner-el...
> Loading 51semi...
> Loading 65wl-beta...
> Loading 95c42_defaults (compiled; note, source file is newer)...
> Loading log-edit...
> Trailing whitespace highlighting is now ON.
> TAB highlighting is now ON.
> Loading /home/dschmi/.recentf...
> Cleaning up the recentf list...
> Cleaning up the recentf list...done (0 removed)
> Loading /usr/local/share/emacs/site-lisp/ob-eukleides.el (source)...
> Loading /home/dschmi/.emacs.d/anything-c-adaptive-history...
> [yas] Prepared just-in-time loading of snippets successfully.
> Loading systemd...
> Loading crontab-mode...
> Loading json-mode...
> Loading ldap-mode...
> Loading nagios-mode...
> Loading org-journal...
> Loading 99c42_keymap...
> Local Ispell dictionary set to british
> Starting new Ispell process aspell with british dictionary...
> ...ing-c-adaptive-history locked by xx@xx... (pid 5423): (s, q, p, ?)?

At this point the emacs is hanging.
Trying to answer the „lock“ prompt is not possible. You have to terminate the 
processing *SIGINT* (Ctrl+C) or killing it.


Why is this bug critical?
-

This bug report is related to bug #886024 – which describes how an unexpected 
problem like this renders debian package
installation unusable.



Further information
---
As requested by da...@tethera.net:
- /etc/emacs/site-start.d/50anything-el.el is not touched – the .deb 
distributed file is in charge.
- `ls -l  /etc/emacs/site-start.d/`
> -rw-r--r-- 1 root root 1.8K May 21  2014 00debian-vars.el
> -rw-r--r-- 1 root root 1.6K Apr  4  2014 50a2ps.el
> -rw-r--r-- 1 root root 1021 Oct 24  2014 50anything-el.el
> -rw-r--r-- 1 root root 1.3K Nov 19  2015 50auctex.el
> -rw-r--r-- 1 root root  891 Mar 28  2012 50auto-complete-el.el
> -rw-r--r-- 1 root root  729 Apr 28  2012 50autoconf.el
> -rw-r--r-- 1 root root  887 May  1  2012 50auto-install-el.el
> -rw-r--r-- 1 root root 1.2K Dec  2  2014 50develock-el.el
> -rw-r--r-- 1 root root 1.8K Oct 23  2015 50dictionaries-common.el
> -rw-r--r-- 1 root root  705 Nov  7  2011 50emacs-goodies-el.el
> -rw-r--r-- 1 root root 1.3K Jan 25  2015 50php-elisp.el
> -rw-r--r-- 1 root root  101 Dec 18  2015 50psvn.el
> -rw-r--r-- 1 root root  927 Jul 16  2014 50pymacs.el
> -rw-r--r-- 1 root root 1.6K Feb 11  2016 50python-mode.el
> -rw-r--r-- 1 root root  618 May 27  2015 50yasnippet.el
> -rw-r--r-- 1 root root  654 Nov  7  2011 51debian-el.el
> lrwxrwxrwx 1 root root   58 Aug 24 13:03 99c42_defaults.el -> 
/etc/c42CfgRepos/data/emacs/site-start.d/99c42_defaults.el

Bug#883636: marked as done (showq: does not start)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 17:34:26 +
with message-id 
and subject line Bug#883636: fixed in showq 0.4.1+git20161215~dfsg0-3
has caused the Debian Bug report #883636,
regarding showq: does not start
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.)


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

Package: showq
Version: 0.4.1+git20161215~dfsg0-2

Dear debian maintainers,

trying to launch showq (debian stretch here) doesn't work at all.
When ran from a terminal, it tells:
$ showq
ShowQ:out_1 # system:playback_1
ShowQ:out_2 # system:playback_2
ShowQ:out_3 # PulseAudio JACK Source:front-left
ShowQ:out_4 # PulseAudio JACK Source:front-right

Then a pop up windows appears telling:

Show Q encountered an unknown error.
Please report this error to the developers of the program.


Pushing the "OK" button, and it stops.

I've already reported this to upstream : 
https://github.com/evandelisle/showq/issues/29


Cheers,
Olivier
--- End Message ---
--- Begin Message ---
Source: showq
Source-Version: 0.4.1+git20161215~dfsg0-3

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated showq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Jan 2018 18:09:47 +0100
Source: showq
Binary: showq
Architecture: source
Version: 0.4.1+git20161215~dfsg0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 showq  - MIDI controllable audio player
Closes: 883636
Changes:
 showq (0.4.1+git20161215~dfsg0-3) unstable; urgency=medium
 .
   * Set dh/compat 11.
   * Hack prefix to get app started. (Closes: #883636)
 Thanks to James Cowgill 
   * Bump Standards.
   * Use git instead of cgit in VCS.
Checksums-Sha1:
 eb132b5aa810b8c9006f4b4141e71f325f76ca00 2230 
showq_0.4.1+git20161215~dfsg0-3.dsc
 f46443e4a24a4d2608e9e447b8cd4e586dfc3a8e 6588 
showq_0.4.1+git20161215~dfsg0-3.debian.tar.xz
 eb4d1d2244b32e5838aaa0b866b9e432fced9e3f 11723 
showq_0.4.1+git20161215~dfsg0-3_amd64.buildinfo
Checksums-Sha256:
 f4a26395c5858872eadf754fe5f1b41a6cb7b59d9663b750a146a244a13cba45 2230 
showq_0.4.1+git20161215~dfsg0-3.dsc
 37cbf88bc9ddbab39b75e7651883a10f4c902ac5e1ae7390911d3bb413b3b50e 6588 
showq_0.4.1+git20161215~dfsg0-3.debian.tar.xz
 5e740e2620289a6954aee924b45317d95806f96cb30de445af8a103ccf05737a 11723 
showq_0.4.1+git20161215~dfsg0-3_amd64.buildinfo
Files:
 63fc32267802f1834e845b88fb13dc77 2230 sound optional 
showq_0.4.1+git20161215~dfsg0-3.dsc
 295af70ab2c3876739d8e49d961154e3 6588 sound optional 
showq_0.4.1+git20161215~dfsg0-3.debian.tar.xz
 1dcf4261474ff0d90f2b79a40501b637 11723 sound optional 
showq_0.4.1+git20161215~dfsg0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESlQ1E9LfY1GoF46jWwGUVeK4T6UFAlpLvocVHG1pcmEubWlr
ZXNAc2V6bmFtLmN6AAoJEFsBlFXiuE+lBHMQALWcmlLYgkzJZc1VfLU8WeL/s03l
uMemUs/ds+m4RoTXNam43XLArClxFl2MhHpn2O4Z1XHlp4PqIBLwseUCVpPiR1vb
m9YPed7EOapIs3Efu227lAPXjdLrWLGpQnLlSb0uPoLJMj5Fy5aCqoBOGHVNeqQq
ww6MuGgZf0t0SSArpq/haCcn4EKnTUYWyBO7LZMjNvKpGe05Ta2J5s7pNdcR0qWH
X4BoYdQQXbqT01IbGcgjHTE49DFZ9RVGewLoz9dhmnPqHZy2Kzkn0arC7Qs1r0gy
25GX4rjh118ywqeioTlwcC2jFmsB/tmOT3vbrvqVSBFSdDdHId+YoaFWj9qF5OWL
0nENgNuh32OpznW9M3us5cgzIOi2stYAHhYizvsEBLq4q+cdZI/YIxLLcDRwwuZ+
h+lkAxYObbQSqkwMHQVLJUd/i+f9gTNd+eWvyzlfVyO4g5UxAQluR7nCaxEJ80Ut
Ij6hho63QfvDQ710pZA5LnLejqRQA7f8r1xZsPIy+B1kyXG6r9jdpEGSSq22WjEf
oVFY+owor4oypbXpzAQi9N8d09a59WYoEE2seqIwWWLyIGq7A2G9kYiVD2dOIPMP
hbY5hYD22s3maYjDuG9mLPbBWCi1rFv82/Hy5h9UX4xrpNoOuVfrP0D+9IzQ3U2C
qnBwPX6kmm6uyAks
=oqew
-END PGP SIGNATURE End Message ---

Bug#883986: openscad: FTBFS on mips/mipsel: virtual memory exhausted: Cannot allocate memory

[chrysn]

On Sun, Dec 10, 2017 at 03:52:04AM +0100, Andreas Beckmann wrote:
> Source: openscad
> openscad did run out of memory during the recent binNMU on mips/mipsel:
> 
> https://buildd.debian.org/status/package.php?p=openscad&suite=unstable

Thanks for the report. I'm waiting for porter box access on MIPS boxes
to resolve the issue.


signature.asc
Description: PGP signature

Processed: Bug#883636 marked as pending

[Debian Bug Tracking System]

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

> tag 883636 pending
Bug #883636 [showq] showq: does not start
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#885259: arandr: Depends on unmaintained pygtk

[Debian Bug Tracking System]

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

> severity 885259 important
Bug #885259 [src:arandr] arandr: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'
> thank you
Stopping processing here.

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

Bug#883636: marked as pending

[Jaromír Mikeš]

tag 883636 pending
thanks

Hello,

Bug #883636 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/showq.git/commit/?id=e3679b4

---
commit e3679b4de4437b81ad4a2e3f46074a830e1ff6da
Author: Jaromír Mikeš 
Date:   Tue Jan 2 18:12:12 2018 +0100

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index 5283fc4..551c8bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
-showq (0.4.1+git20161215~dfsg0-3) UNRELEASED; urgency=medium
+showq (0.4.1+git20161215~dfsg0-3) unstable; urgency=medium
 
   * Set dh/compat 11.
+  * Hack prefix to get app started. (Closes: #883636)
+Thanks to James Cowgill 
+  * Bump Standards.
+  * Use git instead of cgit in VCS.
 
- -- Jaromír Mikeš   Tue, 02 Jan 2018 17:46:56 +0100
+ -- Jaromír Mikeš   Tue, 02 Jan 2018 18:09:47 +0100
 
 showq (0.4.1+git20161215~dfsg0-2) unstable; urgency=medium
 

Bug#885273: Fwd: Bug#885273: diffuse: Depends on unmaintained pygtk

[Philipp Huebner]

> Thanks for giving me a heads up.  I plan on tackling a bunch of issues
> by re-writing most of Diffuse to use Python 3, the GObject bindings, and
> handle word wrap.

That's great news!

> Unfortunately this is a rather big task so it will
> take some time to complete. Hopefully, I will have something that is an
> improvement over the Python 2 implementation of Diffuse by the end of
> 2018.  Given Debian's release cadence so far, I expect the next Debian
> release to be around the end of 2019.  Is that close to when you expect
> Debian's next release to happen?

Yes, maybe a few months earlier.

BTW, I believe the Thai translations in https://bugs.debian.org/793352
are complete and waiting to be included, but I didn't realize that until
a few days ago.

Regards,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Bug#886141: visp: FTBFS on mips: six tests time out

[Aaron M. Ucko]

Source: visp
Version: 3.1.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips

Builds of visp for mips have been failing lately.  Part of the problem
is that all 12 mbtGenericTrackingDepth tests generally fail on
big-endian architectures, as I just reported (#886140).  On top of
that, six tests timed out on this specific architecture, as detailed at
https://buildd.debian.org/status/fetch.php?pkg=visp&arch=mips&ver=3.1.0-1&stamp=1514685910&raw=0:

  2 - testConversion (Timeout)
 23 - testMatrix (Timeout)
 27 - testMatrixPseudoInverse (Timeout)
 60 - testImgproc (Timeout)
 80 - testKeyPoint-5 (Timeout)
 81 - testKeyPoint-6 (Timeout)

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#886140: visp: FTBFS (big-endian): mbtGenericTrackingDepth tests fail

[Aaron M. Ucko]

Source: visp
Version: 3.1.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips

Builds of visp for big-endian architectures have been failing lately,
with errors in all 12 mbtGenericTrackingDepth tests.  The details vary
to some extent by architecture, but I suspect the root cause is the
same.  Specifically:

* On the 32-bit big-endian architectures mips and powerpc[*], these
  tests all fail with

terminate called after throwing an instance of 'std::bad_array_new_length'
  what():  std::bad_array_new_length

  which CTest reports as OTHER_FAULT.  (The mips build also
  encountered six other test failures, which I'll report separately.
  As for m68k[*], that build nominally succeeded only because builds
  there generally run with nocheck in DEB_BUILD_OPTIONS.)

* On s390x, these tests all encountered segmentation faults.

* On ppc64[*], these tests all failed with an unspecified "Exception:
  Other".

Could you please take a look?

Thanks!

[*] Admittedly not a release architecture.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#879482: marked as done (yt FTBFS on 32bit: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 16:21:46 +
with message-id 
and subject line Bug#879482: fixed in yt 3.4.0-3
has caused the Debian Bug report #879482,
regarding yt FTBFS on 32bit: test failures
to be marked as done.

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

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


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

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

...
==
ERROR: yt.utilities.lib.tests.test_alt_ray_tracers.test_cylindrical_ray_trace
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/yt/utilities/lib/tests/test_alt_ray_tracers.py", line 
65, in test_cylindrical_ray_trace
t, s, rztheta, inds = cylindrical_ray_trace(p1, p2, left_grid, right_grid)
  File "yt/utilities/lib/alt_ray_tracers.pyx", line 204, in 
yt.utilities.lib.alt_ray_tracers.cylindrical_ray_trace
tsect, tinds = ret[0], ret[1].astype('int64')
ValueError: Item size of buffer (8 bytes) does not match size of 'int_t' (4 
bytes)

==
ERROR: test_points_vr 
(yt.visualization.volume_rendering.tests.test_points.PointsVRTest)
--
Traceback (most recent call last):
  File 
"/<>/yt/visualization/volume_rendering/tests/test_points.py", line 
75, in test_points_vr
im = sc.render()
  File "/<>/yt/visualization/volume_rendering/scene.py", line 229, 
in render
bmp = self.composite(camera=camera)
  File "/<>/yt/visualization/volume_rendering/scene.py", line 529, 
in composite
source.render(camera, zbuffer=opaque)
  File "/<>/yt/visualization/volume_rendering/render_source.py", 
line 893, in render
zpoints(empty, z, px, py, dz, self.colors, self.radii, self.color_stride)
  File "yt/utilities/lib/misc_utilities.pyx", line 440, in 
yt.utilities.lib.misc_utilities.zpoints
idx = np.argsort(zs)
ValueError: Buffer dtype mismatch, expected 'int64_t' but got 'int'

--
Ran 1161 tests in 1361.004s

FAILED (errors=2)
debian/rules:37: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: yt
Source-Version: 3.4.0-3

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

Debian distribution maintenance software
pp.
BW Keller  (supplier of updated yt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Oct 2017 16:11:30 +
Source: yt
Binary: python-yt python3-yt
Architecture: source
Version: 3.4.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Team 

Changed-By: BW Keller 
Description:
 python-yt  - Framework for analyzing and visualizing simulation data (Python 2
 python3-yt - Framework for analyzing and visualizing simulation data (Python 3
Closes: 879482
Changes:
 yt (3.4.0-3) unstable; urgency=low
 .
   * Fix 32 bit FTBF.  Closes: #879482
Checksums-Sha1:
 39e0c5bff26ff70f147461724d3dbd65835a2fae 2291 yt_3.4.0-3.dsc
 d48c7456b9d728b0159a85e8c0640a6e2151ad82 38156 yt_3.4.0-3.debian.tar.xz
Checksums-Sha256:
 d59fdc2ca28dba370487439e524f8c7307f0b2fc89b27c4c9394c93905b491b4 2291 
yt_3.4.0-3.dsc
 81368729a9461c82ad7998b9d77aef2ed48b2c0c2c135dd86971716355e8395f 38156 
yt_3.4.0-3.debian.tar.xz
Files:
 5ca1ff11ec3bb42e80ffa555baf4f381 2291 python optional yt_3.4.0-3.dsc
 53ac6f369f177569cfb2448ff9de 38156 python optional yt_3.4.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAlpLrl8ACgkQmk9WvbkO
GL268hAAiAisX4PZLUCwsk3CK7iCXufDNB9dHhTcefuynJvj9bv2GnS0VeA4AiIv
XsYX3NoUiqXLIqItGSCo5muRltec+2Wl8oDoliw+s+ZAzxy6/UYkZYxSeU4N310w
oYWxQ97JOGuXz5XEcr4vMG3JauOzIlOGShQxYaLXyP

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

[James Cowgill]

Hi,

On 02/01/18 15:57, Aaron M. Ucko wrote:
> Source: ndpi
> Version: 2.2-1
> Severity: serious
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)
> User: debian-m...@lists.debian.org
> Usertags: mips
> 
> Builds of ndpi for mips, s390x, and the non-release architectures
> powerpc and ppc64 all failed because running the test suite hit the
> autobuilders' inactivity timeouts.  These timeouts are generous enough
> (600 minutes on ppc64, 150 minutes on the other three architectures)
> that hitting them generally indicates that something managed to hang
> or spin indefinitely.  However, I see that the hppa build ran for a
> long time before terminating on its own (albeit with test suite
> errors), so you may simply need to add progress indicators for the
> sake of slow architectures.  (These are inactivity timeouts, so any
> output to stdout or stderr resets them.)
> 
> Could you please take a look?

It so happens that I was having a brief look already :)

The ndpiReader application is the one that hangs.

Extract from example/ndpi_util.c:750
>   case MPLS_UNI:
>   case MPLS_MULTI:
> mpls = (struct ndpi_mpls_header *) &packet[ip_offset];
> label = ntohl(mpls->label);
> /* label = ntohl(*((u_int32_t*)&packet[ip_offset])); */
> workflow->stats.mpls_count++;
> type = ETH_P_IP, ip_offset += 4;
>
> while((label & 0x100) != 0x100) {
>   ip_offset += 4;
>   label = ntohl(mpls->label);
> }

The hang occurs inside the above while loop. Notice that the value
loaded into "label" inside the loop never changes and this is the only
variable the loop condition depends on. Therefore, if the initial loop
condition is true, the program will loop forever.

The reason why this happens only on big-endian may be related to the
definition of ndpi_mpls_header:
> PACK_ON
> struct ndpi_mpls_header
> {
>   u_int32_t label:20, exp:3, s:1, ttl:8;
> } PACK_OFF;

Firstly, the order of fields in a bitfield is ABI dependent so any
architecture could legitimately rearrange all the fields giving wrong
results. I also don't really understand what the programmer intended to
happen when invoking ntohl on a bitfield. Probably teh code needs
rewriting to not use ndpi_mpls_header.

James



signature.asc
Description: OpenPGP digital signature

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

[Aaron M. Ucko]

Source: ndpi
Version: 2.2-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips

Builds of ndpi for mips, s390x, and the non-release architectures
powerpc and ppc64 all failed because running the test suite hit the
autobuilders' inactivity timeouts.  These timeouts are generous enough
(600 minutes on ppc64, 150 minutes on the other three architectures)
that hitting them generally indicates that something managed to hang
or spin indefinitely.  However, I see that the hppa build ran for a
long time before terminating on its own (albeit with test suite
errors), so you may simply need to add progress indicators for the
sake of slow architectures.  (These are inactivity timeouts, so any
output to stdout or stderr resets them.)

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#883636: showq: does not start

[trebmuh]

Le 2018-01-02 12:44, James Cowgill a écrit :

...zip...


Note that the prefix does *not* have a trailing slash in debian/rules:

override_dh_auto_configure:
$(WAF) configure   --prefix=/usr


So the simple fix is to use "--prefix=/usr/", but arguably this is an
upstream bug as well since it should work with prefixes without 
trailing

slashes.


...zip...

Thank you very much James.
I've been testing a rebuild on a Stretch with this small change in 
d/rules and I'm able to launch ShowQ.


I've been letting upstream know about your workaround and inform them 
about the possibility to fix it upstream.
See 
https://github.com/evandelisle/showq/issues/29#issuecomment-354783402


Thanks again James, and enjoy 2018 sunrise.
Cheers.

Processed: slic3r: Binaries except slic3r cannot find Slic3r.pm

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.2.9+dfsg-6.1
Bug #886125 [slic3r] slic3r: Binaries except slic3r cannot find Slic3r.pm
Marked as found in versions slic3r/1.2.9+dfsg-6.1.

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

Bug#886125: slic3r: Binaries except slic3r cannot find Slic3r.pm

[Adrian Bunk]

Package: slic3r
Version: 1.2.9+dfsg-6.1~deb9u1
Severity: serious
Control: found -1 1.2.9+dfsg-6.1

The binaries shipped except slic3r cannot find Slic3r.pm
in the non-standard location, e.g.:

$ split_stl
Can't locate Slic3r.pm in @INC (you may need to install the Slic3r module) 
(@INC contains: /usr/bin/../lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/bin/split_stl line 14.
BEGIN failed--compilation aborted at /usr/bin/split_stl line 14.
$

Processed: Re: [Pkg-privacy-maintainers] Bug#862799: torbrowser-launcher: missing dependencies on libasound2 libdbus-glib-1-2 and libevent-2.0-5

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #862799 [torbrowser-launcher] torbrowser-launcher: missing dependencies on 
libasound2 libdbus-glib-1-2 and libevent-2.0-5
Severity set to 'serious' from 'normal'

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

Bug#886121: nullmailer: cannot be installed: Broken nullmailer:amd64 Depends on systemd-sysv:amd64

[David Bremner]

Thorsten Glaser  writes:

> Package: nullmailer
> Version: 1:2.1-5
> Severity: serious
> Justification: fails to install
> Control: notfound -1 1:2.1-3
>
> Investigating (0) nullmailer:amd64 < 1:2.1-3 -> 1:2.1-5 @ii umU Ib >
> Broken nullmailer:amd64 Depends on systemd-sysv:amd64 < none | 236-2 @un uH >
>   Considering systemd-sysv:amd64 106 as a solution to nullmailer:amd64 0
>   Holding Back nullmailer:amd64 rather than change systemd-sysv:amd64
>  Try to Re-Instate (1) nullmailer:amd64
> Done
> […]
> The following packages have been kept back:
>   nullmailer

I assume you have systemd-sysv held somehow and don't want to install
it?

The current state of nullmailer 2.x is that it requires systemd for
support of the daemon functionality.

Please see #884980, and #885537. Discussion of missing sysvinit support
should go to the latter.

d

Bug#886122: FTBFS: .../Vector.h:251:64: error: no matching function for call

[Adam Borowski]

Source: android-platform-frameworks-base
Version: 1:7.0.0+r33-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build:

In file included from include/androidfw/AssetDir.h:25:0,
 from libs/androidfw/AssetDir.cpp:22:
/usr/include/android/utils/Vector.h: In member function 'const 
android::Vector& android::Vector::operator=(const 
android::Vector&) const':
/usr/include/android/utils/Vector.h:251:64: error: no matching function for 
call to 'android::Vector::operator=(const android::VectorImpl&) const'
 VectorImpl::operator = (static_cast(rhs));
^
Tried on armhf amd64.  Log attached.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.15.0-rc6-00272-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


android-platform-frameworks-base_armhf.build
Description: inode/symlink

Bug#875688: libreoffice-report-builder: report builder inactive; only legacy reports can be created and run

[MAG4 Piemonte]

Hi Rene, upgrading to version 5.4.4-1 solve the problem ...
Thank you and regards!

Guido

Bug#886121: nullmailer: cannot be installed: Broken nullmailer:amd64 Depends on systemd-sysv:amd64

[Thorsten Glaser]

Package: nullmailer
Version: 1:2.1-5
Severity: serious
Justification: fails to install
Control: notfound -1 1:2.1-3

Investigating (0) nullmailer:amd64 < 1:2.1-3 -> 1:2.1-5 @ii umU Ib >
Broken nullmailer:amd64 Depends on systemd-sysv:amd64 < none | 236-2 @un uH >
  Considering systemd-sysv:amd64 106 as a solution to nullmailer:amd64 0
  Holding Back nullmailer:amd64 rather than change systemd-sysv:amd64
 Try to Re-Instate (1) nullmailer:amd64
Done
[…]
The following packages have been kept back:
  nullmailer

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Processed: nullmailer: cannot be installed: Broken nullmailer:amd64 Depends on systemd-sysv:amd64

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 1:2.1-3
Bug #886121 [nullmailer] nullmailer: cannot be installed: Broken 
nullmailer:amd64 Depends on systemd-sysv:amd64
Ignoring request to alter found versions of bug #886121 to the same values 
previously set

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