Bug#874304: [pkg-gnupg-maint] Bug#874304: gpg: --refresh-keys became extremely verbose and complaining

[Werner Koch]

On Wed,  6 Sep 2017 22:21, invernom...@paranoici.org said:

> In the meantime, dear Werner, is there any additional information
> I could provide to help you in pinpointing the bug?

No, this is pretty obvious.  Although I would not call it a bug ;-)


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpSMHDWjktfO.pgp
Description: PGP signature

Bug#873012: not working live migration in qemu ( vm's block storage is LVM )

[David Lamorski]

Dear maintainer,

I can confirm the problem exists in qemu/1:2.8+dfsg-6+deb9u2.

-- 

Bug#874399: [ASK] sync mirror debian

[Agus Priyo]

Hi Admin,
Please tell me if wanna sync mirror debian from 
syncproxy2.wna.debian.org, because i can't again sync mirror from there. 
My mirror is http://mirror.poliwangi.ac.id/debian


thanks
Agus Priyo

Bug#874399: debian mirror mirror.poliwangi.ac.id issues

[Agus Priyo]

oh ok, i will try to use the newer ftpsync.

the first time I sync from ftp.th.debian.org after a few months and an 
error occurs, I switch to syncproxy2.wna.debian.org and it runs smoothly 
for several years, then another error a few days ago. when I try to 
access it immediately it asks for a password


ftpmaster @ mirror: ~ $ rsync syncproxy2.wna.debian.org::debian
Password:

then I try to sync from ftp.kr.debian.org, and then at this point I sync 
from cdimage.debian.org::debian but have not shown satisfactory results


it looks like I should try using the new ftpsync.
Thank you for the advice.

thanks
Agus Priyo

On 9/4/2017 6:32 PM, Peter Palfrader wrote:

Hi!

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

cf.
https://mirror-master.debian.org/status/mirror-info/mirror.poliwangi.ac.id.html

Please investigate.


Also:
o The tracefile
   http://mirror.poliwangi.ac.id/debian/project/trace/mirror.poliwangi.ac.id
   suggests that the ftpsync version you are using is very old.  Please upgrade.

   Using a modern ftpsync ensures updates are done in the correct order
   so apt clients don't get confused.   In particular, it processes
   translations, contents, and more files that have been added to the
   archive in recent years in the correct stage.  It also should produce
   trace files that contain more information that is useful for us.

   http://mirror.poliwangi.ac.id/debian/project/ftpsync/ftpsync-current.tar.gz

o we recommend mirrors not sync directly from service aliases such as
   ftp..debian.org (only http is guaranteed to be available at
   ftp..d.o sites).  Maybe change your config to sync from
   the site currently backing the ftp..debian.org service you sync
   from?

Bug#874399: [ASK] sync mirror debian

[Peter Palfrader]

On Fri, 08 Sep 2017, Agus Priyo wrote:

> Hi Admin,
> Please tell me if wanna sync mirror debian from syncproxy2.wna.debian.org,
> because i can't again sync mirror from there. My mirror is
> http://mirror.poliwangi.ac.id/debian

We try to have a well distributed mirroring hierarchy, and unfortunately
the resources on the syncproxies near the root of the tree are quite
limited.

Thus, we expect mirrors who sync off our syncproxies directly to carry
all archs, have set up push/ssh triggered mirroring, and to be very well
connected in their region and most importantly offer rsync and triggers
to downstream mirrors.

As such, I don't think your mirror currently is a good fit for mirroring
off our syncproxies.


Also, it seems that you successfully sync from ftp.kaist.ac.kr again, and you
have synced from that for about a month.

Yet, you still should refer to ftp.kaist.ac.kr as ftp.kaist.ac.kr and not as
ftp.kr.debian.org, and you should still update your ftpsync version.

If there's anything else we can help you with please let us know.
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#874622: ITP: ruby-gitlab -- Wrapper and CLI for the GitLab API

[Sophie Brun]

Package: wnpp
Severity: wishlist
Owner: Sophie Brun 

* Package name: ruby-gitlab
  Version : 4.1.0
  Upstream Author : Nihad Abbasov 
* URL : https://github.com/narkoz/gitlab
* License : BSD-2-clause
  Programming Lang: Ruby
  Description : Wrapper and CLI for the GitLab API

This gem is a Ruby wrapper and CLI for the GitLab API. It supports only
Ruby 2.0+.

I plan to maintain it in the Debian Ruby Team.

Bug#874623: unblock: cpl/7.0-5

[Ole Streicher]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package cpl.

The package no longer builds a package for the contrib area, so it
should be able to migrate to testing the normal way.

BTW, it would have been nice to contact me and discuss the problem
before just blocking the package. It is not so simple to find out the
cause, and the tracker is quite misleading here (it says that I should
check the freeze policy).

Thank you

Best regards

Ole

Bug#874624: ITP: ruby-terminal-table -- ASCII table generator

[Sophie Brun]

Package: wnpp
Severity: wishlist
Owner: Sophie Brun 

* Package name: ruby-terminal-table
  Version : 1.8.0
  Upstream Author : TJ Holowaychuk 
* URL : https://github.com/tj/terminal-table
* License : Expat
  Programming Lang: Ruby
  Description : ASCII table generator

This gem is a fast and simple, yet feature rich ASCII table generator.

This is a dependency of ruby-gitlab (ITP #869188).
I plan to maintain it in the Debian Ruby Team.

Bug#873012: not working live migration in qemu ( vm's block storage is LVM )

[Michael Schulz]

However, it's not necessary to have the vm block storage device on an LVM 
logical volume; live migration with --copy-storage-all also got stuck (as 
described above) when vm block storage is a qcow2 file on both sides.

Tested on 1:2.8+dfsg-6+deb9u2

Bug#863982: RFS: sphinx-autorun/1.0.4-1 [ITP]

[Félix Sipma]

sphinx-autorun is now updated to 1.1.0-1 on mentors. Could someone have a look
to this package? I can't finish the packaging of todoman because of this build
dependency...

Thanks!

On 2017-07-25 18:45+0200, Félix Sipma wrote:
> Package: sponsorship-requests
> Followup-For: Bug #863982
> 
> I updated the package on mentors to 1.0.4-1.
> 
> -- System Information:
> Debian Release: buster/sid
>  APT prefers unstable
>  APT policy: (990, 'unstable'), (500, 'stable'), (100, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.11.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 /usr/bin/dash
> Init: systemd (via /run/systemd/system)




signature.asc
Description: PGP signature

Bug#873012: not working live migration in qemu ( vm's block storage is LVM )

[Christian Ehrhardt]

On Fri, Sep 8, 2017 at 9:32 AM, Michael Schulz  wrote:

> However, it's not necessary to have the vm block storage device on an LVM
> logical volume; live migration with --copy-storage-all also got stuck (as
> described above) when vm block storage is a qcow2 file on both sides.
>
> Tested on 1:2.8+dfsg-6+deb9u2


Hi,
on the receiving end it only sees no more data coming which breaks it
 2017-08-23 17:29:28.615+: 7060: error : virNetSocketReadWire:1801 :
End of file while reading data: Input/output error

The error most likely happens (and needs to be debugged) on the sending
side of the migration:
I see these in the log:
2017-08-23 17:29:28.627+: 5958: info : qemuMonitorIOProcess:429 :
QEMU_MONITOR_IO_PROCESS: mon=0x7f907c001090 buf={"timestamp": {"seconds":
1503509368, "microseconds": 624377}, "event": "BLOCK_JOB_COMPLETED",
"data": {"device": "drive-ide0-0-0", "len": 2147483648, "offset": 0,
"speed": 9223372036853727232, "type": "mirror", "error": "Input/output
error"}}
 len=245
2017-08-23 17:29:28.627+: 5958: debug :
qemuMonitorJSONIOProcessLine:191 : Line [{"timestamp": {"seconds":
1503509368, "microseconds": 624377}, "event": "BLOCK_JOB_COMPLETED",
"data": {"device": "drive-ide0-0-0", "len": 2147483648, "offset": 0,
"speed": 9223372036853727232, "type": "mirror", "error": "Input/output
error"}}]
2017-08-23 17:29:28.627+: 5958: debug : virJSONValueFromString:1705 :
string={"timestamp": {"seconds": 1503509368, "microseconds": 624377},
"event": "BLOCK_JOB_COMPLETED", "data": {"device": "drive-ide0-0-0", "len":
2147483648, "offset": 0, "speed": 9223372036853727232, "type": "mirror",
"error": "Input/output error"}}

I happened to track down a similar issue in 2.10 in qemu, but I checked and
the issue I found was only applied after 2.8.
Also I didn't have the I/O errors like you have above.

You might check if you happen to have real I/O errors (showing up in demsg)
or if these are only qemu internal on the blockjob that the migration
triggered.

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Bug#869939: [Hyper-V] Feature request: pick up PTP Hyper-V timesync source from upstream 4.12

[Moritz Schlarb]

Control: found -1 linux/4.9.30-2
Control: found 85 linux/4.9.30-2
Control: block 85 by -1

I want to heavily second this request!
In stretch-backports, we have 4.12 now, but as we are having quite a lot
of Jessie machines, we are hoping for a solution for jessie, too (even
if it were having 4.12 in jessie-backports-sloppy).

FWIW, here is the same request from Josh in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676635
and that had already been closed some time ago.

ATM, Debian is not listed as supporting "Windows Server 2016 Accurate
Time" on
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-debian-virtual-machines-on-hyper-v,
whereas Ubuntu is on
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v

Hope there's something that can be done here ;-)

-- 
Moritz Schlarb
Unix-Gruppe | Systembetreuung
Zentrum für Datenverarbeitung
Johannes Gutenberg-Universität Mainz
Raum 01-331 - Tel. +49 6131 39-29441
OpenPGP Fingerprint: DF01 2247 BFC6
5501 AFF2 8445 0C24 B841 C7DD BAAF
<>

Bug#874625: RM: maven-plugin-testing-1.3 -- ROM; No longer used

[Emmanuel Bourg]

Package: ftp.debian.org
Severity: normal

Hi,

Please remove the maven-plugin-testing-1.3 package, this was a temporary
package required for the transition to Maven 3. It's no longer used nor
necessary now.

Thank you,

Emmanuel Bourg

Bug#874621: screen lock cannot be unlocked in vnc session

[Simon McVittie]

On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote:
> Now I have to kill gnome-shell and use metacity to not lose the session
> or kill vncserver and restart session.

You might also be able to use loginctl to list sessions, then something
like "loginctl unlock-session 42" to unlock your session.

I'm somewhat surprised GNOME Shell works over VNC at all, given its
reliance on GL. Please describe your VNC session setup?

S

Bug#846094: cpl_mask.c: Unaligned access

[Ole Streicher]

Control: tag -1 upstream
Control: forwarded -1 PIPE-3890

I reported this upstream a few years ago already under the id PIPE-3890,
but they still didn' fix it. Since the bug database is not public, an
URL is not given.

@Aaron: Could you give me the predefined cpp macro specific for Sparc64?
I'll add it then.

Thanks

Ole

Bug#874621: screen lock cannot be unlocked in vnc session

[Simon McVittie]

On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote:
> package: gnome-shell
> version: 3.22.3-3
> 
> This broke after a dist upgrade in sid yesterday.

What did you upgrade? Please look at /var/log/apt/*.log*. gnome-shell
hasn't been updated in sid since April, so unless your sid installation
was previously extremely outdated, it wasn't a gnome-shell upgrade that
triggered this.

After upgrading whatever packages triggered this, did you reboot, or
log out and back in, or neither? If you didn't do either, the old
gnome-shell will have continued to run with the old libraries, in which
case we'd need to know which gnome-shell version and relevant libraries
(clutter, mutter, gtk, gdk-pixbuf) were installed at the time you
started the VNC session.

Are there any relevant messages in syslog, the systemd Journal,
~/.cache/gdm/session.log (if you use gdm), or ~/.xsession-errors?

(Also, in future please use reportbug, which would have listed all the
relevant packages after your upgrade already.)

Bug#874626: nmu: gnuradio_3.7.11-1 gr-osmosdr_0.1.4-12

[Raphaël Hertzog]

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

nmu gnuradio_3.7.11-1 . ANY . unstable . -m "Rebuild for codecs2 transition"
nmu gr-osmosdr_0.1.4-12 . ANY . unstable . -m "Rebuild for soapysdr transition"

(note gr-osmosdr is already at +b1)

Both packages need to be rebuilt against newer libraries to be able to migrate
to testing.

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

Kernel: Linux 4.12.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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#848090: haveged/systemd somehow clutter up /var/tmp

[intrigeri]

Control: tag -1 + moreinfo
Control: tag -1 + unreproducible

Hi,

Christoph Anton Mitterer:
> I've noticed this on all my systems:
> /var/tmp# ls -al
> total 0
> drwxrwxrwt 1 root root 107210 Dec 13 18:46 .
> drwxr-xr-x 1 root root 90 Mar  4  2012 ..
> drwx-- 1 root root  6 Jun  9  2016 
> systemd-private-0a274b7a4a4d4a2598c6c57c1313a4e3-haveged.service-OOFnxD
> drwx-- 1 root root  6 Sep 27  2015 
> systemd-private-0a406a21c1474b1fbb2502e54773f450-haveged.service-YZgxXX
> drwx-- 1 root root  6 Mar 27  2016 
> systemd-private-0a1020ae163942a8a49e8a20613e6fc8-haveged.service-cWLH4v
> [...]

> Each of these dirs contains:
> drwxrwxrwt 1 root root0 Oct  6 23:02 tmp
> (with different dates of course) which in turn are all empty.

According to /usr/lib/tmpfiles.d/tmp.conf these are "namespace
mountpoints created with PrivateTmp=yes" and they should all be
cleaned up at boot time (except the one created during the current
boot). And as expected, on my sid system I see only one of those.

Do you have anything in /etc/tmpfiles.d/ that might override the
default settings? (I'll assume you haven't modified the defaults in
/usr/lib/tmpfiles.d/ :)

Also, can you please share the output of:

  systemctl status systemd-tmpfiles-setup.service 

?

Cheers,
-- 
intrigeri

Bug#814654: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

[Andreas Beckmann]

> > When updating the nvidia-driver package to 352.79-2 from 352.79-1, 
> > primusrun and optirun
> > become unusable and return an error:
> > primus: fatal: Bumblebee daemon reported: error:
> > [XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
> > Permission denied

Is this still an issue with the latest drivers in stable, unstable or
experimental (375.xx or newer)?


Andreas

Bug#874628: ITP: ruby-flipper --Feature flipper for ANYTHING

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/flipper

dependency of gitlab 9.5







signature.asc
Description: OpenPGP digital signature

Bug#873012: not working live migration in qemu ( vm's block storage is LVM )

[Michael Schulz]

Am 08.09.2017 um 09:55 schrieb Christian Ehrhardt 
:

> I happened to track down a similar issue in 2.10 in qemu, but I checked and 
> the issue I found was only applied after 2.8.
> Also I didn't have the I/O errors like you have above.
> 
> You might check if you happen to have real I/O errors (showing up in demsg) 
> or if these are only qemu internal on the blockjob that the migration 
> triggered.

I do not see any I/O errors in log or something showing up in dmesg.

When I start the migration, VM keeps running on source host. On the target 
host, the qemu process for the vm appears in "virsh list" in "paused" state. 
Then both qemu processes stay in this deadlocked situation forever. However, I 
can see (of course encrypted) network traffic between source and target system 
on libvirt tls port 16514/tcp. I think this could be some kind of polling 
request from the target qemu instance, as the source process doesn't start the 
data transport (?).

However, I don't have any idea how to debug this any deeper.

-- 
Michael Schulz

Bug#873901: fonts-tlwg-waree: Adequate shows obsolete conffile for fonts-tlwg-waree

[Theppitak Karoonboonyanan]

All right. I can reproduce it on a clean schroot at last.

And the flaw is the missing epoch in the prior-version
parameter for rm_conffile maintscript.

This change should fix it:

diff --git a/debian/fonts-tlwg-loma.maintscript
b/debian/fonts-tlwg-loma.maintscript
index a8034b8..dcd9947 100644
--- a/debian/fonts-tlwg-loma.maintscript
+++ b/debian/fonts-tlwg-loma.maintscript
@@ -1,5 +1,5 @@
-rm_conffile /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf 0.6.3-1~
fonts-tlwg-loma
-rm_conffile /etc/fonts/conf.avail/89-tlwg-loma-synthetic.conf
0.6.3-1~ fonts-tlwg-loma
+rm_conffile /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf 1:0.6.3-1~
fonts-tlwg-loma
+rm_conffile /etc/fonts/conf.avail/89-tlwg-loma-synthetic.conf
1:0.6.3-1~ fonts-tlwg-loma

-rm_conffile /etc/fonts/conf.d/64-12-tlwg-loma.conf 0.6.3-1~ fonts-tlwg-loma
-rm_conffile /etc/fonts/conf.avail/64-12-tlwg-loma.conf 0.6.3-1~ fonts-tlwg-loma
+rm_conffile /etc/fonts/conf.d/64-12-tlwg-loma.conf 1:0.6.3-1~ fonts-tlwg-loma
+rm_conffile /etc/fonts/conf.avail/64-12-tlwg-loma.conf 1:0.6.3-1~
fonts-tlwg-loma
diff --git a/debian/fonts-tlwg-waree.maintscript
b/debian/fonts-tlwg-waree.maintscript
index 159db5c..5def0d2 100644
--- a/debian/fonts-tlwg-waree.maintscript
+++ b/debian/fonts-tlwg-waree.maintscript
@@ -1,2 +1,2 @@
-rm_conffile /etc/fonts/conf.d/89-tlwg-waree-synthetic.conf 0.6.3-1~
fonts-tlwg-waree
-rm_conffile /etc/fonts/conf.avail/89-tlwg-waree-synthetic.conf
0.6.3-1~ fonts-tlwg-waree
+rm_conffile /etc/fonts/conf.d/89-tlwg-waree-synthetic.conf 1:0.6.3-1~
fonts-tlwg-waree
+rm_conffile /etc/fonts/conf.avail/89-tlwg-waree-synthetic.conf
1:0.6.3-1~ fonts-tlwg-waree

I'm committing it soon. Thanks for catching it.

Regards,
-- 
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/

Bug#874208: octave: audiodevinfo makes octave segfault when jackd is running

[Peter P.]

* Mike Miller  [2017-09-08 05:35]:
> On Thu, Sep 07, 2017 at 18:08:40 +0200, Peter P. wrote:
> > Thanks for the clear instructions Mike, here it is:
> > 
> > ~$ gdb --args octave-cli
> > [...]
> > Reading symbols from octave-cli...Reading symbols from 
> > /usr/lib/debug/.build-id/a7/beba93cf5339eac11d645050513a47c65388a8.debug...done.
> 
> Thanks, that looks better.
> 
> So a segmentation fault occurs in a jack client thread that must start
> as a result of jack_activate, which is called by Pa_Initialize.
> 
> I don't have a jack setup to try this on at the moment. It would be
> useful to see if someone else can reproduce, and also to see if other
> PortAudio-based programs or simple demos work with jack.
The two other programs I have installed that are using libportaudio2 are
pure-data and audacity. And they both work with and without jack.

Bug#873900: Pending fixes for bugs in the fonts-tlwg package

[pkg-fonts-devel]

tag 873900 + pending
tag 873901 + pending
thanks

Some bugs in the fonts-tlwg package are closed in revision
b3bdee4435dc355a0abc00741ec419f4773ed330 in branch 'master' by
Theppitak Karoonboonyanan

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-fonts/fonts-tlwg.git;a=commitdiff;h=b3bdee4

Commit message:

Fix rm_conffile maintscript

- debian/fonts-tlwg-loma.maintscript:
- debian/fonts-tlwg-waree.maintscript:
  Add missing epoch in  parameter of rm_conffile,
  so the maintscripts become effective.
  Thanks Shirish Agarwal for the report. (Closes: #873900, #873901)

Bug#874539: libarchive: CVE-2017-14166: heap-based buffer overflow in xml_data (archive_read_support_format_xar.c)

[Chris Lamb]

Hi,

Curiously I can't reproduce this on sid. autopkgtest attached, but the
result is:

  archive_read_open_filename() failed: Unrecognized archive format
  ASSERT:Status code expected:<226> but was:<0>

ie. not a crash.

(Maintainers, please consider adding this test to your package!)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/tests/CVE-2017-14166 b/debian/tests/CVE-2017-14166
new file mode 100644
index 000..952a7e3
--- /dev/null
+++ b/debian/tests/CVE-2017-14166
@@ -0,0 +1,28 @@
+#!/bin/sh
+#
+# Test CVE-2017-14166
+
+setUp() {
+   gcc -O2 -g -Wno-unused-result -o untar examples/untar.c \
+   $(pkg-config --cflags --libs libarchive)
+
+   uudecode >archive.xar <

Bug#775012: nvidia-driver: startx initializes nvidia driver but kdm does not

[Andreas Beckmann]

Control: tag -1 moreinfo

On Fri, 9 Jan 2015 17:57:08 -0600  wrote:
> I installed Jessie on a Lenovo W530 with BIOS set to NVIDIA Optimus and
> OS Detection enabled.
> 
> I wanted to use the NVIDIA discrete graphics so I changed the BIOS to
> Discrete Graphics with OS detection disabled, and installed
> nvidia-driver from the repository. I edited /etc/default/grub to add
> the kernel options "nox2apic rcutree.rcu_idle_gp_delay=1".
> 
> This worked through several reboots, for about a day. After that the
> machine froze when the NVIDIA logo should have appeared: the screen
> backlight turned off, the hard drive stopped spinning, and the only
> action that had effect was holding the power button down to power off.
> 
> When I rebooted in single-user mode I discovered I could startx as
> root. The NVIDIA logo appeared, then the kdm login screen. Once I had
> logged in I could log out, kdm would restart, and I could log in
> normally. This lasted about a day, then kdm would not re-start after I
> ended a root session.
> 
> I purged (not removed) *everything* related to NVIDIA, and
> re-installed. I was able to boot normally just ONCE.
> 
> I disabled kdm so I could startx with logverbose 6 and capture the
> failure. Instead kdm started normally.
> 
> The Xorg.0.log below is from starting as a normal user at the console;
> Xorg.0.log.old is the result of trying to boot normally straight to kdm.

Is this issue still present with the latest drivers in
stable/unstable/experimental? (375.xx or newer). There is no more kdm in
stable nowadays ...

Andreas

Bug#779295: nvidia-driver: Problems with software using OpenGL after nvidia-driver install

[Andreas Beckmann]

Control: tag -1 moreinfo

On Thu, 26 Feb 2015 18:22:56 +0100
=?utf-8?q?Jos=C3=A9_Luis_Garc=C3=ADa_Pallero?=  wrote:

> I have a laptop running Debian Sid with an integrated Intel graphic card and a
> NVIDIA Quadro K2100M. I want use the Quadro ONLY for CUDA tests and the Intel
> card for the normal day work. Until now, I usually install the *.run NVIDIA
> driver (blacklisting the nouveau kernel module) but I configure the xorg.conf
> in order to use the Intel graphic card (see below the <<
> /etc/X11/xorg.conf >> section). One problem of this procedure is that
> after the NVIDIA driver installation I can't use some programs that use OpenGL
> for drawing, line the native graphics of GNU Octave (either the official 
> Debian
> package or the program compiled by myself). The error emitted by Octave is:

Hi,

is this issue still reproducible with the latst drivers in
stable/unstable/experimental (375.xx or newer)?


Andreas

Bug#874629: python-otb: PYTHONPATH not updated by python-otb package

[Manuel Grizonnet]

Package: python-otb
Version: 6.0.0+dfsg-1~xenial1
Severity: normal

Dear Maintainer,

the python-otb package (python lib for otb applications) does not work 
out of
the box on my system. The otbApplication Python package is not found 
automatically.


The command to reproduce the issue (just try to import otbApplication):

python
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import otbAplication
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named otbAplication

I think that the package installation should probably update the 
PYTHONPATH and

add the path to the otbApplication.py library.

On my system the library is located in /usr/lib/otb/python folder.

Regards,


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-93-generic (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-otb depends on:
ii  dh-python  2.20151103ubuntu1.1
ii  libc6  2.23-0ubuntu9
ii  libgcc11:6.0.1-0ubuntu1
ii  libinsighttoolkit4.9   4.9.0-4ubuntu1.1
ii  libotb-apps6.0.0+dfsg-1~xenial1
ii  libotbapplicationengine-6.0-1  6.0.0+dfsg-1~xenial1
ii  libotbmetadata-6.0-1   6.0.0+dfsg-1~xenial1
ii  libotbossimadapters-6.0-1  6.0.0+dfsg-1~xenial1
ii  libpython2.7   2.7.12-1ubuntu0~16.04.1
ii  libstdc++6 5.4.0-6ubuntu1~16.04.4
ii  python 2.7.11-1

python-otb recommends no packages.

python-otb suggests no packages.

-- no debconf information

--
Manuel GRIZONNET

Bug#837549: Various crashes not produced by kdenlive, but in main libc functions / nvidia non-free driver

[Andreas Beckmann]

Control: merge 837549 847473 847475
Control: tag -1 moreinfo

On Tue, 24 Jan 2017 09:01:08 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?=
 wrote:
> All those crashes happened in the display manager / Qt / libc, not
> kdenlive and I believe the non-free nvidia driver is the fault here.

Is this issue still reproducible with the latest nvidia driver in
stable/unstable/experimental (375.xx or newer)?


Andreas

Bug#874621: screen lock cannot be unlocked in vnc session

[Pirate Praveen]

On 09/08/2017 01:46 PM, Simon McVittie wrote:
> On Fri, 08 Sep 2017 at 12:22:37 +0530, Pirate Praveen wrote:
>> package: gnome-shell
>> version: 3.22.3-3
>>
>> This broke after a dist upgrade in sid yesterday.
> What did you upgrade? Please look at /var/log/apt/*.log*. gnome-shell
> hasn't been updated in sid since April, so unless your sid installation
> was previously extremely outdated, it wasn't a gnome-shell upgrade that
> triggered this.
attaching the dist-upgrade log
>
> After upgrading whatever packages triggered this, did you reboot, or
> log out and back in, or neither? If you didn't do either, the old
> gnome-shell will have continued to run with the old libraries, in which
> case we'd need to know which gnome-shell version and relevant libraries
> (clutter, mutter, gtk, gdk-pixbuf) were installed at the time you
> started the VNC session.
I rebooted.

tigervnc-standalone-server 1.7.0+dfsg-7

updated vnc libs: libgvnc-1.0-0:amd64 (0.6.0-3, 0.7.1-1),
libgtk-vnc-2.0-0:amd64 (0.6.0-3, 0.7.1-1),

attaching .vnc/xstartup

>
> Are there any relevant messages in syslog, the systemd Journal,
> ~/.cache/gdm/session.log (if you use gdm), or ~/.xsession-errors?
I use gdm, but there is no ~/.cache/gdm folder. Nothing in

~/.xsession-errors

> (Also, in future please use reportbug, which would have listed all the
> relevant packages after your upgrade already.)


Start-Date: 2017-09-07  12:29:08
Commandline: apt-get dist-upgrade
Requested-By: pravi (1000)
Install: fdisk:amd64 (2.29.2-4, automatic), libx265-130:amd64 (2.5-2, automatic), libgcc-7-dev:amd64 (7.2.0-4, automatic), libpython3.6-minimal:amd64 (3.6.2-5, automatic), libfyba0:amd64 (4.1.1-3, automatic), gir1.2-nm-1.0:amd64 (1.8.2-1, automatic), libvulkan1:amd64 (1.0.54.0+dfsg1-1, automatic), gnupg1-l10n:amd64 (1.4.22-1, automatic), gnupg-utils:amd64 (2.2.0-1, automatic), gedit-plugin-dashboard:amd64 (3.22.0-2, automatic), python3-olefile:amd64 (0.44-1, automatic), python-configparser:amd64 (3.5.0-1, automatic), gpg-wks-client:amd64 (2.2.0-1, automatic), libegl1:amd64 (0.2.999+git20170802-3, automatic), libblockdev-swap2:amd64 (2.12-2, automatic), libmaven-resolver-java:amd64 (1.0.3-2, automatic), udftools:amd64 (1.3-1, automatic), sntp:amd64 (1:4.2.8p10+dfsg-5, automatic), gir1.2-gepub-0.5:amd64 (0.5.2-1, automatic), libdw1:amd64 (0.168-1, automatic), gnome-user-docs:amd64 (3.25.90-2, automatic), libegl-mesa0:amd64 (17.2.0-2, automatic), libcommons-compress-java:amd64 (1.13-1, automatic), libarchive-cpio-perl:amd64 (0.10-1, automatic), libraw16:amd64 (0.18.2-2, automatic), libgslcblas0:amd64 (2.4+dfsg-6, automatic), gnupg1-curl:amd64 (1.4.22-1, automatic), libgl1:amd64 (0.2.999+git20170802-3, automatic), mdadm:amd64 (4.0-1, automatic), fonts-smc-karumbi:amd64 (1.0-1, automatic), cpp-7:amd64 (7.2.0-4, automatic), python-future:amd64 (0.15.2-4, automatic), python-automat:amd64 (0.6.0-1, automatic), libpython3.6-stdlib:amd64 (3.6.2-5, automatic), python3-asn1crypto:amd64 (0.22.0-1, automatic), libemf1:amd64 (1.0.9+git.10.3231442-1, automatic), fonts-smc-chilanka:amd64 (1.2.0-1, automatic), perl-modules-5.26:amd64 (5.26.0-7, automatic), libmaven-shared-utils-java:amd64 (3.1.0-1, automatic), libdap25:amd64 (3.19.0-1, automatic), gedit-plugin-multi-edit:amd64 (3.22.0-2, automatic), gpg-wks-server:amd64 (2.2.0-1, automatic), python3.6:amd64 (3.6.2-5, automatic), plymouth-label:amd64 (0.9.2-5, automatic), gpg:amd64 (2.2.0-1, automatic), libblockdev-crypto2:amd64 (2.12-2, automatic), fonts-smc-meera:amd64 (7.0-1, automatic), libsub-quote-perl:amd64 (2.004000-1, automatic), python-certifi:amd64 (2017.4.17-2, automatic), gedit-plugin-bracket-completion:amd64 (3.22.0-2, automatic), fonts-smc-raghumalayalamsans:amd64 (2.1.1-1, automatic), libnotmuch5:amd64 (0.25-6, automatic), libasan4:amd64 (7.2.0-4, automatic), libgles2:amd64 (0.2.999+git20170802-3, automatic), libblockdev-loop2:amd64 (2.12-2, automatic), libsnappy-jni:amd64 (1.1.4-1, automatic), libvoikko1:amd64 (4.1.1-1, automatic), libblockdev-fs2:amd64 (2.12-2, automatic), bubblewrap:amd64 (0.1.8-3, automatic), libntfs-3g872:amd64 (1:2016.2.22AR.2-2, automatic), libblockdev-part2:amd64 (2.12-2, automatic), fonts-smc-keraleeyam:amd64 (2.0-1, automatic), fonts-smc-suruma:amd64 (3.2.1-1, automatic), gedit-plugin-zeitgeist:amd64 (3.22.0-2, automatic), python3-unidiff:amd64 (0.5.4-1, automatic), libgsl23:amd64 (2.4+dfsg-6, automatic), libxmlsec1-nss:amd64 (1.2.24-4, automatic), chromium-common:amd64 (60.0.3112.78-1, automatic), libjim0.77:amd64 (0.77-2, automatic), golang-1.8-src:amd64 (1.8.3-2, automatic), libperl5.26:amd64 (5.26.0-7, automatic), python3.6-minimal:amd64 (3.6.2-5, automatic), libgmime-3.0-0:amd64 (3.0.1-4, automatic), gedit-plugin-draw-spaces:amd64 (3.22.0-2, automatic), binutils-x86-64-linux-gnu:amd64 (2.29-9, automatic), libstdc++-7-dev:amd64 (7.2.0-4, automatic), evolution-plugin-bogofilter:amd64 (3.24.5-3, automatic), libllvm5.0:amd64 (1:5.0-1, automatic), libglib2.0-dev-bin:amd64 (2.53.6-1, 

Bug#848385: libnvidia-glcore: Game "Dota 2" unable to launch with Vulkan API

[Andreas Beckmann]

Control: tag -1 moreinfo

On Sat, 17 Dec 2016 15:24:17 + Luca Boccassi
 wrote:
> Control: tags -1 upstream
> 
> On Sat, 2016-12-17 at 02:00 +0100, Pau Gisbert wrote:
> > Launching the game "Dota 2" with `-vulkan` (forcing the use of Vulkan API) 
> > is unsuccessful, it crashes before launching. 
> > 
> > I have 
> > [reported](https://github.com/ValveSoftware/Dota-2-Vulkan/issues/159#issuecomment-267728390)
> >  this to the relevant issue tracker at valve and they have let me know this 
> > is a crash on the nvidia library, not related to the game.
> > 
> > [Here](https://github.com/ValveSoftware/Dota-2-Vulkan/files/658539/crash_20161217012608_1.zip)'s
> >  a crash dump file which I hope is useful since It's what Valve requests 
> > when filing bug reports.
> > 
> > Please let me know if there's some further troubleshoot steps i can take to 
> > help find and fix this bug.
> > 
> > Kind regards.
> 
> Can reproduce it, but it's fixed by lowering the graphics settings. Try
> restarting the game without -vulkan, lower the settings and try again
> with -vulkan.
> 
> Probably the same as:
> 
> https://github.com/ValveSoftware/Source-1-Games/issues/57
> 
> It really shouldn't crash due to this, so I suggest reporting this
> upstream.
> Nothing we can do in the packaging could help since this is the
> proprietary driver.

Is this issue still present with the latest drivers in
stable/unstable/experimental, i.e. 375.xx or newer?

Andreas

Bug#859154: nvidia-driver: freeze and crash

[Andreas Beckmann]

Control: tag -1 moreinfo upstream

On Thu, 30 Mar 2017 21:30:28 -0400 Xavier Ortiz  wrote:
> Package: nvidia-driver
> Version: 375.39-1

>* What led up to the situation?
> played a game. Eve online
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> logged out of game

Hi,

is this issue still present with the latest drivers (375.82 or newer)?


Andreas

Bug#874630: FTBFS with Java 9: javax.activation

[Chris West]

Source: libaxiom-java
Version: 1.2.8
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.


The wiki has some common problems and their solutions, including this
javax.activation change. No solution, as of today, though!
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
project axiom-api: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: There was an 
error in the forked process
[ERROR] java.lang.NoClassDefFoundError: javax/activation/DataSource
[ERROR] at java.base/java.lang.Class.getDeclaredMethods0(Native Method)
[ERROR] at 
java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3139)
[ERROR] at 
java.base/java.lang.Class.getMethodsRecursive(Class.java:3280)
[ERROR] at java.base/java.lang.Class.getMethod0(Class.java:3266)
[ERROR] at java.base/java.lang.Class.getMethod(Class.java:2063)
[ERROR] at 
org.apache.maven.surefire.common.junit3.JUnit3Reflector.createInstanceFromSuiteMethod(JUnit3Reflector.java:153)
[ERROR] at 
org.apache.maven.surefire.common.junit3.JUnit3Reflector.constructTestObject(JUnit3Reflector.java:124)
[ERROR] at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:74)
[ERROR] at 
org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:136)
[ERROR] at 
org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:109)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:291)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
[ERROR] at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
[ERROR] Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource
[ERROR] at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
[ERROR] at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
[ERROR] at 
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
[ERROR] ... 13 more
[ERROR] -> [Help 1]



Cheers,
Chris.

Bug#874626: nmu: gnuradio_3.7.11-1 gr-osmosdr_0.1.4-12

[Raphael Hertzog]

Hi,

On Fri, 08 Sep 2017, Raphaël Hertzog wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu gnuradio_3.7.11-1 . ANY . unstable . -m "Rebuild for codecs2 transition"

Here it seems to be last and only update needed of the codecs2 (uncoordinated) 
transition.

> nmu gr-osmosdr_0.1.4-12 . ANY . unstable . -m "Rebuild for soapysdr 
> transition"

But this one seems to be part of two unreported transitions that affect more 
packages:
https://release.debian.org/transitions/html/auto-uhd.html
(and soapysdr that has no auto-tracker page but which seems to be complete 
after the gr-osmosdr
bin-nmu)

nmu osmo-trx_0~20170323git2af1440+dfsg-1 . ANY . unstable . -m "Rebuild for uhd 
transition"
nmu soapyuhd_0.3.3-1 . ANY . unstable . -m "Rebuild for uhd transition"
nmu gr-radar_0.0.0.20160615-3 . ANY . unstable . -m "Rebuild for uhd transition"
nmu gnss-sdr_0.0.9-5 . ANY . unstable . -m "Rebuild for uhd transition"

Maitland, Andreas, it would be nice if you could handle library transitions
in coordination with the release team:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions

It would also be nice if you could ensure that gnuradio doesn't get
removed from testing.

FWIW, I investigated this because Kali Linux is based on Debian Testing
and we are gnuradio users so when gnuradio gets out of testing, I
immediately notice it.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#874631: FTBFS with Java 9: com.sun.tools.javac

[Chris West]

Source: libcommons-jexl2-java
Version: 2.1.1
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The class being used here has long been deprecated, and tools.jar has
finally had its long awaited cleanup. Perhaps move to the Java 7 API?

Build log:

Results :

Tests in error: 
  ClassCreatorTest.testMany:123 ?? ClassNotFound com.sun.tools.javac.Main
  ClassCreatorTest.testOne:98 ?? ClassNotFound com.sun.tools.javac.Main

Tests run: 275, Failures: 0, Errors: 2, Skipped: 0


Cheers,
Chris.

Bug#783303: re: chromium: Chromium crash after nVidia driver upgrade

[Andreas Beckmann]

Control: tag -1 moreinfo

On Sun, 26 Apr 2015 21:15:08 -0400 Michael Gilbert 
wrote:
> control: reassign -1 src:nvidia-graphics-drivers
> 
> Proprietary driver issues aren't supported.

Hi,

is this issue still present with the latest versions of chromium and the
nvidia driver?


Andreas

Bug#842582: nvidia-driver: Screen displays boot string on powersave

[Andreas Beckmann]

Control: tag -1 moreinfo

On Sun, 30 Oct 2016 11:23:30 -0400 Nigel Horne  wrote:
> Package: nvidia-driver
> Version: 367.44-3

> After a few minutes instead of the display being put into standby or the
> screen-saver kicking in, the display flashes the boot text repeatedly. Nothing
> works except for "Alt-F7" which blanks the screen.  The only way out of it
> is to ssh in from another machine and reboot.

Hi,

is this still happening with the latest drivers in
stable/unstable/experimental, i.e. 375.xx or newer?


Andreas

Bug#741498: nvidia-kernel-dkms: fails to build for self-compiled 3.12.x kernel

[Andreas Beckmann]

On Fri, 6 Jun 2014 22:28:29 +0200 Alexander Hofbauer
 wrote:
> > This looks like it is related to your kernel configuration, it works fne
> > on the Debian stock kernel.
> 
> 
> I'm not a sure whether the kernel config is to blame here.
> 
> Trying to compile for 3.15-rc8 I get exactly the same error. Might be a
> coincidence, but nevertheless I was able to trace back the problem to
> conftest.h not being able to correctly test for kernel version.
> 
> E.g. "testing for >= 3,10,0" always chooses the else branch (verified by
> adding an #error statement there).
> 
> Further tests (manually resolving every define in conftest.h) yielded a
> compiling and loading kernel module.

Is this issue still present with the latest drivers available in stable,
unstable or experimental? The module build infrastructure was completely
overhauled since this bug was reported ...


Andreas

Bug#874632: texinfo: inconsistent papersize for generated dvi and ps

[Vincent Lefevre]

Package: texinfo
Version: 6.4.90.dfsg.1-1+b1
Severity: important

When generating the MPFR manual, the contents are always in A4.
FYI, the mpfr.texi file has:

@iftex
@afourpaper
@end iftex

But on one of my machines (from which this bug is reported), the
generated dvi and ps have a letter papersize, so that the contents
may be partly truncated. Note that another Debian/unstable machine
(which has the same config, AFAIK) does not have this issue.

This silently occurs, so that for instance, one may upload incorrect
files to a web server, which is really annoying.

The generated pdf is OK on both machines (a4 contents, a4 papersize).

In case this matters (but this shouldn't), the paperconf command
outputs a4 on both machines.

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

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

Versions of packages texinfo depends on:
ii  libc6   2.24-17
ii  libtext-unidecode-perl  1.30-1
ii  libxml-libxml-perl  2.0128+dfsg-3
ii  perl5.26.0-5
ii  perl-base [perlapi-5.26.0]  5.26.0-5
ii  tex-common  6.09

texinfo recommends no packages.

Versions of packages texinfo suggests:
ii  texinfo-doc-nonfree  6.4.0-1
ii  texlive-base 2017.20170818-1
ii  texlive-fonts-recommended2017.20170818-1
ii  texlive-generic-recommended  2017.20170818-1
ii  texlive-latex-base   2017.20170818-1

-- no debconf information

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

[Andreas Beckmann]

On Sun, 10 Jul 2016 21:37:18 +0100 Luca Boccassi
 wrote:
> On Sun, 2016-07-10 at 21:54 +0200, Peter Keel wrote:
> > Hi
> > 
> > * on the Sun, Jul 10, 2016 at 08:23:23PM +0100, Luca Boccassi wrote:
> > > I am running the same driver with 4.6 from Jessie backports, and I'm not
> > > seeing that problem. Are you sure it's not due to the custom kernel?
> > 
> > Pretty sure, as it did work maybe two weeks ago with 4.5.7 and the
> > same kernel config. And I also tried to recompile it now with the
> > old kernel 4.5.7, it also has no versions anymore.
> > 
> > I think it's something that changed in the toolchain within debian/sid.
> > Not necessarily the nvidia-kernel-dkms package (because I didn't 
> > change that one neither) but that's probably where it would need to
> > be mitigated, so I reported the bug there.
> > 
> > > Could you please try with the kernel from the repositories so that we
> > > can narrow it down a bit more?
> > 
> > I'll look into that. 
> 
> Just tried in a sid chroot with 367.27 from SVN and the latest kernel
> headers, all seems fine:
> 
> root@luca-desktop:/# modprobe --dump-modversions 
> /lib/modules/4.6.0-1-amd64/updates/dkms/nvidia-current.ko 
> 0xa435bbb2module_layout
> 0x6bc3fbc0__unregister_chrdev
> 0x5150c634acpi_bus_register_driver

Is this still an issue with latest drivers (375.xx or newer) and kernels?

Andreas

Bug#785598: nvidia-vdpau-driver: routine upgrades again install a nvidia driver on non-nvidia hardware

[Andreas Beckmann]

Control: tag -1 moreinfo

On Mon, 18 May 2015 09:02:39 +0200 jsb...@mimuw.edu.pl (Janusz S.
=?utf-8?Q?Bie=C5=84?=) wrote:
> Package: nvidia-vdpau-driver
> Version: 340.65-2
> Severity: minor
> 
> Dear Maintainer,
> 
> Please reassign as appropriate.
> 
> Contrary to the previous case
> 
>  #769072: Broken graphics due to libgl1-nvidia-glx auto-install on
>  non-nvidia hardware
> 
> I get only warnings, e.g. when calling vlc
> 
>   modprobe: ERROR: could not insert 'nvidia_current': No such device
> 
> I can live with it, especially as I will stop to use the computer in
> question in a few weeks.
> 
> I report the bug just for information that such things happen.

I have no idea how to reproduce this, i.e. what packages need to be
installed such that an upgrade pulls in nvidia bits.


Andreas

Bug#874403: debian mirror mirrors.asnet.am issues

[Arthur Petrosyan]

Hi!


9/6/2017 17:50, Peter Palfrader пишет:

On Wed, 06 Sep 2017, Arthur Petrosyan wrote:


We at ASNET-AM are comleted our 'mirrors.asnet.am' Mirror Upgrade and now
are supporting ALL architectures for Debian Archive.

Great, thanks!

o The tracefile
   http://mirrors.asnet.am/debian/project/trace/mirrors.asnet.am
   suggests that the ftpsync version you are using is a bit dated.
   Please upgrade.

   Using a modern ftpsync ensures updates are done in the correct order
   so apt clients don't get confused.   In particular, it processes
   translations, contents, and more files that have been added to the
   archive in recent years in the correct stage.  It also should produce
   trace files that contain more information that is useful for us.

   http://ftp.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz

Upgraded !

o we recommend mirrors not sync directly from service aliases such as
   ftp.fr.debian.org (only http is guaranteed to be available at
   ftp..d.o sites).  Maybe change your config to sync from
   the site currently backing the ftp.fr.debian.org service?
Now we have switched to 'ftp.halifax.rwth-aachen.de', which I have found 
the nearest for us, since we have now direct GEANT connection to 
Frankfrut as seen on the trace below.


# traceroute ftp.halifax.rwth-aachen.de
traceroute to ftp.halifax.rwth-aachen.de (137.226.34.46), 30 hops max, 
60 byte packets

 1  central.ce-mt.asnet.am (93.187.162.1)  0.535 ms  0.398 ms  0.449 ms
 2  asnet.geant-mt.asnet.am (37.26.173.14)  0.553 ms  0.646 ms 0.590 ms
 3  nasra-gw.mx1.fra.de.geant.net (62.40.125.29)  59.161 ms  59.259 ms  
58.975 ms

 4  cr-fra1.x-win.dfn.de (62.40.124.218)  59.198 ms  59.292 ms 59.081 ms
 5  kr-aah15-0.x-win.dfn.de (188.1.242.110)  67.146 ms  67.362 ms 67.192 ms
 6  fw-xwin-1-vl106.noc.rwth-aachen.de (134.130.3.229)  66.535 ms 
66.253 ms  66.302 ms
 7  n7k-ww10-1-vl158.noc.rwth-aachen.de (134.130.3.243)  67.347 ms 
67.202 ms  67.593 ms
 8  n7k-sw23-2-et1-1.noc.rwth-aachen.de (137.226.38.58)  66.765 ms 
66.634 ms n7k-ww10-2-et1-1.noc.rwth-aachen.de (137.226.139.42) 66.331 ms
 9  ftp.halifax.rwth-aachen.de (137.226.34.46)  66.045 ms  66.271 ms  
66.205 ms



Are you updating four times a day or did you set up ssh triggers with
your upstream mirror?

We update four times a day for now.
Please suggest if it is worth to set up an ssh triggers and
if the 'ftp.halifax.rwth-aachen.de' variant is good choice for us at 
your point of view?

Maybe you can suggest better variants?


Please, take into consideration that we would like to become Primary Country
Mirror for Armenia and also have a CNAME of ftp.am.debian.org to
'mirrors.asnet.am'.

We can consider doing this.  Please ping us in two or three weeks once
we have seen how good the mirror is about keeping up.



Will contact you soon...

--
Regards,
Arthur Petrosyan

| Dr. Arthur Petrosyan
| 
| Senior Scientific Researcher, Head of Network and Cloud Services Direction,
| Deputy Head of Computational and Cognitive Networks Department at the
| Institute for Informatics and Automation Problems /IIAP/
| National Academy of Sciences of Armenia /NAS RA/,
| Academic Scientific Research Computer Network of Armenia /ASNET-AM/
| HTTP://www.asnet.am/   E-mail: art...@sci.am
| Phone:  +37410 526742  Fax:+37410 569281
| 

Bug#874597: debian-installer: switch to debhelper 10

[Cyril Brulebois]

Hi Christian!

Christian PERRIER  (2017-09-08):
> I'd be happy to do that when rebuilding for translation (I have a
> bunch of pending builds to do, because of recent updates for two
> languages).

I really meant that for src:debian-installer. All components below the
packages/ directory already use debhelper 9 AFAICT, which is good enough.

> I can probably start doing so as soon as my next race is over and I'm
> back to work (it is suppsoed to start in.6h30...and end on next
> Sunday).

Good luck with that. ;)


KiBi.


signature.asc
Description: PGP signature

Bug#874633: Debian mirror debian.nautile.nc: broken-ssh-push

[Bastian Blank]

Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem

Hi

Since a few days our mirror pushs to debian.nautile.nc fail.  SSH
connections time out:

|Sep 08 09:26:53 klecker runmirrors[9352]: Sending normal push
|ssh: connect to host debian.nautile.nc port : Connection timed out

As you are syncing directly from a syncproxy and are candidate for
ftp.nc.debian.org, we expect working pushs.  Please make sure such pushs
work.

Regards,
Bastian Blank

-- 
Witch!  Witch!  They'll burn ya!
-- Hag, "Tomorrow is Yesterday", stardate unknown

Bug#818366: Same error with Wayland

[Ronald Miranda]

Hi,

I have the same problem (cannot open display: :0) when using Gnome with
Wayland, to avoid this I'm running Gnome on X. However I'm not sure if
synaptic team is working on this.

Best regards,

Rony

Bug#874632: texinfo: inconsistent papersize for generated dvi and ps

[Vincent Lefevre]

Control: retitle -1 texinfo: inconsistent papersize for generated PostScript 
file (.ps)

On 2017-09-08 11:57:33 +0200, Vincent Lefevre wrote:
> But on one of my machines (from which this bug is reported), the
> generated dvi and ps have a letter papersize, so that the contents
> may be partly truncated. Note that another Debian/unstable machine
> (which has the same config, AFAIK) does not have this issue.

Actually the dvi issue is a viewer issue: If I transfer the .dvi file
to the other machine, the papersize changes (both ways).

But the papersize for the PostScript file really depends on where it
has been generated.

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

Bug#874626: nmu: gnuradio_3.7.11-1 gr-osmosdr_0.1.4-12

[Andreas Bombe]

On Fri, Sep 08, 2017 at 11:41:51AM +0200, Raphael Hertzog wrote:
> Hi,
> 
> On Fri, 08 Sep 2017, Raphaël Hertzog wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: binnmu
> > 
> > nmu gnuradio_3.7.11-1 . ANY . unstable . -m "Rebuild for codecs2 transition"
> 
> Here it seems to be last and only update needed of the codecs2 
> (uncoordinated) transition.
> 
> > nmu gr-osmosdr_0.1.4-12 . ANY . unstable . -m "Rebuild for soapysdr 
> > transition"
> 
> But this one seems to be part of two unreported transitions that affect more 
> packages:
> https://release.debian.org/transitions/html/auto-uhd.html
> (and soapysdr that has no auto-tracker page but which seems to be complete 
> after the gr-osmosdr
> bin-nmu)

soapysdr is completed, it's just that there are cross dependencies
between soapysdr and soapysdr modules so it triggered almost a dozen
auto transitions. Last thing missing was gr-osmosdr, which wasn't in
testing. Transition dependencies would have been uhd → soapyuhd →
soapysdr.

> Maitland, Andreas, it would be nice if you could handle library transitions
> in coordination with the release team:
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions

I thought I could handle it by myself since there was only one
dependency (gr-osmosdr) where I wasn't uploader. After reviewing the
process and seeing how my first soapysdr transition panned out, I'll
follow the official process in the future.

Bug#874635: debian-kernel-handbook: Some outdated instructions in "Common Tasks"

[Nikolaus Rath]

Package: debian-kernel-handbook
Severity: normal

> Hello,
> 
> I would like to rebuild a Debian kernel with an extra patch. I have
> followed the instructions at
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official:
> 
> $ apt-get source -t stretch linux
> $ cd linux-4.9.30
> $ perl -ipe 's/^debug-info: true/debug-info: false/g;' 
> debian/config/amd64/defines 

This won't do anything because debug-info is now enabled in the top
level configuration (debian/config/defines).  Although it is possible
to override it in the per-architecture configuration file, it is
simpler to edit the value in top level file.

> $ fakeroot make -f debian/rules.gen binary-arch_amd64_none_real
> make: Nothing to be done for 'binary-arch_amd64_none_real'.
> 
> 
> What do I have to do to get the -common header .deb?

It's now an arch-independent package, so this should do it:

make -f debian/rules.gen binary-indep_none

Please can you open a bug report against debian-kernel-handbook, so I
remember to update it?

Bug#807754: suspicious-source: prejudiced against Emacs Lisp

[David Bremner]

James McCoy  writes:

> On Sat, Dec 12, 2015 at 08:57:56AM -0400, David Bremner wrote:
>> Common is obviously subjective, but since there are probably a few
>> million lines of emacs lisp source in Debian, it probably qualifies as
>> common-enough.
>> 
>> Anyway, it certainly is the preferred form of modification.
>
> Do you have a specific example?  suspicious-source has whitelisted
> text/x-lisp mime-type since day 1 (in devscripts).

Hmm. In the intervening years I've lost the original context, but
looking around at what I happen to have checked out, I see the following
false positives.

circe
circe.el
lui-irc-colors.el

magit/lisp/magit-log.el

emacs25/lisp

woman.el
help-fns.el
progmodes/cc-mode.el
emacs-lisp/elint.el
emacs-lisp/nadvice.el
emacs-lisp/tcover-ses.el
leim/quail/rfc1345.el
mail/emacsbug.el
gnus/nnmail.el
org/ob-ruby.el
org/org-ctags.el
erc/erc-services.el

Bug#874636: RM? FTBFS with Java 9, no rdeps, dead upstream (2004)

[Chris West]

Source: libgroboutils-java
Version: 5
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk,
although it would probably be trivial to fix.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

I cannot see any rdeps in sid for this library package.

Upstream seems to have been dead since 2004, there have been no
releases. There is a related project, which saw commits in 2014, but no
releases.


Build log:

[javac] XXX: totally hacking the target version
[javac] 
/build/libgroboutils-java-5/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/SubTestTestCase.java:156:
 error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] Enumeration enum = list.elements();
[javac] ^
[javac] 
/build/libgroboutils-java-5/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/SubTestTestCase.java:157:
 error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] while (enum.hasMoreElements())
[javac]^
[javac] 
/build/libgroboutils-java-5/testing-junit/sources/dev/net/sourceforge/groboutils/junit/v1/SubTestTestCase.java:159:
 error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] Test test = (Test)enum.nextElement();
[javac]   ^
[javac] 3 errors
[javac] 3 warnings



Cheers,
Chris.

Bug#874467: Debian mirror mirrors.ircam.fr: tracefile info, syncscript

[Benjamin Boudoir]

Hi,

Le mercredi 6 septembre 2017 11:15:00, vous avez écrit :
> Package: mirrors
> User: mirr...@packages.debian.org
> Usertags: mirror-problem may-auto-close
> 
> Hi,
> 
> I was checking some things in the Debian mirror universe and noticed
> a problem with your mirror:
> 
> o Status:
> https://mirror-master.debian.org/status/mirror-info/mirrors.ircam.fr.html
> 
> o The trace file at
>   http://mirrors.ircam.fr/pub/debian/project/trace/mirrors.ircam.fr
>   does not contain much information.
> 
>   Please use our ftpsync script to mirror Debian.
> 
>   It should produce better trace files, and do the mirroring in a way that
>   ensures the mirror is in a consistent state even during updates,
>   unlike the way the mirror is currently being updated.
> 
>   http://ftp.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz

For practical reasons, we cannot use Debian's ftpsync for now, but we updated 
our script configuration to produces compatibles traces, status page seems 
happier now.

Let us know if we can do anything else.

Regards,

-- 
Benjamin Boudoir
Administrateur Système

Bug#533450: Dear friend

[CHARLES]

-- 
I have business to discuss with you it about money deposited by former Late
president Muammar Qaddafi of Libya. I want you to help me receive it in
your country.
Sincerely
Charles

Bug#874637: RM? FTBFS with Java 9, very outdated, upstream status unclear

[Chris West]

Source: libisnativec-java
Version: 5.3.20100629+fix-1
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls
This package references some sun.misc classes which seem to have been
removed. It's also probably horrifying.

It's unclear if its upstream is active, it looks to have been maintained
by a company that's been bought out?

The only rdeps are libiscwt-java and libisfreetype-java, neither of
which have any rdeps themselves. They are all in exactly the same state
as this package. (The "is" prefix is not a coincedence: it's the name of
the company.)

Can we RM all three?


Build log:

find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jna.jar:/usr/share/java/isrt.jar:debian/_jh_build.isnativec -d 
debian/_jh_build.isnativec -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 1.7
src/de/intarsys/nativec/api/NativeInterface.java:34: error: cannot find symbol
import sun.misc.Service;
   ^
  symbol:   class Service
  location: package sun.misc


Cheers,
Chris.

Bug#395573: Building VisIt for Debian

[Alastair McKinstry]

Hi Steffen,

Sorry for taking so long to respond.

Packaging VisIt was delayed waiting for 'the correct VTK' to be packaged 
for Debian. I also haven't had much time to pay attention to this; I 
still wish to see VisIt packaged as it is a dependency of CDAT which I'd 
like to see in Debian.


Currently VTK6 is present which should work, with VTK8 being packaged 
for buster. What branch are you using ? my latest branch (debian/master) 
should be based off 2.12.3, and refers to python- instead of python3 
until python3-vtk? is provided.  It doesn't build yet, but I can work 
with you to get it working.


Best regards
Alastair




On 06/09/2017 11:17, Steffen Grunewald wrote:

Hello Alastair,

this morning I received the request to make VisIt available on a bunch of
Debian (Jessie at the moment, but perhaps Stretch too within a few months)
machines, by one of our brightest scientists. I simply cannot deny this.

Incidentally, I had started to try to package VisIt (2.12.3) myself, starting
with the "official" build script and a pbuilder with "--usenetwork yes".
I had added a number of build dependencies, only to fail at the VTK build
stage. It turned out that the Xt was missing, but I didn't pursue this any
further because I had spotted your IFP/RFP (bug #395573)...

So I went ahead and cloned your debian-build git repository - only to find
that the last version possibly supported would have been 2.9... I used that
debian/ tree to build my own, still with 2.12.3 in mind, and gradually added
build-depends. I'm stuck now because something in the build process thinks
it would be nice to have python3 support, but there is no python3-vtk6, and
that's it. Is it, really? (This seems to be connected to the change that
included python3 into python-all-dev. Why there's no python3-vtk6, I don't
know, there seems to be no easy way to create one.)

I found that Ole Streicher had already asked for the status of the project
but didn't get a (public) answer. Perhaps I'm luckier. May I learn what
stopped you from working on this build, and what your suggestions are?

For now, I'll continue to iterate over the missing X libraries, perhaps
I'll be successful in the end. (I won't be happy because this "usenetwork"
setting is a horrible kludge, but on the other hand, the whole VisIt build
process seems to be. I need to accept that, sooner or later.)

Thanks,
  Steffen

Bug#874638: FTBFS with Java 9: javadoc classpath

[Chris West]

Source: libjgrapht0.8-java
Version: 0.8.3
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

This package appears to be confused about the classpath during the
javadoc build.

Build log:

jar:
  [jar] Building jar: 
/build/libjgrapht0.8-java-0.8.3/debian/libjgrapht0.8-java/usr/share/java/jgrapht-0.8.3.jar

javadoc:
[mkdir] Created dir: 
/build/libjgrapht0.8-java-0.8.3/debian/libjgrapht0.8-java-doc/usr/share/doc/libjgrapht0.8-java/apidoc
  [javadoc] Generating Javadoc
  [javadoc] Javadoc execution
...
  [javadoc] Loading source files for package org.jgrapht.util...
  [javadoc] Constructing Javadoc information...
  [javadoc] 
/build/libjgrapht0.8-java-0.8.3/src/org/jgrapht/ext/JGraphModelAdapter.java:111:
 error: cannot find symbol
  [javadoc] extends DefaultGraphModel
  [javadoc] ^


Cheers,
Chris.

Bug#874639: ITP: python-b2 -- Python Command Line Tool for Backblaze B2

[Ondřej Kobližek]

Package: wnpp
Severity: wishlist
Owner: Ondřej Kobližek 

* Package name: python-b2
  Version : 0.7.2
  Upstream Author : Backblaze, Inc. 
* URL : https://github.com/Backblaze/B2_Command_Line_Tool
* License : (MIT)
  Programming Lang: (Python)
  Description : Python Command Line Tool for Backblaze B2

This package is CLI for B2 Cloud Storage, which we using at work.
There are no other packages for B2 at Debian.
I plan maintain it in DPMT.

Bug#874640: FTBFS with Java 9: sun.swing..

[Chris West]

Source: libjide-oss-java
Version: 3.6.18+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9
Tags: fixed-upstream

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

This seems to have been fixed upstream, but not released:
https://github.com/jidesoft/jide-oss/commit/afac15d1eb62308d535abeb142cdb1e2df1eab39#diff-b943f8a80f4d59548be8448fddeebf78

Build log:

compile:
[mkdir] Created dir: /build/libjide-oss-java-3.6.18+dfsg/classes
[javac] /build/libjide-oss-java-3.6.18+dfsg/build.xml:54: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Use of a source 1.5 is no longer supported, switching to 1.6
[javac] Use of a target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 496 source files to 
/build/libjide-oss-java-3.6.18+dfsg/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/libjide-oss-java-3.6.18+dfsg/src/com/jidesoft/plaf/basic/BasicPainter.java:11:
 error: cannot find symbol
[javac] import sun.swing.plaf.synth.SynthIcon;
[javac]^
[javac]   symbol:   class SynthIcon
[javac]   location: package sun.swing.plaf.synth



Cheers,
Chris.

Bug#874642: Installation successfully at BananaPi

[Bernhard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: installation-reports

Boot method: SD-Card
Image version: 
http://ftp.de.debian.org/debian/dists/stretch/main/installer-armhf/20170615+deb9u1/images/netboot/SD-card-images/
Date: 2017-08-31

Machine: Banana Pi
Processor: Allwinner sun7i (A20) Family / ARMv7 Processor rev 4 (v7l)
Memory: 1GB
Partitions: 

> Filesystem Type  1K-blocks  Used  Available Use% Mounted on
> udev   devtmpfs 494272 0 494272   0% /dev
> tmpfs  tmpfs102304  3124  99180   4% /run
> /dev/mmcblk0p2 ext4   14015808789648   12494464   6% /
> tmpfs  tmpfs511516 0 511516   0% /dev/shm
> tmpfs  tmpfs  5120 0   5120   0% /run/lock
> tmpfs  tmpfs511516 0 511516   0% /sys/fs/cgroup
> /dev/mmcblk0p1 ext2 240972 25146 203385  12% /boot

Output of lspci -knn: -

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

One very minor issue: at the end of the installation, there is no reboot done.
The reboot has to be done manually.
-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYvvxz3oQWp9oxCe+7FGr7aO6LbYFAlmygE4THGJld29lcm4x
QGdtYWlsLmNvbQAKCRDsUavto7ottrTiD/9nE5dKNVMnXcvLXKASym5DAeVd9DZT
ojw4IyWOJ3tFD9nggqRuxGoy1cdwt/CQv8V1rkV7Ygk6M+cQJmMzXCypHqZxBlna
WMeArORyPqtFcdkxylq2umaL7fY2tlNdPeKcBIVFgpGcLww7Ptrqlzjnr8lOk/bj
iuLEPVOzxFdFWCtxcKjydQqnhTXPbKQazAl6q4SyyL91VUA3wqjRFzcVVknp8U/7
3x7xM2qTNNmPXwblzUBQCHMKegQLwTXKFwiVX3U8lqvwogMsbBcSi4DCJTEW9YVW
06IXgnSNB69ex+Mo1m9St7wBrZlrvqUUtK9+UIXWm8malajg3IPVttPCShxbM6P9
IkgVXJ78qbNX51wlu13DtOJk7C5v4LjnLaxo9nfxjQSDrDiGOhoR/4O7m/R0zCnJ
vyOeGCuA5jxiVclnfhhi9r1o9JBOHB5C1M6R4+uIPNpSagoR8eQYre9AglnTyTlA
W9UXUR2JBGBvNqIJVpJcVe5NKZiBrQJcygn2GWP90DvB9bK3rZI6Ij+iv4Rwnhv+
C8C/oGDCoGTHugLw3a+6kA/Ixb3H1fgRmvpxy6imm8cx9KMaoBR1HQLj3Q+xk+9w
pD9NUeIEBUpL7rbb42oKTq7VkcJw3fWvg+CHj5CRfS/NuWiT5knokXWp4cM6hIe9
EGR7agY9j5kVZw==
=yulX
-END PGP SIGNATURE-

Bug#874641: linux-image-4.9.0-3-amd64: system freezes when disconnecting bluetooth mouse sometimes

[Matthew Harm Bekkema]

Package: src:linux
Version: 4.9.30-2+deb9u3
Severity: normal

Sometimes, disconnecting my bluetooth mouse causes my entire system to freeze. I
cannot even ssh in and need to hard reboot the computer. It doesn't happen all
the time. 99% of the time, when I disconnect my mouse, the computer does not
crash.

So far, this has happened around 6 times, but this is the first time that it
left any messages in the syslog.


-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06)

** Command line:
BOOT_IMAGE=/vmlinuz ro root=/dev/mapper/sda_crypt

** Not tainted

** Kernel log:
Sep  8 20:32:45 thorium kernel: [165282.673872] [ cut here 
]
Sep  8 20:32:45 thorium kernel: [165282.673879] WARNING: CPU: 0 PID: 704 at 
/build/linux-me40Ry/linux-4.9.30/lib/list_debug.c:29 __list_add+0x5c/0xb0
Sep  8 20:32:45 thorium kernel: [165282.673881] list_add corruption. next->prev 
should be prev (8b70b2e634c8), but was dead0200. 
(next=9f28c3f77e58).
Sep  8 20:32:45 thorium kernel: [165282.673882] Modules linked in: uinput hidp 
rfcomm fuse bnep ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter binfmt_misc intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
efi_pstore arc4 intel_cstate iTCO_wdt iTCO_vendor_support eeepc_wmi asus_wmi 
sparse_keymap snd_hda_codec_hdmi snd_hda_codec_realtek intel_uncore ath9k i915 
snd_hda_codec_generic ath9k_common intel_rapl_perf ath9k_hw ath mac80211 
efivars snd_hda_intel serio_raw snd_hda_codec btusb snd_hda_core btrtl btbcm 
snd_hwdep btintel snd_pcm drm_kms_helper ie31200_edac cfg80211 drm bluetooth 
evdev joydev snd_timer snd rfkill mei_me sg i2c_algo_bit soundcore mei lpc_ich 
shpchp mfd_core edac_core battery wmi video button sunrpc efivarfs ip_tables 
x_tables
Sep  8 20:32:45 thorium kernel: [165282.673919]  autofs4 ext4 crc16 jbd2 
crc32c_generic fscrypto ecb mbcache algif_skcipher af_alg dm_crypt dm_mod 
hid_generic usbhid hid sr_mod cdrom sd_mod uas usb_storage crct10dif_pclmul 
crc32_pclmul crc32c_intel ahci libahci xhci_pci xhci_hcd ghash_clmulni_intel 
aesni_intel ehci_pci aes_x86_64 lrw gf128mul glue_helper ehci_hcd ablk_helper 
cryptd psmouse i2c_i801 i2c_smbus libata scsi_mod r8169 usbcore mii usb_common 
fan thermal
Sep  8 20:32:45 thorium kernel: [165282.673941] CPU: 0 PID: 704 Comm: 
bluetoothd Not tainted 4.9.0-3-amd64 #1 Debian 4.9.30-2+deb9u3
Sep  8 20:32:45 thorium kernel: [165282.673943] Hardware name: System 
manufacturer System Product Name/P8Z77-V LX, BIOS 0610 05/08/2012
Sep  8 20:32:45 thorium kernel: [165282.673945]   
9cf28574 9f28c20eba20 
Sep  8 20:32:45 thorium kernel: [165282.673947]  9cc76ebe 
8b70c88aa4b8 9f28c20eba78 9f28c3f77e58
Sep  8 20:32:45 thorium kernel: [165282.673949]  9f28c20ebc6c 
 9f28c20ebc54 9cc76f3f
Sep  8 20:32:45 thorium kernel: [165282.673951] Call Trace:
Sep  8 20:32:45 thorium kernel: [165282.673955]  [] ? 
dump_stack+0x5c/0x78
Sep  8 20:32:45 thorium kernel: [165282.673959]  [] ? 
__warn+0xbe/0xe0
Sep  8 20:32:45 thorium kernel: [165282.673961]  [] ? 
warn_slowpath_fmt+0x5f/0x80
Sep  8 20:32:45 thorium kernel: [165282.673962]  [] ? 
__list_add+0x5c/0xb0
Sep  8 20:32:45 thorium kernel: [165282.673965]  [] ? 
add_wait_queue+0x2b/0x40
Sep  8 20:32:45 thorium kernel: [165282.673988]  [] ? 
bt_sock_poll+0x3a/0x1c0 [bluetooth]
Sep  8 20:32:45 thorium kernel: [165282.673991]  [] ? 
sock_poll+0x79/0x90
Sep  8 20:32:45 thorium kernel: [165282.673993]  [] ? 
do_sys_poll+0x26e/0x550
Sep  8 20:32:45 thorium kernel: [165282.673995]  [] ? 
poll_initwait+0x40/0x40
Sep  8 20:32:45 thorium kernel: [165282.673997]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.673998]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674000]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674001]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674002]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674004]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674005]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674007]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674008]  [] ? 
poll_select_copy_remaining+0x150/0x150
Sep  8 20:32:45 thorium kernel: [165282.674010]  [] ? 
SyS_poll+0xdf/0x120
Sep  8 20:32:45 thorium kernel: [165282.674013]  [] ? 
system_call_fast_compare_end+0xc/0x9b
Sep  8 20:32:45 thorium kernel: [165282.674014] ---[ end trace 14108208e55137ca 
]---
Sep  8 20:32:45 thorium acpid: input device has been 

Bug#874586: actually, it's Wayland that's the problem

[Dmitry Shachnev]

Control: reassign -1 libgtk-3-0 3.22.19-1

Hi Cristopher,

On Thu, Sep 07, 2017 at 04:05:34PM -0400, Christopher Cramer wrote:
> After some further investigation, I have discovered that the problem
> is apparently caused by GDM now defaulting to Wayland, which has no
> accessibility support. My complaint about the lack of an error message
> still stands.
>
> This bug is, perhaps, a duplicate of 648292.

gnome-applets does not support Wayland at all. Moreover we do not deal
with sticky keys, only with sticky notes :)

Also this is unlikely a duplicate of #648292: that bug was filed in 2011
when there was no GNOME Wayland session yet.

According to some upstream links [1][2] this should be moved to gtk+.

[1]: https://fedoraproject.org/wiki/Wayland_features#accessibility:_keyboard
[2]: 
https://mail.gnome.org/archives/desktop-devel-list/2014-February/msg00102.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#874643: Mis-detects Java 9 at "runtime"

[Chris West]

Package: libgluegen2-build-java
Version: 2.3.2-5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package is used while building other packages. It contains some
build helper scripts. These scripts fail to detect Java 9 correctly, so
error out, breaking the build of other packages.

...



...

The value has been changed to 9, not 1.9.
Fix might look like:
https://ssl.icu-project.org/trac/attachment/ticket/13330/icu4j.diff

..or see if someone has put a better solution on the wiki:
https://wiki.debian.org/Java/Java9Pitfalls



Build log from an example broken package, libjogl2-java:

jogamp.env.validation:
 [echo] ant.versionApache Ant(TM) version 1.9.9 compiled on 
June 29 2017
 [echo] ant.java.version   9
 [echo] java.version   9-Debian
 [echo] java.home  /usr/lib/jvm/java-9-openjdk-amd64
 [echo] jvmJava.exe
/usr/lib/jvm/java-9-openjdk-amd64/bin/java
Property "env.JAVA7_EXE" has not been set
Property "env.JAVA7_EXE" has not been set
Property "jvmJava7.exe" has not been set
 [echo] jvmJava7.exe   ${jvmJava7.exe}

BUILD FAILED
/usr/share/gluegen2/make/jogamp-env.xml:48: Unsupported Java version: 9. Make 
sure that the version of the Java compiler is 1.6 (6.0) or greater.
at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:164)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)


Cheers,
Chris.

Bug#874644: FTBFS with Java 9: com.sun.net.ssl

[Chris West]

Source: libjtds-java
Version: 1.2.5+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9
Tags: fixed-upstream

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

This seems to have been addressed upstream a *long* time ago, I'm not
sure why it's not in the release that's in Debian. There is a newer,
semver-compatible release that presumably has it.

https://sourceforge.net/p/jtds/code/987/

Build log:


[javac] /build/libjtds-java-1.2.5+dfsg/debian/build.xml:46: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 67 source files to /build/libjtds-java-1.2.5+dfsg/build
[javac] 
/build/libjtds-java-1.2.5+dfsg/src/main/net/sourceforge/jtds/ssl/SocketFactoriesSUN.java:32:
 error: package com.sun.net.ssl is not visible
[javac] import com.sun.net.ssl.SSLContext;
[javac]   ^


Cheers,
Chris.

Bug#864190: openssh-server: Missing privilege separation directory: /run/sshd

[doak]

Please consider to ensure that the SSH privilege-seperation directory is in 
place as long as SSH is installed (in contract to "as long as SSH is running').

Rationale:

>> RuntimeDirectory=sshd
>> Perhaps that would be a reliable way to fix the problem...
> That does indeed seem like a plausible approach.  Committed to git
> master, thanks.

Although this seems to be very robust way to ensure the privilege-separation 
directory exists and is empty, it disallows to run 'sshd' as a non-root user 
because of missing '/run/sshd' if 'sshd' has not been started by 'systemd'.
My use case is to establish a tunnel between two clients without the need of 
root privileges. The (potentially) missing '/run/sshd' prevents this.

I am not a security expert and do not know if this use case implies security 
issues (e.g. breaks privilege separation), but security is at least not 
decreased if '/run/sshd' exists even if 'sshd' is not running: A user is able 
to create a patched copy of 'sshd' replacing '/run/sshd' with '/tmp/sshd' and 
create a symlink from '/tmp/sshd' to any directory owned by root which is not 
accessible to group or world-side (like e.g. '/run/log').
In fact, users will compromise system security if they are tempted to 
workaround missing '/run/sshd' this.


With best regards,
doak


On Sun, 23 Jul 2017 13:15:45 +0100 Colin Watson  wrote:
> Control: tag -1 pending
> 
> On Mon, Jul 17, 2017 at 09:26:26AM +1000, Dmitry Smirnov wrote:
> > So I had a chance to try another fix to the problem: I was able to start
> > "ssh.service" again after adding the following line:
> > 
> > RuntimeDirectory=sshd
> > 
> > Perhaps that would be a reliable way to fix the problem...
> 
> That does indeed seem like a plausible approach.  Committed to git
> master, thanks.
> 
> -- 
> Colin Watson   [cjwat...@debian.org]
> 
> 

Bug#874592: [patch] Fix upstream name and homepage in src:package

[Matteo F. Vescovi]

Control: severity -1 minor

Hi!

On 2017-09-07 at 13:39 (-0400), Nicholas D Steeves wrote:
> Hi Matteo,
>
> Please find attached patches to fix the upstream name and homepage in
> src:ghub-plus-el.

Ah, right. Gonna fix this soonish.

Thanks for the patches.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#867889: Pending fixes for bugs in the jarjar package

[pkg-java-maintainers]

tag 867889 + pending
thanks

Some bugs in the jarjar package are closed in revision
16b243cd48f9f76e97c2dc383649425346642c65 in branch 'master' by
Emmanuel Bourg

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

Commit message:

Revert to libasm4-java to avoid a compatibility issue with ASM 6 (Closes: 
#867889)

Bug#874645: FTBFS with Java 9: javadoc classpath

[Chris West]

Source: libnative-platform-java
Version: 0.11
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

This package appears to be passing the wrong classpath to the javadoc
tool, which is now illegal in Java 9. You have to fix the -source option
first, to see the second error.

Build log:

warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.

[.. then ..]

src/main/java/net/rubygrapefruit/platform/Native.java:19: error: package 
net.rubygrapefruit.platform.internal does not exist
import net.rubygrapefruit.platform.internal.NativeLibraryLoader;
^

Cheers,
Chris.

Bug#874614: [Pkg-utopia-maintainers] Bug#874614: Please demote some packages from dependency to recommendation

[Bracksiek & Hemmelskamp]

Ok, in that case the modules in udisks2 has to be optional - and not
dependencies. What do you think?

Bug#874480: [Ticket#10518680] Bug#874480: Bug#874480: Debian mirror ftp.tu-chemnitz.de: no tracefile, syncscript

[URZ Datenkommunikation]

Peter Palfrader  wrote:

> > I installed ftpsync and we're using this now to sync our mirror.
> > Please take a look if this is ok.
> 
> I think this looks good, thanks a lot!
> 
> A few minor suggestions:
>  - It seems you run the mirror 6 times a day, or every 4 hours.
>The archive updates 4 times a day, or about every 6 hours.
>Maybe switch to that cycle.
>  (A more involved set up would use ssh triggered mirroring
>   from your upstream, or something that monitors the upstream
>   tracefile -- a future version of ftpsync will include
>   helpers for the latter but right now that's just in git.)

Ok, I took a look at the mirroring time of debian.inf.tu-dresden.de and aligned 
our sync times to them. That should reduce the gap for now. 
Currently our server running the syncs isn't reachable per SSH from the world.
I'll see what I can do.

>  - Your mirror is available at
>http://ftp.tu-chemnitz.de/pub/linux/debian/debian/
>Any chance you could make a (hidden) alias for that at /debian,
>such that e.g.
>http://ftp.tu-chemnitz.de/debian/project/trace/
>works?

It works now with the basic https listing. Probalbly you catch the files 
directly.

>  - You have configured to sync from 141.76.2.4.  I'd probably refer
>to that as debian.inf.tu-dresden.de.

Done.

> Also,
>   I notice you still have a debian-backports repo mirrored at
>   http://ftp.tu-chemnitz.de/pub/linux/debian/debian-backports/
> 
>   It can probably be removed.

Did this with pleasure :-)

Cheers,
Frank

-- 
 Technische Universität Chemnitz
 Universitätsrechenzentrum
 Web: http://www.tu-chemnitz.de/urz

smime.p7s
Description: S/MIME cryptographic signature

Bug#874646: RM? FTBFS with Java 9, no rdeps, idle upstream

[Chris West]

Source: libnetx-java
Version: 5
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The problem would probably be easy to fix, however the package does not
appear to have had any love at all in 7+ years.


Last upstream commit was around 14 years ago. Last comment on a ticket
was around 7 years ago; the ticket wasn't resolved. Last release was 14
years ago.

I cannot find any rdeps, and the package appears to be a library. There
is some indication that people might want to use it interactively, i.e.
not as a library. I cannot find any real examples of anything doing
this?

Can we RM it?


Build log:

[javac] warning: [options] target value 1.4 is obsolete and will be removed 
in a future release
[javac] XXX: totally hacking the target version
[javac] /build/libnetx-java-0.5/src/nanoxml/XMLElement.java:294: error: as 
of release 5, 'enum' is a keyword, and may not be used as an identifier
[javac] Enumeration enum = this.entities.keys();
[javac] ^




Cheers,
Chris.

Bug#874647: liboptimisation-java: RM? FTBFS with Java 9, no rdeps, idle upstream

[Chris West]

Source: liboptimisation-java
Version: 0.1
Severity: wishlist
User: debian-j...@lists.debian.org
Usertags: default-java9
X-Debbugs-Cc: debian-...@lists.debian.org

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

I don't really understand the problem, it's failing to find a class;
this kind of thing shouldn't have changed. I didn't investigate much as
I am hoping to RM it.

Upstream's last release was in 2010. There's no source control or
anything. There's a phone number.

The package seems to have been superseded by JPOP:
https://sourceforge.net/projects/jpop-optimizer/

The package has no current rdeps. It appears to have been added to
support an unspecified Debian Med package, which I am unable to locate.
The maintainer has ended up as Debian Java out of.. politeness?


Can we RM it?


Build log:

find optimization -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.optimization -d 
debian/_jh_build.optimization -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 1.7
optimization/Blas_f77.java:129: error: duplicate class: linear_algebra.Blas_f77
public class Blas_f77 extends Object {
   ^
optimization/Fzero.java:302: error: cannot access Blas_f77
  if (Blas_f77.sign_f77(1.0,fz) != Blas_f77.sign_f77(1.0,fb)) {
  ^
  bad source file: ./optimization/Blas_f77.java
file does not contain class optimization.Blas_f77


Cheers,
Chris.

Bug#873706: [Pkg-utopia-maintainers] Bug#874614: Bug#874614: Please demote some packages from dependency to recommendation

[Michael Biebl]

Am 08.09.2017 um 14:26 schrieb Bracksiek & Hemmelskamp:
> Ok, in that case the modules in udisks2 has to be optional - and not
> dependencies. What do you think?

There is already
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873706

Further discussion should follow up there.

Manually removing the mdraid module leads to
> Sep 08 14:38:13 pluto udisksd[23063]: udisks daemon version 2.7.3 starting
> Sep 08 14:38:13 pluto udisksd[23063]: failed to load module mdraid: 
> libbd_mdraid.so.2: cannot open shared object file: No such file or directory
> Sep 08 14:38:13 pluto udisksd[23063]: Failed to load a libblockdev plugin
> Sep 08 14:38:13 pluto udisksd[23063]: Acquired the name 
> org.freedesktop.UDisks2 on the system message bus
> Sep 08 14:38:13 pluto systemd[1]: Started Disk Manager.

The udisks2 daemon is still running though. Same for the
libbd_crypto.so.2 plugin:

> Sep 08 14:40:46 pluto systemd[1]: Starting Disk Manager...
> Sep 08 14:40:46 pluto udisksd[23330]: udisks daemon version 2.7.3 starting
> Sep 08 14:40:46 pluto udisksd[23330]: failed to load module crypto: 
> libbd_crypto.so.2: cannot open shared object file: No such file or directory
> Sep 08 14:40:46 pluto udisksd[23330]: failed to load module mdraid: 
> libbd_mdraid.so.2: cannot open shared object file: No such file or directory
> Sep 08 14:40:46 pluto udisksd[23330]: Failed to load a libblockdev plugin
> Sep 08 14:40:46 pluto udisksd[23330]: Failed to load a libblockdev plugin
> Sep 08 14:40:46 pluto systemd[1]: Started Disk Manager.
> Sep 08 14:40:46 pluto udisksd[23330]: Acquired the name 
> org.freedesktop.UDisks2 on the system message bus

Maybe that's already good enough to make those plugins optional and
demote them to Recommends. The failure messages are certainly ugly
though and I haven't checked how that failure is propagated to the UI,
say cockpit or gnome-disks and if they handle those properly.

As for LVM2 and btrfs support: Those are already optional modules in
udisks2 (i.e. Suggests).
But I'm actually not sure if LVM support works in the Debian udisks2
package.
I see that the following features need to be switched on explicitly:
  --enable-lvm2   enable LVM2 support
  --enable-lvmcache   enable LVMCache support
  --enable-iscsi  enable iSCSI support
  --enable-btrfs  enable BTRFS support
  --enable-zram   enable ZRAM support
  --enable-lsmenable LibStorageMgmt support
  --enable-bcache enable Bcache support

Andreas, have you tested if e.g. lvm2 or btrfs support actually works in
the Debian udisks2 package?

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



signature.asc
Description: OpenPGP digital signature

Bug#810898: apt: "apt-get update" (1.2) very slow with compressed indices and debtags

[Enrico Rossi]

Hi,

Enrico Zini made this python3 code to test the problem outside debtags:

#!/usr/bin/python3
import apt

def main():
cache = apt.Cache()
for pkg in cache:
cand = pkg.candidate
if not cand: continue
tags = cand.record.get("Tag", None)
if not tags: continue
print(pkg.name, tags)

if __name__ == "__main__":
main()

Running it without compressed index in apt:

# time python3 cattags >/dev/null 
real0m1.671s
user0m1.539s
sys 0m0.132s

with compressed index:

# time python3 cattags >/dev/null 
real1m44.238s
user1m33.536s
sys 0m10.698s

I'm going to re-assign the bug to python-apt, maybe they have more info
on the issue.

Bye
E.

-- 
GPG key: 4096R/5E0195FAF2133176 2010-10-19 Enrico Rossi 

Bug#794410: Same Issue

[Marcel Krausert]

I also experienced the same problem.

Hardware is a B&R PPC2100
Intel Atom E3815

Debian 8.8 amd64 freezing @ "dpkg something" during software installation
Debian 9.1 amd64 freezing @ "discover" during software installation

I changed two things before it worked (after trying and searching 2 
hours):
- Disabled AHCI in BIOS
- Used the "firmware" version of the iso

Hopefully this saves someone some trouble :-)

Bug#874647: liboptimisation-java: RM? FTBFS with Java 9, no rdeps, idle upstream

[Andreas Tille]

Hi Chris,

On Fri, Sep 08, 2017 at 01:49:34PM +0100, Chris West wrote:
> Can we RM it?

Yes, please.
 
Thanks for your QA work

 Andreas.

-- 
http://fam-tille.de

Bug#874648: libwww-perl: LWP makes case-sensitive SSL-checkings on Wildcard Certificates

[Cord Beermann]

Package: libwww-perl
Version: 6.15-2
Severity: important
Tags: upstream

Hello, 

I came over a problem with fetching things from a Webserver which is
protected with a Wildcard-Certificate.

Example:
$ GET -Sd https://WWW.WEBMILES.de/
GET https://WWW.WEBMILES.de/
301 Moved Permanently

$ GET -Sd https://WWW.WEBMILES.DE/
GET https://WWW.WEBMILES.DE/
500 Can't connect to WWW.WEBMILES.DE:443

If the Hostname is written out in all Caps, the Matching against a
Wildcard-Certificate isn't working. If one character is lowercase it
works.

As DNS-Names are case-insensitive this should be a bug.
curl reports this:
*  subject: OU=Domain Control Validated; CN=*.webmiles.de
*  subjectAltName: host "WWW.WEBMILES.DE" matched cert's "*.webmiles.de"

The problem only seems to pop-up when the Webserver has a
Wildcard-Certificate.

Cord


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

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE= (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libwww-perl depends on:
ii  ca-certificates 20170717
ii  libencode-locale-perl   1.05-1
ii  libfile-listing-perl6.04-1
ii  libhtml-parser-perl 3.72-3+b2
ii  libhtml-tagset-perl 3.20-3
ii  libhtml-tree-perl   5.03-2
ii  libhttp-cookies-perl6.01-1
ii  libhttp-date-perl   6.02-1
ii  libhttp-message-perl6.11-1
ii  libhttp-negotiate-perl  6.00-2
ii  liblwp-mediatypes-perl  6.02-1
ii  liblwp-protocol-https-perl  6.07-2
ii  libnet-http-perl6.16-1
ii  liburi-perl 1.72-1
ii  libwww-robotrules-perl  6.01-1
ii  netbase 5.4
ii  perl5.26.0-7

Versions of packages libwww-perl recommends:
ii  libhtml-form-perl6.03-1
pn  libhtml-format-perl  
ii  libhttp-daemon-perl  6.01-1
ii  libmailtools-perl2.18-1

Versions of packages libwww-perl suggests:
pn  libauthen-ntlm-perl  

-- no debconf information


-- 

Bug#874614: AW: [Pkg-utopia-maintainers] Bug#874614: Bug#874614: Please demote some packages from dependency to recommendation

[Bracksiek & Hemmelskamp]

Fine, in that case let's close this bug, it's annoying but udisks2 is the
better places.
Damn, i miss my own well configure mail client

Cheers Alf

Bug#874614: [Pkg-utopia-maintainers] Bug#874614: AW: Bug#874614: Bug#874614: Please demote some packages from dependency to recommendation

[Michael Biebl]

Am 08.09.2017 um 14:54 schrieb Bracksiek & Hemmelskamp:
> Fine, in that case let's close this bug,

#874614 is already closed


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



signature.asc
Description: OpenPGP digital signature

Bug#874649: FTBFS with Java 9: upstream won't support it for now

[Chris West]

Source: jna
Version: 4.4.0
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Upstream are not going to support building with Java 9, even in their
next release, but intend to support running on it:
https://github.com/java-native-access/jna/issues/856

> The upcoming JNA 4.5.0 should work with Java 9, but is only
> buildable on java 8 and before.

(The issue also discusses some less relevant crashes; which we can
ignore for the purpose of this bug report; sorry!)

JNA is pretty important, I believe Gradle depends on it, plus svnkit and
a couple of other important-looking libraries, so we probably can't RM
it, or leave it broken during a transition.

What's the plan? Change the build-dep to openjdk-8, so that default-jdk
can transition, then package newer versions as they are released?



Build log:

[javac] 
/build/libjna-java-4.4.0/contrib/platform/src/com/sun/jna/platform/WindowUtils.java:1392:
 error: cannot find symbol
[javac] Object peer = w.getPeer();
[javac]^
[javac]   symbol:   method getPeer()
[javac]   location: variable w of type Window

Cheers,
Chris.

Bug#874650: ITP: node-color-convert -- Plain color conversion functions

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-color-convert
  Version : 1.9.0
  Upstream Author : Heather Arthur 
* URL : https://github.com/qix-/color-convert#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Plain color conversion functions

 Color-convert is a color conversion library for JavaScript and node.  It
 converts all ways between rgb, hsl, hsv, hwb, cmyk, ansi, ansi16, hex
strings,
 and CSS keywords (will round to closest).
 .
 Node.js is an event-based server-side JavaScript engine.

This library is a dependency for updating node-ansi-styles



signature.asc
Description: OpenPGP digital signature

Bug#874383: torbrowser-launcher: AppArmor failures

[gregor herrmann]

On Fri, 08 Sep 2017 08:48:41 +0200, intrigeri wrote:

> > Sep 5 18:21:18 jadzia kernel: [848718.105570] audit: type=1400
> > audit(1504628478.309:7268): apparmor="DENIED" operation="mknod"
> > profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
> > name="/run/shm/org.chromium.Ob3qhH" pid=19088 comm=57656220436F6E74656E74
> > requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> > [...]
> > and loading any page just hangs.
> Ouch! On my system (sid, systemd) /run/shm is a symlink to /dev/shm,
> so "owner /dev/shm/org.chromium.* rw," is enough. I suspect that:

Oh, yeah, that makes sense.
 
> Can you please try replacing:
> 
>   owner /dev/shm/org.chromium.* rw,
> 
> with:
> 
>   owner /{dev,run}/shm/org.chromium.* rw,
> 
> … and then `sudo apparmor_parser -r 
> /etc/apparmor.d/torbrowser.Browser.firefox'
> and retry?

Much better.

At startup I get only ALLOWED messages:

Sep  8 14:58:42 jadzia kernel: [978231.420401] audit: type=1400 
audit(1504875522.291:7386): apparmor="ALLOWED" operation="exec" 
profile="/usr/bin/torbrowser-launcher" name="/sbin/ldconfig" pid=29296 
comm="torbrowser-laun" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.421179] audit: type=1400 
audit(1504875522.292:7387): apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/bin/torbrowser-launcher//null-/sbin/ldconfig" 
name="/sbin/ldconfig" pid=29296 comm="ldconfig" requested_mask="mr" 
denied_mask="mr" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.421186] audit: type=1400 
audit(1504875522.292:7388): apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/bin/torbrowser-launcher//null-/sbin/ldconfig" 
name="/sbin/ldconfig" pid=29296 comm="ldconfig" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.421355] audit: type=1400 
audit(1504875522.292:7389): apparmor="ALLOWED" operation="open" 
profile="/usr/bin/torbrowser-launcher//null-/sbin/ldconfig" 
name="/etc/ld.so.cache" pid=29296 comm="ldconfig" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.524279] audit: type=1400 
audit(1504875522.395:7390): apparmor="ALLOWED" operation="exec" 
profile="/usr/bin/torbrowser-launcher" name="/usr/bin/gpgconf" pid=29299 
comm="torbrowser-laun" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.525244] audit: type=1400 
audit(1504875522.396:7391): apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/bin/torbrowser-launcher//null-/usr/bin/gpgconf" 
name="/usr/bin/gpgconf" pid=29299 comm="gpgconf" requested_mask="mr" 
denied_mask="mr" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.525249] audit: type=1400 
audit(1504875522.396:7392): apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/bin/torbrowser-launcher//null-/usr/bin/gpgconf" 
name="/usr/bin/gpgconf" pid=29299 comm="gpgconf" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.525252] audit: type=1400 
audit(1504875522.396:7393): apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/bin/torbrowser-launcher//null-/usr/bin/gpgconf" 
name="/lib/x86_64-linux-gnu/ld-2.24.so" pid=29299 comm="gpgconf" 
requested_mask="mr" denied_mask="mr" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.525254] audit: type=1400 
audit(1504875522.396:7394): apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/bin/torbrowser-launcher//null-/usr/bin/gpgconf" 
name="/lib/x86_64-linux-gnu/ld-2.24.so" pid=29299 comm="gpgconf" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Sep  8 14:58:42 jadzia kernel: [978231.525329] audit: type=1400 
audit(1504875522.396:7395): apparmor="ALLOWED" operation="open" 
profile="/usr/bin/torbrowser-launcher//null-/usr/bin/gpgconf" 
name="/etc/ld.so.preload" pid=29299 comm="gpgconf" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0

After the tor circuit is established, and when the GUI appears
there's one DENIED:

Sep  8 14:58:48 jadzia kernel: [978237.358518] kauditd_printk_skb: 71 callbacks 
suppressed
Sep  8 14:58:48 jadzia kernel: [978237.358526] audit: type=1400 
audit(1504875528.229:7467): apparmor="DENIED" operation="open" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/proc/29486/fd/" pid=29486 comm="Gecko_IOThread" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000

(PID 29486 is
/home/gregoa/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/plugin-container
But I can still interact with the plugins.)

After that I can enter a URL and go there without any further
messages or any visible problems in the browser.
 
> If that works better for you, then I'll submit a pull request upstream
> about this (and will ask my team-mates who actively maintain
> torbrowser-launcher to consider applying the patch in Debian without
> waiting for a new upstream release).

Sounds good, thanks!


Cheers,
gregor

-- 
 .''`.  https://info.

Bug#874651: FTBFS with Java 9: javax.rmi

[Chris West]

Source: libquartz-java
Version: 1:1.8.6-4
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

javax.rmi has moved into a module, which is currently a poor state of
affairs. See the javax.activation section on the wiki for more details.

Build log:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (default-cli) on 
project quartz: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/libquartz-java-1.8.6/quartz/src/main/java/org/quartz/jobs/ee/ejb/EJBInvokerJob.java:31:
 error: package javax.rmi is not visible
[ERROR] import javax.rmi.PortableRemoteObject;
[ERROR] ^
[ERROR]   (package javax.rmi is declared in module java.corba, which is not in 
the module graph)
[ERROR] 
[ERROR] Command line was: /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc 
@options @packages
[ERROR] 
[ERROR] Refer to the generated Javadoc files in 
'/build/libquartz-java-1.8.6/quartz/target/apidocs' dir.



Cheers,
Chris.

Bug#764263: linux-image-3.16-2-amd64: WARNING at drivers/base/firmware_class.c:1109 _request_firmware+0x521/0xaf0() [btusb?]

[Darshaka Pathirana]

Hi,

I know, this is a very old bug report but as I am still running
Debian/jessie (and others might too), I thought my findings would
still be helpful and/or lead to closing this bug.

On 10/07/2014 09:18 AM, Bjørn Mork wrote:
> Ben Hutchings  writes:
>> On Mon, 2014-10-06 at 20:15 +0200, Julien Cristau wrote:
>>> Package: src:linux
>>> Version: 3.16.3-2
>>> Severity: normal
>>>
>>> Hi,
>>>
>>> I get the following trace in my kernel log, which I don't think I've
>>> seen in pre-3.16 versions:
>>>
>>> Sep 29 19:12:49 betterave kernel: [ 7696.920600] PM: resume of devices 
>>> complete after 508.149 msecs
>>> Sep 29 19:12:49 betterave kernel: [ 7696.921181] [ cut here 
>>> ]
>>> Sep 29 19:12:49 betterave kernel: [ 7696.921188] WARNING: CPU: 2 PID: 3533 
>>> at /build/linux-P15SNz/linux-3.16.3/drivers/base/firmware_class.c:1109 
>>> _request_firmware+0x521/0xaf0()
>> [...]
>>> Sep 29 19:12:49 betterave kernel: [ 7696.921405]  [] ? 
>>> request_firmware+0x2c/0x40
>>> Sep 29 19:12:49 betterave kernel: [ 7696.921412]  [] ? 
>>> btusb_setup_bcm_patchram+0x85/0x430 [btusb]
>>> Sep 29 19:12:49 betterave kernel: [ 7696.921419]  [] ? 
>>> rpm_check_suspend_allowed+0x6a/0xc0
>> [...]
>>> Sep 29 19:12:49 betterave kernel: [ 7696.921528] bluetooth hci0: firmware: 
>>> brcm/BCM20702A0-0a5c-21e6.hcd will not be loaded
>> [...]
>>
>> This means: btusb tries to load firmware during its resume operation,
>> when userland is not yet available.  This doesn't work if firmware
>> loading depends on the userland firmware agent.
>>
>> The warning won't appear if the firmware is installed in the usual
>> place, as direct loading will work.  And the firmware agent is npw
>> deprecated and not even enabled in Debian kernels.  We could remove this
>> warning, but it would be papering over a driver bug.
> 
> Are you sure about this?  FWIW I've occasionally seen similar warnings
> from another btusb device with firmware (using kernels I've built
> myself, so not reported here of course). And I haven't really bothered to
> look at the root cause before, so I haven't reported it upstream either.
> [...]

I also got this kernel backtrace log, especially after resume from
suspend. So I tested the following configurations:

* Kernel: 3.16.43-2+deb8u2 / without firmware
* Kernel: 3.16.43-2+deb8u2 / with firmware
* Kernel: 4.9.30-2+deb9u2~bpo8+1 / without firmware
* Kernel: 4.9.30-2+deb9u2~bpo8+1 / with firmware

Finding the correct firmware is a complete different story (see
my comments in #801084 for details) but I only got the kernel
backtrace log with the first configuration (Kernel: 3.16.43-2+deb8u2 /
without firmware).

So I think this issue is fixed in the jessie-backports kernel.

If you need more information on this, please let me know. If Julien
can confirm that the kernel log is not shown with the new kernel
version, this bug can be closed.

Regards,
 - Darsha



signature.asc
Description: OpenPGP digital signature

Bug#801084: regression from jessie

[Darshaka Pathirana]

Hi,

On 06/13/2017 02:03 PM, Juha Jäykkä wrote:
> 
> I upgraded from jessie to stretch a few days ago and bluetooth stopped 
> working. With some digging around, it seems I'm affected by this bug.
> 
> The trouble is exacerbated by the fact that the firmware file from the github 
> link does not work on my bt adapter. It loads fine, no error messages, no 
> nothing. No working hci0 either.
> 
> I actually get a hci0:
> 
> hci0: Type: Primary  Bus: USB
>   BD Address: 34:23:87:FF:76:12  ACL MTU: 1021:8  SCO MTU: 64:1
>   DOWN 
>   RX bytes:3374 acl:0 sco:0 events:409 errors:0
>   TX bytes:36217 acl:0 sco:0 commands:408 errors:0
> 
> but it cannot be brought up:
> 
> # hciconfig hci0 up
> Can't init device hci0: Invalid request code (56)

Which firmware did you choose? I found it very difficult to find the
correct one[1] because the firmware driver from winterheart @ github
does not work for my notebook (Lenovo X230). I recently installed the
jessie-backports kernel (to fix another firmware-related kernel bug,
see: #764263) and can confirm that the bluetooth adapter does work
even without a firmware driver loaded.

But be aware: if you load the wrong firmware driver you have to
poweroff the system to unload the firmware (rmmod/modprobe and/or
restarting the system after deleting the firmware from
`/lib/firmware/brcm` is *not* enough).

(Side question: Does anyone know a way to unload the firmware?)


[1] Finding the correct firmware was not easy. On my research I
stumbled over this: https://www.slackwiki.com/Btfirmware-nonfree

He basically downloads the Windows drivers and extracts the firmware
as hex file (BCM20702A1_001.002.014.0449.0462.hex) and converts it
to the hcd format (BCM20702A1-0a5c-21e6.hcd) (via hex2hcd from
jessesung @ github).
As the Thinkpad T430s and my X230 seem to have the same firmware I
attached them for your convenience. Maybe is works for you too.

(Note for Debian/jessie users with Kernel 3.16:
BCM20702A0-0a5c-21e6.hcd is expected as firmware filename).

@Fabian: does the drivers provided by plugable.com really work?
Because they have the ID 0a5c:21e8 whereas your system has a
0a5c:21e6.

@winterheart (aka Azamat): what is difference of the firmware drivers
in your collection and the drivers which are provided by Lenovo?

@bluez-firmware-maintainers:

What needs to be done to bring these firmware drivers in this package?
How can we help?

Regards,
 - Darsha
:02040009F1
:2800010800694204204EB1FD0400400600A0027020020A00280009001D
:FB002800411A0042726F6164636F6D20426C7565746F6F74682044657669636500980100035C010001720600030800017A0208930400200068040012000C006A360003001200B000A000400052008000900060007000C100D00020003000690200CE015D0C000A64E6B08898425A33435F09003C280100040004F70C0A6F0098160800C600F3025D0066033000C900E10268005C033600C300E2026A0053033C00C200E1026C004E034100C500D60272004A034300C300CE02790042034800C500C00283003A034E00C800BF0282003B034E00C900BC02840037035200FF
:FB0123000808070707070707060606060505050502C0F00094FC0E005E0230FC0E000F00630400FD0E000F00680288FC0E0000022CFC0E00490470FC0E000B0974FC0E002E01D8FF0E006219D0FC0E0020C9C8FC0E003885DCFC0E001CC8CCFD0E0004805CFC0E00020020FC0E001921E0FC0E80C0FC0E002200948F080000100010988F080000109C8F08FF00040404CCFC0ED4
:FB021E2B45D07B0001040A08FC0E002E360CFC0E002CAE10FC0E002AAC14FC0E00A22218FC0E001D201CFC0E000D1520FC0E00858D24FC0E00831128FC0E00000198FF0E003E41C316001269141F310870047836047430607180764A3108290ACF0900100F0C6EF0B009F060D10900010403036B1420206B1A2400FF010808041EFC0CF80AF408F006EC04E802041EFC0CF80AF408F006EC04E8020301000182D600040602020A233C5A6E7D800080008000800080008026
:FB031980028002800280028002800214FF1F880AFF610014FF1F820AFF610014FF1F000AFF610014FF1F080AFF610014FF1F0B0AFF610014FF1F100AFF61004068027B4068027B4068027B4068027B4069027B4069027B82D600FF0602020A233C5A6E7D80008000800080008000800080028002800280028002800214FF1F880AFF20001422
:FB041400FF1F820AFF430014FF1F000AFF660014FF1F080AFF660014FF1F0B0AFF430014FF1F100AFF2000417B417B417B417B417B417B861200041300400840130001000180FF000113C15E0044041422A244041422A2

Bug#850888: kdelibs4support: Please migrate to openssl1.1 in buster

[Steven Zalek]

Dear Maintainer,

I attempted to install libkdelib4support-dev, but it requires
libssl1.0-dev. However, libssl1.0-dev conflicts with libssl-dev (version
1.1); libssl-dev is required on my system to support other applications.

I have not installed libkdelib4support-dev on my system. Please update
libkdelib4support-dev such that it does not conflict with the default
libssl-dev.

Thanks.

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

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

Versions of packages libkf5kdelibs4support-dev depends on:
pn  kdoctools-dev   
pn  kgendesignerplugin  
pn  kinit-dev   
pn  kross-dev   
ii  libkf5configwidgets-dev 5.37.0-2
ii  libkf5crash-dev 5.37.0-2
pn  libkf5dnssd-dev 
pn  libkf5emoticons-dev 
ii  libkf5guiaddons-dev 5.37.0-2
ii  libkf5iconthemes-dev5.37.0-2
pn  libkf5idletime-dev  
pn  libkf5itemmodels-dev
pn  libkf5kcmutils-dev  
ii  libkf5kdelibs4support5  5.37.0-2
ii  libkf5kdelibs4support5-bin  5.37.0-2
pn  libkf5khtml-dev 
pn  libkf5mediaplayer-dev   
pn  libkf5newstuff-dev  
ii  libkf5notifications-dev 5.37.0-2
pn  libkf5notifyconfig-dev  
ii  libkf5parts-dev 5.37.0-2
pn  libkf5plotting-dev  
pn  libkf5style-dev 
pn  libkf5su-dev
ii  libkf5textwidgets-dev   5.37.0-2
pn  libkf5threadweaver-dev  
pn  libkf5unitconversion-dev
pn  libkf5wallet-dev
pn  libkf5webkit-dev
ii  libkf5windowsystem-dev  5.37.0-2
pn  libssl1.0-dev   
ii  qtbase5-dev 5.9.1+dfsg-9

libkf5kdelibs4support-dev recommends no packages.

libkf5kdelibs4support-dev suggests no packages.

*Steven F. Zalek*
Email:zalek.ste...@gmail.com
Mobile:   (734) 255-0404

Bug#874652: python3-socketio-client: Set enable_multithread=True when instanciating Websocket

[Celelibi]

Package: python3-socketio-client
Version: 0.6.5-0.1
Severity: normal

Dear Maintainer,

When instanciating the Websocket class through the create_connection
function (in the constructor of the WebsocketTransport class), the flag
enable_multithread should be set to True. The module SocketIO.client
uses a thread to send a heartbeat. On rare occasions, both threads try
to send some data on the same ssl socket at the same time. This lead to
a segmentation fault in the openssl library, thus crashing the python
interpreter.

Regards,
Celelibi

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

Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages python3-socketio-client depends on:
ii  python3-requests   2.18.1-1
ii  python3-six1.10.0-4
ii  python3-websocket  0.37.0-2

python3-socketio-client recommends no packages.

python3-socketio-client suggests no packages.

-- no debconf information

Bug#863266: Re: Bug#863266: [Pkg-libvirt-maintainers] Bug#863266: libvirt-daemon: spice port conflict - multiple VMs want Port 5900

[Guido Günther]

Hi Marc,
On Sun, Aug 13, 2017 at 10:51:25AM +0200, Marc Haber wrote:
> found #863266 3.6.0-1
> thanks
> 
> On Thu, Aug 03, 2017 at 11:32:37AM -0300, Guido Günther wrote:
> > Thanks for checking. I'll close the bug for sid then at least. I have no
> > idea yet how the kernel enters the game on stretch though.
> 
> I still have the issue on current sid. I am, however, also running a
> current kernel, 4.12.7 at the moment.

Could this be the problem you're seeing:

https://bugzilla.redhat.com/show_bug.cgi?id=1489854

It seems we're somehow not tracking ports over daemon restarts
anymore. If it is your problem it should go away if you

 - shut down all vms
 - restart libvirtd

Port allocation should now work _until_ you restart libvirtd again. If
this is the issue I'll mark this bug as forwarded.
Cheers,
 -- Guido

Bug#874653: FTBFS with Java 9: window.getPeer()

[Chris West]

Source: libskinlf-java
Version: 6.7
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

window.getPeer() is gone. There doesn't seem to be an easy work around
in this case. Upstream is 4+ years idle.

https://bugs.openjdk.java.net/browse/JDK-8134422

The code is in a class named "Win32..", maybe it can just be deleted
for Debian?

Build log:

[javac] 
/build/libskinlf-java-6.7/build/src/com/l2fprod/gui/nativeskin/win32/Win32NativeSkin.java:203:
 error: cannot find symbol
[javac] if (window.getPeer() == null) {
[javac]   ^
[javac]   symbol:   method getPeer()
[javac]   location: variable window of type Window
[javac] 
/build/libskinlf-java-6.7/build/src/com/l2fprod/gui/nativeskin/win32/Win32NativeSkin.java:220:
 error: cannot find symbol
[javac] invoke(window.getPeer(), null);
[javac]  ^
[javac]   symbol:   method getPeer()
[javac]   location: variable window of type Window




Cheers,
Chris.

Bug#863266: Re: Bug#863266: [Pkg-libvirt-maintainers] Bug#863266: libvirt-daemon: spice port conflict - multiple VMs want Port 5900

[Marc Haber]

On Fri, Sep 08, 2017 at 03:39:56PM +0200, Guido Günther wrote:
> On Sun, Aug 13, 2017 at 10:51:25AM +0200, Marc Haber wrote:
> > found #863266 3.6.0-1
> > thanks
> > 
> > On Thu, Aug 03, 2017 at 11:32:37AM -0300, Guido Günther wrote:
> > > Thanks for checking. I'll close the bug for sid then at least. I have no
> > > idea yet how the kernel enters the game on stretch though.
> > 
> > I still have the issue on current sid. I am, however, also running a
> > current kernel, 4.12.7 at the moment.
> 
> Could this be the problem you're seeing:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1489854

Unlikely. When I have more than one Vm on Autoport and Autostart, only
one of them is running after a host reboot, and the others don't start
because of the port already been taken. All this without restarting
libvirt daemon after rebooting the host.

And since things are fine with a Debian kernel, this might be a kernel
config issue. I don't have the slightest clue what might be the fault
here, and I have not yet found the time to bisect kernel config.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#874655: FTBFS with Java 9: The type java.lang.String cannot be resolved.

[Chris West]

Source: libspring-java
Version: 4.3.10
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

No idea what's going on here, there's some possibility the issue is
inside gradle, but it appears to actually be breaking while running an
ant job. Upstream appear to have looked at Java 9 support multiple years
ago, but not recently? Some sub-components of Spring are looking at it
actively, so maybe the errors are going to get resolved:
https://github.com/spring-projects/spring-boot/issues/7226

I'm raising this issue mainly because I can't find this build log
excerpt anywhere:

[ant:iajc] 
/build/libspring-java-4.3.10/spring-aspects/src/main/java/org/springframework/transaction/aspectj/AbstractTransactionAspect.aj
 [error] The type java.lang.String cannot be resolved. It is indirectly 
referenced from required .class files
[ant:iajc] (no source information available)
[ant:iajc] 
/build/libspring-java-4.3.10/spring-aspects/src/main/java/org/springframework/transaction/aspectj/AbstractTransactionAspect.aj:48
 [error] The hierarchy of the type AbstractTransactionAspect is inconsistent
[ant:iajc] public abstract aspect AbstractTransactionAspect extends 
TransactionAspectSupport implements DisposableBean {
[ant:iajc]
[ant:iajc] 
/build/libspring-java-4.3.10/spring-aspects/src/main/java/org/springframework/transaction/aspectj/AbstractTransactionAspect.aj:48
 [error] The hierarchy of the type AbstractTransactionAspect is inconsistent
[ant:iajc] public abstract aspect AbstractTransactionAspect extends 
TransactionAspectSupport implements DisposableBean {
[ant:iajc]
[ant:iajc] 
/build/libspring-java-4.3.10/spring-aspects/src/main/java/org/springframework/transaction/aspectj/AbstractTransactionAspect.aj:48
 [error] The hierarchy of the type AbstractTransactionAspect is inconsistent
[ant:iajc] public abstract aspect AbstractTransactionAspect extends 
TransactionAspectSupport implements DisposableBean {
[ant:iajc]
[ant:iajc] 
[ant:iajc] 4 errors
:spring-aspects:compileJava FAILED
:spring-aspects:compileJava (Thread[Task worker Thread 24,5,main]) completed. 
Took 2.583 secs.



Cheers,
Chris.

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Salvo Tomaselli]

Package: libegl1-mesa
Version: 17.2.0-2
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

after the upgrade, trying to play team fortress 2 causes the machine to get
stuck after a few seconds of playing.

Seemingly, downgrading fixes the issues.

I'm opening this at high severity so it can be looked into before it migrates,
and people are aware before upgrading.

It isn't really easy for me to give logs, since the entire machine just crashes
requiring an hard reset.

Best.

-- Package-specific info:
glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_SGI_make_current_read, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)  (0x1916)
Version: 13.0.6
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 13.0.6
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, 
GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, 
GL_AMD_shader_stencil_export, GL_AMD_shader_trinary_minmax, 
GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, 
GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, 
GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, 
GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, 
GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, 
GL_ARB_blend_func_extended, GL_ARB_buffer_storage, 
GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, 
GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, 
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, 
GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, 
GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, 
GL_ARB_derivative_control, GL_ARB_direct_state_access, 
GL_ARB_draw_buf

Bug#874657: pcmanfm: should have explicit recommends on lxpolkit | polkit-1-auth-agent

[Raphaël Hertzog]

Source: pcmanfm
Version: 1.2.5-3
Severity: important
Tags: patch
User: de...@kali.org
Usertags: origin-kali kali-patch

The LXDE image produced by Kali is severly broken and the cause is that
"apt install lxde" ends up installing a mix of lxde and lxqt.

« apt -o Debug::pkgDepCache::AutoInstall="yes" install lxde » shows this:
[...]
Installing lxqt-policykit as Recommande of pcmanfm
  Installing liblxqt0 as Dépend of lxqt-policykit
[...]
  Installing libpolkit-qt5-1-1 as Dépend of lxqt-policykit
  Installing lxqt-session as Dépend of lxqt-policykit

At the end, ligthdm starts the lxqt session but it is broken
because lxqt-panel is not installed.

The fix is simply to change the Recommends from « polkit-1-auth-agent | 
policykit-1-gnome »
to « lxpolkit | polkit-1-auth-agent | policykit-1-gnome » or maybe only
« lxpolkit ».

diff --git a/debian/control b/debian/control
index 14c4893..1260a27 100644
--- a/debian/control
+++ b/debian/control
@@ -17,7 +17,7 @@ Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}, shared-mime-info
 Recommends:
  gvfs-backends, gvfs-fuse [!hurd-any],
- polkit-1-auth-agent | policykit-1-gnome,
+ lxpolkit | polkit-1-auth-agent | policykit-1-gnome,
  lxde-icon-theme | gnome-icon-theme | oxygen-icon-theme | tango-icon-theme
 Description: extremely fast and lightweight file manager
  PCMan File Manager is a GTK+ based file manager, featuring:


Note that pcmanfm-qt correctly recommends lxqt-policykit and does not even
allow any alternative. I'm not sure that allowing alternatives is a good idea
since you want to ensure a well integrated experience. The policy kits agents
are co-installable anyway so it does not cause any problem.

Thank you!

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

Kernel: Linux 4.12.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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#874658: FTBFS with Java 9: no suitable constructor for JTable

[Chris West]

Source: libswingx-java
Version: 1:1.6.2-2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

This might be generics changes (due to the new -source), or Swing changes.

Build log:

ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/libswingx-java-1.6.2/swingx-core/src/main/java/org/jdesktop/swingx/JXTable.java:[564,9]
 no suitable constructor found for JTable(java.util.Vector,java.util.Vector)
constructor 
javax.swing.JTable.JTable(javax.swing.table.TableModel,javax.swing.table.TableColumnModel)
 is not applicable
  (argument mismatch; java.util.Vector cannot be converted 
to javax.swing.table.TableModel)
constructor javax.swing.JTable.JTable(int,int) is not applicable
  (argument mismatch; java.util.Vector cannot be converted 
to int)
constructor javax.swing.JTable.JTable(java.util.Vector,java.util.Vector) is not applicable
  (argument mismatch; java.util.Vector cannot be converted 
to java.util.Vector)
constructor 
javax.swing.JTable.JTable(java.lang.Object[][],java.lang.Object[]) is not 
applicable
  (argument mismatch; java.util.Vector cannot be converted 
to java.lang.Object[][])
[INFO] 1 error


Cheers,
Chris.

Bug#874659: orig-tarball-missing-upstream-signature should not trigger on repacked tarballs

[Guido Günther]

Package: lintian
Version: 2.5.52
Severity: normal

Hi,
We can't use the signatures for these. We don't have a recommended
mechanisms to detect these but looking for +dfsg in the upstream version
and looking for a filter in debian/copyright should catch most of these.
Cheers,
 -- Guido

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

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

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

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

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

-- no debconf information

Bug#874660: FTBFS with Java 9: sun.misc

[Chris West]

Source: libxbean-java
Version: 4.5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

sun.misc.URLClassPath seems to have been removed.

https://github.com/OpenHFT/Java-Thread-Affinity/issues/37 contains an
example of replacing it with real code.

Build log:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile) 
on project xbean-classpath: Compilation failure: Compilation failure: 
[ERROR] 
/build/libxbean-java-4.5/xbean-classpath/src/main/java/org/apache/xbean/classpath/SunURLClassPath.java:[59,23]
 cannot find symbol
[ERROR]   symbol:   class URLClassPath
[ERROR]   location: package sun.misc
[ERROR] 
/build/libxbean-java-4.5/xbean-classpath/src/main/java/org/apache/xbean/classpath/SunURLClassPath.java:[52,17]
 cannot find symbol
[ERROR]   symbol:   class URLClassPath
[ERROR]   location: package sun.misc




Cheers,
Chris.

Bug#874661: FTBFS with Java 9: enum keyword

[Chris West]

Source: libxml-commons-resolver1.1
Version: 1.2
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

It uses enum as a keyword, which is illegal in the now-mandatory -source
1.6. Note that you will need modern ant in sid to get this far.

Build log:

[javac] 
/build/libxml-commons-resolver1.1-java-1.2/src/org/apache/xml/resolver/Catalog.java:1175:
 error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] Enumeration enum = catalogEntries.elements();
[javac] ^
[javac] 
/build/libxml-commons-resolver1.1-java-1.2/src/org/apache/xml/resolver/Catalog.java:1177:
 error: as of release 5, 'enum' is a keyword, and may not be used as an 
identifier
[javac] while (enum.hasMoreElements()) {
[javac]^




Cheers,
Chris.

Bug#874662: FTBFS with Java 9: javax.xml.bind

[Chris West]

Source: libxmlrpc3-java
Version: 3.1.3-8
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

Specifically, the section on javax.xml.bind is relevant here. We don't
have a good solution, at the time of writing; check the wiki for new
info.

Build log:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (default-cli) on 
project xmlrpc-common: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/libxmlrpc3-java-3.1.3/common/src/main/java/org/apache/xmlrpc/jaxb/JaxbParser.java:21:
 error: package javax.xml.bind is not visible
[ERROR] import javax.xml.bind.JAXBContext;
[ERROR] ^



Cheers,
Chris.

Bug#874663: Document +dfsg as extenson when repacking upstream sources

[Guido Günther]

Package: debian-policy
Version: 4.1.0.0
Severity: wishlist

Hi,
when upstream tarballs need to be repacked because they contain non-dfsg
free data appending '+dfsg' to the upstream version seems common
practice. However some packages append '.dfsg', others use
+dfsg and there are more formats around.

It would be great if policy could recommend +dfsg as the default
(falling back to +dfsg if there was a packaging error (i.e. some
files slip through and the package was rejected by ftp-masters).

This would make it simpler for tools like lintian or gbp to detect repacked
tarballs (in this case we don't want to attach the upstream signature to
the chages file).
Cheers,
 -- Guido

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

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

Versions of packages debian-policy depends on:
ii  libjs-sphinxdoc  1.5.6-2

debian-policy recommends no packages.

Versions of packages debian-policy suggests:
pn  doc-base  

-- no debconf information

Bug#810898: apt: "apt-get update" (1.2) very slow with compressed indices and debtags

[Julian Andres Klode]

Control: reassign -1 apt

On Fri, Sep 08, 2017 at 02:46:10PM +0200, Enrico Rossi wrote:
> Hi,
> 
> Enrico Zini made this python3 code to test the problem outside debtags:
> 
> #!/usr/bin/python3
> import apt
> 
> def main():
> cache = apt.Cache()
> for pkg in cache:
> cand = pkg.candidate
> if not cand: continue
> tags = cand.record.get("Tag", None)
> if not tags: continue
> print(pkg.name, tags)
> 
> if __name__ == "__main__":
> main()
> 
> Running it without compressed index in apt:
> 
> # time python3 cattags >/dev/null 
> real  0m1.671s
> user  0m1.539s
> sys   0m0.132s
> 
> with compressed index:
> 
> # time python3 cattags >/dev/null 
> real  1m44.238s
> user  1m33.536s
> sys   0m10.698s
> 
> I'm going to re-assign the bug to python-apt, maybe they have more info
> on the issue.

So the problem really is that random access to lz4 compressed files
does not really exist, instead, when seeking backwards in it, we seek
to the beginning and then re-read until we reached our target position.
When seeking forward, we simply read and discard the bytes from the
current position to the target.

I'm not sure how much backward seeks are involved in that, but if
the slowdown is substantial, probably a lot. I fear that because the
tag file uses a buffer and reads further than needed in the compressed
stream that essentially *every* jump is a backward read, thus causing
a quadratic amount of bytes sum(k * average_section_size, k=1...n) to 
be decompressed - yes, you read that right, O(n^2).

That's of course inefficient. One way to work around this is to make
TagFile use FileFd's native buffering support somehow, instead of maintaining
its own buffer. Then FileFd could just seek forward in the buffer and
then (if needed) in the file  instead of discarding the buffer and
starting from the beginning again.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#874664: Update ledgersmb package to 1.5.x series

[Robert J. Clay]

Package: ledgersmb
Severity: normal

The current version of the LedgerSMB application in Debian is version
1.4.41. As currently noted on the LedgerSMB web site [1], "Version 1.4
will keep receiving critical updates until Sep 15, 2017."; so soon the
ledgersmb package will require updating to a newer version series.

Version 1.5.0 for the LedgerSMB application was released on 23
December 2017 and the most recent version of the 1.5.x series was
version 1.5.10 which was released on 3 September 2017. Update the
ledgersmb package in Debian to the 1.5.x version series of the
application.


-- 
Robert J. Clay
rjc...@gmail.com, j...@rocasa.us
GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A

[1] https://ledgersmb.org/

Bug#873706: [Pkg-utopia-maintainers] Bug#874614: Bug#874614: Please demote some packages from dependency to recommendation

[Andreas Henriksson]

Hello!

On Fri, Sep 08, 2017 at 02:46:06PM +0200, Michael Biebl wrote:
[...]
> Andreas, have you tested if e.g. lvm2 or btrfs support actually works in
> the Debian udisks2 package?

No.

Regards,
Andreas Henriksson