On 4/21/23 23:09, the...@sys-concept.com wrote:
I'm trying "emerge --sync" (few times) but I get this error:
!!! Manifest verification failed:
OpenPGP verification failed:
gpg: Signature made Sat 22 Apr 2023 04:39:56 AM UTC
gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC918
I'm trying "emerge --sync" (few times) but I get this error:
!!! Manifest verification failed:
OpenPGP verification failed:
gpg: Signature made Sat 22 Apr 2023 04:39:56 AM UTC
gpg:using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
gpg: Can't check signature: No public key
Ac
Neil Bothwick wrote:
On Fri, 21 Apr 2023 13:03:51 -0400, Alan Grimes wrote:
I've already pruned everything sus out of my home directory... I'm at a
total loss.. This is insane at this point!!! I've been updating my
system daily hoping that this will be fixed upstream... =(
Have you tried
* Michael Orlitzky:
> The eclass sets S=$WORKDIR at first because it creates a separate
> source tree for each version of ruby that will be built for. [...]
Hm. While that sounds useful for "full Ruby" ebuilds, I don't see how to
circumvent the impact for the particular ebuild I am trying to exte
On Fri, 2023-04-21 at 09:16 +0200, Ralph Seichter wrote:
>
> I tried what you suggested. However, inheriting from ruby-ng.eclass
> introduces an odd problem: For some reason unknown to me, "${S}" no
> longer matches the default value of "${WORKDIR}/${P}", but only what I'd
> expect in "${WORKDIR}"
Neil Bothwick wrote:
> On Fri, 21 Apr 2023 09:55:24 -0500, Dale wrote:
>
Also, I switch to the current kernel, it failed in the same way. It
isn't just the new kernel, it seems to be any of them. I wonder how
hard it is to switch to that other driver. From the wiki page, it
l
On Fri, 21 Apr 2023 13:03:51 -0400, Alan Grimes wrote:
> I've already pruned everything sus out of my home directory... I'm at a
> total loss.. This is insane at this point!!! I've been updating my
> system daily hoping that this will be fixed upstream... =(
>
Have you tried as a different
On Fri, 21 Apr 2023 09:55:24 -0500, Dale wrote:
> >> Also, I switch to the current kernel, it failed in the same way. It
> >> isn't just the new kernel, it seems to be any of them. I wonder how
> >> hard it is to switch to that other driver. From the wiki page, it
> >> looks like a big deal.
Le 21/04/23 à 18:26, Dr Rainer Woitok a tapoté :
> Skimming farther upward reveals the string "x86_64" being derived
> in line "33:" from environment variable "ARCH" which is defined
> in my shell initialization scripts:
>
>export ARCH=$({ arch || uname -m || echo unknown ; } 2> /dev/nul
I've mostly been living on my *cough* windows gaming machine because
chromium STILL spams "Error 11" in all tabs. A 30 second test dumped
bout 415 crash dumps to the log folder. =\
Has ANYONE gotten a handle on this error yet? Any idea what package
causes it? Chromium seems very self-contained
Dr Rainer Woitok wrote:
> Dale,
>
> On Thursday, 2023-04-20 17:36:23 -0500, you wrote:
>
>> ...
>> * Package: x11-drivers/nvidia-drivers-470.182.03:0/470
>> * Repository: mine
> Maybe I'm missing something, but as of today "x11-drivers/nvidia-dri-
> vers" version 470.182.03 is still in the n
Netfab,
On Friday, 2023-04-21 14:43:32 +0200, you wrote:
> ...
> I do not see anything particular in your emerge --info.
> What is your eselect version ?
> > $ eselect --version
$ eselect --version
eselect 1.4.20
Copyright (c) 2005-2020 Gentoo Authors.
Distributed under the terms of
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 11:55, Dale wrote:
>> Did something change with overlays? In the past, I copied the ebuild
>> over to local overlay and ran the ebuild command for the manifest. It
>> downloaded everything that was needed. Now, it seems it doesn't. They
>> add a ste
Neil Bothwick wrote:
> On Fri, 21 Apr 2023 03:58:11 -0500, Dale wrote:
>
>> I did a emerge -ef nvidia-drivers and it still fails. I was hoping that
>> would pick up the needed files. Guess not. I decided to do some more
>> digging. I noticed that the same version is still in the tree. I
>> cop
Neil Bothwick wrote:
> On Thu, 20 Apr 2023 20:33:22 -0500, Dale wrote:
>
>> Also, I switch to the current kernel, it failed in the same way. It
>> isn't just the new kernel, it seems to be any of them. I wonder how
>> hard it is to switch to that other driver. From the wiki page, it looks
>> lik
On Thu, 20 Apr 2023 20:33:22 -0500, Dale wrote:
> Also, I switch to the current kernel, it failed in the same way. It
> isn't just the new kernel, it seems to be any of them. I wonder how
> hard it is to switch to that other driver. From the wiki page, it looks
> like a big deal.
Not really,
On Fri, 21 Apr 2023 03:58:11 -0500, Dale wrote:
> I did a emerge -ef nvidia-drivers and it still fails. I was hoping that
> would pick up the needed files. Guess not. I decided to do some more
> digging. I noticed that the same version is still in the tree. I
> copied the ebuild a while back
Le 20/04/23 à 17:41, Dr Rainer Woitok a tapoté :
> Netfab,
>
> On Tuesday, 2023-04-18 19:23:08 +0200, you wrote:
>
> > ...
> > Please post your emerge --info.
>
> $ emerge --info
I do not see anything particular in your emerge --info.
What is your eselect version ?
> $ eselect --version
You ca
On Thu, Apr 20, 2023 at 05:36:23PM -0500, Dale wrote:
> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
> No such file or directory
This sounds like you copied the ebuild to your local overlay but not
the files/ dir which includes the patch. So
Dale,
On Thursday, 2023-04-20 17:36:23 -0500, you wrote:
> ...
> * Package: x11-drivers/nvidia-drivers-470.182.03:0/470
> * Repository: mine
Maybe I'm missing something, but as of today "x11-drivers/nvidia-dri-
vers" version 470.182.03 is still in the normal Gentoo tree. So why use
your
On Fri, 21 Apr 2023 at 11:55, Dale wrote:
> Did something change with overlays? In the past, I copied the ebuild
> over to local overlay and ran the ebuild command for the manifest. It
> downloaded everything that was needed. Now, it seems it doesn't. They
> add a step? I miss a step that sli
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 10:58, Dale wrote:
>> I put my local ebuilds in /usr/local/portage. Obviously emerge sees it
>> since it was trying to use it. I don't understand why it doesn't work
>> tho. I looked at the ebuild in the tree and my overlay, they look the
>> same, in
On Fri, 21 Apr 2023 at 10:58, Dale wrote:
> I put my local ebuilds in /usr/local/portage. Obviously emerge sees it
> since it was trying to use it. I don't understand why it doesn't work
> tho. I looked at the ebuild in the tree and my overlay, they look the
> same, including the patches from d
Frank Steinmetzger wrote:
> Am Thu, Apr 20, 2023 at 08:33:22PM -0500 schrieb Dale:
>
>> I cleared the tmp files to give it a fresh start. It still failed. The
>> directory and files it complains about being missing, they are. I went
>> to the ebuild to see what patches are supposed to be install
Am Thu, Apr 20, 2023 at 08:33:22PM -0500 schrieb Dale:
> I cleared the tmp files to give it a fresh start. It still failed. The
> directory and files it complains about being missing, they are. I went
> to the ebuild to see what patches are supposed to be installed. This is
> the part of the e
Hello Michael. Long time no read. ;-)
> I think the best way to support that in a package is to declare which
> ruby versions are supported with USE_RUBY and ruby-ng.eclass.
I tried what you suggested. However, inheriting from ruby-ng.eclass
introduces an odd problem: For some reason unknown to m
26 matches
Mail list logo
