Re: platforms build hangs at juicing
Hi Riccardo, Am 08.02.2018 um 10:47 schrieb Riccardo Mottola: > you essentially do: > > dam@unstable10x [global]:/home/dam/staging/build-19.Jan.2018 > > PYTHONPATH=~/mgar/pkg/.buildsys/v2 ~/mgar/pkg/.buildsys/v2/bin/checkpkg > --os-releases=SunOS5.10 --catalog-architecture=sparc --catalog-release=unstabl > e libhistory7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz > libreadline_dev-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz > libreadline7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz > readline_stub-7.0,REV=2018.01.19-SunOS5.9-all-CSW.pkg.gz > > on unstable10x > > I do not have "mgar" in my home. Do I miss something, need to install > something? Look for it elsewhere? You can just check out the tree: dam@unstable10x [global]:/home/dam/mgar/pkg/php5/branches/php-5.6.x > svn info ~/mgar Pfad: /home/dam/mgar Wurzelpfad der Arbeitskopie: /home/dam/mgar URL: https://svn.code.sf.net/p/gar/code/csw/mgar Relative URL: ^/csw/mgar Basis des Projektarchivs: https://svn.code.sf.net/p/gar/code UUID des Projektarchivs: d3b55034-1cff-0310-a425-aefe953e1e90 Revision: 25550 Knotentyp: Verzeichnis Plan: normal Letzter Autor: dmichelsen Letzte geänderte Rev: 25550 Letztes Änderungsdatum: 2016-02-05 18:04:31 +0100 (Fr, 05. Feb 2016) svn co https://svn.code.sf.net/p/gar/code/csw/mgar > I hope you fix the issue soon, so everything becomes smooth again. I am pretty sure that the issue will not be fixed any more - I can’t patch the farm without raising the buildlevel and Solaris 10 is out of support. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
Re: platforms build hangs at juicing
Hi Dago, you essentially do: dam@unstable10x [global]:/home/dam/staging/build-19.Jan.2018 > PYTHONPATH=~/mgar/pkg/.buildsys/v2 ~/mgar/pkg/.buildsys/v2/bin/checkpkg --os-releases=SunOS5.10 --catalog-architecture=sparc --catalog-release=unstabl e libhistory7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz libreadline_dev-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz libreadline7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz readline_stub-7.0,REV=2018.01.19-SunOS5.9-all-CSW.pkg.gz on unstable10x I do not have "mgar" in my home. Do I miss something, need to install something? Look for it elsewhere? Sorry for the stupid question! I hope you fix the issue soon, so everything becomes smooth again. Riccardo
Re: platforms build hangs at juicing
Hi Riccardo, > Am 30.01.2018 um 18:34 schrieb Riccardo Mottola via maintainers >: > > Hi, > > On 2018-01-30 16:19:26 +0100 Dagobert Michelsen via maintainers > wrote: > >> Hi, >> this is an issue with the wrapper for the Solaris 9 brand where fork hangs. >> I have not identified the issue yet. For starters you can build the packages > > Once such a similar issue happened due to a bad openssh upgrade, do you > remember? > >> individually and check the package for Solaris 9 Sparc on Solaris 10 by > > I built them on all 4 platforms with success, that's a thing at least, "mgar > package" worked, so I have them.. could I just upload them_ > >> invoking >> checkpkg manually. > > there is no checkpkg executable... It works like this: dam@unstable10x [global]:/home/dam/staging/build-19.Jan.2018 > ls -l Gesamt 2316 -rw-r--r-- 1 dam csw56170 Jan 19 14:58 libhistory7-7.0,REV=2018.01.19-SunOS5.10-sparc-UNCOMMITTED.pkg.gz -rw-r--r-- 1 dam csw56504 Jan 19 15:08 libhistory7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz -rw-r--r-- 1 dam csw 211834 Jan 19 14:58 libreadline_dev-7.0,REV=2018.01.19-SunOS5.10-sparc-UNCOMMITTED.pkg.gz -rw-r--r-- 1 dam csw 191679 Jan 19 15:08 libreadline_dev-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz -rw-r--r-- 1 dam csw 296463 Jan 19 14:58 libreadline7-7.0,REV=2018.01.19-SunOS5.10-sparc-UNCOMMITTED.pkg.gz -rw-r--r-- 1 dam csw 297283 Jan 19 15:08 libreadline7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz -rw-r--r-- 1 dam csw13383 Jan 19 14:58 readline_stub-7.0,REV=2018.01.19-SunOS5.10-all-UNCOMMITTED.pkg.gz -rw-r--r-- 1 dam csw13372 Jan 19 15:08 readline_stub-7.0,REV=2018.01.19-SunOS5.9-all-CSW.pkg.gz dam@unstable10x [global]:/home/dam/staging/build-19.Jan.2018 > PYTHONPATH=~/mgar/pkg/.buildsys/v2 ~/mgar/pkg/.buildsys/v2/bin/checkpkg --os-releases=SunOS5.10 --catalog-architecture=sparc --catalog-release=unstabl e libhistory7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz libreadline_dev-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz libreadline7-7.0,REV=2018.01.19-SunOS5.9-sparc-CSW.pkg.gz readline_stub-7.0,REV=2018.01.19-SunOS5.9-all-CSW.pkg.gz INFO 2018-01-31 15:35:54,936 package_stats.py:132 Juicing the svr4 package stream files... 100% Time: 0:00:05 |#| INFO 2018-01-31 15:36:02,788 checkpkg_lib.py:263 Unwrapping candies... 100% |###| INFO 2018-01-31 15:36:02,924 checkpkg_lib.py:878 Tasting candies one by one... 100% |###| INFO 2018-01-31 15:36:03,775 checkpkg_lib.py:914 Tasting them all at once... INFO 2018-01-31 15:36:10,215 checkpkg_lib.py:305 Stuffing the candies under the pillow... 100% |###| CSWlibreadline7: CSWreadline: * Dependency issues of CSWlibreadline7: * CSWlibncurses5 is needed by CSWlibreadline7, because: * - opt/csw/lib/libreadline.so.7 needs the libncurses.so.5 soname * - opt/csw/lib/sparcv9/libreadline.so.7 needs the libncurses.so.5 soname * RUNTIME_DEP_PKGS_CSWlibreadline7 += CSWlibncurses5 * If you don't know of any reasons to include these dependencies, you might remove them: * ? CSWlibncurses6 * Dependency issues of CSWreadline: * If you don't know of any reasons to include these dependencies, you might remove them: * ? CSWlibhistory5 * ? CSWlibreadline5 # Checkpkg suggests adding the following lines to the GAR recipe: # This is a summary; see above for details. RUNTIME_DEP_PKGS_CSWlibreadline7 += CSWlibncurses5 If any of the reported errors were false positives, you can override them pasting the lines below to the GAR recipe. CHECKPKG_OVERRIDES_CSWlibreadline7 += surplus-dependency|CSWlibncurses6 CHECKPKG_OVERRIDES_CSWlibreadline7 += missing-dependency|CSWlibncurses5 Do not copy/paste these overrides without thinking! If you're not sure, scroll up and read the details. If you're still not sure, go to the wiki and read about the error tags you see, or ask on the maintainers@ mailing list. http://wiki.opencsw.org/checkpkg-error-tags WARNING: Some overrides did not match any errors. They can probably be removed, as they don't take any effect anyway.
Re: platforms build hangs at juicing
Hi, On 2018-01-30 16:19:26 +0100 Dagobert Michelsen via maintainerswrote: Hi, this is an issue with the wrapper for the Solaris 9 brand where fork hangs. I have not identified the issue yet. For starters you can build the packages Once such a similar issue happened due to a bad openssh upgrade, do you remember? individually and check the package for Solaris 9 Sparc on Solaris 10 by I built them on all 4 platforms with success, that's a thing at least, "mgar package" worked, so I have them.. could I just upload them_ invoking checkpkg manually. there is no checkpkg executable... Riccardo
Re: platforms build hangs at juicing
Hi, this is an issue with the wrapper for the Solaris 9 brand where fork hangs. I have not identified the issue yet. For starters you can build the packages individually and check the package for Solaris 9 Sparc on Solaris 10 by invoking checkpkg manually. Best regards — Dago > Am 30.01.2018 um 15:51 schrieb Jan Holzhueter via maintainers >: > > Could be that the packagedb rest interface was hung. > Restartete the apache. > try again. > > Am 30.01.18 um 15:39 schrieb Riccardo Mottola via maintainers: >> Hi all! >> >> I wanted to rebuild all the GNUstep packages with the fresh releases. >> >> I started with gnustep-make of course, but when sparc 9 finishes >> >> /home/rmottola/spool.5.9-sparc/CSWgnustep-make/install/checkpkg_override >> /home/rmottola/spool.5.9-sparc/CSWgnustep-make/install/copyright >> /home/rmottola/spool.5.9-sparc/CSWgnustep-make/install/depend >> ## Validating control scripts. >> ## Packaging complete. >> mkp: exec( pkgtrans -s /home/rmottola/spool.5.9-sparc >> /tmp/gnustep_make-2.7.0,REV=2018.01.30-SunOS5.9-sparc-CSW.pkg >> CSWgnustep-make ) >> Transferring package instance >> mkp: exec( gzip -9 -f >> /tmp/gnustep_make-2.7.0,REV=2018.01.30-SunOS5.9-sparc-CSW.pkg ) >> mkp: exec( mv >> /tmp/gnustep_make-2.7.0,REV=2018.01.30-SunOS5.9-sparc-CSW.pkg.gz >> /home/rmottola/pkgs ) >> mkp: exec( rm -rf /home/rmottola/spool.5.9-sparc/CSWgnustep-make ) >> INFO 2018-01-30 15:12:39,203 package_stats.py:132 Juicing the svr4 >> package stream files... >> 0% ETA: --:--:-- | >>| >> >> and just sits there for undefined time! Is this a package issue or an >> infrastructure issue? >> I am going to build the packages one by one on all 4 unstable machines >> and see what happens. >> >> Riccardo >> > -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
Re: platforms build hangs at juicing
Could be that the packagedb rest interface was hung. Restartete the apache. try again. Am 30.01.18 um 15:39 schrieb Riccardo Mottola via maintainers: > Hi all! > > I wanted to rebuild all the GNUstep packages with the fresh releases. > > I started with gnustep-make of course, but when sparc 9 finishes > > /home/rmottola/spool.5.9-sparc/CSWgnustep-make/install/checkpkg_override > /home/rmottola/spool.5.9-sparc/CSWgnustep-make/install/copyright > /home/rmottola/spool.5.9-sparc/CSWgnustep-make/install/depend > ## Validating control scripts. > ## Packaging complete. > mkp: exec( pkgtrans -s /home/rmottola/spool.5.9-sparc > /tmp/gnustep_make-2.7.0,REV=2018.01.30-SunOS5.9-sparc-CSW.pkg > CSWgnustep-make ) > Transferring package instance > mkp: exec( gzip -9 -f > /tmp/gnustep_make-2.7.0,REV=2018.01.30-SunOS5.9-sparc-CSW.pkg ) > mkp: exec( mv > /tmp/gnustep_make-2.7.0,REV=2018.01.30-SunOS5.9-sparc-CSW.pkg.gz > /home/rmottola/pkgs ) > mkp: exec( rm -rf /home/rmottola/spool.5.9-sparc/CSWgnustep-make ) > INFO 2018-01-30 15:12:39,203 package_stats.py:132 Juicing the svr4 > package stream files... > 0% ETA: --:--:-- | > | > > and just sits there for undefined time! Is this a package issue or an > infrastructure issue? > I am going to build the packages one by one on all 4 unstable machines > and see what happens. > > Riccardo >