Re: [gentoo-user] Difference between --update and --emptytree?
On Sun, Mar 31, 2013 at 8:09 AM, Walter Dnes waltd...@waltdnes.org wrote: What do you mean by sane depclean? Are there any problems with --depclean that I am not aware of? emerge -p --depclean generates dire warnings. I keep a previous version of the kernel (gentoo-sources) as a fallback, and --depclean wants to remove that, which I want to keep. Quoted below is a solution that was posted to this list a few years ago, I use it for exactly that situation: to prevent kernels from ever getting depcleaned. On Thu, Jun 11, 2009 at 11:45 AM, Mike Kazantsev mk.frag...@gmail.com wrote: So, my question: Is there a way to tell depclean to never remove *any* version of gentoo-sources? That's where portage-2.2 sets find another use. Just add following set to /usr/share/portage/config/sets.conf: [kernels] class = portage.sets.dbapi.OwnerSet world-candidate = False files = /usr/src And append @kernels line to /var/lib/portage/world_sets Now any installed (even with -1) kernel should be safe from ravenous depclean. Hope that helps!
Re: [gentoo-user] Difference between --update and --emptytree?
Am 31.03.2013 05:12, schrieb Walter Dnes: On Sat, Mar 30, 2013 at 10:04:24PM -0400, Mike Gilbert wrote On Sat, Mar 30, 2013 at 9:49 PM, Walter Dnes waltd...@waltdnes.org wrote: Did an update today. After the update, I checked again... [d531][waltdnes][~] emerge -pv --update --changed-use world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB Good... nothing to add... I think. But replace --update with --emptytree, and a whole bunch of new and updated stuff shows up. Is there a logical explanation? Should I emerge world? Or just the new and updated stuff (with the -1 flag)? Here are listings of the new and updated stuff... The extra stuff is probably build-time deps, which do not get updated by default. Try this: emerge -pv --update --changed-use --with-bdeps=y world I see nothing at all to be emerged... [d531][waltdnes][~] emerge -pv --update --changed-use --with-bdeps=y world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB You can also try adding --deep to your emerge options. Or double check with eix -u -c I've written an autodepclean script that I run to guide me through cleaning up orphaned dependancies. Think of it as a sane depclean. After each use, I run revdep-rebuild to ensure that nothing is broken. Could this be at the root of my situation? What do you mean by sane depclean? Are there any problems with --depclean that I am not aware of?
Re: [gentoo-user] Difference between --update and --emptytree?
On Sun, Mar 31, 2013 at 01:56:25PM +0200, Michael Hampicke wrote You can also try adding --deep to your emerge options. That seems to be it... emerge -pv --update --changed-use --deep --with-bdeps=y world produces a list of packages. The list ends with... Total: 52 packages (29 upgrades, 23 new), Size of downloads: 6,521 kB Conflict: 1 block The 29 upgrades and 23 new seem to exactly match what I had from the new and upgrade portions of emerge world. Thanks for your help. What do you mean by sane depclean? Are there any problems with --depclean that I am not aware of? emerge -p --depclean generates dire warnings. I keep a previous version of the kernel (gentoo-sources) as a fallback, and --depclean wants to remove that, which I want to keep. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
Re: [gentoo-user] Difference between --update and --emptytree?
On Sunday 31 March 2013 14:09:56 Walter Dnes wrote: I keep a previous version of the kernel (gentoo-sources) as a fallback, and --depclean wants to remove that, which I want to keep. if you let it unmerge the old kernel it will only remove the sources. Everything that's generated by building the kernel will be left alone. Would that suit you? It's what I do here, anyway: -- Peter
Re: [gentoo-user] Difference between --update and --emptytree?
On Sun, 31 Mar 2013 09:09:56 -0400, Walter Dnes wrote: emerge -p --depclean generates dire warnings. I wouldn't call this dire * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace atom`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. There used to be big scary warnings in the past, but that was years ago and depclean seems very reliable now. I'd certainly trust a feature maintained by the portage devs more than a home-brewed script -- Neil Bothwick There's a fine line between fishing and standing on the shore looking like an idiot. signature.asc Description: PGP signature
Re: [gentoo-user] Difference between --update and --emptytree?
On Sat, Mar 30, 2013 at 9:49 PM, Walter Dnes waltd...@waltdnes.org wrote: Did an update today. After the update, I checked again... [d531][waltdnes][~] emerge -pv --update --changed-use world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB Good... nothing to add... I think. But replace --update with --emptytree, and a whole bunch of new and updated stuff shows up. Is there a logical explanation? Should I emerge world? Or just the new and updated stuff (with the -1 flag)? Here are listings of the new and updated stuff... The extra stuff is probably build-time deps, which do not get updated by default. Try this: emerge -pv --update --changed-use --with-bdeps=y world
Re: [gentoo-user] Difference between --update and --emptytree?
On Sat, Mar 30, 2013 at 10:04:24PM -0400, Mike Gilbert wrote On Sat, Mar 30, 2013 at 9:49 PM, Walter Dnes waltd...@waltdnes.org wrote: Did an update today. After the update, I checked again... [d531][waltdnes][~] emerge -pv --update --changed-use world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB Good... nothing to add... I think. But replace --update with --emptytree, and a whole bunch of new and updated stuff shows up. Is there a logical explanation? Should I emerge world? Or just the new and updated stuff (with the -1 flag)? Here are listings of the new and updated stuff... The extra stuff is probably build-time deps, which do not get updated by default. Try this: emerge -pv --update --changed-use --with-bdeps=y world I see nothing at all to be emerged... [d531][waltdnes][~] emerge -pv --update --changed-use --with-bdeps=y world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB I've written an autodepclean script that I run to guide me through cleaning up orphaned dependancies. Think of it as a sane depclean. After each use, I run revdep-rebuild to ensure that nothing is broken. Could this be at the root of my situation? -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
