From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: Removing the attic package
Date: Sun, 4 Sep 2016 14:44:16 -0400 [thread overview]
Message-ID: <20160904184416.GB29947@jasmine> (raw)
In-Reply-To: <874m5vvmi8.fsf@we.make.ritual.n0.is>
On Sun, Sep 04, 2016 at 01:10:39PM +0000, ng0 wrote:
> There has been no update since 2015. Can the current status of the bug
> (solved? unsolved? wontfix? work in progress?) be requested from the
> upstream developer(s)?
The upstream developer has not replied to the bug report [0]. I think we
can assume "wontfix" after 11 months.
> Otherwise the bug reads like we should include it in our package
> description, pointing out that it is currently limited to 15GB backup
> (if that's what this was about, I did not read all of it).
The bug is that if your disk becomes full, the backup repository will be
permanently corrupted, and you will *lose all your backups*.
I think the project is abandoned, even though it has only been ~15
months since the last public commit, which is not really that long if
the software is working well. But, it's not working well; this is a
critical bug.
Here is some context:
I was following Attic development before it stopped. There were several
Attic users who wanted to assist with Attic development, but the Attic
author explicitly rejected their help [1]. It appears that the Attic
author abandoned Attic after the Borg fork.
I don't want to steer new users towards this broken software, and I
think removing the package is a safe choice. Current Attic users could
continue to use it, because it won't be removed from their profile
unless they do `guix package --remove attic`. And Borg can convert Attic
repos for users who are interested in moving on, so these users will not
lose access to their data even if they do uninstall Attic on their
machines.
Do we have any guidelines about "retiring" packages?
[0]
https://github.com/jborg/attic/issues/356
[1]
https://github.com/jborg/attic/issues/217#issuecomment-78091278
next prev parent reply other threads:[~2016-09-04 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 2:12 Removing the attic package Leo Famulari
2016-09-04 13:10 ` ng0
2016-09-04 18:44 ` Leo Famulari [this message]
2016-09-05 8:20 ` Ludovic Courtès
2016-09-05 8:34 ` Ricardo Wurmus
2016-09-05 9:29 ` Efraim Flashner
2016-09-05 10:05 ` ng0
2016-09-05 10:20 ` ng0
2016-09-06 21:36 ` Superseded packages Ludovic Courtès
2016-09-10 17:25 ` Leo Famulari
2016-09-11 13:46 ` Ludovic Courtès
2016-09-11 15:19 ` Leo Famulari
2016-09-11 20:39 ` Ludovic Courtès
2016-09-20 21:18 ` Leo Famulari
2016-09-24 2:14 ` Ludovic Courtès
2016-09-25 16:42 ` Leo Famulari
2016-09-26 9:44 ` Efraim Flashner
2016-09-27 21:39 ` Leo Famulari
2016-09-28 8:44 ` Ludovic Courtès
2016-09-28 17:58 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160904184416.GB29947@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).