Bug#683277: [reportbug/master] fix vesion/version typo; thanks to Niels Thykier for the report and to Tomas Pospisek for the patch; Closes: #683277

[Sandro Tosi]

tag 683277 pending
tag 683277 pending
thanks

Date:   Thu Sep 11 23:46:16 2014 +0100
Author: Sandro Tosi 
Commit ID: 5ee4b22a2f04c55849bf5c14d323239ebe32727b
Commit URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=5ee4b22a2f04c55849bf5c14d323239ebe32727b
Patch URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=5ee4b22a2f04c55849bf5c14d323239ebe32727b

fix vesion/version typo; thanks to Niels Thykier for the report and to 
Tomas Pospisek for the patch; Closes: #683277

  


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

Bug#761241: gnome-maps: fail to start

[Alessandro Barbieri]

Package: gnome-maps
Version: 3.12.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I get this error when starting gnome-maps:

(gnome-maps:1330): Gdk-ERROR **: The program 'gnome-maps' received an X Window 
System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 313 error_code 8 request_code 155 (GLX) minor_code 31)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)



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

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

Versions of packages gnome-maps depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.20.0-2
ii  geoclue-2.0  2.1.8-1
ii  gir1.2-champlain-0.120.12.8-1
ii  gir1.2-clutter-1.0   1.18.4-2
ii  gir1.2-cogl-1.0  1.18.2-2
ii  gir1.2-gdkpixbuf-2.0 2.30.8-1
ii  gir1.2-geocodeglib-1.0   3.12.2-1
ii  gir1.2-glib-2.0  1.40.0-2
ii  gir1.2-gtk-3.0   3.12.2-3+b1
ii  gir1.2-gtkchamplain-0.12 0.12.8-1
ii  gir1.2-gtkclutter-1.01.5.4-1
ii  gjs  1.40.1-4
ii  libc62.19-10
ii  libgirepository-1.0-11.40.0-2
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.40.1-4
ii  libglib2.0-0 2.40.0-5

gnome-maps recommends no packages.

gnome-maps suggests no packages.

-- no debconf information


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

Bug#761236: wdm does not work with systemd as the init system

[Eliad Bagherzadegan]

On 09/12/2014 03:13 AM, Axel Beckert wrote:

> Can you please elaborate "won't work"? What symptoms does your system
> have? Does it come up, but you can't login? Or does wdm not even come
> up at all?

It does not come up at all. as I said, slim comes up instead.

> (There's only a very small chance that a recent systemd upload broke
> something as I haven't logged out for like one or two weeks on that
> peticular box. Will check upon the next reboot.)

It is possible. I only switched to systemd after debconf14.

> This doesn't sound wdm-related. You can change which display manager
> is started by reconfiguring any of them.

I meant when wdm is chosen (through dpkg-reconfigure wdm) to be the
display manager, it fails and instead slim comes up.


-- 
Eliad Bagherzadegan (eliad@gmail.com)


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

Bug#761242: override: libfm-dev:libdevel/optional

[Andrej N. Gritsenko]

Package: ftp.debian.org
Severity: normal

Please, change override of libfm-dev to optional (set in .deb) which is
a correct one since it is a dependency for the libfm-gtk-dev which is
optional.

Thank you.


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

Bug#761243: RFA: symmetrica

[Tim Abbott]

Package: wnpp
Severity: normal

I request an adopter for the symmetrica package.

The package description is:

  Symmetrica is a library for combinatorics. It has support for the
  representation theory of the symmetric group and related groups,
  combinatorics of tableaux, symmetric functions and polynomials,
  Schubert polynomials, and the representation theory of Hecke
  algebras of type A_n.

Jerome Benoit has privately expressed interest.

-Tim Abbott

Bug#761244: [hdf5-helpers] wrong library path in h5fc

[Julien Bigot]

Package: hdf5-helpers
Version: 1.8.13+docs-10
Severity: important

--- Please enter the report below this line. ---

The h5fc compiler wrapper uses a path for libraries that does not match that 
of the libraries provided by the libhdf5 package.
The h5cc wrapper has no such problem.

$ h5fc -show 
gfortran -g -O2 -fstack-protector-strong -I/usr/include/hdf5/serial -
L/usr/lib/x86_64-linux-gnu/hdf5/_serial /usr/lib/x86_64-linux-
gnu/hdf5/_serial/libhdf5hl_fortran.a /usr/lib/x86_64-linux-
gnu/hdf5/_serial/libhdf5_hl.a /usr/lib/x86_64-linux-
gnu/hdf5/_serial/libhdf5_fortran.a /usr/lib/x86_64-linux-
gnu/hdf5/_serial/libhdf5.a -Wl,-z,relro -lpthread -lz -ldl -lm -Wl,-rpath -
Wl,/usr/lib/x86_64-linux-gnu/hdf5/_serial

$ h5cc -show
/usr/bin/cc -I/usr/include/hdf5/serial -D_LARGEFILE_SOURCE -
D_LARGEFILE64_SOURCE -D_BSD_SOURCE -D_FORTIFY_SOURCE=2 -g -O2 -fstack-
protector-strong -Wformat -Werror=format-security -L/usr/lib/x86_64-linux-
gnu/hdf5/serial /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5_hl.a 
/usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.a -Wl,-z,relro -lpthread -lz -
ldl -lm -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/hdf5/serial

$ ls /usr/lib/x86_64-linux-gnu/hdf5/_serial/libhdf5hl_fortran.a
ls: cannot access /usr/lib/x86_64-linux-gnu/hdf5/_serial/libhdf5hl_fortran.a: 
No such file or directory

$ ls /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.a
/usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.a

(notice the additional underscore in the fortran version: _serial vs. serial)

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16-1-amd64

Debian Release: jessie/sid
  990 unstableftp.debian.org 
  500 testing ftp.debian.org 
  500 stable  ftp.debian.org 
  500 stable  download.videolan.org 
  500 saucy   ppa.launchpad.net 
  500 raring  ppa.launchpad.net 
1 experimentalftp.debian.org 
1 experimentalcdn.debian.net 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.


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

Bug#761138: bug only fixed in one of the many themes

[Paul Wise]

On Fri, Sep 12, 2014 at 3:20 AM, 積丹尼 Dan Jacobson wrote:

> OK I now changed it from "Right Sidebar" to "Default" and yuck... I
> didn't like it and changed it back.

If you could express why you didn't like the debwiki theme in a new
bug report, we can probably fix the issues. The default theme is the
same as the theme on www.debian.org so there isn't huge scope to
completely change the design.

> Anyway please fix the bug in the other 85% of the themes. Thanks!

The other themes are from the software we use (MoinMoin aka moin),
which we aren't going to fork moin just to fix minor usability issues.
If you would like to get this issue fixed in moin, please add a wiki
page for it in the moin bug tracker (which is just the moinmoin.in
wiki, which uses moin).

https://moinmo.in/MoinMoinBugs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#761223: gnome-mplayer: make gnome-mplayer depend on mplayer, mplayer2 or mpv

[Sebastian Ramacher]

Control: forwarded -1 
https://code.google.com/p/gnome-mplayer/issues/detail?id=725
Control: tags -1 + upstream

On 2014-09-11 21:42:56, stijn wrote:
> Is it possible to add mpv to dependencylist?
> Now you need to have mplayer or mplayer2 installed to make gnome-mplayer work.
> It would be nice if it was possible to make it work with mpv.
> Now i have mplayer2 installed just for gnome-player(needed for 
> gecko-mediaplayer) while I normally use mpv.
> 
> Since it's a fork also, it might be possible I think?

This will require some porting work at least. gnome-mplayer parses parts
of the output to stdout which is different in mpv.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#760682: lvm2: debian/rules try to restart lvm2-monitor.socket which doesn't exist

[Laurent Bigonville]

Le Thu, 11 Sep 2014 23:30:24 +0200,
Bastian Blank  a écrit :

> Control: severity -1 important
> 
> On Sat, Sep 06, 2014 at 09:21:01PM +0200, Laurent Bigonville wrote:
> > This is causing issues as the maintainer script are trying to
> > start/stop it:
> 
> Please show _what_ issues it produces.  Sure it is not right, but you
> forgot to show that it actually makes the package unusable.  I tried
> re-installing it several times and it did not break.

lvm2.prerm is containing the following code:

# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
deb-systemd-invoke stop lvm2-monitor.socket >/dev/null
fi
# End automatically added section

On a machine running systemd (214), the following code is returning !=
0:

root@fornost:~# deb-systemd-invoke stop lvm2-monitor.socket >/dev/null ; echo $?
Failed to stop lvm2-monitor.socket: Unit lvm2-monitor.socket not loaded.
5

The fact that some piece of code is returning non-zero in the prerm
script means that removing/updating/purging the pkg will just fail for
people running systemd.

This looks RC to me (breaking maintainer script is not nice for the
users).

root@fornost:~# dpkg -i /tmp/lvm2_2.02.111-1_amd64.deb 
dpkg : avertissement : dégradation (« downgrade ») de lvm2 depuis 
2.02.111-1bigon1 vers 2.02.111-1
(Lecture de la base de données... 275997 fichiers et répertoires déjà 
installés.)
Préparation du dépaquetage de /tmp/lvm2_2.02.111-1_amd64.deb ...
Dépaquetage de lvm2 (2.02.111-1) sur (2.02.111-1bigon1) ...
Paramétrage de lvm2 (2.02.111-1) ...
update-initramfs: deferring update (trigger activated)
Failed to start lvm2-monitor.socket: Unit lvm2-monitor.socket failed to load: 
No such file or directory.
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Traitement des actions différées (« triggers ») pour man-db (2.6.7.1-1) ...
Traitement des actions différées (« triggers ») pour initramfs-tools (0.116) ...
update-initramfs: Generating /boot/initrd.img-3.16-1-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.

Reinstalling the pkg a 2nd time:

root@fornost:~# dpkg -i /tmp/lvm2_2.02.111-1_amd64.deb 
(Lecture de la base de données... 275993 fichiers et répertoires déjà 
installés.)
Préparation du dépaquetage de /tmp/lvm2_2.02.111-1_amd64.deb ...
Failed to stop lvm2-monitor.socket: Unit lvm2-monitor.socket not loaded.
dpkg : avertissement : le sous-processus ancien script pre-removal a retourné 
une erreur de sortie d'état 5
dpkg: tentative d'exécution du script du nouveau paquet à la place...
Failed to stop lvm2-monitor.socket: Unit lvm2-monitor.socket not loaded.
dpkg: erreur de traitement de l'archive /tmp/lvm2_2.02.111-1_amd64.deb 
(--install) :
 le sous-processus nouveau script pre-removal a retourné une erreur de sortie 
d'état 5
Failed to start lvm2-monitor.socket: Unit lvm2-monitor.socket failed to load: 
No such file or directory.
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Des erreurs ont été rencontrées pendant l'exécution :
 /tmp/lvm2_2.02.111-1_amd64.deb


Could you please prevent lvm to migrate to testing to not break futur
upgrades and removal of this packages for jessie users?

The next question is why the start counterpart is not returning
non-zero, but that a question for deb-systemd-invoke maintainers I
guess.


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

Bug#673270: [reportbug/master] use a future-proof URL for the rc_policy.txt document; thanks to Paul Wise for the report and patch; Closes: #673270

[Sandro Tosi]

tag 673270 pending
tag 673270 pending
thanks

Date:   Fri Sep 12 00:59:56 2014 +0100
Author: Sandro Tosi 
Commit ID: 5d995722c39bea25b9793314cfda2ef39c6e4e8d
Commit URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=5d995722c39bea25b9793314cfda2ef39c6e4e8d
Patch URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=5d995722c39bea25b9793314cfda2ef39c6e4e8d

use a future-proof URL for the rc_policy.txt document; thanks to Paul Wise 
for the report and patch; Closes: #673270

  


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

Bug#760900: tagged as pending

[Filipus Klutiero]

On 2014-09-09 01:44, Dmitry Smirnov wrote:

tag 760900 pending
--

We believe that the bug #760900 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

 http://anonscm.debian.org/cgit/collab-maint/libteam.git/diff/?id=0d58638

(This message was generated automatically by
  'git-post-receive-tag-pending-commitmsg' hook).
---
commit 0d58638 (HEAD, master)
Author: Dmitry Smirnov 
Date:   Tue Sep 9 05:40:41 2014

 Improve long description (Closes: #760900).
 
  Thanks, Filipus Klutiero.


Thank you. One more issue persists:

Libteam provides mechanism to team multiple NICs (ports) into logical one 
(teamdev) at OSI Layer 2 (Data link).


"provides mechanism" is incorrect. "mechanism" is missing a determiner, such as "a" (the 
sentence could alternatively read "Libteam allows several NICs (ports) to be grouped into a single logical NIC 
[...]").


By the way, I have never heard about "channel teaming". Wikipedia however mentions 
"NIC teaming".

--
Filipus Klutiero
http://www.philippecloutier.com


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

Bug#761138: bug only fixed in one of the many themes

[積丹尼 Dan Jacobson]

OK I filed https://moinmo.in/MoinMoinBugs/ClarifyPathMeaning
but I don't want to get more involved with wikis other than MediaWiki,
which is also why I didn't spend a lot of times comparing themes, but
just picked one that seemed better at a quick glance.


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

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

[Gilles Darold]

Le 10/09/2014 20:49, Dale Schroeder a écrit :
>
> On 09/10/2014 11:41 AM, Mathieu Parent (Debian) wrote:
>> 2014-09-10 17:02 GMT+02:00 Dale Schroeder
>> :
>> [...]
>>> With the squidclamav service commented out in c-icap.conf and
>>> squidclamav
>>> package uninstalled, this is the backtrace output:
>> [...]
>>
>>> squidclamav directives were active in squid.conf.  As mentioned in a
>>> previous email, commenting the squidclamav directives in squid.conf
>>> allows
>>> squid3 to start/restart without error.
>> This looks like a squid problem then.
> Quite possibly, or a squidclamav conflict.  Gilles from squidclamav
> offered to test with the Debian versions of squid3 and c-icap, but has
> not yet reported back.
> I have not heard from squid3 maintainer Luigi Gangitano.  I'll add him
> to the thread.
>>> I have had no luck with tcpdump using the following command:
>>> tcpdump -w /root/capture.log host 127.0.0.1 and port 1344
>> Try: tcpdump -i lo -w /root/capture.log host 127.0.0.1 and port 1344
> No change; capture.log is still empty.
>> Note that I won't probably solve your problem as it seems too deep in
>> the code for me.
> I appreciate your help.
>> Regards
>>
>

I have play a little this night with a squid3+c-icap+squidanalyzer in
the same version as you. The most difficult for me was to understand how
to install testing packages.

Distributor ID:Debian
Description:Debian GNU/Linux 7.6 (wheezy)
Release:7.6
Codename:wheezy

ii  c-icap  1:0.3.4-1  amd64 
ICAP server implementation
ii  squid3  3.3.8-1.2  amd64 
Full featured Web Proxy cache (HTTP proxy)

and squidclamav-6.11 compiled

Everything works great for me I was able to view my favorit concert of
the moment:-)

But after restarting squid3 I also have the following entries in my
syslog file

Sep 11 21:22:16 gilles-debian kernel: [ 9360.558097] squid3[4919]:
segfault at 0 ip 7f8a88d8e010 sp 7fff6eaddb50 error 4 in
squid3[7f8a88a28000+49b000]
Sep 11 21:22:17 gilles-debian squid3[4987]: Squid Parent: will start 1 kids
Sep 11 21:22:17 gilles-debian squid3[4987]: Squid Parent: (squid-1)
process 4992 started

Outside those entries in /var/log/syslog everything work like a charm, I
keep watching video through c-icap+squidclamav without any problem.

Here what I have in cache.log at the time of the segfault:

2014/09/11 21:22:16 kid1| Shutting down...
2014/09/11 21:22:16.262 kid1| comm.cc(1102) _comm_close: comm_close:
start closing FD 8
2014/09/11 21:22:16.262 kid1| comm.cc(760) commUnsetFdTimeout: Remove
timeout for FD 8
2014/09/11 21:22:16.262 kid1| comm.cc(955) commCallCloseHandlers:
commCallCloseHandlers: FD 8
2014/09/11 21:22:16.262 kid1| AsyncCall.cc(18) AsyncCall: The AsyncCall
comm_close_complete constructed, this=0x7f8a896b7a60 [call18761]
2014/09/11 21:22:16.262 kid1| AsyncCall.cc(85) ScheduleCall:
comm.cc(1178) will call comm_close_complete(FD 8) [call18761]
2014/09/11 21:22:16.262 kid1| comm.cc(1102) _comm_close: comm_close:
start closing FD 7
2014/09/11 21:22:16.262 kid1| comm.cc(760) commUnsetFdTimeout: Remove
timeout for FD 7
2014/09/11 21:22:16.262 kid1| comm.cc(955) commCallCloseHandlers:
commCallCloseHandlers: FD 7
2014/09/11 21:22:16.262 kid1| AsyncCall.cc(18) AsyncCall: The AsyncCall
comm_close_complete constructed, this=0x7f8a896c06d0 [call18762]
2014/09/11 21:22:16.262 kid1| AsyncCall.cc(85) ScheduleCall:
comm.cc(1178) will call comm_close_complete(FD 7) [call18762]
2014/09/11 21:22:16.262 kid1| comm.cc(1781) commCloseAllSockets:
commCloseAllSockets: FD 7: calling comm_reset_close()
2014/09/11 21:22:16.262 kid1| comm.cc(1102) _comm_close: comm_close:
start closing FD 7
2014/09/11 21:22:16.262 kid1| comm.cc(1781) commCloseAllSockets:
commCloseAllSockets: FD 8: calling comm_reset_close()
2014/09/11 21:22:16.262 kid1| comm.cc(1102) _comm_close: comm_close:
start closing FD 8
2014/09/11 21:22:16.262 kid1| comm.cc(1778) commCloseAllSockets:
commCloseAllSockets: FD 14: Calling timeout handler
2014/09/11 21:22:16.262 kid1| AsyncCall.cc(85) ScheduleCall:
comm.cc(1779) will call IdleConnList::Timeout(local=127.0.0.1:39602
remote=127.0.0.1:1344 FD 14 flags=1, data=0x7f8a896bb498) [call18650]
2014/09/11 21:22:16.263 kid1| comm.cc(1778) commCloseAllSockets:
commCloseAllSockets: FD 17: Calling timeout handler
2014/09/11 21:22:16.263 kid1| AsyncCall.cc(85) ScheduleCall:
comm.cc(1779) will call IdleConnList::Timeout(local=127.0.0.1:39604
remote=127.0.0.1:1344 FD 17 flags=1, data=0x7f8a896bc8f8) [call18623]
2014/09/11 21:22:16.263 kid1| comm.cc(1778) commCloseAllSockets:
commCloseAllSockets: FD 19: Calling timeout handler
2014/09/11 21:22:16.263 kid1| AsyncCall.cc(85) ScheduleCall:
comm.cc(1779) will call IdleConnList::Timeout(local=192.168.1.162:46841
remote=173.194.45.36:80 FD 19 flags=1, data=0x7f8a897237b8) [call9105]
2014/09/11 21:22:16.263 kid1| comm.cc(1778) commCloseAllSockets:
commCloseAllSockets: FD 20: Calling timeout handler
2014/09/

Bug#759056: dicompyler: Please update to use wxpython3.0

[Olly Betts]

Looking at the bitpim pubsub changes (patch attached), I think you
want to update from:

from wx.lib.pubsub import Publisher as pub

to this instead:

import wx.lib.pubsub.setuparg1
import wx.lib.pubsub.core
pub = wx.lib.pubsub.core.Publisher()

I'm not sure if it should be the same pub instance in all the modules or
not though.

Updated version of wxpy30-more.patch attached too - with this the package
builds and starts up OK (it failed to start up for me before them).

Not sure how easy this is to automate in the script - I'd think there's
probably a fair bit of variation in the import.

Cheers,
Olly
diff -ruN bitpim-old/src/pubsub.py bitpim-new/src/pubsub.py
--- bitpim-old/src/pubsub.py	2009-11-05 23:17:29.0 -0300
+++ bitpim-new/src/pubsub.py	2014-09-11 21:00:32.0 -0300
@@ -21,7 +21,8 @@
 deleted.
 """
 
-from wx.lib.pubsub import Publisher
+import wx.lib.pubsub.setuparg1
+from wx.lib.pubsub.core import Publisher
 
 
 ###
@@ -69,11 +70,13 @@
 media_old_name='old_name'
 media_new_name='new_name'
 
+my_publisher = Publisher()
+
 def subscribe(listener, topic):
-Publisher.subscribe(listener, topic)
+my_publisher.subscribe(listener, topic)
 
 def unsubscribe(listener):
-Publisher.unsubscribe(listener)
+my_publisher.unsubscribe(listener)
 
 def publish(topic, data=None):
-Publisher.sendMessage(topic, data)
+my_publisher.sendMessage(topic, data)
Author: Andreas Tille 
Last-Update: Sat, 06 Sep 2014 15:57:29 +0200
Bug-Debian: http://bugs.debian.org/759056
Description: Further patches not applied by wx-migration-tool from
 http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git

--- a/dicompyler/baseplugins/anonymize.py
+++ b/dicompyler/baseplugins/anonymize.py
@@ -10,7 +10,9 @@
 
 import wx
 from wx.xrc import XmlResource, XRCCTRL, XRCID
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 import os, threading
 from dicompyler import guiutil, util
 
--- a/dicompyler/baseplugins/treeview.py
+++ b/dicompyler/baseplugins/treeview.py
@@ -13,7 +13,9 @@ logger = logging.getLogger('dicompyler.t
 import threading, Queue
 import wx
 from wx.xrc import XmlResource, XRCCTRL, XRCID
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 from wx.gizmos import TreeListCtrl as tlc
 from dicompyler import guiutil, util
 import dicom
--- a/dicompyler/plugin.py
+++ b/dicompyler/plugin.py
@@ -12,7 +12,9 @@ logger = logging.getLogger('dicompyler.p
 import imp, os
 import wx
 from wx.xrc import *
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 from dicompyler import guiutil, util
 
 def import_plugins(userpath=None):
--- a/dicompyler/baseplugins/quickopen.py
+++ b/dicompyler/baseplugins/quickopen.py
@@ -11,7 +11,9 @@
 import logging
 logger = logging.getLogger('dicompyler.quickimport')
 import wx
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 from dicompyler import dicomparser, util
 import dicom
 
--- a/dicompyler/baseplugins/2dview.py
+++ b/dicompyler/baseplugins/2dview.py
@@ -10,7 +10,9 @@
 
 import wx
 from wx.xrc import XmlResource, XRCCTRL, XRCID
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 from matplotlib import _cntr as cntr
 from matplotlib import __version__ as mplversion
 import numpy as np
--- a/dicompyler/baseplugins/dvh.py
+++ b/dicompyler/baseplugins/dvh.py
@@ -12,7 +12,9 @@
 
 import wx
 from wx.xrc import XmlResource, XRCCTRL, XRCID
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 from dicompyler import guiutil, util
 from dicompyler import dvhdata, guidvh
 from dicompyler import wxmpl
--- a/dicompyler/dicomgui.py
+++ b/dicompyler/dicomgui.py
@@ -15,7 +15,9 @@ logger = logging.getLogger('dicompyler.d
 import hashlib, os, threading
 import wx
 from wx.xrc import *
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 import numpy as np
 from dicompyler import dicomparser, dvhdoses, guiutil, util
 
--- a/dicompyler/guiutil.py
+++ b/dicompyler/guiutil.py
@@ -10,7 +10,9 @@
 import util
 import wx
 from wx.xrc import XmlResource, XRCCTRL, XRCID
-from wx.lib.pubsub import Publisher as pub
+import wx.lib.pubsub.setuparg1
+import wx.lib.pubsub.core
+pub = wx.lib.pubsub.core.Publisher()
 
 def IsMSWindows():
 """Are we running on Windows?
--- a/dicompyler/main.py
+++ b/dicompyler/main.py
@@ -20,7 +20,9 @@ from wx.xrc import *
 import wx.lib.dialogs, webbrowser
 # Uncomment line to setup pubsub for frozen targets on wxPython 2.8.11 and ab

Bug#752384: HEAnet sourceforge mirror is outdated

[Paul Wise]

On Fri, Sep 12, 2014 at 12:59 AM, Daniel Lintott wrote:

> I've attached a patch which should solve this problem, in fact it was
> already in my script just not used as you'll see.

Excellent, applied!

BTW: we could always use more help with QA infra, more details here :)

https://wiki.debian.org/qa.debian.org

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#749432: Fixed in new gnome-shell version

[Pablo Mercader Alcántara]

Kai Lüke:

I couldn't make it work :(

This is what I got:

pablo@dorita:~$ sudo apt -t experimental install gnome-shell gdm3 
gnome-session

Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
No se pudieron instalar algunos paquetes. Esto puede significar que
usted pidió una situación imposible o, si está usando la distribución
inestable, que algunos paquetes necesarios no han sido creados o han
sido movidos fuera de Incoming.
La siguiente información puede ayudar a resolver la situación:

Los siguientes paquetes tienen dependencias incumplidas:
 gnome-session : Depende: gnome-session-bin (>= 3.13.3-1) pero 3.12.1-3 
va a ser instalado
 gnome-shell : Depende: gir1.2-mutter-3.0 (>= 3.13.91) pero 3.12.2-2+b1 
va a ser instalado

   Depende: libmutter0e pero no va a instalarse
E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos.

It is complaining about unsatisfied dependencies.

I tried to look for the packages that are missing but couldn't find 
them, I don't know any other experimental repository.


Maybe those packages are on their way to unstable and have been retired 
momentaneously to appear in the unstable repository??


Saludos!


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

Bug#761136: django / python-mysql.connector / python2 / unicode broken: patch

[Brian May]

Apparently I misunderstood the policy.

So I have uploaded the patch (or rather very similar one) to svn.

I removed the bit that changes the Uploaders field. I will leave it to the
maintainer to decide if they want to make that change or not.
-- 
Brian May 

Bug#758105: handling bytes not part of the charset, and other garbage

[Vincent Lefevre]

On 2014-09-11 09:22:49 -0700, Paul Eggert wrote:
> Vincent Lefevre wrote:
> 
> >There's no reason that '.' matches something that doesn't belong to
> >the charset in C locale, but doesn't match in a UTF-8 locale.
> 
> In the C locale on GNU/Linux, all byte values are members of the charset.

I don't see any valid reason for that (the C locale corresponds
to ANSI_X3.4-1968, which is 7-bit only, so that there is some
inconsistency), except that it could be seen as more practical.
But then, I would say that this should be the same for invalid
byte sequences in a UTF-8 locale.

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


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

Bug#761162: clamav-unofficial-sigs: Cron job results spread onto mail and logs

[Paul Wise]

On Thu, 2014-09-11 at 19:10 +0200, Alessandro Vesely wrote:

> I'd rather suggest something along the lines of the attached patch
> (not tested).  It should get rid of some cron spam.  For reporting, I
> think libclamav does issue some warnings if a database is unacceptably
> old, not sure that covers all databases though.

Two issues with the patch:

I don't think hardcoding the version number in user-agent is a good
idea. I also don't think setting a version number in user-agent is
useful either. I also don't want the clamav-unofficial-sigs user-agent
to be specific to Debian so that part of the patch will be removed until
Bill adds it to the official version.

You removed the comparison between the original dbs in the clamav
directory and the newly downloaded dbs.

I'll fix these and try to test the patch and get the result in jessie.

> On Thu 11/Sep/2014 12:20:11 +0200 Paul Wise wrote:
> 
> > You can change the default URL by putting si_url=... here:
> > 
> > /etc/clamav-unofficial-sigs.conf.d/sanesecurl.conf
> 
> Hm... that would work if those assignments were done before sourcing
> $config_source.

I guess you missed that the main configuration file sources the files in
the conf.d directory (as well as the ones in /usr):

/etc/clamav-unofficial-sigs.conf

> You're right.  Unlike Sanesecurity, SecuriteInfo have no premium
> mirror.  Instead, they warn not to download files more than once a day
> on pain of ip-ban[1].  Hence, I changed to "24" the default
> si_update_hours (it is "4" in the dist clamav-unofficial-sigs.conf).

I guess that should be changed in the official package too...

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#758105: bug#18266: handling bytes not part of the charset, and other garbage

[Paul Eggert]

Vincent Lefevre wrote:

the C locale corresponds to ANSI_X3.4-1968,


No it doesn't, at least not on any current platform I'm aware of.  And 
POSIX does not require that.  POSIX even allows the C locale to be 
multibyte, e.g., UTF-8.



I would say that this should be the same for invalid
byte sequences in a UTF-8 locale.


One *could* design an encoding with that property, but it wouldn't be 
UTF-8; it would be something else.  I don't know of any C library that 
does that to UTF-8.  There are good arguments against doing it, e.g., 
one loses the property that one can concatenate character strings by 
concatenating their byte representations.


Anyway I'm afraid we may be going off the deep end here.  After all, 
grep can't impose its coding system design onto the operating system; 
it's more the other way around.



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

Bug#761245: icedove: STARTTLS regression: "connection to SMTP server was lost in the middle of the transaction"

[Dmitry Smirnov]

Package: icedove
Version: 31.0-3
Severity: serious

Today I upgraded icedove 24.7.0-1~deb7u1 to 31.0-3 and immediately lost 
ability to send messages (connection security: STARTTLS):

connection to SMTP server was lost in the middle of the transaction.

Luckily I have access to server log where exim4 4.80-7 logged the following:

TLS error on connection from [...]
(gnutls_handshake): Could not negotiate a supported cipher suite.

Downgrading icedove back to 24.7.0-1~deb7u1 fixed the problem.

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


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

Bug#747169: RFS: socksjs-twisted/1.2.1-1 [ITP]

[Paul Wise]

On Fri, Sep 12, 2014 at 5:09 AM, Alexandre Rossi wrote:

> From some other discussion, I had understood that including the
> missing source was enough. What is your advice here : should I add a
> Makefile to regenerate those files that don't even get in the binary
> package? Should I repack the source to get rid of those (which would
> be a pity : the archived source package would be stripped of its test
> suite) ?

The ideal situation is that the upstream tarball (and VCS) contain
only source (no generated files) and contain no embedded code copies
of other projects. If you can convince them to do that it would be
helpful. If they want tarballs that contain more than just their
source, they could generate some extra ones.

https://wiki.debian.org/EmbeddedCodeCopies

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#761088: closed by Michael Biebl (Re: [Pkg-utopia-maintainers] Bug#761088: policykit-1: Unable to install Policykit-1 0.105-6.1 without Systemd)

[parspes]

 Looking at the package I see listed as a Depends libpam-systemd which
has systemd listed as a Depends. This prevents installation without
broken packages. When package libpam-systemd is selected systemd is
automatically selected for installation also.

On 9/10/14, Debian Bug Tracking System  wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the policykit-1 package:
>
> #761088: policykit-1: Unable to install Policykit-1 0.105-6.1 without
> Systemd
>
> It has been closed by Michael Biebl .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Biebl
>  by
> replying to this email.
>
>
> --
> 761088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761088
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>


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

Bug#758105: bug#18266: handling bytes not part of the charset, and other garbage

[Vincent Lefevre]

On 2014-09-11 18:16:29 -0700, Paul Eggert wrote:
> Vincent Lefevre wrote:
> >the C locale corresponds to ANSI_X3.4-1968,
> 
> No it doesn't, at least not on any current platform I'm aware of.

It does on Debian:

ypig% LC_ALL=C locale charmap
ANSI_X3.4-1968

> >I would say that this should be the same for invalid
> >byte sequences in a UTF-8 locale.
> 
> One *could* design an encoding with that property, but it wouldn't be UTF-8;
> it would be something else.  I don't know of any C library that does that to
> UTF-8.  There are good arguments against doing it, e.g., one loses the
> property that one can concatenate character strings by concatenating their
> byte representations.

I'm talking only about grep here.

BTW, the current behavior breaks the sometimes used "grep ." solution
to match non-empty lines.

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


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

Bug#758105: bug#18266: Bug#758105: bug#18266: grep -P and invalid exits with error

[Vincent Lefevre]

On 2014-09-11 10:07:49 -0700, Paul Eggert wrote:
> Vincent Lefevre wrote:
> >I've just reported a new Debian concerning the performance problem.
> 
> It's not clear from http://bugs.debian.org/761157 that the performance
> problem occurs only with -P, but I assume that's what is meant.

It's specific to -P:

2.18-2   0.9s with -P, 0.4s without -P
2.20-3  11.6s with -P, 0.4s without -P

> Since this is a performance bug with PCRE, I suggest moving the Debian bug
> report to the Debian libpcre3 package.  Grep cannot go back to the old way,
> which could cause grep to crash, and the bug cannot be fixed in grep because
> libpcre3 does not provide a fast way to search arbitrary data that may
> include encoding errors.  It really is a problem that requires changes to
> libpcre3 to fix; grep cannot fix it.

Fixing the performance problem in libpcre3 would indeed be better
(even with the old version of grep, libpcre3 was twice as slow as
grep, but this is less critical than a 13x slowdown).

However a workaround in grep could be simpler. I've just opened a
new bug and suggested several solutions:

  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18454

> In the meantime, in order to use 'grep' to search for strings in arbitrary
> data, I suggest omitting the '-P'.

This is a bit annoying because I sometimes use specific PCRE features.
I could try to parse the arguments, detect where the pattern is used,
and avoid -P if the pattern doesn't use specific PCRE features (at
least for the most common forms). An additional advantage is that it
could be twice as fast in most cases (see above). This could also be
done in grep, as I suggested in my new bug report.

> Also, I suggest using the C locale.

This could be a solution, because in practice, I pipe the result
to "less -FRX", but only grep has to use the C locale, so that the
accented characters are correctly displayed by "less". However with
some (rare?) patterns, it won't work because an accented character
would no longer be seen as a single character.

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


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

Bug#761215: base-passwd: Changes made to passwd file without administrator permission

[Russ Allbery]

deb...@j.hallam.dk writes:

> Since the shell entry for news is set deliberately by me, I expect
> base-passwd to ASK whether it may change it.

It does, but it asks with a debconf prompting level chosen via an educated
guess about some combination of how likely it is that the change was
important, intentional, not spammy on upgrades, etc.  It sounds like that
heuristic failed in your case.  Unfortunately, we have to make a guess at
what priority to use for everyone.

The general rule of thumb is that changes to home directories, UIDs, GIDs,
or removing a user entirely are asked with high priority, changes to
shells are asked with medium priority, and changes to GECOS and some other
low-impact stuff are asked with low priority.  So you would need your
prompting level set to medium or lower to see the prompts about shell
changes.

-- 
Russ Allbery (r...@debian.org)   


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

Bug#718154: unreproducible (re: psychopy: FTBFS: Tests failed)

[Olly Betts]

Control: tags -1 -unreproducible

On Thu, Oct 10, 2013 at 10:11:04PM +0900, Hideki Yamane wrote:
> I can't reproduce this bug under cowbuilder amd64 (both baremetal and KVM).
> see attached build log.

It's completely reproducible if you use sbuild (it happens when
rebuilding on my machine).

The important difference is that sbuild sets HOME=/sbuild-nonexistent - see
the "User Environment":

http://aws-logs.debian.net/ftbfs-logs/2013/07/26/psychopy_1.77.02.dfsg-1_unstable.log

I'm not very familiar with cowbuilder, but if there's a way to set
environment variables for the build with it, try setting HOME to a
non-existent directory.  Or add this near the start of debian/rules:

export HOME=/sbuild-nonexistent

A simple fix is probably to create a temporary directory and point
HOME to it while running tests.  That should fix the build with sbuild
and is much better for reproducible tests than using someone's actual
home directory.

Cheers,
Olly


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

Bug#759090: psychopy: Patch for wxPython 3.0

[Olly Betts]

Control: tags 759090 + patch

Attached is a patch for wxPython 3.0.

I successfully built the package with DEB_BUILD_OPTIONS=nocheck (build time
tests fail with sbuild due to #718154), and it seems to run OK, though I'm
not familiar with it and it seems quite complex so testing by a habitual
user would be better.

Let me know if you'd like me to NMU this patch, along with a fix for
#718154 if I can manage one.

Cheers,
Olly
diff -Nru psychopy-1.79.00+git16-g30c9343.dfsg/debian/changelog psychopy-1.79.00+git16-g30c9343.dfsg/debian/changelog
--- psychopy-1.79.00+git16-g30c9343.dfsg/debian/changelog	2013-12-21 14:39:17.0 -0300
+++ psychopy-1.79.00+git16-g30c9343.dfsg/debian/changelog	2014-09-11 21:40:50.0 -0300
@@ -1,3 +1,11 @@
+psychopy (1.79.00+git16-g30c9343.dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for wxPython 3.0 (Closes: #759090):
+- New patch: wxpython3.0.patch
+
+ -- Olly Betts   Fri, 12 Sep 2014 00:40:28 +
+
 psychopy (1.79.00+git16-g30c9343.dfsg-1) unstable; urgency=low
 
   * New release (+ post-release fixes)
diff -Nru psychopy-1.79.00+git16-g30c9343.dfsg/debian/control psychopy-1.79.00+git16-g30c9343.dfsg/debian/control
--- psychopy-1.79.00+git16-g30c9343.dfsg/debian/control	2013-12-21 14:39:17.0 -0300
+++ psychopy-1.79.00+git16-g30c9343.dfsg/debian/control	2014-09-11 21:32:56.0 -0300
@@ -10,7 +10,7 @@
xvfb, xauth, libgl1-mesa-dri,
python-pyglet, python-pygame, python-opengl,
python-scipy, python-matplotlib, python-lxml,
-   python-configobj, python-imaging, python-openpyxl, python-mock, python-wxgtk2.8, libavbin0, python-pyo,
+   python-configobj, python-imaging, python-openpyxl, python-mock, python-wxgtk3.0, libavbin0, python-pyo,
python-pytest,
 Vcs-Git: git://git.debian.org/git/pkg-exppsy/psychopy.git
 Vcs-Browser: http://git.debian.org/?p=pkg-exppsy/psychopy.git
@@ -25,7 +25,7 @@
   python-numpy, python-scipy, python-matplotlib,
   python-lxml,
   python-configobj
-Recommends: python-wxgtk2.8,
+Recommends: python-wxgtk3.0,
 python-pyglet, python-pygame,
 python-openpyxl,
 python-imaging,
diff -Nru psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/series psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/series
--- psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/series	2013-12-21 14:39:17.0 -0300
+++ psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/series	2014-09-11 21:38:51.0 -0300
@@ -1,3 +1,4 @@
 deb_do_not_regenerate_init
 deb_use_system_serial
 update_matplotlib_test
+wxpython3.0.patch
diff -Nru psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/wxpython3.0.patch psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/wxpython3.0.patch
--- psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/wxpython3.0.patch	1969-12-31 21:00:00.0 -0300
+++ psychopy-1.79.00+git16-g30c9343.dfsg/debian/patches/wxpython3.0.patch	2014-09-11 22:07:20.0 -0300
@@ -0,0 +1,430 @@
+Description: Update for wxPython 3.0
+ These changes should remain compatible with wxPython 2.8.
+Bug-Debian: https://bugs.debian.org/759090
+Forwarded: no
+Last-Update: 2014-09-11
+
+Index: psychopy-1.79.00+git16-g30c9343.dfsg/psychopy/app/builder/builder.py
+===
+--- psychopy-1.79.00+git16-g30c9343.dfsg.orig/psychopy/app/builder/builder.py
 psychopy-1.79.00+git16-g30c9343.dfsg/psychopy/app/builder/builder.py
+@@ -23,17 +23,17 @@ from psychopy.app.builder import validat
+ from psychopy.constants import *
+ 
+ canvasColor=[200,200,200]#in prefs? ;-)
+-routineTimeColor=wx.Color(50,100,200, 200)
+-staticTimeColor=wx.Color(200,50,50, 100)
+-nonSlipFill=wx.Color(150,200,150, 255)
+-nonSlipEdge=wx.Color(0,100,0, 255)
+-relTimeFill=wx.Color(200,150,150, 255)
+-relTimeEdge=wx.Color(200,50,50, 255)
+-routineFlowColor=wx.Color(200,150,150, 255)
+-darkgrey=wx.Color(65,65,65, 255)
+-white=wx.Color(255,255,255, 255)
+-darkblue=wx.Color(30,30,150, 255)
+-codeSyntaxOkay=wx.Color(220,250,220, 255)  # light green
++routineTimeColor=wx.Colour(50,100,200, 200)
++staticTimeColor=wx.Colour(200,50,50, 100)
++nonSlipFill=wx.Colour(150,200,150, 255)
++nonSlipEdge=wx.Colour(0,100,0, 255)
++relTimeFill=wx.Colour(200,150,150, 255)
++relTimeEdge=wx.Colour(200,50,50, 255)
++routineFlowColor=wx.Colour(200,150,150, 255)
++darkgrey=wx.Colour(65,65,65, 255)
++white=wx.Colour(255,255,255, 255)
++darkblue=wx.Colour(30,30,150, 255)
++codeSyntaxOkay=wx.Colour(220,250,220, 255)  # light green
+ 
+ # regular expression to check for unescaped '$' to indicate code:
+ _unescapedDollarSign_re = re.compile(r"^\$|[^\\]\$")
+@@ -282,9 +282,9 @@ class FlowPanel(wx.ScrolledWindow):
+ self.btnInsertRoutine = platebtn.PlateButton(self,-1,'Insert Routine ', pos=(10,10))
+ self.btnInsertLoop = platebtn.PlateButton(self,-1,'Insert Loop ', p

Bug#671032: Bug#631427: gcc-4.6: FTBFS with GCC_TARGET

[YunQiang Su]

Control: reassign -1 gcc-4.9

On Tue, 01 May 2012 14:01:19 +0200 Matthias Klose  wrote:
> clone 631427 -1
> reassign -1 debhelper
> retitle -1 dh_strip should handle both host and target objects
> thanks
>
> On 23.06.2011 21:17, Adam Borowski wrote:
> > Package: src:gcc-4.6
> > Version: 4.6.0-14
> > Severity: normal
> >
> > Hi!
> >
> > When building a cross compiler, there are two problems:
> >
> > 1. hardcoded use of gcc-4.4 without a declared build-dependency.
>
> now uses gcc. You can't always rely on newer gcc versions for non primary or 
> non
> secondary architectures.
>
> > 2. dh_strip is used both on objects for the build and host arch.  This does
> > not work.  You'd need to either:
> > a) call either native or cross strip appropriately
> > b) build-depend on binutils-multiarch
> > c) Loic Minier suggested there is some way to force dh_strip to do a),
> >although for whatever reason it doesn't work in current unstable
>
> these packages can contain both code for the host and the target. dh_strip
> should either provide a way to handle these automatically, or accept an option
> for the strip binary to use (and then -X could be used to not strip some 
> objects).
>
>

dh_strip can do it now with setting DEB_HOST_GNU_TYPE
The attached patch can fix this bug.

>
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-d.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-d.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-d.mk
+++ gcc-4.9-4.9.1/debian/rules.d/binary-d.mk
@@ -117,7 +117,7 @@
debian/dh_doclink -p$(p_libphobos) $(p_base)
 endif
 
-   dh_strip -p$(p_libphobos)
+   $(cross_strip) dh_strip -p$(p_libphobos)
dh_compress -p$(p_libphobos)
dh_fixperms -p$(p_libphobos)
dh_shlibdeps -p$(p_libphobos)
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-fortran.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-fortran.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-fortran.mk
+++ gcc-4.9-4.9.1/debian/rules.d/binary-fortran.mk
@@ -97,7 +97,7 @@
cp debian/$(p_l).overrides 
debian/$(p_l)/usr/share/lintian/overrides/$(p_l); \
fi
 
-   dh_strip -p$(p_l) --dbg-package=$(p_d)
+   $(cross_strip) dh_strip -p$(p_l) --dbg-package=$(p_d)
dh_compress -p$(p_l) -p$(p_d)
dh_fixperms -p$(p_l) -p$(p_d)
$(cross_makeshlibs) dh_makeshlibs -p$(p_l)
@@ -137,7 +137,7 @@
debian/dh_doclink -p$(p_l) $(p_base)
debian/dh_rmemptydirs -p$(p_l)
 
-   dh_strip -p$(p_l)
+   $(cross_strip) dh_strip -p$(p_l)
dh_compress -p$(p_l)
dh_fixperms -p$(p_l)
$(cross_shlibdeps) dh_shlibdeps -p$(p_l)
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-go.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-go.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-go.mk
+++ gcc-4.9-4.9.1/debian/rules.d/binary-go.mk
@@ -101,7 +101,7 @@
debian/dh_doclink -p$(p_l) $(p_base)
debian/dh_doclink -p$(p_d) $(p_base)
 
-   dh_strip -p$(p_l) --dbg-package=$(p_d)
+   $(cross_strip) dh_strip -p$(p_l) --dbg-package=$(p_d)
dh_compress -p$(p_l) -p$(p_d)
dh_fixperms -p$(p_l) -p$(p_d)
$(cross_makeshlibs) dh_makeshlibs -p$(p_l)
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-libasan.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-libasan.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-libasan.mk
+++ gcc-4.9-4.9.1/debian/rules.d/binary-libasan.mk
@@ -35,7 +35,7 @@
cp debian/$(p_l).overrides 
debian/$(p_l)/usr/share/lintian/overrides/$(p_l); \
fi
 
-   dh_strip -p$(p_l) --dbg-package=$(p_d)
+   $(cross_strip) dh_strip -p$(p_l) --dbg-package=$(p_d)
dh_compress -p$(p_l) -p$(p_d)
dh_fixperms -p$(p_l) -p$(p_d)
$(cross_makeshlibs) dh_makeshlibs -p$(p_l)
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-libatomic.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-libatomic.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-libatomic.mk
+++ gcc-4.9-4.9.1/debian/rules.d/binary-libatomic.mk
@@ -30,7 +30,7 @@
debian/dh_doclink -p$(p_l) $(p_base)
debian/dh_doclink -p$(p_d) $(p_base)
 
-   dh_strip -p$(p_l) --dbg-package=$(p_d)
+   $(cross_strip) dh_strip -p$(p_l) --dbg-package=$(p_d)
dh_compress -p$(p_l) -p$(p_d)
dh_fixperms -p$(p_l) -p$(p_d)
$(cross_makeshlibs) dh_makeshlibs -p$(p_l)
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-libcilkrts.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-libcilkrts.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-libcilkrts.mk
+++ gcc-4.9-4.9.1/debian/rules.d/binary-libcilkrts.mk
@@ -35,7 +35,7 @@
cp debian/$(p_l).overrides 
debian/$(p_l)/usr/share/lintian/overrides/$(p_l); \
fi
 
-   dh_strip -p$(p_l) --dbg-package=$(p_d)
+   $(cross_strip) dh_strip -p$(p_l) --dbg-package=$(p_d)
dh_compress -p$(p_l) -p$(p_d)
dh_fixperms -p$(p_l) -p$(p_d)
$(cross_makeshlibs) dh_makeshlibs -p$(p_l)
diff -u gcc-4.9-4.9.1/debian/rules.d/binary-libgcc.mk 
gcc-4.9-4.9.1/debian/rules.d/binary-libgcc.mk
--- gcc-4.9-4.9.1/debian/rules.d/binary-libgcc.mk
+++ gcc-4.

Bug#759074: pyserial: Patch for wxPython 3.0

[Olly Betts]

Control: tags 759074 + patch

I've rebuilt pyserial with the attached patch, and tested both:

python /usr/share/doc/python-serial/examples/wxSerialConfigDialog.py
python /usr/share/doc/python-serial/examples/wxTerminal.py

I don't have anything on a serial port to connect a terminal to, so I couldn't
actually open a terminal, but the UIs seem to work aside from that.

Cheers,
Olly
diff -u pyserial-2.6/debian/control pyserial-2.6/debian/control
--- pyserial-2.6/debian/control
+++ pyserial-2.6/debian/control
@@ -11,7 +11,7 @@
 Package: python-serial
 Architecture: all
 Depends: ${python:Depends}, ${misc:Depends}
-Suggests: python-wxgtk2.8 | python-wxgtk
+Suggests: python-wxgtk3.0 | python-wxgtk
 XB-Python-Version: ${python:Versions}
 Description: pyserial - module encapsulating access for the serial port
  This module encapsulates the access for the serial port. It provides
@@ -22,7 +22,7 @@
 Package: python3-serial
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}
-Suggests: python3-wxgtk2.8 | python3-wxgtk
+Suggests: python3-wxgtk3.0 | python3-wxgtk
 XB-Python-Version: ${python3:Versions}
 Description: pyserial - module encapsulating access for the serial port
  This module encapsulates the access for the serial port. It provides
diff -u pyserial-2.6/debian/changelog pyserial-2.6/debian/changelog
--- pyserial-2.6/debian/changelog
+++ pyserial-2.6/debian/changelog
@@ -1,3 +1,14 @@
+pyserial (2.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for wxPython 3.0, Closes: #759074:
+- debian/control: Update dependencies.
+- examples/wxSerialConfigDialog.py,examples/wxTerminal.py: Drop calls to
+  wx.InitAllImageHandlers() which is a no-op for 2.8 and gives a
+  deprecation warning with 3.0.  Update deprecated wx.SAVE to wx.FD_SAVE.
+
+ -- Olly Betts   Fri, 12 Sep 2014 02:10:04 +
+
 pyserial (2.6-1) unstable; urgency=low
 
   * New upstream version. Closes: #664788.
only in patch2:
unchanged:
--- pyserial-2.6.orig/examples/wxSerialConfigDialog.py
+++ pyserial-2.6/examples/wxSerialConfigDialog.py
@@ -229,8 +229,6 @@
 class MyApp(wx.App):
 """Test code"""
 def OnInit(self):
-wx.InitAllImageHandlers()
-
 ser = serial.Serial()
 print ser
 #loop until cancel is pressed, old values are used as start for the next run
only in patch2:
unchanged:
--- pyserial-2.6.orig/examples/wxTerminal.py
+++ pyserial-2.6/examples/wxTerminal.py
@@ -202,7 +202,7 @@
 def OnSaveAs(self, event):
 """Save contents of output window."""
 filename = None
-dlg = wx.FileDialog(None, "Save Text As...", ".", "", "Text File|*.txt|All Files|*",  wx.SAVE)
+dlg = wx.FileDialog(None, "Save Text As...", ".", "", "Text File|*.txt|All Files|*",  wx.FD_SAVE)
 if dlg.ShowModal() ==  wx.ID_OK:
 filename = dlg.GetPath()
 dlg.Destroy()
@@ -320,7 +320,6 @@
 
 class MyApp(wx.App):
 def OnInit(self):
-wx.InitAllImageHandlers()
 frame_terminal = TerminalFrame(None, -1, "")
 self.SetTopWindow(frame_terminal)
 frame_terminal.Show(1)

Bug#758105: bug#18266: handling bytes not part of the charset, and other garbage

[Paul Eggert]

Vincent Lefevre wrote:


ypig% LC_ALL=C locale charmap
ANSI_X3.4-1968


That may be what the 'locale' command says, but bytes with the top bit 
on are considered to be valid single-byte characters.  There are no 
encoding errors.  So, in that sense it's not strict ASCII.



the current behavior breaks the sometimes used "grep ." solution
to match non-empty lines.


"grep ." matches lines containing one or more characters.  Encoding 
errors are not characters, at least, not as far as plain grep is concerned.


Perhaps PCRE is different, and if libpcre worked with encoding errors we 
could simply use its way of matching them.  But there doesn't seem to be 
a safe way to do that.



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

Bug#761219: debian-policy: document versioned Provides

[Guillem Jover]

Hi!

On Thu, 2014-09-11 at 21:57:57 +0300, Niko Tyni wrote:
> dpkg 1.17.11 and apt 1.0.7 recently implemented support for versioned
> provides. From the dpkg changelog:
> 
>   * Add versioned Provides support:
> - Add a new dpkg --assert-versioned-provides command.
> - Packages can provide a specific version, “virtual (= 1.0)” which will
>   be honored, previously it would just be accepted when parsing.
> - Non-versioned virtual packages will not satisfy versioned dependencies.
> - Versioned virtual packages will satisfy non-versioned dependencies.

Just a quick note here, I noticed several days ago that I missed
updating the perl code to also handle versioned Provides (so
dpkg-checkbuilddeps will not work on those yet). I've got this fixed
locally pending a bit more testing, but it will make it into 1.17.14,
to be released RSN (i.e. days).

Thanks,
Guillem


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

Bug#761246: O: libpgm -- OpenPGM shared library

[Ana Guerrero Lopez]

Package: wnpp
Severity: normal

The current maintainer of libpgm, Gabriel de Perthuis 
,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: libpgm
Binary: libpgm-5.1-0, libpgm-dbg, libpgm-dev
Version: 5.1.118-1~dfsg-0.1
Maintainer: Gabriel de Perthuis 
Build-Depends: debhelper (>= 7.0.50~), python, libtool, automake
Architecture: any
Standards-Version: 3.9.1
Format: 3.0 (quilt)
Files:
 6e99dcdc6d52b8193cdcea07eb434235 1350 libpgm_5.1.118-1~dfsg-0.1.dsc
 9067f5b94f2672fb9e93bd9b4fcc701d 1154570 libpgm_5.1.118-1~dfsg.orig.tar.gz
 3d299c47b35fa91ee7dc64acc26b22ac 4686 libpgm_5.1.118-1~dfsg-0.1.debian.tar.gz
Vcs-Browser: https://github.com/g2p/libpgm
Vcs-Git: https://github.com/g2p/libpgm.git
Checksums-Sha1:
 2f1f76f839f3ee987e2dd05ce28bf89616f26475 1350 libpgm_5.1.118-1~dfsg-0.1.dsc
 aa5e5562d76404310bf88deca263963d9b48dbca 1154570 
libpgm_5.1.118-1~dfsg.orig.tar.gz
 4f5b76f04de0762023c1fb48923ee0449ad96f9a 4686 
libpgm_5.1.118-1~dfsg-0.1.debian.tar.gz
Checksums-Sha256:
 a9d077d56198dd30cf304f1e148d4d98bb83054f43a42723c572dbd24154d0c1 1350 
libpgm_5.1.118-1~dfsg-0.1.dsc
 8d45cb9753ee942b3fa174008ac287fde9aaf5ce61719430d0673ace8d39659c 1154570 
libpgm_5.1.118-1~dfsg.orig.tar.gz
 45ecf9d56f83de72208a34bb4f816a5d09232a3afa1e75d3dcf44cfd98db14bd 4686 
libpgm_5.1.118-1~dfsg-0.1.debian.tar.gz
Homepage: http://code.google.com/p/openpgm/
Package-List: 
 libpgm-5.1-0 deb libs optional
 libpgm-dbg deb debug extra
 libpgm-dev deb libdevel optional
Directory: pool/main/libp/libpgm
Priority: source
Section: libs

Package: libpgm-5.1-0
Source: libpgm
Version: 5.1.118-1~dfsg-0.1
Installed-Size: 325
Maintainer: Gabriel de Perthuis 
Architecture: amd64
Depends: libc6 (>= 2.7)
Description-en: OpenPGM shared library
 OpenPGM is an open source implementation of the Pragmatic General Multicast
 (PGM) specification in RFC 3208 available at www.ietf.org. PGM is a reliable
 and scalable multicast protocol that enables receivers to detect loss,
 request retransmission of lost data, or notify an application of
 unrecoverable loss. PGM is a receiver-reliable protocol, which means the
 receiver is responsible for ensuring all data is received, absolving the
 sender of reception responsibility. PGM runs over a best effort datagram
 service, currently OpenPGM uses IP multicast but could be implemented above
 switched fabrics such as InfiniBand.
 .
 This is the runtime package for programs that use the OpenPGM library.
Description-md5: 46e778aa0963aa92ffc1db02a8b200a9
Homepage: http://code.google.com/p/openpgm/
Tag: devel::library, implemented-in::c, protocol::TODO, protocol::ip,
 protocol::ipv6, protocol::udp, role::shared-lib, use::transmission
Section: libs
Priority: optional
Filename: pool/main/libp/libpgm/libpgm-5.1-0_5.1.118-1~dfsg-0.1_amd64.deb
Size: 181268
MD5sum: 5acb53c55968678b81ae8e2998de1822
SHA1: e0ac9e8d04152e836e156d061e91ab31b5a1d12f
SHA256: 8952afb9a41c27979946aabc36502712d965a9715a56704c2694ced9836bc3cd

Package: libpgm-dbg
Source: libpgm
Version: 5.1.118-1~dfsg-0.1
Installed-Size: 863
Maintainer: Gabriel de Perthuis 
Architecture: amd64
Depends: libpgm-5.1-0 (= 5.1.118-1~dfsg-0.1)
Description-en: OpenPGM debugging symbols
 OpenPGM is an open source implementation of the Pragmatic General Multicast
 (PGM) specification in RFC 3208 available at www.ietf.org. PGM is a reliable
 and scalable multicast protocol that enables receivers to detect loss,
 request retransmission of lost data, or notify an application of
 unrecoverable loss. PGM is a receiver-reliable protocol, which means the
 receiver is responsible for ensuring all data is received, absolving the
 sender of reception responsibility. PGM runs over a best effort datagram
 service, currently OpenPGM uses IP multicast but could be implemented above
 switched fabrics such as InfiniBand.
 .
 These are the debugging symbols for the library and its utilities.
Description-md5: c20d43290e39204c269445c8443c3fad
Homepage: http://code.google.com/p/openpgm/
Tag: role::debug-symbols
Section: debug
Priority: extra
Filename: pool/main/libp/libpgm/libpgm-dbg_5.1.118-1~dfsg-0.1_amd64.deb
Size: 265892
MD5sum: 0357152a58c148199c3e24ef756dd529
SHA1: af57f6be7624e1e6d9b67971b5b13626083d48c1
SHA256: 0159df15d000e208a84174c462f23740391d0004832c05b569a9c38d76911ba7

Package: libpgm-dev
Source: libpgm
Version: 5.1.118-1~dfsg-0.1
Installed-Size: 694
Maintainer: Gabriel de Perthuis 
Architecture: amd64
Depends: libpgm-5.1-0 (= 5.1.118-1~dfsg-0.1)
Conflicts: libnetpbm9-dev
Description-en: OpenPGM development files
 OpenPGM is an open source implementation of the Pragmatic General Multicast
 (PGM) specification in RFC 3208 availab

Bug#761247: taskwarrior: Sync not availible -- not built with gnutls

[Jack Laxson]

Package: taskwarrior
Version: 2.3.0+dfsg-3
Severity: normal

> $ task sync
> Taskwarrior was built without GnuTLS support.  Sync is not available.

Is there a reason for this? or just no request so far?



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

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

Versions of packages taskwarrior depends on:
ii  libc6 2.19-10
ii  libgcc1   1:4.9.1-12
ii  libreadline6  6.3-8
ii  libstdc++64.9.1-12
ii  libuuid1  2.20.1-5.8

taskwarrior recommends no packages.

taskwarrior suggests no packages.

-- no debconf information


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

Bug#671032: Processed: Re: Bug#631427: gcc-4.6: FTBFS with GCC_TARGET

[Matthias Klose]

Control: reassign -1 debhelper
Control: tags -1 -patch

> dh_strip can do it now with setting DEB_HOST_GNU_TYPE
> The attached patch can fix this bug.

No, it can't handle cases with HOST and TARGET code in packages, and you only do
it for some library packages.

Please see that this issue was cloned for debhelper, and there is #631427 for 
GCC.

  Matthias


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

Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds

[Daniel Baumann]

retitle 759189 please use syslinux-utils instead of isolinux
reassign 759189 debian-installer
forcemerge 759189 751731
thanks

given that:

  * the original bug is in debian-installer which needed to be updated
for newer syslinux (and which has happened in git and which progress
of an uploaded can be tracked through it's original bug report at
#751731)

  * there's nothing that can be done in the syslinux package regarding
this bug report anyway (i.e. the bug 'goes' away without doing
anything at all in the syslinux package)

  * syslinux >= 3:6.03~pre19+dfsg-1 has migrated to testing regardless

  * there was repeatedly not given any purpose to what #759189 filed
against syslinux would be good for

i'm reassigning and merging this bug with #751731 again. feel free to
close it if you like to keep only #751731 open though.

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


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

Bug#757689: SCSI issue?

[Boris]

On Thu, 28 Aug 2014 00:39:44 +0200 =?UTF-8?Q?St=C3=A9phane?= 
 wrote:

> FWIW I have the issue on one of my machines but not two others; all
> machines are running up-to-date `testing` with lshw B.02.17.
> On the machine that has the issue (SIGSEV), this seems to be in the SCSI
> scanning module in my case; running
> sudo lshw -disable scsi
> does not crash lshw. Given the strace given by the original poster it
> seems to happen in a similar location in their case.
>
> To answer's Leonardo's question, #740034 is referring to an issue that
> crashes the machine when running lshw; here we're facing a bug inside
> lshw (or one of its dependencies).
>
> There are no symbols inside /usr/bin/lshw and no lshw-dbg package so I
> had to build a debug version manually. If I use the orig.tar.gz, apply
> Debian's diff.gz, then start dpkg-buildpackage, the binary src/lshw
> crashes. The stack trace is useless for some reason. However the same
> code (accidentally) compiled using "make" in src/ gives a working lshw;
> I noticed the optimization was different (none in the original Makefile,
> -O2 when compiling for dpkg-buildpackage).
>
> I modified debian/rules to always do -O0 and once installed, the
> resulting lshw does not crash anymore when running `sudo /usr/bin/lshw`.
>
>
Your described my situation exactly. Segfault somewhere on SCSI 
scanning, works ok with 'sudo lshw -disable scsi'. I have strace log 
similar to that in bugreport and can't give more info without dbg 
symbols. I tried to launch lshw with gdb, but it is completely useless.

lshw-gtk also crashes when called with gksu or kdesudo.

--
Best regards,
Boris Egorov


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

Bug#761248: gcc-4.9: Please enable gnat for kFreeBSD and Hurd again

[Svante Signell]

Source: gcc-4.9
Version: 4.9.1-13
Severity: important
User: debian-h...@lists.debian.org
Usertags: hurd, kfreebsd

>From the changelog of 4.9.1-6:
gcc-4.9 (4.9.1-6) unstable; urgency=medium

  * Disable Ada for snapshot builds on kfreebsd-i386, kfreebsd-amd64.
Local patch needs an update and upstreaming.
  * Disable Ada for snapshot builds on hurd-i386, build dependencies are
not installable.

Please enable gnat for Hurd and kfreeBSD again. Without it gnat1 is not
found by gcc-4.9 and all packages scheduled for build fails.
For Hurd the missing build dependency of gdb is no more and gnat-4.9.1
builds, see:
https://buildd.debian.org/status/fetch.php?pkg=gnat-4.9&arch=hurd-i386&ver=4.9.1-1%2Bb1&stamp=1407885531

For kFreeBSD I admit that the local patch should be updated and
submitted upstream (and the Hurd patch), but due to this gnat is
scheduled for removal from testing with bug #759407.

Ludovic, can you help out here?

Below is the relevant part of the debdiff from between 4.9.1-6 and
4.9.1-5:
 --- gcc-4.9-4.9.1/debian/rules.defs
+++ gcc-4.9-4.9.1/debian/rules.defs
@@ -521,9 +521,7 @@
 ifeq ($(single_package),yes)
   ada_no_cpus += m68k powerpcspe sh4 sparc64
   ada_no_cpus += alpha
-  ifneq (,$(filter $(DEB_TARGET_ARCH),m68k mips mipsel powerpcspe sh4 sparc64 
hurd-i386 kfreebsd-i386 kfreebsd-amd64))
-ada_no_cpus += mips mipsel
-ada_no_cpus += hurd-i386 kfreebsd-i386 kfreebsd-amd64
+  ifneq (,$(filter $(DEB_TARGET_ARCH),m68k powerpcspe sh4 sparc64))
 ada_no_snap := yes
   endif
 endif


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

Bug#722989: gsmartcontrol: diff for NMU version 0.8.7-1.1

[Stephen Kitt]

Control: tags 722989 + pending

Dear maintainer,

I've prepared an NMU for gsmartcontrol (versioned as 0.8.7-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Stephen
diff -Nru gsmartcontrol-0.8.7/debian/changelog gsmartcontrol-0.8.7/debian/changelog
--- gsmartcontrol-0.8.7/debian/changelog	2013-05-31 15:58:29.0 +0200
+++ gsmartcontrol-0.8.7/debian/changelog	2014-09-12 08:42:32.0 +0200
@@ -1,3 +1,11 @@
+gsmartcontrol (0.8.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Handle empty sections in recent versions of smartmontools; thanks to
+Francesco Presel for the patch. Closes: #722989.
+
+ -- Stephen Kitt   Fri, 12 Sep 2014 08:40:12 +0200
+
 gsmartcontrol (0.8.7-1) unstable; urgency=low
 
   * [314881d] Updated debian/watch
diff -Nru gsmartcontrol-0.8.7/debian/patches/compat_with_smartmontools_6.patch gsmartcontrol-0.8.7/debian/patches/compat_with_smartmontools_6.patch
--- gsmartcontrol-0.8.7/debian/patches/compat_with_smartmontools_6.patch	1970-01-01 01:00:00.0 +0100
+++ gsmartcontrol-0.8.7/debian/patches/compat_with_smartmontools_6.patch	2014-09-12 08:39:45.0 +0200
@@ -0,0 +1,22 @@
+Description: don't try to parse empty sections
+ Since smartmontools 6.0, the output is divided in sections regardless of the
+ drive having or not SMART capabilities; in the latter case the last section
+ is empty. In that case, just skip it (parsing empty sections causes a crash).
+Author: Francesco Presel 
+Bug-Debian: http://bugs.debian.org/722989
+Last-Update: <2014-01-23>
+
+--- a/src/applib/smartctl_parser.cpp
 b/src/applib/smartctl_parser.cpp
+@@ -202,7 +202,10 @@
+ 			&& (section_start_pos = s.find("===", section_start_pos)) != std::string::npos) {
+ 
+ 		tmp_pos = s.find("\n", section_start_pos);  // works with \r\n too.
+-
++		if (tmp_pos == std::string::npos) { // empty section: skip
++			break;
++		}
++			
+ 		// trim is needed to remove potential \r in the end
+ 		std::string section_header = hz::string_trim_copy(s.substr(section_start_pos,
+ (tmp_pos == std::string::npos ? tmp_pos : (tmp_pos - section_start_pos)) ));
diff -Nru gsmartcontrol-0.8.7/debian/patches/series gsmartcontrol-0.8.7/debian/patches/series
--- gsmartcontrol-0.8.7/debian/patches/series	2013-05-31 15:58:29.0 +0200
+++ gsmartcontrol-0.8.7/debian/patches/series	2014-09-12 08:40:05.0 +0200
@@ -1,3 +1,4 @@
 01_use_su-to-root.patch
 02_fix_doc_install.patch
 03_gcc4.4.patch
+compat_with_smartmontools_6.patch


signature.asc
Description: Digital signature

Bug#587063: ITA: libvigraimpex -- C++ computer vision library

[Daniel Stender]

Working on a new package.

Greetings,
Daniel Stender

--
http://www.danielstender.com/blog
PGP key: 2048R/1DFED696


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