From: Martin B. / b. <br...@bs...> - 2009-12-31 14:57:21
|
Hi everyone As announced earlier this month we are about to release LXApperance, the string freeze period is over. Problem is that I have not been able to add files from the tracker at SF and mwei[1] prodded about some issue at the IRC channel. Lastly, I can not do the release, I have no knowledge about how to and looking at the SF pages earlier this week I could not find out how to do it. [1] <medicalwei> lxappearance cannot run with the newest svn version, and main-dlg-ui.{c,h} are missing. Is it a UI redesign? The following things is needed as far as I can tell. 1) check with mwie about what's wrong / test the trunk again 2) add po files (there might not be any) from SF.net patch tracker 3) release 4) announce it in a proper way. And a happy new year (when ever it might happen, time zone wise or cultural =)) -- brother |
From: Andrea F. <an...@op...> - 2009-12-31 15:35:57
Attachments:
lxdm-use-sysconfig.patch
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys... i attached a patch we will use on openSUSE. This patch allow lxdm to Learn about Default Session and Autologin User from systemwide /etc/sysconfig/something settings files... Also fedora (on what i know) use that settings (even if on a different sysconfig files, and only for dafault session). This patch actually make LXDM able to read ONLY from thos sysconfig files, and for what i care is enought. i suggest any way to merge this patch upstream with the following modification: lxdm read first from sysconfig file (if any), if not settings found there then read from /etc/lxdm/lxdm.conf btw, the 2 new source code files /gdm-sysconfig.(c,h) are the exactly the same one openSUSE use, so they are fine even from security side :) feel free to use and fix it and hopefully merge upstream. Regards Andrea - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: an...@op... Packman Packaging Team Email: an...@li... Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAks8xOkACgkQyCZT87TFPuhl5gCguB2f2jt8T+WqBipPSQL6V/48 GW8AoIZkfNqL/Jxxyx9znwA8mWDwXN3m =UYGu -----END PGP SIGNATURE----- |
From: PCMan <pcm...@gm...> - 2010-01-01 00:36:44
|
IMHO, distro-specific stuff should only belong to patches rather than be included in upstream code since its totally useless for other distros, but the decision should be made by dgod since he is the developer of lxdm. On Thu, Dec 31, 2009 at 11:36 PM, Andrea Florio <an...@op...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi guys... i attached a patch we will use on openSUSE. > > This patch allow lxdm to Learn about Default Session and Autologin User > from systemwide /etc/sysconfig/something settings files... > > Also fedora (on what i know) use that settings (even if on a different > sysconfig files, and only for dafault session). > > > This patch actually make LXDM able to read ONLY from thos sysconfig > files, and for what i care is enought. > > i suggest any way to merge this patch upstream with the following > modification: > > lxdm read first from sysconfig file (if any), > if not settings found there then read from > /etc/lxdm/lxdm.conf > > btw, the 2 new source code files /gdm-sysconfig.(c,h) are the exactly > the same one openSUSE use, so they are fine even from security side :) > > feel free to use and fix it and hopefully merge upstream. > > Regards > Andrea > > > - -- > - ------------------------------------------ > Andrea Florio > QSI International School of Brindisi Sys Admin > openSUSE-Education Administrator > openSUSE Official Member (anubisg1) > Email: an...@op... > Packman Packaging Team > Email: an...@li... > Web: http://packman.links2linux.org/ > Cell: +39-328-7365667 > - ------------------------------------------ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.12 (GNU/Linux) > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ > > iEYEARECAAYFAks8xOkACgkQyCZT87TFPuhl5gCguB2f2jt8T+WqBipPSQL6V/48 > GW8AoIZkfNqL/Jxxyx9znwA8mWDwXN3m > =UYGu > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > > |
From: Alessandro P. <al...@am...> - 2010-01-01 08:34:03
|
Il giorno ven, 01/01/2010 alle 08.33 +0800, PCMan ha scritto: > IMHO, distro-specific stuff should only belong to patches rather than > be included in upstream code I totally agree. It also adds code bloat on unrelated distros, and could drive to "merge any distro configuration in mainstream". Bye. |
From: Christoph W. <chr...@go...> - 2010-01-01 11:57:09
|
Am Freitag, den 01.01.2010, 09:32 +0100 schrieb Alessandro Pellizzari: > Il giorno ven, 01/01/2010 alle 08.33 +0800, PCMan ha scritto: > > > IMHO, distro-specific stuff should only belong to patches rather than > > be included in upstream code > > I totally agree. And I have to say I disagree. /etc/sysconfig/* is not really distro specfic, it is used by many distros: Fedora, Red Hat, (Open)SUSE, Mandriva, Foresight, and many more (basically all that use Red Hat's initscripts and this is nearly everything but Debian/Ubuntu). Just as we read locale configuration from /etc/profile or /etc/sysconfig/i18n, we might also support other configuration options. If they are not set, fall back to /etc/lxdm/lxdm.conf (which IMO should be /etc/xdg/lxdm/lxdm.conf btw). > It also adds code bloat on unrelated distros, and could drive to "merge > any distro configuration in mainstream". Not sure if I understand the second part of your sentence... > Bye. Regards, Christoph |
From: Alessandro P. <al...@am...> - 2010-01-01 22:34:09
|
Il giorno ven, 01/01/2010 alle 12.56 +0100, Christoph Wickert ha scritto: > And I have to say I disagree. /etc/sysconfig/* is not really distro > specfic, it is used by many distros: Fedora, Red Hat, (Open)SUSE, > Mandriva, Foresight, and many more (basically all that use Red Hat's > initscripts and this is nearly everything but Debian/Ubuntu). And slackware, sidux, all of BSDs, Solaris, etc. etc. > > It also adds code bloat on unrelated distros, and could drive to "merge > > any distro configuration in mainstream". > > Not sure if I understand the second part of your sentence... Having some config read for RH based, maybe someone else wants the same facility for Debian/Ubuntu/sidux, someone else for Slackware, and another one for FreeBSD. Now we have 4 different config readers in the mainstream. All of them should be maintained stable and tested, and 3 out of 4 of them are completely useless in any distro. Being LXDE oriented toward "small and efficient" software, I consider this as code bloat. If there is a FHS or a freedesktop.org specification for that, that should be implemented. Lacking that, only the base config should be used mainstream, and distro-specific code should be added by distro maintainers as distro-patches. Just IMHO. Bye. |
From: Andrew L. <aj...@de...> - 2010-01-02 05:16:26
|
Christoph Wickert wrote: >>> IMHO, distro-specific stuff should only belong to patches rather than >>> be included in upstream code >> I totally agree. > > And I have to say I disagree. /etc/sysconfig/* is not really distro > specfic, it is used by many distros: Fedora, Red Hat, (Open)SUSE, > Mandriva, Foresight, and many more (basically all that use Red Hat's > initscripts and this is nearly everything but Debian/Ubuntu). I agree with PCMan's opinion. These should only belong to patches rather than included in upstream code. We shouldn't argue here on how many distros use /etc/sysconfig/*. And there are more than just Linux Distros. We also have users who would use lxde with OpenSolaris, *BSD... and so on. Best reagrds, -Andrew |
From: Jürgen H. <ju...@ar...> - 2010-01-02 22:59:27
|
2009/12/31 Andrea Florio <an...@op...> > This patch allow lxdm to Learn about Default Session and Autologin User > from systemwide /etc/sysconfig/something settings files... > > Also fedora (on what i know) use that settings (even if on a different > sysconfig files, and only for dafault session). > > > This patch actually make LXDM able to read ONLY from thos sysconfig > files, and for what i care is enought. > > Although I understand the purpose of this patch for system-wide configuration of a Display Manger I question the implementation: Lots of code (written in C) is added to parse (most likely error prone) distribution-specific shell Code. LXDM is already started by a shell script which loads /etc/sysconfig/i18n and sets LANG. Why not override additional LXDM configuration by using additional environment variables or command line arguments? Jürgen |
From: Martin B. <br...@bs...> - 2010-01-06 15:14:08
|
BUMP No reaction for a week. What's up? On Thu, 31 Dec 2009, Martin Bagge / brother wrote: > Hi everyone > As announced earlier this month we are about to release LXApperance, the > string freeze period is over. Problem is that I have not been able to add > files from the tracker at SF and mwei[1] prodded about some issue at the > IRC channel. Lastly, I can not do the release, I have no knowledge about > how to and looking at the SF pages earlier this week I could not find out > how to do it. > > [1] <medicalwei> lxappearance cannot run with the newest svn version, and > main-dlg-ui.{c,h} are missing. Is it a UI redesign? > > > The following things is needed as far as I can tell. > 1) check with mwie about what's wrong / test the trunk again > 2) add po files (there might not be any) from SF.net patch tracker > 3) release > 4) announce it in a proper way. > > And a happy new year (when ever it might happen, time zone wise or > cultural =)) > -- /brother http://sis.bthstudent.se Bruce Schneier's fists violate the anti-circumvention clause of the Digital Millennium Copyright Act. |
From: Andrew L. <aj...@de...> - 2010-01-06 16:25:10
|
Martin Bagge wrote: >> The following things is needed as far as I can tell. >> 1) check with mwie about what's wrong / test the trunk again Does matter, I've tested the SVN version. It works fine on Debian. >> 2) add po files (there might not be any) from SF.net patch tracker Skip. >> 3) release Just find the way to upload the tarball to SF.net. It should be display now on that. >> 4) announce it in a proper way. I cannot find a way to edit the release note of the tarball on SF.net. Below are the changes(collected from svn log) in this release: - Replace all Glade-generated code with GtkBuilder - Use icon names defined in newer icon naming spec. - UI adjustment - Fix memory leaks and compiler warnings. - Translation update Best regards, -Andrew |
From: Julien L. <gi...@ub...> - 2010-01-07 22:30:25
|
Hi, It seems that some changes occurred between the last call for testing and the release of 0.4.0. I can see a new bug : UI for changing the window theme (1st tab) is different, and now all icons doesn't appear with the default size of the window. This is annoying because you need to resize it at each startup. There is also another bug, but it seems to be cause by a recent update (maybe GTK) on Ubuntu 10.04 : when you launch it with lxterminal, and you clic on "Apply", the background of lxterminal change to white (instead of black). Regards, Julien Lavergne Le jeudi 31 décembre 2009 à 15:56 +0100, Martin Bagge / brother a écrit : > Hi everyone > As announced earlier this month we are about to release LXApperance, the > string freeze period is over. Problem is that I have not been able to add > files from the tracker at SF and mwei[1] prodded about some issue at the > IRC channel. Lastly, I can not do the release, I have no knowledge about > how to and looking at the SF pages earlier this week I could not find out > how to do it. > > [1] <medicalwei> lxappearance cannot run with the newest svn version, and > main-dlg-ui.{c,h} are missing. Is it a UI redesign? > > > The following things is needed as far as I can tell. > 1) check with mwie about what's wrong / test the trunk again > 2) add po files (there might not be any) from SF.net patch tracker > 3) release > 4) announce it in a proper way. > > And a happy new year (when ever it might happen, time zone wise or > cultural =)) |
From: Andrew L. <aj...@de...> - 2010-01-08 06:27:01
|
Hi Julien, Julien Lavergne wrote: > It seems that some changes occurred between the last call for testing > and the release of 0.4.0. I can see a new bug : UI for changing the > window theme (1st tab) is different, and now all icons doesn't appear > with the default size of the window. This is annoying because you need > to resize it at each startup. I don't see problem on my system. I am not sure if I know what do you mean exactly. Would you mind to provide a screenshot? > There is also another bug, but it seems to be cause by a recent update > (maybe GTK) on Ubuntu 10.04 : when you launch it with lxterminal, and > you clic on "Apply", the background of lxterminal change to white > (instead of black). I also cannot reproduce this on Debian sid. I just uploaded this package into sid. Hope it would helpful. Best regards, -Andrew > Le jeudi 31 décembre 2009 à 15:56 +0100, Martin Bagge / brother a > écrit : >> Hi everyone >> As announced earlier this month we are about to release LXApperance, the >> string freeze period is over. Problem is that I have not been able to add >> files from the tracker at SF and mwei[1] prodded about some issue at the >> IRC channel. Lastly, I can not do the release, I have no knowledge about >> how to and looking at the SF pages earlier this week I could not find out >> how to do it. >> >> [1] <medicalwei> lxappearance cannot run with the newest svn version, and >> main-dlg-ui.{c,h} are missing. Is it a UI redesign? >> >> >> The following things is needed as far as I can tell. >> 1) check with mwie about what's wrong / test the trunk again >> 2) add po files (there might not be any) from SF.net patch tracker >> 3) release >> 4) announce it in a proper way. >> >> And a happy new year (when ever it might happen, time zone wise or >> cultural =)) > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |
From: Julien L. <gi...@ub...> - 2010-01-09 10:21:42
|
Le vendredi 08 janvier 2010 à 14:26 +0800, Andrew Lee a écrit : > > I don't see problem on my system. I am not sure if I know what do you > mean exactly. Would you mind to provide a screenshot? Sure : http://people.ubuntu.com/~gilir/Capture-1.png On the left, it's the 0.4 version. On the right, the 0.3. > > There is also another bug, but it seems to be cause by a recent update > > (maybe GTK) on Ubuntu 10.04 : when you launch it with lxterminal, and > > you clic on "Apply", the background of lxterminal change to white > > (instead of black). > > I also cannot reproduce this on Debian sid. I just uploaded this package > into sid. Hope it would helpful. Thanks, I'll sync it on Ubuntu if I have no remaining changes for this package. Also, the white-background bug occur very recently on Ubuntu Lucid, maybe it's a GTK or a Glib unstable uploads (available on Debian experimental if I remember correctly) which break this. I'll try to investigate a bit more. Regards, Julien Lavergne |