[gentoo-dev] Re: Blockers and package moves

2011-01-16 Thread Ryan Hill
On Sun, 16 Jan 2011 13:49:38 + Ciaran McCreesh wrote: > People seem to have started using blockers with package moves recently. > For example, if cat/a is being moved to cat/b, people have started > putting !cat/a as a dependency in cat/b. This is bad, for two reasons. It's bad for a couple

[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2011-01-16 23h59 UTC

2011-01-16 Thread Robin H. Johnson
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2011-01-16 23h59 UTC. Removals: xfce-extra/thunar-media-tags-plugin 2011-01-11 10:13:43 ssuominen xfce-extra/thunar-vcs-plugin2011-01-11 10:13:44 ssuominen xfce-extra/x

[gentoo-dev] genkernel 3.4.11 released

2011-01-16 Thread Sebastian Pipping
Hello! I have just released genkernel 3.4.11 to the testing tree. >From a high level point of view this release brings: - Slightly faster startup - Updated versions of busybox, LVM, e2fsprogs/blkid - A few new features, e.g. GnuPG support - A bunch of bug fixes (see below) Below you can find de

Re: [gentoo-dev] Blockers and package moves

2011-01-16 Thread Ciaran McCreesh
On Sun, 16 Jan 2011 16:05:22 +0100 "Paweł Hajdan, Jr." wrote: > On 1/16/11 2:49 PM, Ciaran McCreesh wrote: > > Second, when performing updates, Paludis also rewrites dependencies > > of installed packages to use the names. > > This seems to imply that portage behaves differently. Should we update

Re: [gentoo-dev] Blockers and package moves

2011-01-16 Thread Paweł Hajdan, Jr.
On 1/16/11 2:49 PM, Ciaran McCreesh wrote: > Second, when performing updates, Paludis also rewrites dependencies of > installed packages to use the names. This seems to imply that portage behaves differently. Should we update PMS when we determine what's the correct behavior? signature.asc Desc

[gentoo-dev] Blockers and package moves

2011-01-16 Thread Ciaran McCreesh
People seem to have started using blockers with package moves recently. For example, if cat/a is being moved to cat/b, people have started putting !cat/a as a dependency in cat/b. This is bad, for two reasons. First, you shouldn't have to do that. If package moves aren't working, we've got bigger