Box-Admins

box-admins@lists.squeakfoundation.org

958 discussions

Re: [Box-Admins] [squeak-dev] Request to manually move the following SqueakSource versions
by Chris Muller 08 Oct '22

08 Oct '22

May we not move 74 to trunk like that? Would you please remake a new version in the correct encoding (utf8, I presume)? Then, resend the full list of what you want where concisely (so I don't have to look at multiple emails) and I will take care of all of them at once. On Thu, Oct 6, 2022 at 8:27 AM Thiede, Christoph < Christoph.Thiede(a)student.hpi.uni-potsdam.de> wrote: > Hi all, dear SqueakSource admins, > > > the following inbox versions need to be moved from the inbox, but I cannot > do this myself because the details page in the web interface won't load > (presumably due to an encoding error): > > > please move to the treated inbox: Regex-Core-ct.68, Regex-Core-ct.71 > please move to the trunk: Regex-Core-ct.74 > > Could someone do this manually from the backend, please? I will take care > not to add any non-ascii characters to a Monticello version's description > again in the future ... > > > Best, > > Christoph > >

1 0

Re: [Box-Admins] [Board] Squeak | Let's migrate to Hetzner
by Chris Muller 05 Jul '22

05 Jul '22

Hi Levente, I'm willing to support the migration of source.squeak.org to the new server, if desirable, including some beyond the initial migration. Thanks for any assistance in helping me get going. After adjusting my ~/.ssh/config file to the new IP addresses and trying to ssh into ian, I got a "This account is currently not available." message (see below). I tried one more time with my username, but it reported "Too many authentication failures". It's possible I did something wrong. - Chris ____ ~$ ssh ian The authenticity of host '116.203.28.174 (116.203.28.174)' can't be established. ED25519 key fingerprint is SHA256:CmQ9VWvhitm5WwLc5GTsbWap47WyfLH4OCUILrYBSYM. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '116.203.28.174' (ED25519) to the list of known hosts. Linux ian 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed Jun 22 11:13:01 2022 from 91.83.13.73 This account is currently not available. Connection to 116.203.28.174 closed. ~$ ssh chrismuller@ian Received disconnect from 116.203.28.174 port 22:2: Too many authentication failures Disconnected from 116.203.28.174 port 22 ____ On Mon, May 23, 2022 at 4:08 AM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > > Hi Marcel, > > We currently have a server which has the containers set up on them. > The ip address of the server is 116.203.28.174. > > Everyone who has an account on rackspace can ssh into to that server with > their existing ssh keys using the ssh user just like on ian but, the ssh > port is kept 22 for now. > > The containers are avaiable on the 10.98.1.0/24 prefix: > 10.98.1.2 alan > 10.98.1.3 adele > 10.98.1.4 andreas > 10.98.1.5 dan > 10.98.1.6 david > 10.98.1.7 scott > 10.98.1.8 ted > > Everyone who has an account to the servers on rackspace can log into these > containers with their existing ssh keys, and everyone has sudo access the > same way as on rackspace. > > We unified the account names so Vanessa and Craig have the username > vanessa and craig on all servers they had access to, respectively. > > The setup is not complete yet. There still are things left to do. > The containers will surely be rebuilt, perhaps the whole server as well, > so don't expect things to persist yet. > > What's left to do before migration to the new server can start is to: > - configure the firewalls of the individual containers > - configure the main server's firewall to forward ports where needed to > - create volumes for some of the containers as we don't have enough space > on the server to host everything > - make the server restart-proof > > Since we're short on time, we won't automate the installation of software > into containers yet. But it would be worth to puruse that to have a > well-documented and repeatable installation process. > > We encourage everyone to log in and have a look around to see if things > work as expected. > > > Levente > > P.S.: @Tony, your key has been added to the authorized keys as well with > the username tonyg. > > On Wed, 18 May 2022, Marcel Taeumel wrote: > > > Hi Levente -- > > What's the current status on the playbooks? :-) > > > > Best, > > Marcel > > > > Am 10.05.2022 13:19:20 schrieb Marcel Taeumel <marcel.taeumel(a)hpi.de>: > > > > Hi Levente -- > > Thank you for doing this! > > > > I just set up an account at Hetzner and will ask the SFC/Pono whether that project-based solution would work for them. > > > > I will also try to set up Hetzner's Cloud DNS with some help from Tobias. Then we can start asking those domain holders to update their entries. And the switch over from Rackspace to Hetzner will be easier once we set > > up Squeak's services there. > > > > Best, > > Marcel > > > > Am 26.04.2022 22:28:05 schrieb Levente Uzonyi <leves(a)caesar.elte.hu>: > > > > Hi Marcel, > > > > On Thu, 21 Apr 2022, Marcel Taeumel wrote: > > > > > Hi Levente -- > > > > > > At yesterday's board meeting, we agreed on migrating back to Hetzner again. We are also grateful for the options/plans you outlined. We agreed on the following: > > > > > > - Single server with containers > > > - Plan #3 (i.e., CX41 + 290GB) if it won't be too difficult to add extra storage later if needed; otherwise Plan #2 (i.e., CX41 + 540GB) > > > - No built-in backup feature of the server (as we should figure out a way to backup both server and storage anyway) > > > > > > While there are a few more volunteers, we would be *very* happy if you would organize (or even perform most of) the migration. Feel free to contact the following people to distribute some of the effort as > > they are happy to help as well: > > > > > > - Bruce (bruce.oneel(a)pckswarms.ch) > > > - Tony (tonyg(a)leastfixedpoint.com) > > > - Dave (lewis(a)mail.msen.com -- SqueakSource) > > > - Chris (ma.chris.m(a)gmail.com -- SqueakSource) > > > - Marcel (marcel.taeumel(a)hpi.de -- DNS updates via e-mail) > > > > > > Yes, you can go ahead and write ansible playbooks to set up servers using lxc containers. If you encounter unforeseen challenges that could eat up a lot of your time, do not hesitate but inform the board. > > > > The playbooks for the server layout are in progress. There are a few > > things that need some extra time: > > - we're upgrading the OS from jessie to bullseye, and there are some > > differences how lxc works in bullseye than in other debian versions > > - we need IPv6 support (because of the smtp server) and no DHCP > > (containers get a dynamic IP address by default but it's better for us if > > they are static) > > - set up wireguard and route traffic to the containers > > through it > > - set up the firewall to replicate what's on rackspace > > > > > > > > We assume that all current services and (SSH) login information can be retained. > > > > The idea is to use wireguard[1] as the main connection point, and then log > > in to the containers through ssh. That way we could avoid the tcp-over-tcp > > access to the servers and have different layers of security. > > To answer your question, yes, the existing users will be recreated in > > the containers and the ssh keys will be copied there as well, even though > > they'll only be needed to manually fix anomalies. > > > > > > > > *** > > > > > > To get started, please set up an account at Hetzner and configure the required service. DO NOT use any existing account of your own as we will share the credentials with the SFC so that they can > > enter/update the billing information. So, create a new account and drop the credentials here: > > > > > > https://www.hpi.uni-potsdam.de/hirschfeld/cloud/s/PsrPXGgHM5HjkBx > > > PW: GLGMqj7cD9 > > > > > > I will then contact Pono/SFC to enter the billing info. If there is any chance that you might pay the first month from your own pocket, we will make sure to reimburse you. > > > > > > (If you learn about that sub-accounts at Hetzner can actually be used to change billing info, please let me know as we then do not have to pass on our credentials to the SFC. Yet, to my knowledge, this is > > not possible.) > > > > According to the documentation[2], the SFC should create a Project for > > the Squeak servers, and invite someone from the Squeak community > > (preferrably from the board) as an Admin of that Project. > > The Admin can create any kind of resources but does not have access to the > > billing information. > > If we automate as many things as I planned with ansible, only an API key > > will need to be created, the rest will be done by the ansible playbooks. > > The Admin user can invite box-admins as Restricted users to maintain the > > resources if needed. > > > > For the DNS, we can use Hetzner's DNS Console[3][4]. Since it's free, we > > don't have to get the SFC involved with that. For example, the Admin > > account can be the owner. > > > > > > Levente > > [1] https://www.wireguard.com/ > > [2] https://docs.hetzner.com/cloud/general/faq/#what-are-projects-and-how-can-i… > > [3] https://www.hetzner.com/dns-console > > [4] https://docs.hetzner.com/dns-console > > > > > > > > *** > > > > > > What do you think? :-) Is it feasible to be done with this by the end of May? What is your (most defensive) estimate? > > > > > > Best, > > > Marcel (on behalf of the Squeak Oversight Board) > > > > > > > > > > > > > > >

2 2

Re: [Box-Admins] [Board] Squeak Services | Inquiry to shutdown david/scott/john
by Levente Uzonyi 20 Apr '22

20 Apr '22

On Wed, 20 Apr 2022, Marcel Taeumel wrote: > Hi Levente, hi Tobias -- > >> P.P.S.: Is "ian" really necessary as SSH gateway? > >> Can this be reconfigured in an easy way? > > > > This requires reconfiguration of the whole login thing. > > Can be done, takes time. > > So, I presume that this cannot be done within a day or two. > Okay. Then let's focus on david/scott/john/cloudDB and leave > ian be for now. > > @Levente: Please try to delete david/scott/john/cloudDB. > If you get a note to call Rackspace, please do so OR send > me the particular identifiers so that I can ask Pono (SFC) > to do it for us. He is on the phone with them on a regular > basis these days. Yes, I get the ridiculous "If you are wanting to delete your cloud server, please call:..." message too when I try to delete the servers. All three servers are powered off, even though rackspace has not noticed that yet because "The Monitoring Agent is disconnected.". List of servers to be deleted: david: id: ad0c2b09-652b-4dd2-8d4e-d6ce76920de3 ip: 23.253.149.127 john: id: 43ab768e-6132-4418-b488-08ea28893555 ip: 104.239.174.108 scott: id: 2a1bd23d-1068-43bf-b739-d14958e31b0b ip: 162.242.248.154 Fortunately, I could delete the mysql database. Levente > > Best, > Marcel > > Am 20.04.2022 07:27:04 schrieb Pape, Tobias <tobias.pape(a)hpi.de>: > > Hi > > > On 20. Apr 2022, at 00:23, Levente Uzonyi wrote: > > > > Hi Marcel, > > > > On Tue, 19 Apr 2022, Marcel Taeumel wrote: > > > >> Hi box admins -- > >> Can we please backup and shutdown the following servers ASAP: > >> - david (planet.squeak) > >> - scott (mantis/codespeed) > >> - john (docker ... already inactive?) > > > > Is there anything useful on john to be backed up? > > no, it's off. I would have deleted it, but rackspace wanted me to _call_ them to remove it. > > > I've never seen that server before, I didn't have my ssh key added to it, I don't have a user on it. It was shut down but not deleted, so it was billed as if it had been running the whole time. > > I changed the root password on it and managed to log in. I only see some old docker images but no containers. > > It was used for the nextcloud thing but nobody cared so I shut it down. > > > > >> Once done, can you please send me some identification for these three machines so that I can contact Rackspace (via Pono/SFC) to have those removed from our current bills? > > > > I'm pretty sure we can delete servers and services. I do have such option in the rackspace UI. > > > >> Please redirect "bugs.squeak.org" to "https://github.com/squeak-smalltalk/squeak-object-memory". > >> Please also try to stop using the Rackspace Cloud DB / MySQL DB. Can this be done via the Web-Interface directly? Backup the existing DB contents as well. > > > > I'm sure it can. I created a new database user to be able to back up the 'cloud' database I had no access to before. > > > > Levente > > > >> Thank you! :-) > >> Best, > >> Marcel > >> P.S.: I think that Levente and Bruce have backups for planet.squeak already. Maybe double check the MySQL DB. > >> P.P.S.: Is "ian" really necessary as SSH gateway? Can this be reconfigured in an easy way? > > This requires reconfiguration of the whole login thing. > Can be done, takes time. > > -Tobias > > >

1 0

Re: [Box-Admins] [Board] Squeak Services | Inquiry to shutdown david/scott/john
by Levente Uzonyi 20 Apr '22

20 Apr '22

Hi Marcel, On Tue, 19 Apr 2022, Marcel Taeumel wrote: > Hi box admins -- > > Can we please backup and shutdown the following servers ASAP: > > - david (planet.squeak) > - scott (mantis/codespeed) > - john (docker ... already inactive?) Is there anything useful on john to be backed up? I've never seen that server before, I didn't have my ssh key added to it, I don't have a user on it. It was shut down but not deleted, so it was billed as if it had been running the whole time. I changed the root password on it and managed to log in. I only see some old docker images but no containers. > > Once done, can you please send me some identification for these three machines so that I can contact Rackspace (via Pono/SFC) to have those removed from our current bills? I'm pretty sure we can delete servers and services. I do have such option in the rackspace UI. > > Please redirect "bugs.squeak.org" to "https://github.com/squeak-smalltalk/squeak-object-memory". > > Please also try to stop using the Rackspace Cloud DB / MySQL DB. Can this be done via the Web-Interface directly? Backup the existing DB contents as well. I'm sure it can. I created a new database user to be able to back up the 'cloud' database I had no access to before. Levente > > Thank you! :-) > > Best, > Marcel > > P.S.: I think that Levente and Bruce have backups for planet.squeak already. Maybe double check the MySQL DB. > > P.P.S.: Is "ian" really necessary as SSH gateway? Can this be reconfigured in an easy way? > >

1 0

Re: [Box-Admins] [Board] Backing up our servers
by Levente Uzonyi 12 Apr '22

12 Apr '22

Hi Marcel, Data is backed up daily to a hard drive sitting on my desk. Levente On Tue, 12 Apr 2022, Marcel Taeumel wrote: > Hi Levente -- > > What's the current status on this? Where did you back up the data to? What is the timestamp of that backup? :-) > > Best, > Marcel > > Am 28.03.2022 11:16:31 schrieb Levente Uzonyi <leves(a)caesar.elte.hu>: > > Hi Tony, hi all, > > @Tony: > If you send me an ssh key, preferrably ed25519, I'll create a user for you > on all the servers, so that you can log in with your key. > > @all: > More than a week ago, I started to create backups of all servers using > rdiff-backup[1]. It took a longer for the initial backup to complete > than I expected due to the nature of the network setup we have: tcp is > tunneled over tcp, which is known to be slow[2] but it surprised me how > slow it turned out to be in practice (~1.66MB/s). > > The process copies the following directories: /etc, /home, /opt /root, > /srv, /var/backups, /var/log, /var/mail, /var/spool, /var/www. > If there are files that need to be preserved in any other directory on > any server you are aware of, let me know. > > > Levente > > [1] https://rdiff-backup.net/ > [2] http://sites.inka.de/~W1011/devel/tcp-tcp.html > > On Fri, 18 Mar 2022, Marcel Taeumel wrote: > > > +1 for giving Tony access to the servers > > Best, > > Marcel > > > > Am 17.03.2022 09:22:17 schrieb Tony Garnock-Jones : > > > > Hi David, Chris, all, > > > > Great, that README is a good initial survey of the machine. The backups > > I run for the various cloud servers under my control are similar. > > > > Generally, I use rsnapshot [1] from cron to make incremental backups > > across ssh (it uses rsync internally). > > > > This works great for unprivileged files, those readable by an account > > you'd trust to log in to grab files to be backed up. > > > > For the privileged ones, as you note in your README, a cronjob running > > as root on the source machines can archive the bits and pieces for later > > pickup by the backup account. > > > > Levente, Tobias, I'd be happy to log into the boxes to do the initial > > survey and set up some backups. I suppose the box-admins team should > > decide if I'm to be trusted to do this! It does require root access at > > least initially. If you all would prefer not to create a new privileged > > unix account, etc, that's cool -- in that case I'd also be happy to > > pair-sysadmin via tmux or screen or similar if that would be helpful. > > And actually even in the case you would be happy letting me work with > > root, I'd also welcome having a second set of screen/tmux eyes on what > > I'm doing. > > > > Cheers, > > Tony > > > > [1] https://rsnapshot.org/ > > > > > > On 3/17/22 01:47, David T. Lewis wrote: > > > Hi Chris, > > > > > > Funny you should mention it, I was doing the same thing last > > > weekend to make sure we could move the squeaksource.com service > > > if needed. I had intended to share this in the board meeting > > > today but was not able to attend. In any case, I'm attaching > > > my "disaster recovery plan" notes (crudely formatted but better > > > than nothing). > > > > > > For me it was a PITA dealing with session timeouts while > > > download 30GB to my tired little old laptop PC, but at least > > > I was able to do it after a few hours, and would be able to > > > restore it to some new server as long as someone else could > > > handle the sys admin things for ssh and port forwarding. > > > > > > I think between the two of us we could handle moving the two > > > squeaksource services, although I don't know how to handle > > > the rest of the services (mailing lists, etc). For that we > > > would need some expertise from the box-admins, especially > > > Levente and Tobias. > > > > > > Dave > > > > > > > > > On Wed, Mar 16, 2022 at 03:58:09PM -0500, Chris Muller wrote: > > >> Hi Tony, Dave, all, > > >> > > >> FYI, I had this *exact thought* yesterday when I was working on our > > >> server. We "expect" cloud services to be redundant and backed up, but > > >> for something this important it's necessary to have a backup system > > >> under our control. Our code is an asset that can't be bought with money, > > >> whereas the bandwidth is. I'm downloading a backup copy of the ./ss > > >> directory at this moment which I need to test a server upgrade to 5.3 > > >> and the latest code. This will at least temporarily reduce our risk > > >> of "total loss" until we can get a permanent backup solution. > > >> > > >> - Chris > > >> > > >> On Wed, Mar 16, 2022 at 12:52 PM David T. Lewis wrote: > > >>> > > >>> Let's make this an agenda item for our meeting (in a few minutes). I > > >>> can share some work I did over the weekend to prepare a "poor person's" > > >>> recovery plan for squeaksource.com. It's painful but it works. > > >>> > > >>> As for Rackspace backups, Levente and Tobias are most likely to know > > >>> how and if this can be done. I don't know the answer, but I have a > > >>> suspicion that the utility for "help me get my stuff off of Rackspace" > > >>> is not something that Rackspace, Inc. would be in a big hurry to support. > > >>> > > >>> Dave > > >>> > > >>> > > >>> On Wed, Mar 16, 2022 at 06:36:32PM +0100, Tony Garnock-Jones wrote: > > >>>> Hello all, > > >>>> > > >>>> I'm writing on behalf of the Squeak Oversight Board - could someone get > > >>>> in touch with me, please, to help me arrange backups of the important > > >>>> bits of our servers with some urgency? We have become concerned with > > >>>> disaster recovery and would like to quickly get something in place to at > > >>>> least have *something* if the servers were to vanish in a puff of logic... > > >>>> > > >>>> Regards, > > >>>> Tony > > > > > > > > >

2 1

Re: [Box-Admins] [Board] Backing up our servers
by Levente Uzonyi 28 Mar '22

28 Mar '22

Hi Tony, hi all, @Tony: If you send me an ssh key, preferrably ed25519, I'll create a user for you on all the servers, so that you can log in with your key. @all: More than a week ago, I started to create backups of all servers using rdiff-backup[1]. It took a longer for the initial backup to complete than I expected due to the nature of the network setup we have: tcp is tunneled over tcp, which is known to be slow[2] but it surprised me how slow it turned out to be in practice (~1.66MB/s). The process copies the following directories: /etc, /home, /opt /root, /srv, /var/backups, /var/log, /var/mail, /var/spool, /var/www. If there are files that need to be preserved in any other directory on any server you are aware of, let me know. Levente [1] https://rdiff-backup.net/ [2] http://sites.inka.de/~W1011/devel/tcp-tcp.html On Fri, 18 Mar 2022, Marcel Taeumel wrote: > +1 for giving Tony access to the servers > Best, > Marcel > > Am 17.03.2022 09:22:17 schrieb Tony Garnock-Jones <tonyg(a)leastfixedpoint.com>: > > Hi David, Chris, all, > > Great, that README is a good initial survey of the machine. The backups > I run for the various cloud servers under my control are similar. > > Generally, I use rsnapshot [1] from cron to make incremental backups > across ssh (it uses rsync internally). > > This works great for unprivileged files, those readable by an account > you'd trust to log in to grab files to be backed up. > > For the privileged ones, as you note in your README, a cronjob running > as root on the source machines can archive the bits and pieces for later > pickup by the backup account. > > Levente, Tobias, I'd be happy to log into the boxes to do the initial > survey and set up some backups. I suppose the box-admins team should > decide if I'm to be trusted to do this! It does require root access at > least initially. If you all would prefer not to create a new privileged > unix account, etc, that's cool -- in that case I'd also be happy to > pair-sysadmin via tmux or screen or similar if that would be helpful. > And actually even in the case you would be happy letting me work with > root, I'd also welcome having a second set of screen/tmux eyes on what > I'm doing. > > Cheers, > Tony > > [1] https://rsnapshot.org/ > > > On 3/17/22 01:47, David T. Lewis wrote: > > Hi Chris, > > > > Funny you should mention it, I was doing the same thing last > > weekend to make sure we could move the squeaksource.com service > > if needed. I had intended to share this in the board meeting > > today but was not able to attend. In any case, I'm attaching > > my "disaster recovery plan" notes (crudely formatted but better > > than nothing). > > > > For me it was a PITA dealing with session timeouts while > > download 30GB to my tired little old laptop PC, but at least > > I was able to do it after a few hours, and would be able to > > restore it to some new server as long as someone else could > > handle the sys admin things for ssh and port forwarding. > > > > I think between the two of us we could handle moving the two > > squeaksource services, although I don't know how to handle > > the rest of the services (mailing lists, etc). For that we > > would need some expertise from the box-admins, especially > > Levente and Tobias. > > > > Dave > > > > > > On Wed, Mar 16, 2022 at 03:58:09PM -0500, Chris Muller wrote: > >> Hi Tony, Dave, all, > >> > >> FYI, I had this *exact thought* yesterday when I was working on our > >> server. We "expect" cloud services to be redundant and backed up, but > >> for something this important it's necessary to have a backup system > >> under our control. Our code is an asset that can't be bought with money, > >> whereas the bandwidth is. I'm downloading a backup copy of the ./ss > >> directory at this moment which I need to test a server upgrade to 5.3 > >> and the latest code. This will at least temporarily reduce our risk > >> of "total loss" until we can get a permanent backup solution. > >> > >> - Chris > >> > >> On Wed, Mar 16, 2022 at 12:52 PM David T. Lewis wrote: > >>> > >>> Let's make this an agenda item for our meeting (in a few minutes). I > >>> can share some work I did over the weekend to prepare a "poor person's" > >>> recovery plan for squeaksource.com. It's painful but it works. > >>> > >>> As for Rackspace backups, Levente and Tobias are most likely to know > >>> how and if this can be done. I don't know the answer, but I have a > >>> suspicion that the utility for "help me get my stuff off of Rackspace" > >>> is not something that Rackspace, Inc. would be in a big hurry to support. > >>> > >>> Dave > >>> > >>> > >>> On Wed, Mar 16, 2022 at 06:36:32PM +0100, Tony Garnock-Jones wrote: > >>>> Hello all, > >>>> > >>>> I'm writing on behalf of the Squeak Oversight Board - could someone get > >>>> in touch with me, please, to help me arrange backups of the important > >>>> bits of our servers with some urgency? We have become concerned with > >>>> disaster recovery and would like to quickly get something in place to at > >>>> least have *something* if the servers were to vanish in a puff of logic... > >>>> > >>>> Regards, > >>>> Tony > > >

1 0

Mantis new login registration (was: Same Dates are not equal)
by David T. Lewis 23 Jan '22

23 Jan '22

Hello J??rg, I am not sure who is our admin on the old Mantis site, so I am sending CC to our box-admins list to ask. The Mantis site is quite old and no longer actively used. Asking your questions here on the squeak-dev list is still the best thing to do. Dave On Sun, Jan 23, 2022 at 07:35:24PM +0100, J??rg Belger wrote: > > I wanted to make a bug request in Mantis, but I did not found a > registration link, I tried also to use the normal Login form and > checked the ???Save Login???, because I thought it will then use > it as new registration, but it does not. I was already registered > on the Squeak dev mailing list some weeks ago, but I deleted my > subscription, because I do not want to get always emails from > other things, that are not interesting for me. The chat is also > not really useful, when always the same people post things about > their effort in their projects. So I think I will delete my > subscription again until I got an answer to this email here. > It would be helpful if somebody can tell me how I can add a > login for Mantis, so that I can make bug request there. If I > have more experience with Squeak maybe I will also have a look > on other issues in Mantis. But currently for me it is only > disturbing to get so much other things, so the mailing lists > and chat is currently nothing for me. > > Regards > J??rg > > >

1 0

Help needed to add a squeakvm.org tarball to files.squeak.org
by David T. Lewis 05 Jan '22

05 Jan '22

Hi box-admins, I have a file that I would like to put in a new folder on files.squeak.org. The file is Squeak-4.19.9-3814-src.tar.gz which can be pulled from this Google drive link: https://drive.google.com/file/d/1kYN5KOv3bIGOc-Q-ei7JqMWcAxCCLs5H/view?usp=… The location for this file should be a new 'tarball' folder under the existing 'debian' folder: https://files.squeak.org/debian/tarball/ For file integrity check the checksum is: $ cksum Squeak-4.19.9-3814-src.tar.gz 1051772195 3441834 Squeak-4.19.9-3814-src.tar.gz Can someone please add Squeak-4.19.9-3814-src.tar.gz to the server? Background: With the support of the Squeak board, Phil Bellalouna has been working with the Debian squeak-vm package team to produce an updated package that will include the opensmalltalk-vm VMs in addition to the traditional interpreter VM. As part of that effort, the Debian maintainers would like to have a reference tarball for the interpreter VM from a recognized Squeak site. I have produced the tarball file, and the board has agreed that we can put it on files.squeak.org. I will also note that an updated tarball can be created at any time by running this script: http://squeakvm.org/cgi-bin/viewvc.cgi/squeak/trunk/platforms/unix/cmake/mk… Thanks! Dave

2 2

Help needed to add a file to http://files.squeak.org/4.6/
by David T. Lewis 10 Nov '21

10 Nov '21

Could someone with access to the file server box please add a file to the files.squeak.org/4.6/ folder? I do not have the necessary access to do it. Background: Per request from David Stes (CCed for info) and with the approval of the board, we would like to put Squeak4.6-15118.zip to the 4.6 folder on the file server. This is the original Squeak4.6-15102.zip, but manually updated to include the available updates in the squeak46 update stream. The Squeak4.6-15118.zip file is on Dropbox at: https://www.dropbox.com/s/tda9u9e6sckf7ci/Squeak4.6-15118.zip?dl=0 File integrity check: $ cksum Squeak4.6-15118.zip 1015180721 8303401 Squeak4.6-15118.zip Thank you! Dave

4 7

[INFO] squeaksource.org notes
by David T. Lewis 03 Oct '21

03 Oct '21

A few notes about squeaksource.com: I restarted the image today at about 1:20pm EST. Reason: I was doing a periodic health check on it, and accidentally terminated a process that I should not have stopped. Root cause was human error. I doubt that anyone will have noticed it, but I'm mentioning it here in case anyone asks. I have added some Montecello packages to match the current running squeaksource.com image: 1) The SqueakSource package version that is running on squeaksource.com is SqueakSource.sscom-dtl.1130 in the source.squeak.org/ss repository. This is a branch (sscom) that captures differences versus the source.squeak.org image. 2) Other support utilities (e.g. things that previously lived in workspaces in the image) are in package Startup-SqueakSource-dtl.9 in the http://www.squeaksource.com/SSImageInit repository. Dave

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Box-Admins