| jono | hey | 00:12 |
|---|---|---|
| jono | is anyone running saucy right now? is it broadly working? | 00:12 |
| cjwatson | jono: wfm | 01:04 |
| jono | thanks cjwatson | 01:04 |
| cjwatson | jono: when I upgraded on Monday or so I had to logout/login before I could control networking again; I *think* pitti fixed that but not sure | 01:04 |
| jono | thanks, cjwatson, I think I will get it installed here | 01:05 |
| cjwatson | not in a departure lounge then? | 01:06 |
| cjwatson | oh yeah, you're local | 01:07 |
| cjwatson | duh | 01:07 |
| cjwatson | I swear I get stupider on the wrong side of the pond | 01:07 |
| jono | cjwatson, heh, yep, I am sat in a coffee shop | 01:08 |
| jono | have a reasonably free weekend until the family return tomorrow night | 01:08 |
| jono | so I am currently using this as an opportunity to learn about QML some more | 01:08 |
| jono | and likely upgrade to Saucy | 01:08 |
| cjwatson | looks like openssh does still need some work to handle logind correctly | 01:12 |
| cjwatson | not that that has any effect on most saucy users | 01:12 |
| cjwatson | maybe attempting to fix that should be my plane project | 01:13 |
| hulu | where the ubuntu livecd's casper create default user | 03:56 |
| hulu | who can help me | 03:56 |
| cyphermox | hulu: what do you want to know | 04:41 |
| hulu | cyphermox: i want to change the home directory of the default user of livecd | 04:43 |
| hulu | cyphermox: can you help me? | 04:44 |
| cyphermox | well, the home directory should match the user name used | 04:45 |
| cyphermox | if that's not what you want then you probably want to modify scripts/casper-bottom/25adduser to some degree. | 04:45 |
| cyphermox | I'm not sure where the username itself is defined | 04:46 |
| hulu | cyphermox: i want to change the ubuntu's .bashrc | 04:46 |
| cyphermox | ok | 04:48 |
| cyphermox | I'd probably just add a script to modify the file | 04:49 |
| cyphermox | somewhere after 25adduser | 04:49 |
| cyphermox | hulu: in any case, you can look at http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/casper/saucy/view/head for how all this is setup -- the scripts in the scripts directory are executed to create the user and set things up | 04:50 |
| cyphermox | the user is defined in casper.conf in the root directory | 04:51 |
| hulu | cyphermox: i want to change the /etc/skel,but the livecd don't create default user with /etc/skel | 04:55 |
| cyphermox | hmm, I don't know | 04:55 |
| cyphermox | I would have thought it come from /etc/skel, yes. | 04:56 |
| cyphermox | perhaps there is another script in casper that does that | 04:56 |
| hulu | cyphermox: i can't find the right place | 05:03 |
| cyphermox | hulu: I don't know how to help you more, I don't know how that file gets written if it's not via skel. | 05:03 |
| hulu | cyphermox: thx | 05:04 |
| cyphermox | hulu: that said, like I wrote above, I'd possibly just write a new script in the script folder that edits .bashrc via sed or something | 05:04 |
| cyphermox | or just blindly append to it | 05:04 |
| hulu | cyphermox: the livecd create default user with out /etc/skel | 05:04 |
| cyphermox | I'm not sure what you want to do with .bashrc, but it's possibly the wrong method too | 05:05 |
| hulu | cyphermox: i change the .bashrc,and place the changed file in /etc/skel,but the livecd create the default user without /etc/skel | 05:07 |
| cyphermox | sure | 05:08 |
| cyphermox | but you can overwrite the file in the user's home directory after it's written | 05:08 |
| hulu | cyphermox: what's you means? | 05:09 |
| cyphermox | well, somewhere after the user is created, you can write another .bashrc in /home/$USERNAME to do what you want, no? | 05:10 |
| === jono is now known as Guest55286 | ||
| hulu | cyphermox: i want to change the .bashrc before user create | 05:12 |
| cyphermox | hmm okay | 05:13 |
| cyphermox | sorry, I don't know | 05:13 |
| cyphermox | I'm going to have to logoff now, need to catch a plane | 05:14 |
| hulu | bye | 05:15 |
| infinity | LoganCloud: Could you please refrain from doing forced sync over packages that need merging? | 05:16 |
| scarecrow_ | Where can I find more information about ubuntu touch, TV and phone? | 06:21 |
| === a16g_ is now known as ypwong | ||
| sladen | congratulations on the release! | 08:32 |
| === G4MBY is now known as PaulW2U | ||
| === mnepton is now known as mneptok | ||
| === hrww is now known as hrw | ||
| === Lutin is now known as Guest30323 | ||
| === Pici` is now known as Pici | ||
| === jrib is now known as Guest31537 | ||
| === Tm_T is now known as Guest1531 | ||
| === ryanakca is now known as Guest91110 | ||
| === Guest31537 is now known as jrib | ||
| Riddell | is merges.ubuntu.com working for saucy? | 12:09 |
| === Pendulum_ is now known as Pendulum | ||
| ScottK | Riddell: yes. | 12:57 |
| dakotawulfy | hi | 14:02 |
| infinity | Hrm, why am I completely unshocked that a package called "mutextrace" hung several buildds? | 15:27 |
| ion | :-D | 15:44 |
| penguin42 | haha | 15:45 |
| === ivoks_ is now known as ivoks | ||
| === Guest1531 is now known as Tm_T | ||
| === cnd` is now known as cnd | ||
| === bdrung_ is now known as bdrung | ||
| === Ursinha-afk is now known as Ursinha | ||
| === trinikrono1 is now known as ubuntu-tt | ||
| weasel | heya. | 20:07 |
| weasel | is there some kind of lucid-backports repository that would have a reasonably recent debhelper I could use for building backports? | 20:08 |
| tumbleweed | there is lucid-backports, but Ubuntu backports policy would make backporting something like debhelper require a crazy amount of testing. I see it has been done in the past, though. ScottK? | 20:11 |
| rbasak | Backporting debhelper would certainly make backporting easier. Most of the time I've backported something (generally not to any official repo though) the only task was to wind back compat. | 20:12 |
| elmo | weasel: I have a 8.0.0ubuntu2~0.IS.10.04 for lucid, if that's any help, ISTR backporting anything newer to lucid got hard | 20:13 |
| rbasak | And debhelper is good at retaining backwards compatibility | 20:13 |
| maxb | weasel: The key questions really are 1) backporting what? 2) how new a debhelper do you need? and 3) backporting for publication where? | 20:13 |
| weasel | elmo: that's about the same level that squeeze has. that should suffice | 20:13 |
| maxb | It's often convenient to backport a version of debhelper into backport PPAs, which requires varying degrees of care depending on what packages it is going to be used fo | 20:14 |
| elmo | weasel: k, one sec, I'll dump it on people.canonical.com | 20:14 |
| maxb | *for | 20:14 |
| weasel | maxb: building my tor binaries for deb.tpo. I just modernized the packaging of the source package to use a new style dh debian/rules, and that requires reasonably recent debhelper. | 20:14 |
| maxb | tpo? | 20:14 |
| weasel | torproject.org | 20:14 |
| Laney | I reckon we could/should work out a way of backporting debhelper. | 20:15 |
| maxb | I have a lucid backport of 8.1.2 here: https://launchpad.net/~mercurial-ppa/+archive/builddeps/+packages | 20:15 |
| maxb | Let me review the diff and remind myself what I had to change | 20:15 |
| Laney | testing all of the rdeps would be a joke, but it's hardly likely to be necessary given what it is | 20:15 |
| weasel | so everybody seems to make their own? | 20:15 |
| Laney | apparently so | 20:16 |
| rbasak | How about a new debhelper9 binary package? THen you'd only have to tweak Build-Depends for a backport. It won't matter if it conflicts with debhelper, right? | 20:16 |
| weasel | seems an awful waste. <cue sweeney todd> | 20:16 |
| elmo | weasel: http://people.canonical.com/~james/debhelper/ | 20:16 |
| Laney | let me just mail the backporters and see if we can do it properly | 20:17 |
| weasel | thanks. I guess I can put that in a repo somewhere and teach schroot to add that to sources.list | 20:17 |
| maxb | https://code.launchpad.net/~bzr/ubuntu/lucid/debhelper/builddeps-ppa <-- looks like 8.1.2 just built fine with no changes on lucid | 20:17 |
| weasel | elmo: while I have you around, did you see my question on #d-a? | 20:18 |
| maxb | I think everyone tends to make their own because it's relatively easy to validate it's fine for any given single backporting project, but amazingly hard to have one true backport | 20:18 |
| maxb | At least you're only going back as far as lucid | 20:20 |
| maxb | Backporting debhelper 7.3 to hardy was "interesting" :-) | 20:20 |
| weasel | I dropped hardy support not too long ago :) | 20:22 |
| weasel | Date: Tue Apr 9 14:17:18 2013 +0000 | 20:22 |
| weasel | We no longer build hardy | 20:22 |
| Laney | <20130505202234.GH3149@iota> | 20:23 |
| maxb | Yes, really no point these days. It was nearly two years ago when I made that backport | 20:23 |
| ScottK | tumbleweed: We backported debhelper 7 to hardy-backports. Debhelper is a bit different since it's only used at build time. Backports of it are relatively safe since anything you're backporting had to build with the newer debhelper in the series you're backporting from. | 21:48 |
| tumbleweed | mind you, we'd need to solve backports build-depending on backports, first | 21:51 |
| Laney | for >= natty, yes | 21:52 |
| tumbleweed | oh, was that not an issue for lucid? np then | 21:52 |
| ScottK | Yep | 21:53 |
| Marlinc | Any mailing list moderators online? | 22:00 |
| Marlinc | Never mind it has been accepted already | 22:02 |
| === ricmm_ is now known as ricmm | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!