Github messages for voidlinux
 help / color / mirror / Atom feed
From: manfred3000 <manfred3000@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] 'dracut' source code and development
Date: Tue, 09 Apr 2024 12:24:17 +0200	[thread overview]
Message-ID: <20240409102417.ACF7D2B1CD@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49750@inbox.vuxu.org>

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

Closed issue by manfred3000 on void-packages repository

https://github.com/void-linux/void-packages/issues/49750

Description:
`dracut` being a mission-critical default package I'm a bit baffled by recent upstream changes:
https://github.com/dracutdevs/dracut/issues/2644
https://github.com/dracut-ng/dracut-ng/

Arch Linux has already adopted the fork:
https://archlinux.org/packages/extra-testing/x86_64/dracut/

Just wanted to raise this as not being a Void issue (yet - and there being too many malicious forks being created recently)...

I'm aware of my choosing a questionable username years ago - so no, this is not a bot-created account or something, I've been a long-time Arch Linux user that didn't want to have to deal with the over-engineered `systemd` any longer and recently switched to the awesome passion project that is Void Linux...

Thank You to everyone involved!

      parent reply	other threads:[~2024-04-09 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07 18:49 [ISSUE] " manfred3000
2024-04-07 19:04 ` classabbyamp
2024-04-09 10:24 ` manfred3000 [this message]

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=20240409102417.ACF7D2B1CD@inbox.vuxu.org \
    --to=manfred3000@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).