Bug#893520: ImportError: No module named backports.ssl_match_hostname

[Scott Kitterman]

On Fri, 30 Mar 2018 23:04:49 -0400 Jason Pleau  wrote:
> Small typo in my previous email, the .prerm script contains:
> 
> pyclean -p python-backports.ssl-match-hostname
> 
> I had another package in my clipboard, just wanted to clear that up so
> there's no confusion :)

Thanks.  That's helpful.

Looking at debpython/namespace.py, it is supposed to prevent this from 
happening.  Not sure why it isn't yet.

I agree python-defaults is the right package for this, I don't think it's 
grave, however.

Scott K

Bug#892503: tmux: display garbling with nested sessions

[Vagrant Cascadian]

On 2018-03-11, Romain Francoise  wrote:
> On Fri, Mar 9, 2018 at 8:45 PM, Vagrant Cascadian  wrote:
>> I've got a tmux (2.3-4) session running on a stretch machine, from which
>> I ssh to a buster machine and run tmux (2.6-3). In both cases,
>> TERM=screen. When the output reaches the bottom of the screen, the
>> output gets garbled, leaving artifacts from previous states: [...]
>
> Thanks for the report, I can definitely reproduce the bug you
> describe. I noticed that if the outer tmux is up-to-date (2.6) then
> the bug doesn't happen anymore, which suggests that this was a bug in
> tmux 2.3 that has since been fixed.
>
> Can you try installing tmux 2.6 from stretch-backports on your stretch
> machine and see if that fixes the issue for you?

At first, that didn't seem to help, even starting a fresh tmux session
on the stretch machine ... but ... after a reboot, it's working fine! So
at least that helps.

Though, while using backports works around the issue, it would be ideal
to get it fixed in stretch as well...

Thanks for following up.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#894068: ocrmypdf: New dependency on PyMuPDF for v6.0.0

[James R Barlow]

Hello Sean,

As promised ocrmypdf v6.1.2 makes pymupdf optional but recommended. My
continuous integration tests check with and without pymupdf.

The only major regression without pymupdf is that with all of:
1) an input file containing a mix of scanned and born digital files
2) --skip-text (not default)
3) --output-type pdf (not default)
the output file can grow extremely large compared to the input. Past
versions of ocrmypdf have had this issue for a long time, and now it will
produce a warning.

So it should be ready for Debian.

Thanks.


On Mon, 26 Mar 2018 at 14:30 Sean Whitton  wrote:

> Hello,
>
> On Mon, Mar 26 2018, James R Barlow wrote:
>
> > Thanks for the information. That's a worryingly high wall to climb and
> > I'm concerned about implications for other platforms as well.
> >
> > I would appreciate if you can see about getting an exception, but I
> > think I will change PyMuPDF to an optional but recommended dependency
> > fairly soon.
>
> That would be great in the meantime.
>
> > I haven't made a major investment in it as yet with new code, but it
> > does provide some powerful features that would be a major engineering
> > effort to replicate and are likely not going to materialize in another
> > open source library anytime soon. (Specifically: incremental updates,
> > safe editing of PDF/A, PDF object garbage collection, fast
> > rasterizing, robust text extraction.) The most commonly used Python
> > PDF library, PyPDF2, is essentially unmaintained and in poor shape.
>
> Having thought some more, I think our best bet will be to try to get
> pymupdf to support linking against the static version of mupdf.  We have
> techniques in Debian to deal with security updates in that case (called
> binNMUs if you want to look them up).
>
> --
> Sean Whitton
>

Bug#874498: protobuf: Please package latest upstream version

[Andres Salomon]

Hi,

So at this point I'm stuck waiting on an updated protobuf before I can 
update gplaycli packages.  Is there something I can do to help get a 
new version of protobuf uploaded to sid?


Thanks,
Andres

Bug#894204: libpython3.7-stdlib: Still having same issue with libpython 3.7.0~b3-1

[Jesse Taylor]

Package: libpython3.7-stdlib
Version: 3.7.0~b3-1
Followup-For: Bug #894204

Dear Maintainer,

   * Trying to upgrade from testing -> sid 
   * Tried dist-upgrade and also just installing libpython3.7 directly.
   * Same as original report.
   * No error, since bug report said would be resolved with upload of 
libpython3.7


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

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

Versions of packages libpython3.7-stdlib depends on:
ii  libbz2-1.01.0.6-8.1
ii  libc6 2.27-2
ii  libdb5.3  5.3.28-13.1+b1
ii  libffi6   3.2.1-8
ii  liblzma5  5.2.2-1.3
ii  libmpdec2 2.4.2-1
ii  libncursesw5  6.1-1
iu  libpython3.7-minimal  3.7.0~b3-1
ii  libreadline7  7.0-3
ii  libsqlite3-0  3.22.0-2
ii  libtinfo5 6.1-1
ii  mime-support  3.60

libpython3.7-stdlib recommends no packages.

libpython3.7-stdlib suggests no packages.

Bug#893520: ImportError: No module named backports.ssl_match_hostname

[Jason Pleau]

Small typo in my previous email, the .prerm script contains:

pyclean -p python-backports.ssl-match-hostname

I had another package in my clipboard, just wanted to clear that up so
there's no confusion :)

-- 
Jason Pleau

Bug#893520: ImportError: No module named backports.ssl_match_hostname

[Jason Pleau]

Hi. I was also affected by this bug and I managed to reproduce it.

> Why do you think that the file going missing is a python-minimal bug?

The missing file seems to be generated by the postinst script which
contains:

pycompile -p python-backports.ssl-match-hostname


But, there's also a .prerm script for this package that runs this:

pyclean -p python-backports-shutil-get-terminal-size


If you install (reinstall) those packages:

python-backports.ssl-match-hostname
python-backports-shutil-get-terminal-size

And remove either of them, you'll end up with

/usr/lib/python2.7/dist-packages/backports/__init__.py{c}

missing.


Maybe those scripts should check if those files belong to another
packages before running pyclean

There are other python-backports-* packages that probably suffer from
the same problem.


-- 
Jason Pleau

Bug#894484: evolution: conffiles not removed

[Paul Wise]

Package: evolution
Version: 3.28.0-3
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ pkg=evolution ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' $pkg | grep 
obsolete
evolution: obsolete-conffile /etc/xdg/autostart/evolution-alarm-notify.desktop
 /etc/xdg/autostart/evolution-alarm-notify.desktop 
7372d76421ab6b272b8d5f3f97ecd161 obsolete

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

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

Versions of packages evolution depends on:
ii  dbus   1.12.6-2
ii  evolution-common   3.28.0-3
ii  evolution-data-server  3.28.0-2
ii  libc6  2.27-2
ii  libcamel-1.2-613.28.0-2
ii  libclutter-gtk-1.0-0   1.8.4-3
ii  libecal-1.2-19 3.28.0-2
ii  libedataserver-1.2-23  3.28.0-2
ii  libevolution   3.28.0-3
ii  libglib2.0-0   2.56.0-4
ii  libgtk-3-0 3.22.29-2
ii  libical3   3.0.1-5
ii  libnotify4 0.7.7-3
ii  libsoup2.4-1   2.62.0-1
ii  libwebkit2gtk-4.0-37   2.20.0-2
ii  libxml22.9.4+dfsg1-6.1
ii  psmisc 23.1-1

Versions of packages evolution recommends:
ii  evolution-plugin-pstimport 3.28.0-3
ii  evolution-plugin-spamassassin  3.28.0-3
ii  evolution-plugins  3.28.0-3
ii  yelp   3.26.0-2

Versions of packages evolution suggests:
pn  evolution-ews   
ii  evolution-plugins-experimental  3.28.0-3
ii  gnupg   2.2.5-1
ii  network-manager 1.10.6-2

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#894483: gaupol: Please add dependency on gstreamer1.0-gtk3

[Osmo Salomaa]

Source: gaupol
Severity: important

Dear Maintainer,

Gaupol's uses the gtk-sink element, which along with GStreamer 1.14 has
moved in upstream from bad to good and now seems in Debian to be built
from the good source into a separate "gstreamer1.0-gtk3" package. So, we
need a dependency on that for the video player to work. Only affects
Gaupol >= 1.3 as earlier versions use autovideosink.

Originally reported upstream: https://github.com/otsaloma/gaupol/issues/83

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

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

Bug#894482: evolution-data-server: crashes caused by lax deps on libebook-contacts, libedata-book, libedata-cal

[Paul Wise]

Package: evolution-data-server
Version: 3.28.0-2
Severity: serious
File: /usr/lib/evolution/evolution-calendar-factory
File: /usr/lib/evolution/evolution-addressbook-factory

I recently auto-upgraded evolution from testing to unstable because
evolution-rss got auto-removed from testing due to the gconf transition
so unattended-upgrades upgraded it to the latest unstable version.

This upgrade did not go well and resulted in the address book and
calendar not working because the above factory programs segfaulted.

I narrowed this down to being caused by the versioned deps on the
libebook-contacts, libedata-book and libedata-cal libraries being too
lax and allowing the versions from testing to stay installed.

Package: evolution-data-server
Depends: ... libebook-contacts-1.2-2 (>= 3.25.90) ... libedata-book-1.2-25 (>= 
3.26.2), libedata-cal-1.2-28 (>= 3.26.2) ...

The crashes persisted until I did this upgrade via aptitude:

$ tail -n3 /var/log/apt/history.log
Start-Date: 2018-03-31  09:01:18
Upgrade: libebook-contacts-1.2-2:amd64 (3.26.5-2, 3.28.0-2), 
libedata-book-1.2-25:amd64 (3.26.5-2, 3.28.0-2), libedata-cal-1.2-28:amd64 
(3.26.5-2, 3.28.0-2)
End-Date: 2018-03-31  09:01:52

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

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

Versions of packages evolution-data-server depends on:
ii  evolution-data-server-common  3.28.0-2
ii  gnome-keyring 3.28.0.1-1
ii  libc6 2.27-2
ii  libcamel-1.2-61   3.28.0-2
ii  libdb5.3  5.3.28-13.1+b1
ii  libebackend-1.2-103.28.0-2
ii  libebook-1.2-19  3.28.0-2
ii  libebook-contacts-1.2-2   3.28.0-2
ii  libecal-1.2-193.28.0-2
ii  libedata-book-1.2-25  3.28.0-2
ii  libedata-cal-1.2-28   3.28.0-2
ii  libedataserver-1.2-23 3.28.0-2
ii  libgcr-base-3-1   3.28.0-1
ii  libgcr-ui-3-1 3.28.0-1
ii  libgdata220.17.9-2
ii  libglib2.0-0  2.56.0-4
ii  libgoa-1.0-0b 3.28.0-1
ii  libgtk-3-03.22.29-2
ii  libgweather-3-15  3.28.1-1
ii  libical3  3.0.1-5
ii  libldap-2.4-2 2.4.45+dfsg-1
ii  libpango-1.0-01.42.0-1
ii  libsecret-1-0 0.18.5-6
ii  libsoup2.4-1  2.62.0-1
ii  libxml2   2.9.4+dfsg1-6.1

evolution-data-server recommends no packages.

Versions of packages evolution-data-server suggests:
ii  evolution  3.28.0-3

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#853726: please put wiki in a -doc package

[Wookey]

So, Phil Sargent fettled the tunnel wiki to be properly standalone. I
tidied up some more cruft, but the result is still 34MB. I'm not
convinced that the 250K tunnelx package should be expanded to 34MB
just for the docs. It could be greatly shrunk by diligent de-crufting
and removing the multiple versions of each page ('talk', 'discussion'
'' '' etc), old images, Special+foo pages etc, but
that's a fair amount of work.

Putting the text back online might be a better use of that time. 

On the other hand if you know of a good tool for munging the set of
pages to remove all those links and pages to make some thing which is
just the core, then I may have a go to see if it can be got down to a
more sensible size.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#894481: numlockx: `laptop-detect` has moved from /usr/sbin to /usr/bin

[Unit 193]

Package: numlockx
Severity: normal

Dear Maintainer,

In debian/55numlockx (on installed systems, /etc/X11/Xsession.d/55numlockx) you 
call /usr/sbin/laptop-detect, but in version 0.14 of laptop-detect the binary 
was moved from /usr/sbin to /usr/bin thus rendering the check unable to 
complete.


~Unit 193
Unit193 @ freenode
Unit193 @ OFTC


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

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

Versions of packages numlockx depends on:
ii  libc6 2.27-2
ii  libx11-6  2:1.6.5-1
ii  libxext6  2:1.3.3-1+b2
pn  libxtst6  

numlockx recommends no packages.

Versions of packages numlockx suggests:
pn  x-display-manager  

Bug#894325: Bug resolved - upstream issue.

[Stefan Blachmann]

FYI:
My investigation turned out that it was indeed an upstream problem of libinput.
https://bugs.freedesktop.org/show_bug.cgi?id=105830
So this report against xinput can be closed as invalid/upstream.

Bug#891486: ITP: pipenv -- python development workflow for humans

[陳昌倬]

On Fri, Mar 30, 2018 at 06:28:47PM +0200, Bastian Venthur wrote:
> Dear ChangZhuo Chen,
> 
> I'm terribly sorry, I just realized that you've already filled an ITP
> for pipenv while I worked on that package too and uploaded it into
> unstable today.

No problem at all.

> Please feel free to take over the package or co-maintain it with me and
> the PAPT.

I think co-maintain in PAPT is good for me.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#894480: ps.1: Some tidying of the manual

[Bjarni Ingi Gislason]

Package: procps
Version: 2:3.3.12-4
Severity: minor
Tags: patch

Dear Maintainer,

  the patch is in the attachment.

Input file is ps.1

Test nr. 2:

Enable and fix warnings from 'test-groff'.

:152 (macro BR): only 1 argument, but more are expected

chk_manuals: Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  and

Test nr. 15:

Change the name of a macro for two fonts (e.g., BR and IR) to one letter,
if there is only one argument.
Add the second argument if needed.  It is sometimes part of the first one.

152:.BR a

#


Test nr. 8:

Protect a full stop (.) with "\&", if it has a blank (white-space) in front
of or (ignoring transparent characters to the full stop) after it, and it does
not mean an end of a sentence.

967:format (e.g. with option

#

Test nr. 20:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them.
[1] man-pages(7)

30:\fBps\fR [\fIoptions\fR]
234:Identical to \fB\-\-pid\ \fI123\fR.
237:Identical to \fB\-\-pid\ \fI123\fR.
318:for the pids listed in the \fIpidlist\fR and doesn't apply
498:\fB\-o\ pid,\:\fIformat\fB,\:state,\:tname,\:time,\:command\fR or
499:\fB\-o\ pid,\:\fIformat\fB,\:tname,\:time,\:cmd\fR,
629:[\fB+\fR|\fB\-\fR]\fIkey\fR[,[\fB+\fR|\fB\-\fR]\fIkey\fR[,...]].
674:\fBO\fR[\fB+\fR|\fB\-\fR]\fIk1\fR[,[\fB+\fR|\fB\-\fR]\fIk2\fR[,...]].
697:[\fB+\fR|\fB\-\fR]\fIkey\fR[,[\fB+\fR|\fB\-\fR]\fIkey\fR[,...]].  Choose a
740:\fIs\fRimple,
741:\fIl\fRist,
742:\fIo\fRutput,
743:\fIt\fRhreads,
744:\fIm\fRisc or
745:\fIa\fRll.
805:will assume you really meant "\fBps\fR \fIaux\fR".
1864:Cancel \fBCMD_ENV\fR=\fIirix\fR non\-standard behavior.

#

Test nr. 24:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

116:.B ps\ -ejH
121:.B ps\ -eLf
126:.B ps\ -eo euser,ruser,suser,fuser,f,comm,label
130:.B ps\ -eM
529:.B ps -o pid=X,\:comm=Y
794:column, the username will be truncated. See the -o and -O formatting

#

Test nr. 27:

Split lines longer than 80 characters into two or more
lines.  Apropriate break points are the end of a sentence or subordinate
clause.

ps.1: line 315  length 90
ps.1: line 746  length 82
ps.1: line 1305 length 87
ps.1: line 1352 length 87
ps.1: line 1356 length 87
ps.1: line 1429 length 87
ps.1: line 1723 length 81
ps.1: line 1777 length 87
ps.1: line 1781 length 87

#

Test nr. 28:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

84:environment variable. The use of BSD\-style options will also change the
319:additional filtering rules. The order of pids is unsorted
320:and preserved. No additional selection options, sorting
432:Do full\-format listing. This option can be combined with many other
794:column, the username will be truncated. See the -o and -O formatting
967:format (e.g. with option
1016:command with all its arguments as a string. Modifications to the arguments
1070:processor utilization. Currently, this is the integer value of the percent
1305:Unique inode number describing the namespace the process belongs to. See 
namespaces(7).
1352:Unique inode number describing the namespace the process belongs to. See 
namespaces(7).
1356:Unique inode number describing the namespace the process belongs to. See 
namespaces(7).
1360:nice value. This ranges from 19 (nicest) to \-20 (not nice to others),
1398:mask of the pending signals. See
1429:Unique inode number describing the namespace the process belongs to. See 
namespaces(7).
1777:Unique inode number describing the namespace the process belongs to. See 
namespaces(7).
1781:Unique inode number describing the namespace the process belongs to. See 
namespaces(7).
1843:Default output format override. You may set this to a format
1937:Michael K. Johnson

#

Test nr. 30:

Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust lengtxh of lines.

NO PATCH

2:.\" (The preceding line is a note to broken versions of man to tell
3:.\" Man page for ps.
4:.\" Quick hack conversion by Albert Cahalan, 1998.
5:.\" Licensed under version 2 of the Gnu General Public License.
6:.\"
8:.\"
9:.\" To render this page:
10:.\"groff -t -b -man -X -P-resolution -P100 -Tps ps.1 &
11:.\"groff -t -b -man -X -TX100 ps.1 &
12:.\"tbl ps.1 | troff -Ww -man -z
13:.\"groff -t -man -Tps ps.1 | ps2pdf - - > ps.pdf
14:.\"
15:.\" Ragged-right text.
17:.\" Disable hyphenation.
19:.\"
20:.\" ColSize is used for the format spec table.
21:.\" It's the left margin, minus the right, minus
22:.\" the space needed for the 1st two columns.
23:.\" Making it messy: inches, 

Bug#894479: python3-distutils: Overwrites files from another packages

[Michael Rasmussen]

Package: python3-distutils
Version: 3.6.5-1
Severity: serious
Justification: Policy 7.6.1

Dear Maintainer,

dpkg: error processing archive 
/var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also 
in package libpython3.6-stdlib:amd64 3.6.5-1

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.

Bug#893606: ntpsec: Please build with --enable-leap-smear

[Richard Laager]

The leap smearing in NTPsec is:
1) Broken.
2) Not Google compatible. It occurs in the interval _before_ the leap
second, not _centered on_ the leap second as Google has proposed.

#1 is specific to NTPsec. I submitted a Merge Request to fix this plus
some whitespace inconsistencies I found while debugging:
https://gitlab.com/NTPsec/ntpsec/merge_requests/671

#2 is inherited from NTP Classic, so I filed bugs on both:
https://gitlab.com/NTPsec/ntpsec/issues/475
http://bugs.ntp.org/show_bug.cgi?id=3481

Given that leap smearing seems to be converging on Google's approach,
I'm very hesitant to enable this feature when it is incompatible.

-- 
Richard

Bug#884284: NFSv4 buggy

[Daniel Smolik]

Dear Maintainer,
I have the same experience with NFSv4. My customer run PHP7/laravel application 
on server which I maintain. I put data directory  with pictures and caches to 
NFSv4.
 Log is filled with   nfs4_reclaim_open_state: Lock reclaim failed! and after 
while system is unusable I can login with ssh but apache don't serve any pages 
with strace I cann't see anything.
Only reboot helps. I try upgrade to 4.14.31 and still the same. Only help is 
switch to NFSv4 local_lock=all.

Regards
Dan Smolik



--
Mydatex s r.o.
http://www.mydatex.cz
email: smo...@mydatex.cz
mob: 604200362

Bug#894478: RM: ruby-debugger-ruby-core-source -- ROM; deprecated, useless

[Antonio Terceiro]

Package: ftp.debian.org
Severity: normal

Please remove ruby-debugger-ruby-core-source from the Debian archive.

The package is is fundamentally useless. ruby-rblineprof, the only
package that used to depend on it would only need it if running under
Ruby 2.0 or ealier, and we are past that point in Debian for some time
(oldstable has Ruby 2.1).  I have just uploaded ruby-rblineprof with
such dependency removed.

It also contains a hardcoded build-dependency on ruby2.3-dev, which is
currently a blocker for the removal of ruby2.3 -- we moved on to ruby2.3
for buster.


signature.asc
Description: PGP signature

Bug#893488: gnome-shell 3.28 crashes on Radeon R9: Failed to create texture 2d due to size/format constraints

[Matteo Settenvini]

Thanks Simon,

I finally got round to re-install the packages that are crashing for me (by
the way, this seem to happen roughly the same on another computer of mine,
which has a nVidia graphics card).
I have no gnome-shell extensions enabled. I am using the stock Adwaita
theme. I saved the original core dump, it is about 11 MB compressed. If it
can be helpful, I can send it to you.
The crashes happen only under Wayland. Running under Xorg seems fine.

Here is a full backtrace for all threads, it crashes in thread 21374
("Thread 1"):


Thread 28 (Thread 0x7f2ba891f700 (LWP 21388)):
#0  0x7f2bde9ca4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x565160998954) at ../sysdeps/unix/sysv/linux/
futex-internal.h:88
#1  0x7f2bde9ca4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x565160998900, cond=0x565160998928) at pthread_cond_wait.c:502
#2  0x7f2bde9ca4ec in __pthread_cond_wait (cond=cond@entry=0x565160998928,
mutex=mutex@entry=0x565160998900) at pthread_cond_wait.c:655
#3  0x7f2bb9bf926b in cnd_wait (mtx=0x565160998900,
cond=0x565160998928) at ../../../include/c11/threads_posix.h:159
#4  0x7f2bb9bf926b in util_queue_thread_func
(input=input@entry=0x5651609a8fe0)
at ../../../src/util/u_queue.c:171
#5  0x7f2bb9bf9187 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#6  0x7f2bde9c45aa in start_thread (arg=0x7f2ba891f700) at
pthread_create.c:463
#7  0x7f2bde6f9cbf in clone () at ../sysdeps/unix/sysv/linux/
x86_64/clone.S:95

Thread 27 (Thread 0x7f2b71ffb700 (LWP 21438)):
#0  0x7f2bde9ca4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x5651607204bc) at ../sysdeps/unix/sysv/linux/
futex-internal.h:88
#1  0x7f2bde9ca4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x56516072d620, cond=0x565160720490) at pthread_cond_wait.c:502
#2  0x7f2bde9ca4ec in __pthread_cond_wait (cond=0x565160720490,
mutex=0x56516072d620) at pthread_cond_wait.c:655
#3  0x7f2bd64c83c4 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#4  0x7f2bd64c8615 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#5  0x7f2bd68c3da5 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#6  0x7f2bd68e45d2 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#7  0x7f2bde9c45aa in start_thread (arg=0x7f2b71ffb700) at
pthread_create.c:463
#8  0x7f2bde6f9cbf in clone () at ../sysdeps/unix/sysv/linux/
x86_64/clone.S:95

Thread 26 (Thread 0x7f2b6fff7700 (LWP 21442)):
#0  0x7f2bde9ca4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x5651607204b8) at ../sysdeps/unix/sysv/linux/
futex-internal.h:88
#1  0x7f2bde9ca4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x56516072d620, cond=0x565160720490) at pthread_cond_wait.c:502
#2  0x7f2bde9ca4ec in __pthread_cond_wait (cond=0x565160720490,
mutex=0x56516072d620) at pthread_cond_wait.c:655
#3  0x7f2bd64c83c4 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#4  0x7f2bd64c8615 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#5  0x7f2bd68c3da5 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#6  0x7f2bd68e45d2 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#7  0x7f2bde9c45aa in start_thread (arg=0x7f2b6fff7700) at
pthread_create.c:463
#8  0x7f2bde6f9cbf in clone () at ../sysdeps/unix/sysv/linux/
x86_64/clone.S:95

Thread 25 (Thread 0x7f2baa7fc700 (LWP 21385)):
#0  0x7f2bde9ca4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x5651607a20d8) at ../sysdeps/unix/sysv/linux/
futex-internal.h:88
#1  0x7f2bde9ca4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5651607a2088, cond=0x5651607a20b0) at pthread_cond_wait.c:502
#2  0x7f2bde9ca4ec in __pthread_cond_wait (cond=cond@entry=0x5651607a20b0,
mutex=mutex@entry=0x5651607a2088) at pthread_cond_wait.c:655
#3  0x7f2bb9bf926b in cnd_wait (mtx=0x5651607a2088,
cond=0x5651607a20b0) at ../../../include/c11/threads_posix.h:159
#4  0x7f2bb9bf926b in util_queue_thread_func
(input=input@entry=0x5651607a59c0)
at ../../../src/util/u_queue.c:171
#5  0x7f2bb9bf9187 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#6  0x7f2bde9c45aa in start_thread (arg=0x7f2baa7fc700) at
pthread_create.c:463
#7  0x7f2bde6f9cbf in clone () at ../sysdeps/unix/sysv/linux/
x86_64/clone.S:95

Thread 24 (Thread 0x7f2b70ff9700 (LWP 21440)):
#0  0x7f2bde9ca4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x5651607204b8) at ../sysdeps/unix/sysv/linux/
futex-internal.h:88
#1  0x7f2bde9ca4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x56516072d620, cond=0x565160720490) at pthread_cond_wait.c:502
#2  0x7f2bde9ca4ec in __pthread_cond_wait (cond=0x565160720490,
mutex=0x56516072d620) at pthread_cond_wait.c:655
#3  0x7f2bd64c83c4 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#4  0x7f2bd64c8615 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#5  0x7f2bd68c3da5 in  () at /lib/x86_64-linux-gnu/libmozjs-52.so.0
#6  0x7f2bd68e45d2 in  () 

Bug#893488: gnome-shell 3.28 crashes on Radeon R9: Failed to create texture 2d due to size/format constraints

[Matteo Settenvini]

2018-03-26 21:00 GMT+02:00 Simon McVittie :

> Something is already going wrong with OpenGL drawing in gdm's gnome-shell,
> but unlike yours, it didn't crash.
>
> Did you notice that in GNOME Shell 3.28, you don't get the grey "noise"
> background texture that you should? In GNOME Shell 3.26, do you get the
> "noise" texture correctly?
>
> (This one:
> https://askubuntu.com/questions/534187/where-is-the-
> login-screen-wallpaper-for-gdm-stored)
>

​I forgot to add that I can see the "noise" wallpaper correctly in GDM,
however text is all garbled whenever shown at all (sometimes it is,
sometimes there is absolutely none displayed).​

​Cheers again,
Matteo​

Bug#894305: package build-depends on legacy ruby2.3-dev

[Antonio Terceiro]

On Thu, 29 Mar 2018 01:11:20 +0800 Matthias Klose  wrote:
> Package: src:ruby-debugger-ruby-core-source
> Version: 1.3.8+ds-1
> Severity: serious
> Tags: sid buster patch
> 
> the package build-depends on legacy ruby2.3-dev which is going to be removed. 
> Is
> there are reason not to use the unversioned b-d?
> 
> patch at
> http://launchpadlibrarian.net/362398716/ruby-debugger-ruby-core-source_1.3.8+ds-1_1.3.8+ds-1ubuntu1.diff.gz

I don't think this patch fixes anything.

This package is fundamentally broken and useless, and is in the archive
just to satisfy a pointless dependency. I did an entire analysis of the
situation back when this package is ITP'ed, but AFAICT I was completely
ignored:

https://lists.debian.org/debian-ruby/2017/09/msg00016.html

Now, we have a hardcoded dependency on ruby2.3-dev, which is a blocker
for the removal of ruby2.3.

I just made an upload of ruby-rblineprof removing the dependency on
ruby-debugger-ruby-core-source, and will request the removal of
ruby-debugger-ruby-core-source from the archive.


signature.asc
Description: PGP signature

Bug#894477: mariadb-server: systemctl /etc/mysql/my.cnf Permission denied, can not read con files

[Stefan Nitz]

Package: mariadb-server
Version: 10.1.26-0+deb9u1
Severity: normal

Dear Maintainer,

* What led up to the situation?
default debian netinst
install mariadb

* What exactly did you do (or not do) that was effective (or
 ineffective)?

need settings in *.cnf file(s)
f.e. 
[mysqld]
max_allowed_packet  = 128M

* What was the outcome of this action?
no *.cnf file settinsg ist used

* What outcome did you expect instead?
settings is used


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

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

Versions of packages mariadb-server depends on:
ii  mariadb-server-10.1  10.1.26-0+deb9u1

mariadb-server recommends no packages.

mariadb-server suggests no packages.

-- no debconf information

Bug#893353: libinline-java-perl FTBFS with openjdk-9

[gregor herrmann]

On Fri, 30 Mar 2018 17:12:20 +0200, Emmanuel Bourg wrote:

> Control: fixed -1 0.63-1
> Control: close -1
> 
> I confirm this is now fixed in unstable.

Thanks, seems we missed to close this bug in two subsequent uploads :/

BTW, do you have an idea why 0.63-1 and 0.64-1 don't build on armel?

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 VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Leonard Cohen: I tried to leave you


signature.asc
Description: Digital Signature

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Thomas Preud'homme]

Package: qtbase5-dev-tools
Version: 5.9.2+dfsg-12
Severity: wishlist
Tags: upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain

Hi,

While investigating ultracopier's lack of build reproducibility, I found
out that rcc encodes the timestamp of the files the QRC file being
compiled references (see end of RCCFileInfo::writeDataInfo()). This
becomes a problem for generated files because the output of rcc is then
different in 2 different builds. It would be nice if rcc had an option
to encode a stable timestamp, eg. EPOCH.

Best regards,

Thomas

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

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

Versions of packages qtbase5-dev-tools depends on:
ii  libc62.27-2
ii  libgcc1  1:8-20180321-1
ii  libqt5core5a [qtbase-abi-5-9-2]  5.9.2+dfsg-12
ii  libqt5dbus5  5.9.2+dfsg-12
ii  libstdc++6   8-20180321-1
ii  perl 5.26.1-5
ii  qtchooser64-ga1b6736-5
ii  zlib1g   1:1.2.8.dfsg-5

qtbase5-dev-tools recommends no packages.

qtbase5-dev-tools suggests no packages.

-- no debconf information

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

[Richard Laager]

I did some testing just now.

I've updated ntpsec.postrm in git. I dropped the unnecessary LANG=C on
the first check, updated the style of the "then" statement, and most
importantly, moved the deluser inside the "! dpkg -s ntp" block:

if ! dpkg -s ntp > /dev/null 2>&1; then
rm -rf /var/lib/ntp/
rm -rf /var/log/ntpstats/
if ! LANG=C dpkg -s ntpsec-ntpviz 2> /dev/null | \
 grep -qE "^Status: (hold|install)"; then
deluser --system --quiet ntp || true
fi
fi

Here is the equivalent diff for ntp, which I have tested and confirmed:

diff --git a/debian/ntp.postrm b/debian/ntp.postrm
index d959aa5..7ec4b6b 100644
--- a/debian/ntp.postrm
+++ b/debian/ntp.postrm
@@ -25,7 +25,12 @@ installinit_error() {
 #DEBHELPER#

 if [ "$1" = "purge" ]; then
-   deluser --system --quiet ntp || true
-   rm -rf /var/lib/ntp/
-   rm -rf /var/log/ntpstats/
+   if ! dpkg -s ntpsec > /dev/null 2>&1; then
+   rm -rf /var/lib/ntp/
+   rm -rf /var/log/ntpstats/
+   if ! LANG=C dpkg -s ntpsec-ntpviz 2> /dev/null | \
+grep -qE "^Status: (hold|install)"; then
+   deluser --system --quiet ntp || true
+   fi
+   fi
 fi

If this coordination is acceptable, I believe it solves the various
interactions. I'm happy to test more scenarios if anyone thinks I missed
something.

If this coordination is not acceptable, I'm open to alternative suggestions.

-- 
Richard

Bug#894456:

[Scott Arciszewski]

Does apt-get autoremove -f followed by apt-get dist-upgrade help?

Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises 

Bug#893182: Pending fixes for bugs in the cmdreader package

[pkg-java-maintainers]

tag 893182 + pending
thanks

Some bugs in the cmdreader package are closed in revision
5ba205e4f57f32d64f2ebfaf2e9bd71d803afe3d in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/cmdreader.git/commit/?id=5ba205e

Commit message:

Fixed the build failure with Java 9 (Closes: #893182)

Bug#894471: gegl: libbabl-dev build dependency should be raised to (>= 0.1.44)

[Jeremy Bicha]

Control: tags -1 +pending

On Fri, Mar 30, 2018 at 4:18 PM, Adrian Bunk  wrote:
> Requested 'babl >= 0.1.44' but version of babl is 0.1.42

Already fixed in git:

https://salsa.debian.org/gnome-team/gegl/commit/6e4cb4e5

Thanks,
Jeremy Bicha

Bug#894474: RFS: keystone-engine/0.9.1-1 [ITP]

[Christian Sharpsten]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "keystone-engine"

* Package name: keystone-engine
  Version : 0.9.1-1
  Upstream Author : Nguyen Anh Quynh 
* URL : http://www.keystone-engine.org/
* License : GPL-2
  Section : devel

It builds those binary packages:

  keystone-engine - Multi-architecture assembler framework
  libkeystone-engine-dev - Multi-architecture assembler framework - development 
files
  libkeystone-engine0 - Multi-architecture assembler framework - shared library
  python3-keystone-engine - Multi-architecture assembler framework - Python 
bindings

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

  https://mentors.debian.net/package/keystone-engine

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

  dget -x 
https://mentors.debian.net/debian/pool/main/k/keystone-engine/keystone-engine_0.9.1-1.dsc

More information about keystone-engine can be obtained from: 
https://salsa.debian.org/csharpsten-guest/keystone-engine

Changes since the last upload:
  * Initial release. Closes: #893580

--
Christian Sharpsten

Bug#891267: man-db: i386 or x32 mandb doesn't work due to seccomp filter

[Colin Watson]

On Mon, Feb 26, 2018 at 05:54:39AM +0100, Mikulas Patocka wrote:
> x32 is faster than amd64, so I am running Debian-amd64-sid with x32 
> foreign architecture and with x32 dash, gcc and other packages.

Hm, OK.  I mean, you could always just make sure that everything man
needs to call matches, but I guess that's a bit fiddly.  Fixed upstream,
and will be in 2.8.3:

  
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=770cd67aaf711b2cded9cbc2f9e503ca0f5e73ba

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

Bug#893197: jfractionlab FTBFS with openjdk-9

[Emmanuel Bourg]

Control: tags -1 + patch

This is easily fixed by modifying the javac arguments in debian/rules:


--- a/debian/rules
+++ b/debian/rules
@@ -13,7 +13,7 @@ build-arch: build-stamp

 build-indep: build-stamp

-JAVA_ARGS=-source 1.5 -target 1.5
+JAVA_ARGS=-source 1.8 -target 1.8 -encoding ISO-8859-1

 build-stamp:
dh_testdir

Bug#889940: stretch-pu: package miniupnpd/1.8.20140523-4.1 fix for CVE-2017-1000494

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 17:35 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2018-02-09 at 00:15 +0100, Thomas Goirand wrote:
> > I'd like to push for an update of miniupnpd in Stretch, in order to
> > fix
> > CVE-2017-1000494. The security team decided to go without a DSA.
> > 
> > Attached is the debdiff for the fix.
> 
> Please go ahead.
> 

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#885333: stretch-pu: package loook/0.8.4-1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-02-23 at 18:06 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> Apologies for the delay in getting back to you.
> 
> On Tue, 2017-12-26 at 19:51 +0100, Mechtilde Stehmann wrote:
> > Hello,
> > 
> > I discussed my wish also with wRAR at IRC #debian-mentors. He
> > pointed
> > out to me that my versioning was wrong.
> > 
> > So I correct it a new build and a new patch file which i applied.
> 
> +loook (0.8.4-1+deb9u1) UNRELEASED; urgency=medium
> 
> To confirm, this will want to be "stretch" for the upload.

Uploaded and flagged for acceptance.

> +  * now it is possible to search in directories which also contains
> password protected files.
> ++ fix for bug #884582
> 
> So "Closes: #884582" then.

Although without that fix, apparently.

Regards,

Adam

Bug#894467: Pending fixes for bugs in the cdk package

[pkg-java-maintainers]

tag 894467 + pending
thanks

Some bugs in the cdk package are closed in revision
bb95a0e195f752b494b6f1d7dc79d950dfa24372 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/cdk.git/commit/?id=bb95a0e

Commit message:

Fixed the build failure with Ant 1.10 (Closes: #894467)

Bug#894473: prodigal FTBFS on armel/armhf: Build killed with signal TERM after 150 minutes of inactivity

[Adrian Bunk]

Source: prodigal
Version: 1:2.6.3-1
Severity: serious
Tags: buster sid patch

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

...
E: Build killed with signal TERM after 150 minutes of inactivity


On armhf gcc needs 6.5 hours (sic) to compile training.c

This can be workarounded with the attached patch plus the
following debian/rules change:

--- debian/rules.old2018-03-27 16:19:52.842571587 +
+++ debian/rules2018-03-27 16:21:55.221340424 +
@@ -3,6 +3,15 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+include /usr/share/dpkg/architecture.mk
+
+ifneq (,$(filter $(DEB_HOST_ARCH), armel armhf))
+  export DEB_CFLAGS_MAINT_APPEND = -O1
+else
+  export DEB_CFLAGS_MAINT_APPEND = -O3
+endif
+
+
 CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
 LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
 CFLAGS+=$(HARDENING_CFLAGS)
Description: Stop overwriting the optimization with -O3
Author: Adrian Bunk 

--- prodigal-2.6.3.orig/Makefile
+++ prodigal-2.6.3/Makefile
@@ -21,7 +21,7 @@
 SHELL   = /bin/sh
 CC  = gcc
 
-CFLAGS  += -pedantic -Wall -O3
+CFLAGS  += -pedantic -Wall
 LFLAGS = -lm $(LDFLAGS)
 
 TARGET  = prodigal

Bug#894471: gegl: libbabl-dev build dependency should be raised to (>= 0.1.44)

[Adrian Bunk]

Source: gegl
Version: 0.3.30-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gegl=s390x=0.3.30-1=1522190230=0

...
checking for BABL... no
configure: error: Package requirements (babl >= 0.1.44) were not met:

Requested 'babl >= 0.1.44' but version of babl is 0.1.42

Bug#894472: libqt5waylandclient5-dev: Missing QtWayland private headers

[Pier Luigi Fiorini]

Package: libqt5waylandclient5-dev
Version: 5.10.1-2
Severity: normal

Dear Maintainer,

Please include both QtWaylandClient and QtWaylandCompositor private headers
as they might be used by other software.

Looks like they are removed on purpose:

https://salsa.debian.org/qt-kde-team/qt/qtwayland/blob/master/debian/rules#L33

but people writing custom Wayland protocol implementations sometimes need them
not to mention client extensions that can only be implemented using private
headers.

Other Qt modules provide private headers in Debian, I don't see why
QtWayland doesn't.



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

Kernel: Linux 4.15.0-2-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)
LSM: AppArmor: enabled

Versions of packages libqt5waylandclient5-dev depends on:
ii  libqt5waylandclient5  5.10.1-2

Versions of packages libqt5waylandclient5-dev recommends:
ii  qtwayland5-dev-tools  5.10.1-2

libqt5waylandclient5-dev suggests no packages.

-- no debconf information

Bug#894456: python3-distutils: trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also in package libpython3.6-stdlib

[Mark Kim]

Heya,

My apt fails to build python3-distutils as well:

dpkg: error processing archive
/var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is
also in package libpython3.6-stdlib:amd64 3.6.5-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm running buster/sid with the 4.15.0-2-amd64 kernel.

All the best,
Mark

On Fri, 30 Mar 2018 17:26:11 +0200 Jochen Sprickerhof
 wrote:
> Package: python3-distutils
> Version: 3.6.5~rc1-3
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> with todays update I get:
>
> # apt-get -f install python3-distutils
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be upgraded:
>   python3-distutils
> 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> Need to get 0 B/147 kB of archives.
> After this operation, 28.7 kB of additional disk space will be used.
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> Reading changelogs... Done
> (Reading database ... 63950 files and directories currently installed.)
> Preparing to unpack .../python3-distutils_3.6.5-1_all.deb ...
> Unpacking python3-distutils (3.6.5-1) over (3.6.5~rc1-3) ...
> dpkg: error processing archive
/var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack):
>  trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is
also in package libpython3.6-stdlib:armhf 3.6.5-1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Could you please fix this?
>
> Thanks
>
> Jochen
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: armhf (armv7l)
>
> Kernel: Linux 4.15.0-2-armmp (SMP w/8 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages python3-distutils depends on:
> ii  python3  3.6.5~rc1-1
> ii  python3-lib2to3  3.6.5-1
>
> python3-distutils recommends no packages.
>
> python3-distutils suggests no packages.
>
> -- debconf-show failed
>
-- 
Mark Hyun-ki Kim | em...@markhkim.com / markh...@acm.org / markh...@nasw.org
 | @markhkim  | markhkim.com

Bug#894325: Bug is deeper, not in xinput, but in libinput

[Stefan Blachmann]

After looking into the stuff I see that the issue is somewhere deeper.
See also http://forums.debian.net/viewtopic.php?f=6=137104
Looks like that the regression is possibly caused by libinput:

https://github.com/wayland-project/libinput/blob/master/src/evdev.c

In particular this
https://github.com/wayland-project/libinput/blob/master/src/evdev.c#L589
(and following)
and this
https://github.com/wayland-project/libinput/blob/master/src/libinput.c#L3901
(and following)
looks odd to me when taking a first glimpse.

My feeling is that there is something foul.

Bug#894470: [readline-common] Consider turning on enable-bracketed-paste

[Michal]

Package: readline-common
Version: 7.0-3
Severity: normal

Please consider turning 

set enable-bracketed-paste on

by default. This at least partially mitigates the unwanted copy side 
effects.

Example of the exploit http://thejh.net/misc/website-terminal-copy-paste

Bug#894469: crystalhd FTBFS with gstreamer 1.14

[Adrian Bunk]

Source: crystalhd
Version: 1:0.0~git20110715.fdd2f19-12
Severity: serious
Tags: buster sid

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

...
   dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/gstreamer1.0-crystalhd/DEBIAN/symbols doesn't 
match completely debian/gstreamer1.0-crystalhd.symbols
--- debian/gstreamer1.0-crystalhd.symbols 
(gstreamer1.0-crystalhd_1:0.0~git20110715.fdd2f19-12_amd64)
+++ dpkg-gensymbols6DFYtG   2018-03-27 02:03:46.576676217 -1200
@@ -1,3 +1,5 @@
 libgstbcmdec.so gstreamer1.0-crystalhd #MINVER#
  gst_bcm_dec_get_type@Base 1:0.0~git20110715.fdd2f19
- gst_plugin_desc@Base 1:0.0~git20110715.fdd2f19
+ gst_plugin_bcmdec_get_desc@Base 1:0.0~git20110715.fdd2f19-12
+ gst_plugin_bcmdec_register@Base 1:0.0~git20110715.fdd2f19-12
+#MISSING: 1:0.0~git20110715.fdd2f19-12# gst_plugin_desc@Base 
1:0.0~git20110715.fdd2f19
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:11: binary] Error 2


Debug symbols for a plugin???

Bug#880501: +1

[Christian Grothoff]

"reproduced" bug, by accident. As the original reporter describes, there
was a libpam update in my recent history. As well as a full hard drive
(explaining the write failure). Re-running pam-auth-update resolved the
situation.



signature.asc
Description: OpenPGP digital signature

Bug#893970: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2018d

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-03-30 at 14:45 +0200, gregor herrmann wrote:
> On Fri, 30 Mar 2018 02:09:18 +0100, Adam D. Barratt wrote:
> 
> > On Sat, 2018-03-24 at 19:26 +0100, gregor herrmann wrote:
> > > I've prepared an update for libdatetime-timezone-perl in jessie
> > > incorporating the Olson db 2018d version. As usual as a quilt
> > > patch
> > > only touching the data files.
> > 
> > Please go ahead.
> 
> Thanks; uploaded.
> 

Flagged for acceptance.

Regards,

Adam

Bug#893971: stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2018d

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2018-03-30 at 14:45 +0200, gregor herrmann wrote:
> On Fri, 30 Mar 2018 02:09:42 +0100, Adam D. Barratt wrote:
> 
> > On Sat, 2018-03-24 at 19:26 +0100, gregor herrmann wrote:
> > > I've prepared an update for libdatetime-timezone-perl in stretch
> > > incorporating the Olson db 2018d version. As usual as a quilt
> > > patch
> > > only touching the data files.
> > 
> > Please go ahead.
> 
> Thank you! Uploaded.

Flagged for acceptance into p-u.

I'm hoping to get SUAs for this and tzdata sorted out over the weekend.

Regards,

Adam

Bug#881871: [pkg-bacula-devel] Bug#881871: stretch-pu: package bacula/7.4.4+dfsg-6

[Sven Hartge]

On 30.03.2018 18:03, Julien Cristau wrote:
> On Sun, Mar  4, 2018 at 11:08:00 +0100, Carsten Leonhardt wrote:
> 
>> Control: tags -1 - moreinfo
>>
>> "Adam D. Barratt"  writes:
>>
>>> -   --oknodo --exec $DAEMON --chuid $BUSER:$BGROUP -- -c $CONFIG
>>> +   --oknodo --exec $DAEMON -- -g $BUSER -g $BGROUP -c $CONFIG
>>>
>>> The first of those "-g" is presumably supposed to be "-u". I realise
>>> this may seem a small point, but it does make me wonder how it wasn't
>>> caught in testing.
>>
>> Thank you for your work and for catching this. A new version of the
>> patch is attached.
>>
> This leaves open the question of how much was this tested.  Can you
> describe what has or hasn't been done there?

I tested the proposed packages in a SysV-Init-based Debian Stretch VM. I
can confirm every daemon runs as the user and group it is supposed to
run as.

root@debian-stretch:~# ps auwwx | grep [b]acula
root  5101  0.0  0.2  66988  5512 ?Ssl  21:16   0:00
/usr/sbin/bacula-fd -u root -g root -c /etc/bacula/bacula-fd.conf
bacula5175  0.0  0.2 130420  5384 ?Ssl  21:16   0:00
/usr/sbin/bacula-sd -u bacula -g tape -c /etc/bacula/bacula-sd.conf
bacula5403  0.0  0.3  74728  6628 ?Ssl  21:20   0:00
/usr/sbin/bacula-dir -u bacula -g bacula -c /etc/bacula/bacula-dir.conf

root@debian-stretch:~# ps -eo pid,comm,euser,supgrp | grep [b]acula
 5101 bacula-fd   root root
 5175 bacula-sd   bacula   tape
 5403 bacula-dir  bacula   tape,bacula

I also checked why I did not notice the problem Adam spotted in the
first place. I can only guess this happened because bacula-dir fell back
to running as "root" when no "-u bacula" was specified, which made all
my tests work as they should (because root has obviously no restrictions).

The reason for this fallback is the Debian package does not specify a
runtime user at build time. This was done in the past so that the
runtime user can be chosen by the admin of the system.

But since then we changed the packaging and got rid of this ability
because in reality nobody was doing this anyway and it complicated the
packaging.

If the runtime user were set during package build, this problem would
not have occurred because the parameters -u and -g wouldn't be needed in
the first place.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature

Bug#882238: [Cupt-devel] Bug#882238: Bug#882238: cupt: FTBFS on hppa and hurd-i386: feeding-input.t fails

[Eugene V. Lyubimkin]

Control: tags -1 + pending

Hi Dave,

On 30.03.2018 19:41, John David Anglin wrote:
> [...]
> The attached change fixed the build failure on my rp3440.  Don't know if 60s 
> is enough for the slower buildds.

Thank you for investigation. It's good to know that the current timeout buffer
just isn't large enough. It's interesting that, judging from the last buildd 
log,
for a particularly CPU-intense case the slowdown versus my desktop was only 5x,
but the more I/O-bound failing case didn't cut it despite a 20x buffer.

I'll increase the timeout to 90s in the next upload, and see if that works 
better
for buildds.


Regards,
-- 
Eugene V. Lyubimkin aka JackYF
C++ GNU/Linux userspace developer, Debian Developer

Bug#894441: dpkg-buildpackage: SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries. Breaks M-A:same

[Sven Joachim]

On 2018-03-30 15:02 +0100, Chris Lamb wrote:

> [adding 894441@ to CC]
>
> Hi Jean-Michel,
>
>> Filled as #894441
>> https://bugs.debian.org/894441
>
> Thanks for this. I was just briefly wondering whether this is related to:
>
>   https://lists.debian.org/debian-security/2017/05/msg00011.html

It seems so.  What you are describing there had been noticed by Ian
Jackson before:

https://lists.debian.org/debian-devel/2016/11/msg00328.html

Ian then filed bug #843773 against sbuild, and as a result sbuild (as of
version 0.73.0-1) no longer reuses the timestamp of the last changelog
entry in binNMUs.

The same version of sbuild introduced a --binNMU-timestamp option, and I
think wanna-build should use it to achieve a consistent
SOURCE_DATE_EPOCH across architectures in binNMUs.  Something along
these lines had already been proposed in #843773.

Cheers,
   Sven

Bug#889669: nvidia-graphics-drivers: solve the upgrade problem

[Luca Boccassi]

On Mon, 2018-03-26 at 18:45 +0200, Philipp Kern wrote:
> Hi Luca,
> 
> On 3/21/18 2:01 PM, Luca Boccassi wrote:
> > Isn't this sort-of-like what Ubuntu does? IIRC they lump together
> > everything into a single package unlike we do, and they are named
> > after
> > the major revision.
> 
> let's say that even Ubuntu have not solved this problem because they
> don't consider the minor revision either, as suggested here.
> 
> I would like to understand better what the current set of packages
> helps
> with, though. It is true that I hadn't considered that you are
> shipping
> so many packages right now. However, you seem to also hardcode the
> dependencies between them with a lot of substvars in the packaging,
> which is understandable given the non-free nature of them. But at the
> same time it makes it more muddy as to what problem that solves.

Well that's the Debian policy - one shared library per package, that's
what we follow.

> At the same time I also did not consider libglvnd - I unfortunately
> was
> not aware of it. That at least in theory seems to be a nice way
> forward
> to just co-install multiple implementations. Is anyone other than
> NVidia
> supporting it at this point? But anyhow we'll live with the two
> options
> here if one of them is a regression, either in bugs or features,
> which
> seems to be the case here. Given that the two are not co-installable
> today anyway, collating the two options into two separate packages
> would
> work. But for that suggestion to make any sense I'd like to
> understand
> the current packaging first - as per the above.

Mesa does support glvnd, and ships with it in sid/buster. One day I'd
like to drop the non-glvnd one, but it would need a solution for
switchable graphics first (hopefully server-side glvnd in Xorg 1.20
will help with that, but can't say I have looked into it yet).

> The key idea is that the packages install their binaries into paths
> versioned with both major and minor revision and do not change while
> the
> machine is booted. Then we would need to juggle around some symlinks
> based off the module version exposed in sysfs on boot. The
> constraints
> here are doing that after the module is loaded and /usr is made
> available and before X(/Wayland?) starts. It does seem a little messy
> with systemd, that's true. We'd likely end up needing this to be
> included in basic.target. With sysvinit rcS would work. If the nvidia
> module is included in the initrd for KMS - which I think is the case?
> -
> udev wouldn't work as easily, just in addition. So I suppose it'd
> need
> one script that puts the symlink farm into the right state and then
> we
> need to sprinkle some hooks into the right places depending on when
> the
> module is loaded.

The modules are not in the initrd (weirdly, I thought they would), at
least on my desktop:

$ lsinitramfs /boot/initrd.img-4.9.0-6-amd64  | grep nvidia
lib/modules/4.9.0-6-amd64/kernel/drivers/net/ethernet/nvidia
lib/modules/4.9.0-6-amd64/kernel/drivers/net/ethernet/nvidia/forcedeth.ko
etc/modprobe.d/nvidia-kernel-common.conf
etc/modprobe.d/nvidia.conf
etc/modprobe.d/nvidia-blacklists-nouveau.conf
etc/nvidia
etc/nvidia/current
etc/nvidia/current/nvidia-modprobe.conf
etc/nvidia/current/nvidia-blacklists-nouveau.conf

> What kind of alternatives do we need to offer at this point? Mesa and
> NVidia? Can legacy drivers be co-installable? I'd intuitively prefer
> to
> have glvnd/non-glvnd be two non-co-installable packages. It'd be
> great
> if legacy drivers could be co-installable and then the right driver
> would be loaded, which is theoretically feasible. And Mesa needs to
> be
> co-installable. So it'd be nice if this would really boil down to
> just
> Mesa vs. NVidia on an alternatives level, unless I miss something.
> 
> Kind regards and thanks for all your replies so far!
> Philipp Kern

Yes, the legacy drivers (340xx and 304xx at the moment, although the
latter is out of support so I guess we'll drop it in buster) are co-
installable. There are update-alternatives for those too. We have a
script to make it easier to manage those and the glx provider (mesa,
fglrx, nvidia), it's update-glx from the update-glx package.

You can find the scripts and configs in the git repo:
https://salsa.debian.org/nvidia-team/glx-alternatives

-- 
Kind regards,
Luca Boccassi

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

Bug#894456: python3-distutils: trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also in package libpython3.6-stdlib

[oz]

Hi,

another user, with the same problem here! My work-around to finish an 
apt-get dist-upgrade today was to apt-get remove python3-distutils for 
the time being.


Freundliche Gruesse


On Fri, 30 Mar 2018 17:26:11 +0200 Jochen Sprickerhof 
 wrote:

Package: python3-distutils
Version: 3.6.5~rc1-3
Severity: grave
Justification: renders package unusable

Hi,

with todays update I get:

# apt-get -f install python3-distutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  python3-distutils
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/147 kB of archives.
After this operation, 28.7 kB of additional disk space will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 63950 files and directories currently installed.)
Preparing to unpack .../python3-distutils_3.6.5-1_all.deb ...
Unpacking python3-distutils (3.6.5-1) over (3.6.5~rc1-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also 
in package libpython3.6-stdlib:armhf 3.6.5-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Could you please fix this?

Thanks

Jochen


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

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

Versions of packages python3-distutils depends on:
ii  python3  3.6.5~rc1-1
ii  python3-lib2to3  3.6.5-1

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- debconf-show failed

Bug#889669: nvidia-graphics-drivers: solve the upgrade problem

[Luca Boccassi]

On Fri, 2018-03-23 at 14:54 +, Michael Schaller wrote:
> > I see. Perhaps a systemd unit with the appropriate precedences set
> > so
> > that it runs before X starts? And $something-$something for Sys-V I
> > guess :-)
> 
> The more I think about it maybe this shouldn't be handled by a
> service at
> boot but rather by udev. What do you think?

That would make it independent from the init system, so don't see why
not.
Haven't really played with with udev so can't propose a solution, but
can help test one.

> > Was worth a try :-) I must admit that lately, looking at the AMD
> > camp
> > with their in-tree kernel drivers and first-class support for Mesa
> > for
> > userspace, I am green with envy (ha!)
> 
> :-D
-- 
Kind regards,
Luca Boccassi

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

Bug#894367: wadc: JRE dependency should be default-jre | java8-runtime

[Jonathan Dowland]

Hi Adrian, thanks for the report.

On Thu, Mar 29, 2018 at 04:29:03PM +0300, Adrian Bunk wrote:

The JRE dependency is currently:
 openjdk-8-jre | java8-runtime

This should instead be:
 default-jre | java8-runtime

This would avoid apt preferring a non-default JRE
(currently openjdk-9-jre is the default).



Thanks. I think I originally wrote it like that back when 7 was default,
and WadC requires ≥ 8. I'll fix.


--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄

Bug#894388: affects corebird

[dann frazier]

On Thu, Mar 29, 2018 at 08:54:51PM +0100, Simon McVittie wrote:
> Control: reassign -1 libgtk-3-0 3.22.29-2
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/129
> 
> On Thu, 29 Mar 2018 at 11:47:12 -0600, dann frazier wrote:
> > affects 894388 + corebird
> 
> This seems very unlikely to be a gnome-terminal bug if you also get it
> for corebird. I'm guessing GDK or GTK+, which are in the same binary
> package so it doesn't really matter which one has the bug.
> 
> > #0  0x72018e79 in wl_proxy_marshal (proxy=0x0, opcode=0)
> > at ../src/wayland-client.c:692
> > #1  0x7fffe2e461b9 in ?? ()
> >from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
> 
> Please could you retry this backtrace with libgtk-3-0-dbgsym installed?

Sure:

(gdb) bt
#0  0x72018e79 in wl_proxy_marshal (proxy=proxy@entry=0x0, 
opcode=opcode@entry=0) at ../src/wayland-client.c:692
#1  0x7fffe2e461b9 in gtk_text_input_destroy (gtk_text_input=0x0)
at ../../../../../modules/input/gtk-text-input-client-protocol.h:498
#2  registry_handle_global_remove (data=0x55e652d0, 
registry=, id=)
at ../../../../../modules/input/imwayland.c:226
#3  0x7fffef1e8fce in ffi_call_unix64 ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#4  0x7fffef1e893f in ffi_call ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#5  0x7201bd8b in wl_closure_invoke (
closure=closure@entry=0x56e5f100, flags=flags@entry=1, 
target=, target@entry=0x55e65310, 
opcode=opcode@entry=1, data=) at ../src/connection.c:935
#6  0x72018928 in dispatch_event (
display=display@entry=0x55b20ae0, queue=)
at ../src/wayland-client.c:1310
#7  0x72019be4 in dispatch_queue (queue=0x55b20ba8, 
display=0x55b20ae0) at ../src/wayland-client.c:1456
#8  wl_display_dispatch_queue_pending (display=0x55b20ae0, 
queue=0x55b20ba8) at ../src/wayland-client.c:1698
#9  0x72019c3c in wl_display_dispatch_pending (display=)
at ../src/wayland-client.c:1761
#10 0x764e85c4 in _gdk_wayland_display_queue_events (
display=) at ../../../../../gdk/wayland/gdkeventsource.c:201
#11 0x76488fc0 in gdk_display_get_event (
display=display@entry=0x55b26110) at ../../../../gdk/gdkdisplay.c:438
#12 0x764e82f2 in gdk_event_source_dispatch (base=, 
callback=, data=)
at ../../../../../gdk/wayland/gdkeventsource.c:120
#13 0x751ef287 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x751ef4c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x751ef54c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x757afcbd in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#17 0x5556eb83 in _vala_main (args=, 
args_length1=) at main.c:50
#18 0x74beca87 in __libc_start_main (main=0x5556ea00 , 
argc=1, argv=0x7fffe178, init=, fini=, 
rtld_fini=, stack_end=0x7fffe168)
at ../csu/libc-start.c:310
#19 0x5556ea3a in _start ()

> I can't say for sure from the backtrace without debug symbols, but this
> looks a lot like  (but we
> thought we fixed that in 3.22.29-2) or
>  (which has a patch waiting
> for review upstream).

Let me know if you'd like me to test that, or any other patch.

   -dann

Bug#882238: [Cupt-devel] Bug#882238: cupt: FTBFS on hppa and hurd-i386: feeding-input.t fails

[John David Anglin]

On 2018-03-30 4:56 AM, Eugene V. Lyubimkin wrote:

Thank you for taking a look.

On 30.03.2018 01:01, John David Anglin wrote:
[...]

On hurd-i386, I tracked it down to a misbehaviour of timeout(1), reported as 
#894379.
For HPPA, I didn't see any available porterboxes for HPPA on db.debian.org, so 
I could not
reproduced it. Did I miss any?

I'll take a look at the timeout problem.  Access to a box can be arranged.

I find timeout works correctly on hppa.

I see, so it's a different issue then. Please let me know if/when there is a 
box I could
reproduce the test case failure on.
The attached change fixed the build failure on my rp3440.  Don't know if 
60s is enough for the slower buildds.


Dave

--
John David Anglin  dave.ang...@bell.net

--- ./test/t/manage/worker/packages/hooks/pre-install-pkgs/feeding-input.t.save 
2018-03-30 11:11:02.697750034 -0400
+++ ./test/t/manage/worker/packages/hooks/pre-install-pkgs/feeding-input.t  
2018-03-30 11:11:41.437969834 -0400
@@ -21,7 +21,7 @@
my ($comment, $hook_command, $checker) = @_;
 
my $hook_options = "-o dpkg::pre-install-pkgs::='$hook_command' ";
-   my $command = get_worker_command("timeout 30s $cupt", "install '*xyz*' 
$hook_options", 'simulate'=>0);
+   my $command = get_worker_command("timeout 60s $cupt", "install '*xyz*' 
$hook_options", 'simulate'=>0);
 
my $output;
subtest $comment => sub {

Bug#894467: cdk FTBFS with ant 1.10

[Adrian Bunk]

Source: cdk
Version: 1:1.2.10-6
Severity: serious
Tags: buster sid

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

...
BUILD FAILED
/build/1st/cdk-1.2.10/build.xml:203: This CDK release requires Ant 1.7.1 or 
better.

Total time: 3 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1

Bug#894466: python-fisx: please make the build reproducible

[Chris Lamb]

Source: python-fisx
Version: 1.1.4-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that python-fisx could not be built reproducibly as it includes
the build path in the definition of FISX_DOC_DIR in DataDir.py:

│ │ │ ├── ./usr/lib/python2.7/dist-packages/fisx/DataDir.py
│ │ │ │ @@ -25,15 +25,15 @@
│ │ │ │  # THE SOFTWARE.
│ │ │ │  #
│ │ │ │  
#*/
│ │ │ │  import os
│ │ │ │  # this will be filled by the setup
│ │ │ │  FISX_DATA_DIR = r'/usr/share/fisx/'
│ │ │ │  # this is to be filled by the setup
│ │ │ │ -FISX_DOC_DIR = 
r'/build/1st/python-fisx-1.1.4/debian/python-fisx/usr/lib/python2.7/dist-packages/fisx/fisx_data'
│ │ │ │ +FISX_DOC_DIR = 
r'/build/python-fisx-1.1.4/2nd/debian/python-fisx/usr/lib/python2.7/dist-packages/fisx/fisx_data'


Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2018-03-30 15:56:57.061589875 +0100
--- b/debian/rules  2018-03-30 17:59:24.106202503 +0100
@@ -4,7 +4,8 @@
 export PYBUILD_VERBOSE=1
 
 export WITH_CYTHON=1
-export FISX_DATA_DIR=/usr/share/fisx/
+export FISX_DATA_DIR=/usr/share/fisx
+export FISX_DOC_DIR=/usr/share/doc/python-fisx-common
 export PKGCOMMON=$(CURDIR)/debian/python-fisx-common/
 
 export PYBUILD_NAME=fisx
@@ -27,4 +28,4 @@
rm -f $(PKGCOMMON)/$(FISX_DATA_DIR)/LICENSE
 
 override_dh_auto_test:
-   FISX_DATA_DIR=$(CURDIR)/fisx_data dh_auto_test
+   FISX_DATA_DIR=$(CURDIR)/fisx_data FISX_DOC_DIR=$(CURDIR)/fisx_data 
dh_auto_test

Bug#799626: RFP: beancount -- command line double-entry bookkeeping system

[Martin Michlmayr]

* Petter Reinholdtsen  [2015-09-21 00:17]:
> * URL : http://furius.ca/beancount/
> * License : GPL v2+
> 
> A double-entry bookkeeping computer language that lets you define
> financial transaction records in a text file, read them in memory,
> generate a variety of reports from them, and provides a web interface.

beancount 2.0 was released a few days ago so it's time to get this
into Debian.

Anyone interested in packaging it?  It's Python code.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#888095: [debian-mysql] Bug#888095:

[Emilio Pozuelo Monfort]

Hi Otto,

On Sun, 4 Mar 2018 00:06:53 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
 wrote:
> It was not intended for the mariadb-10.x packages to ship the new LGPL
> based client library. For that we have the separate
> mariadb-connector-c package.
> 
> The package mariadb-10.2 is to be removed from Debian unstable and the
> next versions of mariadb-10.3 uploaded to Debian will not include this
> libmariadb3 library.

That's fine. There's still the problem that testing / unstable / experimental
users might have installed libmariadb3 when it was available to them, at version
10.2 or 10.3. Now if we go back to libmariadb3 3.0.3 from
src:mariadb-connector-c, apt will refuse to upgrade the package for those users.
That's why we need an epoch here, so that the new libmariadb3 from
src:mariadb-connector-c has a higher version than any previous libmariadb3. That
would also solve the problem with mariadb-connector-c failing to install into
the archive, as you can see in [1]

What I would suggest is that you upload mariadb-connector-c with an epoch (i.e.
1:3.0.3-2) and when it is built and installed, upload mariadb-10.3 without
libmariadb3.

Cheers,
Emilio

[1]
https://buildd.debian.org/status/package.php?p=mariadb-connector-c=unstable

Bug#887399: stretch-pu: package python-certbot/0.10.2-1

[Julien Cristau]

Control: tag -1 moreinfo

On Mon, Jan 15, 2018 at 18:04:59 -0500, Harlan Lieberman-Berg wrote:

> Due to a security issue in the underlying Let's Encrypt protocol, one of the 
> main methods of getting certificates from Let's Encrypt has been disabled 
> (the TLS-SNI-01 protocol; 
> https://community.letsencrypt.org/t/tls-sni-challenges-disabled-for-most-new-issuance/50316
>  for more info).
> 
> This puts us in a bit of an awkward spot.  The upstream certbot provider is 
> preparing to do a new release that has support for HTTP-01 inside the 
> python-certbot-apache and python-certbot-nginx plugins, as well as the 
> required work in python-acme and python-certbot (and certbot), but I'm not 
> sure backporting the patches is realistic.  A lot of development has been 
> done in the interim, both in the certbot packaging and in the upstream 
> software.  Without those patches, users with the apache or nginx plugins will 
> fail to update their certificates starting 2018-04-09.
> 
> I can talk to the certbot upstream to see if they'd be willing to help 
> backport the patches (CCed), but initial conversations seem to indicate that 
> doing so will be difficult.
> 
> The other approach that we can take is to backport the next version that 
> supports the new challenge through to s-p-u and into stable.  I'm guessing 
> that you will ask me to unwind the work I did to convert to python3 in the 
> last release (sadface), but I can do that if that's what it needs to get this 
> fixed in stable.
> 
I'm not sure that'd be wise, if it would mean shipping something
untested.  To me, the workable alternatives seem to be to either remove
those packages from stable, or update them to a current version.  At
least the 0.21 packages have presumably had some testing in
stretch-backports.  The switches to python 3 and debhelper 11 are
unfortunate, and at least the latter would need to be reverted.  I'm
worried about local scripts or other integration using python2 and
breaking if we were to move certbot to python3; how likely is that?  On
the other hand, I guess if they're still using the package from stable
it's going to break on them soon anyway.

What is the minimal set of source packages that we would need to update?
Is it python-acme, python-certbot, python-certbot-apache and
python-certbot-nginx?

Cheers,
Julien

Bug#894456: python3-distutils: trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also in package libpython3.6-stdlib

[Mathias Behrle]

Package: python3-distutils
Version: 3.6.5-1
Followup-For: Bug #894456

Hi Matthias,
indeed quite urgent, because also building with sbuild fails

Preparing to unpack .../53-python3-distutils_3.6.5-1_all.deb ...
Unpacking python3-distutils (3.6.5-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-0sBUSO/53-python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also 
in package libpython3.6-stdlib:amd64 3.6.5-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Thanks!

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

Kernel: Linux 4.14.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)

Versions of packages python3-distutils depends on:
ii  python3  3.6.4-1
ii  python3-lib2to3  3.6.5~rc1-1

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- no debconf information

Bug#888220: ignition-math4: FTBFS on mips(el) and hppa: UNIT_Helpers_TEST fails badly

[Emilio Pozuelo Monfort]

On Tue, 13 Feb 2018 15:15:22 -0800 Jose Luis Rivero 
wrote:
> Thanks very much James for the research and the patch.
> 
> I've sent it upstream:
> https://bitbucket.org/ignitionrobotics/ign-math/pull-requests/232/bug-in-pairing-function-insde-helperscc/diff

Can this be applied now? It's blocking sdformat builds on mips(el), which is in
turn blocking some transitions.

Thanks,
Emilio

Bug#886146: stretch-pu: package sqlcipher/3.2.0-2+deb9u1

[Julien Cristau]

On Thu, Mar 15, 2018 at 16:01:49 +0100, Gianfranco Costamagna wrote:

> Control: tag -1 - moreinfo
> On Sat, 10 Feb 2018 11:48:12 +0100 Julien Cristau  wrote:
> > Control: tag -1 moreinfo
> > 
> > On Tue, Jan  2, 2018 at 17:59:07 +0100, Gianfranco Costamagna wrote:
> > 
> > > +sqlcipher (3.2.0-2+deb9u1) stretch; urgency=medium
> > > +
> > > +  [ Philipp Berger ]
> > > +  * Fixup previous patch, to avoid a crash when opening file
> > > +(Closes: #863530)
> > > +
> > 
> > That bug is still open, implying it still affects sid?
> > 
> 
> I closed it, that patch comes from the new release, actually part of 
> sid/buster
> 
> sorry for not closing it in advance
> 
It'd be better for it to be fixed with a version, rather than imply it's
invalid.

Can you please also describe what if any testing was done on the
proposed update, and why this breakage wasn't caught before release?

Cheers,
Julien

Bug#894465: RFS: materia-gtk-theme/20180321-1

[I Sagar]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "materia-gtk-theme"

* Package name: materia-gtk-theme
   Version : 20180321-1
   Upstream Author : nana-4
* URL : https://github.com/nana-4/materia-theme
* License : GPL-2+
   Section : x11

It builds those binary packages:

materia-gtk-theme - Material Design theme for GNOME/GTK+ based desktop 
environments

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

https://mentors.debian.net/package/materia-gtk-theme


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

dget -x 
https://mentors.debian.net/debian/pool/main/m/materia-gtk-theme/materia-gtk-theme_20180321-1.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

materia-gtk-theme (20180321-1) unstable; urgency=medium

  * New upstream release
  * Depend on gnome-themes-extra (Closes: #892037)
  * Add Vcs fields and update Build-depends
  * Bump debhelper compat to 11


Regards,
Sagar Ippalpalli

Bug#893221: knopflerfish-osgi FTBFS with openjdk-9

[Felix Natter]

Emmanuel Bourg  writes:

hello Emmanuel,

> Le 30/03/2018 à 09:41, Felix Natter a écrit :
>
>> Is the following ok for getting rid of the -java-doc package
>> (I don't think it makes sense to keep an older doc package)?
>> 
>>  Package: libknopflerfish-osgi-framework-java
>>  Architecture: all
>>  Depends: ${misc:Depends}
>> -Suggests: libknopflerfish-osgi-java-doc
>> +Provides: libknopflerfish-osgi-java-doc
>> +Conflicts: libknopflerfish-osgi-java-doc
>> +Replaces: libknopflerfish-osgi-java-doc
>
> libknopflerfish-osgi-java-doc has no reverse dependencies, no need to
> add these fields you can drop it directly.

Are you sure? Without these settings, libknopflerfish-osgi-java-doc-X
will still be kept if libknopflerfish-osgi-framework-java is updated to
Y, thus you have an old doc package lying around.

One important lintian is an FP (#894397)
W: libknopflerfish-osgi-framework-java:
incompatible-java-bytecode-format Java9 version (Class format: 53)

Would you want to sponsor this minor update?

knopflerfish-osgi (6.1.1-2) unstable; urgency=medium

  * Drop -java-doc package due to low popcon (Closes: #893221)
  * Correct description (R5->R6)
  * Priority extra->optional
  * Install NOTICE.txt in main package
  * Bump standards version to 4.1.3

 -- Felix Natter   Fri, 30 Mar 2018 17:29:18 +0200

https://anonscm.debian.org/cgit/pkg-java/knopflerfish-osgi.git

Many Thanks and Best Regards,
-- 
Felix Natter
debian/rules!

Bug#894342: transition: kdepim

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 29/03/18 12:45, Sandro Knauß wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> KDE Pim 17.12 has updated ist API and ABI, that makes it nessasary to bump
> some ABIs. To track those ABI breakages, we updated the package names to
> 5abi1. So far most of the packages, that needs to be rebuild are inside
> KDE Pim itself so only following "external" packages are affected:
> 
> blogilo
> digikam
> kjots
> libkolab
> zanshin
> (calligra, calligraplan)
> 
> I build all rdepends and came to the conclusion:
> * kjots and zanshin build nicely with the new KDE Pim
> * blogilo has fallen out of KDE Pim can't be build anymore -> RM request
> * libkolab do not build anymore with KDE Pim 17.12 it is dead upstream
>   and not needed anymore for KDE Pim -> RM request [1]
> * digikam is not ready for KDE Pim 17.12 (see #893515)
>   the mantainer told me in private:
>   " My suggestion is: go ahead with the upload to unstable.  I should be
>   able to get digikam uploaded very shortly thereafter."
> * calligra and calligraplan depdend on the build pacakges, but the
>   featueres that use KDE Pim are disabled, so no need to build them
>   within the transition.
> 
> This transistion includes/replaces following auto detected transitions:
> auto-akonadi-calendar
> auto-akonadi
> auto-kcalcore
> auto-kdav
> auto-kmime
> auto-kpimtextedit
> auto-libkf5calendarsupport
> auto-libkf5gravatar
> auto-libkf5incidenceeditor
> auto-libkf5mailcommon
> auto-libkf5pimcommon
> 
> These 11 transistions share nearly all rdepdens, that's why I think it is
> easier to track it in only one transistion and not within 11. But if
> you belive it is easier to have saperate ones, please tell me. I look at
> all, and all look correcty so far, but IMO it is not easy keep an
> overview.
> 
> After KDE Frameworks 5.44 entered testing successfully, there is no
> blocker anymore for starting this transition. Please tell me
> additionally, if I need to request the RMs in advanced or while the
> transition is going on.

Go ahead.

You can request the RMs at any point, via reportbug ftp.debian.org. For libkolab
you probably want to wait until you have uploaded kdepim without a dependency on
libkolab.

Emilio

Bug#891486: ITP: pipenv -- python development workflow for humans

[Bastian Venthur]

Dear ChangZhuo Chen,

I'm terribly sorry, I just realized that you've already filled an ITP
for pipenv while I worked on that package too and uploaded it into
unstable today.

It was my mistake, I didn't check for existing ITPs. I've prepared the
pipenv package last week by NMU'ing the outdated virtualenv-clone
package and porting it to Python3.

I'm maintaining the pipenv package under the umbrella of the Python
Applications Packaging Team and you'll find the git repository here:

https://salsa.debian.org/python-team/applications/pipenv

Please feel free to take over the package or co-maintain it with me and
the PAPT.


Have a nice weekend!

Bastian

-- 
Dr. Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org

Bug#894464: RFS: deepin-picker/1.6.2-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-picker"

* Package name: deepin-picker
  Version : 1.6.2-1
  Upstream Author : Deepin Technology Co., Ltd
* URL : https://github.com/linuxdeepin/deepin-picker
* License : GPL-3+
  Section : graphics

It builds those binary packages:

  deepin-picker - Color picker tool for deepin

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

https://mentors.debian.net/package/deepin-picker

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-picker/deepin-picker_1.6.2-1.dsc

More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-picker

Changes since the last upload:
  * New upstream release.
  * d/control: Use Salsa platform for Vcs field.
  * d/control: Update Standers-Version to 4.1.3.
  * d/compat: Swithch compat to level 11.
  * d/patches: add a patch to delete wrong desktop category 'Picker'.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#893239: Pending fixes for bugs in the libjackson-json-java package

[pkg-java-maintainers]

tag 893239 + pending
thanks

Some bugs in the libjackson-json-java package are closed in revision
58c3f70a6ea3be9f51666575ffebeb57919b4b60 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libjackson-json-java.git/commit/?id=58c3f70

Commit message:

Fix FTBFS with Java 9.

Closes: #893239

Bug#887148: stretch-pu: package python-certifi/2016.2.28-1+deb9u1

[Julien Cristau]

On Sun, Jan 14, 2018 at 15:01:34 +0100, Andreas Beckmann wrote:

> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Let's fix the python3 dependencies in stretch: #867421
> 
> $ debdiff python3-certifi_2016.2.28-1_all.deb 
> python3-certifi_2016.2.28-1+deb9u1_all.deb
> File lists identical (after any substitutions)
> 
> Control files: lines which differ (wdiff format)
> 
> Depends: {+python3:any (>= 3.4~),+} ca-certificates
> Version: [-2016.2.28-1-] {+2016.2.28-1+deb9u1+}
> 
For something that's a python3 library I'm thinking there's little
chance it gets installed without python3.  The overhead of a stable
update for something that's very unlikely to affect anyone in real life
is not clearly worth it.  That may mean we should think of ways to cut
down on that overhead, or that we should ignore more bugs for stable,
I'm not sure.

Cheers,
Julien

Bug#894463: synaptic icon seems pixelated (jessie)

[pythesquid]

Package: synaptic
Version: 0.84.2
Severity: minor
Tags: newcomer

Hello folks.
The synaptic icon is pixelated on jessie.



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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.4.8
ii  libapt-pkg5.01.4.8
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u3
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5+deb9u3
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   6.3.0-18+deb9u1
ii  libvte-2.91-00.46.1-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.3-2
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.2499-1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information

Bug#894118: dlib: New upstream release available

[Hugo Lefeuvre]

Hi Séverin,

> I'd be more than happy to delegate the maintenance of dlib! Please feel free
> to take over.
> 
> The package source is here: https://github.com/severin-lemaignan/dlib-debian
> I'm happy to add you as collaborator of the repo if you want to commit
> there.

Thanks for the quick answer. If you don't mind, I'm going to switch to a
Salsa repository, I think it's better to keep package sources in the
Debian infrastructure as far as possible. :)

Do you already have a Salsa account ?

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature

Bug#881871: stretch-pu: package bacula/7.4.4+dfsg-6

[Julien Cristau]

On Sun, Mar  4, 2018 at 11:08:00 +0100, Carsten Leonhardt wrote:

> Control: tags -1 - moreinfo
> 
> "Adam D. Barratt"  writes:
> 
> > -   --oknodo --exec $DAEMON --chuid $BUSER:$BGROUP -- -c $CONFIG
> > +   --oknodo --exec $DAEMON -- -g $BUSER -g $BGROUP -c $CONFIG
> >
> > The first of those "-g" is presumably supposed to be "-u". I realise
> > this may seem a small point, but it does make me wonder how it wasn't
> > caught in testing.
> 
> Thank you for your work and for catching this. A new version of the
> patch is attached.
> 
This leaves open the question of how much was this tested.  Can you
describe what has or hasn't been done there?

Cheers,
Julien

Bug#892633: pytest-catchlog FTBFS with pytest 3.3.2-2

[Hugo Lefeuvre]

Control: forwarded -1 https://github.com/eisensheng/pytest-catchlog/issues/76

Hi,

I've forwarded this issue to upstream.

I suspect incompatibilities with pytest version 3.3.2 (package was
building fine with 3.2.5).

I'm quite in a hurry right now, but without answer from him I'll start
working on a patch (and will probably adopt python-catchlog at the
same time).

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature

Bug#894462: paraview: edges are blotted [regression]

[Francesco Poli (wintermute)]

Package: paraview
Version: 5.4.1+dfsg4-2
Severity: grave
Justification: renders package unusable

Hello paraview Debian package maintainers,
thanks for uploading a Debian revision that uses Qt5 rather than Qt4!

I've just upgraded to it on my Debian testing box, but I found a bad
regression that renders the package unusable to create beautiful and
clear visualizations (this may be considered as basically the main
purpose of paraview!).


The attached test case is based on one of the data files generated
by the little program included in the test case sent for bug #892293.
The program source (written in Fortran) is included again for
completeness' sake.

Steps to reproduce the regression:

  0) start paraview

 $ paraview

  1) click on the "Open" button and open "wave0001.xyz"

  2) specify "PLOT3D Files" in the "Open Data With..." dialog window

  3) click on the "Apply" button
  
  4) change the representation from "Outline" to "Surface With Edges"

  5) from the File menu, select Save State...

  6) save the state as "wave_PARAVIEW-VERSION.pvsm"

  7) from the File menu, select Save Screenshot...

  8) save the screenshot as "wave_PARAVIEW-VERSION.png"


By performing these steps with paraview/5.4.1+dfsg3-2 and
with paraview/5.4.1+dfsg4-2, I obtained the two attached
screenshots.

In paraview/5.4.1+dfsg4-2 there seems to be a commendable attempt
to apply some antialiasing to all the lines (including the edges
on surfaces, the wireframe edges, but also the lines of the orientation
axes, and so forth...).
Unfortunately this new feature creates unsightly images, whenever
the edges are shown from a distance. Please take a look yourself
at the wave_5.4.1+dfsg4-2.png screenshot: all the intersections
between edges seem to be somehow "blotted" and unpleasant to look at.


Please fix this regression, as it makes paraview unusable.

Thanks for your time!
Bye.


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

Kernel: Linux 4.15.0-2-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)
LSM: AppArmor: enabled

Versions of packages paraview depends on:
ii  libavcodec57   7:3.4.2-1+b1
ii  libavformat57  7:3.4.2-1+b1
ii  libavutil557:3.4.2-1+b1
ii  libc6  2.27-2
ii  libcgns3.3 3.3.0-6
ii  libexpat1  2.2.5-3
ii  libfreetype6   2.8.1-2
ii  libgcc11:8-20180321-1
ii  libgl1 1.0.0-2
ii  libgl2ps1.41.4.0+dfsg1-2
ii  libglew2.0 2.0.0-5
ii  libhdf5-1001.10.0-patch1+docs-4
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libjsoncpp11.7.4-3
ii  libnetcdf131:4.6.1-1
ii  libogg01.3.2-1+b1
ii  libopenmpi22.1.1-8
ii  libpng16-161.6.34-1
ii  libprotobuf10  3.0.0-9.1
ii  libpython2.7   2.7.14-7
ii  libqt5core5a   5.9.2+dfsg-12
ii  libqt5gui5 5.9.2+dfsg-12
ii  libqt5help55.9.2-6
ii  libqt5network5 5.9.2+dfsg-12
ii  libqt5widgets5 5.9.2+dfsg-12
ii  libqt5x11extras5   5.9.2-1
ii  libstdc++6 8-20180321-1
ii  libswscale47:3.4.2-1+b1
ii  libtheora0 1.1.1+dfsg.1-14+b1
ii  libtiff5   4.0.9-4
ii  libx11-6   2:1.6.5-1
ii  libxml22.9.4+dfsg1-6.1
ii  libxt6 1:1.1.5-1
ii  python-autobahn17.10.1+dfsg1-2
ii  python-matplotlib  2.1.1-2
ii  python-mpi4py  2.0.0-3
ii  python-six 1.11.0-2
ii  python-twisted 17.9.0-1
ii  tcl [tclsh]8.6.0+9
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages paraview recommends:
ii  mpi-default-bin  1.10
ii  paraview-doc 5.4.1+dfsg4-2
ii  paraview-python  5.4.1+dfsg4-2

Versions of packages paraview suggests:
pn  h5utils 
pn  hdf5-tools  

-- no debconf information


waveplot3d_blotted-edges.tar.xz
Description: application/xz

Bug#663101: Let me know urgently.

[edclark00]

Good morning,
Please did you receive my previous letter dated 14/3/2018?
Let me know urgently.
Edwin.

Bug#893381: openstereogram FTBFS with openjdk-9

[Emmanuel Bourg]

Control: tags -1 + patch

This is easily fixed by adding a debian/ant.properties files containing:

  source.encoding=ISO-8859-1

Bug#894461: python3-matplotlib shows requires backports.functools-lru-cache and subprocess32

[ELMER, BRENT S. [AG/1000]]

Package: python3-matplotlib
Severity: normal

When python3-matplotlib is installed from the debian repository, it shows that
it requires backports.functools-lru-cache and subprocess32.

pip3 show matplotlib
Name: matplotlib
Version: 2.1.1
Summary: Python plotting package
Home-page: http://matplotlib.org
Author: John D. Hunter, Michael Droettboom
Author-email: matplotlib-us...@python.org
License: BSD
Location: /usr/lib/python3/dist-packages
Requires: backports.functools-lru-cache, subprocess32


However, pip3 shows that backports... and subprocess32 is not installed.  Which
is a good thing because they are only valid for python2.

# pip3 show subprocess32
# pip3 show backports.functools-lru-cache
#

However, when I use pip3 to install packages that are not in debian and pip3
sees the two requirements, it tries to install them and errors out saying that
subprocess32 is only for python2.

# pip3 install mlxtend
Collecting mlxtend
  Using cached mlxtend-0.11.0-py2.py3-none-any.whl
Requirement already satisfied: numpy>=1.10.4 in /usr/lib/python3/dist-packages
(from mlxtend)
Requirement already satisfied: scikit-learn>=0.18 in /usr/lib/python3/dist-
packages (from mlxtend)
Requirement already satisfied: matplotlib>=1.5.1 in /usr/lib/python3/dist-
packages (from mlxtend)
Requirement already satisfied: pandas>=0.17.1 in /usr/lib/python3/dist-packages
(from mlxtend)
Requirement already satisfied: scipy>=0.17 in /usr/lib/python3/dist-packages
(from mlxtend)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages
(from mlxtend)
Collecting backports.functools_lru_cache (from matplotlib>=1.5.1->mlxtend)
  Using cached backports.functools_lru_cache-1.5-py2.py3-none-any.whl
Collecting subprocess32 (from matplotlib>=1.5.1->mlxtend)
  Using cached subprocess32-3.2.7.tar.gz
Complete output from command python setup.py egg_info:
This backport is for Python 2.x only.

This can be fixed by uninstalling debian's python3-matplotlib and using pip3 to
install matplotlib which doesn't have the backports... and subprocess32
requirement.  Then the other package that depends on matplotlib installs
successfully.



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

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

Versions of packages python3-matplotlib depends on:
ii  libc6   2.27-2
ii  libfreetype62.8.1-2
ii  libgcc1 1:8-20180321-1
ii  libjs-jquery3.2.1-1
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libpng16-16 1.6.34-1
ii  libstdc++6  8-20180321-1
ii  python-matplotlib-data  2.1.1-2
ii  python3 3.6.4-1
ii  python3-cycler  0.10.0-1
ii  python3-dateutil2.6.1-1
ii  python3-numpy [python3-numpy-abi9]  1:1.13.3-2
ii  python3-pyparsing   2.2.0+dfsg1-2
ii  python3-six 1.11.0-2
ii  python3-tz  2018.3-2
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages python3-matplotlib recommends:
ii  python3-pil  4.3.0-2
ii  python3-tk   3.6.5~rc1-1

Versions of packages python3-matplotlib suggests:
pn  dvipng 
pn  ffmpeg 
ii  ghostscript9.22~dfsg-2
ii  gir1.2-gtk-3.0 3.22.29-2
ii  inkscape   0.92.3-1
pn  ipython3   
ii  librsvg2-common2.40.20-2
pn  python-matplotlib-doc  
pn  python3-cairocffi  
ii  python3-gi 3.26.1-2
ii  python3-gi-cairo   3.26.1-2
pn  python3-gobject
ii  python3-nose   1.3.7-4
pn  python3-pyqt4  
ii  python3-scipy  0.19.1-2
ii  python3-sip4.19.8+dfsg-1
ii  python3-tornado5.0.0-1
pn  texlive-extra-utils
ii  texlive-latex-extra2017.20180305-2
pn  ttf-staypuft   


Brent S. Elmer, Ph.D.

This email and any attachments were sent from a Monsanto email account and may 
contain confidential and/or privileged information. If you are not the intended 
recipient, please contact the sender and delete this email and any attachments 
immediately. Any unauthorized use, including disclosing, printing, storing, 
copying or distributing this email, is prohibited. All emails and attachments 
sent to or from Monsanto email accounts may be subject to monitoring, reading, 
and archiving by Monsanto, including its affiliates and subsidiaries, as 
permitted by applicable law. Thank you.

Bug#893410: Pending fixes for bugs in the polyglot-maven package

[pkg-java-maintainers]

tag 893410 + pending
thanks

Some bugs in the polyglot-maven package are closed in revision
9a21a12cf4c8527d7110844cd51699a88b1ca636 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/polyglot-maven.git/commit/?id=9a21a12

Commit message:

Fixed the build failure with Java 9 (Closes: #893410)

Bug#893243: Pending fixes for bugs in the libhtmlparser-java package

[pkg-java-maintainers]

tag 893243 + pending
thanks

Some bugs in the libhtmlparser-java package are closed in revision
cec5e82aefddba5fee21d3e8699cc96060a8f37f in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libhtmlparser-java.git/commit/?id=cec5e82

Commit message:

Add encoding.patch and fix FTBFS with Java 9.

Closes: #893243

Bug#894457: Acknowledgement (python3-distutils: Install error: "trying to overwrite '/usr/lib/python3.6/distutils/__init__.py'")

[Diederik de Haas]

Control: severity -1 serious
Control: merge -1 894458
Control: severity 894456 serious
Control: merge 894456 894458
thx

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

Bug#893417: Pending fixes for bugs in the spock package

[pkg-java-maintainers]

tag 893417 + pending
thanks

Some bugs in the spock package are closed in revision
715def2e045ef5cde39bf3a0cf4509ae866bf82b in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/spock.git/commit/?id=715def2

Commit message:

Fixed the build failure with Java 9 (Closes: #893417)

Bug#894460: checkrestart: false positive for Xorg with Intel graphics under Linux kernel 4.15

[Francesco Poli (wintermute)]

Package: debian-goodies
Version: 0.79
Severity: normal

Hello!

I noticed a new false positive in checkrestart, since I upgraded my
Debian testing boxes to linux-image-4.15.0-2-amd64/4.15.11-1

Under an X session with Intel graphics, when I run

  # checkrestart -v

I get the attached output, even when the box has just booted and
no upgrade has been performed yet.

I seem to recall that there were some entries ignored in order to
avoid false positives with Intel graphics.
Maybe these entries changed slightly and are no longer ignored?!?

Please add the new entries to the ignore list.

Thanks for your time!
Bye.


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

Kernel: Linux 4.15.0-2-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)
LSM: AppArmor: enabled

debian-goodies depends on no packages.

Versions of packages debian-goodies recommends:
ii  apt1.6~beta1
ii  curl   7.58.0-2
ii  dctrl-tools2.24-2+b1
ii  dialog 1.3-20171209-1
pn  elfutils   
ii  libipc-system-simple-perl  1.25-4
ii  man-db 2.8.2-1
ii  perl   5.26.1-5
ii  popularity-contest 1.66
ii  procps 2:3.3.12-4
ii  python33.6.4-1
ii  sensible-utils 0.0.12
ii  whiptail   0.52.20-4
ii  zenity 3.28.0-1

Versions of packages debian-goodies suggests:
ii  apt-file   3.1.5
ii  chromium [www-browser] 62.0.3202.89-1
ii  firefox-esr [www-browser]  52.6.0esr-2+b1
pn  konqueror  
pn  libgnome2-bin  
ii  lsb-release9.20170808
ii  lsof   4.89+dfsg-0.1
ii  w3m [www-browser]  0.5.3-36
ii  xdg-utils  1.1.2-2

-- no debconf information
Found 1 processes using old versions of upgraded files
(1 distinct program)
[DEBUG] Process /usr/lib/xorg/Xorg (PID: 1171) 
List of deleted files in use:
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
/i915
[DEBUG] Running: dpkg-query --search /usr/lib/xorg/Xorg
[DEBUG] Reading line from dpkg-query: xserver-xorg-core: /usr/lib/xorg/Xorg

[DEBUG] Found package xserver-xorg-core for program /usr/lib/xorg/Xorg
(1 distinct packages)
[DEBUG] Running: dpkg-query --listfiles xserver-xorg-core
These processes (1) do not seem to have an associated init script to restart 
them:
xserver-xorg-core:
1171/usr/lib/xorg/Xorg

Bug#894459: golang-golang-x-crypto-dev: Please package a new snapshot

[Paride Legovini]

Package: golang-golang-x-crypto-dev
Version: 1:0.0~git20170629.0.5ef0053-2
Severity: normal

Dear Maintainers,

Please consider packaging a new snapshot of this library.
I specifically miss the ‘argon2’ functions, which were inroduced
a few months ago.

This is a blocker for my ITP #894406.

Thank you,

Paride

Bug#894458: python3-distutils: fails to upgrade from sid

[Vivia Nikolaidou]

Package: python3-distutils
Version: 3.6.5~rc1-3
Severity: serious
Justification: Policy 7.6.1

Dear Maintainer,

When trying to do a routine dist-upgrade, the package python3-distutils fails 
with the following error message:

Unpacking python3-distutils (3.6.5-1) over (3.6.5~rc1-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also 
in package libpython3.6-stdlib:amd64 3.6.5-1

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

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

Versions of packages python3-distutils depends on:
ii  python3  3.6.5~rc1-1
iu  python3-lib2to3  3.6.5-1

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- no debconf information

Bug#882760: Debian debian.linux.edu.lv: ftpsync version, push+cron

[Bastian Blank]

Hi

All pushs fail since 2018-03-04.  Please investigate.

We did not get any response from you for our last inquiry since several
months.  It is as follows:

On Sun, Nov 26, 2017 at 02:19:38PM +0100, Bastian Blank wrote:
> You receive this mail because you are listed as contact for:
>   debian.linux.edu.lv
> 
> Please update your ftpsync version.  Running a current ftpsync version
> makes sure the update is done in a way apt does not blow up.  Also it
> allows us to monitor the status of the mirror in more detail.  You can
> find the current ftpsync at:
>   http://ftp.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz
> 
> You seem to be both pushed by your upstream syncproxy2.eu.debian.org,
> but also running a sync from cron.  Please disable the later.

Bastian

-- 
I object to intellect without discipline;  I object to power without
constructive purpose.
-- Spock, "The Squire of Gothos", stardate 2124.5

Bug#894456: python3-distutils: trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also in package libpython3.6-stdlib

[Jochen Sprickerhof]

Package: python3-distutils
Version: 3.6.5~rc1-3
Severity: grave
Justification: renders package unusable

Hi,

with todays update I get:

# apt-get -f install python3-distutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  python3-distutils
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/147 kB of archives.
After this operation, 28.7 kB of additional disk space will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 63950 files and directories currently installed.)
Preparing to unpack .../python3-distutils_3.6.5-1_all.deb ...
Unpacking python3-distutils (3.6.5-1) over (3.6.5~rc1-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also 
in package libpython3.6-stdlib:armhf 3.6.5-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Could you please fix this?

Thanks

Jochen


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

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

Versions of packages python3-distutils depends on:
ii  python3  3.6.5~rc1-1
ii  python3-lib2to3  3.6.5-1

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- debconf-show failed

Bug#894457: python3-distutils: Install error: "trying to overwrite '/usr/lib/python3.6/distutils/__init__.py'"

[Diederik de Haas]

Package: python3-distutils
Version: 3.6.5~rc1-3
Severity: normal

The version as stated above is incorrect, the issue is with trying to
install version 3.6.5-1. As it looks like various Debian infra aren't
yet aware of this new version, I'll leave it up to the maintainer to fix
it.

Here's part of the (error) output while trying to upgrade this package:

Preparing to unpack .../2-python3-lib2to3_3.6.5-1_all.deb ...
Unpacking python3-lib2to3 (3.6.5-1) over (3.6.5~rc1-3) ...
Preparing to unpack .../3-python3-distutils_3.6.5-1_all.deb ...
Unpacking python3-distutils (3.6.5-1) over (3.6.5~rc1-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-eHI2ei/3-python3-distutils_3.6.5-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also 
in package libpython3.6-stdlib:amd64 3.6.5-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../4-python3-tk_3.6.5-1_amd64.deb ...
Unpacking python3-tk:amd64 (3.6.5-1) over (3.6.5~rc1-3) ...
...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-eHI2ei/3-python3-distutils_3.6.5-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I can provide more info if needed, but my guess is a breaks/replaces
packaging issue.


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

Kernel: Linux 4.15.0-2-amd64 (SMP w/16 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)
LSM: AppArmor: enabled

Versions of packages python3-distutils depends on:
ii  python3  3.6.5~rc1-1
ii  python3-lib2to3  3.6.5-1

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- no debconf information

Bug#894455: aptitude: Segfault while scrolling through package list

[Axel Beckert]

Package: aptitude
Version: 0.8.10-6

Hi,

aptitude (running inside GNU Screen) just segfaulted while browsing with
"cursor down" through the "Obsolete and locally installed packages"
list:

$ gdb -q aptitude-curses 
/var/crash/0/23865-0-0-11-1522417552-c-cactus2--usr-bin-aptitude-curses.core
Reading symbols from aptitude-curses...Reading symbols from 
/usr/lib/debug/.build-id/43/f28dce371f83231f358317490dc7f606b12753.debug...done.
done.

warning: core file may not match specified executable file.
[New LWP 23865]
[New LWP 26420]
[New LWP 26410]
[New LWP 26411]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `aptitude -u'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f2256c3a686 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
[Current thread is 1 (Thread 0x7f2257052800 (LWP 23865))]
(gdb) bt
#0  0x7f2256c3a686 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#1  0x7f2256c3a741 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#2  0x7f2256c3a7a3 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#3  0x7f2256c39e23 in pkgTagSection::FindS[abi:cxx11](char const*) const () 
from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#4  0x7f2256bc8028 in ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
#5  0x56275e4ea1e0 in pkg_description_widget::set_package 
(this=0x56275fad5c70, pkg=..., ver=...) at ../../src/pkg_view.cc:308
#6  0x56275e4ea44a in info_area_multiplex::set_package 
(this=0x56275fadbb70, pkg=..., ver=...) at ../../src/pkg_view.cc:453
#7  0x56275e4c1460 in sigc::internal::signal_emit2::emit 
(_A_a2=..., 
_A_a1=..., impl=0x56275fc6d070) at 
/usr/include/sigc++-2.0/sigc++/signal.h:1300
#8  sigc::signal2::emit (this=, _A_a2=..., _A_a1=...)
at /usr/include/sigc++-2.0/sigc++/signal.h:3108
#9  sigc::signal2::operator() (_A_a2=..., _A_a1=..., this=)
at /usr/include/sigc++-2.0/sigc++/signal.h:3124
#10 pkg_item::do_highlighted_changed (this=0x5627669e2140, 
highlighted=) at ../../src/pkg_item.cc:115
#11 0x7f225623d2bd in sigc::internal::signal_emit1::emit (impl=0x5627669e2230, _A_a1=@0x7ffc3ddcebc0: true)
at /usr/include/sigc++-2.0/sigc++/signal.h:1045
#12 0x7f2256238cf9 in sigc::signal1::emit 
(this=, _A_a1=@0x7ffc3ddcebc0: true)
at /usr/include/sigc++-2.0/sigc++/signal.h:2955
#13 sigc::signal1::operator() (_A_a1=@0x7ffc3ddcebc0: 
true, this=) at /usr/include/sigc++-2.0/sigc++/signal.h:2971
#14 cwidget::widgets::tree::line_down (this=this@entry=0x56275facb190) at 
tree.cc:404
#15 0x7f225623c488 in cwidget::widgets::tree::handle_key 
(this=this@entry=0x56275facb190, k=...) at tree.cc:796
#16 0x56275e4b551b in menu_tree::handle_key (this=0x56275facb190, k=...) at 
../../src/menu_tree.cc:430
#17 0x56275e4d2623 in pkg_tree::handle_key (this=0x56275facb190, k=...) at 
../../src/pkg_tree.cc:363
#18 0x7f22562409c5 in cwidget::widgets::widget::dispatch_key 
(this=this@entry=0x56275facb190, k=...) at widget.cc:267
#19 0x7f22562280bc in cwidget::widgets::table::handle_key 
(this=0x56275fc6c490, k=...) at table.cc:576
#20 0x7f22562409c5 in cwidget::widgets::widget::dispatch_key 
(this=0x56275fc6c490, k=...) at widget.cc:267
#21 0x7f225621357b in cwidget::widgets::passthrough::handle_key 
(this=0x56275fada820, k=...) at passthrough.cc:98
#22 0x7f22562409c5 in cwidget::widgets::widget::dispatch_key 
(this=this@entry=0x56275fada820, k=...) at widget.cc:267
#23 0x7f22562280bc in cwidget::widgets::table::handle_key 
(this=0x56275fadb470, k=...) at table.cc:576
#24 0x7f22562409c5 in cwidget::widgets::widget::dispatch_key 
(this=0x56275fadb470, k=...) at widget.cc:267
#25 0x7f225621357b in cwidget::widgets::passthrough::handle_key 
(this=0x56275fac35e0, k=...) at passthrough.cc:98
#26 0x7f22562409c5 in cwidget::widgets::widget::dispatch_key 
(this=0x56275fac35e0, k=...) at widget.cc:267
#27 0x7f22561f6449 in cwidget::widgets::menubar::handle_key 
(this=0x56275face7c0, k=...) at menubar.cc:641
#28 0x7f22562409c5 in cwidget::widgets::widget::dispatch_key 
(this=0x56275face7c0, k=...) at widget.cc:267
#29 0x7f22561c481f in 
cwidget::toplevel::input_thread::get_input_event::dispatch 
(this=0x7f223c000b20) at toplevel.cc:400
#30 0x7f22561bc919 in cwidget::toplevel::mainloop (synch=synch@entry=0) at 
toplevel.cc:1171
#31 0x56275e529bea in ui_main () at ../../src/ui.cc:3134
#32 0x56275e44f1a4 in main (argc=, argv=) at 
../../src/main.cc:1430
(gdb) 


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

Bug#894454: xz.1: Some tidying of the manual

[Bjarni Ingi Gislason]

Package: xz-utils
Version: 5.2.2-1.3
Severity: minor
Tags: patch

Dear Maintainer,

  the patch is in the attachment.

Input file is xz.1

Test nr. 2:

Enable and fix warnings from 'test-groff'.

Input file is /tmp/xz.1

:408 (macro BR): only 1 argument, but more are expected
:1724 (macro BR): only 1 argument, but more are expected
:1901 (macro BR): only 1 argument, but more are expected
:2194 (macro BR): only 1 argument, but more are expected

chk_manuals: Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  and

Test nr. 15:

Change the name of a macro for two fonts (e.g., BR and IR) to one letter,
if there is only one argument.
Add the second argument if needed.  It is sometimes part of the first one.

408:.BR \-\-stdout
1724:.BR \-\-info\-memory
1901:.BR 0.123.
2194:.BR lzcat

#

Test nr. 5:

Change '-' (\-) to '\(en' (en-dash) for a numeric range.

xz.1:843:Typically a good value is 2\-4 times
xz.1:1309:1\-3
xz.1:1425:0\-3 and
xz.1:1429:4\-9.
xz.1:1448:can be 2\-273 bytes.
xz.1:1466:for Hash Chains is 4\-100 and 16\-1000 for Binary Trees.
xz.1:1507:which can help LZMA2 to produce 0\-15\ % smaller
xz.1:1626:must be 1\-256.

#


Test nr. 8:

Protect a full stop (.) with "\&", if it has a blank (white-space) in front
of or (ignoring transparent characters to the full stop) after it, and it does
not mean an end of a sentence.

15:.RI [ option... ]
16:.RI [ file... ]
224:wasn't deemed to be flexible enough (e.g. using
259:match the compression level presets, e.g. if the limit is
279:This can be useful e.g. if the
673:e.g. for distributing files that need to be decompressible
1072:preset options (\fB\-0\fR ... \fB\-9\fR and \fB\-\-extreme\fR)
1156:matching the command line options \fB\-0\fR ... \fB\-9\fR.
1237:E.g. in typical English text, an upper-case letter is
1281:E.g. with text files having one-byte
1535:(e.g. object files, static libraries, and Linux kernel modules)
1609:It can be useful when compressing e.g. uncompressed bitmap images
1614:which compresses faster and better e.g. with
1685:never has any colons, e.g. 2 min 30 s.
1698:If the operation didn't finish, e.g. due to user interruption,
2152:This is the case e.g. when
2169:e.g. to set script-specific default compression options.
2172:if that is reasonable, e.g. in
2464:which is slower than e.g. the default
2618:somewhat big dictionary (e.g. 32 MiB) to compress well,
2621:would do, a preset with a low CompCPU value (e.g. 1)
2672:e.g. to make it possible to decompress the file on
2704:E.g. a source code archive contains mostly US-ASCII text,
2721:E.g. to compress a x86-32 or x86-64 shared library
2750:e.g. as uncompressed TIFF.
2753:E.g. 24-bit RGB bitmap needs

#

Test nr. 20:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them.
[1] man-pages(7)

  Only italic corrections (\, and \/) added if it is an argument to the
macro .TP

230:the command line option \fB\-\-memlimit=\fIlimit\fR.
238:by using \fB\-\-memlimit\-compress=\fIlimit\fR and
239:\fB\-\-memlimit\-decompress=\fIlimit\fR.
246:(or \fB\-M\fR \fIlimit\fR)
473:\fB\-S\fR \fI.suf\fR, \fB\-\-suffix=\fI.suf
504:\fB\-\-files\fR[\fB=\fIfile\fR]
518:\fB\-\-files0\fR[\fB=\fIfile\fR]
519:This is identical to \fB\-\-files\fR[\fB=\fIfile\fR] except
524:\fB\-F\fR \fIformat\fR, \fB\-\-format=\fIformat
568:\fB\-C\fR \fIcheck\fR, \fB\-\-check=\fIcheck
889:the value specified with \fB\-\-block\-size=\fIsize\fR),
1025:\fB\-M\fR \fIlimit\fR, \fB\-\-memlimit=\fIlimit\fR, \fB\-\-memory=\fIlimit
1026:This is equivalent to specifying \fB\-\-memlimit\-compress=\fIlimit
1027:\fB\-\-memlimit\-decompress=\fIlimit\fR.
1037:\fB\-T\fR \fIthreads\fR, \fB\-\-threads=\fIthreads
1120:\fB\-\-lzma1\fR[\fB=\fIoptions\fR]
1123:\fB\-\-lzma2\fR[\fB=\fIoptions\fR]
1486:\fB\-\-x86\fR[\fB=\fIoptions\fR]
1489:\fB\-\-powerpc\fR[\fB=\fIoptions\fR]
1491:\fB\-\-ia64\fR[\fB=\fIoptions\fR]
1493:\fB\-\-arm\fR[\fB=\fIoptions\fR]
1495:\fB\-\-armthumb\fR[\fB=\fIoptions\fR]
1497:\fB\-\-sparc\fR[\fB=\fIoptions\fR]
1603:\fB\-\-delta\fR[\fB=\fIoptions\fR]

#

Test nr. 26:

Find a repeated word

! 1554 --> have

#

Test nr. 30:

Surround a block of comments with the macros ".ig" and "..".
The .\" (\#) at the beginning of each line is then not needed.
Makes it easier to add and remove text and adjust lengtxh of lines.

NO PATCH

2:.\"
3:.\" Author: Lasse Collin
4:.\"
5:.\" This file has been put into the public domain.
6:.\" You can do whatever you want with this file.
7:.\"

#

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

Kernel: Linux 4.9.80-2 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions 

Bug#893353: libinline-java-perl FTBFS with openjdk-9

[Emmanuel Bourg]

Control: fixed -1 0.63-1
Control: close -1

I confirm this is now fixed in unstable.

Bug#894330: Pending fixes for bugs in the proguard package

[pkg-java-maintainers]

tag 894330 + pending
thanks

Some bugs in the proguard package are closed in revision
5fa054d253a7fbbd8018582848089e54c3ee7219 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/proguard.git/commit/?id=5fa054d

Commit message:

Build-depend on gradle and build the Gradle task again.

Closes: #894330

Bug#894453: wxglade: new upstream (0.8.0) available

[Karsten Hilbert]

Package: wxglade
Version: 0.8.0~a8-1
Severity: wishlist
Tags: upstream

Upstream has released 0.8.0 which officially supports
wxPhoenix/Python3.

Debian tries to reduce the exposure to Python2 so
this wxGlade version would help in porting projects
(we are using wxGlade for GNUmed which needs to
be ported).

May I kindly ask for packaging as your time allows ?

Thanks,
Karsten


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.15.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wxglade depends on:
ii  python   2.7.14-4
ii  python-wxgtk3.0  3.0.2.0+dfsg-6

wxglade recommends no packages.

wxglade suggests no packages.

-- no debconf information

Bug#889315: designate: please make the build reproducible

[Chris Lamb]

found 889315 1:6.0.0-2
thanks

Dear Zigo,

>  [ Thomas Goirand ]
[…]
>  * Remove make-designate.conf-build-reproducibly.patch applied upstream.

Unfortunately this doesn't seem to be the case:

cfg.StrOpt(
'pybasedir',
default=os.path.abspath(os.path.join(os.path.dirname(__file__),
 '../')),
 ensure_absolute_url
help='Directory where the designate python module is installed'
),

ie. it's missing sample_default='' that was in my patch.


Regards,

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

Bug#894452: RM: libdtdparser-java -- ROM; No longer used, FTBFS with Java 9

[Emmanuel Bourg]

Package: ftp.debian.org
Severity: normal

Hi,

Please remove the libdtdparser-java package. This is a former dependency
of ArgoUML that was left over after its removal 9 years ago (#508358).
This library is no longer used, has a low popcon, and now fails to build
with Java 9 (#893230).

Thank you,

Emmanuel Bourg

Bug#894365: virtualbox build depends on openjdk-8-jdk-headless

[Gianfranco Costamagna]

Still the same...
(the url is always the same as before)

/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/IUSBDeviceStateChangedEvent.java:25:
 error: package javax.xml.ws is not visible
import javax.xml.ws.*; ^ (package javax.xml.ws is declared in module 
java.xml.ws, which is not in the module graph)
/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/IEvent.java:25:
 error: package javax.xml.ws is not visible
import javax.xml.ws.*; ^ (package javax.xml.ws is declared in module 
java.xml.ws, which is not in the module graph)
/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/IUnknown.java:25:
 error: package javax.xml.ws is not visible
import javax.xml.ws.*; ^ (package javax.xml.ws is declared in module 
java.xml.ws, which is not in the module graph)
/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/VirtualBoxManager.java:25:
 error: package javax.xml.ws is not visible
import javax.xml.ws.*; ^ (package javax.xml.ws is declared in module 
java.xml.ws, which is not in the module graph)
/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/VirtualBoxManager.java:42:
 error: package javax.xml.ws is not visible
import javax.xml.ws.BindingProvider; ^ (package javax.xml.ws is declared in 
module java.xml.ws, which is not in the module graph)
/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/VirtualBoxManager.java:43:
 error: package javax.xml.ws is not visible
import javax.xml.ws.Holder; ^ (package javax.xml.ws is declared in module 
java.xml.ws, which is not in the module graph)
/<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/VirtualBoxManager.java:44:
 error: package javax.xml.ws is not visible
import javax.xml.ws.WebServiceException; ^



Il Venerdì 30 Marzo 2018 14:54, Emmanuel Bourg  ha scritto:



Le 30/03/2018 à 13:27, Gianfranco Costamagna a écrit :


> "/usr/lib/jvm/default-java/bin/javac" -encoding UTF-8 -source 1.9 -target 1.9 
> -Xlint:unchecked --add-modules java.xml.ws \
> 
> /<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/IUSBDeviceStateChangedEvent.java:25:
>  error: package javax.xml.ws is not visible
> import javax.xml.ws.*;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the 
> module graph)
> /<>/out/obj/vboxjws-gen/jwsgen/java/org/virtualbox_5_2/IEvent.java:25:
>  error: package javax.xml.ws is not visible
> import javax.xml.ws.*;
> ^
> 
> seems to make not much difference

That's slightly better since it no longer complains about the invalid
module name.

I wonder if this could be a javadoc error this time. Could you try
adding the same --add-modules option to VBOX_JAVADOC_OPTS?

Emmanuel Bourg

Bug#894330: apktool FTBFS with openjdk-9

[Markus Koschany]

Control: reassign -1 src:proguard

Hi,

this is a proguard bug. Version 5.3.3-1 works for me but 6.0.1-1 fails.
The reason is that the gradle.ProguardTask class is not included in
proguard-base.jar. The gradle/build.sh script requires the existence of
Gradle, fails to detect it because proguard doesn't build-depend on
gradle and thus the gradle plugin is not built at all.

I'm going to reassign the RC bugs for apktool and libsmali-java and
upload a new revision of proguard that build-depends on gradle again.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#894451: RFS: deepin-image-viewer/1.2.18-1

[Yanhao Mo]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "deepin-image-viewer"

* Package name: deepin-image-viewer
  Version : 1.2.18-1
  Upstream Author : Deepin Technology Co., Ltd
* URL : https://github.com/linuxdeepin/deepin-image-viewer
* License : GPL-3+
  Section : graphics

It builds those binary packages:

  deepin-image-viewer - Image Viewer for Deepin Desktop Environment

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

  https://mentors.debian.net/package/deepin-image-viewer

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-image-viewer/deepin-image-viewer_1.2.18-1.dsc

More information about hello can be obtained from
https://salsa.debian.org/pkg-deepin-team/deepin-image-viewer

Changes since the last upload:
  * Bug Fixes

This is team upload.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#889740: stretch update for xmotd

[Hugo Lefeuvre]

Hi Adrian,

> Thanks a lot for fixing this bug for unstable.
> 
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.

Feel free to take care of it if possible. Otherwise I'll do it, but it
might take some time.

Thanks !

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA


signature.asc
Description: PGP signature

Bug#891701: requires OSS, too

[Adam Borowski]

Looks like Synaesthesia doesn't work without OSS -- I don't see any options
to use any other audio sink, including even esound.  And, there are only
some shreds of OSS left in the kernel, capable of driving some pre-2000
sound cards.  There's some emulation but I don't know if it even still
works.  OSS4 fails to build with modern kernels and no one responded to the
FTBFS bug for two years.  So that's about it for OSS on Linux.  As for
kfreebsd, it seems to be on its way out.

Thus, Synaesthesia would need a fix to upstream code.  And I don't see one
coming...


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ When I visited the US a couple decades ago, Hillary molested and
⣾⠁⢰⠒⠀⣿⡁ groped me.  You don't believe?  Well, the burden of proof is on you!
⢿⡄⠘⠷⠚⠋⠀ Flooding a douche with obviously false accusations makes your other
⠈⠳⣄ words dubious even when they happen to be true.

Bug#894450: python-wsproto: Incomplete debian/copyright?

[Chris Lamb]

Source: python-wsproto
Version: 0.11.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sebastien Delafond 

Hi,

I just ACCEPTed python-wsproto from NEW but noticed it was missing 
attribution in debian/copyright for at least wsproto/utf8validator.py.

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


Regards,

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