On Tue, Jan 11, 2005 at 07:29:17PM +0100, Bill Allombert wrote:
> On Tue, Jan 11, 2005 at 09:17:36AM -0800, Steve Langasek wrote:
> > Of these packages, one is essential and one is virtually essential. The
> > other two (libgcc1 and libstdc++5) are neither; although in this case they
> > *should*
On Tue, Jan 11, 2005 at 07:29:17PM +0100, Bill Allombert wrote:
> On Tue, Jan 11, 2005 at 09:17:36AM -0800, Steve Langasek wrote:
> > Of these packages, one is essential and one is virtually essential. The
> > other two (libgcc1 and libstdc++5) are neither; although in this case they
> > *should*
On Tue, Jan 11, 2005 at 09:17:36AM -0800, Steve Langasek wrote:
> Of these packages, one is essential and one is virtually essential. The
> other two (libgcc1 and libstdc++5) are neither; although in this case they
> *should* work just fine in a half-configured state, that seems like a hairy
> sol
On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> Adam C Powell IV has reported a problem (bug #289702) when upgrading
> from Woody to Sarge.
> Background:
> The packages below in woody had buggy postinst/postrm scripts that does
> not check whether update-menus was executable befo
On Tue, Jan 11, 2005 at 05:44:26PM +0100, Wouter Verhelst wrote:
> Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> > On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> > > So what would you advise me to do ?
> >
> > Why don't you ship a dummy "update-menus" command? In
On Tue, Jan 11, 2005 at 05:44:26PM +0100, Wouter Verhelst wrote:
> Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> > Why don't you ship a dummy "update-menus" command?
>
> Because that would break other packages.
Sorry if I'm being dumb, but in what way would it break other packages?
On Tue, Jan 11, 2005 at 05:44:26PM +0100, Wouter Verhelst wrote:
> Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> > On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> > > So what would you advise me to do ?
> >
> > Why don't you ship a dummy "update-menus" command? In
Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> > So what would you advise me to do ?
>
> Why don't you ship a dummy "update-menus" command? In the unpacked package,
> the command could be a shell script which does noth
On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> So what would you advise me to do ?
Why don't you ship a dummy "update-menus" command? In the unpacked package,
the command could be a shell script which does nothing. The postinst could
then replace that script with the correct bin
On Tue, Jan 11, 2005 at 09:17:36AM -0800, Steve Langasek wrote:
> Of these packages, one is essential and one is virtually essential. The
> other two (libgcc1 and libstdc++5) are neither; although in this case they
> *should* work just fine in a half-configured state, that seems like a hairy
> sol
Dear debian-release team,
Adam C Powell IV has reported a problem (bug #289702) when upgrading
from Woody to Sarge.
Background:
The packages below in woody had buggy postinst/postrm scripts that does
not check whether update-menus was executable before calling it:
ghostview gwm joe vim-gtk vim-p
On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> Adam C Powell IV has reported a problem (bug #289702) when upgrading
> from Woody to Sarge.
> Background:
> The packages below in woody had buggy postinst/postrm scripts that does
> not check whether update-menus was executable befo
On Tue, Jan 11, 2005 at 05:44:26PM +0100, Wouter Verhelst wrote:
> Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> > On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> > > So what would you advise me to do ?
> >
> > Why don't you ship a dummy "update-menus" command? In
On Tue, Jan 11, 2005 at 05:44:26PM +0100, Wouter Verhelst wrote:
> Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> > Why don't you ship a dummy "update-menus" command?
>
> Because that would break other packages.
Sorry if I'm being dumb, but in what way would it break other packages?
On Tue, Jan 11, 2005 at 05:44:26PM +0100, Wouter Verhelst wrote:
> Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> > On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> > > So what would you advise me to do ?
> >
> > Why don't you ship a dummy "update-menus" command? In
Op di, 11-01-2005 te 17:39 +0100, schreef Richard Atterer:
> On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> > So what would you advise me to do ?
>
> Why don't you ship a dummy "update-menus" command? In the unpacked package,
> the command could be a shell script which does noth
On Tue, Jan 11, 2005 at 05:10:23PM +0100, Bill Allombert wrote:
> So what would you advise me to do ?
Why don't you ship a dummy "update-menus" command? In the unpacked package,
the command could be a shell script which does nothing. The postinst could
then replace that script with the correct bin
Dear debian-release team,
Adam C Powell IV has reported a problem (bug #289702) when upgrading
from Woody to Sarge.
Background:
The packages below in woody had buggy postinst/postrm scripts that does
not check whether update-menus was executable before calling it:
ghostview gwm joe vim-gtk vim-p
18 matches
Mail list logo
