Re: Requesting to take over maintenance of lilo
So I updated the bug report, and have requested maintenance of lilo from Joachim. In any case, I'll be on vacation next week. If Joachim says he wants lilo upstream I'd be glad to let him have it, but I don't think he does.
Re: Requesting to take over maintenance of lilo
On Sat, 2019-12-21 at 08:42 -0800, Joshua Hudson wrote: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861053 I think it would be appropriate to add some more information to this bug to make it easier to understand and take action on. These bits of information would help: The output of both these two commands: sudo /usr/sbin/grub-mkconfig -o /root/grub.cfg sudo sh -x /usr/sbin/grub-mkconfig -o /root/grub.cfg The generated grub config file. > 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. Since Joachim is also the upstream maintainer of lilo, it would be a good idea for someone to take over maintaining it upstream too if it is to continue being available for use in Debian. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Requesting to take over maintenance of lilo
Hi, > 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). can you explain why this is necessary? Do you have a raid over the whole device (like /dev/sda + /dev/sdb)? If so, I'd assume you can talk grub into doing what you need by modifying /etc/grub.d/10_linux Does that help? Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Re: Requesting to take over maintenance of lilo
>> 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 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/2019193422.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 >
Re: Requesting to take over maintenance of lilo
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/2019193422.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
Requesting to take over maintenance of lilo
Basically, the existing package maintainer doesn't want to maintain lilo anymore, says "will disappear by end of 2020" But I have some hardware that update-grub just doesn't understand and a locally modified lilo that has support for it. Multiple attempts at fixing update-grub have resulted in merge-disaster every single update to the grub package and it's just not worth trying that anymore. I want to take over lilo maitenance so that apt-get update integration continues to work.
