Feature #6087

Cleanup liveusb-creator packaging

Added by Tails 2013-07-18 07:50:42 . Updated 2014-07-22 23:00:14 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

The current state of liveusb-creator packaging is, well, suboptimal. Just have a look at the content of the liveusb-creator_3.11.6.orig.tar.gz so-called original source tarball to get an idea. It’s not clear wether "upstream", from a Debian packaging point-of-view, means "Fedora" or "our master Git branch".

Due to this confusion (and lack of interesting changes in there), I’ve refrained from merging upstream 3.11.7 into our tree.


Subtasks


Related issues

Related to Tails - Feature #7095: Integrate the new logo in Tails Installer Resolved 2014-04-15

History

#1 Updated by intrigeri 2014-05-11 03:08:20

  • Subject changed from cleanup liveusb-creator packaging to Cleanup liveusb-creator packaging
  • Description updated
  • Category set to Installation
  • Starter set to No

#2 Updated by intrigeri 2014-05-11 03:08:32

  • related to Feature #7095: Integrate the new logo in Tails Installer added

#3 Updated by intrigeri 2014-05-11 03:39:02

  • Status changed from Confirmed to Fix committed
  • Target version set to Tails_1.1
  • % Done changed from 0 to 100

For Feature #7095, I had to regenerate a new “upstream” tarball, and settled on the following: from now on, “upstream” means, from a Debian packaging point-of-view, the state of our master branch. Let’s not pretend we have not forked liveusb-creator, and admit we are now upstream for our own version.

Still, most of the time, we will be releasing -N “Debian”-specific packages, that really are packaged Git snapshots, rather than new “upstream” releases. Only when we really need it, we will update the “orig” tarball from our master branch.

I have documented this in the liveusb-creator release process doc, calling this a fix.

#4 Updated by BitingBird 2014-07-22 23:00:14

  • Status changed from Fix committed to Resolved