From: Christoph W. <chr...@go...> - 2009-12-11 19:34:08
|
I am very concerned about the recent LXDE updates: * After updating to lxsession-0.4.1, lxde-common-0.5.0 and lxappearance 0.3.0, I can no longer log into LXDE. Instead I get back to the login screen after a second. It doesn't work with a new user ether, so it's not related to my configuration. Any ideas how to debug this? * Even if I can fix these problems, it is not possible to upgrade to the latest components because the config file has changed. As a package maintainer I cannot do such a change in the lifetime of a stable release. This means that LXDE cannot receive any more updates although Fedora 12 was released less than a month ago. * With the new location of the config files we also need a new lxinput, but it's not yet released. IMO we should release all dependent packages at once. * lxpanel-0.5.4 wont build because configure breaks due to the missing cpufreq plugin. Was the plugin supposed to be in the tarball or was configure not updated before doing the release? Was it tested at all? To summarize the above: We need a better quality assurance. Packages must be tested before they get released. Regards, Christoph |
From: Andrea F. <an...@op...> - 2009-12-11 20:06:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 11/12/2009 20:33, Christoph Wickert ha scritto: > I am very concerned about the recent LXDE updates: > > * After updating to lxsession-0.4.1, lxde-common-0.5.0 and > lxappearance 0.3.0, I can no longer log into LXDE. Instead I get > back to the login screen after a second. It doesn't work with a > new user ether, so it's not related to my configuration. Any > ideas how to debug this? i fixed it changing startlxde script # Start the LXDE session - -exec @prefix@/bin/lxsession -s LXDE +exec @prefix@/bin/lxsession -s LXDE -e LXDE > * Even if I can fix these problems, it is not possible to upgrade > to the latest components because the config file has changed. As > a package maintainer I cannot do such a change in the lifetime > of a stable release. This means that LXDE cannot receive any > more updates although Fedora 12 was released less than a month > ago. i agree > * With the new location of the config files we also need a new > lxinput, but it's not yet released. IMO we should release all > dependent packages at once. +1 for me > * lxpanel-0.5.4 wont build because configure breaks due to the > missing cpufreq plugin. Was the plugin supposed to be in the > tarball or was configure not updated before doing the release? > Was it tested at all? > imho they wasn't tested, as i replied before building it i found the same troubles i got with pcmanfm 0.5.2, it's just simply NOT built before release, the ca.po file once again miss "\n" > To summarize the above: We need a better quality assurance. Packages > must be tested before they get released. > > Regards, > Christoph > again i fully agree - -- - ------------------------------------------ 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/ iEYEARECAAYFAksipkYACgkQyCZT87TFPuhlvwCdHl8DL37jpAVDU2x6f23yfokG GkYAoJFzZa0zdBzWRw8qO+kJNhvclssx =kyIG -----END PGP SIGNATURE----- |
From: Jürgen H. <ju...@ho...> - 2010-01-18 22:40:51
|
2009/12/11 Andrea Florio <an...@op...> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Il 11/12/2009 20:33, Christoph Wickert ha scritto: > > I am very concerned about the recent LXDE updates: > > > > * After updating to lxsession-0.4.1, lxde-common-0.5.0 and > > lxappearance 0.3.0, I can no longer log into LXDE. Instead I get > > back to the login screen after a second. It doesn't work with a > > new user ether, so it's not related to my configuration. Any > > ideas how to debug this? > > i fixed it changing startlxde script > > > # Start the LXDE session > - -exec @prefix@/bin/lxsession -s LXDE > +exec @prefix@/bin/lxsession -s LXDE -e LXDE > > The lxde-common-0.5.0 dist tarball does not match the source from SVN commited as 0.5.0 release: [juergen@bitzer lxde-common]$ git log --grep=0.5.0 --oneline aa8b0fd Release lxde-common 0.5.0. Remove icon theme from it. [juergen@bitzer lxde-common]$ git checkout aa8b0fd ... HEAD is now at aa8b0fd... Release lxde-common 0.5.0. Remove icon theme from it. [juergen@bitzer lxde-common]$ tar xf ${ARCH_DISTDIR}/lxde-common-0.5.0.tar.gz -O lxde-common-0.5.0/startlxde.in|diff -u - startlxde.in --- - 2010-01-18 23:02:45.344199353 +0100 +++ startlxde.in 2010-01-18 23:01:56.000000000 +0100 @@ -25,4 +25,4 @@ export SAL_USE_VCLPLUGIN=gtk # Start the LXDE session -exec @prefix@/bin/lxsession -s LXDE +exec @prefix@/bin/lxsession -s LXDE -e LXDE @PCMan : The build of the dist tarball went wrong? We should prepare a new dist tarball. Jürgen |
From: Julien L. <gi...@ub...> - 2009-12-11 22:01:16
|
Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : > * lxpanel-0.5.4 wont build because configure breaks due to the > missing cpufreq plugin. Was the plugin supposed to be in the > tarball or was configure not updated before doing the release? > Was it tested at all? One test that can be made is the "make dist check". Fixing all errors is painful, but that prevent most of problems for the tarball side. Also, it's not too late to do a 0.5.4.1 release with the fixes. Mistakes happens :) Regards, Julien Lavergne |
From: PCMan <pcm...@gm...> - 2009-12-12 01:01:31
|
OK, Sorry for the recent degradation in quality assurance. I'm just too busy recently. After working for more than 12 hours a day in the hospital, I'm quite exhausted and don't have much time to do all the hacking and testing. Can we set up a QA team to handle the release management? I mean, when some new features are completed, developers send message in the mailing list. Then, the QA team do the testing and fix build issues. If things are OK, they release the tarballs. Besides, when translation coordinator find most translations are completed, he can call the QA team to check package integrity. If no problems are found, new release can be made by QA team for translation updates. So, for me, I only push things I developed into svn continuously, and I don't make release myself. The QA people just do QA, and do the release management. Is this model possible? On Sat, Dec 12, 2009 at 6:00 AM, Julien Lavergne <gi...@ub...> wrote: > Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : >> * lxpanel-0.5.4 wont build because configure breaks due to the >> missing cpufreq plugin. Was the plugin supposed to be in the >> tarball or was configure not updated before doing the release? >> Was it tested at all? > One test that can be made is the "make dist check". Fixing all errors is > painful, but that prevent most of problems for the tarball side. Also, > it's not too late to do a 0.5.4.1 release with the fixes. Mistakes > happens :) > > Regards, > Julien Lavergne > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > |
From: Mario B. <mb...@ma...> - 2009-12-12 17:46:15
|
Hi, yes, I think this is a good idea. Best would be to have one or two main QA Managers, I believe. Those persons can change according to needs and resources, but if we have QA manager we have people who we can refer to. Secondly, I would like to start a QA testing team. I will prepare this in the coming days. We can use the translation team set up as an example. Do you agree with this? If yes, who has resources to become a QA Manager? Ciao Mario On Sat, Dec 12, 2009 at 9:01 AM, PCMan <pcm...@gm...> wrote: > OK, > Sorry for the recent degradation in quality assurance. > I'm just too busy recently. > After working for more than 12 hours a day in the hospital, I'm quite > exhausted and don't have much time to do all the hacking and testing. > Can we set up a QA team to handle the release management? > I mean, when some new features are completed, developers send message > in the mailing list. > Then, the QA team do the testing and fix build issues. If things are > OK, they release the tarballs. > Besides, when translation coordinator find most translations are > completed, he can call the QA team to check package integrity. > If no problems are found, new release can be made by QA team for > translation updates. > > So, for me, I only push things I developed into svn continuously, and > I don't make release myself. > The QA people just do QA, and do the release management. > > Is this model possible? > > On Sat, Dec 12, 2009 at 6:00 AM, Julien Lavergne <gi...@ub...> wrote: >> Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : >>> * lxpanel-0.5.4 wont build because configure breaks due to the >>> missing cpufreq plugin. Was the plugin supposed to be in the >>> tarball or was configure not updated before doing the release? >>> Was it tested at all? >> One test that can be made is the "make dist check". Fixing all errors is >> painful, but that prevent most of problems for the tarball side. Also, >> it's not too late to do a 0.5.4.1 release with the fixes. Mistakes >> happens :) >> >> Regards, >> Julien Lavergne >> |
From: C D. R. <c.d...@gm...> - 2009-12-13 23:42:22
|
Mario Behling wrote: > Hi, > > yes, I think this is a good idea. Best would be to have one or two > main QA Managers, I believe. Those persons can change according to > needs and resources, but if we have QA manager we have people who we > can refer to. > > Secondly, I would like to start a QA testing team. I will prepare this > in the coming days. We can use the translation team set up as an > example. > > Do you agree with this? If yes, who has resources to become a QA Manager? > > Ciao Mario > > > It's a good idea. Regards, CDRigby > On Sat, Dec 12, 2009 at 9:01 AM, PCMan <pcm...@gm...> wrote: > >> OK, >> Sorry for the recent degradation in quality assurance. >> I'm just too busy recently. >> After working for more than 12 hours a day in the hospital, I'm quite >> exhausted and don't have much time to do all the hacking and testing. >> Can we set up a QA team to handle the release management? >> I mean, when some new features are completed, developers send message >> in the mailing list. >> Then, the QA team do the testing and fix build issues. If things are >> OK, they release the tarballs. >> Besides, when translation coordinator find most translations are >> completed, he can call the QA team to check package integrity. >> If no problems are found, new release can be made by QA team for >> translation updates. >> >> So, for me, I only push things I developed into svn continuously, and >> I don't make release myself. >> The QA people just do QA, and do the release management. >> >> Is this model possible? >> >> On Sat, Dec 12, 2009 at 6:00 AM, Julien Lavergne <gi...@ub...> wrote: >> >>> Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : >>> >>>> * lxpanel-0.5.4 wont build because configure breaks due to the >>>> missing cpufreq plugin. Was the plugin supposed to be in the >>>> tarball or was configure not updated before doing the release? >>>> Was it tested at all? >>>> >>> One test that can be made is the "make dist check". Fixing all errors is >>> painful, but that prevent most of problems for the tarball side. Also, >>> it's not too late to do a 0.5.4.1 release with the fixes. Mistakes >>> happens :) >>> >>> Regards, >>> Julien Lavergne >>> >>> > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > |
From: PCMan <pcm...@gm...> - 2009-12-12 18:31:37
|
People who I think can be members of QA team: AndrewLee: Debian developer Christoph Wickert: Fedora developer Julien Lavergne: Ubuntu developer and also recently we got a new friend from openSuSE. So, if those people can make a QA team, we can make sure that new features build and work in those major distros. These are my idea: After the team is set up, developers only push code into svn repo and call for testing on ML. It's the QA team who need to test those new features. If things all work, the QA team can decide when to make a new tarball release at any time if they see fit. Before making new release, the QA team fixes grammar errors and typos in English strings in source code. Then, the QA team call for translation, and the translation coordinator work on getting most translation done. Then, the QA team release tarballs for stable release and announce on ML, forum, and blog. This workflow can ensure working stable releases with nice translations included and fix currently broken release model. Also, this can greatly decrease the workload of developers and let them concentrate on new features and bug fixes. Any comment? On Sun, Dec 13, 2009 at 1:45 AM, Mario Behling <mb...@ma...> wrote: > Hi, > > yes, I think this is a good idea. Best would be to have one or two > main QA Managers, I believe. Those persons can change according to > needs and resources, but if we have QA manager we have people who we > can refer to. > > Secondly, I would like to start a QA testing team. I will prepare this > in the coming days. We can use the translation team set up as an > example. > > Do you agree with this? If yes, who has resources to become a QA Manager? > > Ciao Mario > > > On Sat, Dec 12, 2009 at 9:01 AM, PCMan <pcm...@gm...> wrote: >> OK, >> Sorry for the recent degradation in quality assurance. >> I'm just too busy recently. >> After working for more than 12 hours a day in the hospital, I'm quite >> exhausted and don't have much time to do all the hacking and testing. >> Can we set up a QA team to handle the release management? >> I mean, when some new features are completed, developers send message >> in the mailing list. >> Then, the QA team do the testing and fix build issues. If things are >> OK, they release the tarballs. >> Besides, when translation coordinator find most translations are >> completed, he can call the QA team to check package integrity. >> If no problems are found, new release can be made by QA team for >> translation updates. >> >> So, for me, I only push things I developed into svn continuously, and >> I don't make release myself. >> The QA people just do QA, and do the release management. >> >> Is this model possible? >> >> On Sat, Dec 12, 2009 at 6:00 AM, Julien Lavergne <gi...@ub...> wrote: >>> Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : >>>> * lxpanel-0.5.4 wont build because configure breaks due to the >>>> missing cpufreq plugin. Was the plugin supposed to be in the >>>> tarball or was configure not updated before doing the release? >>>> Was it tested at all? >>> One test that can be made is the "make dist check". Fixing all errors is >>> painful, but that prevent most of problems for the tarball side. Also, >>> it's not too late to do a 0.5.4.1 release with the fixes. Mistakes >>> happens :) >>> >>> Regards, >>> Julien Lavergne >>> > |
From: PCMan <pcm...@gm...> - 2009-12-12 18:36:42
|
IMHO, a separate release team is not needed. For package mantainers, they both need to test the latest tarballs and package them. So, the most efficient way should be making those people the QA team + release manager. In this way, when a new stable release of component X is made, all major distros get working updated packages immediately at the same time since the package maintainers are also the people who release the tarballs. On Sun, Dec 13, 2009 at 2:31 AM, PCMan <pcm...@gm...> wrote: > People who I think can be members of QA team: > AndrewLee: Debian developer > Christoph Wickert: Fedora developer > Julien Lavergne: Ubuntu developer > and also recently we got a new friend from openSuSE. > > So, if those people can make a QA team, we can make sure that new > features build and work in those major distros. > > These are my idea: > > After the team is set up, developers only push code into svn repo and > call for testing on ML. > It's the QA team who need to test those new features. > If things all work, the QA team can decide when to make a new tarball > release at any time if they see fit. > Before making new release, the QA team fixes grammar errors and typos > in English strings in source code. > Then, the QA team call for translation, and the translation > coordinator work on getting most translation done. > Then, the QA team release tarballs for stable release and announce on > ML, forum, and blog. > > This workflow can ensure working stable releases with nice > translations included and fix currently broken release model. > Also, this can greatly decrease the workload of developers and let > them concentrate on new features and bug fixes. > > Any comment? > > On Sun, Dec 13, 2009 at 1:45 AM, Mario Behling <mb...@ma...> wrote: >> Hi, >> >> yes, I think this is a good idea. Best would be to have one or two >> main QA Managers, I believe. Those persons can change according to >> needs and resources, but if we have QA manager we have people who we >> can refer to. >> >> Secondly, I would like to start a QA testing team. I will prepare this >> in the coming days. We can use the translation team set up as an >> example. >> >> Do you agree with this? If yes, who has resources to become a QA Manager? >> >> Ciao Mario >> >> >> On Sat, Dec 12, 2009 at 9:01 AM, PCMan <pcm...@gm...> wrote: >>> OK, >>> Sorry for the recent degradation in quality assurance. >>> I'm just too busy recently. >>> After working for more than 12 hours a day in the hospital, I'm quite >>> exhausted and don't have much time to do all the hacking and testing. >>> Can we set up a QA team to handle the release management? >>> I mean, when some new features are completed, developers send message >>> in the mailing list. >>> Then, the QA team do the testing and fix build issues. If things are >>> OK, they release the tarballs. >>> Besides, when translation coordinator find most translations are >>> completed, he can call the QA team to check package integrity. >>> If no problems are found, new release can be made by QA team for >>> translation updates. >>> >>> So, for me, I only push things I developed into svn continuously, and >>> I don't make release myself. >>> The QA people just do QA, and do the release management. >>> >>> Is this model possible? >>> >>> On Sat, Dec 12, 2009 at 6:00 AM, Julien Lavergne <gi...@ub...> wrote: >>>> Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : >>>>> * lxpanel-0.5.4 wont build because configure breaks due to the >>>>> missing cpufreq plugin. Was the plugin supposed to be in the >>>>> tarball or was configure not updated before doing the release? >>>>> Was it tested at all? >>>> One test that can be made is the "make dist check". Fixing all errors is >>>> painful, but that prevent most of problems for the tarball side. Also, >>>> it's not too late to do a 0.5.4.1 release with the fixes. Mistakes >>>> happens :) >>>> >>>> Regards, >>>> Julien Lavergne >>>> >> > |
From: Jürgen H. <ju...@ar...> - 2010-01-18 22:42:05
|
2009/12/11 Andrea Florio <an...@op...> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Il 11/12/2009 20:33, Christoph Wickert ha scritto: > > I am very concerned about the recent LXDE updates: > > > > * After updating to lxsession-0.4.1, lxde-common-0.5.0 and > > lxappearance 0.3.0, I can no longer log into LXDE. Instead I get > > back to the login screen after a second. It doesn't work with a > > new user ether, so it's not related to my configuration. Any > > ideas how to debug this? > > i fixed it changing startlxde script > > > # Start the LXDE session > - -exec @prefix@/bin/lxsession -s LXDE > +exec @prefix@/bin/lxsession -s LXDE -e LXDE > > The lxde-common-0.5.0 dist tarball does not match the source from SVN commited as 0.5.0 release: [juergen@bitzer lxde-common]$ git log --grep=0.5.0 --oneline aa8b0fd Release lxde-common 0.5.0. Remove icon theme from it. [juergen@bitzer lxde-common]$ git checkout aa8b0fd ... HEAD is now at aa8b0fd... Release lxde-common 0.5.0. Remove icon theme from it. [juergen@bitzer lxde-common]$ tar xf ${ARCH_DISTDIR}/lxde-common-0.5.0.tar.gz -O lxde-common-0.5.0/startlxde.in|diff -u - startlxde.in --- - 2010-01-18 23:02:45.344199353 +0100 +++ startlxde.in 2010-01-18 23:01:56.000000000 +0100 @@ -25,4 +25,4 @@ export SAL_USE_VCLPLUGIN=gtk # Start the LXDE session -exec @prefix@/bin/lxsession -s LXDE +exec @prefix@/bin/lxsession -s LXDE -e LXDE @PCMan : The build of the dist tarball went wrong? We should prepare a new dist tarball. Jürgen |
From: PCMan <pcm...@gm...> - 2010-01-19 04:52:33
|
Thank you for the debugging and sorry for the poor quality of tarballs. This kind of errors won't happen in the future. Feel free to fix it and release new tarballs if the problems are confirmed. Later, there will be one incompatible change in lxde-common. The command line: "pcmanfm -d" will be changed to "pcmanfm --desktop" after the first public release of new pcmanfm/libfm is available. Yes, this change implies that the new release of next generation pcmanfm/libfm is coming. So, please help the testing/debugging, or even coding. Cheers! On Tue, Jan 19, 2010 at 6:15 AM, Jürgen Hötzel <ju...@ar...> wrote: > 2009/12/11 Andrea Florio <an...@op...> >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Il 11/12/2009 20:33, Christoph Wickert ha scritto: >> > I am very concerned about the recent LXDE updates: >> > >> > * After updating to lxsession-0.4.1, lxde-common-0.5.0 and >> > lxappearance 0.3.0, I can no longer log into LXDE. Instead I get >> > back to the login screen after a second. It doesn't work with a >> > new user ether, so it's not related to my configuration. Any >> > ideas how to debug this? >> >> i fixed it changing startlxde script >> >> >> # Start the LXDE session >> - -exec @prefix@/bin/lxsession -s LXDE >> +exec @prefix@/bin/lxsession -s LXDE -e LXDE >> > > The lxde-common-0.5.0 dist tarball does not match the source from SVN > commited as 0.5.0 release: > [juergen@bitzer lxde-common]$ git log --grep=0.5.0 --oneline > aa8b0fd Release lxde-common 0.5.0. Remove icon theme from it. > [juergen@bitzer lxde-common]$ git checkout aa8b0fd > ... > HEAD is now at aa8b0fd... Release lxde-common 0.5.0. Remove icon theme from > it. > [juergen@bitzer lxde-common]$ tar xf > ${ARCH_DISTDIR}/lxde-common-0.5.0.tar.gz -O > lxde-common-0.5.0/startlxde.in|diff -u - startlxde.in > --- - 2010-01-18 23:02:45.344199353 +0100 > +++ startlxde.in 2010-01-18 23:01:56.000000000 +0100 > @@ -25,4 +25,4 @@ > export SAL_USE_VCLPLUGIN=gtk > > # Start the LXDE session > -exec @prefix@/bin/lxsession -s LXDE > +exec @prefix@/bin/lxsession -s LXDE -e LXDE > > @PCMan : The build of the dist tarball went wrong? > We should prepare a new dist tarball. > Jürgen > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > > |