Bug#699602: postfixadmin recommends non-existing package postgresql-server, should recommend postgresql instead

[Gaudenz Steinlin]

Hi

Matthias Fritzsche  writes:

> Package: postfixadmin
> Followup-For: Bug #699602
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear Maintainer,
>
> sadly this problem still exists in debian wheezy.

As this is only in a Recommends and not a dependency I don't think this
warrants a stable update. You can just install the postgresql package
yourself if it does not get pulled in by something else. I'm quite sure
it will get pulled in by something else if you install all recommends.

Or am I missing something?

The problem is fixed in the upcoming Debian jessie release.

Gaudenz


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

Bug#769070: dpkg-buildpackage: libraries not found by dpkg-shlibdeps

[Joel Roth]

Package: dpkg-dev
Version: 1.17.21
Severity: normal

Dear Maintainer,

Recently upgraded sid. Ran debuild -b -uc -us on pristine
sources downloaded via "apt-get source".

The build fails due to not finding the libraries that were
compiled, and not finding libc.so.6.

Here is the build output for dbus.

Thank you for your attention.

Joel Roth

---

git:master ~/build/udisks2 $ debuild  -uc -us -b   
dpkg-buildpackage -rfakeroot -D -us -uc -b
dpkg-buildpackage: source package udisks2
dpkg-buildpackage: source version 2.1.3-5
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Michael Biebl 
 dpkg-source --before-build udisks2
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with gir,autoreconf
   dh_testdir
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 debian/rules build
dh build --with gir,autoreconf
   dh_testdir
   dh_autoreconf
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
/usr/share/aclocal/ax_check_enable_debug.m4:46: AX_CHECK_ENABLE_DEBUG is 
expanded from...
/usr/share/aclocal/gnome-common.m4:26: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
/usr/share/aclocal/ax_check_enable_debug.m4:46: AX_CHECK_ENABLE_DEBUG is 
expanded from...
/usr/share/aclocal/gnome-common.m4:26: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
aclocal.m4:68: AX_CHECK_ENABLE_DEBUG is expanded from...
aclocal.m4:598: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
^CYou have new mail in /var/mail/jroth
git:master ~/build/dfree/udisks2 $ debuild  -uc -us -b
 dpkg-buildpackage -rfakeroot -D -us -uc -b
dpkg-buildpackage: source package udisks2
dpkg-buildpackage: source version 2.1.3-5
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Michael Biebl 
 dpkg-source --before-build udisks2
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with gir,autoreconf
   dh_testdir
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 debian/rules build
dh build --with gir,autoreconf
   dh_testdir
   dh_autoreconf
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
/usr/share/aclocal/ax_check_enable_debug.m4:46: AX_CHECK_ENABLE_DEBUG is 
expanded from...
/usr/share/aclocal/gnome-common.m4:26: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
/usr/share/aclocal/ax_check_enable_debug.m4:46: AX_CHECK_ENABLE_DEBUG is 
expanded from...
/usr/share/aclocal/gnome-common.m4:26: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
aclocal.m4:68: AX_CHECK_ENABLE_DEBUG is expanded from...
aclocal.m4:598: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
/usr/share/aclocal/ax_check_enable_debug.m4:46: AX_CHECK_ENABLE_DEBUG is 
expanded from...
/usr/share/aclocal/gnome-common.m4:26: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
/usr/share/aclocal/ax_check_enable_debug.m4:46: AX_CHECK_ENABLE_DEBUG is 
expanded from...
/usr/share/aclocal/gnome-common.m4:26: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
aclocal.m4:68: AX_CHECK_ENABLE_DEBUG is expanded from...
aclocal.m4:598: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
aclocal.m4:68: AX_CHECK_ENABLE_DEBUG is expanded from...
aclocal.m4:598: GNOME_DEBUG_CHECK is expanded from...
configure.ac:37: the top level
configure.ac:37: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG
aclocal.m4:68: AX_CHECK_ENABLE_DEBUG is expanded from...
aclocal.m4:598: GNOME_DEBUG_CHECK is expanded from...

Bug#767892: subtitleeditor: Cannot type or edit subtitles

[Philip Rinn]

Hi,

I uploaded the fixed version to m.d.n:

http://mentors.debian.net/package/subtitleeditor

I'll bother my sponsor now ;)

Best,
Philip


signature.asc
Description: Digital signature

Bug#769068: missing petalogix firmware for microblaze arch

[Michael Tokarev]

Package: qemu-system-misc
Version: 2.1+dfsg-5
Severity: normal
Tags: patch

The package is missing two firmware files for qemu-system-microblaze,
petalogix-ml605.dtb and petalogix-s3adsp1800.dtb.  These files has
been removed in DFSG-fication step from the upstream sources due to
lack of source code for them, but it turns out that these files ARE
the source as upstream ships them.  dtc is used to convert between
dtb (binary) and dts (editable text) forms, and the conversion is
1:1 in this case, there's nothing in the original dts besides the
content dtc produces given a dtb.

The solution is to restore the upstream files, stop removing them
for DFSG, and ship them in qemu-system-misc.  Unfortunately this
requires a new source upload.

Alternative is to ship .dts files in debian/ and compile them during
build time.  Somewhat ugly but should work too.

/mjt


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

Bug#765936: qemu-system-common: please preserve setuid bit on /usr/lib/qemu/qemu-bridge-helper

[Michael Tokarev]

Control: severity 74 wishlist
Control: forcemerge 74 -1
Control: retitle 74 bridge network type does not work for non-root

19.10.2014 16:34, Michael Tokarev wrote:
> On 10/19/2014 03:33 PM, Adam Borowski wrote:
>> Package: qemu-system-common
>> Version: 2.1+dfsg-5+b1
>> Severity: wishlist
>>
>> Hi!
>> In order to have non-crippled networking (ie, better than the user mode
>> stack), one needs to either use tap (via qemu-bridge-helper) or a far more
>> complex setup using vlan.  The helper requires the setuid bit to work, yet
>> is shipped without it.  I understand the rationale, yet in the current way
>> the package works, the setuid bit disappears after every qemu upgrade,
>> making networking "mysteriously" stop working.
>>
>> Thus, could you please preserve this bit of configuration in some way?
> 
> This configuration is unsupported, until proper security model is implemented
> upstream.

Actually this is the same theme as #74, merging the two.

Thanks,

/mjt


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

Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

[Michael Tokarev]

27.09.2014 18:10, Michael Tokarev wrote:
> Control: tag -1 moreinfo unreproducible
> 
> 27.09.2014 16:33, Michal Suchanek wrote:
>> Package: qemu-user-binfmt
>> Version: 2.1+dfsg-4
>> Severity: normal
>>
>> Hello,
>>
>> I tried installing qemu-user-binfmt in the hope I will be able to run 
>> foreign architecture binaries.
>>
>> This has absolutely no results. THe package is empty and foreign binaries do 
>> not run.
> 
> As stated in the package description, the package is empty and the only
> reason for it to exist is to run scripts at install and remove times to
> register binfmt support.  This is the reason why it depends on qemu-user
> (actual implementation) and binfmt-support (registration).
> 
> Please be more specific. Which binaries you tried to run but failed?
> What error message did you get?  With the info you provided it is
> impossible to handle your bugreport, especially since I know this
> package works on my systems.
> 
> Do you realize that in order to run regular foreign binary, you also
> need to install all (foreign) libraries required by that binary.  With
> plain qemu-user and without additional foreig libraries it is possible
> to run only statically linked foreign binaries.
> 
> On the other hand you can create a whole foreign chroot with its own
> libraries and directory structure, and chroot into it using qemu as
> a helper/emulator -- but for this to work, now it is qemu who needs
> (now native) libraries inside the chroot, or you should use statically
> linked qemu.
> 
>> Interestingly, on machines where this works this plackage is not present.
>>
>> Is this package supposed to do anything?
> 
> See above.
> 
>> If not what is the preferred way to run foreign binaries?
> 
> I don't understand this question.  There's no True Way for anything.
> Depending on your needs, you may use qemu-user-binfmt or qemu-user-static,
> there may be other alternatives.

Hello  Michal.  A friendly ping?  Do you have any additional information
for this bugreport?  I can't do anything with it without your input...

Thank you!

/mjt


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

Bug#653396: qemu-kvm / libvirt* : Passthrough of TechnoTrend S2-6400 failed

[Michael Tokarev]

On 28.07.2012 01:08, Kein Kommentar wrote:
[ http://bugs.debian.org/653396 ]

Hello again.  Rehashing old bugs.  Did you try using your card with
a more recent version of qemu?  In later versions upstream introduced
a completely new mechanism of using pci devices in guest, named vfio.
Does it work now?

Since I don't have the device in question, or any other devide of this
kind, I can't verify.

I very much hope this bugreport can be closed now... ;)

Thanks,

/mjt


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

Bug#685353: qemu-kvm 1.1.1 hangs using 100% CPU when using ES1370 emulation

[Michael Tokarev]

[ http://bugs.debian.org/685353 ]

05.09.2012 17:48, Mike Gerber wrote:
[]
> Unfortunately I can't currently as this is going into daily use now with the
> working configuration and I don't really have a different machine at hand to
> reproduce this. The problem is that it takes up to two days to hit this bug...
> 
> Michael: Maybe leave this bug open for others to find? For me, it's closed as
> a. I found a working configuration and b. I don't have the resources to triage
> the bug any further, unfortunately.

(rehashing old bugrepots...)

Hello Mike, Malc, others.  So, has anything changed since qemu-kvm v.1.1 in
this context of 44-vs-48 KHz audio frequency?  Mike, did you try more recent
version of qemu (2.1 currently)?  Malc, did you do anything with this in the
code between 1.1 and 2.1 versions, or do you know any changes which may affect
this in the mentioned "version-frame"?

Thanks,

/mjt


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

Bug#601757: [Pkg-sysvinit-devel] Bug#601757: Please mount cgroup automatically

[Petter Reinholdtsen]

[Ritesh Raj Sarraf]
> The bug is more than 4 years old. And no maintainer wants to bring
> it to closure. There's no comment even whether it is something
> correct or not.

I believe cgroup was discussed in http://bugs.debian.org/572733 >
already.  Is there something new since that bug report?

-- 
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#601757: [Pkg-sysvinit-devel] Bug#601757: Please mount cgroup automatically

[Ritesh Raj Sarraf]

Control: severity -1 wishlist
Control: forcemerge 572733 -1


On 11/11/2014 12:54 PM, Petter Reinholdtsen wrote:
> [Ritesh Raj Sarraf]
>> The bug is more than 4 years old. And no maintainer wants to bring
>> it to closure. There's no comment even whether it is something
>> correct or not.
> 
> I believe cgroup was discussed in http://bugs.debian.org/572733 >
> already.  Is there something new since that bug report?
> 

Thanks. I'm merging it to the older one. The bug request is the same, to
enable cgroup moutpoints.

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



signature.asc
Description: OpenPGP digital signature

Bug#646847: dash.1 - Confusion between two pages c[h]sh

[Herbert Xu]

On Mon, Nov 10, 2014 at 04:02:41PM +0100, Harald van Dijk wrote:
> 
> Even if csh is intentionally in the "See also" section despite not
> being referenced anywhere else, is it also intentional that chsh is
> not in that section despite the earlier reference? Would a patch
> that leaves csh but also adds chsh be more appropriate, or do you
> prefer to leave it as it is now?

The see also section is not meant to be an exhaustive list of
all commands referred to in the manual.  It's meant to be a list
of manual entries related to dash.  So no I'm not going to add
chsh there just because there was an earlier reference.

Cheers,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


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

Bug#769066: lintian: Consider processing files in disk order

[Niels Thykier]

Package: lintian
Version: 2.5.30
Severity: wishlist

Colin Watson suggested that it might be prudent to access files in
disk order to increase performance. Link to man-db code implementing
this below:

http://git.savannah.gnu.org/cgit/man-db.git/tree/lib/orderfiles.c


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

Bug#765431: open-iscsi: umountiscsi.sh script does not properly check while traverse sysfs structure

[Ritesh Raj Sarraf]

On 11/11/2014 01:44 AM, dmitry wrote:
>
> I am sorry, but could you please be answered:
>
> If code above present in umountiscsi.sh init script where can I
> found correct (not tampered) version? As far as I see from contents of
> package umountiscsi.sh script does not contain this code. I look at
> packages from any different repository (ftp.de.debian.org,
> ftp.fi.debian.org, ftp.ru.debian.org) and could not found it.
>

https://packages.qa.debian.org/o/open-iscsi.html


>>
>>
>> And the patch you provided is wrong. Because those block devices we are
>> looping for are not directories.
>
> Are you speaking about /dev/ contents? Am I wrong, that code:
> "
> for BLOCK_FILE in $SESSION_DIR/target*/*\:*/block/*; do
> 
> " -  loop for filesystem with directories?

Yes. Here we only loop through device files.


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



signature.asc
Description: OpenPGP digital signature

Bug#601757: Please mount cgroup automatically

[Ritesh Raj Sarraf]

On 11/11/2014 03:54 AM, John Paul Adrian Glaubitz wrote:
> Hello Ritesh!
> 
> May I ask why you set the severity to "grave"? As far as I know,
> Debian Jessie is going to be released with systemd as the default
> init for all release architectures to which kfreebsd-* does not
> belong to.
> 

The bug is more than 4 years old. And no maintainer wants to bring it to
closure. There's no comment even whether it is something correct or not.


> I don't think that this bug is going to be fixed any time soon
> if the sysvinit maintainers didn't bother enough to fix it
> the past three years.

It is unclear whether what the maintainers want to do with this bug
report. With the maintainers mum, all we can do is assume.



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



signature.asc
Description: OpenPGP digital signature

Bug#356309: dpkg-cross and qemu

[Michael Tokarev]

Control: tag -1 - patch + wontfix

04.11.2014 09:27, Johannes Schauer wrote:
> Hi,
> 
> Quoting Michael Tokarev (2014-11-03 18:16:39)
>> Anyone know if current interp-prefix is actually used by someone in Debian?
>> It is set to /etc/qemu-binfmt/%M but this directory does not exist.  I'm
>> asking because if we're to change the prefix to the one used by dpkg-cross,
>> we'll have to migrate existing /etc/qemu-binfmt/ directory to a new location,
>> which will be really troublesome.
> 
> maybe this is a long shot but the solution I created to a similar problem with
> qemu-user might be able to help you as well. Please see #632192 about it.
> 
> Essentially, I wanted to have qemu-user be run automatically on foreign arch
> binaries using the linux binfmt mechanism. This requires that one is able to
> set the prefix via other means than the -L option because one would not call
> qemu-user directly anymore. Thus, I wrote a patch to accept an environment
> variable containing the prefix path. Upstream accepted that patch in commit
> fc9c5412 in 2011.

Aha.  That makes good sense.

> So now you can just export QEMU_LD_PREFIX and set it to whatever you want like
> for example to /usr/powerpc-linux-gnu as you expressed in #356309.

Yeah.  So it looks like this #356309 can be closed now.   Tagging as `wontfix'
for now, will close if no further comments will follow.

Thank you very much for the information!

/mjt


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

Bug#769032: [pkg-horde] Bug#769032: php-horde-imp: Missing sym link plugins/pasteattachment/plugin.js to imp/js/ckeditor/pasteattachment.js

[Mathieu Parent]

2014-11-10 22:01 GMT+01:00 root :
> Package: php-horde-imp
> Version: 6.2.2-3
> Severity: important
>
> Dear Maintainer,

Hello Andy,

> Horde Imp ckeditor gets a 404 err when it tries to fetch 
> /imp/plugins/pasteattachment/plugin.js
> The file is located at /imp/js/ckeditor/pasteattachment.js .

Actually, the /usr/share/horde/imp/js/ckeditor/pasteattachment.js path
is what upstream expects (according to package.xml).

The problem seems to be on the Horde_Editor side. This is #769031.

Let's take the discussion there.

Regards
-- 
Mathieu


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

Bug#769065: unblock: fatrace/0.9-1

[Martin Pitt]

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

I recently noticed (through the autopkgtest regression [1]) that
fatrace's power-usage-report got broken with the latest powertop 2.6.
So I made a new upstream release 0.9 which adjusts the powertop output
format parsing accordingly. It's just a two line diff (complete
debdiff attached, there no build system noise etc.). Both the
automatic and a manual test are happy again now [2].

Thanks for considering,

Martin

unblock fatrace/0.9-1


[1] 
https://jenkins.qa.ubuntu.com/job/vivid-adt-fatrace/2/ARCH=i386,label=adt/console
[2] 
https://jenkins.qa.ubuntu.com/job/vivid-adt-fatrace/3/ARCH=i386,label=adt/console
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru fatrace-0.8/debian/changelog fatrace-0.9/debian/changelog
--- fatrace-0.8/debian/changelog2014-09-23 16:07:44.0 +0200
+++ fatrace-0.9/debian/changelog2014-11-07 09:19:03.0 +0100
@@ -1,3 +1,10 @@
+fatrace (0.9-1) unstable; urgency=medium
+
+  * New upstream release:
+- power-usage-report: Adjust parsing to also work for powertop 2.6.
+
+ -- Martin Pitt   Fri, 07 Nov 2014 09:18:56 +0100
+
 fatrace (0.8-1) unstable; urgency=medium
 
   * New upstream bug fix release: Fix the "Value too large for defined data
diff -Nru fatrace-0.8/NEWS fatrace-0.9/NEWS
--- fatrace-0.8/NEWS2014-09-23 15:56:19.0 +0200
+++ fatrace-0.9/NEWS2014-11-07 09:17:24.0 +0100
@@ -1,3 +1,7 @@
+0.9 (2014-11-07)
+
+ - power-usage-report: Adjust parsing to also work for powertop 2.6.
+
 0.8 (2014-09-23)
 
  - The previous O_LARGEFILE change to fix "Value too large for defined data
diff -Nru fatrace-0.8/power-usage-report fatrace-0.9/power-usage-report
--- fatrace-0.8/power-usage-report  2014-09-23 15:56:19.0 +0200
+++ fatrace-0.9/power-usage-report  2014-11-07 09:17:24.0 +0100
@@ -166,7 +166,7 @@
 
 for (search_header, print_header) in blocks:
 # skip until search_header
-while i < len(lines) and not lines[i].lower().startswith('**' + 
search_header):
+while i < len(lines) and not search_header in lines[i].lower():
 i += 1
 i += 1  # skip header
 # skip empty lines
@@ -174,7 +174,7 @@
 i += 1
 
 print('== %s ==' % print_header)
-while i < len(lines) and lines[i]:
+while i < len(lines) and lines[i] and not lines[i].startswith('_'):
 print(lines[i])
 i += 1
 print('')


signature.asc
Description: Digital signature

Bug#769064: unblock: g-wrap/1.9.14-2.1

[أحمد المحمودي]

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

Please unblock package g-wrap

* Build against guile-2.0 (Closes: #761210, also refer to guile-1.8-rm 
  transition)
* Automatically use aclocal/autoconf/automake version (Closes: #713203)
* Add delete_aclocal_flags.patch to avoid define loop in Makefile.am


Please find the debdiff attached.

unblock g-wrap/1.9.14-2.1

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

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

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7
diff -Nru g-wrap-1.9.14/debian/changelog g-wrap-1.9.14/debian/changelog
--- g-wrap-1.9.14/debian/changelog  2012-12-06 14:28:47.0 +0200
+++ g-wrap-1.9.14/debian/changelog  2014-10-29 13:54:56.0 +0200
@@ -1,3 +1,25 @@
+g-wrap (1.9.14-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Upload to unstable (Closes: #761210).
+  * merge changes with 1.9.14-1.1 and 1.9.14-2. 
+  * debian/rules
+- automatically use aclocal/autoconf/automake version (Closes: #713203)
+- include autoreconf.mk
+  * debian/control
+- add "Build-Depends: dh-autoreconf" to use above autoreconf.mk
+  * debian/patches
+- add delete_aclocal_flags.patch to avoid define loop in Makefile.am
+
+ -- Hideki Yamane   Thu, 06 Mar 2014 21:16:50 +0900
+
+g-wrap (1.9.14-2) experimental; urgency=low
+
+  * Build against guile-2.0:
+- Build-Depends, Depends and 'configure' invocation adapted.
+
+ -- Andreas Rottmann   Tue, 05 Jun 2012 22:44:57 +0200
+
 g-wrap (1.9.14-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru g-wrap-1.9.14/debian/control g-wrap-1.9.14/debian/control
--- g-wrap-1.9.14/debian/control2012-12-06 14:28:47.0 +0200
+++ g-wrap-1.9.14/debian/control2014-10-29 13:54:56.0 +0200
@@ -6,12 +6,12 @@
 Vcs-Git: git://git.debian.org/git/collab-maint/g-wrap.git
 Vcs-Browser: http://git.debian.org/?p=collab-maint/g-wrap.git
 Standards-Version: 3.9.3
-Build-Depends: debhelper (>> 8), cdbs, texinfo, automake, autoconf,
- guile-1.8-dev (>= 1.8.3+1), guile-library (>= 0.1.1), libglib2.0-dev, 
libffi-dev
+Build-Depends: debhelper (>> 8), cdbs, texinfo, automake, autoconf, 
dh-autoreconf,
+ guile-2.0-dev (>= 2.0.5), guile-library (>= 0.1.1), libglib2.0-dev, libffi-dev
 
 Package: g-wrap
 Architecture: all
-Depends: guile-1.8, guile-library (>= 0.1.1), ${misc:Depends}, 
+Depends: guile-2.0, guile-library (>= 0.1.1), ${misc:Depends},
  dpkg (>= 1.15.4) | install-info
 Recommends: indent, libgwrap-runtime-dev (>= ${source:Version})
 Conflicts: libgwrapguile-dev, guile-g-wrap (<< 1.9.9-1)
@@ -26,7 +26,7 @@
 Package: libgwrap-runtime-dev
 Section: libdevel
 Architecture: any
-Depends: libgwrap-runtime2 (= ${binary:Version}), guile-1.8-dev, libffi-dev, 
libc6-dev,  ${misc:Depends}
+Depends: libgwrap-runtime2 (= ${binary:Version}), guile-2.0-dev, libffi-dev, 
libc6-dev,  ${misc:Depends}
 Conflicts: libgwrapguile-dev, libgwrap-runtime0-dev
 Replaces: libgwrapguile1 (<< 1.3.4-13)
 Description: scripting interface generator for C - development files
diff -Nru g-wrap-1.9.14/debian/gbp.conf g-wrap-1.9.14/debian/gbp.conf
--- g-wrap-1.9.14/debian/gbp.conf   2012-12-06 14:28:47.0 +0200
+++ g-wrap-1.9.14/debian/gbp.conf   2014-10-29 13:54:56.0 +0200
@@ -3,4 +3,3 @@
 
 [git-buildpackage]
 sign-tags = True
-
diff -Nru g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 
g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch
--- g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 1970-01-01 
02:00:00.0 +0200
+++ g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 2014-10-29 
13:54:56.0 +0200
@@ -0,0 +1,14 @@
+Description: 
+Author: Hideki Yamane 
+Forwarded: no
+Last-Update: 2013-10-22
+
+--- g-wrap-1.9.14.orig/Makefile.am
 g-wrap-1.9.14/Makefile.am
+@@ -16,5 +16,5 @@ EXTRA_DIST = g-wrap.scm \
+$(wildcard $(srcdir)/m4/*.m4) \
+$(wildcard $(srcdir)/m4/*.m4-in)
+ 
+-ACLOCAL_AMFLAGS = -I m4 @ACLOCAL_FLAGS@
++ACLOCAL_AMFLAGS = -I m4 
+ 
diff -Nru g-wrap-1.9.14/debian/patches/series 
g-wrap-1.9.14/debian/patches/series
--- g-wrap-1.9.14/debian/patches/series 2012-12-06 14:28:47.0 +0200
+++ g-wrap-1.9.14/debian/patches/series 2014-10-29 13:54:56.0 +0200
@@ -1 +1,2 @@
 0001-Use-GUILE-instead-of-hardcoding-guile-binary-name.patch
+delete_aclocal_flags.patch
diff -Nru g-wrap-1.9.14/debian/README.source g-wrap-1.9.14/debian/README.source
--- g-wrap-1.9.14/debian/README.source  2012-12-06 14:28:47.0 +0200
+++ g-wrap-1.9.14/deb

Bug#760377: confirm apache 1 and gpl-1+ situation

[Florian Weimer]

* Paul Gevers:

> [2]
> http://anonscm.debian.org/cgit/collab-maint/xmlrpc-c.git/tree/lib/util/getoptx.h?h=debian-sid

You should investigate if you can use the getopt from glibc, which is
released under the LGPL.

> [3]
> http://anonscm.debian.org/cgit/collab-maint/xmlrpc-c.git/tree/tools/turbocharger/mod_gzip.c?h=debian-sid

I don't think this file is even compiled, so its license does not
matter.


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

Bug#769063: ITP: apertium-apy -- Apertium APY service

[Kartik Mistry]

Package: wnpp
Severity: wishlist
Owner: Kartik Mistry 

* Package name: apertium-apy
  Version : 0.1
  Upstream Author : Universidad de Alicante / Prompsit Language Engineering S.L.
* URL : http://apertium.org/
* License : GPL-2+
  Programming Lang: Python
  Description : Apertium APY service

This package contains Apertium APY which is simple Apertium
API written in Python 3 meant as a drop-in replacement for
ScaleMT.

 - why is this package useful/relevant? is it a dependency for
   another package? do you use it? if there are other packages
   providing similar functionality, how does it compare?

   A: Apertium is along with standalone installation, largely useful
   as a "service". Apertium-APY is optimized to be use in service and
   quite useful while building service for Machine Translation.

 - how do you plan to maintain it? inside a packaging team
   (check list at https://wiki.debian.org/Teams)? are you
   looking for co-maintainers? do you need a sponsor?

   A: Debian-Science team.

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com


signature.asc
Description: Digital signature

Bug#769062: ITP: puppet-module-puppetlabs-vcsrepo -- Puppet module to deploy content from a version control system

[Jordan Metzmeier]

Package: wnpp
Severity: wishlist
Owner: Jordan Metzmeier 

* Package name: puppet-module-puppetlabs-vcsrepo
  Version : 1.2.0
  Upstream Author : Bruce Williams 
* URL : https://forge.puppetlabs.com/puppetlabs/vcsrepo
* License : GPL-2+
  Programming Lang: Ruby
  Description : Puppet module to deploy content from a version control 
system

Puppet lets you centrally manage every important aspect of your system using a 
cross-platform
specification language that manages all the separate elements normally 
aggregated in different
files, like users, cron jobs, and hosts, along with obviously discrete elements 
like packages,
services, and files.

This module allows you to deploy content from a version control system. The 
following version
control systems are supported:

 * Git
 * Bazaar
 * CVS
 * Mercurial
 * Perforce
 * Subversion


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

Bug#768911: [pkg-cli-apps-team] Bug#768911: Bug#768911: Bug#768911: gnome-do: desktop freezes when gnome-do is launched

[Christopher James Halse Rogers]

Ok. I can now reproduce this too, but *only* if Do is set to show on 
startup (which I didn't have).


I wonder if this is related to the GMutex unpleasantness recently. I'll 
investigate.



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

Bug#768769: plastimatch: FTBFS in jessie: Tests failures

[Andreas Tille]

Hi Gregory,

On Mon, Nov 10, 2014 at 12:01:48PM -0800, Gregory Sharp wrote:
> This is a bug in upstream, where the regression test
> is missing a dependency.

I'm not sure what this really means but if it is a missing dependency do
you want to express that we can fix this by just another Build-Depends
and if yes which one?  Are you able to commit a patch to SVN?

Kind regards

Andreas.

-- 
http://fam-tille.de


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

Bug#425859: user-setup: Cannot preseed an installation with a locked (!) root password and no user account

[Christian PERRIER]

Quoting Sebastian Unger (sebunge...@gmail.com):
> Hi,
> 
> So has anybody ever found a solution to this? I'm still in the same boat 7
> years later with 1.48 of user-setup on ubuntu 14.04. The work-around using
> !! kind of works but means that the emergency recovery mode in Ubuntu
> mistakenly thinks that root has a password set and prompts for one which
> makes it rather useless in an emergency.

Hello Sebastian,

Thanks for bringing back this issue.

I suspect that actually nobody felt like implementing this (which would
indeed require another pressedable variable) mostly because
(speculation here) we consider this to be a corner case that can be
solved by alternative methods.

And then the issue fell under the radar of everybody (the installer
team desperately needs people to help triaging bugs)

The documentation is indeed unclear more than wrong: it lets you think
that you can preseed the locked root password *and* not have a regular
user created,; which is not the case. Your (interesting) workaround
could however be documented in the installation manual, though.

> 
> Cheers,
> Seb
> 
> On Thu, 24 May 2007 16:29:05 +0100 Matthew Johnson <
> mjj29-deb...@srcf.ucam.org> wrote:
> > Package: user-setup
> > Severity: minor
> >
> >
> > I have been trying to preseed config files for a set of servers we have
> > just bought. Since I do not want either the root password (even hashed)
> > in the config file or any user-interaction on these (headless) machines,
> > I would like to disable both the root password and not create a user.
> > Access is enabled by late_command which installs an ssh public key to
> > /root/.ssh/authorized_keys.
> >
> > The documentation (at
> > http://www.debian.org/releases/stable/i386/apbs04.html.en) says:
> >
> >"The passwd/root-password-crypted and passwd/user-password-crypted
> >variables can also be preseeded with ?!? as their value. In that
> >case, the corresponding account is disabled. This may be convenient
> >for the root account, provided of course that an alternative method
> >is setup to allow administrative activities or root login (for
> >instance by using SSH key authentication or sudo)"
> >
> > However, a preseed file containing:
> >d-i passwd/make-user boolean false
> >d-i passwd/root-password-crypted string !
> > or:
> >d-i passwd/make-user boolean false
> >d-i passwd/root-login boolean false
> >
> > still prompts for either the root password or creation of a user. This
> > would appear to be deliberate because user-setup-ask contains:
> >
> >   db_get passwd/root-login
> >   if [ "$RET" = false ]; then
> >  # always make non-root user; this user will be able
> >  # to sudo to root
> >  db_set passwd/make-user true
> >
> > and
> >
> >  db_get passwd/root-password-crypted || true
> >  if ! test "$RET" || [ "x$RET" = "x!" ]; then
> > # No preseed of the root password hash
> > # we will prompt the user
> >
> > This, however, is not what the documentation claims or what would be
> > useful in this case.
> >
> > I have currently solved the problem by using the following preseed:
> >
> >d-i passwd/make-user boolean false
> >d-i passwd/root-password-crypted string !!
> >
> > but it would better if the actual implementation matched the
> > documentation and if the situation I would like were supported.
> >
> > As an additional wishlist item; user-setup could do the preseeding of
> > ssh public keys for users or root itself and therefore explicitly
> > support this case. No patch yet; maybe if I have time.
> >
> > Matt

-- 




signature.asc
Description: Digital signature

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

[Andreas Tille]

On Mon, Nov 10, 2014 at 06:05:36PM -0500, Yaroslav Halchenko wrote:
> 
> On Mon, 10 Nov 2014, Andreas Tille wrote:
> 
> > On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote:
> > > amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a
> > > bug fix so we could demand unblock for this one
> 
> > I'll take the bet that this will fail.  I personally would not try to
> > stress test the patience of the release team. ;-)
> 
> well -- the changes are indeed miniscule (if I got it right) and just a
> bugfix anyways I guess -- I bet RT can swallow this one

To my experience over several releases it does not matter at all how
small the upstream bugfixes might be.  Freeze means only RC bugs will be
fixed.  Your only chance to get this through is if you file an RC bug
which is fixed by the diff between 0.8.4 to 0.8.6 - but I doubt that
this is rectified.  The release team is following the rules very
strictly so I think you will loose your bet.

BTW, I would concentrate on the question why the tests that passed
before are failing now.

Kind regards

Andreas.

-- 
http://fam-tille.de


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

Bug#768842: dpkg: please document the dependency:arch syntax for architecture qualifiers

[Johannes Schauer]

Hi!

Quoting Guillem Jover (2014-11-11 01:14:29)
> I've done the change now, just changing the order of the architecture
> qualifier values list.
[...]
> I've also updated the Multi-Arch field description. New patch attached.

I think this version is good now. Thanks!

cheers, josch


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

Bug#768930: unblock: pynag and syslog-nagios-bridge

[Clint Byrum]

Excerpts from Daniel Pocock's message of 2014-11-10 12:19:19 -0800:
> 
> On 10/11/14 20:56, Niels Thykier wrote:
> > Control: tags -1 moreinfo
> > 
> > On Mon, 10 Nov 2014 10:31:03 +0100 Daniel Pocock  wrote:
> >> Package: release.debian.org
> >>
> >>
> >>
> >> syslog-nagios-bridge requires pynag 0.9.1+, older versions have a bug in
> >> check result file generation:
> >>
> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768928
> >>
> >>
> >> I added a constraint in syslog-nagios-bridge well before the freeze so
> >> it would not propagate to testing until pynag 0.9.1 was uploaded:
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378
> >>
> >> Note that the pynag upload in unstable is also cleaning out minified
> >> jquery and other things that make the package more compliant with Debian
> >> policy
> >>
> >>
> >> [...]
> > 
> > Hi,
> > 
> > I am afraid I will have to reject this request in its current form.
> > 
> > The changes to pynag is beyond what can be reasonably reviewed and
> > indeed it is not a targeted fix for #768928.  The changes to
> > syslog-nagios-bridge are reasonable and I could accept them, but I
> > understand it is of no use without pynag as well.
> > 
> > Can you please provide a targeted fix for pynag?
> 
> This (just a few lines) could be dropped into
> debian/patches/checkresult_fix.patch
> 
> https://github.com/pynag/pynag/commit/3aad1176bca4b2f39c2c851396d30647efbf2bed
> 
> Clint, would you be happy to upload 0.8.9 with that or would you like me
> to NMU perhaps?
> 
> Or is there any reason why the whole 0.9.1 should be considered for jessie?

I think we should unblock 0.9.1.


signature.asc
Description: PGP signature

Bug#761182: xserver-xorg-video-nouveau: NV94: screen black after resume from S3

[Dennis Linnell]

I have been suffering similar symptoms. The problem occurs in all the 
3.16 kernels through 3.16.5-1, but not in any of the 3.14 kernels, most 
recently 3.14.15-2.


As suggested above, I tried the latest kernel, 
linux-image-3.17-1-686-pae (3.17-1~exp1) from experimental. That fixed 
the problem for me.


This appears to be the relevant upstream bug report:

https://www.libreoffice.org/bugzilla/show_bug.cgi?id=83550

See the patch. It would be nice to see this problem fixed in the jessie 
3.16 kernel.


Many thanks,
Dennis


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

Bug#769061: ITP: vim-easymotion -- simple and efficient motions in vim

[Jason Pleau]

Package: wnpp
Severity: wishlist
Owner: Jason Pleau 

* Package name: vim-easymotion
  Version: 2.0
  Upstream Author: Kim Silkebækken , haya14busa
* URL: https://github.com/Lokaltog/vim-easymotion
* License: Creative Commons Attribution Share-Alike (CC-BY-SA) v3.0
  Programming Lang: VimL
  Description: simple and efficient motions in vim

(shameless copy paste from upstream's url)

EasyMotion provides a much simpler way to use some motions in vim. It
takes the  out of w or f{char} by highlighting
all possible choices and allowing you to press one key to jump directly
to the target.

When one of the available motions is triggered, all visible text
preceding or following the cursor is faded, and motion targets are
highlighted.


I intend to maintain this package in the pkg-vim team.

-- 
Jason Pleau


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

Bug#769060: unblock: m-tx/0.60d.ctan20131224-1

[Norbert Preining]

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

Please unblock package m-tx

the m-tx lua script had a one-line bug that was fixed shortly
after last years release, which I didn't realise. It is about
a missing "then" in a long elseif 

Full debdiff attached, nothing spectacular, only code change in all
of it is this (for m-tx.lua script):
@@ -104,7 +104,7 @@
 dvi = ""; ps2pdf = ""
   elseif this_arg == "-d" then
 dvi = "dvipdfm"; ps2pdf = ""
-  elseif this_arg == "-c"
+  elseif this_arg == "-c" then
 pmx = "pmxchords"
   elseif this_arg == "-F" then
 narg = narg+1

Thanks

Norbert

unblock m-tx/0.60d.ctan20131224-1

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

Kernel: Linux 3.18.0-rc4+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru m-tx-0.60d.ctan20131214/debian/changelog m-tx-0.60d.ctan20131224/debian/changelog
--- m-tx-0.60d.ctan20131214/debian/changelog	2014-10-21 09:25:54.0 +0900
+++ m-tx-0.60d.ctan20131224/debian/changelog	2014-10-31 10:23:10.0 +0900
@@ -1,3 +1,10 @@
+m-tx (0.60d.ctan20131224-1) unstable; urgency=medium
+
+  * Imported Upstream version 0.60d.ctan20131224
+- fixed m-tx.lua script (Closes: #767434)
+
+ -- Norbert Preining   Fri, 31 Oct 2014 10:22:26 +0900
+
 m-tx (0.60d.ctan20131214-2) unstable; urgency=medium
 
   * fix mismatch of prototypes of predelete (Closes: #749782)
diff -Nru m-tx-0.60d.ctan20131214/doc/generic/m-tx/README m-tx-0.60d.ctan20131224/doc/generic/m-tx/README
--- m-tx-0.60d.ctan20131214/doc/generic/m-tx/README	2013-12-12 09:52:36.0 +0900
+++ m-tx-0.60d.ctan20131224/doc/generic/m-tx/README	2013-12-24 14:19:30.0 +0900
@@ -1,4 +1,4 @@
-This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-12).
+This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-24).
 
 M-Tx is a preprocessor for PMX that facilitates inputting lyrics. It
 builds the PMX input file based on a language very similar to PMX. M-Tx
diff -Nru m-tx-0.60d.ctan20131214/README m-tx-0.60d.ctan20131224/README
--- m-tx-0.60d.ctan20131214/README	2013-12-12 14:52:36.0 +0900
+++ m-tx-0.60d.ctan20131224/README	2013-12-24 20:19:30.0 +0900
@@ -1,4 +1,4 @@
-This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-12).
+This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-24).
 
 M-Tx is a preprocessor for PMX that facilitates inputting lyrics. It
 builds the PMX input file based on a language very similar to PMX. M-Tx
diff -Nru m-tx-0.60d.ctan20131214/scripts/m-tx/m-tx.lua m-tx-0.60d.ctan20131224/scripts/m-tx/m-tx.lua
--- m-tx-0.60d.ctan20131214/scripts/m-tx/m-tx.lua	2013-12-11 17:09:50.0 +0900
+++ m-tx-0.60d.ctan20131224/scripts/m-tx/m-tx.lua	2013-12-24 14:19:02.0 +0900
@@ -104,7 +104,7 @@
 dvi = ""; ps2pdf = ""
   elseif this_arg == "-d" then
 dvi = "dvipdfm"; ps2pdf = ""
-  elseif this_arg == "-c"
+  elseif this_arg == "-c" then
 pmx = "pmxchords"
   elseif this_arg == "-F" then
 narg = narg+1

Bug#767445: (no subject)

[Daniele Tricoli]

Hello,
I have already sent a RFS for requests 2.4.3-3 with a fix for this. I already 
tried python-docker 0.5.3-1 after building it inside a pbuilder chroot: using 
requests 2.4.3-3, python-docker works.

See this thread for details:
https://lists.debian.org/debian-python/2014/11/msg1.html

Specifically:
https://lists.debian.org/debian-python/2014/11/msg00019.html

For example, python-botocore 0.69.0-1 uses both requests and urllib3
(upstream is using requests.packages.urllib3 as import point) and with 
requests 2.4.3-3 it will not need a patch like the one provided by Kuba.

Of couse many thanks to Jakub Warmuz for investigating this! :)

I already opened a RC bug against requests, it will be closed with the upload 
of requests 2.4.3-3 (already asked a RFS to my usual sponsor) and then I will 
ask for an unblok since I want this fixed in Jessie.

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org


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

Bug#767826: python3-django-assets: fails to install: SyntaxError: Missing parentheses in call to 'print'

[Jason Pleau]

Hello,

I have noticed this error when installing this package.

Attached is a trivial patch that fixes this bug

Sent upstream: https://github.com/miracle2k/django-assets/pull/47

-- 
Jason Pleau
Description: python3 compat for pytest_plugin.py
 Trivial change to make the print statement compatible with python3 in the
 django_assets/pytest_plugin.py
 .
 Closes #767826
Author: Jason Pleau 
Forwarded: https://github.com/miracle2k/django-assets/pull/47
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/django_assets/pytest_plugin.py
+++ b/django_assets/pytest_plugin.py
@@ -3,5 +3,5 @@
 
 @pytest.fixture(autouse=True)
 def set_django_assets_env():
-print "Set django assets environment"
+print("Set django assets environment")
 django_assets.env.get_env() # initialise django-assets settings

Bug#768686: maxima ftbfs due to gcl dependency

[Michael Gilbert]

Hi Camm,

It looks like you're gcl uploads didn't make it to testing in time for
the freeze, but maxima did.

Maxima in testing now has an unsatisfiable build dependency on gcl in unstable.

I did a rebuild of maxima 5.34.1-2 with gcl 2.6.11-3 from testing,
which seemed to work just fine, but I'm not familiar enough with why
there is so often a need for updating the gcl build-dep in the
package.

Is it ok to downgrade the dependency to >= 2.6.11-3?

Best wishes,
Mike


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

Bug#766114: [pkg-fso-maint] Bug#766114: Aw: Re: Bug#766114: Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf

[Sebastian Reichel]

Hi,

Sorry for the long time to answer, but I had no time to dig into
this.

On Thu, Nov 06, 2014 at 10:40:39PM +0100, hikaru.deb...@web.de wrote:
> > Hmm, it's a strange thing. If I recompile fso-deviced eveything works as 
> > expected.
> 
> But you can reproduce the problem with the packages as they are in
> Debian right now?
> I just rebuild the Jessie package (armhf) and still get the same
> startup error (as I expected).

I can verify, that the binary is broken (and thus the init script
fails, too).

> > It seems, the generated .c files from vala-sources are broken.
> 
> Unfortunately this is above my skills. Please let me know if I can be of any
> further assistance in solving this!

starting the binary without the init script tells us:

$ sudo fsodeviced
*** stack smashing detected ***: fsodeviced terminated
[...]

Which means, that there is a stack based buffer overflow. I could
trace the problem to the Kernel.InputDevice constructor method,
which is kernel_input_device_construct() in the plugin.c

I guess Rico does not use the "-fstack-protector-strong" gcc
parameter, so in his build setup the binary does not verify if the
stack has been corrupted.

Stuff I tried so far to find the stack problem:

* comparing the generated C code from current vala with the
  pregenerated C code from FSO:
  problem has not been introduced by newer vala!
* reading through the C code to find the stack problem:
  could not find it!
* runing binary without -fstack-protector-strong in valgrind:
  nothing found in the Kernel.InputDevice constructor
* building without -O2:
  works
* build using clang-3.5 without changing CFLAGS/LDFLAGS
  still broken
* build using clang-3.5 + address sanitizer:
  problem gone :( [it would have traced the error]

So I think I will enable "-fno-stack-protector" in the package
for now.

-- Sebastian


signature.asc
Description: Digital signature

Bug#691128: Patch Applied to My Fork

[Jacob Adams]

Upstream is no longer maintaining this package.

I have forked it:
https://github.com/Tookmund/swapspace

Your patch has been applied to my fork and eventually will make it back
to Debian once I fix a few other bugs.

Thank you for your help.

Jacob Adams
GPG Key: AF6B 1C26 E2D0 A988 432B  94F4 24C0 2B85 B59F E5A9



signature.asc
Description: OpenPGP digital signature

Bug#769059: base: eeepc 1015PN: alsa sound not working

[Samuel Bernardo]

Package: base
Severity: important

Dear Maintainer,

Alsa can't detect my audio device in eeepc 1015PN.

http://www.alsa-project.org/main/index.php/Matrix:Module-hda-intel
I followed what was described in that page and the best I could achieve was 
starting nvidia sound card when manually loading following modules:
modprobe snd-hda-intel ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss
but sound continues not to work because that seems to be related with GPU and 
not with Intel Corporation NM10/ICH7 Family High Definition Audio Controller.
The Intel Audio controller can't be loaded with alsa.

initial state after boot is the following:
http://www.alsa-project.org/db/?f=609eff36d7b903493b97914d4b8e1ed12ea454b9

I try to start alsa with following command
$ alsactl init
Found hardware: "HDA-Intel" "Nvidia GPU 0b HDMI/DP" 
"HDA:10de000b,10de0101,00100200" "0x1043" "0x8470"
Hardware is initialized using a generic method

$ speaker-test -t wav -c 2 -l 2

speaker-test 1.0.28

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Playback open error: -2,No such file or directory

After this the result of detected interfaces is the following with only NVIDIA 
card detected and that is not expected:
http://www.alsa-project.org/db/?f=684d72d045fa39666db5e4d6dc620304373a8b0e

I'm trying to get audio module snd-hda-intel detecting my card but it gives the 
following message as shown in dmesg:
[   26.988349] oss_hdaudio: HDA codec 0x10ec0269 not known yet
[   26.997841] oss_hdaudio: HDA codec 0x10ec0269 not known yet

So I trying to found a solution to start Intel Corporation NM10/ICH7 Family 
High Definition Audio Controller.
Until now only NVIDIA Corporation High Definition Audio Controller seems to be 
starting.



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

Kernel: Linux 3.16-3-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


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

Bug#768937: [Pkg-zsh-devel] Bug#768937: zsh: [patch] not binNMU-safe due to --link-doc between arch-dep and arch-indep

[Axel Beckert]

Control: tag -1 - patch pending

Hi Simon,

I'm not yet sure what's the culprit, but after applying your patch
(without the changelog) to the current HEAD of our packging git repo,
the installation of zsh-common always aborts as follows:

Preparing to unpack zsh-common_5.0.7-4_all.deb ...
Unpacking zsh-common (5.0.7-4) over (5.0.7-3+0~2014001757.238~1.gbp353e05) 
...
dpkg: error processing archive zsh-common_5.0.7-4_all.deb (--install):
 unable to open '/usr/share/doc/zsh-common/ChangeLog-3.0.gz.dpkg-new': No such 
file or directory
Processing triggers for menu (2.1.47) ...
Processing triggers for man-db (2.7.0.2-3) ...
Errors were encountered while processing:
 zsh-common_5.0.7-4_all.deb

I currently suspect that dpkg-maintscript-helper may be confused
because because /usr/share/doc/zsh is now a directory inside zsh _and_
zsh-common. Will have a close look tomorrow evening. So in case you
have an idea, feel free to reply.

(I also tried to bump zsh-common's Replaces header to zsh <= 5.0.7-3,
but this didn't seem to make a change.)

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


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

Bug#769058: cups: "/usr/lib/cups/filter/foomatic-rip failed" after last CUPS update

[Tom Maneiro]

Package: cups
Version: 1.7.5-7
Severity: important

After the last CUPS packages update (1.7.5-7) on all of my Jessie boxes at
home, I've been unable to print to my Konica-Minolta magicolor 1600W, which is
plugged to a old box running Wheezy. My last successful print jobs were under
1.7.5-5, a week ago. Due to resource constraints on the print server box, using
the remote print queue isn't an option (the print driver -foo2zjs- is very
resource-hungry and the print server only has 128MB RAM, hence the queues must
be local for the clients so they can crunch the print data before sending it to
the server, and ultimately to the printer). Printing still works from Windows
hosts, so there is nothing to blame in the server

After raising the debug level on CUPS, and taking a look at error_log, I've
noticed something... odd:

D [10/Nov/2014:21:04:23 -04-30] [Job 155] IPP/2.0 Create-Job #4
D [10/Nov/2014:21:04:23 -04-30] [Job 155]  operation-attributes-tag 
D [10/Nov/2014:21:04:23 -04-30] [Job 155] attributes-charset charset utf-8
D [10/Nov/2014:21:04:23 -04-30] [Job 155] attributes-natural-language
naturalLanguage es-ve
D [10/Nov/2014:21:04:23 -04-30] [Job 155] printer-uri uri
ipp://saki.tomman.net.ve:631/printers/CL3005W
D [10/Nov/2014:21:04:23 -04-30] [Job 155] requesting-user-name
nameWithoutLanguage root
D [10/Nov/2014:21:04:23 -04-30] [Job 155] job-name nameWithoutLanguage Test
Page
D [10/Nov/2014:21:04:23 -04-30] [Job 155]  job-attributes-tag 
D [10/Nov/2014:21:04:23 -04-30] [Job 155] job-originating-host-name
nameWithoutLanguage localhost
D [10/Nov/2014:21:04:23 -04-30] [Job 155] job-uuid uri
urn:uuid:47ecf607-9d3d-3091-7581-ca1a88cbd249
D [10/Nov/2014:21:04:23 -04-30] [Job 155]  end-of-attributes-tag 
D [10/Nov/2014:21:04:23 -04-30] [Job 155] Create-Job: successful-ok
(successful-ok)
D [10/Nov/2014:21:04:23 -04-30] [Job 155] Print job accepted - job ID 329.
D [10/Nov/2014:21:04:23 -04-30] [Job 155] Sending file 1 using chunking...
D [10/Nov/2014:21:04:23 -04-30] [Job 155] kid4 exited with status 0
D [10/Nov/2014:21:04:23 -04-30] [Job 155] kid3 finished
D [10/Nov/2014:21:04:23 -04-30] [Job 155] kid3 exited with status 0
D [10/Nov/2014:21:04:23 -04-30] [Job 155] pdf-to-ps exited with status 0
D [10/Nov/2014:21:04:23 -04-30] [Job 155] Closing foomatic-rip.
d [10/Nov/2014:21:04:23 -04-30] cupsdFinishProcess(pid=27918,
name=0x7fffe8b037f0, namelen=1024, job_id=0x7fffe8b037ec(155)) =
"/usr/lib/cups/filter/foomatic-rip"
D [10/Nov/2014:21:04:23 -04-30] [Job 155] PID 27918 (/usr/lib/cups/filter
/foomatic-rip) exited with no errors.
I [10/Nov/2014:21:04:23 -04-30] [Job 155] /usr/lib/cups/filter/foomatic-rip
failed
D [10/Nov/2014:21:04:23 -04-30] [Job 155] update_reasons(attr=1(none),
s="(null)")
d [10/Nov/2014:21:04:23 -04-30] [Job 155] op=' ', new_reasons=0,
state_reasons=0
D [10/Nov/2014:21:04:23 -04-30] [Job 155] Get-Printer-Attributes: successful-ok
(successful-ok)
D [10/Nov/2014:21:04:23 -04-30] [Job 155] (monitor) Get-Job-Attributes:
successful-ok (successful-ok)
D [10/Nov/2014:21:04:23 -04-30] [Job 155] (monitor) job-state=pending-held


So... the filter (foomatic-rip) successfully exits, yet it fails!? This makes
no sense.



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

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

Versions of packages cups depends on:
ii  cups-client1.7.5-7
ii  cups-common1.7.5-7
ii  cups-core-drivers  1.7.5-7
ii  cups-daemon1.7.5-7
it  cups-filters   1.0.61-2
ii  cups-ppdc  1.7.5-7
ii  cups-server-common 1.7.5-7
ii  debconf [debconf-2.0]  1.5.53
ii  ghostscript9.06~dfsg-1.1+b1
ii  libavahi-client3   0.6.31-4+b1
ii  libavahi-common3   0.6.31-4+b1
ii  libc-bin   2.19-12
ii  libc6  2.19-12
ii  libcups2   1.7.5-7
ii  libcupscgi11.7.5-7
ii  libcupsimage2  1.7.5-7
ii  libcupsmime1   1.7.5-7
ii  libcupsppdc1   1.7.5-7
ii  libgcc11:4.9.1-19
ii  libstdc++6 4.9.1-19
ii  libusb-1.0-0   2:1.0.19-1
ii  lsb-base   4.1+Debian13+nmu1
ii  poppler-utils  0.26.5-2
ii  procps 2:3.3.9-8

Versions of packages cups recommends:
it  avahi-daemon 0.6.31-4+b1
ii  colord   1.2.1-1+b1
it  cups-filters [ghostscript-cups]  1.0.61-2
ii  printer-driver-gutenprint5.2.10-3

Versions of packages cups suggests:
ii  cups-bsd   1.7.5-7
pn  cups-pdf   
ii  foomatic-db-compressed-ppds [foomatic-db]  20141016-1
it  hplip  3.14.6-1+b2
ii  printer-driver-hpcups  3.14.6-1+b2
i

Bug#768841: libgnutls-deb0-28: SIGABRT when loading certificates

[Marc Dequènes (Duck)]

Coin,

Quoting Andreas Metzler :


Could you check whether upgrading to 3.3.10 (just uploaded to
experimental) fixes the issues you reported, too?


You're right, this fixed the problem for both minbif and ircd-ratbox.


PS: Looking at
 this seems
to match "a bug which has a major effect on the usability of a
package, without rendering it completely unusable to everyone" which
would be "important", not "grave".


I disagree. When a bug breaks other packages, this is clearly  
unsuitable for release and ought to be RC. It can't be critical as it  
does not break "unrelated softwares […]". It can't be serious as it is  
not a matter of policy. For a library, which only use is to provide  
functions to other programs, to cause crashes to many rdeps is in my  
opinion being "unusable or mostly so".



Well, thanks for your help. I think the next step is ensuring this fix  
enters Jessie. 3.3.10 does not seem to add more than a few fixes  
(which at first glance seem important). It could be reasonable to  
discuss an unblock with the RT.


Regards.

--
Marc Dequènes (Duck)



pgpEl1cgNZe95.pgp
Description: PGP Digital Signature

Bug#768485: dpkg: format string vulnerability

[Guillem Jover]

Hi!

On Mon, 2014-11-10 at 01:00:56 +1100, Joshua Rogers wrote:
> On 08/11/14 06:47, Guillem Jover wrote:
> > Nicely spotted! And thanks for the report, I've fixed it now locally
> > and it will be included in the next 1.17.x release. I'll be preparing
> > fixed packages for stable too. 

> Could you provide a patch for this bug via email?

Sure, attached the patch that I'll be using in principle for the
stable update (being coordinated with the security team separately).

BTW Jakub, did you find this in parallel, or simply relied the bug
filed in Launchpad? Just to give proper attribution, and if the latter
appreciated as much otherwise I'd not have noticed.

Regards,
Guillem
From 1e8665c7c01a5db54d057de89b18152af605d8b9 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Fri, 7 Nov 2014 20:49:26 +0100
Subject: [PATCH] libdpkg: Escape package and architecture on control file
 parsing warning

The package name and architecture are injected into a string that is
used as a format string. Because these are user controlled, we need to
format-escape them so that they become inert.

Regression introduced in commit 0b8652b226a7601dfd71471797d15168a7337242.

Fixes: CVE-2014-8625
Closes: #768485
---
 lib/dpkg/parsehelp.c | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/lib/dpkg/parsehelp.c b/lib/dpkg/parsehelp.c
index d9a574e..9e1d624 100644
--- a/lib/dpkg/parsehelp.c
+++ b/lib/dpkg/parsehelp.c
@@ -44,11 +44,14 @@ parse_error_msg(struct parsedb_state *ps, const char *fmt)
 
   str_escape_fmt(filename, ps->filename, sizeof(filename));
 
-  if (ps->pkg && ps->pkg->set->name)
+  if (ps->pkg && ps->pkg->set->name) {
+char pkgname[256];
+
+str_escape_fmt(pkgname, pkgbin_name(ps->pkg, ps->pkgbin, pnaw_nonambig),
+   sizeof(pkgname));
 sprintf(msg, _("parsing file '%.255s' near line %d package '%.255s':\n"
-   " %.255s"), filename, ps->lno,
-   pkgbin_name(ps->pkg, ps->pkgbin, pnaw_nonambig), fmt);
-  else
+   " %.255s"), filename, ps->lno, pkgname, fmt);
+  } else
 sprintf(msg, _("parsing file '%.255s' near line %d:\n"
" %.255s"), filename, ps->lno, fmt);
 
-- 
2.1.3

Bug#769053: uwsgi-plugin-python3: libapache2-mod-wsgi-py3: should not provide httpd-wsgi

[Jonas Smedegaard]

tags 769053 pending
thanks

Quoting Brian May (2014-11-11 01:40:59)
> Package: uwsgi-plugin-python3
> Version: 2.0.7-1
> Severity: important
> uwsgi-plugin-python3 provides httpd-wsgi, however httpd-wsgi is for the
> Python 2 WSGI API.
> As the Python 3 WSGI API cannot be used with Python 2 applications, this
> will break Python 2 applications that depend on httpd-wsgi.
> A bug report has been filled against debian-policy for a httpd-wsgi3
> virtual package for Python 3 WSGI, see #768117.

Thanks!  Applied to Vcs.

 - Jonas

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

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


signature.asc
Description: signature

Bug#768979: Thanks and geoipupdate for free GeoLite users

[Faidon Liambotis]

On 11/11/14 02:42, Gregory Oschwald wrote:

Thanks so much for packaging all of these!


You're very welcome :) FWIW, I've also submitted an ITP for the Python 
bindings, #768984. I don't have any plans for the rest of the language 
binaries for now. All three packages are essentially done (modulo your 
recommendations below) and in Debian's git:

http://anonscm.debian.org/cgit/collab-maint/geoipupdate.git
http://anonscm.debian.org/cgit/collab-maint/libmaxminddb.git
http://anonscm.debian.org/cgit/collab-maint/python-maxminddb.git


Although it is poorly advertised, geoipupdate can actually be used with
the free GeoLite databases, e.g., with the GeoIP.conf file:

UserId 99
LicenseKey 
ProductIds 506 533

I think it would be reasonable to use this as a default in a general
package. The GeoLite2 databases should work too with the product IDs of
"GeoLite2-City" and "GeoLite2-Country", but there appears to be an issue
with the deployment of them for geoipupdate currently.

Hopefully in the future we will clean up that fake UserId/LicenseKey,
but even as it stands, this is preferable for most people to using a
homemade script for downloading as it only downloads if the file has
changed, verifies the MD5s before deploy, and safely moves the verified
files over the old files.


Oh wow, that is indeed great (and indeed poorly advertised :). I wasn't 
aware of this at all. We could replace geoip-database-contrib with this 
entirely. Two questions:
1) Where can I find the product IDs for the rest of the GeoLite 
databases? Ideally we'd list all of them, at least commented-out.
2) Is there an ETA for fixing the GeoLite2 products on the server? I 
could wait for this before I make an upload.


Thanks for the amazingly quick feedback :)

Regards,
Faidon


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

Bug#769056: unblock: rkhunter/1.4.2-0.3

[Francois Marier]

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

Please unblock package rkhunter

This release fixes a single important bug (#767731) introduced in
the latest upstream release, with a very simple fix:

-  if [ `${IPCS_CMD} -u 2>/dev/null | awk -F' ' '/segments allocated/ {print 
$3}'` -ne 0 ]; then
+  if [ `LANG=C ${IPCS_CMD} -u 2>/dev/null | awk -F' ' '/segments allocated/ 
{print $3}'` -ne 0 ]; then

(the addition of "LANG=C" before grepping in the command's output)

Attached is a full debdiff.

unblock rkhunter/1.4.2-0.3
diff -Nru rkhunter-1.4.2/debian/changelog rkhunter-1.4.2/debian/changelog
--- rkhunter-1.4.2/debian/changelog	2014-10-19 20:14:41.0 +1300
+++ rkhunter-1.4.2/debian/changelog	2014-11-07 14:35:51.0 +1300
@@ -1,3 +1,10 @@
+rkhunter (1.4.2-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix IPCS command on non-English locales (closes: #767731)
+
+ -- Francois Marier   Fri, 07 Nov 2014 14:34:19 +1300
+
 rkhunter (1.4.2-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff
--- rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff	1970-01-01 12:00:00.0 +1200
+++ rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff	2014-11-07 14:35:51.0 +1300
@@ -0,0 +1,18 @@
+Description: Force english locale for ipcs call
+Author: Francois Marier 
+Forwarded: https://sourceforge.net/p/rkhunter/patches/42/
+Last-Update: 2014-11-07
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767731
+Bug: https://sourceforge.net/p/rkhunter/bugs/130/
+
+--- a/files/rkhunter
 b/files/rkhunter
+@@ -13964,7 +13964,7 @@ ${FOUND_PROCS}"
+ touch "${IPCS_TMPFILE}"
+ FOUND=0; echo $FOUND > "${IPCS_TMPFILE}"
+ 
+-if [ `${IPCS_CMD} -u 2>/dev/null | awk -F' ' '/segments allocated/ {print $3}'` -ne 0 ]; then
++if [ `LANG=C ${IPCS_CMD} -u 2>/dev/null | awk -F' ' '/segments allocated/ {print $3}'` -ne 0 ]; then
+ ${IPCS_CMD} -m | grep "^0x" | while read RKH_SHM_KEY RKH_SHM_SHMID RKH_SHM_OWNER RKH_SHM_PERMS RKH_SHM_BYTES RKH_SHM_NATTACH RKH_SHM_STATUS; do
+ if [ $RKH_SHM_PERMS -eq 666 -a $RKH_SHM_BYTES -ge 100 ]; then
+ FOUND=1; echo $FOUND > "${IPCS_TMPFILE}"
diff -Nru rkhunter-1.4.2/debian/patches/series rkhunter-1.4.2/debian/patches/series
--- rkhunter-1.4.2/debian/patches/series	2014-10-19 20:14:41.0 +1300
+++ rkhunter-1.4.2/debian/patches/series	2014-11-07 14:35:51.0 +1300
@@ -1,3 +1,4 @@
 05_custom_conffile.diff
 10_fix-man.diff
 15_remove-empty-dir.diff
+20_fix-ipcs-language.diff

Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'

[Miriam Ruiz]

Well, it's not really a "why not" decision :) , I mean, it's somehow a
kind of commitment statement. I mean, while debian/changelog
essentially talks about the past (who did what), imo Maintaner and
Uploaders talk about the future of the packahe, more or less saying:
"hey, if there's something to fix in here, contact me and I will try
to take care of it".

Miry

2014-11-10 20:56 GMT+01:00 Peter Pentchev :
> On Mon, Nov 10, 2014 at 08:07:21PM +0100, Miriam Ruiz wrote:
>> Thanks a lot, I'll have a look at it and commit it.Do you want to be
>> included in Uploaders, as the patch seems to say? If you do, you're
>> essentially declaring that you're willing to take care of that
>> package, essentially :)
>
> Sure, why not? :)  I could refresh its packaging after the freeze.
>
> Thanks for looking at the patch!
>
> G'luck,
> Peter
>
> --
> Peter Pentchev  r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
> PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
> Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


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

Bug#721689: (no subject)

[Dominik George]

Package: iceweasel
Version: 31.2.0esr-3
Followup-For: Bug #721689
Control: severity -1 serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The issue is still there and is a privacy issue. Apart from that, the
loaded scripts replace huge parts of the Iceweasel branding with the
original Firefox logo, or even fancy JavaScript games, or whatever
Mozilla decide to impose on their users.

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

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

Versions of packages iceweasel depends on:
ii  debianutils   4.4
ii  fontconfig2.11.0-6.1
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-11
ii  libcairo2 1.12.16-5
ii  libdbus-1-3   1.8.8-2
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-1.1
ii  libffi6   3.1-2
ii  libfontconfig12.11.0-6.1
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.2-1
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.0-2
ii  libgtk2.0-0   2.24.25-1
ii  libhunspell-1.3-0 1.3.3-2
ii  libnspr4  2:4.10.7-1
ii  libnss3   2:3.17.1-1
ii  libpango-1.0-01.36.8-2
ii  libsqlite3-0  3.8.6-1
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-1
ii  libvpx1   1.3.0-2.1
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxrender1   1:0.9.8-1
ii  libxt61:1.1.4-1
ii  procps2:3.3.9-8
ii  zlib1g1:1.2.8.dfsg-2

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  fonts-mathjax  
ii  fonts-oflb-asana-math  000.907-6
ii  fonts-stix [otf-stix]  1.1.1-1
ii  libcanberra0   0.30-2.1
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.12.1+dfsg-10
pn  mozplugger 

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUYWCAAAoJELeaPBagxPKWASgQAJGtt3aYe0bnOGhVdgKeS/bq
kPVh4oyFrp0oZqXmuqyrRJ0iukDVaw2wVp27eqn4/ycinJZK0P9+fm9DkIkxMLpP
16FKGT3X5WF5sYNEvjrG9btqLEplOK8ka4wqI1CWfEq3ohx7rwrycwvp5+Ypogug
/ncG9AiN7HSwMnuKfsr5g3pQJcHwolfTwWIx+PxTB47WoA+yzg4twnFP1YXExs3+
WIzDxgEa7L9mQxMN6deXmWIDxF96vNL1gRAFKPR+nlW2HNIl6gG8QXcUPkjDc5dX
S8he5MATnaTROOFspbIvfgFuOOIYc2EymWNeplOmaBBv6dpqvBPUiWAMryrYsbQL
d0Jxd/K6UyqDGF9V5w3Xo+24oD8jfhAAQaHVQtcZdO16vNJ2fZ2gr6gGn2ZXtbLT
v87f+MJk2JDIWVK53nwgVzOz7BYmH/6yqM7bKQRj8DtfQZ6lsDQ+jlY2g0JfaCQt
lBNlX9fs7JLDSyG8wzq8LJ5nFuJ/TCmVxeIlgZ1MX8MMi9unYhvNt3902I/uVw7n
ZMA8m8RC29lgWOpqkKshjXUUgRxP5c5/kB5I3Da7p3pLiiFNcEYlD4cRYUkP+fjU
eyng2UkWik0MV7p/8qcT1ai8XaoW1px5qt71xS/YQU857i1toXTrhGvFTTv3DFqX
AVbyi9CrRxe+eo8+nHJy
=gz6m
-END PGP SIGNATURE-


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

Bug#768979: Thanks and geoipupdate for free GeoLite users

[Gregory Oschwald]

On Mon, Nov 10, 2014 at 4:58 PM, Faidon Liambotis 
wrote:

>
> Oh wow, that is indeed great (and indeed poorly advertised :). I wasn't
> aware of this at all. We could replace geoip-database-contrib with this
> entirely. Two questions:
> 1) Where can I find the product IDs for the rest of the GeoLite databases?
> Ideally we'd list all of them, at least commented-out.
>

506 -  GeoLite Legacy Country
517 - GeoLite ASN
533 - GeoLite Legacy City
GeoLite2-Country - GeoLite2 Country
GeoLite2-City - GeoLite2 City

It doesn't appear that we have any of the legacy IPv6 databases available
through geoipupdate. I'll create an internal issue for that but work on the
legacy products is generally a lower priority now that GeoIP2 is out.

2) Is there an ETA for fixing the GeoLite2 products on the server? I could
> wait for this before I make an upload.
>
>
If the current build goes smoothly, this should be available tomorrow.

Greg

Bug#760303: squid 3.3.8-1.2 segfaults during initscript start/restart

[Dmitry Katsubo]

> On Fri, 12 Sep 2014 08:01:25 -0500 Dale Schroeder wrote:
>> I don't understand how a log rotation can fail, yet succeed.
> 
> The way the log rotation integrates with external log management tools
> is that Squid leaves the external tool to do file renaming or moving,
> and just re-opens the filedescriptors it has for the log files.
> 
> So the logs have been changed successfully by logrotated. But the squid
> binary is asserting at some point in the followup process.
> 
> The assertion seems to be caused by memory management for some globals
> allocated for the ICAP services.

Hello,

I have noticed the same error during log rotation. I have "icap_enable
off" (default) and no squidclamav (almost default config) but I have

  ecap_service gzip_service respmod_precache ...
  loadable_modules /usr/lib/squid3/ecap_adapter_gzip.so
  adaptation_access gzip_service allow GZIP_HTTP_STATUS
  ^ correlates with bug#4057 mentioned above

Now when I run squid from command line (with another instance running in
background), it segfauls:

> # gdb /usr/sbin/squid3
> Reading symbols from /usr/sbin/squid3...Reading symbols from 
> /usr/lib/debug//usr/sbin/squid3...done.
> (gdb) run
> Starting program: /usr/sbin/squid3
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
> "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
> 
> Program received signal SIGABRT, Aborted.
> 0xb7fde424 in __kernel_vsyscall ()
> (gdb) bt
> #0  0xb7fde424 in __kernel_vsyscall ()
> #1  0xb78f9307 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #2  0xb78fa9c3 in __GI_abort () at abort.c:89
> #3  0x801470a4 in xassert (msg=0x80438250 "size == 
> StrPoolsAttrs[i].obj_size", file=0x8043f7c4 "mem.cc", line=282) at 
> debug.cc:566
> #4  0x801f0fc7 in memFreeString (size=721, buf=0x806c87e0) at mem.cc:282
> #5  0x80233e1a in String::clean (this=0x806ccd0c) at String.cc:159
> #6  0x80399033 in Adaptation::AccessRule::~AccessRule (this=0x806ccd08, 
> __in_chrg=) at AccessRule.cc:16
> #7  0x80399f4a in Adaptation::Config::FreeAccess () at Config.cc:281
> #8  0x8039ad64 in Adaptation::Config::freeService (this=0x806b34c0 
> ) at Config.cc:148
> #9  0x8039adb8 in Adaptation::Config::~Config (this=0x806b34c0 
> , __in_chrg=) at Config.cc:307
> #10 0x803b5d04 in Adaptation::Icap::Config::~Config (this=0x806b34c0 
> , __in_chrg=) at Config.cc:54
> #11 0xb78fc121 in __run_exit_handlers (status=status@entry=0, 
> listp=0xb7a723c4 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true)
> at exit.c:82
> #12 0xb78fc17d in __GI_exit (status=0) at exit.c:104
> #13 0x801ee9cf in watch_child (argv=) at main.cc:1687
> #14 SquidMain (argc=1, argv=0xba94) at main.cc:1452
> #15 0x800d5c79 in SquidMainSafe (argv=0xba94, argc=1) at main.cc:1260
> #16 main (argc=1, argv=0xba94) at main.cc:1252

In /var/log/squid3/cache.log:

> 2014/11/11 01:30:36| Squid is already running!  Process ID 22357
> 2014/11/11 01:30:36| assertion failed: mem.cc:282: "size == 
> StrPoolsAttrs[i].obj_size"

I am running squid 3.4.8-2 / jessie

-- 
With best regards,
Dmitry


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

Bug#769055: reportbug: AttributeError: 'NoneType' object has no attribute 'startswith'

[Brian May]

Package: reportbug
Version: 6.6.0
Severity: important

Not only did it crash, but there doesn't seem to be any sign of the temp
file any more, so I had to retype the bug report :-(


Report will be sent to "Debian Bug Tracking System" 
Submit this report on libapache2-mod-wsgi-py3 (e to edit)
[Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? y
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2211, in 
main()
  File "/usr/bin/reportbug", line 1081, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2203, in user_interface
self.options.envelopefrom)
  File "/usr/lib/python2.7/dist-packages/reportbug/submit.py", line 316, in
send_report
msgname = os.path.expanduser(outfile) or ('/var/tmp/%s.bug' % package)
  File "/usr/lib/python2.7/posixpath.py", line 261, in expanduser
if not path.startswith('~'):
AttributeError: 'NoneType' object has no attribute 'startswith'


Looking at the code:

elif outfile or not ((mta and os.path.exists(mta)) or smtphost):
msgname = os.path.expanduser(outfile) or ('/var/tmp/%s.bug' % package)$


It would appear to be that outfile is None (not sure I understand why),
however the condition gets satisfied if a MTA is not installed or is
smtphost is defined.

It then crashes.

If this is an error condition, there needs to be a better error message,
and even better the temp file created by the editor should not get deleted.

Thanks
-- 
Brian May 

Bug#764904: apophenia: FTBFS - test suite times out or has unexpected failures

[Jerome BENOIT]

On 10/11/14 23:48, Edmund Grimley Evans wrote:
> By the way, it might be a good idea to remove the ">/dev/null 2>&1"
> from the command lines in case the compiler wants to warn you about
> this sort of thing. (I don't know whether GCC does in this particular
> case.)
> 

Please could you specify the place of this code.
Thanks in advance, Jerome


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

Bug#764904: apophenia: FTBFS - test suite times out or has unexpected failures

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks Edmund for your comment:
I will forward them to the upstream author.

On 10/11/14 23:48, Edmund Grimley Evans wrote:
> By the way, it might be a good idea to remove the ">/dev/null 2>&1"
> from the command lines in case the compiler wants to warn you about
> this sort of thing. (I don't know whether GCC does in this particular
> case.)
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJUYVyoAAoJEIC/w4IMSybjKs0IANSzM1Bd7KybP7qK43ZhYSfR
yGB0qP9nOBgVTmb/ujq5309ykdMvdEyCAgo/8HzjC+ttHFukYUnVc7f80PsVC/Em
uTNYsOC9Dc5R/u75ZaiKFNK2L6Svns7CR4cYJ33mSdptpVYaPSYnxsfL+jEXKO8D
9WY4B3m22qQe1CXWEdKDCCLqx+j5KAbHQPdoqm2wagg0gUa3DI6H+faMjmBGjhQK
3NrO8twq/Hss9WKMlr9H8zQ5KAcmqVALIjRHcj2+LNHjgrk2QjeqZNHkObVOlrFz
cvoUrr4wXMJn7EeCfMUHMkImUaJdup/GZYmsqVylhAUEb0NV5pHtnoqtEqUuwdY=
=gKn6
-END PGP SIGNATURE-


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

Bug#769050: [Debian-med-packaging] Bug#769050: sra-toolkit should only install binaries, not symlinks to symlinks to binaries

[Charles Plessy]

Le Mon, Nov 10, 2014 at 04:15:07PM -0800, Don Armstrong a écrit :
> Package: src:sra-sdk
> Version: 2.3.5-2+dfsg-1
> Severity: minor
> 
> Since sra-toolkit isn't co-installable with another version, it should
> just install the binaries, and not symlinks which are two levels deep.

Hi Don,

I (or any other packager quicker than me) will investigate this for the next
update of the package.

Update to version 2.4.x has been delayed because the source tarball is not
distributed on the NCBI's website.  It is now on GitHub but there has been
a gap.

If you have time, and if it is till relevant to version 2.4.2-3, maybe you can
also make your suggestion in Upstream's tracker ?

https://github.com/ncbi/sra-tools

Have a nice day,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan


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

Bug#769053: uwsgi-plugin-python3: libapache2-mod-wsgi-py3: should not provide httpd-wsgi

[Brian May]

Package: uwsgi-plugin-python3
Version: 2.0.7-1
Severity: important

uwsgi-plugin-python3 provides httpd-wsgi, however httpd-wsgi is for the
Python 2 WSGI API.

As the Python 3 WSGI API cannot be used with Python 2 applications, this
will break Python 2 applications that depend on httpd-wsgi.

A bug report has been filled against debian-policy for a httpd-wsgi3
virtual package for Python 3 WSGI, see #768117.
-- 
Brian May 

Bug#769052: libapache2-mod-wsgi-py3: should not provide httpd-wsgi

[Brian May]

Package: libapache2-mod-wsgi-py3
Version: 2.0.7-1
Severity: important

 provides httpd-wsgi, however httpd-wsgi is for the Python 2 WSGI API.

As the Python 3 WSGI API cannot be used with Python 2 applications, this
will break Python 2 applications that depend on httpd-wsgi.

As libapache2-mod-wsgi-py3 conflicts with libapache2-mod-wsgi this also
means anybody installing libapache2-mod-wsgi-py3 will
cause libapache2-mod-wsgi to be removed, breaking Python 2 applications
that depend on the recommended httpd-wsgi virtual package.

A bug report has been filled against debian-policy for a httpd-wsgi3
virtual package for Python 3 WSGI, see #768117.
-- 
Brian May 

Bug#768979: Thanks and geoipupdate for free GeoLite users

[Gregory Oschwald]

Thanks so much for packaging all of these!

Although it is poorly advertised, geoipupdate can actually be used with the
free GeoLite databases, e.g., with the GeoIP.conf file:

UserId 99
LicenseKey 
ProductIds 506 533


I think it would be reasonable to use this as a default in a general
package. The GeoLite2 databases should work too with the product IDs of
"GeoLite2-City" and "GeoLite2-Country", but there appears to be an issue
with the deployment of them for geoipupdate currently.

Hopefully in the future we will clean up that fake UserId/LicenseKey, but
even as it stands, this is preferable for most people to using a homemade
script for downloading as it only downloads if the file has changed,
verifies the MD5s before deploy, and safely moves the verified files over
the old files.

Greg

Bug#769054: nautilus: Crashes when reallocating a bookmark

[Manuel Luque]

Package: nautilus
Version: 3.14.0-1
Severity: normal

Dear Maintainer,

When the user has several bookmarks in Nautilus, and he/she drags a bookmark
in the list of bookmarks in order to change the order in which they appear, then
Nautilus closes automatically. When the user opens Nautilus again, the order
of bookmarks have not changed. I should expect:
1) Nautilus kept open when reordering bookmarks.
2) The bookmarks are reallocated when the user decides to reorder them.

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

Kernel: Linux 3.16-3-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 nautilus depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  gvfs   1.22.1-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-12
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libexempi3 2.2.1-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.14.4-1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libglib2.0-0   2.42.0-2
ii  libglib2.0-data2.42.0-2
ii  libgnome-desktop-3-10  3.14.1-1
ii  libgtk-3-0 3.14.4-1
ii  libnautilus-extension1a3.14.0-1
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.36.8-2
ii  libpangocairo-1.0-01.36.8-2
ii  libselinux12.3-2
ii  libtracker-sparql-1.0-01.2.2-2+b1
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-4
ii  nautilus-data  3.14.0-1
ii  shared-mime-info   1.3-1

Versions of packages nautilus recommends:
ii  eject  2.1.5+deb1+cvs20081104-13.1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-sushi3.12.0-2
ii  gvfs-backends  1.22.1-1
ii  librsvg2-common2.40.5-1

Versions of packages nautilus suggests:
ii  brasero3.11.4-1
ii  eog3.14.1-1
ii  evince [pdf-viewer]3.14.1-1
ii  okular [pdf-viewer]4:4.14.2-2
ii  totem  3.14.0-2
ii  tracker1.2.2-2+b1
ii  vlc [mp3-decoder]  2.2.0~pre4-2
ii  vlc-nox [mp3-decoder]  2.2.0~pre4-2
ii  xdg-user-dirs  0.15-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#707087: xword: Close button does not work on Help > About dialog

[Eric Cooper]

Package: xword
Version: 2.0.0~rc2-1
Followup-For: Bug #707087

I happened to try this while running xword from a terminal window, and
noticed that clicking the Close button on the About dialog
consistently produces the following error:

Traceback (most recent call last):
  File "/usr/share/games/xword/main.py", line 485, in 
dialog.connect('response', lambda *args: dialog.destroy())
NameError: free variable 'dialog' referenced before assignment in enclosing 
scope


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

Bug#769051: fr_CA locale has wrong weekday start (should be 1, not 2)

[Don Armstrong]

Package: locales
Version: 2.13-38
Control: found -1 2.19-12
Control: submitter -1 ste...@openmailbox.org

On Mon, 10 Nov 2014, Stephane R. wrote:
> It's imposible include the name of the package because it's a bad
> locate configuration file!!!

The name of the package you want is locales.

dpkg -S locales/fr_CA; will give you that information
 
> Date: Mon, 10 Nov 2014 18:41:27 -0500
> From: "Stephane R." 
> To: sub...@bugs.debian.org
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101
>  Icedove/31.2.0
> Subject: fr_CA locale error
> 
> French Canadian locale error in Wheezy and Jessie
> 
> In this file:
> /usr/share/i18n/locales/fr_CA
> 
> Please replace "first_weekday 2" by "first_weekday 1". The french canadian
> use only a calendar begin by the Sunday, not the Monday same the european.
> 
> -- 
> . ><> Stéphane R. <><

-- 
Don Armstrong  http://www.donarmstrong.com

If I had a letter, sealed it in a locked vault and hid the vault
somewhere in New York. Then told you to read the letter, thats not
security, thats obscurity. If I made a letter, sealed it in a vault,
gave you the blueprints of the vault, the combinations of 1000 other
vaults, access to the best lock smiths in the world, then told you to
read the letter, and you still can't, thats security.
 -- Bruce Schneier


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

Bug#769049: unblock: ruby-elasticsearch/1.0.5-1

[Potter, Tim (Cloud Services)]

Nuts - I think I've filed this against the wrong package version and
slightly too early.  There should shortly be an upload of version 1.0.5-2
to unstable which (after ageing out) should then be blocked entering
testing.

Sorry, the whole process makes more sense now.  (-:


Tim.


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

Bug#769050: sra-toolkit should only install binaries, not symlinks to symlinks to binaries

[Don Armstrong]

Package: src:sra-sdk
Version: 2.3.5-2+dfsg-1
Severity: minor

Since sra-toolkit isn't co-installable with another version, it should
just install the binaries, and not symlinks which are two levels deep.



-- 
Don Armstrong  http://www.donarmstrong.com

When bad men combine, the good must associate; else they will fall one
by one, an unpitied sacrifice in a contemptible struggle.
 -- Edmund Burke "Thoughts on the Cause of Present Discontents"


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

Bug#768842: dpkg: please document the dependency:arch syntax for architecture qualifiers

[Guillem Jover]

Hi!

On Mon, 2014-11-10 at 20:23:25 +0100, Johannes Schauer wrote:
> Quoting Guillem Jover (2014-11-10 19:48:33)
> > (Hmm, doing another quick check, I might rearrange the lists to mention
> > real arch, "any" then "native" if relevant to be consistent.)
> 
> I don't fully understand your last comment in brackets but here is what I
> thought (my comments apply to deb-control as well as deb-src-control):

I've done the change now, just changing the order of the architecture
qualifier values list.

> > @@ -187,8 +187,16 @@ fields is a list of groups of alternative packages. 
> > Each group is a list
> >  of packages separated by vertical bar (or `pipe') symbols, `|'. The
> >  groups are separated by commas. Commas are to be read as `AND', and pipes
> >  as `OR', with pipes binding more tightly. Each package name is
> > +optionally qualified with an architecture name appended after a colon ":",
> 
> It is not necessarily an "architecture name" that follows but also "any" or
> "native". For clarity and to avoid ambiguity with below section I'd write:
> 
>   'optionally followed by an architecture qualifier after a colon ":",'
> 
> or
> 
>   'optionally qualified with an architecture name or "any" or "native"
>   appended after a colon ":"'
> 
> Since this is explained in the next paragraph, the former is probably the
> better choice.

Right, changed. I actually had:

  "… architecture qualified with an architecture name appended …"

but removed the first one to avoid duplication instead of getting rid
of the second one. :)

> >  optionally followed by a version number specification in parentheses.
> >  .LP
> > +An architecture qualifier name can be \fBany\fP (since dpkg 1.16.2) or a
> > +real Debian architecture name (since dpkg 1.16.5).
> > +If omitted, the default is the current binary package architecture.
> 
> maybe say host or native architecture here? Maybe rather "native" because
> "host" is more meaningful in the crossbuild context. Maybe there is an even
> better way in dpkg speech. Is the native architecture not determined by the
> architecture of dpkg itself?

The default architecture for those dependencies is the one matching
the binary package containing that dependency field.

So:

  dpkg native → amd64
  dpkg foreign → i386

  Package: pkgname
  Architecture: i386
  Depends: otherpkg

In that case the implicit arch-qualifier for otherpkg is i386. The
concept of host and native does not apply here, because if the native
and foreign dpkg architectures got swapped the same implicit architecture
qualifier would apply to otherpkg. Or did you mean something else?

> > +A real Debian architecture name will match exactly that architecture for
> > +that package name, \fBany\fP will match any architecture for that package
> > +name.
> 
> maybe it should be noted that it is only meaningful to annotate dependencies 
> on
> Multi-Arch:allowed packages with :any?

Yeah, make sense, added.

> > +An architecture qualifier name can be \fBany\fP (since dpkg 1.16.2),
> > +\fBnative\fP (since 1.16.5) or a real Debian architecture name (since
> > +dpkg 1.16.5).
> > +If omitted, the default for \fBBuild\-Depends\fP fields is the current host
> > +architecture, the default for \fBBuild\-Conflicts\fP fields is \fBany\fP.
> > +A real Debian architecture name will match exactly that architecture for
> > +that package name, \fBany\fP will match any architecture for that package
> > +name, and \fBnative\fP will match the current build architecture.
> 
> As above, maybe mention that :any only makes sense to annotate M-A:allowed
> packages with and :native is disallowed for M-A:foreign packages. But maybe
> this is too much for this man page.

This too, added.

I've also updated the Multi-Arch field description. New patch
attached.

Thanks,
Guillem
From db3e96c698c547a92bcf138700ff2b307f9aad42 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Mon, 10 Nov 2014 19:40:22 +0100
Subject: [PATCH] man: Document arch-qualifiers for dependency fields

Closes: #768842
Reported-by: Johannes Schauer 
---
 man/deb-control.5 | 21 -
 man/deb-src-control.5 | 14 +-
 2 files changed, 29 insertions(+), 6 deletions(-)

diff --git a/man/deb-control.5 b/man/deb-control.5
index 289b1ba..d4b6766 100644
--- a/man/deb-control.5
+++ b/man/deb-control.5
@@ -3,7 +3,7 @@
 .\" Copyright © 1995 Raul Miller, Ian Jackson, Ian Murdock
 .\" Copyright © 1999 Ben Collins 
 .\" Copyright © 2000 Wichert Akkerman 
-.\" Copyright © 2007-2011, 2013 Guillem Jover 
+.\" Copyright © 2007-2011, 2013-2014 Guillem Jover 
 .\" Copyright © 2008-2012 Raphaël Hertzog 
 .\"
 .\" This is free software; you can redistribute it and/or modify
@@ -126,8 +126,8 @@ of a different architecture from itself. The value \fBforeign\fP means that
 the package is not co-installable with itself, but should be allowed to
 satisfy the dependency of a package of a different arch from itself. The
 value \fBallowed\fP allows reverse-dependencies to 

Bug#769049: unblock: ruby-elasticsearch/1.0.5-1

[Tim Potter]

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

Please unblock package ruby-elasticsearch.

This package has a RC bug (#768613) filed against it due to a dependency
that is not currently in testing.  The dependency is for an optional 
transport-layer plugin that doesn't affect any functionality in the 
package.  One unit test (out of 127) has also been disabled.

I would love to see this package stay in testing and not be removed due
to a broken, optional dependency.  No source changes were made, and
the binary packages are unchanged

ruby-elasticsearch (1.0.5-2) unstable; urgency=medium

  * Remove build/test dependency on ruby-patron.  The ruby-patron
package is not currently in testing and is only one of a handful
of transport-layer adapters and so does not affect any functionality.
(Closes: #768613)

 -- Tim Potter   Tue, 11 Nov 2014 10:21:11 +1100

Attached are debdiffs for the source and binary packages.

unblock ruby-elasticsearch/1.0.5-1

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

Kernel: Linux 3.15.3-tinycore64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
diff -Nru ruby-elasticsearch-1.0.5/debian/changelog ruby-elasticsearch-1.0.5/debian/changelog
--- ruby-elasticsearch-1.0.5/debian/changelog	2014-11-11 10:48:47.0 +1100
+++ ruby-elasticsearch-1.0.5/debian/changelog	2014-11-11 10:51:21.0 +1100
@@ -1,3 +1,12 @@
+ruby-elasticsearch (1.0.5-2) unstable; urgency=medium
+
+  * Remove build/test dependency on ruby-patron.  The ruby-patron
+package is not currently in testing and is only one of a handful
+of transport-layer adapters and so does not affect any functionality.
+(Closes: #768613)
+
+ -- Tim Potter   Tue, 11 Nov 2014 10:21:11 +1100
+
 ruby-elasticsearch (1.0.5-1) unstable; urgency=low

   * Initial release (Closes: #760806)
diff -Nru ruby-elasticsearch-1.0.5/debian/control ruby-elasticsearch-1.0.5/debian/control
--- ruby-elasticsearch-1.0.5/debian/control	2014-11-11 10:48:47.0 +1100
+++ ruby-elasticsearch-1.0.5/debian/control	2014-11-11 10:51:21.0 +1100
@@ -14,7 +14,6 @@
ruby-jsonify,
ruby-mocha,
ruby-multi-json,
-   ruby-patron,
ruby-shoulda-context,
ruby-test-unit
 Standards-Version: 3.9.6
diff -Nru ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch
--- ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch	1970-01-01 10:00:00.0 +1000
+++ ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch	2014-11-11 10:51:21.0 +1100
@@ -0,0 +1,28 @@
+Description: Remove semi-bogus build/test dependency on ruby-patron
+ The ruby-patron package is currently not in testing, and looks like
+ it is no longer maintained.  This patch disables the build and test
+ dependency on ruby-patron as it's an optional transport-layer plugin.
+Author: Tim Potter 
+Last-Update: 2014-11-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: ruby-elasticsearch/elasticsearch-transport/test/unit/client_test.rb
+===
+--- ruby-elasticsearch.orig/elasticsearch-transport/test/unit/client_test.rb
 ruby-elasticsearch/elasticsearch-transport/test/unit/client_test.rb
+@@ -193,15 +193,6 @@ class Elasticsearch::Transport::ClientTe
+
+ assert_includes handlers, Faraday::Adapter::Typhoeus
+   end
+-
+-  should "detect the adapter" do
+-require 'patron'; load 'patron.rb'
+-
+-c = Elasticsearch::Transport::Client.new
+-handlers = c.transport.connections.all.first.connection.builder.handlers
+-
+-assert_includes handlers, Faraday::Adapter::Patron
+-  end
+ end
+
+   end
diff -Nru ruby-elasticsearch-1.0.5/debian/patches/series ruby-elasticsearch-1.0.5/debian/patches/series
--- ruby-elasticsearch-1.0.5/debian/patches/series	2014-11-11 10:48:47.0 +1100
+++ ruby-elasticsearch-1.0.5/debian/patches/series	2014-11-11 10:51:21.0 +1100
@@ -1 +1,2 @@
 really-disable-ruby-prof.patch
+disable-patron-test.patch
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Depends: ruby | ruby-interpreter, ruby-elasticsearch-api (= [-1.0.5-1),-] 
{+1.0.5-2),+} ruby-elasticsearch-transport (= [-1.0.5-1)-] {+1.0.5-2)+}
Version: [-1.0.5-1-] {+1.0.5-2+}
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Version: [-1.0.5-1-] {+1.0.5-2+}
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Bug#769048: ITP: pydxcluster -- Dxcluster reporting software for Linux ; Ham Radio

[ki7mt]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Owner: Greg Beam 
Severity: wishlist

* Package name: pydxcluster
  Version : 1.14
  Upstream Author : Jakab Szilárd
* URL : http://sourceforge.net/projects/pydxcluster/
* License : (GPL-3)
  Programming Lang: (Python)
  Description : Dxcluster reporting software for Linux ; Ham Radio

 Ext. Desc copied directly from: 
 A DX Cluster is in essence a "chatroom" or node into which amateur DX
 hunters can post information about DX either worked or heard.
 Physically, it is a central computer that collects, stores and
 disseminates information that hams send to it. There are thousands of
 nodes around the world, connected together via the internet or radio.
 connection to a cluster is by either telnet or packet radio.
 .
 The networked nature of DX clusters is perhaps its most powerful
 feature as it gives amateurs almost instant access to information about
 rare and unusual DX conditions such as meteor scatter or VHF ducting.
 .
 Cluster users will use computer software (for example, many logging
 programs have this capability) that is capable of communicating with
the cluster. On initial login, users will be asked to provide station
information. This allows other hams compare DX openings to their
physical position, and hence to make informed decisions about beam
direction for example. New information is passed on to logged in users
continuously.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUYVIwAAoJEBjA9rcNovmRla8P/0/3jSXmQfTiz0tRJnNmQFHl
Pl6Oy9Opi6/OmMgC9ef3HMbtrJBFdYoeD11r3MjMvQ6pYGP0JdBVqvuQK8NSUgzZ
+K6RDmUi+BoHyoSbbqaEDfrDmfJG+I0NC3EVavJaYFHICu/EHbJ8UHoyr8bMcIaX
JJ7Za5RisCB5rUZsp2TjNe2qBS2bwIEL7GouGrzsRPVctAAbaYgRvcIs/fPUT7Gk
1Yuid6BJBLpocpQcUvIZ0O32jprI6yQxrQQK925unYDoB+KHwz9RAtzw1Ew+HLVs
lni2AXFboCjNDvTYE9oJyUYuMlKaRbPPbP3S8URqaxAgQ4hXYQzoybMBvnCLeSHF
jLiyc0kdABiQyh5EKvOO5md8pWTaubysROOAehjG9e/glK8jGLzFDeJiMgn5CBia
pVHdl3mBsU/OXGG3rrUfznAnk8V0l8y4cDQ0XUQeE5Ho/wcMtxOAAwPvI+89x6tc
Sh7a4uqLrHt1HypifXt08cgoTGOH2o3mSj25iC2guhXnFAJCWOChHnLvXmK9m9ya
pBX9edlscWO8MTRuSu2zoRoK+jcG4DupMbByv1AFs2Q6MlJrzKsWNIy25K7W9Ojf
YjogexYOJQJV/8KYAulZjf3R6vq6gvPOELHDFnn0jSPR3OXDca/kf8CaOKpGav+a
pMwhuBYO+OeHU50GJ7Nt
=kygG
-END PGP SIGNATURE-


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

Bug#769047: requests.packages.urllib3 stub must be the same of global urllib3 package

[Daniele Tricoli]

Source: requests
Version: 2.4.3-1
Severity: critical
Justification: breaks unrelated software

To prevent other bugs like #767445.

Look at the whole thread for a complete explanation:
https://lists.debian.org/debian-python/2014/11/msg1.html

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

Kernel: Linux 3.16-3-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


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

Bug#637777: zeromq: fix kFreeBSD build

[Steven Chamberlain]

retitle 63 zeromq: tests fail on kfreebsd
severity 63 wishlist
thanks

Hi Gianluca,

Gianluca Bonetti wrote:
> I can confirm that zeromq_2.2.0+dfsg-6 builds cleanly on up to date Jessie.

Many thanks for checking this and supplying a build log.  We can see
in it though that the tests still fail;  the errors simply don't
cause the package to FTBFS any more (since package version -6).
.
I'll retitle the bug accordingly and reduce severity to 'wishlist' in
case someone ever can look into those in detail.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


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

Bug#768843: fetchmail: Improved TLS support

[Kurt Roeckx]

On Mon, Nov 10, 2014 at 11:50:58PM +0100, Matthias Andree wrote:
> > I've also changed the way in which opportunistic TLS works a
> > little.  It seems to have only done this with TLS1 for the above
> > stated reasons which were wrong.
> > 
> > This patch results in the following changes with a server support
> > STARTTLS:
> > | --ssl | no option | sslproto ssl23| sslproto tls1
> > Old:| TLS 1.2   | TLS1.0| not working   | TLS1.0
> > New:| TLS 1.2   | TLS1.2| TLS1.2| TLS1.0
> > 
> > The "sslproto ssl23" case just send logout, I assume because
> > maybe_tls returns false.
> > 
> > This started by making the call to SSLv3_client_method() optional
> > in case openssl doesn't support it.
> 
> I am not sure I understand the last two phrases.  The next-to-last is
> probably a matter of reading code and perhaps debugging (also your later
> sslproto "" behaving differently than an omitted sslproto option - this
> may have to do with automated repolls for opportunistic TLS).

I just looked at the traffic using either wireshark and/or setting
-v.  It looks like this in the log file:
IMAP< * OK IMAP4 ready
IMAP> A0001 CAPABILITY
IMAP< * CAPABILITY ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ID 
IDLE IMAP4rev1 LIST-EXTENDED LITERAL+ MULTIAPPEND NAMESPACE QRESYNC QUOTA 
RIGHTS=ektx SASL-IR SEARCHRES UIDPLUS UNSELECT WITHIN ESORT I18NLEVEL=1 SORT 
THREAD=ORDEREDSUBJECT LIST-STATUS XLIST STARTTLS LOGINDISABLED
IMAP< A0001 OK completed
Authorization failure on 
For help, see http://www.fetchmail.info/fetchmail-FAQ.html#R15
IMAP> A0002 LOGOUT
IMAP< * BYE Zimbra IMAP server terminating connection
IMAP< A0002 OK completed

It should just continue with LOGIN instead of LOGOUT.  This is the
behaviour I see with sslproto set to either ssl23 or "", it's not
what I'm expecting.  I didn't wait for it to try again.

The thing about SSLv3_client_method():  I've dropped SSLv3 support
in Debian's openssl by compiling with no-ssl3.  However the
SSLv3_client_method() still exists so you can still create a SSLv3
connection.  I want to remove the existence of that
SSLv3_client_method() which is what I started with.  And then I
noticed all the other things and just wanted to fix that.

You should always use SSLv23_client_method() and set the options
you want instead, like SSL_OP_NO_SSLv2 or SSL_OP_NO_TLSv1_2.

> I am rather loathe to propose/endorse/support changing option semantics
> for a stable release; we'd probably need to add new switches.

I think I haven't changed the behaviour that much.  The changes
are:
- By default it now does opportunistic TLS with all supported
  version instead of only supporting TLS 1.0, and I get TLS 1.2
  instead of 1.0.  This might actually cause problems for people
  who try to connect to a broken server that is intolerant to TLS
  1.2.  When using -ssl it was already doing that, it now just
  also does it when using opportunistic TLS.
  (That's the "tls1" to ctl->sslproto change in the SSLOpen()
  calls.) 
- Change the madatory upgrade using STARTTLS from == "tls1" to
  != "".
  (That's the change in tls.c)

> Please have a look at the current state of fetchmail's "master" (note:
> it is non-default, so you'll need to "git checkout master" after
> cloning) branch in Git, either here
>  or here:
> 

I'll try to take a look at this tomorrow.


Kurt


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

Bug#767711: openstack-pkg-tools: systemd start fails a fresh install

[Mikaël Cluseau]

Hi Thomas,

On 11/11/2014 10:36 AM, Thomas Goirand wrote:

I have uploaded version 19 of openstack-pkg-tools, which fixes the
issue. The way to fix it is to do:

RuntimeDirectory=${PROJECT_NAME}

as per the systemd manpages, and per what the guys in #debian-systemd
adviced.


Systemd is awesome: of course, they though about the fact that /run or 
/var/run is standard and doesn't have to be repeated in each unit...


Thanks for fixing :-)


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

Bug#767711: openstack-pkg-tools: systemd start fails a fresh install

[Thomas Goirand]

Hi Mikael,

I have uploaded version 19 of openstack-pkg-tools, which fixes the
issue. The way to fix it is to do:

RuntimeDirectory=${PROJECT_NAME}

as per the systemd manpages, and per what the guys in #debian-systemd
adviced.

The fixed package has been uploaded to Sid, and unblocked by the release
team. I will then re-upload updates of all OpenStack packages so that
they have the fixe.

Cheers,

Thomas Goirand (zigo)


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

Bug#743057: FTBFS, testsuite failure

[Gianluca Bonetti]

Hello

buzztard has gone from Debian, see https://tracker.debian.org/pkg/buzztard

buzztard has been removed from testing on 2013-12-31
(https://tracker.debian.org/news/435659)
buzztard has been removed from unstable on 2014-05-20
(https://tracker.debian.org/news/435660)

So I think that this bug could be marked as closed.

Best regards
Gianluca Bonetti


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

Bug#769046: inn2: Allow for better TLS configurability

[christian mock]

Source: inn2
Severity: wishlist
Tags: patch

Dear Maintainer,

INN, at the moment, supports TLS connections to nnrpd, but does not
allow any configuration besides the certificate and key.

This means that Wheezy's nnrpd is currently susceptible to the CRIME
(because TLS compression is on) and POODLE (because SSLv3 is
supported) attacks, should those be exploitable with NNTP. In
addition, it supports weak symmetrical ciphers (40 and 56 bit key
length). 

I've patched nnrpd to allow for detailed TLS configuration: protocol
versions, cipher suites, compression and whether the client or server
choses the cipher can now be configured. With the default
configuration, TLS behaviour is unchanged, as to not break existing
setups.

This patch is to be integrated upstream[0], but ideally I'd like it
to be in the next Wheezy point release because I consider the current
TLS config to be insecure.

The patch, as attached, is against a clean 2.5.4 upstream source, but
I'd be happy to provide a patch for quilt if you tell me which package
version I should target.

regards,

cm.

[0] https://lists.isc.org/pipermail/inn-workers/2014-November/018339.html
diff --git a/doc/pod/inn.conf.pod b/doc/pod/inn.conf.pod
index f8f5f79..98ebd6e 100644
--- a/doc/pod/inn.conf.pod
+++ b/doc/pod/inn.conf.pod
@@ -1054,6 +1054,28 @@ I/key.pem.
 This file must only be readable by the news user or B will refuse to
 use it.
 
+=item I
+
+The list of TLS protocol versions to support. Valid protocols are
+B, B, B, B and B. The default
+value is B<[ SSLv3 TLSv1 TLSv1.1 TLSv1.2 ]>.
+
+=item I
+
+The string describing the cipher suites OpenSSL will support. See
+OpenSSL's B command documentation for details. The default is
+unset, which uses OpenSSL's default cipher suite list.
+
+=item I
+
+Whether to let the client or the server decide the preferred cipher.
+This is a boolean and the default is false.
+
+=item I
+
+Whether to enable or disable TLS compression support (boolean). The
+default is true.
+
 =back
 
 =head2 Monitoring
diff --git a/doc/pod/news.pod b/doc/pod/news.pod
index 4315b3f..64cd93b 100644
--- a/doc/pod/news.pod
+++ b/doc/pod/news.pod
@@ -1,3 +1,17 @@
+=head1 Changes in TLS configuration
+
+=over 2
+
+=item *
+
+New parameters used by B to fine-tune the TLS configuration:
+I, I, I and
+I. If you've been using TLS with B before, be
+aware that the defaults of those parameters may differ from the
+previous defaults (which depended on your OpenSSL version).
+
+=back
+
 =head1 Changes in 2.5.4
 
 =over 2
diff --git a/doc/pod/nnrpd.pod b/doc/pod/nnrpd.pod
index 9c13821..32698ae 100644
--- a/doc/pod/nnrpd.pod
+++ b/doc/pod/nnrpd.pod
@@ -224,6 +224,12 @@ run B.  (Change the path to B to match your installation.)
 You may need to replace C with C<563> if C isn't
 defined in F on your system.
 
+Optionally, you may set the I, I,
+I and I parameters in
+F to fine-tune the behaviour of the TLS negotiation whenever
+a new attack on the TLS protocol or some supported cipher suite is
+discovered.
+
 =head1 PROTOCOL DIFFERENCES
 
 B implements the NNTP commands defined in S (NNTP),
diff --git a/include/inn/innconf.h b/include/inn/innconf.h
index ee16620..669255c 100644
--- a/include/inn/innconf.h
+++ b/include/inn/innconf.h
@@ -127,6 +127,10 @@ struct innconf {
 char *tlscapath;/* Path to a directory of CA certificates */
 char *tlscertfile;  /* Path to the SSL certificate to use */
 char *tlskeyfile;   /* Path to the key for the certificate */
+bool tlsprefer_server_ciphers; /* Make server select the cipher */
+bool tlscompression;		   /* Turn TLS compression on/off */
+struct vector *tlsprotocols;		  /* List of supported TLS versions */
+char *tlsciphers;		  /* openssl-style cipher string */
 #endif /* HAVE_SSL */
 
 /* Monitoring */
diff --git a/lib/innconf.c b/lib/innconf.c
index ded674c..9e6183d 100644
--- a/lib/innconf.c
+++ b/lib/innconf.c
@@ -231,6 +231,10 @@ const struct config config_table[] = {
 { K(tlscapath),   STRING  (NULL) },
 { K(tlscertfile), STRING  (NULL) },
 { K(tlskeyfile),  STRING  (NULL) },
+{ K(tlsprefer_server_ciphers), BOOL  (false) },
+{ K(tlscompression),  BOOL(true) },
+{ K(tlsprotocols),LIST(NULL) },
+{ K(tlsciphers),  STRING  (NULL) },
 #endif /* HAVE_SSL */
 
 /* The following settings are used by nnrpd and rnews. */
diff --git a/nnrpd/tls.c b/nnrpd/tls.c
index 62b1a51..22a00c7 100644
--- a/nnrpd/tls.c
+++ b/nnrpd/tls.c
@@ -425,7 +425,9 @@ set_cert_stuff(SSL_CTX * ctx, char *cert_file, char *key_file)
 int
 tls_init_serverengine(int verifydepth, int askcert, int requirecert,
   char *tls_CAfile, char *tls_CApath, char *tls_cert_file,
-  char *tls_key_file)
+  char *tls_key_file, int prefer_server_ciphers,
+		  int tls_compression, struct vector *tls_proto_vect,
+		  char *tls_cipher

Bug#720378: cctools: FTBFS on non-linux

[Gianluca Bonetti]

Hello

I wanted to test this bug, but cctools is no more in Debian.

Bug was opened on 2013/08/21

cctools was removed from Debian on 2013/09/08
See https://tracker.debian.org/news/153893

So I think this bug could be marked as fixed.

Best regards
Gianluca Bonetti


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

Bug#769031: php-horde-editor: Suggested solution for working HTML editor

[root]

Package: php-horde-editor
Version: 2.0.4+debian0-3
Followup-For: Bug #769031

Dear Maintainer,

As you know, even after sym links are added so that all the 
appropriate file uploads succeed, CKEditor 4.x does not 
appear compatible with Horde 5.2.x and Imp 6.2.x.  This was 
confirmed by the Horde team today: "Using Ckeditor 4.x will 
only be possible when all of IMP's javascript code interfacing 
with Ckeditor is rewritten."

The easiest fix appears to be to install files and directories from 
horde/framework/Editor/js/ckeditor
into the debian package directory /usr/share/horde/js/ckeditor/

I tried this and it fixed the problem with the HTML editor not working.

This will also remove the dependency on ckeditor 4.4.4 and 
the requirement for a sym link imp/core -> /usr/share/javascript/ckeditor/core

The downside is the Horde/Imp HTML compose security updates will now depend
on the Horde dev team and CKEditor security back ports to 3.6.x.

I have suggested that the Horde team establish a sponsorship fund to pay
for moving to a current version of CKEditor.

Thank you

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages php-horde-editor depends on:
ii  ckeditor 4.4.4+dfsg1-2
ii  php-horde-browser2.0.7-2
ii  php-horde-exception  2.0.4-4
ii  php-horde-serialize  2.0.2-5
ii  php5-common  5.6.2+dfsg-1

php-horde-editor recommends no packages.

php-horde-editor 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#769045: gv: zooms in when file is changed

[Renato Andrade Galvão]

Package: gv
Version: 1:3.7.4-1
Severity: normal

By opening a pdf (or a ps) file with the --watch option and selecting 'Fit
width to window' in the view menu, gv incrementally zooms in the view every
time the pdf file is regenerated.

The reproduction can be made by doing:

1. gv --watch test.pdf

2. Select 'Fit width to window' in the menu

3. latex test.tex && dvips test.dvi && ps2pdf test.ps

Then repeat step 3. several times and gv will zoom in for each reload. This
seems to happen with the combination of --watch option and 'Fit width to
window'.



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

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

Versions of packages gv depends on:
ii  ghostscript-x  9.06~dfsg-1.1+b1
ii  libc6  2.19-12
ii  libx11-6   2:1.6.2-3
ii  libxinerama1   2:1.1.3-1+b1
ii  libxmu62:1.1.2-1
ii  libxt6 1:1.1.4-1+b1
ii  xaw3dg 1.5+E-18.2

Versions of packages gv recommends:
ii  xaw3dg  1.5+E-18.2

gv 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#768360: iceweasel: crashes with Illegal instruction at startup

[Mike Hommey]

On Tue, Nov 11, 2014 at 12:06:30AM +0100, Ondrej Zary wrote:
> (gdb) print JSC::MacroAssemblerX86Common::s_sseCheckState
> $1 = JSC::MacroAssemblerX86Common::HasSSE3

Aha! At least now it's clear what part is doing wrong.

Can you compile and run the following code, and give its output?

#include 

int main() {
  int flags_edx = 0;
  int flags_ecx = 0;
  asm (
   "movl $0x1, %%eax;"
   "pushl %%ebx;"
   "cpuid;"
   "popl %%ebx;"
   : "=c" (flags_ecx), "=d" (flags_edx)
   :
   : "%eax"
   );
  printf("%04x %04x\n", flags_ecx, flags_edx);
  return 0;
}

Thanks

Mike


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

Bug#769044: unblock (pre-approval): xfce4-notes-plugin

[peter green]

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

I'm seeking approval for fixing the arm64 build failure in xfce4-notes-plugin.
The package FTBFS due to outdated config.sub/guess.

The maintainer doesn't have a problem with the changes but wants approval from
the release team before going ahead.

The attatched debdiff uses --with autotools_dev to update config.sub and 
config.guess unconditionally . If you would preffer a different approach to
updating them please tell me.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


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

Bug#761986: Me too!

[Dima Kogan]

Henrik Sandklef  writes:

> Can you run the same command you had problem with:
>
>   cnee --record --mouse -o /tmp/xnee.xns --first-last --smp
>
> and use a mouse instead of the Touchpad. This is really not likely the
> cause, but I would like to make sure.

That's it!

Currently my laptop is on a docking station, so both a touchpad and a
USB mouse are available. Recording events from the USB mouse works just
fine, but recording events from the touchpad requires
--force-core-replay, as described previously. This is both with the
stock xnee and with the one you sent a few days ago. I'm attaching 4
xnee recordings, showing all combinations of (USB,touchpad) and (debian
cnee,patched cnee).



xnee_debian.xns
Description: Binary data


xnee_debian_touchpad.xns
Description: Binary data


xnee_from_henrik_2014_11_06.xns
Description: Binary data


xnee_from_henrik_2014_11_06_touchpad.xns
Description: Binary data

Bug#769043: unblock: xserver-xorg-video-geode/2.11.16-5

[Martin-Éric Racine]

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

Please unblock package xserver-xorg-video-geode

2.11.16-4 mistakenly dropped a (Provides: xorg-driver-video). Without it, on 
hosts without any other X.Org video driver installed, this results in an APT 
decision to remove the whole X.Org stack and most desktop applications. 

debdiff (minus changelog.dch, which somehow shipped with 2.11.16-4 unnoticed):

diff -Nru xserver-xorg-video-geode-2.11.16/debian/changelog 
xserver-xorg-video-geode-2.11.16/debian/changelog
--- xserver-xorg-video-geode-2.11.16/debian/changelog   2014-09-14 
13:41:27.0 +0300
+++ xserver-xorg-video-geode-2.11.16/debian/changelog   2014-11-11 
01:12:48.0 +0200
@@ -1,3 +1,12 @@
+xserver-xorg-video-geode (2.11.16-5) unstable; urgency=medium
+
+  * debian/control:
++ Provides: xorg-driver-video
+  This reverses part of the previous changes. Without this, APT uninstalls
+  the whole X.Org if no other video driver is installed (Closes: #769042).
+
+ -- Martin-Éric Racine   Tue, 11 Nov 2014 01:07:59 
+0200
+
 xserver-xorg-video-geode (2.11.16-4) unstable; urgency=medium

   * debian/control,debian/rules; Gotten one step closer to XSF:
diff -Nru xserver-xorg-video-geode-2.11.16/debian/control 
xserver-xorg-video-geode-2.11.16/debian/control
--- xserver-xorg-video-geode-2.11.16/debian/control 2014-09-14 
14:00:15.0 +0300
+++ xserver-xorg-video-geode-2.11.16/debian/control 2014-11-11 
00:33:21.0 +0200
@@ -23,7 +23,8 @@
 Depends: ${misc:Depends},
  ${shlibs:Depends},
  ${xviddriver:Depends}
-Provides: xserver-xorg-video-amd,
+Provides: xorg-driver-video,
+  xserver-xorg-video-amd,
   ${xviddriver:Provides}
 Breaks: xserver-xorg-video-amd (<< ${binary:Version})
 Description: X.Org X server -- Geode GX2/LX display driver

unblock xserver-xorg-video-geode/2.11.16-5

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (1001, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16-3-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#637777: zeromq: fix kFreeBSD build

[Gianluca Bonetti]

Hello

I can confirm that zeromq_2.2.0+dfsg-6 builds cleanly on up to date Jessie.

Best regards
Gianluca Bonetti

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libzmq1 depends on:
ii  libc0.12.19-12
ii  libgcc11:4.9.1-19
ii  libpgm-5.1-0   5.1.118-1~dfsg-1
ii  libstdc++6 4.9.1-19
ii  libuuid1   2.25.2-2
ii  multiarch-support  2.19-12

libzmq1 recommends no packages.

libzmq1 suggests no packages.

-- no debconf information
dpkg-buildpackage: source package zeromq
dpkg-buildpackage: source version 2.2.0+dfsg-6
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Laszlo Boszormenyi (GCS) 
 dpkg-source --before-build zeromq-2.2.0+dfsg
dpkg-buildpackage: host architecture kfreebsd-amd64
 debian/rules clean
dh clean --with=autoreconf
   dh_testdir
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 debian/rules build
dh build --with=autoreconf
   dh_testdir
   dh_autoreconf
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: copying file `config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `config'.
libtoolize: copying file `config/libtool.m4'
libtoolize: copying file `config/ltoptions.m4'
libtoolize: copying file `config/ltsugar.m4'
libtoolize: copying file `config/ltversion.m4'
libtoolize: copying file `config/lt~obsolete.m4'
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
perf/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
tests/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
parallel-tests: installing 'config/test-driver'
   debian/rules override_dh_auto_configure
make[1]: ingresso nella directory "/home/src/zeromq-2.2.0+dfsg"
dh_auto_configure -- --with-system-pgm
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for gcc option to accept ISO C99... -std=gnu99
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking for a sed that does not truncate output... /bin/sed
checking for gawk... (cached) gawk
checking for xmlto... no
checking for asciidoc... no
checking build system type... x86_64-pc-kfreebsd-gnu
checking host system type... x86_64-pc-kfreebsd-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc -std=gnu99... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-pc-kfreebsd-gnu file names to x86_64-pc-kfreebsd-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-kfreebsd-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for

Bug#768772: ITP: xkcdpass -- secure passphrase generator inspired by XKCD 936

[Ben Finney]

Jonas Smedegaard  writes:

> [adding bugreport as recipient]

Thanks. I need to be more careful in accessing Debian discussion
forums; I usually do so via via NNTP.

> curious questions for your xkcdpass tool:
>
>   * Does it handle alternate dictionaries (e.g. danish)?
>   * Does it handle massaging dictionary (e.g. strip profanities)?

The tool comes with a default wordlist, but can be instructed via a
command-line option to use any correctly-formatted wordlist the user
chooses.

So, yes, it allows the above if the user points it to an existing
wordlist.

-- 
 \ “Education is learning what you didn't even know you didn't |
  `\  know.” —Daniel J. Boorstin, historian, 1914–2004 |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature

Bug#768570: A new RC

[Bastien ROUCARIES]

control: severity -1 serious
control: tags -1 + pending

Uploaded under mentors. Waiting for your sponsorship

Bastien

On Sun, Nov 9, 2014 at 10:02 PM, Mathieu Parent  wrote:
> Hello Bastien,
>
> Can you propose a patch for the missing _bootstrap.js?
>
> Regards
>
> --
> Mathieu


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

Bug#768360: iceweasel: crashes with Illegal instruction at startup

[Ondrej Zary]

On Monday 10 November 2014 23:18:14 Mike Hommey wrote:
> On Mon, Nov 10, 2014 at 09:25:50PM +0100, Ondrej Zary wrote:
> > On Monday 10 November 2014 06:03:04 Mike Hommey wrote:
> > > On Sun, Nov 09, 2014 at 08:30:58AM +0900, Mike Hommey wrote:
> > > > Okay, so despite all the changes in the related code, this was not
> > > > fixed. I now need to know if this is a bug in cpu detection or in the
> > > > code deciding what to JIT features to enabled based on the cpu
> > > > detection.
> > > >
> > > > In gdb, after the crash, with version 31, could you report what the
> > > > following command prints out?
> > > >
> > > > gdb> print JSC::MacroAssemblerX86Common::s_sseCheckState
> >
> > Program received signal SIGILL, Illegal instruction.
> > [Switching to Thread 0xac4ffb70 (LWP 6778)]
> > 0xac620722 in ?? ()
> > (gdb) print JSC::MacroAssemblerX86Common::s_sseCheckState
> > No type "MacroAssemblerX86Common" within class or namespace "JSC".
>
> Did you run this on version 31?

Yes, 31.2.0esr-2~deb7u1. But I forgot to do "info threads" before. Now I got
this:

Program received signal SIGILL, Illegal instruction.
0xae0466f1 in ?? ()
(gdb) print JSC::MacroAssemblerX86Common::s_sseCheckState
No type "MacroAssemblerX86Common" within class or namespace "JSC".
(gdb) info threads
  Id   Target Id Frame
  25   Thread 0xacafeb70 (LWP 8278) "Analysis Helper"
0xb592d615 in js::detail::HashTable::SetOps, 
js::SystemAllocPolicy>::lookup (this=0xb1375b80, l=..., keyHash=3606372014, 
collisionBit=0) at ../../dist/include/js/HashTable.h:1241
  24   Thread 0xad5feb70 (LWP 8277) "Analysis Helper" 0xb7fe1422 in 
__kernel_vsyscall ()
  21   Thread 0xa8effb70 (LWP 8274) "StreamTrans #4" 0xb7fe1422 in 
__kernel_vsyscall ()
  20   Thread 0xa86feb70 (LWP 8273) "ImageDecoder #1" 0xb7fe1422 in 
__kernel_vsyscall ()
  18   Thread 0xa93ffb70 (LWP 8271) "DOM Worker" 0xb7fe1422 in 
__kernel_vsyscall ()
  16   Thread 0xaa8ffb70 (LWP 8269) "HTML5 Parser" 0xb7fe1422 in 
__kernel_vsyscall ()
  15   Thread 0xab3ffb70 (LWP 8266) "iceweasel" 0xb7fe1422 in __kernel_vsyscall 
()
  14   Thread 0xab8ffb70 (LWP 8265) "DOM Worker" 0xb7fb7a2a in 
pthread_cond_signal@@GLIBC_2.3.2 () from 
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0
  13   Thread 0xac2ffb70 (LWP 8264) "mozStorage #1" 0xb7fe1422 in 
__kernel_vsyscall ()
  12   Thread 0xac8ffb70 (LWP 8263) "DOM Worker" 0xb7fe1422 in 
__kernel_vsyscall ()
  10   Thread 0xaddffb70 (LWP 8261) "Cert Verify" 0xb7fe1422 in 
__kernel_vsyscall ()
  9Thread 0xae8ffb70 (LWP 8260) "Timer" 0xb7fe1422 in __kernel_vsyscall ()
  8Thread 0xb0a70b70 (LWP 8259) "Cache2 I/O" 0xb7fe1422 in 
__kernel_vsyscall ()
  7Thread 0xaf4ffb70 (LWP 8258) "Hang Monitor" 0xb7fe1422 in 
__kernel_vsyscall ()
  6Thread 0xb00feb70 (LWP 8257) "JS Watchdog" 0xb7fe1422 in 
__kernel_vsyscall ()
  5Thread 0xb08ffb70 (LWP 8256) "JS GC Helper" 0xb7fe1422 in 
__kernel_vsyscall ()
  4Thread 0xb12ffb70 (LWP 8255) "Socket Thread" 0xb7fe1422 in 
__kernel_vsyscall ()
  3Thread 0xb2da1b70 (LWP 8254) "Gecko_IOThread" 0xb7fe1422 in 
__kernel_vsyscall ()
* 1Thread 0xb7d096e0 (LWP 8242) "iceweasel" 0xae0466f1 in ?? ()
(gdb) print JSC::MacroAssemblerX86Common::s_sseCheckState
$1 = JSC::MacroAssemblerX86Common::HasSSE3


-- 
Ondrej Zary


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

Bug#769042: xserver-xorg-video-geode: missing Provides: xorg-driver-video

[Martin-Éric Racine]

Package: xserver-xorg-video-geode
Version: 2.11.16-4
Severity: important

Spotted while testing an upgrade from Wheezy to Jessie:

2.11.16-4 mistakenly dropped a (Provides: xorg-driver-video). Without it, on 
hosts without any other X.Org video driver installed, this results in an APT
decision to remove the whole X.Org stack and most desktop applications.

Fixing this simply require putting the Provides back into debian/control.


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

Bug#767457: Error creating partition

[Michael Gilbert]

> [...]
> Error creating partition
> Error wiping newly created partition /dev/sdf1: Command-line `wipefs
> -a "/dev/sdf1"' exited with non-zero exit status 1: wipefs: error:
> /dev/sdf1: probing initialization failed: No such file or directory
>  (udisks-error-quark, 0)
> [...]

I ran into the exact same problem just now creating a new partition on
a hard drive, probably a race condition.  It likely needs a loop
waiting for the new partition to really be available.

Found an easy enough workaround, run the suggested wipefs command
manually, then reopen gnome-disks.

Best wishes,
Mike


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

Bug#761986: Me too!

[Henrik Sandklef]

Can you run the same command you had problem with:

  cnee --record --mouse -o /tmp/xnee.xns --first-last --smp

and use a mouse instead of the Touchpad. This is really not likely the
cause, but I would like to make sure.

/h




On Thu, Nov 06, 2014 at 01:27:58PM -0800, Dima Kogan wrote:
> Henrik Sandklef  writes:
> 
> > How about your input devices, can you list them?
> >   You can use xinput (with no args).
> 
> Hi. I'm attaching a recorded file that has some mouse motion. I start in
> one corner, then move to the middle and trace out a star. You can see
> the path with this:
> 
>  awk -F, '$2==6 {print $3,$4}' /tmp/xnee.xns | feedgnuplot --lines --points 
> --domain
> 
> On my box, replaying with
> 
>  cnee --force-core-replay --replay -f /tmp/xnee.xns
> 
> works, but omitting the --force-core-replay has the behavior described
> earlier: cursor moves to the top-left and insists on staying there.
> 
> xinput output:
> 
>   ⎡ Virtual core pointer  id=2[master pointer  
> (3)]
>   ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  
> (2)]
>   ⎜   ↳ Synaptics Touchpadid=7[slave  pointer  
> (2)]
>   ⎜   ↳ trackpointid=8[slave  pointer  
> (2)]
>   ⎜   ↳ Logitech USB Receiver id=16   [slave  pointer  
> (2)]
>   ⎣ Virtual core keyboard id=3[master keyboard 
> (2)]
>   ↳ Virtual core XTEST keyboard   id=5[slave  keyboard 
> (3)]
>   ↳ Generic Keyboard  id=6[slave  keyboard 
> (3)]
>   ↳ Power Button  id=9[slave  keyboard 
> (3)]
>   ↳ Video Bus id=10   [slave  keyboard 
> (3)]
>   ↳ Sleep Button  id=11   [slave  keyboard 
> (3)]
>   ↳ ThinkPad Extra Buttonsid=12   [slave  keyboard 
> (3)]
>   ↳ ACPI Virtual Keyboard Device  id=13   [slave  keyboard 
> (3)]
>   ↳   USB Keyboardid=14   [slave  keyboard 
> (3)]
>   ↳   USB Keyboardid=15   [slave  keyboard 
> (3)]
>   ↳ Logitech USB Receiver id=17   [slave  keyboard 
> (3)]
> 
> 
> I have an /etc/X11/xorg.conf. Relevant pieces:
> 
> Section "ServerLayout"
> Identifier "Default Layout"
> InputDevice"Generic Keyboard"
> InputDevice"Synaptics Touchpad"
> InputDevice"trackpoint"
> EndSection
> 
> Section "InputDevice"
> Identifier  "trackpoint"
> Option  "Device" 
> "/dev/input/by-path/platform-i8042-serio-2-event-mouse"
> Driver  "evdev"
> Option  "Protocol" "ImPS/2"
> Option  "Emulate3Buttons" "false"
> Option  "EmulateWheel" "true"
> Option  "EmulateWheelTimeOut" "0"
> Option  "EmulateWheelButton" "0"
> Option  "EmulateWheelInertia" "10"
> Option  "XAxisMapping" "6 7"
> Option  "ZAxisMapping" "4 5"
> Option  "YAxisMapping" "4 5"
> EndSection
> 
> Section "InputDevice"
> Identifier  "Synaptics Touchpad"
> Driver  "synaptics"
> Option  "Device" 
> "/dev/input/by-path/platform-i8042-serio-1-event-mouse"
> Option  "HorizScrollDelta" "60"
> Option  "HorizEdgeScroll" "1"
> Option  "VertEdgeScroll"  "1"
> Option  "EmulateMidButtonTime" "0"
> Option  "VertTwoFingerScroll" "0"
> Option  "SHMConfig" "on"
> Option  "RTCornerButton" "4"
> Option  "RBCornerButton" "5"
> Option  "LTCornerButton" "0"
> Option  "LBCornerButton" "0"
> Option  "TapButton1" "1"
> Option  "TapButton2" "0"
> Option  "TapButton3" "0"
> Option  "Emulate3Buttons" "0"
> Option  "MinSpeed" "0.3"
> Option  "MaxSpeed" "0.4"
> Option  "AccelFactor" "0.5"
> EndSection
> 
> 
> 
> None of that looks particularly noteworthy to me, but I'm no expert.
> 


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

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

[Yaroslav Halchenko]

On Mon, 10 Nov 2014, Andreas Tille wrote:

> On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote:
> > amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a
> > bug fix so we could demand unblock for this one

> I'll take the bet that this will fail.  I personally would not try to
> stress test the patience of the release team. ;-)

well -- the changes are indeed miniscule (if I got it right) and just a
bugfix anyways I guess -- I bet RT can swallow this one

$> git diff v0.8.4..v0.8.6   
diff --git a/MANIFEST.in b/MANIFEST.in
index e2b071e..6e868f4 100644
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -9,7 +9,12 @@ recursive-include mne/data *.sel
 recursive-include mne/data *.fif.gz
 recursive-include mne/layouts *.lout
 recursive-include mne/layouts *.lay
+recursive-include mne/html *.js
+recursive-include mne/html *.css
 recursive-exclude examples/MNE-sample-data *
+recursive-exclude examples/MNE-testing-data *
+recursive-exclude examples/MNE-spm-face *
+recursive-exclude examples/MNE-somato-data *
 # recursive-include mne/fiff/tests/data *
 recursive-exclude mne/fiff/tests/data *
 recursive-exclude mne/fiff/bti/tests/data *
diff --git a/doc/source/whats_new.rst b/doc/source/whats_new.rst
index 0f31d17..23919c5 100644
--- a/doc/source/whats_new.rst
+++ b/doc/source/whats_new.rst
@@ -143,7 +143,7 @@ API
 
- Deprecate Epochs.drop_picks in favor of a new method called drop_channels
 
-   - Deprecate `labels_from_parc` and `parc_from_labels` in favor of 
`read_annot` and `write_annot`
+   - Deprecate `labels_from_parc` and `parc_from_labels` in favor of 
`read_labels_from_annot` and `write_labels_to_annot`
 
- The default of the new add_dist option of `setup_source_space` to add 
patch information will change from False to True in MNE-Python 0.9
 
diff --git a/mne/__init__.py b/mne/__init__.py
index 0b90048..2ae0043 100644
--- a/mne/__init__.py
+++ b/mne/__init__.py
@@ -1,7 +1,7 @@
 """MNE for MEG and EEG data analysis
 """
 
-__version__ = '0.8.4'
+__version__ = '0.8.6'
 
 # have to import verbose first since it's needed by many things
 from .utils import (set_log_level, set_log_file, verbose, set_config,
diff --git a/mne/coreg.py b/mne/coreg.py
index ce634e1..2461380 100644
--- a/mne/coreg.py
+++ b/mne/coreg.py
@@ -1150,6 +1150,7 @@ def scale_source_space(subject_to, src_name, 
subject_from=None, scale=None,
 
 if add_dist:
 logger.info("Recomputing distances, this might take a while")
-add_source_space_distances(sss, sss[0]['dist_limit'], n_jobs)
+dist_limit = np.asscalar(sss[0]['dist_limit'])
+add_source_space_distances(sss, dist_limit, n_jobs)
 
 write_source_spaces(dst, sss)




-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


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

Bug#759960: libcatalyst-engine-psgi-perl: FTBFS: dh_auto_test: make -j1 test returned exit code 2

[gregor herrmann]

On Sun, 09 Nov 2014 18:45:25 +, Simon McVittie wrote:

> On Sat, 25 Oct 2014 at 20:04:19 +0200, gregor herrmann wrote:
> > libmojomojo-perl uploaded with the patch and without the dependency
> > on libcatalyst-engine-psgi-perl, so the latter can be removed from
> > testing (and the archive).
> Any objection to an RM:RoQA bug asking for libcatalyst-engine-psgi-perl
> to be removed from unstable?

Not at all, please feel free to go ahead, and thanks for your help.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#768904: gnus: Fails to start, “Cannot open load file: no such file or directory, image”

[Ben Finney]

package emacs24-common
tags 768904 + patch upstream
thanks

On 10-Nov-2014, Rob Browning wrote:
> Rob Browning  writes:
> > Aha?
> >   http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18813
> 
> And if that is the cause, perhaps this will fix it:
> 
> --- a/lisp/gnus.el
> +++ b/lisp/gnus.el
> @@ -327,7 +327,8 @@ be set in `.emacs' instead."
>(defun gnus-mode-line-buffer-identification (line)
>   (let ((str (car-safe line))
> (load-path (append (mm-image-load-path) load-path)))
> -   (if (and (stringp str)
> +   (if (and (display-graphic-p)
> +(stringp str)
>  (string-match "^Gnus:" str))
> (progn (add-text-properties
> 0 5
> 
> If you're comfortable editing
> /usr/share/emacs/24.4/lisp/gnus/gnus.el.gz. to add that
> "(display-graphic-p)" test, please let me know if it helps.

I saved a modified version to my ‘$HOME/.emacs.d/lib/’ directory,
byte-compiled it, and now:

$ emacs -f gnus

starts successfully and runs normally.

This works around the issue for me; I can leave that file in my
customisation directory, and wait for Debian's Emacs to gain the patch.

-- 
 \   “Anyone who puts a small gloss on [a] fundamental technology, |
  `\  calls it proprietary, and then tries to keep others from |
_o__)   building on it, is a thief.” —Tim O'Reilly, 2000-01-25 |
Ben Finney 


signature.asc
Description: Digital signature

Bug#768843: fetchmail: Improved TLS support

[Matthias Andree]

Am 09.11.2014 um 17:02 schrieb Kurt Roeckx:
> Package: fetchmail
> Tags: patch
> 
> Hi,
> 
> The attached patch improves fethcmail SSL/TLS support.  It seems
> to have some misunderstandings of openssl / SSL / TLS.

Dear Kurt,

thank you very much for spending time on this matter.

What you are writing is generally correct (while I have not audited your
patch in minute detail).

The SSL support patches that went into fetchmail years ago, from various
authors, in various stages, are flakey and used to be incomplete in
older versions.  Some of that was due to the very scattered and
incomplete SSL documentation in general.

Some of the original contributors mingled SSL/TLS versions with the
point in time when negotiation takes place: up front
("SSL/TLS-wrapped"), or in-band after STLS/STARTTLS, or not at all.

The option set fetchmail offers is awkward in 6.x.  Sorting this out,
however, isn't easily done without breaking existing semantics.  While I
appreciate very much that your change also affects documentation, I fear
the patch is inacceptable for stable releases.  (About future releases,
please see the end of this message.)

> First, STARTTLS should work with both SSL and TLS, not just from
> TLS 1.0.  The TLS in STARTTLS does not mean it's TLS only, TLS is
> just a different name for SSL.

I understand that, the original contributors did not.  (Technically, TLS
1.0 is SSL v3.1, TLS 1.1 SSL v3.2, TLS 1.2 SSL v3.3 during handshakes,
for instance.)

> It also still seems to think only TLS 1.0 is supported while there
> are more recent versions, and it encourages SSL3 because SSL2 is
> broken.

True.

> I've also changed the way in which opportunistic TLS works a
> little.  It seems to have only done this with TLS1 for the above
> stated reasons which were wrong.
> 
> This patch results in the following changes with a server support
> STARTTLS:
>   | --ssl | no option | sslproto ssl23| sslproto tls1
> Old:  | TLS 1.2   | TLS1.0| not working   | TLS1.0
> New:  | TLS 1.2   | TLS1.2| TLS1.2| TLS1.0
> 
> The "sslproto ssl23" case just send logout, I assume because
> maybe_tls returns false.
> 
> This started by making the call to SSLv3_client_method() optional
> in case openssl doesn't support it.

I am not sure I understand the last two phrases.  The next-to-last is
probably a matter of reading code and perhaps debugging (also your later
sslproto "" behaving differently than an omitted sslproto option - this
may have to do with automated repolls for opportunistic TLS).

I am rather loathe to propose/endorse/support changing option semantics
for a stable release; we'd probably need to add new switches.

Please have a look at the current state of fetchmail's "master" (note:
it is non-default, so you'll need to "git checkout master" after
cloning) branch in Git, either here
 or here:


and let me know what you think of the --sslmode and --sslproto as you've
found, if documentation is missing or inaccurate.  I would personally
prefer discussion through the fetchmail-devel@ mailing list (which has
public archives, but requires subscrption), but if you can't be
bothered, the Debian BTS will be better than no feedback.

We should then see if we want to backport that without the
obsolete-options-warnings (but perhaps with an --ssl-newstyle option
required to switch semantics) or if we leave that for 7.x.

Thank you very much.

Best regards,
Matthias


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

Bug#764904: apophenia: FTBFS - test suite times out or has unexpected failures

[Edmund Grimley Evans]

By the way, it might be a good idea to remove the ">/dev/null 2>&1"
from the command lines in case the compiler wants to warn you about
this sort of thing. (I don't know whether GCC does in this particular
case.)


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

Bug#768942: Description of python-rudolf

[Thomas Goirand]

On 11/11/2014 02:21 AM, W. Martin Borgert wrote:
> I wonder, whether this sentence is helpful:
> 
>> It only works on Unix-like systems, as it uses ANSI colour codes.
> 
> But this is a Debian package and no Debian GNU/Windows in sight :~) Maybe:
> 
>> It only works on ANSI-compatible terminals, as it uses ANSI colour codes.
> 
> Cheers

Hi,

Unfortunately, Debian isn't the only system in the world. I think it's
important for someone to know that a given python module wont work on
Windows. Or at least, I have no problem to do a cut/past from upstream
if he/she wants to say that in the long description.

Cheers,

Thomas


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

Bug#768140: torsocks: FTBFS on kfreebsd-*

[intrigeri]

Hi,

David Goulet wrote (10 Nov 2014 18:52:09 GMT) :
> Please see top commit that fixes that:

Cherry-picked, uploaded. Thanks!


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

Bug#768292: Let's add the MPLs to /usr/share/common-licenses ? (was Re: Bug#768292: debian-policy: please allow copyright file to refer to license text in separate files)

[Charles Plessy]

Le Sun, Nov 09, 2014 at 09:13:21AM -0800, Russ Allbery a écrit :
> 
> > How about adding both MPLs to /usr/share/common-licenses ?
> 
> Given those numbers, I think we should.  And possibly also CC-BY-SA 3.0
> while we're at it.

Hi Russ,

I fully agree.

For the avoidance of doubt, I have also counted the numbers for other CC
licenses; here is the result.

AGPL 3  294
Apache 2.0 4740
Artistic   3811
Artistic 2.0195
BSD (common-licenses)   347
CC-BY 1.011
CC-BY 2.0 1
CC-BY 2.533
CC-BY 3.0   311
CC-BY-SA 1.0  2
CC-BY-SA 2.0 32
CC-BY-SA 2.5 16
CC-BY-SA 3.0883
CC-BY-SA 4.0 23
CDDL504
CeCILL   54
CeCILL-B 50
CeCILL-C 33
GFDL (any) 2155
GFDL (symlink)  539
GFDL 1.2   1074
GFDL 1.3619
GPL (any) 40659
GPL (symlink)  7641
GPL 1  3657
GPL 2 25546
GPL 3 11363
LGPL (any)18315
LGPL (symlink) 2466
LGPL 214666
LGPL 2.1  10422
LGPL 3 2644
LaTeX PPL76
LaTeX PPL (any) 197
LaTeX PPL 1.3c  184
MPL 1.11146
MPL 2.0 847
SIL OFL 1.0  13
SIL OFL 1.1 567

Total number of packages: 73292

By the way, would you and the other Policy editors mind if I would save these
numbers in the Git repository, for insance in a text file named
tools/license-check.latest.txt ?  This way, it will be easier to keep an eye
on the evolution of these numbers.

As far as I could see with search engine, the previous number for MPL-1.1 was
740.

https://lists.debian.org/debian-policy/2011/12/msg00130.html

For the CC licenses, it was:

CC-BY 3.068
CC-BY-SA 3.0133

https://bugs.debian.org/662649#31

Before taking final action, shall we consider adding also CC-BY 3.0 (not as
popular as the SA variant, but this may avoid some errors), and the 4.0 version
of the licenses ?

The rationale for using the 4.0 version is that if their use increases like for
the 3.0 versions (and I would be surprised if not), then waiting to add them to
/usr/share/common-licenses is giving double work to the maintainers: first they
have to include them in debian/copyright, and then they will have to remove
them.  This said, I do not have a strong opinion.

Once this is discussed, I will propose a patch to the Policy.  After it is 
properly
seconded, I will ping the Lintian maintainers (please remind me if I forget).

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


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

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

[Andreas Tille]

On Mon, Nov 10, 2014 at 05:48:32PM +0100, Alexandre Gramfort wrote:
> hi,
> 
> ok but the current master branch on debian.org is at version 0.8.6.
> 
> I doubt I should make changes their for version 0.8.4 no?

Just create a branch named jessie starting from 0.8.4.  Unfortunately
your sponsor has ignored the rules for freeze where you should upload to
experimental and not to unstable.  Please sort this out with your
sponsor - he should know what to do.  I'll be on vacation soon and have
no time at all to fiddle around with this.
 
> these 3 tests
> 
> > test_legendre_val
> > test_legendre_table
> > test_make_field_map_meg
> 
> should be deleted by the patch.

So just do it.

Kind regards

  Andreas.

-- 
http://fam-tille.de


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

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

[Andreas Tille]

On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote:
> amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a
> bug fix so we could demand unblock for this one

I'll take the bet that this will fail.  I personally would not try to
stress test the patience of the release team. ;-)
 
Kind regards

Andreas.

-- 
http://fam-tille.de


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

Bug#768910: Missed one timer arg

[Peter Chubb]

If wl-biff-use-idle-timer is non-nil, there's another place that needs
to be switched from a bool to an integer.

Updated patch attached.

--- wl-beta-2.15.9+0.20141019/wl/wl-util.el 2014-10-19 19:07:15.0 
+1100
+++ wl-beta-fixed/wl/wl-util.el 2014-11-11 08:52:13.764418131 +1100
@@ -774,11 +774,11 @@
   (if wl-biff-use-idle-timer
  (if (get 'wl-biff 'timer)
  (progn (timer-set-idle-time (get 'wl-biff 'timer)
- wl-biff-check-interval t)
+ wl-biff-check-interval 
wl-biff-check-interval)
 (timer-activate-when-idle (get 'wl-biff 'timer)))
(put 'wl-biff 'timer
 (run-with-idle-timer
- wl-biff-check-interval t 'wl-biff-event-handler)))
+ wl-biff-check-interval wl-biff-check-interval 
'wl-biff-event-handler)))
(if (get 'wl-biff 'timer)
(progn
  (timer-set-time (get 'wl-biff 'timer)

-- 
Dr Peter Chubb  peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au  Software Systems Research Group/NICTA


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

Bug#601757: Please mount cgroup automatically

[John Paul Adrian Glaubitz]

Hello Ritesh!

May I ask why you set the severity to "grave"? As far as I know,
Debian Jessie is going to be released with systemd as the default
init for all release architectures to which kfreebsd-* does not
belong to.

I don't think that this bug is going to be fixed any time soon
if the sysvinit maintainers didn't bother enough to fix it
the past three years.

Adrian

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


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

Bug#769041: RM: postgresql-pljava -- ROM; RoM: upstream mostly dead, and doesn't work with 9.4

[Christoph Berg]

Package: ftp.debian.org
Severity: normal

Hi,

please remove postgresql-pljava. Upstream isn't really active, they
haven't even ported the code to PostgreSQL 9.3, and the last release
has been years ago.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature

Bug#769040: RFP: minimap-el -- Minimap sidebar for Emacs

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

Package name: minimap-el
Version : 0.1
Upstream Author : Dustin Lacewell 
URL : https://github.com/dustinlacewell/emacs-minimap
License : GPL2+
Programming Lang: Emacs Lisp
Description : Minimap sidebar for Emacs

Minimap is an implementation of a minimap sidebar, i.e., a
smaller display of the current buffer on the left side. It
highlights the currently shown region and updates its position
automatically. You can navigate in the minibar by dragging the
active region with the mouse, which will scroll the corresponding
edit buffer.


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

Bug#768360: iceweasel: crashes with Illegal instruction at startup

[Mike Hommey]

On Mon, Nov 10, 2014 at 09:25:50PM +0100, Ondrej Zary wrote:
> On Monday 10 November 2014 06:03:04 Mike Hommey wrote:
> > On Sun, Nov 09, 2014 at 08:30:58AM +0900, Mike Hommey wrote:
> > > Okay, so despite all the changes in the related code, this was not
> > > fixed. I now need to know if this is a bug in cpu detection or in the
> > > code deciding what to JIT features to enabled based on the cpu
> > > detection.
> > >
> > > In gdb, after the crash, with version 31, could you report what the
> > > following command prints out?
> > >
> > > gdb> print JSC::MacroAssemblerX86Common::s_sseCheckState
> 
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread 0xac4ffb70 (LWP 6778)]
> 0xac620722 in ?? ()
> (gdb) print JSC::MacroAssemblerX86Common::s_sseCheckState
> No type "MacroAssemblerX86Common" within class or namespace "JSC".

Did you run this on version 31?

Mike


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

Bug#764904: apophenia: FTBFS - test suite times out or has unexpected failures

[Edmund Grimley Evans]

>From the buildd logs it appears that the tests are timing out.

A quick look at apop_conversions.c suggests a plausible explanation.

In that file there is code like this:

char c = fgetc(infile);
...
while(c!='\n' && c !=EOF){

EOF is negative, and plain char is unsigned on ARM architectures, so
c !=EOF will always be true.

Every use of EOF in that file seems to suffer from the same problem.

The fragment above could probably be fixed just by changing "char" to
"int". In other places the fix is less trivial because the code is
trying to store EOF into an array of char, for example.

This might explain the test failures: it spins forever reading EOF but
not recognising it as EOF.


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

Bug#765272: [Pkg-xfce-devel] Bug#765272: xfce4-notes-plugin: run dh-autoreconf to update for new architectures

[Yves-Alexis Perez]

On lun., 2014-11-10 at 21:43 +, peter green wrote:
> Yves-Alexis Perez wrote:
> 
> >> Since we are now post-freeze bugs should be fixed in a minimal way
> >> and 
> >> as such adding an autoreconf at this point would be frowned upon. As 
> >> such for jessie I propose using the autotools_dev feature in dh to 
> >> update config.sub and config.guess without autoreconfing.
> >> 
> >
> > Are you sure that's ok for the release team?
> My understanding is that updating config.sub/guess is ok, autoreconf is 
> generally frowned upon but if you want to be sure then feel free to file 
> a "pre-approval" unblock request.

I kind of hope you would have done that yourself, actually…
> 
> > Well, if your only goal is to have xfce4-goodies installable I could
> > also upload an xfce4-goodies with notes-plugin removed on arm64…
> I'd kinda consider that approach as a last resort. As far as possible we 
> should be trying to give a consistent experiance across architectures.

It was not really a serious proposal :)

Regards,
-- 
Yves-Alexis


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