?

Log in

No account? Create an account
 
 
22 December 2006 @ 12:44 am
Christmas for childish developers  

Although you've not behaved very good, Santa Claus has a present for you: the entire GNOME 2.16.2 desktop in experimental. All core applications are here, only some bindings are still missing. Which means it's time for the most courageous to test it.

With the experimental APT source configured, it should be a matter of apt-get install -t experimental gnome-desktop-environment.

Be warned, it's still rough around the edges:

  • GTK+ makes liferea crash repeatedly;
  • there are a few glitches in the file chooser;
  • there is only one working icon theme (the default one);
  • evince seems to crash on some files;
  • the keyboard switching stuff doesn't work at all.
But there are also many pleasant speed and UI improvements in most modules.

Unfortunately for many, it is currently only available on amd64. Now, if a group of reindeers could rebuild it on i386, the children would be much happier. Otherwise, I will take some time to rebuild them in an i386 chroot in a few days.

 
 
 
simbab on December 22nd, 2006 12:18 am (UTC)
I would be glad to do this...I have both i386 and amd64 machines. Can you point me to some documentation on how to rebuild a package (gnome-desktop-environment) and it's dependencies? Thanks.
simbab on December 22nd, 2006 06:37 pm (UTC)
Ech...they won't install on amd64 (missing deps) and I found debian-builder, which has a debian-builder-recursive script that looks like it should fit the bill, but it just seems to recurse endlessly over the same dependencies. This is with both all of experimental and just gnome-desktop-environment pinned above unstable in /etc/apt/preferences in my sid chroot.
np237np237 on December 22nd, 2006 08:18 pm (UTC)
Which deps are missing? Maybe you just have to wait for the next mirror pulse.
simbab on December 22nd, 2006 08:24 pm (UTC)
With all of experimental pinned in a fresh sid chroot:


root@conroe:/etc/apt# apt-get install gnome-desktop-environment
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
gnome-desktop-environment: Depends: gnome-core (= 1:2.16.2) but it is not going to be installed
Depends: evince (>= 0.6.1) but it is not going to be installed
Depends: gnome-media (>= 2.16.1) but it is not going to be installed
Depends: sound-juicer (>= 2.16.2) but it is not going to be installed
Depends: fast-user-switch-applet (>= 2.16.0) but it is not going to be installed
E: Broken packages
(Anonymous) on December 23rd, 2006 03:38 am (UTC)
I tracked those and it looks like the culprit is libgnome-media0
simbab on December 23rd, 2006 03:43 am (UTC)
Yes...I found the same thing myself.
np237np237 on December 23rd, 2006 06:32 pm (UTC)
Ick... I thought I had rebuilt it. I'll upload it after Xmas then.
(Anonymous) on December 22nd, 2006 07:42 am (UTC)
status page
So is the status page (http://www.0d.be/debian/debian-gnome-2.16-status.html) not up-to-date then?
np237np237 on December 22nd, 2006 08:20 pm (UTC)
Re: status page
It is not, because madison is broken on merkel, and the admins seem to be too busy forbidding the arm uploads to fix it.
(Anonymous) on December 23rd, 2006 07:06 pm (UTC)
uninstallable
... at least not without removing several software I'd like to keep.
The problem is with libwmf
(Anonymous) on December 23rd, 2006 07:11 pm (UTC)
Re: uninstallable
args. no idea how i triggered the submit button.

aptitude -t experimental install libgtk2.0-0
[...]
The following packages are BROKEN:
beagle gimp graphicsmagick gtk2-engines-geramik gtk2-engines-pixbuf
gtk2-engines-thingeramik krita libgraphicsmagick1 libgtk2.0-0 libwmf-bin
libwv-1.2-3
[...]

I'd like to be able to keep gimp, beagle, inkscape, koffice and graphicsmagic.

They all depend one way or another on libwmf (e.g. via libwv), but the new gtk conflicts libwmf0.2-7 (<= 0.2.8.4-2) and thats the only version available.
(Anonymous) on January 19th, 2007 11:34 pm (UTC)
What are the sources?
What are the exact sources to add to my source list? Should I write "experimental" instead of "etch/testing/unstable"?
np237np237 on January 19th, 2007 11:44 pm (UTC)
Re: What are the sources?
Just copy the line containing "unstable" and in the new line, replace unstable by experimental.
(Anonymous) on February 1st, 2007 04:31 pm (UTC)
I did it
Just finished the install using aptitude. Took a little extra time to resolve the dependencies, but no errors during installation. Will now reboot, and if anything is obviously broken I will report.

rickh
(Anonymous) on February 1st, 2007 05:21 pm (UTC)
Re: I did it
For the record, no obvious problems.
(Anonymous) on February 11th, 2007 02:33 am (UTC)
Re: I did it
gedit no longer works

rickh
np237np237 on February 11th, 2007 11:33 pm (UTC)
Re: I did it
I think this should be fixed by the latest upload (missing dependency).
(Anonymous) on February 22nd, 2007 05:50 pm (UTC)
Re: I did it ... by rickh
Hope it's OK to post this here. I didn't see an Email option. Gedit still doesn't work on my system. As soon as I click on the icon or attempt to open a file in Nautilus, BugBuddy immediately comes up.

Looking at his Detail window shows this: (The "upright ellipsis" about line 19 represents 80+ lines identical to those above and below it. Lines like this, (---), said, "No symbol table info available.")

Memory status: size: 127328256 vsize: 127328256 resident: 20127744 share: 11411456 rss: 20127744 rss_rlim: -1
CPU usage: start_time: 1172164450 rtime: 29 utime: 25 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gedit'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47632197383136 (LWP 4059)]
(no debugging symbols found)
.
.
.
(no debugging symbols found)
0x00002b5236957fd5 in waitpid () from /lib/libpthread.so.0
#0 0x00002b5236957fd5 in waitpid () from /lib/libpthread.so.0
#1 0x00002b5236beb600 in ?? () from /usr/lib/libgnomeui-2.so.0
#2
#3 0x0000000000450cdd in ?? ()
#4 0x00002b523850dcef in g_type_class_ref ()
from /usr/lib/libgobject-2.0.so.0
#5 0x00002b52384f4951 in g_object_new_valist ()
from /usr/lib/libgobject-2.0.so.0
#6 0x00002b52384f4d51 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#7 0x00000000004508ab in gedit_python_module_new ()
#8 0x0000000000433aec in ?? ()
#9 0x0000000000433d15 in gedit_plugins_engine_update_plugins_ui ()
#10 0x000000000044b890 in ?? ()
#11 0x00002b523850e8f0 in g_type_create_instance ()
from /usr/lib/libgobject-2.0.so.0
#12 0x00002b52384f5c8d in ?? () from /usr/lib/libgobject-2.0.so.0
#13 0x00002b52384f40ef in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#14 0x00002b52384f4b1c in g_object_new_valist ()
from /usr/lib/libgobject-2.0.so.0
#15 0x00002b52384f4d51 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#16 0x0000000000426301 in ?? ()
#17 0x000000000042647d in gedit_app_create_window ()
#18 0x0000000000425215 in main ()

Thread 1 (Thread 47632197383136 (LWP 4059)):
#0 0x00002b5236957fd5 in waitpid () from /lib/libpthread.so.0
(---)
#1 0x00002b5236beb600 in ?? () from /usr/lib/libgnomeui-2.so.0
(---)
#2
(---)
#3 0x0000000000450cdd in ?? ()
(---)
#4 0x00002b523850dcef in g_type_class_ref ()
from /usr/lib/libgobject-2.0.so.0
(---)
#5 0x00002b52384f4951 in g_object_new_valist ()
from /usr/lib/libgobject-2.0.so.0
(---)
#6 0x00002b52384f4d51 in g_object_new () from /usr/lib/libgobject-2.0.so.0
(---)
#7 0x00000000004508ab in gedit_python_module_new ()
(---)
#8 0x0000000000433aec in ?? ()
(---)
#9 0x0000000000433d15 in gedit_plugins_engine_update_plugins_ui ()
(---)
#10 0x000000000044b890 in ?? ()
(---)
#11 0x00002b523850e8f0 in g_type_create_instance ()
from /usr/lib/libgobject-2.0.so.0
(---)
#12 0x00002b52384f5c8d in ?? () from /usr/lib/libgobject-2.0.so.0
(---)
#13 0x00002b52384f40ef in g_object_newv () from /usr/lib/libgobject-2.0.so.0
(---)
#14 0x00002b52384f4b1c in g_object_new_valist ()
from /usr/lib/libgobject-2.0.so.0
(---)
#15 0x00002b52384f4d51 in g_object_new () from /usr/lib/libgobject-2.0.so.0
(---)
#16 0x0000000000426301 in ?? ()
(---)
#17 0x000000000042647d in gedit_app_create_window ()
(---)
#18 0x0000000000425215 in main ()
(---)
#0 0x00002b5236957fd5 in waitpid () from /lib/libpthread.so.0
The program is running. Quit anyway (and detach it)? (y or n)

Running from the Terminal only displays the message "** (bug-buddy:5222): WARNING **: Couldn't load icon for Open Folder"

I have not summoned up the courage to try upgrading libc6 from Experimental

Apart from that, I have a few intermittent application crashes etc., but nothing that really concerns me.
np237np237 on February 23rd, 2007 07:27 am (UTC)
Re: I did it ... by rickh
Please, this isn't a place to report bugs.

See http://www.debian.org/Bugs/Reporting
(Anonymous) on May 18th, 2007 09:20 pm (UTC)
Re: I did it ... by rickh
Hey there, just ran across this after updating debian sid. On May 18th I decided, oh well, lets select "Mark all Upgrades" in Synaptic....so I knew something was going to break....so far to my knowledge nothing that bad. I'm a KDE user and I was unable to log into KDE without it crashing and bouncing me back out to the login splash screen....so I reinstalled my NVIDIA driver and all was well....however I did notice that when I selected "Mark all Upgrades" it did actually remove gnome, and I use gnome from time to time and couldn't reinstall it due to the dependency issues you discussed above...before applying any new updates...I was curious...did you guys find out what the actual source of the problem was? ...and how it was fixed?

Thanks guys
np237np237 on May 18th, 2007 10:06 pm (UTC)
Re: I did it ... by rickh
Things get much easier when packages are in unstable. Almost all dependencies should be correct now, and the upgrade path is smooth.