/srv/irclogs.ubuntu.com/2018/01/26/#launchpad.txt

=== ePierre_ is now known as ePierre
alexpHello everybody. I am aware of the recent build farm issues, but we have a build stuck for a couple of days now. It is not urgent, so we can live with this for now. Still, is there a page somewhere to monitor how deep the build queue is? It would help us getting an idea about the timelines of these builds.10:52
alexpI'll answer myself, https://launchpad.net/builders. Have a nice day everybody.10:56
patdk-lapwhen will launchpad get fixed? my packages have been bouncing between 2 to 6 hours, for the last 20hours16:00
cjwatsonpatdk-lap: It's not currently particularly broken (aside from not having Spectre-mitigation microcode for a chunk of our x86 farm, which is in the hands of Intel and AMD), just a longish queue.  I can score up individual builds if they're urgent.16:04
cjwatsonYour build times keep jumping up because new builds arrive with a higher score and jump the queue.16:06
cjwatsonWhich happens when we can't quite service the rate of incoming builds quickly enough.16:07
patdk-lapya, just attempting to get this dovecot cve patched, but ppa's are kindof low priority so they take awhile16:34
patdk-lapI don't mind 12hour waits, but 24 is heh16:34
patdk-laptimes like this I should just buildup my own internal systems to do it, but it is a lot of overhead16:35
cjwatsonpatdk-lap: like I say, happy to score up things people are actually waiting for; just need to know the build URLs16:36
patdk-laphttps://launchpad.net/~patrickdk/+archive/ubuntu/testing/+packages16:36
patdk-lapjust waiting on the amd64's16:36
cjwatsonpatdk-lap: all building now16:39
patdk-lapnice :)16:40
patdk-laponce I test them and verify, I'll copy don't rebuild to production repo16:40
patdk-lapthat shouldn't cause a wait again so all should be good16:40
cjwatsonindeed16:41
patdk-lapthink the only other time I had this issue was during an lts release16:42
patdk-lapif it wasn't for that auth memleak cve issue I wouldn't really mind at all16:43
cjwatsonYes, pre-Spectre we hadn't had much of a queue for a while.16:45
patdk-lapah ya, I didn't think of that, wonder how much the builders slowed down from their patches16:48
patdk-laplooks good, a new unit test failed for xenial, but otherwise fine, xenial can wait16:50
doublehpin short, I can reach https://login.ubuntu.com/ and i am said to be logged in, but when I visit https://bugs.launchpad.net/ubuntu/+source/libtasn1-6/+filebug/4ffd812c-02c3-11e8-9dd0-d485646cd9a4? i get "Oops!                    Sorry, something just went wrong in Launchpad.                             We’ve recorded what happened,           and we’ll fix it as soon as possible.           Apologies for the inconvenience.                    18:39
ubot5Ubuntu bug 4 in Launchpad itself "Importing finished po doesn't change progressbar" [Medium,Fix released]18:39
cjwatsondoublehp: Hopefully you got an OOPS ID?  If so, please quote it19:11
doublehpcjwatson: ... was my line trunckated ?19:12
doublehp(Error ID:           OOPS-99109a4ff4a3fe6a44f99c058fff1690)19:12
ubot5https://oops.canonical.com/?oopsid=OOPS-99109a4ff4a3fe6a44f99c058fff169019:12
cjwatsonApparently so19:12
cjwatsonOK, just a minute19:13
cjwatsondoublehp: fixed now, sorry about that.  you ran into https://bugs.launchpad.net/launchpad/+bug/1607242 due to an old comment from your email address that we imported from another bug tracker.19:23
ubot5Ubuntu bug 1607242 in Launchpad itself "Logging into a placeholder person OOPSes if email address already on another person" [Critical,Triaged]19:23
doublehpcjwatson: i will eat soon; i will be back in 30-45mn; I will go to bed in 90-120mn - after I left, either send me a memo via memoserv, or an email benoit@demaine.info19:24
cjwatsondoublehp: uh, there should be nothing more to do, just try the login again19:24
doublehpok ...19:24
cjwatsonlike I say your account should be fixed now19:24
doublehpfirst time i use that site, got bugs ... will i receive email notifications when people update my report ?19:29
cjwatsonYes19:29
doublehpthanks, bye19:29
cjwatsonnp19:29
jfmcarreiraheyyy guys21:37
jfmcarreirawhat is the version of debhelper available on xenial?21:37
nacc!info debhelper xenial21:40
ubot5debhelper (source: debhelper): helper programs for debian/rules. In component main, is optional. Version 9.20160115ubuntu3 (xenial), package size 721 kB, installed size 1300 kB21:40
naccjfmcarreira: there is also a more recent one in xenial-backports21:40
jfmcarreiranacc: i have debhelper (>= 9.0.0), and it is not being installed21:45
naccjfmcarreira: where? do you have logs21:46
naccjfmcarreira: it might mean you have other deps that break it21:46
jfmcarreirahttps://launchpadlibrarian.net/354633756/buildlog.txt.gz21:48
jfmcarreiranacc: as in the past I wanted version 10 I copied from backports to my ppa. but it should not be a problem. it could also use version 1021:49
naccjfmcarreira: have you tried to reproduce it in a chdist?21:50
naccjfmcarreira: or build it locally to see?21:50
jfmcarreiradebuild -uc -us -b??21:50
naccjfmcarreira: with -backports enabled, presumably21:51
nacci'd use an sbuild or a lxd to do it21:51
jfmcarreirawhats the command to auto download source?21:57
jfmcarreiratrying to use sbuild21:57
naccjfmcarreira: how do you mean?21:57
jfmcarreirathe comand to download the source based on info on debian folder21:58
naccjfmcarreira: if you have the debian folder, you have the source package already?21:59
naccjfmcarreira: sorry, i'm not following21:59
jfmcarreirauscan22:00
jfmcarreirai mean uscan22:00
jfmcarreirafetch the source doe22:00
jfmcarreiracode*22:00
jfmcarreirasbuild requires22:00
naccuscan and uupdate22:00
naccthey get the orig tarballs22:00
jfmcarreiranacc: yeah thats it. sbuild required it22:00
naccjfmcarreira: you can also just download the files from the ppa22:00
jfmcarreiranacc: done.22:01
jfmcarreiranow i get an error with debuild: "dh_install: Cannot find (any matches for) "usr/lib/libPlaYUVerLib.so*" (tried in "." and "debian/tmp")" with the pattern because it puts in usr/lib/x86_64-linux-gnu/libPlaYUVerLib.so*22:02
naccjfmcarreira: wasn't that the error you got before?22:03
jfmcarreirayeah because before i had usr/lib/*/libPlaYUVerLib.so*22:04
jfmcarreiraand I removed the extra "/*"22:04
jfmcarreiracant run sbuild22:05
jfmcarreirahttp://paste.ubuntu.com/26467048/22:05
naccjfmcarreira: how are you invoking it?22:06
jfmcarreirasbuild only22:06
naccjfmcarreira: so you are in the source package directory?22:07
jfmcarreirayeah and i ran uscan and it downloaded the source tar to the directory above22:08
naccjfmcarreira: sorry, i'm confused; have you used sbuild before?22:09
jfmcarreirai ran uscan and then sbuild22:09
naccjfmcarreira: you need to give  it a source package directory. not the debian/ and not just the upstream22:09
jfmcarreirafirst time using it22:09
naccjfmcarreira: yeah, that's not quite how you use it22:09
naccjfmcarreira: do you konw what a debian source package is?22:09
jfmcarreiranot really... it is a combination of source files and control files to describe the pkg and the build?22:10
naccjfmcarreira: right, basically, it's an upstream orig tarball(s), untarred, and a debian tarball (untarred)22:10
naccjfmcarreira: so you need to be in that untarred state to build it, or use the dsc22:11
jfmcarreirai have this playuver-0.18.2.tar.gz and playuver_0.18.2-2.debian.tar.xz which were downloaded automatically from github.. at least the first22:12
jfmcarreirathis file is empty playuver_0.18.2-2.debian.tar.xz22:13
naccjfmcarreira: well, it certinaly shouldn't be empty22:13
jfmcarreirahow should  i fill it?22:14
jfmcarreirai can run debuild to create a source package22:14
naccjfmcarreira: this might be more of a rathole than is nencessary22:14
naccjfmcarreira: if you can build a source package, pass that source pacakge to sbuild22:14
jfmcarreirawhere should i be to build a src pkg?22:14
jfmcarreirasource folder? debian folder?22:15
naccjfmcarreira: you shulld be in the untarred source packages root directory22:16
jfmcarreirawith the debian folder?22:17
jfmcarreirado i need to be in the src folder and have .orig above it?22:19
naccjfmcarreira: it's better to be specific here22:19
naccsrc might mean a directory called 'src' or you might mean 'source'22:19
jfmcarreirai mean having the source code folder with a debian folder inside22:20
naccyou should be in a directory containing the uncompressed orig tarball, a debian/ and the .orig tarball should be in the parent directory, in my experience22:20
jfmcarreiranow i tried inside the debian folder with the source in ../XXX.orig22:20
jfmcarreiranow it created the .changes, .build, .dsc22:21
jfmcarreirawhat do i do with it?22:21
naccyou should pass the .dsc to sbuild22:22
=== newell is now known as Guest48853
jfmcarreiranacc: i do need to create a chroot right?22:31
naccjfmcarreira: yeah with mk-sbuild22:34
jfmcarreirasbuild-createchroot --include=eatmydata,ccache,gnupg unstable /local/jcarreira.it/unstable-amd64-sbuild http://deb.debian.org/debian22:34
naccjfmcarreira: well, if you want to build a debian unstable one...22:35
naccjfmcarreira: but i thought you were building xenial?22:35
jfmcarreira i do22:35
jfmcarreiraxenial and bionic and other debian distro22:35
naccjfmcarreira: those are ubuntu22:36
naccjfmcarreira: not debian22:36
jfmcarreiranacc: short term goal are ubuntu xenial and bionic cause are the ones i use in my research lab. but I wanted to deploy it to as much distros ass possible22:38
jfmcarreirathe xenial problem were raised becasue of the launchpad build recipes22:38
naccjfmcarreira: i don't have any context into what you are doing, but if this is an applilcation, why ont build a snap?22:39
jfmcarreiranacc: why snap? why not debian packages? to be honest I am not big fan of snap22:40
naccjfmcarreira: because it avoids these issues? :)22:41
naccjfmcarreira: and debian packages only work on debia-based distros; snaps are cross-distro22:41
jfmcarreiranacc: the issue here seems quiet stupid. it is a problem with a dependency which exists on xenial22:41
naccjfmcarreira: it's something else, most likely22:41
naccjfmcarreira: for whatever reason, due to other dependencies, most likely, you are not able to install debhelper whenn buildig your srcpkg22:42
naccjfmcarreira: but hey, in a snap you don't need debhelper at all22:42
jfmcarreiranacc: based on that it makes sense to deploy a snap package. but i would like to be able to deploy debian pkgs for xenial and bionic (next LTS) as I need to have daily builds for it22:42
naccjfmcarreira: like i said, if this is an application, snaps feel like a natural fit, esp. if you aren't already committed to doing debs (i mean, you don't have a xeniall build yet)22:42
naccjfmcarreira: you cann do daily builds with sanps22:43
nacc*snaps22:43
naccthat's waht 'edge' is for22:43
jfmcarreiranacc: i have xenial build for a long time. but in the past days i tried to split the pkgs into multiple apps and thats what raised problems22:43
naccjfmcarreira: oh i didn't know that22:44
naccjfmcarreira: sorry, i need to refocus on some other stuff before i eod22:44
naccjfmcarreira: but i'd seriously look at snaps. you'd then only have one versionn (well, 4 if you do all for tracks) to worry about everywhere22:45
cjwatson922:45
cjwatsonoops, sorry22:45
jfmcarreiranacc: ok thanks22:46

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!