Thanks Levente -- I did try adding the password to the repo details.
I've just been trying to log in to source.squeak.org via a browser, and
that isn't working either, so I've emailed box-admins@ to see if someone
could take a look for me.

Regards,
  Tony


On 1/29/19 6:44 PM, Levente Uzonyi wrote:
> Hi Tony,
> 
> You have to add your username and password to the Trunk repository. Open
> the Monticello Browser, right click on the Trunk repository's line,
> select edit repository info and change the content to:
> 
> MCHttpRepository
>     location: 'https://source.squeak.org/trunk'
>     user: 'tonyg'
>     password: '*****'
> 
> with your actuall password instead of stars of course.
> Note that I used https instead of http, because SSL has recently been
> enabled on source.squeak.org.
> 
> Once done, you'll be able to commit to Trunk directly, but I suggest you
> only do that when you're 100% sure that your changes work.
> I prefer to save work to the package cache first, then load it to a
> Trunk image and once it works there, I just use the copy feature of MC
> to copy the package to the Trunk.
> 
> Since you have already commited your changes to the Inbox, I suggest you
> log in to https://source.squeak.org via a web browser, select the Inbox
> repository, navigate to the Latest tab, find the package you want to
> move to the Trunk, click on details, and finally click on the Move to
> The Trunk button. That way you won't have to clean the packages from the
> Inbox.
> 
> Levente
> 
> On Tue, 29 Jan 2019, Tony Garnock-Jones wrote:
> 
>> Hi all,
>>
>> Sorry if this is a stupid question, but I just now tried to use my Core
>> Committer powers for the first time (!) to save a .mcz directly to
>> trunk, and it complained I was not authorized.
>>
>> What am I doing wrong, do you think?
>>
>> I'd completely understand if, in the year (!!) since I was admitted to
>> Core Committer status, my not actually getting time to do any committing
>> has led to that status being revoked, for example...
>>
>> ... or it could also be that I missed the memo on how I'm supposed to
>> proceed to get commits onto trunk, in which case sorry.
>>
>> Tony
>>
>>
>>
>> On 1/29/19 5:48 PM, commits at source.squeak.org wrote:
>>> A new version of Kernel was added to project The Inbox:
>>> http://source.squeak.org/inbox/Kernel-tonyg.1212.mcz
>>>
>>> ==================== Summary ====================
>>>
>>> Name: Kernel-tonyg.1212
>>> Author: tonyg
>>> Time: 29 January 2019, 5:20:15.285274 pm
>>> UUID: b291eae8-dfde-4ee1-b5dd-a351cb270ec9
>>> Ancestors: Kernel-mt.1211, Kernel-tonyg.1153
>>>
>>> Merge "Improve promise resolution error handling via #fulfillWith:."
>>>
>>> =============== Diff against Kernel-mt.1211 ===============
>>>
>>> Item was added:
>>> + ----- Method: Promise>>fulfillWith: (in category 'resolving') -----
>>> + fulfillWith: aBlock
>>> +     self fulfillWith: aBlock passErrors: rejecters isEmpty!
>>>
>>> Item was added:
>>> + ----- Method: Promise>>fulfillWith:passErrors: (in category
>>> 'resolving') -----
>>> + fulfillWith: aBlock passErrors: aBoolean
>>> +     "Evaluate aBlock. If it signals an exception, reject this
>>> promise with the exception
>>> +     as the argument; if it returns a value [or another Promise],
>>> resolve this promise
>>> +     with the result.
>>> + +     If aBoolean is true, and an exception is signaled, it is
>>> passed out to the caller.
>>> +     If aBoolean is false, signaled exceptions are considered
>>> handled after the promise
>>> +     has been rejected."
>>> +     [ self resolveWith: aBlock value ]
>>> +         on: Exception
>>> +         do: [ :ex |
>>> +             (ex isKindOf: Halt)
>>> +                 ifTrue: [ex pass]
>>> +                 ifFalse: [
>>> +                     self rejectWith: ex.
>>> +                     aBoolean ifTrue: [ ex pass ] ]]!
>>>
>>>
>