[12:21] <bradb> SteveA: yeah, it's not really important enough to bug stub, IMHO
[03:13] <elmo> bradb: how do you delete attachments in malone?
[04:05] <jamesh> spiv: ping?
[04:05] <spiv> jamesh: pong
[04:05] <spiv> I'm just starting skype :)
[04:17] <bradb> elmo: attachments can't be deleted, unfortunately. bug 48771.
[04:17] <Ubugtu> Malone bug 48771 in malone "It should be possible to delete attachments" [Normal,Unconfirmed]  http://launchpad.net/bugs/48771
[05:27] <BenC> what might be the problem with an attachment in malone that isn't hyperlinked (meaning it shows it, but there's no way to get it)
[05:28] <BenC> I can privmsg the bug url to a dev, but not in channel (private bug)
[05:44] <bradb> BenC: are you saying that attachment title isn't hyperlinked in the bug attachments portlet on the RHS?
[05:44] <bradb> s/that/the/
[05:45] <bradb> BenC: you can privmsg me the url if you don't mind first sub'ing me to the bug report so i can view it
[06:23] <BenC> sorry, I had to leave
[06:30] <stub> bradb: The attachment isn't hyperlinked because elmo requested I remove the file.
[06:31] <stub> (If there is a bug here, it is that we need a (deleted) flag or something when rendering expired or deleted librarian files)
[07:13] <stub> Launchpad will be going down in 20 minutes for its regular code update. Estimated down time is 10 minutes.
[09:09] <SteveA> morning
[09:18] <SteveA> stub: hello
[09:55] <sivang> morning all
[10:03] <SteveA> hi sivan
[10:06] <stub> SteveA: Hi
[10:08] <carlos> stub: where you able to do the production update?
[10:08] <stub> carlos: Yes, as per the mailing list email and wiki page updates.
[10:09] <carlos> hmm, I didn't see the mail in the mailing list
[10:09] <carlos> stub: ok, thanks!
[10:09] <SteveA> carlos: subscribe to the production status wiki page
[10:09] <carlos> yeah, good idea...
[10:10] <carlos> BjornT: hi, around?
[10:11] <BjornT> hi carlos
[10:12] <carlos> BjornT: would you have time today to have a skype call about the desing of https://launchpad.net/products/rosetta/+bug/44214 ?
[10:13] <carlos> salgado told me that he's a bit busy but that would try to do it if you are not available
[10:14] <stub> BjornT: Did you send me a reminder email telling me about something important to do after rollout? If so, I've lost it ;)
[10:14] <stub> Ahh... found it.
[10:14] <SteveA> carlos: i updated the description of bug 44214 to say "bug 41653" rather than "#41653"
[10:14] <SteveA> the latter isn't auto-linked
[10:14] <SteveA> i wonder if it should be
[10:15] <carlos> SteveA: ok, thanks
[10:15] <stub> Should be - I tend to use that form ;)
[10:15] <sivang> hey stub , SteveA , carlos
[10:15] <SteveA> someone who cares should file a bug then :-)
[10:15] <carlos> sivang: hi!
[10:16] <SteveA> i think it is a bit permissive to autolink on #1234
[10:16] <SteveA> because that means  "number 1234"
[10:16] <stub> Oh... not just that. That would suck.
[10:16] <SteveA> do we number anything else?
[10:16] <BjornT> carlos: sure. maybe in an hour?
[10:16] <stub> Bug #1234
[10:16] <SteveA> that will work
[10:16] <carlos> BjornT: ok
[10:16] <carlos> 09:15 UTC ?
[10:16] <BjornT> yeah, that'll be fine
[10:17] <carlos> BjornT: ok, thanks
[10:31] <mdke> my mail software doesn't allow filtering on reply-to, only sender/subject/recipient. Is there another easy way I can filter bugmail?
[10:34] <SteveA> not really.  what is your mail software?
[10:42] <mdke> SteveA: I dunno, it is what is provided by the control panel on the hosting I have. I will learn procmail and see if I can use that
[11:03] <lifeless> spiv: does os.listdir use readdir ?
[11:10] <Kinnison> BjornT: Do products not have the same subscribe/unsubscribe as packages for bugs?
[11:12] <BjornT> Kinnison: not quite. a package can have any number of bug contacts, while a product can have only one.
[11:13] <Kinnison> Mmm, this kinda sucks
[11:13] <Kinnison> Was there a reason for not adding it to products too, or was it just never asked for?
[11:14] <BjornT> i'm not sure why it was done this way, you have to ask bradb about it.
[11:15] <Kinnison> Okay, thanks
[11:19] <siretart> is launchpad able to mirror 'knit' branches?
[11:20] <Kinnison> spiv: ^^^
[11:21] <carlos> BjornT: meeting time?
[11:21] <carlos> BjornT: if you need more time, feel free to delay it
[11:21] <Kinnison> carlos: So are we ready to open edgy as far as rosetta is concerned?
[11:22] <carlos> Kinnison: yeah, from the UI part, we are ready. The translations imports can be handled later
[11:22] <BjornT> carlos: i'm ready. what's your skype handle?
[11:22] <carlos> carlospm_1
[11:22] <Kinnison> carlos: right
[11:46] <Keybuk> how often are archives mirrored from sftp to http (bazaar.lp.net)
[11:56] <glatzor> Keybuk: once a day - I think
[12:07] <mdz> kiko: awake?
[12:13] <Kinnison> mdz: Judging by previous days I'd say we're not due kiko for between 1h and 2h
[12:14] <mdz> I wouldn't be surprised if he showed up early to prepare for opening edgy
[12:14] <Kinnison> That's a good point
[12:17] <SteveA> kiko mentioned 1200 UTC to me last night
[12:17] <Kinnison> So in 1h45m ?
[12:17] <SteveA> yes
[12:27] <tortho> FYI: Since we didn't find any good answers to it, and it has been discussed here before, From the norwegian translators: Bug #48799:
[02:00] <spiv> lifeless: yes, os.listdir on posix uses readdir
[02:00] <spiv> siretart, Kinnison: launchpad should be able to mirror knit branches as of the rollout earlier today.
[02:02] <Kinnison> Cool
[02:04] <Keybuk> Is ddaa at the London sprint?
[02:08] <lifeless> yes
[02:09] <Keybuk> can be be summoned briefly
[02:12] <spiv> Keybuk, ddaa: https://launchpad.net/products/launchpad-bazaar/+bug/48813
[02:18] <lifeless> Keybuk: summoned
[02:18] <cprov> stub: ping
[02:18] <stub> cprov: pong
[02:18] <lifeless> Keybuk: actually, hes rather focusde. can I realy ?
[02:18] <lifeless> s/realy/relay
[02:19] <cprov> stub: do we have a production DB backup for today (open edgy task) ?
[02:20] <stub> There is one running right now... and the last one was...
[02:20] <stub> Around 01:00 UTC
[02:20] <Keybuk> lifeless: would like a vague answer as to whether that bug is possible to fix quickly or not
[02:21] <lifeless> yes, I thought there was one already open. If spiv has time to do the relevant hack - we've discussed it already - then it should be fine. Spiv can you chat with SteveA about timing for this ?
[02:21] <cprov> stub: uhm the 01AM would be enough
[02:21] <lifeless> we should not poll all hosted branches everytime.
[02:21] <kiko> morning!
[02:22] <lifeless> we have machinery to set an arbitrary interval already.
[02:22] <kiko> hello cprov
[02:22] <kiko> hello stub
[02:22] <kiko> hello mdz
[02:22] <stub> kiko: 'ello
[02:22] <stub> Whee... more lightening
[02:23] <stub> If I disappear, the power has gone out ;)
[02:23] <kiko> how's it going out east?
[02:23] <cprov> kiko: hello
[02:23] <stub> Getting into the cool thunderstorm season. Great view from up here ;)
[02:24] <lifeless> ack after lunch
[02:29] <kiko> cprov, so are we waiting for a backup to push the button?
[02:32] <cprov> kiko: kind of, we have the 1AM one, but since stub has started another one, let's wait it to finish
[02:33] <cprov> kiko: I'm sorting archive backup with Kinnison
[02:33] <kiko> all right. coolio
[02:33] <stub> Its done
[02:36] <kiko> rockon
[02:36] <kiko> spiv, ping?
[02:36] <spiv> kiko: pong
[02:37] <spiv> lifeless: sure, I'll do that.
[02:38] <kiko> spiv!
[02:38] <spiv> kiko!
[02:38] <spiv> What's up? :)
[02:38] <kiko> spiv, on a scale from 1-10, how likely am I to get an email about this dotted prejoin business? :)
[02:39] <spiv> How long are you prepared to wait? ;)
[02:39] <spiv> I'll take a look now.
[02:42] <kiko> thanks!
[02:48] <kiko> spiv, I have improved the tests and they guarantee sanity! yay!
[03:27] <bradb> Kinnison: In retrospect, it may have been a mistake to allow only one bug contact for product/distro, because it would seem to make it very hard for non-core-team users to follow bug activity, in many cases.
[03:28] <bradb> Kinnison: what product do you want to be a bug contact for? i'm curious to see its configuration.
[03:30] <spiv> kiko: sent
[03:33] <kiko> spiv, is it good news or bad news?
[03:34] <spiv> kiko: good, I hope.  I have a suggestion about _prejoinOne that I hope you like.
[03:37] <kiko> spiv, I have factored cache.clear() and the assert == 0s into a function, which avoids some of the repetition and makes clear that yes the repetition was accidental :-/
[03:38] <kiko> spiv, your suggestion is excellent but I will need to butcher the entire method to do it, and you want me to stop straying from upstream. should I do it anyway, or should I limit its impact?
[03:39] <spiv> You could limit it to just dealing with the prejoin bits.
[03:39] <spiv> I think I'd lean towards limiting it, but I'm not sure.
[03:40] <spiv> I guess it depends on how much cleaner it would be if you butchered the entire method.
[03:40] <spiv> If it was sufficiently beautiful, perhaps rewriting changes made in upstream to use our newer code wouldn't be so painful.
[03:41] <kiko> spiv, I'll consider that carefully then
[03:41] <spiv> Or perhaps it would be horribly difficult... but wasn't his function originally fairly simple before we added this prejoin business?
[03:41] <spiv> s/his/this/
[03:41] <kiko> I can't remember
[03:41] <kiko> spiv, however, your suggestion is somewhat limited by the fact that it doesn't take into account the fact that current_class and current_table need to mutate
[03:41] <spiv> Like 15 lines or something that suddenly turned into 100.
[03:42] <kiko> but perhaps I can supply them to addPrejoin()
[03:42] <spiv> kiko: They'd be state on the queryBuilder object.
[03:42] <kiko> hmmm
[03:42] <kiko> I think that'd be bad
[03:42] <kiko> well, unless we /did/ limit its use
[03:42] <spiv> Hmm, perhaps.
[03:42] <kiko> because you always want to reset back to the original class
[03:42] <spiv> Ah, right.
[03:42] <kiko> but I think we can manage well enough in the loop
[03:42] <spiv> Yeah, when I wrote that sketch I was just thinking of the limited problem.
[03:43] <kiko> so I'll take that into consideration. when working on SO I always find it hard to balance between rewriting the goddamned thing and doing what I need to do
[03:43] <spiv> It was a bit of a "this proof is left as an exercise for the reader" kind of review ;)
[03:43] <spiv> Yeah.
[03:44] <kiko> heh
[03:44] <kiko> okay I'll improve it
[03:44] <spiv> I'd lean towards the path of spending less effort.
[03:44] <kiko> but apparently testing it on LP has shown a bug in it! I am fascinated
[03:45] <spiv> I'm really happy to see that prejoin code somewhat factored out of that function, btw.  It was getting crazy...
[03:46] <kiko> I just discovered I need to normalize the prejoins
[03:46] <kiko> because if you do
[03:46] <kiko>             prejoins=["potemplate", "language", "latestsubmission",
[03:46] <kiko>                       "potemplate.sourcepackagename",
[03:46] <kiko>                       "latestsubmission.person"] ,
[03:47] <kiko> then it fucks up by joining twice on latestsubmission and potemplate
[03:47] <spiv> Whee!
[03:47] <kiko> hmmm
[03:47] <kiko> that idea about the QueryBuilder
[03:48] <kiko> it is pure genius :)
[03:48] <kiko> hmmmm
[03:48] <spiv> What about ["foo.owner", "bar.owner"] , i.e. two different dotted prejoins onto Person, did you have a test for that already?
[03:49] <kiko> no, haven't tested that either
[03:49] <kiko> should work as long as the renaming works though
[03:49] <spiv> Oh, crazy idea: use sqlobject's sqlbuilder ;)
[03:49] <spiv> Yeah, I agree it *should*... can't hurt to be sure we didn't miss something :)
[03:49] <Kinnison> bradb: launchpad-publisher
[03:53] <kiko> oh-oh
[03:53] <kiko> spiv, https://chinstrap.ubuntu.com/~dsilvers/paste/fileTekw4O.html
[03:55] <spiv> I think my eyes are bleeding.
[03:56] <kiko> stub, do you know how we should reformat https://chinstrap.ubuntu.com/~dsilvers/paste/fileTekw4O.html to actually work?
[03:56] <kiko> spiv, I think I hit a speedbump
[03:57] <kiko> it appears that we can't mix inner and outer joins?
[04:02] <spiv> kiko: maybe we need to use parens?
[04:02] <kiko> spiv, can you explain further? you mean subqueries?
[04:03] <cprov> salgado: ping
[04:03] <spiv> "A JOIN clause combines two FROM items. Use parentheses if necessary to determine the order of nesting. In the absence of parentheses, JOINs nest left-to-right."
[04:04] <salgado> cprov, pong
[04:04] <cprov> salgado: do you have any idea about how mirror stuff will get affected by open edgy ?
[04:04] <lifeless> Keybuk: I am here now
[04:05] <salgado> cprov, it's designed to Just Work
[04:05] <salgado> cprov, but we'll see if that happens in practice after edgy opens
[04:07] <cprov> salgado: perfect, dude, thank you. keep your eyes on it and let me know if the procedure to open edgy can do something to help you in this land
[04:08] <stub> salgado: How often should it be running? I think it is currently scheduled to run daily.
[04:08] <salgado> cprov, thanks for asking, but I think all we can do is wait until the mirrors start mirroring edgy
[04:09] <cprov> salgado: right, let's watch it
[04:10] <salgado> stub, I think daily should be okay for now. maybe later we can make it run more often
[04:13] <mdz> morning
[04:14] <cprov> mdz: morning, publishing edgy
[04:16] <cprov> mdz: when can you come around to __sign___ the archive results ?
[04:17] <mdz> cprov: sign?
[04:17] <cprov> mdz: check
[04:18] <mdz> cprov: I'm here now
[04:19] <Kinnison> Publisher is almost finished
[04:19] <cprov> mdz: then check archive in drecher, if you can
[04:20] <mdz> cprov: did you make a hardlink backup I can compare against?
[04:20] <Kinnison> Yes I did
[04:21] <Kinnison> in .../ubuntu-archive-backup
[04:22] <bradb> Kinnison: Interesting (re: launchpad-publisher) team. Is it an option for you to set up a team for this product? Then add mdz, you, etc.? Then you could all get email about it (no need for a mailing list.)
[04:22] <Kinnison> A team would do, but then individuals couldn't unsub from bugs
[04:23] <bradb> Kinnison: Indeed, though that bug remains even if more than one person can be a product bug contact.
[04:23] <Kinnison> bradb: I thought the bug contact could unsubscribe if they wanted
[04:23] <Kinnison> bradb: I want the same sort of behaviour as package subscriptions
[04:24] <Kinnison> mdz: It's ready for checking
[04:24] <Kinnison> s'just removing dists.old
[04:24] <mdz> cprov: edgy is missing the Task extraoverrides
[04:24] <bradb> Kinnison: You can't unsubscribe from package bugs anymore either. Package contact subscriptions are now looked up at bugmail delivery time, not "explicitly" created at filebug time.
[04:24] <Kinnison> mdz: Right, cron.germinate probably hasn't built them yet
[04:24] <mdz> cprov: and main/*installer*
[04:25] <Kinnison> mdz: yep, those need copying in, I knew that and I'm not sure how we should automate it in the future
[04:25] <cprov> mdz: uhm ..
[04:25] <bradb> Kinnison: maybe ping me later to discuss this further when you're less busy?
[04:25] <Kinnison> bradb: sure, that'd be cool
[04:26] <bradb> thanks
[04:26] <Kinnison> mdz: Germinate running
[04:27] <Kamion> Kinnison: you need to change cron.germinate to say suite=edgy
[04:27] <Kamion> at the moment it's working on dapper
[04:27] <Kinnison> Kamion: poo
[04:27] <Kinnison> Kamion: thanks
[04:29] <Kamion> Contents needs to be copied in too
[04:29] <mdz> the dist-upgrader stuff is missing too, though perhaps that's not a bug
[04:29] <Kamion> unless that'll get rebuilt automaticaly
[04:29] <Kamion> +k
[04:29] <Kamion> damn, +l. I'll stop now.
[04:31] <mdz> Kamion: I think it's uploaded pre-built
[04:32] <Kamion> I meant Contents
[04:32] <Kinnison> Contents will be copied and/or generated soon
[04:41] <Kinnison> mdz: Right, I'm ready to re-run the publisher to see if the germinate did the right thing
[04:41] <Kinnison> running
[04:42] <Kamion> oh, er, wonder what it'll have done with xubuntu seeds
[04:42] <kiko> please mind the gap
[04:43] <Kamion> xubuntu seeds will be b0rken
[04:43] <Kamion> sorry about that, I can fix it, give me a minute
[04:44] <Kinnison> Kamion: it's already running, but it won't reach the override generation phase for a few minutes
[04:44] <Kinnison> Kamion: not that cron.germinate would run in time
[04:45] <Kamion> I can't pull from jani until the SM gets round to pulling the seeds, but that's ok, I just branched xubuntu-dapper to xubuntu-edgy
[04:46] <Kamion> ... however, it seems to have worked anyway, I guess it reused the old dapper files when germinate failed
[04:46] <Kamion> so we're actually ok
[04:47] <cprov> salgado: don't we use a field validator for email addresses yet ?
[04:47] <cprov> salgado: instead of simple TextLine. Do you think it's worth to have ?
[04:48] <cprov> salgado: i know that we have high-level validation for that, but right no I need to map an address that isn't stored in EmailAddress table
[04:50] <salgado> cprov, the interface for IEmailAddress.email is bogus. IIRC, all forms that expect an email address do the validation manually
[04:51] <salgado> so, yes, a custom field for email addresses would probably be a good idea, but we'd also need to switch some pages to use GeneralFormView
[04:51] <cprov> salgado: uhm, what do you think about writing a EmailAddress field validator ? would you also use it in FOAF ?
[04:53] <salgado> yes, it'd be useful, definitely
[04:53] <kiko> spiv, I am completely and absolutely fucked.
[04:53] <kiko> I will need to produce a query ordering thingifier
[04:53] <salgado> cprov, but I don't see why do you want it
[04:53] <cprov> salgado: yes, maybe fixing the callsites will be overkill, but at least we can reuse it for new forms, which would use GFV anyway, thanks for the oppinion, I will write it
[04:54] <cprov> salgado: DistroRelease.changeslist tweak via distrorelease/+admin
[04:55] <salgado> cprov, but aren't you going to need to create a special schema in order to have an emailaddress field on that page?
[04:55] <cprov> salgado: don't know if we can model it using EmailAddress, it doesn't need hig level validation
[04:55] <stub> kiko: Sounds like you have been belting at SQLObject with a hammer to keep the rusty old thing running and it finally exploded.
[04:55] <salgado> cprov, I don't see what you mean
[04:56] <BjornT> anyone up for a trivial review?
[04:56] <cprov> salgado: I mean validation cycle compared with what we have for personal email addresses
[04:57] <kiko> stub, I appreciate your support
[04:57] <kiko> a query ordering thingamajingifier
[04:58] <stub> heh... I just noticed on that my web host provider has switched to Ubuntu ;)
[04:58] <cprov> salgado: don't know if we have plans to model maillistings in LP and how we would do it. the point is we can't simply check "user@url"
[04:59] <stub> cprov, salgado: http://www.stuartbishop.net/Software/EmailAddress/index.html will do the validation heavy lifting
[04:59] <stub> (I think(
[04:59] <stub> )
[05:00] <salgado> cprov, what other checks do we need to do?
[05:00] <cprov> stub: you rock ! do you think we can create a field validator based on it ?
[05:01] <cprov> salgado: that's the point, right now, we can't do anything to certify it's a real maillisting and people are listening it
[05:02] <stub> cprov: It might be strict enough. If not, it would be a start.
[05:02] <cprov> salgado: even checking user@host we mail be sending email to an non-existent maillisting
[05:03] <salgado> cprov, but checking that a given email is for an existing mailing list involves at least sending one email and receiving a response, doesn't it?
[05:03] <stub> We can't confirm that the address is deliverable though without sending an email and catching bounces, and we can't confirm that anyone actually monitors that mailbox and it is not a spam honeypot or anything
[05:03] <salgado> this sounds like you need a LoginToken-style workflow
[05:04] <salgado> like the one we do to add new email addresses for people/teams
[05:04] <cprov> however, I'll continue with the field validator, it's an admin page, people will take care, later we can thing in a login-token extension
[05:04] <salgado> what is your field validator going to do, exactly?
[05:04] <cprov> salgado: yes, we may think about this at somepoint
[05:05] <cprov> salgado: just check if the email address sintaxe is correct
[05:06] <salgado> well, AFAIK, the rules for inserting an email address in the database are pretty strict. I'm not sure if the fact that it's inserted using an admin interface is enough for us to alleviate these rules
[05:06] <cprov> salgado: stub's code looks sane for doing this
[05:06] <cprov> salgado: you're right, it's not, but anyway it's not in EA table yet ;)
[05:07] <salgado> eh? that email address will go in a separate table?
[05:07] <cprov> salgado: and current EA is only refered by Person table
[05:08] <matsubara> cprov: fwiw, we've been using validators/email.py for simple syntax checking
[05:08] <cprov> salgado: yes, I told you the text field, IDistroRelease.changeslist
[05:09] <hub> how do I unsubscribe from a bug I am notified because of dupliactes...
[05:09] <salgado> cprov, that doesn't mean much. I thought it'd be a reference to the EmailAddress table
[05:09] <hub> I get spammed several times a day and this is driving me nuts
[05:09] <salgado> but it looks like it's a text column?
[05:10] <cprov> salgado: yes, it still being a text field, which I pointed as an unreliable wy to solve the problem ;)
[05:11] <bradb> hub: You can't, atm, unfortunately. Just curious, why are you interested in being subscribed to the duplicate, but not to the dupe target?
[05:11] <salgado> cprov, well, if that's the case then all you need to do is to specify a constraint on IDistroRelease.changeslist's definition
[05:11] <cprov> salgado: uhm .. we already have that validator, I forgot about it, it's used in logintoken
[05:12] <hub> bradb: I don't even know what the duplicate is, and I think I got subscribed to the duplicate because I'm upstream on the package where the bug orignally is reported in
[05:12] <carlos> hub: hmm, you would need to wait for bradb to answer you, but I just tried unsubscribing me from the duplicate bug and seems like I'm still subscribed, so seems like the fact that you cannot subscribe it's a bug
[05:12] <ajmitch> bradb: a bug may be marked duplicate later on
[05:12] <cprov> salgado: Text(..,constraint=valid_email,...) should work
[05:12] <carlos> oh, bradb already answered ;-)
[05:12] <hub> bradb:  that bug https://launchpad.net/distros/ubuntu/+source/libgnomeprint/+bug/34112
[05:12] <Ubugtu> Malone bug 34112 in libgnomeprint "gnome programs don't respect ~/.cups/lpoptions" [Unknown,Unknown]
[05:12] <hub> bradb: I'm in "also notified"
[05:12] <Kinnison> mdz: Cleaning up the old dists, Do you want to take a quick look?
[05:12] <hub> and can't remove myself
[05:13] <carlos> bradb: I guess we should be removed from it when we remove our subscription to the duplicated bug
[05:13] <hub> no
[05:13] <hub> we should be able to get unotified on that bug too
[05:13] <hub> this bug as something like 20 dupes
[05:14] <hub> and I don't know which one is mine
[05:14] <bradb> indeed, there are too many to look through
[05:14] <carlos> hub: it makes no sense to be unsubscribed from the main bug and stay subscribed to the duplicate one. The duplicate one should not get any activity
[05:14] <Kinnison> mdz: Once you're happy we can turn things on again :-)
[05:14] <carlos> hub: oh, I see your point
[05:14] <hub> carlos: it makes no sense to not not be able to unsubscribe from anyuthing
[05:15] <carlos> hub: sorry, I misunderstood you
[05:15] <hub> carlos: I call that SPAM
[05:15] <hub> carlos: in fact it is easier for me to hunt down a LP developer than to hunt down the duplicate on that one
[05:15] <hub> bradb: fear, I'm only 2 hours away
[05:15] <hub> :-)
[05:15] <hub> bradb: I know where you live :-)
[05:16] <bradb> heh
[05:16] <bradb> hub: I can see why this is causing you, and others, grief. I'll need some time to think about how to address it.
[05:16] <carlos> hub: yeah, I didn't get your point, I thought you wanted to stay subscribed to the duplicated one
[05:16] <hub> ok
[05:16] <hub> bradb: bonus point: provide a direct link in the message "unsubscribe from this"
[05:17] <hub> bradb: with a way that it does not get caught by spamassassin
[05:17] <hub> bradb: just for the hacking value :-)
[05:17] <hub> then I'll owe you beer
[05:17] <bradb> yeah, that's a nice idea
[05:17] <Kamion> Kinnison: xubuntu-desktop tasks did end up wrong in the end
[05:17] <bradb> can you file a bug about being able to unsub from the "also notified" list?
[05:18] <bradb> hub ^^
[05:18] <hub> okay then
[05:18] <bradb> thanks
[05:18] <hub> and then I'll get spammed again ;-)
[05:18] <Kamion> Kinnison: I have a feeling they've ended up as copies of corresponding edubuntu-* tasks
[05:18] <Kamion> I'm pretty sure that'll get cleaned up automatically next cron.germinate/cron.daily runs though
[05:18] <Kinnison> cool
[05:18] <Kamion> I'd understand if mdz wanted to make sure though
[05:19] <Kamion> the rest of diff -ru dists/{dapper,edgy} looks ok to me
[05:20] <hub> what distribution or whatever shoudl I use?
[05:20] <bradb> hub: https://launchpad.net/products/malone/+filebug
[05:20] <Kamion> hub: /products/malone
[05:20] <hub> there is no launchpad / malone
[05:20] <hub> great
[05:20] <mdz> Kinnison: looking
[05:21] <Kinnison> mdz: thanks
[05:21] <mdz> Kamion: btw, ~kiko/bin/compare-archives is the latest version of the somewhat smarter comparison tool
[05:22] <hub> https://launchpad.net/products/malone/+bug/48862
[05:22] <Ubugtu> Malone bug 48862 in malone "Can not unsubscribe from a bug when "Also Notified"" [Untriaged,Unconfirmed]
[05:22] <mdz> Kinnison: all of the old Release.gpg have been re-signed (hoary, etc.)
[05:22] <hub> no offense guys, but UI-wise, I give a good D
[05:22] <hub> to not give a F
[05:23] <bradb> hub: No offense taken, and bug reports welcome.
[05:23] <kiko> spiv, stub: SUCCESS!
[05:23] <kiko> YES!
[05:23] <hub> bradb: well, I have a few weeks of filing
[05:24] <hub> then
[05:24] <Kinnison> mdz: very odd
[05:25] <hub> bradb: and I'm currenly busy with *paid* work
[05:25] <bradb> hub: I understand fully. Just noting that it's much more likely that the specific issues you encounter will be fixed if you or somebody else reports them.
[05:26] <hub> I know that
[05:26] <hub> that's why I filed to bugs, but at the same time I found 4 more to file
[05:26] <Kamion> mdz: kewl
[05:26] <hub> so I don't really want an exponential progression of bugs to file
[05:27] <bradb> Maybe one day soon Launchpad can have an Edgy style development process. :)
[05:27] <Kinnison> mdz: Is it causing an issue?
[05:28] <mdz> Kinnison: I haven't checked the signatures, but have no reason to believe so
[05:28] <Kamion> somewhat smarter but a hell of a lot slower. urk.
[05:30] <mdz> Kamion: longer runtime, less time reviewing the output :-)
[05:31] <kiko> hah
[05:31] <kiko> HAH!
[05:32] <hub> bradb: maybe
[05:32] <kiko> https://chinstrap.ubuntu.com/~dsilvers/paste/fileuUCO5b.html
[05:32] <kiko> I KILL YOU
[05:32] <hub> bradb: since I don't know python, I'll be useless
[05:32] <kiko> stub, how horrible is that query going to be?
[05:32] <kiko> https://chinstrap.ubuntu.com/~dsilvers/paste/fileuUCO5b.html
[05:33] <Kinnison> mdz: D'you want us to turn on the pipeline then?
[05:33] <mdz> Kinnison: is there anything in the queue?
[05:33] <mdz> would be nice to run a test upload through it
[05:33] <Kamion> the queue is staying disabled until glibc/gcc land anyway, I'm tol
[05:33] <Kamion> told
[05:33] <Kamion> we could run something non-C through
[05:34] <Kinnison> We can run a source through
[05:34] <Kinnison> there're no chroots
[05:34] <Kinnison> Until infinity supplies us with chroots we're not turning binaries on
[05:34] <Kinnison> (his request)
[05:35] <mdz> Kinnison: how about a trivial upload of a package which is modified in ubuntu anyway?
[05:35] <mdz> er, hmm
[05:36] <mdz> if there are no chroots, we can neither test nor do useful work
[05:36] <mdz> why delay that?
[05:36] <Kamion> Keybuk/jbailey want to start building the world with the new toolchain
[05:37] <Kinnison> The delay is, afaict, jbailey owes infinity a new glibc
[05:37] <mdz> Kinnison: but we'll need to build that
[05:37] <Keybuk> Kamion: waiting on a new libc from jbailey to test on my i386
[05:37] <Keybuk> and then we need new gcc and gcj from doko
[05:38] <Keybuk> and then we need infinity to be awake to make chroots and feed the buildds some hamsters
[05:38] <mdz> Kinnison: I don't see the point in rolling this out without creating chroots...what will happen with uploads? source will be published and just never built?
[05:38] <Kinnison> indeed
[05:38] <Kinnison> once the chroots turn up the builds will happen
[05:38] <Keybuk> mdz: we've turned off the upload processor
[05:39] <mdz> Keybuk: but we want to turn that back on
[05:39] <Keybuk> no, we don't
[05:39] <Keybuk> otherwise somebody will start uploading crap to edgy
[05:39] <Keybuk> and then we'll have to have all of it rebuilt again once the new toolchain is in
[05:39] <mdz> Keybuk: no builds will happen
[05:40] <mdz> Kinnison: so all you're asking is whether to re-enable pushing to the mirrors?
[05:40] <Keybuk> true, but this way the buildds don't need to be on manual or anything
[05:40] <mdz> Kinnison: if so, sure
[05:40] <Kamion> infinity will have to be very careful about sucking from the firehose if the whole queue comes back on
[05:40] <stub> kiko: You appear to be joining POTemplate about three times with exactly the same criteria.
[05:41] <stub> kiko: If we are going to start to join more than 6 tables I'm going to need to tweak some PostgreSQL config to keep the query optimizer working well.
[05:41] <Keybuk> scary gnome people were talking about starting the war-uploader
[05:41] <Kinnison> Right, so I'll turn cron.daily back on, but not the buildd sequencer or the upload processor
[05:42] <Kinnison> Okay cron.daily and cron.germinate are reenabled
[05:42] <Keybuk> we can re-enable the security upload processor, right?
[05:43] <Kinnison> Umm, *ponder*
[05:43] <Kinnison> Should be able to, yes
[05:43] <kiko> stub, well, the POTemplate duplication is a bug
[05:44] <Keybuk> ok
[05:47] <Kinnison> Keybuk: security queue is alive
[06:03] <Kinnison> stub: any chance that the statistician will run soon?
[06:04] <kiko> stub, https://chinstrap.ubuntu.com/~dsilvers/paste/file62ZUoL.html
[06:04] <kiko> stub, look better now?
[06:05] <Kinnison> stub: otherwise LP claims edgy is empty
[06:08] <salgado> stub, I just commented on https://launchpad.net/products/shipit/+bug/5812/ explaining what I discussed with SteveA yesterday. can you check if that's okay?
[06:13] <kiko> stub's in high demand
[06:14] <Keybuk> stub: does my bum look big in this?
[06:15] <stub> Kinnison: It will kick in tomorrow I think. You need it run earlier?
[06:16] <Kinnison> stub: ideally, currently LP thinks edgy is empty
[06:16] <Kinnison> stub: which makes for bad looking /distros/ubuntu/edgy
[06:16] <stub> kiko: There is still a spurious POTemplate join in there.
[06:18] <stub> FROM POTemplate, POFile JOIN POTemplate AS _prejoin0 ON _prejoin0.id = POFile.potemplate ... WHERE ... AND POfile.potemplate = POTemplate.id
[06:19] <carlos> stub: do you think this restriction makes sense?: 'posubmission_can_be_selected' UNIQUE, btree (pomsgset, pluralform, id)
[06:19] <carlos> I think it makes no sense at all, the id is going to be unique anyway...
[06:20] <carlos> sorry, forget what I said
[06:20] <stub> Kinnison: Running now
[06:20] <Kinnison> stub: thanks
[06:24] <Keybuk> I'd guess it means taht the PO submission can be selected
[06:48] <stub> carlos: it is required so another table can refer to those columns using a foreign key
[06:49] <carlos> stub: Oh, I see
[07:12] <Keybuk> where did the stuff in dapper-updates go?
[07:12] <Keybuk> is that copied into edgy?
[07:12] <Keybuk> or is edgy == dapper ?
[07:13] <Kinnison> The decision made in conjunction with some distro team members was that when initialising a new release, you only copy the release pocket, not -updates or -security
[07:13] <Keybuk> right
[07:14] <Keybuk> what's proposed, btw?
[07:14] <Keybuk> that's a new pocket to me
[07:14] <Kinnison> proposed-updates
[07:14] <Kinnison> the idea being you could put stuff in there, and then if they are okay they could migrate to -updates
[07:18] <fabbione> Kinnison:
[07:18] <Keybuk> so it's not related to UNAPPROVED ?
[07:18] <fabbione> dists/edgy/main/daily-installer-amd64/20051026ubuntu13.0.20060124/
[07:18] <fabbione> is it expected?
[07:18] <Kinnison> yes, we copied daily-installer and installer in from dapper
[07:19] <Kinnison> Keybuk: no, UNAPPROVED is a queue state, not a pocket
[07:19] <Keybuk> right
[07:19] <Keybuk> I'm curious as to the process
[07:19] <Keybuk> it is intended to be like backports, and a free-for-all update zone?
[07:20] <Kinnison> It's a sabdfl idea
[07:20] <Kinnison> ask him
[07:20] <kiko> well, there must be some rationale behind it you understand Kinnison?
[07:22] <Kinnison> The sab explained it to me a while ago and I must confess I don't remember the rationale other than as a staging area because -updates was in the apt config and -proposed-updates wouldn't be
[07:22] <kiko> I guess that's reasonable enough
[07:22] <Kinnison> He'll be able to better explain it
[07:26] <fabbione> Kinnison: out of curiosity, why?
[07:26] <fabbione> (the copy of the installer)
[07:27] <fabbione> (that also triggered a pulse in the dapper/ dirs)
[07:29] <sabdfl> staging area is a good description
[07:30] <sabdfl> so, a sysadmin has three sane options
[07:30] <sabdfl>  - enable -security only (very stable, only security updates)
[07:30] <sabdfl>  - leave it as -security and -updates (should be stable, some new bits, and security)
[07:30] <sabdfl>  - enable all of -security, -updates,  -proposed-updates (get new up and coming fixes, perhaps for internal testing)
[07:31] <salgado> BjornT, around?
[07:35] <BjornT> hi salgado
[07:36] <salgado> BjornT, have you seen https://chinstrap.ubuntu.com/~dsilvers/paste/fileSELAtI.html before?
[07:36] <salgado> I'm getting that when running a new-style pagetest, and I think it's because the page I'm trying to print the contents of contains non-ascii characters
[07:39] <BjornT> salgado: yeah, i think so to. i guess you should either not print the contents, or convert the contents to ascii, replacing non-ascii characters with something.
[07:41] <salgado> well, in this specific case the problem is that the content is not what the test expects, and then zope is printing it for me
[07:41] <salgado> so, I don't see how I could do what you suggest
[07:42] <BjornT> ah, right
[07:42] <Kinnison> fabbione: we copied the dirs to edgy because it seemed like the right thing to do
[07:44] <BjornT> salgado: well, you could use '"foo" in browser.contents', or you could use something like BeautifulSoup to extract the parts your interested in.
[07:45] <SteveA> doing a match like:  "<h1> whatever </h1>" in fuzzy_htmlmatch(browser.contents)   would be cool
[07:45] <salgado> hmmm. is it impossible to fix this in zope?
[07:45] <SteveA> and having this as a standard thing in pagetests
[07:46] <BjornT> salgado: it's in python, not in zope
[07:46] <salgado> BjornT, because when it fails, I'd like to have browser.contents printed so that I can see what went wrong
[07:47] <salgado> well, I was thinking of catching that exception and then smashing the non-ascii characters or something like that
[07:48] <salgado> (doing that in zope/testing/doctest.py, I mean)
[07:51] <SteveA> salgado: encode using the error handling strategy that replace unencodable chars as ?
[07:54] <BjornT> salgado: changing zope/testing/doctest.py should probably be avoided, since that's basically a copy the doctest module in python. i think encoding the content yourself is the best option for now
[08:04] <salgado> so, that would be "browser.contents.encode('ascii', 'replace')"?
[08:06] <BjornT> yeah
[08:06] <salgado> shouldn't browser.contents be a unicode object?
[08:06] <salgado> (Pdb) type(browser.contents)
[08:06] <salgado> <type 'str'>
[08:07] <SteveA> i guess not.  a bytestream is what gets served up
[08:07] <BjornT> ah, then that won't work. not sure what it's meant to be.
[08:07] <SteveA> there shoud/could be a method getUnicodeContents()
[08:08] <SteveA> that would use the encoding header of the page
[08:08] <salgado> exactly. that's why the contents.encode('ascii') won't work
[08:08] <SteveA> if there is one
[08:08] <SteveA> but meanwhile, you can write a function to do that
[08:08] <SteveA> and re-encode it as ascii
[08:09] <BjornT> according to the interface (IBrowser) it should be a unicode string, though.
[08:09] <salgado> aha!
[08:21] <salgado> so, we'll have to do this for every page that (with our sampledata) can contain non-ascii characters?
[08:40] <carlos> hmm
[08:40] <carlos> SteveA, kiko: Would be possible to get bzr updated in asuka? (I still don't know if we should ask those things directly to admins or ask you first)
[08:41] <fabbione> Kinnison: imho it's kind of pointless :) dapper installer can't install edgy :) you might as well wait for the first edgy installer upload ;)
[08:41] <carlos> we have there 0.7pre
[08:41] <carlos> so it's useless with the knits branches
[08:42] <kiko> carlos, I think so, yes -- I'd write to stub,lifeless CC: launchpad and if so I'd request rt@admins
[08:43] <carlos> kiko: ok, thanks
[09:03] <SteveA> just go to RT
[09:03] <SteveA> stub has asked about this before
[09:03] <SteveA> there may even be an RT issue on it
[09:05] <SteveA> nope, not in rt
[09:05] <SteveA> carlos: please send in an RT request, r=me
[09:06] <carlos> SteveA: ok
[09:19] <Keybuk> can somebody confirm that the sftp->http bazaar.lp.net mirror happened today?
[09:24] <sivang> hmm, any reason why I wouldn't have .bzr dir after installing bzr from dapper?
[09:25] <Keybuk> why would you expect a .bzr dir?
[09:26] <sivang> Well, it alaways had been before I reinstalled dapper and reinstalled bzr ;-)
[09:26] <sivang> and I would create .bazaar manually, as per the RocketFuelSetup document
[09:27] <sivang> (before, that is)
[09:39] <Keybuk> .bzr is created by "bzr init"
[09:39] <Keybuk> ie. it marks a repository
[09:41] <sivang> ah , right damn my memory. it's created per branch.
[09:41] <sivang> Keybuk: sorry
[09:47] <Kamion> can somebody just kill off daily-installer-* from edgy please?
[09:48] <Kamion> we have no mechanism to update it since the switch to soyuz, and it's better missing than outdated
[09:48] <Kamion> in fact, I really wouldn't object if it got purged from dapper too
[09:48] <Kamion> I know it's released, but I can guarantee that nobody can actually be using it successfully
[09:49] <Kamion> (it has an incompatible kernel; if you try to boot it it will get to the point where it tries to suck more of itself from the archive and then fall over in a heap)
[09:49] <Kamion> fabbione: no, having the dapper installer there is good, daily-installer is pointless though
[09:49] <Kamion> the dapper installer certainly can install edgy; you might have to preseed stuff but that's about it
[10:01] <sivang> do we have packages for rocketfuel-get and -refesh scripts?
[10:03] <sivang> I have a very small fix to the rocketfuel-refresh script, but I see the RFS wiki page he become immutable (good thinkg to protect the PQM key fingerprint for verification) but if we have packages for that, I could introduct the fix there.
[10:04] <sivang> basically, the change is from 'XPULL=".bzr/parent"' to 'XPULL=".bzr/branch/parent"'
[10:04] <sivang> if someone could change that on the wiki page, that would be great.
[10:54] <cprov> kiko: do you have time for a quick review/talk on fixes for edgy release ? https://chinstrap.ubuntu.com/~dsilvers/paste/fileTK38zd.html
[10:55] <kiko> cprov, for you? always


[06:32] <duflu> Whee, a phone with Mir 0.18
[08:06] <dholbach> good morning
[08:36]  * donkey_12 I Love Monday!
[09:25] <JamesTait> Good morning all; happy Monday, happy New Year, and happy World Braille Day! 😃
[09:25] <lotuspsychje> ;:..:::;...::::
[10:34] <popey> Is it still the case that a device (e.g. OPO) (ping mariogrip) needs to be on Android 4.x before we flash Ubuntu on it?
[10:34] <popey> or can I have an OPO with 5.1 on it and flash ubuntu directly as per https://wiki.ubports.com/w/OnePlus_One
[11:37] <mariogrip> popey: android version should not effect Ubuntu at all, so you can flash it directly with 5.1
[11:37] <popey> oh hey :)
[11:38] <popey> I get "2016/01/04 10:57:19 Expecting the device to be in the bootloader... waiting"
[11:38] <popey> it just sits there, when I have the phone in TWRP
[11:39] <mariogrip> What does "fastboot devices" say?
[11:39] <popey> nothing mariogrip
[11:40] <mariogrip> Sudo?
[11:40] <popey> same
[11:40] <mariogrip> Is your device in fastboot mode? (adb reboot bootloader)
[11:40] <popey> no, recovery
[11:41] <mariogrip> Oh, you need to be in fastboot mode
[11:41] <popey> ok, rebooted into fastboot
[11:41] <popey> and now it shows up in fastboot devices
[11:41] <mariogrip> Then it should work
[11:41] <popey> well, it does with sudo
[11:41] <popey> just says "waiting..."
[11:42] <mariogrip> Did you start the script again?
[11:42] <popey> yes
[11:42] <popey> interestingly if I try ubuntu-device-flash with sudo, it reports the device name
[11:42] <popey> ahh, i see the issue (maybe)
[11:43] <popey> the -- in my terminal are broken because I copy pasted from your page
[11:43] <popey>  — vs --
[11:43] <popey> yeah, it's flashing now!
[11:43] <mariogrip> Oh
[11:43] <mariogrip> Cool :)
[11:43] <popey> thanks dude :)
[11:43] <popey> 2016/01/04 11:43:21 Flashing version 8 from ubuntu-touch/stable channel and server http://system-image.ubports.com to device bacon
[11:43] <popey> :D
[11:43] <popey> \o/ bacon
[11:44] <mariogrip> :D
[12:02] <popey> mariogrip, "recovery image not found, cannot continue with bootstrap" :(
[12:53] <mariogrip> popey: sorry for late answer, but I'm not home atm
[12:54] <mariogrip> But, try without bootstrap from twrp
[13:12] <popey> mariogrip, okay, thanks for the help! :D
[13:15] <popey> mariogrip, it fails in the same way unfortunately. "recovery image not found, cannot continue with bootstrap"
[13:16] <popey> gets further if I don't use --bootstrap
[13:20] <popey> mariogrip, seems to do the flash but then reboots back into twrp but doesn't install
[13:31] <mariogrip> Ah, you need to flash boot.img
[13:33] <popey> mariogrip, I purchased this OPO second-hand from someone else, and I am going through the instructions as if I'm completely new to this :)
[13:33] <popey> (which I am)
[13:34] <popey> mariogrip, so it sounds like the docs need updating
[14:22] <beuno> jdstrand_, happy new years!
[14:23] <beuno> found binaries for architecture 'all': share/locale/de/LC_MESSAGES/checkers.costa.mo, share/locale/it/LC_MESSAGES/checkers.costa.mo lint_control_architecture_valid_contents
[14:23] <beuno> those errors, are they valid for .mo's?
[14:23] <beuno> I see those more and more often
[14:36] <n1cky> is a lack of 4.2.2 sources still a preventing factor in porting devices launched with 5.0+?
[14:36] <n1cky> I've got some free time and am looking to work on a Nexus 6 port
[14:36] <n1cky> s/4.2.2/4.4.2/
[14:54] <dobey> n1cky: the nexus6 is armv8, so unless you can run an armv7 build on it, 64-bit hardware is going to require a lot more work than just building on the android 5.x kernel source
[14:55] <dobey> beuno: that seems like a bug to me.
[15:00] <n1cky> dobey: are you sure about that? My googling says that it's a Snapdragon 805, i don't think it is armv8
[15:00] <n1cky> I'm talking about Shamu not the 6P.
[15:02] <dobey> oh, ok. i thought the 6 was v8 as well
[15:02] <dobey> i guess it should be plausible then, as long as you can get the necessary features enabled in the kernel
[15:03] <dobey> there has been some work to enable ubuntu based on android 5.x, but i don't know how far along that work is
[15:11] <n1cky> cool, thank you
[16:05] <mariogrip> popey: Yeah, I'm working on a new wiki. (Sorry for not answer as so fast, i have been away all day)
[16:06] <mariogrip> popey: did you get it working btw?
[16:06] <popey> mariogrip, no problem :) - appreciate the help
[16:06] <popey> mariogrip, no, I didn't know where to get boot.img from
[16:08] <mariogrip> https://cdimage.ubports.com/ubuntu-touch/bacon/device/device_bacon.tar.xz
[16:09] <mariogrip> then it should be in the "partition" folder inside the tar ball
[16:10] <mariogrip> btw, I'm cooking up a new version based on 5.1
[16:11] <mariogrip> where mostly everything seem to work correctly
[16:12] <mariogrip> popey: ^
[16:12]  * popey looks
[16:32] <popey> mariogrip, not sure what I'm doing wrong. i used fastboot to flash boot.img, and when I try and ubuntu-device-flash it pushes all the files then reboots into twrp. Am I supposed to do something else to make it actually do the flashing?
[17:01] <mariogrip> can you check if system.img is created (in recovery in /data folder)
[17:02] <mariogrip> and sorry for the delay, i had to wrap my head around some ikea furnitures...
[17:02] <mariogrip> popey: ^
[17:02] <popey> heh
[17:03] <popey> there is no /data/recovery folder
[17:03] <mariogrip> no, look for the /data/system.img
[17:03] <popey> oh, you mean /data/system.img when in recovery mode?
[17:03] <popey> no, not there
[17:04] <mariogrip> any output when you flash?
[17:04] <popey> mariogrip, http://paste.ubuntu.com/14401350/
[17:05] <mariogrip> oh, wait twrp does not use the recovery mode adb....
[17:05] <mariogrip> okey then, reboot to bootloader
[17:05] <popey> ok
[17:05] <popey> ok, done
[17:05] <mariogrip> find the recovery.img from the tarball you downloaded
[17:06] <mariogrip> then sudo fastboot boot recovery.img
[17:06] <mariogrip> then start the flash script
[17:06] <popey> did you mean "sudo fastboot recovery recovery.img"?
[17:07] <popey> or did you really mean "sudo fastboot boot recovery.img" ?
[17:07] <mariogrip> yeah, boot
[17:07] <popey> ok
[17:07] <mariogrip> so you can keep twrp
[17:07] <popey> gotcha
[17:08] <popey> should it have done something after the sudo fastboot boot recovery.img
[17:08] <popey> it did the "downloading boot.img" thing
[17:08] <mariogrip> no, it just says on the opo logo
[17:08] <mariogrip> try adb devices
[17:08] <popey> ok
[17:08] <popey> i see it in recovery
[17:08] <mariogrip> then start the script
[17:09] <popey> so now... sudo ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=bacon --bootstrap
[17:09] <mariogrip> no bootstarp
[17:09] <popey> ok
[17:11] <popey> mariogrip, ok. it's rebooted into twrp again
[17:11] <mariogrip> oh? log?
[17:11] <popey> same http://paste.ubuntu.com/14401431/
[17:12] <mariogrip> okey, okey, don't stop the script and do the same thing with fastboot boot recovery
[17:13] <popey> eh?
[17:14] <popey> I don't know what you mean by "don't stop the script"
[17:14] <mariogrip> wait, do you use the "ubp" twrp?
[17:15] <mariogrip> ubports twrp version
[17:15] <popey> uh, dunno. I'm just following your guide
[17:15] <popey> I have done nothing but what the steps you've said since I got this device
[17:16] <mariogrip> I see, i really need to update to the new wiki asap, sorry for the confusion
[17:16] <popey> np
[17:17] <popey> I just expected to run ubuntu-device-flash and it work :)
[17:17] <mariogrip> yeah, it should do that
[17:19] <mariogrip> okey, let's try again, reboot to bootloader can copy this ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=bacon --bootstrap
[17:19] <davmor2> Saviq: ahayzen points out in bug 1528668 that the launcher is requiring a double tap to close it now it still is with the silo installed so I guess it isn't related to that do you need a new bug for it?
[17:19] <ubot5`> bug 1528668 in qtubuntu (Ubuntu) "[regression] Qt.application.active not working correctly" [Critical,In progress] https://launchpad.net/bugs/1528668
[17:20] <popey> mariogrip, ok, doing that
[17:21] <popey> mariogrip, "recovery image not found, cannot continue with bootstrap"
[17:23] <mariogrip> try to add --recovery-image=[recovery.img that you downloaded]
[17:23] <popey> ok
[17:23] <mariogrip> and, I need to test this for my self, that should not happen
[17:26] <popey> mariogrip, just rebooted into recovery again (twrp v<IP_ADDRESS>)
[17:26] <mariogrip> log?
[17:27] <popey> http://paste.ubuntu.com/14401561/
[17:27] <mariogrip> oh, you forgot --bootstrap
[17:27] <popey> oh
[17:27] <popey> sorry
[17:28] <mariogrip> np
[17:30] <popey> mariogrip, just sits there after:-
[17:30] <popey> 2016/01/04 17:28:11 Device is |bacon|
[17:30] <popey> 2016/01/04 17:28:11 Flashing version 8 from ubuntu-touch/stable channel and server http://system-image.ubports.com to device bacon
[17:31] <mariogrip> try to restart it, and are you in bootloader?
[17:33] <popey> mariogrip, yeah, restarting it...
[17:33] <popey> hah, now it's moving :)
[17:34] <mariogrip> :)
[17:36] <popey> mariogrip, rebooted and now at 1+ screen.
[17:36] <popey> will get a cup of tea and leave it alone ;)
[17:36] <mariogrip> :D
[17:37] <mariogrip> it now flashes, this takes a little while
[17:39] <popey> thanks for your help mariogrip! I really appreciate it!
[17:39] <mariogrip> np, im glad to help :D
[17:41] <mariogrip> to check the progress, you can use adb shell "cat /data/.last_update"
[17:41] <mariogrip> if it says true, just do adb reboot
[17:43] <Saviq> davmor2, ahayzen, doubt it's the same issue, can you please file a bug?
[17:44] <popey> nice
[17:44] <davmor2> ahayzen: do you want to do the honours?
[17:46] <mariogrip> popey: still processing?
[17:47] <mariogrip> oh, it was if the file exist then it's done.
[17:48] <mariogrip> the recovery sometimes dosent want to reboot after it's done.
[17:51] <ahayzen> davmor2, yeah no problem, Saviq which project should it be against ?
[17:52] <davmor2> ahayzen: unity8 for now Saviq can blame someone else after :D
[17:52] <ahayzen> hehe ok :-)
[17:53] <Saviq> davmor2, ahayzen, unlikely to blame someone else I'm afraid :P
[17:55] <ahayzen> davmor2, Saviq, bug 1530940
[17:55] <ubot5`> bug 1530940 in unity8 (Ubuntu) "Dismissing the launcher in the dimmed/shadow portion requires two taps" [Undecided,New] https://launchpad.net/bugs/1530940
[17:55] <Saviq> ahayzen, tx
[17:55] <ahayzen> no problem :-)
[17:58] <davmor2> ahayzen: thanks dude :)
[18:03] <kaie> hello. Is there a key-press combination to reboot a phone that is in "fastboot mode"?
[18:03] <greyback_> kaie: usually long press on power key will end that
[18:04] <kaie> my aquaris e5 was off, and I must have accidentally pressed keys that caused it to boot into fastboot mode. now it's stuck and doesn't react to anything.
[18:04] <kaie> Hmm. Yeah, I have tried long power. Let me try again
[18:05] <kaie> 20 seconds and it's still on
[18:06] <kaie> I'm on the "release candidate" channel. I installed a new OTA update today. I didn't pay attention if it ever came up again since installed. But I think it was fine, and I think I had turned it off, because I wanted to remove a sim card, but then got distracted.
[18:08] <kaie> ok, connected cable, ran "fastboot reboot", and it did.
[18:08] <kaie> Now I'm just worried this could happen me again while I'm not close to a computer.
[18:08] <greyback_> kaie: heh good, I was 90% through writing that suggestion
[18:21] <popey> mariogrip, still going and that file exists, so time to reboot?
[18:21] <mariogrip> jup
[18:21]  * popey crosses fingers
[18:23] <popey> mariogrip, sitting at the 1+ screen
[18:24] <mariogrip> adb devices
[18:24] <popey> not there
[18:26] <mariogrip> oh, did you flash boot.img?
[18:26] <mariogrip> oh, wait you used bootstrap
[18:28] <mariogrip> popey: give me a minute so i can test this, i dunno why it's not working as expected...
[18:28] <popey> sure
[18:39] <mariogrip> popey: OH! dangit,  i upgraded the system-server the other day and it does not make device part images.......!
[18:39] <popey> heh, oops
[18:40] <mariogrip> I'm so sorry about that! my head sometimes cannot keep up with everything xP
[18:43] <popey> heh
[18:59] <mariogrip> popey: now you can try XP
[19:00] <popey> sure!
[19:00] <mariogrip> now you can remove --recovery
[19:00] <mariogrip> --recovery-image=
[19:01] <popey> hmm
[19:02] <popey> power + volup ?
[19:02] <mariogrip> for bootloader yes
[19:03] <popey> not working
[19:03] <popey> wont power on
[19:03] <popey> oh, now it does
[19:03] <popey> silly phone
[19:04] <mariogrip> xP
[19:05] <mariogrip> should flash v9 now
[19:05] <mariogrip> sudo ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=bacon --bootstrap
[19:09] <popey> yup, 9 installing
[19:09] <mariogrip> :)
[19:10] <mariogrip> and if it doesn't reboot after booting into recovery for flash, just reboot it after 10 mins
[19:11] <mariogrip> that should be plenty
[19:16] <popey> okay, i think it's done
[19:17] <popey> \o/ ubuntu logo
[19:17] <popey> welcome screen!
[19:17] <popey> Nice one mariogrip
[19:19] <popey> Ubuntu is nice and quick on this!
[19:22] <mariogrip> Yeeey :D \o/
[19:36] <mterry> morphis, hello!  I'm told you are the guy to talk to when making aosp changes?  I've got a gerrit checkout of android_bootable_recovery, but are there instructions for building?  I'm not used to Android.mk
[19:39] <morphis> mterry: I am one, yes :-)
[19:41] <morphis> mterry: its a matter of:
[19:41] <morphis> repo init ...
[19:41] <morphis> repo sync -j<n>
[19:41] <morphis> . build/envsetup.sh
[19:41] <morphis> lunch <select machine>
[19:41] <morphis> make -j4
[19:41] <morphis> should build you everything
[19:41] <mterry> morphis, I need everything?
[19:41] <morphis> there is a short cut to build just the recovery
[19:42] <morphis> ondra knows it
[19:42] <mterry> morphis, I tried the repo init route, but couldn't figure out how to pass the port to use.  I tried "repo init --repo-url=mterry@code-review.phablet.ubuntu.com:29418" but it timed out on port 22 anyway
[19:42] <mterry> So I went to just straight git
[19:42] <morphis> yeah
[19:43] <morphis> using simply https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git here
[19:43] <morphis> and pushing against ssh://morphis@code-review.phablet.ubuntu.com:29418/aosp/platform/manifest
[19:43] <morphis> mterry: https://wiki.cyanogenmod.org/w/Doc:_Building_Basics is also helpful
[19:45] <mterry> OK, repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git worked.
[19:45] <mterry> I'll add that to the wiki...
[19:48] <mterry> morphis, thanks!  This seems to be working.  I'll poke you again when I have something to review  :)  -- I'm working on a redesign of the flashing-new-image recovery animation (from design team specs)
[19:51] <morphis> mterry: great!
[19:59] <mterry> morphis, hrm.  repo sync -j4 fails due to missing git repos
[20:01] <popey> mariogrip, do you know why I have to run "sudo fastboot devices" and not just "fastboot devices"?
[20:01] <popey> mariogrip, on your pc do you have an entry in an adb.ini file somewhere for this device?
[20:02] <mariogrip> due to udev
[20:02] <popey> ah yeah
[20:02]  * popey will add a udev rule
[20:02] <popey> ta
[20:02] <genii> popey: This seems to be the same with *buntu fastboot no matter what the device attached
[20:27] <popey> hmm
[20:27] <popey> added to 70-android.rules, but it still needs sudo for fastboot, which is annoying
[20:31] <taiebot> Hi All Happy new year. Has anyone reported that on nexus 4 app cannot go fullscreen anymore on rc-proposed? It is a regression or a new feature?
[20:32] <dobey> taiebot: eh?
[20:33] <mariogrip> https://github.com/M0Rf30/android-udev-rules/blob/master/51-android.rules popey
[20:33] <taiebot> dobey app like camera used to go fullscreen (without the top bar) and now the top bar is always there. my webapp https://uappexplorer.com/app/runeaudio.taiebot65 is now always displaying the top bar
[20:34] <dobey> taiebot: ah, probably a regression in mir perhaps
[20:35] <taiebot> dobey: Ok i thought there was a design decision to not allow apps to go fullscreen anymore
[20:35] <dobey> i don't know, but i don't think so
[20:36] <dobey> there have been updates to mir and qt recently though, so maybe those caused something to break?
[20:36] <taiebot> dobey ok i create a bug report
[20:36] <dobey> yes, please do
[20:40] <taiebot> dobey: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530977
[20:40] <ubot5`> Launchpad bug 1530977 in Canonical System Image "Regression apps cannot go fullscreen" [Undecided,New]
[20:41] <dobey> kgunn: ^^ do you know if maybe mir or qtubuntu is the cause of that?
[20:42] <kgunn> dobey: not completely sure...but i think i did hear something like this morning in a unity meeting
[20:42] <kgunn> dobey: lemme ping in #ubuntu-unity
[20:43] <dobey> sure, thanks
[20:45] <kgunn> dobey: and fix is in midst of migrating
[20:45] <kgunn> aiui
[20:45] <dobey> cool
[20:46] <dobey> "already fixed and moving through the system" is my favorite type of bug reports
[21:14] <Guest66299> hi, Im trying to install ubuntu touch on a brand new nexus 7 and keep getting directory access issues. the only item I can find referencing this suggests the newest nexus devices have a different mmc card. Is there any documented solution to this?
[21:16] <popey> Guest66299, which model of nexus 7?
[21:16] <popey> 2012 or 2013?
[21:16] <Guest66299> sorry, 2013, just bought it
[21:17] <Guest66299> manufactured july 2015
[21:19] <popey> not seen that issue, sorry
[21:20] <Guest66299> Flashing the device fails with the message that the image didn't copy to /cache/recovery/ because it "Is a directory"
[21:20] <Guest66299> just found the specific error
[21:23] <Guest66299> http://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to details the only info I can find
[21:24] <Guest66299> does anyone have any idea on an alternate solution?
[21:25] <dobey> Guest66299: if you can flash android 4.4 to the device, i would suggest doing that, booting to the android welcome screen, then rebooting to the bootloader and trying ubuntu-device-flash again. if android 4.4 is not instalalble on the latest nexus 7 devices, then it may require waiting until we have builds that are based on android 5.x
[21:25] <Guest66299> OK cool, I shall try that thanks
[21:26] <Guest66299> signing out now, if it works I shall post my result tomorrow.
[22:10] <taiebot> Hi all can someone else on rc-proposed confirm this bug. https://bugs.launchpad.net/unav/+bug/1530222 Thanks
[22:10] <ubot5`> Launchpad bug 1530222 in uNav "Taping on the back arrow in the main screen leads to a blank screen" [Undecided,Confirmed]
[23:02] <a10b87a10feea58e> Guest66299, dobey, popey: https://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to
[23:22] <Guest57618> Hi, spoke about an hour ago on problems installing Ubuntu on new Nexus 7, july 2015 manufacture. There appears to be an issue with the latest devices using a new MMC card which renders the stock install useless on these machines. Suggestion was to downghrade Android to 4.4. Tried this but it did not work, no version 4.x would install. re-installed version 5.1 image which worked fine. Back to starting point now, new Nexus 7 w


[05:47] <fishcooker> is there any apps that save buffer copy paste list ?
[07:38] <Usman> Hi
[07:38] <Usman> I am running DSpace on VMware 11
[07:39] <Usman> I have a question, how to take backup and restore the database of dspace
[07:42] <Usman> plz share the link
[07:43] <Usman> Hi Jirido
[07:44] <Usman> could you help me?
[07:44] <Usman> I want to take backup and restore the dspace
[07:45] <Usman> running on vmware
[07:46] <jirido> Hi.. well I would like to but Im not so good at stuff but more of a low end user .. sorry
[07:57] <Usman> HI
[07:58] <krytarik> Usman: That doesn't strike me as particularly Lubuntu-related.
[07:58] <Usman> No Prob
[08:56] <Guest7041> Hi all. I am having trouble booting into lubuntu 17.10 from a USB
[09:01] <Guest7041> I have a nVidia gpu i heard that causes some problems in Linux
[09:02] <hateball> Guest7041: what issues are you having? black screen?
[09:03] <hateball> Guest7041: if you have an nvidia card that is not supported by nouveau you can boot with nomodeset to get past install and be able to install nvidia blob
[09:03] <hateball> !nomodeset
[09:05] <Guest7041> I'll send photos you tell me what is happening.
[09:05] <Guest7041> https://usercontent.irccloud-cdn.com/file/51EVqn0y/IMG_20171211_100313.jpg
[09:05] <Guest7041> Stuck here for the moment
[09:06] <hateball> that doesnt look too great
[09:06] <hateball> thats a rather ancient BIOS, perhaps it chokes on that
[09:06] <hateball> you can try the various boot options by pressing F6, try noacpi etc
[09:08] <Guest7041> Ok let me reboot
[09:09] <Guest7041> Wait you mean noapic? Because acpi is already off
[09:10] <hateball> Guest7041: yeah you could try all of those options I guess, but also try adding nomodeset manually if it is gpu driver related
[09:13] <Guest7041> Actually i think i know what to do now brb
[09:15] <Guest7041> Okay i added nouveau.modeset=0 grub_gfxmode=1024x768x16
[09:17] <Guest7041> Yay a blue screen lubuntu 17.10
[09:17] <Guest7041> https://usercontent.irccloud-cdn.com/file/CrCKbjMH/irccloudcapture1470590103.jpg
[09:18] <Guest7041> Wtf
[09:20] <Guest7041> It failed to satrt login service smh
[09:22] <hateball> Guest7041: is your RAM ok?
[09:22] <Guest7041> Yea i got 2gb and a 32bit version of lubuntu
[09:23] <hateball> I mean OK as in error free
[09:23] <Guest7041> https://usercontent.irccloud-cdn.com/file/Gse446hd/irccloudcapture-322438636.jpg
[09:23] <Guest7041> I got stuck here
[09:24] <Guest7041> I don't see any mention of ram here
[09:26] <hateball> Guest7041: well the livemedia copies the squashfs into ram
[09:27] <hateball> Guest7041: but it could also have problems reading from the CD, I guess
[09:28] <Guest7041> Well it is an old USB drive should i go to a cd?
[09:28] <hateball> Guest7041: oh I just assumed CD. No, media itself doesnt matter, so long as it's not broken
[09:29] <hateball> Guest7041: you should be able to verify the media from the boot menu as well
[09:29] <hateball> as well as run a memtest to check your RAM
[09:29] <Guest7041> Okay let me verify then
[09:30] <Guest7041> This is gonna take a while I'll be back when it's done
[13:56] <defenderoffreedo> hey so my previous hard drive had windows but it is in a bit of trouble, might die any day
[13:56] <defenderoffreedo> so i got a new hard disk
[13:56] <defenderoffreedo> and intend to install both lubuntu and windows on it
[13:56] <defenderoffreedo> so is there a concern if i install lubuntu first?
[13:57] <defenderoffreedo> or will installing windows later mess up the boot loader?
[13:58] <hateball> yep
[13:58] <hateball> !fixgrub | defenderoffreedo
[13:58] <defenderoffreedo> so better to install windows first?
[14:00] <aka555> Hi to all
[14:00] <aka555> When I try to install encrypted I get this error: aunsafe swap space has been detected
[14:01] <aka555> How is possible to fix it?
[14:02] <defenderoffreedo> also, while installing ubuntu, what is the recommended thing to do for swap space?
[14:03] <defenderoffreedo> the hard disk is 500GB and RAM is 4GB on the machine
[14:03] <defenderoffreedo> i am thinking of about 440GB for lubuntu and the rest for windows
[14:08] <defenderoffreedo> ??
[14:08] <aka555> Is a common problem or only for me?
[14:10] <aka555> When I try to install encrypted I get this error: an unsafe swap space has been detected
[14:10] <aka555> In the installation...the hard disk is empty
[14:11] <aka555> I only choose encrypted installation
[14:11] <aka555> And I have 8gb of RAM don't need a swap space
[14:12] <hateball> defenderoffreedo: if you intend to hibernate you need swap at least as large as your RAM
[14:13] <hateball> defenderoffreedo: no reason to go beyond that imo
[14:14] <defenderoffreedo> i'd prefer to be able to hibernate if need be
[14:14] <aka555> So I can not do the encrypted installation?
[14:14] <defenderoffreedo> how would i create the swap space and how do i select a partition to be the swap partition?
[14:15] <hateball> aka555: you probably can, but as you can see not many people are around to answer your question right now
[14:15] <hateball> and I dont know how
[14:15] <hateball> defenderoffreedo: iirc the installer offers to do so, otherwise choose manual partitioning
[14:17] <aka555> Ok thanks anyway
[17:17] <laptop212321321> is manjaro faster than lubuntu
[17:17] <wxl> let's go with no?
[17:18] <laptop212321321> why
[17:19] <wxl> because this channel is about lubuntu, not manjaro?
[17:20] <laptop212321321> what is the best version of lubuntu to install, for example I want to search for stuff when I click the button that allows a search to occur for lbuntu 16.04
[17:20] <laptop212321321> and also is 17.10 faster than 16/04
[17:21] <laptop212321321> on an older machine
[17:21] <laptop212321321> core2duo 2.1 ghz
[17:21] <laptop212321321> 2 gb ram
[17:21] <laptop212321321> I have lubuntu on another hd
[17:21] <laptop212321321> notice they are about the same
[17:21] <laptop212321321> but manjaro lite has more on it
[17:44] <laptop212321321> help
[19:05] <beanbag-> so when is the actual drop dead release for 32 bit
[19:05] <beanbag-> since you guys managed to put out one more
 @beanbag-, Not soon.
[19:20] <beanbag-> OH GOOD :)
[19:20] <beanbag-> I figured since ubuntu was cutting off 32 bit it would make your lives harder
[19:20] <wxl> well, there will be a time in the future when it goes away
[19:21] <wxl> and honestly i don't think it will be that far away
[19:21] <beanbag-> oh well, time marches on


[08:35] <jfi> Any way to ask to extend today quota for recipe build? I am trying to debug errors and have exceeded the quota:(
[08:45] <czajkowski> jfi: ask a question on lp or ping wgrant nicely
[08:45] <cjwatson> There's no way, it's hardcoded
[08:46] <jfi> cjwatson, ha ok, so will wait tomorrow to fix my issues, thx for the info
[13:02] <dobey> jfi: don't use recipe builds to debug problems. do the debugging locally with bzr dailydeb, sbuild, etc…
[13:11] <jfi> dobey, the issue is about the build of the recipe itself
[13:11] <dobey> jfi: bzr dailydeb is for building recipes
[13:13] <jfi> Oo did not know that I can do that part locally (https://help.launchpad.net/Packaging/SourceBuilds/BzrBuilder)
[13:13] <jfi> sorry for that
[13:54] <patdk-wk> buildlogs missing?
[13:54] <patdk-wk> https://launchpad.net/~patrickdk/+archive/general-lucid/+build/5901781
[13:55] <cjwatson> happens if the builder guest crashes hard enough
[13:55] <patdk-wk> ya, it was a striaght rebuild, didn't expect it to have any issues
[13:55] <cjwatson> hit retry and watch the logtail as it goes past?
[13:57] <patdk-wk> had one last night, I think crashed
[13:57] <patdk-wk> it ws building, but wasn't doing a logtail
[13:58] <patdk-wk> then after 15min or so, it was being build by a different builder
[14:20] <diwic> Hi, I get timeout errors when trying to create a recipe
[14:21] <patdk-wk> use less yeast
[14:22] <diwic> ha ha
[14:23] <diwic> any ideas on how to create a launchapad code recipe?
[14:28] <dobey> diwic: carefully
[14:28] <dobey> diwic: timeout errors happen occasionally, if you hit them, you just have to be patient and try again
[14:29] <diwic> dobey, any recommended time to wait between "reload page" hits?
[14:29] <diwic> dobey, I think I've tried 10 - 15 times now
[14:30] <dobey> no
[14:30] <dobey> do you have aa lot of recipes set up already?
[14:31] <diwic> dobey, hmm, not for ~diwic, I have a few for ~ubuntu-audio-dev
[14:31] <dobey> not sure then
[14:31] <dobey> i've gotten plenty of timeouts as well, but things eventually load after a while
[14:33] <diwic> I guess I could try again tomorrow...
[14:33] <diwic> maybe there is less work going on on Saturdays
[14:34] <dobey> i'm not sure that's why you're getting a timeout
[14:44] <diwic> \o/ it went trhough now
[14:45] <diwic> maybe it's clicking a few times in a row that did it, then it was hot in cache or something
[14:49] <patdk-wk> heh, rebuild was perfect, dunno what happened, builder crashed :)
[14:50] <dobey> patdk-wk: if there was no log, then yes, it failed before it could create a chroot
[14:50] <patdk-wk> chroot? says it's using qemu
[14:50] <dobey> yes
[14:51] <dobey> one is not exclusive of the other
[15:13] <cjwatson> dobey: no, it's also possible for that to mean it crashed later - the full buildlog is only retrieved at the end of the build
[15:13] <cjwatson> LP doesn't keep hold of the logtail snippets it fetches during a build
[15:14] <dobey> oh
[15:14] <cjwatson> and qemu is only actually used on architectures other than x86, so not this build
[15:15] <dobey> indeed (i didn't look at the arch, just stating that even when qemu is used it's still building in a chroot)
[15:16] <patdk-wk> odd, it said building using qemu
[15:16] <patdk-wk> on the i386 build
[15:17] <patdk-wk> same deal on the x64 build
[15:32] <diwic> gaah, now it time outs when I try to edit the recipe :-(
[15:33] <diwic> hmm, but the edit seems to have succeeded anyway
[15:55] <cjwatson> patdk-wk: that's just the fixed builder title
[15:55] <cjwatson> patdk-wk: it doesn't actually signify anything about the build, apologies for the confusion
[15:55] <patdk-wk> ah, ok
[16:11] <n00bnoxious> Hey folks. I've been putting together a PPA with the intention of supporting Precise and Saucy... The control file definitely works locally for both and x86 and x64 in pbuilder, but I notice that it's only building the Saucy version, even though the changelog has 2 entries, one for Precise and one for Saucy. I assume I'm missing a pretty basic fact, and any advice is appreciated!
[16:12] <n00bnoxious> Oh btw pbuilder will build for precise OR saucy fine
[16:12] <n00bnoxious> And both arches, but on Launchpad it isn't building for Precise...
[16:25] <n00bnoxious> Anybody?
[16:26] <n00bnoxious> The long story short of my question is: Does Launchpad only build the very top revision in the changelog?
[16:26] <dobey> any debian build system does, yes
[16:27] <dobey> pbuilder isn't building the older changelog entry
[16:27] <dobey> with pbuilder you are explicitly stating what to build on in the command line
[16:27] <n00bnoxious> Ah I see
[16:28] <n00bnoxious> So I have to upload two separate revisions with the same content, but different versions in the changelog?
[16:28] <n00bnoxious> *different releases
[16:28] <dobey> ideally, yes. you'd have 1.0-0ubunt1~ppa1~precise1, and 1.0-0ubuntu1~ppa1~saucy1 for example
[16:28] <n00bnoxious> Ah ok I see :) Thank you for your help dobey :D
[16:30] <n00bnoxious> And one last thing: I understand it doesn't accept binary uploads, but I also checked an older repository I had (a few days old) and it still said no packages had been uploaded even though the builds succeeded. Do I have to do anything after uploading the changes?
[16:32] <dobey> no, you can't upload binaries
[16:32] <dobey> no, if the source succeeds the binaries will be published automatically
[16:33] <n00bnoxious> Is there some kind of waiting period until it publishes them?
[16:34] <n00bnoxious> Ah ignore me
[16:34] <n00bnoxious> It's all good I just saw packages come up now :D
[16:35] <n00bnoxious> Thank you very much for your help!
[18:12] <spayno> i'm just learning about launchpad now (though linaro).  Alot of the web pages haven't been updated since 2011 or 2012 (e.g. the most Recent Launchpad blog post is Nov 2012).  Was there an exodus in 2012?
[18:12] <dobey> no
[18:13] <beuno> spayno, I think it's mostly that the tool got good enough for Ubuntu, so a lot of developers were re-assigned
[18:13] <spayno> bueno: thanks for the context/thoughts
[18:18] <cjwatson> That said, there's still development; see https://code.launchpad.net/~launchpad-pqm/launchpad/devel
[18:18] <dobey> yeah, "last blog post" is a horrible metric for whether a piece of software is actively used/developed
[18:19] <cjwatson> For some reason the front page is behind on the blog
[18:19] <cjwatson> http://blog.launchpad.net/
[18:19] <spayno> i do know it's being used, and I'm happy to hear it is
[18:20] <spayno> (more than it might appear from where I landed first)
[18:22] <spayno> I do have a bonafide linaro question.  If you look at a build, can you find the configuration and scripts used to do the build (eg like in Jenkins?).  Specifically I'm looking at the following build and I want to know how they did it: https://launchpad.net/~linaro-maintainers/+archive/staging-overlay/+build/5617474
[18:23] <spayno> the build log gives me some hints, but I"m wondering if there is a real config file somewhere
[18:23] <dobey> the source package is the "configuration"
[18:23] <cjwatson> Yes, follow the link under Archive, then "View package details", then expand the relevant entry and you can grab the source package from there
[18:24] <cjwatson> The entry points to the build system are in debian/rules
[18:24] <cjwatson> Oh and you can unpack the source package (.dsc plus whatever it refers to, usually .diff.gz / .debian.tar.gz plus .orig.tar.gz, or similar) using dpkg-source -x
[18:29] <spayno> cjwatson: trying your first way I picked a package, then expanded it.... now I'm not sure where to find the configuration
[18:30] <cjwatson> I only gave one way :)
[18:31] <cjwatson> so, expand acpi-abat, dget -x https://launchpad.net/~linaro-maintainers/+archive/staging-overlay/+files/acpi-abat_0.2-0linaro1.dsc, look in acpi-abat-0.2/debian/rules
[18:32] <cjwatson> (possibly dget -u if you aren't likely to have the relevant key available)
[18:37] <spayno> cjwatson: dget-u worked great thanks.
[18:41] <spayno> if I want to create a test/play project, should I just create one on qastaging.launchpad.net?
[18:42] <cjwatson> You can do that, yeah
[18:42] <dobey> or just staging.launchpad.net (i'm not sure what the difference between those two is exactly)
[18:42] <cjwatson> I can never remember the precise details, but I'd probably use staging, I think it's overwritten slightly less often
[18:46] <spayno> cjwatson: I'm now reading your blog post btw about your arm build farm
[18:47] <spayno> cjwatson: do you an linaro share ARM build infrastructure or do they have their own hardware?
[18:54] <cjwatson> spayno: I believe they have their own hardware, but they do run some ARM builds on Launchpad.  I don't know the details of how Linaro builds things.
[20:28] <bekks> Hi! What could be wrong when I dont see a bug in "Affecting bugs" after just clicking "This bug affects me" in a bug?
[22:13] <RFleming> Greetings.  I was redirected here to ask about an abandoned account


[04:01] <mfisch> TheMuso`: ping
[04:02] <mfisch> I have an odd situation with speakup
[04:03] <mfisch> We can sync with debian since the binaries are now in the kernel according to TheMuso`
[04:03] <mfisch> the only binary built anymore is speakup-doc
[04:03] <mfisch> so if I sync to debian, then we will have a newer speakup-doc, but still the old binary speakup package I assume?
[07:28] <dholbach> good morning
[07:45] <Noskcaj> evening dholbach. Would you mind giving me a testimonial for https://wiki.ubuntu.com/Noskcaj/MOTU ?
[07:46] <Noskcaj> I won't actually have the meeting till january when i have school holidays
[07:46] <Noskcaj> And it probably has to be be email because of my timezone
[07:46] <dholbach> Noskcaj, sure
[07:47] <dholbach> Noskcaj, I'd recommend you use https://wiki.ubuntu.com/UbuntuDevelopment/DeveloperApplicationTemplate as a template for the application
[07:47] <Noskcaj> thanks
[07:48] <Noskcaj> will do
[07:49] <dholbach> :)
[07:50] <Noskcaj> should i still have a separate page for the MOTU application or just use my main one?
[07:51] <dholbach> one should be enough
[08:24] <Noskcaj> dholbach, https://wiki.ubuntu.com/Noskcaj should be close enough
[08:26] <dholbach> cool
[08:30]  * Noskcaj wishes alioth was less broken so he could get a list of people who have sponsored stuff for him
[08:35]  * Zhenech hands Noskcaj "who-uploads"
[08:36] <Noskcaj> um?
[08:36] <Noskcaj> i.e. the sponsorship miner
[08:43] <Zhenech> it should give you who uplaoded which package, so your sponsors
[19:45] <Ampelbein> Where would I investigate why dbus-sharp 0.8.0-1, uploaded to debian 32 days ago, didn't make it automatically into trusty yet?
[19:46] <Ampelbein> The Ubuntu package does not have local changes as far as I can tell (https://launchpad.net/ubuntu/+source/dbus-sharp)
[19:52] <Noskcaj> Ampelbein, I don't know the exact reason, but it's probably because dbus-sharp is FTBFS everywhere
[19:53] <Ampelbein> The source package isn't even in Ubuntu?
[19:54] <Ampelbein> And I don't see it FTBFS in Debian either.
[19:57] <geser> I see no reason why it shouldn't got auto-synced
[20:01] <Ampelbein> So, if I manually used syncpackage it wouldn't cause the world to collapse into a super black hole?
[20:02] <geser> no :)
[20:02] <geser> using syncpackage would be what I would try if was on my Ubuntu system right now
[20:04] <Noskcaj> Ampelbein, It looks like it was never built on debian. I think it has to before we sync it
[20:04] <Ampelbein> Wouldn't that mean that we would never get pure arch:all packages since they technically are never built on Debian's build servers?
[20:05] <Ampelbein> If I understand Debian correctly, arch:all packages are build and uploaded by the developers instead of being built.
[20:05] <geser> Noskcaj: the arch:all deb was uploaded with the source (as is required by Debian) so there is no build log for it available in Debian
[20:06] <geser> It would be news to me if the autosync would care about FTBFS in Debian
[20:06] <Ampelbein> Anyway, syncpackage did succeed and the package is now in trusty.
[20:06] <Noskcaj> ok. Ignore everything i said
[20:07] <Ampelbein> Thanks to both of you, Noskcaj and geser for checking if I missed something obvious.
[21:07] <Ampelbein> Great. I upload a fix for a package that failed on amd64. Build succeeds locally in sbuild. On the auto-builders? All arches fail.


[00:11] <fluvvell> dekarl, thanks for the interesting and fully random response, for anybody who may find this post should it happen to be archived online, let me just say this card has been working in a mythtv install since 2007, various kernels and iterations all from the Ubuntu stream. The fault turned out to be a motherboard with a faulty pci card controller/heatsink combo.
[00:14] <fluvvell> for those readers who happen to be in New Zealand, the skystar II cards have been available to access freeview when they are not in line of sight of a terrestrial transmitter digitally enabled.  b2c2-flexcop drivers are installed on the ubuntu/mythbuntu distros, probably on others as well. This was confirmed with a 12.04.2 boot CD on a working motherboard.
[00:14] <fluvvell> They are of course a satellite receiver card
[01:52] <qwebirc34341> I'm trying to install mythbuntu 12.04, 32-bit.  Burned the iso to CD, booted from it, and after a bit I get to what looks to be a desktop screen, with "Applications" in the top left corner.  However, there is no "install mythbuntu" icon (or any icon) on the desktop, and the mouse freezes.
[01:52] <qwebirc34341> My next step is to just try to install plain Ubuntu and see if that works
[02:27] <qwebirc34341> gonna go troubleshoot some hardware.  thanks yall.
[05:41] <dekarl> sorry fluvvell, no harm intended. I missed the part where you said "this is the kernel version that worked up to last week" and got side tracked by google results for "a new revision of an old card that needs new glue code"
[05:48] <fluvvell> dekarl, yes that was a bit of a givaway! I wasn't sure if you had been online at that point so wasn't going to be too rude. All a good learning experience for me anyway, hadn't been too ready to give up the motherboard so quickly as its within warranty. All the better though. Supplier (freight delivery notwithstanding during a local flood with road-outages) is overnighting me a new one. Gigabyte GA-880GA-UD3H
[06:34] <dekarl> the little girl is up, got baby duty
[08:04] <dekarl> OT, we now plug barges in the gaps in our dikes... http://www.faz.net/-12223561.html
[20:03] <qwebirc88408> hello how do i select the cad driver eg card=114


[02:35] <LLStarks> hey bryceh, would you recommend ati or nvidia for a new linux box if i exclusively use non-free drivers?
[02:35] <bjsnider> nvidia, no contest
[02:36] <LLStarks> reasoning?
[02:36] <bjsnider> you're using the blobs, right?
[02:37] <bjsnider> the nvidia driver gives you vdpau, opengl 3.2, xrender accel
[02:37] <bjsnider> support for newest x servers and cards right away
[02:38] <JanC> OTOH, like I saw twice during the last 10 days, people can't seem to get there laptop to work together with a beamer if they have nvidia  ;-)
[02:38] <LLStarks> what about free drivers? how are nv, nouveau, radeon, and radeonhd?
[02:38] <bryceh> they all suck
[02:38] <bryceh> buy a mac
[02:38] <bjsnider> they're all crap
[02:38] <LLStarks> no 3d?
[02:39] <bryceh> radeon's ok
[02:39] <bryceh> at least for R500 and earlier
[02:39] <bjsnider> the intel driver is the ony good foss graphics driver
[02:39] <JanC> radeonhd has 3D if you have the exact same card as the developers IIRC  ;)
[02:39] <JanC> (or was it the radeon driver?)
[02:39] <LLStarks> intel graphic drivers are godly. intel graphic hardware is crap.
[02:40] <LLStarks> how is gallium coming along?
[02:41] <LLStarks> can i expect nouveau to perfect it and all of xf86-intel to use it by the end of 2011?
[02:41] <bjsnider> not ready for prime time
[02:41] <JanC> AFAIK gallium is a tool (library) to make 3D graphics drivers, it's not a graphics driver in itself...
[02:41] <bjsnider> possibly
[02:41] <JanC> ?
[02:41] <LLStarks> heh. i though gallium was replacing mesa.
[02:42] <LLStarks> or do i have a completely incorrect view of how graphic stacks work?
[02:42] <bjsnider> not anytime soon, that's for sure
[02:42] <JanC> well, mesa is used for something like that too  ;)
[02:43] <JanC> as I understand mesa, it implements OpenGL in software, and lets drivers override that by hardware-supported methods
[02:45] <LLStarks> hm
[02:46] <bjsnider> i don't know how anyone tolerates the fglrx/ati drivers
[02:46] <JanC> """Gallium3D is a software library for 3D graphics device drivers being developed by VMware (previously Tungsten Graphics).[1] Gallium3D operates as a layer between the graphics API and the operating system with the primary goal of making driver development easier, bundling otherwise duplicated code of several different drivers at a single point."""
[02:47] <JanC> http://en.wikipedia.org/wiki/Gallium3D
[02:47] <bjsnider> when i put this system together i tolerated it for 15 minutes before returning the card
[02:51] <LLStarks> wut. vmware gobbled tungsten?
[02:52] <JanC> maybe for the better (let's hope)
[02:52] <LLStarks> anyway, i have a question about the 2.6.33 backport plans. which option is being considered most heavily?
[02:52] <JanC> LLStarks: I guess vmware wanted 3D graphics knowledge for VMs
[02:53] <LLStarks> that's good. 3d emulation sucks.
[02:54] <LLStarks> as long as they keep it gpl
[02:54] <JanC> well, I guess they want 3D passthrough  ;)
[06:03] <kklimonda> bryceh: if I have to add resume=/dev/sdXY to resume from hibernation should I mark test as passed or nt?
[06:03] <kklimonda> not*
[06:03] <kklimonda> bryceh: I'm talking about nouveau evaluation
[06:03] <bryceh> not
[06:03] <bryceh> mark it failed and list what you did to work around it
[06:04] <bryceh> kklimonda, btw thanks for helping with testing :-)
[06:08] <kklimonda> bryceh: and when testing dual head should I mark it as failed if nouveau fail to detect that I've plugged my monitor until I use xrandr or display from preferences menu?
[06:08] <kklimonda> plugged or unplugged
[06:09] <bryceh> if you can get it to work after fiddling with xrandr, count it passed
[06:10] <bryceh> kklimonda, but we're not sticklers on what counts as passed or failed; kind of use your judgment, if you feel the driver is really sucking on something, fail it.  If you think it's adequate, give it a thumbs up
[06:10] <bryceh> remember we're comparing against -nv, so that's a pretty low hurdle ;-)
[06:11] <kklimonda> bryceh: I should mark all tests as passed then - maybe leave hibernation one as failed..
[06:11] <bryceh> kewl
[06:11] <kklimonda> bryceh: are all required bits for nouveau uploaded to archive or do I still have to use xorg-edgers ppa?
[06:11] <kklimonda> I'd like to reinstall system when alpha3 is released and test it on clean install
[06:12] <bryceh> kklimonda, I'm pretty pleased with the testing that folks have done.  It's giving me confidence that we're going in the right direction with nouveau.  We may have some issues to square away but I don't feel like we're going to need to go back to -nv or anything drastic
[06:12] <bryceh> kklimonda, there are still a few bits outstanding for nouveau.  I think we may have them all in by the end of the week
[06:13] <kklimonda> bryceh: for example packages that have been uploaded to archive seem to be missing nouveau_kvm_hook for initramfs.. or maybe I don't have the right package installed
[06:14] <kklimonda> bryceh: I'm really pleased with nouveau myself - especially now that there are so many weird problems with nvidia driver in lucid :)
[06:14] <bryceh> yeah I'm not sure whether linux-backports-modules is in yet, but we'll need that in the archive before we can really start wrapping things up
[07:11] <RAOF> kklimonda: The kms hook really needs to go into the framebuffer hook shipped with initramfs-tools.
[10:47] <tjaalton> any pending changes to mesa, or should I upload what's in git now?
[10:48] <tjaalton> Sarvatt: ^
[12:21] <tjaalton> xserver 1.7.5 merged
[14:12] <sebner> tseliot: your new nvidia upload to lucid drops my glxgears frames rate about 5-10k (to half maybe)
[14:13] <tseliot> sebner: what does glxinfo say?
[14:14] <sebner> tseliot: http://pastebin.com/m59fe117a
[14:15] <tseliot> sebner: it's not the final release so it might be a temporary regression
[14:15] <sebner> kk
[14:15] <tseliot> sebner: do 3D applications seem slower?
[14:16] <sebner> tseliot: definately
[14:16] <tseliot> glxgears is not a benchmark
[14:16] <tseliot> ok
[14:17] <tseliot> sebner: also what does this command say? "ldconfig -p | grep GL" and does the X log show anything interesting?
[14:18] <sebner> tseliot: http://pastebin.com/m213d74b2 Xorg log shows acpi failure (dunno if this is new though)
[14:20] <tseliot> sebner: maybe nvidia is doing something "new" ;)
[14:20] <tseliot> but other than that it should be fine
[14:21] <sebner> heh
[14:21] <sebner> kk
[14:22]  * sebner will just wait until mighty tseliot gets his hands on a new and fixed driver then :)
[14:22] <tseliot> ;)
[18:42] <Sarvatt> tjaalton: whats in git now works for mesa, the bug fix for building rss-glx is waiting on moving libGL back to /usr/lib as far as I can see but the alternatives for libgl1-mesa-swx11 are working fine
[19:06] <bryceh> heya Sarvatt
[19:06] <bryceh> Sarvatt, what's your opinion on sticking with 2.9.1 vs moving to 2.10 for -intel?
[19:12] <Duke`> no execbuf error for days... Duke` is happy \o/
[19:13] <bryceh> Duke`, is that with stock lucid or xorg-edgers?
[19:13] <Duke`> xorg-edgers
[19:13] <Duke`> on karmic
[22:45] <bryceh> tjaalton, heh the comments on the phoronix article are arguing every single opinion on this.
[22:46] <bryceh> a third think we're crazy not to be using the 2.6.33 kernel, a third think we're crazy to be considering backporting *anything* from 2.6.33 for an lts, and a third are crazy themselves
[22:47] <RAOF> Are you sure those groups have no intersection? :)
[22:47] <bryceh> RAOF, ;-)
[22:49] <BUGabundo> ehe
[22:49] <BUGabundo> bryceh: what are we backporting from .33?
[22:50] <bryceh> it's a bit irritating how closely phoronix follows our development discussions.  It's like having a conference call and someone hooks the phone to the loudspeaker at comdex
[22:51] <bryceh> BUGabundo, drm
[22:51] <bryceh> BUGabundo, RTFPhornix ;-)
[22:51] <BUGabundo> ?
[22:51] <BUGabundo> that I don't know
[22:52] <bryceh> probably for the best
[23:05] <tjaalton> bryceh: haha :)
[23:06] <tjaalton> Sarvatt: ok, I'll probably upload it tomorrow until someone gets to it before me
[23:13] <bryceh> tjaalton, mesa?
[23:15] <BUGabundo> any news on fixing 3D in nouvuea?
[23:15] <BUGabundo> been broken since Sunday
[23:15] <tjaalton> bryceh: yep
[23:16] <bryceh> tjaalton, great
[23:17] <RAOF> BUGabundo: -ENOTSUPPORTED!  Without having looked at it, I'd guess that it now requires libdrm 2.4.18 and a drm interface version 0.0.16, which means pulling from nouveau's linux tree rather than linus.
[23:18] <BUGabundo> ok
[23:18] <BUGabundo> thanks
[23:20] <RAOF> If we end up planning on pulling 2.6.34 intel & radeon into linux-backports-modules, we may well end up pulling in the 0.0.16 nouveau drm interface soon.
[23:59] <persia> Hey.  Seems that the latest x11-common pulls in a heap of -dev packages.  Is this intentional?  What use case does it support?