bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, Can this issue be closed? Otherwise, what remains to be acted upon? Thanks, Maxim

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi Maxim, On Wed, 28 Sep 2022 at 20:32, Maxim Cournoyer wrote: > Can this issue be closed? This “meta” bug raises 2 levels of issues for long-term: 1. save the source code, 2. save the current binary substitutes. For #1, we have now a roadmap to tackle this via Disarchive or sources.json an

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, zimoun skribis: > This “meta” bug raises 2 levels of issues for long-term: > > 1. save the source code, > 2. save the current binary substitutes. Maybe we can close this bug and open an issue for each of these, or discuss them on guix-devel until there are actionable items that come out o

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, Ludovic Courtès writes: > Hi, > > zimoun skribis: > >> This “meta” bug raises 2 levels of issues for long-term: >> >> 1. save the source code, >> 2. save the current binary substitutes. > > Maybe we can close this bug and open an issue for each of these, or > discuss them on guix-devel un

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, On Thu, 29 Sep 2022 at 23:10, Maxim Cournoyer wrote: > Wholly agreed, this thread is already too long and the original problem > was fixed. Closing. I disagree, the original problem is not fixed; as I explained. Well, since you consider it is, please also close the related patch#43442. C

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

On 30-09-2022 05:10, Maxim Cournoyer wrote: Hi, Ludovic Courtès writes: Hi, zimoun skribis: This “meta” bug raises 2 levels of issues for long-term: 1. save the source code, 2. save the current binary substitutes. Maybe we can close this bug and open an issue for each of these, o

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, zimoun skribis: > On Thu, 29 Sep 2022 at 23:10, Maxim Cournoyer > wrote: > >> Wholly agreed, this thread is already too long and the original problem >> was fixed. Closing. > > I disagree, the original problem is not fixed; as I explained. What would you think of opening specific issues

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, zimoun writes: > Hi, > > On Thu, 29 Sep 2022 at 23:10, Maxim Cournoyer > wrote: > >> Wholly agreed, this thread is already too long and the original problem >> was fixed. Closing. > > I disagree, the original problem is not fixed; as I explained. Well, > since you consider it is, please

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hello, Maxim Cournoyer skribis: > zimoun writes: > >> Hi, >> >> On Thu, 29 Sep 2022 at 23:10, Maxim Cournoyer >> wrote: >> >>> Wholly agreed, this thread is already too long and the original problem >>> was fixed. Closing. >> >> I disagree, the original problem is not fixed; as I explained.

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hello! The hosting site gforge.inria.fr will be taken off-line in December 2020. This GForge instance hosts source code as tarballs, Subversion repos, and Git repos. Users have been invited to migrate to gitlab.inria.fr, which is Git only. It seems that Software Heritage hasn’t archived (yet) a

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi Ludo, On Thu, 02 Jul 2020 at 09:29, Ludovic Courtès wrote: > The hosting site gforge.inria.fr will be taken off-line in December > 2020. This GForge instance hosts source code as tarballs, Subversion > repos, and Git repos. Users have been invited to migrate to > gitlab.inria.fr, which is G

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

zimoun skribis: > On Thu, 02 Jul 2020 at 09:29, Ludovic Courtès > wrote: > >> The hosting site gforge.inria.fr will be taken off-line in December >> 2020. This GForge instance hosts source code as tarballs, Subversion >> repos, and Git repos. Users have been invited to migrate to >> gitlab.in

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hello Ludovic, Ludovic Courtès writes: > Hello! > > The hosting site gforge.inria.fr will be taken off-line in December > 2020. This GForge instance hosts source code as tarballs, Subversion > repos, and Git repos. Users have been invited to migrate to > gitlab.inria.fr, which is Git only. It

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi Maxim, Maxim Cournoyer skribis: >> The following packages have their source on gforge.inria.fr: >> >> scheme@(guile-user)> ,pp packages-on-gforge >> $7 = (#> 7f632401a640> >> # >> # [...] > I ran the code you had attached to the original message and got: > > ,pp packages-on-gforge > $2 =

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hello, Am Wed, Jan 13, 2021 at 11:39:19AM +0100 schrieb Ludovic Courtès: > ISL, MPFI, and GMP-ECM haven’t migrated, it seems. CMH is now at > but without its tarballs. > > Andreas, do you happen to know about the status of these? For CMH, the tarballs are avail

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

help-debb...@gnu.org (GNU bug Tracking System) skribis: > We can already change Scotch and CMH to ‘git-fetch’ I think. For Scotch, the ‘v6.1.0’ tag at gitlab.inria.fr provides different content than the tarball on gforge: Nur en /tmp/scotch_6.1.0/: bin Nur en /tmp/scotch_6.1.0/doc/src/ptscotch:

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Am Wed, Jan 13, 2021 at 11:39:19AM +0100 schrieb Ludovic Courtès: > ISL, MPFI, and GMP-ECM haven’t migrated, it seems. gmp-ecm has migrated to gitlab.inria.fr; I just pushed a commit with an updated URI. Besides the automatically created gitlab releases with git snapshots, the maintainer also uplo

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi Ludovic, Ludovic Courtès writes: [...] > There’s not much we can do if upstream isn’t more cautious though. > Perhaps we can still update to the “new” 6.1.0, maybe labeling it > “6.1.0b”? I'd prefer to append a '-1' revision rather than changing the version string itself; as that is IMO the

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi Ludo, On Mon, 04 Oct 2021 at 17:59, Ludovic Courtès wrote: > Believe it or not, gforge.inria.fr was finally phased out on > Sept. 30th. And believe it or not, despite all the work and all the > chat :-), we lost the source tarball of Scotch 6.1.1 for a short period > of time (I found a copy

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi! zimoun skribis: > Euh, I do not understand. From bug#43442 [1] on Wed, 16 Sep 2020, > Scotch was not missing. And from [2] neither. > > Nah, the hole is the (double) update (from 6.0.6 to 6.1.0 then 6.1.1) > without manually taking care of this bug report; by switching from > url-fetch to

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi, On Thu, 7 Oct 2021 at 18:07, Ludovic Courtès wrote: > I guess, in our mind, the problem was fixed long ago. :-) Yes, to me the 2 remaining packages was from but moved already to Gitlab. Whatever, :-) > > As I am asking in this thread [3], the Guix pro

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hello! I sense a lot of impatience in your message :-), and I also see many questions. It is up to us all to answer them, I’ll just reply selectively here. zimoun skribis: > On Thu, 7 Oct 2021 at 18:07, Ludovic Courtès wrote: [...] >> The second-best solution is to improve our tooling so we

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

Hi Ludo, On Tue, 12 Oct 2021 at 11:24, Ludovic Courtès wrote: > I sense a lot of impatience in your message :-), and I also see many > questions. It is up to us all to answer them, I’ll just reply > selectively here. Impatience? Probably. :-) > zimoun skribis: >> On Thu, 7 Oct 2021 at 18:0

bug#42162: gforge.inria.fr to be taken off-line in Dec. 2020

On Thu, 07 Oct 2021 18:07:16 +0200 Ludovic Courtès wrote: > Hi! > > zimoun skribis: > > > Euh, I do not understand. From bug#43442 [1] on Wed, 16 Sep 2020, > > Scotch was not missing. And from [2] neither. > > > > Nah, the hole is the (double) update (from 6.0.6 to 6.1.0 then > > 6.1.1) with