Bastian Blank <[EMAIL PROTECTED]> writes:
> On Sat, Apr 22, 2006 at 08:33:38PM +0200, Andreas Barth wrote:
>> A combination of a working patch in the most current point release,
>> documentation in the etch release notes and a conflict with the current
>> package in sarge might however do the tric
* Bastian Blank ([EMAIL PROTECTED]) [060428 22:50]:
> On Sat, Apr 22, 2006 at 08:33:38PM +0200, Andreas Barth wrote:
> > A combination of a working patch in the most current point release,
> > documentation in the etch release notes and a conflict with the current
> > package in sarge might however
Dear Bastian Blank,
> The attached patch is a port of my original patch to the version in
> sarge.
> diff -u grub-0.95+cvs20040624/debian/changelog
> grub-0.95+cvs20040624/debian/changelog
> --- grub-0.95+cvs20040624/debian/changelog
> +++ grub-0.95+cvs20040624/debian/changelog
> @@ -1,3 +1,9 @@
On Sat, Apr 22, 2006 at 08:33:38PM +0200, Andreas Barth wrote:
> A combination of a working patch in the most current point release,
> documentation in the etch release notes and a conflict with the current
> package in sarge might however do the trick.
Dear grub maintainers
Can you please prepar
* Martin Schulze ([EMAIL PROTECTED]) [060422 11:17]:
> Bastian Blank wrote:
> > On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote:
> > > waldi why not add your patch to update-grub to the next stable release?
>
> Please keep in mind that you can't rely on a current sarge installati
Martin Schulze wrote:
> Bastian Blank wrote:
> > On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote:
> > > waldi why not add your patch to update-grub to the next stable release?
>
> Please keep in mind that you can't rely on a current sarge installation
> when it is upgraded to etc
Bastian Blank wrote:
> On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote:
> > waldi why not add your patch to update-grub to the next stable release?
Please keep in mind that you can't rely on a current sarge installation
when it is upgraded to etch, in other words, you can't depen
On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote:
> waldi why not add your patch to update-grub to the next stable release?
> kernel-package 8 should be able to cope with the stderr output, no?
Yeah should work, but this have to be checked.
Bastian
--
Suffocating together ... w
On Mon, 17 Apr 2006, Andreas Metzler wrote:
> At short glance the respective changes in update-grub seem to be like
> this:
> -echo -n "Searching for splash image... "
> +echo -n "Searching for splash image ... " >&2
> i.e. the newer update-grub is simply sending to stderr instead of
> stdout.
>
On 17 Apr 2006, Andreas Barth wrote:
>> kernel-package >> 10 uses debconf for the user communication. This
>> includes the pre and post scripts specified in
>> /etc/kernel-img.conf. update-grub from grub older than 0.97-3
>> writes informations to stdout, which is coupled to debconf and
>> makes
On 2006-04-17 Sven Luther <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 17, 2006 at 12:52:11PM +0200, Andreas Metzler wrote:
[...]
> > This afaik could be solved be redirecting stdout to stderr in the
> > *invocation* of update-grub in the kernel's maintainerscripts.
> > But I am sure I am missing som
On Mon, Apr 17, 2006 at 01:51:30PM +0100, Colin Watson wrote:
> On Mon, Apr 17, 2006 at 11:38:54AM +0200, Bastian Blank wrote:
> > On Sun, Apr 16, 2006 at 09:59:55PM -0700, Steve Langasek wrote:
> > > On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
> > > > For sarge updates of the li
On Mon, Apr 17, 2006 at 12:52:11PM +0200, Andreas Metzler wrote:
> On 2006-04-17 Bastian Blank <[EMAIL PROTECTED]> wrote:
> > On Mon, Apr 17, 2006 at 12:09:27PM +0200, Andreas Metzler wrote:
> >>> kernel-package >> 10 uses debconf for the user communication. This
> >>> includes the pre and post scr
* Bastian Blank ([EMAIL PROTECTED]) [060417 11:39]:
> On Sun, Apr 16, 2006 at 09:59:55PM -0700, Steve Langasek wrote:
> > On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
> >
> > > For sarge updates of the linux kernels, grub needs to be updated before
> > > linux-image*. Can this be
On Mon, Apr 17, 2006 at 11:38:54AM +0200, Bastian Blank wrote:
> On Sun, Apr 16, 2006 at 09:59:55PM -0700, Steve Langasek wrote:
> > On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
> > > For sarge updates of the linux kernels, grub needs to be updated before
> > > linux-image*. Can t
On 2006-04-17 Bastian Blank <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 17, 2006 at 12:09:27PM +0200, Andreas Metzler wrote:
>>> kernel-package >> 10 uses debconf for the user communication. This
>>> includes the pre and post scripts specified in /etc/kernel-img.conf.
>>> update-grub from grub older t
On Mon, Apr 17, 2006 at 12:09:27PM +0200, Andreas Metzler wrote:
> > kernel-package >> 10 uses debconf for the user communication. This
> > includes the pre and post scripts specified in /etc/kernel-img.conf.
> > update-grub from grub older than 0.97-3 writes informations to stdout,
> > which is co
On 2006-04-17 Bastian Blank <[EMAIL PROTECTED]> wrote:
> On Sun, Apr 16, 2006 at 09:59:55PM -0700, Steve Langasek wrote:
>> On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
>>> For sarge updates of the linux kernels, grub needs to be updated before
>>> linux-image*. Can this be forced
On Sun, Apr 16, 2006 at 09:59:55PM -0700, Steve Langasek wrote:
> On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
>
> > For sarge updates of the linux kernels, grub needs to be updated before
> > linux-image*. Can this be forced by an conflict with older versions? A
> > dependency i
On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank <[EMAIL PROTECTED]>
wrote:
> Hi folks
>
> For sarge updates of the linux kernels, grub needs to be updated before
> linux-image*. Can this be forced by an conflict with older versions? A
> dependency is not appropriate.
Why does grub have t
On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank wrote:
> For sarge updates of the linux kernels, grub needs to be updated before
> linux-image*. Can this be forced by an conflict with older versions? A
> dependency is not appropriate.
Can you give more detail on why grub needs to be updat
Hi folks
For sarge updates of the linux kernels, grub needs to be updated before
linux-image*. Can this be forced by an conflict with older versions? A
dependency is not appropriate.
Bastian
--
In the strict scientific sense we all feed on death -- even vegetarians.
-- Spock, "W
22 matches
Mail list logo
