Re: [Pharo-dev] Iceberg Bug? Branches with $/

While that may be true, I'd like to note that git-flow [1], one of the most widely used Git workflows, uses slashes in its default conventions. Bernhard [1] https://github.com/petervanderdoes/gitflow-avh > Am 14.01.2020 um 05:35 schrieb Ben Coman : > > Even from the command line I find slashes

Re: [Pharo-dev] Iceberg confusion

Hi, > On 14 Mar 2020, at 04:35, Ben Coman wrote: > > So I discovered a bug with Pharo Launcher and logged... > https://github.com/pharo-project/pharo-launcher/issues/431 > > and then wanted to contributing a fix, > but hit some

Re: [Pharo-dev] Iceberg Bug? Branches with $/

Hi all, Iceberg supports branches named with slashes. It can pull, push, merge, checkout… IIRC, what does not properly work is metacello support regarding it, because the parser of metacello urls may consider those extra “url path elements” part of the directory to fetch the project. Guille

Re: [Pharo-dev] Iceberg Bug? Branches with $/

On Tue, 14 Jan 2020 at 21:26, Sean P. DeNigris wrote: > > Ben Coman wrote > > I find slashes in branch names problematic > > Okay, you've convinced me. How do we guide people toward that policy? > A warning when creating such branches? That sounds reasonable. Perhaps a discrete warning

Re: [Pharo-dev] Iceberg Bug? Branches with $/

Ben Coman wrote > I find slashes in branch names problematic Okay, you've convinced me. How do we guide people toward that policy? A warning when creating such branches? At minimum we should change the ghost text from Iceberg's branch creation dialog, which suggests "feature/what" as a branch

Re: [Pharo-dev] Iceberg Bug? Branches with $/

On Tue, Jan 14, 2020 at 12:35:27PM +0800, Ben Coman wrote: > Even from the command line I find slashes in branch names problematic, > because slashes are as a "remote/branch" separator incites confusion about > what is being referenced. > > Other have different problems... The VM's shell scripts

Re: [Pharo-dev] Iceberg Bug? Branches with $/

Even from the command line I find slashes in branch names problematic, because slashes are as a "remote/branch" separator incites confusion about what is being referenced. Other have different problems...

[Pharo-dev] Iceberg: Why create branch when Reviewing a PR?

When reviewing a pull request, when merging, why does Iceberg prepend the repo name to the branch? It seems to require one to manually checkout the issue branch (and remember not to checkout any packages) in order to modify the code, no? - Cheers, Sean -- Sent from:

[Pharo-dev] Iceberg Bug? Branches with $/

As per common Git workflow, I named an issue branch "port/mac-pharo-7". When trying to load via: Metacello new baseline: 'VLC'; repository: 'github://seandenigris/Pharo-LibVLC:port/mac-pharo-7'; onConflict: [ :ex | ex allow ]; load. I got: NotFound: Revspec 'port' not found..

Re: [Pharo-dev] Iceberg Error in Pharo 7

Sean P. DeNigris wrote > somehow the PackageSet got out of sync This was also the cause of the problem I reported on Discord where changes were not showing up in Iceberg. I create an issue: RPackageSet Out of Sync https://github.com/pharo-project/pharo/issues/4648 - Cheers, Sean -- Sent

Re: [Pharo-dev] Iceberg Error in Pharo 7

Sean P. DeNigris wrote > UndefinedObject(Object)>>doesNotUnderstand: #methodClass > RGMethodDefinition>>asMCMethodDefinitionFromActiveDefinition This happened to me again in a different image, but this time with a different cause. I removed some methods via Calypso and somehow the PackageSet got

[Pharo-dev] Iceberg Error in Pharo 7

When trying to convert Soup to Tonel, I got: UndefinedObject(Object)>>doesNotUnderstand: #methodClass RGMethodDefinition>>asMCMethodDefinitionFromActiveDefinition RGMethodDefinition>>basicAsMCMethodDefinition RGMethodDefinition>>asMCMethodDefinition [ :ea | definitions add: ea

[Pharo-dev] Iceberg > trouble creating branches

In latest Pharo 8.0 (2019-07-05)(55f0b29) in Iceberg going Pharo > Create new branch from Issue is not picking up Issues from Github, only from Fogbugz. I'm half-sure that its been working for Github Issues ?? Then also Repository > Branch button is reporting an error with DropListPresenter

Re: [Pharo-dev] Iceberg: No Project Founds

> On 2 Jun 2019, at 19:22, Shaping wrote: > > From a 64-bit Pharo 7.0.3 I cloned UpdatedPharoByExample and immediately saw > in red ‘No Project Found’. Why is this and what must I do to fix it? > GitKraken shows that the repo is healthy. But what are you clone a book repo only

[Pharo-dev] Iceberg: No Project Founds

>From a 64-bit Pharo 7.0.3 I cloned UpdatedPharoByExample and immediately saw >in red ‘No Project Found’. Why is this and what must I do to fix it? >GitKraken shows that the repo is healthy. I tried pointing Iceberg in a virgin Pharo to the same folder, got the same result.

Re: [Pharo-dev] iceberg: merging branches just at the git level without changing code in the image

Hi, On Mon, Feb 4, 2019 at 6:19 PM Andrei Chis wrote: > Hi, > > Currently in Iceberg to merge a branch into another, we need to checkout > the branch into which we want to merge and then do the merge. > For the moment it is done that way because - every commit is first written in disk before

Re: [Pharo-dev] iceberg: merging branches just at the git level without changing code in the image

On Tue, 5 Feb 2019 at 01:19, Andrei Chis wrote: > Hi, > > Currently in Iceberg to merge a branch into another, we need to checkout > the branch into which we want to merge and then do the merge. > Checking out a branch also updates the code in the image, which when > needing to perform automatic

[Pharo-dev] iceberg: merging branches just at the git level without changing code in the image

Hi, Currently in Iceberg to merge a branch into another, we need to checkout the branch into which we want to merge and then do the merge. Checking out a branch also updates the code in the image, which when needing to perform automatic releases on a branch can cause issues. Is there already a

[Pharo-dev] Iceberg - Merging when there are changes in the working copy

Hi, IceCommitish>>#validateCanMerge has the warning: ''Experimental Feature: merge when there is a dirty working copy. Could cause a loss of your local changes. Please commit before merge.''. Are there some known situations when code can be lost? I'm asking because in releaser (

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log

--- Begin Message --- > Hi Petr, > > along with Esteban’s request for the error code from > allocateExecutablePage can you also see whether use of iceberg is successful > the second time you launch Pharo? So start up your virtualbox, try and > interact with iceberg, quit if it fails,

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log

Hi Petr, along with Esteban’s request for the error code from allocateExecutablePage can you also see whether use of iceberg is successful the second time you launch Pharo? So start up your virtualbox, try and interact with iceberg, quit if it fails, relaunch and try again? Also in your

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log

--- Begin Message --- Thanks for your assistance, but sources of this weird behavior is probably in the virtualization layer: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2018-September/273069.html pf > That means > > primAllocateExecutablePage > > failed. > There should be

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - solved (probably virtualization problem)

--- Begin Message --- Something very weird happens - my steps:

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log

That means primAllocateExecutablePage failed. There should be an errorCode value there, that can help us understand better the problem. Can you check at it? Thanks! Esteban > On 24 Sep 2018, at 17:49, Petr Fischer via Pharo-dev > wrote: > >

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log

--- Begin Message --- PharoDebug.log attached

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - corrected screenshot link

This looks like an FFI error... Can you try running uFFI tests in your system and sen us the results? Tx, Guille On Sun, Sep 23, 2018 at 9:54 PM Petr Fischer via Pharo-dev < pharo-dev@lists.pharo.org> wrote: > Ohh sorry - better screenshot link: > > > >

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - corrected screenshot link

--- Begin Message --- Ohh sorry - better screenshot link:

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage

Hi Petr, On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev wrote: > > Hello, I want to propose some small fixes to Pharo, it took me hours just to > run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > Now I am stuck with this Iceberg error: >

[Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage

--- Begin Message --- Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... Now I am stuck with this Iceberg error: https://app.box.com/file/321243070589 I am using 64bit Pharo VM + latest Pharo7 image from

Re: [Pharo-dev] Iceberg goodness plus ideas

On Mon, 10 Sep 2018 at 03:40, Guillermo Polito wrote: > Hi Ben, > > I'm really interested on improving on this. Please read below :) > > On Sun, Sep 9, 2018 at 5:07 PM Ben Coman wrote: > >> First, kudos to Iceberg team for detecting the mistake I made messing >> around at the command line under

Re: [Pharo-dev] Iceberg goodness plus ideas

Hi Ben, I'm really interested on improving on this. Please read below :) On Sun, Sep 9, 2018 at 5:07 PM Ben Coman wrote: > First, kudos to Iceberg team for detecting the mistake I made messing > around at the command line under the feet of an Iceberg managed repo. > I'm interested in some

Re: [Pharo-dev] Iceberg goodness plus ideas

On Sun, 9 Sep 2018 at 23:06, Ben Coman wrote: > d. In [D], its not clear the difference between: > "Discard local changes" > "Discard image changes" > Sorry, disregard [d.]. I missed that I could click on these to get a description. cheers -ben

Re: [Pharo-dev] Iceberg goodness plus ideas

I found a related issue https://github.com/pharo-vcs/iceberg/issues/762 and attached there the pic I left off the previous post. cheers -ben On Sun, 9 Sep 2018 at 23:06, Ben Coman wrote: > First, kudos to Iceberg team for detecting the mistake I made messing > around at the command line under

[Pharo-dev] Iceberg goodness plus ideas

First, kudos to Iceberg team for detecting the mistake I made messing around at the command line under the feet of an Iceberg managed repo. I'm interested in some general discussion of a few ideas before logging any issues. I had an Iceberg managed repo branch "ready-multiple-commands" as shown

Re: [Pharo-dev] Iceberg > review pull request & repo name clash

Hi Ben, The github integration has sure problems, since we were not actively working on it. So I really think it needs some love. Please go ahead an open as many issues (or PRs) as you want ^^. On Fri, Sep 7, 2018 at 4:54 AM Ben Coman wrote: > Two concerns from one flow of events... > > I was

[Pharo-dev] Iceberg > review pull request & repo name clash

Two concerns from one flow of events... I was trying out "review a pull request" feature for the first time. This looks very promising, but I got stuck. In Pharo 6.1... Downloaded http://files.pharo.org/platform/Pharo6.1-win.zip Updated Icerberg per

Re: [Pharo-dev] Iceberg: Cannot Clone Pharo Repository

As a workaround, maybe you can try updating your fork before cloning it from Iceberg? $ git clone yourFork $ git pull from-pharo $ git push On Mon, Aug 6, 2018 at 10:26 AM Guillermo Polito wrote: > Hi Eric, > > Thanks for the report. I'm looking into it. > > On Sun, Aug 5, 2018 at 6:20 PM Eric

Re: [Pharo-dev] Iceberg: Cannot Clone Pharo Repository

Hi Eric, Thanks for the report. I'm looking into it. On Sun, Aug 5, 2018 at 6:20 PM Eric Gade wrote: > I am having (new) issues cloning my forked pharo repository in a fresh P7 > image for development. Git objects are pulled from the repository > successfully, but during the checkout phase the

[Pharo-dev] Iceberg: Cannot Clone Pharo Repository

I am having (new) issues cloning my forked pharo repository in a fresh P7 image for development. Git objects are pulled from the repository successfully, but during the checkout phase the error posted below occurs (I can also provide a fuel dump by request). Here is my current system: OSX 10.13.1

Re: [Pharo-dev] Iceberg "Duplicated project!"

On 06/04/2018 11:33 AM, Esteban Lorenzano wrote: > hi, > >> On 4 Jun 2018, at 19:11, Martin McClure wrote: >> >> On 06/04/2018 05:34 AM, Esteban Lorenzano wrote: >>> hello Martin, >>> >>> This is becacuse metacello finds another version already registered. >> How is it already registered? This

Re: [Pharo-dev] Iceberg "Duplicated project!"

hi, > On 4 Jun 2018, at 19:11, Martin McClure wrote: > > On 06/04/2018 05:34 AM, Esteban Lorenzano wrote: >> hello Martin, >> >> This is becacuse metacello finds another version already registered. > How is it already registered? This is a fresh image. The only thing that > has happened is

Re: [Pharo-dev] Iceberg "Duplicated project!"

On 06/04/2018 05:34 AM, Esteban Lorenzano wrote: > hello Martin, > > This is becacuse metacello finds another version already registered. How is it already registered? This is a fresh image. The only thing that has happened is that it is already cloned, since I had loaded it in a different

Re: [Pharo-dev] Iceberg "Duplicated project!"

hello Martin, This is becacuse metacello finds another version already registered. Usually you can avoid that adding: onConflict: [ :e | e useLoaded ] and/or onUpgrade: [ :e | e useLoaded ] both messages act in different contexts: onConflict: between what is in disk and what is in image.

[Pharo-dev] Iceberg "Duplicated project!"

On a Pharo7, Linux, from yesterday: Build information: Pharo-7.0+alpha.build.994.sha.6b52ae62b755d8778fa0b5a4ac53b39b6c107dc9 (32 Bit) During an Iceberg load of a Metacello baseline, I get a dialog Duplicated project! There is already a project "OSSubprocess" in this installation. It's true

[Pharo-dev] [Iceberg] Call for contributions

Hi everybody, just for information, we have gathered some ideas on possible contributions for iceberg besides those in the issue tracker. We've put that in Iceberg's wiki: https://github.com/pharo-vcs/iceberg/wiki/How-to-help-us,-What-you-could-contribute The idea is that those contributions

Re: [Pharo-dev] Iceberg and new failure of Metacello github:// URLs

> On 19 Apr 2018, at 08:03, Martin McClure wrote: > > I have a project that depends on OSSubprocess. In the Pharo 7 of a week > ago I could load this by putting in my baseline: > > project: 'OSSubprocess' > with: [ spec >

[Pharo-dev] Iceberg and new failure of Metacello github:// URLs

I have a project that depends on OSSubprocess. In the Pharo 7 of a week ago I could load this by putting in my baseline: project: 'OSSubprocess'                     with: [ spec                         className: #ConfigurationOfOSSubprocess;                         versionString: #stable;        

Re: [Pharo-dev] Iceberg workflow

Torsten Bergmann wrote > !- docker - for docker Is anyone using a `docker` subfolder in a ST repo? I'm curious what one would store there and whether/how that would tie into GH/BB/GL CI infrastructures… - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

Sean P. DeNigris wrote > FYI #60530 is supposed to have Iceberg 0.6.8, but there is something > amiss. Any progress on this? I'm a bit stuck because I already started porting my baselines to use `gitlab://` - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Iceberg left:right

Tx On Sat, Feb 17, 2018 at 9:31 AM, Esteban Lorenzano wrote: > yes, is super confusing and is completely mixed :( > > I’m working on the changes with this in mind. In the future, all diffs with > be show with: left old/right new metaphor (problem is even that will have >

Re: [Pharo-dev] Iceberg left:right

yes, is super confusing and is completely mixed :( I’m working on the changes with this in mind. In the future, all diffs with be show with: left old/right new metaphor (problem is even that will have some problems, but at least it will be coherent) Esteban > On 17 Feb 2018, at 08:23,

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

Sean P. DeNigris wrote >> I backported iceberg 0.6.8 to Pharo 6.1 FYI #60530 is supposed to have Iceberg 0.6.8, but there is something amiss. For example, the IceGithubRepositoryType>>#mcRepository in the image is not the one in 0.6.8

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

EstebanLM wrote > I backported iceberg 0.6.8 to Pharo 6.1, so now it is in sync with the > version on Pharo 7.0 Hmm, Launcher still seems to download the same image version as before (#529), and MCGitlabRepository is still missing #httpsUrl and #scpUrl, which are present in Iceberg 0.6.8

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

EstebanLM wrote > I backported iceberg 0.6.8 to Pharo 6.1, so now it is in sync with the > version on Pharo 7.0 Sweet! I think I should now be able to get all my CI back up and running on GitLab :) - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

Nice, thank you! Julien --- Julien Delplanque Doctorant à l’Université de Lille 1 http://juliendelplanque.be/phd.html Equipe Rmod, Inria Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq Numéro de téléphone: +333 59 35 86 40 > Le 13 févr. 2018 à 13:33, Esteban Lorenzano

[Pharo-dev] Iceberg 0.6.8 backported to 6.1

Hi, I backported iceberg 0.6.8 to Pharo 6.1, so now it is in sync with the version on Pharo 7.0 Esteban

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

On Thu, Feb 8, 2018 at 6:28 AM, Ben Coman wrote: > Could the Iceberg gurus try and comment on the following workflow. > > Please familiarise with the first four commits here... > https://github.com/Traadh/cloudflareun/network > > from these actions... > > "first commit" --

Re: [Pharo-dev] Iceberg package addition

Tx denis. On Sun, Feb 11, 2018 at 8:58 PM, Denis Kudriashov wrote: > There is already issue Unable commit new added package > > 2018-02-11 19:27 GMT+01:00 Stephane Ducasse : >> >> Hi esteban >> >> each time I add a new packages to an iceberg

Re: [Pharo-dev] Iceberg package addition

There is already issue Unable commit new added package 2018-02-11 19:27 GMT+01:00 Stephane Ducasse : > Hi esteban > > each time I add a new packages to an iceberg project I get the same DNU > > KeyNotFound: why the name

[Pharo-dev] Iceberg package addition

Hi esteban each time I add a new packages to an iceberg project I get the same DNU KeyNotFound: why the name of my new package (which I added). packageNamed: packageName ^ self savedPackagesDictionary at: packageName

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

On 11 February 2018 at 02:28, Stephane Ducasse wrote: > > > > P.P.S. I think more thought needs to be given to whether mixing > > updates from both the remote and disk working directory in the one > > pane is beneficial? > > As an alternative, perhaps some

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

> > P.P.S. I think more thought needs to be given to whether mixing > updates from both the remote and disk working directory in the one > pane is beneficial? > As an alternative, perhaps some side-scrolling GTInspector-like panes >Image <--> Working Directory <--> Remote <--> Server(github)

Re: [Pharo-dev] Iceberg - creating virgin repos

Does it work if you add the package, commit changes (without push) and then in separate step do the push? -- Pavel 2018-02-08 4:28 GMT+01:00 Ben Coman : > If in the System Browser I do and work a bit on it, > then later want to push it to a new github repo, what is the >

[Pharo-dev] Iceberg experience report - synchronising README change made on github

Could the Iceberg gurus try and comment on the following workflow. Please familiarise with the first four commits here... https://github.com/Traadh/cloudflareun/network from these actions... "first commit" -- on github I created it as an unitialized repo to try to push a "new repo" to it per my

[Pharo-dev] Iceberg - creating virgin repos

If in the System Browser I do and work a bit on it, then later want to push it to a new github repo, what is the recommended procedure? As a rough guess I tried the "New repository" button, then added the package and a remote, but then trying to push gives me an error...

Re: [Pharo-dev] Iceberg UI feedback - synchronise v. status

On 29 January 2018 at 21:32, Christophe Demarey wrote: > >> Le 29 janv. 2018 à 14:16, Ben Coman a écrit : >> >> I hear Iceberg UI is getting a redesign. >> To feed into that... I'm trying to analyse myself, why I've not been >> comfortable with

Re: [Pharo-dev] Iceberg UI feedback - synchronise v. status

> Le 29 janv. 2018 à 14:16, Ben Coman a écrit : > > I hear Iceberg UI is getting a redesign. > To feed into that... I'm trying to analyse myself, why I've not been > comfortable with the "Synchronise..." menu item. I think maybe its > because that term feels like an

[Pharo-dev] Iceberg UI feedback - synchronise v. status

I hear Iceberg UI is getting a redesign. To feed into that... I'm trying to analyse myself, why I've not been comfortable with the "Synchronise..." menu item. I think maybe its because that term feels like an "action" that going to "do something" when I'm not sure what that something is.But

Re: [Pharo-dev] Iceberg Loading issue

dev@lists.pharo.org> Subject: Re: [Pharo-dev] Iceberg Loading issue Hi Vincent, Every time I've seen this question asked, the answer has been to checkout the branch that you want and then "Reload All" from the list of packages. Cheers, Alistair On 26 January 2018 at 00:42,

Re: [Pharo-dev] Iceberg Loading issue

Hi Vincent, Every time I've seen this question asked, the answer has been to checkout the branch that you want and then "Reload All" from the list of packages. Cheers, Alistair On 26 January 2018 at 00:42, wrote: > Hi, > > I am encountering some problems

Re: [Pharo-dev] Iceberg Loading issue

to refresh (at least under Windows). Cheers, Vincent From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Max Leske Sent: jeudi 25 janvier 2018 22:15 To: Pharo Development List Subject: Re: [Pharo-dev] Iceberg Loading issue Hi Vincent, Possibly a problem with updating

Re: [Pharo-dev] Iceberg Loading issue

Hi Vincent, Possibly a problem with updating FETCH_HEAD. Does it work when you perform only the pull operation from Pharo (i.e., check out the branch on the command line)? Cheers, Max On 26 January 2018 at 00:43:40, vincent.blond...@lamresearch.com ( vincent.blond...@lamresearch.com) wrote:

[Pharo-dev] Iceberg Loading issue

Hi, I am encountering some problems with Iceberg on the latest version. I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). Thanks to the iceberg

Re: [Pharo-dev] Iceberg merged pull requests?

> On 6 Jan 2018, at 09:27, Bernhard Pieber wrote: > > Hi Esteban, > > Thanks for your answer. See more questions below. > >> Am 04.01.2018 um 09:16 schrieb Esteban Lorenzano : >> >>> On 3 Jan 2018, at 23:09, Stephane Ducasse

Re: [Pharo-dev] Iceberg merged pull requests?

Hi Esteban, Thanks for your answer. See more questions below. > Am 04.01.2018 um 09:16 schrieb Esteban Lorenzano : > >> On 3 Jan 2018, at 23:09, Stephane Ducasse wrote: >> >> You should double click on the pharo lines and looks in the update >>

Re: [Pharo-dev] Iceberg merged pull requests?

> On 3 Jan 2018, at 23:09, Stephane Ducasse wrote: > > You should double click on the pharo lines and looks in the update > pane you will see the updates (but you should pull from pharo to sync > your repo). > > Stef > > On Tue, Jan 2, 2018 at 10:45 PM, Bernhard

Re: [Pharo-dev] Iceberg merged pull requests?

You should double click on the pharo lines and looks in the update pane you will see the updates (but you should pull from pharo to sync your repo). Stef On Tue, Jan 2, 2018 at 10:45 PM, Bernhard Pieber wrote: > I saw that two pull requests were accepted and merged into the

[Pharo-dev] Iceberg merged pull requests?

I saw that two pull requests were accepted and merged into the development branch. I had expected that Iceberg would show me them somewhere. However, in the branches pane of my repository the status pharo-project/development is shown as Up to date. Shouldn't there be some indication that new

Re: [Pharo-dev] iceberg metacello integration not working?

Hi, Thanks! This worked fine: Iceberg enableMetacelloIntegration: true. IceMetacelloPharoPlatform select. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. Cheers, Doru > On Dec 1, 2017, at 7:45 AM, Esteban Lorenzano wrote: >

Re: [Pharo-dev] iceberg metacello integration not working?

a regression, see: https://pharo.fogbugz.com/f/cases/20784/update-Metacello-since-last-update-failed in the meantime you can fix it by executing: IceMetacelloPharoPlatform select. Esteban > On 1 Dec 2017, at

[Pharo-dev] iceberg metacello integration not working?

Hi, In - a 60523 image, - with the latest stable VM (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)) I am doing: Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository:

Re: [Pharo-dev] Iceberg workflow

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. -

Re: [Pharo-dev] Iceberg workflow

On 28-11-17 22:08, Torsten Bergmann wrote: Having the code directly in the root is possible but not a good style or to be recommended - because often projects include more than just the source code and over time include more and more things like docu or other. Thanks for the explanation for

Re: [Pharo-dev] Iceberg workflow

> On 29 Nov 2017, at 07:19, Ben Coman wrote: > > On 29 November 2017 at 07:50, Sean P. DeNigris wrote: >> Stephan Eggermont-3 wrote 2c) Code subdirectory: enter "src" here !!! >>> Do we really need that? Why would I care about that? >>

Re: [Pharo-dev] Iceberg workflow

showing a correct error message, not not showing the changes :) cheers, Esteban > > Can anyone reproduce this? > > cheers -ben > > ** Maybe if Metacello integration is disabled the menu option in > Iceberg should greyed out. > > >> >>If there are oth

Re: [Pharo-dev] Iceberg workflow

com/pharo-project/pharo > > or many of the other Pharo or non-Pharo projects on GitHub. > > Hope this explains it. +1000 thanks Torsten :) Esteban > > Bye > T. > > [1] https://www.sohamkamani.com/blog/2015/08/21/frontend/ > [2] > https://maven.apache.org/guid

Re: [Pharo-dev] Iceberg workflow

> On 28 Nov 2017, at 20:25, stephan wrote: > > On 28-11-17 19:40, Torsten Bergmann wrote: >> 2c) Code subdirectory: enter "src" here !!! > > Do we really need that? Why would I care about that? because you want to structure your projects as you want, and not as some

Re: [Pharo-dev] Iceberg workflow

>If there are other groups defined you can use "Install baseline ..." > > So you missed the step 2c. > > Hope this helps! +1 :) > > Thanks > T. > > > > >> Gesendet: Dienstag, 28. November 2017 um 15:41 Uhr >> Vo

Re: [Pharo-dev] Iceberg workflow

Hi Ben, we have been discussing a lot this issues in discord recently (expectations from git users, monticello users and what iceberg needs to do/show in which case). basically, we have a mess on terminology and some workflows needs to be enhanced. Now, about your observations: a) more

Re: [Pharo-dev] Iceberg workflow

Hi Ben, On 29 November 2017 at 06:51, Ben Coman wrote: > On 29 November 2017 at 02:40, Torsten Bergmann wrote: >> Hi Ben, >> >> I think you forgot to give Iceberg the "src" subdirectory where all the code >> packages reside. > > Not such much forgot and

Re: [Pharo-dev] Iceberg workflow

On 29 November 2017 at 07:50, Sean P. DeNigris wrote: > Stephan Eggermont-3 wrote >>>2c) Code subdirectory: enter "src" here !!! >> Do we really need that? Why would I care about that? > > BTW in latest Iceberg this is automatically selected if it is one of the >

Re: [Pharo-dev] Iceberg workflow

cheers -ben ** Maybe if Metacello integration is disabled the menu option in Iceberg should greyed out. > > If there are other groups defined you can use "Install baseline ..." > > So you missed the step 2c. > > Hope this helps! > > Thanks > T. > &

Re: [Pharo-dev] Iceberg workflow

Stephan Eggermont-3 wrote >>2c) Code subdirectory: enter "src" here !!! > Do we really need that? Why would I care about that? BTW in latest Iceberg this is automatically selected if it is one of the standard names (e.g. src, repository) - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Iceberg workflow

.com/blog/2015/08/21/frontend/ [2] https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > Gesendet: Dienstag, 28. November 2017 um 20:25 Uhr > Von: stephan <step...@stack.nl> > An: pharo-dev@lists.pharo.org > Betreff: Re: [Pharo-dev] I

Re: [Pharo-dev] Iceberg workflow

On 28-11-17 19:40, Torsten Bergmann wrote: 2c) Code subdirectory: enter "src" here !!! Do we really need that? Why would I care about that? Stephan

Re: [Pharo-dev] Iceberg workflow

loads all dependencies and the necessary packages in the right order. If there are other groups defined you can use "Install baseline ..." So you missed the step 2c. Hope this helps! Thanks T. > Gesendet: Dienstag, 28. November 2017 um 15:41 Uhr > Von: "Ben C

[Pharo-dev] Iceberg workflow

I'm still struggling with Iceberg workflow for a personal repo. World menu > Iceberg Clicked Remote URL <-- g...@github.com:bencoman/libclang-pharo-bindings.git Clicked So now I have a new row... Name = libclang-pharo-bindings Current Branch = master Loaded version = No package loaded

[Pharo-dev] Iceberg "Create repository" buttons

In Iceberg I am finding the "Create repository" button disconcerting for some of the Iceberg repository dialogs. For example, clicking "Add local repository" shows a dialog "Import local repository into Iceberg" with a "Create repository" button and perception of this which I can't shake is

Re: [Pharo-dev] Iceberg operations overview

On 22-11-17 09:33, Pavel Krivanek wrote: during brainstorming of the Iceberg UI simplification we created a document that shows what the current Iceberg operations do. It should help you to clarify the role of the working copy etc. Thanks, that is helpful. From the discussions on discord and

Re: [Pharo-dev] Iceberg Clone Location

Sean P. DeNigris wrote > Iceberg seems to expect clones to be in > {sharedRepoFolder}/{gitHubUser}/{projectName} I wonder if this is even conceptually correct. After all, wouldn't different users' forks just be different remotes on the same repo in the git worldview? - Cheers, Sean --

  1   2   3   >