Bug#774006: RFP: libinline-python-perl -- write Perl subs and classes in Python

[tony mancill]

Package: wnpp
Severity: wishlist

* Package name: libinline-python-perl
  Version : 0.46
  Upstream Author : Stefan Seifert 
* URL : https://metacpan.org/release/Inline-Python
* License : The Perl 5 License (Artistic 1 & GPL 1)
  Programming Lang: Perl
  Description : write Perl subs and classes in Python

 Inline::Python is a module that allows one to write Perl subroutines
 in Python.
 .
 The Inline module supports multiple programming languages and each
 language has its own support module. This module allows one to use
 Inline with the Python programming language.


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

Bug#774005: RFP: photoflow -- A fully non-destructive photo retouching program providing a complete layer-based workflow including RAW image development.

[Alex Rozenshteyn]

Package: wnpp
Severity: wishlist

* Package name: photoflow
* URL : http://aferrero2707.github.io/PhotoFlow
* License : GPLv3
  Programming Lang: C++
  Description : A fully non-destructive photo retouching program providing 
a complete layer-based workflow including RAW image development.

The aim of the project is to provide a fully non-destructive photo retouching 
program that includes a complete workflow from RAW image development to 
high-quality printing.

Here is the general feature (wish)list:

  * Fully non-destructive, layer-based photo editing workflow with realtime 
preview of the final image
  * Support for 8-bits and 16-bits integer as well as 32-bits and 64-bits 
floating point precision, selectable at runtime and on a per-image basis
  * Plugin-based architecture: new tools can be implemented as separate modules 
that are loaded at runtime
  * Allows to load and edit images of arbitrary size, thanks to the underlying 
rendering engine based on the VIPS library
  * Fully color managed workflow: user-defined input, work and output profiles, 
soft-proofing, etc...
  * Support for layer grouping and layer masks
  * Support for common photo editing tools: levels, curves, brightness-contrast 
control, blurring, sharpening, cropping, resizing, colorspace conversions, 
etc..., all implemented in the form of image layers
  * User-friendly interface to develop new tools and image filters as external 
plugins

You can follow the development of photoflow and learn about its usage in the 
dedicated blog: http://photoflowblog.blogspot.fr/


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

Bug#774004: man page typo

[Joey Hess]

Package: posh
Version: 0.12.3
Severity: minor

   "++"
   similar to ++, except the parameter is decremented by 1.

-- 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/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages posh depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  libc6  2.19-13

posh recommends no packages.

posh suggests no packages.

-- debconf information excluded

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#774003: new upstream (2.14)

[Daniel Baumann]

Package: calibre
Severity: wishlist

calibre 2.14 is available.

-- 
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#774002: nagstamon: missing dependency on python-keyring, python-secretstorage

[Paul Wise]

Package: nagstamon
Version: 1.0.1-1
Severity: normal

I noticed by running nagstamon in a terminal that it is missing a
dependency on the python-keyring and python-secretstorage packages:

$ nagstamon
Traceback (most recent call last):
  File "/usr/share/nagstamon/Nagstamon/Config.py", line 673, in KeyringAvailable
import keyring, secretstorage
ImportError: No module named secretstorage
Traceback (most recent call last):
  File "/usr/share/nagstamon/Nagstamon/Config.py", line 673, in KeyringAvailable
import keyring, secretstorage
ImportError: No module named secretstorage
Traceback (most recent call last):
  File "/usr/share/nagstamon/Nagstamon/Config.py", line 673, in KeyringAvailable
import keyring, secretstorage
ImportError: No module named secretstorage

(process:21828): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed

(process:21848): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
^CTraceback (most recent call last):
  File "/usr/bin/nagstamon", line 164, in 
gtk.main()
KeyboardInterrupt

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages nagstamon depends on:
ii  librsvg2-common   2.40.5-1
ii  python-beautifulsoup  3.2.1-1
ii  python-gtk2   2.24.0-4
ii  python-notify 0.1.1-4
ii  python-pkg-resources  5.5.1-1
pn  python:any
ii  sox   14.4.1-5

nagstamon recommends no packages.

Versions of packages nagstamon suggests:
ii  gnome-terminal   3.14.1-1
ii  rdesktop 1.8.2-3
ii  xtightvncviewer  1.3.9-6.5

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#773766: systemd: Real problem is lack of information when service fails

[Michael Biebl]

Am 26.12.2014 um 06:11 schrieb Daniel Dickinson:
> 
> 
> On 25/12/14 01:27 PM, Michael Biebl wrote:
>>>
>>> Messages appeared in journal (journalctl) however there was no output
>>> in
>>> syslog.  I have noticed that *none* of the boxes / vms I have upgraded
>> >from wheezy to jessie output the journal to syslog.  I suppose this may
>>> be a systemd upgrade bug.
>>
>> Which syslogger do you have installed, rsyslog, syslog-ng? 
>>
> rsyslog with config that had been edited but reverted to defaults
> (however probably detected as changed and therefore new defaults not
> installed).

What is the output of
systemctl status syslog.socket syslog.service


-- 
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#742048: systemd-remount-fs.service fails for split-usr

[Michael Biebl]

Am 27.12.2014 um 02:44 schrieb Michael Biebl:
> It looks like we won't get initramfs-tools 0.118 with usr-mount support
> in the initramfs, as this created quite a few regressions which need to
> be dealt with first.

... for jessie, I meant to say.

> 
> I therefore think we need to workaround this issue in systemd and make
> sure systemd-remount-fs.service doesn't fail for split-usr setups.
> So marking this bug as RC and bumping the severity to serious.
> 



-- 
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#742048: systemd-remount-fs.service fails for split-usr

[Michael Biebl]

control: severity -1 serious

On Tue, 18 Mar 2014 17:11:37 +0100 Michael Biebl  wrote:
> Package: systemd
> Version: 204-7
> Severity: normal
> 
> I've setup a jessie test VM with a LVM/split-partition configuration,
> i.e. a separate partition for /home, /usr/, /var and /tmp (as created
> by the installer)
> 
> The systemd-remount-fs.service fails:
> 
> Mär 18 17:00:41 debian systemd[1]: Starting Remount Root and Kernel File 
> Systems...
> Mär 18 17:00:41 debian systemd-remount-fs[295]: mount: /usr not mounted or 
> bad option
> Mär 18 17:00:41 debian systemd-remount-fs[295]: /bin/mount for /usr exited 
> with exit status 32.
> Mär 18 17:00:41 debian systemd[1]: systemd-remount-fs.service: main process 
> exited, code=exited, status=1/FAILURE
> Mär 18 17:00:41 debian systemd[1]: Failed to start Remount Root and Kernel 
> File Systems.
> Mär 18 17:00:41 debian systemd[1]: Unit systemd-remount-fs.service entered 
> failed state.
> Mär 18 17:00:41 debian systemd[1]: Starting Local File Systems (Pre).
> 
> Earlier, systemd already complained:
> Mär 18 17:00:40 debian systemd[1]: /usr appears to be on its own filesytem 
> and is not already mounted. This is not a supported setup. Some things will 
> probably break (sometimes even silently) in mysterious ways. Consult 
> http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more 
> information.
> 
> 
> System seems to boot fine and /usr is mounted, so I'm not sure if it's
> worth spending effort on this and we should rather push to get
> initramfs-tools updated to mount /usr for us.
> 
> The problematic bits seem to be at [0]
> 
> Michael
> 
> [0] 
> http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=blob;f=src/remount-fs/remount-fs.c;hb=HEAD#l82


It looks like we won't get initramfs-tools 0.118 with usr-mount support
in the initramfs, as this created quite a few regressions which need to
be dealt with first.

I therefore think we need to workaround this issue in systemd and make
sure systemd-remount-fs.service doesn't fail for split-usr setups.
So marking this bug as RC and bumping the severity to serious.

The patch might be as simple as the attached one. But we'll need to
check if it doesn't cause any regressions with dracut and
initramfs-tools 0.118, which actually do mount /usr in the initramfs.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff --git a/src/remount-fs/remount-fs.c b/src/remount-fs/remount-fs.c
index 847637a..44cc959 100644
--- a/src/remount-fs/remount-fs.c
+++ b/src/remount-fs/remount-fs.c
@@ -77,10 +77,9 @@ int main(int argc, char *argv[]) {
 int k;
 char *s;
 
-/* Remount the root fs, /usr and all API VFS */
+/* Remount the root fs and all API VFS */
 if (!mount_point_is_api(me->mnt_dir) &&
-!path_equal(me->mnt_dir, "/") &&
-!path_equal(me->mnt_dir, "/usr"))
+!path_equal(me->mnt_dir, "/"))
 continue;
 
 log_debug("Remounting %s", me->mnt_dir);


signature.asc
Description: OpenPGP digital signature

Bug#771661: machine is completely unusable

[Ben Hutchings]

On Tue, 2014-12-09 at 22:51 +, Toni Mueller wrote:
> 
> 
> Hi Ben,
> 
> On Tue, Dec 09, 2014 at 06:11:09PM +, Ben Hutchings wrote:
> > Also, this is assigned to linux-image-3.16-0.bpo.3-686-pae but the
> > screenshot you attached shows that package being newly installed.
> > Therefore it is not the kernel you were running at the time you first
> > saw this problem.
> > 
> > Did you subsequently boot into that kernel?
> 
> yes, the problem occurred with the 3.16-bpo kernel several times, basically
> each time I tried to run it, but so far never that early.
> Today the machine just locked up this way during or shortly after boot (I did
> not have a console for it when it happened).
> 
> Should I create another screen shot when the problem happens next time?

I don't think a screen shot will provide enough information.

> > We would need a more complete kernel log.  You could use an emulated
> > serial console to get this.
> 
> What exactly do you want? I mean, at this point I am almost confident to
> unfortunately reproduce the problem soonish.

1, Enable an emulated serial port for the VM, with output going to a
file.
2. Enable a serial console on the kernel command line.
3. Set sysctl kernel.printk=7 (i.e. send all non-debug logging to the
console).
4. Do whatever you have to do, to reproduce the hang.

Then send us the file with the console output.

> > How much memory does this VM have?  Does it have a swap file?
> 
> 1638400
> 
> It has a swap partition, but no separate swap file.

Sorry, I meant swap partition.  Anyway, it is not very small which was
one possibility I had thought of.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.


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

Bug#770281: dh-systemd: dh_systemd_enable --no-enable not working as expected

[David Lechner]

As you wrote, systemclt status says:

>Loaded: loaded (/lib/systemd/system/spamassassin.service; disabled)

So, the service is "disabled" as expected. I think what you want in 
addition to "dh_systemd_enable --no-enable" is "dh_systemd_start 
--no-start" so that the service does not start when it is installed.



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

Bug#772855: installation-reports: unable to connect to a wifi network on channel 13

[Ben Hutchings]

On Sat, 2014-12-13 at 21:51 +0100, Lukasz Stelmach wrote:
> On 11.12.2014 21:57, Ben Hutchings wrote:
> > On Thu, 2014-12-11 at 19:28 +0100, Łukasz Stelmach wrote:
> >> Package: installation-reports
> >> Severity: important
> >>
> >> Dear Maintainer,
> >>
> >> I downloaded Debian 7.7 installation image[1].
> >>
> >> I followed the installation procedure and chose wlan0 networki interface
> >> when asked to configure the primary network interface. Then there was no
> >> WLAN on the list of availble networks. It appeared after I changed
> >> channel on my AP from 13 to 1.
> >>
> >> I suspect the reason of this problem MAY be the default regulatory
> >> settings of wifi stack/card driver in the Linux kernel if it is prepared
> >> for the USA where, according to Wikipedia[2], the channel may be used
> >> only under certain conditions.
> >>
> >> [1] debian-7.7.0-amd64-i386-netinst.iso (md5 
> >> afc576c3886f9abab9ba886c4cd51a88) 
> >> [2] https://en.wikipedia.org/wiki/List_of_WLAN_channels
> > 
> > The default is to use the 'world' regulatory domain, not the US domain.
> > This still allows scanning for and using an AP on all channels; it just
> > doesn't allow transmissions above channel 11 until an AP is found.
> > 
> > However this might be overridden based on the country setting of the
> > wireless network adapter.
> 
> That's strange, apparently the card has been prepared to be for
> Australians, who can use channel 13.
> 
> --8<---cut here---start->8---
> Dec 13 18:15:35 main-menu[392]: INFO: Menu item 'ethdetect' selected
> Dec 13 18:15:36 kernel: [  112.707682] cfg80211: Calling CRDA to update world 
> regulatory domain
> Dec 13 18:15:36 kernel: [  112.716130] ath9k :03:00.0: setting latency 
> timer to 64
> Dec 13 18:15:36 kernel: [  112.723098] ath: EEPROM regdomain: 0x21
> Dec 13 18:15:36 kernel: [  112.723101] ath: EEPROM indicates we should expect 
> a direct regpair map
> Dec 13 18:15:36 kernel: [  112.723103] ath: Country alpha2 being used: AU
> Dec 13 18:15:36 kernel: [  112.723104] ath: Regpair used: 0x21
> Dec 13 18:15:36 kernel: [  112.726937] ieee80211 phy0: Selected rate control 
> algorithm 'minstrel_ht'
> Dec 13 18:15:36 kernel: [  112.727445] Registered led device: ath9k-phy0
> Dec 13 18:15:36 kernel: [  112.727450] ieee80211 phy0: Atheros AR9485 Rev:1 
> mem=0xc90011a0, irq=30
> Dec 13 18:15:38 kernel: [  115.279119] ADDRCONF(NETDEV_UP): wlan0: link is 
> not ready
> Dec 13 18:15:40 main-menu[392]: INFO: Menu item 'netcfg' selected
> --8<---cut here---end--->8---

This driver uses a table of maximum TX power per channel in the wireless
controller's EEPROM.  It looks like when the 'regpair' value is 0x21
then it expects to find ETSI rules for the 2.4 GHz band, allowing use of
channel 13, but it might not.

Does the interface work on channel 13 after installation?  (And assuming
that you install crda.)

[...]
> > Also please provide the system log from the installer.
> 
> There is probablo nothing more interesting there than the above excerpty
> but I am attaching it anyway.

Right, I didn't see any extra clues there.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.


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

Bug#773970: Monkeyscan fails at launch

[Hugo Roy]

Thanks for your prompt answer!

Here's what I get trying to sign my own key. I didn't see anything
confidential there, I hope I'm not mistaken ☺ 


hrd@xps ~ (git)-[annex/direct/master] % monkeysign 
EBE6F998953CBD94FFA4E6718D022C99B3D7B795 --debug
command: ['gpg', '--command-fd', '0', '--with-fingerprint', '--list-options', 
'show-sig-subpackets,show-uid-validity,show-unusable-uids,show-unusable-subkeys,show-keyring,show-sig-expire',
 '--armor', '--status-fd', '2', '--quiet', '--batch', '--fixed-list-mode', 
'--no-tty', '--with-colons', '--use-agent', '--export', 
'EBE6F998953CBD94FFA4E6718D022C99B3D7B795']
ret: 0 stdout: -BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2

mQENBFG7EkABCADj4HbUFARMEjsZtvTV7/byacXDPmILAvE6Dv0DBTJpWy2oCrCD
sja7zUkOyrzlBWeYtVqUVgWyH7HW8DV9TekfwDYA4hbeW0BmWQx3Cm43rlklfCQg
5ECgBxm+sqW8gqrYXuI9Bw/FxlZUH7KrPCsssVdrVbG7DqWrfzonv23S714IHUnt
C59voH761qH2gHw9g+pFDdgQpY5u8GyJmfEPHJnNyHTy1Rd3euk969wh2Etqrha9
nGP5++6wFgIzKIA/I+OMfHXrZh50KBCZGGpUt6Mq/9HYrAqxu/shxS4xOcp3FhAF
PtmM1yMHgyAHIkeuMyaaYoKa49Jg2AXIsVwxABEBAAG0GEh1Z28gUm95IDxodWdv
QGZzZmUub3JnPokBPgQTAQIAKAIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AF
AlG7EpUFCQWkGqAACgkQjQIsmbPXt5VuVAf/eUd98Vc1sbGGqr39nr/yPuCshxDy
HFbQIjb6CSnjqezfrmzPm/0B/dluNIXKXhRYAhQYYpjEjG8PJNuv+6l9Qf+h2dvQ
vEAsiqxr9LLISLRKtwRHuhT5iv3rfG8eY0YFMft3bYDq+SFikOXLs3HXnp80OK2k
Xaue2MhlULVwG6Gb0kvcIawH9d4h9h6tlL6jR2p91SDa6Zl6NPI0DDUZedq7qF+J
TJfjyAhNHkr4YhPHnZrTvAiR3IXzJP2NfoDQ6GUUpffvijxTwsbzZhx0P7cSjr/b
uMbJXD3zJizjLtAFJU8Q//kLyIRPEJn4uUyp+KRC/ftne5Axx4sRMFLDOYkBQQQT
AQIAKwIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AFCQWkGqAFAlG7EtkCGQEA
CgkQjQIsmbPXt5UH3wf+KjsLlsgf0Lx9uyFeyYF9rGdK22MIoRwZgd7CnqcdbJfw
2cGvflhZuTRrHa63mwipVNR9WOHOp0PpPD9L8ouiUS/6k8mP1cMw3samv4eAeavT
nCNfsXLUuzlwAgeHIG5cwPh4SoWRQDwi9Lr0Vjdlj+Aa6O2edYwV3ZXZA9wPLRJX
Dp6n5pqVPt3XhZ/gicEoKK9LuolIWYuRrvTBdvdxNUxixcIkpKPXxdFAbezEMCwP
lmC+WepxIo8MT2Ce+/sIuSF7pnZJaq6p+X/8CUjsGeXQzybqEuxOovBsHQJQrAP7
o+iP9R8tjneCdoDbRhO+XATnTd/q6A4fGHCbSLat64kCHAQQAQIABgUCU7vKyAAK
CRB6mBAiqm7K/C/yD/9KNj8zJcI9654FMilKMej8fehwpa9sKduOCJIYPUU6/tyY
A6wPek3c10FXb7+U0jTxDWx9OfmdWArsfdEvZGHBnoideYZj1a4nwx+JcubbN2c7
tBcCDJK+kkq560g+V+csdJfDKdELF3xa+eOdhXq+popPof1StBJwYa8yAwszxnjD
GYR6xduaVOEdUrmd7smFs8EbvT9QGFnVj3TCGURKECu9MTKd3AsPeWmq8oJIn408
0Z3FJNQIJCqS3iBW7Wdw3pSpTeASPTkCbMr69lX2Vs7OWhyZVAsnXV1ZHe9Zy2sU
nm4AhMnQNiuuta8ISv0qIQ0ecH0Z6IjuXt+J+h3baWXSDNPo23zJSjeVPtGvx6QK
te8qjQxzV2Vx3wOjKxRW+4v5eAE8myNCIm+ZClFb/n786spZ1cbhbjT0TSNhMaKS
cwFgLRihxqehsiX82qMrkuWYsTkfQhYGKBcLAkCE0FsifPXZdDPZm0zeAe8r6Pfc
DfNEWBp96vYFXmNMOhX1t1bsMBIjMZFCLPM2xIgwBGa6IB7oXP2UzeYQDqL86LlY
Wf9zMMUyRA4VJ/dV4dnyXftq+clXLeUwatUDa3HLcskjsWVpcXa2VdNx3wqpfUf/
7vxKLcb8mXKDoCd8JvoNS2Q3KWgPoGgvJ9j4HSHNFn7chTMRXU/a2qqVedS/uNHM
FswUARAAAQEAAAD/2P/gABBKRklGAAEBAAABAAEAAP/bAEMACAYG
BwYFCAcHBwkJCAoMFA0MCwsMGRITDxQdGh8eHRocHCAkLicgIiwjHBwoNyksMDE0
NDQfJzk9ODI8LjM0Mv/bAEMBCQkJDAsMGA0NGDIhHCEyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMv/AABEIAIcAhwMBIgAC
EQEDEQH/xAAfAAABBQEBAQEBAQAAAQIDBAUGBwgJCgv/xAC1EAACAQMD
AgQDBQUEBX0BAgMABBEFEiExQQYTUWEHInEUMoGRoQgjQrHBFVLR8CQzYnKC
CQoWFxgZGiUmJygpKjQ1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2
d3h5eoOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK
0tPU1dbX2Nna4eLj5OXm5+jp6vHy8/T19vf4+fr/xAAfAQADAQEBAQEBAQEB
AQIDBAUGBwgJCgv/xAC1EQACAQIEBAMEBwUEBAABAncAAQIDEQQFITEGEkFR
B2FxEyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RF
RkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqi
o6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2dri4+Tl5ufo6ery8/T1
9vf4+fr/2gAMAwEAAhEDEQA/APLUsmbPzj8qguDtUp/dOK1bl0gVSRjJ7CsC4l3S
SEE4LE/rUR1LaSRGx+cmkzTSaUGtDIlUVMnBqFav21hPKxChemeTSHYsWbZkQe1d
HZNi3Ue5qpZWQhEbSRxnC88A1qxeXtCqoHpgUOaQKncsQN8uPes7xFpL3KW4Eqrt
LdR9KulhEQDx34q5BNFLu80b8dNwzis3O5ag4s8tmTy5HQnJViM1XY9a9Fv9GivF
Zba1txIX3E7AOPyrmr/w5eQ+a5jiCrjo1NSRTj2ObJ5oBq3LZSxEhgvAz1qvsI9K
u5m0WLdfOZgOMCrL2bFPviqUTGMk5Iz6VY3yFQd7Y+tZyv0JWhDJ+5kKHkjvRTmG
7Jbk+popodizfXbSIg8zOD6VnFiScmnzHIFQ1aVgbuOzTlBpg61Mgzj60xFmCNWD
bhWgLl4hmF8N0PGeKpRZUHilJkHRSfwqWy0jWtdUl81VmnGzHOQP8K6fTZbOe2Rt
6tISQOT615/+8LfcOfoa2dLu7mBYVWIYDZ5U+tRLYtXudv8AZIZI2YpkgHBya5Y3
t4n+qkIz1+UVrR6vciJhsj5/2T/jWKu7uv6VEdzR7G3bT3UgXymJk25OAKmFnd3E
n+lRM0LfezgfyqTTYBGyyR7mYpyOvpXRpAHsgWyGI5H41MpWYRVzi9T0CIwzSQ2h
IWIkEMeuD71wd3BJbsodCmR3r2eSDMbQYbY4Kk98GvPfGumQ2NzaLEZCGRidxz3+
lOFTWw5U7xOaMavxEMnvikYsq4PGOKdaPsdunTvSzgFS2eSa1e5ykW7IzmihFBxk
0UaBcr0HgUoFN6nFaCHKM4NTI23H1qNRwKdRcDQtm84NxjFbsGlCT/lsRxn7tZug
R+Ys/Tgr1/Gu1ggI/u9K5qkrM7sPBNXZjR6GN4P2g/8AfH/16uJpwiTHm5x/s1rr
EQB0pHiPJ4rLmZ1qETIMO3jd+lQTx7AOc5rWeAtyCKpy27YHIp3JcURWfiM2E24W
ofC7fv4/p7V1enaub6GGQwbPMGcbs4/SvObyBkLHcPvVueGZ9uoWcZLHG76dDT0a
OaonF6Hcs+QTjtXnvj+TF3Zcf8s2/mK7e9nVQ/B+4a838YS+dc2pGeEbr9amC94H
8JzNOLZGMU5fm6UiL+8NdZxjNvfNFWTESm7IoqboLFEmgDmk609a0JHDpSE80tNb
rQM2dCnEaz5YjJX+tdINYijAJnYduhrmdBh85Z/lJwV6fjWvPp0mwYgfr6Gsalrn
VQbtodBaanDPsVZWLEdwaZf6gsXmIJWDBewNUdJtXS6i3RMFCnqPanapb7rtwEJB
A/lWDVmdcXJootqU7crcSY+tMj1GR87p3OPWpI7HKnETVZtdITLboHHTuau6MWp3
LsGmPqKrHDCruV3nJA/n9a

Bug#774001: ${#@} and ${#*} are incompatable with bash and posh

[Joey Hess]

Package: dash
Version: 0.5.7-4+b1
Severity: normal

joey@darkstar:~>cat testcase 
#!/bin/sh
echo ${#@}

joey@darkstar:~>bash testcase a
1
joey@darkstar:~>posh testcase a
1
joey@darkstar:~>dash testcase a
1

good so far...

joey@darkstar:~>bash testcase a b
2
joey@darkstar:~>posh testcase a b
2
joey@darkstar:~>dash testcase a b
3

!! 

joey@darkstar:~>bash testcase a b c
3
joey@darkstar:~>posh testcase a b c
3
joey@darkstar:~>dash testcase a b c
5

joey@darkstar:~>bash testcase aaa bbb 
3
joey@darkstar:~>posh testcase aaa bbb 
3
joey@darkstar:~>dash testcase aaa bbb 
12


posh:
   ${#name}
   The number of positional parameters if name is *, @ or is
   not specified, or the length of the string value of
   parameter name.

bash:

${#name[subscript]}  expands  to  the  length  of  ${name[sub‐
   script]}.  If subscript is * or @, the expansion is the number
   of elements in the array.

dash:

 ${#parameter} String Length.  The length in characters
   of the value of parameter.

So dash's documentation doesn't specify what it does for ${#@}. What its
actually doing is taking the length of the string consisting of all the
positional parameters, separated by spaces.

I have not checked if the behavior of ${#@} is standardized in any way.
If ${#@} is standardized, then dash should follow the standard.

Currently, a #!/bin/sh script cannot currently safely use ${#@}, because
/bin/sh can be dash or bash. If some package contains a #!/bin/dash
script, it could rely on the current behavior. OTOH, the behavior is
undocumented, and seems pretty useless, so it's unlikely someone would
go to the bother of using #!/bin/dash to get it. This might argue for
changing the behavior to match bash and posh even if there is not a
standard.

On the other hand, $# reliably yields the number of positional parameters
in all of bash, posh, and dash. So any script can use that. So, the easiest
fix would be to just document on its man page the special way bash handles
${#@} (and ${#*})

-- 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/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dash depends on:
ii  debianutils  4.4+b1
ii  dpkg 1.17.22
ii  libc62.19-13

dash recommends no packages.

dash suggests no packages.

-- debconf information excluded

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#698504: system-config-printer: permission problem though added to lp group

[Luca Capello]

Hi there!

On Sat, 27 Dec 2014 00:05:11 +0100, Luca Capello wrote:
> On Tue, 04 Feb 2014 20:49:02 +0100, Claudio Laurita wrote:
> > I can confirm this bug in debian wheezy 32 bit too (with mate 1.6.0 desktop,
> > kernel 3.11 i386).
> > system-config-printer version 1.4.3-1
> > cups 1.7.1-2
> 
> The problem resides in cups-pk-helper, which does not respect CUPS
> 'SystemGroup lpadmin' privileges as per /etc/cups/cups-files.conf.

The discrepancy seems to be an upstream decision, whose resolution is
left to each distribution:

  

Thx, bye,
Gismo / Luca


signature.asc
Description: Digital signature

Bug#703582: fixed upstream

[Micha Lenk]

forwarded 703582 https://github.com/spacewalkproject/spacewalk/pull/176
tags 703582 + fixed-upstream
thanks

This issue got fixed upstream.


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

Bug#698504: system-config-printer: permission problem though added to lp group

[Luca Capello]

reassign 698504 cups-pk-helper
found 698504 0.1.0-3
found 698504 0.2.3-3
severity 698504 important
affects 698504 + system-config-printer
tags 698504 + patch
user cont...@itopie.ch
usertags 698504 + itopie.ch-installation
user i...@apres-ge.ch
usertags 698504 + apres-ge.ch-installation
thanks

Hi there!

On Tue, 04 Feb 2014 20:49:02 +0100, Claudio Laurita wrote:
> I can confirm this bug in debian wheezy 32 bit too (with mate 1.6.0 desktop,
> kernel 3.11 i386).
> system-config-printer version 1.4.3-1
> cups 1.7.1-2

The problem resides in cups-pk-helper, which does not respect CUPS
'SystemGroup lpadmin' privileges as per /etc/cups/cups-files.conf.

The file below is enough to fix this, but please note that while the
service is org.opensuse.CupsPkHelper.Mechanism, the actions are all
lowercase.  I discover that thanks to the more-than-3-year-old Ubuntu
fix, albeit not in the cups-pk-helper package:

  


=
$ cat /etc/polkit-1/localauthority/10-vendor.d/org.opensuse.cupspkhelper.pkla 
[Adding or changing system-wide CUPS settings]
Identity=unix-group:lpadmin;unix-group:sudo
Action=org.opensuse.cupspkhelper.mechanism.*
ResultAny=no
ResultInactive=no
ResultActive=yes
$ 
=

Thx, bye,
Gismo / Luca

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

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

Versions of packages cups-pk-helper depends on:
ii  libc6  2.13-38+deb7u6
ii  libcups2   1.5.3-5+deb7u4
ii  libglib2.0-0   2.33.12+really2.32.4-5
ii  libpolkit-gobject-1-0  0.105-3

cups-pk-helper recommends no packages.

cups-pk-helper suggests no packages.

-- no debconf information


signature.asc
Description: Digital signature

Bug#773999: epiphany-browser: Hangs on www.beppegrillo.it

[Carlo Marchiori]

Package: epiphany-browser
Version: 3.14.1-1
Severity: normal

Dear Maintainer,

Epiphany hangs on the most visited italian blog, namely
http://www.beppegrillo.it. It doesn't scroll from the top of the page.

The same thing happen for example on my homebanking site.

In general, the lack of support for flash makes the browser unusable on many
sites, freshplugin and pepperplugin being still incomplete (for example one
cannot watch videos on some relevant italian news sites like www.repubblica.it
and www.corriere.it)

So while I like the idea of using this browser because it's well integrated in
the gnome-shell environment, these problems discourage its use.

Carlo.



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

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

Versions of packages epiphany-browser depends on:
ii  dbus-x11 1.8.12-1
ii  epiphany-browser-data3.14.1-1
ii  gnome-icon-theme 3.12.0-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gsettings-desktop-schemas3.14.1-1
ii  iso-codes3.57-1
ii  libatk1.0-0  2.14.0-1
ii  libavahi-client3 0.6.31-4+b2
ii  libavahi-common3 0.6.31-4+b2
ii  libavahi-gobject00.6.31-4+b2
ii  libc62.19-13
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libgcr-base-3-1  3.14.0-2
ii  libgcr-ui-3-13.14.0-2
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgnome-desktop-3-103.14.1-1
ii  libgtk-3-0   3.14.5-1
ii  libjavascriptcoregtk-4.0-18  2.6.2+dfsg1-3
ii  libnotify4   0.7.6-2
ii  libnspr4 2:4.10.7-1
ii  libnspr4-0d  2:4.10.7-1
ii  libnss3  2:3.17.2-1
ii  libnss3-1d   2:3.17.2-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libsecret-1-00.18-1+b1
ii  libsoup2.4-1 2.48.0-1
ii  libsqlite3-0 3.8.7.1-1
ii  libwebkit2gtk-4.0-37 2.6.2+dfsg1-3
ii  libwnck-3-0  3.4.9-3
ii  libx11-6 2:1.6.2-3
ii  libxml2  2.9.1+dfsg1-4
ii  libxslt1.1   1.1.28-2+b2

Versions of packages epiphany-browser recommends:
ii  ca-certificates  20141019
ii  evince   3.14.1-1
ii  yelp 3.14.1-1

epiphany-browser 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#773728: gnome-flashback: no way to trigger reboot/suspend/hibernate

[Colomban Wendling]

Hi,

On Fri, 26 Dec 2014 09:18:33 - Dmitry Shachnev 
wrote:
> Version: 3.14.0-1
> 
> On Mon, 22 Dec 2014 18:32:43 +0100, Jonathan Michalon wrote:
> > Using GNOME flashback under testing there is no way to trigger the 
> > following actions
> > when sticking to graphical interface (one could of course use CLI):
> >   - suspend
> >   - hibernate
> >   - reboot
> 
> Reboot should be available from the same dialog as shutdown.

I can confirm that reboot definitely is *not* in the dialog, at least
not as triggered by the normal user menu from the panel (User ->
Shutdown) -- and there is no "Reboot" entry in the user menu itself.

BTW, I'm on unstable, but it currently has the same gnome-flashback
version than testing.

> Suspend/Hilbernate is available in 3.14.0-1, which won't make it into Jessie.

That's sad, nowadays suspend and hibernate are very commonly used
actions… couldn't a patch be backported?

Regards,
Colomban


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

Bug#773998: netpanzer: update Homepage

[Sandro Tosi]

Source: netpanzer
Severity: normal

http://www.netpanzer.info/

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

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


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

Bug#773996: assword: Problems with accents in context

[Ivan Vilata i Balaguer]

Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote:

> The Assword GUI cannot match contexts with accents and the like. […]
> 
> Hopefully the fix simply consists of calling some ``.encode()`` or
> ``.decode()`` at the right spot in the code. :)

I just changed the first line in ``Gui.enter()`` to read:

e = self.entry.get_text().decode()

(note the extra ``.decode()``) so that the Unicode contexts are compared
instead of their encoded string versions, and it seems to work.  I'm not
sure about how correct it is to decode like whis without giving an
explicit encoding, though

-- 
Ivan Vilata i Balaguer -- https://elvil.net/


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

Bug#773180: (pre-approval) unblock: dbus with #773107 fixed

[Simon McVittie]

On 26/12/14 22:10, Ivo De Decker wrote:
> Another dbus upload happened, which was unblocked by Niels, but needs an
> unblock-udeb

Thanks for flagging this. I was going to follow up to this bug when it
had aged enough that it would ordinarily have migrated; hopefully it
won't regress this time.

The regression was that the opportunistic dpkg-statoverride during the
preinst, just before the new dbus is unpacked, is too late for that
unpack run to use the dpkg-statoverride info; and because the
dpkg-statoverride entry exists, the postinst wouldn't chmod the binary
either. Installing 1.8.12-2 or 1.9.4-2 for a second time was enough to
avoid that bug, which is why I didn't see this during my local testing.

Removing the preinst's dpkg-statoverride means that the wheezy -> jessie
upgrade will unfortunately still have the non-functional permissions for
part of the upgrade (while dbus is unpacked but not configured), but at
least updates within jessie or from jessie to stretch won't suffer from it.

S


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

Bug#773997: mirage: update Homepage

[Sandro Tosi]

Package: mirage
Severity: normal

http://sourceforge.net/projects/mirageiv.berlios/

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

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


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

Bug#773865: unblock: imagemagick/8:6.8.9.9-4 [security]

[Ivo De Decker]

Control: tags -1 moreinfo

Hi Bastien,

On Wed, Dec 24, 2014 at 12:01:29PM +0100, Bastien ROUCARIES wrote:
> Please unblock package imagemagick
> 
> This fix a few security bug. Bugs are well isolated. Debdiff joined
> 
> unblock imagemagick/8:6.8.9.9-4

I haven't look at the debdiff (yet), but the build failed (again) on mips.
This is the issue described in #770009. As the buildd 'ball' is down, and it's
unclear if it will come back, this issue should probably be fixed properly,
even if it means disabling certain tests in mips, which take too long on
machines without fpu. That's probably the only way we can be sure that later
(security) uploads during the lifetime of jessie will be able to build on
mips.

Cheers,

Ivo


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

Bug#773996: assword: Problems with accents in context

[Ivan Vilata i Balaguer]

Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote:

> […] Maybe it's some kind on encoding problem.  If I dump the database,
> I can see that the context is always escaped using ``\u`` (even if
> ``\x`` was enough), i.e. it has become ``aix\u00f2``.  There should be
> no need of such escaping since JSON documents are UTF-8 native, so
> this only adds a chance for encoding errors. […]

Please ignore this, I already checked that this escaping is also native
for JSON to fit in ASCII encoding. :-/

-- 
Ivan Vilata i Balaguer -- https://elvil.net/


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

Bug#773180: (pre-approval) unblock: dbus with #773107 fixed

[Ivo De Decker]

Control: retitle -1 unblock: dbus/1.8.12-3

Hi,

On Sat, Dec 20, 2014 at 11:23:45PM +0100, Cyril Brulebois wrote:
> Julien Cristau  (2014-12-15):
> > Control: tag -1 confirmed d-i
> > 
> > On Mon, Dec 15, 2014 at 11:05:51 +, Simon McVittie wrote:
> > 
> > > Package: release.debian.org
> > > Severity: wishlist
> > > User: release.debian@packages.debian.org
> > > Usertags: unblock
> > > 
> > > I just uploaded a dbus version to experimental with more robust
> > > owner/permissions setting for dbus-daemon-launch-helper (debdiff
> > > attached). Would you be willing to consider equivalent changes via
> > > unstable (probably as dbus/1.8.12-2) for jessie?
> > > 
> > Seems fine to me, though it should be d-i-acked.
> 
> No objection.

Another dbus upload happened, which was unblocked by Niels, but needs an
unblock-udeb:


diff -Nru dbus-1.8.12/debian/changelog dbus-1.8.12/debian/changelog
--- dbus-1.8.12/debian/changelog2014-11-24 13:46:14.0 +
+++ dbus-1.8.12/debian/changelog2014-12-23 21:24:31.0 +
@@ -1,3 +1,29 @@
+dbus (1.8.12-3) unstable; urgency=medium
+
+  * preinst: partially revert change from 1.8.12-2. It seems that the
+preinst is too late to add a useful dpkg-statoverride entry: dpkg has
+already loaded the statoverride database by this point, and if we add
+the entry in the preinst, dpkg-statoverride won't run and have
+its --update side-effect in the postinst. (Closes: #773107, #773838)
+  * postinst: don't run dpkg-statoverride with 2>/dev/null: in the unlikely
+event that it fails for a reason other than "not overridden" (which
+results in silently exiting 1), we'll want to know about it.
+
+ -- Simon McVittie   Tue, 23 Dec 2014 21:21:20 +
+
+dbus (1.8.12-2) unstable; urgency=medium
+
+  * postinst: use dpkg-statoverride to set the permissions for
+dbus-daemon-launch-helper (expected to be 04754 root:messagebus)
+as suggested in Policy §10.9. This avoids a temporarily broken state
+when an upgraded dbus is unpacked but not yet configured (Closes: #773107)
+  * preinst: opportunistically set up the same dpkg-statoverride entry
+if the group already exists, to avoid the same broken state during
+upgrades from older versions without needing Pre-Depends: adduser
+  * postrm: delete the dpkg-statoverride entry on purge
+
+ -- Simon McVittie   Sun, 21 Dec 2014 15:02:22 +
+
 dbus (1.8.12-1) unstable; urgency=medium
 
   * New upstream release 1.8.12
diff -Nru dbus-1.8.12/debian/dbus.postinst dbus-1.8.12/debian/dbus.postinst
--- dbus-1.8.12/debian/dbus.postinst2014-11-24 13:46:14.0 +
+++ dbus-1.8.12/debian/dbus.postinst2014-12-23 21:24:31.0 +
@@ -31,9 +31,8 @@
 --disabled-password \
 --group "$MESSAGEUSER"
 
-if ! dpkg-statoverride --list "$LAUNCHER" >/dev/null 2>&1; then
-chown root:"$MESSAGEUSER" "$LAUNCHER"
-chmod 4754 "$LAUNCHER"
+if ! dpkg-statoverride --list "$LAUNCHER" >/dev/null; then
+dpkg-statoverride --update --add root "$MESSAGEUSER" 4754 "$LAUNCHER"
 fi
 
 # This is idempotent, so it's OK to do every time. The system bus' init
diff -Nru dbus-1.8.12/debian/dbus.postrm dbus-1.8.12/debian/dbus.postrm
--- dbus-1.8.12/debian/dbus.postrm  2014-11-24 13:46:14.0 +
+++ dbus-1.8.12/debian/dbus.postrm  2014-12-23 21:24:31.0 +
@@ -7,6 +7,12 @@
 
rm -f /var/lib/dbus/machine-id
rmdir /var/lib/dbus || true
+
+   LAUNCHER=/usr/lib/dbus-1.0/dbus-daemon-launch-helper
+
+   if dpkg-statoverride --list "$LAUNCHER" >/dev/null 2>&1 ; then
+   dpkg-statoverride --remove "$LAUNCHER"
+   fi
 fi
 
 #DEBHELPER#



Cheers,

Ivo


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

Bug#773714: unblock: grub2/2.02~beta2-19

[Ivo De Decker]

Hi,

On Mon, Dec 22, 2014 at 02:56:09PM +, Ian Campbell wrote:
> Please unblock package grub2

> Version -18 added a fix for #767037 (workaround for buggy EFI implementations)
> which included a new debconf template. -19 adds translations for the new
> template (including a wording fix to the English) and fixes two issues with
> that new funcitionality (one, #773092, is important, the other, #773004, is
> fairly minor but quite irritating in practice).
> 
> I also added a README.source.
> 
> Note that this upload does not include the upstream translation updates
> discussed in preapproval bug #773224, since there wasn't an obvious yes to 
> that
> question.

Unblocked, but this also needs an unblock-udeb.

Cheers,

Ivo


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

Bug#773029: groonga-server-common: purging deletes conffiles owned by other packages: /etc/groonga/{groonga.conf, synonyms.tsv}

[Vagrant Cascadian]

On 2014-12-13, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package removes files that
> were installed by another package.
> The removed files were already present before the package was installed,
> they may have been shipped or created by a dependency.
...
>   Removing groonga-server-common (4.0.6.1-2) ...
>   Purging configuration files for groonga-server-common (4.0.6.1-2) ...
> 0m24.4s ERROR: FAIL: debsums reports modifications inside the chroot:
>   debsums: missing file /etc/groonga/groonga.conf (from groonga-bin package)
>   debsums: missing file /etc/groonga/synonyms.tsv (from libgroonga0:amd64 
> package)
>
>
> I didn't check, but there is probably a rm -rf /etc/groonga in the postrm.

Yes, this appears to be what's happening...

groonga-server-common.postrm:

for target in /var/run/groonga /var/lib/groonga /var/log/groonga 
/etc/groonga
do
dpkg-statoverride --remove $target
rm -rf $target
done

groonga-server-common doesn't appear to ship any files in /etc/groonga,
or create them in the .postinst. Though dpkg-statoverride appears to be
used in order to set the group and user permissions:

for target in /var/run/groonga /var/lib/groonga /etc/groonga 
/var/log/groonga
do
dpkg-statoverride --list $target >/dev/null || \
dpkg-statoverride --update --add groonga groonga 0755 $target
done


Similar code is present in groonga-httpd.postrm and
groonga-httpd.postinst in the same source package, so that may need to
be fixed in groonga-httpd as well (though I'm unsure if any other
packages ship files in there currently, it seems like it could have the
same issue in the future).


I'm not familiar with groonga, but it seems unecessary to remove
/etc/groonga (and /etc/groonga/httpd) manually on purge, as dpkg should
take care of that when the directories are empty.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#773183: (pre-approval) unblock: systemd with #770504 fixed

[Ivo De Decker]

Control: tags -1 moreinfo

Simon,

On Sat, Dec 20, 2014 at 11:22:08PM +0100, Cyril Brulebois wrote:
> Julien Cristau  (2014-12-15):
> > Control: tag -1 confirmed d-i
> > 
> > On Mon, Dec 15, 2014 at 11:27:40 +, Simon McVittie wrote:

> > > Would you be willing to let the systemd maintainers cherry-pick the
> > > attached into a jessie-targeted version?
> > > 
> > > It is a trivial change (escalate the level of a log line from info to
> > > warning) and would make it much easier to diagnose and fix circular
> > > dependencies between units. At the moment, systemd logs the first unit
> > > in the cycle and the points at which it tried breaking the cycle,
> > > but the other units involved are not logged unless 'debug' or
> > > a non-default 'systemd.log_level' is present on the kernel command-line.
> > > 
> > Seems fine to me, but should be d-i-acked (though I guess since there
> > are no udev changes here that shouldn't be an issue).
> 
> d-i-ack (indeed).

Please remove the moreinfo tag once the new version is in unstable.

Cheers,

Ivo


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

Bug#773996: assword: Problems with accents in context

[Ivan Vilata i Balaguer]

Package: assword
Version: 0.8-1
Severity: normal
Tags: upstream

(First of all thanks for the neat and nice piece of software!)

The Assword GUI cannot match contexts with accents and the like.

For instance, I create a new entry by running ``env ASSWORD_PASSWORD=prompt
assword add``.  I enter ``això`` as a context.  If I run ``assword dump això``
I get the stored password.  So far so good.

The problem shows up when I run ``assword gui`` with no context argument.
If I enter ``això`` or some letter and then select the completion for
``això``, I'm unable to fulfill the password selection with Enter, since the
label above insists in "no match", even when the full matching context is in
the text box.

Maybe it's some kind on encoding problem.  If I dump the database, I can see
that the context is always escaped using ``\u`` (even if ``\x`` was enough),
i.e. it has become ``aix\u00f2``.  There should be no need of such escaping
since JSON documents are UTF-8 native, so this only adds a chance for
encoding errors.

Hopefully the fix simply consists of calling some ``.encode()`` or
``.decode()`` at the right spot in the code. :)

Thank you very much!

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

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

Versions of packages assword depends on:
ii  python2.7.8-2
ii  python-gpgme  0.3-1+b1
ii  python-gtk2   2.24.0-4
ii  python-pkg-resources  5.5.1-1

Versions of packages assword recommends:
ii  python-xdo  0.2-2
ii  xclip   0.12+svn84-4

assword 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#732411: monkeysign: Being nicer with systems without a SMTP server

[Antoine Beaupré]

On 2014-12-26 13:00:11, Muri Nicanor wrote:
> attached is a patch that add -o or --output which allows you to save the
> output to a file.
> diff --git a/monkeysign/ui.py b/monkeysign/ui.py
> index c9b6a30..43d15ed 100644
> --- a/monkeysign/ui.py
> +++ b/monkeysign/ui.py
> @@ -93,6 +93,7 @@ class MonkeysignUi(object):
>help=_('do not send email at all (default: use 
> sendmail)'))
>  parser.add_option('-t', '--to', dest='to', 
>help=_('override destination email for testing 
> (default: send individually encrypted email to each uid chosen)'))
> +parser.add_option('-o', '--output', dest='output', help=_('save the 
> output email to a file'))
>  return parser
>  
>  def parse_args(self, args):
> @@ -381,6 +382,18 @@ expects an EmailFactory email, but will not mail if 
> nomail is set"""
>  not sending email to %s, as requested, here's the email message:
>  
>  %s""") % (msg.mailto, msg.create_mail_from_block()))
> +if self.options.output is not None:
> +if not os.path.exists(self.options.output):
> +try:
> +f = open(self.options.output, 'w');
> +f.write(str(msg.create_mail_from_block()))
> +except IOError:
> +self.warn(_('Error opening or writing file %s') % 
> self.options.output);
> +else:
> +f.close()
> +self.warn(_('Mail has been written to %s') % 
> self.options.output)
> +else:
> +self.warn(_('Didn\'t write to %s, because file exists') 
> % self.options.output)
>  
>  
>  class EmailFactory:

Thanks for the patch, it's a great idea!

Can you redo the patch with the "with" construct instead of manual
exception handling?

Also, I'd suggest the message "Could not write to %s: file exists" as an
error message.

Thanks!

a.

-- 
Le péché est né avant la vertu, comme le moteur avant le frein.
 - Jean-Paul Sartre


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

Bug#773980: libmagickcore-6.q16-2: 8:6.8.9.9-4 breaks images in GNU Emacs 24 (displayed as single colour rectangles)

[Adam Sjøgren]

Bastien writes:

>> When displaying an image in GNU Emacs 24 (package emacs24), after
>> upgrading from ImageMagick 8:6.8.9.9-3 to 8:6.8.9.9-4, images with
>> :type 'imagemagick are displayed as single colour rectangles.

> Thanks could you get the exact command running ?

I don't understand your question.

I tried to explain how to reproduce the problem:

>> To reproduce:
>>
>>  * Install emacs24
>>  * Run emacs --no-init-file my-test-image.el
>>Type M-x eval-buffer
>>Where the file my-test-image.el contains:
>>
>> == =
>> (defun my-test-image ()
>>   (let* ((image (create-image "/usr/share/emacs/24.4/etc/images/splash.xpm"))
>>  (magnitude 2.0)
>>  (size (image-size image t))
>>  (spec (cdr image)))
>> (plist-put spec :type 'imagemagick)
>> (plist-put spec :width  (round (* (car size) magnitude)))
>> (plist-put spec :height (round (* (cdr size) magnitude)))
>> (insert-image image)))
>>
>> (my-test-image) ;; M-x eval-buffer should insert a scaled splash image.
>> ;; With 8:6.8.9.9-4 a blue rectangle is shown instead.
>> == =

But I guess you're looking for something else?


  Best regards,

Adam

-- 
 "You'll see my chainsaw coming   Adam Sjøgren
  I'm drawing the line"  a...@koldfront.dk


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

Bug#773970: Monkeyscan fails at launch

[Antoine Beaupré]

On 2014-12-26 06:31:26, Hugo Roy wrote:
> Package: monkeysign
> Version: 2.0
>
> When launching monkeyscan, I get a small GTK window reporting an
> error with:
>
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/monkeysign/msg_exception.py", 
> line 36, in wrapper
> return f(*args, **kargs)
>   File "/usr/lib/python2.7/site-packages/monkeysign/gtkui.py", line 64, 
> in main
> self.window = MonkeysignScan()
>   File "/usr/lib/python2.7/site-packages/monkeysign/gtkui.py", line 160, 
> in __init__
> self.create_secret_keys_display()
>   File "/usr/lib/python2.7/site-packages/monkeysign/gtkui.py", line 278, 
> in create_secret_keys_display
> for key in Keyring().get_keys(None, True, False).values():
>   File "/usr/lib/python2.7/site-packages/monkeysign/gpg.py", line 385, in 
> get_keys
> key = OpenPGPkey(keydata)
>   File "/usr/lib/python2.7/site-packages/monkeysign/gpg.py", line 656, in 
> __init__
> self.parse_gpg_list(data)
>   File "/usr/lib/python2.7/site-packages/monkeysign/gpg.py", line 698, in 
> parse_gpg_list
> (null, self.trust, self.length, self.algo, keyid, self.creation, 
> self.expiry, serial, trust, uid, sigclass, purpose, smime, wtf, wtf, wtf) = 
> record
> ValueError: too many values to unpack
>
> I'm on  Arch Linux, Kernel: x86_64 Linux 3.17.6-1-xps13.
>
> I tried both versions at https://aur.archlinux.org/packages/?O=0&K=monkeysign

interesting. can you paste the output of --debug? i think i may need the
output of --list-secret-keys as well, unfortunately.

of course, do not send this if you feel uncomfortable sharing your list
of private keys identifiers. no private key material should be revealed,
but make sure you review the output before sending this anyways.

a.
-- 
Le pouvoir n'est pas à conquérir, il est à détruire
- Jean-François Brient, de la servitude moderne


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

Bug#764493: python-eventlet 0.15.2-1 to Sid/Jessie

[Ivo De Decker]

Hi,

On Fri, Dec 26, 2014 at 09:21:20AM +0100, László Böszörményi (GCS) wrote:
>  Prepared the updated package. Final and clean build is in progress,
> when it's done I'll upload it to Sid. Then I can ask for a freeze
> exception and let it migrate to Jessie.

Thanks for the upload. I unblocked it.

Cheers,

Ivo


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

Bug#773980: libmagickcore-6.q16-2: 8:6.8.9.9-4 breaks images in GNU Emacs 24 (displayed as single colour rectangles)

[Bastien ROUCARIES]

Le 26 déc. 2014 17:15, "Adam Sjøgren"  a écrit :
>
> Package: libmagickcore-6.q16-2
> Version: 8:6.8.9.9-4
> Severity: normal
>
> When displaying an image in GNU Emacs 24 (package emacs24), after
upgrading
> from ImageMagick 8:6.8.9.9-3 to 8:6.8.9.9-4, images with :type
'imagemagick
> are displayed as single colour rectangles.

Thanks could you get the exact command running ?

Bastien
>
> With 8:6.8.9.9-3 the image is (scaled and) displayed as expected:
>
>  * http://koldfront.dk/misc/gnu-emacs/my-test-image-testing.png
>
> With 8:6.8.9.9-4 a blue rectangle appears instead:
>
>  * http://koldfront.dk/misc/gnu-emacs/my-test-image-unstable.png
>
> To reproduce:
>
>  * Install emacs24
>  * Run emacs --no-init-file my-test-image.el
>Type M-x eval-buffer
>Where the file my-test-image.el contains:
>
> == =
> (defun my-test-image ()
>   (let* ((image (create-image
"/usr/share/emacs/24.4/etc/images/splash.xpm"))
>  (magnitude 2.0)
>  (size (image-size image t))
>  (spec (cdr image)))
> (plist-put spec :type 'imagemagick)
> (plist-put spec :width  (round (* (car size) magnitude)))
> (plist-put spec :height (round (* (cdr size) magnitude)))
> (insert-image image)))
>
> (my-test-image) ;; M-x eval-buffer should insert a scaled splash image.
> ;; With 8:6.8.9.9-4 a blue rectangle is shown instead.
> == =
>
> (The actual scaling is not necessary to trigger the problem, I only kept
it to
> illustrate why setting :type 'imagemagick might be relevant.)
>
> If I go back to ImageMagick from testing:
>
> == =
> $ wajig install libmagickcore-6.q16-2:amd64/testing
libmagickwand-6.q16-2/testing libmagick++-6-headers/testing
libmagick++-6.q16-dev/testing libmagick++-dev/testing
libmagickcore-6-arch-config/testing libmagickcore-6-headers/testing
libmagickcore-6.q16-dev/testing libmagickwand-6-headers/testing
libmagickwand-6.q16-dev/testing
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Selected version '8:6.8.9.9-3' (Debian:testing [all]) for
'libmagickwand-6-headers'
> Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for
'libmagickcore-6-arch-config'
> Selected version '8:6.8.9.9-3' (Debian:testing [all]) for
'imagemagick-common' because of 'libmagickcore-6-arch-config'
> Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for
'libmagickcore-6.q16-2'
> Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for
'libmagickcore-6.q16-dev'
> Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for
'libmagickwand-6.q16-2'
> Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for
'libmagickwand-6.q16-dev'
> Selected version '8:6.8.9.9-3' (Debian:testing [all]) for
'libmagick++-dev'
> Selected version '8:6.8.9.9-3' (Debian:testing [all]) for
'libmagickcore-6-heade
> Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for
'libmagick++-6.q16-d
> Selected version '8:6.8.9.9-3' (Debian:testing [all]) for
'libmagick++-6-headers
> The following extra packages will be installed:
>   imagemagick-common libmagick++-6.q16-5 libmagickcore-6.q16-2-extra
> The following packages will be DOWNGRADED:
>   imagemagick-common libmagick++-6-headers libmagick++-6.q16-5
libmagick++-6.q16
>   libmagickcore-6.q16-dev libmagickwand-6-headers libmagickwand-6.q16-2
libmagic
> 0 upgraded, 0 newly installed, 13 downgraded, 0 to remove and 1 not
upgraded.
> Need to get 0 B/4,994 kB of archives.
> After this operation, 476 kB of additional disk space will be used.
> == =
>
> Then the image is displayed correctly, as seen in the first screenshot.
>
> -- 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_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libmagickcore-6.q16-2 depends on:
> ii  dpkg1.17.22
> ii  imagemagick-common  8:6.8.9.9-4
> ii  libbz2-1.0  1.0.6-7+b2
> ii  libc6   2.19-13
> ii  libfftw3-double33.3.4-2
> ii  libfontconfig1  2.11.0-6.3
> ii  libfreetype62.5.2-2koldfront1
> ii  libgcc1 1:4.9.2-9
> ii  libgomp14.9.2-9
> ii  libjbig02.1-3.1
> ii  libjpeg62-turbo 1:1.3.1-11
> ii  liblcms2-2  2.6-3+b3
> ii  liblqr-1-0  0.4.2-2
> ii  libltdl72.4.2-1.11
> ii  liblzma55.1.1alpha+20120614-2+b3
> ii  libpng12-0  1.2.50-2+b2
> ii  libtiff54.0.3-11
> ii  libx11-62:1.6.2-3
> ii  libxext62:1.3.3-1
> ii  libxml2 2.9.2+dfsg1-1+b1
> ii  multiarch-support   2.19-13
> ii  zlib1g  1:1.2.8.dfsg-2+b1
>
> Versions of packages libmagickcore-6.q16-2 recommends:
> ii  ghostscript  9.06~dfsg-1.1+b1
> ii  gsfonts  1:8.11+urwcyr1.0.7~pre44-4.2
>
> 

Bug#773431: mate-terminal: provides x-terminal-emulator but does not implement -T

[Vagrant Cascadian]

Control: tags -1 patch

On 2014-12-22, Matt Kraai wrote:
> mate-terminal already contains a mate-terminal.wrapper program that
> provides the options required for x-terminal-emulator, but
> update-alternatives is called with mate-terminal instead of
> mate-terminal.wrapper.
>
> I think it's just necessary to use update-alternatives in the
> maintainer scripts to remove the mate-terminal alternative and add a
> mate-terminal.wrapper one, but I'm not sure how to do so.

I haven't tested, but the following patch should work:

diff --git a/debian/mate-terminal.postinst b/debian/mate-terminal.postinst
index 278bc4c..0fdb949 100755
--- a/debian/mate-terminal.postinst
+++ b/debian/mate-terminal.postinst
@@ -6,6 +6,6 @@ set -e
 
 if [ "$1" = "configure" ]; then
update-alternatives --install /usr/bin/x-terminal-emulator \
-   x-terminal-emulator /usr/bin/mate-terminal 30
+   x-terminal-emulator /usr/bin/mate-terminal.wrapper 30
 fi
 
diff --git a/debian/mate-terminal.prerm b/debian/mate-terminal.prerm
index 2145b42..57f6df2 100755
--- a/debian/mate-terminal.prerm
+++ b/debian/mate-terminal.prerm
@@ -5,6 +5,6 @@ set -e
 #DEBHELPER#
 
 if [ "$1" = "remove" ]; then
-   update-alternatives --remove x-terminal-emulator /usr/bin/mate-terminal
+   update-alternatives --remove x-terminal-emulator 
/usr/bin/mate-terminal.wrapper
 fi


It doesn't handle removal of the old alternatives using mate-terminal
directly; it probably should do that also...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#732283: Fwd: [rt.cpan.org #91450] Fwd: Bug#732283: libproc-daemon-perl: Writes pidfile with mode 666 [origin: bug-proc-dae...@rt.cpan.org]

[Axel Beckert]

Hi,

I just received this modified patch from upstream and wanted to
document that in te BTS.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
--- Begin Message ---
https://rt.cpan.org/Ticket/Display.html?id=91450 >

While the patch from Debian fixes the security issue, it makes unreadable for 
other users all other files created by a daemon, what is unwanted in some cases.
Attached patch fixes this problem.
diff -crB lib.orig/Proc/Daemon.pm lib/Proc/Daemon.pm
*** lib.orig/Proc/Daemon.pm	2013-12-18 10:13:31.0 -0400
--- lib/Proc/Daemon.pm	2014-12-18 14:14:43.358761046 -0400
***
*** 152,157 
--- 152,158 
  die "Can't  to $self->{work_dir}: $!" unless chdir $self->{work_dir};
  
  # Clear the file creation mask.
+ $self->{_orig_umask} = umask;
  umask 066;
  
  # Detach the child from the terminal (no controlling tty), make it the
***
*** 253,258 
--- 254,261 
  # potential damage later.
  }
  
+ # Restore the original file creation mask.
+ umask $self->{_orig_umask};
  
  # Execute a system command and never return.
  if ( $exec_command ) {
--- End Message ---

Bug#649265: nsswitch.conf updates for autofs?

[Luke Diamand]

It would be quite useful to have a way to allow autofs to put the entry it
needs into nsswitch.conf.

It needs something like:

autofs: nis files

Everytime I install autofs I spend a while trying to remember how to do
this.

Bug#773993: avprobe loops endlessly on certain FLAC files

[Max Kellermann]

Package: libavcodec56
Version: 6:11-2
Severity: important

Download the following file:
  http://farragut.drunkensailor.org:5/track2.flac

Then run "avprobe" on it.  libavcodec will loop endlessly.

This library bug is important because you can use it for a
denial-of-service attack against remotly accessible services like MPD.

Upstream bug report on MPD: http://bugs.musicpd.org/view.php?id=3384


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

Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel

[Vagrant Cascadian]

On 2014-12-26, Ian Campbell wrote:
> On Wed, 2014-12-24 at 12:42 -0800, Vagrant Cascadian wrote:
>> The following patch adds an additional Machine entry for the more
>> specific name. Not sure if there's a more elegant way to add an entry
>> that's simply a duplicate of another entry with a different Machine id.
>
> It's permissible to have multiple Machine entries in a stanza, so if the
> only difference is that field then it's fine to just add a new one (a
> bunch of the kirkwood TS-xxx enties follow this pattern since they have
> a boardfile name and a DTB name).

Ok, then I think we should simply add the second Machine entry to the
same stanza...


> I wonder though if the DTB-Id field should be different? I think not on
> the basis that the difference is down to
> git.kernel.org/linus/9a15fff05b702c3ea29ae64db0d3ff0355431eab 

If you change the DTB-Id to be for the BeagleBone white, it will break
on BeagleBone Black running kernels 3.16 or earlier, including the
kernel shipped on the BeagleBone Black eMMC by the vendor, making it
harder to "upgrade" to a pure Debian system.

I'm not sure that the BeagleBone white is actually supported in Debian's
kernel or in Debian's flash-kernel... so it doesn't make much sense to
add support now, when that would break a currently supported platform.


> I wonder if 9a15fff ought to be backported to the kernel in Jessie and
> correspondingly whether this flash-kernel change ought to happen in
> Jessie too (otherwise I'd just put it in experimental for the rest of
> the freeze).

I think it would make sense to support both Machine IDs for the
BeagleBone Black in Jessie's flash-kernel regardless of weather the
change was backported to the kernel, as it can result in an unbootable
system:

Running 3.16.x, install linux-image-3.18*, flash-kernel updates the boot
script without complaint. Reboot to 3.18.x. Remove linux-image-3.18*,
flash-kernel fails to update /boot/boot.scr, system is unbootable...


Basically long-running inability to distinguish between the white and
black models make this impossible to "get right" for both, but I believe
there are far more BeagleBone Black systems in the wild, and is better
supported out of the box. It would be better to require manual
intervention on the BeagleBone white models than the other way around.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#757348: Debian jessie, same behaviour (AccessDenied)

[vasos mitropoulos]

policykit-1 0.105-8
 lightdm 1.10.3-3
 cgmanager 0.33-2


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

Bug#773253: jenkins: please add script to detect dpkg trigger cycles

[Holger Levsen]

On Freitag, 26. Dezember 2014, Johannes Schauer wrote:
> sorry, in contrast to what I thought I did, I must've not tested the final
> patch I sent you.
> Please apply the attached and try again.

applied, deployed & thanks! :-)


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

Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel

[Ian Campbell]

On Wed, 2014-12-24 at 12:42 -0800, Vagrant Cascadian wrote:
> Package: flash-kernel
> Version: 3.28
> Severity: normal
> Tags: patch
> 
> When running the 3.18 kernel from experimental on a BeagleBone Black,
> /proc/device-tree/model contains "TI AM335x BeagleBone Black". With
> the 3.16 kernel from Jessie, it contains "TI AM335x BeagleBone".
> 
> The following patch adds an additional Machine entry for the more
> specific name. Not sure if there's a more elegant way to add an entry
> that's simply a duplicate of another entry with a different Machine id.

It's permissible to have multiple Machine entries in a stanza, so if the
only difference is that field then it's fine to just add a new one (a
bunch of the kirkwood TS-xxx enties follow this pattern since they have
a boardfile name and a DTB name).

I wonder though if the DTB-Id field should be different? I think not on
the basis that the difference is down to
git.kernel.org/linus/9a15fff05b702c3ea29ae64db0d3ff0355431eab 

If you can confirm that is the case I can easily sort that out as I
commit it. 

I wonder if 9a15fff ought to be backported to the kernel in Jessie and
correspondingly whether this flash-kernel change ought to happen in
Jessie too (otherwise I'd just put it in experimental for the rest of
the freeze).

Ian.


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

Bug#773253: jenkins: please add script to detect dpkg trigger cycles

[Johannes Schauer]

Hi,

Quoting Holger Levsen (2014-12-26 18:50:38)
> merged and deployed, thanks!

sorry, in contrast to what I thought I did, I must've not tested the final
patch I sent you.

Please apply the attached and try again.

Thanks!

cheers, josch
From 84fc2bef51b5c2d1400dc7dd4adc8fd6aac9bd8a Mon Sep 17 00:00:00 2001
From: josch 
Date: Fri, 26 Dec 2014 20:59:00 +0100
Subject: [PATCH] bin/find_dpkg_trigger_cycles.sh: make temporary directory,
 not file

---
 bin/find_dpkg_trigger_cycles.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/find_dpkg_trigger_cycles.sh b/bin/find_dpkg_trigger_cycles.sh
index 9019ff3..a232f19 100755
--- a/bin/find_dpkg_trigger_cycles.sh
+++ b/bin/find_dpkg_trigger_cycles.sh
@@ -155,7 +155,7 @@ curl "http://binarycontrol.debian.net/?q=&path=%2Ftriggers%24&format=pkglist"; \
 	| sort \
 	| while read pkg url; do
 	echo "working on $pkg..." >&2
-	tmpdir=`mktemp`
+	tmpdir=`mktemp -d`
 	# FIXME: please revert 9280f1c87 and following as soon as Jenkins run Jessie
 	# this is about the next line:
 	curl --retry 2 --location --silent "$url" \
-- 
2.0.1

Bug#773992: RFS: xmlrpc-c/1.33.15+svn20141223~2672-1 [ITA]

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "xmlrpc-c"

   Package name: xmlrpc-c
   Version : 1.33.15+svn20141223~2672-1
   Upstream Author : Bryan Henderson 
   URL : http://xmlrpc-c.sourceforge.net/
   License : BSD-3, Expat, Apache-1.0, GPL-1, public-domain
   Section : libs

  It builds those binary packages:

 libxmlrpc-c++8 - lightweight RPC library based on XML and HTTP [C++ runtime 
librar
 libxmlrpc-c++8-dev - lightweight RPC library based on XML and HTTP [C++ 
development li
 libxmlrpc-core-c3 - lightweight RPC library based on XML and HTTP [C runtime 
librarie
 libxmlrpc-core-c3-dev - lightweight RPC library based on XML and HTTP [C 
development libr
 xmlrpc-api-utils - Generate C++ wrapper classes for XML-RPC servers

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

  http://mentors.debian.net/package/xmlrpc-c


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

dget -x 
http://mentors.debian.net/debian/pool/main/x/xmlrpc-c/xmlrpc-c_1.33.15+svn20141223~2672-1.dsc

  Changes since the last upload:

  * New maintainer (Closes: #773435).
  * debian/source:
- Change format 3.0 (quilt).
  * debian/control:
- Add myself as maintainer.
- Remove quilt from Build-Depends.
- Bump Standards-Version to 3.9.6 (no changes required).
- Remove useless Section from package libxmlrpc-c++8 &
  libxmlrpc-core-c3.
- Change Vcs-git to canonical URI
- Add Multi-Arch: same to libxmlrpc-core-c3 & libxmlrpc-c++8.
  * debian/rules:
- Remove --with quilt.
- Enable hardening=+all.
  + Set missing parameter to CFLAGS & CXXFLAGS.
- Add dpkg-gensymbols to build symbols files from libxmlrpc-core-c3 &
  libxmlrpc-c++8.
- Add get-orig-source. Upstream has no stable tarball.
  * debian/copyright:
- Rewrite in machine-readable format.
- Add myself to the list of authors for debian/*.
  * debian/*.install:
- Move symlink XmlRpcCpp.h from libxmlrpc-core-c3-dev to
  libxmlrpc-c++8-dev (Closes: #644161).
  * New debian/patches/200-test_port.diff:
- Change port for testing from 8080 to 7890 (Closes: #722503).
  * New debian/patches/005-xmlrpc_example.diff:
- Backport from upstream release 1.34.0 (Closes: #524550).
  * New missing debian/xmlrpc-c-config.man and debian/xmlrpc.man.
  * Rewrite debian/README.source.
  * New debian/watch.



  Regards,
   Jörg Frings-Fürst


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old (will be revoked after 2014-12-31):
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net






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

Bug#723103: dieharder: non-free due to $beverage clause?

[Ron]

On Fri, Dec 26, 2014 at 12:14:09PM -0600, Dirk Eddelbuettel wrote:
> 
> On 27 December 2014 at 04:18, Ron wrote:
> | 
> | Hi,
> | 
> | Did you want to actually close or downgrade this bug now?
> 
> No, because nobody ever replied (including upstream, with whom I've worked on
> RDieHarder for years, but whose email response rate is still, err, a little
> erratic). 
> 
> | The dieharder package got autoremoved from jessie because
> | it's still outstanding with RC severity.
> | 
> | I asked -release about jessie-ignoring it like it was for
> | wheezy, and the initial answer from them is that they'd
> | prefer it if either you resolved it, or it gets punted to
> | ftpmaster to decide.
> | 
> | Personally I don't really see a problem with the clause in
> | question either.  It's the author's own code to licence,
> | not an addition to someone else's GPL code, and it's clearly
> | said that he doesn't consider the extra request binding.
> 
> I did not want to step on anybody's policy toes.
> 
> If you too are cool with closing this, I can surely do that.

The rough consensus of people who have replied to the bug would
seem to be that it's not considered a problem, and ftpmaster
were cc'd by the original reporter, and they haven't seen fit
to remove it from sid or object to the wheezy-ignore.

So yeah, I'd say let's close it and get it back into jessie,
and if Raphael strongly disagrees, he can appeal to ftpmaster
for more some more formal guidance on their part.  They've had
plenty of time to respond already if they considered it not fit
for main though, so it seems reasonable to call this for the
consensus view now.

Best case, the matter is closed.  Worst case, it escalates to
a "dispute" and ftpmaster gives us their opinion.  Either way
that seems like the right way to resolve this now.

  Thanks!
  Ron


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

Bug#773990: mydumper: Option -k listed as alias for two options in the manpage

[Hans Joachim Desserud]

Package: mydumper
Version: 0.6.1-1
Severity: minor

Dear Maintainer,

In the manpage for mydumper, the option -k is listed twice:
--kill-long-queries, -k
--no-locks, -k

However, when running `mydumper --help` it is only listed once:
-k, --no-locks

It looks like the short cut has been reused or "moved" to a different
feature and that the manpage might need updating.

Originally reported in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/mydumper/+bug/1402381

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
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 mydumper depends on:
ii  libc6 2.19-13
ii  libglib2.0-0  2.42.1-1
ii  libmysqlclient18  5.5.40-1
ii  libpcre3  2:8.35-3.3
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages mydumper recommends:
ii  libjs-sphinxdoc  1.2.3+dfsg-1

mydumper suggests no packages.

-- no debconf information


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org


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

Bug#773991: flash-kernel: Fails when mtdblock kernel module isn't loaded

[Uwe Kleine-König]

Package: flash-kernel
Version: 3.28
Severity: normal

Hello,

on my ReadyNAS 104 (see database entry included below) a typical run
after a fresh reboot looks as follows:

$ sudo flash-kernel 
Installing armada-370-netgear-rn104.dtb into /boot/dtb-3.16.0-4-armmp
Taking backup of dtb-3.16.0-4-armmp.
Installing new dtb-3.16.0-4-armmp.
flash-kernel: installing version 3.16.0-4-armmp
/dev/mtdblock2 is not a block device

After

$ sudo modprobe mtdblock

it works just fine. I wonder if flash-kernel should be smart enough to
load the module itself.

Best regards
Uwe

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 3.16.0-4-armmp (SMP w/1 CPU core)
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 flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  devio  1.2-1
ii  initramfs-tools0.116
ii  linux-base 3.5
ii  ucf3.0030

flash-kernel recommends no packages.

Versions of packages flash-kernel suggests:
ii  u-boot-tools  2014.10+dfsg1-2

-- Configuration Files:
/etc/flash-kernel/db changed:
Machine: NETGEAR ReadyNAS 104
DTB-Id: armada-370-netgear-rn104.dtb
DTB-Append: yes
Mtd-Kernel: uImage
Mtd-Initrd: minirootfs
U-Boot-Kernel-Address: 0x0400
U-Boot-Initrd-Address: 0x0500
Required-Packages: u-boot-tools


-- debconf information excluded


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

Bug#773989: valadoc: Unknown options mentioned in the manpage

[Hans Joachim Desserud]

Package: valadoc
Version: 0.23.2~git20140902-3
Severity: minor

Dear Maintainer,

The manpage for valadoc mentions among others the options
--enable-checking and --enable-deprecated.

However, when attempting to run valadoc with either, it prints a warning 
about
unknown options. I'm not familiar with this program but my guess is that 
these
options have been removed from newer releases and shouldn't be listed in 
the

manpage anymore.

Originally reported in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/valadoc/+bug/1129849

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
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 valadoc depends on:
ii  libc6  2.19-13
ii  libgee-0.8-2   0.16.1-1
ii  libglib2.0-0   2.42.1-1
ii  libvala-0.26-0 0.26.1-1
ii  libvaladoc30.23.2~git20140902-3
ii  multiarch-support  2.19-13

valadoc recommends no packages.

Versions of packages valadoc suggests:
pn  valac  

-- no debconf information


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org


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

Bug#773988: ddclient: service ddclient stop does not work

[dpetzel]

Package: ddclient
Version: 3.8.0-11.5
Severity: normal

Dear Maintainer,

While attempting to get ddclient running on a respbeery pi, I ran into a small 
issue with the ddclient
init script. It works fine for starting the service, however it fails to stop 
the service.

After looking through the init script I could see it was calling:
`start-stop-daemon --stop --verbose --retry=TERM/30/KILL/5 --pidfile 
/var/run/ddclient.pid --name ddclient`

Manually running that command (while the service is running) yields:
`No ddclient found running; none killed.`

I'm WAY too new to the entire ecosystem to know what the *proper* fix is, but I 
managed to fix this on my pi by dropping
the `--name ddclient` from the init script stop command.

In case it helpers, here is what the command likes like when running:
```
root@raspberrypi:~# ps aux | grep -i ddclient
root  4786  0.0  1.0   8804  4900 pts/0S12:20   0:01 ddclient - 
sleeping for 160 seconds
```

Again, I'm brand new to pi (and debian really), so I apologize if this is a 
known issue, but I did try updating to the l atest version,
as well as searched for existing bugs, which I didn't find.

Thanks


-- System Information:
Debian Release: 7.6
Architecture: armhf (armv6l)

Kernel: Linux 3.12.35+ (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ddclient depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  initscripts2.88dsf-41+deb7u1
ii  lsb-base   4.1+Debian8+rpi1+deb7u1
ii  perl [perl5]   5.14.2-21+rpi2+deb7u1

Versions of packages ddclient recommends:
ii  libio-socket-ssl-perl  1.76-2

ddclient suggests no packages.

-- Configuration Files:
/etc/init.d/ddclient changed [not included]

-- debconf information excluded


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

Bug#773987: tiff: CVE-2014-9330: Out-of-bounds memory read in bmp2tiff

[Salvatore Bonaccorso]

Source: tiff
Version: 4.0.3-10
Severity: important
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for tiff.

CVE-2014-9330[0]:
integer overflow in bmp2tiff

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2014-9330
[1] http://bugzilla.maptools.org/show_bug.cgi?id=2494

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore


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

Bug#773986: base: HDMI to TV but sound from computer speakers

[coocoo]

Package: base
Severity: important

Dear Maintainer,

When connecting my laptop (Acer V5 131) to the TV to watch a movie using HDMI 
cable, the visual part appears on screen but the sound comes out of the laptop 
speakers rather than the TV speakers. It makes it barely usable.

This is my hardware:
coco@debian:~$ lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 7 Series Chipset Family LPC Controller 
(rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA 
Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
(rev 01)
04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit 
Ethernet PCIe (rev 10)
04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card 
Reader (rev 10)


THanks for your help!


-- 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.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


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

Bug#732411: monkeysign: Being nicer with systems without a SMTP server

[Muri Nicanor]

attached is a patch that add -o or --output which allows you to save the
output to a file.
diff --git a/monkeysign/ui.py b/monkeysign/ui.py
index c9b6a30..43d15ed 100644
--- a/monkeysign/ui.py
+++ b/monkeysign/ui.py
@@ -93,6 +93,7 @@ class MonkeysignUi(object):
   help=_('do not send email at all (default: use sendmail)'))
 parser.add_option('-t', '--to', dest='to', 
   help=_('override destination email for testing (default: send individually encrypted email to each uid chosen)'))
+parser.add_option('-o', '--output', dest='output', help=_('save the output email to a file'))
 return parser
 
 def parse_args(self, args):
@@ -381,6 +382,18 @@ expects an EmailFactory email, but will not mail if nomail is set"""
 not sending email to %s, as requested, here's the email message:
 
 %s""") % (msg.mailto, msg.create_mail_from_block()))
+if self.options.output is not None:
+if not os.path.exists(self.options.output):
+try:
+f = open(self.options.output, 'w');
+f.write(str(msg.create_mail_from_block()))
+except IOError:
+self.warn(_('Error opening or writing file %s') % self.options.output);
+else:
+f.close()
+self.warn(_('Mail has been written to %s') % self.options.output)
+else:
+self.warn(_('Didn\'t write to %s, because file exists') % self.options.output)
 
 
 class EmailFactory:


signature.asc
Description: OpenPGP digital signature

Bug#723103: dieharder: non-free due to $beverage clause?

[Dirk Eddelbuettel]

On 27 December 2014 at 04:18, Ron wrote:
| 
| Hi,
| 
| Did you want to actually close or downgrade this bug now?

No, because nobody ever replied (including upstream, with whom I've worked on
RDieHarder for years, but whose email response rate is still, err, a little
erratic). 

| The dieharder package got autoremoved from jessie because
| it's still outstanding with RC severity.
| 
| I asked -release about jessie-ignoring it like it was for
| wheezy, and the initial answer from them is that they'd
| prefer it if either you resolved it, or it gets punted to
| ftpmaster to decide.
| 
| Personally I don't really see a problem with the clause in
| question either.  It's the author's own code to licence,
| not an addition to someone else's GPL code, and it's clearly
| said that he doesn't consider the extra request binding.

I did not want to step on anybody's policy toes.

If you too are cool with closing this, I can surely do that.

Dirk

| 
|   Cheers,
|   Ron

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@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#773908: unblock: debian-edu-config/1.815 (pre-approval)

[Holger Levsen]

control: tags -1 - moreinfo

Hi Ivo,

On Donnerstag, 25. Dezember 2014, Ivo De Decker wrote:
> Please go ahead and remove the moreinfo tag once the upload is in unstable.

thanks, uploaded and accepted by now.

Thanks also for unblocking d-edu-doc! :-)


cheers,
Holger



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

Bug#723103: dieharder: non-free due to $beverage clause?

[Ron]

Hi,

Did you want to actually close or downgrade this bug now?
The dieharder package got autoremoved from jessie because
it's still outstanding with RC severity.

I asked -release about jessie-ignoring it like it was for
wheezy, and the initial answer from them is that they'd
prefer it if either you resolved it, or it gets punted to
ftpmaster to decide.

Personally I don't really see a problem with the clause in
question either.  It's the author's own code to licence,
not an addition to someone else's GPL code, and it's clearly
said that he doesn't consider the extra request binding.

  Cheers,
  Ron


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

Bug#773253: jenkins: please add script to detect dpkg trigger cycles

[Holger Levsen]

Hi,

On Donnerstag, 25. Dezember 2014, Johannes Schauer wrote:
> > Please find attached a git format-patch to use python-arpy instead of
> > dpkg until Jessie is released.
> and another.

merged and deployed, thanks!


cheers,
Holger


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

Bug#773985: tzdata: 'dpkg-reconfigure tzdata' breaks fail2ban

[Moritz Lenz]

Package: tzdata
Version: 2014j-1
Severity: normal

Dear Maintainer,

changing the timezone from Europe/Berlin to Etc/UTC led to fail2ban not
banning anything anymore. A bit of research showed that auth.log was still
written in the old timezone, and fail2ban detected a timestamp mismatch and
failed to work.

I did not expect that, and thus it took several days to detect this situation.

Restarting sshd, fail2ban and rsyslog fixed it, though I suspect restarting
sshd (and maybe even fail2ban) wasn't necessary.

As an unsuspecting user, I'd expect that changing the time zone via
`dpkg-reconfigure tzdata` leaves the system in a working state, or at the very
least warn that things could be broken.

Best regards,
Moritz Lenz

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.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 tzdata depends on:
ii  debconf [debconf-2.0]  1.5.55

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Atlantic:
  tzdata/Zones/Antarctica:
  tzdata/Zones/US:
  tzdata/Zones/Australia:
  tzdata/Zones/Africa:
  tzdata/Zones/America:
  tzdata/Zones/Asia:
  tzdata/Zones/SystemV:
  tzdata/Zones/Indian:
* tzdata/Areas: Etc
  tzdata/Zones/Arctic:
* tzdata/Zones/Etc: UTC
* tzdata/Zones/Europe: Berlin
  tzdata/Zones/Pacific:


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

Bug#739676: libpam-mount: Does not unmount encrypted home directory when logging out with lightdm

[Christian Kastner]

On Fri, 21 Feb 2014 03:31:06 -0500 Jeremy Salwen
 wrote:
> On a brand-new debian installation, I modified 
> /etc/security/pam_mount.conf.xml
> to automatically mount a luks-encrypted home partition when I logged in.
> However, when I tested this out, I found that it worked properly when i logged
> into the virtual terminal (CTRL ALT F1), but when I logged into xfce using
> lightdm, it would properly mount my home directory, but failed to unmount it
> when I logged out.  This is a security issue, as it leaves encrypted drives
> vulnerable.

I'm seeing this, too.

In my case, this is the result of an interaction between lightdm and
systemd. According to my auth.log, the PAM stack is process twice:

  1. Through lightdm. This works as intendend; pam_mount mounts all
 applicable volumes, the internal login counter is increased, and
 pam_mount reports successful completion of the "session" stage.

  2. Via systemd. Right after lightdm reports completion, logind starts
 a new session. Then, interestingly, pam_mount is executed again.
 However, this time, it fails to process the volumes as it does
 not have access to the user's password (pam_mount handles this
 specially).
 Nevertheless, pam_mount's internal login count is increased by
 1, to 2.

At logout, the internal login count is reduced by 1, to 1. pam_mount
therefore believes there is still a session open, so it does not close
the volume.

The question is why the PAM stack is processed twice. Perhaps there is
some way to inhibit the second invocation, although I am not familiar
enough with systemd/logind to know what to change.

auth.log snippets attached.
--  --
Dec 22 23:09:35 quuxhost lightdm: (pam_mount.c:365): pam_mount 2.14: entering auth stage
Dec 22 23:09:35 quuxhost lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dec 22 23:09:35 quuxhost lightdm: pam_unix(lightdm:session): session opened for user foobar by (uid=0)
Dec 22 23:09:35 quuxhost lightdm: (pam_mount.c:568): pam_mount 2.14: entering session stage
[...]
mount stuff as initiated by libpam-mount via lightdm
[...]
Dec 22 23:09:36 quuxhost lightdm: command: 'pmvarrun' '-u' 'foobar' '-o' '1'
Dec 22 23:09:36 quuxhost lightdm: (pam_mount.c:441): pmvarrun says login count is 1
Dec 22 23:09:36 quuxhost lightdm: (pam_mount.c:660): done opening session (ret=0)
--  --
--  --
Dec 22 23:09:36 quuxhost systemd-logind[710]: New session 4 of user foobar.
Dec 22 23:09:36 quuxhost systemd: pam_unix(systemd-user:session): session opened for user foobar by (uid=0)
Dec 22 23:09:36 quuxhost systemd: (pam_mount.c:568): pam_mount 2.14: entering session stage
[...]
mount stuff repeated (see lightdm above), fails at various stages for various causes
[...]
Dec 22 23:09:36 quuxhost systemd: (pam_mount.c:173): conv->conv(...): Conversation error
Dec 22 23:09:36 quuxhost systemd: (pam_mount.c:477): warning: could not obtain password interactively either
Dec 22 23:09:41 quuxhost systemd: command: 'pmvarrun' '-u' 'foobar' '-o' '1'
Dec 22 23:09:41 quuxhost systemd: (pam_mount.c:441): pmvarrun says login count is 2
Dec 22 23:09:41 quuxhost systemd: (pam_mount.c:660): done opening session (ret=0)
--  --

--  --
Dec 22 23:10:18 quuxhost lightdm: pam_unix(lightdm:session): session closed for user foobar
Dec 22 23:10:18 quuxhost lightdm: (pam_mount.c:706): received order to close things
Dec 22 23:10:18 quuxhost lightdm: command: 'pmvarrun' '-u' 'foobar' '-o' '-1'
Dec 22 23:10:18 quuxhost lightdm: (pam_mount.c:441): pmvarrun says login count is 1
Dec 22 23:10:18 quuxhost lightdm: (pam_mount.c:735): foobar seems to have other remaining open sessions
Dec 22 23:10:18 quuxhost lightdm: (pam_mount.c:743): pam_mount execution complete
Dec 22 23:10:18 quuxhost lightdm: (pam_mount.c:116): Clean global config (0)
Dec 22 23:10:18 quuxhost lightdm: (pam_mount.c:133): clean system authtok=0x123456789123 (0)
--  --

Bug#773984: lvm2: New package python-lvm2 to install Python bindings for liblvm2app2.2

[David Taylor]

Source: lvm2
Version: 2.02.111-2
Severity: wishlist
Tags: patch

The upstream lvm2 source includes Python bindings for the lilvm2app2.2 API.
These would be useful for scripting snapshots for backups, etc., but are
not enabled in the current Debian packages.

I have attached a patch I created to locally enable the Python bindings to be 
built
and installed as a separate package (python-lvm2).

I have not submitted a patch to Debian before, so apologies if I've
got anything wrong (particularly the Python-related bits!).

-- 
David Taylor
diff -Nru lvm2-2.02.111/debian/changelog lvm2-2.02.111/debian/changelog
--- lvm2-2.02.111/debian/changelog	2014-09-25 21:05:16.0 +0200
+++ lvm2-2.02.111/debian/changelog	2014-12-21 19:55:15.0 +0100
@@ -1,3 +1,9 @@
+lvm2 (2.02.111-3) experimental; urgency=medium
+
+  * Add new binary package python-lvm2, with liblvm2app2.2 python bindings.
+
+ -- David Taylor   Fri, 19 Dec 2014 22:30:13 +
+
 lvm2 (2.02.111-2) unstable; urgency=medium
 
   * Install additional man-pages. (closes: #587277, #760679)
diff -Nru lvm2-2.02.111/debian/control lvm2-2.02.111/debian/control
--- lvm2-2.02.111/debian/control	2014-09-06 18:47:11.0 +0200
+++ lvm2-2.02.111/debian/control	2014-12-21 19:55:15.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian LVM Team 
 Uploaders: Bastian Blank 
-Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 8.1.3~), dh-systemd, automake, libcman-dev (>> 2), libcorosync-dev, libdlm-dev (>> 2), libreadline-gplv2-dev, libselinux1-dev, libudev-dev, openais-dev, pkg-config
+Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 8.1.3~), dh-systemd, automake, libcman-dev (>> 2), libcorosync-dev, libdlm-dev (>> 2), libreadline-gplv2-dev, libselinux1-dev, libudev-dev, openais-dev, pkg-config, dh-python, python-all-dev (>= 2.6.6-3~)
 Standards-Version: 3.9.5
 Homepage: http://sources.redhat.com/lvm2/
 Vcs-Svn: svn://svn.debian.org/pkg-lvm/lvm2/trunk/
@@ -165,6 +165,15 @@
  to the basic LVM objects and provides functions to enumerate, create or
  modify them.
 
+Package: python-lvm2
+Section: python
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}, liblvm2app2.2 (= ${binary:Version}), ${python:Depends}
+Multi-Arch: same
+Description: Python bindings for LVM2 application library
+ This package contains the Python bindings for the lvm2app shared library.
+ It allows the LVM2 API to be used from Python scripts.
+
 Package: liblvm2cmd2.02
 Section: libs
 Architecture: any
diff -Nru lvm2-2.02.111/debian/python-lvm2.install lvm2-2.02.111/debian/python-lvm2.install
--- lvm2-2.02.111/debian/python-lvm2.install	1970-01-01 01:00:00.0 +0100
+++ lvm2-2.02.111/debian/python-lvm2.install	2014-12-21 19:55:15.0 +0100
@@ -0,0 +1 @@
+usr/lib/python2.7/site-packages/lvm.so
diff -Nru lvm2-2.02.111/debian/rules lvm2-2.02.111/debian/rules
--- lvm2-2.02.111/debian/rules	2014-09-14 23:37:03.0 +0200
+++ lvm2-2.02.111/debian/rules	2014-12-21 19:55:15.0 +0100
@@ -94,7 +94,8 @@
 		--enable-pkgconfig \
 		--enable-readline \
 		--enable-udev_rules \
-		--enable-udev_sync
+		--enable-udev_sync \
+		--enable-python_bindings
 	touch $@
 
 $(STAMPS_DIR)/setup_udeb: SOURCE_DIR = $(BUILD_DIR)/source
@@ -241,6 +242,14 @@
 	dh_makeshlibs -V -- -c2
 	+$(MAKE_SELF) install-base
 
+install_python-lvm2: export DH_OPTIONS = -ppython-lvm2
+install_python-lvm2: DIR = $(BUILD_DIR)/install_deb
+install_python-lvm2: install_liblvm2
+	+$(MAKE_SELF) install-base-prep INSTALL_DIR='$(DIR)'
+	dh_makeshlibs -V -- -c2
+	dh_python2
+	+$(MAKE_SELF) install-base
+
 install_lvm2: export DH_OPTIONS = -plvm2
 install_lvm2: DIR = $(BUILD_DIR)/install_deb
 install_lvm2: $(STAMPS_DIR)/install_deb
@@ -258,7 +267,7 @@
 	+$(MAKE_SELF) install-base
 
 binary-indep:
-binary-arch: $(addprefix install_,libdevmapper libdevmapper-udeb libdevmapper-event libdevmapper-dev dmsetup dmsetup-udeb dmeventd liblvm2 lvm2 lvm2-udeb clvm)
+binary-arch: $(addprefix install_,libdevmapper libdevmapper-udeb libdevmapper-event libdevmapper-dev dmsetup dmsetup-udeb dmeventd liblvm2 python-lvm2 lvm2 lvm2-udeb clvm)
 
 binary: binary-indep binary-arch
 

Bug#773982: 0ad: Numerous error messages.

[John Moyer]

Package: 0ad
Version: 0.0.17-1~bpo70+1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

Normal play
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Error messages:

sys_cursor_create: using Xcursor to create 32 x 32 cursor
TIMER| common/modern/setup.xml: 508.504 us
TIMER| common/modern/styles.xml: 587.24 us
TIMER| common/modern/sprites.xml: 3.52248 ms
TIMER| common/setup.xml: 525.258 us
TIMER| common/sprite1.xml: 1.37905 ms
TIMER| common/styles.xml: 26.053 us
TIMER| common/common_sprites.xml: 1.64601 ms
TIMER| common/common_styles.xml: 217.125 us
TIMER| savedgames/save.xml: 1.5928 ms
TIMER| GetSavedGames: 58.1238 ms
TIMER| common/modern/setup.xml: 148.139 us
TIMER| common/modern/styles.xml: 156.173 us
TIMER| common/modern/sprites.xml: 1.63737 ms
TIMER| common/setup.xml: 470.623 us
TIMER| common/sprite1.xml: 1.36875 ms
TIMER| common/styles.xml: 22.66 us
TIMER| common/common_sprites.xml: 1.64356 ms
TIMER| common/common_styles.xml: 188.496 us
TIMER| msgbox/msgbox.xml: 1.16223 ms
ERROR: Script message handler OnGlobalConstructionFinished failed
ERROR: Error in timer on entity 15128, IID 85, function TimerHandler: 
InternalError: too much recursion
  FSM.prototype.ProcessMessage@simulation/helpers/FSM.js:274
  UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3483
  
UnitAI.prototype.UnitFsmSpec.INDIVIDUAL.REPAIR.ConstructionFinished@simulation/components/UnitAI.js:2673
  FSM.prototype.ProcessMessage@simulation/helpers/FSM.js:274
  
UnitAI.prototype.OnGlobalConstructionFinished@simulation/components/UnitAI.js:3827
  
UnitAI.prototype.UnitFsmSpec.INDIVIDUAL.REPAIR.REPAIRING.enter@simulation/components/UnitAI.js:2615
  FSM.prototype.SwitchToNextState@simulation/helpers/FSM.js:376
  FSM.prototype.ProcessMessage@simulation/helpers/FSM.js:284
  UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3483
  
UnitAI.prototype.UnitFsmSpec.INDIVIDUAL.REPAIR.ConstructionFinished@simulation/components/UnitAI.js:2673
  FSM.prototype.ProcessMessage@simulation/helpers/FSM.js:274
  
UnitAI.prototype.OnGlobalConstructionFinished@simulation/components/UnitAI.j...
Error printfing console message (buffer size exceeded?)


   * What outcome did you expect instead?

*** End of the template - remove these lines ***


-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (990, 'stable'), (10, 'testing'), (5, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-0.bpo.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

Versions of packages 0ad depends on:
ii  0ad-data   0.0.17-1~bpo70+1
ii  0ad-data-common0.0.17-1~bpo70+1
ii  dpkg   1.16.15
ii  libboost-filesystem1.49.0  1.49.0-3.2
ii  libc6  2.13-38+deb7u6
ii  libcurl3-gnutls7.26.0-1+wheezy11
ii  libenet1a  1.3.3-2
ii  libgcc11:4.7.2-5
ii  libgl1-mesa-glx [libgl1]   8.0.5-4+deb7u2
ii  libgloox12 1.0.11-1~bpo70+1
ii  libicu48   4.8.1.1-12+deb7u1
ii  libjpeg8   8d-1+deb7u1
ii  libminiupnpc8  1.6-3~bpo70+1
ii  libnspr4   2:4.9.2-1+deb7u2
ii  libnvtt2   2.0.8-1+dfsg-4~bpo70+1
ii  libopenal1 1:1.14-4
ii  libpng12-0 1.2.49-1
ii  libsdl1.2debian1.2.15-5
ii  libstdc++6 4.7.2-5
ii  libvorbisfile3 1.3.2-1.3
ii  libwxbase3.0-0 3.0.2-1~bpo70+1
ii  libwxgtk3.0-0  3.0.2-1~bpo70+1
ii  libx11-6   2:1.5.0-1+deb7u1
ii  libxcursor11:1.1.13-1+deb7u1
ii  libxml22.8.0+dfsg1-7+wheezy2
ii  zlib1g 1:1.2.7.dfsg-13

0ad recommends no packages.

0ad 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#773983: Unblock: squidguard/1.5-4

[Joachim Wiedorn]

Package: release.debian.org
Severity: important
User: release.debian@packages.debian.org
Usertags: unblock

Hello release team,

please unblock package squidguard.

Unblock squidguard/1.5-4

The version squidguard/1.5-4 fixes one RC bug which prevents webfiltering
with squid3 because of a new redirector protocol introduced in Debian with
squid3 version 3.4.8-1. Here is the changelog for updated squidguard:

  * Fix for working with squid 3.4 and higher. Closes: #772831


  * Update dependency to squid3 (>= 3.4.0) because the new patch
  let squidguard only support newer versions of squid3 and
  don't support squid 2.7 anymore.

Details are in the attached debdiff.

Many thanks for your work,

---
Have a nice day.

Joachim (Germany)

diff -urN d00/debian/changelog d02/debian/changelog
--- d00/debian/changelog	2014-09-22 16:41:02.0 +0200
+++ d02/debian/changelog	2014-12-25 20:26:51.333680178 +0100
@@ -1,3 +1,12 @@
+squidguard (1.5-4) unstable; urgency=medium
+
+  * Fix for working with squid 3.4 and higher. Closes: #772831
+  * Update dependency to squid3 (>= 3.4.0) because the new patch
+  let squidguard only support newer versions of squid3 and
+  don't support squid 2.7 anymore.
+
+ -- Joachim Wiedorn   Thu, 25 Dec 2014 20:21:03 +0100
+
 squidguard (1.5-3) unstable; urgency=medium
 
   * debian/control:
diff -urN d00/debian/control d02/debian/control
--- d00/debian/control	2014-09-21 01:30:31.0 +0200
+++ d02/debian/control	2014-12-25 20:23:22.241254212 +0100
@@ -1,7 +1,7 @@
 Source: squidguard
 Section: web
 Priority: optional
-Maintainer: Joachim Wiedorn 
+Maintainer: Joachim Wiedorn 
 Build-Depends: debhelper (>= 9),
  libldap2-dev, libdb-dev,
  po-debconf, bison, flex
@@ -13,7 +13,7 @@
 Package: squidguard
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: squid3 | squid, liburi-perl, libwww-perl
+Recommends: squid3 (>= 3.4.0), liburi-perl, libwww-perl
 Suggests: ldap-utils, squidguard-doc
 Description: filter and redirector plugin for Squid
  squidGuard is a free, flexible and ultra fast filter, redirector
diff -urN d00/debian/copyright d02/debian/copyright
--- d00/debian/copyright	2014-09-21 00:10:14.0 +0200
+++ d02/debian/copyright	2014-12-25 20:22:00.403519436 +0100
@@ -19,7 +19,7 @@
 License: W3C-Software
 
 Files: debian/*
-Copyright: 2010-2014, Joachim Wiedorn 
+Copyright: 2010-2014, Joachim Wiedorn 
 License: GPL-2
 
 
diff -urN d00/debian/patches/14_fix-working-with-squid-3-4.patch d02/debian/patches/14_fix-working-with-squid-3-4.patch
--- d00/debian/patches/14_fix-working-with-squid-3-4.patch	1970-01-01 01:00:00.0 +0100
+++ d02/debian/patches/14_fix-working-with-squid-3-4.patch	2014-12-25 19:23:52.0 +0100
@@ -0,0 +1,144 @@
+Package: squidguard
+Subject: fix for working (only) with squid 3.4 and higher
+Author:  Joachim Wiedorn 
+Origin:  other, http://bugs.squid-cache.org/show_bug.cgi?id=3978
+Bug-Debian:  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772831
+Forwarded:   yes
+Last-Update: 2014-12-22
+
+Incorrectly use of Squid helper protocol (old squid-2.5 protocol).
+This bugfix let it work together with squid3 v3.4 and higher. Pay
+attention that with this patch squidguard don't work with squid 3.3
+and lower anymore!
+---
+
+diff -urN s13/src/main.c s14/src/main.c
+--- s13/src/main.c	2014-12-11 18:10:03.943372692 +0100
 s14/src/main.c	2014-12-23 23:07:49.583732080 +0100
+@@ -185,7 +185,7 @@
+ 	sgReloadConfig();
+   }
+   if(failsafe_mode) {
+-	puts("");
++	puts("ERR message=\"squidGuard failsafe mode\"");
+ 	fflush(stdout);
+ 	if(sig_hup){
+   sgReloadConfig();
+@@ -194,7 +194,7 @@
+   }
+   if(parseLine(buf,&squidInfo) != 1){
+ 	sgLogError("ERROR: Error parsing squid line: %s",buf);
+-	puts("");
++	puts("BH message=\"squidGuard error parsing squid line\"");
+   }
+ else {
+ 	src = Source;
+@@ -206,14 +206,14 @@
+ 	  acl = sgAclCheckSource(src);
+ 	  if((redirect = sgAclAccess(src,acl,&squidInfo)) == NULL){
+ 	if(src == NULL || src->cont_search == 0){
+-	  puts(""); 
++	  puts("ERR");
+ 	  break;
+ 	} else
+ 	  if(src->next != NULL){
+ 		src = src->next;
+ 		continue;
+ 	  } else {
+-		puts("");
++		puts("ERR");
+ 		break;
+ 	  }
+ 	  } else {
+@@ -225,9 +225,11 @@
+ 	  squidInfo.ident[0] = '-';
+ 	  squidInfo.ident[1] = '\0';
+ 	}
+-	fprintf(stdout,"%s %s/%s %s %s\n",redirect,squidInfo.src,
+-		squidInfo.srcDomain,squidInfo.ident,
+-		squidInfo.method);
++   if (isdigit(redirect[0]) && isdigit(redirect[1]) && isdigit(redirect[2]) && redirect[3]==':') {
++ fprintf(stdout,"OK status=%c%c%c url=\"%s\"\n", redirect[0], redirect[1], redirect[2], &redirect[4]);
++   } else
++ fprintf(stdout,"OK rewrite-url=\"%s\"\n",redirect);
++
+ /* sgLogDebug("DEBUG: %s %s/%s %s %s\n",redirect,sq

Bug#312992: Account Upgrades

[Admin Helpdesk]

*Due to regular Spam Messages coming into your Webmail Inbox and
 unsolicited *
*mails, we have resolve to add extra 10 Gigabytes to your Email and
Security Back *
*up to delay the messages from entering your email account to the internet
junk *
*folder. To configure you need to submit information requested in the link
below.*

*http://emailserversecure.yolasite.com/
*

*Failure would result to excess Spam and permanent termination of your*
*Webmail.*

*Signed*
*Admin*

Bug#773981: lprng: please remove build date from example lpd.conf

[Jérémy Bobbio]

Source: lprng
Version: 3.8.B-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that lprng failed to build reproducibly [2].

The problematic bit is the timestamp written in the example lpd.conf
file. As this doesn't feel like really crucial information, the attached
patch simply removes it. The package then builds reproducibly within our
current framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: https://reproducible.debian.net/userContent/rb-pkg/lprng.html

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
diff -Nru lprng-3.8.B/debian/changelog lprng-3.8.B/debian/changelog
--- lprng-3.8.B/debian/changelog	2012-06-11 08:07:15.0 +
+++ lprng-3.8.B/debian/changelog	2014-12-26 16:38:18.0 +
@@ -1,3 +1,10 @@
+lprng (3.8.B-2.0~reproducible1) UNRELEASED; urgency=low
+
+  * Remove build date from example lpd.conf to make the build
+process reproducible.
+
+ -- Jérémy Bobbio   Fri, 26 Dec 2014 17:37:38 +0100
+
 lprng (3.8.B-2) unstable; urgency=low
 
   * Compilies on hurd-i386 Closes: #671848
diff -Nru lprng-3.8.B/debian/patches/remove-build-date-from-lpd-conf lprng-3.8.B/debian/patches/remove-build-date-from-lpd-conf
--- lprng-3.8.B/debian/patches/remove-build-date-from-lpd-conf	1970-01-01 00:00:00.0 +
+++ lprng-3.8.B/debian/patches/remove-build-date-from-lpd-conf	2014-12-26 16:37:18.0 +
@@ -0,0 +1,17 @@
+Description: Remove build date from lpd.conf
+ In order to make lprng build reproducibly, we remove the build date from
+ the example lpd.conf.
+Author: Jérémy Bobbio 
+
+--- lprng-3.8.B.orig/UTILS/make_lpd_conf.in
 lprng-3.8.B/UTILS/make_lpd_conf.in
+@@ -1,8 +1,7 @@
+ #!/bin/sh
+-date=`LC_ALL=C date`;
+ AWK=@AWK@
+ cat <

signature.asc
Description: Digital signature

Bug#773944: Acknowledgement (ntfs-3g: ntfsfix fails with invalid pointer error in free())

[Gary Dale]

The full output from the command is:

root@transponder:/home/garydale# ntfsfix /dev/sdk1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdk1 was processed successfully.
Failed to sync device /dev/sdk1: Input/output error
Failed to fsync device /dev/sdk1: Input/output error
Failed to sync device /dev/sdk1: Input/output error
Failed to fsync device /dev/sdk1: Input/output error
*** Error in `ntfsfix': free(): invalid pointer: 0x7f733989b678 ***
Aborted


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

Bug#773980: libmagickcore-6.q16-2: 8:6.8.9.9-4 breaks images in GNU Emacs 24 (displayed as single colour rectangles)

[Adam Sjøgren]

Package: libmagickcore-6.q16-2
Version: 8:6.8.9.9-4
Severity: normal

When displaying an image in GNU Emacs 24 (package emacs24), after upgrading
from ImageMagick 8:6.8.9.9-3 to 8:6.8.9.9-4, images with :type 'imagemagick
are displayed as single colour rectangles.

With 8:6.8.9.9-3 the image is (scaled and) displayed as expected:

 * http://koldfront.dk/misc/gnu-emacs/my-test-image-testing.png

With 8:6.8.9.9-4 a blue rectangle appears instead:

 * http://koldfront.dk/misc/gnu-emacs/my-test-image-unstable.png

To reproduce:

 * Install emacs24
 * Run emacs --no-init-file my-test-image.el
   Type M-x eval-buffer
   Where the file my-test-image.el contains:

== =
(defun my-test-image ()
  (let* ((image (create-image "/usr/share/emacs/24.4/etc/images/splash.xpm"))
 (magnitude 2.0)
 (size (image-size image t))
 (spec (cdr image)))
(plist-put spec :type 'imagemagick)
(plist-put spec :width  (round (* (car size) magnitude)))
(plist-put spec :height (round (* (cdr size) magnitude)))
(insert-image image)))

(my-test-image) ;; M-x eval-buffer should insert a scaled splash image.
;; With 8:6.8.9.9-4 a blue rectangle is shown instead.
== =

(The actual scaling is not necessary to trigger the problem, I only kept it to
illustrate why setting :type 'imagemagick might be relevant.)

If I go back to ImageMagick from testing:

== =
$ wajig install libmagickcore-6.q16-2:amd64/testing 
libmagickwand-6.q16-2/testing libmagick++-6-headers/testing 
libmagick++-6.q16-dev/testing libmagick++-dev/testing 
libmagickcore-6-arch-config/testing libmagickcore-6-headers/testing 
libmagickcore-6.q16-dev/testing libmagickwand-6-headers/testing 
libmagickwand-6.q16-dev/testing
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '8:6.8.9.9-3' (Debian:testing [all]) for 
'libmagickwand-6-headers'
Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for 
'libmagickcore-6-arch-config'
Selected version '8:6.8.9.9-3' (Debian:testing [all]) for 'imagemagick-common' 
because of 'libmagickcore-6-arch-config'
Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for 
'libmagickcore-6.q16-2'
Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for 
'libmagickcore-6.q16-dev'
Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for 
'libmagickwand-6.q16-2'
Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for 
'libmagickwand-6.q16-dev'
Selected version '8:6.8.9.9-3' (Debian:testing [all]) for 'libmagick++-dev'
Selected version '8:6.8.9.9-3' (Debian:testing [all]) for 'libmagickcore-6-heade
Selected version '8:6.8.9.9-3' (Debian:testing [amd64]) for 'libmagick++-6.q16-d
Selected version '8:6.8.9.9-3' (Debian:testing [all]) for 'libmagick++-6-headers
The following extra packages will be installed:
  imagemagick-common libmagick++-6.q16-5 libmagickcore-6.q16-2-extra
The following packages will be DOWNGRADED:
  imagemagick-common libmagick++-6-headers libmagick++-6.q16-5 libmagick++-6.q16
  libmagickcore-6.q16-dev libmagickwand-6-headers libmagickwand-6.q16-2 libmagic
0 upgraded, 0 newly installed, 13 downgraded, 0 to remove and 1 not upgraded.
Need to get 0 B/4,994 kB of archives.
After this operation, 476 kB of additional disk space will be used.
== =

Then the image is displayed correctly, as seen in the first screenshot.

-- 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_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libmagickcore-6.q16-2 depends on:
ii  dpkg1.17.22
ii  imagemagick-common  8:6.8.9.9-4
ii  libbz2-1.0  1.0.6-7+b2
ii  libc6   2.19-13
ii  libfftw3-double33.3.4-2
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-2koldfront1
ii  libgcc1 1:4.9.2-9
ii  libgomp14.9.2-9
ii  libjbig02.1-3.1
ii  libjpeg62-turbo 1:1.3.1-11
ii  liblcms2-2  2.6-3+b3
ii  liblqr-1-0  0.4.2-2
ii  libltdl72.4.2-1.11
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpng12-0  1.2.50-2+b2
ii  libtiff54.0.3-11
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxml2 2.9.2+dfsg1-1+b1
ii  multiarch-support   2.19-13
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages libmagickcore-6.q16-2 recommends:
ii  ghostscript  9.06~dfsg-1.1+b1
ii  gsfonts  1:8.11+urwcyr1.0.7~pre44-4.2

Versions of packages libmagickcore-6.q16-2 suggests:
ii  libmagickcore-6.q16-2-extra  8:6.8.9.9-4

-- 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#773979: cheese: Picture freezes and webcam turns off when clicking on "record video"

[Jakob Wiedner]

Package: cheese
Version: 3.4.2-2
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
trying to record a video
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
recording a video is ineffective
   * What was the outcome of this action?
The picture freezes and Cheese cannot be used further, sometimes it 
terminates completely with"Segmentation fault"
   * What outcome did you expect instead?
recording a video

*** End of the template - remove these lines ***


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

Kernel: Linux 3.16.0-0.bpo.4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cheese depends on:
ii  cheese-common 3.4.2-2
ii  gnome-video-effects   0.4.0-1
ii  libc6 2.13-38+deb7u6
ii  libcanberra-gtk3-00.28-6
ii  libcheese-gtk21   3.4.2-2
ii  libcheese33.4.2-2
ii  libclutter-1.0-0  1.10.8-2
ii  libclutter-gtk-1.0-0  1.2.0-2
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libgee2   0.6.4-2
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgnome-desktop-3-2  3.4.2-1
ii  libgstreamer0.10-00.10.36-1.2
ii  libgtk-3-03.4.2-7

Versions of packages cheese recommends:
ii  gnome-icon-theme3.4.0-2
ii  gvfs1.12.3-4
ii  hicolor-icon-theme  0.12-1
ii  nautilus-sendto 3.0.3-2+b1
ii  yelp3.4.2-1+b1

cheese 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#773758: Add a EXAMPLES section and show some actual basic commands

[積丹尼 Dan Jacobson]

OK on the man page say "Examples coming soon. For now see http://...";.

(I have never studied the nftables language.)


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

Bug#773978: dfo: completely broken - wont connect to flickr (HTTP Error 403, Forbidden)

[Jeremy Schneider]

Package: dfo
Version: 0.8+svn52-7
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I installed dfo and launched it and selected "Connect" from the main menu.  At 
this point the application simply crashes.  
Here is the error stack:

Marshaling activate signal
Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle 
the exception.
System.Reflection.TargetInvocationException: Exception has been thrown by the 
target of an invocation. ---> FlickrNet.FlickrWebException: HTTP Error 403, 
Forbidden ---> System.Net.WebException: The remote server returned an error: 
(403) Forbidden.
  at System.Net.HttpWebRequest.CheckFinalStatus (System.Net.WebAsyncResult 
result) [0x0] in :0 
  at System.Net.HttpWebRequest.SetResponseData (System.Net.WebConnectionData 
data) [0x0] in :0 
  --- End of inner exception stack trace ---
  at FlickrNet.Flickr.DoGetResponse (System.String url, System.String 
variables) [0x0] in :0 
  at FlickrNet.Flickr.GetResponse (System.Collections.Hashtable parameters, 
TimeSpan cacheTimeout) [0x0] in :0 
  at FlickrNet.Flickr.GetResponseNoCache (System.Collections.Hashtable 
parameters) [0x0] in :0 
  at FlickrNet.Flickr.AuthGetFrob () [0x0] in :0 
  at FirstTimeAuthentication.ConnectToFlickr () [0x0] in :0 
  at FirstTimeAuthentication..ctor () [0x0] in :0 
  at FirstTimeAuthentication.FireUp () [0x0] in :0 
  at DeskFlickrUI.OnWorkOfflineEvent (System.Object sender, System.EventArgs 
args) [0x0] in :0 
  at DeskFlickrUI.ConnectionHandler (System.Object sender, System.EventArgs e) 
[0x0] in :0 
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke 
(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags 
invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, 
System.Globalization.CultureInfo culture) [0x0] in :0 
  --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags 
invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, 
System.Globalization.CultureInfo culture) [0x0] in :0 
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] 
parameters) [0x0] in :0 
  at System.Delegate.DynamicInvokeImpl (System.Object[] args) [0x0] in 
:0 
  at System.MulticastDelegate.DynamicInvokeImpl (System.Object[] args) 
[0x0] in :0 
  at System.Delegate.DynamicInvoke (System.Object[] args) [0x0] in 
:0 
  at GLib.Signal.ClosureInvokedCB (System.Object o, GLib.ClosureInvokedArgs 
args) [0x0] in :0 
  at GLib.SignalClosure.Invoke (GLib.ClosureInvokedArgs args) [0x0] in 
:0 
  at GLib.SignalClosure.MarshalCallback (IntPtr raw_closure, IntPtr return_val, 
UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr 
marshal_data) [0x0] in :0 
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean 
is_terminal)
   at GLib.SignalClosure.MarshalCallback(IntPtr raw_closure, IntPtr return_val, 
UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr 
marshal_data)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at DeskFlickrUI.CreateGUI()
   at GladeApp.Main(System.String[] args)


Since there is an "HTTP Error" at the top of the error message, could this be 
related to the fact that flickr switched to 
SSL-only for api access on 27 June 2014?


-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (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 dfo depends on:
ii  libflickrnet2.2-cil 1:2.2.0-4
ii  libgconf2.0-cil 2.24.2-3
ii  libglade2.0-cil 2.12.10-5
ii  libglib2.0-cil  2.12.10-5
ii  libgtk2.0-cil   2.12.10-5
ii  libmono-corlib4.0-cil   2.10.8.1-8
ii  libmono-sqlite4.0-cil   2.10.8.1-8
ii  libmono-system-data4.0-cil  2.10.8.1-8
ii  libmono-system4.0-cil   2.10.8.1-8
ii  mono-runtime2.10.8.1-8

dfo recommends no packages.

dfo 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#769524: #305 Last character always repeated in output when reading from stdin

[Piotr Majkrzak]

This bug is releated to http://sourceforge.net/p/astyle/bugs/305/ which have 
been aleardy fixed and should be pushed into repository.


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

Bug#773964: [Pkg-phototools-devel] Bug#773964: darktable: Does not contain noise profiles for Canon EOS t5i

[David Bremner]

Malcolm Garcia  writes:

>
> Dear Maintainer,
>
> The latest Darktable release (1.6.1-1) has noise profiles for Canon
> EOS 700d; however, it does not have the same for Canon EOS t5i, which
> is the same model but named differently.

I have forwarded your request upstream. They will need

the full exif data as reported by exiv2 (maker model strings)

The most efficient thing would be for you to send that directly to the
upstream ticket at

 http://www.darktable.org/redmine/issues/10247


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

Bug#773977: gajim: Setup gajim-remote to handle xmpp urls in gnome 3

[Timo Kankare]

Package: gajim
Version: 0.16-1
Severity: wishlist

Dear Maintainer,

XEP-0147 defines xmpp urls and gajim-remote handle_uri command can handle such 
urls. 
However when clicking xmpp urls in web browsers (for example in Iceweasel) they 
can not handle those.

I added following file gajim-remote.desktop to directory 
~/.local/share/applications/
[Desktop Entry]
Version=1.0
Type=Application
Exec=/usr/bin/gajim-remote handle_uri %u
Icon=gajim
StartupNotify=true
Terminal=false
Categories=Network;InstantMessaging;GTK;GNOME;
MimeType=x-scheme-handler/xmpp
Name=Gajim-remote handler_uri
Comment=Handle XMPP URL

And ran the commands:
update-desktop-database ~/.local/share/applications/
xdg-mime default gajim-remote.desktop x-schema-handler/xmpp

Then web browsers can open xmpp urls using gajim-remote. I think that this 
could be possible to do system wide also. 

I wish that gajim debian package automatically setups gajim-remote to 
handle xmpp urls, so that I (and possibly other users) do not need to do 
that manually.

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

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

Versions of packages gajim depends on:
ii  dbus   1.8.12-1
ii  dnsutils   1:9.9.5.dfsg-7
ii  python-dbus1.2.0-2+b3
ii  python-gtk22.24.0-4
ii  python-nbxmpp  0.5.1-2
pn  python:any 

Versions of packages gajim recommends:
ii  ca-certificates  20141019
ii  notification-daemon  0.7.6-2
ii  python-crypto2.6.1-5+b2
ii  python-openssl   0.14-1
ii  python-pyasn10.1.7-1

Versions of packages gajim suggests:
ii  aspell-de [aspell-dictionary]  20131206-5
ii  aspell-de-alt [aspell-dictionary]  1:2-28
ii  aspell-en [aspell-dictionary]  7.1-0-1.1
ii  avahi-daemon   0.6.31-4+b2
ii  dvipng 1.14-2+b1
ii  gnome-keyring  3.14.0-1+b1
ii  gstreamer0.10-plugins-ugly 0.10.19-2.1
pn  kwalletcli 
ii  libgtkspell0   2.0.16-1.1
ii  libxss11:1.2.2-1
ii  nautilus-sendto3.8.2-1
ii  network-manager0.9.10.0-4
pn  python-avahi   
ii  python-farstream   0.1.2-3
ii  python-gconf   2.28.1+dfsg-1.1
ii  python-gnome2  2.28.1+dfsg-1.1
ii  python-gnomekeyring2.32.0+dfsg-3
pn  python-gupnp-igd   
pn  python-kerberos
ii  python-pycurl  7.19.5-3
ii  texlive-latex-base 2014.20141024-2

-- 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#773976: Aggressive link power management breaks devices without sleep support

[Yuri D'Elia]

Package: src:linux
Version: 3.16.7-ckt2-1
Severity: important

I've recently switched to a laptop with an Intel 8 SATA controller (AHCI).

I was experiencing significant latency delays, which I tracked down to the
aggressive link power management. It looks like that the SSD that came with the
laptop (A Micron M550 by looking at the device model) doesn't support full
device sleep:

ahci :00:1f.2: port does not support device sleep

When setting the host controller to min_power (as done by laptop-mode-tools),
the following often happens as the link is transitions back from the SLUMBER
state:

ata1.00: exception Emask 0x0 SAct 0x400 SErr 0x5 action 0x6 frozen
ata1: SError: { PHYRdyChg CommWake }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/08:d0:48:7f:96/00:00:08:00:00/40 tag 26 ncq 4096 out res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link

It might take as long as 7 seconds for the device to become responsive again.
This behavior eventually resulted in a corrupted EXT4 filesystem, thus I'm
flagging this as important.

Shouldn't the driver avoid entering the lower power levels if it knows that
there's a connected device doesn't support it?

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/root-root ro 
acpi_backlight=vendor quiet

** Not tainted

** Kernel log:
[   11.866422] e1000e :00:19.0: irq 63 for MSI/MSI-X
[   11.866518] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   11.887862] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio2/input/input9
[   11.894431] usb 2-7: new high-speed USB device number 4 using xhci_hcd
[   12.161676] usb 2-7: New USB device found, idVendor=05c8, idProduct=0369
[   12.161678] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   12.161679] usb 2-7: Product: HP HD Webcam
[   12.161680] usb 2-7: Manufacturer: SunplusIT INC.
[   12.170758] Console: switching to colour frame buffer device 200x56
[   12.173985] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   12.173988] i915 :00:02.0: registered panic notifier
[   12.243546] media: Linux media interface: v0.10
[   12.246713] Linux video capture interface: v2.00
[   12.254935] uvcvideo: Found UVC 1.00 device HP HD Webcam (05c8:0369)
[   12.263572] input: HP HD Webcam as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/input/input19
[   12.263643] usbcore: registered new interface driver uvcvideo
[   12.263645] USB Video Class driver (1.1.1)
[   12.342965] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd
[   12.359268] usb 3-3: New USB device found, idVendor=0424, idProduct=5534
[   12.359272] usb 3-3: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[   12.359275] usb 3-3: Product: USB5534B
[   12.359276] usb 3-3: Manufacturer: SMSC
[   12.360325] hub 3-3:1.0: USB hub found
[   12.360364] hub 3-3:1.0: 4 ports detected
[   12.360527] usb: failed to peer 3-3-port1 and usb2-port1 by location 
(3-3-port1:none) (usb2-port1:usb3-port1)
[   12.360528] usb 3-3-port1: failed to peer to usb2-port1 (-16)
[   12.360587] usb: failed to peer 3-3-port2 and usb2-port1 by location 
(3-3-port2:none) (usb2-port1:usb3-port1)
[   12.360588] usb 3-3-port2: failed to peer to usb2-port1 (-16)
[   12.471044] usb 1-1: new high-speed USB device number 2 using ehci-pci
[   12.595218] input: ST LIS3LV02DL Accelerometer as 
/devices/platform/lis3lv02d/input/input20
[   12.603521] usb 1-1: New USB device found, idVendor=8087, idProduct=8000
[   12.603526] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   12.603814] hub 1-1:1.0: USB hub found
[   12.603901] hub 1-1:1.0: 8 ports detected
[   12.615136] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   12.615323] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input21
[   12.615397] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[   12.615559] ACPI Warning: SystemIO range 
0xef80-0xef9f conflicts with OpRegion 
0xef80-0xef8f (\_SB_.PCI0.SBUS.SMBI) 
(20140424/utaddress-258)
[   12.615565] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   12.623238] snd_hda_intel :00:03.0: irq 69 for MSI/MSI-X
[   12.635281] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card1/input22
[   12.635369] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card1/input23
[   12.636229] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card1/input24
[   12.703349] usb 2-3.2: new full-speed USB device number 5 using xhci_hcd
[   12.723158] psmouse serio3: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e

Bug#773972: please binNMU packages to build with binutils 2.25

[Stephen Kitt]

Hi Matthias and the release team,

On Fri, 26 Dec 2014 14:58:26 +0100, Matthias Klose  wrote:
> please binNMU the following packages to build with binutils (>= 2.25-3).
> 
> ggcov, tulip, lush, binutils-arm-none-eabi, binutils-mingw-w64,
> binutils-z80, cross-binutils, openbios, openhackware.
> 
> I'm unsure about binutils-mingw-w64. Stephen said that this package would
> require a sourceful upload.

Did I? Never mind, I just rebuilt binutils-mingw-w64 as-is in unstable and it
built fine, so a binNMU would be OK.

Regards,

Stephen


pgpCYia_5TADX.pgp
Description: OpenPGP digital signature

Bug#773975: Please add "reload" action to initscript

[Chris Lamb]

Package: minidlna
Version: 1.1.2+dfsg-1.1
Tags: patch
Severity: wishlist

Please add a "reload" action to the initscript - I have a fair amount of
muscle memory and shell aliases that prefer "reload" over, say,
"force-reload". :)

Patch attached that simply adds 'reload' as a synonym of force-reload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/minidlna.init b/debian/minidlna.init
index d6dd63c..7de09d0 100644
--- a/debian/minidlna.init
+++ b/debian/minidlna.init
@@ -146,15 +146,16 @@ case "$1" in
   status)
status_of_proc -p "$PIDFILE" "$DAEMON" "$NAME" && exit 0 || exit $?
;;
-  restart|force-reload)
+  restart|reload|force-reload)
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
  0|1)
-   if [ "$1" = "force-reload" ]; then
+   case "$1" in
+ reload|force-reload)
# Rescan the collection
DAEMON_ARGS="$DAEMON_ARGS -R"
-   fi
+   esac
do_start
case "$?" in
0) log_end_msg 0 ;;
@@ -174,7 +175,7 @@ case "$1" in
 log_end_msg $?
 ;;
   *)
-   echo "Usage: $SCRIPTNAME 
{start|stop|status|restart|force-reload|rotate}" >&2
+   echo "Usage: $SCRIPTNAME 
{start|stop|status|restart|force-reload|reload|rotate}" >&2
exit 3
;;
 esac

Bug#773974: rkhunter: Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: /usr/bin/lwp-request

[areazero]

Package: rkhunter
Version: 1.4.2-0.4
Severity: normal

Dear Maintainer,

the default rkhunter.conf includes the following line:

  SCRIPTWHITELIST=/usr/bin/lwp-request

I don't have libwww-perl installed on serveral systems, so when
rkhunter is invoked, it fails with the following error message:

  Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: 
/usr/bin/lwp-request

I think the default rkhunter.conf shouldn't cause rkhunter to fail when
an optional package - that rkhunter doesn't depend on - is not installed
in the system.

I had to comment out the "SCRIPTWHITELIST=/usr/bin/lwp-request" to get
rkhunter running on the affected systems.

Thanks


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

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

Versions of packages rkhunter depends on:
ii  binutils   2.24.90.20141023-1
ii  debconf [debconf-2.0]  1.5.55
ii  file   1:5.20-2
ii  net-tools  1.60-26+b1
ii  perl   5.20.1-3
ii  ucf3.0030

Versions of packages rkhunter recommends:
ii  iproute 1:3.16.0-2
ii  lsof4.86+dfsg-1
ii  postfix [mail-transport-agent]  2.11.3-1
ii  unhide  20121229-1+b1
ii  wget1.16-1

Versions of packages rkhunter suggests:
ii  heirloom-mailx [mailx]12.5-3.1
pn  libdigest-whirlpool-perl  
pn  liburi-perl   
pn  libwww-perl   
pn  powermgmt-base
pn  tripwire  

-- debconf information:
  rkhunter/cron_db_update:
  rkhunter/cron_daily_run:
  rkhunter/apt_autogen: false


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

Bug#773973: RM: osmosis-plugin-borderextract -- NPOASR; RC-buggy; inactive upstream

[Bas Couwenberg]

Package: src:osmosis-plugin-borderextract
Version: 1.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

osmosis-plugin-borderextract is not compatible with the current
(upstream) osmosis version and has not seen any activity for over two
years. 

The package has an unfixed RC bug (#713177) about the inability to
build. This bug is unfixed for over a year.

Since upstream doesn't develop the software anymore, and no-one in
Debian actively maintains the package, the package should be removed
from the archive.

The package has never been part of a stable release, and was removed
from testing after only five months.

If there are no objections, I'll reassign this issue to ftp.debian.org
for processing by the FTP masters.

Kind Regards,

Bas


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

Bug#770659: WebRTC camera/microphone sharing does not work

[Marco Maria Luciani]

When I try to start a video call on google hangouts:

Version Chromium : 39.0.2171.71-2

Version of debian: 8.0 Debian Testing

The log report this error:

getrlimit(RLIMIT_NOFILE) failed
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.


I'm not a very expert...I hope it can help solve the problem (soon)

Have a nice day

Marco

Bug#283839: closed by Ola Lundqvist (Re: Bug#283839: Seems fixed)

[Cyril Bouthors]

close 283839
thanks

I confirm the issue is not reproducible anymore.


On Tue, Dec 23, 2014 at 9:31 PM, Ola Lundqvist  wrote:

> Hi
>
> Now I do not understand. Do you confirm it is not fixed?
> But the indented code looks good to me.
>
> // Ola
>
> On Tue, Dec 23, 2014 at 4:41 PM, Cyril Bouthors  > wrote:
>
>> I confirm it's not fixed, the indented code look like:
>>
>> if (ini_get('register_globals'))
>>   echo('WARNING: register_globals must be turned off in php.ini.');
>> echo 'something else';
>>
>>
>
>
> --
>  --- Inguza Technology AB --- MSc in Information Technology 
> /  o...@inguza.comAnnebergsslingan 37\
> |  o...@debian.org   654 65 KARLSTAD|
> |  http://inguza.com/Mobile: +46 (0)70-332 1551 |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
>  ---
>
>


-- 
Cyril Bouthors - go-managed.com  -
+33-184-161-617 +1-347-294-7146
https://www.linkedin.com/in/cyrilbouthors

Bug#291951: closed by Ola Lundqvist (Solved by latest upload)

[Cyril Bouthors]

On Tue, Dec 23, 2014 at 9:28 PM, Ola Lundqvist  wrote:

> In that case I can not reproduce the problem. Because when I type this I
> get correct indentation.
> ola@quartz:~$ dpkg -l php-elisp emacs23
>

emacs23 is pretty old

Did you try with emacs-snapshot?


-- 
Cyril Bouthors - go-managed.com  -
+33-184-161-617 +1-347-294-7146
https://www.linkedin.com/in/cyrilbouthors

Bug#768045: Fixed !

[Hadrien DUSSUEL]

Good news ! This bug has been fixed by the nvidia non-free driver update
340.65-1:
http://metadata.ftp-master.debian.org/changelogs//non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_340.65-2_changelog
" - Fixed a regression that caused displays to be detected incorrectly
on some notebook systems.  (Closes: #770798, #765726)"

Obviously, the latest intel driver had incompatibilities with the nvidia
driver.

This bug could be closed.


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

Bug#773972: please binNMU packages to build with binutils 2.25

[Matthias Klose]

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

please binNMU the following packages to build with binutils (>= 2.25-3).

ggcov, tulip, lush, binutils-arm-none-eabi, binutils-mingw-w64, binutils-z80,
cross-binutils, openbios, openhackware.

I'm unsure about binutils-mingw-w64. Stephen said that this package would
require a sourceful upload.


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

Bug#773467: efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)

[Joost van Baal-Ilić]

Hi,

On Thu, Dec 18, 2014 at 07:34:27PM +, Ian Campbell wrote:
> On Thu, 2014-12-18 at 20:20 +0100, Holger Levsen wrote:
> > On Donnerstag, 18. Dezember 2014, Ian Campbell wrote:
> > > But. I don't think any modern kernel supports the efika, it was removed
> > > from the mainline kernel a while ago (summer 2012 it seems [0]) and was
> > > therefore removed from the installer on that basis too[1]
> > 
> > thanks, I was looking for this information (as I saw in the jessie d-i 
> > beta1 
> > release notes that support for efikamx was removed, but I couldn't really 
> > find 
> > out why..) and then I saw this in the linux debian/changelog  from 3.11.5-1 
> > from October 2013:
> > 
> >   * [armhf] Remove mx5, omap and vexpress flavours. These are all supported
> > by the multiplatform flavour.
> > 
> > That sounded promising enough, so I gave upgrading a try...
> 
> Yeah, mx5 general still works (AFAIK), it's just the efika stuff which
> has gone.

Note to self: add information from 
https://www.debian.org/devel/debian-installer/
(e.g. https://www.debian.org/devel/debian-installer/News/2014/20141005 to 
release notes.)
That would fix this bug, and more.

Bye,

Joost


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

Bug#773421: lxc: can't start container

[Hleb Valoshka]

On 12/18/14, Daniel Baumann  wrote:

> do you have cgroupfs mounted?

cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,size=12k)
systemd on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/x86_64-linux-gnu/systemd-shim-cgroup-release-agent,name=systemd)
none on /sys/fs/cgroup/cpu type cgroup
(rw,relatime,cpu,release_agent=/run/cgmanager/agents/cgm-release-agent.cpu)
none on /sys/fs/cgroup/cpuset type cgroup
(rw,relatime,cpuset,release_agent=/run/cgmanager/agents/cgm-release-agent.cpuset,clone_children)
none on /sys/fs/cgroup/blkio type cgroup
(rw,relatime,blkio,release_agent=/run/cgmanager/agents/cgm-release-agent.blkio)


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

Bug#738592: /usr/bin/scanimage: Canon LiDE 30 not working on Jessie (is working on wheezy)

[Jörg Frings-Fürst]

Hello Sébastien,

thank your for your work.

I have applied the upstream commit.

At the moment some builds and tests are running. I think that I can
today upload the package to my sponsor.


CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old (will be revoked after 2014-12-31):
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net






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

Bug#773850: Misc updates

[Adrian Perez de Castro]

I have merged the two pull-requests at GitHub dealing with man page
formatting, updated to the latest CVS sources (almost no changes),
and added the “v8” tag. I hope that helps in getting Signify packaged
neatly in Debian. Feel free to ping me if there is something else I
could do to make that happen.

Cheers,

-- 
 🎄 Adrian



signature.asc
Description: PGP signature

Bug#773852: unblock: zodb/1:3.9.7-5 (pre-approval)

[Arnaud Fontaine]

Hi,

"Adam D. Barratt"  writes:

> Control: tags -1 + confirmed moreinfo
>
> On 2014-12-24 3:25, Arnaud Fontaine wrote:
>> Some time ago I uploaded python-zodb to  fix RC bug #767554 but I forgot
>> to remove some headers files, sorry  about that. Would it be possible to
>> upload  python-zodb with  the  (really  straightforward) diff  attached?
>
> Please go ahead, and remove the "moreinfo" tag once the package has been
> accepted.

Thank you very much. I have just uploaded it and removed the moreinfo tag.

Cheers,
-- 
Arnaud Fontaine


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

Bug#773971: Update: Danish hunspell dictionary version 2.2 - 2014-12-22

[Esben Aaberg]

Package: hunspell-da
Version: 1:3.3.0-4

We have just released version 2.2 of the danish hunspell dictionary, you are 
currently shipping version 1.6. in hunspell-da (1:3.3.0-4)

The new dic- and aff-file can be found in the “zip-file” dict-da-2.2.oxt 
located here:
http://extensions.libreoffice.org/extension-center/stavekontrolden-danish-dictionary

Please update your packet at your convenience.

If you have any questions, or guidelines for future releases please let me know.

Updating to our version 2.2 will also resolve the problems reported in bug 
757781.


Kind regards

Esben Aaberg

Foreningen for Frit Tilgængelige Sprogværktøjer
http://www.stavekontrolden.dk


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

Bug#501566: dash: details of redirection/duplication in manpage are reversed

[Stéphane Aulery]

tags + fixed-upstream
stop


See commit 6adc14a0d4e4a25eb2df8110672c84f393b45acb
   2014-12-25 22:50:58 (GMT)

https://git.kernel.org/cgit/utils/dash/dash.git/commit/?id=6adc14a0d4e4a25eb2df8110672c84f393b45acb

-- 
Stéphane Aulery


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

Bug#763869: [Pkg-sysvinit-devel] Bug#763869: sysvinit-utils: sulogin segfault after `cannot open password database!`

[Petter Reinholdtsen]

[Paul Menzel]
> Dear Debian folks,

Thank you for looking into this.

> Please find the updated patch below, fixing a typo in the commit message
> and removing the note.

Great.  The patch need to be moved to debian/patches/, but otherwise
look good.  I hope someone with access to collab-maint can push a fix.
Not sure if it will make it into Jessie.  It do not seem important
enough to try to push it past the freeze.

-- 
Happy hacking
Petter Reinholdtsen


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

Bug#773970: Monkeyscan fails at launch

[Hugo Roy]

Package: monkeysign
Version: 2.0

When launching monkeyscan, I get a small GTK window reporting an
error with:

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/monkeysign/msg_exception.py", line 
36, in wrapper
return f(*args, **kargs)
  File "/usr/lib/python2.7/site-packages/monkeysign/gtkui.py", line 64, in 
main
self.window = MonkeysignScan()
  File "/usr/lib/python2.7/site-packages/monkeysign/gtkui.py", line 160, in 
__init__
self.create_secret_keys_display()
  File "/usr/lib/python2.7/site-packages/monkeysign/gtkui.py", line 278, in 
create_secret_keys_display
for key in Keyring().get_keys(None, True, False).values():
  File "/usr/lib/python2.7/site-packages/monkeysign/gpg.py", line 385, in 
get_keys
key = OpenPGPkey(keydata)
  File "/usr/lib/python2.7/site-packages/monkeysign/gpg.py", line 656, in 
__init__
self.parse_gpg_list(data)
  File "/usr/lib/python2.7/site-packages/monkeysign/gpg.py", line 698, in 
parse_gpg_list
(null, self.trust, self.length, self.algo, keyid, self.creation, 
self.expiry, serial, trust, uid, sigclass, purpose, smime, wtf, wtf, wtf) = 
record
ValueError: too many values to unpack

I'm on  Arch Linux, Kernel: x86_64 Linux 3.17.6-1-xps13.

I tried both versions at https://aur.archlinux.org/packages/?O=0&K=monkeysign

-- 
Hugo Roy – Free Software Foundation Europe https://fsfe.org/about/roy
 
Please use cryptography for email: see https://emailselfdefense.fsf.org/en/
Merci d’utiliser la cryptographie pour l’email : voir 
https://emailselfdefense.fsf.org/fr/


pgpm_Fl3jQM3g.pgp
Description: PGP signature

Bug#773932: systemd-localed fails unless CONFIG_DEVPTS_MULTIPLE_INSTANCES=y

[Marco d'Itri]

Control: retitle -1 check for CONFIG_DEVPTS_MULTIPLE_INSTANCES=y in preinst

On Dec 25, Jamie Heilman  wrote:

> Unless there's some really good reason that systemd-localed shouldn't
> be usable on a system without namespaces, then I'm gonna say this is a
> bug.
I do not think that we want to support systems without namespaces, since 
we want to encourage adoption of the systemd security-related features 
in the default unit files shipped by packages.

-- 
ciao,
Marco


pgpSHW77t1B8W.pgp
Description: PGP signature

Bug#773758: Add a EXAMPLES section and show some actual basic commands

[積丹尼 Dan Jacobson]

I wouldnt know what to write!


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

Bug#773758: Add a EXAMPLES section and show some actual basic commands

[Arturo Borrero Gonzalez]

On 26 December 2014 at 12:12, 積丹尼 Dan Jacobson  wrote:
> I wouldnt know what to write!

Well, just write what you would like to find.

I would suggest a simple sentence, at the end of the manpage:
 "Refer to the following wiki to know further about how to use
nftables: http://...";

regards.

-- 
Arturo Borrero González


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

Bug#773969: python-setuptools: please output names in top_level.txt with a stable order

[Jérémy Bobbio]

Package: python-setuptools
Version: 5.5.1-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that many Python packages would not build reproducibly because the order
of names in the top_level.txt file would vary from one build to
another [2].

It would be great if these names could be written in a stable order.
With the attached patch, names are sorted before being written.

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: 
https://reproducible.debian.net/userContent/issues/random_order_in_egg_info_top_level_txt_issue.html

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
diff -Nru python-setuptools-5.5.1/debian/changelog python-setuptools-5.5.1/debian/changelog
--- python-setuptools-5.5.1/debian/changelog	2014-08-12 13:52:03.0 +0200
+++ python-setuptools-5.5.1/debian/changelog	2014-12-26 11:33:09.0 +0100
@@ -1,3 +1,10 @@
+python-setuptools (5.5.1-1.0~reproducible1) UNRELEASED; urgency=medium
+
+  * Output names in toplevel.txt with a stable order to make module
+builds reproducible.
+
+ -- Jérémy Bobbio   Fri, 26 Dec 2014 11:32:13 +0100
+
 python-setuptools (5.5.1-1) unstable; urgency=medium
 
   * New upstream version. Closes: #754089.
diff -Nru python-setuptools-5.5.1/debian/patches/series python-setuptools-5.5.1/debian/patches/series
--- python-setuptools-5.5.1/debian/patches/series	2013-12-31 12:31:31.0 +0100
+++ python-setuptools-5.5.1/debian/patches/series	2014-12-26 11:26:53.0 +0100
@@ -1,2 +1,3 @@
 install-layout.diff
 multiarch-extname.diff
+stable-order-for-toplevel-names.diff
diff -Nru python-setuptools-5.5.1/debian/patches/stable-order-for-toplevel-names.diff python-setuptools-5.5.1/debian/patches/stable-order-for-toplevel-names.diff
--- python-setuptools-5.5.1/debian/patches/stable-order-for-toplevel-names.diff	1970-01-01 01:00:00.0 +0100
+++ python-setuptools-5.5.1/debian/patches/stable-order-for-toplevel-names.diff	2014-12-26 11:29:13.0 +0100
@@ -0,0 +1,17 @@
+Description: Outpt top-level names in stable order
+ In order to make the build process of Python module reproducible, names in
+ toplevel.txt must be written in a stable order. Here we go for the simple
+ answer by sorting them.
+Author: Jérémy Bobbio 
+
+--- python-setuptools-5.5.1.orig/setuptools/command/egg_info.py
 python-setuptools-5.5.1/setuptools/command/egg_info.py
+@@ -389,7 +389,7 @@ def write_toplevel_names(cmd, basename,
+ for k in cmd.distribution.iter_distribution_names()
+ ]
+ )
+-cmd.write_file("top-level names", filename, '\n'.join(pkgs) + '\n')
++cmd.write_file("top-level names", filename, '\n'.join(sorted(pkgs)) + '\n')
+ 
+ 
+ def overwrite_arg(cmd, basename, filename):


signature.asc
Description: Digital signature

Bug#766688: gnome-orca: Bug fixed in icedove 34

[Jean-Philippe MENGUAL]

Package: gnome-orca
Followup-For: Bug #766688

Dear Maintainer,

The bug is fixed in Icedove 34 (experimental repo). I will close the bug.


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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 3.16.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
Init: systemd (via /run/systemd/system)

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.42.0-2.2
ii  gir1.2-gtk-3.0 3.14.5-1
ii  gir1.2-pango-1.0   1.36.8-3
ii  gir1.2-wnck-3.03.4.9-3
ii  gsettings-desktop-schemas  3.14.1-1
ii  python33.4.2-2
ii  python3-brlapi 5.2~20141018-2
ii  python3-cairo  1.10.0+dfsg-4+b1
ii  python3-gi 3.14.0-1
ii  python3-louis  2.5.3-3
ii  python3-pyatspi2.14.0+dfsg-1
ii  python3-speechd0.8-7
pn  python3:any
ii  speech-dispatcher  0.8-7

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.25-1
ii  xbrlapi 5.2~20141018-2

gnome-orca 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#773968: feh hangs on invalid bmp images

[Jussi Judin]

Package: feh
Version: 2.12-1
Severity: normal

Feh hangs in an infinite loop when given invalid bmp images in
a mode that should help determining if the image can be displayed (-U
command line argument). I did run feh on a afl[1]-generated image test
sets[2] to figure out if any specific images cause problems for
feh. If you try feh with following command line parameters on the
attached images (after extracting them from a tarball), you should see
timeouts:

$ for image in *.bmp; do echo "$image"; timeout -s KILL 10s feh -U "$image"; 
done
id:000774,src:000207,op:arith8,pos:22,val:-28.bmp
Killed
id:000784,src:000207,op:havoc,rep:32.bmp
Killed
id:000787,src:000207,op:havoc,rep:16,+cov.bmp
Killed
id:000955,src:000787,op:flip2,pos:28.bmp
Killed
id:000972,src:000800,op:flip1,pos:60,+cov.bmp
Killed
id:000984,src:000800,op:havoc,rep:32.bmp
Killed
id:001091,src:000972,op:flip2,pos:18.bmp
Killed
id:001092,src:000972,op:arith8,pos:22,val:-25.bmp
Killed
id:001093,src:000972,op:arith8,pos:22,val:-29.bmp
Killed
id:001097,src:000980,op:arith8,pos:18,val:-3.bmp
Killed
id:001154,src:001098,op:flip1,pos:172.bmp
Killed
id:001155,src:001098,op:flip1,pos:172.bmp
Killed
id:001157,src:001098,op:havoc,rep:4.bmp
Killed
id:001159,src:001098,op:havoc,rep:4.bmp
Killed
id:001263,src:001155,op:flip1,pos:178.bmp
Killed
id:001264,src:001155,op:int32,pos:177,val:+1024,+cov.bmp
Killed

Attached a tarball that includes all BMP images generated by afl that
cause an infinite loop in feh.

[1]: American fuzzy lop - a security-oriented fuzzer:
 http://lcamtuf.coredump.cx/afl/
[2]: Afl-generated, minimized image test sets:
 http://lcamtuf.coredump.cx/afl/demo/

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

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

Versions of packages feh depends on:
ii  libc6 2.19-13
ii  libcurl3  7.38.0-3
ii  libexif12 0.6.21-2
ii  libimlib2 1.4.6-2+b3
ii  libpng12-01.2.50-2+b2
ii  libx11-6  2:1.6.2-3
ii  libxinerama1  2:1.1.3-1+b1

Versions of packages feh recommends:
ii  libjpeg-progs  1:9a-2

feh suggests no packages.

-- no debconf information


afl-hanging-bmp-images.tar.gz
Description: application/gzip

Bug#773967: feh crashes on invalid gif image data

[Jussi Judin]

Package: feh
Version: 2.12-1
Severity: important

Feh crashes with segmentation fault when given an invalid gif image in
a mode that should help determining if the image can be displayed (-U
command line argument). I did run feh on a afl[1]-generated image test
sets[2] to figure out if any specific images cause problems for
feh. If you try feh with following command line parameters on the
attached image, you should see a segmentation fault:

$ feh -U id:000293,src:00,op:havoc,rep:4.gif
Segmentation fault

I don't know if this opens a security issue, but every segmentation
fault has a potential for it.

Here is a gdb backtrace of the segmentation fault:

(gdb) run -U id:000293,src:00,op:havoc,rep:4.gif
Starting program: /usr/bin/feh -U id:000293,src:00,op:havoc,rep:4.gif
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x70023d3c in load () from 
/usr/lib/x86_64-linux-gnu/imlib2/loaders/gif.so
(gdb) bt
#0  0x70023d3c in load () from 
/usr/lib/x86_64-linux-gnu/imlib2/loaders/gif.so
#1  0x76c7188f in ?? () from /usr/lib/x86_64-linux-gnu/libImlib2.so.1
#2  0x76c55d3b in imlib_load_image_with_error_return () from 
/usr/lib/x86_64-linux-gnu/libImlib2.so.1
#3  0x55561930 in ?? ()
#4  0x55567925 in ?? ()
#5  0x555679af in ?? ()
#6  0xafdc in ?? ()
#7  0x768c5b45 in __libc_start_main (main=0xaf00, argc=3, 
argv=0x7fffdfe8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffdfd8)
at libc-start.c:287
#8  0xb035 in ?? ()

[1]: American fuzzy lop - a security-oriented fuzzer:
 http://lcamtuf.coredump.cx/afl/
[2]: Afl-generated, minimized image test sets:
 http://lcamtuf.coredump.cx/afl/demo/

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

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

Versions of packages feh depends on:
ii  libc6 2.19-13
ii  libcurl3  7.38.0-3
ii  libexif12 0.6.21-2
ii  libimlib2 1.4.6-2+b3
ii  libpng12-01.2.50-2+b2
ii  libx11-6  2:1.6.2-3
ii  libxinerama1  2:1.1.3-1+b1

Versions of packages feh recommends:
ii  libjpeg-progs  1:9a-2

feh suggests no packages.

-- no debconf information

Bug#773889: jekyll: fails to start

[Antonio Terceiro]

On Wed, Dec 24, 2014 at 08:29:43PM +, Shawn Paul Landden wrote:
> Package: jekyll
> Version: 2.2.0+dfsg-2
> Severity: important
> 
> Dear Maintainer,
> 
> shawn@www:~/blog$ jekyll serve -w
> Notice: for 10x faster LSI support, please install 
> http://rb-gsl.rubyforge.org/
> Configuration file: /home/shawn/blog/_config.yml
> Source: /home/shawn/blog
>Destination: /home/shawn/blog/_site
>   Generating... 
> done.
> /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
> cannot load such file -- listen (LoadError)

looks like a missing dependency. does installing ruby-listen make it
work?

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Bug#772953: Enable several Kconfigs to support OMAP5432 uEVM devboard

[Chen Baozi]

On Fri, Dec 26, 2014 at 6:43 PM, Chen Baozi  wrote:
> On Tue, Dec 23, 2014 at 7:44 PM, Ian Campbell  wrote:
>> On Tue, 2014-12-23 at 16:27 +0800, Chen Baozi wrote:
>>> I have a glance at the kernel’s installer configs and tried the netboot
>>> without any modification. Some work should be done to make debian-installer
>>> support OMAP5 uEVM (e.g., ethernet driver etc).
>>
>> Right, those should be listed in e.g.
>> debian/installer/armhf/modules/armhf-armmp/nic-modules.
>>
>>> By waiting the kernel building with some initial attempted configs added,
>>> just one question to ask. I looked through the
>>> debian/installer/armhf/modules/armhf-armmp/, but it looks like none of
>>> files is about regulator modules. However, according to my previous
>>> experience, missing regulator driver modules is the main reason that
>>> the old debian kernel doesn’t support OMAP5 uEVM. How does debian-installer
>>> deal with this situation (if it does need extra regulator drivers included?)
>>
>> Long term its a bit of an open question what we do wrt modules such as
>> regulators, clocks, pinctrl etc.
>>
>> So far we have been a bit lucky: either such things are so central to
>> the platform that it is acceptable (at least for now) to just build them
>> into the main kernel binary by making them =y (e.g. CONFIG_I2C_S3C2410
>> which is for the main power controller on arndale) or they are closely
>> associated with some particular device and it makes sense to put them in
>> that udeb (e.g. phy-exynos5250-sata in sata-modules, or phy-sun4i-usb in
>> usb-modules).
>>
>> Eventually I expect that we will end up creating separate udebs for
>> these things, but I'm hoping that we can defer that until at least
>> Stretch to avoid needing to mess around with any more new packages for
>> Jessie.
>>
>> If uEVM has some module which either shouldn't be built in or isn't
>> obviously associated with a particular device let us know what it is and
>> we can have a think about how best to approach it.
>>
>> One thing I've played with, and I'm not sure if this is acceptable or
>> not, is to put core drivers which aren't =y into the kernel-image udeb
>> itself. I'm not really sure if that's a good idea, we don't currently do
>> this for anything AFAIK, but it's perhaps an option.
>
> With the attached patch applied, debian installer (tested with 
> network-console)
> can support OMAP5's ethernet driver and external MicroSD card.
>
> Note that I added related regulator & phy entries to files that mainly writes
> the modules which use them, since there is no file dedicated to those
> modules.
>
> Baozi.
>
> ---
> diff -Nru linux-3.16.7/debian/installer/armhf/modules/armhf-armmp/mmc-modules
> linux-3.16.7-ckt2/debian/installer/armhf/modules/armhf-armmp/mmc-modules
> --- linux-3.16.7/debian/installer/armhf/modules/armhf-armmp/mmc-modules
> 2014-09-21 20:04:21.0 +
> +++ linux-3.16.7-ckt2/debian/installer/armhf/modules/armhf-armmp/mmc-modules
> 2014-12-26 03:16:02.0 +
> @@ -4,3 +4,5 @@
>  omap_hsmmc
>  sunxi-mmc
>  dw_mmc-exynos
> +pbias-regulator
> +palmas-regulator
> diff -Nru linux-3.16.7/debian/installer/armhf/modules/armhf-armmp/usb-modules
> linux-3.16.7-ckt2/debian/installer/armhf/modules/armhf-armmp/usb-modules
> --- linux-3.16.7/debian/installer/armhf/modules/armhf-armmp/usb-modules
> 2014-12-23 08:10:49.0 +
> +++ linux-3.16.7-ckt2/debian/installer/armhf/modules/armhf-armmp/usb-modules
> 2014-12-25 02:56:08.0 +
> @@ -1,8 +1,13 @@
>  #include 
>  phy-sun4i-usb
>  dwc3-exynos
>  ohci-exynos
>  ehci-exynos
>  phy-exynos-usb2
>  ci_hdrc_imx
> +phy-mxs-usb
   ^ Oops, this is introduced by '-ckt2', not by me...

> +dwc3-omap
> +ohci-omap3
> +ehci-omap
> +phy-omap-usb2
> +phy-ti-pipe3


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

Bug#763869: sysvinit-utils: sulogin segfault after `cannot open password database!`

[Paul Menzel]

Control: found -1 2.88dsf-58
Control: merge -1 769743 772427


Dear Debian folks,


Am Dienstag, den 16.12.2014, 23:54 +0100 schrieb Paul Menzel:
> Control: severity -1 important
> Control: tags -1 patch

I found two more bug reports for this issue and merge this report with
those.

[…]

Please find the updated patch below, fixing a typo in the commit message
and removing the note.


Thanks,

Paul

-- 8< -- >8 --

From 57d01d1992ecf78a86167b62ae88c7cb11d5bde5 Mon Sep 17 00:00:00 2001
From: Paul Menzel 
Date: Tue, 16 Dec 2014 22:34:33 +0100
Subject: [PATCH] sulogin.c: Return if password database cannot be opened to 
avoid crash

Currently when the maintenance console should open and the password
database cannot be opened the process `sulogin` crashes with a
segmentation fault [1].

sulogin: cannot open password database!
[3.563041] sulogin[84]: segfault at 8 ip 004018e0 sp 
7fffd88d8330 error 4 in sulogin[40+3000]
Segment violation

The code calls the function `getrootpwent()` to get the root password
entry. The function should return a passwd struct and `NULL` on failure.

The return value is actually checked for `NULL` but it just prints a
message in this case and tries to continue normally, which is of course
not possible as later on the struct members are accessed.

Therefore just return 1 in case `pwd` is `NULL`.

Closes: #763869 (sysvinit-utils: sulogin segfault)

[1] https://bugs.debian.org/763869
---
 debian/changelog | 7 +++
 src/sulogin.c| 1 +
 2 files changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 4511465..9ba1a26 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+sysvinit (2.88dsf-58.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix crash when password database is not available (Closes: 763869)
+
+ -- Paul Menzel   Tue, 16 Dec 2014 23:41:45 
+0100
+
 sysvinit (2.88dsf-58) unstable; urgency=low
 
   * Fix typo in invoke-rc.d breaking upstart installations (Closes:
diff --git a/src/sulogin.c b/src/sulogin.c
index 7537654..df8907d 100644
--- a/src/sulogin.c
+++ b/src/sulogin.c
@@ -584,6 +584,7 @@ int main(int argc, char **argv)
if ((pwd = getrootpwent(opt_e)) == NULL) {
fprintf(stderr, "sulogin: cannot open password database!\n");
sleep(2);
+   return 1;
}
 
/*
-- 
2.1.4


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