Re: [E-devel] Nightly builds - Was: Is this a community project?
On Fri, 27 Jul 2007 20:07:58 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Fri, 27 Jul 2007 10:22:20 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > Another option would be for whoever has control of the mailing list > > to simply add [EMAIL PROTECTED] Set it up so that they > > can post, but don't receive email. > > we have this for cvs-commits. in fact you should possibly send to > cvs-commits? we can set up a new list - but i am not sure we need to > really? enlightenment-cvs is a good place to put it, as this relates to the CVS commits, and people interested in that subscribe to that list. > > The next hoop is that sf.net will then check to see if a user called > > onefang is allowed to send email from enlightenment.org. Once > > again, easydns.com may be able to help us jump through this hoop > > with their email forwarding service. > > > > In my testing I've never gotten past this hoop, so I don't know what > > other hoops there may be. Typically there is no response from these > > hoops, nothing ever gets bounced, and nothing is ever left in log > > files we can check. So the hoop jumping has to be done blind. > > > > Actually running our own SMTP server on e2.enlightenment.org would > > help to solve these problems, but I doubt we want to do that. > > cvs-commits list mail gets through - kainx may be able to help as he > manages the dev server that sends the mail that goes to cvs-commits. > see the commit.pl to see how it sends the mail too (in CVSROOT) commit.pl uses a method that was closer to my original efforts than what the nightly build has drifted to. I've changed the nightly build method back and it works as well as it used to. The resulting email still has to navigate the treacherous sf.net waters. Would not surprise me to find that KainX has a proper email setup on that server, instead of MX records that point to his DNS provider like e2 has. We should do the same for e2. I note that KainX has an e2 account and already has sudo. Care to help out KainX? For now I've got an evil hack setup. I still send the emails to myself, the difference is that instead of manually resending it, my email client does that automatically. Obviously only a temp solution, but at least it's fully automated. B-) > > Speaking of cron jobs, since it needs to run as root anyway if we > > are to use ionice, I propose sticking a suitable named script > > into /etc/cron.daily. It should run last, after all the useful > > system cron jobs have finished. Calling it zz_nightly_build should > > do the trick. > > > > What do the people that actually maintain the server think? > > you can run the build script - sleep for 10 seconds then sudo ionice > the PID How is that any better than what I originally proposed - sudo ionice -c3 su onefang -c NIGHTLY_BUILD sudo is still involved, you just complicated things with PID tracking and made a ten second window where the script can grind the machine to a halt. /etc/cron.daily/zz_nightly_build has the advantage of being easy to track down by later sys admins. It runs nightly, it needs root privs to start with even though it drops those very quickly, and it's the standard place for such things. > we probably should set up a user called ebuild that runs this stuff > actually - not run as root or as onefang :) Once we have the basics running, then we can sweat the details. B-) signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Fri, 27 Jul 2007 15:32:31 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Fri, 27 Jul 2007 15:21:47 +1000 David Seikel <[EMAIL PROTECTED]> > wrote: > > > Guess I could install it as a root cron job, that leaves out the > > initial sudo command at least. > > Speaking of cron jobs, since it needs to run as root anyway if we are > to use ionice, I propose sticking a suitable named script > into /etc/cron.daily. It should run last, after all the useful system > cron jobs have finished. Calling it zz_nightly_build should do the > trick. > > What do the people that actually maintain the server think? you can run the build script - sleep for 10 seconds then sudo ionice the PID we probably should set up a user called ebuild that runs this stuff actually - not run as root or as onefang :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Fri, 27 Jul 2007 10:22:20 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > The one big remaining problem is getting the summary sent to the > mailing list. sf.net is fussy about this, it's not good enough to just > use /usr/bin/mail, sf.net makes you jump through hoops. This is why I > have been cutting and pasting, or sending to myself then forwarding. > > The emails are being sent from the script running on > e2.enlightenment.org as user onefang using /usr/bin/mail, so it ends up > with a from address of [EMAIL PROTECTED] Note, not > @e2.enlightenment.org. > > The first obvious hoop is that the sender has to be on the mailing > list. To subscribe to a mailing list I need to receive the > confirmation email, and respond to it or click on the supplied URL. So > I would need to get the [EMAIL PROTECTED] emails. > enlightenment.org's MX records point to easydns.com, which is our DNS > hosting provider. Reading through their website, they could provide > email forwarding for us. Currently, emails to > [EMAIL PROTECTED] just seem to disappear into the ether. it didn't even make it as far as the list moderation info - it got filtered before that. > Another option would be for whoever has control of the mailing list to > simply add [EMAIL PROTECTED] Set it up so that they can post, > but don't receive email. we have this for cvs-commits. in fact you should possibly send to cvs-commits? we can set up a new list - but i am not sure we need to really? > The next hoop is that sf.net will then check to see if a user called > onefang is allowed to send email from enlightenment.org. Once again, > easydns.com may be able to help us jump through this hoop with their > email forwarding service. > > In my testing I've never gotten past this hoop, so I don't know what > other hoops there may be. Typically there is no response from these > hoops, nothing ever gets bounced, and nothing is ever left in log files > we can check. So the hoop jumping has to be done blind. > > Actually running our own SMTP server on e2.enlightenment.org would help > to solve these problems, but I doubt we want to do that. cvs-commits list mail gets through - kainx may be able to help as he manages the dev server that sends the mail that goes to cvs-commits. see the commit.pl to see how it sends the mail too (in CVSROOT) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Wed, 25 Jul 2007 09:21:24 +1000 David Seikel <[EMAIL PROTECTED]> wrote: > On Wed, 25 Jul 2007 07:44:36 +0900 Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: > > > On Wed, 25 Jul 2007 08:03:49 +1000 David Seikel <[EMAIL PROTECTED]> > > babbled: > > > > > On Sun, 22 Jul 2007 12:11:07 +0900 Carsten Haitzler (The > > > Rasterman) <[EMAIL PROTECTED]> wrote: > > > > > > > p.s. - might also want to try ionice as well as nice :) > > > > > > I had not actually heard of that, and its not installed on my > > > Ubuntu box. Not even available through a standard Ubuntu repo. > > > Is it in Debian? More importantly, is it already installed on > > > e2? Looks like a good idea though, would have to check for it's > > > existence before trying to use it though. > > > > apt-get install schedutils :) it's already installed on e2 > > Hmm, Ubuntu's universe repo. The description doesn't mention ionice, > that's why I couldn't find it by searching before. Installed here > now, so I can play with it at my leisure. Strange, ionice requires root privs, even when using -c3 to mean "A program running with idle io priority will only get disk time when no other program has asked for disk io for a defined grace period. The impact of idle io processes on normal system activity should be zero.". Compared to nice(1), which does not need root privs if just lowering the priority. Got to grab root privs for long enough to lower IO priority, then drop them again to actually do stuff as an ordinary user. sudo ionice -c3 su onefang -c NIGHTLY_BUILD Yuck. Guess I could install it as a root cron job, that leaves out the initial sudo command at least. signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
David Seikel wrote: > The one big remaining problem is getting the summary sent to the > mailing list. sf.net is fussy about this, it's not good enough to just > use /usr/bin/mail, sf.net makes you jump through hoops. This is why I > have been cutting and pasting, or sending to myself then forwarding. > > The emails are being sent from the script running on > e2.enlightenment.org as user onefang using /usr/bin/mail, so it ends up > with a from address of [EMAIL PROTECTED] Note, not > @e2.enlightenment.org. That could be changed easily, just set myorigin to something else (even something completely different like gmail.com) Just make sure the domain chosen doesn't have spf entries that preclude e2 from sending mail on its behalf (that means gmail.com is out of the question) -- Cheers, Morten :wq - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Fri, 27 Jul 2007 15:21:47 +1000 David Seikel <[EMAIL PROTECTED]> wrote: > Guess I could install it as a root cron job, that leaves out the > initial sudo command at least. Speaking of cron jobs, since it needs to run as root anyway if we are to use ionice, I propose sticking a suitable named script into /etc/cron.daily. It should run last, after all the useful system cron jobs have finished. Calling it zz_nightly_build should do the trick. What do the people that actually maintain the server think? signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Thu, 26 Jul 2007 21:47:14 -0500 Ravenlock <[EMAIL PROTECTED]> wrote: > Would something like ssmtp help here? Changing SMTP software isn't going to help when the problem is not in the SMTP software side of things. signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Fri, 27 Jul 2007 03:39:41 +0200 Dave <[EMAIL PROTECTED]> wrote: > David Seikel ha scritto: > > The one big remaining problem is getting the summary sent to the > > mailing list. sf.net is fussy about this, it's not good enough to > > just use /usr/bin/mail, sf.net makes you jump through hoops. This > > is why I have been cutting and pasting, or sending to myself then > > forwarding. > > > > The emails are being sent from the script running on > > e2.enlightenment.org as user onefang using /usr/bin/mail, so it > > ends up with a from address of [EMAIL PROTECTED] Note, not > > @e2.enlightenment.org. > > > can't you simply specify a different 'From' header in the generated > mail? This works on my server but maybe depend on the smtp-server > configuration. Tried that, it's the sf.net anti spam hoops that are the issue. Specifying a different From header is more likely to get sf.net to identify it as spam. signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On 07/26/2007 19:22, David Seikel wrote: > The one big remaining problem is getting the summary sent to the > mailing list. sf.net is fussy about this, it's not good enough to just > use /usr/bin/mail, sf.net makes you jump through hoops. This is why I > have been cutting and pasting, or sending to myself then forwarding. > > The emails are being sent from the script running on > e2.enlightenment.org as user onefang using /usr/bin/mail, so it ends up > with a from address of [EMAIL PROTECTED] Note, not > @e2.enlightenment.org. > > The first obvious hoop is that the sender has to be on the mailing > list. To subscribe to a mailing list I need to receive the > confirmation email, and respond to it or click on the supplied URL. So > I would need to get the [EMAIL PROTECTED] emails. > enlightenment.org's MX records point to easydns.com, which is our DNS > hosting provider. Reading through their website, they could provide > email forwarding for us. Currently, emails to > [EMAIL PROTECTED] just seem to disappear into the ether. > > Another option would be for whoever has control of the mailing list to > simply add [EMAIL PROTECTED] Set it up so that they can post, > but don't receive email. > > The next hoop is that sf.net will then check to see if a user called > onefang is allowed to send email from enlightenment.org. Once again, > easydns.com may be able to help us jump through this hoop with their > email forwarding service. > > In my testing I've never gotten past this hoop, so I don't know what > other hoops there may be. Typically there is no response from these > hoops, nothing ever gets bounced, and nothing is ever left in log files > we can check. So the hoop jumping has to be done blind. > > Actually running our own SMTP server on e2.enlightenment.org would help > to solve these problems, but I doubt we want to do that. Would something like ssmtp help here? > > Thoughts? > > > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Regards, Ravenlock signature.asc Description: OpenPGP digital signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
David Seikel ha scritto: > The one big remaining problem is getting the summary sent to the > mailing list. sf.net is fussy about this, it's not good enough to just > use /usr/bin/mail, sf.net makes you jump through hoops. This is why I > have been cutting and pasting, or sending to myself then forwarding. > > The emails are being sent from the script running on > e2.enlightenment.org as user onefang using /usr/bin/mail, so it ends up > with a from address of [EMAIL PROTECTED] Note, not > @e2.enlightenment.org. > can't you simply specify a different 'From' header in the generated mail? This works on my server but maybe depend on the smtp-server configuration. > The first obvious hoop is that the sender has to be on the mailing > list. To subscribe to a mailing list I need to receive the > confirmation email, and respond to it or click on the supplied URL. So > I would need to get the [EMAIL PROTECTED] emails. > enlightenment.org's MX records point to easydns.com, which is our DNS > hosting provider. Reading through their website, they could provide > email forwarding for us. Currently, emails to > [EMAIL PROTECTED] just seem to disappear into the ether. > > Another option would be for whoever has control of the mailing list to > simply add [EMAIL PROTECTED] Set it up so that they can post, > but don't receive email. > > The next hoop is that sf.net will then check to see if a user called > onefang is allowed to send email from enlightenment.org. Once again, > easydns.com may be able to help us jump through this hoop with their > email forwarding service. > > In my testing I've never gotten past this hoop, so I don't know what > other hoops there may be. Typically there is no response from these > hoops, nothing ever gets bounced, and nothing is ever left in log files > we can check. So the hoop jumping has to be done blind. > > Actually running our own SMTP server on e2.enlightenment.org would help > to solve these problems, but I doubt we want to do that. > > Thoughts? > > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
The one big remaining problem is getting the summary sent to the mailing list. sf.net is fussy about this, it's not good enough to just use /usr/bin/mail, sf.net makes you jump through hoops. This is why I have been cutting and pasting, or sending to myself then forwarding. The emails are being sent from the script running on e2.enlightenment.org as user onefang using /usr/bin/mail, so it ends up with a from address of [EMAIL PROTECTED] Note, not @e2.enlightenment.org. The first obvious hoop is that the sender has to be on the mailing list. To subscribe to a mailing list I need to receive the confirmation email, and respond to it or click on the supplied URL. So I would need to get the [EMAIL PROTECTED] emails. enlightenment.org's MX records point to easydns.com, which is our DNS hosting provider. Reading through their website, they could provide email forwarding for us. Currently, emails to [EMAIL PROTECTED] just seem to disappear into the ether. Another option would be for whoever has control of the mailing list to simply add [EMAIL PROTECTED] Set it up so that they can post, but don't receive email. The next hoop is that sf.net will then check to see if a user called onefang is allowed to send email from enlightenment.org. Once again, easydns.com may be able to help us jump through this hoop with their email forwarding service. In my testing I've never gotten past this hoop, so I don't know what other hoops there may be. Typically there is no response from these hoops, nothing ever gets bounced, and nothing is ever left in log files we can check. So the hoop jumping has to be done blind. Actually running our own SMTP server on e2.enlightenment.org would help to solve these problems, but I doubt we want to do that. Thoughts? signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Wed, 25 Jul 2007 07:44:36 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Wed, 25 Jul 2007 08:03:49 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > On Sun, 22 Jul 2007 12:11:07 +0900 Carsten Haitzler (The Rasterman) > > <[EMAIL PROTECTED]> wrote: > > > > > p.s. - might also want to try ionice as well as nice :) > > > > I had not actually heard of that, and its not installed on my Ubuntu > > box. Not even available through a standard Ubuntu repo. Is it in > > Debian? More importantly, is it already installed on e2? Looks > > like a good idea though, would have to check for it's existence > > before trying to use it though. > > apt-get install schedutils :) it's already installed on e2 Hmm, Ubuntu's universe repo. The description doesn't mention ionice, that's why I couldn't find it by searching before. Installed here now, so I can play with it at my leisure. signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Wed, 25 Jul 2007 08:03:49 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Sun, 22 Jul 2007 12:11:07 +0900 Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: > > > On Sat, 21 Jul 2007 22:24:50 +1000 David Seikel <[EMAIL PROTECTED]> > > babbled: > > > > > On Sat, 21 Jul 2007 18:04:35 +0900 Carsten Haitzler (The Rasterman) > > > <[EMAIL PROTECTED]> wrote: > > > > > > > On Sat, 21 Jul 2007 17:22:39 +1000 David Seikel > > > > <[EMAIL PROTECTED]> babbled: > > > > > > > > > On Sat, 21 Jul 2007 17:07:57 +1000 David Seikel > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > I'll run the script from e2 right now and see how it goes. > > > > > > > > > > Who do I talk to about getting stuff installed on e2? Gonna > > > > > need a few things, starting with autoconf, automake, ... you > > > > > get the idea. mc would be nice as well. B-) > > > > > > > > log out and in - use sudo. :) > > > > > > It's basically working on e2 now. > > > > > > Compiles as an ordinary user, no sudo required. Running at nice > > > 19, so low impact on the rest of the box. Installing to my home > > > directory. Most of the dependencies are installed, still some > > > obscure ones left though. Most of the packages are building fine. > > > Most of the failures are missing dependencies, or packages that > > > could do with some pkg-config lovin'. > > > > > > No email out, not even to myself. Have to figure out where in the > > > web site to put the results. Once it is all sorted, then I'll hook > > > it up to cron. > > > > /var/www has all the websites - you might want to put it in > > "download" for now. > > Will do. > > > > Getting tired, I'll sort the rest out tomorrow. > > Actually got sick, project put on hold until I recover. > > > p.s. - might also want to try ionice as well as nice :) > > I had not actually heard of that, and its not installed on my Ubuntu > box. Not even available through a standard Ubuntu repo. Is it in > Debian? More importantly, is it already installed on e2? Looks like a > good idea though, would have to check for it's existence before trying > to use it though. apt-get install schedutils :) it's already installed on e2 -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sun, 22 Jul 2007 12:11:07 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Sat, 21 Jul 2007 22:24:50 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > On Sat, 21 Jul 2007 18:04:35 +0900 Carsten Haitzler (The Rasterman) > > <[EMAIL PROTECTED]> wrote: > > > > > On Sat, 21 Jul 2007 17:22:39 +1000 David Seikel > > > <[EMAIL PROTECTED]> babbled: > > > > > > > On Sat, 21 Jul 2007 17:07:57 +1000 David Seikel > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > I'll run the script from e2 right now and see how it goes. > > > > > > > > Who do I talk to about getting stuff installed on e2? Gonna > > > > need a few things, starting with autoconf, automake, ... you > > > > get the idea. mc would be nice as well. B-) > > > > > > log out and in - use sudo. :) > > > > It's basically working on e2 now. > > > > Compiles as an ordinary user, no sudo required. Running at nice > > 19, so low impact on the rest of the box. Installing to my home > > directory. Most of the dependencies are installed, still some > > obscure ones left though. Most of the packages are building fine. > > Most of the failures are missing dependencies, or packages that > > could do with some pkg-config lovin'. > > > > No email out, not even to myself. Have to figure out where in the > > web site to put the results. Once it is all sorted, then I'll hook > > it up to cron. > > /var/www has all the websites - you might want to put it in > "download" for now. Will do. > > Getting tired, I'll sort the rest out tomorrow. Actually got sick, project put on hold until I recover. > p.s. - might also want to try ionice as well as nice :) I had not actually heard of that, and its not installed on my Ubuntu box. Not even available through a standard Ubuntu repo. Is it in Debian? More importantly, is it already installed on e2? Looks like a good idea though, would have to check for it's existence before trying to use it though. signature.asc Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 22:24:50 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Sat, 21 Jul 2007 18:04:35 +0900 Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: > > > On Sat, 21 Jul 2007 17:22:39 +1000 David Seikel <[EMAIL PROTECTED]> > > babbled: > > > > > On Sat, 21 Jul 2007 17:07:57 +1000 David Seikel <[EMAIL PROTECTED]> > > > wrote: > > > > > > > I'll run the script from e2 right now and see how it goes. > > > > > > Who do I talk to about getting stuff installed on e2? Gonna need a > > > few things, starting with autoconf, automake, ... you get the > > > idea. mc would be nice as well. B-) > > > > log out and in - use sudo. :) > > It's basically working on e2 now. > > Compiles as an ordinary user, no sudo required. Running at nice 19, so > low impact on the rest of the box. Installing to my home directory. > Most of the dependencies are installed, still some obscure ones left > though. Most of the packages are building fine. Most of the failures > are missing dependencies, or packages that could do with some > pkg-config lovin'. > > No email out, not even to myself. Have to figure out where in the web > site to put the results. Once it is all sorted, then I'll hook it up > to cron. /var/www has all the websites - you might want to put it in "download" for now. > Getting tired, I'll sort the rest out tomorrow. p.s. - might also want to try ionice as well as nice :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 18:04:35 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Sat, 21 Jul 2007 17:22:39 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > On Sat, 21 Jul 2007 17:07:57 +1000 David Seikel <[EMAIL PROTECTED]> > > wrote: > > > > > I'll run the script from e2 right now and see how it goes. > > > > Who do I talk to about getting stuff installed on e2? Gonna need a > > few things, starting with autoconf, automake, ... you get the > > idea. mc would be nice as well. B-) > > log out and in - use sudo. :) It's basically working on e2 now. Compiles as an ordinary user, no sudo required. Running at nice 19, so low impact on the rest of the box. Installing to my home directory. Most of the dependencies are installed, still some obscure ones left though. Most of the packages are building fine. Most of the failures are missing dependencies, or packages that could do with some pkg-config lovin'. No email out, not even to myself. Have to figure out where in the web site to put the results. Once it is all sorted, then I'll hook it up to cron. Getting tired, I'll sort the rest out tomorrow. signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 17:22:39 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Sat, 21 Jul 2007 17:07:57 +1000 David Seikel <[EMAIL PROTECTED]> > wrote: > > > I'll run the script from e2 right now and see how it goes. > > Who do I talk to about getting stuff installed on e2? Gonna need a few > things, starting with autoconf, automake, ... you get the idea. mc > would be nice as well. B-) log out and in - use sudo. :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 17:07:57 +1000 David Seikel <[EMAIL PROTECTED]> wrote: > I'll run the script from e2 right now and see how it goes. Who do I talk to about getting stuff installed on e2? Gonna need a few things, starting with autoconf, automake, ... you get the idea. mc would be nice as well. B-) signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 15:32:32 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Sat, 21 Jul 2007 13:33:51 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > access to set up a cron job? Being able to send email, and being > > able to convince sf.net that we are allowed to send email to the > > list are two separate things. > > :/ true - but its easier for e.org as its an official server - your > adsl link will be on an RBL somewhere as a dialup/user account ip > thus be blocked. I don't have an ADSL link, and I have a static IP. It's not RBL blocking that is the problem from here. It will be a problem for Random E. Developer though. I'll run the script from e2 right now and see how it goes. signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 13:33:51 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Sat, 21 Jul 2007 12:24:25 +0900 Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: > > > On Sat, 21 Jul 2007 12:43:39 +1000 David Seikel <[EMAIL PROTECTED]> > > babbled: > > > > > On Wed, 18 Jul 2007 12:30:53 +0900 Carsten Haitzler (The Rasterman) > > > <[EMAIL PROTECTED]> wrote: > > > > > > > can you... put the script in cvs somewhere? tough to talk about > > > > something we can't see. > > > > > > After much experimentation, we ended up with easy_e17.sh and a post > > > install script. easy_e17.sh is available from morlenxus' server as > > > I've mentioned before. The post install script relies on the > > > current svn version, but that will be the next release soon enough. > > > > > > I'll put the post install script into cvs somewhere. The real > > > question is - where? Create a new project in > > > e17/apps/nightly_build? e17/test perhaps? > > > > > > The major problem at the moment is that sf.net is really fussy about > > > emails you send to it. Seems like a typical workstation with a > > > dynamic IP and default install will not be able to use sendmail > > > > > real mail server to do it for you. So some config of local mail > > > systems may be needed if we want volunteers to use this to cover > > > various distros etc. > > > > > > Once we are happy with the output generated and where it goes we can > > > worry about OS / distro / CPU coverage details. > > > > tus why you should not worry and just run this on > > e2.enlightenment.org - it already can send email as part of bugzilla > > requirements. :) > > Yes, that is planned. Do I have a shell account on that and enough yes :) > access to set up a cron job? Being able to send email, and being able > to convince sf.net that we are allowed to send email to the list are > two separate things. :/ true - but its easier for e.org as its an official server - your adsl link will be on an RBL somewhere as a dialup/user account ip thus be blocked. > Does e2.enlightenment.org have enough grunt to run a half dozen qemu > sessions for nightly testing on a few distro/CPU combinations? If not > this is why volunteers may be needed later. Like I said, nothing to > worry about now. it's a dual cpu dual core xeon @ 3ghz. 2gb ram. it's got enough. we also have e1.enlightenment.org too - same specs. we can split builds across them. e2 runs all our www stuff - e1 is anon cvs right now. also just run the build with really low priority - niced down so www or later anoncvs don't get too impacted. builds can just roll along in the background - the time they take is not important. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 12:24:25 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Sat, 21 Jul 2007 12:43:39 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > On Wed, 18 Jul 2007 12:30:53 +0900 Carsten Haitzler (The Rasterman) > > <[EMAIL PROTECTED]> wrote: > > > > > can you... put the script in cvs somewhere? tough to talk about > > > something we can't see. > > > > After much experimentation, we ended up with easy_e17.sh and a post > > install script. easy_e17.sh is available from morlenxus' server as > > I've mentioned before. The post install script relies on the > > current svn version, but that will be the next release soon enough. > > > > I'll put the post install script into cvs somewhere. The real > > question is - where? Create a new project in > > e17/apps/nightly_build? e17/test perhaps? > > > > The major problem at the moment is that sf.net is really fussy about > > emails you send to it. Seems like a typical workstation with a > > dynamic IP and default install will not be able to use sendmail > > > real mail server to do it for you. So some config of local mail > > systems may be needed if we want volunteers to use this to cover > > various distros etc. > > > > Once we are happy with the output generated and where it goes we can > > worry about OS / distro / CPU coverage details. > > tus why you should not worry and just run this on > e2.enlightenment.org - it already can send email as part of bugzilla > requirements. :) Yes, that is planned. Do I have a shell account on that and enough access to set up a cron job? Being able to send email, and being able to convince sf.net that we are allowed to send email to the list are two separate things. Does e2.enlightenment.org have enough grunt to run a half dozen qemu sessions for nightly testing on a few distro/CPU combinations? If not this is why volunteers may be needed later. Like I said, nothing to worry about now. signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Sat, 21 Jul 2007 12:43:39 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Wed, 18 Jul 2007 12:30:53 +0900 Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: > > > On Tue, 17 Jul 2007 10:14:58 +1000 David Seikel <[EMAIL PROTECTED]> > > babbled: > > > > > Attached is the result of a first cut at a nightly build script. > > > Early days, baby steps, don't pick over the little details. We can > > > start with the basics and work up to more features later. > > > > > > For now I can run this on my boxen while it gets developed further. > > > Move it to the E servers and volunteer boxen when it's more mature. > > > > > > Currently it only compiles stuff that uses autofoo. Some things are > > > skipped, mostly due to being deprecated or broken and unmantained. > > > Most of what is skipped is in misc. Everything in e17, misc, and > > > e_modules is included except for the e17/test and e17/docs > > > directories. > > > > can you... put the script in cvs somewhere? tough to talk about > > something we can't see. > > After much experimentation, we ended up with easy_e17.sh and a post > install script. easy_e17.sh is available from morlenxus' server as > I've mentioned before. The post install script relies on the current > svn version, but that will be the next release soon enough. > > I'll put the post install script into cvs somewhere. The real question > is - where? Create a new project in e17/apps/nightly_build? e17/test > perhaps? > > The major problem at the moment is that sf.net is really fussy about > emails you send to it. Seems like a typical workstation with a dynamic > IP and default install will not be able to use sendmail a script to send to sf.net. Looks like you need a real mail server to > do it for you. So some config of local mail systems may be needed if > we want volunteers to use this to cover various distros etc. > > Once we are happy with the output generated and where it goes we can > worry about OS / distro / CPU coverage details. tus why you should not worry and just run this on e2.enlightenment.org - it already can send email as part of bugzilla requirements. :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Wed, 18 Jul 2007 12:30:53 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Tue, 17 Jul 2007 10:14:58 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > Attached is the result of a first cut at a nightly build script. > > Early days, baby steps, don't pick over the little details. We can > > start with the basics and work up to more features later. > > > > For now I can run this on my boxen while it gets developed further. > > Move it to the E servers and volunteer boxen when it's more mature. > > > > Currently it only compiles stuff that uses autofoo. Some things are > > skipped, mostly due to being deprecated or broken and unmantained. > > Most of what is skipped is in misc. Everything in e17, misc, and > > e_modules is included except for the e17/test and e17/docs > > directories. > > can you... put the script in cvs somewhere? tough to talk about > something we can't see. After much experimentation, we ended up with easy_e17.sh and a post install script. easy_e17.sh is available from morlenxus' server as I've mentioned before. The post install script relies on the current svn version, but that will be the next release soon enough. I'll put the post install script into cvs somewhere. The real question is - where? Create a new project in e17/apps/nightly_build? e17/test perhaps? The major problem at the moment is that sf.net is really fussy about emails you send to it. Seems like a typical workstation with a dynamic IP and default install will not be able to use sendmail signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
Greetings. I'm not an E developer at all but thought I'd chime in anyways. I'm probably trying to teach the choir how to sing but it appears to me that what people seem to be looking for here, essentially, is a buildbot. [ http://en.wikipedia.org/wiki/Buildbot ] If the need is along the lines of : a. Triggering a build of specific components of the e source base in response to a commit (amongst a host of other build triggers) b. Automatic intimation to "culprit" developers, lists etc c. IRC integration for build breakages alerts (which would be cool for #e etc) d. Automated testing where appropriate ..then the buildbot sounds like a good fit. I guess this has probably been discussed in the past and shelved because of the extra work involved in setting this up (among other things) but it does sound like exactly what's needed. That said, I'm a huge fan of the easy_e17.sh project which, it appears, is the cornerstone on which the implementation being discussed currently seems to rest. Cheerio! Robin On Thu, 2007-07-19 at 10:51 +0300, Chady Kassouf wrote: > On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > > > Stashing it all on a web page means that people will not bother to look > > > at it. Sending a built/not built summary to this list means that > > > people will actually read it. Stashing the full build logs on the web > > > is good, it doesn't fill the list with tons of shit no one needs to > > > look at, and the one or two people that note that their project is not > > > building know where to find the full build log to investigate further. > > > > > Maybe the the full output could be sent to the CVS mailing list. That > > sounds a bit counterintuitive but if you think about it it's purpose is to > > alert developers of changes to the codebase. This is somewhat similar. > > > Well, not really... > when information get bigger, you will tend to start skipping it. > A summary like this is great, cause all you have to do is skim the list for > ERROR and then you'll know what broke and you go check it out, but trying to > wade through all the output of a build to find an error is painful. > > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Thu, 19 Jul 2007 10:51:13 +0300 "Chady Kassouf" <[EMAIL PROTECTED]> wrote: > On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > > > Stashing it all on a web page means that people will not bother to look > > > at it. Sending a built/not built summary to this list means that > > > people will actually read it. Stashing the full build logs on the web > > > is good, it doesn't fill the list with tons of shit no one needs to > > > look at, and the one or two people that note that their project is not > > > building know where to find the full build log to investigate further. > > > > > Maybe the the full output could be sent to the CVS mailing list. That > > sounds a bit counterintuitive but if you think about it it's purpose is to > > alert developers of changes to the codebase. This is somewhat similar. > > > Well, not really... > when information get bigger, you will tend to start skipping it. > A summary like this is great, cause all you have to do is skim the list for > ERROR and then you'll know what broke and you go check it out, but trying to > wade through all the output of a build to find an error is painful. That's probably true. However it could be shortened a bit. You could have the script output something like this: Build results: 232 passed, 5 failed. Failing modules: To see a full output of the build script please go to . Pretty please ;) I think that's short enough not to hurt anyone's eyes. > > > -- > Chady 'Leviathan' Kassouf > http://chady.net/ > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Eugen Minciu. Wasting valuable time since 1985. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On 7/19/07, Eugen Minciu <[EMAIL PROTECTED]> wrote: > > > Stashing it all on a web page means that people will not bother to look > > at it. Sending a built/not built summary to this list means that > > people will actually read it. Stashing the full build logs on the web > > is good, it doesn't fill the list with tons of shit no one needs to > > look at, and the one or two people that note that their project is not > > building know where to find the full build log to investigate further. > > > Maybe the the full output could be sent to the CVS mailing list. That > sounds a bit counterintuitive but if you think about it it's purpose is to > alert developers of changes to the codebase. This is somewhat similar. Well, not really... when information get bigger, you will tend to start skipping it. A summary like this is great, cause all you have to do is skim the list for ERROR and then you'll know what broke and you go check it out, but trying to wade through all the output of a build to find an error is painful. -- Chady 'Leviathan' Kassouf http://chady.net/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
> Stashing it all on a web page means that people will not bother to look > at it. Sending a built/not built summary to this list means that > people will actually read it. Stashing the full build logs on the web > is good, it doesn't fill the list with tons of shit no one needs to > look at, and the one or two people that note that their project is not > building know where to find the full build log to investigate further. > Maybe the the full output could be sent to the CVS mailing list. That sounds a bit counterintuitive but if you think about it it's purpose is to alert developers of changes to the codebase. This is somewhat similar. Then again, I don't know ... Just my 2% of a dollar. -- Eugen Minciu. Wasting valuable time since 1985. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On 7/18/07, David Seikel <[EMAIL PROTECTED]> wrote: > > Stashing it all on a web page means that people will not bother to look > at it. Sending a built/not built summary to this list means that > people will actually read it. Stashing the full build logs on the web > is good, it doesn't fill the list with tons of shit no one needs to > look at, and the one or two people that note that their project is not > building know where to find the full build log to investigate further. I would only send the summary if there is a failure, or if there is a difference since the last build log and then only send the differences Too much or repetitive information also discourages people from looking at it. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Wed, 18 Jul 2007 12:30:53 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Tue, 17 Jul 2007 10:14:58 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > Attached is the result of a first cut at a nightly build script. > > Early days, baby steps, don't pick over the little details. We can > > start with the basics and work up to more features later. > > > > For now I can run this on my boxen while it gets developed further. > > Move it to the E servers and volunteer boxen when it's more mature. > > > > Currently it only compiles stuff that uses autofoo. Some things are > > skipped, mostly due to being deprecated or broken and unmantained. > > Most of what is skipped is in misc. Everything in e17, misc, and > > e_modules is included except for the e17/test and e17/docs > > directories. > > can you... put the script in cvs somewhere? tough to talk about > something we can't see. I'm modifying easy_e17.sh. morlenxus has his own svn server that includes it. http://omicron.homeip.net/projects/#easy_e17.sh My changes are committed to that svn server, and morlenxus is also pitching in with relevant changes. There is also a small wrapper script that just calls easy_e17.sh then uses sendmail to send the results. Seems to work fine sending to one of my email addresses, but fails when sending to this list. I blame gmail and sf.net not talking to one another properly, I've had issues with that in the past. This morning there would have been two automated summaries sent if it was not for this email problem. One for Ubuntu/x86 and one for YDL/PPC. I'll wait a few days to see if a bounce is sent. When I've had this problem in the past, neither gmail nor sf.net bothered to send bounces. In the end, I might just subscribe one of my other email addresses to the list. Just so we have something to look at, I'll manually send one of the summaries as it would normally appear. > > Do we need more information, less information, actual build logs to > > be stored somewhere, etc? Throw in e16, eterm, e17/test, and > > e17/docs just for completion? > > personally - i think this needs an explicit list of things to build > (and thus the order to build them in). doing it as a user is trivial > - just need to do a --prefix=/path/to/user/owned/dir in configure. > the rest is just a matter of $PKG_CONFIG_PATH, $PATH, > $LD_LIBRARY_PATH then > > cvs update -dP > for I in `cat build-list`; do build.sh; done >& build.log > > and a build.sh (or a shell func) that runs the autogen.sh, make and > make install with a low priority with nice + ionice. easy_E17.sh already does all that and more, which is why I started with it. > the build log doesn't need to be fancy or pretty - just needs to be > all the raw output of the whole build. > > > I think a nightly email to this list would be the most useful, just > > stashing the results away on the web somewhere makes it too easy to > > ignore. > > don't even think we need that much - just stashing the results in a > web page somewhere is enough Stashing it all on a web page means that people will not bother to look at it. Sending a built/not built summary to this list means that people will actually read it. Stashing the full build logs on the web is good, it doesn't fill the list with tons of shit no one needs to look at, and the one or two people that note that their project is not building know where to find the full build log to investigate further. I'm basing this initial version on what I've seen working for other projects with lots of sub projects. > > For the curious, I'm modifying easy_e17.sh to do this, as I'm very > > familiar with it. I've discussed this with morlenxus, and we have > > agreed to add a few things to easy_e17.sh to make it better for this > > type of work. > > > > TODO - > > > > Remove need to be root/use sudo. Done. > > Support things that don't use the autofoo three step. > > Add qemu / scratchbox support for hardware / OSs we don't have test > > boxen for. > > Maybe create .rpm files on RPM based distros and .deb files on > > Debian based distros. > > BTW, while on the subject of automated testing, I've been asked if > > E17 supports accessibility stuff. Apparently he wanted to use a > > particular automated GUI test system that uses that. As far as I > > know, we do not support that. Any thoughts? > > you will need to be more specific with "supports accessibility > stuff". e make no particular efforts one way or another for > "accessibility". if something works or not depends on the details of > what it does. It was a request from a fellow TSS developer, he was not more specific than to mention that he wants to use some automated test tool. signature.asc Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits.
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Tue, 17 Jul 2007 10:14:58 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > Attached is the result of a first cut at a nightly build script. Early > days, baby steps, don't pick over the little details. We can start > with the basics and work up to more features later. > > For now I can run this on my boxen while it gets developed further. > Move it to the E servers and volunteer boxen when it's more mature. > > Currently it only compiles stuff that uses autofoo. Some things are > skipped, mostly due to being deprecated or broken and unmantained. > Most of what is skipped is in misc. Everything in e17, misc, and > e_modules is included except for the e17/test and e17/docs directories. can you... put the script in cvs somewhere? tough to talk about something we can't see. > Do we need more information, less information, actual build logs to be > stored somewhere, etc? Throw in e16, eterm, e17/test, and e17/docs > just for completion? personally - i think this needs an explicit list of things to build (and thus the order to build them in). doing it as a user is trivial - just need to do a --prefix=/path/to/user/owned/dir in configure. the rest is just a matter of $PKG_CONFIG_PATH, $PATH, $LD_LIBRARY_PATH then cvs update -dP for I in `cat build-list`; do build.sh; done >& build.log and a build.sh (or a shell func) that runs the autogen.sh, make and make install with a low priority with nice + ionice. the build log doesn't need to be fancy or pretty - just needs to be all the raw output of the whole build. > I think a nightly email to this list would be the most useful, just > stashing the results away on the web somewhere makes it too easy to > ignore. don't even think we need that much - just stashing the results in a web page somewhere is enough > For the curious, I'm modifying easy_e17.sh to do this, as I'm very > familiar with it. I've discussed this with morlenxus, and we have > agreed to add a few things to easy_e17.sh to make it better for this > type of work. > > TODO - > > Remove need to be root/use sudo. > Support things that don't use the autofoo three step. > Add qemu / scratchbox support for hardware / OSs we don't have test > boxen for. > Maybe create .rpm files on RPM based distros and .deb files on Debian > based distros. > > > BTW, while on the subject of automated testing, I've been asked if E17 > supports accessibility stuff. Apparently he wanted to use a particular > automated GUI test system that uses that. As far as I know, we do not > support that. Any thoughts? you will need to be more specific with "supports accessibility stuff". e make no particular efforts one way or another for "accessibility". if something works or not depends on the details of what it does. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
Attached is the result of a first cut at a nightly build script. Early days, baby steps, don't pick over the little details. We can start with the basics and work up to more features later. For now I can run this on my boxen while it gets developed further. Move it to the E servers and volunteer boxen when it's more mature. Currently it only compiles stuff that uses autofoo. Some things are skipped, mostly due to being deprecated or broken and unmantained. Most of what is skipped is in misc. Everything in e17, misc, and e_modules is included except for the e17/test and e17/docs directories. Do we need more information, less information, actual build logs to be stored somewhere, etc? Throw in e16, eterm, e17/test, and e17/docs just for completion? I think a nightly email to this list would be the most useful, just stashing the results away on the web somewhere makes it too easy to ignore. For the curious, I'm modifying easy_e17.sh to do this, as I'm very familiar with it. I've discussed this with morlenxus, and we have agreed to add a few things to easy_e17.sh to make it better for this type of work. TODO - Remove need to be root/use sudo. Support things that don't use the autofoo three step. Add qemu / scratchbox support for hardware / OSs we don't have test boxen for. Maybe create .rpm files on RPM based distros and .deb files on Debian based distros. BTW, while on the subject of automated testing, I've been asked if E17 supports accessibility stuff. Apparently he wanted to use a particular automated GUI test system that uses that. As far as I know, we do not support that. Any thoughts? Build log for Enlightenment DR 0.17 on 2007-07-17 08:46:27 +10 Ubuntu 6.10 \n \l Linux cluster 2.6.17-11-generic #2 SMP Fri May 18 23:39:08 UTC 2007 i686 GNU/Linux autoconf (GNU Autoconf) 2.60 automake (GNU automake) 1.9.6 ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 22:14:06) imlib2 autogen make gendoc install ok edb autogen make install ok eet autogen make gendoc install ok evas autogen make gendoc install ok ecoreautogen make gendoc install ok embryo autogen make gendoc install ok edje autogen make gendoc install ok efreet autogen make gendoc install ok epeg autogen make gendoc install ok epsilon autogen make gendoc install ok esmart autogen make install ok emotion autogen make gendoc install ok ewl autogen make gendoc install ok engrave autogen make gendoc install ok etk autogen make gendoc install ok etk_extraautogen ERROR etk-perl no autogen.sh etox skipped evoakskipped evolve autogen make ERROR exml autogen make install ok enhance autogen make install ok imlib2_loaders autogen make install ok eautogen make install ok e_dbus autogen make install ok e_phys no autogen.sh e_utils autogen make install ok eclair autogen make install ok edje_editor autogen make install ok edje_viewer autogen make install ok edvi autogen make install ok eflppno autogen.sh elation autogen make install ok elicit autogen make install ok elitaire autogen make install ok emphasis autogen make gendoc install ok empower autogen make install ok engycad autogen make install ok enityautogen make gendoc install ok enscribe skipped enterminus autogen make gendoc install ok entice autogen make gendoc install ok entrance autogen make install ok entrance_edit_guiautogen make install ok evfs autogen make install ok entropy autogen make install ok epdf autogen ERROR ephoto autogen make install ok estickiesautogen make install ok etk_server skipped euphoria no autogen.sh examine autogen make gendoc install ok exhibit autogen make gendoc install ok exorcist no autogen.sh expedite autogen make install ok express autogen make install ok extrackt autogen make install ok gfx_routines skipped i
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Tue, 17 Jul 2007 07:27:51 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Tue, 17 Jul 2007 01:45:00 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > On Mon, 16 Jul 2007 10:28:07 -0500 "Nathan Ingersoll" > > <[EMAIL PROTECTED]> wrote: > > > > > On 7/16/07, David Seikel <[EMAIL PROTECTED]> wrote: > > > > > > > > > So you are you complaining about API changes breaking the CVS > > > > > build and not getting fixed, > > > > > > > > Yes. > > > > > > This is actually a series of problems, not just one person taking > > > the time to fix CVS, though that is part of it. It also indicates > > > we are lacking good review of changes, user feedback is not > > > reaching the developers that will fix it, and maintainers are not > > > updating their module as dependency changes occur. > > > > > > An automated nightly build could improve the build break > > > detection. > > > > I do a mostly regular build of almost everything, which is why I > > notice these things. I'll be happy to setup regular automated > > builds. > > > > Where would an automated nightly build best be run? Where would the > > results be delivered? Since we are scattered all over the planet, > > whose night should be used to define "nightly"? > > we have servers! e1.enlightenment.org and e2.enlightenment.org. we > can install any locally required packages for builds and have them > automated. build + install (into a specific prefix - eg /opt/e17). > only a matter of scripting it up so it is automated and won't fail if > not done as root (we need to do it as a user here for security > reasons considering what a build can actually do). currently the > builds should not fail if done as a user. Still working on the automation script. Should have a first cut result available in an hour. > > Many other questions need to be answered to set this up. > > > > Off the top of my head. sf.net has a compile farm that can be used > > for such things and I already use it for another project. Then we > > can do builds on several platforms. I have seen other projects get > > the results of the nightly build sent as a single email to their dev > > mailing list each night. > > aaah - other platforms - that is a problem. we can do a nightly build > for at least x86 (and x86_64). that should be sufficient for us for > now. other arches are good - but we only have so much in the way of > resources. we could do ARM builds via scratchbox the same way we do > x86/x86_64 easily. i assume ppc could be done in a similar way if > someone wants to set up a scratchbox ppc env. Think I can scare up some PPC build boxen. B-) signature.asc Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Tue, 17 Jul 2007 01:45:00 +1000 David Seikel <[EMAIL PROTECTED]> babbled: > On Mon, 16 Jul 2007 10:28:07 -0500 "Nathan Ingersoll" > <[EMAIL PROTECTED]> wrote: > > > On 7/16/07, David Seikel <[EMAIL PROTECTED]> wrote: > > > > > > > So you are you complaining about API changes breaking the CVS > > > > build and not getting fixed, > > > > > > Yes. > > > > This is actually a series of problems, not just one person taking the > > time to fix CVS, though that is part of it. It also indicates we are > > lacking good review of changes, user feedback is not reaching the > > developers that will fix it, and maintainers are not updating their > > module as dependency changes occur. > > > > An automated nightly build could improve the build break detection. > > I do a mostly regular build of almost everything, which is why I notice > these things. I'll be happy to setup regular automated builds. > > Where would an automated nightly build best be run? Where would the > results be delivered? Since we are scattered all over the planet, > whose night should be used to define "nightly"? we have servers! e1.enlightenment.org and e2.enlightenment.org. we can install any locally required packages for builds and have them automated. build + install (into a specific prefix - eg /opt/e17). only a matter of scripting it up so it is automated and won't fail if not done as root (we need to do it as a user here for security reasons considering what a build can actually do). currently the builds should not fail if done as a user. > Many other questions need to be answered to set this up. > > Off the top of my head. sf.net has a compile farm that can be used for > such things and I already use it for another project. Then we can do > builds on several platforms. I have seen other projects get the > results of the nightly build sent as a single email to their dev > mailing list each night. aaah - other platforms - that is a problem. we can do a nightly build for at least x86 (and x86_64). that should be sufficient for us for now. other arches are good - but we only have so much in the way of resources. we could do ARM builds via scratchbox the same way we do x86/x86_64 easily. i assume ppc could be done in a similar way if someone wants to set up a scratchbox ppc env. > I live an the same side of the planet as raster, so I share his night, > but I work at strange hours so that I can deal with my USA client in > real time (and not disrupt my local clients servers during local > business hours), so I don't really care what time it runs at. Probably > doesn't matter so much what time, so I'll suggest a completely > arbitrary GMT midnight to start the builds. Probably take one to two > hours to complete each build, but on the sf.net compile farm, they can > all build at the same time. On the other hand, trying to dodge compile > farm busy times might be worth while. as i said - "we have the power" :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
On Mon, 16 Jul 2007 18:40:27 +0200 Morten Nilsen <[EMAIL PROTECTED]> wrote: > David Seikel wrote: > > Where would an automated nightly build best be run? > > We might be able to get that sorted using community horsepowers.. > I, for one, could certainly run x86 builds on one of my boxes. I'll put together something that will run on my three boxen first (x86, PPC, Cell), then package it up into something simple others can use. I'm still leaning towards a centralised build though, that way only one build report gets sent, and we don't have to deal with the usual "user X volunteered resources but didn't deliver" admin nightmare we've had before. That's why qemu is on my radar. Something simple first though, to work out the kinks. signature.asc Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Nightly builds - Was: Is this a community project?
David Seikel wrote: > Where would an automated nightly build best be run? We might be able to get that sorted using community horsepowers.. I, for one, could certainly run x86 builds on one of my boxes. -- Cheers, Morten - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Nightly builds - Was: Is this a community project?
On Mon, 16 Jul 2007 10:28:07 -0500 "Nathan Ingersoll" <[EMAIL PROTECTED]> wrote: > On 7/16/07, David Seikel <[EMAIL PROTECTED]> wrote: > > > > > So you are you complaining about API changes breaking the CVS > > > build and not getting fixed, > > > > Yes. > > This is actually a series of problems, not just one person taking the > time to fix CVS, though that is part of it. It also indicates we are > lacking good review of changes, user feedback is not reaching the > developers that will fix it, and maintainers are not updating their > module as dependency changes occur. > > An automated nightly build could improve the build break detection. I do a mostly regular build of almost everything, which is why I notice these things. I'll be happy to setup regular automated builds. Where would an automated nightly build best be run? Where would the results be delivered? Since we are scattered all over the planet, whose night should be used to define "nightly"? Many other questions need to be answered to set this up. Off the top of my head. sf.net has a compile farm that can be used for such things and I already use it for another project. Then we can do builds on several platforms. I have seen other projects get the results of the nightly build sent as a single email to their dev mailing list each night. I live an the same side of the planet as raster, so I share his night, but I work at strange hours so that I can deal with my USA client in real time (and not disrupt my local clients servers during local business hours), so I don't really care what time it runs at. Probably doesn't matter so much what time, so I'll suggest a completely arbitrary GMT midnight to start the builds. Probably take one to two hours to complete each build, but on the sf.net compile farm, they can all build at the same time. On the other hand, trying to dodge compile farm busy times might be worth while. signature.asc Description: PGP signature - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
