/srv/irclogs.ubuntu.com/2011/12/14/#ubuntu-release.txt

=== bladernr_afk is now known as bladernr_
CareBear\Hi all! I'm upstream maintainer of libusb, and debian have just packaged one of our upstream release candidates, which will be superseded by the actual release which has significant changes. What should I do to ensure at least that 12.04 does not ship with the rc3, but with the full release?10:31
cjwatsonCareBear\: get the full release into Debian testing before Jan 12? :-)10:37
cjwatsonactually Jan 910:38
* cjwatson reads the schedule more closely10:38
cjwatsonCareBear\: you could file an artificial bug on libusb in Ubuntu which we mark as a blocker, perhaps10:39
cjwatson(target to precise, milestone ubuntu-12.04-beta-1, tag rls-mgr-p-tracking)10:40
Laneywhy is it the monday? The 12th would better cover the new-year-holiday uploads10:41
cjwatsonI think because that's the Monday of the platform rally10:42
cjwatson(personally I don't care)10:42
Laneynot really a big deal I guess10:43
CareBear\cjwatson : thanks for confirm! I saw the 12 Jan date but I wasn't sure about the details10:50
CareBear\cjwatson : by when would that bug have to be filed?10:51
CareBear\I'm thinking: I will try to get into debian testing before Jan 9 (I hope before holidays) and if that fails, maybe I can file bug then?10:51
CareBear\and only if that fails, even10:52
cjwatsonCareBear\: sure, that would be fine, just let us know here10:52
CareBear\will do - thanks for help!10:52
cjwatsonJan 9 is just the point when we stop auto-importing; the resistance increases as time goes on, but through January at least it should be basically a rubber stamp10:53
CareBear\ok!10:53
CareBear\how often does the auto-import run?10:55
cjwatsondaily, ish10:55
cjwatson(it's only semi-automatic, I run a script by hand)10:55
cjwatsonsometimes forget at the weekends10:56
CareBear\<310:58
CareBear\I see the debian package is currently only in unstable10:58
CareBear\I will talk to them about that10:59
cjwatsoner11:00
cjwatson libusb | 2:0.1.12-19 | wheezy  | source11:00
cjwatson libusb | 2:0.1.12-19 | sid     | source11:00
cjwatsonhas the source package name changed or something?11:00
cjwatsonoh, libusb-1.011:01
cjwatsonyou don't need to talk to them, it's as expected; there's a 10-day aging period before things land in testing11:01
cjwatsonhttp://paste.ubuntu.com/769916/11:01
* ogra_ grumbles about packages that havent been built since maverick and now fail on armhf 11:01
CareBear\cjwatson : yes - I emailed him already11:06
=== bladernr_ is now known as bladernr_afk
=== doko_ is now known as doko
stgraberskaet: thanks to cjwatson we now have everything that's built daily showing up on the tracker (including Wubi, since this morning). Upgrade results are also appearing for flavours with most of them upgrading fine, with the exception of xubuntu.15:14
skaetthanks cjwatson & stgraber!  :D  great to have all the pieces visible!15:17
stgrabercasper change affecting all flavours: The new casper will now use edubuntu/kubuntu/lubuntu/xubuntu/... as the hostname and username in the live environment. A quick check didn't show anything blowing up but some per-flavour scripts may fail.21:16
stgraberso if you see something like that, please poke me and I'll be happy to fix it (I checked Edubuntu and Ubuntu with a custom build here, will test more after we have our first dailies)21:17
cjwatsonscripts/plugininstall.py:1530:        casper_user = 'ubuntu'21:19
cjwatsonstgraber: ^- in ubiquity21:20
stgrabercjwatson: Replacing by pwd.getpwuid(999).pw_name should work21:24
cjwatsonI'd suggest retaining the hardcoded username as a fallback21:25
cjwatsonor maybe parsing casper.conf?  ubiquity has a helper for that somewhere21:25
stgraberyep, it's a ubiquity.casper but that won't really help as the uid isn't stored in casper.conf21:28
stgraberAFAICS 999 is pushed into debconf for a very short while at boot time (to create the user) and then at least in another place to grep for the username21:28
cjwatsonthe username could be, though21:29
cjwatsonwe don't actually need the uid directly21:29
cjwatsononly as a possible indirect way to get the username21:29
stgraberhmm, right, so having my code actually change /etc/casper.conf in the target with the username and hostname?21:30
cjwatsonOr derive it in the same way in ubiquity21:30
cjwatsonAlthough clone-and-hack probably isn't ideal21:30
cjwatsonHave you considered setting the username at the live-build stage instead?21:31
cjwatsonIt knows what flavour it's building, and so casper's initramfs hook could work it out and plug that statically into casper.conf21:31
stgraberoh, indeed we could just generate casper.conf with the right value in live-build21:32
stgraberthen my casper change won't be needed at all and we can use ubiquity.casper to get the username21:33
cjwatsonSounds good21:33
stgrabercjwatson: so I'm currently looking at generating /etc/casper.conf from scripts/build/lb_chroot_hacks in live-build, not quite sure what variable contains the product name though21:53
cjwatson$PROJECT I think21:53
cjwatsonIt'll have to be in livecd-rootfs if you're keying off $PROJECT though21:53
cjwatson(livecd-rootfs installs some live-build hooks; it's a bit twisty)21:54
cjwatsonif this is too complex then don't worry about it for now, file a bug and we'll clean things up later?)21:54
stgraberlooks like $PROJECT isn't exactly what we want as it can be things like ubuntu-dvd (or edubuntu-dvd) which I'm pretty sure we don't want to use as username21:57
cjwatsonah yes21:58
cjwatson(bah.)21:58
stgrabercjwatson: I could apply http://paste.ubuntu.com/770579/ to ubiquity to avoid exploding when the ubuntu user doesn't exist and file a bug against something (what exactly? :)) to move the magic from casper to a script generating casper.conf instead21:59
cjwatson(a) yes, that looks fine (b) livecd-rootfs22:00
cjwatson(it might get reassigned but that's the starting point)22:00
stgraberok, doing that then22:00

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