I just tried it on my Ubuntu workstation and it appeared to save
everything like it should. So it seems specific to the Windows version.
On 6/14/2016 11:37 PM, Bernardo Ezequiel Contreras wrote:
im on debian with
Pharo5.0
Latest update: #50760
i just add a whitespace in the class comment of
im on debian with
Pharo5.0
Latest update: #50760
i just add a whitespace in the class comment of the class RxParser and then
follow your steps, saving the slice locally in a directory.
On Wed, Jun 15, 2016 at 12:08 AM, Mark Bratcher wrote:
> Thanks for trying it. Are you
Thanks for trying it. Are you on Windows and Pharo 5.0?
Can you tell me what item you changed? I'd be curious just to try the
same thing.
On 6/14/2016 11:04 PM, Bernardo Ezequiel Contreras wrote:
i tried your steps locally in a directory with a fake change and i
couldnt reproduce the bug,
i tried your steps locally in a directory with a fake change and i couldnt
reproduce the bug, i got the slice and the dependent package(with the fake
change).
please report it, someone with more knowledge should check it.
On Tue, Jun 14, 2016 at 11:54 PM, Mark Bratcher
Just saving the slice to the repository (as the instructions indicate)
does not save the code also, and Monticello marks the slice and
associated packages all clean when just saving the slice. So I'm
thinking bug...?
On 6/14/2016 10:38 PM, Bernardo Ezequiel Contreras wrote:
the slice has no
the slice has no code, it just a reference to the dependencies (the dirty
packages), those dirty packages should be save in the repository(files
ended with mcz in your directory)
if you don't have those files in the local repository(directory), theres a
bug.
On Tue, Jun 14, 2016 at 11:33 PM, Mark
I opened the MCZ file saved for the slice package and it has no code
changes in it. It just has the dependency information. So it does seem
that more has to be saved to the repository than just the SLICE. Or, the
SLICE operation isn't "capturing" the code properly as part of the
package. In
I have the same error, even if I save the slice to a local repository.
So my steps are:
1) Open a clean Pharo 5.0 image
2) Modify one class#selector in Regex-Core
3) "Accept" the change (it prompts me to enter my name, which I do as
MarkBratcher)
4) Open Monticello, and see "*Regex-Core
there's something fishy going on. (the dependency wasn't save to the inbox).
in the other hand, the contribution steps could be improved
On Tue, Jun 14, 2016 at 11:03 PM, Mark Bratcher wrote:
> Bernardo
>
> Thank you. That's a good idea. I'll try that. I was surprised that
Bernardo
Thank you. That's a good idea. I'll try that. I was surprised that it didn't go
to the inbox as I thought I set up the repository path properly.
Mark
Sent from TypeApp
On Jun 14, 2016, 10:00 PM, at 10:00 PM, Bernardo Ezequiel Contreras
wrote:
>i forgot to
Hi mark,
it seems that your package: Regex-Core-MarkBratcher.39.mcz is not the
inbox.
if you have the package, then you can Copy(button in the monticello
browser) it to the inbox, and try again.
On Tue, Jun 14, 2016 at 9:53 PM, Mark Bratcher wrote:
> I am trying to push
11 matches
Mail list logo