Do I really have to configure the inbox repository for each single package?

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

Do I really have to configure the inbox repository for each single package?

Christoph Thiede

Hi all,


in the meantime, I probably have a really boring question for you:

Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)


I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:

 (no package selected)

 (MorphicTests selected)


I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...

This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?


Thanks in advance,

Christoph



Carpe Squeak!
Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Levente Uzonyi
IIRC the Inbox repository was originally added to all core packages. Later
the repository was removed from the image altogether, and when it got
added back again, only the repository itself was added without but was not
attached to packages.

While we're discussing repositories, I think it's about time we changed
the default urls from http to https for everything hosted on
source.squeak.org.

Levente.

On Mon, 30 Dec 2019, Thiede, Christoph wrote:

>
> Hi all,
>
>
> in the meantime, I probably have a really boring question for you:
>
> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>
>
> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>
> [IMAGE] (no package selected)
>
> [IMAGE] (MorphicTests selected)
>
>
> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>
> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>
>
> Thanks in advance,
>
> Christoph
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Christoph Thiede

Alright. It would be great to have a button or a method to enter my credentials once for all packages ...


While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.


Wait, I have been communicating to source.squeak.org all the time without encryption? :o This is indeed bad. I just updated the wiki entry. In general, I wonder whether Monticello should warn before broadcasting any unencrypted credentials to the web ...

Best,
Christoph


Von: Squeak-dev <[hidden email]> im Auftrag von Levente Uzonyi <[hidden email]>
Gesendet: Dienstag, 31. Dezember 2019 02:15:15
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Do I really have to configure the inbox repository for each single package?
 
IIRC the Inbox repository was originally added to all core packages. Later
the repository was removed from the image altogether, and when it got
added back again, only the repository itself was added without but was not
attached to packages.

While we're discussing repositories, I think it's about time we changed
the default urls from http to https for everything hosted on
source.squeak.org.

Levente.

On Mon, 30 Dec 2019, Thiede, Christoph wrote:

>
> Hi all,
>
>
> in the meantime, I probably have a really boring question for you:
>
> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>
>
> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>
> [IMAGE] (no package selected)
>
> [IMAGE] (MorphicTests selected)
>
>
> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>
> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>
>
> Thanks in advance,
>
> Christoph
>
>
>


Carpe Squeak!
Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Chris Muller-3

Alright. It would be great to have a button or a method to enter my credentials once for all packages ...


+1 and would recommend the interface write the ./prefs/mcSettings file.  MC currently reads this file, if present, so you never have to enter credentials again, and keeps the sensitive parts out of the saved image memory.  You can create the file manually now, and you'll and never have to deal with it again, but we should be more welcoming to new users, there's nothing to tell them its there...
 


While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.

The other thing we need:  when the updateURL is changed to trunk, it needs to somehow re-order all the Packages repositori lists to put /trunk first, BELOW /squeak53, so that revisions will work...   Currently, it has to be done manually for each package...

 - Chris
 

Wait, I have been communicating to source.squeak.org all the time without encryption? :o This is indeed bad. I just updated the wiki entry. In general, I wonder whether Monticello should warn before broadcasting any unencrypted credentials to the web ...

Best,
Christoph


Von: Squeak-dev <[hidden email]> im Auftrag von Levente Uzonyi <[hidden email]>
Gesendet: Dienstag, 31. Dezember 2019 02:15:15
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Do I really have to configure the inbox repository for each single package?
 
IIRC the Inbox repository was originally added to all core packages. Later
the repository was removed from the image altogether, and when it got
added back again, only the repository itself was added without but was not
attached to packages.

While we're discussing repositories, I think it's about time we changed
the default urls from http to https for everything hosted on
source.squeak.org.

Levente.

On Mon, 30 Dec 2019, Thiede, Christoph wrote:

>
> Hi all,
>
>
> in the meantime, I probably have a really boring question for you:
>
> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>
>
> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>
> [IMAGE] (no package selected)
>
> [IMAGE] (MorphicTests selected)
>
>
> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>
> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>
>
> Thanks in advance,
>
> Christoph
>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Tobias Pape
In reply to this post by Levente Uzonyi

> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>
> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without but was not attached to packages.
>
> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.

This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…

-t


>
> Levente.
>
> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>
>> Hi all,
>> in the meantime, I probably have a really boring question for you:
>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>> [IMAGE] (no package selected)
>> [IMAGE] (MorphicTests selected)
>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>> Thanks in advance,
>> Christoph
>



Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Levente Uzonyi
On Tue, 31 Dec 2019, Tobias Pape wrote:

>
>> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>>
>> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without but was not attached to packages.
>>
>> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.
>
> This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…

I meant using https urls for the MCHttpRespositories in the image. Those
are independent of the server image except for redirects, but AFAIK there
are no redirects involved in up/downloading and repository listing.
I've been using https there for half a year now without problems.

Levente

>
> -t
>
>
>>
>> Levente.
>>
>> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>>
>>> Hi all,
>>> in the meantime, I probably have a really boring question for you:
>>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>>> [IMAGE] (no package selected)
>>> [IMAGE] (MorphicTests selected)
>>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>>> Thanks in advance,
>>> Christoph
>>

Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Tobias Pape

> On 31.12.2019, at 15:21, Levente Uzonyi <[hidden email]> wrote:
>
> On Tue, 31 Dec 2019, Tobias Pape wrote:
>
>>
>>> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>>> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without but was not attached to packages.
>>> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.
>>
>> This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…
>
> I meant using https urls for the MCHttpRespositories in the image. Those are independent of the server image except for redirects, but AFAIK there are no redirects involved in up/downloading and repository listing.
> I've been using https there for half a year now without problems.

That's good to know!
Let's switch.


Best regards
        -Tobias

PS: we're using https with our squeaksource for more than 2 1/2 years at HPI, no hickups either.


>
> Levente
>
>>
>> -t
>>
>>
>>> Levente.
>>> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>>>> Hi all,
>>>> in the meantime, I probably have a really boring question for you:
>>>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>>>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>>>> [IMAGE] (no package selected)
>>>> [IMAGE] (MorphicTests selected)
>>>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>>>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>>>> Thanks in advance,
>>>> Christoph
>



Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Nicolas Cellier
Hi all, Hi Tobias,
I'm using https: on OSX for some months too.

I have minor issues:
- each time I commit, the remote repository update fails while reading allFileNames
- from time to time, the connection is closed before the action is performed (browsing a repository, downloading a mcz, etc...).

That's a bit upsetting, but minor, I just close the debugger and retry.
I don't remember that it's been working OK with http for a long time.
So I'm for using https.

Le mar. 31 déc. 2019 à 17:36, Tobias Pape <[hidden email]> a écrit :

> On 31.12.2019, at 15:21, Levente Uzonyi <[hidden email]> wrote:
>
> On Tue, 31 Dec 2019, Tobias Pape wrote:
>
>>
>>> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>>> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without but was not attached to packages.
>>> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.
>>
>> This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…
>
> I meant using https urls for the MCHttpRespositories in the image. Those are independent of the server image except for redirects, but AFAIK there are no redirects involved in up/downloading and repository listing.
> I've been using https there for half a year now without problems.

That's good to know!
Let's switch.


Best regards
        -Tobias

PS: we're using https with our squeaksource for more than 2 1/2 years at HPI, no hickups either.


>
> Levente
>
>>
>> -t
>>
>>
>>> Levente.
>>> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>>>> Hi all,
>>>> in the meantime, I probably have a really boring question for you:
>>>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>>>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>>>> [IMAGE] (no package selected)
>>>> [IMAGE] (MorphicTests selected)
>>>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>>>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>>>> Thanks in advance,
>>>> Christoph
>





Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Nicolas Cellier
I forgot to say, OSX has 5 Socket tests failing:

SocketTest>>testSocketReuse in
self assert: recvProc isTerminated description: 'recvProc hasn''t terminated till the deadline';

SocketTest>>testUDP in
clientSocket sendData: 'Hello World'. (timeout)

SqueakSSLTest>>testSSLSockets in
server sslAccept: self certName. (error: 'SSL accept failed with code: -5')

Same for SqueakSSLTest>>testSocketAccept

SqueakSSLTest>>clientSocket sslConnect in
inbuf := self receiveData.
Same error message while #waitForDataIfClosed: (probably signalled by [sslServer accept] fork).

Le mar. 31 déc. 2019 à 18:09, Nicolas Cellier <[hidden email]> a écrit :
Hi all, Hi Tobias,
I'm using https: on OSX for some months too.

I have minor issues:
- each time I commit, the remote repository update fails while reading allFileNames
- from time to time, the connection is closed before the action is performed (browsing a repository, downloading a mcz, etc...).

That's a bit upsetting, but minor, I just close the debugger and retry.
I don't remember that it's been working OK with http for a long time.
So I'm for using https.

Le mar. 31 déc. 2019 à 17:36, Tobias Pape <[hidden email]> a écrit :

> On 31.12.2019, at 15:21, Levente Uzonyi <[hidden email]> wrote:
>
> On Tue, 31 Dec 2019, Tobias Pape wrote:
>
>>
>>> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>>> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without but was not attached to packages.
>>> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.
>>
>> This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…
>
> I meant using https urls for the MCHttpRespositories in the image. Those are independent of the server image except for redirects, but AFAIK there are no redirects involved in up/downloading and repository listing.
> I've been using https there for half a year now without problems.

That's good to know!
Let's switch.


Best regards
        -Tobias

PS: we're using https with our squeaksource for more than 2 1/2 years at HPI, no hickups either.


>
> Levente
>
>>
>> -t
>>
>>
>>> Levente.
>>> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>>>> Hi all,
>>>> in the meantime, I probably have a really boring question for you:
>>>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>>>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>>>> [IMAGE] (no package selected)
>>>> [IMAGE] (MorphicTests selected)
>>>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>>>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>>>> Thanks in advance,
>>>> Christoph
>





Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Levente Uzonyi
In reply to this post by Nicolas Cellier
Hi Nicolas,

On Tue, 31 Dec 2019, Nicolas Cellier wrote:

> Hi all, Hi Tobias,
> I'm using https: on OSX for some months too.
>
> I have minor issues:
> - each time I commit, the remote repository update fails while reading allFileNames
> - from time to time, the connection is closed before the action is performed (browsing a repository, downloading a mcz, etc...).
>
> That's a bit upsetting, but minor, I just close the debugger and retry.
> I don't remember that it's been working OK with http for a long time.
> So I'm for using https.
That seems to be the same issue Karl experienced on windows. The main
cause is probably that the connection gets closed, but WebClient doesn't
notice that until it tries to reuse it.
Does the issue still exist if you evaluate [MCHttpRepository
useSharedWebClientInstance: false]?

Levente

>
> Le mar. 31 déc. 2019 à 17:36, Tobias Pape <[hidden email]> a écrit :
>
>       > On 31.12.2019, at 15:21, Levente Uzonyi <[hidden email]> wrote:
>       >
>       > On Tue, 31 Dec 2019, Tobias Pape wrote:
>       >
>       >>
>       >>> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>       >>> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without
>       but was not attached to packages.
>       >>> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.
>       >>
>       >> This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…
>       >
>       > I meant using https urls for the MCHttpRespositories in the image. Those are independent of the server image except for redirects, but AFAIK there are no redirects involved in up/downloading and repository
>       listing.
>       > I've been using https there for half a year now without problems.
>
>       That's good to know!
>       Let's switch.
>
>
>       Best regards
>               -Tobias
>
>       PS: we're using https with our squeaksource for more than 2 1/2 years at HPI, no hickups either.
>
>
>       >
>       > Levente
>       >
>       >>
>       >> -t
>       >>
>       >>
>       >>> Levente.
>       >>> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>       >>>> Hi all,
>       >>>> in the meantime, I probably have a really boring question for you:
>       >>>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>       >>>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>       >>>> [IMAGE] (no package selected)
>       >>>> [IMAGE] (MorphicTests selected)
>       >>>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>       >>>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>       >>>> Thanks in advance,
>       >>>> Christoph
>       >
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

Nicolas Cellier
Thanks Levente,
so far, it works well.

Le mar. 31 déc. 2019 à 18:55, Levente Uzonyi <[hidden email]> a écrit :
Hi Nicolas,

On Tue, 31 Dec 2019, Nicolas Cellier wrote:

> Hi all, Hi Tobias,
> I'm using https: on OSX for some months too.
>
> I have minor issues:
> - each time I commit, the remote repository update fails while reading allFileNames
> - from time to time, the connection is closed before the action is performed (browsing a repository, downloading a mcz, etc...).
>
> That's a bit upsetting, but minor, I just close the debugger and retry.
> I don't remember that it's been working OK with http for a long time.
> So I'm for using https.

That seems to be the same issue Karl experienced on windows. The main
cause is probably that the connection gets closed, but WebClient doesn't
notice that until it tries to reuse it.
Does the issue still exist if you evaluate [MCHttpRepository
useSharedWebClientInstance: false]?

Levente

>
> Le mar. 31 déc. 2019 à 17:36, Tobias Pape <[hidden email]> a écrit :
>
>       > On 31.12.2019, at 15:21, Levente Uzonyi <[hidden email]> wrote:
>       >
>       > On Tue, 31 Dec 2019, Tobias Pape wrote:
>       >
>       >>
>       >>> On 31.12.2019, at 02:15, Levente Uzonyi <[hidden email]> wrote:
>       >>> IIRC the Inbox repository was originally added to all core packages. Later the repository was removed from the image altogether, and when it got added back again, only the repository itself was added without
>       but was not attached to packages.
>       >>> While we're discussing repositories, I think it's about time we changed the default urls from http to https for everything hosted on source.squeak.org.
>       >>
>       >> This needs changes to the image on the server, it forcefully serves some stuff with http:// in the url…
>       >
>       > I meant using https urls for the MCHttpRespositories in the image. Those are independent of the server image except for redirects, but AFAIK there are no redirects involved in up/downloading and repository
>       listing.
>       > I've been using https there for half a year now without problems.
>
>       That's good to know!
>       Let's switch.
>
>
>       Best regards
>               -Tobias
>
>       PS: we're using https with our squeaksource for more than 2 1/2 years at HPI, no hickups either.
>
>
>       >
>       > Levente
>       >
>       >>
>       >> -t
>       >>
>       >>
>       >>> Levente.
>       >>> On Mon, 30 Dec 2019, Thiede, Christoph wrote:
>       >>>> Hi all,
>       >>>> in the meantime, I probably have a really boring question for you:
>       >>>> Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)
>       >>>> I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:
>       >>>> [IMAGE] (no package selected)
>       >>>> [IMAGE] (MorphicTests selected)
>       >>>> I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...
>       >>>> This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?
>       >>>> Thanks in advance,
>       >>>> Christoph
>       >
>
>
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Do I really have to configure the inbox repository for each single package?

marcel.taeumel
In reply to this post by Christoph Thiede
Hi Christoph,

there is no need to have a button for everything. Maybe for this one, but not everything. :-D

So, instead, use this request of yours as an opportunity to write a small script that attaches the inbox to all your packages. Document the process of figuring out the piece of code you need to do that. Then share your experience on the discoverability and exploration of running tools and their source code.

Best,
Marcel

Am 30.12.2019 21:05:48 schrieb Thiede, Christoph <[hidden email]>:

Hi all,


in the meantime, I probably have a really boring question for you:

Is there any way to configure the inbox repo once for all Squeak packages? (Of course, there is a way, but I can't find it.)


I am strictly following the instructions from the wiki to create the repository, but it does not appear for any trunk package:

 (no package selected)

 (MorphicTests selected)


I admit that in all the time, I was too lazy to ask this questions so I added the repository again and again, for each single package I needed ...

This probably isn't the right way to do it, is it? How can I enter the inbox repo code once for all packages?


Thanks in advance,

Christoph