From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: clamav 0.105.1-3 needs rust >1.61
Date: Sat, 19 Nov 2022 16:56:02 +0100 [thread overview]
Message-ID: <5316d26d-7f90-6279-d5bb-31c7323d13aa@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4727 bytes --]
Hi,
...I'd like to have a small problem... ;-)
A few days ago, 'clamav 0.105.1' was updated, again:
=>
https://blog.clamav.net/2022/11/second-clamav-100-release-candidate-and.html
"...[it] was intended to also include bug fixes for the jpeg and tiff
Rust-based libraries that are bundled with the source code tarball.
Unfortunately, those fixes were not all release-ready in time for the
0.105.1-2 packages."
So far, so [oh, forget it!].
Unfortunately, building the third version of 'clamav 0.105.1' with
current 'next' failed:
***SNIP***
...
error: package `tiff v0.8.0` cannot be built because it requires
rustc 1.61.0 or newer, while the currently active rustc version is
1.60.0-nightly.
[193/379] Building C object
libclamav/CMakeFiles/lzma_sdk.dir/7z/7zIn.c.o
[194/379] Building C object
libclamav/CMakeFiles/bytecode_runtime.dir/bytecode_nojit.c.o
[195/379] Building C object
libclamav/CMakeFiles/yara.dir/yara_grammar.c.o
[196/379] Building C object libclamav/CMakeFiles/yara.dir/yara_lexer.c.o
yara_lexer.c:2571:24: warning: 'yy_fatal_error' defined but not used
[-Wunused-function]
yara_lexer.c: In function 'yara_yylex':
yara_lexer.l:263:16: warning: '%s' directive output may be truncated
writing up to 1023 bytes into a region of size 999 [-Wformat-truncation=]
In file included from /usr/include/stdio.h:906,
from yara_lexer.c:32:
/usr/include/bits/stdio2.h:54:10: note: '__builtin___snprintf_chk'
output between 26 and 1049 bytes into a destination of size 1024
54 | return __builtin___snprintf_chk (__s, __n,
__USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 | __glibc_objsize (__s), __fmt,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.
make: *** [clamav:89: /usr/src/log/clamav-0.105.1] Error 1
***SNAP***
Hm. Great.
So I tried the current 'rust 1.65' version.
This time, the building failed because of a rust component:
***SNIP***
...
Finished release [optimized] target(s) in 1.92s
cd /usr/src/cipher-0.3.0 && mkdir -pv
"/usr/share/cargo/registry/cipher-0.3.0" && if
CARGOPATH=/usr/src/cipher-0.3.0/.cargo RUSTC_BOOTSTRAP=1 cargo --offline
metadata --format-version 1 --no-deps | jq -e
".packages[].targets[].kind | any(. == \"lib\")" | grep -q "true" ||
CARGOPATH=/usr/src/cipher-0.3.0/.cargo RUSTC_BOOTSTRAP=1 cargo --offline
metadata --format-version 1 --no-deps | jq -e
".packages[].targets[].kind | any(. == \"rlib\")" | grep -q "true" ||
CARGOPATH=/usr/src/cipher-0.3.0/.cargo RUSTC_BOOTSTRAP=1 cargo --offline
metadata --format-version 1 --no-deps | jq -e
".packages[].targets[].kind | any(. == \"proc-macro\")" | grep -q
"true"; then awk
'/^\\\[((.+\\\.)?((dev|build)-)?dependencies|features)/{f=1;next}
/^\\\[/{f=0}; !f' < Cargo.toml > Cargo.toml.deps &&
CARGOPATH=/usr/src/cipher-0.3.0/.cargo RUSTC_BOOTSTRAP=1 cargo --offline
package -l | grep -wEv "Cargo.(lock|toml.orig)" | xargs -d "\n" cp -v
--parents -a -t /usr/share/cargo/registry/cipher-0.3.0 && install -v -m
644 Cargo.toml.deps /usr/share/cargo/registry/cipher-0.3.0/Cargo.toml &&
echo "{\"files\":{},\"package\":\"\"}" >
/usr/share/cargo/registry/cipher-0.3.0/.cargo-checksum.json; fi && if
true && CARGOPATH=/usr/src/cipher-0.3.0/.cargo RUSTC_BOOTSTRAP=1 cargo
--offline metadata --format-version 1 --no-deps | jq -e
".packages[].targets[].kind | any(. == \"bin\")" | grep -q "true"; then
CARGOPATH=/usr/src/cipher-0.3.0/.cargo RUSTC_BOOTSTRAP=1 cargo --offline
install -Z avoid-dev-deps -j8 --no-track --path .; fi
mkdir: created directory '/usr/share/cargo/registry/cipher-0.3.0'
warning: No (git) VCS found for `/usr/src/cipher-0.3.0`
error: invalid inclusion of reserved file name Cargo.toml.orig in
package source
cp: missing file operand
Try 'cp --help' for more information.
make: *** [rust-cipher:78: /usr/src/log/cipher-0.3.0] Error 123
***SNAP***
Ok, even greater.
Does anyone have an idea to solve this? I can't even find an updated
package for , e.g., 'cipher-0.3.0tar.gz', although apparently I found at
least an updated version (0.4.3) here:
=> https://docs.rs/cipher/latest/cipher/#
But no download links... Hm! Where on earth did 'cipher-0.3.0.tar.gz'
came from?
What makes me a bit nervous though is the fact that if clamav really can
only be made to work with a major rust update, the other rust components
might have to be updated as well. And I found 103 rust*-lfs files...
Any thoughts and hints welcome!
Best,
Matthias
next reply other threads:[~2022-11-19 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 15:56 Matthias Fischer [this message]
2022-11-21 10:44 ` Michael Tremer
2022-11-21 17:19 ` Matthias Fischer
2022-11-21 19:05 ` Matthias Fischer
2022-11-22 15:39 ` Adolf Belka
2022-11-22 16:11 ` Matthias Fischer
2022-11-22 16:38 ` Adolf Belka
2022-11-29 22:24 ` No chance updating rust to 1.65 (was: Re: clamav 0.105.1-3 needs rust >1.61) Matthias Fischer
2023-01-15 19:17 ` clamav 0.105.1-3 needs rust >1.61 Matthias Fischer
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=5316d26d-7f90-6279-d5bb-31c7323d13aa@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