From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Nvidia-driver installation problems...
Date: Fri, 10 Apr 2020 12:48:17 +0100 [thread overview]
Message-ID: <20200410124817.7fdb39aa@digimed.co.uk> (raw)
In-Reply-To: <20200410102146.2htdcbu4ypif3o35@solfire>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On Fri, 10 Apr 2020 12:21:46 +0200, tuxic@posteo.de wrote:
> On 04/10 11:11, Neil Bothwick wrote:
> > On Fri, 10 Apr 2020 11:40:59 +0200, tuxic@posteo.de wrote:
> >
> > > > package.provided requires a specific version, try
> > > >
> > > > x11-drivers/nvidia-drivers-340.108
> > > >
> > > > If you want to stop portage trying to replace this with a later
> > > > version, add ">x11-drivers/nvidia-drivers-340.108", note > not
> > > > >=, to package.mask.
> > >
> > > /etc/portage/profile/package.provided is still being ignored.
> > >
> > > Current content:
> > > >x11-drivers/nvidia-drivers-340.108
> > >
> > > Emerge starts to install the newest driver available.
> >
> > Because package.provided still doesn't contain a single version.
> > Remove the >.
>
> That leads to another problem:
> It will not detect newer version comping into portage...
> I need to include any single version available.
> That's kinda painful...
That's the burden you take on by managing the package yourself. You have
to watch for new versions yourself.
--
Neil Bothwick
All generalizations are false.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-10 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 9:25 [gentoo-user] Nvidia-driver installation problems tuxic
2020-04-10 9:29 ` Neil Bothwick
2020-04-10 9:40 ` tuxic
2020-04-10 10:11 ` Neil Bothwick
2020-04-10 10:21 ` tuxic
2020-04-10 11:48 ` Neil Bothwick [this message]
2020-04-10 12:23 ` tuxic
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=20200410124817.7fdb39aa@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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