[00:04] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_akonadi build #176: STILL FAILING in 34 sec: https://kci.pangea.pub/job/xenial_stable_akonadi/176/
[00:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #599: STILL FAILING in 36 sec: https://kci.pangea.pub/job/xenial_unstable_akonadi/599/
[00:04] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_akonadi build #177: STILL FAILING in 32 sec: https://kci.pangea.pub/job/xenial_stable_akonadi/177/
[00:07] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akonadi build #229: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/artful_stable_akonadi/229/
[00:08] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadi build #231: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/artful_unstable_akonadi/231/
[00:08] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kopete build #88: FAILURE in 19 min: https://kci.pangea.pub/job/bionic_stable_kopete/88/
[00:10] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kdb build #140: STILL FAILING in 33 sec: https://kci.pangea.pub/job/xenial_stable_kdb/140/
[00:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #254: STILL FAILING in 34 sec: https://kci.pangea.pub/job/xenial_unstable_kdb/254/
[00:10] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_messagelib build #240: STILL FAILING in 3 min 54 sec: https://kci.pangea.pub/job/xenial_stable_messagelib/240/
[00:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #486: STILL FAILING in 3 min 54 sec: https://kci.pangea.pub/job/xenial_unstable_messagelib/486/
[00:10] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_messagelib build #348: STILL FAILING in 2 min 51 sec: https://kci.pangea.pub/job/artful_unstable_messagelib/348/
[00:11] -kubuntu-ci:#kubuntu-devel- Project artful_stable_messagelib build #174: STILL FAILING in 3 min 53 sec: https://kci.pangea.pub/job/artful_stable_messagelib/174/
[00:12] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdb build #105: STILL FAILING in 2 min 42 sec: https://kci.pangea.pub/job/artful_stable_kdb/105/
[00:13] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdb build #191: STILL FAILING in 3 min 40 sec: https://kci.pangea.pub/job/artful_unstable_kdb/191/
[00:25] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kitinerary build #12: NOW UNSTABLE in 36 min: https://kci.pangea.pub/job/bionic_unstable_kitinerary/12/
[00:26] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #99: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/bionic_unstable_cantor/99/
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kopete build #56: STILL FAILING in 4 min 7 sec: https://kci.pangea.pub/job/xenial_stable_kopete/56/
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #266: STILL FAILING in 4 min 12 sec: https://kci.pangea.pub/job/xenial_unstable_kopete/266/
[00:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #191: FAILURE in 4 min 50 sec: https://kci.pangea.pub/job/artful_unstable_kopete/191/
[00:30] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kopete build #125: FAILURE in 4 min 50 sec: https://kci.pangea.pub/job/artful_stable_kopete/125/
[00:31] <Guest61335> hi, are people aware of a major bug in Plasma where if the screen resolution changes the settings for the panel are disregarded?
[00:42] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #106: STILL UNSTABLE in 1 hr 35 min: https://kci.pangea.pub/job/bionic_stable_cantor/106/
[00:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:42] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kdb build #122: FIXED in 33 min: https://kci.pangea.pub/job/bionic_stable_kdb/122/
[00:42] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #88: STILL UNSTABLE in 1 hr 34 min: https://kci.pangea.pub/job/bionic_stable_kalzium/88/
[00:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdb build #114: FIXED in 36 min: https://kci.pangea.pub/job/bionic_unstable_kdb/114/
[00:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkgapi build #69: STILL UNSTABLE in 1 hr 38 min: https://kci.pangea.pub/job/bionic_unstable_libkgapi/69/
[00:46] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_poxml build #98: FAILURE in 26 sec: https://kci.pangea.pub/job/bionic_stable_poxml/98/
[00:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #136: STILL UNSTABLE in 1 hr 40 min: https://kci.pangea.pub/job/bionic_unstable_ark/136/
[01:06] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #113: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/bionic_stable_ark/113/
[01:06] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdav2 build #94: FAILURE in 1 min 21 sec: https://kci.pangea.pub/job/bionic_unstable_kdav2/94/
[01:07] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kdenetwork-filesharing build #54: STILL UNSTABLE in 35 min: https://kci.pangea.pub/job/bionic_stable_kdenetwork-filesharing/54/
[01:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #134: STILL UNSTABLE in 2 hr 0 min: https://kci.pangea.pub/job/bionic_unstable_kstars/134/
[01:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #104: STILL UNSTABLE in 2 hr 2 min: https://kci.pangea.pub/job/bionic_unstable_amarok/104/
[01:20] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:20] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kopete build #89: FIXED in 54 min: https://kci.pangea.pub/job/bionic_stable_kopete/89/
[01:23] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #86: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/86/
[01:23] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kamoso build #100: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/bionic_unstable_kamoso/100/
[01:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kitinerary build #13: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/bionic_unstable_kitinerary/13/
[01:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdenetwork-filesharing build #75: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/bionic_unstable_kdenetwork-filesharing/75/
[01:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #194: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/194/
[01:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_xdg-desktop-portal-kde build #127: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/bionic_unstable_xdg-desktop-portal-kde/127/
[01:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kimap build #57: FAILURE in 30 min: https://kci.pangea.pub/job/bionic_unstable_kimap/57/
[01:47] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #89: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/bionic_stable_kalzium/89/
[01:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:47] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_poxml build #99: FIXED in 23 min: https://kci.pangea.pub/job/bionic_stable_poxml/99/
[01:47] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_polkit-kde-agent-1 build #116: STILL UNSTABLE in 1 hr 1 min: https://kci.pangea.pub/job/bionic_stable_polkit-kde-agent-1/116/
[01:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kimap build #392: STILL FAILING in 2 min 41 sec: https://kci.pangea.pub/job/xenial_unstable_kimap/392/
[01:48] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kimap build #130: STILL FAILING in 2 min 42 sec: https://kci.pangea.pub/job/xenial_stable_kimap/130/
[01:48] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kimap build #135: FAILURE in 2 min 46 sec: https://kci.pangea.pub/job/artful_stable_kimap/135/
[01:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kimap build #191: FAILURE in 2 min 46 sec: https://kci.pangea.pub/job/artful_unstable_kimap/191/
[01:49] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #137: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/bionic_unstable_ark/137/
[01:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:50] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdav2 build #95: FIXED in 26 min: https://kci.pangea.pub/job/bionic_unstable_kdav2/95/
[01:50] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_syndication build #125: STILL FAILING in 25 min: https://kci.pangea.pub/job/bionic_unstable_syndication/125/
[01:51] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ruqola build #168: STILL FAILING in 36 sec: https://kci.pangea.pub/job/artful_unstable_ruqola/168/
[01:51] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #195: FAILURE in 45 sec: https://kci.pangea.pub/job/bionic_unstable_ruqola/195/
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ruqola build #91: STILL FAILING in 37 sec: https://kci.pangea.pub/job/xenial_unstable_ruqola/91/
[01:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmailtransport build #113: STILL FAILING in 2 min 40 sec: https://kci.pangea.pub/job/bionic_unstable_kmailtransport/113/
[02:03] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #107: STILL UNSTABLE in 54 min: https://kci.pangea.pub/job/bionic_stable_cantor/107/
[02:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:07] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kimap build #58: FIXED in 21 min: https://kci.pangea.pub/job/bionic_unstable_kimap/58/
[02:07] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #135: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/bionic_unstable_kstars/135/
[02:21] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ruqola build #169: FIXED in 26 min: https://kci.pangea.pub/job/artful_unstable_ruqola/169/
[02:21] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ruqola build #92: FIXED in 26 min: https://kci.pangea.pub/job/xenial_unstable_ruqola/92/
[02:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkgapi build #70: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/bionic_unstable_libkgapi/70/
[02:21] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #196: FIXED in 26 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/196/
[02:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #105: STILL UNSTABLE in 57 min: https://kci.pangea.pub/job/bionic_unstable_amarok/105/
[02:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #100: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/bionic_unstable_cantor/100/
[02:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ruqola build #170: FAILURE in 3 min 51 sec: https://kci.pangea.pub/job/artful_unstable_ruqola/170/
[03:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #198: STILL FAILING in 27 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/198/
[03:12] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #147: FAILURE in 4 hr 3 min: https://kci.pangea.pub/job/bionic_unstable_kwin/147/
[03:44] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kmime build #129: FAILURE in 4 min 50 sec: https://kci.pangea.pub/job/bionic_stable_kmime/129/
[03:48] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libgravatar build #81: STILL FAILING in 17 min: https://kci.pangea.pub/job/bionic_unstable_libgravatar/81/
[04:20] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktorrent build #119: STILL FAILING in 6 min 49 sec: https://kci.pangea.pub/job/bionic_unstable_ktorrent/119/
[04:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmime build #124: FAILURE in 16 min: https://kci.pangea.pub/job/bionic_unstable_kmime/124/
[04:48] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #148: UNSTABLE in 34 min: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/148/
[04:53] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_akonadi build #151: STILL FAILING in 23 min: https://kci.pangea.pub/job/bionic_unstable_akonadi/151/
[05:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_pimcommon build #100: STILL FAILING in 11 min: https://kci.pangea.pub/job/bionic_unstable_pimcommon/100/
[05:42] <valorie> yikes: https://www.reddit.com/r/Kubuntu/comments/8fqrsf/kubuntu_1804_installer_crashes/?st=jgltg4ui&sh=19d582f4
[05:48] <valorie> https://www.reddit.com/r/Kubuntu/comments/8foojm/kubuntu_1804_freezes_at_try_kubuntu/?st=jgltlcoq&sh=20ad6df2
[05:48] <valorie> gosh, why *after* the release
[06:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmime build #526: STILL FAILING in 3 min 40 sec: https://kci.pangea.pub/job/xenial_unstable_kmime/526/
[06:32] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kmime build #137: STILL FAILING in 3 min 40 sec: https://kci.pangea.pub/job/xenial_stable_kmime/137/
 @acheronuk, so far so good ...
[07:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:18] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kmime build #130: FIXED in 14 min: https://kci.pangea.pub/job/bionic_stable_kmime/130/
[07:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmime build #125: FIXED in 15 min: https://kci.pangea.pub/job/bionic_unstable_kmime/125/
 gosh, why *after* the release
[07:44] <acheronuk> because pre-release testing cannot replicate all corner cases
[07:45] <acheronuk> so far, by far, problems are very few. not replicated much, so limited
[08:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitinerary build #3: STILL FAILING in 30 sec: https://kci.pangea.pub/job/xenial_unstable_kitinerary/3/
[08:13] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kitinerary build #3: STILL FAILING in 3 min 40 sec: https://kci.pangea.pub/job/artful_unstable_kitinerary/3/
[09:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:07] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdeclarative build #88: FIXED in 25 min: https://kci.pangea.pub/job/bionic_unstable_kdeclarative/88/
[09:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #660: STILL FAILING in 1 min 56 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/660/
[09:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #278: STILL FAILING in 4 min 19 sec: https://kci.pangea.pub/job/artful_unstable_kstars/278/
[09:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #148: FIXED in 35 min: https://kci.pangea.pub/job/bionic_unstable_kwin/148/
[09:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #136: FIXED in 35 min: https://kci.pangea.pub/job/bionic_unstable_kstars/136/
[10:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kitinerary build #14: STILL UNSTABLE in 56 min: https://kci.pangea.pub/job/bionic_unstable_kitinerary/14/
[11:09] <BluesKaj> Hey folks
[12:09] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2205: SUCCESS in 48 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2205/
[12:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2205: SUCCESS in 1 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2205/
[12:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2205: SUCCESS in 4 min 9 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2205/
[12:27] <itsfemme[m]> Does the kubuntu theme use system colors for the hilighting of the panels? I am trying to figure out how to edit those (from blue to something else) but I seem to have tried to edit all the colors to no avail. I tried to look through the these files for what svgz to edit and that also turned up short
[12:34] <acheronuk> itsfemme[m]: /usr/share/plasma/desktoptheme/default/widgets/tasks.svgz
[12:34] <itsfemme[m]> Thank you
[12:35] <acheronuk> https://i.imgur.com/t5QrCwN.png
[12:37] <itsfemme[m]> acheronuk: Do you get that view with the inkscape extension on the wiki?
[12:38] <acheronuk> not sure what you mean. I just opened in inkscape I have here. not done anything special I recall
[12:39] <itsfemme[m]> I mean the XML object view
[12:40] <acheronuk> likely I had that open for last think I looked at (logos likely), and it just remembered
[12:43] <itsfemme[m]> Ah, you are right it is called the Object Manager and is built into inkscape
[14:10] <fregl> hi, does anyone know why firefox works with highdpi in a ubuntu-gnome wayland session (18.04) but not with plasma-wayland? (it runs, but the scaling is horribly pixelated)
[14:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2206: SUCCESS in 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2206/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2206: SUCCESS in 1 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2206/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2206: SUCCESS in 4 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2206/
 @nggraham is it still possible to make suggestions for the window tiling shortcuts we talked about before? I saw you make a task in phab for it and wanted to offer some options
 all machines here upgraded to bionic with out hitch (ones which were not on it already and exluding neon)
 actually I want to make suggestions for keyboard shortcuts for changing like 80% of them lol
 @acheronuk, nice
 @MichaelTun, my concern with that is confusing the hell out of existing KDE users :P
 @acheronuk, meh
 if we dont change for the better for fear of the old then we will forever be held back by the chain
 but to be clear, I always want to push them upstream because so many default shortcuts are terrible.
 Desktop Grid = Ctrl+F8  . . . that isn't just bad, that is super uber mega crap
 I didnt realize those tiling shortcuts were going to be in 18.04. Those are better than nothing but they are problematic due to the limitations of KWin and since we know that KWin will not have any new X features the structure kind of has to change since it wont be compensated for
 the problem with changing shortcuts is mostly Martin
 I'm always up for it if the new one is better (IMHO) but Martin is incredibly conservative and you need to make an ironclad case that appeals to his sense of correctness
 he will accept it immediately if you can convince him that the existing ons is somehow incorrect or violates a spec
 all other arguments will fail
 As a distro, we have the ability to go against upstream and patch in our own shortcuts at the risk of unfamiliarity.
 we do, that's true
 but IMHO it's better tro try to do it upstream first
 Right.
 @nggraham, there are no specs for shortcuts that I've ever seen. … there is no correct so there technically cant be an incorrect. … it essentially would be "these would make it easier to use" argument
 I've had mixed luck with those, but it couldn't hurt to try. Can you make up a list of actions whose shortcuts you'd like changed, and to what?
 @nggraham, I agree with attempting upstream but not obey it blindly. :)
 @nggraham, that is what I am planning. There are quite a few. Essentially I am going to address all of the defaults and see if they need replacing or not
[23:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1089: SUCCESS in 5 min 58 sec: https://kci.pangea.pub/job/mgmt_merger/1089/
[23:52] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #108: STILL UNSTABLE in 45 min: https://kci.pangea.pub/job/bionic_stable_cantor/108/


[00:29] <brenopolanski> someone writing the documentation of Juju to portuguese/brazil (https://github.com/juju/docs)
[00:29] <brenopolanski> ??
[00:42] <magicaltrout> hey marcoceppi my fellow charmer brenopolanski is interested int committing some PR/BR translations, do you have any way of accomodating that stuff yet?
[07:28] <kjackal> Good morning Juju world!
[12:45] <dougi> Hi. im try to install openstack... im jusing latest conjure-up on MAAS ubuntu 16.04 LTS, in all dokumentation it says that i need 1 MAAS server, 1 juju, and 3 comp nodes for openstack. But i run conjure-up openstack, bootstrapping the juju node goes fine, but when nodes are deploing i run juju status and there i see that it expect 4 mashine?? why ? and is it possible to run it at 3 comp nodes?
[12:49] <kjackal> hi dougi, you could ask at #openstack-charms
[12:59] <marcoceppi> magicaltrout: email the list, we've not really talked much about translations. I'd like to use Launchpad for it, but I don't run the docs
[12:59] <magicaltrout> fair enough
[13:02] <admcleod> magicaltrout: HELLO!
[13:04] <magicaltrout> jesus
[13:06] <dougi> kjackal: ok thanks :)
[13:19] <admcleod> magicaltrout: HOW R U?
[13:20] <admcleod> lolz
[13:20] <magicaltrout> you a bit bored admcleod ?   Isn't there some way to get into the charm's environment to run the hook tools lke config-get manually?
[14:08] <bladernr> I want to test some of them out and then write a hook to take advantage of them.
[14:08] <bladernr> ^^ IOW, I can't just juju-ssh to a unit and run config-get, there's something more that needs to be done to get into the Juju environment on the deployed unit?
[14:09] <jrwren> bladernr: juju run for a unit runs in a hook context. you can invoke that way.
[14:26] <bladernr> jrwren, perfect! that's exactly what I was looking for
[14:26] <bladernr> jrwren, thanks a ton!
[14:29] <jrwren> bladernr: you are welcome. If you can suggest a place where you would have found this in the docs, maybe we could update the docs to mention it.
[14:39] <bladernr> jrwren, maybe just a mention here: https://jujucharms.com/docs/2.0/reference-hook-tools
[14:39] <bladernr> perhaps in one of the Note boxes at the top of the page as just a hint for testing the hook helpers
[14:39] <bladernr> sprint over, time go to.
[14:40] <jrwren> bladernr: thanks!
[15:27] <cory_fu> tvansteenburgh: https://github.com/juju/python-libjuju/commit/6ba2856fecf224ae3fd589331e889a6587e8153b#commitcomment-20136048
[15:29] <cory_fu> tvansteenburgh: I was using add_model in matrix already before your change and just passing None for both of those, so I think we can just pass those through.  (Though your "tag.cloud(cloud_name)" change will probably need an if / else wrapper.)
[15:31] <tvansteenburgh> cory_fu: passing None for both of what?
[15:32] <cory_fu> cloud_name and credential_name
[15:32] <tvansteenburgh> oh i see
[15:32] <tvansteenburgh> well that's great news!
[15:32] <tvansteenburgh> didn't realize that
[15:32] <tvansteenburgh> cory_fu: will refactor, thanks for the tip
[15:33] <cory_fu> tvansteenburgh: No problem.  And thanks for the merge conflicts.  ;)
[15:33] <tvansteenburgh> any time!!
[15:33] <cory_fu> =D
[15:59] <skay_> stub: hi, I'd like for the snap layer to support private/unpublished snaps. how would I go about adding that functionality?
[18:12] <cholcombe> bdx, could you publish your vault, consul and consul-agent charms?
[20:00] <mbruzek> bergtwvd ping
[20:22] <tvansteenburgh> if i run `juju config ...` and then run `juju run ...`, am i guaranteed that the config-changed hook has finished before the `juju run` command is executed?
[20:24] <tvansteenburgh> iotw, are `juju run` commands queued along with regular hook invocations, or run out-of-band?
[20:24] <tvansteenburgh> i thought it was the latter but i can't find any docs that say either way
[21:55] <rick_h> tvansteenburgh: yes
[22:11] <tvansteenburgh> rick_h: yes to which question?
[22:12] <tvansteenburgh> rick_h: yes, config-changed will def finish before the juju run command executes?
[22:13] <rick_h> Yes, it will go in order
[22:13] <rick_h> The events are sync though they occur async


[08:07] <lamont> Extracting upstream tarball ../pango1.0_1.6.0.orig.tar.gz gunzip:
[08:07] <lamont> +/build/buildd/pango1.0-1.6.0/../pango1.0_1.6.0.orig.tar.gz: No such file or
[08:07] <lamont> +directory
[08:07] <lamont> I bet that's relevant...
[08:07] <seb128> I've stopped my fetchmail, I want to check if my ISP drop the mail or what
[08:07] <seb128> lamont: ok, thanks
[08:08] <lamont> bounced, and forwarded.  let me know which you get (or both)
[08:08] <thom> YA new X
[08:08] <thom> suck
[08:08] <lamont> 18? or 17?
[08:08] <sivang> does anybody knows the /etc/init.d/ script file for ftpd ?
[08:09] <sivang> name that is
[08:09] <mdz> seb128: do we need to update the seeds to account for the new evolution?
[08:09] <thom> 17
[08:09] <Mithrandir> sivang: it's run from inetd
[08:09] <sivang> Mithrandir : oh
[08:09] <lamont> ah, I still haven't finished wading through gnome 2.8 and a new kernel to get that far yet...,
[08:09] <seb128> mdz: yes, drop the 1.5 evolution1.5 -> evolution
[08:09] <jdub> seb128: in the Evolution Mail menu entry, did you make it run 'evolution-2.0 --component=mail' ?
[08:10] <seb128> jdub: hum no, it just starts evolution
[08:10] <sivang> nautilus is crashing after multiple mounts/umoubnts of cdrom and a dvd devoce
[08:10] <sivang> device
[08:10] <seb128> jdub: ok, I'l upload a 0ubuntu2
[08:10] <jdub> seb128: the --component=mail bit would be extra cool :)
[08:10] <sivang> mount media=knoppix
[08:10] <seb128> any other change ?
[08:10] <jdub> seb128: nup, sorry about that 8)
[08:12] <seb128> np
[08:12] <mdz> seb128: evolution-webcal and evolution-exchange stay the same?
[08:12] <seb128> yes
[08:12] <mdz> ok, done
[08:13] <seb128> thanks
[08:17] <sivang> i really like that "click on cd icon == close tray, mount" thing
[08:20] <mdz> Kamion: regarding the metapackages for linux-restricted-modules, I was going to ask Herbert to do that anyway, but you're OK for preview with it as-is, right?
[08:21] <Md> does linux-restricted-modules contain anything else other than the proprietary nvidia driver?
[08:21] <Kamion> mdz: yes; the only glitch is that (as I realized today) we're not actually installing the linux-image metapackages
[08:22] <Kamion> due to weirdness in base-installer
[08:22] <mdz> oh
[08:22] <mdz> is that easy to fix?
[08:22] <mdz> it would be nice if that worked for preview
[08:22] <Kamion> mdz: when I fix that, the linux-restricted-modules metapackages will need to be there as well otherwise it gets really hairy
[08:22] <mdz> hmmm
[08:22] <Kamion> I looked at it, but it was getting into sed nightmare land without the linux-restricted-modules metapackage
[08:22] <Kamion> it's hard to take linux-image-2.6 and work out that you need linux-restricted-modules-<IP_ADDRESS>-2
[08:23] <mdz> what I'm unsure of with the l-r-m metapackage is how it should sync up with linux-source
[08:23] <Kamion> the <IP_ADDRESS>-2 part needs to be in sync ...
[08:23] <mdz> maybe linux-source should build all the metpackaages
[08:23] <Kamion> hmm, I see what you mean I think
[08:24] <Kamion> I have some thoughts, but I think we should leave this until after preview, it doesn't feel like a good idea to try to get this right in under 24 hours
[08:24] <Kamion> Md: also ath, ath_hal, net80211
[08:24] <sivang> mdz : i have aptitude tell me that linux-image is installed 2.6.8 , but it's using 2.6.7
[08:25] <mdz> Kamion: agreed
[08:25] <Kamion> we still seem to have debugging artwork in gdm
[08:26] <mdz> sivang: check /boot/grub/menu.lst perhaps?
[08:26] <Kamion> and the wallpaper
[08:26] <mdz> yes, we do. jdub?
[08:27] <jdub> yes, being worked on atm.
[08:27] <seb128> lamont: ok, I got the mail, and I know where the problem is
[08:27] <lamont> something more for my hoary plate
[08:27] <hypatia> hey folks...
[08:27] <seb128> lamont: any chance to delete an orig.tar.gz broken, or I should happen a b to the version and make a new one ?
[08:28] <hypatia> spiv tells me that if I plug in for example, a USB digital camera that "something" should just appear "somewhere" on my desktop and let me use it "somehow".
[08:28] <Md> Kamion: what is net80211?
[08:28] <lamont> seb128: that's an elmo question
[08:28] <seb128> elmo: ping ?
[08:28] <hypatia> does anyone have any more details on where this magic should happen?
[08:29] <jdub> Kamion: how big's the isolinux splash?
[08:29] <seb128> lamont: BTW my system has droped the mail from buildd@ somewhere, I've a mail problem
[08:29] <thom> hypatia: it should get mounted under /media ;
[08:29] <hypatia> ok
[08:30] <thom> and you should have gnome-volume-manager running
[08:30] <Kamion> jdub: 6K
[08:30] <seb128> (the mail was on the server but is not in my evolution boxes)
[08:30] <Kamion> jdub: oh, resolution?
[08:30] <jdub> yeah :)
[08:30] <Kamion> Md: don't know the details
[08:30] <Kamion> jdub: 639x320
[08:30] <Kamion> jdub: I dropped in a new image recently which looks much better
[08:30] <hypatia> thom: nup, there's only cdroms under there
[08:30] <hypatia> thom: is that bug worthy?
[08:31] <thom> hypatia: do you have gnome-volume-manager running?
[08:31] <jdub> Kamion: got one for you from the design firm to compare against
[08:31] <hypatia> thom: as user or root? root I guess
[08:31] <thom> user
[08:31] <hypatia> ok
[08:31] <Kamion> jdub: throw it over
[08:32] <hypatia> thom: yep, there it is
[08:32] <lamont> seb128: could just be spam filters...
[08:32] <jdub> Kamion: sent a png
[08:32] <thom> ok, file a bug, including dmesg from when you insert the thing, and also /var/log/messages
[08:32] <hypatia> ok
[08:32] <seb128> lamont: I'm checking
[08:34] <hypatia> grrr, copy and paste between firefox and gnome-terminal still does not love me
[08:35] <hypatia> I can't do anything on this computer without filing a bug
[08:35] <hypatia> So far my attempts to file bugs have themselves resulted in two bug reports
[08:35] <thom> the search one is a classic
[08:36] <hypatia> what component am I filing against (for the camera thing)?
[08:36] <hypatia> and for that matter, which one for "can't copy and paste between Firefox and GT"?
[08:36] <Kamion> jdub: I'll have to reduce the colourmap on that
[08:37] <thom> hypatia: gnome-volume-manager
[08:37] <hypatia> thom: not in the list
[08:37] <thom> gar
[08:37] <hypatia> thom: gnome-v gives me "gnome-vfs2"
[08:37] <thom> UNKNOWN, assign it to me
[08:37] <jdub> Kamion: 'scool
[08:37] <jdub> Kamion: if it looks shit, let me know
[08:37] <hypatia> thom: alternatively I can file a third "cannot file against gnome-volume-manager" bug... or perhaps not
[08:37] <jdub> Kamion: oh, send over the one you did for perving :)
[08:41] <hypatia> Who should I file gnome-terminal bugs against (no it isn't in the components either)?
[08:41] <hypatia> I guess the c+p one can be filed against firefox
[08:41] <lamont> hypatia: the issue is that components need to be added by one of the admins, and they should sync things up sometime soon...
[08:42] <lamont> meanwhile, for everything else, there's UNKNOWN.  and then he notices that when he assigns it, and maybe fixes the component list..
[08:42] <Kamion> jdub: mine isn't nearly as nice-looking on the face of it
[08:42] <Kamion> jdub: https://chinstrap.warthogs.hbd.com/~cjwatson/ubuntu-isolinux.ppm
[08:44] <jdub> Kamion: it'd look very nice if it weren't jaggy
[08:45] <jdub> Kamion: i will do something similar on top of the zebra to see how that looks
[08:45] <Kamion> jdub: jaggies are pretty unavoidable with the damned curves
[08:46] <Kamion> and 16 colours
[08:46] <Kamion> there'll be some jaggies on the new one, too :-/
[08:46] <Kamion> not *too* bad, though ...
[08:47] <doko> hmm, I see that prebaseconfig and base-installer messages are not up to date for german only :-(
[08:52] <hypatia> thom: bug filed
[08:54] <tvon|X31> jdub: still want 2.8 screenshots?
[08:54] <tvon|X31> jdub: ala the #gnome topic
[08:56] <jdub> sure
[08:56] <Kamion> jdub: that looks fairly reasonable. only minor issue is that the background ends up the dark blue of the "ubuntu" text
[08:56] <jdub> Kamion: bong!
[08:56] <Kamion> it doesn't look too bad that way, though
[08:56] <jdub> Kamion: need to adjust the palette then :|
[08:56] <jdub> or doesn't it have any black?
[08:56] <Kamion> nope
[08:56] <Kamion> pas de noir
[08:56] <jdub> tvon|X31: a screenshot of 2.8 in ubuntu would be cool ;)
[08:57] <Kamion> I'd digicam it if I could find the digicam
[08:57] <tvon|X31> jdub: got two of em...one of em with the ubuntu theme
[08:58] <jdub> tvon|X31: hrm
[08:59] <jdub> tvon|X31: that might not be so great (given we're turning it all off) ;-)
[08:59] <jdub> tvon|X31: send 'em anyway ;)
[08:59] <tvon|X31> jdub: ye got two
[09:00] <mako> lulu: you around?
[09:00] <lulu> yebo!
[09:02] <Kamion> jdub: https://chinstrap.warthogs.hbd.com/~cjwatson/isolinux-photo.jpg
[09:02] <Kamion> jdub: lighting's dreadful, sorry
[09:02] <jdub> oh, ta
[09:02] <jdub> hrm
[09:03] <Kamion> it's brighter than it looks on that photo
[09:03] <Kamion> I think it's probably good enough for preview at least, we can get the design company to tweak it later if we want
[09:04] <Kamion> don't really fancy tweaking colours on antialiased pngs by hand
[09:10] <mdz> justdave: just filed a bug for you regarding Warty bugzilla which needs attention today
[09:11] <Kamion> ok, the only two reasonably-unused keys I can find for powermac mouse buttons are F11 and F12
[09:12] <mdz> jdub: you seem to be collecting branding/defaults bugs; are you going to be able to get all of those done today, or do you need help?
[09:12] <jdub> mdz: i passed off the openoffice ones
[09:12] <jdub> mdz: concentrating on ubuntu-artwork and a couple of desktop changes
[09:13] <mdz> jdub: oh, the bug is still assigned to you
[09:13] <jdub> mdz: seb's already done evo, haven't seen nat for the openoffice ones (though seb was going to fix them anyway)
[09:13] <mdz> seb seems to have a lot on his plate gnome-wise
[09:14] <jdub> mdz: hrm
[09:14] <mdz> nathaniel can do it
[09:14] <tvon|X31> hrm
[09:14] <jdub> mdz: well if pitti/nat can do those, that'd be very helpful
[09:14] <mdz> pitti is gone for the day
[09:14] <jdub> ok
[09:14] <mdz> but it's only 3pm nathaniel time
[09:14] <tvon|X31> Should evolution-2.0 obsolete evolution1.5-2.0 ?
[09:14] <tvon|X31> s/should/shouldnt/
[09:15] <tvon|X31> or 'replace' or whatever the debian equiv is
[09:15] <mdz> whoa
[09:15] <mdz> jdub: does nautilus try to call growisofs?
[09:15] <doko> Kamion: which packages belong to the base installer and should be translated?
[09:15] <justdave> mdz: you had something in debzilla that automatically added a component if it didn't exist when importing from debbugs, right?
[09:16] <mdz> justdave: yes
[09:16] <justdave> mind if I borrow that?
[09:16] <justdave> that'd be the quickest way to do it is separate that out and feed the list to it
[09:16] <Kamion> doko: "the base installer"?
[09:16] <mdz> justdave<EMAIL_ADDRESS>[09:16] <mdz><EMAIL_ADDRESS>[09:16] <doko> kamion: packages that print messages during the installation process ...
[09:18] <doko> do we want to update the message catalogs for these packages for warty (for some languages?)
[09:18] <mdz> justdave: just instantiate a bugzilla.Database with db authentication info and use .components() and .add_component()
[09:18] <justdave> cool, thanks
[09:18] <Kamion> doko: everything that's got a udeb
[09:19] <Kamion> doko: translations would be good and are reasonably low risk, although we're not regarding complete translations as release-critical
[09:19] <Kamion> mdz: is that base-installer fix-to-the-fix OK with you?
[09:20] <mdz> Kamion: yes, didn't I OK it in bugzilla alreday?
[09:20] <mdz> already
[09:21] <Kamion> nope
[09:21] <mdz> gah
[09:21] <mdz> bugzilla is sitting at a login prompt
[09:22] <mdz> Kamion: my comment didn't get posted because I got logged out somehow
[09:23] <Kamion> ah well
[09:24] <doko> kamion: is there a quick way to determine the source packagess building udeb's?
[09:25] <Kamion> doko: Source: lines in /dists/warty/main/debian-installer/binary-*/, plus Package: lines of stanzas there that don't have a Source: line
[09:26] <dieman> elmo: ping
[09:26] <Kamion> doko: oh, or the second column of https://chinstrap.warthogs.hbd.com/~cjwatson/germinate-warty-output/installer, I suppose
[09:26] <Kamion> if you have a chinstrap account ... don't remember
[09:32] <Kamion> jdub,mdz: I plan to kick off another CD build for general testing sometime between 2000 and 2100 UTC tonight. Anything I should wait for?
[09:33] <mdz> Kamion: there ought to be a new openoffice today
[09:33] <mdz> theoretically
[09:33] <Kamion> any idea of timescale?
[09:34] <mdz> none
[09:34] <Kamion> damn, that'll take ages to build though
[09:34] <mdz> seb128: are you working on openoffice?
[09:34] <sivang> Kamion : new daily will be announced on the list?
[09:34] <mdz> 2000 UTC is in...25 minutes?
[09:34] <mdz> don't wait for it
[09:34] <thom> yep
[09:34] <mdz> hmm
[09:34] <Kamion> sivang: maybe :-)
[09:35] <seb128> mdz: no, I was waiting to get Nathaniel's patch attached to the bug report (and I've just finished packaging GNOME 2.8 tarballs before dinner)
[09:35] <mdz> Kamion: is anyone other than you currently able to build CD images?
[09:35] <sivang> Kamion : you devil :-))
[09:36] <mdz> seb128: have you heard from him today?
[09:36] <seb128> no
[09:36] <Kamion> mdz: anyone in the cdimage group on little can log in and type 'DATE_SUFFIX=<whatever> cron.daily'
[09:36] <Kamion> mdz: so theoretically Alex could do it
[09:36] <Kamion> mdz: nobody else ever has, though ... I should almost certainly fix that
[09:36] <mdz> Kamion: assuming you're planning to sleep tonight, we might want to get someone else (perhaps me) added to that group
[09:37] <Kamion> I was sort of viewing sleep tonight as optional :)
[09:37] <Kamion> but that might well be a good idea
[09:37] <mdz> likewise
[09:37] <Kamion> elmo: around?
[09:37] <Kamion> might need to check for group-writability of everything
[09:38] <sivang> Kamion : the public review iso is ready for testing?
[09:38] <mdz> elmo is bleeding at the data center, apparently
[09:38] <thom> i can check
[09:38] <Kamion> sivang: you can test whenever you like, the preview is not ready though
[09:39] <Kamion> sivang: trust me, it will not be quiet when it's released
[09:39] <Kamion> thom: can you add mdz to the set of people allowed on little as well as to the cdimage group?
[09:40] <thom> doing so now
[09:40] <Kamion> ta
[09:43] <Kamion> ok, everything relevant is group-writable now
[09:43] <thom> mdz: you have a login on little and you're in the cdimage group
[09:44] <Kamion> mdz: all the top-level scripts are in /srv/cdimage.no-name-yet.com/bin; I just have that in $PATH
[09:44] <Kamion> mdz: normally, cron.daily is the only one you need to run (preferably with umask 002)
[09:44] <mdz> Kamion: if you're going to do a build anyway, perhaps I should run it as a test
[09:45] <Kamion> sounds good
[09:45] <Kamion> you need to set DATE_SUFFIX if you're building manually; DATE_SUFFIX=1 produces a build like 20040914.1
[09:47] <mdz> Kamion: so this one should be DATE_SUFFIX=1?
[09:47] <Kamion> yep
[09:48] <mdz> running
[09:49] <doko> kamion: you did change the messages directly in the installer packages? no central translation file as for the current debian installer packages? daf just mentioned the existance of such a central file.
[09:50] <daf> doko: for some languages, at least
[09:50] <Kamion> on phone
[09:50] <daf> doko: Christian has given individual teams the option of using the new system
[09:51] <daf> although I think by far the majority have taken it up
[09:53] <fabbione> mdz: thom is having the same problem you had with xresprobe.
[09:53] <fabbione> mdz: how did you debug it? mind to tell him?
[09:54] <mdz> fabbione: which one?
[09:54] <fabbione> mdz: the LCD detection at install time
[09:54] <fabbione> mdz: the nv driver is going good btw.. 3 tester = 3 success
[09:54] <fabbione> mdz: but yeah.. it will never make it for tomorrow
[09:54] <mdz> thom: but it works for you when you test manually after install?
[09:54] <fabbione> mdz: yes. exactly as your
[09:54] <mdz> thom: you're getting xresprobe 0.4.3 at install time?
[09:55] <mdz> (or later)
[09:55] <mdz> hmm
[09:55] <mdz> thom: your laptop has an i810, right?
[09:55] <mdz> thom: maybe related to the change in 0.4.6?
[09:55] <mdz> speaking of which
[09:55] <mdz> jdub: did you approve xresprobe 0.4.6?
[09:56] <fabbione> mdz: probing on i810 when X run = BAD BAD BAD
[09:56] <mdz> fabbione: yes, I know, but if the check is broken, it could cause the probe not to run at all
[09:56] <doko> daf: ok, but this was after the point we did fork the installer packages from unstable?
[09:57] <fabbione> mdz: if it runs once X is installed ...
[09:57] <fabbione> mdz: it smells more the problem you had
[09:57] <fabbione> mdz: than the check in xresprobe
[09:57] <mdz> Kamion: cron.daily exited, no output
[09:57] <mdz> fabbione: the problem I had is fixed
[09:57] <thom> mdz: yes
[09:57] <mdz> I even tested with today's daily
[09:57] <fabbione> mdz: ah
[09:57] <thom> i have xresprobe 0.4.6
[09:57] <fabbione> head
[09:58] <mdz> thom: does it work when you try it after the installation is complete?
[09:58] <thom> mdz: it fails during base-config, but if i purge and reinstall it works
[09:58] <mdz> hmm
[09:59] <daf> doko: it happened around the end of August
[09:59] <mdz> thom: any output in base-config.log?
[09:59] <thom> wait one
[10:01] <mdz> npmccallum: hey, what is the status of the openoffice.org changes?
[10:01] <fabbione> good night guys
[10:02] <seb128> 'night fabbione
[10:02] <fabbione> cya tomorrow morning
[10:02] <npmccallum> mdz: the icon names are done, but for some reason when I do debuild -S it screws up translations
[10:02] <mdz> fabbione: night
[10:03] <seb128> npmccallum: -S ?
[10:03] <thom> mdz: nothing that i can see
[10:03] <seb128> it just build the source package, how do you see that ?
[10:04] <npmccallum> seb128, yes -S
[10:04] <mdz> thom: must be a different bug
[10:04] <seb128> npmccallum: where do you look to see than translation are screwed ?
[10:04] <mdz> thom: I guess you'll need to reinstall, edit /usr/sbin/xresprobe and set XRESPROBE_DEBUG=yes
[10:04] <npmccallum> seb128: doing a debdiff between the packages
[10:04] <mdz> I had to do that 3 times to track down my bug
[10:04] <thom> doing so now
[10:04] <npmccallum> seb128: you should see it in the diff I sent you
[10:05] <seb128> npmccallum: as said yesterday I never got the mail
[10:05] <npmccallum> seb128: argh
[10:05] <mdz> thom: fortunately, there's a nice wide window between xresprobe install and xserver-xfree86 postinst
[10:05] <seb128> I've some mail issue apparently, that's why I asked to attach the changes to the bug yesterday
[10:05] <npmccallum> seb128: ok, I'll do that now
[10:06] <thom> mdz: a freakin' huge one, given this is coming over the network :-)
[10:10] <mdz> is someone taking care of the bug reporting menu item?
[10:10] <mdz> I think that was jdub's, as part of ubuntu-artwork
[10:10] <seb128> which menu item ?
[10:11] <mdz> #1080
[10:12] <mdz> we agreed that the best thing for preview is to have a menu item which launches the browser pointing to bugzilla
[10:12] <mdz> because we cannot get bug-buddy into shape in time
[10:13] <seb128> ok
[10:15] <npmccallum> seb128: the attachment should be on the bug now
[10:15] <seb128> ok, thanks
[10:15] <seb128> I'll look in about half an hour
[10:15] <seb128> time to fix pango and make a change in evolution
[10:15] <npmccallum> sure
[10:17] <mdz> npmccallum: thanks, have you looked at the splash screen?
[10:23] <npmccallum> mdz: I'm doing that now
[10:23] <thom> seb128: uh, evolution1.5 Conflicts: evolution-data-server (>= 0.0.100) but 1.0.0-0ubuntu1 is to be installed
[10:24] <seb128> thom: I've uploaded e-d-s and evolution 2.0 in the same time
[10:25] <thom> ok, cool
[10:25] <seb128> the second need the first but is longer to build
[10:25] <seb128> I can't do anythin to avoid this
[10:26] <thom> gar.
[10:26] <thom> ok, well, i'll wait for that to come down, since it nuked base-config
[10:27] <whiprush_> favorite warty feauture = someone took the time to pick only the good screensavers.
[10:27] <mako> hah, this glossary i'm editing linked to osi.org instead of opensource.org
[10:27] <whiprush_> that bouncing cow is the best ever.
[10:28] <thom> bouncing cow rocks :-)
[10:28] <mako> oh wow, the ottowa swine initiative has upgraded their site!
[10:29] <mako> sorry.. ontario
[10:32] <mdz> seb128: evolution 2.0 will require NEW processing, no?
[10:32] <seb128> hum, probably
[10:32] <seb128> no
[10:33] <seb128> I've got an ACCEPTED mail IIRC
[10:33] <seb128> evolution_2.0.0-0ubuntu1_source.changes ACCEPTED
[10:33] <seb128> yes
[10:34] <mdz> I think it would be the binary uploads which required manual processing
[10:34] <mdz> rather than the source
[10:39] <mdz> Kamion: I expected cron.daily to create 20040914.1, but it didn't
[10:40] <Kamion> mdz: it fell over; I know why, still on phone though
[10:40] <mdz> Kamion: ok
[10:40] <mdz> oh, I see, it writes a logfile
[10:40] <Kamion> yep
[10:41] <mako> thom: can you install my new shipit?
[10:41] <pitti> sivang: Hi, I'm back
[10:41] <mako> thom: if elmo is unavailable
[10:41] <sivang> pitti : hi again !
[10:41] <thom> doing bittorrent currently
[10:43] <mako> thom: ok, i'd like to have daniels and whoever else test it a little bit before we throw the gates open
[10:43] <thom> i'll let you know
[10:54] <mdz> seb128: evolution binaries are in the archive now
[10:54] <seb128> cool
[10:56] <mdz> seb128: is ximian-connector still building?
[10:56] <mdz> seb128: or did it produce different binaries as well?
[10:56] <seb128> ximian-connector was dep-waiting on evo 2.0
[10:56] <seb128> it should be building now
[10:56] <mdz> ah
[10:56] <mdz> lamont: please confirm
[10:57] <mdz> sometimes the auto-depwaiter needs a nudge
[10:57] <Kamion> mdz: try now
[10:58] <lamont> mdz: nope.
[10:58] <Kamion> mdz: are you using umask 002?
[10:58] <lamont> gnome/ximian-connector_2.0.0-0ubuntu1: Installed [optional:out-of-date]
[10:58] <lamont> :-)
[10:58] <seb128> lamont: I've just reuploaded pango, let me know if this one is fine please
[10:58] <seb128> damned, dbs is a pain
[10:58] <mdz> Kamion: 022
[10:59] <lamont> even without the bs, he's a pain. :-)
[10:59] <mdz> Kamion: I didn't even have a home directory until I logged into that box
[10:59] <mdz> lamont: so it's waiting in queue/accepted?
[10:59] <seb128> oups
[10:59] <mdz> oh, it's actually there
[10:59] <seb128> mdz: did we solve the ~/Documents creation issue ?
[10:59] <mdz> and yet apt wants to remove evolution-exchange when I upgrade
[11:00] <mdz> seb128: not to my knowledge
[11:00] <lamont> mdz: actually, I believe it's in the archive, just not referenced by Packages until about 3 min from now
[11:00] <seb128> arg
[11:00] <mdz> lamont: ah
[11:00] <lamont> there is no queue/accepted...
[11:00] <lamont> but cron.daily (sic) does the rebuild of Packages.
[11:01] <Kamion> mdz: 002's be good
[11:01] <Kamion> 'd
[11:01] <lamont> mdz: btw, fire training tonight.  I'll make a point to be home by 2200, even if I wind up leaving a little early.
[11:01] <mdz> lamont: thanks
[11:01] <lamont> (trainings are tue 1900-2200 local)
[11:01] <mdz> Kamion: done
[11:02] <lamont> but often finish early
[11:02] <mdz> lamont: sorry, I've no choice in the scheduling on this one
[11:02] <lamont> np at all
[11:02] <lamont> it's a whopping 10 minutes away, and leaving a little early isn't really a big deal
[11:02] <lamont> we're usually done by about 21:30 or so
[11:03] <lamont> should be back online from said sounder's place sometime after I leave...
[11:14] <seb128> mdz: I've made dummy evolution1.5/evolution1.5-dev for transition, should we add them to the seed ? Currently they are out of warty ...
[11:17] <mdz> seb128: yes, I'll do it
[11:18] <seb128> ok, thanks
[11:18] <mdz> added to Supoprted
[11:19] <pitti> seb128: odd, I want to dist-upgrade, and evolution1.5 and evolution-exchange are to be removed correctly, but evolution is not installed additionally
[11:19] <seb128> that's because the dummy package is not in the seed
[11:19] <pitti> seb128: ah, I see.
[11:23] <mdz> seb128: new evolution looks good
[11:23] <seb128> nice
[11:24] <lucas_> hi
[11:24] <seb128> we are uptodate with GNOME 2.8 release now
[11:24] <seb128> but no control-center/gnome-terminal 2.8 for the moment
[11:24] <seb128> hey lucas_
[11:26] <elmo_dc> evo1.5 promoted back to warty, pushing through now
[11:27] <elmo_dc> btw, if you use that dvd/cd creator program that launches when you insert a blank disk, it really will write an ISO of an ISO
[11:28] <elmo_dc> if you copy an iso into the window and choose "write this file".. which seems a bit user unfriendly to me.. (but not major of course)
[11:29] <lamont> seb128: since you're the only one doing uploads, want me to just (today only special) forward you all the failures?
[11:30] <lamont> seb128: pango1.0....
[11:30] <seb128> hum, yes, do that
[11:30] <lamont> email>?
[11:30] <seb128> lamont: still ftbfsing ?
[11:31] <seb128> lamont<EMAIL_ADDRESS>[11:31] <lamont> doh
[11:31] <lamont> no, not still ftbfsing.
[11:32] <lamont>   * ^Subject: Log for failed .*build of .*dist=warty
[11:32] <lamont><EMAIL_ADDRESS>[11:32] <lamont> "have a nice day".
[11:32] <seb128> thanks :)
[11:32] <Kamion> mdz: right, sorry about that, old university friend phoned up
[11:32] <lamont> I'll rip that out tomorrow sometime and let you know
[11:33] <mdz> Kamion: I have all night :-)
[11:33] <Kamion> mdz: can you chmod -R g+w everything? there are some directories still owned by you and g-w so I probably won't be able to remove them
[11:33] <mdz> Kamion: for what value of everything?
[11:33] <lamont>  /?
[11:34] <mdz> find /srv/cdimage.no-name-yet.com -user mdz \! -perm +020 |wc -l
[11:34] <mdz> 2429
[11:34] <mdz> Kamion: that stuff?
[11:34] <Kamion> mdz: /srv/cdimage.no-name-yet.com I guess
[11:34] <Kamion> yep
[11:34] <Kamion> I'll put a umask setting in cron.daily to make sure
[11:34] <mdz> find /srv/cdimage.no-name-yet.com -user mdz \! -perm +020 -print0 | xargs -0 chmod g+rwX
[11:34] <mdz> done
[11:36] <Kamion> oh, crap, just realized you won't be able to run sync-auckland
[11:36] <Kamion> because ssh is annoying and doesn't like group-readable/writable key files
[11:37] <Kamion> hm, let me install a workaround for that
[11:41] <Kamion> mdz: see /srv/cdimage.no-name-yet.com/secret/README
[11:42] <mdz> Kamion: done. shall I try again?
[11:42] <mdz> and if so, should I re-use .1 or use .2?
[11:42] <Kamion> mdz: yep; reusing .1 is fine
[11:42] <Kamion> (since it hasn't been published)
[11:43] <mdz> running
[11:45] <Kamion> bleh, that's annoying, some stuff isn't respecting umask
[11:45] <elmo_dc> err, is 20040914 known to be broken?
[11:45] <Kamion> like, err, scratch/apt/
[11:45] <Kamion> elmo_dc: no, why?
[11:46] <elmo_dc> kamion: I just got a "downloading bsdutils" failed.. I haven't checked the CD yet tho
[11:46] <Kamion> mdz: at this rate I'm going to have to add a kludge chmod to the end of cron.daily or something ...
[11:46] <Kamion> oh, hey, openoffice.org is built on amd64 now, isn't it?
[11:47] <mdz> elmo_dc: 20040914 worked fine for me
[11:47] <mdz> but of course it now installs new stuff directly from the archive, so my 20040914 is not your 20040914
[11:47] <mdz> Kamion: yes
[11:47] <mdz> Kamion: if you had a kludge in for that, it can and should be removed
[11:47] <Kamion> yep, that just occurred to me
[11:48] <elmo_dc> mdz: blink it does?
[11:48] <Kamion> not at the bsdutils level though
[11:48] <Kamion> that's installed by debootstrap, isn't it?
[11:48] <Kamion> that's only from the CD
[11:49] <Kamion> mdz: kludge gone, not in time for your current build though
[11:50] <elmo_dc> yeah my cd is fucked
[11:51] <Kamion> mdz: heh, was ssh waiting for confirmation there?
[11:52] <elmo_dc> that sucks, nautlius just said it had completed, not that it only burnt 1/3 of the bloody disc
[11:52] <mdz> Kamion: dunno, I had no output
[11:52] <mdz> Kamion: if there was any, I assume it was written to the log and not to my tty
[11:53] <mdz> Kamion: let's do another one, oo.o on amd64 is worth it
[11:53] <Kamion> mdz: would appreciate it if you could do that chmod again
[11:53] <mdz> we certainly have the disk space
[11:53] <mdz> Kamion: done
[11:53] <Kamion> mdz: wait just a sec
[11:53] <mdz> Kamion: too late, if you meant the chmod
[11:53] <Kamion> nah
[11:54] <Kamion> ok, rptprobs.sh was doing an explicit chmod 644, fixed
[11:54] <mdz> workrave break
[11:54] <Kamion> for the rest, I've kludged cron.daily
[11:57] <jdub> seb128: control-center on its way
[11:57] <doko> kamion, mdz: localization of the installer: what would be the last date for updated message catalogs for packages which are part of the installer? I did prepare tarballs for each language whith outdated message catalogs, one file for each package which belongs to the install system. I'd propose to send them ount to the sounders list and ask for translation, then merge them back into the package and make one upload with the updated catalogs.
[11:57] <seb128> jdub: ok
[11:58] <Kamion> doko: sorry, missed your comment earlier; I've just changed the files directly in the packages, there's no central infrastructure yet.
[11:58] <Kamion> doko: that's fine by me but dunno what the release manager has to say :-)
[11:59] <seb128> jdub: we have not fixed the ~/Documents creation issue ?


[06:25] <Terminus> hello. it was suggested that i ask this question here. is there any chance that this fix will make it into lucid? --> https://bugs.launchpad.net/ubuntu/+source/vim/+bug/584797
[06:49] <nigelb> !sru | Terminus
[06:49] <nigelb> You'll have to follow the guidelines there for an SRU
[06:50] <Terminus> nigelb: i see. thanks.
[06:51] <gua> hi, not sure if this is the best place to put this, but i noticed ubuntu-10.04 server torrents were linked under the "Ubuntu 10.10" header instead of 10.10 torrents at the bottom on http://www.ubuntu.com/desktop/get-ubuntu/alternative-download#bt
[06:52] <micahg> gua: please file an issue here: https://bugs.launchpad.net/ubuntu-website/
[06:53] <gua> ah ok
[06:53] <nigelb> whoa, that took a few moments to figure out what was wrong :(
[07:27] <pitti> Good morning
[08:03] <didrocks> good morning
[08:47] <dholbach> good morning
[08:49] <pitti> hey dholbach
[08:49] <dholbach> hey pitti
[09:30] <sirlatrom> hi, got a possible bug in apt-get or aptitude but not sure which of the two to submit it to
[09:31] <sladen> sirlatrom: which did you type when the bug/issue appeared :)
[09:31] <sirlatrom> aptitude, but it uses apt-get right?
[09:31] <sladen> sirlatrom: http://launchpad.net/ubuntu/+source/aptitude/+filebug
[09:32] <sirlatrom> sladen: ok, thanks
[13:04] <amitk> njpatel: I still don't see the skype icon in the status bar after getting friday's updates. (And yes, it is merely invisible. Clicking on the empty space brings up the skype dialog)
[13:06] <njpatel> amitk, Urgh, I can't reproduce that after the updates at all :/
[13:07] <njpatel> amitk, can yo ufile a bug please?
[13:07] <njpatel> I'll have another look this week
[13:07]  * njpatel wonders what magic he can do to make it stay in the right stacking order
[13:50] <SpamapS> wth? DMB moved their meeting to 12:00 UTC ?!
[13:53] <geser> SpamapS: it alternates between 12:00 UTC and 19:00 UTC for some time now
[13:53] <SpamapS> ahhh I didn't know that. :-/
[13:54] <kirkland> @pilot on
[13:54] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[13:54] <SpamapS> well then..2 more weeks.
[13:54] <kirkland> @pilot in
[13:54] <SpamapS> win 11
[13:54] <SpamapS> doh
[13:55] <SpamapS> kirkland: o/ morning
[13:55] <kirkland> SpamapS: howdy
[13:55] <geser> SpamapS: looks like you didn't miss anything as the DMB meeting was unquorate
[13:59] <SpamapS> geser: right.. last time the quorum took 45 min to achieve, and I passed out from jet lag waiting for the meeting to complete. :-p
[14:52] <kirkland> bryceh_: hi, about https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/415586
[14:52] <kirkland> bryceh_: i see the patch you attached,  i'm curious if there's a good reason you haven't uploaded yourself
[14:52] <kirkland> bryceh_: I was about to do so as today's patchpilot, but wanted to check with you first
[15:04] <kirkland> jamesh: ping
[15:04] <kirkland> jamesh: i'm all kinds of confused about the state of lp:~jamesodhunt/ubuntu/natty/vim/add-upstart-syntax
[15:05] <cjwatson> kirkland: (a) you have the wrong James, (b) I'm happy to handle that one since I handled the previous similar one
[15:05] <kirkland> cjwatson: so i see (a), whoops
[15:05] <kirkland> jhunt: ^
[15:05]  * ogra_ was thinking upstart grew some python when seein (a) phew
[15:06] <ogra_> *seeing
[15:06] <cjwatson> lp:ubuntu/vim is out of date due to importer bugs
[15:06] <cjwatson> which makes LP merge requests against it pretty confusing
[15:06] <kirkland> cjwatson: yes, agreed
[15:06] <cjwatson> I just processed the previous one by hand
[15:06] <kirkland> cjwatson: i was about to import-dsc it
[15:06] <cjwatson> I didn't bother :)
[15:06] <kirkland> cjwatson: shall i just walk away from this one, then?
[15:07] <cjwatson> as I say, I'm happy to handle it
[15:07] <kirkland> cjwatson: k, thanks
[15:07] <jhunt> cjwatson: thx from me too! :)
[15:09] <cjwatson> jhunt: you should probably just 'apt-get source vim' for future changes, and file bugs with patches, until such time as the import is sorted out
[15:10] <cjwatson> I'll massage this into 2:7.3.035+hg~8fdc12103333-1ubuntu4
[15:10] <apw> cjwatson, jhunt, did either of you see my write up on the vesafb thingy?
[15:10] <cjwatson> apw: not yet, where was it?
[15:10] <apw> cjwatson, in the first instance direct email
[15:10] <jhunt> cjwatson: ack
[15:10] <apw> cjwatson, subject: framebuffer initialisation
[15:12] <cjwatson> ah, drowned in my inbox
[15:13]  * cjwatson finds it and will think hard about that
[15:15] <cjwatson> vim> done (2:7.3.035+hg~8fdc12103333-1ubuntu5)
[15:17] <jhunt> cjwatson: thx!
[15:51] <kirkland> pitti: morning!
[15:51] <kirkland> pitti: i'm reviewing https://code.launchpad.net/~er-abhinav-upadhyay/ubuntu/natty/apport/bugfix-357847/+merge/53184  as part of my patch pilot day
[15:52] <kirkland> pitti: against apport
[15:52] <kirkland> pitti: i was wondering if you wanted to review that one yourself
[15:52] <kirkland> pitti: and also if this one requires an FFe, in your opinion
[15:54] <hallyn> hi all - there is a package in universe called celt, which is at version 0.7.1.  We need version 0.5.1 for another package.  Would it be best to create 'celt051' package?  (requiring users to pin seems so barbaric)  Is there a better name for the package?
[15:55] <pitti> hey kirkland (sorry, was at the phone)
[15:55] <kirkland> pitti: no problem
[15:56] <kirkland> hallyn: that is the best way to solve that particular problem, but it's somewhat frowned upon, in my experience
[15:56] <pitti> kirkland: hm, I'd rather avoid having that implementation in the shell wrapper
[15:56] <kirkland> hallyn: usually, we lean heavily on the dependent package to modernize
[15:56] <pitti> kirkland: so yes, I'd rather review it myself then; thanks for pointing out!
[15:56] <kirkland> pitti: no problem
[15:57] <hallyn> kirkland: so the name 'celt051' is ok?
[15:57] <pitti> kirkland: (it should also be committed to trunk first)
[15:57] <kirkland> pitti: right, i'll add a comment that I'm deferring to you
[15:58] <hallyn> kirkland: you can see the depending's package's attitude to upgrading in the debian ITP  :)
[15:58] <hallyn> IMO our options are (1) don't package it, (2) packaging something patched and incompatible with other distro's client/server, or (3) package 0.5.1.  I was hoping (2) would work better than it apparently will, so I'd started 2 in my ppa, but am now punting on that
[16:00] <kirkland> hallyn: what's the depending package?
[16:01] <hallyn> spice
[16:01] <kirkland> hallyn: hah :-)
[16:01] <hallyn> dev-zero is going to push the stuff in his ppa (with some modifications) into universe
[16:01] <hallyn> (yay)
[16:03] <hallyn> biab
[16:04] <kirkland> hallyn: anyway, to answer your question, yes, that is the way to do it
[16:05] <kirkland> hallyn: see python3, python2.6, python2.7
[16:07] <abhinav-> ttx, thanks for reviewing it again :) . I did "bzr status" in my branch, it showed nothing, also I think catalina.policy is already present in conf/ ?
[16:08] <ttx> ah?
[16:08] <ttx> oh.
[16:08]  * ttx branches and checks
[16:09] <abhinav-> ttx :-)
[16:15] <ttx> abhinav-: right, it's just the stock one, so it's already in.
[16:16] <abhinav-> yes
[16:16] <ttx> abhinav-: i'll test and sponsor that in. Tomorrow.
[16:16] <manish> abhinav-: ping. on #ubuntu-in
[16:16] <abhinav-> ttx,  ok thanks :)
[16:33] <SpamapS> jhunt: /win 11
[16:33] <SpamapS> dohh
[16:33] <SpamapS> jhunt: hey.. I was just going to say hi, and let you know that I installed your upstart package.. no problems yet
[17:03] <geser> jhunt: did you forward your upstart syntax changes for vim to Debian? so we have less delta for the next vim merge
[17:03] <jhunt> geser: no - I forwarded them to vim.org.
[17:03] <geser> that's also ok :)
[17:03] <jhunt> geser: :)
[17:15] <kirkland> pitti: hey, one more for you
[17:15] <kirkland> pitti: i see you were the last to comment on https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/699886
[17:16] <kirkland> pitti: the report has reported it upstream, as you requested
[17:16] <kirkland> pitti: is it okay to apply the patch now to langpack-locales  and upload to natty?
[17:26] <apw> cjwatson, thanks, i'd like you and jhunt to be happy before i go any further
[18:00] <pitti> kirkland: sounds good! if you are at it, perhaps you can add the patch in bug 546581 as well?
[18:05] <ScottK> Bug #734957 <-- Less than one hour from reported to fix released ...
[18:06] <slangasek> pitti: hi there; did you happen to see my bug about cdbs+python-scour making fontconfig unbuildable? (bug #734471)
[18:15] <pitti> hey slangasek
[18:15] <pitti> slangasek: no, I didn't see it /me reading
[18:15] <NCommander> directhex: you about?
[18:16] <directhex> a little
[18:17] <NCommander> directhex: need additional mono help :-(. trying that 2.10 setup with banshee failed with issues in Mono.Addins
[18:17] <MadCow108> scottK:  haven't you reverted piotrs fix with your fix?
[18:17] <MadCow108> which is in the same changelog entry ^^
[18:18] <ScottK> No.  I added his.
[18:18] <MadCow108> the diff only shows removal
[18:18] <ScottK> We didn't have it in Ubuntu before.
[18:18] <directhex> NCommander:  oh? odd, it should be using mono.addins from the gac. what does "/path/to/parallel/mono/bin/gacutil -l | grep -i addins" say?
[18:18] <NCommander> directhex: no, that works, the problem is it throws exceptions
[18:18] <ScottK> MadCow108: Yes.  Piotr's fix was to remove a bad change.
[18:19] <directhex> NCommander: interesting. pastebin the errors?
[18:19] <NCommander> directhex: give me a sec
[18:20] <NCommander> directhex: root@risingsun:/# /opt/mono-2.10/bin/gacutil -l | grep -i addins
[18:20] <NCommander> Mono.Addins, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=0738eb9f132ed756
[18:20] <pitti> slangasek: replied in the bug
[18:20] <MadCow108> ah I understand, the log is from the cherry pick
[18:21] <directhex> NCommander: yeah, the lib is definitely there. can you try erasing the addins cache from ~/.config/banshee-1/addins* ? there are lingering bugs in 0.4
[18:21] <ScottK> Yes.
[18:21] <NCommander> directhex: same crash
[18:21] <directhex> weird
[18:22] <NCommander> directhex: http://paste.ubuntu.com/580227/
[18:25] <directhex> NCommander: /usr/bin/banshee is using your /opt banshee?
[18:25] <directhex> um, /opt mono
[18:26] <NCommander> directhex: yeah
[18:32] <directhex> NCommander: can you try installing addins from sid? wait, did i remember to upload to sid?
[18:32] <directhex> sigh, no
[18:32] <NCommander> directhex: I can install them if you want
[18:33] <NCommander> directhex: got a source package I can build?
[18:33] <directhex> NCommander: in git
[18:36] <NCommander> directhex: got it, building
[18:41] <Laney> 14/03 18:32:54 <NCommander> directhex: I can install them if you want
[18:41] <Laney> 14/03 18:33:04 <NCommander> directhex: got a source package I can build?
[18:41] <Laney> 14/03 18:33:15 <directhex> NCommander: in git
[18:41] <Laney> 14/03 18:36:05 <NCommander> directhex: got it, building
[18:41] <Laney> OOPS
[18:41] <Laney> sorry folks
[18:42] <Laney> NCommander: you can run with MONO_LOG_LEVEL=debug to get even more output too
[18:53] <directhex> bloody dsl
[19:07] <lan3y> i got killed too, wasn't the dsl
[19:12] <ari-tczew> ;o
[19:33] <abhinav->  I just noticed that the application deadline for gsoc is over. I was wondering if Ubuntu applied or not ?
[19:40] <highvoltage> lamont: hey there, I updated livecd-rootfs to install edubuntu theming in the ltsp chroot shipped with edubuntu. could you update it on the build machines so that we could have it in daily builds?
[19:47] <hallyn> trying to install natty-desktop from friday's iso, from cd, it was hanging at partman.  (the hd had been pre-partitioned, which may or may not be relevant)  Anyone else see a problem like that?
[19:55] <charlie-tca> hallyn: desktop cd's been doing it all weekend
[19:55] <charlie-tca> ubi-partman error?
[19:55] <MadCow108> can apparmor profiles handle XDG base desktop directories?
[19:55] <MadCow108> XDG_CONFIG_DIR etc
[19:55] <beuno> hallyn, I had that 2 weeks ago, and evan gave me a workaround which I can't find now
[19:56] <beuno> it was bug #722198
[19:56] <jdstrand> MadCow108: I assume you mean dynamically at runtime. That would be 'no', though the situation could be improved somewhat by using variables in the profiles (which we don't yet)
[19:57] <hallyn> charlie-tca: beuno:  thanks, great to know it's not just me :)
[19:58] <hallyn> beuno: hm.  but i dont' have unpartitioned space.  it's all owned by lvm.  how is 'unpartitioned space' defined i wonder?
[19:58] <MadCow108> with runtime you mean change it during apparmor running does not work? but it works when it does not change?
[19:59] <charlie-tca> this is a different bug again, it is the old ubi-partman 141 error back
[20:00] <charlie-tca> It doesn't care if there is blank drive space or not, from what I can tell
[20:08] <jdstrand> MadCow108: by runtime, I mean something like @{HOM}/Private is mapped to something other translated string for 'Private'. that is not possible atm. One can update the profiles to use @{HOME}/<your translated 'Private'> and it would all work fine
[20:08] <jdstrand> s/something/some/
[20:09] <hallyn> charlie-tca: is there an open bug about it that you know of?
[20:10] <leimy> Wondering about the ubuntu process of building release ISOs.  Is there some publicly available build scripts that could make it easy to make a derivative of ubuntu?
[20:10] <charlie-tca> hallyn: I don't know. I saw an update for it today, hoping it got fixed and the images tomorrow will work
[20:11] <leimy> For example I'd really like a 64bit version of JeOS.
[20:11]  * ScottK drums his fingers and look around for barry ...
[20:11] <leimy> but it looks like I might need to do that myself :-)
[20:13] <NCommander> directhex: so upgraded mono-addins, still crashing and buring
[20:15] <NCommander> f-spot works though ...
[20:17] <hallyn> charlie-tca: i can roll with that.  will test tomorrow
[20:17] <charlie-tca> I will be filing one if it fails again tomorrow
[20:17] <hallyn> ok, thanks
[20:32] <MadCow108> jdstrand: why does @{HOME}/.opera/** lrwk, allow opera to lock files in /usr/share? removing the k disallows it. there are no links to /usr/share in ~/.opera
[20:34] <NCommander> directhex: I stil see no love. f-spot will crashes, and banshee still crashes. I find myself going out of my mind in debugging this
[21:03] <cjwatson> charlie-tca: probably bug 729394
[21:03] <cjwatson> (it's not LVM-specific, despite the title)
[21:04] <cjwatson> it won't necessarily be fixed tomorrow, since I'm probably not going to squeeze in another ubiquity upload before going to bed
[21:05] <charlie-tca> Thanks
[21:06] <MadCow108> ah great this is fixed, thanks
[21:07] <MadCow108> was it related to bug 729556?
[21:15] <LLStarks> ev, how do i trigger ubiquity-preserve-home?
[21:36] <cjwatson> MadCow108: I imagine there were several duplicates
[21:37] <directhex> NCommander: i have no idea what's happening with it
[21:37] <cjwatson> I've duped it
[21:41] <leimy> It's been a few hours so I thought I'd ask again.  Is there any kind of way to reproduce an ubuntu build process, or is it that one is just supposed to remaster new systems from selected packages.  I'm still not finding a lot of information on how Ubuntu derivative systems are actually built.
[21:48] <ev> LLStarks: can you elaborate?  If you have an existing copy of Ubuntu, you'll have an option to reinstall or upgrade on the partitioning page on the natty desktop CD.
[21:49] <leimy> Huh, and now the wiki page I was looking at for derivatives has been pulled?
[22:13] <LLStarks> the feature is new to natty right, because i'm wondering whether to recommend a standard or separate-home installation for maverick/natty.
[22:14] <LLStarks> to ev btw
[22:15] <ev> LLStarks: it exists in versions prior to natty in the advanced partitioner
[22:16] <LLStarks> i know,  but natty makes it idiot-proof, right?
[22:16] <ev> LLStarks: if you go into the advanced partitioner and set your partitions back up as they were in the previous version of ubuntu, then uncheck the format button, it will clean out /, preserving /home, /usr/local, etc.
[22:16] <LLStarks> haven't re/installed natty in a few weeks
[22:16] <ev> LLStarks: correct
[22:16] <ev> well, idiot-proof-ish
[22:17] <ev> if you're recommending to people that they use this, please include a disclaimer that they should make a backup first
[22:17] <ev> this will be the first release with this feature (I realize the / clearing stuff has been there for a while, but package reinstallation is new)
[22:17] <ev> there will be bugs
[22:17] <ogra_> fta, did you recently upload a chromium browser SRU that enables NEON in maverick ?
[22:18] <LLStarks> gotcha, thanks ev
[22:18] <ev> LLStarks: sure thing
[22:18]  * ogra_ gets reports from people where it dies with SIGILL since a few days
[22:18] <ogra_> and it seems to be the in-archive package they use
[22:22] <SpamapS> The following NEW packages will be installed: ecryptfs-utils gettext-base keyutils libecryptfs0 libkeyutils1 libnspr4 libnss3 libnss3-1d libpopt0 lsof rsync
[22:22] <SpamapS> Hmm.. more stuff in base files?
[22:25] <fta> ogra, nope, the opposite. neon=0 thumb=1 everywhere, and armv7 on maverick+natty only
[22:26] <ogra> did that recently change ?
[22:26] <fta> ogra, why?
[22:27] <ogra> because i have people in the ac100 community complaining to me that chromium doesnt start for them since a few days
[22:27] <ogra> the browser dies with SIGILL on startup
[22:28] <fta> since ch10, i enforced arm_neon=0 to fix a ftbfs
[22:28] <ogra> so i was wondering if something recently changed in the package (ac100 has no NEON)
[22:29] <fta> could be v7, which i flipped (the test was wrongly reversed before)
[22:29] <ogra> v7 shuld be fine
[22:31] <fta> ogra, http://paste.ubuntu.com/574525/  the various flags/tests in the chromium build system
[22:32] <soren> SpamapS: adduser recommends ecryptfs-utils now.
[22:32] <soren> SpamapS: Up from a suggests.
[22:33] <zyga-ill> cjwatson, hi
[22:34] <zyga-ill> cjwatson, I read your blog post, I'm sure you know that qemu -snashot -hda /dev/sda _does_ allow you to boot into the same operating system again, assuming you have enough storage for temporary files
[22:34] <zyga-ill> -snapshot even
[22:36] <ogra> fta, hmm, that looks to me like neon is on by default
[22:39] <fta> ogra, i'm quite sure i disabled it: http://launchpadlibrarian.net/66221823/buildlog_ubuntu-maverick-armel.chromium-browser_10.0.648.133~r77742-0ubuntu<IP_ADDRESS>_BUILDING.txt.gz
[22:39] <fta> wouldn't build otherwise
[22:40] <fta> i can do a verbose build to confirm if you want
[22:42] <ogra> no, looks fine