>> I have some hardware that update-grub just doesn't understand > > Please report a bug about it if you haven't done that yet.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861053 >> a locally modified lilo that has support for it. > >Is the modification likely to be break lilo for other folks or is it >suitable for distribution in the Debian package? I knocked out the sanity check preventing it from being installed on my RAID array. If I did it for distribution I'd have it actually check if the RAID array is RAID 1 (as no other will function). I have less resources than Joachim Wiedorn , but it looks like maintaining lilo is very little work. The upstream source (same person) had its last release in 2015. On 12/21/19, Paul Wise <p...@debian.org> wrote: > On Sat, Dec 21, 2019 at 5:21 AM Joshua Hudson wrote: > >> Basically, the existing package maintainer doesn't want to maintain >> lilo anymore, says "will disappear by end of 2020" > > You might want to read through the thread about this if you haven't yet: > > https://lists.debian.org/msgid-search/20191111193422.2852b...@jupiter.home > >> I have some hardware that update-grub just doesn't understand > > Please report a bug about it if you haven't done that yet. > >> a locally modified lilo that has support for it. > > Is the modification likely to be break lilo for other folks or is it > suitable for distribution in the Debian package? > >> I want to take over lilo maitenance so that apt-get update integration >> continues to work. > > Please contact the current lilo maintainer about this and also read > through these documents: > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#adopting-a-package > https://mentors.debian.net/intro-maintainers > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise >
