From: David S. <on...@gm...> - 2007-07-19 02:28:10
Attachments:
signature.asc
|
Hmm, the script can send to other mailing lists just fine. Begin forwarded message: Date: Thu, 19 Jul 2007 12:16:46 +1000 (EST) From: David Seikel To: tes...@ma... Subject: [Test-edevelop] Nightly build log for E17 Build log for Enlightenment DR 0.17 on 2007-07-19 11:16:34 +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 docs install ok edb autogen make install ok eet autogen make docs install ok evas autogen make docs install ok ecore autogen make docs install ok embryo autogen make docs install ok edje autogen make docs install ok efreet autogen make docs install ok epeg autogen make docs install ok epsilon autogen make docs install ok esmart autogen make install ok emotion autogen make docs install ok ewl autogen make docs install ok engrave autogen make docs install ok etk autogen make docs install ok etk_extra autogen ERROR etk-perl no build system etox skipped evoak skipped evolve autogen make ERROR exml autogen make install ok enhance autogen make install ok imlib2_loaders autogen make install ok e autogen make install ok e_dbus autogen make install ok e_phys bootstrap ERROR e_utils autogen make install ok eclair autogen make install ok edje_editor autogen ERROR edje_viewer autogen make install ok edvi autogen make install ok eflpp bootstrap configure make ERROR elation autogen make install ok elicit autogen make install ok elitaire autogen make install ok emphasis autogen make docs install ok empower autogen make install ok engycad autogen make install ok enity autogen make docs install ok enscribe skipped enterminus autogen make docs install ok entice autogen make docs install ok entrance autogen make install ok entrance_edit_gui autogen make install ok evfs autogen make install ok entropy autogen make install ok epdf autogen ERROR ephoto autogen make install ok estickies autogen make install ok etk_server skipped euphoria no build system examine autogen make docs install ok exhibit autogen make docs install ok exorcist no build system expedite autogen make install ok express autogen make install ok extrackt autogen make install ok gfx_routines skipped iconbar autogen make install ok imlib2_tools autogen make install ok med skipped ruby-efl no build system Evas_Perl no build system Imlib2_Perl no build system camE skipped eflame no build system elapse autogen make ERROR embrace skipped engage autogen make install ok enotes skipped enthrall no build system envision autogen make install ok epbb skipped eplay skipped equate autogen make install ok erss skipped esmart_rsvg no build system feh autogen make install ok lvs-gui skipped nexus no build system pesh no build system notgame skipped rage autogen make install ok scrot autogen make install ok webcam skipped alarm autogen make install ok bling autogen make install ok cpu autogen make install ok deskshow autogen make install ok emu autogen make install ok flame autogen make install ok forecasts autogen make install ok language autogen make install ok mail autogen make install ok mem autogen make install ok mixer autogen make install ok moon autogen make install ok net autogen make install ok news autogen make install ok photo autogen make install ok rain autogen make install ok screenshot autogen make install ok slideshow autogen make install ok snow autogen make install ok taskbar autogen make install ok tclock autogen make install ok uptime autogen make install ok weather autogen make install ok winselector autogen make install ok wlan autogen make install ok The nightly build system tries to build everything in the Enlightenment CVS or give a reason why. Currently eterm, e16, e17/docs, e17/test, and web are not built. Feel free to enlighten me about any decisions. The web directory does not contain anything that needs to be built. The e17/test directory is just a dumping ground for old testing stuff that is not meant to be built automatically. The e17/docs directory contains documentation. Some of it can be "built" but I have not bothered yet. The eterm and e16 directories are not currently being built because the build script used as the basis for the nightly build system didn't support those. This may change. The "autogen make gendoc install ok" result means that everything built fine. Not every project has gendoc, so that will be missing from the result for those projects. The "ERROR" result means that something went wrong during the build test. There may be a partial "autogen make gendoc install" result before the error. So "autogen make ERROR" means that the make step failed. The "no build system" result means that this particular project does not have a supported build system. Currently supported build systems are autogen.sh and bootstrap scripts. Others are likely to be added in the future. The "skipped" result means that the nightly build system was configured to skip that particular project for some reason. Those reasons should be listed here - etox - Obsolete. evoak - Obsolete. enscribe - Unmaintained, broken, and too old to fix.=20 med - Unmaintained, broken, and too old to fix.=20 camE - Unmaintained, broken, and too old to fix.=20 embrace - Unmaintained, broken, and too old to fix.=20 epbb - Unmaintained, broken, and too old to fix.=20 eplay - Unmaintained, broken, and too old to fix.=20 erss - Unmaintained, broken, and too old to fix.=20 lvs-gui - Unmaintained, broken, and too old to fix.=20 notgame - Unmaintained, broken, and too old to fix. webcam - Unmaintained, broken, and too old to fix.=20 enotes - Unmaintained, broken, and too old to fix.=20 etk_server - Uses huge amounts of RAM, so may fail.=20 gfx_routines - This was just a bunch of graphics tests. NOTE: sometimes an ERROR is the result of a failed dependency. The epdf project is a prime example, as it often requires the very latest poppler version, and not everybody is using the latest version of everything.=20 Some people are quite happy running a slightly older, stable OS. _______________________________________________ Test-edevelop mailing list Tes...@ma... http://lists.matrix-rad.net/mailman/listinfo/test-edevelop |
From: David S. <on...@gm...> - 2007-07-21 03:14:08
Attachments:
signature.asc
|
Build log for Enlightenment DR 0.17 on 2007-07-21 13:11:41 +1000 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) gettext (GNU gettext-runtime) 0.15 Failed Packages (and command that failed): eflpp make -j 2 elapse make -j 2 epdf ./autogen.sh --prefix=3D/opt/e17 --cache-file=3D/tmp/easy_e17/easy_e17.cache e_phys ./bootstrap etk_extra ./autogen.sh --prefix=3D/opt/e17 --cache-file=3D/tmp/easy_e17/easy_e17.cache etk-perl make install Evas_Perl make -j 2 Packages with no supported build system: eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl, Skipped Packages: camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, evoak, gfx_routines, lvs-gui, med, notgame, webcam, Successful Packages: alarm, bling, cpu, deskshow, eclair, ecore, edb, e_dbus, edje_editor, edje, edje_viewer, edvi, eet, efreet, elation, elicit, elitaire, e, embryo, emotion, emphasis, empower, emu, engage, engrave, engycad, enhance, enity, enterminus, entice, entrance_edit_gui, entrance, entropy, envision, epeg, ephoto, epsilon, equate, esmart, estickies, etk, e_utils, evas, evfs, evolve, ewl, examine, exhibit, exml, expedite, express, extrackt, feh, flame, forecasts, iconbar, imlib2_loaders, imlib2, Imlib2_Perl, imlib2_tools, language, mail, mem, mixer, moon, net, news, pesh, photo, rage, rain, screenshot, scrot, slideshow, snow, taskbar, tclock, uptime, weather, winselector, wlan, Build logs are available at http://onefang.humbug.org.au/E-build-logs/ The nightly build system tries to build everything in the Enlightenment CVS or give a reason why. Currently eterm, e16, e17/docs, e17/test, and web are not built. Feel free to enlighten me about any decisions. The web directory does not contain anything that needs to be built. The e17/test directory is just a dumping ground for old testing stuff that is not meant to be built automatically. The e17/docs directory contains documentation. Some of it can be "built" but I have not bothered yet. The eterm and e16 directories are not currently being built because the build script used as the basis for the nightly build system didn't support those. This may change. The "skipped" result means that the nightly build system was configured to skip that particular project for some reason. Those reasons should be listed here - etox - Obsolete. evoak - Obsolete. enscribe - Unmaintained, broken, and too old to fix. med - Unmaintained, broken, and too old to fix. camE - Unmaintained, broken, and too old to fix. embrace - Unmaintained, broken, and too old to fix. epbb - Unmaintained, broken, and too old to fix. eplay - Unmaintained, broken, and too old to fix. erss - Unmaintained, broken, and too old to fix. lvs-gui - Unmaintained, broken, and too old to fix. notgame - Unmaintained, broken, and too old to fix. webcam - Unmaintained, broken, and too old to fix. enotes - Unmaintained, broken, and too old to fix. etk_server - Uses huge amounts of RAM, so may fail. gfx_routines - This was just a bunch of graphics tests. NOTE: sometimes an ERROR is the result of a failed dependency. The epdf project is a prime example, as it often requires the very latest poppler version, and not everybody is using the latest version of everything. Some people are quite happy running a slightly older, stable OS. |
From: David S. <on...@gm...> - 2007-07-21 03:24:28
Attachments:
signature.asc
|
Damn, cutting and pasting it to my mail client screwed up the formatting a little bit. The next one will test to see if I have done enough to satisfy the sf.net list servers that I am a legitimate member of the list and can send via the sendmail command from a script. On Sat, 21 Jul 2007 13:13:57 +1000 David Seikel <on...@gm...> wrote: > etk-perl make install Now that Makefile.PL is supported, that autogen.sh file should be removed. It failed because it tried to build as a user and - Makefile.PL prefix=3D/foo/bar is needed. Autogen.sh is checked before Makefile.PL as most projects use autogen.sh. |
From: Eugen M. <mi...@gm...> - 2007-07-21 12:36:36
|
Hi list, I'm sorry if this is actually a repost of a message I wrote a couple of days ago. However, it may be that my MDA (which wasn't properly configured back then) failed to send that message. If it is a repost, I deeply apologize. I have a couple of comments about the format of this build log. Obviously, this is a bikeshed thing and I'll avoid posting about it again. Obviously, these comments are just my impressions and you needn't share them. Excerpts from David Seikel's message of Sat Jul 21 06:13:57 +0300 2007: > Build log for Enlightenment DR 0.17 on 2007-07-21 13:11:41 +1000 > > 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) > gettext (GNU gettext-runtime) 0.15 > 1. The list of projects that fail should probably be the first thing to see after the name of the OS. The detailed list of autotools versions and such should probably only be detailed in the log on the web page, or near the end of this message. > Failed Packages (and command that failed): > eflpp make -j 2 > elapse make -j 2 > epdf ./autogen.sh --prefix=/opt/e17 > --cache-file=/tmp/easy_e17/easy_e17.cache e_phys ./bootstrap > etk_extra ./autogen.sh --prefix=/opt/e17 > --cache-file=/tmp/easy_e17/easy_e17.cache etk-perl make install > Evas_Perl make -j 2 2. The list of failed projects should (at least in the beginning of the message) be a single line (possibly wrapped) of text. example: Failed Packages: eflpp elapse epdf e_phys etk_extra etk-perl Evas_Perl 3. Each project that failed to get built should have a link to its log something like: Details about failed packages: eflpp: failed command: make -j 2 build log: http://onefang.humbug.org.au/E-build-logs/eflpp.log ... > > Packages with no supported build system: > eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl, > > Skipped Packages: > camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, > evoak, gfx_routines, lvs-gui, med, notgame, webcam, > > Successful Packages: > alarm, bling, cpu, deskshow, eclair, ecore, edb, e_dbus, edje_editor, > edje, edje_viewer, edvi, eet, efreet, elation, elicit, elitaire, e, > embryo, emotion, emphasis, empower, emu, engage, engrave, engycad, > enhance, enity, enterminus, entice, entrance_edit_gui, entrance, > entropy, envision, epeg, ephoto, epsilon, equate, esmart, estickies, > etk, e_utils, evas, evfs, evolve, ewl, examine, exhibit, exml, > expedite, express, extrackt, feh, flame, forecasts, iconbar, > imlib2_loaders, imlib2, Imlib2_Perl, imlib2_tools, language, mail, mem, > mixer, moon, net, news, pesh, photo, rage, rain, screenshot, scrot, > slideshow, snow, taskbar, tclock, uptime, weather, winselector, wlan, 4. The list of projects that were successfully built shouldn't be written, I think. The whole point of this system is to tell people what projects haven't been built. A lot of lines of text are taken up by the projects that haven been successfully built. > > Build logs are available at http://onefang.humbug.org.au/E-build-logs/ > 5. The build logs should be dated, but I'm sure that will happen (something like: http://onefang.humbug.org.au/E-build-logs/2007/07/21) > The nightly build system tries to build everything in the Enlightenment > CVS or give a reason why. Currently eterm, e16, e17/docs, e17/test, and > web are not built. Feel free to enlighten me about any decisions. > > The web directory does not contain anything that needs to be built. > > The e17/test directory is just a dumping ground for old testing stuff > that is not meant to be built automatically. > > The e17/docs directory contains documentation. Some of it can be > "built" but I have not bothered yet. > > The eterm and e16 directories are not currently being built because the > build script used as the basis for the nightly build system didn't > support those. This may change. > Maybe I'm not understanding this and this part isn't really a part of the log. But if it is, I think this is maybe a bit too verbose. How about something like: The nightly build system tries to build everything in the Enlightenment CVS or give a reason why it isn't being built. For more information about this system, please go to this link: ... > The "skipped" result means that the nightly build system was configured > to skip that particular project for some reason. Those reasons should > be listed here - > > etox - Obsolete. > evoak - Obsolete. > enscribe - Unmaintained, broken, and too old to fix. > med - Unmaintained, broken, and too old to fix. > camE - Unmaintained, broken, and too old to fix. > embrace - Unmaintained, broken, and too old to fix. > epbb - Unmaintained, broken, and too old to fix. > eplay - Unmaintained, broken, and too old to fix. > erss - Unmaintained, broken, and too old to fix. > lvs-gui - Unmaintained, broken, and too old to fix. > notgame - Unmaintained, broken, and too old to fix. > webcam - Unmaintained, broken, and too old to fix. > enotes - Unmaintained, broken, and too old to fix. > etk_server - Uses huge amounts of RAM, so may fail. > gfx_routines - This was just a bunch of graphics tests. > > > NOTE: sometimes an ERROR is the result of a failed dependency. The epdf > project is a prime example, as it often requires the very latest poppler > version, and not everybody is using the latest version of everything. > Some people are quite happy running a slightly older, stable OS. Of course, these are all my opinion, and you know what those are like ... :) -- Eugen Minciu. Wasting valuable time since 1985. |
From: David S. <on...@gm...> - 2007-07-24 22:15:08
Attachments:
signature.asc
|
Sorry about not getting back to this sooner, I've been dreadfully ill. On Sat, 21 Jul 2007 15:36:26 +0300 Eugen Minciu <mi...@gm...> wrote: > I have a couple of comments about the format of this build log. > Obviously, this is a bikeshed thing and I'll avoid posting about it > again. Obviously, these comments are just my impressions and you > needn't share them. >=20 > Excerpts from David Seikel's message of Sat Jul 21 06:13:57 +0300 > 2007: > > Build log for Enlightenment DR 0.17 on 2007-07-21 13:11:41 +1000 > >=20 > > Ubuntu 6.10 \n \l > >=20 > > Linux cluster 2.6.17-11-generic #2 SMP Fri May 18 23:39:08 UTC 2007 > > i686 GNU/Linux > >=20 > > 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) > > gettext (GNU gettext-runtime) 0.15 > >=20 > 1. The list of projects that fail should probably be the first thing > to see after the name of the OS. The detailed list of autotools > versions and such should probably only be detailed in the log on the > web page, or near the end of this message. Slowly but surely I'm beating the report format into some sort of useful shape. Something like this is planned. > > Failed Packages (and command that failed): > > eflpp make -j 2 > > elapse make -j 2 > > epdf ./autogen.sh --prefix=3D/opt/e17 > > --cache-file=3D/tmp/easy_e17/easy_e17.cache e_phys ./bootstrap > > etk_extra ./autogen.sh --prefix=3D/opt/e17 > > --cache-file=3D/tmp/easy_e17/easy_e17.cache etk-perl make install > > Evas_Perl make -j 2 > 2. The list of failed projects should (at least in the beginning of > the message) be a single line (possibly wrapped) of text. >=20 > example:=20 > Failed Packages: eflpp elapse epdf e_phys etk_extra etk-perl Evas_Perl Another good idea I'll consider. > 3. Each project that failed to get built should have a link to its log > something like: >=20 > Details about failed packages: > eflpp: > failed command: make -j 2 > build log: http://onefang.humbug.org.au/E-build-logs/eflpp.log Already planning on including a link to the log file. > > Successful Packages: > > alarm, bling, cpu, deskshow, eclair, ecore, edb, e_dbus, > > edje_editor, edje, edje_viewer, edvi, eet, efreet, elation, elicit, > > elitaire, e, embryo, emotion, emphasis, empower, emu, engage, > > engrave, engycad, enhance, enity, enterminus, entice, > > entrance_edit_gui, entrance, entropy, envision, epeg, ephoto, > > epsilon, equate, esmart, estickies, etk, e_utils, evas, evfs, > > evolve, ewl, examine, exhibit, exml, expedite, express, extrackt, > > feh, flame, forecasts, iconbar, imlib2_loaders, imlib2, > > Imlib2_Perl, imlib2_tools, language, mail, mem, mixer, moon, net, > > news, pesh, photo, rage, rain, screenshot, scrot, slideshow, snow, > > taskbar, tclock, uptime, weather, winselector, wlan, > 4. The list of projects that were successfully built shouldn't be > written, I think. The whole point of this system is to tell people > what projects haven't been built. A lot of lines of text are taken up > by the projects that haven been successfully built. It's a sanity check. Did package X not get built because it failed, was skipped, or it's not even in the list of packages to test? This list of successful packages covers that last one. If a new package gets added, and doesn't show up on any of those lists, the author of the new package knows that the list to be checked needs updating. I'll be keeping the list up to date, but other devs should be able to tweak the list as needed. Especially if I'm ill and can't get anything done. B-) > > Build logs are available at > > http://onefang.humbug.org.au/E-build-logs/ > >=20 > 5. The build logs should be dated, but I'm sure that will happen > (something like: http://onefang.humbug.org.au/E-build-logs/2007/07/21) Don't think we really want to keep old logs, or if we do, not too many old logs. > > The nightly build system tries to build everything in the > > Enlightenment CVS or give a reason why. Currently eterm, e16, > > e17/docs, e17/test, and web are not built. Feel free to enlighten > > me about any decisions. > >=20 > > The web directory does not contain anything that needs to be built. > >=20 > > The e17/test directory is just a dumping ground for old testing > > stuff that is not meant to be built automatically. > >=20 > > The e17/docs directory contains documentation. Some of it can be > > "built" but I have not bothered yet. > >=20 > > The eterm and e16 directories are not currently being built because > > the build script used as the basis for the nightly build system > > didn't support those. This may change. > >=20 > Maybe I'm not understanding this and this part isn't really a part of > the log. But if it is, I think this is maybe a bit too verbose. How > about something like: >=20 > The nightly build system tries to build everything in the > Enlightenment CVS or give a reason why it isn't being built.=20 > For more information about this system, please go to this link: ... Already done. Just waiting to be healthy enough to get back to it and actually create the files on the e2 web server. |
From: David S. <on...@gm...> - 2007-07-25 02:07:44
Attachments:
signature.asc
|
Build log for Enlightenment DR 0.17 on 2007-07-24 18:38:35 -0700 Build logs are available at http://download.enlightenment.org/tests/logs Debian GNU/Linux 4.0 \n \l Linux enlightenment2 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux Autoconf version 2.13 automake (GNU automake) 1.10 ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 22:14:06) gettext (GNU gettext-runtime) 0.16.1 FAILED PACKAGE: bling COMMAND: make -j 2 BUILD LOG: http://download.enlightenment.org/tests/logs/bling.log FAILED PACKAGE: edvi COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/edvi.log=20 FAILED PACKAGE: eflpp=20 COMMAND: ./configure --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/eflpp.log FAILED PACKAGE: elapse=20 COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/elapse.log FAILED PACKAGE: elation=20 COMMAND: make -j 2=20 BUILD LOG: http://download.enlightenment.org/tests/logs/elation.log FAILED PACKAGE: envision=20 COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/envision.log FAILED PACKAGE: epdf=20 COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/epdf.log FAILED PACKAGE: e_phys=20 COMMAND: ./bootstrap=20 BUILD LOG: http://download.enlightenment.org/tests/logs/e_phys.log FAILED PACKAGE: Evas_Perl=20 COMMAND: make -j 2=20 BUILD LOG: http://download.enlightenment.org/tests/logs/Evas_Perl.log FAILED PACKAGE: evolve=20 COMMAND: make -j 2=20 BUILD LOG: http://download.enlightenment.org/tests/logs/evolve.log FAILED PACKAGE: express=20 COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/express.log FAILED PACKAGE: feh=20 COMMAND: make -j 2=20 BUILD LOG: http://download.enlightenment.org/tests/logs/feh.log=20 FAILED PACKAGE: iconbar=20 COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/iconbar.log FAILED PACKAGE: imlib2_tools=20 COMMAND: make -j 2=20 BUILD LOG: http://download.enlightenment.org/tests/logs/imlib2_tools.log=20 FAILED PACKAGE: language=20 COMMAND: ./autogen.sh --prefix=3D/home/onefang/nightly/install --cache-file=3D/tmp/easy_e17/easy_e17.cache=20 BUILD LOG: http://download.enlightenment.org/tests/logs/language.log Packages with no supported build system: eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl, Skipped Packages: camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, evoak, gfx_routines, lvs-gui, med, notgame, webcam, Successful Packages: alarm, cpu, deskshow, eclair, ecore, edb, e_dbus, edje_editor, edje, edje_viewer, eet, efreet, elicit, elitaire, e, embryo, emotion, emphasis, empower, emu, engage, engrave, engycad, enhance, enity, enterminus, entice, entrance_edit_gui, entrance, entropy, epeg, ephoto, epsilon, equate, esmart, estickies, etk_extra, etk, etk-perl, e_utils, evas, evfs, ewl, examine, exhibit, exml, expedite, extrackt, flame, forecasts, imlib2_loaders, imlib2, Imlib2_Perl, mail, mem, mixer, moon, net, news, pesh, photo, rage, rain, screenshot, scrot, slideshow, snow, taskbar, tclock, uptime, weather, winselector, wlan, See http://download.enlightenment.org/tests/ for details. |
From: David S. <on...@gm...> - 2007-07-25 02:12:24
Attachments:
signature.asc
|
Once again I had to cut and paste it, still haven't cracked the email to sf.net list problem. Formatting screwed up a bit as a result. A lot of these new failures are due to lack of dependencies on the build box. On Wed, 25 Jul 2007 12:07:32 +1000 David Seikel <on...@gm...> wrote: > FAILED PACKAGE: bling > COMMAND: make -j 2 > BUILD LOG: http://download.enlightenment.org/tests/logs/bling.log I think maybe I should cut this down to the bare minimum, just the link. The name of the failed package is obvious from the link. The failure point is available in the log. |
From: Chady K. <cha...@gm...> - 2007-07-25 06:05:28
|
On 7/25/07, David Seikel <on...@gm...> wrote: > > Once again I had to cut and paste it, still haven't cracked the email > to sf.net list problem. Formatting screwed up a bit as a result. > > A lot of these new failures are due to lack of dependencies on the build > box. > > On Wed, 25 Jul 2007 12:07:32 +1000 David Seikel <on...@gm...> > wrote: > > > FAILED PACKAGE: bling > > COMMAND: make -j 2 > > BUILD LOG: http://download.enlightenment.org/tests/logs/bling.log > > I think maybe I should cut this down to the bare minimum, just the > link. The name of the failed package is obvious from the link. The > failure point is available in the log. Yes, and I also think that the COMMAND is irrelevant in the email log.. maybe it should be something link this for the failed packages: FAILED PACKAGES: bling http://download.enlightenment.org/tests/logs/bling.log edvi http://download.enlightenment.org/tests/logs/edvi.log eflpp http://download.enlightenment.org/tests/logs/eflpp.log elapse http://download.enlightenment.org/tests/logs/elapse.log This way the summary makes it very easy to see what failed, and details are one click away. -- Chady 'Leviathan' Kassouf http://chady.net/ |
From: David S. <on...@gm...> - 2007-07-27 05:07:37
Attachments:
signature.asc
|
Build log for Enlightenment DR 0.17 on 2007-07-26 22:05:20 -0700 Build logs are available at http://download.enlightenment.org/tests/logs Packages that failed to build: bling http://download.enlightenment.org/tests/logs/bling.log edvi http://download.enlightenment.org/tests/logs/edvi.log eflpp http://download.enlightenment.org/tests/logs/eflpp.log elapse http://download.enlightenment.org/tests/logs/elapse.log elation http://download.enlightenment.org/tests/logs/elation.log envision http://download.enlightenment.org/tests/logs/envision.log epdf http://download.enlightenment.org/tests/logs/epdf.log e_phys http://download.enlightenment.org/tests/logs/e_phys.log Evas_Perl http://download.enlightenment.org/tests/logs/Evas_Perl.log evolve http://download.enlightenment.org/tests/logs/evolve.log express http://download.enlightenment.org/tests/logs/express.log feh http://download.enlightenment.org/tests/logs/feh.log iconbar http://download.enlightenment.org/tests/logs/iconbar.log imlib2_tools http://download.enlightenment.org/tests/logs/imlib2_tools.log language http://download.enlightenment.org/tests/logs/language.log Packages with no supported build system: eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl,=20 Packages skipped: camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, evoak, gfx_routines, lvs-gui, med, notgame, webcam,=20 Packages that build OK: alarm, cpu, deskshow, eclair, ecore, edb, e_dbus, edje_editor, edje, edje_viewer, eet, efreet, elicit, elitaire, e, embryo, emotion, emphasis, empower, emu, engage, engrave, engycad, enhance, enity, enterminus, entice, entrance_edit_gui, entrance, entropy, epeg, ephoto, epsilon, equate, esmart, estickies, etk_extra, etk, etk-perl, e_utils, evas, evfs, ewl, examine, exhibit, exml, expedite, extrackt, flame, forecasts, imlib2_loaders, imlib2, Imlib2_Perl, mail, mem, mixer, moon, net, news, pesh, photo, rage, rain, screenshot, scrot, slideshow, snow, taskbar, tclock, uptime, weather, winselector, wlan,=20 Debian GNU/Linux 4.0 \n \l Linux enlightenment2 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux Autoconf version 2.13 automake (GNU automake) 1.10 ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 22:14:06) gettext (GNU gettext-runtime) 0.16.1 See http://download.enlightenment.org/tests/ for details. |
From: Nightly b. s. <on...@gm...> - 2007-07-27 11:55:14
|
Build log for Enlightenment DR 0.17 on 2007-07-27 04:53:01 -0700 Build logs are available at http://download.enlightenment.org/tests/logs Packages that failed to build: Packages with no supported build system: Packages skipped: Packages that build OK: Debian GNU/Linux 4.0 \n \l Linux enlightenment2 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux Autoconf version 2.13 automake (GNU automake) 1.10 ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 22:14:06) gettext (GNU gettext-runtime) 0.16.1 See http://download.enlightenment.org/tests/ for details. |
From: David S. <on...@gm...> - 2007-07-27 11:58:38
Attachments:
signature.asc
|
Ignore this, it was a test. |
From: Nightly b. s. <on...@gm...> - 2007-07-27 14:57:05
|
Build log for Enlightenment DR 0.17 on 2007-07-27 07:55:55 -0700 Build logs are available at http://download.enlightenment.org/tests/logs Packages that failed to build: bling http://download.enlightenment.org/tests/logs/bling.log edvi http://download.enlightenment.org/tests/logs/edvi.log eflpp http://download.enlightenment.org/tests/logs/eflpp.log elapse http://download.enlightenment.org/tests/logs/elapse.log elation http://download.enlightenment.org/tests/logs/elation.log envision http://download.enlightenment.org/tests/logs/envision.log epdf http://download.enlightenment.org/tests/logs/epdf.log Evas_Perl http://download.enlightenment.org/tests/logs/Evas_Perl.log evolve http://download.enlightenment.org/tests/logs/evolve.log express http://download.enlightenment.org/tests/logs/express.log feh http://download.enlightenment.org/tests/logs/feh.log iconbar http://download.enlightenment.org/tests/logs/iconbar.log imlib2_tools http://download.enlightenment.org/tests/logs/imlib2_tools.log language http://download.enlightenment.org/tests/logs/language.log Packages with no supported build system: eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl, Packages skipped: camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, evoak, gfx_routines, lvs-gui, med, notgame, webcam, Packages that build OK: alarm, cpu, deskshow, eclair, ecore, edb, e_dbus, edje_editor, edje, edje_viewer, eet, efreet, elicit, elitaire, e, embryo, emotion, emphasis, empower, emu, engage, engrave, engycad, enhance, enity, enterminus, entice, entrance_edit_gui, entrance, entropy, epeg, ephoto, e_phys, epsilon, equate, esmart, estickies, etk_extra, etk, etk-perl, e_utils, evas, evfs, ewl, examine, exhibit, exml, expedite, extrackt, flame, forecasts, imlib2_loaders, imlib2, Imlib2_Perl, mail, mem, mixer, moon, net, news, pesh, photo, rage, rain, screenshot, scrot, slideshow, snow, taskbar, tclock, uptime, weather, winselector, wlan, Debian GNU/Linux 4.0 \n \l Linux enlightenment2 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux Autoconf version 2.13 automake (GNU automake) 1.10 ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 22:14:06) gettext (GNU gettext-runtime) 0.16.1 See http://download.enlightenment.org/tests/ for details. |
From: Chady K. <cha...@gm...> - 2007-07-27 15:00:37
|
One request, Dunno if others agree too, but isn't it good to have the date in the subject of the email? gmail for one merges all these emails into one conversation, which makes it hard later on to find a certain build log. On 7/27/07, Nightly build system <on...@gm...> wrote: > > Build log for Enlightenment DR 0.17 on 2007-07-27 07:55:55 -0700 > Build logs are available at http://download.enlightenment.org/tests/logs > > Packages that failed to build: > bling http://download.enlightenment.org/tests/logs/bling.log > edvi http://download.enlightenment.org/tests/logs/edvi.log > eflpp http://download.enlightenment.org/tests/logs/eflpp.log > elapse http://download.enlightenment.org/tests/logs/elapse.log > elation http://download.enlightenment.org/tests/logs/elation.log > envision http://download.enlightenment.org/tests/logs/envision.log > epdf http://download.enlightenment.org/tests/logs/epdf.log > Evas_Perl http://download.enlightenment.org/tests/logs/Evas_Perl.log > evolve http://download.enlightenment.org/tests/logs/evolve.log > express http://download.enlightenment.org/tests/logs/express.log > feh http://download.enlightenment.org/tests/logs/feh.log > iconbar http://download.enlightenment.org/tests/logs/iconbar.log > imlib2_tools > http://download.enlightenment.org/tests/logs/imlib2_tools.log > language http://download.enlightenment.org/tests/logs/language.log > > Packages with no supported build system: > eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl, > > Packages skipped: > camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, > evoak, > gfx_routines, lvs-gui, med, notgame, webcam, > > Packages that build OK: > alarm, cpu, deskshow, eclair, ecore, edb, e_dbus, edje_editor, edje, > edje_viewer, > eet, efreet, elicit, elitaire, e, embryo, emotion, emphasis, empower, emu, > engage, engrave, engycad, enhance, enity, enterminus, entice, > entrance_edit_gui, > entrance, entropy, epeg, ephoto, e_phys, epsilon, equate, esmart, > estickies, > etk_extra, etk, etk-perl, e_utils, evas, evfs, ewl, examine, exhibit, > exml, > expedite, extrackt, flame, forecasts, imlib2_loaders, imlib2, Imlib2_Perl, > mail, mem, mixer, moon, net, news, pesh, photo, rage, rain, screenshot, > scrot, slideshow, snow, taskbar, tclock, uptime, weather, winselector, > wlan, > > > Debian GNU/Linux 4.0 \n \l > > Linux enlightenment2 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 > GNU/Linux > > Autoconf version 2.13 > automake (GNU automake) 1.10 > ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 > 22:14:06) > gettext (GNU gettext-runtime) 0.16.1 > > See http://download.enlightenment.org/tests/ for details. > > > ------------------------------------------------------------------------- > 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 > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Chady 'Leviathan' Kassouf http://chady.net/ |
From: David S. <on...@gm...> - 2007-07-27 15:23:32
Attachments:
signature.asc
|
On Fri, 27 Jul 2007 18:00:34 +0300 "Chady Kassouf" <cha...@gm...> wrote: > Dunno if others agree too, but isn't it good to have the date in the > subject of the email? > gmail for one merges all these emails into one conversation, which > makes it hard later on to find a certain build log. Couldn't hurt. Done. |
From: Koen K. <ko...@do...> - 2007-07-27 15:02:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nightly build system schreef: > Build log for Enlightenment DR 0.17 on 2007-07-27 07:55:55 -0700 > Build logs are available at http://download.enlightenment.org/tests/logs > > Packages that failed to build: > epdf http://download.enlightenment.org/tests/logs/epdf.log checking for EPDF... configure: error: Package requirements (poppler >= 0.5.9 evas >= 0.9.9 ecore >= 0.9.9) were not met: No package 'poppler' found It looks like the buildhost needs to install the 0.6.0rc of poppler. regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGqgj8MkyGM64RGpERAhkwAJ0eIIU+1ZimDl9pcfgtqjBY8S3w1wCcDEYW culMtDfvEMoK7v9DsIbktX0= =anau -----END PGP SIGNATURE----- |
From: David S. <on...@gm...> - 2007-07-27 15:21:17
Attachments:
signature.asc
|
On Fri, 27 Jul 2007 17:02:20 +0200 Koen Kooi <ko...@do...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Nightly build system schreef: > > Build log for Enlightenment DR 0.17 on 2007-07-27 07:55:55 -0700 > > Build logs are available at > > http://download.enlightenment.org/tests/logs > >=20 > > Packages that failed to build: >=20 > > epdf http://download.enlightenment.org/tests/logs/epdf.log >=20 > checking for EPDF... configure: error: Package requirements (poppler > >=3D 0.5.9 evas >=3D 0.9.9 ecore >=3D 0.9.9) were not met: >=20 > No package 'poppler' found >=20 > It looks like the buildhost needs to install the 0.6.0rc of poppler. I know that, several other packages also failed due to missing dependencies. At the moment I only installed things that could be found in the debian repos that e2.enlightenment.org has configured. I don't want to go and mess with the E web server by installing random tarballs or cvs snapshots. |
From: Carsten H. (T. R. <ra...@ra...> - 2007-07-28 01:16:59
|
On Sat, 28 Jul 2007 01:21:04 +1000 David Seikel <on...@gm...> babbled: it does have poppler - just the version is too old. that is a direct bi-product of us being conservative for the server(s) and running debian stable. > On Fri, 27 Jul 2007 17:02:20 +0200 Koen Kooi > <ko...@do...> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Nightly build system schreef: > > > Build log for Enlightenment DR 0.17 on 2007-07-27 07:55:55 -0700 > > > Build logs are available at > > > http://download.enlightenment.org/tests/logs > > > > > > Packages that failed to build: > > > > > epdf http://download.enlightenment.org/tests/logs/epdf.log > > > > checking for EPDF... configure: error: Package requirements (poppler > > >= 0.5.9 evas >= 0.9.9 ecore >= 0.9.9) were not met: > > > > No package 'poppler' found > > > > It looks like the buildhost needs to install the 0.6.0rc of poppler. > > I know that, several other packages also failed due to missing > dependencies. At the moment I only installed things that could be > found in the debian repos that e2.enlightenment.org has configured. I > don't want to go and mess with the E web server by installing random > tarballs or cvs snapshots. > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 Tokyo, Japan (東京 日本) |
From: David S. <on...@gm...> - 2007-07-28 01:50:19
Attachments:
signature.asc
|
On Sat, 28 Jul 2007 10:09:46 +0900 Carsten Haitzler (The Rasterman) <ra...@ra...> wrote: > On Sat, 28 Jul 2007 01:21:04 +1000 David Seikel <on...@gm...> > babbled: >=20 > > On Fri, 27 Jul 2007 17:02:20 +0200 Koen Kooi > > <ko...@do...> wrote: > >=20 > > >=20 > > > Nightly build system schreef: > > > > Build log for Enlightenment DR 0.17 on 2007-07-27 07:55:55 -0700 > > > > Build logs are available at > > > > http://download.enlightenment.org/tests/logs > > > >=20 > > > > Packages that failed to build: > > >=20 > > > > epdf http://download.enlightenment.org/tests/logs/epdf.log > > >=20 > > > checking for EPDF... configure: error: Package requirements > > > (poppler > > > >=3D 0.5.9 evas >=3D 0.9.9 ecore >=3D 0.9.9) were not met: > > >=20 > > > No package 'poppler' found > > >=20 > > > It looks like the buildhost needs to install the 0.6.0rc of > > > poppler. > >=20 > > I know that, several other packages also failed due to missing > > dependencies. At the moment I only installed things that could be > > found in the debian repos that e2.enlightenment.org has > > configured. I don't want to go and mess with the E web server by > > installing random tarballs or cvs snapshots. >=20 > it does have poppler - just the version is too old. that is a direct > bi-product of us being conservative for the server(s) and running > debian stable. Stability and conservatism is good when running a public facing server. So the real question is, does epdf really need the latest, bleeding edge, release candidate of poppler? Is the API of poppler so unstable that older versions wont work? Should I add epdf to the skip list as "always requires bleeding edge version of poppler"? |
From: <vt...@un...> - 2007-07-28 05:43:31
|
Quoting David Seikel <on...@gm...>: > So the real question is, does epdf really need the latest, bleeding > edge, release candidate of poppler? Is the API of poppler so > unstable that older versions wont work? Should I add epdf to the skip > list as "always requires bleeding edge version of poppler"? I can add support for older versions of poppler, if this can help. Vincent ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Koen K. <ko...@do...> - 2007-07-28 07:08:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 vt...@un... schreef: > Quoting David Seikel <on...@gm...>: > >> So the real question is, does epdf really need the latest, bleeding >> edge, release candidate of poppler? Is the API of poppler so >> unstable that older versions wont work? Should I add epdf to the skip >> list as "always requires bleeding edge version of poppler"? > > I can add support for older versions of poppler, if this can help. That would be great! In out buildsystem (openembedded) epdf is the only app that can handle the new api other apps (e.g evince, epdfview, abiword) can't :( regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGquttMkyGM64RGpERAmCPAJ9r6p4x5SZhSxx4McOF1KEIXXHZ2QCdGoWB ZFmlEXyDrynboheR+3EQa/A= =KfuZ -----END PGP SIGNATURE----- |
From: Koen K. <ko...@do...> - 2007-07-28 07:21:08
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Seikel schreef: > On Sat, 28 Jul 2007 10:09:46 +0900 Carsten Haitzler (The Rasterman) > <ra...@ra...> wrote: >> it does have poppler - just the version is too old. that is a direct >> bi-product of us being conservative for the server(s) and running >> debian stable. > > Stability and conservatism is good when running a public facing server. Fire up debootstrap and make a chroot? regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGqu5MMkyGM64RGpERAgkjAJoDVwdv7n0oMFC9wM/5PrL7RCeLWACeI0V/ WQPaE2c3Haxq92I/FuVlufc= =lVbt -----END PGP SIGNATURE----- |
From: Sebastian D. <seb...@ta...> - 2007-07-27 16:14:47
|
> Packages skipped: > camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox, evoak, > gfx_routines, lvs-gui, med, notgame, webcam, embrace should build again. As it is a nice standalone mail-checker, I see no reason not to have it working. Sebastian |
From: David S. <on...@gm...> - 2007-07-27 23:03:39
Attachments:
signature.asc
|
On Fri, 27 Jul 2007 18:14:38 +0200 Sebastian Dransfeld <seb...@ta...> wrote: > > Packages skipped: > > camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, > > etox, evoak, gfx_routines, lvs-gui, med, notgame, webcam,=20 >=20 > embrace should build again. As it is a nice standalone mail-checker, > I see no reason not to have it working. Embrace has been taken off the skip list. |
From: Sebastian D. <seb...@ta...> - 2007-07-27 16:23:54
|
And, BTW, shouldn't the build script also do 'make distcheck'? Sebastian |
From: David S. <on...@gm...> - 2007-07-27 23:08:21
Attachments:
signature.asc
|
On Fri, 27 Jul 2007 18:23:47 +0200 Sebastian Dransfeld <seb...@ta...> wrote: > And, BTW, shouldn't the build script also do 'make distcheck'? Other checks can be added once the basics are taken care of. The basics are almost taken care of. B-) Building test RPM and DEB packages will also help test out more stuff. Turning on more .configure --enable-* things will test more code. There are plenty of things that can be added in the future. |