[19:04] <danjared> What's up with this?
[19:04] <danjared> Unpacking linux-image-extra-3.13.0-63-generic (3.13.0-63.103) ...
[19:04] <danjared> dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-3.13.0-63-generic_3.13.0-63.103_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-3.13.0-63-generic 3.13.0-63.104~precise1
[19:11] <danjared> argh, somehow I have a precise kernel on this system
[20:50] <apw> danjared, are you doing an upgrade ?
[20:51] <apw> that looks like an lts backport being overritten by a non-lts version of the same package
[20:52] <apw> otherwise it looks like you have a linux-image package for trusty and an lts backport of near same version from precise
[20:52] <apw> and they ought not be on the same machine
[20:52] <infinity> Which is fine, but why is that module in extra in one, and in image in the other.
[20:52] <infinity> apw: The problem is the split being different, so it's not upgrading correctly.
[20:52] <infinity> Which is... Weird.
[20:53] <apw> well it depends if it is an upgrade, if not its just fail
[20:53] <apw> if it is then we hasve moved something in one release and the breaks only affect the same package
[20:53] <infinity> apw: That upgrade is meant to work. :P
[20:53] <apw> so its broken
[20:53] <infinity> It's from precise+lts to trusty, if you read the output.
[20:54] <apw> ie the breaks you'd need ofr th move need to affect linux <= X and linux-lts-trusty <= X
[20:54] <apw> and they arn't there 
[20:54] <infinity> And it's saying extra has the module on trusty, and image has it on lts-trusty.
[20:54] <infinity> Shouldn't need a breaks, should just need the split to match.
[20:54] <infinity> So extra upgrades extra and image upgrades image.
[20:54] <apw> but one is one upload older
[20:54] <apw> so if the move occured ni a non-abi bumper, that might account for it
[20:54] <infinity> But yes, maybe the module moved between those uploads?
[20:54] <infinity> Seems unlikely, though.
[20:54] <apw> or ... as you say the split could just be wrong
[20:54] <infinity> Moves should be an ABI break.
[20:54] <apw> ie not copied back ... 
[20:55] <apw> moves should be an abi break but arn't no doubt
[20:55] <apw> so i suspect we moved one in the non-lts and didn't backport it right ...
[20:55] <infinity> They have to be, the ABI checker screams when a module moves.
[20:55] <apw> bjf, ^
[20:55] <apw> it notices when the old had and the new does not
[20:55] <apw> if it is in either we have it from the module checker point of view
[20:55] <apw> and likely we should notice and hwine
[20:56] <infinity> Oh, it doesn't check post-split?
[20:56] <apw> but ... i bet this is different in lts and non-lts because we don't copy it
[20:56] <infinity> That's probably a bug.
[20:56] <infinity> But it's probably just a bad backport.
[20:56] <apw> copy the module-inclusion.generic
[20:56] <apw> sigh
[20:56] <apw> and now we are pooped
[20:56] <infinity> If you could check the split difference and just commit a fix for next upload?  I don't care if old ones don't upgrade right.
[20:56] <infinity> Life's like that sometimes.
[20:56] <apw> danjared, could you file a bug against linux-lts-trusty for us with the details above and drop the bug number in here
[20:57] <apw> danjared, and ping me with it
[20:57] <apw> and i'll get it fixed up
[20:57] <apw> now how does he get out of this
[20:57] <infinity> Dear armhf test runner, run tests faster.
[20:58] <infinity> apw: Best way out is just to dpkg -i --force-overwrite /var/cache/apt/foo.deb 
[20:58] <infinity> danjared: ^
[20:59] <infinity> 103 and 104 were identical, so it didn't move between uploads.
[21:00] <infinity> It's just a backport bug in the split, then.
[21:01] <infinity> I don't think lts-trusty has the new and improved "rsync all the things" backport method.
[21:01] <infinity> So, it's potentially sketchy and out of sync.
[21:03] <apw> yeah, likely
[21:05] <apw> danjared, ... ok i'll file a bug now
[21:07] <apw> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1492466
[21:07] <apw> will sort later