Bug#877740: gedit-latex-plugin: diff for NMU version 3.20.0-1.2
Thank you again! Meanwhile, I merged your changes back in salsa, where there is a new version in principle ready to be uploaded: https://salsa.debian.org/debian/gedit-latex-plugin It fixes a number of small other issues which are not urgent, but neither invasive. I'll let you judge if you want to proceed with this NMU or rather upload the new version (notice I'm not a DD, so I need a sponsor anyway). If you choose the second option, let me know beforehand and I will quickly squeeze 3.20.0-1.2 out of debian/changelog. CC-ing Olivier Tilloy, who had prepared few months ago a 3.20.0-2 fixing this issue which however, to the best of my understanding, never got uploaded to any repo, so I've removed the related lines from debian/changelog. Pietro Il giorno sab, 13/02/2021 alle 10.57 +0200, Adrian Bunk ha scritto: > Dear maintainer, > > I've prepared an NMU for gedit-latex-plugin (versioned as 3.20.0- > 1.2). > The diff is attached to this message. > > This upload was a correction for a mistake I did in my previous NMU. > > cu > Adrian
Bug#877740: Bug#955812: gedit-latex-plugin: diff for NMU version 3.20.0-1.1
Il giorno dom, 07/02/2021 alle 11.30 +0200, Adrian Bunk ha scritto: > I've prepared an NMU for gedit-latex-plugin (versioned as 3.20.0- > 1.1). Thank you very much Adrian, and sorry everybody for the extremely slow reaction. Pietro
Bug#945681: gvb: diff for NMU version 1.4-1.1
Dear Adrian, thank you, I really appreciate. I was planning to fix that packaging mistake, but as you might have noticed, I have really slow reactions lately - and then, I still need to go through a sponsor. So if you prefer, feel free to re-upload the package without delay. Pietro Il giorno gio, 26/12/2019 alle 15.04 +0200, Adrian Bunk ha scritto: > Control: tags 945681 + patch > Control: tags 945681 + pending > > Dear maintainer, > > I've prepared an NMU for gvb (versioned as 1.4-1.1) and uploaded it > to DELAYED/14. Please feel free to tell me if I should cancel it. > > cu > Adrian
Bug#885212: Somebody plans to work on this?
Dear Debian Science Maintainers, are there plans to fix this, or should we worry? (I ask because I am the maintainer of gbutils which is set for autoremoval in 9 days due to this) Thanks, Pietro
Bug#896726: gedit-source-code-browser-plugin: diff for NMU version 3.0.3-5.1
Dear Adrian, Il giorno dom, 10/06/2018 alle 16.44 +0300, Adrian Bunk ha scritto: > I've prepared an NMU for gedit-source-code-browser-plugin (versioned > as > 3.0.3-5.1) and uploaded it to DELAYED/15. Thanks, this is much appreciated. Pietro
Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring
Il giorno dom, 31/12/2017 alle 17.13 -0500, Jeremy Bicha ha scritto: > On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston <me@pietrobattiston > .it> wrote: > > given that gallery is dead upstream since 2014 > > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to > > orphan > > this package (which I'm using no more). > > > > In fact, gallery-uploader (and its dependency python-galleryremote) > > never supported Gallery 3, and hence were officially obsolete since > > since way before. > > In that case, could you consider requesting those two packages be > removed instead of orphaning them? Done: #888645, #888646 Pietro
Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring
Il giorno dom, 31/12/2017 alle 17.13 -0500, Jeremy Bicha ha scritto: > On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston <me@pietrobattiston > .it> wrote: > > given that gallery is dead upstream since 2014 > > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to > > orphan > > this package (which I'm using no more). > > [...] > > In that case, could you consider requesting those two packages be > removed instead of orphaning them? Sure. For reference: https://groups.yahoo.com/neo/groups/gallery3/conversations/messages/555 Pietro
Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring
Il giorno dom, 31/12/2017 alle 14.28 -0500, Jeremy Bicha ha scritto: > It is my understanding that it is Release > Critical for a package to recommend a removed library because it > keeps > the package from being a candidate for auto-removal when users > upgrade. Thanks Jeremy for opening this issue, given that gallery is dead upstream since 2014 ( http://galleryproject.org/time-to-hibernate ), I'm tempted to orphan this package (which I'm using no more). In fact, gallery-uploader (and its dependency python-galleryremote) never supported Gallery 3, and hence were officially obsolete since since way before. I'm going to send a message to the unofficial support group just to check if anybody complains. Pietro
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Il giorno lun, 24/10/2016 alle 16.28 +0200, IOhannes m zmölnig (Debian/GNU) ha scritto: > > On 2016-10-24 13:48, Pietro Battiston wrote: > > > > Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha > > scritto: > > > > > > It's just a wild guess, but this > > > > > > Pietro Battiston wrote: > > > > > > > > > > > > Package: ardour > > > > Version: 1:5.4.0~dfsg-1 > > > [...] > > > > > > > > > > > > ii ardour-data 1:4.2~dfsg-5 > > > > > > just doesn't seem corect to me! > > > > > > > Oooohhh... > > right. > > This explains everything. > > > > Package "ardour" should probably depend on the same exact version > > of > > package "ardour-data". > > this is the fix i uploaded today with 1:5.4.0~dfsg-2 Yep, I replied before seeing it! Thank you very much, Pietro
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha scritto: > It's just a wild guess, but this > > Pietro Battiston wrote: > > > > Package: ardour > > Version: 1:5.4.0~dfsg-1 > [...] > > > > ii ardour-data 1:4.2~dfsg-5 > > just doesn't seem corect to me! > Oooohhh... right. This explains everything. Package "ardour" should probably depend on the same exact version of package "ardour-data". Pietro
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Il giorno lun, 24/10/2016 alle 09.31 +0200, IOhannes m zmölnig ha scritto: > [...] > is it possible to try the ardour5 binary provided by upstream [1] and > see whether the problem persists? > I just did (with the "Free/Demo" version), and it works perfectly (with the same session/jack configuration). However, experimenting a bit more... the packaged ardour5 works too. But if I downgrade to 4.7, it will now segfault :-) So I understood what's going on (but now why): if you install the package for version 4 or 5, it will work. But if you upgrade/downgrade from a version 4 to 5 or vice-versa, the folder in /usr/share (e.g. /usr/share/ardour4) will keep its name, with the result that the new version will not find the required files. For instance, I now have a version 4.7 installed with a /usr/share/ardour5 folder (not appearing in the output of "dpkg -L ardour", by the way). Uninstalling and reinstalling the desired version "fixes" the issue. Pietro
Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
Package: ardour Version: 1:5.4.0~dfsg-1 Severity: grave Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to load any project. I am attaching a gdb run (from 1:5.4.0~dfsg-1). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ardour depends on: ii ardour-data 1:4.2~dfsg-5 ii jackd 5 ii libarchive13 3.2.1-4 ii libasound21.0.29-1 ii libatk1.0-0 2.18.0-1 ii libatkmm-1.6-1v5 2.24.2-1 ii libaubio4 0.4.1-2+b3 ii libbluetooth3 5.33-1 ii libc6 2.24-3 ii libcairo2 1.14.2-2 ii libcairomm-1.0-1v51.12.0-1 ii libcurl3-gnutls 7.45.0-1 ii libcwiid1 0.6.00+svn201-3.2 ii libfftw3-single3 3.3.5-1 ii libflac8 1.3.1-4 ii libfluidsynth11.1.6-3 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.6-2 ii libgcc1 1:5.2.1-22 ii libgdk-pixbuf2.0-02.36.0-1 ii libglib2.0-0 2.50.0-1 ii libglibmm-2.4-1v5 2.50.0-1 ii libgtk2.0-0 2.24.28-1 ii libgtkmm-2.4-1v5 1:2.24.5-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20150825git1ed50c92~dfsg-1 ii liblilv-0-0 0.24.0~dfsg0-1 ii liblo70.28-5 ii liblrdf0 0.4.0-5 ii libltc11 1.1.4-1 ii libogg0 1.3.2-1 ii libpango-1.0-01.38.0-3 ii libpangocairo-1.0-0 1.38.0-3 ii libpangoft2-1.0-0 1.38.0-3 ii libpangomm-1.4-1v52.40.1-3 ii librubberband21.8.1-6+b1 ii libsamplerate00.1.8-8 ii libserd-0-0 0.24.0~dfsg0-1 ii libsigc++-2.0-0v5 2.10.0-1 ii libsndfile1 1.0.25-9.1 ii libsord-0-0 0.16.0~dfsg0-1 ii libsratom-0-0 0.4.6~dfsg0-1 ii libstdc++66.2.0-6 ii libsuil-0-0 0.8.2~dfsg0-1 ii libtag1v5 1.9.1-2.4 ii libvamp-hostsdk3v52.6~repack0-2 ii libvamp-sdk2v52.6~repack0-2 ii libx11-6 2:1.6.3-1 ii libxml2 2.9.2+zdfsg1-4 Versions of packages ardour recommends: ii ardour-video-timeline 1:5.4.0~dfsg-1 ii chromium [www-browser] 50.0.2661.94-1 ii epiphany-browser [www-browser] 3.18.0-1+b1 ii firefox-esr [www-browser] 45.0.1esr-1 ii iceweasel 45.3.0esr-1 ii links [www-browser] 2.12-1 ii w3m [www-browser] 0.5.3-25 Versions of packages ardour suggests: pn jamin ii qjackctl 0.4.0-1 -- no debconf information (gdb) r Starting program: /usr/lib/ardour5/ardour-5.4.0 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot find ArdourMono TrueType font bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale Ardour5.4.0 (built using 1:5.4.0~dfsg-1 and GCC version 6.2.0 20161010) ardour: [INFO]: Your system is configured to limit Ardour to only 65.536 open files ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config ardour: [INFO]: Loading user configuration file /home/pietro/.config/ardour5/config [New Thread 0x7fffd942d700 (LWP 27425)] ardour: [INFO]: CPU vendor: GenuineIntel ardour: [INFO]: AVX-capable processor ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz ardour: [INFO]: Using SSE optimized routines [New Thread 0x7fffd8c2c700 (LWP 27426)] [New Thread 0x7fffd3fff700 (LWP 27427)] [New Thread 0x7fffd37fe700 (LWP 27428)] [New Thread 0x7fffd196e700 (LWP 27429)] [New Thread 0x7fffd116d700 (LWP 27430)] Cannot xinstall SIGPIPE error handler ardour: [INFO]: Loading default ui configuration file /etc/ardour5/default_ui_config ardour: [INFO]: Loading user ui configuration file /home/pietro/.config/ardour5/ui_config ardour: [WARNING]: Color file for dark-ardour not found along /home/pietro/.config/ardour5/themes:/usr/share/ardour5/themes ardour: [INFO]: Loading ui configuration file /etc/ardour5/clearlooks.rc /etc/ardour5/clearlooks.rc:9: Invalid symbolic
Bug#783169: google-drive-ocamlfuse
I just want to signal that google-drive-ocamlfuse seems to work reliably, has a Ubuntu package (which I'm using under Debian) and is quite comfortable to use - just mounts the drive in the desired position: http://gdfuse.forge.ocamlcore.org/ Pietro
Bug#798738: Unable to reproduce
I'm unfortunately unable to reproduce both on my normal user and on a brand new user: fontypython seems to behave fine. The only difference I spot in the dependencies is that my version of python-wxgtk3.0 is 3.0.2.0+dfsg-1+b1 : could this explain the different behavior? Pietro
Bug#773579: fontypython should be ported to wx 3.0 (yes, again)
Il giorno dom, 21/12/2014 alle 20.07 +, Olly Betts ha scritto: On Sun, Dec 21, 2014 at 12:41:19AM +0100, Pietro Battiston wrote: Il giorno sab, 20/12/2014 alle 10.37 +, Olly Betts ha scritto: On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote: [...] 1) I and other people (a niche, but a stable niche, and if I don't misinterpret popcon, its 0.03% of active users locate it in the top 10% of debian packages) use it I think you must be misinterpreting - popcon doesn't report data about how much people use the packages they have installed (only if they've used each package recently). Sorry... I'm missing the difference! [...] I tried to test the latest fontypython version (your NMU) but the package seems to be missing any actual python code: [...] Yes, that's exactly what I meant when I said my package was useless. It looks like the assertions are due to trying to create wx.Locale objects before the wx.App object. It doesn't need to create one in every file - just creating one should be enough. No worry, the lines you deleted are apparently not needed at all. It then runs into the wx.ListCtrl issue you mention in the other bug. The simple fix is to just disable all such assertions (as happens by default with wx 2.8): http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README With that, fontypython runs for me - I'll send an nmudiff in a moment. It would be better to try to fix them, but I don't have time to dig in deeper. If you want to, please do - or let me know if you'd like me to just upload my NMU. I did fix the issue (patch 0003-... in the attached debdiff), but your approach may be better suited for jessie. Most importantly, I introduced another minimal patch to fix an annoying bug (patch 0001-...). Feel free to upload my nmu or to only pick this last patch, as you think is more appropriate. Pietro diff -Nru fontypython-0.4.4/debian/changelog fontypython-0.4.4/debian/changelog --- fontypython-0.4.4/debian/changelog 2014-12-21 23:05:39.0 +0100 +++ fontypython-0.4.4/debian/changelog 2014-12-21 22:57:15.0 +0100 @@ -1,3 +1,12 @@ +fontypython (0.4.4-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Removed flawed patch (wx 2.8 is not in jessie) + * Patch: do not crash on empty pogs list + * Patches for compatibility with wxpython 3.0 (Closes: #773579) + + -- Pietro Battiston m...@pietrobattiston.it Sun, 21 Dec 2014 22:54:02 +0100 + fontypython (0.4.4-1.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch --- fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch 1970-01-01 01:00:00.0 +0100 +++ fontypython-0.4.4/debian/patches/0001-Do-not-crash-on-empty-pogs-list.patch 2014-12-21 22:49:18.0 +0100 @@ -0,0 +1,21 @@ +From: Pietro Battiston m...@pietrobattiston.it +Date: Sun, 21 Dec 2014 11:50:28 +0100 +Subject: Do not crash on empty pogs list + +--- + fontypythonmodules/gui_PogChooser.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/fontypythonmodules/gui_PogChooser.py b/fontypythonmodules/gui_PogChooser.py +index 94b7f2e..f233529 100644 +--- a/fontypythonmodules/gui_PogChooser.py b/fontypythonmodules/gui_PogChooser.py +@@ -80,7 +80,7 @@ class PogChooser(wx.ListCtrl) : + i = self.FindItem(-1, select) + self.indexselected = i # Set this to help initial icon settings. + self.Select(i, True) +- else: ++ elif self.__poglistCopy: + self.Select(0, False) + self.indexselected = -1 + diff -Nru fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch --- fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch 2014-12-21 23:05:39.0 +0100 +++ fontypython-0.4.4/debian/patches/0001-Select-wx-2.8-rather-than-3.0.patch 1970-01-01 01:00:00.0 +0100 @@ -1,21 +0,0 @@ -From: Pietro Battiston m...@pietrobattiston.it -Date: Sun, 14 Dec 2014 09:39:17 +0100 -Subject: Select wx 2.8 (rather than 3.0) - - fontypythonmodules/sanitycheck.py | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/fontypythonmodules/sanitycheck.py b/fontypythonmodules/sanitycheck.py -index cf4fcc1..0448b6b 100644 a/fontypythonmodules/sanitycheck.py -+++ b/fontypythonmodules/sanitycheck.py -@@ -31,7 +31,7 @@ except: - - try: - import wxversion ## Dec 2007: noticed that it may not be installed along with wxPython -- wxversion.ensureMinimal(2.8) -+ wxversion.select(2.8) - except: - print strings.wxVersionError - print diff -Nru fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch fontypython-0.4.4/debian/patches/0002-Removed-unused-code-which-causes-crash-with-wx-3.0.patch
Bug#773579: fontypython should be ported to wx 3.0 (yes, again)
Il giorno dom, 21/12/2014 alle 22.58 +, Olly Betts ha scritto: On Sun, Dec 21, 2014 at 11:16:16PM +0100, Pietro Battiston wrote: Il giorno dom, 21/12/2014 alle 20.07 +, Olly Betts ha scritto: On Sun, Dec 21, 2014 at 12:41:19AM +0100, Pietro Battiston wrote: Il giorno sab, 20/12/2014 alle 10.37 +, Olly Betts ha scritto: On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote: [...] 1) I and other people (a niche, but a stable niche, and if I don't misinterpret popcon, its 0.03% of active users locate it in the top 10% of debian packages) use it I think you must be misinterpreting - popcon doesn't report data about how much people use the packages they have installed (only if they've used each package recently). Sorry... I'm missing the difference! Looking at: https://qa.debian.org/popcon.php?package=fontypython 304 of the 172166 machines which report to popcon have fontypython installed. Of those 304: * 47 appear to have actually used the package in the past X days (I forget what X is) * 246 have it installed but haven't used it in the past X days * 10 have recently installed or upgraded it so information on when they last used it isn't available (since this is determined by looking at the last access times of files in the package). * 1 didn't report a useful atime or ctime - not sure what can cause that. And overall, there are 17708 packages with more reported installs and 12444 with more reported recent uses. That page doesn't show how many packages there are, but apparently jessie has about 2. That's were I got it wrong... I saw ~ 400 000 lines in http://popcon.debian.org/by_inst.gz and thought that was the number of packages. Instead all but ~ 49 499 say Not in sid, and probably even less are in jessie. Sorry for the OT. It looks like the assertions are due to trying to create wx.Locale objects before the wx.App object. It doesn't need to create one in every file - just creating one should be enough. No worry, the lines you deleted are apparently not needed at all. If we don't create a wx.Locale at all, are the stock button labels localised? I only have English locales set up so I can't trivially check (the call to setlocale() fails if I set LANG to a locale I don't have set up), but I guess you have an Italian locale set up. Yes, stock buttons are indeed localized (i.e. the wx.ID_CANCEL in the settings dialog). The only localization initialization I see is in fontypythonmodules/i18n.py ... maybe wx is getting the locale from gettext?! Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773579: fontypython should be ported to wx 3.0 (yes, again)
Package: fontypython Version: 0.4.4-1.2 Severity: grave When I fixed #765487, I missed #757886, that is, the fact that the transition from 2.8 to 3.0 (of fontypython) had not been spontaneous. As a consequence of this, I assumed Depends were OK, which they are not, and the current package is useless. As a consequence of this (probably), I also missed #755757. (applause) So using wx 2.8 is not an option in jessie, and the original bug must be solved. Olly, in #757886 you state that everything seems to be fine... can you confirm with wxpython3.0 3.0.1.1+dfsg-2 ? -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fontypython depends on: ii python-imaging 2.6.1-1 ii python-wxgtk3.0 3.0.1.1+dfsg-2 fontypython recommends no packages. fontypython 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#773579: fontypython should be ported to wx 3.0 (yes, again)
Il giorno sab, 20/12/2014 alle 10.37 +, Olly Betts ha scritto: On Sat, Dec 20, 2014 at 10:10:53AM +0100, Pietro Battiston wrote: When I fixed #765487, I missed #757886, that is, the fact that the transition from 2.8 to 3.0 (of fontypython) had not been spontaneous. As a consequence of this, I assumed Depends were OK, which they are not, and the current package is useless. As a consequence of this (probably), I also missed #755757. (applause) So using wx 2.8 is not an option in jessie, and the original bug must be solved. Or we don't release jessie with fontypython - you say in #765487 that it seems pretty abandoned upstream. It does seem like people are actually still using it though, judging from the comments in that ticket. I'm reluctant for three reasons: 1) I and other people (a niche, but a stable niche, and if I don't misinterpret popcon, its 0.03% of active users locate it in the top 10% of debian packages) use it 2) to the best of my knowledge, there are no alternatives (i.e. programs allowing to install a font without admin powers or messing with shell/hidden files), 3) it works flawlessly with wx 2.8, and I expect the fix for 3.0 to be easy. Olly, in #757886 you state that everything seems to be fine... can you confirm with wxpython3.0 3.0.1.1+dfsg-2 ? Will retest it when I have a suitable machine in front of me. But the error messages in #765487 do seem to indicate how to solve the problem: .../src/common/stdpbase.cpp(62): assert traits failed in Get(): create wxApp before calling this i.e. make sure that the wxApp object is created before this code gets called. This is easily fixed.¹ I will try to also fix the rest,¹ but since you reported fontypython working with wx 3.0, and since I am not a wx expert, I was wondering whether only some systems were affected, and why. Pietro ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765487#25 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773525: Randomly excludes available connections [when there are too many?]
Package: network-manager Version: 0.9.10.0-4 Severity: grave Copypasted from a shell: pietro@debiousci:~$ for i in `seq 1 10`; do nmcli c | wc; done 127 637 12827 127 637 12827 127 627 12827 126 628 12726 127 629 12573 127 634 12828 127 629 12827 127 630 12319 127 631 12827 127 627 12827 I am clearly not changing my list of available connections (so quick!). So what is happening is that network-manager is dropping some of my registered connections, in a random way. Initially I though it is unable to handle more than 127, but then I saw that sometimes it only lists 126. The output of nmcli c is otherwise almost sane (see below). Some connections show up more frequently, some less. Consider for instance: pietro@debiousci:~$ for i in `seq 1 10`; do nmcli c | grep -i condividi; done | sort Condividi 8a006f93-95ac-4683-a683-56413cbb95bb 802-3-ethernet -- Condividi 8a006f93-95ac-4683-a683-56413cbb95bb 802-3-ethernet -- Condividi 8a006f93-95ac-4683-a683-56413cbb95bb 802-3-ethernet -- Condividi cab18fac-376f-42cf-9349-d9b4170dacce 802-3-ethernet -- condividi con dnsmasq d54c2a91-f654-4d52-bdbd-cf9d8efdd9e5 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- condividi daa501b5-87eb-4a3f-a6d5-4fa73d042a66 802-3-ethernet -- So - one connection, Condividi, is shown 3 times out of 10 - one connection, condividi con dnsmasq, is shown 1 time only - one connection, condividi, is shown most of the times... with different space paddings Different runs of the above command will clearly give different results, but some connections are indeed more rare - i.e. condividi con dnsmasq usually shows in none of the 10 tries - and some exhibit (even more than 2) different space paddings. The wireless connection I need to use at work shows up more or less once every 100 tries. Which, by the way, is very annoying: it usually disables autoconnect, makes it virtually impossible to use gnome-control-center (or the GNOME 3 drop-down menu) to connect, and makes it very hard and time consuming also with nmcli c up (nm-connection-editor is also affected). This is why the bug is grave: in particular, if a remote server relies on network-manager in order to connect at startup... you'd better hope it is not too remote. The bug was present also with 0.9.10.0-3. My rough guess is that the problematic upgrade was located between July and September. P.S: just for info: _most_ of the connections are dropped: pietro@debiousci:~$ ls /etc/NetworkManager/system-connections | wc 431 8918594 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.12-1 ii init-system-helpers1.22 ii isc-dhcp-client4.3.1-5 ii libc6 2.19-13 ii libdbus-1-31.8.12-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-5 ii libgudev-1.0-0 215-7 ii libmm-glib01.4.0-1 ii libndp01.4-2 ii libnewt0.520.52.17-1+b1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-3 ii libnm-util20.9.10.0-3 ii libpam-systemd 215-7 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b1 ii libsoup2.4-1 2.48.0-1 ii libsystemd0215-7 ii libteamdctl0 1.12-1 ii libuuid1 2.25.2-3 ii lsb-base 4.1+Debian13+nmu1 ii policykit-10.105-8 ii udev 215-7 ii wpasupplicant 2.3-1 Versions of packages network-manager recommends:
Bug#768134: Plugin does not work with gedit 3.8
Il giorno dom, 23/11/2014 alle 14.07 +0100, Tobias Frost ha scritto: Package: gedit-latex-plugin Followup-For: Bug #768134 Control: tags -1 pending Hi Pietro, I read your last message as a pending is warranted... (Please remove it again when I'm wrong...) Right, thanks! Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768134: Ready...
3.8.0-2 is ready... http://anonscm.debian.org/cgit/collab-maint/gedit-latex.git/log/ I'm just waiting a couple of days to see if #768134 gets fixed, then I will upload in any case. Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768134: Plugin does not work with gedit 3.8
Package: gedit-latex-plugin Version: 3.8.0-1 Severity: grave The last upstream release of the plugin, 3.8, is totally useless with gedit (3.12 and) 3.14, which jessie ships. I did fix this however in upstream git, making the plugin work again: https://git.gnome.org/browse/gedit-latex/commit/?id=9cb413d78d363d47a03bd30984cfadea79220df2 but was not able to have a new version released and into sid in time. I will soon upload 3.8.0-2, including the patch which updates the interface (together with a patch only introducing language updates, and updated dependences solving bug #740222), and ask for a freeze exception. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gedit-latex-plugin depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gedit3.14.0-2 ii gvfs-bin 1.22.0-1+b1 ii python-poppler 0.12.1-8.1 ii python3 3.4.1-1 ii python3-dbus 1.2.0-2+b3 ii rubber 1.1+20100306-6 Versions of packages gedit-latex-plugin recommends: pn python-enchant none pn texlive none gedit-latex-plugin 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#765371: Import fails - error parsing version (fixed upstream)
Package: python-ow Version: 2.9p5-1 Severity: grave Trying to import ow results in pietro@debiousci:~$ python -c import ow Traceback (most recent call last): File string, line 1, in module File /usr/lib/python2.7/dist-packages/ow/__init__.py, line 37, in module __version__ = _OW.version( ) + '-%s' % '$Id$'.split( )[ 2 ] IndexError: list index out of range The line which gives an error... couldn't really do otherwise. The problem comes from the fact that while in previous upstream versions that line looked like __version__ = _OW.version( ) + '-%s' % '$Id: __init__.py,v 1.19 2013/03/24 01:23:30 alfille Exp $'.split( )[ 2 ] , this was changed probably through an automatic replacement which broke owpython in version 2.9p5. The same applies to ownet. Attached is a patch which fixes both. Notice that both are also fixed upstream in version 2.9p7 (exactly in the same way as my patch). So the optimal fix would be to simply package it. But if this can't be done in reasonable time, I could (push 2.9p5-1.1 to collab-maint, and) try to get a new NMU sponsored with my simple patch applied. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-ow depends on: ii libc62.19-11 ii libow-2.9-5 2.9p5-1.1 ii python 2.7.8-1 python-ow recommends no packages. python-ow suggests no packages. -- no debconf information commit 64222f5788c664c15bb0f980ed170be1405c308c Author: Pietro Battiston m...@pietrobattiston.it Date: Tue Oct 14 14:32:29 2014 +0200 Only return the OW version diff --git a/debian/patches/only-return-the-OW-version.patch b/debian/patches/only-return-the-OW-version.patch new file mode 100644 index 000..3c040be --- /dev/null +++ b/debian/patches/only-return-the-OW-version.patch @@ -0,0 +1,25 @@ +From: Pietro Battiston m...@pietrobattiston.it +Date: Tue, 14 Oct 2014 14:29:13 +0200 +Subject: Only return the OW version. + +The python files are currently installed without replacing some +placeholders such as $Id$. As a consequence, the parsing (split()) +of the version number fails. This horrible hack simply disables it, +until the real fix is implemented. +--- + module/swig/python/ow/__init__.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/module/swig/python/ow/__init__.py b/module/swig/python/ow/__init__.py +index 0ed9dfd..84bc115 100644 +--- a/module/swig/python/ow/__init__.py b/module/swig/python/ow/__init__.py +@@ -34,7 +34,7 @@ from ow import _OW + + __author__ = 'Peter Kropf' + __email__ = 'pkr...@gmail.com' +-__version__ = _OW.version( ) + '-%s' % '$Id$'.split( )[ 2 ] ++__version__ = _OW.version( ) + + + # diff --git a/debian/patches/series b/debian/patches/series index 494f101..f0fe969 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -7,3 +7,4 @@ deb-specific_python-install.patch deb_specific__owfs-use-config.patch for-upstream_fix-ABI.patch for-upstream_owexist-manpage.patch +only-return-the-OW-version.patch
Bug#735822: Patch: fixed sphinx documentation build path
Il giorno sab, 31/05/2014 alle 12.07 +0200, Domenico Iezzi ha scritto: Hi, FTBFS can be fixed by changing doc/build/sphinx/html to build/sphinx/html in debian/python-sqlkit-doc.docs Regards, Domenico Iezzi Hi Domenico, thanks a lot for your patch. Unfortunately I am very busy at the moment, but I should be able to take care of this package at the latest in July. By the way, I wouldn't object to an NMU. Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748545: Does not work - starts, but does nothing
Package: gxtuner Version: 2.1-1 Severity: critical The window regularly opens, but the program never shows any activity. Nothing is written to the terminal. The two buttons allow me to change the level of threshold and reference pitch, but nothing changes. (on the same system, at the same time and with the same connections, jmeters correctly shows the volume of the audio input, and zita-at1 even works as a rough tuner) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gxtuner depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.18-5 ii libcairo2 1.12.16-2 ii libfftw3-single3 3.3.4-1 ii libfontconfig12.11.0-5 ii libfreetype6 2.5.2-1 ii libgcc1 1:4.9.0-2 ii libgdk-pixbuf2.0-02.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.23-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.9.5+20140404git3d7c67dc~dfsg-1 ii libpango-1.0-01.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-0 1.36.3-1 ii libstdc++64.9.0-2 ii libx11-6 2:1.6.2-1 ii libzita-resampler11.3.0-2 gxtuner recommends no packages. gxtuner 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#725372: python-sqlkit should depend on python-babel, and not python-pybabel anymore
Hi Thomas, I had already switched to python-babel in my packaging git repo, I will upload a new version as soon as possible. Pietro Il giorno sab, 05/10/2013 alle 02.55 +0800, Thomas Goirand ha scritto: Package: python-sqlkit Version: 0.9.5-1 Severity: serious Hi, I would like to remove python-pybabel from the archive, as this is a transitional package. Please switch to python-pybabel for your dependency. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718078: Bug#717680: gvb: Update help handling for python-distutils-extra 2.38
Hi Martin, I did have fixing those bugs in my TODO list, but those are a couple of critical months for me on the non-Debian side, so thank you very much for the NMU. Pietro Il giorno gio, 29/08/2013 alle 08.29 +0200, Martin Pitt ha scritto: tag 717680 pending tag 718078 pending thanks Hello Jeremy, Jeremy Bicha [2013-07-23 14:05 -0400]: python-distuils-extra 2.38-1 was uploaded yesterday and changes the behavior of build_help.py. http://packages.qa.debian.org/p/python-distutils-extra/news/20130722T160301Z.html I'm attaching a patch to update gvb for these changes. I also took the liberty of updating the packaging a bit: switched to quilt patches instead of dpatch, switched to dh_python2 (since python-support will probably be dropped during the Jessie cycle anyway). This is a looong overdue packaging modernization and I think it's entirely adequate at this point even for an NMU. It also fixes the FTBFS RC bug #718078. I uploaded your debdiff to DELAYED/7 with a few modifications: * UNRELEASED - unstable * Use an NMU version number and mention NMU in changelog * Close #718078 Attaching final debdiff. Thank you! Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650856: closing 650856
Il giorno mar, 10/04/2012 alle 22.52 +0200, Laurent Bigonville ha scritto: So this cannot be reproduced anymore, upstream think it could be a GTK+ issue. Sorry for disappearing: the requests for additional tests got lost in my flood of mail, but I confirm the problem is solved. Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666655: python-shapely: FTBFS: tests failed
severity 55 minor thanks == FAIL: /«PKGBUILDDIR»/shapely/tests/cascaded_union.txt Doctest: cascaded_union.txt -- Traceback (most recent call last): File /usr/lib/python2.7/doctest.py, line 2201, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for cascaded_union.txt File /«PKGBUILDDIR»/shapely/tests/cascaded_union.txt, line 0 -- File /«PKGBUILDDIR»/shapely/tests/cascaded_union.txt, line 22, in cascaded_union.txt Failed example: cascaded_union(spots) # doctest: +ELLIPSIS Expected: shapely.geometry.multipolygon.MultiPolygon object at 0x... Got: shapely.geometry.polygon.Polygon object at 0x307ff50 The bug is in the random generator of the buildd... OK, joking: the failed test includes scattering some random points and verify that the patches built around them form a MultiPolygon: it will sometimes (rarely) fail because they build a (connected) Polygon. I'll solve that on next upload, but for the moment I'm lowering severity. Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650856: Crash on restore GUI startup
Il giorno gio, 08/12/2011 alle 12.43 +0100, Jose Carlos Garcia Sogo ha scritto: On Sun, Dec 4, 2011 at 1:06 AM, Pietro Battiston m...@pietrobattiston.it wrote: [...] At the end of this email is the output when ran in gdb, including a backtrace. Could you install deja-dup-dbg package Uhm... but that's what I did since the first moment! pietro@debiousci:~$ LANG=C apt-cache policy deja-dup-dbg deja-dup-dbg: Installed: 20.2-1 Candidate: 20.2-1.1 Version table: 20.2-1.1 0 600 http://ftp.it.debian.org/debian/ unstable/main amd64 Packages *** 20.2-1 0 100 /var/lib/dpkg/status 14.2-1squeeze1 0 500 http://ftp.it.debian.org/debian/ squeeze/main amd64 Packages That said, I noticed some strings in my previous mail were in Italian, so a new gdb output follows. Pietro ~$ LANG=C gdb deja-dup GNU gdb (GDB) 7.3-debian Copyright (C) 2011 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. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/deja-dup...Reading symbols from /usr/lib/debug/usr/bin/deja-dup...done. done. (gdb) r --restore Starting program: /usr/bin/deja-dup --restore [Thread debugging using libthread_db enabled] [New Thread 0x7fffee350700 (LWP 8151)] [New Thread 0x7fffedb4f700 (LWP 8152)] [New Thread 0x7fffde45a700 (LWP 8154)] [New Thread 0x7fffdda44700 (LWP 8156)] [New Thread 0x7fffdd243700 (LWP 8157)] [New Thread 0x7fffdca42700 (LWP 8158)] Program received signal SIGFPE, Arithmetic exception. 0x778db217 in gtk_grid_request_allocate (request=0x7fffdbb0, orientation=optimized out, total_size=0) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c:951 951 /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c: No such file or directory. in /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c (gdb) backtrace #0 0x778db217 in gtk_grid_request_allocate (request=0x7fffdbb0, orientation=optimized out, total_size=0) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c:951 #1 0x778dba01 in gtk_grid_get_size_for_size (grid=optimized out, orientation=GTK_ORIENTATION_VERTICAL, size=0, minimum=0x7fffdc8c, natural=0x7fffdc90) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c:1094 #2 0x77981af0 in compute_size_for_orientation (widget=0x9f6c10, orientation=GTK_SIZE_GROUP_VERTICAL, for_size=-1, minimum_size=0x7fffdd08, natural_size=0x7fffdd0c) at /build/buildd-gtk +3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtksizerequest.c:248 #3 0x778db8ed in gtk_grid_request_non_spanning (contextual=0, orientation=GTK_ORIENTATION_VERTICAL, request=0x7fffddb0) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c:628 #4 gtk_grid_request_run (request=0x7fffddb0, orientation=GTK_ORIENTATION_VERTICAL, contextual=0) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c:915 #5 0x778dbab3 in gtk_grid_get_size (grid=optimized out, orientation=GTK_ORIENTATION_VERTICAL, minimum=0x7fffde7c, natural=0x7fffde80) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtkgrid.c:1068 #6 0x77981af0 in compute_size_for_orientation (widget=0x9f6a10, orientation=GTK_SIZE_GROUP_VERTICAL, for_size=-1, minimum_size=0x7fffded8, natural_size=0x7fffdedc) at /build/buildd-gtk +3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtksizerequest.c:248 #7 0x77981dfa in gtk_widget_get_preferred_size (widget=0x9f6a10, minimum_size=0x0, natural_size=0x7fffdf00) at /build/buildd-gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk +3.0-3.0.12/./gtk/gtksizerequest.c:545 #8 0x00417bce in assistant_reset_size (self=0x74c040, page=0x9f6a10) at Assistant.c:772 #9 0x00418e24 in assistant_append_page (self=0x74c040, page=0x9f6a10, type=optimized out) at Assistant.c:750 #10 0x0041e117 in assistant_operation_add_confirm_page (self=0x74c040) at AssistantOperation.c:1058 #11 assistant_operation_constructor (type=optimized out, n_construct_properties=optimized out, construct_properties=optimized out) at AssistantOperation.c:1966 #12 0x00421147 in assistant_restore_constructor (type=7038112, n_construct_properties=3, construct_properties=0x70c6f0) at AssistantRestore.c:1420 #13 0x759615f4 in g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x759627ec in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x00420c06 in assistant_restore_construct_with_files
Bug#650856: Crash on restore GUI startup
Package: deja-dup Version: 20.2-1 Severity: grave Deja-dup just crashes when started with the --restore argument. Backup instead works fine. At the end of this email is the output when ran in gdb, including a backtrace. As far as I can tell, that could also just be a bug in libgtk... I don't think that matters, but I'm running GNOME 3 fallback. Pietro ~$ gdb deja-dup GNU gdb (GDB) 7.3-debian Copyright (C) 2011 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. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/deja-dup...Reading symbols from /usr/lib/debug/usr/bin/deja-dup...done. done. (gdb) deja-dup --restore Undefined command: deja-dup. Try help. (gdb) r --restore Starting program: /usr/bin/deja-dup --restore [Thread debugging using libthread_db enabled] [New Thread 0x7fffee2ca700 (LWP 4724)] [New Thread 0x7fffedac9700 (LWP 4725)] [New Thread 0x7fffde45a700 (LWP 4727)] [New Thread 0x7fffdda44700 (LWP 4729)] [New Thread 0x7fffdd243700 (LWP 4730)] [New Thread 0x7fffdca42700 (LWP 4731)] [New Thread 0x7fffdc241700 (LWP 4732)] [New Thread 0x7fffdba40700 (LWP 4733)] [New Thread 0x7fffdb23f700 (LWP 4734)] [New Thread 0x7fffdaa3e700 (LWP 4735)] [New Thread 0x7fffda23d700 (LWP 4736)] Program received signal SIGFPE, Arithmetic exception. 0x778db217 in gtk_grid_request_allocate (request=0x7fffdbb0, orientation=optimized out, total_size=0) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c:951 951 /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c: File o directory non esistente. in /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c (gdb) backtrace #0 0x778db217 in gtk_grid_request_allocate (request=0x7fffdbb0, orientation=optimized out, total_size=0) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c:951 #1 0x778dba01 in gtk_grid_get_size_for_size (grid=optimized out, orientation=GTK_ORIENTATION_VERTICAL, size=0, minimum=0x7fffdc8c, natural=0x7fffdc90) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c:1094 #2 0x77981af0 in compute_size_for_orientation (widget=0xaf2c20, orientation=GTK_SIZE_GROUP_VERTICAL, for_size=-1, minimum_size=0x7fffdd08, natural_size=0x7fffdd0c) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtksizerequest.c:248 #3 0x778db8ed in gtk_grid_request_non_spanning (contextual=0, orientation=GTK_ORIENTATION_VERTICAL, request=0x7fffddb0) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c:628 #4 gtk_grid_request_run (request=0x7fffddb0, orientation=GTK_ORIENTATION_VERTICAL, contextual=0) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c:915 #5 0x778dbab3 in gtk_grid_get_size (grid=optimized out, orientation=GTK_ORIENTATION_VERTICAL, minimum=0x7fffde7c, natural=0x7fffde80) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtkgrid.c:1068 #6 0x77981af0 in compute_size_for_orientation (widget=0xaf2a20, orientation=GTK_SIZE_GROUP_VERTICAL, for_size=-1, minimum_size=0x7fffded8, natural_size=0x7fffdedc) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtksizerequest.c:248 #7 0x77981dfa in gtk_widget_get_preferred_size (widget=0xaf2a20, minimum_size=0x0, natural_size=0x7fffdf00) at /build/buildd- gtk+3.0_3.0.12-2-amd64-rEYsqr/gtk+3.0-3.0.12/./gtk/gtksizerequest.c:545 #8 0x00417bce in assistant_reset_size (self=0x762030, page=0xaf2a20) at Assistant.c:772 #9 0x00418e24 in assistant_append_page (self=0x762030, page=0xaf2a20, type=optimized out) at Assistant.c:750 #10 0x0041e117 in assistant_operation_add_confirm_page (self=0x762030) at AssistantOperation.c:1058 #11 assistant_operation_constructor (type=optimized out, n_construct_properties=optimized out, construct_properties=optimized out) at AssistantOperation.c:1966 #12 0x00421147 in assistant_restore_constructor (type=7720624, n_construct_properties=3, construct_properties=0x75dae0) at AssistantRestore.c:1420 #13 0x759615f4 in g_object_newv () from /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0 #14 0x759627ec in g_object_new () from /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0 #15 0x00420c06 in assistant_restore_construct_with_files (object_type=optimized out, files=0x0) at AssistantRestore.c:323 #16 0x00429117 in deja_dup_app_main (args=0x7fffe358, args_length1=1) at main.c:333 #17 0x748a0ead in __libc_start_main () from
Bug#637312: Modified package
A working package with the fix suggested by Paul is here: http://mentors.debian.net/package/deja-dup with that I don't mean it's time/I'm entitled for a NMU (though some ETA on producing the ETA would be appreciated - that's maybe the most popular desktop backup software, and it's uninstallable); just that people who get in trouble as me with not being able to backup/restore can run in a terminal: dget\ http://mentors.debian.net/debian/pool/main/d/deja-dup/deja-dup_18.1.1-2.2.dsc dpkg-source -x deja-dup_18.1.1-2.2.dsc cd deja-dup-18.1.1/ dpkg-buildpackage sudo dpkg -i ../deja-dup_18.1.1-2.2_amd64.deb bye Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618898: Wrong link
Sorry, in the above description I linked to the wrong bug: the right one is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614192 Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617637: FTBFS (because of linker changes?)
Package: xournal Version: 0.4.5-2 Severity: serious Justification: fails to build from source Xournal currently FTBFS. Here is the relevant part of the build log: [...] gcc -Wall -g -O2 -Wl,--as-needed -o xournal main.o xo-misc.o xo-file.o xo- paint.o xo-print.o xo-support.o xo-interface.o xo-callbacks.o xo-shapes.o ttsubset/libttsubset.a -pthread -lgnomecanvas-2 -lart_lgpl_2 -lgtk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lfreetype -lfontconfig -lpoppler-glib -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 /usr/bin/ld: xo-file.o: undefined reference to symbol 'XUngrabButton' /usr/bin/ld: note: 'XUngrabButton' is defined in DSO /usr/lib64/libX11.so.6 so try adding it to the linker command line /usr/lib64/libX11.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[4]: *** [xournal] Error 1 make[4]: Leaving directory `/home/pietro/cancellami/riprovo/xournal-0.4.5/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/pietro/cancellami/riprovo/xournal-0.4.5/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/pietro/cancellami/riprovo/xournal-0.4.5' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/pietro/cancellami/riprovo/xournal-0.4.5' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Notice the same problem is mentioned here: https://wiki.kubuntu.org/ScottHoward/FTBFSreport and implicitly here: http://www.novarata.net/mootbot/ubuntu-meeting.log.20101210_1000.html as several hundred unbuildable packages due to linker changes. Pietro -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xournal depends on: ii ghostscript-x 8.71~dfsg2-10 The GPL Ghostscript PostScript/PDF ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.28.1-1+b1 The GLib library of C routines ii libgnomecanvas2-0 2.30.1-1 A powerful object-oriented display ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libpango1.0-0 1.28.3-1+squeeze1 Layout and rendering of internatio ii libpoppler-glib4 0.12.4-1.2PDF rendering library (GLib-based ii libx11-6 2:1.4.1-5 X11 client-side library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime xournal recommends no packages. xournal 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#598463: Alive
Il giorno ven, 12/11/2010 alle 13.46 +0100, Moritz Muehlenhoff ha scritto: On Mon, Nov 08, 2010 at 11:08:38AM +0100, Pietro Battiston wrote: I didn't forget this, it's just harder than I thought, in particular considering I have no cloud computing experience and account. I'm still committed to fix it (and also asked for help upstream), but have no precise idea of the time it will take. In particular, any help is appreciated. This appears to be still unfixed in current 0.4 and should be reported/ fixed upstream. Given that libcloud is already outdated, has no reverse deps and virtually no users in popcon, we should remove it from Squeeze. Please (not just you, possibly anyone who can test it), just check [1], then decide freely - I'm not necessarily against removing it, but it's apparently not that hard to keep it. bye Pietro [1]: http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201011.mbox/%3c1289241616.27934.29.ca...@voubian.casa%3e signature.asc Description: This is a digitally signed message part
Bug#598463: Alive
I didn't forget this, it's just harder than I thought, in particular considering I have no cloud computing experience and account. I'm still committed to fix it (and also asked for help upstream), but have no precise idea of the time it will take. In particular, any help is appreciated. Pietro signature.asc Description: This is a digitally signed message part
Bug#598463: I can do that
Il giorno dom, 31/10/2010 alle 21.01 +0100, Moritz Muehlenhoff ha scritto: On Thu, Oct 21, 2010 at 09:57:50AM +0200, Pietro Battiston wrote: I wrote Soren 8 days ago informing him that I could take of that. I'll soon submit a patch. What's the status? That I'll soon submit a patch. OK, let's say 1 week as worst case expectation - but if someone else wants to do it before, no problem. Otherwise, please let me know if the patch should be a complete debdiff for NMU. Pietro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598463: I can do that
I wrote Soren 8 days ago informing him that I could take of that. I'll soon submit a patch. Pietro signature.asc Description: This is a digitally signed message part
Bug#535357: Fixed upstream
As far as I can tell,
1) this is fixed upstream
http://trac.sagemath.org/sage_trac/attachment/ticket/6927/6927-disk_cache-ref.patch
(and in the last upstream release)
2) the (upstream) patched file is the only one currently importing
processing ( sage/parallel/decorate.py already imports multiprocessing).
So once the upstream fix is imported (for convenience, I'm attaching a
stripped patch which, if saved to debian/spkg-patches/sage , should
apply only the desired change), the dependency can be dropped (and the
bug closed).
Assuming that's really a drop-in replacement, of course: I tried to
build and verified the patch does compile, but space on device ended
before finishing compilation, so I couldn't test the package.
Pietro
diff -ur sage-3.0.5/sage/parallel/multiprocessing.py sage-3.0.5_p/sage/parallel/multiprocessing.py
--- sage-3.0.5/sage/parallel/multiprocessing.py 2010-02-17 15:58:32.0 +0100
+++ sage-3.0.5_p/sage/parallel/multiprocessing.py 2010-02-17 16:17:28.0 +0100
@@ -11,7 +11,9 @@
# http://www.gnu.org/licenses/
-from processing import Pool
+from __future__ import absolute_import
+
+import multiprocessing
from functools import partial
from sage.misc.fpickle import pickle_function, call_pickled_function
import ncpus
@@ -59,7 +61,7 @@
[(((2,), {}), 4), (((3,), {}), 6)]
if processes == 0: processes = ncpus.ncpus()
-p = Pool(processes)
+p = multiprocessing.Pool(processes)
fp = pickle_function(f)
result = p.imapUnordered(call_pickled_function, [ (fp, t) for t in inputs ])
signature.asc
Description: Questa è una parte del messaggio firmata digitalmente
Bug#555713: jokosher: No real hint that Jokosher is GPL 2+
Package: jokosher Version: 0.11.3-1 Severity: serious Justification: Policy 12.5 I think I checked the Jokosher tarball throughly, and found absolutely no reference to the fact that Jokosher would be GPL v. 2+. debian/copyright instead states so. Now: it's true that the GPL itself states that a GPL covered software not precising which version of the GPL applies can be assumed being released under any desired one (and notice I still wouldn't understand why really 2+). However, most files in Jokosher _do_ refer to the file COPYING, which contains the GPL 2, so I think this is a very clear reference to 2 (and not to 2+). Notice that file Jokosher/elements/singledecodebin.py _is_ GPL 2+, but it's taken from another project, so I wouldn't take it as a proof of 2+-ness of the whole program. This particular file is an exception... also missing in debian/copyright. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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#505554: drgeo: sistematically segfaults if rebuilt in unstable
Package: drgeo Version: 1.1.0-1 Severity: grave Tags: patch Justification: renders package unusable drgeo 1.1.0-1 actually seems to work, in Lenny, just by luck, but if recompiled with a more modern gcc, i.e. the one found in Sid (or in Ubuntu Intrepid), it sistematically segfaults. The bug is known upstream and has been solved in CVS, but still not in the upstream release. The corresponding Launchpad bug, LP #257797, has both a minimal patch and a debdiff for the Ubuntu version; I can provide a debdiff for Debian if it is appreciated. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-486 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
