Bug#949162: pyspread: pyspread does not start
I am sorry, I must have made a typo while testing before uploading. The bug was already fixed in the git repo, I have uploaded a fixed package now. Test still fail though, still trying to figure out how to make them run. Andreas fre. 17. jan. 2020 kl. 16:30 skrev Salman Mohammadi : > > Package: pyspread > Version: 1.99.0.1-1 > Severity: grave > > Dear Maintainer, > > After installing pysread I cannot run it. I get the following message > when I try to run the software from terminal: > > > Traceback (most recent call last): > File "/usr/bin/pyspread", line 58, in > from src.workflows import Workflows > File "/usr/share/pyspread/src/workflows.py", line 55, in > from src.dialogs import DiscardChangesDialog, FileOpenDialog, > GridShapeDialog > File "/usr/share/pyspread/src/dialogs.py", line 1377, in > class TutorialDialog(HelpDialogBase): > File "/usr/share/pyspread/src/dialogs.py", line 1381, in TutorialDialog > baseurl = str(path.parent) + '/' > AttributeError: 'str' object has no attribute 'parent' > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages pyspread depends on: > ii python3 3.7.5-3 > ii python3-numpy 1:1.17.4-5 > ii python3-pyqt5 5.14.1+dfsg-2 > ii python3-pyqt5.qtsvg 5.14.1+dfsg-2 > > Versions of packages pyspread recommends: > ii python3-enchant 2.0.0-2 > ii python3-matplotlib 3.1.2-1 > > pyspread suggests no packages. > > -- no debconf information >
Bug#875176: [scantailor] Future Qt4 removal from Buster
The package for scantailor-advanced is almost done. Since I'm only a DM I'd need a sponsor for the first upload and (hopefully) someone to grant me upload privileges for later revisions. I'll wait for the next upstream release before pushing for a upload. I have currently packaged for a pre-release. Andreas ons. 25. sep. 2019 kl. 20:03 skrev Moritz Mühlenhoff : > On Tue, Sep 24, 2019 at 03:39:47PM -0600, Jason Crain wrote: > > On Tue, Sep 24, 2019 at 10:54:01PM +0200, Moritz Mühlenhoff wrote: > > > per Github issue 121 there's no current activity to port scantailor to > > > Qt5. Are you planning to switch to the scantailor-advanced fork? > Otherwise > > > let's remove it, we're now moving forward with removal of Qt4 from > Debian > > > (and all non-ported reverse dependencies left) > > > > I will not be working on it, but Andreas Noteng has an ITP for > > scantailor-advanced (https://bugs.debian.org/940329), which I suggested > > could be a "Replaces" for scantailor. > > Ack, filing a removal bug, then. There's still a lot of time to > package scantailor-advanced before bullseye freezes. > > Cheers, > Moritz >
Bug#767567: bashburn: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/bashburn.1.gz
... diff -Nru bashburn-3.0.1/debian/changelog bashburn-3.0.1/debian/changelog --- bashburn-3.0.1/debian/changelog 2011-06-25 23:17:11.0 +0200 +++ bashburn-3.0.1/debian/changelog 2014-11-03 19:13:52.0 +0100 @@ -1,3 +1,11 @@ +bashburn (3.0.1-1+deb7u1) wheezy; urgency=medium + + * Add Conflicts/Replaces: mybashburn to resolve a file conflict. +mybashburn from squeeze has been superseded by bashburn in wheezy, +but both used the same manpage. (Closes: #767567) + + -- Andreas Noteng andr...@noteng.no Mon, 03 Nov 2014 19:09:17 +0100 + bashburn (3.0.1-1) unstable; urgency=low * Initial release (Closes: #497092) diff -Nru bashburn-3.0.1/debian/control bashburn-3.0.1/debian/control --- bashburn-3.0.1/debian/control 2011-06-25 23:17:11.0 +0200 +++ bashburn-3.0.1/debian/control 2014-11-02 23:05:34.0 +0100 @@ -10,6 +10,8 @@ Package: bashburn Architecture: all +Replaces: mybashburn +Conflicts: mybashburn Depends: ${shlibs:Depends}, ${misc:Depends}, bash (= 3.0), cdrdao, wodim, dvd+rw-tools, cdparanoia, vorbis-tools, flac, eject, normalize-audio, mpg123, sudo, genisoimage Description: simplify cd/dvd burning at the command line signature.asc Description: OpenPGP digital signature
Bug#767567: bashburn: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/bashburn.1.gz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Den 03. nov. 2014 18:55, skrev Andreas Beckmann: On 2014-11-03 18:09, Andreas Noteng wrote: Den 02. nov. 2014 18:53, skrev Andreas Beckmann: I'll sponsor your uploads. If you want a review, send me (and this bug) source debdiffs. Looks like stable upload was approved. Attached is the debdiff. where did you get the idea of approval? Don't know, must have seen the closing of the dupe bug. the version should be 3.0.1-1+deb7u1, not -2 Fixed. It makes sense, but is this documented somewhere? I have done updates to released packages in Ubuntu before, but this is the first time I update anything outside of unstable in Debian. and be a bit more elaborate in the changelog entry Add Conflicts/Replaces: mybashburn to resolve a file conflict. mybashburn from squeeze has been superseded by bashburn in wheezy, but both used the same manpage. (Closes:... and target wheezy not stable Done. Thanks for your patience :-) Debdiff between the package currently in testing and the 3.1.0-1 is also attached, still awaiting unblock for that one. two weeks earlier would have been easier :-) Yea, I know. Should have uploaded it two years ago. There doesn't seem to be much activity upstream, so I guess this page will eventually go away. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUV8mrAAoJELRG7qgympRa774QAKn/6YQGvEn5wZeeYylwGMqX okGZt6vf202JhrWQSqrw/jFwtH3VFwNkpfZ3k2rjpj6OxgnFLPOnpfphkT1ChieM 7WlZO8HC/J2Whrj+16hCSssCI+aiTUoxeFI89X9ovZ+LPr/zDoc1KZkwAeN7oZ0Z hJ5fK6oSx9Rv12IZZGnbPY3md7QZVqEI1GrVNXcvs7AjDuatYqyuU0hGSoZfPGLc WHd09xNmfPuHOllYht91GN/UeANouofmDM3dYgsnUSpjav2H3Kl0R53WeWqdV17O hojcVLpHlKpRnonbeiJFKzUv4mUm6JMCaECcakKyOC+tPjL/kmKK0sRetMFYa/Ri 94VUPHwE2K1Kj5eds81A3WOGT5u9wlSWnaP8RLgCQGZbB6To6uarovHWH/pm4WLr qeo6M/n5Xsp4Slr105Y6KtEZLlqtdbnwJKAZdk2HVqLofmG0QPjMzFYaoknZQt/O NgjxFBAsu/GHkZdhQbsEfMw92iZEuUHomZZcsj0G7f9DQDf7me2TvFmCleE2gM2i YPHyQd1SssL+m00Bz0Pb8WKt7U0IZodKXEfw1Tme7XwskQVrRHL9jztmx9QivE0/ dMR3l4OpdaVQYoN36tpx9FxiocSRLdJAV0/R45Pbyl4Ni5ICQSuLlOgkcLRpMjXY VxxKG1uEgPKtpe7B9AEq =yPZ5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767567: bashburn: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/bashburn.1.gz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Den 03. nov. 2014 20:13, skrev Andreas Beckmann: On 2014-11-03 20:04, Adam D. Barratt wrote: That might be true if the fix could wait until the next stable point release (unplanned yet, but at the earliest in mid-December). Aside from anything else, at least this SRM will be following standard procedure and not acking the wheezy fix until at least unstable is fixed in any case. Unstable/jessie would not really need that fix (it's a squeeze-wheezy upgrade issue), but it won't harm :-) @Andreas Noteng: So lets get the fix into sid. Same changelog as for 3.0.1-1+deb7u1, but version it again as 3.0.1-2 and target unstable. Upload to mentors and send me the link to the .dsc http://mentors.debian.net/debian/pool/main/b/bashburn/bashburn_3.0.1-2.dsc Not sure if the (Closes: #) should still be in the changelog though. If the package gets uploaded to unstable before stable it would prematurely close the bug.. Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUV9dEAAoJELRG7qgympRaLHwP/jjFrAzYPjqXymbY6VZq0ah0 C3sAXgSMcKhS6lLXjX1SWdPICFRcG4n9Q1rPDZ5Q68RB8KQKJYbaV2wwCPUUMhFE BnU04dtbeA6/7JB+YfCi9eNGl1KQtJxqIINDSSX7DIg8Lp8f07kPcE+rxz0Gpv6i SK3K+jVL+vS+eA2Tt/MREzL+ewiTMJo622/a+TxxSVM/GlOXx8XMrDA/6ctLPA/L +rh+rUNBRwuqcF/hPmBHRSATv5cCZ3edWApBlr+lCHHeY7ulAd4uLAb3X54Y8wHW cxts/7F/q75egaceKGJQFmDk69ixQletP7Ui5JtbmFkaKP9YQWoomXPaoY0kYwU7 byvXraMLuTV8ea+fEE8dAryqpMB0/PYGbkmYYaig7slJQoxKoCy09/gGa2uKt9SY Lyg/DI4S+NWgArE5F9VX0EnPAGwr3Xgm2/sdAXhZF1KLCig9+WRk0m+SDRWEEbuU jVjBq9U8TJZjlMyUWMUJKvlcEQ6YXqZiOOygVu5lCYvrxeWTRz+I2I0t4HQ8AiCZ d0qRlC5vm2u11SXM3Ol1KwQGtVtoSXUiGME+4hdh6OawjyjdcqWBVmXYlL6e50kc NH8AS7iLSQK8KudEy9/akKtd3u1n29JEMyFThoIDZdl1+dbVy2UGl4F4rISLoFZx PfWqc1aDPVjTTFnUEio2 =cEZh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767567: bashburn: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/bashburn.1.gz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Den 03. nov. 2014 20:13, skrev Andreas Beckmann: On 2014-11-03 20:04, Adam D. Barratt wrote: That might be true if the fix could wait until the next stable point release (unplanned yet, but at the earliest in mid-December). Aside from anything else, at least this SRM will be following standard procedure and not acking the wheezy fix until at least unstable is fixed in any case. Unstable/jessie would not really need that fix (it's a squeeze-wheezy upgrade issue), but it won't harm :-) @Andreas Noteng: So lets get the fix into sid. Same changelog as for 3.0.1-1+deb7u1, but version it again as 3.0.1-2 and target unstable. Upload to mentors and send me the link to the .dsc Thanks for the upload. Wouldn't it be just as easy to upload the 3.1.0-1 package to unstable right away? If the release team agrees with the unblock for testing or not, I still want the updated package to go into unstable. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUV9xGAAoJELRG7qgympRacC0QAI1RihnhVV+ityqyFzNGgW39 OuTaN0QLKaWqHAgunsB9rip1aOhVlObeCRtYNSS/Drcx4amgNPgotjPu14MRGOuu WP47ks9kOAvL9JGh+n6mGcBmcCXMyyaKIcIHqhk+IgwB0+/JOYApzpvM/flt30mT zEPBnFfe1eqNVH/IVKFzgaWwPWqFdLA6uX9Ua7OhQrBYCYQdCwRkv7/B5QClbnqt SYe/Vz+5baRY/3raMQ8yPt6KB4yRLKE9n73QwZSHmOgazgtIv03clDx/fJk3zpwQ hAMCkAJgbFVTFW3I/mkv1u22mf6dbj0SA2aYesk9IcZp0dS4n3f4cZ3dG15xeeKW FqrnOEt/fr0W2bm4UA0CA8a++SKsykF98wMkRd81dgAZmYouvVPkpwIWMdFJTqmV ZrOiVR8aKfUWuAN8FMUXgviAiA0ffCT75BB42Cxkf7w5f7n+dxdQqWgA0KlATlaK KcHm9emJpZKVeyP/nOFWuqPicN1kRPEjvfCN7kczWmr+txMDeHuzH86un18I+JrC 7fjVX8QB/7HzEGRQ8iHH0OGP1qscSeW01+Zzb4CjT/RpZijMKhsHxmQMjEMz4nfx oT7jtyY9N0xmyDFVxBVzfygm92Fi7RV99MuBrv8bFcQyjpOmRnrfPv5dHf17Ok+q EmPWkcQTMFOL5wHmWBIx =R9pk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767567: bashburn: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/bashburn.1.gz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Den 02. nov. 2014 09:56, skrev Andreas Beckmann: On 2014-11-02 03:26, Michael Gilbert wrote: I think this is a false positive. bashburn never existed in squeeze. $ rmadison bashburn bashburn | 3.0.1-1 | wheezy | source, all bashburn | 3.0.1-1 | jessie | source, all bashburn | 3.0.1-1 | sid| source, all It was called mybashburn there ... debian: mybashburn | 1.0.2-1 | squeeze | source, all This needs to be fixed in wheezy too ( or only :-)) Bashburn never existed in squeeze, and should not be affected by an upgrade to Wheezy. Mybashburn was removed and has not existed in Debian since Squeeze. These are not the same packages, but mybashburn is a fork from bashburn which has since died upstream. Since mybashburn was removed I see no harm in including a replaces: mybashburn in the bashburn package. I consider this change very low importance. Do you guys still think I should release a new stable revision? If so, a sponsorship or upload permissions for the package (I'm a dm) would be greatly appreciated. I will update the package to the latest upstream version in testing. Regards Andreas Noteng -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUVmqTAAoJELRG7qgympRacv4P/0m73OB0aXNFQOSDIwagtU8a I6Z9PXKKZrEduqZUyFlHFQTlRwen8nZ5F9cKxhKrAGQI/Q0Q6YP8AOpJg4G8su0h tMrABjz7A3QxPwKs4CVTtPALtpGEh7zM/BFJb+oAuwhtFn6UBRCbSV09iZX6f9aQ AyXy37kcPqvJqLIuues2p7Qqp5lpyv3KcjOpPEWsa9B6Ghtgjfnenu6D5COyFWcd q+2ebBAxg09gVs0ZtO6UFsGQqmo5PaokNYxxD0ifEtxWnbaC0Ju0Vr07siw5g2dZ CsDq2MPsgXpBhebF0mOMC5iNNhuUjs/AKBLjHyTlqG7+B6uKOEtg7/znweh4LeNW wbg7a6lP6TMq35cUJA700MyfXwx7PUgvMcGCotu9HjIYZ+jA9QmtJBqo319RLUaH +1634qAzWz4csbtVEEiWxwjUa2KwsltrIGrtpn/npScnU5XWE7Xb3TA+8L+rtjV+ kZ7E6aU4I3VBnniSr3vaGKOpeEeeTM7UI89kxKlS+Hj0DHbk2/tZmUvX0fq9BVDz nVwb5ImgsdTUjR1h1rPgOvcJ/AnZeNB8ZKtcV6Pj3qzZiqdv13l2n1k+nmTDHueI gdi3PxBEAj8lMw/qmVTRVyMwDsL2Tt26n+ufD0FfZWClnPmQ58krYBOvMijPBffc fmdwMwol20VjXA3KGJCB =L/Nt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663552: transgui: diff for NMU version 3.2-1.1
On 06. april 2012 22:11, Mònica Ramírez Arceda wrote: tags 663552 + pending thanks Dear maintainer, I've uploaded the previous NMU for transgui (versioned as 3.2-1.1) to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. Your patch was included in the recent upload to Ubuntu. The reason I've uploaded to Ubuntu was to get it in there in time for Precise release. The reason I've not uploaded to Debian yet, is that I'm waiting for my sponsor to reply. If you have upload rights; would you please instead upload the package available in the git repo: git://git.debian.org/git/collab-maint/transmission-remote-gui.git ? There's a release ready, but untagged in master. Regards Andreas Noteng PS! transgui v. 4 will be released by upstream within a week or so.. signature.asc Description: OpenPGP digital signature
Bug#632532: transgui: hardcoded Depends on libssl0.9.8
On Thu, Sep 08, 2011 at 11:58:18PM +0200, gregor herrmann wrote: On Thu, 07 Jul 2011 17:13:32 +0200, Andreas Noteng wrote: transgui hardcodes a dependency on libssl0.9.8, which is going away. I'm currently on vacation, will have a look at this when I get back, in about 2 weeks. This bug (and the not-yet-reported FTBFS) seem to be fixed in the package's git repository since 2011-07-21. Any reason why this is not yet uploaded? Yes, I'm waiting for upstream to fix some issues that occur when transgui is built with the newest fpc. Cheers Andreas Noteng signature.asc Description: Digital signature
Bug#632532: transgui: hardcoded Depends on libssl0.9.8
On Sun, Jul 03, 2011 at 12:36:33PM +0200, Julien Cristau wrote: transgui hardcodes a dependency on libssl0.9.8, which is going away. I'm currently on vacation, will have a look at this when I get back, in about 2 weeks. Cheers Andreas Noteng -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620713: transgui: FTBFS: Can't find unit Interfaces used by transgui
On 04/03/2011 06:05 PM, Jakub Wilk wrote: | PPU Loading /usr/lib/lazarus/0.9.28.2//lcl/units/i386-linux/gtk2/interfaces.ppu | PPU Invalid Version 100 | Fatal: Can't find unit Interfaces used by transgui | Fatal: Compilation aborted | make[1]: *** [transgui] Error 1 I'm working on a fix, but there's a new upstream release due next week, so I won't upload anything until then. Regards Andreas Noteng -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598661: PyPE broken in unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: pype Version: 2.5-2 Severity: Grave Currently the pype package is abandoned, and the version in unstable dates back to 2006! The current version does not work with the version of wxGTK in unstable. See bug #579372 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyk/6UACgkQc3gI15Pmn+8tegCfQWn/fgrKx7RoW5edhTI2aDwB jJMAoJQzY3vjWUXpUXyPw+B6cb+WmzSn =3BaO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org