pross / pross-overlay Goto Github PK

Hi Simon, seems the metadata needs to be rebuilt:

Total: 1 package (1 in new slot), Size of downloads: 219 KiB

Would you like to merge these packages? [Yes/No] y

>>> Verifying ebuild manifests

!!! Digest verification failed:
!!! /mnt/ext4_STORAGE/var/lib/layman/pross/sys-kernel/ck-sources/metadata.xml
!!! Reason: Filesize does not match recorded size
!!! Got: 400
!!! Expected: 568

Happy Holidays!

ck-sources-5.10.2 fails with the full message below:

`root@Q6600: ~# emerge -av ck-sources

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild NS #] sys-kernel/ck-sources-5.10.2:5.10.2::pross [5.9.12:5.9.12::pross, 5.9.13:5.9.13::pross, 5.9.14:5.9.14::pross] USE="-build -symlink" 0 KiB

Total: 1 package (1 in new slot), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No]

Verifying ebuild manifests

Emerging (1 of 1) sys-kernel/ck-sources-5.10.2::pross

• patch-5.10.2.xz BLAKE2B SHA512 size ;-) ... [ ok ]
• linux-5.10.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]

Preparing to unpack ...
Unpacking source...
Unpacking linux-5.10.tar.xz to /var/tmp/portage/sys-kernel/ck-sources-5.10.2/work
/var/tmp/portage/sys-kernel/ck-sources-5.10.2/temp/environment: line 2718: 10#: invalid integer constant (error token is "10#")

• The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
• is known to be triggered by things such as failed variable assignments
• (bug #190128) or bad substitution errors (bug #200313). Normally, before
• exiting, bash should have displayed an error message above. If bash did
• not produce an error message above, it's possible that the ebuild has
• called exit when it should have called die instead. This behavior
• may also be triggered by a corrupt bash binary or a hardware problem
• such as memory or cpu malfunction. If the problem is not reproducible or
• it appears to occur randomly, then it is likely to be triggered by a
• hardware problem. If you suspect a hardware problem then you should try
• some basic hardware diagnostics such as memtest. Please do not report
• this as a bug unless it is consistently reproducible and you are sure
• that your bash binary and hardware are functioning properly.

Failed to emerge sys-kernel/ck-sources-5.10.2, Log file:

'/var/log/portage/sys-kernel:ck-sources-5.10.2:20201227-115344.log'

• Messages for package sys-kernel/ck-sources-5.10.2:

• Log file: /var/log/portage/sys-kernel:ck-sources-5.10.2:20201227-115344.log

• The ebuild phase 'unpack' has exited unexpectedly. This type of behavior

• is known to be triggered by things such as failed variable assignments

• (bug #190128) or bad substitution errors (bug #200313). Normally, before

• exiting, bash should have displayed an error message above. If bash did

• not produce an error message above, it's possible that the ebuild has

• called exit when it should have called die instead. This behavior

• may also be triggered by a corrupt bash binary or a hardware problem

• such as memory or cpu malfunction. If the problem is not reproducible or

• it appears to occur randomly, then it is likely to be triggered by a

• hardware problem. If you suspect a hardware problem then you should try

• some basic hardware diagnostics such as memtest. Please do not report

• this as a bug unless it is consistently reproducible and you are sure

• that your bash binary and hardware are functioning properly.`

Calculating dependencies / * ERROR: x11-libs/gtk+-3.24.23-r1::pross failed (depend phase):

• gnome3.eclass could not be found by inherit()
• Call stack:

•            ebuild.sh, line 609:  Called source '/var/lib/layman/pross/x11-libs/gtk+/gtk+-3.24.23-r1.ebuild'
  

• • gtk+-3.24.23-r1.ebuild, line 7: Called inherit 'flag-o-matic' 'gnome3' 'virtualx'

•            ebuild.sh, line 290:  Called die
  

• The specific snippet of code:

•          [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
  

• If you need support, post the output of emerge --info '=x11-libs/gtk+-3.24.23-r1::pross',
• the complete build log and the output of emerge -pqv '=x11-libs/gtk+-3.24.23-r1::pross'.
• Working directory: '/usr/lib/python3.8/site-packages'
• S: '/var/tmp/portage/x11-libs/gtk+-3.24.23-r1/work/gtk+-3.24.23'
  / * ERROR: x11-libs/gtk+-2.24.32-r2::pross failed (depend phase):
• gnome3.eclass could not be found by inherit()
• Call stack:

•            ebuild.sh, line 609:  Called source '/var/lib/layman/pross/x11-libs/gtk+/gtk+-2.24.32-r2.ebuild'
  

• gtk+-2.24.32-r2.ebuild, line 5: Called inherit 'autotools' 'flag-o-matic' 'gnome3' 'readme.gentoo-r1' 'virtualx'

•            ebuild.sh, line 290:  Called die
  

• The specific snippet of code:

•          [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
  

• If you need support, post the output of emerge --info '=x11-libs/gtk+-2.24.32-r2::pross',
• the complete build log and the output of emerge -pqv '=x11-libs/gtk+-2.24.32-r2::pross'.
• Working directory: '/usr/lib/python3.8/site-packages'
• S: '/var/tmp/portage/x11-libs/gtk+-2.24.32-r2/work/gtk+-2.24.32'
  ... done!

Hey Simon, the other bug is closed, so I'm opening this one.

I get this noise from emerge every time I sync and update. I have the entire overlay masked in package.mask, and only ck-sources unmasked, so I don't know why it is complaining. Any idea how to squash the noise?

root@Q6600: ~# emerge -avuDN @world

These are the packages that would be merged, in order:

Calculating dependencies - * ERROR: x11-libs/gtk+-3.24.23-r1::pross failed (depend phase):
 *   gnome3.eclass could not be found by inherit()
 * 
 * Call stack:
 *                ebuild.sh, line 609:  Called source '/mnt/ext4_STORAGE/var/lib/layman/pross/x11-libs/gtk+/gtk+-3.24.23-r1.ebuild'
 *   gtk+-3.24.23-r1.ebuild, line   7:  Called inherit 'flag-o-matic' 'gnome3' 'virtualx'
 *                ebuild.sh, line 290:  Called die
 * The specific snippet of code:                                                                                                                                                              \ *   		[[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
 * 
 * If you need support, post the output of `emerge --info '=x11-libs/gtk+-3.24.23-r1::pross'`,
 * the complete build log and the output of `emerge -pqv '=x11-libs/gtk+-3.24.23-r1::pross'`.
 * Working directory: '/usr/lib/python3.8/site-packages'
 * S: '/var/tmp/portage/x11-libs/gtk+-3.24.23-r1/work/gtk+-3.24.23'                                                                                                                           | * ERROR: x11-libs/gtk+-2.24.32-r2::pross failed (depend phase):
 *   gnome3.eclass could not be found by inherit()
 * 
 * Call stack:
 *                ebuild.sh, line 609:  Called source '/mnt/ext4_STORAGE/var/lib/layman/pross/x11-libs/gtk+/gtk+-2.24.32-r2.ebuild'
 *   gtk+-2.24.32-r2.ebuild, line   5:  Called inherit 'autotools' 'flag-o-matic' 'gnome3' 'readme.gentoo-r1' 'virtualx'
 *                ebuild.sh, line 290:  Called die
 * The specific snippet of code:
 *   		[[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
 * 
 * If you need support, post the output of `emerge --info '=x11-libs/gtk+-2.24.32-r2::pross'`,
 * the complete build log and the output of `emerge -pqv '=x11-libs/gtk+-2.24.32-r2::pross'`.
 * Working directory: '/usr/lib/python3.8/site-packages'
 * S: '/var/tmp/portage/x11-libs/gtk+-2.24.32-r2/work/gtk+-2.24.32' 

Hey Simon, Happy New Year.

Just checking; is there any plan to update ck-sources in your overlay?

The digest for ck-sources needs to be regenerated, emerge is giving me the below error.

!!! Digest verification failed:
!!! /var/lib/layman/pross/sys-kernel/ck-sources/files/0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch
!!! Reason: Filesize does not match recorded size
!!! Got: 3786
!!! Expected: 4671

Manifest for sys-kernel/ck-sources must be regenerated, as it contains information about nonexistent ebuilds, causing Portage to refuse it.