| View previous topic :: View next topic |
| Author |
Message |
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1071
Location: Belgium
|
 Posted: Tue Jun 24, 2025 8:27 pm Post subject: kicad and cryfs: strange dependency and failure (solved) |
 |
|
This morning (EU time) I tried to emerge kicad. I had some use flags to change but nothing out of the ordinary (boost needed python and wxgtk needed gstreamer). So I made the needed entries in /etc/portage/package.use and started first ran "emerge --pretend kicad". One of the packages listed with "U" was cryfs. At that time I did not take notice of it, there were several packages that needed an update. All went well until it came to cryfs, below the /var/tmp/portage/sys.fs/cryfs-1.0.1/build.log:
| Code: | >>> Downloading 'http://distfiles.gentoo.org/distfiles/f1/cryfs-1.0.1.tar.gz'
--2025-06-24 11:43:40-- http://distfiles.gentoo.org/distfiles/f1/cryfs-1.0.1.tar.gz
Resolving distfiles.gentoo.org... 2a02:6ea0:c700::101, 2a02:6ea0:c700::19, 2a02:6ea0:c700::11, ...
Connecting to distfiles.gentoo.org|2a02:6ea0:c700::101|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2025-06-24 11:43:42 ERROR 404: Not Found.
>>> Downloading 'https://github.com/cryfs/cryfs/archive/refs/tags/1.0.1.tar.gz'
--2025-06-24 11:43:43-- https://github.com/cryfs/cryfs/archive/refs/tags/1.0.1.tar.gz
Resolving github.com... 140.82.121.3
Connecting to github.com|140.82.121.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/cryfs/cryfs/tar.gz/refs/tags/1.0.1 [following]
--2025-06-24 11:43:43-- https://codeload.github.com/cryfs/cryfs/tar.gz/refs/tags/1.0.1
Resolving codeload.github.com... 140.82.121.9
Connecting to codeload.github.com|140.82.121.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘/var/cache/distfiles/cryfs-1.0.1.tar.gz.__download__’
/var/cach [<=> ] 0 --.-KB/s
/var/cache [ <=> ] 1.71M 8.55MB/s
/var/cache/ [ <=> ] 3.85M 9.61MB/s
/var/cache/d [ <=> ] 5.98M 9.96MB/s
/var/cache/di [ <=> ] 8.11M 10.1MB/s
/var/cache/distfile [ <=> ] 9.09M 10.2MB/s in 0.9s
2025-06-24 11:43:44 (10.2 MB/s) - ‘/var/cache/distfiles/cryfs-1.0.1.tar.gz.__download__’ saved [9527521]
!!! Fetched file: cryfs-1.0.1.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got: 9527521
!!! Expected: 9527514
Refetching... File renamed to '/var/cache/distfiles/cryfs-1.0.1.tar.gz._checksum_failure_.vs8w6xyd'
!!! Couldn't download 'cryfs-1.0.1.tar.gz'. Aborting. |
Not being able to download the distfile is new for me in all the years. Looked on the forum but nothing about it. I started to write a post here but I had to leave for a meeting so I saved the build/log and shut the pc down.
Now I returned, ran "emerge --pretend kicad" again and was surprised that cryfs was not in the list anymore. So I ran "emerge kicad" it ran ok. I can start Kicad and it doesn't complain so far. I admit I still have to learn and go further with it. But I'm left with the following questions:
What triggered the cryfs update and how bad is it that it isn't updated?
| Code: | daw ~ # equery depends boost
* These packages depend on boost:
app-text/libabw-0.1.3 (dev-libs/boost)
app-text/libebook-0.1.3-r3 (dev-libs/boost)
app-text/libepubgen-0.1.1-r1 (dev-libs/boost)
app-text/libetonyek-0.1.10-r2 (dev-libs/boost)
app-text/libmspub-0.1.4 (dev-libs/boost)
app-text/libqxp-0.0.2 (dev-libs/boost)
app-text/libwpd-0.10.3 (dev-libs/boost)
app-text/libwpg-0.3.4 (dev-libs/boost)
app-text/poppler-24.11.0-r1 (>=dev-libs/boost-1.74)
dev-cpp/cairomm-1.14.4 (test ? dev-libs/boost[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
dev-cpp/eigen-3.4.0-r3 (boost ? dev-libs/boost)
dev-cpp/libcmis-0.6.2 (dev-libs/boost)
(dev-libs/boost)
dev-lang/swig-4.2.1 (test ? dev-libs/boost)
dev-libs/libixion-0.19.0-r1 (dev-libs/boost)
(dev-libs/boost)
dev-libs/liborcus-0.19.2 (dev-libs/boost[zlib(+)])
(dev-libs/boost[zlib(+)])
dev-libs/librevenge-0.0.5 (dev-libs/boost)
dev-libs/libsigc++-2.12.0 (test ? dev-libs/boost[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
dev-python/pybind11-2.13.6 (test ? dev-libs/boost)
dev-util/codeblocks-20.03_p13518 (contrib ? dev-libs/boost)
(contrib ? dev-libs/boost)
dev-util/mdds-2.1.1 (dev-libs/boost)
(dev-libs/boost)
kde-misc/kdiff3-1.12.0 (>=dev-libs/boost-1.82)
kde-plasma/kactivitymanagerd-6.2.5 (dev-libs/boost)
kde-plasma/plasma-activities-6.2.5 (dev-libs/boost)
kde-plasma/plasma-activities-stats-6.2.5 (test ? dev-libs/boost)
kde-plasma/plasma-desktop-6.2.5-r1 (dev-libs/boost)
media-gfx/inkscape-1.4-r1 (dev-libs/boost[stacktrace(-)])
(dev-libs/boost[stacktrace(-)])
media-libs/libcdr-0.1.8 (dev-libs/boost)
media-libs/libfreehand-0.1.2-r1 (dev-libs/boost)
media-libs/libpagemaker-0.0.4-r1 (dev-libs/boost)
media-libs/libvisio-0.1.7 (dev-libs/boost)
media-libs/libzmf-0.0.2-r1 (dev-libs/boost)
media-libs/lvtk-1.2.0-r2 (dev-libs/boost)
(dev-libs/boost)
net-ftp/filezilla-3.67.1 (>=dev-libs/boost-1.76.0)
(>=dev-libs/boost-1.76.0)
net-libs/kdsoap-2.2.0-r1 (dev-libs/boost)
sci-electronics/kicad-9.0.0-r1 (dev-libs/boost[context,nls])
(python_single_target_python3_10 ? dev-libs/boost[context,nls,python,python_targets_python3_10(-)])
(python_single_target_python3_11 ? dev-libs/boost[context,nls,python,python_targets_python3_11(-)])
(python_single_target_python3_12 ? dev-libs/boost[context,nls,python,python_targets_python3_12(-)])
(dev-libs/boost[context,nls])
(python_single_target_python3_10 ? dev-libs/boost[context,nls,python,python_targets_python3_10(-)])
(python_single_target_python3_11 ? dev-libs/boost[context,nls,python,python_targets_python3_11(-)])
(python_single_target_python3_12 ? dev-libs/boost[context,nls,python,python_targets_python3_12(-)])
sys-fs/cryfs-0.11.4 (dev-libs/boost)
(dev-libs/boost)
daw ~ #
|
So if this is the reason for the cryfs update then I'm very likely safe as I don't need plasma-vault for lxde.
_________________
Expert in non-working solutions
Last edited by Spanik on Wed Jun 25, 2025 6:18 pm; edited 1 time in total |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31734
Location: here
|
| Posted: Wed Jun 25, 2025 8:16 am Post subject: |
|
|
Moved from Kernel & Hardware to Portage & Programming.
_________________
Questions are guaranteed in life; Answers aren't.
"Those who would give up essential liberty to purchase a little temporary safety,
deserve neither liberty nor safety."
- Ben Franklin
https://www.news.admin.ch/it/nsb?id=103968 |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4833
Location: Germany
|
| Posted: Wed Jun 25, 2025 11:00 am Post subject: |
|
|
Spanik,
you should sync the repo (emerge --sync) and update @world first, before install new packages.
The cryfs-1.0.1-r1.ebuild has a change in SRC_URI
it was fixed in April, see https://bugs.gentoo.org/955073
This means: | Code: | emerge --sync
emerge -avuDU @world
emerge -a --depclean
eclean-dist -d |
should help :) |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1071
Location: Belgium
|
| Posted: Wed Jun 25, 2025 6:18 pm Post subject: |
|
|
Oh right, thank for pointing that out. Didn't do it this time because I just wanted to give it a go to see if it could replace my aging version of Eagle.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
