Hi nicolai here is what I do. I always download the latest image via a bash script because updating can fail since loading package without a baseline may break. After I use the set up described by guille blog post and I reuse my downloaded clone (to avoid to trash my SSD). Esteban told me that he will do a video: - for producing a PR - for reviewing Stef On Thu, Aug 31, 2017 at 12:06 AM, Nicolai Hess <[hidden email]> wrote:
|
In reply to this post by Nicolai Hess-3-2
Hi Niolai
thanks for raising this issue. The description should be migrated to Pharo github. Stef On Thu, Aug 31, 2017 at 12:42 AM, Nicolai Hess <[hidden email]> wrote: > > > 2017-08-31 0:28 GMT+02:00 Cyril Ferlicot D. <[hidden email]>: >> >> Le 31/08/2017 à 00:06, Nicolai Hess a écrit : >> > Hi, >> > >> > I am now able to use iceberg on windows, thanks for the help. >> > >> > But I am still a bit unsure about how the review and contribution >> > workflow should work. >> > >> > up to pharo 6 I just load a latest image, >> > - load the slice from a fogbugz number and was able to review the change >> > - or create a slice and upload it to the inbox >> > >> > in pharo 7 >> > - what is the equivalent to "getting the latest image" (and being able >> > to load and review a fix), >> > up to pharo 6 I just >> > - load the latest image in pharolauncher (or from the command line). >> > - opened the inbox repository. >> > - load and review change/fix >> > - throw away this change (close image without save) >> > - reopen that image to move on with the next item to review. >> > >> >> Hi, >> >> I'll not be of a great help here since I only reviewed PR via the github >> interface for now but I know that Guille wrote this guide: >> >> https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-Process >> >> There is a review process discription. > > > Thank you Cyril. > > Do we have a list of links to this and other usefull articles or how did you > know about this article? > > |
In reply to this post by Stephane Ducasse-3
2017-08-31 20:05 GMT+02:00 Stephane Ducasse <[hidden email]>:
Thanks, that would be great. looking forward to it, but for now I think I will quit trying this. It is too frustrating. I can not even try to explore icebergs functionality because it is crashing all the time.
|
I know your feelings. I got a bad time back in July on my mac. Iceberg blew up on me on anything I tried. So I did something else and waited for a better version. On Fri, Sep 1, 2017 at 5:54 PM, Nicolai Hess <[hidden email]> wrote:
|
In reply to this post by Guillermo Polito
2017-08-10 18:20 GMT-03:00 Guillermo Polito <[hidden email]>:
I tested it on Windows with msysgit. First you have to make the git clone $ git clone https://github.com/hernanmd/pharo.git You have to ***let it fail*** ... "fatal: unable to checkout working tree" ... Then $ cd pharo/ $ git config core.longpaths true $ git checkout -f HEAD Checking out files: 100% (107983/107983), done. Your branch is up-to-date with 'origin/development'. |
In reply to this post by Guillermo Polito
This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the Pharo entry. You'll see the option Create new branch from Fogbugz issue." Because there is no such "Pharo" option in the menu. See the attached screenshot.Did I miss something? Any suggestion?2017-08-10 12:17 GMT-03:00 Guillermo Polito <[hidden email]>:
Clipboard01.png (101K) Download Attachment |
which Pharo version (and Iceberg version) do you have?
Esteban
|
2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <[hidden email]>:
|
I don't see any easy way to find the Iceberg version. Should I update Iceberg using this script also in Pharo 7?"Restore defaults" Iceberg enableMetacelloIntegration: false. MetacelloPharo30Platform select. "Update metacello" Metacello new baseline: 'Metacello'; repository: 'github://metacello/metacello:Pharo6.1/repository'; onConflict: [:e | e useIncoming ]; get; load. "Update iceberg" #( 'Iceberg-UI' 'Iceberg-Plugin-GitHub' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' 'Iceberg-Libgit-Tonel' 'Iceberg-Libgit-Filetree' 'Iceberg-Libgit' 'Iceberg' 'LibGit-Core') do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ]. Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v0.6'; load. 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand <[hidden email]>:
|
no is ok.
with the pharo version I know the iceberg version :) anyway your problem is that the remote for pharo is bad. you added [hidden email]:pharo/pharo.git and I do not think that exists. Correct one is: [hidden email]:pharo-project/pharo.git Esteban
|
Thank you Esteban, that was the problem! :) Maybe guille wants to clarify the correct remote repository in the page: https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo after "You can click on the Add remote option and configure a remote with a name and repository url."Do I miss something? 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano <[hidden email]>:
=?UTF-8?B?UHVsbF9SZXF1ZXN0c1/Ct19oZXJuYW5tZF9waGFyb18tXzIwMTctMTAtMTdfMDcuMzYuNTQucG5n?= (51K) Download Attachment History browser.png (220K) Download Attachment |
2017-10-17 7:42 GMT-03:00 Hernán Morales Durand <[hidden email]>:
Ah, it is in the pharo repository: https://github.com/pharo-project/pharo/pulls Cool
|
In reply to this post by EstebanLM
Esteban it would be good to make the remote handling more robust because many people face this problem. On Tue, Oct 17, 2017 at 11:53 AM, Esteban Lorenzano <[hidden email]> wrote:
|
In reply to this post by hernanmd
On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand <[hidden email]> wrote:
Done that. Can you check if that's ok?
|
In reply to this post by Stephane Ducasse-3
hi,
if people enter a wrong url, we can't do anything. now, the RSD is another problem, not related with this one. Esteban
|
In reply to this post by Guillermo Polito
Thanks Guille, now it looks fine. Another issue for Windows users is that you cannot execute the workaround:$ git config core.longpaths true until you first cloned the repository. That's why I said one first should let fail the git clone command and then: $ cd pharo/ $ git config core.longpaths true $ git checkout -f HEAD If anyone can check because submitting a fix should be easy and there shouldn't be guessing in the process. Cheers, Hernán 2017-10-18 4:37 GMT-03:00 Guillermo Polito <[hidden email]>:
|
Hi,
that’s why we created tonel (we will be moving to it soon). libgit2 does not recognise core.longpaths (in iceberg, process is split in two: bare clone and checkout so I tried adding that option when repository is created before checking out and it does not works either). also, one other reason to move to tonel is time: clone itself is very fast, but the checkout (there is a ridiculous amount of files to recreate there) is very slow. Esteban
|
In reply to this post by hernanmd
On Thu, Oct 19, 2017 at 1:36 AM, Hernán Morales Durand <[hidden email]> wrote:
If a windows user confirms, I update it. I don't have access to a windows machine right now :).
|
Free forum by Nabble | Edit this page |