Ticket #481 (closed enhancement: fixed)

Opened 15 years ago

Last modified 12 years ago

Upgrade debhelper compatibility level

Reported by: broder Owned by:
Priority: normal Milestone: Precise Release
Component: development Keywords:
Cc: Fixed in version:
Upstream bug:


Now that Sarge is gone, we no longer need to declare a debhelper compatibility level of 4. Furthermore, we probably shouldn't, and there are probably places where we're not actually compatible with dh 4.

So long as Etch and Hardy are still around, we can only bump it to 5. But we probably should do so anyway.

Change History

comment:1 Changed 15 years ago by geofft

I'm not yet sure how straightforward this is. A cursory scanning of the manpages indicates dh_strip --dbg-package changed its semantics after v4, but nothing else at this version, so maybe this will be easy, but we should definitely look more carefully.

comment:2 Changed 14 years ago by jdreed

  • Milestone set to The Distant Future

comment:3 Changed 13 years ago by jdreed

  • Priority changed from low to normal
  • Milestone changed from The Distant Future to Natty Release

This is actively throwing warnings during the build process these days, so let's go ahead and do this.

comment:4 Changed 12 years ago by jdreed

OK, the only things calling dh_strip are debathena/third/schroot (I really think we can move this to the attic, it's jaunty-only, right?) and third/moira, and both are using dh5 syntax anyway, so we can go to 5.

We should probably go to 6, which is available in everything we care about. The major change appears to be the maintainer script fragment reverse order. Is there anything we have that could possibly care about that? I don't thinkso

comment:5 Changed 12 years ago by jdreed

  • Status changed from new to committed

r25600, all added as UNRELEASED changes.

comment:6 Changed 12 years ago by jdreed

I'm not rebuilding the world yet, we'll pick most of this up in the Qantas rebuild. I reserve the right to flip out and rebuild everything later. Ben notes we might end up not building some of these before going straight to 7 once Hardy is dead, but since this only affects builds, I think I'd prefer a bunch of UNRELEASED packages and attrition to possible skew and the time and effort involved in a full rebuild, particularly at this point in the release cycle.

comment:7 Changed 12 years ago by jdreed

  • Status changed from committed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.