Re: Bug#704748: Not a practical issue (could even be considered a feature...:-))
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. 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. 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? 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? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/516afbf4.5030...@pyro.eu.org
Re: Gnome installability vs. GNU/kFreeBSD
On 09/04/13 19:15, Didier 'OdyX' Raboud wrote: > I just did (in kvm/qemu) and the result isn't great (for Gnome): Thank you very much for testing. > - gdm3 … doesn't finish loading. It fullscreen-says "Oops, an error occured". Confirmed: gdm3 shows the 'fail whale' modal dialog; at least the clock and power-off button are visible, but it is not possible to click them. > - lightdm + "Gnome": same. > - lightdm + "Gnome classic": same. Not really the same situation as gdm3, but the same uninformative 'fail whale' modal dialog is shown. But in fact, behind it is a seemingly functional window manager and panel with menus... I was able to manually start those things, by using 'xinit', from which I could launch the basic GNOME apps (terminal, calculator, file manager, settings page, telepathy) as I've just explained here (with screenshot) : https://wiki.debian.org/Debian_GNU/kFreeBSD_Desktop#Wheezy_GNOME Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/516b2a9f.2050...@pyro.eu.org
Re: Gnome installability vs. GNU/kFreeBSD
On 09/04/13 19:15, Didier 'OdyX' Raboud wrote: > - gdm3 … doesn't finish loading. It fullscreen-says "Oops, an error occured". > - lightdm + "Gnome": same. > - lightdm + "Gnome classic": same. Found a workaround for this :) But it is strange... 1. Start the system without gdm3 (e.g. update-rc.d gdm3 remove) 2. Log into ttyv1, run "while sleep 1 ; do pkill pulse ; done" 3. Log into ttyv2, run `/etc/init.d/gdm3 start` And all is fine! gdm3 greeter is working, logs into a working session (fallback mode because acceleration is not available). I noticed during testiong that `pstree $(which gnome-session)` showed a single pulseaudio child process; for some reason it may hang (AFAIK I have no working sound devices, if that makes any difference) and after some timeout either gdm3 or gnome-session would otherwise show the 'fail whale' modal dialog. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/516b3ac3.9020...@pyro.eu.org
Re: Bug#704748: Not a practical issue (could even be considered a feature...:-))
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? signature.asc Description: OpenPGP digital signature
Re: Bug#704748: Not a practical issue (could even be considered a feature...:-))
Quoting Steven Chamberlain (ste...@pyro.eu.org): > 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. I'm sorry for this but, given the feedback received by Cyril's mail to -bsd, -boot, that seemed to be the simplest option. I was balanced about working in tasksel to upload with the simple "move to Recommends" fix but a brief discussion on IRC discouraged me. The fix is simple, yesbut the work in tasksel's git to create a wheezy branch starting from 3.14+nmu1, adding the fix to it and upload was something not trivial andat the same time I got an RC bug in one of my packages, one I consider much more important than Gnome in kFreeBSD. So, my priority changed. I think that nobody is prevented to fix the issue but I would ask fixing it *and* dealing with things in tasksel's git, not just with an NMU. Things are probably trivial for someone very comfortable with git. I am not...not enough at least. And, well, doesn't this issue really fit the definition of "important"? signature.asc Description: Digital signature
