All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: Glenn Washburn <development@efficientek.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Tobias Powalowski <tobias.powalowski@googlemail.com>
Subject: Re: Arch Linux latest git snapshot has too many issues to be a new release base
Date: Fri, 21 Feb 2025 10:37:30 +0100	[thread overview]
Message-ID: <20250221103730.0b6fe48c@leda.eworm.net> (raw)
In-Reply-To: <20250221013353.20cd3d3a@crass-HP-ZBook-15-G2>


[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]

Glenn Washburn <development@efficientek.com> on Fri, 2025/02/21 01:33:
> > It failed for my co-maintainer in 2 cases:
> > 
> > - loopback device seems to be broken
> > 
> > - encrypted devices is not working anymore for him  
> 
> These two issues are news to me. Were these failed tests using the
> latest security patch series, specifically commit 67f70f70a36b
> (disk/loopback: Reference tracking for the loopback). Other than that,
> I don't think anything has changed for loopback devices in a while and
> I'm not aware of issues for encrypted devices either. The information
> given is too little to be of any use and I'm skeptical that these are
> issues. Can you help in getting to the bottom of these issues? A start
> might be to send a lot more specifics on the what and how of the issues.

First one fixed, actually can not reproduce the second. See the mail from
Michael Chang and answers to that for details. Thanks!
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

  reply	other threads:[~2025-02-21  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 11:27 Arch Linux latest git snapshot has too many issues to be a new release base Tobias Powalowski via Grub-devel
2025-02-21  7:33 ` Glenn Washburn
2025-02-21  9:37   ` Christian Hesse [this message]
2025-02-21  7:55 ` Michael Chang via Grub-devel
2025-02-21  9:01   ` Christian Hesse
2025-02-21  9:19     ` Michael Chang via Grub-devel
2025-02-21  9:33   ` Christian Hesse

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=20250221103730.0b6fe48c@leda.eworm.net \
    --to=list@eworm.de \
    --cc=development@efficientek.com \
    --cc=grub-devel@gnu.org \
    --cc=tobias.powalowski@googlemail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.