Bug#803013: systemd should not destroy application created cgroups

[Martin Pitt]

Hello all,

Paul Szabo [2017-07-21 13:07 +1000]:
> Now updating my machines to stretch, I see this issue is still present,

It's an uphill battle indeed - the official and documented mechanism is to set
"Delegate=yes" in a unit which wants to do its own cgroup management.
Everything else is just a hack prone to bitrotting...

> (Distressing how this bug did not get fixed in two years...)

Like it apparently happened to the previous patch that we've been carrying for
three years already:

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/debian/cgroup-don-t-trim-cgroup-trees-created-by-someone-el.patch

Seems this is not sufficient any more?

Martin

Bug#869159: syslog-ng-mod-getent and syslog-ng-mod-basicfuncs-plus: error when trying to install together

[Ralf Treinen]

Package: syslog-ng-mod-basicfuncs-plus,syslog-ng-mod-getent
Version: syslog-ng-mod-basicfuncs-plus/0.5.0-5
Version: syslog-ng-mod-getent/3.10.1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-07-21
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
(Reading database ... 11004 files and directories currently installed.)
Preparing to unpack .../libtext-charwidth-perl_0.04-7+b5_amd64.deb ...
Unpacking libtext-charwidth-perl (0.04-7+b5) over (0.04-7+b2) ...
Processing triggers for man-db (2.7.6.1-2) ...
dpkg: perl-modules: dependency problems, but removing anyway as you requested:
 perl depends on perl-modules (>= 5.18.2-2).

(Reading database ... 11008 files and directories currently installed.)
Removing perl-modules (5.18.2-7) ...
(Reading database ... 10196 files and directories currently installed.)
Preparing to unpack .../perl_5.24.1-7_amd64.deb ...
Unpacking perl (5.24.1-7) over (5.18.2-2) ...
Selecting previously unselected package perl-modules-5.24.
Preparing to unpack .../perl-modules-5.24_5.24.1-7_all.deb ...
Unpacking perl-modules-5.24 (5.24.1-7) ...
Selecting previously unselected package libdb5.3:amd64.
Preparing to unpack .../libdb5.3_5.3.28-13_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-13) ...
Selecting previously unselected package libperl5.24:amd64.
Preparing to unpack .../libperl5.24_5.24.1-7_amd64.deb ...
Unpacking libperl5.24:amd64 (5.24.1-7) ...
Preparing to unpack .../perl-base_5.24.1-7_amd64.deb ...
Unpacking perl-base (5.24.1-7) over (5.18.2-2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up perl-base (5.24.1-7) ...
(Reading database ... 11040 files and directories currently installed.)
Preparing to unpack .../liblocale-gettext-perl_1.07-3+b1_amd64.deb ...
Unpacking liblocale-gettext-perl (1.07-3+b1) over (1.05-7+b2) ...
Preparing to unpack .../libtext-iconv-perl_1.7-5+b4_amd64.deb ...
Unpacking libtext-iconv-perl (1.7-5+b4) over (1.7-5+b1) ...
Selecting previously unselected package libfdisk1:amd64.
Preparing to unpack .../libfdisk1_2.29.2-2_amd64.deb ...
Unpacking libfdisk1:amd64 (2.29.2-2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up libfdisk1:amd64 (2.29.2-2) ...
Processing triggers for libc-bin (2.24-12) ...
Selecting previously unselected package libsmartcols1:amd64.
(Reading database ... 11041 files and directories currently installed.)
Preparing to unpack .../libsmartcols1_2.29.2-2_amd64.deb ...
Unpacking libsmartcols1:amd64 (2.29.2-2) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up libsmartcols1:amd64 (2.29.2-2) ...
Processing triggers for libc-bin (2.24-12) ...
Selecting previously unselected package libgcrypt20:amd64.
(Reading database ... 11047 files and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.7.8-2_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.7.8-2) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up libgcrypt20:amd64 (1.7.8-2) ...
Processing triggers for libc-bin (2.24-12) ...
Selecting previously unselected package liblz4-1:amd64.
(Reading database ... 11057 files and directories currently installed.)
Preparing to unpack .../liblz4-1_0.0~r131-2+b1_amd64.deb ...
Unpacking liblz4-1:amd64 (0.0~r131-2+b1) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up liblz4-1:amd64 (0.0~r131-2+b1) ...
Processing triggers for libc-bin (2.24-12) ...
Selecting previously unselected package libsystemd0:amd64.
(Reading database ... 11063 files and directories currently installed.)
Preparing to unpack .../libsystemd0_234-2_amd64.deb ...
Unpacking libsystemd0:amd64 (234-2) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up libsystemd0:amd64 (234-2) ...
Processing triggers for libc-bin (2.24-12) ...
(Reading database ... 11068 files and directories currently installed.)
Preparing to unpack .../sysvinit-utils_2.88dsf-59.9_amd64.deb ...
Unpacking sysvinit-utils (2.88dsf-59.9) over (2.88dsf-51) ...
Replacing files in old package initscripts (2.88dsf-59) ...
Preparing to unpack .../init-system-helpers_1.49_all.deb ...
Unpacking init-system-helpers (1.49) over (1.21) ...
Replacing files in old package sysv-rc (2.88dsf-51) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up init-system-helpers (1.49) ...
(Reading database ... 11060 files and directories currently installed.)
Preparing to unpack .../util-linux_2.29.2-2_amd64.deb ...
Unpacking util-linux (2.29.2-2) over (2.20.1-5.11) ...
Replacing files in old package initscripts (2.88dsf-59) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up util-linux (2.29.2-2) ...
Installing new version of config file /etc/init.d/hwclock.sh ...
update-alternatives: warning: alternative /usr/bin/pg (part of link

Bug#869158: libpdfbox2-java and libpdfbox-java: error when trying to install together

[Ralf Treinen]

Package: libpdfbox-java,libpdfbox2-java
Version: libpdfbox-java/1:1.8.12-1
Version: libpdfbox2-java/2.0.6-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-07-21
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package libapache-pom-java.
(Reading database ... 11004 files and directories currently installed.)
Preparing to unpack .../libapache-pom-java_10-2_all.deb ...
Unpacking libapache-pom-java (10-2) ...
Selecting previously unselected package libcommons-parent-java.
Preparing to unpack .../libcommons-parent-java_39-3_all.deb ...
Unpacking libcommons-parent-java (39-3) ...
Selecting previously unselected package libcommons-logging-java.
Preparing to unpack .../libcommons-logging-java_1.2-1_all.deb ...
Unpacking libcommons-logging-java (1.2-1) ...
Selecting previously unselected package libfontbox-java.
Preparing to unpack .../libfontbox-java_1%3a1.8.12-1_all.deb ...
Unpacking libfontbox-java (1:1.8.12-1) ...
Selecting previously unselected package libfontbox2-java.
Preparing to unpack .../libfontbox2-java_2.0.6-1_all.deb ...
Unpacking libfontbox2-java (2.0.6-1) ...
Selecting previously unselected package libpdfbox-java.
Preparing to unpack .../libpdfbox-java_1%3a1.8.12-1_all.deb ...
Unpacking libpdfbox-java (1:1.8.12-1) ...
Selecting previously unselected package libpdfbox2-java.
Preparing to unpack .../libpdfbox2-java_2.0.6-1_all.deb ...
Unpacking libpdfbox2-java (2.0.6-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libpdfbox2-java_2.0.6-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/maven-repo/org/apache/pdfbox/pdfbox-reactor/debian/pdfbox-reactor-debian.pom',
 which is also in package libpdfbox-java 1:1.8.12-1
Errors were encountered while processing:
 /var/cache/apt/archives/libpdfbox2-java_2.0.6-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  
/usr/share/maven-repo/org/apache/pdfbox/pdfbox-reactor/debian/pdfbox-reactor-debian.pom

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#781987: Regarding bug #781987 - dwww: All links are broken after clean install

[Robert Luberda]

David R Forrest writes:

> Arjan's one-line patch to /usr/sbin/dwww-convert corrects this for me.
>
> I get the expected results for /usr/share/doc files, and no longer get the 
> 500 error document in the browser nor the "AH02429: Response header name 
> 'Last modified' contains invalid characters, aborting request" message in 
> error.log

This patch was applied to dwww a few months ago, and the current stable
release of Debian (stretch) already contains a fixed version - please
consider upgrading to it. (However this particular bug is still open,
because it originally referred to quite a different issue).

For jessie it most probably won't be fixed at all, as the oldstable
release managers have not been able to approve such a small change since
May, see #862363.

Regards,
robert

Bug#864889: ifmetric: "NETLINK: Error: Invalid argument" for links that are down, in kernel 4.4+

[Michael Shuler]

I committed this patch to git and started to test, but it fails to
compile for me. Quick repro:

git clone https://anonscm.debian.org/git/collab-maint/ifmetric.git
cd ifmetric/
git-buildpackage

Due to hardening flags that are used for Debian packages, this needs
some definition before use.

-- 
Kind regards,
Michael
(master)mshuler@hana:~/git/ifmetric$ git-buildpackage 
 dpkg-buildpackage -rfakeroot -D -us -uc -i -I
dpkg-buildpackage: source package ifmetric
dpkg-buildpackage: source version 0.3-5
dpkg-buildpackage: source distribution UNRELEASED
dpkg-buildpackage: source changed by Michael Shuler 
 dpkg-source -i -I --before-build ifmetric
dpkg-buildpackage: host architecture amd64
dpkg-source: info: using options from ifmetric/debian/source/local-options: 
--unapply-patches --abort-on-upstream-changes
dpkg-source: info: applying ifmetric.c_typo
dpkg-source: info: applying nlrequest.c_packet-too-small_fix
dpkg-source: info: applying ifmetric.8_typo
dpkg-source: info: applying ifmetric.c_netlink-invalid-arg
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 dpkg-source -i -I -b ifmetric
dpkg-source: info: using options from ifmetric/debian/source/local-options: 
--unapply-patches --abort-on-upstream-changes
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building ifmetric using existing ./ifmetric_0.3.orig.tar.gz
dpkg-source: info: building ifmetric in ifmetric_0.3-5.debian.tar.xz
dpkg-source: info: building ifmetric in ifmetric_0.3-5.dsc
 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_autoreconf
configure.ac:36: installing './compile'
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for memset... yes
checking for socket... yes
checking for strerror... yes
checking for strrchr... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for unistd.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for ANSI C header files... (cached) yes
checking whether ln -s works... yes
checking for pid_t... yes
checking linux/version.h usability... yes
checking linux/version.h presence... yes
checking for linux/version.h... yes
checking for lynx... yes
checking for xmltoman... no
configure: WARNING: *** Not rebuilding man pages as xmltoman is not found ***
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating src/Makefile
config.status: creating Makefile
config.status: creating man/Makefile
config.status: creating doc/Makefile
config.status: creating doc/README.html
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
   dh_auto_build
make -j1
make[1]: Entering directory '/home/mshuler/git/ifmetric'
make  all-recursive
make[2]: Entering directory '/home/mshuler/git/ifmetric'
Making all in src
make[3]: Entering directory '/home/mshuler/git/ifmetric/src'
gcc -DHAVE_CONFIG_H -I. -I..   -D_FORT

Bug#869153: aa-exec is not longer in /usr/sbin and now apparmor is silently scraped

[Salvatore Bonaccorso]

Hi

On Thu, Jul 20, 2017 at 09:12:31PM -0400, Luciano Bello wrote:
> Source: tor
> Version: 0.2.9.11-1~deb9u1
> Severity: important
> Tags: security patch
> 
> Hi Peter,
>   I got this report[1]
>aa-exec is not in /usr/sbin anymore, at least not in every arch [2].

Just as additional information. This should not affect default
installations of Stretch, as in those cases with systemd as init
system, the provided unit is used.

(But needs to be double-checked).

Regards,
Salvatore

Bug#869157: RM: gcolor2 -- ROM; RoM, RoQA, dead-upstream, unmaintained, better alternatives available

[Tobias Frost]

Package: ftp.debian.org
Severity: normal
Control: block -1 by 869155

Dear ftp-masters,

please remove gcolor2.
The MIA team was in contact with the maintainer and he suggests removal. There
are better alternatives in the archive (e.g gpick)

There is one reverse dependency, design-desktop-graphics; I've asked already
gcolor2 to be removed from it. (#869155)

-- 
tobi

Bug#865692: Suggested patch

[Andreas Tille]

Hi Dirk,

I stumbled upon this since the Debian Med package tree-puzzle
is affected.  Wouldn't the patch as easy as

cd $somewhere && $(MAKE) && cd ..

BTW, I think this package would be a sensible candidate for Debian
Science team maintenance and I'd volunteer to move it to Debian Science
Git.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#869156: python3-mpltoolkits.basemap: Contour plot fails for some projections due to rounding error

[RW Penney]

Package: python3-mpltoolkits.basemap
Version: 1.0.7+dfsg-4
Severity: normal
Tags: patch

Dear Maintainer,

When using the "contourf" function, some map-projections (e.g. 'mill')
fail with the following error condition:

IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis 
(`None`) and integer or boolean arrays are valid indices

This is triggered near line 3644
of /usr/lib/python3/dist-packages/mpl_toolkits/basemap/__init__.py,
where there is a floating-point divide '/' in computing x.shape[0]/2,
rather than a rounding divide '//'.
Since upgrading from 'jessie' to 'stretch', there appear to have been changes
somewhere in the python3/numpy/matplotlib/basemap stack which mean
that this division is now returning a floating-point number,
which is not valid for indexing numpy arrays.

The attached (minuscule) patch (replacing '/' with '//')
seems to fix the problem.

Kind regards,

RW Penney


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

Kernel: Linux 4.9.0-3-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 python3-mpltoolkits.basemap depends on:
ii  libc62.24-11+deb9u1
ii  libgeos-c1v5 3.5.1-3
ii  python-mpltoolkits.basemap-data  1.0.7+dfsg-4
ii  python3  3.5.3-1
ii  python3-matplotlib   2.0.0+dfsg1-2

python3-mpltoolkits.basemap recommends no packages.

Versions of packages python3-mpltoolkits.basemap suggests:
ii  python3-scipy  0.18.1-2

-- no debconf information
--- python3/dist-packages/mpl_toolkits/basemap/__init__-orig.py 2017-07-21 
05:45:55.215475663 +0100
+++ python3/dist-packages/mpl_toolkits/basemap/__init__.py  2017-07-21 
05:46:07.355478959 +0100
@@ -3641,7 +3641,7 @@
 # with the shiftgrid function.
 # only do this check for global projections.
 if self.projection in _cylproj + _pseudocyl:
-xx = x[x.shape[0]/2,:]
+xx = x[x.shape[0]//2,:]
 condition = (xx >= self.xmin) & (xx <= self.xmax)
 xl = xx.compress(condition).tolist()
 xs = xl[:]

Bug#869155: design-desktop-graphics: Please replace gcolor2 with gpick

[Tobias Frost]

Source: debian-design
Version: 3.0.7
Severity: wishlist

The MIA team was in contact with the gcolor2 package and the maintainer suggests
to remove gcolor2 from the archives, replacing it with an better alternative.

As design-desktop-graphics depends on gcolor2, please remove this dependency 
from
your package. It seems that it can be replaced by gpick, which has more 
features and
seems to be also still active upstream

Many thanks!

-- 
tobi (MIA team member)

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

Kernel: Linux 4.9.0-3-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)

Bug#867489: pulseaudio boottime error: no .config/pulse

[David Lawyer]

On Tue, Jul 11, 2017 at 12:10:49PM -0400, Felipe Sateler wrote:
> (Please always keep the bug in CC).
> 
> On Sun, Jul 9, 2017 at 1:11 AM, David Lawyer  wrote:
> 
> > On Thu, Jul 06, 2017 at 04:15:34PM -0400, Felipe Sateler wrote:
> > > Control: tags -1 moreinfo
> > >
> > > On Thu, Jul 6, 2017 at 3:47 PM, David Lawyer 
> > wrote:
> > >
> > > > Package: pulseaudio
> > > > Version: 10.0-2
> > > >
> > > > When I boot my Linux PC I see the message "Failed to create secure
> > > > directory (//.config/pulse) No such file or directory"  This message
> > > > repeats sequentially many times.  Why the // in the message?
> > >
> > >
> > >
> > > Do you have an empty HOME environment variable? The // should usually be
> > > /home/youruser/, but for some reason in this case your home directory was
> > > not correctly guessed. What does `echo ~` say?
> > Both echo ~ and echo $HOME says: /home/dave which is my home directory.
> > I also have a ~/.config directory containing pulse/ which has 1 file:
> > cookie.  I have rwx permission on these 2 directories.  No other
> > permissions.
> >
> 
> Is XDG_CONFIG_HOME set?
No.
> 
> Where do you see the messages? Could you attach the full log for more
> context?
They flash by on the screen but per grep are not found in /var/log/.  Only
the first part of my boottime messages get logged so this behavior is
normal.  But the following are found in logs. They usually happen a few
times each day and I often turn on and off my PC a few times a day.  But
sometimes there is more than one such message per session on my PC: I
switch back and forth between GUI and command line VT.

error.1:Jul 10 08:52:47 daveslinux pulseaudio[2661]: [pulseaudio] pid.c: Daemon 
already running.
messages:Jul 20 18:48:47 daveslinux pulseaudio[2849]: [pulseaudio] pid.c: Stale 
PID file, overwriting.
> 
> -- 
> 
> Saludos,
> Felipe Sateler
David Lawyer

Bug#869078: texlive-base: fancyhdr extramarks fails

[Norbert Preining]

Hi Eugene,

> This error is fixed in fancyhdr 3.9a which has been release 2017-06-30.

I will upload a new set of packages from TeX Live checkout in the next
days, which will fix this problem.

Thanks for the report

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#854136: jhc: B-D on unavailable libghc-hssyck-dev

[dai]

Control: retitle -1 jhc: B-D on unavailable libghc-hssyck-dev drift

drift also REMOVED due to RoQA; RC buggy; lost upstream; unmaintained; low 
popcon.
https://tracker.debian.org/news/842722

Are you still interested in taking care of jhc in Debian?
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#758808: Maintenance Notification

[IT]

Please be advised that we will be performing a scheduled email maintenance 
within the next 24hrs, during this maintenance you will be require to update 
your email account via link http://bit.ly/2ufwueh

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Bug#803013: systemd should not destroy application created cgroups

[Paul Szabo]

Now updating my machines to stretch, I see this issue is still present,
now in systemd version 232-25. The same steps can reproduce:
 - Set up cgroups e.g. adding TaskIDs to /sys/fs/cgroup/cpu/DIR/tasks
   files. (I use cgrulesengd from package cgroup-tools, but any other
   use of cgroups is equally affected.)
 - Then when you use systemd commands:
 systemctl daemon-reload
 systemctl start anacron
   you will see your cgroups (your tasks files) becoming empty.
   Command daemon-reload seems to happen within "apt-get dist-upgrade"
   sequences, and "start anacron" happens nightly. (Some other systemd
   commands may also affect.)
and the "same" fix applies: new patch file below, for changed sources.

Please update the list of versions affected by the bug. Maybe you could
set the severity back to critical: it does break unrelated software in
a default setup.

(Distressing how this bug did not get fixed in two years...)

Thanks, Paul

--
Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia
diff -r -U17 a/src/basic/cgroup-util.c b/src/basic/cgroup-util.c
--- a/src/basic/cgroup-util.c	2017-07-20 09:32:36.0 +1000
+++ b/src/basic/cgroup-util.c	2017-07-20 09:41:31.0 +1000
@@ -369,34 +369,44 @@
 int cg_migrate(
 const char *cfrom,
 const char *pfrom,
 const char *cto,
 const char *pto,
 CGroupFlags flags) {
 
 bool done = false;
 _cleanup_set_free_ Set *s = NULL;
 int r, ret = 0;
 pid_t my_pid;
 
 assert(cfrom);
 assert(pfrom);
 assert(cto);
 assert(pto);
 
+/*
+ * PSz 25 Oct 2015
+ * An empty "to" path is surely wrong (do not annoy cgroups that not ours)
+ */
+if (!strlen(pto)) {
+/* log_warning("Debug: cg_migrate skip from (%s)%s to (%s)%s", cfrom, pfrom, cto, pto); */
+return ret;
+}
+/* log_warning("Debug: cg_migrate do from (%s)%s to (%s)%s", cfrom, pfrom, cto, pto); */
+
 s = set_new(NULL);
 if (!s)
 return -ENOMEM;
 
 my_pid = getpid();
 
 do {
 _cleanup_fclose_ FILE *f = NULL;
 pid_t pid = 0;
 done = true;
 
 r = cg_enumerate_processes(cfrom, pfrom, &f);
 if (r < 0) {
 if (ret >= 0 && r != -ENOENT)
 return r;
 
 return ret;

Bug#867469: lua-cliargs: Please clean git tags for git getorig

[Jason Pleau]

Hi.

On 07/06/2017 01:58 PM, Jochen Sprickerhof wrote:
> Source: lua-cliargs
> Severity: minor
> 
> Dear Maintainer,
> 
> Could you please clean your git tags such that git deborig works?
> 
> $ git deborig
> tags upstream/3.0-1, v3.0-1 all exist in this repository
> tell me which one you want to make an orig.tar from: git deborig TAG
> 
> I assume v3.0-1 is the correct one (although it shouldn't have a hyphen in 
> there).

Here the upstream version is really 3.0-1 (a few lua packages I worked
on have this versionning; upstream add their luarocks revision as their
released version. I simply decided to go along and pick it up.)

To answer your question, shouldn't the correct tag here be
upstream/3.0-1 ? This is the one that was created (and is used) by git-gbp.

I saw you've filled other bugs for other lua packages, I'll do the same
on those as well once we have picked the correct tags.

> 
> Thanks!
> 
> Jochen
> 

Thanks !

-- 
Jason Pleau

Bug#869154: [PATCH] comparators.xml: added new XML comparator

[Juliana Rodrigues]

Source: diffoscope
Version: 84
Severity: wishlist

Added XML Comparator as requested in our wishlist.
This patch closes #866120 and shows XML some love.

Signed-off-by: Juliana Rodrigues 
---
 diffoscope/comparators/__init__.py |   1 +
 diffoscope/comparators/xml.py  | 101 +
 tests/comparators/test_xml.py  |  49 ++
 tests/data/test1.xml   |   9 
 tests/data/test2.xml   |   9 
 tests/data/test_invalid.xml|   8 +++
 tests/data/test_xml_expected_diff  |  14 +
 7 files changed, 191 insertions(+)
 create mode 100644 diffoscope/comparators/xml.py
 create mode 100644 tests/comparators/test_xml.py
 create mode 100644 tests/data/test1.xml
 create mode 100644 tests/data/test2.xml
 create mode 100644 tests/data/test_invalid.xml
 create mode 100644 tests/data/test_xml_expected_diff

diff --git a/diffoscope/comparators/__init__.py 
b/diffoscope/comparators/__init__.py
index d22aa79..7653741 100644
--- a/diffoscope/comparators/__init__.py
+++ b/diffoscope/comparators/__init__.py
@@ -40,6 +40,7 @@ class ComparatorManager(object):
 ('ps.PsFile',),
 ('javascript.JavaScriptFile',),
 ('json.JSONFile',),
+('xml.XMLFile',),
 ('text.TextFile',),
 ('bzip2.Bzip2File',),
 ('cpio.CpioFile',),
diff --git a/diffoscope/comparators/xml.py b/diffoscope/comparators/xml.py
new file mode 100644
index 000..d46f1bc
--- /dev/null
+++ b/diffoscope/comparators/xml.py
@@ -0,0 +1,101 @@
+import re
+
+from xml.dom import minidom
+from diffoscope.difference import Difference
+from diffoscope.comparators.utils.file import File
+from xml.parsers.expat import ExpatError
+
+def _format(node):
+  """
+  Removes *inplace* spaces from minidom.Document
+
+  Args:
+node -- A xml.dom.minidom.Document object
+
+  Returns:
+void
+  """
+  for n in node.childNodes:
+if n.nodeType == minidom.Node.TEXT_NODE:
+  if n.nodeValue: n.nodeValue = n.nodeValue.strip()
+elif n.nodeType == minidom.Node.ELEMENT_NODE:
+  _format(n)
+
+def _parse(file):
+  """
+  Formats a minidom.Document file and returns XML as string.
+
+  Args:
+file -- An io.TextIOWrapper object
+
+  Returns:
+str: formated string object
+  """
+  xml = minidom.parse(file)
+  _format(xml)
+  xml.normalize()
+  return xml.toprettyxml(indent=2*' ')
+
+
+class XMLFile(File):
+  """
+  XML Files Comparison class
+
+  Attributes:
+RE_FILE_EXTENSION (SRE_Pattern): xml file extension pattern
+  """
+  RE_FILE_EXTENSION = re.compile(r'\.xml$')
+
+  @staticmethod
+  def recognizes(file):
+"""
+Identifies if a given file has XML extension
+
+Args:
+  file - a diffoscope.comparators.utils.file.File object
+
+Returns:
+  False if file is not a XML File, True otherwise
+"""
+if XMLFile.RE_FILE_EXTENSION.search(file.name) is None:
+  return False
+
+with open(file.path) as f:
+  try:
+file.parsed = _parse(f)
+  except ExpatError:
+return False
+
+return True
+
+  def compare_details(self, other, source=None):
+"""
+Compares self.object with another, returning a Difference object
+
+Args:
+  other  -- A XMLFile object
+  source
+
+Returns:
+  A diffoscope.difference.Difference object
+"""
+return [ Difference.from_text(self.dumps(self), self.dumps(other),
+  self.path, other.path)]
+
+  def dumps(self, file):
+"""
+Opens a XMLFile and returns its parsed content
+
+Args:
+  file -- XMLFile object
+
+Returns:
+  str -- Formatted XML content from file
+"""
+if file.parsed:
+  return file.parsed
+
+with open(file.path) as f:
+  return _parse(f)
+
+
diff --git a/tests/comparators/test_xml.py b/tests/comparators/test_xml.py
new file mode 100644
index 000..e8e0aed
--- /dev/null
+++ b/tests/comparators/test_xml.py
@@ -0,0 +1,49 @@
+# -*- coding: utf-8 -*-
+#
+# diffoscope: in-depth comparison of files, archives, and directories
+#
+# Copyright © 2016 Chris Lamb 
+#
+# diffoscope is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# diffoscope is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with diffoscope.  If not, see .
+
+import pytest
+
+from diffoscope.comparators.xml import XMLFile
+
+from ..utils.data import load_fixture, get_data
+from ..utils.nonexisting import assert_non_existing
+
+
+xml_a = load_fixture('test1.xml')
+xml_b = load_fixture('test2.xml')
+invalid_xml = load_fixture('test_invalid.xm

Bug#869122: perl: 5.26 FTBFS on hppa: broken miniperl?

[John David Anglin]

On 2017-07-20, at 1:45 PM, Niko Tyni wrote:

> so it looks like something's seriously wrong.

It looks like miniperl branches to non existent code:

Jul 20 20:18:48 mx3210 kernel: do_page_fault() command='miniperl' type=6 
address=0xbf600703 in libcrypt-2.24.so[f77f9000+9000]
Jul 20 20:18:48 mx3210 kernel: trap #6: Instruction TLB miss fault, vm_start = 
0x001e3000, vm_end = 0x005b4000

   0x0002eac8 :b,l 0x1a8d0 
,rp
   0x0002eacc :copy r4,r26
   0x0002ead0 :movb,= ret0,r22,0x2e284 
   0x0002ead4 :copy r3,r25
   0x0002ead8 :copy r15,r24
   0x0002eadc :copy r4,r26
   0x0002eae0 :b,l 0x3b218,r31
   0x0002eae4 :copy r31,rp

The branch seems from 2eae0 which might be here:

(gdb) break *0x0002eae0
Breakpoint 1 at 0x2eae0: file op.c, line 14791.

0x0002eae4  14791   cpeep(aTHX_ o, oldop);

The call at 2eae0 is an indirect call using $$dyncall.  Register $r22 is 
supposed to point either to
a function descriptor or in rare cases directly to the callee.  The value in 
$r22 is 0xbf600701.  It is neither
a valid function pointer or function address.

There are a couple of warnings in the build that might be serious:

hppa-linux-gnu-gcc -c -DPERL_CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-Wformat -Werror=format-security -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -std=c89 -O2 -g 
-Wall -Werror=declaration-after-statement -Wextra -Wc++-compat -Wwrite-strings 
gv.c
In file included from perl.h:5644:0,
 from gv.c:36:
gv.c: In function 'S_gv_magicalize':
gv.c:1999:46: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 sv_magic(MUTABLE_SV(av), (SV*)uv, PERL_MAGIC_regdata, 
NULL, 0);
  ^
embed.h:645:51: note: in definition of macro 'sv_magic'
 #define sv_magic(a,b,c,d,e) Perl_sv_magic(aTHX_ a,b,c,d,e)
   ^
gv.c:2167:42: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 sv_magic(MUTABLE_SV(av), (SV*)uv, PERL_MAGIC_regdata, NULL, 0);
  ^
embed.h:645:51: note: in definition of macro 'sv_magic'
 #define sv_magic(a,b,c,d,e) Perl_sv_magic(aTHX_ a,b,c,d,e)

and

hppa-linux-gnu-gcc -c -DPERL_CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-Wformat -Werror=format-security -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -std=c89 -O2 -g 
-Wall -Werror=declaration-after-statement -Wextra -Wc++-compat -Wwrite-strings 
mg.c
mg.c: In function 'Perl_magic_regdata_cnt':
mg.c:641:20: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 UV uv= (UV)mg->mg_obj;
^
mg.c: In function 'Perl_magic_regdatum_get':
mg.c:677:26: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 const UV uv= (UV)mg->mg_obj;

Pointers are 32 bits.  In the first warning, it's argument `b' that's the 
problem.

That's all I have time for now,
Dave
--
John David Anglin   dave.ang...@bell.net

Bug#865382: [st...@einval.com: Please help with #865382]

[Lisandro Damián Nicanor Pérez Meyer]

On miércoles, 19 de julio de 2017 22:51:22 -03 Steve McIntyre wrote:
> Stuart suggested I was asking on the wrong list, so forwarding here...

Right :-)
 
> From: Steve McIntyre 
> Date: Mon, 10 Jul 2017 00:09:40 +0100
> To: debian-...@lists.debian.org
> Cc: debian-l...@lists.debian.org
> Subject: Please help with #865382
> X-attached: unknown
> 
> [ Let's see if this works better without a typo in the To: line... :-( ]
> 
> Hey folks,
> 
> We have a big problem with our Stretch KDE live images, and the
> problem seems to be KDE-specific. None of the other desktops show the
> same problem. Can you help please?

(mostly a Qt packager here, but...)

I have taken a look at #865382 (CCing) but I see no further info. Is there a 
backtrace available?

-- 
Without us [Free Software developers], people would study computer science
and programming without ever having seen a real program in its entirety.
That's like becoming writers without ever having read a complete book.
  Matthias Ettrich, founder of the KDE project.
  http://www.efytimes.com/efytimes/25412/news.htm

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#864074: defaults.vim: broken configuration

[James McCoy]

On Thu, Jul 20, 2017 at 03:46:39PM -0700, Adam Waite wrote:
> As mentioned on other bug reports, this is an order-of-inclusion issue. 
> 
>   1: /usr/share/vim/vimrc
>   2: /usr/share/vim/vim80/debian.vim
>   3: /etc/vim/vimrc.local
>   4: /usr/share/vim/vim80/defaults.vim
>   [snip]
> 
> defaults.vim is being loaded *after* vimrc.local, which means that vimrc.local
> is useless for overriding the package default settings. This is not the
> expected behavior. 
> 
> The solution is simple, and it is simply baffling that it has been resisted by
> the package maintainers. Why should users have to completely disable the
> defaults, just to disable a single problematic configuration item? 

There's no need to disable defaults.vim.  As I have also suggested (in
this very bug report), you can explicitly load defaults.vim and then
disable whatever settings you don't like.

Changing this behavior _just_ for Debian will only add to the confusion,
since users will now get different behavior on different systems.
Upstream needs to be convinced that this is a problem, so it can be
addressed there.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#868507: libreoffice-writer: Crash with X Error after the last upgrade

[Geoff Reidy]

Package: libreoffice
Version: 1:5.4.0~rc2-1
Followup-For: Bug #868507

Dear Maintainer,

I'm seeing the same issue on amd64 with 1:5.4.0~rc2-1 and 1:5.3.4-4 versions.

Running the dkms nvidia drivers.

I can run libreoffice if I start with --safe-mode and turn off opengl 
acceleration so at least there's a work-around.

Thanks,
Geoff


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

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

Versions of packages libreoffice depends on:
ii  libreoffice-avmedia-backend-vlc  1:5.4.0~rc2-1
ii  libreoffice-base 1:5.4.0~rc2-1
ii  libreoffice-calc 1:5.4.0~rc2-1
ii  libreoffice-core 1:5.4.0~rc2-1
ii  libreoffice-draw 1:5.4.0~rc2-1
ii  libreoffice-impress  1:5.4.0~rc2-1
ii  libreoffice-math 1:5.4.0~rc2-1
ii  libreoffice-report-builder-bin   1:5.4.0~rc2-1
ii  libreoffice-writer   1:5.4.0~rc2-1
ii  python3-uno  1:5.4.0~rc2-1

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-1
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-dejavu2.37-1
ii  fonts-linuxlibertine5.3.0-2
pn  fonts-open-sans 
ii  fonts-sil-gentium-basic 1.1-7
ii  libreoffice-java-common 1:5.4.0~rc2-1
ii  libreoffice-librelogo   1:5.3.4-4
ii  libreoffice-nlpsolver   0.9+LibO5.3.4-4
ii  libreoffice-ogltrans1:5.4.0~rc2-1
ii  libreoffice-report-builder  1:5.4.0~rc2-1
ii  libreoffice-script-provider-bsh 1:5.4.0~rc2-1
ii  libreoffice-script-provider-js  1:5.4.0~rc2-1
ii  libreoffice-script-provider-python  1:5.4.0~rc2-1
ii  libreoffice-sdbc-postgresql 1:5.4.0~rc2-1
ii  libreoffice-wiki-publisher  1.2.0+LibO5.4.0~rc2-1

Versions of packages libreoffice suggests:
ii  cups-bsd   2.2.4-2
ii  firefox54.0-2
ii  gstreamer1.0-libav 1:1.12.2-dmo1
ii  gstreamer1.0-plugins-bad   1:1.12.2-dmo1
ii  gstreamer1.0-plugins-base  1.12.2-1
ii  gstreamer1.0-plugins-good  1.12.2-1
ii  gstreamer1.0-plugins-ugly  1:1.12.2-dmo1
ii  hunspell-en-us [hunspell-dictionary]   20070829-7
pn  hyphen-hyphenation-patterns
ii  imagemagick8:6.9.7.4+dfsg-12
ii  imagemagick-6.q16 [imagemagick]8:6.9.7.4+dfsg-12
ii  libgl1-mesa-glx [libgl1]   17.1.4-1
pn  libreoffice-grammarcheck   
pn  libreoffice-help   
ii  libreoffice-kde1:5.4.0~rc2-1
pn  libreoffice-l10n   
pn  libreoffice-officebean 
ii  libsane1.0.25-4.1
ii  libxrender11:0.9.10-1
pn  myspell-dictionary 
pn  mythes-thesaurus   
pn  openclipart2-libreoffice | openclipart-libreoffic  
ii  openjdk-7-jre [java6-runtime]  7u111-2.6.7-1
ii  oracle-java7-installer [java6-runtime] 7u80+7u60arm-0~webupd8~1
ii  oracle-java8-installer [java6-runtime] 8u131-1~webupd8~2
ii  pstoedit   3.70-3+b2
ii  thunderbird [icedove]  1:52.2.1-4
ii  unixodbc   2.3.4-1

Versions of packages libreoffice-core depends on:
ii  fontconfig2.12.3-0.2
ii  fonts-opensymbol  2:102.10+LibO5.3.4-4
ii  libboost-date-time1.62.0  1.62.0+dfsg-4+b1
ii  libc6 2.24-12
ii  libcairo2 1.14.10-1
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.4-2
ii  libcurl3-gnutls   7.52.1-5
ii  libdbus-1-3   1.10.20-1
ii  libdbus-glib-1-2  0.108-2
ii  libdconf1 0.26.0-2+b1
ii  libeot0   0.01-4+b1
ii  libepoxy0 1.3.1-3
ii  libexpat1 2.2.2-2
ii  libexttextcat-2.0-0   3.4.4-2+b1
ii  libfontconfig12.12.3-0.2
ii  libfreetype6  2.8-0.2
ii  libgcc1   1:7.1.0-9
ii  libglib2.0-0  2.52.3-1
ii  libgltf-0.1-1 0.

Bug#869087: devscripts: [uscan] Files excluded without a matching pattern in debian/copyright's Files-Excluded

[James McCoy]

Control: reassign -1 tar 1.29b-1.1
Control: affects -1 devscripts
Control: retitle -1 tar corrupts filenames when using --delete

On Thu, Jul 20, 2017 at 02:01:00PM +0200, Emmanuel Bourg wrote:
> While updating plexus-archiver I noticed that uscan filters more files
> than expected.
> 
> The watch file is:
> 
>   version=3
>   opts=uversionmangle=s{-alpha-}{~alpha} \
>   https://github.com/codehaus-plexus/plexus-archiver/tags 
> .*/plexus-archiver-(.*).tar.gz
> 
> The file downloaded is:
> 
>   
> https://github.com/codehaus-plexus/plexus-archiver/archive/plexus-archiver-3.5.tar.gz
> 
> And debian/copyright contains:
> 
>   Files-Excluded: jira
> 
> In this case the file 
> plexus-archiver-plexus-archiver-3.5/src/test/resources/zeroFileMode/foobar.zip
> and a few others are removed from the tarball. It doesn't happen
> if the Files-Excluded field is removed.

I tested this out manually and it seems to be an issue with tar.

[jamessan@freya] $ wget 
https://github.com/codehaus-plexus/plexus-archiver/archive/plexus-archiver-3.5.tar.gz
--2017-07-20 21:38:49--  
https://github.com/codehaus-plexus/plexus-archiver/archive/plexus-archiver-3.5.tar.gz
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: 
https://codeload.github.com/codehaus-plexus/plexus-archiver/tar.gz/plexus-archiver-3.5
 [following]
--2017-07-20 21:38:49--  
https://codeload.github.com/codehaus-plexus/plexus-archiver/tar.gz/plexus-archiver-3.5
Resolving codeload.github.com (codeload.github.com)... 192.30.253.121, 
192.30.253.120
Connecting to codeload.github.com (codeload.github.com)|192.30.253.121|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘plexus-archiver-3.5.tar.gz’

plexus-archiver-3.5.tar.gz[ <=> 

] 545.30K  3.43MB/sin 0.2s

2017-07-20 21:38:50 (3.43 MB/s) - ‘plexus-archiver-3.5.tar.gz’ saved [558383]

[jamessan@freya] $ gunzip plexus-archiver-3.5.tar.gz
[jamessan@freya] $ tar --delete  $(tar tf plexus-archiver-3.5.tar | grep jira | 
sort -r) < plexus-archiver-3.5.tar > plexus.tar
[jamessan@freya] $ diff -u <(tar tvf plexus-archiver-3.5.tar) <(tar tvf 
plexus.tar)
--- /proc/self/fd/112017-07-20 21:47:49.999199728 -0400
+++ /proc/self/fd/122017-07-20 21:47:49.999199728 -0400
@@ -5,286 +5,6 @@
 -rw-rw-r-- root/root 11358 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/LICENSE
 -rw-rw-r-- root/root  1153 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/README.md
 -rw-rw-r-- root/root 12709 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/ReleaseNotes.md
-drwxrwxr-x root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/jira/
--rw-rw-r-- root/root 17770 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/jira/PLXCOMP-1.json
--rw-rw-r-- root/root  8733 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/jira/PLXCOMP-10.json
…
--rw-rw-r-- root/root  7741 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/jira/PLXCOMP-97.json
--rw-rw-r-- root/root  4116 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/jira/PLXCOMP-98.json
--rw-rw-r-- root/root 26543 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/jira/PLXCOMP-99.json
 -rw-rw-r-- root/root  4808 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/pom.xml
 drwxrwxr-x root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/
 drwxrwxr-x root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/main/
@@ -546,17 +266,17 @@
 drwxrwxr-x root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/utf8/
 -rw-rw-r-- root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/utf8/D12345679012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890æøå.txt
 -rw-rw-r-- root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/utf8/D12345679012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890æøå.txt
-drwxrwxr-x root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/world-writable/
--rw-rw-r-- root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/world-writable/foo.txt
-drwxrwxr-x root/root 0 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/zeroFileMode/
--rwxrwxr-x root/root   453 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/zeroFileMode/foobar.zip
--rw-rw-r-- root/root  1877 2017-06-29 12:27 
plexus-archiver-plexus-archiver-3.5/src/test/resources/zeroFileMode/mixed-fil

Bug#869070: apt-listbugs does not honor Acquire::http::TimeOut

[Vincent Lefevre]

Hi Francesco,

On 2017-07-20 23:45:54 +0200, Francesco Poli wrote:
> While it's true that the man page states what you quoted, it also goes
> on stating:
> 
> | The notable configuration options are
> 
> followed by a list of the options that are read and used by apt-listbugs.
> And Acquire::http::TimeOut is _not_ included in the list...

If you meant that these are the only supported options, then "notable"
is not the right word (as I understood "notable configuration
options", I thought these were the most important options in
practice, in the context of apt-listbugs).

> As far as the feature request itself is concerned, it seems to me
> that apt.conf(5) man page says:
> 
> | The option timeout sets the timeout timer used by the method; this
> | value applies to the connection as well as the data timeout.
> 
> It's not too clear to me whether the value is in seconds or in some
> other unit of measurement. Where is this documented?

I was wondering the same thing (since I had to use this option for
"apt"), and assumed that this was in seconds, as this is the standard
time unit (and the man page also mentions "seconds" for other time
options). And indeed, this corresponds to the observed behavior.

> Anyway, I'll try and take a look at some method to set the timeout
> for ruby-httpclient. Let's hope it's not too difficult to do.

That would be strange that standard modules wouldn't allow a
configurable timeout. Actually this seems possible:

  
https://stackoverflow.com/questions/20399534/whats-the-default-time-out-limitation-of-ruby-httpclient

Otherwise, wouldn't the right solution to use libapt-pkg (just
guessing), if there's a Ruby interface?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#869153: aa-exec is not longer in /usr/sbin and now apparmor is silently scraped

[Luciano Bello]

Source: tor
Version: 0.2.9.11-1~deb9u1
Severity: important
Tags: security patch

Hi Peter,
  I got this report[1]
   aa-exec is not in /usr/sbin anymore, at least not in every arch [2].

Cheers, luciano

[1]  https://twitter.com/pissquark/status/888142796414226432
[2]  
https://packages.debian.org/search?searchon=contents&keywords=bin%2Faa-exec&mode=path&suite=unstable&arch=any

Bug#865926: jsonpickle: ftbfs with python3.6, please upgrade to 0.9.4

[Michael Hudson-Doyle]

The recently released 0.9.5 does pass tests with python 3.6.

On 26 June 2017 at 10:26, Michael Hudson-Doyle 
wrote:

> Source: jsonpickle
> Version: 0.9.3-1
> Severity: normal
> User: debian-pyt...@lists.debian.org
> Usertags: python3.6
>
> Dear Maintainer,
>
> jsonpickle fails to build when Python 3.6 is a supported version, as the
> current development version of Ubuntu. The 0.9.4 upstream release builds
> fine
> though, so it would be good to update to that in preparation for the
> Python 3.6
> transition in unstable.
>
> Cheers,
> mwh
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers xenial-updates
>   APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
> 'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.4.0-81-generic (SMP w/4 CPU cores)
> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>

Bug#822436: nestopia closes when launching roms

[Aaron Valdes]

Interesting Clues

working with older version

http://archive.ubuntu.com/ubuntu/pool/universe/n/nestopia/

nestopia_1.45+dfsg-1_i386.deb  Works with this version.  
nestopia_1.46.2-1_i386.deb Gives me only a white screen.
nestopia_1.47-1_i386.deb   Crashes with the error mentioned.
nestopia_1.47-2_i386.deb   Crashes with the error mentioned.

I am testing with this older version.

nestopia_1.45+dfsg-1_i386.deb

Hope this helps track what the bug is in the newer versions.

Aaron


On Sun, 24 Apr 2016 15:08:23 +0200 diego  wrote:
> Package: nestopia
> Version: 1.47-1
> Severity: important
> 
> Dear Maintainer,
> 
> When launching a rom the program closes. I don't know how to retrieve more
> information about the bug, so if more information is needed you will have to
> say me how I should obtain it.
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages nestopia depends on:
> ii  libao4  1.1.0-3
> ii  libarchive133.1.2-11+b1
> ii  libc6   2.22-6
> ii  libepoxy0   1.3.1-1
> ii  libgcc1 1:5.3.1-14
> ii  libgdk-pixbuf2.0-0  2.34.0-1
> ii  libglib2.0-02.48.0-1
> ii  libgtk-3-0  3.18.9-1
> ii  libsdl2-2.0-0   2.0.4+dfsg1-2+b1
> ii  libstdc++6  5.3.1-14
> ii  zlib1g  1:1.2.8.dfsg-2+b1
> 
> nestopia recommends no packages.
> 
> nestopia suggests no packages.
> 
> -- no debconf information
> 
> 

Bug#869152: lv2-dev: type conflict of and

[Joël Krähemann]

Package: lv2-dev
Version: 1.14.0~dfsg1-1
Severity: important

Dear Maintainer,

As doing #include  before  I get following compiler errors:

/usr/lib/lv2/atom.lv2/forge.h:114:11: error: two or more data types in 
declaration specifiers
LV2_URID Bool;
^
/usr/lib/lv2/atom.lv2/forge.h: In function 'lv2_atom_forge_init':
/usr/lib/lv2/atom.lv2/forge.h:147:9: error: expected identifier before 'int'
forge->Bool = map->map(map->handle, LV2_ATOM__Bool);
^
/usr/lib/lv2/atom.lv2/forge.h: In function 'lv2_atom_forge_bool':
/usr/lib/lv2/atom.lv2/forge.h:408:54: error: expected identifier before 'int'
const LV2_Atom_Bool a = { { sizeof(int32_t), forge->Bool }, val ? 1 : 0 };
^

The compilation of my program aborted with the above error message. However
as swapping the include order, it compiles.

I was expecting no conflict in the header files.

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

Kernel: Linux 4.9.0-1-rt-amd64 (SMP w/24 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#867636: Bug#867634: linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components.

[Ben Hutchings]

Control: reopen -1
Control: tag -1 moreinfo

[Retrying this with the other address given]

On Fri, 2017-07-07 at 21:01 -0400, madsara wrote:
[...]
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   The following actions have been taken so far, none of which are 
> successful:
>   - Upgraded Dell R210 II's BIOS
>   - Purchased an entirely new Sandisk TowerRAID TR8M+B
>   - Replaced the eSATA card - moving from SIL chipset to Marvell
>   - Replaced all hard drives with brand new 3TB drives.

Did you try replacing the eSATA cables yet?

>   - Upgraded OS from Debian Jessie to Debian Stretch
>   - Ensured BIOS was set for maximum performance and not power saving.
>   - Added noapic, acpi=off, and apm=off kernel parameter options.

These parameters were once useful with old hardware and kernel
versions, but now will usually only make things worse.

>   - Performed a full on-board health check (part of the Dell on-board 
> management abilities), finding no issues.
>   - Performed an extensive memory test, finding no issues.

[...]

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.



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

Bug#869151: kolourpaint4: Getting 'Cannot talk to klauncher' error in Save dialog

[Stiliyan Varbanov]

Package: kolourpaint4
Version: 4:16.08.3-1
Severity: important

Dear Maintainer,

Since upgrading to Debian Stretch, the Save dialog in KolourPaint has been
broken
on my system. I receive an error saying: "Could not start process; cannot start
klauncher:
The name org.kde.klauncher5 was not provided by any .service files.".
After clicking OK, the dialog remains open, but directories and files are not
listed.

I can still save the file in the current directory or any of its parents, but
since
files can't be listed, I can only go up the directory tree.

I tried uninstalling kolourpaint4 and installing it again, but the problem
remains.

I am using LXDE and KDE is not installed, and so I think it's likely there is
at least one
package kolourpaint4 should list as a dependency, but does not, and as a result
the package(s)
was/were not installed.



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

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

Versions of packages kolourpaint4 depends on:
ii  libc6   2.24-11+deb9u1
ii  libkf5configcore5   5.28.0-2
ii  libkf5configgui55.28.0-2
ii  libkf5configwidgets55.28.0-2
ii  libkf5coreaddons5   5.28.0-2
ii  libkf5guiaddons55.28.0-1
ii  libkf5i18n5 5.28.0-2
ii  libkf5iconthemes5   5.28.0-2
ii  libkf5kdelibs4support5  5.28.0-1
ii  libkf5service-bin   5.28.0-1
ii  libkf5service5  5.28.0-1
ii  libkf5textwidgets5  5.28.0-1
ii  libkf5widgetsaddons55.28.0-3
ii  libkf5xmlgui5   5.28.0-1
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5printsupport5 5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libstdc++6  6.3.0-18

kolourpaint4 recommends no packages.

kolourpaint4 suggests no packages.

-- no debconf information

Bug#869121: ITP: dragonfire -- Dragonfire is an open source virtual assistant project for Debian based Linux distributions

[Mehmet Mert Yıldıran]

Finally, I fixed both subject and summary. Please take a look at again.

Bug#869150: /usr/bin/uscan: doesn't find the correct version for directory based version detection

[Paul Gevers]

Package: devscripts
Version: 2.17.6
Severity: normal
File: /usr/bin/uscan

Recently I started improving the packaging of the festvox packages in
the tts team. Most of my upstream sources can be found by URL's like
http://festvox.org/packed/festival/2.4/voices/festvox_kallpc16k.tar.gz

The previous time that I worked on the packages, uscan didn't support
the version to originate from the diretory tree. Luckily, it now does,
but it seems to be processing the version in a weird way. With the
attached (and uploaded) watch file for festlex-cmu, uscan reports that
there is a version 4 available, while the version it found is 2.4. Also
running "uscan -v" before the changelog was updated showed the wrong
behavior.

I don't know enough perl to know how to do it, but I think that the
expression for the version in the next line isn't greedy (I found this
on line 3293 in the version in stretch):
# uversionmanglesd version is '', make best effort to set it
$newfile_base =~
m/^.+[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
$newversion = $1;
   ^^^

paul@testavoira ~/packages/a11y/festvox-rablpc16k $ uscan -v
uscan info: uscan (version 2.17.6) See uscan(1) for help
uscan info: Scan watch files in .
uscan info: Check debian/watch and debian/changelog in .
uscan info: package="festvox-rablpc16k" version="1.4.0-3" (as seen in
debian/changelog)
uscan info: package="festvox-rablpc16k" version="1.4.0" (no epoch/revision)
uscan info: Check debian/watch and debian/changelog in ./.git/refs/tags
uscan info: Check debian/watch and debian/changelog in
./.git/dgit/unpack/festvox-rablpc16k-1.4.0
uscan info: ./debian/changelog sets package="festvox-rablpc16k"
version="1.4.0"
uscan info: Process ./debian/watch (package=festvox-rablpc16k version=1.4.0)
uscan info: opts:
filenamemangle=s#.*/festival/[-_]?(\d[\-+\.:\~\da-zA-Z]*)/voices/festvox_rablpc16k#festvox-rablpc16k_$1#
uscan info: line:
http://festvox.org/packed/festival/[-_]?(\d[\-+\.:\~\da-zA-Z]*)/voices/
festvox_rablpc16k(?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip)
uscan info: Parsing
filenamemangle=s#.*/festival/[-_]?(\d[\-+\.:\~\da-zA-Z]*)/voices/festvox_rablpc16k#festvox-rablpc16k_$1#
uscan info: line:
http://festvox.org/packed/festival/[-_]?(\d[\-+\.:\~\da-zA-Z]*)/voices/
festvox_rablpc16k(?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip)
uscan info: Last orig.tar.* tarball version (from debian/changelog): 1.4.0
uscan info: Last orig.tar.* tarball version (dversionmangled): 1.4.0
uscan info: dir=>/packed/festival/  dirpattern=>[-_]?(\d[\-+\.:\~\da-zA-Z]*)
uscan info: Requesting URL:
   http://festvox.org/packed/festival/
uscan info: Matching pattern:

(?:(?:http://festvox.org)?\/packed\/festival\/)?[-_]?(\d[\-+\.:\~\da-zA-Z]*)
uscan info: Matching target for dirversionmangle:   ?C=N;O=D
uscan info: Matching target for dirversionmangle:   ?C=M;O=A
uscan info: Matching target for dirversionmangle:   ?C=S;O=A
uscan info: Matching target for dirversionmangle:   ?C=D;O=A
uscan info: Matching target for dirversionmangle:   /packed/
uscan info: Matching target for dirversionmangle:   1.4.1/
uscan info: Matching target for dirversionmangle:   1.4.2/
uscan info: Matching target for dirversionmangle:   1.4.3/
uscan info: Matching target for dirversionmangle:   1.95/
uscan info: Matching target for dirversionmangle:   1.96/
uscan info: Matching target for dirversionmangle:   2.0.95/
uscan info: Matching target for dirversionmangle:   2.1/
uscan info: Matching target for dirversionmangle:   2.4/
uscan info: Matching target for dirversionmangle:   Linux-1.4.1/
uscan info: Matching target for dirversionmangle:   Linux-1.4.2/
uscan info: Matching target for dirversionmangle:   free-1.4.1/
uscan info: Matching target for dirversionmangle:   free-1.4.2/
uscan info: Matching target for dirversionmangle:   free-1.4.3/
uscan info: Matching target for dirversionmangle:   latest/
uscan info: Found the following matching directories (newest first):
   2.4/ (2.4)
   2.1/ (2.1)
   2.0.95/ (2.0.95)
   1.96/ (1.96)
   1.95/ (1.95)
   1.4.3/ (1.4.3)
   1.4.2/ (1.4.2)
   1.4.1/ (1.4.1)
uscan info: newest_dir => '2.4'
uscan info: Requesting URL:
   http://festvox.org/packed/festival/2.4/voices/
uscan info: Matching pattern:

(?:(?:http://festvox.org)?\/packed\/festival\/2\.4\/voices\/)?festvox_rablpc16k(?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip)
uscan info: Found the following matching hrefs on the web page (newest
first):
   festvox_rablpc16k.tar.gz () index=-1
uscan info: Matching target for downloadurlmangle:
http://festvox.org/packed/festival/2.4/voices/festvox_rablpc16k.tar.gz
uscan info: Upstream URL (downloadurlmangled):
   http://festvox.org/packed/festival/2.4/voices/festvox_rablpc16k.tar.gz
uscan info: Matching target for filenamemangle:
http://festvox.org/packed/festival/2.4/voices/festvox_rablpc16k.tar.gz
uscan info: Newest upstream tarball version from the filenamemangled
filename: 4
uscan info: Download filename (fil

Bug#869144: systemd: Setting PATH with environment.d does not work

[Michael Biebl]

Am 21.07.2017 um 01:01 schrieb Stefan Tatschner:
>> The PATH you have above is not hard-coded in systemd afaics.
>> To me this looks like PATH is set somewhere outside of systemd and then
>> pushed into the systemctl --user environment.
> 
> Any idea how I can find out which component is overwriting PATH?

Not sure. Maybe raise this question upstream.



signature.asc
Description: OpenPGP digital signature

Bug#869097: Sphinsearch crash dump

[Maxime Buquet]

Here is a new bt, I am not sure it is related, but I am now getting
these all the time after the average 2s of indexing is done in searchd.


--- crashed SphinxAPI request dump ---

--- request dump end ---
Sphinx 2.2.11-id64-release (95ae9a6)
Handling signal 11
-- backtrace begins here ---
Program compiled with x86_64-linux-gnu-gcc 6.2.1
Configured with flags:  '--prefix=/usr' '--includedir=${prefix}/include' 
'--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' 
'--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' '--libd
ir=${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--host=x86_64-linux-gnu' 
'--build=x86_64-linux-gnu' '--localstatedir=/
var/lib/sphinxsearch' '--sysconfdir=/etc/sphinxsearch' '--with-libstemmer' 
'--with-pgsql' 'build_alias=x86_64-linux-gnu' 'host_alias=x86_64-linux-gnu' 
'CFLAGS=-g -O2 -fdebug-prefix-map=/build/sphinxsearch-uQF11y/
sphinxsearch-2.2.11=. -fstack-protector-strong -Wformat -Werror=format-security 
-O2' 'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' 
'CXXFLAGS=-g -O2 -fdebug-prefix-map=/build/sphinxsearch-uQF11
y/sphinxsearch-2.2.11=. -fstack-protector-strong -Wformat 
-Werror=format-security'
Host OS is Linux x86-ubc-01 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 
(2016-10-19) x86_64 GNU/Linux
Stack bottom = 0x7ffeafbec637, thread stack size = 0x10
Trying manual backtrace:
Frame pointer is null, manual backtrace failed (did you build with 
-fomit-frame-pointer?)
Trying system backtrace:
begin of system symbols:
/usr/bin/searchd(+0x1cf939)[0x56419e43a939]
/usr/bin/searchd(+0x65097)[0x56419e2d0097]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f08f5def0c0]
/lib/x86_64-linux-gnu/libc.so.6(+0x84380)[0x7f08f5226380]
/usr/bin/searchd(+0xfb9d4)[0x56419e3669d4]
/usr/bin/searchd(+0xfc10c)[0x56419e36710c]
/usr/bin/searchd(+0x70643)[0x56419e2db643]
/usr/bin/searchd(+0x8a22c)[0x56419e2f522c]
/usr/bin/searchd(+0xb0e71)[0x56419e31be71]
/usr/bin/searchd(+0x5f9ae)[0x56419e2ca9ae]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f08f51c22b1]
/usr/bin/searchd(+0x5ff6a)[0x56419e2caf6a]
-- backtrace ends here ---
Please, create a bug report in our bug tracker (http://sphinxsearch.com/bugs) 
and attach there:
a) searchd log, b) searchd binary, c) searchd symbols.
Look into the chapter 'Reporting bugs' in the documentation
(/usr/share/doc/sphinx/sphinx.txt or 
http://sphinxsearch.com/docs/current.html#reporting-bugs)
--- BT to source lines (depth 12): ---
??:0
??:0
??:0
??:0
??:0
??:0
??:0
??:0
??:0
??:0
??:0
??:0
--- BT to source lines finished ---
--- CRASH DUMP END ---

-- 
Maxime “pep” Buquet


signature.asc
Description: PGP signature

Bug#869144: systemd: Setting PATH with environment.d does not work

[Stefan Tatschner]

> The PATH you have above is not hard-coded in systemd afaics.
> To me this looks like PATH is set somewhere outside of systemd and then
> pushed into the systemctl --user environment.

Any idea how I can find out which component is overwriting PATH?


(sry, I did not hit reply all in the first place)

Bug#869144: systemd: Setting PATH with environment.d does not work

[Michael Biebl]

Am 20.07.2017 um 23:24 schrieb Stefan Tatschner:
> Subject: systemd: Setting PATH with environment.d does not work
> Package: systemd
> Version: 234-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Setting the $PATH variable with systemd's environment.d feature does not work
> as expected. I have this content in my
> `~/.config/environment.d/99-defaults.conf`:
> 
> ```
> GOPATH=$HOME/Go
> PATH1=$GOPATH/bin:$HOME/.cargo/bin:$HOME/.local/bin:$PATH
> PATH=$GOPATH/bin:$HOME/.cargo/bin:$HOME/.local/bin:$PATH
> ```
> 
> After a login in gnome3 I expect to see `$PATH` and `$PATH1` to be equal; with
> expanded `$GOPATH` prepended.
> 
> On a shell I get this instead:
> 
> ```
> $ printenv PATH PATH1 GOPATH
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> /home/stefan/Go/bin:/home/stefan/.cargo/bin:/home/stefan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> /home/stefan/Go
> ```
> 
> ```
> $ systemctl --user show-environment
> ...
> GOPATH=/home/stefan/Go
> PATH1=/home/stefan/Go/bin:/home/stefan/.cargo/bin:/home/stefan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/u
> PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> ...
> ```
> 
> `$PATH` seems to be hardcoded somewhere which overwrites my setting; important
> fact: I use gnome on **wayland**. So I have no shellscripts that are being
> exectued during login.
> 

The PATH you have above is not hard-coded in systemd afaics.
To me this looks like PATH is set somewhere outside of systemd and then
pushed into the systemctl --user environment.



signature.asc
Description: OpenPGP digital signature

Bug#864074: defaults.vim: broken configuration

[Adam Waite]

As mentioned on other bug reports, this is an order-of-inclusion issue.

  1: /usr/share/vim/vimrc
  2: /usr/share/vim/vim80/debian.vim
  3: /etc/vim/vimrc.local
  4: /usr/share/vim/vim80/defaults.vim
  [snip]

defaults.vim is being loaded *after* vimrc.local, which means that
vimrc.local is useless for overriding the package default settings. This is
not the expected behavior.

Suggesting that each individual user on a system should supply their own
.vimrc is a ridiculous non-solution, especially since the functionality
exists to set system-wide defaults.

Prematurely closed bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837761
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837880

The solution is simple, and it is simply baffling that it has been resisted
by the package maintainers. Why should users have to completely disable the
defaults, just to disable a single problematic configuration item?

Bug#867610: python3-libvhdi: Missing python3 interpreter depends

[Hilko Bengen]

Hi Scott,

I have just uploaded a fixed package, but a question remains:

> As an added bonus, it would be nice if you could build python3-libvhdi
> for all supported python3 versions and not just the default. This
> eases python3 transitions considerably.

At some point I thought that building with all available Python versions
was no longer necessary with Python3 due to some ABI stability
guarantees...

Do I really need to rebuild the package or is there some dh_python magic
that edits the resulting pyvhdi.*.so file(s)?

Cheers,
-Hilko

Bug#869149: linux: please merge Btrfs: fix early ENOSPC due to delalloc

[Christoph Anton Mitterer]

Source: linux
Version: 4.9.30-2+deb9u2
Severity: normal


Hey Ben, et al.

There seems to be an annoying bug in btrfs, as described here:
https://www.spinics.net/lists/linux-btrfs/msg67479.html

It's not really extremely critical as it causes no direct fs corruption,
but it gives spurious ENOSPC in case of heavy metadata operation,
even though plenty of space is left.

It affects stretch kernels as well as the current 4.12.


It can e.g. easily be hit, when copying a root-fs, as described in the
thread above.

There's a fix, which seems to work:
https://patchwork.kernel.org/patch/9829593/

Omar will mark it for linux-stable, I'm just reporting it here as well
to make sure that it doesn't get lost :-)


Best wishes,
Chris

Bug#869148: digikam cannot import photos from iphone

[Herminio Hernandez Jr]

Package: digikam
Version: 4:5.3.0-1
Severity: normal

Dear Maintainer,

I am trying to import my photos from my iphone to my desktop. I plug the
iphone into the USB port and I see KDE recognizing and asking if I want
digikam in import. I click on the digikam icon and it the app launches.
After launch I recieve an error say the device is not recognized. I will
be attaching a screenshot of the error.

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

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

Versions of packages digikam depends on:
ii  digikam-data  4:5.3.0-1
ii  digikam-private-libs  4:5.3.0-1
ii  kipi-plugins  4:5.3.0-1
ii  libc6 2.24-12
ii  libgcc1   1:7.1.0-9
ii  libkf5configcore5 5.28.0-2
ii  libkf5coreaddons5 5.28.0-2
ii  libkf5filemetadata3   5.28.0-1+b2
ii  libkf5i18n5   5.28.0-2
ii  libqt5core5a  5.7.1+dfsg-4
ii  libqt5gui55.7.1+dfsg-4
ii  libqt5sql55.7.1+dfsg-4
ii  libqt5sql5-mysql  5.7.1+dfsg-4
ii  libqt5sql5-sqlite 5.7.1+dfsg-4
ii  libqt5widgets55.7.1+dfsg-4
ii  libstdc++67.1.0-9
ii  perl  5.24.1-7

Versions of packages digikam recommends:
ii  ffmpegthumbs4:16.08.3-1
ii  firefox-esr [www-browser]   52.2.0esr-2
ii  google-chrome-stable [www-browser]  59.0.3071.115-1
ii  konqueror [www-browser] 4:16.08.3-1
ii  qupzilla [www-browser]  1.8.9~dfsg1-3.1

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:5.8.7-1

-- no debconf information

Bug#867643: downgrading

[Holger Levsen]

control: severity -1 important

this bug has been tagged unreproducible, thus downgrading severity to prevent
autoremoval from Buster…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#867031: downgrading

[Holger Levsen]

control: severity -1 important

upstream knows of 3-4 installations of schleuder on wheezy using Debian 
packages,
thus downgrading the severity, this is a rather academic test case ;-)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#869147: Dovecot authentication not working due to double free

[Alex]

Package: libpam-yubico
Version: 2.23-1
Severity: important
Tags: upstream

I have confiugured Yubikey PAM authentication. It works for SSH and sudo, but 
it fails for dovecot, as shown in syslog:

dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(759)] called.
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(760)] flags 0 argc 5
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(762)] 
argv[0]=mode=client
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(762)] 
argv[1]=try_first_pass
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(762)] 
argv[2]=id=[REDACTED]
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(762)] argv[3]=debug
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(762)] 
argv[4]=key=[REDACTED]
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(763)] id=[REDACTED]
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(764)] key=[REDACTED]
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(765)] debug=1
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(766)] alwaysok=0
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(767)] verbose_otp=0
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(768)] try_first_pass=1
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(769)] use_first_pass=0
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(770)] authfile=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(771)] ldapserver=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(772)] ldap_uri=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(773)] 
ldap_bind_user=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(774)] 
ldap_bind_password=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(775)] ldap_filter=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(776)] 
ldap_cacertfile=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(777)] ldapdn=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(778)] user_attr=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(779)] yubi_attr=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(780)] 
yubi_attr_prefix=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(781)] url=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(782)] urllist=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(783)] capath=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(784)] cainfo=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(785)] proxy=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(786)] token_id_length=12
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(787)] mode=client
dovecot: auth-worker: Error: [../pam_yubico.c:parse_cfg(788)] 
chalresp_path=(null)
dovecot: auth-worker: Error: [../pam_yubico.c:pam_sm_authenticate(834)] get 
user returned: [REDACTED]
dovecot: auth-worker: Error: [../pam_yubico.c:pam_sm_authenticate(855)] get 
password returned: (null)
dovecot: auth-worker: Error: [../pam_yubico.c:pam_sm_authenticate(985)] conv 
returned 53 bytes
dovecot: auth-worker: Error: [../pam_yubico.c:pam_sm_authenticate(1003)] 
Skipping first 9 bytes. Length is 53, token_id set to 12 and token OTP always 
32.
dovecot: auth-worker: Error: [../pam_yubico.c:pam_sm_authenticate(1010)] OTP: 
[REDACTED] ID: [REDACTED]
dovecot: auth-worker: Error: [../pam_yubico.c:pam_sm_authenticate(1025)] 
Extracted a probable system password entered before the OTP - setting item 
PAM_AUTHTOK
dovecot: auth-worker: Error: *** Error in `dovecot/auth`: double free or 
corruption (!prev): 0x7f389ba54e40 ***
dovecot: auth: Error: auth worker: Aborted PASSV request for [REDACTED]: Worker 
process died unexpectedly
dovecot: auth-worker: Fatal: master: service(auth-worker): child 1281 killed 
with signal 6 (core dumps disabled)
-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-042stab120.11 (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-yubico depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u1
ii  libldap-2.4-2  2.4.44+dfsg-5
ii  libpam-runtime 1.1.8-3.6
ii  libpam0g   1.1.8-3.6
ii  libykclient3   2.15-1
ii  libykpers-1-1  1.17.3-1
ii  libyubikey01.13-2

libpam-yubico recommends no packages.

libpam-yubico suggests no packages.

-- debconf information:
* libpam-yubico/module_args: mode=client try_first_pass id=[REDACTED] 
key=[REDACTED]

Bug#869146: dgit: should never add .orig to the .changes more than once

[Sean Whitton]

Package: dgit
Version: 3.10
Severity: minor

Hello,

Today I did:

% dgit push --new

followed by:

% dgit push --new --deliberately-include-questionable-history

Each of these commands added the .orig to the .changes file, so I got a
non-fatal error from dput that ftp-master wouldn't let it overwrite the
first file that was uploaded.

This could be confusing.

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

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

Versions of packages dgit depends on:
ii  apt   1.4.6
ii  ca-certificates   20161130+nmu1
ii  coreutils 8.26-3
ii  curl  7.52.1-5
ii  devscripts2.17.6
ii  dpkg-dev  1.18.24
ii  dput-ng [dput]1.13
ii  git [git-core]1:2.11.0-3
ii  git-buildpackage  0.8.12.2
ii  libdpkg-perl  1.18.24
ii  libjson-perl  2.90-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-glob-perl 0.10-1
ii  libtext-iconv-perl1.7-5+b4
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10

Versions of packages dgit suggests:
ii  sbuild  0.73.0-4

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#869140: casync FTBFS on mips64el: test-casync TIMEOUT

[Adrian Bunk]

On Thu, Jul 20, 2017 at 04:58:22PM -0400, Felipe Sateler wrote:
> Control: forwarded -1 https://github.com/systemd/casync/issues/61
> 
> On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk  wrote:
> > Source: casync
> > Version: 1+65-1
> > Severity: important
> >
> > https://buildd.debian.org/status/fetch.php?pkg=casync&arch=mips64el&ver=1%2B65-1&stamp=1500580132&raw=0
> >
> > ...
> >dh_auto_test -a
> > ninja test
> > [0/1] Running all tests.
> >  1/14 test-script.sh  OK  633.39 s
> >  2/14 test-script-sha256.sh   OK  636.46 s
> >  3/14 test-nbd.sh OK  177.02 s
> >  4/14 test-fuse.shOK  305.71 s
> >  5/14 test-cachunkOK   6.05 s
> >  6/14 test-cachunker  OK   2.25 s
> >  7/14 test-cachunker-histogramOK   2.57 s
> >  8/14 test-cadigest   OK  10.35 s
> >  9/14 test-caencoder  OK   0.62 s
> > 10/14 test-camakebst  OK  19.00 s
> > 11/14 test-caorigin   OK   0.12 s
> > 12/14 test-casync TIMEOUT 120.20 s
> > 13/14 test-cautil OK   0.11 s
> > 14/14 test-util   OK   0.11 s
> >
> > OK:13
> > FAIL:   1
> > SKIP:   0
> > TIMEOUT:1
> >
> >
> > The output from the failed tests:
> >
> > 12/14 test-casync TIMEOUT 120.20 s
> >
> > --- command ---
> > /<>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
> > ---
> >
> > Full log written to 
> > /<>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
> > FAILED: test
> > /usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild 
> > --print-errorlogs
> > ninja: build stopped: subcommand failed.
> > dh_auto_test: ninja test returned exit code 1
> > debian/rules:8: recipe for target 'build-arch' failed
> > make: *** [build-arch] Error 1
> >
> >
> >
> > On mipsel this test succeeded after 108.83 seconds, so this might
> > just require an increased timeout (untested).
> 
> This test runs faster than test-camakebst on my amd64 machine, so
> there may be a real issue.

On all architectures where the build succeeded on the buildds 
test-casync took 2-5 times as much time as test-camakebst.

On i386 3.5 times as much.

On my amd64 machine casync takes 4 times as long as camakebst.

> Saludos,
> Felipe Sateler

cu
Adrian

-- 

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

Bug#854414: screen uses "screen.xterm-256color" without screen I get "xterm-256color" which works

[Axel Beckert]

Hi Martin,

Martin Steigerwald wrote:
> > +   To avoid this error message, the best way is to start a new screen
> > +   session under a different circumstances, but there are also ways
> 
> => "under different circumstances"

Good catch!

> I am not sure whether I´d understand this as "under different circumstances" 
> is quite unspecific.

Hrm. It's very general on purpose as the different circumstances are
listed only afterwards.

> I´d think I´d rather write "with different terminal 
> configuration"

I think I had "a different environent" in mind when I wrote that "a".

I went with ""with different terminal settings" for now the "terminal
configuration" feels misleading to me.

> Whoa, I wondered whether to give this many options, but… I think its okay :) 
> as you added the options that IMHO works best at the beginning of the lists.

I prefer choice. :-)

> You might want to add a link to the bug report in README.Debian.

Thanks! That's a good idea! Done and pushed to the git repository.

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

Bug#869145: haskell-servant-server FTBFS: Couldn't match expected type `MatchBody' with actual type `Maybe BCL.ByteString'

[Adrian Bunk]

Source: haskell-servant-server
Version: 0.9.1.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-servant-server&suite=sid

...
[ 8 of 10] Compiling Servant.Server.ErrorSpec ( 
test/Servant/Server/ErrorSpec.hs, 
dist-ghc/build/spec/spec-tmp/Servant/Server/ErrorSpec.o )

test/Servant/Server/ErrorSpec.hs:214:44: error:
* Couldn't match expected type `MatchBody'
  with actual type `Maybe BCL.ByteString'
* In the `matchBody' field of a record
  In the second argument of `shouldRespondWith', namely
`200 {matchBody = Just $ encode (8 :: Int)}'
  In a stmt of a 'do' block:
request methodPost "" [jsonCT, jsonAccept] jsonBody
`shouldRespondWith` 200 {matchBody = Just $ encode (8 :: Int)}

test/Servant/Server/ErrorSpec.hs:218:44: error:
* Couldn't match expected type `MatchBody'
  with actual type `Maybe BCL.ByteString'
* In the `matchBody' field of a record
  In the second argument of `shouldRespondWith', namely
`200 {matchBody = Just $ encode (4 :: Int)}'
  In a stmt of a 'do' block:
request methodGet "a" [jsonCT, jsonAccept] jsonBody
`shouldRespondWith` 200 {matchBody = Just $ encode (4 :: Int)}
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1

Bug#869070: apt-listbugs does not honor Acquire::http::TimeOut

[Francesco Poli]

Control: severity -1 wishlist


On Thu, 20 Jul 2017 10:43:22 +0200 Vincent Lefevre wrote:

> Package: apt-listbugs
> Version: 0.1.23
> Severity: important

Hello Vincent,
thanks for your bug report.

> 
> apt-listbugs does not honor Acquire::http::TimeOut, while its man page
> says:
> 
> CONFIGURATION FILE
>   apt-listbugs understands APT configuration file (see apt.conf(5) for
>   more details). [...]

While it's true that the man page states what you quoted, it also goes
on stating:

| The notable configuration options are

followed by a list of the options that are read and used by apt-listbugs.
And Acquire::http::TimeOut is _not_ included in the list...

As a consequence, yours is actually a feature request.
I am setting the severity accordingly.

As far as the feature request itself is concerned, it seems to me
that apt.conf(5) man page says:

| The option timeout sets the timeout timer used by the method; this
| value applies to the connection as well as the data timeout.

It's not too clear to me whether the value is in seconds or in some
other unit of measurement. Where is this documented?

Anyway, I'll try and take a look at some method to set the timeout
for ruby-httpclient. Let's hope it's not too difficult to do.
Unfortunately, I won't be able to act soon: I am afraid you'll have
to wait some time...

Bye.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpvjum15e6vY.pgp
Description: PGP signature

Bug#861541: jessie-pu: package kedpm/1.0

[Antoine Beaupré]

On 2017-06-27 22:39:23, Cyril Brulebois wrote:
> Control: tag -1 confirmed
>
> Antoine Beaupre  (2017-04-30):
>> diff -Nru kedpm-1.0/debian/changelog kedpm-1.0+deb8u1/debian/changelog
>> --- kedpm-1.0/debian/changelog   2012-11-30 15:45:14.0 -0500
>> +++ kedpm-1.0+deb8u1/debian/changelog2017-04-26 20:44:11.0 
>> -0400
>> @@ -1,3 +1,10 @@
>> +kedpm (1.0+deb8u1) jessie; urgency=high
>> +
>> +  * Non-maintainer upload by the Security Team.
>> +  * fix information leak via command history file (Closes: #860817)
>> +
>> + -- Antoine Beaupré   Wed, 26 Apr 2017 20:44:11 -0400
>> +
>>  kedpm (1.0) unstable; urgency=low
>>  
>>* New upstream release.
>> diff -Nru 
>> kedpm-1.0/debian/patches/0001-always-prompt-for-password-and-do-not-save-to-databa.patch
>>  
>> kedpm-1.0+deb8u1/debian/patches/0001-always-prompt-for-password-and-do-not-save-to-databa.patch
>> --- 
>> kedpm-1.0/debian/patches/0001-always-prompt-for-password-and-do-not-save-to-databa.patch
>>  1969-12-31 19:00:00.0 -0500
>> +++ 
>> kedpm-1.0+deb8u1/debian/patches/0001-always-prompt-for-password-and-do-not-save-to-databa.patch
>>   2017-04-26 20:43:55.0 -0400
>> @@ -0,0 +1,61 @@
>> +From b8f7e8b3b2cb37425cb89b205c9836c6ac02a048 Mon Sep 17 00:00:00 2001
>> +From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
>> +Date: Wed, 26 Apr 2017 16:58:56 -0400
>> +Subject: [PATCH 1/2] always prompt for password and do not save to database
>
> The 1/2 part seems a bit weird here; was the second patch relevant for
> this security fix?

No, it wasn't.

>> +-"""Change master password for opened database
>> +-
>> +-Syntax:
>> +-password [new password]
>> +-
>> +-If new password is not provided with command, you will be promted to enter 
>> new
>> +-one.
>> +-"""
>> +-
>> +-if not arg:
>> +-# Password is not provided with command. Ask user for it
>> +-pass1 = getpass(_("New password: "))
>> +-pass2 = getpass(_("Repeat password: "))
>> +-if pass1 == '':
>> +-print _("Empty passwords are really insecure. You should " 
>> \
>> +-"create one.")
>> +-return
>> +-if pass1!=pass2:
>> +-print _("Passwords don't match! Please repeat.")
>> +-return
>> +-new_pass = pass1
>> +-else:
>> +-new_pass = arg
>> ++"""Change master password for opened database"""
>> ++
>> ++# remove possibly master password from history file
>> ++
>> readline.remove_history_item(readline.get_current_history_length()-1)
>
> I'm assuming the history was already updated to include the last/current
> command?

Yes: the command handling framework automatically records the current
command in the history.

>> ++# Password is not provided with command. Ask user for it
>
> I suppose this became a bit of a lie. :) Feel free to replace it with
> “Always ask the user for the password”, or remove it entirely.
>
> With or without the comment fix, feel free to upload.

Thanks.

A.

-- 
We are discreet sheep; we wait to see how the drove is going, and then go
with the drove.
- Mark Twain

Bug#861541: jessie-pu: package kedpm/1.0

[Antoine Beaupré]

On 2017-06-27 21:45:17, Adam D. Barratt wrote:
> On Tue, 2017-06-27 at 22:39 +0200, Cyril Brulebois wrote:
>> Control: tag -1 confirmed
>> 
>> Antoine Beaupre  (2017-04-30):
>> > diff -Nru kedpm-1.0/debian/changelog kedpm-1.0+deb8u1/debian/changelog
>> > --- kedpm-1.0/debian/changelog 2012-11-30 15:45:14.0 -0500
>> > +++ kedpm-1.0+deb8u1/debian/changelog  2017-04-26 20:44:11.0 
>> > -0400
>> > @@ -1,3 +1,10 @@
>> > +kedpm (1.0+deb8u1) jessie; urgency=high
>> > +
>> > +  * Non-maintainer upload by the Security Team.
>
> On a side note, the above appears to be incorrect.

Bad habit, will fix.

A.

-- 
There has been only one Christian.
They caught him and crucified him -- early.
- Mark Twain

Bug#868462: lintian: obsolete-url-in-packaging doesn't check the Homepage: field

[Dylan Aïssi]

Hi,

The Homepage field is checked here:
 debian/control http://code.google.com/p/autokey/


Best regards,
Dylan

Bug#747469: openssl s_client -starttls hangs on XMPP s2s connections

[Richard Levitte]

Hi,

I was made aware of this issue through github:
https://github.com/openssl/openssl/issues/3980

I believe the following patch (commit
56d909863dcff26e82ebb06d185668f00287f67b) fixes this issue:

diff --git a/apps/s_client.c b/apps/s_client.c
index 85c1b6b579..dc467994f8 100644
--- a/apps/s_client.c
+++ b/apps/s_client.c
@@ -1667,6 +1667,8 @@ int MAIN(int argc, char **argv)
 if (strstr(mbuf, "/stream:features>"))
 goto shut;
 seen = BIO_read(sbio, mbuf, BUFSIZZ);
+if (seen <= 0)
+goto shut;
 mbuf[seen] = 0;
 }
 BIO_printf(sbio,

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/

Bug#822436: nestopia closes when launching roms

[Aaron Valdes]

Thanks for the response.

Am I missing a package?

glxinfo reports the following.

glxinfo | grep Open
Vendor: Intel Open Source Technology Center (0x8086)
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 13.0.6
OpenGL extensions:

lspci reports

lspci
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to 
I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics 
Device (rev 02)
00:1d.0 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #3 (rev 01)
00:1d.7 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI 
Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge 
(rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 
01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 
Modem Controller (rev 01)
01:01.0 CardBus bridge: Texas Instruments PCI4510 PC card Cardbus Controller 
(rev 02)
01:01.1 FireWire (IEEE 1394): Texas Instruments PCI4510 IEEE-1394 Controller
01:03.0 Network controller: Broadcom Limited BCM4309 802.11abg Wireless Network 
Controller (rev 03)
01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) 
Ethernet Controller (rev 81)

lshw for Video Driver

  *-display:0
 description: VGA compatible controller
 product: 82852/855GM Integrated Graphics Device
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 32 bits
 clock: 33MHz
 capabilities: pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:11 memory:f000-f7ff 
memory:faf8-faff ioport:c000(size=8) memory:c-d




On Thu, 20 Jul 2017 22:50:31 +0200 Stephen Kitt  wrote:
> Hi Aaron,
> 
> On Thu, 20 Jul 2017 15:05:56 -0400, Aaron Valdes 
> wrote:
> > I get something similar.
> 
> Given the lack of details in the original bug, it’s impossible to determine
> whether yours is the same or not. However ...
> 
> > daylan@RogueOne:~/Games/Nestopia$ nestopia 
> > 0 joystick(s) found:
> > Could not create glcontext: Could not create GL context: GLXBadFBConfig
> > OpenGL: (null)
> > Database: 2901 items imported from internal DB
> > /home/daylan/.nestopia/disksys.rom not found, Disk System games will not
> > work. Ines: warning, unknown or invalid header data!
> > Ines: 128k PRG-ROM set
> > Ines: 128k CHR-ROM set
> > Ines: 840k W-RAM set
> > Ines: vertical mirroring set
> > Ines: NTSC set
> > Ines: mapper 1 set
> > Board: SKROM
> > Board: 128k PRG-ROM
> > Board: 128k CHR-ROM
> > Board: 8k auto W-RAM
> > Board: MMC rev. B2
> > Region: NTSC
> > nestopia: Couldn't find current GLX or EGL context.
> 
> This indicates that you don’t have OpenGL available; Nestopia needs OpenGL to
> work.
> 
> Regards,
> 
> Stephen

Bug#863089: [Piuparts-devel] Bug#863089: Bug#863089: Please provide post-processed logs output for manpages.d.o

[Holger Levsen]

Hi Michael, 

sorry for the delay here…

On Thu, Jun 01, 2017 at 09:30:50PM +0200, Michael Stapelberg wrote:
> Alright, then. Find attached a patch against the piuparts git to add
> debiman-piuparts-distill. You can build it by running “go build” in the
> debiman-piuparts-distill subdirectory.

cool!

can you please also a.) patch the Makefile, update-piuparts-master-setup and
debian/piuparts-master.install in a meaningful way and b.) push this to your
piuparts.git repo?

Thanks already!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#869143: [udevil] Unnecessary recommends reduces system security (particularly pmount)

[OmegaPhil]

Package: udevil
Version: 0.4.4-1+b1
Severity: normal

udevil is a standalone secure mounting tool (and the packaged devmon
tool will use udevil if it is present) - however this package recommends
udisks2 and pmount, causing them to be installed on the system by
default. This defeats the purpose of udevil, since they can be used to
mount things outside of udevil's security model, and with the associated
security bugs etc that the simple udevil tool was made to avoid.

I have been pinged by the udevil programmer over this, hence the random
bug here - the 'official' upstream control has no recommends for this
reason:

https://github.com/IgnorantGuru/udevil/blob/next/distros/debian/control

Please can the 'recommends' packages be removed?


--- System information. ---
Architecture: Kernel:   Linux 4.9.0-3-amd64

Debian Release: stretch/sid
  990 testing 10.1.0.3   500 unstable10.1.0.3   500
quodlibet-unstable lazka.github.io   100 ascii-proposed  10.1.0.3
--- Package information. ---
Depends(Version) | Installed
-+-
libc6  (>= 2.14) | libglib2.0-0 (>= 2.16.0) | libudev1
 (>= 183) |

Recommends  (Version) | Installed
=-+-===
udisks2   | 2.1.8-1+devuan2
zenity| 3.22.0-1+b1
pmount| 0.9.23-3+b2


Suggests(Version) | Installed
=-+-===
eject | 2.1.5+deb1+cvs20081104-13.2
cifs-utils| curlftpfs | 0.9.2-9+b1
sshfs | 2.8-1







signature.asc
Description: OpenPGP digital signature

Bug#869144: systemd: Setting PATH with environment.d does not work

[Stefan Tatschner]

Subject: systemd: Setting PATH with environment.d does not work
Package: systemd
Version: 234-1
Severity: normal

Dear Maintainer,

Setting the $PATH variable with systemd's environment.d feature does not work
as expected. I have this content in my
`~/.config/environment.d/99-defaults.conf`:

```
GOPATH=$HOME/Go
PATH1=$GOPATH/bin:$HOME/.cargo/bin:$HOME/.local/bin:$PATH
PATH=$GOPATH/bin:$HOME/.cargo/bin:$HOME/.local/bin:$PATH
```

After a login in gnome3 I expect to see `$PATH` and `$PATH1` to be equal; with
expanded `$GOPATH` prepended.

On a shell I get this instead:

```
$ printenv PATH PATH1 GOPATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
/home/stefan/Go/bin:/home/stefan/.cargo/bin:/home/stefan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
/home/stefan/Go
```

```
$ systemctl --user show-environment
...
GOPATH=/home/stefan/Go
PATH1=/home/stefan/Go/bin:/home/stefan/.cargo/bin:/home/stefan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/u
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
...
```

`$PATH` seems to be hardcoded somewhere which overwrites my setting; important
fact: I use gnome on **wayland**. So I have no shellscripts that are being
exectued during login.

-- Package-specific info:

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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.115
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.0-6
ii  libaudit1   1:2.7.7-1+b1
ii  libblkid1   2.29.2-2
ii  libc6   2.24-12
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-4
ii  libgcrypt20 1.7.8-2
ii  libgpg-error0   1.27-3
ii  libidn111.33-1
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-2
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3+b2
ii  libsystemd0 234-1
ii  mount   2.29.2-2
ii  procps  2:3.3.12-3
ii  util-linux  2.29.2-2

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

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

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 234-1

-- Configuration Files:
/etc/systemd/resolved.conf changed [not included]

-- no debconf information

Bug#846982: override: downgrade priority of all libraries to optional (was: override: libudev1:libs/optional)

[Felipe Sateler]

Control: retitle -1 override: downgrade priority of all libraries to optional

On Sun, 04 Dec 2016 20:52:14 +0100 Michael Biebl  wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Hi,
>
> please demote the priority of libudev1 from important to optional.
>
> Having library packages being pulled in as a result of their priority is
> actively harmful. See #845464 as a current example.
>
> The priority of libudev1 was taken over from the original udev source
> package, but I'm convinced we should fix that.
>
> #758234 has some more background.

This bug is pending, and the appropriate change has been committed[1].
I think the priorities of all libraries should be downgraded to
optional

% grep-dctrl -n -sPackage -FPriority required \
  -a -FSection 'libs'  \
  /var/lib/apt/lists/deb.debian.org_debian_dists_sid_main_binary-amd64_Packages
libacl1
libattr1
e2fslibs
libcomerr2
libss2
gcc-5-base
gcc-6-base
gcc-7-base
libgcc1
libc-bin
libc6
multiarch-support
libselinux1
libsepol1
libtinfo5
libpam0g
libpcre3
libblkid1
libfdisk1
libmount1
libsmartcols1
libuuid1
liblzma5
zlib1g

% grep-dctrl -n -sPackage -FPriority important \
   -a -FSection 'libs' \
   /var/lib/apt/lists/deb.debian.org_debian_dists_sid_main_binary-amd64_Packages
libapt-inst2.0
libapt-pkg5.0
libbz2-1.0
libstdc++6
libgdbm3
libkmod2
libestr0
liblogging-stdlog0
libpipeline1
libncursesw5
libnewt0.52
libssl1.1
libssl1.0.2
libpopt0
libprocps6
libreadline7
libreadline6
libslang2
libudev1
libxapian30


It wold be nice to finally get gcc-5 out of minbase :)

[1] 
https://anonscm.debian.org/cgit/dbnpolicy/policy.git/commit/?id=4b3e61ac3fa06d8b82433e09a76f42a4f8859306

Bug#869142: ceph: /etc/init.d/ceph creates /var/run/ceph with wrong permissions

[Birger Brunswiek]

Package: ceph
Version: 10.2.5-7.2
Severity: important
Tags: patch

Dear Maintainer,


   * What led up to the situation?
   Reboot. I expected all ceph daemons to start automatically but they
   did not. /var/run/ceph had incorrect ownership. It belonged to root
   instead of ceph. I am using sysvinit. I have not checked whether
   this is also a problem using other "init".

   I appled the patch below, after which all daemons were started as
   expected.

   The removal of the mkdir is safe as the directory is created using
   install further down in the script using the correct ownership.

--- /tmp/ceph   2017-07-20 23:00:23.924080968 +0200
+++ /etc/init.d/ceph2017-07-15 01:21:30.116388768 +0200
@@ -275,7 +275,6 @@

 if [ "$command" = "start" ]; then
if [ -n "$pid_file" ]; then
-   do_cmd "mkdir -p "`dirname $pid_file`
cmd="$cmd --pid-file $pid_file"
fi
 
-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.31-moby (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages ceph depends on:
pn  ceph-mon  
pn  ceph-osd  
ii  lsb-base  9.20161125

ceph recommends no packages.

Versions of packages ceph suggests:
pn  ceph-mds  

Bug#869135: Please consider switching to giza

[gregor herrmann]

On Thu, 20 Jul 2017 21:10:29 +0200, Ole Streicher wrote:

> since about a year, there is a replacement library for pgplot available
> in Debian: giza [1]. This is almost compatible, but has a DFSG conform
> license (GPL-2+), which would allow to migrate libpgplot-perl to the
> main section. I already use it successfully in a number of packages in
> the astronomy context, f.e. in dpuser which allows an interactive
> transparent access to pgplot functions from a command line.

Good news, thank you.
 
> Would you consider testing the adoption of giza for libpgplot-perl?

I've tried now, with mixed results:

- Build-Depend on giza-dev instead of pgplot5 -> the package builds
  and the dependencies look reasonable.
- When I enable the tests, I get:
  + success in autopkgtest
  + a segfault in perl during the build:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strcat_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:313
313 ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S: No such file or 
directory.
(gdb) bt full
#0  __strcat_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:313
No locals.
#1  0x7f66f422bf45 in ?? ()
No symbol table info available.
#2  0x59711419 in ?? ()
No symbol table info available.
#3  0x5603c8025c22 in Perl_safesysmalloc (size=) at 
util.c:153
ptr = 
#4  0x5603c86c45b8 in ?? ()
No symbol table info available.
#5  0x0100 in ?? ()
No symbol table info available.
#6  0x5603c860c010 in ?? ()
No symbol table info available.
#7  0x0100 in ?? ()
No symbol table info available.
#8  0x in ?? ()
No symbol table info available.


So I have a hunch that something is not quite right ...
The test suite was disabled before because of X and stdin; but as it
does run and it passes under autopkgtest and it shouldn't segfault
even when there are problems, this doesn't look good.

But I'm afraid this needs someone more debugging-savvy than me.

Pushed to git.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones


signature.asc
Description: Digital Signature

Bug#869135: Pending fixes for bugs in the libpgplot-perl package

[pkg-perl-maintainers]

tag 869135 + pending
thanks

Some bugs in the libpgplot-perl package are closed in revision
f4a28f40e1e9ddec3774bca189207ed5f5d28d74 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libpgplot-perl.git/commit/?id=f4a28f4

Commit message:

Build-Depend on giza-dev instead of pgplot5.

Closes: #869135

Bug#869141: grub-install: error: cannot find a device ... when chrooted in a btrfs subvol

[Christoph Anton Mitterer]

Package: grub-pc
Version: 2.02-2
Severity: normal


Hi.

I've noticed the following:

When I have a btrfs fs, which is e.g. mounted and /mnt/ and a subvol at 
/mnt/root ...
and that subvol contains a Debian image...
Then one typically does something like:
 cd /mnt/root/
 mount --bind /dev/ dev/
 mount --bind /proc/ proc/
 mount --bind /sys/ sys/
 chroot .
 
 grub-install --no-floppy --recheck /dev/sdX

in order to make the device bootable.

This however fails with:
 Installing for i386-pc platform.
 grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).

The problem seems to be that one is located in the subvolume.

E.g. when unmounting all the above, and repeating it with the subvolume mounted
at /mnt, i.e.
 mount -o subvol=/root /dev/sdX1 /mnt/
 …

the process works.

Perhaps it can be made working out of the box for all cases :-)


Cheers,
Chris.

Bug#837351: tar: FTBFS on kfreebsd: --numeric-owner basic tests FAILED

[James Clarke]

On Tue, Sep 13, 2016 at 10:20:54AM +0200, Andreas Beckmann wrote:
> On 2016-09-13 08:32, Pavel Raiskup wrote:
> > On Saturday, September 10, 2016 10:43:59 PM CEST Bdale Garbee wrote:
> >> Andreas Beckmann  writes:
> >>
> >>>  30: --numeric-owner basic tests FAILED  
> >>> (numeric.at:29)
> >>
> >> I'm unlikely to find time to investigate this soon.  Help figuring out
> >> what's going wrong and how to fix it would be appreciated.
> >
> > Relevant part of test-suite log?
>
> Unfortunately I cannot reproduce the failure on the kfreebsd
> porterboxes, so I requested a give-back to retry the build.
>
> Bdale, perhaps you could use
>
>   $(MAKE) check || { cat tests/testsuite.log; false; }
>
> to dump the testsuite log upon failure.

Hi Bdale,
Ping; this is still an issue (I couldn't reproduce on falla either so
requested a give-back which failed before seeing this bug). An
alternative to that is to use TESTSUITEFLAGS:

> $(MAKE) check TESTSUITEFLAGS=-v

This is extremely verbose, but logs are only really interesting when
something needs debugging, so I don't see that as an issue myself
(though you may disagree). Do you think you'd be able to prepare an
upload with this, please (experimental is fine if you want to leave
unstable alone)?

Regards,
James

Bug#869140: casync FTBFS on mips64el: test-casync TIMEOUT

[Felipe Sateler]

Control: forwarded -1 https://github.com/systemd/casync/issues/61

On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk  wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
>
> https://buildd.debian.org/status/fetch.php?pkg=casync&arch=mips64el&ver=1%2B65-1&stamp=1500580132&raw=0
>
> ...
>dh_auto_test -a
> ninja test
> [0/1] Running all tests.
>  1/14 test-script.sh  OK  633.39 s
>  2/14 test-script-sha256.sh   OK  636.46 s
>  3/14 test-nbd.sh OK  177.02 s
>  4/14 test-fuse.shOK  305.71 s
>  5/14 test-cachunkOK   6.05 s
>  6/14 test-cachunker  OK   2.25 s
>  7/14 test-cachunker-histogramOK   2.57 s
>  8/14 test-cadigest   OK  10.35 s
>  9/14 test-caencoder  OK   0.62 s
> 10/14 test-camakebst  OK  19.00 s
> 11/14 test-caorigin   OK   0.12 s
> 12/14 test-casync TIMEOUT 120.20 s
> 13/14 test-cautil OK   0.11 s
> 14/14 test-util   OK   0.11 s
>
> OK:13
> FAIL:   1
> SKIP:   0
> TIMEOUT:1
>
>
> The output from the failed tests:
>
> 12/14 test-casync TIMEOUT 120.20 s
>
> --- command ---
> /<>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
> ---
>
> Full log written to 
> /<>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
> FAILED: test
> /usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> dh_auto_test: ninja test returned exit code 1
> debian/rules:8: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 1
>
>
>
> On mipsel this test succeeded after 108.83 seconds, so this might
> just require an increased timeout (untested).

This test runs faster than test-camakebst on my amd64 machine, so
there may be a real issue.

-- 

Saludos,
Felipe Sateler

Bug#822436: nestopia closes when launching roms

[Stephen Kitt]

Hi Aaron,

On Thu, 20 Jul 2017 15:05:56 -0400, Aaron Valdes 
wrote:
> I get something similar.

Given the lack of details in the original bug, it’s impossible to determine
whether yours is the same or not. However ...

> daylan@RogueOne:~/Games/Nestopia$ nestopia 
> 0 joystick(s) found:
> Could not create glcontext: Could not create GL context: GLXBadFBConfig
> OpenGL: (null)
> Database: 2901 items imported from internal DB
> /home/daylan/.nestopia/disksys.rom not found, Disk System games will not
> work. Ines: warning, unknown or invalid header data!
> Ines: 128k PRG-ROM set
> Ines: 128k CHR-ROM set
> Ines: 840k W-RAM set
> Ines: vertical mirroring set
> Ines: NTSC set
> Ines: mapper 1 set
> Board: SKROM
> Board: 128k PRG-ROM
> Board: 128k CHR-ROM
> Board: 8k auto W-RAM
> Board: MMC rev. B2
> Region: NTSC
> nestopia: Couldn't find current GLX or EGL context.

This indicates that you don’t have OpenGL available; Nestopia needs OpenGL to
work.

Regards,

Stephen


pgpUA1wf53zYC.pgp
Description: OpenPGP digital signature

Bug#866389: transition: perl 5.26

[Niko Tyni]

Control: block -1 with 869139

On Thu, Jul 20, 2017 at 09:16:41PM +0200, Emilio Pozuelo Monfort wrote:
> On 20/07/17 21:01, Niko Tyni wrote:
> > On Thu, Jun 29, 2017 at 07:51:33PM +0200, Emilio Pozuelo Monfort wrote:
> >> Control: forwarded -1 
> >> https://release.debian.org/transitions/html/perl5.26.html

> > Please let us know when it would be OK to upload Perl 5.26 to sid.
> 
> Awesome. Now is a good time. I have added some hints for the gsoap and
> libprelude transitions, so they don't get entangled with this one.

Thanks. I have an upload (almost) ready, but a last minute issue popped
up as the fixed syslog-ng-incubator fails to build on s390x. See #869139.

Do you want me to hold off because of that?
-- 
Niko Tyni   nt...@debian.org

Bug#869098: python2.7 2.7.13-4 causes EOFError breakage in python-sphinx

[Matthias Klose]

On 20.07.2017 16:40, Neil Williams wrote:
> Package: python2.7
> Version: 2.7.13-4
> Severity: serious
> Justification: causes other packages to FTBFS
> 
> With 2.7.13-4 installed, I am unable to build documentation as sphinx
> errors out:

please could you check if it builds with the debug interpreter?

Bug#869140: casync FTBFS on mips64el: test-casync TIMEOUT

[Adrian Bunk]

Source: casync
Version: 1+65-1
Severity: important

https://buildd.debian.org/status/fetch.php?pkg=casync&arch=mips64el&ver=1%2B65-1&stamp=1500580132&raw=0

...
   dh_auto_test -a
ninja test
[0/1] Running all tests.
 1/14 test-script.sh  OK  633.39 s
 2/14 test-script-sha256.sh   OK  636.46 s
 3/14 test-nbd.sh OK  177.02 s
 4/14 test-fuse.shOK  305.71 s
 5/14 test-cachunkOK   6.05 s
 6/14 test-cachunker  OK   2.25 s
 7/14 test-cachunker-histogramOK   2.57 s
 8/14 test-cadigest   OK  10.35 s
 9/14 test-caencoder  OK   0.62 s
10/14 test-camakebst  OK  19.00 s
11/14 test-caorigin   OK   0.12 s
12/14 test-casync TIMEOUT 120.20 s
13/14 test-cautil OK   0.11 s
14/14 test-util   OK   0.11 s

OK:13
FAIL:   1
SKIP:   0
TIMEOUT:1


The output from the failed tests:

12/14 test-casync TIMEOUT 120.20 s

--- command ---
/<>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
---

Full log written to 
/<>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
FAILED: test 
/usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
dh_auto_test: ninja test returned exit code 1
debian/rules:8: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1



On mipsel this test succeeded after 108.83 seconds, so this might
just require an increased timeout (untested).

Bug#867718: CVE-2017-11108

[Romain Francoise]

On Thu, Jul 20, 2017 at 10:27:44AM -0400, Antoine Beaupré wrote:
> Opened an issue upstream, as recommended by the RedHat security
> folks. Also sent a pull request for the fix:
>
> https://github.com/the-tcpdump-group/tcpdump/pull/617

It's likely that this was wasted effort--tcpdump is the token
application for afl testing and the upstream team gets lots of reports.
The fix probably already exists in the embargoed repository (which I
don't have access to). The next security release will include it along
with others (see the 4.9.0 changelog to get an idea).

> I'll sit on this one until we get a review from upstream now.

I'm also monitoring the situation, but thanks for your work.

-- 
Romain Francoise 
https://people.debian.org/~rfrancoise/

Bug#869098: python2.7 2.7.13-4 causes EOFError breakage in python-sphinx

[Matthias Klose]

On 20.07.2017 16:40, Neil Williams wrote:
> Package: python2.7
> Version: 2.7.13-4
> Severity: serious
> Justification: causes other packages to FTBFS
> 
> With 2.7.13-4 installed, I am unable to build documentation as sphinx
> errors out:
> 
> sphinx-build -b html -d _build/doctrees  -n -j 4 . _build/html
> Running Sphinx v1.4.9
> making output directory...
> loading pickled environment... not yet created
> loading intersphinx inventory from https://docs.python.org/2/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 91 source files that are out of date
> updating environment: 91 added, 0 changed, 0 removed
> reading sources... [100%] test-repositories .. writing-tests  
> 
> waiting for workers...
> 
> Exception occurred:
>   File "/usr/lib/python2.7/dist-packages/sphinx/util/parallel.py", line 97, 
> in _join_one
> exc, result = pipe.recv()
> EOFError
> The full traceback has been saved in /tmp/sphinx-err-o8zX9U.log, if you want 
> to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> ^CError in atexit._run_exitfuncs:
> 
> The problem now is that lava-server and potentially other packages which build
> documentation with python-sphinx will FTBFS with this version of python2.7
> in unstable.
> 
> Downgrading python-sphinx to the version in Stretch makes no difference.
> 
> Downgrading python2.7 to the version in testing fixes the problem entirely.
> 
> $ sudo apt install python2.7=2.7.13-2 python2.7-minimal=2.7.13-2 
> libpython2.7-stdlib=2.7.13-2 libpython2.7-minimal=2.7.13-2
> 
> sphinx-build -b html -d _build/doctrees  -n -j 4 . _build/html
> Running Sphinx v1.4.9
> making output directory...
> loading pickled environment... not yet created
> loading intersphinx inventory from https://docs.python.org/2/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 91 source files that are out of date
> updating environment: 91 added, 0 changed, 0 removed
> reading sources... [100%] test-repositories .. writing-tests  
> 
> waiting for workers...
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] user-notifications .. writing-tests  
> 
> waiting for workers...
> generating indices... genindex
> writing additional pages... search
> copying images... [100%] images/micro-instance-lab.svg
> 
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en) ... done
> dumping object inventory... done
> build succeeded.
> 
> Build finished. The HTML pages are in _build/html.
> 
> To reproduce, it should be enough to install lava-dev to get the correct
> build dependencies, and try to rebuild lava-server. A quicker test would
> be to get the lava-server source and run:
> 
> $ make -C doc/v2 clean
> $ make -C doc/v2 html
> 
> in the top level directory.
> 
> One of the sphinx error logs:
> 
> # Sphinx version: 1.5.6
> # Python version: 2.7.13+ (CPython)
> # Docutils version: 0.13.1 release
> # Jinja2 version: 2.9.6
> # Last messages:
> #   91 added, 0 changed, 0 removed
> #   reading sources... [ 14%] actions-boot .. data-export
> #   reading sources... [ 28%] debian .. explain_first_job
> #   reading sources... [ 42%] first-devices .. ipxe
> #   reading sources... [ 57%] lava-dashboard-image-reports .. migrate-lava
> #   reading sources... [ 71%] migrating-admin-example .. pipeline-writer
> #   reading sources... [ 85%] pipeline-writer-secondary .. tables
> #   reading sources... [100%] test-repositories .. writing-tests
> #   
> #   waiting for workers...
> # Loaded extensions:
> #   sphinx.ext.coverage (1.5.6) from 
> /usr/lib/python2.7/dist-packages/sphinx/ext/coverage.pyc
> #   sphinx.ext.viewcode (1.5.6) from 
> /usr/lib/python2.7/dist-packages/sphinx/ext/viewcode.pyc
> #   sphinx.ext.todo (1.5.6) from 
> /usr/lib/python2.7/dist-packages/sphinx/ext/todo.pyc
> #   sphinx.ext.autodoc (1.5.6) from 
> /usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.pyc
> #   sphinx.ext.intersphinx (1.5.6) from 
> /usr/lib/python2.7/dist-packages/sphinx/ext/intersphinx.pyc
> #   sphinx.ext.doctest (1.5.6) from 
> /usr/lib/python2.7/dist-packages/sphinx/ext/doctest.pyc
> #   alabaster (0.7.8) from 
> /usr/lib/python2.7/dist-packages/alabaster/__init__.pyc
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/sphinx/cmdline

Bug#868998: debhelper: dh_installman doesn't support paths with space characters

[Sven Joachim]

On 2017-07-20 11:47 +0800, 林博仁 wrote:

> Package: debhelper
> Version: 10.6.4
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> I am practicing maint-guide chapter 5 and implemented a manpage after the
> template
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> I placed the manpage at "Manual Pages" directory under the source root
> directory and added the following line(s) to debian/.manpages:
>
> * Manual Pages/.1
>
>* What was the outcome of this action?
>
> dh_installman complains of missing "Manual" file:
>
> ```
> dh_installman
> "Manual: No such file or directory at /usr/bin/dh_installman line 131.
> debian/rules:19: recipe for target 'binary' failed
> make: *** [binary] Error 2
> ```
>
>* What outcome did you expect instead?
>
> manpage correctly installed either in the following forms in
> debian/.manpages:
>
> * Manual Pages/.1
> * Manual\ Pages/.1
> * "Manual Pages/.1"

I don't think any of these have ever worked in dh_installman (or other
dh_* utilities, for that matter).  What _should_ work is the following:

dh_installman 'Manual Pages/.1'

However, in debhelper 10.6.4 this is currently broken because of bug
#868649, for which I have just sent a patch.

Cheers,
   Sven

Bug#781987: Regarding bug #781987 - dwww: All links are broken after clean install

[David R Forrest]

Arjan's one-line patch to /usr/sbin/dwww-convert corrects this for me.

I get the expected results for /usr/share/doc files, and no longer get the 500 
error document in the browser nor the "AH02429: Response header name 'Last 
modified' contains invalid characters, aborting request" message in error.log

Dave

Bug#868743: gutenprint FTBFS on mips64el: check-TESTS killed with signal TERM after 150 minutes of inactivity

[Didier 'OdyX' Raboud]

Control: severity -1 important
Control: retitle -1 gutenprint sometimes FTBFS on mips64el: check-TESTS killed 
with signal TERM after 150 minutes of inactivity

Le mardi, 18 juillet 2017, 11.05:34 h CEST Adrian Bunk a écrit :
> https://buildd.debian.org/status/fetch.php?pkg=gutenprint&arch=mips64el&ver=
> 5.2.13-1&stamp=1500347072&raw=0
> 
> ...
> Making check in cups
> make[4]: Entering directory '/<>/src/cups'
> make  check-TESTS
> make[5]: Entering directory '/<>/src/cups'
> make[6]: Entering directory '/<>/src/cups'
> E: Build killed with signal TERM after 150 minutes of inactivity

It built when it was retried on mipsel-aql-03; hereby downgrading the severity
accordingly.

Cheers,
OdyX

Bug#858495: glusterfs-client: glusterfs fails to mount storage pool over infiniband rmda

[Phillip Seeber]

Hi all,
news from my infiniband setup: after trying Ingo's recommendation i can
now mount my storage pool again, but strangely files and directories,
that are created do not show up.

/GlusterVolume$ echo "hello" > test.txt

/GlusterVolume$ ls -lah

insgesamt 0

/GlusterVolume$ cat test.txt

hello


So very strange behaviour but the original problem disappeared in some
way...

@Patrick here the netstat -tulpen outputs from the clients

Aktive Internetverbindungen (Nur Server)

Proto Recv-Q Send-Q Local Address   Foreign Address State   
Benutzer   Inode  PID/Program name

tcp0  0 0.0.0.0:22  0.0.0.0:*   LISTEN  
0  4029   499/sshd

tcp0  0 0.0.0.0:68180.0.0.0:*   LISTEN  
0  10399  540/slurmd  

tcp0  0 0.0.0.0:111 0.0.0.0:*   LISTEN  
0  18450  311/rpcbind 

tcp6   0  0 :::22   :::*LISTEN  
0  4031   499/sshd

tcp6   0  0 :::111  :::*LISTEN  
0  3903   311/rpcbind 

udp0  0 0.0.0.0:111 0.0.0.0:*   
0  11401  311/rpcbind 

udp0  0 192.168.1.106:123   0.0.0.0:*   
109102552/ntpd

udp0  0 192.168.178.106:123 0.0.0.0:*   
0  3065   552/ntpd

udp0  0 127.0.0.1:123   0.0.0.0:*   
0  3063   552/ntpd

udp0  0 0.0.0.0:123 0.0.0.0:*   
0  3059   552/ntpd

udp0  0 0.0.0.0:911 0.0.0.0:*   
0  18449  311/rpcbind 

udp6   0  0 :::111  :::*
0  18451  311/rpcbind 

udp6   0  0 fe80::202:c902:22:4:123 :::*
1091023338552/ntpd

udp6   0  0 fd00::d250:99ff:fec:123 :::*
10923253  552/ntpd

udp6   0  0 fe80::d250:99ff:fec:123 :::*
0  3071   552/ntpd

udp6   0  0 ::1:123 :::*
0  3067   552/ntpd

udp6   0  0 :::123  :::*
0  3056   552/ntpd

udp6   0  0 :::911  :::*
0  3902   311/rpcbind


and from the server

Aktive Internetverbindungen (Nur Server)

Proto Recv-Q Send-Q Local Address   Foreign Address State   
Benutzer   Inode  PID/Program name

tcp0  0 0.0.0.0:55761   0.0.0.0:*   LISTEN  
0  17144  643/rpc.mountd  

tcp0  0 0.0.0.0:47505   0.0.0.0:*   LISTEN  
0  17120  643/rpc.mountd  

tcp0  0 192.168.1.1:53  0.0.0.0:*   LISTEN  
1121200942620/named   

tcp0  0 192.168.178.40:53   0.0.0.0:*   LISTEN  
11218140  620/named   

tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN  
11218138  620/named   

tcp0  0 0.0.0.0:22  0.0.0.0:*   LISTEN  
0  3755613618/sshd

tcp0  0 127.0.0.1:631   0.0.0.0:*   LISTEN  
0  69032417770/cupsd  

tcp0  0 127.0.0.1:250.0.0.0:*   LISTEN  
0  287990030154/exim4 

tcp0  0 127.0.0.1:5433  0.0.0.0:*   LISTEN  
114403000 26254/postgres  

tcp0  0 127.0.0.1:953   0.0.0.0:*   LISTEN  
11218143  620/named   

tcp0  0 0.0.0.0:49152   0.0.0.0:*   LISTEN  
0  123040224957/glusterfsd

tcp0  0 0.0.0.0:68170.0.0.0:*   LISTEN  
64030  19899  699/slurmctld   

tcp0  0 0.0.0.0:20490.0.0.0:*   LISTEN  
0  17348  -   

tcp0  0 0.0.0.0:44645   0.0.0.0:*   LISTEN  
0  17363  -   

tcp0  0 0.0.0.0:31420.0.0.0:*   LISTEN  
12519349  623/apt-cacher-ng   

tcp0  0 0.0.0.0:24007   0.0.0.0:*   LISTEN  
0 

Bug#868649: dh_installdocs: cp --reflink=auto -a cccc/CCCC debian/cccc/usr/share/doc/cccc returned exit code 1

[Sven Joachim]

Control: tags -1 + patch

On 2017-07-17 11:24 +0300, Adrian Bunk wrote:

> Package: debhelper
> Version: 10.6.4
> Severity: serious
> Control: affects -1 src:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/.html
>
> ...
>debian/rules override_dh_installdocs
> make[1]: Entering directory '/build/1st/-3.1.4'
> dh_installdocs '/ User Guide.html'
> cp: cannot stat '/': No such file or directory
> dh_installdocs: cp --reflink=auto -a / debian//usr/share/doc/ 
> returned exit code 1
> debian/rules:41: recipe for target 'override_dh_installdocs' failed
> make[1]: *** [override_dh_installdocs] Error 2
>
>
> Works with debhelper 10.2.5, FTBFS with 10.6.4

The culprit is commit d00d7d524f874c which fixed the changed behavior in
dh_install (see #867866) but overzealously also touched a few other
utilities like dh_installdocs.  It turns out that these programs
actually treated an argument like 'foo bar' as a single file in 10.2.5,
and obviously there are a few packages which rely on that.

Attached is a patch to revert these programs to their previous behavior.

Cheers,
   Sven

>From 91d23c5cb9af4694b018bc2fd219da0dfa941f9d Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Thu, 20 Jul 2017 20:46:26 +0200
Subject: [PATCH] Revert to the pre-10.6.4 behavior for dh_installdocs and the
 like

It turned out that "dh_installdocs 'foo bar'" has historically treated
the argument as a single file rather than two, and packages were
relying on it, since there is really no other way to install such a
file with dh_installdocs.  Hence commit d00d7d524f8 broke them.

The situation for dh_installexamples, dh_installman and dh_installinfo
is exactly the same.

That dh_install has behaved differently in this respect is
unfortunate, but can only be fixed in a new compat level.
---
 dh_installdocs | 3 +--
 dh_installexamples | 3 +--
 dh_installinfo | 3 +--
 dh_installman  | 3 +--
 4 files changed, 4 insertions(+), 8 deletions(-)

diff --git a/dh_installdocs b/dh_installdocs
index 7b81e008..bb2616c1 100755
--- a/dh_installdocs
+++ b/dh_installdocs
@@ -235,8 +235,7 @@ foreach my $package (getpackages()) {
 	}
 
 	if (($package eq $dh{FIRSTPACKAGE} || ($dh{PARAMS_ALL} && !$link_doc)) && @ARGV) {
-		# The split is for bug-backwards compatibility (#867866).
-		push(@docs, map { split } @ARGV);
+		push @docs, @ARGV;
 	}
 
 	log_installed_files($package, @docs);
diff --git a/dh_installexamples b/dh_installexamples
index 79e68020..6f0e8068 100755
--- a/dh_installexamples
+++ b/dh_installexamples
@@ -100,8 +100,7 @@ foreach my $package (getpackages()) {
 	}	
 
 	if (($package eq $dh{FIRSTPACKAGE} || $dh{PARAMS_ALL}) && @ARGV) {
-		# The split is for bug-backwards compatibility (#867866).
-		push(@examples, map { split } @ARGV);
+		push @examples, @ARGV;
 	}
 
 	log_installed_files($package, @examples);
diff --git a/dh_installinfo b/dh_installinfo
index ff9bbe21..dbef7de6 100755
--- a/dh_installinfo
+++ b/dh_installinfo
@@ -83,8 +83,7 @@ foreach my $package (getpackages()) {
 	}
 
 	if (($package eq $dh{FIRSTPACKAGE} || $dh{PARAMS_ALL}) && @ARGV) {
-		# The split is for bug-backwards compatibility (#867866).
-		push(@info, map { split } @ARGV);
+		push @info, @ARGV;
 	}
 
 	next if not process_pkg($package) or $nodocs;
diff --git a/dh_installman b/dh_installman
index f61d7e62..1740a5d7 100755
--- a/dh_installman
+++ b/dh_installman
@@ -161,8 +161,7 @@ on_items_in_parallel(\@all_packages, sub {
 		@manpages = filearray($file, \@search_dirs, $error_handler) if $file;
 
 		if (($package eq $dh{FIRSTPACKAGE} || $dh{PARAMS_ALL}) && @ARGV) {
-			# The split is for bug-backwards compatibility (#867866).
-			push(@manpages, map { split } @ARGV);
+			push @manpages, @ARGV;
 		}
 
 		log_installed_files($package, @manpages);
-- 
2.13.3

Bug#869121: ITP: dragonfire -- Dragonfire is an open source virtual assistant project for Debian based Linux distributions

[Mehmet Mert Yıldıran]

Mr. Treinen,

I fixed the subject using cont...@bugs.debian.org, but I couldn't update
the "Description : " part. So I'm sending the updated description via this
email:

This package installs a binary named "dragonfire" to your system. Once it's
installed, the user can execute it either from command line or from the
Application Launcher. It receives voice commands from users and takes
actions accordingly.

Dragonfire goes through these steps for your commands, respectively:
 - Search across the built-in commands
 - Try to Learn using Advanced NLP and Database Management Techniques
 - Ask to Omniscient Q&A Engine

Dragonfire plays an avatar animation on the screen (for max 10 seconds)
everytime she speaks. It uses default notification method of the system and
also places an icon to the system tray.

Dragonfire is the missing virtual assistant of Linux while macOS has Siri,
Windows has Cortana. This is why it's an indispensable package for Debian's
repositories. I also guarantee to maintain this package for at least 8
years. The project is already 2 years old.

Thanks for your attention. Kindest regards...

Bug#868896: xdu: does not show result with huge input file

[Karl Voit]

Rémi Vanicat (remi.vani...@lot-of-stuff.info) wrote:

> Karl Voit  writes:
> 
> Hello, thanks for the report.

You're welcome.

> > Maybe there is an overflow somewhere?
> 
> Some test seem to point in this direction. As a way to overcome this
> problem you could try to use the "-k" or "-m" option of du.

This is a good workaround which works at my side. Thanks for the
pointer. It was not that obvious to me ;-)

-- 
Karl Voit

Bug#869139: syslog-ng-incubator FTBFS on s390x: FAIL: modules/grok/tests/test_grok

[Adrian Bunk]

Source: syslog-ng-incubator
Version: 0.5.0-5
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=syslog-ng-incubator&arch=s390x&ver=0.5.0-5&stamp=1500577713&raw=0

...
FAIL: modules/grok/tests/test_grok
PASS: modules/date/tests/test_date
=
   syslog-ng-incubator 0.5.0: ./test-suite.log
=

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: modules/grok/tests/test_grok
==

[2017-07-20T19:08:28.677347] WARNING: template: the default value for 
template-escape has changed to 'no' from syslog-ng 3.0, please update your 
configuration file accordingly;
[50431] [patterns] [grok_pattern_add:29] Adding new pattern 'STRING' => 
'[a-zA-Z]+'
[50431] [patterns] [grok_pattern_add:29] Adding new pattern 'NUMBER' => '[0-9]+'
[50431] [compile] [grok_compilen:66] Compiling '%{STRING:field}'
[50431] [regexpand] [grok_pattern_expand:179]  start of expand: 
%{STRING:field}
[50431] [regexpand] [grok_pattern_expand:190]start of loop: 
%{STRING:field}
[50431] [regexpand] [grok_pattern_expand:203] Pattern length: 15
[50431] [regexpand] [grok_pattern_expand:209] Pattern name: STRING
[50431] [patterns] [grok_pattern_find:41] Searching for pattern 'STRING' 
(found): 
[50431] [capture] [grok_capture_add:30] Adding pattern 'STRING:field' as 
capture 0 (pcrenum 0)
[50431] [regexpand] [grok_pattern_expand:281]   replace with (?<>): (?<>)
[50431] [regexpand] [grok_pattern_expand:288]   add capture id: (?<_>)
[50431] [regexpand] [grok_pattern_expand:297] :: Inserted: 
[50431] [regexpand] [grok_pattern_expand:298] :: STR: (?<_>)
[50431] [regexpand] [grok_pattern_expand:330] Fully expanded: (?<_>)
[50431] [compile] [grok_study_capture_map:407] Studying capture 0
[50431] [capture] [grok_capture_add:30] Adding pattern 'STRING:field' as 
capture 0 (pcrenum 1)
[50431] [exec] [grok_execn:128] value =~ /%{STRING:field}/ => 2
[50431] [capture] [grok_capture_walk_next:231] walknext ok 0
[50431] [match] [grok_match_walk_next:61] CaptureWalk 'STRING:field' is 0 -> 0 
of string 'value'
[50431] [capture] [grok_capture_walk_next:228] walknext null

  ###
  #
  # FAIL: ASSERTION FAILED: Named capture didn't stored;  actual_length=0 
expected_length=5,
  #  actual=   '',
  #  expected= 'value'
  #
  ###

FAIL modules/grok/tests/test_grok (exit status: 1)


Testsuite summary for syslog-ng-incubator 0.5.0

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to viktor.juh...@balabit.com

Makefile:2162: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1

Bug#869138: ITP: fonts-sil-tagmukay -- Tagmukay is a Shifinagh (also know as Tifinagh) script font

[Bobby de Vos]

Package: wnpp
Version N/A; reported 2017-07-20
Severity: wishlist

Greetings,

My team at SIL-NRSI has released a font not in Debian, Tagmukay
that I would like to package for Debian.

Package name: fonts-sil-tagmukay
Version : 2.000
Upstream Author : SIL NRSI 
URL : http://software.sil.org/tagmukay
License : OFL-1.1
Section : fonts
Description : Tifinagh Unicode TrueType font with OT and Graphite support

Tagmukay is a Shifinagh (also know as Tifinagh) script font with support
for the Tawallammat Tamajaq language. It is a Unicode font that features
bi-consonant ligatures and alternate forms necessary to support this
language. It has Graphite and OpenType tables that have the logic to
support these features.

It builds those binary packages:

fonts-sil-tagmukay - Tagmukay is a Shifinagh (also know as Tifinagh)
script font

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

http://software.sil.org/tagmukay/

Daniel Glassey can sponsor this package, or Fabian Greffrath might, as
he sponsored the last font I packaged, fonts-sil-annapurna.

Regards,
Bobby

-- 
Bobby de Vos
/bobby_de...@sil.org/

Bug#860801: Add a check for missing dependencies from gir packages

[Chris Lamb]

tags 860801 + pending
thanks

Fixed in Git:

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


Regards,

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

Bug#856240: jessie-pu: package elog/2.9.2+2014.05.11git44800a7-2+deb8u1

[Gianfranco Costamagna]

Hello,
> I don't see see your package in jessie-new; the next jessie point release
> is coming up shortly, so feel free to prod your sponsor again if you want
> to have a chance of fixing this in jessie. :)
> 
sponsored, sorry for the delay

G.



signature.asc
Description: OpenPGP digital signature

Bug#854414: screen uses "screen.xterm-256color" without screen I get "xterm-256color" which works

[Martin Steigerwald]

Axel Beckert - 16.07.17, 23:26:
> Hi,
> 
> Axel Beckert wrote:
> > So my current plan is to document the issue in README.Debian with the
> > following suggestions as workaround, depending on the ncurses-term
> > versions installed locally and remote:
> > 
> > * Use "env TERM=xterm screen" (or similar).
> > * Use "term screen" inside .screenrc
> > * Uninstall ncurses-term locally or install ncurses-term on the remote
> > 
> >   machine.
> > 
> > Exact wording still needs to be determined. Suggestions welcome,
> > especially from users which ran into that issue and hence have a
> > better feeling what works in which case and what doesn't.
> 
> Based on the feedback on this mail, I've made a first try on
> documenting ways out of that $TERM fiddling hell:
> 
> https://anonscm.debian.org/cgit/collab-maint/screen.git/commit/?id=5aa1cd4cb
> af92e2d7570b102e9069d8898ca4807

Quoting in mail:

> diff --git a/debian/README.Debian b/debian/README.Debian
> index 1797fc4..6d4479c 100644
> --- a/debian/README.Debian
> +++ b/debian/README.Debian
[…]
> +Q: When I'm using ssh from inside screen, I get the error message
> +   "Error opening terminal: screen.xterm-256color." or similar.
> +
> +A: The TERM variable inside a screen session (which is then passed to
> +   the remote shell by ssh) depends on two things:
> +
> +   1. Availability of of specific termcap entries locally.
> +   2. Value of the TERM variable when the session was started.
> +
> +   To avoid this error message, the best way is to start a new screen
> +   session under a different circumstances, but there are also ways

=> "under different circumstances"

I am not sure whether I´d understand this as "under different circumstances" 
is quite unspecific. I´d think I´d rather write "with different terminal 
configuration"

> +   without starting a new sessions. You have several options:
> +
> +   Without starting a new screen session:
> +
> +   * Start ssh with "env TERM=screen-256color ssh".
> +
> +   * Install ncurses-term on  the remote machine and then  start a new
> + ssh session. (Might help, depending on the remote distribution.)
> +
> +   Exiting the current screen session, change one of the following and
> +   start a new screen session:
> +
> +   * Add "term screen-256color" to ~/.screenrc or /etc/screenrc on
> + your local machine.
> +
> +   * Start the new screen session with "env TERM=xterm screen".
> +
> +   * Start the new screen session with "screen -T screen-256color".
> +
> +   * Uninstall ncurses-term locally and then start a new screen
> + session. (Might help, depending on the remote distribution.)

Whoa, I wondered whether to give this many options, but… I think its okay :) 
as you added the options that IMHO works best at the beginning of the lists.

> +   If "screen-256color" is not available on the remote distribution
> +   either, especially if it's not a recent release, try just "screen"
> +   instead of "screen-256color".

You might want to add a link to the bug report in README.Debian. I know you 
added a hint to it into the Changelog, but I think I´d add it here as well for 
people who want to know the background behind all of this.

Thanks,
-- 
Martin

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

Bug#869136: casync: FTBFS on sparc64: test suite bus error

[Felipe Sateler]

Control: forwarded -1 https://github.com/systemd/casync/issues/60

On Thu, Jul 20, 2017 at 3:13 PM, Aaron M. Ucko  wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
> Justification: fails to build from source
>
> The build of casync for sparc64 (admittedly not a release
> architecture) failed:
>
>   + /<>/casync-1+65/obj-sparc64-linux-gnu/casync -v 
> --without=privileged --digest=sha256 list 
> localhost:/var/tmp/test-casync.20172/test.caidx
>   Selected chunk sizes: min=16384..avg=65536..max=262144
>   -sing feature flags: nsec-time permissions symlinks fifos sockets 
> flag-hidden flag-archive flag-noatime flag-compr flag-nocow flag-dirsync 
> flag-sync flag-nocomp flag-projinherit xattrs
>   Excluding files with chattr(1) -d flag: yes
>   Excluding submounts: no
>   Digest algorithm: sha256
>   /<>/casync-1+65/obj-sparc64-linux-gnu/test-script.sh: line 138: 
> 58494 Bus error   
> "/<>/casync-1+65/obj-sparc64-linux-gnu"/casync $PARAMS list 
> localhost:$SCRATCH_DIR/test.caidx > $SCRATCH_DIR/test-remote.caidx.list
>
> I don't have further details beyond what you can find at
> https://buildd.debian.org/status/fetch.php?pkg=casync&arch=sparc64&ver=1%2B65-1&stamp=1500566201&raw=0,
> but perhaps you can reproduce the crash on a porterbox.
>
> Could you please take a look?

Indeed, I have it on my todo list.

-- 

Saludos,
Felipe Sateler

Bug#869137: sash: [INTL:de] Initial German debconf translation

[Chris Leick]

Package: sash
Version: 3.8-4
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the initial German debconf translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#868788: Security fixes from the July 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Thu, Jul 20, 2017 at 12:08:29PM +0200, Lars Tangvald wrote:
> Hi,
> 
> The Jessie update to MySQL 5.5.57 has been built and tested without any
> issues seen.
> 
> Attached are debdiff files for the Jessie update to MySQL 5.5.57

This is fine. Do you have a DD in your team who can preferably sponsor
the upload to jessie-security?

Regards,
Salvatore

Bug#869134: casync: FTBFS: linux/magic.h: No such file or directory

[Felipe Sateler]

Control: tags -1 pending

On Thu, Jul 20, 2017 at 3:09 PM, Aaron M. Ucko  wrote:
>
> Source: casync
> Version: 1+65-1
> Severity: important
> Justification: fails to build from source
>
> Builds of casync on kfreebsd-* (admittedly not release architectures) failed:
>
>   ../src/util.h:17:25: fatal error: linux/magic.h: No such file or directory
>
> I presume a build on hurd-i386 (not a release architecture either)
> would have failed in the same fashion if not for an unsatisfiable
> build dependency on libfuse-dev.  Could you please either accommodate
> non-Linux architectures or adjust casync's Architecture setting
> appropriately?


Upstream has indicated it is willing to accept patches for other
architectures as long as they are not too intrusive, but currently
only linux is supported.

Fixed in git. I'll wait until 869136 is fixed before uploading though.

-- 

Saludos,
Felipe Sateler

Bug#866389: transition: perl 5.26

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 20/07/17 21:01, Niko Tyni wrote:
> On Thu, Jun 29, 2017 at 07:51:33PM +0200, Emilio Pozuelo Monfort wrote:
>> Control: forwarded -1 
>> https://release.debian.org/transitions/html/perl5.26.html
>>
>> On 29/06/17 14:07, Niko Tyni wrote:
>>> Package: release.debian.org
>>> User: release.debian@packages.debian.org
>>> Usertags: transition
>>> X-Debbugs-Cc: debian-p...@lists.debian.org
>>>
>>> We'd like to get Perl 5.26 in sid/buster soonish.
> 
>> Nice. Let us know when things are better. Currently there's not much going on
>> and we could do the perl transition without problems if you were ready. But
>> let's evaluate again when things are improved.
> 
> Hi, we're now ready to go. The only known blocker left is #826473 in
> kdesrc-build, which can be removed from testing. We just did a one last
> rebuild test of the packages that will need a binnmu, and found no new
> issues.
> 
> Many kudos to all the maintainers who fixed their packages, and to Gregor
> who fixed the rest :)
> 
> Please let us know when it would be OK to upload Perl 5.26 to sid.

Awesome. Now is a good time. I have added some hints for the gsoap and
libprelude transitions, so they don't get entangled with this one.

go go go!
Emilio

Bug#869126: [Debian-med-packaging] Bug#869126: augustus: explicit dependency on libhts1, blocks transition

[Mattia Rizzolo]

On Thu, Jul 20, 2017 at 08:32:56PM +0200, Graham Inggs wrote:
> In addition, it appears that at least bam2wig is statically linked
> against libbam.a and libhts.a [3], so that should probably changed to
> link against the shared libraries instead.

Please note that this is a bug by itself, as the package is not
publishing any Built-Using field.  (plus, put here usual rant about
statically linked binaries)

-- 
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#869135: Please consider switching to giza

[Ole Streicher]

Source: libpgplot-perl
Version: 1:2.21-6
Severity: wishlist

Dear maintainer,

since about a year, there is a replacement library for pgplot available
in Debian: giza [1]. This is almost compatible, but has a DFSG conform
license (GPL-2+), which would allow to migrate libpgplot-perl to the
main section. I already use it successfully in a number of packages in
the astronomy context, f.e. in dpuser which allows an interactive
transparent access to pgplot functions from a command line.

Would you consider testing the adoption of giza for libpgplot-perl?

Best regards

Ole (maintainer of the Debian giza package)

[1] https://tracker.debian.org/pkg/giza

Bug#869136: casync: FTBFS on sparc64: test suite bus error

[Aaron M. Ucko]

Source: casync
Version: 1+65-1
Severity: important
Justification: fails to build from source

The build of casync for sparc64 (admittedly not a release
architecture) failed:

  + /<>/casync-1+65/obj-sparc64-linux-gnu/casync -v 
--without=privileged --digest=sha256 list 
localhost:/var/tmp/test-casync.20172/test.caidx
  Selected chunk sizes: min=16384..avg=65536..max=262144
  -sing feature flags: nsec-time permissions symlinks fifos sockets flag-hidden 
flag-archive flag-noatime flag-compr flag-nocow flag-dirsync flag-sync 
flag-nocomp flag-projinherit xattrs
  Excluding files with chattr(1) -d flag: yes
  Excluding submounts: no
  Digest algorithm: sha256
  /<>/casync-1+65/obj-sparc64-linux-gnu/test-script.sh: line 138: 
58494 Bus error   
"/<>/casync-1+65/obj-sparc64-linux-gnu"/casync $PARAMS list 
localhost:$SCRATCH_DIR/test.caidx > $SCRATCH_DIR/test-remote.caidx.list

I don't have further details beyond what you can find at
https://buildd.debian.org/status/fetch.php?pkg=casync&arch=sparc64&ver=1%2B65-1&stamp=1500566201&raw=0,
but perhaps you can reproduce the crash on a porterbox.

Could you please take a look?

Thanks!

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

Bug#869134: casync: FTBFS: linux/magic.h: No such file or directory

[Aaron M. Ucko]

Source: casync
Version: 1+65-1
Severity: important
Justification: fails to build from source

Builds of casync on kfreebsd-* (admittedly not release architectures) failed:

  ../src/util.h:17:25: fatal error: linux/magic.h: No such file or directory

I presume a build on hurd-i386 (not a release architecture either)
would have failed in the same fashion if not for an unsatisfiable
build dependency on libfuse-dev.  Could you please either accommodate
non-Linux architectures or adjust casync's Architecture setting
appropriately?

Thanks!

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

Bug#782075: gnome-tweak-tool: Crashes Gnome when reducing Number of Workspaces

[intrigeri]

Jens Reyer:
> This bug is still marked as unreproducible.  Did you (or anyone else)
> try to reproduce with my previously described steps (see below)?

I did that a while ago, but it was on Tails (based on Jessie back
then): https://labs.riseup.net/code/issues/10797

Bug#866016: 866016 is closed by mockldap upload

[Neil Williams]

notfound 866016 1.2.12+dfsg-1
thanks

Just built django-auth-ldap in a sid schroot as the mockldap upload has
been made.

Updating 866016 as the bug was actually not in this package but in the
fact that the mockldap package was missing. This allows packages
depending on django-auth-ldap to not get listed for auto-removal.

Closing 782917 as the python3 package now exists:

https://packages.debian.org/unstable/python3-django-auth-ldap

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpoQicYZSesm.pgp
Description: OpenPGP digital signature

Bug#822436: nestopia closes when launching roms

[Aaron Valdes]

I get something similar.

daylan@RogueOne:~/Games/Nestopia$ nestopia 
0 joystick(s) found:
Could not create glcontext: Could not create GL context: GLXBadFBConfig
OpenGL: (null)
Database: 2901 items imported from internal DB
/home/daylan/.nestopia/disksys.rom not found, Disk System games will not work.
Ines: warning, unknown or invalid header data!
Ines: 128k PRG-ROM set
Ines: 128k CHR-ROM set
Ines: 840k W-RAM set
Ines: vertical mirroring set
Ines: NTSC set
Ines: mapper 1 set
Board: SKROM
Board: 128k PRG-ROM
Board: 128k CHR-ROM
Board: 8k auto W-RAM
Board: MMC rev. B2
Region: NTSC
nestopia: Couldn't find current GLX or EGL context.


On Sun, 24 Apr 2016 20:23:10 +0200 Stephen Kitt  wrote:
> Hi Diego,
> 
> On Sun, 24 Apr 2016 15:08:23 +0200, diego  wrote:
> > When launching a rom the program closes. I don't know how to retrieve more
> > information about the bug, so if more information is needed you will have to
> > say me how I should obtain it.
> 
> How do you go about launching the ROM? Does this happen with specific ROMs,
> or with all those you've tried?
> 
> Regards,
> 
> Stephen

Bug#866389: transition: perl 5.26

[Niko Tyni]

On Thu, Jun 29, 2017 at 07:51:33PM +0200, Emilio Pozuelo Monfort wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/perl5.26.html
> 
> On 29/06/17 14:07, Niko Tyni wrote:
> > Package: release.debian.org
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: debian-p...@lists.debian.org
> > 
> > We'd like to get Perl 5.26 in sid/buster soonish.

> Nice. Let us know when things are better. Currently there's not much going on
> and we could do the perl transition without problems if you were ready. But
> let's evaluate again when things are improved.

Hi, we're now ready to go. The only known blocker left is #826473 in
kdesrc-build, which can be removed from testing. We just did a one last
rebuild test of the packages that will need a binnmu, and found no new
issues.

Many kudos to all the maintainers who fixed their packages, and to Gregor
who fixed the rest :)

Please let us know when it would be OK to upload Perl 5.26 to sid.
-- 
Niko Tyni   nt...@debian.org

Bug#868777: #868777

[Alexandre Viau]

I have started working on this already.

I maintain a TODO list in d/changelog:
 -
https://anonscm.debian.org/cgit/pkg-go/packages/influxdb.git/tree/debian/changelog

It will probably take a while to package uber-go/zap. It has a lot of
dependencies that are not in Debian already.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#869133: bibledit-gtk: RM bibledit-gtk bibledit-gtk-data

[Teus Benschop]

Source: bibledit-gtk
Severity: normal

Dear Maintainer,

Because of bug #866632 (depends on deprecated libwebkitgtk-1.0-0,
and because the maintainer does not update bibledit-gtk,
the packages bibledit-gtk and bibledit-gtk-data are requested
to be removed from the archives.

(There's a newer package (bibledit) available in experimental.
That package is maintained.)


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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
*** End of the template - remove these template lines ***

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#869132: curvedns: Incomplete debian/copyright?

[Chris Lamb]

Source: curvedns
Version: 0.87-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: NEVEU Stephane 

Hi,

I just ACCEPTed curvedns from NEW but noticed it was missing 
attribution in debian/copyright for at least:

  nacl/crypto_scalarmult/curve25519/donna_c64/smult.c


(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#869129: librsvg: CVE-2017-11464

[Salvatore Bonaccorso]

On Thu, Jul 20, 2017 at 08:37:30PM +0200, Salvatore Bonaccorso wrote:
> Please adjust the affected versions in the BTS as needed.

AFAICT, the problematic code has been introduced while "This replaces
the blurring machinery with a real gaussian blur for small radiuses,
and fixes box blurs for large radiuses." with upstream commit  and
included in 2.40.9. So jessie is not affected.

Please double-check.

Regards,
Salvatore

p.s.: adjusted severity, grave is not warranted here IMHO, and was an
  error on my side while filling the bug. OTOH I have no access to
  the upstream bug which might contain more relevant information.

Bug#869121: ITP: dragonfire -- Dragonfire is an open source virtual assistant project for Debian based Linux distributions

[Mehmet Mert Yıldıran]

Hi Mr. Treinen,

Thanks for the reply. How can I update my bug report?

Bug#869131: override: libjs-mousetrap:web/extra

[Alexandre Viau]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 832...@bugs.debian.org

As mentioned in #832237.

> The section “ruby” is for packages that install the Ruby programming
> language or libraries. Its packages are primarily of interest only to
> Ruby programmers.

> The package ‘libjs-mousetrap’ installs primarily a library in the
> JavaScript programming language. It should not be in the “ruby”
> section.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#869130: ITP: libstorj

[Josue Ortega]

Package: wnpp
Severity: wishlist
Owner: Josue Ortega 

*Package name: libstorj
 Version: 1.0.1
 Upstream Author: Storj Labs
*URL: https://github.com/Storj/libstorj
*Licence: GPLv2
Programming Lang: C
Description: Asynchronous multi-platform C library and CLI for encrypted file 
transfer on the Storj network. https://storj.io

---
Josue Ortega
http://josueortega.org

signature.asc
Description: PGP signature