[01:27] if there is a package in universe which has a Ubuntu-specific patch which has been rolled up into the upstream debian version, is there anything that needs to happen manually? or will the debian import figure this out? [01:28] specifically, the digitemp package. I am now the debian maintainer for it, and a new upload is on its way to sid [04:56] fo0bar: Something needs to happen. It needs a sync request. See syncpackage in ubuntu-dev-tools. [05:27] ScottK: ahh right, thank you === nenolod is now known as moogle === moogle is now known as nenolod === nenolod is now known as nenolod_ === nenolod_ is now known as nenolod === Nafallo is now known as Nafallo_ === Nafallo_ is now known as Nafallo === cjwatson is now known as cjwatson_ === cjwatson_ is now known as cjwatson [13:53] freenode services will be upgraded soon, if you're around and have ops here, please op up incase a troll swarm hits. === elky is now known as melissa === melissa is now known as Guest28480 === Guest28480 is now known as elky === ashams_ is now known as ashams [17:39] paultag: welcome [17:39] Greetings MOTU people [17:40] I come to you because as the maintainer of tcc in Debian, I feel concerned about its state in Ubuntu [17:41] In particular, I see that Oneiric uses 0.9.25-10 which fails to build on armel [17:41] The current version in Debian (as well as any 0.9.26~foo IIRW) builds on armel [17:42] It also builds on armhf but it will generate armel code so I don't think it's interesting to build it on armhf [17:42] I think no tcc on armel is acceptable for a short support term release [17:42] Hence I was thinking a stable upgrade of tcc might be worthwhile [17:42] but if you have a patch, an sru can be done [17:42] RoboTux: hi :) [17:43] jtaylor_: oh, I thought Oneiric was a LTS [17:43] I must confuse with Precise [17:43] precise is the lts which appears to ahve tcc on arm [17:43] Indeed [17:43] Ok then, sorry for the noise [17:43] RoboTux: an update for oneiric is still a good idea [17:44] it's still supported [17:44] but its no regression [17:44] earlier releases never had it on arm [17:44] paultag: I don't know if it's that worthwhile [17:44] there's LP: #823716 - safe to close/ignore? [17:44] It would if armhf was supported but as you know, it's not fully the case yet [17:44] jtaylor_: ^ [17:45] paultag: I'm so sorry for disturbing you for nothing [17:45] RoboTux: it's quite alright, I'm happy to help. [17:46] By the way, it seems the fix for the kfreebsd problem is pending \o/ [17:46] paultag: it should be marked fix released, if someone prepares an sru I can nominate it [17:46] but I agree with RoboTux that its probably not worth the effort [17:46] jtaylor_: I don't think there will be an sru [17:47] I tried to fix it by backporting patches in Debian but never succeeded [17:47] It seems several patches are needed, I don't know which ones and they are non trivial to backport [17:47] jtaylor_: I'm fine with closing it fixed release [17:47] the source tree was completely reorganized since 0.9.25 [17:47] then no update the risk of regression outweights the benefit [17:47] Definitely [17:47] yep. [17:47] alright, thanks jtaylor_, I'll close that out. [17:48] Thanks jtaylor_ and paultag [17:48] paultag: I don't know how many beers I owe you now :] [17:48] RoboTux: closed :) [17:49] Maybe it'll be cheaper to bring you some strong chinese alcohol the day we meet [17:49] Great [17:49] :) [17:51] See ya [17:55] micahg: I've now managed to testbuild the branch, and the result looks OK to me [17:56] micahg: I'm now having dinner, but unless I hear from you, I'm going to upload libav-extra afterwards === ashams_ is now known as ashams === ral is now known as oojah === oojah is now known as ral === yofel_ is now known as yofel