- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

by Marcus Denker

â¦ report: Move done: http://books.pharo.org http://lectures.pharo.org http://mooc.pharo.org <http://mooc.pharo.org/> https certificates are in creation, too. Ongoing: get files updates get: here the problem is that the files get-files on files.pharo.org <http://files.pharo.org/> uses lots of symbolic links, but with full path (which is different on the new server). We are now fixing these links once, then the script that creates them need to be updated Marcus > On 30 Nov 2017, at 10:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > We are doing the switch now. > >> On 29 Nov 2017, at 16:28, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> We will do the switch to the new server tomorrow, Nov 30. >> >> -> for people downloading, there should be no service intererruption >> -> For *uploaders* (mostly CI jobs), you need new SSH credentials. >> This means some upload jobs might break, but they will be easy >> to fix >> -> Uploading humans (people that scp to files.pharo.org <http://files.pharo.org/>): Talk to Christoph or me. >> >> Marcus >

Nov. 30, 2017

Re: [Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

by Marcus Denker

We are doing the switch now. > On 29 Nov 2017, at 16:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We will do the switch to the new server tomorrow, Nov 30. > > -> for people downloading, there should be no service intererruption > -> For *uploaders* (mostly CI jobs), you need new SSH credentials. > This means some upload jobs might break, but they will be easy > to fix > -> Uploading humans (people that scp to files.pharo.org <http://files.pharo.org/>): Talk to Christoph or me. > > Marcus

Nov. 30, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Eduardo de Oliveira Padoan

I liked the launcher a lot, but It took me a while to get a version working out-of-the-box on Ubuntu. It's not available with the VM on the /download page for Linux. My preferred choice would be the PPA anyway, as I like to keep stuff under APT control, but I had to dig a lot to find a sources.list entry combination that worked: not all packages are available on all repositories, and some old repos have invalid crypto signatures. In the end, what worked was: - Xenial AND Trusty deb http://ppa.launchpad.net/pharo/stable/ubuntu xenial main deb http://ppa.launchpad.net/pharo/stable/ubuntu trusty main deb-src http://ppa.launchpad.net/pharo/stable/ubuntu xenial main deb-src http://ppa.launchpad.net/pharo/stable/ubuntu trusty main - Disabled signatures checking (at my own risk): sudo apt -o Acquire::AllowInsecureRepositories=true \ -o Acquire::AllowDowngradeToInsecureRepositories=true \ update - Finally: sudo apt install pharo-vm-core pharo-launcher But if I try to load a Pharo 5.0 image (created from the launcher's list, marked as beta), I get this on the terminal: "This interpreter (vers. 6505) cannot read image file (vers. 6521)." Pharo 4.0 is the most recent on that list that works, at least that I could find -- there are too many branches under Pharo Jenkins for instance, and I couldn't find a suitable image there. Att, On Wed, Nov 29, 2017 at 5:13 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > demarey wrote > > Maybe it could be related to this bug: > > https://github.com/pharo-project/pharo-launcher/issues/52 > > It is a different bug in the same behavior. > > The easy workaround is to manually create a pharo.version file for the > offending image. > > As to the bugâ¦ > > The immediate problem turned out to be that I had a startup error in > certain > images due to a startup script that only worked in more recent Pharo > versions. So, suggestion #1: check that pharo.version has actually been > created, and if not produce a better error message. Also, ideally there > should probably also be a timeout in determining the image version because > sometimes the process returns without creating the file and other times it > doesn't return at all. > > However, even after disabling the startup scripts, I was only able to > generate pharo.version by replacing > "~/Documents/Pharo/vms/private/6505/Pharo.app" with > "~/Documents/Pharo/vms/30-x86/Pharo.app", so there does also seem to be > something fishy with the 6505 VM > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Nov. 29, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Sean P. DeNigris

demarey wrote > Maybe it could be related to this bug: > https://github.com/pharo-project/pharo-launcher/issues/52 It is a different bug in the same behavior. The easy workaround is to manually create a pharo.version file for the offending image. As to the bugâ¦ The immediate problem turned out to be that I had a startup error in certain images due to a startup script that only worked in more recent Pharo versions. So, suggestion #1: check that pharo.version has actually been created, and if not produce a better error message. Also, ideally there should probably also be a timeout in determining the image version because sometimes the process returns without creating the file and other times it doesn't return at all. However, even after disabling the startup scripts, I was only able to generate pharo.version by replacing "~/Documents/Pharo/vms/private/6505/Pharo.app" with "~/Documents/Pharo/vms/30-x86/Pharo.app", so there does also seem to be something fishy with the 6505 VM ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 29, 2017

Re: [Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

by Nicolas Cellier

Maybe a good occasion to fix opensmalltalk-vm :) i.e. https://ci.appveyor.com/project/OpenSmalltalk/vm/branch/Cog/job/h8la5cg9fi2… /cygdrive/c/projects/vm/deploy/pharo %CYG_ROOT%\bin\bash -lc "cd $APPVEYOR_BUILD_FOLDER/deploy/pharo; exec 0</dev/null; exec ./filter-exec.sh deploy-key.sh" %CYG_ROOT%\bin\bash -lc "cd $APPVEYOR_BUILD_FOLDER; exec 0</dev/null; exec ./deploy/pharo/filter-exec.sh deploy-files.pharo.org.sh" Uploading ./pharo-win-x86_64-201711262336-8879e2e.zip to pharo.files.org//appli/files.pharo.org/vm/pharo-spur64/win Warning: Permanently added the RSA host key for IP address '193.51.193.142' to the list of known hosts. Uploading ./pharo-win-x86_64-201711262336-8879e2e.zip to pharo.files.org//appli/files.pharo.org/vm/pharo-spur64/win/latest.zip scp: /appli/files.pharo.org/vm/pharo-spur64/win/latest.zip: Permission denied Command exited with code 1 2017-11-29 16:28 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > We will do the switch to the new server tomorrow, Nov 30. > > -> for people downloading, there should be no service intererruption > -> For *uploaders* (mostly CI jobs), you need new SSH credentials. > This means some upload jobs might break, but they will be easy > to fix > -> Uploading humans (people that scp to files.pharo.org) Talk to > Christoph or me. > > Marcus >

Nov. 29, 2017

[ANN] files.pharo.org server move tomorrow, Nov 30

by Marcus Denker

Hi, We will do the switch to the new server tomorrow, Nov 30. -> for people downloading, there should be no service intererruption -> For *uploaders* (mostly CI jobs), you need new SSH credentials. This means some upload jobs might break, but they will be easy to fix -> Uploading humans (people that scp to files.pharo.org <http://files.pharo.org/>): Talk to Christoph or me. Marcus

Nov. 29, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Sean P. DeNigris

demarey wrote > Yes, I'm able to run pharo 1.4 images. Hmm, when I tried to launch a 1.4 image, it hung forever while "Determining image version". I interrupted and manually run the command on the terminal: "/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Pharo" --headless "/Users/sean/Dynabook/Working Images/COTDC/COTDC.image" --no-default-preferences eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]" Result = same, command hangs, plus the following output: /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' 2017-11-29 10:08:38.507 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/MiscPrimitivePlugin' 2017-11-29 10:08:38.507 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/LargeIntegers' 2017-11-29 10:08:38.508 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/LargeIntegers' 2017-11-29 10:08:38.508 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/LargeIntegers' 2017-11-29 10:08:38.645 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/MiscPrimitivePlugin' 2017-11-29 10:08:38.653 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/FilePlugin' 2017-11-29 10:08:38.654 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/MiscPrimitivePlugin' 2017-11-29 10:08:38.654 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/MiscPrimitivePlugin' 2017-11-29 10:08:38.654 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/MiscPrimitivePlugin' 2017-11-29 10:08:38.655 Pharo[12375:1203919] *** -[NSPathStore2 stringByAppendingPathExtension:]: cannot append extension 'bundle/Contents/MacOS/' to path '/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Plugins/FilePlugin' I tried again headful and got a Pharo window with all black contents. Here are my system details: Image ----- /Applications/Pharo.app/Contents/Resources/Pharo.image Pharo6.0 Latest update: #60510 Unnamed Virtual Machine --------------- /Applications/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) VMMaker versionString VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 Operating System/Hardware ------------------------- Mac OS 1013.1 intel ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 29, 2017

Re: [Pharo-dev] Iceberg workflow

by Sean P. DeNigris

Ben Coman wrote > That is cool to automate that, but these names seem a bit generic to > take ownership across all domains in random projects. I may have explained poorly. It merely guesses a default value in the repo creation form. One is free to change manually as always if needed. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 29, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Torsten Bergmann

Unfortunately this fix did not work. Details are described in https://github.com/pharo-project/pharo-launcher/issues/55 Meanwhile I fixed it in an own commit: PharoLauncher-Core-TorstenBergmann.146 Launcher is now able to give the filter pattern not as global regex but now specific to the version: self name: 'Pharo 7.0 (development version)' url: 'http://files.pharo.org/image/70/' asZnUrl filterPattern: 'href="(Pharo-7.0.0-alpha.build.[^"]*.zip)"' and it works and filters the alpha version (see screenshot). So anyone who would like to test should give it a try. For sure it can be improved to support also the other images in the future. But at least one can download the standard release for Pharo 7 as it was for Pharo 6. Thx T. > Gesendet: Mittwoch, 29. November 2017 um 09:26 Uhr > Von: "Christophe Demarey" <christophe.demarey(a)inria.fr> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] I love the launcher!!!! > > Hi Torsten, > > I think I have a fix for your problem. I opened an issue fot it: https://github.com/pharo-project/pharo-launcher/issues/55. > Could you confirm if it is ok now? > > > Le 28 nov. 2017 Ã 20:11, Torsten Bergmann <astares(a)gmx.de> a Ã©crit : > > > > Hi, > > > > Launcher is a power tool and has helped many of us so far. Thanks to all who helped moving > > it forward, especially Christophe who is currently caring a lot. > > > > Unfortunately one primary issue is not yet solved: > > > > The downloadable files for Pharo 7 are not correctly displayed (see Screenshot attached). > > > > I guess this is because the image file names have changed (initially the build process was set up > > to include the git hash but now we also have the build number returned again, see [1]) > > > > So with the current Launcher one can not directly load a specific build number for Pharo 7 or see which > > build number is the latest available. So for Pharo 7 it is usable to download "latest", "latest-32" > > or "latest-64" but it is not possible to really distinguish all the "Pharorpackage-7" entries. > > > > It would be really a step forward if this could be fixed somehow and also for Pharo 7 display the > > image build number to make Launcher usable also for contributors to Pharo 7 again. > > > > Thanks > > T. > > > > [1] http://forum.world.st/SystemVersion-cleanup-or-the-return-of-the-explicit-b…<launcher.png> > > >

Nov. 29, 2017

[Pharo 7.0-dev] Build #350: 20782-CompiledCode-misses-an-abstract-sourcePointer-method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #350 was: SUCCESS. The Pull Request #561 was integrated: "20782-CompiledCode-misses-an-abstract-sourcePointer-method" Pull request url: https://github.com/pharo-project/pharo/pull/561 Issue Url: https://pharo.fogbugz.com/f/cases/20782 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 29, 2017