[00:23] <lazyPower> bdx yep, $LAYER_PATH and $INTERFACE_PATH
[09:55] <tiagogomes> Hi all, does JuJu boostrapped on OpenStack requires Swift?
[10:18] <gnuoy> jamespage, got a sec for https://code.launchpad.net/~gnuoy/charms/trusty/nova-compute/1515570/+merge/277556 ?
[12:20] <stub> tvansteenburgh: Bootstrap is failing in the lxc test runner (ERROR there was an issue examining the environment: cannot use 37017 as state port, already in use)
[13:22] <tvansteenburgh> stub: thanks, will fix
[13:57] <icey> has anybody made a custom hook for juju before?
[13:57] <icey> outside of juju core that is
[14:12] <jrwren> icey: I don't even know what that means. When would it trigger? :)
[14:13] <icey> as a result of juju-run :)
[14:13] <jrwren> icey: how would that differ from an action?
[14:13] <icey> expanding on an idea that came out of the sprint
[14:14] <icey> it woudn't really, except that the user shouldn't be calling it, another charm would be :-D
[14:14] <jrwren> icey: how would that differ from a realtion? :]
[14:15] <icey> this charm would have no relations
[14:15] <icey> it woulkd interct with potentially every other charm deployed
[14:15] <jrwren> why not?
[14:15] <icey> IF the other charm had defined this hook
[14:15] <jrwren> ah, there is the implicit relation, right?
[14:15] <icey> in essence, it would be an advanced service health monitor
[14:15] <jrwren> i can't see how this differs from a relation.
[14:15] <jrwren> IMO you have just defined relation.
[14:16] <icey> can I have one side of a relation run a command on the other service?
[14:16] <icey> there's relation-joined, relation-departing
[14:16] <jrwren> yes?
[14:16] <icey> but not relation-run?
[14:16] <icey> itr should run every update-status
[14:16] <jrwren> well, both run.
[14:16] <icey> it*
[14:17] <jrwren> relation-changed
[14:17] <jrwren> so update-status would change the relation state causing the relation-changed to run
[14:17] <icey> thaat could be a lot of bouncing back and forth
[14:17] <jrwren> what is update-status? do you mean maintenance status?
[14:18] <icey> update-status is a hook that runs regularly
[14:18] <icey> update-status provides constant feedback to the user about the status of the service the charm is modeling. The charm is run by Juju at regular intervals, and gives authors an opportunity to run code that gets the “health” of the service or services.
[14:18] <jrwren> ah cool, i've not used that. maybe I should :)
[14:19] <icey> yeah, in essence I'm working on a beefed up version of that, and charm authors can define both health checking functionality and potentially remediation for issues
[14:19] <jrwren> sounds very interesting.
[14:19] <icey> examples coming from storage charms: hard drive becomes unhealthy, system can remove the hard drive, run tests against it, and maybe re-add it
[14:19] <icey> if that fails, alert a human to intervene
[14:20] <jrwren> we are currently using nrpe for health checking and the nrpe subordinate and nrpe module in charmhelpers makes it simple and great.
[14:20] <icey> my coworker has been lightly discussing it with someone on the core team and they like it, we're going to talk about it more but I figure maybe I can hack together a super basic version :)
[14:20] <icey> so far it's working out but I wondered if anybody had done anything similar
[14:21] <jrwren> icey: I think you can. update-status could change relation data which would cause relation-changed to execute. That gives you what you need afaict.
[14:22] <icey> I really don't want to have to add a relation to it; it also works just fine by adding the juju-client layer to the charm
[14:22] <icey> if we have to add relations, it becomes something that the administrator must add all of the relations when it can be done through juju itself
[14:26] <jrwren> i see. yeah.
[14:28] <beisner> hi all.  juju 1.25.2 is in ppa:juju/proposed.   today i'll be flipping our openstack charm testing lab to use that version for test automation.
[14:30] <tiagogomes> Hi all, does JuJu boostrapped on OpenStack requires Swift?
[14:33] <beisner> hi tiagogomes, i don't believe it is expressly required.  two links for reference:
[14:33] <beisner> https://jujucharms.com/docs/1.25/config-openstack
[14:33] <beisner> https://jujucharms.com/docs/1.25/howto-privatecloud
[14:36] <tiagogomes> thanks. I have seen those, but I when I try to bootrap juju I got an "caused by: the configured region "RegionOne" does not allow access to all required services, namely: compute, object-store. access to these services is missing: object-store" error
[14:49] <mgz> beisner: yell if you see anything fun with 1.25.2
[14:49] <beisner> mgz, thx sir.  i've just done a global force of all uosci jobs to proposed 1.25.2.  it'll get some serious exercise as we're in charm freeze/testing.
[14:49] <mgz> since I added extra validation to our OS-deployer job we've had intermittent failures due to the env not finishing all relations, but that should hopefully just be master
[14:51] <beisner> mgz, our automation calls `juju-wait -v` immediately after juju-deployer exits.  that has resolved the testing-too-soon issue for us.
[14:52] <beisner> we found that arbitrary sleep times are racy, given the undercloud load varies.
[14:52] <beisner> but i can't point at a single case where juju-wait failed to wait 'til the deployment, hooks, relations, etc., were actually-done.
[14:52] <beisner> so that's a cool tool.  +100 stub
[14:52] <beisner> +1000 even
[14:54] <mgz> beisner: my version is similar to that, but also looks at the workload-status reported by the charms
[14:54] <mgz> well, instead really.
[14:55] <beisner> mgz, yeah in our amulet tests we don't use juju-wait, we wait for extended workload state as well.  which is arguably the best way.  for the charm to announce: ok, i'm ready now.
[14:55] <mgz> indeed, but relies on charm sanity
[14:55] <beisner> yep
[14:55] <lazyPower> oi, our charms are sane
[14:55] <mgz> :P
[14:55] <lazyPower> what are you insinuating mgz? ;)
[15:36] <aisrael> tvansteenburgh: Should this merge request be showing up in the queue? It's been reviewed as needs fixing but the original author hasn't responded since then: https://code.launchpad.net/~brad-marshall/charms/trusty/memcached/add-monitors-relation/+merge/276958
[15:39] <aisrael> tvansteenburgh: also, item 2391 in the queue is a dead link
[15:41] <tvansteenburgh> aisrael: 2391 removed
[15:41] <aisrael> ta
[15:41] <tvansteenburgh> aisrael: i'll have to look into the other thing, just not right this sec
[15:42] <aisrael> tvansteenburgh: No worries. Just wanted to make sure it was on your radar.
[16:30] <icey> anybody have thoughts on testing an action that would require removing parts of a unit and multiple minutes for any differences to become visible
[16:32] <stub> icey, jrwren : You don't need update-status. You can call the juju-run tool from a cronjob running on the unit to do stuff in a hook context.
[17:26] <mbruzek> cory_fu_: marcoceppi, lazyPower, any other charmers, can I get a review on the charm-helpers update: https://code.launchpad.net/~mbruzek/charm-helpers/host-docstrings/+merge/282788
[17:30] <bdx> marcoceppi: do have a example of layer-django being consumed?
[17:31] <bdx> marcoceppi: I've created `anyapp` to test with here -> https://github.com/jamesbeedy/anyapp
[17:32] <bdx> and django-nginx charm here http://bazaar.launchpad.net/~jamesbeedy/charms/trusty/django-nginx/dev/files
[17:34] <bdx> marcoceppi: what I'm wondering is how you are setting up your django project <-> what params you are setting in your django.yaml
[17:43] <lazyPower> i'm pretty sure marco is travelling today bdx, replys may be latent.
[17:43] <lazyPower> thanks for the PR btw :)
[17:49] <bdx> lazyPower: ok. cool. yea... about that ... I'm testing it out a bunch as well .... not sure its fully there yet ... but I think I'm making some good headway... http://bazaar.launchpad.net/~jamesbeedy/charms/trusty/django-nginx/dev/view/head:/reactive/django_nginx.py
[17:49] <lazyPower> nice
[17:50] <bdx> lazyPower: the @when hook will only execute when all states are met right?
[17:51] <lazyPower> yep
[17:51] <bdx> lazyPower: but will it execute everytime the states are met?
[17:51] <lazyPower> yep
[17:51] <lazyPower> unless you add a @when_not to prevent it from running
[17:52] <lazyPower> or something to that effect
[17:52] <bdx> so then using the only_once hook will ensure that it only runs one time, no matter how many times the states are satisfied in the @when?
[17:53] <lazyPower> good question, i'm not sure :)
[17:53] <lazyPower> I've not used only_once
[18:01] <tiagogomes> Hi, when JuJu 1.25 will be released? Will it be part of ubuntu 16.04 ?
[18:02] <lazyPower> tiagogomes 1.25.0 is already out as stable
[18:02] <lazyPower> 1.26.0-alpha is the current dev release, with 2.0 on the horizon
[18:03] <tiagogomes> lazyPower ah thanks
[18:14] <icey> I'm adding an action to a charm and I'm not entirely sure how to test it; it changes a config in a running program, the easiest way I've thought of testing it is to query that the config value is changed. If I add testing for the functionality exposed by the configuration, I'm testing the underlying software as part of the charm tests, would that be desired?
[18:19] <stub> I think it is desired. You do want to test the underlying software, because you need to confirm that the process you are using to change the configuration is correct (eg. you are remembering to send a HUP signal to reload, or that this particular setting requires the daemon bounced)
[18:20] <stub> You could test that you changed the config and maybe issued a reload command, but that doesn't mean it actually works.
[18:20] <stub> icey: ^
[18:20] <lazyPower> o/ stub
[18:20] <stub> o/
[18:21] <stub> Off into the night in a tick
[18:21] <icey> well, the program I'm using lets us send in cluster config through the program itself, and I can query the program to validate that the configuration changed stub
[18:22] <icey> testing the underlying functionality would require me removing a disk, waiting (10+ minutes) for the disk to be marked down, bring the disk back up, trigger the action, kill the disk, wait longer than the first time to make sure it is not marked down
[18:22] <icey> so, 20+ minutes of waiting?
[18:22] <icey> and the program, ceph, will report the config to me if it is set
[18:23] <stub> Right. Removing disks isn't possible in most automated test frameworks, so that is right out. Setting the config value and reading it back from ceph (not just looking at the config files) seems good.
[18:24] <bdx> stub: yes!!!!
[18:24] <icey> yeah, it's not a config file thing, it's literally telling ceph `ceph osd set nodown`
[18:24] <icey> stub: thanks~!
[18:25] <bdx> stub: you just touched on something near and dear to my heart
[18:26] <bdx> stub: removing/replacing ceph disks is a danger zone
[18:26] <bdx> stub: this is an area that needs help from the MAAS team
[18:27] <stub> The kernel guys might be able to help you fake a failed disk if you really want (if ln -s /dev/random /dev/sdb2 doesn't do the trick)
[18:27] <bdx> stub: if you replace/remove a disk in ceph, maas will assume a different drive for sda
[18:28] <bdx> you also have to reboot the node
[18:28] <bdx> but
[18:29] <bdx> stub: ^ is a huge issue for me right now
[18:29] <bdx> I have done alot of DR testing with ceph/maas
[18:31] <bdx> maas would need to recommission  the node to be able to account for a new/replaced disk
[18:31] <icey> bdx stub we're working on making the ceph experience better with juju, including updating / replacing disks
[18:32] <icey> it's on our roadmap :)
[18:32] <bdx> thats a relief
[18:32] <bdx> the CIO of my company keeps bugging me about it
[18:32] <bdx> he knows its not a thing
[18:33] <bdx> I have been able to work around it by manually altering maasdb
[18:43] <aisrael> stub: Is the cassandra work you've done ready-ready to go? https://code.launchpad.net/~stub/charms/trusty/cassandra/ensure-thrift/+merge/279869
[18:44] <stub> aisrael: Yes. Just been resending it to the CI system for laughs.
[18:45] <aisrael> stub: CI always needs something to do. :D
[18:45] <stub> Good timing if you are reviewing - that branch was about to go into production ;)
[18:46] <aisrael> stub: Yup, I am reviewing. So far, so good.
[18:56] <icey> so, I'm noticing that the update-status hook doesn't seem to actually exist in any documentation yet?
[18:57] <stub> icey: No, but I already opened an issue on that and it is being added.
[18:57] <icey> ok, just wanted to make sure it was ok stub, thanks!
[18:59] <mbruzek> bdx: I just got back from lunch and I am going to review your tls/k8s pull requests after my meeting
[19:06] <bdx> mbruzek: sweet! its small, just swapped out your local chdir
[19:06] <bdx> but the tls one is a little bigger
[19:08] <icey> is there a recommended way to run actions in a functional test?
[19:10] <tvansteenburgh> icey: https://github.com/juju/amulet/blob/master/amulet/deployer.py#L362
[19:11] <icey> thanks tvansteenburgh, I just found the PR that added that :)
[19:14] <icey> it's funny when google shows the PR before the actual file :-P
[20:08] <pmatulis> mbruzek: fyi, https://github.com/juju/docs/pull/801 , comments welcome
[20:08] <mbruzek> pmatulis: I am taking a look now
[20:13] <mbruzek> pmatulis: I see what I was looking for on line 54!
[20:13] <mbruzek> still reading
[20:54] <pmatulis> mbruzek: thanks for the comments
[20:54] <mbruzek> pmatulis: thanks for sending me the link
[21:01] <bdx> anyone have luck with GitUrlFetchHandler or install_remote from charmhelpers.fetch ?
[21:06] <natefinch> rick_h_: you around?
[21:06] <mbruzek> bdx how did you run the tls tests?  http://paste.ubuntu.com/14510918/  I am getting an assertion error on the test_ca() method
[21:07] <mbruzek> bdx I see a /tmp/server.crt, but not a /tmp/ca
[21:07] <mbruzek> .crt
[21:46] <bdx> mbruzek: ooo mbruzek, my bad, here
[21:46] <mbruzek> no problem I am fixing it
[21:47] <mbruzek> and setting up the repo to run these tests every push
[21:52] <bdx> niceee
[21:53] <lazyPower> 'eating broccoli' ;)
[22:32] <lazyPower> bdx: Landed your class + tests with some refactoring
[22:32] <lazyPower> give a look at master
[22:33] <lazyPower> bdx https://travis-ci.org/mbruzek/layer-tls
[22:33] <mbruzek> bdx: we had to rewrite the tests to pass.
[22:34] <lazyPower> not really i mean
[22:34] <lazyPower> we took his high level abstract, and then made it red2green
[22:35] <bdx> lazyPower, mbruzek: nice!
[22:39] <bdx> I knew the tests would need a little love


[02:28] <boredandblogging> somerville32: are you making changes to the UWN?
[02:28] <somerville32> boredandblogging, yes :P
[02:28] <somerville32> boredandblogging, Your lock timed out
[02:28] <boredandblogging> somerville32: let me know when you are done
[02:31] <somerville32> ok
[02:40]  * somerville32 cries.
[02:41] <somerville32> I'm trying to rewrite the eeePC article and I'm sick and firefox just crashed :(
[02:41] <boredandblogging> somerville32: you want to send me your text?
[02:42] <somerville32> boredandblogging, you can do that?
[02:42] <somerville32> oh, I misread that
[02:42] <boredandblogging> just paste it here or email it to me
[02:42] <somerville32> I thought you were going to give me what I was writing but lost
[02:42] <boredandblogging> lol
[02:42] <boredandblogging> wish I could
[02:43] <boredandblogging> maybe the wiki needs some auto-saving draft functionality
[02:43] <boredandblogging> a la gmail
[02:43] <somerville32> gmail is so slow these days :(
[02:43] <boredandblogging> the new version is pretty fast for me these days
[02:43] <boredandblogging> i'm going to save my changes to the UWN
[02:45] <boredandblogging> somerville32: did you want to try to put your changes in again? I'm getting ready to release it
[02:46] <somerville32> I'm typing as fast as I can :P
[02:52] <johnc4510-laptop> boredandblogging: hey bud
[02:53] <boredandblogging> johnc4510-laptop: hey
[02:53] <johnc4510-laptop> how's it going
[02:53] <johnc4510-laptop> LOL
[02:53] <boredandblogging> not too shabby
[02:54] <somerville32> Ok
[02:54] <somerville32> I think I got it
[02:54] <somerville32> Is it okay for me to save or should I send it to you otherwise?
[02:54]  * johnc4510-laptop claps
[02:54] <boredandblogging> somerville32: go ahead and save
[02:55] <johnc4510-laptop> boredandblogging: MacGregor is a hot link in new members
[02:57] <boredandblogging> johnc4510-laptop: ok, I'll fix it after somerville32 is done
[02:57] <johnc4510-laptop> kk
[02:57] <somerville32> done
[02:57] <boredandblogging> somerville32: thanks
[02:58]  * johnc4510-laptop waves at somerville32
[02:58] <somerville32> erm
[02:58] <somerville32> boredandblogging, there are still some edit conflicts I guess. You can fix them :P
[02:58] <somerville32> johnc4510-laptop, Hi
[03:34] <boredandblogging> please digg: http://digg.com/linux_unix/Ubuntu_Weekly_Newsletter_70


[02:20] <ScottL> was someone looking for me about the -rt kernel?
[02:21] <nhandler> ScottL:<PHONE_NUMBER> 15:34:25 < cjwatson> curious what they're going to do about the linux-headers-rt recommendation from ubuntustudio-desktop, given that linux-rt's been removed
[02:22] <ScottL> thanks nhandler
[02:52] <ScottL> cjwatson, hopefully tomorrow i'll take care of the linux-headers-rt recommendation in ubuntustudio-desktop
[03:04] <NCommander> cjwatson: that's fine, I fpassed out before I saw your message or I would have done it
[03:29] <slangasek> ^^ per mvo's request this morning; note that this bug only affects upgrades from systems that aren't up-to-date on lucid-updates, so may not be worth accepting before beta
[03:30] <persia> Depends on testing methodologies: lots of folks try to do the install/dist-upgrade trick on a VM, and may not remember to update first.
[07:45] <mvo> slangasek: \o/ for fixing the ifupdown #620956
[09:14] <Riddell> ev: the standalone installer seems to be working in Kubuntu but when clicking "Try Kubuntu" it goes to the slideshow rather than the live session
[09:14] <ara> morning all!
[09:15] <ara> when do we expect the first candidate images?
[09:15] <persia> cronjob was still enabled last I heard, so today's dailies should be candidates as they become available.
[09:16] <persia> I believe this will take at least two more hours, perhaps a bit more.
[09:16] <persia> Err, rather, I'm doing math wrong.  Should be any time now.
[09:29] <Riddell> ev: hum, the installer seems to freeze this VM
[09:35] <Riddell> ev: bug 625586 I guess
[09:35] <ubot4> Launchpad bug 625586 in ubiquity (Ubuntu) "ubiquity killed by OOM killer (affects: 2) (heat: 1154)" [High,New] https://launchpad.net/bugs/625586
[09:35] <Riddell> the install does complete fine for me if you ignore the UI freeze
[09:40] <ogra> hrm, lamont i cant reach sycamore or acorn through http, are they down ?
[09:40] <ogra> (builds failed as well it seems)
[09:53] <Riddell> bug 627284
[09:53] <ubot4> Launchpad bug 627284 in ubiquity (Ubuntu) "Try Kubuntu leads to slideshow not live CD (affects: 1) (heat: 6)" [Critical,New] https://launchpad.net/bugs/627284
[09:54] <ogra> lamont, hmm, in fact i cant reach *any* of the livefs builders
[09:54]  * ogra wonders whats going on here
[10:02] <ogra> sycamore.buildd starting at Tue Aug 31 10:02:07 BST 2010
[10:02] <ogra> ssh: connect to host sycamore.buildd port 22: No route to host
[10:02] <ogra> sycamore.buildd finished at Tue Aug 31 10:02:10 BST 2010 (failed)
[10:02] <ogra> geez
[10:02] <cjwatson> I can't reach acorn or sycamore either, but e.g. kapok is fine
[10:03] <ogra> are terranova and king still livefs builders ?
[10:03] <cjwatson> no
[10:03] <ogra> ah, k
[10:03] <cjwatson> cardamom weddell royal concordia all work fine.  clementine is reachable but doesn't have a ~buildd directory.
[10:03] <ogra> clementine is dead since maverick started
[10:03] <cjwatson> from which I infer that I forgot to update livefs-build-logs-mirror
[10:03] <ogra> acorn took over
[10:04] <ogra> and sycamore is a new one for omap4 builds only
[10:04] <cjwatson> well, that would be why you haven't been getting your logs on the web ;-)
[10:05] <cjwatson> I'd recommend asking #is about those hosts being down; lamont probably won't be around for a few hours yet
[10:05] <ogra> cjwatson, yeah, sorry, my fault i should have pinged you about it ... i personally look directly on the buildd nowadays so i forgot
[11:24]  * cjwatson wonders why the kubuntu daily has uninstallable packages
[11:25] <cjwatson> building updated kubuntu dvds since those wouldn't normally happen today
[11:32] <\sh> moins :) can some approve last zend-framework upload 1.10.8 (bug fix only upload -> bug #627319)
[11:32] <ubot4> Launchpad bug 627319 in zend-framework (Ubuntu) "zend-framework 1.10.8 (bugfix release) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/627319
[11:44] <lamont> clementine is a recycled name (sorry) and not a livecd builder.  sycamore was down, is now back up <-- ogra, cjwatson
[11:44] <ogra> lamont, yeah, i'm alreday building on it again :)
[11:44] <Riddell> \sh: accepted
[11:45] <lamont> ogra: acorn was not on my list of hate as of last night, though.
[11:45] <ogra> it did build the dove and omap3 images but was dead when i tried to reach it today
[11:46] <lamont> must have gotten annoyed after I went offline
[11:46] <\sh> Riddell, thx...
[11:46] <ogra> heh, yeah, it needs its master :)
[11:47] <\sh> Riddell, when you are at it...could you review bug #627337 and think about it ?? :)
[11:47] <ubot4> Launchpad bug 627337 in ubuntu "[FFE] FAI 3.4 for Ubuntu Maverick (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/627337
[11:51] <cjwatson> acorn and sycamore build logs will now be mirrored
[11:51] <cjwatson> ogra: you want to kick rebuilds?
[11:52] <ogra> cjwatson, running since ~30min already
[11:52] <cjwatson> ok
[12:09] <Riddell> ogra: what ARM images are you expecting to build for beta?
[12:11]  * cjwatson starts sorting out the tracker
[12:13] <ara> cjwatson, thanks!
[12:13] <cjwatson> ubuntu alternates both oversized
[12:14] <cjwatson> hmm, why isn't "Maverick Beta" an option on http://iso.qa.ubuntu.com/qatracker/admin/addbuild ?
[12:15] <cjwatson> stgraber: ^- do you know?  I added it in http://iso.qa.ubuntu.com/qatracker/admin/milestone
[12:15] <ev> Riddell: I've committed a fix for bug 627284.  You're not in -installer, so I wasn't sure if you would notice.
[12:15] <ubot4> Launchpad bug 627284 in ubiquity (Ubuntu) "Try Kubuntu leads to slideshow not live CD (affects: 1) (heat: 6)" [Critical,Fix committed] https://launchpad.net/bugs/627284
[12:15] <cjwatson> ev: are there ubiquity fixes pending for beta?
[12:16] <ev> cjwatson: I was just going to ask.  What are my chances of getting a respin?
[12:16] <cjwatson> 'cos I was about to start posting desktops, once the tracker will let me
[12:16] <cjwatson> what's your timeframe?
[12:16] <ev> as yes, there are fixes I'd like to see in
[12:16] <cjwatson> can you upload right away?
[12:16] <ev> yes
[12:16] <cjwatson> please do then
[12:17] <ev> should I do the usual freeze exception dance, or are you happy to push it through?
[12:18] <cjwatson> please just upload it
[12:18] <cjwatson> I'll check it over in the queue
[12:18] <ev> will do, thanks
[12:18] <cjwatson> have we had a translations update recently?
[12:18] <cjwatson> ... apparently so
[12:27] <\sh> ScottK, thx
[12:28]  * cjwatson fixes Ubuntu alternate oversizedness
[12:28] <cjwatson> hm, there's been an issue updating the seed mirrors for the last week
[12:29] <cjwatson> actually it was probably ok, just slow
[12:31] <Riddell> thanks ev
[12:32] <ev> sure thing, sorry for the screw up there
[12:32] <ev> cjwatson: uploaded
[12:55] <cjwatson> ev: accepted (please push the debcommit -r bit to bzr?)
[12:56] <ev> cjwatson: done, thanks
[12:57] <Riddell> cjwatson: could you take a look at kdenetwork in unapproved?  it's needed to stop libavcodecs being pulled onto the CD
[12:58] <cjwatson> ok, is that what the uninstallables are about?
[12:58] <Riddell> cjwatson: yes
[12:59] <cjwatson> accepted
[13:00] <cjwatson> seb128: is there any of this gnome update that's beta-critical, as opposed to would-be-nice?
[13:00] <cjwatson> I wasn't available yesterday to review it and it doesn't look like others did, and I'd like to start building beta candidates v. soon
[13:01] <cjwatson> we have a slot for a small number of them if they're needed
[13:01] <seb128> cjwatson, hi
[13:01] <seb128> cjwatson, those are not beta stopper no
[13:02] <seb128> I pinged slangasek about the important ones yesterday
[13:02] <seb128> we might still want to get some unity changes in the next hour
[13:02] <cjwatson> ah, ok, so those went in?
[13:02] <seb128> do you think there is a margin to wait a bit for UNE?
[13:02] <seb128> cjwatson, yes
[13:02] <cjwatson> I can hold off on building netbook, yes
[13:02] <cjwatson> plenty of other stuff to do
[13:02] <seb128> would be nice, just for an hour
[13:02] <seb128> I want to sort the status with njpatel when he's online
[13:02] <cjwatson> I have to wait 1.5 hours or so for ubiquity and kdenetwork anyway
[13:03] <seb128> they are sprinting in canada this week
[13:03] <seb128> he should be there rsn
[13:03] <seb128> ok
[13:04] <cjwatson> I wonder if I can do anything about the powerpc desktop oversizedness
[13:04] <cjwatson> that's the only oversized thing left, I think
[13:04] <cjwatson> a
[13:05] <cjwatson> probably not a whole lot
[13:20] <persia> cjwatson, Given how long it's been since Windows worked on powerpc, the lupin and casper-lupin stuff could be dropped (although that might be deeper than you want to play today)
[13:25] <cjwatson> persia: thanks, done, though it won't make much difference
[13:26] <ogra> Riddell, ubuntu-netbook for omap3 and 4, kubuntu and kubuntu-mobile for omap3, no idea what NCommander's plans for dove are
[13:27] <NCommander> ogra: I'll attempt to test tomorrow, can't now
[13:27] <ogra> NCommander, what images do you plan to have rolled ofr beta was the question
[13:27] <ogra> *for
[13:28]  * persia doesn't see anything else obvious, seeing use cases for ntfs, and knowing the reasons libdrm-intel is there.
[13:28] <ogra> Riddell, nobody in the team will have time to test any of the kubuntu ones though, so testing these is up to the community
[14:25] <seb128> cjwatson, ok, do we still have a margin to have changes in before the end of the hour out of UNE or is late for that?
[14:25] <cjwatson> go ahead
[14:26] <seb128> cjwatson, the shotwell update has small changes and fix import issues and a crasher if you can review that, rather a would be nice to have
[14:27] <seb128> cjwatson, evo in the queue just fix some files installed at the wrong location, that should make the default signature work and have a menu entry in internet
[14:27] <seb128> cjwatson, I will upload rsn a telepathy-logger update with a recommends on libdconf0
[14:28] <seb128> seems we got bitten again by the "libglib2.0-0 recommends are not installed" I asked you about at the sprint
[14:28] <seb128> ie dconf doesn't get pulled on the iso which leads to have different programs falling back to use the default glib backend which has no storage
[14:29] <seb128> and I will have an unity update for UNE before end of the hour
[14:29] <seb128> I think that's it by checking with different desktop and dx people
[14:32] <ttx> ara, cjwatson: anything blocking using the current server ISO daily as the beta candidate ? Or are we waiting for something to show up to respin ?
[14:32] <ara> ttx, I don't know. I am waiting as well for images to appear in the tracker
[14:41] <cjwatson> ttx: I need help with the tracker, which is refusing to let me post images for Maverick Beta
[14:41] <cjwatson> 14:38 <agy> cjwatson: ara is probably the person to talk to about qatracker
[14:41] <cjwatson> ara: ^- can you help?
[14:42]  * ttx shakes its fist towards the tracker to see if it helps
[14:42] <ara> cjwatson, sure, what's  the issue?
[14:42] <cjwatson> 12:57 <cjwatson> Can somebody look at iso.qa.ubuntu.com for me?  I added a "Maverick Beta" milestone using http://iso.qa.ubuntu.com/qatracker/admin/milestone, but it's not showing up in the drop-down at the
[14:42] <cjwatson>                  bottom of http://iso.qa.ubuntu.com/qatracker/admin/addbuild
[14:42] <cjwatson> 12:57 <cjwatson> I'm wondering if it needs some kind of manual push
[14:42] <cjwatson> sigh, I wish seb128 had told me about those uploads when I asked earlier
[14:43] <ara> cjwatson, I'll have a look
[14:43] <cjwatson> I bet that'll mean another hour
[14:43] <ara> cjwatson, I see that milestone in the dropdown
[14:43] <ara> cjwatson, (the first of the list)
[14:44] <ara> cjwatson, the ordering of that list could be wiser, that's true
[14:44] <cjwatson> oh, sigh, ok
[14:44] <cjwatson> can you change the default?
[14:44] <cjwatson> which is currently Lucid 10.04.1
[14:45] <cjwatson> ttx: posted
[14:45] <ttx> cjwatson: thanks !
[14:47] <seb128> re, sorry system crash on user switching
[14:47] <ara> cjwatson, done
[14:47] <cjwatson> seb128: would have been nice to know earlier :-/, but shotwell and evolution accepted now
[14:47] <cjwatson> ara: thanks
[14:48] <cjwatson> might be 1530 UTC or so before I can start building candidates
[14:48] <seb128> cjwatson, sorry I was set on the "let them roll beta iso we can get those later", but somebody raised the dconf issue
[14:48] <seb128> cjwatson, so I figured we will need to get that anyway so...
[14:49] <cjwatson> how long will telepathy-logger be?
[14:49] <seb128> thanks
[14:49] <seb128> I'm uploading now
[14:49] <seb128> I was about when my box crashed
[15:00] <seb128> cjwatson, telepathy-logger shows up in the queue
[15:01] <cjwatson> accepted, thanks
[15:02] <seb128> thank you
[15:20] <Riddell> cjwatson: kdenetwork and ubiquity seem to be in, can I build kubuntu candidate CDs?
[15:20] <cjwatson> can I do it please
[15:20] <Riddell> sure
[15:22] <cjwatson> building
[15:22]  * cjwatson looks suspiciously at how all his jigdo attempts today yield checksum errors
[15:23] <cjwatson> wonder if there's a problem on my local mirror ...
[15:24]  * ttx expects a eucalyptus upload fixing a few beta-targeted bugs, that will generate a server ISO respin.
[15:37] <stgraber> cjwatson: is your issue fixed ?
[15:38] <cjwatson> stgraber: yes, thanks
[15:38] <cjwatson> seb128: is unity-asset-pool for beta, and is there anything else in that list?
[15:39] <seb128> cjwatson, yes and unity which is coming in 2 minutes
[15:39] <seb128> that's UNE only
[15:39] <seb128> and we should be done then
[15:39] <seb128> we are done for desktop already
[15:48] <ttx> hm, about server ISOs: looking at the potenial euca upload, there is nothing worth a respin there. So we won't respin over that one alone.
[16:49] <cjwatson> seb128: any news on unity?
[16:49] <seb128> cjwatson, hum, I uploaded an hour ago, let me see what happened
[16:50] <seb128> Rejected:
[16:50] <seb128> dpkg-source failed for unity_0.2.32-0ubuntu3.dsc [return: 29]
[16:50] <seb128> hum
[16:50] <seb128> cjwatson, can we change a source to format 3 in a new revision?
[16:51] <cjwatson> tar: data/trash.png: Cannot open: File exists
[16:51] <cjwatson> tar: data/files.png: Cannot open: File exists
[16:51] <cjwatson> tar: data/applications.png: Cannot open: File exists
[16:51] <cjwatson> yes
[16:51] <cjwatson> doesn't mean you can ship files in the .debian.tar.gz that exist in the .orig.tar.gz though
[16:51] <seb128> oh :-(
[16:52] <cjwatson> at least I don't think so
[16:52] <cjwatson> though actually that seems slightly odd
[16:52] <cjwatson> but can you stick them under debian/ instead as a workaround?
[16:52] <seb128> sure
[16:52] <seb128> weird that it works there
[16:53] <seb128> I can dpkg-source -x it
[16:53] <cjwatson> the dpkg-source -x failure is reproducible on cocoplum
[16:53] <cjwatson> dpkg-dev <IP_ADDRESS>ubuntu1~1.IS.PATCHED.8.04
[16:54] <cjwatson> maybe it's a bug that was fixed since?
[16:54] <seb128> could be
[16:54] <seb128> in any case I'm going to fix that, sorry for the delay :-(
[16:55] <cjwatson> I don't see anything obvious in the dpkg changelog
[16:55] <cjwatson> maybe report a bug and attach the uploaded files
[16:55] <cjwatson> spinning other images in the meantime
[16:55] <seb128> ok, let me get a valid upload in first
[16:58] <ScottK> cjwatson: Where are we wrt spinning mythbuntu images?  The mythbuntu-common in the queue is desired, but not required for beta.
[16:59] <ScottK> I've reviewed it and it seems OK if it won't hurt ISO generation signfificantly.
[17:02] <cjwatson> $ echo ubuntu; for-project ubuntu cron.daily; buildlive ubuntu && for-project ubuntu cron.daily-live; echo xubuntu; for-project xubuntu cron.daily; buildlive xubuntu && for-project xubuntu cron.daily-live; echo ubuntustudio; for-project ubuntustudio cron.daily; echo mythbuntu; buildlive mythbuntu && for-project mythbuntu cron.daily-live
[17:02] <cjwatson> currently in Ubuntu daily-live
[17:02] <cjwatson> go ahead and accept it
[17:02] <cjwatson> may not quite make that build but we can respin quickly
[17:03] <ScottK> OK.  Thanks.
[17:04] <ScottK> Done.
[17:10] <ara> cjwatson, ubiquity is crashing for me on kubuntu
[17:10] <ara> bug 627489
[17:10] <ubot4> Launchpad bug 627489 in ubiquity (Ubuntu) "Ubiquity crashes in Kubuntu (Maverick Beta candidate) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/627489
[17:11] <cjwatson> ev: ^-
[17:12] <ev> looking
[17:17] <ev> ugh, fixing
[17:23] <GrueMaster> I also saw this yesterday on the http://cdimage.ubuntu.com/kubuntu/ports/daily-preinstalled/20100830/maverick-preinstalled-desktop-armel+omap.img.gz image.
[17:23] <GrueMaster> Hadn't had time to look at it though.
[17:31] <seb128> cjwatson, unity uploaded again let's see how it goes this time
[17:32] <seb128> cjwatson, it's in the queue
[17:35] <cjwatson> damnit, desktops oversized again
[17:35] <cjwatson> quite dramatically - I wonder what happened
[17:38] <cjwatson> unity accepted
[17:40] <seb128> thanks
[17:42] <GrueMaster> ev: I'm not sure if I have the same kubuntu installer issue or not.  Could you quickly scan my logs at http://members.dsl-only.net/~tdavis/oem-config-crash.tgz?  This is on omap (armel) platform.
[17:42] <GrueMaster> If it isn't the same, I'll look into it more and file a bug asap.
[17:43] <cjwatson> oh, argh, oversized because we've just picked up the last week's worth of seed changes in one go
[17:43]  * cjwatson cries a little bit inside
[17:48] <cjwatson> and since the necessary change is in the live task, we'll need the usual publisher runs to fix it.  I'll try to speed it up a bit
[17:51] <cjwatson> (running 'LPCONFIG=ftpmaster-publish /srv/launchpad.net/codelines/current/cronscripts/publishing/cron.germinate' by hand as lp_publish@cocoplum, since we're at the right time for that to be a useful speedup)
[18:12] <cjwatson> BTW, Ubuntu alternate and Xubuntu alternate posted
[18:12] <charlie-tca> Thanks
[18:22] <charlie-tca> umm, those images don't exist for xubuntu alternate on http://cdimage.ubuntu.com/xubuntu/daily
[18:26] <charlie-tca> well, got them now
[18:26] <cjwatson> wait, it's just slow
[18:27] <charlie-tca> Thanks
[18:28]  * charlie-tca is in a hurry. It could a long time to sync them on his s-l-o-w connection now
[18:28] <cjwatson> xubuntu desktop posted
[18:28] <charlie-tca> Thanks
[18:28] <cjwatson> hey, I've been downloading a single poxy cd for a couple of hours
[18:30] <slangasek> maybe a non-poxy one would download faster
[18:30] <charlie-tca> oh! Maybe mine is just as good, then :-)
[18:30] <cjwatson> slangasek: if poxy == large :-)
[18:31] <slangasek> I dunno, maybe the pox causes packet fragmentation?
[18:31]  * cjwatson applies antibiotics to his ethernet port
[18:32] <cjwatson> ubuntustudio alternate posted
[18:33] <cjwatson> ev: any ETA on a ubiquity fix for Kubuntu?
[18:35] <Riddell> ev: my first test gave me the OOM issue again on Kubuntu
[18:35] <Riddell> testing again with a console running to get more info
[18:35] <ev> cjwatson: soonish.  I'm assuming we're only respinning for KDE, right?
[18:35] <ev> Riddell: ouch.
[18:36] <cjwatson> ev: I think so
[18:36] <cjwatson> (for the time being)
[18:36] <cjwatson> well, Ubuntu desktop does need a respin anyway, but I wasn't planning to wait for ubiquity
[18:37] <ev> can you?  Looking at the code, it will break in the GTK frontend if you enter a username with ^[0-9A-Za-z] in it.  I'd like to just ressurect the hostname box, reusing the old code making a minor change to make it fit the current flow.
[18:37] <Riddell> ev: yes lots of plugininstall.py instances running
[18:37] <ev> Riddell: ughhhhh
[18:38] <ev> Riddell: logs please
[18:38]  * cjwatson has a horrible thought
[18:38] <cjwatson> forgot to update OFFICIAL to say "Beta"
[18:38] <cjwatson> you can tell I haven't done this for a while
[18:40] <slangasek> at least that doesn't require respinning any livefses
[18:40] <cjwatson> done, but all images built until now will say "Alpha" instead.  I don't plan to respin just for this unless somebody tells me I have to
[18:40] <slangasek> I guess the noise it will cause with users is going to be fairly minimal
[18:40] <Riddell> ev: http://muse.19inch.net/~jr/tmp/syslog  http://muse.19inch.net/~jr/tmp/debug
[18:41] <cjwatson> I dunno, feel free to suggest I'm wrong, I know we've done differently in the past (but we had fewer images then)
[18:41]  * Riddell out for an hour
[18:42] <cjwatson> Ubuntu and Kubuntu desktops need to be respun anyway, and those are the highest-profile ones aside from perhaps Ubuntu server
[18:43] <charlie-tca> We can release note xubuntu, if no other respin is needed
[18:49] <slangasek> cjwatson: I don't feel strongly about it, particularly as none of the noise is going to be directed at me... :)
[18:49] <cjwatson> heh
[18:49] <cjwatson> wanna bet
[18:49] <slangasek> hah :)
[18:49] <cjwatson> respinning Ubuntu desktop
[18:50] <slangasek> TBH I've always found it a little bit bothersome that, in preparation of the milestone, we prepare a series of *candidate* images that all get labeled "Beta" or "RC"
[18:50] <cjwatson> also have commented out the crontab now that the day's normal ports builds have finished
[18:50] <cjwatson> well, yeah, have always agreed but never saw an alternative
[18:50] <slangasek> smarter on-the-fly ISO editing :-)
[18:50] <cjwatson> short of sedding the ISO which gives me the shivers
[18:50] <slangasek> I said smarter
[18:50] <slangasek> ;)
[18:50] <cjwatson> that was a metasyntactic sed :)
[18:51] <cjwatson> given that there's code that parses .disk/info ...
[19:11]  * cjwatson confirms that the mythbuntu desktop images have current mythbuntu-common, and posts
[19:20] <cjwatson> slangasek: do we customarily post the upgrade tests around this time?
[19:20] <slangasek> cjwatson: yes
[19:20] <cjwatson> what build id do you use?  just the current date?
[19:21] <cjwatson> ev: sorry, I didn't notice your comment above.  I can respin Ubuntu desktop again
[19:21] <ev> cjwatson: okay
[19:22] <ev> I've committed the hostname fix, just testing now
[19:22] <ev> then I'll try to reproduce Riddell's scary bug
[19:22] <ev> err and upload ubiquity, of course
[19:26] <slangasek> cjwatson: current date, yes
[19:31] <GrueMaster> Is there a respin planned for Ubuntu-Netbook on Arm?  If not, can we get them enabled in iso.qa.ubuntu.com?
[19:31] <cjwatson> respin planned
[19:31] <cjwatson> I'm just waiting for unity to publish
[19:31] <GrueMaster> ok.
[19:32] <cjwatson> I think just about all the candidates are up now except arm and DVDs, and of course the Ubuntu and Kubuntu desktop respins
[19:32] <cjwatson> (for ubiquity)
[19:33] <GrueMaster> Since there is a respin planned, is there a chance someone can tweak livecd to run /usr/lib/gdm/gdm-set-default-session une-efl prior to building squashfs for armel+dove?  Otherwise there is no way to boot past X.
[19:33] <cjwatson> I had a respin planned but in like ten minutes
[19:33] <cjwatson> I'm not sure how quick I can get a livecd-rootfs change in
[19:34] <cjwatson> can you propose a branch of livecd-rootfs for merging anyway, though?
[19:34] <cjwatson> is this beta-critical?  should I be building DVDs first, and waiting for this?
[19:34] <GrueMaster> I wouldn't know where to start.  NCommander is planning on doing it, but he's in China on assignment.
[19:35] <GrueMaster> This only affects armel+dove.
[19:35] <GrueMaster> No other platforms would be affected.
[19:35] <cjwatson> I mean, I can do it, but I'll probably get it slightly wrong
[19:35] <GrueMaster> (or should).
[19:36] <GrueMaster> ok.  Not sure how best to proceed then.
[19:36] <cjwatson> something like http://paste.ubuntu.com/486429/?
[19:36]  * GrueMaster hates being the only teammate on arm in the PST timezone.
[19:37] <cjwatson> er, except with chroot $ROOT
[19:37] <cjwatson> does gdm-set-default-session need $DISPLAY?
[19:38] <GrueMaster> No display needed.  Here's what we currently have in jasper for omap images.  It is run on first boot.
[19:38] <GrueMaster> if [ -e /root/usr/share/xsessions/une-efl.desktop ] && [ -e /root/usr/lib/gdm/gdm-set-default-session ];then
[19:38] <GrueMaster>     chroot /root /usr/lib/gdm/gdm-set-default-session une-efl >>$LOGFILE 2>&1 || true
[19:38] <GrueMaster> fi
[19:39] <NCommander> GrueMaster: cjwatson: I'd be glad to do it, but I'm not quite awake enough to trust myself with an editor, and my Dove board is locked at Marvell :-/
[19:40] <cjwatson> NCommander: does http://paste.ubuntu.com/486431/ seem plausible?
[19:42]  * GrueMaster likes line 14 of the patch.  :D
[19:42] <GrueMaster> The rest looks plausible to me, but I'm not familiar with the base code.
[19:45] <cjwatson> committed
[19:45] <cjwatson> lamont: do the buildds pull from bzr at the moment, or do I need to upload this livecd-rootfs change?
[19:46] <lamont> cjwatson: they dist-upgrade ... livecd-rootfs is the then-current-for-the-distroarchseries each build
[19:47] <cjwatson> ok, so the only delay is publication
[19:47] <lamont> except that BuildLiveCD.sh is a manual migration from inside the chroot to outside, and should be done via RT
[19:47] <cjwatson> that's not needed here
[19:48] <cjwatson> UNE i386 building
[19:56] <cjwatson> could somebody review livecd-rootfs 1.150 in the queue?  (there's also a 1.149 from earlier)
[19:58] <cjwatson> I guess I'll build some DVDs after UNE i386
[19:58] <cjwatson> oh, hell, will need to wait for ubiquity for that anyway, and respin UNE for it
[19:58] <cjwatson> ev: now blocked
[19:59] <ev> cjwatson: already uploaded
[19:59] <ev> haven't got the mail yet though
[19:59] <cjwatson> ah
[19:59] <cjwatson> should arrive in a minute or so
[20:01] <cjwatson> ev: po/Makefile.in seems to keep flipping back and forward between in the package and not in the package
[20:01] <cjwatson> might benefit from a better clean rule or something
[20:01] <ev> indeed, will do
[20:02] <cjwatson> accepted though
[20:12] <cjwatson> really must make publish-queue faster, by caching or something
[20:15] <NCommander> cjwatson: that looks sane, but probably needs a smoke test
[20:16]  * NCommander was going to implement it as a command line switch ...
[20:18] <cjwatson> I figure it should behave as we want it to behave by default
[20:19] <NCommander> cjwatson: well, if we ever get 3D, although it won't exist until natty at the earlist
[20:20] <cjwatson> guess we can worry about it then
[20:21] <NCommander> cjwatson: indeed. Thanks
[20:29] <cjwatson> dinnertime; will likely be at least an hour until more spins are usefully possible
[20:51] <kees> cjwatson: hi! do you have any plans to respin ISOs in the next day? I'm trying to coordinate a security publication. it's currently embargoed, but if you're going to respin, I'd like to get it out asap, otherwise I can wait until maverick is unfrozen.
[21:24] <cjwatson> kees: planning to respin Ubuntu and Kubuntu desktops shortly, plus all arm and DVDs
[21:25] <kees> cjwatson: define "shortly" ?
[21:25] <kees> I suspect I should just probably wait until beta unfreezes. :)
[21:25] <cjwatson> I thought it would be 10 minutes, but ubiquity needs another hotfix, so a couple of hours
[21:26] <cjwatson> msg me the details?
[21:28] <kees> sent
[21:37] <slangasek> cjwatson: do you want to hand off any of this to me so you can have an evening?
[21:44] <cjwatson> not sure yet, K is tired and might go to bed early
[21:53] <cjwatson> I think I'll want to hand some of it off, just not sure what yet
[21:54] <slangasek> ack
[21:59]  * slangasek wonders who's still passing around bad recommendations about installing the 'grub' package
[22:00] <cjwatson> the grub/Windows issues I blogged about recently are another source of this
[22:00] <cjwatson> grub legacy's stage 1.5 is smaller and so less likely to suffer from it, though it does still happen
[22:01] <cjwatson> (in fact I was thinking of backporting the workaround to legacy once I have it safely sorted out in 2)
[22:03] <slangasek> ah
[22:03] <slangasek> well whoever is telling people to install grub should tell them how to bloody configure it
[22:03] <slangasek> instead of just telling them to install the package, which doesn't help anything
[23:04] <cjwatson> I've added caching to publish-queue, so it's now MUCH quicker to run
[23:05] <cjwatson> as in seconds rather than approaching ten minutes
[23:10] <ScottK> Nice
[23:12] <ScottK> cjwatson: Do you still want the livecd-rootfs changes in?
[23:15] <cjwatson> yes please
[23:16] <ScottK> cjwatson: Done
[23:18] <cjwatson> thanks
[23:21] <cjwatson> server installations are failing to boot after installation (reported by marjo); investigating
[23:40] <marjo> thx cjwatson
[23:44] <cjwatson> I wonder if your netbook is PAE-capable
[23:44] <cjwatson> I see it in kvm, but kvm has given me grief with PAE in the past


[03:28] <BobJonkman> Is Freenode alive again?
[03:28] <BobJonkman> Netsplits galore today
[17:07] <Azeban> Hello hello hello.
[17:08] <Azeban> good afternoon
[19:21] <BobJonkman> Hello Azeban!
[21:31] <Azeban> how are you bob


 Small status update: … - Fixed qttools, this allowed me to retry a dozen of failed riscv64 builds. I will be able to retry more when kxmlgui is built on riscv64. … - Copied qbs 1.14 from Debian. This is not the latest release, but 1.16 will take more time because it will need to pass Debian's NEW queue. But it should be already compat
 module qtqml is not installed :/
 Where is that?
 (Photo, 1280x865) https://i.imgur.com/opOlznR.jpg
 sddm startup
 Something needs to depend on qml-module-qtqml
 is that new?
 Yes, it is new. Looks like qml-module-qtquick-controls needs that dependency (it needs a new upload because of tests anyway).
 @mitya57 [Yes, it is new. Looks like qml-module-qtquick-controls needs that dependency (it …], Makes sense. Thanks :)
 Installing that fixes sddm and plasma
 Great!
 Had to use proposed as webengine picked up a dep on the new re2 lib in there, but things seem ok in a very quick VM test now
 Fixed dde-qt5integration
 We need a helper that will automatically add QML dependencies based on plugins.qmltypes
 I might start test building new plasma against the PPA later
 Do anyone know nature of this patch? https://packaging.neon.kde.org/kde/kwallet.git/tree/debian/patches/blowfish_endianess.diff?h=Neon/unstable
 `#define Q_BYTE_ORDER Q_BIG_ENDIAN` (which was in original file and not patched out) looks very wrong
 @bhushanshah [Do anyone know nature of this patch? https://packaging.neon.kde.org/kde/kwallet. …], debian/changelog says it was added for this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828160
 @mitya57 [Yes, it is new. Looks like qml-module-qtquick-controls needs that dependency (it …], Added in https://salsa.debian.org/qt-kde-team/qt/qtquickcontrols/-/commit/cb684fa064063135, will be in the next upload to PPA.
 So just as a note : https://bugs.kde.org/show_bug.cgi?id=362805#c19 new upstream patch in kwallet breaks existing wallets with debian patchset
 So you will have to revert part of upstream patch for next release
 @bhushanshah [So you will have to revert part of upstream patch for next release], I'm slightly lost, but I guess follow what you do in Neon?
 More or less yes
 https://cgit.kde.org/kwallet.git/commit/?id=850219f83e7d74621efba9cf8a6eebb11f6bc3fc essentially revert of this will be needed
 right
 Hopefully fixed gammaray, qgis and qtav. The major remaining package is qtcreator, which is better with new qbs, but now has error installing the documentation.
 Looks like that error was always there, but now is fatal because of https://code.qt.io/cgit/qt/qtbase.git/commit/?id=20e9422e069a27b7
 I think I fixed everything now, we should just wait until it builds :)
 :)
 new perl just landing in proposed which makes pkg-kde-tools impossible to install in builds :(
[19:49] <mamarley> RikMills: It looks like libclass-xsaccessor-perl and possible libcommon-sense-perl need rebuilds.
 For Qt transition, we need to wait for a few builds to finish and then it will be good to land.
 @RikMills Feel free to do that if I will be sleeping :)
 (Or you want to wait until perl is fixed?)
 I'll think about that. I will check in a couple of hrs before I sleep
[20:08] <valorie> y'all are heroes!
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960856
 I think we may as well land.
[22:41]  * RikMills clicks buttons
[22:54] <RikMills> 5.14.2 landing
[23:20] <mamarley> \o/ Great job!
[23:22] <mamarley> Also, it looks like https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987 is going to get some attention very soon.  That package is also needed for kwayland-server.


[01:08] <MACscr> any advice for simply switching to the virtual kernel and thus updates will keep using thew newest virtual kernel as well?
[01:26] <jak2000> hi all
[01:27] <jak2000> how to change the ip of the server?
[09:22] <lordievader> Good morning.
[10:12] <Gregor3000> hello i need help with SSH i keep getitng the passphrase qustion: Authenticating with public key "imported-openssh-key" ; Passphrase for key "imported-openssh-key":
[10:12] <Gregor3000> once i enter it it authenticates but when i exit and try to login again it asks for password again.
[10:13] <Gregor3000> i am using putty and i imported the linux key hence the comment -  "imported-openssh-key"
[10:14] <lordievader> Gregor3000: The passphrase is whatever you set it to.
[10:16] <Gregor3000> i've entered it but when i logout and again log back in i again get the prompt. i dont' want the server to asks for passphrase every time
[10:16] <Gregor3000> PasswordAuthentication no
[10:16] <Gregor3000> ah it means i need to create a key with no passphrase?
[10:37] <lordievader> Gregor3000: No, that is a bad idea. You need to run an ssh agent.
[11:57] <StathisA> need some help with apticron...had it all working correctly - sending daily notification from cron.d etc, but had to change the notification time. Now whatever time I enter I do not get any notifications. If I manually do a "sudo apticron" I get the notification alright
[11:57] <StathisA> so smth is wrong with the cron.d schedule?
[11:58] <StathisA> syslog : Jun 14 14:10:01 servername CRON[1008]: (root) CMD (if test -x /usr/sbin/apticron; then /usr/sbin/apticron --cron; else true; fi)
[11:58] <StathisA> but nothing else after it
[11:58] <StathisA> if i do a manual "sudo apticron" I see the mail going out in the syslog...
[11:59] <StathisA> via localhost postfix
[11:59] <StathisA> and I receive it too on my mailbox
[11:59] <StathisA> so somethings up with the cron job i think
[12:38] <YamakasY> any help with building a sssd package ?
[13:48] <DWSR> Hey all, I have installed Ubuntu Server 14.04 into a Hyper-V VM. I installed linux-virtual through apt but it is not being loaded by default and there is no grub menu to select which kernel I want. How do I remove all of the generic kernels from my system and force virtual?
[14:08] <DWSR> Hey all, I have installed Ubuntu Server 14.04 into a Hyper-V VM. I installed linux-virtual through apt but it is not being loaded by default and there is no grub menu to select which kernel I want. How do I remove all of the generic kernels from my system and force virtual?
[14:16] <RoyK> DWSR: AFAIK the virtual kernel package is just a metapackage these days
[14:16] <RoyK> DWSR: the normal kernel packages work well
[14:19] <DWSR> Oh, really? :(
[14:19] <DWSR> RoyK: Someone should tell Microsoft then: https://technet.microsoft.com/en-us/library/dn531029.aspx?f=255&MSPPError=-2147217396
[14:21] <DWSR> Ah yes, you are correct.
[14:21] <DWSR> http://packages.ubuntu.com/trusty/linux-virtual
[14:21] <DWSR> When did that change?
[14:26] <RoyK> DWSR: not sure - some years back
[14:27] <DWSR> Oh well, that answers that. Might build a custom kernel that strips out some of the hardware support.
[14:30] <RoyK> no need
[14:31] <RoyK> drivers are only loaded when needed
[14:32] <RoyK> DWSR: do you have problems you're seeking to fix, or is it just the thought?
[14:34] <DWSR> RoyK: I'm a bit constrained on resources, so making the kernel smaller seems like a reasonable way to optimize.
[14:35] <DWSR> But I completely forgot about DDL.
[14:36] <DWSR> Eh, probably more trouble than it's worth, then
[15:41] <jak2000> hi all
[15:41] <jak2000> how to disable, my server sleep, i dont want the server sleep, tahnks
[17:18] <xperia> Hi all. My Ubuntu Server is under a spam attack at the moment and i need help with ip tables to block this Spammers. My question is how can i list all the tables with iptables so i can only export a specific table or better target. i have a script that log all attacks and i can create a file list specific for iptables to import it but i need to know how exactly this file need to look a like.
[17:48] <zermanno> Hi, which are the common ways to analyze log files? As an example, how people query apache logs?
[18:09] <teward> is there a way for me to force IPv4 resolution preferable to v6 on servers?
[18:09] <teward> i haven't set up v6 routing yet on some of my VPSes so they fail updates, i'm just doing manual v4 /etc/hosts entries
[18:09] <teward> (14.04 VPSes)
[18:10] <maswan> don't configure a global v6 address if you don't have it working?
[18:12] <teward> maswan: i don't have one configured?
[18:12] <teward> unless something is doing it without telling me
[18:12]  * teward shrugs
[18:12] <teward> i should set up at least one v6 imo *shrugs*
[18:13] <maswan> ip addr list
[18:13] <maswan> will tell you
[18:13] <jelly> maswan: the resolver library tends to give AAAA records in some cases regardless of a globally routable ipv6 being set up or not
[18:14] <maswan> Ok, I don't run many v4-only systems anymore
[18:15] <maswan> but that used to be the semantics of it
[18:16] <teward> it's only a temporary thing, but meh
[18:16] <teward> v6 is finnicky on this box
[18:16] <teward> s/this box/these boxes/
[18:17] <teward> mm, looks like v6 is still getting set as a route
[18:17] <teward> but then it fails
[18:32] <teward> god i hate myself
[18:32] <teward> i accidentally ip6tables'd the rules such that lo was accepted but RELATED,ESTABLISHED going outbound from apt and such was getting bounced
[18:33] <teward> routing was fine though apparently :/
[19:42] <RoyK> teward: hehe
[22:29] <xperia> hi all. what is the best way to increase the amount of possible parallel connection for apache2 on ubuntu. sometimes i have spamer attacks with over 1000 Connection that blocks everything at once. need help with this. thanks for any tips.
[22:32] <bekks> Drop his connections instead of pointlessly increasing the total number of connections.
[22:35] <xperia> bekks: thanks a lot for your tip. yes droping the connection sound good but how can i find out which connection to drop and if possible to log this droped connections so i can use iptables.
[22:35] <bekks> Investigate your webservers log files.
[22:36] <xperia> i dont see any errors for timeouts in the apache log files. not sure if apache logs tmeouts by default.
[22:36] <bekks> Why do you search for timeouts?
[22:37] <bekks> Investigate the log files to see how and from where your spamming is actually spamming.
[22:37] <bekks> It has nothing to do with timeouts. Timeouts only occur of your webserver cant handle the requests anymore.
[22:39] <xperia> bekks: for what else should i search else ? the connections by apache are closed after 10 seconds timeouts so it would be good to log this problematic connections. i dont see however this spammer connection anywhere in the logs however i see them on the router allways in a 10 Minute Interval.
[22:40] <bekks> I just told you what to look for.
[22:46] <xperia> okey i have found a good monitor tracker for apache2 to get a insight what is going on with the server. think this will help a little to isolate the problem much more.


[08:33] <lordievader> Good morning.
[11:04] <clivejo> hi lordievader
[11:05] <soee_> >_<
[11:07] <clivejo> yofel: you about?
[11:22] <lordievader> Hey clivejo, how are you doing?
[11:23] <lordievader> Relieved some stress from yesterday?
[11:27] <clivejo> not really
[11:28] <clivejo> need help
[11:28] <clivejo> if I could just get a yes or a no whether Im doing these merges correctly
[11:29] <lordievader> Unfortunately I cannot help you with that.
[11:30] <clivejo> so Im just playing about with packaging kolab
[11:37] <yofel> clivejo: pong
[11:38] <clivejo> hi yofel would you check over my merges
[11:43] <yofel> clivejo: I'll probably won't review everything, but I'll look at some of them
[11:44] <clivejo> I need help with kio too
[11:44] <clivejo> Ive really messed it up :(
[11:44] <yofel> saying that, the changelog in knetwalk is wrong
[11:45] <yofel> frameworks kio?
[11:46] <clivejo> yes
[11:47] <yofel> could you push your changes somewhere so I can see them?
[11:49] <clivejo> yofel: there are a few changes
[11:51] <yofel> well, I need to see them *somehow*. You can also git add everything then pastebin the output of git diff HEAD
[11:51] <yofel> that should show all changes
[11:51] <yofel> as long as you didn't commit anything yet
[11:51] <clivejo> Ive only touched the unstable branch
[11:52] <yofel> ok, there we go. Now I know where to look :)
[11:52] <clivejo> but I created a stable branch
[11:53] <clivejo> and thats when things started going haywire :(
[11:53] <clivejo> theres a new lib libkf5kiogui
[11:53] <clivejo> so I added two new packages libkf5kiogui5 and libkf5kiogui5 -dev
[11:54] <clivejo> but somehow I seems to have done a merge of master into unstable
[11:54] <yofel> do frameworks even need a stable branch?
[11:55] <yofel> and remove  libkf5kiogui5 -dev, the content belongs into kio-dev
[11:56] <yofel> http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/diff/debian/libkf5kiogui5.install?h=kubuntu_unstable&id=0e3e08096a4ead8b06a8610277d5f17ceb21d184
[11:56] <yofel> please wildcard the api version away.
[11:57] <clivejo> how do you keep local branches separate?
[11:59] <yofel> I don't quite get your question. Local branches are kept separate by different names. Remote branches are namespaced using their remote by default
[11:59] <yofel> e.g. local kubuntu_unstable trackes remote origin/kubuntu_unstable
[11:59] <clivejo> like if I want to build it locally and make changes to try and fix it
[11:59] <yofel> you commit without pushing?
[11:59] <clivejo> sometimes these "experiental" changes are getting into the branch and being commited
[12:00] <yofel> always read the git diff output before committing
[12:00] <clivejo> Id intended to keep them local
[12:00] <yofel> aah
[12:01] <yofel> you have changes that you only want to keep in your local env
[12:01] <yofel> the thing intended for managing that would be git stash
[12:01] <clivejo> well for example I just pasted in the files here - http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/diff/debian/libkf5kiogui5.install?h=kubuntu_unstable&id=0e3e08096a4ead8b06a8610277d5f17ceb21d184
[12:01] <clivejo> but then changed it locally and build it
[12:02] <clivejo> but it seems to have take my "experimental" changes and commited them
[12:02] <yofel> nothing ever gets committed without you running git commit
[12:03] <yofel> so please explain a bit more detailed what you actually did
[12:03] <clivejo> I use git gui to commit
[12:03] <clivejo> I stage and commit them in git gui
[12:03] <yofel> then you need to be careful about what you stage..
[12:04] <clivejo> then push using git push origin kubuntu_unstable
[12:05] <clivejo> I stage the final version, but sometimes it only stages changes I made a while back
[12:05] <clivejo> its a bit crazy
[12:05] <yofel> well, I haven't used git gui in a long time, so I can't help you with that
[12:06] <yofel> but it's probably a good idea if you run git diff before pushing
[12:06] <yofel> + git status
[12:06] <yofel> just to be sure that what you're pushing is what you want to push
[12:07] <clivejo> so wildcard usr/lib/*/libKF5KIOGui.so.5.* ?
[12:07] <clivejo> is there a way to remove that kubuntu_stable branch?
[12:08] <yofel> yes
[12:08] <yofel> no
[12:09] <clivejo> Ill do that later, have some work to do outside
[12:09] <yofel> you are not allowed to delete branches on alioth
[12:13] <apol> can somebody take a look at this bug report? https://bugs.kde.org/show_bug.cgi?id=359120
[12:13] <apol> looks like a packaging issue in Kubuntu
[12:16] <shadeslayer> I don't see the log
[12:16] <shadeslayer> ah
[12:16] <shadeslayer> nvm
[12:17] <shadeslayer> installng intel microcode removed packages 0.o
[12:24] <lordievader> Err, wut? Why? What did it remove by the way?
[12:36] <Mirv> FYI I filed FTBFS bug against kblog and ktnef bug #1543093
[13:01] <maxyz> Are you really planning to add a new -dev package in kio for the new favicons thingy?
[13:01] <maxyz> All the other parts are in kio-dev.
[13:03] <blaze> maxyz: i guess no
[13:03] <blaze> clivejo: ^
[13:05] <maxyz> There is a thread about kdeconnect in the list pkg-kde-talk that needs some input from the kubuntu side of things.
[13:05] <BluesKaj> Hey folks
[13:05] <maxyz> And it would be nice is we can consider pkg-kde-talk a list were we can coordinate some things.
[13:12] <blaze> it would be nice to have akonadi-server deps done in a debian way
[13:13] <yofel> there are reasons why mysql is handled the way it is
[13:14] <maxyz> I've recently realized that mysql-server-core was missing in the mysql backend dependencies.
[13:14] <blaze> i know, but still mysql backend is the default one
[13:14] <yofel> unless akonadi learns runtime backend support detection, uninstalling mysql is not an option
[13:16] <maxyz> Also, mysql is the only reasonably supported backend
[13:18] <blaze> hopefully akonadi-nextgen will be ready soon
[13:46] <maxyz> thunderbird works... :)
[13:48] <sitter> maxyz: I am pretty sure the understanding was that all kubuntu people with commit access are to subscribe to pkg-kde-talk so it's more a problem of not reading/answering than not being subscribed (:
[13:54] <maxyz> sitter: Ok, I have an answer in draft, but every time I read I re write it.
[15:04] <sitter> clivejo, yofel: jobs updated. took a bit longer than expected unfortunately
[15:04] <sitter> clivejo: I am pretty sure the job count is broken or something ... notice how the installation count dropped for no apparent reason rather substantially https://wiki.jenkins-ci.org/display/JENKINS/Countjobs+Viewstabbar
[15:04] <clivejo> maxyz: do you have access to delete a branch on alioth?
[15:04] <sitter> I think if you want it back you'll have to file a bug and/or find someone to look into it
[15:07] <sitter> oh oh, I also ripped out 'discover' to not have confusion there
[15:07] <clivejo> is it plasma-discover now?
[15:09] <sitter> yeah
[15:09] <clivejo> nice :)
[15:12]  * BluesKaj still uses muon
[15:21] <clivejo> yofel: regarding knetwalk, the changelog didnt get staged with my commit
[15:22] <clivejo> I dont understand why this is happening
[15:23] <clivejo> http://paste.ubuntu.com/14993712/
[15:24] <clivejo> how did git-buildpackage-ppa work?
[15:28] <maxyz> clivejo: There is a hook that forbids that, but it can be done, directly or disabling the hook
[15:28] <clivejo> maxyz: apologies, I went a bit crazy over the weekend
[15:29] <maxyz> clivejo: I was planning on updating the hook to forbid the deletion of non merged branches
[15:29] <clivejo> maxyz: for some reason I convinced myself that KCI needed a kubuntu_stable branch to work
[15:30] <clivejo> maxyz: how do you get the information to write a description of a package?
[15:31] <clivejo> for example that kiogui lib, where do you go to find out what it is?
[15:32] <maxyz> clivejo: For libraries the api is usually a good start, the code is in src/gui 1 .h file, so it was easy enough
[15:34] <clivejo> maxyz: https://quickgit.kde.org/?p=kio.git&a=tree&h=b3c4f8d89813c326ecc31ce2f3e8c92901532494&hb=8d016d2950778168a9deb90bd51a1d78f91e7705&f=src%2Fgui
[15:34] <clivejo> where does it say what the lib does?
[15:35] <maxyz> clivejo: The cmakelist lists the source files that are part of the KF5KIOGui library, in this case    faviconrequestjob.cpp
[15:37] <maxyz> The faviconrequestjob.h has a doxygen documentation of the API. which only add a support for faviconrequests. So the name "kiogui" is quite bad.
[15:52] <yofel> clivejo: did you maybe commit but not push? Then git-buildpackage-ppa would work..
[15:53] <clivejo> Im sure I pushed
[15:55] <clivejo> when I do git merge master, if everything goes ok does it autocommit?
[15:56] <clivejo> Merge branch 'master' into kubuntu_xenial_archive that is the automatic generated commit message
[16:13] <sheytan> Guys, can someone tell me how to fix this bug? http://img-9gag-fun.9cache.com/photo/ajA5xwq_460s.jpg
[16:16] <yofel> clivejo: yes
[16:17] <yofel> should also be the commit message for non-automatic merges
[16:17] <clivejo> should I be doing it in two steps?
[16:18] <clivejo> the merge first, commit, then fix the changelog & new release?
[16:20] <clivejo> yofel: why has master got an UNRELEASED in it?
[16:20] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/applications/signon-kwallet-extension.git/tree/debian/changelog
[16:20] <clivejo> line 45
[16:20] <yofel> if you do it like that then it's pointless to split the steps
[16:20] <yofel> merge --no-commit, fix changelog, commit, new release
[16:20] <yofel> is something I tried once. But that's more hassle than it's worth IMO
[16:21] <yofel> looks like we never released it?
[16:21] <clivejo> does that belong in master?
[16:22] <yofel> ah wait master
[16:22] <clivejo> yeah debians master branch
[16:22] <yofel> I guess that was simply merged before we released that. Can probably be removed
[16:22] <yofel> AFTER merging in the new changelog entries
[16:23] <yofel> it's not just us merging in debian, the other way happens too
[16:24] <clivejo> yofel: http://anonscm.debian.org/cgit/pkg-kde/applications/signon-kwallet-extension.git/commit/?h=kubuntu_xenial_archive&id=522030fa0d547ad82834b99f7f17a107f58ccd74
[16:31] <clivejo> I think Im causing more problems than Im fixing with these merges
[16:40] <maxyz> clivejo: I'll fix that in signon-kwallet-extension master branch
[16:41] <clivejo> maxyz: thanks :)
[16:42] <clivejo> maxyz: how do you know which KDE applications have been changed?
[16:42] <clivejo> do you have a script compares the source tarballs or something?
[16:43] <maxyz> clivejo, I check the diff against the previous release tag
[16:43] <clivejo> kde git?
[16:43] <maxyz> I import the tarballs, but kde.git should work.
[16:44] <clivejo> thats clever
[16:45] <clivejo> are you the main KDE packager then?
[16:48] <maxyz> clivejo: for now, yes, I'm trying to replace myself with jenkins or something like that.
[16:49] <clivejo> you cant be replaced!
[16:50] <clivejo> how long have you been packaging?
[16:51] <maxyz> kde, 2 years, or so. Random stuff in Debian, ~10 years.
[16:52] <clivejo> do you have any experience with kolab?
[16:55] <maxyz> At what level? I never used it, but I uploaded some versions of the libs with the help of detrout. heffee works there so he should probably know more about it.
[16:55] <clivejo> Im trying to package it on Launchpad
[16:55] <clivejo> but Im having trouble with the existing packaging
[16:56] <maxyz> I wanted to add the dovecot support to debian some time ago, but I use SOGo, which is ugly, but it works, so it's not really worth the change for me.
[18:58] <BluesKaj> !project neon
[19:00] <genii> BluesKaj: CI now
[19:04] <BluesKaj> genii, yeah, but I read something here the other day about new a project neon
[19:04] <BluesKaj> anew
[19:05] <acheron88> http://neon.kde.org.uk/
[19:07] <BluesKaj> something about JR announcing it
[19:08] <acheron88> he did at FOSDEM, a week ago on sunday
[19:09] <BluesKaj> it was in the rss feeds https://dot.kde.org/2016/01/30/fosdem-announcing-kde-neon
[19:09] <acheron88> not sure if the video of his talk is there yet?
[19:14] <BluesKaj> asume this a new neon project, separate from the old one
[19:16] <genii> Seems to be no pool/ there
[19:18] <acheron88> genii: the neon repo?
[19:23] <BluesKaj> all this publicity about new plasma desktops but there's is no comprihensive guide for them, for example activities has a whole lot of hype, but I've yet to find any tuts for them that actually help make it work
[19:23] <genii> Yep
[19:25] <BluesKaj> correction: make them work :-)
[19:26] <acheron88> http://archive.neon.kde.org.uk/unstable/pool/
[19:26] <clivejo> BluesKaj: ask in #kde-neon ?
[19:28] <BluesKaj> looking for a method to assign apps that launch inside anactivity when the activity itself is launched, supposedly there's a method to do that, but the only one i found doesn't do what it claims
[19:31] <BluesKaj> clivejo, I'm not compaining about neon's apps whatewver they might be, just the activities in plasma 5
[19:32] <clivejo> BluesKaj: I guess my point is that this is Kubuntu development, at the moment we have nothing really to do with Neon and how it operates
[19:34] <lordievader> BluesKaj: It is called KDE Neon, to avoid confusion (a little) with Project Neon.
[19:34] <lordievader> And the video ain't available yet.
[19:34] <BluesKaj> yeah it's only in the sense that KDE/plasma is the Kubuntu desktop
[19:34] <BluesKaj> I'm not bothering with neon , just to clarify :-)
[19:37] <BluesKaj> I have enough desktop freezes happening here of late, I don't need any more
[19:42] <blaze> in a week or so qt5.6rc will arrive, that would be a good sign
[20:13] <clivejo> yofel: would you look at marble please
[20:42] <clivejo> yofel: Debian dropped the epoch in this package http://anonscm.debian.org/cgit/pkg-kde/applications/libkmahjongg.git/commit/?id=f36da2301091ad464370795f81039c7d3291abbd
[20:42] <clivejo> can we rename and do the same?
[22:17] <clivejo> anyone installed kubuntu-desktop on xenial?
[23:05] <valorie> clivejo: I could -- what is the question?
[23:06] <clivejo> does it install?
[23:15] <valorie> I'll start it up and try that
[23:18] <valorie> updating first though
[23:36] <yofel> clivejo: yes, we should do the rename as well
[23:37] <yofel> marble will have to wait for tomorrow
[23:42] <valorie> is the broken installer our problem, or ubuntu's problem?
[23:42] <valorie> someone was asking last night about the daily ISO -- and s/he is among many reporting a broken installer
[23:42] <valorie> we can't release that way...
[23:43] <clivejo> did you install Ubuntu first?
[23:43] <yofel> ours, ubuntu just broke it
[23:44] <yofel> well yeah, but fixing the installer can be done after feature freeze, unless someone really wants to take care of that
[23:44] <clivejo> only two months left :/
[23:44] <clivejo> tick tock
[23:45] <yofel> what 2 months?
[23:45] <yofel> feature freeze is in 1.5 weeks
[23:45] <clivejo> release
[23:46] <clivejo> 16.04?
[23:46] <clivejo> maybe they'll wait til 16.06?
[23:46] <yofel> release yes, but that's not the only milestone we need to pay attention to
[23:46] <yofel> no
[23:48] <clivejo> 16.07?
[23:49] <yofel> now you're just plain delusional :P
[23:49] <valorie> yofel, good point
[23:49] <valorie> having it broken does keep people from testing, though
[23:50] <valorie> darn it, in my xenial upgrade I missed the chance to tell it to use the new configs


[00:24] <wgrant> helmut: Thanks for poking us about that. Do you have a timeline for those packages starting to land in sid?
[03:55] <DalekSec> (Instrusted to try asking here.) So why is it when I use bzr lp-propose (with or without target branch), it seemingly randomly targets whatever it wants, not what I specify?  Most recently, I targetted nothing and it errord out, I targetted branch/utopic and it tried to submit to branch/trusty.
[04:01] <wgrant> DalekSec: How are you invoking it?
[04:08] <DalekSec> bzr lp-propose  or  bzr lp-propose lp:~xubuntu-dev/ubuntu-seeds/xubuntu.utopic   or   bzr lp-propose bzr+ssh://bazaar.launchpad.net/xubuntu-dev/ubuntu-seeds/xubuntu.utopic/
[04:12] <DalekSec> Also tried putting in some "saved" location in .bzr/branch/branch.conf
[04:15] <wgrant> DalekSec: It's working fine for me. Which version of bzr are you using?
[04:16] <wgrant> ubuntu-seeds has no development focus, so there will be no default.
[04:16] <DalekSec> Installed: 2.6.0+bzr6593-1ubuntu1.1
[04:17] <DalekSec> It'd be a great tool, but it works about 30% of the time.:/
[04:21] <DalekSec> But yeah, happens on many different repos, that's just the latest. :/
[04:26] <wgrant> DalekSec: It's a bug in bzr. It tries to turn the given submit branch URL into a Launchpad API URL using lp_api.LaunchpadBranch.from_bzr, which calls candidate_urls, which looks up the branch's parent branch.
[04:27] <wgrant> I'm not sure why it doesn't use bzr_branch.base
[04:27] <wgrant> But I'd be filing a bug against bzr.
[04:29] <DalekSec> I would if I knew what was going on more than bzr being bzr..  I'll use that info and see if I can find any reported bug.
[04:34] <DalekSec> Hrm, perhaps 1078211.
[04:35] <wgrant> Yup, that looks like it.
[04:36] <DalekSec> wgrant: As always, thanks for your help.  Do you ever stop looking here? :P
[04:36] <wgrant> Sometimes for almost eight hours a day!
[04:36] <DalekSec> \o/
[04:37] <DalekSec> Welp, have a good night.
[04:37] <wgrant> Night.
[04:47] <helmut> wgrant: we are in the process of updating the tools and updating the infrastructure. the next steps (hopefully) are uploading to wheezy-backports, updating ftp-master's installation and then uploading to experimental. I think sid should be safe for a month at least.
[04:48] <wgrant> helmut: Thanks. experimental's interesting for us too. I can easily formulate some example packages to test, but are there some existing samples?
[04:49] <helmut> wgrant: there are quite a few patches in the debian bts. most of them are in bug reports blocked by #744246
[04:49] <helmut> (that's a debian number)
[04:50] <wgrant> helmut: Thanks.
[04:50] <helmut> wgrant: one thing I'd like to see become common is Build-Depends: myownbinarypackage <profile.cross>
[04:51] <helmut> wgrant: that's a good test-case, because it uses a profile in a positive way, so you need to ignore this build-dependency unless the cross profile is activated.
[04:54] <helmut> wgrant: cjwatson pointed out to me that lp:launchpad-buildd and sbuild likely need changes. I didn't check the former, but patches for the latter can be found at http://bugs.debian.org/731798
[04:55] <helmut> since debian traditionally uses a different sbuild package from the one in sid, this bug may stay open even after using build profiles.
[04:55] <wgrant> helmut: Our sbuild is currently a fork of DSA sbuild from ~2004, so sadly the patches won't be terribly useful. Until we upgrade to something more modern, I intend to do the minimum and just drop any dep that is restricted and doesn't have at least one negative term.
[04:56] <wgrant> That is the minimum, isn't it?
[04:56] <helmut> yes, that is perfectly ok and is what we are proposing the the wheezy-backports, see https://lists.debian.org/deity/2014/04/msg00142.html
[04:57] <helmut> there you can see example patches for dpkg and apt that support just the syntax without actually supporting profiles
[04:58] <helmut> and there is not much more to do anyway unless you actually want to use build profiles.
[04:58] <helmut> so just supporting the syntax may get you a long way.
[04:59] <helmut> the main use case currently is for cross-compilation and bootstrapping, where knowing what dependencies can be dropped in staged builds is cruicial.
[05:00] <wgrant> Yeah, exactly. We don't do early bootstrapping directly in Launchpad. We use a modern distro sbuild for that.
[05:01] <wgrant> Thanks.
[05:02] <helmut> if you have any other questions at a later time or need patch review, just ask. you'll reach those driving build profiles in oftc #debian-bootstrap
[05:02] <helmut> should I stumble accross more infrastructure pieces in Debian that likely have a match in launchpad, I shall notify you.
[05:04] <wgrant> helmut: Great. IRC or<EMAIL_ADDRESS>works, but I can't think of much else. I'll test it all out next week.
[05:05] <helmut> I see that launchpad will be faster in supporting build profiles than Debian will be.
[05:07] <wgrant> I'm hoping to avoid the unpleasantness back in 2010 of having to quickly implement 3.0 (quilt) just after it started landing it sid.
[05:08] <helmut> I guess that is why vorlon asked me to poke you.
[05:09] <helmut> wgrant: my plan is to use doxygen as a test package in experimental first and only if nothing breaks upload to sid.
[05:10] <wgrant> Sounds good.
[05:10] <wgrant> I hate the mess of loops around doxygen :)
[05:10] <helmut> in what ways did it cause grief to you?
[05:11] <wgrant> Oh, just the doxygen -> graphviz -> THE ENTIRE WORLD dep chain makes arch bootstraps annoying.
[05:11] <helmut> the profile stuff will not get around that issue
[05:12] <helmut> it only removes the qt dependency
[05:12] <wgrant> Ahh
[05:14] <helmut> on the bright side, bootstrapping is already in way better shape than it was recently (at least in sid) due to the amount of patches applied.
[05:15] <helmut> my personal interest resides mostly in https://wiki.debian.org/HelmutGrohne/rebootstrap </advertisement>


[01:31] <callmepk> good morning
[01:57] <duflu> Hi callmepk
[01:59] <callmepk> hi duflu
[06:43] <jpnurmi> good morning. hi callmepk duflu
[06:43] <duflu> Hi jpnurmi
[07:09] <didrocks> good morning
[07:09] <callmepk> hi jpnurmi didrocks
[07:09] <didrocks> hey callmepk
[07:09] <jpnurmi> hi didrocks
[07:13] <didrocks> hey jpnurmi!
[07:24] <duflu> Hi didrocks
[07:29] <didrocks> hey duflu
[08:02] <laney> moin
[08:03] <duflu> Hi laney
[08:09] <callmepk> hi laney
[08:15] <laney> hey duflu callmepk
[08:15] <laney> how's it going?
[08:16] <duflu> Pretty good. You, laney?
[08:17] <laney> yeah alright
[08:17] <laney> I had my second vax the other day. They warned me the side effects would be worse than the first one but actually they were better
[08:20] <duflu> laney, yeah everyone's different. I was surprised I had almost no reaction the first time and the second time was horrific
[08:22] <laney> :(
[08:22] <laney> that's true: there was someone in the post vaccine waiting area who was definitely not loving it
[08:27] <didrocks> hey hey laney
[08:27] <laney> what's up didrocks
[08:28] <didrocks> nothing special, more than 2 weeks after my second shot, no effect, lucky :)
[08:29] <laney> 2 weeks is time for FULL POWER!
[08:30] <didrocks> isn’t it? :)
[09:56] <GunnarHj> Hi laney, can you please approve ibus in the NEW queue. (Steve has fixed so gtk4 build on i386.)
[10:01] <laney> GunnarHj: I'll take a look in a bit, cheers
[10:20] <GunnarHj> laney: TIA
[14:53] <hellsworth> good morning desktopers
[14:53] <GunnarHj> Good afternoon hellsworth! :)
[14:55] <hellsworth> well hi there GunnarHj


[07:15] <lamont> BenC: lamont: I'm thinking it might be a good idea to add the ps/2 drivers to the ia64 edgy install
[01:49] <zul> hey
[01:54] <tonfa> hi
[01:54] <tonfa> by chance does anybody knows what command are used by the gnome-applet when hibernating/suspending ?
[04:02] <zul> bunch of tards
[08:30] <Mithrandir> BenC__: nfs-utils ftbfs due to UTS_RELEASE not being defined (http://librarian.launchpad.net/5071382/buildlog_ubuntu-feisty-i386.nfs-utils_1%3A1.0.10-4_FAILEDTOBUILD.txt.gz ) Any idea about that?
[08:56] <BenC__> Mithrandir: it's a bug in nfs-utils
[08:56] <BenC__> Mithrandir: it needs to #include <linux/utsrelease.h>
[08:57] <zul> kernel-headers have changed havent they as well
[08:57] <Mithrandir> BenC: ls: /usr/include/linux/utsrelease.h: No such file or directory
[08:57] <Mithrandir> (on feisty)
[08:58] <BenC> Mithrandir: my question is, why does it use UTS_RELEASE from userspace? That's incorrect
[08:59] <BenC> Mithrandir: if it's a userspace program, it should really be using uname() and utsname.release
[08:59] <zul> BenC: i ran into this when i was trying to port xen to 2.6.19
[08:59] <zul> i dont remember the fix right now
[08:59] <BenC> if it's actually a kernel bit (like for zul) then it needs to use utsrelease() in the kernel
[09:00] <BenC> or something like that
[09:00] <Mithrandir>  * Get version number of the kernel this was compiled for.
[09:00] <Mithrandir>  * This is NOT the same as calling uname(), because we may be
[09:00] <Mithrandir>  * running on a different kernel.
[09:00] <Mithrandir> I'm not sure what it needs it _for_, but that's why it's not using uname.
[09:00] <BenC> Mithrandir: the "kernel it was compiled for" is pretty bogus thing to assume from userspace
[09:01] <kylem> possibly structure versioning or something equally incorrect.
[09:01] <Mithrandir> BenC: this is the nfs userland bits; they reasonably need to stay very much in sync with the kernel.
[09:01] <zul> heh if gitweb was working for me i could point out where it changed
[09:01] <BenC> Mithrandir: then they very much need to use linux-headers instead of the libc-kernel-dev
[09:02] <BenC> libc-kernel-dev is by nature just what userspace needs...something tightly bound to kernel needs to use kernel headers
[09:06] <kylem> zul, use www2
[09:07] <kylem> oh, they're both broken. use hera.kernel.org/git/
[09:08] <zul> kylem: that works thanks
[09:10] <zul> doh i had it somewhere..
[09:14] <zul> ok maybe it was something else, but this what i ran into http://hera.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-2.6.git;a=commitdiff;h=96b644bdec977b97a45133e5b4466ba47a7a5e65;hp=e9ff3990f08e9a0c2839cc22808b01732ea5b3e4
[09:54] <ajmitch> great release name, sounds like an interesting week in SF :)
[09:55] <zul> or BenC is on crack
[11:30] <fabbione> BenC: CJA still has problems with her wireless... what should I poke?
[11:31] <BenC> fabbione: modprobe -r bcm43xx; modprobe bcm43xx
[11:31] <fabbione> oh ok
[11:31] <BenC> repeat until "iwlist eth1 scan" shows ap's
[11:31] <fabbione> feh ok
[11:31] <BenC> yeah, it sucks
[11:31] <kylem> yeah, broadcom has issues with bringingg the if up and down.
[11:31] <BenC> hold on, be right there
[11:33] <fabbione> git pull
[11:33] <fabbione> fatal: unexpected EOF
[11:33] <fabbione> Fetch failure: git://git.kernel.org/pub/scm/linux/kernel/git/bcollins/ubuntu-2.6.git
[11:33] <fabbione> kylem: please fix...
[11:33] <kylem> the kernel.org mirroring is fucked right now
[11:33] <fabbione> ok