View previous topic :: View next topic |
Author |
Message |
revoohc Tux's lil' helper
Joined: 12 Oct 2002 Posts: 128
|
Posted: Wed Apr 02, 2003 8:08 pm Post subject: how to "lock" a package? |
|
|
I need some help with emerge. I have updated my nvidia kernel module and nvidia glx to the newest version that was released a day or two ago (I used a temp ~x86 to get the build). Now when I do an emerge -up world to see what is ready to be upgraded on my emerge wants to upgrade. Since I am not normally running the testing/unstable with the ~x86 flag, it is wanting to downgrade my nvidia stuff.
How can I get emerge to "lock" my nivida packages when I to the upgrade?
Thanks,
Chris |
|
Back to top |
|
|
AlterEgo Veteran
Joined: 25 Apr 2002 Posts: 1619
|
Posted: Wed Apr 02, 2003 8:24 pm Post subject: |
|
|
as root, find /var/cache/edb/world,
and add the version-number after the nvidia-kernel and -glx entries.
example:
media-video/nvidia-glx-1.0.4349
This will block any upgrades, and I think also downgrades. |
|
Back to top |
|
|
revoohc Tux's lil' helper
Joined: 12 Oct 2002 Posts: 128
|
Posted: Wed Apr 02, 2003 8:38 pm Post subject: |
|
|
This did not work. I went as far as to remove both nvidia lines from the world file and even did an emerge sync just to make sure everything is up to date. However after all this and verifying that the nvidia packages are not in the world file, emerge -up world still wants to downgrade the packages!
Please help as this does not make any since from what I understand of the emerge system. I thought if the package is not in the world file, then emerge would not mess with it unless you specifically told it to.
Thanks,
Chris |
|
Back to top |
|
|
shadow303 Tux's lil' helper
Joined: 19 Apr 2002 Posts: 101
|
Posted: Wed Apr 02, 2003 10:05 pm Post subject: |
|
|
Something is fishy with the version pinning. I have my nvidia-glx and nvidia-kernel pinned in the world file, but it wants to downgrade them anyway. I have this happening on two machines. On the one machine, it calls the kernel downgrade an upgrade. If I use the --upgradeonly option, it avoids the downgrade, but I shouldn't need to use upgradeonly. I have also noticed that if I try using the upgradeonly and deep options, emerge chokes:
Quote: |
root@epsilon /home/gabe # emerge -puD --upgradeonly world
These are the packages that I would merge, in order:
Calculating world dependencies \
!!! all ebuilds that could satisfy "~media-video/nvidia-kernel-1.0.4191" have been masked.
!!! (dependency required by "media-video/nvidia-glx-1.0.4191-r1" [ebuild])
!!! Problem with ebuild app-office/koffice-1.2.1-r1
!!! Possibly a DEPEND/*DEPEND problem.
!!! Depgraph creation failed.
|
I saw there was a bug report filed about some people having problems with pinning things, but it appears to have been ignored. |
|
Back to top |
|
|
floam Veteran
Joined: 27 Oct 2002 Posts: 1067 Location: Vancouver, WA USA
|
Posted: Wed Apr 02, 2003 11:48 pm Post subject: |
|
|
uh, its not that complicated, just inject the old versions. do emerge inject /path/to/old/nvidia-kernel.ebuild and the same for glx |
|
Back to top |
|
|
shadow303 Tux's lil' helper
Joined: 19 Apr 2002 Posts: 101
|
Posted: Thu Apr 03, 2003 2:35 pm Post subject: |
|
|
Yeah, that would probably get around the problem, but it is a cludge. Clearly there is something that needs addressed with portage. It would be better to get it fixed than to bandaid around it. |
|
Back to top |
|
|
rtn Guru
Joined: 15 Nov 2002 Posts: 427
|
Posted: Thu Apr 03, 2003 3:58 pm Post subject: |
|
|
This is what I use to keep postgres from being updated:
Code: | $ grep postgres /var/cache/edb/world
=dev-db/postgresql-7.2.3-r1
|
It sure works for me.
--rtn |
|
Back to top |
|
|
shadow303 Tux's lil' helper
Joined: 19 Apr 2002 Posts: 101
|
Posted: Fri Apr 04, 2003 1:42 am Post subject: |
|
|
Unfortunately, it doesn't work for me. I wonder what the problem is. |
|
Back to top |
|
|
|