• bachmeier (2/2) Aug 05 2022 According to [this
• bachmeier (3/5) Aug 05 2022 Or, I guess, other packages that someone might rage delete like
• user1234 (3/5) Aug 05 2022 This information is already [out of
• mw (4/6) Aug 06 2022 But still I think we should cache all the dub registered packages
• Martin B (4/11) Aug 07 2022 Since git is a distributed version control system, used repos are
• mw (4/10) Aug 07 2022 The problem is that is local copy, nobody else can find the
• bauss (5/16) Aug 07 2022 I think the best solution overall would have been to copy from

bachmeier <no spam.net> writes:

According to [this 
story](https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/)
GitLab will be automatically deleting repos that are inactive for a year. Is
there a way to archive D packages that use GitLab? I don't know how much GitLab
is used, but I'd hate lose anything, considering the low cost of options such
as Backblaze B2 or S3 Glacier.

bachmeier <no spam.net> writes:

On Friday, 5 August 2022 at 17:37:41 UTC, bachmeier wrote:
 According to [this 
 story](https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/)
GitLab will be automatically deleting repos that are inactive for a year. Is
there a way to archive D packages that use GitLab? I don't know how much GitLab
is used, but I'd hate lose anything, considering the low cost of options such
as Backblaze B2 or S3 Glacier.

Or, I guess, other packages that someone might rage delete like 
https://forum.dlang.org/post/xfuzcjhkchdnfidnjhsf forum.dlang.org

user1234 <user1234 12.de> writes:

On Friday, 5 August 2022 at 17:37:41 UTC, bachmeier wrote:
 According to [this 
 story](https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/)
GitLab will be automatically deleting repos that are inactive for a year. Is
there a way to archive D packages that use GitLab? I don't know how much GitLab
is used, but I'd hate lose anything, considering the low cost of options such
as Backblaze B2 or S3 Glacier.

This information is already [out of 
date](https://mobile.twitter.com/gitlab/status/1555325376687226883), so don't
worry.

mw <mingwu gmail.com> writes:

On Friday, 5 August 2022 at 22:12:22 UTC, user1234 wrote:

 This information is already [out of 
 date](https://mobile.twitter.com/gitlab/status/1555325376687226883), so don't
worry.

But still I think we should cache all the dub registered packages 
as backup, in case any project get deleted for whatever reasons. 
As we've seen in the other threads.

Martin B <martin.brzenska googlemail.com> writes:

On Sunday, 7 August 2022 at 01:03:33 UTC, mw wrote:
 On Friday, 5 August 2022 at 22:12:22 UTC, user1234 wrote:

 This information is already [out of 
 date](https://mobile.twitter.com/gitlab/status/1555325376687226883), so don't
worry.

 But still I think we should cache all the dub registered 
 packages as backup, in case any project get deleted for 
 whatever reasons. As we've seen in the other threads.

Since git is a distributed version control system, used repos are 
backed up by the community automatically - as long as it's being 
used.

mw <mingwu gmail.com> writes:

On Sunday, 7 August 2022 at 08:02:52 UTC, Martin B wrote:

 But still I think we should cache all the dub registered 
 packages as backup, in case any project get deleted for 
 whatever reasons. As we've seen in the other threads.

 Since git is a distributed version control system, used repos 
 are backed up by the community automatically - as long as it's 
 being used.

The problem is that is local copy, nobody else can find the 
package and use it, that is why we need a central registry like 
dub.

bauss <jacobbauss gmail.com> writes:

On Sunday, 7 August 2022 at 16:05:09 UTC, mw wrote:
 On Sunday, 7 August 2022 at 08:02:52 UTC, Martin B wrote:

 But still I think we should cache all the dub registered 
 packages as backup, in case any project get deleted for 
 whatever reasons. As we've seen in the other threads.

 Since git is a distributed version control system, used repos 
 are backed up by the community automatically - as long as it's 
 being used.

 The problem is that is local copy, nobody else can find the 
 package and use it, that is why we need a central registry like 
 dub.

I think the best solution overall would have been to copy from 
source controls to a registry, so it doesn't fetch from github, 
but from its own registry and then only fetch each version once 
from source control.