tahoe-lafs
/
trac-2024-07-25
2
0
Issues 1.1k Wiki

help to package Tahoe-LAFS v1.10.1 for Debian/Ubuntu #2429

New Issue
Closed
opened 2015-05-22 21:10:50 +00:00 by daira · 7 comments
daira commented 2015-05-22 21:10:50 +00:00
Owner
Copy Link
No description provided.
tahoe-lafs added the
packaging
normal
defect
1.10.0
 labels 2015-05-22 21:10:50 +00:00
tahoe-lafs added this to the 1.10.1 milestone 2015-05-22 21:10:50 +00:00
warner commented 2015-06-02 16:17:07 +00:00
Copy Link

I hear vu3rdd is a debian developer.. could you see if you can package 1.10.1a1? (not for release, of course.. just to make a functional/installable .deb).

If we can do that ahead of the release, and find out what else needs to be updated (I think we'll need a new debian-packaged version of Foolscap, at least), then we should be able to reduce the lag between the Tahoe 1.10.1 release and the subsequent availability in debian/sid.

I hear vu3rdd is a debian developer.. could you see if you can package 1.10.1a1? (not for release, of course.. just to make a functional/installable .deb). If we can do that ahead of the release, and find out what else needs to be updated (I think we'll need a new debian-packaged version of Foolscap, at least), then we should be able to reduce the lag between the Tahoe 1.10.1 release and the subsequent availability in debian/sid.
warner commented 2015-06-16 01:32:01 +00:00
Copy Link

The release is out now.. package away!

The release is out now.. package away!
warner modified the milestone from 1.10.1 to soon (release n/a) 2015-06-16 01:32:01 +00:00
vu3rdd commented 2015-06-16 03:31:16 +00:00
Copy Link

Replying to warner:

The release is out now.. package away!

Built and tested the package locally. The package files are here: https://github.com/vu3rdd/tahoe-lafs-debian

I will push them into the debian unstable later today.

Replying to [warner](/tahoe-lafs/trac-2024-07-25/issues/2429#issuecomment-97352): > The release is out now.. package away! Built and tested the package locally. The package files are here: <https://github.com/vu3rdd/tahoe-lafs-debian> I will push them into the debian unstable later today.
zooko commented 2015-07-06 18:06:20 +00:00
Copy Link

vu3rdd: is this ticket now fixed and can be closed? ☺

vu3rdd: is this ticket now fixed and can be closed? ☺
vu3rdd commented 2015-07-07 01:17:16 +00:00
Copy Link

Yes.

https://packages.debian.org/sid/tahoe-lafs

Yes. <https://packages.debian.org/sid/tahoe-lafs>
vu3rdd added the
fixed
 label 2015-07-07 01:17:16 +00:00
daira commented 2015-07-07 03:53:17 +00:00
Author
Owner
Copy Link

Does the Debian package automatically get propagated to Ubuntu, or do we have to nag someone to do that (i.e. open an Ubuntu ticket)?

Does the Debian package automatically get propagated to Ubuntu, or do we have to nag someone to do that (i.e. open an Ubuntu ticket)?
vu3rdd commented 2015-07-07 04:10:22 +00:00
Copy Link

Replying to daira:

Does the Debian package automatically get propagated to Ubuntu, or
do we have to nag someone to do that (i.e. open an Ubuntu ticket)?

AFAIK from the past, it gets automatically propagated into their "universe" repository, unless something changed recently.

Replying to [daira](/tahoe-lafs/trac-2024-07-25/issues/2429#issuecomment-97359): > Does the Debian package automatically get propagated to Ubuntu, or > do we have to nag someone to do that (i.e. open an Ubuntu ticket)? AFAIK from the past, it gets automatically propagated into their "universe" repository, unless something changed recently.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear 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

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No Label
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
Milestone
Clear milestone
No items
No Milestone
soon (release n/a)
Assignees
Clear assignees
No Assignees
vu3rdd
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2429
No description provided.
Delete Branch "%!s(<nil>)"

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?