[07:57] <jnl> hi, when i pipe bzr log --line to a pager the lines gets chopped off to 78 with (with a "..." at the end), can i avoid this?
[08:13] <mgz> morning
[08:14] <bialix> hi all
[08:14] <bialix> hi jelmer
[08:22] <jnl> n/m, looks like bug in old version (2.0)
[08:41] <matttbe> Hello
[08:41] <matttbe> Recently, I wanted to update the version of Cairo-Dock in Ubuntu.
[08:41] <matttbe> I updated my branch to be synced with the main branch (bzr uncommit -r 25; bzr revert; bzr pull # => now on rev 26) and used merge-upstream option (bzr mu --version "3.0.2" --distribution=quantal).
[08:41] <matttbe> On Launchpad, I can see that the previous rev (26) has the same rev ID on my new branch (lp:~cairo-dock-team/ubuntu/quantal/cairo-dock/3.0.2) and on the main branch (lp:ubuntu/cairo-dock).
[08:41] <matttbe> But if someone tries to merge my new branch into the ubuntu branch, it seems there is a conflict. => https://code.launchpad.net/~cairo-dock-team/ubuntu/quantal/cairo-dock/3.0.2/+merge/111020
[08:41] <matttbe> Note that on rev 26, there is a patch (in debian/patches) which was applied but the diff (available in LP)  seems correct except that if you have a look to the conflict, it seems the previous patched was unapplied before merging:
[08:41] <matttbe> This is what I can find in src/gldit/cairo-dock-callbacks.c:
[08:41] <matttbe> <<<<<<< TREE
[08:41] <matttbe> 		if (pDock->iSidTestMouseOutside == 0 && pEvent)  //(...)
[08:41] <matttbe> [08:41] <matttbe> 		if (pDock->iSidTestMouseOutside == 0 && pEvent && ! pDock->bHasModalWindow)  // (...)
[08:41] <matttbe> >>>>>>> MERGE-SOURCE
[08:41] <matttbe> But we can find this diff on rev 26:
[08:41] <matttbe> -  if (pDock->iSidTestMouseOutside == 0 && pEvent)  // (...)
[08:41] <matttbe> + if (pDock->iSidTestMouseOutside == 0 && pEvent && ! pDock->bMenuVisible)  // (...)
[08:42] <matttbe> Should I have to remove my previous patches, commit and then use bzr merge-upstream?
[09:47] <mgz> matttbe: have you had any luck getting an answer?
[09:48] <matttbe> mgz: no
[09:48] <matttbe> mgz: but if we use 'bzr pull' instead of 'bzr merge', we don't have this bug because  it seems patches are unapplied just before:
[09:48] <matttbe>   > Unapplying quilt patches to prevent spurious conflicts
[09:49] <mgz> right, my guess would be one branch was done with the quilt plugin enabled and the other wasn't
[09:50] <mgz> but I don't understand from yuor description if your branch or lp:ubuntu/cairo-dock has the quilt patches applied in tree
[09:50] <matttbe> yes, lp:ubuntu/cairo-dock has quilt patches applied in tree
[09:51] <matttbe> and these patches are removed in the new one
[09:51] <mgz> in the diff I see the patches are completely removed, right?
[09:51] <matttbe> yes
[09:51] <mgz> were they merged upstream?
[09:52] <mgz> or just dropped?
[09:52] <matttbe> merged upstream
[09:52] <mgz> okay
[09:52]  * mgz ponders
[09:52] <matttbe> but it seems the problem is that they are merge upstream but the same line has been modified too
[09:56] <mgz> so, either you can play with the quilt options in bzr-builddeb and see if one of them helps,
[09:56] <mgz> or just do the merge locally, resolve the conflict and push it?
[09:56] <mgz> jelmer may have better ideas.
[09:56] <matttbe> note that in lp:ubuntu/cairo-dock, there is a patch (which is applied in tree) to remove one line in: src/gldit/cairo-dock-keybinder.h
[09:56] <matttbe> Now this patch is no longer needed (merged upstream) but if we use 'bzr merge', the line is still there
[09:57] <matttbe> yes, I merge it locally, resolve conflict, revert the wrong change in src/gldit/cairo-dock-keybinder.h and  push it on another branch
[10:02]  * jelmer reads up on the last few minutes of converstaion..
[10:02] <matttbe> but if we use 'bzr pull' we don't have any problem (but if the sponsor want to merge this branch just to modify the ubuntu version in debian/changelog and push only one rev, it's not so easy and he has to check that all files are corrects)
[10:02] <matttbe> maybe it can be interesting to unapply patches just before merging (if it's possible)
[10:02] <jelmer> matttbe: bzr-builddeb can do that
[10:03] <matttbe> jelmer: but who has to do that? the sponsor?
[10:04] <jelmer> matttbe: matttbe whoever does the merge
[10:04] <matttbe> ok, thank you!
[10:06] <jelmer> matttbe: the bzr-builddeb has some documentation; you'll need a newer version of bzr-builddeb
[10:08] <matttbe> jelmer: I've the version 2.8.4 from Ubuntu Quantal repos
[10:11] <jelmer> that should be new enough
[10:21] <matttbe> jelmer: but what should the sponsor has to use? I used 'bzr merge-upstream' and everything was ok for me (but not for the sponsor)
[10:22] <matttbe> I see that now 'bzr mu' unapplied patches and it's great but then, the sponsor has to use 'bzr pull', or is there another solution?
[10:24] <jelmer> matttbe: if you've done the merge then the sponsor shouldn't have to do it again
[10:28] <matttbe> jelmer: except if he want to do modifications, no? e.g. the current Ubuntu version in debian/changelog is set as UNRELEASED (or should I've to set modify it but I thought that it had to be done by the sponsor)
[10:35] <jelmer> matttbe: sure, but he shouldn't get conflicts that you (or bzr-builddeb for you) resolved earlier
[10:40] <matttbe> yes but he doesn't have this conflicts if he uses 'bzr pull' because 'quilt pop -a' command is automatically launched. This is why I wonder why patches are not automatically unapplied if we use 'bzr merge'.
[10:40] <matttbe> But if you say that the sponsor has to use 'bzr pull' and not 'bzr merge', I can understand. Now I know what the sponsor has to do with my branch ;)
[10:41] <jelmer> matttbe: I'm not sure I follow - 'bzr merge' already should be automatically unapplying patches for '3.0 (quilt)' during a merge
[10:46] <matttbe> jelmer: yes, you're right, sorry. But if it removes patches, it will not see that patches have been removed and then the diff is wrong.
[10:46] <matttbe> jelmer: Or is it maybe simply because patches shouldn't be applied in tree?
[10:46] <jelmer> matttbe: What do you mean with "But if it removes patches, it will not see that patches have been removed and then the diff is wrong" ?
[10:47] <jml> I'm using 'bzr branch lp:foo' in an automated environment. Is there any way to shut up the warning about launchpad-login?
[10:47] <jml> I guess I can just specify the http url.
[10:48] <jelmer> jml: specifying the http URL is probably easiest
[10:48] <jelmer> there might me some warning suppressing config option too, though I'm not sure about the name..
[10:48] <jelmer> jml: no, doesn't look like we have a way to silence that message~
[10:49] <jml> jelmer: thanks.
[10:57] <matttbe> jelmer: on lp:ubuntu/cairo-dock, there is a patch (applied in tree) which removes one line in one file. With the new version, we can remove this patch (merged upstream). On my branch, 'bzr mu' has unapplied this patch and I've removed it (with 'quilt delete -r').
[10:57] <matttbe> But if the sponsor merge my branch, the line has not been removed.
[10:57] <matttbe> It's maybe because if this patch is unapplied just before merging, the line is still in the tree (ok) and then, if we merge this branch with no applied patches with my new branch, this line will remain because on my branch, I don't have changed this file (if we have a look to the diff file, we don't see any modification about this line because I don't modify between the two revisions)
[10:57] <matttbe> Sorry, I'm not sure that it's understandable :)
[10:57] <matttbe> (and I don't know how bzr works to do the merge)
[11:10] <jelmer> matttbe: is the change also gone from the working tree, and from the .pc directory (quilt should take care of that)
[11:12] <matttbe> after the merge (my new branch => lp:ubuntu/cairo-dock), the '.pc' directory is empty and debian/patches only contain 'series' (which is empty)
[11:16] <matttbe> in fact, I guess I'll have the same result if I do that:
[11:16] <matttbe> quilt pop -a ## Now the line is reverted back in the corresponding file
[11:16] <matttbe> bzr commit ## just to do the merge or I have to use bzr merge --force
[11:16] <matttbe> bzr merge my_new_branch ## the line is still there
[11:18] <matttbe> (yes, I confirm I've the same problem if I launch these commands)
[13:42] <alf_> james_w: jelmer_: Hi! I am trying to merge a new version of a package with merge-upstream, but it complains that "bzr: ERROR: Upstream version 2012.06 has already been merged." . I had previously merged 2012.06 and commited, but then reverted/uncommitted the changes.
[13:43] <james_w> alf_, run bzr tags and you will see an upstream-2012.06 tag?
[13:43] <james_w> "bzr tag --delete upstream-2012.06" and you should be good to merge again
[13:45] <alf_> james_w: Right, "upstream-2012.06     ?" . I did that and now I am getting: bzr: ERROR: Unable to find the tag for the previous upstream version, 2012.06, in the branch: upstream-2012.06
[13:45] <james_w> alf_, hmm
[13:46] <james_w> alf_, do you have a 2012.06 tag hanging around as well?
[13:46] <alf_> james_w: no
[13:46] <james_w> alf_, hmm
[13:47] <james_w> alf_, and I guess debian/changelog has no mention of 2012.06 any more?
[13:48] <alf_> james_w: aha, I made an intermediate commit to update the debian/ dir and have a 2012.06 entry in the debian changelog as UNRELEASED.
[13:49] <james_w> alf_, that will be it then
[13:51] <alf_> james_w: ok, so how do I get around that? Do I have to uncommit?
[13:51] <james_w> alf_, if you remove that entry from the changelog and commit then it should work
[13:52] <alf_> james_w: so 1. remove that entry, commit, then 2. merge-upstream ?
[13:52] <james_w> alf_, I think so
[13:53] <alf_> james_w: it worked, thanks!
[13:55] <jam1> james_w: I replied to jml's message about upgrading jubany. I imagine we'll want both you and vila around if/when we deploy to Jubany.
[13:55] <jam1> What time do you usually start in the AM?
[13:55] <jam1> (utc)
[13:56] <james_w> jam, 1300
[13:56] <jam> james_w, so about 1hr ago, right?
[13:57] <james_w> jam, yeah
[13:57] <vila> jam: huh ?
[13:58] <jam> vila: see the thread about upgrading udd
[13:58] <jam> I think it is reasonable to try to roll out storm again, and if it fails, just roll it back.
[13:58] <jam> But we don't have to be afraid of that step, as long as we can catch it and roll it back quickly if it starts failing.
[13:58]  * vila blinks
[13:58] <jam> and if we get it working, then we can think more sanely about a next step.
[14:00] <jam> vila: why do you think it is unsafe to *try* a storm rollout?
[14:00] <vila> because it failed at last attempt ?
[14:01] <vila> corrupting the db ?
[14:01] <vila> maxb knows the details, I've just read his emails
[14:01] <jam> vila, james_w: did it actually corrupt the db? I realize some bits got deadlocked.
[14:01] <jam> and it wouldn't be rolling out the exact code, it would be with an update to avoid the increased isolation level.
[14:01] <jam> I don't see a point to rolling out the exact thing we know was failing.
[14:02] <james_w> it did write some bad data due to the db due to storms behaviour regarding str/unicode
[14:02] <jam> james_w: was that part of the fixes from max?
[14:02] <james_w> but I plan to fix the instance Max found and do another pass looking for other cases
[14:02] <jam> (fixes unrelated to locking to quote you)
[14:02] <james_w> jam, we haven't yet fixed the last instance he found
[14:02] <james_w> but we fixed some other things before rolling back
[14:02] <jam> so that would be a blocker, certainly.
[14:03] <james_w> yep
[14:04] <jam> james_w: so another possible transition plan would be to wait until we get some sort of staging system setup.
[14:04] <vila> +1e6
[14:04] <jam> I feel like the timeline on that is a bit... unbounded
[14:05] <vila> I thought a basic test was conducted on ec2 ?
[14:05] <jam> if it isn't, then it 'races' with finishing the unicode/str fixes
[14:05] <jam> if we can get a staging set up first, or close to the same time, then doi t
[14:05] <jam> it
[14:05] <vila> not to mention the pristine-tar failures ?
[14:05] <jam> vila: isn't pristine-tar 100% orthogonal to this?
[14:06] <vila> when it comes to deployment, no
[14:06] <james_w> a staging system that would do everything except push the branches back?
[14:06] <jam> james_w: something like that
[14:06] <jam> I would have some concern that 'doing work but throwing it away' might thrash (if say the primary is stopped for a while)
[14:06] <jam> james_w: but we really need a place we can test things that isn't prod
[14:07] <james_w> yes
[14:07] <vila> james_w: as long as you start with a copy of the dbs
[14:08] <vila> james_w: pushing does some more db updates but.. well, if the rest is ok, you'll know what to expect
[14:08] <jam> james_w: do you have any idea of a timeline for the unicode fixes? I imagine if you felt there was no way to get the code deployed, it wasn't worked on as a priority. :)
[14:09] <jam> vila, james_w: So if we feel there is a reasonable recovery step (snapshot the dbs first, know exactly what to roll back to), it feels like we can at least start to get forward momentum. And if we can get things moving, then we can *improve* stuff.
[14:11] <jam> jelmer_: are you still doing up-merges?
[14:11] <james_w> vila, what bd operations does the push do?
[14:11] <james_w> db
[14:11] <jelmer_> jam: nope, I'm done
[14:11] <james_w> it won't test things like filing merge proposals, or the push code
[14:11] <jam> jelmer_: how are the lp branches coming?
[14:11] <james_w> and makes the bookeeping a bit off
[14:11] <james_w> is that an issue?
[14:12] <vila> james_w: I thought the revids were recorded after pushing ? (That's a gut feeling not from reading the code)
[14:13] <jelmer_> jam: I was struggling with some tests yesterday, am currently reviewing
[14:13] <jam> jelmer_: as in doing reviews for others? Or getting the branches reviewe
[14:13] <jam> d?
[14:13] <james_w> vila, ah yes, sorry, I was reading the wrong bit
[14:13] <vila> james_w: at least when I test locally, doing the same import without pushing seems to redo the same steps
[14:13] <james_w> yeah
[14:14] <james_w> I see what jam means about thrashing now
[14:14] <james_w> jam, indeed, I hadn't done the fixes because it wasn't clear what the plan was
[14:14] <jelmer_> jam: reviewing for others
[14:14] <james_w> jam, they are just a couple of hours work though
[14:18] <jam> anyway, I'm at EOD (have to go take my son to swimming), but I'd like us to hash out a quick 'next steps' and see what can get the ball moving again.
[14:26] <james_w> I'll followup on the mailing list
[18:26] <LeoNerd> FSCKING REBASE!
[18:26] <LeoNerd> Can anyone tell me why I have to 'bzr unbind' before it'll actually work? I hate having to do this
[18:27] <LeoNerd> Otherwise it immediately claims that bzr: ERROR: Bound branch BzrBranch6(file:///home/leo/src/perl/IO-Async.TASKS/) is out of date with master branch RemoteBranch(bzr+ssh://cel/var/bzr/leo/perl/IO-Async.TASKS/).
[18:30] <jelmer_> LeoNerd: why would you want to use rebase with a checkout?
[18:30] <LeoNerd> Because I never do anything that isn't in a checkout
[18:30] <LeoNerd> I don't trust my ability not to lose my laptop or crash its disk, so everything is backed up on my server
[18:31] <LeoNerd> Currently I  bzr unbind;  bzr rebase ..... bzr bind :bound; bzr push --overwrite :bound
[18:38] <jelmer_> LeoNerd: generally you would make a checkout of the master branch
[18:38] <jelmer_> LeoNerd: and it's pretty uncommon to rewrite branches in the main project branch
[18:39] <LeoNerd> Hrm? It's not the main branch. It's a feature branch
[18:39] <jelmer_> anyway, what you're trying to do isn't really wrong but it's not very common either
[18:39] <LeoNerd> I rebase it after every main release
[18:56] <CodeNinjaSD> Does bazaar support E-mail messages to one or more addresses should be generated when a change is committed. Format of e-mail may change (e.g., doc committer committing to src tree)
[19:00] <CodeNinjaSD> What about sthe ability to attach searchable/annotated tags, other than revision number to code artifacts
[19:03] <gour>  /c
[19:16] <psusi> I have noticed that I made a slight error a few commits back.  With git, I would fix the error, commit it, then rebase -i to sqash that commit back into the previous one.  How can I do this with bzr?
[19:16] <psusi> or maybe pop the last few commits off the branch into patch files, fix the errored commit, then reapply the patches


[00:07] <slangasek> kirkland: well, hopefully the buildds will catch up by then
[00:07] <kirkland> slangasek: let's hope there's more bandwidth too by then
[01:35] <Darxus> Starting my first upgrade to a pre-release.
[01:36] <jdong> :) it's not all that painfull
[01:36] <jdong> as long as upstart doesn't bite ;-)
[01:36] <Darxus> Heh.
[01:36] <sistpoty> !jdong
[01:36] <slangasek> well, the NFS-hanging-boot bug should be fixed now
[01:36] <Darxus> I've done some pretty dumb stuff, intentionally, and survived.
[01:36] <Darxus> And I have a full backup, and both the beta cd, and the jaunty cd.
[01:37] <sistpoty> jdong: meh, who "fixed" ubottu :P
[01:37] <jdong> sistpoty: IRC council I'd guess :)
[01:37] <sistpoty> hehe
[01:42]  * feat testing
[01:43]  * feat testing Ubuntu 9.10 - acer aspire one D150
[01:44] <feat> ?
[01:45] <Darxus> 1779M to download, eta 2 hours 27 minutes.  Damn.
[01:45] <feat> yep
[01:45] <feat> 3 hrs ç
[01:45] <feat> xD
[01:46] <Darxus> 33 packages removed, 392 new packages, 1605 upgraded.
[01:46] <Darxus> It's amaizing this ever works :P
[01:46]  * Darxus loves on apt.
[01:46] <feat> :O
[01:46] <feat> you speak spanish
[01:46] <feat> ?
[01:47] <Darxus> Me?   I think there's a real problem with gdm upgrades
[02:07] <maxb> it seems you can't upgrade gdm whilst a session is running any more
[03:11] <ion> Heh. upgrade to the most recent stuff, switch from fi.archive.ubuntu.com to archive.ubuntu.com and upgrade to the most recent stuff: 164 packages upgraded, 1 newly installed, 2 to remove and 0 not upgraded. It’s almost as if the mirror were *gasp* a bit behind. :-) (I realize it’s possible a lot of packages were just published by an archive admin, though.)
[04:40] <Darxus> I just submitted a bug, and it was marked as a duplicate of https://bugs.launchpad.net/bugs/365371 but that page is saying "Sorry, you don't have permission to access this page.  You are logged in as Darxus."  What's up with that?
[04:40] <Darxus> Hah.
[04:40] <Darxus> WTF?
[04:45] <Linux_Boricua> Hello
[04:45] <Linux_Boricua> ola
[04:45] <Linux_Boricua> alguien ke me ayude
[04:45] <Linux_Boricua> por favor
[04:45] <Linux_Boricua> alguien que hable español
[04:45] <Linux_Boricua> ????
[04:46] <LaserJock> Darxus: so it got dup'd to a private bug
[04:46] <Linux_Boricua> What??
[04:47] <Linux_Boricua> I do not speak English
[04:47] <LaserJock> Linux_Boricua: #ubuntu-es ?
[04:47] <slangasek> Linux_Boricua: este no es un canal de ayuda; le recomiendo preguntar en #ubuntu-es
[04:47] <Linux_Boricua> mmm
[04:47] <Linux_Boricua> bueno este
[04:47] <Linux_Boricua> es que quiero saber
[04:48] <Linux_Boricua> algo solamente
[04:48] <Darxus> LaserJock: Yes.  What's up with the bug being private?
[04:48] <Linux_Boricua> :D
[04:48] <Linux_Boricua> es que no quiero ayuda en esencial solo quiero aclarme unas dudas
[04:48] <Linux_Boricua> :D
[04:48] <Linux_Boricua> jajaj
[04:48] <LaserJock> Darxus: crasher bugs are automatically marked Private, that could be the issue
[04:49] <Darxus> Weird.
[04:50] <Darxus> I can't even figure out who marked it duplicate....
[04:51] <LaserJock> Darxus: it was automatically dup'd
[04:51] <LaserJock> Darxus: the apport retracer detected that it was a dup
[04:54] <LaserJock> Darxus: the private bug looks like it could be made private, but I don't know for sure
[04:54] <LaserJock> be made public, rather
[04:55] <Darxus> Okay.  I'll try to stop worrying about it :P
[04:55] <Darxus> Thanks.
[05:04] <zsoc> ~seen Mithrandir
[05:05]  * zsoc wonders if there's a similar working bot command to the one he just embarrassedly failed at
[05:13] <Darxus> zsoc: Doesn't look like it.
[05:14] <Darxus> zsoc: That nick has not occurred in this channel while I've been here.
[05:14] <Darxus> --- Log opened Mon Sep 21 19:07:49 2009
[05:14] <zsoc> Wow, hm. I am going a bit back. Thanks for checking the logs :) Guess I'll send him an email.
[05:15] <Darxus> You're welcome.
[10:35] <ccm> is the channel for the global jam?
[10:54] <ccm> dholbachc: is the channel for the global jam?
[10:54] <ccm> erm
[10:54] <ccm> dholbach: is the channel for the global jam?
[10:55] <dholbach> ccm: I don't know :)
[10:57] <dholbach> #ubuntu-locoteams maybe?
[10:59] <dholbach> bdrung: can you all yourselves to https://wiki.ubuntu.com/Bugs/Events
[11:00] <mdz> cjwatson, apw, sorry, I was confused by cjwatson's comment. I think it's important to have a full changelog in the binary package. just having a copy of the old debian/changelog (all of it!) installed as changelog.Debian.old would be good enough
[12:23] <dholbach> does anybody know how an upgrade from CD is supposed to work?
[12:23] <ogra> isnt there a cdromupgrade script on the alternate CD ?
[12:23] <dholbach> when I put in the CD a dialogue asks me something and if say "Yes", it opens synaptic
[12:23] <dholbach> that was a desktop cd
[12:23] <dholbach> hi ogra :)
[12:23] <ogra> ah
[12:23] <ogra> you cant upgrade from desktop
[12:24] <ogra> hey
[12:24] <dholbach> ah...!
[12:24] <dholbach> ok
[12:24] <ogra> desktop only has a few actual packages, the real system is in the squashfs and gets copied 1:1 on install
[12:24] <dholbach> yeah
[12:24] <dholbach> ok
[12:24] <dholbach> that makes sense
[12:24] <dholbach> we have to wait a bit then :-)
[12:26] <tormod> dholbach, for user support, ask in #ubuntu ;)
[12:26] <ogra> lol
[12:26]  * dholbach slaps tormod with a trout
[12:26] <dholbach> hi tormod :)
[12:27] <tormod> hi dholbach, trying "dogfood" ?
[12:27] <dholbach> we're test-installing a bunch of machines during the Ubuntu Berlin Jam here
[12:27] <dholbach> and #ubuntu-testing is asleep
[12:28] <tormod> dholbach, how many are you?
[12:28] <dholbach> 8
[12:28] <dholbach> and 1 dog
[12:28] <dholbach> but we just started to get rolling
[13:57] <directhex> ARGH, still no audio via hdmi, even on karmic
[13:59]  * directhex prods dtchen
[15:14] <mnemonikk> i've got a problem with booting karmic, the root device isn't recognized during booting if i specify it by uuid. It says that /dev/disk/by-uuid/... doesn't exist. If I specify it by its traditional device name it works fine, in /etc/fstab i also use uuids with no problem. Is this a problem of the linux kernel or an upstart problem? Maybe it's a problem that I'm still using murder^Wreiserfs?
[15:25] <tormod> mnemonikk, /dev/disk/by-uuid/.. doesn't exist after booting either?
[15:26] <mnemonikk> tormod: well, that's what it says.
[15:26] <mnemonikk> tormod: i can't do much in the init shell, though.
[15:27] <tormod> mnemonikk, when you boot with trad name, there is still no by-uuid link after boot?
[15:28] <tormod> mnemonikk, ls -l /dev/disk/by-uuid/ should show the uuid
[15:28] <mnemonikk> tormod: if i boot with root=/dev/sdaX, then /dev/disk/by-uuid/.. exists.
[15:28] <mnemonikk> tormod: i've got other partitions apart from the root partition that get mounted properly, and they are specified by uuid in the /etc/fstab.
[15:28] <mnemonikk> tormod: yes, that works, the link is there.
[15:31] <mnemonikk> tormod: does the fs type play a role in generating these uuids?
[15:31] <tormod> mnemonikk, should not, especially since it works later
[15:32] <mnemonikk> tormod: me still using reiserfs is a bit unusual, which would explain why no one else fixed this earlier.
[15:32] <tormod> mnemonikk, I guess so
[15:33] <mnemonikk> tormod: i could imagine something like that the reiserfs module is not loaded and so the proper uuid cannot be generated.
[15:34] <tormod> mnemonikk, yes that would explain it. do you have reiserfs (?) in /etc/initramfs-tools/modules?
[15:34] <mnemonikk> tormod: no, nothing.
[15:35] <tormod> mnemonikk, try that. the installer or initramfs-tools should add that module if root is on reiserfs IMO. how did you install?
[15:35] <mnemonikk> tormod: should i add it, do update-initramfs and try again?
[15:35] <tormod> mnemonikk, yes
[15:36] <mnemonikk> tormod: I think the last install was feisty, or something... upgraded since then.
[15:38] <mnemonikk> tormod: I'll try that now.
[15:41] <tormod> mnemonikk, I am just checking /usr/share/initramfs-tools/hook-functions and I see reiserfs is in the "base" modules. try modprobe reiserfs in the initrd shell.
[15:46] <mnemonikk> tormod: I get into the initramfs shell when I press the power button. is that the right way to do it?
[15:46] <mnemonikk> tormod: and resume with ^D?
[15:47] <tormod> mnemonikk, not sure I follow, when you press the power button?
[15:47] <mnemonikk> tormod: added reiserfs to /etc/initramfs-tools/modules, did sudo update-initramfs -u and tried with the uuid again, didn't work.
[15:48] <mnemonikk> tormod: i press the power button when I think it's waiting for the root fs too long. Or how am I supposed to get the initrd shell?
[15:48] <tormod> mnemonikk, oh I see, it's hanging. it should time out after a minute or so.
[15:49] <mnemonikk> tormod: so maybe it was just a coincidence.
[15:49] <mnemonikk> tormod: hold on...
[15:50] <tormod> mnemonikk, in the initrd shell, see if reiserfs module has been / can be loaded. then check ls -l /dev/disk/by-uuid there.
[15:57] <pgraner> kirkland: ping
[15:58] <mnemonikk> tormod: i did a modprobe, it still can't find /dev/disk/by-uuid/xxx.
[15:58] <mnemonikk> tormod: there's no "ls" in my initrd.
[15:59] <tormod> mnemonikk, then your initrd must be broken. you are not running out of disk space?
[16:01] <mnemonikk> tormod: hum, no, not currently.
[16:02] <mnemonikk> tormod: "update-initramfs -u" is the correct incantation?
[16:03] <tormod> mnemonikk, yes, as long as your booting the same (or one) kernel that your initrd is for, otherwise add "-k all"
[16:04] <mnemonikk> tormod: ok... any idea what else I could try?
[16:05] <tormod> mnemonikk, if "ls" does not work I wonder if something is really broken. Otherwise, see if your disk device exist (ls -l /dev/sd*) and check the UUIDs on them with "/sbin/blkid /dev/sda1" etc
[16:06] <mnemonikk> tormod: you mean, I should call blkid from initrd?
[16:07] <tormod> mnemonikk, yes, you can try it out in the booted system to get the hang of it, it should be the same, but we want to see if it works in the initrd
[16:08] <mnemonikk> tormod: i have to try that later, have to go now. thanks for your help!
[16:08] <tormod> mnemonikk, please file a bug or question, and feel free to subscribe me to it
[17:14] <directhex> dtchen, poke poke?
[17:21] <dtchen> directhex: hi
[17:35] <directhex> dtchen, is there some documentation on how to debug a distinct lack of sound via hdmi on karmic?
[17:41] <dtchen> directhex: not consolidated, and mostly trial-'n-error
[17:42] <dtchen> directhex: namely, make sure it works in ALSA first
[17:42] <dtchen> directhex: so the process is (briefly): disable PA autospawn; test the plug HDMI device using speaker-test
[17:43] <dtchen> directhex: (and killall pulseaudio immediately after disabling PA autospawn)
[17:43] <directhex> how would one disable PA autospawn on a temporary basis?
[17:44] <dtchen> echo autospawn = no|tee -a ~/.pulse/client.conf
[17:48] <Amaranth> Isn't there a pa suspender program or something for that too?
[17:48] <dtchen> Amaranth: it does the wrong thing when you're trying to test certain functionality
[17:48] <Amaranth> ah
[17:50] <dtchen> directhex: i presume you've tested pavucontrol, too, and are able to reproduce this symptom using it?
[17:51] <dtchen> directhex: also, it would be quite useful if it's reproducible in PA 0.9.19 (in the ubuntu-audio-dev PPA)
[17:52] <directhex> aha! made it work via alsa!
[17:52] <directhex> had to unmute an IEC in alsamixer
[17:53] <directhex> so, now to see what happens if i turn PA back on
[17:55] <directhex> hurrah, audio in mythtv!
[17:56] <directhex> first time since i built this pc
[17:56] <directhex> now to see if it persists across reboots
[18:00] <kees> kenvandine, pitti: erm, your upload of xsplash (0.8.2-0ubuntu1) did not include the 0.8.1-0ubuntu2 changes...
[18:06] <Darxus> I'm trying to test the debian experimental version of the hugin package under karmic, to get it moved to sid and then synced to lucid.
[18:08] <Darxus> Oh, hmm, maybe it's not in main.
[18:10] <Darxus> No, it's in main.
[18:11] <kirkland> pgraner: pong
[18:12] <Darxus> http://www.chaosreigns.com/ubuntu/experimental.txt
[18:13] <Darxus> ^ Contents of /etc/apt/preferences, and the output of apt-cache policy hugin, showing that the version from experimental is available but not getting the priority I set in preferences.  Why not?
[18:20] <pgraner> kirkland: question on enc-swap
[18:20] <kirkland> pgraner: yo
[18:21] <pgraner> kirkland: is there a way to temp disable to test to see if  a hibernate prob is due to the enc-swap?
[18:21] <kirkland> pgraner: i don't understand your question
[18:22] <pgraner> kirkland: someone has issues with hibernate and he is using enc-swap. I need to have him test without they enc-swap to see if that make the prob go away
[18:22] <pgraner> kirkland: I'm looking for a enc-swap=0 on the kernel command line or something
[18:25] <kirkland> pgraner: oh, yeah, you can't resume from hibernate if you have encrypted swap
[18:25] <pgraner> kirkland: do we have that documented somewhere I can point to
[18:25] <kirkland> pgraner: yeah, a bunch of places
[18:26] <kirkland> pgraner: i'll grab you a link
[18:26] <pgraner> kirkland: I googled all over and came up with nadda
[18:27] <kirkland> pgraner: you can turn it off in /etc/crypttab
[18:28] <kirkland> pgraner: hmm, we were supposed to remove the "Hibernate" button from the Shut Down menui
[18:28] <kirkland> pgraner: i see that hasn't happened yet
[18:35] <pgraner> kirkland: ok, if you can point me to the "hibernate is not supported" reference material I can get rid of one "regression" bug :-)
[18:35] <kirkland> pgraner: i'm writing it now
[18:35] <kirkland> pgraner: i found it scattered in a few places
[18:36] <kirkland> pgraner: but nothing comprehensive
[18:36] <kirkland> I'm putting something up now
[18:36] <kirkland> pgraner: on help.ubuntu.com
[18:36] <pgraner> kirkland: great thanks man, you rock.
[18:37] <kirkland> pgraner: and then i'm going watch football :-)
[18:38] <pgraner> kirkland: I'm at the nc Global Jam squashing bugs in real time....
[18:39] <pgraner> kirkland: dude get some dedication :-)
[18:39] <kirkland> pgraner: i am dedicated ... to the Texas A&M v. Arkansas game at the new Jerry Jones Deathstar in Dallas
[18:39] <pgraner> kirkland: yea yea I hear ya
[18:41] <pgraner> kirkland: drop me the link when your done
[18:41] <kirkland> pgraner: nearly done
[18:57] <kirkland> pgraner: https://help.ubuntu.com/community/EncryptedHome
[18:59] <pgraner> kirkland: thanks dude. Enjoy the game
[19:00] <kirkland> pgraner: thanks
[19:00] <kirkland> pgraner: watching LSU v. Georgia first
[19:06] <Darxus> I believe I found a bug in apt pinning in karmic, I'd appreciate confirmation:  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/441585
[19:16] <ebroder> Ugh - are there any more local mirrors (to the US) of the daily CD builds than cdimage.ubuntu.com
[19:19] <LaserJock> ebroder: I don't think so
[19:20] <ebroder> :(
[19:27] <zsakr> Hello, any one know how I can determine the  size(in bytes and/or blocks) of  an iso filesystem if it's  in a  larger container?  Am willing to read superblocks in hex.
[19:27] <zsakr> t's in a larger contaner, so the reported size is  too big.
[19:27] <zsakr> if I do something like like ls -l file.iso that is
[19:28] <zsakr> Some thing like ckisofs or tun(e)isofs, I've looked for docs describing the superblock but  couldn't fnd any.
[19:31] <devned> anyone know for sis mirage 3D (M671/M672) driver on ubuntu 9.04 ? And who can make it ? becouse from sis  declaned support for this product
[19:35] <devned> i was geting only for SuSe pack files for this project byt i not have enought skills on c++
[19:36] <ScottK> devned: support is in #ubuntu
[19:36] <ScottK> zsakr: You too ^^^
[19:41] <devned> Scottk thanks
[20:09] <Darxus> apt-get and aptitude keep telling me stuff is not installable that apt-cache policy says is installable.  How can I figure out what the hell is going on?  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/441626
[20:09] <kanuha> If I wanted to add KDE to the Ubuntu 9.10 Beta, which package would I need to install? kdebase-workspace?
[20:10] <ScottK> kanuha: kubuntu-desktop
[20:10] <ScottK> That will bring you a full KDE system
[20:11] <kanuha> ScottK, thx
[20:11] <Darxus> How does apt-get decide what is installable?
[20:11] <Darxus> This seems like a pretty major karmic bug.
[20:15] <ScottK> Darxus: Check and make sure the exact same version of libpano13-0 is also available.
[20:15] <ScottK> If not, it will be available, but not installable.
[20:15] <Darxus> Ah.
[20:17] <Darxus> Hmm, the install just worked.
[20:42] <highvoltage> jono: glad to see I'm not the only one working on a saturday night :)
[20:45] <jono> highvoltage, hehe
[20:46] <jono> what are you working on?
[20:46]  * MenZa sips his tea.
[20:47] <highvoltage> jono: I was working on ltsp-related bugs for a client. tight now I'm actually playing with snowy (http://brad.getcoded.net/blog/entry.php?e=348085118)
[20:48] <highvoltage> (s/tight/right)
[20:48] <ScottK> Darxus: Probably libpano13-0 hadn't quite published the first time you tried.  Generally it's better to show up and ask something like "I don't understand why ..." that announce "OMG, bugz."
[20:49] <jono> highvoltage, cool
[20:56] <porcorico> hey ubuntu devs
[20:57] <porcorico> how y'all doing?
[20:57] <porcorico> I just came here to tell you that I am enjoying the beta
[20:58] <porcorico> and also to ask info on the HP printer thingie hidden in the Main Menu...
[21:01] <porcorico> This thingie right here: http://imgur.com/8CFbh.png
[21:02] <porcorico> I don't understand what is that
[21:02] <porcorico> I don't have printers installed
[22:28] <DexterF> 'evening
[22:28] <DexterF> what's the recommended procedure for 9.04->9.10b?
[22:29] <DexterF> is there an upgrade-manager yet or is it safe to do it with aptitude?
[22:29] <ebroder> DexterF: `sudo do-release-upgrade -d`, but #ubuntu+1 is more appropriate for that sort of question
[22:29] <ebroder> (upgrade-manager would presumably also work)
[22:29] <DexterF> ah, thanks.
[22:49] <YokoZar> What's the user-friendly way of figuring out if you're on i386 or amd64?  We don't mention this in System->About Ubuntu, About Gnome, or even in System Monitor
[22:50] <sistpoty> YokoZar: my best guess would be /proc/cpuinfo
[22:54] <jpds> YokoZar: uname --machine ?
[23:11] <LaserJock> we don't need Release Team approval for uploads yet do we?
[23:11] <ebroder> Just bugfixes should still be OK, right?
[23:12] <sistpoty> LaserJock, ebroder: for bugfixes only, I assume it's still ok (otherwise I'm violating the policy :P)
[23:16] <YokoZar> sistpoty: jpds: was hoping for a non-terminal command ;)  oh well
[23:19] <dtchen> YokoZar: System -> Administration -> Log File Viewer -> dmesg
[23:22] <dtchen> YokoZar: or Xorg.0.log, since it prints the current operating system
[23:24] <ion> zul: Hi. Please see bug 441518. Debdiff attached.


[01:50] <amurray> jamespage: jdstrand has uploaded my iptables updates for hirsute and groovy - groovy is still in unapproved but hirsute is in -proposed - could you please verify this resolves the issue with neutron-linuxbridge-agent? (I have checked it via the simple iptables-restore test in the bug)
[01:52] <amurray> jamespage: but I don't have a configured install of openstack/neutron to test that neutron-linuxbridge-agent itself is happier with this change so it would be good to get this verified as well if possible
[09:10] <jamespage> amurray: yep we can do that
[09:10] <jamespage> we had an alternative reproducer as well
[09:17] <mwhudson> cpaelzer__: "Merge with Debian unstable (LP: #9999999)" :)
[09:39] <cpaelzer__> did that get into the changelog mwhudson - grml
[09:39] <cpaelzer__> thanks for the ping
[09:40] <cpaelzer__> and sorry
[09:47] <cpaelzer__> ok my pre upload checker now has a detection for this case
[09:47] <cpaelzer__> and since it was in proposed still I have uploaded a fixed ubuntu2
[09:47] <cpaelzer__> thanks again mwhudson
[10:20] <alkisg> Hi, a very recent update in 18.04 (maybe accountmanager or systemd) makes slick-greeter segfault, so MATE users get black screens. I'll start searching which update exactly caused it, but did anyone already report it?
[10:35] <seb128> it's annoying that python-apt blows up every cycle until it's updated to include the new codename :-/
[10:39] <Unit193> Too bad it can't steal from distro-info-data...
[10:51] <alkisg> The black screen (slick-greeter segfault) in 18.04 is caused by the systemd update
[10:51] <alkisg> "Bump the memlock limit"
[10:53] <alkisg> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746
[10:55] <Laney> sounds similar to the lightdm-gtk-greeter thing seb128 was looking into
[10:58] <alkisg> I also found a related lightdm bug about memory limits causing segfaults there: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1662244
[10:59] <alkisg> I commented in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/comments/16, let's see...
[10:59] <seb128> alkisg, what systemd update?
[10:59] <alkisg> seb128: see 1830746
[10:59] <alkisg> It was sent to 18.04 a couple of days ago
[11:00] <alkisg> It's enforcing some memory limits that lightdm doesn't like, causing the greeters to segfault
[11:00] <seb128> that bug is old
[11:00] <seb128> you mean https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 ?
[11:00] <seb128> that is recent
[11:01] <alkisg> apt changelog systemd, in 18.04, shows 1830746
[11:01] <alkisg> It's systemd 237-3ubunt10.43
[11:01] <alkisg> Signed Wed, 07 Oct 2020
[11:01] <seb128> thx
[11:04] <seb128> bah, gnome-boxes isn't working for me anymore
[11:04] <seb128> libvirt-machine.vala:275: Failed to connection to system libvirt: Unable to open qemu+unix:///system: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory
[11:04] <seb128> does that error ring a bell to anyone?
[11:11] <alkisg> Putting * soft memlock 262144 in /etc/security/limits.conf avoids the segfault. Should all lightdm users put that manually there, or should we expect an update?
[11:12] <seb128> alkisg, you should reach to ddstreet and the SRU team to get the systemd SRU blocked probably until that's sorted out
[11:12] <seb128> sil2100, ^
[11:12] <seb128> alkisg, is there a launchpad report for the slick-greeter issue yet?
[11:12] <cpaelzer> seb128: rings a few bells, let me check with you which it could be in your case
[11:13] <alkisg> seb128, a related lightdm report is this: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1662244
[11:13] <cpaelzer> seb128: does the socket not exist at all OR is it there and just something can't access
[11:13] <alkisg> It was characterized as "invalid" because the reported had manually played with memory limits, but it's the same problem; now they're enforced by systemd
[11:13] <alkisg> *the reporter
[11:14] <alkisg> I've cross-linked the two bug reports with appropriate comments
[11:14] <seb128> cpaelzer, /var/run/libvirt doesn't exists
[11:14] <seb128> alkisg, we would need a new report from the systemd regression I think
[11:15] <cpaelzer> seb128: service not started maybe?
[11:16] <cpaelzer> seb128: do you have pkg libvirt-daemon-system istalled?
[11:16] <cpaelzer> +n
[11:16] <seb128> cpaelzer, what packag... no, I don't
[11:16] <seb128> shouldn't that we pulled it through some depends?
[11:16] <cpaelzer> that is what brings the service files and anything else that you need to run, so get this installed
[11:17] <cpaelzer> seb128: yes if the dependencies of what you installed are correct :-)
[11:17] <seb128> it's weird, gnome-boxes was working until a week ago
[11:17] <seb128> and according to my dpkg.log* that didn't get uninstalled
[11:17] <seb128> like that was never installed
[11:17] <seb128> I wonder what changed :/
[11:18] <cpaelzer> seb128: there are three entry points to libvirt a) libvirt-daemon-system (what most packages should depend on) b) libvirt-clients (if you jsut want the CLI but server is remote) and c) libvirt-daemon (the binaries, but to drive it your own way)
[11:18] <alkisg> I tried 'sudo apport-bug /var/crash/_usr_sbin_slick-greeter.110.crash', and it displayed the initial apport dialog, but then nothing; what's the correct command to open a new launchpad bug while including the crash dump?
[11:18] <seb128> alkisg, that probably submit to errors.ubuntu.com
[11:19] <cpaelzer> seb128: I have a suspicion - they might have changed their dep to "libvirt-daemon-driver-qemu" which expresses that they want that particuar virtualization of the many it supports
[11:19] <seb128> cpaelzer, I think gnome-boxes might do c) ?
[11:19] <cpaelzer> but that does not bring in (a) but only (c) to allow non default .service solution
[11:20] <cpaelzer> seb128: they are indeed (c) and they were back to at least focal
[11:20] <cpaelzer> but if a solution goes (c) then it needs to take care itself to start the daemon somehow
[11:20] <cpaelzer> not sure what happened on that part
[11:21] <seb128> cpaelzer, should 'sudo libvirtd' work or is that naive and I need some arguments?
[11:21] <seb128> 2020-11-04 11:20:52.930+0000: 24979: error : virGetUserID:848 : invalid argument: Failed to parse user 'libvirt-qemu'
[11:21] <cpaelzer> there is more to do
[11:21] <cpaelzer> the default config needs some help to fit your case
[11:22] <seb128> well, I was just trying to figure out if the issue is that libvirtd errors out
[11:22] <cpaelzer> if it would be the service that we provide the systemctl status would show
[11:22] <cpaelzer> but in your case you need to find if/how gnome-boxe start their local version
[11:22] <seb128> cpaelzer, my journal has
[11:22] <seb128> nov. 04 12:20:18 sebxps libvirtd[24864]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied
[11:22] <seb128> nov. 04 12:20:18 sebxps libvirtd[24864]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied
[11:22] <cpaelzer> and start/debug that
[11:22] <cpaelzer> they probably start the daemon under the users permission
[11:23] <seb128> which match time where I tried to start gnome-boxes
[11:23] <cpaelzer> which can work, but you won't have appamor isolation (and many other things)
[11:23] <seb128> k, so probably not the error I'm looking for
[11:25] <seb128> cpaelzer, thanks for the help, I installed libvirt-daemon-system and that warning is gone but gnome-boxes still segfaults so I think it was maybe a redherring and I'm hitting a bug in boxes itself
[11:25] <seb128> I learnt a bit on the way though :)
[11:30] <cpaelzer> yw seb128
[11:45] <seb128> alkisg, you basically need https://github.com/linuxmint/slick-greeter/commit/f9af95ea3f.patch cherry picked, I'm also wondering if it means lightdm-gtk-greeter is going to hit the issue now on bionic & focal
[11:45] <seb128> ddstreet, ^ opinion since you did the systemd SRU?
[12:28] <ahasenack> sergiodj: congrats on becoming an Ubuntu Core Developer! :)
[12:41] <sil2100> seb128: thanks for the heads up
[12:44] <sil2100> alkisg: as per my comment on the bug, could you fill in a new bug for this and tag it 'regression-update'?
[12:45] <seb128> sil2100, it's bricking user systems, I would argue we should back that version out of updates back to proposed until that's sorted out
[12:54] <ricotz> what is the interval this site is expect to be updated? https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[12:54] <sil2100> seb128: I'll try to address this after my current meeting
[12:55] <sil2100> (since I'm having an interview)
[13:02] <alkisg> sil2100: sure, I'll do it this afternoon or tomorrow morning
[13:03] <alkisg> Thank you both
[13:14] <seb128> ricotz, those details have never been clear to me,I think when there is archive publisher cycle done which is probably every hour or so
[13:15] <seb128> ricotz, the recent updates have been failed on a an http error 500 from https://people.canonical.com/~ubuntu-archive/proposed-migration/log/groovy/2020-11-04/12:38:14.log
[13:15] <ricotz> seb128, I see, if that is the case, then something seems broken ;)
[13:15] <ricotz> ah ok
[13:16] <seb128> I mentied it on #ubuntu-release now
[13:17] <ricotz> thanks
[13:26] <alkisg> sil2100, seb128: I filed LP bug 1902879, thank you :)
[13:27] <seb128> alkisg, thanks
[14:46] <sergiodj> ahasenack: thanks :)
[15:10] <seb128> rbalint, bug 902832 claims to a regression from the recent bionic glibc SRU, could you have a look?
[15:14] <seb128> rbalint, sorry one digit missed when copying, bug #1902832
[15:18] <rbalint> seb128, thanks, will look into that soon
[15:19] <rbalint> sil2100, could you please stop phasing glibc until this is triaged?
[16:43] <max12345> Hi, newb question, There are bugs at https://bugs.launchpad.net/package and https://bugs.launchpad.net/ubuntu/+source/package and they're different, how is that?
[16:46] <cjwatson> max12345: The first of those represents an upstream project; the second represents a package in Ubuntu
[16:46] <ogra> the former are upstream projects (original developers, no dirsto packaging) ... the latter one is the ubuntu package in the distro
[16:46] <ogra> *distro
[16:46] <ogra> (also ... *snap* ... )
[16:47] <cjwatson> max12345: like, "the Linux kernel" (/linux) is not necessarily quite the same thing as "the Linux kernel in Ubuntu" (/ubuntu/+source/linux).  The kernel doesn't track its upstream bugs in Launchpad as it happens, but some projects do.
[16:49] <max12345> cjwatson: thanks you! that makes sense.
[19:20] <seb128> is there any documentation on how the Ubuntu ISO builds are done (components involved, how they are called, etc) or on how to locally set up and drive the process?
[19:20] <seb128> something which could be used to do local build testing e.g livecd-rootfs changes
[19:21] <seb128> xnox, mwhudson, sil2100, you might know? you have experience working on image builds, unsure how you usually test your changes?
[19:23] <mwhudson> seb128: it's definitely a pain
[19:24] <mwhudson> seb128: for subiquity i have a script that repacks the iso with a new subiquity snap
[19:24] <mwhudson> it could be adapted to be more generic
[19:24] <seb128> mwhudson, I don't want to repack an iso though, I want to fix/produce a new one for the desktop installer
[19:26] <mwhudson> seb128: are you talking about on your system or what steps have to be taken to start making a new image type on cdimage.ubuntu.com
[19:27] <mwhudson> on your system it really is easier to repack an ISO, for the new desktop installer i'd take a live server installer iso, replace the filesystem and installer squashfses and repack
[19:28] <mwhudson> making a new image type means changes to ubuntu-cdimage, and probably some scripts and config i don't have access to
[19:30] <seb128> mwhudson, we already have a new image 'canary' which was set up by didrocks and j_ible some cycles ago
[19:30] <seb128> mwhudson, I'm trying to understand how the image is built to be able to tweak it and also fix the build which was broken after changes in how kernels are handled from what I've been told
[19:31] <mwhudson> seb128: ok, so ubuntu-cdimage is the place to start
[19:31] <seb128> mwhudson, I'm not familiar with the process so would be nice to be able to test locally my changes to livecd-rootfs instead of submitting poke in the dark fixes
[19:31] <mwhudson> seb128: it has a concept of a "project" (or at least i think that's what it's called)
[19:32] <mwhudson> building a project means starting a livefs build per arch on launchpad, downloading the results, building a pool and using our fork of debian-cd-ubuntu to turn it into an ISO
[19:33] <mwhudson> seb128: livecd-rootfs changes i usually just test by doing a livefs build on launchpad and inspecting the artefacts, not putting them on an ISO
[19:33] <mwhudson> depends a bit what you are doing though
[19:34] <mwhudson> i have a script for starting a livefs build: https://paste.ubuntu.com/p/HmNk7y7xYY/
[19:35] <seb128> mwhudson, I was trying to start by driving livecd-rootfs by doing similar to what is described on https://chenhan1218.github.io/post/2016-07-06-763254/
[19:36] <mwhudson> seb128: oh right, running livecd-rootfs locally is another nest of vipers
[19:36] <mwhudson> the cpc team have some scripts for this iirc, i've never used them though
[19:37] <seb128> do you know who from cpc I could try to ping about that?
[19:37] <seb128> it's a bit annoying that it's undocumented
[19:37] <seb128> I wonder how many people had to refigure the details out by themself :/
[19:37] <mwhudson> rcj might still be around?
[19:38] <seb128> mwhudson, thanks for the help, I will keep poking!
[19:39] <mwhudson> seb128: the alternative is to read the launchpad-buildd source, figure out how it drives live-build and repeat that by hand
[19:39] <mwhudson> i've done this in the past but forget the details now
[19:40] <mwhudson> seb128: good luck
[19:40] <seb128> thx
[19:45] <rcj> seb128: You can use our tools that recreate the LP build env as faithfully in AWS or multipass as we can using https://github.com/chrisglass/ubuntu-old-fashioned
[19:45] <rcj> The 'bartender' script automates things further https://github.com/chrisglass/ubuntu-old-fashioned/blob/master/scripts/ubuntu-bartender/ubuntu-bartender
[19:45] <seb128> rcj, ah, great, thanks for the url, the description looks like what I want :)
[19:47] <rcj> seb128: and we've checked with cjwatson and wgrant in the past to ensure we're running the same commands from launchpad-buildd, etc to make this a decent development platform without the need to wait for livecd-rootfs ppa publication and let you drop into the lxd container when things go sideways.
[19:48] <seb128> rcj, that's exactly what I needed :)
[20:06] <tribaal> rcj: oh wow, that thing lives on :)
[20:07] <tribaal> (that URL highlighted :) )
[21:07] <rcj> tribaal: Hey man, how are you doing?
[21:07] <rcj> We keep patching it ;)
[21:09] <Odd_Bloke> It's becoming more and more old fashioned by the day.
[23:43] <xnox> mwhudson:  how can godefaults to 1.15 work in hirsute-proposed? are you gonna keep riscv64 on 1.14? I was hoping to skip 1.14 and go for 1.16 later...... however debian will be frozen at that point in time.
[23:44] <xnox> mwhudson:  do we need to upload golang-defaults that makes it 1.15 everywhere, and 1.14 on riscv64? i've tried to do cherrypicks of all the fixes from 1.16 to 1.15 even with jsing backport/patches and it failed to build for me =(
[23:44] <xnox> (on all arches)


 How are you liking 2013?
[13:04] <waltman> oops, 2014.
[13:05] <rmg51> so JonathanD, who won the 2012 election?
[13:06] <JonathanD> Fred.
[13:07] <waltman> rmg51: I imagine the timecops won't let him tell us.
[13:08] <rmg51> I just want to know if I should stock up on tea :P
[13:11] <waltman> rmg51: You should always have tea in stock, because tea is yummy and good for you!
[13:12] <rmg51> it just depends on what type of "party" is involved
[13:14] <waltman> I'm thinking more "Alice" than "Boston"
[15:13] <andrew> I hiked for about 7 miles yesterday, with 30-35lb pack
[21:48] <waltman> I have a sad confession to make: I caused perfectly good bacon to be wasted today.
[21:49] <waltman> I stopped at a diner this morning and ordered pancakes and sausage. The waitress brought out pancakes and sausage. When I said I'd ordered sausage, she went into the kitchen and came back out with sausage.
[21:49] <waltman> Then it gets confusing. I thought she said she was just going to take back the bacon and give it to someone else. Instead she took it from me and threw it out right in front of me.
[21:49] <waltman> So sad.
[21:49] <waltman> I didn't really want to eat both, but the women sitting next to me at the counter were already coveting the bacon.
[21:51] <waltman> I've spent the rest of the day wondering how I could have saved my bacon.
[21:56] <waltman> but...sausage really is the superior breakfast meat with pancakes.


[00:02] <RAOF> rafaeldtinoco: Both uploads, I assume?
[00:03] <rafaeldtinoco> RAOF: yes please
[00:03] <RAOF> Done!
[00:03] <rafaeldtinoco> RAOF: tks a lot
[08:54] <toabctl> bdmurray, hey. I see commits in https://code.launchpad.net/~ubuntu-on-ec2/vmbuilder/jenkins_kvm from 202o from you. is that project used by you somehow? I'm asking because the CPC team would like to move the project to git
[14:37] <bdmurray> toabctl: No, I just fixed a typo
[15:03] <toabctl> bdmurray, ok. thanks
[15:15] <jawn-smith> Is someone else covering sil2100's SRU shift today?
[15:41] <bdmurray> jawn-smith: I can push some buttons
[15:43] <jawn-smith> bdmurray: in this case you pushed the button to upload to the queue, so someone else needs to approve it right?
[15:43] <jawn-smith> LP: #1923352
[15:45] <bdmurray> jawn-smith: ah, that's true
[15:46] <jawn-smith> bdmurray: thanks though!
[15:50] <jawn-smith> Trying to get more SRU experience. Is any core or SRU dev available to take a look at LP: #1913656 ?
[15:51] <jawn-smith> till-kamppeter has stated that the SRU template and patch look good.
[15:55] <jawn-smith> (preferably someone who isn't on the foundations team, due to the feedback I received in my first core-dev application)
[16:46] <jawn-smith> There's also LP: #1938442. It has verbal approval from till and we have submitted a patch upstream. The SRU's could use some review though
[16:57] <jawn-smith> In order for livecd-rootfs to migrate it will need to be tested against the new ubuntu-image in -proposed. This has already been done and passed on amd64 and s390x
[16:57] <jawn-smith> Is any core dev available to start this test on arm64 as well? https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=arm64&package=ubuntu-image&trigger=livecd-rootfs/2.743&trigger=ubuntu-image/2.0%2B22.04ubuntu3
[18:05] <bdmurray> I started that test
[18:05] <jawn-smith> bdmurray: thanks!
[19:10] <rbasak> !dmb-ping
[21:41] <ItzSwirlz> FYI GNOME/related devs using meson in Debian: Debian Bugs #998124
[21:41] <ItzSwirlz> regression of meson 0.60 ^


[00:00] <astraljava> micahg: It's a good starting point. :)
[00:01] <micahg> well, we always need testing :)
[00:01] <micahg> anyone else?
[00:01] <DaveF_> Specs say 11.04 needs 4.4 GB of space. Can I still FULL INSTALL it on a 4GB USB drive- I don't need all the apps like Gimp, office, or games.
[00:03]  * micahg thinks xubuntu will fit on that, but can't be 100% sure
[00:03] <pleia2> you can use the alternate installer to install on less than 4G
[00:03]  * micahg thought there was a bug recently about the space requirements being wrong
[00:03] <pleia2> yeah
[00:03] <pleia2> ubiquity requires 4.4
[00:04] <DaveF_> thanks!
[00:04]  * micahg cries over the 803MB i386 daily live ISO
[00:04] <DaveF_> I'm new to linux so I need the system gui apps like synaptic, etcs, I can always ad Libreoffice, gimp later if I need and have space
[00:05] <DaveF_> pleia2: do you know what is missing from the alternate cd?
[00:05] <astraljava> micahg: It'll come down in time, for sure. :)
[00:05] <pleia2> DaveF_: nothing, it's a different installer that doesn't have the same hard-coded installation requirements (the 4.4 is actually for ubuntu, not xubuntu)
[00:05] <micahg> astraljava: s/gdm/lightdm in the seed should knock off at least 50 :)
[00:05] <astraljava> micahg: Great!
[00:06] <DaveF_> pleia2: thanks. I tried ubuntu but dont like the unity interface (like so many others)
[00:06] <pleia2> it's not for everyone :)
[00:07] <astraljava> pleia2: What do you mean? I thought Ubuntu was supposed to be Linux for Everyone! :D
[00:07] <DaveF_> pleia2: so the normal installer is that much bigger than the alternate installer?
[00:08] <pleia2> DaveF_: it's not the installer that's bigger, the installer just checks for 4.4G before moving forward to make sure ubuntu will fit - xubuntu is smaller so it doesn't *need* 4.4G free, but the installer still checks for it
[00:08] <pleia2> the bug report is here: https://bugs.launchpad.net/xubuntu-website/+bug/784020
[00:08] <DaveF_> Ah! any less apps in the alternate, that you know of?
[00:08] <pleia2> no, it's identical
[00:09] <DaveF_> pleia2: Cool! and thanks!
[00:09] <pleia2> welcome :)
[00:09] <DaveF_> I use LiLi USB Creator to build my USB installs - works great!
[00:09] <pleia2> micahg: thanks for chairing!
[00:10] <astraljava> Yeah, good job!
[00:12] <micahg> pleia2: thanks, my first time :)
[00:12]  * micahg just send the meeting notes off to the ML
[00:12] <micahg> thanks to everyone for coming
[00:15] <astraljava> Thanks for hosting! Will be back tomorrow to talk about testing, might in fact be able to do daily tests for the time being.
[00:22] <micahg> astraljava: cool, charlie-tca should be back tomorrow and he has more info on testing
[00:26] <astraljava> micahg: Yeah, sure I'll talk to him more about it.
[00:48] <Unit193> I did a test of 32 alt today (Was my turn) and I know drc also does some testing
[01:15] <pleia2> oh, we never got an alpha 1 news post on the site, we should be sure to designate a writer of these things for alpha2 (I can get it posted)
[01:15] <pleia2> if we don't think it's too late for alpha1 I can post that too :)
[01:51] <micahg> welcome back GridCube
[01:51] <GridCube> thank you
[01:51] <micahg> GridCube: I was in the middle or conducting the meeting when you left
[01:51] <GridCube> oh
[01:51] <GridCube> sorry
[01:51] <GridCube> :/ did i miss something?
[01:52] <micahg> GridCube: it's ok, I posted the noted to the mailing list, not much
[01:52] <micahg> *notes
[01:52] <GridCube> oh i don't have a mailing list list
[01:52] <GridCube> i mean im not in the mailing list list
[01:52]  * micahg is digging up a URL
[01:53] <micahg> GridCube: https://lists.ubuntu.com/archives/xubuntu-devel/2011-June/007814.html
[01:55] <GridCube> oh :) thanks
[01:57] <GridCube> micahg, i wonder, couldnt xubuntu have a first run welcome thing? like a link to an html on the desktop that people can double clic and read really basic stuff about the system?
[01:57]  * micahg thought that already exists
[01:57] <GridCube> like a short faq?
[01:57] <GridCube> no its not there, not easily visible tho
[01:58] <GridCube> if you happen to install xfce you get the "tips" but is not enabled on xubuntu
[01:58] <GridCube> and thats also really anoying and people just usually dissmiss it
[02:00] <Unit193> micahg: Do you happen to know how many people are on the list?
[02:00] <micahg> Unit193: no, sorry, I am not a list admin
[02:01] <micahg> GridCube: maybe write an e-mail to the xubuntu-devel list with a proposal?
[02:01] <Unit193> Thanks
[02:03] <GridCube> mmm ok i will ask charlie next time i see him
[03:15] <xrdodrx> GridCube, I think that'd be better accessible from the menu, like how ubuntu used to do it
[03:15] <xrdodrx> "About Xubuntu"
[03:15] <xrdodrx> right now we've got About Xfce
[03:16] <xrdodrx> and of course these entries could both be hidden in the usual way
[03:16] <GridCube> probably, but the "about xfce" just gives licences and not a guide to do simple tasks
[03:17] <xrdodrx> well no one said we had to do it the same way ;)
[03:17] <GridCube> like for example saying to people, "How do i enable mp3? you install gstreamer" "how to compiz? see this site" etc
[03:18] <GridCube> something like read me
[03:18] <xrdodrx> I don't think that stuff is basic at all, especially the second one
[03:18] <GridCube> XD yeah well
[03:18] <GridCube> but its an usual question
[03:18] <GridCube> for xfce4.8 you have to have a "how do i move panels? you unlock them" XD
[03:19] <xrdodrx> for most OS, the about page outlines the programs installed by default and contains links to further documentation
[03:19] <GridCube> mmm yes
[03:19] <xrdodrx> I don't think it's smart to have the about page immediately tell you how to enable compiz or mp3 support
[03:19] <xrdodrx> especially since mp3 is a non-free technology, that shouldn't be the first thing in our about page :)
[03:20] <xrdodrx> just my ideas
[03:20] <GridCube> thats probably why i said  "a first run welcome thing" stuff like, "you need more help, go to #xubuntu"
[03:20] <xrdodrx> IRC isn't very welcoming to newcomers,, it can be quite confusing for those who've never used it
[03:21] <GridCube> well, forums them
[03:21] <GridCube> something to tell them they are not alone
[03:21] <xrdodrx> oh, I know what you mean
[03:21] <GridCube> its frigthening changing an operative system
[03:22] <xrdodrx> but an OS's about page is usually really basic and outlines the OS's features and programs, maybe a better help system can help with this, but I don't know how this fits into the oneiric development schedule
[03:22] <GridCube> and having something right there saying "hey you are welcome"
[03:22] <GridCube> mmm yes i see
[03:31] <GridCube> i never imagined nothing that complex tho
[03:32] <GridCube> just something like, for example, the firefox first run page?
[14:44] <charlie-tca> Good morning
[14:45] <charlie-tca> I think I 'm here. I got about 30 seconds lag today
[14:45] <charlie-tca> micahg: thanks for chairing the meeting. I was setting up Oneiric yesterday
[14:45]  * charlie-tca forgot about the time change for the meeting, too, but that is not my excuse.
[14:46] <DarkEra> Good morning charlie-tca, yep you're here :)
[14:46] <DarkEra> Strange to say good morning... its afternoon over here....
[14:57] <charlie-tca> Well, Good afternoon, then!
[15:00] <DarkEra> thanks :-)
[15:19] <charlie-tca> bbl
[15:19] <micahg> charlie-tca: you're welcome, glad all is ok
[15:20] <charlie-tca> not *all* okay
[15:20] <charlie-tca> I can't quite get oneiric to start email or news online
[15:20] <charlie-tca> and my email seems severely broken
[15:21] <charlie-tca> and Users and Groups fails, too
[15:21] <charlie-tca> can't add new users or groups with the GUI
[15:21] <micahg> hmmm, well, the new network manager API breaks backwards compatability, I wouldn't be surprised if there were issues, but Firefox seems to work fine
[15:21] <charlie-tca> but in general, yes, I didn't mean to scare you.
[15:21] <charlie-tca> things are going fine, me.
[15:22] <charlie-tca> things are going fine, for me.
[15:22] <charlie-tca> I installed fresh
[15:24] <micahg> hmmm, and you're using thunderbird or something else?
[16:21] <charlie-tca> claws-mail. Have to try Thunderbird and see how it works in Oneiric
[16:36] <micahg> charlie-tca: ah, claws-mail needs a merge, I can try to take care of that this week if barry doesn't want to do it
[16:36] <micahg> oh, wait, no i can't, over the weekend then :)
[16:36] <charlie-tca> Yeah, it seems kind of broken
[16:37] <ochosi> micahg: btw, *if* you decide to take care of claws, what would be really nice would be to activate indicator support
[16:37] <GridCube> hello charlie-tca
[16:37] <charlie-tca> GridCube: Hello
[16:37] <charlie-tca> any signs of drc today?
[16:37] <GridCube> don't know
[16:38] <GridCube> just singed in today
[16:38] <ochosi> micahg: i mean bug 715257
[16:38] <charlie-tca> I want to know what is happening to our daily testing?
[16:38] <charlie-tca> No one showed up at the meeting yesterday for testing either.
[16:41] <charlie-tca> I think we are seeing things broken due to gtk3. some of the errors are that applications are not able to use gtk2 and gtk3 at the same time.
[16:42] <micahg> ochosi: that's a separate source :)
[16:43] <charlie-tca> ochosi: I would prefer a bigger font than droid gives us
[16:43] <charlie-tca> or at least a bigger size than we are defaulting to
[16:43] <charlie-tca> or something...  I wasn't really able to be at the meeting, but I made a comment after
[18:35] <charlie-tca> no, not yet
[18:36] <charlie-tca> I sort of lost my .org address temporarily, and just got it back
[18:36] <charlie-tca> I will go see if there are emails to release to the ML, I guess
[18:44] <Unit193> charlie-tca: I was talking about memoserv msg
[18:45] <charlie-tca> Oh, got it
[18:45] <charlie-tca> yes, thanks for checking it
[18:45] <Unit193> You were not on and I wasn't sure if I would remember :P
[18:45] <Unit193> No problem! Isn't that what I'm supposed to be doing?
[18:45] <charlie-tca> I don't check for those
[18:46] <charlie-tca> it is fine to do that, I will have to check to see if there any
[18:46] <charlie-tca> Otherwise, we mail the xubuntu-devel ML with issues
[18:50] <Unit193> I wasn't sure if it would PM you when you got on, or if it would "notice" you
[18:52] <charlie-tca> It doesn't seem to PM me. It was a notice but since all notices are a separate tab, I don't look at them when logging in. It notices all the log in buttetins, which I don't need to see everytime.
[19:02] <charlie-tca> oh, we never do a login sound for Xubuntu
[19:02] <astraljava> Hi charlie-tca! I guess I somehow sorta kinda promised I would be helping out with testing. *grin*
[19:03] <astraljava> in the last night's meeting, I mean
[19:03] <charlie-tca> Really?
[19:03] <charlie-tca> that's great!
[19:03] <Unit193> It was on the list...
[19:03] <astraljava> Hehe. Yeah. :)
[19:03] <charlie-tca> We can always use more testers
[19:03] <astraljava> I thought as much.
[19:03] <charlie-tca> Are you able to test daily or milestones?
[19:04] <astraljava> Well at the moment I should be able to do dailies as well.
[19:04] <charlie-tca> Unit193: really? I guess I have to go update that list, then.
[19:05] <charlie-tca> astraljava: welcome to testing Xubuntu1
[19:05] <astraljava> Thanks! :)
[19:05] <charlie-tca> We have some information at https://wiki.ubuntu.com/Xubuntu/Testing
[19:05] <charlie-tca> We would like to run the short test daily, but at the least, we run an install
[19:06] <astraljava> Yeah I'm actually using that page as a reference for Ubuntu Studio testing procedure enhancements.
[19:06] <charlie-tca> The main thing at this point in the cycle is install, update, restart, shutdown
[19:07] <charlie-tca> preasure ****
[19:07] <charlie-tca> Ubuntu Studio wants up to date docs, and they want mine up to date to help them update theirs :-)
[19:08] <astraljava> Exactly. :D No pressure or anything, but... ;D
[19:08] <charlie-tca> lol
[19:08] <astraljava> Nah, I'm here to help as well.
[19:08] <charlie-tca> We can all use help
[19:09] <astraljava> Most definitely. I hear you're running under quite a lot of stress.
[19:09] <astraljava> If I can ease some of that, would be awesome.
[19:09] <charlie-tca> Help with testing is awesome
[19:10] <charlie-tca> drc was organizing it some for us. We think we can test all the images twice a week or so
[19:10] <astraljava> I have several boxen here that I can use, I just first need to figure out which of them can boot from a USB stick, that would help a lot.
[19:10] <charlie-tca> yeah, I guess. I am one of the users with "older" systems. I can't boot from usb
[19:10] <micahg> charlie-tca: will you be around this evening?
[19:10] <charlie-tca> micahg: I can be, yes
[19:11] <micahg> k, maybe we can chat a little bit then
[19:11] <charlie-tca> Okay, I will be here then
[19:12] <charlie-tca> You might have to ping me, but I will stay around
[19:18] <micahg> k, don't worry if you can't, I'll catch you tomorrow
[20:15] <astraljava> Crap, I chose alternate install iso. ;)
[20:15] <ochosi> charlie-tca: what do you mean? droid works in pretty much any size in my xp
[20:15] <charlie-tca> that's okay, we got both alternate and desktop images
[20:16] <charlie-tca> ochosi: we start with a very tiny font size for droid, it can be increased, but the default is a 10, I think?
[20:16] <charlie-tca> and droid has smaller letters than sans, for example, so 10 droid is about 8 or 9 sans
[20:17] <charlie-tca> I am wondering if we shouldn't be starting at maybe 12 or 14 with it?
[20:17] <astraljava> charlie-tca: Actually, you don't. Not at least in the daily cdimage section.
[20:17] <charlie-tca> huh?
[20:18] <astraljava> http://cdimage.ubuntu.com/xubuntu/daily/20110606/
[20:19] <charlie-tca> that's the alternate, desktop is http://cdimages.ubuntu.com/xubuntu/daily-live/current/
[20:19] <astraljava> HAHA!
[20:19] <astraljava> Oh man.
[20:19] <astraljava> I suck.
[20:19] <charlie-tca> We will help you. Before you know it, you will be smart again
[20:21]  * charlie-tca thinks that sounds wrong, but the intent was very nice :-)
[20:21] <astraljava> I sincerely doubt that, but I like the sound of that. :D
[20:23] <charlie-tca> ochosi: making these windows all the way to the screen bottom takes a lot of getting used to, too
[20:23] <ochosi> charlie-tca: k, i won't be around much now, let's test this a bit more in the upcoming weeks
[20:23]  * micahg is reminded of the Star Trek TNG episode "Samaritan Snare"
[20:23] <charlie-tca> okay
[20:23] <ochosi> (actually i have a few busy weeks ahead of me)
[20:24] <ochosi> charlie-tca: what would be great is something like a screenshot-comparison of the different font-sizes
[20:24] <ochosi> that'd make it easy for everyone
[20:24] <charlie-tca> I will make notes then, so we have something to start with
[20:24] <ochosi> because DPI settings are also really crucial for that
[20:24] <charlie-tca> I can try to do screenshots
[20:24] <ochosi> different DPI settings, different font-size
[20:24] <charlie-tca> Okay
[20:24] <ochosi> that's actually a real problem with setting the default..
[20:25] <charlie-tca> They reverted the DPI back to 96 now, so it should stay the same
[20:25] <ochosi> because something in x (not sure what exactly) calculates the "optimum" dpi settings for your resolution
[20:25] <charlie-tca> really?
[20:25] <ochosi> otherwise the pixels look blurry
[20:25] <cody-somerville> micahg, did you ping me?
[20:25] <charlie-tca> I will try different things, then
[20:25] <ochosi> yeah, thanks
[20:25] <charlie-tca> no problem
[20:25] <charlie-tca> LIke I say, it could be my eyes, too
[20:25] <ochosi> or the resolution ;)
[20:26] <charlie-tca> lol
[20:26] <charlie-tca> again with the resolution wrong?
[20:30] <micahg> cody-somerville: yesterday to see if you wanted to run the meeting in charlie-tca's absence
[20:30]  * charlie-tca hides face again
[20:31] <micahg> charlie-tca: no worries :)
[20:32] <charlie-tca> Leafpad has print capability now. Mousepad is stalled unless jeromeg picks it up.
[20:35] <micahg> charlie-tca: jannis dented that nick might pick it up
[20:35] <micahg> (mousepad)
[20:36] <charlie-tca> Maybe I got the name wrong, I though I saw where jeromeg might. At least if one of them does, it will be good.
[21:30] <astraljava> Well, the alternate worked okay.
[21:31] <astraljava> Going to try the desktop now.
[21:33] <charlie-tca> 32 or 64bit?
[21:34] <astraljava> 32-bit
[21:34] <charlie-tca> Great! Thanks for testing it
[21:34] <Unit193> There goes my job...
[21:35] <astraljava> Unit193: My humblest apologies. :D
[21:35] <charlie-tca> you ain't getting off that easy
[21:35] <Unit193> astraljava: Thanks!
[21:35] <Unit193> I'm guessing I followed the short list too closely...
[21:36] <charlie-tca> You get to try again tomorrow, Unit193
[21:37] <charlie-tca> Unit193: alternate manual install, desktop guided resize tomorrow, please.
[21:42] <Unit193> charlie-tca: I did the alt cd last. I do it again? (It was whole disk)
[21:44] <Unit193> Do you have things in mind you want me to test? or just mostly follow the short guide?
[21:46] <charlie-tca> mostly follow the guide. Yup, want the test again, but this time instead of whole disk, manual partition
[21:47] <charlie-tca> If you did the whole short test, just install, restart, update, restart, shutdown is good
[21:48] <Unit193> Yes, boss!
[21:48] <astraljava> Does xubuntu have update-manager, btw.?
[21:48] <astraljava> I _could_ look it up, of course...
[21:48] <charlie-tca> Got to know right away if the partitioning or boots or shutdowns fail on these. That will get them fixed quicker
[21:49] <charlie-tca> yes, it does, astraljava
[21:49] <astraljava> charlie-tca: Okay, and it should have notified me of updates?
[21:49] <charlie-tca> I forget to use it sometimes, but it is there. We do not insist on you being forced to use it immediately, though
[21:49] <astraljava> charlie-tca: Cause I didn't even try since it didn't.
[21:49] <charlie-tca> It should notify, after a few to several minutes
[21:49] <astraljava> Right, okay.
[21:49] <Unit193> apt-get is fine?
[21:50] <charlie-tca> yup
[21:50] <charlie-tca> If you download updates while installing, it usually triggers update-manager quickly, otherwise, it can take it quite a while to trigger
[21:50] <Unit193> I'll report back here or memo you, sound good?
[21:51] <charlie-tca> sounds good, yes
[21:51] <charlie-tca> hm, seems I will need to leave my xchat up, so I get these messages properly.
[21:52] <Unit193> Did you see the email about the guy that doesn't want LibreOffice? (I would like it included)
[21:53] <charlie-tca> We won't add libreoffice as a default application, it is too big and slow
[21:55] <Unit193> That works for me!
[21:55] <astraljava> Damn, maverick's usb-creator crashes while trying to create an install disk from the desktop iso
[21:55] <charlie-tca> try unetbootin, it works better for me
[21:57] <astraljava> Okay, will do.
[22:11] <charlie-tca> Unit193: answered that email
[22:12] <charlie-tca> Unit193: I don't what day the image he tried was, I installed Oneiric this weekend and am using it now.  I thought I picked oneiric iso, as I don't even have a natty iso for xubuntu on my system.
[22:19] <astraljava> But it said "You are installing the latest, 11.04 of Xubuntu"
[22:19] <astraljava> ...or something...
[22:28] <astraljava> Hmm... shouldn't update-manager ask for password when you're doing a check, too? Similar to `sudo apt-get update'?
[22:32] <astraljava> Well, desktop install for 32-bit seems to work very well too. Nothing to update, so cannot verify that part.
[22:44] <charlie-tca> no, password only asks for password to do the updates themselves, usually
[22:44] <charlie-tca> It might not have the wording updated yet, something for Unit193 to verify tomorrow, though.
[22:45] <charlie-tca> astraljava: how many people you got in studio that will be testing for you?
[22:46] <charlie-tca> oops, got to run
[22:50] <astraljava> charlie-tca: I have no idea, so far.
[22:50] <astraljava> Just got into this position last night. :)
[23:23] <Unit193> So I need to check for "Installing 11.04"
[23:24] <Unit193> charlie-tca: When you get back (To answer your question) http://paste.ubuntu.com/620327/
[23:27] <astraljava> Unit193: Yeah, that's on one of the screens when using the desktop installer icon, when the actual installation procedure kicks in.
[23:29] <Unit193> astraljava: I'm doing the alt install tomorrow (Depending on what charlie-tca wants, I may have to do both...)
[23:34] <astraljava> Unit193: Okay cool, I'll be here to see how it goes for you at some point, my bro will come for an over-night, but I should have some time.


[11:17] <airurando> got efibre today :-)
[11:19] <airurando> AndrewMcC: 46Mbps download and 17Mbps upload over WiFi
[11:21] <ebel> noise
[11:30] <zmoylan-br> nice with autocorrect? :-)
[11:32] <airurando> ebel: noise?  off topic or you don't consider that good? or as zmoylan-br suggested autocorrect difficulties?
[11:33] <ebel> sorry, noice :P
[11:33] <ebel> with an accent
[11:33] <zmoylan-br> ah, posh nice
[11:33] <ebel> airurando: btw got the CDs, shall leave in tog tonight
[11:33] <airurando> he he
[11:33] <ebel> Swear to god, I've been to tog ~3 times with the CDs in my bag and forgot to take them out
[11:34] <airurando> good ebel. if you want more just shout
[11:34] <tdr112> hey airurando
[11:34] <tdr112> going to 3d camp again this year ?
[11:36] <airurando> hi tdr112.
[11:36] <airurando> not this year.
[11:37] <airurando> I was in Limerick for the last two weekends
[11:37] <tdr112> ah well, I will have to see you some other time
[11:37] <airurando> Oisins communion is next weekend
[11:37] <airurando> just relaxing at home this weekend
[11:38] <airurando> tdr112 definitely
[11:38] <tdr112> airurando: did they have to dig up your garden for the new efibre
[11:40] <airurando> tdr112: nope
[11:41] <airurando> changed the main eircom point to the one in the sitting room and that was it.
[11:59] <czajkowski> airurando: howdy
[11:59] <czajkowski> tdr112: ello
[12:01] <tdr112> hey cztab
[12:01] <tdr112> I am heading down to your old college for 3dcamp tomorrow
[12:01] <tdr112> they have a great line up
[12:02] <tdr112> it has turned into a very maker event
[12:02] <czajkowski> yay
[12:06] <airurando> czajkowski: hi there