Feature #6563

Backport syslinux 6.x for Wheezy

Added by intrigeri 2014-01-02 11:42:51 . Updated 2014-11-10 16:04:26 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2014-01-02
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

For Tails 1.1, we’ll carry a custom backport, likely with a backported upstream bugfix (Bug #7232). But then, once syslinux 6.03-pre5 or later reaches Jessie, we would like to use an official one.


Subtasks


Related issues

Related to Tails - Feature #5739: Support UEFI boot Resolved 2013-10-03
Blocked by Tails - Feature #7174: Wait for syslinux 6.03-pre5 or later to be in Debian Resolved 2014-05-08

History

#1 Updated by intrigeri 2014-03-31 13:49:58

#2 Updated by intrigeri 2014-05-03 10:43:43

Its maintainer said he wants to upload syslinux 6.x to sid in two weeks.

#3 Updated by intrigeri 2014-05-13 08:55:05

  • blocked by Feature #7174: Wait for syslinux 6.03-pre5 or later to be in Debian added

#4 Updated by intrigeri 2014-05-13 08:57:46

  • Description updated

#5 Updated by intrigeri 2014-05-13 08:58:53

  • blocked by Feature #7173: Upgrade to syslinux 6.03-pre18 or later added

#6 Updated by intrigeri 2014-05-13 08:59:18

  • blocks deleted (Feature #7173: Upgrade to syslinux 6.03-pre18 or later)

#7 Updated by intrigeri 2014-06-29 09:41:17

Now waiting for syslinux 6.x to migrate to Jessie.

#8 Updated by intrigeri 2014-07-22 17:22:04

> Now waiting for syslinux 6.x to migrate to Jessie.

Done.

#9 Updated by BitingBird 2014-07-22 17:57:55

So it has to be backported in Debian now ?

#10 Updated by intrigeri 2014-07-22 18:12:17

> So it has to be backported in Debian now ?

Exactly. Which generally starts with getting in touch with the maintainer, making sure they don’t mind / have no plans to do it themselves, etc. Note that I have already done the backporting work.

In this case, the main problem is that the backport probably should have Breaks relationships added, which I didn’t do yet. And then, it’ll conflict with many other packages. The backports ftp-masters might not like this too much.

#11 Updated by intrigeri 2014-07-28 22:39:04

  • Status changed from Confirmed to In Progress

Asked the syslinux maintainer how he feels about it.

#12 Updated by intrigeri 2014-11-10 16:04:26

  • Status changed from In Progress to Rejected
  • Assignee deleted (intrigeri)

No reply from the maintainer, and as said in comment 10, the backport either would require a lot of work (that is, backporting changes to quite a few reverse-dependencies, and adding versioned Breaks+Replaces), or would not be very useful (with the right Breaks+Replaces in place, it would not be co-installable with a lot of other packages, so maybe not even useful for Tails). So, dropping the ball on that one, let’s keep using our custom backport, and focus on migrating to Jessie instead.