Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

Am 12.02.2015 um 08:31 schrieb Michael Biebl:
> Am 12.02.2015 um 07:34 schrieb Michael Biebl:
>> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
>>
>>> It is curious that the bug only manifests itself with the qemu watchdog.
>>> Two physical machines using the hardware iTCO_wdt watchdog reboot fine.
>>
>> In my tests, I did indeed have an unclean shutdown, and got an fsck on
>> next boot. Which looks to me, as if the watchdog i.e. qemu resets the VM
>> before it can shutdown cleanly.
> 
> A "systemctl poweroff" does not seem to trigger this issue. In that
> case, the system is properly shutdown.
> Only on "systemctl reboot" I'm to reproduce the problem, that the VM is
> reset after having reached the shutdown target.
> 
> With poweroff it looks like this (dump from the serial console log)
> 

...

> Note this line:
> [9.402243] i6300esb: Unexpected close, not stopping watchdog!

Some more findings: Aside from only happening on reboot, but not
shutdown, it also seems to only happen with i6300esb. Switching the qemu
config to use ib700 instead of i6300esb, I am not able to trigger the
problem. This confirm's Peter's findings who was not able to reproduce
it on real hardware.

I wonder, if this is a qemu issue, after all?

CCing our Debian qemu maintainer. Maybe he has some insight on this
matter (the complete bug log is at [1]).

Michael

[1] http://bugs.debian.org/35

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



signature.asc
Description: OpenPGP digital signature

Bug#777743: ITP: wallpaperd -- X wallpaper changing daemon

[Dmitry Bogatov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Bogatov 

* Package name: wallpaperd
  Version : 0.2.1
  Upstream Author : Claes Nästén 
* URL : http://projects.pekdon.net/git/wallpaperd.git
* License : BSD-2-clause
  Programming Lang: X
  Description : X wallpaper changing daemon

 - why is this package useful/relevant?

It follows unix way and manages wallpapers without connection to
your DE, WM or anything.

is it a dependency for another package?

No

do you use it?

Yes


if there are other packages providing similar functionality, how does it 
compare?

Such functionality exists in GNOME and KDE, at least. But I know nothing similar
for bare WM.

- how do you plan to maintain it?

I will need sponsor for it. I can maintain it myself or as
part of X team.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

Am 12.02.2015 um 07:34 schrieb Michael Biebl:
> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
> 
>> It is curious that the bug only manifests itself with the qemu watchdog.
>> Two physical machines using the hardware iTCO_wdt watchdog reboot fine.
> 
> In my tests, I did indeed have an unclean shutdown, and got an fsck on
> next boot. Which looks to me, as if the watchdog i.e. qemu resets the VM
> before it can shutdown cleanly.

A "systemctl poweroff" does not seem to trigger this issue. In that
case, the system is properly shutdown.
Only on "systemctl reboot" I'm to reproduce the problem, that the VM is
reset after having reached the shutdown target.

With poweroff it looks like this (dump from the serial console log)


...
[^[[32m  OK  ^[[0m] Stopped target Local File Systems.
 Unmounting /run/user/0...
[^[[32m  OK  ^[[0m] Stopped Load/Save Random Seed.
[^[[32m  OK  ^[[0m] Unmounted /run/user/0.
[^[[32m  OK  ^[[0m] Reached target Unmount All Filesystems.
[^[[32m  OK  ^[[0m] Stopped target Local File Systems (Pre).
 Stopping Create Static Device Nodes in /dev...
[^[[32m  OK  ^[[0m] Stopped Create Static Device Nodes in /dev.
 Stopping Remount Root and Kernel File Systems...
[^[[32m  OK  ^[[0m] Stopped Remount Root and Kernel File Systems.
[^[[32m  OK  ^[[0m] Reached target Shutdown.
[7.381639] systemd-shutdown[1]: Sending SIGTERM to remaining
processes...
[7.383562] systemd-journald[127]: Received SIGTERM from PID 1
(systemd-shutdow).
[7.434620] systemd-shutdown[1]: Sending SIGKILL to remaining
processes...
[7.437469] systemd-shutdown[1]: Unmounting file systems.
[7.438414] systemd-shutdown[1]: Unmounting /sys/kernel/debug.
[7.439219] systemd-shutdown[1]: Unmounting /dev/mqueue.
[7.439959] systemd-shutdown[1]: Unmounting /dev/hugepages.
[7.474276] EXT4-fs (vda1): re-mounted. Opts: (null)
[7.475479] EXT4-fs (vda1): re-mounted. Opts: (null)
[7.475881] EXT4-fs (vda1): re-mounted. Opts: (null)
[7.476303] systemd-shutdown[1]: All filesystems unmounted.
[7.476754] systemd-shutdown[1]: Deactivating swaps.
[7.477228] systemd-shutdown[1]: All swaps deactivated.
[7.477667] systemd-shutdown[1]: Detaching loop devices.
[7.478984] systemd-shutdown[1]: All loop devices detached.
[7.479815] systemd-shutdown[1]: Detaching DM devices.
[7.480675] systemd-shutdown[1]: All DM devices detached.
[7.482287] systemd-shutdown[1]: Powering off.
[7.503279] ACPI: Preparing to enter system sleep state S5
[7.503821] reboot: Power down


with reboot:

[^[[32m  OK  ^[[0m] Reached target Unmount All Filesystems.
[^[[32m  OK  ^[[0m] Stopped target Local File Systems (Pre).
 Stopping Create Static Device Nodes in /dev...
[^[[32m  OK  ^[[0m] Stopped Create Static Device Nodes in /dev.
 Stopping Remount Root and Kernel File Systems...
[^[[32m  OK  ^[[0m] Stopped Remount Root and Kernel File Systems.
[^[[32m  OK  ^[[0m] Reached target Shutdown.

nothing beyond this line


I then changed the watchdog action to dump. This time I get the
following log on reboot:

[^[[32m  OK  ^[[0m] Stopped Create Static Device Nodes in /dev.
 Stopping Remount Root and Kernel File Systems...
[^[[32m  OK  ^[[0m] Stopped Remount Root and Kernel File Systems.
[^[[32m  OK  ^[[0m] Reached target Shutdown.
[9.402243] i6300esb: Unexpected close, not stopping watchdog!
[9.448797] systemd-shutdown[1]: Sending SIGTERM to remaining
processes...
[9.514019] systemd-journald[127]: Received SIGTERM from PID 1
(systemd-shutdow).
[9.541822] systemd-shutdown[1]: Sending SIGKILL to remaining
processes...
[9.546845] systemd-shutdown[1]: Hardware watchdog 'i6300ESB timer',
version 0
[9.606194] systemd-shutdown[1]: Unmounting file systems.
[9.608565] systemd-shutdown[1]: Unmounting /sys/kernel/debug.
[9.610247] systemd-shutdown[1]: Unmounting /dev/mqueue.
[9.611636] systemd-shutdown[1]: Unmounting /dev/hugepages.
[9.664149] EXT4-fs (vda1): re-mounted. Opts: (null)
[9.666461] EXT4-fs (vda1): re-mounted. Opts: (null)
[9.666976] EXT4-fs (vda1): re-mounted. Opts: (null)
[9.667571] systemd-shutdown[1]: All filesystems unmounted.
[9.668304] systemd-shutdown[1]: Deactivating swaps.
[9.668988] systemd-shutdown[1]: All swaps deactivated.
[9.669632] systemd-shutdown[1]: Detaching loop devices.
[9.671348] systemd-shutdown[1]: All loop devices detached.
[9.672155] systemd-shutdown[1]: Detaching DM devices.
[9.672949] systemd-shutdown[1]: All DM devices detached.
[9.674747] systemd-shutdown[1]: Rebooting.


Note this line:
[9.402243] i6300esb: Unexpected close, not stopping watchdog!



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



signature.asc
Description: OpenPGP digital signature

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

Am 12.02.2015 um 07:34 schrieb Michael Biebl:
> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
> 
>> It is curious that the bug only manifests itself with the qemu watchdog.
>> Two physical machines using the hardware iTCO_wdt watchdog reboot fine.
> 
> In my tests, I did indeed have an unclean shutdown, and got an fsck on
> next boot. Which looks to me, as if the watchdog i.e. qemu resets the VM
> before it can shutdown cleanly.

A "systemctl poweroff" does not seem to trigger this issue. In that
case, the system is properly shutdown.
Only on "systemctl reboot" I'm to reproduce the problem, that the VM is
reset after having reached the shutdown target.

With poweroff it looks like this (dump from the serial console log)


...
[^[[32m  OK  ^[[0m] Stopped target Local File Systems.
 Unmounting /run/user/0...
[^[[32m  OK  ^[[0m] Stopped Load/Save Random Seed.
[^[[32m  OK  ^[[0m] Unmounted /run/user/0.
[^[[32m  OK  ^[[0m] Reached target Unmount All Filesystems.
[^[[32m  OK  ^[[0m] Stopped target Local File Systems (Pre).
 Stopping Create Static Device Nodes in /dev...
[^[[32m  OK  ^[[0m] Stopped Create Static Device Nodes in /dev.
 Stopping Remount Root and Kernel File Systems...
[^[[32m  OK  ^[[0m] Stopped Remount Root and Kernel File Systems.
[^[[32m  OK  ^[[0m] Reached target Shutdown.
[7.381639] systemd-shutdown[1]: Sending SIGTERM to remaining
processes...
[7.383562] systemd-journald[127]: Received SIGTERM from PID 1
(systemd-shutdow).
[7.434620] systemd-shutdown[1]: Sending SIGKILL to remaining
processes...
[7.437469] systemd-shutdown[1]: Unmounting file systems.
[7.438414] systemd-shutdown[1]: Unmounting /sys/kernel/debug.
[7.439219] systemd-shutdown[1]: Unmounting /dev/mqueue.
[7.439959] systemd-shutdown[1]: Unmounting /dev/hugepages.
[7.474276] EXT4-fs (vda1): re-mounted. Opts: (null)
[7.475479] EXT4-fs (vda1): re-mounted. Opts: (null)
[7.475881] EXT4-fs (vda1): re-mounted. Opts: (null)
[7.476303] systemd-shutdown[1]: All filesystems unmounted.
[7.476754] systemd-shutdown[1]: Deactivating swaps.
[7.477228] systemd-shutdown[1]: All swaps deactivated.
[7.477667] systemd-shutdown[1]: Detaching loop devices.
[7.478984] systemd-shutdown[1]: All loop devices detached.
[7.479815] systemd-shutdown[1]: Detaching DM devices.
[7.480675] systemd-shutdown[1]: All DM devices detached.
[7.482287] systemd-shutdown[1]: Powering off.
[7.503279] ACPI: Preparing to enter system sleep state S5
[7.503821] reboot: Power down


with reboot:

[^[[32m  OK  ^[[0m] Reached target Unmount All Filesystems.
[^[[32m  OK  ^[[0m] Stopped target Local File Systems (Pre).
 Stopping Create Static Device Nodes in /dev...
[^[[32m  OK  ^[[0m] Stopped Create Static Device Nodes in /dev.
 Stopping Remount Root and Kernel File Systems...
[^[[32m  OK  ^[[0m] Stopped Remount Root and Kernel File Systems.
[^[[32m  OK  ^[[0m] Reached target Shutdown.

nothing beyond this line


I then changed the watchdog action to dump. This time I get the
following log on reboot:

[^[[32m  OK  ^[[0m] Stopped Create Static Device Nodes in /dev.
 Stopping Remount Root and Kernel File Systems...
[^[[32m  OK  ^[[0m] Stopped Remount Root and Kernel File Systems.
[^[[32m  OK  ^[[0m] Reached target Shutdown.
[9.402243] i6300esb: Unexpected close, not stopping watchdog!
[9.448797] systemd-shutdown[1]: Sending SIGTERM to remaining
processes...
[9.514019] systemd-journald[127]: Received SIGTERM from PID 1
(systemd-shutdow).
[9.541822] systemd-shutdown[1]: Sending SIGKILL to remaining
processes...
[9.546845] systemd-shutdown[1]: Hardware watchdog 'i6300ESB timer',
version 0
[9.606194] systemd-shutdown[1]: Unmounting file systems.
[9.608565] systemd-shutdown[1]: Unmounting /sys/kernel/debug.
[9.610247] systemd-shutdown[1]: Unmounting /dev/mqueue.
[9.611636] systemd-shutdown[1]: Unmounting /dev/hugepages.
[9.664149] EXT4-fs (vda1): re-mounted. Opts: (null)
[9.666461] EXT4-fs (vda1): re-mounted. Opts: (null)
[9.666976] EXT4-fs (vda1): re-mounted. Opts: (null)
[9.667571] systemd-shutdown[1]: All filesystems unmounted.
[9.668304] systemd-shutdown[1]: Deactivating swaps.
[9.668988] systemd-shutdown[1]: All swaps deactivated.
[9.669632] systemd-shutdown[1]: Detaching loop devices.
[9.671348] systemd-shutdown[1]: All loop devices detached.
[9.672155] systemd-shutdown[1]: Detaching DM devices.
[9.672949] systemd-shutdown[1]: All DM devices detached.
[9.674747] systemd-shutdown[1]: Rebooting.


Note this line:
[9.402243] i6300esb: Unexpected close, not stopping watchdog!



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





signature.asc
Description: OpenPGP digital signature

Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces

[Heiko Ernst]

On Tue, 10 Feb 2015 17:47:01 +0100 Holger Wansing  
wrote:
> This is getting confusing:
> In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777439#35 you wrote,
> that you have done a shell-only install (no desktop environment).
> Now you write, that you have kde and network-manager installed.
> ???
> Without the installer logs there is no chance to get this sorted out.
> 

Sorry, I have install only the shell with the debian installer and have than 
with apt-get install kde., after installing the shell.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777732: ITP: nagios-check-xmppng -- monitoring plugin for checking XMPP servers

[Alexander Wirt]

On Wed, 11 Feb 2015, Jan Dittberner wrote:

> Package: wnpp
> Severity: wishlist
> Owner: Jan Dittberner 
> 
> * Package name: nagios-check-xmppng
>   Version : 0.1.2
>   Upstream Author : Jan Dittberner 
> * URL : https://exchange.icinga.org/jandd/check_xmppng
> * License : GPL
>   Programming Lang: Python
>   Description : monitoring plugin for checking XMPP servers
> 
> implements a nagios check plugin for XMPP servers implementing the XMPP
> protocol as specified in RFC 6120.
> 
> The program implements the following features:
> 
>  - check client to server (C2S) as well as server to server (S2S) ports
>  - check XMPP servers on IPv6 and IPv4 addresses
>  - support STARTTLS as specified in RFC 6120 section 5.
>  - check the validity of the server certificate presented by the XMPP server
> 
> The plugin has been implemented because of insufficiencies in the existing
> check_ssl_cert and check_xmpp plugins.
> 
> Maximum acceptable timeouts as well as minimum acceptable number of days the
> server certificate needs to be valid can be specified as command line
> parameters.
> 
> I'm upstream developer of the plugin and use it to monitor my own XMPP
> servers.
For such a simple plugin, wouldn't it be easier to just add it to
nagios-plugins-contrib? 

Alex



pgpyTtqrvzS5n.pgp
Description: PGP signature

Bug#727242: kmail: Kmail does not import filters from previous version

[Stuart Prescott]

Control: summary -1 Filters need to be restored from the old kmail 
configuration; see https://wiki.debian.org/KDE/Jessie/kontact

Hi,

> I suggested this workaround on https://bugs.kde.org/show_bug.cgi?id=326474
[..]

yes, that's pretty much what is documented in the release notes [1] and on the 
wiki [2].

[1] 
https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#kde-kontact

[2] https://wiki.debian.org/KDE/Jessie/kontact

Good to have that noted in this bug too.

cheers
Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777649: cgmanager security update for jessie

[Niels Thykier]

Control: tags -1 confirmed moreinfo

On 2015-02-12 05:32, Serge Hallyn wrote:
> Here is a new debdiff.  (tested in its original upstream version
> in v0.36)   Maybe it would've been easier to squash the two patches,
> but this way it's easier to tell whether the patches match what is
> upstream.
> 
> [...]

Ack, looks better.  :)  Please add the (missing parts of this) patch to
unstable first and then upload the target fixes into testing with
version 0.33-2+deb8u1.

Please remove the moreinfo tag once the above have been done.

Thanks,
~Niels


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777742: simple-scan: "All pages from feeder" scans an extra blank page

[Ivan Kohler]

Package: simple-scan
Version: 3.15.4-1
Severity: normal
Tags: upstream

When I put a single page into the feeder of my scanner and use the
"All Pages From Feeder" scan option, an extra blank page is appended to the
output.  (If I use the "Single Page" option, it doesn't pull from the feeder at
all, which is not what is most useful.)

Mechanically, the scanner only scans the one page -- it doesn't have some sort
of paper detection error and physically scan another page.  Other applications
like skanlite in ADF mode correctly scan a single page.

Also, deleting the additional page does not work -- I right click on the page,
select delete, and nothing happens.  This might be a separate bug report, can
clone if so, but I mention it here because page deletion otherwise seems to
work and I wouldn't have to delete the extra blank page if it wasn't there in
the first place.

p.s. thanks for a scanning program for the free software desktop that finally
has a nice UI, PDF output, options for the things I need and no cluuter for
useless options I don't.

-- Package-specific info:

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

Kernel: Linux 3.16.0-4-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 simple-scan depends on:
ii  adwaita-icon-theme   3.14.0-2
ii  dbus-x11 1.8.14-1
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-13
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libcolord2   1.2.1-1+b2
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgtk-3-0   3.14.5-1
ii  libgudev-1.0-0   215-11
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libsane  1.0.24-9
ii  xdg-utils1.1.0~rc1+git20111210-7.3
ii  zlib1g   1:1.2.8.dfsg-2+b1

simple-scan recommends no packages.

simple-scan suggests no packages.

-- no debconf information

-- 
Ivan Kohler
President and Head Geek, Freeside Internet Services, Inc.  http://freeside.biz/
Debian GNU/Linux developer  |  CPAN author  |  cat person  |  ski addict


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#727273: [Pkg-ime-devel] Bug#727273: sunpinyin: diff for NMU version 2.0.3+git20140127-1.1

[Liang Guo]

Hi, Baozi

On Thu, Feb 12, 2015 at 10:40 AM, Chen Baozi  wrote:
> tags 727273 + pending
> thanks
>
> Dear maintainer,
>
> I've prepared an NMU for sunpinyin (versioned as 2.0.3+git20140127-1.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
>
> (I've noticed that this bug was claimed to be fixed in a previous commit.
> However, it has come back since the following update...)
>
> Regards.
>
> ___
> Pkg-ime-devel mailing list
> pkg-ime-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ime-devel

Please upload it to DELAYED/0, thanks,

sunpinyin use git to keep its source, if possible please update git too.

Thanks,
-- 
Liang Guo
http://guoliang.me/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

Am 12.02.2015 um 07:29 schrieb Peter Colberg:
> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:

> It is curious that the bug only manifests itself with the qemu watchdog.
> Two physical machines using the hardware iTCO_wdt watchdog reboot fine.

In my tests, I did indeed have an unclean shutdown, and got an fsck on
next boot. Which looks to me, as if the watchdog i.e. qemu resets the VM
before it can shutdown cleanly.



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



signature.asc
Description: OpenPGP digital signature

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Peter Colberg]

On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
> Thanks, I was able to reproduce the issue this way (marking the bug
> accordingly).
> It's likely that the watchog is resetting systemd/rsyslog before it has
> a chance to stop properly.
> 
> Let's see, where we can go from here.

In a vimdiff comparing the two console logs I sent earlier, the last
messages before the reboot of the VM with watchdog are

  Failed to send unit remove signal for final.target: Transport endpoint is not 
connected
  Hardware watchdog 'i6300ESB timer', version 0

while the VM without watchdog does unmounts after final.target

  Failed to send unit remove signal for final.target: Transport endpoint is not 
connected
  Sending SIGTERM to remaining processes...
  [   62.134791] systemd-journald[146]: Received SIGTERM from PID 1 
(systemd-shutdow).
  Sending SIGKILL to remaining processes...
  Unmounting file systems.
  Unmounting /dev/mqueue.
  Unmounting /sys/kernel/debug.
  Unmounting /dev/hugepages.
  [   62.314461] EXT4-fs (vda3): re-mounted. Opts: (null)
  [   62.316377] EXT4-fs (vda3): re-mounted. Opts: (null)
  [   62.316999] EXT4-fs (vda3): re-mounted. Opts: (null)
  All filesystems unmounted.
  Deactivating swaps.
  All swaps deactivated.
  Detaching loop devices.
  All loop devices detached.
  Detaching DM devices.
  All DM devices detached.
  /lib/systemd/system-shutdown succeeded.
  [   62.382524] Unregister pv shared memory for cpu 2
  Rebooting.
  [   62.382524] Unregister pv shared memory for cpu 0
  [   62.382524] Unregister pv shared memory for cpu 1
  [   62.385199] Unregister pv shared memory for cpu 3
  [   62.386474] reboot: Restarting system
  [   62.387022] reboot: machine restart


It is curious that the bug only manifests itself with the qemu watchdog.
Two physical machines using the hardware iTCO_wdt watchdog reboot fine.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777741: wss4j: CVE-2015-0226 CVE-2015-0227

[Moritz Muehlenhoff]

Package: wss4j
Severity: grave
Tags: security
Justification: user security hole

Hi,
please see
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-0226
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-0227

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

control: tags -1 = confirmed
control: retitle -1 data corruption on reboot when using watchdog/qemu

Am 12.02.2015 um 06:57 schrieb Peter Colberg:
> On Thu, Feb 12, 2015 at 05:44:59AM +0100, Michael Biebl wrote:
>> Fwiw, I pulled the debian_wheezy_amd64_desktop.qcow2 qemu-kvm image from
>> [1], started it with "qemu-system-x86_64 -enable-kvm -hda
>> debian_wheezy_amd64_standard.qcow2".
>> Then did a dist-upgrade to jessie, which replaced sysvinit with
>> systemd-sysv as default.
>> Did a couple of reboots and couldn't find any corruption in any of the
>> rsyslog managed log files.
> 
> Good idea! I did the same and then started the VM with
> 
> qemu-system-x86_64 -curses -enable-kvm -device i6300esb -watchdog-action 
> reset -hda debian_wheezy_amd64_standard.qcow2
> 
> A reboot triggers corruption in /var/log/syslog with a hole of nils.
> 

Thanks, I was able to reproduce the issue this way (marking the bug
accordingly).
It's likely that the watchog is resetting systemd/rsyslog before it has
a chance to stop properly.

Let's see, where we can go from here.


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



signature.asc
Description: OpenPGP digital signature

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Peter Colberg]

On Thu, Feb 12, 2015 at 05:44:59AM +0100, Michael Biebl wrote:
> Fwiw, I pulled the debian_wheezy_amd64_desktop.qcow2 qemu-kvm image from
> [1], started it with "qemu-system-x86_64 -enable-kvm -hda
> debian_wheezy_amd64_standard.qcow2".
> Then did a dist-upgrade to jessie, which replaced sysvinit with
> systemd-sysv as default.
> Did a couple of reboots and couldn't find any corruption in any of the
> rsyslog managed log files.

Good idea! I did the same and then started the VM with

qemu-system-x86_64 -curses -enable-kvm -device i6300esb -watchdog-action reset 
-hda debian_wheezy_amd64_standard.qcow2

A reboot triggers corruption in /var/log/syslog with a hole of nils.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777740: debian-installer: Default keyboard is not set for Korean language

[Christian PERRIER]

reassign 40 console-setup
thanks

Quoting Changwoo Ryu (cw...@debian.org):

>Like other languages, it should choose the default kr keymap.
> 
> I have no idea which package decides the default keyboard for a given
> language. I added Korean default in console-setup package, in #756052.
> But it doesn't seem to change d-i.


Still, the package responsible for this is console-setup.

Hence reassigning, though I have no idea why things don't work as expected...



signature.asc
Description: Digital signature

Bug#777740: debian-installer: Default keyboard is not set for Korean language

[Changwoo Ryu]

Package: debian-installer
Severity: normal

Dear D-I team,

Currently on jessie d-i, it always asks keyboard to use when I select
Korean language.

   * What led up to the situation?

   Select Korean language and proceed

   * What was the outcome of this action?

   It asks keyboard type, presenting the full list of available
   keyboards.

   * What outcome did you expect instead?

   Like other languages, it should choose the default kr keymap.

I have no idea which package decides the default keyboard for a given
language. I added Korean default in console-setup package, in #756052.
But it doesn't seem to change d-i.


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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Peter Colberg]

On Thu, Feb 12, 2015 at 04:28:38AM +0100, Michael Biebl wrote:
> Just to be clear here: Is this only happening once after the
> dist-upgrade from wheezy (sysvinit) to jessie (systemd-sysv) on reboot
> or everytime you reboot your jessie system?

It happens everytime I reboot from within the VM.

> What makes you think this is a disk corruption? The log message you
> provided shows that the disks are clean?

Yes, this is not disk corruption. The fsck at bootup is clean.

This is more acurately described as data loss. I see it in the form of
log data produced shortly before the reboot (that is after reboot is
issued and before the machine is reset) not being written to disk.
Instead, the log files contain variably-sized holes of nil bytes.

> Which other file? What file system is this?

So far I noticed corruption in /var/log/syslog and /var/log/daemon.log
which are written by rsyslog, and in /var/log/prosody/prosody.log
which is written by prosody.

Each VM has attached a single virtio disk with a GPT partition label
that contains a swap partition, an ext4 filesystem for /, and further
ext4 filesystems for /home and /srv.

> Can you share such a (gzipped) qemu-kvm image or provide instructions,
> how we can reproduce the problem?

Sorry, I cannot share the machine images since they contain private
data. However, I have now disabled any non-essential services on one
machine. Please see the file 'ps_aux' that shows all processes running
when logged in via ssh. I can still reproduce the corruption with this
mimimal configuration.

> Since systemd-logind reacts on external ACPI power button presses with
> the same command (systemctl poweroff), I'm suprised that this is
> supposed to make a difference.

I have narrowed down the issue significantly: corruption only occurs if
qemu-kvm emulates a watchdog device. I am using libvirt, please see
the file 'himeji.xml' for the machine setup.

When I remove the watchdog device from the VM, the corruption
disappears and /var/log/syslog contains the expected last and
first messages before and after the reboot:

Feb 11 23:41:19 himeji rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" 
x-pid="532" x-info="http://www.rsyslog.com";] exiting on signal 15.
Feb 11 23:41:57 himeji rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" 
x-pid="518" x-info="http://www.rsyslog.com";] start

> Can you follow the steps at [1] and provide a verbose debug log from
> boot and poweroff by logging to the serial console.
> 
> 
> [1] http://freedesktop.org/wiki/Software/systemd/Debugging/

I captured a reboot of the VM with and without a watchdog device. Please note
that reboots in a VM with watchdog device were working fine with sysvinit.

Does systemd always use /dev/watchdog? /etc/systemd/system.conf was left
unmodified, in particular it does not define RuntimeWatchdogSec.

Regards,
Peter
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.6  0.1  28460  4548 ?Ss   23:45   0:01 /sbin/init
root 2  0.0  0.0  0 0 ?S23:45   0:00 [kthreadd]
root 3  0.3  0.0  0 0 ?S23:45   0:00 [ksoftirqd/0]
root 4  0.0  0.0  0 0 ?S23:45   0:00 [kworker/0:0]
root 5  0.0  0.0  0 0 ?S<   23:45   0:00 [kworker/0:0H]
root 6  0.0  0.0  0 0 ?S23:45   0:00 [kworker/u8:0]
root 7  0.3  0.0  0 0 ?S23:45   0:00 [rcu_sched]
root 8  0.0  0.0  0 0 ?S23:45   0:00 [rcu_bh]
root 9  0.0  0.0  0 0 ?S23:45   0:00 [migration/0]
root10  0.0  0.0  0 0 ?S23:45   0:00 [watchdog/0]
root11  0.0  0.0  0 0 ?S23:45   0:00 [watchdog/1]
root12  0.0  0.0  0 0 ?S23:45   0:00 [migration/1]
root13  0.4  0.0  0 0 ?S23:45   0:00 [ksoftirqd/1]
root14  0.0  0.0  0 0 ?S23:45   0:00 [kworker/1:0]
root15  0.0  0.0  0 0 ?S<   23:45   0:00 [kworker/1:0H]
root16  0.0  0.0  0 0 ?S23:45   0:00 [watchdog/2]
root17  0.0  0.0  0 0 ?S23:45   0:00 [migration/2]
root18  0.3  0.0  0 0 ?S23:45   0:00 [ksoftirqd/2]
root19  0.0  0.0  0 0 ?S23:45   0:00 [kworker/2:0]
root20  0.0  0.0  0 0 ?S<   23:45   0:00 [kworker/2:0H]
root21  0.0  0.0  0 0 ?S23:45   0:00 [watchdog/3]
root22  0.0  0.0  0 0 ?S23:45   0:00 [migration/3]
root23  0.3  0.0  0 0 ?S23:45   0:00 [ksoftirqd/3]
root24  0.0  0.0  0 0 ?S23:45   0:00 [kworker/3:0]
root25  0.0  0.0  0 0 ?S<   23:45   0:00 [kworker/3:0H]
root26  0.0  0.0  0 0 ?S<   23:45   0:00 [khelper]
root27  0.0  0.

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

control: severity -1 important

Am 12.02.2015 um 04:28 schrieb Michael Biebl:
>> I could reproduce this issue with three machines that are virtualized
>> > with qemu-kvm. On the other hand, I did not see this issue with two
>> > physical machines. All of these are running the above version of
>> > systemd.
> Can you share such a (gzipped) qemu-kvm image or provide instructions,
> how we can reproduce the problem?

Fwiw, I pulled the debian_wheezy_amd64_desktop.qcow2 qemu-kvm image from
[1], started it with "qemu-system-x86_64 -enable-kvm -hda
debian_wheezy_amd64_standard.qcow2".
Then did a dist-upgrade to jessie, which replaced sysvinit with
systemd-sysv as default.
Did a couple of reboots and couldn't find any corruption in any of the
rsyslog managed log files.



[1] https://people.debian.org/~aurel32/qemu/amd64/
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#777649: cgmanager security update for jessie

[Serge Hallyn]

Here is a new debdiff.  (tested in its original upstream version
in v0.36)   Maybe it would've been easier to squash the two patches,
but this way it's easier to tell whether the patches match what is
upstream.

diff -Nru cgmanager-0.33/debian/changelog cgmanager-0.33/debian/changelog
--- cgmanager-0.33/debian/changelog 2014-10-13 18:35:43.0 -0500
+++ cgmanager-0.33/debian/changelog 2015-02-11 22:28:11.0 -0600
@@ -1,3 +1,18 @@
+cgmanager (0.33-3) testing; urgency=medium
+
+  * SECURITY UPDATE: Cross-cgroup resource control bypass.
+- debian/patches/0003-make-sure-to-check-cgroup-hierarchy.patch, modify
+  cgmanager.c to verify that requests are allowed under the caller's
+  cgroup.
+- CVE-2014-1425
+  * 0004-chown-stop-cgmanager-crash-on-chown-of-bad-file.patch and
+0005-prevent-some-cgmanager-asserts.patch: prevent cgmanager
+crashing on unhandled asserts or dbus error (LP: #1407787)
+  * 0006-fix-subdirectory-check: further fix to the previous patch for
+CVE-2014-1425.
+
+ -- Serge Hallyn   Mon, 26 Jan 2015 09:12:02 -0600
+
 cgmanager (0.33-2) unstable; urgency=medium
 
   * Cherrypick two upstream patches to ensure that 'movepid all' continues
diff -Nru 
cgmanager-0.33/debian/patches/0003-make-sure-to-check-cgroup-hierarchy.patch 
cgmanager-0.33/debian/patches/0003-make-sure-to-check-cgroup-hierarchy.patch
--- 
cgmanager-0.33/debian/patches/0003-make-sure-to-check-cgroup-hierarchy.patch
1969-12-31 18:00:00.0 -0600
+++ 
cgmanager-0.33/debian/patches/0003-make-sure-to-check-cgroup-hierarchy.patch
2015-01-26 09:15:58.0 -0600
@@ -0,0 +1,201 @@
+From 6267916d4ea939794e0583cd8b08bd0b9594a6e2 Mon Sep 17 00:00:00 2001
+From: Serge Hallyn 
+Date: Wed, 26 Nov 2014 01:00:10 -0600
+Subject: [PATCH 1/1] make sure to check cgroup hierarchy
+
+Some cases weren't doing that, although at least those were still
+checking for proper ownership.
+
+Signed-off-by: Serge Hallyn 
+---
+ cgmanager.c |   85 

+ 1 file changed, 80 insertions(+), 5 deletions(-)
+
+Index: cgmanager-0.33/cgmanager.c
+===
+--- cgmanager-0.33.orig/cgmanager.c
 cgmanager-0.33/cgmanager.c
+@@ -558,13 +558,20 @@ next:
+ int get_value_main(void *parent, const char *controller, const char *cgroup,
+   const char *key, struct ucred p, struct ucred r, char **value)
+ {
+-  char path[MAXPATHLEN];
++  char pcgpath[MAXPATHLEN], path[MAXPATHLEN];
+ 
+   if (!sane_cgroup(cgroup)) {
+   nih_error("%s: unsafe cgroup", __func__);
+   return -1;
+   }
+ 
++  // Get p's current cgroup in pcgpath
++  if (!compute_pid_cgroup(p.pid, controller, "", pcgpath, NULL)) {
++  nih_error("%s: Could not determine the proxy's cgroup for %s",
++  __func__, controller);
++  return -1;
++  }
++
+   if (!compute_pid_cgroup(r.pid, controller, cgroup, path, NULL)) {
+   nih_error("%s: Could not determine the requested cgroup 
(%s:%s)",
+ __func__, controller, cgroup);
+@@ -577,6 +584,14 @@ int get_value_main(void *parent, const c
+   return -1;
+   }
+ 
++  // Make sure target cgroup is under proxy's
++  int plen = strlen(pcgpath);
++  if (strncmp(pcgpath, path, plen) != 0) {
++  nih_error("%s: target cgroup is not below r (%d)'s", __func__,
++  r.pid);
++  return -1;
++  }
++
+   /* append the filename */
+   if (strlen(path) + strlen(key) + 2 > MAXPATHLEN) {
+   nih_error("%s: filename too long for cgroup %s key %s", 
__func__, path, key);
+@@ -608,19 +623,34 @@ int set_value_main(const char *controlle
+   struct ucred r)
+ 
+ {
+-  char path[MAXPATHLEN];
++  char pcgpath[MAXPATHLEN], path[MAXPATHLEN];
+ 
+   if (!sane_cgroup(cgroup)) {
+   nih_error("%s: unsafe cgroup", __func__);
+   return -1;
+   }
+ 
++  // Get p's current cgroup in pcgpath
++  if (!compute_pid_cgroup(p.pid, controller, "", pcgpath, NULL)) {
++  nih_error("%s: Could not determine the proxy's cgroup for %s",
++  __func__, controller);
++  return -1;
++  }
++
+   if (!compute_pid_cgroup(r.pid, controller, cgroup, path, NULL)) {
+   nih_error("%s: Could not determine the requested cgroup 
(%s:%s)",
+ __func__, controller, cgroup);
+   return -1;
+   }
+ 
++  // Make sure target cgroup is under proxy's
++  int plen = strlen(pcgpath);
++  if (strncmp(pcgpath, path, plen) != 0) {
++  nih_error("%s: target cgroup is not below r (%d)'s", __func__,
++  r.pid);
++  return -1;
++  }
++
+   /* Check access rights to the cgroup directory */
+   if (!m

Bug#775527: live-images: upgrade splash to Jessie theme

[Daniel Baumann]

On 02/11/15 20:19, jnqnfe wrote:
> Why are we now using the simple black syslinux theme instead of the
> official install disc theme?

it's the one Juliette provided in her tarball.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771805: input-events still registers events from the "mouse"

[Yaroslav Halchenko]

according to 

$> sudo input-events -t 10 15
/dev/input/event15
   bustype : BUS_I8042
   vendor  : 0x2
   product : 0x1
   version : 0
   name: "PS/2 Generic Mouse"
   phys: "isa0060/serio2/input0"
   bits ev : EV_SYN EV_KEY EV_REL

...

events continue to arrive.  so I guess the issue is further down the food-chain
(gnome to blame?)

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777694: RFA: icu -- Development utilities for International Components for Unicode

[Dimitri John Ledkov]

On Wed, 11 Feb 2015 10:29:24 -0500 Jay Berkenbilt  wrote:
> Package: wnpp
> Severity: normal
>
> I request an adopter for the icu package as I no longer have time to
> maintain the package.
>

I am happy to help out, not as main maintainer but uploader/contributor.

I also contribute to boost.

Regards,

Dimitri.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776345: Close this

[Matt Harvey]

I realized that these crashes correlated absolutely with me changing my
xorg.conf to switch to a different Intel 2D graphics driver. I don't think
Intel is supporting that graphics driver again, so this bug can probably be
safely closed.

It is still odd that it was crashing.

Thanks,
Matt

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Michael Biebl]

control: tags -1 moreinfo unreproducible

Am 12.02.2015 um 03:19 schrieb Peter Colberg:
> Package: systemd
> Version: 215-11
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> 
> After upgrading to jessie from wheezy, I noticed that some of the
> system logs experience corruption when rebooting the system.

Just to be clear here: Is this only happening once after the
dist-upgrade from wheezy (sysvinit) to jessie (systemd-sysv) on reboot
or everytime you reboot your jessie system?

> After rebooting the system using the command ‘reboot’ or ‘systemctl
> reboot’, some log files such as /var/log/syslog contain a hole with
> nil bytes:
>

>   Feb 11 14:48:22 himeji systemd[20266]: Reached target Sockets.
>   Feb 11 14:48:22 himeji systemd[20266]: Starting Basic System.
>   Feb 11 14:48:22 himeji systemd[20266]: Reached target Basic System.
>   Feb 11 14:48:22 himeji systemd[20266]: Starting Default.
>   Feb 11 14:48:22 himeji systemd[20266]: Reached target Default.
>   Feb 11 14:48:22 himeji systemd[20266]: Startup finished in 3ms.
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>   ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb 11 14:54:55 himeji 
> rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="539" 
> x-info="http://www.rsyslog.com";] start
>   Feb 11 14:54:55 himeji systemd-fsck[137]: /dev/vda3: clean, 81576/2621440 
> files, 889144/10485760 blocks
>   Feb 11 14:54:55 himeji systemd-fsck[233]: /dev/vda4: clean, 2187/3670016 
> files, 1858872/14679547 blocks
>   Feb 11 14:54:55 himeji networking[245]: Configuring network 
> interfaces...Waiting for DAD... Done
>   Feb 11 14:54:55 himeji networking[245]: done.



What makes you think this is a disk corruption? The log message you
provided shows that the disks are clean?


> 
> This happened with log files managed by rsyslog as well as one log
> file not managed by rsyslog.

Which other file? What file system is this?

 I assume this issue is not related to
> logging, but rather manifests itself in any files that are modified
> right before the reboot, e.g. due to daemons logging a shutdown
> notice.
> 
> I could reproduce this issue with three machines that are virtualized
> with qemu-kvm. On the other hand, I did not see this issue with two
> physical machines. All of these are running the above v

Bug#777739: rinse: silence postcmd by mounting /proc

[Olaf Meeuwissen]

Package: rinse
Version: 3.0.6
Severity: wishlist

Dear Maintainer,

While building a chroot for Fedora 19, the following caught my eye:

  $ sudo http_proxy=$http_proxy https_proxy=$https_proxy rinse --verbose 
--distribution fedora-19 --arch amd64 --directory=/var/tmp/rinse-fedora-19
  Copying rpm's from cache /var/cache/rinse//fedora-19.amd64/ to 
/var/tmp/rinse-fedora-19
  Loading sub index pages from 
http://mirrors.kernel.org/fedora/releases/19/Everything/x86_64/os/Packages/
  0 3 4 9 a b c d e f g h i j k l m n o p q r s t u v w x y z 


 
  Copying rpm's from /var/tmp/rinse-fedora-19 to cache 
/var/cache/rinse//fedora-19.amd64/


  
  Execute postcmd cp /var/tmp/rinse-fedora-19/fedora-release-19-2.noarch.rpm 
/var/tmp/rinse-fedora-19/tmp ; chroot /var/tmp/rinse-fedora-19 rpm -ivh --force 
--nodeps /tmp/fedora-release-19-2.noarch.rpm ; rm 
/var/tmp/rinse-fedora-19/tmp/fedora-release-19-2.noarch.rpm
  warning: Failed to read auxiliary vector, /proc not mounted?
  warning: Failed to read auxiliary vector, /proc not mounted?
  warning: Failed to read auxiliary vector, /proc not mounted?

While this does not seem to cause any problems, it would be nicer if the
warnings weren't issued.  That can be achieved by mounting /proc before
running the postcmd.  I was surprised that rinse doesn't do this given
the number of references to the fact that that is why rinse needs to run
as root ;-)

Please mount /proc before running the postcmd.  It is probably best to
unmount it again immediately afterwards.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages rinse depends on:
ii  libterm-size-perl  0.207-1+b2
ii  libwww-perl6.08-1
ii  perl-modules   5.20.1-5
ii  rpm4.11.3-1.1
ii  wget   1.16-1

rinse recommends no packages.

rinse suggests no packages.

-- Configuration Files:
/etc/rinse/fedora-core-10.packages 6e2621c788fb0025f6951770c9644fd5 [Errno 2] 
No such file or directory: u'/etc/rinse/fedora-core-10.packages 
6e2621c788fb0025f6951770c9644fd5'
/etc/rinse/fedora-core-7.packages 8a62dea080c3b6c75431cd4b684f5067 [Errno 2] No 
such file or directory: u'/etc/rinse/fedora-core-7.packages 
8a62dea080c3b6c75431cd4b684f5067'
/etc/rinse/fedora-core-8.packages 1a1b06ac5f1ce814a95aa67e04e86769 [Errno 2] No 
such file or directory: u'/etc/rinse/fedora-core-8.packages 
1a1b06ac5f1ce814a95aa67e04e86769'
/etc/rinse/fedora-core-9.packages 009b69c21f10e9f5de21713843c24920 [Errno 2] No 
such file or directory: u'/etc/rinse/fedora-core-9.packages 
009b69c21f10e9f5de21713843c24920'

-- no debconf information

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#727273: sunpinyin: diff for NMU version 2.0.3+git20140127-1.1

[Chen Baozi]

tags 727273 + pending
thanks

Dear maintainer,

I've prepared an NMU for sunpinyin (versioned as 2.0.3+git20140127-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

(I've noticed that this bug was claimed to be fixed in a previous commit.
However, it has come back since the following update...)

Regards.
diff -Nru sunpinyin-2.0.3+git20140127/debian/changelog sunpinyin-2.0.3+git20140127/debian/changelog
--- sunpinyin-2.0.3+git20140127/debian/changelog	2014-03-01 07:25:20.0 +
+++ sunpinyin-2.0.3+git20140127/debian/changelog	2015-02-11 12:36:14.0 +
@@ -1,3 +1,10 @@
+sunpinyin (2.0.3+git20140127-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix aarch64 endian check. (Closes: #727273)
+
+ -- Chen Baozi   Wed, 11 Feb 2015 12:34:59 +
+
 sunpinyin (2.0.3+git20140127-1) unstable; urgency=low
 
   * New upstream snapshot 20140127
diff -Nru sunpinyin-2.0.3+git20140127/debian/patches/detect-endianness-for-arm64.patch sunpinyin-2.0.3+git20140127/debian/patches/detect-endianness-for-arm64.patch
--- sunpinyin-2.0.3+git20140127/debian/patches/detect-endianness-for-arm64.patch	1970-01-01 00:00:00.0 +
+++ sunpinyin-2.0.3+git20140127/debian/patches/detect-endianness-for-arm64.patch	2015-02-11 12:04:04.0 +
@@ -0,0 +1,20 @@
+--- sunpinyin-2.0.3+git20140127.orig/SConstruct
 sunpinyin-2.0.3+git20140127/SConstruct
+@@ -312,7 +312,7 @@ def AppendEndianCheck(conf):
+ #elif defined(__sparc) || defined(__sparc__) \
+   || defined(_POWER)   || defined(__powerpc__) \
+   || defined(__ppc__)  || defined(__hpux) || defined(__hppa) \
+-  || defined(_MIPSEB)  || defined(_POWER) \
++  || defined(_MIPSEB)  || defined(_POWER) || defined(__aarch64_be__) \
+   || defined(__s390__) || (defined(__sh__) && defined(__BIG_ENDIAN__))
+ # define WORDS_BIGENDIAN 1
+ 
+@@ -323,7 +323,7 @@ def AppendEndianCheck(conf):
+   || defined(__amd64__) || defined(_M_AMD64) \
+   || defined(__x86_64)  || defined(__x86_64__) \
+   || defined(_M_X64)|| defined(__bfin__) \
+-  || defined(__alpha__) || defined(__ARMEL__) \
++  || defined(__alpha__) || defined(__ARMEL__) || defined(__aarch64__) \
+   || defined(_MIPSEL)   || (defined(__sh__) && defined(__LITTLE_ENDIAN__))
+ # undef WORDS_BIGENDIAN
+ 
diff -Nru sunpinyin-2.0.3+git20140127/debian/patches/series sunpinyin-2.0.3+git20140127/debian/patches/series
--- sunpinyin-2.0.3+git20140127/debian/patches/series	2014-03-01 07:09:05.0 +
+++ sunpinyin-2.0.3+git20140127/debian/patches/series	2015-02-11 11:59:23.0 +
@@ -1,2 +1,3 @@
 fix-data-dir.diff
 strndup_in_cxx.patch
+detect-endianness-for-arm64.patch

Bug#623271: Adoption of Slides (Python-based Slide Maker)

[Matthias Klose]

Hi, I won't have the time to do that, CCing debian-python. You may want to ask
for a sponsor there, or even join the python-modules team.

Matthias

On 02/06/2015 06:23 AM, Riley Baird wrote:
> Hi Matthias,
> 
> A couple of years ago, you orphaned the "slides" package. I'd like to
> adopt it, but since I'm not a DD, I can't upload the package. Would you
> be interested in sponsoring my uploads?
> 
> You can get the new version of the package with this command:
> dget -x
> http://mentors.debian.net/debian/pool/main/s/slides/slides_1.0.1-14.dsc
> 
> For your reference, the changelog entry is:
>   * New maintainer (closes: #623271).
>   * Upgraded to Debhelper 9/pybuild
>   * Bumped standards version to 3.9.6
>   * Added Vcs and Homepage fields to d/control
>   * Changed dependencies
>   * Added DEP-5 copyright
>   * Extended the description of slides-doc
>   * Updated source format to "3.0 (quilt)"
> 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771269: ITP: jnr-ffi -- Java library for loading native libraries without writing writing JNI code

[Miguel Landaeta]

On Mon, Dec 01, 2014 at 05:24:44AM +, Potter, Tim (Cloud Services) wrote:
> >
> 
> Thanks Emmanuel.  You're correct of course.  The rest of the jnr-* modules
> require a big update (1.0.2 -> 1.2.7) to the jffi package, but I haven't
> been able to get it building yet.

I think you should prepare an upload for 2.0.1 release of this package.

Dependencies on old jffi packages should be migrated (i.e. jython,
jaffl and jenkins) and remove jffi from the archive.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#777738: jnr-netdb: Please package 1.1.4 or more recent releases

[Miguel Landaeta]

Package: src:jnr-netdb
Version: 1.0.3-3
Severity: wishlist

As title says and mostly a reminder for myself.
To be used with recent jruby releases.

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

Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#777737: cdebootstrap: please make the build reproducible

[Chris Lamb]

Source: cdebootstrap
Version: 0.6.4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes timestamps from the build system. Once
applied, cdebootstrap can be built reproducibly in our current
experimental
framework.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad cdebootstrap.orig/cdebootstrap-0.6.4/debian/rules 
cdebootstrap/cdebootstrap-0.6.4/debian/rules
--- cdebootstrap.orig/cdebootstrap-0.6.4/debian/rules   2015-02-11 
22:52:37.057717891 +
+++ cdebootstrap/cdebootstrap-0.6.4/debian/rules2015-02-12 
02:30:03.394302529 +
@@ -7,6 +7,7 @@
 include /usr/share/dpkg/default.mk
 
 VERSION  := $(shell dpkg-parsechangelog | sed -ne 's,^Version: *\(.*\),\1,p')
+BUILD_DATE := $(shell dpkg-parsechangelog --show-field Date)
 
 configure:
autoreconf -i
@@ -86,7 +87,7 @@
dh_prep
dh_installdirs
 
-   $(MAKE) -C build-deb install DESTDIR=$(CURDIR)/debian/cdebootstrap
+   $(MAKE) -C build-deb install DESTDIR=$(CURDIR)/debian/cdebootstrap 
BUILD_DATE="$(BUILD_DATE)"
 
$(MAKE) -C build-static install 
DESTDIR=$(CURDIR)/debian/cdebootstrap-static
mv debian/cdebootstrap-static/usr/bin/cdebootstrap 
debian/cdebootstrap-static/usr/bin/cdebootstrap-static
@@ -94,7 +95,7 @@
 
$(MAKE) -C build-tar install DESTDIR=$(CURDIR)/debian/tmp
strip --remove-section=.comment --remove-section=.note 
debian/tmp/usr/bin/cdebootstrap
-   tar -C debian/tmp/usr/bin -czf 
debian/tmp/cdebootstrap_$(VERSION)_$(DEB_HOST_ARCH).tar.gz .
+   GZIP=-9n tar -C debian/tmp/usr/bin --mtime="$(BUILD_DATE)" -czf 
debian/tmp/cdebootstrap_$(VERSION)_$(DEB_HOST_ARCH).tar.gz .
mkdir -p debian/cdebootstrap-static/usr/lib/cdebootstrap
cp debian/tmp/cdebootstrap_$(VERSION)_$(DEB_HOST_ARCH).tar.gz 
debian/cdebootstrap-static/usr/lib/cdebootstrap
 
diff -urNad cdebootstrap.orig/cdebootstrap-0.6.4/helper/Makefile.am 
cdebootstrap/cdebootstrap-0.6.4/helper/Makefile.am
--- cdebootstrap.orig/cdebootstrap-0.6.4/helper/Makefile.am 2015-02-11 
22:52:37.061718068 +
+++ cdebootstrap/cdebootstrap-0.6.4/helper/Makefile.am  2015-02-12 
02:36:09.415943735 +
@@ -22,6 +22,8 @@
 
 temp-%:
$(MAKE) -C $(PACKAGE) package DESTDIR=$(CURDIR)/temp-$(PACKAGE)
+   find "$(CURDIR)/temp-$(PACKAGE)" -print0 | \
+   xargs -0r touch --date="$(BUILD_DATE)"
 
 root-%:
dpkg-deb -Zgzip --build temp-$(PACKAGE) $(PACKAGE).deb
diff -urNad cdebootstrap.orig/cdebootstrap-0.6.4/helper/Makefile.in 
cdebootstrap/cdebootstrap-0.6.4/helper/Makefile.in
--- cdebootstrap.orig/cdebootstrap-0.6.4/helper/Makefile.in 2015-02-11 
22:52:37.061718068 +
+++ cdebootstrap/cdebootstrap-0.6.4/helper/Makefile.in  2015-02-12 
02:35:35.802681843 +
@@ -604,6 +604,8 @@
 
 root-%:
dpkg-deb -Zgzip --build temp-$(PACKAGE) $(PACKAGE).deb
+   find "$(CURDIR)/temp-$(PACKAGE)" -print0 | \
+   xargs -0r touch --date="$(BUILD_DATE)"
 
 clean-local:
rm -rf $(foreach package,$(packages),temp-$(package))

Bug#747256: Chocolate Doom should be split into separate packages

[Andrew Apted]

Package: chocolate-doom
Version: 2.1.0-1
Followup-For: Bug #747256

I think this is more severe than just "wishlist", since it installs menu items
for things which DO NOT WORK when you click on them (e.g. Chocolate-Heretic is
in the games menu, but absolutely nothing happens when you select it, not even
an error message about missing game data).



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

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

Versions of packages chocolate-doom depends on:
ii  doom-wad-shareware [doom-wad]  1.9.fixed-2
ii  libc6  2.19-13
ii  libpng12-0 1.2.50-2+b2
ii  libsamplerate0 0.1.8-8
ii  libsdl-mixer1.21.2.12-11+b1
ii  libsdl-net1.2  1.2.8-4
ii  libsdl1.2debian1.2.15-10+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

chocolate-doom recommends no packages.

Versions of packages chocolate-doom suggests:
ii  zenity  3.14.0-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777712: i386 kernel list out of date

[Steve McIntyre]

Control: tag -1 pending
Control: severity -1 normal

On Wed, Feb 11, 2015 at 07:03:59PM +, Ben Hutchings wrote:
>Package: debian-cd
>Version: 3.1.13
>Severity: serious
>
>As the 486 kernel flavour was renamed to 586, linux-image-586 needs to
>be included on CD#1 and so should linux-headers-586.
>
>There is an option to exclude the 486 flavour, and I wasn't sure
>whether this should cover 586 as well or whether it should be renamed.
>The following *untested* patch is meant to exclude both flavours if
>either of EXCLUDE_{486,586}_KERNEL is set.

Similar changes are already in git for the regular builds, just not in
the archive yet for v3.1.17. Expecting an upload shortly.

Again, curious why you're looking at 3.1.13...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777736: redmine: Typo in documentation for apache2-host.conf

[Andrew Harvey]

Package: redmine
Version: 3.0~20140825-4
Severity: minor

Dear Maintainer,

There is a typo at

http://anonscm.debian.org/cgit/pkg-ruby-extras/redmine.git/tree/debian/doc/examples/apache2-host.conf

on line two, "libapache2-mod-fcdid"

Bug#777735: systemd: Disk corruption on reboot initiated through systemd

[Peter Colberg]

Package: systemd
Version: 215-11
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

After upgrading to jessie from wheezy, I noticed that some of the
system logs experience corruption when rebooting the system.

After rebooting the system using the command ‘reboot’ or ‘systemctl
reboot’, some log files such as /var/log/syslog contain a hole with
nil bytes:

  Feb 11 14:48:22 himeji systemd[20266]: Reached target Sockets.
  Feb 11 14:48:22 himeji systemd[20266]: Starting Basic System.
  Feb 11 14:48:22 himeji systemd[20266]: Reached target Basic System.
  Feb 11 14:48:22 himeji systemd[20266]: Starting Default.
  Feb 11 14:48:22 himeji systemd[20266]: Reached target Default.
  Feb 11 14:48:22 himeji systemd[20266]: Startup finished in 3ms.
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb 11 14:54:55 himeji 
rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="539" 
x-info="http://www.rsyslog.com";] start
  Feb 11 14:54:55 himeji systemd-fsck[137]: /dev/vda3: clean, 81576/2621440 
files, 889144/10485760 blocks
  Feb 11 14:54:55 himeji systemd-fsck[233]: /dev/vda4: clean, 2187/3670016 
files, 1858872/14679547 blocks
  Feb 11 14:54:55 himeji networking[245]: Configuring network 
interfaces...Waiting for DAD... Done
  Feb 11 14:54:55 himeji networking[245]: done.

This happened with log files managed by rsyslog as well as one log
file not managed by rsyslog. I assume this issue is not related to
logging, but rather manifests itself in any files that are modified
right before the reboot, e.g. due to daemons logging a shutdown
notice.

I could reproduce this issue with three machines that are virtualized
with qemu-kvm. On the other hand, I did not see this issue with two
physical machines. All of these are running the above version of
systemd.

Further, I found a work-around to avoid data corruption as seen in the
log files. If the system is rebooted through an external ACPI event
(sent to the qemu-kvm process), /var/log/syslog is not corrupted:

  Feb 11 18:17:03 himeji systemd[4412]: Reached target Default.
  Feb 11 18:17:03 himeji systemd[4412]: Startup finished in 4ms.
  Feb 11 18:17:04 himeji systemd[4412]: Stopping Default.
  Feb 11 18:17:04 himeji systemd[4412]: Stopped target Default.
  Feb 11 18:17:04 himeji systemd[4412]: Stopping Basic System.
  Feb 11

Bug#777675: qtcreator: hang and repeated SIGSEGV on exit

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 11 February 2015 14:30:51 Martin Kourim wrote:
> See inline.
[snip]
> > Which driver are you using for it?
> 
> fglrx-driver (1:14.9+ga14.201-2) from non-free

A proprietary driver, that's what I've expected :)

> > Did you test it in another machine with different video specs?
> 
> Yes, I can't reproduce this issue on my ThinkPad x220 with Intel graphics.

Please try to reproduce the bug without the proprietary driver, ie, using the 
radeon one.

-- 
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#777711: ARM and MIPS kernel lists out of date

[Steve McIntyre]

Control: tag -1 pending

On Wed, Feb 11, 2015 at 06:56:43PM +, Ben Hutchings wrote:
>Package: debian-cd
>Version: 3.1.13
>Severity: important
>Tags: patch
>
>tools/generate_d-i+k_list has outdated lists of kernel packages for
>armhf, mips and mipsel.

Taken these for mips*; armhf is already up-to-date but you're looking
at an old version.

>- There are new flavours for all of these in jessie, and MIPS kernels
>  now boot using an initramfs
>- The mipsel/loongson-2f and mips/octeon flavours were added in
>  wheezy but seem to have been missed here (this should perhaps be
>  fixed in a wheezy point release too)

Good point. I'll backport this too.

>The 4kc-malta and 5kc-malta flavours for mips and mipsel are also
>missing here, but since these flavours have been around for a long
>time I assume this is deliberate.

I believe so, but it's been a long time since I've had any of the mips
folks suggest updates.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#773942: O: lynx-cur -- Text-mode WWW Browser with NLS support (development version)

[Denis Briand]

On Thu, Feb 12, 2015 at 02:04:26AM +0100, Axel Beckert wrote:
> Shall we open an Alioth project to get a team mailing list? Or will
> collab-maint plus bug tracking system already suffice the team's
> needs?

IMHO I think a team mailing list will be better to coordinate our work. 

> > Maybe Axel could open a collab-maint git repository on alioth to
> > work together ?
> 
> Done: https://anonscm.debian.org/cgit/collab-maint/lynx-cur.git/

Great !
Have I an access to push my commits on this repository with my narcan-guest 
alioth account?


> I've created it with "git-import-dscs --debsnap lynx-cur", so the
> whole package history (one commit per upload or upstream release) as
> far back as available on snapshots.debian.org is in there now --
> including Andreas' uploads to experimental. (Thanks for these,
> Andreas! Much appreciated.)
> 
> I've also added according Vcs-* headers, did some minor cosmetic
> changes and dropped the transitional packages which seem to be
> transitional packages since at least Squeeze.

I couldn't have put it better myself !
Many thanks.

Best regards

Denis Briand


signature.asc
Description: Digital signature

Bug#705218: deluge-gtk crash with libcrypto.so.1.0.0

[Hector Colina]

Package: deluge-gtk
Version: 1.3.3-2+nmu1
Followup-For: Bug #705218

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

deluge-gtk crash frequently and dmesg show:

root@astrid:/# dmesg |grep segfault
[ 8681.837216] /usr/bin/deluge[5849]: segfault at 7fbb4a178340 ip
7fbb56f72f9e sp 7fbb3d6b8cc0 error 4 in
libcrypto.so.1.0.0[7fbb56ed1000+1ca000]
[17567.139623] /usr/bin/deluge[10401]: segfault at 7f7f5a6e0710 ip
7f7f1211cf9e sp 7f7ef8862cc0 error 4 in
libcrypto.so.1.0.0[7f7f1207b000+1ca000]
[27803.365835] /usr/bin/deluge[16070]: segfault at 7f1842594cc0 ip
7f18283a8f9e sp 7f180eaeecc0 error 4 in
libcrypto.so.1.0.0[7f1828307000+1ca000]
root@astrid:/#

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages deluge-gtk depends on:
ii  deluge-common1.3.3-2+nmu1
ii  librsvg2-common  2.36.1-2
ii  mate-notification-daemon [notification-daem  1.8.0-2~bpo70+1
ii  notification-daemon  0.7.6-1
ii  python   2.7.3-4+deb7u1
ii  python-glade22.24.0-3+b1
ii  python-notify0.1.1-3
ii  xdg-utils1.1.0~rc1+git20111210-6+deb7u2

Versions of packages deluge-gtk recommends:
ii  python-pygame  1.9.1release+dfsg-8

deluge-gtk suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQGcBAEBAgAGBQJU3AAqAAoJEDV/gfVc/LSBPHgL/RQ2caQ0tNASD9cpuJLv5Zem
AFlu3evHrVxtKC/20G67Buw+IqU1bwlM7HxMGyrjDZ4+xHcmw9ePDqXV1VXk24ue
TrEH7gFWhLRMPYITmNhpfa3Gv3YUPuUrQBDVpjbWDCBIPXbdUa56W6wLW5GXYcr/
0stPbjECU4z+yckj985Nos0cD7pzTPl0uiS4QjP+i+L/9ppQbxYdbj5JMWUY3c6a
pmJj0AX3IDobx+5dsL+bb8/kmbIOGV8BD6sYCMUCNPU1zi7PQPrIKHb5dfHYpuCp
aLZqrVKsokDGK96Ml9w8Gs3G8jhUM/Te4dOGn1ix1mq7Yh933XgNzRJ9kPIlhA/f
EEy4Z2enO7JcEFfJfpYmdSH4NwVe2n6cpWJAsVfoJqZbnJVcTl/Q8YyuZzq56UKy
x7iV5Tngg/uBU/SxCS1J4d35zbr199ffXYSyy65+MeGHu8dC90UJ78yFsHEkW34H
nPYfEKybX67NLpPsgeZg3R2kWNBYRiRsEtkMuB3OKw==
=+d6H
-END PGP SIGNATURE-

-- 
**
Hector Colina. Linux  counter id 131637
Debian user, aka e1th0r
Mérida-Venezuela http://colina.net.ve
Key fingerprint = E81B 8228 8919 EE27 85B7  A59B 357F 81F5 5CFC B481
LA REVOLUCIÓN NO SE HACE UNICAMENTE CON LAS ARMAS


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#670984: Debian package for phidget

[Jonathan McCrohan]

Hi Faben,

On Wed, Feb 11, 2015 at 10:56:04AM +0100, Fabien André wrote:
> I saw your ITP of libphidget21 and the discussions that followed. Links
> from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673098#5 suggest
> that you have done most of the job but unfortunately they are broken.
> 
> Is the packaging code still available somewhere ?

Yes, it is still available here [1]. Please bear in mind that I haven't
looked at in number of years and will need refreshing. The comments
below might also be no longer relevant, but I suspect not.

> Also, could you elaborate on copyright concerns with upstream code raised
> by Nicholas Breen?

Relevant excerpts from Nicholas' mail:

* None of the Phidgets code files have copyright information in the headers,
  except for a couple that have something other than LGPL notices, such as
  examples/phidgetsbclist.c and most files in Java/com/phidgets ("All rights
  reserved").  Presumably it's LGPLed like the rest, but their own copyright
  statement should clarify what files the LGPL license applies to -- ideally
  in the files themselves, since the All Rights Reserved by itself does not
  permit anything.

* include/dns_sd.h: Copyright belongs to Apple and must be noted in the
  documentation.

* include/jni/*: "SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license
  terms."  Those license terms are not defined in the package.  Whatever they
  may be, it's almost certainly not permitted to redistribute them without that
  license available.

* Java/com/phidgets/event/KeyChangeEvent.java: "Copyright 2006 Dictionarys Inc.
  All rights reserved."  Needs clarification and possible relicensing.  Also
  KeyRemovalEvent.java.

* Java/*.h: all machine generated, but from what?  Can they be regenerated from
  files in the package and tools available in Debian?  A brief note in
  debian/README.source would more than suffice here.

* zeroconf_lookup.c: claims to be taken from "mDNSResponderPosix's nss_mdns
  code", which I believe is Apache 2.0-licensed (by Apple), not LGPL.

* utils/cvtutf.?: "This code is copyrighted. Under the copyright laws, this
  code may not be copied, in whole or part, without prior written consent of
  Taligent." That's a red flag!  It may need to be replaced with other code,
  e.g. http://www.unicode.org/faq/utf_bom.html#gen4

* utils/md5.?: Copyright Aladdin Enterprises.  Okay to use but should be noted
  in copyright file.

* linux/avahi-{client,common}: Code copies are discouraged.  Could it instead
  build against the existing libavahi-client-dev and libavahi-common-dev
  packages?  The different origin of these files should also be noted in
  debian/copyright; they could also be stripped entirely, but since they're
  LGPLed as well, probably not worth repacking the tarbell.  A note in
  debian/README.source explaining that they're unused (if moved to using the
  libavahi* packages instead) would help.

> Last question, are you still interested in maintaining this package, and
> would you mind if somebody else take over?

Unfortunately I have no longer have access to any phidget hardware, so I
have no interest in maintaining it. Feel free to reassign the ITP.

Jon

[1] http://git.dereenigne.org/debian/libphidget21.git


pgpSm872MSm8l.pgp
Description: PGP signature

Bug#777720: Suggested debdiff for #777720, #777723 and #777724

[John Paul Adrian Glaubitz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/12/2015 02:03 AM, Iain R. Learmonth wrote:
> Please upload an NMU with the changes posted in the debdiff to 
> DELAYED/5. (Debian Developer's Reference §5.6.2)

Sure, I will. I just reworded the first changelog entry slightly as
it sounded a bit weird :). Will upload in a minute.

> If Colin has any objections to the changes, this will give him an 
> oppertunity to intervene before the package is installed into 
> unstable.

Agree.

> I had noticed these problems before but hadn't had the time yet to 
> sit down and work out what the dependencies should have been. 
> Thanks for your work on this.

I'm just starting with amateur radio and, of course, any software I use
for that should run on Linux. And usually, when I start using something
new, I always find something small that can be improved :).

Thanks for packaging cqrlog!

Cheers,
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
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU2//OAAoJEHQmOzf1tfkTc5MP/i38BfbS9Z43K4z1Le0+Io8j
2dSFusCbX2H6OQjb0cag/ZoS4aOOS7Y0OuOyQwSxchiYLJMrApeK8BqXYnhpgRSL
B9Sx/a9tAETVMp+1fK5Cr0qAcj9v/PTxrfKRdNEewBo+nnkBWFdGSRc1M8vKkta4
G5dJYzqLF07G6lfE2VkfhxORxO7wuIIx1DMVCQJxI0H6rlWa1X24/kplZrfXhVDI
7GTcrEIKiDlLvZbE6YDD9aPkGOihTX4AiR3+LdqYu0u+gryztKDtZ5mQTb+IJY6J
xY6deuRNW2vY9jv9RNCXD/8oSUuTFy89hZtFop/8MBrUwD8HNJu9Pcfp9P5BB3cS
Z3kR8SH5p/QZCCFd0XddzBRK34z9tPFtHYLrDA4PGgD6WXkMkcTwcEnz9iu51xky
dMVZG3zilK+xRbT41+r92yPk2tWiZyhSofG/B3b1lO+KVVITzpLm5tdPm/fgj+5d
eZ1hJfe1ib5vkw+BpWUW5akkoN/qLw8fRTLeZewf7/0m89vROT9OoUnou4uXi3lm
uV6VnuQTEhOlg96glanGnSbED9kRAwcE1a4NXB2G+Kjk4u9r4XaCMcTsQj4IIUxY
A5BDlg6LizLIRxYTa4ch+RQoB8UUppBr3x3xpvkZM6LB2gDL3R+pxLlnRquG5qeJ
dc/A+iy7DXWWtniTu/A+
=WDSB
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777720: Suggested debdiff for #777720, #777723 and #777724

[Iain R. Learmonth]

Hi John,

On Wed, Feb 11, 2015 at 11:46:59PM +0100, John Paul Adrian Glaubitz wrote:
> I made the necessary changes [...]

These changes look good. Colin is currently the last person to look at this
package, but I believe this was part of his sweep through the team packages
fixing bugs.

Please upload an NMU with the changes posted in the debdiff to DELAYED/5.
(Debian Developer's Reference §5.6.2)

If Colin has any objections to the changes, this will give him an
oppertunity to intervene before the package is installed into unstable.

I had noticed these problems before but hadn't had the time yet to sit down
and work out what the dependencies should have been. Thanks for your work on
this.

Thanks,
Iain.

-- 
e: i...@fsfe.orgw: iain.learmonth.me
x: i...@jabber.fsfe.org t: EPVPN 2105
c: 2M0STB  g: IO87we
p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49


pgp4AN9PDauX2.pgp
Description: PGP signature

Bug#775319: Further testing

[lachlan-00]

I've tested the most recent 3.16 and 3.18 kernels with the same results.

I also shrank my partitions to install windows and have no sound issues with 
windows.

Bug#777649: cgmanager security update for jessie

[Serge Hallyn]

Quoting Niels Thykier (ni...@thykier.net):
> Ok, are we guaranteed that pcgpath ends with the path separator?  Consider:

No in fact I think we're guaranteed it won't.

>   "/foo/bar"
>   "/foo/bar2/somewhere-else"
> 
> Unless the path separator is included in the end (i.e. it always uses
> "/foo/bar/" instead of "/foo/bar"), then it might still be possible to
> by-pass the prefix test.

Indeed it will, thanks!  I'm going to write a patch which commonizes
the checks and takes care of this case.  I'll get it into the next
release and send a patch for jessie tonight or tomorrow.

Note that ownership checks still apply, so the task in /foo/bar
could only affect /foo/bar2  if it owns /foo/bar2.  Or if it is
root, but root in a privileged container will be locked under
/lxc/$container.  So this should be less urgent than the larger
fix already addressed.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#738760: libav: Add proper raspberry pi CPU detection

[peter green]

On 12/02/15 00:29, Sebastian Ramacher wrote:

Hi Peter,

Rasbperry Pi 2 has now been released and, if I read the news correctly,
it supports NEON instructions. Should we revert the changes or do they
need any modifications?
   

That is a question that will need some experimentation/testing to answer.

What is the best way to test libav? (ideally a test that can be done on 
the built packages rather than at build time)



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#738760: libav: Add proper raspberry pi CPU detection

[Sebastian Ramacher]

Hi Peter,

Rasbperry Pi 2 has now been released and, if I read the news correctly,
it supports NEON instructions. Should we revert the changes or do they
need any modifications?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#777734: libfreenect version bump

[Benn Snyder]

Package: libfreenect


libfreenect and associated packages are at v0.2.0 in Debian unstable.
However, upstream  is at
v0.5.2.  Please bump to the latest version.



Best Regards,
Benn

Bug#777733: squirrelmail: please enable UTF-8 for French

[Jeremie Bouttier]

Package: squirrelmail
Version: 2:1.4.23~svn20120406-2
Severity: wishlist
Tags: l10n

  Hi,

Currently, using the SquirrelMail interface in French implies using the 
iso-8859-1 charset (this is hardcoded in 
/usr/share/squirrelmail/functions/i18n.php). When replying to a message 
in utf-8, the accentuated characters are broken unless one enables the 
lossy_encoding option to force conversion to iso-8859-1 (but of course 
this won't work for all characters). Wouldn't it be a better solution to 
use utf-8 directly ?
Best,

  Jérémie


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages squirrelmail depends on:
ii  apache2-mpm-worker [httpd]  2.2.22-13+deb7u4
ii  perl5.14.2-21+deb7u2
ii  php55.4.36-0+deb7u3
ii  php5-cgi5.4.36-0+deb7u3

Versions of packages squirrelmail recommends:
ii  aspell [aspell-bin]   0.60.7~20110707-1
ii  ispell3.3.02-6
ii  php5-common [php5-mhash]  5.4.36-0+deb7u3
ii  squirrelmail-locales  1.4.18-20090526-1
pn  squirrelmail-viewashtml   

Versions of packages squirrelmail suggests:
ii  dovecot-imapd [imap-server]  1:2.1.7-7+deb7u1
ii  imapproxy1.2.7-1.1
ii  php-pear 5.4.36-0+deb7u3
pn  php5-ldap
pn  php5-recode  
ii  squirrelmail-decode  1.2-1

-- Configuration Files:
/etc/squirrelmail/apache.conf changed [not included]

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777643: general: possibly, some keyboard layouts should use U+22C5 DOT OPERATOR instead of U+00B7 MIDDLE DOT

[Jonas Smedegaard]

Quoting Joachim Breitner (2015-02-12 00:23:13)
> Am Mittwoch, den 11.02.2015, 23:32 +0100 schrieb Christoph Anton
> Mitterer:
>> Anyway, to finally end this ugly matter on the Debian side, I've 
>> forwarded the pointer about this possible issue upstream, so that 
>> they can choose to have what Debian didn't want to do - a proper look 
>> at the matter.
>> 
>> It should be noted for those who seems to accuse me of bad faith, 
>> that I, personally, use a custom keymapping anyway,... so I don't 
>> care much whether it's left as is or not.
>
> just for the record, I find Christophs suggestion valid, reasonable, 
> well explained and done in best featth, and it does by no means 
> deserve the treatment that he received.

I fully agree.


> (who already wondered why · does not align with + and − (not - or –, 
> of course). But ⋅ doesn’t either, here... I guess you can file a bug 
> against some font packages :-))

How dare you write ... instead of the proper … :-P

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#777643: general: possibly, some keyboard layouts should use U+22C5 DOT OPERATOR instead of U+00B7 MIDDLE DOT

[Jeremy Stanley]

On 2015-02-11 23:32:32 +0100 (+0100), Christoph Anton Mitterer wrote:
[...]
> Am I know expected to insult you as well? Guess I'm not up to date, what
> Debian's CoC actually demands, it only seems to be usable when being
> against me but not for myself ;-)
[...]

Apologies--I was paraphrasing Ralph Waldo Emerson's warning against
consistency for consistency's sake--it wasn't meant as a personal
slight in any way whatsoever.
-- 
Jeremy Stanley


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777691: dbus: Can't logout properly after "service dbus restart"; reboot needed

[Vincent Lefevre]

Control: reassign -1 debian-goodies 0.64
Control: retitle -1 checkrestart should not recommend "service dbus restart"

On 2015-02-11 22:08:52 +, Simon McVittie wrote:
> On 11/02/15 14:51, Vincent Lefevre wrote:
> > When I execute "service dbus restart" as root
> 
> Restarting the dbus-daemon other than by rebooting (system bus) or
> logging out/back in (session bus) is not a supported action, and
> checkrestart should not be recommending it. Yes, I know this is not how
> things should be, and in an ideal world it would be fully restartable,
> but we do not live in that ideal world.
[...]

So, I'm reassigning the bug to debian-goodies, which provides the
checkrestart utility.

I think that checkrestart should have a special test for dbus, and
say that dbus is affected and a reboot may be needed.

BTW, "service kerneloops restart" also fails to restart, so that
there may be something similar for it.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777643: general: possibly, some keyboard layouts should use U+22C5 DOT OPERATOR instead of U+00B7 MIDDLE DOT

[Joachim Breitner]

Hi,

Am Mittwoch, den 11.02.2015, 23:32 +0100 schrieb Christoph Anton
Mitterer:
> Anyway, to finally end this ugly matter on the Debian side, I've
> forwarded the pointer about this possible issue upstream, so that they
> can choose to have what Debian didn't want to do - a proper look at the
> matter.
> 
> It should be noted for those who seems to accuse me of bad faith, that
> I, personally, use a custom keymapping anyway,... so I don't care much
> whether it's left as is or not.

just for the record, I find Christophs suggestion valid, reasonable,
well explained and done in best featth, and it does by no means deserve
the treatment that he received.

The only “mistake”, if any, would have been to report the bug against
"general" instead of finding out the proper package.

And the proper response should have been “You might be right, but this
issue does not seem to be sever enough to warrant Debian to deviate from
Upstream. We suggest that you take the issue to upstream.”

I’m sorry for how this went and hope that your next contribution to
Debian will be more enjoyable to you.

Greetings,
Joachim

(who already wondered why · does not align with + and − (not - or –, of
course). But ⋅ doesn’t either, here... I guess you can file a bug
against some font packages :-))


-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#777732: ITP: nagios-check-xmppng -- monitoring plugin for checking XMPP servers

[Jan Dittberner]

Package: wnpp
Severity: wishlist
Owner: Jan Dittberner 

* Package name: nagios-check-xmppng
  Version : 0.1.2
  Upstream Author : Jan Dittberner 
* URL : https://exchange.icinga.org/jandd/check_xmppng
* License : GPL
  Programming Lang: Python
  Description : monitoring plugin for checking XMPP servers

implements a nagios check plugin for XMPP servers implementing the XMPP
protocol as specified in RFC 6120.

The program implements the following features:

 - check client to server (C2S) as well as server to server (S2S) ports
 - check XMPP servers on IPv6 and IPv4 addresses
 - support STARTTLS as specified in RFC 6120 section 5.
 - check the validity of the server certificate presented by the XMPP server

The plugin has been implemented because of insufficiencies in the existing
check_ssl_cert and check_xmpp plugins.

Maximum acceptable timeouts as well as minimum acceptable number of days the
server certificate needs to be valid can be specified as command line
parameters.

I'm upstream developer of the plugin and use it to monitor my own XMPP
servers.

-- 
Jan Dittberner - Debian Developer
GPG-key: 4096R/558FB8DD 2009-05-10
 B2FF 1D95 CE8F 7A22 DF4C  F09B A73E 0055 558F B8DD
https://portfolio.debian.net/ - https://people.debian.org/~jandd/


signature.asc
Description: Digital signature

Bug#777731: chromium-dbg: Incomplete debug symbols

[Paul Menzel]

Package: chromium-dbg
Version: 40.0.2214.91-1
Severity: normal

Dear Debian folks,


Chromium crashed today and I wanted to create a meaningfull backtrace.

NetworkChangeNo[1138]: segfault at fff4 ip b2100217 sp ad6e8c20 
error 5 in chromium[b172e000+60bb000]

Wanting to create a meaningful backtrace from the core dump file I
installed chromium-dbg` for the debugging symbols.

Reading symbols from /usr/lib/chromium/chromium...Reading symbols from 
/usr/lib/debug/.build-id/4c/a2c2adb2c05798f349d6314650fd76f742609b.debug...Can't
 read data for section '.debug_info' in file 
'/usr/lib/debug/.build-id/4c/a2c2adb2c05798f349d6314650fd76f742609b.debug'
(no debugging symbols found)...done.
(no debugging symbols found)...done.
[…]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `/usr/lib/chromium/chromium'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb2100217 in base::(anonymous 
namespace)::FilePathWatcherImpl::OnFilePathChanged(int, std::string const&, 
bool, bool, bool) ()
[Messages with symbols unavailable]

So it looks like not all debugging symbols are there.

It’d be great if these could be added.


Thanks,

Paul

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages chromium-dbg depends on:
ii  chromium  40.0.2214.91-1

chromium-dbg recommends no packages.

chromium-dbg suggests no packages.

-- no debconf information


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

Bug#777730: debdelta: please make the build reproducible

[Chris Lamb]

Source: debdelta
Version: 0.55
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes timestamps from the build system. Once
applied, debdelta can be built reproducibly in our current experimental
framework.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad debdelta.orig/debdelta-0.55/debian/rules 
debdelta/debdelta-0.55/debian/rules
--- debdelta.orig/debdelta-0.55/debian/rules2015-02-11 22:53:24.17985 
+
+++ debdelta/debdelta-0.55/debian/rules 2015-02-11 23:13:19.171868158 +
@@ -51,7 +51,7 @@
rm -rf $(D2)
install -d $(D2)/DEBIAN  $(docdir2)  $(docdir2doc)
cp doc/debdelta_suite.pdf debian/copyright debian/changelog 
$(docdir2doc)
-   cd $(docdir2doc) && gzip -9 changelog
+   cd $(docdir2doc) && gzip -9n changelog
cp -r doc/html  $(docdir2doc)
ln -s ../debdelta-doc/debdelta_suite.pdf  $(docdir2)
ln -s ../debdelta-doc/html  $(docdir2)
@@ -94,10 +94,10 @@
ln -s debdelta  $(D)/usr/bin/debdelta-upgrade
# /usr/share/doc
cp FAQ README.features debian/copyright debian/changelog $(docdir)
-   cd $(docdir) && gzip -9 changelog FAQ
+   cd $(docdir) && gzip -9n changelog FAQ
# man
cp *.1 $(mandir)
-   gzip -9 $(mandir)/*.1 
+   gzip -9n $(mandir)/*.1 
# build package
dpkg-shlibdeps $(D)/usr/lib/debdelta/minigzip  
$(D)/usr/lib/debdelta/minibzip2
dpkg-gencontrol -Pdebian/debdelta -pdebdelta

Bug#777728: when downloading magnet link ktorrent's interface freezes

[Tomas Pospisek]

Package: ktorrent
Version: 4.3.1-2+b1
Severity: important

Hello,

I start ktorrent, I go to File->Open Address, I enter the following
magnet address:

magnet:?xt=urn:btih:32E50D9656E101F54120ADA3CE73F7A65EC9D5CB&dn=10-million-combos.zip&tr=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969&tr=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969%2fannounce&tr=udp%3a%2f%2fopen.demonii.com%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969%2fannounce&tr=http%3a%2f%2fbt.careland.com.cn%3a6969%2fannounce&tr=http%3a%2f%2fi.bandito.org%2fannounce&tr=http%3a%2f%2fopensharing.org%3a2710%2fannounce&tr=udp%3a%2f%2ftrackr.sytes.net%3a80

(it's the password file from Mark Burnett)

press enter and ktorrent freezes. The interface is dead. I can't scroll,
nothing. When I minimize the ktorrent window and reopen it, it's just
blank. When I click on the blue arrow in the gadgets list in the menu
bar nothing happens.

However I see that ktorrent is generating a lot of network traffic, so
"something" is working.

I'm running xfce with no particular weird config that I'd estimate could
have any influence on ktorrent.

?

*t

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

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

Versions of packages ktorrent depends on:
ii  kde-runtime 4:4.14.2-2
ii  ktorrent-data   4.3.1-2
ii  libc6   2.19-13
ii  libgcc1 1:4.9.1-19
ii  libgeoip1   1.6.2-4
ii  libkcmutils44:4.14.2-4
ii  libkdecore5 4:4.14.2-4
ii  libkdeui5   4:4.14.2-4
ii  libkdewebkit5   4:4.14.2-4
ii  libkdnssd4  4:4.14.2-4
ii  libkio5 4:4.14.2-4
ii  libknotifyconfig4   4:4.14.2-4
ii  libkparts4  4:4.14.2-4
ii  libkrosscore4   4:4.14.2-4
ii  libktorrent-l10n1.3.1-3
ii  libktorrent51.3.1-3+b1
ii  libkworkspace4abi2  4:4.11.13-2
ii  libnepomuk4 4:4.14.2-4
ii  libnepomukutils44:4.14.2-4
ii  libphonon4  4:4.8.0-4
ii  libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-network  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-qt3support   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-script   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-sql  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-svg  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtwebkit42.3.4.dfsg-3
ii  libsolid4   4:4.14.2-4
ii  libsoprano4 2.9.4+dfsg-1.1
ii  libstdc++6  4.9.1-19
ii  libsyndication4 4:4.14.2-2+b1
ii  libtag1c2a  1.9.1-2.1
ii  phonon  4:4.8.0-4

ktorrent recommends no packages.

Versions of packages ktorrent suggests:
pn  krosspython 
pn  plasma-widget-ktorrent  

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777729: angband-doc: please make the build reproducible

[Chris Lamb]

Source: angband-doc
Version: 3.0.3.5
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes timestamps from the build system. Once
applied, angband-doc can be built reproducibly in our current
experimental
framework.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad angband-doc.orig/angband-doc-3.0.3.5/debian/local.mk 
angband-doc/angband-doc-3.0.3.5/debian/local.mk
--- angband-doc.orig/angband-doc-3.0.3.5/debian/local.mk2015-02-11 
22:52:45.018078628 +
+++ angband-doc/angband-doc-3.0.3.5/debian/local.mk 2015-02-11 
23:12:24.797397467 +
@@ -38,9 +38,9 @@
   $(LINTIANDIR)/$(package)
$(install_file)  debian/changelog $(DOCDIR)/
$(install_file)  debian/README.debian $(DOCDIR)/
-   gzip -9fqr   $(DOCDIR)
+   gzip -9nfqr  $(DOCDIR)
$(MAKE)  $(INT_INSTALL_TARGET) prefix=$(TMPTOP) \
-  infodir=$(INFODIR)mandir=$(MANDIR)
+  infodir=$(INFODIR)mandir=$(MANDIR) 
GZIP="-9n"
$(install_file)  debian/copyright $(DOCDIR)/copyright
$(install_file)  debian/docentry  $(DOCBASEDIR)/$(package)
$(install_file)  debian/docfaq1   $(DOCBASEDIR)/$(package)_faq1

Bug#777727: authbind: please make the build reproducible

[Chris Lamb]

Source: authbind
Version: 2.1.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes timestamps from the build system. Once
applied, authbind can be built reproducibly in our current experimental
framework.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad authbind.orig/authbind-2.1.1/debian/rules 
authbind/authbind-2.1.1/debian/rules
--- authbind.orig/authbind-2.1.1/debian/rules   2015-02-11 22:52:49.394276949 
+
+++ authbind/authbind-2.1.1/debian/rules2015-02-11 23:05:00.277196045 
+
@@ -83,7 +83,7 @@
$(MAKE) prefix=debian/tmp/usr etc_dir=debian/tmp/etc/authbind \
man_dir=debian/tmp/usr/share/man  install install_man
$(INSTALL_FILE) debian/changelog $(udp)/changelog
-   gzip -9 debian/tmp/usr/share/man/man*/* $(udp)/*
+   gzip -9n debian/tmp/usr/share/man/man*/* $(udp)/*
$(INSTALL_FILE) debian/copyright $(udp)/.
$(INSTALL_SCRIPT) debian/{postrm,prerm,postinst} debian/tmp/DEBIAN
dpkg-shlibdeps ./authbind

Bug#777726: joe: please make the build reproducible

[Chris Lamb]

Source: joe
Version: 3.7-2.4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes timestamps from the build system. Once
applied, joe can be built reproducibly in our current experimental
framework.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad joe.orig/joe-3.7/debian/rules joe/joe-3.7/debian/rules
--- joe.orig/joe-3.7/debian/rules   2015-02-11 22:52:21.433009820 +
+++ joe/joe-3.7/debian/rules2015-02-11 23:01:36.351926648 +
@@ -30,8 +30,8 @@
strip --remove-section=.comment --remove-section=.note 
$(tmp)/usr/bin/joe
 endif
rm -f $(tmp)/usr/bin/termidx
-   gzip -9 $(tmp)/usr/share/man/man1/joe.1
-   gzip -9 $(tmp)/usr/share/man/ru/man1/joe.1
+   gzip -9n $(tmp)/usr/share/man/man1/joe.1
+   gzip -9n $(tmp)/usr/share/man/ru/man1/joe.1
for i in jmacs jstar rjoe jpico; do \
   ln -s joe.1.gz $(tmp)/usr/share/man/man1/$$i.1.gz; \
 done
@@ -43,11 +43,11 @@
 binary-arch: install
install -m 755 -d $(tmp)/usr/share/doc/joe
for doc in README LIST TODO NEWS; do \
-  gzip -9c $$doc >$(tmp)/usr/share/doc/joe/$$doc.gz; \
+  gzip -9nc $$doc >$(tmp)/usr/share/doc/joe/$$doc.gz; \
 done
rm -rf $(tmp)/etc/joe/doc
-   gzip -9c debian/changelog > $(tmp)/usr/share/doc/joe/changelog.Debian.gz
-   gzip -9c ChangeLog > $(tmp)/usr/share/doc/joe/changelog.gz
+   gzip -9nc debian/changelog > 
$(tmp)/usr/share/doc/joe/changelog.Debian.gz
+   gzip -9nc ChangeLog > $(tmp)/usr/share/doc/joe/changelog.gz
install -m 644 debian/help.pl.txt $(tmp)/usr/share/doc/joe/
install -m 644 debian/copyright debian/README.Debian 
$(tmp)/usr/share/doc/joe
install -m 755 -d $(tmp)/DEBIAN

Bug#769106:

[Robert Nelson]

This change is causing issues in debootstrap:

from: debootstrap/debootstrap.log

dpkg: version 2.7.8-3 of libpython-stdlib:armhf already installed, skipping
dpkg: regarding .../python_2.7.8-3_armhf.deb containing python,
pre-dependency problem:
 python pre-depends on python-minimal (= 2.7.8-3)
  python-minimal is unpacked, but has never been configured.

dpkg: error processing archive
/var/cache/apt/archives/python_2.7.8-3_armhf.deb (--unpack):
 pre-dependency problem - not installing python
dpkg: version 2.7.8-3 of python-minimal already installed, skipping
dpkg: version 5.5.1-1 of python-pkg-resources already installed, skipping

Using: debootstrap version: 1.0.67

sudo debootstrap --arch=armhf
--include=alsa-utils,apache2,autoconf,automake,avahi-daemon,bash-completion,bc,bison,bluetooth,build-essential,ca-certificates,connman,cpufrequtils,curl,debhelper,dnsmasq,dosfstools,fakeroot,fbset,file,firmware-atheros,firmware-ralink,firmware-realtek,firmware-zd1211,flex,gdb,git-core,hdparm,hexedit,hostapd,htop,i2c-tools,info,initramfs-tools,iw,libtool,libncurses5-dev,libpython2.7-dev,lightdm,linux-base,locales,lsb-release,lshw,lsof,lzma,lzop,nodejs,nodejs-legacy,npm,openssh-server,openbox,pastebinit,ppp,python-minimal,read-edid,rfkill,rsync,ruby,ruby-dev,screen,ssl-cert,systemd,sudo,tightvncserver,tmux,usb-modeswitch,usbutils,u-boot-tools,v4l-utils,vim,wireless-tools,wget,wpasupplicant,wvdial,xinput,xinput-calibrator,xorg,xserver-xorg-video-fbdev,xserver-xorg-video-modesetting,zd1211-firmware
--components=main,contrib,non-free --foreign jessie
/home/voodoo/git/omap-image-builder/ignore/tmp.hiYMWqz2cd
http://apt-proxy:3142/ftp.us.debian.org/debian/

Sorry, I haven't fully minimized the "--include=" option

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#634079: qelectrotech: the symbols differ depending on the standard, need a tag for it

[Denis Briand]

tags 634079 pending
thanks 

Hello Jonas,
Thank you for your suggestion.
It will be on the next pending version.
Best regards

Denis Briand


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

Bug#777725: taggrepper: please make the build reproducible

[Chris Lamb]

Source: taggrepper
Version: 0.05-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes timestamps from the build system. Once
applied, taggrepper can be built reproducibly in our current
experimental
framework.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad taggrepper.orig/taggrepper-0.05/debian/rules 
taggrepper/taggrepper-0.05/debian/rules
--- taggrepper.orig/taggrepper-0.05/debian/rules2015-02-11 
22:43:34.793144511 +
+++ taggrepper/taggrepper-0.05/debian/rules 2015-02-11 22:47:06.114720683 
+
@@ -83,12 +83,12 @@
$(INSTALL_FILE) -m 644 ChangeLog 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/changelog
$(INSTALL_FILE) -m 644 debian/changelog 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/changelog.Debian
for i in $(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/changelog*;do \
-   gzip -9v $$i; \
+   gzip -9nv $$i; \
done;
$(INSTALL_FILE) -m 644 debian/copyright 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/copyright
$(INSTALL_DIR) $(PACKAGE_DIR)/usr/share/man/man1
$(INSTALL_FILE) -m 644 doc/$(PACKAGE_NAME).1 
$(PACKAGE_DIR)/usr/share/man/man1
-   gzip -9v $(PACKAGE_DIR)/usr/share/man/*/*
+   gzip -9nv $(PACKAGE_DIR)/usr/share/man/*/*
 # Strip binaries
 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
strip -R.note -R.comment $(PACKAGE_DIR)/usr/bin/*

Bug#777720: Suggested debdiff for #777720, #777723 and #777724

[John Paul Adrian Glaubitz]

Hello!

I made the necessary changes to the debian/control file to fix the
dependency issues of cqrlog both when using MySQL and MariaDB
(#20 and #23).

Furthermore, I added xplanet to Recommends in debian/control such
that xplanet is actually available when cqrlog is installed
(#24).

Attaching a debdiff with my suggested changes.

Cheers,
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

diff -Nru cqrlog-1.8.2/debian/changelog cqrlog-1.8.2/debian/changelog
--- cqrlog-1.8.2/debian/changelog	2014-10-04 17:14:15.0 +0200
+++ cqrlog-1.8.2/debian/changelog	2015-02-11 23:30:37.0 +0100
@@ -1,3 +1,17 @@
+cqrlog (1.8.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch order of Recommends mariadb-server and mysql-server in debian/control
+to fix that cqrlog cannot be installed when mysql-server is not installed
+(Closes: #20).
+  * Add mariadb-client as an alternative dependency for cqrlog in debian/control
+to fix the installation when using cqrlog with MariaDB (Closes: #23).
+  * Add xplanet to Recommends in debian/control as cqrlog contains a menu
+shortcut for it in its main window which is otherwise useless
+(Closes: #24).
+
+ -- John Paul Adrian Glaubitz   Wed, 11 Feb 2015 23:01:45 +0100
+
 cqrlog (1.8.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru cqrlog-1.8.2/debian/control cqrlog-1.8.2/debian/control
--- cqrlog-1.8.2/debian/control	2014-07-27 22:01:40.0 +0200
+++ cqrlog-1.8.2/debian/control	2015-02-11 23:27:21.0 +0100
@@ -9,8 +9,8 @@
 
 Package: cqrlog
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libssl-dev, mysql-client, libhamlib2 (>= 1.2.10), libhamlib-utils (>= 1.2.10)
-Recommends: mariadb-server | mysql-server
+Depends: ${shlibs:Depends}, ${misc:Depends}, libssl-dev, mysql-client | mariadb-client, libhamlib2 (>= 1.2.10), libhamlib-utils (>= 1.2.10)
+Recommends: mysql-server | mariadb-server, xplanet
 Description: Advanced logging program for hamradio operators
  CQRLOG is an advanced ham radio logger based on MySQL embedded database. 
  Provides radio control based on hamlib libraries (currently support of 140+ 

Bug#777643: general: possibly, some keyboard layouts should use U+22C5 DOT OPERATOR instead of U+00B7 MIDDLE DOT

[Christoph Anton Mitterer]

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=89092

Since that's the first good valid argument against I feel I should
answer:


On Wed, 2015-02-11 at 21:12 +, Jeremy Stanley wrote: 
> My passwords will stop working. (Okay, not _mine_ specifically, but
> someone's...) Changing the established values in a keymap out from
> under users is
Valid point. But such users might also run into troubles just by
attaching another keyboard.
Or, when you look at the git log of xkeyboard-config, just by some new
update of it.

Actually it seems that these schema changes, seem to happen much more
often than this storm against my report and my person in specifc would
make one believe, see e.g. commits:
f1868bdacb4c227e1daa4088fb28f5968874a38e
1b9901151cdb22e413319e6fca80fbbfc5e51502
99be93b116101921611bbcaa07a59b1de589f4bf
and these were just from the first two sides of the log.


>  foolish when the gains are nearly nonexistent and the
> workaround is relatively trivial for those who actually want to side
> with hobgoblins.
Am I know expected to insult you as well? Guess I'm not up to date, what
Debian's CoC actually demands, it only seems to be usable when being
against me but not for myself ;-)


Anyway, to finally end this ugly matter on the Debian side, I've
forwarded the pointer about this possible issue upstream, so that they
can choose to have what Debian didn't want to do - a proper look at the
matter.

It should be noted for those who seems to accuse me of bad faith, that
I, personally, use a custom keymapping anyway,... so I don't care much
whether it's left as is or not.


Cheers,
Chris.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#769155: kde-workspace-bin: PowerDevil is ignoring battery thresholds

[Andreas Stempfhuber]

Package: kde-workspace-bin
Version: 4:4.11.13-2
Followup-For: Bug #769155
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

I have installed Jessie with the RC1 i386 installer from the first CD on a 
Dell Latitude D620 notebook. It's a standard installation, nothing special. I 
just selected KDE instead of GNOME as desktop environment. To troubleshoot the 
issue I verified that suspend to disk, suspend to RAM and shutdown are 
generally working. To get a better understanding of the issue I enabled all 
notification messages within PowerDevil.

PowerDevil is able to correctly display the battery level. When a power supply 
is connected or disconnected the icon changes accordingly and the 
corresponding notifications are shown.

But battery warning and battery critical thresholds are not working at all. 
The configured thresholds are ignored, notifications are not shown, battery 
critical action (suspend to disk, suspend to RAM or shutdown) is not 
performed. Notebook looses power when battery runs empty.

While searching for a solution I also found other users with this issue: 
https://lists.debian.org/debian-kde/2014/12/msg00025.html

While troubleshooting I found out that when I boot with no battery installed 
and install the battery *after* KDE is started then PowerDevil is working as 
expected.

A notebook relies on the power management capability of the chosen desktop 
environment to avoid data loss and file system corruption when battery runs 
empty.

Thanks

Andreas


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

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 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 kde-workspace-bin depends on:
ii  iso-codes 3.57-1
ii  kde-runtime   4:4.14.2-2
ii  kde-style-oxygen  4:4.11.13-2
ii  kde-workspace-data4:4.11.13-2
ii  kde-workspace-kgreet-plugins  4:4.11.13-2
ii  kscreen   1.0.2.1-1
ii  libc6 2.19-13
ii  libcln6   1.3.4-1
ii  libdbusmenu-qt2   0.9.2-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.1-19
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libice6   2:1.0.9-1+b1
ii  libjpeg62-turbo   1:1.3.1-11
ii  libkactivities6   4:4.13.3-1
ii  libkcmutils4  4:4.14.2-5
ii  libkdeclarative5  4:4.14.2-5
ii  libkdecore5   4:4.14.2-5
ii  libkdesu5 4:4.14.2-5
ii  libkdeui5 4:4.14.2-5
ii  libkfile4 4:4.14.2-5
ii  libkidletime4 4:4.14.2-5
ii  libkio5   4:4.14.2-5
ii  libknewstuff3-4   4:4.14.2-5
ii  libknotifyconfig4 4:4.14.2-5
ii  libkparts44:4.14.2-5
ii  libkpty4  4:4.14.2-5
ii  libkscreensaver5  4:4.11.13-2
ii  libkworkspace4abi24:4.11.13-2
ii  libnepomukcore4   4:4.14.0-1+b2
ii  libpam0g  1.1.8-3.1
ii  libphonon44:4.8.0-4
ii  libplasma34:4.14.2-5
ii  libplasmagenericshell44:4.11.13-2
ii  libpng12-01.2.50-2+b2
ii  libprocesscore4abi1   4:4.11.13-2
ii  libprocessui4a4:4.11.13-2
ii  libqalculate5 0.9.7-9
ii  libqimageblitz4   1:0.0.6-4
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libsm62:1.2.2-1+b1
ii  libsolid4 4:4.14.2-5
ii  libsoprano4   2.9.4+dfsg-1.1
ii  libstdc++64.9.1-19
ii  libstreamanalyzer00.7.8-1.2+b2
ii  libudev1  215-11
ii  libusb-0.1-4  2:0.1.12-25
ii  libx11-6  2:1.6.2-3
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxft2   2.3.2-1
ii  libxi62:1.7.4-1+b2
ii  libxinerama1  2:1.1.3-1+b1
ii  libxkbfile1   1:1.0.8-1
ii  libxrandr22:1.4.2-1+b1
ii  libxrender1   1:0.9.8-1+b1
ii  libxtst6  2:1.2.2-1+b1
ii  phonon

Bug#777724: cqrlog: Should add xplanet to Recommends in debian/control

[John Paul Adrian Glaubitz]

Package: cqrlog
Version: 1.8.2-1
Severity: normal

Hello!

cqrlog contains a shortcut for 'xplanet' in the "Window" menu in
its main window. However, since xplanet is not installed by default
and cqrlog neither depends nor recommends the package, the shortcut
remains without function until xplanet is installed manually.

I suggest adding 'xplanet' to Recommends in debian/control to
fix this.

Cheers,
Adrian


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777723: cqrlog: Not installable with MariaDB as database backend

[John Paul Adrian Glaubitz]

Package: cqrlog
Version: 1.8.2-1
Severity: normal

Hello!

cqrlog is currently not installable with MariaDB as the database
backend. This is caused by the dependency of cqrlog on mysql-client
without an alternative dependency on mariadb-client which is necessary
when cqrlog should be installable with MariaDB instead of MySQL.

To fix it, mariadb-client needs to be added as an alternative dependency
for cqrlog in debian/control: mysql-client => mysql-client | mariadb-client.

Cheers,
Adrian


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#652684: qelectrotech: typo "imn"

[Denis Briand]

tags 652684 confirmed pending
thanks 

hello Jonas,
Thank you for your bug report.
This issue is fixed in next pending version.
Best regards

Denis Briand


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

Bug#682347: mark 'editor' virtual package name as obsolete

[Bill Allombert]

On Fri, Feb 28, 2014 at 08:57:33PM +0100, Bill Allombert wrote:
> On Sun, Jul 22, 2012 at 01:16:08AM +0400, Artem Leshchev wrote:
> > Package: debian-policy
> > Severity: wishlist
> > 
> > Virtual package name 'editor' was removed from Authoritative List of Virtual
> > Package Names in 1996 year, but it is used at our days. Maybe we need to 
> > add it
> > to section "Old and obsolete virtual package names", which is empty? If yes,
> > we need to file a bug against each package that uses it, so this name will 
> > be
> > removed from repository. If no, maybe we need to add it again in the List?
> 
> Hello Artem, 
> As far as I see, no packages Depends/Recommends on "editor", thought there are
> still a number of package that Provides: editor.
> 
> Since the editor virtual package is not defined, bugs should be reported 
> against
> packages that still provides it.

This is the list of packages that 'Provides: editor'

fte-console fte-terminal fte-xwindow
jove 
jupp
le
levee
mg
nano nano-tiny
ne
scite
vigor
vile xvile
vim vim-tiny

Not sure whether it is wortwhile to reort all these bugs.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777722: xdg-open: another command injection vulnerability

[Jiri Horner]

Package: xdg-utils
Version: 1.1.0~rc1+git20111210-7.3
Severity: grave
Tags: security patch
Justification: user security hole

Hi,

there is a long-standing issue with xdg-open on debian -- it parses all files 
it is trying to open. This is easily exploitable. Requirements are similar as 
in last RCE: Window Manager which is _NOT_ one of the following:

* KDE
* GNOME
* MATE
* XFCE
* ENLIGHTENMENT

Problem is caused by name collision in local variables, which are apparently 
not very local in this case (maybe also dash problem?)

Exploit was made from wikipedia image [0].

It would be nice to have it fixed in jessie.

Cheers,

Jiri

[0] 
https://commons.wikimedia.org/wiki/Category:Unidentified_animals#mediaviewer/File:Augochlora_buscki,_M,_Back5,_Puerto_Rico,_Yauco_2014-09-15-18.11.39_ZS_PMax_(16292752499).jpg


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-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)

xdg-utils depends on no packages.

Versions of packages xdg-utils recommends:
pn  libfile-mimeinfo-perl  
pn  libnet-dbus-perl   
pn  libx11-protocol-perl   
ii  x11-utils  7.7+2
ii  x11-xserver-utils  7.7+3+b1

Versions of packages xdg-utils suggests:
pn  gvfs-bin  

-- no debconf information
--- xdg-open.orig	2015-02-11 21:40:42.560282993 +0100
+++ xdg-open	2015-02-11 21:44:10.695894428 +0100
@@ -538,16 +538,16 @@
 
 DEBUG 3 "$xdg_user_dir:$xdg_system_dirs"
 for x in `echo "$xdg_user_dir:$xdg_system_dirs" | sed 's/:/ /g'`; do
-local file
+local desktop_file
 # look for both vendor-app.desktop, vendor/app.desktop
 if [ -r "$x/applications/$default" ]; then
-  file="$x/applications/$default"
+  desktop_file="$x/applications/$default"
 elif [ -r "$x/applications/`echo $default | sed -e 's|-|/|'`" ]; then
-  file="$x/applications/`echo $default | sed -e 's|-|/|'`"
+  desktop_file="$x/applications/`echo $default | sed -e 's|-|/|'`"
 fi
 
-if [ -r "$file" ] ; then
-set -- $(sed -n 's/^Exec\(\[[^]]*\]\)\{0,1\}=//p' "$file")
+if [ -r "$desktop_file" ] ; then
+set -- $(sed -n 's/^Exec\(\[[^]]*\]\)\{0,1\}=//p' "$desktop_file")
 command_exec="$(which "$1" 2> /dev/null)"
 if [ -x "$command_exec" ] ; then
 shift

Bug#749158: qelectrotech: FTBFS with clang instead of gcc

[Denis Briand]

tags 749158 pending
thanks

Hello Alexander,
Thank you very much for your bug report and for your patch.
This issue will be fixed in the next pending version.
Best regards

Denis Briand


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

Bug#777681: slapd deleting attributes fills mdb backend

[GALAMBOS Daniel]

I done some more testing, built from upstream git
branch OPENLDAP_REL_ENG_2_4
tag OPENLDAP_REL_ENG_2_4_40
with config options: ./configure --with-tls=gnutls --enable-ppolicy=yes
--enable-overlays=yes

I could not reproduce the problem with these.

2.4.39 reproducibly has the problem (we recompiled on wheezy the
jessie's openldap when -backports didn't have slapd yet)

I couldn't make wheezy-backports version of slapd to fail like
afternoon. Maybe I missed something afternoon when changed the installed
versions on the test box, or maybe some lib stuck then.

I'll clone a fresh VM and test again.

Dancsa



On 02/11/2015 05:49 PM, Ryan Tandy wrote:
> Hi,
> 
> Sorry, I don't know LMDB well enough to answer your question. I
> recommend asking on the openldap-technical list. I guess they'll suggest
> simply increasing the mapsize, but it would be interesting to know
> whether this is expected and what causes it.
> 
> You may want to try building the OPENLDAP_REL_ENG_2_4 upstream git
> branch (2.4.41 release candidate) to see if it has the same behaviour.
> 
> thanks,
> Ryan


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777691: dbus: Can't logout properly after "service dbus restart"; reboot needed

[Simon McVittie]

On 11/02/15 14:51, Vincent Lefevre wrote:
> When I execute "service dbus restart" as root

Restarting the dbus-daemon other than by rebooting (system bus) or
logging out/back in (session bus) is not a supported action, and
checkrestart should not be recommending it. Yes, I know this is not how
things should be, and in an ideal world it would be fully restartable,
but we do not live in that ideal world.

The ability to restart the system bus without breaking applications
would require a lot of rarely-tested complexity to serialize state, pass
it to the new dbus-daemon, fd-pass the sockets and so on. As far as I'm
aware, nobody has worked on this in the 10ish years since D-Bus was
first written.

The long-term solution is likely to be kdbus, which is part of the
kernel, so you restart it by rebooting (but it isn't affected by any
library updates, because, again, kernel).

> First, when I quit the window manager (fvwm), only the window manager
> quits; the X applications are still running. I suspect that the cause
> is that the X server is still running.

I'm not sure why that would happen. Perhaps bits of lightdm communicate
with each other, or with systemd-logind, via the system bus.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776530: dnsmasq: fails to start when dbus is not installed and running systemd

[Simon Kelley]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 11/02/15 21:56, Simon McVittie wrote:
> On 11/02/15 21:26, Simon Kelley wrote:
>> Thanks, that looks good, but I think that probably the default 
>> --enable-dbus should go as well. It's only there for the previous
>> use with systemd's dbus method. DBus is not enabled by default
>> when dnsmasq is started by sysvinit.
> 
> I wondered about this, but I was a little concerned that it would
> be a regression for any systemd users who are currently
> remote-controlling dnsmasq via D-Bus without having specifically
> enabled it.
If it was also enabled when sysvinit was in use, I'd agree, but a
system which is working as a side-effect of using systemd probably
should be fixed, so it will work with sysvinit too.


> 
> Given that a D-Bus-enabled dnsmasq seems to cope equally gracefully
> with dbus present or absent, is there a cost to enabling it?
> 

There is. Dnsmasq will poll, attempting to create a connection, so
there's some CPU cost.


>> I'll make a patch with that too. Are you happy if I upload it
>> rather than your NMU, to save you grief with my mangled config
>> files :)
> 
> Upload whatever you prefer. I mainly prepared my patch in the form
> of an NMU so I wouldn't have to rebuild and re-test if you asked me
> to NMU it later.
> 
> S
> 

OK. My sid VM is currently updating to allow the test. Will upload soon.


Cheers,

Simon.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU29LrAAoJEBXN2mrhkTWiVwUP/2bDRUk158rS2YoNQqF9BPdm
yPrydm2OMyr+cG5pYQhlcPdXXtVLY1/wd7HAFAbum36tE53APpuSqairdlv/bKRY
bbqyboAqHw04PBqKNJnwkhGuOjXQrkySMXV/tu2CDZjZ+xqGtgB2Nwy+xJKPUpp6
vPSU7FPhXEp1Ik2Bv95mWhRaH9erFL44wbYuUKXYuQeU69vE6Zaj8gQZdQNBVdtP
XOzR4pN75HmVEHFjlCSlQAVec0+mAyCUfEjwbT3yd+be0V6fR0ayF9zr82oRtrEX
sZhhXto14BE5qFwjQUrzqwBn30TuCrucmAC847NXeRbt85wNf2vxmqTMTVcs5J2B
u50Fm1AXFPEwWN8VZMyJOxPXcznNtc5DQgyDgG9r7vNIqLDZewONlbZWIyOERtXX
50YH4ajhzZx5VIjLM1TNEo5hvq+snPqULbd8b4/Py57jMSb5zrZkIHhIDao5nHDT
S040YfTXOGNRObJva+YVcQkPnJb8gTEN05D8nrfucEocvECYxonzZg9q8AwalvAl
XAR8cOnRXDGHpTDbMRgBco0u9Il6g/XjRz3KbEnM1MXYD0NorYMjCL8vyLGERFJ3
luQ6NvrpXM+gaLLKIS/QMD9Sjkxt1UZerylGc/oY6VMBvdA6cLtjmPnkh+n/7sV3
ZAb5girZxA6Bp9HqkJoy
=L8Mk
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777721: softhsm: FTBFS on arm64

[Artur Rona]

Package: softhsm
Version: 1.3.7-2
Tags: patch
Usertags: origin-ubuntu ubuntu-patch vivid

#define PACKAGE_TARNAME "softhsm"
#define PACKAGE_VERSION "1.3.7"
#define PACKAGE_STRING "SoftHSM 1.3.7"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define PACKAGE "softhsm"
#define VERSION "1.3.7"

configure: exit 1
dh_auto_configure: ./configure --build=aarch64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--libexecdir=${prefix}/lib/softhsm --disable-maintainer-mode 
--disable-dependency-tracking --sysconfdir=/etc/softhsm 
--localstatedir=/var/lib --with-botan=/usr --with-pic --enable-64bit 
LDFLAGS=-Wl,-z,defs -Wl,--as-needed returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 25
debian/rules:22: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:19: recipe for target 'build-arch' failed


In Ubuntu, we've applied the attached patch to achieve the following:

- debian/patches/remove-64bit-check.diff:
  + Remove the check for -m64, not needed for package builds.
- debian/rules:
  + Don't use unrecognized build flags on aarch64, resolving FTBFS

We thought you might be interested in doing the same.
diff -Nru softhsm-1.3.7/debian/patches/remove-64bit-check.diff 
softhsm-1.3.7/debian/patches/remove-64bit-check.diff
--- softhsm-1.3.7/debian/patches/remove-64bit-check.diff1970-01-01 
01:00:00.0 +0100
+++ softhsm-1.3.7/debian/patches/remove-64bit-check.diff2014-04-03 
13:59:17.0 +0200
@@ -0,0 +1,13 @@
+Index: b/configure.ac
+===
+--- a/configure.ac
 b/configure.ac
+@@ -63,8 +63,6 @@
+ [SOFTLOGLEVEL=3]
+ )
+ 
+-ACX_64BIT
+-
+ # Check for library include arguments
+ ACX_BOTAN
+ ACX_LIBSQLITE3
diff -Nru softhsm-1.3.7/debian/patches/series 
softhsm-1.3.7/debian/patches/series
--- softhsm-1.3.7/debian/patches/series 2014-12-01 17:52:26.0 +0100
+++ softhsm-1.3.7/debian/patches/series 2014-12-01 22:42:19.0 +0100
@@ -1,2 +1,3 @@
 SUPPORT-101.patch
 002_libtool_export_symbols_fix.patch
+remove-64bit-check.diff
diff -Nru softhsm-1.3.7/debian/rules softhsm-1.3.7/debian/rules
--- softhsm-1.3.7/debian/rules  2014-12-01 17:52:26.0 +0100
+++ softhsm-1.3.7/debian/rules  2015-02-11 00:52:59.0 +0100
@@ -6,7 +6,7 @@
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_HOST_ARCH_BITS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_BITS)
 
-SKIP_64BIT_ON_CPU="alpha ia64 mips64 mips64el"
+SKIP_64BIT_ON_CPU="alpha ia64 mips64 mips64el aarch64"
 
 ifeq ($(DEB_HOST_ARCH_BITS),64)
   # -m64 is not recognized on some architectures

Bug#776530: dnsmasq: fails to start when dbus is not installed and running systemd

[Simon McVittie]

On 11/02/15 21:26, Simon Kelley wrote:
> Thanks, that looks good, but I think that probably the default
> --enable-dbus should go as well. It's only there for the previous use
> with systemd's dbus method. DBus is not enabled by default when
> dnsmasq is started by sysvinit.

I wondered about this, but I was a little concerned that it would be a
regression for any systemd users who are currently remote-controlling
dnsmasq via D-Bus without having specifically enabled it.

Given that a D-Bus-enabled dnsmasq seems to cope equally gracefully with
dbus present or absent, is there a cost to enabling it?

> I'll make a patch with that too. Are you happy if I upload it rather
> than your NMU, to save you grief with my mangled config files :)

Upload whatever you prefer. I mainly prepared my patch in the form of an
NMU so I wouldn't have to rebuild and re-test if you asked me to NMU it
later.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777643: general: possibly, some keyboard layouts should use U+22C5 DOT OPERATOR instead of U+00B7 MIDDLE DOT

[Jeremy Stanley]

On 2015-02-11 16:14:06 +0100 (+0100), Christoph Anton Mitterer wrote:
[...]
> Is there any special reason why you think it would be bad idea?
> Like a use case where people depend on having the MIDDLE DOT and
> which would break if it was changed?
[...]

My passwords will stop working. (Okay, not _mine_ specifically, but
someone's...) Changing the established values in a keymap out from
under users is foolish when the gains are nearly nonexistent and the
workaround is relatively trivial for those who actually want to side
with hobgoblins.
-- 
Jeremy Stanley


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777349: intermittent "size read failed" (clients can lose response data from server)

[Kees Cook]

Hi Ondřej,

On Wed, Feb 11, 2015 at 01:46:59PM +0100, Ondřej Surý wrote:
> Kees,
> 
> thanks for the patch, I have two questions though:
> 
> 1) Do you think it's a jessie material?

I think so -- this problem manifested when I switched from a 3.13 kernel to
a 3.16 kernel. Since Jessie will ship at least 3.16, I think it would be a
good change to backport.

> 2) Has it been submitted upstream?

I have not, no.

Thanks!

-Kees

-- 
Kees Cook@debian.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#625906: qelectrotech: Alignment of "Date" and "File"

[Denis Briand]

tags 625906 confirmed pending
thanks

Hello Jonas,
Thank you for your bug report.
It will be fixed in next pending version.
Best regards

Denis Briand


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

Bug#777720: cqrlog: Not installable unless mysql-client-5.5 is installed manually in advance

[John Paul Adrian Glaubitz]

Package: cqrlog
Version: 1.8.2-1
Severity: normal

Hello!

Attempts to install cqrlog on newly installed systems fail unless the
dependency mysql-client-5.5 is installed manually:



root@z6:~> apt-get install cqrlog
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cqrlog : Depends: mysql-client
  Recommends: mariadb-server but it is not going to be installed or
  mysql-server but it is not going to be installed
root@z6:~> apt-get install mysql-client-5.5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libdbd-mysql-perl libdbi-perl
Suggested packages:
  libmldbm-perl libnet-daemon-perl libsql-statement-perl
The following NEW packages will be installed:
  libdbd-mysql-perl libdbi-perl mysql-client-5.5
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 2,751 kB of archives.
After this operation, 41.7 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.debian.org/debian/ unstable/main libdbi-perl amd64 1.631-3+b1 
[816 kB]
Get:2 http://ftp.debian.org/debian/ unstable/main libdbd-mysql-perl amd64 
4.028-2+b1 [119 kB]
Get:3 http://ftp.debian.org/debian/ unstable/main mysql-client-5.5 amd64 
5.5.42-1 [1,815 kB]
Fetched 2,751 kB in 0s (4,594 kB/s)
Selecting previously unselected package libdbi-perl.
(Reading database ... 432854 files and directories currently installed.)
Preparing to unpack .../libdbi-perl_1.631-3+b1_amd64.deb ...
Unpacking libdbi-perl (1.631-3+b1) ...
Selecting previously unselected package libdbd-mysql-perl.
Preparing to unpack .../libdbd-mysql-perl_4.028-2+b1_amd64.deb ...
Unpacking libdbd-mysql-perl (4.028-2+b1) ...
Selecting previously unselected package mysql-client-5.5.
Preparing to unpack .../mysql-client-5.5_5.5.42-1_amd64.deb ...
Unpacking mysql-client-5.5 (5.5.42-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libdbi-perl (1.631-3+b1) ...
Setting up libdbd-mysql-perl (4.028-2+b1) ...
Setting up mysql-client-5.5 (5.5.42-1) ...
root@z6:~> apt-get install cqrlog
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libhamlib-utils libhamlib2 libssl-dev libssl-doc
Recommended packages:
  mariadb-server mysql-server
The following NEW packages will be installed:
  cqrlog libhamlib-utils libhamlib2 libssl-dev libssl-doc
0 upgraded, 5 newly installed, 0 to remove and 1 not upgraded.
Need to get 10.7 MB of archives.
After this operation, 39.6 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.debian.org/debian/ unstable/main libhamlib2 amd64 
1.2.15.3-2+b1 [398 kB]
Get:2 http://ftp.debian.org/debian/ unstable/main libhamlib-utils amd64 
1.2.15.3-2+b1 [119 kB]
Get:3 http://ftp.debian.org/debian/ unstable/main libssl-dev amd64 1.0.1k-1 
[1,271 kB]
Get:4 http://ftp.debian.org/debian/ unstable/main libssl-doc all 1.0.1k-1 
[1,138 kB]
Get:5 http://ftp.debian.org/debian/ unstable/main cqrlog amd64 1.8.2-1 [7,728 
kB]
Fetched 10.7 MB in 1s (6,219 kB/s)
Selecting previously unselected package libhamlib2.
(Reading database ... 433094 files and directories currently installed.)
Preparing to unpack .../libhamlib2_1.2.15.3-2+b1_amd64.deb ...
Unpacking libhamlib2 (1.2.15.3-2+b1) ...
Selecting previously unselected package libhamlib-utils.
Preparing to unpack .../libhamlib-utils_1.2.15.3-2+b1_amd64.deb ...
Unpacking libhamlib-utils (1.2.15.3-2+b1) ...
Selecting previously unselected package libssl-dev:amd64.
Preparing to unpack .../libssl-dev_1.0.1k-1_amd64.deb ...
Unpacking libssl-dev:amd64 (1.0.1k-1) ...
Selecting previously unselected package libssl-doc.
Preparing to unpack .../libssl-doc_1.0.1k-1_all.deb ...
Unpacking libssl-doc (1.0.1k-1) ...
Selecting previously unselected package cqrlog.
Preparing to unpack .../cqrlog_1.8.2-1_amd64.deb ...
Unpacking cqrlog (1.8.2-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for gnome-menus (3.13.3-5) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Setting up libhamlib2 (1.2.15.3-2+b1) ...
Setting up libhamlib-utils (1.2.15.3-2+b1) ...
Setting up libssl-dev:amd64 (1.0.1k-1) ...
Setting up libssl-doc (1.0.1k-1) ...
Setting up cqrlog (1.8.2-1) ...
Processing triggers for libc-bin (2.19-15) ...
root@z6:~>



Trying to install cqrlog with aptitude gives a more v

Bug#777719: Segfault on DuckDuckGo search with "non official" dillorc

[Yvan Masson]

Package: dillo
Version: 3.0.4-2+b1

Dear maintainer,

If I use a simple dillorc file, dillo crashes when I type a
DuckDuckGo search in the address bar.

You can test this by creating an empty dillorc file :
$ touch ~/.dillo/dillorc

Start dillo, and in the address bar type "dd anything". Dillo will
crash because of a segfault.

The same crash happens if there si only a comment line, or if there is
only one parameters set (for example "panel_size=tiny"), and so on.

However, this does not happen if I use the "official" dillorc file you
can find at http://www.dillo.org/dillorc
Also, if I modify this file to adjust some settings, there are applied
and Dillo does not crash.

Thanks for your time and work,
Yvan


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777718: cpan2deb using wrong module from CPAN

[Damyan Ivanov]

Package: dh-make-perl
Version: 0.84-1
Severity: normal
Tags: upstream confirmed

-=| gregor herrmann, 10.02.2015 21:35:13 +0100 |=-
> On Tue, 10 Feb 2015 19:33:11 +, Andrew Beverley wrote:
> 
> > > % cpan2deb DBIx::Class 
> > 
> > Okay, this is interesting. That command does indeed work correctly for
> > me. However, if I then do cpan2deb DBIx-Class it picks the wrong version
> >   ^^^
> 
> Oh, interesting.
>  
> > So if I use '::' it uses the correct one, if I use '-' it uses the wrong
> > one. Is there a subtle difference between them that I'm not aware of?
> 
> If there is I'd call it a bug :)

Indeed, let's report it as such.

> Let me try as well:
> 
> % cpan2deb DBIx-Class
> == dh-make-perl 0.84 == 
> CPAN: Term::ANSIColor loaded ok (v4.02)
> CPAN: File::HomeDir loaded ok (v1.00)
> Reading '/home/gregoa/.cpan/Metadata'
>   Database was generated on Tue, 10 Feb 2015 16:53:15 GMT
> CPAN: Time::HiRes loaded ok (v1.9726)
> Fetching with LWP:
> ftp://cpan.inode.at/authors/id/A/AB/ABRAXXA/DBIx-Class-0.08195.tar.gz
> CPAN: Digest::SHA loaded ok (v5.88)
> Fetching with LWP:
> ftp://cpan.inode.at/authors/id/A/AB/ABRAXXA/CHECKSUMS
> Checksum for 
> /home/gregoa/.cpan/sources/authors/id/A/AB/ABRAXXA/DBIx-Class-0.08195.tar.gz 
> ok
> 
> Indeed. 
> 
> But:
> 
> % dh-make-perl --cpan DBIx-Class
> == dh-make-perl 0.84 ==
> CPAN: Term::ANSIColor loaded ok (v4.02)
> CPAN: File::HomeDir loaded ok (v1.00)
> Reading '/home/gregoa/.cpan/Metadata'
>   Database was generated on Tue, 10 Feb 2015 16:53:15 GMT
> CPAN: Digest::SHA loaded ok (v5.88)
> Checksum for 
> /home/gregoa/.cpan/sources/authors/id/R/RI/RIBASUSHI/DBIx-Class-0.082810.tar.gz
>  ok
> 
> So same as for you, and the bug is really only in cpan2deb (i.e.
> dh-make-perl called as cpan2deb). Hm? Weird.
> 
> Does anyone on the list quickly see where this comes from? Otherwise
> we should file a bug at least.

The glitch is in DhMakePerl::Config::parse_command_line_options

When run as 'dh-make-perl --cpan Foo-Bar', the $self->cpan value is 
massaged and Foo-Bar is converted to Foo::Bar. When run as cpan2deb, 
no such massaging is done.

This seems to make a difference when requesting the tarball from 
CPAN.pm. Requesting 'DBIx-Class' "module" gets us the stale version. 
Requesting 'DBIx::Class' seems to make it all work as expected.

I have a fix ready and will commit it after I get the bug number.


-- dam


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776530: dnsmasq: fails to start when dbus is not installed and running systemd

[Simon Kelley]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 10/02/15 09:17, Simon McVittie wrote:
> On Mon, 09 Feb 2015 at 16:33:31 +, Simon McVittie wrote:
>> If I was the maintainer, I'd go for option 2, Type=forking, which
>> makes the systemd unit work even more like the init script does
>> now - signalling readiness via the parent process exiting. I'll
>> look into doing a patch at some point.
> 
> See attached. Tested successfully in a jessie 'standard' virtual
> machine with and without dbus.
> 

Thanks, that looks good, but I think that probably the default
- --enable-dbus should go as well. It's only there for the previous use
with systemd's dbus method. DBus is not enabled by default when
dnsmasq is started by sysvinit.

I'll make a patch with that too. Are you happy if I upload it rather
than your NMU, to save you grief with my mangled config files :)


Cheers,

Simon.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU28khAAoJEBXN2mrhkTWirxsP/1Qb8ZZlbx999z1BKKR8OWp6
Gv0/GXWIRYf+1SeIcLio+ukMCl+EhNVgWrtCasbCDBkav1INqOAX7b0StI6Ubeig
SPQtLyaus0NypY1t7vo97nt7y3D3DMYaERqRoKn+gFBbwozMRnDQZ0xdG1OKIxiP
uKz/c4yQ4QfN+YJDGV3gaR7F53pURjs7kyIyFs/8uERMdDQZ55HC+R2YOQEP7Ob4
WfivYrZF+yUwIrYpWhzQSc1HnfynEP8mgBwYTIXpqhz5mLyR6iAJ7vswG2Dbteq8
FuGb83UK9+uGpeYnGbvSZbAhBJNVXnKRvZXNrIHg8+qZWjCRFMJgBJzdkPlLOh+Z
3IhwS3hXqeneyen7ucK/yJWBLw46s3bz2qMXBQaPWvNnzYI8zHUk3GcQubZRYmeW
tM2511Ukhh+4PF/c5PqqSk/lw5ji2ERVYz5GVFgK1ZtHj3ypScjHPqnoVtZMIkad
zSzETJwHWhjVjGk9zjEZHOnd1wbiPSMOPJGyYwbjM0VTtCKnJpb/zgtEE3ny1wPT
nUP9w1bqtQO2cbrjwtTVDpqQ89iceXfru9CvUP0yyacnETvkajtYmESe6Trd6FQY
6WVHFyIDfcvI5SkzRbVmGVmfH16rCq6B/kZVN/NkaKV3jgLs5mrO+WEKXAN1K23u
LixgpogYIuSW0AH43ruB
=qjNN
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777706: nut-monitor: Inform user of compromised passwords

[Ben Armstrong]

Package: nut-monitor
Version: 2.7.2-1.1
Followup-For: Bug #06

Thinking this through a bit more, it's not sufficient to just fix the
permissions on the file. The user should be notified if they have
passwords stored insecurely and warned to change them, as they should
be considered compromised. It would be good if this message continues
to be shown until the user confirms they have taken action. For
example, the file with the compromised passwords could be renamed and
the user asked to delete the file once the passwords are changed to
silence the warning message, though other implementations are
possible.

Ben


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#722075: libc6: getaddrinfo() sends DNS queries to random file descriptors

[Aurelien Jarno]

Control: notfound -1 eglibc 2.13-38+deb7u7
Control: fixed -1 eglibc/2.13-38+deb7u5

On 2015-01-29 23:53, Ben Hutchings wrote:
> Control: retitle -1 libc6: getaddrinfo() sends DNS queries to random file 
> descriptors (CVE-2013-7423)
> Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=15946
> Control: severity -1 serious
> Control: found -1 eglibc 2.11.3-4+deb6u4
> Control: found -1 eglibc 2.13-38+deb7u7
> 
> This bug came up again at
> .  It still
> needs fixing in wheezy and squeeze-lts.

It does NOT need to be fixed on wheezy, as it was already done a few
months ago as part of the 2.13-38+deb7u5 upload:

| eglibc (2.13-38+deb7u5) wheezy; urgency=medium
| 
|   * debian/patches/any/cvs-resolv-reuse-fd.diff: new patch from upstream
| to fix invalid file descriptor reuse while sending DNS query.  Closes:
| #722075, #756343.
|   * debian/patches/any/cvs-CVE-2013-4357.diff: new patch from upstream to
| fix stack overflow issues. Closes: #742925.
|   * debian/patches/any/submitted-CVE-2014-0475.diff: update from upstream
| to fix a localplt regression introduced in version 2.13-38+deb7u3.
|   * patches/any/cvs-dlopen-tls-memleak.patch: new patch from upstream to
| fix a memory leak with dlopen() and thread-local storage variables.
| Closes: #763559.
|   * debian/TODO, debian/debhelper.in/glibc-doc.{install,links,manpage}:
| re-add files lost in the deb7u3 and deb7u4 security upgrades, causing
| the glibc-doc package to be almost empty.
| 
|  -- Aurelien Jarno   Wed, 08 Oct 2014 22:50:01 +0200

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: Digital signature

Bug#775564: upgrade with wheezy org-mode and notmuch OK

[David Bremner]

I just verified that the emacs backport (and thus presumeably the emacs
24 from jessie) can be installed on top of the wheezy versions of
org-mode and notmuch-emacs (either seperately). Byte compilation of apel
does indeed fail with the backports version of emacs.

d


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#709804: RFP: indicator-multiload

[Michaël Malter]

Hello,

I would really like to have this in Debian. The last message is more
than a year old. How can I provide help?

Best,
Michaël


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777649: cgmanager security update for jessie

[Niels Thykier]

On 2015-02-11 19:57, Serge Hallyn wrote:
> Quoting Niels Thykier (ni...@thykier.net):
>> Control: tags -1 moreinfo
>>
>> On 2015-02-11 05:36, Serge Hallyn wrote:
>>> Package: release.debian.org
>>> Usertags: jessie-pu
>>>
>>> A security issue was found in cgmanager, allowing root-owned privileged
>>> containers to fully administer cgroups on the host.  Two other issues
>>> were found which allow cgmanager to be crashed by unprivileged users.
>>> These have all been fixed in sid. The debdiff below, against the current
>>> jessie package, fixes them for jessie.
>>>
>>> debdiff:
>>>
>>> [...]
>>> + 
>>> ++  // Make sure target cgroup is under proxy's
>>> ++  int plen = strlen(pcgpath);
>>> ++  if (strncmp(pcgpath, path, plen) != 0) {
>>> ++  nih_error("%s: target cgroup is not below r (%d)'s", __func__,
>>> ++  r.pid);
>>> ++  return -1;
>>> ++  }
>>> ++
>>> [...]
>>
>> Hi,
>>
>> Is this truly a sufficient test?  The above only tests that pcgpath is a
>> prefix of path.  I do not know exactly what these paths are, so I have
>> to ask.
>>
>> Consider:
>>
>>   pcgpath = "root"
>>   pcpgpath = "root-acually-not-really"
>>   plen = strlen(pcgpath) (= 4)
>>
>> So if only the first plen characters match, they will be considered
>> equal.  If you know, cases like this cannot happen, then it is fine.  I
>> just wanted to double check.
> 
> Thanks, I appreciate the extra set of eyes.
> 
> The situation is that the task making the request (or proxying the request)
> is supposed to be locked under its current cgroup, say /a/b/c.  It's making
> a request pertaining to some cgroup X.  We want to make sure that X is
> under /a/b/c.  Hence the path prefix test.
> 
> thanks,
> -serge
> 

Ok, are we guaranteed that pcgpath ends with the path separator?  Consider:

  "/foo/bar"
  "/foo/bar2/somewhere-else"

Unless the path separator is included in the end (i.e. it always uses
"/foo/bar/" instead of "/foo/bar"), then it might still be possible to
by-pass the prefix test.

~Niels


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777237: Sagemath has special needs

[Bill Allombert]

On Fri, Feb 06, 2015 at 07:08:49PM +0100, Julien Puydt wrote:
> Package: pari-gp
> Version: 2.7.2-1
> Severity: wishlist

Hello Julien,

> While trying to use the debian package in sagemath, it turned out
> two things were lacking to make it work:
> - they use anal.h ;

This is a private header file, there is no good purpose to include in the
binary package. If SAGE really needs it, they should just copy the part
they need. There is not interface garanty anyway.

> - they also have backported patches to add cb_pari_err_handle from
> upstream's repository (see end of this mail).
> 
> Can we get those in debian too?

This patch is breaking the ABI and API, thus this is not possible to
apply it.

Beside SAGE could do the same thing without patching PARI, by
using the standard PARI error trapping mechanism (iferr_env and
global_err_data). This would be much better.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777717: apache2-mpm-prefork: "Permission denied" on unexistent .htaccess

[Victor Porton]

Package: apache2-mpm-prefork
Version: 2.2.22-13+deb7u4
Severity: minor

Dear Maintainer,

It produces errors like the following on unexistent .htaccess files. There 
should be no such message.

[Wed Feb 11 20:05:51 2015] [crit] [client 220.181.108.140] (13)Permission 
denied: /var/www/theses/web/sites/all/modules/ctools/.htaccess pcfg_openfile: 
unable to check htaccess file, ensure it is readable, referer: 
http://theses.portonvictor.org/node/776


-- Package-specific info:
List of /etc/apache2/mods-enabled/*.load:
  actions alias auth_basic authn_file authz_default authz_groupfile
  authz_host authz_user autoindex cgi deflate dir env mime
  negotiation php5 php5_cgi reqtimeout rewrite setenvif ssl status
  suexec suphp
List of enabled php5 extensions:
  curl gd mcrypt mysql mysqli pdo pdo_mysql

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

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

Versions of packages apache2-mpm-prefork depends on:
ii  apache2.2-bin 2.2.22-13+deb7u4
ii  apache2.2-common  2.2.22-13+deb7u4

apache2-mpm-prefork recommends no packages.

apache2-mpm-prefork suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775930: Aw: Re: [lvs-users] [PATCH] ipvsadm: add SCTP support

[support]

> > The ipvsadm Tarball Distribution had been changed  at 2013 , an GIT
> > repro exist since then from
> >
> > http://www.linux-vs.org/software/kernel-2.6/ to
> > https://kernel.org/pub/linux/utils/kernel/ipvsadm
> >
> > Julian, Me and others HAD written Notices to distrib mainta8iners -
> > but that seems been ignored.
> 
> Not arguing here.  I tried to provide some explanation, not an excuse.
> The Debian watch file certainly points to the old location.

I had understand your point allready - and for this "debian BUG" .

The ipvsadm Debian Maintainer & and debian 775930 BUG assignee  allready taken 
this information.

> -- 
> Regards,
> Feri.

maybe i had asked to hard to get that issue fixed - but +5 Years are way too 
mutch .

Thanks you all.
Hopefully some admins enjoy it :)
<>

Bug#777716: [jessie RC1] wireless LAN card not usable, problem with loading/using firmware

[Holger Wansing]

Package: installation-reports


I have a laptop here which needs firmware for the wireless LAN card
Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter (PCI-ID: 8086:1043).

It seems the process of requesting, loading and using firmware is not fully
functional:
When it comes to the d-i step "Detecting network hardware", there is lot of
output on the 4th console regarding 
"BUG: unable to handle kernel paging request at ce8ec00c"
and
"Oops: 0002 [#1]
and
"Call Trace:"
" ? ipw2100_down+0x9e/ox10 [ipw2100]
and the like.

I have attached a syslog of this installation try.

But I am able to proceed with the installation steps, d-i requests firmware
file, so I plug in my usbstick, the relevant firmware package is installed
(the firmware files end up in /lib/firmware), but the device is not able
to operate. It is not shown in the list of available network devices in the
d-i UI.


To investigate this, I started the installation again, but before the step
"Detect network hardware" is started, I mount my usbstick, copy the needed
firmware file into /lib/firmware by hand and then start the step
"Detect network hardware". And now the device is working, it is shown as
available nework device, it scans and shows available WLANs, so the hardware 
seems to work.
So it calms down to the firmware not being available, when the module is loaded.


(Please note, that the needed firmware is detected correctly, and the 
correct package is installed, so the newly created way of detecting missing
firmware seems to work fine!)



Regards
Holger



-- 

Created with Sylpheed 3.2.0 under
D E B I A N   L I N U X   7 . 0   W H E E Z Y !

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



firmware-problem.dmesg
Description: Binary data

Bug#775099: bluetooth: bluethoothd requires 2 starts at boot before reconnecting the devices

[Steven Post]

Hi,

Unfortunately the issue still remains, any help debugging is
appreciated.

Regards,
Steven


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

Bug#772963: release-notes: cellphone friendly CSS

[Stéphane Blondon]

Thank you Niels for the integration into master. :-)


2015-02-11 11:49 GMT+01:00 Osamu Aoki :
>> The main problem with changing the HTML is that it is mostly generated
>> beyond our control.
>
> I would not say this but I agree customizing auto-generated HTML is not
> for the faint hearted (including myself.)

I've seen the XML and XSLT stuff for the maint-guide and I don't plan
to dive in this part.
I agree to maintain and help in the future for CSS patches, not the XSLT part.


> Normal customization xslt file in the source of documentation starts off
> like:
> ... after some standard lines ...
> 
>  href="file:///usr/share/xml/docbook/stylesheet/docbook-xsl/xhtml-1_1/chunk.xsl"/>
>
> But I think this is not something we should do for this late in the
> freeze time.  Let's stick with simple CSS only fix for now.

I agree about this strategy.

I will probalby update the icons for caution, info blocks this week-end.


-- 
Stéphane


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777650: no cryptsetup in initrd when btrfs selected

[jnqnfe]

Control: close -1
Control: archive -1

As identified in bug #777578, btrfs-tools was not installed during the
installation, which was the real cause of the issues I was experiencing.
So on the assumption that a resolution to that issue would successfully
allow cryptsetup to be added to the initrd with a btrfs + luks install,
just as with an ext4 + luks install, I will close and archive this.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767468: [cgmanager] RE: cgmanager: Prevents clean umounts and breaks unrelated software (autofs, e2fsprogs)

[Serge Hallyn]

git://github.com/cgmanager/cgmanager should have a complete fix for this
bug.  I want to test in several scenarios before pushing a package with
those changes.  Anyone who wants to test for themselves can build the
package with the last two patches from the git tree pushed.

After further testing I will release 0.36 upstream and 0.36-1 to sid.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768185: [Pkg-opencl-devel] Bug#768185: mesa-opencl-icd, beignet: installing together breaks all ICDs

[Rebecca N. Palmer]

Not confident I have the hardware you asked to test on .
model name  : Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
Unfortunately you don't: what you've done is confirmed that this bug 
("mesa breaks beignet") is fixed, what I wanted was a test for the 
opposite problem ("does beignet break mesa?"), which requires AMD hardware.



I rebuilt beignet with the patch provided in message #78. It do fix the :
Pass 'SPIR backend: custom loop unrolling pass' is not initialized.
Verify if there is a pass dependency cycle.
Required Passes:
Segmentation fault

issue that I had with 1.0.0-1
That's this bug, so this confirms it is now fixed.  (The fix is included 
in 1.0.1-1, currently in the NEW queue.)



ERROR: clGetKernelWorkGroupInfo(-33)

that I have with 0.9.3~really.0.8+dfsg-1
That's expected: 0.8 only supports Ivy Bridge (ix-3xxx), your hardware 
needs the newer version (which is only in experimental because of the 
release freeze).



With mesa forced I get:[...]
ERROR: clGetDeviceIDs(-1)
Same error if beignet is removed
That's also expected: mesa-opencl-icd isn't supposed to work on Intel 
hardware, the bug was that its being installed broke beignet as well.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#760281: Not fixed

[Serge Hallyn]

git://github.com/cgmanager/cgmanager should have a complete fix for this
bug.  I want to test in several scenarios before pushing a package with
those changes.  Anyone who wants to test for themselves can build the
package with the last two patches from the git tree pushed.

After further testing I will release 0.36 upstream and 0.36-1 to sid.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777578: initramfs-tools: update-initramfs fails with btrfs

[jnqnfe]

On 11/02/2015 18:42, Ben Hutchings wrote:
> So the root (no pun intended) of the problem is that btrfs-tools was
> not installed. Ben. 

Ah ha, you're absolutely right, I assumed it was but it is indeed not
installed. Thanks for that.

Yep, now it boots successfully :D


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777338: Bug#764200: Bug#777338: game-data-packager: please add support for Doom3 BFG

[Tobias Frost]

Am Mittwoch, den 11.02.2015, 09:36 +0100 schrieb Alexandre Detiste:
> Le mardi 10 février 2015, 20:39:21 Tobias Frost a écrit :
> > Am Dienstag, den 10.02.2015, 11:10 +0100 schrieb Alexandre Detiste:
> > > Tobias,
> > > 
> > > Thanks, the only bit still missing in doom3.yaml is the size (in
> > > bytes) of the .pk4 files.
> > > The output of "cksums" is ok too.
> > 
> > Attached.
> > 
> > --
> > tobi
> 
> Hi,
> 
> I see that you miss base/pak008.pk4 , shipped with v1.3.1 patch ;
> found here: http://doom3.filefront.com/file/DOOM_3_Patch
> 
> DOOM3-1.3.1.exe (19Mb) can be read automatically with 7z
> 
> GDP will patch your game automatically to the latest version
> as it already does for several other games like the Quake series,
> Wolfenstein 3D 1.0 etc... when it's implemented.

:)
Yes, I didn't install any patches, the files were directly from the DVD
that I just pulled out of the shelf to calc the sums

> 
> Do you have sums for the expansion, only d3xp/pak000.pk4,
> d3xp/pak001.pk4 is also in the patch?
> 
>   doom3-resurrection-data:
> longname: 'Doom 3: Resurrection of Evil'
> expansion_for: doom3-data
> steam:  
>   id: 9070
> install_to: usr/share/games/doom3
> install:
> - d3xp/pak000.pk4
> - d3xp/pak001.pk4

Also, those are also from the DVD:
tobi-> ls
game01.pk4  game02.pk4  game03.pk4  pak001.pk4
[/media/cdrom/Setup/Data/d3xp]
tobi-> cksum *
691409431 1645741 game01.pk4
255066 1888500 game02.pk4
1141627363 1035335 game03.pk4
1892025358 99336 pak001.pk4
[/media/cdrom/Setup/Data/d3xp]
tobi-> md5sum *
5a83710af3530b4fb4ed86c19b9a1b2a  game01.pk4
4ecfcd51e4b45534fc1968b1b69619d4  game02.pk4
eb9b5260b8695a764832a30e32ded796  game03.pk4
06fc9be965e345587064056bf22236d2  pak001.pk4
[/media/cdrom/Setup/Data/d3xp]
tobi-> sha1sum *
97d21648b424f1f6f8c11456166fd6e38e24abe0  game01.pk4
22c7f6117043b2ddd10d9076336cce67bfd15a90  game02.pk4
46230705a87cf88f1fa4a6094abc3c7cdf1ab428  game03.pk4
0d9ca3d4532c0d412fbb64ab2885f52ef8852594  pak001.pk4
[/media/cdrom/Setup/Data/d3xp]
tobi-> sha256sum *
915c2a7cbfce211069415bc83e64de617e8accf4643dc023931fb1317b175104
game01.pk4
2bd0eab08bada630c9322789cbca844a335da4c7dd6ea7cfd836dee72b047252
game02.pk4
f07871570b18617d1b2692360102e0509a1e7aaeca755e879fb2ca9f1cc54018
game03.pk4
2ba245254b8ed3440e252f6e2e24af2c6343d7c312f9a9a7e73509abdaf13e49
pak001.pk4

Note, there's no pak000 on the DVD...

On the DVD are also severval localization... Interested in those as
well?

--
tobi


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org