Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Tue, Jan 3, 2012 at 11:00 PM, peter green plugw...@p10link.net wrote: armhf has now pretty much cleared the needs-build queue (the only things left are non-free stuff and recently added stuff) and has built arround 89% of the archive (placing it between kfreebsd and ia64) with about 99.5% up to date (placing it between amd64 and i386). Would now be a good time to begin inclusion in testing? It seems that currently no buildds build packages for experimental. Is that correct? Is there a plan/timeline for this? -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJ0cceYhNE13EwZ=ijmyebzebhbgjjv-c917w7pbkm2oj9c...@mail.gmail.com
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Mon, 09, Jan, 2012 at 10:10:57AM +0100, Reinhard Tartler spoke thus.. On Tue, Jan 3, 2012 at 11:00 PM, peter green plugw...@p10link.net wrote: armhf has now pretty much cleared the needs-build queue (the only things left are non-free stuff and recently added stuff) and has built arround 89% of the archive (placing it between kfreebsd and ia64) with about 99.5% up to date (placing it between amd64 and i386). Would now be a good time to begin inclusion in testing? It seems that currently no buildds build packages for experimental. Is that correct? Is there a plan/timeline for this? Yes - it'll be sorted soon once all of the buildds are using autosigning. Mark -- Mark Hymers mhy at debian dot org Oh, this is John Reid who is 'Cabinet Bruiser' which just means that he's a bit squat, ugly and unpleasant and therefore gets to be called a 'Bruiser'. Jeremy Hardy, The News Quiz -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120109114713.ga13...@hymers.org.uk
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Sun, 2012-01-08 at 05:04 +, peter green wrote: An initial push of packages to testing occurred with tonight's britney run. There's a certain amount of uninstallability and loads of missing packages still, but it's a start :) I guess the next step is to try and get it to the point where it is bootstrapable. [...] So lets try to follow the trail of why armhf bash isn't in. [...] And it seems that openldap is being held out of testing by testsuite failures on kfreebsd (654824) :( Yes, there's still a bunch of work to be done. Some of it will be port-specific, some of it more general like trying to get issues in various packages resolved so that we can unblock migrations from unstable. Regards, Adam -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1326094992.13341.26.ca...@jacala.jungle.funky-badger.org
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Tue, 2012-01-03 at 22:54 +, Adam D. Barratt wrote: I had been planning on having a look at the situation for both armhf and s390x over the period between Christmas and New Year, but for a variety of reasons that never happened. It's still on my short-term to-do list; it's not quite as simple as just adding the relevant entries to the configuration file, sadly, or we'd have done it already. :-) An initial push of packages to testing occurred with tonight's britney run. There's a certain amount of uninstallability and loads of missing packages still, but it's a start :) Note that this doesn't make armhf a release architecture at this point, and port-specific bugs are still not RC. Regards, Adam -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1325977482.13341.11.ca...@jacala.jungle.funky-badger.org
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
An initial push of packages to testing occurred with tonight's britney run. There's a certain amount of uninstallability and loads of missing packages still, but it's a start :) I guess the next step is to try and get it to the point where it is bootstrapable. When I tried to bootstrap it I got a failure on being unable to find mount. On trying to enter the resulting chroot I noticed bash was missing. On checking Whether bash was in the packages file or not I found it was not. So lets try to follow the trail of why armhf bash isn't in. It seems bash isn't in because bash-static depends on passwd (source package shadow) It seems shadow isn't in because login and passwd depend on libpam-modules (source package pam) It seems pam isn't in because libpam-modules and libpam-cracklib depend on libdb5.1 (source package db) It seems db isn't in because the source versions in testing and unstable are different. It seems the source versions of db in testing an unstable are different because jcristau put a block on it It seems that jcristau blocked it because of waiting for the fix for 651333 (source package openldap) And it seems that openldap is being held out of testing by testsuite failures on kfreebsd (654824) :( Note that this doesn't make armhf a release architecture at this point, and port-specific bugs are still not RC. Regards, Adam -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0923c7.3060...@p10link.net
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Wed, Jan 4, 2012 at 12:24 AM, peter green plugw...@p10link.net wrote: Luke Kenneth Casson Leighton wrote: On Tue, Jan 3, 2012 at 10:54 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: (fwiw, the not-yet-built list includes webkit and ruby1.9.1, each of which have a number of other packages directly or indirectly stuck behind them). ahh... webkit. do you have a system anywhere that has 2gb of RAM? if not, i strongly strongly advise skipping the debug builds on any webkit library. as webkit is mostly c++ and as pretty much everything goes into one massive library with hundreds of object files that are very closely inter-dependent, linking the library requires a whopping 1.5gb of *resident* memory in order to complete within a reasonable amount of time. anything outside of that - even by a marginal amount - will result in the build machine absolutely thrashing its nuts off. 1gb is not enough (tried it...). 1.5gb will not be enough. 2gb is the bare minimum for the link stage Well anthiel built the armel webkit package (including debug packages) successfully and according to the machines database it only has 1.5Gb of ram. OTOH the build DID take 33 hours. :) 90% of that will have been absolute thrashing the nuts off the hard drive during the link phase. increase that RAM to a mere 2gb and it'll drop drastically to about 3 hours, with the link phase taking only about... *guesses* 20 mins instead of 30 hours. Furthermore the failure on armhf didn't look like a timeout to me, the error was ERROR: can't resolve libraries to shared libraries: javascriptcoregtk-3.0, webkitgtk-3.0. hmmm... those are internal libraries which are private to webkit. they get linked into libwebkitXYZgtk-N.N which is the public library but the symbols in those two libraries must *not* be made publicly accessible (nor the header files made available either). so if the build tries to do anything fancy/special by moving those out of the location they're supposed to be in to stop them being public... just speculation but something to watch out for. l. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPweEDzo3M8rW-qfJT4Peuj_r0p=+M7W+eDc=_yqsh9q7ak...@mail.gmail.com
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
Luke Kenneth Casson Leighton wrote: [...] ahh... webkit. do you have a system anywhere that has 2gb of RAM? if not, i strongly strongly advise skipping the debug builds on any webkit library. I'm running the prerelease Ubuntu precise on armhf. They have built webkit, but it just plain doesn't work: any web browser which uses it gets most of the way through rendering a page and then exits silently. It *looks* suspiciously like the glib incompatibility described on the Midori FAQ page here: http://wiki.xfce.org/midori/faq ...but of course the current glib version is much more recent that the ones mentioned. I have no idea if any of this is relevant to Debian. -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─ http://www.cowlark.com ─ │ I have always wished for my computer to be as easy to use as my │ telephone; my wish has come true because I can no longer figure out │ how to use my telephone. --- Bjarne Stroustrup signature.asc Description: OpenPGP digital signature
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Wed, Jan 4, 2012 at 11:55 AM, David Given d...@cowlark.com wrote: Luke Kenneth Casson Leighton wrote: [...] ahh... webkit. do you have a system anywhere that has 2gb of RAM? if not, i strongly strongly advise skipping the debug builds on any webkit library. I'm running the prerelease Ubuntu precise on armhf. They have built webkit, but it just plain doesn't work: any web browser which uses it gets most of the way through rendering a page and then exits silently. yeah you reallly have to use the builds that xan - carefully and painstakingly - puts together, tests etc. for midori ohh yeah that's webkitgtk-based - yeah, xan goes to a lot of trouble to specifically patch the version of webkitgtk that he releases, including patches that may not yet have been accepted into webkit but are absolutely essential for stability. It *looks* suspiciously like the glib incompatibility described on the Midori FAQ page here: http://wiki.xfce.org/midori/faq ...but of course the current glib version is much more recent that the ones mentioned. i ran into an issue with libsoup in webkit 18 months ago - they did some improvements that broke things... in webkit [with absolutely no code-changes to webkit]. whoops. had to wait for the patches to make their way through the system. bottom line is: if you can get a set of stake-in-ground libraries from anywhere, bloody well use them, don't arse about: there's too much going on. I have no idea if any of this is relevant to Debian. more than likely :) -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capweedxw2ekqapz4ogpiw+ln5m9umunoax9ksv8wrxr+jpl...@mail.gmail.com
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
armhf has now pretty much cleared the needs-build queue (the only things left are non-free stuff and recently added stuff) and has built arround 89% of the archive (placing it between kfreebsd and ia64) with about 99.5% up to date (placing it between amd64 and i386). Would now be a good time to begin inclusion in testing? -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f037a89.8000...@p10link.net
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Tue, Jan 3, 2012 at 10:54 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: (fwiw, the not-yet-built list includes webkit and ruby1.9.1, each of which have a number of other packages directly or indirectly stuck behind them). ahh... webkit. do you have a system anywhere that has 2gb of RAM? if not, i strongly strongly advise skipping the debug builds on any webkit library. as webkit is mostly c++ and as pretty much everything goes into one massive library with hundreds of object files that are very closely inter-dependent, linking the library requires a whopping 1.5gb of *resident* memory in order to complete within a reasonable amount of time. anything outside of that - even by a marginal amount - will result in the build machine absolutely thrashing its nuts off. 1gb is not enough (tried it...). 1.5gb will not be enough. 2gb is the bare minimum for the link stage. if you absolutely absolutely must have the debug builds, but there is nowhere in the world any ARM Cortex A8/9 system with 2gb of RAM, i strongly advise you to not mess about, and use cross-compiling. please feel free to entirely ignore this advice however and pursue whatever you wish. l. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capweedy7ptylcrqapy+66eykscp25yjtkhon_sx8kvwjzkf...@mail.gmail.com
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
On Tue, Jan 3, 2012 at 11:04 PM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: anything outside of that - even by a marginal amount - will result in the build machine absolutely thrashing its nuts off. [for anything in excess of 24 hours]. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capweedzkxztvb_ez9nhiao5xdyys3ex7tpmeryxgmbebyqw...@mail.gmail.com
Re: Bug#615513: release.debian.org: armhf inclusion into the archive
Luke Kenneth Casson Leighton wrote: On Tue, Jan 3, 2012 at 10:54 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: (fwiw, the not-yet-built list includes webkit and ruby1.9.1, each of which have a number of other packages directly or indirectly stuck behind them). ahh... webkit. do you have a system anywhere that has 2gb of RAM? if not, i strongly strongly advise skipping the debug builds on any webkit library. as webkit is mostly c++ and as pretty much everything goes into one massive library with hundreds of object files that are very closely inter-dependent, linking the library requires a whopping 1.5gb of *resident* memory in order to complete within a reasonable amount of time. anything outside of that - even by a marginal amount - will result in the build machine absolutely thrashing its nuts off. 1gb is not enough (tried it...). 1.5gb will not be enough. 2gb is the bare minimum for the link stage Well anthiel built the armel webkit package (including debug packages) successfully and according to the machines database it only has 1.5Gb of ram. OTOH the build DID take 33 hours. Furthermore the failure on armhf didn't look like a timeout to me, the error was ERROR: can't resolve libraries to shared libraries: javascriptcoregtk-3.0, webkitgtk-3.0. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f039c4a.7000...@p10link.net
