=== bradm changed the topic of #ubuntu-devel to: Wiki.ubuntu.com upgrade in progress | Oneiric Alpha 1 released | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [00:24] What? Gah! There should be an easier way of testing armel builds than failing on the buildd. [00:25] there's a porter machine [00:25] and there's qemu [00:25] Yeah, there's the porter machine. [00:25] RAOF: apt-get install qemu-user-static; /usr/sbin/qemu-debootstrap -aarmel [...] [00:25] The buildds take *8 hours* to build mesa; a local build would still be going from yesterday. [00:26] there's a cross-compiler package :) [00:26] I've got an armel schroot, and for things smaller than mesa it's very nice :) [00:28] This typo was in the install target of debian/rules though, so… urgh. [00:28] slangasek: an ubuntu porter machine? [00:28] you've inspired me to check whether I can get away with cross-installing all the mesa build-deps with mulitarch [00:29] directhex: a Canonical ubuntu porter machine, sorry :/ [00:29] shell access in the DC, company policy, etc etc [00:29] yeah, that's fine. i've never encountered an arm bug on ubuntu's smp omap4 target that i haven't hit on a single-core efikamx [00:29] no, wait, the opposite of what i just said [00:30] the porter machine isn't an smp omap4 anyway [00:30] winnar [00:30] When will multiarch stop killing update-manager? [00:31] :) [00:37] RAOF: oh, how's it killing it for you? It works for me! :) [00:37] i'm sure i can badger access to a pandaboard in the office if i need to (note: this is a lie) [00:38] Hm. Last time I tried it would kinda refresh the apt cache and then die with an inscrutable error message. [00:38] And I went back to apt-get update && apt-get dist-upgrade… [00:38] I'll try again once apt's finished :) [00:38] RAOF: so as of the last u-m changes before the natty release, all those issues have been resolved for me [00:40] I'll try again, and this time report bugs when they fail. [00:41] yay :) [00:41] So, does this mean we're actually quite close from being able to drop mesa from ia32-libs? [00:41] What's left before i386 is a default foreign arch? [00:42] we wouldn't drop mesa from ia32-libs, we would want to drop ia32-libs itself from the archive [00:43] "what's left" - we need to be satisfied that turning on i386+amd64 isn't going to carry so much a penalty in index download time that it makes it (more) painful to run apt-get update [00:46] Hm. Looks like update-manager's perfectly happy now. [00:46] Yeah. I'm now downloading ~50MB of apt indexes. [00:59] slangasek: Ah. The partial-upgrade tool seems be spinning indefinitely. Is there any debugging information I can nab before killing it? [00:59] RAOF: mm, no idea on that, sorry [00:59] Not something you've run into? [01:00] Ok. Well, I'll file a bug and see. [01:01] RAOF: nope, not run into it that I can recall [01:13] slangasek: bug 798478 [01:13] Launchpad bug 798478 in update-manager (Ubuntu) "Partial upgrade spins indefinitely in “Preparing to upgrade” with multiarch" [Undecided,New] https://launchpad.net/bugs/798478 [01:14] Ah, need to update the title. It doesn't spin indefinitely, it waits for you to submit a bug and then throws up an error message :) [01:19] heh :) [01:37] slangasek: http://online.wsj.com/article/SB10001424052702304066504576345782284098222.html?KEYWORDS=telecommuting+tax [01:37] ouch [01:37] which state is Canonical Inc incorporated in, again? :) [01:38] isle of man, iirc? [01:38] directhex: that's Canonical Ltd [01:39] New York and New Jersey have extremely punitive tax codes [01:39] http://www.manta.com/c/mtvfcjz/canonical-usa-inc [01:39] Keybuk: handy. maybe there's more reason for collabora.ca than i thought [01:40] directhex: well, .ca has that law that defines the difference between an employee and a contractor, right? [01:40] dunno, but we have plenty of contractors on the payroll :p [01:40] there is, I believe, also a Canonical Canada Ltd [01:41] it's funny how sladen stopped his Canonical tax accounting stalking when he joined ... [01:41] it's also funny that he's not a DD [01:41] hehe [01:42] it's also funny that he eats ice cream with chopsticks === asac_ is now known as asac [03:30] Hello all. Seeking assistance in finding procedure for updating /etc/motd w/o reboot: [03:30] distro: ubuntu server 10.04 [03:30] /etc/motd gets modified to the value of /etc/lsb-release:DISTRIB_DESCRIPTION. But this only takes effect after rebooting (more specifically, I think it's already modified before the reboot, when switching to RUNLEVEL 1). [03:30] Can /etc/motd be auto-modified w/o a reboot? [03:34] amit: you might want to try #ubuntu-server [03:36] micahg: ok, 10x. === bradm changed the topic of #ubuntu-devel to: Oneiric Alpha 1 released | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [03:44] ubuntu wiki upgrade is done, please let us know if there are any troubles [03:48] bradm: login seems to be taking forever [04:29] kees: Canonical, USA is incorporated in Delaware, like all corporations worth their salt [04:29] eh [04:29] kees: not you, the Keybuk who dodged :P === _LibertyZero is now known as LibertyZero [06:05] Good morning [06:24] hmm -- wiki, where are thou? [06:24] pitti: It was upgraded, do you have an issue? [06:25] trying to login, it times out [06:25] anonymous viewing works [06:27] I can duplicate that [06:38] SpamapS: darn, lucid's launchpadlib doesn't yet work with the launchpadlib queue count; I reverted that change to screenscraping again to get the queue counts back on pending-sru.html === _LibertyZero is now known as LibertyZero [07:55] good morning === tkamppeter_ is now known as tkamppeter [08:31] WTH -- does https://wiki.ubuntu.com/ReleaseTeam/Meeting/Agenda work for anyone? [08:31] I get redirected to some http://www.releaseteam.com commercial page [08:34] pitti: broken wiki redirect [08:35] pitti: just asked in #is === smb` is now known as smb [09:01] pitti, dpm: I'm just looking at the merge of myspell-hr and the only change is to add a (or) dependency to language-support-writing-hr. it appears like this is the only of hte hypen packages doing this, can we drop that delta and sync the pkg? [09:02] morning [09:02] hey mvo, I'm not sure, I'll let pitti answer that one [09:08] mvo: confirmed [09:08] language-support-* are gone [09:10] pitti: thanks, I will request the sync [09:25] pitti: some discussion on the internal foundations list raised an interesting possibility: purge .pyc files from the live filesystem, and have ubiquity byte-compile them after copying the filesystem [09:25] pitti: .pyc files are about 12MB right now [09:25] we have to be careful to avoid making installed systems inconsistent between d-i and ubiquity, but if that can be avoided it does seem worth pursuing [09:27] cjwatson: indeed, that came up recently [09:27] cjwatson: but as the .pyc files are generated at package install time, and not shipped in the .debs, it should not be more inconsistent than a live vs. alternate install already is? [09:28] well, if you removed them from the live filesystem and didn't have ubiquity do the byte-compile step, nothing would ever generate them until the packages in question are upgraded [09:28] if ubiquity does that work, though, it's feasible [09:28] right, that's what I meant [09:29] I meant that it shouldn't matter much whether it was live-builder or ubiquity which triggers the pyc building [09:29] it costs a bit of extra time at installation; but 12MB isn't small change [09:29] even compressed that should be some 5 MB perhaps [09:29] I'm quoting the compressed size [09:30] it's more like 40MB uncompressed [09:30] ! [09:30] by the looks of man pycompile, we wouldn't even need to iterate over all packages, it seems it can build them all [09:30] $ sudo find /mnt -name \*.pyc | xargs cat | gzip -9c | wc -c [09:30] 11812952 [09:31] I'll check out exactly what dh_python2 etc. causes to happen, to make sure it matches [09:31] thanks! [09:32] we might want to trigger a fake python runtime update or something rather than calling pycompile directly [09:33] oh, that indeed seems easier [09:33] interesting that it doesn't seem to differ between pysupport, pycentral, and dh_python2 [09:34] oh, wait [09:34] those three have quite different .rtinstall files [09:34] it only seems to rebuild its own pycs, not for all python-* packages [09:34] for hook in /usr/share/python/runtime.d/*.rtinstall; do [09:34] [ -x $hook ] || continue [09:34] $hook rtinstall python2.7 "$2" "$version" [09:34] done [09:34] is basically what python does to byte-compile stuff [09:36] I'll check safety with doko [09:43] mvo: hi! I implemented some new features in gdebi, I plan to upload to experimental soon, then sync it in oneiric. Does it sound good to you? === shadeslayer_ is now known as shadeslayer [10:24] Why do random applications (browser, instant messenger etc) keep greying out and locking up? [10:27] this often happens if you do heavy I/O, such as copying big files, rsyncing cd images, etc. [10:28] if not, then the browser/IM is just busy (which is a bug, as it shoudln't stop responding to the UI) [10:28] pitti: The browser is doing nothing, but has locked [10:29] pitti: When the IM locked up, it was doing nothing [10:29] pitti: They just become unresponsive and lock [10:29] bugs [10:29] pitti: My mail client does the same, again whilst doing nothing [10:29] it's not "desired behaviour" of course [10:30] pitti: Must be a Ubuntu bug, can't be all these different applications [10:35] check syslog in case you have a disk device that's returning I/O errors [10:37] might be a hint from your system that you should probably stop doing nothing then :P [10:38] I get it when I have incredibly high i/o wait [10:40] ogra_: HA - jerk! [10:40] !coc | lag [10:40] lag: The Ubuntu Code of Conduct is a community etiquette document to which we ask all Ubuntu users to adhere, and can be found at http://www.ubuntu.com/community/conduct/ | For information on how to electronically sign the CoC, see https://help.ubuntu.com/community/SigningCodeofConduct [10:40] ogra_: My terminal is extremely busy (but it's not failing) [10:41] micahg: the problem with Linux is unfortunately that merely doing an rsync or copying 2 GB around already counts as "incredibly high" :( [10:41] micahg: I'd love to open it, but my browser is locked ;) [10:41] micahg: Why did you send that to me? [10:41] lag, see, that supports my theory ;) [10:42] lag, i find i get the same greying with no load, things grey out one by one, resolving when an OSD message finally spits out [10:42] lag: we don't tolerate insults here [10:42] micahg: ogra is a good friend of mine - he knows I was joking [10:43] somehow they cause a log jam which can even affect gnome-terminal ... which makes no sense, but its happened often enough that i've mannaged to killall the notifier to confirm its definatly that thats causing the blockage [10:43] apw: I am used to momentary greying out, but when these go, they are perm and the only way I can resolve is to kill the app [10:43] and its always for me an xchat OSD thats trying to display [10:43] apw: I haven't seen an OSD message for ages [10:44] apw: Let me try [10:44] how long is perm, i see minutes of grey during which a restart of notify-osd fixes it [10:44] jhunt, I am trying to stop a job on "stopped udev" [10:44] not that anyone believes me [10:44] but this never happens [10:44] psurbhi, udev runs all the time doesn't it? [10:44] so, I put post-stop script ; echo "in post stop"; end script [10:44] udev doesn't stop (except on shutdown) [10:44] and i cant see that either [10:44] cjwatson [10:44] exactly [10:45] apw: As long as I am patient enough to leave it - I need my browser and mail client, so I guess I've left it for 10-15 mins [10:45] but i want to do something similar in the initramfs [10:45] and somehow i cant see udev in the "stopped" case [10:45] it always reaches "stopping" and thats it [10:45] ah, I'll leave you alone then, not sure what that would be [10:45] i want to stop upstart-udev job on "stopped" udev [10:45] and then run the pivot command [10:46] right now, to achieve the same effect [10:46] i am stopping the upstart-udev-bridge [10:46] cjwatson: Just checked syslog, looks like I have problems! [10:46] on stopping udev [10:46] pitti: could you ack my debian-installer/lucid-proposed upload, please? [10:46] and then in the post-stop of upstart-udev-bridge, i execute kill all udev [10:46] lag: busted disk? [10:46] lag: past time to check those backups :) [10:47] cjwatson: Seemingly: https://pastebin.canonical.com/48644/ [10:47] jhunt ^^ [10:47] cjwatson: diff looks fine, accepted [10:47] cjwatson: I'm all backed up ;) [10:47] pitti: ta [10:47] i was wondering if anyone has seen that udev really stops on shutdown [10:47] atleast? [10:47] psurbhi: how do you know it only reaches stopping? [10:47] because i have put echos in the scripts [10:47] oh good, it's so rare that I say that and it's actually true [10:47] lag: doesn't seem related at all to IO errors; it just says that your keyboard has unknown keys [10:47] i.e post-stop script [10:47] and pre-stop script [10:48] psurbhi: where are the echoes going? [10:48] and also, the job that should execute on stopped [10:48] never gets executed [10:48] running upstart in --debug mode [10:48] never shows udev in the "stopped" state [10:48] lag: by any chance, does the blocking start when you press a particular key? [10:48] it says "stopping" udev [10:48] lag: yeah, those don't look like serious disk problems to me either [10:48] but i did not see anything more than that [10:48] lag: we had that problem with many Samsung laptops, they have a BIOS bug which needs to be worked around [10:49] some filesystem consistency problems, but not I/O [10:49] jhunt? [10:49] lag: try pressing Ctrl+Alt+F1, then Ctrl+Alt+F7 (or F8, whatever gets you back to the graphical desktop), and check whether it's gone [10:49] i did not get the question - where are the echoes going [10:49] sorry [10:49] lag: then find out whether pressing that magic Fn+something key triggers it [10:49] pitti: I was referring to the 1587 ext2 errors I have in there [10:49] pitti: Jun 17 10:48:14 system1 kernel: [11052.251178] EXT2-fs (sdb1): error: ext2_lookup: deleted inode referenced: 3268621 [10:50] wow [10:50] lag, is that an internal drive? cirtainly needs unmounting and checking properly [10:50] that doesnt look good [10:50] yeah, worth unmounting and doing a manual fsck [10:50] Not at all :( [10:50] Yes, it's mounted at /home/lag/ [10:50] * apw suggests crossing anything you have more than one of [10:51] * lag lols @ apw [10:51] lag, well we know there is nothing in there thats important :) [10:51] Right, BBS (if all goes well) [10:51] apw: You lot are rude! [10:51] ;) [10:51] lag, is my job [10:51] apw: Quite [10:52] Right, I'm off to fsck [10:52] heres hoping its your git trees, as most files in there are regenerrable :) [10:53] apw: /home/lag/projects are mounted separately ;) [10:54] jhunt, i can see the echoes in the pre-stop scripts for mountall.conf and udevd.conf [10:54] but i cant see the echoes in the post-stop script [10:55] psurbhi: I've just done a test and I have a simple job which successfully starts on "stopping udev". [10:55] jhunt - yes that works [10:55] but can you try starts on "stopped udev" [10:55] the stopping clause works [10:55] but the "stopped" doesnt for me [10:56] psurbhi: I think just aren't seeing the messages - rsyslog stops on the same condition as udev - try logging to the console/serial device [10:56] jhunt, the job does not start too [10:56] :-/ [10:56] can you please let me know if the job starts on "stopped udev" ? for you? [10:56] psurbhi, how can you tell if its not started if the logging output is not logged> [10:56] jhunt, yes, i am getting the messages on the serial console [10:57] apw, you could stop the logging on "stopped udev" [10:57] instead of "stopping udev" [10:57] works for stopped udev too...? [10:57] still too late though right as your job also starts then [10:57] jhunt, does your job work? [10:57] apw, then you can stop logging after stopping your test-job [10:57] psurbhi: it runs, so yes :) [10:57] ok! [10:58] jhunt, thanks [10:58] i will probably send you the initramfs [10:58] can you please let me know what you think is wrong in there? [10:58] psurbhi: can you show me your .conf file? [10:58] i had to log directly to /dev/.foo i think the only reliable way to get diagnostics, when i was playing with the vesafb stuff [10:58] yes, exactly [10:59] psurbhi: (from other channel) - yes, lets take this offline now... [10:59] yeah, I've always logged to /dev/.initramfs/ when trying to debug this kind of thing [10:59] (/run will reduce typing ...) [12:05] * ogra_ wonders what changed in upower recently ... i get battery discharge notifications every few mins since my last upgrade [12:13] ogra_: maybe your battery started dying? [12:13] ;D [12:14] its brand new [12:14] charged for the first time yesterday [12:16] bad purchase? :) [12:18] nah [12:18] it was fine before the upgrade [12:20] well, mine started showing zero recently, but it ever had a good battery. Like its totally drained. I thought that was a bug fixed to show it correctly ;) [12:20] *never === MacSlow is now known as MacSlow|lunch === DrKranz is now known as DktrKRanz === DktrKRanz is now known as DktrKranz [13:03] mvo: have you seen bug 774999? [13:03] Launchpad bug 774999 in update-manager (Ubuntu) "[i865G] Upgrade should warn user about lack of support for old 8xx intel hardware" [High,New] https://launchpad.net/bugs/774999 [13:05] I was hoping to upload a package to ubuntu today, but I tested in a pbuilder and found that it failed to install build deps due to bug 775546 [13:05] Launchpad bug 775546 in tex-common (Ubuntu) "/usr/sbin/update-language-def: line 779: printf: missing unicode digit for \u" [Undecided,Confirmed] https://launchpad.net/bugs/775546 [13:05] cjwatson: no, sorry, I have a look now [13:05] should I upload it anyways? or should I wait until the bug is fixed? [13:09] mvo: np, thanks [13:16] cnd: is that actually the reason it's failing? that bug suggests that it's cosmetic [13:17] cjwatson, yeah, I think you are right after I googled some more [13:17] let me pastebin the error message I see [13:18] I just assumed that was the reason since it was the first error/warning message I saw [13:19] cjwatson, here's what I believe is the relevant snippet: http://paste.ubuntu.com/628382/ [13:24] cnd: right, I was actually in the middle of a test live filesystem build to track that down, since it broke those too [13:24] cjwatson, ok [13:25] so should I hold off on uploading packages until it's fixed? [13:25] or should I upload now, and just retry builds as necessary? [13:25] it doesn't *hugely* matter; if you don't hold off, you'll have to retry [13:25] I wouldn't worry too much about it [13:25] if you have relevant upload privileges, retrying isn't too much of a hassle [13:26] ok, thanks! === psurbhi is now known as psurbhi_ [13:35] What's the best way to have a package build with gcc 4.4 on Lucid, 4.5 on maverick (whose default is 4.4), and 4.5 on natty? [13:37] a big ol' conditional in debian/rules [13:37] * Laney conditions directhex goooooooooood [13:38] directhex: so I take it we don't provide some sort of gcc-latest symlink? [13:39] YokoZar, nafaik, just gcc as a symlink to the default [13:40] Anyone else noticed archive builds failing for odd reasons atm? === psurbhi_ is now known as psurbhi [13:41] Daviey: see discussion with cnd above, perhaps [13:41] I'm just trying to pinpoint it with a livefs build here, since the logs are awkwardly unhelpful (failure distant from cause) [13:41] what's the deal with powerpc right now? buildds seem backed up [13:41] cjwatson: ok, thanks [13:42] it would probably help if dpkg rejected packages with syntactically invalid triggers files at unpack time rather than later [13:42] Daviey: however, can you point to a build log to make sure we're looking at the same thing? [13:42] https://launchpad.net/ubuntu/+source/cvs/2:1.12.13+real-5ubuntu1/+build/2575050 [13:42] cjwatson: that is the second build attempt [13:43] first one failed for "sh: gcc: not found" [13:43] sadly, i didn't save the log [13:43] "sh: gcc: not found" appears in lots of build logs due to something being run in the wrong chroot, and isn't normally fatal [13:43] I also saw one of slangasek's builds fail a few hours ago, but worked locally here - so hit rebuild and it worked. [13:44] (seeing this on i386 and amd64) [13:44] anyway, yeah, that's the same thing that I'm looking at [13:45] though perhaps a livefs build isn't the most efficient way to do it, but I might as well wait for it now ... [13:45] rocking [13:50] DktrKranz: gdebi> thats fine of course, many thanks for working on it, I noticed a bunch of fixes :) === MacSlow|lunch is now known as MacSlow [14:39] slangasek: hmm, looks like multiarch+triggers breaks world [14:39] $ cat chroot/var/lib/dpkg/triggers/Unincorp [14:39] aspell-autobuildhash dictionaries-common:all [14:48] aha, I think it's a non-updated trigdeferred.c [15:21] cjwatson, the gtk3 cpp bindings landed in debian unstable, should be on ubuntu on next new-source run then [15:21] cjwatson, it might make easier the work for the gparted guys, dunno what distro they run [15:25] jdstrand: can I get my armhf cross toolchain from NEW? [15:25] hrw: yeah, I am going to be working on it today [15:26] hrw: what are the packages? [15:26] jdstrand: cool, thanks [15:26] jdstrand: all with armhf in name: armhf-cross-toolchain-base, gcc-4.[456]-armhf-cross, gcc-defaults-armhf-cross [15:26] jdstrand: I will take care of build order once they will be out of NEW [15:28] seb128: thanks [15:33] win 39 [15:33] oops [15:53] cjwatson: doh, sorry for the mismerge; are you fixing/uploading, or do you need me to do something? [15:53] cjwatson, do you have a bug number for the bug we were hitting with the Unincorp trigger? [15:56] Daviey,cnd: new dpkg should fix it [15:56] cnd: no [15:56] I couldn't see a reported bug anywhere particularly obvious, so just fixed it [15:56] ok, knowing it's a dpkg bug is good enough :) [15:56] slangasek: done now. oddly, I couldn't see anything in your upload that should have broken it [15:57] huh [15:57] trigdeferred.c was out of date in the same way in the old version too [15:57] and the changes to trigcmd.c that tickled it were in the old version [15:58] but meh, I tested my change and it fixed the problem in my chroot [15:59] ah, an out-of-date generated file rather than a missing merge, doh [16:00] slangasek: merry hell to find [16:09] cjwatson: awesome, thanks [16:34] mdeslaur, you about? seems the fix for kernel 3.0 version issue in lm-sensors-3 (bug #797001) is only good for 3.0, i've re-fixed it up and pushed a branch to the bug ... testing is in the bug ... perhaps you could review [16:34] Launchpad bug 797001 in lm-sensors-3 (Ubuntu) "sensors-detect won't recognize 3.0 kernel" [Medium,In progress] https://launchpad.net/bugs/797001 [16:46] apw: hold on a sec [16:53] apw: ah, yes, that makes more sense [16:53] apw: I'll upload it in a sec [16:53] mdeslaur, thanks [17:05] barry: hi [17:05] apw: uploaded, thanks [17:05] mdeslaur, thank you [17:07] charlie-tca: oh, your goal is to not ship libgtk-3-0? [17:07] vs porting the whole of xfce on his own ? :) [17:07] charlie-tca: I thought you were using evince and other GNOME apps [17:09] not using gtk3 is not going to work [17:09] hmm ? [17:10] you think all of universe will be ported by release date ? [17:10] it's going to hard to find a gtk application to use [17:10] no, but I think if you want to get ride of gedit, eog, file-roller, evince, etc it's not a win [17:10] ah, yeah [17:11] well you can but you will corner yourself at shipping applications which don't have an active upstream [17:11] because those who have one will be ported [17:11] it's not really a winning option [17:11] but what do you do if your DE upstream doesnt move ? [17:11] you ship 2 gtk versions [17:12] cjwatson: howdy!! I was wondering if you managed to look into providing some kind of file with info in the Ubuntu mini.iso after discussing it at the UDS (with kirkland as well) [17:12] we do that for Ubuntu... [17:12] you can have a shell on gtk2 and application on gtk3 [17:12] that's basically what oneiric is [17:12] RoAkSoAx: grab that bug number, i think cjwatson upped it from won'tfix to triaged, as i recal [17:12] well until next week when unity-gtk3 lands [17:12] sure, but that eats CD space [17:12] RoAkSoAx: I closed that bug with an explanation of what I'd done [17:12] bug 765254 [17:12] Launchpad bug 765254 in debian-installer (Ubuntu Oneiric) "MiniCD needs a .disk/info structure" [Wishlist,Fix released] https://launchpad.net/bugs/765254 [17:13] ogra_, welcome to our world ;-) [17:13] heh [17:13] I guess you don't read your bug mail either? ;-) [17:13] ogra_, you just summarize oneiric :p [17:13] (me hugs his ARM world for not having these restrictions) [17:13] cjwatson: ah cool!! I somehow missed that :) Thanks!! [17:14] kirkland: Will now get the import with cobbler to automatically detect it [17:20] cjwatson: thanks [17:27] cjwatson, i am wondering if this was the message which was the dpkg bug: bug #798800 [17:27] Launchpad bug 798800 in libcanberra (Ubuntu) "package libcanberra-gtk-module 0.28-0ubuntu5 failed to install/upgrade: ErrorMessage: syntax error in triggers deferred file `/var/lib/dpkg/triggers/Unincorp' at character `:' midline" [Undecided,New] https://launchpad.net/bugs/798800 [17:29] pitti: hah, ok, I was just thinking you had been really good about getting them all done. OOPS! [17:30] SpamapS: well, I still did quite a few of them this mornign :) basically all that could be accepted, there were some which need further discussion or wait for the current proposed pacakge [17:30] slangasek, ping. [17:31] smoser: ohai [17:31] bug 798803 [17:31] Launchpad bug 798803 in atkmm1.6 (Ubuntu) "package libatkmm-1.6-1 2.22.5-1 failed to install/upgrade: ErrorMessage: syntax error in triggers deferred file `/var/lib/dpkg/triggers/Unincorp' at character `:' midline" [Medium,Confirmed] https://launchpad.net/bugs/798803 [17:31] i'm thinking its related to your dpkg upload/merge [17:31] smoser: already fixed in the preceding dpkg upload by cjwatson [17:32] well there ya go. i'm slow. [17:33] bug 798798 looks unrelated to libcap. First error comes from tex, and the rest all seems somehow unicode related. Not sure what to target the bug at. [17:33] Launchpad bug 798798 in libcap2 (Ubuntu) "package libcap2-bin 1:2.21-1 failed to install/upgrade: ErrorMessage: syntax error in triggers deferred file `/var/lib/dpkg/triggers/Unincorp' at character `:' midline" [Undecided,New] https://launchpad.net/bugs/798798 [17:33] ah [17:33] same as smoser's [17:33] i'll just mark it as a dup then [17:33] yes please [17:34] i just moved mine to dpkg, and marked fix released. [17:34] sorry for the breakage :/ [17:35] oh feh it was the same guy :) [17:36] @pilot in === udevbot changed the topic of #ubuntu-devel to: Oneiric Alpha 1 released | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: smoser [17:41] Daviey: do you know why my one-line edit of debian/control has broken builds of libapache2-mod-perl2? :) [17:41] apw: yes [17:41] heh [17:42] slangasek: developers not testing uploads? ... :) [17:42] cjwatson, is there a master bug to dup it to? [17:42] apw: not that I know of [17:42] Daviey: that's orthogonal! :) [17:42] slangasek: heh.. no - it was an interim issue.. NFI what caused it.. built locally here, so i fired rebuild.. and it worked [17:42] Daviey: I didn't test that it still built because I only edited a Recommends to a Suggests :-) ok [17:42]