Bug#1017463: wajig: Please restore automatic installation of bash-completion script
Thanks for the report. This has been fixed in 4.0.12 on https://github.com/gjwgit/wajig and to be uploaded to Debian repository shortly.
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#619854: wajig: Please use gdebi for install of .deb
Thanks for the clarification. I was thinking it was the gdebi GUI. Regards, Graham On 28 March 2011 19:42, Reuben Thomas wrote: > On 28 March 2011 10:19, Graham Williams wrote: >> Does the command line use of gdebi exclude popups appearing? Seems >> like a good idea, but I just wonder what changes occur to interactions >> with wajig when we use gdebi instead of the current install method? If >> none, and we automatically get dependencies when manually installing a >> .deb, then yes - we should use it. > > I'm slightly unsure what you mean by "popup", but gdebi is a > command-line client, and when there are extra dependencies to install, > it prompts for them on the terminal, like apt-get (indeed, it seems to > depend on apt). It doesn't use a GUI. > > The package is gdebi-core, not gdebi, which may be confusing the issue. > > -- > http://rrt.sc3d.org > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619854: wajig: Please use gdebi for install of .deb
Does the command line use of gdebi exclude popups appearing? Seems like a good idea, but I just wonder what changes occur to interactions with wajig when we use gdebi instead of the current install method? If none, and we automatically get dependencies when manually installing a .deb, then yes - we should use it. Regards, Graham On 28/03/2011, Tshepang Lekhonkhobe wrote: > On Sun, Mar 27, 2011 at 21:10, Reuben Thomas wrote: >> Please make wajig install use gdebi, as this then offers to install >> any missing dependencies. Another convenience. It’s useful enough that >> my brain remembers to use gdebi when I want to install a .deb >> manually, rather than wajig. > > Makes sense. What do you think Graham? > -- Regards, Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#582250: wajig: language improvement suggestion
Fixed in 2.0.48. Regards, Graham On 19 May 2010 22:46, Reuben Thomas wrote: > Package: wajig > Version: 2.0.38 > Severity: minor > > "dependees" is not a word; it should be "dependents". I suggest that > to avoid future problems with this word you change it in the code as > well as in the output of list-commands. > > -- System Information: > Debian Release: 5.0.4 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.20.2+lenny1 Advanced front-end for dpkg > ii dselect 1.14.29 Debian package management > front-en > ii python 2.5.2-3 An interactive high-level > object-o > ii python-apt 0.7.7.1+nmu1 Python interface to libapt-pkg > ii python-central 0.6.8 register and build utility for > Pyt > > wajig recommends no packages. > > Versions of packages wajig suggests: > pn alien (no description available) > pn apt-listbugs (no description available) > pn apt-move (no description available) > ii apt-show-versions 0.15 lists available package versions > w > ii debconf 1.5.24 Debian configuration management > sy > ii deborphan 1.7.27 program that can find unused > packa > pn dpkg-repack (no description available) > ii fakeroot 1.11 Gives a fake root environment > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST packets > to > pn gkdebconf (no description available) > pn gnome-tasksel (no description available) > pn gnome-terminal (no description available) > ii locales 2.7-18lenny2 GNU C Library: National Language > ( > pn lynx (no description available) > pn python-glade2 (no description available) > pn python-gnome2 (no description available) > pn python-gtk2 (no description available) > ii reportbug 3.48 reports bugs in the Debian > distrib > ii sudo 1.6.9p17-2+lenny1 Provide limited super user > privile > ii vrms 1.14 virtual Richard M. Stallman > ii wget 1.11.4-2+lenny1 retrieves files from the web > > -- no debconf information > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579419: wajig: Simpler, faster implementation of remove-depend
Thanks Reuben. That is in wajig 2.0.47. I will aim to get that out in the next day or so. Regards, Graham On 28 April 2010 02:29, Reuben Thomas wrote: > Package: wajig > Version: 2.0.38 > Severity: minor > > Please use apt-get remove --auto-remove to implement remove-depend. > This is simpler than making wajig do the dependency checking, and runs > much faster. > > -- System Information: > Debian Release: 5.0.4 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.20.2+lenny1 Advanced front-end for dpkg > ii dselect 1.14.29 Debian package management > front-en > ii python 2.5.2-3 An interactive high-level > object-o > ii python-apt 0.7.7.1+nmu1 Python interface to libapt-pkg > ii python-central 0.6.8 register and build utility for > Pyt > > wajig recommends no packages. > > Versions of packages wajig suggests: > pn alien (no description available) > pn apt-listbugs (no description available) > pn apt-move (no description available) > ii apt-show-versions 0.15 lists available package versions > w > ii debconf 1.5.24 Debian configuration management > sy > ii deborphan 1.7.27 program that can find unused > packa > pn dpkg-repack (no description available) > ii fakeroot 1.11 Gives a fake root environment > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST packets > to > pn gkdebconf (no description available) > pn gnome-tasksel (no description available) > pn gnome-terminal (no description available) > ii locales 2.7-18lenny2 GNU C Library: National Language > ( > pn lynx (no description available) > pn python-glade2 (no description available) > pn python-gnome2 (no description available) > pn python-gtk2 (no description available) > ii reportbug 3.48 reports bugs in the Debian > distrib > ii sudo 1.6.9p17-2+lenny1 Provide limited super user > privile > pn vrms (no description available) > ii wget 1.11.4-2+lenny1 retrieves files from the web > > -- no debconf information > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#402598: wajig: More precise description of bug
Hi Reuben. I've changed the installr to use aptitude -r - will be in next release. Regards, Graham On 24 February 2010 01:27, Reuben Thomas wrote: > Package: wajig > Version: 2.0.38 > Followup-For: Bug #402598 > > > I just came across the same problem: it appeared that installr, aka > recommends, did not actually install recommended packages. > > In fact, this is not true. In fact, it does install recommends, but > only of packages explicitly requested for installation, not of their > dependencies. So, if package a depends on b, and b recommends c, then > “wajig install a” will install a and b but not c, whereas “wajig > install b” will install b and c. > > Fairly obviously, this sucks, both because it looks like it doesn’t > work and because it’s not nearly as useful as it should be. > > You can use aptitude -r to achieve this result. > > -- System Information: > Debian Release: 5.0.4 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.20.2+lenny1 Advanced front-end for dpkg > ii dselect 1.14.28 Debian package management > front-en > ii python 2.5.2-3 An interactive high-level > object-o > ii python-apt 0.7.7.1+nmu1 Python interface to libapt-pkg > ii python-central 0.6.8 register and build utility for > Pyt > > wajig recommends no packages. > > Versions of packages wajig suggests: > pn alien (no description available) > pn apt-listbugs (no description available) > pn apt-move (no description available) > ii apt-show-versions 0.15 lists available package versions > w > ii debconf 1.5.24 Debian configuration management > sy > ii deborphan 1.7.27 program that can find unused > packa > pn dpkg-repack (no description available) > ii fakeroot 1.11 Gives a fake root environment > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST packets > to > pn gkdebconf (no description available) > pn gnome-tasksel (no description available) > pn gnome-terminal (no description available) > ii locales 2.7-18lenny2 GNU C Library: National Language > ( > pn lynx (no description available) > pn python-glade2 (no description available) > pn python-gnome2 (no description available) > pn python-gtk2 (no description available) > ii reportbug 3.48 reports bugs in the Debian > distrib > ii sudo 1.6.9p17-2 Provide limited super user > privile > pn vrms (no description available) > ii wget 1.11.4-2+lenny1 retrieves files from the web > > -- no debconf information > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#565303: [wajig] regression: bash completion gone
Hi Eike, Sorry I missed your email closing the bug. Thanks for that. And thanks for the hint on how you resolved the problem. Dirk Eddelbuettel has reported the same issue and suggests that it looks like a dpkg/upgrade issue. Dirk's work around was (for the record and for those who might also stumble over the bug): > I did 'sudo rm /etc/bash_com*.d/wajig', reinstalled the package, answered in > the affirmative about 'new conf file?' and am back in business. Regards, Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#565303: [wajig] regression: bash completion gone
Thanks for the further information. The completion certainly works for me. I get daily-upgrade when I press tab. I'll check some other installations in case something went wrong in packaging. If you go back to the old version does tab completion work again? If not, does tab completion work for other applications in your shell? Regards, Graham 2010/1/15 Eike Sauer > Hello! > > Am Freitag, 15. Januar 2010 schrieb Graham Williams: > > I'm not able to repeat this. Bash completion is working on the machines > > I've tested. Could you give me some more details please since without > > being able to repeat it, it's a little difficult to debug. > > I don't know how bash completion is implemented, so I don't know where > to look. But I was quite short with my description what happened... > > When I type "wajig dai" and press the tab key, I used to get the line > "wajig daily-upgrade" automatically. This is not happening anymore. > As I do this daily, and it stopped working with the new wajig hitting > testing, I suppose it's the new version that's missing something... > > Ciao, > Eike >
Bug#565303: [wajig] regression: bash completion gone
Thanks for the bug report Eike. I'm not able to repeat this. Bash completion is working on the machines I've tested. Could you give me some more details please since without being able to repeat it, it's a little difficult to debug. Regards, Graham 2010/1/15 Eike Sauer > Package: wajig > Version: 2.0.44 > Severity: normal > > --- Please enter the report below this line. --- > It seems bash completion has gone as of version 2.0.44. > > --- System information. --- > Architecture: i386 > Kernel: Linux 2.6.30-1-686-bigmem > > Debian Release: squeeze/sid > 50 unstableftp.uni-kl.de > 50 unstableftp.de.debian.org > 150 testing security.eu.debian.org > 150 testing ftp.uni-kl.de > 150 testing ftp.de.debian.org > 150 stable volatile.debian.org > 150 stable security.eu.debian.org > 150 stable ftp.uni-kl.de > > --- Package information. --- > Depends (Version) | Installed > ==-+- > python | 2.5.4-5 > python-central (>= 0.6.11) | 0.6.14+nmu2 > apt| 0.7.25 > python-apt | 0.7.13.3 > dselect| 1.15.5.5 > > > Package's Recommends field is empty. > > Suggests (Version) | Installed > -+-=== > wget | 1.12-1.1 > fping| 2.4b2-to-ipv6-16 > debconf | 1.5.28 > reportbug| 4.9 > apt-move | 4.2.27-1+b7 > dpkg-repack | 1.32 > alien| 8.79 > fakeroot | 1.14.4-1 > gkdebconf| > lynx | > python-gtk2 | 2.16.0-1 > python-glade2| 2.16.0-1 > python-gnome2| 2.28.0-1 > gnome-terminal | > locales | 2.10.2-2 > gnome-tasksel| > deborphan| 1.7.28 > vrms | > sudo | 1.7.2p1-1 > apt-show-versions| 0.16 > apt-listbugs | > > > > >
Bug#551749: wajig: Remove start, stop, restart, reload
Closing this request. Regards, Graham 2009/10/27 Reuben Thomas > 2009/10/26 Graham Williams : > > Thanks for the wishlist report. However, I rely on this functionality > > regularly. I think it is in line with wajig being an administrative tool, > > not just a package manager. So I'd probably not entertain its removal. > Happy > > to fix it to work with Ubuntu if you know the fix. > > For the moment this problem seems to have gone way in Ubuntu. I shall > open an Ubuntu bug against wajig if it resurfaces; probably better to > close this bug since it's not the same thing (remove the feature > rather than fix a problem). > > -- > http://rrt.sc3d.org > Imagine someone who has only ever heard music once >
Bug#551749: wajig: Remove start, stop, restart, reload
Thanks for the wishlist report. However, I rely on this functionality regularly. I think it is in line with wajig being an administrative tool, not just a package manager. So I'd probably not entertain its removal. Happy to fix it to work with Ubuntu if you know the fix. Regards, Graham 2009/10/20 Reuben Thomas > Package: wajig > Version: 2.0.38 > Severity: wishlist > > > Please remove the start, stop, restart and reload commands. They are > nothing to do with package management, and on some installations they > now do the wrong thing: Ubuntu Karmic uses upstart, which uses > different commands to start and stop services. Rather than try to cope > with this, I suggest removing the commands as being beyond wajig’s > scope. > > -- System Information: > Debian Release: 5.0.3 > APT prefers stable > APT policy: (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.20.2+lenny1 Advanced front-end for dpkg > ii dselect 1.14.25 Debian package management > front-en > ii python 2.5.2-3 An interactive high-level > object-o > ii python-apt 0.7.7.1+nmu1Python interface to libapt-pkg > ii python-central 0.6.8 register and build utility for > Pyt > > wajig recommends no packages. > > Versions of packages wajig suggests: > pn alien (no description available) > pn apt-listbugs (no description available) > pn apt-move (no description available) > ii apt-show-versions 0.15 lists available package > versions w > ii debconf 1.5.24 Debian configuration > management sy > ii deborphan 1.7.27 program that can find unused > packa > pn dpkg-repack(no description available) > ii fakeroot1.11 Gives a fake root environment > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST > packets to > pn gkdebconf (no description available) > pn gnome-tasksel (no description available) > pn gnome-terminal (no description available) > ii locales 2.7-18 GNU C Library: National > Language ( > pn lynx (no description available) > pn python-glade2 (no description available) > pn python-gnome2 (no description available) > pn python-gtk2(no description available) > ii reportbug 3.48 reports bugs in the Debian > distrib > ii sudo1.6.9p17-2 Provide limited super user > privile > pn vrms (no description available) > ii wget1.11.4-2+lenny1 retrieves files from the web > > -- no debconf information > > >
Bug#515874: wajig pretend to install depends of the upgrade version of an hold package
ted; use "safe-upgrade" instead.
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Reading task descriptions... Done
> Resolving dependencies...
> The following NEW packages will be installed:
> dvdstyler-data{a} libwxsvg0{a}
> The following packages will be REMOVED:
> mpgtx{u}
> The following packages will be upgraded:
> dvdstyler
> 1 packages upgraded, 2 newly installed, 1 to remove and 24 not upgraded.
> Need to get 0B/1407kB of archives. After unpacking 2654kB will be used.
>
> If I mark the version to "F"orget in aptitude
>
> refugio:/home/chptma# aptitude upgrade
> W: The "upgrade" command is deprecated; use "safe-upgrade" instead.
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Reading task descriptions... Done
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 25 not upgraded.
> Need to get 0B of archives. After unpacking 0B will be used.
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Reading task descriptions... Done
>
> Hope all this helps.
Yes it does. Thanks. It does look like an apt-get
issue. Interestingly, "wajig upgrade" does not seem to try to install
dvdstyler-data (as one might expect given the difference between
upgrade and dist-upgrade).
I'll reassign this to apt-get. I don't see it as a wajig issue as
such.
Is it problematic that the other two packages get installed? At least
dvdstyler is not being upgraded.
Regards,
Graham
>
> 2009/5/1 Graham Williams :
> > Hi Jaime,
> >
> > Could you provide the sequence of commands or example that exhibits
> > the bug behaviour and is repeatable. I've not been able to repeat
> > this yet and without repeatability and a clear demonstration it is
> > hard to fix.
> >
> > Thanks,
> > Graham
> >
> > Received Sat 02 May 2009 5:33am +1000 from Jaime Ochoa Malagón:
> >> Hi Graham,
> >>
> >> You are right, the bug is on apt-get.
> >>
> >> I didn know how work the hold feature in apt-get any way at this
> >> moment didn't work...
> >>
> >> I don't know how to reasign the bug, did you mind to do this for me?
> >>
> >> Really I use aptitude that brings to me the feel of control and in
> >> this case thats true, someone write about wajig and their good
> >> features and I was testing it but this problem disapoint me and I
> >> return to use aptitude, I feel confortable with wajig while that works
> >> for me (not any more until this bug in apt-get is solved), thanks.
> >>
> >> 2009/4/30 Graham Williams
> >> >
> >> > Hi Jaime,
> >> >
> >> > Thanks for the bug report.
> >> >
> >> > Underneath, the dailyupgrade command is simply doing:
> >> >
> >> > apt-get --show-upgraded dist-upgrade
> >> >
> >> > so I would guess the same situation is there with apt-get.
> >> >
> >> > Do you think instead this might be a wajig specific problem?
> >> >
> >> > Otherwise could you reassign this to apt-get, perhaps as a wishlist?
> >> >
> >> > Or is there an option to apt-get to get the behaviour you want? That
> >> > might be something we could fix wajig with.
> >> >
> >> > Thanks,
> >> > Graham
> >> >
> >> > Received Wed 18 Feb 2009 4:41pm +1100 from Jaime Ochoa Malagón:
> >> > > Package: wajig
> >> > > Version: 2.0.38
> >> > > Severity: normal
> >> > >
> >> > > *** Please type your report below this line ***
> >> > >
> >> > > Some package have a bug and I request to downgrade it to the stable
> >> > > version...
> >> > >
> >> > > wajig dailyupgrade wants to upgrade it to my preferences (testing)
> >> > >
> >> > > I hold the package
> >> > >
> >> > > wajig dailyupgrade hold the stable package BUT pretends to install the
> >> > > depends of the test version, thats is a bug...
> >> > >
> >> > > -- System Information:
> >
Bug#515874: wajig pretend to install depends of the upgrade version of an hold package
Hi Jaime, Could you provide the sequence of commands or example that exhibits the bug behaviour and is repeatable. I've not been able to repeat this yet and without repeatability and a clear demonstration it is hard to fix. Thanks, Graham Received Sat 02 May 2009 5:33am +1000 from Jaime Ochoa Malagón: > Hi Graham, > > You are right, the bug is on apt-get. > > I didn know how work the hold feature in apt-get any way at this > moment didn't work... > > I don't know how to reasign the bug, did you mind to do this for me? > > Really I use aptitude that brings to me the feel of control and in > this case thats true, someone write about wajig and their good > features and I was testing it but this problem disapoint me and I > return to use aptitude, I feel confortable with wajig while that works > for me (not any more until this bug in apt-get is solved), thanks. > > 2009/4/30 Graham Williams > > > > Hi Jaime, > > > > Thanks for the bug report. > > > > Underneath, the dailyupgrade command is simply doing: > > > > apt-get --show-upgraded dist-upgrade > > > > so I would guess the same situation is there with apt-get. > > > > Do you think instead this might be a wajig specific problem? > > > > Otherwise could you reassign this to apt-get, perhaps as a wishlist? > > > > Or is there an option to apt-get to get the behaviour you want? That > > might be something we could fix wajig with. > > > > Thanks, > > Graham > > > > Received Wed 18 Feb 2009 4:41pm +1100 from Jaime Ochoa Malagón: > > > Package: wajig > > > Version: 2.0.38 > > > Severity: normal > > > > > > *** Please type your report below this line *** > > > > > > Some package have a bug and I request to downgrade it to the stable > > > version... > > > > > > wajig dailyupgrade wants to upgrade it to my preferences (testing) > > > > > > I hold the package > > > > > > wajig dailyupgrade hold the stable package BUT pretends to install the > > > depends of the test version, thats is a bug... > > > > > > -- System Information: > > > Debian Release: 5.0 > > > APT prefers stable > > > APT policy: (900, 'stable'), (550, 'unstable'), (500, 'oldstable') > > > Architecture: amd64 (x86_64) > > > > > > Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) > > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > > Shell: /bin/sh linked to /bin/bash > > > > > > Versions of packages wajig depends on: > > > ii apt 0.7.20.2 Advanced front-end for dpkg > > > ii dselect 1.14.25 Debian package management > > > front-en > > > ii python 2.5.2-3 An interactive high-level > > > object-o > > > ii python-apt 0.7.7.1+nmu1 Python interface to > > > libapt-pkg > > > ii python-central 0.6.8 register and build utility > > > for Pyt > > > > > > wajig recommends no packages. > > > > > > Versions of packages wajig suggests: > > > ii alien 8.72 convert and install rpm and > > > other > > > ii apt-listbugs 0.0.94 Lists critical bugs before > > > each ap > > > ii apt-move 4.2.27-1+b4 Maintain Debian packages in > > > a pack > > > ii apt-show-versions 0.15 lists available package > > > versions w > > > ii debconf 1.5.24 Debian configuration > > > management sy > > > ii deborphan 1.7.27 program that can find unused > > > packa > > > ii dpkg-repack 1.30 puts an unpacked .deb file > > > back to > > > ii fakeroot 1.11 Gives a fake root environment > > > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST > > > packets to > > > pn gkdebconf (no description available) > > > pn gnome-tasksel (no description available) > > > pn gnome-terminal (no description available) > > > ii locales 2.7-18 GNU C Library: National > > > Language ( > > > pn lynx (no description available) > > > ii python-glade2
Bug#515874: wajig pretend to install depends of the upgrade version of an hold package
Hi Jaime, Thanks for the bug report. Underneath, the dailyupgrade command is simply doing: apt-get --show-upgraded dist-upgrade so I would guess the same situation is there with apt-get. Do you think instead this might be a wajig specific problem? Otherwise could you reassign this to apt-get, perhaps as a wishlist? Or is there an option to apt-get to get the behaviour you want? That might be something we could fix wajig with. Thanks, Graham Received Wed 18 Feb 2009 4:41pm +1100 from Jaime Ochoa Malagón: > Package: wajig > Version: 2.0.38 > Severity: normal > > *** Please type your report below this line *** > > Some package have a bug and I request to downgrade it to the stable version... > > wajig dailyupgrade wants to upgrade it to my preferences (testing) > > I hold the package > > wajig dailyupgrade hold the stable package BUT pretends to install the > depends of the test version, thats is a bug... > > -- System Information: > Debian Release: 5.0 > APT prefers stable > APT policy: (900, 'stable'), (550, 'unstable'), (500, 'oldstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.20.2 Advanced front-end for dpkg > ii dselect 1.14.25 Debian package management > front-en > ii python 2.5.2-3 An interactive high-level > object-o > ii python-apt 0.7.7.1+nmu1 Python interface to libapt-pkg > ii python-central 0.6.8register and build utility for > Pyt > > wajig recommends no packages. > > Versions of packages wajig suggests: > ii alien 8.72 convert and install rpm and other > ii apt-listbugs0.0.94 Lists critical bugs before each > ap > ii apt-move4.2.27-1+b4 Maintain Debian packages in a > pack > ii apt-show-versions 0.15 lists available package versions > w > ii debconf 1.5.24 Debian configuration management > sy > ii deborphan 1.7.27 program that can find unused > packa > ii dpkg-repack 1.30 puts an unpacked .deb file back > to > ii fakeroot1.11 Gives a fake root environment > ii fping 2.4b2-to-ipv6-15 sends ICMP ECHO_REQUEST packets > to > pn gkdebconf (no description available) > pn gnome-tasksel (no description available) > pn gnome-terminal (no description available) > ii locales 2.7-18 GNU C Library: National Language > ( > pn lynx (no description available) > ii python-glade2 2.12.1-6 GTK+ bindings: Glade support > ii python-gnome2 2.22.3-1 Python bindings for the GNOME > desk > ii python-gtk2 2.12.1-6 Python bindings for the GTK+ > widge > ii reportbug 3.48 reports bugs in the Debian > distrib > ii sudo1.6.9p17-2 Provide limited super user > privile > > > > -- > Perhaps the depth of love can be calibrated by the number of different > selves that are actively involved in a given relationship. > >Carl Sagan (Contact) > >Jaime Ochoa Malagón >Arquitecto de Soluciones >Cel: +52 (55) 1021 0774 > > > > -- > Perhaps the depth of love can be calibrated by the number of different > selves that are actively involved in a given relationship. > > Carl Sagan (Contact) > > Jaime Ochoa Malagón > Arquitecto de Soluciones > Cel: +52 (55) 1021 0774 > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#464003: wajig: "wajig build" tends to fail with permission problems
Received Tue 05 Feb 2008 4:07am +1100 from Tshepang Lekhonkhobe: > Package: wajig > Version: 2.0.38 > Severity: normal > > Attempt to build 'cdbs' or 'fakeroot' and watch as wajig fails to > build them with permission issues, while "sudo apt-get source -b" > builds these without trouble. > > [sidenote] > I like wajig because it automatically installs build-deps, eliminating > the "sudo apt-get build-dep" step for me. Hi Tshepang, Sorry for taking so long . The problem seems to be that sudo apt-get source -b cdbs works but fakeroot apt-get source -b cdbs fails. In wajig I've used fakeroot for the build command. It seems to work otherwise and does not need system admin. (I try to avoid sysadmin unless it is really needed.) I guess this is a case where it is needed, but I wonder why, compared to other packages. Do you have any insights about that? Perhaps I just need to use sudo for all builds. It would be a pity. Keen to know your suggestion Regards, Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#432266: wajig: details doesn't work on installed but unavailable packages
Hi Reuben, I'm looking to close out some long outstanding wajig "bugs." I'm thinking to close this one - perhaps its a wishlist? Or would you have some suggested code to update? Thanks, Graham Received Mon 09 Jul 2007 9:13am +1000 from Reuben Thomas: > Package: wajig > Version: 2.0.36 > Severity: normal > > wajig details doesn't work on packages that are not installable, but > are installed. This is not a big surprise, as -t reveals that it uses > apt-cache avail. I guess that if this fails, it should try "dpkg -S". > > -- System Information: > Debian Release: lenny/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > > Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.7.3 Advanced front-end for dpkg > ii dselect 1.14.4 user tool to manage Debian > package > ii python2.4.4-6An interactive high-level > object-o > ii python-apt0.7.2 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#344399: wajig show don't show locally created packages
I believe this was fixed: $ wajig show sim Package: sim Priority: optional Section: net Installed-Size: 7856 [...] Regards, Graham Received Fri 23 Dec 2005 12:49am +1100 from Serge Matveev: > Package: wajig > Version: 2.0.31 > Severity: normal > > I thing the behaviour of aptitude is more handy > > > wajig show sim > No packages found from those known to be available or installed > > aptitude show sim > Package: sim > State: installed > Automatically installed: no > Version: 0.9.3+svn051212-1 > Priority: extra > Section: net > Maintainer: r...@serge.relcom.net > Uncompressed Size: 8701k > Description: SIM is a open-source ICQ client, using QT with enhanced features. > > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/dash > Kernel: Linux 2.6.12-1-686-smp > Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) > > Versions of packages wajig depends on: > ii apt 0.6.42.1 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.6.13.1 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520968: /usr/share/ggobi/plugins assumes ../.. is /usr
Package: ggobi Version: 2.1.8-1 Severity: normal Hi Dirk, Maybe a wishlist rather than a bug? On one of my servers I have /usr/share physcially located on another partition, with a symlink back to /usr/share (for whatever bizarre reason actually because I ran out of space on /usr). Not sure whether that violates a Debian or Linux policy. But plugins are not found for ggobi: $ ls -l /usr/share/ggobi/ total 8 drwxr-xr-x 2 root root 4096 2008-10-06 16:54 data lrwxrwxrwx 1 root root 23 2008-12-20 15:03 plugins -> ../../lib/ggobi/plugins drwxr-xr-x 2 root root 4096 2008-10-06 16:54 share $ ls -l /usr/share/ggobi/../../ total 168 [...] drwxrwsr-x 13 root src 4096 2006-09-03 21:55 cvs drwxrwxr-x 8 www-data staff 4096 2008-10-07 08:09 g2data drwxr-xr-x 3 root root 4096 2008-01-09 05:23 jaya drwx-- 2 root root 16384 2004-05-18 20:11 lost+found [...] drwxr-xr-x 407 root root 12288 2009-02-28 14:18 usrshare drwxr-xr-x 17 root root 4096 2008-07-11 19:42 var [...] That is, there is no lib directory there. My quick fix is to symlink /usr/lib to here but should the ggobi sym link be to /usrs/lib/ggobi/plugins, rather than assuming location (or does that imply other assumpmtions about location?). Regards, Graham -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ggobi depends on: ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libc6 2.7-15GNU C Library: Shared libraries ii libcairo2 1.8.6-2 The Cairo 2D vector graphics libra ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib ii libglib2.0-0 2.18.4-2 The GLib library of C routines ii libgraphviz4 2.20.2-3 rich set of graph drawing tools ii libgtk2.0-02.14.7-4 The GTK+ graphical user interface ii libpango1.0-0 1.22.4-2 Layout and rendering of internatio ii libpixman-1-0 0.14.0-1 pixel-manipulation library for X a ii libpng12-0 1.2.27-2 PNG library - runtime ii libx11-6 2:1.1.5-2 X11 client-side library ii libxcb-render-util00.3.3-2+b1utility libraries for X C Binding ii libxcb-render0 1.1-1.1 X C Binding, render extension ii libxcb11.1-1.1 X C Binding ii libxml22.6.32.dfsg-5 GNOME XML library ii libxrender11:0.9.4-2 X Rendering Extension client libra ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime ggobi recommends no packages. ggobi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#506795: wajig: Wajig auto-install ignors "noauth" option
Fixed in 2.0.40. Received Tue 25 Nov 2008 8:04am +1100 from Leslie Viljoen: > Package: wajig > Version: 2.0.38 > Severity: normal > Tags: patch > > > Here's the fix. Not sure which version to patch against, so I'll just > include some context (the fix is on line 3). > > elif command == "autoinstall": > if requires_args(command, args, "a list of package names"): > command = "apt-get install --assume-yes " + noauth + " " +\ > perform.concat(args[1:]) > perform.execute(command, root=1 > > > -- System Information: > Debian Release: lenny/sid > APT prefers intrepid-updates > APT policy: (500, 'intrepid-updates'), (500, 'intrepid-security'), (500, > 'intrepid') > Architecture: i386 (i686) > > Kernel: Linux 2.6.27-7-generic (SMP w/2 CPU cores) > Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages wajig depends on: > ii apt 0.7.14ubuntu6 Advanced front-end for dpkg > ii dselect 1.14.20ubuntu6 Debian package management > front-en > ii python2.5.2-1ubuntu1 An interactive high-level > object-o > ii python-apt0.7.7.1ubuntu4 Python interface to libapt-pkg > ii python-central0.6.7ubuntu1 register and build utility for > Pyt > > wajig recommends no packages. > > -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477921: wajig: Please add purge-removed
Received Sun 01 Jun 2008 10:47pm +1000 from Reuben Thomas:
> On Sun, 1 Jun 2008, Graham Williams wrote:
>
>> Thanks for the suggestions Reuben. Comments are below...
>>
>>
>> Received Sat 26 Apr 2008 6:20am +1000 from Reuben Thomas:
>>> Package: wajig
>>> Version: 2.0.38
>>> Severity: wishlist
>>>
>>>
>>> I often go through my packages and purge configuration files of removed
>>> packages. It'd be nice to do at least one of two things:
>>>
>>> 1. Have wajig purge prompt. I often want to know whether a purge is
>>> likely to cause problems, so I run wajig remove to see if any problems
>>> will be caused, then wajig purge to remove the packages. This is to
>>> avoid the situation where packages are purged but still installed
>>> because of dependency problems, as wajig purge doesn't prompt, but just
>>> goes ahead and tries to purge the packages you ask to be purged without
>>> first checking dependencies.
>>
>> I just use dpkg --purge here. So wajig does not dependency checks. In
>> fact, doesn't it fail if there are dependencies?
>
> Yes, but the packages are still marked as "purge" afterwards, as with
> (and presumably because of!) dpkg --purge.
Okay. So perhaps that's a dpkg issue? Happy to put submitted code into
wajig to address this if you have some.
>>> 2. Add wajig purge-removed to purge packages that have already been
>>> removed but have configuration files still in the system. This is useful
>>> in its own right e.g. after a system upgrade. I use the following script
>>> for this at the moment:
>>>
>>> dpkg-query -W --showformat='${Package}\t${Status}\n' | grep "deinstall ok
>>> config-files" | cut -f 1 | xargs wajig purge
>>>
>>
>> Would this be the same as dpkg --purge --pending?
>
> No, because such packages are not marked as pending anything.
I see. Perhaps I will just include the above snippet then for the
"purge-removed" command.
Thanks,
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477921: wajig: Please add purge-removed
Thanks for the suggestions Reuben. Comments are below...
Received Sat 26 Apr 2008 6:20am +1000 from Reuben Thomas:
> Package: wajig
> Version: 2.0.38
> Severity: wishlist
>
>
> I often go through my packages and purge configuration files of removed
> packages. It'd be nice to do at least one of two things:
>
> 1. Have wajig purge prompt. I often want to know whether a purge is
> likely to cause problems, so I run wajig remove to see if any problems
> will be caused, then wajig purge to remove the packages. This is to
> avoid the situation where packages are purged but still installed
> because of dependency problems, as wajig purge doesn't prompt, but just
> goes ahead and tries to purge the packages you ask to be purged without
> first checking dependencies.
I just use dpkg --purge here. So wajig does not dependency checks. In
fact, doesn't it fail if there are dependencies?
> 2. Add wajig purge-removed to purge packages that have already been
> removed but have configuration files still in the system. This is useful
> in its own right e.g. after a system upgrade. I use the following script
> for this at the moment:
>
> dpkg-query -W --showformat='${Package}\t${Status}\n' | grep "deinstall ok
> config-files" | cut -f 1 | xargs wajig purge
>
Would this be the same as dpkg --purge --pending?
Regards,
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#483706: wishlist/suggestion: wajig reportbug => reportbug
Maybe I need to have an alias so that "reportbug" is the same as "bug" in wajig, but the command is there: wajig bug wine Regards, Graham Received Sat 31 May 2008 2:51am +1000 from Karl Chen: > Package: wajig > Version: 2.0.38 > Severity: wishlist > > > Suggestion: "wajig reportbug PKG" runs "reportbug PKG" > > I start all my Debian package-related commands with "wajig" > so uniformly that I usually forget "reportbug" isn't a wajig > subcommand. It'd be a trivial pass-through to > /usr/bin/reportbug... > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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#454717: gxine with audio out of sync
Package: gxine Version: 0.5.11-4 Severity: important gxine has started playing audio out of sync with video. The audio is 2 seconds behind the video (repeatable). It was working just fine a few days ago. Seems to be the same irrespective of source (DVD, DVB, mpeg file) I have not been able to track it nack to any particular system changes. I have done some recent distupgrades. xine and totem continue to work just fine for exactly the same sources. Regards, Graham -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gxine depends on: ii libc6 2.7-3 GNU C Library: Shared libraries ii libdbus-glib-1-2 0.74-1 simple interprocess messaging syst ii libglib2.0-0 2.14.4-2 The GLib library of C routines ii libgtk2.0-0 2.12.3-1 The GTK+ graphical user interface ii liblircclient00.8.0-13 infra-red remote control support - ii libmozjs0d1.8.1.11-1 The Mozilla SpiderMonkey JavaScrip ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii librsvg2-common 2.18.2-1 SAX-based renderer library for SVG ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxine1 1.1.8-3the xine video/media player librar ii libxine1-x1.1.8-3X desktop video output plugins for ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library Versions of packages gxine recommends: ii libxine1-ffmpeg 1.1.8-3MPEG-related plugins for libxine1 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#440255: wajig changelog breaks sh due to parenthesis in package name-version string
Hi Jonathon,
Thanks for the bug report below. I'm cleaning up the backlog of bugs
in wajig, and I can't replicate this bug at present. Does it still
happen for you?
Thanks,
Graham
Received Fri 31 Aug 2007 10:10am +1000 from Jonathan Wilson:
> Package: wajig
> Version: 2.0.34
> Severity: normal
>
>
>
> -- System Information:
> Debian Release: 4.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.18-4-vserver-686
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>
> Versions of packages wajig depends on:
> ii apt 0.6.46.4-0.1 Advanced front-end for dpkg
> ii python 2.4.4-2 An interactive high-level
> object-o
> ii python-apt 0.6.19 Python interface to libapt-pkg
>
> wajig recommends no packages.
>
> -- no debconf information
> When I try to run wajig changelog linux-image-vserver-686, the following
> happens:
>
> # wajig changelog linux-image-vserver-686
> = linux-latest-2.6 (6) =
> sh: -c: line 0: syntax error near unexpected token `('
> sh: -c: line 0: `set -o noglob; wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:linux-latest-2.6 (6) 2> /dev/null'
>
> See also: # wajig -t changelog linux-image-vserver-686
> Performing: cat /var/lib/dpkg/status | egrep
> '^(Package|Status|Version):' | awk '/^Package: / {pkg=$2} /^Status:
> / {s1=$2;s2=$3;s3=$4} /^Version: / {print pkg,$2,s1,s2,s3}' | grep
> 'ok installed' | awk '{print $1,$2}' | sort >
> /root/.wajig/amethyst/tmpLeN9e0
> Performing: fping localhost 2>/dev/null >/dev/null
> Performing: fping packages.debian.org 2>/dev/null >/dev/null
> = linux-latest-2.6 (6) =
> Performing: wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:linux-latest-2.6 (6) 2> /dev/null
> sh: -c: line 0: syntax error near unexpected token `('
> sh: -c: line 0: `set -o noglob; wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:linux-latest-2.6 (6) 2> /dev/null'
> Performing: cat /var/lib/dpkg/status | egrep
> '^(Package|Status|Version):' | awk '/^Package: / {pkg=$2} /^Status:
> / {s1=$2;s2=$3;s3=$4} /^Version: / {print pkg,$2,s1,s2,s3}' | grep
> 'ok installed' | awk '{print $1,$2}' | sort
>
> It seems to be a problem with the "(6)" in the version number of the
> package. I guess it needs some escaping so the shell won't stumble over
> the parenthesis.
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443593: wajig whichpkg shows extra useless information
Thanks for the Bug report David. The HTML format has changed and I'll have to parse it differently. Will be fixed once I get a chance. Regards, Graham Received Sun 23 Sep 2007 4:12am +1000 from David Liontooth: > Package: wajig > Version: 2.0.34 > Severity: minor > > > Not sure what happened here, but the 'whichpkg' command has started showing > lots of extra useless information: > > # wajig whichpkg /usr/sbin/exportfs > File Path Package > ===-= > /usr/sbin/exportfs nfs-kernel-server > >> Debian > >> Packages > >> Package Contents Search Results > > [sarge] > > > [sarge-volatile] > > > [sarge-backports] > > > [etch] > > > [etch-m68k] > > > [etch-volatile] > > > [etch-backports] > > > [lenny] > > > [sid] > > > [experimental] > > > Cheers, > Dave > > > -- System Information: > Debian Release: 4.0 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores) > Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set > to en_US) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.6.46.3 Advanced front-end for dpkg > ii python2.4.4-1An interactive high-level > object-o > ii python-apt0.6.19 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444875: wajig new is very slow
Received Fri 05 Oct 2007 4:13am +1000 from Jeff King: > On Thu, Oct 04, 2007 at 09:06:10PM +1000, Graham Williams wrote: > > > I've not been able to repeat. For example: > > > > $ time wajig new > > [27 packages] > > real0m0.996s > > user0m0.784s > > sys 0m0.336s > > $ > > > > Wajig is essentially doing the same as you suggest. I save the list of > > packages in ~/.wajig/Available and ~/.wajig/Available.prv. I extract > > (in python though) those in one and not in the other. Then list the > > results, getting the descriptions from dpkg and print them. > > > > Do you repeatably get the 1 minute execution? > > Yes, I do. If I run 'top' while doing the 'wajig new', it looks like all > of the CPU time is spent in a single egrep process. However, doing an > strace reveals that it is simply running > > egrep ^(Package|Status|Version): > > which seems reasonable. However, this is quite curious: > > $ time egrep '^(Package|Status|Version)' \ > >~/egrep.out > real1m21.106s > user1m19.765s > sys 0m0.244s > > $ time perl -ne 'print if /^(Package|Status|Version)/' \ > >perl.out > real0m0.734s > user0m0.628s > sys 0m0.096s > > $ cmp perl.out egrep.out && echo same > same > > IOW, egrep takes 110 times as long to produce the same output as perl. > So it looks like this is actually a serious performance regression in > egrep. Downgrading to 2.5.1.ds2-6 is much better (although it still > takes 3.2 seconds ot perl's .734!). > > So clearly this is an egrep bug, and should be reassigned. Although now > 'wajig new' still takes 3.3 seconds, which is a little sluggish. It > looks like the data passes through a mish-mash of shell tools, which we > can probably speed up a bit. Any interest in a patch? Thanks for that Peff. A patch is most welcome. However, that is certainly very peculiar of egrep. I'm using the same version and see the opposite behaviour? $ time egrep '^(Package|Status|Version)' \ | ~/egrep.out real0m0.129s user0m0.068s sys 0m0.028s $ time perl -ne 'print if /^(Package|Status|Version)/' \ | perl.out real0m0.500s user0m0.452s sys 0m0.048s $ wajig status grep Package Installed PreviousNow State ===-===-===-===-= grep2.5.3~dfsg-22.5.3~dfsg-22.5.3~dfsg-2install $ wajig status perl Package Installed PreviousNow State ===-===-===-===-= perl5.8.8-115.8.8-7 5.8.8-11install Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444875: wajig new is very slow
Received Tue 02 Oct 2007 1:36am +1000 from Jeff King:
> Package: wajig
> Version: 2.0.37
> Severity: wishlist
>
> Running "wajig new" takes a very long time:
>
> $ time wajig new
> [... wajig new output, 5 packages ...]
> real1m36.576s
> user1m35.570s
> sys 0m0.652s
>
> I haven't profiled it closely, but I assume there is some bad
> algorithmic behavior. As a proof of concept, I created the following
> shell script that does the same thing much more quickly:
>
> -- >8 --
> #!/bin/sh
>
> OLD=$HOME/.debnew-packages
> NEW=$OLD.new
>
> set -e
>
> update() {
> test -e $OLD || touch $OLD
> apt-cache pkgnames | sort >$NEW
> }
>
> show() {
> echo '==> Added packages'
> comm -13 $OLD $NEW |
> xargs --no-run-if-empty apt-cache show |
> perl -ne '/^Package: (.*)/ and $package = $1;
> /^Description: (.*)/ and printf "%-24s %s\n", $package, $1;'
> echo '==> Removed packages'
> comm -23 $OLD $NEW
> }
>
> case "$1" in
> mark) mv $NEW $OLD ;;
> *) update; show | less -S ;;
> esac
>
> -- >8 --
>
> On the same dataset (and producing the same results, albeit with
> slightly different formatting):
>
> $ time debnew
> real0m2.390s
> user0m2.048s
> sys 0m0.348s
>
> Is there any interest in trying to integrate this into wajig? It might
> also be possible to simply fix the performance issue currently in wajig,
> but I don't have any experience with profiling python, so I'm not even
> sure which part of the code is the culprit.
Thanks for the bug report.
I've not been able to repeat. For example:
$ time wajig new
[27 packages]
real0m0.996s
user0m0.784s
sys 0m0.336s
$
Wajig is essentially doing the same as you suggest. I save the list of
packages in ~/.wajig/Available and ~/.wajig/Available.prv. I extract
(in python though) those in one and not in the other. Then list the
results, getting the descriptions from dpkg and print them.
Do you repeatably get the 1 minute execution?
Regards,
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442169: wajig: whichpkg broken
Received Fri 14 Sep 2007 5:10am +1000 from Alex Malinovich: > Package: wajig > Version: 2.0.37 > Severity: normal > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Seems that a change on the website has rendered whichpkg largely > useless. > > [EMAIL PROTECTED]:~$ wajig whichpkg /usr/lib/perl/5.8/Encode.pm > File Path Package > ===-= > >> Debian > >> Packages > >> Packages Contents Search Results > > [sarge] > > > [sarge-volatile] > > > [sarge-backports] > > > [etch] > > > [etch-m68k] > > > [etch-volatile] > > > [etch-backports] > > > [lenny] > > > [sid] > > > [experimental] > > Content Copyright © 1997 - 2007 SPI Inc.; See license terms. Debian is a > trademark of SPI Inc. > Thanks Alex. I had noticed that. I'll have a look at the fix required as time permits. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#424668: wajig changelog behaviour
Thanks Mikhail. That is a very good suggestion. If you had some code changes to implement this I would be happy to include it. Otherwise it may be a while before I get a chance to have a look at implementing it. Regards, Graham Received Thu 17 May 2007 3:03am +1000 from Mikhail Sokolov: > Package: wajig > Version: 2.0.36 > Severity: wishlist > > > I think 'wajig changelog' should have an option to show only changes > between installed package version and version that is available for > upgrade, skipping all older changes. > > -- System Information: > Debian Release: lenny/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.17 (SMP w/1 CPU core) > Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.6.46.4-0.1 Advanced front-end for dpkg > ii dselect 1.13.25 user tool to manage Debian > package > ii python 2.4.4-2 An interactive high-level > object-o > ii python-apt 0.6.21 Python interface to libapt-pkg > > wajig recommends no packages. > > -- debconf-show failed > > -- 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#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#422500: wajig: Please support apt-file
Received Tue 08 May 2007 6:18am +1000 from Reuben Thomas: > On Mon, 7 May 2007, Graham Williams wrote: > > >I'm not sure that the apt-file functionality provides anything more > >than what is already in wajig? The locate functionality is called > >"whichpkg" in wajig (and perhaps I'll alias it to locate). Is there > >other functionality you were looking for that apt-file provides and > >wajig does not? > > Most obviously, disconnected operation. I'm on a train without internet at > the moment, and obtain: > > $ wajig whichpkg /usr/bin/snd > JIG Warning: Could not contact the Debian server at > packages.debian.org > Perhaps it is down or you are not connected to the network. > JIG will continue to try to get the information required. > > File Path Package > ===-= > $ apt-file search /usr/bin/snd > csound: usr/bin/sndinfo > samplerate-programs: usr/bin/sndfile-resample > snd-gtk: usr/bin/snd > sndfile-programs: usr/bin/sndfile-convert > sndfile-programs: usr/bin/sndfile-info > sndfile-programs: usr/bin/sndfile-play > sndfile-programs: usr/bin/sndfile-regtest > > Also, as with various other functions, it seems better for wajig to > delegate. There's less chance of things going wrong, for the user to be > surprised because wajig gives a different result from some other tool that > ought to be equivalent, or for you to be tempted to paper over cracks in > Debian's administration interface by implementing functionality in wajig > that ought to have some lower-level equivalent. Thanks for that Reuben. It makes a lot of sense on both counts. Indeed, wajig was really only meant to be a wrapper around other functionality! I think I will replace the whichpkg and locate functionality with apt-file. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422500: wajig: Please support apt-file
Thanks for the suggestion. I'm not sure that the apt-file functionality provides anything more than what is already in wajig? The locate functionality is called "whichpkg" in wajig (and perhaps I'll alias it to locate). Is there other functionality you were looking for that apt-file provides and wajig does not? Thanks, Graham Received Sun 06 May 2007 11:32pm +1000 from Reuben Thomas: > Package: wajig > Version: 2.0.34 > Severity: wishlist > > apt-file support would make a very handy addition to wajig. I'd > suggest the following: > > 1. wajig update should run apt-file update too. > > 2. wajig details could use apt-file list. > > 3. wajig locate could run apt-file search. I suggest "locate" because >"wajig search" is already taken and does something different, while >"locate" suggests a function like the "locate" command, and also >like "dlocate", except those only work on files already on the >system. > > You might want to alias apt-file purge, or you might conclude that > it's rarely enough used that it doesn't need a wajig command. > > -- System Information: > Debian Release: lenny/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > > Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages wajig depends on: > ii apt 0.6.46.4-0.1 Advanced front-end for dpkg > ii python 2.4.4-2 An interactive high-level > object-o > ii python-apt 0.6.19 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415378: wajig: should suggest locales instead of base-config
Received Mon 19 Mar 2007 9:53am +1100 from Michael Gilbert: > Package: wajig > Version: 2.0.34 > Severity: normal > > wajig currently suggests base-config, but this has been superseeded by > locales. the wajig suggests should be modified to reflect this change. > > mike Thanks. I have made the change. Will be in next release of wajig. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415365: wajig: Should depend on dselect
Received Mon 19 Mar 2007 7:39am +1100 from Chris AtLee: > Package: wajig > Version: 2.0.34 > Severity: normal > > > wajig should depend on dselect since it requires it for the update > command at least. Thanks. I've made the change. It will appear in the next release of wajig. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396796: wajig: list-commands should group synonyms
Just to be a bit clearer - I think the command name rationalisation can be done relatively easily. The --simulate and --from-file are good ideas and that'll take time to see how best to incorporate them into the code. Tested code updates are always welcome :-) Regards, Graham Received Sun 05 Nov 2006 7:13am +1100 from Graham Williams: > Thanks Reuben. That is a very good list of suggestions. I will start > working my way through them. (May need patience things are quite > busy at present.) > > Regards, > Graham > > Received Sun 05 Nov 2006 4:54am +1100 from Reuben Thomas: > > On Sat, 4 Nov 2006, Graham Williams wrote: > > > > >Thanks for the suggestion. More than happy to take up your offer of > > >putting together your proposals for a rationalisation. > > > > Here's a revised list. I've tried mostly to rationalise the names, > > removing dups. One assumption is that wajig users will have a good > > completion mechanism, and will use many commands rarely, so that > > descriptive names are often better than short ones. (I just submitted a > > script derived from bash_completion.py to fish upstream.) > > > > There are a lot of changes here, some minor, some less minor. I'm not > > sure there's an easy summary. Perhaps diff against list-commands? > > > > addcdrom Add a CD-ROM to the list of available sources of packages > > auto-alts Mark the alternative to be auto set (using set priorities) > > auto-clean Remove superseded .deb files from the download cache > > auto-download Do an update followed by a download of all updated packages > > auto-install Perform an install without asking questions > > (non-interactive) > > available-version List versions of packages available for installation > > bugCheck reported bugs in package using the Debian Bug Tracker > > build Retrieve/unpack sources and build .deb for the named > > packages > > build-depend Retrieve packages required to build listed packages > > changelog Retrieve up-to-date changelog for the package > > changelog-new Retrieve the latest changelog entries for package > > clean Remove all .deb files from the download cache > > commands List all the JIG commands and one line descriptions for each > > daily-upgrade Perform an update, then dist-upgrade > > dependents List of packages which depend/recommend/suggest the package > > describe One line description of packages (-v and -vv for more > > detail) > > describe-new One line description of new packages > > detail Provide a detailed description of package (describe -vv) > > detail-new Provide a detailed description of new packages (describe > > -vv) > > dist-upgrade Upgrade to new distribution (installed and new rqd packages) > > download Download package files ready for an install > > download-depends Download package and any packages it depends on > > find-file Search for a file within installed packages > > find-unofficial Search for an unofficial Debian package at apt-get.org > > fix-configure Perform dpkg --configure -a (to fix interrupted configure) > > fix-installPerform apt-get -f install (to fix broken dependencies) > > fix-missingPerform apt-get --fix-missing upgrade > > help Print documentation (-v or -vv for more detail) > > hold Place listed packages on hold so they are not upgraded > > init (Re)initialise the JIG archive files > > installInstall (or upgrade) one or more packages or .deb files > > install-force Install packages and ignore file overwrites and depends > > install-recommended Install package and associated recommended packages > > install-recommended-suggested Install package and recommended and > > suggested packages > > install-suggested Install package and associated suggested packages > > install/dist Install packages from specified distribution > > last-updateIdentify when an update was last performed > > list List the status and description of installed packages > > list-all List a one line description of given or all packages > > list-alts List the objects that can have alternatives configured > > list-cache List the contents of the download cache > > list-daemons List the daemons that JIG can start/stop/restart > > list-files List the files that are supplied by the named package > > list-hold List those packages on hold > > list-installed List packages (with optional argument
Bug#396796: wajig: list-commands should group synonyms
Thanks Reuben. That is a very good list of suggestions. I will start working my way through them. (May need patience things are quite busy at present.) Regards, Graham Received Sun 05 Nov 2006 4:54am +1100 from Reuben Thomas: > On Sat, 4 Nov 2006, Graham Williams wrote: > > >Thanks for the suggestion. More than happy to take up your offer of > >putting together your proposals for a rationalisation. > > Here's a revised list. I've tried mostly to rationalise the names, > removing dups. One assumption is that wajig users will have a good > completion mechanism, and will use many commands rarely, so that > descriptive names are often better than short ones. (I just submitted a > script derived from bash_completion.py to fish upstream.) > > There are a lot of changes here, some minor, some less minor. I'm not > sure there's an easy summary. Perhaps diff against list-commands? > > addcdrom Add a CD-ROM to the list of available sources of packages > auto-alts Mark the alternative to be auto set (using set priorities) > auto-clean Remove superseded .deb files from the download cache > auto-download Do an update followed by a download of all updated packages > auto-install Perform an install without asking questions > (non-interactive) > available-version List versions of packages available for installation > bugCheck reported bugs in package using the Debian Bug Tracker > build Retrieve/unpack sources and build .deb for the named > packages > build-depend Retrieve packages required to build listed packages > changelog Retrieve up-to-date changelog for the package > changelog-new Retrieve the latest changelog entries for package > clean Remove all .deb files from the download cache > commands List all the JIG commands and one line descriptions for each > daily-upgrade Perform an update, then dist-upgrade > dependents List of packages which depend/recommend/suggest the package > describe One line description of packages (-v and -vv for more > detail) > describe-new One line description of new packages > detail Provide a detailed description of package (describe -vv) > detail-new Provide a detailed description of new packages (describe > -vv) > dist-upgrade Upgrade to new distribution (installed and new rqd packages) > download Download package files ready for an install > download-depends Download package and any packages it depends on > find-file Search for a file within installed packages > find-unofficial Search for an unofficial Debian package at apt-get.org > fix-configure Perform dpkg --configure -a (to fix interrupted configure) > fix-installPerform apt-get -f install (to fix broken dependencies) > fix-missingPerform apt-get --fix-missing upgrade > help Print documentation (-v or -vv for more detail) > hold Place listed packages on hold so they are not upgraded > init (Re)initialise the JIG archive files > installInstall (or upgrade) one or more packages or .deb files > install-force Install packages and ignore file overwrites and depends > install-recommended Install package and associated recommended packages > install-recommended-suggested Install package and recommended and > suggested packages > install-suggested Install package and associated suggested packages > install/dist Install packages from specified distribution > last-updateIdentify when an update was last performed > list List the status and description of installed packages > list-all List a one line description of given or all packages > list-alts List the objects that can have alternatives configured > list-cache List the contents of the download cache > list-daemons List the daemons that JIG can start/stop/restart > list-files List the files that are supplied by the named package > list-hold List those packages on hold > list-installed List packages (with optional argument substring) installed > list-large List size of all large (>10MB) installed packages > list-log List the contents of the install/remove log file (filtered) > list-names List all known packages or those containing supplied string > list-scripts List the control scripts of the package of .deb file > list-section List packages that belong to a specific section > list-sections List the sections that are available > list-statusSame as list but only prints first two columns, not > truncated > list-upgradeable List packages with newer versions available for upgrading > list-versions Generates list of package=version for all installed pack
Bug#396796: wajig: list-commands should group synonyms
Received Fri 03 Nov 2006 10:25am +1100 from Reuben Thomas: > Package: wajig > Version: 2.0.34 > Severity: wishlist > > If you must have synonyms, please have list-commands group them. > wajig's command list is too long to take in easily, which is why I > don't think there should be synonyms, but at least grouping them would > make the list easier to understand. > > There's inconsistency about the naming too; fixing that would help. > For example, some commands are two words, whereas others use > abbreviations, such as installr. Why not replace "installr" and > "recommended" (which I would imagine would list recommended packages) > with "install-recommended", for example? > > If you're at all interested in this, I'd be happy to make suggestions > for a complete rationalisation of the command name set. Thanks for the suggestion. More than happy to take up your offer of putting together your proposals for a rationalisation. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396798: wajig: Eccentric spelling of "downloadable": prefer this to "down-loadable"
Received Fri 03 Nov 2006 11:04am +1100 from Reuben Thomas: > Package: wajig > Version: 2.0.34 > Severity: minor > > A small thing, but a visual irritant. Thanks. But where does this occur? Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386658: wajig: want a verify command (debsums)
Received Sat 09 Sep 2006 6:04pm +1000 from Francesco Potorti: > Package: wajig > Version: 2.0.34 > Severity: wishlist > > Wajig is missing a `verify' command (? la rpm -K) for checking a > packag?s sum using debsums or whatever. Do you know of specific debian commands to do this check? Thanks, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396795: wajig: Typo in list-commands output for list-sections
Thanks for that. It has been fixed and will be in 2.0.35. Received Fri 03 Nov 2006 10:40am +1100 from Reuben Thomas: > Package: wajig > Version: 2.0.34 > Severity: minor > > The command "list-section" is listed twice by list-commands. The > second time it should be "list-commands". > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.16 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > > Versions of packages wajig depends on: > ii apt 0.6.46.2 Advanced front-end for dpkg > ii python2.4.3-11 An interactive high-level > object-o > ii python-apt0.6.19 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396698: wajig: Why distribute bash_completion.py?
Thanks for the feedback. A good point. I'll double check I don;t use it dynamically, and then consider removing it from the distributed code. Regards, Graham Received Thu 02 Nov 2006 11:23pm +1100 from Reuben Thomas: > Package: wajig > Version: 2.0.34 > Severity: minor > > Why are you distributing bash_completion.py? Since you already include > the bash completions, it seems a bit redundant... > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.17-2-k7 > Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) > > Versions of packages wajig depends on: > ii apt 0.6.46.2 Advanced front-end for dpkg > ii python2.4.3-11 An interactive high-level > object-o > ii python-apt0.6.19 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386658: wajig: want a verify command (debsums)
Thanks for the suggestion. I'll look into including it with the next release. Regards, Graham Received Sat 09 Sep 2006 6:04pm +1000 from Francesco Potorti: > Package: wajig > Version: 2.0.34 > Severity: wishlist > > Wajig is missing a `verify' command (? la rpm -K) for checking a > packag?s sum using debsums or whatever. > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (990, 'testing'), (500, 'testing-proposed-updates') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.15-1-amd64-k8-smp > Locale: LANG=C, [EMAIL PROTECTED] (charmap=ANSI_X3.4-1968) (ignored: LC_ALL > set to C) > > Versions of packages wajig depends on: > ii apt 0.6.45 Advanced front-end for dpkg > ii python2.4.3-11 An interactive high-level > object-o > ii python-apt0.6.19 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385612: wajig changelog fails sometimes
Thanks for the bug report. The bug has been fixed in version 2.0.35.
Regards,
Graham
Received Sat 02 Sep 2006 1:39am +1000 from Reuben Thomas:
> Package: wajig
> Version: 2.0.34
> Severity: normal
>
> e.g. at the moment on my etch system,
>
> wajig -t changelog gcc
>
> gives the following output:
>
> Performing: cat /var/lib/dpkg/status | egrep '^(Package|Status|Version):' |
> awk '/^Package: / {pkg=$2} /^Status: / {s1=$2;s2=$3;s3=$4}
> /^Version: / {print pkg,$2,s1,s2,s3}' | grep 'ok installed' | awk '{print
> $1,$2}' | sort > /home/rrt/.wajig/drom/tmpjjZ2ed
> Performing: fping localhost 2>/dev/null >/dev/null
> Performing: fping packages.debian.org 2>/dev/null >/dev/null
> = gcc-defaults (1.40) =
> Performing: wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:gcc-defaults (1.40) 2> /dev/null
> sh: -c: line 0: syntax error near unexpected token `('
> sh: -c: line 0: `set -o noglob; wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:gcc-defaults (1.40) 2> /dev/null'
> Performing: cat /var/lib/dpkg/status | egrep '^(Package|Status|Version):' |
> awk '/^Package: / {pkg=$2} /^Status: / {s1=$2;s2=$3;s3=$4}
> /^Version: / {print pkg,$2,s1,s2,s3}' | grep 'ok installed' | awk '{print
> $1,$2}' | sort
>
> which looks as though somewhere some text matching failed, and added
> the unwanted "(1.40)" to the wget line.
> -- System Information:
> Debian Release: testing/unstable
> APT prefers testing
> APT policy: (500, 'testing'), (1, 'experimental')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.16
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
>
> Versions of packages wajig depends on:
> ii apt 0.6.45 Advanced front-end for dpkg
> ii python2.3.5-11 An interactive high-level
> object-o
> ii python-apt0.6.19 Python interface to libapt-pkg
>
> wajig recommends no packages.
>
> -- no debconf information
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385612: wajig changelog fails sometimes
Thanks for the bug report Reuben. I'll have a look into it shortly.
Regards,
Graham
Received Sat 02 Sep 2006 1:39am +1000 from Reuben Thomas:
> Package: wajig
> Version: 2.0.34
> Severity: normal
>
> e.g. at the moment on my etch system,
>
> wajig -t changelog gcc
>
> gives the following output:
>
> Performing: cat /var/lib/dpkg/status | egrep '^(Package|Status|Version):' |
> awk '/^Package: / {pkg=$2} /^Status: / {s1=$2;s2=$3;s3=$4}
> /^Version: / {print pkg,$2,s1,s2,s3}' | grep 'ok installed' | awk '{print
> $1,$2}' | sort > /home/rrt/.wajig/drom/tmpjjZ2ed
> Performing: fping localhost 2>/dev/null >/dev/null
> Performing: fping packages.debian.org 2>/dev/null >/dev/null
> = gcc-defaults (1.40) =
> Performing: wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:gcc-defaults (1.40) 2> /dev/null
> sh: -c: line 0: syntax error near unexpected token `('
> sh: -c: line 0: `set -o noglob; wget --timeout=60 --output-document=-
> http://packages.debian.org/changelog:gcc-defaults (1.40) 2> /dev/null'
> Performing: cat /var/lib/dpkg/status | egrep '^(Package|Status|Version):' |
> awk '/^Package: / {pkg=$2} /^Status: / {s1=$2;s2=$3;s3=$4}
> /^Version: / {print pkg,$2,s1,s2,s3}' | grep 'ok installed' | awk '{print
> $1,$2}' | sort
>
> which looks as though somewhere some text matching failed, and added
> the unwanted "(1.40)" to the wget line.
> -- System Information:
> Debian Release: testing/unstable
> APT prefers testing
> APT policy: (500, 'testing'), (1, 'experimental')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.16
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
>
> Versions of packages wajig depends on:
> ii apt 0.6.45 Advanced front-end for dpkg
> ii python2.3.5-11 An interactive high-level
> object-o
> ii python-apt0.6.19 Python interface to libapt-pkg
>
> wajig recommends no packages.
>
> -- no debconf information
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380242: wajig: reproduced segfault on amd64
Received Mon 07 Aug 2006 8:46pm +1000 from Jeff King: > On Sun, Aug 06, 2006 at 02:30:46PM +1000, Graham Williams wrote: > > > Thanks for the additional information Jeff and confirmation of the > > problem on AMD64. Without access to such a machine its a little tricky > > to debug but I'll see what I can do. > > I traced the problem to TagFileFree from apt_pkg.so, so I believe the > problem is in python-apt. It looks like this is the same as bug #381520. > Like that submitter, when I tried to build an unstripped version of > apt_pkg.so for debugging, the segfaults went away. Thank you for your effort Jeff. I'll reassign this to #381520 in that case. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380242: wajig: reproduced segfault on amd64
Thanks for the additional information Jeff and confirmation of the
problem on AMD64. Without access to such a machine its a little tricky
to debug but I'll see what I can do.
Regards,
Graham
Received Sun 06 Aug 2006 6:23am +1000 from Jeff King:
> Package: wajig
> Version: 2.0.34
> Followup-For: Bug #380242
>
> I was able to reproduce the same segfault (I note that both I and the
> original submitter are on amd64 -- maybe a bug in python on amd64?).
>
> Here's the result you asked for:
> $ wajig -t dependents wajig
> Performing: cat /var/lib/dpkg/status | egrep
> '^(Package|Status|Version):' | awk '/^Package: / {pkg=$2} /^Status:
> / {s1=$2;s2=$3;s3=$4} /^Version: / {print pkg,$2,s1,s2,s3}' | grep
> 'ok installed' | awk '{print $1,$2}' | sort >
> /home/peff/.wajig/sigio/tmpkOF_dA
> Performing: apt-cache showpkg wajig | awk 'BEGIN{found=0}/^Reverse
> Depends:/{found=1;next}/^[^ ]/{found=0}found==1{print}{next}' | sed
> 's|Reverse Depends:||' | tr "," " " | awk '{print $1}' | sort -u | grep
> -v '^$'
> Performing: apt-cache dumpavail > /home/peff/.wajig/sigio/tmprpfgQf
> s apt
> /usr/bin/wajig: line 8: 5639 Segmentation fault /usr/bin/python -O
> $WAJIGDIR/wajig.py "$@"
>
> I get the same error when doing 'wajig new' which also does an apt-cache
> dumpavail right before dying. Perhaps there's something confusing in the
> parsing of that result. Other wajig commands I tried ran fine (e.g.,
> dist-upgrade) and running python works fine. I can send the results of
> apt-cache dumpavail if you want, but it is, of course, large.
>
> -- System Information:
> Debian Release: testing/unstable
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.17-1-amd64-k8
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>
> Versions of packages wajig depends on:
> ii apt 0.6.45 Advanced front-end for dpkg
> ii python2.3.5-11 An interactive high-level
> object-o
> ii python-apt0.6.19 Python interface to libapt-pkg
>
> wajig recommends no packages.
>
> -- no debconf information
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380242: /usr/bin/wajig: line 8: 28000 Segmentation fault /usr/bin/python -O $WAJIGDIR/wajig.py "$@"
Received Sat 29 Jul 2006 2:39am +1000 from David Liontooth: > Package: wajig > Version: 2.0.34 > Severity: normal > > > On wajig dependents wajig I get this (also a couple of other contexts): > > /usr/bin/wajig: line 8: 28000 Segmentation fault /usr/bin/python -O > $WAJIGDIR/wajig.py "$@" Hi Dave, Thanks for the report. I haven't been able to repeat it yet. Could you send me the output of "wajig -t dependents wajig". This might give a hint as to where the seg fault occurs. Can you run Python from the command line? Like just "python". Thanks, Graham > > Dave > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.16 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.6.45 Advanced front-end for dpkg > ii python2.3.5-11 An interactive high-level > object-o > ii python-apt0.6.19 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374386: wajig: typo in update
Received Tue 20 Jun 2006 4:27am +1000 from David Liontooth: > Graham Williams wrote: > > Hi David, > > > > Could you give some more context on where this message appears. I don't > > get it with a "wajig update". > > > Interesting. This sort of thing: > > # wajig update > > Get: 56 2006-06-14-1351.33.pdiff [1230B] > Get: 57 2006-06-18-1412.03.pdiff [12.0kB] > Get: 58 2006-06-14-1351.33.pdiff [21.2kB] > 99% [57 Packages rred 3158016] [58 Packages 0/21.2kB > 0%] 8549B/s > > Consistently on half a dozen machines running wajig 2.0.33. Extremely > minor, mind you! Thanks David. That looks like an issue with dselect rather than wajig. Wajig does not generate these messages. I believe they are generated by dselect. I have reassigned the bug report to dselect. Regards, Graham > > Cheers, > David > > Received Mon 19 Jun 2006 4:35pm +1000 from David Liontooth: > > > >> Package: wajig > >> Version: 2.0.33 > >> Severity: minor > >> > >> > >> When issuing "wajig update", it gives the receipt "Packages rred" > >> That's a lot of r's! > >> > >> > >> -- System Information: > >> Debian Release: testing/unstable > >> APT prefers unstable > >> APT policy: (500, 'unstable') > >> Architecture: amd64 (x86_64) > >> Shell: /bin/sh linked to /bin/bash > >> Kernel: Linux 2.6.16 > >> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > >> > >> Versions of packages wajig depends on: > >> ii apt 0.6.44.2 Advanced front-end for dpkg > >> ii python2.3.5-10 An interactive high-level > >> object-o > >> ii python-apt0.6.18 Python interface to libapt-pkg > >> > >> wajig recommends no packages. > >> > >> -- no debconf information > >> > >> > >> > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374386: wajig: typo in update
Hi David, Could you give some more context on where this message appears. I don't get it with a "wajig update". Regards, Graham Received Mon 19 Jun 2006 4:35pm +1000 from David Liontooth: > Package: wajig > Version: 2.0.33 > Severity: minor > > > When issuing "wajig update", it gives the receipt "Packages rred" > That's a lot of r's! > > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.16 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.6.44.2 Advanced front-end for dpkg > ii python2.3.5-10 An interactive high-level > object-o > ii python-apt0.6.18 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#370679: wajig: whichpkg does not work
Received Tue 06 Jun 2006 9:27pm +1000 from Francesco Potorti`: > Package: wajig > Version: 2.0.32 > Severity: normal > > [EMAIL PROTECTED] wajig whichpkg /usr/share/fonts/X11/TTF > JIG Warning: Could not contact the Debian server at > packages.debian.org > Perhaps it is down or you are not connected to the network. > JIG will continue to try to get the information required. Thanks for the report. What is the result of: # fping packages.debian.org Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366678: apt 0.6.44 changed tagfile code
Received Mon 15 May 2006 9:44pm +1000 from Michael Vogt: > On Mon, May 15, 2006 at 06:48:04AM +1000, Graham Williams wrote: > > Received Sat 13 May 2006 5:51am +1000 from Michael Vogt: > > > I looked into wajigs code and it turns out that the problem is that > > > the latest apt uses MMap inside the pkgTagFile that is used on a pipe > > > from wajig. This obviously does no longer work. I'll investigate what > > > can be done about it. See #350025 for the rational of that change. > > > > > > There are better (and faster) ways in python-apt nowdays to read the > > > description for packages btw (no need to pipe from apt-cache > > > dumpavail). > [..] > > Looks a bit of a problem with the new apt. I've not had a look at the > > newer python-apt, so any specific pointers are most welcome! > > I was not aware that the pkgTagFile code was used on things like > pipes, otherwise I would have not done the mmap modification in > libapt. If more applications use it this way (and break because of > it), I'll revert it. > > I attach a patch that switches a bit of wajig to use more recent [...] Thanks again Michael. I've not had a chance to explore the new apt. So for now I've reverted to placing the output of dumpavail into a temporary file. Not the best solution, but the simplest just at present. This bug fix will be in 2.0.33 of wajig after I've tested it a bit more. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366678: apt 0.6.44 changed tagfile code
Received Sat 13 May 2006 5:51am +1000 from Michael Vogt: > Hi, > > I looked into wajigs code and it turns out that the problem is that > the latest apt uses MMap inside the pkgTagFile that is used on a pipe > from wajig. This obviously does no longer work. I'll investigate what > can be done about it. See #350025 for the rational of that change. > > There are better (and faster) ways in python-apt nowdays to read the > description for packages btw (no need to pipe from apt-cache > dumpavail). > > Cheers, > Michael Thanks for the bug report Anthony. (Appologies if anyone got bounces re my email address - catastrophic failure from my web/email hosting). Looks a bit of a problem with the new apt. I've not had a look at the newer python-apt, so any specific pointers are most welcome! Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362632: wajig: purge doesn't purge
Received Sat 15 Apr 2006 12:52pm +1000 from David Liontooth: > Graham Williams wrote: > >Hi David, > > > >Thank you for the bug report. Could you give me an example that > >illustrates what you observe. > > > # just list linux-image-2.6.16-alsa-agp > rc linux-image-2.6.16-alsa-agp > 6 Linux kernel binary image for version 2.6.16 > # just purge linux-image-2.6.16-alsa-agp > Reading package lists... Done > Building dependency tree... Done > Package linux-image-2.6.16-alsa-agp is not installed, so not removed > 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded. > # just list linux-image-2.6.16-alsa-agp > rc linux-image-2.6.16-alsa-agp > 6 Linux kernel binary image for version 2.6.16 > > What I would like this do to is to remove the package so it doesn't show > in list (it's not just deinstalled but purged). In /var/lib/dpkg/status, > I would like to see something like this: > > Package: libpostproccvs51-dev > Status: purge ok not-installed > Priority: optional > Section: libdevel > Bugs: mailto:[EMAIL PROTECTED] > Architecture: amd64 > > That's what a purged package should look like. If I do a list here, I > see nothing -- not even a blank line: > > [EMAIL PROTECTED]:~# just list libpostproccvs51-dev > [EMAIL PROTECTED]:~# > > But purge isn't working, so /var/lib/dpkg/status shows the whole thing, > as below. It clutters my lists badly. As an installation grows in age, > it accretes increasing quantities of useless information that distracts > from the task at hand. It seems this is a change in the way apt-get works. Previously, "apt-get remove --purge" would purge a package even if it had been previously removed. I've changed the command to call "dpkg --purge". Regards, Graham > > David > > Package: linux-image-2.6.16-alsa-agp > Status: deinstall ok config-files > Priority: optional > Section: base > Installed-Size: 11400 > Maintainer: John Doe <[EMAIL PROTECTED]> > Architecture: amd64 > Source: linux-source-2.6.16-alsa-agp > Version: 6 > Config-Version: 6 > Provides: linux-image, linux-image-2.6 > Depends: coreutils | fileutils (>= 4.0) > Pre-Depends: debconf (>= 0.2.17) | debconf-2.0 > Suggests: lilo (>= 19.1) | grub, fdutils, linux-doc-2.6.16-alsa-agp | > linux-source-2.6.16$ > Description: Linux kernel binary image for version 2.6.16-alsa-agp > This package contains the Linux kernel image for version > 2.6.16-alsa-agp. > . > It also contains the corresponding System.map file, and the modules > built by the packager. It also contains scripts that try to ensure > that the system is not left in a unbootable state after an update. > . > Kernel image packages are generally produced using kernel-package, > and it is suggested that you install that package if you wish to > create a custom kernel from the sources. Please look at kernel-img.conf(5), > and /usr/share/doc/kernel-package/README.gz from the package > kernel-package > for details on how to tailor the installation of this or any other kernel > image package > > > > >Thanks, > >Graham > > > >Received Sat 15 Apr 2006 3:38am +1000 from David Liontooth: > > > >>Package: wajig > >>Version: 2.0.31 > >>Severity: minor > >> > >> > >>wajig purge no longer changes the status of that package from > >>deinstall to purged. Perhaps this is a dpkg feature? > >> > >>It would also be very useful to have a command that removes purged > >>packages from /var/lib/dpkg/status, so they don't clutter queries. > >> > >>David > >> > >>-- System Information: > >>Debian Release: testing/unstable > >> APT prefers unstable > >> APT policy: (500, 'unstable') > >>Architecture: amd64 (x86_64) > >>Shell: /bin/sh linked to /bin/bash > >>Kernel: Linux 2.6.16 > >>Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > >> > >>Versions of packages wajig depends on: > >>ii apt 0.6.43.1 Advanced front-end for dpkg > >>ii python2.3.5-4An interactive high-level > >>object-o > >>ii python-apt0.6.16 Python interface to > >>libapt-pkg > >> > >>wajig recommends no packages. > >> > >>-- no debconf information > >> > >> > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362632: wajig: purge doesn't purge
Hi David, Thank you for the bug report. Could you give me an example that illustrates what you observe. Thanks, Graham Received Sat 15 Apr 2006 3:38am +1000 from David Liontooth: > Package: wajig > Version: 2.0.31 > Severity: minor > > > wajig purge no longer changes the status of that package from > deinstall > to purged. Perhaps this is a dpkg feature? > > It would also be very useful to have a command that removes purged packages > from > /var/lib/dpkg/status, so they don't clutter queries. > > David > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.16 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.6.43.1 Advanced front-end for dpkg > ii python2.3.5-4An interactive high-level > object-o > ii python-apt0.6.16 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#359013: gallery2: Work around for G1/G2 upgrade bug
Package: gallery2 Version: 2.1-1 Followup-For: Bug #359013 I finally managed to get to the gallery2 site admin page by replacing gallery/ with gallery2/ in the URL several times. Then I was able to go to the URL Rewrite module configuation and reactivate the Migration option. My Gallery is now fully functional again. It seems that the upgrade killed this option setting. Regards, Graham -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gallery2 depends on: ii apache22.0.55-4 next generation, scalable, extenda ii apache2-mpm-prefork [httpd 2.0.55-4 traditional model for Apache2 ii debconf [debconf-2.0] 1.4.72Debian configuration management sy ii imagemagick7:6.2.4.5-0.8 Image manipulation programs ii libapache2-mod-php44:4.4.2-1+b1 server-side, HTML-embedded scripti ii mysql-client-5.0 [mysql-cl 5.0.19-2 mysql database client binaries ii netpbm 2:10.0-10.1 Graphics conversion tools ii php4-cgi 4:4.4.2-1+b1 server-side, HTML-embedded scripti ii php4-mysql 4:4.4.2-1+b1 MySQL module for php4 ii wwwconfig-common 0.0.45Debian web auto configuration Versions of packages gallery2 recommends: pn dcraw (no description available) ii ffmpeg3:20060323-0.1 audio/video encoder, streaming ser ii jhead 2.50-1 manipulate the non-image part of E ii libjpeg-progs 6b-12 Programs for manipulating JPEG fil ii mysql-server-5.0 [mysql-s 5.0.19-2 mysql database server binaries pn php4-gd | php5-gd (no description available) pn postgresql-7.4 | postgres (no description available) ii unzip 5.52-7 De-archiver for .zip files ii zip 2.31-3 Archiver for .zip files -- debconf information: * gallery2/mysql/dbserver: localhost * gallery2/restart-webserver: true * gallery2/webserver_type: apache2 * gallery2/mysql/dbname: gallery2 * gallery2/mysql/configure: true * gallery2/purge: true * gallery2/mysql/dbadmin: root -- 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#361282: wajig: crashes immediately
Received Sat 08 Apr 2006 9:28am +1000 from Francesco Potorti`: > >Thanks. Has it ever worked for you? > > Yes. I always use wajig. Thanks. > >It looks like a problem with the apt_pkg package rather than wajig? > > apt-get worked when wajig failed. I could reinstall apt-get, maybe. > How do I do it? I know how to do it with wajig, but not without. Could you try the following for me: $ python >>> import apt_pkg and tell me what output you get. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361282: wajig: crashes immediately
Thanks. Has it ever worked for you? It looks like a problem with the apt_pkg package rather than wajig? I'll investigate. Regards, Graham Received Sat 08 Apr 2006 2:58am +1000 from Francesco Potorti`: > Package: wajig > Version: 2.0.31 > Severity: important > > # wajig reinstall wajig > Traceback (most recent call last): > File "/usr/share/wajig/wajig.py", line 32, in ? > import documentation,commands,changes,perform > File "/usr/share/wajig/commands.py", line 38, in ? > import apt_pkg > ImportError: libstdc++.so.6: cannot handle TLS data > > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (990, 'testing'), (500, 'testing-proposed-updates') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.4.30-pre2-pr-hrt-1kHz-1 > Locale: LANG=C, [EMAIL PROTECTED] (charmap=ANSI_X3.4-1968) (ignored: LC_ALL > set to C) > > Versions of packages wajig depends on: > ii apt 0.6.43.3 Advanced front-end for dpkg > ii python2.3.5-5An interactive high-level > object-o > ii python-apt0.6.16.1 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360321: gramps: Fails to start: rd_object called with exception set
Package: gramps Version: 2.0.10-1 Severity: important On starting up gramps: XXX rd_object called with exception set Traceback (most recent call last): File "/usr/share/gramps/gramps.py", line 81, in ? import gramps_main File "/usr/share/gramps/gramps_main.py", line 59, in ? import MediaView File "/usr/share/gramps/MediaView.py", line 49, in ? import ImageSelect File "/usr/share/gramps/ImageSelect.py", line 62, in ? import Sources File "/usr/share/gramps/Sources.py", line 56, in ? from DdTargets import DdTargets TypeError: argument 1 must be string, not None Regards, Graham -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gramps depends on: ii gconf22.14.0-1 GNOME configuration database syste ii python2.3.5-5An interactive high-level object-o ii python-glade2 2.8.2-3GTK+ bindings: Glade support ii python-gnome2 2.12.3-2 Python bindings for the GNOME desk ii scrollkeeper 0.3.14-10 A free electronic cataloging syste ii yelp 2.12.2-4 Help browser for GNOME 2 Versions of packages gramps recommends: ii graphviz2.8-0.4 rich set of graph drawing tools ii python-gnome2-extras2.12.1-2.1 Python bindings for the GNOME desk ii python-reportlab1.20debian-3 ReportLab library to create PDF do ii ttf-freefont20060126b-3 Freefont Serif, Sans and Mono True -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#359013: Upgrade to 2.1 breaks gallery2 - mixed /gallery/ and /gallery2/ links?
Package: gallery2 Version: 2.1-1 Severity: important I upgraded from 2.0.4-1. The web-based upgrade appeared to work just fine. Visiting /gallery2/ I can login, visit an album but then thumbnails are not found and links go to /gallery/ instead of /gallery2/ and are not found! If I can select an album, but I don't get thumbnails, but I do get everything else. But click on a sub album and it takes me to a /gallery/ link that does note exist. If I manually change /gallery/ to /gallery2/ in the URL text entry of the browser (epiphany), it works for that page, except for the thumbnails, but further links to /gallery/ fail? I have two aliases defined in apache.conf: Alias /gallery /usr/share/gallery2 Alias /gallery2 /usr/share/gallery2 Previous upgrades have all worked just fine. My mysql backup compared to current mysqldump has quite a few structural changes, eg: *** gallery2_060325.sql Sat Mar 25 19:12:50 2006 --- gallery2_060326.sql Sun Mar 26 07:52:14 2006 *** *** 25,26 - `g_userId` int(11) default NULL, - `g_groupId` int(11) default NULL, --- 24 *** *** 28 ! UNIQUE KEY `g_accessListId` (`g_accessListId`,`g_userId`,`g_groupId`), --- 26,27 ! `g_userOrGroupId` int(11) NOT NULL default '0', ! PRIMARY KEY (`g_accessListId`,`g_userOrGroupId`), *** etc., but perhaps due to the 2.0 to 2.1 version diff (I don't see such significant changes from the 2.0.3 to 2.0.4 dumps). Basically, my Gallery is kaput. Regards, Graham -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gallery2 depends on: ii apache22.0.55-4 next generation, scalable, extenda ii apache2-mpm-prefork [httpd 2.0.55-4 traditional model for Apache2 ii debconf [debconf-2.0] 1.4.72Debian configuration management sy ii imagemagick6:6.2.4.5-0.7 Image manipulation programs ii libapache2-mod-php44:4.4.2-1+b1 server-side, HTML-embedded scripti ii mysql-client-5.0 [mysql-cl 5.0.19-2 mysql database client binaries ii netpbm 2:10.0-10.1 Graphics conversion tools ii php4-cgi 4:4.4.2-1+b1 server-side, HTML-embedded scripti ii php4-mysql 4:4.4.2-1+b1 MySQL module for php4 ii wwwconfig-common 0.0.45Debian web auto configuration Versions of packages gallery2 recommends: pn dcraw (no description available) ii ffmpeg3:20060323-0.0 audio/video encoder, streaming ser ii jhead 2.50-1 manipulate the non-image part of E ii libjpeg-progs 6b-12 Programs for manipulating JPEG fil ii mysql-server-5.0 [mysql-s 5.0.19-2 mysql database server binaries pn php4-gd | php5-gd (no description available) pn postgresql-7.4 | postgres (no description available) ii unzip 5.52-7 De-archiver for .zip files ii zip 2.31-3 Archiver for .zip files -- debconf information: * gallery2/mysql/dbserver: localhost * gallery2/restart-webserver: true * gallery2/webserver_type: apache2 * gallery2/mysql/dbname: gallery2 * gallery2/mysql/configure: true * gallery2/purge: true * gallery2/mysql/dbadmin: root -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350944: wajig: command line processing interacts badly with archives names having dash
Received Thu 02 Feb 2006 9:18am +1100 from John V. Belmonte: > Package: wajig > Version: 2.0.31 > Severity: normal > > The backports.org archive uses a dash in their archive name (sarge-backports). > Apparently wajig strips dashes in its command line processing, so the > following doesn't work: > > $ wajig -t install/sarge-backports lua5.1 > ... > Performing: apt-get --target-release sargebackports install 'lua5.1' > Thanks for the bug report John. I'll fix the processing to ensure I don't touch anything in the command name after the "/". Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347919: wajig: "toupgrade" shows no output nor error if run as non-root user
Hi Calum, Thank you for the bug report. I can't yet see what the problem is. Could you do a "wajig update" priori to the "wajig toupgrade" (as the user and separately as root) and let me know again the output of the two "wajig toupgrade"s. Thanks, Graham Received Sat 14 Jan 2006 2:03am +1100 from Calum Mackay: > Package: wajig > Version: 2.0.31 > Severity: normal > > When run as a normal user, "toupgrade" produces no output, nor any error: > > diz $ wajig toupgrade > Package AvailableInstalled > -- > diz $ > > yet run as root it shows the data: > > diz # wajig toupgrade > Package AvailableInstalled > -- > capplets-data1:2.12.2-1 1:2.10.2-1 > dosemu 1.2.1-3.11.2.1-3 > exim44.60-2 4.60-1 > exim4-base 4.60-2 4.60-1 > exim4-config 4.60-2 4.60-1 > exim4-daemon-heavy 4.60-2 4.60-1 > eximon4 4.60-2 4.60-1 > gnome-applets2.12.2-4 2.10.1-5 > gnome-applets-data 2.12.2-4 2.10.1-5 > gnome-control-center 1:2.12.2-1 1:2.10.2-1 > gnome-utils 2.12.2-3 2.10.1-4 > gnome-volume-manager 1.4.0-4 1.4.0-3 > hal 0.5.5.1-50.4.8-8 > hal-device-manager 0.5.5.1-50.4.8-8 > procmail 3.22-13 3.22-12 > python2.3-gnome2-extras 2.12.1-2 2.10.2-1 > python2.4-gnome2-extras 2.12.1-2 2.10.2-1 > > > Since this option shouldn't require root privs, I think the bug is the > lack of output, rather than the lack of error. > > best regards, > calum. > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.14 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > > Versions of packages wajig depends on: > ii apt 0.6.43.1 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.6.16 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346022: gnubiff: Stops reporting new mail afte a little time
Package: gnubiff Version: 2.1.8-1 Severity: normal I've been having this problem for some time, trying to find a pattern to the behaviour - no success yet Gnubiff works fine on startup and then for a few hours after this, but then it stops noticing new email - i.e., the icon does not change from "no mail" and a single click does not bring up any new messages. All the rest of its functionality works just fine. My setup: debian, sid, gnome, Maildir mailbox (~/Maildir), running 'gnome-terminal -t "Mutt" -e mutt' on double click, permanently connected to the Internet. I don't think I've changed any other options. Mail is filtered through procmail before ending up in my Maildir new mailbox. Regards, Graham -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gnubiff depends on: ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.10.1-1 Bonobo CORBA interfaces library ii libbonoboui2-02.10.1-1 The Bonobo UI library ii libc6 2.3.5-9GNU C Library: Shared libraries an ii libgamin0 [libfam0] 0.1.7-2Client library for the gamin file ii libgcc1 1:4.0.2-5 GCC support library ii libgconf2-4 2.10.1-6 GNOME configuration database syste ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.8.4-2The GLib library of C routines ii libgnome2-0 2.10.1-1 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.10.2-2 A powerful object-oriented display ii libgnomeui-0 2.10.1-1 The GNOME 2 libraries (User Interf ii libgnomevfs2-02.10.1-5 The GNOME virtual file-system libr ii libgtk2.0-0 2.8.9-2The GTK+ graphical user interface ii libice6 6.9.0.dfsg.1-1 Inter-Client Exchange library ii liborbit2 1:2.12.4-1 libraries for ORBit2 - a CORBA ORB ii libpanel-applet2-02.10.2-1 library for GNOME 2 panel applets ii libpango1.0-0 1.10.1-2 Layout and rendering of internatio ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm66.9.0.dfsg.1-1 X Window System Session Management ii libssl0.9.8 0.9.8a-5 SSL shared libraries ii libstdc++64.0.2-5The GNU Standard C++ Library v3 ii libxml2 2.6.22-2 GNOME XML library ii sox 12.17.9-1 A universal sound sample translato ii zlib1g1:1.2.3-9 compression library - runtime gnubiff recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#339010: wajig uses a deprecated option for tail
Received Tue 15 Nov 2005 1:04am +1100 from Yves-Alexis Perez: > Package: wajig > Version: 2.0.30 > Severity: normal > > After doing an update, wajig counts new packages to present some stats. > It uses tail with a deprecated syntax: tail -|+N, while it should use tail > -n -|+N, so it doesnt work with the current version. > > (tail (GNU coreutils) 5.93) > > Attached patch solve this. Dear Yves-Alexis, Thank you for your prompt bug report. Now fixed in 2.0.31. Available on deb http://www.togaware.com/debian ./ Being uploaded to the archives. Regards, Graham > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'stable') > Architecture: powerpc (ppc) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.14 > Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 > (charmap=ISO-8859-15) > > Versions of packages wajig depends on: > ii apt 0.6.42.3 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.6.14 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > --- commands.py 2005-11-05 06:23:03.0 +0100 > +++ commands.py.new 2005-11-14 14:40:51.0 +0100 > @@ -358,7 +358,7 @@ > # the download archive, if there is any there. > # > lscmd = "/bin/ls " + archives > -lscmd += " | egrep '^" + pkg + "_' | sort | tail -1" > +lscmd += " | egrep '^" + pkg + "_' | sort | tail -n -1" > matches = perform.execute(lscmd, pipe=True) > debpkg = matches.readline().strip() > # > --- changes.py2005-11-05 06:23:03.0 +0100 > +++ changes.py.new2005-11-14 14:40:10.0 +0100 > @@ -169,7 +169,7 @@ >"| egrep '^(Package|Version):' " +\ >"| tr '\n' ' '" +\ >"| perl -p -e 's|Package: |\n|g; s|Version: ||g'" +\ > - "| sort | tail +2 | sed 's| $||' > " + available_file > + "| sort | tail -n +2 | sed 's| $||' > " + available_file > # Use langC in the following since it uses a grep. > perform.execute(command, noquiet=True, langC=True) # root is not > required. > os.rename(temporary_file, previous_file) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318048: wajig: During install, bash_completion works only on the first package's name
Received Wed 13 Jul 2005 3:25pm +1000 from Kamaraju Kusumanchi: > Package: wajig > Version: 2.0.29 > Severity: wishlist > > > Hi, >I love wajig and am hoping this would be easy to fix. When I have the > /etc/bash_completion sourced in ~/.bashrc, I can do > > wajig install vim-co > > and it will result in > > wajig install vim-common > > which is great. However, this feature works only on the first packagename and > does not work for subsequent package names. For example, If I do > > wajig install vim-common vim-d > > it does not exapand to > > wajig install vim-common vim-doc > > It would be nice if the auto completion works on all the package names. As a > side note, I would like to mention that, apt-get's bash_completion feature > works > on multiple package names. Dear Kamaraju, Thanks for the bug report. Wajig now has this behaviour from version 2.0.31. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337587: bad behavior after Ctrl-C at "wajig source" continue prompt
Received Mon 07 Nov 2005 1:03am +1100 from John Belmonte: > Graham, since you removed the implicit apt-get build-dep, this is likely > no longer an issue for "wajig source". However, it may be worth > investigating if other commands such as "wajig build" have a similar issue. > > Yep. Now fixed. Thanks for the bug report John. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#330473: wajig: list-log missing from bash completion
Received Wed 28 Sep 2005 7:18pm +1000 from John V. Belmonte: > Package: wajig > Version: 2.0.29 > Severity: normal > > Bash completion does not include the list-log command. Please confirm that > there are no others missing. Ideally the bash completion script would be > generated from wajig itself (e.g. via "wajig commands") rather than > maintaining a separate command list. Hi John, Thanks for the report. Actually it is automatically generated, just that it was being missed in the make. Fixed in 2.0.30. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337588: implicit "apt-get build-dep" on "wajig source" is misdesign
Thanks for the feedback John. I've reverted the SOURCE command to not call build-depend. This will be in 2.0.30. Regards, Graham Received Sat 05 Nov 2005 2:49pm +1100 from John V. Belmonte: > Package: wajig > Version: 2.0.29 > Severity: normal > > Starting with wajig 2.0.26, the source command causes an implicit "apt-get > build-dep". This is not the desired behavior if the user is intending to > build the package with tools such as pbuilder which run in an isolated > environment. My typical use pattern is to use "wajig source" to grab a > package, modify the source tree to my needs, and build it with pdebuild. > Besides building in a clean environment, this prevents my normal environment > from being littered over the long term with every package in the Debian > archive. The current behavior of "wajig source" defeats this-- please > revert to the previous behavior. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337587: bad behavior after Ctrl-C at "wajig source" continue prompt
Received Sat 05 Nov 2005 2:49pm +1100 from John V. Belmonte: > Package: wajig > Version: 2.0.29 > Severity: normal > > When running "wajig source", hitting Ctrl-C at the "Do you want to continue?" > prompt causes wajig to behave as if you've entered yes. Hi John, Thanks for the bug report. Could you show me the output of "wajig -t source ..." so I might see where the question is being asked. I don;t get this question. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#335240: wajig: Please add a command to search for build dependencies
Received Sun 23 Oct 2005 5:34am +1000 from Florian Ragwitz: > Package: wajig > Version: 2.0.29 > Severity: wishlist > > Hello, > > it would be nice to be able to search for packages that build-depend on > another. I don't like using grep-dctrl for that. > > TIA, > Flo Hi Flo, Could you give some examples of what you would like here? Thanks, Graham > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.13 > Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) > > Versions of packages wajig depends on: > ii apt 0.6.42 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.6.13.1 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > -- 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#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#329882: apt-get source priorities changed in newer version?
Package: apt Version: 0.6.41 Severity: normal Since the upgrade of apt (supporting gpg) into unstable, after the release of 3.1, my local archive no longer works? I've tried tracking the problem down on and off over the past few weeks but to no avail. Not sure if this is an apt problem or a problem with my archive, but it used to work and I don't think I have changed how my archive is managed (with apt-move). I've cut my sources.list to just two sources: mine and debian. I remove a small package from my system: # apt-get remove most Reading package lists... Done Building dependency tree... Done The following packages will be REMOVED: most 0 upgraded, 0 newly installed, 1 to remove and 3 not upgraded. Need to get 0B of archives. After unpacking 111kB disk space will be freed. Do you want to continue [Y/n]? (Reading database ... 264409 files and directories currently installed.) Removing most ... I do an UPDATE # apt-get update Ign http://togaware.redirectme.net unstable Release.gpg Get:1 http://togaware.redirectme.net unstable Release [856B] Ign http://togaware.redirectme.net unstable/main Packages Ign http://togaware.redirectme.net unstable/non-free Packages Get:2 http://togaware.redirectme.net unstable/main Packages [161kB] Get:3 http://togaware.redirectme.net unstable/non-free Packages [424B] Get:4 http://ftp.debian.org unstable Release.gpg [189B] Hit http://ftp.debian.org unstable Release Hit http://ftp.debian.org unstable/main Packages Hit http://ftp.debian.org unstable/contrib Packages Hit http://ftp.debian.org unstable/non-free Packages Fetched 163kB in 1s (118kB/s) Reading package lists... Done I check where policy thinks I should get the package from: # apt-cache policy most most: Installed: (none) Candidate: 4.10.2-1 Version table: 4.10.2-1 0 500 http://togaware.redirectme.net unstable/main Packages 500 http://ftp.debian.org unstable/main Packages Yet when I install it goes to debian, not togaware: # apt-get install most Reading package lists... Done Building dependency tree... Done The following NEW packages will be installed: most 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. Need to get 43.5kB of archives. After unpacking 111kB of additional disk space will be used. Get:1 http://ftp.debian.org unstable/main most 4.10.2-1 [43.5kB] Fetched 43.5kB in 1s (26.6kB/s) Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Selecting previously deselected package most. (Reading database ... 264402 files and directories currently installed.) Unpacking most (from .../most_4.10.2-1_i386.deb) ... Setting up most (4.10.2-1) ... Why is it retrieving the package from http://ftp.debian.org rather than http://togaware.redirectme.net? Regards, Graham -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "i386"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; Dir "/"; Dir::State "var/lib/apt/"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::userstatus "status.user"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt/"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt/"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::vendorlist "vendors.list"; Dir::Etc::vendorparts "vendors.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::dpkg "/usr/bin/dpkg"; DPkg ""; DPkg::Pre-Install-Pkgs ""; DPkg::Pre-Install-Pkgs:: "if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed'; then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo 'Warning: apt-listbugs exited abnormally, hit enter key to continue.' 1>&2 ; read a < /dev/tty ); fi"; DPkg::Pre-Install-Pkgs:: "/usr/bin/apt-listchanges --apt || test $? -ne 10"; DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true"; DPkg::Tools ""; DPkg::Tools::Options ""; DPkg::Tools::Options::/usr/bin/apt-listchanges ""; DPkg::Tools::Options::/usr/bin/apt-listchanges::Version "2"; -- (no /etc/apt/preferences present) -- -- /etc/apt/sources.list -- deb http://togaware.redirectme.net/pub/debian unstable main non-free deb http://ftp.debian.org/debian unstable main contrib non-free -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Ver
Bug#328782: wajig: add experimental
Hi David, Thanks for the suggestion. But I would put this one outside the scope of wajig. The UNOFFICIAL command queries www.apt-get.org and you are probably able to request there that the experimental package archive be included in their list. Regards, Graham Received Sat 17 Sep 2005 10:33pm +1000 from David Liontooth: > > Package: wajig > Version: 2.0.29 > Severity: wishlist > > *** Please type your report below this line *** > > Wajig currently provides access to unofficial packages (find-pkg and > unofficial), but I don't see a way to > query experimental. Would it be possible add an "experimental" command, > and perhaps extend find-pkg to look > in both places, adding appropriate warnings? > > Dave > > > -- System Information: > Debian Release: sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.12 > Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) > > Versions of packages wajig depends on: > ii apt 0.6.41 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.6.12.1 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#322323: wajig: use aptitude instead of apt-get sometimes
Received Thu 11 Aug 2005 4:52am +1000 from Karl Chen: > > Hmm, OK. I did also find aptitude to be unstable at times in the > past. Anyway, for the specific problem of purging deinstalled > packages, maybe wajig could directly call `dpkg --purge'? Thanks Karl. I believe apt-get remove --purge used to purge deinstalled config files, but some quick testing now seems to indicate that it does not - but then for the same packages dpkg --purge doesn't seem to be purging either. I'll have to investigate some more, unless you have specific examples of where it works in one and not the other. Regards, Graham > > >>>>> On 2005-08-10 02:38 PDT, Graham Williams writes: > > Graham> Thanks Karl. I did use aptitude for a while but it > Graham> did not interact so well with apt-get and for various > Graham> reasons I reverted to apt-get. you will find various > Graham> comments in the code relating to the issues with > Graham> aptitude. There will also be some discussion of this > Graham> over the years in the BTS. Perhaps the issues have > Graham> been fixed, but I am hesitant to move to aptitude > Graham> unless there was a good reason to do so. > > Graham> Regards, Graham > > Graham> Received Wed 10 Aug 2005 6:56pm +1000 from Karl Chen: > >> Package: wajig Version: 2.0.29 Severity: wishlist > >> > >> Aptitude(8) is better than apt-get(8) for various purposes. > >> For example, 'aptitude purge package' can purge a > >> deinstalled package, while 'apt-get remove --purge package' > >> cannot. Its dependency resolution engine is (supposedly) > >> better. Since aptitude is now 'important' and default for > >> Sarge, I think some wajig commands should use aptitude. > >> > > -- > Karl 2005-08-10 11:27 > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#322323: wajig: use aptitude instead of apt-get sometimes
Thanks Karl. I did use aptitude for a while but it did not interact so well with apt-get and for various reasons I reverted to apt-get. you will find various comments in the code relating to the issues with aptitude. There will also be some discussion of this over the years in the BTS. Perhaps the issues have been fixed, but I am hesitant to move to aptitude unless there was a good reason to do so. Regards, Graham Received Wed 10 Aug 2005 6:56pm +1000 from Karl Chen: > Package: wajig > Version: 2.0.29 > Severity: wishlist > > Aptitude(8) is better than apt-get(8) for various purposes. For > example, 'aptitude purge package' can purge a deinstalled package, > while 'apt-get remove --purge package' cannot. Its dependency > resolution engine is (supposedly) better. Since aptitude is now > 'important' and default for Sarge, I think some wajig commands > should use aptitude. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320126: wajig: Please use `sudo -v' before using pipelined sudo commands
Received Sat 06 Aug 2005 12:55am +1000 from Karl Chen:
> >>>>> On 2005-08-04 13:14 PDT, Graham Williams writes:
>
> Graham> command = setroot + " sh -c '%s'" % command
>
> This would work for me, but won't work for people that either can
> only run certain commands, or have NOPASSWD for certain commands.
>
> You might want to quote command, e.g.
> command = setroot + " sh -c '%s'" % command.replace("'","'''")
Thanks Karl. I've been playing with a few ideas. None are really
satisfactory yet. I'm trying to avoid the temporary file path, but
maybe I can't, in the end. Currently I've gone back to your solution
of doing a "sudo -v" if there is a pipe and then the sudo substitute
for each part of a pipe. At least this will mostly be the same
behaviour, and will fix the problem you identified.
Again, I'll test this out for a little while before uploading.
Regards,
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320126: wajig: Please use `sudo -v' before using pipelined sudo commands
Received Fri 05 Aug 2005 1:00am +1000 from Karl Chen:
> >>>>> On 2005-07-30 15:06 PDT, Graham Williams writes:
>
> Graham> Thanks. But I was more wondering how the problem
> Graham> manifests itself. What happened that caused you to
> Graham> submit a bug report? I don't think I've ever noticed a
> Graham> problem with these pipes.
>
> Try the commands without NOPASSWD. The behavior I get is two
> Password: prompts simultaneously. The problem is you shouldn't
> have to enter the password twice (with normal sudo settings), and
> for the second password the tty settings are in clear the first
> attempt (and it's not clear what's going on to the casual user).
Thanks Karl. I can repeat the error now. It is indeed very ugly!!!
I'm looking to see if I can use something like:
command = setroot + " sh -c '%s'" % command
for the sudo commands, instead of
command = setroot + " " + command.replace("|", "| %s " % setroot)
It is working on the limited testing I've done but need more testing.
If you get a chance, could you check if that fixes it for you.
Thanks,
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#321050: Complains: no module apt_pkg
Received Wed 03 Aug 2005 1:39pm +1000 from Mozai: > Package: wajig > Version: 2.0.29 > Severity: normal > > > Unpacking wajig (from .../archives/wajig_2.0.29_all.deb) ... > Setting up python2.3-apt (0.6.12.2) ... > Setting up python-apt (0.6.12.2) ... > Setting up wajig (2.0.29) ... > > margot:/home/moses# wajig install lynx-ssl > Traceback (most recent call last): > File "/usr/share/wajig/wajig.py", line 32, in ? > import documentation,commands,changes,perform > File "/usr/share/wajig/commands.py", line 38, in ? > import apt_pkg > ImportError: No module named apt_pkg > margot:/home/moses# wajig sizes > Traceback (most recent call last): > File "/usr/share/wajig/wajig.py", line 32, in ? > import documentation,commands,changes,perform > File "/usr/share/wajig/commands.py", line 38, in ? > import apt_pkg > ImportError: No module named apt_pkg Thank you for the bug report. I am currently attempting to replicate this. I have seen this when downgrading apt-get once. Are you likely to have downgraded apt-get lately? Regards, Graham > > ? > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.11-1-k7 > Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) > > Versions of packages wajig depends on: > ii apt 0.6.39.0.1 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.6.12.2 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320126: wajig: Please use `sudo -v' before using pipelined sudo commands
Received Sat 30 Jul 2005 9:45am +1000 from Karl Chen: > >>>>> On 2005-07-28 12:53 PDT, Graham Williams writes: > > Graham> After some testing, a problem with the proposed > Graham> solution is that a user may have sudo set up with the > Graham> NOPASSWD option for certain commands. "sudo -v" > Graham> requires the password unconditionally, thus not > Graham> matching the user's configuration. > > Good point. Also affects users that cannot run all commands but > only certain commands. I thought about it for a while, and the > only solution I see that preserves NOPASSWD usage is to break the > pipeline up into separate commands, e.g. sudo command1 > tmpfile > && sudo command2 < tmpfile. (That has the minor advantage that > you can additionally check exit codes in each pipeline component.) Thanks Karl. I'll have another think about this. Perhaps the tmpfiles is a solution. > Graham> So I think I need to go back to the specific example > Graham> where the previous behaviour of wajig has a > Graham> problem. could you give me an example of using wajig > Graham> where it has a problem with the previous behaviour. > > These functions use root=1 with pipeline: do_hold, do_listnames, > do_unhold, do_update. Thanks. But I was more wondering how the problem manifests itself. What happened that caused you to submit a bug report? I don't think I've ever noticed a problem with these pipes. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320126: wajig: Please use `sudo -v' before using pipelined sudo commands
Received Thu 28 Jul 2005 8:28am +1000 from Karl Chen: > >>>>> On 2005-07-27 14:45 PDT, Graham Williams writes: > > Graham> Thanks Karl. I'll include this in the next release. > > Thanks! Hi Karl, After some testing, a problem with the proposed solution is that a user may have sudo set up with the NOPASSWD option for certain commands. "sudo -v" requires the password unconditionally, thus not matching the user's configuration. So I think I need to go back to the specific example where the previous behaviour of wajig has a problem. could you give me an example of using wajig where it has a problem with the previous behaviour. Thanks, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320126: wajig: Please use `sudo -v' before using pipelined sudo commands
Received Thu 28 Jul 2005 7:11am +1000 from Karl Chen: > >>>>> On 2005-07-27 02:56 PDT, Graham Williams writes: > > >> For some wajig commands, wajig executes "sudo command1 | > >> sudo command 2...", which is impossible to authenticate > >> properly. Doing a "sudo -v" before any pipeline solves it. > > Graham> Thanks for the bug report Karl. Yes, this seems like > Graham> it could be a problem. I've had a look for places > Graham> where I might be doing such a pipe. Do you have any > Graham> examples where this arises? > > Well, there are a couple solutions. The following patch does a > `sudo -v' before every command requiring sudo, even if there is no > pipeline. But you could check for pipeline first if you wish. > > The additional advantage of doing it even without pipeline is that > if sudo authentication fails, currently wajig confuses it with a > failure in the invocation of the command. Thanks Karl. I'll include this in the next release. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320126: wajig: Please use `sudo -v' before using pipelined sudo commands
Received Wed 27 Jul 2005 6:07pm +1000 from Karl Chen: > Package: wajig > Version: 2.0.29 > Severity: normal > > > For some wajig commands, wajig executes "sudo command1 | > sudo command 2...", which is impossible to authenticate > properly. Doing a "sudo -v" before any pipeline solves it. Thanks for the bug report Karl. Yes, this seems like it could be a problem. I've had a look for places where I might be doing such a pipe. Do you have any examples where this arises? Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318048: wajig: During install, bash_completion works only on the first package's name
Thanks for the bug report Kamaraju. I'm currently looking into add the completion as suggested. Received Wed 13 Jul 2005 3:25pm +1000 from Kamaraju Kusumanchi: > Package: wajig > Version: 2.0.29 > Severity: wishlist > > > Hi, >I love wajig and am hoping this would be easy to fix. When I have the > /etc/bash_completion sourced in ~/.bashrc, I can do > > wajig install vim-co > > and it will result in > > wajig install vim-common > > which is great. However, this feature works only on the first packagename and > does not work for subsequent package names. For example, If I do > > wajig install vim-common vim-d > > it does not exapand to > > wajig install vim-common vim-doc > > It would be nice if the auto completion works on all the package names. As a > side note, I would like to mention that, apt-get's bash_completion feature > works > on multiple package names. > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.9-1-686 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.5.28.6 Advanced front-end for dpkg > ii python2.3.5-3An interactive high-level > object-o > ii python-apt0.5.10 Python interface to libapt-pkg > > wajig recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317584: wajig: want installed list that shows distribution
Received Sun 10 Jul 2005 9:25am +1000 from John V. Belmonte: > Package: wajig > Version: 2.0.29 > Severity: wishlist > > I'd like a wajig command that lists installed packages with distribution > info (i.e. stable, testing, unstable), similar to apt-show-versions. Thanks for the suggestion John. Has been implemented as VERSIONS and will be in wajig version 2.0.30. 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#315082: wajig which-pkg doesn't seem to like '+' character in package name
Received Tue 21 Jun 2005 12:09am +1000 from John V. Belmonte: > Package: wajig > Version: 2.0.27 > Severity: normal > > When "wajig which-pkg" is given a package name with the '+' character, it > returns a cryptic message. I expect the following command to yield > libsigc++-1.2-dev, etc. > > $ wajig which-pkg sigc++.h > File Path Package > ===-= > No keyword given for search. Hi John, Thanks for the bug report. The error was in the ++ in the pattern being searched for, and these had to be replaced with %2B. Now works in 2.0.29 - soon to hit the archives (and already at http://wajig.sarovar.org/debian/) Regards, Graham > Versions of packages wajig depends on: > ii apt 0.5.28.6 Advanced front-end for dpkg > ii python2.3.5-2An interactive high-level > object-o > ii python-apt0.5.10 Python interface to libapt-pkg > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314730: wajig: Install new or newupgrade packages
Received Sat 18 Jun 2005 1:10pm +1000 from David Liontooth: > Package: wajig > Version: 2.0.27 > Severity: wishlist > > > It would be very useful to be able to install all new or all newupgrade > packages, > perhaps simply by allowing "install" as a parameter to those commands: > > wajig new install > wajig newupgrade install > > Another solution would be to allow the list of new packages to be piped to a > format > that could be used by wajig install-file. Hi Dave, Thanks for the suggestion. I'm not quite sure I see the use of it! You could achieve it with the following: wajig new | tail +3 | cut -d' ' -f1 | xargs wajig install or wajig newupgrades | tail +3 | cut -d' ' -f1 | xargs wajig install ... it does need extra work and knowledge of the Linux tools. For "new" would you really want to install all of the new packages at any time? I simply cut and past the ones I want onto the command line. For "newupgrades" why would you want to do this rather than "distupgrade"? They are both easy enough to implement, and as a user you obviously would find it useful. So I'll do it! Would like to understand how you find them useful though and I'll document it. Regards, Graham > > Dave > > > -- System Information: > Debian Release: sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.12-rc2 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.5.28.1 Advanced front-end for dpkg > ii python2.3.5-1An interactive high-level > object-o > ii python-apt0.5.10 Python interface to libapt-pkg > > wajig recommends no packages. > > Versions of packages wajig is related to: > ii reportbug 3.13 reports bugs in the Debian > distrib > pn totem-gstreamer(no description available) > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314338: wajig: Messy exit on declined update from bug report
Received Thu 16 Jun 2005 5:39am +1000 from David Liontooth: > Package: wajig > Version: 2.0.24 (reproduced in 2.0.27) > Severity: minor > > > If you have bug report checking turned on, and respond n to an upgrade > because of a bug > report, you get a messy error -- this may be a feature, but spilling the guts > of the > program is of course slightly revolting to non-surgeons... Hi David, Thanks for the report. I've recently started using apt-listbugs but haven't yet bailed out! I'll have a look to see if I can capture the exit gracefully in wajig. Regards, Graham > > > Retrieving bug reports... Done > grave bugs of samba (3.0.10-1 -> 3.0.14a-5) > #304300 - samba: Security update breaks systems > Summary: > samba(1 bug) > Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n > > ** Exit with an error by force in order to stop the installation. ** > > E: Sub-process if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed'; > then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo > 'Warning: apt-listbugs exited abnormally, hitenter key to continue.' 1>&2 ; > read a < /dev/tty ); fi returned an error code (10) > E: Failure running script if dpkg -s apt-listbugs | grep -q '^Status: .* ok > installed'; then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; > echo 'Warning: apt-listbugs exited abnormally, hit enter key to continue.' > 1>&2 ; read a < /dev/tty ); fi > > > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Kernel: Linux 2.6.9 > Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) > > Versions of packages wajig depends on: > ii apt 0.5.25 Advanced front-end for dpkg > ii python2.3-4 An interactive high-level > object-o > ii python-apt0.5.8 Python interface to libapt-pkg > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312949: Using S29hdparm.second didn't work but S39hdparm.second did?
Received Sat 11 Jun 2005 12:21pm +1000 from Stephen Gran: > This one time, at band camp, Graham Williams said: > > I'm using "hdparm -a8 -u" on /dev/hda (a CD/DVD). > > I need to do this so that DVD viewing is smooth > > (at least this is a solution that works) . > > > > Wanted to maintain this over a reboot. > > Editted /etc/hdparm.conf as suggested in README.Debian > > Symlinked /etc/init.d/hdparm to /etc/rcS.d/S29hdparm.second > > Reboot and hdparm settings not taken > > > > Changing to later in init: /etc/rcS.d/S39hdparm.second > > Reboot and hdparm settings have taken! > > Do you use udev? I suppose this is going to be a FAQ at some point. I > don't, so testing is going to be difficult for me. If not, I'll need > some error messages to get any further with this. If so, I suppose it's > because udev hasn't set up the device yet, although it's init script has > run. Yes I do use udev. I had a bit of a look around for any errors but didn't see anything. I used to use hwtools to run hdparm and that is at S60 and never had a problem with it there. I am not familiar with the corruption problem though. If you can suggest anything I can do to help track down the issue, happy to do so. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312949: Using S29hdparm.second didn't work but S39hdparm.second did?
Package: hdparm Version: 6.1-2 Severity: minor I'm using "hdparm -a8 -u" on /dev/hda (a CD/DVD). I need to do this so that DVD viewing is smooth (at least this is a solution that works) . Wanted to maintain this over a reboot. Editted /etc/hdparm.conf as suggested in README.Debian Symlinked /etc/init.d/hdparm to /etc/rcS.d/S29hdparm.second Reboot and hdparm settings not taken Changing to later in init: /etc/rcS.d/S39hdparm.second Reboot and hdparm settings have taken! Regards, Graham -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') 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 hdparm depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311543: wajig: dist-upgrade can have -t option
Received Thu 02 Jun 2005 5:46am +1000 from Graham Williams: > Received Thu 02 Jun 2005 4:09am +1000 from August Mayer: > > Package: wajig > > Version: 2.0.25 > > Severity: wishlist > > > > It is sometimes useful to specify the target archive for dist-upgrade. For > > example, to check whether new archives are in experimental, I would do > > apt-get -t experimental dist-upgrade > > > > However, wajig doesn't take any parameters with its dist-upgrade command. > > Thanks for the suggestion August. I've added support for the > following: > > $ wajig dist-upgrade experimental > > That is, an optional argument to dist-upgrade where you can list the > distribution. This then calls > > $ apt-get -u -t experimental dist-upgrade > > This will be in the next release (2.0.27). P.S. It is now available from deb http://www.togaware.com/debian ./ Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311543: wajig: dist-upgrade can have -t option
Received Thu 02 Jun 2005 4:09am +1000 from August Mayer: > Package: wajig > Version: 2.0.25 > Severity: wishlist > > It is sometimes useful to specify the target archive for dist-upgrade. For > example, to check whether new archives are in experimental, I would do > apt-get -t experimental dist-upgrade > > However, wajig doesn't take any parameters with its dist-upgrade command. Thanks for the suggestion August. I've added support for the following: $ wajig dist-upgrade experimental That is, an optional argument to dist-upgrade where you can list the distribution. This then calls $ apt-get -u -t experimental dist-upgrade This will be in the next release (2.0.27). Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306222: wajig: Add list-scripts command to show package install and remove scripts
Received Tue 26 Apr 2005 12:24pm +1000 from Jerry Quinn: ... > > wajig list-scripts most > > I'd want to see something like: > > package most-2.3-1 scripts > [postinst] > #!/bin/sh > echo "hi there" > > [prerm] > echo "Are you sure" Thanks Jerry. I've implemented this for the next version (2.0.26) of wajig. I've also implemented: $ wajig list-scripts tetex-base_2.0.2-9_i386.deb preinst #!/bin/sh # preinst script for tetex-base [...] exit 0 postinst #!/bin/sh set -e [...] Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302648: wajig: status-match and status fails to show available for installed packages
Received Sat 02 Apr 2005 4:40pm +1000 from David Liontooth: > Package: wajig > Version: 2.0.24 > Severity: minor > > > A persistent error has snuck into recent versions of wajig. When listing > status or > status-match, it doesn't show Previous and Now for installed packages: Hi David, Is this still a problem for you? I've still not been able to replicate it. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306221: wajig: Indicate depend/recommend/suggest on output of dependents command
Received Mon 25 Apr 2005 3:23pm +1000 from Jerry Quinn: > Package: wajig > Version: 2.0.25 > Severity: wishlist > > This would be useful output. I'd just put a letter in front of each > package name. Thanks for the suggestion. This has been implemented and will be released in version 2.0.26: $ wajign dependents less s gzip s man-db s mindi d colormake d console-log s dak r education-common o fdclone d kmtrace d mn-fit d mooix d octave2.0 d rsbac-admin d squidview d topal Regards, Graham > > -- System Information: > Debian Release: 3.1 > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable') > Architecture: i386 (i686) > Kernel: Linux 2.6.10-1-k7 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.5.28.1 Advanced front-end for dpkg > ii python2.3.5-1An interactive high-level > object-o > ii python-apt0.5.10 Python interface to libapt-pkg > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306222: wajig: Add list-scripts command to show package install and remove scripts
Received Mon 25 Apr 2005 3:23pm +1000 from Jerry Quinn: > Package: wajig > Version: 2.0.25 > Severity: wishlist > > I'm looking for an equivalent to rpm -q --scripts . Hi Jerry, Thanks for the bug report. It looks like a useful idea. A little more detail would help me though. What would you expect the output of the command to be. For example, would do you expect from: wajig list-scripts most Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
