public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Failure to build clamav due to rust reversion
Date: Fri, 30 Aug 2024 10:37:25 +0200	[thread overview]
Message-ID: <074bd2c0-db51-4ea9-99d7-8b7db5580ae7@ipfire.org> (raw)
In-Reply-To: <4294a345-52f8-460e-b4af-8abdb7bb1652@ipfire.org>

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

On 29.08.2024 23:17, Adolf Belka wrote:
> Hi Matthias,

Hi Adolf,

> On 29/08/2024 19:18, Matthias Fischer wrote:
>> On 29.08.2024 15:24, Adolf Belka wrote:
>>> Hi All,
>> 
>> Hi,
>> 
>>> On 29/08/2024 15:04, Adolf Belka wrote:
>>>> Hi Michael & Matthias,
>>>>
>>>> I just re-ran my build after the removal of the coreutils patch.
>>>>
>>>> The build went past coreutils with no problem. However it has then failed at clamav (1.4.0) with the message

>>>> ...

[some stuff shortened]

>>> Looking through clamav, I can't find a way to easily tell clamav to use the rust-home version that is in IPFire. Hopefully Matthias with his knowledge of building clamav with rust can find a way.
>> 
>> Sorry Adolf, but I fear, I'm not *that* experienced... ;-)
> 
> I had a look through and found the rust source from 1.65.0 and I created a patch to change the home directory contents in the clamav source tarball to the version of home-0.5.3 instead of 0.5.5 which requires a min rust of 0.70.1 or similar.

First attempt...

> That resulted in the next fail where the rust-which package was asking for a minimum home version of 0.5.5

Next failure...

> So then I created another patch to modify the rust-which version requirement for home to 0.5.3

Oh my...

> Then the build failed again with a message that home has to be > 0.5.3 and that is locked to version 0.5.9 but I can't find where that requirement is specified and I have the feeling this will become like going down the rabbit hole in Alice in Wonderland, so I am giving up at this point.

Could that be 'Cargo.lock' (line 465ff) or 'Cargo.toml' (line 12ff)?

But: WOW! You have my fullest sympathy and respect! But this was what I
expected - and I still think its not worth it, the efforts and work are
too extensive.

> There were no CVE fixes in clamav-1.4.0 so I think we can just wait for rust to be updated.

FULL ACK!

Best
Matthias

> Regards,
> 
> Adolf.
> 
>> 
>> I wouldn't want to temper with this and revert 'clamav', too.
>> 
>> Best
>> Matthias
>> 
>>> Regards,
>>>
>>> Adolf.
>>>
>>>> Regards,
>>>>
>>>> Adolf.
>>>>
>> 


  reply	other threads:[~2024-08-30  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 13:04 Adolf Belka
2024-08-29 13:24 ` Adolf Belka
2024-08-29 13:55   ` Michael Tremer
2024-08-29 18:06     ` Adolf Belka
2024-08-29 17:18   ` Matthias Fischer
2024-08-29 21:17     ` Adolf Belka
2024-08-30  8:37       ` Matthias Fischer [this message]
2024-08-30 15:39         ` 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=074bd2c0-db51-4ea9-99d7-8b7db5580ae7@ipfire.org \
    --to=matthias.fischer@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