This is blocking pyxattr.
0.30 still is py2 only so bumping is a waste of time. but git master has lots of python3 commits, so let's hope they make a new release soon.
Had a talk with upstream in irc and raised some urgency to make a python-3 based release before introducing major breaking changes. We'll see.
Are you interested in becoming a maintainer for it?
Also note that pylibacl is now py3-only.
I can't pick up any additional packages.
Hmm, I guess that means lastriting app-backup/kup as well.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a658b4b3604a092193b3eb9184000afd19693c26 commit a658b4b3604a092193b3eb9184000afd19693c26 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-04-23 11:20:43 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-04-23 11:23:36 +0000 package.mask: Last rite app-backup/bup, app-backup/kup Bug: https://bugs.gentoo.org/713366 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 6 ++++++ 1 file changed, 6 insertions(+)
I use bup and kup so I'd quite like to see them reintroduced to Portage once they've been ported to Python 3. Is that likely to happen given the current state of things, or if not would it help if I volunteer as a proxy maintainer? While my free time is pretty limited, hopefully I could handle these couple relatively small packages.
Having someone (proxy-)maintain app-backup/bup who is actively using it would certainly be good. In that case kde proj will be able to keep app-backup/kup in the tree. However the burden is on upstream right now to actually create a py3-based release. One issue seems to be some lack of awareness what a release can do to keep their software relevant; the main guy doing the py3 porting work does not really seem to care about (but also does not block making) releases at all and is already way ahead with major changes.
Thanks Andreas (and sorry for the late response; I missed the email about your reply). I fully agree that the burden is on upstream. How about this: I'll watch the mailing list for when they make a new release that supports Python 3, and at that point I'll submit a request to reintroduce the package to the tree with myself as a proxied maintainer for it, following the directions on the wiki. It does look like the bup maintainers have some kind of plan (https://groups.google.com/forum/#!topic/bup-list/bXhVRnt_cXE), although it's not clear what timescale they have in mind.
Sure. When you do that, please ping us that it's a reintroduced package, so we'll prioritize it over new packages.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea4ac42ea4f9f77410a783fdb46d630925955ecf commit ea4ac42ea4f9f77410a783fdb46d630925955ecf Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-05-23 09:52:36 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-05-23 09:53:32 +0000 app-backup/bup: Remove last-rited pkg Closes: https://bugs.gentoo.org/713366 Signed-off-by: Michał Górny <mgorny@gentoo.org> app-backup/bup/Manifest | 1 - app-backup/bup/bup-0.29.2.ebuild | 58 --------------------------- app-backup/bup/files/bup-0.29.2-sitedir.patch | 38 ------------------ app-backup/bup/metadata.xml | 11 ----- profiles/base/package.use.mask | 4 -- profiles/package.mask | 5 --- 6 files changed, 117 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=409d596d048a300233d0e439007f343b805c86ad commit 409d596d048a300233d0e439007f343b805c86ad Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-05-23 09:52:29 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-05-23 09:53:31 +0000 app-backup/kup: Remove last-rited pkg Closes: https://bugs.gentoo.org/713366 Signed-off-by: Michał Górny <mgorny@gentoo.org> app-backup/kup/Manifest | 1 - app-backup/kup/files/kup-0.7.3-libgit2.patch | 140 --------------------------- app-backup/kup/kup-0.7.3.ebuild | 57 ----------- app-backup/kup/metadata.xml | 8 -- profiles/package.mask | 1 - 5 files changed, 207 deletions(-)
(In reply to David Zaslavsky from comment #8) > would it help if I volunteer as a proxy maintainer? While my free time is > pretty limited, hopefully I could handle these couple relatively small packages "Call for testing for a 0.31 release (supporting Python 3)" https://groups.google.com/forum/#!msg/bup-list/HmGgQrzLcmM/NFgIf3hWCAAJ
0.31 released: https://github.com/bup/bup/releases/tag/0.31 Release notes: https://github.com/bup/bup/blob/5967a4cdb76c8c70409cfe16cc1b78683ef16de6/note/0.31-from-0.30.1.md
