[02:10] <facundobatista> Hi all! I'm failing to be able to do a "bzr pull" on launchpad projects, I got a "ssh_exchange_identification: Connection closed by remote host"
[02:11] <facundobatista> is launchpad all ok?
[02:11] <jose> facundobatista: I'm checking with the sysadmins at the moment, they're internally checking
[02:11] <facundobatista> jose, thanks
[02:25] <dobey> facundobatista: you can try ssh -vv bazaar.launchpad.net btw
[02:25] <dobey> bzr info and such seem to work ok here for me anyway
[02:25] <jose> it started working again
[02:26] <facundobatista> yes, now it works
[02:26] <facundobatista> dobey, jose, gracias!
[07:45] <dpm> hi wgrant, a LP question for you if you're around. Is there a way to set up a project, so that when a new MP is submitted the maintainer team is automatically added as a reviewer? I've noticed when I submit a MP myself, that happens, but not when external contributors submit MPs
[07:46] <wgrant> dpm: It depends on how you've configured the reviewer of the target branch.
[07:47] <wgrant> You'll see a "Set branch reviewer" link on the right
[07:47]  * dpm looks
[07:50] <dpm> wgrant, I'm looking at calendar trunk (which is always our target), and the reviewer there is already set to ubuntu-calendar-dev, which is the maintainer team. However, it seems only on the MPs I submitted ubuntu-calendar-dev was explicitly added to the list of reviewers. For all the other MPs I had to set it manually - the context here is that we use a launchpadlib script to track core app reviews, and it will only list them via the getRequestedReviews()
[07:50] <dpm> if the team is in the reviewers list
[07:58] <dpm> Another example is https://code.launchpad.net/reminders-app/+activereviews - the first MP has reminders-app-dev in the reviewers list, whereas the second doesn't
[08:05] <lanoxx> hello, I would like to request a maintainer change for the package tilda
[08:06] <czajkowski> lanoxx: if you file a question they can help you
[08:07] <czajkowski> lanoxx: https://answers.launchpad.net/launchpad/+addquestion
[08:08] <lanoxx> czajkowski, https://answers.launchpad.net/launchpad/+question/247073
[08:13] <wgrant> dpm: Oh. Once a member of the team reviews it, the team review request will be replaced with a vote from that person. Because there's no need for a review from that team.
[08:15] <dpm> wgrant, oh bummer, so effectively that means we cannot track "Needs review" branches in our script? As the initial review request for the team will disappear as soon as a team member sends a vote?
[08:15] <wgrant> dpm: Why not use branch.getMergeProposals?
[08:16] <wgrant> getRequestedReviews is a method to get the requested reviews.
[08:16] <dpm> wgrant, ah, nice one. I was using team.getMergeProposals and that obviously didn't return anything. I'll try branch.getMergeProposals
[08:19] <dpm> wgrant, do you know where I can find any snippets to get hold of a branch using launchpadlib?
[08:20] <wgrant> dpm: lp.branches.getByUrl(url='lp:blahblahblah')
[08:21] <dpm> cool, thanks!
[08:23] <StevenK> Oh god, it exists
[08:23] <StevenK> bzr: ERROR: Parent not accessible given base "bzr+ssh://bazaar.launchpad.net/+branch/blahblahblah/" and relative path "../../../~gbancroft-canonical/blahblahblah/design-blog-theme/"
[08:24] <czajkowski> :o
[08:26] <StevenK> I think a project was renamed and then deactivated rather than just deactivated
[08:29] <wgrant> StevenK: Not deactivated, just with a weird stacked_on_location
[08:30] <StevenK> Hah
[15:12] <dajhorn> I have a PPA that is sporadically failing with a "State: Chroot problem" error because util-linux is failing to install.  Is this the right place to report it?
[15:13] <cjwatson> Maybe.  Which PPA?
[15:13] <dajhorn> cjwatson, Here is an example:  https://launchpad.net/~zfs-native/+archive/staging/+build/5914177/+files/buildlog_ubuntu-trusty-amd64.spl-linux_0.6.2-2.1~trusty~10.gbpedccf5_CHROOTWAIT.txt.gz
[15:14] <cjwatson> blink
[15:15] <dajhorn> cjwatson, the glitch began yesterday.  I think that the pertinent line is:  udev depends on util-linux (>= 2.16); however: Package util-linux is not configured yet.
[15:15] <cjwatson> infinity: ^- Could you please have a look?  From the timing it seems like it must be something to do with your util-linux upload, but I can't see what
[15:27] <infinity> cjwatson: That looks a lot like an apt bug, but not sure how.
[15:28] <infinity> The simple workaround is probably just to refresh the chroots.
[15:28] <infinity> But...
[15:31] <dajhorn> infinity, feel free to kick over anything in those PPAs (if you can do that as an admin).   I will be /away for an hour or two.  (Thanks.)
[15:36] <cjwatson> dajhorn: thanks very much for mentioning this, I think we'll need to get an urgent fix into trusty - it affects upgrades of minimal saucy chroots to trusty
[18:19] <zyga> hi, what is the frequency of publisher runs that copies bult binaries into a PPA archive
[18:19] <zyga> https://code.launchpad.net/~checkbox-dev/+archive/ppa/+packages
[18:19] <zyga> this archive has some packages that built over an hour ago but are still not published
[18:19] <wgrant> It's probably fallout from the firewall issues earlier.
[18:19] <wgrant> Let me see.
[18:20] <zyga> thanks
[18:34] <zyga> wgrant: any luck?
[18:34] <wgrant> zyga: It's publishing now, but there's a bit of a backlog.
[18:35] <zyga> wgrant: ok, thanks for your help :-)
[18:35] <wgrant> np
[21:05] <AtnNn> Hello. What could cause this error in a launchpad build? unmet dependencies: npm : Depends: node-gyp (>= 0.10.9) but it is not going to be installed
[21:05] <AtnNn> I can install node-gyp 0.10.10 on trusty just fine locally
[21:06] <dobey> the dependency not being installable
[21:07] <dobey> maybe it conflicts with something else that's also trying to be installed?
[21:09] <AtnNn> dobey: all the dependencies install correctly on my trusty schroot. and the same package builds fine for saucy on launchpad. Is there a way I can reproduce the launchpad build environment locally?
[21:11] <dobey> use sbuild, but it won't be exactly the same; but it's the closest you can get
[21:15] <AtnNn> that's what I used.
[21:19] <dobey> what's the url to the build log?
[21:19] <AtnNn> https://launchpadlibrarian.net/172971888/buildlog_ubuntu-trusty-amd64.rethinkdb_1.12.2-0ubuntu1~trusty_FAILEDTOBUILD.txt.gz
[21:22] <dobey> if i run that apt-get command on trusty here, it fails with the same error
[21:24] <dobey> libv8-dev and node-gyp conflict
[21:25] <dobey> not sure why, but that's what is causing the issue
[21:27] <AtnNn> dobey: thanks for trying. I can now get the error too. I had not run that exact apt-get command because debuild did not report any missing dependencies