| View previous topic :: View next topic |
| Author |
Message |
phanxen
n00b
Joined: 02 Jan 2022
Posts: 10
Location: Jugoslavija
|
 Posted: Sat Aug 03, 2024 6:22 pm Post subject: Having too frequently "Missing digest for ebuild" |
 |
|
Hi, recently I'm having quite frequently "Missing digest for ebuild" error messages running emerge command. Usually, I solve this issue using the following command (it shows a concrete example I'm dealing with):
| Code: |
$ sudo ebuild /var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-11.5.0.ebuild manifest
>>> Creating Manifest for /var/db/repos/crossdev/cross-arm-none-eabi/gcc
|
After that I can run emerge again and everything goes fine. However, after a while using emerge again, the missing digest problem comes back. What could be the reason.
Today, for instance, this what I got after synchronizing and trying to update my system:
| Code: |
* IMPORTANT: 2 news items need reading for repository 'dlang'.
* IMPORTANT: 40 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-11.5.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/binutils/binutils-2.42-r2.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/binutils/binutils-9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/binutils/binutils-2.43.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240728.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240721.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240714-r1.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240714.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.3.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.2.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.1.1_p20240729.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.1.1_p20240727.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.1.1_p20240723.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.1.1_p20240720.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.1.1_p20240713.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.1.1_p20240622.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.4.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240802.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240726.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240719.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240712.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240614.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.2.1_p20240210.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.2.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.5.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.1_p20240801.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.1_p20240725.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.1_p20240711.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.3.1_p20240209.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-11.4.1_p20240501.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-10.5.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-9.5.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-8.5.0-r1.ebuild'
|
_________________
:.P.h.A.n.X.e.N.: |
|
| Back to top |
|
 |
Banana
Moderator
Joined: 21 May 2004
Posts: 1729
Location: Germany
|
|
| Back to top |
|
|
bstaletic
Guru
Joined: 05 Apr 2014
Posts: 373
|
| Posted: Sun Aug 04, 2024 9:15 am Post subject: |
|
|
| Banana wrote: | | Those are no official gentoo repos, aren't they? |
The crossdev repo is created by sys-devel/crossdev when setting up a new cross compiling toolchain.
It creates something like /var/db/repos/crossdev/cross-arm-none-eabi/gcc/
If I remember correctly, the crossdev/cross-arm-none-eabi/gcc is a symlink to gentoo/sys-devel/gcc.
After the initial setup of the crossdev/cross-arm-none-eabi, emerge can be used as usual to update the new toolchain.
All that said, I have never had to manually generate manifests for crossdev ebuilds. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22649
|
| Posted: Sun Aug 04, 2024 2:14 pm Post subject: |
|
|
If /var/db/repos/crossdev/cross-arm-none-eabi/gcc is a symlink to $PORTDIR/sys-devel/gcc, then the manifests that OP generates will be written under $PORTDIR, and would be subject to modification/deletion during the next emerge --sync, which would explain why they break after a time. It does not explain why OP needs to generate the manifests at all. If that path is a symlink into $PORTDIR, then the manifests distributed with Portage ought to suffice.
To confirm, OP, what is the output of namei -l /var/db/repos/crossdev/cross-arm-none-eabi/gcc/? |
|
| Back to top |
|
|
phanxen
n00b
Joined: 02 Jan 2022
Posts: 10
Location: Jugoslavija
|
| Posted: Tue Oct 01, 2024 10:00 pm Post subject: |
|
|
| Hu wrote: | If /var/db/repos/crossdev/cross-arm-none-eabi/gcc is a symlink to $PORTDIR/sys-devel/gcc, then the manifests that OP generates will be written under $PORTDIR, and would be subject to modification/deletion during the next emerge --sync, which would explain why they break after a time. It does not explain why OP needs to generate the manifests at all. If that path is a symlink into $PORTDIR, then the manifests distributed with Portage ought to suffice.
To confirm, OP, what is the output of namei -l /var/db/repos/crossdev/cross-arm-none-eabi/gcc/? |
Hi Hu, thanks for your explanation. It makes sense. 
Here is the output of namei -l /var/db/repos/crossdev/cross-arm-none-eabi/gcc/:
| Code: | $ namei -l /var/db/repos/crossdev/cross-arm-none-eabi/gcc
f: /var/db/repos/crossdev/cross-arm-none-eabi/gcc
drwxr-xr-x root root /
drwxr-xr-x root root var
drwxr-xr-x root root db
drwxr-xr-x root root repos
drwxr-xr-x portage portage crossdev
drwxr-xr-x root root cross-arm-none-eabi
lrwxrwxrwx root root gcc -> /var/db/repos/gentoo/sys-devel/gcc
drwxr-xr-x root root /
drwxr-xr-x root root var
drwxr-xr-x root root db
drwxr-xr-x root root repos
drwxr-xr-x root root gentoo
drwxr-xr-x root root sys-devel
drwxr-xr-x root root gcc
|
Following your explanation about $PORTDIR, I would say, if I'm not mistaken, that things are as expected:
| Code: | $ ls /var/db/repos/crossdev/cross-arm-none-eabi/gcc -la
lrwxrwxrwx 1 root root 34 Apr 8 2022 /var/db/repos/crossdev/cross-arm-none-eabi/gcc -> /var/db/repos/gentoo/sys-devel/gcc |
On the other hand, when I posted this question the first time I had lots of messages to eread. I read all of them, and kept the system updated. Today, once again, I had the same problem with missing digest:
| Code: | $ sudo emerge -quvaND @world
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-11.5.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240929.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240922-r2.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240922.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240915.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-15.0.0_pre20240908.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.3.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.2.1_p20240928.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.2.1_p20240921.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-14.2.1_p20240817.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.4.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240927.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240920.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.3.1_p20240614.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-13.2.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.5.9999.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.1_p20240926.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.1_p20240919.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-12.4.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-10.5.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-9.5.0.ebuild'
* Missing digest for '/var/db/repos/crossdev/cross-arm-none-eabi/gcc/gcc-8.5.0-r1.ebuild'
[ebuild U ] app-portage/elt-patches-20240912 [20240824]
[ebuild U ] dev-libs/openssl-3.3.2 [3.0.15] USE="asm quic%* -fips -ktls -rfc3779 -sctp -static-libs -test -tls-compression -vanilla -verify-sig -weak-ssl-ciphers" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="(sse2)"
(...)
|
_________________
:.P.h.A.n.X.e.N.: |
|
| Back to top |
|
|
Spankin Partier
n00b
Joined: 15 Jan 2007
Posts: 34
|
| Posted: Tue Oct 15, 2024 11:26 pm Post subject: |
|
|
Not sure if you got this resolved or not. I just ran into the same problem over the weekend and found the cause/solution for my system. On the Gentoo Wiki for setting up the Arduino development platform they say we need to add 'thin-manifests = true' to the /var/db/repos/portage-crossdev/metadata/layout.conf file when using Git for synchronizing Portage. Link
It just so happened I switched to Git to improve my sync performance and shortly afterwards, these errors started. |
|
| 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
|
|
Other Things Gentoo
