Re: [darcs-users] [ANN] Darcs 2.18.1 release

[Simon Michael]

Sounds like great improvements, thanks Ganesh, all!
___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

Re: [darcs-users] Couldn't fetch when cloning a repository

[Simon Michael]

> On Oct 14, 2021, at 10:09 AM, Karl O. Pinc  wrote:
> 
> FYI.  The OpenSSH 8.8 release has some changes listed
> in the release email for OpenBSD 7.0 that may be relevant.

Thanks Karl. I'm hoping the published config works around this, no matter what 
openssh release one has.

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

Re: [darcs-users] Couldn't fetch when cloning a repository

[Simon Michael]

On 10/14/21 10:09 AM, Karl O. Pinc wrote:
> 

Thanks Karl. I'm hoping the config provided works around this.

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

Re: [darcs-users] Couldn't fetch when cloning a repository

[Simon Michael]

Hi Alexis, Gian Piero.  I currently don't check the mail list too often, so 
thanks for cc-ing me. I am starting to add more #darcs chat links to darcs hub 
docs, since that is where I'm most responsive for darcs hub issues.

Today I have rewritten 
https://hub.darcs.net/#what-is-the-special-ssh-config-i-need-for-darcs-hub 
 . 
Any testing of these instructions is welcome, on old and new ssh versions.

Best
-Simon



> On Oct 11, 2021, at 10:00 PM, Alexis Praga  wrote:
> 
> 
> Hi Gian Piero,
> 
> Here's what worked for me in ~/.ssh/config on Archlinux:
>> Host hub.darcs.net
>>   Ciphers +aes256-cbc
>>   PubkeyAcceptedKeyTypes +ssh-rsa
>>   HostKeyAlgorithms=+ssh-rsa
> 
> 
> 
> Gian Piero Carrubba  writes:
> 
>> * [Wed, Oct 06, 2021 at 02:46:15PM +0200] Alexis Praga:
>>> 
>>> More testing: this happens with Archlinux (latest), and not on FreeBSD
>>> 13.0.
>>> I can push/pull fine to my SSH server.
>> 
>> (replying to all in order to reach Simon, too).
>> 
>> Latest releases of openssh (not yet in FreeBSD, but already in Arch I 
>> guess) disable ssh-rsa signatures. IIRC, there should be a way to 
>> re-enable them in the config, but a cursory search found nothing, so 
>> maybe I'm remembering poorly.
>> The best way forward would be updating all the involved keys, but - 
>> again IIRC - darcs hub uses an Haskell implementation of the ssh server, 
>> so it could be not so straightforward.
>> 
>> Ciao,
>> Gian Piero.
>> 
>> PS: anyway, while at it could it be possible to also implement support 
>> for ed25519 keys?.
> 
> -- 
> Alexis Praga

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

Re: [darcs-users] Couldn't fetch when cloning a repository

[Simon Michael]

Good. I have deleted blog2 from the database (it had not been created on the 
filesystem).


> On Aug 31, 2021, at 6:39 AM, Alexis Praga  wrote:
> 
> 
> Thanks for the answer, Ben and Simon.
> Creating a new repo fixed it.
> 
> Simon, would it be possible to delete this "repository" : 
> hub.darcs.net/alexdarcy/blog2 ?
> When creating it, I got a GET error and I cannot access it since.
> 
> Thanks !
> 
> Simon Michael  writes:
> 
>> Thanks for the ping Ben.
>> 
>> On the server, `darcs check` passes, and I can `darcs get` the repo to a 
>> local copy without error. I ran `darcs optimize http` for good measure. But 
>> like you, I still can't `darcs get` this repo to a remote machine. I was 
>> able to `darcs get` another of Alexis's repos. 
>> 
>> That's a puzzle. Sorry Alexis, I'm going to recommend you try pushing a new 
>> copy of this repo under a new name (or delete the old one and re-push to a 
>> new repo with the same name) and see if that "fixes" it.
>> 
>> 
>> 
>>> On Aug 29, 2021, at 1:52 AM, Ben Franksen  wrote:
>>> 
>>> Am 28.08.21 um 23:03 schrieb Alexis Praga:
>>>> I'm trying darcs again since a few days and have hit an issue when
>>>> cloning a (non-empty) repository hosted on hub.darcs.net.
>>>> The error is:
>>>>> Done fetching and unpacking basic pack.
>>>>> Copying patches, to get lazy repository hit ctrl-C...
>>>>> Exception while getting patches pack:
>>>>> user error (Couldn't fetch 
>>>>> 001251-f948ccb7fba745717a321df8692dd42a829f9f74bff78205e20ddcafcc0b61d8
>>>>> in subdir patches from sources:
>>>>> 
>>>>> thisrepo:/usr/home/alex/code/blog
>>>>> cache:/home/alex/.cache/darcs
>>>>> repo:.
>>>>> repo:alexda...@hub.darcs.net:blog
>>>>> )
>>>>> Couldn't fetch 
>>>>> 001251-f948ccb7fba745717a321df8692dd42a829f9f74bff78205e20ddcafcc0b61d8
>>>>> in subdir patches from sources:
>>>>> 
>>>>> thisrepo:/usr/home/alex/code/blog
>>>>> cache:/home/alex/.cache/darcs
>>>>> repo:.
>>>>> repo:alexda...@hub.darcs.net:blog
>>>>> 
>>>>> 
>>>>> By the way, I could not reach the following location:
>>>>>  alexda...@hub.darcs.net:blog
>>>>> Unless you plan to restore access to it, you should delete the 
>>>>> corresponding entry from _darcs/prefs/sources.
>>>> I managed to get around it by downloading the repository as a zip file,
>>>> running 'darcs init' and 'darcs pull'.
>>>> After that, cloning works again.
>>>> Any idea appreciated, thanks !
>>> 
>>> Indeed I can reproduce the problem with darcs-2.16.4, with different files:
>>> 
>>> ben@home[3]:~/scratch>darcs-2.16.4 clone b...@hub.darcs.net:alexdarcy/blog 
>>> --no-cache
>>> Done fetching and unpacking basic pack.
>>> Copying patches, to get lazy repository hit ctrl-C...
>>> Exception while getting patches pack:
>>> user error (Couldn't fetch 
>>> 002258-69b6b76aa783a1a96ffa71c33e3f3c47187191f5f8a824376662c78494ceb2dc
>>> in subdir patches from sources:
>>> 
>>> thisrepo:/home/ben/scratch/blog
>>> repo:.
>>> repo:b...@hub.darcs.net:alexdarcy/blog
>>> )
>>> Couldn't fetch 
>>> 153496-12b83e9c17802e71926c9bf9d3cdeda3f1b93e1188de445b95556ff03cabdc4a
>>> in subdir inventories from sources:
>>> 
>>> thisrepo:/home/ben/scratch/blog
>>> repo:.
>>> repo:b...@hub.darcs.net:alexdarcy/blog
>>> 
>>> 
>>> By the way, I could not reach the following location:
>>> b...@hub.darcs.net:alexdarcy/blog
>>> Unless you plan to restore access to it, you should delete the 
>>> corresponding entry from _darcs/prefs/sources.
>>> 
>>> 
>>> (I used --no-cache to circumvent the cache on my machine to make sure it 
>>> actually tries to download all files.)
>>> 
>>> This is pretty strange. It works when I pass --lazy. And when I issue a 
>>> darcs check --no-cache afterwards (which should download all missing files) 
>>> this seems to work, too.
>>> 
>>> I can also clone from the https URL. And, notably, I can clone the same 
>>> repo via ssh from localhost (also with --no-cache). This suggests the 
>>> problem may lie with hub.darcs.net and not with darcs; perhaps a slow 
>>> response runs into a timeout? I have cc'ed Simon...
>>> 
>>> Cheers
>>> Ben
>>> -- 
>>> I would rather have questions that cannot be answered, than answers that
>>> cannot be questioned.  -- Richard Feynman
>>> 
>> 
> 
> -- 
> Alexis Praga

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

Re: [darcs-users] Couldn't fetch when cloning a repository

[Simon Michael]

Thanks for the ping Ben.

On the server, `darcs check` passes, and I can `darcs get` the repo to a local 
copy without error. I ran `darcs optimize http` for good measure. But like you, 
I still can't `darcs get` this repo to a remote machine. I was able to `darcs 
get` another of Alexis's repos. 

That's a puzzle. Sorry Alexis, I'm going to recommend you try pushing a new 
copy of this repo under a new name (or delete the old one and re-push to a new 
repo with the same name) and see if that "fixes" it.



> On Aug 29, 2021, at 1:52 AM, Ben Franksen  wrote:
> 
> Am 28.08.21 um 23:03 schrieb Alexis Praga:
>> I'm trying darcs again since a few days and have hit an issue when
>> cloning a (non-empty) repository hosted on hub.darcs.net.
>> The error is:
>>> Done fetching and unpacking basic pack.
>>> Copying patches, to get lazy repository hit ctrl-C...
>>> Exception while getting patches pack:
>>> user error (Couldn't fetch 
>>> 001251-f948ccb7fba745717a321df8692dd42a829f9f74bff78205e20ddcafcc0b61d8
>>> in subdir patches from sources:
>>> 
>>> thisrepo:/usr/home/alex/code/blog
>>> cache:/home/alex/.cache/darcs
>>> repo:.
>>> repo:alexda...@hub.darcs.net:blog
>>> )
>>> Couldn't fetch 
>>> 001251-f948ccb7fba745717a321df8692dd42a829f9f74bff78205e20ddcafcc0b61d8
>>> in subdir patches from sources:
>>> 
>>> thisrepo:/usr/home/alex/code/blog
>>> cache:/home/alex/.cache/darcs
>>> repo:.
>>> repo:alexda...@hub.darcs.net:blog
>>> 
>>> 
>>> By the way, I could not reach the following location:
>>>   alexda...@hub.darcs.net:blog
>>> Unless you plan to restore access to it, you should delete the 
>>> corresponding entry from _darcs/prefs/sources.
>> I managed to get around it by downloading the repository as a zip file,
>> running 'darcs init' and 'darcs pull'.
>> After that, cloning works again.
>> Any idea appreciated, thanks !
> 
> Indeed I can reproduce the problem with darcs-2.16.4, with different files:
> 
> ben@home[3]:~/scratch>darcs-2.16.4 clone b...@hub.darcs.net:alexdarcy/blog 
> --no-cache
> Done fetching and unpacking basic pack.
> Copying patches, to get lazy repository hit ctrl-C...
> Exception while getting patches pack:
> user error (Couldn't fetch 
> 002258-69b6b76aa783a1a96ffa71c33e3f3c47187191f5f8a824376662c78494ceb2dc
> in subdir patches from sources:
> 
> thisrepo:/home/ben/scratch/blog
> repo:.
> repo:b...@hub.darcs.net:alexdarcy/blog
> )
> Couldn't fetch 
> 153496-12b83e9c17802e71926c9bf9d3cdeda3f1b93e1188de445b95556ff03cabdc4a
> in subdir inventories from sources:
> 
> thisrepo:/home/ben/scratch/blog
> repo:.
> repo:b...@hub.darcs.net:alexdarcy/blog
> 
> 
> By the way, I could not reach the following location:
>  b...@hub.darcs.net:alexdarcy/blog
> Unless you plan to restore access to it, you should delete the corresponding 
> entry from _darcs/prefs/sources.
> 
> 
> (I used --no-cache to circumvent the cache on my machine to make sure it 
> actually tries to download all files.)
> 
> This is pretty strange. It works when I pass --lazy. And when I issue a darcs 
> check --no-cache afterwards (which should download all missing files) this 
> seems to work, too.
> 
> I can also clone from the https URL. And, notably, I can clone the same repo 
> via ssh from localhost (also with --no-cache). This suggests the problem may 
> lie with hub.darcs.net and not with darcs; perhaps a slow response runs into 
> a timeout? I have cc'ed Simon...
> 
> Cheers
> Ben
> -- 
> I would rather have questions that cannot be answered, than answers that
> cannot be questioned.  -- Richard Feynman
> 

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

[darcs-users] darcs hub is back up

[Simon Michael]

Darcs hub ssh access, and the whole site should now be working normally again. 
(Thanks to gpiero for the hint to add darcs to $PATH for ssh users.)

Updating your known hosts file

When you next attempt a darcs operation using ssh, you will likely see a big 
warning like "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!", because the 
new server has a new ssh key. I think this was needed to prevent warnings about 
the IP address change. And I think this means every user will have to update 
their $HOME/.ssh/known_hosts file (or windows equivalent) to silence the 
warning. (If you know otherwise, let me know). 

The error message should tell you where the known_hosts file is, and the 
problem line. You can open the file in an editor remove this line, and any 
others it complains about. But this is easier, if it works on your system:

$ ssh-keygen -R hub.darcs.net <http://hub.darcs.net/>   # remove 
hub.darcs.net <http://hub.darcs.net/> entry from known_hosts
$ ssh-keygen -R 173.255.254.122  # remove entry for the old IP address
$ ssh-keygen -R 173.255.254.113  # remove any out-of-date entry for the new IP 
address
$ ssh hub.darcs.net <http://hub.darcs.net/>
The authenticity of host 'hub.darcs.net (173.255.254.113)' can't be established.
RSA key fingerprint is SHA256:3eBJH9dB8ez4tJuxmnEP7dNHRRTk2BAKPuUmcGaoAAM.
Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'hub.darcs.net,173.255.254.113' (RSA) to the list of 
known hosts.
PTY allocation request failed on channel 0
shell request failed on channel 0

Now "ssh hub.darcs.net <http://hub.darcs.net/>" and "darcs push", "darcs pull" 
etc. should work as before, without warnings.

Sum-up

I'll keep this brief. I'm sorry for the length of this outage (by far the 
longest in darcs hub's history.) I have no particular plans or budget for darcs 
hub at the moment, and I have been relying on it to just keep running. As a 
result of this incident it now has its own VPS, separate from my other 
projects, which is an old goal. And the file layout and ops processes have been 
improved and documented. When couchdb arrives for ubuntu, I will try again to 
upgrade to latest ubuntu LTS (and couchdb 2.x), more carefully.  Hopefully the 
ops improvements will continue and lead to better insight into current darcs 
hub activity. 

Best,
-Simon



> On Jun 25, 2018, at 2:03 PM, Simon Michael  wrote:
> 
> Another update. 
> 
> I have moved hub.darcs.net <http://hub.darcs.net/> to a new VPS of its own. 
> Note the IP address has changed to 173.255.219.113.
> 
> The web UI is up again and should be working normally. I have added status 
> info to the front page. 
> 
> The ssh server is not yet operational, I am still working out a few problems 
> with it. For now, you can get or pull repos using their http url (eg darcs 
> get http://hub.darcs.net/simon/ssh <http://hub.darcs.net/simon/ssh>).
> 
> Thanks for your patience, and please watch the #darcs IRC channel, 
> darcs-users list or http://hub.darcs.net <http://hub.darcs.net/> front page 
> for more news.
> 
> Best
> -Simon
> 
> 
> 
> 
>> On Jun 17, 2018, at 3:17 PM, Simon Michael > <mailto:si...@joyful.com>> wrote:
>> 
>> Hi all. Here's an update on the current outage at http://hub.darcs.net 
>> <http://hub.darcs.net/> .
>> - All data is safe and service will be restored asap. 
>> 
>> - This is the fourth day of the incident. Though this is a best-effort free 
>> service provided in my "spare" time, I do care about reliability. This is 
>> the longest outage we've had. I'm very sorry about it.
>> - Unfortunately due to press of life events just now I'm not able to drop 
>> everything and work on it; I have windows of time. This is contributing to 
>> the delay.
>> 
>> - This is an upgrade that went wrong. In short, I upgraded the VPS on which 
>> darcs hub runs, without realising that couchdb was not available for the 
>> newer OS. (See below). 
>> 
>> - Rolling back the VPS upgrade was not practical, as I run other things 
>> there as well.
>> 
>> - I guessed wrongly that the new couchdb packages would appear within hours. 
>> It now looks like that could take a week, or more. 
>> (https://github.com/apache/couchdb/issues/1314 
>> <https://github.com/apache/couchdb/issues/1314>)
>> - In parallel I started building a new VPS, but last night it got 
>> compromised. So I must start over with this.
>> 
>> - Hopefully, you all are working productively from your local repo copies. 
>> But if you are urgently blocked, there may be something helpful I could do; 
>> let me know.
>> 
>> I'll update you when things

[darcs-users] darcs hub outage update, 2018-06-25

[Simon Michael]

Another update. 

I have moved hub.darcs.net <http://hub.darcs.net/> to a new VPS of its own. 
Note the IP address has changed to 173.255.219.113.

The web UI is up again and should be working normally. I have added status info 
to the front page. 

The ssh server is not yet operational, I am still working out a few problems 
with it. For now, you can get or pull repos using their http url (eg darcs get 
http://hub.darcs.net/simon/ssh).

Thanks for your patience, and please watch the #darcs IRC channel, darcs-users 
list or http://hub.darcs.net <http://hub.darcs.net/> front page for more news.

Best
-Simon




> On Jun 17, 2018, at 3:17 PM, Simon Michael  wrote:
> 
> Hi all. Here's an update on the current outage at http://hub.darcs.net 
> <http://hub.darcs.net/> .
> - All data is safe and service will be restored asap. 
> 
> - This is the fourth day of the incident. Though this is a best-effort free 
> service provided in my "spare" time, I do care about reliability. This is the 
> longest outage we've had. I'm very sorry about it.
> - Unfortunately due to press of life events just now I'm not able to drop 
> everything and work on it; I have windows of time. This is contributing to 
> the delay.
> 
> - This is an upgrade that went wrong. In short, I upgraded the VPS on which 
> darcs hub runs, without realising that couchdb was not available for the 
> newer OS. (See below). 
> 
> - Rolling back the VPS upgrade was not practical, as I run other things there 
> as well.
> 
> - I guessed wrongly that the new couchdb packages would appear within hours. 
> It now looks like that could take a week, or more. 
> (https://github.com/apache/couchdb/issues/1314 
> <https://github.com/apache/couchdb/issues/1314>)
> - In parallel I started building a new VPS, but last night it got 
> compromised. So I must start over with this.
> 
> - Hopefully, you all are working productively from your local repo copies. 
> But if you are urgently blocked, there may be something helpful I could do; 
> let me know.
> 
> I'll update you when things change. Thanks for your patience. 
> 
> Best,
> 
> -Simon
> sm on #darcs IRC channel
> 
> 
>> On Jun 14, 2018, at 2:57 PM, Simon Michael > <mailto:si...@joyful.com>> wrote:
>> 
>> Hi all,
>> 
>> I apologise for the darcs hub outage in progress at the moment. I began a 
>> systems upgrade to ubuntu bionic, and too late discovered this is a problem 
>> for couchdb:
>> 
>> - ubuntu's couchdb packages are gone
>> - couchdb's ubuntu packages are not yet ready
>> - building couchdb from source is too costly
>> - https://launchpad.net/~couchdb/+archive/ubuntu/master 
>> <https://launchpad.net/~couchdb/+archive/ubuntu/master> can't be added to my 
>> system for some reason
>> 
>> If you know a quick solution, please contact me here or on #darcs. 
>> Otherwise, I'm afraid we will be waiting until 
>> https://github.com/apache/couchdb/issues/1314 
>> <https://github.com/apache/couchdb/issues/1314> is complete. I think and 
>> hope this will be quite soon. Sorry for the inconvenience. 
>> 
>> Best,
>> -Simon
>> 
> 

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users

[darcs-users] ANN: darcs hub outage 2018-06-14

[Simon Michael]

Hi all,

I apologise for the darcs hub outage in progress at the moment. I began a 
systems upgrade to ubuntu bionic, and too late discovered this is a problem for 
couchdb:

- ubuntu's couchdb packages are gone
- couchdb's ubuntu packages are not yet ready
- building couchdb from source is too costly
- https://launchpad.net/~couchdb/+archive/ubuntu/master can't be added to my 
system for some reason

If you know a quick solution, please contact me here or on #darcs. Otherwise, 
I'm afraid we will be waiting until 
https://github.com/apache/couchdb/issues/1314 is complete. I think and hope 
this will be quite soon. Sorry for the inconvenience. 

Best,
-Simon

___
darcs-users mailing list
darcs-users@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-users