Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: grub: update to 2.12.
Date: Mon, 25 Mar 2024 07:43:03 +0100	[thread overview]
Message-ID: <20240325064303.B1C9B21345@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48817@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

New comment by dataCobra on void-packages repository

https://github.com/void-linux/void-packages/pull/48817#issuecomment-2017328415

Comment:
I've tested a bit more and couldn't reproduce my `grub doesn't boot` after update problem.

I need to check a bit more and encourage others to help me if possible.



> > is it enough to create an update message and inform the users about what to do?
> 
> If we can do it in a way that does not require manual intervention, prefer that.

I checked a few more things and to this point couldn't find a way to not require manual intervention from the user when upgrading.

But if somebody has knowledge about that or has some information, I appreciate the help.

  parent reply	other threads:[~2024-03-25  6:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 17:18 [PR PATCH] " dataCobra
2024-02-26  9:41 ` dataCobra
2024-02-26  9:41 ` dataCobra
2024-02-26 19:35 ` dataCobra
2024-03-02 16:30 ` classabbyamp
2024-03-25  6:43 ` dataCobra [this message]
2024-03-25  6:43 ` dataCobra
2024-04-27 13:08 ` classabbyamp
2024-04-27 14:00 ` [PR PATCH] [Updated] " classabbyamp
2024-04-27 14:00 ` classabbyamp
2024-04-27 15:08 ` [PR PATCH] [Updated] " classabbyamp
2024-04-27 15:08 ` classabbyamp
2024-04-27 16:30 ` classabbyamp
2024-04-28 17:40 ` [PR PATCH] [Updated] " classabbyamp
2024-04-28 17:55 ` [PR PATCH] [Merged]: " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240325064303.B1C9B21345@inbox.vuxu.org \
    --to=datacobra@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).