package Tahoe-LAFS for Fedora #170
Labels
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: tahoe-lafs/trac-2024-07-25#170
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In theory, you can run "./setup.py bdist_rpm" and an "allmydata-tahoe.rpm" package will magically appear. In practice, I don't have access to an RPM-using operating system, so I can't try it.
If anybody tries that and reports the results here I would appreciate it!
Bumping this to v0.7.
I don't want to do this, but I want somebody to do it for v0.6.2. Oh heck, I'll do it if someone will give me ssh access to a Fedora system. :-)
We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.
We need to choose a manageable subset of desired improvements for v0.7.1, scheduled for two week hence, so I'm bumping this one into v0.7.2, scheduled for mid-December.
Is this bug still relevant?
Ruben Kerkhof has done a lot of work on packaging Tahoe-LAFS and its dependencies for Fedora. It looks like zfec and pycryptopp are approved for inclusion in Fedora!
https://admin.fedoraproject.org/pkgdb/acls/name/python-zfec
https://admin.fedoraproject.org/pkgdb/acls/name/pycryptopp
Let's change the meaning of this ticket to packaging Tahoe-LAFS for Fedora and assign it to Ruben. :-)
build RPMsto package Tahoe-LAFS for FedoraProbably via fpm in this day and age
Ticket retargeted after milestone closed