Bug#827149: RFS: triggerhappy/0.4.0-1

[Stefan Tomanek]

Good morning,

Dies schrieb Sean Whitton (spwhit...@spwhitton.name):

> On Sun, Jun 12, 2016 at 11:59:34PM +0200, Stefan Tomanek wrote:
> >   Changes since the last upload:
> > 
> >* update to version 0.4.0 (closes: bug#827079, bug#769184)
> 
> Although this bug closing syntax is acceptable, it's marked as "not
> preferred" Developer's Reference section 5.8.4.  You might consider the
> more usual syntax:
> 
> Closes: #769184, #827079
> 
> and you should perhaps mention that 0.4.0 is a new *upstream* version.
> 
> >* adapt to newer debian packaging standards
> 
> Could you be more verbose here, please?  What you wrote could mean a lot
> of things!

Thanks for your input, I adjusted the changelog accordingly and reuploaded the
package.

Bug#827159: /usr/share/man/man5/logind.conf.5.gz: Wrong default for KillUserProcesses= in the logind.conf(5) manpage

[Laurent Bigonville]

Package: systemd
Version: 230-2
Severity: normal
File: /usr/share/man/man5/logind.conf.5.gz

Hi,

The logind.conf.5 manpage states that default value for
KillUserProcesses= is "yes"

But package in debian has reverted this to "no" at compile time.

The man page should be fixed.

Regards,

Laurent Bigonville

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser 3.114
ii  libacl1 2.2.52-3
ii  libapparmor12.10-4
ii  libaudit1   1:2.5.2-1
ii  libblkid1   2.28-5
ii  libc6   2.22-11
ii  libcap2 1:2.25-1
ii  libcap2-bin 1:2.25-1
ii  libcryptsetup4  2:1.7.0-2
ii  libgcrypt20 1.7.0-2
ii  libgpg-error0   1.22-2
ii  libkmod222-1.1
ii  liblzma55.1.1alpha+20120614-2.1
ii  libmount1   2.28-5
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.5-3
ii  libsystemd0 230-2
ii  mount   2.28-5
ii  util-linux  2.28-5

Versions of packages systemd recommends:
ii  dbus1.10.8-1
ii  libpam-systemd  230-2

Versions of packages systemd suggests:
ii  systemd-container  230-2
ii  systemd-ui 3-4

Versions of packages systemd is related to:
ii  udev  230-2

-- no debconf information

Bug#821150: cmucl: non-DFSG license

[Peter Van Eynde]

Hello Dmitry,

On 19/04/16 23:18, Dmitry Smirnov wrote:
> But this requirement is not optional. License do not allow us to speculate 
> whether they are checking their post box or email and choose whether to 
> comply with this requirement...

I checked and nobody is listening anymore at that email address, or at
xerox in general. For all intents and purposes the upstream is gone.

Furthermore I've discussed this with the CMUCL developers and they,
being native English speakers, interpret this requirement "Any person
obtaining a copy of this software is requested ..." is a request and
this optional, not required. So SHOULD in the rfc2119 way, not MUST.

Is there a precedent or ruling on the 'is requested' in licenses?

Best regards, Peter

-- 
signature -at- pvaneynd.mailworks.org
http://pvaneynd.dreamwidth.org/
God, root, what is difference?-Pitr|God is more forgiving.-Dave Aronson|



signature.asc
Description: OpenPGP digital signature

Bug#827160: jessie-pu: package dosfstools/3.0.27-1+deb8u1

[Petter Reinholdtsen]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-CC: Andreas Bombe 

On my Debian Jessie machine, I would like to fix the two security issues
in dosfstools that show up in the debsecan report:
https://security-tracker.debian.org/tracker/CVE-2016-4804 >
https://security-tracker.debian.org/tracker/CVE-2016-4804 >.

The issues were fixed in Wheezy by the LTS team (DLA-474-1) and is also
fixed in unstable.  I would like to get it fixed in stable too, to get
it out of my debsecan list.

The attached patch is based on the patches in wheezy, and should solve
the problems.

Is it OK to upload the fix for stable?

I plan to push the changes to a debian/jessie branch on collab-maint
once I know the changes are acceptable for a stable update.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=no_NO (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 4f1e009..db765aa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+dosfstools (3.0.27-1+deb8u1) unstable; urgency=medium
+
+  * Non-maintainer upload to fix security issue.
+  * Added d/gbp.conf to document git branch used for Jessie updates.
+  * [CVE-2015-8872] Invalid memory read in fsck.vfat
+  * [CVE-2016-4804] Heap overflow in function read_fat()
+
+ -- Petter Reinholdtsen   Mon, 13 Jun 2016 08:17:24 +0200
+
 dosfstools (3.0.27-1) unstable; urgency=medium
 
   * New upstream version 3.0.27
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..3926a07
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,3 @@
+[DEFAULT]
+debian-branch = debian/jessie
+pristine-tar = True
diff --git a/debian/patches/CVE-2015-8872.diff b/debian/patches/CVE-2015-8872.diff
new file mode 100644
index 000..07fb6c8
--- /dev/null
+++ b/debian/patches/CVE-2015-8872.diff
@@ -0,0 +1,22 @@
+https://github.com/dosfstools/dosfstools/commit/07908124838afcc99c577d1d3e84cef2dbd39cb7
+
+Index: dosfstools-collab/src/fat.c
+===
+--- dosfstools-collab.orig/src/fat.c	2016-06-13 08:07:44.669688617 +0200
 dosfstools-collab/src/fat.c	2016-06-13 08:07:44.665688587 +0200
+@@ -197,10 +197,12 @@
+ 	data[1] = new >> 4;
+ 	} else {
+ 	FAT_ENTRY subseqEntry;
+-	get_fat(&subseqEntry, fs->fat, cluster + 1, fs);
++	if (cluster != fs->clusters - 1)
++	get_fat(&subseqEntry, fs->fat, cluster + 1, fs);
++	else
++	subseqEntry.value = 0;
+ 	data[0] = new & 0xff;
+-	data[1] = (new >> 8) | (cluster == fs->clusters - 1 ? 0 :
+-(0xff & subseqEntry.value) << 4);
++	data[1] = (new >> 8) | ((0xff & subseqEntry.value) << 4);
+ 	}
+ 	size = 2;
+ 	break;
diff --git a/debian/patches/CVE-2016-4804.diff b/debian/patches/CVE-2016-4804.diff
new file mode 100644
index 000..d28174c
--- /dev/null
+++ b/debian/patches/CVE-2016-4804.diff
@@ -0,0 +1,64 @@
+https://github.com/dosfstools/dosfstools/commit/e8eff147e9da1185f9afd5b25948153a3b97cf52
+
+Index: dosfstools-collab/src/boot.c
+===
+--- dosfstools-collab.orig/src/boot.c	2016-06-13 07:59:10.337694024 +0200
 dosfstools-collab/src/boot.c	2016-06-13 08:00:46.290436480 +0200
+@@ -101,8 +101,8 @@
+ 	   (unsigned long long)fs->fat_start,
+ 	   (unsigned long long)fs->fat_start / lss);
+ printf("%10d FATs, %d bit entries\n", b->fats, fs->fat_bits);
+-printf("%10d bytes per FAT (= %u sectors)\n", fs->fat_size,
+-	   fs->fat_size / lss);
++printf("%10lld bytes per FAT (= %llu sectors)\n", (long long)fs->fat_size,
++	   (long long)fs->fat_size / lss);
+ if (!fs->root_cluster) {
+ 	printf("Root directory starts at byte %llu (sector %llu)\n",
+ 	   (unsigned long long)fs->root_start,
+@@ -326,7 +326,7 @@
+ struct boot_sector b;
+ unsigned total_sectors;
+ unsigned short logical_sector_size, sectors;
+-unsigned fat_length;
++off_t fat_length;
+ loff_t data_size;
+ 
+ fs_read(0, sizeof(b), &b);
+@@ -354,8 +354,12 @@
+ /* Can't access last odd sector anyway, so round down */
+ fs_test((loff_t) ((total_sectors & ~1) - 1) * (loff_t) logical_sector_size,
+ 	logical_sector_size);
++
+ fat_length = le16toh(b.fat_length) ?
+ 	le16toh(b.fat_length) : le32toh(b.fat32_length);
++if (!fat_length)
++die("FAT size is zero.");
++
+ fs->fat_start = (loff_t) le16toh(b.reserved) * logical_sector_size;
+ fs->root_start = ((loff_t) le16toh(b.reserved) + b.fats * fat_length) *
+ 	logical_sector_size;
+@@ -363,7 +367,11 @@
+ fs-

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Bogdan Vatra]

Package: nvidia-driver
Version: 352.79-8
Severity: normal

--- Please enter the report below this line. ---

Hello,

NVIDIA 364.12 is coming with lots of (quite desired) features:
- updated Vulkan support
- mir & wayland support (Finally !)

Is there any plans to have it soon as an official debian package?

Thank you!

Yours,
BogDan.

->8--->8--->8--->8--->8--->8--->8--->8--->8--

Bug#827162: needrestart: reports unchanged backport kernel as changed

[Martin Steigerwald]

Package: needrestart
Version: 2.8-1~bpo8+1
Severity: normal

Dear Maintainer,

After apt dist-upgrade on one of my Debian Jessie server VMs, I get

needrestart output:


│ Neuer Kernel vorhanden

  │ 
│   

  │ 
│ Die aktuelle Kernel-Version ist 4.5.0-0.bpo.2-686, es wird jedoch die 
Version 4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) #1 SMP Debian 
4.5.4-1~bpo8+1   │ 
│ (2016-05-13) erwartet.

  │ 
│   

  │ 
│ Das System wird nicht automatisch neu gestartet, um den neuen Kernel zu 
laden. Ein Neustart sollte durchgeführt werden.   

Means it thinks the kernel has changed, while it has not. I know for sure
I booted exactly this kernel. It seems to be confused detecting the end of
the version number in the second case as it appears that it uses the whole
output of /proc/version for comparison.

mondschein:~> cat /proc/version
Linux version 4.5.0-0.bpo.2-686 (debian-ker...@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13)


Why doesn´t it just use uname -r and be done with it?


On another of my Debian Jessie server VMs I am not seeing this issue, but
it uses amd64 as architecture instead of i386.

Thanks,
Martin

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.5.0-0.bpo.2-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages needrestart depends on:
ii  dpkg   1.17.27
ii  gettext-base   0.19.3-2
ii  libintl-perl   1.23-1
ii  libmodule-find-perl0.12-1
ii  libmodule-scandeps-perl1.16-1
ii  libproc-processtable-perl  0.51-1
ii  libsort-naturally-perl 1.03-1
ii  libterm-readkey-perl   2.32-1+b1
ii  perl   5.20.2-3+deb8u5
ii  xz-utils   5.1.1alpha+20120614-2+b3

needrestart recommends no packages.

Versions of packages needrestart suggests:
pn  needrestart-session | libnotify-bin  

-- no debconf information

Bug#827157: otb: hardcoded library build dependencies

[Bas Couwenberg]

Control: tags -1 pending

Hi Pino,

Thanks for the patch. I've applied it and a new otb revision is on its 
way to unstable.


Kind Regards,

Bas

Bug#827163: gitlab requires gitlab-workhorse at version 0.7.1

[Libor Klepáč]

Package: gitlab
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
please tighten dependency on and update workhorse, gitlab doesn't work with 
0.6.3 in archive.

Thanks,

Libor

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXXmmPAAoJEPDvjG7Cn0eOgjsP/2Cd3jN/APwfSauDr9SuqrE5
ImpSVD/WgBYg6rmKiQIExkD3udfHxVBZv96qxWeEAEWmJtempcUqjKmg6CioCitT
De7s04HJZQrcDISH2V4p4zaWSL/7Rw2Yfi2nLFeSOqvFkultQ68y/kdn+snb1DGr
BkiUyxkLayE7w0LOmtgTqz8pLzFdEgsaLKEpjX+ihim+Rg1TYn72gCxqb3xf8AAA
rhdFKAdQ9zd0yk3gUt15cvmxMoPU6Wm/oQRltk1Ep9OsT0QWnA9Vd+1pX1Gu+xJv
PXMwKBeuJquLDg2fUgA2NTWK0rTy1wp+BIm3Ym4sPtPDrEtV6ZiCGunD9mlzfFvu
cfatBMVnGI9u7h5jD2UzBa1TMwfNbtlSkYE6cuRhZmMJQUKspkRbdk2zLEe63m6v
nxLhOCDV82/EN3Be+syjhoWc8NlJJ7titWKOGYiGKx+yDABngvLz0UrC4aHP7Ano
lSPY751wkpKT4n6q0qeDvJL13PzmywbQtcmwE/evidf1sZFQG+Hb9+7dGUB63l1C
mshQBSiDptNBAit1rgLN0pspyCn+q4tBpKJprmlpK6XZBXfLXZPIagadKAh/v+Ca
s5AXkHMoq7MetphR043xhI1JKtDBaVAP0PByyhVCzUXuZDsEgvXmsUnJc4a5ScUW
5NLYNEOR6OezVZR1uJLq
=dKM3
-END PGP SIGNATURE-

Bug#825997: openvpn 2.3.11 breaks connections to Mikrotik routers, 2.3.10 works fine

[Kamil Kachyňa]

It is fixed in RouterOS version 6.36rc28 (Release candidate)

*) ovpn - fixed compatibility with OpenVPN 2.3.11;




smime.p7s
Description: Elektronicky podpis S/MIME

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

[Mathieu Malaterre]

On Fri, Jun 3, 2016 at 5:29 PM, Wolfram Sang  wrote:
> On Tue, Apr 12, 2016 at 12:08:03PM +0200, Mathieu Malaterre wrote:
>> Dear all,
>>
>> I am looking for testers for the following patch:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663#20
>>
>> Wolfram (CC here) is looking for feedback from users for this patch.
>
> For completeness, it should be one of those machines:
>
> https://en.wikipedia.org/wiki/Power_Mac_G4#Wind_Tunnel
>

As Gilles discovered the concerned MDD models are the following:

http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_867_dp_mdd.html

http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.0_dp_mdd.html

http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.25_dp_mdd.html

some people have older PowerPC + SMP machine such as:

http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_450_dp.html

but they are not concerned with this patch.

Sorry for the confusion everybody, thanks to Gilles for the update.

-M

Bug#827104: [Pkg-xfce-devel] Bug#827104: Recommends: obsolete package xfce4-volumed

[ian_bruce]

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


On Sun, 12 Jun 2016 17:30:19 +0200
Yves-Alexis Perez  wrote:

 Please remove this false dependency.
>>> 
>>> It's not a false dependency, it's just that the package has been
>>> removed and the dependency line not updated.
>> 
>> If a dependency on a currently non-existent package is "not false",
>> then I wonder what meaning you think the word has.
>> 
>> Again, do you think this situation is perfectly proper and correct?
>> Do you propose that it should persist indefinitely? Was it incorrect
>> to file a bug report describing it? After all, what's the purpose of
>> filing ANY bug reports; the final collapse of the universe will
>> eventually happen anyway, rendering the whole point moot, as you say.
>
> I honestly don't know what you're talking about, and I frankly don't
> care. This will be fixed in the next package upload anyway.

I'm confused. Does the Debian Project actually WANT people to file bug
reports? If not, why bother having a public bug-tracker, where the
standard reply is, "That's not a bug, you're just too stupid to
understand the perfection that we've created."

Conversely, if bug reports ARE wanted, then why is it considered
appropriate to reply in such a condescending and insulting way, to the
people who file them?

Do you want bug reports, or not? Would anybody care to argue that this
current case is NOT a bug? Should I infer that in the future, you would
prefer that I f*** off, and mind my own business?


-- Ian Bruce

Bug#827111: jessie-pu: package exim4/4.84.2-2

[Julien Cristau]

On Sun, Jun 12, 2016 at 14:06:54 +0200, Andreas Metzler wrote:

> +  * Improve on NEWS file. Closes: #81834

I'm guessing this is not the right bug number.

Cheers,
Julien

Bug#827054: jessie-pu: package openssl/1.0.1t-1+deb8u3

[Julien Cristau]

On Mon, Jun 13, 2016 at 00:50:05 +0200, Kurt Roeckx wrote:

> I should probably add that I don't intend to fix this in
> testing/unstable.  There are probably reverse dependencies that
> saw those symbols are available and then started using them again,
> and so it would break things.  But I'm going to change to the 1.1

Doesn't the same reasoning apply to stable?

Why was this not caught when updating the libssl1.0.2.symbols file for
the new release?

> soname soon anyway, and it'll get fixed at that point.  Also, the
> symbols are available but if you try to use them it's not going to
> do anything useful.
> 

> But I'd like to remove them in stable again, since nothing there
> should use on it now, and it broke something.
> 
Can you be more specific than "broke something"?

Cheers,
Julien

Bug#823865: phpsysinfo: missing copyright

[Frederik Schueler]

Hi Björn,

all files within the debian folder I am the author of are GPL-2.

Best regards
Frederik

On 12.06.2016 11:25, Bjoern Boschman wrote:
> Hi,
> 
> I did not recieve any reply yet.
> Please reply until 2016-06-25. Otherwise I have to choose a copyright on
> my own.
> See also. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823865
> 
> Cheers
> B
> 
> On Thu, May 26, 2016 at 1:59 PM Bjoern Boschman  > wrote:
> 
> Hi,
> 
> as the current maintainer of phpsysinfo I'd like to ask you if GPL-2
> is ok for you for all files within debian/ folder.
> 
> Cheers
> B
> 



signature.asc
Description: OpenPGP digital signature

Bug#827164: unable to start guest with ceph rbd disks

[uli iske]

Package: qemu
Version: 2.6+dfsg-1+b1

When trying to start or migrate Guest with ceph rbd Disk image
connected I get the following error message:

internal error: process exited while connecting to monitor:
2016-06-13T08:11:05.686421Z qemu-system-x86_64: -drive
file=rbd:rbd/sam:id=admin:auth_supported=cephx\;none:mon_host=10.210.0.5\:6789\;10.210.0.6\:6789\;10.210.0.88\:6789,password-secret=virtio-disk0-secret0,format=raw,if=none,id=drive-virtio-disk0,cache=none:
error connecting

Same Guest works ok with qemu version 2.5+dfsg-5+b1

Regards

Uli

Bug#825997: openvpn 2.3.11 breaks connections to Mikrotik routers, 2.3.10 works fine

[Alberto Gonzalez Iniesta]

On Mon, Jun 13, 2016 at 10:09:56AM +0200, Kamil Kachyňa wrote:
> It is fixed in RouterOS version 6.36rc28 (Release candidate)
> 
> *) ovpn - fixed compatibility with OpenVPN 2.3.11;
> 
>

Hi Kamil,

Thanks for the info! Closing now.

Regards,

Alberto



-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#827165: qct: FTBFS:

[Chris Lamb]

Source: qct
Version: 1.7-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

qct fails to build from source in unstable/amd64:

  [..]

  Setting up libqtcore4:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-xml:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqtdbus4:amd64 (4:4.8.7+dfsg-8) ...
  Setting up qtchooser (58-gfab25f1-1) ...
  Setting up qdbus (4:4.8.7+dfsg-8) ...
  Setting up libqt4-dbus:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-network:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-script:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-sql:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libpng16-16:amd64 (1.6.22-1) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up fontconfig (2.11.0-6.4) ...
  Regenerating fonts cache... done.
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up x11-common (1:7.7+15) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libaudio2:amd64 (1.9.4-4) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up liblcms2-2:amd64 (2.7-1) ...
  Setting up libmng1:amd64 (1.0.10+dfsg-3.1+b3) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libtiff5:amd64 (4.0.6-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libqtgui4:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-declarative:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-designer:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-help:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-scripttools:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-svg:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqt4-test:amd64 (4:4.8.7+dfsg-8) ...
  Setting up libqtassistantclient4:amd64 (4.6.3-7) ...
  Setting up python-sip (4.18+dfsg-1) ...
  Setting up python-qt4 (4.11.4+dfsg-2) ...
  Setting up pyqt4-dev-tools (4.11.4+dfsg-2) ...
  Setting up sgml-base (1.27) ...
  Setting up xml-core (0.13+nmu2) ...
  Setting up libxml2-utils (2.9.3+dfsg1-1.2) ...
  Setting up libxslt1.1:amd64 (1.1.28-4) ...
  Setting up xsltproc (1.1.28-4) ...
  Setting up asciidoc (8.6.9-3) ...
  Processing triggers for sgml-base (1.27) ...
  Setting up sgml-data (2.0.10) ...
  Setting up docbook-xsl (1.79.1+dfsg-1) ...
  Processing triggers for sgml-base (1.27) ...
  Setting up docbook-xml (4.5-7.3) ...
  Processing triggers for sgml-base (1.27) ...
  Setting up xmlto (0.0.28-0.1) ...
  Setting up qct-build-deps (1.7-3) ...
  Processing triggers for libc-bin (2.22-11) ...
  Processing triggers for systemd (230-2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=e841f348cd14
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160613093157.saEWe2Ad2h.qct/qct-1.7
  OLDPWD=/home/lamby/temp/cdt.20160613093157.saEWe2Ad2h.qct
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building qct 1.7-3 on amd64
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package qct
  dpkg-buildpackage: info: source version 1.7-3
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Vincent Danjean 

   dpkg-source --before-build qct-1.7
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  test -

Bug#827164: unable to start guest with ceph rbd disks

[Michael Tokarev]

Control: tag -1 + moreinfo

13.06.2016 11:15, uli iske wrote:
> Package: qemu
> Version: 2.6+dfsg-1+b1
> 
> When trying to start or migrate Guest with ceph rbd Disk image
> connected I get the following error message:
> 
> internal error: process exited while connecting to monitor:
> 2016-06-13T08:11:05.686421Z qemu-system-x86_64: -drive
> file=rbd:rbd/sam:id=admin:auth_supported=cephx\;none:mon_host=10.210.0.5\:6789\;10.210.0.6\:6789\;10.210.0.88\:6789,password-secret=virtio-disk0-secret0,format=raw,if=none,id=drive-virtio-disk0,cache=none:
> error connecting

Please give complete qemu error message, not the interpretation
given by libvirt.

Also please ensure you have qemu-block-extra of the right version.

Thanks,

/mjt

Bug#824928: letsencrypt.sh: move the default position of the domains file to /etc/letsencrypt.sh/

[Daniel Beyer]

Hi Mattia,

On Thu, 2016-06-09 at 06:34 +0200, Daniel Beyer wrote:
> Hi Mattia,
> 
> (...)
> 
> I'll get back to you as soon I have implemented something useful here.

I pushed changes to this new branch (based on current debian/master):
wip/dabe/domains.txt-in-etc-maint-scripts

It adds maintainer scripts to deal with domains.txt as well as the
PRIVATE_KEY to ACCOUNT_KEY renaming. I also updated d/NEWS to mention
what happens during the upgrade and updated d/changelog accordingly
using '# gbp dch --snapshot --auto'. Fell free to push additional
changes to it and/or share your opinion about those scripts - or simply
merge it into debian/master.

Note that I did not do anything regarding installing a domains.txt
in /etc/letsencrypt.sh.

I'm not sure if I can react in a timely manner to mails this week, but I
should be able to work on letsencrypt.sh this weekend, if there will be
work left to get 0.2.0-1 ready for an upload to unstable.

Greetings
Daniel


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

Bug#827166: RM: tailor -- ROM; dead upstream, empty Debian package since 2015-08-27

[Vincent Danjean]

Package: ftp.debian.org
Severity: normal

  Hi,

  Tailor seems dead upstream. Its homepage 
(http://progetti.arstecnica.it/tailor)
does not respond anymore. Most of its features are integrated main SCM
(ie conversion mercurial<->git, git<->svn, ...)
  Someone just noticed that the last NMU upload makes the package empty
(ie since 2015-08-27 in testing). So, in my opinion, its not required to
keep this software in Debian anymore.

  Regards,
Vincent

Bug#827004: kdenlive: Segfault or arithmetic exception with "Reverse Clip"

[Patrick Matthäi]

Hey Jean-Baptiste,

could you work with these information?

Am 11.06.2016 um 06:21 schrieb Kyanos:
> Package: kdenlive
> Version: 16.04.1-1
> Severity: normal
>
> Dear Maintainer,
>
> When I try to run the "Reverse Clip" job on a video clip, one of a few
> errors occurs. I've tried this on a few different video clips,  I can't
> find any clear pattern as to which error occurs.
>
>
> GDB sessions follow.
>
> Error 1: Segmentation fault in xmlCheckUTF8__internal_alias (libxml2)
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffa67fb700 (LWP 12597)]
> 0x7fffccd19483 in xmlCheckUTF8__internal_alias (
> utf=utf@entry=0x703532  0x703532>)
> at ../../xmlstring.c:795
> 795 ../../xmlstring.c: No such file or directory.
> (gdb) bt
> #0  0x7fffccd19483 in xmlCheckUTF8__internal_alias (
> utf=utf@entry=0x703532  0x703532>)
> at ../../xmlstring.c:795
> #1  0x7fffccca3311 in xmlNewPropInternal (node=0x7fff681faa30,
> ns=ns@entry=0x0, name=name@entry=0x7fffc8aba09b "description",
> value=0x703532 ,
> eatname=eatname@entry=0) at ../../tree.c:1875
> #2  0x7fffccca34c8 in xmlNewPropInternal (eatname=0,
> value=, name=0x7fffc8aba09b "description", ns=0x0,
> node=0x7fff681faa30) at ../../tree.c:1940
> #3  xmlNewProp__internal_alias (node=node@entry=0x7fff681faa30,
> name=name@entry=0x7fffc8aba09b "description", value=)
> at ../../tree.c:1939
> #4  0x7fffc8ab5c86 in xml_make_doc (
> consumer=consumer@entry=0x7fff681e4b20,
> service=service@entry=0x7fff681e4a80) at consumer_xml.c:760
> #5  0x7fffc8ab611a in output_xml
> (consumer=consumer@entry=0x7fff681e4b20)
> at consumer_xml.c:842
> #6  0x7fffc8ab62d0 in consumer_start (consumer=0x7fff681e4b20)
> at consumer_xml.c:898
> #7  0x766e8536 in mlt_consumer_start (self=0x7fff681e4b20)
> at mlt_consumer.c:599
> #8  0x764b811c in Mlt::Consumer::run (this=0x7fff681e49d0)
> at MltConsumer.cpp:129
> #9  0x5565f78b in MeltJob::startJob (this=0x5cccdb40)
> at /build/kdenlive-16.04.1/src/project/jobs/meltjob.cpp:218
> #10 0x556662cf in JobManager::slotProcessJobs (this=0x58746f50)
> at /build/kdenlive-16.04.1/src/project/jobs/jobmanager.cpp:191
> #11 0x5563b33d in QtConcurrent::RunFunctionTask::run (
> this=0x5cd2cb00)
> at
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:130
> #12 0x707e2303 in QThreadPoolThread::run (this=0x7fffac08cfc0)
> at thread/qthreadpool.cpp:93
> #13 0x707e580e in QThreadPrivate::start (arg=0x7fffac08cfc0)
> at thread/qthread_unix.cpp:331
> #14 0x7fffec7bb454 in start_thread (arg=0x7fffa67fb700)
> at pthread_create.c:334
> #15 0x7fffefbf0e5d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
>
>
> Note: In place of 0x703532 in the backtrace above, have also gotten
> various other addresses, including 0x513c70614d512c67 and 0x30.
>
>
> Error 2: Arithmetic exception in MltVideoProfile::isCompatible (Kdenlive)
>
> Program received signal SIGFPE, Arithmetic exception.
> [Switching to Thread 0x7fffba697700 (LWP 12840)]
> 0x55947fe5 in MltVideoProfile::isCompatible (
> this=this@entry=0x7fffba696af0, point=...)
> at /build/kdenlive-16.04.1/src/definitions.cpp:115
> 115 /build/kdenlive-16.04.1/src/definitions.cpp: No such file or
> directory.
> (gdb) bt
> #0  0x55947fe5 in MltVideoProfile::isCompatible (
> this=this@entry=0x7fffba696af0, point=...)
> at /build/kdenlive-16.04.1/src/definitions.cpp:115
> #1  0x55908ce1 in ProducerQueue::processFileProperties (
> this=)
> at /build/kdenlive-16.04.1/src/mltcontroller/producerqueue.cpp:237
> #2  0x5563b33d in QtConcurrent::RunFunctionTask::run (
> this=0x5cca5b80)
> at
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:130
> #3  0x707e2303 in QThreadPoolThread::run (this=0x57178180)
> at thread/qthreadpool.cpp:93
> #4  0x707e580e in QThreadPrivate::start (arg=0x57178180)
> at thread/qthread_unix.cpp:331
> #5  0x7fffec7bb454 in start_thread (arg=0x7fffba697700)
> at pthread_create.c:334
> #6  0x7fffefbf0e5d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
>
>
> What's interesting about this error is that a .mlt file is produced, but
> the  tag in it has corrupt values. A sample follows:
>
>
>  sample_aspect_num="1677751152" sample_aspect_den="956329573"
> display_aspect_num="235736320" display_aspect_den="37"
> frame_rate_num="37" frame_rate_den="0" colorspace="0"/>
>
>
> Trying to import this into a new project results in the same arithmetic
> exception.
>
> Error 3: Segmentation fault in mlt_profile_fps (libmlt)
>
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff89ff9700 (LWP 13146)]
> 0x766eccad in mlt_profile_fps (profile=0x73746e6576655f)
> at mlt_pr

Bug#827168: numpy: Please make numpy.i 'visible'

[Alastair McKinstry]

Package: numpy
Severity: normal

Several packaegs within Debian (including two I maintain, grib-api and 
magics++) ship their own
obsolete copies of numpy.i, the SWIG wrappers for numpy. This leads to bugs, as 
they are out of date,
lacking python3 support, etc.

Please ship as e.g. /usr/share/swig/numpy.i so that the canonical version can 
be used elswehere.

Thanks
Alastair McKinstry


-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#827167: Version 0.6.* not supported anymore

[Marian Sigler]

Package: duplicity
Tags: security

I wonder what debian is going to do on this?


 Forwarded Message 
Subject:[Duplicity-announce] 0.6 Series Support EOL
Date:   Sun, 12 Jun 2016 13:03:45 -0500
From:   Kenneth Loafman 
Reply-To:   Announcements about duplcity backup

To: Discussion of the backup program duplicity
, duplicity-t...@lists.launchpad.net,
duplicity-annou...@nongnu.org



Hi,

This is to announce that the 0.6 series has reached End-Of-Life.  No
further updates or upgrades will be made to it.  The long term support
folks can easily upgrade to the tarball version
, the Daily PPA
, or the
Stable PPA ,
depending on their needs.

The 0.7 series will continue while we work on 0.8 with an eye to ever
larger backups and split signature files.

We would love to work with the distros to figure out how to assist in
their long term support needs, but currently we are at odds with how
development is done. We do not have time to maintain dozens of different
versions dependent on the vagaries of each of the distros, while at the
same time adding new features.  Heck, we don't even have the time to
maintain the half-dozen or so versions that Ubuntu would need.  So,
progress will be made, but if you want or need to stick with the
distribution repository for whatever reason, we'll try to help, but the
most common response will be to upgrade to one of the above.

...Thanks,
...Ken

Bug#827025: kde-l10n-de dependency problem with plasma-desktop 5.6.4-2

[Hans]

Hi,
I discovered, that the removal of kde-l10n-de by the package manager also 
effected packages, which got their own *-l10n-de. 

For example libreoffice and firefox-esr now are also in English. I guess, that 
the removal of kde-l10n-de switched something internally of in kde, so that 
the other applications are now in English, too.

Of course I do not want to delete the whole ~/.kde folder, so it would be 
nice, if you could point me, where I should look at for a workaround or a fix 
for the time, this bug is unfixed. 

Thank you for any help!

Best regards

Hans

Bug#827165: qct: FTBFS:

[Vincent Danjean]

Control: tag -1 help

  Hi,

  Thanks for the notice.

  That said, qct is dead upstream since 2011 and have numerous
replacements in Debian. So, unless someone step in, I plan to
let the package be removed from testing, and then I will ask
FTP team to remove it from unstable.

  If someone want to become upstream (or, at least, maintainer),
please, say so.

  Regards,
Vincent


Le 13/06/2016 à 10:33, Chris Lamb a écrit :
> Source: qct
> Version: 1.7-3
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> qct fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   Setting up libqtcore4:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-xml:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqtdbus4:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up qtchooser (58-gfab25f1-1) ...
>   Setting up qdbus (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-dbus:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-network:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-script:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-sql:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libpng16-16:amd64 (1.6.22-1) ...
>   Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
>   Setting up ucf (3.0036) ...
>   Setting up fonts-dejavu-core (2.35-1) ...
>   Setting up fontconfig-config (2.11.0-6.4) ...
>   Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
>   Setting up fontconfig (2.11.0-6.4) ...
>   Regenerating fonts cache... done.
>   Setting up libxau6:amd64 (1:1.0.8-1) ...
>   Setting up x11-common (1:7.7+15) ...
>   update-rc.d: warning: start and stop actions are no longer supported; 
> falling back to defaults
>   invoke-rc.d: could not determine current runlevel
>   invoke-rc.d: policy-rc.d denied execution of start.
>   Setting up libice6:amd64 (2:1.0.9-1+b1) ...
>   Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
>   Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
>   Setting up libxcb1:amd64 (1.11.1-1) ...
>   Setting up libx11-data (2:1.6.3-1) ...
>   Setting up libx11-6:amd64 (2:1.6.3-1) ...
>   Setting up libxt6:amd64 (1:1.1.5-1) ...
>   Setting up libaudio2:amd64 (1.9.4-4) ...
>   Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
>   Setting up liblcms2-2:amd64 (2.7-1) ...
>   Setting up libmng1:amd64 (1.0.10+dfsg-3.1+b3) ...
>   Setting up libjbig0:amd64 (2.1-3.1) ...
>   Setting up libtiff5:amd64 (4.0.6-1) ...
>   Setting up libxext6:amd64 (2:1.3.3-1) ...
>   Setting up libxrender1:amd64 (1:0.9.9-2) ...
>   Setting up libqtgui4:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-declarative:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-designer:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-help:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-scripttools:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-svg:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqt4-test:amd64 (4:4.8.7+dfsg-8) ...
>   Setting up libqtassistantclient4:amd64 (4.6.3-7) ...
>   Setting up python-sip (4.18+dfsg-1) ...
>   Setting up python-qt4 (4.11.4+dfsg-2) ...
>   Setting up pyqt4-dev-tools (4.11.4+dfsg-2) ...
>   Setting up sgml-base (1.27) ...
>   Setting up xml-core (0.13+nmu2) ...
>   Setting up libxml2-utils (2.9.3+dfsg1-1.2) ...
>   Setting up libxslt1.1:amd64 (1.1.28-4) ...
>   Setting up xsltproc (1.1.28-4) ...
>   Setting up asciidoc (8.6.9-3) ...
>   Processing triggers for sgml-base (1.27) ...
>   Setting up sgml-data (2.0.10) ...
>   Setting up docbook-xsl (1.79.1+dfsg-1) ...
>   Processing triggers for sgml-base (1.27) ...
>   Setting up docbook-xml (4.5-7.3) ...
>   Processing triggers for sgml-base (1.27) ...
>   Setting up xmlto (0.0.28-0.1) ...
>   Setting up qct-build-deps (1.7-3) ...
>   Processing triggers for libc-bin (2.22-11) ...
>   Processing triggers for systemd (230-2) ...
>   
>   
> **
>   ** Environment  
> **
>   
> **
>   
>   
> PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>   HOSTNAME=e841f348cd14
>   TERM=xterm
>   PAGER=more
>   DISPLAY=:0
>   DOCKER_IMAGE=lamby-debian-sid
>   DEB_BUILD_OPTIONS=parallel=9
>   PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
>   HOME=/home/lamby
>   LOGNAME=lamby
>   SHLVL=1
>   PWD=/home/lamby/temp/cdt.20160613093157.saEWe2Ad2h.qct/qct-1.7
>   OLDPWD=/home/lamby/temp/cdt.20160613093157.saEWe2Ad2h.qct
>   GPG_TTY=/dev/console
>   QUILT_PATCHES=debian/patches
>   QUILT_NO_DIFF_INDEX=1
>   QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
>   DEBEMAIL=la...@debian.org
>   DEBFULLNAME=Chris Lamb
>   EDITOR=vim
>   LESS=-cgiFx4M
>   BLASTER=A220 I5 D1 H5 P330 T6
>   _=/usr/bin/env
>   
>   

Bug#827169: RFA: qct

[Vincent Danjean]

Package: wnpp
Severity: normal

  Currently, qct FTBFS (see #827165).

  qct is dead upstream since 2011 and have numerous
replacements in Debian. So, unless someone step in, I plan to
let the package be removed from testing, and then I will ask
FTP team to remove it from unstable.

  Regards,
Vincent

Bug#825642: libreoffice-gtk: Missing file qstart.desktop

[Rene Engelhard]

reopen 825642
retitle 825642 please re-enable Quickstarter
severity 825642 wishlist
thanks

Hi,

On Sun, Jun 12, 2016 at 07:01:05PM +0200, Reto Schoch wrote:
>I don't think it's appropriate to only consider GNOME3 as an uptodate
>desktop. And given that, for other desktops (e.g. XFCE) it's not only a

True. But it's a prominent one and the one which is/was default in a Debian
desktop install.

And KDE people (often) don't like installing Gtk-specific applications, even
if it would work (didn't try)

Didn't try Cinammon and MATE either.

>matter of speed, but also a matter of comfort (direct access to LO from
>the panel).

You could not add own stuff in the panel? But yeah, that's a argument.

>Beside, if this bug didn't occure in LO, there would have not
>been any occasion to disable it. 

Except it being unneeded and unmaintained upstream and the display issue(s)
in (some) DEs

>So, why not leave Quickstarter enabled as
>long as libreoffice-gtk is around. The necessary steps on the part of LO
>have been done. I don't see anything sensibly speaking against.

Because it's not necessary?

Because it's not maintained upstream and a big part of upstream also wants
to see it go away?

Because -gtk will be -gtk2 (starting from 5.2.0 which will be in sid in August)
to actually show it's for a old Gtk version in stretch so -gtk will not be not
around anymore anyway ;-)
And both MATE and Cinammon now also use Gtk3, leaving Xfce alone "needing" Gtk2.

(In any case, the fix is not in 4.1.4 rc2 yet and not in 5.2.0 beta2 so it'll
only be enabled in a few weeks anyway (given 5.1.x is almost dead and will not
be what stretch is shipping I am not going to "waste time" by backporting
"minor" fixes like this to it. So if it was being re-enabled not now but
later. I am not yet convinced, though.)

But let's reopen this (and retitling to have a sensible title) as it's a valid
wish after all..

Regards,

Rene

Bug#801102: Fix for security issue in audiofile (CVE-2015-7747)?

[Petter Reinholdtsen]

Hi.  You get this email as author of the audiofile package. Are you
aware of the security issue reported in Debian for audiofile, see the
CVE entry on top of https://bugs.debian.org/src:audiofile >.  Is
there a fix available?  Is the same issue reported in other bug trackers
you are aware of?  Are there plans for a new release?

-- 
Happy hacking
Petter Reinholdtsen

Bug#811417: apt-dater reports an error for servers with multi-line issue.net

[Thomas Liske]

severity 811417 normal
tags 811417 wontfix
thanks

Re,

On Sun, Jun 12, 2016 at 11:13:38PM +0200, Alexander Schier wrote:
> Am 12.06.2016 um 21:30 schrieb Thomas Liske:
> 
> > Does your issue.net contain the words 'error', 'warning' or 'failed'
> > (case insensitive)?
> Yes, it does. It has some legal notice, that access is logged in there,
> which starts with "WARNING".

so this triggers the error detection.


> Maybe apt-dater just should supress the issue.net, like using "ssh -q"?

It seems to depend on the OpenSSH version if -q or -qq is
required. Since it might suppress other useful messages I do not like
to add -q(q) by default.

As a workaround you could:
- add '-q' to /apt-dater/ssh/@opt-cmd in apt-dater.xml
- disable or tune the err-pattern regex (i.e. with a negative look
  ahead)


HTH,
Thomas

> See
> http://serverfault.com/q/66986
> 
-- 
supp...@ibh.de  Tel. +49 351 477 77 30
www.ibh.de  Fax  +49 351 477 77 39

---
Dipl.-Ing. Thomas Liske
Teamleiter DataCenter Services


IBH IT-Service GmbH Amtsgericht Dresden
Gostritzer Str. 67a HRB 13626
D-01217 Dresden GF: Prof. Dr. Thomas Horn
Germany VAT DE182302907
---
Ihr Partner für: LAN, WAN IP-Quality, Security, VoIP, SAN, Backup, USV
---
   professioneller IT-Service - kompetent und zuverlässig
---

Bug#827170: xul-ext-foxyproxy-standard: Please don't integrate into icedove

[Uwe Kleine-König]

Package: xul-ext-foxyproxy-standard
Severity: normal

Hello,

since icedove 1:45.1.0-1 icedove conflicts with
xul-ext-foxyproxy-standard (>> 3.4-1) to work around
http://bugs.debian.org/820026.

As I want to use foxyproxy in firefox and I also use icedove (without
need for foxyproxy) it would be great if foxyproxy just would not try to
integrate into icedove/thunderbird.

I'm not into packaging xul extentions but I imagine that it is easy for
foxyproxy to not claim to be compatible with icedove which then would
allow (after the Breaks: is dropped) to install both packages again.
It would still be better if this could be done on icedove's side, but I
think that's not that easy.

Thanks
Uwe

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

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

Bug#827018: xserver-xorg-input-all: Don't depend on x-x-input-synaptics

[Julien Cristau]

On Sat, Jun 11, 2016 at 11:35:48 +0200, Nicolas LE CAM wrote:

> Package: xserver-xorg-input-all
> Version: 1:7.7+15
> Severity: important
> 
> Dear Maintainer,
> 
> As of x-x-input-synaptics 1.8.3-2, my touchpad (on an Asus UX303) has become 
> a basic mouse (previously tapping, scrolling etc were working) and I can't 
> revert back as task-desktop depends on x-x-input-all, which depends on 
> x-x-input-synaptics.
> 
> This is due to a change in synaptics package to make it be used instead of 
> libinput if both are installed.
> The rationnal for that, as explained in the commit, is :
> "The synaptics driver is more of a leaf package than libinput (which covers a 
> multitude of device types) and can be removed by default. When specifically 
> installed by the user, the synaptics driver should override the system 
> default."
> 
> So IMHO synaptics shouldn't be installed by default.
> 
That would break all non-gnome environments.

Cheers,
Julien

Bug#827164: unable to start guest with ceph rbd disks

[uli iske]

> Control: tag -1 + moreinfo
> 
> 13.06.2016 11:15, uli iske wrote:
> > Package: qemu
> > Version: 2.6+dfsg-1+b1
> > 
> > When trying to start or migrate Guest with ceph rbd Disk image
> > connected I get the following error message:
> > 
> > internal error: process exited while connecting to monitor:
> > 2016-06-13T08:11:05.686421Z qemu-system-x86_64: -drive
> > file=rbd:rbd/sam:id=admin:auth_supported=cephx\;none:mon_host=10.210.0.5\:6789\;10.210.0.6\:6789\;10.210.0.88\:6789,password-secret=virtio-disk0-secret0,format=raw,if=none,id=drive-virtio-disk0,cache=none:
> > error connecting  
> 
> Please give complete qemu error message, not the interpretation
> given by libvirt.

Is there a log somewhere or do I have to start the guest with
qemu-system-x86_64 ?

> Also please ensure you have qemu-block-extra of the right version.

qemu-block-extra is of Version 2.6+dfsg-1+b1
 
> Thanks,
> 
> /mjt

Bug#823843: cinnamon-common: Touchpad setting "tap to click" stopped working

[Julien Cristau]

On Sat, Jun 11, 2016 at 19:19:09 -0400, Jeremy Bicha wrote:

> Version: 1.8.3-2

This is not how you close bugs.

Cheers,
Julien

Bug#825840: Update(s)

[Mathieu Malaterre]

So if I understand correctly since https://bugs.debian.org/748398
radeonfb is now a module. What this means is that now instead of
radeonfb taking the lead over OFfb, currently OFfb setup /dev/fb0
first (build-in driver takes over modules??). It is then impossible to
load radeonfb since it lack something like:

https://lists.freedesktop.org/archives/dri-devel/2010-August/002907.html

Some historical references:

https://bugs.debian.org/614221#86

What's still not clear is order OFfb / radeonfb / radeon since they
all can support my card.

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Luca Boccassi]

Control: forcemerge 814347 827161

On Mon, 2016-06-13 at 10:28 +0300, Bogdan Vatra wrote:
> Package: nvidia-driver
> Version: 352.79-8
> Severity: normal
> 
> --- Please enter the report below this line. ---
> 
> Hello,
> 
> NVIDIA 364.12 is coming with lots of (quite desired) features:
> - updated Vulkan support
> - mir & wayland support (Finally !)
> 
> Is there any plans to have it soon as an official debian package?
> 
> Thank you!
> 
> Yours,
> BogDan.

Hi,

It's all packaged in SVN but waiting for approval in NEW queue, we
cannot upload until it clears.  You can build locally if you want to try
the new versions. See:

https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012918.html
https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012919.html
https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-May/013028.html

Kind regards,
Luca Boccassi


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

Bug#827164: unable to start guest with ceph rbd disks

[Michael Tokarev]

13.06.2016 12:31, uli iske wrote:

>> Please give complete qemu error message, not the interpretation
>> given by libvirt.
> 
> Is there a log somewhere or do I have to start the guest with
> qemu-system-x86_64 ?

I don't know libvirt enough to be able to answer this question, sorry.

Thanks,

/mjt

Bug#827025: kde-l10n-de dependency problem with plasma-desktop 5.6.4-2

[Hans]

On Monday 13 June 2016 11:01:56 Hans wrote:
Answerinhg myself
>Hi,
>I discovered, that the removal of kde-l10n-de by the package manager also 
> effected packages, which got their own *-l10n-de. 

> For example libreoffice and firefox-esr now are also in English. I guess, 
> that 
> the removal of kde-l10n-de switched something internally of in kde, so that 
> the other applications are now in English, too.

I found out, that due to the removal of kde-l10n-de the following packages 
were altered:

~/.config/kdeglobals
~/.config/plasma-locale-settings.sh
~/.config/plasma-localerc

All files lost either the entry of en_US and changed the German locale from 
the correct de_DE@euro to nds_de_DE. 

If you manually correct these to your own language, most non-kde applications 
are again in your preferred language (of course the necessary *-l10n-de 
packages have to be installed).

Hope this helps a little bit.

Happy hacking.

Hans

 

Bug#827119: AttributeError: 'Namespace' object has no attribute 'action'

[Enrico Rossi]

Package: debtags
Version: 2.1
Severity: minor

Dear Alexander,

I confirm the bug. It a minor bug. It should print the short usage help.
It is also an already reported bug for the v.2.0.

Thanks for reporting.
E.

-- 
GPG Key: 4096R/F2133176 2010-10-19 Enrico Rossi 

Bug#827171: [uptime] show container uptime

[Daniel Baumann]

Package: procps
Version: 2:3.3.11-3

Hi Craig,

when using 'uptime' in containers (regardless what kind of containers), 
it shows the uptime of the host system rather than the one of the container.


What we used locally here is to look at /dev/pts:

DATE_CONTAINER="$(stat -c %z /dev/pts)"
DATE_CONTAINER="$(date +%s -d"${DATE_CONTAINER}")"

UPTIME_CONTAINER="$((${DATE_HOST} - ${DATE_CONTAINER}))"

and then go on with that and calculate the uptime days/hours/minutes etc.

It would be nice if uptime could do something about this in order to be 
more container friendly.


Regards,
Daniel

Bug#827133: aptitude cannot find changelogs of source packages

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi,

2016-06-12 19:50 Emmanouil Maroudas:

Package: aptitude
Version: 0.8.1-1
Severity: normal
Tags: patch

Hello,

The changelog command line fails to fetch the changelog file from source
packages.

Example:
   $ aptitude changelog glibc
   Get: Changelog of glibc
   E: Couldn't find a changelog for glibc

After applying the attached patch:

   $ aptitude changelog glibc
   Get: Changelog of glibc
   # opens the pager as expected


Thanks for the patch, applied.

Good catch, I think that it's been like that since the inception of the
code in 2008.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#827025: kde-l10n-de dependency problem with plasma-desktop 5.6.4-2

[Martin Steigerwald]

On Montag, 13. Juni 2016 11:57:33 CEST Hans wrote:
> On Monday 13 June 2016 11:01:56 Hans wrote:
> Answerinhg myself
> 
> >Hi,
> >I discovered, that the removal of kde-l10n-de by the package manager also
> >
> > effected packages, which got their own *-l10n-de.
> > 
> > For example libreoffice and firefox-esr now are also in English. I guess,
> > that the removal of kde-l10n-de switched something internally of in kde,
> > so that the other applications are now in English, too.
> 
> I found out, that due to the removal of kde-l10n-de the following packages
> were altered:
> 
> ~/.config/kdeglobals
> ~/.config/plasma-locale-settings.sh
> ~/.config/plasma-localerc
> 
> All files lost either the entry of en_US and changed the German locale from
> the correct de_DE@euro to nds_de_DE.
> 
> If you manually correct these to your own language, most non-kde
> applications are again in your preferred language (of course the necessary
> *-l10n-de packages have to be installed).

I recommend using

dpkg-reconfigure locales

to set the system locale. Select "de_DE.UTF-8" there unless you are not using 
UTF-8.

I do not have any issues with LibreOffice or Firefox being in english here. 
All still in german.

But this is a user support question, please use debian-user-german or debian-
kde mailinglists for that.

Thank you,
-- 
Martin

Bug#781449: marked as pending

[Martin Steigerwald]

On Montag, 13. Juni 2016 02:14:26 CEST you wrote:
> tag 781449 pending
> thanks
> 
> Hello,

Hello Craig,

> Bug #781449 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
> 
>
> http://git.debian.org/?p=collab-maint/wordpress.git;a=commitdiff;h=aeefbd4

Thank you for addressing this.

Looks good.

Even better if you add the plugin to disable google fonts to the package. But 
it doesn´t seem to be updated often, so…

… another alternative would be to provide at least one theme that doesn´t use 
public cdns. But well, both ideas might be for different reports, as your 
warning sufficiently addresses this bug IMHO.

Thanks,
Martin

> ---
> commit aeefbd43e6eb38fde8c3b6f5b8bf040b151f959f
> Author: Craig Small 
> Date:   Mon Jun 13 12:13:33 2016 +1000
> 
> Add warning about googleapi external resource
> 
> The default themes use googleapis CSS and fonts.
> Could be a problem, or not. See #781449
> 
> diff --git a/debian/changelog b/debian/changelog
> index 64c15c3..5a42698 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -2,6 +2,8 @@ wordpress (4.5.2+dfsg-2) UNRELEASED; urgency=medium
> 
>* Updated language files Closes: #772498
>* Add alias to nginx example configuration
> +  * Add warning in description and README about googleapis
> +Closes: #781449
> 
>   -- Craig Small   Mon, 13 Jun 2016 11:45:45 +1000


-- 
Martin

Bug#826788: fsck run before unmounting?; failed unmounting /home.

[積丹尼 Dan Jacobson]

The problem doesn't happen on every shutdown, but most. So maybe there
is a race condition involved.

Bug#780205: patch - fix crash with long one-line XML documents

[Vlad Orlov]

affects 780205 mousepad
thanks


Hi,

So, starting from version 1.14, MATE is built with GTK+3 in Testing and 
Unstable,
which is probably good news for you. :)

However, this bug still affects Pluma in Jessie as MATE is built with GTK+2 
there.

Moreover, I found out it affects another editor, mousepad (which is commonly 
used
in Xfce). It might take a few more text deletions than in Pluma, but eventually
it crashes in the same place as Pluma, as it can be seen in the backtrace [1].
And the patch fixes mousepad crash for good.

So please consider applying the patch in Jessie.


[1] http://pastebin.com/2ijSnZsC

Bug#827172: reaver: please make the build reproducible (fileordering)

[Alexis Bienvenüe]

Source: reaver
Version: 1.4-2
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

While working on the "reproducible builds" effort [1], we have noticed
that 'reaver' could not be built reproducibly.

The attached patch fixes the order in which object files are passed to
gcc. Once applied, reaver can be built reproducibly in our current
experimental framework.

Regards,
Alexis Bienvenüe.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Description: Order object files when linking
 Sort object files when liking, to make the build reproducible.
Author: Alexis Bienvenüe 

Index: reaver-1.4/src/Makefile.in
===
--- reaver-1.4.orig/src/Makefile.in
+++ reaver-1.4/src/Makefile.in
@@ -5,15 +5,15 @@ prefix=@prefix@
 exec_prefix=@exec_prefix@
 CONFDIR=@sysconfdir@/@target@
 CFLAGS=-DCONF_DIR='"$(CONFDIR)"' -DREAVER_DATABASE='"$(CONFDIR)/reaver.db"' @CFLAGS@
-LDFLAGS=$(LIBWPS_DIR)/*.o wps/*.o tls/bignum.o tls/libtls.a utils/libutils.a crypto/libcrypto.a lwe/libiw.a @LDFLAGS@
+LDFLAGS=`LC_ALL=C ls $(LIBWPS_DIR)/*.o wps/*.o` tls/bignum.o tls/libtls.a utils/libutils.a crypto/libcrypto.a lwe/libiw.a @LDFLAGS@
 
 all: wash reaver
 
 wash: wps libiw libwps.o argsparser.o globule.o init.o misc.o 80211.o iface.o
-	$(CC) $(CFLAGS) $(INC) wpsmon.c *.o $(LDFLAGS) -o wash
+	$(CC) $(CFLAGS) $(INC) wpsmon.c `LC_ALL=C ls *.o` $(LDFLAGS) -o wash
 
 reaver: wps libiw libwps.o argsparser.o globule.o init.o sigint.o sigalrm.o misc.o cracker.o
-	$(CC) $(CFLAGS) $(INC) wpscrack.c *.o $(LDFLAGS) -o reaver
+	$(CC) $(CFLAGS) $(INC) wpscrack.c `LC_ALL=C ls *.o` $(LDFLAGS) -o reaver
 
 libwps.o:
 	(cd $(LIBWPS_DIR) && make)

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Luca Boccassi]

On Mon, 2016-06-13 at 13:29 +0300, Bogdan Vatra wrote:
> On Monday 13 June 2016 10:53:00 Luca Boccassi wrote:
> > Control: forcemerge 814347 827161
> > 
> > On Mon, 2016-06-13 at 10:28 +0300, Bogdan Vatra wrote:
> > > Package: nvidia-driver
> > > Version: 352.79-8
> > > Severity: normal
> > > 
> > > --- Please enter the report below this line. ---
> > > 
> > > Hello,
> > > 
> > > NVIDIA 364.12 is coming with lots of (quite desired) features:
> > > - updated Vulkan support
> > > - mir & wayland support (Finally !)
> > > 
> > > Is there any plans to have it soon as an official debian package?
> > > 
> > > Thank you!
> > > 
> > > Yours,
> > > BogDan.
> > 
> > Hi,
> > 
> > It's all packaged in SVN but waiting for approval in NEW queue, we
> > cannot upload until it clears.  You can build locally if you want to try
> > the new versions. See:
> > 
> > https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012918
> > .html
> > https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/01291
> > 9.html
> > https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-May/013028.
> > html
> > 
> > Kind regards,
> > Luca Boccassi
> 
> Hi,
> 
> Is there any tutorial how to build it from svn?
> 
> Thanks!
> 
> Yours,
> BogDan.

https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012917.html

Kind regards,
Luca Boccassi


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

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Bogdan Vatra]

On Monday 13 June 2016 10:53:00 Luca Boccassi wrote:
> Control: forcemerge 814347 827161
> 
> On Mon, 2016-06-13 at 10:28 +0300, Bogdan Vatra wrote:
> > Package: nvidia-driver
> > Version: 352.79-8
> > Severity: normal
> > 
> > --- Please enter the report below this line. ---
> > 
> > Hello,
> > 
> > NVIDIA 364.12 is coming with lots of (quite desired) features:
> > - updated Vulkan support
> > - mir & wayland support (Finally !)
> > 
> > Is there any plans to have it soon as an official debian package?
> > 
> > Thank you!
> > 
> > Yours,
> > BogDan.
> 
> Hi,
> 
> It's all packaged in SVN but waiting for approval in NEW queue, we
> cannot upload until it clears.  You can build locally if you want to try
> the new versions. See:
> 
> https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012918
> .html
> https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/01291
> 9.html
> https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-May/013028.
> html
> 
> Kind regards,
> Luca Boccassi

Hi,

Is there any tutorial how to build it from svn?

Thanks!

Yours,
BogDan.

smime.p7s
Description: S/MIME cryptographic signature

Bug#827173: gcc-6: missing "Debian" in "gcc-6 --version" output

[Vincent Lefevre]

Package: gcc-6
Version: 6.1.1-6
Severity: minor

$ gcc-6 --version
gcc-6 ( 6.1.1-6) 6.1.1 20160609
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The first line of the output should have been:

gcc-6 (Debian 6.1.1-6) 6.1.1 20160609

There was no such problem with gcc-6 6.1.1-5.

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

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

Versions of packages gcc-6 depends on:
ii  binutils  2.26-11
ii  cpp-6 6.1.1-6
ii  gcc-6-base6.1.1-6
ii  libc6 2.22-11
ii  libcc1-0  6.1.1-6
ii  libgcc-6-dev  6.1.1-6
ii  libgcc1   1:6.1.1-6
ii  libgmp10  2:6.1.0+dfsg-2
ii  libisl15  0.17.1-1
ii  libmpc3   1.0.3-1
ii  libmpfr4  3.1.4-2
ii  libstdc++66.1.1-6
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages gcc-6 recommends:
ii  libc6-dev  2.22-11

Versions of packages gcc-6 suggests:
ii  gcc-6-doc 6.1.0-1
ii  gcc-6-locales 6.1.1-6
ii  gcc-6-multilib6.1.1-6
pn  libasan3-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information

Bug#827171: works on vserver but not lxc

[Adam Borowski]

> when using 'uptime' in containers (regardless what kind of containers), 
> it shows the uptime of the host system rather than the one of the container.

It _does_ work on vserver but not on lxc (and similar).

'uptime' is just a pretty-printer for /proc/uptime, you'd need to teach the
kernel what a "container" means.  And here's a problem: unlike vserver where
containers are an in-kernel thing, lxc is merely a wrapper for
chroot+cgroups+unshare.  You can mix and match those yourself -- which
raises the question when two processes stop being in the same "container".
When their root filesystem differs?  When they're in different namespaces --
but which namespace?

I think the best approximation is the PID namespace -- ie, defining
containers as "having separate inits".  But when did the current init start?
There _is_ task->real_start_time, ie, field 22 of /proc/1/stat, but it
changes whenever init is exec()ed.  What we'd want is the time when unshare
was called, and I don't think that's stored anywhere.

Thus, unless someone has a better idea, all we can get in modern containers
is "time since init was started/upgraded".


Meow!
-- 
An imaginary friend squared is a real enemy.

Bug#827174: xul-ext-https-finder is broken

[Jakub Wilk]

Package: xul-ext-https-finder
Version: 091-1
Severity: grave

HTTPS Finder does not seem to find any HTTPS pages.
To reproduce, go to . This site has a valid HTTPS 
version, but HTTPS Finder doesn't find it.



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

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

Versions of packages xul-ext-https-finder depends on:
ii  iceweasel  45.2.0esr-1

--
Jakub Wilk

Bug#824566: thanks for the patch

[Ritesh Raj Sarraf]

Control: tag -1 confirmed


Thank you for the patch. I am the current maintainer for LIO in Debian. For
reasons I don't know, I never received this bug report, which makes me wonder if
there are more such bugs reported.


I verified your fix and will apply it for Stretch.
I have opened a bug with Datera too.
https://github.com/Datera/rtslib/issues/13


Thanks,
Ritesh


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Bug#825968: epydoc: nondeterminism caused by list and file ordering

[Sascha Steinbiss]

Hi Ken,

> Sorry for the late reply; I've been traveling.
> I'll work to apply these patches sometime soon -- hopefully within the
> next week.  I do track the reproducible status for this package, so
> this is a high priority for me.

Thanks a lot for this. There might be some extra patches coming later;
I'm looking at each package that seems to be non-reproducible due to
epydoc and try to determine whether it's something to be fixed in epydoc
itself or specific to that package.

Cheers
Sascha


-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Andreas Beckmann]

On 2016-06-13 12:36, Luca Boccassi wrote:
>> Is there any tutorial how to build it from svn?

> https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012917.html

And the easier way to build the .orig.tar.gz:

debian/rules get-orig-source


Luca, maybe we should have a section about this in the wiki?


Andreas

Bug#824566: thanks for the patch

[Ritesh Raj Sarraf]

Now having looked at the Tracker (and explicitly subscribing to my packages), I
see that LIO is marked for removal because of another bug, https://bugs.debian.o
rg/cgi-bin/bugreport.cgi?bug=824738


This one is a plain FTBFS of the simpleparse package. There's no update on that
bug report, hence asking here.


On Mon, 2016-06-13 at 16:31 +0530, Ritesh Raj Sarraf wrote:
> Control: tag -1 confirmed
> 
> 
> Thank you for the patch. I am the current maintainer for LIO in Debian. For
> reasons I don't know, I never received this bug report, which makes me wonder
> if
> there are more such bugs reported.
> 
> 
> I verified your fix and will apply it for Stretch.
> I have opened a bug with Datera too.
> https://github.com/Datera/rtslib/issues/13
> 
> 
> Thanks,
> Ritesh
> 
> 
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Bug#826167: Compilation with different lua implémentations

[Christos Trochalakis]

On Thu, Jun 02, 2016 at 06:31:57PM +0200, Frederic Pauget wrote:

Package: nginx-extras
Version: 1.6.2-5+deb8u2
Severity: normal

Hi,

With the last security update the nginx binary is linked to liblua5.1.so.0, in 
the previous version (1.6.2-5+deb8u1 and stable release) it is linked to 
libluajit-5.1.so.2

It can be a problem if some specific extensions of luajit are used (like ffi).

I've changed my lua code in order to not use ffi anymore but I think it can be 
a problem for some users. So I prefer to report it.

Best regards.


There was a problem with the build environment that the package was
build. This is taken care of  in 1.6.2-5+deb8u2+b1 (binnmu).

Sorry for the inconvenience.

Bug#796625: [PATCH] clvm: ship native systemd units in debian package

[Andreas Henriksson]

Control: tags -1 + patch

Hello!

The attached patch updates the packaging to ship (modified versions of)
the upstream/redhat native systemd units in the clvm package.
I don't have possibility to test this myself, so hopefully this is
good enough result. I've compared checks in the init script but
they seem pretty obsolete. eg. the check for /etc/cluster/cluster.conf
which the lvm2 sources doesn't have any references to (anymore?).
Given this I opted to NOT enable/start the new
lvm2-cluster-activation.service by default. This creates a problem
on upgrades where people will manually need to enable it, thus
I also added a debian/NEWS entry to mention that.

In essence, clvm init script is masked replaced by two new services:
lvm2-cluster-activation.service and lvm2-clvmd.service
The lvm2-clvmd.service is not something you can manually handle at all
so all admin tasks should be against lvm2-cluster-activation.service
(which will start/stop lvm2-clvmd.service).

Hope this helps. Would be much appreciated if we could resolve this
bug report (very) soon. I'd like to avoid NMUing this package but
if progress is blocked on this bug report I'll go ahead if there's
no feedback by then.

Ulf Norberg it would be very appreciated if you could test building
a package with the patch attached and report back on status.

Regards,
Andreas Henriksson
diff -Nru lvm2-2.02.153/debian/changelog lvm2-2.02.153/debian/changelog
--- lvm2-2.02.153/debian/changelog  2016-05-09 16:45:32.0 +0200
+++ lvm2-2.02.153/debian/changelog  2016-06-13 13:16:07.0 +0200
@@ -1,3 +1,25 @@
+lvm2 (2.02.153-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+- This upload is targeted at and below changes closes: #796625
+  * Add debian/patches/clvm-systemd-unit-debian-adaptions.patch
+- this among other things makes lvm2-cluster-activation.service
+  take the LVM_VGS from /etc/default/clvm into consideration, but
+  ignores other things like CLVMDTIMEOUT from the same file.
+  Use systemctl edit lvm2-cluster-activation.service to override
+  settings instead of the /etc/default/clvm file which should be
+  considered deprecated under systemd.
+  See patch header for more details.
+  * Add debian/clvm.links masking clvm init script under systemd
+in favour of lvm2-{clvmd,cluster-activation}.service
+  * debian/rules: use systemd dh tools on lvm2-cluster-activation.service
+- no start on installation. Use systemctl enable lvm2-cluster-activation
+  once the cluster has been configured!
+  * debian/NEWS: Add a note about enabling lvm2-cluster-activation.service
+for people upgrading from previous versions.
+
+ -- Andreas Henriksson   Fri, 10 Jun 2016 17:06:54 +0200
+
 lvm2 (2.02.153-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru lvm2-2.02.153/debian/clvm.links lvm2-2.02.153/debian/clvm.links
--- lvm2-2.02.153/debian/clvm.links 1970-01-01 01:00:00.0 +0100
+++ lvm2-2.02.153/debian/clvm.links 2016-06-10 17:07:30.0 +0200
@@ -0,0 +1 @@
+dev/null lib/systemd/system/clvm.service
diff -Nru lvm2-2.02.153/debian/NEWS lvm2-2.02.153/debian/NEWS
--- lvm2-2.02.153/debian/NEWS   1970-01-01 01:00:00.0 +0100
+++ lvm2-2.02.153/debian/NEWS   2016-06-13 13:11:39.0 +0200
@@ -0,0 +1,9 @@
+lvm2 (2.02.153-1.1) UNRELEASED; urgency=medium
+
+  * This version introduces native systemd units to replace /etc/init.d/clvm
+Please note that "lvm2-cluster-activation.service" is NOT enabled by
+default as local system administrator will need to configure the
+cluster first. Use "systemctl enable lvm2-cluster-activation.service"
+to have clvm enabled under systemd. (The old clvm init script is masked.)
+
+ -- Andreas Henriksson   Mon, 13 Jun 2016 13:09:37 +0200
diff -Nru lvm2-2.02.153/debian/patches/clvm-systemd-unit-debian-adaptions.patch 
lvm2-2.02.153/debian/patches/clvm-systemd-unit-debian-adaptions.patch
--- lvm2-2.02.153/debian/patches/clvm-systemd-unit-debian-adaptions.patch   
1970-01-01 01:00:00.0 +0100
+++ lvm2-2.02.153/debian/patches/clvm-systemd-unit-debian-adaptions.patch   
2016-06-13 13:05:16.0 +0200
@@ -0,0 +1,54 @@
+From: Andreas Henriksson 
+Subject: Debian adaptions of upstream/redhat systemd units
+
+The following adaptions where made to make the upstream redhat-specific
+units work under Debian:
+ * Import environment file /etc/default/clvm instead of sysconfig/clvmd
+   - This makes LVM_VGS available to the activation script but ignores
+ the CLVMDTIMEOUT in /etc/default/clvm ... use systemctl edit
+ to override instead.
+   - replace dlm.service with cman.service in unit dependencies/ordering
+   - demote cman.service from Requires= to Wants= as it's only Recommends
+ (and not Depends) in the Debian package.
+   - use /usr/sbin/clvmd in unit file to match where upstream build system
+ and debian package ship the binary (note: using @usrsbindir@ instead
+ of @sbindir@ d

Bug#827164: unable to start guest with ceph rbd disks

[uli iske]

Hmm, looks like qemu is not guilty here.

Guest is starting and accessing the ceph disk with the following
command:

qemu-system-x86_64 -drive
file=rbd:rbd/sam:id=admin:key=mysecretcephkey==:auth_supported=cephx:mon_host=10.210.0.5,format=raw
-machine pc-i440fx-2.4,accel=kvm -enable-kvm -curses

no errors. 

Sorry for the noise.

Regards

Uli

> 13.06.2016 12:31, uli iske wrote:
> 
> >> Please give complete qemu error message, not the interpretation
> >> given by libvirt.  
> > 
> > Is there a log somewhere or do I have to start the guest with
> > qemu-system-x86_64 ?  
> 
> I don't know libvirt enough to be able to answer this question, sorry.
> 
> Thanks,
> 
> /mjt

Bug#827175: RM: cmip5-cmor-tables -- ROM; obsoleted by cmor-tables

[Alastair McKinstry]

Package: ftp.debian.org
Severity: normal

This package is obsoleted by the addition of cmor-tables which will provide 
cmip5-cmor-tables for stretch.

Bug#827149: RFS: triggerhappy/0.4.0-1

[Jakub Wilk]

Control: tags -1 + moreinfo

[I don't intend to sponsor this package.]

* Stefan Tomanek , 2016-06-12, 23:59:

https://mentors.debian.net/debian/pool/main/t/triggerhappy/triggerhappy_0.4.0-1.dsc


Bumping compat to 9 is not documented in the changelog.

Please double-check that all other changes are documented, too.

Your copyright file says "License: GPL-3", but it's "GPLv3 or any later 
version" according to upstream source.
Also, it's not enough to say "On Debian systems, the full text ..." in 
the License field. You need to actually quote the license statement, 
i.e. "You have permission to copy, modify, and redistribute ...".


Tagging this bug moreinfo, because the update would introduce an RC bug.

--
Jakub Wilk

Bug#827176: fpga-icestorm: Incorrect chipdb path in icetime

[whitequark]

Package: fpga-icestorm
Version: 0~20160218gitf2b2549-2
Severity: important

Dear Maintainer,

When running icetime, it tries to load supplementary chipdb information 
from
/usr/local/share/icebox/chipdb-*.txt. These files are actually located 
in the
package fpga-icestorm-chipdb at 
/usr/share/fpga-icestorm/chipdb/chipdb-*.txt.


I think that beyond fixing the path, also fpga-icestorm should have a 
hard
dependency on fpga-icestorm-chipdb, or perhaps icetime could be patched 
to

print an error message directing to install this package.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fpga-icestorm depends on:
ii  libc6   2.22-11
ii  libftdi10.20-4
ii  libgcc1 1:6.1.1-4
ii  libstdc++6  6.1.1-4
ii  python3 3.5.1-4

Versions of packages fpga-icestorm recommends:
ii  yosys  0.6-6

Versions of packages fpga-icestorm suggests:
ii  arachne-pnr   0.1+20151224git1a4fdf9-1
pn  fpga-icestorm-chipdb  

-- no debconf information

Bug#827177: transition: qtbase-opensource-src

[Lisandro Damián Nicanor Pérez Meyer]

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

Hi RT! After a long wait we pushing Qt 5 to unstable again.

It is worth to note that with this transition qtquick1-opensource-src
will no longer build and so we will ask for it's removal.

Affected packages are kadu, kadu-mime-tex and musescore:



Thanks in advance!

Ben file:

title = "qtbase-opensource-src";
is_affected = .depends ~ "qtbase-abi-5-5-1" | .depends ~ "qtbase-abi-5-6-1";
is_good = .depends ~ "qtbase-abi-5-6-1";
is_bad = .depends ~ "qtbase-abi-5-5-1";

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

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

Bug#824956: Raising severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 824956 serious
thanks

Hi! Qt 5.6.1 has been released and we are ready to push it to unstable.

Kinds regards, Lisandro.

-- 
Paris, Je suis impregnée de ta présence!!!
vous cette une fleche alée qui traspase mon cour
  muxbalsoc. Comment posted in
  http://youtube.com/watch?v=G3S_sOEjsmo

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


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

Bug#827178: virsh: Failed to create SASL client context: -7 (invalid parameter supplied)

[Martin Gebhardt]

Package: libvirt-clients
Version: 1.3.5-1
Severity: normal

Dear Maintainer,

I try to connect to a libvirt 1.2.17-13 instance running on CentOS 7. 
Since 1.3.5-1 I'm not able to connect to a 1.2.17-13 libvirtd using sasl 
authentication. With 1.3.3 it works as expected. 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 virsh -c qemu+tcp://kvm01/system sysinfo --

   * What was the outcome of this action?
 error: failed to connect to the hypervisor
 error: authentication failed: Failed to create SASL client context: -7 
(invalid parameter supplied)

I can reproduce this with same libvirt verion on Arch-Linux. Are you able to 
avoid/solve this problem? On CentOS 7, 1.2.17-13 ist the "latest" version.

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

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

Versions of packages libvirt-clients depends on:
ii  libapparmor12.10-4
ii  libaudit1   1:2.5.2-1
ii  libavahi-client30.6.32~rc+dfsg-1
ii  libavahi-common30.6.32~rc+dfsg-1
ii  libc6   2.22-11
ii  libcap-ng0  0.7.7-2
ii  libdbus-1-3 1.10.8-1
ii  libdevmapper1.02.1  2:1.02.124-1
ii  libgnutls30 3.4.13-1
ii  libnl-3-200 3.2.27-1
ii  libnl-route-3-200   3.2.27-1
ii  libnuma12.0.11-1
ii  libreadline66.3-8+b4
ii  libsasl2-2  2.1.26.dfsg1-15
ii  libselinux1 2.5-3
ii  libssh2-1   1.5.0-2.1
ii  libsystemd0 230-2
ii  libvirt01.3.5-1
ii  libxen-4.6  4.6.0-1+nmu2
ii  libxml2 2.9.3+dfsg1-1.2
ii  libyajl22.1.0-2

libvirt-clients recommends no packages.

Versions of packages libvirt-clients suggests:
ii  libvirt-daemon  1.3.5-1

-- no debconf information

Bug#617300: Hello Dear,

[Redmond Kojo]

Hello Dear,

I am still waiting for your Email response, you did receive my first
email to you

Respectfully Yours,

Mr Redmond Kojo(Esq)

Bug#826169: RFS: gpxsee/2.14 [ITP] -- GPX viewer and analyser

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

On Thu, Jun 02, 2016 at 06:12:12PM -0400, Martin Tůma wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Hi,
> I'm looking for a sponsor for the Debian GPXSee package
> 
> Package name: gpxsee
> Version : 2.14
> Upstream Author : Martin Tůma 
Even if you are the author you shouldn't make the package a native one.

> The project source code is hostad at GitHub:
> https://github.com/tumic0/GPXSee
> 
> And the DEB packages are built and available on OBS:
> https://build.opensuse.org/package/show/home:tumic:GPXSee/gpxsee
When asking for a review you should provide a source package, repferably
in a form usable by dget(1).

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#827089: RFS: dh-runit/0.1 ITP

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


>I am looking for a sponsor for my package "dh-runit"


while I did some work on runit package a while ago, I'm not sure about
how you want the packages to use your new shiny dh call?
how do you plan to notify them about it?
do you plan to open a lot of bugs for packages exposing a runit script?

I admit, I'm not a fan of too-many-init-systems-to-support, and runit
is not so far one of the most used...

but a debhelper script is always something appreciated that can simplify 
things...

another question: I see a lot of activity on git, so you need to freeze at some 
point, and
tag the "release", otherwise the sponsor won't know when you are ready to go.

bests,

Gianfranco

Bug#813949: bluetooth: error causing service to be unusable: Not enough free handles to register service

[Jakobus Schürz]

Package: bluez
Version: 5.36-1+b1
Followup-For: Bug #813949

Dear Maintainer,

on my system the bug still exists.

best regards

jakob

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

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

Versions of packages bluez depends on:
ii  dbus 1.10.8-1
ii  init-system-helpers  1.34
ii  kmod 22-1.1
ii  libc62.22-11
ii  libdbus-1-3  1.10.8-1
ii  libglib2.0-0 2.48.1-1
ii  libreadline6 6.3-8+b4
ii  libudev1 230-2
ii  lsb-base 9.20160601
ii  udev 230-2

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/bluetooth/main.conf changed:
[General]
Name = aldebaran
MultiProfile = multiple


-- no debconf information

Bug#827177: transition: qtbase-opensource-src

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/qtbase-abi-5-6-1.html

On 13/06/16 13:54, Lisandro Damián Nicanor Pérez Meyer wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi RT! After a long wait we pushing Qt 5 to unstable again.
> 
> It is worth to note that with this transition qtquick1-opensource-src
> will no longer build and so we will ask for it's removal.
> 
> Affected packages are kadu, kadu-mime-tex and musescore:
> 
> 
> 
> Thanks in advance!

Go ahead.

Cheers,
Emilio

Bug#827180: RFS: skiboot/5.2.2-2

[Frederic Bonnard]

Package: sponsorship-requests
Severity: normal

Dear mentors, Gianfranco,

I am looking for a sponsor for my package "skiboot". This is a packaging update
because I modified debian/copyright for 3 files.

 Package name: skiboot
 Version : 5.2.2-2
 Upstream Author : skiboot team
 URL : http://github.com/open-power/skiboot/
 License : Apache-2.0, CC0, BSD-2-Clause, MIT/X11-BSD-like
 Section : admin

It builds those binary packages:

  opal-prd   - OPAL Processor Recovery Diagnostics daemon
  opal-utils - OPAL firmware utilities

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/skiboot/skiboot_5.2.2-2.dsc

More information about skiboot can be obtained from 
http://github.com/open-power/skiboot/


Regards,
 Frederic Bonnard

Bug#827179: nova-common: pybasedir in nova.conf contains build directory information

[Turbo Fredriksson]

Package: nova-common
Version: 2:13.0.0-3
Severity: minor

- s n i p -
# Directory where the nova python module is installed (string value)
#pybasedir = 
/home/zigo/sources/openstack/mitaka/nova/build-area/nova-13.0.0/debian/tmp/usr/lib/python2.7/dist-packages
- s n i p -

Granted, it's commented out, but it would be nice if it
was correct anyway.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nova-common depends on:
ii  adduser3.114
ii  bridge-utils   1.5-9
ii  dbconfig-common2.0.4
ii  debconf [debconf-2.0]  1.5.59
ii  iproute2   4.3.0-1+b1
ii  python-amqplib 1.0.2-1
ii  python-configobj   5.0.6-2
ii  python-iso8601 0.1.11-1
ii  python-nova2:13.0.0-3
pn  python:any 
ii  sqlite33.13.0-1

nova-common recommends no packages.

Versions of packages nova-common suggests:
ii  python-mysqldb  1.3.7-1+b1

-- debconf information:
* nova/metadata_secret: (password omitted)
  nova-common/pgsql/admin-pass: (password omitted)
* nova/rabbit_password: (password omitted)
* nova/neutron_admin_password: (password omitted)
* nova/admin-password: (password omitted)
  nova-common/app-password-confirm: (password omitted)
  nova-common/mysql/app-pass: (password omitted)
* nova-common/mysql/admin-pass: (password omitted)
  nova-common/pgsql/app-pass: (password omitted)
* nova-common/password-confirm: (password omitted)
  nova-common/pgsql/authmethod-user: password
* nova-common/remote/newhost: openstack.bayour.com
* nova-common/remote/port:
* nova-common/dbconfig-upgrade: true
* nova/rabbit_host: openstack.bayour.com
  nova-common/pgsql/changeconf: false
  nova-common/pgsql/method: TCP/IP
* nova/neutron_admin_username: admin
  nova-common/pgsql/no-empty-passwords:
* nova-common/upgrade-error: abort
* nova/rabbit_userid: openstack
* nova-common/database-type: mysql
* nova/my-ip: 10.0.4.3
* nova-common/dbconfig-install: true
  nova-common/pgsql/admin-user: postgres
* nova-common/install-error: abort
* nova/active-api: osapi_compute, metadata
* nova-common/dbconfig-remove: true
* nova-common/db/dbname: nova
  nova-common/pgsql/manualconf:
  nova-common/passwords-do-not-match:
* nova-common/mysql/admin-user: root
* nova-common/missing-db-package-error: abort
* nova/configure_db: true
* nova-common/remove-error: abort
* nova/auth-host: 10.0.4.1
* nova-common/remote/host: openstack.bayour.com
  nova-common/internal/reconfiguring: false
* nova-common/db/basepath: /var/lib/openstack/nova
* nova-common/mysql/method: TCP/IP
  nova-common/pgsql/authmethod-admin: ident
  nova-common/purge: false
* nova/neutron_admin_tenant_name: admin
* nova/neutron_url: http://127.0.0.1:9696
* nova/admin-user: admin
* nova/admin-tenant-name: admin
  nova-common/internal/skip-preseed: false
* nova-common/db/app-user: nova-common
* nova-common/dbconfig-reinstall: false
* nova-common/upgrade-backup: true

Bug#826954: cloud.debian.org: NoCloud datasource not enabled in Debian 8.5 image

[Thomas Goirand]

On 06/10/2016 11:35 PM, Clint Byrum wrote:
> Excerpts from Thomas Goirand's message of 2016-06-10 21:20:30 +0200:
>> On 06/10/2016 03:42 PM, Benjamin Drung wrote:
>>> Package: cloud.debian.org
>>> Severity: normal
>>>
>>> Hi,
>>>
>>> the cloud image debian-8.5.0-openstack-amd64.qcow2 [1] does not enable
>>  the
>>> NoCloud datasource:
>>>
>>> <8-
>>> root@debian:~# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
>>> # to update this file, run dpkg-reconfigure cloud-init
>>> datasource_list: [ConfigDrive, Openstack, Ec2]
>>> root@debian:~# dpkg-reconfigure cloud-init
>>> root@debian:~# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
>>> # to update this file, run dpkg-reconfigure cloud-init
>>> datasource_list: [ NoCloud, AltCloud, CloudStack, ConfigDrive, Ec2, MA
>> AS, OVF, GCE, None ]
>>> <8-
>>>
>>> Please enable the NoCloud datasource (and maybe others).
>>
>> Hi,
>>
>> I can enable so many source, yes, but what would be the use case of them
>> all? Isn't there is a drawback if I do activate all of the above
>> mentioned sources? Or do you believe it's fine to just use all of that?
>>
>> Please let me know and I'll do as suggested,
> 
> NoCloud is quite useful for making use of cloud-init when file-injection
> is the only option for an image boot, but one wants to still use
> cloud-init's features for some reason.
> 
> Unlike some of the others that poll network addresses, this one is pretty
> close to free. It just looks for a couple of files in /var.
> 
> 

Ok, so would it be nice to do:
datasource_list: [NoCloud, ConfigDrive, Openstack, Ec2]

and then nothing else? Any other suggestion?

Cheers,

Thomas Goirand (zigo)




signature.asc
Description: OpenPGP digital signature

Bug#826981: [tryton-debian] Bug#826981: cached-property: FTBFS:

[Mathias Behrle]

* Chris Lamb: " [tryton-debian] Bug#826981: cached-property: FTBFS:" (Fri, 10
  Jun 2016 21:11:42 +0100):

> Source: cached-property
> Version: 1.3.0-2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> cached-property fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   running install_scripts
>   I: pybuild base:184: /usr/bin/python3 setup.py install
> --root 
> /home/lamby/temp/cdt.20160610205935.MGGbCMSdcT.cached-property/cached-property-1.3.0/debian/python3-cached-property
> running install error: invalid Python installation: unable to
> open /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefile (No such file
> or directory) E: pybuild pybuild:274: install: plugin distutils failed with:
> exit code=1: /usr/bin/python3 setup.py install
> --root 
> /home/lamby/temp/cdt.20160610205935.MGGbCMSdcT.cached-property/cached-property-1.3.0/debian/python3-cached-property
> dh_auto_install: pybuild --install -i python{version} -p 3.5
> --dest-dir 
> /home/lamby/temp/cdt.20160610205935.MGGbCMSdcT.cached-property/cached-property-1.3.0/debian/tmp
> returned exit code 13 debian/rules:6: recipe for target 'binary' failed make:
> *** [binary] Error 25
> 
>   [..]
> 
> The full build log is attached.
> 
> 
> Regards,
> 

Hi Chris,

I cannot reproduce the issue when building with sbuild locally (build log
attached).

Could you please check, if your Python 3.5 installation at the time of testing
was up-to-date/corrupted?

Cheers,
Mathias

-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6


cached-property_1.3.0-2_amd64-20160613-1415.build
Description: Binary data


pgpYDvhdZTV52.pgp
Description: Digitale Signatur von OpenPGP

Bug#823843: cinnamon-common: Touchpad setting "tap to click" stopped working

[Jeremy Bicha]

On Mon, Jun 13, 2016 at 5:28 AM, Julien Cristau  wrote:
> On Sat, Jun 11, 2016 at 19:19:09 -0400, Jeremy Bicha wrote:
>
>> Version: 1.8.3-2
>
> This is not how you close bugs.

xserver-xorg-input-synaptics (1.8.3-2) unstable; urgency=medium

  * Cherry-pick upstream commit 59e5db, which renames 50-synaptics.conf
to 70-synaptics.conf. This means the synaptic driver will be used
instead of the libinput driver when both are installed.
  * Drop dbg package in favor of the dbgsym.

 -- Emilio Pozuelo Monfort  Thu, 26 May 2016 18:32:56 +0200

I apologize and will try to remember to be more verbose next time when
closing bugs.

But wasn't this bug supposed to be marked as fixed in message #20? The
fix in version 1.8.3-2 seems to match very closely with what messages
#10 and #15 describe.

The next message (#33) is actually the opposite problem where this fix
broke GNOME.

Jeremy Bicha

Bug#827149: RFS: triggerhappy/0.4.0-1

[Andrew Shadura]

On 13 Jun 2016 00:03, "Stefan Tomanek" 
wrote:
>
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "triggerhappy"
>
>  * Package name: triggerhappy
>Version : 0.4.0-1
>Upstream Author : Stefan Tomanek 
>  * URL : https://github.com/wertarbyte/triggerhappy
>  * License : GPLv3
>Section : utils
>
>   It builds those binary packages:
>
> triggerhappy - global hotkey daemon for Linux
>
>   To access further information about this package, please visit the
following URL:
>
>   https://mentors.debian.net/package/triggerhappy
>
>
>   Alternatively, one can download the package with dget using this
command:
>
> dget -x
https://mentors.debian.net/debian/pool/main/t/triggerhappy/triggerhappy_0.4.0-1.dsc
>
>   More information about hello can be obtained from
https://www.example.com.
>
>   Changes since the last upload:
>
>* update to version 0.4.0 (closes: bug#827079, bug#769184)
>* adapt to newer debian packaging standards

Hi, could you please also ship my systemd integration (see upstream PR and
branch)?

-- 
Cheers,
  Andrew

Bug#827108: patch for --downloadonly (was Re: [qubes-devel] Re: Reinitialize Templates

[Holger Levsen]

On Sun, Jun 12, 2016 at 02:09:58PM +0200, Marek Marczykowski-Górecki wrote:
> > > Hmm, Fedora has 3.4.3-507, so I'm afraid --downloadonly option is added
> > > only in some Fedora local patch :/
> >  
> > hmpf. if that patch were identified one could file a wishlist bug
> > against the Debian package to include it…
> 
> Sigh.., it's part of a giant patch 3.4.3..HEAD:
> http://pkgs.fedoraproject.org/cgit/rpms/yum.git/tree/yum-HEAD.patch
> 
> Anyway it looks like the right commit is here:
> http://yum.baseurl.org/gitweb?p=yum.git;a=commit;h=639a768c93d8c18a1906bb22840d4acb5efa7ac4
> 
> But there were few modifications later. Generally this should be
> helpful:
> http://yum.baseurl.org/gitweb?p=yum.git&a=search&h=HEAD&st=commit&s=downloadonly

Thanks Marek, adding this info to the bug…

> Also it looks like downloadonly option was implemented as a plugin the
> past. So maybe cleaner solution would be to package that plugin on
> Debian?
> It used to be part of yum-utils repository, at least at the time of its
> last release (1.1.31, 5 years ago):
> http://yum.baseurl.org/gitweb?p=yum-utils.git;a=tree;f=plugins/downloadonly;h=b8442914b20623015a87ba30b4ae63e20e5c5e53;hb=ccf29c9525c1b39498d37384ede1a12bec766a1b

yum-utils 1.1.31 is in Debian stable and stretch…

> > does dnf have --downloadonly? 
> Yes, it works slightly differently than in yum, but is good enough.

maybe the yum Debian maintainers have plans of packaging dnf?


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#825693: RFS: nlohmann-json/1.1.0-1 [ITP]

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

Here are some notes about the packaging:

debian/nlohmann-json-dev.doc-base:
"Document: json" is too generic, remember it must be unique.

debian/rules:
There is too many commented out dh_make example lines, you should remove
them if you don't need them.

debian/README.source:
It says "You WILL either need to modify or delete this file"

debian/patches:
Patch names should end with .patch

debian/copyright:
It has Files-Excluded: test/catch.hpp but the tarball still contains this
file.
Consider using the same license as the upstream for debian/.
The format specification doesn't know about the License-Reference:
pseudo-field or whatever it is. Instead you should do the same as for GPL
licenses, provide a short license grant and add the path of the license
text. You can look at /usr/share/doc/*/copyright on your system for
examples.


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Luca Boccassi]

On Mon, 2016-06-13 at 13:04 +0200, Andreas Beckmann wrote:
> On 2016-06-13 12:36, Luca Boccassi wrote:
> >> Is there any tutorial how to build it from svn?
> 
> > https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/012917.html
> 
> And the easier way to build the .orig.tar.gz:
> 
> debian/rules get-orig-source
> 
> 
> Luca, maybe we should have a section about this in the wiki?
> 
> 
> Andreas

Good point, yes it would help, especially until we have new drivers up.

I tried to create an account but it errored out:

"Account creation failed: Due to an ongoing spam attack, this wiki is
configured to not automatically create wiki accounts for some users.
Please contact w...@debian.org first if you wish to create an account,
and describe what you want to do in the wiki.."

I've sent a mail, as soon as I have an account I'll add a few lines.

Kind regards,
Luca Boccassi


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

Bug#826300: fpc: fp-compiler not installable on powerpc since glibc 2.23

[Gianfranco Costamagna]

Hi,

>According to upstream:
>> Looking at that report, an objdump -D and/or gcc -S of a
>> the crt1.o of a relevant
>> system might help?
>Can you please check that?

I/we did debug a little bit, the failure actually is in the postinst script, 
here:
https://sources.debian.net/src/fpc/3.0.0%2Bdfsg-6/debian/fp-compiler.postinst.in/
fpcmkcfg-${VERSION} -0 -d "basepath=${LIB_DIR}/\$fpcversion" -o 
"${PKG_CFG_PATH}"

calling fpcmkcfg-3.0.0 fails with the log attached (log-fpcmkcfg)

I also called the script with strace (log-strace)

tried gcc -S (log-gcc)

and objdump -D (log-objdump)

please let me know if you need more information, or I have to forward logs to 
somebody
else.

Gianfranco


log-fpcmkcfg
Description: Binary data


log-gcc
Description: Binary data


log-objdump
Description: Binary data


log-strace
Description: Binary data

Bug#827158: lintian: false positive: depends-on-obsolete-package should no longer refer to debmake

[Santiago Vila]

On Mon, 13 Jun 2016, Paul Wise wrote:

> Package: lintian
> Version: 2.5.44
> Severity: normal
> X-Debbugs-CC: Osamu Aoki , Santiago Vila 
> 
> 
> debmake was removed from Debian in 2008 and then the name was hijacked
> in 2013 by a new package with a new codebase that AFAICT does a
> completely different thing to the earlier debmake.
> 
> https://tracker.debian.org/news/453372
> https://bugs.debian.org/462978
> https://tracker.debian.org/news/453375
> 
> Unfortunately lintian still warns about depending on debmake despite it
> being a completely new codebase, please remove it from that list.
> 
> E: check-all-the-things: depends-on-obsolete-package recommends: debmake

Alternatively, the current debmake could/should change its name and
call itself some other way.

In the last years of the old debmake, my job was to ensure that we
could live without it, i.e. to kill it for good. Seeing the name being
used again (even if it's for a different codebase) seems awkward.

Thanks.

Bug#827173: gcc-6: missing "Debian" in "gcc-6 --version" output

[Matthias Klose]

On 13.06.2016 12:46, Vincent Lefevre wrote:
> Package: gcc-6
> Version: 6.1.1-6
> Severity: minor
> 
> $ gcc-6 --version
> gcc-6 ( 6.1.1-6) 6.1.1 20160609
> Copyright (C) 2016 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> The first line of the output should have been:
> 
> gcc-6 (Debian 6.1.1-6) 6.1.1 20160609
> 
> There was no such problem with gcc-6 6.1.1-5.

from the logs:

> Configured with: -v
>--with-pkgversion=' 6.1.1-6'

Don't know what happened. A new build has the distro name again.

Bug#827108: patch for --downloadonly (was Re: [qubes-devel] Re: Reinitialize Templates

[Marek Marczykowski-Górecki]

On Mon, Jun 13, 2016 at 12:32:23PM +, Holger Levsen wrote:
> yum-utils 1.1.31 is in Debian stable and stretch…

But apparently plugins are not packaged there[1].

yum-utils.spec contains manual installation of them:
mkdir -p $RPM_BUILD_ROOT/%{_sysconfdir}/yum/pluginconf.d/
$RPM_BUILD_ROOT/usr/lib/yum-plugins/
mkdir -p $RPM_BUILD_ROOT/%{_sysconfdir}/yum/post-actions

cd plugins
for plug in $plugins; do
install -m 644 $plug/*.conf
$RPM_BUILD_ROOT/%{_sysconfdir}/yum/pluginconf.d/
install -m 644 $plug/*.py $RPM_BUILD_ROOT/usr/lib/yum-plugins/
%{__python} -c "import compileall;
%compileall.compile_dir('$RPM_BUILD_ROOT/usr/lib/yum-plugins', 1)"
done

`make install` doesn't include it.

> > > does dnf have --downloadonly? 
> > Yes, it works slightly differently than in yum, but is good enough.
> 
> maybe the yum Debian maintainers have plans of packaging dnf?

So there are three ways of adding this feature:
 - include yum patch for --downloadonly option
 - package yum-utils plugins (probably each as separate sub-package)
 - package dnf

[1] https://packages.debian.org/jessie/all/yum-utils/filelist

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


signature.asc
Description: PGP signature

Bug#827181: ITP: libjs-angular-file-upload -- lightweight angular directive to upload files

[Ivan Udovichenko]

Package: wnpp
Severity: wishlist
Owner: Ivan Udovichenko 

* Package name: libjs-angular-file-upload
  Version : 12.0.4
  Upstream Author : Danial Farid
* URL : https://github.com/danialfarid/ng-file-upload
* License : MIT
  Programming Lang: JavaScript
  Description : lightweight angular directive to upload files

 Angular ng-file-upload directive which supports a wide variety of features.
 It allows you to upload files in many sophisticated ways with ability to
 track the progress, native validation support for file type/size, image
 width/height/aspect ratio, video/audio duration, ng-required with
 pluggable custom sync or async validations, show thumbnail or preview of
 selected images/audio/videos, and more.



signature.asc
Description: OpenPGP digital signature

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Bogdan Vatra]

On Monday 13 June 2016 13:36:35 Luca Boccassi wrote:
> On Mon, 2016-06-13 at 13:04 +0200, Andreas Beckmann wrote:
> > On 2016-06-13 12:36, Luca Boccassi wrote:
> > >> Is there any tutorial how to build it from svn?
> > > 
> > > https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-April/01
> > > 2917.html> 
> > And the easier way to build the .orig.tar.gz:
> > 
> > debian/rules get-orig-source
> > 
> > 
> > Luca, maybe we should have a section about this in the wiki?
> > 
> > 
> > Andreas
> 
> Good point, yes it would help, especially until we have new drivers up.
> 
> I tried to create an account but it errored out:
> 
> "Account creation failed: Due to an ongoing spam attack, this wiki is
> configured to not automatically create wiki accounts for some users.
> Please contact w...@debian.org first if you wish to create an account,
> and describe what you want to do in the wiki.."
> 
> I've sent a mail, as soon as I have an account I'll add a few lines.
> 

I just tried 364 and it doesn't work on Linux 4.6 :( I had to go back to 352.
Shall I try 367 :) ?

Yours,
BogDan.

Bug#827089: RFS: dh-runit/0.1 ITP

[Dmitry Bogatov]

> while I did some work on runit package a while ago, I'm not sure about
> how you want the packages to use your new shiny dh call?
> how do you plan to notify them about it?
> do you plan to open a lot of bugs for packages exposing a runit script?

First of all, runit supports (as policy requires) support for running
/etc/init.d/scripts, so there is no need to make haste. Yes, I plan to
open bugs with patches to provide `runscripts'. As long as there is no
runscript is provided, runit can use init.d script.

dh_runit is now needed by 'getty-run', that now is built
from runit source package.

> I admit, I'm not a fan of too-many-init-systems-to-support, and runit
> is not so far one of the most used...

Sure. As-is in archives it requires determination to migrate on it, so
no surprise. And, as was discussed in upstart RM thread, popularity is
poor metric, when you compare any init system with systemd, which is
installed by default (ugh) and sysvinit, compatibility with which is
mandated by policy.

> but a debhelper script is always something appreciated that can
> simplify things...

Again, dh_runit is dependency of runit now. I would put it into runit
source package, but it would create chicken-and-egg problem.

> another question: I see a lot of activity on git, so you need to
> freeze at some point, and tag the "release", otherwise the sponsor
> won't know when you are ready to go.

If I am correct, master is same as version on mentors. If you insist,
I can make 'release' tag, but I prefer to tag things when they reach
Archives.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
X-Web-Site: sinsekvu.github.io

Bug#827182: hplip: HP C3180 failing halted with blinking display

[José Luis González]

Package: hplip
Version: 3.16.5+repack0-1

After printing inverted even pages on range 1-55 from the
follwing document:

http://www.brilliantclassics.com/media/965989/94840-Vivaldi-Liner-Notes-Download.pdf

my HP C3180 has become unresponding with all the leds and display
blinking very fast and an E letter in the copies display. The end of
the last page was seemingly printed but it didn't get ejected. The
cancel button did not work. I had to turn the printer off and on again
to get it to a working state and eject the end of the page. Afterwards
a test page was printed.

Bug#649623: status of python-freetype packaging

[Ghislain Vaillant]

Hi Daniel,

Any news on this? Do you need any help?

Ghis

Bug#819178: Incorrect CA file path

[Christian Henz]

I am having the same issue on Ubuntu 14.04.

The problem seems to be that pgbouncer asks libssl (via libusual) to load a non 
existing file "/etc/ssl/cert.pem".

The configuration script for libusual tries to autodetect the CA file as either

/etc/ssl/certs/ca-certificates.crt
/etc/ssl/cert.pem

The first file does exist, the latter does not. So it seems that build-time 
configuration for pgbouncer/libusual is not correct here.

As a workaround, I created a symlink:

/etc/ssl/cert.pem -> /etc/ssl/certs/ca-certificates.crt


Greetings,
Christian

Bug#827178:

[Martin Gebhardt]

I found an additional message in auth.log:

==> /var/log/auth.log <==
Jun 13 14:58:06 cld005 virsh: Bad IPLOCALPORT value

Bug#797917: Porting the patch to debian?

[Danny Edel]

Hi,

I would like to try one of the patches from upstream, but I can't figure
out how to apply them to the sourcecode I grab with "apt-get source
clang-".

In particular, neither the patch from
https://llvm.org/bugs/attachment.cgi?id=14874 nor the newer one from
http://reviews.llvm.org/D18035?download=true applies (quilt import ->
quilt push dies with "can't find file to patch").

Could someone help me by porting that patch against the Debian version
of clang, or even by uploading a patched version to experimental?  I
would gladly test and provide feedback, right now clang is near-unusable
since pretty much every c++ library in Debian uses those abi tags.

Thank you in advance,
Danny

Bug#826991: fastboot missing libziparchive.so.0

[Alberto Garcia]

On Fri, Jun 10, 2016 at 10:04:35PM +, Mouaad Aallam wrote:

> fastboot fails, says libziparchive.so.0 is missing:
> 
> $fastboot devices
> fastboot: error while loading shared libraries: libziparchive.so.0: cannot 
> open shared object file: No such file or directory

Same problem here, but with libext4_utils.so.0 instead:

$ fastboot
fastboot: error while loading shared libraries: libext4_utils.so.0: cannot open 
shared object file: No such file or directory

$ ldd /usr/bin/fastboot
linux-vdso.so.1 (0x7ffdc29c3000)
libziparchive.so.0 => /usr/lib/android/libziparchive.so.0 
(0x7f58671ab000)
libsparse.so.0 => /usr/lib/android/libsparse.so.0 (0x7f5866fa3000)
libext4_utils.so.0 => not found
libf2fs_utils.so.0 => not found
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5866bd5000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f58669b9000)
libutils.so.0 => /usr/lib/android/libutils.so.0 (0x7f5866793000)
liblog.so.0 => /usr/lib/android/liblog.so.0 (0x7f586658b000)
libbase.so.0 => /usr/lib/android/libbase.so.0 (0x7f5866385000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f5866005000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5865d07000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f5865af)
/lib64/ld-linux-x86-64.so.2 (0x56389cce9000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f58658d3000)
libcutils.so.0 => /usr/lib/android/libcutils.so.0 (0x7f58656c7000)
libbacktrace.so.0 => /usr/lib/android/libbacktrace.so.0 
(0x7f58654ba000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f58652b2000)
libunwind.so.0 => not found

$ ls /usr/lib/x86_64-linux-gnu/android/
libext4_utils.so.0  libf2fs_utils.so.0  libselinux.so.0  libunwind.so.0

Berto

Bug#827183: gwenview: kipi-plugins do not work with gwenview anymore

[Michael Meier]

Package: gwenview
Version: 4:16.04.1-1
Severity: normal

Since the whole mess with the update to plasma 5 the kipi plugins, which should 
appear in the "extra" menu in gwenview, are not loaded anymore.
I tried out to install the newer libkf5kipi31.0.0 (you have to deinstall 
digikam thatfor) but they don't appear. they also don't appear when libkipi11 
is installed.


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

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

Versions of packages gwenview depends on:
ii  libc6   2.22-11
ii  libexiv2-14 0.25-3
ii  libgcc1 1:6.1.1-4
ii  libjpeg62-turbo 1:1.4.2-2
ii  libkf5activities5   5.22.0-2
ii  libkf5baloo55.22.0-2
ii  libkf5completion5   5.22.0-1
ii  libkf5configcore5   5.22.0-1
ii  libkf5configgui55.22.0-1
ii  libkf5configwidgets55.22.0-1
ii  libkf5coreaddons5   5.22.0-1
ii  libkf5filemetadata3 5.22.0-1
ii  libkf5i18n5 5.22.1-1
ii  libkf5iconthemes5   5.22.0-1
ii  libkf5itemmodels5   5.22.0-1
ii  libkf5itemviews55.22.0-1
ii  libkf5jobwidgets5   5.22.0-1
ii  libkf5kdelibs4support5  5.22.0-2
ii  libkf5kiocore5  5.22.0-1
ii  libkf5kiofilewidgets5   5.22.0-1
ii  libkf5kiowidgets5   5.22.0-1
ii  libkf5notifications55.22.0-1
ii  libkf5parts55.22.0-1
ii  libkf5service-bin   5.22.0-1
ii  libkf5service5  5.22.0-1
ii  libkf5textwidgets5  5.22.0-1
ii  libkf5widgetsaddons55.22.0-1
ii  libkf5xmlgui5   5.22.0-1
ii  liblcms2-2  2.7-1
ii  libphonon4qt5-4 4:4.9.0-2
ii  libpng16-16 1.6.22-1
ii  libqt5core5a5.5.1+dfsg-17
ii  libqt5gui5  5.5.1+dfsg-17
ii  libqt5opengl5   5.5.1+dfsg-17
ii  libqt5printsupport5 5.5.1+dfsg-17
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-17
ii  libqt5x11extras55.5.1-3
ii  libstdc++6  6.1.1-4
ii  libx11-62:1.6.3-1
ii  phonon4qt5  4:4.9.0-2

Versions of packages gwenview recommends:
ii  kamera 4:16.04.1-1
pn  kio-extras 
pn  qt5-image-formats-plugins  

gwenview suggests no packages.

-- no debconf information

Bug#827184: yakuake: "Manage Profiles" settings option doesn't work

[Andrew Donnellan]

Package: yakuake
Version: 3.0.2-1
Severity: normal

Dear Maintainer,

Summary: the "Manage Profiles" menu item doesn't work as expected.

Steps to reproduce:

1) Open Yakuake
2) Click on settings menu in bottom right
3) Click Manage Profiles

Expected behaviour: Manage Profiles dialog box appears.

Actual behaviour: Nothing appears. If I run yakuake from another
console, I observe the following:

ajd@hal:~$ yakuake
Attempted to re-run an already running session.
QMetaObject::invokeMethod: No such method
Konsole::Part::showManageProfilesDialog(QWidget*)

Regards,

Andrew Donnellan


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

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

Versions of packages yakuake depends on:
ii  konsole-kpart 4:16.04.1-1
ii  libc6 2.22-11
ii  libgcc1   1:6.1.1-6
ii  libkf5archive55.22.0-1
ii  libkf5attica5 5.22.0-1
ii  libkf5auth5   5.22.0-1
ii  libkf5codecs5 5.22.0-1
ii  libkf5completion5 5.22.0-1
ii  libkf5configcore5 5.22.0-1
ii  libkf5configgui5  5.22.0-1
ii  libkf5configwidgets5  5.22.0-1
ii  libkf5coreaddons5 5.22.0-1
ii  libkf5crash5  5.22.0-1
ii  libkf5dbusaddons5 5.22.0-1
ii  libkf5globalaccel55.22.0-1
ii  libkf5i18n5   5.22.1-1
ii  libkf5iconthemes5 5.22.0-1
ii  libkf5jobwidgets5 5.22.0-1
ii  libkf5kiocore55.22.0-1
ii  libkf5kiowidgets5 5.22.0-1
ii  libkf5newstuff5   5.22.0-1
ii  libkf5notifications5  5.22.0-1
ii  libkf5notifyconfig5   5.22.0-1
ii  libkf5parts5  5.22.0-1
ii  libkf5service-bin 5.22.0-1
ii  libkf5service55.22.0-1
ii  libkf5sonnetui5   5.22.0-2
ii  libkf5textwidgets55.22.0-1
ii  libkf5widgetsaddons5  5.22.0-1
ii  libkf5windowsystem5   5.22.0-1
ii  libkf5xmlgui5 5.22.0-1
ii  libqt5core5a  5.5.1+dfsg-17
ii  libqt5dbus5   5.5.1+dfsg-17
ii  libqt5gui55.5.1+dfsg-17
ii  libqt5network55.5.1+dfsg-17
ii  libqt5widgets55.5.1+dfsg-17
ii  libqt5x11extras5  5.5.1-3
ii  libqt5xml55.5.1+dfsg-17
ii  libstdc++66.1.1-6
ii  libx11-6  2:1.6.3-1

yakuake recommends no packages.

yakuake suggests no packages.

-- no debconf information

Bug#826991: [Android-tools-devel] Bug#826991: fastboot missing libziparchive.so.0

[Chirayu Desai]

Hi,

This problem seems to have been fixed already in the source code.
The issue here is that fastboot doesn't search in the multi-arch path
(/usr/lib/x86_64-linux-gnu/android/) - you can verify that by
installing the 'patchelf' package, and then running 'patchelf
--print-rpath `which fastboot`', which prints '/usr/lib/android' for
the current version available in the repositories, 1:6.0.1+r16-3

The current version available in the source code, 1:6.0.1+r43-1,
doesn't have this problem as the commit [1] sets the proper rpath.

Kai-Chung, is there anything holding up the r43 release?
I'm guessing we need to do a synchronized release across all packages,
or perhaps even update to r46 first given that it's already available.

Either way, this has already been fixed and the nest version should be fine.

[1]: 
http://anonscm.debian.org/cgit/android-tools/android-platform-system-core.git/commit/?id=881e89cda5c49aa29d631bbc100d153cea0b63f0

On Mon, Jun 13, 2016 at 6:42 PM, Alberto Garcia  wrote:
> On Fri, Jun 10, 2016 at 10:04:35PM +, Mouaad Aallam wrote:
>
>> fastboot fails, says libziparchive.so.0 is missing:
>>
>> $fastboot devices
>> fastboot: error while loading shared libraries: libziparchive.so.0: cannot 
>> open shared object file: No such file or directory
>
> Same problem here, but with libext4_utils.so.0 instead:
>
> $ fastboot
> fastboot: error while loading shared libraries: libext4_utils.so.0: cannot 
> open shared object file: No such file or directory
>
> $ ldd /usr/bin/fastboot
> linux-vdso.so.1 (0x7ffdc29c3000)
> libziparchive.so.0 => /usr/lib/android/libziparchive.so.0 
> (0x7f58671ab000)
> libsparse.so.0 => /usr/lib/android/libsparse.so.0 (0x7f5866fa3000)
> libext4_utils.so.0 => not found
> libf2fs_utils.so.0 => not found
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5866bd5000)
> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f58669b9000)
> libutils.so.0 => /usr/lib/android/libutils.so.0 (0x7f5866793000)
> liblog.so.0 => /usr/lib/android/liblog.so.0 (0x7f586658b000)
> libbase.so.0 => /usr/lib/android/libbase.so.0 (0x7f5866385000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
> (0x7f5866005000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5865d07000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
> (0x7f5865af)
> /lib64/ld-linux-x86-64.so.2 (0x56389cce9000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
> (0x7f58658d3000)
> libcutils.so.0 => /usr/lib/android/libcutils.so.0 (0x7f58656c7000)
> libbacktrace.so.0 => /usr/lib/android/libbacktrace.so.0 
> (0x7f58654ba000)
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f58652b2000)
> libunwind.so.0 => not found
>
> $ ls /usr/lib/x86_64-linux-gnu/android/
> libext4_utils.so.0  libf2fs_utils.so.0  libselinux.so.0  libunwind.so.0
>
> Berto
>
> ___
> Android-tools-devel mailing list
> android-tools-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Andreas Beckmann]

On 2016-06-13 14:49, Bogdan Vatra wrote:
> I just tried 364 and it doesn't work on Linux 4.6 :( I had to go back to 352.
> Shall I try 367 :) ?

I'll try to propagate the 4.6 patches from 352 to the newer relases tonight

Andreas

Bug#827149: RFS: triggerhappy/0.4.0-1

[Andrew Shadura]

On 13 June 2016 at 15:47, Gianfranco Costamagna
 wrote:
> control: owner -1 !
>
>>Hi, could you please also ship my systemd integration (see upstream PR and 
>>branch)?
>
>
> Andrew, do you plan to upload the package once this is fixed?

I think I could.

> I see Jakub already did a wonderful review, and the current package on 
> mentors seems
> to address his concerns.
>
> I see your pull request doesn't merge anymore on current branch...

There's https://github.com/wertarbyte/triggerhappy/commits/systemd but
I haven't looked how much does it conflict with the master branch.

-- 
Cheers,
  Andrew

Bug#827185: source:llvm-toolchain-snapshot: Enable a full bootstrap of clang

[Sylvestre Ledru]

Package: source
Severity: wishlist

For now, clang is built using gcc.
We should be able to build clang using clang using the classical bootstrap 
sequence.
This will probably require a bunch of changes on debian/rules.


Sylvestre

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Bogdan Vatra]

On Monday 13 June 2016 15:44:26 Andreas Beckmann wrote:
> On 2016-06-13 14:49, Bogdan Vatra wrote:
> > I just tried 364 and it doesn't work on Linux 4.6 :( I had to go back to
> > 352. Shall I try 367 :) ?
> 
> I'll try to propagate the 4.6 patches from 352 to the newer relases tonight
> 

I installed 367 and I'm running it right now, seems to be ok.

Though VK support is not working. First and foremost it doesn't copy 
nvidia_icd.json to /usr/share/vulkan/implicit_layer.d and even when I copy it, 
it still fails to open it, because the vk_loader fails to "map" the functions 
names (vkGetInstanceProcAddr" -> "vk_optimusGetInstanceProcAddr")
even the mapping is in the json file
[...]
"functions": {
"vkGetInstanceProcAddr": "vk_optimusGetInstanceProcAddr"
},
[...]

BogDan.

Bug#827164: unable to start guest with ceph rbd disks

[Geert Stappers]

Control: tags -1 -moreinfo
Control: reassign -1 libvirt-clients

On Mon, Jun 13, 2016 at 01:34:02PM +0200, uli iske wrote:
> Hmm, looks like qemu is not guilty here.
> 
> Guest is starting and accessing the ceph disk with the following
> command:
> 
> qemu-system-x86_64 -drive
> file=rbd:rbd/sam:id=admin:key=mysecretcephkey==:auth_supported=cephx:mon_host=10.210.0.5,format=raw
> -machine pc-i440fx-2.4,accel=kvm -enable-kvm -curses
> 
> no errors. 
> 
> Sorry for the noise.

Please hunt to original problem about the 'internal error: process exited while 
connecting to monitor'

Bugreport reassigned to libvirt-clients as my best guest


Cheers
Geert Stappers

Bug#827161: [nvidia-driver] Any chance to get NVIDIA 364.12 soon?

[Luca Boccassi]

On Mon, 2016-06-13 at 15:44 +0200, Andreas Beckmann wrote:
> On 2016-06-13 14:49, Bogdan Vatra wrote:
> > I just tried 364 and it doesn't work on Linux 4.6 :( I had to go back to 
> > 352.
> > Shall I try 367 :) ?
> 
> I'll try to propagate the 4.6 patches from 352 to the newer relases tonight
> 
> Andreas

Bogdan,

Either wait for Andreas to do the merges from older versions, or try to
copy this patch manually:

https://anonscm.debian.org/viewvc/pkg-nvidia/packages/nvidia-graphics-drivers/trunk/debian/module/debian/patches/get-user-pages.patch?view=markup

to debian/module/debian/patches

And append "get-user-pages.patch" at the bottom of
debian/module/debian/patches/series

If memory serves that should be the only patch needed on x86 to build on
4.6

Kind regards,
Luca Boccassi


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

Bug#827186: links2: -http.fake-user-agent "UA" fails

[Fulano Diego Perez]

Package: links2
Version: 2.12-2
Severity: normal


try with these but not working from a few ip test sites like wtfismyip.com

-http.fake-user-agent 'UA'
-http.fake-user-agent "UA"

used with/without some other options still fails

which ever UA i try to use firefox 38 is reported

also the same when using fake.firefox 0/1



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

Kernel: Linux 4.5.0-2-amd64
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages links2 depends on:
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.22-7
ii  libcairo2   1.14.6-1+b1
ii  libdirectfb-1.2-9   1.2.10.0-5.2+b1
ii  libevent-2.0-5  2.0.21-stable-2+b1
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libglib2.0-02.48.1-1
ii  libgomp16.1.1-4
ii  libgpm2 1.20.4-6.2
ii  libjpeg62-turbo 1:1.4.2-2
ii  liblzma55.1.1alpha+20120614-2.1
ii  libpng16-16 1.6.21-5
ii  librsvg2-2  2.40.15-1
ii  libssl1.0.2 1.0.2h-1
ii  libtiff54.0.6-1
ii  libx11-62:1.6.3-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages links2 recommends:
ii  gnome-terminal [x-terminal-emulator]  3.20.2-1
ii  stterm [x-terminal-emulator]  0.6-1
ii  xterm [x-terminal-emulator]   324-2

links2 suggests no packages.

-- no debconf information