Bug#805268: Adoption of syslinux
On Sat, Nov 12, 2016 at 03:27:49PM +0000, Iain R. Learmonth wrote:
>Hi,
>
>On Sat, Nov 12, 2016 at 12:52:24PM +0100, Christian Seiler wrote:
>> Oh, I didn't know you were also planning to adopt it - the package
>> had been orphaned for quite a while now, and I just assumed there
>> were no other takers.
>
>No problem, we should have been speedier at sending the emails.
>
>> I'd be very happy to co-maintain the package though - I just didn't
>> mention that in the ITA mail because I thought that if someone else
>> was interested in the package, they'd have already adopted it by
>> that time.
>
>I've CC'd the CD team, I wonder if we'd like to set the maintainer line to
>Debian CD. If not, we can set it to Debian Live. I'd definitely want to have
>this maintained by one of those teams.
Makes sense, yes. Whatever makes most sense to you guys, really. We're
looking at starting up (or maybe switching to) a Debian Images team,
whic might work even better?
>> My plans for the package were to update to a newer upstream
>> version (there's a -pre1 from the beginning of this year of
>> 6.04 IIRC, but I wanted to go through upstream git to see if
>> a git snapshot might not be better suited), and improve the
>> packaging were needed. (Though the last QA upload already did
>> quite a bit there.) I then wanted to ask for sponsorship for
>> an upload to experimental first and let it stew there for a
>> while before going on to sid.
>
>Unless there are big objections from Debian CD, I'd really like to not make
>any changes for syslinux that may cause breakage in the release process. I'm
>happy that we can do bugfix uploads, but I wouldn't want to make any updates
>to new upstreams before stretch is released (or at least, wouldn't want
>those updates migrating to stretch though we could load them into unstable
>after the final freeze).
Definitely, and thanks for thinking of us. We've had a very bad
historical experience with breaking changes hitting us around release
times.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"I've only once written 'SQL is my bitch' in a comment. But that code
is in use on a military site..." -- Simon Booth
Reply to: