Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

Matthias Berth-2
Hi,


I was following

  http://code.google.com/p/pharo/wiki/HowToContribute

I have saved the patched package into my package-cache, giving
Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image
(pharo core 1.0rc 10505).

Then I wanted to save to PharoInbox, by selecting PharoInbox in
Monticello browser and clicking "save". Monticello asked for my
initials (no problem) and then it gave the package a new version
number Network-Protocols-MatthiasBerth.18.mcz. Is that expected
behavior? I cancelled that because I did not want to increase the
version number.

I tried again, now by following the instructions to the letter and
pressing the +Repository button. Same problem, even worse: now I got
version 19 (Network-Protocols-MatthiasBerth.19.mcz).

Do others see the same problem? Am I doing something stupid here?


Cheers

Matthias

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

Miguel Cobá
El mar, 12-01-2010 a las 18:52 +0100, Matthias Berth escribió:

> Hi,
>
>
> I was following
>
>   http://code.google.com/p/pharo/wiki/HowToContribute
>
> I have saved the patched package into my package-cache, giving
> Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image
> (pharo core 1.0rc 10505).
>
> Then I wanted to save to PharoInbox, by selecting PharoInbox in
> Monticello browser and clicking "save". Monticello asked for my
> initials (no problem) and then it gave the package a new version
> number Network-Protocols-MatthiasBerth.18.mcz. Is that expected
> behavior? I cancelled that because I did not want to increase the
> version number.
>
> I tried again, now by following the instructions to the letter and
> pressing the +Repository button. Same problem, even worse: now I got
> version 19 (Network-Protocols-MatthiasBerth.19.mcz).
>
> Do others see the same problem? Am I doing something stupid here?

Same happens to me. I don't care for the numbers :)

>
>
> Cheers
>
> Matthias
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
Miguel Cobá
http://miguel.leugim.com.mx


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

Gary Chambers-4
You should open your package cache repository and, for the required version,
choose "copy" then select the PharoInbox repository as destination.

Might be nice if MC effectively did this for saving working copies of saved
versions that have no changes.

Regards, Gary

----- Original Message -----
From: "Miguel Enrique Cobá Martinez" <[hidden email]>
To: <[hidden email]>
Sent: Tuesday, January 12, 2010 6:03 PM
Subject: Re: [Pharo-project] Monticello gives me new version numbers when I
just want to publish a fix to PharoInbox


> El mar, 12-01-2010 a las 18:52 +0100, Matthias Berth escribió:
>> Hi,
>>
>>
>> I was following
>>
>>   http://code.google.com/p/pharo/wiki/HowToContribute
>>
>> I have saved the patched package into my package-cache, giving
>> Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image
>> (pharo core 1.0rc 10505).
>>
>> Then I wanted to save to PharoInbox, by selecting PharoInbox in
>> Monticello browser and clicking "save". Monticello asked for my
>> initials (no problem) and then it gave the package a new version
>> number Network-Protocols-MatthiasBerth.18.mcz. Is that expected
>> behavior? I cancelled that because I did not want to increase the
>> version number.
>>
>> I tried again, now by following the instructions to the letter and
>> pressing the +Repository button. Same problem, even worse: now I got
>> version 19 (Network-Protocols-MatthiasBerth.19.mcz).
>>
>> Do others see the same problem? Am I doing something stupid here?
>
> Same happens to me. I don't care for the numbers :)
>
>>
>>
>> Cheers
>>
>> Matthias
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> Miguel Cobá
> http://miguel.leugim.com.mx
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

Simon Denier-3
In reply to this post by Matthias Berth-2

On 12 janv. 2010, at 18:52, Matthias Berth wrote:

> Hi,
>
>
> I was following
>
>  http://code.google.com/p/pharo/wiki/HowToContribute
>
> I have saved the patched package into my package-cache, giving
> Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image
> (pharo core 1.0rc 10505).
>
> Then I wanted to save to PharoInbox, by selecting PharoInbox in
> Monticello browser and clicking "save". Monticello asked for my
> initials (no problem) and then it gave the package a new version
> number Network-Protocols-MatthiasBerth.18.mcz. Is that expected
> behavior? I cancelled that because I did not want to increase the
> version number.
>
> I tried again, now by following the instructions to the letter and
> pressing the +Repository button. Same problem, even worse: now I got
> version 19 (Network-Protocols-MatthiasBerth.19.mcz).
>
> Do others see the same problem? Am I doing something stupid here?


Yes it's the expected behavior for Monticello, which always increases the version number if you save the package. Instead, one you can do from the MC browser is to *copy* your version 17 to the PharoInbox (provided that PharoInbox is registered as a repository for the package)


--
 Simon




_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

Matthias Berth-2
In reply to this post by Gary Chambers-4
Gary, Simon,

thanks a lot -- I'll do a copy then.

Cheers

Matthias

On Tue, Jan 12, 2010 at 7:10 PM, Gary Chambers
<[hidden email]> wrote:

> You should open your package cache repository and, for the required version,
> choose "copy" then select the PharoInbox repository as destination.
>
> Might be nice if MC effectively did this for saving working copies of saved
> versions that have no changes.
>
> Regards, Gary
>
> ----- Original Message -----
> From: "Miguel Enrique Cobá Martinez" <[hidden email]>
> To: <[hidden email]>
> Sent: Tuesday, January 12, 2010 6:03 PM
> Subject: Re: [Pharo-project] Monticello gives me new version numbers when I
> just want to publish a fix to PharoInbox
>
>
>> El mar, 12-01-2010 a las 18:52 +0100, Matthias Berth escribió:
>>> Hi,
>>>
>>>
>>> I was following
>>>
>>>   http://code.google.com/p/pharo/wiki/HowToContribute
>>>
>>> I have saved the patched package into my package-cache, giving
>>> Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image
>>> (pharo core 1.0rc 10505).
>>>
>>> Then I wanted to save to PharoInbox, by selecting PharoInbox in
>>> Monticello browser and clicking "save". Monticello asked for my
>>> initials (no problem) and then it gave the package a new version
>>> number Network-Protocols-MatthiasBerth.18.mcz. Is that expected
>>> behavior? I cancelled that because I did not want to increase the
>>> version number.
>>>
>>> I tried again, now by following the instructions to the letter and
>>> pressing the +Repository button. Same problem, even worse: now I got
>>> version 19 (Network-Protocols-MatthiasBerth.19.mcz).
>>>
>>> Do others see the same problem? Am I doing something stupid here?
>>
>> Same happens to me. I don't care for the numbers :)
>>
>>>
>>>
>>> Cheers
>>>
>>> Matthias
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> Miguel Cobá
>> http://miguel.leugim.com.mx
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project