[00:00] well it builds and pyside builds (with a couple new failures which might not necessarily be related) [00:01] when I finally get a raring install going I wanted to test some basic functionality [00:01] and hope upstream replies at some point ... [00:01] if not I guess upload and hope for the memleak is not too bad [00:01] and if it is replace it with the crash again ^^ [00:02] I'd say we should decide before feature freeze [00:03] * jtaylor offline [00:06] jtaylor: I'm able to test with raring if you want some assistance === sagaci is now known as jpickett === murthy is now known as murthy_ === tiagohillebrandt is now known as tiagoscd === almaisan-away is now known as al-maisan [07:29] good morning [07:31] 'morning dholbach :) [07:32] hey ESphynx [07:48] To everyone who speaks a language apart from English: please help out with translating: https://translations.launchpad.net/ubuntu-packaging-guide/ :-) [07:48] thanks [07:48] * dholbach will do a page of German translations now [07:49] wow... the Brazilians are getting close to the magic 70% mark: pt_BR.po (64%) :-) === zequence_ is now known as zequence === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === matttbe_ is now known as matttbe === barry` is now known as barry_ === barry` is now known as barry_ [17:45] wtf [17:46] su: System error in my chroot [17:46] what does that mean? it worked yesterday ._. [17:48] I need to test something, can someone build http://incoming.debian.org/sundials_2.5.0-3.dsc in raring and check the dpkg-shlibdeps output? [17:54] is week-old raring ok? (my local mirror is on the blink) [17:56] yes [17:58] weird unstable chroot works [17:59] talknig of which, mirror-maintainer-poking-time... [18:01] hm quantal works too, should be sufficient for the test [18:01] tumbleweed: you may abort if you like, thanks [18:04] jtaylor: it finished. all I saw was [18:04] dpkg-shlibdeps: warning: symbol N_VNewEmpty_Serial used by debian/libsundials-nvecserial0/usr/lib/libsundials_fnvecserial.so.0.0.2 found in none of the libraries [18:04] dpkg-shlibdeps: warning: symbol N_VCloneVectorArrayEmpty_Serial used by debian/libsundials-nvecserial0/usr/lib/libsundials_fnvecserial.so.0.0.2 found in none of the libraries [18:04] only those two? good [18:05] yeah === ogra_ is now known as ogra [19:43] Subject: problem [19:43] blad 502 getaway [19:44] … and that's all of the mail. I can just *assume* that it's meant to be related to packages.ubuntu.com, but who knows. Mails get weird these days. [19:44] This may be a silly question, but, as a MOTU, do I also have to be part of ubuntu-sponsors to sponsor stuff for people? [19:45] no [19:45] grats on motu btw [19:45] Cool, thanks. :) [19:46] Logan_: being a membor of ubuntu-sponsors allows you to unsubscribe the team from bugs [19:46] that's about it [19:46] Oh, I see. So it's more of an administrative thing. [19:46] yeah [19:47] Still waiting on my cloak (*cough* Pici *cough*) ;) [20:00] Is sync package not working for anyone else? [20:00] *syncpackage [20:00] what happens? [20:01] jtaylor: http://paste.ubuntu.com/5571510/ [20:01] It's weird because it was definitely working yesterday. [20:02] Timestamp appears to come from bad system clock [20:02] I checked my system time, and it is correct. [20:02] I even did a dpkg-reconfigure of tzdata. [20:03] …wait, no it's not. [20:03] I set it to EST, and it says "Local time is now: Wed Feb 27 11:43:13 EST 2013." [20:03] And it's 3:03 PM... [20:03] Logan_: by the way, when the sponsoree doesn't have a public email address in LP, you probably don't want to use the -s option [20:05] kk [20:05] and that bug wasn't a sync request [20:07] But, since it, by the nature of the new version of the software being in experimental, fixes the bug, shouldn't I mark that bug as fixed by the sync? [20:07] (Or are you just saying that I shouldn't include a sponsor?) [20:07] *sponsoree [20:07] yeah, the sponsoring [20:07] Ah, okay. [20:09] Another question (sorry) - when it says to wait for the sync to be successful before closing the bug, does that mean I should wait until the package has been built/accepted into the archive? [20:09] Or should I just wait until I get the e-mail saying the sync was acknowledged? [20:10] so, syncpackage sends a sync request to LP [20:11] LP doesn't actually do that immediately, but queues it [20:11] when it does get around to looking at it, it may reject the sync [20:11] so, either leave it open until you get an email saync it synced, or remember to go back and re-open syncs, if it gets rejected [20:11] Okay, awesome. [20:12] *sayng, *re-open bugs [20:12] I'm typing sync too much :P [20:12] * ScottK can't remember the last time he had one rejected, so has a strong opinion on which option is less work. [20:13] yeah, I put that prompt in before we really had a feel for how it would work [20:16] probably best to wait until you know the package has built successfully & been published [20:16] we should really just add bug-closing support to syncs in LP [20:17] although, that's probably hard [20:17] for normal uploads, the bugs get closed on copy into -release, right? [20:18] yeah [20:18] or -updates [20:20] so, if we wanted to attach bug closing to a sync, it'd have to be attached to the SPPH [20:24] got a step closer to installing raring [20:24] if I pull out the usb before starting the step that hangs it continues [20:24] but of course the test fails with io errors then [20:25] I probably have to try a cd ._. === murthy_ is now known as murthy === al-maisan is now known as almaisan-away [21:28] tumbleweed for DPL! [21:28] (re -vote) [21:28] * tumbleweed hides [21:30] * ajmitch seconds === murthy is now known as murthy_