public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: For Info - libgudev-238 can't be built
Date: Mon, 10 Jul 2023 18:46:00 +0100	[thread overview]
Message-ID: <586E8701-67FF-44F4-B288-3BCE7D59AC56@ipfire.org> (raw)
In-Reply-To: <924e510b-d82b-8d30-ec90-0a46e72fec33@ipfire.org>

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

Hey,

Thanks for looking into this.

Is there a specific reason why we are not updating to 3.2.12? Just curious here...

  https://github.com/eudev-project/eudev/releases/tag/v3.2.12

For completeness, here is the issue:

  https://github.com/eudev-project/eudev/issues/249

And what do we actually need libgudev for? Do we know this?

-Michael

> On 9 Jul 2023, at 15:51, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> 
> For info, the latest version of libgudev, 238, fails to build because it is looking for a libudev of at least 251 and eudev has version 243.
> 
> This has been reported as an issue to the eudev issues section in github 3 days ago. Someone has tried just changing the version number in the libgudev meson requirements section but then the build fails because there is a new function which has been added in the systemd udev that is not yet in the standalone eudev package.
> 
> I will keep an eye out on the eudev issues page for this.
> 
> 
> Regards,
> 
> 
> Adolf.
> 


  reply	other threads:[~2023-07-10 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 14:51 Adolf Belka
2023-07-10 17:46 ` Michael Tremer [this message]
2023-07-11 13:44   ` Adolf Belka
2023-07-11 13:46     ` Michael Tremer

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=586E8701-67FF-44F4-B288-3BCE7D59AC56@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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