On Mon, Oct 15, 2012 at 10:04 AM, Thiago Bellini Ribeiro <hackedbell...@gmail.com> wrote: > On Sun, Oct 14, 2012 at 3:23 PM, Jasper St. Pierre > <jstpie...@mecheye.net> wrote: >> Note that with Debian/Ubuntu, there's an issue with multiarch >> conflicting with 64-bit systems. jhbuild assumes that /usr/lib64/ >> exists on all systems with "x86_64" in the uname, but that's untrue >> for Debian systems. >> >> Put "use_lib64 = False" in your .jhbuildrc as a workaround for this. > > Did it! Thanks for the hint! > > I'm just having one issue now: http://hastebin.com/feyamejeqo > I'm using the last available jhbuild from git.
Tried to do a simple debug..The problem seems to be here: http://hastebin.com/luqijuboto.py (line 188 to 208 on systeminstall.py) I put a print before the "if len(pk_package_ids) == 0" for pk_package_ids and pkconfig_ids This is what they printed: pk_package_ids = set([]) # empty set pkconfig_ids = [u'soundtouch-1.4', u'python', u'wavpack', u'xcb-aux', u'vpx', u'icu-i18n', u'flac', u'libv4l2', u'taglib', u'libnl-3.0', u'libpulse', u'speex', u'oauth', u'pycairo', u'libexif', u'sndfile', u'libxslt', u'libproxy-1.0', u'libgphoto2', u'icon-naming-utils', u'libcanberra-gtk', u'poppler-glib', u'bluez', u'json', u'liboil-0.3'] I don't know what the WhatProvides do but at the end, none of those pkconfig_ids wasn't added to pk_package_ids. And doing a 'apt-cache search' I can see that most of those packages exists on archive. > >> >> On Sun, Oct 14, 2012 at 2:20 PM, Thiago Bellini Ribeiro >> <hackedbell...@gmail.com> wrote: >>> On Sun, Oct 14, 2012 at 2:49 PM, Giovanni Campagna >>> <scampa.giova...@gmail.com> wrote: >>>> 2012/10/14 Thiago Bellini Ribeiro <hackedbell...@gmail.com>: >>>>> On Sun, Oct 14, 2012 at 1:26 PM, Giovanni Campagna >>>>> <scampa.giova...@gmail.com> wrote: >>>>>> 2012/10/9 Thiago Bellini Ribeiro <hackedbell...@gmail.com>: >>>>>>> On Sat, Oct 6, 2012 at 11:59 AM, Giovanni Campagna >>>>>>> <scampa.giova...@gmail.com> wrote: >>>>>>>> Ok after digging a bit, the problem is that .acknowledged is only set >>>>>>>> for notifications that are in the queue, but >>>>>>>> (notificationDaemon.js:564) resident notifications are not queued if >>>>>>>> the originating app is currently focused. A good fix, for which you >>>>>>>> can prepare a patch if you want, is to mark those notifications as >>>>>>>> immediately acknowledged, since that's the point. >>>>>>>> All other cases, including resident notifications for background apps >>>>>>>> (such as rhythmbox changing song), should be already covered. >>>>>>> >>>>>>> I would like to create a patch for this. Actually, I would love to >>>>>>> start contributing code to gnome, but I'm having a hard time with >>>>>>> jhbuild. >>>>>>> >>>>>>> I'm on Debian Testing and trying to run "jhbuild build gnome-shell" >>>>>>> always ends in a lot of dependency problems, since packages there tend >>>>>>> to be older than needed to build (specially on freeze). Even at the >>>>>>> beginning of 3.6's development, I never got gnome-shell to build. >>>>>>> >>>>>>> What should I do? I mean, what can I do to setup a working environment >>>>>>> for coding/testing/etc gnome's apps that works on Debian? >>>>>> >>>>>> If you're using the official modulesets, jhbuild sysdeps should >>>>>> install the necessary system packages (that are supposedly good enough >>>>>> on all modern distros), while everything else is built from scratch. >>>>>> Nothing should fail anymore for 3.6, although for core development you >>>>>> may want to switch to 3.8. Try jhbuild build --ignore-suggests >>>>>> gnome-shell, to skip anything you don't need. >>>>>> We don't have (yet) a SDK or anything like that for building >>>>>> applications, and in any case I don't think it would be inclusive >>>>>> enough for shell hacking. >>>>> >>>>> Great! Will try that! >>>>> >>>>> Just a little doubt: Taking a look at [1], it's not very clear that >>>>> those packages will be installed at my system or just for jhbuild (at >>>>> /opt/gnome). >>>>> I imagine that it's not going to install anything in my system, >>>>> possibly breaking other packages..am I right? >>>> >>>> jhbuild sysdeps will fetch system dependencies from the normal >>>> distribution channels (i.e. apt-get under debian), so the installation >>>> will be in /usr and you will be asked for root's password. For some >>>> system dependencies, if not found in the repositories it will download >>>> and build an upstream tarball (in which case the resulting binaries >>>> will be in /opt/gnome ) >>> >>> Great! :) >>> >>> Thanks for the hints and everything. >>> Hope I can provide a patch for the issue soon! >>> >>>> >>>> Giovanni >>> >>> >>> >>> -- >>> Thiago Bellini | http://hackedbellini.org >>> >>> “Real knowledge is to know the extent of one's ignorance.” - Confucius >>> _______________________________________________ >>> gnome-shell-list mailing list >>> gnome-shell-list@gnome.org >>> https://mail.gnome.org/mailman/listinfo/gnome-shell-list >> >> >> >> -- >> Jasper > > > > -- > Thiago Bellini | http://hackedbellini.org > > “Real knowledge is to know the extent of one's ignorance.” - Confucius -- Thiago Bellini | http://hackedbellini.org “Real knowledge is to know the extent of one's ignorance.” - Confucius _______________________________________________ gnome-shell-list mailing list gnome-shell-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-shell-list
