don't upload debs built from a branch #1308

Closed
opened 2011-01-14 07:44:19 +00:00 by davidsarah · 1 comment
davidsarah commented 2011-01-14 07:44:19 +00:00
Owner

(http://tahoe-lafs.org/buildbot/builders/deb-lenny-i386-arthur/builds/177) built debs for a branch (ticket1306), and uploaded them to tahoe-lafs.org and the apt repository. That should only happen for trunk. (The deb name includes the version, but that's not enough because revision numbers are not unique across branches.)

(http://tahoe-lafs.org/buildbot/builders/deb-lenny-i386-arthur/builds/177) built debs for a branch (ticket1306), and uploaded them to tahoe-lafs.org and the apt repository. That should only happen for trunk. (The deb name includes the version, but that's not enough because revision numbers are not unique across branches.)
tahoe-lafs added the
dev-infrastructure
critical
defect
n/a
labels 2011-01-14 07:44:19 +00:00
tahoe-lafs added this to the soon (release n/a) milestone 2011-01-14 07:44:19 +00:00
davidsarah commented 2011-08-16 00:49:13 +00:00
Author
Owner

Is this still relevant, or should we disable those builders now that we're relying on the official Debian tahoe-lafs packages?

Is this still relevant, or should we disable those builders now that we're relying on the official Debian tahoe-lafs packages?
tahoe-lafs added the
invalid
label 2011-08-26 21:54:57 +00:00
davidsarah closed this issue 2011-08-26 21:54:57 +00:00
Sign in to join this conversation.
No Assignees
1 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#1308
No description provided.