Ticket #456 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

Maintainer for debathenified packages should be Debathena

Reported by: broder Owned by: broder
Priority: low Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

For reasons more or less identical to those in < https://wiki.ubuntu.com/DebianMaintainerField>, when we modify somebody else's package, we should stick our name on it and not theirs.

The debathenificator should be able to move the Maintainer field to XSBC-Original-Maintainer, and put us down as the Maintainer.

We're actually only using the debathenificator framework for lprng right now, making it the only package affected by this, but we should be sure to bump its version number and rebuild when we fix this.

Change History

comment:1 Changed 12 years ago by broder

Incidentally, what should we do if a package already has an Original-Maintainer set? Original-Original-Maintainer? Drop the old Original-Maintainer?

comment:2 Changed 12 years ago by broder

  • Owner set to broder
  • Status changed from new to accepted

I attempted to fix this in r24211 and r24212. Unfortunately, the debathenificator stopped working after I committed the change - specifically lprng fails to build if it's run under da (but not if I run ./debathenify-lprng or sbuildhack directly). I have no idea why that is, but ideas would be appreciated.

I've paused the autodebathenificator until we figure out what's up

comment:3 Changed 12 years ago by broder

  • Status changed from accepted to closed
  • Resolution set to fixed

The a18r started working again at some point, so all of the packages we're actively building should have a maintainer of Debathena.

Note: See TracTickets for help on using tickets.