Versionner and issue tracking

Evan Donahue wrote

I am presented with
a prompt for "Retrieve Slice title" with a field for "issue number" and
"title."

What version of Pharo are you using (major version and update number)?

pharo --version returns "3.9-7" and the image's about pane lists "Latest update: #30848" Is either of those the relevant statistic?

I should also note that I can't seem to find a way to dismiss the issue tracker window one way or another and ended up killing the vm process. Probably missing something obvious.

Thanks,
Evan

Evan Donahue wrote

pharo --version returns "3.9-7" and the image's about pane lists "Latest update: #30848" Is either of those the relevant statistic?

The first one is the VM version. The second is what I was after. In Pharo's system, #30848 means version 3.0, update 848.

I tried to recreate your problem in #30848.

Background: The window you're describing references issue-tracking-like things because it started life as part of our Pharo contribution process and ended up doing double duty in Versionner because its quite useful. However, it is somewhere geared to the contribution use case of always committing to one repository (the Pharo inbox)

Because of this history, right now all packages in the project have to be associated to a common repository to commit via that window. On the right side of the window, just below center, there is a "Remote" dropdown. If your project's packages share a common repository, select it here and you will avoid the Issue# dialog. If not, use the MC Browser to commit them individually the old fashioned way for now. [World Menu]->[Monticello Browser]

HTH

Evan Donahue wrote

I can't seem to find a way to dismiss the issue tracker window one way or another and ended up killing the vm process

In my image, the dialog layout is off, and the buttons are /almost/ completely out of view, but I can see the tops. The one on the right is the Cancel button. Or, you can bring up the halos on the window and close it that way. Or, you could (but it's not efficient in this case) do it programmatically, but no you should never have to quit via the VM for this kind of problem. Welcome to a live, dynamic, turtles all the way down experience :)

Halos! Of course! Thanks, new smalltalker here. Your advice in the other message proved key. I had set the ConfigurationOf's repo, but didn't realize I had to manually set the repo for each package on the commit screen. I have now uploaded and downloaded to a new image and everything works.

Thanks,
Evan

Evan Donahue wrote

everything works

:)