[11:35] <TandyUK> run-parts: /etc/cron.hourly/mythtv-frontend exited with return code 1
[11:35] <TandyUK> run-parts: /etc/cron.hourly/mythvideo exited with return code 1
[11:35] <TandyUK> any idea how i can top that?
[11:36] <TandyUK> STOP*
[11:36] <TandyUK> i dont wannt to silence cron thoguh as i need the reports if there is a real error
[11:38] <TandyUK> oh i see
[11:38] <TandyUK> old shit you can be arsed to delete
[11:38] <Zinn> TandyUK: Please watch your language.
[11:39] <TandyUK> if your gonan update a package and add a 'fix' delete the file when you no longer need it
[11:39] <TandyUK> insstead of leavign it to sit around indefinitely until someone investigates the error
[11:39] <TandyUK> i wonder how many people just set a mailto="" line to shut cron up
[14:06] <superm1> TandyUK: there was a server bug in autobuilds that only affected builds from one day
[14:06] <superm1> for -fixes builds
[14:06] <superm1> if you happened to upgrade to that day's builds, those files showed up when they shouldn't
[14:07] <TandyUK> this has been going on for months
[14:07] <TandyUK> the machien is set to auto update
[14:07] <superm1> that's nearly 6 months ago though
[14:07] <superm1> ah :)
[14:07] <TandyUK> yeah my customer just told me how thheyve been getting emails  from cron on a daily bass
[14:07] <superm1> not many people complained about it so after fixing the server bug the next day we decided it wasn't necessary to figure out the right stuff in postinst to clean it up
[14:08] <TandyUK>  bet many people have the bug, just cron is silenced
[14:08] <superm1> it's possible yeah
[14:08] <TandyUK> both myth boxes on this site had it
[14:08] <TandyUK> so i bet every other 'appliance' type myth box does too
[14:08] <superm1> well only if they actually installed updates from that day
[14:09] <TandyUK> its daily updates
[14:09] <superm1> at least most of the people we were querying only install them every few days
[14:09] <TandyUK> so ofc it did
[14:09] <superm1> if you'd like to help work out the stuff that goes in postinst to clean up those files properly, i'll be glad to help merge a patch
[14:09] <TandyUK> but anyhow ive shut my boxes up now
[14:10] <TandyUK> how hard is it to "rm /etc/cron.daily/mythtv-frontend"
[14:10] <superm1> well there's more to it, you have to key off of what version they're upgrading from
[14:10] <superm1> and what they're upgrading to
[14:10] <superm1> because those files do have a purpose in some versions
[14:11] <superm1> so it's a dpkg --compare-versions test that needs to go in there
[17:40] <dekarl> superm1: the build script from packaging doesn't like running twice on the same build dir (to avoid pulling everything again) because of the uncommited changes to mythtv/VERSION
[18:02] <superm1> dekarl: hmm interesting
[18:03] <superm1> so during the clean phase it needs another call then
[18:03] <dekarl> or shall I just always remove the build directory?
[18:03] <superm1> dekarl: was that with a source package run or a binary package run
[18:03] <superm1> you shouldn't have to remove the build directory (we don't for autobuilds)
[18:03] <dekarl> build-debs.sh
[18:03] <superm1> ok so that was a binary package run
[18:04] <superm1> can you pastebin how it fails?
[18:04] <dekarl> to late
[18:04] <superm1> dang
[18:04] <superm1> well off hand do you remember what was complaining about that file?  was it git?
[18:04] <dekarl> basically it complains when git pulling about local changes in the way
[18:04] <superm1> ok so probably during the debian/rules get-git-source then
[18:05] <dekarl> I'd try to recreate but the script doesn't like the patch I'd like to test :(
[18:05] <superm1> what's wrong with that?  wrong patch level?
[18:06] <dekarl> tells me to refresh the patch because it can't unapply it
[18:06] <dekarl> ahh, I could convince it to build without patch at least
[18:06] <superm1> that's werid though
[18:06] <superm1> it should have cleaned up a failed patch run
[18:07] <dekarl> I'll try again
[18:07] <superm1> it must have been a side effect of this not being able to do a full binary build twice because of that mythtv/VERSION failure
[18:08] <superm1> i think two things need to happen then
[18:09] <superm1> 1) during the checkout it needs to clean the tree if necessaary
[18:09] <superm1> 2) add a trap to the shell script to catch failures at any step, not just the patch testing
[18:17] <superm1> dekarl: ok i think i fixed up <1> via changes to the bzr, shouldn't happen now as long as the build is successful each time
[18:20] <dekarl> thanks, we'll see
[18:30] <dekarl> end of succesgul build without patch and start of another round http://paste.ubuntu.com/735522/
[18:30] <Zinn> [paste.ubuntu.com] Ubuntu Pastebin
[18:38] <dekarl> "git stash" and starting again (now with a patch again) works... it's the same patch that wasn't working earlier
[18:40] <superm1> ah but you didn't have the updated bzr for teh first run
[18:40] <superm1> that's why
[18:41] <superm1> i see that it was updated for that second though
[18:41] <superm1> that's the key
[18:43] <dekarl> I think so, too
[18:43] <dekarl> you fixed it while it was already running
[23:55] <antnash_> Evening guys. Can I install mythbuntu onto existing LVM partitions?