Re: [Pharo-users] Metacello with Git

Pavel Krivanek-3 wrote > the pull request was against the issue branch, not the development one, so > the merging of it had no real effect Oops, he he thanks. - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Metacello with Git

thanks! > On 2 Feb 2018, at 10:12, Pavel Krivanek wrote: > > the pull request was against the issue branch, not the development one, so > the merging of it had no real effect. I created a new one > (https://github.com/pharo-project/pharo/pull/790 >

Re: [Pharo-users] Metacello with Git

the pull request was against the issue branch, not the development one, so the merging of it had no real effect. I created a new one ( https://github.com/pharo-project/pharo/pull/790) -- Pavel 2018-02-02 9:47 GMT+01:00 Esteban Lorenzano : > yes, I asked Pavel to look at it… > > Esteban > > > On

Re: [Pharo-users] Metacello with Git

yes, I asked Pavel to look at it… Esteban > On 2 Feb 2018, at 09:38, Guillermo Polito wrote: > > I've seen that the other day. The package is in the repository but is not > loaded in the image. Probably somebody committed it but not added it into any > baseline. > > On Fri, Feb 2, 2018 at 4:

Re: [Pharo-users] Metacello with Git

I've seen that the other day. The package is in the repository but is not loaded in the image. Probably somebody committed it but not added it into any baseline. On Fri, Feb 2, 2018 at 4:35 AM, Sean P. DeNigris wrote: > An image with build 454 seems still not to have MCGitlabRepository present.

Re: [Pharo-users] Metacello with Git

An image with build 454 seems still not to have MCGitlabRepository present. What am I missing? Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, which has the package in its source: https://github.com/pharo-project/pharo/tree/3641442f3ba0613cd9a6428181487ea29e62418c/src/Metacell

Re: [Pharo-users] Metacello with Git

Sean P. DeNigris wrote > These both have been integrated. Hmm, I'm confused. PR #667, which seems definitely to include MCGitlabRepository, has been merged into the dev branch [1], but MCGitlabRepository is not present in a fresh Pharo 7 image with "Build information: Pharo-7.0+alpha.build.438.sha

Re: [Pharo-users] Metacello with Git

Sean P. DeNigris wrote > 20953: Gitlab Private Project Support (via Iceberg) > https://pharo.fogbugz.com/f/cases/20953/ > > PRs issued > - https://github.com/pharo-project/pharo/pull/667 > - https://github.com/pharo-vcs/iceberg/pull/559 These both have been integrated. Will someone confirm they a

Re: [Pharo-users] Metacello with Git

EstebanLM wrote > yep. that seems to be a bug. 20953: Gitlab Private Project Support (via Iceberg) https://pharo.fogbugz.com/f/cases/20953/ PRs issued - https://github.com/pharo-project/pharo/pull/667 - https://github.com/pharo-vcs/iceberg/pull/559 - Cheers, Sean -- Sent from: http://forum

Re: [Pharo-users] Metacello with Git

>> >> About pillar, we are working on a new pipeline and lot of cleaning >> compared to the version available on smalltalkhub. >> The new version Branch new pipeline seems broken (I will check it >> tomorrow it cannot handle internal references). >> I want to be able to build the old books with the

Re: [Pharo-users] Metacello with Git

Hi Stef, On 2 January 2018 at 20:11, Stephane Ducasse wrote: > Hi Alistair > > About pillar, we are working on a new pipeline and lot of cleaning > compared to the version available on smalltalkhub. > The new version Branch new pipeline seems broken (I will check it > tomorrow it cannot handle in

Re: [Pharo-users] Metacello with Git

> Am 03.01.2018 um 00:26 schrieb Sean P. DeNigris : > > EstebanLM wrote >> yep. that seems to be a bug. > > Okay, I hacked a solution. Before I submit the fix I want to verify: no one > has been successfully using gitlab:// URLs in a MetaC baseline spec for a > private dependent project (access

Re: [Pharo-users] Metacello with Git

EstebanLM wrote > yep. that seems to be a bug. Okay, I hacked a solution. Before I submit the fix I want to verify: no one has been successfully using gitlab:// URLs in a MetaC baseline spec for a private dependent project (accessed via SSH keys), right? - Cheers, Sean -- Sent from: http://

Re: [Pharo-users] Metacello with Git

Hi Alistair About pillar, we are working on a new pipeline and lot of cleaning compared to the version available on smalltalkhub. The new version Branch new pipeline seems broken (I will check it tomorrow it cannot handle internal references). I want to be able to build the old books with the new

Re: [Pharo-users] Metacello with Git

Hi Sean, On 2 January 2018 at 18:00, Sean P. DeNigris wrote: > EstebanLM wrote >> if you have iceberg metacello integration enabled… Then it works on >> baselines, etc. > > Strange. I did `Iceberg enableMetacelloIntegration: true.` first and still > got the error. I can't easily test in 7 because

Re: [Pharo-users] Metacello with Git

> On 2 Jan 2018, at 18:00, Sean P. DeNigris wrote: > > EstebanLM wrote >> if you have iceberg metacello integration enabled… Then it works on >> baselines, etc. > > Strange. I did `Iceberg enableMetacelloIntegration: true.` first and still > got the error. I can't easily test in 7 because it d

Re: [Pharo-users] Metacello with Git

EstebanLM wrote > if you have iceberg metacello integration enabled… Then it works on > baselines, etc. Strange. I did `Iceberg enableMetacelloIntegration: true.` first and still got the error. I can't easily test in 7 because it depends on Magritte which depends on Grease which doesn't seem to lo

Re: [Pharo-users] Metacello with Git

if you have iceberg metacello integration enabled (default in 7.0), the repository is resolved as part of iceberg and then it does not instances a MC*Repository but an IceMetacelloRepositoryAdaptor. Then it works on baselines, etc. Esteban > On 2 Jan 2018, at 17:18, Sean P. DeNigris wrote: >

Re: [Pharo-users] Metacello with Git

EstebanLM wrote > MC*Repository is not iceberg but monticello api. Except it is extended by Iceberg-Adapters for #httpsUrl and #scpUrl! Also, MCBitbucketRepository is hardcoded in IceProviderRepositoryType>>#mcRepository, which was mangling the URL (off the top of my head I assume because 'bitbuc

Re: [Pharo-users] Metacello with Git

> On 2 Jan 2018, at 16:43, Sean P. DeNigris wrote: > > Vitor Medina Cruz wrote >>> I don't know for gitlab. > > It doesn't seem to work (in Pharo 6.1). `LGit_GIT_EEOF`. I see there is > MCBitbucketRepository but no MCGitlabRepository. MC*Repository is not iceberg but monticello api. Iceberg

Re: [Pharo-users] Metacello with Git

Vitor Medina Cruz wrote >> I don't know for gitlab. It doesn't seem to work (in Pharo 6.1). `LGit_GIT_EEOF`. I see there is MCBitbucketRepository but no MCGitlabRepository. - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Metacello with Git

On Wed, Dec 20, 2017 at 06:08:16PM +0100, Thierry Goubier wrote: > >Iceberg does, with RSA keys. Iceberg didn't work for me with ED25519 keys. > does command line git work with those ED25519 keys? Yes. I have been using GH with ED25519 keys. I added RSA keys to my GH setup specifically for Iceber

Re: [Pharo-users] Metacello with Git

> Am 21.12.2017 um 15:54 schrieb Sean P. DeNigris : > > NorbertHartl wrote >> I have projects that are loaded from bitbucket private repos and that have >> dependencies to… private bitbucket repos all at once. > > Is `Iceberg enableMetacelloIntegration: true` what gets around the tarball / > SS

Re: [Pharo-users] Metacello with Git

NorbertHartl wrote > I have projects that are loaded from bitbucket private repos and that have > dependencies to… private bitbucket repos all at once. Is `Iceberg enableMetacelloIntegration: true` what gets around the tarball / SSH-support issue? - Cheers, Sean -- Sent from: http://forum.w

Re: [Pharo-users] Metacello with Git

> Am 21.12.2017 um 03:27 schrieb Sean P. DeNigris : > > Tudor Girba-2 wrote >> We also use private GitHub projects with Iceberg and it works fine. >>> Au contraire! It works really good with SSH keys. I work all day with it. >>> I added support for bitbucket to iceberg because I’m using bitbucke

Re: [Pharo-users] Metacello with Git

Tudor Girba-2 wrote > We also use private GitHub projects with Iceberg and it works fine. >> Au contraire! It works really good with SSH keys. I work all day with it. >> I added support for bitbucket to iceberg because I’m using bitbucket >> private repos in my company. This is very intriguing. So

Re: [Pharo-users] Metacello with Git

Hi Pierce, Le 20/12/2017 à 17:17, Pierce Ng a écrit : On Tue, Dec 19, 2017 at 07:07:16PM -0800, Dale Henrichs wrote: I am under the impression that iceberg is able to authenticate with SSH keys I am not a pharo/iceberg user myself, but it seems that iceberg should be able to fill that gap.

Re: [Pharo-users] Metacello with Git

On 12/20/17 2:53 AM, Vitor Medina Cruz wrote: These days, we are getting to the point where I am beginning to flip the question on it's head and begin thinking that it should be possible for  a developer to choose to have have the github:// url interpreted as "create a local cl

Re: [Pharo-users] Metacello with Git

On Tue, Dec 19, 2017 at 07:07:16PM -0800, Dale Henrichs wrote: > I am under the impression that iceberg is able to authenticate with > SSH keys I am not a pharo/iceberg user myself, but it seems > that iceberg should be able to fill that gap. Iceberg does, with RSA keys. Iceberg didn't work f

Re: [Pharo-users] Metacello with Git

Hi, We also use private GitHub projects with Iceberg and it works fine. Cheers, Doru > On Dec 20, 2017, at 10:50 AM, Norbert Hartl wrote: > > > >> Am 20.12.2017 um 04:02 schrieb Sean P. DeNigris : >> >> CyrilFerlicot wrote >>> For bitbucket you can use bitbucket://. >>> I don't know for gi

Re: [Pharo-users] Metacello with Git

> > These days, we are getting to the point where I am beginning to flip the > question on it's head and begin thinking that it should be possible for a > developer to choose to have have the github:// url interpreted as "create a > local clone of the remote repository" instead of "download a tarb

Re: [Pharo-users] Metacello with Git

> Am 20.12.2017 um 04:02 schrieb Sean P. DeNigris : > > CyrilFerlicot wrote >> For bitbucket you can use bitbucket://. >> I don't know for gitlab. > > Unless something has changed, the cool git URLs only work for public > projects. In any case, it was not possible to authenticate with SSH keys

Re: [Pharo-users] Metacello with Git

Sean, I am under the impression that iceberg is able to authenticate with SSH keys I am not a pharo/iceberg user myself, but it seems that iceberg should be able to fill that gap. Dale On 12/19/17 7:02 PM, Sean P. DeNigris wrote: CyrilFerlicot wrote For bitbucket you can use bitbucke

Re: [Pharo-users] Metacello with Git

CyrilFerlicot wrote > For bitbucket you can use bitbucket://. > I don't know for gitlab. Unless something has changed, the cool git URLs only work for public projects. In any case, it was not possible to authenticate with SSH keys last time I checked (so I could not use them)… - Cheers, Sea

Re: [Pharo-users] Metacello with Git

Thanks. On Tue, Dec 19, 2017 at 4:40 PM, Cyril Ferlicot D. wrote: > Le 19/12/2017 à 19:25, Vitor Medina Cruz a écrit : > > Hello, > > > > Using github:/// metacello works fine, but is > > there another more general way of refering to a remote git repo? From > > BitBucket or Gitlab for example. >

Re: [Pharo-users] Metacello with Git

BitBucket is supported with like Github with: butbucket:///. With regards to GitLab, their download zip format is/was different enough from BitBucket/Github to make it difficult to provide the same level of support. See the series of comments here[1]. When the github:// was first introduced

Re: [Pharo-users] Metacello with Git

Le 19/12/2017 à 19:25, Vitor Medina Cruz a écrit : > Hello, > > Using github:/// metacello works fine, but is > there another more general way of refering to a remote git repo? From > BitBucket or Gitlab for example. > Hi, For bitbucket you can use bitbucket://. I don't know for gitlab. Anyway

[Pharo-users] Metacello with Git

Hello, Using github:/// metacello works fine, but is there another more general way of refering to a remote git repo? From BitBucket or Gitlab for example. Regards, Vitor

Re: [Pharo-users] Metacello with git

Hi, you can use gitfiletree (for Mac and Linux); you have to ensure ConfigurationOfGitFileTree is loaded in your configuration. Have a look at ConfigurationOfSmaCC and ConfigurationOfAltBrowser for examples (in the Pharo3 configuration browser). Thierry Le 19/05/2014 11:46, Laurent Laffont

Re: [Pharo-users] Metacello with git

spec repository: ‘filetree://relative-path-to-your-repository' is a bit annoying because you have to hardcode the directory but well… I already asked for an override functionality in metacello, but still not implemented. Esteban On 19 May 2014, at 11:46, Laurent Laffont wrote: > Hi, > > H

[Pharo-users] Metacello with git

Hi, How to specify a git filetree repository (but not github) in a Metacello Configuration ? Laurent