Am 14.04.2013 20:56, schrieb Steven Chamberlain: > On 14/04/13 11:03, Christian PERRIER wrote: >> As a consequence, having the desktop-gnome task broken on kFreeBSD >> because of the dependency on n-m-gnome can be considered as non >> release critical... > > Just for the record, I'm not happy about this. > > Why could this not have been fixed in any case, it was obviously a > mistake/oversight, creates a regression for kfreebsd-*, and I provided a > patch which is trivial. This patch doesn't help. The Depends was added in the first place to ensure network-manager is on CD1. Demoting that to Recommends is pointless, since we already have a Recommends in gnome-core. > How are users expected to be test GNOME anyway on kfreebsd if they're > prevented from installing it since the rc1 installer. As a 'new' arch, > people typically don't have installed systems to use as a basis to try > things. I don't want to comment on whether we actually have any GNOME users on kbsd. That said, you can of course always use a minimal installation and install GNOME later on. That should make it easy enough to test GNOME on kfreebsd. > Are kfreebsd-*'s GNOME CD-1 etc. going to be able to build if > task-gnome-desktop is uninstallable? Is there any point building them? One possible solution is to make the task- package arch:any, but IIRC that was an option joeyh didn't like. The other option to make sure NM is on CD1 IIRC was to do that via debian-cd. > Furthermore what about tech-ctte decision #688772 that squeeze->wheezy > upgrades (on GNU/Linux) should not pick up network-manager as a > dependency? Is that would what happen if they have task-gnome-desktop > installed and it Depends now on network-manager-gnome? task-gnome-desktop is not a real package on squeeze, so no, the new dependency in task-gnome-desktop does not pull NM on squeeze to wheezy upgrades. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature