Your message dated Fri, 9 Dec 2016 20:12:32 +0000
with message-id <[email protected]>
and subject line Re: Bug#741656: grub-common: grub-mkrescue lost its -J flag,
d-i now FTBFS on kfreebsd-*
has caused the Debian Bug report #741656,
regarding grub-common: grub-mkrescue lost its -J flag, d-i now FTBFS on
kfreebsd-*
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.)
--
741656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741656
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-common
Version: 2.02~beta2-7
Severity: serious
File: /usr/bin/grub-mkrescue
Tags: d-i
Justification: triggers FTBFS
Hi,
so there are some grub-* packages used in debian-installer's build-deps,
and grub-common is among them, since grub-mkrescue is used on kfreebsd-*.
It apparently lost its -J flag, making debian-installer FTBFS on those
architectures. Excerpt from a daily build log after 2014-03-10:
| # Create the ISO with Joliet extensions, needed for win32-loader.ini
| grub-mkrescue --output=./tmp/netboot-9/mini.iso ./tmp/netboot-9/cd_tree -J
| grub-mkrescue: invalid option -- 'J'
| Try 'grub-mkrescue --help' or 'grub-mkrescue --usage' for more information.
| make[2]: *** [arch_miniiso] Error 64
Not too nice when I'm about to upload debian-installer for jessie alpha 1. :(
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.02~beta3-1
On Sat, Nov 26, 2016 at 09:56:46PM +0100, Cyril Brulebois wrote:
> Colin Watson <[email protected]> (2016-11-26):
> > Yep, as Thomas said, this changed back to the original state in
> > 2.02~beta3. I think that in fact allows us to close #741656 if you also
> > revert your previous workaround in d-i, but please confirm. Compare:
> >
> >
> > https://anonscm.debian.org/cgit/pkg-grub/grub.git/commit/?id=496cca85259c77b5fc8ad39a9064c83c3a39b7a6
> >
> > (Sorry, I forgot that d-i had worked around this.)
>
> (No worries.)
>
> Yeah, a revert was what I had in mind, but I thought I'd double check
> anyway. Just pushed it, triggered a build on falla and fischer, and
> builds seem happier now. Thanks!
>
> I think this bug report should be closed now?
Indeed, thanks. Done with this message.
--
Colin Watson [[email protected]]
--- End Message ---
