Bug#931519: Wajig update to resolve bug - wajig version 3.2.20
Latest version of wajig (3.2.20) on https://github.com/gjwgit/wajig has resolved the issue. Currently working on an update to Debian repo. Regards, Graham
Bug#459722: wajig: n
Received Tue 08 Jan 2008 9:25pm +1100 from Anthony Campbell: Package: wajig Version: n Severity: grave Justification: renders package unusable My installed version of wajig has just been removed owing to a dependency problem on python-apt, which in turn has other dependency problems. Thanks for the bug report Anthony. This sounds like a bug with python-apt (or something it depends on) rather than with wajig? It might need to be reassigned/reported to python-apt. It does look rather grave. What were the dependency errors that caused python-apt to be removed. Please let me know if you think this is something that needs repair in wajig itself. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422596: 2.0.36 does not fix the problem here
Received Sat 12 May 2007 12:52am +1000 from Thomas Quas: Hm, what I get here is this: $ sudo apt-get remove wajig Reading package lists... Done Building dependency tree... Done The following packages will be REMOVED: wajig 0 upgraded, 0 newly installed, 1 to remove and 79 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 446kB disk space will be freed. Do you want to continue [Y/n]? dpkg: error processing wajig (--remove): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: wajig E: Sub-process /usr/bin/dpkg returned an error code (1) $ sudo apt-get install wajig Reading package lists... Done Building dependency tree... Done Suggested packages: dpkg-repack gkdebconf gnome-tasksel apt-show-versions The following packages will be upgraded: wajig 1 upgraded, 0 newly installed, 0 to remove and 79 not upgraded. 1 not fully installed or removed. Need to get 0B/96.7kB of archives. After unpacking 0B of additional disk space will be used. Reading changelogs... Done Selecting previously deselected package wajig. (Reading database ... 360163 files and directories currently installed.) Preparing to replace wajig 2.0.35 (using .../archives/wajig_2.0.36_all.deb) ... INFO: using old version '/usr/bin/python2.3' Traceback (most recent call last): File /usr/bin/pycentral, line 1373, in ? main() File /usr/bin/pycentral, line 1367, in main rv = action.run(global_options) File /usr/bin/pycentral, line 945, in run pkg.read_version_info() File /usr/bin/pycentral, line 539, in read_version_info raise PyCentralError, package has no field Python-Version __main__.PyCentralError: package has no field Python-Version dpkg: warning - old pre-removal script returned error exit status 1 dpkg - trying script from the new package instead ... INFO: using old version '/usr/bin/python2.3' Traceback (most recent call last): File /usr/bin/pycentral, line 1373, in ? main() File /usr/bin/pycentral, line 1367, in main rv = action.run(global_options) File /usr/bin/pycentral, line 945, in run pkg.read_version_info() File /usr/bin/pycentral, line 539, in read_version_info raise PyCentralError, package has no field Python-Version __main__.PyCentralError: package has no field Python-Version dpkg: error processing /var/cache/apt/archives/wajig_2.0.36_all.deb (--unpack): subprocess new pre-removal script returned error exit status 1 INFO: using old version '/usr/bin/python2.3' Traceback (most recent call last): File /usr/bin/pycentral, line 1373, in ? main() File /usr/bin/pycentral, line 1367, in main rv = action.run(global_options) File /usr/bin/pycentral, line 869, in run pkg.read_version_info() File /usr/bin/pycentral, line 539, in read_version_info raise PyCentralError, package has no field Python-Version __main__.PyCentralError: package has no field Python-Version dpkg: error while cleaning up: subprocess post-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/wajig_2.0.36_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Received Sat 12 May 2007 12:49am +1000 from Thomas Quas: It worked. I figured that the $ sudo rm /var/lib/dpkg/wajig.prerm as described on the issue report should really be $ sudo rm /var/lib/dpkg/info/wajig.prerm My fault. Sorry for the inconvenience. -tom Actually, my fault! Sorry about the bad information. You are absolutely correct that I missed the info bit in the path. Sorry for that. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422596: wajig: This bug still exists for me
Received Sat 12 May 2007 2:12am +1000 from Gary Koskenmaki: Package: wajig Version: 2.0.35 Followup-For: Bug #422596 I ran into this bug during an apt-get upgrade yesterday. After following the workarounds you gave to those who first reported this bug, I am still unable to resolve this. One thing I found different on my system was that the prerm script to be deleted was not present on my system. I also tried using the 2.0.36 deb package and it returned the same error. Preparing to replace wajig 2.0.35 (using .../archives/wajig_2.0.35_all.deb) ... INFO: using old version '/usr/bin/python2.3' Traceback (most recent call last): File /usr/bin/pycentral, line 1373, in ? main() File /usr/bin/pycentral, line 1367, in main rv = action.run(global_options) File /usr/bin/pycentral, line 945, in run pkg.read_version_info() File /usr/bin/pycentral, line 539, in read_version_info raise PyCentralError, package has no field Python-Version __main__.PyCentralError: package has no field Python-Version dpkg: warning - old pre-removal script returned error exit status 1 dpkg - trying script from the new package instead ... INFO: using old version '/usr/bin/python2.3' Traceback (most recent call last): File /usr/bin/pycentral, line 1373, in ? main() File /usr/bin/pycentral, line 1367, in main rv = action.run(global_options) File /usr/bin/pycentral, line 945, in run pkg.read_version_info() File /usr/bin/pycentral, line 539, in read_version_info raise PyCentralError, package has no field Python-Version __main__.PyCentralError: package has no field Python-Version dpkg: error processing /var/cache/apt/archives/wajig_2.0.35_all.deb (--install): subprocess new pre-removal script returned error exit status 1 INFO: using old version '/usr/bin/python2.3' Traceback (most recent call last): File /usr/bin/pycentral, line 1373, in ? main() File /usr/bin/pycentral, line 1367, in main rv = action.run(global_options) File /usr/bin/pycentral, line 869, in run pkg.read_version_info() File /usr/bin/pycentral, line 539, in read_version_info raise PyCentralError, package has no field Python-Version __main__.PyCentralError: package has no field Python-Version dpkg: error while cleaning up: subprocess post-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/wajig_2.0.35_all.deb Sorry about the trouble Gary. It was my fault again, with some bad information. You need to do: $ sudo rm /var/lib/dpkg/info/wajig.prerm $ wajig install wajig_2.0.35_all.deb I previously left off the info bit in the remove. Sorry for the inconvenience. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361572: wajig cannot perform administrative commands and says Access denied (sudo related)r
Received Sun 09 Apr 2006 1:08pm +1000 from Ferenczi Viktor: Package: wajig Severity: grave Justification: renders package unusable I've a default sudo and wajig installation on Debian Stable. When trying to perform administrative commands like install, hold, etc. wajig says Access denied. This message is displayed when I run su as root without a user name. I tried to change my sudoers file with visudo, without success. I dig into wajig and found, that is uses su and not sudo on my system. I changed line 28 of /usr/share/wajig/perform.py to setroot = /usr/bin/sudo Now wajig works fine as root, but does not work as a normal user. I know, I have to use visudo... wajig's perform.py is a bit messy and not suits well for Debian and possibly other distributions. Thanks for the bug report. I've not seen this problem before. I'll look for a general solution. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332822: wajig search-apt writes to the current working directory instead of /etc/apt/
Received Sun 09 Oct 2005 5:49am +1000 from David Fedoruk: package: wajig replace: wajig version: 2.0.29 replace: 2.0.20 severity: critical I normally run wajig as an unprivialiged user from my home directory using sudo like I do for all other packages install related commands. Wajig assumes my location is /etc/apt/ when I am really in /home/$USER and this happens: Hi David, Thanks for the bug report. I'm not sure why you think it might be a critical bug. It doesn't render the system unusable. In fact, if it did overwrite sources.list then I might even consider that a critical bug instead. The behaviour you report is how it is specifically implemented. I did not want to accidently overwrite /etc/apt/sources.list. The purpose of this command, as the description indicates, is to find local Debian archives SUITABLE FOR sources.list, rather than TO REPLACE CURRENT. Thus it creates a suggested sources.list file which it writes into wherever you run the command. In fact, this command does no more than to run the netselect-apt command. If the resulting sources.list looks okay to you then you can go ahead and cut and past the entry you want into the system version (perhaps using wajig editsources). I could add the extra functionality to automatically overwrite the system sources.list but that does seem a little dangerous to me, since many people fine tune their sources.list and overwritting it would be a surprise. I will close the bug with this email. Let me know if you don't agree with the rationale. Regards, Graham console snip - [EMAIL PROTECTED]:~$ sudo wajig search-apt stable Using distribution stable. Retrieving the list of mirrors from www.debian.org... --12:15:12-- http://www.debian.org/mirror/mirrors_full = `mirrors_full' esolving www.debian.org... 192.25.206.10 Connecting to www.debian.org|192.25.206.10|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 163,789 (160K) [text/html] Then: The fastest non-US server seems to be: http://debian.yorku.ca/debian/non-US/ Writing sources.list. Done --- end snip Wajig has assumed all along without checking that I am issuing teh command from /etc/apt/ when I am really in /home/$USER/. I use sudo wajig update as I would use sudo apt-get update and expect that it updates the packages list as per usual . I hope I have three Debian installed Sarge machines, kernels, blackstar's kernel I compiled the others are standard Debian kernel images: Linux blackstar 2.6.11.7-Blackstar-1.1 #1 Mon May 2 03:00:18 PDT 2005 i686 GNU/Linux Linux fireroad 2.4.27-2-386 #1 Tue Aug 16 15:28:25 JST 2005 i686 GNU/Linux Linux arbutus 2.6.12-3-multimedia-686 #1 Thu Jun 23 11:52:20 CEST 2005 i686 GNU/Linux I've just re-checked these results by changing to root and working in root's home. wajig downloads a list of mirrors then procedes to find appropriate mirros and produded a sources.list in /root. Hope this helps, David -- David Fedoruk B.Mus. UBC,1986 Certificate in Internet Systems Administration, UBC, 2003 Music is enough for one's life time, but one life time is not enough for music Sergei Rachmaninov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332822: acknowledged by developer (Re: Bug#332822: wajig search-apt writes to the current working directory instead of /etc/apt/)
Received Sun 09 Oct 2005 7:34am +1000 from David Fedoruk: HI: I'm not sure why you think it might be a critical bug. It doesn't render the system unusable. In fact, if it did overwrite sources.list then I might even consider that a critical bug instead. I was thinking along the lines of missing critical security update becauase you thought you had upt to date sources when you didn't The behaviour you report is how it is specifically implemented. I did not want to accidently overwrite /etc/apt/sources.list. The purpose of this command, as the description indicates, is to find local Debian archives SUITABLE FOR sources.list, rather than TO REPLACE CURRENT. Thus it creates a suggested sources.list file which it writes into wherever you run the command. Then i miss interperted what was expected behaviour. I expect that my sources list would be edited (added to) not destroyed even old configuration files are valuable. In fact, this command does no more than to run the netselect-apt command. If the resulting sources.list looks okay to you then you can go ahead and cut and past the entry you want into the system version (perhaps using wajig editsources). The main reason I use Debian is its packaage management system which is light years ahead of anyoen elses, however even it is getting weighted down by the number of commands and layers so what I never got to with the older systems... list netselect and a few others, wajig instantly gave me access to in a way which I could remember. So in reading the documentation, much of it is new in that I didn't encounter it at all withouth wajig. That is the route of my missinterpertaion. I could add the extra functionality to automatically overwrite the system sources.list but that does seem a little dangerous to me, since many people fine tune their sources.list and overwritting it would be a surprise. Me as welll, I live in fear that an old configuration file will go into /dev/null when I had some valluable notes there! So I'm glad that this wasn'nt the case. Let me know if you don't agree with the rationale. No, I agree completely, but with my above explanations ... for some newer users things can be less than clear when you don't have years of experience piled on top. Wajig has been a godsend, It should have been done long ago. Even the best of systems get bogged down with addititons and improvements and sometimes somone needs to go through and merge it all together again. You've done that magnificently. But how about adding a few lines to the documentation in an upcoming version which makes this a bit clearer. It would help reduce the posibility of misinterpertation. Thanks for the thinking behind this David. Yes, the aim is that you should not have to know much about what wajig does under the bonnet, and hope that it just does the right thing! I guess, as I say, I could add the found site to the sources.list file but I do think that even a user of wajig probably needs to understand a little bit about the sources.list file and that they can use this to tune where they download their packages from. The central security archive is usually there by default anyhow. I've added the following to the documentation just before the section titled FINDING PACKAGES - does this help? There are quite a few archives available and you can test for a good connection to one with: $ wajig netselect-apt This will write a candidate sources.list in the current directory, which you can then review and add to the system sources.list, if you wish, with $ wajig edit-sources Thank you again for your interest in wajig. And let me know if there are other improvements that would help someone new to Debian. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316492: apt-move: A work-around
Package: apt-move Version: 4.2.23 Followup-For: Bug #316492 I had the same problem. Seems like the new apt provides libapt-pkg-libc6.3-5-3.9 and apt-move requires libapt-pkg-libc6.3-5-3.3. My fix was: wajig source apt-move cd apt-move-4.2.23 wajig build apt-move wajig install apt-move_4.2.23_i386.deb Not sure why this should have worked - if this is the actual source of apt-move Regards, Graham -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apt-move depends on: hi apt [libapt-pkg-libc6.3-5-3 0.6.38 Advanced front-end for dpkg ii bc 1.06-17 The GNU bc arbitrary precision cal ii coreutils 5.2.1-2 The GNU core utilities ii dash0.5.2-5 The Debian Almquist Shell ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libgcc1 1:4.0.0-12 GCC support library ii libstdc++6 4.0.0-12 The GNU Standard C++ Library v3 ii mawk1.3.3-11 a pattern scanning and text proces Versions of packages apt-move recommends: hi apt 0.6.38 Advanced front-end for dpkg -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293834: TypeError: encode() argument 1 must be string, not None
Package: quodlibet Version: 0.8-1 Severity: grave Justification: renders package unusable Updataing my system this morning lead to Quod Libet failing: $ quodlibet Traceback (most recent call last): File /usr/bin/quodlibet, line 2792, in ? library.init(const.LIBRARY) File /usr/lib/quodlibet/quodlibet.zip/library.py, line 797, in init File /usr/lib/quodlibet/quodlibet.zip/util.py, line 20, in to TypeError: encode() argument 1 must be string, not None Downgrading to 0.7-2 works just fine: $ wajig install quodlibet=0.7-2 quodlibet-ext=0.7-2 ... $ quodlibet ... Regards, Graham -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages quodlibet depends on: ii python2.3.4-6An interactive high-level object-o ii python-glade2 2.4.1-2GTK+ bindings: Glade support ii python-id3lib 0.5.1-3id3lib wrapper for Python - dummy ii python-pymad 0.5.2-1Python wrapper to the MPEG Audio D ii python-pyvorbis 1.3-1 A Python interface to the Ogg Vorb ii quodlibet-ext 0.8-1 extensions for the Quod Libet audi -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293834: TypeError: encode() argument 1 must be string, not None
Received Sun 06 Feb 2005 4:15pm +1100 from Joe Wreschnig: Can you send the output of the following Python script? Thanks. #!/usr/bin/python import locale print locale.getdefaultlocale() print locale.getpreferredencoding() -- Joe Wreschnig [EMAIL PROTECTED] $ cat test.py #!/usr/bin/python import locale print locale.getdefaultlocale() print locale.getpreferredencoding() $ ./test.py (None, None) ANSI_X3.4-1968 Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
