[00:00] directhex: right; except that now by touching gnome-sharp2, I've inadvertently added to the NBS list, which means it's also on my todo list :) [00:01] don't forget gnome-desktop-sharp2 too! [00:01] i have no idea why upstream split those [00:04] slangasek: iso coming down painfully slower than usual [00:05] any ideas why my usb mouse stopped working in jaunty after an update earlier this week? [00:06] usb mouse - no idea here [00:09] weird, four files are now missing from my git import [00:10] 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 [00:10] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 [00:12] * slangasek scratches his head [00:12] 0! [00:14] right, I got that part :) [00:14] morning/evening/whenever slangasek and directhex [00:14] NCommander, just gone midnight [00:15] NCommander: dawn of a new age, NCommander [00:15] according to my inbox, yes, yes it is :-P [00:15] oh hah, gnome-sharp2 is missing Replaces: on the old package names [00:20] slangasek: so those server cd's still have the "encrypt home" option [00:20] slangasek: which is going to fail miserably [00:20] slangasek: if a user select the "yes, encrypt my home" option, the user creation will fail [00:21] slangasek: i was under the impression that cjwatson had disabled that, in lieu of the missing kernel modules [00:25] kirkland: seems appropriate to treat that as errata, IMHO [00:26] slangasek: :-/ i'll go ahead and file a bug and prepare for the many duplicates [00:27] you should only get duplicates from those who use early alphas without reading the errata from the technical overview [00:27] I hope this is a small set :) [00:28] always the optimist, steve [01:06] best buy is giving away bluray players when you buy any HDMI cable $79.99 or higher and 10 bluray movies (out of a set of 50) [01:07] and has a cable advertised next to it for $116.99 [01:07] when you can get them for $4.99 easily [01:07] slangasek: https://bugs.edge.launchpad.net/ubuntu/+source/user-setup/+bug/309541 [01:07] Launchpad bug 309541 in user-setup "Jaunty Alpha 2 Installation: encrypted home directory broken" [Critical,Triaged] [01:07] slangasek: details of that bug; workaround too [01:07] slangasek: can you add that to the errata? [01:29] slangasek: okay, server iso testing posted for amd64 and i386 [01:29] kirkland: woot, thanks. Working on the errata now [01:30] * kirkland -> back to work that requires far more brain cycles [01:38] evand: was there a bug number for the ongoing issues with ubiquity manual partitioning? [01:47] Hm. It seems https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview is lying at the moment; while alpha 2 contains the DDX part of nouveau, synced from debian, we still need the kernel modules before it'll actually work. [01:48] I've got a dkms'd source package built for them; it just needs some debian/copyright love and a review. [02:03] slangasek, where are the CD build logs? [02:03] http://people.ubuntu.com/~ubuntu-archive/cd-build-logs/ ? [02:05] RAOF, ah okay - can you update the release notes accordingly [02:05] bryce: Certainly [02:05] RAOF basically what I was going for is, "Yeah, -nouveau is in the archive, but don't expect it to work" [02:06] slangasek, thanks, for some reason, twm is on the Xubuntu CD O_O; [02:06] bryce: I think we _might_ want bugs, once the kernel module's in. Upstream certainly doesn't mind bugs against the 2d component. [02:07] RAOF: please let me know when you're done making that change, I have other cleanup pending [02:09] Hm. Do you still have the lock on that page? [02:11] slangasek: Do you want to finish your edits before I do mine? The wiki's complaining you've still got the lock on that page. [02:11] RAOF: ignore my lock [02:11] moin and browser back buttons don't play nice [02:11] Heh. Done. [02:38] slangasek, can you confirm a bug for me on the CD in /etc/apt/sources.list [02:39] universe seems to have gone missing .... [02:39] in xubuntu? [02:39] yeah [02:39] this is the line shipped: deb cdrom:[Xubuntu 9.04 _Jaunty Jackalope_-Alpha i386 (20081218)/ jaunty main multiverse restricted [02:40] I don't have the xubuntu images to hand where I could inspect them [02:40] bah. Who do I file a bug with to get that fixed :-)? [02:40] is this the same xubuntu image that someone said 3 of 4 test cases passed just fine on for alpha-2? [02:41] The alternate passed [02:41] No one has reported success with desktop [02:41] you're talking about desktop? [02:41] slangasek: fyi, RAID seems busted in the installer [02:41] ok [02:41] slangasek, sorry that I wasn't clear [02:41] kirkland: bug + errata? :) [02:42] sladen: https://bugs.edge.launchpad.net/ubuntu/+source/partman-md/+bug/309555 [02:42] Launchpad bug 309555 in partman-md "cannot create raid device" [High,New] [02:42] ack [04:08] slangasek: iso tracker says we aren't currently testing upgrades. Is the intended? [04:14] hello [04:51] morning [04:54] ScottK: I wasn't planning on focusing on upgrades yet given that upgrades are a moving target (generally happening via upgrade against the archive, not against ISOs) [04:55] cjwatson: kees: hey guys, i just merged mdadm for jaunty [04:55] slangasek: OK. As long as it's by design. [04:55] cjwatson: kees: i haven't seen TheMuso around lately, who did the last merge [04:55] cjwatson: kees: the diff is exceptionally big, due to our udev methodology [04:55] cjwatson: kees: so I'd appreciate a good review [04:56] cjwatson: kees: importantly, this merge fixes a couple of really nasty, critical segfault issues, brought up by Fabbione earlier today [04:56] https://bugs.edge.launchpad.net/ubuntu/+source/mdadm/+bug/282492 for example [04:56] Launchpad bug 282492 in mdadm "mdadm seg faults when forced to assemble array" [Critical,Triaged] [04:57] cjwatson: kees: my work is available for review/sponsoring at http://people.ubuntu.com/~kirkland/mdadm/ [04:58] cjwatson: kees: from a testing perspective, i've functionally tested only a small subset of the vast array of mdadm functionality [04:59] cjwatson: kees: raid1, booting, degraded, adding a disk, failing a disk [05:00] cjwatson: kees: it would take a week or more to test every mdadm option ... what's my due diligence, here? [05:10] kirkland: I may be able to lend a mdadm testing hand in the next few days if needed when I get back in the office...I am looking at mdadm as an option for one of our appliances in the future [05:38] slangasek: I think we're in reasonable shape for Kubuntu unless some ubiquity fixes magically appear. [05:39] For Alpha 2, I'm not sure we care. [05:39] * slangasek nods [05:39] slangasek: We also have release notes for you to link to in your release announcment. [05:40] URL? [05:41] https://wiki.kubuntu.org/JauntyJackalope/Alpha2/Kubuntu [05:41] Sorry. Got distracted. [05:41] They aren't "Done", but they aren't horrible either. [05:43] dh_install --sourcedir=debian/tmp-udeb -pudev-udeb [05:43] dh_install: libvolume-id1 missing files (lib/libvolume_id.so.*), aborting [05:43] err, but I didn't tell you to do that package [05:43] The iso tracker is reasonably well filled out http://iso.qa.ubuntu.com/qatracker/build/kubuntu/all - nixternal is currently doing more amd64 alternates. [05:44] slangasek: If it were up to me and everyone else was ready to go, I'd say Kubuntu is ready enough to pull the trigger. [05:44] slangasek: In the meantime, we'll keep testing. [05:44] JFTR I did a kubuntu-desktop upgrade in a chroot and it went smoothly. [05:45] ah, apparently I did [05:45] bloody build-arch: DH_OPTIONS=a [05:45] ScottK: I am going to pass it...retested w/o my goofy setup just fine [05:46] nixternal: Great. Progress. [05:46] just gotta remember which partition is root for my goofy partition.... /dev/sda9 == (hd0,8) [05:46] ooh, pretty KDE 4 :) [05:48] slangasek: I'm off to bed, so good luck. [05:56] kirkland: cool, I will review and install it tomorrow. generally, if it looks right and you think it's ready, it's good to upload. we should always be careful, but glitches are okay -- it is the devel release, after all. :) [05:57] who needs a stripe anyways :p [05:58] Hmm I'm afraid I need to raise a SRU regression, even if it's fairly minor [05:58] dpkg : erreur de traitement de /var/cache/apt/archives/linux-libc-dev_2.6.27-11.21_amd64.deb (--unpack) : tentative de remplacement de « /usr/include/drm/drm_sarea.h », qui appartient aussi au paquet libdrm-dev [06:00] Ah no, not promoted to updates yet [06:00] slangasek: Around? we need to prevent linux from migrating to intrepid === LucidFox_ is now known as LucidFox [06:01] oh gar, I was wondering about that bit of the changelog [06:01] * synchronise our linux-libc-dev with the kernel userspace headers [06:01] - LP: #300803 [06:02] lool: please mark bug #300803 verification-failed [06:02] Launchpad bug 300803 in linux "linux-libc-dev: please include video/uvesafb.h" [Medium,Fix committed] https://launchpad.net/bugs/300803 [06:02] I don't think this should have been done in intrpeid [06:02] slangasek: (done) [06:02] indeed not; but the changelog was terse and the upstream delta large, so it didn't get very close inspection on its way through unapproved [06:04] Touching the linux-libc-dev headers in a released distro doesn't make sense IMO [06:06] (didn't exactly understand the scope of the change until reading the full description in the bug) [06:06] slangasek: Also, this needs to go synchronized with a new meta, right? [06:06] yes [06:10] good morning [06:10] hey Daniel [06:11] hey lool :) === WelshDragon is now known as Guest27540 [06:32] hmm [06:32] keep getting internal compiler errors [06:36] only in an i386 chroot though === tkamppeter_ is now known as tkamppeter === dholbach_ is now known as dholbach [08:16] hey cjwatson_ === cjwatson_ is now known as cjwatson === fargiola` is now known as fargiolas === anil1 is now known as anilg [11:24] hmm, something apparently went wrong with the pygobject build for hardy-updates/sparc; it claims to be only for python 2.5, unlike other architectures [11:24] this breaks ubiquity's build [11:26] gar, timestamps caused an autotools regeneration [11:56] bug 309674: hardy-updates regression [11:56] Launchpad bug 309674 in pygobject "python-gobject in hardy-updates on sparc misbuilt only for python2.5" [Critical,New] https://launchpad.net/bugs/309674 [11:56] (I've mailed the TB and others) [12:26] pitti: Is it your day for Archive duties? [12:28] pitti: If so, if you would accept kde4-style-bespin from binary New, then libplasma2 could be removed (NBS). [12:34] * ScottK just noticed that kdeedu is also in binary New. === lamont` is now known as lamont [13:29] WOOO, My application moved! [13:39] ^NM [13:40] NCommander, quick, apply to be project secretary! [13:40] Still no account [13:40] and I think you need to be in a year before you can apply [13:40] * NCommander would be more interested in FTP assistant if I did anything [13:40] Must. Get. NEW. Queue. Empty [13:41] yeah, greenlight my moon package plz kkthx [14:17] Does anyone know if gettext has a mechanism for handling a variable length list? For example, "%s, %s, and %s" or "%s and %s" or "%s". === fta_ is now known as fta [14:28] bryce, just attached the info you asked in bug 265029 [14:28] Launchpad bug 265029 in xorg-server "no mouse/keyboard when using evdev and autologin in gdm" [Undecided,Incomplete] https://launchpad.net/bugs/265029 [14:45] nixternal: awesome, thanks dude! [14:45] kees: cool, thanks. [14:54] kees, what do you think about bug 309732? [14:54] Launchpad bug 309732 in duma "duma FTBFS in intrepid/jaunty" [Undecided,New] https://launchpad.net/bugs/309732 [14:58] * EtienneG wonder: should mkfs create ext3 file system by default? [14:59] EtienneG: According to man mkfs, ext2 is the default. [15:00] ScottK, I know, I am questioning why :) [15:01] At a guess either a developer picking a very conservative default or not updated in a long time. [15:03] Since it's util-linux, I'd just ask lamont` === lamont` is now known as lamont [15:05] on the other hand, if it is the default in util-linux as shipped by upstream, no need to break people's assumption needlessly [15:05] still, I get caught almost everytime I manually create an fs :( [15:07] hey ScottK [15:08] Heya NCommander. [15:08] how goes it? [15:10] I keep waiting for slangasek to pull the trigger on Alpha 2. In the meantime I might get some actual $WORK done. [15:16] ScottK, same here [15:16] * NCommander is working on fixing a rather nasty bug in dpkg [15:16] assuming my sid chroot will actually build this century [15:38] * kirkland is wondering if an archive admin out there could nudge screen profiles through the queue, https://edge.launchpad.net/ubuntu/jaunty/+queue [15:38] pretty please :-) [15:42] * RainCT hugs kirkland for creating the screen profiles :) [15:42] RainCT: \o/ === The_Company is now known as Company === fargiola` is now known as fargiolas === Richie is now known as WelshDragon [16:16] norsetto: since duma was designed to overload those kinds of things, yeah, I think it's fine to pass -U_FORTIFY_SOURCE to it. === anilg is now known as anil_away [16:57] asac: around? === nhandler_ is now known as nhandler [16:57] LaserJock: on vac ;) whats up? [17:00] asac: oh, sorry. was just a NM question [17:01] asac: I can't seem to get NM to stick with a connection when I have eth0 and wifi available [17:01] when I first get on the network I tell it to connect to the eth0 network, but then it starts connecting to various wifi networks I also have available [17:02] is there some way to like prioritize them or something? [17:02] Airplane mode switch should do it. [17:02] ;-) [17:02] Remember how I said people's #1 complaint is updates break their computer? I'm on the phone with someone who says after the updates they're getting the following error message: [17:02] Aborted because of invalid compressed format (error=2) [17:02] Kernel Panic: SYNCING VFS, unable to mount root fs on unknown-block. [17:03] LaserJock: commonly complained feature ... only solution as of now is to disable wireless while being on wired [17:04] asac: ok [17:04] asac: I thought I had turned of "automatically connect" on the wifi networks but when I go into the editor it's checked [17:04] asac: does NM keep that setting? [17:04] LaserJock: system connection? [17:04] no [17:04] LaserJock: usually it works for me [17:05] asac: ok, I'll play with it some more [17:21] kees, okki, thx [17:47] evand: when is ext4 gonna appear as an option when installing server? [17:52] When It’s Ready™ would be my guess. :-) [17:54] rtg: do you think it's appropriate? it wouldn't be hard to add but I think we were waiting for the go from you guys ... [17:54] oh and I suppose we need the userspace tools to be in place, I don't know if they are [17:54] * ScottK knows jdong has been experimenting with ext4. [17:55] cjwatson: The UDS discussion was that ext4 would be offered as an option on a disk formatted installed. dist-upgrades would continue with ext3 [17:55] somebody might need to hack minimal ext4 support into parted [17:55] s/installed/install/ [17:55] dist-upgrades> yeah, I didn't doubt that [17:55] ext3 will remain the default, but ext4 needs exercizing. [17:57] I'd love to have ext4 support for fallocate. [17:57] doesn't appear to be any ext4 support in libparted. poo. [17:57] indded, ext4 has a number of advantages. [17:58] I'm interested in the trim instruction on SSDs [17:59] hmm, I thought fallocate was being implemented in ext3 as well? [18:00] kees, we planed to point to the partner repository instead of the adobe web site. [18:00] Is it? I searched for such an article on Google hoping that it would be, but came up empty. Perhaps my google-fu is lacking. [18:00] slangasek: link? [18:00] cjwatson: iirc the discussion mentioned the userspace tools were already in intrepid, but i'm sure they are still being updated as bugs are found ;-) [18:01] evand: some factoid I absorbed from skimming the samba-technical mailing list; it's possible I misunderstood [18:02] I'll just continue to hope then :) [18:02] fta: yeah, just got a brain-dump from asac [18:03] calc: looks like e2fsprogs is but that nobody's worked on libparted at all [18:03] kees, if you're already done, well.. go ahead [18:03] cjwatson: ah ok [18:20] cody-somerville: What update caused that crash? [18:21] slangasek: Is there anything from Kubuntu holding you back from Alpha 2? [18:22] ScottK: no, I just have one more Ubuntu test failure to review and some publishing to do, then we should be there [18:22] though xubuntu alternate/amd64 is untested [18:22] cody-somerville, NCommander: either of you in a position to test that? [18:22] slangasek: Great. Just wanted to make sure we weren't on the critical path. [18:23] sure, thanks for asking [18:23] slangasek, NCommander is [18:24] slangasek: Any chance of getting some binary New done? I'm particularly anxious for kde4-style-bespin and kde-edu. Once kde4-style-bespin is out, libplasma2 can be removed. [18:25] ScottK: why is kde-edu in NEW? [18:25] ScottK: yes, but not before I finish up alpha2 [18:25] New/renamed biany, I assume. [18:25] biany/bianary [18:25] slangasek: Great. [18:26] LaserJock: What university are you at again? [18:26] ScottK: University of Nevada [18:27] Is somebody working on fixing X again in jaunty? [18:27] LaserJock: plasmoid-worldclock is the new package for kde-edu [18:28] LaserJock: ondrej from DPMT is moving to Reno to go to U of N, Reno. [18:29] why is worldclock in KDE Edu? [18:29] Debian Python Modules Team (where you show up to talk matplotlib sometimes) [18:29] Dunno. Upstream does as upstream wills. [18:29] ScottK: oh, cool [18:48] * directhex reckons that if the desktop experience team were hiring for some kind of GL programming position, they should really really look at the application from the gtkglarea maintainer [18:48] if such a person had applied, anyway === anil_away is now known as anilg [20:07] Is there a channel for mirror maintence, the /fiesty/* is down at 91.189.88.40 80 [20:07] does any one have an alt ip i can use? [20:12] EvanCarroll-box2: feisty is EOL its available at old-releases but should no longer be used in general [20:13] hrm, i thought it was supported for 1yr [20:13] EvanCarroll-box2: 1.5 years... [20:13] EvanCarroll-box2: 18 months and it came out in apr 2007 [20:13] oh shit. I'm a year behind the rest of the world. [20:13] EvanCarroll-box2: no longer supported as of Oct 2008 [20:15] EvanCarroll-box2: current release is intrepid (8.10) [20:17] calc: yes, i know, i'm trying to trouble shoot intrepids cups-pdf which i think is bugged, and I wanted to have an older version for these issues.. [20:18] I aparently overachived. [20:18] I wanted 8.04, i got 7.04 [20:20] EvanCarroll-box2: heh [20:20] EvanCarroll-box2: well if you do need to go back that far you can get all releases at old-releases.ubuntu.com [20:45] I love that on one mailing list is a discussion on how SRU is too easy and on the other there is a discussion on how it's too difficult. :) [20:45] Well they both probably have their points. [20:46] Yes, but you'd have to admit there is a certain amount of irony there. [20:46] OTOH, I'm still waiting to find out which update broke cody-somerville's friend's box [20:46] Totally [20:46] ScottK, I have no idea. I'm in Ontario and they're in New Brunswick [20:46] ScottK, they can't even boot their machine [20:47] cody-somerville: surely they can use an older kernel? [20:47] like vorlon said, that's just the kind of error that comes from update-initramfs being killed or breaking [20:47] last time I saw it, a user had closed the upgrade window mid-run [20:48] elmo, Yes, I was going to give those directions but unfortunately the power is out now for her [20:48] (yea winter!) [20:48] ScottK: I find it pretty hard to figure out which update breaks things [20:49] if you're getting ~20 packages/update and you don't notice the breakage right away it's hard to pin down [20:49] elmo: hrm, our kernel postinsts should be robust against a mid-upgrade abort [20:50] you know, I think I had one of those the other day [20:50] ("should" in both the "damn well oughta be" and "I believe they're designed correctly" senses) [20:51] I was upgrading and my computer froze at updating the initramfs [20:51] but I was able to reboot ok, and running dpkg --configure -a got everything in shape [20:51] slangasek: unfortunately, I wasn't there to witness what they did, I only arrived in time to stop some helpful muppet from wiping their laptop as a "fix" [20:55] in the future I will have a consultancy firm named "Helpful Muppets" [20:57] slangasek: ok, so checking my irc logs, it appears it use to be broken; keybuk claims to have fixed it, back in Feb or so [20:57] hmm [20:57] or rather, TheMuso fixed it [20:57] bad that it was ever broken; the root design of initramfs-tools was always correct in this matter [21:04] elmo: right, this was something we fixed as a hardy "feature" (i.e. err this is a scary bug let's call the fix a feature to make damn sure it gets scheduled) [21:07] if you know the upstream bug number of a bug can you search for that via lp somehow to find the ubuntu bug report [21:07] if they are already attached together [21:07] i have a new dupe that i can't find the original bug report for [21:19] calc: yeah, there's a special redirect, let me look up how you get to it [21:23] calc: there might be a better way to do this, but one way is https://bugs.launchpad.net/bugs/bugtrackers, follow the link to the bug tracker in question, and then append /BUGNUMBER to the URL [21:23] if the bug is linked, it'll redirect you to the LP bug; otherwise it'll 404 [21:25] cjwatson: cool, thanks :) [22:01] slangasek: is archive still frozen for alpha-2, or can we start uploading post-alpha-2 stuff? [22:01] bryce: go ahead with uploading, I'm pushing the button now [22:01] (need to set up some kind of better pulley system to push the button for me) [22:07] err. did somebody NBS the armel kernel without making sure there was a new one there? [22:08] Please Don't Do That [22:08] (and if somebody could score up https://launchpad.net/ubuntu/+source/linux/2.6.28-3.4/+build/811335, I'd appreciate it) [22:09] (reason not to do it is that it means the kernel-overrides script won't be usable) [22:22] cjwatson: possibly my fault for not thinking through the implications for armel, sorry [22:23] rather, I appear to have assumed the NBS report's claim that the armel kernel flavors had no reverse-deps was an accurate indication of their state; do we not have a linux-meta on armel yet? === slangasek changed the topic of #ubuntu-devel to: UDS: done, alpha-2 released, Archive: open, MoM running | Ubuntu 8.10 released! | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-intrepid | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [22:46] ScottK, ping? [23:04] slangasek: can you help out with #304907 at all? [23:06] slangasek do you mind if I add a link to the Kubuntu release notes on the testing wiki page you referenced in the announcement? [23:15] ScottK: hmm, fail. I noticed after sending the mail that I didn't link to the release notes anywhere; you can link to them from the TechnicalOverview wiki page, and I can ask for the contents to be copied to www.u.c [23:15] Caesar: I can start by helping to stare at it in disbelief [23:18] Caesar: this seems to be a package version newer than hardy, older than hardy-updates? [23:19] Caesar: hrm, still buggy, though. I'm surprised, because I remember us having to fix a bug just like this already in hardy [23:38] what page on wiki.ubuntu.com might provide insight on how upstream project collaborate their branches with the ubuntu-core-dev team? I'm looking at the UbuntuDevelopers page and I was expecting to see somekind of link to best practices for collaboration [23:45] cjwatson: rescored [23:46] one of the questions I'm asking myself relating to collaboration is whether I should add the ubuntu-core-dev team to the trunk of my project or if I should create another branch specifically for the team. [23:47] cr3: perfectly reasonable to let ubuntu-core-dev create its own branch which is authoritative for the Ubuntu packaging [23:47] * Hobbsee mutters something about mail as a result [23:48] slangasek: is there a usual naming convention or recommendation for the branch used by the ubuntu-core-dev team/ [23:48] Caesar: actually, I can't find any record of this particular file conflict existing in the Ubuntu archive [23:48] slangasek: and, in launchpad, should the branch be under the ubuntu project or under the upstream project? [23:48] cr3: that would normally be created by the ubuntu-core-dev team itself [23:48] it would be a branch associated with the upstream project [23:49] but belonging to the ubuntu-core-dev [23:49] group [23:49] e.g., lp:~ubuntu-core-dev/grub/ubuntu [23:51] And if you're not in ubuntu-core-dev, you can request a merge into that branch [23:54] slangasek: thanks for the explanation, everything is now clear :)