Bug#803547: bbswitch: please make the build reproducible

[Vincent Cheng]

Hi Luca,

On Sun, May 29, 2016 at 5:27 AM, Luca Boccassi  wrote:
> Control: -1 tags pending
>
> On Sat, 2015-10-31 at 10:56 +0100, Reiner Herrmann wrote:
>> Source: bbswitch
>> Version: 0.8-2
>> Severity: wishlist
>> Tags: patch
>> User: reproducible-bui...@lists.alioth.debian.org
>> Usertags: umask
>> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>>
>> Hi!
>>
>> While working on the "reproducible builds" effort [1], we have noticed
>> that bbswitch could not be built reproducibly.
>> The permissions inside a tarball vary because of different umasks.
>>
>> The attached patch tells tar to normalize the permissions.
>>
>> Regards,
>>  Reiner
>>
>> [1]: https://wiki.debian.org/ReproducibleBuilds
>
> Hello Reiner,
>
> Thanks for the patch, Vincent has applied it to Git so it will be in the
> next upload.
>
> I had noticed that the CI was reporting this problem for i386/armhf, but
> hadn't got around to look into it yet.
>
> Andreas, Vincent,
>
> There is movement again upstream but I don't think there will be a new
> release soon, and I don't think we have anything pending ourselves, so
> IMHO we can upload this already.

Ok, I've gone ahead and uploaded bbswitch a few minutes ago.

> I'm happy to take care of it, if one of you whitelists my key for the
> package. Thanks!

Of course. :)

Regards,
Vincent

Bug#825800: graphicsmagick: CVE-2016-5118

[Salvatore Bonaccorso]

Source: graphicsmagick
Version: 1.3.23-3
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for graphicsmagick.

CVE-2016-5118[0]:
popen() shell vulnerability via filename

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-5118
[1] http://www.openwall.com/lists/oss-security/2016/05/29/7

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#825799: imagemagick: CVE-2016-5118

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.8.9.9-7
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for imagemagick.

CVE-2016-5118[0]:
popen() shell vulnerability via filename

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-5118
[1] http://www.openwall.com/lists/oss-security/2016/05/29/7

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#825798: RFS: pidgin-sipe/1.21.1-1 -- Pidgin plugin for MS Office Communicator and MS Lync

[Jakub Adam]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for package "pidgin-sipe", whose source code is at:

  https://anonscm.debian.org/cgit/collab-maint/pidgin-sipe.git

or you may also:

  dget -x 
http://mentors.debian.net/debian/pool/main/p/pidgin-sipe/pidgin-sipe_1.21.1-1.dsc

It builds this binary package:

  pidgin-sipe - Pidgin plugin for MS Office Communicator and MS Lync

Changes since the last upload:

pidgin-sipe (1.21.1-1) unstable; urgency=medium

  * New upstream release.
- various bug fixes in media support
- configure no longer ignores CFLAGS/LDFLAGS/LIBS
  * Refresh cflags-remove-Wundef.patch.

 -- Jakub Adam   Mon, 30 May 2016 07:11:07 +0200

Regards,

Jakub




signature.asc
Description: OpenPGP digital signature

Bug#631189: openssh-server: sshd_config should support "include" directive

[Simon Law]

From: https://bugzilla.mindrot.org/show_bug.cgi?id=1585#c24

Damien Miller 2016-04-15 13:01:08 EST

Slightly modified patch applied, this will be in openssh-7.3

commit dc7990be865450574c7940c9880567f5d2555b37
Author: d...@openbsd.org 
Date:   Fri Apr 15 00:30:19 2016 +

upstream commit

Include directive for ssh_config(5); feedback & ok markus@

Upstream-ID: ae3b76e2e343322b9f74acde6f1e1c5f027d5fff
commit 35f22dad263cce5c61d933ae439998cb965b8748
Author: d...@openbsd.org 
Date:   Fri Apr 15 00:31:10 2016 +

upstream commit

regression test for ssh_config Include directive

Upstream-Regress-ID: 46a38c8101f635461c506d1aac2d96af80f97f1e

Bug#825797: RFP: druid -- fast column-oriented distributed data store

[Ben Finney]

Package: wnpp
Severity: wishlist

* Package name: druid
  Version : 0.9.0
  Upstream Author : Metamarkets Group Inc.
* URL : http://druid.io/
* License : Apache License 2.0
  Programming Lang: Java
  Description : fast column-oriented distributed data store

Druid is designed to ingest event/log data, chunking and compressing
that data into column-based queryable segments.
.
Features:
 * Low latency (real-time) data ingestion.
 * Arbitrary slice-and-dice data exploration.
 * Sub-second analytic queries.
 * Approximate and exact computations.

-- 
 \
  `\
_o__) Ben Finney 

Bug#825796: RFP: caravel -- data exploration platform

[Ben Finney]

Package: wnpp
Severity: wishlist

* Package name: caravel
  Version : 0.9.0
  Upstream Author : Maxime Beauchemin 
* URL : https://github.com/airbnb/caravel/
* License : Apache License 2.0
  Programming Lang: Python, JavaScript
  Description : data exploration platform

Caravel is a data exploration platform designed to be visual,
intuitive, and interactive.
.
Caravel provides:
.
 * A quick way to intuitively visualize datasets by allowing users
 to create and share interactive dashboards.
 * A rich set of visualizations to analyze your data, as well as a
 flexible way to extend the capabilities.
 * An extensible, high granularity security model allowing intricate
 rules on who can access which features, and integration with major
 authentication providers (database, OpenID, LDAP, OAuth &
 REMOTE_USER through Flask AppBuilder).
 * A simple semantic layer, allowing to control how data sources are
 displayed in the UI, by defining which fields should show up in
 which drop-down and which aggregation and function (metrics) are
 made available to the user.
 * Deep integration with Druid allows for Caravel to stay blazing
 fast while slicing and dicing large, real-time datasets.

-- 
 \
  `\
_o__) Ben Finney 

Bug#825110: /pci@f400000/ata-6@d/@0:3,/boot/vmlinux: Unknown or corrupt

[Milan Kupcevic]

affects 825110 yaboot
tags 825110 pending
thanks

Yaboot is not able to load files from a partition with metadata_csum and 64bit 
ext4 features enabled.

Milan

Bug#825394: systemd kill background processes after user logs out

[Lawrence D'Oliveiro]

Does setsid(1) still work? I read over this

carefully, and I think the answer is yes, but I’m not sure.

If it does, I’m happy. If it doesn’t, I would be annoyed.

Bug#526308: closed by Etienne Millon <m...@emillon.org> (Re: Bug#526308: rss2email needs DELAY_PER_MESSAGE)

[積丹尼 Dan Jacobson]

OK

Bug#825795: ITP: googler -- A power tool to Google (Web & News) and Google Site Search from the terminal

[szlin]

Package: wnpp
Severity: wishlist
Owner: SZ Lin (林上智) 

* Package name: googler
  Version : 2.4.1
  Upstream Author : Arun Prakash Jana , Zhiming
Wang .
* URL : https://github.com/jarun/googler
* License : GPLv3
  Programming Lang: Python
  Description :  A power tool to Google (Web & News) and Google Site
Search from the terminal

Googler is a python script which shows title, URL and text context for each
result and
supports sequential searches in a single googler instance in terminal;
furthermore, it can display results from terminal to browser directly.
.
Googler can also work fine in the device which didn't install X-Window.
.
Googler is under GNU GPLv3.


--
Sun-Ze Lin  (林上智)

Bug#825394: systemd kill background processes after user logs out

[Vladimir K]

If some software is supposed to relate to user's session and does not properly 
exit with session, that is the bug of said software and no business of init 
system.
This change breaks things and requires to jump through hoops to repair things 
that until now just worked.

Bug#821270: Review of git version

[Paul Wise]

On Mon, May 30, 2016 at 9:45 AM, Sean Whitton wrote:
> On Sun, May 29, 2016 at 03:12:27PM +, nord-stream wrote:
>> Done. Will this close the ITP bug automatically?
>
> Yup!

Long answer:

dh will run dh_genchanges which will run dpkg-genchanges, which will
use the find_closes function of the Dpkg::Changelog::Entry::Debian
perl module from libdpkg-perl to extract closed bugs from the
debian/changelog entry and then write those bugs to Closes filed in
the .changes file. The maintainer will upload that .changes file to
the Debian archive and dak (the Debian archive software) will use the
closed_bugs function to extract those bug numbers and send bug closing
mails to each of them.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Rick Thomas]

Package: procmail
Version: 3.22-24
Severity: normal

Dear Maintainer,

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

If procmail processes a mail with body containing a plaintext attachment that 
has a line
that begins with the string "From " it seems to think this is a separator 
between mails.
It winds up splitting the original mail into two parts and filing each as a 
separate mail
item.

This can happen when the attachment is a mail item that has not had the proper 
quoting
for lines beginning with "From ".  I have attached such an email to this 
bugreport.

There needs to be some way of telling procmail that it will receive input one 
email item
at a time, (as when being fed by fetchmail) so the line-begins-with-From 
processing is
not necessary.


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

Kernel: Linux 3.18.16-powerpc64 (SMP w/2 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 procmail depends on:
ii  libc6  2.19-18+deb8u4

Versions of packages procmail recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.84.2-1
ii  fetchmail  6.3.26-1+b1

procmail suggests no packages.

-- no debconf information
--- Begin Message ---
Your message dated Sun, 29 May 2016 22:37:47 +
with message-id 
and subject line Bug#825458: fixed in u-boot 2016.03+dfsg1-5
has caused the Debian Bug report #825458,
regarding Please enable Jetson TX1 (P2371-2180)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: u-boot
Version: 2016.05+dfsg1-1
Severity: wishlist

Please enable Jetson TX1 (P2371-2180).

I've attached a tested patch.

Note: NVidia's flash script looks for a file called "u-boot" so I
added a symlink from eboot.elf.

-- 
Martin Michlmayr
http://www.cyrius.com/
>From 12f46a6bc34370153def69c43e87aede348e4003 Mon Sep 17 00:00:00 2001
From: Martin Michlmayr 
Date: Thu, 26 May 2016 16:11:28 -0700
Subject: [PATCH] Add Jetson TX1 (P2371_2180) target

---
 debian/changelog  | 9 +
 debian/control| 2 +-
 debian/targets| 3 +++
 debian/u-boot-tegra.README.Debian | 8 
 debian/u-boot-tegra.links | 1 +
 debian/u-boot-tegra.lintian-overrides | 2 ++
 6 files changed, 24 insertions(+), 1 deletion(-)
 create mode 100644 debian/u-boot-tegra.links

diff --git a/debian/changelog b/debian/changelog
index 2df0edb..9ab93ce 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+u-boot (2016.05+dfsg1-2) UNRELEASED; urgency=medium
+
+  [ Martin Michlmayr ]
+  * u-boot-tegra: Add Jetson TX1 (P2371-2180) target.
+  * u-boot-tegra: Add arm64 arch.
+  * u-boot-tegra: Update README.Debian for Jetson TX1.
+
+ -- Martin Michlmayr   Thu, 26 May 2016 15:05:36 -0700
+
 u-boot (2016.05+dfsg1-1) experimental; urgency=medium
 
   * New upstream version.
diff --git a/debian/control b/debian/control
index 6da1a69..6e2d3ee 100644
--- a/debian/control
+++ b/debian/control
@@ -39,7 +39,7 @@ Description: A boot loader for imx systems
  ${uboot:platforms}
 
 Package: u-boot-tegra
-Architecture: armhf
+Architecture: armhf arm64
 Multi-Arch: same
 Depends: ${misc:Depends}
 Breaks: u-boot (<< 2014.10~rc2+dfsg1-2~)
diff --git a/debian/targets b/debian/targets
index 634e93c..71a06bf 100644
--- a/debian/targets
+++ b/debian/targets
@@ -153,6 +153,9 @@ armhf	sunxi		orangepi_plus	u-boot-sunxi-with-spl.bin
 # Ryan Finnie 
 arm64	rpi		rpi_3		u-boot.bin
 
+# Martin Michlmayr 
+arm64	tegra		p2371-2180	u-boot-dtb.bin
+
 avr32	-		hammerhead	u-boot.img
 
 mips	-		qemu_mips	u-boot.bin
diff --git a/debian/u-boot-tegra.README.Debian b/debian/u-boot-tegra.README.Debian
index 83cc222..97a0200 100644
--- a/debian/u-boot-tegra.README.Debian
+++ b/debian/u-boot-tegra.README.Debian
@@ -3,11 +3,19 @@
 At this point, you must install U-Boot to flash yourself from a host
 system using the Linux_For_Tegra tools.
 
+=== Jetson TK1 ===
+
 sudo ./flash.sh -L /usr/lib/u-boot/jetson-tk1/u-boot-dtb-tegra.bin jetson-tk1 mmcblk1p1
 
 It seems that L4T R19.3.0 is currently required (image does not boot
 if flashed with L4T R21.X).
 
+=== Jetson 

Bug#825785: ITP: tab -- Typesetter for lute tablature

[Paul Wise]

On Mon, May 30, 2016 at 4:36 AM, Chris Lamb wrote:

> * Package name: tab

This is uh, a little bit generic :)

> * URL : https://github.com/mandovinnie/Lute-Tab

I would suggest using the upstream name instead: lute-tab

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#825791: caja crashes

[shirish शिरीष]

in-line :-

On 29/05/2016, John Paul Adrian Glaubitz  wrote:
> Control: severity -1 normal
> Control: tags -1 unreproducible
> Control: tags -1 moreinfo
>
> On 05/30/2016 12:48 AM, shirish शिरीष wrote:
>> Dear Maintainer,
>> Trying to start caja on the Desktop gives me the following output on the
>> CLI -
>
> Could you please stop filing bugs without verifying first that it's a local
> configuration issue, please?

Dear John,

I tried it two ways :-

a. Looked at .config/caja in my home directory and tried to see if
there was anything that I may have changed inadvertantly but didn't
see anything that is/was amiss.

b. In order to ensure that it's not something in .config/caja
sub-directory that might have been disruptive, removed the whole caja
sub-directory and ran caja again but with the same results as before.

If there is anything else I should have tried out, please let me know.

The only thing I can think of which might remotely have connection is
with the newer marco as that is still stuck in the NEW queue and hence
the rest of the mate-core and it dependants are not able to jump to
1.14 . If it's to do with that then there is no way to know that.

Actually I was not gonna file this bug and wait for the whole
migration to take place but then saw this blog post from p.d.o.
http://sunweavers.net/blog/node/42 hence decided to file the
bug-report.

> Also, please refrain from filing bugs with severity grave unless you know
> what the ramifications are. Filing bug report with "grave" will prevent
> a package from migration to testing and if you file a bug report like
> that, you should be absolutely sure it's *not* a local issue.
>
> Which it apparently is, because caja works fine here.

Please let me know if there is anyway to figure out the issue/bug.

> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#821270: Review of git version

[Sean Whitton]

control: tag -1 -moreinfo

On Sun, May 29, 2016 at 03:12:27PM +, nord-stream wrote:
> Done. Will this close the ITP bug automatically?

Yup!

--
Sean Whitton


signature.asc
Description: PGP signature

Bug#825089: Fixed with systemd upgraded to 230

[Steven Shiau]

On 5/23/2016 PM 09:38, Steven Shiau wrote:

Package: util-linux
Version: 2.28-5
Severity: important

Dear Maintainer,

* What led up to the situation?
  After upgrading to util-linux 2.28-5, the nfsroot machine fails to reboot 
or shutdown. It hangs at
  "nfs: server xxx not responding, still trying".
  If I reverted to util-linux 2.27.1-6, then no such issue.
  Attached please find the error messages when client failing to 
reboot/shutdown.
  If you need more info, please let me know.



This issue was fixed when my systemd was upgraded to 230.
Thanks.

Steven

--
Steven Shiau 
Public Key Server PGP Key ID: 4096R/47CF935C
Fingerprint: 0240 1FEB 695D 7112 62F0  8796 11C1 12DA 47CF 935C

Bug#825793: Installing the lilo bootloader on a qemu/kvm VM fails

[Marvin Renich]

Package: installation-reports
Severity: important
Tags: d-i

Installing lilo bootloader on qemu/kvm virtual machine fails.

-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/stretch_di_alpha6/amd64/iso-cd/debian-stretch-DI-alpha6-amd64-netinst.iso
Date: 

Machine: qemu/kvm using virt-manager
Partitions: 
(I cannot cut-and-paste from the virt-viewer, but here is an abridged
summary, typed by hand)

/dev/vda1 is mounted on both /target and /dev/.static/dev.
/dev/sr0 is mounted on both /target/media/cdrom0 and /cdrom.

sfdisk -l /dev/vda gives

DeviceBoot Start  End  Sectors Size Id Type
/dev/vda1  2048 14678015 14675968   7G 83 Linux


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

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

Comments/Problems:

I created a virtual machine using virt-manager and used the stretch DI
alpha 6 netinst to install Debian.  I selected expert (non-graphical)
install.  I used manual partitioning to create a single partition
without a swap partition.  The other options were defaults, except for
things like hostname and initial user (no root login).  When I skipped
"Install GRUB boot loader" and selected "Install LILO boot loader", then
selected "/dev/vda: Master Boot Record", I get the "Installation step
failed" dialog.

As a side note, the actual command that failed and the output from that
command would help immensely.  The idea that "technical output" scares
users is flawed; when something goes wrong, even if the user is unable
to understand the lower level diagnostics, providing it allows the user
to find help more easily and/or provide more useful bug reports.

I am going to guess (and this is just a guess) that what I would have
seen, had the output to the command been visible, was either

/bin/sh: liloconfig: not found

or 

/bin/sh: lilo: not found

as switching to another console shows that neither command is installed.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

I have snipped the installer-hardware summary, as I believe the host
environment is completely irrelevant to this bug, other than it is an
amd64 architecture.  If there is a specific piece of information that
would help in the diagnosis, I will be more than happy to provide it.

I am using libvirt-clients, libvirt-daemon, and libvirt-daemon-system
version 1.3.3-2; virt-manager 1:1.3.2-4; qemu 1:2.5+dfsg-5+b1.

Thanks...Marvin

Bug#825677: freedombox-setup: Remove flash-kernel code specific for beaglebone

[Sunil Mohan Adapa]

On 05/30/2016 05:40 AM, James Valleroy wrote:
[...]
> 
> It looks like this may not be working as intended. flash-kernel is still
> run during first-run, except $kernel_version is now empty. Should
> flash-kernel only be run here for dreamplug?
> 

I saw no reason why flash-kernel should be specially for Beagle Bone
Black, so I removed that part of the code.  It is not a problem if
flash-kernel is run during first-boot.

I believe that there is no reason to run flash-kernel code for any
machine other than Dreamplug.  I wanted to deal with that at a later point.

Even for Dreamplug, I don't believe that flash-kernel actually works
given its vfat boot partition.

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#784612: [anki] Qt4's WebKit removal

[Nicolas Kuttler]

For anybody else wondering about this, the maintainer has already
contacted upstream and they are aware of the problem,
https://anki.tenderapp.com/discussions/ankidesktop/16516

Bug#825792: issues caused by lack of a bpo in jessie

[Nicholas D Steeves]

Correction, for item 3)

dh_elpa is not provided by debhelper, but the dh-elpa package depends
on a newer version of debhelper.

Sorry for the oversight!
Nicholas

Bug#825792: issues caused by lack of a bpo in jessie

[Nicholas D Steeves]

Package: debhelper
Version: 9.20160403

Dear maintainer,

Please backport debhelper to Jessie.  Here are the issues I've
encountered resulting from its absence:

1) lintian bpo version depends on a newer debhelper
- lintians errors must presently be ignored
2) without a newer debhelper, one of the following occurs
a) a package ignores removing explicit creation of -dbg packages
to reduce bpo maintainance, which needlessly impedes progress to Stretch
b) bpo maintenance becomes a needless hassle as those -dbg rules need to be
added for each bpo release.
3) a bpo of Magit 2.x requires dh_elpa, thus a newer debhelper
 - the changes between Magit 1.x and 2.x make learning 1.x a waste of time

I sincerely hope that the issues related to backporting libdpkg-perl
can be overcome to make this possible, because Debian stable +
backports is the most reliable and featureful workstation OS I've had
the pleasure of using.  Truly the best of the best.

Nicholas

Bug#825677: freedombox-setup: Remove flash-kernel code specific for beaglebone

[James Valleroy]

On Sat, 28 May 2016 23:52:03 +0530 Sunil Mohan Adapa 
wrote:
> Currently freedom-maker uses flash-kernel to generate boot script, copy
> the DTB etc. during BeagleBone Black's image building. This is no
> longer required. When a kernel is upgraded, flash-kernel is
> automatically run from the hooks.
>
> Attached patch remove this code. It has not be tested yet.

It looks like this may not be working as intended. flash-kernel is still
run during first-run, except $kernel_version is now empty. Should
flash-kernel only be run here for dreamplug?



signature.asc
Description: OpenPGP digital signature

Bug#824676: cleandb.sh fails when run

[Rob McAninch]

Just realized when I do run this via cron, it gives this eror

ERROR: Configuration error. Unsupported database driver: 

-- 
Rob McAninch

Bug#825305: hints on the gthumb gconf2->gsettings convertion issue

[Herbert Fortes (hpfn)]

Hi,

Em 29/05/2016 16:37, Andreas Henriksson escreveu:

Hello Herbert Fortes.

Hopefully I can help out with the information you need.

The debian pkg gthumb-data built from src:gthumb contains the convertion
file:
https://sources.debian.net/src/gthumb/3:3.4.3-1/data/gthumb.convert/

Among other things this file specifies the gconf2 key called
"show-thumbnails" should be mapped to "org.gnome.gthumb.browse
show-thumbnails" gsettings schema key.

The gsettings schema for gthumb on the other hand also shipped declares
that no such key exists in the schema, see:
https://sources.debian.net/src/gthumb/3:3.4.3-1/data/org.gnome.gthumb.gschema.xml.in/#L48

My guess is that it has simply been removed and the convertion mapping
forgotten to be upgraded when doing so...
This suspicion was quickly confirmed by looking at your git history:
https://anonscm.debian.org/cgit/collab-maint/gthumb.git/commit/data/org.gnome.gthumb.gschema.xml.in?id=485570d6cbd5cbc5a9026acc31ba9f108e9e998b

I'd strongly suggest you simply stop shipping the (outdated/broken)
gconf2 convertion file in the debian pkg since all users of old gthumb
versions using gconf2 should have been uograded and converted over to
gsettings long ago already.
I'd also urge you to contact gthumb uostream to have them remove the
convertion file (or fix it if they think there are still remaining users
that need to be converted).

Hope thus helps clear out the confusion.



Thanks !

Tomorrow I will remove 'gthumb.convert' file from the Debian package
and talk to the upstream.

Was really nice.



regards,
Herbert

Bug#825610: Updated Vietnamese translation for adduser

[Afif Elghraoui]

Control: tag -1 + pending

على السبت 28 أيار 2016 ‫18:08، كتب Trần Ngọc Quân:
> Hi,
> 
> Please help me apply this patch on
> 
> 

Many thanks!
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#825785: ITP: tab -- Typesetter for lute tablature

[Ben Hutchings]

On Sun, 2016-05-29 at 22:47 +0100, Chris Lamb wrote:
> > 
> > Should be lute-tab or something like that.
> 
> That just seems to be the GitHub repo name, upstream seems to call it
> "Tab":
> 
>  http://www.cs.dartmouth.edu/~wbc/lute/AboutTab.html
> 
> .. and the binary is called "tab".
> 
> Would you still suggest the "lute" prefix?

I would - 'tab' is a very generic name and is also used to refer to
other kinds of tablature notation, a control character, a user
interface element, etc.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer


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

Bug#824673: wine32-development-tools:i386 cannot be installed on amd64

[Jens Reyer]

I'll change the dependencies once I've verified if pkg:i386
or pkg:amd64 are legit notations.


Package: wine32VERSION-tools
Depends:
 gcc | gcc-multilib:amd64 [i386],
 ${perl:Depends} | perl:any [i386],

Package: wine64VERSION-tools
 Depends:
 libwineVERSION-dev (= ${binary:Version}) | libwineVERSION-dev:i386 (>= 
${source:Version}) [amd64],


I'd add to README.Debian something like:

Tools (winegcc, ...) and 32-/64 bit
===
For 32-bit output from the wine64-tools (or wine64-development-tools) on amd64
install libwine-dev:i386 (or libwine-development-dev:i386).
Than use "-m32" (for winemaker --wine32). For winegcc specify additionally
"-L/usr/lib/i386-linux-gnu/wine".

Any review is welcome!

Greets
jre

Bug#127074: axel: Axel does not support .netrc files

[Eriberto Mota]

To make easier the development, some information about .netrc files
can be found at:

- man 5 netrc
- http://www.mavetju.org/unix/netrc.php

Eriberto

Bug#825010: libscope-upper-perl: FTBFS with Perl 5.24: 'CXt_LOOP_FOR' undeclared

[gregor herrmann]

On Sun, 22 May 2016 16:34:57 +0300, Niko Tyni wrote:

> Package: libscope-upper-perl
> Version: 0.28-1
> Severity: important
> User: debian-p...@lists.debian.org
> Usertags: perl-5.24-transition zrh2016
> Forwarded: https://rt.cpan.org/Ticket/Display.html?id=112246
> 
> This package fails to build with Perl 5.24 (currently in experimental).
> 

There has been talk on p5p pointing to a patchset at rt.perl.org:
https://rt.perl.org/Public/Bug/Display.html?id=127875


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Cocksucker


signature.asc
Description: Digital Signature

Bug#825735: Bacula director does not start silently due to database mismatch

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am So den 29. Mai 2016 um 20:25 schrieb Paul Gevers:
> Control: retitle -1 enable setting dbc_install during reconfigure
> Control: severity -1 minor

I still think that is a mayor error. It killed my database.

> On 27-05-16 14:34, Klaus Ethgen wrote:
> >> I am not sure if you are now talking about the current upgrade. If you
> >> are than that is correct, you didn't get the question because you had
> >> dbc_install=false. If you are talking about "ever" than something
> >> clearly failed during the migration.
> > 
> > True, with upgrade I did not get any question.
> > 
> > I got this (and only this) question when using dpkg-reconfigure.
> 
> Sure, but dpkg-reconfigure will never apply upgrades from the past

I never claimed that.

> because it only applies the upgrades that are needed from YOUR old
> version to the current version. As the old version and the current
> version are the same, that would not make sense.

Well, you are wrong. dpkg-reconfigure asks every existing question. In
this case there is just only one in the present package.

> dpkg-reconfigure can sensibly only recreate the database from scratch
> or leave it alone. So dpkg-reconfigure is the wrong solution to the
> problem.

No, it is the right one. The questions, respective the configuring items
are wrong.

That was never made for migrating existing databases into this system.
And more over, there was no way documented how to do it.

Fact is that old bacula was able to do the migration of older databases
to new versions and the new system does not. So this is a complete
change of how it work. More over, dbc is completely useless except you
start using the bacula package _after_ dbc was stated to get used.

> >> As bacula migrated to
> >> dbconfig-common support for their MySQL and PostgreSQL databases way
> >> before that time (in 2006), I suspect you got the old (install) question
> >> and this would explain why you haven't seen the question in mentioned in
> >> my previous e-mail.
> > 
> > Well, I do not know how long, but I use bacula for really long time now.
> > I have file dates up to begin of 2009 but using bacula much longer.
> 
> Well, the bacula SQLite switch was done in version 3.0.3-3 (8 Feb 2010),
> so if you were following closely (have you always run your bacula on
> unstable), you may have been just in between.

Yes, I always run it on unstable. I was depending on settings that was
only available there.

And yes, I got that, that the dbc switch was done in 2010. And I
answered you that I use bacula from much longer before that date.

> >>> And that might be the problem.
> > 
> >> Why?
> > 
> > Well, I want to use the upgrade but not the install of a new database.
> 
> Well, that is a uncommon situation,

Whut!?

Not deleting a existing database is a uncommon situation?

> so you currently need to do some manual action, i.e. a change in a
> configuration file.

Even if I should do that, there was never a hint about that. And the
name of the relevant variable does say: "Never ever change me to true
if you want to keep your database!"

Sorry, but slowly that issue gets surreal. Database is to keep values.
Deleting the database is never a good option (except you did only play
around in the begin).

And when the topic and all documentation says that when one change that
parameter to true it will delete the database, then, I could not believe
that anybody would answer "yes" to that question.

> The point of confusion may be that database install in dbconfig-common
> only means initial install and possibly during reconfigure. Any other
> moment, dbconfig-common is not going to install anything, definitely
> not during upgrades.

What now? Does this parameter do initial installation of the database?
Does it delete it or not? Does it do that when doing the configuration
via debian-config? What is true now?

> >>> There was never a question about update.
> > 
> >> As explained, with dbc_install=false that is to be expected.
> > 
> > I mean, there as never a question about that even when dbc gots
> > installed in the begin.
> 
> Sure, if you were just in the time gap mentioned before, that is understood.

Again: I used bacula in no time gap. I used it _bevore_ dbc was
invented. (At least for bacula) So I had have a productive database
before you came up with that dbc idea at all.

> > Well, from the user perspective, I just vote for not overwriting my
> > existing database. I did not get any question about migrating the
> > database. (That was working bevore bacula switched to dbc.)
> 
> Again (except with dpkg-reconfigure) the existing database is never
> overwritten. I believe you are voting for an option during reconfigure
> to turn on upgrades again. I already accepted that as the description of
> this bug.

Well, ok, that sounds opposite to what you told above.

However, I just ask about handling the (not so seldom) usecase that
there _is_ already a productive database.

Bug#449513: axel: crashes when a HTTP 302 redirects it to a FTP location

[Eriberto Mota]

Control: found 449513 2.7-1

Hi,

Currently, it can be reproduced using:

$ axel 
http://ftp.linux.ncsu.edu/pub/CentOS/7.2.1511/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso

I attached a tcpdump capture made with Axel 2.7-1. (to reproduct, #
tcpdump -n host ftp.linux.ncsu.edu -A; to read the attached file #
tcpdumpp -nr  -A)

The attached file is ftp.linux.ncsu.edu-2.pcap.gz

I can see the following sequence:

1. The tcpdump shows the redirection from http://ftp.linux.ncsu.edu to
ftp://ftp.linux.ncsu.edu (HTTP/1.1 301 Moved Permanently).

2. The server sents a FIN and Axel sents a ACK followed by a RST.

3. A new connection from Axel to ftp://ftp.linux.ncsu.edu. Client port
41350. The traffic:

server> _AE220 Welcome to NC State Red Hat Linux and Realm Linux mirror.
client> USER anonymous
server> _Ax331 Please specify the password.
client> PASS mailto:axel@axel.project
server> _A.230 Login successful
client> TYPE I
server> _A.200 Switching to Binary mode
client> CWD //pub/CentOS/7.2.1511/isos/x86_64/
server> _B.250 Directory successfully changed
client> PASV
server> _BB227 Entering Passive Mode (152,1,2,172,255,65)

4. A new connection from Axel without close the last connection. Port 60908:

client> REST 1
server> _B.350 Restart position accepted (1)
client> RETR CentOS-7-x86_64-DVD-1511.iso
server> _B.150 Opening BINARY mode data connection for
CentOS-7-x86_64-DVD-1511.iso (4329570304 bytes)
client> FIN (port 41350)
client> FIN (port 60908)
server> data sent to port 60908
client> RST

5. A new connection from Axel. Port 41352:

server> Still sending data to 60908
client> RST
server> Still sending data to 60908
client> RST
server> Still sending data to 60908 (TCP sliding window?)
client> RST
server> Still sending data to 60908
client> RST
server> Still sending data to 60908
client> RST
[...]
server> _C^220 Welcome to NC State Red Hat Linux and Realm Linux
mirror. (to 41352)
client> USER anonymous (41352)
server> _C.331 Please specify the password
client> PASS mailto:axel@axel.project
server> Still sending data to 60908
client> RST
server> _C.230 Login successful (41352)
client> TYPE I
server> _C.200 Switching to Binary mode
client> CWD //pub/CentOS/7.2.1511/isos/x86_64/
server> 250 Directory successfully changed
client> PASV
server> _BB227 Entering Passive Mode (152,1,2,172,23,196)

6. A new connection from Axel (port 43218)

client> REST 1 (from 41352)
server> 350 Restart position accepted (1) (to 41352)
client> RETR CentOS-7-x86_64-DVD-1511.iso (41352)
server> 150 Opening BINARY mode data connection for
CentOS-7-x86_64-DVD-1511.iso (4329570304 bytes) (41352)
client> FIN (from 41352)
client> FIN (from 43218)
server> data to 43218
client> RST (from 43218)

7. A new connection from Axel (port 41354)

server> data to 43218
client> RST

[similar traffic will occur several times]

8. After several connections, resets and events:

server> 426 Failure writing network stream (to 41356)
client> RST
server> 8500 OOPS
client> RST
server> vsf_sysutil_recv_peek: no data
client> RST
server> anything to client (PSH)
client> RST
server> 8500 OOPS
client> RST
server> child died
client> RST
server> anything to client (PSH)
client> RST
server> FIN
client> RST
server> 8426 Failure writing network stream
client> RST
server> 8426 Failure writing network stream
client> RST

9. Following, a traffic from server to client port 34421:

server> data to client
client> RST
server> 8426 Failure writing network stream
client> RST

10. Server to 41356:

server> 8426 Failure writing network stream
client> RST

11. Server to client 43218:

server> data
client> RST

12. server to client 34421:

server> data
client> RST

13. server to client 41356:

server> 8426 Failure writing network stream
client> RST
server> 8426 Failure writing network stream
client> RST


--

Trying a limited conection:

$ axel -n 1 
http://ftp.linux.ncsu.edu/pub/CentOS/7.2.1511/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso

Segmentation fault

The traffic is very similar: several resets etc. I attached this file:
ftp.linux.ncsu.edu-3.pcap.gz

-

New tests:

1. A test with wget do a download with perfection.

2. The 
http://ftp.linux.ncsu.edu/pub/CentOS/7.2.1511/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso
is redirected to
http://ftp.linux.ncsu.edu/pub/CentOS/7.2.1511/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso,
as seem.

I a new test, the following command works fine:

$ axel 
ftp://ftp.linux.ncsu.edu/pub/CentOS/7.2.1511/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso

So, confirmed: the redirection from HTTP to FTP is broken.

Eriberto


ftp.linux.ncsu.edu-2.pcap.gz
Description: GNU Zip compressed data


ftp.linux.ncsu.edu-3.pcap.gz
Description: GNU Zip compressed data

Bug#825791: caja crashes

[John Paul Adrian Glaubitz]

Control: severity -1 normal
Control: tags -1 unreproducible
Control: tags -1 moreinfo

On 05/30/2016 12:48 AM, shirish शिरीष wrote:
> Dear Maintainer,
> Trying to start caja on the Desktop gives me the following output on the CLI -

Could you please stop filing bugs without verifying first that it's a local
configuration issue, please?

Also, please refrain from filing bugs with severity grave unless you know
what the ramifications are. Filing bug report with "grave" will prevent
a package from migration to testing and if you file a bug report like
that, you should be absolutely sure it's *not* a local issue.

Which it apparently is, because caja works fine here.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#825790: w3m: -cols should work without -dump

[Eric Wong]

Package: w3m
Version: 0.5.3-19
Severity: normal
Tags: upstream

In other words, there should be a way to forcibly wrap long
lines of text when using w3m interactively.

I looked around the source and docs but could not find a
way to do it, but please tell me if I missed something.

This is an accessibility issue as it makes it hard to read some
sites.

For now, I pipe the buffer within (using "|") to another w3m
invocation:

w3m -dump -cols 64 -T text/html


Btw, is upstream still around (their mailing lists are dead) or
is Debian considered upstream?

Thank you for maintaining w3m.

Bug#825791: caja crashes

[shirish शिरीष]

Package: caja
Version: 1.14.1-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
Trying to start caja on the Desktop gives me the following output on the CLI -

[$] caja

(caja:24636): Gtk-WARNING **: Theme parsing error: gtk.css:63:28: The
:prelight pseudo-class is deprecated. Use :hover instead.

(caja:24636): Gtk-WARNING **: Theme parsing error: gtk.css:73:35: The
:prelight pseudo-class is deprecated. Use :hover instead.

Please fix the above issue.

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/2 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 caja depends on:
ii  caja-common   1.14.1-1
ii  desktop-file-utils0.22-1
ii  gvfs  1.28.2-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.22-9
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.1-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.20.5-4
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-1
ii  libglib2.0-data   2.48.1-1
ii  libgtk-3-03.20.5-4
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.3+dfsg1-1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.28.2-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
ii  gstreamer1.0-tools  1.8.1-1
ii  meld3.16.0-1

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#825789: kshisen crashes

[shirish शिरीष]

Package: kshisen
Version: 4:16.04.1-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
Get the following when trying to launch the new kshisen on Debian testing -

[$] kshisen
 [4:10:59]
AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x01
AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
log_libkmahjongg: Using background at
"/usr/share/kmahjongglib/backgrounds/summerfield.svg"
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check: __n (which is 0) >= this->size() (which is 0)
[1]24324 abort (core dumped)  kshisen

Please fix the issue mentioned above.

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/2 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 kshisen depends on:
ii  kdegames-mahjongg-data-kf5  16.04.0-1
ii  libc6   2.22-9
ii  libkf5configcore5   5.22.0-1
ii  libkf5configgui55.22.0-1
ii  libkf5configwidgets55.22.0-1
ii  libkf5coreaddons5   5.22.0-1
ii  libkf5crash55.22.0-1
ii  libkf5dbusaddons5   5.22.0-1
ii  libkf5i18n5 5.22.1-1
ii  libkf5kdegames7 4:16.04.0-1
ii  libkf5kmahjongglib5 16.04.0-1
ii  libkf5widgetsaddons55.22.0-1
ii  libkf5xmlgui5   5.22.0-1
ii  libqt5core5a5.5.1+dfsg-17
ii  libqt5gui5  5.5.1+dfsg-17
ii  libqt5widgets5  5.5.1+dfsg-17
ii  libstdc++6  6.1.1-4

Versions of packages kshisen recommends:
ii  khelpcenter  4:5.4.3-1

kshisen suggests no packages.

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#825788: WishList: Shotwell 0.23.1

[Stephen]

Package: shotwell
Version: 0.22.1-1
Severity: wishlist

Dear Maintainer,

The only reason I'm asking for a newer version rather than biding time
as I usually do, is that a number of bugs are fixed in the upstream
version. To make my argument I'll list them, and let you the Debian
maintainer decide what to do. Thanks for your work, much appreciated!


Shotwell 0.23.1 features a selection of bug bandaids, including a
welcome fix for Facebook integration failure.

Various obsolete snippets of code have been removed, as have references
to Yorba. The About dialog also now links to the new Shotwell website.

Other notable changes in the Shotwell 0.23.1 change-log:

Update Facebook application ID so that Facebook integration works again

Fix for a file monitor issue when renaming an image

New and updated icons, including hi-res and symbolic

“Yorba website” renamed to “Shotwell website” in ‘About’ dialog

Adjust how Shotwell checks whether it runs uninstalled to allow running
with symlinks

Allow the viewer to be closed when there is an issue loading an image

Fix error when no metadata is present in an image

Toolbar now uses GtkOverlay instead of custom pop-up

Critical errors caused by mouse hiding algorithm have been removed


-- Package-specific info:

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

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

Versions of packages shotwell depends on:
ii  dbus-x111.10.8-1
ii  dconf-cli   0.26.0-1
ii  libatk1.0-0 2.20.0-1
ii  libc6   2.22-9
ii  libcairo-gobject2   1.14.6-1+b1
ii  libcairo2   1.14.6-1+b1
ii  libexif12   0.6.21-2
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libgee-0.8-20.18.0-1
ii  libgexiv2-2 0.10.3-2
ii  libglib2.0-02.48.1-1
ii  libgomp16.1.1-4
ii  libgphoto2-62.5.10-2
ii  libgphoto2-port12   2.5.10-2
ii  libgstreamer-plugins-base1.0-0  1.8.1-1
ii  libgstreamer1.0-0   1.8.1-1
ii  libgtk-3-0  3.20.5-4
ii  libgudev-1.0-0  230-3
ii  libjavascriptcoregtk-4.0-18 2.12.3-1
ii  libjson-glib-1.0-0  1.2.0-1
ii  liblcms2-2  2.7-1
ii  libpango-1.0-0  1.40.1-1
ii  libpangocairo-1.0-0 1.40.1-1
ii  libraw150.17.2-1
ii  librest-0.7-0   0.8.0-1
ii  librsvg2-common 2.40.15-1
ii  libsoup2.4-12.54.1-1
ii  libsqlite3-03.13.0-1
ii  libstdc++6  6.1.1-4
ii  libwebkit2gtk-4.0-372.12.3-1
ii  libx11-62:1.6.3-1
ii  libxml2 2.9.3+dfsg1-1
ii  shotwell-common 0.22.1-1

shotwell recommends no packages.

shotwell suggests no packages.

-- no debconf information

Bug#825435: Pending fixes for bugs in the libdbix-dbstag-perl package

[pkg-perl-maintainers]

tag 825435 + pending
thanks

Some bugs in the libdbix-dbstag-perl package are closed in revision
f055085c9c7bee230f9d52ffb4b4692b351e6af6 in branch 'master' by gregor
herrmann

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

Commit message:

Use (file-)rename instead of (p)rename.

Closes: #825435

Bug#825653: New frame in TraditionalOK/Green themes makes main menu hard to click on

[Raphaël Halimi]

Le 29/05/2016 à 22:20, Mike Gabriel a écrit :
> Feedback from upstrean. Please provide screenshots where missing and  
> mark the area of the screenshot you are referencing in your bugs.

Please find two screenshots attached.

Maybe related to the main issue of this bugreport, maybe not.

As mentioned before, with TraditionalOK, there's now an thin grey
outline around mate-terminal when it's maximized, which 1/ wasn't
present with previous versions of TraditionalOK, and 2/ isn't present
with other themes in mate-themes 1.14 (as seen in the Menta screenshot).

Regards,

-- 
Raphaël Halimi


signature.asc
Description: OpenPGP digital signature

Bug#825434: Pending fixes for bugs in the libdata-stag-perl package

[pkg-perl-maintainers]

tag 825434 + pending
thanks

Some bugs in the libdata-stag-perl package are closed in revision
6bee939bbd68c8bc5754765cc3deb7a16b5baa68 in branch 'master' by gregor
herrmann

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

Commit message:

Use (file-)rename instead of (p)rename.

Closes: #825434

Bug#825659: Bug#825669: Most themes lack a border around the title bar on maximized windows

[Raphaël Halimi]

Le 29/05/2016 à 22:20, Mike Gabriel a écrit :
> Feedback from upstrean. Please provide screenshots where missing and  
> mark the area of the screenshot you are referencing in your bugs.

Please find two screenshots attached.

With the Menta theme, there's not separation between the title bar and
the panel. Previous versions of the theme didn't have this problem, and
TraditionalOK/Green don't have this problem either.

Regards,

-- 
Raphaël Halimi


signature.asc
Description: OpenPGP digital signature

Bug#825653: New frame in TraditionalOK/Green themes makes main menu hard to click on

[Raphaël Halimi]

Le 29/05/2016 à 22:20, Mike Gabriel a écrit :
> Feedback from upstrean. Please provide screenshots where missing and  
> mark the area of the screenshot you are referencing in your bugs.

Please find two screenshots attached.

Notice the grey outline around the blue highlighted area in the
TraditionalOK screenshot (I suggest using an image  viewer with a black
background, for example qiv in fullscreen mode). This outline is not
part of the clickable zone, which makes the main menu quite hard to
click on, because when you try to click on the main menu, most clicks
end on the top of the screen.

Menta theme doesn't have this problem; clicking on top the screen
triggers the menu as expected. Notice that said outline is missing in
the Menta screenshot.

Regards,

-- 
Raphaël Halimi


signature.asc
Description: OpenPGP digital signature

Bug#825787: FTBFS: src/Makefile.am: error: required file './depcomp' not found

[Vincent Lefevre]

Source: paps
Version: 0.6.8-7
Severity: serious
Justification: fails to build from source

I get the following error.

zira:...ftware/paps-0.6.8> debuild -i -us -uc -b
 dpkg-buildpackage -rfakeroot -D -us -uc -i -b
dpkg-buildpackage: info: source package paps
dpkg-buildpackage: info: source version 0.6.8-7
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Lior Kaplan 
 dpkg-source -i --before-build paps-0.6.8
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from paps-0.6.8/debian/source/options: 
--extend-diff-ignore=(^|/)(Makefile.in|aclocal.m4|configure|config.h.in|ltmain.sh)$
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp 
# Add here commands to clean up after the build process.
[ ! -f Makefile ] || /usr/bin/make distclean
rm -f config.log doc/libpaps.tag
dh_clean 
 debian/rules build
dh_testdir
# Add here commands to configure the package.
libtoolize -f -c
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: You should add the contents of the following files to 'aclocal.m4':
libtoolize:   '/usr/share/aclocal/libtool.m4'
libtoolize:   '/usr/share/aclocal/ltoptions.m4'
libtoolize:   '/usr/share/aclocal/ltsugar.m4'
libtoolize:   '/usr/share/aclocal/ltversion.m4'
libtoolize:   '/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
/usr/share/aclocal/libstroke.m4:29: warning: underquoted definition of 
smr_ARG_WITHLIB
/usr/share/aclocal/libstroke.m4:29:   run info Automake 'Extending aclocal'
/usr/share/aclocal/libstroke.m4:29:   or see 
http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:4: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.  For more info, see:
configure.in:4: 
http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:7: error: required file './compile' not found
configure.in:7:   'automake --add-missing' can install 'compile'
configure.in:4: error: required file './missing' not found
configure.in:4:   'automake --add-missing' can install 'missing'
src/Makefile.am:17: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
'*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
src/Makefile.am: error: required file './depcomp' not found
src/Makefile.am:   'automake --add-missing' can install 'depcomp'
autoreconf: automake failed with exit status: 1
debian/rules:27: recipe for target 'config.status' failed
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc -i -b failed
zsh: exit 29debuild -i -us -uc -b

-- 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)

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 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)

-- no debconf information

Bug#823870: Upgrade to v1.1.7

[Dima Kogan]

djcj  writes:

> Package: gmsl
> Version: 1.1.5-1
>
> Version 1.1.7 has been released quite a while ago:
> https://sourceforge.net/projects/gmsl/files/GNU%20Make%20Standard%20Library/v1.1.7/
>
> Can you upgrade the package?

I'm waiting to get full DD rights (should be about a month), and will do
the upload then.

Bug#811494: Pending fixes for bugs in the libcam-pdf-perl package

[pkg-perl-maintainers]

tag 811494 + pending
thanks

Some bugs in the libcam-pdf-perl package are closed in revision
83c7c2d156f501d712ec8eed9fc720b0efc9c340 in branch 'master' by gregor
herrmann

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

Commit message:

Add patch to handle decoded paths.

Thanks: Marco Pessotto for the bug report and patch.
Closes: #811494

Bug#825433: Pending fixes for bugs in the libcam-pdf-perl package

[pkg-perl-maintainers]

tag 825433 + pending
thanks

Some bugs in the libcam-pdf-perl package are closed in revision
090be1e53e6424656c658479db2f82daad47c38e in branch 'master' by gregor
herrmann

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

Commit message:

Use (file-)rename instead of (p)rename.

Closes: #825433

Bug#825785: ITP: tab -- Typesetter for lute tablature

[Chris Lamb]

> Should be lute-tab or something like that.

That just seems to be the GitHub repo name, upstream seems to call it "Tab":

 http://www.cs.dartmouth.edu/~wbc/lute/AboutTab.html

.. and the binary is called "tab".

Would you still suggest the "lute" prefix?


Regards,

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

Bug#825394: systemd kill background processes after user logs out

[Renaud Allard]

While I agree that it would be a good idea to kill the non useful 
remaining processes when a users logs out on a desktop or remote session 
server, the new behavior completely beats the purpose of 
nohup/tmux/screen or any user started daemon.


Actually, if a user logs out and some gnome (for example) related 
processes are not killed, this is more a bug which needs to be solved in 
gnome and not on the whole OS. When you quit gnome, gnome needs to 
ensure its own processes it started on login are killed at logout, but 
not anything that doesn't belong to gnome.




smime.p7s
Description: S/MIME Cryptographic Signature

Bug#821391: tomcat8: postinst script overwrites file permissions in /etc

[Markus Koschany]

clone 821391 -1
reassign -1 src:tomcat8
retitle -1 tomcat8: postinst script overwrites file permissions in /etc
thanks

This bug also affects Tomcat 8.


I have prepared another security update and I intend to change the
current behavior in Jessie and Sid for new installations to avoid
similar breakage when upgrading Tomcat 8.

Currently tomcat8.postinst changes file ownership of all files in
/etc/tomcat8 to root:tomcat8. I think this isn't necessary because the
default is to use root:root (rw-r-r) which ensures that all
configuration files can still be read by Tomcat8. The only security
relevant file is /etc/tomcat8/tomcat-users.xml in the default Debian
configuration. I propose to modify only this one by changing the line

chown -Rh root:$TOMCAT8_GROUP /etc/tomcat8/*

to

chown root:$TOMCAT8_GROUP /etc/tomcat8/tomcat-users.xml


This should address the issue.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#825078: Audio over HDMI not working

[Bálint Réczey]

2016-05-29 23:03 GMT+02:00 Erik de Castro Lopo :
> Bálint Réczey wrote:
>
>> Have you checked the suggestions listed here?:
>> http://kodi.wiki/view/PulseAudio
>
> Yes, I did. The problem was not at the PusleAudio level, because ALSA
> did not find the HDMI audio device either.

This sounds like an ALSA/PulseAudio/kernel problem rather than a Kodi one.

Can't do too much when the audio device is not found.

Would you like to share some info about the HW?

Cheers,
Balint

Bug#825078: Audio over HDMI not working

[Erik de Castro Lopo]

Bálint Réczey wrote:

> Have you checked the suggestions listed here?:
> http://kodi.wiki/view/PulseAudio

Yes, I did. The problem was not at the PusleAudio level, because ALSA
did not find the HDMI audio device either.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#809521: Keyboard not working on BananaPI

[Ben Hutchings]

Control: close -1

On Sun, 22 May 2016 17:29:27 +0200 Tobias Frost 
wrote:
> Control: unarchive -1
> Control: reopen -1
> 
> Today, with daily installerimages [1], I tried to install a BananaPi
> and I also run into this.
> 
> However, it seems that the complete usb subsystem was not loaded.
[...]

So it's not actually the same bug.

Ben.

-- 
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump
of a severed limb. - me, 29 June 1999


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

Bug#809488: kodi does not suspend anymore

[Bálint Réczey]

Control: notfound -1 15.2+dfsg1-1

Hi Johannes,

2015-12-31 16:35 GMT+01:00 Johannes Schauer :
> Hi,
>
> Quoting Johannes Schauer (2015-12-31 10:29:22)
>> I used to run Debian Jessie with Mate as a DM with Kodi from backports.
>> With that setup Kodi used to suspend just fine.
>>
>> Now I updated my base system to Squeeze and Kodi doesn't automatically
>> suspend anymore.
>>
>> Maybe connected: the "power" menu at the lower left of the home screen
>> now only shows the options "Exit" and "Inhibit idle shutdown". Before
>> the upgrade I had more options there.
>>
>> Additionally, even when I try to use the Mate automatic suspend on idle
>> options in the power menu, my system will not suspend while Kodi is
>> still running.
>>
>> How can I make my system suspend automatically again with Kodi running
>> in the foreground?
>
> I have no clue about polkit but after searching in the internet it seems that
> doing the following fixes this problem:
>
> $ cat << END | sudo tee 
> /var/lib/polkit-1/localauthority/50-local.d/custom-actions.pkla
> [Actions for kodi user]
> Identity=unix-user:kodi
> Action=org.freedesktop.login1.*;org.freedesktop.udisks2.*
> ResultAny=yes
> ResultInactive=no
> ResultActive=yes
> END
>
> Maybe this helps!
>
> In the worst case I now have documented a solution/workaround for others who
> might also stumble over this problem :)

Thank you for collecting the info here.
It can also be found on Kodi's wiki:
http://kodi.wiki/view/HOW-TO:Suspend_and_wake_in_Ubuntu

I'm closing the bug since there is documentation available for
enabling suspend when it does not work out of the box.

Cheers,
Balint

Bug#825785: ITP: tab -- Typesetter for lute tablature

[Ben Hutchings]

On Sun, 2016-05-29 at 21:36 +0100, Chris Lamb wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Chris Lamb 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: tab

Should be lute-tab or something like that.

Ben.

>   Upstream Author : Wayne Cripps
> * URL : https://github.com/mandovinnie/Lute-Tab
> * License : BSD
>   Programming Lang: C
>   Description : Typesetter for lute tablature
> 
> Tab is a typesetter for lute tablature for renaissance and baroque
> lutes and theorboes, in both French and Italian notation. You edit a
> plain text file with special commands to enter the lute tablature,
> then you run tab to convert that input into PostScript output that
> you can print or display with the right program.
> 
> 
> Regards,
> 
-- 
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump
of a severed limb. - me, 29 June 1999


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

Bug#825078: Audio over HDMI not working

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Erik,

2016-05-23 14:17 GMT+02:00 Erik de Castro Lopo :
> Source: kodi
> Version: 16.1+dfsg1-1
> Severity: normal
>
> After upgrading from kodi-15 to kodi-16, audio over HDMI stopped working
> on my dedicated kodi box.
>
> I spent a *lot* of time debugging this and in the end installed a kodi
> specific linux distro (http://wiki.libreelec.tv/) and everything works.

Have you checked the suggestions listed here?:
http://kodi.wiki/view/PulseAudio

There can be many configuration combinations, thus knowing more
about your setup/audio stream could help in resolving the issue.

Cheers,
Balint

Bug#825785: ITP: tab -- Typesetter for lute tablature

[Chris Lamb]

Package: wnpp
Severity: wishlist
Owner: Chris Lamb 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: tab
  Upstream Author : Wayne Cripps
* URL : https://github.com/mandovinnie/Lute-Tab
* License : BSD
  Programming Lang: C
  Description : Typesetter for lute tablature

Tab is a typesetter for lute tablature for renaissance and baroque lutes and 
theorboes, in both French and Italian notation. You edit a plain text file with 
special commands to enter the lute tablature, then you run tab to convert that 
input into PostScript output that you can print or display with the right 
program.


Regards,

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

Bug#825760: kodi: Crash on startup when connecting to CEC adapter

[Bálint Réczey]

Hi Torsten,

2016-05-29 21:17 GMT+02:00 Torsten Crass :
> OK,
>
> maybe I was a little dumb... The crash symptoms I described in my initial
> report resulted from an attempt to reproduce the problem by remotely calling
> kodi through an ssh connection. I don't know how cec actually interacts with
> an application, but maybe it just didn't feel comfortable with the UI
> running on a different physical machine.
>
> Anyway, when firing up kodi locally on the actual HTPC, the crash on launch
> is caused by an
>
> 21:06:38 T:140259291035840   ERROR: SQL: SQL error or missing database
> Query: SELECT idVersion FROM
> version
>
> So... should I vote for closing this bug and open a new one, or shall we
> proceed under #825760?

I have just uploaded kodi 16.1+dfsg1-1~bpo8+1 to jessie-backports which
is built with latest libcec thus fixes the crash due to the ABI breakage and
probably other bugs.

Please don't open bugs affecting package versions in jessie-backports,
use the backports mailing list for reporting such issues:
https://backports.debian.org/Instructions/#index6h2

OTOH if you can reproduce an issue with packages from testing/unstable only,
please open a bug report in the BTS like this one.

Also note that the packages from deb-multimedia can interfere with packages
from Debian, thus systems having those installed are not supported here.

The kodi-pvr-mythtv package will be available from jessie-backports in
the next weeks.

Cheers,
Balint

Bug#825669: Most themes display sliders indicators overlapping surrounding elements

[Mike Gabriel]

Control: reassign -1 gtk+-3.0
Control: retitle -1 slider issue in MATE themes due to GtkScale bug

On  Sa 28 Mai 2016 17:38:51 CEST, Raphaël Halimi wrote:


Package: mate-themes
Version: 3.20.7-1
Severity: minor
Tags: upstream

Hi,

Since version 3.20 of mate-themes, most themes (not sure about BlackMATE
and ContrastHighInverse) display sliders indicators slightly zoomed in;
they almost always overlap surrounding UI elements when the indicator is
dragged to one of the extremities, as shown in the attached images (on
the mouse preferences one, there are "e"s at the end of both words,
hidden behind the indicators).

Regards,


After detailled looking into this issue by the MATE upstream themes  
developer, I reassign this bug to gtk+-3.0.


```
22:27 <@raveit65> about bug=825669 GtkSlider is broken with gtk+  
itself, reassign it to them , known issue
22:29 <@raveit65> sunweaver, you can  test this whit starting an app  
from terminal and moving the slider to the edge

22:29 <@raveit65> you will see Spam in terminal
22:32 <@raveit65> btw. bug in GtkScale
```

Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgpxGh5o1PAzL.pgp
Description: Digitale PGP-Signatur

Bug#825653: Bug#825669: Bug#825653: New frame in TraditionalOK/Green themes makes main menu hard to click on

[Mike Gabriel]

Hi Raphael,

On  So 29 Mai 2016 20:18:17 CEST, Mike Gabriel wrote:


Hi Raphael,

On  So 29 Mai 2016 15:20:09 CEST, Raphaël Halimi wrote:

[...]


So, all three bug reports I sent yesterday were observed under a
complete MATE 1.14 desktop (including marco).


Ok. Understood. I have just pointed the upstream maintainer of  
mate-themes to your findings. Hope to get some feedback from there.


Mike


Feedback from upstrean. Please provide screenshots where missing and  
mark the area of the screenshot you are referencing in your bugs.


Thanks,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgpd4qIbEiMKa.pgp
Description: Digitale PGP-Signatur

Bug#825784: libinput10: libinput is very choppy with ELAN1000 touchpads since 1.3.0

[Mike Palmer]

Package: libinput10
Version: 1.3.0-2
Severity: normal

Dear Maintainer,

Ever since libinput 1.3.0 my touchpads have been stalling and gotten very 
choppy. After quilting the following patch into the package I was able to get
it working again:

https://lists.freedesktop.org/archives/wayland-devel/2016-May/028932.html

It behaves so poorly if you don't have one of those lenovos, I feel like it 
might be worth quilting the source package in debian until libinput releases 
a fixed version.

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

Kernel: Linux 4.6.0-trunk-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 libinput10 depends on:
ii  libc6 2.22-9
ii  libevdev2 1.5.1+dfsg-1
ii  libinput-bin  1.3.0-2
ii  libmtdev1 1.1.5-1
ii  libudev1  230-1
ii  libwacom2 0.19-1

libinput10 recommends no packages.

libinput10 suggests no packages.

-- no debconf information

Bug#798401: gdb-python2 does not actually link to python2, but python3

[Ben Longbons]

On Sun, May 29, 2016 at 1:59 AM, Hector Oron  wrote:
> Please let me know your gdb-python2 use case, that'd be quite helpful.

I certainly prefer the python3 version most of the time - by this
point, the infelicities of python3 are well understood and fewer in
number than those of python2.

However, remember that it is (to Debian) an RC bug to ship gdb python
scripts that are not compatible with both python2 and python3, so
being able to quickly test both is very important. And outside of
Debian, I need to ship scripts that work with distros that don't have
a python3 gdb. Yes, there's CI, but anything that doesn't get caught
until that late takes a longer cycle to fix.

Ideally, this *should* have been done for Jessie, but instead it got
stuck only with the python2 version instead of allowing both. There
*must* be at least one stable release that supports both; after that
the python2 variant can be removed.

-Ben

Bug#825075: deb-systemd-invoke: incomplete handling of policy-rc.d status codes

[Martin Pitt]

Control: tag -1 pending

Hello Edward,

Edward Allcutt [2016-05-23 12:22 +0100]:
> In particular, where policy-rc.d returns 0 deb-systemd-invoke prints a
> spurious warning. The original spec for policy-rc.d mentioned only 0 as
> the return code for "action allowed" and 104 was added later.
> invoke-rc.d treats 0 the same as 104 and so should deb-systemd-invoke.

Thanks for pointing out! Fixed in git.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#801081: Re: xserver-xorg-video-qxl: QXL video unusable due to performance

[Jason Briggs]

Please include this patch as well:

http://pkgs.fedoraproject.org/cgit/rpms/xorg-x11-drv-qxl.git/plain/qxl-kms-disable-composite.patch

it appear to help with glitches.

Is there any chance these two patch can make it into Jessie? The reason is 
because it affects all jessie live CD and live CD can't be used properly at all 
with KVM/spice, it really break functionality and there is no workaround there 
unless you rebuild the CD. There is still 2 years of life to jessie and all 
downstream suffer.

 On Tue, 24 May 2016 07:26:52 -0400 Jason Briggs  wrote  
>Dear Maintainer:
>
>I need to advise you that the current package in Stretch 
>xserver-xorg-video-qxl 0.1.4-3+b1 is
>***NOT*** fixed
>
>on my Stretch I manually recompile xserver-xorg-video-qxl and applied the 
>following patch:
>
>http://pkgs.fedoraproject.org/cgit/rpms/xorg-x11-drv-qxl.git/plain/no-surfaces-kms.patch
>
>using this patch on the recompile package, the issue no longer happens (when 
>kms enabled).
>
>To be specific, with this patch enabled, even though Xorg.0.log report that 
>surfaces enabled,
>they behave as if disable and all works. This is the same behavior I can see 
>when I ran a Fedora;
>log say enabled but no issue, because in fact disable internally.
>
>I advise please apply the patch above to package (if there is no other patch 
>in works).
>This can't be in the next Debian.
>
>In addition I advise to check other patches listed:
>http://pkgs.fedoraproject.org/cgit/rpms/xorg-x11-drv-qxl.git/tree/
>to see if they fix anything else, such as qxl-kms-disable-composite.patch
>I can confirm there is other issues with QXL driver (other than this bug) with 
>4.x+ kernel such as broken auto-resizing ("Auto Resize VM with Window" broken).
>
>Thank you
>
>
>
>

Bug#799061: open-isns package in Debian

[Christian Seiler]

Hi again,

On 05/27/2016 08:06 PM, Christian Seiler wrote:
> just wanted to ping you again about the open-isns package.

Just FYI: there was a question about getting iscsiuio into
Debian on the pkg-iscsi mailing list today:

http://lists.alioth.debian.org/pipermail/pkg-iscsi-maintainers/2016-May/002101.html

I'd really like to be able to tell users of the open-iscsi
package that I'm actively working on it, but I can't enable
iscsiuio support in open-iscsi until I upgrade it. But I
can't upgrade open-iscsi until open-isns is packaged for
Debian.

Since this has been stalled for the last 8 months, and I
haven't heard any replies from you for over 6 months (I
have pinged you 3 times with months of time in between
the pings), I'm hereby announcing that I'll take over this
ITP if I don't hear anything from you in the next 7 days.
I really don't want to step on your toes, especially since
you said you have already started packaging it; and if I
do take over the ITP, I'll be happy to co-maintain it with
you, but I cannot in good conscience let this stall the
progress on open-iscsi any longer - sorry!

Regards,
Christian

Bug#825783: cyrus-imapd-2.4: Cyrus does not create directory in /var/run

[Dmitry Katsubo]

Package: cyrus-imapd-2.4
Version: 2.4.17+nocaldav-2+b1

Hello,

I have noticed that Cyrus does not create necessary directory in /var/run
when needed. For example, when the following is specified in /etc/imapd.conf

lmtpsocket: /var/run/cyrus/lmtp

the directory /var/run/cyrus is not created, even though Cyrus starts up and
functions ok.

Expected: the directory /var/run/cyrus (or any other necessary top-level
directory) is created or Cyrus complains that directory is not writeable.

Solution: Do it in init.d script (very draft suggestion is attached) or via
/etc/tmpfiles.d/cyrus.conf:

d /var/run/cyrus 0755 cyrus mail

-- 
With best regards,
Dmitry
--- /etc/init.d/cyrus-imapd.orig2015-03-24 12:10:20.0 +0100
+++ /etc/init.d/cyrus-imapd 2016-05-29 21:31:56.947282286 +0200
@@ -61,6 +61,14 @@
 
 SYNC_CLIENT=/usr/lib/cyrus/bin/sync_client
 SYNCSHUTDOWN="$(gawk '/^sync_shutdown_file:[[:blank:]]/ { print $2 }' $CONF)"
+SOCKET="$(gawk '/^lmtpsocket:[[:blank:]]/ { print $2 }' $CONF)"
+
+if [ ! -z "$SOCKET" ]
+then
+   SOCKET_DIR=`dirname $SOCKET`
+   [ -d "$SOCKET_DIR" ] || mkdir -p "$SOCKET_DIR"
+   chown cyrus.mail "$SOCKET_DIR"
+fi
 
 # Load the VERBOSE setting and other rcS variables
 . /lib/init/vars.sh

Bug#806867: python-scipy: FTBFS when built with dpkg-buildpackage -A (No module named scipy)

[Santiago Vila]

> Exception occurred:
>   File "conf.py", line 58, in 
> import scipy
> ImportError: No module named scipy
> The full traceback has been saved in /tmp/sphinx-err-dX0KL_.log, if you want 
> to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> Makefile:87: recipe for target 'html' failed
> make[1]: *** [html] Error 1
> make[1]: Leaving directory '/<>/doc'
> debian/rules:37: recipe for target 'build-indep' failed

This error message suggests that the package build may not be split
into build-arch and build-indep, because the manual needs "python-scipy"
to be present in the system and this is created in the build-arch
target.

My suggestion to fix this would be to make build-arch and build-indep
to depend on build (not the other way around) and build everything in
the build target.

The package will probably not build "optimally", but at least it
should build, and that will always be better than the current FTBFS bug.

Thanks.

Bug#825769: Please add support for MATE desktop

[Lisandro Damián Nicanor Pérez Meyer]

tag 825769 pending
thanks

On Sunday 29 May 2016 19:03:52 Raphaël Halimi wrote:
> Package: qt4-x11
> Version: 4:4.8.7+dfsg-7
> Severity: wishlist
> Tags: upstream patch
> 
> Hi,
> 
> Qt4 applications are smart enough to detect when they're run under GNOME
> or XFCE, and use the GTK+ theme unless configured otherwise, thanks to a
> bunch of tests that determine which desktop the application is running on.
> 
> Unfortunately, these tests don't include the MATE desktop; Qt5 does
> include such a test, but a lot of applications still use Qt4 (for
> example, on my system, I have avidemux, bitcoin-qt, clementine, and
> skype which depend on Qt4 libs).
[snip]

Considering that Qt4 is dead upstream I can't forward it. Moreover the patch 
is simple and self-contained, so I think it's OK to have this delta.

Patch applied, it will be included int he next upload.

Thanks for the patch!

-- 
Those are my principles. If you don't like them I have others.
 -- Groucho Marx

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#825305: hints on the gthumb gconf2->gsettings convertion issue

[Andreas Henriksson]

Hello Herbert Fortes.

Hopefully I can help out with the information you need.

The debian pkg gthumb-data built from src:gthumb contains the convertion
file:
https://sources.debian.net/src/gthumb/3:3.4.3-1/data/gthumb.convert/

Among other things this file specifies the gconf2 key called
"show-thumbnails" should be mapped to "org.gnome.gthumb.browse
show-thumbnails" gsettings schema key.

The gsettings schema for gthumb on the other hand also shipped declares
that no such key exists in the schema, see:
https://sources.debian.net/src/gthumb/3:3.4.3-1/data/org.gnome.gthumb.gschema.xml.in/#L48

My guess is that it has simply been removed and the convertion mapping
forgotten to be upgraded when doing so...
This suspicion was quickly confirmed by looking at your git history:
https://anonscm.debian.org/cgit/collab-maint/gthumb.git/commit/data/org.gnome.gthumb.gschema.xml.in?id=485570d6cbd5cbc5a9026acc31ba9f108e9e998b

I'd strongly suggest you simply stop shipping the (outdated/broken)
gconf2 convertion file in the debian pkg since all users of old gthumb
versions using gconf2 should have been uograded and converted over to
gsettings long ago already.
I'd also urge you to contact gthumb uostream to have them remove the
convertion file (or fix it if they think there are still remaining users
that need to be converted).

Hope thus helps clear out the confusion.

Regards,
Andreas Henriksson

Bug#825735: Bacula director does not start silently due to database mismatch

[Paul Gevers]

Control: retitle -1 enable setting dbc_install during reconfigure
Control: severity -1 minor

Hi Klaus,

On 27-05-16 14:34, Klaus Ethgen wrote:
>> I am not sure if you are now talking about the current upgrade. If you
>> are than that is correct, you didn't get the question because you had
>> dbc_install=false. If you are talking about "ever" than something
>> clearly failed during the migration.
> 
> True, with upgrade I did not get any question.
> 
> I got this (and only this) question when using dpkg-reconfigure.

Sure, but dpkg-reconfigure will never apply upgrades from the past
because it only applies the upgrades that are needed from YOUR old
version to the current version. As the old version and the current
version are the same, that would not make sense. dpkg-reconfigure
can sensibly only recreate the database from scratch or leave it alone.
So dpkg-reconfigure is the wrong solution to the problem.

>> As bacula migrated to
>> dbconfig-common support for their MySQL and PostgreSQL databases way
>> before that time (in 2006), I suspect you got the old (install) question
>> and this would explain why you haven't seen the question in mentioned in
>> my previous e-mail.
> 
> Well, I do not know how long, but I use bacula for really long time now.
> I have file dates up to begin of 2009 but using bacula much longer.

Well, the bacula SQLite switch was done in version 3.0.3-3 (8 Feb 2010),
so if you were following closely (have you always run your bacula on
unstable), you may have been just in between.

>>> And that might be the problem.
> 
>> Why?
> 
> Well, I want to use the upgrade but not the install of a new database.

Well, that is a uncommon situation, so you currently need to do some
manual action, i.e. a change in a configuration file. The point of
confusion may be that database install in dbconfig-common only means
initial install and possibly during reconfigure. Any other moment,
dbconfig-common is not going to install anything, definitely not during
upgrades.

>>> There was never a question about update.
> 
>> As explained, with dbc_install=false that is to be expected.
> 
> I mean, there as never a question about that even when dbc gots
> installed in the begin.

Sure, if you were just in the time gap mentioned before, that is understood.

> Well, from the user perspective, I just vote for not overwriting my
> existing database. I did not get any question about migrating the
> database. (That was working bevore bacula switched to dbc.)

Again (except with dpkg-reconfigure) the existing database is never
overwritten. I believe you are voting for an option during reconfigure
to turn on upgrades again. I already accepted that as the description of
this bug.

>> The question it stands for is, "do you want dbconfig-common to manage
>> the database on behalf of ${pkg}". And as already noted, the question
>> that is actually asked has been changed more than 6 years ago.
> 
> Well, it asked to purge my existing database.

I assume you are talking about the reconfigure situation. That is
designed behavior.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#822083: refcard: The refcard layout is screwed up for RTL languages

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> Holger Wansing  wrote:
> > Omer Zak  wrote:
> > > 1. Explanations of the changes:
> > > 
> > > debian/rules
> > > LC_ALL=en_US.utf8
> > > Fixes the behavior of 'grep' when it deals with text with non-Latin
> > > characters.
> > > Without this change, 'grep' outputs 'Binary file _ matches', 
> > > causing
> > > further operations in the build to fail.
[...]
> > I'm lacking the skills to value this patch, so could please someone comment
> > on it? 
> 
> Are there any objections against me committing that parts of the patch,
> which are related to Hebrew?
> Since I have no proofreader for Arabic until now, I feel somewhat 
> uncomfortable
> with applying changes to Arabic ATM.
> 
> 
> Holger

I should have mentioned explicitly, that Omer proposed to change the global 
build variables in debian/rules, so that might affect all languages!

Are there any known side effects or objections on adding 
LC_ALL=en_US.utf8
to the used environment variables for building refcard?


I could not see any difference while testing the proposed chagings though.



Holger



-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#825760: kodi: Crash on startup when connecting to CEC adapter

[Torsten Crass]

OK,

maybe I was a little dumb... The crash symptoms I described in my 
initial report resulted from an attempt to reproduce the problem by 
remotely calling kodi through an ssh connection. I don't know how cec 
actually interacts with an application, but maybe it just didn't feel 
comfortable with the UI running on a different physical machine.


Anyway, when firing up kodi locally on the actual HTPC, the crash on 
launch is caused by an


21:06:38 T:140259291035840   ERROR: SQL: SQL error or missing database
Query: SELECT idVersion 
FROM version


So... should I vote for closing this bug and open a new one, or shall we 
proceed under #825760?


Regards --

Torsten

Bug#825394: systemd kill background processes after user logs out

[John Brooks]

On Sun, 29 May 2016 11:46:36 +0200 Guus Sliepen  wrote:
> I'm sure the majority of users couldn't care less either way. What we
> have to think about is: does the minority of people who really want this
> feature (for example, because you want your homedir to be locked
> whenever possible) outweigh the minority of people who really don't
> want this feature (because they lose time/work when their processes get
> killed unexpectedly)?

Actually, I think this would be of concern to anyone who uses screen or 
tmux to manage their sessions and/or run background processes (not 
limited to screen/tmux either). It may be a minority, but I'm sure it's 
a significant amount of people. Most of them wouldn't be following this 
news or posting here, however. As for whether which group of people is 
right, I think the principle of least surprise decides that easily; the 
people who want it can enable it manually, and the people that don't can 
continue operating as they have always done without having to be aware 
of this.


On Sun, 29 May 2016 11:13:32 +0200 Martin Pitt  wrote:
> I believe this *is* it the expected thing to do
> on personal computers. This is certainly different in environments
> like universities where one often does put long-running stuff in the
> background, but this doesn't appeal to me as being the behaviour to
> optimize for. At the moment I'm not sure whether this bug report and
> the followups are just a vocal minority or somewhat representative of
> Debian's user (I lean towards the former).

Most Debian installations (derivatives notwithstanding) are on servers, 
not workstations. I think it's a safe assumption that most of them would 
prefer that the system behaves in a way that is optimal for the server 
use case.

Bug#825782: libpam-modules: pam_umask man documentation is wrong

[Pat]

Package: libpam-modules
Version: 1.1.8-3.1+deb8u1+b1
Severity: minor

Dear Maintainer,

The description of 'man pam_umask' is completely wrong. It says the following:

"
The PAM module tries to get the umask value from the following places
   in the following order:

   ·   umask= argument

   ·   umask= entry in the user's GECOS field

   ·   UMASK= entry from /etc/default/login

   ·   UMASK entry from /etc/login.defs
"

It is not this order at all. I tested experimentally and the real order of
checking is this:

1. umask= entry in the user's GECOS field
2. umask= argument (to pam_umask.so)
3. UMASK entry from /etc/login.defs
4. UMASK= entry from /etc/default/login

such that GECOS has top priority and /etc/default/login is almost useless.

I checked the pam_umask source code and it confirm my experiment:

"
  /* Parse parameters for module [ this is umask= arg] */
  for ( ; argc-- > 0; argv++)
parse_option (pamh, *argv, options);

  if (options->umask == NULL)
options->umask = search_key (LOGIN_DEFS);
  if (options->umask == NULL)
options->umask = search_key (LOGIN_CONF);
"
[ and GECOS override all this later ]


Thank you









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

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

Versions of packages libpam-modules depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libaudit1  1:2.4-1+b1
ii  libc6  2.19-18+deb8u4
ii  libdb5.3   5.3.28-9
ii  libpam-modules-bin 1.1.8-3.1+deb8u1+b1
ii  libpam0g   1.1.8-3.1+deb8u1+b1
ii  libselinux12.3-2

libpam-modules recommends no packages.

libpam-modules suggests no packages.

-- debconf information excluded

Bug#825781: libgit2: FTBFS on kfreebsd* and hurd-i386: testsuite problems

[Andreas Beckmann]

Source: libgit2
Version: 0.24.1-2
Severity: important

Hi,

the current version of libgit2 FTBFS on !linux:
https://buildd.debian.org/status/fetch.php?pkg=libgit2=hurd-i386=0.24.1-2=1462259730
https://buildd.debian.org/status/fetch.php?pkg=libgit2=kfreebsd-amd64=0.24.1-2=1460548701
https://buildd.debian.org/status/fetch.php?pkg=libgit2=kfreebsd-i386=0.24.1-2=1460548603

If that is not trivially fixable, please request decrufting of the
outdated binary packages.


Andreas

Bug#825780: opensc: FTBFS on kfreebsd: #error "Don't know how to handle user consent in this (rare) Operating System"

[Andreas Beckmann]

Source: opensc
Version: 0.16.0~rc2-1
Severity: important

Hi,

opensc FTBFS on kfreebsd-*, but previous versions built there:
https://buildd.debian.org/status/fetch.php?pkg=opensc=kfreebsd-amd64=0.16.0~rc2-1=1464411154

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. 
-DOPENSC_CONF_PATH=\"/etc/opensc/opensc.conf\" -I../../src -Wdate-time 
-D_FORTIFY_SOURCE=2 -DPKCS11_THREAD_LOCKING -pthread -I/usr/include/PCSC 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -Wno-unused-parameter 
-Werror=declaration-after-statement -c card-dnie.c  -fPIC -DPIC -o 
.libs/card-dnie.o
card-dnie.c: In function 'dnie_ask_user_consent':
card-dnie.c:340:2: error: #error "Don't know how to handle user consent in this 
(rare) Operating System"
 #error "Don't know how to handle user consent in this (rare) Operating System"
  ^
Makefile:723: recipe for target 'card-dnie.lo' failed


If that bug is not trivially fixable, please request decrufting
of the outdated binary packages.


Andreas

Bug#825768: Acknowledgement (libavcodec-ffmpeg56 : Depends: libx265-59 (>= 1.7) but it is not installable [home.experiatis.com])

[Jaoued Zahraoui]

thank you very much for your help.


Jaoued Zahraoui
0618021128
jzahra...@gmail.com
Mon CV : http://www.doyoubuzz.com/zahraoui-jaoued
Mes liens :


2016-05-29 19:06 GMT+02:00 Debian Bug Tracking System :
> Thank you for filing a new Bug report with Debian.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Multimedia Maintainers 
> 
>
> If you wish to submit further information on this problem, please
> send it to 825...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 825768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825768
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#825779: RM: cpqarrayd [armel armhf mips mipsel s390x] -- ANAIS; restricted to amd64 i386

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

Maintainer restricted the arch list to amd64 i386


Andreas

Bug#825324: byobu: Byobu session closes on SSH disconnect

[Alex Chernyakhovsky]

tags 825324 -moreinfo -unreproducible
tags 825324 wontfix
thanks

Marking as wontfix as this is an issue due to tmux/screen and systemd
interactions, discussed in #825394.

On Thu, May 26, 2016 at 2:17 AM, Ivan Frimmel  wrote:
> HI .. Thanks for your quick response. TBH .. I didn’t know where to
> start. It looks like nohup and screen are doing the same thing. And
> its only recent. I created a brand new user - enabled byobu and ran
> something simple .. disconnect .. and the session closes completely.
>
> Screen sadly does the same thing from what I can see. Just to repeat -
> byoby/screen and nohup  are all doing it - I love Byobu - so this is
> my first port of call ! :) ( please be gentle ) ..
>
> executing nohup /usr/bin/python /foo/pythonthing.py &  works fine
> while I am connected and then instantly terminates on disconnect of
> the SSH. It is only very recent. And I don't think its anything I
> did..
>
> the baffling thing is that ROOT is unaffected by this disconnection ..
> I wonder if their isn’t some new permission being pushd that makes
> persistence a "option ?" seems silly to do that.
>
> Please help!
> Tx
> Ivan.
>
>
>
>
> -Original Message-
> From: Alex Chernyakhovsky [mailto:acher...@mit.edu]
> Sent: Thursday, May 26, 2016 1:46 AM
> To: Ivan Frimmel ; 825...@bugs.debian.org
> Cc: Debian Bug Tracking System ; 
> cont...@bugs.debian.org
> Subject: Re: Bug#825324: byobu: Byobu session closes on SSH disconnect
>
> tags 825324 moreinfo unreproducible
> thanks
>
> Hi Ivan,
>
> Did your apt-get dist-upgrade include an update to tmux and/or screen?
> byobu has not been pushed to sid or stretch recently, so I do not see
> how it can be at fault. It is likely that some change in the
> underlying tmux and/or screen backend you are using has changed. Try
> `tmux list-sessions` or `screen -ls` depending on which byobu backend
> you are using (tmux is currently the default) to see if the sessions
> are present. Additionally, please try reproducing with tmux/screen
> directly, without byobu.
>
> Sincerely,
> -Alex
>
>
> On Thu, May 26, 2016 at 1:19 AM, Ivan Frimmel  wrote:
>> Package: byobu
>> Version: 5.87-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where
>> appropriate ***
>>
>>* What led up to the situation?
>> Did a apt-get dist-upgrade
>>* What exactly did you do (or not do) that was effective (or
>>  ineffective)?
>> root sessions will persist for some reason, but regular account 
>> sessions that used to allow disconnect of ssh now terminate immediately on 
>> disconnect and do not persist at all. I am not sure if byobu is crashing, I 
>> looked for dump files but here arent any that I can see.
>>* What was the outcome of this action?
>> I can't fix the problem. I searched all the byobu an bash 
>> documentation and /etc/profile and /etc/skel etc and I can't find anything 
>> that would be causing this all of a suddent. I don't think it's anything I 
>> did specifically.
>>* What outcome did you expect instead?
>> The sessions would persist after ssh disconnect.
>> *** End of the template - remove these template lines ***
>>
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.5.0-2-amd64 (SMP w/8 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 byobu depends on:
>> ii  debconf [debconf-2.0]  1.5.59
>> ii  gawk   1:4.1.3+dfsg-0.1
>> ii  gettext-base   0.19.7-2
>> ii  python 2.7.11-1
>> ii  python-newt0.52.18-3
>> ii  screen 4.3.1-3
>> ii  tmux   2.2-2
>>
>> Versions of packages byobu recommends:
>> pn  run-one  
>> ii  screen   4.3.1-3
>> ii  tmux 2.2-2
>>
>> Versions of packages byobu suggests:
>> pn  apport  
>> pn  ccze
>> ii  lsb-release 9.20160110
>> ii  po-debconf  1.0.19
>> pn  ttf-ubuntu-font-family  
>> pn  update-notifier-common  
>> pn  vim 
>> ii  w3m 0.5.3-28
>> pn  wireless-tools  
>>
>> -- debconf information:
>>   byobu/launch-by-default: false

Bug#825778: [INTL:da] Danish translation of the template adduser

[Joe Dalton]

Package: adduser
Severity: wishlist
Tags: l10n patch

Please include the attached Danish adduser translation

joe@pc:~/over/debianp/adduser$ msgfmt --statistics -c -v -o /dev/null da.po
da.po: 114 oversatte tekster.

bye
Joe

Bug#825774: RM: ejabberd [m68k sh4] -- ROM; hopelessly outdated

[Scott Kitterman]

On Sunday, May 29, 2016 08:12:45 PM Philipp Huebner wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> The ejabberd package for m68k and sh is hopelessly outdated and this is
> unlikely to change.
> Please remove it from the archive.

Ports architectures are not maintained by the FTP team.  

Scott K 

Bug#825776: logrotate: Sometimes files are skipped during weekly rotation.

[Kees Theunissen]

Package: logrotate
Version: 3.8.7-1+b1
Severity: normal
Tags: upstream patch

Dear Maintainer,

Sometimes files are not rotated during weekly logrotation, despite of
the fact that the last rotation was a week ago (within a few seconds).
This bugs seems to be introduced in Debian Jessie.

Debian Wheezy stored only the date of the last rotation in the
logrotate status file (/var/lib/logrotate/status) like:
  "/var/log/syslog" 2016-5-29
The "hour", "minutes" and "seconds" were initialized as 0 when the
status file was read. This pins the timestamp of the last rotation
effectively at 12:00:00 AM.

Debian Jessie stores the full date and time:
  "/var/log/syslog" 2016-5-29-6:25:4
and checks for weekly rotation if the last rotation was more than
(7 * 24 * 3600) seconds ago.
This check fails occasionally due to some jitter in the exact moment
that logrotate is started.

The patch below should fix this. (untested)

$ diff -u logrotate.c.original logrotate.c
--- logrotate.c.original2016-05-29 17:32:06.954792359 +0200
+++ logrotate.c 2016-05-29 17:39:56.674758835 +0200
@@ -856,12 +856,13 @@
   1) the current weekday is before the weekday of the
   last rotation
   2) more then a week has passed since the last
-  rotation */
+  rotation. Allow some jitter in the time - 60 seconds
+  should be sufficient and harmless. */
state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday)
   ||
   ((mktime() -
 mktime(>lastRotated)) >
-   (7 * 24 * 3600)));
+   (7 * 24 * 3600 - 60)));
break;
case ROT_HOURLY:
state->doRotate = ((now.tm_hour != state->lastRotated.tm_hour) ||



Regards,

Kees Theunissen.



-- Package-specific info:
Contents of /etc/logrotate.d
total 32
-rw-r--r-- 1 root root 173 Apr 13  2015 apt
-rw-r--r-- 1 root root  79 Nov  8  2014 aptitude
-rw-r--r-- 1 root root 382 Mar 10 05:06 clamav-daemon
-rw-r--r-- 1 root root 409 Mar 10 05:06 clamav-freshclam
-rw-r--r-- 1 root root 139 Jan 15  2014 clamav-unofficial-sigs
-rw-r--r-- 1 root root 232 Apr 10  2015 dpkg
-rw-r--r-- 1 root root 140 Oct 16  2014 mimedefang
-rw-r--r-- 1 root root 515 Oct  2  2014 rsyslog


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 logrotate depends on:
ii  base-passwd 3.5.37
ii  cron [cron-daemon]  3.0pl1-127+deb8u1
ii  libacl1 2.2.52-2
ii  libc6   2.19-18+deb8u4
ii  libpopt01.16-10
ii  libselinux1 2.3-2

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20141216cvs-2

logrotate suggests no packages.

-- no debconf information

Bug#825777: [INTL:da] Danish translation adduser manual

[Joe Dalton]

Package: adduser
Severity: wishlist
Tags: l10n patch

Please include the attached Danish adduser manual translation.

joe@pc:~/over/debianm/adduser$ msgfmt --statistics -c -v -o /dev/null da.po
da.po: 231 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#825653: New frame in TraditionalOK/Green themes makes main menu hard to click on

[Mike Gabriel]

Hi Raphael,

On  So 29 Mai 2016 15:20:09 CEST, Raphaël Halimi wrote:

[...]


So, all three bug reports I sent yesterday were observed under a
complete MATE 1.14 desktop (including marco).


Ok. Understood. I have just pointed the upstream maintainer of  
mate-themes to your findings. Hope to get some feedback from there.


Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgp2zTRa4zzM5.pgp
Description: Digitale PGP-Signatur

Bug#807553: Could you possibly provide the init scripts?

[Steffen Möller]

Hi Franz,

somehow I am still shying off a bit from providing the init scripts for
alfred and friends. The link you provide is stale now. If you happen to
have something fancy available that with a chance is already tested then
I would add it to the package.

Cheers,

Steffen

Bug#825775: RM: ejabberd-contrib [arm64 sh4] -- ROM; obsolete

[Philipp Huebner]

Package: ftp.debian.org
Severity: normal

ejabberd-contrib has become arch: all quite some time ago.
Please remove these leftovers.

Bug#825768: libavcodec-ffmpeg56 : Depends: libx265-59 (>= 1.7) but it is not installable [home.experiatis.com]

[Bálint Réczey]

Dear Jaoued,

2016-05-29 19:02 GMT+02:00 Jaoued ZAHRAOUI :
> Package: libavcodec-ffmpeg56
> Version: 2.8.6-1~bpo8+1
> Severity: important
>
> Dear Maintainer,
>
> impossible to install this package due to dependencie libx265-59 missing.
> by the way, libx265-79 is avalaible.

Please report bugs that you found in the jessie-backports packages to the
backports mailing list and _not_ to the Debian BTS:
https://backports.debian.org/Instructions/#index6h2

FFmpeg 3.x just been accepted to jessie-backports and I have already
uploaded Kodi 16.1 which package most probably pulled the uninstallable
libavcodec for you.

Everything will install properly when the latest kodi package gets accepted.

Cheers,
Balint

Bug#825774: RM: ejabberd [m68k sh4] -- ROM; hopelessly outdated

[Philipp Huebner]

Package: ftp.debian.org
Severity: normal

The ejabberd package for m68k and sh is hopelessly outdated and this is
unlikely to change.
Please remove it from the archive.

Bug#825668: Firefox memory reporting

[Pavon]

Another clue that I have seen is that Firefox has been reporting a negative 
value for the heap-texture memory use. I don't know if this indicates a bug in 
Firefox's managing of that memory, it's reporting of that memory, or of Xorg's 
managing of that memory which is just being exposed by Firefox. I have noticed 
that Xorg's memory does grow even when Firefox is not running as shown in the 
idle logs in my original post. I haven't been able to keep the computer idle 
for more than a day to see how bad the problem gets in that situation.

3,530.59 MB (100.0%) -- explicit
├──2,136.22 MB (60.51%) -- window-objects
│ ├958.44 MB (27.15%) ++ top(, id=1851)
│ ├673.34 MB (19.07%) ++ (429 tiny)
│ ├177.67 MB (05.03%) ++ top(none)
│ ├138.30 MB (03.92%) ++ top(, id=3408)
│ ├─97.81 MB (02.77%) ++ top(, id=2247)
│ ├─47.99 MB (01.36%) ++ top(, id=2725)
│ └─42.67 MB (01.21%) ++ top(, id=728)
├──1,862.17 MB (52.74%) ── heap-unclassified
├494.26 MB (14.00%) ++ js-non-window
├─96.45 MB (02.73%) ++ heap-overhead
├─43.69 MB (01.24%) ++ xpconnect
└──-1,102.20 MB (-31.22%) -- (22 tiny) [?!]
├──29.89 MB (00.85%) ++ workers
├──27.46 MB (00.78%) ++ images
├──22.72 MB (00.64%) ++ atom-tables
├──20.70 MB (00.59%) ++ storage
├──17.34 MB (00.49%) ++ media
├──17.15 MB (00.49%) ++ add-ons
├──12.33 MB (00.35%) ++ network
├───7.98 MB (00.23%) ++ dom
├───2.25 MB (00.06%) ++ cycle-collector
├───1.79 MB (00.05%) ++ layout
├───1.03 MB (00.03%) ── xpti-working-set
├───0.72 MB (00.02%) ── cookie-service
├───0.69 MB (00.02%) ── history-links-hashtable
├───0.58 MB (00.02%) ── preferences
├───0.51 MB (00.01%) ++ xpcom
├───0.45 MB (00.01%) ── icu
├───0.43 MB (00.01%) ++ webgl
├───0.34 MB (00.01%) ── telemetry
├───0.26 MB (00.01%) ++ startup-cache
├───0.13 MB (00.00%) ── script-namespace-manager
├───0.00 MB (00.00%) ── spell-check
└──-1,266.96 MB (-35.89%) -- gfx [?!]
├───7.95 MB (00.23%) ── font-shaped-words
├───0.42 MB (00.01%) ── font-tables
├───0.26 MB (00.01%) ── font-cache
├───0.09 MB (00.00%) ── font-list
├───0.08 MB (00.00%) ── font-charmaps
└──-1,275.77 MB (-36.13%) ── heap-textures [?!]

Bug#825773: libsodium: Old libsodium in your distro corrupts data when encrypt/decrypt buffers overlap

[Glenn Fiedler]

Package: libsodium13
Version: 1.0.0-1
Severity: important
File: libsodium

Dear Maintainer,

The version of libsodium you install on Debian is out of date. The current 
version supports overlapping encrypt and decrypt buffers (e.g. encrypt and 
decrypt in place),
but when this is attempted with the version that is installed in Debian it 
corrupts the buffer on decrypt (without noting any error). This has wasted an 
incredible amount
of time, and all future users of Debian are likely to encounter this same 
issue, because they expect overlapping decrypt/encrypt buffers to work 
(per-documentation).

Please package up a newer version of libsodium with the support for overlapping 
buffers, else users of libsodium on Debian are going to be scratching their 
heads
and wasting time with an advertised feature that works everywhere else, but 
corrupts data on debian after compressing and decompressing it.

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

Kernel: Linux 4.1.5-x86_64-linode61 (SMP w/2 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 libsodium13:amd64 depends on:
ii  libc6  2.19-18+deb8u4
ii  multiarch-support  2.19-18+deb8u4

libsodium13:amd64 recommends no packages.

libsodium13:amd64 suggests no packages.

-- no debconf information

Bug#715507: axel: VERY often: segmentation fault core dumped

[Eriberto Mota]

Hi,

The bug description is very very very incomplete and gerenic.

Axel is working good for all users. So, the problem should be a local
behavior caused by a problematic environment.

Considering the non explaination about the problem and this bug was
openned a long time ago, I am close this issue. Feel free to reopen it
if needed, supplying some information about how to reproduce the
problem.

Regards,

Eriberto

Bug#825772: seems to ignore SIGHUP sometimes/somehow

[Joey Hess]

Package: alpine
Version: 2.20+dfsg1-2
Severity: normal

I have a server with some users who ssh in to run alpine, and often find
alpine processes left behind after the users have presumably closed
their terminal window or perhaps shut off their computer.
I'm quite sure these nontchnical users are not using nohup to run alpine
or somehing like that. It could be that alpine is crashing somehow and
they're closing the window; they have not said.

(I realize systemd is in the process of fixing this problem erm,
comprehensively, but it still seems worth reporting. My server has run
out of memory partly because of this at least once.)

Glancing at the code, it seems alpine does in
fact catch SIGHUP for some reason. It looks like it can call
signal(SIGHUP, SIG_IGN) in some circumstances.

Attaching gdb to such a process, I got this backtrace:

#0  __lll_lock_wait_private ()
at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7efec3fa6d82 in __tz_convert (timer=0x7efec429cb20 , 
timer@entry=0x7fff278a4f58, use_localtime=use_localtime@entry=1, 
tp=tp@entry=0x7efec429f560 <_tmbuf>) at tzset.c:623
#2  0x7efec3fa5411 in __GI_localtime (t=t@entry=0x7fff278a4f58)
at localtime.c:42
#3  0x005db4d2 in debug_time (include_date=include_date@entry=1, 
include_subseconds=0) at debugtime.c:52
#4  0x005bcb51 in pine_mail_actually_close (stream=0x129f620)
at stream.c:1351
#5  0x004cd014 in fast_clean_up () at signal.c:370
#6  0x004cd10e in hup_signal () at signal.c:244
#7  
#8  0x7efec3fd76d5 in __GI___xstat (vers=, 
name=0x7efec406295c "/etc/localtime", buf=0x7fff278a5630)
at ../sysdeps/unix/sysv/linux/wordsize-64/xstat.c:35
#9  0x7efec3fa6fdc in __tzfile_read (
file=file@entry=0x7efec406295c "/etc/localtime", extra=extra@entry=0, 
extrap=extrap@entry=0x0) at tzfile.c:161
#10 0x7efec3fa6a39 in tzset_internal (always=, 
explicit=explicit@entry=1) at tzset.c:443
#11 0x7efec3fa6dab in __tz_convert (timer=timer@entry=0x7fff278a5768, 
use_localtime=use_localtime@entry=1, tp=tp@entry=0x7efec429f560 <_tmbuf>)
at tzset.c:628
#12 0x7efec3fa5411 in __GI_localtime (t=t@entry=0x7fff278a5768)
at localtime.c:42
#13 0x7efec3fa5369 in ctime (t=t@entry=0x7fff278a5768) at ctime.c:27
#14 0x005db46b in debug_time (include_date=include_date@entry=0, 
include_subseconds=include_subseconds@entry=1) at debugtime.c:63
#15 0x00559c3c in add_review_message (
message=message@entry=0xaf1380  "- completely_done_with_adrbks -\n", 
level=level@entry=1) at help.c:342
#16 0x005e1ac3 in output_debug_msg (dlevel=dlevel@entry=1, 
fmt=fmt@entry=0x7add41 "read_bail: cleaning up\n") at debuging.c:324
#17 0x005e6cd5 in read_bail () at termin.unx.c:579
#18 0x0050a9f4 in simple_ttgetc (
recorder=recorder@entry=0x5e6730 , 
bail_handler=bail_handler@entry=0x5e6cc0 ) at tty.c:157
#19 0x005e68e8 in pine_simple_ttgetc (
fi=0x5e6730 , fv=0x5e6cc0 )
at termin.unx.c:660
#20 0x00507509 in kbseq (
getcfunc=getcfunc@entry=0x5e6870 , 
recorder=recorder@entry=0x5e6730 , 
bail_handler=bail_handler@entry=0x5e6cc0 , 
data=0x7b3de8 , ch=ch@entry=0x7fff278a59dc)
at getkey.c:359
#21 0x005e7055 in read_char (time_out=time_out@entry=8)
at termin.unx.c:342
#22 0x005e476c in read_command (
utf8str=utf8str@entry=0x7fff278a5aa8) at termin.gen.c:116
#23 0x00497147 in scrolltool (
sparms=sparms@entry=0x7fff278a5bc0) at mailview.c:2606
#24 0x0049939d in mail_view_screen (ps=0x12845c0)
at mailview.c:445
#25 0x0040a0d5 in main (argc=, 
ut>) at alpine.c:1336

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

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

Versions of packages alpine depends on:
ii  libc6 2.22-9
ii  libgssapi-krb5-2  1.13.2+dfsg-5
ii  libkrb5-3 1.13.2+dfsg-5
ii  libldap-2.4-2 2.4.42+dfsg-2+b2
ii  libpam0g  1.1.8-3.2
ii  libssl1.0.2   1.0.2h-1
ii  libtinfo5 6.0+20160319-1
ii  mlock 8:2007f~dfsg-4+b1

Versions of packages alpine recommends:
ii  alpine-doc  2.20+dfsg1-2

Versions of packages alpine suggests:
ii  aspell  0.60.7~20110707-3+b1
ii  postfix [mail-transport-agent]  3.1.0-3

-- no debconf information

-- 
see shy jo

Bug#825283: apt-listbugs: misses bug with affects

[Francesco Poli]

On Sat, 28 May 2016 22:45:36 +0200 Vincent Lefevre wrote:

> On 2016-05-28 13:25:37 +0200, Francesco Poli wrote:
[...]
> > Except that stable and oldstable systems do have RC bugs, regardless of
> > what they are supposed to have.
> > I think that ignoring them would be plain arbitrary...
> 
> This is contradictory to what you said above. The fact is that
> handling "affects" is useful for unstable.

No, it's not contradictory.
I have not said that handling "affects" would only be useful for
unstable.
I think that handling the "affects" field would be useful for any
apt-listbugs user (regardless of the Debian distribution he/she is
running), but *only*:

 • if there were a way to distinguish between scenario 0 and scenario 1

 • if there were version tracking info associated with the "affects"
   field in scenario 1

Until these conditions are met (or another distinct way to express
scenario 1 is implemented in the BTS), I cannot think of a way to
usefully take advantage of the "affects" field in apt-listbugs.

> If you think that it
> is useful for stable and older too, then enable it for these
> versions. Otherwise don't. Simple.

It would be useful for any Debian distribution, but without associated
version tracking info, I cannot see any sane way to handle it.

[...]
> > I think it's clear that "do not upgrade to B/b1" implies "if it is not
> > already too late".
> 
> I don't think so. If the packages are already installed, apt-listbugs
> won't come into play.

It won't come into play exactly because, if the buggy version is
already installed, the bug is *already* present in the system, so
there's no point in stopping any further upgrade.



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


pgpM59boLNno6.pgp
Description: PGP signature

Bug#825771: quodlibet: QuodLibet should depend on or at least recommend gir1.2-webkit2-4.0

[Klaumi Klingsporn]

Package: quodlibet
Version: 3.6.1-2
Severity: normal

Dear Maintainer,

QuodLibet should depend on or at least recommend gir1.2-webkit2-4.0 because 
otherwise 
the lyrics-plugin gives an error-message that it cannot find a webkit2-module.
After installing gir1.2-webkit2-4.0 all went fine.

Klaumi


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

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

Versions of packages quodlibet depends on:
ii  exfalso 3.6.1-2
ii  gir1.2-gst-plugins-base-1.0 1.8.1-1
ii  gir1.2-gstreamer-1.01.8.1-1
ii  gstreamer1.0-alsa [gstreamer1.0-audiosink]  1.8.1-1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-audiosink]   1.8.1-2
ii  gstreamer1.0-plugins-base   1.8.1-1
ii  gstreamer1.0-plugins-good [gstreamer1.0-audiosink]  1.8.1-1
ii  gstreamer1.0-plugins-ugly   1.8.1-1
ii  gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]1.8.1-1
ii  python  2.7.11-1

Versions of packages quodlibet recommends:
ii  gir1.2-gtksource-3.03.20.3-1
pn  gir1.2-keybinder-3.0
ii  gir1.2-soup-2.4 2.54.1-1
ii  libgpod40.8.3-7
ii  lxqt-notificationd [notification-daemon]0.10.0-2
ii  mate-notification-daemon [notification-daemon]  1.12.1-1
ii  media-player-info   22-2
ii  notification-daemon 3.20.0-1
ii  plasma-workspace [notification-daemon]  4:5.4.3-2
ii  python-dbus 1.2.4-1
ii  python-feedparser   5.1.3-3
ii  python-pyinotify0.9.5-1
ii  udisks  1.0.5-1+b1
ii  udisks2 2.1.7-1
ii  xfce4-notifyd [notification-daemon] 0.2.4-3+b1

Versions of packages quodlibet suggests:
ii  gstreamer1.0-plugins-bad  1.8.1-2

-- no debconf information

Bug#813197: RFP: nik4 -- Mapnik to image export

[Sebastiaan Couwenberg]

Because OSGeo-Live is now including nik4 in its osm installer, there is
more need for a nik4 package.

Upstream does not tag releases yet, but is considering it now that
OSGeo-Live includes it, so that latest git snapshot has been packaged.

Packaging is available in the Debian GIS git repository:

 https://anonscm.debian.org/cgit/pkg-grass/nik4.git

The package has also been uploaded but will need to pass the NEW queue.

Kind Regards,

Bas

Bug#825074: mirror submission for mirrors.cug.edu.cn

[Donald Norwood]

control: tag -1 +moreinfo

Hi,

Merged with Bug #82[1]

The trace directory indicates that this mirror has not been updated
since 20160523.

The tracefile named: mirrors.cug.edu.cn indicates the date information
in a manner that may not be readable by our mirror scanner.

Please display the README.html in your upper level directory for /debian/.

There is no need to re-submit this mirror, you may reply to this email.

Best regards,

Donald Norwood
-Debian Mirrors Team


[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=82

On Mon, 23 May 2016 11:14:53 + "PointStone Team"
 wrote:
> Package: mirrors
> Severity: wishlist
> User: mirr...@packages.debian.org
> Usertags: mirror-submission
> 
> Submission-Type: new
> Site: mirrors.cug.edu.cn
> Type: leaf
> Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 
> kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x 
> Archive-http: /debian/
> Archive-rsync: debian/
> CDImage-http: /debian-cd/
> CDImage-rsync: debian-cd/
> IPv6: yes
> Archive-upstream: ftp.cn.debian.org
> CDImage-upstream: ftp.cn.debian.org
> Updates: four
> Maintainer: PointStone Team 
> Country: CN China
> Location: Wuhan City, Hubei Province, China
> Sponsor: China University of Geosciences http://www.cug.edu.cn/
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#825770: adduser: [INTL:sk] Slovak po-debconf translation

[helix84]

Package: adduser
Version: 3.115
Priority: wishlist
Tags: l10n patch

.po attached


~~helix84


sk.po
Description: Binary data

Bug#798179: openconnect: Link to Juniper VPN will not be established without reconnect

[Mike Miller]

On Sun, Oct 18, 2015 at 05:06:21 +0200, Adnan Hodzic wrote:
> Hello,
> 
> I've upgraded my whole system to Stretch now, and I can confirm that I
> still have problem which I initially submitted in this bug report.
> 
> Please let me know if I can provide you with any additional information
> which could help you resolve it.

NetworkManager debug logs would be helpful (your earlier logs do not
have debug log level enabled), and ensure you are running the latest NM
1.2.2.

As David said earlier, the problem may turn out to be that
NetworkManager just doesn't work well when you configure things behind
its back. I would not be surprised if you are able to debug this and
determine that OpenConnect is behaving correctly, writing the expected
resolv.conf, and NetworkManager is noticing a state change and deciding
to "refresh" resolv.conf with its current internal state of what your
DNS should be, which does not include the Juniper tunnel that you just
brought up.

Apologies for not seeing this earlier,

-- 
mike

Bug#825703: utopia-documents: should be removed from Debian?

[Mattia Rizzolo]

On Sun, May 29, 2016 at 01:11:45PM -0400, Yaroslav Halchenko wrote:
> On Sat, 28 May 2016, Mattia Rizzolo wrote:
> > It doesn't look any good to me.
> > Please either fix the package soon (few weeks), or bear with us and do
> > not keep a broken package in the archive.
> 
> Upstream/maintainer is working to ship a new release within few
> weeks, which should address all outstanding issues.

I don't plan on taking a stick and poking any harder in less than a
month anyway.
And probably I'm not going to ask for RM these package were there was a
reply, but rather force the libssl1.0.0 removal breaking those packages.

That's should not be an exucuse to keep broken packages in the archive,
anyway.

> Unfortunately some
> correspondence tech issues forbidden follow up on bug reports.

unfortunately.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#825703: utopia-documents: should be removed from Debian?

[Yaroslav Halchenko]

On Sat, 28 May 2016, Mattia Rizzolo wrote:
> It doesn't look any good to me.
> Please either fix the package soon (few weeks), or bear with us and do
> not keep a broken package in the archive.

Upstream/maintainer is working to ship a new release within few
weeks, which should address all outstanding issues.  Unfortunately some
correspondence tech issues forbidden follow up on bug reports.

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