Bug#779573: bibtool: heap buffer overflow in the bibtool tests

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello All,

I have just deposited a minimal fix at Alioth (unstable/master branch).

Thanks for the reports, the patches, and the comments.

Jerome 

On 03/03/15 16:48, Moritz Muehlenhoff wrote:
> On Tue, Mar 03, 2015 at 08:13:12AM +0100, Jerome BENOIT wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello All,
>>
>> The patch was committed by the upstream maintainer [1].
>> He is also currently working on the print issue.
>> Once solved, he may release a new version for BibTool.
>>
>> On the other hand, the bug was downgraded from RC to Grave.
>>
>> I will package this new version in due time in experiment.
>>
>> My question is: may I patch the bibtool debian package 2.57+ds-2 and put it 
>> in unstable ?
> 
> Yes, if you upload the fix to unstable it will most likely be unblocked
> by the release managers.
> 
> Cheers,
> Moritz
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJU9ro7AAoJEIC/w4IMSybj60oH/1f5xfaampdw8iCe7DSBWHB6
eiq1UdMu3NySJb7E5h7fChSRZxa8Z4IjfOxU4crAbYoEo6nUpPP0nGI6gWzOQSYh
3+Rcm5CK5bSwsqhrDrHVCeBV3YiboB+UU4HIKeC6qeOaRJQh+mJhCbIEUm6zBKYO
mpcUEhhiH/frScm4W3inxoGEQjBhUwhXqDJ0sqB9QM+PoKrSFsD+t+i8BpjoT4yM
/k2i5Ni+65JrcG3tG8Zgcsz3xG8oM48nGDT0ZKGXHdYl/LmqXnnCeu8GbwvjtEWQ
WR8M9K2z638N2sVPBfDmEF5gdFHk6+fbB7DxQaLVPh6cBP1oqGnD3swpd43ICFM=
=1ZoT
-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#779421: RM: python-oauth2 -- RC-buggy; abandoned upstream

[Jörg Frings-Fürst]

Hello Scott,

first thanks for your work.

Please can you remove python-oauth2 from stable, too?

It's the same bubby version as in unstable.


Am Samstag, den 28.02.2015, 11:13 -0500 schrieb Scott Kitterman:
> Please file removal bugs (one per package) for the other packages that also 
> should be removed.
> 
[...]


CU
Jörg

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

Old pgp Key: BE581B6E (revoked since 2014-12-31).

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

Threema: SYR8SJXB

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

My wish list: 
 - Please send me a picture from the nature at your home.




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

Bug#779613: "no such file or directory" trying to connect through the blueman-applet

[Christopher Schramm]

>> Anyway, connecting to a NAP should work. You just have to select the
>> service from the device menu and not use the generic connect item for that.
> 
> There's no service from the menu, in fact, the "Serial server" menu item
> is gone.

So you are talking about a serial service, not a NAP service. Support
for serial services with BlueZ 5 is not available in the alpha1
snapshot, but recently made it into current upstream master. I'm
actually planning to do an alpha2 snapshot release and package it for
unstable or experimental at the end of the week.


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

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Stéphane Fillion]

On 2015-03-04 02:11, Sebastiaan Couwenberg wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 03/04/2015 07:53 AM, Ross Gammon wrote:

On 03/03/2015 09:33 PM, Sebastiaan Couwenberg wrote:

* Remove async.js and use packaged version instead

This looks a lintian false positive, the async.js in bluebird is
quite different from the node-async one.

Compare:

http://anonscm.debian.org/cgit/pkg-javascript/node-async.git/tree/lib/async.js




http://anonscm.debian.org/cgit/pkg-javascript/node-bluebird.git/tree/src/async.js

I think reverting this change and adding a lintian override
instead is a better idea.

Whoops - I should of checked that. I was in a hurry to finish -
that is never a good thing. I have a few family commitments
tonight, but after that I will fix.

There is no hurry getting the the openlayers dependency tree packaged,
there is a lot of work to do which will take quite some time and
that's not a problem. Remember: Good things come to those who wait. :-)

Kind Regards,

Bas

- -- 
  GPG Key ID: 4096R/6750F10AE88D4AF1

Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJU9rAVAAoJEGdQ8QrojUrx5PIQAK8ZtMnv24NhhSBc6EuG63TI
ckEUJkdAi+8mBCNH/W2YS8mgs2p4KOSx5OCMl/fAHidEd4NRPGxbzxY0D7dxLVGr
e3zLhl2XpKfTXxB8lXyjCFhbrt3y+BNdRH8JJKt0WfGrz3lkp9XtI0L9B/vbZ/uZ
vNXVNeQUPcz1xZcAJlVv8LOnqnsj9pj/5sqSKsd2z4bcyh4dhxUjhuqDhjErzJS4
eqAzMJPzl6FavdU+pbGyeGGxpCGjyK9zte3VW1E1xgd30OKoTRbzV+LkmY2s02qG
lj9rcgf+PTYE391CETDTzpVg5t/RfnoAc7O/YIORfVFehor3aUDVOdiXz0HhN6B6
KTsd/WNO/JzAbNvpkGIrTzuXz0AOz8At6Cnz8BEm8v1hcWaoHyRPdO8fGbNvD8Tl
yejmCAUDsbbZfPQzZ21Di9lRalD02mKSqS37d0X7xnJPvNRrKBQYwuB3v51Cnjey
EOzA/QMCv6JXv/29YooR6L2WnwuhIADy4CXBgZyo2MIQkzwBoAfUB1VIDNmkm53V
0DkgnQIZ5R3mKPrRHSFJzNPRAEyaa0halFYWlGk5LqK0d7xBRGWM/BdMll3mH4hP
0AsOy0cwL54tvGABfAm7C/xK2MgV6yudDMJkXORWv1oG0v5HEX0zF7L+bv7zK8ch
91LPdA2FU3j7rKIlNS/2
=adMa
-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#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Sebastiaan Couwenberg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 03/04/2015 07:53 AM, Ross Gammon wrote:
> On 03/03/2015 09:33 PM, Sebastiaan Couwenberg wrote:
>>> * Remove async.js and use packaged version instead
>> 
>> This looks a lintian false positive, the async.js in bluebird is
>> quite different from the node-async one.
>> 
>> Compare:
>> 
>> http://anonscm.debian.org/cgit/pkg-javascript/node-async.git/tree/lib/async.js
>>
>>
>> 
http://anonscm.debian.org/cgit/pkg-javascript/node-bluebird.git/tree/src/async.js
>> 
>> I think reverting this change and adding a lintian override
>> instead is a better idea.
> 
> Whoops - I should of checked that. I was in a hurry to finish -
> that is never a good thing. I have a few family commitments
> tonight, but after that I will fix.

There is no hurry getting the the openlayers dependency tree packaged,
there is a lot of work to do which will take quite some time and
that's not a problem. Remember: Good things come to those who wait. :-)

Kind Regards,

Bas

- -- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJU9rAVAAoJEGdQ8QrojUrx5PIQAK8ZtMnv24NhhSBc6EuG63TI
ckEUJkdAi+8mBCNH/W2YS8mgs2p4KOSx5OCMl/fAHidEd4NRPGxbzxY0D7dxLVGr
e3zLhl2XpKfTXxB8lXyjCFhbrt3y+BNdRH8JJKt0WfGrz3lkp9XtI0L9B/vbZ/uZ
vNXVNeQUPcz1xZcAJlVv8LOnqnsj9pj/5sqSKsd2z4bcyh4dhxUjhuqDhjErzJS4
eqAzMJPzl6FavdU+pbGyeGGxpCGjyK9zte3VW1E1xgd30OKoTRbzV+LkmY2s02qG
lj9rcgf+PTYE391CETDTzpVg5t/RfnoAc7O/YIORfVFehor3aUDVOdiXz0HhN6B6
KTsd/WNO/JzAbNvpkGIrTzuXz0AOz8At6Cnz8BEm8v1hcWaoHyRPdO8fGbNvD8Tl
yejmCAUDsbbZfPQzZ21Di9lRalD02mKSqS37d0X7xnJPvNRrKBQYwuB3v51Cnjey
EOzA/QMCv6JXv/29YooR6L2WnwuhIADy4CXBgZyo2MIQkzwBoAfUB1VIDNmkm53V
0DkgnQIZ5R3mKPrRHSFJzNPRAEyaa0halFYWlGk5LqK0d7xBRGWM/BdMll3mH4hP
0AsOy0cwL54tvGABfAm7C/xK2MgV6yudDMJkXORWv1oG0v5HEX0zF7L+bv7zK8ch
91LPdA2FU3j7rKIlNS/2
=adMa
-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#779698: linux-image-3.16.0-4-amd64: Please enable mcelog support under XEN

[Henrik Riomar]

Package: src:linux
Version: 3.16.7-ckt4-3
Severity: wishlist

Dear Maintainer,

It seems mcelog support when running under XEN (new feature in 3.6) is not
enabled in the Debian build.

Please consider enabling XEN_MCE_LOG in the Debian kernel.

Please note that mcelog works fine in Jessie when not running under xen
(from /var/log/mcelog):

Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 8
MISC 890a12240082 ADDR 10364c0
TIME 1425461644 Wed Mar  4 10:34:04 2015
MCG status:
MCi status:
Error overflow
Corrected error
MCi_MISC register valid
MCi_ADDR register valid
MCA: MEMORY CONTROLLER RD_CHANNELunspecified_ERR
Transaction: Memory read error
Memory read ECC error
Memory corrected error count (CORE_ERR_CNT): 39
Memory transaction Tracker ID (RTId): 82
Memory DIMM ID of error: 0
Memory channel ID of error: 1
Memory ECC syndrome: 890a1220
STATUS cc0009c1009f MCGSTATUS 0
MCGCAP 1c09 APICID 0 SOCKETID 0
CPUID Vendor Intel Family 6 Model 44

But when the Jessie kernel is running under XEN I get nothing in
/var/log/mcelog, but still see the memory errors in 'xl dmesg'.

Thanks,
 Henrik

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03)

** Command line:
  n/a

** Not tainted

** Kernel log:
  n/a

** Model information
not available

** Loaded modules:
  n/a

** PCI devices:

** USB devices:
not available


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

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

Versions of packages linux-image-3.16.0-4-amd64 depends on:
ii  debconf [debconf-2.0]   1.5.55
ii  initramfs-tools [linux-initramfs-tool]  0.116
ii  kmod18-3
ii  linux-base  3.5
ii  module-init-tools   18-3

Versions of packages linux-image-3.16.0-4-amd64 recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3

Versions of packages linux-image-3.16.0-4-amd64 suggests:
pn  debian-kernel-handbook 
pn  grub-pc | grub-efi | extlinux  
pn  linux-doc-3.16 

Versions of packages linux-image-3.16.0-4-amd64 is related to:
pn  firmware-atheros   
pn  firmware-bnx2  
pn  firmware-bnx2x 
pn  firmware-brcm80211 
pn  firmware-intelwimax
pn  firmware-ipw2x00   
pn  firmware-ivtv  
pn  firmware-iwlwifi   
pn  firmware-libertas  
pn  firmware-linux 
pn  firmware-linux-nonfree 
pn  firmware-myricom   
pn  firmware-netxen
pn  firmware-qlogic
pn  firmware-ralink
pn  firmware-realtek   
ii  xen-hypervisor-4.4-amd64 [xen-hypervisor]  4.4.1-6

-- debconf information excluded

Bug#779687: libdevel-callchecker-perl: FTBFS on i386: DynaLoader bombs out

[Niko Tyni]

(technically, I think this isn't RC as the package never built on i386.)

On Tue, Mar 03, 2015 at 10:32:50PM -0500, Aaron M. Ucko wrote:
> Source: libdevel-callchecker-perl
> Version: 0.006-1
> Severity: serious
> Justification: fails to build from source
> 
> The automated build of libdevel-callchecker-perl failed (only) on
> i386 due to test suite errors (excerpted from
> https://buildd.debian.org/status/fetch.php?pkg=libdevel-callchecker-perl&arch=i386&ver=0.006-1&stamp=1425399391
>  ):
> 
>   cd . && ./Build test  --verbose 1
>   Can't use an undefined value as a subroutine reference at 
> /usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210.

This is a sign of ABI incompatibility between perl and the built XS
modules.  The build is not using $Config{ccflags} for some reason,
so it's missing -D_FILE_OFFSET_BITS=64 which affects the binary interface.

No time to look further right now, but hope this helps.
-- 
Niko Tyni   nt...@debian.org


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

Bug#779697: metacam: SIGBUS, Bus error at dataifdentry.cc

[Henri Salo]

Package: metacam
Version: 1.2-6
Severity: important
Tags: security

metacam crashes when using following example input file fuzzed with AFL
.

08cc3e8a67812d32d51c5aff70a10a77e4b73644  
/home/fgeek/security/afl-samples/metacam/afl-metacam-sample-003.jpg

Starting program: metacam afl-metacam-sample-003.jpg
File: afl-metacam-sample-003.jpg
WARNING: Unknown field type 58624
WARNING: Unknown field type 0
WARNING: Unknown field type 8241
WARNING: Unknown field type 9361
  Standard Fields ---

Program received signal SIGBUS, Bus error.
_DataIFDEntry::getSTRING (this=0x663380) at dataifdentry.cc:121
121 tmpbuf[value_count] = 0;

(gdb) bt
#0  _DataIFDEntry::getSTRING (this=0x663380) at dataifdentry.cc:121
#1  0x00417b68 in getSTRING (this=) at metatiff.h:411
#2  dpyString (ctx=..., name=0x45870c "Model", e=...) at dpyfuncs.cc:46
#3  0x0040ebe3 in displayTags (driver=driver@entry=0x661010, 
header=header@entry=0x4581e5 "Standard Fields", tag_map=..., known=, verbose=0) at metacam.cc:86
#4  0x004060bc in processFile (is=..., fname=, 
driver=0x661010) at metacam.cc:255
#5  main (argc=, argv=) at metacam.cc:359
#6  0x772d1ead in __libc_start_main (main=, 
argc=, ubp_av=, init=, 
fini=, rtld_fini=,
stack_end=0x7fffe4a8) at libc-start.c:244
#7  0x0040c271 in _start ()

(gdb) list
116 vector v;
117 if (getRawType() != tASCII) {return v;}
118 char tmpbuf[1024];
119 source.seek(offset);
120 source.getData((unsigned char *)tmpbuf, value_count);
121 tmpbuf[value_count] = 0;
122 v.push_back(string(tmpbuf));
123 return v;
124 }
125

-- 
Henri Salo


signature.asc
Description: Digital signature

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Ross Gammon]

On 03/03/2015 09:33 PM, Sebastiaan Couwenberg wrote:

>>   * Fix duplicate package descriptions
> 
> You may want to tweak these a bit to be more in line with other node-*
> and libjs-* packages.
> 
> See for example node-q:
> 
> http://anonscm.debian.org/cgit/pkg-javascript/node-q.git/tree/debian/control
> 
> And also what npm2deb generates.
> 
> I pushed a change with my suggested improvement.
> 

Changes looked good - will double check later tonight.

>>   * Remove async.js and use packaged version instead
> 
> This looks a lintian false positive, the async.js in bluebird is quite
> different from the node-async one.
> 
> Compare:
> 
> http://anonscm.debian.org/cgit/pkg-javascript/node-async.git/tree/lib/async.js
> 
> http://anonscm.debian.org/cgit/pkg-javascript/node-bluebird.git/tree/src/async.js
> 
> I think reverting this change and adding a lintian override instead is a
> better idea.

Whoops - I should of checked that. I was in a hurry to finish - that is
never a good thing. I have a few family commitments tonight, but after
that I will fix.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#779696: metacam: segmentation fault at getRATIONAL dpyfuncs.cc:938

[Henri Salo]

Package: metacam
Version: 1.2-6
Severity: important
Tags: security

metacam crashes when using following example input file fuzzed with AFL
.

727e57e1d8f6a88bdefee47198ff8ab94fe2e1dc  afl-metacam-sample-002.jpg

Starting program: metacam afl-metacam-sample-002.jpg
File: afl-metacam-sample-002.jpg
  Standard Fields ---
Make: EASTMAN KODAK COMPANY
   Model: KODAK CX4200 DIGITAL CAMERA
Software Version: Ver�on 1.0100
X Resolution: 230 Pixels/Inch
Y Resolution: 230 Pixels/Inch
 Bits Per Sample: (1)
   YCbCr Positioning: Datum Point
WARNING: Unknown field type 65535
WARNING: Unknown field type 65535
WARNING: Unknown field type 37
WARNING: Unknown field type 136
WARNING: Unknown field type 144
WARNING: Unknown field type 12432
WARNING: Unknown field type 5264
WARNING: Unknown field type 10385
WARNING: Unknown field type 145
WARNING: Unknown field type 19602
WARNING: Unknown field type 21650
WARNING: Unknown field type 23698
WARNING: Unknown field type 25746
WARNING: Unknown field type 27794
WARNING: Unknown field type 146
WARNING: Unknown field type 146
WARNING: Unknown field type 29842
WARNING: Unknown field type 25
  EXIF Fields ---
   Exposure Time: 35882743/38096943 Sec.
Aperture: f59.3514
Exif Image Width: 1705168 pixels
   Exif Image Height: 1632 pixels
   Exposure Mode: Auto Exposure
   White Balance: Auto White Balance
  Sensing Method: Single Chip Color Area Sensor
  ColorSpace: sRGB

Program received signal SIGSEGV, Segmentation fault.
getRATIONAL (this=) at dpyfuncs.cc:938
938 }

(gdb) bt
#0  getRATIONAL (this=) at dpyfuncs.cc:938
#1  dpyRationalAsDouble (ctx=..., name=, e=..., units=0x0) at 
dpyfuncs.cc:346
#2  0x0040ebe3 in displayTags (driver=driver@entry=0x661010, 
header=header@entry=0x45820d "EXIF Fields", tag_map=..., known=, 
verbose=0) at metacam.cc:86
#3  0x0040742f in processFile (is=..., fname=, 
driver=0x661010) at metacam.cc:296
#4  main (argc=, argv=) at metacam.cc:359
#5  0x772d1ead in __libc_start_main (main=, 
argc=, ubp_av=, init=, 
fini=, rtld_fini=,
stack_end=0x7fffe4b8) at libc-start.c:244
#6  0x0040c271 in _start ()

(gdb) list
933   17 42 33 43 06 - ?? only on D ??
934   00 00 00 00 00 02 02 - ?? don't know ?? constant
935
936 */
937
938 }

-- 
Henri Salo


signature.asc
Description: Digital signature

Bug#779695: metacam: segmentation fault in tiffRATIONAL::normalize at rationals.cc:40

[Henri Salo]

Package: metacam
Version: 1.2-6
Severity: important
Tags: security

metacam crashes when using following example input file fuzzed with AFL
.

5d4c287cf40b73d2a5aac8b4a7367564ce823937  afl-metacam-sample-001.jpg

Starting program: metacam afl-metacam-sample-001.jpg
File: afl-metacam-sample-001.jpg
WARNING: Unknown field type 0
WARNING: Unknown field type 0
  Standard Fields ---

Program received signal SIGSEGV, Segmentation fault.
tiffRATIONAL::normalize (this=0x0) at rationals.cc:40
40  if ((num == 0) || (den == 0)) return *this;

(gdb) bt
#0  tiffRATIONAL::normalize (this=0x0) at rationals.cc:40
#1  0x00421bf7 in dpyResolution (ctx=..., name=0x4584f7 "X Resolution", 
e=...) at dpyfuncs.cc:194
#2  0x0040ebe3 in displayTags (driver=driver@entry=0x661010, 
header=header@entry=0x4581e5 "Standard Fields", tag_map=..., known=, 
verbose=0) at metacam.cc:86
#3  0x004060bc in processFile (is=..., fname=, 
driver=0x661010) at metacam.cc:255
#4  main (argc=, argv=) at metacam.cc:359
#5  0x772d1ead in __libc_start_main (main=, 
argc=, ubp_av=, init=, 
fini=, rtld_fini=, stack_end=0x7fffe4e8) 
at libc-start.c:244
#6  0x0040c271 in _start ()

(gdb) list
35
36
37  tiffRATIONAL
38  tiffRATIONAL::normalize() const
39  {
40  if ((num == 0) || (den == 0)) return *this;
41  unsigned long d = Euclid(num, den);
42  return tiffRATIONAL(num/d, den/d);
43  }
44

-- 
Henri Salo


signature.asc
Description: Digital signature

Bug#779694: openbsd-inetd: broaden the runtime-dependency on update-inetd to update-inetd|reconf-inetd

[Rolf Leggewie]

Package: openbsd-inetd
Version: 2:1.9.2.39.3a460-3
Severity: normal
Tags: patch

Dear Maintainer,

please consider to relax the run-time dependency on update-inetd to
(update-inetd|reconf-inetd). I have prepared a patch.

Regards

Rolf
--- debian/control.orig	2015-03-04 14:31:50.953955974 +0800
+++ debian/control	2015-03-04 14:32:12.102060846 +0800
@@ -11,7 +11,7 @@
 Package: openbsd-inetd
 Architecture: any
 Multi-Arch: foreign
-Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 3.2-13), update-inetd, tcpd
+Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 3.2-13), update-inetd | reconf-inetd, tcpd
 Provides: inet-superserver
 Description: OpenBSD Internet Superserver
  The inetd server is a network daemon program that specializes in managing

Bug#777208: [claws-mail] Can't reorganize mailboxes

[Paul]

On Wed, 4 Mar 2015 01:38:59 +0100
Ricardo Mones  wrote: 

> As a workaround you can manually edit your
> ~/.claws-mail/folderlist.xml file and rearrange the whole
> ' ... ' items. Probably with the help of an
> XML editor to avoid mistakes and exiting from Claws Mail first.

Somewhat easier is to use drag'n'drop to rearrange the order, which
still works.

with regards

Paul


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

Bug#776599: python-watchdog: please provide Python3 package

[Brian May]

On 4 Mar 2015 17:04, "gustavo panizzo (gfa)"  wrote:
> it won't build without python-pytest-cov

It seemed OK for me, however I will double check again tomorrow.

Thanks.

Bug#776599: python-watchdog: please provide Python3 package

[gustavo panizzo (gfa)]

On 03/04/2015 12:10 PM, Brian May wrote:

On 3 March 2015 at 20:55, gustavo panizzo (gfa) mailto:g...@zumbi.com.ar>> wrote:

pkg has been uploaded to


Have uploaded with some small changes to Debian. See attached patch.


it won't build without python-pytest-cov


I: pybuild base:170: python2.7 setup.py test
running test
Searching for pytest-cov
Reading https://pypi.python.org/simple/pytest-cov/
Download error on https://pypi.python.org/simple/pytest-cov/: [Errno 
111] Connection refused -- Some packages may not be found!

Couldn't find index page for 'pytest-cov' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno 111] 
Connection refused -- Some packages may not be found!

No local packages or download links found for pytest-cov
error: Could not find suitable distribution for 
Requirement.parse('pytest-cov')
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned 
exit code 13

debian/rules:4: recipe for target 'build' failed

using an up-to-date sid chroot (without internet)


--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333


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

Bug#778795: O: morfeusz -- morphological analyser of Polish

[Stéphane Fillion]

popularity-contest says morfeusz has no user and only one install -- 
possibly  the maintainer. Should it be deleted entirely from Debian?



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

Bug#779693: inetutils-inetd: broaden dependency on update-inetd

[Rolf Leggewie]

Package: inetutils-inetd
Version: 2:1.9-2
Severity: normal
Tags: patch

Dear Maintainer,

I think the dependency of inetutils-inetd on update-inetd should be broadened
to update-inetd or alternatively reconf-inetd.  Please look at the attached
patch.

Regards

Rolf
--- debian/control.orig	2015-03-04 13:44:28.403860537 +0800
+++ debian/control	2015-03-04 13:51:12.365863684 +0800
@@ -33,7 +33,7 @@
 Architecture: any
 Provides: inet-superserver, netkit-inetd
 Conflicts: inet-superserver, netkit-inetd
-Depends: ${shlibs:Depends}, ${misc:Depends}, update-inetd, tcpd, lsb-base,
+Depends: ${shlibs:Depends}, ${misc:Depends}, update-inetd | reconf-inetd, tcpd, lsb-base,
  inetutils-syslogd | system-log-daemon
 Description: internet super server
  Inetd is the daemon that listens on various TCP and UDP ports and spawns

Bug#779692: rlwrap coqtop aborts with spurious error from stale errno

[Anders Kaseorg]

Package: rlwrap
Version: 0.41-1
Tags: fixed-upstream
Forwarded: https://github.com/hanslub42/rlwrap/issues/18

$ rlwrap coqtop
rlwrap: error: Couldn't read completions from 
/usr/share/rlwrap/completions/coqtop: No such file or directory
$ ls -l /usr/share/rlwrap/completions/coqtop
-rw-r--r-- 1 root root 730 Oct 25 15:53 /usr/share/rlwrap/completions/coqtop

This error results from an incorrect test with a stale value of errno.  
It was reported and fixed uptream in v0.42:

https://github.com/hanslub42/rlwrap/issues/18
https://github.com/hanslub42/rlwrap/commit/691b4a60204da9648914d64627a946914efd6536

Anders


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

Bug#779475: [Reproducible-builds] Bug#779475: debbindiff: table borders in html output

[Paul Wise]

On Mon, 2015-03-02 at 23:13 +0100, Jérémy Bobbio wrote:

> Could you please provide a patch or a sample report?

This seems to be the appropriate command:

sed -i "s|https://wiki.debian.org/PaulWise



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

Bug#779391: [Reproducible-builds] Bug#779391: debbindiff: crashes when comparing .changes files for two versions of the same source package

[Paul Wise]

On Mon, 2015-03-02 at 23:19 +0100, Jérémy Bobbio wrote:

> I agree that debbindiff should not crash, but I don't think it should
> try to guess which files map to which other files in archives. This
> feels out of scope.

Without debbindiff mapping files between the two .changes files, it will
be useless for comparing two different versions before upload and I will
have to manually perform the mapping and debbindiff each pair of .deb
files so it would be much better to have debbindiff perform the mapping.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#779669: [Pkg-openssl-devel] Bug#779669: OpenSSL: consider completely disabling EXPORT cipher suites

[Kurt Roeckx]

On Tue, Mar 03, 2015 at 10:45:41PM +0200, Török Edwin wrote:
> can you consider disabling the export suites in OpenSSL like LibreSSL did, and
> like you've done for SSLv3?

I do want to remove the export ciphers from the DEFAULT cipher
string in all released branches.  I have patches upstream to do
that, and to completly remove support for export ciphers in
master.

> [2] https://github.com/libressl-
> portable/openbsd/commit/9e3c8206e0f32386e79956dfa4a26bbfdb3dd10d
> [4] https://github.com/libressl-
> portable/openbsd/commit/9e3c8206e0f32386e79956dfa4a26bbfdb3dd10d

That's the same link.

I suspect at least one of those patches is doing something wrong,
but didn't have a close look.


Kurt


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

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Michael Samuel]

Hi,

On 4 March 2015 at 15:22, Stephen Frost  wrote:
> That really just changes it back to the 'password' case though, doesn't
> it?  An attacker who can sniff the network would get the response from
> the client and be able to use it in a replay attack just as if it was
> the password.

They can already do that if they reconnect 65k times (on average -
this could be fixed by choosing the challenges sequentially instead of
randomly).  But yes, the intent is to make it as secure as the
'password' case.

> Sure, we could store multiple responses, but given that we don't have
> any auto-lockout mechanism after X bad attempts or anything like that,
> an attacker could simply continue retrying until we pick the one which
> they sniffed.

You'd have to store billions for this to be effective without lockout.

> I realize that's what you were getting at with your replay comment above
> but I wanted to re-state it to make sure I understood your suggestion
> correctly.  While the PG community might be willing to pursue this
> approach, I doubt they'd want to seriously increase the size of
> pg_authid and, really, to make this work well, how many different stored
> hashes would be required for this to be effective at preventing an
> attacker who can sniff the network from getting in?  We are clearly not
> going to store 4 billion entries and I doubt most people would even want
> to store more than, say, *10*.  Perhaps if we also added an auto-lockout
> feature (something I've wanted for quite a while anyway...) this would
> work out well.

As I said, you can't make this scheme safe against a network attacker.
They'd be able to dictionary attack the response, or just mess with
the active connection.

> One advantage of this approach over password is that the attacker
> wouldn't be able to get the actual password very easily and so the
> sniffed response would only be usable for the given system, but this
> definitely reduces the effectivness of the challenge/response aspect, to
> a point where I'm not really sure it's still useful.

That is correct.  I'm personally in favour of just using 'password' -
at-least it's honest.  Server-authenticated TLS (eg. verify the server
certificate only) or SSH tunnelling are the best ways to secure the
network protocol as it stands.

Regards,
  Michael


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

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Stephen Frost]

Michael,

* Michael Samuel (m...@miknet.net) wrote:
> On 4 March 2015 at 12:33, Stephen Frost  wrote:
> > To be clear, I *am* from the PostgreSQL community and I'd be happy to
> > discuss any useful suggestions about providing an alternative that
> > doesn't break the wireline protocol, because as far as I'm aware that's
> > not possible to do.  The wireline protocol is quite clear about what it
> > requires and we have quite a few client-side implementations to
> > consider.
> 
> The way I'd do this is to store a strong hash (eg. bcrypt, scrypt) of
> the password pre-digested for the challenge-response protocol with a
> fixed challenge.
> 
> The server sends the same challenge every time - this allows replays
> of the challenge-response protocol, but means that the stored hash is
> reasonably secured and disables pass-the-hash.

That really just changes it back to the 'password' case though, doesn't
it?  An attacker who can sniff the network would get the response from
the client and be able to use it in a replay attack just as if it was
the password.

Sure, we could store multiple responses, but given that we don't have
any auto-lockout mechanism after X bad attempts or anything like that,
an attacker could simply continue retrying until we pick the one which
they sniffed.

I realize that's what you were getting at with your replay comment above
but I wanted to re-state it to make sure I understood your suggestion
correctly.  While the PG community might be willing to pursue this
approach, I doubt they'd want to seriously increase the size of
pg_authid and, really, to make this work well, how many different stored
hashes would be required for this to be effective at preventing an
attacker who can sniff the network from getting in?  We are clearly not
going to store 4 billion entries and I doubt most people would even want
to store more than, say, *10*.  Perhaps if we also added an auto-lockout
feature (something I've wanted for quite a while anyway...) this would
work out well.

One advantage of this approach over password is that the attacker
wouldn't be able to get the actual password very easily and so the
sniffed response would only be usable for the given system, but this
definitely reduces the effectivness of the challenge/response aspect, to
a point where I'm not really sure it's still useful.

Thoughts appreciated.

Thanks!

Stephen


signature.asc
Description: Digital signature

Bug#776599: python-watchdog: please provide Python3 package

[Brian May]

On 3 March 2015 at 20:55, gustavo panizzo (gfa)  wrote:

> pkg has been uploaded to
>

Have uploaded with some small changes to Debian. See attached patch.


i forgot to close the bug on the changelog, i will manually close the
> bug when the pkg reach the archive
>
>
Oops. I should have fixed this myself before doing the upload, but was
getting confused between packages, ftp-master's can refer to relevant bugs
when approving packages.
-- 
Brian May 


diff
Description: Binary data

Bug#779691: libjson-rpc-cpp: FTBFS on non-Linux: No man pages to install

[Aaron M. Ucko]

Source: libjson-rpc-cpp
Version: 0.4.2-3
Severity: important
Justification: fails to build from source

The hurd-i386 build of libjson-rpc-cpp failed with the errors

  cp: cannot stat 'debian/tmp/usr/share/man/man1': No such file or directory
  dh_install: cp -a debian/tmp/usr/share/man/man1 
debian/libjsonrpccpp-tools//usr/share/man/ returned exit code 1
  make: *** [binary-arch] Error 2

and it looks like the kFreeBSD builds would have done the same if they
hadn't already failed due to test suite errors (#779689) -- according
to the build logs, man page generation occurred only on Linux.  Could
you please make sure it happens on all architectures?

Thanks!


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

Bug#779474: [Reproducible-builds] Bug#779474: debbindiff: hide temporary paths in html and text output when comparing tarballs

[Paul Wise]

On Mon, 2015-03-02 at 23:12 +0100, Jérémy Bobbio wrote:

> Without full path for the filenames at the top-level, there is no way to
> differentiate a report for two builds of the same source. As this is
> debbindiff primary purpose, I must admit I am a bit at loss.

The path names in question only occur during the runtime of debbindiff
as it is extracting them to a pair of temporary directories, diffing
them and then deleting them. The tar.gz files passed to debbindiff are
in the current directory and are fine, the issue is that the .tar files
extracted from those .tar.gz files are attributed to temporary paths
instead of being attributed to the .tar.gz files. I found that it
confusing that debbindiff was showing /tmp/XXXdebbindiff/ temporary
paths inside the .gz compression container, especially since the .gz
file was not produced by debbindiff and debbindiff did not exist when
the .gz file was created.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#779689: libjson-rpc-cpp: FTBFS: test suite errors

[Aaron M. Ucko]

Source: libjson-rpc-cpp
Version: 0.4.2-3
Severity: serious
Justification: fails to build from source

Builds of libjson-rpc-cpp failed on several platforms with test suite
errors.  On armel,

  The following tests FAILED:
  4 - connector_http (Failed)
  6 - integration (Failed)
  7 - all (Failed)

and each of those tests also failed on some other platforms, though
never the whole set elsewhere.  Could you please take a look?

Thanks!


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

Bug#779690: cecilia: can't open anymore

[Sanjeev]

Package: cecilia
Version: 5.0.9-1.1
Severity: important

Dear Maintainer,

 i can not open cecilia it throws error, here is the traceback

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_misc.py", line
1367, in Notify
self.notify()
  File 
"/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py",
line 16866, in Notify
self.result = self.callable(*self.args, 
**self.kwargs)
  File

"/usr/lib/python2.7/dist-packages/cecilia/Resources/splash.py",
line 75, in OnClose
self.callback()
  File 
"/usr/bin/cecilia", line 68, in onStart

ceciliaMainFrame.onOpen(os.path.join(MODULES_PATH,

category, file), True)

  File


"/usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaMainFrame.py",

line 236, in onOpen

CeciliaLib.openCeciliaFile(self, event,

builtin)

  File


"/usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaLib.py",

line 584, in openCeciliaFile


getVar("audioServer").openCecFile(cecFilePath)

  File


"/usr/lib/python2.7/dist-packages/cecilia/Resources/audio.py",

line 
1660, in openCecFile


CeciliaLib.getVar("mainFrame").onUpdateInterface(None)


  File



"/usr/lib/python2.7/dist-packages/cecilia/Resources/CeciliaMainFrame.py",


line 326, in


onUpdateInterface


ceciliaInterface =


CeciliaInterface.CeciliaInterface(None,


title='Interface - %s' %


 

Bug#779688: libjson-rpc-cpp: FTBFS: gen/abstractsubserver.h: No such file or directory

[Aaron M. Ucko]

Source: libjson-rpc-cpp
Version: 0.4.2-3
Severity: serious
Justification: fails to build from source

Builds of libjson-rpc-cpp failed for several architectures with the error

  /«PKGBUILDDIR»/src/test/test_integration.cpp:17:35: fatal error: 
gen/abstractsubserver.h: No such file or directory

It looks like this error may stem from an undeclared dependency that's
only a problem in parallel builds; if so, you might consider simply
dropping --parallel from your dh invocations for now.

Could you please take a look?

Thanks!


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

Bug#779687: libdevel-callchecker-perl: FTBFS on i386: DynaLoader bombs out

[Aaron M. Ucko]

Source: libdevel-callchecker-perl
Version: 0.006-1
Severity: serious
Justification: fails to build from source

The automated build of libdevel-callchecker-perl failed (only) on
i386 due to test suite errors (excerpted from
https://buildd.debian.org/status/fetch.php?pkg=libdevel-callchecker-perl&arch=i386&ver=0.006-1&stamp=1425399391
 ):

  cd . && ./Build test  --verbose 1
  Can't use an undefined value as a subroutine reference at 
/usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210.
  END failed--call queue aborted at lib/Devel/CallChecker.pm line 210.
  Compilation failed in require at t/WriteHeader.pm line 14.
  # Looks like your test exited with 2 before it could output anything.
  t/callck.t . 
  1..79
  Dubious, test returned 2 (wstat 512, 0x200)
  Failed 79/79 subtests 

The portion of DynaLoader.pm leading up to line 210 (from
DynaLoader::bootstrap) reads

  boot:
my $xs = dl_install_xsub("${module}::bootstrap", $boot_symbol_ref, $file);

# See comment block above

push(@dl_shared_objects, $file); # record files loaded

&$xs(@args);

I'm not sure if it's relevant, but the i386 build of perl has the
unusual property that the perl binary links statically rather than
dynamically to libperl for performance reasons.

At any rate, could you please take a look?

Thanks!


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

Bug#779686: RFP: namecoin -- decentralized information registration and transfer system

[Carlo Stemberger]

Package: wnpp
Severity: wishlist

* Package name: namecoin
  Version : 0.3.76rc1
  Upstream Author : Namecoin Developers
* URL : http://namecoin.info/
* License : MIT
  Programming Lang: C++, Python
  Description : decentralized information registration and transfer system

Namecoin is a decentralized open source information registration and transfer
system based on the Bitcoin cryptocurrency.

What does it do?
* Securely record and transfer arbitrary names (keys).
* Attach a value (data) to the names
  (up to 520 bytes, more in the future).
* Transact namecoins, the digital currency (ℕ, NMC).

Namecoin was the first fork of Bitcoin and still is one of the most innovative
altcoins. It was first to implement merged mining and a decentralized DNS.

What can it be used for?
* Protect free-speech rights online by making the web more resistant to
  censorship.
* Access websites using the .bit domain (with TLS/SSL).
* Store identity information such as email, GPG key, BTC address, TLS
  fingerprints, Bitmessage address, etc.
* Human readable Tor .onion names/domains.
* File signatures, Voting, bonds/stocks,/shares, web of trust, escrow and notary
  services (to be implemented).


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

Bug#779359: apache2-bin: SSL SNI check fails for larger PHP uploads with "no hostname provided in HTTP request"

[Adam Rosi-Kessel]

Perhaps unsurprisingly, the same issue appears with any form submission, 
whether it is a file upload or just an HTTP POST. The cut-off point for 
failure seems to be somewhere just around 1K.



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

Bug#779685: libnm-qt: homepage in metadata goes to a 404

[Stephen Paul Weber]

Source: libnm-qt
Version: 0.9.8.2-1

The metadata in the source package libnm-qt lists a homepage which leads to 
a 404.  I believe the new homepage for this package is 
, but I'm 
not sure this is indeed the same package.



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

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Michael Samuel]

Hi,

On 4 March 2015 at 12:33, Stephen Frost  wrote:
> * Michael Samuel (m...@miknet.net) wrote:
>> - I don't recommend storing the password in cleartext
>> - I *do* recommend exchanging the password in cleartext over the network
>
> And I will continue to argue that it's far worse these days to send the
> password in cleartext across the wire.

For Unix and server-authenticated TLS sockets, this is a clear loss.
For cleartext sockets, you're going to have a very bad day if there's
a network attacker, regardless of authentication protocol.


> Where would they get the pg_authid entry from?  It's not directly
> visible in the network traffic because PG using a challenge/response
> system with md5.

>From an old backup tape, a stolen hard drive, SQL injection (or is
this no longer viable?).  This is the reason why the stored password
is hashed in the first place :)

But a fair point - it would be much easier to go from sniffing
challenge-response to cleartext than it would to get the intermediate
hash.

> No, it isn't a great challenge/response, but it's certainly better than
> just forgoing all of that and sending the password in cleartext.

See above...

> To be clear, I *am* from the PostgreSQL community and I'd be happy to
> discuss any useful suggestions about providing an alternative that
> doesn't break the wireline protocol, because as far as I'm aware that's
> not possible to do.  The wireline protocol is quite clear about what it
> requires and we have quite a few client-side implementations to
> consider.

The way I'd do this is to store a strong hash (eg. bcrypt, scrypt) of
the password pre-digested for the challenge-response protocol with a
fixed challenge.

The server sends the same challenge every time - this allows replays
of the challenge-response protocol, but means that the stored hash is
reasonably secured and disables pass-the-hash.

> Note that this is specifically why other authentication methods are
> available and encouraged with PG.

No disagreement with that approach either.  But defaults are easier
than non-defaults, and there's a hell of a lot that can go wrong with
Kerberos, PKIX, etc too...


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

Bug#764298: Still an issue

[Michael Biebl]

Am 2015-03-04 01:13, schrieb Michael Biebl:

Am 04.03.2015 um 01:34 schrieb Michael Biebl:

Am 04.03.2015 um 01:07 schrieb Daurnimator:
Did you dist-upgrade the VM and those failures are from before the 
upgrade?

Can you attach your /var/log/dpkg.log


The reason why I'm asking is, that the fixed version 215-12 migrated to
testing on 2015-02-28.
The latest AMI according to [1] is from 20150213, so it can't have
215-12 yet. So this looks like the VM was upgraded and the error
messages are from before the upgrade when systemd < 215-12 was 
installed.


[1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie


Just double checked: The latest AMI provided by Debian ships 215-11.
So, if you have 215-12 installed, this means the VM was upgraded after 
the VM was instantiated and booted and the error messages you see are 
most likely from 215-11, which does not ship the fix yet.



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

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Stephen Frost]

* Michael Samuel (m...@miknet.net) wrote:
> - I don't recommend storing the password in cleartext
> - I *do* recommend exchanging the password in cleartext over the network

And I will continue to argue that it's far worse these days to send the
password in cleartext across the wire.

> This is because the exchange network protocol is vulnerable to "pass
> the hash" - so somebody who has your pg_shadow but can't crack your
> password can still use the hash to login.

Where would they get the pg_authid entry from?  It's not directly
visible in the network traffic because PG using a challenge/response
system with md5.

> In the thread it was pointed out that the network protocol is
> vulnerable to session hijacking.  Additionally, the challenge-response
> protocol is vulnerable to extremely fast password searches. This is
> just another broken ad-hoc challenge-response protocol to be added to
> the heap.  If anyone from postgres is interested in putting a
> network-compatible fix for password hashing in, feel free to contact
> me.

No, it isn't a great challenge/response, but it's certainly better than
just forgoing all of that and sending the password in cleartext.

To be clear, I *am* from the PostgreSQL community and I'd be happy to
discuss any useful suggestions about providing an alternative that
doesn't break the wireline protocol, because as far as I'm aware that's
not possible to do.  The wireline protocol is quite clear about what it
requires and we have quite a few client-side implementations to
consider.

Note that this is specifically why other authentication methods are
available and encouraged with PG.

Thanks,

Stephen


signature.asc
Description: Digital signature

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Stephen Frost]

* Michael Samuel (m...@miknet.net) wrote:
> On 4 March 2015 at 12:03, Aaron Zauner  wrote:
> >> Uh, no, using 'password' is far worse, and uniformly so, than using md5.
> >> I have no idea why anyone would think it's better to store a cleartext
> >> version of your password in the pg_authid data (note that pg_shadow is
> >> only a view now, I replaced it long ago when I rewrote the user/group
> >> system to be role-based).
> 
> I was referring to the pg_hba.conf setting in my recommendation.
> Using "password" there does not change the stored hash, it only
> changes the network protocol.

Then it's simply a trade-off between trusting the network traffic, as
the password will then be sent *in-cleartext* across the wire, and
trusting the data on disk (which, as discussed, if you have access to
already then you hardly need the password).  PG does allow you to make
that trade-off, but having a challenge/response to protect the hash of
the password as it goes across the network is far more useful than
trying to protect something in pg_authid, which you can only get if
you've already compromised the postgres account.

> > Agreed - most enterprise or cloud deployment I've been involved with
> > use either PKIX or kerberos. This is a good security measure.
> > Replacing MD5 would be nice as well (scrypt, bcrypt?). But I guess a
> > debian bug report is the wrong place to discuss this.
> 
> Agree that debian bug is wrong place to discuss fixing password hashing.

The current discussion in the community is about implementing SCRAM with
SASL as an additional authentication method.  You would certainly be
welcome to provide any thoughts you have to the thread on pgsql-hackers.

Thanks,

Stephen


signature.asc
Description: Digital signature

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Michael Samuel]

Just to make it clear:

- I don't recommend storing the password in cleartext
- I *do* recommend exchanging the password in cleartext over the network

This is because the exchange network protocol is vulnerable to "pass
the hash" - so somebody who has your pg_shadow but can't crack your
password can still use the hash to login.

In the thread it was pointed out that the network protocol is
vulnerable to session hijacking.  Additionally, the challenge-response
protocol is vulnerable to extremely fast password searches. This is
just another broken ad-hoc challenge-response protocol to be added to
the heap.  If anyone from postgres is interested in putting a
network-compatible fix for password hashing in, feel free to contact
me.


On 4 March 2015 at 12:09, Michael Samuel  wrote:
> Hi,
>
> On 4 March 2015 at 12:03, Aaron Zauner  wrote:
>>> Uh, no, using 'password' is far worse, and uniformly so, than using md5.
>>> I have no idea why anyone would think it's better to store a cleartext
>>> version of your password in the pg_authid data (note that pg_shadow is
>>> only a view now, I replaced it long ago when I rewrote the user/group
>>> system to be role-based).
>
> I was referring to the pg_hba.conf setting in my recommendation.
> Using "password" there does not change the stored hash, it only
> changes the network protocol.
>
>> Agreed - most enterprise or cloud deployment I've been involved with
>> use either PKIX or kerberos. This is a good security measure.
>> Replacing MD5 would be nice as well (scrypt, bcrypt?). But I guess a
>> debian bug report is the wrong place to discuss this.
>
> Agree that debian bug is wrong place to discuss fixing password hashing.


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

Bug#779417: ITP: python-pytest-timeout -- pytest plugin to abort hanging tests

[Brian May]

On 4 March 2015 at 12:18, Brian May  wrote:

> On 3 March 2015 at 20:53, gustavo panizzo (gfa)  wrote:
>
>> @Brian, can you sponsor this upload? thanks!
>>
>
> Ok, done.
>

Just noticed that the build-depends on python-tox is possibly redundant. At
least it seems to build fine on wheezy which doesn't have it.
-- 
Brian May 

Bug#779684: phabricator: does not allow empty mysql root password

[Christoph Egger]

Package: phabricator
Version: 0~git20150211-1
Severity: normal

Hi!

  If I use an empty root password for mysql (should be fine so far -- only
listening on localhost), pharicator (almost) silently fails to setup.

  Christoph

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

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

Versions of packages phabricator depends on:
ii  arcanist   0~git20150211-1
ii  dbconfig-common1.8.47+nmu3
ii  debconf [debconf-2.0]  1.5.55
ii  fonts-font-awesome 4.2.0~dfsg-1
ii  jq 1.4-2.1
ii  libjs-raphael  2.1.0-1
ii  libphutil  0~git20150211-1
ii  php5   5.6.5+dfsg-2
ii  php5-cli   5.6.5+dfsg-2
ii  php5-curl  5.6.5+dfsg-2
ii  php5-mysql 5.6.5+dfsg-2
ii  po-debconf 1.0.16+nmu3
ii  ucf3.0030

Versions of packages phabricator recommends:
ii  mariadb-server  10.0.16-1
ii  nginx   1.6.2-5
ii  nginx-full [nginx]  1.6.2-5
pn  php5-apcu   
pn  php5-gd 

Versions of packages phabricator suggests:
pn  flashplugin-nonfree  
ii  python   2.7.8-3

-- debconf information:
* phabricator/pwd_check: (password omitted)
* phabricator/phabricator_mysql_pwd: (password omitted)
* phabricator/domain_name: projects.faui2k9.de
* phabricator/phabricator_mysql_user: root
  phabricator/mysql_host: localhost
* phabricator/webserver: nginx
  phabricator/password_mismatch:


-- 
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/20150304010937.ga12...@phabricator.siccegge.de

Bug#779417: ITP: python-pytest-timeout -- pytest plugin to abort hanging tests

[Brian May]

On 3 March 2015 at 20:53, gustavo panizzo (gfa)  wrote:

> @Brian, can you sponsor this upload? thanks!
>

Ok, done.
-- 
Brian May 

Bug#764298: Still an issue

[Michael Biebl]

Am 04.03.2015 um 01:34 schrieb Michael Biebl:
> Am 04.03.2015 um 01:07 schrieb Daurnimator:
> Did you dist-upgrade the VM and those failures are from before the upgrade?
> Can you attach your /var/log/dpkg.log

The reason why I'm asking is, that the fixed version 215-12 migrated to
testing on 2015-02-28.
The latest AMI according to [1] is from 20150213, so it can't have
215-12 yet. So this looks like the VM was upgraded and the error
messages are from before the upgrade when systemd < 215-12 was installed.

[1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Michael Samuel]

Hi,

On 4 March 2015 at 12:03, Aaron Zauner  wrote:
>> Uh, no, using 'password' is far worse, and uniformly so, than using md5.
>> I have no idea why anyone would think it's better to store a cleartext
>> version of your password in the pg_authid data (note that pg_shadow is
>> only a view now, I replaced it long ago when I rewrote the user/group
>> system to be role-based).

I was referring to the pg_hba.conf setting in my recommendation.
Using "password" there does not change the stored hash, it only
changes the network protocol.

> Agreed - most enterprise or cloud deployment I've been involved with
> use either PKIX or kerberos. This is a good security measure.
> Replacing MD5 would be nice as well (scrypt, bcrypt?). But I guess a
> debian bug report is the wrong place to discuss this.

Agree that debian bug is wrong place to discuss fixing password hashing.


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

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Aaron Zauner]

Hi Stephen,

* Stephen Frost  [04/03/2015 01:45:56] wrote:
> Aaron,
> 
> * Aaron Zauner (a...@azet.org) wrote:
> > Debian ships a set of Perl scripts to configure for PostgreSQL server
> > configurations, these are quite outdated and are currently configuring
> > authentication to use MD5 when 'password' should be used instead.
> 
> Uh, no, using 'password' is far worse, and uniformly so, than using md5.
> I have no idea why anyone would think it's better to store a cleartext
> version of your password in the pg_authid data (note that pg_shadow is
> only a view now, I replaced it long ago when I rewrote the user/group
> system to be role-based).
> 

I assumed 'password' is an alias for a stronger hashing scheme. Mea
culpa, I should have read the source-code, not only the package
content and upstream defaults. I was not aware that 'password' is
indeed 'plaintext'.

> Absolutely no would be the answer. 

Given your explaination I totally agree here. I'm good to close this
- but let's wait if mik replies to this as well.

> The PG community has long been discussing the possibility of providing a
> new authentication mechanism to replace the md5 one, but anyone who
> actually cares about security will be using Kerberos or Certificate
> based authentication anyway, so it hasn't been a priority.

Agreed - most enterprise or cloud deployment I've been involved with
use either PKIX or kerberos. This is a good security measure.
Replacing MD5 would be nice as well (scrypt, bcrypt?). But I guess a
debian bug report is the wrong place to discuss this.

Thanks for clearing this up & your quick reply,
Aaron


signature.asc
Description: Digital signature

Bug#692512: ITP: tilde -- a text editor for the console/terminal with intuitive interface

[Stéphane Fillion]

retitle 692512 ITP: tilde -- a text editor for the console/terminal with
intuitive interface
owner 692512 !
thanks

This is my favorite editor and it's a shame it's not in debian already.
I intent to package it.

Bug#777123:

[Stéphane Fillion]

owner 777123 !
thanks

Bug#779546: Further information

[Cyril Brulebois]

Ben Hutchings  (2015-03-03):
> Yes, that's right.  The problem is that we now detect missing firmware
> by scraping the kernel log, and we still pick up old ones after
> installing firmware and poking the driver.
> 
> I think we could solve this by noting the timestamp at the bottom of the
> kernel log every time we scan it, then only checking lines after that on
> the next scan.

I think that's an idea I mentioned in a previous bug report, yes. I'll
try and see if I can implement & verify this before RC2.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#779683: [Pkg-postgresql-public] Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Stephen Frost]

Aaron,

* Aaron Zauner (a...@azet.org) wrote:
> Debian ships a set of Perl scripts to configure for PostgreSQL server
> configurations, these are quite outdated and are currently configuring
> authentication to use MD5 when 'password' should be used instead.

Uh, no, using 'password' is far worse, and uniformly so, than using md5.
I have no idea why anyone would think it's better to store a cleartext
version of your password in the pg_authid data (note that pg_shadow is
only a view now, I replaced it long ago when I rewrote the user/group
system to be role-based).

> http://www.openwall.com/lists/oss-security/2015/03/03/12

This isn't news and the post linked by Michael is actually a discussion
that I started 10 years ago.  It's cute that atom has "found" it and
claimed it to be a serious issue, but it simply isn't.

> I'd recommend to change this setting ASAP. Open to discuss.

Absolutely no would be the answer.  There is no reason to believe that
having a cleartext password is better than having a hashed
representation of it.  I hope someone on the OSS list corrects Michael's
understanding.

The PG community has long been discussing the possibility of providing a
new authentication mechanism to replace the md5 one, but anyone who
actually cares about security will be using Kerberos or Certificate
based authentication anyway, so it hasn't been a priority.

Thanks,

Stephen


signature.asc
Description: Digital signature

Bug#777208: [claws-mail] Can't reorganize mailboxes

[Ricardo Mones]

Control: tags -1 confirmed
Control: forwarded -1 
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3397

Hi Antonio,

On Fri, 6 Feb 2015 11:08:32 +0100
Antonio  wrote:

> Package: claws-mail
> Version: 3.11.1-3
> Severity: minor
> 
> --- Please enter the report below this line. ---
> Hi!
> 
> I have two IMAP accounts and two local ones; I added the second IMAP
> account recently and Claws-Mail can't put its mailbox in second
> position. With "Reorganize mailboxes" I can see the four of them, but
> the buttons "up" and "down" are greyed out.
> 
> Thanks!

This seems also present in latest git version, so I'm forwarding it upstream.

As a workaround you can manually edit your ~/.claws-mail/folderlist.xml file
and rearrange the whole ' ... ' items. Probably with
the help of an XML editor to avoid mistakes and exiting from Claws Mail first.

Thanks for reporting,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «He that teaches himself has a fool for a master. -- Benjamin Franklin»


pgpPsvHKIm_rx.pgp
Description: OpenPGP digital signature

Bug#764298: Still an issue

[Michael Biebl]

Am 04.03.2015 um 01:07 schrieb Daurnimator:
> On 3 March 2015 at 18:42, Michael Biebl  wrote:
>> What's the output of
>> systemctl cat systemd-logind.service
>> systemctl status systemd-logind.service
> 
> $ sudo systemctl cat systemd-logind.service
> # /lib/systemd/system/systemd-logind.service
> #  This file is part of systemd.
> #
> #  systemd is free software; you can redistribute it and/or modify it
> #  under the terms of the GNU Lesser General Public License as published by
> #  the Free Software Foundation; either version 2.1 of the License, or
> #  (at your option) any later version.
> 
> [Unit]
> Description=Login Service
> Documentation=man:systemd-logind.service(8) man:logind.conf(5)
> Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind
> Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat
> Wants=user.slice
> After=nss-user-lookup.target user.slice
> ConditionPathExists=/lib/systemd/system/dbus.service

That looks ok.

> # Ask for the dbus socket. If running over kdbus, the socket will
> # not be actually used.
> Wants=dbus.socket
> After=dbus.socket
> 
> [Service]
> ExecStart=/lib/systemd/systemd-logind
> Restart=always
> RestartSec=0
> BusName=org.freedesktop.login1
> CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN
> CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER
> CAP_SYS_TTY_CONFIG
> WatchdogSec=1min
> 
> # Increase the default a bit in order to allow many simultaneous
> # logins since we keep one fd open per session.
> LimitNOFILE=16384
> 
> 
> $ sudo systemctl status systemd-logind.service
> ● systemd-logind.service - Login Service
>Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
>Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56
> UTC; 4h 3min ago
>start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago
>  Docs: man:systemd-logind.service(8)
>man:logind.conf(5)
>http://www.freedesktop.org/wiki/Software/systemd/logind
>http://www.freedesktop.org/wiki/Software/systemd/multiseat
>  Main PID: 341 (code=exited, status=1/FAILURE)
>Status: "Shutting down..."
> 
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
> has no holdoff time, scheduling restart.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
> start request repeated too quickly, refusing to start.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit
> systemd-logind.service entered failed state.
> Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service.
> Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service.

Did you dist-upgrade the VM and those failures are from before the upgrade?
Can you attach your /var/log/dpkg.log

Is the problem reproducible after a reboot?

Fwiw, I can't reproduce the problem in a VM without dbus installed, so
we need to find what's special in your case.

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



signature.asc
Description: OpenPGP digital signature

Bug#779683: postgresql: pg_hba scripts (mis)configures for MD5 authentication

[Aaron Zauner]

Package: postgresql
Severity: important
Tags: security

Hi,

Debian ships a set of Perl scripts to configure for PostgreSQL server
configurations, these are quite outdated and are currently configuring
authentication to use MD5 when 'password' should be used instead.

http://www.openwall.com/lists/oss-security/2015/03/03/12

I'd recommend to change this setting ASAP. Open to discuss.

(Also applies to Ubuntu)

Thanks,
Aaron


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

Bug#764298: Still an issue

[Daurnimator]

On 3 March 2015 at 18:42, Michael Biebl  wrote:
> What's the output of
> systemctl cat systemd-logind.service
> systemctl status systemd-logind.service

$ sudo systemctl cat systemd-logind.service
# /lib/systemd/system/systemd-logind.service
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Login Service
Documentation=man:systemd-logind.service(8) man:logind.conf(5)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind
Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat
Wants=user.slice
After=nss-user-lookup.target user.slice
ConditionPathExists=/lib/systemd/system/dbus.service

# Ask for the dbus socket. If running over kdbus, the socket will
# not be actually used.
Wants=dbus.socket
After=dbus.socket

[Service]
ExecStart=/lib/systemd/systemd-logind
Restart=always
RestartSec=0
BusName=org.freedesktop.login1
CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN
CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER
CAP_SYS_TTY_CONFIG
WatchdogSec=1min

# Increase the default a bit in order to allow many simultaneous
# logins since we keep one fd open per session.
LimitNOFILE=16384


$ sudo systemctl status systemd-logind.service
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
   Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56
UTC; 4h 3min ago
   start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago
 Docs: man:systemd-logind.service(8)
   man:logind.conf(5)
   http://www.freedesktop.org/wiki/Software/systemd/logind
   http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 341 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
has no holdoff time, scheduling restart.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
start request repeated too quickly, refusing to start.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit
systemd-logind.service entered failed state.
Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service.
Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service.


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

Bug#779682: texlive-base: install complains a4 is not valid for pdftex but says a4 is valid

[Chris Bainbridge]

Package: texlive-base
Version: 2014.20141024-2
Severity: normal

Dear Maintainer,

texlive-base warns that a4 is not a valid setting for pdftex, but then
recommends a command which says that a4 is valid.


# apt-get install texlive-base

Unmanageable system paper size (a4)  The currently defined system-wide paper
size is a4. However, the TeX  configuration system cannot handle this paper
size for pdftex.  The setting will remain unchanged.  The following command can
show the list of known paper sizes for pdftex:  texconfig pdftex paper


# texconfig pdftex paper

WARNING: On Debian, this change will NOT be persistent
upon upgrades or changes to the libpaper settings!
Usage: texconfig pdftex paper PAPER

Valid PAPER settings:
  a4 letter



-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 828 Mar  3 23:49 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 21 01:46 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Dec  2 13:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Dec  2 13:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Mar  3 23:44 /etc/texmf/web2c/texmf.cnf
-rw-r--r-- 1 root root 3186 Mar  3 23:49 /var/lib/texmf/web2c/fmtutil.cnf
lrwxrwxrwx 1 root root 32 Dec  2 13:39 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
Warning: language.dat cannot be found with kpsewhich!
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Oct 21 01:46 mktex.cnf
-rw-r--r-- 1 root root 475 Mar  3 23:44 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  dpkg   1.17.23
ii  libpaper-utils 1.1.24+nmu4
ii  tex-common 5.03
ii  texlive-binaries   2014.20140926.35254-6
ii  ucf3.0030
ii  xdg-utils  1.1.0~rc1+git20111210-7.4

Versions of packages texlive-base recommends:
ii  lmodern  2.004.4-5

Versions of packages texlive-base suggests:
ii  evince [postscript-viewer]   3.14.1-1
ii  ghostscript [postscript-viewer]  9.06~dfsg-2
pn  perl-tk  
pn  xpdf-reader | pdf-viewer 

Versions of packages tex-common depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  dpkg   1.17.23
ii  ucf3.0030

Versions of packages tex-common suggests:
ii  debhelper  9.20141022

Versions of packages texlive-base is related to:
ii  tex-common5.03
ii  texlive-binaries  2014.20140926.35254-6

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of 

Bug#777237: Sagemath has special needs

[Bill Allombert]

On Wed, Feb 18, 2015 at 10:40:24AM +0100, Julien Puydt wrote:
> >>- they also have backported patches to add cb_pari_err_handle from
> >>upstream's repository (see end of this mail).
> >>
> >>Can we get those in debian too?
> >
> >This patch is breaking the ABI and API, thus this is not possible to
> >apply it.
> 
> Since it's backported from upstream, it will be in some version at
> some point : do you have an ETA?

I expect PARI 2.9 to be released in about one year.
But at this point SAGE will require other patches to be applied anyway.

> >Beside SAGE could do the same thing without patching PARI, by
> >using the standard PARI error trapping mechanism (iferr_env and
> >global_err_data). This would be much better.
> 
> That would be the sensible thing to do, but sage developers have a
> terrible tendency to patch upstream instead of using upstream. On
> some occasions, I have proposed them to replace an upstream patch
> with a one-line patch to their code, because the api to configure
> what they wanted was right there...

Yes, they should create a small C library that would be linked with 
libpari and would provide the changes they like instead of patching
libpari directly.

> It looks like they've been toying with pari error handling for months:
> http://trac.sagemath.org/ticket/14894

I have been trying to explain to the SAGE developers how to use pari error
handling since 2005...
 
> Is there a better way to do what they want ?

I expect they should do something like
if (setjmp(&iferr_env))
{
  GEN E = pari_err_last();
  char *s = GSTR(GENtoGENstr(E));
  fprintf(stderr,s);
  ...
}
before the point they are recovering using cb_pari_err_recover() at this time.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


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

Bug#779681: executing ifdown on a dhcp configured interface unconfigures other dhcp interfaces

[David S. Roth]

Package: ifupdown
Version: 0.7.52

The system under test has 3 network interfaces each configured using dhcp.

System configuration:

/etc/network/interfaces:

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

auto eth2
allow-hotplug eth2
iface eth2 inet dhcp

auto eth3
allow-hotplug eth3
iface eth3 inet dhcp

/etc/dhcp/dhclient.conf:

option rfc3442-classless-static-routes code 121 = array of unsigned 
integer 8;


#send host-name "andare.fugue.com";
send host-name = gethostname();

interface "eth2" {
request subnet-mask, broadcast-address, time-offset, interface-mtu, 
ntp-servers,

domain-name-servers, domain-name;
require domain-name-servers, domain-name;
send dhcp-client-identifier "cs-controller1";}


interface "eth3" {
request subnet-mask, broadcast-address, time-offset, interface-mtu, 
ntp-servers,

domain-name-servers, domain-name;
require domain-name-servers, domain-name;
send dhcp-client-identifier "cs-controller2";}


Post boot 'ifdown ethN; ifup ethN' is executed to reconfigure the dhcp
interfaces one at a time.

Executing ifdown on a specific interface unconfigures the other dhcp
interfaces rather than just the targeted interface.

E. g.: 'ifdown eth2' results in eth3 being unconfigured.

When executing ifdown eth2 we would expect only eth2 to be affected.


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

Bug#764298: Still an issue

[Michael Biebl]

Am 04.03.2015 um 00:19 schrieb Daurnimator:
> I just installed a fresh systemd (via amazon AMI:
> https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd
> 215-12
> I still got the log message:
> 
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
> Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to
> system bus: No such file or directory
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main
> process exited, code=exited, status=1/FAILURE
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service
> entered failed state.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no
> holdoff time, scheduling restart.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...
> 
> (and then again a few times)
> 

What's the output of
systemctl status dbus.service dbus.socket?

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



signature.asc
Description: OpenPGP digital signature

Bug#779678: udev spins up disk after spindown

[Michael Biebl]

control: tags -1 moreinfo

Am 03.03.2015 um 23:42 schrieb Mikulas Patocka:
> Package: udev
> Version: 215-12
> Severity: normal
> 
> Dear Maintainer,
> 
> When I spin down SCSI disk with sdparm -C stop /dev/sdc, udev spins up the 
> disk
> immediatelly.
> 
> This bug is new in Jessie. In Wheezy, udev doesn't spin the disk up.

How did you conclude, that it is udev, which spins up the disk?


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



signature.asc
Description: OpenPGP digital signature

Bug#764298: Still an issue

[Michael Biebl]

Am 04.03.2015 um 00:37 schrieb Daurnimator:
> On 3 March 2015 at 18:35, Michael Biebl  wrote:
>>
>> What's the output of
>> systemctl status dbus.service dbus.socket?
> 
> 
> I do not have dbus installed.
> 
> $ sudo systemctl status dbus.service
> ● dbus.service
>Loaded: not-found (Reason: No such file or directory)
>Active: inactive (dead)
> 
> 
> $ sudo systemctl status dbus.socket
> ● dbus.socket
>Loaded: not-found (Reason: No such file or directory)
>Active: inactive (dead)
> 

What's the output of
systemctl cat systemd-logind.service
systemctl status systemd-logind.service


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



signature.asc
Description: OpenPGP digital signature

Bug#764298: Still an issue

[Daurnimator]

On 3 March 2015 at 18:35, Michael Biebl  wrote:
>
> What's the output of
> systemctl status dbus.service dbus.socket?


I do not have dbus installed.

$ sudo systemctl status dbus.service
● dbus.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)


$ sudo systemctl status dbus.socket
● dbus.socket
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.


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

Bug#774914: firmware-linux-nonfree: Include the intel sst firmwares required for audio on Bay Trail

[René Wagner]

Hi,

On 03/03/2015 10:53 PM, René Wagner wrote:

I believe this is a manifestion of incorrect dynamic irq allocation
causing all sorts of GPIO/SDIO-using hardware to break  (see e.g.
[3]). A patch by Thomas Gleixner is available at [4] which IIRC has
already been applied upstream in later kernel releases.


It turns out the patch had already been merged sometime around 3.15 and
is included in the Jessie kernel so I'm not sure what's going on here.

Regards,

Rene


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

Bug#774914: firmware-linux-nonfree: Include the intel sst firmwares required for audio on Bay Trail

[René Wagner]

Hi Antonio,

On 03/03/2015 10:23 PM, Antonio Ospite wrote:

It is true that I am running a custom kernel, but the files I am
talking about are shipped upstream by linux-firmware anyways.

Of course this is not a urgent matter at all and it can wait after
Jessie becomes stable but, eventually, tracking what upstream ships
is the way to go when the licenses of the firmware files are
compatible with Debian.


Sure, my point was that the firmware files from linux-firmware.git are
either incompatible with the 3.16 kernel from Jessie, or there are
hardware differences between different Baytrail devices preventing
things from working on my Dell Venue 8 Pro. I'll have to test more
recent kernels to rule out the latter.

Does sound work for you with 3.19 and the firmware files from
linux-firmware.git?

Regards,

Rene


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

Bug#764298: Still an issue

[Daurnimator]

I just installed a fresh systemd (via amazon AMI:
https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd
215-12
I still got the log message:

Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to
system bus: No such file or directory
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main
process exited, code=exited, status=1/FAILURE
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service
entered failed state.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no
holdoff time, scheduling restart.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...

(and then again a few times)

Bug#717215: [pkg-dhcp-devel] Bug#717215: Bug#717215: dhcpd: 5 bad udp checksums in 5 packets

[Michael Gilbert]

control: reassign -1 src:isc-dhcp
control: reassign 652739 src:isc-dhcp
control: forcemerge 652739 -1

On Tue, Mar 3, 2015 at 9:25 AM, Simon Boulet wrote:
> This bug prevents *Debian* instances using DHCP from working in any
> virtualized environments (being KVM, Xen or LXC) without the workaround.
> Every other major distributions (Red Hat in 2011, Ubuntu in 2013) now have
> fixed their DHCP client. Also LXC added the iptables workaround to 1.0.0 in
> 2014.

KVM actually seems to work ok.  Anyway, the changes are somewhat
large.  It would be far better for this to happen first upstream, so
your best bet is to move the discussion to their lists.

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#779680: ITP: node-argparse -- command-line argument parser for node.js

[Stephen Kitt]

Package: wnpp
Severity: wishlist
Owner: Stephen Kitt 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-argparse
  Version : 1.0.1
  Upstream Author : Vitaly Puzrin 
* URL : https://github.com/nodeca/argparse
* License : Expat
  Programming Lang: JavaScript
  Description : command-line argument parser for node.js

 argparse is a full JavaScript port of Python's argparse module. It supports
 parsing command-line options, both long and short forms, non-option
 arguments, and can build help messages listing all known options.
 .
 Node.js is an event-based server-side JavaScript engine.

This is a requirement for Keybase.


pgpXLdb9uQmVR.pgp
Description: OpenPGP digital signature

Bug#778729: Try 2: Bug#778729: RFS: git-tools/1.0.0-1 [ITP]

[Adam Borowski]

On Thu, Feb 19, 2015 at 02:53:52AM +0100, Adam Borowski wrote:
> * Package name: git-tools
> * URL : https://github.com/MestreLion/git-tools
> 
> It builds those binary packages:
>   git-restore-mtime - set timestamps to the date of a file's last commit

Hi guys again!  Lemme ping you, as sadly no one offered to sponsor this
package yet...  I made a few changes:
* fixed a reference to GPL2 (should be GPL3)
* moved my hand-crafted manpages to debian/ (so they don't require a patch)
* actually installed them (only the help2manned one was there[¹])
* renamed the source to git-tools, per Chris Lamb's suggestion.
* picked a fix from upstream

The m.d.n page:
http://mentors.debian.net/package/git-tools
dget
http://mentors.debian.net/debian/pool/main/g/git-tools/git-tools_1.0.0-1.dsc

The main installed tool, "git restore-mtime" sets the timestamp of each file
in the working dir to the date of the last commit that touched that file.
This is useful whenever timestamps provide some value, as opposed to just
being older/newer than the result of a make command.

There's three other tools: "git clone-subset" butchers a repository (incl. 
history) leaving only files you choose, "git find-uncommitted-repos"
searches your filesystem for unclean git repos, "git strip-merge" helps
drop some files during merge.


It would be nice if someone could sponsor this for me.


[¹]. Lintian checks only programs in [/usr]/[s]bin, not in /usr/lib/git-core,
so this did not get caught.
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.


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

Bug#779679: libvirt-python: please make the build reproducible

[Chris Lamb]

Source: libvirt-python
Version: 1.2.9-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

The attached patch removes randomess from the build system. Once
applied, libvirt-python can be built reproducibly in our reproducible
toolchain.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -urNad 
libvirt-python.orig/libvirt-python-1.2.9/debian/patches/reproducible_build 
libvirt-python/libvirt-python-1.2.9/debian/patches/reproducible_build
--- libvirt-python.orig/libvirt-python-1.2.9/debian/patches/reproducible_build  
1970-01-01 01:00:00.0 +0100
+++ libvirt-python/libvirt-python-1.2.9/debian/patches/reproducible_build   
2015-03-03 22:40:36.200504422 +
@@ -0,0 +1,55 @@
+--- libvirt-python-1.2.9.orig/generator.py
 libvirt-python-1.2.9/generator.py
+@@ -1792,7 +1792,7 @@ def buildWrappers(module):
+ value = int(value)
+ except ValueError:
+ value = float('inf')
+-return value
++return value, data[0]
+ 
+ # Resolve only one level of reference
+ def resolveEnum(enum, data):
+@@ -1877,7 +1877,7 @@ def qemuBuildWrappers(module):
+ #
+ # Generate functions directly, no classes
+ #
+-for name in list(qemu_functions.keys()):
++for name in sorted(qemu_functions.keys()):
+ func = nameFixup(name, 'None', None, None)
+ (desc, ret, args, file, mod, cond) = qemu_functions[name]
+ fd.write("def %s(" % func)
+@@ -1927,10 +1927,10 @@ def qemuBuildWrappers(module):
+ #
+ # Generate enum constants
+ #
+-for type,enum in list(qemu_enums.items()):
++for type,enum in sorted(qemu_enums.items()):
+ fd.write("# %s\n" % type)
+ items = list(enum.items())
+-items.sort(key=lambda i: int(i[1]))
++items.sort(key=lambda i: (int(i[1]), i[0]))
+ for name,value in items:
+ fd.write("%s = %s\n" % (name,value))
+ fd.write("\n")
+@@ -1990,7 +1990,7 @@ def lxcBuildWrappers(module):
+ #
+ # Generate functions directly, no classes
+ #
+-for name in list(lxc_functions.keys()):
++for name in sorted(lxc_functions.keys()):
+ func = nameFixup(name, 'None', None, None)
+ (desc, ret, args, file, mod, cond) = lxc_functions[name]
+ fd.write("def %s(" % func)
+@@ -2040,10 +2040,10 @@ def lxcBuildWrappers(module):
+ #
+ # Generate enum constants
+ #
+-for type,enum in list(lxc_enums.items()):
++for type,enum in sorted(lxc_enums.items()):
+ fd.write("# %s\n" % type)
+ items = list(enum.items())
+-items.sort(key=lambda i: int(i[1]))
++items.sort(key=lambda i: (int(i[1]), i[0]))
+ for name,value in items:
+ fd.write("%s = %s\n" % (name,value))
+ fd.write("\n")
diff -urNad libvirt-python.orig/libvirt-python-1.2.9/debian/patches/series 
libvirt-python/libvirt-python-1.2.9/debian/patches/series
--- libvirt-python.orig/libvirt-python-1.2.9/debian/patches/series  
1970-01-01 01:00:00.0 +0100
+++ libvirt-python/libvirt-python-1.2.9/debian/patches/series   2015-03-03 
22:40:32.160324047 +
@@ -0,0 +1 @@
+reproducible_build

Bug#779678: udev spins up disk after spindown

[Mikulas Patocka]

Package: udev
Version: 215-12
Severity: normal

Dear Maintainer,

When I spin down SCSI disk with sdparm -C stop /dev/sdc, udev spins up the disk
immediatelly.

This bug is new in Jessie. In Wheezy, udev doesn't spin the disk up.

   * What led up to the situation?
I want to spin down unused disks to reduce noise
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Run sdparm -C stop /dev/sdc
   * What was the outcome of this action?
The disk spins down and then spins up immediatelly
   * What outcome did you expect instead?
The disk should not spin up

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



-- Package-specific info:

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

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

Versions of packages udev depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.55
ii  libacl12.2.52-2
ii  libblkid1  2.25.2-5
ii  libc6  2.19-15
ii  libkmod2   18-3
ii  libselinux12.3-2
ii  libudev1   215-12
ii  lsb-base   4.1+Debian13+nmu1
ii  procps 2:3.3.9-8
ii  util-linux 2.25.2-5

udev recommends no packages.

udev suggests no packages.

-- debconf information:
  udev/title/upgrade:
  udev/sysfs_deprecated_incompatibility:
  udev/reboot_needed:
  udev/new_kernel_needed: false
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:04
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:04
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:05
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:05
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:06
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:06
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:07
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:07
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:08
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:08
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:09
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:09
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:0a
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:0a
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXCPU:0b
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:0b
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=984944

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2
N: input/event2
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event2
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: MAJOR=13
E: MINOR=66
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=984957
E: XKBLAYOUT=us
E: XKBMODEL=pc105

P: /devices/LNXSYSTM:00/LNXSLPBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSLPBN:00
E: DRIVER=button
E: MODALIAS=acpi:LNXSLPBN:
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSLPBN:00/input/input3
E: DEVPATH=/devices/LNXSYSTM:00/LNXSLPBN:00/input/input3
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXSLPBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXSLPBN:00
E: ID_PATH_TAG=acpi-LNXSLPBN_00
E: KEY=4000 0 0
E: MODALIAS=input:b0019vp0003e-e0,1,k8E,ramlsfw
E: NAME="Sleep Button"
E: PHYS="LNXSLPBN/button/input0"
E: PRODUCT=19/0/3/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=984984

P: /devices/LNXSYSTM:00/LNXSLPBN:00/input/input3/event3
N: input/event3
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event3
E: DEVPATH=/devices/LNXSYSTM:00/LNXSLPBN:00/input/input3/event3
E:

Bug#507085: beef up sync worry note

[Stéphane Aulery]

tags 507085 - wontfix
stop

---

Hello,

jidanni is right. Sync can return before the data are fully synchronized in
accordance with POSIX.1-2001. Quote of the sync.2 man page:

According to the standard specification (e.g., POSIX.1-2001),
sync() schedules the writes, but may return before the actual
writing is done. However, since version 1.3.20 Linux does actually
wait. (This still does not guarantee data integrity: modern disks
have large caches.)

It deserves to be mentioned in sync.1.

Regards,

-- 
Stéphane Aulery


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

Bug#726430: apt-listbugs: Does not uses proxy from Acquire::http::ProxyAutoDetect

[Francesco Poli]

On Tue, 03 Mar 2015 11:44:37 -0300 Lisandro Damián Nicanor Pérez Meyer
wrote:

> On Monday 02 March 2015 19:43:43 Francesco Poli wrote:
[...]
> > Hence, I would like to see the output of the following commands on your
> > system:
> > 
> >   $ grep -i detect /etc/apt/apt.conf /etc/apt/apt.conf.d/*
> 
> /etc/apt/apt.conf.d/30autoproxy:Acquire::http::ProxyAutoDetect 
> "/usr/share/squid-deb-proxy-client/apt-avahi-discover";

ProxyAutoDetect is the legacy option name (see apt.conf(5) man page for
more details) and it's not supported by apt-listbugs.

You have to use the current option name:
  Acquire::http::Proxy-Auto-Detect
as explained in apt-listbugs(1) man page.

Please try to add those two hyphens to your configuration and test
apt-listbugs again.

> 
> >   $ apt-config shell proxy_detect acquire::http::proxy-auto-detect
> 
> Returns nothing

After the configuration change, this command should return something
like:

  proxy_detect='/usr/share/squid-deb-proxy-client/apt-avahi-discover'

Please check!




-- 
 http://www.inventati.org/frx/
 fsck is a four letter word...
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpSBhbpn8Idf.pgp
Description: PGP signature

Bug#774643: [Pkg-puppet-devel] Bug#774643: [DRE-maint] Bug#774643: verify_active_connections is not present in ruby-activerecord 4.1.8

[Stig Sandbeck Mathisen]

Apollon Oikonomopoulos  writes:

> Then for Puppet 4/5/whatever we definitely need to provide a PuppetDB
> package.

To package puppetdb while following the Debian packaging policy,
experience with packaging clojure or java apps for Debian with leiningen
and maven would be a big bonus. The learning curve is scary steep.

-- 
Stig Sandbeck Mathisen


signature.asc
Description: PGP signature

Bug#779312: freerdp-x11: Segfaults on start 100% of the time

[John Goerzen]

Removing those parameters indeed fixes the crash.

John

On 03/01/2015 08:00 AM, Bernhard Übelacker wrote:
> Hello John Goerzen,
> I was able to reproduce a crash with xfreerdp.
>
> First a question:
> does the crash still happen, if you omit this part of the command line:
> --plugin rdpsnd --data alsa latency:100 --
>
> ---
>
> After installing the 5 *-dbg packages I get such a stack:
> gdb --args xfreerdp --plugin rdpsnd --data alsa latency:100 -- 
> /v:192.168.178.45
> directory libfreerdp/core:libfreerdp/common:client/common
> set height 0
> set width 0
> run
> Starting program: /usr/bin/xfreerdp --plugin rdpsnd --data alsa 
> latency:100 -- /v:192.168.178.45
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x75bb058c in freerdp_static_channel_collection_add 
> (settings=settings@entry=0x65ac10, channel=channel@entry=0x666bb0) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/libfreerdp/common/settings.c:214
> 214 
> settings->StaticChannelArray[settings->StaticChannelCount++] = channel;
>
> (gdb) bt
> #0  0x75bb058c in freerdp_static_channel_collection_add 
> (settings=settings@entry=0x65ac10, channel=channel@entry=0x666bb0) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/libfreerdp/common/settings.c:214
> #1  0x76ce5563 in freerdp_client_add_static_channel 
> (settings=settings@entry=0x65ac10, count=, params=0x666b60) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/cmdline.c:393
> #2  0x76ce8252 in freerdp_client_old_process_plugin 
> (settings=settings@entry=0x65ac10, args=args@entry=0x666b40) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/compatibility.c:176
> #3  0x76ce863c in freerdp_client_old_command_line_pre_filter 
> (context=context@entry=0x65ac10, index=5, index@entry=1, argc=argc@entry=8, 
> argv=argv@entry=0x7fffe018) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/compatibility.c:292
> #4  0x73baed6e in CommandLineParseArgumentsA 
> (argc=argc@entry=8, argv=argv@entry=0x7fffe018, 
> options=options@entry=0x76efd1c0 , flags=flags@entry=1036, 
> context=context@entry=0x65ac10, preFilter=preFilter@entry=0x76ce83e0 
> , postFilter=0x0) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/utils/cmdline.c:88
> #5  0x76ce884b in freerdp_detect_old_command_line_syntax 
> (argc=argc@entry=8, argv=argv@entry=0x7fffe018, 
> count=count@entry=0x7fffddcc) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/compatibility.c:346
> #6  0x76ce5ff2 in freerdp_client_detect_command_line (argc=8, 
> argv=0x7fffe018, flags=0x7fffde30) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/cmdline.c:911
> #7  0x76ce62b3 in freerdp_client_parse_command_line_arguments 
> (argc=8, argv=0x7fffe018, settings=0x60e8e0) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/cmdline.c:1014
> #8  0x76ce4d56 in freerdp_client_parse_command_line 
> (context=context@entry=0x609420, argc=argc@entry=8, 
> argv=argv@entry=0x7fffe018) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/client.c:111
> #9  0x00401be8 in main (argc=8, argv=0x7fffe018) at 
> /build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/X11/cli/xfreerdp.c:56
>
> (gdb) print settings->StaticChannelArray
> $1 = (ADDIN_ARGV **) 0x0
> (gdb) print settings->StaticChannelCount
> $2 = 2
> (gdb) print channel
> $3 = (ADDIN_ARGV *) 0x666bb0
> (gdb) print settings->StaticChannelArraySize
> $4 = 0
>
> ---
>
> In my opinion the problem lies in the initialization of the "settings" 
> structure.
>
> In "freerdp_detect_old_command_line_syntax" the "settings" are only allocated 
> and
> the whole memory set to 0. Therefore  StaticChannelArraySize is 0.
>
> Later when we get into this function we enter the if block. But because
> StaticChannelArraySize equals still 0 the "*= 2" has no effect and it stays 0.
> Therefore the realloc is done with size 0. Therefore a null pointer is 
> returned.
>
>
> void freerdp_static_channel_collection_add(rdpSettings* settings, ADDIN_ARGV* 
> channel)
> {
>   if (settings->StaticChannelArraySize < (settings->StaticChannelCount + 
> 1))
>   {
>   settings->StaticChannelArraySize *= 2;
>   settings->StaticChannelArray = (ADDIN_ARGV**)
>   realloc(se

Bug#779677: csslint-0.6: hangs forever

[Jakub Wilk]

Package: libcroco-tools
Version: 0.6.8-3+b1
Usertags: afl

csslint hangs forever (at least for 2 minutes, after which I lost my 
patience :-P) when checking the attached file:


$ csslint-0.6 hang.css
[nothing happens]


This bug was found using American fuzzy lop:
http://lcamtuf.coredump.cx/afl/
(available in Debian experimental)

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

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

Versions of packages libcroco-tools depends on:
ii  libc6 2.19-15
ii  libcroco3 0.6.8-3+b1
ii  libglib2.0-0  2.42.1-1
ii  libxml2   2.9.2+dfsg1-3

--
Jakub Wilk
@media print { a { color: r

Bug#779545: ITP: rofi -- A window switcher, run dialog and dmenu replacement

[Jason Pleau]

Hello !

On 03/03/15 03:59 PM, Alessandro Ghedini wrote:
> On dom, mar 01, 2015 at 11:42:00 -0500, Jason Pleau wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Jason Pleau 
>>
>> * Package name: rofi
>>   Version : 0.15.2
>>   Upstream Author : Dave Davenport 
>> * URL : https://davedavenport.github.io/rofi/
>> * License : MIT/X11
>>   Programming Lang: C
>>   Description : A window switcher, run dialog and dmenu replacement
>>
>> rofi can act as an application launcher, window switcher, ssh launcher and
>> dmenu replacement.
>>
>> [...]
>>
>> I plan on maintaining this package in collab-maint.
> 
> Hello,
> 
> what's the status on this? I'm available for sponsoring, if needed.
> 
> Cheers
> 

Packaging is going well, there are a few things I'd like to talk about
with upstream before asking for a review/sponsor:

 * "make test" fails with the release tarball

 * dpkg-shlibdeps warns me about unused dependencies, will need to
investigate a bit

 * gcc gives a few warnings while compiling, would be nice to have those
fixed I think

 * a few typos to fix in the source code


I will push my files to collab-maint by friday (and will let you know!)

Thanks!


-- 
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#779676: dep5-copyright-license-name-not-unique check is too strict or too severe.

[Charles Plessy]

Package: lintian
Version: 2.5.30+deb8u3
Severity: normal

Dear Lintian maintainers,

thank you for your support of the machine-readable copyright format.

Regarding the tag dep5-copyright-license-name-not-unique, I think that it
is either too strict or too severe.

The specification does not require the use of stand-alone License paragraphs
when the same license short name is used in multiple Files paragraphs.  Hence
it is only an error if two Files paragraphs use the same short name for a
License, but with a different description.

I think that the dep5-copyright-license-name-not-unique tag should either:

 - reduce its severity, as just an advice for readability, or
 - only be issued when the same short name is used with a different description.

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#779675: lintian: Add flag --list-tags that will list all tags Lintian knows about

[Rajendra Gokhale]

Package: lintian
Version: 2.5.6ubuntu0.1
Severity: wishlist

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

I would like to avoid having to maintain multiple 

If I ask Lintian to suppress a tag that is known to a later version of Lintian 
but not known to the current version it will exit with an error.  This can
be problematic in an environment where a package gets built on different
versions of OSes running different versions of Lintian (potentially).

Having a --list-tags option will allow me to take a set of tags I have and 
create a new set that consists exclusively of tags known to the current
version of Lintian so that I do not need to maintain a separate list of 
override tags for each platform I run lintian on

There could be other uses to for this option

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


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

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

Versions of packages lintian depends on:
ii  binutils   2.22-6ubuntu1.2
ii  bzip2  1.0.6-1
ii  diffstat   1.54-1
ii  file   5.09-2ubuntu0.6
ii  gettext0.18.1.1-5ubuntu3
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.25build2
ii  libc-bin   2.15-0ubuntu10.11
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.31-1build3
ii  libdpkg-perl   1.16.1.2ubuntu7.5
ii  libemail-valid-perl0.185-1
ii  libipc-run-perl0.90-1
ii  libparse-debianchangelog-perl  1.2.0-1ubuntu1
ii  libtimedate-perl   1.2000-1
ii  liburi-perl1.59-1
ii  locales2.13+git20120306-3
ii  man-db 2.6.1-2
ii  patchutils 0.3.2-1.1
ii  perl [libdigest-sha-perl]  5.14.2-6ubuntu2
ii  unzip  6.0-4ubuntu1

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch 
ii  dpkg-dev   1.16.1.2ubuntu7.5
ii  libhtml-parser-perl3.69-1build1
ii  libtext-template-perl  
ii  man-db 2.6.1-2
ii  xz-utils   5.1.1alpha+20110809-3

-- 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#774914: firmware-linux-nonfree: Include the intel sst firmwares required for audio on Bay Trail

[René Wagner]

[My appologies if you received an earlier draft of this. I accidentally
hit "Send"...]

Hi,

On Fri, 09 Jan 2015 02:34:54 +0100 Antonio Ospite  wrote:

On a Bay Trail tablet I get this error:

[   16.532488] sst-acpi 80860F28:00: Direct firmware load for 
intel/fw_sst_0f28.bin-48kHz_i2s_master failed with error -2
[   16.536747] sst-acpi 80860F28:00: Cannot load firmware 
intel/fw_sst_0f28.bin-48kHz_i2s_master

The fimrware is available upstream:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/intel

And comes with this license:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.fw_sst_0f28

[...]

-- System Information:

[...]

Kernel: Linux 3.19.0-rc3-ao2 (SMP w/2 CPU cores)


Note that this is not a Debian kernel. AFAIK, Jessie will ship with
3.16.7-cktX which after enabling the relevant Alsa modules (#773835)
requests a different file. I haven't tested with kernels more recent
than 3.16. While they may work with the firmware files from linux-
firmware.git I cannot reproduce this on 3.16.

Running the current kernel from unstable

# uname -a
Linux v8p 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 
GNU/Linux


which already has a fix for #773835 I get the following in dmesg without 
the firmware files:


[3.450588] sst-acpi 80860F28:00: firmware: failed to load 
intel/fw_sst_0f28.bin-i2s_master (-2)
[3.450605] sst-acpi 80860F28:00: Direct firmware load failed with 
error -2



linux-firmware.git does not contain this file. The closest match is
indeed intel/fw_sst_0f28.bin-48kHz_i2s_master but if I rename that I
get this:

[4.043897] sst-acpi 80860F28:00: firmware: direct-loading firmware 
intel/fw_sst_0f28.bin-i2s_master
[4.413322] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.418954] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.440286] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.440313] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.442714] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.442735] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.471208] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.471228] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.557096] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.557123] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.711890] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.711916] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.719557] baytrail-pcm-audio baytrail-pcm-audio: ipc: error DSP 
boot timeout



The same behavior was also reported in a Ubuntu forum post [1] which
suggests using the firmware files from Chromium OS [2]. If I place
those files in /lib/firmware/intel the driver gets a little farther:

[3.943870] sst-acpi 80860F28:00: firmware: direct-loading firmware 
intel/fw_sst_0f28.bin-i2s_master
[4.299639] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio 
not registered
[4.306458] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.407729] byt-rt5640 byt-rt5640: ASoC: CODEC i2c-10EC5640:00 not 
registered
[4.407749] platform byt-rt5640: Driver byt-rt5640 requests probe 
deferral
[4.576641] byt-rt5640 byt-rt5640: rt5640-aif1 <-> baytrail-pcm-audio 
mapping ok



A little later the system runs into a number of issues (full dmesg
attached):

[5.258395] irq 28: nobody cared (try booting with the "irqpoll" option)
[5.263733] CPU: 0 PID: 1 Comm: systemd Tainted: G   O 
3.16.0-4-amd64 #1 Debian 3.16.7-ckt7-1
[5.274233] Hardware name: Dell Inc. Venue 8 Pro 3845/03JYKK, BIOS 
A02 12/29/2014
[5.279511]  880038eeb6c4 81509e7c 880038eeb600 
810bcffd
[5.284880]  880038eeb600 001c  
810bd521
[5.290282]    001c 


[5.295682] Call Trace:
[5.300979][] ? dump_stack+0x41/0x51
[5.306305]  [] ? __report_bad_irq+0x2d/0xc0
[5.311575]  [] ? note_interrupt+0x241/0x290
[5.316794]  [] ? handle_irq_event_percpu+0xa1/0x190
[5.322022]  [] ? handle_irq_event+0x38/0x60
[5.327211]  [] ? handle_fasteoi_irq+0x83/0x150
[5.332355]  [] ? handle_irq+0x1d/0x30
[5.337497]  [] ? do_IRQ+0x49/0xe0
[5.342625]  [] ? common_interrupt+0x6d/0x6d
[5.347718]  
[5.347750] handlers:
[5.357760] [] sst_byt_irq 
[snd_soc_sst_baytrail_pcm] threaded [] 
sst_byt_irq_thread [snd_soc_sst_baytrail_pcm]

[5.367991] Disabling IRQ #28
[5.859157] Clocksource tsc unstable (delta = 119957660 ns)
[5.863734] Switched to clocksource refined-jiffies
[8.722354] baytrail-pcm-audio baytrail-pcm-audio: ipc: --message 
timeout-- ipc

Bug#624739: formating issue with long description

[Daniele Forsi]

Package: ges0.10-tools
Followup-For: Bug #624739

Dear Maintainer,

I'm attaching a patch to debin/control that fixes the formatting issue.
--- debian/control.orig	2011-02-08 10:52:45.0 +0100
+++ debian/control	2015-03-03 22:30:49.860242398 +0100
@@ -34,10 +34,10 @@
 Description: GStreamer editing services (documentation)
  The GStreamer multimedia framework and the accompanying GNonLin set of
  plugins for non-linear editing offer all the building blocks for:
- * Decoding and encoding to a wide variety of formats, through all the
-   available GStreamer plugins.
- * Easily choosing segments of streams and arranging them through time
-   through the GNonLin set of plugins.
+  * Decoding and encoding to a wide variety of formats, through all the
+available GStreamer plugins.
+  * Easily choosing segments of streams and arranging them through time
+through the GNonLin set of plugins.
  But all those building blocks only offer stream-level access, which
  results in developers who want to write non-linear editors to write a
  consequent amount of code to get to the level of non-linear editing
@@ -62,10 +62,10 @@
 Description: GStreamer editing services (development files)
  The GStreamer multimedia framework and the accompanying GNonLin set of
  plugins for non-linear editing offer all the building blocks for:
- * Decoding and encoding to a wide variety of formats, through all the
-   available GStreamer plugins.
- * Easily choosing segments of streams and arranging them through time
-   through the GNonLin set of plugins.
+  * Decoding and encoding to a wide variety of formats, through all the
+available GStreamer plugins.
+  * Easily choosing segments of streams and arranging them through time
+through the GNonLin set of plugins.
  But all those building blocks only offer stream-level access, which
  results in developers who want to write non-linear editors to write a
  consequent amount of code to get to the level of non-linear editing
@@ -92,10 +92,10 @@
 Description: GStreamer editing services (shared library)
  The GStreamer multimedia framework and the accompanying GNonLin set of
  plugins for non-linear editing offer all the building blocks for:
- * Decoding and encoding to a wide variety of formats, through all the
-   available GStreamer plugins.
- * Easily choosing segments of streams and arranging them through time
-   through the GNonLin set of plugins.
+  * Decoding and encoding to a wide variety of formats, through all the
+available GStreamer plugins.
+  * Easily choosing segments of streams and arranging them through time
+through the GNonLin set of plugins.
  But all those building blocks only offer stream-level access, which
  results in developers who want to write non-linear editors to write a
  consequent amount of code to get to the level of non-linear editing
@@ -118,10 +118,10 @@
 Description: Tools for use with the GStreamer editing services
  The GStreamer multimedia framework and the accompanying GNonLin set of
  plugins for non-linear editing offer all the building blocks for:
- * Decoding and encoding to a wide variety of formats, through all the
-   available GStreamer plugins.
- * Easily choosing segments of streams and arranging them through time
-   through the GNonLin set of plugins.
+  * Decoding and encoding to a wide variety of formats, through all the
+available GStreamer plugins.
+  * Easily choosing segments of streams and arranging them through time
+through the GNonLin set of plugins.
  But all those building blocks only offer stream-level access, which
  results in developers who want to write non-linear editors to write a
  consequent amount of code to get to the level of non-linear editing
@@ -146,10 +146,10 @@
 Description: GObject introspection data for the GES library
  The GStreamer multimedia framework and the accompanying GNonLin set of
  plugins for non-linear editing offer all the building blocks for:
- * Decoding and encoding to a wide variety of formats, through all the
-   available GStreamer plugins.
- * Easily choosing segments of streams and arranging them through time
-   through the GNonLin set of plugins.
+  * Decoding and encoding to a wide variety of formats, through all the
+available GStreamer plugins.
+  * Easily choosing segments of streams and arranging them through time
+through the GNonLin set of plugins.
  But all those building blocks only offer stream-level access, which
  results in developers who want to write non-linear editors to write a
  consequent amount of code to get to the level of non-linear editing

Bug#774914: firmware-linux-nonfree: Include the intel sst firmwares required for audio on Bay Trail

[Antonio Ospite]

On Tue, 03 Mar 2015 21:59:20 +0100
René Wagner  wrote:

> Hi,
> 
> On Fri, 09 Jan 2015 02:34:54 +0100 Antonio Ospite  wrote:
> > please consider adding to firmware-linux-nonfree (or firmware-linux if
> > possible) the sst firmware files required to have audio working on
> > devices based on Bay Trail.
> >
> > On a Bay Trail tablet I get this error:
> >
> > [   16.532488] sst-acpi 80860F28:00: Direct firmware load for 
> > intel/fw_sst_0f28.bin-48kHz_i2s_master failed with error -2
> > [   16.536747] sst-acpi 80860F28:00: Cannot load firmware 
> > intel/fw_sst_0f28.bin-48kHz_i2s_master
> >
> > The firmware is available upstream:
> > http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/intel
> [...]
> > -- System Information:
> [...]
> > Kernel: Linux 3.19.0-rc3-ao2 (SMP w/2 CPU cores)
> 
> Note that this is not a Debian kernel. AFAIK, Jessie will ship with 
> 3.16.7-cktX. This kernel request a different file. Running
> 
> 
> # uname -r
> 3.16.0-4-amd64

Hi René,

It is true that I am running a custom kernel, but the files I am talking
about are shipped upstream by linux-firmware anyways.

Of course this is not a urgent matter at all and it can wait after
Jessie becomes stable but, eventually, tracking what upstream ships is
the way to go when the licenses of the firmware files are compatible
with Debian.

Thanks,
   Antonio

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?


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

Bug#779673: openssh-blacklist: Remove references to ssh-vulnkey(1)

[Antoine Sirinelli]

Package: openssh-blacklist
Version: 0.4.1+nmu1
Severity: normal

Dear Maintainer,

There are still references to the removed program ssh-vulnkey(1) in the
package description and in the files /usr/share/ssh/blacklist/*.

I believe this reference should be removed or noted that this program is
no longer shipped in Debian packages.

Antoine

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

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

Versions of packages openssh-blacklist depends on:
ii  dpkg  1.17.24

Versions of packages openssh-blacklist recommends:
ii  openssh-client  1:6.7p1-3

openssh-blacklist suggests no packages.

-- no debconf information


signature.asc
Description: Digital signature

Bug#779600: linux-image-3.16.0-4-686-pae: Linux console does not render the bold attribute correctly

[Samuel Bronson]

Package: src:linux
Version: 3.16.7-ckt7-1
Followup-For: Bug #779600

Dear Maintainer,

Well, it turns out that the framebuffer contains the proper colors:

,[ fbcat | ppmhist ]
|r g b   lum count
|  - - --   ---
|  0 0 00   1945537
|170   170   170  170112890
|255   255   255  255 10772
|17085 0  101  1471
|255   25585  236   926
|  0   170   170  119   704
|170 0   170   70   624
| 858585   85   397
|  0   170 0  100   273
| 85   255   255  204 6
`

but somehow they just don't look that way on my TV.  I tried resetting
the color settings on the TV but it didn't help.

Really wish I could spy on the HDMI output to see if the colors are
already screwed up or not :-(

Any information on how to check what transformations are being done to
the framebuffer data before it's sent over the HDMI would be greatly
appreciated.

-- Package-specific info:
** Version:
Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae root=/dev/mapper/Group1-ROOT ro

** Not tainted

** Kernel log:
[3.196403] scsi 6:0:0:0: Direct-Access MultiFlash Reader 1.00 
PQ: 0 ANSI: 0
[3.196695] sd 6:0:0:0: Attached scsi generic sg2 type 0
[3.197802] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[3.335820] Switched to clocksource tsc
[3.832585] random: nonblocking pool is initialized
[4.486634] systemd-udevd[317]: starting version 215
[5.240221] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
[5.240308] ACPI: Power Button [PWRB]
[5.240630] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[5.240712] ACPI: Power Button [PWRF]
[5.351248] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[5.382006] mei_me :00:16.0: irq 46 for MSI/MSI-X
[5.419268] ACPI Warning: SystemIO range 0xf040-0xf05f conflicts 
with OpRegion 0xf040-0xf04f (\_SB_.PCI0.SBUS.SMBI) 
(20140424/utaddress-258)
[5.419431] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[5.640934] [drm] Initialized drm 1.1.0 20060810
[5.689211] alg: No test for crc32 (crc32-pclmul)
[5.705872] input: PC Speaker as /devices/platform/pcspkr/input/input7
[5.997601] [drm] Memory usable by graphics device = 2048M
[5.997668] [drm] Replacing VGA console driver
[5.998188] Console: switching to colour dummy device 80x25
[6.016227] cfg80211: Calling CRDA to update world regulatory domain
[6.018714] i915 :00:02.0: irq 47 for MSI/MSI-X
[6.018723] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[6.018726] [drm] Driver supports precise vblank timestamp query.
[6.018749] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[6.094245] fbcon: inteldrmfb (fb0) is primary device
[6.119847] Console: switching to colour frame buffer device 240x67
[6.124821] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[6.124846] i915 :00:02.0: registered panic notifier
[6.163404] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[6.163606] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
[6.163692] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[6.164075] snd_hda_intel :00:03.0: irq 48 for MSI/MSI-X
[6.164113] snd_hda_intel :00:1b.0: irq 49 for MSI/MSI-X
[6.446096] sound hdaudioC1D0: autoconfig: line_outs=1 
(0x14/0x0/0x0/0x0/0x0) type:line
[6.446133] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[6.446159] sound hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[6.446183] sound hdaudioC1D0:mono: mono_out=0x0
[6.446203] sound hdaudioC1D0:inputs:
[6.446220] sound hdaudioC1D0:  Front Mic=0x19
[6.446240] sound hdaudioC1D0:  Rear Mic=0x18
[6.446260] sound hdaudioC1D0:  Line=0x1a
[6.450614] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card0/input9
[6.454684] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input10
[6.454761] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input11
[6.454830] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card1/input12
[6.454897] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1b.0/sound/card1/input13
[6.454967] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input14
[6.458776] iTCO_vendor_support: vendor-support=0
[6.459282] iTCO_wdt: Intel TCO WatchDog Timer Drive

Bug#779513: LaTeX Error: File `lambda.sty' not found.

[Hilmar Preuße]

On 03.03.2015 10:28, Joachim Breitner wrote:

Hi,


Maybe the line in the package description could have mentioned the
dependency, e.g.

  xskak -- An extension to the skak package for chess typesetting (requires 
texlive-generic-extra).

Feel free to use apt-file to search for missing files. "apt-file search 
lambda.sty" would point you to that package.


Hilmar
--
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org


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

Bug#779672: Multi-Line Architecture fields are not allowed per Debian policy

[Matthias Klose]

Package: src:calendarserer
Version: 5.2.2+dfsg-2
Severity: serious
Tags: sid jessie

Multi-Line Architecture fields are not allowed per Debian policy. Please either
use linux-any (preferred), or a one-liner.


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

Bug#779671: llvm: Symbolic links /usr/bin/llvm-ld and /usr/bin/llvm-prof are broken

[Sébastien Dinot]

Package: llvm
Version: 1:3.5-25
Severity: normal

Dear maintainer,

There are two broken links into the llvm package:

/usr/bin/llvm-ld -> ../lib/llvm-3.5/bin/llvm-ld
/usr/bin/llvm-prof -> ../lib/llvm-3.5/bin/llvm-prof


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

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

Versions of packages llvm depends on:
ii  llvm-3.5  1:3.5-9
ii  llvm-runtime  1:3.5-25

llvm recommends no packages.

llvm 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#779209: unblock: grml2usb/0.14.10.1

[Ivo De Decker]

Control: tags -1 confirmed moreinfo

Hi,

On Wed, Feb 25, 2015 at 02:34:37PM +0100, Michael Prokop wrote:
> I'm hereby asking for pre-approval of grml2usb/0.14.10.1.
> 
> It's fixing RC bug #779193 and includes a fix related to #751724
> which also affects grml2usb's grml2iso script.
> 
> debdiff of grml2usb 0.14.10 as in Debian/jessie against what I'd
> like to upload towards Debian/unstable is at the end of my mail.
> 
> Please let me know if I can upload this to Debian/unstable to get it
> towards jessie.

Please go ahead and remove the moreinfo tag from this bug once the upload is
in unstable.

Cheers,

Ivo


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

Bug#779670: wheezy-pu: package maven2-core/2.2.1-8+deb7u1

[Emmanuel Bourg]

Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu

Hi,

Please accept maven2-core/2.2.1-8+deb7u1 in stable-updates to backport
the security fix recently applied to Maven 2 in testing/unstable.

Thank you,

Emmanuel Bourg


diff -Nru maven2-core-2.2.1/debian/changelog maven2-core-2.2.1/debian/changelog
--- maven2-core-2.2.1/debian/changelog  2011-10-13 04:58:44.0 +0200
+++ maven2-core-2.2.1/debian/changelog  2015-03-03 21:27:40.0 +0100
@@ -1,3 +1,11 @@
+maven2-core (2.2.1-8+deb7u1) stable; urgency=low
+
+  * Team upload.
+  * Use a secure connection by default to download artifacts
+from the Maven Central repository (Closes: #779338)
+
+ -- Emmanuel Bourg   Fri, 27 Feb 2015 11:46:36 +0100
+
 maven2-core (2.2.1-8) unstable; urgency=low

   * Team upload.
diff -Nru 
maven2-core-2.2.1/debian/patches/0005-secure-maven-central-access.patch 
maven2-core-2.2.1/debian/patches/0005-secure-maven-central-access.patch
--- maven2-core-2.2.1/debian/patches/0005-secure-maven-central-access.patch 
1970-01-01 01:00:00.0 +0100
+++ maven2-core-2.2.1/debian/patches/0005-secure-maven-central-access.patch 
2015-03-03 21:23:21.0 +0100
@@ -0,0 +1,22 @@
+Description: Download artifacts from Maven central using https by default
+Origin: backport, https://github.com/apache/maven/commit/9216191
+--- a/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml
 b/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml
+@@ -27,7 +27,7 @@
+   central
+   Maven Repository Switchboard
+   default
+-  http://repo1.maven.org/maven2
++  https://repo1.maven.org/maven2
+   
+ false
+   
+@@ -38,7 +38,7 @@
+ 
+   central
+   Maven Plugin Repository
+-  http://repo1.maven.org/maven2
++  https://repo1.maven.org/maven2
+   default
+   
+ false
diff -Nru maven2-core-2.2.1/debian/patches/series 
maven2-core-2.2.1/debian/patches/series
--- maven2-core-2.2.1/debian/patches/series 2011-08-15 00:03:53.0 
+0200
+++ maven2-core-2.2.1/debian/patches/series 2015-03-03 21:26:53.0 
+0100
@@ -1,3 +1,4 @@
 0001-remove-webdav-support.patch
 0002-update-plugin-versions.patch
 0003-update-plexus-utils.patch
+0005-secure-maven-central-access.patch


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

Bug#779545: ITP: rofi -- A window switcher, run dialog and dmenu replacement

[Alessandro Ghedini]

On dom, mar 01, 2015 at 11:42:00 -0500, Jason Pleau wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Jason Pleau 
> 
> * Package name: rofi
>   Version : 0.15.2
>   Upstream Author : Dave Davenport 
> * URL : https://davedavenport.github.io/rofi/
> * License : MIT/X11
>   Programming Lang: C
>   Description : A window switcher, run dialog and dmenu replacement
> 
> rofi can act as an application launcher, window switcher, ssh launcher and
> dmenu replacement.
> 
> [...]
> 
> I plan on maintaining this package in collab-maint.

Hello,

what's the status on this? I'm available for sponsoring, if needed.

Cheers


signature.asc
Description: Digital signature

Bug#774914: firmware-linux-nonfree: Include the intel sst firmwares required for audio on Bay Trail

[René Wagner]

Hi,

On Fri, 09 Jan 2015 02:34:54 +0100 Antonio Ospite  wrote:

please conside adding to firmware-linux-nonfree (or firmware-linux if
possible) the sst firmware files required to have audio working on
devices based on Bay Trail.

On a Bay Trail tablet I get this error:

[   16.532488] sst-acpi 80860F28:00: Direct firmware load for 
intel/fw_sst_0f28.bin-48kHz_i2s_master failed with error -2
[   16.536747] sst-acpi 80860F28:00: Cannot load firmware 
intel/fw_sst_0f28.bin-48kHz_i2s_master

The fimrware is available upstream:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/intel

[...]

-- System Information:

[...]

Kernel: Linux 3.19.0-rc3-ao2 (SMP w/2 CPU cores)


Note that this is not a Debian kernel. AFAIK, Jessie will ship with 
3.16.7-cktX. This kernel request a different file. Running



# uname -r
3.16.0-4-amd64


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

Bug#779669: OpenSSL: consider completely disabling EXPORT cipher suites

[Török Edwin]

Package: libssl1.0.0
Version: 1.0.1k-1
Severity: normal

Dear Maintainer,

CVE-2015-0204 [1] happened because OpenSSL still had code supporting export
cipher suites.
LibreSSL has disabled the use of export cipher suites [2] and all the code
relating to use of export RSA [3]

Although I'd much rather replace OpenSSL with LibreSSL on my box, it is not
ready yet for Jessie or unstable even [4], so meantime
can you consider disabling the export suites in OpenSSL like LibreSSL did, and
like you've done for SSLv3?
Perhaps something to discuss with upstream to provide a flag for that, although
maybe the correct thing to do would be to remove that code from upstream as
well.

[1]
https://github.com/openssl/openssl/commit/ce325c60c74b0fa784f5872404b722e120e5cab0
[2] https://github.com/libressl-
portable/openbsd/commit/9e3c8206e0f32386e79956dfa4a26bbfdb3dd10d
[3] https://github.com/libressl-
portable/openbsd/commit/b0a3dc11e2f40da00441447a359ed16e8c578e44
[4] https://github.com/libressl-
portable/openbsd/commit/9e3c8206e0f32386e79956dfa4a26bbfdb3dd10d



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

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

Versions of packages libssl1.0.0 depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  libc6  2.19-15
ii  multiarch-support  2.19-15

libssl1.0.0 recommends no packages.

libssl1.0.0 suggests no packages.

-- debconf information:
  libssl1.0.0/restart-services:
  libssl1.0.0/restart-failed:


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

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Sebastiaan Couwenberg]

Hi Ross,

Thanks for your work on the bluebird packaging!

On 03/03/2015 09:01 PM, Ross Gammon wrote:
>   * Fix duplicate package descriptions

You may want to tweak these a bit to be more in line with other node-*
and libjs-* packages.

See for example node-q:

http://anonscm.debian.org/cgit/pkg-javascript/node-q.git/tree/debian/control

And also what npm2deb generates.

I pushed a change with my suggested improvement.

>   * Remove async.js and use packaged version instead

This looks a lintian false positive, the async.js in bluebird is quite
different from the node-async one.

Compare:

http://anonscm.debian.org/cgit/pkg-javascript/node-async.git/tree/lib/async.js

http://anonscm.debian.org/cgit/pkg-javascript/node-bluebird.git/tree/src/async.js

I think reverting this change and adding a lintian override instead is a
better idea.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


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

Bug#779664: ffmpeg: needs Breaks+Replaces: libav-tools (<< 6:9~)

[Andreas Cadhalpun]

Control: tags -1 pending

Hi Andreas,

On 03.03.2015 20:46, Andreas Beckmann wrote:

during a test with piuparts I noticed your package fails to co-install
with libav-tools from wheezy.


Thanks for all your testing with piuparts. :)


Since there is no ffmpeg package in jessie, adding these Breaks+Replaces
would ease some upgrade paths from wheezy as well as possible backporting.


Indeed.


In libav (6:9~beta1-1) the compatibility links for ff* tools were removed.


I just added the Breaks+Replaces in git [1].

Best regards,
Andreas

1: 
https://anonscm.debian.org/cgit/collab-maint/ffmpeg.git/commit/?id=705a1ffdfcccf83f1892353951378d9e9526804e



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

Bug#779656: unblock: freetype/2.5.2-3

[Julien Cristau]

Control: tag -1 + kibi
Control: tag -1 + d-i

On Tue, Mar  3, 2015 at 18:11:19 +0100, Moritz Muehlenhoff wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package freetype. It fixes multiple security issues.
> 
> unblock freetype/2.5.2-3
> 
unblocked, but needs kibi-ack for the udeb.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#779655: invesalius: "ZeroDivisionError: float division by zero" upon importing DICOM X-ray videos

[Andreas Tille]

Hi Axel,

thanks for your bug report.  I hope you are fine and do not need to
diagnose your own. ;-)  I have put Thiago in  CC (in case he might have
missed the bug report).  He has close connection to upstream and will
surely work on fixing the issue.

As an independant hint you might like to try ginkgocadx, amide and
aeskulap (in this order) to perhaps see what you want to see.  Any
reports about these would be welcome as well.

Kind regards

 Andreas.

On Tue, Mar 03, 2015 at 06:00:56PM +0100, Axel Beckert wrote:
> Package: invesalius
> Version: 3.0~b5-4
> Severity: normal
> 
> Hi,
> 
> thanks for packaging software for Debian which enables me to view my own
> medical data on my own and Debian running computer! :-)
> 
> I've tried to view some X-ray videos in DICOM format with Invesalius and
> when I want to import them it shows me that there 8 videos (or images,
> not 100% sure) to import, but as soon as I click on the "Import" button,
> I get an empty (0%) progress bar popup and the following Python
> stacktrace on the commandline where I started Invesalius:
> 
> Traceback (most recent call last):
>   File "/usr/share/invesalius/invesalius/gui/import_panel.py", line 171, in 
> OnClickOk
> self.LoadDicom(group)
>   File "/usr/share/invesalius/invesalius/gui/import_panel.py", line 191, in 
> LoadDicom
> [self.first_image_selection, self.last_image_selection]))
>   File 
> "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub/core/arg1/publisher.py",
>  line 36, in sendMessage
> topicObj.publish(data)
>   File 
> "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub/core/arg1/publishermixin.py",
>  line 23, in publish
> self._publish(data)
>   File 
> "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub/core/topicobj.py",
>  line 376, in _publish
> self.__sendMessage(data, self, iterState)
>   File 
> "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub/core/topicobj.py",
>  line 397, in __sendMessage
> self._mix_callListener(listener, data, iterState)
>   File 
> "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub/core/arg1/publishermixin.py",
>  line 34, in _mix_callListener
> listener(self, data)
>   File 
> "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub/core/arg1/listenerimpl.py",
>  line 51, in __call__
> cb(msg, **kwargs)
>   File "/usr/share/invesalius/invesalius/control.py", line 486, in 
> OnOpenDicomGroup
> matrix, matrix_filename, dicom = self.OpenDicomGroup(group, interval, 
> file_range, gui=True)
>   File "/usr/share/invesalius/invesalius/control.py", line 542, in 
> OpenDicomGroup
> orientation, resolution_percentage)
>   File "/usr/share/invesalius/invesalius/data/imagedata_utils.py", line 425, 
> in dcm2memmap
> update_progress= vtk_utils.ShowProgress(len(files) - 1, dialog_type = 
> "ProgressDialog")
>   File "/usr/share/invesalius/invesalius/data/vtk_utils.py", line 52, in 
> ShowProgress
> ratio = (100.0 / number_of_filters)
> ZeroDivisionError: float division by zero
> 
> (I could import and view my computer tomography data without issues into
> Invesalius, so it's not a general issue, maybe just with some specific
> data formats or even with some specific data.)
> 
> -- System Information:
> Debian Release: 8.0
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), 
> (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.16.0-4-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/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages invesalius depends on:
> ii  invesalius-bin  3.0~b5-4
> ii  python-casmoothing  0.1-2
> ii  python-gdcm 2.4.4-3
> ii  python-imaging  2.6.1-1
> ii  python-nibabel  1.3.0-2
> ii  python-numpy1:1.8.2-2
> ii  python-psutil   2.1.1-1+b1
> ii  python-scipy0.14.0-2
> ii  python-serial   2.6-1.1
> ii  python-vtk  5.8.0-17.5
> ii  python-vtkgdcm  2.4.4-3
> ii  python-wxgtk3.0 3.0.1.1+dfsg-2
> pn  python2.7:any   
> pn  python:any  
> 
> invesalius recommends no packages.
> 
> invesalius suggests no packages.
> 
> -- no debconf information
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
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#779668: (pre-approval) unblock: qtsmbstatus/2.2.1-4

[Andreas Beckmann]

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

Hi,

we have a serious upgrade problem with the qtsmbstatus package from
wheezy. Even after the recently added Breaks in samba, the upgrade paths
are still failing (#779666): 

  Setting up samba (2:4.1.17+dfsg-1) ...
  Installing new version of config file /etc/init.d/samba ...
  Installing new version of config file /etc/logrotate.d/samba ...
  update-alternatives: warning: alternative /usr/bin/smbstatus.samba3 (part of 
link group smbstatus) doesn't exist; removing from list of alternatives
  update-alternatives: warning: /etc/alternatives/smbstatus is dangling; it 
will be updated with best choice
  insserv: Service samba has to be enabled to start service qtsmbstatusd
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package samba (--configure):
   subprocess installed post-installation script returned error exit status 1

samba has changed what it's initscript provides, therefore
/etc/init.d/qtsmbstatusd needs to be upgraded as well - or at least
disabled, but this does not happen on removal, only on purge.

I have prepared a QA upload for sid that adds a preinst script to
temporarily deactivates the old incompatible initscript, that has fixed
the issue in my piuparts tests. The problem: this cannot be backported
to jessie since qtsmbstatus is not part of testing right now.

The easiest solution would be to allow qtsmbstatus back into jessie, a
proposed debdiff (relative to wheezy) is attached. Better solutions welcome.

I personally have *no* interest in qtsmbstatus beyond fixing upgrade
issues.

Please unblock package qtsmbstatus

unblock qtsmbstatus/2.2.1-4


Andreas
diff --git a/debian/changelog b/debian/changelog
index c10849b..7ce3807 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,25 @@
+qtsmbstatus (2.2.1-4) UNRELEASED; urgency=medium
+
+  * QA upload.
+  * qtsmbstatus-server.preinst: Deactivate our old init script that has
+dependencies incompatible with the new samba package to allow
+configuration of the new samba package before ourselves.  (Closes: #xx)
+  * Revert to debhelper compat level 7.
+
+ -- Andreas Beckmann   Tue, 03 Mar 2015 19:24:25 +0100
+
+qtsmbstatus (2.2.1-3) unstable; urgency=medium
+
+  * QA upload.
+  * Switch qtsmbstatusd.init from 'Required-Start: samba' to 'Should-Start:
+smbd samba-ad-dc' to restore installability with current samba packages.
+No warranty that qtsmbstatusd is working properly!  (Closes: #722465)
+  * Update Vcs-* URLs.
+  * Switch to debhelper compat level 9.
+  * Switch to copyright-format 1.0.
+
+ -- Andreas Beckmann   Sat, 10 Jan 2015 16:44:03 +0100
+
 qtsmbstatus (2.2.1-2) unstable; urgency=low
 
   * QA upload.
diff --git a/debian/control b/debian/control
index 6146ae4..d041b67 100644
--- a/debian/control
+++ b/debian/control
@@ -8,8 +8,8 @@ Build-Depends:
  libqt4-dev
 Standards-Version: 3.9.2
 Homepage: http://qtsmbstatus.free.fr/
-Vcs-Git: git://git.debian.org/collab-maint/qtsmbstatus.git
-Vcs-Browser: http://git.debian.org/?p=collab-maint/qtsmbstatus.git
+Vcs-Git: git://anonscm.debian.org/collab-maint/qtsmbstatus.git
+Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/qtsmbstatus.git
 
 Package: qtsmbstatus-language
 Architecture: all
diff --git a/debian/copyright b/debian/copyright
index d844b72..836fccd 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,30 +1,31 @@
-Format-Specification: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=135
-Name: QtSmbstatus
-Maintainer: Daniel Rocher 
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: QtSmbstatus
+Upstream-Contact: Daniel Rocher 
 Source: http://qtsmbstatus.free.fr/index.php?page=downloads
 
+Files: *
 Copyright: 2004-2008, Daniel Rocher 
 License: GPL-2+
 
-File: ./debian/*
+Files: debian/*
 Copyright:
- 2009-2010, Alessio Treglia 
+ 2009-2011, Alessio Treglia 
  2007, Daniel Rocher 
 License: GPL-2+
 
 License: GPL-2+
- This program is free software; you can redistribute it and/or modify
+ This package is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (at your option) any later version.
  .
- This program is distributed in the hope that it will be useful,
+ This package is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.
  .
- You should have received a copy of the GNU General Public License along
- with this program; if not, write to the Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-X-Comment: On Debian systems the full text of the GNU General Public
- Lic

Bug#779652: 9141 segmentation fault avconv -i -c:v libx264 -crf 23 -vf scale=1280:-1 -c:a aac -strict -sn

[Sebastian Ramacher]

Control: tags -1 = upstream
Control: forwarded -1 https://bugzilla.libav.org/show_bug.cgi?id=826

On 2015-03-03 21:06:27, Mathieu Malaterre wrote:
> On Tue, Mar 3, 2015 at 7:48 PM, Sebastian Ramacher  
> wrote:
> > Control: tags -1 + moreinfo
> >
> > On 2015-03-03 17:29:21, Mathieu Malaterre wrote:
> >> Package: libav-tools
> >> Version: 6:11.2-1
> >> Severity: normal
> >>
> >> I can make avconv crash using:
> >>
> >> $ avconv -i "6ter - OSS 117 : Le Caire nid d'espions - 01-03-2015
> >> 20h45 2h05m.ts" -c:v libx264 -crf 23 -vf scale=1280:-1 -c:a aac
> >> -strict experimental -sn -metadata title="Le Caire nid d'espions"
> >> lecaire.mkv
> >
> > Please report the issue upstream following
> > https://libav.org/bugreports.html and let us know the bug number.
> 
> Here you go:
> 
> https://bugzilla.libav.org/show_bug.cgi?id=826

Thank you.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#779652: 9141 segmentation fault avconv -i -c:v libx264 -crf 23 -vf scale=1280:-1 -c:a aac -strict -sn

[Mathieu Malaterre]

On Tue, Mar 3, 2015 at 7:48 PM, Sebastian Ramacher  wrote:
> Control: tags -1 + moreinfo
>
> On 2015-03-03 17:29:21, Mathieu Malaterre wrote:
>> Package: libav-tools
>> Version: 6:11.2-1
>> Severity: normal
>>
>> I can make avconv crash using:
>>
>> $ avconv -i "6ter - OSS 117 : Le Caire nid d'espions - 01-03-2015
>> 20h45 2h05m.ts" -c:v libx264 -crf 23 -vf scale=1280:-1 -c:a aac
>> -strict experimental -sn -metadata title="Le Caire nid d'espions"
>> lecaire.mkv
>
> Please report the issue upstream following
> https://libav.org/bugreports.html and let us know the bug number.

Here you go:

https://bugzilla.libav.org/show_bug.cgi?id=826


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

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-bluebird"

* Package name: node-bluebird
  Version : 2.9.13+dfsg-1
  Upstream Author : Petka Antonov 
* URL : https://github.com/petkaantonov/bluebird
* License : Expat
  Section : web

It builds these binary packages:

libjs-bluebird - Fully featured Promises/A+ implementation - javascript
node-bluebird - Fully featured Promises/A+ implementation - Nodejs

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

http://mentors.debian.net/package/node-bluebird


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

dget -x http://mentors.debian.net/debian/pool/main/n/node-bluebird/node-
bluebird_2.9.13+dfsg-1.dsc

The packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-bluebird.git

Changes since the last upload:

  [ Ross Gammon ]
  * Initial release (Closes: #779305)
  * Repack tarball to exclude minified javascript without source
  * Document repacking of tarball in d/README.source
  * Add a libjs-bluebird package for the browser js files
  * Fix duplicate package descriptions
  * Remove async.js and use packaged version instead

  [ Bas Couwenberg ]
  * Restructure control file with cme.
  * Add myself to Uploaders.
  * Update Vcs-Browser URL to use cgit instead of gitweb.

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-security
  APT policy: (990, 'trusty-security'), (900, 'trusty-updates'), (500, 
'trusty'), (400, 'trusty-proposed'), (200, 'utopic-proposed'), (100, 
'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-46-generic (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#779474: debbindiff: hide temporary paths in html and text output when comparing tarballs

[Nikolaus Rath]

On Mar 02 2015, Jérémy Bobbio  
wrote:
> Paul Wise:
>> The output when directly comparing two tarballs contains the temporary
>> paths used. This leaks the debbindiff user's TMP variable into the
>> report and is also ugly. I suggest changing to just showing filenames.
>> 
>> Current:
>> 
>> /tmp/user/1000/tmpFsxqeVdebbindiff/flasm_1.62-6.debian.tar vs.
>> /tmp/user/1000/tmpEVZZmydebbindiff/flasm_1.62-7.debian.tar
>> 
>> Desired:
>> 
>> flasm_1.62-6.debian.tar vs.
>> flasm_1.62-7.debian.tar
>
> I am not sure what the use case is here.
>
> Without full path for the filenames at the top-level, there is no way to
> differentiate a report for two builds of the same source. As this is
> debbindiff primary purpose, I must admit I am a bit at loss.

As you say, the primary purpose of debbindiff is to compare two builds
of the same source. So why does the path matter at all? I think all that
matters is the difference - it's not as if there's a "newer" and "older"
version or something like that.

In the case where debbindiff is used to compare different sources (as
apparently done above), the filename alone contains the necessary
information.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«


signature.asc
Description: PGP signature

Bug#779666: qtsmbstatus-server: fails to upgrade from 'wheezy': insserv: Service samba has to be enabled to start service qtsmbstatusd

[Andreas Beckmann]

Package: qtsmbstatus-server
Version: 2.2.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails.

>From the attached log (scroll to the bottom...):

  Setting up samba (2:4.1.17+dfsg-1) ...
  Installing new version of config file /etc/init.d/samba ...
  Installing new version of config file /etc/logrotate.d/samba ...
  update-alternatives: warning: alternative /usr/bin/smbstatus.samba3 (part of 
link group smbstatus) doesn't exist; removing from list of alternatives
  update-alternatives: warning: /etc/alternatives/smbstatus is dangling; it 
will be updated with best choice
  insserv: Service samba has to be enabled to start service qtsmbstatusd
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package samba (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of qtsmbstatus-server:
   qtsmbstatus-server depends on samba; however:
Package samba is not configured yet.
  
  dpkg: error processing package qtsmbstatus-server (--configure):
   dependency problems - leaving unconfigured


This is caused by the incompatible dependencies in the *old*
qtsmbstatusd initscript, but that won't be replaced before the
configure stage (which requires samba to be configured first).
Being activated, the old initscripts causes insserv to error out.

The recently added Breaks in samba is not sufficient to fix this.
This is especially a problem for wheezy->jessie upgrades since jessie
has no qtsmbstatus-server package.


cheers,

Andreas


qtsmbstatus-server_2.2.1-3.log.gz
Description: application/gzip

Bug#779080: unblock (pre-approval): gtk+2.0/2.24.25-2

[Niels Thykier]

Control: tags -1 d-i

On 2015-03-03 19:59, Iain Lane wrote:
> retitle 779080 unblock gtk+2.0/2.24.25-3
> thanks
> 
> On Tue, Mar 03, 2015 at 05:03:03PM +0100, Niels Thykier wrote:
>> Control: tags -1 -d-i
>>
>> [...]
>>
>> OK, removing the d-i tag for now.
> 
> I backported these commits too. AFAIK it's good again (spotify works for
> me now anyway... I didn't know to blame the crashes on gtk before)
> 
> Cheers,
> 

Noted, I have updated my unblock hint and re-added the d-i tag.

~Niels


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

Bug#779665: get-iplayer: version 2.87-2 fails to download many radio programs

[getiplayer@discard.email]

Package: get-iplayer
Version: 2.87-2
Severity: important
Tags: fixed-upstream
 
I can no longer download most radio programs using get-iplayer version 2.87-2.
I get an error message saying no versions of the program are available.
Upgrading to upstream version 2.91 fixed the problem for me.