[darcs-users] [ANN] Darcs 2.18.2 release

Hi, On behalf of the Darcs team, I would like to announce the release of Darcs 2.18.2 [1]. The full release notes [2] are appended below. Regards, Ganesh [1] https://hackage.haskell.org/package/darcs-2.18.2 [2] https://hackage.haskell.org/package/darcs-2.18.2/changelog Darcs 2.18.2, 24 Mar

[darcs-users] [ANN] Darcs 2.18.1 release

Hi, On behalf of the Darcs team, I would like to announce the release of Darcs 2.18.1 [1]. The full release notes [2] are appended below. Regards, Ganesh [1] https://hackage.haskell.org/package/darcs-2.18.1 [2] https://hackage.haskell.org/package/darcs-2.18.1/changelog Darcs 2.18.1, 25 Feb

[darcs-users] https support on darcs.net

Hi, Just to let people know that darcs.net, bugs.darcs.net etc now all support (and in fact enforce) https. Thanks to n.daniel and sm on IRC/Matrix Chat for helping get this long-overdue change made. Cheers, Ganesh ___ darcs-users mailing list

[darcs-users] [ANN] Darcs 2.16.5 release

Hi, On behalf of the Darcs team, I would like to announce the release of Darcs 2.16.5 [1]. Quoting from the release notes [2]: This release is to support newer dependencies, most importantly GHC 9.0 and Cabal 3.6. It also includes a small number of refactors that help with moving to those

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

On 14/10/2021 20:54, Simon Michael wrote: Would me switching darcs hub to use the system openssh server, suitably locked down, be an alternative ? IIRC, I think not; the haskell ssh server allows the necessary tight integration with darcs hub's users and repos. (Aside from the resources

Re: [darcs-users] Cannot create an account at bug.darcs.net

On 13/09/2021 12:14, Ben Franksen wrote: Hi Ganesh I guess this is a problem related to the roundup migration. If you could take a look at that? I tried twice to create an account with this email, but submitting the form fails with:    Form is corrupted, missing: opaqueregister. It

Re: [darcs-users] [darcs-devel] darcs.net migration in progress

Hi, > Please don't make any updates to roundup until I announce it's done - > I'll try to make it read-only to begin with if possible. The other items > (website+repos) are darcs repos anyway so it won't be a big deal to pull > across updates if anyone does make any. > > Assuming all goes well

[darcs-users] darcs.net migration in progress

Hi, I'm kicking off migrating darcs.net to a new machine now. This includes: - The http://darcs.net website+wiki - The repositories hosted at http://darcs.net - The roundup tracker for bugs and patches It *doesn't* include hub.darcs.net. Please don't make any updates to roundup until I

[darcs-users] advance warning: darcs.net migration this weekend

Hi, Just a heads-up: darcs.net will be migrated to a new machine this weekend. That includes the following things: - The http://darcs.net website+wiki - The repositories hosted at http://darcs.net - The roundup tracker for bugs and patches It *doesn't* include hub.darcs.net. I'll send an

Re: [darcs-users] Write-up on "tree repositories" as an alternative to conflictors

Hi, On 24/11/2020 21:43, James Cook wrote: > I wrote a description of how to store a repository as a tree of > primitive patches with active and inactive branches, as an alternative > to conflictors. For context, see recent discussion on the thread > "How to extend a patch theory to fully

Re: [darcs-users] RFC: safer default for patch editing operations

On 25/09/2020 13:46, Ben Franksen wrote: > Since 2.16 the --not-in-remote option is supported for all operations > that edit the history: amend, rebase suspend, obliterate, and unrecord. > > Should we make this the default behavior? I'm weakly in favour. > Now, if --not-in-remote becomes the

Re: [darcs-users] darcs.net down

On 05/02/2020 15:28, Benjamin Franksen wrote: > Am 04.02.20 um 16:22 schrieb Henning Thielemann: >> http://darcs.net/ says: >> >> Service Temporarily Unavailable >> >> The server is temporarily unable to service your request due to >> maintenance downtime or capacity problems. Please try again

Re: [darcs-users] rebase pull/apply vs. pull/apply --rebase

Hi, On 28/01/2020 10:37, Ben Franksen wrote: > It would be quite convenient to have a --rebase option for obliterate > that automatically suspends all patches that depend on the one(s) you > want to obliterate. > Note that this is something completely different than 'rebase > obliterate' which

[darcs-users] force commuting in practice

Hi, At the moment the darcs patch theory doesn't support the idea of forcibly commuting two patches A;B when B depends on A. It's tricky because both results would have conflicts. So if you want to do it anyway, you have to make two new patches B';A'. The best way I know of doing it at the

[darcs-users] darcs 2.14.2 released

Hi, I released darcs 2.14.2 earlier today. It adds support for GHC 8.6 and also has the fix (from Ben) for the git import import issue reported a few days ago (http://bugs.darcs.net/issue2617). http://darcs.net/Releases/2.14 https://hackage.haskell.org/package/darcs-2.14.2 Cheers, Ganesh

Re: [darcs-users] darcs and redmine

On 15/10/2018 19:49, Axel Hellinger wrote: > I get a 404 repository not found on redmine and on the shell the error > shows "darcs failed: unrecognized option `--xml-output'" darcs annotate no longer has an --xml-output option and instead has --machine-readable which is a custom format designed

Re: [darcs-users] memory leak in 'darcs log'

On 14/08/2018 15:37, Henning Thielemann wrote: > > On Tue, 14 Aug 2018, Henning Thielemann wrote: > >> I cloned a darcs repository lazily > > $ darcs get --lazy http://hub.darcs.net/thielema/lapack > >> and then wanted to pull the unfetched patches via the hint from [1]: >> >> $ darcs log