On Mon, May 27, 2002 at 04:55:16AM -0700, Paul Johnson wrote:
> On Mon, May 27, 2002 at 10:32:55AM +0100, Colin Watson wrote:
> > Looks like a locally installed version to me, which makes it Paul's own
> > fault. :-)
>
> Except the only deb I've built myself is pine...
Maybe from some other archi
On Mon, May 27, 2002 at 10:32:55AM +0100, Colin Watson wrote:
> Looks like a locally installed version to me, which makes it Paul's own
> fault. :-)
Except the only deb I've built myself is pine...
--
Baloo
pgp851lpj22wQ.pgp
Description: PGP signature
On Mon, May 27, 2002 at 01:22:40AM -0700, Sean 'Shaleh' Perry wrote:
> On 27-May-2002 Paul Johnson wrote:
> > On Mon, May 27, 2002 at 02:12:08AM -0400, Joey Hess wrote:
> >> [EMAIL PROTECTED]:~>dpkg -S menu/tin
> >> tin: /usr/lib/menu/tin
> >> [EMAIL PROTECTED]:~>dpkg -s tin |grep Version:
> >> Ver
On 27-May-2002 Paul Johnson wrote:
> On Mon, May 27, 2002 at 01:22:40AM -0700, Sean 'Shaleh' Perry wrote:
>> > [EMAIL PROTECTED]:~$ dpkg -S menu/tin
>> > dpkg: *menu/tin* not found.
>> > [EMAIL PROTECTED]:~$ dpkg -s tin |grep Version:
>> > Version: 2:1.5.8-9
>>
>> what is that, potato's version?
On Mon, May 27, 2002 at 01:22:40AM -0700, Sean 'Shaleh' Perry wrote:
> > [EMAIL PROTECTED]:~$ dpkg -S menu/tin
> > dpkg: *menu/tin* not found.
> > [EMAIL PROTECTED]:~$ dpkg -s tin |grep Version:
> > Version: 2:1.5.8-9
>
> what is that, potato's version? Both woody and unstable hae 1.5.12.
I don'
On 27-May-2002 Paul Johnson wrote:
> On Mon, May 27, 2002 at 02:12:08AM -0400, Joey Hess wrote:
>
>> [EMAIL PROTECTED]:~>dpkg -S menu/tin
>> tin: /usr/lib/menu/tin
>> [EMAIL PROTECTED]:~>dpkg -s tin |grep Version:
>> Version: 1:1.5.12.20020311-1
>
> [EMAIL PROTECTED]:~$ dpkg -S menu/tin
> dpkg:
On Mon, May 27, 2002 at 02:12:08AM -0400, Joey Hess wrote:
> [EMAIL PROTECTED]:~>dpkg -S menu/tin
> tin: /usr/lib/menu/tin
> [EMAIL PROTECTED]:~>dpkg -s tin |grep Version:
> Version: 1:1.5.12.20020311-1
[EMAIL PROTECTED]:~$ dpkg -S menu/tin
dpkg: *menu/tin* not found.
[EMAIL PROTECTED]:~$ dpkg -s
Paul Johnson wrote:
> [EMAIL PROTECTED]:/usr/lib/menu$ ls -l mutt tin
> ls: tin: No such file or directory
> -rw-r--r--1 root root 103 Mar 19 05:05 mutt
>
>
> OK, I just didn't see mutt in the menu then. So where's tin? I've
> reinstalled tin, and it's still missing.
[EMAIL PR
> On Sun, May 26, 2002 at 09:10:50AM -0400, Joey Hess wrote:
>
>> [EMAIL PROTECTED]:/usr/lib/menu>ls -l mutt tin
>> -rw-r--r--1 root root 103 Mar 19 08:05 mutt
>> -rw-r--r--1 root root 102 Mar 16 20:45 tin
>
> [EMAIL PROTECTED]:/usr/lib/menu$ ls -l mutt tin
> ls:
On Sun, May 26, 2002 at 09:10:50AM -0400, Joey Hess wrote:
> [EMAIL PROTECTED]:/usr/lib/menu>ls -l mutt tin
> -rw-r--r--1 root root 103 Mar 19 08:05 mutt
> -rw-r--r--1 root root 102 Mar 16 20:45 tin
[EMAIL PROTECTED]:/usr/lib/menu$ ls -l mutt tin
ls: tin: No such
On Sunday 26 May 2002 20:14, Shaul Karl wrote:
> > On Sat, May 25, 2002 at 09:59:45PM -0700, Sean 'Shaleh' Perry wrote:
> > > any package not supporting menu when it should (ie. almost any X app)
> > > is violating policy.
> >
> > The X apps do have this. Console apps that previously did have menu
> On Sat, May 25, 2002 at 09:59:45PM -0700, Sean 'Shaleh' Perry wrote:
>
> > any package not supporting menu when it should (ie. almost any X app) is
> > violating policy.
>
> The X apps do have this. Console apps that previously did have menu
> entries are slowly dropping them for whatever reas
Paul Johnson wrote:
> The X apps do have this. Console apps that previously did have menu
> entries are slowly dropping them for whatever reason, despite the fact
> that it would be reasonable to spawn an xterm and start it there.
> Examples off the top of my head on this one are mutt and tin.
I
On Sat, May 25, 2002 at 09:59:45PM -0700, Sean 'Shaleh' Perry wrote:
> any package not supporting menu when it should (ie. almost any X app) is
> violating policy.
The X apps do have this. Console apps that previously did have menu
entries are slowly dropping them for whatever reason, despite th
On 26-May-2002 Paul Johnson wrote:
> On Sat, May 25, 2002 at 07:41:08PM +0100, Martin Rowe wrote:
>
>> I've recently installed Debian sid on my kids' box and it's running fine,
>> except that the menus (in Blackbox) don't get updated after an apt-get
>> install or dist-upgrade. A manual update-
On Sat, May 25, 2002 at 07:41:08PM +0100, Martin Rowe wrote:
> I've recently installed Debian sid on my kids' box and it's running fine,
> except that the menus (in Blackbox) don't get updated after an apt-get
> install or dist-upgrade. A manual update-menus does the trick, but I'm
> wondering
>
> Can it be that it does not happen automagically because there is a
> ~/.menu directory? Maybe Blackbox handles the menus in some way that
> requires it to be manually updated?
>
no blackbox watches the menu and updates on a timer so updates will get noticed.
I suspect your first question
On 25-May-2002 Martin Rowe wrote:
> Hi all
>
> I've recently installed Debian sid on my kids' box and it's running fine,
> except that the menus (in Blackbox) don't get updated after an apt-get
> install or dist-upgrade. A manual update-menus does the trick, but I'm
> wondering what is missing
> Hi all
>
> I've recently installed Debian sid on my kids' box and it's running fine,
> except that the menus (in Blackbox) don't get updated after an apt-get
> install or dist-upgrade. A manual update-menus does the trick, but I'm
> wondering what is missing for it not to happen automagically
Hi all
I've recently installed Debian sid on my kids' box and it's running fine,
except that the menus (in Blackbox) don't get updated after an apt-get
install or dist-upgrade. A manual update-menus does the trick, but I'm
wondering what is missing for it not to happen automagically. It runs
f
20 matches
Mail list logo
