Bug#650386: reportbug: reports against src:binarypackagename
On Sat, Oct 18, 2014 at 7:08 PM, Jakub Wilk jw...@debian.org wrote: * Julien Cristau jcris...@debian.org, 2014-10-07, 18:53: I think the (untested) patch below would fix this and only set issource if the user actually selected the source package. I think I will go with this patch: diff --git a/bin/reportbug b/bin/reportbug index e429e6c..9bfd4a1 100755 --- a/bin/reportbug +++ b/bin/reportbug @@ -1429,7 +1429,7 @@ class UI(object): pkgversion = v break elif len(packages) 0: -src = package +src = utils.get_source_name(package) if len(packages) and not notatty: packages.sort() if src not in [x[0] for x in packages]: I gave it some testing, but I'd be happy to hear from you for some corner case I might have missed. As I told Julien on IRC, with this patch I am prompted twice to select the package: which exposes a similar behaviour: $ PYTHONPATH=. ./bin/reportbug --debug -O zlib1g *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Sandro Tosi mo...@debian.org' as your from address. Getting status for zlib1g... Which of the following packages is the bug in? 1 lib32z1 compression library - 32 bit runtime 2 lib32z1-dev compression library - 32 bit development 3 lib64z1 compression library - 64 bit runtime 4 lib64z1-dev compression library - 64 bit development 5 zlib-bin compression library - sample programs 6 zlib1g compression library - runtime 7 zlib1g-dbg compression library - development 8 zlib1g-dev compression library - development 9 zlib Source package Select one of these packages: 6 Getting status for zlib1g... Which of the following installed packages is the bug in? 1 zlib1g compression library - runtime 2 zlib1g compression library - runtime 3 zlib1g Uninstalled/non-existent package, which misses the arch qualification of the packages, but I think it's better than now. I will fix the last menu to include teh arch qualif too. Cheers (and sorry for the long overdue on this bug), -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650386: reportbug: reports against src:binarypackagename
Package: reportbug On Sat, Oct 18, 2014 at 7:08 PM, Jakub Wilk jw...@debian.org wrote: * Julien Cristau jcris...@debian.org, 2014-10-07, 18:53: I think the (untested) patch below would fix this and only set issource if the user actually selected the source package. As I told Julien on IRC, with this patch I am prompted twice to select the package: $ dpkg-query -W zlib1g zlib1g:amd641:1.2.8.dfsg-2 zlib1g:i386 1:1.2.8.dfsg-2 $ reportbug zlib1g *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Jakub Wilk jw...@debian.org' as your from address. Getting status for zlib1g... Which of the following packages is the bug in? 1 lib32z1 compression library - 32 bit runtime 2 lib32z1-dev compression library - 32 bit development 3 lib64z1 compression library - 64 bit runtime 4 lib64z1-dev compression library - 64 bit development 5 zlib1g compression library - runtime 6 zlib1g-dbg compression library - development 7 zlib1g-dev compression library - development Select one of these packages: 5 Which of the following installed packages is the bug in? 1 zlib1g compression library - runtime 2 zlib1g compression library - runtime 3 zlib1g Uninstalled/non-existent package this menu should present the arch-qualification of the 2 packages -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650386: [reportbug/master] correctly identify source packages when presenting the packages menu, preventing from reporting bugs against unexisting source packages; thanks to Jakub Wilk and Andreas
tag 650386 pending tag 650386 pending thanks Date: Wed Oct 29 00:03:54 2014 + Author: Sandro Tosi mo...@debian.org Commit ID: 9860ca230fd7a5899a8d06ed710f8d0d45f4ec59 Commit URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=9860ca230fd7a5899a8d06ed710f8d0d45f4ec59 Patch URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=9860ca230fd7a5899a8d06ed710f8d0d45f4ec59 correctly identify source packages when presenting the packages menu, preventing from reporting bugs against unexisting source packages; thanks to Jakub Wilk and Andreas Beckmann for the report; Closes: #650386 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765144: [Pkg-amule-devel] Bug#765144: amule: FTBFS: Logger.h:346: undefined reference to `MULE_EVT_LOGLINE'
control: tags -1 +unreproducible +moreinfo Hello David, On Mon, Oct 13, 2014 at 5:53 PM, David Suárez david.sephi...@gmail.com wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): g++ -W -Wall -Wshadow -Wundef -pthread -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -lpthread -Wl,-z,relro -o amulecmd amulecmd-TextClient.o amulecmd-ExternalConnector.o amulecmd-LoggerConsole.o amulecmd-OtherFunctions.o amulecmd-NetworkFunctions.o -Llibs/common -Llibs/ec/cpp -L. -lmulecommon -lec -lmulesocket -L/usr/lib/x86_64-linux-gnu -pthread -lwx_baseu_net-3.0 -lwx_baseu-3.0 -lreadline -lz amulecmd-LoggerConsole.o: In function `CLoggingEvent': /«BUILDDIR»/amule-2.3.1+git1a369e47/obj-x86_64-linux-gnu/src/../../src/Logger.h:346: undefined reference to `MULE_EVT_LOGLINE' collect2: error: ld returned 1 exit status I just rebuild amule in an up-to-date sid chroot and I cant reproduce the problem. Do you know what could have gone wrong there? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760434: [Pkg-amule-devel] Bug#760434: amule: unusable GUI
2.3.1+git1a369e47-1 works flawlessly when built against WX-2.8. I'm going to close this bug soon, reverting amule to wx2.8 (at least our user will have a working amule, and it's not in testing anyway, like libwx2.8) and reopen 751241 - maybe the progression could be tracked there? Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760434: [Pkg-amule-devel] Bug#760434: amule: unusable GUI
Hello Olly, On Sat, Sep 13, 2014 at 5:10 PM, Olly Betts o...@survex.com wrote: There are two big changes between 2.3.1-11 and 2.3.1+git1a369e47-1 - one of them is indeed the switch to wx3.0, but the other is a switch to an upstream git snapshot of amule. the switch to the git snapshot was done because it seemed to include supports to wx3.0 in the unreleased code. I think it would be prudent to rebuild 2.3.1+git1a369e47-1 against wx2.8 and test if that has similar issues before blaming wx3.0 for these problems. While they could be related to wx3.0, I've not seen such issues in any other packages. Also, upstream's response to the forwarded ticket might be more useful if you could show it happens with wx2.8 too. I tried rebuilding 2.3.1+git1a369e47-1 with wx2.8 myself, but I couldn't trigger this behaviour from either the package in sid or my rebuilt version (I tried switching between tabs over and over as described above), so that's rather inconclusive. I wasn't connected to any networks though, so that's perhaps why it didn't manifest. I noticed wx upstream has applied a fix for the wxExecuteData issue (http://trac.wxwidgets.org/ticket/16325) - I can apply that to the wxwidgets3.0 package if you'd prefer to try updating 2.3.1-11 to work with wx3.0. Is there any chance you can give us a hand in fixing amule to support wx3.0? Upstream has only partially ported the code to it, and they are not actively working on it atm. IT would be a shame to ship Jessie without amule, but i dont have the resources to port amule to wx. I can consider getting back to 2.3.1-11 instead of the git snapshot if that makes the effort easier. Thanks Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759094: matplotlib: Please update to use wxpython3.0
Hello Olly, On Mon, Oct 13, 2014 at 4:13 AM, Olly Betts o...@survex.com wrote: On Fri, Sep 19, 2014 at 03:01:24PM +, mo...@users.alioth.debian.org wrote: tag 759094 + pending This bug has been marked as pending for 3.5 weeks now - is there a plan for when the next upload will be? I was waiting for some blockers to clear up: panda is fixed to support mpl 1.4 and now we have cairocffi which is needed to support GTK3 backend on py3k (and actually the preferred backend for GTK an all py versions), so hopefully I will find the time to finalize the upload in the coming days, sorry for the delay. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765300: pymvpa2: download files during build (intersphinx)
Source: pymvpa2 Version: 2.3.1-1 Severity: serious Hello, I just noticed this: loading intersphinx inventory from http://docs.python.org/objects.inv... loading intersphinx inventory from http://docs.scipy.org/doc/scipy/reference/objects.inv... loading intersphinx inventory from http://matplotlib.sourceforge.net/objects.inv... loading intersphinx inventory from http://nipy.sourceforge.net/nipy/stable/objects.inv... loading intersphinx inventory from http://docs.scipy.org/doc/numpy/objects.inv... loading intersphinx inventory from http://nipy.sourceforge.net/nipype/objects.inv... loading intersphinx inventory from http://h5py.alfven.org/docs/objects.inv... WARNING: intersphinx inventory 'http://h5py.alfven.org/docs/objects.inv' not fetchable due to class 'urllib2.HTTPError': HTTP Error 404: Not Found please either disable intersphing or use a technique similar to networkx when dealing with intersphinx. Regads, Sandro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764717: reportbug -- crash on start
control: severity -1 minor control: tags -1 +moreinfo On Sat, Oct 11, 2014 at 6:17 AM, Jörg Frings-Fürst deb...@jff-webhosting.net wrote: $ reportbug reportbug No protocol specified /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display this is the problem, you have configured to use GTK+ backend but it cant access a display. Sorry but this is not the problem. well likely it is... if you want to open a graphical application and it cant access the display, it wont start. 1. A call of reportbug in KDE and Gnome don't run (no window are open, also no setup window. do you mean from the applications menu? 2. By running in a terminal must open the windows. Or? if you have configured to run with GTK+ UI then usually yes, it should open the graphical interface. you can try running reportbug like this from the CLI: $ reportbug --ui=text Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763451: [Python-modules-team] Bug#763451: mpmath files should be installed in /usr/share/pyshared
control: reassign -1 python On Tue, Sep 30, 2014 at 12:42 PM, Sergey B Kirpichev skirpic...@gmail.com wrote: Package: mpmath Severity: serious Mpmath's source files are identical across all python's versions. You should share them in /usr/share/pyshared, see the policy [1]. .. [1] https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths policy is outdated (or misleading), reassigning. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
Hello Simon, On Thu, Aug 21, 2014 at 10:38 AM, Simon McVittie s...@debian.org wrote: --- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + +++ gtk2_ui.py 2014-08-21 09:29:02.843495121 + @@ -35,6 +35,7 @@ except: has_spell = False +gtk.set_interactive (0) gtk.gdk.threads_init () import sys sadly this patch didnt fix the problem, and I can replicate it in a clean sid chroot. do you have any other suggestions? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759908: [Python-modules-team] Bug#759908: python-graph: FTBFS: tests segfault
control: severity -1 normal control: forcemerge 750362 -1 Hello Lucas, On Sat, Aug 30, 2014 at 10:04 PM, Lucas Nussbaum lu...@lucas-nussbaum.net wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»' export PYTHONPATH=../core/build/lib.linux-x86_64-2.7 cd tests/ python2.7 testrunner.py No handlers could be found for logger __main__ test_accessibility_hypergraph (unittests-accessibility.test_accessibility) ... ok test_accessibility_in_digraph (unittests-accessibility.test_accessibility) ... ok test_accessibility_in_graph (unittests-accessibility.test_accessibility) ... ok test_accessibility_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok test_connected_components_hypergraph (unittests-accessibility.test_accessibility) ... ok test_connected_components_in_graph (unittests-accessibility.test_accessibility) ... ok test_connected_components_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok test_cut_edges_in_graph (unittests-accessibility.test_accessibility) ... ok test_cut_edges_in_hypergraph (unittests-accessibility.test_accessibility) ... ok test_cut_edges_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok test_cut_nodes_in_graph (unittests-accessibility.test_accessibility) ... ok test_cut_nodes_in_hypergraph (unittests-accessibility.test_accessibility) ... ok test_cut_nodes_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok test_mutual_accessibility_in_digraph (unittests-accessibility.test_accessibility) ... ok test_mutual_accessibility_in_graph (unittests-accessibility.test_accessibility) ... ok test_mutual_accessibility_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok test_critical_path (unittests-critical.test_critical_path_and_transitive_edges) ... ok test_critical_path_with_cycle (unittests-critical.test_critical_path_and_transitive_edges) ... ok test_empty_intersection (unittests-critical.test_critical_path_and_transitive_edges) ... ok test_partial_intersection (unittests-critical.test_critical_path_and_transitive_edges) ... ok test_transitivity (unittests-critical.test_critical_path_and_transitive_edges) ... ok test_transitivity_with_cycle (unittests-critical.test_critical_path_and_transitive_edges) ... ok test_find_cycle_on_digraph (unittests-cycles.test_find_cycle) ... ok test_find_cycle_on_digraph_without_cycles (unittests-cycles.test_find_cycle) ... ok test_find_cycle_on_graph (unittests-cycles.test_find_cycle) ... ok test_find_cycle_on_graph_withot_cycles (unittests-cycles.test_find_cycle) ... ok test_find_cycle_on_very_deep_graph (unittests-cycles.test_find_cycle) ... Segmentation fault make[2]: *** [test] Error 139 the package doesn't FTBFS (as I'm ignoring errors in tests, for now) (I know this report could have been triggered by parsing logs, so that's fine :) ), but it's indeed something to fix, hence I'm merging with the already existing but about it. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761727: [reportbug] Can't start reportbug
control: severity -1 normal control: tags -1 +moreinfo Original exception was: Traceback (most recent call last): File /usr/bin/reportbug, line 2209, in module main() File /usr/bin/reportbug, line 1056, in main if newui.initialize (): File /usr/lib/python2.7/dist-packages/reportbug/ui/gtk2_ui.py, line 1535, in initialize gtk.window_set_default_icon_from_file (DEBIAN_LOGO) glib.GError: Cant recognize image format «/usr/share/pixmaps/debian-logo.png» can you check if this file is corrupted for some reason? are you able to replicate the same problem with a different user on the same machine or on other machines? I tried and I cant replicate -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760434: [Pkg-amule-devel] Bug#760434: amule: unusable GUI
Also it would be nice if such problem would be caught before migration to testing but priority medium left little time to avoid larger impact... amule is not in testing at the moment, you have installed from sid. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760434: [Pkg-amule-devel] Bug#760434: amule: unusable GUI
I see it was removed from testing due to WX-3.0 transition... What a mess... :( indeed :( -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: [reportbug/master] uninstall GTK+ readline hook, this prevent a crash in reportbug; thanks to Eric Valette for the report and to Simon McVittie for the GTK+-side analysis and patch; Closes
tag 758619 pending tag 758619 pending thanks Date: Thu Sep 4 23:14:37 2014 +0100 Author: Sandro Tosi mo...@debian.org Commit ID: 0d118098881a15a92a089ed20ba3e2eb08cfc4b7 Commit URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=0d118098881a15a92a089ed20ba3e2eb08cfc4b7 Patch URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=0d118098881a15a92a089ed20ba3e2eb08cfc4b7 uninstall GTK+ readline hook, this prevent a crash in reportbug; thanks to Eric Valette for the report and to Simon McVittie for the GTK+-side analysis and patch; Closes: #758619 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760434: [Pkg-amule-devel] Bug#760434: amule crash, jam, cpu hog, memory hog after running some time
Hello, after running some minutes (might be almost immediate) amule crashed, jams, consumes cpu power and allocates more and more memory. (before its killed) this happened after upgrade to 2.3.1+git1a369e47-1. older version was 2.3.1-11 and it was not affected this bug. can you install amule-dbg and run amule thru gdb and when it crashes attach to this bug the output of bt / bt full / thread apply all bt gdb command? Thanks, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751241: [Pkg-amule-devel] Bug#751241: amule: Please update to use wxwidgets3.0
On Fri, Aug 29, 2014 at 5:04 AM, Olly Betts o...@survex.com wrote: On Wed, Jun 11, 2014 at 03:37:45PM +0200, Werner Mahr wrote: There are just no new features to do, that would need a new release and for now it's more a state of waiting. A new release could fix bugs even if there are no features to do (the BTS suggests there are a number of bugs). There's also updating it to work with newer releases of its dependencies (not just wxWidgets, though that is a current case in point). I'm trying a Git snapshot (from commit 1a369e47, currently HEAD) as just cherrypicking the commit that should fix compatibility with 3.0 is entangled with previous commits. dunno how long it will take and/or if it will be successful, but no amule in next stable will be a shame :) Regards, Sandro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758697: trying to overwrite shared '/usr/bin/policyeditor', which is different from other instances of package icedtea-netx:i386
Package: icedtea-netx Version: 1.5-2 Severity: grave Hello, got this error installing icedtea plugin for i386 (on an amd64 machine) apt-get install icedtea-netx:i386 Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: icedtea-netx:i386 The following NEW packages will be installed: icedtea-netx:i386 0 upgraded, 1 newly installed, 0 to remove and 86 not upgraded. 1 not fully installed or removed. Need to get 0 B/23.8 kB of archives. After this operation, 155 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 202583 files and directories currently installed.) Preparing to unpack .../icedtea-netx_1.5-2_i386.deb ... Unpacking icedtea-netx:i386 (1.5-2) ... dpkg: error processing archive /var/cache/apt/archives/icedtea-netx_1.5-2_i386.deb (--unpack): trying to overwrite shared '/usr/bin/policyeditor', which is different from other instances of package icedtea-netx:i386 Errors were encountered while processing: /var/cache/apt/archives/icedtea-netx_1.5-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Regards, Sandro -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/16 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.5-2 ii openjdk-6-jre6b32-1.13.4-1~deb7u1 ii openjdk-7-jre7u65-2.5.1-4 icedtea-netx recommends no packages. icedtea-netx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: [Reportbug-maint] reportbug is broken due to glib
control: reassign -1 libglib2.0-0 control: affects -1 reportbug Hello, thanks for the trace; I'm forwarding this info to the bug report and reassign it to glib. Regards, Sandro On Mon, Aug 18, 2014 at 4:13 PM, VALETTE Eric OLNC/OLPS eric2.vale...@orange.com wrote: gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0 GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html 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: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from python...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/python /usr/bin/reportbug -b --no-check-available libpulse0 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Eric Valette eric2.vale...@orange.com' as your from address. Getting status for libpulse0... Will send report to Debian (per lsb_release). Maintainer for libpulse0 is 'Pulseaudio maintenance team pkg-pulseaudio-de...@lists.alioth.debian.org'. Looking up dependencies of libpulse0... Getting changed configuration files... Briefly describe the problem (max. 100 characters allowed). This will be the bug email subject, so keep the summary as concise as possible, for example: fails to send email or does not start with -q option specified (enter Ctrl+c to exit reportbug without reporting a bug). Attempt to unlock mutex that was not locked = Program received signal SIGABRT, Aborted. 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x76f297e8 in __GI_abort () at abort.c:89 #2 0x72cdc85d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x719f4bbf in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #4 0x720a7d54 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #5 0x74148a99 in ?? () from /usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so #6 0x00448d04 in PyOS_Readline () #7 0x0044413c in ?? () #8 0x004c347d in PyEval_EvalFrameEx () #9 0x004c1d29 in PyEval_EvalCodeEx () #10 0x004c3963 in PyEval_EvalFrameEx () #11 0x004c1d29 in PyEval_EvalCodeEx () #12 0x004c3963 in PyEval_EvalFrameEx () #13 0x004c3c12 in PyEval_EvalFrameEx () #14 0x004c3c12 in PyEval_EvalFrameEx () #15 0x004c1d29 in PyEval_EvalCodeEx () #16 0x004fb43f in ?? () #17 0x004f0c72 in PyRun_FileExFlags () #18 0x004efdc4 in PyRun_SimpleFileExFlags () #19 0x00492398 in Py_Main () #20 0x76f14b45 in __libc_start_main (main=0x491e50 main, argc=5, argv=0x7fffe3f8, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe3e8) at libc-start.c:287 #21 0x00491d7d in _start () (gdb) -- eric ___ Reportbug-maint mailing list reportbug-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741380: hgview: segmentation fault
Package: hgview Version: 1.8.0-1 Severity: grave Hello, I've just installed hgview, run it and got: $ hgview Segmentation fault Attached is the gdb session of the crash. Regards, Sandro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hgview depends on: ii hgview-common 1.8.0-1 ii python 2.7.5-5 ii python-docutils 0.11-2 ii python-qscintilla2 2.7.2-1+b3 ii python-qt4 4.10.2-2 hgview recommends no packages. hgview suggests no packages. -- no debconf information hgview_sigsegv_gdb.txt.bz2 Description: BZip2 compressed data
Bug#740337: gnome-tweak-tool: AttributeError: 'gi.repository.Gtk' object has no attribute 'ListBox'
Package: gnome-tweak-tool Version: 3.10.1-1 Severity: grave Hello, I just installed gnome-tweak-tool and launching it got this error: $ gnome-tweak-tool WARNING : Shell not installed or running Traceback (most recent call last): File /usr/bin/gnome-tweak-tool, line 84, in module from gtweak.app import GnomeTweakTool File /usr/lib/python2.7/dist-packages/gtweak/app.py, line 25, in module from gtweak.tweakview import Window File /usr/lib/python2.7/dist-packages/gtweak/tweakview.py, line 26, in module from gtweak.widgets import Title File /usr/lib/python2.7/dist-packages/gtweak/widgets.py, line 207, in module class ListBoxTweakGroup(Gtk.ListBox, TweakGroup): File /usr/lib/python2.7/dist-packages/gi/module.py, line 313, in __getattr__ return getattr(self._introspection_module, name) File /usr/lib/python2.7/dist-packages/gi/module.py, line 134, in __getattr__ self.__name__, name)) AttributeError: 'gi.repository.Gtk' object has no attribute 'ListBox' with this versin of python-gi $ COLUMNS=80 dpkg -l python-gi | tail -n1 ii python-gi 3.10.2-1 amd64Python 2.x bindings for gobject-i but also updating to the latest version in sid: $ COLUMNS=80 dpkg -l python-gi | tail -n1 ii python-gi 3.10.2-2+b1 amd64Python 2.x bindings for gobject-i Regards, Sandro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-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 Versions of packages gnome-tweak-tool depends on: ii gir1.2-gnomedesktop-3.03.8.4-2 ii gir1.2-gtk-3.0 3.8.6-1 ii gnome-shell-common 3.8.4-5 ii gsettings-desktop-schemas 3.8.2-2 ii python 2.7.5-5 ii python-gi 3.10.2-1 gnome-tweak-tool recommends no packages. gnome-tweak-tool suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740337: gnome-tweak-tool: AttributeError: 'gi.repository.Gtk' object has no attribute 'ListBox'
On Fri, Feb 28, 2014 at 12:19 PM, Emilio Pozuelo Monfort po...@debian.org wrote: On 28/02/14 11:17, Sandro Tosi wrote: ii gir1.2-gtk-3.0 3.8.6-1 You need 3.10 (which is in testing already). yup, with that version it works We should have a versioned dependency there. yes indeed, a versioned depends is in order (which currently missing :) ). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739487: python-mysql.connector: Trying to overwrite a file that belong to mysql-utilities
control: reassign -1 mysql-utilities Hello, Yes it is known, and we had agreed with Dmitry that he'll update mysql-utilities to prevent that after I uploaded python-mysql.connector (which I did) so I'll reassign this bug to that package. Regards, Sandro On Wed, Feb 19, 2014 at 10:18 AM, Laurent Bigonville bi...@debian.org wrote: Package: python-mysql.connector Version: 1.1.5-1 Severity: serious Hi, python-mysql.connector is trying to override a file that currently belong to 1.1.5-1. Unpacking python-mysql.connector (1.1.5-1) over (0.3.2-1) ... dpkg: error processing archive /var/cache/apt/archives/python-mysql.connector_1.1.5-1_all.deb (--unpack): tentative de remplacement de « /usr/share/pyshared/mysql/__init__.py », qui appartient aussi au paquet mysql-utilities 1.3.5-1 Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-mysql.connector depends on: ii python 2.7.5-5 ii python-support 1.0.15 python-mysql.connector recommends no packages. python-mysql.connector suggests no packages. -- no debconf information -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725435: trying to overwrite shared '/etc/sane.d/gt68xx.conf', which is different from other instances of package libsane:amd64
Package: libsane Version: 1.0.23-3 Severity: grave Hello, when installing gnome, libsane fails to be installed due to: Unpacking libsane:amd64 (from .../libsane_1.0.23-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libsane_1.0.23-3_amd64.deb (--unpack): trying to overwrite shared '/etc/sane.d/gt68xx.conf', which is different from other instances of package libsane:amd64 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Regards, Sandro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725436: trying to overwrite shared '/etc/sane.d/dll.d/libsane-extras', which is different from other instances of package libsane-extras:amd64
Package: libsane-extras Version: 1.0.22.3 Severity: grave Hello, when installing gnome, libsane-extras fails to install due to: Unpacking libsane-extras:amd64 (from .../libsane-extras_1.0.22.3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libsane-extras_1.0.22.3_amd64.deb (--unpack): trying to overwrite shared '/etc/sane.d/dll.d/libsane-extras', which is different from other instances of package libsane-extras:amd64 Regards, Sandro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719065: [Python-modules-team] Bug#719065: NMU, fix for #719065 and #719384, debdiff, DELAYED/2
Hello, please cancel the upload, I'll deal with it soon. Cheers, Sandro On Sun, Sep 29, 2013 at 8:29 PM, Anton Gladky gladky.an...@gmail.com wrote: tags 719065 +pending +patch tags 719384 +pending +patch thanks Dear maintainers, it seems, upstream has fixed both #719065 [1] and #719384 [2] bugs. I have prepared NMU, based on those commits (see attachment for debdiff) and uploaded it in DELAYED/2 queue, because #719384 causes FTBFS's on several packages. If you are not agree with it, feel free to cancel the upload or delay it longer. Best regards, Anton [1] https://github.com/matplotlib/matplotlib/commit/ffb37468644b0dae66b7ceb8e84f1079127c0100 [2] https://github.com/mdboom/matplotlib/commit/1e8d592ed0439ac6fe8fc08d5efe522799acf4fe ___ Python-modules-team mailing list python-modules-t...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719065: [Python-modules-team] Bug#719065: NMU, fix for #719065 and #719384, debdiff, DELAYED/2
Ok, no worries :) please, just post the nmudiff to the relevant bugs (as per NMU policy). Cheers, Sandro On Sun, Sep 29, 2013 at 8:51 PM, Anton Gladky gladky.an...@gmail.com wrote: Hi Sandro, I am really sorry, it seems, dput ignored my delayed-request: dput ftp-master matplotlib_1.3.0-1.1_amd64.changes --delayed 2 and it is now accepted in unstable. I hope, it will not demotivates you... Best regards, Anton 2013/9/29 Sandro Tosi mo...@debian.org: Hello, please cancel the upload, I'll deal with it soon. Cheers, Sandro -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712416: The Twitter REST API v1 is no longer active. Please migrate to API v1.1
Package: python-twitter Version: 0.8.5-1 Severity: grave Hello, as the subject says the REST API version python-twitter uses is no longer supported by Twitter; a new upstream release is available to support v1.1 - could you please package it? If you can, since it's maintained under the DPMT umbrella, I can push the updated version for you. Regards, Sandro -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-twitter depends on: ii python2.7.3-5 ii python-oauth2 1.5.211-2 ii python-pkg-resources 0.6.24-1 python-twitter recommends no packages. Versions of packages python-twitter suggests: ii chromium [www-browser] 27.0.1453.110-1 ii iceweasel [www-browser] 15.0.1-1 ii w3m [www-browser]0.5.3-8 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698809: Debian Reportbug simply quits in 80% of all cases
Control: severity -1 normal Control: tags -1 +moreinfo Hello, On Wed, Jan 23, 2013 at 10:48 PM, Rolf Heinrichs rolf.o1.heinri...@gmx.net wrote: Package: Reportbug Version: Squeeze 6.06 amd64, Gnome did you forge this version yourself? please don't and please report the exact version of reportbug you're using. Trying to use Reportbug with user rights to report a problem: usually after trying to selected a package Reportbug simply quits. No useful info in logs. Open a terminal, and run 'reportbug' from it and report the eventual error message/traceback/whatever is displayed on the terminal upon error. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650454: checkgmail: keeps popping up login window but fails to log in
On Mon, Aug 20, 2012 at 3:17 AM, Jonathan Nieder jrnie...@gmail.com wrote: Sandro Tosi wrote: If you want to upload it to stable, feel free to. Thanks. pu bug filed. awesome, thanks! I'm not a DD, so I can't upload directly. If the release team gives the ok, would you like to sponsor the upload? (If not, that's fine and I can look for another sponsor.) I'd prefer if you could look for another sponsor. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650454: checkgmail: keeps popping up login window but fails to log in
On Sun, Aug 19, 2012 at 8:51 PM, Jonathan Nieder jrnie...@gmail.com wrote: Hi again, In January, Jonathan Nieder wrote: Sandro Tosi wrote: * debian/patches/60_bts650454_send_galx_as_cookie.patch - fix auth problem with GMail, by passing GALX in the cookie; thanks to Johan Sandblom for the report; Closes: #650454 Yep, I can reproduce this. I tried applying this patch in squeeze and it seemed to behave as advertised. Maybe the result can save you some time. Ping. Is there some reason not to apply this patch? If you just haven't had time to look it over, that's fine, but please do let me know if you'd like an NMU or if you'd prefer more time to review it. Thanks, Jonathan who would like squeeze to be less buggy in general but could easily be missing details since he doesn't use this particular package If you want to upload it to stable, feel free to. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683680: [Pkg-amule-devel] Bug#683680: amule don't start
Hello Michael, On Fri, Aug 3, 2012 at 8:36 PM, Michael Stapelberg stapelb...@debian.org wrote: tags 683680 +patch thanks Hi, On Thu, 02 Aug 2012 20:48:51 +0200 florian fgr...@hotmail.com wrote: amule launch if delete statistics.dat. file was 0 byte Thanks for the report. This is tracked upstream at http://www.amule.org/abugs/view.php?id=1704 and fixed in revision 10754. I have backported that fix to 2.3.1 (see the attached file).ù Thanks a lot for your work: i'll upload the fix in unstable tomorrow. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677419: fdupes: When using -L and traversing filesystems, removes files
On Wed, Jun 20, 2012 at 5:56 PM, Touko Korpela touko.korp...@iki.fi wrote: Package: fdupes Followup-For: Bug #677419 It's wrong to remove this useful option, removing causes FTBFS #678254 So -L should be fixed to fail gracefully instead This is the quickest thing we could do - if we'll get a working functionalities again, we'll reintroduce, but we're too close to the freeze to leave that bug opened. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678036: [Python-modules-team] Bug#678036: 1.7~rc1 causes FTBFS in nipype 0.5.3-1
Hello,
can you please provide a minimal test case I can use as example to
forward upstream?
thanks,
Sandro
On Mon, Jun 18, 2012 at 9:02 PM, Yaroslav Halchenko
deb...@onerussian.com wrote:
Package: python-networkx
Version: 1.7~rc1-1
Severity: serious
I was about to upload a fix for #664944 but the build failed due to error
while running unittests:
==
ERROR: Failure: ValueError (need more than 0 values to unpack)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/nose/loader.py, line 231, in generate
for test in g():
File
/tmp/buildd/nipype-0.5.3/debian/python-nipype/usr/lib/python2.7/site-packages/nipype/pipeline/plugins/tests/test_callback.py,
line 76, in test_callback_multiproc_normal
wf.run(plugin='MultiProc', plugin_args={'status_callback': so.callback})
File
/tmp/buildd/nipype-0.5.3/debian/python-nipype/usr/lib/python2.7/site-packages/nipype/pipeline/engine.py,
line 519, in run
runner.run(execgraph, updatehash=updatehash, config=self.config)
File
/tmp/buildd/nipype-0.5.3/debian/python-nipype/usr/lib/python2.7/site-packages/nipype/pipeline/plugins/base.py,
line 140, in run
self._generate_dependency_list(graph)
File
/tmp/buildd/nipype-0.5.3/debian/python-nipype/usr/lib/python2.7/site-packages/nipype/pipeline/plugins/base.py,
line 329, in _generate_dependency_list
self.depidx = nx.to_scipy_sparse_matrix(graph)
File /usr/lib/pymodules/python2.7/networkx/convert.py, line 783, in
to_scipy_sparse_matrix
for u,v,d in G.edges(nodelist, data=True)
ValueError: need more than 0 values to unpack
begin captured logging
workflow: INFO: ['check', 'execution', 'logging']
workflow: INFO: Running in parallel.
- end captured logging -
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677026: [Python-modules-team] Bug#677026: python-matplotlib: pylab crashes with Illegal instruction error
severity 677026 minor thanks Hello Anton, On Mon, Jun 11, 2012 at 11:01 AM, Anton Gladky gladky.an...@gmail.com wrote: In [1]: import pylab In [2]: pylab.figure() it works here and in a clean amd64 chroot: import pylab pylab.figure() matplotlib.figure.Figure object at 0x2e54c10 In [1]: import pylab In [2]: pylab.figure() Out[2]: matplotlib.figure.Figure at 0x2673690 it's probably something broken on your system. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673790: [Python-modules-team] Bug#673790: Broken API on new version
severity 673790 normal thanks Hello, On Mon, May 21, 2012 at 3:20 PM, Florent Fourcot florent.four...@resel.fr wrote: The new version of python-prettytable use an other API than the 0.5. Extract of the changelog: * Replaced all setter methods with managed attributes The new API breaks this is somehow possible for 0.* modules/libraries. The example script is broken too: $ python /usr/share/doc/python-prettytable/examples/prettytable-example.py Traceback (most recent call last): File /usr/share/doc/python-prettytable/examples/prettytable-example.py, line 20, in module main() File /usr/share/doc/python-prettytable/examples/prettytable-example.py, line 9, in main x.set_field_align(City name, l) # Left align city names File /usr/lib/pymodules/python2.7/prettytable.py, line 163, in __getattr__ raise AttributeError(name) AttributeError: set_field_align this has been fixed in svn Please consider to warn users about changes, or to provide compatibility with old versions. Upstream doesn't provide release note to help the upgrade. I was working with upstream to release also documentation along with the code. it should have been done with 0.6 release but there were some problems. Next will have upstream doc with it, I'll close this bug at that time. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670962: [Pkg-amule-devel] Bug#670962: amule: FTBFS (cannot convert 'UpnpString* {aka s_UpnpString*}' to 'const char*')
Hi Cyril, On Thu, May 3, 2012 at 3:52 AM, Cyril Brulebois k...@debian.org wrote: Anyway, the following patch allows amule to build, but I performed no run-time test. Thanks for the patch! I've just forwarded upstream (which is currently tracking it at http://forum.amule.org/index.php?topic=19738). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666469: [Reportbug-maint] Bug#666469: reportbug: reports bug assigned to the wrong package (multi-arch problem?)
severity 666469 important thanks On Sat, Mar 31, 2012 at 02:49, Vincent Lefevre vinc...@vinc17.net wrote: Package: reportbug Version: 6.3.1 Severity: grave Justification: renders package unusable (well, not completely, but this is definitely a RC bug if you don't want a mess in the bug reports) I'm not convinced this is RC (on reportbug) because it's not effecting all the users: downgraded. I wanted to report a bug against libcairo2, but I got: $ reportbug libcairo2 [...] Getting status for libcairo2... Verifying package integrity... There may be a problem with your installation of libcairo2; the following problems were detected by debsums: debsums: package libcairo2 is not installed this is debsums replying, so at least you should have filed the bug against that: reportbug here is just a interface to it. Do you still want to file a report [y|N|q|?]? So, I suspected that I should have used the complete package name: $ reportbug libcairo2:amd64 [...] then everything seemed to be OK, as usual. The bug report was sent: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666468 However the bug was assigned to libcairo2:amd64, which doesn't exist for the Debian BTS (unknown maintainer, unknown source). was it defined somewhere how bugs for m-a packages should be filed? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666637: [Python-modules-team] Bug#666637: pyopenssl: FTBFS: cp: cannot stat `doc/pyOpenSSL.ps': No such file or directory
reassign 37 texlive-binaries retitle 37 mktexpk: Permission denied on buildd thanks Thanks for your report! On Sat, Mar 31, 2012 at 21:28, Lucas Nussbaum lu...@lucas-nussbaum.net wrote: Source: pyopenssl Version: 0.13-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. ... cp: cannot stat `doc/pyOpenSSL.ps': No such file or directory The problem is that: /usr/bin/make -C doc all make[1]: Entering directory `/«PKGBUILDDIR»/doc' python tools/mkhowto --a4 --ps pyOpenSSL.tex *** Session transcript and error messages are in pyOpenSSL.how. The relevant lines from the transcript are: +++ dvips -N0 -o pyOpenSSL.ps pyOpenSSL This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com) ' TeX output 2012.03.30:2143' - pyOpenSSL.ps kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 ecss2488 mkdir: cannot create directory `././sbuild-nonexistent': Permission denied mkdir: cannot create directory `././var/cache/fonts/pk': Permission denied mktexpk: /usr/share/texlive/texmf/web2c/mktexdir /var/cache/fonts/pk/ljfour/jknappen/ec failed. kpathsea: Appending font creation commands to missfont.log. dvips: Font ecss2488 not found; using cmr10 /usr/share/texlive/texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk dvips: Design size mismatch in font ecss2488 dvips: Checksum mismatch in font ecss2488 and it keeps going and going until it crashes, and no doc is generated. It's probably related to the recent updated of texlive-binaries to a new upstream release. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665362: reportbug: Crashes with python2.7
reassign 665362 python2.7 forcemerge 665346 665362 thanks On Fri, Mar 23, 2012 at 14:28, Fabian Greffrath fab...@greffrath.com wrote: currently reportbug crashes on my system when using python2.7 with the attached the problem is in python2.7, which was uploaded recently and it's bugged (I know, testing packages is difficult). Reassigning to it. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663403: [Python-modules-team] Bug#663403: FTBFS: cannot find -lgeos
On Sat, Mar 17, 2012 at 00:43, Francesco P. Lovergine fran...@debian.org wrote: This is a patch for the problem of re-linking the c++ geos lib: Thanks for the patch, preparing the upload right now. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647695: spyder: segfaults right after start
Package: spyder Version: 2.1.1-1 Severity: grave Hello, I've just installed spyder (new installation, no previous version) and then I tried to start it and got: # spyder loaded the Generic plugin Segmentation fault If there's something I can do to help you debug this problem, just ask. Cheers, Sandro -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.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/bash Versions of packages spyder depends on: ii python2.7.2-9 ii python-spyderlib 2.1.1-1 spyder recommends no packages. spyder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647695: RE : RE : Bug#647695: spyder: segfaults right after start
2011/11/5 PICCA Frédéric-Emmanuel frederic-emmanuel.pi...@synchrotron-soleil.fr: Hello, can you look at bug 618836 [1] It seems that it came back... this kind of recurrent bug is a pain. Can you give me your python-qt4 version It would be nice also to add it to the bug-control file ;) usually this is a problem with python-qt4, python-sip [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618836 Ok, upgrading python-qt4, libqtwebkit4 and a bunch of qt4 libs spyder it's now starting. Anyhow, given it's a recurring problem, and it seems spyder needs QT4 stuff to work, you might need to tune dependencies of spyder package. Leaving this bug opened to let remind of doing that. Cheers thanks for the help, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647695: RE : RE : RE : Bug#647695: spyder: segfaults right after start
2011/11/5 PICCA Frédéric-Emmanuel frederic-emmanuel.pi...@synchrotron-soleil.fr: Ok, upgrading python-qt4, libqtwebkit4 and a bunch of qt4 libs spyder it's now starting. Anyhow, given it's a recurring problem, and it seems spyder needs QT4 stuff to work, you might need to tune yes everythings is in tune :) My problem is that I do not know which version of python-qt4 is ok ? with which combination of libqt4... it seems that the python-qt4 maintainer started a thread [1] about this python-qt4, python-sip compatibility etc.. I am not even convince that this is the same issue. infact I don't think it is: I first upgraded the QT4 stack, and still segfault, then python-qt4, still segfault, only after upgradng also libqtwebkit4 the segfault gone away. Is it a API breakage in the qt4 library which cause this segfault ? I don't know, maybe ask the QT4 maint? dependencies of spyder package. Leaving this bug opened to let remind of doing that. ok, do you think that I can downgrad it to unblock the testing migration ? Well, you'd have to check if the version in testing of qt4/python-qt/libwebkitqt don't make spyder segfault. Else, I think it's better not to transit to testing until it's working correctly out-of-the-box (which currently doesn't). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647695: spyder: segfaults right after start
2011/11/5 PICCA Frédéric-Emmanuel frederic-emmanuel.pi...@synchrotron-soleil.fr: infact I don't think it is: I first upgraded the QT4 stack, and still segfault, then python-qt4, still segfault, only after upgradng also libqtwebkit4 the segfault gone away. do you have the version before and after ? here's the list of the package upgrades (some may be unrelated to the problem at hand): libqt4-dbus (4:4.7.3-7 - 4:4.7.3-8) libqt4-declarative (4:4.7.3-7 - 4:4.7.3-8) libqt4-designer (4:4.7.3-7 - 4:4.7.3-8) libqt4-dev (4:4.7.3-7 - 4:4.7.3-8) libqt4-help (4:4.7.3-7 - 4:4.7.3-8) libqt4-network (4:4.7.3-7 - 4:4.7.3-8) libqt4-opengl (4:4.7.3-7 - 4:4.7.3-8) libqt4-qt3support (4:4.7.3-7 - 4:4.7.3-8) libqt4-script (4:4.7.3-7 - 4:4.7.3-8) libqt4-scripttools (4:4.7.3-7 - 4:4.7.3-8) libqt4-sql (4:4.7.3-7 - 4:4.7.3-8) libqt4-sql-mysql (4:4.7.3-7 - 4:4.7.3-8) libqt4-sql-sqlite (4:4.7.3-7 - 4:4.7.3-8) libqt4-svg (4:4.7.3-7 - 4:4.7.3-8) libqt4-test (4:4.7.3-7 - 4:4.7.3-8) libqt4-xml (4:4.7.3-7 - 4:4.7.3-8) libqt4-xmlpatterns (4:4.7.3-7 - 4:4.7.3-8) libqtcore4 (4:4.7.3-7 - 4:4.7.3-8) libqtgui4 (4:4.7.3-7 - 4:4.7.3-8) libqtwebkit4 (2.1.0~2011week09-3 - 2.1.0~2011week13-2) pyflakes (0.4.0-1 - 0.5.0-1) pyqt4-dev-tools (4.8.3-4 - 4.8.6-2) python-qscintilla2 (2.5.1-1 - 2.5.1-1+b1) python-qt4 (4.8.3-4 - 4.8.6-2) python-qt4-gl (4.8.3-4 - 4.8.6-2) qt4-demos (4:4.7.3-7 - 4:4.7.3-8) qt4-designer (4:4.7.3-7 - 4:4.7.3-8) qt4-dev-tools (4:4.7.3-7 - 4:4.7.3-8) qt4-linguist-tools (4:4.7.3-7 - 4:4.7.3-8) qt4-qmake (4:4.7.3-7 - 4:4.7.3-8) that way I should prevent spyder to be installed with the wrong libqtwebkit4 how? I don't know, maybe ask the QT4 maint? I will look for the libqtwebkit4 bugs for now Well, you'd have to check if the version in testing of qt4/python-qt/libwebkitqt don't make spyder segfault. Else, I think it's better not to transit to testing until it's working correctly out-of-the-box (which currently doesn't). I un-install all the qt4 library from my unstable box then switch to testing repository and re-install spyder 2.0.12 from testing. guest what it works out of the box. then I upgraded to spyder 2.1.1 and it was also ok. so it seems that spyder segfault for a faulty combination of python-qt4 / libqtwebkit4. I doesn not seems to me that this is a spyder bug. well, it's indeed a bug in spyder that it doesn't declare the correct relationship with other pkgs (it doesn't even say it needs libwebkit...) Maybe a Break should be added to libqtwebkit4 to avoid installation of the faulty combination I think better a conflict on spyder side. I will forward this bug to python-qt4 if you are ok with my analyse. while there might be a bug on the qt4 side, there's one for sure on the spyder side too, so if you want file another one, but this one is still valid for spyder. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645534: [reportbug] reportbug always crashes
severity 645534 normal tags 645534 +moreinfo -patch -security thanks On Fri, Oct 14, 2011 at 18:17, Bruno Maximo e Melo brunoso...@gmail.com wrote: Package: reportbug Version: 4.12 where did you get this version? stable has 4.12.6, so you can probably upgrade your version. Severity: critical really? don't over-inflate severity if you don't know what they mean. Tags: patch security where is the patch? where is the security issue? don't use tags if you don't know what they mean. X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org --- Please enter the report below this line. --- Reportbug always crashes, i can't find bugs about a software because it stops, always stops and i need to kill it. Opening from terminal, terminal doesn't show me anything error :s is a grave bug, can you fix it please? Sure, if you give use *detailed* information, which you didn't up to now. Either you provide some specific information we can use to decipher your problem or we can't do anything but discard this report. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644965: [Reportbug-maint] Bug#644965: reportbug -Q -N bug-ID, subsequent choice o - stacktrace
severity 644965 normal forcemerge 642939 644965 thanks On Tue, Oct 11, 2011 at 11:32, debbug l...@think-future.com wrote: Package: reportbug Version: 6.2.1 Severity: serious really? if you don't know what severity is for, don't over-inflate it. Description: - Using query mode -Q w/ -N 1234, viewing report, then selecting o in the menu crashes reportbug. Trace: What do you want to do now? [N|x|o|r|b|e|q|?]? ? N - (default) Show next message (followup). x - Provide extra information. o - Show other bug reports (return to bug listing). r - Redisplay this message. b - Launch web browser to read full log. e - Launch e-mail client to read full log. q - I'm bored; quit please. ? - Display this help. What do you want to do now? [N|x|o|r|b|e|q|?]? o Traceback (most recent call last): File /usr/bin/reportbug, line 2186, in module main() File /usr/bin/reportbug, line 1073, in main return iface.user_interface() File /usr/bin/reportbug, line 1354, in user_interface package = exinfo.package or exinfo.source AttributeError: 'NoneType' object has no attribute 'package' also, already reported: thanks for checking. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640752: reportbug: submitting email completely broken
severity 640752 inportant forcemerge 640434 640752 thanks Hello, On Wed, Sep 7, 2011 at 02:35, Norbert Preining prein...@logic.at wrote: Package: reportbug Version: 6.2 Severity: grave Justification: renders package unusable sorry but I disagree, only the follow-up functionality is broken - downgrading. Also, the very same bug was already reported - forcemerge. Note the wonderful Debian Bug Tracking System fixed_versions which is NOT a valid email adress on my system!!! You know, people makes mistakes - make irony on it won't make them be fixed any faster. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625423: sitecopy: ftbfs with gcc-4.6 -Werror
On Sun, Aug 14, 2011 at 01:46, jida...@jidanni.org wrote: ST == Sandro Tosi mo...@debian.org writes: ST It would be nice if you can give it a look, since soon sitecopy will ST not be buildable anymore. Hey, some of us still use sitecopy here on Debian. that's what I maintain it in Debian. What will happen if upstream is unresponsive? I'll worry when (and *if*) it will happen. What should be my contingency plan? Thanks. you can provide us a patch, or find someone that wants to write one. That would speed up upstream and debian fixing. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625423: sitecopy: ftbfs with gcc-4.6 -Werror
forwarded 625423 sitec...@lists.manyfish.co.uk thanks Hello, In Debian we have received this bug report: On Tue, May 3, 2011 at 12:34, Matthias Klose d...@debian.org wrote: This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures, but this patch will be reverted with the GCC 4.6.1 release, and the severity of the report will be raised. The full build log can be found at: http://people.debian.org/~doko/tmp/werror/sitecopy_1:0.16.6-3_lsid64.buildlog The last lines of the build log are at the end of this report. It would be nice if you can give it a look, since soon sitecopy will not be buildable anymore. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634434: [Python-modules-team] Bug#634434: python-scipy: FTBFS: (.text+0x20): undefined reference to `main'
On Tue, Jul 19, 2011 at 00:05, Lucas Nussbaum lu...@lucas-nussbaum.net wrote: Source: python-scipy Version: 0.9.0+dfsg1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc: scipy/fftpack/src/zfftnd.c /usr/bin/gfortran -Wall build/temp.linux-x86_64-2.7-pydebug/build/src.linux-x86_64-2.7/scipy/fftpack/_fftpackmodule.o build/temp.linux-x86_64-2.7-pydebug/scipy/fftpack/src/zfft.o build/temp.linux-x86_64-2.7-pydebug/scipy/fftpack/src/drfft.o build/temp.linux-x86_64-2.7-pydebug/scipy/fftpack/src/zrfft.o build/temp.linux-x86_64-2.7-pydebug/scipy/fftpack/src/zfftnd.o build/temp.linux-x86_64-2.7-pydebug/build/src.linux-x86_64-2.7/scipy/fftpack/src/dct.o build/temp.linux-x86_64-2.7-pydebug/build/src.linux-x86_64-2.7/fortranobject.o -Lbuild/temp.linux-x86_64-2.7-pydebug -ldfftpack -lfftpack -lgfortran -o build/lib.linux-x86_64-2.7-pydebug/scipy/fftpack/_fftpack_d.so I think this is related to the situation I described in #634012 - could you please verify if with the new debhelper, the package builds fine? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634012: [Python-modules-team] Bug#634012: FTBFS: undefined references
On Thu, Aug 4, 2011 at 12:57, Torquil Macdonald Sørensen torq...@gmail.com wrote: Package: python-numpy Version: 1:1.5.1-2+b1 Followup-For: Bug #634012 I had a similar problem trying to compile numpy 1.6.1. It seems to build when using gfortran-4.5 instead of gfortran-4.6. I had to edit debian/control by changing the build-depends so that dpkg-buildpackage would allow this. unacceptable as a solution to make the package build. Caveat: I haven't done any testing to check that my resulting build is up to scratch, or lacking in some way due to this change. I have not studied the build log either, for errors. So perhaps gfortran-4.6 causes this problem? probably, as it seems scipy is affected by a similar bug. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632079: reportbug crash (segfault)
severity 632079 important forcemerge 620225 632079 thanks On Wed, Jun 29, 2011 at 15:36, ludovic mercier ludovic.merc...@gmail.com wrote: Package: reportbug Version: 4.12.6 Severity: critical don't use exterme severity if you don't know what they mean. It was also already reported several times, thanks for checking. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626800: [Jppy-devel] Bug#626421: Bug#626421: jppy: FTBFS: Checking for PyErr_Clear() in C library libpython2.7... no
On Wed, Jun 15, 2011 at 09:23, nick-deb...@nickpiper.co.uk wrote: Hi Sandro, Sandro Tosi wrote: is there any update on this issue (and on 626800 too) ? do you need sponsoring? Please note we need a quick fix for them, since this package is blocking the python transition. Both of these are fixed in the git repository at http://anonscm.debian.org/gitweb/?p=jppy/jppy.git . but require * 0.0.59 tagging (I can do that once we find someone for step two) * Debian release and upload (we use git-buildpackage) Are you able to help with the second part? sure, just prepare the code to be released (changelog entries, new tags so on) and ping me when done. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626421: [Jppy-devel] Bug#626421: jppy: FTBFS: Checking for PyErr_Clear() in C library libpython2.7... no
Hello Nick, is there any update on this issue (and on 626800 too) ? do you need sponsoring? Please note we need a quick fix for them, since this package is blocking the python transition. Thanks for your work and attention, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625135: necpp: diff for NMU version 1.5.0+cvs20101003-2.1
tags 625135 + patch
thanks
Dear maintainer,
I've prepared an NMU for necpp (versioned as 1.5.0+cvs20101003-2.1). The diff
is attached to this message.
Regards.
diff -u necpp-1.5.0+cvs20101003/Python/PyNEC/setup.py necpp-1.5.0+cvs20101003/Python/PyNEC/setup.py
--- necpp-1.5.0+cvs20101003/Python/PyNEC/setup.py
+++ necpp-1.5.0+cvs20101003/Python/PyNEC/setup.py
@@ -88,7 +88,8 @@
api_path = os.path.join(sys.prefix, 'include','numarray')
else :
# api_path = os.path.join(sys.prefix, 'include', 'python'+python_version, 'numarray')
- api_path = os.path.join(sys.prefix, 'share','pyshared','numpy','numarray','numpy')
+# api_path = os.path.join(sys.prefix, 'share','pyshared','numpy','numarray','numpy')
+ api_path = os.path.join(sys.prefix, 'share','pyshared','numpy','numarray','include','numpy')
test_api_path(api_path)
return api_path
except:
diff -u necpp-1.5.0+cvs20101003/debian/control necpp-1.5.0+cvs20101003/debian/control
--- necpp-1.5.0+cvs20101003/debian/control
+++ necpp-1.5.0+cvs20101003/debian/control
@@ -32,7 +32,7 @@
Package: python-necpp
Section: python
Architecture: any
-Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
+Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}, python-numpy
Provides: ${python:Provides}
XB-Python-Version: ${python:Versions}
Description: Python module for using NEC2++
diff -u necpp-1.5.0+cvs20101003/debian/changelog necpp-1.5.0+cvs20101003/debian/changelog
--- necpp-1.5.0+cvs20101003/debian/changelog
+++ necpp-1.5.0+cvs20101003/debian/changelog
@@ -1,3 +1,14 @@
+necpp (1.5.0+cvs20101003-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Python/PyNEC/setup.py
+- fix a FTBFS with python2.7 updating location of libnumarray.h; patches
+ from ubuntu; Closes: #625135
+ * debian/control
+- added python-numpy to Depends of python-necpp
+
+ -- Sandro Tosi mo...@debian.org Sun, 05 Jun 2011 12:51:28 +0200
+
necpp (1.5.0+cvs20101003-2) unstable; urgency=low
[ Emmanuel QUEMENER ]
Bug#624194: Re. sssd: Dangling dependency on libldb0
retitle 624194 sssd: new upstream release thanks The FTBFS and the libldb0/1 dependency has been fixed in the 1.2.1-4.2 upload, so this bug report is only valid for the request of the new upstream release, retitling it accordingly. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618159: sssd: diff for NMU version 1.2.1-4.2
tags 618159 + patch thanks Dear maintainer, I've prepared an NMU for sssd (versioned as 1.2.1-4.2). The diff is attached to this message. Regards. diff -u sssd-1.2.1/debian/sssd.install sssd-1.2.1/debian/sssd.install --- sssd-1.2.1/debian/sssd.install +++ sssd-1.2.1/debian/sssd.install @@ -1,6 +1,6 @@ usr/lib/sssd/* usr/lib/lib*.so.* -usr/lib/ldb/memberof.so +usr/lib/ldb/modules/ldb/memberof.so usr/lib/krb5/plugins/libkrb5/* usr/share/locale/*/LC_MESSAGES/* usr/sbin/sssd diff -u sssd-1.2.1/debian/changelog sssd-1.2.1/debian/changelog --- sssd-1.2.1/debian/changelog +++ sssd-1.2.1/debian/changelog @@ -1,3 +1,11 @@ +sssd (1.2.1-4.2) unstable; urgency=low + + * Non-maintainer upload. + * debian/sssd.install +- updated location for ldb modules; Closes: #618159 + + -- Sandro Tosi mo...@debian.org Fri, 03 Jun 2011 23:53:59 +0200 + sssd (1.2.1-4.1) unstable; urgency=medium * Non-maintainer upload by the Security Team
Bug#628860: ethos: diff for NMU version 0.2.2-1.2
tags 628860 + patch thanks Dear maintainer, I've prepared an NMU for ethos (versioned as 0.2.2-1.2). The diff is attached to this message. Regards. diff -u ethos-0.2.2/debian/changelog ethos-0.2.2/debian/changelog --- ethos-0.2.2/debian/changelog +++ ethos-0.2.2/debian/changelog @@ -1,3 +1,11 @@ +ethos (0.2.2-1.2) unstable; urgency=low + + * Non-maintainer upload. + * debian/patches/02-pkg-config-for-vala-0.10.patch, debian/control +- transition from libvala to libvala-1.0, patch from ubuntu; Closes: #628860 + + -- Sandro Tosi mo...@debian.org Fri, 03 Jun 2011 22:49:55 +0200 + ethos (0.2.2-1.1) unstable; urgency=low * Non-maintainer upload diff -u ethos-0.2.2/debian/control ethos-0.2.2/debian/control --- ethos-0.2.2/debian/control +++ ethos-0.2.2/debian/control @@ -5,12 +5,12 @@ Build-Depends: debhelper (= 7), cdbs (= 0.4.49), quilt, - valac, + valac-0.10, gnome-pkg-tools (= 0.11), pkg-config (= 0.14), libglib2.0-dev (= 2.16.0), libgtk2.0-dev (= 2.10.0), - libvala-dev, + libvala-0.10-dev, gtk-doc-tools (= 1.9), python-dev (= 2.2), python-gtk2-dev, diff -u ethos-0.2.2/debian/patches/series ethos-0.2.2/debian/patches/series --- ethos-0.2.2/debian/patches/series +++ ethos-0.2.2/debian/patches/series @@ -1,0 +2 @@ +02-pkg-config-for-vala-0.10.patch only in patch2: unchanged: --- ethos-0.2.2.orig/debian/patches/02-pkg-config-for-vala-0.10.patch +++ ethos-0.2.2/debian/patches/02-pkg-config-for-vala-0.10.patch @@ -0,0 +1,14 @@ +--- a/configure.ac b/configure.ac +@@ -81,9 +81,9 @@ + + dnl = Enable Vala == + enable_vala=no +-PKG_CHECK_MODULES(VALA, vala-1.0, enable_vala=yes, enable_vala=no) ++PKG_CHECK_MODULES(VALA, vala-0.10, enable_vala=yes, enable_vala=no) + if test x$enable_vala = xyes; then +- VAPI_DIR=`pkg-config --variable=vapidir vala-1.0` ++ VAPI_DIR=`pkg-config --variable=vapidir vala-0.10` + else + VAPI_DIR= + fi
Bug#626199: bzr-hg: diff for NMU version 0.2.0~bzr409-1.1
tags 626199 + patch thanks Dear maintainer, I've prepared an NMU for bzr-hg (versioned as 0.2.0~bzr409-1.1). The diff is attached to this message. Regards. diff -Nru bzr-hg-0.2.0~bzr409/debian/changelog bzr-hg-0.2.0~bzr409/debian/changelog --- bzr-hg-0.2.0~bzr409/debian/changelog 2011-03-15 23:45:19.0 +0100 +++ bzr-hg-0.2.0~bzr409/debian/changelog 2011-06-02 17:30:00.0 +0200 @@ -1,3 +1,12 @@ +bzr-hg (0.2.0~bzr409-1.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/control +- added python-bzrlib.tests to b-d-i, needed to run tests, and fix a FTBFS; + Closes: #626199 + + -- Sandro Tosi mo...@debian.org Thu, 02 Jun 2011 17:29:57 +0200 + bzr-hg (0.2.0~bzr409-1) unstable; urgency=low * Support running the test suite in parallel. diff -Nru bzr-hg-0.2.0~bzr409/debian/control bzr-hg-0.2.0~bzr409/debian/control --- bzr-hg-0.2.0~bzr409/debian/control 2011-03-15 23:43:45.0 +0100 +++ bzr-hg-0.2.0~bzr409/debian/control 2011-06-02 17:20:00.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Debian Bazaar Maintainers pkg-bazaar-ma...@lists.alioth.debian.org Uploaders: Jelmer Vernooij jel...@debian.org, John Francesco Ferlito jo...@inodes.org Build-Depends: debhelper (= 7.0.50~), python (= 2.6.6-3) -Build-Depends-Indep: mercurial, bzr (= 2.3), bzr ( 2.5~), mercurial (= 1.6~), mercurial ( 1.9~), python-testtools, python-subunit +Build-Depends-Indep: mercurial, bzr (= 2.3), bzr ( 2.5~), mercurial (= 1.6~), mercurial ( 1.9~), python-testtools, python-subunit, python-bzrlib.tests Standards-Version: 3.9.1 Homepage: https://launchpad.net/bzr-hg Vcs-Bzr: http://bzr.debian.org/pkg-bazaar/bzr-hg/unstable
Bug#605875: avant-window-navigator: diff for NMU version 0.4.0-2.1
Dear maintainer, I've prepared an NMU for avant-window-navigator (versioned as 0.4.0-2.1). The diff is attached to this message. Regards. diff -Nru avant-window-navigator-0.4.0/debian/changelog avant-window-navigator-0.4.0/debian/changelog --- avant-window-navigator-0.4.0/debian/changelog 2010-06-23 00:25:14.0 +0200 +++ avant-window-navigator-0.4.0/debian/changelog 2011-06-02 20:45:41.0 +0200 @@ -1,3 +1,11 @@ +avant-window-navigator (0.4.0-2.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/patches/ld-no-add-needed.patch +- fix a FTBFS with ld --no-add-needed; patch from ubuntu; Closes: #605875 + + -- Sandro Tosi mo...@debian.org Thu, 02 Jun 2011 20:45:08 +0200 + avant-window-navigator (0.4.0-2) unstable; urgency=medium * Set priority to medium to fix RC bug. diff -Nru avant-window-navigator-0.4.0/debian/patches/ld-no-add-needed.patch avant-window-navigator-0.4.0/debian/patches/ld-no-add-needed.patch --- avant-window-navigator-0.4.0/debian/patches/ld-no-add-needed.patch 1970-01-01 01:00:00.0 +0100 +++ avant-window-navigator-0.4.0/debian/patches/ld-no-add-needed.patch 2011-06-02 19:36:06.0 +0200 @@ -0,0 +1,99 @@ +--- avant-window-navigator-0.4.0.orig/src/Makefile.in avant-window-navigator-0.4.0/src/Makefile.in +@@ -310,6 +310,7 @@ AM_CPPFLAGS = \ + avant_window_navigator_LDADD = \ + $(DOCK_LIBS)\ + $(top_builddir)/libawn/libawn.la \ ++ $(AWN_LIBS) \ + $(NULL) + + avant_window_navigator_SOURCES = \ +--- avant-window-navigator-0.4.0.orig/src/Makefile.am avant-window-navigator-0.4.0/src/Makefile.am +@@ -18,6 +18,7 @@ bin_PROGRAMS = avant-window-navigator + avant_window_navigator_LDADD = \ + $(DOCK_LIBS)\ + $(top_builddir)/libawn/libawn.la \ ++ $(AWN_LIBS) \ + $(NULL) + + avant_window_navigator_SOURCES = \ +--- avant-window-navigator-0.4.0.orig/tests/Makefile.in avant-window-navigator-0.4.0/tests/Makefile.in +@@ -58,7 +58,7 @@ mkinstalldirs = $(SHELL) $(top_srcdir)/m + CONFIG_HEADER = $(top_builddir)/config.h + CONFIG_CLEAN_FILES = + CONFIG_CLEAN_VPATH_FILES = +-@HAVE_VALA_TRUE@am__EXEEXT_1 = test-vala-awn-dialog$(EXEEXT) ++#@HAVE_VALA_TRUE@am__EXEEXT_1 = test-vala-awn-dialog$(EXEEXT) + PROGRAMS = $(noinst_PROGRAMS) + am_test_applet_simple_OBJECTS = test-applet-simple.$(OBJEXT) + test_applet_simple_OBJECTS = $(am_test_applet_simple_OBJECTS) +@@ -315,13 +315,13 @@ AM_CPPFLAGS = $(STANDARD_CPPFLAGS) $(DIS + AM_CFLAGS = $(WARNING_FLAGS) + INCLUDES = $(AWN_CFLAGS) -I$(top_srcdir) + test_applet_simple_SOURCES = test-applet-simple.c +-test_applet_simple_LDADD = $(top_builddir)/libawn/libawn.la ++test_applet_simple_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + test_awn_effects_SOURCES = test-awn-effects.c +-test_awn_effects_LDADD = $(top_builddir)/libawn/libawn.la ++test_awn_effects_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + test_awn_icon_SOURCES = test-awn-icon.c +-test_awn_icon_LDADD = $(top_builddir)/libawn/libawn.la ++test_awn_icon_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + test_awn_icon_box_SOURCES = test-awn-icon-box.c +-test_awn_icon_box_LDADD = $(top_builddir)/libawn/libawn.la ++test_awn_icon_box_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + test_taskmanager_SOURCES = test-taskmanager.c + test_taskmanager_LDADD = \ + $(AWN_LIBS) \ +@@ -329,7 +329,7 @@ test_taskmanager_LDADD = \ + $(NULL) + + test_themed_icon_SOURCES = test-themed-icon.c +-test_themed_icon_LDADD = $(top_builddir)/libawn/libawn.la ++test_themed_icon_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + EXTRA_DIST = test-awn-dialog.py test-awn-tooltip.py test-effects.py \ + test-effects-scaling.py test-overlays.py \ + test-taskmanager-dnd.py test-taskmanager-windows.py \ +--- avant-window-navigator-0.4.0.orig/tests/Makefile.am avant-window-navigator-0.4.0/tests/Makefile.am +@@ -13,16 +13,16 @@ AM_CFLAGS = $(WARNING_FLAGS) + INCLUDES = $(AWN_CFLAGS) -I$(top_srcdir) + + test_applet_simple_SOURCES = test-applet-simple.c +-test_applet_simple_LDADD = $(top_builddir)/libawn/libawn.la ++test_applet_simple_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + + test_awn_effects_SOURCES = test-awn-effects.c +-test_awn_effects_LDADD = $(top_builddir)/libawn/libawn.la ++test_awn_effects_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + + test_awn_icon_SOURCES = test-awn-icon.c +-test_awn_icon_LDADD = $(top_builddir)/libawn/libawn.la ++test_awn_icon_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + + test_awn_icon_box_SOURCES = test-awn-icon-box.c +-test_awn_icon_box_LDADD = $(top_builddir)/libawn/libawn.la ++test_awn_icon_box_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS) + + test_taskmanager_SOURCES = test-taskmanager.c + test_taskmanager_LDADD = \ +@@ -31,7 +31,7 @@ test_taskmanager_LDADD = \ + $(NULL) + + test_themed_icon_SOURCES = test-themed-icon.c +-test_themed_icon_LDADD = $(top_builddir)/libawn/libawn.la ++test_themed_icon_LDADD = $(top_builddir)/libawn/libawn.la $(AWN_LIBS
Bug#626918: python-visual: diff for NMU version 1:5.12-1.2
tags 618055 + patch tags 626918 + patch thanks Dear maintainer, I've prepared an NMU for python-visual (versioned as 1:5.12-1.2). The diff is attached to this message. Regards. diff -u python-visual-5.12/debian/control python-visual-5.12/debian/control --- python-visual-5.12/debian/control +++ python-visual-5.12/debian/control @@ -2,7 +2,7 @@ Section: python Priority: optional Maintainer: Jonas Smedegaard d...@jones.dk -Build-Depends: cdbs (= 0.4.39), autotools-dev, devscripts (= 2.10.7), quilt, patchutils (= 0.2.25), python-all-dev (= 2.3.5-11), python-central (= 0.5.6), debhelper (= 6), dh-buildinfo, python-numpy, libgtkglextmm-x11-1.2-dev (= 1.2), libglibmm-2.4-dev, libpangomm-1.4-dev, libglademm-2.4-dev, libpango1.0-dev, libfreetype6-dev, libboost-python-dev, libboost-signals-dev, libboost-thread-dev, libglu1-mesa-dev | xlibmesa-glu-dev | libglu-dev +Build-Depends: cdbs (= 0.4.39), autotools-dev, devscripts (= 2.10.7), quilt, patchutils (= 0.2.25), python-all-dev (= 2.3.5-11), python-central (= 0.5.6), debhelper (= 6), dh-buildinfo, python-numpy, libgtkglextmm-x11-1.2-dev (= 1.2), libglibmm-2.4-dev, libpangomm-1.4-dev, libglademm-2.4-dev, libpango1.0-dev, libfreetype6-dev, libboost-python-dev, libboost-signals-dev, libboost-thread-dev, libglu1-mesa-dev | xlibmesa-glu-dev | libglu-dev, libxcb-render-util0-dev Standards-Version: 3.8.3 XS-Python-Version: all Homepage: http://www.vpython.org diff -u python-visual-5.12/debian/changelog python-visual-5.12/debian/changelog --- python-visual-5.12/debian/changelog +++ python-visual-5.12/debian/changelog @@ -1,3 +1,12 @@ +python-visual (1:5.12-1.2) unstable; urgency=low + + * Non-maintainer upload. +- with the rebuild, it links to the correct libboost; Closes: #626918 + * debian/control +- added 'libxcb-render-util0-dev' to b-d, fix a FTBFS; Closes: #618055 + + -- Sandro Tosi mo...@debian.org Wed, 01 Jun 2011 16:27:53 +0200 + python-visual (1:5.12-1.1) unstable; urgency=low * Non-maintainer upload.
Bug#625677: gtask: diff for NMU version 0.1.2-2.1
tags 625677 + patch thanks Dear maintainer, I've prepared an NMU for gtask (versioned as 0.1.2-2.1). The diff is attached to this message. Regards. diff -Nru gtask-0.1.2/debian/changelog gtask-0.1.2/debian/changelog --- gtask-0.1.2/debian/changelog 2010-04-24 23:36:34.0 +0200 +++ gtask-0.1.2/debian/changelog 2011-05-27 10:22:06.0 +0200 @@ -1,3 +1,15 @@ +gtask (0.1.2-2.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/control.in +- b-depends on libvala-0.12-dev; Closes: #625677 + * debian/patches/vala_check.patch +- check for updated vala lib name, patch from Ubuntu + * debian/libgtask-dev.install +- updated path location + + -- Sandro Tosi mo...@debian.org Fri, 27 May 2011 10:22:00 +0200 + gtask (0.1.2-2) unstable; urgency=low * debian/watch: Fixed. diff -Nru gtask-0.1.2/debian/control gtask-0.1.2/debian/control --- gtask-0.1.2/debian/control 2010-04-24 23:42:21.0 +0200 +++ gtask-0.1.2/debian/control 2011-05-27 10:22:11.0 +0200 @@ -13,7 +13,7 @@ gnome-pkg-tools (= 0.11), pkg-config (= 0.14), libglib2.0-dev (= 2.16.0), - libvala-dev, + libvala-0.12-dev, gtk-doc-tools (= 1.9), python-all-dev (= 2.2), python-gtk2-dev, diff -Nru gtask-0.1.2/debian/control.in gtask-0.1.2/debian/control.in --- gtask-0.1.2/debian/control.in 2010-04-24 23:17:59.0 +0200 +++ gtask-0.1.2/debian/control.in 2011-05-27 10:09:13.0 +0200 @@ -8,7 +8,7 @@ gnome-pkg-tools (= 0.11), pkg-config (= 0.14), libglib2.0-dev (= 2.16.0), - libvala-dev, + libvala-0.12-dev, gtk-doc-tools (= 1.9), python-all-dev (= 2.2), python-gtk2-dev, diff -Nru gtask-0.1.2/debian/libgtask-dev.install gtask-0.1.2/debian/libgtask-dev.install --- gtask-0.1.2/debian/libgtask-dev.install 2008-11-14 11:45:41.0 +0100 +++ gtask-0.1.2/debian/libgtask-dev.install 2011-05-27 09:58:51.0 +0200 @@ -2,4 +2,4 @@ debian/tmp/usr/lib/libgtask-1.0.a debian/tmp/usr/lib/libgtask-1.0.so debian/tmp/usr/lib/pkgconfig/gtask-1.0* -debian/tmp/usr/share/vala/vapi +debian/tmp/usr/share/vala*/vapi diff -Nru gtask-0.1.2/debian/patches/series gtask-0.1.2/debian/patches/series --- gtask-0.1.2/debian/patches/series 2010-04-24 22:54:37.0 +0200 +++ gtask-0.1.2/debian/patches/series 2011-05-27 09:58:59.0 +0200 @@ -1 +1,2 @@ 99_ltmain_as-needed.patch +vala_check.patch diff -Nru gtask-0.1.2/debian/patches/vala_check.patch gtask-0.1.2/debian/patches/vala_check.patch --- gtask-0.1.2/debian/patches/vala_check.patch 1970-01-01 01:00:00.0 +0100 +++ gtask-0.1.2/debian/patches/vala_check.patch 2011-05-27 10:00:31.0 +0200 @@ -0,0 +1,17 @@ +=== modified file 'configure.ac' +Index: gtask-0.1.2/configure.ac +=== +--- gtask-0.1.2.orig/configure.ac 2008-11-13 06:50:08.0 +0100 gtask-0.1.2/configure.ac 2011-05-27 10:00:25.0 +0200 +@@ -76,9 +76,9 @@ + + dnl === Build Vala + has_vala=no +-PKG_CHECK_MODULES(VALA, vala-1.0, has_vala=yes, has_vala=no) ++PKG_CHECK_MODULES(VALA, libvala-0.12, has_vala=yes, has_vala=no) + if test x$has_vala = xyes; then +-VAPI_DIR=`pkg-config --variable=vapidir vala-1.0` ++VAPI_DIR=`pkg-config --variable=vapidir libvala-0.12` + else + VAPI_DIR= + fi
Bug#553961: audit: diff for NMU version 1.7.13-1.1
Dear maintainer,
I've prepared an NMU for audit (versioned as 1.7.13-1.1). The diff
is attached to this message.
Regards.
diff -u audit-1.7.13/debian/changelog audit-1.7.13/debian/changelog
--- audit-1.7.13/debian/changelog
+++ audit-1.7.13/debian/changelog
@@ -1,3 +1,16 @@
+audit (1.7.13-1.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/ld-no-add-needed.diff
+- fix build with ld --no-add-needed, patch from bug; Closes: #553961
+ * debian/patches/add_missing_headers.diff
+- Add missing headers to fix undefined reference to `S_ISREG' linker error,
+ from Ubuntu
+ * debian/python-audit.install, debian/rules
+- use '*-packages' instead of 'site-packages', diff from Ubuntu
+
+ -- Sandro Tosi mo...@debian.org Wed, 25 May 2011 12:24:02 +0200
+
audit (1.7.13-1) unstable; urgency=low
* New upstream release.
diff -u audit-1.7.13/debian/python-audit.install audit-1.7.13/debian/python-audit.install
--- audit-1.7.13/debian/python-audit.install
+++ audit-1.7.13/debian/python-audit.install
@@ -1,2 +1,2 @@
-usr/lib/python*/site-packages/*.py
-usr/lib/python*/site-packages/*.so
+usr/lib/python*/*-packages/*.py
+usr/lib/python*/*-packages/*.so
diff -u audit-1.7.13/debian/rules audit-1.7.13/debian/rules
--- audit-1.7.13/debian/rules
+++ audit-1.7.13/debian/rules
@@ -100,9 +100,9 @@
$(RM) debian/tmp/usr/lib/libauparse.so
# The Debian way compiles Python packages on install
- $(RM) debian/tmp/usr/lib/python*/site-packages/_au*.*a
- $(RM) debian/tmp/usr/lib/python*/site-packages/auparse.*a
- $(RM) debian/tmp/usr/lib/python*/site-packages/au*.py[co]
+ $(RM) debian/tmp/usr/lib/python*/*-packages/_au*.*a
+ $(RM) debian/tmp/usr/lib/python*/*-packages/auparse.*a
+ $(RM) debian/tmp/usr/lib/python*/*-packages/au*.py[co]
$(RM) debian/tmp/usr/share/system-config-audit/*.py[co]
my-check:
@@ -129,8 +129,8 @@
chrpath -d $(CURDIR)/debian/auditd/usr/bin/aulastlog
chrpath -d $(CURDIR)/debian/auditd/usr/bin/ausyscall
chrpath -d $(CURDIR)/debian/libaudit0/lib/libauparse.so.0.0.0
- chrpath -d $(CURDIR)/debian/python-audit/usr/lib/python*/site-packages/_audit.so
- chrpath -d $(CURDIR)/debian/python-audit/usr/lib/python*/site-packages/auparse.so
+ chrpath -d $(CURDIR)/debian/python-audit/usr/lib/python*/*-packages/_audit.so
+ chrpath -d $(CURDIR)/debian/python-audit/usr/lib/python*/*-packages/auparse.so
chrpath -d $(CURDIR)/debian/system-config-audit/lib/system-config-audit-server
dh_link
diff -u audit-1.7.13/debian/patches/series audit-1.7.13/debian/patches/series
--- audit-1.7.13/debian/patches/series
+++ audit-1.7.13/debian/patches/series
@@ -4,0 +5,2 @@
+add_missing_headers.diff
+ld-no-add-needed.diff
only in patch2:
unchanged:
--- audit-1.7.13.orig/debian/patches/ld-no-add-needed.diff
+++ audit-1.7.13/debian/patches/ld-no-add-needed.diff
@@ -0,0 +1,54 @@
+--- audit-1.7.13.orig/audisp/plugins/remote/Makefile.in
audit-1.7.13/audisp/plugins/remote/Makefile.in
+@@ -240,7 +240,7 @@
+ man_MANS = audisp-remote.8 audisp-remote.conf.5
+ audisp_remote_SOURCES = audisp-remote.c remote-config.c queue.c
+ audisp_remote_CFLAGS = -fPIE -DPIE -g -D_REENTRANT -D_GNU_SOURCE -Wundef
+-audisp_remote_LDFLAGS = -pie -Wl,-z,relro $(gss_libs)
++audisp_remote_LDFLAGS = -pie -Wl,-z,relro -lkrb5 $(gss_libs)
+ all: all-am
+
+ .SUFFIXES:
+--- audit-1.7.13.orig/audisp/plugins/remote/Makefile.am
audit-1.7.13/audisp/plugins/remote/Makefile.am
+@@ -34,7 +34,7 @@
+
+ audisp_remote_SOURCES = audisp-remote.c remote-config.c queue.c
+ audisp_remote_CFLAGS = -fPIE -DPIE -g -D_REENTRANT -D_GNU_SOURCE -Wundef
+-audisp_remote_LDFLAGS = -pie -Wl,-z,relro $(gss_libs)
++audisp_remote_LDFLAGS = -pie -Wl,-z,relro -lkrb5 $(gss_libs)
+
+ install-data-hook:
+ mkdir -p -m 0750 ${DESTDIR}${plugin_confdir}
+--- audit-1.7.13.orig/src/Makefile.in
audit-1.7.13/src/Makefile.in
+@@ -273,10 +273,10 @@
+ AM_CFLAGS = -D_REENTRANT -D_GNU_SOURCE
+ noinst_HEADERS = auditd-config.h auditd-event.h auditd-listen.h ausearch-llist.h ausearch-options.h auditctl-llist.h aureport-options.h ausearch-parse.h aureport-scan.h ausearch-lookup.h ausearch-int.h auditd-dispatch.h ausearch-string.h ausearch-nvpair.h ausearch-common.h ausearch-avc.h ausearch-time.h ausearch-lol.h
+ auditd_SOURCES = auditd.c auditd-event.c auditd-config.c auditd-reconfig.c auditd-sendmail.c auditd-dispatch.c auditd-listen.c
+-auditd_CFLAGS = -fPIE -DPIE -g -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing
+-auditd_LDFLAGS = -pie -Wl,-z,relro
++auditd_CFLAGS = -pthread -fPIE -DPIE -g -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing
++auditd_LDFLAGS = -pthread -pie -Wl,-z,relro
+ auditd_DEPENDENCIES = mt/libauditmt.a libev/libev.a
+-auditd_LDADD = @LIBWRAP_LIBS@ @libev_LIBS@ -Llibev -lev -lrt -lm $(gss_libs)
++auditd_LDADD = @LIBWRAP_LIBS@ @libev_LIBS@ -Llibev -lev -lrt -lm -lkrb5 $(gss_libs)
+ auditctl_SOURCES = auditctl.c auditctl-llist.c delete_all.c
+ auditctl_DEPENDENCIES = mt/libauditmt.a
+ aureport_SOURCES = aureport.c auditd-config.c
Bug#625150: matplotlib: FTBFS: ln: creating symbolic link `/build/user-matplotlib_0.99.3-1-amd64-C4ZThE/matplotlib-0.99.3/debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/
Hi Stefano, thanks for the patch, but... On Fri, May 6, 2011 at 01:46, Stefano Rivera stefa...@debian.org wrote: Sandro: This code has completely changed in 1.x, I suspect it won't be a blocker for bringing 1.x to unstable. ... 1.0.1 rebuilt in sid fails with the same error :( -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625695: Perl upgrade in Unstable breaks mrtg
Hi Dominic, thanks for the patch On Fri, May 6, 2011 at 20:59, Dominic Hargreaves d...@earth.li wrote: NMU diff attached. Unless the maintainer or release team ask me to upload sooner, or the maintainer asks me to not upload, I will upload this next Wednesday. I'll see if I can work on mrtg asap, as to update it to the latest upstream version (that already includes this fix). If you don't hear back from me on wednesday, please go on with you NMU. Thanks for your interest, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623432: new version breaks offlineimap
On Wed, Apr 20, 2011 at 09:57, Mehdi Dogguy me...@dogguy.org wrote: reassign 623432 offlineimap found 623432 offlineimap/6.3.2~rc3-2 tags 623432 + wheezy sid thanks Are you sure about that? the important code at /usr/lib/python2.6/imaplib.py is: try: import ssl except ImportError: pass else: class IMAP4_SSL(IMAP4): and infact IMAP4_SSL is not defined since the python maintainer deliberately broke ssl module: $ python2.6 -c import ssl Traceback (most recent call last): File string, line 1, in module File /usr/lib/python2.6/ssl.py, line 64, in module from _ssl import PROTOCOL_SSLv2, PROTOCOL_SSLv3, PROTOCOL_SSLv23, PROTOCOL_TLSv1 ImportError: cannot import name PROTOCOL_SSLv2 See #623423 Regards. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623432: new version breaks offlineimap
On Wed, Apr 20, 2011 at 10:53, Mehdi Dogguy me...@dogguy.org wrote: It's a pity that the testsuite didn't report anything about those missing/broken modules. actually it's there (at least in the i386 buildd log): test_ssl test_ssl skipped -- No SSL support ... 7 skips unexpected on linux2: test_cprofile test_gdbm test_hotshot test_ioctl test_profile test_pstats test_ssl (and it's fine it didn't failed, since you can run the full test suite but you compilation didn't include some features) but it needs someone to look at the tests output in order for them to be useful. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611316: Bug#616364: transition: python-numpy
On Mon, Apr 4, 2011 at 10:20, Julien Cristau jcris...@debian.org wrote: On Sun, Apr 3, 2011 at 20:17:38 +0200, Sandro Tosi wrote: How long should we keep waiting? From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616364: Fix blocked by 616702: transition: libvigraimpex, 613207: python-sphinx: please upload 1.x series into unstable, 611316: nipy: FTBFS: Some tests fail 616702 was cleared last night. What's the status of the other two? 613207: sphinx will be uploaded along with numpy 611316: if it holds the transition, we can remove it from testing until fixed (76 days RC bug, 58 popcon), but in any case: Yaroslav, any news on that? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564576: Package completely fails to support IPv6
On Mon, Feb 14, 2011 at 15:00, Scott Kitterman sc...@kitterman.com wrote: I think this should be RC for Wheezy as libspf appears to completely lack IPv6 support. why? IPv6 support is a release goal for wheezy, and RG does not warrant a RC severity: please fix it. [1] http://release.debian.org/wheezy/goals.txt Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
On Tue, Jan 4, 2011 at 03:06, Jonathan Nieder jrnie...@gmail.com wrote: ii python-central 0.6.16+nmu1 There goes that theory. Alternatively this could be a bug in packages that moved from dh_pycentral to dh_python2 as Sandro suggested. If so, does anyone have a pointer to a page describing what these packages should do to avoid the problem? Yes, there is a page[1] on the wiki (it talks about pycentral-pysupport, but it can be applied also to -dh_python2); here[2]'s and example of a package using it. [1] http://wiki.debian.org/Python/central2support [2] http://svn.debian.org/viewsvn/python-modules/packages/numpy/trunk/debian/python-numpy.preinst Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607988: ok sure
On Sun, Jan 2, 2011 at 12:34, dave b db.pub.m...@gmail.com wrote: Ok sure - the bug isn't so critical really and really what happens is that when upgrading there are those damn broken symlinks which should be cleaned up / ignored. Indeed; in particular, reportlab maintainer is the same maintaining python interpreters packages (and the python modules team implemented in all the packages moving out from python-central a workaround, it seems the maintainer didn't managed to add one for reportlab) It would appear that in my case several of the python packages I had installed but not --purged (in removal) resulted in their symlinks being left behind. Let me guess: all of them were using python-central ? -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606993: [Python-apps-team] Bug#606993: subdownloader: always fail to download selected subs
Hi all,
On Mon, Dec 13, 2010 at 20:17, florian fgr...@hotmail.com wrote:
Package: subdownloader
Version: 2.0.14-1
Severity: grave
Justification: renders package unusable
When launched from commandline, this message appears for all selected subtitle
Traceback (most recent call last):
File /usr/share/subdownloader/gui/main.py, line 1043, in onButtonDownload
destinationPath = self.getDownloadPath(sub.getVideo(), sub)
File /usr/share/subdownloader/gui/main.py, line 1012, in getDownloadPath
downloadFullPath = os.path.join(folderPath, subFileName).decode('utf8')
File /usr/lib/python2.6/encodings/utf_8.py, line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position
13: ordinal not in range(128)
the problem is easily replicable with:
$ python -c import os.path ; print os.path.join('/tmp/',
u'\xe9').decode('utf8')
Traceback (most recent call last):
File string, line 1, in module
File /usr/lib/python2.6/encodings/utf_8.py, line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
position 5: ordinal not in range(128)
That's because one of the 2 parameters is already encoded (the '/tmp/'
one, which is a string) while the other is unicode. The solution here
is either make both params a string, and then decode after the join()
or just remove the .decode('utf8'):
$ python -c import os.path ; print os.path.join('/tmp/', u'\xe9')
/tmp/é
since join() returns a unicode object in that case.
What do the subdownloader developers think about it?
Even if the bug is annoying, I don't think it deserves an RC severity
in Debian: anynow against downgrading it to important?
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605155: gquilt: Use of PYTHONPATH env var in an insecure way
Hi Christine, On Thu, Dec 2, 2010 at 04:22, Christine Spang sp...@mit.edu wrote: It looks like gquilt doesn't actually require PYTHONPATH to be set, anyway, since python already adds the directory of the executed script to sys.path. I propose the following patch: That patch seems ok. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605155: gquilt: Use of PYTHONPATH env var in an insecure way
found 605155 0.20-2 0.22-1 tags 605155 fixed-upstream thanks Hi Peter On Sun, Nov 28, 2010 at 01:11, Peter Williams pwil3...@bigpond.net.au wrote: Please update to gquilt-0.24 (released about 7 weeks ago) as the above problem is no longer present in the code. Thanks for letting us know! Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605150: mmass: Use of PYTHONPATH env var in an insecure way
Package: mmass
Version: 3.8.0-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605151: snappea: Use of PYTHONPATH env var in an insecure way
Package: snappea
Version: 3.0d3-20
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605152: gquilt: Use of PYTHONPATH env var in an insecure way
Package: gquilt
Version: 0.22-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605153: pybliographer: Use of PYTHONPATH env var in an insecure way
Package: pybliographer
Version: 1.2.14-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605155: gquilt: Use of PYTHONPATH env var in an insecure way
Package: gquilt
Version: 0.22-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605154: salome: Use of PYTHONPATH env var in an insecure way
Package: salome
Version: 5.1.3-9
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605156: pybliographer: Use of PYTHONPATH env var in an insecure way
Package: pybliographer
Version: 1.2.14-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605157: calendarserver: Use of PYTHONPATH env var in an insecure way
Package: calendarserver
Version: 2.4.dfsg-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605158: ironpython: Use of PYTHONPATH env var in an insecure way
Package: ironpython
Version: 2.6~beta2-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605159: gnumed-client: Use of PYTHONPATH env var in an insecure way
Package: gnumed-client
Version: 0.8.4-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605160: pymca: Use of PYTHONPATH env var in an insecure way
Package: pymca
Version: 4.4.0-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605162: gnumed-client: Use of PYTHONPATH env var in an insecure way
Package: gnumed-client
Version: 0.8.4-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605161: opendnssec-signer: Use of PYTHONPATH env var in an insecure way
Package: opendnssec-signer
Version: 1.1.3-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605165: opendnssec-signer: Use of PYTHONPATH env var in an insecure way
Package: opendnssec-signer
Version: 1.1.3-1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605166: calendarserver: Use of PYTHONPATH env var in an insecure way
Package: calendarserver
Version: 2.4.dfsg-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605164: guake: Use of PYTHONPATH env var in an insecure way
Package: guake
Version: 0.4.2-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605163: guake: Use of PYTHONPATH env var in an insecure way
Package: guake
Version: 0.4.2-2
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605167: gnome-schedule: Use of PYTHONPATH env var in an insecure way
Package: gnome-schedule
Version: 2.1.1-3
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605169: gnome-schedule: Use of PYTHONPATH env var in an insecure way
Package: gnome-schedule
Version: 2.1.1-3
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605168: distcc-pump: Use of PYTHONPATH env var in an insecure way
Package: distcc-pump
Version: 3.1-3.1
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602742: apt-listchanges: errors during removal
2010/11/7 Gonzalo Pérez de Olaguer Córdoba g...@iies.es: Package: apt-listchanges Version: 2.83 Severity: critical Tags: patch Justification: breaks unrelated software I have tagged this bug as critical because the post removal script is not idempotent (policy requirement) and because aptitude install and remove operations fail as long as apt-listchanges postremoval script fails. don't you think 'critical' is a bit too much? I don't consider apt/aptitude so unrelated to apt-listchanges. 'serious' would have been enough, but still RC. Before upgrading from lenny to squeeze I have started by upgrading aptitude. Due to dependencies, aptitude tells me to remove apt-listchanges. I say ok. During upgrade of aptitude and removal of apt-listchanges the following error appears: Desinstalando apt-listchanges ... mv: no se puede efectuar `stat' sobre «/etc/apt/apt.conf.d/20listchanges»: No existe el fichero o el directorio dpkg: error al procesar apt-listchanges (--remove): el subproceso post-removal script devolvió el código de salida de error 1 i.e., /etc/apt/apt-conf.d/20listchanges doesn't exist. That's true. /etc/apt/apt.conf.d/20listchanges.disabled also doesn't exist. What I have here is /etc/apt/listchanges.conf instead. Then I run manually /var/lib/dpkg/info/apt-listchanges.prerm and it runs ok. Then I run /varlib/dpkg/info/apt-listchanges.postrm and get the same error. It gets solved when I change the folowing line: if [ $1 = remove ]; then - mv $hook $hook.disabled + test -e $hook mv $hook $hook.disabled fi This way the script is idempotent (it can be run several times without failing). Anyhow, I've just committed to the git repo your patch, and I'll upload the package soon. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601690: CVE-2010-3493: smtpd module
On Mon, Nov 1, 2010 at 14:26, Matthias Klose d...@debian.org wrote: offline this week, so please go ahead with a fix. so get comaintainers, that can work when you're offline -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593019: solfege: FTBFS: ImportError: cannot import name GObject
reassign 593019 python-gobject forcemerge 590680 593019 thanks this bug reported in solfege is actually 590680 (in python-gobject): reassigning and merging. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595860: solfege: diff for NMU version 3.16.4-1.1
tags 595860 + pending thanks Dear maintainer, I've prepared an NMU for solfege (versioned as 3.16.4-1.1) and uploaded it to DELAYED/1. Regards. diff -Nru solfege-3.16.4/debian/changelog solfege-3.16.4/debian/changelog --- solfege-3.16.4/debian/changelog 2010-07-24 12:37:04.0 +0200 +++ solfege-3.16.4/debian/changelog 2010-09-19 13:38:34.0 +0200 @@ -1,3 +1,13 @@ +solfege (3.16.4-1.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/patches/test-py-displayhook.patch +- redefine sys.__displayhook__ in test.py, to avoid to overwrite the '_' + upstream function; thanks to Lucas Nussbaum for the report ant to Michael + Schutte for the patch; Closes: #595860 + + -- Sandro Tosi mo...@debian.org Sun, 19 Sep 2010 13:38:30 +0200 + solfege (3.16.4-1) unstable; urgency=low * New upstream release diff -Nru solfege-3.16.4/debian/patches/series solfege-3.16.4/debian/patches/series --- solfege-3.16.4/debian/patches/series 2010-03-28 22:23:10.0 +0200 +++ solfege-3.16.4/debian/patches/series 2010-09-19 12:31:42.0 +0200 @@ -2,3 +2,4 @@ xsltproc-nonet.patch xmllint-nonet.patch test-py-xvfb-run.patch +test-py-displayhook.patch diff -Nru solfege-3.16.4/debian/patches/test-py-displayhook.patch solfege-3.16.4/debian/patches/test-py-displayhook.patch --- solfege-3.16.4/debian/patches/test-py-displayhook.patch 1970-01-01 01:00:00.0 +0100 +++ solfege-3.16.4/debian/patches/test-py-displayhook.patch 2010-09-19 12:23:20.0 +0200 @@ -0,0 +1,27 @@ +Subject: Set sys.__displayhook__ = sys.displayhook in test.py +From: Michael Schutte mi...@uiae.at +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595860 +Forwarded: not-needed + +doctest from Python = 2.6 resets sys.displayhook whenever a test is +run. The default displayhook sets _ to the evaluation result of the +last line, but this messes with the global definition of _ in +solfege.i18n. + +This patch implements an ugly fix by redefining sys.__displayhook__ in +test.py. Upstream has already fixed the problem properly by avoiding +doctest in the first place. + +Index: solfege-3.16.4/test.py +=== +--- solfege-3.16.4.orig/test.py 2010-09-18 19:28:26.0 +0200 solfege-3.16.4/test.py 2010-09-18 19:28:33.0 +0200 +@@ -19,7 +19,7 @@ + else: + print s + +-sys.displayhook = f ++sys.__displayhook__ = sys.displayhook = f + + from solfege import testlib + import solfege.i18n
