=== FourDollars_ is now known as FourDollars
=== marcoceppi_ is now known as marcoceppi
=== HyperCupid is now known as chaos7theory
=== rsalveti_ is now known as rsalveti
=== Ursinha__ is now known as Ursinha_
=== plars-holiday is now known as plars
pittiGood morning06:18
=== mariogrip_ is now known as mariogrip
=== mariogrip_ is now known as mariogrip
=== rsalveti_ is now known as rsalveti
dholbachgood morning08:35
seb128hey dholbach08:41
dholbachhi seb12808:43
seb128dholbach, congrats for the Cc election ;-)08:45
dholbachthanks :)08:45
=== psivaa-afk is now known as psivaa
=== davmor2_ is now known as davmor2
zequenceI've uploaded a package (ubuntustudio-meta), but it doesn't seem to be building. Where can I see errors for things like that?09:09
sladenzequence: https://launchpad.net/ubuntu/+source/ubuntustudio-meta  there was an upload 48 hours ago; is there a newer one aswell?09:11
zequencesladen: The source is there, but no binaries09:13
sladenzequence: (if) it is the 0.143, buildlog will be here  https://launchpad.net/ubuntu/+source/ubuntustudio-meta/0.143/+build/835268109:15
=== larsu_ is now known as larsu
sladenzequence: but it claims to have built; in which case perhaps you need an archive admin to look into it09:16
zequencesladen: Right. Thanks!09:17
Mirvporters: bos01-ppc64el-027 hanged on build (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+build/8357535), will cancel and retry09:18
Mirvhmm, I didn't notice it in the snippet but looks like it was ppc64el ICE actually that then didn't really fail (the build status remained building)? https://launchpadlibrarian.net/227978020/buildlog_ubuntu-xenial-ppc64el.qtscript-opensource-src_5.5.1%2Bdfsg-2build1_CANCELLING.txt.gz < doko09:20
dokoThe bug is not reproducible, so it is likely a hardware or OS problem.09:21
dokojust retry09:21
Mirvright, so it says09:23
=== cpaelzer__ is now known as cpaelzer
=== mariogrip_ is now known as mariogrip
=== ahasenac` is now known as ahasenack
=== vrruiz_ is now known as rvr
cjwatsonzequence: it's in NEW, awaiting review12:46
cjwatsonor was12:46
cjwatsonzequence: appears to have been accepted not long before you asked about it12:47
ginggsdidrocks (or anyone else willing to sponsor): suitesparse ready for transition, please remove fop from -proposed, LP: #151898513:29
ubottuLaunchpad bug 1518985 in suitesparse (Ubuntu) "Please merge suitesparse 1:4.4.5-2 (main) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/151898513:29
didrocksginggs: good, removing fop then, one sec13:31
didrocksginggs: done, just wait for a publisher cycle to show up13:33
ginggsdidrocks: thanks, are you sponsoring my suitesparse merge as well?13:38
didrocksginggs: yeah, I'll have a look shortly13:40
ginggsdidrocks: cool, thanks again!13:40
didrocksginggs: thanks to *you*! :)13:41
pitticjwatson: is there a LP redirect that would get me the latest .dsc for a given package?14:03
lamontpitti: you'd have to define "latest" (highest version? most recently uplaoded? published? etc) -- I too would be interested in the answer, but I suspect it's "no, you have to use the api"14:05
pittilamont: highest version, yes14:05
pittiwell, it's not too hard for me to figure out the version, but if there was some kind of /+latest.dsc redirect I wouldn't have to14:06
xnoxwhy is $ pull-debian-source -> not working at all?! =(14:17
xnoxpitti, don't think so, the thing that is shown as "latest" is any latest upload in the ui, rather than highest.14:17
* xnox looks at stuff.14:18
xnoxpitti, i think there was a magic url, into which one could plugin e.g. hello_1.2-3.dsc and it would download it, obviously one would have to know the full filename on wants to fetch.14:20
pittixnox: ok, thanks; nevermind, it's fine14:21
pittichdist --data-dir data/chdist grep-dctrl-sources xenial-amd64 -n -s Package,Version -F Testsuite autopkgtest|paste -sd '  \n' | sed 's/ [0-9]\+:/ /'14:21
pittithat pretty much gives me what I want -- a list of all sources and their versions which have a test14:21
pittiand with the version I can use https://launchpad.net/ubuntu/+archive/primary/+files/$src_$ver.dsc14:23
xnoxaha https://github.com/xnox/apt-mirror/blob/master/apt-mirror-librarian 'https://launchpad.net/ubuntu/+archive/primary/+files/' + debfile but yeah, that's to actually download any .dsc from librarian. (possibly pre publish into the apt archive, but not sure)14:23
xnoxthat's the url i was thinking about.14:23
juliankI can't reach launchpad.net (  - am I the only one?14:24
JanCworks for me14:25
juliankSeems I have issues here14:25
JanCwait, I'm on .22314:27
JanChttps:// gives me an error page from the reverse proxy14:28
JanC(for obvious reasons)14:29
xnoxmardy, would the bug #1521226 be of interest to you?15:10
ubottubug 1521226 in libaccounts-glib (Ubuntu) "FTBFS on all arches in xenial" [High,Confirmed] https://launchpad.net/bugs/152122615:10
mardyxnox: vaguely ;-)15:10
* mardy tries to hide15:10
xnoxmardy, it fails on -Wall -Werror stuff with something rather, new glib, gibberish =)15:11
xnoxerror: 'g_simple_async_result_propagate_error' is deprecated et.al.15:11
xnoxmaybe disabling -werror would be enough for now. or maybe you are up for porting things to the "new" apis.15:11
mardyxnox: ah, I can't tell you how much I love GLib deprecation policies :-)15:11
seb128mardy, what an idea to build with Werror15:15
seb128mardy, at least use -Wno-error=deprecated-declarations ;-)15:15
mardyseb128: actually, you are right, better get rid of Werror in the first place15:16
mardyseb128: and I'll add G_GNUC_BEGIN_IGNORE_DEPRECATIONS in the right places15:16
Mirvxnox: if you don't mind, ignore your fcitx-qt5 sync's problems and let me upload a no-changes rebuild as part of the Qt 5.5 landing this week15:23
xnoxMirv, i've synced it for very much different reasons. The sync is successful, the failures on power with respect to libxkbcommon are odd, given that libxkbcommon did not change since wily.15:26
xnoxMirv, that new version has corrected symbols for extra architectures.15:27
Mirvxnox: yes, I know the problem and that's why it wouldn't need now any changes after I land a synced Qt 5.5 in. it will need a rebuild however since it uses private symbols. the rebuild is already building at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+packages15:27
Mirvxnox: it's nice it has the symbol updates since I had the older version manually patched before your upload in that PPA15:28
xnoxMirv, ah cool, thanks for explaining.15:28
=== Ursinha_ is now known as Ursinha
=== balloons_ is now known as balloons
juliankmvo: 1.1.3 is visible on Launchpad now16:13
=== jdstrand_ is now known as jdstrand
mvojuliank: lots go then16:16
juliankThe APT 1.1 Ubuntu party starts :)16:16
juliankThanks to pitti for already merging the goplay nmu16:17
pittijuliank: it wasn't actually a real merge; I synced, then found that weird gcc error, then uploaded a workaround16:18
juliankpitti: Right, thanks anyway :)16:19
juliankppc64el is a strange beast16:19
juliankWe have an even more crazy gcc workaround in apt: http://anonscm.debian.org/cgit/apt/apt.git/commit/?id=0300f0077af832e87beb290f26b13404cab81fd316:20
mvojuliank: apt and libept are synced now, weeeeeeee16:42
juliankmvo: Great. python-apt can be synced  as well16:43
mvojuliank: done, woah16:43
mvojuliank: I'm so excited!16:43
=== ben is now known as ben___
Laneyapt is synced?16:44
ricotzbetter don't break the world ;P16:44
davmor2just the rest of the universe ;)16:45
ogra_who needs apt ... its a snappy future !16:45
* davmor2 snaps his fingers....computer is just sat there doing nothing. /me thinks ogra_ lies16:46
jamespagecjwatson, should have your ubuntu-repository-cache MP landed shortly - the tests where failing due to changes in Juju and the testing framework for the charms17:06
shadeslayerdoko: ping17:24
shadeslayerdoko: Is packagekit being finally updated in Xenial?17:24
juliankshadeslayer: PackageKit definitely needs to be merged soon for the APT transition at least.17:40
juliankThe first PackageKit to support APT 1.1 is 1.0.1117:41
dobeypitti: ping. you around? need a manual ack on some autopkgtest issues17:42
zequencecjwatson: Didn't realize the packages go through review at this stage in development. They usually get published so quickly.17:52
seb128juliank, packagekit 1.0 was merged and got deleted since we need somebody to port aptdaemon for the api changes first, and somebody to update click to not use the packagekit plugin api since that was removed17:54
seb128mvo started on the click work but he seems to busy to land it and nobody else knows click enough/has slots for it17:54
shadeslayerjuliank: I see18:17
shadeslayerjuliank: I need it for muon in the next Kubuntu release too18:18
=== sforshee` is now known as sforshee
smoserhey. barry can you verify or suggest work around?  it seems that: http_proxy=http://.... pip install something18:43
smoseron trusty will just not work18:43
smoseri think its related to https://github.com/shazow/urllib3/issues/42218:44
barrysmoser: does it work in xenial?18:44
smoseryes. and vivid18:44
smoseri'm just kind of surprised such a thing has lasted so long.18:45
barrysmoser: i can't remember what the state of backports/srus are for the pip stack :/18:45
barrysmoser: this seems familiar, but i don't remember the details18:46
smosertox uses pip from the system ?18:46
barrysmoser: i think it may depend on whether sitepackages=true in your tox.ini18:46
barrywell, maybe not18:47
barrytox probably uses the system virtualenv, which uses the system pip18:47
* barry can't understand why https://www.google.com gives an ssl connection error, but only on one fully up-to-date xenial machine18:48
barryall other https sites seem to work too18:48
smoserbarry, ok. so it getting python-virtualenv from vivid (python-virtualenv_1.11.6+ds-1_all.deb) fixes it for me.18:55
smoseri guess virtualenv has an embedded pip that it uses18:55
smoserhm.. or  maybe not as i dont see it.18:56
juliankmvo: What's the plan with PackageKit and APT 1.1? That needs 1.0.11 or a backport.  seb12 8 wrote "we need somebody to port aptdaemon for the api changes first, and somebody to update click to not use the packagekit plugin api since that was removed"19:06
infinitymvo: I may be late to the party here, but what was wrong with parsing /etc/lsb-release?19:09
juliankinfinity: You're really late ;)19:10
infinityjuliank: Figured. :P19:11
infinityjuliank: I'm assuming (well, hoping) there was also discussion about formalizing CODENAME in the os-release spec, so we're not using a distro-specific extention forever?19:12
juliankWill the auto-dep-wait stuff automatically be "un"waited? apt 1.1.3 has been built and is pending publications, and python-apt and libept are in dep-wait waiting for it19:12
infinityjuliank: Yeah, it'll unwait once the deps are available.  apt's still in NEW, unless someone accepted it when I wasn't looking.19:12
juliankI at least don't find any mention of NEW on launchpad19:13
infinityI do. :P19:14
juliankOh yeah, on the right side19:14
juliankAnnoyingly, once libept is built, it will also be NEW again19:15
julianks/ again//19:15
infinityNot a big deal.19:16
infinityI'll give libaptwhatever a quick once-over and get the ball rolling.19:16
infinityThanks for proper build-deps, BTW.19:16
infinitySince I'm doing an out-of-archive bootstrap right now, it's much appreciated.19:16
juliankWhich proper build deps ?19:16
infinityAs in, you're dep-waiting on the new apt, rather than counting on upload timing to get it right.19:17
infinitySo I can't build in the wrong order by accident.19:17
juliankinfinity: I bootstrapped that in Debian experimental, so the deps were needed otherwise the packages would have built with unstable APT :)19:18
smoseranyone else see this, or is it just lucky me19:20
smoser https://bugs.launchpad.net/ubuntu/+source/unity/+bug/152130219:20
ubottuLaunchpad bug 1521302 in unity (Ubuntu) "gnome-terminal maximize than un-maximize behaves odd" [Undecided,New]19:20
stgraberbdmurray: hmm, how comes that as a coredev working for Canonical I don't have access to crash reports on errors.ubuntu.com?20:12
stgraberbdmurray: I'm being told I'm not in the right group when I go to https://errors.ubuntu.com/problem/9d8b1bc865eba0604b89ca1f7a24f0a1a0186290 and after I do SSO auth20:13
dobeystgraber: are you in ~ubuntu-bug-control?20:13
stgraberpretty sure I am, yes20:16
dobeyyeah, that's not it20:17
dobeyi can see that link, so it's some group i'm in, at least :)20:18
dobeyand looking at my teams list, i have no idea which one it'd be20:23
yofeldobey, stgraber: AFAIK you need to be in https://launchpad.net/~error-tracker-access20:36
dobeyyofel: that doesn't exist20:36
yofeldobey: huh? The team does exist, I vaguely remember there being an email that you should apply for that to get access when the tracker was initially set up20:37
dobeyyofel: well launchpad gives a 404, and i can't possibly be a member of it, and not be able to see it20:38
yofelgood point..20:38
Unit193https://lists.ubuntu.com/archives/ubuntu-devel/2012-June/035321.html Heh.20:39
bdmurraystgraber: it doesn't look like you are in error-tracker-access20:48
stgraberbdmurray: can you add me? I sure used to have access to that stuff back in the days ;)20:49
bdmurraystgraber: fixed now20:49
dobeyso confused20:50
stgraberdobey: no idea why you have access though :)20:52
dobeyor why trying to view that team gives me a 40420:53
stgraberit's a private team20:53
stgraberso that part's normal20:53
stgraber(and you're not a member of it, just checked)20:53
dobeyprivate private then i guess20:53
mvoinfinity: lsb-release> ogra_ is unhappy about that python dependency there. and yes, a upstream key would be ideal, but I failed to send a upstream bugreport :/ sorry for that20:56
=== mfisch is now known as Guest7150
cjwatsonjamespage: great, thanks22:06
cjwatsonzequence: new package names (source or binary) cause manual review no matter what stage of development we're at22:07
=== bladernr` is now known as bladernr
rxcommCan anyone point me to documentation on how to use the hashsum.mod module in grub2?23:01

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