[gentoo-user] Need ebuild no longer in Portage

[gentoo-user] Need ebuild no longer in Portage

[Grant]

The current version of nvidia-drivers I have installed is pretty old
but it's the last one I've found that will display the resolution of
my monitor correctly at 1366x768.  The later versions insist on
1280x768 I think.  I need to re-compile the nvidia module since I'm
upgrading the kernel, but how can I do that if there is no ebuild?  I
use 'eclean distfiles' regularly and apparently eclean will delete the
distfile of an installed program since the distfile for the version of
nvidia-drivers I have installed doesn't exist in
/usr/portage/distfiles.

I would at least try to get the right resolution working with the
latest nvidia-drivers but I don't think I'll be able to revert back to
the old version since 'emerge -K =nvidia-drivers-1.0.9639' doesn't
work.  I'm not sure why since I've always had FEATURES="buildpkg" set.
 Can I build a binary package now in case I need to revert?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Need ebuild no longer in Portage

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 917 bytes --]

Am Freitag, 4. Januar 2008 schrieb ext Grant:
> The current version of nvidia-drivers I have installed is pretty old
> but it's the last one I've found that will display the resolution of
> my monitor correctly at 1366x768.  The later versions insist on
> 1280x768 I think.  I need to re-compile the nvidia module since I'm
> upgrading the kernel, but how can I do that if there is no ebuild?

There is still the ebuild you have installed from 
in /var/db/pkg/<category>/<package>. You can copy it over to your local 
overlay and keep it there forever.

HTH...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Need ebuild no longer in Portage

[William Kenworthy]

Also, gentoo has an "attic" where all older ebuilds are archived.  You
can grab the ebuild and any related files and use your local overlay to
keep it around for as long as you need.

http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-drivers/

There are nvidia-drivers and a legacy branch for even older.  In
nvidia-drivers there is a link to view dead files (or attic) - prob same
everywhere.

BillK



On Fri, 2008-01-04 at 07:29 +0100, Dirk Heinrichs wrote:
> Am Freitag, 4. Januar 2008 schrieb ext Grant:
> > The current version of nvidia-drivers I have installed is pretty old
> > but it's the last one I've found that will display the resolution of
> > my monitor correctly at 1366x768.  The later versions insist on
> > 1280x768 I think.  I need to re-compile the nvidia module since I'm
> > upgrading the kernel, but how can I do that if there is no ebuild?
> 
> There is still the ebuild you have installed from 
> in /var/db/pkg/<category>/<package>. You can copy it over to your local 
> overlay and keep it there forever.
> 
> HTH...
> 
> 	Dirk
-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Need ebuild no longer in Portage

[Grant]

> Also, gentoo has an "attic" where all older ebuilds are archived.  You
> can grab the ebuild and any related files and use your local overlay to
> keep it around for as long as you need.
>
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-drivers/
>
> There are nvidia-drivers and a legacy branch for even older.  In
> nvidia-drivers there is a link to view dead files (or attic) - prob same
> everywhere.
>
> BillK

That works great but the emerge fails during installation:

>>> Install nvidia-drivers-1.0.9639 into
/var/tmp/portage/x11-drivers/nvidia-drivers-1.0.9639/image/ category
x11-drivers
 * Installing nvidia module
 *
 * ERROR: x11-drivers/nvidia-drivers-1.0.9639 failed.
 * Call stack:
 *                        ebuild.sh, line 1701:  Called dyn_install
 *                        ebuild.sh, line 1138:  Called qa_call 'src_install'
 *                        ebuild.sh, line   44:  Called src_install
 *   nvidia-drivers-1.0.9639.ebuild, line  231:  Called die
 * The specific snippet of code:
 *              [ -f "${FILESDIR}/nvidia" ] || die "nvidia missing in FILESDIR"
 *  The die message:
 *   nvidia missing in FILESDIR

Can anyone tell what happened?

- Grant


> > > The current version of nvidia-drivers I have installed is pretty old
> > > but it's the last one I've found that will display the resolution of
> > > my monitor correctly at 1366x768.  The later versions insist on
> > > 1280x768 I think.  I need to re-compile the nvidia module since I'm
> > > upgrading the kernel, but how can I do that if there is no ebuild?
> >
> > There is still the ebuild you have installed from
> > in /var/db/pkg/<category>/<package>. You can copy it over to your local
> > overlay and keep it there forever.
> >
> > HTH...
> >
> >       Dirk
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Need ebuild no longer in Portage

[Jesús Guerrero]

On Fri, 4 Jan 2008 07:58:52 -0800
Grant <emailgrant@gmail.com> wrote:

>  *   nvidia missing in FILESDIR
> 
> Can anyone tell what happened?
> 
You probably copied the ebuild, but not the contents of the files/
subdirectory. It probably needs some patch that lived there. So you
need to copy that directory along with its contents to the same place
you copied the old ebuild.

-- 
Jesús Guerrero <i92guboj@terra.es>
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Need ebuild no longer in Portage

[Grant]

> >  *   nvidia missing in FILESDIR
> >
> > Can anyone tell what happened?
> >
> You probably copied the ebuild, but not the contents of the files/
> subdirectory. It probably needs some patch that lived there. So you
> need to copy that directory along with its contents to the same place
> you copied the old ebuild.

That was it, thank you.

Does anyone know if there is a way to prevent eclean from removing a
distfile for an installed package.  Seems like that should be default
behavior.

- Grant

> Jesús Guerrero <i92guboj@terra.es>
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Need ebuild no longer in Portage

[Grant]

> > >  *   nvidia missing in FILESDIR
> > >
> > > Can anyone tell what happened?
> > >
> > You probably copied the ebuild, but not the contents of the files/
> > subdirectory. It probably needs some patch that lived there. So you
> > need to copy that directory along with its contents to the same place
> > you copied the old ebuild.
>
> That was it, thank you.

Actually, it compiles and installs when /usr/src/linux points to
2.6.20-hardened-r6 but fails to compile when it points to
linux-2.6.23-hardened-r4.  The error instructs me as follows:

ERROR: Kernel configuration is invalid.
include/linux/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.

Which I did with the same results.  Does anyone know how to fix this?

- Grant
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Need ebuild no longer in Portage

[Grant Edwards]

On 2008-01-04, Grant <emailgrant@gmail.com> wrote:
>> > >  *   nvidia missing in FILESDIR
>> > >
>> > > Can anyone tell what happened?
>> > >
>> > You probably copied the ebuild, but not the contents of the files/
>> > subdirectory. It probably needs some patch that lived there. So you
>> > need to copy that directory along with its contents to the same place
>> > you copied the old ebuild.
>>
>> That was it, thank you.
>
> Actually, it compiles and installs when /usr/src/linux points to
> 2.6.20-hardened-r6 but fails to compile when it points to
> linux-2.6.23-hardened-r4.  The error instructs me as follows:
>
> ERROR: Kernel configuration is invalid.
> include/linux/autoconf.h or include/config/auto.conf are missing.
> Run 'make oldconfig && make prepare' on kernel src to fix it.
>
> Which I did with the same results.  Does anyone know how to fix this?

ISTR that "make prepare" isn't sufficient.  You have to do a
"make".  IIRC, you can kill it once it starts compiling "real
code".

-- 
Grant Edwards                   grante             Yow! RELATIVES!!
                                  at               
                               visi.com            

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Need ebuild no longer in Portage

[Grant]

> >> > >  *   nvidia missing in FILESDIR
> >> > >
> >> > > Can anyone tell what happened?
> >> > >
> >> > You probably copied the ebuild, but not the contents of the files/
> >> > subdirectory. It probably needs some patch that lived there. So you
> >> > need to copy that directory along with its contents to the same place
> >> > you copied the old ebuild.
> >>
> >> That was it, thank you.
> >
> > Actually, it compiles and installs when /usr/src/linux points to
> > 2.6.20-hardened-r6 but fails to compile when it points to
> > linux-2.6.23-hardened-r4.  The error instructs me as follows:
> >
> > ERROR: Kernel configuration is invalid.
> > include/linux/autoconf.h or include/config/auto.conf are missing.
> > Run 'make oldconfig && make prepare' on kernel src to fix it.
> >
> > Which I did with the same results.  Does anyone know how to fix this?
>
> ISTR that "make prepare" isn't sufficient.  You have to do a
> "make".  IIRC, you can kill it once it starts compiling "real
> code".

I can't keep up with the acronyms but I did a full make and I still
get the same error.  Should I be booted into the same kernel that
/usr/src/linux points to when compiling nvidia-modules?

- Grant
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Need ebuild no longer in Portage

[Grant Edwards]

On 2008-01-04, Grant <emailgrant@gmail.com> wrote:

>> ISTR that "make prepare" isn't sufficient.  You have to do a
>> "make".  IIRC, you can kill it once it starts compiling "real
>> code".
>
> I can't keep up with the acronyms

I seem to recall. :)

> but I did a full make and I still get the same error.  Should
> I be booted into the same kernel that /usr/src/linux points to
> when compiling nvidia-modules?

I didn't think that was required, but that's probably how I've
always done it, so it's worth a shot.

-- 
Grant Edwards                   grante             Yow! An Italian is COMBING
                                  at               his hair in suburban DES
                               visi.com            MOINES!

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Need ebuild no longer in Portage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

Grant Edwards wrote:
> On 2008-01-04, Grant <emailgrant@gmail.com> wrote:
>
>   
>>> ISTR that "make prepare" isn't sufficient.  You have to do a
>>> "make".  IIRC, you can kill it once it starts compiling "real
>>> code".
>>>       
>> I can't keep up with the acronyms
>>     
>
> I seem to recall. :)
>
>   
>> but I did a full make and I still get the same error.  Should
>> I be booted into the same kernel that /usr/src/linux points to
>> when compiling nvidia-modules?
>>     
>
> I didn't think that was required, but that's probably how I've
> always done it, so it's worth a shot.
>
>   

I have tried it with it pointing to the wrong kernel, sometimes it
works, sometimes not.  Best to point it to the right one I guess.

Dale

:-)  :-)

[-- Attachment #2: Type: text/html, Size: 1400 bytes --]

Re: [gentoo-user] Re: Need ebuild no longer in Portage

[Grant]

> >> ISTR that "make prepare" isn't sufficient.  You have to do a
> >> "make".  IIRC, you can kill it once it starts compiling "real
> >> code".
> >
> > I can't keep up with the acronyms
>
> I seem to recall. :)
>
> > but I did a full make and I still get the same error.  Should
> > I be booted into the same kernel that /usr/src/linux points to
> > when compiling nvidia-modules?
>
> I didn't think that was required, but that's probably how I've
> always done it, so it's worth a shot.

Same result unfortunately.  Is it possible that this version of
nvidia-drivers isn't compatible with 2.6.23?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Need ebuild no longer in Portage

[Grant]

> >> ISTR that "make prepare" isn't sufficient.  You have to do a
> >> "make".  IIRC, you can kill it once it starts compiling "real
> >> code".
> >
> > I can't keep up with the acronyms
>
> I seem to recall. :)
>
> > but I did a full make and I still get the same error.  Should
> > I be booted into the same kernel that /usr/src/linux points to
> > when compiling nvidia-modules?
>
> I didn't think that was required, but that's probably how I've
> always done it, so it's worth a shot.

Strange though.  Here's the error:

include/linux/autoconf.h or include/config/auto.conf are missing.

but both of those files clearly exist.

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Need ebuild no longer in Portage

[Renat Golubchyk]

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

On Fri, 4 Jan 2008 11:01:44 -0800 Grant <emailgrant@gmail.com> wrote:
> Does anyone know if there is a way to prevent eclean from removing a
> distfile for an installed package.  Seems like that should be default
> behavior.

From the eclean manpage:

If you use the --destructive option, eclean will only protect files
corresponding to some currently installed package  (taking  their
exact version into account).



Cheers,
Renat

-- 
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
                                              (Einstein)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] Need ebuild no longer in Portage

[Alan McKinnon]

On Saturday 05 January 2008, Renat Golubchyk wrote:
> On Fri, 4 Jan 2008 11:01:44 -0800 Grant <emailgrant@gmail.com> wrote:
> > Does anyone know if there is a way to prevent eclean from removing
> > a distfile for an installed package.  Seems like that should be
> > default behavior.
>
> From the eclean manpage:
>
> If you use the --destructive option, eclean will only protect files
> corresponding to some currently installed package  (taking  their
> exact version into account).

He'd be better off using /etc/eclean/packages.exclude, described in the 
EXCLSUION FILES section of man eclean.

eclean's default behaviour is to retain distfiles for installed packages 
*that are in the portage tree*. The file Grant wants to protect is not 
in the portage tree anymore



-- 
Alan McKinnon
alan dot mckinnon at gmail dot com
-- 
gentoo-user@gentoo.org mailing list