Bug#803040: RM: dfo -- ROM; Abandoned upstream

[Jo Shields]

Package: ftp.debian.org
Severity: normal

This package is dead & should be removed.

Bug#802145: Attached debdiff for NMU - please commit to packaging Git

[Andreas Tille]

Hi,

I took the freedom to fix the minor bug in addition to the serious
one.  Please add the debdiff to your packaging git.

Kind regards

   Andreas.

-- 
http://fam-tille.de
diff -Nru python-cachecontrol-0.11.5/debian/changelog 
python-cachecontrol-0.11.5/debian/changelog
--- python-cachecontrol-0.11.5/debian/changelog 2015-06-01 21:48:16.0 
+0200
+++ python-cachecontrol-0.11.5/debian/changelog 2015-10-26 10:54:45.0 
+0100
@@ -1,3 +1,13 @@
+python-cachecontrol (0.11.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add python-requests to Build-Depends
+Closes: #802145
+  * Removed some underscores from long description
+Closes: #799531
+
+ -- Andreas Tille   Mon, 26 Oct 2015 10:51:48 +0100
+
 python-cachecontrol (0.11.5-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru python-cachecontrol-0.11.5/debian/control 
python-cachecontrol-0.11.5/debian/control
--- python-cachecontrol-0.11.5/debian/control   2015-06-01 21:48:16.0 
+0200
+++ python-cachecontrol-0.11.5/debian/control   2015-10-26 10:54:09.0 
+0100
@@ -9,8 +9,10 @@
 Build-Depends: debhelper (>= 9),
dh-python,
python-all (>= 2.6.6-3~),
+   python-requests,
python-setuptools,
python3-all,
+   python3-requests,
python3-setuptools
 Standards-Version: 3.9.6
 Vcs-Git: 
git://anonscm.debian.org/python-modules/packages/python-cachecontrol.git
@@ -20,8 +22,8 @@
 Architecture: all
 Depends: python-requests, ${misc:Depends}, ${python:Depends}
 Description: caching algorithms in httplib2 for use with requests
- CacheControl is a port of the caching algorithms in httplib2_ for use with
- requests_ session object.
+ CacheControl is a port of the caching algorithms in httplib2 for use with
+ requests session object.
  .
  It was written because httplib2's better support for caching is often
  mitigated by its lack of threadsafety. The same is true of requests in
@@ -33,8 +35,8 @@
 Architecture: all
 Depends: python3-requests, ${misc:Depends}, ${python3:Depends}
 Description: caching algorithms in httplib2 for use with requests
- CacheControl is a port of the caching algorithms in httplib2_ for use with
- requests_ session object.
+ CacheControl is a port of the caching algorithms in httplib2 for use with
+ requests session object.
  .
  It was written because httplib2's better support for caching is often
  mitigated by its lack of threadsafety. The same is true of requests in

Bug#803042: unbound: new upstream (1.5.6)

[Daniel Baumann]

Package: unbound
Severity: wishlist

Hi,

it would be nice if you could upgrade to the current upstream version
(1.5.6).

Regards,
Daniel

Bug#803043: mod_perl2 / Apache segfaults after upgrading from Wheezy to Jessie

[Patrick Matthäi]

Package: libapache2-mod-perl2
Version: 2.0.9~1624218-2
Severity: grave

Hello,

after upgrading our otrs2 server from wheezy/amd64 to jessie I noticed 
dozens of apache segfaults per day on this machine. In dmesg it looks 
like this:
[596698.770628] /usr/share/otrs[6733]: segfault at 8 ip 7f0d3da86933 
sp 7f0d36396740 error 4 in libperl.so.5.20.2[7f0d3d9a3000+1b5000]
[660795.241194] /usr/share/otrs[451]: segfault at 1 ip 0001 
sp 7f0d28ff0988 error 14
[660891.928530] /usr/sbin/apach[1162]: segfault at 10 ip 
7f0d3da78ec0 sp 7f0d36b97b80 error 4 in 
libperl.so.5.20.2[7f0d3d9a3000+1b5000]
[668700.556882] /usr/sbin/apach[14545]: segfault at 18 ip 
7f0d3da79307 sp 7f0d267eb8f0 error 4 in 
libperl.so.5.20.2[7f0d3d9a3000+1b5000]
[751331.096289] traps: /usr/sbin/apach[29092] general protection 
ip:7f0d3da78baf sp:7f0d2d7f97f0 error:0 in 
libperl.so.5.20.2[7f0d3d9a3000+1b5000]


In the apache error log:
[Mon Oct 26 11:12:14.001586 2015] [core:notice] [pid 23277:tid 
140548357687168] AH00051: child pid 23283 exit signal Segmentation fault 
(11), possible coredump in /tmp/apache


Now the more curious thing. I have updated another server from Wheezy to 
Jessie, which is just serving gitolite and subversion repositories 
(about mod_svn). After the upgrade full svn checkouts were impossible, 
also because of segfaults from Apache itself. Later I found, that 
mod_perl2 was installed and activated on this system, but it was not 
used at all. So uninstalling libapache2-mod-perl2 solved the issue on 
the server, where it was not required.


From the otrs Server I have got the following core dump:

root@ticket:/tmp/apache# gdb /usr/sbin/apache2 -c core
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/apache2...Reading symbols from 
/usr/lib/debug//usr/sbin/apache2...done.

done.

warning: core file may not match specified executable file.
[New LWP 23304]
[New LWP 23305]
[New LWP 23307]
[New LWP 23296]
[New LWP 23308]
[New LWP 23293]
[New LWP 23309]
[New LWP 23291]
[New LWP 23286]
[New LWP 23289]
[New LWP 23288]
[New LWP 23287]
[New LWP 23290]
[New LWP 23285]
[New LWP 23292]
[New LWP 23294]
[New LWP 23310]
[New LWP 23295]
[New LWP 23283]
[New LWP 23297]
[New LWP 23298]
[New LWP 23301]
[New LWP 23300]
[New LWP 23299]
[New LWP 23302]
[New LWP 23306]
[New LWP 23303]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/apache2 -k start'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fd3f096bac2 in modperl_interp_unselect () from 
/usr/lib/apache2/modules/mod_perl.so

(gdb) bt
#0  0x7fd3f096bac2 in modperl_interp_unselect () from 
/usr/lib/apache2/modules/mod_perl.so
#1  0x7fd3f63959be in apr_pool_destroy () from 
/usr/lib/x86_64-linux-gnu/libapr-1.so.0
#2  0x7fd3ef858c24 in ssl_io_filter_output (f=0x7fd3f6d15868, 
bb=0x7fd3f6be2b58) at ssl_engine_io.c:1659
#3  0x7fd3ef85577a in ssl_io_filter_coalesce (f=0x0, 
bb=0x7fd3f6be2b58) at ssl_engine_io.c:1558
#4  0x7fd3f6cd5b3d in ap_process_request_after_handler 
(r=0x7fd3f6bda0a0) at http_request.c:256
#5  0x7fd3f6cd6820 in ap_process_request (r=0x7fd3f6bda0a0) at 
http_request.c:363
#6  0x7fd3f6cd3122 in ap_process_http_sync_connection 
(c=0x7fd3f6d152c8) at http_core.c:190

#7  ap_process_http_connection (c=0x7fd3f6d152c8) at http_core.c:231
#8  0x7fd3f6cc9b10 in ap_run_process_connection (c=0x7fd3f6d152c8) 
at connection.c:41
#9  0x7fd3f0da651b in process_socket (bucket_alloc=, 
my_thread_num=, my_child_num=,
sock=, p=, thd=) at 
worker.c:619

#10 worker_thread (thd=0x0, dummy=0x0) at worker.c:978
#11 0x7fd3f61640a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0

#12 0x7fd3f5e9904d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0  0x7fd3f096bac2 in modperl_interp_unselect () from 
/usr/lib/apache2/modules/mod_perl.so

No symbol table info available.
#1  0x7fd3f63959be in apr_pool_destroy () from 
/usr/lib/x86_64-linux-gnu/libapr-1.so.0

No symbol table info available.
#2  0x7fd3ef858c24 in ssl_io_filter_output (f=0x7fd3f6d15868, 
bb=0x7fd3f6be2b58) at ssl_engine_io.c:1659

data = 0x0
len = 0
bucket = 

Bug#719601: RFS: datatables.js -- jQuery plug-in that makes nice tables from different data sources

[Sascha Steinbiss]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

this package is now in collab-maint:
https://anonscm.debian.org/cgit/collab-maint/datatables.js.git

Andreas, could you please take a look for sponsoring -- thanks!

I was going to just remove the 'old'
collab-maint/jquery-datatables.git. Is this OK or would you rather
have the (really unrelated) history in this repo preserved?

Cheers
Sascha

On 16/10/2015 22:20, Matthias Schmitz wrote:
> Hi Sascha, hi *,
> 
> Am Thu, 15 Oct 2015 21:18:51 +0100 schrieb Sascha Steinbiss
> :
> 
 Please either do
> 
> 1. merge your repository into
> collab-maint/jquery-datatables.git
 
 Well, the JS policy [1] stating that the repository should
 reflect the source package name, which according to the
 policy should have a different name than the one Matthias
 chose several years ago for his one. But they also state it's
 not a hard requirement so I guess this is an option.
>>> 
>>> I think you should follow JS policy which I was not aware
>>> about. So the best thing to do would probably be to rename the
>>> existing repository to collab-maint/datatables.js.git.
>> 
>> I agree. @Matthias, would that be OK with you? I can take over
>> this package for now.
> please take over :-).
> 
> Best wishes, Matthias
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWLgniAAoJEFVWo04Eo2ELz0UQAL9AcIqO4B37yz/Rq1nxtA3m
n8A8poRw8+NyWmkpeHQx1pywzsfSwzrxXNesIt+ZeF29aIV+uJsi0sst7XFsrH58
GAfeb84SSitdZECF5fdvO+wIXPegvyAhol5hQbKib+fFTDq1apw7Vj8/h0cB1BaM
UxAS+Lc7GuY3/OrFMz3IgSzG6MwcYUkesdpu3bYDksKrdB3xhEQsBBfIxeClsx1F
ArKIjwpVhFFhYgYdodnYCn99CNV/6xElcyj18Fn2Lk+buBXTkCpt87NkoLoxb6b/
Bl+F8A/8sVEYDdv3zF9wTsMrPbGqjXXn0JpaqyNoS9u+/fuzfR1kMWKjvhNsOCd5
iYHyyWc2XGcI2kGU9IzqBtkPyXnl1MjgYSp4H/JtQYQmy+66ZxEHj2qjciUg4MW2
TPatwyiG2b0VRNuzOCs4T9M5EH/rUbCfwQZqfsAfud4QY+Pln6ZvlQ43v7nEekGU
ub+N3cb/SYMA4tN4BIxW9ONcgs/7xV/SQqXIV3Lwpi0um1UbkO9saw7ZuhabQcw1
87iK/WxIN1MoJ/VX29/qRDtAC6/lI6LETds5O2lodhpdEUKChD0nqJHCn4PduRoh
V+3pbOSj3siFgrsoGXHY/e/RziCUAvUWIrZNqgFmFBvRF1IktK6Sb97xd3igKdfC
qHmw/vsrq0fIyfPMNLtK
=ngAq
-END PGP SIGNATURE-


-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 

Bug#802281: icedove: I can confirm this bug

[G. L. Gragnani]

After a fresh install of sid,
I tried to set-up Icedove.
The program starts and show the graphical window to set a new account.
However this windows does not work, in particular I noticed that the 
usual gtk-spinner
indicating that the program is looking for possible e-mail sites does 
not show up,

and no button or entry field is working.
The only thing that one can do is clicking of the main window cross to 
end the program.
What I did was then downgrade to the previous version, setup my account 
and all worked fine.
After that a made a dist-upgrade and all went fine too, since the 
account was already known to Icedove.


when I installed Icedove I also was notified that iceowl-extension was 
going to be installed, too,
but a did not care too much, and I really don't know if this is my apt 
setting or there is a dependence.


Should I guess, I suspect that is the starting form for a new set-up 
that is somewhat wrong,

but I cannot help more.

best regards

Gigi

On 10/24/15 07:34, Carsten Schoenert wrote:

Hello,

On Fri, Oct 23, 2015 at 12:30:18PM +0200, g.l. gragnani wrote:

I can confirm this behavior.
As a temporary workaround I downgraded to 31.8.0-1~deb8u1
and after setting up my account I upgraded again and
all worked flawlessy

can you please better explain what you have tried to do? Without a
better knowledge which component is provoking this issue we won't fix
this.

Have you started Icedove without any plugins in safe-mode? Wich plugins
you have normally installed?
Did this issue happen if you have only installed the package icedove
itself, no iceowl-extension or calendar-google-provider package
installed.
What is the outcome if you start icedove from a terminal (with/without)
extensions?
Which desktop environment you are using?

Please tell us more about the circumstances on your system.

Regards
Carsten



--
Gian Luigi Gragnani
Diten - University of Genoa
Via Opera Pia 11A, 16145 Genova, Italy
phone: + 39 010 353 2244

Bug#798208: Fix?

[Jayson Willson]

Could you please consider removing 081_fix_huge_icons.patch so as to fix 
this bug?

--
Yours sincerely, Jayson Willson

Bug#624076: rsyslog: Uses deprecated _set_priority GnuTLS functions

[Michael Biebl]

Am 26.10.2015 um 07:34 schrieb Andreas Metzler:
> On 2015-10-25 Michael Biebl  wrote:
> [...]
>> While 8.13.0 successfully builds with gnutls 3.4.0 now, it still seems
>> to use gnutls_certificate_type_set_priority when available, so will
>> trigger this build warning you referenced in your initial bug report.
> 
>> The upstream "fix" is to simply not use
>> gnutls_certificate_type_set_priority if not available [1], you mentioned
>> in your bug report that gnutls_priority_set_direct() should be used instead.
> 
>> Could you please follow up here or the upstream bug report if the
>> upstream change really is sufficient or if there is still some work to
>> be done.
> [...]
> 
> Hello,
> 
> Thanks for the heads-up, I have added a comment to the upstream
> report. Dropping gnutls_certificate_type_set_priority() is fine, since
> rsyslog used it to limit certificate type to X.509. As this is gnutls'
> default setting, the function call can be dropped.

Ok, great, so do you think this bug can be closed now for 8.13.0-1?


-- 
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#799250: Still freezing, may be SATA and/or md related

[Thorsten Glaser]

Version: 4.2.3-2

The BTS is down enough for reportbug at the moment, so a manual
follow-up: this also happens with linux-image-4.2.0-1-amd64:amd64
but seems to be SATA related. I seem to have a bad disc or cable
or mainboard port, and 4.1.0-2 and 4.2.0-1 seem to get hung up
over this while 4.1.0-1 just threw a bit of message into dmesg
and continued to work.

With 4.1.0-1, I have these in syslog once every couple of days:

Oct 25 02:32:11 tglase vmunix: [2910705.554295] ata7.00: exception Emask 0x0 
SAct 0x10 SErr 0x0 action 0x0
Oct 25 02:32:11 tglase vmunix: [2910705.554300] ata7.00: irq_stat 0x4008
Oct 25 02:32:11 tglase vmunix: [2910705.554302] ata7.00: failed command: READ 
FPDMA QUEUED
Oct 25 02:32:11 tglase vmunix: [2910705.554306] ata7.00: cmd 
60/04:a0:54:ee:24/00:00:0e:00:00/40 tag 20 ncq 2048 in
Oct 25 02:32:11 tglase vmunix: [2910705.554306]  res 
41/40:00:56:ee:24/00:00:0e:00:00/40 Emask 0x409 (media error) 
Oct 25 02:32:11 tglase vmunix: [2910705.554309] ata7.00: status: { DRDY ERR }
Oct 25 02:32:11 tglase vmunix: [2910705.554310] ata7.00: error: { UNC }
Oct 25 02:32:11 tglase vmunix: [2910705.556329] ata7.00: configured for UDMA/133
Oct 25 02:32:11 tglase vmunix: [2910705.556342] sd 6:0:0:0: [sdc] tag#20 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 25 02:32:11 tglase vmunix: [2910705.556345] sd 6:0:0:0: [sdc] tag#20 Sense 
Key : Medium Error [current] [descriptor]
Oct 25 02:32:11 tglase vmunix: [2910705.556347] sd 6:0:0:0: [sdc] tag#20 Add. 
Sense: Unrecovered read error - auto reallocate failed
Oct 25 02:32:11 tglase vmunix: [2910705.556350] sd 6:0:0:0: [sdc] tag#20 CDB: 
Read(10) 28 00 0e 24 ee 54 00 00 04 00
Oct 25 02:32:11 tglase vmunix: [2910705.556352] blk_update_request: I/O error, 
dev sdc, sector 237301334
Oct 25 02:32:11 tglase vmunix: [2910705.556367] ata7: EH complete

With 4.2.0-1, I have a lot more… I only could get the system
back to be responsible at all by --fail’ing the disc in the
RAID; complete dmesg follows:

[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.3-2 (2015-10-14)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 
root=/dev/mapper/vg--tglase-lv--tglase ro syscall.x32=y
[0.00] tseg: 00
[0.00] x86/fpu: Legacy x87 FPU detected.
[0.00] x86/fpu: Using 'lazy' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc7e8] usable
[0.00] BIOS-e820: [mem 0xc7e9-0xc7ea7fff] ACPI data
[0.00] BIOS-e820: [mem 0xc7ea8000-0xc7ec] ACPI NVS
[0.00] BIOS-e820: [mem 0xc7ed-0xc7ef] reserved
[0.00] BIOS-e820: [mem 0xff70-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x000437ff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.5 present.
[0.00] DMI: System manufacturer System Product Name/M4A785TD-V EVO, 
BIOS 210507/23/2010
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] AGP: No AGP bridge found
[0.00] e820: last_pfn = 0x438000 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-E uncachable
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base  mask 8000 write-back
[0.00]   1 base 8000 mask C000 write-back
[0.00]   2 base C000 mask F800 write-back
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] TOM2: 00043800 aka 17280M
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT
[0.00] e820: update [mem 0xc800-0x] usable ==> reserved
[0.00] e820: last_pfn = 0xc7e90 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at 
[880ff780]
[0.00] Base memory trampoline at [88099000] 99000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] init_memory_mapping: [mem 0x-0x000f]
[0.00]  [mem 0x-0x000f] page 4k
[0.00] BRK [0x01d2c000, 

Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]

[Daniel Stender]

On 26.10.2015 10:47, Cornelius Kölbel wrote:
> Hi Daniel,
> 
> what do you need me to do?
> As the poster of RFS do I need to take action?
> 
> Thanks
> Cornelius
> 
> Am Sonntag, den 25.10.2015, 22:00 +0100 schrieb Daniel Stender:
>> My idea with this would be, close the RFS for now, then file RFP and
>> wishlist-please-update bugs with blocks against the ITP as a todo list.
>>
>> Needs some afforestation, when everything is available privacyidea goes into
>> NEW. Like said, I think I've seen that most of the packages are group 
>> maintained
>> (with Python group in Maintainers field), that's good.
>>
>> Daniel

Yes, I didn't closed it because it's not my bug, that should do the reporter.

I've made a "afforestation" before for Prospector, there were ... I think ... 
more
than ten things outdated or not available. I'm going to help with uploads in 
the groups,
and I would really see Privacyidea in Debian at the year's turn (depends on how 
long
the missing packages are going to be in NEW), for Debian 9 there's nothing 
against it.
I'm on it (owner of the ITP bug)!

Best,
Daniel

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Bug#801435: dgit: avoiding/fixing "Source-only uploads to NEW are not allowed"

[Johannes Schauer]

Hi,

Quoting Johannes Schauer (2015-10-10 20:34:40)
> Quoting Ian Jackson (2015-10-10 18:07:02)
> > You will need to tell dgit --deliberately-include-questionable-history
> > because it doesn't know why the package was REJECTed and it wants to be
> > told that it's not because of copyright problems (in which case ideally you
> > would provide a differnet git history as well as a different package).
> 
> Aha, so --deliberately-include-questionable-history is the knob I have to 
> turn.
> That wasn't clear to me from the documentation before you told me to use it,
> and reading the documentation again it is still not clear to me how that 
> option
> works, why it exists and how it fixes my problem.
> 
> From the context I assume that this option lets me do a `dgit push` even 
> though
> I already pushed that exact same version? If so, then maybe this should be
> mentioned in the description of the option?
> 
> I was also wondering about why the mentioning of copyright and
> redistributability reasons is important there. I can think of many other
> reasons why there could be a REJECT after a dgit push including the one we
> talked about in #800060 which was REJECTED because of a hash sum mismatch.
> 
> So is --deliberately-include-questionable-history indeed the right option I
> want to do a `dgit push` of a fixed .changes or .dsc file after a REJECTED
> upload (assuming I didn't change anything of the packaging but just did a
> rebuild with different options)?

I just so happened to have made the same mistake and used `dgit push` with a
source-only .changes file even though the values of the Binaries field of the
.changes and .dsc changed compared to the last version. Thus I got, again, a
reject.

So I tried using --deliberately-include-questionable-history when doing `dgit
push` but this just results in:

josch@hoothoot> dgit push --deliberately-include-questionable-history
canonical suite name for unstable is sid
downloading 
http://ftp.debian.org/debian//pool/main/f/fuzzylite/fuzzylite_5.1+dfsg-1.dsc...
last upload to archive has NO git hash
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100 1221k  100 1221k0 0  2038k  0 --:--:-- --:--:-- 
--:--:-- 2042k
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
100 12364  100 123640 0   105k  0 --:--:-- --:--:-- 
--:--:--  106k
dpkg-source: info: extracting fuzzylite in fuzzylite-5.1+dfsg
dpkg-source: info: unpacking fuzzylite_5.1+dfsg.orig.tar.xz
dpkg-source: info: unpacking fuzzylite_5.1+dfsg-1.debian.tar.xz
dpkg-source: info: applying pkgconfig_installdir
Format `3.0 (quilt)', checking/updating patch stack
Format `3.0 (quilt)', checking/updating patch stack
synthesised git commit from .dsc 5.1+dfsg-1
HEAD is now at f327338 release 5.1+dfsg-2

Version actually in archive:5.1+dfsg-1 (older)
Last allegedly pushed/uploaded: 5.1+dfsg-2 (newer or same)
Perhaps the upload is stuck in incoming.  Using the version from git.

Format `3.0 (quilt)', checking/updating patch stack
nothing quilty to commit, ok.
checking that fuzzylite_5.1+dfsg-2.dsc corresponds to HEAD
dpkg-source: warning: extracting unsigned source package 
(../../../../fuzzylite_5.1+dfsg-2.dsc)
dpkg-source: info: extracting fuzzylite in fuzzylite-5.1+dfsg
dpkg-source: info: unpacking fuzzylite_5.1+dfsg.orig.tar.xz
dpkg-source: info: unpacking fuzzylite_5.1+dfsg-2.debian.tar.xz
dpkg-source: info: applying pkgconfig_installdir
Format `3.0 (quilt)', checking/updating patch stack
Format `3.0 (quilt)', checking/updating patch stack

You need a passphrase to unlock the secret key for
user: "Johannes Schauer "
4096-bit RSA key, ID 8FBD83E1, created 2013-07-04 (main key ID CF4D3EB4)

gpg: Signature made Mon 26 Oct 2015 11:07:58 AM CET using RSA key ID 
8FBD83E1
gpg: Good signature from "Johannes Schauer "
gpg: aka "Johannes Schauer "
gpg: aka "Johannes Schauer "
To git+ssh://d...@push.dgit.debian.org/dgit/debian/repos/fuzzylite.git
 ! [rejected]debian/5.1+dfsg-2 -> debian/5.1+dfsg-2 (already 
exists)
error: failed to push some refs to 
'git+ssh://d...@push.dgit.debian.org/dgit/debian/repos/fuzzylite.git'
hint: Updates were rejected because the tag already exists in the 
remote.
dgit: failed command: git push 

Bug#803041: gbonds: FTBFS with gnome-common 3.18

[Andreas Henriksson]

Source: gbonds
Version: 2.0.3-2.2
Severity: important

Dear Maintainer,

The gbonds package in Debian unstable fails to build from source
when using the gnome-common package currently in experimental (soon
to be uploaded to unstable, making this issue serious/RC).

The xmldocs.make file is no longer shipped in gnome-common since
https://git.gnome.org/browse/gnome-common/commit/?id=a912a74ba7999fe3ed49b07bab86685a5d117f82

Unless you want to port to newer infrastructure an alternative might
be to just use the xmldocs.make file already bundled within gbonds sources,
ie. this untested change:


diff -urip gbonds-2.0.3.orig/debian/rules gbonds-2.0.3/debian/rules
--- gbonds-2.0.3.orig/debian/rules  2010-06-07 01:59:25.0 +0200
+++ gbonds-2.0.3/debian/rules   2015-10-26 11:05:23.607479477 +0100
@@ -24,14 +24,12 @@ override_dh_auto_clean:
-rm -f ltmain.sh
-rm -f po/Makefile.in.in
-rm -f omf.make
-   -rm -f xmldocs.make
 
find -name Makefile.in -delete
find -name .cvsignore  -delete
 
 override_dh_auto_configure:
ln -sf /usr/share/gnome-common/data/omf.make .
-   ln -sf /usr/share/gnome-common/data/xmldocs.make .
 
libtoolize
intltoolize

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

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

Bug#803046: RFP: python-privacyidea -- Two Factor Authentication

[Cornelius Kölbel]

Package: wnpp
Severity: wishlist

privacyIDEA is an open solution for two-factor authentication.
privacyIDEA aims to not bind you to any decision of the authentication
protocol or it does not dictate you where your user information should
be stored. This is achieved by its totally modular architecture.
privacyIDEA supports a long list of different token types like HOTP,
TOTP, mOTP, SMS, Email, Google Authenticator, TiQR (OCRA), U2F,
x509 certificates, SSH keys, RADIUS, Remote...
It can read users from LDAP/AD, SQL, flat files and SCIM services.
It is licensed under AGPLv3

homepage: http://www.privacyidea.org
source: http://github.com/privacyidea/privacyidea




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

Bug#802999: Patch for Debian Bug#802999: generated swig file not ready for Python 3.5

[Andreas Tille]

Hi Steven,

it has turned out that the generated swig files does not build with
Python 3.5.  Since neither Matthias nor me know how to autogenerate the
file a manual patch was applied.  The patch is available here:

   
https://anonscm.debian.org/cgit/debian-med/hyphy.git/tree/debian/patches/python3.5.patch

Kind regards

Andreas.

- Forwarded message from Matthias Klose  -

Date: Sun, 25 Oct 2015 22:06:07 +0100
From: Matthias Klose 
To: Debian Bug Tracking System 
Subject: Bug#802999: generated swig file not ready for Python 3.5
X-Debian-PR-Message: report 802999
X-Debian-PR-Package: src:hyphy
X-Debian-PR-Keywords: sid stretch
X-Debian-PR-Source: hyphy

Package: src:hyphy
Version: 2.2.6+dfsg-1
Severity: serious
Tags: sid stretch

the generated swig file (how to generate this?) is not ready for Python 3.5.
Hand-patched for now.

Patch at
http://launchpadlibrarian.net/222817150/hyphy_2.2.6%2Bdfsg-1_2.2.6%2Bdfsg-1ubuntu1.diff.gz

___
Debian-med-packaging mailing list
debian-med-packag...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


- End forwarded message -

-- 
http://fam-tille.de

Bug#803050: miaviewit: FTBFS: configure: error: Unable to find MIA 2.2

[Chris Lamb]

Source: miaviewit
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

miaviewit fails to build from source in unstable/amd64:

  [..]

  checking pkg-config is at least version 0.9.0... yes
  checking for MIA... no
  configure: error: Unable to find MIA 2.2
"tail -v -n +0 config.log"

  [..]
  
  configure: exit 1
  dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
  --includedir=${prefix}/include --mandir=${prefix}/share/man
  --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
  --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu
  --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
  --disable-dependency-tracking returned exit code 1
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 255
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/miaviewit_1.0.1-1.build1.log.gz


Regards,

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


miaviewit.1.0.1-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#803049: barry: FTBFS: error: call of overloaded 'mem_fn(void (XmlNodeMapping::*)(std::ostream&) const)' is ambiguous

[Chris Lamb]

Source: barry
Version: 0.18.5-1.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

barry fails to build from source in unstable/amd64:

  [..]

  In file included from /usr/include/c++/5/memory:81:0,
   from
   /usr/include/libxml++-2.6/libxml++/parsers/saxparser.h:14,
   from
   /usr/include/libxml++-2.6/libxml++/libxml++.h:53,
   from xmlmap.h:30,
   from xmlmap.cc:24:
  /usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
 template class auto_ptr;
  ^
  xmlmap.cc: In function 'int main(int, char**)':
  xmlmap.cc:543:47: error: call of overloaded 'mem_fn(void
  (XmlNodeMapping::*)(std::ostream&) const)' is ambiguous
  bind( mem_fn(::DumpSummaries),
 ^
  In file included from xmlmap.cc:522:0:
  /usr/include/c++/5/tr1/functional:827:5: note: candidate:
  std::tr1::_Mem_fn<_Tp _Class::*> std::tr1::mem_fn(_Tp _Class::*) [with
  _Tp = void(std::basic_ostream&) const; _Class = XmlNodeMapping]
   mem_fn(_Tp _Class::* __pm)
   ^
  In file included from /usr/include/c++/5/memory:79:0,
   from
   /usr/include/libxml++-2.6/libxml++/parsers/saxparser.h:14,
   from
   /usr/include/libxml++-2.6/libxml++/libxml++.h:53,
   from xmlmap.h:30,
   from xmlmap.cc:24:
  /usr/include/c++/5/functional:739:5: note: candidate: std::_Mem_fn<_Tp
  _Class::*> std::mem_fn(_Tp _Class::*) [with _Tp =
  void(std::basic_ostream&) const; _Class = XmlNodeMapping]
   mem_fn(_Tp _Class::* __pm) noexcept
   ^
  xmlmap.cc:544:17: error: call of overloaded 'ref(std::ostream&)' is
  ambiguous
   _1, ref(cout)));
   ^
  In file included from xmlmap.cc:522:0:
  /usr/include/c++/5/tr1/functional:505:5: note: candidate:
  std::tr1::reference_wrapper<_Tp> std::tr1::ref(_Tp&) [with _Tp =
  std::basic_ostream]
   ref(_Tp& __t)
   ^
  In file included from /usr/include/c++/5/memory:79:0,
   from
   /usr/include/libxml++-2.6/libxml++/parsers/saxparser.h:14,
   from
   /usr/include/libxml++-2.6/libxml++/libxml++.h:53,
   from xmlmap.h:30,
   from xmlmap.cc:24:
  /usr/include/c++/5/functional:436:5: note: candidate:
  std::reference_wrapper<_Tp> std::ref(_Tp&) [with _Tp =
  std::basic_ostream]
   ref(_Tp& __t) noexcept
   ^
  xmlmap.cc:549:47: error: call of overloaded 'mem_fn(void
  (XmlNodeMapping::*)(std::ostream&) const)' is ambiguous
  bind( mem_fn(::DumpSummaries),
 ^
  In file included from xmlmap.cc:522:0:
  /usr/include/c++/5/tr1/functional:827:5: note: candidate:
  std::tr1::_Mem_fn<_Tp _Class::*> std::tr1::mem_fn(_Tp _Class::*) [with
  _Tp = void(std::basic_ostream&) const; _Class = XmlNodeMapping]
   mem_fn(_Tp _Class::* __pm)
   ^
  In file included from /usr/include/c++/5/memory:79:0,
   from
   /usr/include/libxml++-2.6/libxml++/parsers/saxparser.h:14,
   from
   /usr/include/libxml++-2.6/libxml++/libxml++.h:53,
   from xmlmap.h:30,
   from xmlmap.cc:24:
  /usr/include/c++/5/functional:739:5: note: candidate: std::_Mem_fn<_Tp
  _Class::*> std::mem_fn(_Tp _Class::*) [with _Tp =
  void(std::basic_ostream&) const; _Class = XmlNodeMapping]
   mem_fn(_Tp _Class::* __pm) noexcept
   ^
  xmlmap.cc:550:17: error: call of overloaded 'ref(std::ostream&)' is
  ambiguous
   _1, ref(cout)));
   ^
  In file included from xmlmap.cc:522:0:
  /usr/include/c++/5/tr1/functional:505:5: note: candidate:
  std::tr1::reference_wrapper<_Tp> std::tr1::ref(_Tp&) [with _Tp =
  std::basic_ostream]
   ref(_Tp& __t)
   ^
  In file included from /usr/include/c++/5/memory:79:0,
   from
   /usr/include/libxml++-2.6/libxml++/parsers/saxparser.h:14,
   from
   /usr/include/libxml++-2.6/libxml++/libxml++.h:53,
   from xmlmap.h:30,
   from xmlmap.cc:24:
  /usr/include/c++/5/functional:436:5: note: candidate:
  std::reference_wrapper<_Tp> std::ref(_Tp&) [with _Tp =
  std::basic_ostream]
   ref(_Tp& __t) noexcept
   ^
  Makefile:1540: recipe for target 'xmlmap-xmlmap.o' failed
  make[6]: *** [xmlmap-xmlmap.o] Error 1
  make[6]: Leaving directory '/build/barry-0.18.5/desktop/src'
  Makefile:1583: recipe for target 'all-recursive' failed
  make[5]: *** [all-recursive] Error 1
  make[5]: Leaving directory '/build/barry-0.18.5/desktop/src'
  Makefile:465: recipe for target 'all-recursive' failed
  make[4]: *** 

Bug#803038: ITP: ccdproc -- Basic data reductions of astronomy CCD images

[Ole Streicher]

Package: wnpp
Owner: Ole Streicher 
Severity: wishlist
X-Debbugs-Cc: 
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-pyt...@lists.debian.org

* Package name: ccdproc
  Version : 0.3.3
  Upstream Author : Steve Crawford
* URL : http://ccdproc.readthedocs.org/
* License : BSD-3-Clause
  Programming Lang: Python
  Description : Basic data reductions of astronomy CCD images

The ccdproc package provides many of the necessary tools for processing
of ccd images built on a framework to provide error propagation and bad
pixel tracking throughout the reduction process.

It will maintained within the Debian Astronomy Working Group. A git
repository will be created on alioth [2].

Best regards

Ole

[1] http://www.astropy.org/affiliated/index.html
[2] https://anonscm.debian.org/cgit/debian-astro/packages/ccdproc.git

Bug#802106: Please commit joblib to exppsy Git (or some other team repository)

[Andreas Tille]

Hi Yaroslav,

I'd like to squash bugs of python-skbio dependencies and I could
consider helping to fix joblib but it would help if you would move the
Git repository to exppsy Git (or any other team repository at
git.debian.org).

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#803039: [PATCH] libffi: enable autoreconf

[Frederic Bonnard]

Source: libffi
Source-Version: 3.2.1-3
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el

--

Hi,
here is a patch to enable autoreconf for libffi as it was not figuring out the
good linker on ppc64el :
---
checking whether the powerpc64le-linux-gnu-gcc linker 
(/usr/powerpc64le-linux-gnu/bin/ld -m elf64ppc) supports shared libraries... no 
---
and it should be ld only.
This was particularly problematic when cross compiling and rebootstrap was 
impacted :
https://jenkins.debian.net/view/All/job/rebootstrap_ppc64el_gcc5/44/console

Thanks,
Fred
diff -Nru libffi-3.2.1/debian/control libffi-3.2.1/debian/control
--- libffi-3.2.1/debian/control	2014-11-18 16:58:51.0 +0100
+++ libffi-3.2.1/debian/control	2015-10-22 10:21:33.0 +0200
@@ -5,7 +5,8 @@
 Build-Depends: debhelper (>= 5),
   g++-multilib [amd64 i386 mips mipsel powerpc ppc64 s390 sparc kfreebsd-amd64],
   dejagnu, lsb-release, texinfo,
-  dpkg-dev (>= 1.16.0~ubuntu4)
+  dpkg-dev (>= 1.16.0~ubuntu4),
+  dh-autoreconf, libltdl-dev
 Standards-Version: 3.9.6
 Section: libs
 
diff -Nru libffi-3.2.1/debian/rules libffi-3.2.1/debian/rules
--- libffi-3.2.1/debian/rules	2014-06-04 15:28:42.0 +0200
+++ libffi-3.2.1/debian/rules	2015-10-26 10:29:11.0 +0100
@@ -39,6 +39,7 @@
 	dh_testdir
 	rm -rf build
 	mkdir -p build
+	dh_autoreconf
 	cd build && ../configure \
 		--host=$(DEB_HOST_GNU_TYPE) \
 		--build=$(DEB_BUILD_GNU_TYPE) \
@@ -75,6 +76,7 @@
 	rm -f stamp-*
 	rm -rf build*
 	rm -f doc/libffi.info
+	dh_autoreconf_clean
 	dh_clean 
 
 install: build

Bug#803016: I've experience this on 10 diffrent installation.

[Anton Avramov]

I've also experience this on 10 different servers. Does anyone know of a
workaround?
-- 
Anton Avramov 

Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]

[Cornelius Kölbel]

Hi Daniel,

what do you need me to do?
As the poster of RFS do I need to take action?

Thanks
Cornelius


Am Sonntag, den 25.10.2015, 22:00 +0100 schrieb Daniel Stender:
> My idea with this would be, close the RFS for now, then file RFP and
> wishlist-please-update bugs with blocks against the ITP as a todo list.
> 
> Needs some aforestation, when everything is available privacyidea goes into
> NEW. Like said, I think I've seen that most of the packages are group 
> maintained
> (with Python group in Maintainers field), that's good.
> 
> Daniel
> 



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

Bug#792177: libjson-c-dev: causes creation of unowned /usr/lib//libjson-c.so.2 -> libjson-c.so symlink

[Andreas Beckmann]

On 2015-10-25 23:29, Michael Biebl wrote:
> btw, I don't see why this particular bug i RC? Unowned files by itself
> are not a reason for RC bugs.

The problem I see is leaving around broken SONAME symlinks in
/usr/lib/ upon removal of one of these -dev packages.
These could break things.


Andreas

Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]

[Cornelius Kölbel]

close 801213

Am Montag, den 26.10.2015, 11:01 +0100 schrieb Daniel Stender:
> On 26.10.2015 10:47, Cornelius Kölbel wrote:
> > Hi Daniel,
> > 
> > what do you need me to do?
> > As the poster of RFS do I need to take action?
> > 
> > Thanks
> > Cornelius
> > 
> > Am Sonntag, den 25.10.2015, 22:00 +0100 schrieb Daniel Stender:
> >> My idea with this would be, close the RFS for now, then file RFP and
> >> wishlist-please-update bugs with blocks against the ITP as a todo list.
> >>
> >> Needs some afforestation, when everything is available privacyidea goes 
> >> into
> >> NEW. Like said, I think I've seen that most of the packages are group 
> >> maintained
> >> (with Python group in Maintainers field), that's good.
> >>
> >> Daniel
> 
> Yes, I didn't closed it because it's not my bug, that should do the reporter.
> 
> I've made a "afforestation" before for Prospector, there were ... I think ... 
> more
> than ten things outdated or not available. I'm going to help with uploads in 
> the groups,
> and I would really see Privacyidea in Debian at the year's turn (depends on 
> how long
> the missing packages are going to be in NEW), for Debian 9 there's nothing 
> against it.
> I'm on it (owner of the ITP bug)!
> 
> Best,
> Daniel
> 

-- 


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

Bug#803044: gexiv2: Fix autopkgtest regression

[Martin Pitt]

Package: gexiv2
Version: 0.10.3-1
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch xenial

Hello,

gexiv2's autopkgtest recently started failing [1]

| adt-run [03:36:38]: test gir.smoketest: ---]
| adt-run [03:36:38]: test gir.smoketest:  - - - - - - - - - - results - - - - 
- - - - - -
| gir.smoketestFAIL stderr: test.py:1: PyGIWarning: GExiv2 was imported 
without specifying a version first. Use gi.require_version('GExiv2', '0.10') 
before import to ensure that the right version gets loaded.
| adt-run [03:36:39]: test gir.smoketest:  - - - - - - - - - - stderr - - - - - 
- - - - -
| test.py:1: PyGIWarning: GExiv2 was imported without specifying a version 
first. Use gi.require_version('GExiv2', '0.10') before import to ensure that 
the right version gets loaded.

This is apparently due to the recent python-gi which now emits these
warnings. Obvious patch attached.

While I was at it, I also took the liberty to rewrite the test to use
#!/usr/bin/python instead of the shell wrapper. The "cd $ADTTMP"
should be a no-op as there is no "gi" module in the gexiv2/ tree. If
you don't like this, feel free to ignore this part of course and only
add the gi.require_version.

Thanks for considering,

Martin

[1] http://ci.debian.net/packages/g/gexiv2/unstable/amd64/

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru gexiv2-0.10.3/debian/changelog gexiv2-0.10.3/debian/changelog
--- gexiv2-0.10.3/debian/changelog  2015-08-06 08:03:31.0 +0200
+++ gexiv2-0.10.3/debian/changelog  2015-10-26 11:28:04.0 +0100
@@ -1,3 +1,11 @@
+gexiv2 (0.10.3-1ubuntu1) xenial; urgency=medium
+
+  * debian/tests/gir.smoketest: Explicitly require GIR module version to avoid
+a warning on stderr. Also rewrite to use python directly, instead of an
+unnecessary shell wrapper.
+
+ -- Martin Pitt   Mon, 26 Oct 2015 11:27:27 +0100
+
 gexiv2 (0.10.3-1build2) wily; urgency=medium
 
   * No-change rebuild against libexiv2-14
diff -Nru gexiv2-0.10.3/debian/tests/gir.smoketest 
gexiv2-0.10.3/debian/tests/gir.smoketest
--- gexiv2-0.10.3/debian/tests/gir.smoketest2014-09-26 14:05:23.0 
+0200
+++ gexiv2-0.10.3/debian/tests/gir.smoketest2015-10-26 11:27:24.0 
+0100
@@ -1,11 +1,7 @@
-#!/bin/sh
-set -e
-
-cd "$ADTTMP"
-cat > test.py << EOF
+#!/usr/bin/python
+import gi
+gi.require_version('GExiv2', '0.10')
 from gi.repository import GExiv2
 
-print GExiv2.initialize()
-print type(GExiv2.Metadata())
-EOF
-python test.py
+print(GExiv2.initialize())
+print(type(GExiv2.Metadata()))


signature.asc
Description: Digital signature

Bug#792177: libjson-c-dev: causes creation of unowned /usr/lib//libjson-c.so.2 -> libjson-c.so symlink

[Michael Biebl]

Am 26.10.2015 um 10:47 schrieb Andreas Beckmann:
> On 2015-10-25 23:29, Michael Biebl wrote:
>> btw, I don't see why this particular bug i RC? Unowned files by itself
>> are not a reason for RC bugs.
> 
> The problem I see is leaving around broken SONAME symlinks in
> /usr/lib/ upon removal of one of these -dev packages.
> These could break things.

I don't see how. Well that aside, besides fixing ldconfig or updating
the rdeps of libjson0-dev, we might have a 3rd alternative:

Use the upstream, builtin --enable-oldname-compat support in json-c.
This will create a proper libjson.so lib with the correct soname. So
ldconfig won't run into this issue.

The current, Debian-only solution of using just symlinks is simply broken.


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

Bug#803045: /usr/bin/wxglade: Ipossible to addd static line

[Miloslav Semler]

Package: python-wxglade
Version: 0.7.1~rc1-3
Severity: important
File: /usr/bin/wxglade

Dear Maintainer,
recently I tried to add static line to flexgridsizer and I got following error:

ERROR   : None
An unexpected error occurred!

Date and time:   2015-10-26T11:29:16.677245
Python version:  2.7.9
wxPython version:3.0.1.1
wxWidgets platform:  __WXGTK__
wxGlade version: 0.7.0
Language code:   cs_CZ
Encoding:UTF-8
Filesystem encoding: UTF-8

Exception type:  
Exception details:   not all arguments converted during string formatting
Application stack trace:
Stack frame at level 0
==
  File 
"/usr/lib/python2.7/dist-packages/wxGlade-0.7.0-py2.7.egg/wxglade/widgets/static_line/static_line.py",
 line 107
  Function "builder(parent=, 
sizer=, 
pos=4, number=[3])"
  Source code context:
  label = '%s_%d' % (tmpl_label, number[0])
  while common.app_tree.has_name(label):
  number[0] += 1
  ->  label = tmpl_label % number[0]
  widget = editor_class(label, parent, wx.ID_ANY, 
dialog.get_selection(),
sizer, pos, common.property_panel)
  node = Tree.Node(widget)
  Local variables:
  -> sizer (): 

  -> parent (): 
  -> pos (): 4
  -> number (): [3]
  -> dialog (): 

  -> label (): 'static_line_2'

Stack frame at level 1
==
  File 
"/usr/lib/python2.7/dist-packages/wxGlade-0.7.0-py2.7.egg/wxglade/edit_sizers/edit_sizers.py",
 line 393
  Function "drop_widget(self=, event=)"
  Source code context:
  self.widget.Hide()
  # call the appropriate builder
  common.widgets[common.widget_to_add](self.parent, self.sizer,
  ->   self.pos)
  common.widget_to_add = None
  common.app_tree.app.saved = False
  
  Local variables:
  -> self (): 

  -> event (): 

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

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

Versions of packages python-wxglade depends on:
ii  python   2.7.9-1
ii  python-wxgtk3.0  3.0.1.1+dfsg-2

python-wxglade recommends no packages.

python-wxglade suggests no packages.

-- no debconf information

Bug#802648: [Aptitude-devel] Bug#802648: aptitude: definite loop when searching "youk" in "youtube-dl" package info page

[Manuel A. Fernandez Montecelo]

Control: found -1 aptitude/0.6.11


Hi all,

2015-10-22 12:23 Axel Beckert:

Control: tag -1 + confimred - unreproducible

Hi,

Axel Beckert wrote:

> > 5. press "/", and enter "you", everything is OK for now
> > 6. enter "k", the definite loop occures
>
> JFTR: I can't reproduce this with 0.7.2-1 from Debian Testing (in the
> big terminal). Will test Sid later.

Tried it on Debian Sid amd64 with a 157x21 terminal. But nothing
crashed, continues to work fine.


Sorry, I think I misunderstood the description initially. I
interpreted 'enter "you"' as typing the letters "y", "o", "u", and
then pressing the enter key and the pressing "k" to get one line up.

But if you enter "youk" aptitude no more reacts except on Ctrl-C. At
least once in the 157x21 terminal. But I wasn't able to reproduce it
even in the 157x21 terminal after I tried it in the same process while
the terminal was bigger.

So it may depend on what has already been done (and hence maybe cached
internally) before.

I was not able to reproduce it in 0.7.2-1 from testing at all, even
if I followed the instructions inside a freshly started aptitude in a
157x21 terminal.


I can reproduce it all the time, also in 0.6.11 from stable (Jessie).

I think that it's partly due to the incremental search feature
(according to the backtrace), feature about which there are more
complaints in the BTS (but I haven't checked if they are related or
not).


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#799559: [Python-modules-team] Bug#799559: python-pip: Recommends non-existing package python-dev-all

[Alexandre Novakovski]

On Sun, 20 Sep 2015 09:13:31 -0400 Scott Kitterman  wrote:
> 
> 
> On September 20, 2015 7:03:05 AM EDT, Hans Joachim Desserud  wrote:
> >Package: python-pip
> >Version: 1.5.6-7
> >Tags: patch
> >Severity: minor
> >
> >Dear maintainer,
> >
> >python-pip recommends the package python-dev-all which doesn't seem
to 
> >exist [1].
> >The attached patch removes this suggestion.
> 
> I'm pretty sure they meant python-all-dev which does exist and is a
reasonable suggestion.
> 
> Scott K
>

You got it right Scott:

sudo apt-get install python-pip
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Version choisie « 1.5.6-7 » (Debian:testing [all]) pour « python-pip »
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation : 

Les paquets suivants contiennent des dépendances non satisfaites :
 python-pip : Dépend: python-setuptools (>= 0.6c1) mais ne sera pas
installé
  Recommande: python-dev-all (>= 2.6) mais il n'est pas
installable
E: Impossible de corriger les problèmes, des paquets défectueux sont en
mode « garder en l'état ».

sudo apt-get install python-all-dev
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Les paquets supplémentaires suivants seront installés : 
  libpython-all-dev python-all
Les NOUVEAUX paquets suivants seront installés :
  libpython-all-dev python-all python-all-dev
0 mis à jour, 3 nouvellement installés, 0 à enlever et 31 non mis à
jour.
Il est nécessaire de prendre 3 028 o dans les archives.
Après cette opération, 64,5 ko d'espace disque supplémentaires seront
utilisés.
Souhaitez-vous continuer ? [O/n] 
Réception de : 1 http://mirror.steadfast.net/debian/ stable/main
libpython-all-dev amd64 2.7.9-1 [1 008 B]
Réception de : 2 http://mirror.steadfast.net/debian/ stable/main
python-all amd64 2.7.9-1 [996 B]
Réception de : 3 http://mirror.steadfast.net/debian/ stable/main
python-all-dev amd64 2.7.9-1 [1 024 B]
3 028 o réceptionnés en 1s (2 003 o/s)  
Sélection du paquet libpython-all-dev:amd64 précédemment désélectionné.
(Lecture de la base de données... 164037 fichiers et répertoires déjà
installés.)
Préparation du dépaquetage de .../libpython-all-dev_2.7.9-1_amd64.deb
...
Dépaquetage de libpython-all-dev:amd64 (2.7.9-1) ...
Sélection du paquet python-all précédemment désélectionné.
Préparation du dépaquetage de .../python-all_2.7.9-1_amd64.deb ...
Dépaquetage de python-all (2.7.9-1) ...
Sélection du paquet python-all-dev précédemment désélectionné.
Préparation du dépaquetage de .../python-all-dev_2.7.9-1_amd64.deb ...
Dépaquetage de python-all-dev (2.7.9-1) ...
Paramétrage de libpython-all-dev:amd64 (2.7.9-1) ...
Paramétrage de python-all (2.7.9-1) ...
Paramétrage de python-all-dev (2.7.9-1) ...

anovakovski@HPBox:~/Projets/CGG/nagios-plugin-mongodb$ sudo apt-get
install python-pip
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Les paquets supplémentaires suivants seront installés : 
  python-cffi-backend python-colorama python-cryptography python-
distlib python-enum34 python-idna python-ipaddress python-ndg-
httpsclient
  python-openssl python-pyasn1 python-requests python-setuptools
python-urllib3 python-wheel
Paquets suggérés :
  python-cryptography-doc python-cryptography-vectors python-enum34-doc 
python-openssl-doc python-openssl-dbg doc-base python-setuptools-doc
  python-ntlm
Paquets recommandés :
  python-dev-all
Les NOUVEAUX paquets suivants seront installés :
  python-cffi-backend python-colorama python-cryptography python-
distlib python-enum34 python-idna python-ipaddress python-ndg-
httpsclient
  python-openssl python-pip python-pyasn1 python-requests python-
setuptools python-urllib3 python-wheel
0 mis à jour, 15 nouvellement installés, 0 à enlever et 31 non mis à
jour.
Il est nécessaire de prendre 1 138 ko dans les archives.
Après cette opération, 5 495 ko d'espace disque supplémentaires seront
utilisés.
Souhaitez-vous continuer ? [O/n] 
Réception de : 1 http://mirror.steadfast.net/debian/ testing/main
python-cffi-backend amd64 1.2.1-1+b1 [58,2 kB]
Réception de : 2 http://mirror.steadfast.net/debian/ testing/main
python-colorama all 0.3.3-1 [21,4 kB]
Réception de : 3 http://mirror.steadfast.net/debian/ testing/main
python-enum34 all 1.0.4-3 [27,3 kB]
Réception de : 4 http://mirror.steadfast.net/debian/ testing/main
python-idna all 2.0-3 [35,7 kB]
Réception de : 5 http://mirror.steadfast.net/debian/ testing/main
python-ipaddress all 1.0.14-2 [17,9 kB]
Réception de : 6 http://mirror.steadfast.net/debian/ testing/main
python-pyasn1 all 0.1.9-1 [51,4 

Bug#803047: override: pyrite-publisher:text/optional

[Daniel Stender]

Package: ftp.debian.org
Severity: normal

Hello,

the former Section of pyrite-publisher "otherosfs" (software to run
programs compiled for other operating systems, and to use their
filesystems) isn't accurate, this app is for converting text and HTML
documents into formats for Palm PDAs, thus "text" is more appropriate.

the former Priority "extra" has been changed to "optional", the package
doesn't conflict with any other package and could be installed in terms
of what the Debian Policy (2.5) says about "optional", so "extra" isn't
accurate, either.

Thanks,
Daniel Stender

Bug#771829: python-googlecloudapis: build-depend on python-setuptools and python3-setuptools

[Chris Lamb]

severity 771829 serious
thanks

Logan Rosen wrote:

> This package's setup.py imports setuptools, but it doesn't build-depend
> on python-setuptools or python3-setuptools, which causes an FTBFS in
> Ubuntu

.. and in Debian too; raising severity.


Regards,

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

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Gianfranco Costamagna]

Hi,

>Well I had no modules for framebuffer, so Xorg would not run because of "no 
>video card" and no modules for network interfaces.
we don't provide any graphical kernel module AFAIK, so I don't think we can mess
with framebuffer.


TBH we have a guest module that might have some graphical interaction, but 
nothing
on host.

cheers,

G.

Bug#803051: cpl-plugin-naco: please make the build reproducible

[Chris Lamb]

Source: cpl-plugin-naco
Version: 4.4.0+dfsg-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness 
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed that
cpl-plugin-naco could not be built reproducibly.

The attached patch removes randomness from the build system. Once
applied, cpl-plugin-naco can be built reproducibly using our
reproducible
toolchain.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/create_manpage.py  2015-10-26 11:30:54.249833214 +
--- b/debian/create_manpage.py  2015-10-26 11:37:53.466486006 +
@@ -70,7 +70,7 @@
 pipeline = sys.argv[1]
 
 cpl.Recipe.path = "recipes"
-recipes = cpl.Recipe.list()
+recipes = sorted(cpl.Recipe.list())
 
 def param(recipe, template):
 return "".join(template.format(name = p.name,

Bug#801435: dgit: avoiding/fixing "Source-only uploads to NEW are not allowed"

[Ian Jackson]

Johannes Schauer writes ("Bug#801435: dgit: avoiding/fixing "Source-only 
uploads to NEW are not allowed""):
> So I tried using --deliberately-include-questionable-history when doing `dgit
> push` but this just results in:

I think I must have confused myself and you when I wrote my earlier
advice.

In Debian
  dgit push --deliberately-include-questionable-history
is applicable only for a completely-NEW source package.

Ian.

Bug#802088: openpyxl Git repository lagging way behind

[Andreas Tille]

Hi,

since python-skbio is in danger of beeing removed due to

  802088: openpyxl: FTBFS: /bin/sh: 1: python3.5: not found

I intended to have a look into openpyxl.  I noticed that the packaging
Git is lagging *way* behind the current package.

Did you moved the repository and forgot to update Vcs-Git or did you
forget to push?

(for sure I'd be even more happy if you simply fix the bug :-P)

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#777930: ksh

[Nicholas Bamber]

owner 777930 nicho...@periapt.co.uk
thanks

The upload was rejected but I will try again.

Bug#803048: moksha.common: FTBFS: rm: cannot remove 'debian/python-

[Chris Lamb]

tags 803048 + patch
thanks

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/rules b/debian/rules
index d3c53a7..523cf07 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,7 @@
 
 override_dh_install:
dh_install -Xusr/bin/moksha
-   rm 
debian/python-moksha.common/usr/lib/python*/dist-packages/moksha.common-*.egg-info/SOURCES.txt
+   rm -f 
debian/python-moksha.common/usr/lib/python*/dist-packages/moksha.common-*.egg-info/SOURCES.txt
 
 
 override_dh_auto_test:

Bug#803052: ITP: fonts-sil-andikanewbasic -- Smart Unicode Latin/Greek fonts for literacy (full family of styles)

[Daniel Glassey]

Package: wnpp
Severity: wishlist
Owner: Daniel Glassey 
X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org

Package name: fonts-sil-andikanewbasic
Version: 5.500
Upstream Author: SIL International http://scripts.sil.org/Support
URL: http://scripts.sil.org/Andika_New_Basic
License: Open Font License 1.1 with Reserved Font Names "Andika" and "SIL"
Description: Smart Unicode Latin/Greek fonts for literacy (full family of
styles)
 Andika ("Write!" in Swahili) is a sans serif, Unicode-compliant font
 designed especially for literacy use, taking into account the needs of
 beginning readers. The focus is on clear, easy-to-perceive letterforms that
 will not be easily confused with one another.

 A sans serif font is preferred by some literacy personnel for teaching
 people to read. Its forms are simpler and less cluttered than some serif
 fonts can be. For years, literacy workers have had to make do with fonts
 that were available but not really suitable for beginning readers and
 writers. In some cases, literacy specialists have had to tediously cobble
 together letters from a variety of fonts in order to get the all of
 characters they need for their particular language project, resulting in
 confusing and unattractive publications. Andika addresses those issues.

 Andika New Basic is a limited-character-set version of Andika that includes
 a full family of styles (Regular, Bold, Italic and Bold-Italic).

 In particular, these fonts do not support:
   Full extended Latin IPA
   Complete support for Central European languages
   Greek
   Cyrillic

Bug#803016: Is this only an issue on 686 and not amd64 servers?

[Chris Croome]

Hi

I have had this issue on one server but not others, the only difference
I can think of being, the one with the issue is running 2.6.32-5-686 and
the others are running 2.6.32-5-xen-amd64 -- is the issue related to the
lack of support for "activate-noawait" in x86 kernal or something like
that?

All the best

Chris

-- 
Webarchitects Co-operative
http://webarchitects.coop/
+44 114 276 9709
@webarchcoop

Bug#803026: guilt uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: guilt
Version: 0.35-1.2
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the guilt package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' guilt-0.35
guilt-0.35/guilt:   find "`dirname $0`/../lib/guilt" -maxdepth 1 -name 
"guilt-*" -type f -perm +111 2> /dev/null | sed -e "s/.*\\/`basename $0`-//"
guilt-0.35/guilt:   find "`dirname $0`" -maxdepth 1 -name "guilt-*" -type f 
-perm +111 | sed -e "s/.*\\/`basename $0`-//"
guilt-0.35/.pc/drop-dependency-check.patch/guilt:   find "`dirname 
$0`/../lib/guilt" -maxdepth 1 -name "guilt-*" -type f -perm +111 2> /dev/null | 
sed -e "s/.*\\/`basename $0`-//"
guilt-0.35/.pc/drop-dependency-check.patch/guilt:   find "`dirname $0`" 
-maxdepth 1 -name "guilt-*" -type f -perm +111 | sed -e "s/.*\\/`basename 
$0`-//"
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#782080:

[Dylan]

Should be fixed since libmtp 1.1.9 [1]


[1]
http://sourceforge.net/p/libmtp/code/ci/ef422d81b25fd0c772c9b014bc46b1e6e0524922/

Bug#803030: autopsy uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: autopsy
Version: 2.24-1
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the autopsy package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' autopsy-2.24
autopsy-2.24/Makefile:  find . -type f -perm +g+x,o+x,u+x | xargs  chmod -x
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803027: freevo uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: freevo
Version: 1.9.2b2-4.2
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the freevo package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' freevo-1.9.2b2
freevo-1.9.2b2/runtime/Makefile:find apps -perm +111 -type f -exec 
strip {} \;
freevo-1.9.2b2/runtime/Makefile:find lib -name "*.py" -perm +0111 -exec 
chmod ugo-x \{\} \;
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#800650: Create development header packages

[Michael D]

Any news on this? Maintainers alive?

Bug#800618: [ycmd] C++ checker reports errors not being able to find standard header (stddef.h)

[Jan Hudec]

On Sunday 25 of October 2015 11:27:18 Onur Aslan wrote:
> Looks like libclang-common-3.6-dev dependency is missing from package.

I do have full clang suite including that package installed, so adding it 
(though it obviously is correct to add it) will _not_ fix this bug.

When I remove the /usr/lib/ycmd/clang_includes -> /usr/lib/clang/3.6/include
symlink, ycmd still gives the "cannot find stddef.h" errors. Either the 
symlink needs to be also added, the default flags in ycmd (in 
/usr/lib/ycmd/ycmd/completers/cpp/flags.py:256) need to be adjusted to yield 
/usr/lib/clang/3.6/include (which points to the headers provided by libclang-
common-3.6-dev), or somehow (but I don't know how) libclang has to be made to 
use the correct defaults itself.

-- 
 - Jan Hudec 

Bug#803016: libxml2: Upgrade fails with "triggers ci file contains unknown directive `activate-noawait'"

[Tore Anderson]

Package: libxml2
Version: 2.7.8.dfsg-2+squeeze13
Severity: important


This console output probably says it all:

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libxml2
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/813 kB of archives.
After this operation, 241 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 33143 files and directories currently installed.)
Preparing to replace libxml2 2.7.8.dfsg-2+squeeze12 (using 
.../libxml2_2.7.8.dfsg-2+squeeze13_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libxml2_2.7.8.dfsg-2+squeeze13_i386.deb (--unpack):
 triggers ci file contains unknown directive `activate-noawait'
configured to not write apport reports
  Errors were encountered while processing:
 /var/cache/apt/archives/libxml2_2.7.8.dfsg-2+squeeze13_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- System Information:
Debian Release: 6.0.10
  APT prefers squeeze-lts
  APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-xen-686 (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

Versions of packages libxml2 depends on:
ii  libc6   2.11.3-4+deb6u7  Embedded GNU C Library: Shared lib
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages libxml2 recommends:
pn  xml-core   (no description available)

libxml2 suggests no packages.

-- no debconf information

Bug#803021: request-tracker4 uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: request-tracker4
Version: 4.2.12-3
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the request-tracker4 package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' request-tracker4-4.2.12/
request-tracker4-4.2.12/Makefile.in:# Note that we use the deprecated (by 
GNU/POSIX find) -perm +0NNN syntax
request-tracker4-4.2.12/Makefile.in:( cd etc/upgrade && find . -type f -not 
-name '*.in' -perm +0111 -print ) | while read file ; do \
request-tracker4-4.2.12/Makefile:   # Note that we use the deprecated (by 
GNU/POSIX find) -perm +0NNN syntax
request-tracker4-4.2.12/Makefile:   ( cd etc/upgrade && find . -type f -not 
-name '*.in' -perm +0111 -print ) | while read file ; do \
request-tracker4-4.2.12/.pc/no_testdeps.diff/Makefile.in:   # Note that we 
use the deprecated (by GNU/POSIX find) -perm +0NNN syntax
request-tracker4-4.2.12/.pc/no_testdeps.diff/Makefile.in:   ( cd 
etc/upgrade && find . -type f -not -name '*.in' -perm +0111 -print ) | while 
read file ; do \
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#802382: transition: qtbase-opensource-src

[Emilio Pozuelo Monfort]

On 26/10/15 05:31, Adam Majer wrote:
> Package: release.debian.org
> Followup-For: Bug #802382
> 
> Hello,
> 
> Qt Creator is now uploaded with reduced build-depends to
> 
>   libclang-3.7-dev | libclang-3.6-dev
> 
> What is a little puzzling is that on s390x, libclang-3.7 is
> uninstallable, OK. But then libclang-3.6-dev is not attempted at
> all.
> 
> Is this by design? Shouldn't build with libclang-3.6-dev be attempted?

That's by design, only the first alternative is tried by sbuild. So we either
need a fixed llvm-toolchain-3.7 package, or to build against 3.6 on various
arches (s390x, mips and powerpc, which don't have llvm 3.7 in testing).

Cheers,
Emilio

Bug#803018: troffcvt uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: troffcvt
Version: 1.04-21
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the troffcvt package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM/troffcvt-1.04$ grep -r -- '-perm +'
debian/rules:file_list=`find subdir -name \*.[ah] -o -perm +111 -a -type f`; \
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803024: libembperl-perl uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: libembperl-perl
Version: 2.5.0-4
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the libembperl-perl package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' libembperl-perl-2.5.0
libembperl-perl-2.5.0/debian/rules: find eg blib/lib -type f -a -perm +111 
-exec chmod -x \{\} \;
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803033: catdoc: non-free Unicode files

[Dmitry Smirnov]

Source: catdoc
Version: 0.94.4-1.1
Severity: serious

According to their headers, the following files are non-free:

Files:
charsets/8859-1.txt 

   
charsets/8859-2.txt 

   
charsets/8859-3.txt 

   
charsets/8859-4.txt 

   
charsets/8859-5.txt 

   
charsets/8859-6.txt 

   
charsets/8859-7.txt 

   
charsets/8859-8.txt 

   
charsets/8859-9.txt 

   
charsets/big5.txt   

   
charsets/cns11643.txt   

   
charsets/jis0201.txt

   
charsets/jis0208.txt

   
charsets/jis0212.txt

   
charsets/shiftjis.txt   

   
Copyright:  

   
1991-1995 Unicode, Inc  

   
License: Unicode-noDistribute   

 [disclaimer excluded]
 .
 Recipient is granted the right to make copies in any form for
 internal distribution and to freely use the information supplied
 in the creation of products supporting Unicode.  Unicode, Inc.
 specifically excludes the right to re-distribute this file directly
 to third parties or other organizations whether for profit or not.

Please investigate.

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

"All government, of course, is against liberty.
-- H. L. Mencken


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

Bug#803019: timidity uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: timidity
Version: 2.13.2-40.2
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the timidity package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM/timidity-2.13.2$ grep -r -- '-perm +'
debian/rules:   -find -type f -perm +111 ! -name 'rules' -exec chmod 644 {} \;
debian/patches/debian-changes-2.13.2-36:+   find -type f -perm +111 
! -name '.*' -fprint debian/executable.files
autogen.sh: find -type f -perm +111 ! -name '.*' -fprint 
debian/executable.files
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803020: switchconf uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: switchconf
Version: 0.0.9-2
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the switchconf package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' switchconf-0.0.9/
switchconf-0.0.9/switchconf:for r in `find ${scriptsdir} -type f -perm +1 | 
sort`; do
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803022: php-fpdf uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: php-fpdf
Version: 3:1.7.dfsg-1
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the php-fpdf package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' php-fpdf-1.7.dfsg
php-fpdf-1.7.dfsg/debian/rules: find $(DEB_DESTDIR) -type f -and -perm +111 
-print0 | xargs -0ri chmod a-x '{}'
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803023: mongrel2 uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: mongrel2
Version: 1.10.0-1
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the mongrel2 package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' mongrel2-1.10.0
mongrel2-1.10.0/debian/rules:   find "$$(pwd)/debian/mongrel2-core" -name 
"*.css" -perm +a+x -exec chmod -x "{}" \;
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803016: libxml2: Upgrade fails with "triggers ci file contains unknown directive `activate-noawait'"

[Martin Fiala]

I've got the same problem on one machine, while on two others it 
installed without problems.


"apt-get -f install" and "dpkg --configure -a" does not report any 
problem, but upgrading the package fails:


Preparing to replace libxml2 2.7.8.dfsg-2+squeeze12 (using 
.../libxml2_2.7.8.dfsg-2+squeeze13_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libxml2_2.7.8.dfsg-2+squeeze13_i386.deb (--unpack):

 triggers ci file contains unknown directive `activate-noawait'
configured to not write apport reports
  Errors were encountered while 
processing:

 /var/cache/apt/archives/libxml2_2.7.8.dfsg-2+squeeze13_i386.deb

ii  dpkg 1.15.12   
Debian package management system

ii  libc6 2.11.3-4+deb6u7 Embedded GNU C Library: Shared libraries
ii  zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime

Martin Fiala

Bug#803032: openvpn: Start before user sessions to avoid hiding password prompt

[Martin Pitt]

Package: openvpn
Version: 2.3.7-2
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch xenial

Hello,

openvpn's SysV init script has

  X-Start-Before:$x-display-manager gdm kdm xdm wdm ldm sdm nodm

to make sure that display managers wait for openvpn to start.
Otherwise it could happen that openvpn asks for a password, and then
the display manager clobbers the screen by starting X.

However, this is missing in the systemd unit. This will do the same
thing for all DMs plus gettys, by sorting before the
systemd-user-sessions.service synchronization point.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
 - Run openvpn@.service before systemd-user-sessions.service to avoid
   gettys and display managers starting on top of possible password prompts.
   This provides the equivalent of the init.d script's X-Start-Before:.
diff -pruN 2.3.7-1/debian/openvpn@.service 2.3.7-1ubuntu1/debian/openvpn@.service
--- 2.3.7-1/debian/openvpn@.service	2015-07-07 09:54:33.0 +
+++ 2.3.7-1ubuntu1/debian/openvpn@.service	2015-07-08 10:28:10.0 +
@@ -2,6 +2,7 @@
 Description=OpenVPN connection to %i
 PartOf=openvpn.service
 ReloadPropagatedFrom=openvpn.service
+Before=systemd-user-sessions.service
 Documentation=man:openvpn(8)
 Documentation=https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage
 Documentation=https://community.openvpn.net/openvpn/wiki/HOWTO


signature.asc
Description: Digital signature

Bug#803010: nmu: libjson0 reverse dependencies

[Emilio Pozuelo Monfort]

On 26/10/15 09:34, Emilio Pozuelo Monfort wrote:
> On 26/10/15 02:04, Michael Biebl wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: binnmu
>>
>> Hi,
>>
>> libjson0 is a transitional package built from src:json-c and currently
>> three packages still depend on it: libxr, mypaint and upstart.
>>
>> Rebuilding those packages will make them depend on the non-transitional
>> libjson-c2 package. Thus please schedule the following binNMUs
>>
>> nmu libxr_1.0-2.1 . ANY . unstable . -m "Rebuild against libjson-c2"
>> nmu mypain_1.1.0-3 . ANY . unstable . -m "Rebuild against libjson-c2"

^ Should have been mypaint, I guess. (Scheduled.)

Emilio

>> nmu upstart_1.11-5 . ANY . unstable . -m "Rebuild against libjson-c2"
> 
> Scheduled.
> 
> Emilio
> 

Bug#801549: gitg: new upstream release available (3.18.0)

[Dmitry Smirnov]

On Sunday 25 October 2015 14:25:28 Jérémy Lal wrote:
> I'm trying to find how to fix it.

Thanks. I hope you have some ideas about it or we will just have to open 
upstream bug...


> Please also accept my apologies for the non-friendly tone i had before.

No worries. :)

By the way thank you for your work on Redmine which I use fairly often. ;)

-- 
Cheers,
 Dmitry Smirnov.


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

Bug#803037: synfigstudio: FTBFS: uimanager.h:33:27: fatal error: sigc++/object.h: No such file or directory

[Chris Lamb]

Source: synfigstudio
Version: 1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

synfigstudio fails to build from source in unstable/amd64:

  [..]

  libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I../../src
  -I../../libltdl -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT
  -std=c++11 -I/usr/include/synfig-1.0 -I/usr/include/giomm-2.4
  -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include
  -I/usr/include/libxml++-2.6
  -I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include
  -I/usr/include/libxml2 -I/usr/include/glibmm-2.4
  -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include
  -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
  -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0
  -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
  -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/mlt++
  -I/usr/include/mlt -I/usr/include/sigc++-2.0
  -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include
  -DLOCALEDIR=\"/usr/share/locale\" -fstack-protector-strong -Wformat
  -Werror=format-security -DNDEBUG -g -O2 -W -Wall -c
  actions/activepointadd.cpp  -fPIC -DPIC -o
  actions/.libs/libsynfigapp_la-activepointadd.o
  In file included from uimanager.cpp:32:0:
  uimanager.h:33:27: fatal error: sigc++/object.h: No such file or
  directory
  compilation terminated.
  Makefile:2128: recipe for target 'libsynfigapp_la-uimanager.lo' failed
  make[5]: *** [libsynfigapp_la-uimanager.lo] Error 1
  make[5]: *** Waiting for unfinished jobs
  In file included from canvasinterface.cpp:58:0:
  canvasinterface.h:34:27: fatal error: sigc++/object.h: No such file or
  directory
  compilation terminated.
  In file included from action_system.cpp:32:0:
  action_system.h:32:27: fatal error: sigc++/object.h: No such file or
  directory
  compilation terminated.
  Makefile:2058: recipe for target 'libsynfigapp_la-action_system.lo'
  failed
  make[5]: *** [libsynfigapp_la-action_system.lo] Error 1
  Makefile:2079: recipe for target 'libsynfigapp_la-canvasinterface.lo'
  failed
  make[5]: *** [libsynfigapp_la-canvasinterface.lo] Error 1
  In file included from action.cpp:34:0:
  instance.h:39:27: fatal error: sigc++/object.h: No such file or
  directory
  compilation terminated.
  Makefile:2044: recipe for target 'libsynfigapp_la-action.lo' failed
  make[5]: *** [libsynfigapp_la-action.lo] Error 1
  In file included from instance.cpp:34:0:
  instance.h:39:27: fatal error: sigc++/object.h: No such file or
  directory
  compilation terminated.
  Makefile:2100: recipe for target 'libsynfigapp_la-instance.lo' failed
  make[5]: *** [libsynfigapp_la-instance.lo] Error 1
  In file included from actions/activepointremove.cpp:34:0:
  ../../src/synfigapp/canvasinterface.h:34:27: fatal error:
  sigc++/object.h: No such file or directory
  compilation terminated.
  Makefile:1330: recipe for target
  'actions/libsynfigapp_la-activepointremove.lo' failed
  make[5]: *** [actions/libsynfigapp_la-activepointremove.lo] Error 1
  In file included from actions/activepointadd.cpp:34:0:
  ../../src/synfigapp/canvasinterface.h:34:27: fatal error:
  sigc++/object.h: No such file or directory
  compilation terminated.
  In file included from main.cpp:32:0:
  main.h:38:27: fatal error: sigc++/object.h: No such file or directory
  compilation terminated.
  In file included from inputdevice.cpp:37:0:
  main.h:38:27: fatal error: sigc++/object.h: No such file or directory
  compilation terminated.
  In file included from action_param.cpp:34:0:
  canvasinterface.h:34:27: fatal error: sigc++/object.h: No such file or
  directory
  compilation terminated.
  Makefile:1323: recipe for target
  'actions/libsynfigapp_la-activepointadd.lo' failed
  make[5]: *** [actions/libsynfigapp_la-activepointadd.lo] Error 1
  Makefile:2107: recipe for target 'libsynfigapp_la-main.lo' failed
  make[5]: *** [libsynfigapp_la-main.lo] Error 1
  Makefile:2093: recipe for target 'libsynfigapp_la-inputdevice.lo'
  failed
  make[5]: *** [libsynfigapp_la-inputdevice.lo] Error 1
  Makefile:2051: recipe for target 'libsynfigapp_la-action_param.lo'
  failed
  make[5]: *** [libsynfigapp_la-action_param.lo] Error 1
  In file included from pluginmanager.cpp:43:0:
  ../../src/synfigapp/main.h:38:27: fatal error: sigc++/object.h: No
  such file or directory
  compilation terminated.
  Makefile:2114: recipe for target 'libsynfigapp_la-pluginmanager.lo'
  failed

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/synfigstudio_1.0-1.build1.log.gz


Regards,

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


synfigstudio.1.0-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#782763: RFP: sirius -- Speech and Vision Based Intelligent Personal Assistant

[Iain R. Learmonth]

Control: retitle -1 RFP: sirius -- Speech and Vision Based Intelligent Personal 
Assistant
Control: noowner -1

Hi,

I'm not going to have the time available to follow through with this ITP, so
converting to an RFP. Hopefully there is someone who has interest in
packaging this.

If you're new to Debian Development and you'd like to have a go at this,
your starting point is http://mentors.debian.net/intro-maintainers.

I will be happy to review and sponsor uploads of this package. Just send me
an email and we can get to work.

Thanks,
Iain.

-- 

Bug#802989: [pkg-php-pear] Bug#802989: Composer: ~5 translates badly as (>= 5) and (<< 1~~)

[Mathieu Parent]

2015-10-25 21:03 GMT+01:00 David Prévot :
> Package: pkg-php-tools
> Version: 1.30
> Severity: normal
>
> Hi,

Hi David,

> While looking at the latest (2.0.1) version of phpunit-dbunit (Vcs up to
> date, except the changelog entry), I noticed that the following entry in
> composer.json:
>
> "require": {
> […]
> "phpunit/phpunit": "~5",
>
> was translated as “phpunit (>= 5), phpunit (<< 1~~)” by dh_phpcomposer,
> making the package uninstallable (even if phpunit 5 were available),
> instead of the expected “phpunit (>= 5), phpunit (<< 6~~)”.

Accorind to doc (https://getcomposer.org/doc/articles/versions.md#tilde):

Note: The ~ operator has an exception on its behavior for the major
release number. This means for example that ~1 is the same as ~1.0 as
it will not allow the major number to increase trying to keep
backwards compatibility.

> I haven’t tracked down the issue, sorry, but filling a bug report not to
> forget it.

Will fix and upload shortly (hopefully).

Regards
-- 
Mathieu

Bug#803017: /usr/bin/wxglade: Unicode error when cut flexgridsizer with contents

[Miloslav Semler]

Package: python-wxglade
Version: 0.7.1~rc1-3
Severity: important
File: /usr/bin/wxglade

Dear Maintainer,
recently I wanted to cut and paste flex grid sizie with contents (textbox, 
alebel, etc.) and
I got following error:

ERROR   : None
An unexpected error occurred!

Date and time:   2015-10-26T07:33:07.519003
Python version:  2.7.9
wxPython version:3.0.1.1
wxWidgets platform:  __WXGTK__
wxGlade version: 0.7.0
Language code:   cs_CZ
Encoding:UTF-8
Filesystem encoding: UTF-8

Exception type:  
Exception details:   'ascii' codec can't encode character u'\u0159' in position 
785: ordinal not in range(128)
Application stack trace:
Stack frame at level 0
==
  File 
"/usr/lib/python2.7/dist-packages/wxGlade-0.7.0-py2.7.egg/wxglade/clipboard.py",
 line 34
  Function "_widget2repr(self=, *args=('1', 0, '0', 
u'\n0\n
1\n4\n
0\n1\n0\n
\nwxEXPAND\n
0\n1\n\n 
   0\n1\n3\n 
   0\n\n
wxALL\n5\n
0\n\nP\u0159idat lot\n

 \nPridatLot\n\n 
   \n\n\nwxALL\n
5\n0\n\n  
  Zobraz/M\u011b\u0159 lot\n
1\n\n
ZobrazLot\n
\n\n\n
\nwxALL\n
5\n0\n\n   
 Kop\xedrovat...\n<
 events>\nLotCopy\n\n   
 \n\n\n\n
\nwxALL|wxEXPAND\n
5\n1\n\n600, 350\n   
 1\n0\n 
   1\n
0\n
1\n
1\n
1\n
wxGrid.wxGridSelectRows\n
\nID\n
Popis/pozn\xe1mka\nKus\u016f v s\xe9rii\nSledovan\xe1 lambda\nTyp\n\n\n  
  TlacitkaLoty\n   
 TlacitkaLoty\n 
   \n\n\n\nwxEXPAND\n5\n 
   1\n\n0\n 
   1\n2\n0\n 
   \nwxALL\n 
   5\n0\n 
   \n
 P\u0159edchoz\xed\n
1\n\n
LotyPrev\n\n 
   \n\n\nwxALL\n
5\n0\n\n
Dal\u0161\xed \n
1\n\n
LotyNext\n\n 
   \n\n\n
\n\nwxEXPAND\n  
  0\n0\n\nwxLI_HORIZONTAL\n
1\n\n\n\n'))"
  Source code context:
  *args contains option, flag, border, xml_str.
  """
  assert len(args) == 4
  ->  return ":".join([str(elem) for elem in args])
  
  def GetWidgetData(self):
  """\
  Local variables:
  -> self (): 

  -> args (): ('1',
 0,
 '0',
 u'\n0\n
1\n4\n
0\n1\n0\n
\nwxEXPAND\n
0\n1\n\n 
   0\n1\n3\n 
   0\n\n
wxALL\n5\n
0\n\nP\u0159idat lot\n
\nPridatLot\n\n 
   \n
 \n\n
wxALL\n5\n
0\n\n
Zobraz/M\u011b\u0159 lot\n
1\n\n
ZobrazLot\n
\n\n\n
\nwxALL\n
5\n0\n\n   
 Kop\xedrovat...\n\n 
   LotCopy\n
\n\n   
  \n\n\n\n 
   wxALL|wxEXPAND\n5\n
1\n\n600, 350\n
1\n0\n  
  1\n
0\n
1\n
1\n
1\n
wxGrid.wxGridSelectRows\n
\nID\n
Popis/pozn\xe1mka\nKus\u016f v s\xe9rii\nSledovan\xe1 lambda\nTyp\n\n\nTlacitkaLoty\n

Bug#798872: RFS: python-pbcommand (NEW)

[Afif Elghraoui]

Hi, all,
I've finished preparing the python-pbcommand package. This is part of
the smrtanalysis suite for long-read DNA sequencing data analysis.

git+ssh://git.debian.org/git/debian-med/python-pbcommand.git
http://anonscm.debian.org/cgit/debian-med/python-pbcommand.git

Many thanks and regards
Afif

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

Bug#803031: patch: support serial serial dev/serial/by-path names

[Riku Voipio]

Package: ser2net
Version: 2.9.1-1
Severity: wishlist
Tags: patch

Hi,

ser2net uses : as field separator in ser2net.conf. Udev creates by-path and
by-id paths to identify unique serial ports. These paths are highly
useful as ttyUSB* might end up shuffling around.

But the by-path symlink has always a : in the filename, and by-id might:

# arndale
7001:telnet:0:'/dev/serial/by-path/pci-:00:1d.0-usb-0:1.8.4.2:1.0-port0':115200
8DATABITS NONE 1STOPBIT

In this case the by-id doesn't, but it illustrates that the name comes
from the device and can have anything in the name. 

The attached patch adds quoting to ser2net device name:

--- x/ser2net-2.9.1/readconfig.c2013-07-24 19:04:39.0 +0300
+++ ser2net-2.9.1/readconfig.c  2015-10-26 09:55:53.973462321 +0200
@@ -379,7 +379,14 @@
return;
 }
 
-devname = strtok_r(NULL, ":", _data);
+if (strtok_data[0] == '\'') {
+/* device name may contains character ':'
+ eg. 
2003:raw:5:'/dev/serial/by-path/pci-:00:1d.1-usb-0:2.1:1.0-port0':9600 */
+devname = strtok_r(NULL, "'", _data);
+}
+else {
+devname = strtok_r(NULL, ":", _data);
+}
 if (devname == NULL) {
syslog(LOG_ERR, "No device name given on line %d", lineno);
return;


origin of patch:

https://github.com/Lingku/mser2net/commit/e36aa4b12d896e056c13759105ee9380c1f20fbe

Github seems to carry severaly useful forks of ser2net, all in having
useful features yet not beeing very actively maintained :(

https://github.com/longshine/ser2nets
https://github.com/Lingku/mser2net

Riku

Bug#803010: nmu: libjson0 reverse dependencies

[Michael Biebl]

Am 26.10.2015 um 09:38 schrieb Emilio Pozuelo Monfort:
> On 26/10/15 09:34, Emilio Pozuelo Monfort wrote:
>> On 26/10/15 02:04, Michael Biebl wrote:

>>> nmu mypain_1.1.0-3 . ANY . unstable . -m "Rebuild against libjson-c2"
> 
> ^ Should have been mypaint, I guess. (Scheduled.)

Indeed. Sorry for the C failure.

>>> nmu upstart_1.11-5 . ANY . unstable . -m "Rebuild against libjson-c2"
>>
>> Scheduled.

Thanks, Emilio.

Regards,
Michael

-- 
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#803035: apache2: mod_socache_memcache does not reuse memcache connections

[Valentin Vidic]

Package: apache2
Version: 2.4.10-10+deb8u3
Severity: normal
Tags: upstream

Dear Maintainer,

While trying to use memcache for SSL sessions

  SSLSessionCache memcache:127.0.0.1

I noticed the connection to the memcache server is not reused but dropped and
recreated on every request. This can be checked using tcpdump.

This issue has been reported and fixed upstream in 2.4.17:

  *) mod_socache_memcache: Add the 'MemcacheConnTTL' directive to control how 
 long to keep idle connections with the memcache server(s).
 Change default value from 600 usec (!) to 15 sec. PR 58091
 [Christophe Jaillet]

  https://bz.apache.org/bugzilla/show_bug.cgi?id=58091
  https://svn.apache.org/viewvc?view=revision=1696105

Is it possible to add this change to jessie?

-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin2.4.10-10+deb8u3
ii  apache2-data   2.4.10-10+deb8u3
ii  apache2-utils  2.4.10-10+deb8u3
ii  dpkg   1.17.25
ii  lsb-base   4.1+Debian13+nmu1
ii  mime-support   3.58
ii  perl   5.20.2-3+deb8u1
ii  procps 2:3.3.9-9

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.35

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  elinks [www-browser] 0.12~pre6-5+b2
ii  links [www-browser]  2.8-2+b3
ii  lynx-cur [www-browser]   2.8.9dev1-2+deb8u1

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.1-3
ii  libaprutil1  1.5.4-1
ii  libaprutil1-dbd-sqlite3  1.5.4-1
ii  libaprutil1-ldap 1.5.4-1
ii  libc62.19-18+deb8u1
ii  libldap-2.4-22.4.40+dfsg-1+deb8u1
ii  liblua5.1-0  5.1.5-7.1
ii  libpcre3 2:8.35-3.3
ii  libssl1.0.0  1.0.1k-3+deb8u1
ii  libxml2  2.9.1+dfsg1-5
ii  perl 5.20.2-3+deb8u1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  elinks [www-browser] 0.12~pre6-5+b2
ii  links [www-browser]  2.8-2+b3
ii  lynx-cur [www-browser]   2.8.9dev1-2+deb8u1

Versions of packages apache2 is related to:
ii  apache2  2.4.10-10+deb8u3
ii  apache2-bin  2.4.10-10+deb8u3

-- Configuration Files:
/etc/apache2/mods-available/ssl.conf changed [not included]
/etc/apache2/sites-available/000-default.conf changed [not included]
/etc/apache2/sites-available/default-ssl.conf changed [not included]

-- no debconf information

Bug#624076: rsyslog: Uses deprecated _set_priority GnuTLS functions

[Andreas Metzler]

On 2015-10-25 Michael Biebl  wrote:
[...]
> While 8.13.0 successfully builds with gnutls 3.4.0 now, it still seems
> to use gnutls_certificate_type_set_priority when available, so will
> trigger this build warning you referenced in your initial bug report.

> The upstream "fix" is to simply not use
> gnutls_certificate_type_set_priority if not available [1], you mentioned
> in your bug report that gnutls_priority_set_direct() should be used instead.

> Could you please follow up here or the upstream bug report if the
> upstream change really is sufficient or if there is still some work to
> be done.
[...]

Hello,

Thanks for the heads-up, I have added a comment to the upstream
report. Dropping gnutls_certificate_type_set_priority() is fine, since
rsyslog used it to limit certificate type to X.509. As this is gnutls'
default setting, the function call can be dropped.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803029: dbacl uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: dbacl
Version: 1.12-2.1
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the dbacl package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' dbacl-1.12
dbacl-1.12/src/mailtest.functions.in:FILTS=`find $FILTERS -type f -perm 
+0111 -exec basename {} \; | sort -u`
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803028: emscripten uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: emscripten
Version: 1.22.1-1
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the emscripten package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' emscripten-1.22.1
emscripten-1.22.1/tests/freealut/Makefile.in:   find . -type f \! -perm +222 \! 
-name "*.sh" -exec chmod +w {} \;
emscripten-1.22.1/tests/freealut/Makefile.am:   find . -type f \! -perm +222 \! 
-name "*.sh" -exec chmod +w {} \;
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803025: gutenprint uses deprecated find -perm +xxx syntax, please switch to find -perm /+++

[Andreas Metzler]

Package: gutenprint
Version: 5.2.10-3
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the gutenprint package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' gutenprint-5.2.10
gutenprint-5.2.10/debian/rules: find debian/printer-driver-gutenprint/usr/lib 
-type f -perm +0111 -print0 | xargs -0 chrpath --delete
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#803034: libgusb build-depends should be updated to 0.2.7

[Sebastien Bacher]

Package: gnome-multi-writer
Version: 3.18.0-1

The 3.17.92 update raised the libgusb requirement to 0.2.7, that should
be reflected in the control (would be a good idea to require glib 2.46
as well)

Cheers,
Sebastien Bacher

Bug#803036: qemu-system-x86: Qemu guest hangs 100% CPU on IO

[Gavin Pidgley]

Package: qemu-system-x86
Version: 2.1+dfsg-12~bpo70+1
Severity: important

Dear Maintainer,

We are seeing guests lockup/hang with qemu. The guests hang with 100% CPU
usage. The problem seems to be storage/IO related, but there is not necessarily
high IO happening on the host at the time the guest hangs.

At the time of the crash, the VNC console is not responsive and the only way to
resolve is to forcefully power off the guest and back on.

This guest shown below is running Debian Wheezy, but it seems to affect other
guests operating systems such as Windows, CentOS etc.

The hosts storage where guest disk images are stored is OCFS2 formatted running
over iSCSI.

Guests that have a disk cache of cache='writeback' and the qcow2 disk image
file created with qemu-img -o preallocation=metadata seem to be less frequently
affected, but none the less are still affected. We have also tried virtio-blk,
virtio-scsi, scsi and standard IDE for the disk controller on the guest, but
doesn't seem to improve things.

qemu-system-x86_64 -enable-kvm -name guest1 -S -machine pc-
i440fx-2.1,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp
1,sockets=1,cores=1,threads=1 -uuid 973bf27b-04f9-61dd-9272-de2467b599d5 -no-
user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/guest1.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
lsi,id=scsi0,bus=pci.0,addr=0x4 -drive file=/mnt/vm/guest1.img,if=none,id
=drive-scsi0-0-0,format=qcow2,cache=none -device scsi-hd,bus=scsi0.0,scsi-
id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=1 -netdev
tap,fd=31,id=hostnet0,vhost=on,vhostfd=42 -device virtio-net-
pci,netdev=hostnet0,id=net0,mac=52:54:00:9a:36:10,bus=pci.0,addr=0x3 -chardev
pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device
usb-tablet,id=input0 -vnc 127.0.0.1:9 -device cirrus-
vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on


A backtrace of a hung guest shows:

(gdb) bt
#0  0x7f6ce44fed5c in __lll_lock_wait () from /lib/x86_64-linux-
gnu/libpthread.so.0
#1  0x7f6ce44fa3a9 in _L_lock_926 () from /lib/x86_64-linux-
gnu/libpthread.so.0
#2  0x7f6ce44fa1cb in pthread_mutex_lock () from /lib/x86_64-linux-
gnu/libpthread.so.0
#3  0x7f6cea9849f9 in ?? ()
#4  0x7f6cea9313bb in ?? ()
#5  0x7f6cea66ebed in main ()
(gdb) info threads
  Id   Target Id Frame
  3Thread 0x7f6cdac4a700 (LWP 29599) "qemu-system-x86" 0x7f6ce4236de1
in ppoll () from /lib/x86_64-linux-gnu/libc.so.6
  2Thread 0x7f6c993ff700 (LWP 29601) "qemu-system-x86" 0x7f6ce44fc344
in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
* 1Thread 0x7f6cea49b900 (LWP 29596) "qemu-system-x86" 0x7f6ce44fed5c
in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0


(gdb) thread apply all bt

Thread 3 (Thread 0x7f6cdac4a700 (LWP 29599)):
#0  0x7f6ce4236de1 in ppoll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f6cea931f1b in ?? ()
#2  0x7f6cea933230 in ?? ()
#3  0x7f6cea924fdd in ?? ()
#4  0x7f6cea8925b6 in ?? ()
#5  0x7f6cea899676 in ?? ()
#6  0x7f6cea8998c5 in ?? ()
#7  0x7f6cea891bb7 in ?? ()
#8  0x7f6cea824929 in ?? ()
#9  0x7f6cea824078 in ?? ()
#10 0x7f6cea823f98 in ?? ()
#11 0x7f6cea6b2c79 in ?? ()
#12 0x7f6cea6b89bf in ?? ()
#13 0x7f6cea679163 in ?? ()
#14 0x7f6cea6b1cf5 in ?? ()
#15 0x7f6cea69d25c in ?? ()
#16 0x7f6ce44f7b50 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#17 0x7f6ce424195d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#18 0x in ?? ()

Thread 2 (Thread 0x7f6c993ff700 (LWP 29601)):
#0  0x7f6ce44fc344 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64
-linux-gnu/libpthread.so.0
#1  0x7f6cea984c19 in ?? ()
#2  0x7f6cea920b7b in ?? ()
#3  0x7f6cea920f50 in ?? ()
#4  0x7f6ce44f7b50 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5  0x7f6ce424195d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x in ?? ()

Thread 1 (Thread 0x7f6cea49b900 (LWP 29596)):
#0  0x7f6ce44fed5c in __lll_lock_wait () from /lib/x86_64-linux-
gnu/libpthread.so.0
#1  0x7f6ce44fa3a9 in _L_lock_926 () from /lib/x86_64-linux-
gnu/libpthread.so.0
#2  0x7f6ce44fa1cb in pthread_mutex_lock () from /lib/x86_64-linux-
gnu/libpthread.so.0
#3  0x7f6cea9849f9 in ?? ()
#4  0x7f6cea9313bb in ?? ()
#5  0x7f6cea66ebed in main ()

Host system information:

Linux 3.14-0.bpo.2-amd64 #1 SMP Debian 3.14.15-2~bpo70+1 (2014-08-21) x86_64
GNU/Linux

qemu-kvm   1:2.1+dfsg-12~bpo70+1  amd64
qemu-system-x861:2.1+dfsg-12~bpo70+1  amd64


Though not quite the same situation, google yeilds similar problems:

Bug#802912: nmu: openmw_0.36.1-1

[Emilio Pozuelo Monfort]

On 25/10/15 02:27, Scott Howard wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu openmw_0.36.1-1 . ANY . unstable . -m "rebuild against new libbullet"
> 
> The maintainer (Bret Curtis) is busy but asked me to request this binNMU
> 
> Game crashes because it was compiled against an old libbullet. More info:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801914
> https://forum.openmw.org/viewtopic.php?f=2=3053

Sounds like you need a library transition.

Emilio

Bug#802765: gnome-calculator: just drop gnome-icon-theme recommends

[Andreas Henriksson]

Control: tags -1 + pending

On Sun, Oct 25, 2015 at 04:10:11AM +0100, Michael Biebl wrote:
[...]
> I'm fine with dropping the Recommends altogether.
> 
> Andreas, please go ahead.

Committed to svn, pending next upload 

Regards,
Andreas Henriksson

Bug#802836: python-pytest-cov: please update pytest-cov

[Daniel Stender]

Control: block 800684 by -1

An update is also needed by Privacyidea (>= 1.8.1).

Thanks,
DS

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Bug#803099: golang-ginkgo: FTBFS on arm64

[Edmund Grimley Evans]

Source: golang-ginkgo
Version: 1.2.0-1

It failed to build on arm64:

https://buildd.debian.org/status/package.php?p=golang-ginkgo=sid

The error was:

src/github.com/onsi/ginkgo/internal/remote/output_interceptor_unix.go:34: 
undefined: syscall.Dup2
src/github.com/onsi/ginkgo/internal/remote/output_interceptor_unix.go:35: 
undefined: syscall.Dup2

On arm64 there is no dup2 system call; there's only dup3:
dup2(oldfd, newfd) is equivalent to dup3(oldfd, newfd, 0)
unless oldfd == newfd.

I don't know whether you can use dup3 on all the architectures you
care about or whether there's a Go package that already provides a
Dup2 wrapper that works on all architectures. If you're not interested
in errors and don't care about the performance cost of an additional
system call then you could probably just call Dup2 and Dup3: one will
do what you want and the other won't do any damage even if both are
implemented, as far as I can tell.

Bug#685878: [Pkg-netatalk-devel] Bug#685878: Another year has passed, still no netatalk3

[Jonas Smedegaard]

Quoting Bernd Zeimetz (2015-10-26 20:27:07)
> 
> On 10/26/2015 01:12 PM, Adrian Knoth wrote:
>> Looks like we're talking about ~10 FIXMEs in debian/copyrights. This 
>> is http://bugs.debian.org/751121.
>
> Did you check if they apply to netatalk 3.1.7?
> On the first quick look the problem files are gone.

Please check properly (not just quickly) and report your findings at 
bug#751121.


 - Jonas

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

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


signature.asc
Description: signature

Bug#685878: [Pkg-netatalk-devel] Bug#685878: Another year has passed, still no netatalk3

[Bernd Zeimetz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 10/26/2015 08:43 PM, Jonas Smedegaard wrote:
> Quoting Bernd Zeimetz (2015-10-26 20:27:07)
>> 
>> On 10/26/2015 01:12 PM, Adrian Knoth wrote:
>>> Looks like we're talking about ~10 FIXMEs in debian/copyrights.
>>> This is http://bugs.debian.org/751121.
>> 
>> Did you check if they apply to netatalk 3.1.7? On the first quick
>> look the problem files are gone.
> 
> Please check properly (not just quickly) and report your findings
> at bug#751121.

I'm not the maintainer of the package, but you are the maintainer. It
is YOUR job to do so. If you don't want to do it, you should orphan
the package. If you think the latest version is still in RC shape, you
should document that in the bug report.


- -- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWLor5AAoJEOs2Fxpv+UNf4XEP/jEkeYKN43r0flEv+Th3YOko
yqs5qj2MUiOiFhTP6FyHeCdo2XESygNon84ZF6Dnvk0g1XN6pztcTZwc9ZmK+XlC
ETMQ8c3ZjhGTW3Jcq4+SMYRUB13/TA2W4Dr53L+dJBsOX3Zc2GXJhsFPwQI16JS/
R8NGfhpLwdRm5ZsO1xHmVEjFGoI93DS2pXAiF1GZ2xJBGZHLYwO54odzCVjVaiMZ
CqOCZ7rnsD51fcPrtvbTebY+kC9iu0o1PO3hlDLiT3qgNhXTNFyU1/A5gOM0Diia
f+3RQ0bbG+qAgSv+sMGm9quXaOi2DAfhYJcSKYihnzDFcorUrVFhuUiZCwGhR+bv
oqf9D4SAbHh5ojlNDE6ZizqA25SSdKguGpUQnM+TildASnyEzof1Ir7oRiCniBb4
9Nnr3scefoU+a7CGtPvycA7G2FLG72yoUrIu1IsDQeBJgDmDB9wByJT/AFyWA+8k
0tAjeadoEs2fOZ8PSIbCsYdTATixct1bMa/9f5GLehhfsYuTK9NeZVLC5z3DGwWE
k20aMFjua2jlU2zgftZGgsXD9njROWm/Xft2Vkn0SY6OKZjHW/mUZfbGhjJn/VKy
FrdtK8YyWpdtbWZQ0nwDSdoz+RWVSMaLqP9R8Jj5qmlbhQsptT8wU7m65V3wKpwd
+d20Xzm/kUdlmuoCKgOP
=keAJ
-END PGP SIGNATURE-

Bug#685878: [Pkg-netatalk-devel] Bug#685878: Another year has passed, still no netatalk3

[Jonas Smedegaard]

Quoting Bernd Zeimetz (2015-10-26 21:20:17)
> On 10/26/2015 08:43 PM, Jonas Smedegaard wrote:
>> Quoting Bernd Zeimetz (2015-10-26 20:27:07)
>>> On 10/26/2015 01:12 PM, Adrian Knoth wrote:
 Looks like we're talking about ~10 FIXMEs in debian/copyrights. 
 This is http://bugs.debian.org/751121.
>>>
>>> Did you check if they apply to netatalk 3.1.7? On the first quick 
>>> look the problem files are gone.
>>
>> Please check properly (not just quickly) and report your findings at 
>> bug#751121.
>
> I'm not the maintainer of the package, but you are the maintainer. It 
> is YOUR job to do so. If you don't want to do it, you should orphan 
> the package. If you think the latest version is still in RC shape, you 
> should document that in the bug report.

Thanks for your kind interest in this issue.

I apologize for misunderstanding in what way you wanted to help here.


 - Jonas

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

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


signature.asc
Description: signature

Bug#803104: yelp: FTBFS: Segmentation fault

[Chris Lamb]

Source: yelp
Version: 3.18.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

yelp fails to build from source in unstable/amd64. (Whilst it segfaults,
I think this actually is due to the lack of an $DISPLAY - see the
warnings. Perhaps something like xvfb is needed?)

  [..]

  gtkdoc-scangobj  $scanobj_options --module=libyelp; \
  else \
  for i in libyelp.args libyelp.hierarchy libyelp.interfaces
  libyelp.prerequisites libyelp.signals ; do \
  test -f $i || touch $i ; \
  done \
  fi
  
  (process:14998): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed
  
  ** (process:14998): WARNING **: Unable to connect to dbus: Cannot
  autolaunch D-Bus without X11 $DISPLAY
  Segmentation fault
  Scan failed: 
  Makefile:644: recipe for target 'scan-build.stamp' failed
  make[4]: *** [scan-build.stamp] Error 139
  make[4]: Leaving directory '/build/yelp-3.18.1/docs/libyelp'
  Makefile:413: recipe for target 'all-recursive' failed
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory '/build/yelp-3.18.1/docs'
  Makefile:535: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory '/build/yelp-3.18.1'
  Makefile:444: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory '/build/yelp-3.18.1'
  /usr/share/cdbs/1/class/makefile.mk:47: recipe for target
  'debian/stamp-makefile-build' failed
  make: *** [debian/stamp-makefile-build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/yelp_3.18.1-1.build1.log.gz


Regards,

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


yelp.3.18.1-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#802735: nodejs: add autopkgtests

[Jérémy Lal]

2015-10-26 23:24 GMT+01:00 Jérémy Lal :

>
>
> 2015-10-26 23:22 GMT+01:00 dann frazier :
>
>> On Fri, Oct 23, 2015 at 09:14:54AM +0200, Jérémy Lal wrote:
>> > 2015-10-23 2:32 GMT+02:00 dann frazier :
>> >
>> > > Source: nodejs
>> > > Version: 4.0.0~dfsg-2
>> > > Severity: wishlist
>> > > Tags: patch
>> > >
>> > > Attached is a patch to add a couple simple autopkgtests to nodejs.
>> > >
>> >
>> > Hello,
>> > beside a very simple test like
>> > nodejs -e "console.log('test');"
>>
>> The attached patch should do that.
>>
>> > i don't see the point of testing further since hundreds of tests are
>> > already run
>> > during package build.
>>
>> I could also wrap those tests up to run against the host binary - is
>> that something you'd be interested in including?
>>
>> fyi, my goal is to be able to run tests against an existing binary
>> package to make sure there are no issues due to an ancillary software
>> update (e.g. kernel).
>>
>>
> Don't bother. It is true that autopkgtests have different use cases than
> tests done
> during build. I'll apply your patch as is.
>


Ha, spoke too fast (there should be an acronym for that).

Maybe pure upstream js tests could be part of autopkgtests, because they
just
require source package with patches applied + nodejs runtime.
The only (solvable) problem is to pass correct cpu param to the test suite.
That would separate building from testing, which is often a problem on
buildd
servers where slowdowns can make some tests timeout. Maybe also more
control over autopkgtest environment could enable more tests (ipv6, tty).

I'll look into it before next upstream release.

Jérémy

Bug#803107: Liferea crashes when I want to edit feed properties

[antistress]

Package: liferea
Version: 1.10.16-2

Hi,

When I try to edit properties of a feed (either from contextual menu or
from menubar), Liferea crashes.

See below what I got in a terminal

I'm using :
- libc6 2.19-22
- Linux debian 4.2.0-1-amd64 #1 SMP Debian 4.2.3-1 (2015-10-06) x86_64
GNU/Linux

Thanks

---

~$ liferea

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

(liferea:24004): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(liferea:24004): GLib-CRITICAL **: g_strchug: assertion 'string != NULL'
failed

** (liferea:24004): ERROR **: Loading /usr/share/liferea/liferea.ui failed.
Trappe pour point d'arrêt et de trace

Bug#802945: golang-go: Install fails with golang-golang-x-tools 1:0.0~git20150716.0.87156cb+dfsg1-4 installed

[Andreas Beckmann]

There is also a file conflict with golang-go.tools from jessie:

  Selecting previously unselected package golang-go.
  Preparing to unpack .../golang-go_2%3a1.5.1-1_amd64.deb ...
  Unpacking golang-go (2:1.5.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-go_2%3a1.5.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/go/pkg/tool/linux_amd64/vet', which is also in 
package golang-go.tools 0.0~hg20140703-4
  Errors were encountered while processing:
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
   /var/cache/apt/archives/golang-go_2%3a1.5.1-1_amd64.deb


Andreas

Bug#803099: golang-ginkgo: FTBFS on arm64

[Edmund Grimley Evans]

I must have been thinking of an entirely different programming
language. For some reason I was thinking that the undefined syscall
was a run-time rather than a compile-time error. Clearly you can't use
Dup2 at all on arm64. Does that mean you need two additional source
files, one with "// +build arm64", one with "// +build !arm64", if
there isn't already a wrapper defined somewhere else?

Bug#496930: ITP: dvc -- Emacs front-end to distributed version control systems

[Daniel Dehennin]

Ben Finney  writes:

> Upstream development  has resumed in
> recent months, with what appear to be some improvements and bug fixes
> committed to the VCS.
>
> Are you still interested in collaborating with upstream to get this
> package into Debian?

Hello,

I did not notice it, I switched to magit[1].

I rarely use something else than Git, I really prefer magit over DVC and
I'm not interested in it any more.

Regards.

Footnotes: 
[1]  http://magit.vc

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF


signature.asc
Description: PGP signature

Bug#803112: gdm3: Black/grey screen with unresponsive mouse cursor on GDM start

[Adam M]

Package: gdm3
Version: 3.18.0-2
Severity: important

Dear Maintainer,

When I boot up, upon gdm3 loading I am presented by an unresponsive mouse
cursor and either a black screen (if I have two monitors plugged in) or a grey
background (if I have one monitor plugged in). Either way I am unable to login.
I am also unable to switch console with Ctl+Alt+F*. The only thing I can do is
Alt+SysRq+(R,S) which kills gdm3 and gets me back to the console.
   * What led up to the situation?
I ran an upgrade on 24 October.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I tried adding user Debian-gdm to the video group (see bug #799948),
which did nothing.
I tried to access Xorg via the startx command which works.
I tried enabling automatic login, this also works and so acts as a
workaround / temporary solution.

Am using the intel Xorg driver (for an Intel 4000 chipset) and have a feeling
this problem may have something to do with it going by the errors below.

***I found the following errors in my journal which started appearing almost
immediately after I upgraded on 24th:***
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: Fatal
server error:
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: Please
consult the The X.Org Foundation support
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: at
http://wiki.x.org
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: for help.
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
Please also check the log file at "/home/[username-
removed]/.local/share/xorg/Xorg.0.log" for additional information.
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (WW)
xf86CloseConsole: KDSETMODE failed: Operation not permitted
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (WW)
xf86CloseConsole: VT_SETMODE failed: Operation not permitted
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]:
FatalError re-entered, aborting
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
xf86CloseConsole: VT_ACTIVATE failed: Operation not permitted
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: (EE)
Oct 26 18:48:08 [hostname-removed] /usr/lib/gdm3/gdm-x-session[3470]: Unable to
run X server
Oct 26 18:48:08 [hostname-removed] gdm-autologin][3483]: pam_unix(gdm-
autologin:session): session opened for user [username-removed] by (uid=0)

*** And here is the output of "journalctl -u gdm3" for for a failed attempt at
running gdm3: ***
Oct 25 01:24:43 [hostname-removed] systemd[1]: Starting GNOME Display
Manager...
Oct 25 01:24:43 [hostname-removed] systemd[1]: Started GNOME Display Manager.
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Enabling debugging
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Changing user:group to Debian-
gdm:Debian-gdm
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Successfully connected to D-Bus
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmManager: GDM starting to
manage displays
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Could not ping plymouth: Failed
to execute child process "/bin/plymouth" (No such file or directory)
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmLocalDisplayFactory: Adding
display on seat seat0
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: id: (null)
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: seat id: (null)
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: session class:
greeter
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: initial: no
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: allow timed login:
yes
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: local: yes
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: session type:
wayland
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: seat id: seat0
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: initial: yes
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplayStore: Adding display
/org/gnome/DisplayManager/Displays/38765344 to store
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: Managing display:
/org/gnome/DisplayManager/Displays/38765344
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: GdmDisplay: Preparing display:
/org/gnome/DisplayManager/Displays/38765344
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: doing initial setup? no
Oct 25 01:24:43 [hostname-removed] 

Bug#803097: busybox: segmentation fault while unzipping bad archive

[Henri Salo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: buzybox
Version: 1:1.22.0-15
Severity: normal
Tags: security, fixed-upstream

Unziping a specially crafted zip file results in a computation of an invalid
pointer and a crash reading an invalid address.

Mailing list post:
  http://www.openwall.com/lists/oss-security/2015/10/25/3
Fix:
  
http://git.busybox.net/busybox/commit/?id=1de25a6e87e0e627aa34298105a3d17c60a1f44e

- -- 
Henri Salo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWLn2SAAoJECet96ROqnV0Na0QAMltt4Ou89+Y1MygWLoME4or
TJTdvBlUmZhkZAKup6ZbnrdRsF/sUZZB62F/2DibIbtL3bEbSypfOHsg6P/+Q/j9
vxxxD/yJ1Ry1/Qqseox1Ye7IuoqIto2Gey88bhZVRjHNPBXY3wBQfBF7IbJIpnZH
+Lr5uVb8+4vIXy3iKbxLhXY7/hNj19Lg4n4AqQVq/Lbqz1ZLQUAdsOAulrN1l9bJ
lcFvtZ5kxWS8a2du+qIfpy14avdpv+rrD+StWbkzbemri9XZpDyGeeFvhg/BQMz/
n+4P5c8B5GVa7IZRxtVTc8tRV2gv3LvipewXxXdX7xxYfXt4iw8SHtFxvUxAD6JM
l8dXuSdWFxVKHkf7T8o7refxTyuZ0mY3fmRmpi1dLJiRRegoCarlSs/1YbgjCdp9
R0Y5aS+QWrVRrIcq9BYnCxDa+lBmuMpb6qNFYCVmXideI6RyR3Q+us/aNn/sOCPQ
AoKu2tHstHISigTzIjJMVERHBoJInciF4XnxpKJ6XXXIj/1UGNtlRyIpkfY6G2BP
ygiTwrtyKLAy3hXNd2rgoWjBW1MkSpg9izumH3E8Pfah+jLqJD/WuBR56yLFL76X
PECdqv/tojzqOTgSCxNsvqlP8h8f8FIxXH87xvKyXfOigPw+tMGTeO3q+uCSPak5
O1B2G9rwbzoiBpO7ungy
=PGtQ
-END PGP SIGNATURE-

Bug#803083: CVE-2015-2695 in libgssapi-krb5-2, SPNEGO context aliasing

[Salvatore Bonaccorso]

Hi Sam, hi Ben,

On Mon, Oct 26, 2015 at 04:04:24PM -0400, Sam Hartman wrote:
> Do I need to do anything here?
> I have availability this evening and Wednesday evening.

I just only added the issues to the security-tracker but have not yet
looked at any of the issues closer. Can you, once you have updates
ready for wheezy- and jessie-security send debdiffs for a review to
the security team mail alias? (t...@security.debian.org).

Thanks in advance already!

Regards,
Salvatore

Bug#798500: Drush version in Debian package

[Antoine Beaupré]

On 2015-10-24 05:40:44, Jan Pobořil wrote:
> Hello,
> I would be likely to use Debian package for Drush, but it seems there are
> too old version. Even in testing is old version 5.x, but currently actively
> developed version is 8 and version is 5 is unsupported.
>
> see: http://docs.drush.org/en/master/install/
>
> What is cause for this situation? Is package dead?

Pretty much. Upstream has basically rewrote the whole distribution
mechanism to depend on Composer, which made it very hard to package new
versions, as composer isn't itself packaged in Debian (or wasn't, last i
checked):

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714118

I have therefore orphaned the package:

https://bugs.debian.org/798500

I do not use drush anymore, either. You are welcome, of course, to take
over the package! :)

A.

-- 
If builders built houses the way programmers built programs,
The first woodpecker to come along would destroy civilization.
- Gerald Weinberg

Bug#802493: debian-rtc mailing list creation

[Thorsten Alteholz]

I really like that idea.

  Thorsten

Bug#802848: RFS: gnome-twitch/0.1.0-1 [ITP]

[Tim Dengel]

Am 26.10.2015 um 19:00 schrieb Gianfranco Costamagna:
> Hi, the packaging looks good to me (note: I didn't do a full review)

Hi, thanks for looking at my package!

> however I don't like your dh_auto_install target override.
> 
> dh_auto_install should install into debian/tmp, not into debian/package.

I installed into debian/package because "man dh_auto_install" told me
that "[...]the files are installed into debian/package/ if there is only
one binary package. In the multiple binary package case, the files are
instead installed into debian/tmp/ [...]".
Although there is no reason given why it should be debian/package in one
case and debian/tmp in the other. What's the difference?

> I propose you to use dh_install like this:
> 
> override_dh_install:
> 
> DESTDIR=$(CURDIR)/debian/gnome-twitch ninja -C build install
> 
> what do you think?

I overrode dh_auto_install because that is where "normally" (when using
autotools for example) the "make install" stage of the process is
executed, right?
And the "ninja install" command would be my equivalent of that "make
install".
After that, I thought, dh_install could be used to install files that
were not picked up by the call to make (or ninja in my case).

If that is not the case, what difference does overriding dh_install make
in contrast to overriding dh_auto_install? Both seem to produce a
working package for me.

Also, the command you proposed would also install into
debian/gnome-twitch, but at the top you said I should be installing into
debian/tmp? I'm a little confused ;)

> you could also use MAKE=ninja and
> $(MAKE) during the calls, to keep it simple and possible to easily change the 
> build system.

While writing an answer to this, I just realized that make also takes
the -C option, I didn't know that before.
So yes, that would probably be a good idea, I'll do that.

--
Tim

Bug#800574: backport to sid/stable? (was RE: libc6: lock elision hazard on Intel Broadwell and Skylake)

[Carlos Alberto Lopez Perez]

On 23/10/15 22:10, Henrique de Moraes Holschuh wrote:
> On Fri, Oct 23, 2015, at 11:13, Carlos Alberto Lopez Perez wrote:
>> I was having trouble (crashes with the NVIDIA proprietary driver) on a
>> Debian system with an i7-5775C and libc6=2.19-18+deb8u1 (stable)
> 
> This is very very likely to be braindamage on the NVIDIA driver, though.
> 
> Are you sure that driver is not doing something as idiotic as unlocking
> an already unlocked mutex ?
> 
> The proper fix in that case is _always_ to fix whatever is broken,
> because eventually it will run on something that has working hardware
> lock elision... and crash.
> 

I can't know, since I don't have access to the source code of the
driver, neither the debug symbols are available, so any attempt to get a
meaningful backtrace was hopeless.

At first I also thought it was the driver doing something wrong, but
then I found several reports of people with the same cryptic backtrace
than me saying that this was because of the TSX-NI bug of recent Intel
CPUs [1].

And effectively, after upgrading glibc to this one that disables TSX-NI
for broadwell it suddenly works as expected...

So this seems to suggest that effectively TSX-NI is buggy on this CPU.

In any case... Do you know of any program or test that I can run to
check if TSX-NI (both HLE and RTM) is working as it should or is still
buggy on this CPU? That way we can verify better if the problem is in
the CPU or in the driver.

>> I tried first to update the Intel microcode with the "unreleased" 0x13
>> microcode version but it didn't disabled the TSX-NI instructions [1]
>> neither the crashes.
> 
> Mobile Broadwell-H seems to disable TSX, while Desktop Broadwell-H
> doesn't.  That's why we blacklisted the whole thing: inconsistent
> behavior on the same microcode, and that behavior is itself inconsistent
> with the errata sheet that says such processors shouldn't even be able
> to advertise Intel TSX RTM in CPUID.
> 
> At the moment, we don't even know what is wrong with RTM in
> Broadwell/Broadwel-H/Broadwell-DE.  We do know some of what is wrong
> with HLE in Broadwell/-H/-DE (and it is really nasty), but HLE is not
> used by glibc in the first place, and the HLE erratum is supposedly
> worked around somehow (because it is documented to be so on the Xeon
> D-1500/Broadwell-DE) by the batch of microcode updates available in the
> kernel bugzilla bug report mentioned in this bug report.
> 
> Broadwell-H Microcode 0x13 is useful anyway because it fixes other
> critical errata that hangs/oopses the kernel: you box should be a _lot_
> more stable with it.  And at least one person reported that not all
> hangs were fixed by microcode 0x12, thus you probably should use keep
> using microcode 0x13 (or newer, should one become available).
> 

Good to know, thanks for the advice. I will keep using this 0x13
"unofficial" microcode until a new one is out.
I can't keep wondering why Intel is not releasing this :\


Regards!


[1]
https://lists.archlinux.org/pipermail/arch-general/2015-April/038953.html



signature.asc
Description: OpenPGP digital signature

Bug#803098: segfaults upon closing evince window leading to the restart of gnome-shell

[Yaroslav Halchenko]

Package: libatspi2.0-0
Version: 2.18.1-1
Severity: grave
File: /usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1

NB It might be also related or triggering another issue I have detected
after recent upgrade which completely stalls the box: #803087.

If I open evince (3.18.0... currently upgrading evince and other gnome pieces
to 3.18.1) and close it (via GUI close buttong or via keyboard shortcuts),
gnome-shell restarts and journalctl reports

Oct 26 15:25:32 hopa kernel: gnome-shell[3905]: segfault at 18 ip 
7f5ad748ec2d sp 7ffc051d2a70 error 4 in 
libatspi.so.0.0.1[7f5ad7478000+31000]
Oct 26 15:25:32 hopa gnome-session[2423]: gnome-session[2423]: WARNING: 
Application 'gnome-shell.desktop' killed by signal 11


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

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

Versions of packages libatspi2.0-0:amd64 depends on:
ii  libc6 2.19-22
ii  libdbus-1-3   1.10.0-3
ii  libglib2.0-0  2.46.1-1
ii  libx11-6  2:1.6.3-1

Versions of packages libatspi2.0-0:amd64 recommends:
ii  at-spi2-core  2.18.1-1

libatspi2.0-0:amd64 suggests no packages.

-- no debconf information

Bug#803066: [tryton-debian] Bug#803066: tryton-server: problem with init scripts and "$DAEMON_OPTS" as set in /etc/default/tryton-server

[Raphael Hertzog]

On Mon, 26 Oct 2015, Mathias Behrle wrote:
> Could you please confirm, that I understand correctly, that the following diff
> is meant to solve this problem:

Yes, that diff looks correct.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#100808: Please kindly view the attached file to apply for a low interest loan or contact us at; gfs...@consultant.com Tel: +27 78 881 9145.

[Financial Services]

 Please kindly view the attached file to apply for a low interest loan 
or contact us at; gfs...@consultant.com Tel: +27 78 881 9145.

APPLY FOR A LOAN .pdf
Description: Adobe PDF document

Bug#802248: awesome: FTBFS: ldoc: Error: no suitable Lua interpreter found

[Uli Schlachter]

Hi everyone,

isn't this a bug in ldoc?

If I understand the dependencies correctly, awesome depends on lua 5.1 and
lua-ldoc depends on lua5.1 | lua5.2, so only lua 5.1 is installed.

However, looking at [0], ldoc contains "Lua-Versions: 5.2", so lua-any doesn't
consider lua 5.1 a valid option.

Thus, either lua-ldoc should depend on lua 5.2 or allow to be used with lua 5.1.

Anyone disagrees?

Cheers,
Uli

[0]:
https://anonscm.debian.org/cgit/pkg-lua/lua-ldoc.git/commit/?id=ed6a8e46ce29e2a31eccc685c162e7b704539808
-- 
Sent from my Game Boy.

Bug#777481: [Pkg-clamav-devel] Bug#777481: clamav-daemon: /etc/clamav/freshclam.conf corruped after fresh installing clamav-daemon

[Sebastian Andrzej Siewior]

On 2015-03-11 21:19:25 [+0100], Matthias Klumpp wrote:
> 2015-03-11 21:10 GMT+01:00 Andreas Cadhalpun 
> :
> > Hi Matthias,
Hi Matthias,

> > The complete VirtualBox image that I use to reproduce this is available:
> > https://breakpoint.cc/bts_777481/Debian-Clamav-bug.zip
> 
> Nice, I'll look into it.
> >> After that, could you delete the file and try to reproduce the issue
> >> again?
> >
> >
> > Even after deleting this file, I could still reproduce the problem with
> > apper.
> >
> > Should I still send you the file or is it best to reassign this to apper
> > now?
> 
> Please send me the file anyway, it's not clear if this really is an
> Apper bug or a PackageKit issue.
> I guess something is setting an uninitialized variable as HTTPProxy...
> Not sure where this happens though.

Is there any update on this? According to #799808 another user managed
to run into this. Antti, could you tell us please what you used to install
clamav?

> Regards,
> Matthias
> 

Sebastian

Bug#802838: ada: gnatgcc-5 and gnatmake symlinks

[Ludovic Brenta]

Matthias Klose  writes:
> I've never understood why this link moved to the versioned gnat
> package and didn't stay in the unversioned gnat package. So maybe we
> changed that when preparing the ada cross compiler?
>
> The cross compiler builds shouldn't ship such unversioned links at
> all. I very much would prefer to have these links in the unversioned
> gnat package again.

My first reaction is to agree wholeheartedly but one of Nicolas'
greatest qualities is that he discusses and documents such changes
beforehand:

https://lists.debian.org/debian-ada/2014/04/msg0.html

I think the problem he wanted to solve was to be able to build gnat-x.y
with itself even during the transition period when gnat pointed to an
earlier, or later, on nonexistent, gnat-x'.y'.

Now I'm not sure how such a situation could arise, or how it could
prevent building gnat-x.y.

> Not sure about gnatmake and others. I'm not an gnat developer.  If it
> is possible that the versioned tools can be used on its own, then
> again I would prefer to ship these in the gnat package.

No, the "versioned" tools cannot be used on their own.  We don't want to
require users to type gnatmake-x.y instead of gnatmake; and there is a
whole bunch of user-facing programs that call each other, too, like
gnatls, gprbuild, etc.

--
Ludovic Brenta.

Bug#803093: flask-script: please update flask-script

[Daniel Stender]

Source: flask-script
Severity: wishlist
Control: block 800684 by -1

Please update flask-script, packaging of Privacyidea needs >= 2.0.5.

Thanks,
DS

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

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

Bug#801427: remember to ask for password

[Paul Gevers]

Hi Dan

On 26-10-15 19:53, 積丹尼 Dan Jacobson wrote:
> Well that package should not assume all users are running mysql all the
> time, and only find out too late in its upgrade procedure, causing
> things to get stuck in an non-ideal state, causing much work...

And lots of setups don't need mysql running on the localhost. So
checking for a running mysql doesn't work in lots of cases.

> Instead it should first check, and if it finds mysql not running it
> should say
> "Mysql is not running. Please start it and hit RET, or type "a" to
> abort." etc.

The current checks should cover this. Do you think the error message
should be improved? The current error message is below. Which point is
not clear enough?
_Description: Next step for database upgrade:
 An error occurred while upgrading the database:
 .
 ${error}
 .
 Fortunately, ${dbfile} should hold a backup of the database, made just
before the upgrade (unless the error occurred during backup creation, in
which case no changes will have been applied yet). Your options are:
  * abort - Causes the operation to fail; you will need to downgrade,
reinstall, reconfigure this package, or otherwise manually intervene
to continue using it. This will usually also impact your ability to
install other packages until the installation failure is resolved.
  * retry - Prompts once more with all the configuration questions
(including ones you may have missed due to the debconf priority
setting) and makes another attempt at performing the operation.
  * retry (skip questions) - Immediately attempts the operation again,
skipping all questions. This is normally useful only if you have
solved the underlying problem since the time the error occurred.
  * ignore - Continues the operation ignoring dbconfig-common errors.
This will usually leave this package without a functional database.

Paul



signature.asc
Description: OpenPGP digital signature