Date: Sun, 14 Aug 2022 06:04:59 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 264816] archivers/py-borgbackup: Update to 1.2.1 Message-ID: <bug-264816-21822-3a3K5b0xzm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264816-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-264816-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264816 --- Comment #8 from Matthias Andree <mandree@FreeBSD.org> --- Note that depending on when (time-wise) exactly we will have a working approved 1.2.x port of borgbackup in relation to the quarterly branch time (2022-10-01 is the nominal date to branch 2022Q4), we may want to add the update as a new py-borgbackup12 port instead and keep 1.1.y as the py-borgbackup port for a while, so as to reduce astonishment and not force migrations on users. The upstream's upgrade instructions are under "Upgrade notes:" here https://borgbackup.readthedocs.io/en/1.2-maint/changes.html#change-log The "borg won't start" issue we have just solved in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265060 was painful enough for the port's users, we should avoid hurting them again. Backup is a sensitive topic. Also note that I see two self-test failures from "make test" with my proposed update. I have not investigated them up close yet. Expect "make test" to run for like 15 minutes even on reasonably fast computers under Python 3.9, or else, longer. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264816-21822-3a3K5b0xzm>