Your message dated Tue, 7 Apr 2009 21:26:22 +1000
with message-id <[email protected]>
and subject line Re: Bug#385318: wajig: This perhaps needs more explanation,
but it's not a bug
has caused the Debian Bug report #385318,
regarding wajig: install/dist doesn't seem to work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
385318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385318
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wajig
Version: 2.0.34
Severity: normal
If I run
wajig install/unstable debtags-edit
on my etch system, I'm told I already have the newest version, but
it's not true! I had 1.1.2+b2, and 1.1.3 was in unstable.
Just to check it wasn't a dependency problem, I manually downloaded
and installed 1.1.3, and it worked fine; I didn't need to update
anything else.
Hence, it seems that there's something wrong with wajig. I have had
this problem before, but didn't have time to test dependencies and so
forth to check it really was a bug and not just an unclear error.
-- 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 python 2.3.5-11 An interactive high-level object-o
ii python-apt 0.6.19 Python interface to libapt-pkg
wajig recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I added a comment in the docs.
Thanks (sorry for slowness in closing...)
Received Wed 26 Sep 2007 10:31pm +1000 from Reuben Thomas:
> Package: wajig
> Version: 2.0.37
> Followup-For: Bug #385318
>
> Actually, install/<DISTRIBUTION> works fine, but only if you have that
> distribution in your /etc/apt/sources.list. Maybe it's worth
> explaining that somewhere in the documentation. It's also probably
> worth explaining the use of pinning to make sure that you don't simply
> get the newest packages all the time (in which case you may as well
> run unstable).
>
> I'm not sure if there's an official Debian document on this subject; I
> found a useful page at
>
> http://jaqque.sbih.org/kplug/apt-pinning.html
>
> My only reservation is the suggestion that you can usefully mix
> stable, testing and unstable, which is fine until the first libc
> transition after stable is released. I run testing with some unstable
> and occasionally experimental mixed in, which is a bit more workable.
>
> Anyway, you can close this bug.
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers testing
> APT policy: (700, 'testing'), (600, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.21-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/dash
>
> Versions of packages wajig depends on:
> ii apt 0.7.6 Advanced front-end for dpkg
> ii dselect 1.14.6 user tool to manage Debian
> package
> ii python 2.4.4-6 An interactive high-level
> object-o
> ii python-apt 0.7.3.1 Python interface to libapt-pkg
> ii python-central 0.5.15 register and build utility for
> Pyt
>
> wajig recommends no packages.
>
> -- no debconf information
>
>
>
--- End Message ---
