linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: decayhonor@gmail.com
To: Christian Hesse <list@eworm.de>
Cc: linux-lvm@lists.linux.dev
Subject: Re: [packaging] Who packages LVM2 for Manjaro
Date: Mon, 16 Jun 2025 12:13:06 +0400	[thread overview]
Message-ID: <99dc017e-aef9-47b4-97a6-163d8feb7c30@gmail.com> (raw)
In-Reply-To: <20250616093724.734b23ab@leda.eworm.net>

I didn't want anyone to register there, just trying to figure why the 
binary isn't there and how to contribute.
Anyways, here's the answer: 
https://www.reddit.com/r/archlinux/comments/1lcmw93/comment/my1mxvk

Feel free to expand if some vital details are missing.

The thread isn't for the mailing list from this point, I think.

On 6/16/25 11:37 AM, Christian Hesse wrote:
> DeCay <decayhonor@gmail.com> on Mon, 2025/06/16 11:08:
>>       I have a question regarding LVM package for Manjaro Linux. Are you
>> involved in packaging ?
>>
>>       lvmdbusd is missing on my system and I want to understand why. I
>> started from the Manjaro forum:
>> https://forum.manjaro.org/t/no-lvmdbusd-binary-in-lvm2-package/175096
>>
>>       I was told to look at the package's URL, which is
>> https://sourceware.org/lvm2/. I think that it's just a project's site
>> and it's not related to the packaging process in any way.
>>
>>       The packager (Christian Hesse <eworm@archlinux.org>) doesn't
>> response either.
> The packager is Arch Linux developer and not involved with Manjaro,
> thus not interested in registering in that forum to discuss.

  reply	other threads:[~2025-06-16  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  7:08 [packaging] Who packages LVM2 for Manjaro DeCay
2025-06-16  7:37 ` Christian Hesse
2025-06-16  8:13   ` decayhonor [this message]
2025-06-17 12:17     ` Zdenek Kabelac
2025-06-17 14:31       ` decayhonor

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=99dc017e-aef9-47b4-97a6-163d8feb7c30@gmail.com \
    --to=decayhonor@gmail.com \
    --cc=linux-lvm@lists.linux.dev \
    --cc=list@eworm.de \
    /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).