Bug#931519: Wajig update to resolve bug - wajig version 3.2.20

2020-11-13 Thread Graham Williams
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

2008-01-08 Thread Graham Williams
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 > proble

Bug#422596: wajig: This bug still exists for me

2007-05-11 Thread Graham Williams
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 res

Bug#422596: 2.0.36 does not fix the problem here

2007-05-11 Thread Graham Williams
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 upg

Bug#361572: wajig cannot perform administrative commands and says "Access denied" (sudo related)r

2006-04-08 Thread Graham Williams
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 "Acce

Bug#332822: acknowledged by developer (Re: Bug#332822: wajig search-apt writes to the current working directory instead of /etc/apt/)

2005-10-08 Thread Graham Williams
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 a

Bug#332822: wajig search-apt writes to the current working directory instead of /etc/apt/

2005-10-08 Thread Graham Williams
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. > W

Bug#316492: apt-move: A work-around

2005-07-09 Thread Graham Williams
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

Bug#293834: TypeError: encode() argument 1 must be string, not None

2005-02-05 Thread Graham Williams
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

Bug#293834: TypeError: encode() argument 1 must be string, not None

2005-02-05 Thread Graham Williams
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/quod