Bug#878181: Wrong path sent...

[xo0ox]

I deleted the contents of /var/lib/bluetooth/* not the rfkill files 
before reinstalling the packages and reinstalling. But I checked that 
all rfkill switches where set to 0.

Bug#878212: mon: fails to properly log errors from alert scripts

[Russell Coker]

Package: mon
Version: 1.3.2-1
Severity: normal

When an alert script returns non-zero that should be logged and treated
specially.  That's an unusually significant error because it means other
errors aren't being reported.

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

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

Versions of packages mon depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libtime-period-perl  1.20-8.2
ii  mon-client   1.2.0-2

Versions of packages mon recommends:
ii  bc   1.06.95-9+b3
pn  fping
pn  libauthen-pam-perl   
ii  libcgi-pm-perl   4.35-1
pn  libcrypt-ssleay-perl 
ii  libfilesys-df-perl   0.92-6+b1
ii  libmail-imapclient-perl  3.38-1
ii  libnet-dns-perl  1.07-1
pn  libnet-ldap-perl 
pn  libnet-telnet-perl   
ii  libproc-processtable-perl0.53-2
pn  libsnmp-perl 
pn  libstatistics-descriptive-perl   
pn  libtime-parsedate-perl   
ii  perl-modules-5.24 [libnet-perl]  5.24.1-3+deb9u2
ii  swaks20170101.0-1

Versions of packages mon suggests:
ii  mon-contrib  1.0+dfsg-4

-- Configuration Files:
/etc/mon/mon.cf changed [not included]

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/mon/alert.d/mailxmpp.alert (from mon package)

Bug#878158: lapack: debian/rules sed expression breaks for some LDFLAGS values

[Roberto C . Sánchez]

Of course, a better delimiter is one that is not already used in the
expression itself.  Perhaps the at symbol @.

-- 
Roberto C. Sánchez

Bug#878203: [pkg-apparmor] Bug#878203: AA breaks libvirt when running with kernel 4.13

[Seth Arnold]

Hello Michael, do you still have the DENIED lines from your kernel logs
when experiencing this problem? If so please share them here.

Thanks


signature.asc
Description: PGP signature

Bug#877461: closed by Andreas Tille <ti...@debian.org> (Bug#877461: fixed in logol 1.7.5-2)

[Andreas Beckmann]

Control: severity -1 normal

On 10/10/2017 02:57 PM, Debian Bug Tracking System wrote:
>* remove drmaa sym link as patches remove drmaa support

Oh, in that case we can lower the severity (for stable), since the
broken symlink is unused.


Andreas

Bug#876761: python3-ipython depends on python-pexpect instead of python3-pexpect

[Daniel Kahn Gillmor]

On Mon 2017-09-25 11:44:25 -0400, Daniel Kahn Gillmor wrote:
> python3-ipython should Depend: python3-pexpect, not python-pexpect.
>
> It looks like this is due to be fixed already in packaging commit
> 467513c63897c3182ffdc942a03355066d940706, so hopefully it will get
> fixed and released soon.

as a workaround for the moment, i've used equivs to build a placeholder:

--
$ cat ipython3-pexpect
Section: misc
Priority: optional
Standards-Version: 4.1.0

Package: ipython3-pexpect
Version: 1.0
Maintainer: Daniel Kahn Gillmor 
Depends: python3-pexpect
Provides: python-pexpect
Enhances: python3-ipython
Description: workaround for https://bugs.debian.org/876761
 python3-ipython should Depend: on python3-pexpect, not python-pexpect
$ equivs-build ipython3-pexpect
---

now i can install the generated ipython3-pexpect_1.0_all.deb (it showed
up in my $TMPDIR) and then install ipython3 without needing to install
python 2.x.

This is not what we'd really want to have for the long run though --
it'd be great to get this fixed!

 --dkg


signature.asc
Description: PGP signature

Bug#878211: crtmpserver can not be compilled from source

[root]

Package: crtmpserver
Version: 1.0~dfsg-5.3
Severity: normal

Dear Maintainer,

#apt-get source crtmpserver
Getting source crtmpserver, it can be configured to compile.
I have compilled it a long ago on Debian 8 with my patches to prevent
anonymous live streaming. That binary compilation is working on Debian 9
after upgrading from Debian 8, but I can't make it from source now and
I do not know how to send my patches to contributors.


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

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

Versions of packages crtmpserver depends on:
ii  crtmpserver-apps   1.0~dfsg-5.3
ii  crtmpserver-libs   1.0~dfsg-5.3
ii  libc6  2.24-11+deb9u1
ii  libgcc11:6.3.0-18
ii  liblua5.1-05.1.5-8.1+b2
ii  libssl1.0.21.0.2l-2
ii  libstdc++6 6.3.0-18
ii  libtinyxml2.6.2v5  2.6.2-4

crtmpserver recommends no packages.

crtmpserver suggests no packages.

-- Configuration Files:
/etc/default/crtmpserver changed:
ENABLED="yes"
DAEMON_USER="root"
DAEMON_ARGS="--daemon"
DAEMON_CONF="/root/app/crtmpserver/builders/cmake/crtmpserver/crtmpserver.lua"

/etc/init.d/crtmpserver changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="C++ RTMP Server"
NAME=crtmpserver
WD_PATH=/root/app/crtmpserver/builders/cmake
DAEMON=$WD_PATH/crtmpserver/crtmpserver
DAEMON_ARGS=" --daemon "
DAEMON_CONF="$WD_PATH/crtmpserver/crtmpserver.lua"
DAEMON_USER="root"
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
ENABLED="no"
[ -r /etc/default/$NAME ] && . /etc/default/$NAME
[ -x $DAEMON ] || exit 0
[ -r $DAEMON_CONF ] || exit 0
[ $ENABLED = "yes" ] || exit 0
. /lib/init/vars.sh
. /lib/lsb/init-functions
DAEMON_UID=$(getent passwd ${DAEMON_USER} | cut -d":" -f3)
if [ -z "${DAEMON_UID}" ]; then
echo "Error: User ${DAEMON_USER} does not exist."
exit 1
fi
UID_ARG=" --uid=${DAEMON_UID} "
do_start()
{
cd $WD_PATH
start-stop-daemon --start --quiet --chdir $WD_PATH --pidfile $PIDFILE 
--exec $DAEMON --test > /dev/null \
|| return 1
start-stop-daemon --start --quiet --chdir $WD_PATH --pidfile $PIDFILE 
--exec $DAEMON -- \
$DAEMON_ARGS $UID_ARG $DAEMON_CONF \
|| return 2
}
do_stop()
{
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile 
$PIDFILE --name $NAME
RETVAL="$?"
[ "$RETVAL" = 2 ] && return 2
start-stop-daemon --stop --quiet --oknodo --retry=INT/30/KILL/5 --exec 
$DAEMON
[ "$?" = 2 ] && return 2
rm -f $PIDFILE
return "$RETVAL"
}
case "$1" in
  start)
log_daemon_msg "Starting $DESC " "$NAME"
do_start
case "$?" in
0|1) log_end_msg 0 ;;
2) log_end_msg 1 ;;
esac
  ;;
  stop)
log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) log_end_msg 0 ;;
2) log_end_msg 1 ;;
esac
;;
  status)
   status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
   ;;
  restart)
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
  0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
  *)
# Failed to stop
log_end_msg 1
;;
esac
;;
  force-reload)
restart
;;
  *)
echo "Usage: $SCRIPTNAME {start|stop|status|restart}" >&2
exit 3
;;
esac
:


-- no debconf information

Bug#806852: Why hasn't the "sulogin --force" patch been merged yet?

[Stijn van Drongelen]

Hi everyone,

Today, I was fiddling around a bit with nVidia drivers. I was fed up
with the constant screen tearing, and decided to try fixing it once more.
In the end, I hit a fatal bug in nvidia_drm that triggers when X starts.

This taught me two things:

1) I really should back up more often.
2) I really should understand solutions before applying them.

I could recover my system, if only I could prevent X from loading before
I can revert the settings by moving and deleting some files. I rebooted
and tried starting the rescue mode.

This taught me two things:

3) The behaviour described in this bugreport exists.
4) The people responsible for resolving this bug are avoiding any kind
   of honest security analysis.

Let's assume for a second that the Debian installer offers the option
to password-protect GRUB. When configured properly, this prevents an
unauthenticated user from opening the console, editing options, and
from starting specific boot variants (such as rescue mode; see [1]).
The fact that the Debian installer doesn't offer this option is IMO
not merely something that warrants a feature request, but a huge glaring
security problem.

Let's also assume that, whoever installed the system, had the knowledge
and forethought to lock down any options in the BIOS that would allow
anyone from booting anything else than that password-protected GRUB.

That should match Michael Biebl's example scenario in message 31 of
#802211. Now, tell me:

Once an attacker has managed to start rescue mode,
what exactly is one extra root password going to accomplish?!

For a simplistic security configuration of GRUB, there is just one
password for both editing commands and activating the recovery mode.
So, if you're able to start recovery mode because you managed to get
that password, then that same password would also allow you to start
"init=/bin/bash" and bypass root logon anyway.

You might then want to distinguish between a recovery user (who may
activate the recovery mode option) and a real superuser (who may issue
arbitrary GRUB commands). Then, the recovery user would indeed still
have to punch in the root password, so an attacker would need to steal
two passwords rather than just one. However, you'll have to already
configure some less than trivial authentication and authorization
in GRUB. Why would you want to duplicate that effort with sulogin
parsing /etc/passwd if you somehow know beforehand that the root account
is enabled? Is there really a plausible scenario where you can steal
the password of the GRUB recovery user, but you can't steal the second
password that user needs before any recovery can be performed? I doubt
that barrier reduces more risk than it costs, especially when there
is a sane password policy in effect.

I urge the maintainers of the systemd package to outright dismiss this
kind of scenarios. Those hand-wavy excuses only arise because paranoia
makes one want to defend existing practices. Security is about
mitigating risks, which instead requires clear and well-founded
arguments. And sometimes that means you'll conclude you have to do
things in a way you're not used to, such as entirely disabling root
accounts.

If you truly care about security, you know very well that any process
running as root is a liability (even when you're running a kiosk),
and you also know very well that disabling "login as root" for
**normal, everyday operation** is part of any healthy security policy
and an important mitigation w.r.t. automated attacks.

Rescue mode is reserved for special occasions, so it deserves
a tailor-made solution -- as long as that solution doesn't affect
normal, everyday operation. Moving the responsibility of securing rescue
mode to the bootloader, which needs to be secured *anyway*, seems like
a suitable solution.

Enabling the root account by setting a password, or even setting a flag
that indicates that the account is only for rescue mode (as suggested
by Kevin Locke), is not a suitable solution. It would place the root
account back in the realm of "normal, everyday operation", where people
who (let alone: software that) didn't get the memo about that special
flag will probably not enforce the intended policy, and where plenty of
software will happily make authentication attempts for root when asked
by an otherwise unauthenticated user (see for instance CUPS' web
interface).

If someone is stubborn enough to wave away modern best practices,
let them do so, but let them also deal with the fallout. A big screaming
warning that their pathological case is insecure should suffice. But for
sake of the rest of us, who just want to use Debian in a sane and
safe way, please prioritise rootless installations, throw in
the `--force` flag and fix this 720-days-and-counting-old bug (you can
always add that "but don't --force when root is enabled" logic later).
Alternatively, have the guts to admit that you think that rootless
installations are a misfeature and tell the debian-installer to 

Bug#878210: libnginx-mod-rtmp: Broken dependencies for libnginx-mod-rtmp

[root]

Package: libnginx-mod-rtmp
Severity: normal

Dear Maintainer,

#apt-get install libnginx-mod-rtmp

The following packages have unmet dependencies:
 libnginx-mod-rtmp : Depends: nginx-common (= 1.13.3-1~bpo9+1) but 
1.10.3-1+deb9u1 is to be installed
E: Unable to correct problems, you have held broken packages.

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

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

Versions of packages libnginx-mod-rtmp depends on:
ii  libc6 2.24-11+deb9u1
pn  nginx-common  

libnginx-mod-rtmp recommends no packages.

libnginx-mod-rtmp suggests no packages.

Bug#874402: debian mirror kambing.ui.edu issues

[Tonny Adhi Sabastian]

On 2017-10-10 18:05, Peter Palfrader wrote:

On Mon, 04 Sep 2017, Peter Palfrader wrote:


It seems your mirror isn't updating correctly at the moment.


The mirror has been out of date for over a week.

Accordingly, I am removing it from out list of mirrors for now.

If you want to bring it back, please do and fill in
 https://www.debian.org/mirror/submit
again.

Thanks for having provided this service.


Thank you for your notification Peter. There seems to be problem when we 
doing mirror within our ISP. Currently we are using mirrors.kernel.org.


I will resubmit Kambing again after our synchronization finished.

#regards

--
Tonny Adhi Sabastian, M. Kom.
Part Time Lecturer - Faculty of Computer Science
DevOps Head @ Peentar
Gembala Kambing UI -- http://kambing.ui.ac.id
Registered Linux User #345051
Staff UI Blog : http://staff.blog.ui.ac.id/t.a.sabastian

Bug#878209: apcupsd: please provide a split package without X11 deps

[Jon]

Package: apcupsd
Version: 3.14.14-1
Severity: normal

The new package adds in a dependecy on x11 for a package with heavy
server use. Please split the package so that servers do not need to add
an extra 65MB of x11 libs that they dont really need.

-- apt output below 

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following NEW packages will be installed:
   fontconfig (2.12.3-0.2)
   gconf-service (3.2.6-4+b1)
   gconf2-common (3.2.6-4)
   gnome-icon-theme (3.12.0-2)
   gtk-update-icon-cache (3.22.24-1)
   hicolor-icon-theme (0.17-1)
   libatk1.0-0 (2.26.0-2)
   libatk1.0-data (2.26.0-2)
   libavahi-client3 (0.7-3)
   libavahi-common-data (0.7-3)
   libavahi-common3 (0.7-3)
   libcairo2 (1.14.10-1)
   libcroco3 (0.6.12-1)
   libcups2 (2.2.4-8)
   libdatrie1 (0.2.10-5)
   libdbus-1-3 (1.11.20-1)
   libdbus-glib-1-2 (0.108-2)
   libgconf-2-4 (3.2.6-4+b1)
   libgdk-pixbuf2.0-0 (2.36.11-1)
   libgdk-pixbuf2.0-common (2.36.11-1)
   libgraphite2-3 (1.3.10-5)
   libgtk2.0-0 (2.24.31-2)
   libgtk2.0-common (2.24.31-2)
   libharfbuzz0b (1.5.1-1)
   libpango-1.0-0 (1.40.12-1)
   libpangocairo-1.0-0 (1.40.12-1)
   libpangoft2-1.0-0 (1.40.12-1)
   libpixman-1-0 (0.34.0-1)
   librsvg2-2 (2.40.18-1)
   librsvg2-common (2.40.18-1)
   libthai-data (0.1.26-3)
   libthai0 (0.1.26-3)
   libxcb-render0 (1.12-1)
   libxcb-shm0 (1.12-1)
   libxcomposite1 (1:0.4.4-2)
   libxcursor1 (1:1.1.14-3)
   libxdamage1 (1:1.1.4-3)
   libxext6 (2:1.3.3-1+b2)
   libxfixes3 (1:5.0.3-1)
   libxi6 (2:1.7.9-1)
   libxinerama1 (2:1.1.3-1+b3)
   libxrandr2 (2:1.5.1-1)
   libxrender1 (1:0.9.10-1)
The following packages will be upgraded:
   apcupsd (3.14.14-0.3 => 3.14.14-1)
1 upgraded, 43 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/22.5 MB of archives.
After this operation, 65.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Bug#877948: aptitude needs to improve

[Anonymous]

Package: aptitude
Followup-For: Bug #877948

Mr. Kalnischkies,

I really appreciate your helpful and detailed reply, as well as your
good advice.

I must say though that you should not have had to explain the SHA1
limitation - that's something aptitude should have done.  I've always
found the user feedback from aptitude quite lacking w.r.t errors (and
reported it 4 years ago):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706183

How could I (as an apt team outsider) have known that the (poorly
worded) "invalid" signature error was due to use of a substandard
algorithm?  I ran aptitude with debugging output enabled, and it gave
no further information about this.  The man page for aptitude also
says nothing about the subjective criteria in play for validation.

BTW, I have a couple new bug reports coming to hopefully mitigate the
report herein being repeated by others.

-- Package-specific info:
Terminal: screen
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.11 compiled at Nov  8 2014 13:34:39
Compiler: g++ 4.9.1
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.4.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20140913
  cwidget version: 0.5.17
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x7ffd2e9f5000)
/usr/lib/torsocks/libtorsocks.so (0x7ffb63a8)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 
(0x7ffb6371)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7ffb634da000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7ffb632b)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7ffb630aa000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7ffb62d94000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7ffb62acb000)
libboost_iostreams.so.1.55.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7ffb628b3000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7ffb624a2000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ffb62285000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ffb61f7a000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ffb61c79000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ffb61a63000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ffb616b8000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ffb614b4000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7ffb612b1000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ffb61096000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7ffb60e86000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ffb60c63000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ffb60a5b000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7ffb60856000)
/lib64/ld-linux-x86-64.so.2 (0x7ffb642e5000)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common   0.6.11-1
ii  libapt-pkg4.121.0.9.8.3
ii  libboost-iostreams1.55.0  1.55.0+dfsg-3
ii  libc6 2.19-18+deb8u6
ii  libcwidget3   0.5.17-2
ii  libgcc1   1:4.9.2-10
ii  libncursesw5  5.9+20140913-1+b1
ii  libsigc++-2.0-0c2a2.4.0-1
ii  libsqlite3-0  3.8.7.1-1+deb8u2
ii  libstdc++64.9.2-10
ii  libtinfo5 5.9+20140913-1+b1
ii  libxapian22   1.2.19-1+deb8u1

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-doc]  0.6.11-1
ii  libparse-debianchangelog-perl   1.2.0-1.1
ii  sensible-utils  0.0.9

Versions of packages aptitude suggests:
ii  apt-xapian-index  0.47
pn  debtags   
ii  tasksel   3.31+deb8u1

-- no debconf information

Bug#878208: graphite-web: Error when rendering errors

[Lee Begg]

Package: graphite-web
Version: 1.0.2+debian-2
Severity: normal

Dear Maintainer,

After installing the testing version of graphite-web on stable, if there is an 
error when
accessing a web page the error page also errors with

TypeError: context must be a dict rather than Context

Using a Context is no longer permitted, but line 8 of 
/usr/lib/python2.7/dist-packages/graphite/views.py creates
a Context. Removing the Context from around the dict corrects the issue.


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

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

Versions of packages graphite-web depends on:
ii  adduser3.115
ii  python 2.7.13-2
ii  python-cairo   1.8.8-2.2
ii  python-django  1:1.11.5-2
ii  python-django-tagging  1:0.4.5-1
ii  python-pyparsing   2.1.10+dfsg1-1
ii  python-scandir 1.6-1
ii  python-simplejson  3.11.1-1+b1
ii  python-tz  2017.2-2
ii  python-urllib3 1.21.1-1
ii  python-whisper 1.0.2-1

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
ii  graphite-carbon  1.0.2-1
pn  libapache2-mod-wsgi  
pn  python-ldap  
pn  python-memcache  
pn  python-mysqldb   

-- no debconf information

Bug#877146: Bug#877329: Bug#877146: update to runc (1.0.0~rc4) breaks docker

[Tianon Gravi]

On 10 October 2017 at 12:59, Tianon Gravi  wrote:
> I've been working on a "docker-containerd" package today (since that's
> going to be useful regardless), and found that there are other
> packages needed which depend on
> "golang-github-opencontainers-runc-dev", so we're going to have to end
> up with either splitting all the deps too, or going with Provides and
> hoping for the best compatibility-wise (and perhaps splitting only
> if/when there's an actual compatibility divergence for one of the
> deps).

Alright, I've managed to get everything to a working state.  Upload
for "docker-runc" is up (with appropriate maintainer), and a
"docker-containerd" package should be hitting NEW shortly.  Once
"docker-containerd" is accepted, then I can upload the fixed
"docker.io" package.


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#878207: graphite-web: Migration files missing

[Lee Begg]

Package: graphite-web
Version: 1.0.2+debian-2
Severity: important

Dear Maintainer,

The migration files for the graphite sub apps are missing. Without these, 
running

$ graphite-manage migrate

on a fresh install doesn't create all the tables required to run graphite web.
No pages are available, therefore the package is unusable.

Apps that need migrations:
 * graphite.account
 * graphite.dashboard
 * graphite.events
 * graphite.url_shortener



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

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

Versions of packages graphite-web depends on:
ii  adduser3.115
ii  python 2.7.13-2
ii  python-cairo   1.8.8-2.2
ii  python-django  1:1.11.5-2
ii  python-django-tagging  1:0.4.5-1
ii  python-pyparsing   2.1.10+dfsg1-1
ii  python-scandir 1.6-1
ii  python-simplejson  3.11.1-1+b1
ii  python-tz  2017.2-2
ii  python-urllib3 1.21.1-1
ii  python-whisper 1.0.2-1

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
ii  graphite-carbon  1.0.2-1
pn  libapache2-mod-wsgi  
pn  python-ldap  
pn  python-memcache  
pn  python-mysqldb   

-- no debconf information

Bug#878206: RFS: jamnntpd/1.3-1 - NNTP Server allowing access a JAM messagebase

[Robert J. Clay]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "jamnntpd"

* Package name: jamnntpd
  Version : 1.3-1
  Upstream Author : Johan Billing 
  URL : http://ftnapps.sourceforge.net/jamnntpd.html
* License : permissive
  Section : news

It builds those binary packages:

jamnntpd   - NNTP Server allowing newsreaders to access a JAM messagebase

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/jamnntpd

Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/j/jamnntpd/jamnntpd_1.3-1.dsc

More information about  JamNNTPd can be obtained from
http://ftnapps.sourceforge.net/jamnntpd.html.

Changes since the last upload:

  * New Upstream Release.
  * Changes to debian/control:
  Use https URL for the 'Vcs-Git' keyword.
  Use https URL for the 'Vcs-Browser' keyword.
  Declare compliance with Debian Policy 4.1.1.
  Add 'lsb-base (>= 3.0-6)' to the Depends setting.
  Remove the 'jamnntpd-dbg' stanza  as no longer necessary.
  Update the Debhelper Build-Depends version to '>= 9.20151219'.
  * Changes to debian/copyright:
  Change 'Copyright-Format 1.0' URL to use HTTPS.
  Update copyright years for the 'debian/*' Files stanza.
  Add Robert James Clay to the 'Files: *' stanza.
  * Changes to debian/rules:
  Add setting of hardening flags for package build.
  Update 'override_dh_strip' target for dbgsym migration.


Also, I request that jamnntpd be added to the rest of my packages that
I can upload as a Debian Maintainer, under my email address
'j...@rocasa.us'.


-- 
Robert James Clay, DM
rjc...@gmail.com, j...@rocasa.us
Key ID: 4096/198CAB6F43B7EA9A

Bug#878205: please drop transitional package autofs5-hesiod

[Holger Levsen]

Package: autofs5-hesiod,autofs5-hesiod,autofs5
Version: 5.1.2-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop the transitional packages autofs5, autofs5-hesiod and autofs5-ldap
for buster, as they have been released with wheezy, jessie and stretch already.

Thanks for maintaining autofs!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878204: please drop transitional package libatk-adaptor-data

[Holger Levsen]

Package: libatk-adaptor-data
Version: 2.26.0-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package libatk-adaptor-data for buster, as it has been 
released with jessie and stretch.

Thanks for maintaining at-spi2-atk!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878203: AA breaks libvirt when running with kernel 4.13

[Michael Biebl]

Package: apparmor
Version: 2.11.0-11
Severity: serious

After the kernel upgrade from 4.12 to 4.13 my KVM/libvirt instances
failed to start:
Okt 10 19:24:44 pluto libvirtd[673]: 2017-10-10 17:24:44.404+: 797: error : 
virProcessRunInMountNamespace:1159 : internal error: child reported: Kernel 
does not provide mount namespace: Permission denied

Disabling AppArmor made libvirt work again.
There seems to be an incompatibility between the 4.13 kernel and
AppArmor. Please reassign if you think this is a bug in the kernel.

I've decided to mark this as RC, as breaking KVM is a rather severe
regression which needs to be fixed for buster.

A quick internet search turns up
https://forums.opensuse.org/showthread.php/527394-KVM-guest-will-not-start-with-latest-version-of-kernel
and following that
https://www.redhat.com/archives/libvir-list/2017-September/msg00546.html

Regards,
Michael


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

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

Versions of packages apparmor depends on:
ii  debconf  1.5.63
ii  init-system-helpers  1.49
ii  libapparmor-perl 2.11.0-11
ii  libc62.24-17
ii  lsb-base 9.20170808
ii  python3  3.5.3-3

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles2.11.0-11
pn  apparmor-profiles-extra  
ii  apparmor-utils   2.11.0-11

-- debconf information excluded

Bug#878202: please drop transitional package autoconf-gl-macros

[Holger Levsen]

Package: autoconf-gl-macros
Version: 20160916-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package autoconf-gl-macros for buster, as it has been
released with jessie and stretch.

Thanks for maintaining autoconf-archive!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878201: please drop transitional packages kdemultimedia-kio-plugins and kdemultimedia-dev

[Holger Levsen]

Package: kdemultimedia-kio-plugins,kdemultimedia-dev
Version: 4:16.08.3-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop the transitional packages kdemultimedia-kio-plugins and
kdemultimedia-dev for buster, as they have been released with jessie and
stretch already.

Thanks for maintaining audiocd-kio!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878200: please drop transitional package asterisk-prompt-it

[Holger Levsen]

Package: asterisk-prompt-it
Version: 1:1.4.22+mm20110907-3
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package  for buster, as it has been released with 
wheezy, jessie and stretch.

Thanks for maintaining asterisk-prompt-it!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878198: please drop transitional package gperf-ace

[Holger Levsen]

Package: gperf-ace
Version: 6.3.3+dfsg-1.2
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package  for buster, as it has been released with 
wheezy, jessie  and stretch.

Thanks for maintaining ace!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878199: please drop transitional package libalberta2-dev

[Holger Levsen]

Package: libalberta2-dev
Version: 3.0.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package  for buster, as it has been released with 
jessie and stretch.

Thanks for maintaining alberta!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#747629: Problem still exists in systemd 234-3

[Loyall, David]

Hi.  I just encountered this bug.  I'm using systemd 234-3 on a fresh install.

The advice here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747629#15 
worked for me.

Cheers,
--Dave

Bug#878197: Mutt destroys colors I set as default

[David Lawyer]

Package: mutt
Version: 1.7.1-5

Here's the /etc/rc.local script I use to set colors.
Note that I send ESC[8] to set as default.  Other programs such as vim
restore the default colors after exiting but mutt doesn't nor does it use
these colors.

# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.   By default this script does nothing.

# Setting terminal colors  done here since it's done last.  If done sooner
# they interfere with boot display

#  is esc and not the 2 chars ^[.  ESC[8] makes bg and fg indicies weak
# defaults = seterm -store.  The reset command resets the color pallete.
# RGB=rrggbb (6 hex digits) =red,green,blue. P7rrggbb makes color 7
# (background 47) this defined RGB palette color.  Then ESC[47;30m applies
# it.  

echo "Set colors and cursor on virtual terminals from /etc/rc.local"

#Colors:
#Set palatte color first with P seq.
echo "]P777ee99  [8]"> /dev/tty1 #my lt. green
echo "]P755aabb " [8]> /dev/tty2 #my lt. cyan
echo "[8]" > /dev/tty3 #7-grey #standard light white (grey)
echo "]P7dd9988 " [8]> /dev/tty4 #my pink

Bug#840830: [Fwd: Re: mark gnome-mime-data Multi-Arch: foreign]

[Michael Biebl]

Am 11.10.2017 um 00:19 schrieb Manuel A. Fernandez Montecelo:
> Control: tags -1 + pending
> 
> Forwarding to the correct bug report now...

Feel free to go ahead with the NMU directly.

You might as well orphan the package while at it.
The Debian GNOME team doesn't have interest in that package anymore and
is most likely not going to touch it in the future either.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#878196: libopenmpt0: Illegal instruction on mipsel arch

[gperreal]

Package: libopenmpt0
Version: 0.3.1-1
Severity: important
Tags: upstream

Dear Maintainer,

I have encountered this bug while trying to use minidlnad/stable, which depends
on libopenmpt0. It crashes with an "illegal instruction" error. I have found
that the illegal instruction is in libopenmpt0 using gdb.

I have tried to recompile libopenmpt0 from Debian source to no avail. I have 
also
downloaded and compiled the upstream sources, both 0.2.8760-beta27 and 0.3.1,
with no more success: the compiled binary does not pass the provided tests.
I finally tried to install the latest version from testing, with the
same results.

I am wondering about an hardware/cross-compilation problem. The system runs on
a SoC: MediaTek MT7621 ver:1 eco:3 (CPU: MIPS 1004Kc V2.15).

Best Regards,
Guillaume Perréal.

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (400, 'testing')
Architecture: mipsel (mips)

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

Versions of packages libopenmpt0 depends on:
ii  libc6   2.24-11+deb9u1
ii  libgcc1 1:6.3.0-18
ii  libmpg123-0 1.23.8-1+b1
ii  libstdc++6  6.3.0-18
ii  libvorbis0a 1.3.5-4
ii  libvorbisfile3  1.3.5-4
ii  zlib1g  1:1.2.8.dfsg-5

libopenmpt0 recommends no packages.

libopenmpt0 suggests no packages.

-- no debconf information

Bug#871702: Latest Stretch qemu-system-i386 process balloons in Xen Dom0 RAM, crashes DomU

[Darius Spitznagel]

Hello,

cannot tell if it works now or not > migrated all hosts to KVM.

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

[Francois Marier]

On 2017-10-10 at 21:37:30, Ian Campbell wrote:
> Sorry, looks like I accidentally missed out a hunk in the orignal patch
> I sent, see below. Like last time note the mode as well as the content
> change.
> 
> Sorry again for the confusion.

Thanks. That was the problem.

I've uploaded the package. Let me know whether it works for you.

Francois

Bug#868582: skimage (was: Re: Bug#729956: Python 3 Statsmodels & Pandas)

[Yaroslav Halchenko]

On Tue, 10 Oct 2017, Yuri D'Elia wrote:

> On Sat, Sep 16 2017, Yuri D'Elia wrote:
> > Looking at python3-skimage-lib (which also requires a rebuild), it seems
> > that the package failed to pass some tests.

> > Bug #868582 even includes a patch to update to 0.13 [and disables some
> > test failures].

> Has anyone had a chance to look at skimage btw?

my bad 

will look into updating skimage now. thanks for the buzz

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#840830: [Fwd: Re: mark gnome-mime-data Multi-Arch: foreign]

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending

Forwarding to the correct bug report now...

--
Manuel A. Fernandez Montecelo 
--- Begin Message ---

Control: tags -1 + pending


Hi,

2016-10-15 13:39 Helmut Grohne:

Package: gnome-mime-data
Version: 2.18.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gnome-vfs

gnome-vfs cannot be cross built from source, because its build
dependency on gnome-mime-data is unsatisfiable. In general, dependencies
on Architecture: all packages are cross unsatisfiable unless they are
marked Multi-Arch: foreign.

In this case, the marking looks correct, because gnome-mime-data is
Architecture: all and doesn't have any maintainer scripts or
dependencies. Please consider applying the attached patch.


This package is a build-dependency of gnome-vfs, which in turn is a
build-dependency of many others, so I think that it's important that
this fix is applied.

I uploaded an NMU to delayed/10 directly, since the package hasn't seen
an upload in 10+ years; but please let me know if you prefer me to
cancel it.

.debdiff attached.


Cheers.
--
Manuel A. Fernandez Montecelo 

diff -u gnome-mime-data-2.18.0/debian/changelog 
gnome-mime-data-2.18.0/debian/changelog
--- gnome-mime-data-2.18.0/debian/changelog
+++ gnome-mime-data-2.18.0/debian/changelog
@@ -1,3 +1,14 @@
+gnome-mime-data (2.18.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Modifying d/control.in rather than d/control for the fix of Helmut to
+take effect
+
+  [ Helmut Grohne ]
+  * Mark Multi-Arch: foreign. (Closes: #840830)
+
+ -- Manuel A. Fernandez Montecelo   Tue, 10 Oct 2017 23:27:05 
+0200
+
 gnome-mime-data (2.18.0-1) unstable; urgency=low
 
   * Add a get-orig-source target to retrieve the upstream tarball.
diff -u gnome-mime-data-2.18.0/debian/control 
gnome-mime-data-2.18.0/debian/control
--- gnome-mime-data-2.18.0/debian/control
+++ gnome-mime-data-2.18.0/debian/control
@@ -13,6 +13,7 @@
 
 Package: gnome-mime-data
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: base MIME and Application database for GNOME.
  This module contains the base MIME and Application database for GNOME.
diff -u gnome-mime-data-2.18.0/debian/control.in 
gnome-mime-data-2.18.0/debian/control.in
--- gnome-mime-data-2.18.0/debian/control.in
+++ gnome-mime-data-2.18.0/debian/control.in
@@ -9,6 +9,7 @@
 
 Package: gnome-mime-data
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: base MIME and Application database for GNOME.
  This module contains the base MIME and Application database for GNOME.
--- End Message ---

Bug#838866: vorbis-tools FTCBFS: does not honour DEB_BUILD_OPTIONS=nocheck

[Manuel A. Fernandez Montecelo]

Control: tags -1 - pending

Sorry for the last message to this bug report (#15, "Re: mark
gnome-mime-data Multi-Arch: foreign"), the notice of NMU is obviously
wrong and intended to another package.


--
Manuel A. Fernandez Montecelo 

Bug#878195: nautilus-dropbox: please drop recommends on python-gpgme

[Mattia Rizzolo]

Package: nautilus-dropbox
Version: 2015.10.28-1

Dear maintainer,

python-gpgme has been removed from the archive, please stop recommending
that package.

See https://bugs.debian.org/876844 for more information.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#872251: libvoikko-dev is wrongly marked Multi-Arch: foreign

[Manuel A. Fernandez Montecelo]

Hi,

2017-08-15 12:20 Helmut Grohne:

Package: libvoikko-dev
Version: 4.1.1-1
Severity: important
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:tmispell-voikko

tmispell-voikko fails to cross build from source, because it cannot find
-lvoikko in the public shared library search path. It requested
libvoikko-dev its Build-Depends. The build architecture libvoikko-dev
was installed, because libvoikko-dev is wrongly marked Multi-Arch:
foreign.

libvoikko-dev was probably marked Multi-Arch: foreign, because it also
contains tools in /usr/bin that are expected to be executable. For
practical cross building, those tools will need to be installed for a
different architecture than the .so symlink. Thus the only viable long
term solution is to split libvoikko-dev into two packages, one of them
being Multi-Arch: foreign and the other Multi-Arch: same. Typically, the
package containing the programs would be called libvoikko-dev-bin and
libvoikko-dev would depend on it.

As a short term solution (closing this bug), please remove Multi-Arch:
foreign from libvoikko-dev as it does more harm than good.


This seem to be an important package to build enchant and, through it,
many other packages.  So I think that it would be nice if this is
solved.

Will it help if I prepare an NMU?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#878191: Error in `/usr/bin/mplayer': corrupted double-linked list: 0x0000560ab80de850

[Brad Barnett]

Some info.

It seems that the default for probesize might be 500:

https://ffmpeg.org/ffprobe-all.html

probesize integer (input)

Set probing size in bytes, i.e. the size of the data to analyze to
get stream information. A higher value will enable detecting more
information in case it is dispersed into the stream, but will
increase latency. Must be an integer not lesser than 32. It is
500 by default.


When I try -lavfdopts probesize=32, there is no crash, and it plays fine.

I wrote a little script.  Random values below -lavfdopts probesize=282574
are fine.  282575 and above crashed.  I tried this same with the other
video file, exhibiting the same issue, and the 'crash point' was
different.  EG, 291281 and below was fine, 291282 and above crashed.

Well.. it's info anyhow.

Bug#878194: python-statistics: new upstream version “3.4.0b3”

[Ben Finney]

Source: python-statistics
Severity: wishlist

The upstream project has recently released the ‘statistics’
distribution version “3.4.0b3” to PyPI
.

Please package this more current release in Debian.

-- 
 \“When I was a baby I kept a diary. Recently I was re-reading |
  `\   it, it said ‘Day 1: Still tired from the move. Day 2: Everybody |
_o__)  talks to me like I'm an idiot.’” —Steven Wright |
Ben Finney 


signature.asc
Description: PGP signature

Bug#878193: fails to start with minimal dependencies from testing

[Kilian Krause]

Package: puppetdb
Version: 4.4.1-1
Severity: normal

Hi,

While trying to start puppetdb with as much a testing install as
possible, I get:
--(snip)--
Oct 10 23:14:49 puppet-db systemd[1]: Started Puppet data warehouse server.
Oct 10 23:14:57 puppet-db java[32440]: Exception in thread "main" 
java.lang.RuntimeException: No such var: cli/parse-opts, 
compiling:(puppetlabs/kitchensink/core.clj:867:52)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6688)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6625)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:3766)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyzeSeq(Compiler.java:6870)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6669)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.access$300(Compiler.java:38)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6269)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyzeSeq(Compiler.java:6868)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6669)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyzeSeq(Compiler.java:6856)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6669)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6625)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6005)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler$FnMethod.parse(Compiler.java:5380)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler$FnExpr.parse(Compiler.java:3972)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyzeSeq(Compiler.java:6866)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6669)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyzeSeq(Compiler.java:6856)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6669)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.access$300(Compiler.java:38)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler$DefExpr$Parser.parse(Compiler.java:590)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyzeSeq(Compiler.java:6868)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6669)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.analyze(Compiler.java:6625)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.eval(Compiler.java:6931)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.Compiler.load(Compiler.java:7379)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.RT.loadResourceScript(RT.java:372)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.RT.loadResourceScript(RT.java:363)
Oct 10 23:14:57 puppet-db java[32440]: #011at clojure.lang.RT.load(RT.java:453)
Oct 10 23:14:57 puppet-db java[32440]: #011at clojure.lang.RT.load(RT.java:419)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load$fn__1621.invoke(core.clj:5893)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load.invokeStatic(core.clj:5892)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load.doInvoke(core.clj:5876)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.RestFn.invoke(RestFn.java:408)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_one.invokeStatic(core.clj:5697)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_one.invoke(core.clj:5692)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_lib$fn__1570.invoke(core.clj:5737)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_lib.invokeStatic(core.clj:5736)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_lib.doInvoke(core.clj:5717)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.RestFn.applyTo(RestFn.java:142)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$apply.invokeStatic(core.clj:648)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$apply.invoke(core.clj:641)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_libs.invokeStatic(core.clj:5775)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$load_libs.doInvoke(core.clj:5758)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.lang.RestFn.applyTo(RestFn.java:137)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$apply.invokeStatic(core.clj:648)
Oct 10 23:14:57 puppet-db java[32440]: #011at 
clojure.core$apply.invoke(core.clj:641)
Oct 10 23:14:57 puppet-db java[32440]: #011at 

Bug#636871: provide a command-line switch to prefer IPv6 or IPv4

[Ludens]

On Sat, 7 Oct 2017 23:28:57 +0200 Julian Andres Klode 
wrote:
> JFTR: I wrote an implementation of parts of happy eyeballs for another
> bug we should probably merge in here, but it fails the test suite on
> CI: https://github.com/julian-klode/apt/commits/bugfix/happy-eyeballs
>
> I started a rewrite of that in another local branch, but it's not
> done yet.

Hi,

I started some work on this without knowing about the code that was
there. The patch attached implements Happy Eyeballs in (roughly) the
following way:

In ConnectToHostname, if the first DoConnect does not complete within
300ms, another DoConnect is performed with an address of a different IP
family. So, if the first DoConnect used IPv6, the second will use IPv4
and vice versa. Of these two connection attempts, the first one that
completes will be used. The precedence ordering of getaddrinfo is also
taken into account. Hopefully, this is helpful.

The patch is based on the 1.4.y branch, and should be applicable to
commit ac0d26d4e3. If there is something that I could change, please let
me know.

Kind regards,
Ludens
diff --git a/apt-pkg/contrib/fileutl.cc b/apt-pkg/contrib/fileutl.cc
index e4c40fb4f..8b3ac8015 100644
--- a/apt-pkg/contrib/fileutl.cc
+++ b/apt-pkg/contrib/fileutl.cc
@@ -741,22 +741,28 @@ void SetNonBlock(int Fd,bool Block)
 // WaitFd - Wait for a FD to become readable/*{{{*/
 // -
 /* This waits for a FD to become readable using select. It is useful for
-   applications making use of non-blocking sockets. The timeout is 
-   in seconds. */
-bool WaitFd(int Fd,bool write,unsigned long timeout)
+   applications making use of non-blocking sockets. */
+bool WaitFd(int Fd,bool write,unsigned long timeout_sec,
+	unsigned long timeout_usec)
 {
fd_set Set;
struct timeval tv;
FD_ZERO();
FD_SET(Fd,);
-   tv.tv_sec = timeout;
-   tv.tv_usec = 0;
+
+   tv.tv_sec = timeout_sec;
+   tv.tv_usec = timeout_usec;
+
+   struct timeval * tv_arg = 0;
+   if (timeout_sec != 0 || timeout_usec != 0)
+  tv_arg = 
+
if (write == true) 
{  
   int Res;
   do
   {
-	 Res = select(Fd+1,0,,0,(timeout != 0?:0));
+	 Res = select(Fd+1,0,,0,tv_arg);
   }
   while (Res < 0 && errno == EINTR);
   
@@ -768,7 +774,7 @@ bool WaitFd(int Fd,bool write,unsigned long timeout)
   int Res;
   do
   {
-	 Res = select(Fd+1,,0,0,(timeout != 0?:0));
+	 Res = select(Fd+1,,0,0,tv_arg);
   }
   while (Res < 0 && errno == EINTR);
   
diff --git a/apt-pkg/contrib/fileutl.h b/apt-pkg/contrib/fileutl.h
index dddeb70f5..474b283f8 100644
--- a/apt-pkg/contrib/fileutl.h
+++ b/apt-pkg/contrib/fileutl.h
@@ -191,7 +191,8 @@ std::vector GetListOfFilesInDir(std::string const , bool SortLi
 std::string SafeGetCWD();
 void SetCloseExec(int Fd,bool Close);
 void SetNonBlock(int Fd,bool Block);
-bool WaitFd(int Fd,bool write = false,unsigned long timeout = 0);
+bool WaitFd(int Fd,bool write = false,unsigned long timeout_sec = 0,
+	unsigned long timeout_usec = 0);
 pid_t ExecFork();
 pid_t ExecFork(std::set keep_fds);
 void MergeKeepFdsFromConfiguration(std::set _fds);
diff --git a/methods/connect.cc b/methods/connect.cc
index dc2aee05c..be4ea3c86 100644
--- a/methods/connect.cc
+++ b/methods/connect.cc
@@ -25,8 +25,8 @@
 #include 
 #include 
 #include 
-#include
-#include
+#include 
+#include 
 
 // Internet stuff
 #include 
@@ -49,6 +49,14 @@ static std::vector SrvRecords;
 // Set of IP/hostnames that we timed out before or couldn't resolve
 static std::set bad_addr;
 
+// Time-out for attempting Happy Eyeballs rotation
+// See https://tools.ietf.org/rfc/rfc6555.txt
+static struct timeval const TimeOutHE =
+{ // 300 ms
+   0,
+   300 * 1000
+};
+
 // RotateDNS - Select a new server from a DNS rotation			/*{{{*/
 // -
 /* This is called during certain errors in order to recover by selecting a 
@@ -79,9 +87,34 @@ static bool ConnectionAllowed(char const * const Service, std::string const 
 // DoConnect - Attempt a connect operation/*{{{*/
 // -
 /* This helper function attempts a connection to a single address. */
+
+// The previous value of DoConnect's HappyEyeballsAttempt parameter.
+// We expect to see either:
+// 0 (no attempt) followed by 0 or 1
+// 1 (first connect during Happy Eyeballs) followed by 2
+// 2 (second connect during Happy Eyeballs) followed by 0 or 1
+// Anything else is wrong.
+static unsigned char prevAttemptHE = 0;
+
 static bool DoConnect(struct addrinfo *Addr,std::string const ,
-		  unsigned long TimeOut,int ,pkgAcqMethod *Owner)
+		  unsigned long TimeOutSec,unsigned long TimeOutUsec,
+		  int ,pkgAcqMethod *Owner,
+		  unsigned char HappyEyeballsAttempt = 0)
 {
+   if (HappyEyeballsAttempt > 2
+   ||
+   (prevAttemptHE == 0 && 

Bug#838866: mark gnome-mime-data Multi-Arch: foreign

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi,

2016-10-15 13:39 Helmut Grohne:

Package: gnome-mime-data
Version: 2.18.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gnome-vfs

gnome-vfs cannot be cross built from source, because its build
dependency on gnome-mime-data is unsatisfiable. In general, dependencies
on Architecture: all packages are cross unsatisfiable unless they are
marked Multi-Arch: foreign.

In this case, the marking looks correct, because gnome-mime-data is
Architecture: all and doesn't have any maintainer scripts or
dependencies. Please consider applying the attached patch.


This package is a build-dependency of gnome-vfs, which in turn is a
build-dependency of many others, so I think that it's important that
this fix is applied.

I uploaded an NMU to delayed/10 directly, since the package hasn't seen
an upload in 10+ years; but please let me know if you prefer me to
cancel it.

.debdiff attached.


Cheers.
--
Manuel A. Fernandez Montecelo 

diff -u gnome-mime-data-2.18.0/debian/changelog 
gnome-mime-data-2.18.0/debian/changelog
--- gnome-mime-data-2.18.0/debian/changelog
+++ gnome-mime-data-2.18.0/debian/changelog
@@ -1,3 +1,14 @@
+gnome-mime-data (2.18.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Modifying d/control.in rather than d/control for the fix of Helmut to
+take effect
+
+  [ Helmut Grohne ]
+  * Mark Multi-Arch: foreign. (Closes: #840830)
+
+ -- Manuel A. Fernandez Montecelo   Tue, 10 Oct 2017 23:27:05 
+0200
+
 gnome-mime-data (2.18.0-1) unstable; urgency=low
 
   * Add a get-orig-source target to retrieve the upstream tarball.
diff -u gnome-mime-data-2.18.0/debian/control 
gnome-mime-data-2.18.0/debian/control
--- gnome-mime-data-2.18.0/debian/control
+++ gnome-mime-data-2.18.0/debian/control
@@ -13,6 +13,7 @@
 
 Package: gnome-mime-data
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: base MIME and Application database for GNOME.
  This module contains the base MIME and Application database for GNOME.
diff -u gnome-mime-data-2.18.0/debian/control.in 
gnome-mime-data-2.18.0/debian/control.in
--- gnome-mime-data-2.18.0/debian/control.in
+++ gnome-mime-data-2.18.0/debian/control.in
@@ -9,6 +9,7 @@
 
 Package: gnome-mime-data
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: base MIME and Application database for GNOME.
  This module contains the base MIME and Application database for GNOME.

Bug#876667: RFS: pragha/1.3.3-1

[Gabriel F. T. Gomes]

On Fri, 06 Oct 2017, Breno Leitao wrote:

>I am just doing a final review for the sponsor, and I found something
>that annoys every developer, it seems that pragha does not re-builds
>after an initial build.
>
>It builds fine for the very first time, but if you try to re-build, the
>directory stays dirty and does not allow the package to be rebuilt:
>
>This is what I tried:
>
>$ get -x
>https://mentors.debian.net/debian/pool/main/p/pragha/pragha_1.3.3-1.dsc
>
>$ cd pragha-1.3.3 
>
>$ debuild ; debuild
>
>You are going to see something like:
>
>   dpkg-source: error: cannot represent change to po/bg.gmo: binary file 
> contents changed
>   dpkg-source: error: add po/bg.gmo in debian/source/include-binaries if 
> you want to store the modified binary in the debian tarball
>
>This means that your clean rules is not cleaning everything that was
>generated during the build process.

Thanks for taking the time to write these steps.  I can easily reproduce
this on my machine.

I'll prepare a new version with that fixed.

Bug#878185: nixnote2: Doesn't start

[Torquil Macdonald Sørensen]

Package: nixnote2
Version: 2.0.2-1
Followup-For: Bug #878185

This can be solved by installing libqt5sql5-sqlite, so if that is added as a 
dependency, this
bug can be marked as resolved.

Best regards
Torquil Sørensen

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

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

Versions of packages nixnote2 depends on:
ii  default-jre [java8-runtime]2:1.8-59
ii  libc6  2.24-17
ii  libcurl3   7.55.1-1
ii  libgcc11:7.2.0-8
ii  libpoppler-qt5-1   0.57.0-2
ii  libqt5core5a   5.9.1+dfsg-11
ii  libqt5gui5 5.9.1+dfsg-11
ii  libqt5network5 5.9.1+dfsg-11
ii  libqt5printsupport55.9.1+dfsg-11
ii  libqt5qevercloud3  3.0.3+ds-3
ii  libqt5qml5 5.9.1-6
ii  libqt5sql5 5.9.1+dfsg-11
ii  libqt5webkit5  5.9.1+dfsg-5
ii  libqt5widgets5 5.9.1+dfsg-11
ii  libqt5xml5 5.9.1+dfsg-11
ii  libstdc++6 7.2.0-8
ii  openjdk-8-jre [java8-runtime]  8u144-b01-2
ii  tidy   1:5.2.0-2

Versions of packages nixnote2 recommends:
ii  mimetex  1.74-1+b3

Versions of packages nixnote2 suggests:
pn  cups  

-- no debconf information

Bug#878164: dunst systemd service and dbus service are both suboptimal

[Daniel Kahn Gillmor]

On Tue 2017-10-10 22:27:23 +0200, Michael Stapelberg wrote:
> Okay, so I think the issue is that we have an old
> debian/org.knopwob.dunst.service lying around, which overrides the
> upstream-provided org.knopwob.dunst.service. I’ll prepare a new upload
> in a second, but until then, you can add
> “SystemdService=dunst.service” to
> /usr/share/dbus-1/services/org.knopwob.dunst.service.

thanks for this fix, Michael!

out of curiosity, where is the documentation for the directives
available for files like
/usr/share/dbus-1/services/org.knopwob.dunst.service ?

I'm spoiled by the high quality of the systemd manpages, i think, but
SystemdService= doesn't show up in systemd.directives(7) so i don't know
where to read up on it in more detail.

  --dkg

Bug#878192: Vagrant/virtualbox: Optionally disable rsync synced_folder if vagrant-vbguest is installed

[Jon Spriggs]

Package: cloud.debian.org
Severity: wishlist
Tags: newcomer patch

Dear Maintainer,

I would like to propose that you add the following wrapper to the 
"config.vm.synced_folder" line in 
the Vagrantfile packaged in the debian/squeeze64 (and potentially the other 
distributed images?)

This would permit people who prefer the vboxfs file system, to use that, if 
they have the plugin
loaded, but also allows them to overide the option, if that's their preferred 
sync mechanism. With
the current Vagrantfile shipped with the box, it's not clearly defined how 
someone prevents the
rsync default from being applied.

   config.vm.base_mac = "decafbad1234"
-  config.vm.synced_folder ".", "/vagrant", type: "rsync"
+
+  unless Vagrant.has_plugin?("vagrant-vbguest")
+config.vm.synced_folder ".", "/vagrant", type: "rsync"
+  end
+
   config.vm.post_up_message = ".."

I have tested this today with my Vagrant setup, and it works, with both the 
Jessie and Stretch boxes.

Regards,

-- 
Jon "The Nice Guy" Spriggs

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

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

Bug#878191: Error in `/usr/bin/mplayer': corrupted double-linked list: 0x0000560ab80de850

[Brad Barnett]

Package: mplayer
Version: 2:1.3.0-6



I've recently been playing more 4k / 2160p video files, 8 bit encoded.

All have been fine with the exception of two of them.


$ uname -a
Linux xsdfsdf 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux

$ /usr/bin/mplayer -fs 
filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos/filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos.mkv
 
MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick

Playing 
filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos/filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos.mkv.
Cache fill:  0.00% (0 bytes)

libavformat version 57.71.100 (external)
Mismatching header version 57.56.100
libavformat file format detected.
[matroska,webm @ 0x7ff05ff98560]Stream #20: not enough frames to estimate rate; 
consider increasing probesize
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 5 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 6 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 7 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 8 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 9 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 10 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 11 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 12 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 13 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 14 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 15 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 16 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 17 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 18 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[matroska,webm @ 0x7ff05ff98560]Could not find codec parameters for stream 19 
(Subtitle: hdmv_pgs_subtitle): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[lavf] stream 0: video (h264), -vid 0, 
filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos
[lavf] stream 1: audio (truehd), -aid 0, -alang eng, 
filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos
[lavf] stream 2: audio (dca), -aid 1, -alang eng, 
filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos
[lavf] stream 3: audio (ac3), -aid 2, -alang eng, 
filename.2160p.BluRay.x264.8bit.SDR.DTS-HD.MA.TrueHD.7.1.Atmos
[lavf] stream 4: subtitle (srt), -sid 0, -slang eng, English-SRT
[lavf] stream 5: subtitle (pgssub), -sid 1, -slang eng, English-PGS
[lavf] stream 6: subtitle (pgssub), -sid 2, -slang spa, Spanish-PGS
[lavf] stream 7: subtitle (pgssub), -sid 3, -slang fre, French-PGS
[lavf] stream 8: subtitle (pgssub), -sid 4, -slang fre, French-PGS
[lavf] stream 9: subtitle (pgssub), -sid 5, -slang spa, Spanish-PGS
[lavf] stream 10: subtitle (pgssub), -sid 6, -slang dan, Danish-PGS

Bug#878190: wiki.debian.org: "apt-get autoremove" also changes the grub.cfg - it should not

[nbi]

Package: wiki.debian.org
Severity: normal
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
apt-get autoremove
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Had to restore the grub.cfg from an archived version.
   * What was the outcome of this action?
It regenerated the grub.cfg, thus destroying specific customizations that could
render some partitions unbootable.
   * What outcome did you expect instead?
"apt-get autoremove" should NOT regenerate the grub.cfg file. It shouldn't
touch it at all! That action has nothing to do with the intent & purpose of
"autoremove".

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



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

Kernel: Linux 4.9.2 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US.utf8 (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#878169: apt-cacher-cleanup.pl removes all packages not only old ones

[Mark Hindley]

package apt-cacher
tag -1 moreinfo
thanks

On Tue, Oct 10, 2017 at 07:49:10PM +0200, Christian Bachmaier wrote:
> Package: apt-cacher
> Version: 1.7.15
> Severity: important
> 
> Dear Maintainer,
> 
> executing /usr/share/apt-cacher/apt-cacher-cleanup.pl manually (or
> automatically by /etc/crond/apt-cacher) removes all deb-packages from
> /var/cache/apt-cacher, even if there is no newer versions in the debian
> repositories.

Thanks for this. You will have to give me more detail.

 - What repositories were clients accessing thorugh apt-cacher?
 - What packages and versions were present and then removed by
   apt-cacher-cleanup.pl?
 
> According to the documentation and to the used behavior some timne ago, the
> newest packages should be left untouched.

As far as I know the current behaviour is as it always has been -- once a
package is no longer mentioned in any index file it is removed. The newest
package is not kept unless it is still current in at least one release.

Mark

Bug#838866: vorbis-tools FTCBFS: does not honour DEB_BUILD_OPTIONS=nocheck

[Manuel A. Fernandez Montecelo]

Hi,

2016-09-25 23:16 Helmut Grohne:

Source: vorbis-tools
Version: 1.4.0-10
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

vorbis-tools fails to cross build from source, because it runs tests
even when invoked with DEB_BUILD_OPTIONS=nocheck. Tests naturally fail,
because host architecture executables cannot be executed at all in a
cross build setting. The attached patch implements the necessary
handling of DEB_BUILD_OPTIONS=nocheck. Please consider applying it.

After applying it, vorbis-tools does not become cross buildable. It also
fails to find ao.pc using pkg-config, because ao.pc does not live in a
multiarch path. So #638741 needs to be fixed as well for actually cross
building vorbis-tools.


This patch looks sensible and worth on its own right, and I would like
to get it applied.

Does it help if I prepare a NMU for this?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#745771: util-linux: Enable audit support

[Joy Latten]

Hello,

I wanted to inquire into the status of this bug and patch filed a while
back. There is a similar one opened here,
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313.

To address just a few of the issues discussed in the thread for this bug...

- Only hwclock would be affected by this change.
I have enabled --with-audit in Ubuntu Xenial's util-linux package and
tested the hwclock on amd64 and ppc64el systems. I issued, "sudo hwclock
--set --date 11:36" And saw the following entry in my
/var/log/audit/audit.log file,

type=USYS_CONFIG msg=audit(1507653892.513:8900): pid=9909 uid=0
auid=1000 ses=433 msg='changing system time exe="/sbin/hwclock"
hostname=? addr=? terminal=pts/0 res=success'

The audit record was generated and all appears ok.

- util-linux package is Priority: required and the libaudit1 package is
Priority: optional.

Possibly this is no longer a problem in reference to a change in Version
4.0.1 listed here,
https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt ?

I hope to hear from you. Thanks!

regards,
Joy

Bug#878189: please drop transitional package git-core

[Holger Levsen]

On Tue, Oct 10, 2017 at 01:42:25PM -0700, Jonathan Nieder wrote:
> Good call.  Done for the next upload.

thanks! :)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878177: [Aptitude-devel] Bug#878177: aptitude: Use of the word "invalid" in error msgs should be restored to meaning

[Axel Beckert]

Control: reassign -1 apt
Control: affects -1 + aptitude

Hi,

Anonymous wrote:
> Aptitude's error messages often create confusion, either due to
> vagueness or improper use of English.  In particular, use of the word
> /invalid/ in the following warning message needs to be re-examined:
> 
> W: GPG error: tor+http://wertarbyte.de/apt ./ Release: The following 
> signatures were invalid: CC49F74C816C499C899A42885145B9CD752C0197
> E: The repository 'tor+http://wertarbyte.de/apt ./ Release' is not signed.
> E: Failed to download some files

Despite this error message is emitted by the program aptitude, it
comes from apt's libraries' usage of GPG, so reassigning to apt, too.

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

Bug#878189: please drop transitional package git-core

[Jonathan Nieder]

tags 878189 + pending
quit

Hi,

Holger Levsen wrote:

> Please drop obsolete transitional package git-core for Buster, as it
> has been released with Wheezy already.

Good call.  Done for the next upload.

Thanks,
Jonathan

Bug#878184: invalid link to upgrading-checklist

[Chris Lamb]

tags 878184 + pending
thanks

Fixed in Git, many thanks :)

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


Regards,

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

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

[Ian Campbell]

On Tue, 2017-10-10 at 13:13 -0700, Francois Marier wrote:
> On 2017-10-10 at 19:38:18, Ian Campbell wrote:
> > On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote:
> > >   E: libhdhomerun4: ldconfig-symlink-missing-for-shlib 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 libhdhomerun.so.4
> > >   W: libhdhomerun4: dev-pkg-without-shlib-symlink 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so
> > 
> > Sorry, I don't know how I missed that. Looking now I only actually see
> > the second one (the warning). It's fixed by the additional patch below
> > (note the mode change as well as the content change).
> > 
> > Not sure about the error though since I don't see it, but perhaps the
> > same patch helps there?
> 
> The warning is indeed fixed by your second patch but the error is still
> there.

Sorry, looks like I accidentally missed out a hunk in the orignal patch
I sent, see below. Like last time note the mode as well as the content
change.

Sorry again for the confusion.

Ian.

diff --git a/debian/libhdhomerun4.links b/debian/libhdhomerun4.links
old mode 100644
new mode 100755
index 074bcaa..43ca729
--- a/debian/libhdhomerun4.links
+++ b/debian/libhdhomerun4.links
@@ -1 +1,2 @@
-/usr/lib/libhdhomerun.so.4.0.0 /usr/lib/libhdhomerun.so.4
+#! /usr/bin/dh-exec
+/usr/lib/${DEB_HOST_MULTIARCH}/libhdhomerun.so.4.0.0 
/usr/lib/${DEB_HOST_MULTIARCH}/libhdhomerun.so.4

Bug#839108: [pkg-go] Bug#839108: dh-golang: Please document behavior and variables used

[Michael Stapelberg]

Thanks for the hint, I wasn’t aware of that! I’ll document the
variables and upload a new version.

On Sat, Sep 23, 2017 at 12:08 PM, Shengjing Zhu  wrote:
> On Tue, 20 Jun 2017 09:49:26 +0200 Michael Stapelberg
>  wrote:
>> Hi Guillem,
>>
>> Thanks for your report!
>>
>> Guillem Jover  writes:
>> > Please document at least the variables from the environment that
>> > directly affect the behavior such as GOPATH, DH_GOPKG,
>> > DH_GOLANG_INSTALL_ALL, DH_GOLANG_INSTALL_EXTRA, DH_GOLANG_BUILDPKG,
>> > DH_GOLANG_GO_GENERATE. And the field control field Go-Import-Path.
>>
>> What’s the correct place to document them? Stuffing this buildsystem
>> related documentation into the dh_golang(1) manpage seems inappropriate,
>> as that manpage should only document the dh_golang executable, right?
>
> Add to man 3 Debian::Debhelper::Buildsystem::golang?
>
> If you add the docs to lib/Debian/Debhelper/Buildsystem/golang.pm, the
> auto generated manpage is
> man3/Debian::Debhelper::Buildsystem::golang.3pm.gz
>
> --
> Best regards,
> Shengjing Zhu
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



-- 
Best regards,
Michael

Bug#878186: fbpanel: Re:

[Juri Grabowski]

Package: fbpanel
Version: 7.0-3
Followup-For: Bug #878186

Dear Maintainer,

here is my patch for this issue.

Best Regards,
Juri Grabowski
Description: no libexecdir in debian
 On gentoo it is placed in /usr/libexec, on Debian in /usr/lib
 .
 fbpanel (7.0-3) unstable; urgency=high
 .
   * execve from make_profile is now possible
Author: Juri Grabowski 
Bug-Debian: https://bugs.debian.org/878186
Last-Update: 2017-10-09

--- fbpanel-7.0.orig/.config/options.py
+++ fbpanel-7.0/.config/options.py
@@ -17,7 +17,7 @@ def init():
 default = lambda : opt('eprefix') + '/sbin')
 opt_new("libexecdir", group = 'autoconf',
 help = "program executables", metavar='DIR',
-default = lambda : opt('eprefix') + '/libexec/' + opt('project_name'))
+default = lambda : opt('eprefix') + '/lib/' + opt('project_name'))
 opt_new("libdir", group = 'autoconf',
 help = "object code libraries", metavar='DIR',
 default = lambda : opt('eprefix') + '/lib/' + opt('project_name'))
--- fbpanel-7.0.orig/panel/panel.c
+++ fbpanel-7.0/panel/panel.c
@@ -923,7 +923,7 @@ ensure_profile()
 {
 return;
 }
-cmd = g_strdup_printf("%s %s", LIBEXECDIR "/fbpanel/make_profile",
+cmd = g_strdup_printf("%s %s", LIBDIR "/fbpanel/make_profile",
 profile);
 g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
 g_free(cmd);

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

[Ian Campbell]

On Tue, 2017-10-10 at 13:13 -0700, Francois Marier wrote:
> On 2017-10-10 at 19:38:18, Ian Campbell wrote:
> > On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote:
> > >   E: libhdhomerun4: ldconfig-symlink-missing-for-shlib 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 libhdhomerun.so.4
> > >   W: libhdhomerun4: dev-pkg-without-shlib-symlink 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 
> > > usr/lib/x86_64-linux-gnu/libhdhomerun.so
> > 
> > Sorry, I don't know how I missed that. Looking now I only actually see
> > the second one (the warning). It's fixed by the additional patch below
> > (note the mode change as well as the content change).
> > 
> > Not sure about the error though since I don't see it, but perhaps the
> > same patch helps there?
> 
> The warning is indeed fixed by your second patch but the error is still
> there.

Weird. What is the contents of the package you build? Mine is:
drwxr-xr-x root/root 0 2017-10-10 19:34 ./
drwxr-xr-x root/root 0 2017-10-10 19:34 ./usr/
drwxr-xr-x root/root 0 2017-10-10 19:34 ./usr/lib/
drwxr-xr-x root/root 0 2017-10-10 19:34 ./usr/lib/x86_64-linux-gnu/
-rw-r--r-- root/root 79784 2017-10-10 19:34 
./usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0
drwxr-xr-x root/root 0 2017-10-10 19:34 ./usr/share/
drwxr-xr-x root/root 0 2017-10-10 19:34 ./usr/share/doc/
drwxr-xr-x root/root 0 2017-10-10 19:34 
./usr/share/doc/libhdhomerun4/
-rw-r--r-- root/root   503 2017-06-12 20:31 
./usr/share/doc/libhdhomerun4/README.md
-rw-r--r-- root/root  1697 2017-10-10 19:34 
./usr/share/doc/libhdhomerun4/changelog.Debian.gz
-rw-r--r-- root/root 11229 2017-10-10 19:34 
./usr/share/doc/libhdhomerun4/changelog.gz
-rw-r--r-- root/root  1267 2017-10-08 17:56 
./usr/share/doc/libhdhomerun4/copyright
lrwxrwxrwx root/root 0 2017-10-10 19:34 
./usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 -> libhdhomerun.so.4.0.0

If I understand the warning correctly it is complaining that you are
missing that symlink at the end.

Ian.

Bug#878164: dunst systemd service and dbus service are both suboptimal

[Michael Stapelberg]

Okay, so I think the issue is that we have an old
debian/org.knopwob.dunst.service lying around, which overrides the
upstream-provided org.knopwob.dunst.service. I’ll prepare a new upload
in a second, but until then, you can add
“SystemdService=dunst.service” to
/usr/share/dbus-1/services/org.knopwob.dunst.service.

Aside from that, you need to install the dbus-user-session Debian
package. Things are set up correctly once “org.freedesktop.systemd1”
appears in the output of “qdbus”.

After fixing both of the above on my machine, dunst is dbus-activated
and started as systemd user unit dunst.service. Verify using systemctl
--user status dunst.service.

On Tue, Oct 10, 2017 at 8:12 PM, Daniel Kahn Gillmor
 wrote:
> On Tue 2017-10-10 19:16:28 +0200, Michael Stapelberg wrote:
>> Please refer to https://github.com/systemd/systemd/issues/892. I have
>> only skimmed that, so if you could figure out what we need to change
>> upstream in dunst or downstream in the packaging to make this work,
>> that’d be appreciated. Thanks!
>
> thanks for the quick response, Michael!
>
> hm, i can't see how that's exactly related to this problem, though i'm
> pretty sure i don't understand all the moving parts.
>
> also, that issue appears to have been closed upstream a few months ago.
> does it need re-opening?
>
> sorry to not have any good suggestions here.
>
>  --dkg



-- 
Best regards,
Michael

Bug#878189: please drop transitional package git-core

[Holger Levsen]

Package: git-core
Version: 1:2.1.4-2.1+deb8u5
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop obsolete transitional package git-core for Buster, as it has been 
released with Wheezy already.

Thanks for maintaining git!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878188: unattended-upgrades: [INTL:de] Updated German translation

[Chris Leick]

Package: unattended-upgrades
Version: 0.98

Severity: wishlist
Tags: l10n patch



Hi,

please find attached the newest German translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#878187: nmu: simbody_3.5.4+dfsg-1

[Jochen Sprickerhof]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu simbody_3.5.4+dfsg-1 . ANY . unstable . -m "recompile against multiarch 
lapack"

Hi,

lapack moved it's libraries to /usr/include/ in 3.7.1-2. As
libsimbody-dev includes the full path in SimbodyConfig.cmake, please do
an nmu to fix it. This currently brakes compilation of gazebo.

Cheers

Jochen

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

Kernel: Linux 4.13.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Bug#878185: nixnote2: Doesn't start

[Torquil Macdonald Sørensen]

Package: nixnote2
Version: 2.0.2-1
Severity: grave
Justification: renders package unusable

When trying to start nixnote2, I get:

$ nixnote2
DEBUG 2017-10-10 21:38:29.616 ( gui/shortcutkeys.cpp @ 246 ) Unable to open 
file for reading or file does not exist. 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 55 ) "Script filename 
is blank. Disabling exit " "ExitPoint_LoadNote" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 67 ) "Script file 
doesn't exist or cannot be read. Disabling exit " "ExitPoint_LoadNote" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 55 ) "Script filename 
is blank. Disabling exit " "ExitPoint_SaveNote" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 67 ) "Script file 
doesn't exist or cannot be read. Disabling exit " "ExitPoint_SaveNote" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 55 ) "Script filename 
is blank. Disabling exit " "ExitPoint_ImportKeep" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 67 ) "Script file 
doesn't exist or cannot be read. Disabling exit " "ExitPoint_ImportKeep" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 55 ) "Script filename 
is blank. Disabling exit " "ExitPoint_ImportDelete" 
ERROR 2017-10-10 21:38:29.616 ( exits/exitmanager.cpp @ 67 ) "Script file 
doesn't exist or cannot be read. Disabling exit " "ExitPoint_ImportDelete" 
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
ERROR 2017-10-10 21:38:29.622 ( sql/databaseconnection.cpp @ 44 ) Error opening 
database:  QSqlError("", "Driver not loaded", "Driver not loaded")

Best regards,
Torquil Sørensen

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

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

Versions of packages nixnote2 depends on:
ii  default-jre [java8-runtime]2:1.8-59
ii  libc6  2.24-17
ii  libcurl3   7.55.1-1
ii  libgcc11:7.2.0-8
ii  libpoppler-qt5-1   0.57.0-2
ii  libqt5core5a   5.9.1+dfsg-11
ii  libqt5gui5 5.9.1+dfsg-11
ii  libqt5network5 5.9.1+dfsg-11
ii  libqt5printsupport55.9.1+dfsg-11
ii  libqt5qevercloud3  3.0.3+ds-3
ii  libqt5qml5 5.9.1-6
ii  libqt5sql5 5.9.1+dfsg-11
ii  libqt5webkit5  5.9.1+dfsg-5
ii  libqt5widgets5 5.9.1+dfsg-11
ii  libqt5xml5 5.9.1+dfsg-11
ii  libstdc++6 7.2.0-8
ii  openjdk-8-jre [java8-runtime]  8u144-b01-2
ii  tidy   1:5.2.0-2

Versions of packages nixnote2 recommends:
ii  mimetex  1.74-1+b3

Versions of packages nixnote2 suggests:
pn  cups  

-- no debconf information

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

[Francois Marier]

On 2017-10-10 at 19:38:18, Ian Campbell wrote:
> On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote:
> >   E: libhdhomerun4: ldconfig-symlink-missing-for-shlib 
> > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 
> > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 libhdhomerun.so.4
> >   W: libhdhomerun4: dev-pkg-without-shlib-symlink 
> > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 
> > usr/lib/x86_64-linux-gnu/libhdhomerun.so
> 
> Sorry, I don't know how I missed that. Looking now I only actually see
> the second one (the warning). It's fixed by the additional patch below
> (note the mode change as well as the content change).
> 
> Not sure about the error though since I don't see it, but perhaps the
> same patch helps there?

The warning is indeed fixed by your second patch but the error is still
there.

Francois

Bug#878186: fbpanel -p $YOURPROFILE do not create profile in $HOME from /usr/share/fbpanel/$YOURPROFILE as template

[Juri Grabowski]

Package: fbpanel
Version: 7.0-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?
 Created new User with emty Homedir after upgrade from Jessie and
 started fbpanel with -p myprofile
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 fbpanel -p myprofile
 If I start it with strace:
 strace -e execve -f -s 2000 fbpanel -p myprofile
 execve("/usr/bin/fbpanel", ["fbpanel", "-p", "myprofile"], [/* 13
 vars */]) = 0
 strace: Process 4988 attached
 [pid  4988] execve("/usr/lib/fbpanel/fbpanel/fbpanel/make_profile",
 ["/usr/lib/fbpanel/fbpanel/fbpanel/make_profile", "myprofile"], [/*
 13 vars */]) = -1 ENOENT (No such file or directory)
 [pid  4988] +++ exited with 1 +++
 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=4988,
 si_uid=1000, si_status=1, si_utime=0, si_stime=0} ---
 Can't open profile myprofile - /home/pdi/.config/fbpanel/myprofile
 +++ exited with 1 +++
 So, we can see, that fbpanel looking for make_profile in wrong
 path. /usr/lib/fbpanel/fbpanel/make_profile instead of
 /usr/lib/fbpanel/fbpanel/make_profile .
   * What was the outcome of this action?
 Can't open profile myprofile - /home/pdi/.config/fbpanel/myprofile
 and fbpanel was not started
   * What outcome did you expect instead?
 Started fbpanel with /usr/share/fbpanel/myprofile as template

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/40 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 /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages fbpanel depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  librsvg2-common  2.40.16-1+b1
ii  libx11-6 2:1.6.4-3

fbpanel recommends no packages.

Versions of packages fbpanel suggests:
ii  hicolor-icon-theme  0.15-1
ii  menu2.1.47+b1

-- no debconf information

Bug#878183: systemd-journal-remote: Should stop creating systemd-journal-gateway user

[Felipe Sateler]

Package: systemd-journal-remote
Version: 235-1
Severity: normal

Since systemd 235, systemd-journal-gateway has DynamicUsers=yes. This
means there is no longer need to allocate a static UID for it.

I have not checked if it is safe to remove the user on upgrades.

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

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

Versions of packages systemd-journal-remote depends on:
ii  adduser  3.116
ii  libc62.24-17
ii  libcurl3-gnutls  7.55.1-1
ii  libgnutls30  3.5.15-2
ii  libmicrohttpd12  0.9.55-1
ii  systemd  234-3

systemd-journal-remote recommends no packages.

systemd-journal-remote suggests no packages.

Bug#878184: invalid link to upgrading-checklist

[dann frazier]

Package: lintian
Version: 2.5.54
Severity: normal

The "out-of-date-standards-version" verbose output (-i) contains a link to the
debian policy upgrading checklist, but it 404s:
  https://www.debian.org/doc/debian-policy/upgrading-checklist

Perhaps this should instead point to:
  https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt ?

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

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

Versions of packages lintian depends on:
ii  binutils  2.29.1-4
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdigest-sha-perl5.98-1
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-8
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-8
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

Versions of packages lintian suggests:
ii  binutils-multiarch 2.29.1-4
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.47-1

-- no debconf information

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Herbert Fortes]

Em 10-10-2017 16:31, Andrey Rahmatullin escreveu:
> On Tue, Oct 10, 2017 at 04:06:59PM -0300, Herbert Fortes wrote:
>> It seems that the package is ready. Andrey Rahmatullin
>> did the review.
>>
>> The last activity was on 01 Oct 2017;  I can take one last
>> look in the package and upload it if the is no problem with
>> that.
> Yes please. The package seemed in good shape.
> 

Ok.



Regards,
Herbert

Bug#878171: [Vmdebootstrap-devel] Bug#878171: vmdebootstrap: misformatted man page

[Lars Wirzenius]

> Here's how vmdebootstrap's manpage is formatted:
> 
>   1:| VMDEBOOTSTRAP(8)   System Manager's Manual  
> VMDEBOOTSTRAP(8)
>   2:| 
>   3:| " "vmdebootstrap"
>   4:| 
>   5:| NAME
>   6:|vmdebootstrap - install basic Debian system into virtual disk 
> image
>   7:| 
>   8:| PURPOSE
> 
> It seems there's an extraneous line (#3).

The whole manual page is so far away from manual page conventions, it
should be rewritten from scratch, before minor mistakes are worth
considering. However, since I'd like the whole program to die, I'm
afraid I'm not interested in fixing this formatting mistake.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Heiner Markert]

On Tue, 10 Oct 2017 11:38:01 +0200 m-a-...@web.de wrote:
>
> Same problem here.
>
> "apt-get install --reinstall postfix" helped to fix this problem.
>
>

Same problem here.

The fix "apt-get install --reinstall postfix" only helps partially:
1) after executing the command, postfix starts
2) however, after another reboot, postfix again does not start up and I 
need to repeat the reinstall command


This means that after each reboot, postfix will not come up 
automatically -- please fix.

Bug#877146: Bug#877329: Bug#877146: update to runc (1.0.0~rc4) breaks docker

[Tianon Gravi]

On 3 October 2017 at 15:52, Bálint Réczey  wrote:
> I think it would be cleaner to go without the Provides: and adding
> docker-containerd build-depending on
> golang-github-opencontainers-docker-runc-dev, but feel free to go either way.
>
> I think the most efficient way forward would be if you could adopt the
> docker-runc
> package for the Docker Team and updating it as you please without
> waiting for me -
> and I'm perfectly OK with that.

I've been working on a "docker-containerd" package today (since that's
going to be useful regardless), and found that there are other
packages needed which depend on
"golang-github-opencontainers-runc-dev", so we're going to have to end
up with either splitting all the deps too, or going with Provides and
hoping for the best compatibility-wise (and perhaps splitting only
if/when there's an actual compatibility divergence for one of the
deps).

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#878182: systemd: Should stop creating systemd-bus-proxy user

[Felipe Sateler]

Package: systemd
Version: 234-3
Severity: normal

Systemd is still creating in postinst the systemd-bus-proxy user. That
user is no longer used upstream as all kdbus code was removed.

The user should no longer be created. It appears (but I haven't checked)
that it is safe to remove the user on upgrades, because the user never
created any files.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser 3.116
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.0-11
ii  libaudit1   1:2.7.8-1
ii  libblkid1   2.29.2-5+b1
ii  libc6   2.24-17
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.5-1
ii  libgcrypt20 1.7.9-1
ii  libgpg-error0   1.27-3
ii  libidn111.33-2
ii  libip4tc0   1.6.1-2
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.3
ii  libmount1   2.29.2-5+b1
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.7-2
ii  libsystemd0 234-3
ii  mount   2.29.2-5+b1
ii  procps  2:3.3.12-3
ii  util-linux  2.29.2-5+b1

Versions of packages systemd recommends:
ii  dbus1.11.20-1
ii  libpam-systemd  234-3

Versions of packages systemd suggests:
ii  policykit-10.105-18
ii  systemd-container  234-3

Versions of packages systemd is related to:
pn  dracut   
pn  initramfs-tools  
pn  udev 

-- no debconf information

Bug#878181: bluetooth: Bluetooth with different devices stopped working recently on buster/sid

[Torsten]

Package: bluetooth
Version: 5.47-1
Severity: important

Recently my bluetooth Microsoft Bluetooth Keyboard stopped working
sometimes. Also other devices wherer hard to pair.

I purged all blue* packages, deleted /var/lib/systemd/rfkill/* and
reinstalled all.

I paired different devices with blueman and bluetoothctl. It worked only
in about 10% of the cases. And most devices got problems after about 1-3
minutes.

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

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

Versions of packages bluetooth depends on:
ii  bluez  5.47-1

bluetooth recommends no packages.

Versions of packages bluetooth suggests:
pn  bluez-cups   
ii  bluez-obexd  5.47-1

-- no debconf information

Bug#878166: [Aptitude-devel] Bug#878166: aptitude: feature request: admins should determine their security stand team

[Axel Beckert]

Control: reassign -1 apt

Hi,

Nomen Nescio wrote:
> Package: aptitude
[..]
> Aptitude developers have taken the liberty of deciding for everyone
> subjectively what quality of cryptographic signature [...]

That's wrong. It's not the Aptitude developers but the Apt developers
you're talking about:

>   https://wiki.debian.org/Teams/Apt/Sha1Removal

That's "Apt", not "Aptitude" in that link.

Reassigning accordingly.

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

Bug#878167: RFS: cl-asdf/3.3.0 - Another System Definition Facility

[Sébastien Villemot]

Dear Kambiz,

On Tue, 10 Oct 2017 19:14:39 +0200 Kambiz Darabi  wrote:
> Package: sponsorship-requests
> Severity: normal

> I have packaged the new upstream release 3.3.0 of the Common Lisp ASDF
> software:
 
Thanks for your work.

Could you please push your changes to the git repository for cl-asdf on
alioth?

I will make an upload based on your work (probably making minor
additional changes).

Also, in the future, I suggest that you make requests for sponsorship
on the list of the Debian Common Lisp Team, which is the right place to
discuss about this package.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Andrey Rahmatullin]

On Tue, Oct 10, 2017 at 04:06:59PM -0300, Herbert Fortes wrote:
> It seems that the package is ready. Andrey Rahmatullin
> did the review.
> 
> The last activity was on 01 Oct 2017;  I can take one last
> look in the package and upload it if the is no problem with
> that.
Yes please. The package seemed in good shape.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#878180: Package udftools: Not working in stretch with DVDRAM

[Eckhard Neber]

Package: udftools

I'm using debian stretch on an i386 arch.

I installed and configured udftools but the directory /dev/pktcdvd/
was not created. I went through the startup-script in
/etc/init.d/udftools and encountered that this
PKTSETUP=/usr/bin/pktsetup
has moved to
PKTSETUP=/usr/sbin/pktsetup
after fixing it I could access the DVDRAM.

I hope this helps to improve the package.

With best regards
Eckhard Neber

PS: Please excuse me for not using reportbug, it did not work, see bug 877650.

Bug#878178: cdimage.debian.org: Debian 9.2.0 and 9.2.0-live images built with base-files 9.9+deb9u1

[Daniel Lewart]

Package: cdimage.debian.org
Severity: normal

Debian CD-ROM [sic] Team,

All Debian 9.2.0 and 9.2.0-live images appear to have been built with
base-files 9.9+deb9u1 instead of 9.9+deb9u2.

I'll guess that this was due to 9.9+deb9u2 being accepted
into proposed-updates on Oct 7, 2017.

Thank you!
Dan

Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package

[Fabian Greffrath]

Am Dienstag, den 10.10.2017, 21:18 +0200 schrieb Thorsten Glaser:
> They could switch to a different one, is what I meant.
> 
> (or embed it in the C source… *shudder*)

Whoa, I think both these cases would be incentive enough to package it
on its own.

> Exactly. Good that we’re on the same page.

Indeed!

> Uploaded, should enter NEW any time now.

Great, thank you!

 - Fabian


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

Bug#878176: reportbug: have a way to have a fake/mungled subject in order to have $editor start without needing to write subject

[Sandro Tosi]

use the --template switch?

reportbug --template 

On Tue, Oct 10, 2017 at 3:06 PM, shirish शिरीष  wrote:
> Package: reportbug
> Version: 7.1.7
> Severity: wishlist
>
> Dear Maintainer,
>
> Right now, I need to put up a subject each time I want to get the
> system state of the package including depends, recommends in a compact
> manner. It feels tedious to write the subject every time specifically
> when I need to share the system state with upstream of a package. I
> also did have a cursory look at bugs.debian.org/reportbug but couldn't
> find any which talk about this issue as well as didn't find this
> functionality in the manpage given.
>
>
> -- Package-specific info:
> ** Environment settings:
> PAGER="less"
> INTERFACE="text"
>
> ** /home/shirish/.reportbugrc:
> reportbug_version "7.1.4"
> mode standard
> ui text
> offline
> email "shir...@deb.org"
> no-cc
> header "X-Debbugs-CC: shir...@deb.org"
> smtphost shirish.deb.org
> editor "leafpad"
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (500, 'unstable-debug'), (500,
> 'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1,
> 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.12.0-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages reportbug depends on:
> ii  apt1.5
> ii  python33.5.3-3
> ii  python3-reportbug  7.1.7
>
> reportbug recommends no packages.
>
> Versions of packages reportbug suggests:
> pn  claws-mail 
> ii  debconf-utils  1.5.63
> ii  debsums2.2.2
> ii  dlocate1.07+nmu1
> ii  emacs25-bin-common 25.2+1-6
> ii  exim4  4.89-7
> ii  exim4-daemon-light [mail-transport-agent]  4.89-7
> ii  file   1:5.32-1
> ii  gir1.2-gtk-3.0 3.22.21-1
> ii  gir1.2-vte-2.910.50.0-1
> ii  gnupg  2.2.1-1
> ii  python3-gi 3.24.1-3
> ii  python3-gi-cairo   3.24.1-3
> ii  python3-gtkspellcheck  4.0.5-1
> ii  python3-urwid  1.3.1-2+b2
> ii  xdg-utils  1.1.1-1
>
> Versions of packages python3-reportbug depends on:
> ii  apt1.5
> ii  file   1:5.32-1
> ii  python33.5.3-3
> ii  python3-debian 0.1.31
> ii  python3-debianbts  2.6.3
> ii  python3-requests   2.18.1-1
>
> python3-reportbug suggests no packages.
>
> -- no debconf information
>



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#878179: ITP: mate-window-applets -- MATE Window Applets (WindowButtons, WindowTitle and WindowMenu Applets for the MATE Panel)

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: mate-window-applets
  Version : 1.5
  Upstream Author : IKRadulov (https://github.com/IKRadulov)
* URL : https://github.com/IKRadulov/mate-window-applets
* License : GPL-3+
  Programming Lang: Vala
  Description : MATE Window Applets (WindowButtons, WindowTitle and 
WindowMenu Applets for the MATE Panel)

 The MATE Window Applets collection provides various applets to show
 window control elements in the MATE Panel.
 .
 TheWindowButtons applet shows you close, minimize, actions.
 .
 The WindowTitle applet shows you the class, title, role, xid, pid of
 the active window.
 .
 The WindowMenu applet shows you the window menu of the active window.

Bug#877418: Is strip-nondeterminism causing performance regressions in your packages?

[Paul Gevers]

[Resending to the bug. It seems I am not allowed to post this message to
debian-devel@l.d.o. I did send it first on on 2017-10-04 19:51 +0200]

Hi Chris,

On 04-10-17 13:43, Chris Lamb wrote:
>  a) Ship both compiled & source in the .deb
> 
> and
> 
>  b) Do a *runtime* timestamp comparison between the two.

Yes, FreePascal does such a thing. And it is causing me headaches
already. I introduced a helper script to fix some of the issues called
fp-fix-timestamps¹. It isn't great, but it does the job so far for
multiple packages. If strip-nondeterminism could support ppu files as
well, that would be awesome (I never realized that it could).

Paul

¹ https://manpages.debian.org/stretch/fp-utils/fp-fix-timestamps.1.en.html







signature.asc
Description: OpenPGP digital signature

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

[Ian Campbell]

On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote:
> Thanks for the patch Ian.
> 
> I merged it [1] but then noticed that it introduces two lintian problems:
> 
>   E: libhdhomerun4: ldconfig-symlink-missing-for-shlib 
> usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 
> usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 libhdhomerun.so.4
>   W: libhdhomerun4: dev-pkg-without-shlib-symlink 
> usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 
> usr/lib/x86_64-linux-gnu/libhdhomerun.so

Sorry, I don't know how I missed that. Looking now I only actually see
the second one (the warning). It's fixed by the additional patch below
(note the mode change as well as the content change).

Not sure about the error though since I don't see it, but perhaps the
same patch helps there?

Ian.

diff --git a/debian/libhdhomerun-dev.install b/debian/libhdhomerun-dev.install
old mode 100644
new mode 100755
index 5101440..4d7dbdf
--- a/debian/libhdhomerun-dev.install
+++ b/debian/libhdhomerun-dev.install
@@ -1,2 +1,3 @@
+#! /usr/bin/dh-exec
 *.h /usr/include/libhdhomerun
-*.so /usr/lib
+*.so /usr/lib/${DEB_HOST_MULTIARCH}

Bug#869222: Invalid DNSSEC signatures

[Chris Hofstaedtler]

* Arnaud Launay  [171010 15:48]:
> Any chance on seeing this bug corrected in regular stretch (or at
> least as a backport) ?

stretch-pu bug: #878173

Cheers,
C.

Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package

[Thorsten Glaser]

On Tue, 10 Oct 2017, Fabian Greffrath wrote:

> Hi again,

same,

> Am Dienstag, den 10.10.2017, 17:41 +0200 schrieb Thorsten Glaser:
> > What if they decide to stop shipping it?
>
> then we would proceed as we did for the previous soundfont they
> provided, i.e. timgm6mb-soundfont. That is, we would continue to
> package it in its own source package.

Yes, as you argued later on in your eMail.

> .o(On the other hand, musescore requires a soundfont to be installed in
> order to work, so why should they ever stop shipping one? In that case,

They could switch to a different one, is what I meant.

(or embed it in the C source… *shudder*)

> > Yes, but, I’m a MuseScore user, and so really really *really* wish
> > to not prevent getting a newer version.
>
> I don't think the soundfont is to blame for the slow adaption of
> musescore 2.0 in Debian. It was just the usual packaging glue. ;)

No, I got a .dsc from Toby way before it entered Debian, which worked
with only the most minor tweaks (it *was* intended for his PPA), and
the soundfont slowed getting it uploaded to Debian by quite a bit.

I hope I’ll be able to speed things up in the future now, though. I
was a new to-be-a-user-soon back then only learning of its existence
by a workshop a fellow choir member gave.

> If future problems arise with the soundfont, we will package it in its
> own source package and upload new musescore releases to experimental in

Exactly. Good that we’re on the same page.

> > I can do that, but thanks.
>
> Cool, thank you!

Uploaded, should enter NEW any time now.

bye,
//mirabilos
-- 
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”  ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die!

Bug#873531: Additional info.

[Tim]

Hi,

I really don't know if this report was worth sending.  This system has 
run GNOME really well since before wheezy.  The hardware, though not 
weak, is getting older.  Switching to Cinnamon DE has solved any 
problems I was having.


Tim

Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package

[Fabian Greffrath]

Hi again,

Am Dienstag, den 10.10.2017, 17:41 +0200 schrieb Thorsten Glaser:
> What if they decide to stop shipping it?

then we would proceed as we did for the previous soundfont they
provided, i.e. timgm6mb-soundfont. That is, we would continue to
package it in its own source package.

.o(On the other hand, musescore requires a soundfont to be installed in
order to work, so why should they ever stop shipping one? In that case,
we would have to ship the soundfont in its own source package anyway,
and in the meantime musescore could/would have to use one of the other
soundfonts already packaged in Debian -- it is still able to read the
SF2 format after all.)

> Yes, but, I’m a MuseScore user, and so really really *really* wish
> to not prevent getting a newer version.

I don't think the soundfont is to blame for the slow adaption of
musescore 2.0 in Debian. It was just the usual packaging glue. ;)

If future problems arise with the soundfont, we will package it in its
own source package and upload new musescore releases to experimental in
the mean time. I don't see why this should be so much different from
any other "transition". ;)

> I can do that, but thanks.

Cool, thank you!

 - Fabian


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

Bug#878177: aptitude: Use of the word "invalid" in error msgs should be restored to meaning

[Anonymous]

Package: aptitude
Version: 0.6.11-1+b1
Severity: minor

Dear Maintainer,

Aptitude's error messages often create confusion, either due to
vagueness or improper use of English.  In particular, use of the word
/invalid/ in the following warning message needs to be re-examined:

W: GPG error: tor+http://wertarbyte.de/apt ./ Release: The following 
signatures were invalid: CC49F74C816C499C899A42885145B9CD752C0197
E: The repository 'tor+http://wertarbyte.de/apt ./ Release' is not signed.
E: Failed to download some files

After a costly investigation involving multiple developers, it was
discovered that the apt team has taken an objective word
(valid/invalid) out of context and given it a new subjective meaning.
A signature is "valid" when whatever algorithm used determines it is
valid.  This is not subjective.  It is a matter of fact and is
mathematically provable.

In the above case, a valid signature was falsely reported as invalid
by aptitude because the algorithm (SHA1) was considered substandard in
the opinion of the apt team.  It's a reasonable opinion to have, but
please express it in a way that does not hi-jack a term that has a
different common understanding with a higher mathematical purpose.
There are many ways to express that warning in a non-misleading way:

 * The following signatures were valid but substandard
 * The following signatures do not meet apt team standards
 * The algorithm used by the signature is not worthy
 * The signature does not use a debian-accepted hash
 * No approval granted for the hash used in the following signature
 * The following signature does not conform to debian security standards

In the course of investigating, gpg confirmed that the SHA1 sig was
*valid*, and rightly so.  When aptitude debug output was enabled,
there was still no indication of what aptitude did, or why it did it.
There was no mention that SHA1 was insufficient, or even that SHA1 was
used, or whether it's a factor.  The man page also says nothing about
this.  So in addition to a false error msg, aptitude is not doing what
it's documented to do.

-- Package-specific info:
Terminal: screen
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.11 compiled at Nov  8 2014 13:34:39
Compiler: g++ 4.9.1
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.4.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20140913
  cwidget version: 0.5.17
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x7fffc5ff4000)
/usr/lib/torsocks/libtorsocks.so (0x7fc1d058b000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 
(0x7fc1d021b000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fc1cffe5000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fc1cfdbb000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fc1cfbb5000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fc1cf89f000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fc1cf5d6000)
libboost_iostreams.so.1.55.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7fc1cf3be000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fc1cefad000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc1ced9)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fc1cea85000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc1ce784000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fc1ce56e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc1ce1c3000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc1cdfbf000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fc1cddbc000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fc1cdba1000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fc1cd991000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fc1cd76e000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fc1cd566000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fc1cd361000)
/lib64/ld-linux-x86-64.so.2 (0x7fc1d0df)

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

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

Versions of packages aptitude depends on:
ii  aptitude-common   0.6.11-1
ii  libapt-pkg4.121.0.9.8.3
ii  libboost-iostreams1.55.0  1.55.0+dfsg-3
ii  libc6 

Bug#878176: reportbug: have a way to have a fake/mungled subject in order to have $editor start without needing to write subject

[shirish शिरीष]

Package: reportbug
Version: 7.1.7
Severity: wishlist

Dear Maintainer,

Right now, I need to put up a subject each time I want to get the
system state of the package including depends, recommends in a compact
manner. It feels tedious to write the subject every time specifically
when I need to share the system state with upstream of a package. I
also did have a cursory look at bugs.debian.org/reportbug but couldn't
find any which talk about this issue as well as didn't find this
functionality in the manpage given.


-- Package-specific info:
** Environment settings:
PAGER="less"
INTERFACE="text"

** /home/shirish/.reportbugrc:
reportbug_version "7.1.4"
mode standard
ui text
offline
email "shir...@deb.org"
no-cc
header "X-Debbugs-CC: shir...@deb.org"
smtphost shirish.deb.org
editor "leafpad"

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

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

Versions of packages reportbug depends on:
ii  apt1.5
ii  python33.5.3-3
ii  python3-reportbug  7.1.7

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf-utils  1.5.63
ii  debsums2.2.2
ii  dlocate1.07+nmu1
ii  emacs25-bin-common 25.2+1-6
ii  exim4  4.89-7
ii  exim4-daemon-light [mail-transport-agent]  4.89-7
ii  file   1:5.32-1
ii  gir1.2-gtk-3.0 3.22.21-1
ii  gir1.2-vte-2.910.50.0-1
ii  gnupg  2.2.1-1
ii  python3-gi 3.24.1-3
ii  python3-gi-cairo   3.24.1-3
ii  python3-gtkspellcheck  4.0.5-1
ii  python3-urwid  1.3.1-2+b2
ii  xdg-utils  1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt1.5
ii  file   1:5.32-1
ii  python33.5.3-3
ii  python3-debian 0.1.31
ii  python3-debianbts  2.6.3
ii  python3-requests   2.18.1-1

python3-reportbug suggests no packages.

-- no debconf information

Bug#858155: RFS: stenc/1.0.7-1 [ITP]

[Herbert Fortes]

Hi Denys Berkovskyy and Andrey Rahmatullin,

>On Tue, 26 Sep 2017 15:34:35 +0100 Denys Berkovskyy  
>wrote:
>
> > On 8 Aug 2017, at 19:22, Andrey Rahmatullin  wrote:
> >
> > On Mon, Aug 07, 2017 at 11:52:33AM +0100, Denys Berkovskyy wrote:
> >> Thank you for your comments, I have made the changes you mentioned and 
> >> uploaded updated version to https://mentors.debian.net/package/stenc
> > debian/compat is still 9.
> > Also, please change priority to optional (and you should have done that
> > while updating to the Standards-Version 4.0.1, as you don't just bump the
> > version, you read
> > https://www.debian.org/doc/debian-policy/upgrading-checklist.html).
> >
> > --
> > WBR, wRAR
>
> I fixed the issues and uploaded new version to mentors: 
> https://mentors.debian.net/package/stenc 
> 
> Standards-Version is 4.1.0 now. Hopefully I haven't missed anything.
>

It seems that the package is ready. Andrey Rahmatullin
did the review.

The last activity was on 01 Oct 2017;  I can take one last
look in the package and upload it if the is no problem with
that.

Standards-Version is 4.1.1 now.



Regards,
Herbert

Bug#878175: RFS: python-mechanicalsoup/0.8.0-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the following package:

* Package name: python-mechanicalsoup
  Version : 0.8.0-1
  Upstream Author : Mirth Hickford 
* URL : https://github.com/hickford/MechanicalSoup
* License : Expat
  Section : python

One can check out the package by visiting the following URL:


https://anonscm.debian.org/cgit/python-modules/packages/python-mechanicalsoup.git

Changes since last upload:

  * Add recommended get-orig-source target
  * New upstream version 0.8.0
  * Bump the minimum Python versions to 2.7 and 3.4
  * Fixup the Vcs-Browser URI
  * Bump the standards version to 4.1.1
  * Avoid dependency on pytest-runner
- New patch No-pytest-runner.patch
  * Move extend-diff-ignore to d/s/options

Best regards,
Ghis

Bug#878174: RFS: pytest-qt/2.2.1-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the following package:

* Package name: pytest-qt
  Version : 2.2.1-1
  Upstream Author : Bruno Oliveira
* URL : https://github.com/pytest-dev/pytest-qt
* License : Expat
  Section : python

Please check out the package by visiting the following URL:

  https://anonscm.debian.org/cgit/python-modules/packages/pytest-qt.git

Changes since the last upload:

  * New upstream version 2.2.1
  * Add choice of PyQt APIs to Recommends
  * Bump the standards version to 4.1.1

Regards,
Ghis

Bug#878173: stretch-pu: package pdns/4.0.3-1+deb9u1

[Christian Hofstaedtler]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear Release Team,

pdns before 4.0.4 replies incorrectly to DNS questions with the
DNSSEC query bit (DO) set, when the query also uses the "0x20"
mechanism to increase spoofing resistance.

Unfortunately this is the configuration letsencrypt uses to check
for CAA records on domains. This implies letsencrypt being broken
for all users that have domains on pdns from stretch.

Upstream has fixed this in 4.0.4, but that didn't make it into
stretch.

There is more discussion on this in Debian bug #869222 and
at https://github.com/PowerDNS/pdns/issues/5546 and at
https://community.letsencrypt.org/t/caa-servfail-changes/38298/2

I have imported a minimal patch from upstream and attached the
debdiff. Please let me know if this looks good or if I got something
wrong.

Thanks,
Chris

diff -Nru pdns-4.0.3/debian/changelog pdns-4.0.3/debian/changelog
--- pdns-4.0.3/debian/changelog 2017-01-19 23:05:09.0 +
+++ pdns-4.0.3/debian/changelog 2017-10-10 18:08:15.0 +
@@ -1,3 +1,9 @@
+pdns (4.0.3-1+deb9u1) stable; urgency=medium
+
+  * Fix incorrect qname casing in NSEC3 generation (Closes: #869222)
+
+ -- Christian Hofstaedtler   Tue, 10 Oct 2017 18:08:15 +
+
 pdns (4.0.3-1) unstable; urgency=medium
 
   * New upstream version 4.0.3, fixing bug when running bindbackend
diff -Nru 
pdns-4.0.3/debian/patches/869222-lowercase-qname-before-NSEC-generation.patch 
pdns-4.0.3/debian/patches/869222-lowercase-qname-before-NSEC-generation.patch
--- 
pdns-4.0.3/debian/patches/869222-lowercase-qname-before-NSEC-generation.patch   
1970-01-01 00:00:00.0 +
+++ 
pdns-4.0.3/debian/patches/869222-lowercase-qname-before-NSEC-generation.patch   
2017-10-10 18:08:15.0 +
@@ -0,0 +1,25 @@
+From b91cfe5c069df975176f5fd944540f72fc5d01bb Mon Sep 17 00:00:00 2001
+From: Kees Monshouwer 
+Date: Wed, 3 May 2017 21:49:11 +0200
+Subject: [PATCH] auth: lowercase qname before NSEC generation
+
+[z...@debian.org]: Patch from upstream PR #5289.
+https://github.com/PowerDNS/pdns/commit/b91cfe5c069df975176f5fd944540f72fc5d01bb
+
+---
+ pdns/dnsbackend.cc | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/pdns/dnsbackend.cc b/pdns/dnsbackend.cc
+index 4e43ffc2b1..2454d6efb8 100644
+--- a/pdns/dnsbackend.cc
 b/pdns/dnsbackend.cc
+@@ -273,7 +273,7 @@ bool DNSBackend::getBeforeAndAfterNames(uint32_t id, const 
DNSName& zonename, co
+   // lcqname=labelReverse(lcqname);
+   DNSName dnc;
+   string relqname, sbefore, safter;
+-  relqname=labelReverse(makeRelative(qname.toStringNoDot(), 
zonename.toStringNoDot())); // FIXME400
++  relqname=labelReverse(makeRelative(toLower(qname.toStringNoDot()), 
zonename.toStringNoDot()));
+   //sbefore = before.toString();
+   //safter = after.toString();
+   bool ret = this->getBeforeAndAfterNamesAbsolute(id, relqname, dnc, sbefore, 
safter);
diff -Nru pdns-4.0.3/debian/patches/series pdns-4.0.3/debian/patches/series
--- pdns-4.0.3/debian/patches/series1970-01-01 00:00:00.0 +
+++ pdns-4.0.3/debian/patches/series2017-10-10 18:08:15.0 +
@@ -0,0 +1 @@
+869222-lowercase-qname-before-NSEC-generation.patch

Bug#877581: Patch

[intrigeri]

Control: tag -1 + pending

Hi,

Vincas Dargis:
> Indeed, with 4.14 I got my first Debian network (potential) denies (yay! :-D 
> ):

Nice, it's good news in some way :)

> Anyway, patch suggested by Christian Boltz fixes these issues, which is 
> attached.

Thanks. I've imported it as a quilt patch, adjusted a bit the embedded
"TODO", added a bunch of DEP-3 metadata and committed locally.
Will push to Vcs-Bzr once I get back online.

I'll try to do some testing myself with Linux 4.13 and 4.14 before
I upload, but if I don't manage to find time to test this early
enough, I'll upload anyway: your testing + Christian's input + my code
review is enough to make me confident this patch can only
improve things.

I'm a little bit curious wrt. whether this patch will be enough.
If you have extra time/desire to spend on this, you could test
profiles in the archive that don't include the nameservice abstraction
(there are some on my system) and thus won't be fixed by this patch
*if* they happen to need similar "unix" permissions.

Cheers,
-- 
intrigeri

Bug#795431: Fix for #795431 v2

[intrigeri]

Control: tag -1 + pending

Hi Vincas,

Vincas Dargis:
> Patch v2.

Thanks a lot! Applied locally, will push once I get back online.

I've fixed two issues:

1. It seems that your replacement worked fine in most cases (i.e.
   we now have "$package provides") but in some cases I see "$package
   package provides", which sounds weird to my ear.

2. Apparently you had missed apparmor-utils.

Cheers,
-- 
intrigeri

Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

[intrigeri]

Hi,

Vincas Dargis:
> On 2017.09.30 08:27, intrigeri wrote:
>> Interestingly
>> http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Execute_rules
>> says that Pux is supported since 2.5, so I wonder who's correct.

Thanks to everyone who helped clarifying this matter :)

>> Replacing Pux with pux fixes the problem you've seen here, and better
>> expresses what I intended initially.
>>
>> Can you please confirm? If that works, would you be up to
>> update my merge request upstream accordingly:
>> https://code.launchpad.net/~intrigeri/apparmor-profiles/+git/apparmor-profiles/+merge/331058

> Yes, using `pux` fixes the issue.

Great!

> Not sure what updating mere request means. Should I simply create new MR with 
> alternative `pux`?

Yes: fork a branch based on mine, add a commit with this change and an
suitable justification, create a new MR and add a note on mine to say
it's obsoleted by yours (I'll close it).

>> … and then propose a branch forked off current Vcs-Git on the Debian side?

> Sorry I do not follow, how do I propose branch for Debian?

Fork the repo somewhere, push your branch there, and point to it from
this bug report (with a "Control: tag -1 + patch" pseudo-header).

Please ensure you update debian/README.Debian accordingly so it points
to the correct upstream MR :)

Cheers,
-- 
intrigeri

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

[Francois Marier]

Thanks for the patch Ian.

I merged it [1] but then noticed that it introduces two lintian problems:

  E: libhdhomerun4: ldconfig-symlink-missing-for-shlib 
usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 
usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 libhdhomerun.so.4
  W: libhdhomerun4: dev-pkg-without-shlib-symlink 
usr/lib/x86_64-linux-gnu/libhdhomerun.so.4.0.0 
usr/lib/x86_64-linux-gnu/libhdhomerun.so

Francois

[1] 
https://anonscm.debian.org/git/collab-maint/libhdhomerun.git/commit/?id=a90d4674879f2331b7bd331a1136afb8bd1e3587

Bug#878171: vmdebootstrap: misformatted man page

[Cyril Brulebois]

Package: vmdebootstrap
Version: 1.7-1
Severity: minor

Hi,

Here's how vmdebootstrap's manpage is formatted:

  1:| VMDEBOOTSTRAP(8)   System Manager's Manual
  VMDEBOOTSTRAP(8)
  2:| 
  3:| " "vmdebootstrap"
  4:| 
  5:| NAME
  6:|vmdebootstrap - install basic Debian system into virtual disk image
  7:| 
  8:| PURPOSE

It seems there's an extraneous line (#3).


KiBi.

Bug#878172: tor_bug_occurred_(): Bug: ../src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv == TOR_COMPRESS_OK)...

[Gerald Turner]

Package: tor
Version: 0.3.1.7-1~bpo9+1
Severity: normal

Dear Maintainer,

I run a tor relay/exit running on stretch and I upgraded to the
stretch-backports 0.3.1.7-1~bpo9+1 version that recently became
available.

About every two hours the following is logged:

  Oct 10 09:30:20 ghatanothoa Tor[30872]: tor_bug_occurred_(): Bug: 
../src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv 
== TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) 
failed. (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: Non-fatal assertion !((rv == 
TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) failed 
in tor_compress_process at ../src/common/compress.c:576. Stack trace: (on Tor 
0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(log_backtrace+0x44) [0x5571c1ed4194] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(tor_bug_occurred_+0xb9) [0x5571c1eed029] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(tor_compress_process+0x135) [0x5571c1ef5fa5] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(+0x18e171) 
[0x5571c1ef6171] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(tor_uncompress+0x31) [0x5571c1ef6631] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(connection_dir_reached_eof+0x118c) [0x5571c1e9866c] (on Tor 
0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(+0x1089bc) 
[0x5571c1e709bc] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(+0x4d85e) 
[0x5571c1db585e] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x6a0) 
[0x7f5d4ca3a5a0] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(do_main_loop+0x29d) [0x5571c1db698d] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/usr/bin/tor(tor_main+0x1c35) [0x5571c1dba4d5] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(main+0x19) 
[0x5571c1db2189] (on Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5d4b49c2b1] (on 
Tor 0.3.1.7 )
  Oct 10 09:30:20 ghatanothoa Tor[30872]: Bug: /usr/bin/tor(_start+0x2a) 
[0x5571c1db21da] (on Tor 0.3.1.7 )
  Oct 10 09:37:27 ghatanothoa Tor[30872]: Tried to establish rendezvous on 
non-OR circuit with purpose Acting as rendevous (pending)

It looks like upstream bug 22719:

  https://trac.torproject.org/projects/tor/ticket/22719

I have the same package running on several other hosts that are not
relays that never see this error.

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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libevent-2.0-5   2.0.21-stable-3
ii  liblzma5 5.2.2-1.2+b1
ii  libseccomp2  2.3.1-2.1
ii  libssl1.11.1.0f-3
ii  libsystemd0  232-25+deb9u1
ii  libzstd1 1.1.2-1
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages tor recommends:
ii  logrotate3.11.0-0.1
ii  tor-geoipdb  0.2.9.12-1
ii  torsocks 2.2.0-1+deb9u1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  obfs4proxy   
pn  obfsproxy
pn  socat
ii  tor-arm  1.4.5.0-1.1
pn  torbrowser-launcher  

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- no debconf information

-- 
Gerald Turner Encrypted mail preferred!
OpenPGP: 4096R / CA89 B27A 30FA 66C5 1B80  3858 EC94 2276 FDB8 716D


signature.asc
Description: PGP signature

Bug#878164: dunst systemd service and dbus service are both suboptimal

[Daniel Kahn Gillmor]

On Tue 2017-10-10 19:16:28 +0200, Michael Stapelberg wrote:
> Please refer to https://github.com/systemd/systemd/issues/892. I have
> only skimmed that, so if you could figure out what we need to change
> upstream in dunst or downstream in the packaging to make this work,
> that’d be appreciated. Thanks!

thanks for the quick response, Michael!

hm, i can't see how that's exactly related to this problem, though i'm
pretty sure i don't understand all the moving parts.

also, that issue appears to have been closed upstream a few months ago.
does it need re-opening?

sorry to not have any good suggestions here.

 --dkg

Bug#871570:

[Steve Laursen]

Why is this hackturd not jailled?