[00:08] <maxb> Daviey: This is a bad time of day to find someone who can help with that, I think. US or European daytime are good times, or you could ask via the answers tracker (https://answers.launchpad.net/launchpad/+addquestion)
[00:20] <Daviey> maxb: i'll try tommorrow, thanks
[00:33] <fta> are lucid builders sick?
[00:33] <fta> http://launchpadlibrarian.net/38060835/buildlog_ubuntu-lucid-i386.chromium-browser_<IP_ADDRESS>~r34537-0ubuntu1~ucd1_FAILEDTOBUILD.txt.gz
[00:36] <ScottK> Nice.  How long ago was that?
[00:41] <crimsun> well, I do trigger that libtool asplode on armel pretty often
[00:55] <fta> amd64 too
[00:56] <fta> ScottK, was the question for me? if so, ~30min ago
[00:56] <wgrant> fta: Same builder?
[00:56] <wgrant> Wait, no, no arch-agnostic buildds in production yet.
[00:57] <fta> nope, promethium & protactinium
[00:57] <wgrant> Is it always the same package?
[01:34] <stgraber> all my LTSP builds (3 uploads) failed for te same reason
[01:34] <stgraber> *the
[01:35] <wgrant> stgraber: Links to the builds?
[01:35] <stgraber> https://launchpad.net/~stgraber/+archive/ppa/+build/1453022/+files/buildlog_ubuntu-lucid-amd64.ltsp_5.1.99~bzr1534-0ubuntu1~ppa1~lucid1_FAILEDTOBUILD.txt.gz
[01:36] <stgraber> https://launchpad.net/~stgraber/+archive/ppa/+build/1453043/+files/buildlog_ubuntu-lucid-amd64.ltsp_5.1.99~bzr1534-0ubuntu1~ppa2~lucid1_FAILEDTOBUILD.txt.gz
[01:37] <stgraber> second was retried from LP after 30min with the same result
[01:41] <wgrant> lamont: ^^ That looks reasonably sinister.
[01:44] <lamont> wicked.  did you happen to notice which buildd?
[01:44] <stgraber> lamont: happened for both i386 and amd64 on 3 different build for me, so probably not a single buildd (or I'm very unlucky today)
[01:46] <wgrant> There are no obvious problematic uploads.
[01:48] <stgraber> happened on promethium, aluminium and platinum with my LTSP builds
[01:48]  * lamont gets out his ballpeen for a little adjustment.
[01:51] <lamont> stgraber: interestingly, crested seems happy
[01:55] <crimsun> rothera, adare, yellow, hooker, and jaboticaba just frowned really nastily at me
[01:56] <crimsun> (I really did pbuilder+piuparts on amd64 beforehand)
[01:58] <stgraber> I uploaded an updated pkgbinarymangler earlier tonight, seems like something with that bzr branch is a bit broken (as in, it doesn't seem to match what used to be in archive so some unknown changes might have happened), I really hope it's not what we are seeing now
[01:58] <stgraber> but I'm looking at it and will upload a fixed one (basically, previous source package + my change without using the bzr branch)
[01:58]  * lamont fetches the current tarball so he can dist-upgrade and see what it does from there
[01:59] <lamont> if it's package mangler, I'm gonna put it in the *^()**(_*%^*_%_%^ JAIL AGAIN
[02:00] <lamont> stgraber: I don't suppose that it build-depends on nothing more than build-essential?
[02:00]  * stgraber fixes it the hard way, will poke with the bzr branch later ...
[02:00] <stgraber> lamont: lockfile-progs
[02:01] <lamont> well, installing the build-deps is the step that fails....
[02:02] <stgraber> right, though if I understand correctly what happened, the new pkgbinarymangler no longer contains anythings as a lot of very useful files were bzrignored for some reason
[02:02] <stgraber> and so were dropped from the bzr branch ...
[02:03] <stgraber> http://pastebin.com/f7b7e45ef
[02:03] <stgraber> is the current .bzrignore
[02:03] <wgrant> Impressive.
[02:03] <wgrant> But that shouldn't break dpkg-deb.
[02:06] <stgraber> uploaded new pkgbinarymangler, though it'll probably fail because of the current issue.
[02:06] <stgraber> Now to poke at bzr and make the branch work as it should ...
[02:08] <wgrant> Ah.
[02:08] <ScottK> wgrant, lamont: Is it known that this problem affects Ubuntu buildds too?
[02:08] <wgrant> Yes.
[02:08] <ScottK> OK
[02:08] <wgrant> pkgbinarymangler is broken.
[02:08] <wgrant> And it diverts dpkg-deb.
[02:08] <ScottK> Sigh.
[02:08] <wgrant> => BOOM
[02:08] <ajmitch> stevenk is sitting here rejoicing in that fact now
[02:11] <stgraber> ok, managed to fix the branch too (as in, bzr-buildpackage -S now gives the same result as my non-bzr source package)
[02:12] <stgraber> of course the fixed pkgbinarymangler failed to build but that was to be expected ...
[02:12] <wgrant> If only copy-package.py allowed copies of deleted packages with binaries.
[02:12] <lamont> yeah.  and I'm going to go put it on hold and just leave it that way and manually upgrade it from time to time
[02:13] <wgrant> That would make fixing this really easy.
[02:14] <lamont> yeah.  shouldn't take me more than about 30 minutes
[02:14] <lamont> bide
[02:16] <stgraber> I guess only reason why the last working upload was ok was because it was on lool's computer and so he had that file even if it was bzrignored ...
[02:17] <stgraber> lool: around by any chance ? (not very likely at 3am but who knows)
[02:19] <maxb> Is merge proposal diff generation instantaneous now, or was I just incredibly lucky?
[02:27] <lamont> new chroots uploaded, when slangasek tells me to, I'll  unhold it again.  you get to convince him to tell me.
[02:28] <lamont> stgraber: ^^
[02:28] <stgraber> lamont: thanks for fixing everything.
[02:33] <wgrant> maxb: It's */1 now.
[02:47] <verbalshadow> i'm have trouble following the how to let several people commit to a branch, https://help.launchpad.net/Code/QuickStart i'm missing something
[02:48] <spiv> verbalshadow: create a team that you are all members of (if you haven't already), and set the branch to be owned by that team.
[02:50] <verbalshadow> spiv: thanks had not thought of that
[02:50] <maxb> wgrant: Apparently it managed to run inbetween me submitting the MP and the page rendering, then :-)
[02:51] <wgrant> maxb: Handy.
[03:16] <andresm> good night, anyone knows where can i find the launchpad roadmap -or existing effort- for translating its own interface ?
[03:21] <kirkland> lamont: do i need to re-try my builds?
[03:21] <kirkland> lamont: or will that trigger automatically?
[03:21] <crimsun> I retried mine
[03:22] <crimsun> lamont: you're a rock star. Thanks!
[03:37] <xnox> andresm: search bugs.launchpad.net/launchpad it was there somewhere there are just discussions
[03:41] <andresm> ok, this is the one i was looking for bug #81419
[05:52] <AnAnt> Hello, I have a question about translations
[05:54] <AnAnt> so a person adds a translation to a project on Launchpad, so the Last-Translator is set to the name of this person, now after this translation gets exported to bzr then imported back into Launchpad, launchpad changes the Last-Translator field to the project owner, why is that ?
[05:54] <AnAnt> I see that this is not a nice thing
[06:46] <aalex> How come the source of my package was not available ? It says "Source: not available". See the build log : http://launchpadlibrarian.net/38068464/buildlog_ubuntu-lucid-i386.toonloop_1.1.8-0ubuntu2_FAILEDTOBUILD.txt.gz
[06:52] <aalex> "toonloop_1.1.8-0ubuntu2.dsc.
[06:52] <aalex> Package includes an .orig.tar.gz file although the debian revision suggests
[06:52] <aalex> that it might not be required. Multiple uploads of the .orig.tar.gz may be
[06:52] <aalex> rejected by the upload queue management software."
[06:52] <aalex> That's from my most recent trial.
[07:32] <dholbach> hiya
[07:32] <dholbach> who could help me with getting a poll removed from LP?
[07:56] <spm> dholbach: possibly me.... :-)
[08:34] <MegaHerz|wrk> Hi all
[08:34] <MegaHerz|wrk> Any ideas how to search launchpad for PROJECTS not BUGS#
[08:34] <MegaHerz|wrk> ?
[08:36] <thekorn> MegaHerz|wrk, https://edge.launchpad.net/projects
[08:38] <MegaHerz|wrk> thekorn: hah, thanks!
[08:38]  * MegaHerz|wrk has bookmarked the link
[10:41] <slytherin> How do I report a bug against the translations component of launchpad?
[11:32] <matsubara> slytherin, https://launchpad.net/rosetta/+filebug
[11:32] <henninge> slytherin: Maybe we can talk about it first? ;-)
[11:34] <slytherin> henninge: Sure, it's a minor issue.
[11:35] <slytherin> henninge: On translations page for any project, we can sort the translations with various criteria i.e. Status, Untranslated, Last Changed etc. But there are no visual indicators for this. A small arrow besides column names would be good.
[11:38] <henninge> slytherin: ah, I see. Yes, please add the bug and add a "ui" tag to it.  That ^ is agood description alrady, btw. ;-)
[11:38]  * henninge adds a space and an 'e' ...
[11:39] <henninge> slytherin: thank you for the suggestion.
[11:39] <slytherin> henninge: You are welcome. :-)
[11:41] <slytherin> henninge: The small arrow appears only when you actually click the column name.
[11:42] <henninge> slytherin: so the problem is that the default sorting is not indicated?
[11:43]  * henninge takes a closer look now
[11:43] <slytherin> henninge: yes. On first load of the page there is no indication how it is sorted as well as the indication that user can sort the data.
[11:44] <henninge> slytherin: is that only on translation pages? Maybe it's a general ui problem.
[11:44] <slytherin> I haven't checked if it is general problem. I am just checking translation summary page for my project - https://translations.edge.launchpad.net/gnusim8085
[11:45] <henninge> slytherin: I see the same problem on branches pages
[11:46] <henninge> slytherin: i.e. https://code.launchpad.net/launchpad
[11:47] <slytherin> henninge: right
[11:48] <henninge> slytherin: so please report the bug here https://bugs.launchpad.net/launchpad-foundations/+filebug
[11:48] <slytherin> ok
[11:54] <slytherin> henninge: Done - bug 509596
[11:55] <henninge> slytherin: thanks!
[11:56] <slytherin> I have another issue I want to report but it needs discussion first.
[11:56] <slytherin> henninge: Are you free for that?
[12:00] <henninge> slytherin: not too much atm. I'd prefer later. I have a phone call now and will go to lunch after that.
[12:00] <slytherin> fine, will discuss later
[12:00] <henninge> slytherin: cool, thanks.
[12:39] <asabil> hi all
[12:39] <asabil> can someone help me fixing this: https://code.launchpad.net/~vcs-imports/vala ?
[12:45] <matsubara> asabil, let me take a look
[12:45] <asabil> thanks
[12:45] <asabil> basically there is trunk and new-trunk
[12:46] <asabil> maybe rm trunk && mv new-trunk trunk ?
[12:47] <matsubara> asabil, done
[12:47] <asabil> thanks
[12:48] <matsubara> you're welcome
[13:06] <fagan> Hey all, I was wondering about the search
[13:07] <fagan> I wanted to send someone a link to the results and it was really long
[13:17] <matsubara> fagan, you can use http://tinyurl.com/ to make it shorter
[13:17] <idnar> or http://bit.ly/
[13:18] <fagan> True but then launchpad says the link was wrong
[13:19] <fagan> I did an advanced search to find all the bugs with a tag that I was looking for and it didnt work
[13:20] <fagan> It would be nice if the url wasnt a mile long anyway
[13:43] <leoquant> matsubara how to prevent an open pgp key used in launchpad and mailing from expiring, and how to tell the ubuntu keyserver the newe expiring date and update my launchpad account?
[13:44] <matsubara> leonardr, let me check that for you. it's an option for the gpg command
[13:45] <matsubara> leonardr, basically you need to update your key with the new expire date and re publish it to the keyserver
[13:45] <leonardr> matsubara: you mean leoquant -^
[13:45] <leoquant> ツ
[13:46] <matsubara> yes, sorry leonardr
[13:46] <matsubara> :-)
[13:46] <leoquant> and how to update the new expir date via launchpad in my account?
[13:47] <leoquant> matsubara can this only be done via the console or also via seahorse?
[13:47] <matsubara> leoquant, so, this has nothing to do with launchpad. it's all done with your gpg key. launchpad will then "know" that the new expire date when it checks it from the keyserver
[13:48] <leoquant> ok
[13:48] <matsubara> leoquant, my own choice is to use the console to update it
[13:48] <leoquant> indeed, sorry
[13:48] <leoquant> the console is my choise also
[13:49] <leoquant> a did a wilde google ride but didn't get the how to.....:P
[13:49] <leoquant> *I
[13:50] <leoquant> thats why I am asking you
[13:50] <matsubara> leoquant, gpg --edit-key <key-id> (e.g. gpg --edit-key 767E56BC)
[13:50] <matsubara> leoquant, it'll then enter a Command>  prompt
[13:50] <matsubara> type expire
[13:51] <matsubara> and then choose one of the options
[13:51] <leoquant> ok
[13:52] <matsubara> leoquant, let me know if you need further help
[13:52] <leoquant> thx for now
[13:53] <matsubara> sure, you're welcome
[13:55] <matsubara> leoquant, after successfully updating the expiration date, you need to send it to the keyserver: gpg --send-key <key-id> --keyserver keyserver.ubuntu.com
[13:58] <ammonkey> hello, is there a problem with launchpad's ppa?
[13:58] <leoquant> ok matsubara when my visitors are left i'll give it try and let you know
[13:59] <leoquant> *visitors*friends
[14:00] <matsubara> ammonkey, can you be more specific? we had an issue with the PPA publisher yet but that's been solved
[14:00] <matsubara> s/yet/yesterday/
[14:02] <ammonkey> well i upload new packages version and it does not appear ...but i ve got a problem before on a version i did not commited all the files so there was a compil error ...but impossible to update with the same version number so i tried a new one ...But nothing new in my ppa ...so i am lost :)
[14:02] <ammonkey> all in sucessful with dput i sign my files etc but i don't receive any email from launchpad
[14:03] <ammonkey> s/all in/all is/
[14:07] <matsubara> ammonkey, what's the ppa? can you paste the output of the commands you ran to upload the package?
[14:08] <ammonkey> matsubara: dput ppa:am-monkeyd/nautilus-elementary-ppa nautilus_2.28.4-0ubuntu1.3_source.changes
[14:09] <ammonkey> matsubara: the output is here: http://pastebin.com/m49a23d8c
[14:13] <matsubara> ammonkey, I don't know what's wrong with that. bigjools can you help ammonkey with a PPA uploading problem ^?
[14:14] <ammonkey> matsubara: maybe it s stuck because of compil problem on 1.2version and now refuse to upgrade to 1.3? ... ppa upload are in realtime or it must wait for a crontab?
[14:15] <ammonkey> i tried many time to re upload in the same version but with no success so i incremented the version and still no result
[14:18] <matsubara> ammonkey, I think the compilation problem can't affect the build process. In any case, you should get an email saying what's wrong. let's wait a bit for bigjools as he's a soyuz developer and knows this stuff very well.
[14:18] <ammonkey> matsubara: thx for your help
[14:46] <leonardr> gary et al: http://blog.launchpad.net/general/anonymous-access-to-the-launchpad-web-service-api
[14:48] <mars> leonardr, great!  That should make writing small utility scripts much easier
[14:48] <mars> It was annoying to have them hang because they needed the auth cookie
[14:48] <mars> cookie/token
[14:53] <bigjools> ammonkey: https://answers.launchpad.net/soyuz/+faq/227 help?
[14:53] <bigjools> matsubara: fyi as well --^
[14:54] <matsubara> thanks bigjools
[14:55] <ammonkey> bigjools: it's ok for the mails i get them....in fact i got a bad filter in my mailbox my bad ...i deleted my pakages versions .. i hope to not get an error for the next dput
[14:55] <ammonkey> bigjools, matsubara how much time do launchpad need to delete the files?
[14:56] <bigjools> ammonkey: why do you need to know?  it's generally within 24h
[14:56] <ammonkey> bigjools: to know when re upload again ;)
[14:56] <bigjools> ammonkey: you can't re-upload the same version
[14:57] <bigjools> bump the version, re-upload, and the old package will automatically be removed
[14:57] <ammonkey> bigjools: well i tried with an incremented one with no succes
[14:57] <bigjools> what error did you get?
[14:57] <ammonkey> wait i try again..and tell u
[14:58] <thekorn> leonardr, great news, thanks!
[14:59] <maxb> leonardr: Nice! One piece of information that's missing from the blog post: What's the 'name' of production for use in Launchpad.login_anonymously ?
[15:01] <maxb> Also, what's the rationale for using a 'name' rather than the *_SERVICE_ROOT constants?
[15:02] <maxb> (and why does lp:launchpadlib not have any tags?!)
[15:05] <vish> hi.. how to do a merge in lp? ken Accepted the merge , but he isnt sure how to do it...  ;)  https://code.launchpad.net/~vish.../ubuntu/lucid/human-theme/bug507632+bug495644/+merge/17538
[15:05] <vish> do i set the status to "merged" or... does  he have to do it?
[15:05] <leonardr> maxb: the rationale is that it's easier
[15:05] <ammonkey> bigjools: http://pastebin.com/d191c6931 ..still no email i checked my email filters this time ...And no news on the ppa page
[15:05] <leonardr> you can still use _SERVICE_ROOT if you want
[15:06] <ammonkey> bigjools: Oo accepted this time :)
[15:06] <bigjools> glad to hear it :)
[15:06] <proppy> Hi, I've got an OOPS-1480B1319 when trying to submit a bug to https://bugs.launchpad.net/ubuntu/+source/poker-network/+filebug-inline-form
[15:06] <proppy> how can I help
[15:06] <leonardr> maxb: the production string is 'production'. all the strings are given in launchpadlib uris.py
[15:07] <bigjools> ammonkey: it can take up to 5 minutes after your upload completes
[15:07] <ammonkey> bigjools: thank u very much...it seems in a good way this time
[15:07] <bigjools> great
[15:08] <maxb> leonardr: oh.. I see.. it's confusing because you use both patterns in the blog post, but I guess that's because not only are you demonstrating two different APIs, but two different launchpadlib versions.
[15:08] <leonardr> maxb: right. old version of launchpad doesn't support 'edge'
[15:08] <leonardr> er, launchpadlib
[15:11] <mars> vish, did you have a look at https://help.launchpad.net/Code/Review ?
[15:12] <vish> mars: yeah , then also saw > http://doc.bazaar.canonical.com/bzr.dev/en/user-guide/merging_changes.html
[15:12] <mars> vish, good question about the status though.  beuno ^ any ideas?  The Code team is in Wellington I believe
[15:13] <mars> beuno, I ask because I have often wondered about the status myself.  Is it a manual or magic setting?  How is it supposed to be used?  Is there an implicit workflow? (I could go on :)
[15:14] <vish> mars: so the main author would have to do > $bzr merge https://code.launchpad.net/~vish.../ubuntu/lucid/human-theme/bug507632+bug495644/+merge/17538 and it gets merged?
[15:15] <proppy> got it, https://lp-oops.canonical.com/oops.py/?oopsid=1480B1319 happends when body of the bug report is empty
[15:16] <mars> vish, he would just merge the branch, no the merge proposal.  So he would execute: $ bzr merge lp:~vish.../ubuntu/lucid/human-theme/bug507632+bug495644
[15:16] <vish> ah... ok
[15:18] <mars> he would check that your changes merged cleanly into mainline, "bzr ci" if they did, then "bzr push" back onto LP.  http://doc.bazaar.canonical.com/bzr.dev/en/user-guide/organizing_branches.html#merging-a-feature-into-the-trunk
[15:18] <mars> vish, ^
[15:19] <vish> mars: thanks :)
[15:28] <soren> Dear Santa. Can I please have a "E-mail me all (including historic) bug mail for this bug" method in the lp api? Love, Soren.
[15:30] <soren> And a pony.
[15:33] <proppy> Which color ?
[15:33] <soren> proppy: All of them.
[15:34] <soren> proppy: Oh, the e-mail? Black and white, please.
[15:34] <proppy> ah a rainbow pony, my sister had one :)
[15:35] <proppy> soren: maybe there is something like an rdf export for bug report
[15:35] <proppy> that's not exactly black and white but :)
[15:35] <soren> I want e-mail.
[15:36] <soren> I might be able to settle for a button in the web UI to trigger it.
[15:46] <soren> What's supposed to be in the messages attribute of bugs when I use launchpadlib?
[15:46] <soren> If I do this: for m in launchpad.bugs[494185]: print m
[15:46] <soren> I get no output.
[15:47] <soren> Is that just launchpadlib not proxying the response correctly?
[15:47] <soren> As I expected, doing the same for bugs[1] takes considerably longer, but gives the same result.
[15:48] <soren> Is it perhaps because I used Launchpad.login_anonymously?
[15:53] <soren> Apparantly so.
[16:17] <leoquant> matsubara everthing fine. just updating the keyserver gave errors this one worked: gpg --keyserver keyserver.ubuntu.com --send-key 0x key
[16:18] <leoquant> so again thx
[16:18] <matsubara> leoquant, cool. glad to help. you're welcome
[17:00] <popey> is staging.lp.net configured to send mail notifications or are they blocked?
[17:13] <superm1> hi guys, i'm having a hard time setting up a translations export branch
[17:14] <superm1> i'm a bit confused.  I pushed the trunk branch to ~dell-team/dell-recovery/translations with the intent of putting that in https://translations.edge.launchpad.net/dell-recovery/trunk/+link-translations-branch, but it keeps telling me that's an invalid value
[17:17] <matsubara> popey, they're sent to a mailbox but not to the outside world. LP developers have access to that mailbox
[17:17] <popey> ok, ta
[17:17]  * popey points Daviey to that
[17:18] <matsubara> superm1, looking
[17:20] <superm1> thanks
[17:26] <matsubara> danilos, can you help superm1 ^?
[17:26] <matsubara> Ursinha, maybe you can help superm1 ^?
[17:26] <Ursinha> hello
[17:26] <superm1> hi
[17:26] <Ursinha> :)
[17:26]  * Ursinha reads backlog
[17:27] <Ursinha> superm1: what exactly it says is the invalid value?
[17:27] <matsubara> superm1, I think you've hit bug https://bugs.edge.launchpad.net/rosetta/+bug/407260
[17:27] <superm1> Ursinha, well there is only one box on that page
[17:28] <Ursinha> superm1: ~dell-team/dell-recovery/translations as the translations branch?
[17:28] <superm1> Ursinha, yeah
[17:28] <superm1> matsubara, ah that sounds like a high possibility
[17:28] <Ursinha> superm1: so I guess it's the bug matsubara pointed, unfortunately
[17:28] <matsubara> superm1, try the workaround in the bug report
[17:29] <superm1> Yup that appears to have worked.
[17:29] <superm1> thanks guys!
[17:30] <matsubara> sure, glad to help
[17:30] <superm1> okay so next question; when i set it to automatically synch, most of the translations dissappeared that were there already from the previous manual upload
[17:30] <superm1> https://translations.edge.launchpad.net/dell-recovery/trunk
[17:31] <superm1> its like only two of the strings are showing up now
[17:31] <matsubara> superm1, see this announcement: https://edge.launchpad.net/launchpad-project/+announcement/3451
[17:31] <matsubara> superm1, more specifically: "A word of caution: whatever branch you pick here, Launchpad is going to
[17:31] <matsubara> commit files to it. It will ruthlessly overwrite any previous versions
[17:31] <matsubara> of the files. So you probably don't want to use your development branch
[17:31] <matsubara> for this, or any other branch that you use for other things. We
[17:31] <matsubara> recommend that you create an fresh branch, and don't use it for anything
[17:31] <matsubara> else but getting translation snapshots of a single release series."
[17:32] <matsubara> so I guess, that's what happened :-(
[17:32] <matsubara> hopefully you do have a local branch for that one
[17:32] <superm1> well i did use a new branch, so they havent been clobbered in the trunk branch
[17:32] <superm1> they're just clobbered in the web ui
[17:32] <superm1> and i'm guessing will be shortly in this translations branch too
[17:33] <superm1> i think it looks like it only imported one of the .pot files actually now that i look at the import queue
[17:33] <superm1> so perhaps it's just waiting for someone to manually review the other one
[17:56] <\u03b5> is it possible to reorder releases on our project and set our proper last stable release as current ? (armagetronad)
[18:01] <\u03b5> in particular, launchpad shows 0.3.0 as our current release, while uneven version numbers in our project mean unstable builds, and while we just released <IP_ADDRESS> (stable)
[18:26] <geser> bigjools: Hi, did you have time to look what caused the OOPS I mentioned yesterday?
[18:26] <tyranos> yesterday i tried to file a bug for the first time in hwinfo package but failed due to this https://bugs.launchpad.net/malone/+bug/500856
[18:28] <bigjools> geser: I looked but I can't find the oops log :(  seb was looking into trying to make it happen again
[18:28]  * bigjools has to dash, will be back in 2h
[19:52] <cody-somerville> Just got an OOPS when trying to authenticate via OpenID: OOPS-1480I1749
[19:55] <Daviey> i've been getting OOPS's with openid recently
[19:56] <Daviey> What can i do about this? http://pastebin.daviey.com/4B58/
[19:57] <maxb> Daviey: You can use a SFTP client to delete the backup.bzr folder left over from a previous upgrade (attempt)
[19:57] <Daviey> !
[19:58] <maxb> Please note that upgrading remotely is not advised unless you have a reliable and fast connection to launchpad
[19:58] <Daviey> thanks maxb
[19:58] <Daviey> maxb: I tried branching, upgrading, pointless commit, pushing
[19:59] <Daviey> bu the upgrade didn't work
[20:00] <xnox> Daviey: see bzr upgrade guide
[20:00] <xnox> on how to upgrade branches on lp
[20:00] <xnox> 1se
[20:00] <xnox> 1sec
[20:00] <xnox> Daviey: http://doc.bazaar.canonical.com/bzr.2.0/en/upgrade-guide/index.html#migrating-branches-on-launchpad
[20:02] <Daviey> xnox: Isn't that the same as just deleting the branch via web interface, and re-pushing?
[20:02] <Daviey> same end result, but fewer steps
[20:05] <xnox> Daviey: no, if you have development focus set
[20:06] <xnox> You need to unset it first, because otherwise launchpad stacks your new branch onto the old one
[20:06] <xnox> and you are stuck with older format for most of your branch on lp
[20:06] <Daviey> crikey
[20:15] <lifeless> is there a feed off project releases?
[20:15] <lifeless> s/off/of/
[20:16] <Daviey> lifeless: Are you asking me?
[20:18] <wgrant> lifeless: I don't believe so. Most people use the announcements feed.
[20:19] <wgrant> It should be pretty easy to do, though.
[20:21] <lifeless> Daviey: no
[20:21] <lifeless> wgrant: it would be nice IMO to include releases in the announcements feed. What do you think?
[20:21] <Daviey> ok :)
[20:22] <wgrant> lifeless: I don't think so.
[20:22] <wgrant> lifeless: I think it should be trivial to create an announcement while creating a release, however.
[20:23] <lifeless> wgrant: that would work too, particularly if its on by default.
[20:24] <lifeless> wgrant: but I'mm not sure why you wouldn't want to consider releases announcements.
[20:27] <wgrant> I'm sure somebody can find a good reason.
[20:27] <maxb> hmm, is there no way to convince bzr to push ignoring a destination stacking policy?
[20:31] <maxb> apparently not
[20:33] <wgrant> maxb: '--stacked-on=', maybe?
[20:33] <wgrant> Alternatively, push, wait for it to create the branch on LP, kill it before it finishes, then push again.
[20:34] <Daviey> somewhat ugly.
[20:34] <wgrant> Yes.
[20:34] <wgrant> There should really be a --no-stacked.
[20:35] <maxb> hmm. --stacked-on= has managed to create a branch with the warning "Launchpad does not mirror file:// URLs." showing in the web UI
[20:35] <wgrant> Argh, yes.
[20:36] <maxb> stacked_on_location = file:///home/maxb/wc/bzr/bzr/bzr.dev
[20:37]  * xnox says specifying stacking options on launchpad doesn't work........
[20:37]  * xnox did file bugs a while ago
[20:37] <lifeless> maxb: reconfigure can unstack it
[20:38] <xnox> lifeless: but you cannot stack it onto something else
[20:38] <xnox> and you need fast connection
[20:38] <lifeless> xnox: thats why it stacks by default to save bandwidth
[20:39] <xnox> Yeah, I mean if you want to restack a branch onto something else the only way is to change development focus and push a new branch
[20:40] <lifeless> xnox: thats false
[20:40] <xnox> You cannot do bzr reconfigure lp:~me/pr/branch --stack-on=lp:~team/pr/experimental
[20:40] <xnox> it results in a broken branch on launchpad
[20:40] <xnox> lifeless: please prove me wrong
[20:40] <lifeless> bzr reconfigure lp:~me/pr/branch --stacked-on=bzr+ssh://bazaar.launchpad.net/team/pr/experimental
[20:42] <xnox> bug #498063
[20:42] <lifeless> it may not propogate that setting to the mirror branch; if so thats not a bzr bug
[20:42] <xnox> yeap I did that
[20:42] <xnox> then see lp:~dmitrij.ledkov/xiphos/commit-2
[20:43] <xnox> what state it is at
[20:43] <xnox> Unsupported protocol for url "lp-hosted://../commit-1"
[20:44] <lifeless> sure, there is a bug. I don't see that its a bzr bug
[20:44] <lifeless> relative stacked paths should work fine.
[20:44] <xnox> like what
[20:45] <xnox> bzr reconfigure lp:branch --stack-on=../other-branch?
[20:47] <lifeless> in the internal code on the server
[20:48] <xnox> well I tried my hardest and it didn't work by default
[20:48] <lifeless> yes, I get that.
[20:48] <lifeless> I'm not saying you can mke  it work by poking at the UI
[20:48] <xnox> maybe I can use bzrlib to set the correct path on the sample broken branch
[20:48] <lifeless> I'm saying there is a bug, but *I don't think the bug is in bzrlib*
[20:49] <xnox> Aha
[20:49] <xnox> so it's launchpad-bzr-integration which does too many smart things ;-)
[20:49] <xnox> So bzrlib does the right thing hmmmm
[20:51] <lifeless> the relative path shouldn't break anything, there is a known path to normalise against. So I think its a bug in launchpad-codes open hooks.
[20:53] <xxploit_> question im trying to setup a pbuilder environment but get this output http://pastebin.org/78828 I'm guessing it has to do with me running mint and need to change a line.
[20:56] <xnox> xxploit_: nothing to do with launchpad.... try your distribution help channell
[20:58] <lifeless> xxploit_: try #ubuntu-motu
[21:06] <xxploit_> seems the --othermirror flag was the problem works now by using --mirror instead
[22:14] <derks> Quick question, is it or will it ever be possible to creating multiple mailing lists for a team?  For example, I think it doesn't really make sense to have a 'myproject-announce' team just so i can get an announce mailing list setup
[22:15] <derks> That and, the ability to subscribe to a list without having a launchpad account or joining the team would be nice....  a lot of people just want the announce email, not to have to signup on a site and join a team, etc.    Just curious
[22:21] <maxb> derks: It's worth searching for and filing a feature request bug if there isn't one already
[22:22] <derks> maxb, thanks... that is my next step.  just wanted to see if there was any hearsay or what-not
[22:23] <maxb> I think there's a bug somewhere about making it possible to subscribe to a ML without joining the team
[22:23] <maxb> That would be a good first step for your use case
[22:27] <robert_ancell> I'm getting "Rejected:<lp.archiveuploader.permission.CannotUploadToPocket object at 0x64ab510>" when I try and upload a package to universe
[22:28] <wgrant> robert_ancell: To which suite are you trying to upload?
[22:31] <robert_ancell> suite?
[22:31] <al-maisan> distro series + pocket
[22:31] <al-maisan> = suite
[22:31] <wgrant> Right.
[22:32] <wgrant> That exception means you're trying to upload somewhere that doesn't make sense.
[22:32] <wgrant> eg. karmic(-release)
[22:32] <wgrant> (the error message should be better, of course.)
[22:32] <robert_ancell> wgrant, uh, I think I know - I'm using a new laptop and I haven't copied my .dput.cf
[22:33] <mwhudson> there's a bug about the crappy error i think
[22:34] <wgrant> There is.
[22:34] <wgrant> Bug #434391
[22:34] <wgrant> Bug #494391
[22:36] <robert_ancell> So how do I find what pocket I am uploading to?
[22:37] <al-maisan> robert_ancell: look at your most recent changelog entry
[22:37] <al-maisan> at the top line
[22:37] <wgrant> "karmic -> Karmic RELEASE
[22:37] <al-maisan> that specifies the suite
[22:37] <wgrant> karmic-updates -> Karmic UPDATES
[22:38] <robert_ancell> right, so the distro series is karmic
[22:38] <robert_ancell> ok, so it's karmic release
[22:38] <wgrant> And an attempt to upload to that does not make sense.
[22:38] <robert_ancell> oh duh
[22:39] <al-maisan> since karmic is not the series under development
[22:39] <robert_ancell> I was previously uploading to a PPA.
[22:40] <robert_ancell> thanks
[23:34] <xteejx> Hey guys, I'm having LP problems. I'm trying to convert bug 311417 to a question, and LP keeps failing with an OOPS, and it has just come up with "Please try again.... problem connecting to LP server"
[23:35] <xteejx> Hmm strange, it's Ok now.... dont worry :)
[23:42] <jkakar> After moaning, complaining and a fair amount of obstinence we've started using merge proposals on the Landscape team.
[23:43] <jkakar> It's been two days and I already love it.  They're SO much better than the last time we looked.  Thanks code hosting team. :)


[14:40] <mcphail> tedg: is there a way I can use ubuntu-app-launch to call gdb on the launched app?
[14:55] <popey> mcphail, wouldn't that need root?
[14:55] <popey> bartbes, tried your patch but it didn't work here. I get a vibrate when i tap "Control" but if I then tap a key (like D) it just echos it, doesn't do "CTRL+D". Am I doing/holding it wrong?
[14:56] <bartbes> hmm, I guess the device osk uses another codepath?
[14:56] <bartbes> that's weird
[14:57] <bartbes> I haven't figured out how to upload to my phone from the vm
[14:58] <mcphail> popey: that's why I'm trying to get it to run "gdb appname" rather than running the app and attaching afterwards :)
[14:59] <bartbes> oh, there's a separate event that can also trigger key presses
[15:01] <MikkoMM> Hi! I must ask from the wiser: I've been making Scope with JavaScript, but I've had no luck with reading the scope's settings. I'm not even sure if it's supported already or not. Has anyone had success with the config and JS-scope?
[15:02] <popey> MikkoMM, ooh, new territory. Maybe poke davidcalle when he's around during the week.
[15:03] <MikkoMM> popey: Thanks, I'll do that!
[15:03] <bartbes> popey: do you happen to know how the osk injects keypresses?
[15:03] <popey> bartbes, I don't, sorry.
[15:04] <popey> you having trouble getting your stuff running on a device?
[15:04] <popey> do you have an armhf "kit" in the sdk?
[15:04] <bartbes> well, I run the sdk in a vm I've barely set up
[15:05] <bartbes> I haven't really spent much time figuring out how to get that to work
[15:22] <popey> bartbes, basically create an armhf kit, that will enable you to build a native click for the phone
[15:22] <popey> https://developer.ubuntu.com/en/apps/sdk/tutorials/click-targets-and-device-kits/ has the basics


[00:06] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4846 Pending binary packages
[00:47] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4846 Diff missing
[01:29] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4846 Generating diffs
[01:30] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4846 Successfully built
[02:07] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4847 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[02:14] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4848 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[03:08] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4847 Pending binary packages
[03:28] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4847 Generating diffs
[03:29] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4847 Pending binary packages
[03:29] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4848 Generating diffs
[03:48] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4847 Successfully built
[06:54] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Preparing packages
[06:54] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[07:56] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Proposed pocket (impish/unity). Ready to build (/:, /: Failed to update local lp:unity cache., impish/Failed, impish/cache., impish/local, impish/lp:unity, impish/to, impish/update)
[07:57] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4693 Ready to build (/:, /: Failed to update local lp:unity cache., focal/Failed, focal/cache., focal/local, focal/lp:unity, focal/to, focal/update). Updates pocket (focal/unity)
[07:57] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2393 Failed to build (xenial/aethercast). Needs rebuild due to higher version at destination (zesty/aethercast). Ready to build (/:, /: Failed to update local lp:aethercast cache., xenial/Failed, xenial/cache., xenial/local, xenial/lp:aethercast, xenial/to, xenial/update, zesty/Failed, zesty/cache., zesty/local, zesty/lp:aethercast, zesty/to, zesty/update)
[08:02] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/3658 Failed to build (disco/nux). Ready to build (/:, /: Failed to update local lp:nux cache., disco/Failed, disco/cache., disco/local, disco/lp:nux, disco/to, disco/update)
[08:06] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/4442 Ready to build (/:, /: Failed to update local lp:bamf cache., focal/Failed, focal/cache., focal/local, focal/lp:bamf, focal/to, focal/update). Successfully built (focal/bamf)
[08:06] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Needs rebuild due to higher version at destination (zesty/aethercast). Ready to build (/:, /: Failed to update local lp:aethercast cache., xenial/Failed, xenial/cache., xenial/isc-dhcp, xenial/local, xenial/lp:aethercast, xenial/to, xenial/update, zesty/Failed, zesty/cache., zesty/isc-dhcp, zesty/local, zesty/lp:aethercast, zesty/to, zesty/update). Successfully built (xenial/aethercast)
[08:41] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/3658 Needs rebuild due to new commits (disco/nux). Ready to build (/:, disco/Failed, disco/cache., disco/local, disco/lp:nux, disco/to, disco/update)
[08:43] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/4442 Needs rebuild due to new commits (focal/bamf). Ready to build (/:, focal/Failed, focal/cache., focal/local, focal/lp:bamf, focal/to, focal/update)
[08:43] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Needs rebuild due to new commits (zesty/aethercast). Ready to build (/:, xenial/Failed, xenial/cache., xenial/isc-dhcp, xenial/local, xenial/lp:aethercast, xenial/to, xenial/update, zesty/Failed, zesty/cache., zesty/isc-dhcp, zesty/local, zesty/lp:aethercast, zesty/to, zesty/update). Successfully built (xenial/aethercast)
[08:53] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Proposed pocket (impish/unity). Ready to build (/:, impish/Failed, impish/cache., impish/local, impish/lp:unity, impish/to, impish/update)
[08:54] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4693 Ready to build (/:, focal/Failed, focal/cache., focal/local, focal/lp:unity, focal/to, focal/update). Updates pocket (focal/unity)
[08:54] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2393 Failed to build (xenial/aethercast). Needs rebuild due to new commits (zesty/aethercast). Ready to build (/:, xenial/Failed, xenial/cache., xenial/local, xenial/lp:aethercast, xenial/to, xenial/update, zesty/Failed, zesty/cache., zesty/local, zesty/lp:aethercast, zesty/to, zesty/update)
[08:59] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/3658 Failed to build (disco/nux). Ready to build (/:, disco/Failed, disco/cache., disco/local, disco/lp:nux, disco/to, disco/update)
[09:03] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/4442 Ready to build (/:, focal/Failed, focal/cache., focal/local, focal/lp:bamf, focal/to, focal/update). Successfully built (focal/bamf)
[09:08] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4848 Successfully built
[09:10] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Diff missing
[09:12] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Generating diffs
[09:13] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Pending binary packages
[09:28] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4848 Pending binary packages
[09:48] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4848 Successfully built
[09:49] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Successfully built
[09:50] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Publishing packages
[10:10] -queuebot:#ubuntu-ci-eng- rikmills, https://bileto.ubuntu.com/#/ticket/4849 Proposed pocket
[17:58] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4850 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[18:01] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4851 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[18:15] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4851 Generating diffs
[18:15] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/4852 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[19:12] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/4852 Uploading build
[19:32] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/4852 Pending binary packages
[19:51] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4850 Uploading build
[19:53] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/4852 Diff missing
[20:02] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/4852 Generating diffs
[20:03] -queuebot:#ubuntu-ci-eng- ahasenack, https://bileto.ubuntu.com/#/ticket/4852 Successfully built
[20:11] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4850 Pending binary packages
[21:51] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4851 Uploading build
[22:12] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4851 Pending binary packages
[22:32] -queuebot:#ubuntu-ci-eng- sergiodj, https://bileto.ubuntu.com/#/ticket/4851 Successfully built


[07:18] <RikMills> santa_: apologies. launchpad/builder were broken most of yesterday, so I gave up trying to get anything done
[08:32] <crydotsnake-M> Hello all!. I have a question.. i really want to Help improving Kubuntu, but i dont really find a starting Point.. could you give me some Tipps?.
[12:37] <mparillo> (1) Help out with the #kubuntu channel. (2) Install the daily ISO (http://cdimage.ubuntu.com/kubuntu/daily-live/current/) use it and report anything unusual here. You may be asked to create a bug report on Kubuntu (Launchpad.net) or KDE (bugs.kde.org). (3) Hang here and look for a call for testers and volunteer. (4) If you have particular talents in coding, system administration, documentation, translations, etc, announce
[12:37] <mparillo> them here and maybe somebody needs a bit of help
[13:14] <BluesKaj> Howdy all
[13:23] <crydotsnake-M> Thank you ! mparillo
[13:24] <crydotsnake-M> How can i edit pages on community.kde.org?
[14:29] <mparillo> I think you need a KDE Identity
[14:29] <mparillo> Login with Phabricator
[14:30] <mparillo> Target URL for me: https://phabricator.kde.org/oauthserver/auth/?scopes%5B0%5D=whoami&scopes%5B1%5D=offline_access&state=a050fbac809f7cf3cac472f2b7be3372&scope=whoami&response_type=code&approval_prompt=auto&redirect_uri=https%3A%2F%2Fcommunity.kde.org%2FSpecial%3APhabricatorLogin%2Fcallback&client_id=PHID-OASC-tndrk63hnqw4rq3y4zjm
[14:31] <mparillo> Probably different for you, so look for the Login with Phabricator in the right hand navigation.
[14:34] <RikMills> so many things are broken for building in the archive!
[14:34]  * RikMills give up for a while
[15:47] <santa_> good afternoon
[15:47] <santa_> RikMills: ok, no problem, can we see a few easy things now?
[15:47] <RikMills> santa_: sure
[15:48] <santa_> ok, FYI I have fixed yesterday one of my servers for the i386 drop
[15:49] <santa_> I'm going to fix the other one now and start with test rebuilds wo would be nice to get everything right in git repos
[15:49] <santa_> s/wo/so/
[15:51] <santa_> RikMills: ok, so first of all it would be nice to get the plasma .4 in the _archive branches
[15:51] <santa_> I'm here @ .3
[15:52] <RikMills> I thought I pushed. maybe just to the staging.....
[15:52] <santa_> yeah, the staging is right
[15:52] <santa_> the _staging branch I mean
[15:52] <santa_> but not _archive
[15:53] <RikMills> pushing
[15:54] <santa_> ok, another one: kimageformats, no-change rebuild made by you
[15:54] <santa_> and I think they were a few apps not in sync, let me check...
[15:56] <santa_> hmm you already did marble
[15:56] <RikMills> yesw
[15:56] <RikMills> yes
[15:57] <santa_> ok I will fix area51 now so I will start fresh with test rebuilds, I plan to build the _staging branches @ groomlake and the _archive branches @ area51
[15:58] <RikMills> be warned that there is breakage in focal proposed for building some things
[15:58] <santa_> oh, how is that?
[16:00] <RikMills> gdk-pixbuf had a binary deleted
[16:00] <RikMills> make a mice chain of things from that to vlc to phonon backend to knotificationconfig-dev to maybe other things fail to install
[16:01] <RikMills> mice chain?
[16:01] <RikMills> nice chain!
[16:01] <RikMills> made the ktp-* things you wanted uploaded FTBFS
[16:02] <santa_> hmm
[16:02] <santa_> ok, well let's see how that affects the rebuilds
[16:03] <RikMills> a lot should be ok. just saying
[16:04] <santa_> the kimeageformats tag is missing
[16:04] <RikMills> kdeconnect 1.4 is out :)
[16:04] <santa_> aha
[16:05] <RikMills> was a scripted rebuild without the tooling, so no automatic tag
[16:05] <santa_> oh, ok
[16:19] <crydotsnake-M> Thanks mparillo
[17:08] <santa_> RikMills: ok, more stuff, KA
[17:09] <santa_> I would like to fix that fix to not use float
[17:10] <RikMills> go ahead
[17:10] <santa_> wrt branch managing I plan to fix this in the 2.3 branch, make a new alpha package from there, merge 2.3 into master and then release 2.3 with whatever we have in master
[17:12] <santa_> * and then release 2.3 beta 1 with whatever we have in master
[17:12] <RikMills> ok :)
[18:36] <santa_> RikMills: changes pushed to 2.3 I haven't tested the 100% of things which could be tested but it seems it could work
[18:38] <santa_> RikMills: so could you do a quick test? if it works for you I will proceed with the package, then I will merge into master to prepare 2.3-beta1
[18:38] <santa_> (which I would like to test doing fw 5.65)
[18:39] <RikMills> doing
[18:43] <RikMills> santa_: seem to switch dir depending on version ok here on a VERY quick test
[18:44] <santa_> RikMills: ack
[18:44] <RikMills> if an issue crops up can fix as we go, but dowloading tars and gbp seems ok
[18:44] <santa_> ok, I will proceed with the package then
[19:31] <santa_> RikMills: hmm, what happenned exactly with gdk-pixbuf?
[19:34] <RikMills> santa_: vorlon deleted one of the binaries on all arches to break a circular build dependency for something
[19:36] <RikMills> santa_: that got left overnight USA time, breaking lots of other things
[19:36] <RikMills> then a short while ago, he copied the binaries back
[19:39] <santa_> RikMills: what's the name of the removed binary?
[19:40] <RikMills> santa_: it was libgdk-pixbuf2.0-common 2.40.0+dfsg-1ubuntu1
[19:45] <RikMills> https://launchpad.net/ubuntu/focal/armhf/libgdk-pixbuf2.0-common
[19:46] <RikMills> Deleted 14 hours ago by Steve Langasek
[19:46] <RikMills> Hack around gdk-pixbuf circular build-dep
[19:46] <RikMills> Published 2 hours ago
[19:46] <RikMills> same history for all arches
[19:51] <santa_> RikMills: thanks for the info, so I guess as soon as my mirror gets the package the builds are going to be ok
[19:53] <RikMills> hopefully
[20:02] <santa_> ok, so package published and everything merged into master
[20:02] <santa_> tomorrow or so I plan to do a few changes in master and test them doing the 5.65 release
[20:03] <santa_> specifically the branch checking removal
[20:07] <RikMills> might have to temporarily drop the libgit2 build dep for ktexteditor in a weeks time. the libgit2 soname transition seems to not be going anywhere in proposed at the moment
[20:07] <santa_> aha
[20:09] <RikMills> or maybe drop it in staging and test the consequences? I did that in my ppa, and could not see much impact of say kate
[20:10] <santa_> probably it's not the most important feature there
[20:10] <RikMills> indeed
[20:10] <santa_> just don't forget to add it back ;)
[20:11] <RikMills> that is the thing!