On jeu., 2013-02-07 at 13:19 +0100, Daniel Baumann wrote: > On 02/07/2013 01:02 PM, Yves-Alexis Perez wrote: > > - I have no idea if it's syslinux or syslinux-themes-debian fault > > did you read the other bug?
Actually yes, even without being bitten by the bug it'd be hard to miss. > > usually, opening a duplicate bug doesn't mean that the maintainer will > re-tell the whole story again, and that pointing to the first bug about > the same issue should be enough, so that the bug reporter would read it > there when being pointed at it. > > > - the bug is still present in 2:5.01+dfsg-1 / 12-1.1 > > that's why it's open and not closed yet. Yeah, I was merely pointing out that version tracking was definitely confusing here (because of the reassigns) > > > If it needs manual tuning in some scripts to port it to the new > > syslinux, then fine, you seem to be the de factor maintainer of both > > packages so everything's under your control. > > look at the live-build commit and replicate it in > /usr/share/syslinux/theme/$your_theme, Actually it's $your_theme, but eh. > or wait until the theme in debian > is fixed. I'm waiting. -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
