Re: [Pharo-users] Iceberg "adopt commit" behavior

Thanks Sean, I switched to use that, I didn't know about the "DO NOT CHECK OUT..." option. This sequence is so convenient it might be worth having as a single click option (repair > discard > do not checkout). Regards! Esteban A. Maringolo On Sat, Aug 22, 2020 at 8:24 AM Sean P. DeNigris wrote

Re: [Pharo-users] Iceberg "adopt commit" behavior

Esteban A. Maringolo wrote > So... rephrasing the question... What is the recommended way to work > with external files in the same repository as these of Tonel? Here is what I do (although I'm not sure if it's "the" way). This is off the top of my head because I'm not in front of an image right n

Re: [Pharo-users] Iceberg "adopt commit" behavior

Hi Pablo, I did the following: 1. Have Pharo with no changes in the current branch. 2. Edit an external file (foo.txt) and commit just modifying this file. 3. Go to Pharo, select the recently created commit and do an "Adopt commit" command on it. 4. Make some change and commit in Iceberg The chan

Re: [Pharo-users] Iceberg "adopt commit" behavior

You can always get the registered repositories through: IceRepository registry But take care that the API is not intended to be stable through versions as it is always intended to be used by the UI. So, script it as you wish, we can answer whatever doubt you have, but I have warn you :D! On Fri,

Re: [Pharo-users] Iceberg "adopt commit" behavior

Esteban A. Maringolo wrote > so I add how do I get the IceLibgitRepository > instance? (given I provide the name). I got it via Iceberg contextMenu -> Extra -> Inspect, which works via the UI but maybe you're looking for a programmatic way? - Cheers, Sean -- Sent from: http://forum.world.st

Re: [Pharo-users] Iceberg "adopt commit" behavior

I did a PR, with small adjustments. Pierre On 20/08/2020 21:00, Stéphane Ducasse wrote: pablo may be we should add this in a class comment or fly by help somewhere. S On 20 Aug 2020, at 11:45, teso...@gmail.com wrote: Hi,  the adopt commit operation has noth

Re: [Pharo-users] Iceberg "adopt commit" behavior

pablo may be we should add this in a class comment or fly by help somewhere. S > On 20 Aug 2020, at 11:45, teso...@gmail.com wrote: > > Hi, > the adopt commit operation has nothing to do with the rebase. It > sets the reference commit of the image to the given commit. It does > not affect

Re: [Pharo-users] Iceberg "adopt commit" behavior

On Thu, Aug 20, 2020 at 10:48 AM Sean P. DeNigris wrote: > > The image knows at any moment the commit it has loaded (or it supposed > > to have loaded). > > For posterity, that info can be accessed via e.g. `anIceLibgitRepository > workingCopy referenceCommit shortId` This comes really handy, so

Re: [Pharo-users] Iceberg "adopt commit" behavior

teso...@gmail.com wrote > It sets the reference commit of the image to the given commit. It does > not affect the git repository...The adopt operation overrides the > reference commit with the selected > one, it does not affect the loaded code. Ah, good to know! I didn't know this was available an

Re: [Pharo-users] Iceberg "adopt commit" behavior

Yes, it should work. The same if you repair the repository doing a checkout loading the changes from the repository (there should not be changes) Tell us if you have any questions Thanks! On Thu, Aug 20, 2020 at 2:21 PM Esteban Maringolo wrote: > > Hi Pablo, > > Thanks for the answer. > > So my

Re: [Pharo-users] Iceberg "adopt commit" behavior

Hi Pablo, Thanks for the answer. So my workflow of editing files outside of Pharo, committing them, and then adopting the latest commit would be safe? (as long I don't modify files modified by Pharo). Best regards! Esteban A. Maringolo On Thu, Aug 20, 2020 at 6:46 AM teso...@gmail.com wrote:

Re: [Pharo-users] Iceberg "adopt commit" behavior

Hi, the adopt commit operation has nothing to do with the rebase. It sets the reference commit of the image to the given commit. It does not affect the git repository. The image knows at any moment the commit it has loaded (or it supposed to have loaded). The adopt operation overrides the ref

Re: [Pharo-users] Iceberg: Installing a baseline from a self hosted Git/Gitea repository branch

Thanks a lot Christophe! It worked like a charm. Now I'm able to build a shareable installation baseline that uses external git repositories not hosted in the oligopolistic providers by downloading them with Iceberg and loading from the hard disk with Metacello. I have updated the Grafoscopio readm

Re: [Pharo-users] Iceberg: Installing a baseline from a self hosted Git/Gitea repository branch

Hi Offray, You can also use something like: location := FileLocator localDirectory / 'iceberg' / 'pharo-contributions' / 'taskit'. (IceRepositoryCreator new location: location; remote: (IceGitRemote url: 'https://github.com/pharo-contributions/taskit.git'); createReposit

Re: [Pharo-users] Iceberg: Installing a baseline from a self hosted Git/Gitea repository branch

Hi Pierce, I'm loading the stuff in the self Gitea repositories from local copies and in the order I know they are needed. So in a sense I following a similar behavior as yours (but I will use the `tonel:///` trick now when needed, thanks for it). My problem is with sharing my baseline with other

Re: [Pharo-users] Iceberg: Installing a baseline from a self hosted Git/Gitea repository branch

On Wed, Jul 15, 2020 at 08:41:04AM -0500, Offray Vladimir Luna Cárdenas wrote: > So, a better question would be: Is possible to load programatically (via > a code snippet) using Iceberg, Monticello or something else a baseline > that installs a project and its dependencies and is hosted in an > ind

Re: [Pharo-users] Iceberg: Installing a baseline from a self hosted Git/Gitea repository branch

Thanks Guille, The document you point was the one I was reading. But I thought that, despite differences between Iceberg and Monticello, the last one would be able to load baselines in a host-neutral Git repository, using https. So, a better question would be: Is possible to load programatically

Re: [Pharo-users] Iceberg: Installing a baseline from a self hosted Git/Gitea repository branch

Hi Offray, Metacello and Iceberg are different things, although there is some integration between them. Iceberg understand git urls (ssh:// … g...@github.com …. https://…) Metacello understand its own urls, because it was originally designed to work in independence of

Re: [Pharo-users] Iceberg: relative file path to repository

Posting a question to this list brings the inspiration by itself :-) When the location of repository is set like this: (IceLibgitRepository registry) do: [ :reg | (reg name = 'myRepo') ifTrue: [ reg location: ('pharo-local/iceberg/myRepo' asFileReference) ] ] the path is taken as rela

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

Dale, Besides the issue affecting this particular case, I think that the Tonel "format" should support and honor "metadata" at the class/package/method level. E.g. the SETT exporter creates the #vw_namespace for classes, other dialects may need to specify other information that would be useful tha

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

SETT was create based on our understanding (GemTalk Systems) of what the tonel disk format was _supposed_ to be and I think that Pharo has departed from somewhat from what was understood to be the format. I've had similar problems trying to use filetree repositories with Iceberg that have been

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

Hi Guillermo, Your workaround effectively solved my issue. About the tonel format, in the .properties file at the sources directory there was such setting: https://github.com/eMaringolo/rbac/blob/9279f22ef5fd1c4149090b5b39a6afa143a6519c/sources/properties.st But the .project file was missing at

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

I’ve created an issue: https://github.com/pharo-vcs/iceberg/issues/1251 > El 18 jun 2019, a las 9:30, Guillermo Polito > escribió: > > Hi Esteban, > > It seems like a bug in Iceberg. If you click on debug, you’ll see that > although you’ve

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

Hi Esteban, It seems like a bug in Iceberg. If you click on debug, you’ll see that although you’ve said the project is in tonel format, it’s trying to use a Filetree reader This is due to some missing metadata in the commit (iceberg is relying on commit information there and not working copy

Re: [Pharo-users] Iceberg for files other than code?

Hi Tim, > Hi Konrad - I think you can do what you describe - I think the > ICeRepository entry for your project will have the path you want. Indeed. Here's how to get the repository for class MyClass: repo := IceRepository registeredRepositoryIncludingPackage: MyClass package. And then the pa

Re: [Pharo-users] Iceberg for files other than code?

Hi Konrad - I think you can do what you describe - I think the ICeRepository entry for your project will have the path you want. And yes, its the committing back non source files where iceberg doesn’t try to do anything (and so needs help from elsewhere). Tim > On 7 Apr 2019, at 16:40, Konrad

Re: [Pharo-users] Iceberg for files other than code?

Hi Christopher and Tim, Thanks for your comments! I agree that managing the README from Pharo is not the most important use case, I just mentioned it because everyone know what a README is. A better example of what I want to do is Pharo's Help system. It stores the individual pages as methods th

Re: [Pharo-users] Iceberg for files other than code?

My understanding is that at the moment commits are restricted to what’s I the designated src directory, so you need to use an external way to commit non code files into your branch. These can be 1. Git cmd line 2. Another tool like IntelliJ 3. The github web bowser If you do, you need to pull o

Re: [Pharo-users] Iceberg for files other than code?

Hi Konrad, On Sat, 6 Apr 2019 at 15:46, Konrad Hinsen wrote: > Hi everyone, > > Is it possible to read and modify files not containing Pharo code in a > repository managed by Iceberg? I am thinking of reading the repository's > README file, for example, or storing data files read by my code > al

Re: [Pharo-users] Iceberg Custom SSH Keys

Hi, We are still looking into this issue but we have everything configurated: If i can fix it i will post it here. regards bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Ah - I think I know whats happened - I didn’t do a proper reset of my fork - the real command is: Tims-MacBook-Pro:pharo-exercism macta$ git fetch exercism Tims-MacBook-Pro:pharo-exercism macta$ git reset --hard exercism/master HEAD is now at 28a7a95 Update readme for pharo smalltalk repo name #2

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Tue, Feb 19, 2019 at 2:08 AM Tim Mackinnon wrote: > Hi Guille - thanks for taking the time to write this up… in the middle > there I finally spotted the crucial bit “clone the original, push to your > fork”. I think thats what I’ve been doing wrong - and it leads to all kinds > of confusion (a

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Hi Guille - thanks for taking the time to write this up… in the middle there I finally spotted the crucial bit “clone the original, push to your fork”. I think thats what I’ve been doing wrong - and it leads to all kinds of confusion (at least I’m hoping this is what it is). As I have cloned fr

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Mon, Feb 18, 2019 at 7:50 AM Konrad Hinsen wrote: > Am 18.02.19 um 01:19 schrieb Tim Mackinnon: > > > Hey Ben - I’m not sure that this actually does the same thing. I just > > tried it now, and it resulted in an extra merge in my forked repo - as I > > think this effectively pulls down from up

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Mon, Feb 18, 2019 at 2:45 AM Sean P. DeNigris wrote: > Tim Mackinnon wrote > > wouldn’t it be helpful if this was a command in Iceberg? > > Yes! This is a super common task and for easy cases would be great to > automate > https://help.github.com/articles/syncing-a-fork/ > > > That's useful

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Mon, Feb 18, 2019 at 1:19 AM Tim Mackinnon wrote: > Hey Ben - I’m not sure that this actually does the same thing. I just > tried it now, and it resulted in an extra merge in my forked repo - as I > think this effectively pulls down from upstream into pharo and then if you > have any differenc

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Hi! On Fri, Feb 15, 2019 at 7:06 PM Tim Mackinnon wrote: > Hi guys - I’ve spent a few hours scratching my head trying to understand > why some of my Pull Requests to a project I had forked kept showing my > previous commits when I thought I was all caught up. > > It suddenly dawned on me, that w

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Am 18.02.19 um 01:19 schrieb Tim Mackinnon: Hey Ben - I’m not sure that this actually does the same thing. I just tried it now, and it resulted in an extra merge in my forked repo - as I think this effectively pulls down from upstream into pharo and then if you have any differences in your loc

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Tim Mackinnon wrote > wouldn’t it be helpful if this was a command in Iceberg? Yes! This is a super common task and for easy cases would be great to automate https://help.github.com/articles/syncing-a-fork/ - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.h

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Hey Ben - I’m not sure that this actually does the same thing. I just tried it now, and it resulted in an extra merge in my forked repo - as I think this effectively pulls down from upstream into pharo and then if you have any differences in your local image copy they might cause some changes wh

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Sat, 16 Feb 2019 at 02:06, Tim Mackinnon wrote: > Hi guys - I’ve spent a few hours scratching my head trying to understand > why some of my Pull Requests to a project I had forked kept showing my > previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I h

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

> On 21 Jan 2019, at 15:36, sergio ruiz wrote: > > Ah! > > I have been using 6.0 as this project is going to be a seaside website on a > real production project.. > > Maybe I should try it in Pharo 7, and see if it works.. Sure, Seaside works fine on Pharo 7, and overall you will get bett

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

Ah! I have been using 6.0 as this project is going to be a seaside website on a real production project.. Maybe I should try it in Pharo 7, and see if it works.. On January 21, 2019 at 9:16:12 AM, Sven Van Caekenberghe (s...@stfx.eu) wrote: Wow, this looks like a very old Iceberg. At least in P

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

> On 21 Jan 2019, at 14:58, sergio ruiz wrote: > >> >> >> You can also double click into the repository, or click on the "Packages" >> menu. >> > > For some reason, I am not getting “Packages” in my menu: > > <02E567F3-283C-4010-93D6-392BDD5F6012.png> Wow, this looks like a very old Ic

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

Am 21.01.19 um 14:59 schrieb sergio ruiz: I am not able to get the packages view to load on my project. How would I go about creating a baseline? Check out this explanation (with examples) : https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/Baselines.md Konrad.

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

I am not able to get the packages view to load on my project. How would I go about creating a baseline? On January 21, 2019 at 4:00:01 AM, Sven Van Caekenberghe (s...@stfx.eu) wrote: For your own projects, you will have to create your own BaselineOf, which is easier than creating a Configuration

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

You can also double click into the repository, or click on the "Packages" menu. For some reason, I am not getting “Packages” in my menu: peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandm

Re: [Pharo-users] [Iceberg] Loading my git project into a new image

On Mon, Jan 21, 2019 at 03:10:49AM +0100, sergio ruiz wrote: > While I can clone the the repo on in my new image using Iceberg, I can’t > figure out now to load the packages, now that they are loaded up via > iceberg. If you mean you want to load from a git repo in your local filesystem, then like

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

> On 2 Dec 2018, at 12:00, Sven Van Caekenberghe wrote: > > > >> On 2 Dec 2018, at 11:31, Hilaire wrote: >> >> Hi Ichi, >> >> If you are learning Pharo I suggest you to not follow this way for now >> as it may result in cognitive overload and frustration. > > Although the workflow descri

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

> On 2 Dec 2018, at 11:31, Hilaire wrote: > > Hi Ichi, > > If you are learning Pharo I suggest you to not follow this way for now > as it may result in cognitive overload and frustration. Although the workflow described below does indeed work, it (1) assumes you already know how to handle a

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

Hi Ichi, If you are learning Pharo I suggest you to not follow this way for now as it may result in cognitive overload and frustration. If you just want to save your code on some repo, use Metacello to create a tonel repository, then do code revision the way you use to do it (command line, third

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

Hi, You are not alone. I have the same impression that Metacello+Git+Iceberg is something very difficult to grasp. It is getting hard to keep the pace with a constant evolving Pharo system. best ichi -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

Hello, Thank you Sean :) >> So is it possible to define such constraints ? > > IIUC you could use #onConflict: and be more specific in the block as to > allow only the specific case you mentioned, but I think the more common > approach is to use the Metacello API to "lock" NeoJSON to the version

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

cedreek wrote > So is it possible to define such constraints ? IIUC you could use #onConflict: and be more specific in the block as to allow only the specific case you mentioned, but I think the more common approach is to use the Metacello API to "lock" NeoJSON to the version you want. I don't hav

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

Nobody knows ? I probably do/ask something wrong… My impression is that it is very difficult for a newcomer to get into Iceberg/Github (I tried to avoid GIT as much as possible and I understand why now ^_^)… but still it’s a great tool. Just not that easy to "master" (there are several possibil

Re: [Pharo-users] Iceberg - better control of project name?

> > On Wed, 3 Oct 2018 at 16:18, Guillermo Polito > wrote: > > > On 2 Oct 2018, at 12:30, Ben Coman wrote: > > On Mon, 1 Oct 2018 at 23:16, Sean P. DeNigris > wrote: > >> Tim Mackinnon wrote >> > either by showing {owner}/{project} >> >> What about when there are multiple remotes? >> > > +1 to

Re: [Pharo-users] Iceberg - better control of project name?

On Tue, Oct 2, 2018 at 6:54 PM Ben Coman wrote: > > > On Tue, 2 Oct 2018 at 15:52, Guillermo Polito > wrote: > >> - Maybe, for old projects that don't have a name, we could initialize a >> project's name as it's repository name? >> > > In any case, I'd expect the project name within Iceberg to

Re: [Pharo-users] Iceberg - better control of project name?

Ben Coman wrote > I'd expect the project name within Iceberg to match the name > of the working directory on disk. I wonder if e.g. direct git loading creating a directory with the same name as the repo (and maybe not what you'd want to see in Pharo) would make that potentially problematic. Maybe

Re: [Pharo-users] Iceberg - better control of project name?

On Tue, 2 Oct 2018 at 15:52, Guillermo Polito wrote: > - Maybe, for old projects that don't have a name, we could initialize a > project's name as it's repository name? > In any case, I'd expect the project name within Iceberg to match the name of the working directory on disk. Possibly even th

Re: [Pharo-users] Iceberg - better control of project name?

Issue: https://github.com/pharo-vcs/iceberg/issues/1009 On Tue, Oct 2, 2018 at 10:02 AM Guillermo Polito wrote: > Aaand the mail got sent before :) > > Then two other comments that are related or I'd like to discuss: > - So far we can allow in iceberg several projects with the same name. > T

Re: [Pharo-users] Iceberg - better control of project name?

Aaand the mail got sent before :) Then two other comments that are related or I'd like to discuss: - So far we can allow in iceberg several projects with the same name. That is not a problem, so you can clone the same project from two different repositories. Of course this would mean that one wi

Re: [Pharo-users] Iceberg - better control of project name?

Yes, I agree with most of the comments here. I'll try to summarize: - we should be able to specify the name of a project independently of their location/repository name - Maybe, for old projects that don't have a name, we could initialize a project's name as it's repository name? On Tue, Oct 2,

Re: [Pharo-users] Iceberg - better control of project name?

Sounds like the user override is what we are after - I guess we need to make a pr ... sadly my laptop has died so it’s not going to be me for a little while until I can find an Apple store on my travels. Tim Sent from my iPhone > On 2 Oct 2018, at 12:30, Ben Coman wrote: > > > >> On Mon, 1

Re: [Pharo-users] Iceberg - better control of project name?

On Mon, 1 Oct 2018 at 23:16, Sean P. DeNigris wrote: > Tim Mackinnon wrote > > either by showing {owner}/{project} > > What about when there are multiple remotes? > +1 to what you imply here, that the owner/remote should not be auto-coded into the project name. Remote are well handled within Ice

Re: [Pharo-users] Iceberg - better control of project name?

Tim Mackinnon wrote > either by showing {owner}/{project} What about when there are multiple remotes? Tim Mackinnon wrote > letting you give a better name in the definition to override what is > shown? We have project metadata now, so that seems straightforward. I have a few use cases where the

Re: [Pharo-users] Iceberg issue on Ubuntu 16.04.3 Pharo 6.1

--- Begin Message --- Hi Guillermo, Thank you for the explanation. I have noticed that if I use https://get.pharo.org/64/vm61 instead of 64/vmI61 (__I__ letter) it works. The same happens for Pharo 7.0. Cheers, Juraj > On Jul 17, 2018, at 04:33, Guillermo Poli

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Thanks Ben - I hadn’t really thought of using the GitHub web ui itself (so many places to choose from ;) Effectively the ~1 syntax Guille mentioned is exactly what you’ve explained (so that hangs together nicely). Now looking back at the tutorial I had followed, I didn’t notice the ~1 in there.

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

On 28 June 2018 at 07:38, Tim Mackinnon wrote: > Hey thanks Ben - this still doesn’t work for me… good idea to try on the > Pharo repo itself. > > I have a fork of it, which I catch up periodically - so I tried a similar > suggestion to you - went into my directory (underneath the src folder) and

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

> You mentioned a Calypso plugin for versions - where is that? I loaded a recentish P7 image and I don’t see those icons? Is this something I can easily load to try out? As soon as a class is inside a package that is managed by iceberg, you should see in Calypso a new button and menu item on metho

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

For the record - I get the same error using those steps on Ubuntu as well. So I must be doing something wrong? (Note in my message when I pasted the command used - I neglected the git in front of: log --diff-filter=D --summary —pretty="format:%cd | %h | %H | %cn%n-> %s%n”) Tim > On 28 Jun 2

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

And just to add to this - I just did a git clone (git clone g...@github.com :pharo-project/pharo.git) in a fresh directory and can see that same deleted file - and when I try to do a checkout, it gives the path spec error. This is very weird - is it some osx thing? I wi

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hey thanks Ben - this still doesn’t work for me… good idea to try on the Pharo repo itself. I have a fork of it, which I catch up periodically - so I tried a similar suggestion to you - went into my directory (underneath the src folder) and typed: log --diff-filter=D --summary --graph --pretty

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

On 25 June 2018 at 19:41, Tim Mackinnon wrote: > I’d be really interested if someone with lower level GIT knowledge might > try a: > > git checkout src//.class.st > > > For their project - as I don’t understand what I’m doing wrong - and I’d > like the comfort of

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

I’d be really interested if someone with lower level GIT knowledge might try a: git checkout src//.class.st For their project - as I don’t understand what I’m doing wrong - and I’d like the comfort of knowing that our source is in a place/state where we can rel

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Just to add more information to this - I did try what was suggested here (it refers to a branch and not a commit id - but heck worth a shot) https://stackoverflow.com/questions/5989592/git-cannot-checkout-branch-error-pathspec-did-not-match-any-files-kn

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Guille - just following up on this thread as I’d like to get more confident with this stuff. You mentioned a Calypso plugin for versions - where is that? I loaded a recentish P7 image and I don’t see those icons? Is this something I can easily load to try out? As I don’t have that plugin, I’ve

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

On Thu, Jun 14, 2018 at 10:17 AM Tim Mackinnon wrote: > Hi Guille - I have tried the repo browser with the new iceberg loaded in > Pharo 6.1 and I couldn’t see how it helps me? (I will make a firm point of > using 7 now as I think I’ve now got a reasonable grasp of how things should > work). > >F

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hi Guille - I have tried the repo browser with the new iceberg loaded in Pharo 6.1 and I couldn’t see how it helps me? (I will make a firm point of using 7 now as I think I’ve now got a reasonable grasp of how things should work). From the threads below - how would I find the commit with my miss

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hi, Regarding history, right now we have a history browser implemented as a Calypso plugin, that is open using context menu => history or the little box button on the top right of the method pane (second button from the left in the picture): [image: Screen Shot 2018-06-14 at 09.34.24.png] That b

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hi Sean - I tried it again, and it worked: git log --full-history -- */PrismicBlock.class* (I got my wildcard slightly wrong for tonel format) - although the beauty of the one I gave was that it shows you all deleted classes (in case you don’t know the name) I’m still confused why I can’t chec

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Tim Mackinnon wrote > I didn’t quite get your fu to work Interesting. When I searched for commits affecting the deleted class SuDebianKey: $ git log --full-history -- */SuDebianKey.class/properties.json I got back a list of commits (obviously with the last chronologically being the deletion):

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hi Sean - that is an excellent reply, I didn’t quite get your fu to work - but if you look up how to find deleted classes in git they give the following: git log --diff-filter=D --summary This gives you a git list of checkins and shows you the checkin comment, along with the list of files that

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Tim Mackinnon wrote > Hi - I am interested in what the future holds with Iceberg for things like > finding deleted classes or reverting to older versions of things. Great question! It used to be in the Change Sorter that delections were logged and reversible. At some point that stopped working and

Re: [Pharo-users] Iceberg Pharo6.1 on Microsoft Windows 7

On 2 May 2018 at 22:02, Guillermo Polito wrote: > Hi Federico, > > I don't think compiling libgit in your box will solve the problem. I think > libgit is correctly compiled (otherwise you'd have another kind of error). > What you probably have is an ssh authentication error. > It would be nice i

Re: [Pharo-users] Iceberg Pharo6.1 on Microsoft Windows 7

Hi Federico, I don't think compiling libgit in your box will solve the problem. I think libgit is correctly compiled (otherwise you'd have another kind of error). What you probably have is an ssh authentication error. Could you try cloning using the https url provided by github instead? That sho

Re: [Pharo-users] Iceberg: whom to email directly?

Ben Coman wrote: On 10 April 2018 at 23:46, Herbert Vojčík mailto:he...@mailbox.sk>> wrote: I have a strict "no github account" policy. Whom/where should I post to report issues? Thanks, Herby https://pharo.fogbugz.com Ironically, I ask because of https://pharo.fogbugz.com

Re: [Pharo-users] Iceberg: whom to email directly?

On 10 April 2018 at 23:46, Herbert Vojčík wrote: > I have a strict "no github account" policy. > > Whom/where should I post to report issues? > > Thanks, Herby > > https://pharo.fogbugz.com cheers -ben

Re: [Pharo-users] Iceberg and resource files

Guille shows me a filesystem git accessed and browsed from Pharo. Soon to be public. On Mon, Jan 29, 2018 at 10:14 AM, Christophe Demarey wrote: > Hi Ken, > >> Le 27 janv. 2018 à 15:38, kmo a écrit : >> >> I don't understand how iceberg handles resource files that you might also >> like to ver

Re: [Pharo-users] Iceberg and resource files

Hi Ken, > Le 27 janv. 2018 à 15:38, kmo a écrit : > > I don't understand how iceberg handles resource files that you might also > like to version along with the pharo code. For now, Iceberg do not really handle these files but it is planned in a next future. > Say I have an CSV file and a tex

Re: [Pharo-users] Iceberg and resource files

These suggestions look really good. Thanks to everyone. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Iceberg and resource files

Hi, > How do I include these in the iceberg commit/push? > How do I see changes made in these files from version to version? Apart from directly using the actual git repo outside of pharo, you can use the facade provided by IceRepository, or you can use libgit inside Pharo. E.g. to add an extern

Re: [Pharo-users] Iceberg and resource files

Hi Ken, Some days ago I published a package to manage download of resources from Metacello configurations. Have a look at https://github.com/hernanmd/MetacelloFileDownload Hernán 2018-01-27 11:38 GMT-03:00 kmo : > I don't understand how iceberg handles resource files that you might also > like

Re: [Pharo-users] Iceberg and resource files

OK. I thought that this was more or less the case. Thanks. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Iceberg and resource files

You can version such code in your repo using git. Now Iceberg does not manage them (from what I understood). We will probably have a kind of GitRepo file Location so that you can know from where you want to load such files. (Right now pointing to "IceRepository default" should work). Stef On Sat

Re: [Pharo-users] Iceberg Branching

Hi, I think it's ok. I had accidentally gotten a 70 alpha version. Workflow seems fine on 61 and 70 stable versions. I tried to go in again and see what the error message was on the alpha version, but something else went wrong, and then I discovered that it had somehow found my actual working repo

Re: [Pharo-users] Iceberg Branching

yes, as Stef says, branching works ok… maybe you can describe what you are trying to do, in case is a workflow not yet covered? Esteban > On 14 Jan 2018, at 10:23, Stephane Ducasse wrote: > > Hi evan > > can you describe what you are doing because branching normally works? > I know that esteb

Re: [Pharo-users] Iceberg Branching

Hi evan can you describe what you are doing because branching normally works? I know that esteban was working on support to be able load submitted pull requests directly from the branch history. Guillermo and Pablo are making progress on refactoring the core of iceberg. They are arriving to the po

Re: [Pharo-users] Iceberg, Git and Package version

Hi Stef For example, my project can depend on Iceberg using the following definition: spec baseline: 'Iceberg' with: [ spec repository: > 'github://pharo-vcs/iceberg/:' ]; But now suppose my project have one package that depends on Iceberg "minimal" and other that depends on the "default" group

Re: [Pharo-users] Iceberg, Git and Package version

Hi vitor I'm sorry but I do not understand your question? can you rephrase it and give an example? Stef On Sat, Dec 30, 2017 at 10:03 PM, Vitor Medina Cruz wrote: > Hello Stephane > > What if I want to define two projects for the same baseline: both pointing > to different groups? > > >

Re: [Pharo-users] Iceberg, Git and Package version

Hello Stephane What if I want to define two projects for the same baseline: both pointing to different groups? Livre de vírus. www.avg.com

  1   2   >