#ubuntu-release 2010-04-01 <pitti> so I did some NBS and component mismatches fixes, which should clean some i386 bits on http://people.canonical.com/~ubuntu-archive/testing/lucid_probs.html <pitti> but for this to be really useful I guess we have to wait a day or two for the buildds to catch up <pitti> (which have been used for some 16 hours for security and openjdk builds) <ScottK> Not to mention a huge stack of private builds overnight too. <nigelb> ok, I got this ack on wednesday from release team, since today we're in beta freeze, do I need another ack? <nigelb> I subscribed sponsors, no one bothered I guess <ScottK> nigelb: No, just normal sponsorship. <nigelb> ScottK, so that ack would also hold good for beta freeze, right? <cjwatson> beta freeze just means that everything gets manually reviewed before it hits the archive <cjwatson> after beta-2 release, we go back to feature freeze status for a while, so feature freeze approvals still hold good - if it's not considered suitable for beta-2 by the reviewer, we just hold it in the queue until the beta's out <nigelb> ok, thanks :) <ttx> cjwatson: Do you formally review all uploads during freeze, or expect to be pinged for things that need to go through ? I was wondering if we should avoid uploading what is not beta2-critical (because reviewing the queue means more work to you) <ttx> the announcement is not clear if we should "refrain from uploading" like during the softfreezes <cjwatson> if there's stuff that *must not* go into beta-2, please don't upload it <cjwatson> otherwise, it's probably best to upload anyway, but if there's something you explicitly need then it's a good idea to ask <ttx> cjwatson: ok <Riddell> I wonder where today's kubuntu daily CDs got lost <cjwatson> lost? <Riddell> nothing at http://cdimage.ubuntu.com/kubuntu/daily/20100401/ build logs seem fine <cjwatson> Missing debootstrap-required libdb4.7 <cjwatson> CD1 missing some packages needed by debootstrap <cjwatson> make: *** [/srv/cdimage.ubuntu.com/scratch/kubuntu/daily/tmp/lucid-amd64/packages-stamp] Error 1 <cjwatson> ERROR WHILE BUILDING OFFICIAL IMAGES !! <cjwatson> archive error, I'll fix it <Riddell> ah, it helps if I look at the daily build log not the daily live log <lamont> rolling brownout of buildds for a new lp-buildd rollout, just fyi <pitti> slangasek: oh, we haven't talked about it last Friday? will we move the release team meeting to Tuesday or somethign such? (Good Friday/Easter Monday holidays) <pitti> or just skip it? <slangasek> pitti: oh, I keep forgetting that Europe gets Good Friday off <pitti> slangasek: oh, the US doesn't? <slangasek> I don't think we should try to do one on Tuesday; we'll have our hands full with the beta itself at that point <pitti> *nod* <slangasek> no, we don't <slangasek> we get Easter off ;P <pitti> Monday? <ScottK> pitti: Schools often get it off, but not work. <ScottK> No, Sunday. <slangasek> pitti: no, Easter Sunday :) <pitti> how .. generous :) <pitti> slangasek: anyway, is it okay if I update our release status page to the current status quo, and ask Ken or Rick to join the meeting as a desktop team delegate? <pitti> the release status page is really what takes most of the work/conveys the most interesting information anyway <ttx> slangasek: fwiw, the french work on Good Friday. <slangasek> pitti: sure <slangasek> cjwatson: I can haz queue bot? <cjwatson> you can haz <slangasek> kthx! <ev> If someone could let usb-creator through, I'd appreciate it. According to rgreening, it fixes a critical bug in the kde frontend. <slangasek> ev: looking <ttx> slangasek: the dhcp3 thing there is mine, would be good to have in the milestone to catch any corner case I didn't think of, but it's hardly critical or needed for beta2. * ttx calls it a day <slangasek> ev: this breaks string freeze? <ev> erm, yeah, ouch <ev> please reject, fixing <slangasek> ok <slangasek> that might be alright to let in immediately post-beta, if coordinated with translators; the new string is short and easy <slangasek> and unlikely to appear in screenshots <ev> reuploaded <pitti> liblauncher-0.1 kills the previous changelog, I pinged didrocks to fix and reupload <pitti> (actual code change is obvious one-line patch) <slangasek> ev: <cough> this upload misses the functional changes to the kde frontend <pitti> mvo: so, I can't make too much sense of the aptdaemon upload, and there's no associated bug <ev> arrrr <pitti> mvo: what does that do? and how much was it tested? <ev> this is what I get for rushing <ev> slangasek: okay, uploaded. Sorry for the hassle. I've got to run to catch a train though. If it's broken this time, it's a release note, I guess. <slangasek> ev: ok, g'night :) <ev> slangasek: cheers <ScottK> slangasek: ^^^ clamav update catches (minor) security fixes from clamav 0.96 final. I'd like those in for the beta, but am waiting on uploading 0.96 final so I can coordinate with Debian. <mvo> pitti: sorry, its for the ubuntuone-music-store <mvo> pitti: and it makes it use less authentication dialogs <mvo> pitti: currently each action (add-repo, update-cache, install-pkg) is a policykit action that needs confirmation <mvo> pitti: with the patch add-repo implicitely grants update-cache and install-pkg so that the music store needs to prompt only once <mvo> pitti: if you need a bugreport I can ask aquarius to write one <ScottK> queue bot gone mad. <ScottK> Looking at the packages in Main without a package set, it seems like there's a need to adjust the promotion process to also add to a package set. <slangasek> hmm, no doubt <ScottK> Is UNR using chromium-browser? It's in Universe and not part of a package set, but I thought they were. <cjwatson> promotion process> yes, there is a problem at the moment that the two processes aren't unified <cjwatson> this is a real pain but I haven't had time to sit down and fix it <cjwatson> package set addition relies on me periodically processing the output of a script :-/ <doko_> please consider accepting python2.6 (only affecting the python2.6-dbg package and helping apport) <cjwatson> grub-installer is one half of the server splash screen bug; the other half is a debian-cd change, which I can do easily but don't want to do before grub-installer's in * cjwatson -> bed #ubuntu-release 2010-04-02 * ScottK returns with more Scotch. <ScottK> More Scotch == More NBS gets done. <ScottK> Urgh. Samba4 got no updates this cycle. Do we want the 9 month old snapshot we have, the 7 month old snapshot from Unstable, or the 4 month old snapshot from December? <ScottK> Need to rebuild due to talloc transition anyway. <ScottK> Correction, the Experimental snapshot is two months old <ScottK> I'll leave all three building when I go to bed and see what survives. <ScottK> Looks like the answer may be "the one that builds". Two of the three didn't make it through configure. <ScottK> OK, 0 for 3 and I see it's on the supportable binaries removal list. Will see what I can do with it tomorrow. <asac> ubufox_0.9~rc1-0ubuntu1_source.changes: done. <asac> Successfully uploaded packages. <asac> ok ... <asac> slangasek: we wont be able to attend todays meeting ... holiday + travelling <asac> slangasek: i will send a mail with our status replying to the meeting reminder <asac> slangasek: also will include the stuff we wanted to discuss on omap ... <asac> i will be back on Wed <slangasek> asac: omap> ok, thanks - have a good holiday! <ScottK> slangasek: I believe I have a plan: downgrade ldb to 1:0.9.6~git20090912-1, upgrade samba4 to 4.0.0~alpha8+git20090912-1 (from Unstable), then rebuild openchange and sssd. I've tried these locally. <ScottK> Can haz FFe? <ScottK> (please no paperwork, I don't think I could stand making a sensible bug of it) <ScottK> 1:0.9.10~git20091212+really0.9.6~git20090912-0ubuntu1 <slangasek> ScottK: how are you handling the downgrade? +really.git20090912-1? <ScottK> Except ld is getting confused now for some reason. <slangasek> howso? <ScottK> err dpkg-shlibdeps I mean <ScottK> https://launchpad.net/~kitterman/+archive/ppa/+build/1623812/+files/buildlog_ubuntu-lucid-i386.ldb_1:0.9.10~git20091212+really0.9.6~git20090912-0ubuntu1~ppa1_FAILEDTOBUILD.txt.gz <ScottK> I'm trying another local build of the unmodified package to make sure it's related to the rename <ScottK> Should know in ~5 minutes <ScottK> Yeah, builds fine when not renamed <ScottK> Foundi t. <ScottK> it. <slangasek> \o/ <slangasek> ScottK: FFe granted, yes <ScottK> Thanks. <ScottK> On it's way. <doko__> hmm, who did give back schroot on armel? did give it back just 1h ago ... <slangasek> not me * ScottK neither <ScottK> Any ideas what samba4 would be in the Xubuntu package set? <slangasek> sounds like a bug to me * ScottK wonders if the bug gets filed against cjwatson? <ScottK> I was wrong about saving a binary New. The newer samba4 snapshot has new binary packages. * ScottK is off for a while. <slangasek> ScottK: the kdebase-workspace repo has an unrelated change to the default homepage; are you ok with that going in w/ the plymouth fix, or should I revert temporarily? <slangasek> ScottK: I see samba4 in the queue, but not ldb? <ScottK> slangasek: I went ahead and pushed ldb through since Universe isn't frozen. <slangasek> ah, ok <ScottK> slangasek: I'm fine with the homepage change (it's been discussed in #kubuntu-devel) <ScottK> Pushed samba4 too. <ScottK> I'm off (really this time). I 'll at kdebase-workspace when I get back. <slangasek> ok - should finally reach the queue in 10min or so #ubuntu-release 2010-04-03 <ScottK> slangasek: Accepted (workspace). Thank you. <slangasek> ScottK: yay \o/ <ScottK> samba4 is working out too. It goes on the binary New stack for Monday's archive admin .... <slangasek> I'll hopefully get to that yet tonight <ScottK> apt-cache unmet|grep -c Depends <ScottK> 205 <ScottK> Some work there too for the next few weeks. * slangasek nods <sistpoty> did the binary package removal thingy happen already? <slangasek> sistpoty: I was trying to get debtags-edit sorted out first, and it's being stubborn <ScottK> FYI, since the Launchpad rollout yesterday, packages are not automatically coming off of depwait. They need a manual push. <wgrant> s/yesterday/Wednesday/ <slangasek> ScottK: has that bug been reported? <wgrant> Yes, a CP is pending. <slangasek> oh, wgrant knows - same thing :-P <ScottK> Yep <slangasek> that explains the strangeness of me having to nudge packages along <wgrant> https://bugs.edge.launchpad.net/soyuz/+bug/553068 <ubottu> Ubuntu bug 553068 in soyuz "buildd-retry-depwait.py crashing" [High,In progress] <sistpoty> ok, thanks, I guess 230 unmet deps isn't too good then :/ <slangasek> how many go away when we remove the unbuildable binaries? <ScottK> Not sure if that makes it more or less. We'll see. <slangasek> right, so lucas has reported a FTBFS bug against debtags-edit in Debian too <ScottK> slangasek: Please try and document what you're doing so when I suggest we do this every cycle at UDS, you won't have to cringe and wish you had. <slangasek> and the reason it build-depends on g++-4.2 is because of an Ubuntu delta; the bug was fixed differently in Debian, and now there's a fresh FTBFS <slangasek> ScottK: the email included pointers to and/or copies of all the scripts used :) <slangasek> I documented it so I wouldn't have to remember how to do it a week later, let alone a cycle ;) <ScottK> ;-) <slangasek> right, so, debtags-edit is orphaned in Debian; gonna do a QA upload and fakesync <sistpoty> is ries already back up? <slangasek> yes <sistpoty> oh, nice, thanks! <slangasek> but backlogged so badly that it's not feasible to wait until I can do a real sync <wgrant> Yay, my inbox might stop filling up. <ScottK> slangasek: Would you please look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566270 and give me a preference between putting the offending package back or removing the rdpends (which are currently uninstallable)? <ubottu> Debian bug 566270 in ftp.debian.org "RM: libclass-dbi-loader-relationship-perl/unstable -- RoQA; License problems" [Normal,Open] <ScottK> Odd it's open, since it was removed from Unstable. <ScottK> and StevenK, of course, chopped it right out of Ubuntu. <ScottK> Based on the comment from the original author in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563519 I'd be inclined to put it back. <ubottu> Debian bug 563519 in libclass-dbi-loader-relationship-perl "libclass-dbi-loader-relationship-perl: missing copyright and license" [Serious,Fixed] <slangasek> ScottK: oh, geez; yes, please put it back <ScottK> slangasek: It's still in Testing, can you sync it from there. <slangasek> "can't independently verify the license in debian/copyright by looking at the upstream sources" - not a bug <slangasek> will I be able to sync it, or will I get a "version previously seen" from LP? <ScottK> You will. <ScottK> (get the previously seen) <ScottK> I'll upload it. <slangasek> ok <ScottK> Would you remove it from the sync blacklist please. <wgrant> I really should fix copy-package.py to let you revive binaries. <wgrant> It's perfectly possible for other archives through the web UI. Just not through the console for the primary archive. <slangasek> ScottK: it's not in the sync blacklist (removals generally don't end up there) - did you want it added /to/ the blacklist (to prevent it from showing up on the removal list)? <slangasek> taking a smidge longer than expected to fix up debtags-edit, because I'm fixing up the Vcs-* settings while I'm uploading - given that the package is orphaned and I can't commit to the target repo <ScottK> Hmmm. Probably should be added. <slangasek> done <ScottK> Uploaded. <sistpoty> ok, unless I made another silly mistake as with mclibs, libgfortran2 -> libgfortran3 should be done. <slangasek> \o/ <ScottK> To balance the karma, I found another package that needs removing. <ScottK> Found another premature removal, but fortunately it has a new version, so I just filed a sync bug. <ScottK> Good night. <slangasek> 'night! <ScottK> slangasek: Could we perhaps have plymouth-theme-ubuntu-logo seeded somewhere that all derivatives don't end up with it seeded? #ubuntu-release 2010-04-04 <slangasek> ScottK: yes, though I think we should make sure all the flavor theme packages depend on plymouth-label before switching <ScottK> slangasek: How about just seeding plymouth-label then, not the entire Ubuntu theme? <slangasek> the target is to not need to seed plymouth-label at all and only pull it in as a dep; I'd rather just get all the theme packages fixed so we don't have to change it twice <cjwatson> slangasek: I want to move plymouth-theme-ubuntu-logo from standard to desktop-common too to avoid excessive pollution of Priority: standard; I switched the seeds over, but I think all the -metas that use desktop-common will need uploads ... <cjwatson> I figure servers won't want it anyway <cjwatson> oh, err, does this conflict with what ScottK said above? <cjwatson> actually no, it supports what ScottK said :-) <cjwatson> ok, so I won't upload *-meta until the themes have been switched <cjwatson> I'm away Sun/Mon anyway <ScottK> slangasek: Are you tracking which are updated and which aren't? Kubuntu is fixed. <slangasek> ScottK: I'll look this weekend and make sure it's sorted before Monday <ScottK> Great. <ScottK> I need to do a kubuntu-meta upload, but not before it's fixed so that doesn't get dragged in. <slangasek> ScottK: the last workitem for foundations-lucid-supportable-binaries is 'update SRU policy to ensure it's clear FTBFS fixes for missing binaries are SRU candidates', but it already seems clear to me - do you think changes are still needed here? <ScottK> slangasek: If you're happy. I'm happy. <ScottK> There was some discussion about it as UDS, but we didn't review it in detail. <ScottK> I think particularly since you said they were SRU candidates in your u-d-a mail, it should be fine. <slangasek> okie <ScottK> It's interesting how fast the vnc FTBFS got fixed once it was removed.... <slangasek> that does tend to be the way <ScottK> BTW, ldb -> samba4 -> openchange -> evolution-mapi is all done. * slangasek cheers <doko_> slangasek: I'd like to upload a gcc-snapshot/gcc-4.5 build (supposed to build on armel). it will block the community ports for a while, but the queues are empty <slangasek> doko_: go ahead and upload, though there may be a few more accepts in the meantime out of the stuff currently in the queue <ScottK> Interesting. I didn't realize Partner would build on the Ubuntu buildds. <wgrant> ScottK: That does seem pointless. <wgrant> But it's trivial for an admin to change. <ScottK> For sun-java6 it makes sense to do it that way. It just further blurs the line about is Partner part of Ubuntu. <wgrant> I heard rumours that Partner will be replaced with PPAs soon. <wgrant> As it should have been from the start... <wgrant> (technically they're not 'Ubuntu' buildds; they're just non-virtual) <ScottK> I heard that rumor too, but it may have been from you. <wgrant> Possibly. I heard it from a reasonable source last week. <slangasek> ^^ would be great if someone could review plymouth <ScottK> Is queuediff expected to be able to cope with v3 format source packages? <ScottK> BTW, a certain maintainer is unlikely to be pleased with your versioning. <slangasek> I did several other uploads with the same versioning and there was no screaming. I'm happy to use dch the way it's meant to work, and he's apparently happy to fix the version up by hand each time he uploads. <shrug> :) <ScottK> OK. <ScottK> For some reason, queuediff seems to be failing to remember to download plymouth_0.8.1-4ubuntu1.debian.tar.gz and things go downhill from there. <slangasek> :( <ScottK> slangasek: I'm not comfortable with accepting the plymouth upload, but I did fix queuediff to work with v3 source format. <wgrant> ScottK: I'm guessing that it would make everyone involved rather happy if LP did the diff itself? <ScottK> Not sure. Queuediff seems to work pretty well. <ScottK> Just interdiff doesn't work on v3 source. <ScottK> So you have to skip the shortcut of not downloading the orig.tar.gz . <ScottK> I guess it would depend on how much I trusted LP to really be diffing the correct files. <wgrant> Interestingly, LP does actually do the diff before the upload is accepted. <wgrant> It just doesn't display a link anywhere. <wgrant> LP uses debdiff. <ScottK> What gets diffed if there are two uploads of the same package in queue? <wgrant> It will diff against the latest primary archive version. <wgrant> Latest accepted, that is. * ScottK needs to get to sleep, but will think about it. <wgrant> Night. <ScottK> Good night. <cjwatson> slangasek: plymouth looks good to me; accepted <sistpoty> cjwatson, iulian, Riddell, pitti, nhandler, ScottK, slangasek: wrt. delegates, I've finally got confirmation from anyone and have drafted a mail about it: http://paste.ubuntu.com/409073/ <sistpoty> any comments, questions, objections? <ScottK> No server delegat then? <sistpoty> ScottK: thought you'd handle server? (no need to delegate then) <sistpoty> should I explicitely mention that kubuntu and server has members in the release team already, so isn't delegated? <ScottK> Sounds reasonable. <sistpoty> revised version: http://paste.ubuntu.com/409076/ <ScottK> sistpoty: Looks good. <sistpoty> ok, thanks <sistpoty> (I'll wait a little bit longer yet in case someone else has objections or additions before sending) <nhandler> sistpoty: What do you mean by "directory process"? Do you mean Ack+Upload? <sistpoty> nhandler: grant an exception. Do you think that's unclear? <sistpoty> (it's "directly process" btw, seems like I even spellt it correctly *g*) <nhandler> sistpoty: Yeah, it is a bit unclear, as they should be leaving a comment on those types of bugs as well to show they granted a FFe. /me can't type right after waking up <sistpoty> heh <sistpoty> ok, will try to improve the wording <sistpoty> http://paste.ubuntu.com/409086/ <sistpoty> nhandler: is that better? ^^ <nhandler> sistpoty: Is there a reason for the distinction between sync requests? Shouldn't a note saying an ack has been (not) granted be left on all bugs they process? <sistpoty> nhandler: good point, was thinking of FFe's granted on irc when I wrote explicitely about sync requests <sistpoty> next try: http://paste.ubuntu.com/409089/ <sistpoty> nhandler: ^^ <nhandler> Looks good <sistpoty> and yet one small fix: http://paste.ubuntu.com/409090/ (s/nonetheless/always/) <nhandler> :) <sistpoty> ok, mail sent to U-D-A, pending moderation. In case there's anything that should get improved, please delete it from moderation, make the changes and resend (as I'm most likely afk for the rest of the day), thanks! <ScottK> slangasek: ^^^ <slangasek> mail accepted #ubuntu-release 2010-04-05 <ScottK> slangasek: Would you please try an new ISO build for Kubuntu, port, live? It looks like the meta changes I did to try to fix the powerpc oversize didn't make it in time for today's run. <ScottK> port/ports <slangasek> ScottK: running <ScottK> slangasek: Thanks. <slangasek> ScottK: failed in <4min <slangasek> oh wait, that was ia64 <slangasek> nevermind * ScottK relaxes. <ScottK> AFAIK there are no Kubuntu IA64 users. There are powerpc users. <ScottK> slangasek: One thing I think I didn't think through on the supportable binaries spec was the impact of removing build depends. I hit one package yesterday that is now no longer buildable. <ScottK> Fortunately that one was fixed in Debian, but I think that class of packages needs to be identified. <slangasek> right <slangasek> that makes at least three now that we've hit <ScottK> Did you publish the final list of binaries removed? <slangasek> no, I'm afraid I didn't keep track of which removals succeeded vs. being superseded already by new versions <stgraber> I'll be uploading a new edubuntu-meta in a few minutes to match with the seed change I just uploaded. That should hopefully fix the build failures for Edubuntu DVD. <slangasek> ok <ScottK> OK, so I've asked lucas to do another rebuild and then I can diff that from the results of the last one. <ScottK> Sigh. 05-Apr-2010 18:35 701M <ScottK> Close. * ScottK rips more out. * ScottK heads out for a while. <ScottK-droid> slangasek: ace i386 hit New again, FYI. <slangasek> ack <ScottK> slangasek: If it wouldn't interfere with anything, could I please have another Kubuntu, Ports, Live ISO build? <slangasek> scheduled <ScottK> Thanks. <kees> can someone shove refpolicy through universe, please? <ScottK> Sure <ScottK> kees: Done. <kees> ScottK: thanks! <ScottK> No problem. #ubuntu-release 2010-04-06 <ogra> slangasek, arm images dont use OO.o, we need to make sure OO.o gets built on one of the new machines, the old ones segfault randomly <slangasek> which ones are the new ones? <ogra> slangasek, but that shouldnt hold up beta <ogra> ubuntu-netbook and ubuntu-server are the ones we test <ogra> netbook has the new weboffice stuff in the image, while its important that we have OO.o building and running for final it doesnt impact the milestones anymore <ScottK> It's still on the KNR armel images. <ogra> slangasek, oh, you mean the new builders ? (sorry, i'm very tired) lamont should be able to tell, i think gourd is one of the new ones <ogra> cushaw sounds new as well <slangasek> previous build was on buttercup - do you know if that's new or old? <ogra> not of the top of my head, lamont is really the safest person to ask here, he just set up a set of new builders <slangasek> lamont: ping * ogra is totally swamped in omap stuff since a while <ogra> slangasek, do you plan a d-i upload before beta ? (i saw you bumped the ABI for armel arches and the commit i did today for omap would be helpful for server images) <slangasek> server images? <ogra> we build netbook, servar and netinst images for all arm arches <lamont> ogra: new (bbg3): buttercup, cushaw, gourd <ogra> *server <slangasek> ogra: ^^ then OOo is FTBFS on the new armel buildds. <lamont> ogra: and to come: acorn crabapple satinash hubbard sycamore hawthorn <lamont> though one of those will be livecd builds <ogra> slangasek, given the kernel is only half way there (still waiting on amit here to do teh final fixes) i'd be fine to have at least a server image atm <ogra> lamont, can you give back OO.o to build on one of the old buildds to check if its probably an issue with the new setup ? <slangasek> ogra: building server images is an artifact of how the cronjobs are set up, no one has mentioned to me that we're supposed to support armel server images; why do you care if those are working? <lamont> ogra: with some sobbing, yes <slangasek> (I had no plans to upload d-i because I was unaware anyone cared - you can upload it, though) <ogra> slangasek, we dont *suuport* them per se :) they are just the easiest thing to get working to have something at all <ogra> slangasek, currentl kernel prob with omap is that HID is screwed, so live images are a no go on an arch that only has USB input <ogra> *current <slangasek> heh <lamont> ogra: so we know it'll fail on buttercup? <ogra> lamont, apparently <slangasek> lamont: yes <lamont> just for the record, this isn't trivial. <slangasek> what isn't? <lamont> forcing the m achine it lands on <slangasek> oh, giving back on an old one <ogra> well, its not urgent that we have oo.o for beta, but i think it seems to show a potential buildd prob <slangasek> I don't see the point in doing it <wgrant> lamont: I suppose you have to flip them all onto manual, tweak a build score, and flip one back onto auto? Ew. <ogra> well, probably something for next week anyway, given that all old machines are totally busy atm <lamont> wgrant: step 0: nuke the current build to get it back into failed <ogra> yeah, dont nuke gcc <lamont> which actually is just a matter of waiting for the build to get to that step <wgrant> True. <lamont> the easy part is landing it on an old machine - I have some of those that are trying to be retired <ogra> slangasek, when did you give it back last time ? <ogra> the log i checked today seems to have failed in a different place <ogra> (today like about 12-14h ago) <lamont> it does help to have a spare buildd in your back pocket. <lamont> huito is building it, but ogra... I'm thinking you really want it to fail there, too. <ogra> yeah, i really hope it does <slangasek> ogra: I think I last gave it back before that <ogra> hmm, k, then i might misremember, i cant remember seeing anything about localedata around the segfault line <ogra> slangasek, d-i is in the queue <slangasek> ok <lamont> at any rate, afk for a goodly while, I think * slangasek gets the isotracker a-movin' <ScottK> Ah my, he's not done. <ScottK> Ah/Oh <slangasek> who? <ScottK> slangasek: zul. This big slew of Universe uploads is all zul doing mysql rebuilds. <slangasek> ah <slangasek> why are mysql rebuilds needed, OOI? <slangasek> (I don't see anything on NBS) <ScottK> Maybe he's trying to get everything to 5.1. <ScottK> Not sure. <slangasek> mmk <slangasek> GrueMaster: FWIW, ARM candidate images for beta2 have started building, but with the addition of omap, I guess that'll take another 2 hours longer so won't be ready 'til morning <ScottK> If stuff isn't seeded, I'm just pushing Universe through. I view needing the push as a workaround to an LP limitation because the unseeded part of Universe isn't frozen. * slangasek nods <slangasek> speaking of which, is there a reason chromium-browser is still in the queue? Does somebody have that seeded somewhere? * wgrant points at the augmented queue, with package sets. <ScottK> I thought it was seeded on armel, but I wasnt' sure * slangasek chuckles <ScottK> wgrant: Very helpful. <ScottK> Unfortunately I've discovered as a result that package sets are manually maintained at the moment and not always in sync with the seeds. <wgrant> YAY <ScottK> That's a limitation of the current initial implementation. Not "the plan". <slangasek> ScottK: chromium-browser was investigated for armel this cycle, and in the end they stuck with firefox <wgrant> Ah, good. <ScottK> slangasek: OK. Thanks. I'll accept it then. <ScottK> slangasek: I left twm there because it's a pending MIR issue. I'm not sure Depends -> Suggests for menu is a great idea. <ScottK> I didn't get a chance to see what twm uses it for. <slangasek> twitch <slangasek> has someone opened an MIR bug, or is it just currently in components-mismatches? <ScottK> There's a MIR bug. It's referenced in debian/changelog <ScottK> The MIR is ~approved too. <ScottK> Read the bug and then double twitch. <slangasek> meh, I think the right answer is to b-d on metacity instead of twm <slangasek> promoting a wm just to have it for a java test suite seems absurd to me <ScottK> Thus the double twitch. <ScottK> slangasek: Are you going to write in the bug and reject it? <slangasek> ScottK: I've commented the bug, but I'm not ubuntu-mir <slangasek> so I'll wait for their decision before accepting/rejecting the package <ScottK> OK. <slangasek> in the meantime, AFK <GrueMaster> slangasek: What, you mean I can't start testing until after midnight? Aww. :P <ara> morning all! * slangasek waves <ara> hey slangasek <ttx> slangasek, ara: o/ <mvo> ttx: good morning, not sure you have noticed, I added the server-tasks upgrade test profile. karmic->lucid seems to have a conffile prompt in bind9, otherwise it looks good <ttx> mvo: no, haven't had a look yet. That sounds good, thanks. Do we have a bug about the bind9 thing or do you want me to look into it ? <mvo> ttx: I have not checked for bugs or details yet, I do a app-install-data update now, then I can check it out <slangasek> GrueMaster: arm netbook is up <slangasek> ara: should the UbuntuGlobalJam milestone be hidden on the tracker? <ara> slangasek, indeed, I'll do it <slangasek> thanks <pitti> slangasek: still okay to sync a new tzdata into lucid at this point, or shall I do it after beta-2? (just two simple DST rule updates, bug 550157) <ubottu> Launchpad bug 550157 in tzdata "DST time is cancelled in Tunisia - 2010h available" [High,In progress] https://launchpad.net/bugs/550157 <slangasek> pitti: if it's not urgent, please wait until after beta2 or until we have to reroll for something else <slangasek> http://qa.ubuntu.com/reports/ogasawara/weatherreport.html is a lot easier to read when it lists 0s instead of 1s <pitti> slangasek: not that urgent; time will be wrong in Tunesia and Pakistan, but it's certainly not worth a re-roll <pitti> yes, understood <slangasek> will be wrong immediately? <pitti> yes, the changes got effective two weeks ago in Tunis <slangasek> yuck :/ <pitti> oh, Pakistan only changes April 15, so that's still ok <pitti> slangasek: but we'll provide an updated tzdata in lucid, so on an installed system you can just upgrade <slangasek> yeah <pitti> slangasek: I'd only sync it if you were planning a re-roll anyway <slangasek> I guess the SRUs are more important for production <pitti> right, I'm doing them right now <pitti> +# > On Thursday (2010-03-25) it was announced that DST would start in <pitti> +# > Pakistan on 2010-04-01. <pitti> How the heck can governments do things like that?? * pitti stops grumbling and continues to fire SRUs <slangasek> they can do things like that because there's no physical law that ensures good sense in government :) <pitti> right, and instead we get bug comments "24 hours later, still not assigned... and importance "undecided".... Viva Ubuntu ! Pfffffff...... :-(" ... <pitti> slangasek: want me to process those SRUs myself? <slangasek> yeah, feel free <slangasek> comments> those are the kind of people I tell that they should be complaining to their government for being irresponsible <ttx> cjwatson: "splash" is still present on the beta2 candidate server install <ttx> pitti: sounds like an april 1st joke <pitti> ttx: sadly not; many countries do that unfortunately <ttx> slangasek: for some reasons, the samba-server task installs winbind, so the pam_winbind profile borkenage affects the resulting install -- I'm looking at where that comes from <slangasek> ttx: I would expect a samba server task to include winbind <slangasek> I'd rather focus on understanding the profile error, which I have yet to reproduce here despite having pam_winbind configured <ttx> slangasek: right <slangasek> I really need someone who's seeing this problem to post me their full /etc/pam.d/common-* for analysis <ttx> I can reproduce on a bare ISO+samba-server task install, cannot log in <ttx> I can provide that info <slangasek> including on console? <ttx> yes. <slangasek> ok <ttx> just a sec, booting single-user mode and packing that up for you <slangasek> thanks <ttx> the missing piece of the puzzle might be that pam_smbpass is also active <ttx> (or not) <slangasek> I've been running with both pam_winbind and pam_smbpass active for months <slangasek> no errors <slangasek> I've just stripped it down to unix+winbind; still no errors * ttx grumbles -- for some reason I can't login even with winbind disabled * ttx digs deeper <slangasek> ah :) <ttx> hmm, I must have forgotten the password I used in my ISO install (or mistyped it... twice??!), let me re-reproduce cleanly :) <ttx> or.. maybe the password was not set correctly at the end of the install on top of the borken stack. <ttx> ew, and the primary user is not added to sudoers group either <slangasek> check for a password hash in /etc/shadow? <slangasek> (if you haven't already clobbered it) <ttx> I clobbered it <ttx> but I'm reproducing on another box <slangasek> ok <slangasek> I was musing that this might be a possibility <slangasek> but that means the installer isn't letting the user know about failures setting the password? <ttx> I'll have a look at the install console and see if there is something showing, but yes, I'd suspect the installer wouldn't let you know about it * ttx reboots in single-user mode to get sufficient privileges to access that profiles tarball <slangasek> I expect better than that of the installer :) <ttx> took longer than expected, but here you go: <ttx> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/546874/comments/17 <ubottu> Ubuntu bug 546874 in samba "passwd - can't login, change password (pam_winbind pam-auth-update profile)" [High,Triaged] <ttx> I'm reproducing on an unclobbered new install to look at the state of the passwd file <ttx> slangasek: confirmed, no passwd hash entry on the regular user in /etc/shadow at the end of the install <slangasek> yay <ttx> also the installer logs show that it fails <ttx> chpasswd pam_winbind failure <ttx> WBC_ERR_WINBIND_NOT_AVAILABLE <ttx> warning: /usr/lib/finish-install.d/06user-setup returned error code 1 * slangasek nods <ttx> but that's apparently not a blocking error. <ttx> slangasek: so the "even on console" answer above might be biased: doing it "from ISO" like this will end up with no passwd set, so you obviously can't login even on console. <ttx> that doesn't mean the pam stack would prevent you from doing so, given that there is a good passwd entry set. * ttx checks on an already-installed system <slangasek> ttx: so the fix to winbind is pretty straightforward, I think <slangasek> 1) call pam-auth-update in winbind.postinst <ttx> (and prerm) <slangasek> 2) Password-Type: Primary instead of Password-Type: Additional in debian/winbind.pam-config <ttx> ah, so the auth stack was never wrong, just the password stack <ttx> with the ISo installs blurring the line <ttx> slangasek: if that's all it takes, I'll assign me and target to beta2, if that's ok with you <mvo> ttx: bug #556332 - bind9 is acting strange here, feedback welcome <ubottu> Launchpad bug 556332 in bind9 "leftover /etc/init.d/bind9.dpkg-dist on 9.10 -> 10.04" [Undecided,New] https://launchpad.net/bugs/556332 <mvo> ttx: not a showstopper or anything, but really odd IMO <ttx> mvo: I'll add it to the hit list <ttx> mvo: thanks <slangasek> ttx: sure, go ahead <slangasek> (still doesn't explain some people who are reporting *recent* problems being able to log in, but we can at least fix the installer case this way) <ttx> most people report passwd-changing issues. The ones with login problems are usually beta ISo testers <ttx> so that seems coherent <slangasek> re: the prerm, I've already committed the fix for that in Debian Samba svn; but it's bound up now with the question of whether Debian is doing 3.4 or 3.5 for squeeze, so you'll need to cherry-pick <ttx> ok <mvo> ttx: and bug #556343 <ubottu> Launchpad bug 556343 in bind9 "upgrade error on 8.04 -> 10.04 " [Undecided,New] https://launchpad.net/bugs/556343 <mvo> ttx: more important as it causes a real failure <slangasek> ttx: bug #546874's submitter claimed that logins were broken, only after an upgrade, and he installed from a desktop - I don't see any way that winbind would get pulled in immediately as part of a desktop install so the initial password setting should still be correct, and anyway we have his statement that it broke only after upgrade <ubottu> Launchpad bug 546874 in samba "passwd - can't login, change password (pam_winbind pam-auth-update profile)" [High,In progress] https://launchpad.net/bugs/546874 <slangasek> so there's some other bug here, still <ttx> ah, yes, got lost in duplicates. <ttx> slangasek: did you get some answer about removing the wine rdepends ? <cjwatson> ttx: still catching up from holiday - syncing and having a look, may take a while <ttx> cjwatson: ack <slangasek> ttx: no <slangasek> ttx: I also didn't file a bug about it; would you care to, or should I do so in the morning? <ttx> slangasek: I'll do it <cjwatson> that winbind failure in user-setup above might well cause some odd knock-on effects, despite not blocking <slangasek> python-pkg-resources> curses, one o-o-d package on all ISOs now <slangasek> cjwatson: it causes knock-on effects like a successful install w/o an authenticatable user, apparently... <cjwatson> yes, I can believe that. needs rather better error handling, but for now we need to fix the failure anyway ... <slangasek> yep <ttx> slangasek: here is the winbind fix ^ <ScottK> slangasek: Last week you removed libannodex, but left pyannodex. Would you please remove that too? * ScottK reports a bug. <cjwatson> ttx: is there a bug open for the server splash still not working? (if not, don't bother filing one, just want to check if I should be closing one) <ttx> cjwatson: no, I just commented on the existing one, wasn't sure which task I should reopen, if any <ttx> I was wondering if something wasn't just waiting for a respin to trigger <cjwatson> no, it's a bug <cjwatson> I'll reopen the existing bug, then <cjwatson> the "could not write bytes: broken pipe" bit is unrelated, but I think there's already a bug somewhere for that <cjwatson> parted: not needed for beta-2 <cjwatson> could somebody please review grub-installer? RC IMO, to fix ttx's problem above <ttx> yes, we definitely need the potentially-final server boot experience in beta2 for testing :) <cjwatson> it also needs another debian-cd change, which I have prepared and ready to go <ScottK> cjwatson: Looks good to me. Accepting. <ScottK> Done. <cjwatson> ScottK: thanks <ScottK> cjwatson: I know there isn't any documentation in the package to be affected, but is there online documentation about customization that needs updating for splash=false instead of nosplash? <cjwatson> ScottK: I wouldn't expect so - nosplash is very new, on the order of days <ScottK> OK. Thanks. <ScottK> "If your documentation is that bleeding edge, you need to be paying attention" <ttx> cjwatson: could you respin a Server ISO / beta2 candidate whenever that fix lands ? Also the samba in the queue (unbreaking the samba-server task) would be good to have in the next candidate. <cjwatson> planning to <cjwatson> would prefer somebody more domain-competent to review samba, though * ScottK is fixing quediff to work with .bz2 orig <ScottK> Done, so it can be used by whoever has the domain-competence to review it. <james_w> any thoughts on https://bugs.edge.launchpad.net/ubuntu/+source/xpdf/+bug/556483? <ubottu> Ubuntu bug 556483 in xpdf "Merge xpdf 3.02-2 from Debian Unstable" [Wishlist,New] <james_w> no new features, but rewritten packaging, would that require an exception? <ScottK> james_w: Generally yes. <Riddell> ev: thanks for fixing bug 556180 <ubottu> Launchpad bug 556180 in ubiquity "Buttons on ubiquity partition page doesn't work" [Undecided,Fix committed] https://launchpad.net/bugs/556180 <ev> sure thing <Riddell> ev: planning a ubiquity upload at some point? <ev> Riddell: yeah. I was hoping to get Ken's timezone map changes in, but as those will require an exception, I might as well do an upload now so that your fixes don't block on that. <Riddell> ev: changing the SVG requires a UI freeze exception? <ev> I had assumed so <Riddell> doesn't seem like a big enough change to need that, I doubt we have many screenshots of the map with India or Pakistan selected <ev> Russia as well, but noted <Riddell> Russia claims Kashmir? <cjwatson> some of Russia's timezones changed a bit recently <cjwatson> I agree, I think it's worth notifying the doc team but I don't think it needs freeze paperwork really <ev> okay cool, I'll take care of this first then <ScottK> Bug #556629 is potentially significant. <ubottu> Launchpad bug 556629 in update-manager "Upgrade fails due to no video driver - Intel removed during upgrade" [High,New] https://launchpad.net/bugs/556629 <ev> if anyone has some free cycles, I'd appreciate a review of bug 554570 and bug 554976 <ubottu> Launchpad bug 554570 in ubiquity "Freeze exception request: only show update installer link when an update is available." [Undecided,New] https://launchpad.net/bugs/554570 <ubottu> Launchpad bug 554976 in ubiquity-slideshow-ubuntu "UI freeze exception request: adjusting icons and CSS style" [Undecided,New] https://launchpad.net/bugs/554976 <ev> Riddell: ubiquity 2.2.15 is in the queue <Riddell> ev: accepted! <mvo> http://people.ubuntu.com/~mvo/automatic-upgrade-testing/current/ looks not that great currently (but server-tasks and lts-ubuntu should really only be WARN and not FAIL, the bugs are not that serious) <GrueMaster> Riddell: Does this mean there will be a respin for Ubiquity 2.2.15? <Riddell> GrueMaster: for Kubuntu yes, probably the rest too if we want to keep the Kashmir lobby happy <GrueMaster> sigh. I'm doing the ubuntu-armel testing. Takes a lot longer than desktop or netbook due to limited resources. <GrueMaster> And I hate having to recompile my bug lists. <Riddell> such is the world of ISO testing, slow and painful <Riddell> surely launchpad can handle bug lists <ttx> slangasek: please review the samba (winbind) fix whenever you have the time, and respin server ISo / refresh beta2 server candidate when it lands <ttx> slangasek: ping smoser when done so that he can generate EC2 cloud image candidates <Riddell> ttx: not sure if slangasek is around just now, maybe another release team member should help? <ttx> Riddell: iirc most of them declined to review the samba as not being in their domain, but yes, anyone can help :) <Riddell> ttx: I accepted samba <ttx> Riddell: ok, so when it lands, we could use a server ISo respin/ candidate refresh, the sooner the better <Riddell> disabled current images in tracker <Riddell> ev: we want new ubuntu desktop images I take it? I should disable those in tracker too? <slangasek> ttx, Riddell: samba> thanks <slangasek> ScottK: libannodex> yes, was going to file that bug myself prior to removal * cjwatson writes an interactive version of packageset-push in the hope that that will enable him to keep up with packageset changes a bit more effectively <charlie-tca> Are you going to respin xubuntu? <charlie-tca> 7q83+TKbzFN <slangasek> the ubiquity changes would also apply to xubuntu, but I wouldn't think it's critical <charlie-tca> okay <cjwatson> charlie-tca: might want to change that password :) <charlie-tca> yeah, good thing it is for testing, huh <slangasek> so bug #519541 keeps getting reported as a serious bug in all the xubuntu tests, but it has no assignee? <ubottu> Launchpad bug 519541 in abiword "Abiword 2.8.1 freezes with document lost when help is clicked or F1 is pressed" [Unknown,Confirmed] https://launchpad.net/bugs/519541 <charlie-tca> yup <charlie-tca> It completely freezes abiword, the Xubuntu default word processor. If the document is not already saved, it is lost <slangasek> yes, I understand it's a serious bug, that's not the question - the question is why no xubuntu dev has taken responsibility for it <charlie-tca> I don't know. I keep telling them about it, too. <slangasek> Riddell: what did kubuntu alternate need respun for? <Riddell> slangasek: I don't think it did, did I mark that in iso tracker? <Riddell> fixed <slangasek> ok, cheers <slangasek> I'm going to start the respins now <slangasek> assuming I'm not colliding with you :) <Riddell> go ahead <Riddell> although `ls cdimage/ftp/pool/main/u/ubiquity/*2.2.15*` is empty on antimony, I take it that's not what counts? <slangasek> GrueMaster: I don't think I'll respin armel netbook for the ubiquity change; I don't imagine there are a lot of ARM hardware vendors is Kashmir that are going to come after us for an inaccurate beta map <GrueMaster> cool <slangasek> Riddell: nope, antimony's mirror is updated /by/ the ISO job <slangasek> ev, cjwatson: any other installer issues on the horizon that look like they could be beta blockers? <slangasek> all respins done/posted except for DVD <cjwatson> slangasek: not that I've seen so far, but I've been feeling ill this evening so am not as on top of bugs as I'd like :-/ <slangasek> understood <slangasek> aside from the last kubuntu issues, the ISO tracker looks (deceptively?) calm <kees> ScottK: are you around to push selinux and refpolicy-ubuntu for me? * kees thanks mystery pusher <mdeslaur> lol <slangasek> lamont, elmo: old-releases.u.c requires a manual push, is that right? <slangasek> (I've dropped intrepid from releases.u.c, but I don't see it showing up on old-releases) #ubuntu-release 2010-04-07 <ScottK> kees: You're welcome. <ScottK> slangasek: If you have a moment to help me figure this out, I'd appreciate it... The second Kubuntu ports respin you did for me yesterday still had the packages that were removed from the seeds, but manifest shows the new kubuntu-desktop version. Any suggestions? <ScottK> http://cdimage.ubuntu.com/kubuntu/ports/daily-live/20100405.2/ <slangasek> task changes take 2 publishing cycles to propagate, did we respin too soon? <ScottK> slangasek: Probably. I forgot about that when I asked you to respin. <ScottK> If it wouldn't be a problem, could I have another respin? <slangasek> running <ScottK> Thanks <slangasek> kees: is there any periodic review done of the packages in 'supported' that were requested by IS / Launchpad, to confirm there's still an internal need for sec support? <kees> slangasek: just what's done at UDS time with elmo <ScottK> Wasn't that just the server seed that was reviewed? * ScottK recalls a session about that. <slangasek> there was a server review, yeah, which I don't think covers the python dev stuff <ScottK> No, it didn't. <ScottK> slangasek: Hooray! powerpc is not oversized anymore. Thanks. <slangasek> \o/ <kees> slangasek: is the publisher off? (security updates aren't getting into the archive...) <ScottK> kees: IIRC there isn't normally a publisher run this hour. Has it been going on for a while? <kees> ScottK: this hour (04:03) yes, but it seemed to miss the 03:03 run too. maybe I just have bad luck <ScottK> There are two hours it misses and with the DST changes I don't remember which two. <ScottK> I think it would have been last hour and this one, but I'm not sure. <kees> 2? hm, that's new <ScottK> Or it could be it's after midnight here, I got up early, and I'm not remembering very well. <ScottK> Eventually slangasek will set us straight. <slangasek> kees: there's one hour when the publisher doesn't run because contents generation runs in its place; then there's the hour after that, when the publisher doesn't run because the contents generation job still holds the lock <slangasek> (I don't think it ever finishes within the hour) <kees> slangasek: ah, heh, so 05:03 won't run either. meh <ara> morning :) <Riddell> hmm, /home/ubuntu-archive/public_html/germinate-output/kubuntu.lucid is over a week out of date <ara> Riddell, I am afraid that bug 556555 still happens :( <ubottu> Launchpad bug 556555 in ubiquity "oem-config loops indefinitely in Kubuntu OEM installations" [Undecided,New] https://launchpad.net/bugs/556555 <Riddell> ara: do you get a crash at the end of oem config ? <ara> Riddell, the first time it loops, no, the second time, yes <Riddell> ara: have you seen bug 557197 ? <ubottu> Launchpad bug 557197 in ubiquity "ubiquity does not change pages without moving mouse" [Undecided,New] https://launchpad.net/bugs/557197 <ara> Riddell, I haven't. I will try to reproduce it <cjwatson> ara: I'm in the process of investigating that <cjwatson> (556555) <ara> cjwatson, nice, thanks <cjwatson> may be for final rather than b2 though <ara> Riddell, I cannot reproduce 557197 <ara> cjwatson, I am glad to hear that ;-) <Riddell> ara: hmm, I hope I'm not just going mad then :) <ara> Riddell, ah, non-english, ok, let me try again <ara> Riddell, no, I cannot reproduce it either <Riddell> ara: hmm, so I am going mad <ara> Riddell, is there a bug about timezone selection being quite arbitrary? <Riddell> ara: what's arbitrary about it? <Riddell> it uses some geoip thingy to give you a local default if you have network <ara> Riddell, yes, but it does not work <ara> Riddell, in Ubuntu it places me correctly in Spain <ara> Riddell, in Kubuntu is either Argentina or sometimes Barbados <Riddell> hmm, are you routing your internet through random countries to avoid the MPAA? :) <ara> Riddell, hehehe <Riddell> ara: file a bug and assign to shtylman <ara> Riddell, ok, will do :-) <ara> Riddell, nice, found a new crash, filing it <Riddell> wibble <ev> ara: do note that there are two timezone setup bugs fixed with a new version of tzsetup in the queue. It may fix the bug you're seeing if you have something like "Could not understand timezone" and a bit of XML data in your install logs. <cjwatson> ara: bug 556555: looks to me like that bug *is* fixed, but you are now experiencing a new one with similar symptoms which needs fresh logs attached ... <ubottu> Launchpad bug 556555 in ubiquity "oem-config loops indefinitely in Kubuntu OEM installations" [Undecided,Confirmed] https://launchpad.net/bugs/556555 <ara> cjwatson, ok, will do <ara> cjwatson, new bug? or the same one? <ara> ev, ok, will have a look <cjwatson> strictly speaking that bug should be marked as a dup and a new one filed - but it probably doesn't matter that much, go ahead and reuse that bug since it's yours <ara> ev, yes, that's the bug. Thanks! <ara> Riddell, I was able to reproduce bug 557197 <ubottu> Launchpad bug 557197 in ubiquity "ubiquity does
{'channel': 'ubuntu-release', 'month': 4}