Update GnuTLS minimum dependency to 2.12.0?
In order to complete the GIO TLS Database work [1] for smart cards and other PKCS#11 databases (like gnome-keyring), it looks like I'll need to update the GnuTLS dependency [2] to 2.12.0 or later. Any objections to doing this? Are we too late in the release cycle? The alternative to updating is to doing a mess of #ifdef soup, which I'm not really keen on. Cheers, Stef [1] https://bugzilla.gnome.org/show_bug.cgi?id=656361 [2] https://bugzilla.gnome.org/show_bug.cgi?id=656903 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing bug-buddy?
On Fri, 2011-08-26 at 00:05 +0200, Olav Vitters wrote: > That all said, I propose killing bug-buddy and recommending the usage > of ABRT. Hi, well, there are things about ABRT you might want to know. The feature of "ABRT talking to bugzilla" is not that great, as it talks to downstream bugzilla only, it doesn't know how to talk to upstream bugzilla like the Gnome's. You might notice significantly less bug crashers reported by regular users since ABRT got in use, those bugs are usually moved manually to Gnome's bugzilla. Though 'usually' here doesn't mean much, because there is no enough man power to investigate and move each ABRT downstream report to upstream, basically the work I would expect triage team does, thus one might become a monkey for moving bugs between bugzillas instead of fixing those bugs. What's the gain of ABRT then? But to be correct, I was told that there is only a matter of writing a plugin for Gnome bugzilla (I do not know whether it is written already or not, I lost track of it after more than a year), so maybe once that is written, and downstream packagers will be able to instruct ABRT to use certain bugzilla instead of the distribution's (which might be already possible with latest ABRT, I suppose), then that will be the time when ABRT will be usable for upstream projects too. I guess you want to kill bug-buddy for regular users only, as you was talking about bugzilla connection, because ABRT is unusable for developers, as it silently ignores crashes in applications which are not packaged, furthermore, if you enable to catch crashes of unpackaged applications, then it is not able to get the backtrace right. That's a reason why I resurrected bug-buddy on my machine, also for gtk3 applications, thus I know why my application is crashing, and when. Anyway, from my point of view, if there will be a real replacement of bug-buddy, which for ABRT means being able to directly report to upstream bugzilla for upstream projects, then I'm totally for it. Bye, Milan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Killing bug-buddy?
The Bugzilla developers pinged me regarding the GNOME Bugzilla version. So I checked a bit into what changes we have. One of the big difference vs upstream that is hard to change into an extension is the way Bug-Buddy interacts with Bugzilla. It was meant to use the standard XML-RPC method, but unfortunately the API changed after we used it. Furthermore, Bug-Buddy actually creates new users in Bugzilla and never really investigates if that email address belong to the user (tradeoff between security and easy of use). That is something that upstream obviously never does. Since Bug-Buddy was created, there have been other tools to catch crashers. The one I know is ABRT; I know it can interact with Bugzilla, but that requires you to fill in your Bugzilla account information in ABRT. Other than that, I have 0 knowledge regarding ABRT. That all said, I propose killing bug-buddy and recommending the usage of ABRT. As mentioned, I don't know if this makes sense; but really hope it does. I'm guessing we'll need to work with the various distributions to ensure the crashers still get sent to us. Comments / advice? -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
I recently added a to the gudev module in jhbuild, so you should get the system gudev if your system is halfway modern and not have jhbuild build that very old version. We can certainly bump the version that jhbuild will try to build to something less ancient, too. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
Malcom, there are two distincts parts to SweetTooth: - A server part (repository sweettooth) which is intended to run on http://extensions.gnome.org and requires a database but doesn't need any packaging. - And the plugin for gnome-shell (repository sweettooth-plugin) which provide integration between the shell and the server, this need packaging but doesn't use a database. HTH. On Thu, Aug 25, 2011 at 5:47 PM, Jasper St. Pierre wrote: > On Thu, Aug 25, 2011 at 11:44 AM, Malcolm > wrote: > > On Thu, 25 Aug 2011 11:31:32 -0400 > > "Jasper St. Pierre" > > wrote: > > > >> http://github.com/magcius/sweettooth is intended to be deployed in one > >> place: extensions.gnome.org. It's not intended to be packaged. > >> > > This is just the plugin? Or is that deployed into the users directory > > too, not system wide? > > > > Aside from that, can you clarify the steps to setup the database? > > What database? The plugin has no database. > > > -- > > Cheers Malcolm °¿° (Linux Counter #276890) > > openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop > > up 2 days 1:27, 4 users, load average: 0.00, 0.05, 0.11 > > GPU GeForce 8600 GTS Silent - Driver Version: 280.13 > > > > > > ___ > > gnome-shell-list mailing list > > gnome-shell-l...@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-shell-list > > > > > > -- > Jasper > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Olivier Lê Thanh Duong Phone : +32487892093 Jabber: oleth...@gmail.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
On Thu, Aug 25, 2011 at 11:44 AM, Malcolm wrote: > On Thu, 25 Aug 2011 11:31:32 -0400 > "Jasper St. Pierre" > wrote: > >> http://github.com/magcius/sweettooth is intended to be deployed in one >> place: extensions.gnome.org. It's not intended to be packaged. >> > This is just the plugin? Or is that deployed into the users directory > too, not system wide? > > Aside from that, can you clarify the steps to setup the database? What database? The plugin has no database. > -- > Cheers Malcolm °¿° (Linux Counter #276890) > openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop > up 2 days 1:27, 4 users, load average: 0.00, 0.05, 0.11 > GPU GeForce 8600 GTS Silent - Driver Version: 280.13 > > > ___ > gnome-shell-list mailing list > gnome-shell-l...@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-shell-list > -- Jasper ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
http://github.com/magcius/sweettooth is intended to be deployed in one place: extensions.gnome.org. It's not intended to be packaged. On Thu, Aug 25, 2011 at 10:56 AM, Malcolm wrote: > On Thu, 25 Aug 2011 05:03:18 -0400 > "Jasper St. Pierre" wrote: > >> On Thu, Aug 25, 2011 at 4:53 AM, Olav Vitters wrote: >> > On Wed, Aug 24, 2011 at 02:00:32PM -0400, Jasper St. Pierre wrote: >> >> For 3.2, besides item #5, I'm going to be working on all the >> >> "boring" stuff that needs to be done in a webapp (user >> >> registration, etc.), a simple page that lets you enable/disable >> >> all the extensions on your machine, as well as general UI polish. >> >> For 3.4, I hope to get updates working. >> > >> > Nice work! >> > >> > When do you expect the website code is good enough to be hosted on >> > GNOME? Could you also document the requirements (software, disk >> > space, etc)? >> >> The Python package requirements are listed at >> https://github.com/magcius/sweettooth. >> You can see how much disk space the git checkout takes there, and we >> also have to save >> any user-uploaded data -- extension zipfiles and images. That >> shouldn't take too much space, >> though. >> >> Additionally, if someone wants to help me make >> https://github.com/magcius/sweettooth-plugin >> more packageable it would be much appreciated. If you want me to >> transfer to the GNOME Git >> Infrastructure so that things like i18n can be done better (I >> currently have no support for i18n), >> please tell me. >> >> > It would be nice to have something at .91 / .92 (rc) stage (see >> > https://live.gnome.org/ThreePointOne for schedule). I'd prefer >> > having something available even if not totally complete so that >> > people can test and also the website itself has been used. >> >> I'm working on the generic polish as well as a few last features so >> that I can get something ready >> for 2.91/2.92. >> >> > -- >> > Regards, >> > Olav >> > >> >> Jasper > Hi > I've already packaged as an rpm > http://software.opensuse.org/search?q=sweettooth&baseproject=openSUSE%3AFactory&lang=en&include_home=true&exclude_debug=true > https://build.opensuse.org/package/files?package=sweettooth-plugin&project=home%3Amalcolmlewis%3AGNOME%3A3.0 > > Some more info or a pointer for the database setup would be helpful, I > have setup the python environment fine, just not sure wht to do for the > database? > > -- > Cheers Malcolm °¿° (Linux Counter #276890) > openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop > up 2 days 0:38, 4 users, load average: 0.37, 0.31, 0.16 > GPU GeForce 8600 GTS Silent - Driver Version: 280.13 > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list -- Jasper ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 03:14:09PM +0300, Claudio Saavedra wrote: > I guess a configuration option not to build the recommended package > version at all if the minimum version required is present would help > those wanting to go through the build as quickly as possible. I said the same thing; There is no such distinction at the moment. So any version in jhbuild would be interpreted as the minimum. So if you put the recommended version in there, it would be seen as the minimum. Other words: At the moment, if the distro version has the minimum, jhbuild has the recommended, jhbuild is NOT going to use the system version because it cannot tell it is ok. It would be nice to change that, but think the work to use more things from the distribution is nicer. It makes building GNOME easier. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 02:04:25PM +0200, Olav Vitters wrote: > >Not for me so far, just that davidz said lots of bugs have been > > fixed since version 147. > > It might be better to focus on what Colin is working on in jhbuild; to > make it use system dependencies if they're available. However, it > assumes the version in jhbuild is the minimum required version. Shouldn't jhbuild build the recommended version instead? I hardly see the point on building, in some cases, fairly outdated packages. The minimum required version makes sense when you bypass building the package and just use the system version. You don't alienate developers willing to build their own packages if you let them build a recommended instead of a minimum version. I guess a configuration option not to build the recommended package version at all if the minimum version required is present would help those wanting to go through the build as quickly as possible. Claudio ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
On Thu, 25 Aug 2011 05:03:18 -0400 "Jasper St. Pierre" wrote: > On Thu, Aug 25, 2011 at 4:53 AM, Olav Vitters wrote: > > On Wed, Aug 24, 2011 at 02:00:32PM -0400, Jasper St. Pierre wrote: > >> For 3.2, besides item #5, I'm going to be working on all the > >> "boring" stuff that needs to be done in a webapp (user > >> registration, etc.), a simple page that lets you enable/disable > >> all the extensions on your machine, as well as general UI polish. > >> For 3.4, I hope to get updates working. > > > > Nice work! > > > > When do you expect the website code is good enough to be hosted on > > GNOME? Could you also document the requirements (software, disk > > space, etc)? > > The Python package requirements are listed at > https://github.com/magcius/sweettooth. > You can see how much disk space the git checkout takes there, and we > also have to save > any user-uploaded data -- extension zipfiles and images. That > shouldn't take too much space, > though. > > Additionally, if someone wants to help me make > https://github.com/magcius/sweettooth-plugin > more packageable it would be much appreciated. If you want me to > transfer to the GNOME Git > Infrastructure so that things like i18n can be done better (I > currently have no support for i18n), > please tell me. > > > It would be nice to have something at .91 / .92 (rc) stage (see > > https://live.gnome.org/ThreePointOne for schedule). I'd prefer > > having something available even if not totally complete so that > > people can test and also the website itself has been used. > > I'm working on the generic polish as well as a few last features so > that I can get something ready > for 2.91/2.92. > > > -- > > Regards, > > Olav > > > > Jasper Hi I've already packaged as an rpm http://software.opensuse.org/search?q=sweettooth&baseproject=openSUSE%3AFactory&lang=en&include_home=true&exclude_debug=true https://build.opensuse.org/package/files?package=sweettooth-plugin&project=home%3Amalcolmlewis%3AGNOME%3A3.0 Some more info or a pointer for the database setup would be helpful, I have setup the python environment fine, just not sure wht to do for the database? -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop up 2 days 0:38, 4 users, load average: 0.37, 0.31, 0.16 GPU GeForce 8600 GTS Silent - Driver Version: 280.13 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 08:31:40AM -0400, David Zeuthen wrote: > On Thu, Aug 25, 2011 at 7:36 AM, Olav Vitters wrote: > > On Thu, Aug 25, 2011 at 01:34:36PM +0300, Zeeshan Ali (Khattak) wrote: > >> Ah, sorry! My dyslexia kicks-in sometimes. However, thats still > >> pretty old so my question remains. > > > > We upgrade if needed. Keeping the requirements low makes it easier to > > use stuff from your distribution. > > > > Is a newer version needed? > > In this particular case, libgudev version 163 has a bug fix so the > library can be used safely in multi-threaded applications. This is the > commit in question > > > http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=cbdf255e255adc0f30b40be296fbbf2f3cd2be80 > > In the future, for gudev, please either track HEAD or rely on the > distro to provide a sufficiently new version (ideally the latter) - > this business of locking onto old versions is just very bad practice > and confusing for everyone and it's pretty annoying to see that bug > fixes made almost a year ago isn't being used. Who knows what other > kinds of bugs this has caused... I explained the reasoning in my other reply. Distro version should be used. Regarding tracking head: This causes problems during release time. We then have to wait for tarballs and there are only 2 days in total for any GNOME release to get everything QA'ed + fixes + released. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, 2011-08-25 at 14:22 +0200, Stefan Kost wrote: > I am currently jhbuilding under Ubuntu lucid and alredy there, lots of > modules get skipped. Mostly because of libusb>=1.0 requirement. Lucid > has 0.1.12 (without a pc file in the -dev package) :/. Imho not a lot of > stuff is anymore buildable under karmic. > > Stefan libusb-1 != libusb. They're different projects and are parallel installable. Maybe it's an option to include libusb-1 in jhbuild for that, the library isn't very common on the more conservative distributions. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
Hello Stefan, Stefan Kost [2011-08-25 14:22 +0200]: > I am currently jhbuilding under Ubuntu lucid and alredy there, lots of > modules get skipped. Mostly because of libusb>=1.0 requirement. Lucid > has 0.1.12 (without a pc file in the -dev package) :/ Note that this is an ancient version. For GNOME you really want libusb-1.0-dev, which is 1.0.6 in lucid, and 1.0.8 in the current devel release. It also has a .pc file. Unfortunately there are still some ancient reverse dependencies of the old libusb, so that it can't be removed yet. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
Hi, On Thu, Aug 25, 2011 at 7:36 AM, Olav Vitters wrote: > On Thu, Aug 25, 2011 at 01:34:36PM +0300, Zeeshan Ali (Khattak) wrote: >> Ah, sorry! My dyslexia kicks-in sometimes. However, thats still >> pretty old so my question remains. > > We upgrade if needed. Keeping the requirements low makes it easier to > use stuff from your distribution. > > Is a newer version needed? In this particular case, libgudev version 163 has a bug fix so the library can be used safely in multi-threaded applications. This is the commit in question http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=cbdf255e255adc0f30b40be296fbbf2f3cd2be80 In the future, for gudev, please either track HEAD or rely on the distro to provide a sufficiently new version (ideally the latter) - this business of locking onto old versions is just very bad practice and confusing for everyone and it's pretty annoying to see that bug fixes made almost a year ago isn't being used. Who knows what other kinds of bugs this has caused... David ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On 08/25/11 13:44, Craig Keogh wrote: > On Thu, 2011-08-25 at 13:34 +0300, Zeeshan Ali (Khattak) wrote: >> On Thu, Aug 25, 2011 at 1:30 PM, Andre Klapper wrote: >>> On Thu, 2011-08-25 at 13:23 +0300, Zeeshan Ali (Khattak) wrote: Hi everyone, David Zeuthen pointed out that gudev in jhbuild (3.2 modulesets) is several years old (from 08-Dec-2004) >>> For the records, >>> http://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-suites-core-deps-3.2.modules >>> says module="utils/kernel/hotplug/udev-147.tar.bz2" version="147". >>> That's 10-Nov-2009 according to >>> https://www.kernel.org/pub/linux/utils/kernel/hotplug/ >>> >>> 047 is from 08-Dec-2004. >> Ah, sorry! My dyslexia kicks-in sometimes. However, thats still >> pretty old so my question remains. >> > gudev is packaged in the one tarball with udev. Therefore I assumed that > gudev version 147 requires >= udev 147. udev 147 was selected so JHBuild > supports as many distros as possible. I don't want to alienate potential > developers because their distro is a tiny bit old. > > Distro's with udev 147: > Ubuntu >= 9.10 karmic > Fedora >= 13 goddard > Mint >= 8 helena > openSUSE >= 11.3 > Red Hat >= RHEL-6 > Mandriva >= 2010.1 > I am currently jhbuilding under Ubuntu lucid and alredy there, lots of modules get skipped. Mostly because of libusb>=1.0 requirement. Lucid has 0.1.12 (without a pc file in the -dev package) :/. Imho not a lot of stuff is anymore buildable under karmic. Stefan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 02:47:35PM +0300, Zeeshan Ali (Khattak) wrote: > On Thu, Aug 25, 2011 at 2:36 PM, Olav Vitters wrote: > > On Thu, Aug 25, 2011 at 01:34:36PM +0300, Zeeshan Ali (Khattak) wrote: > >> Ah, sorry! My dyslexia kicks-in sometimes. However, thats still > >> pretty old so my question remains. > > > > We upgrade if needed. Keeping the requirements low makes it easier to > > use stuff from your distribution. > > Please note that I was talking of providing a newer gudev in > jhbuild, not bump the minimum requirement. >From my POV it is effectively the same thing. If the newer version is used in gudev, then jhbuilders + buildbots + release-team won't notice if you depend on a newer gudev. > > Is a newer version needed? > >Not for me so far, just that davidz said lots of bugs have been > fixed since version 147. It might be better to focus on what Colin is working on in jhbuild; to make it use system dependencies if they're available. However, it assumes the version in jhbuild is the minimum required version. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 2:36 PM, Olav Vitters wrote: > On Thu, Aug 25, 2011 at 01:34:36PM +0300, Zeeshan Ali (Khattak) wrote: >> Ah, sorry! My dyslexia kicks-in sometimes. However, thats still >> pretty old so my question remains. > > We upgrade if needed. Keeping the requirements low makes it easier to > use stuff from your distribution. Please note that I was talking of providing a newer gudev in jhbuild, not bump the minimum requirement. > Is a newer version needed? Not for me so far, just that davidz said lots of bugs have been fixed since version 147. -- Regards, Zeeshan Ali (Khattak) FSF member#5124 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, 2011-08-25 at 13:34 +0300, Zeeshan Ali (Khattak) wrote: > On Thu, Aug 25, 2011 at 1:30 PM, Andre Klapper wrote: > > On Thu, 2011-08-25 at 13:23 +0300, Zeeshan Ali (Khattak) wrote: > >> Hi everyone, > >> David Zeuthen pointed out that gudev in jhbuild (3.2 modulesets) is > >> several years old (from 08-Dec-2004) > > > > For the records, > > http://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-suites-core-deps-3.2.modules > > says module="utils/kernel/hotplug/udev-147.tar.bz2" version="147". > > That's 10-Nov-2009 according to > > https://www.kernel.org/pub/linux/utils/kernel/hotplug/ > > > > 047 is from 08-Dec-2004. > > Ah, sorry! My dyslexia kicks-in sometimes. However, thats still > pretty old so my question remains. > gudev is packaged in the one tarball with udev. Therefore I assumed that gudev version 147 requires >= udev 147. udev 147 was selected so JHBuild supports as many distros as possible. I don't want to alienate potential developers because their distro is a tiny bit old. Distro's with udev 147: Ubuntu >= 9.10 karmic Fedora >= 13 goddard Mint >= 8 helena openSUSE >= 11.3 Red Hat >= RHEL-6 Mandriva >= 2010.1 -- Craig Keogh ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 01:34:36PM +0300, Zeeshan Ali (Khattak) wrote: > Ah, sorry! My dyslexia kicks-in sometimes. However, thats still > pretty old so my question remains. We upgrade if needed. Keeping the requirements low makes it easier to use stuff from your distribution. Is a newer version needed? -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, Aug 25, 2011 at 1:30 PM, Andre Klapper wrote: > On Thu, 2011-08-25 at 13:23 +0300, Zeeshan Ali (Khattak) wrote: >> Hi everyone, >> David Zeuthen pointed out that gudev in jhbuild (3.2 modulesets) is >> several years old (from 08-Dec-2004) > > For the records, > http://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-suites-core-deps-3.2.modules > says module="utils/kernel/hotplug/udev-147.tar.bz2" version="147". > That's 10-Nov-2009 according to > https://www.kernel.org/pub/linux/utils/kernel/hotplug/ > > 047 is from 08-Dec-2004. Ah, sorry! My dyslexia kicks-in sometimes. However, thats still pretty old so my question remains. -- Regards, Zeeshan Ali (Khattak) FSF member#5124 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gudev from my grandpa
On Thu, 2011-08-25 at 13:23 +0300, Zeeshan Ali (Khattak) wrote: > Hi everyone, > David Zeuthen pointed out that gudev in jhbuild (3.2 modulesets) is > several years old (from 08-Dec-2004) For the records, http://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-suites-core-deps-3.2.modules says module="utils/kernel/hotplug/udev-147.tar.bz2" version="147". That's 10-Nov-2009 according to https://www.kernel.org/pub/linux/utils/kernel/hotplug/ 047 is from 08-Dec-2004. andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper | http://www.openismus.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
gudev from my grandpa
Hi everyone, David Zeuthen pointed out that gudev in jhbuild (3.2 modulesets) is several years old (from 08-Dec-2004) and we really should use some recent enough release of it. Is there a particular reason we are doing this or shall I fix this? -- Regards, Zeeshan Ali (Khattak) FSF member#5124 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
On Thu, Aug 25, 2011 at 4:53 AM, Olav Vitters wrote: > On Wed, Aug 24, 2011 at 02:00:32PM -0400, Jasper St. Pierre wrote: >> For 3.2, besides item #5, I'm going to be working on all the "boring" >> stuff that needs to be done in a webapp (user registration, etc.), a >> simple page that lets you enable/disable all the extensions on your >> machine, as well as general UI polish. For 3.4, I hope to get updates >> working. > > Nice work! > > When do you expect the website code is good enough to be hosted on > GNOME? Could you also document the requirements (software, disk space, > etc)? The Python package requirements are listed at https://github.com/magcius/sweettooth. You can see how much disk space the git checkout takes there, and we also have to save any user-uploaded data -- extension zipfiles and images. That shouldn't take too much space, though. Additionally, if someone wants to help me make https://github.com/magcius/sweettooth-plugin more packageable it would be much appreciated. If you want me to transfer to the GNOME Git Infrastructure so that things like i18n can be done better (I currently have no support for i18n), please tell me. > It would be nice to have something at .91 / .92 (rc) stage (see > https://live.gnome.org/ThreePointOne for schedule). I'd prefer having > something available even if not totally complete so that people can test > and also the website itself has been used. I'm working on the generic polish as well as a few last features so that I can get something ready for 2.91/2.92. > -- > Regards, > Olav > Jasper ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
On Wed, Aug 24, 2011 at 02:00:32PM -0400, Jasper St. Pierre wrote: > For 3.2, besides item #5, I'm going to be working on all the "boring" > stuff that needs to be done in a webapp (user registration, etc.), a > simple page that lets you enable/disable all the extensions on your > machine, as well as general UI polish. For 3.4, I hope to get updates > working. Nice work! When do you expect the website code is good enough to be hosted on GNOME? Could you also document the requirements (software, disk space, etc)? It would be nice to have something at .91 / .92 (rc) stage (see https://live.gnome.org/ThreePointOne for schedule). I'd prefer having something available even if not totally complete so that people can test and also the website itself has been used. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SweetTooth and Live Extension Enabling/Disabling
"Jasper St. Pierre" writes: Hi Jasper, >> 3. After a crash, the fail-whale dialog will show you your enabled >> extensions with an option to disable them before restarting the Shell. > Done. [2] So if the shell crashed because of some extension, I'm able to disable that and the shell will restart, right? But I think the issue I reported at https://bugzilla.gnome.org/show_bug.cgi?id=656813 is not completely solved by that. Bye, Tassilo ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
