[00:00] <slangasek> 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] <directhex> don't forget gnome-desktop-sharp2 too!
[00:01] <directhex> i have no idea why upstream split those
[00:04] <kirkland> slangasek: iso coming down painfully slower than usual
[00:05] <kirkland> any ideas why my usb mouse stopped working in jaunty after an update earlier this week?
[00:06] <slangasek> usb mouse - no idea here
[00:09] <Keybuk> weird, four files are now missing from my git import
[00:10] <geubank4> 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[00:10] <geubank4> 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[00:12]  * slangasek scratches his head
[00:12] <directhex> 0!
[00:14] <slangasek> right, I got that part :)
[00:14] <NCommander> morning/evening/whenever slangasek and directhex
[00:14] <directhex> NCommander, just gone midnight
[00:15] <slangasek> NCommander: dawn of a new age, NCommander
[00:15] <NCommander> according to my inbox, yes, yes it is :-P
[00:15] <slangasek> oh hah, gnome-sharp2 is missing Replaces: on the old package names
[00:20] <kirkland> slangasek: so those server cd's still have the "encrypt home" option
[00:20] <kirkland> slangasek: which is going to fail miserably
[00:20] <kirkland> slangasek: if a user select the "yes, encrypt my home" option, the user creation will fail
[00:21] <kirkland> slangasek: i was under the impression that cjwatson had disabled that, in lieu of the missing kernel modules
[00:25] <slangasek> kirkland: seems appropriate to treat that as errata, IMHO
[00:26] <kirkland> slangasek: :-/  i'll go ahead and file a bug and prepare for the many duplicates
[00:27] <slangasek> you should only get duplicates from those who use early alphas without reading the errata from the technical overview
[00:27] <slangasek> I hope this is a small set :)
[00:28] <directhex> always the optimist, steve
[01:06] <calc> 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] <calc> and has a cable advertised next to it for $116.99
[01:07] <calc> when you can get them for $4.99 easily
[01:07] <kirkland> slangasek: https://bugs.edge.launchpad.net/ubuntu/+source/user-setup/+bug/309541
[01:07] <kirkland> slangasek: details of that bug;  workaround too
[01:07] <kirkland> slangasek: can you add that to the errata?
[01:29] <kirkland> slangasek: okay, server iso testing posted for amd64 and i386
[01:29] <slangasek> kirkland: woot, thanks.  Working on the errata now
[01:30]  * kirkland -> back to work that requires far more brain cycles
[01:38] <slangasek> evand: was there a bug number for the ongoing issues with ubiquity manual partitioning?
[01:47] <RAOF> 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] <RAOF> I've got a dkms'd source package built for them; it just needs some debian/copyright love and a review.
[02:03] <NCommander> slangasek, where are the CD build logs?
[02:03] <slangasek> http://people.ubuntu.com/~ubuntu-archive/cd-build-logs/ ?
[02:05] <bryce> RAOF, ah okay - can you update the release notes accordingly
[02:05] <RAOF> bryce: Certainly
[02:05] <bryce> RAOF basically what I was going for is, "Yeah, -nouveau is in the archive, but don't expect it to work"
[02:06] <NCommander> slangasek, thanks, for some reason, twm is on the Xubuntu CD O_O;
[02:06] <RAOF> 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] <slangasek> RAOF: please let me know when you're done making that change, I have other cleanup pending
[02:09] <RAOF> Hm.  Do you still have the lock on that page?
[02:11] <RAOF> 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] <slangasek> RAOF: ignore my lock
[02:11] <slangasek> moin and browser back buttons don't play nice
[02:11] <RAOF> Heh.  Done.
[02:38] <NCommander> slangasek, can you confirm a bug for me on the CD in /etc/apt/sources.list
[02:39] <NCommander> universe seems to have gone missing ....
[02:39] <slangasek> in xubuntu?
[02:39] <NCommander> yeah
[02:39] <NCommander> this is the line shipped:  deb cdrom:[Xubuntu 9.04 _Jaunty Jackalope_-Alpha i386 (20081218)/ jaunty main multiverse restricted
[02:40] <slangasek> I don't have the xubuntu images to hand where I could inspect them
[02:40] <NCommander> bah. Who do I file a bug with to get that fixed :-)?
[02:40] <slangasek> is this the same xubuntu image that someone said 3 of 4 test cases passed just fine on for alpha-2?
[02:41] <NCommander> The alternate passed
[02:41] <NCommander> No one has reported success with desktop
[02:41] <slangasek> you're talking about desktop?
[02:41] <kirkland> slangasek: fyi, RAID seems busted in the installer
[02:41] <slangasek> ok
[02:41] <NCommander> slangasek, sorry that I wasn't clear
[02:41] <slangasek> kirkland: bug + errata? :)
[02:42] <kirkland> sladen: https://bugs.edge.launchpad.net/ubuntu/+source/partman-md/+bug/309555
[02:42] <slangasek> ack
[04:08] <ScottK> slangasek: iso tracker says we aren't currently testing upgrades.  Is the intended?
[04:14] <ashiswin> hello
[04:51] <lool> morning
[04:54] <slangasek> 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] <kirkland> cjwatson: kees: hey guys, i just merged mdadm for jaunty
[04:55] <ScottK> slangasek: OK.  As long as it's by design.
[04:55] <kirkland> cjwatson: kees: i haven't seen TheMuso around lately, who did the last merge
[04:55] <kirkland> cjwatson: kees: the diff is exceptionally big, due to our udev methodology
[04:55] <kirkland> cjwatson: kees: so I'd appreciate a good review
[04:56] <kirkland> cjwatson: kees: importantly, this merge fixes a couple of really nasty, critical segfault issues, brought up by Fabbione earlier today
[04:56] <kirkland> https://bugs.edge.launchpad.net/ubuntu/+source/mdadm/+bug/282492 for example
[04:57] <kirkland> cjwatson: kees: my work is available for review/sponsoring at http://people.ubuntu.com/~kirkland/mdadm/
[04:58] <kirkland> cjwatson: kees: from a testing perspective, i've functionally tested only a small subset of the vast array of mdadm functionality
[04:59] <kirkland> cjwatson: kees: raid1, booting, degraded, adding a disk, failing a disk
[05:00] <kirkland> cjwatson: kees: it would take a week or more to test every mdadm option ... what's my due diligence, here?
[05:10] <nixternal> 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] <ScottK> slangasek: I think we're in reasonable shape for Kubuntu unless some ubiquity fixes magically appear.
[05:39] <ScottK> For Alpha 2, I'm not sure we care.
[05:39]  * slangasek nods
[05:39] <ScottK> slangasek: We also have release notes for you  to link to in your release announcment.
[05:40] <slangasek> URL?
[05:41] <ScottK> https://wiki.kubuntu.org/JauntyJackalope/Alpha2/Kubuntu
[05:41] <ScottK> Sorry.  Got distracted.
[05:41] <ScottK> They aren't "Done", but they aren't horrible either.
[05:43] <Keybuk> dh_install --sourcedir=debian/tmp-udeb -pudev-udeb
[05:43] <Keybuk> dh_install: libvolume-id1 missing files (lib/libvolume_id.so.*), aborting
[05:43] <Keybuk> err, but I didn't tell you to do that package
[05:43] <ScottK> 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] <ScottK> 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] <ScottK> slangasek: In the meantime, we'll keep testing.
[05:44] <ScottK> JFTR I did a kubuntu-desktop upgrade in a chroot and it went smoothly.
[05:45] <Keybuk> ah, apparently I did
[05:45] <Keybuk> bloody build-arch: DH_OPTIONS=a
[05:45] <nixternal> ScottK: I am going to pass it...retested w/o my goofy setup just fine
[05:46] <ScottK> nixternal: Great.  Progress.
[05:46] <nixternal> just gotta remember which partition is root for my goofy partition.... /dev/sda9 == (hd0,8)
[05:46] <nixternal> ooh, pretty KDE 4 :)
[05:48] <ScottK> slangasek: I'm off to bed, so good luck.
[05:56] <kees> 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] <nixternal> who needs a stripe anyways :p
[05:58] <lool> Hmm I'm afraid I need to raise a SRU regression, even if it's fairly minor
[05:58] <lool> 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] <lool> Ah no, not promoted to updates yet
[06:00] <lool> slangasek: Around?  we need to prevent linux from migrating to intrepid
[06:01] <slangasek> oh gar, I was wondering about that bit of the changelog
[06:01] <lool>   * synchronise our linux-libc-dev with the kernel userspace headers
[06:01] <lool>     - LP: #300803
[06:02] <slangasek> lool: please mark bug #300803 verification-failed
[06:02] <lool> I don't think this should have been done in intrpeid
[06:02] <lool> slangasek: (done)
[06:02] <slangasek> 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] <lool> Touching the linux-libc-dev headers in a released distro doesn't make sense IMO
[06:06] <lool> (didn't exactly understand the scope of the change until reading the full description in the bug)
[06:06] <lool> slangasek: Also, this needs to go synchronized with a new meta, right?
[06:06] <slangasek> yes
[06:10] <dholbach> good morning
[06:10] <lool> hey Daniel
[06:11] <dholbach> hey lool :)
[06:32] <Keybuk> hmm
[06:32] <Keybuk> keep getting internal compiler errors
[06:36] <Keybuk> only in an i386 chroot though
[08:16] <NCommander> hey cjwatson_
[11:24] <cjwatson> 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] <cjwatson> this breaks ubiquity's build
[11:26] <cjwatson> gar, timestamps caused an autotools regeneration
[11:56] <cjwatson> bug 309674: hardy-updates regression
[11:56] <cjwatson> (I've mailed the TB and others)
[12:26] <ScottK> pitti: Is it your day for Archive duties?
[12:28] <ScottK> 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.
[13:29] <NCommander> WOOO, My application moved!
[13:39] <NCommander> ^NM
[13:40] <directhex> NCommander, quick, apply to be project secretary!
[13:40] <NCommander> Still no account
[13:40] <NCommander> 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] <NCommander> Must. Get. NEW. Queue. Empty
[13:41] <directhex> yeah, greenlight my moon package plz kkthx
[14:17] <evand> 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".
[14:28] <fta> bryce, just attached the info you asked in bug 265029
[14:45] <kirkland> nixternal: awesome, thanks dude!
[14:45] <kirkland> kees: cool, thanks.
[14:54] <norsetto> kees, what do you think about bug 309732?
[14:58]  * EtienneG wonder: should mkfs create ext3 file system by default?
[14:59] <ScottK> EtienneG: According to man mkfs, ext2 is the default.
[15:00] <EtienneG> ScottK, I know, I am questioning why :)
[15:01] <ScottK> At a guess either a developer picking a very conservative default or not updated in a long time.
[15:03] <ScottK> Since it's util-linux, I'd just ask lamont`
[15:05] <EtienneG> 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] <EtienneG> still, I get caught almost everytime I manually create an fs :(
[15:07] <NCommander> hey ScottK
[15:08] <ScottK> Heya NCommander.
[15:08] <NCommander> how goes it?
[15:10] <ScottK> I keep waiting for slangasek to pull the trigger on Alpha 2.  In the meantime I might get some actual $WORK done.
[15:16] <NCommander> ScottK, same here
[15:16]  * NCommander is working on fixing a rather nasty bug in dpkg
[15:16] <NCommander> 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] <kirkland> pretty please :-)
[15:42]  * RainCT hugs kirkland for creating the screen profiles :)
[15:42] <kirkland> RainCT: \o/
[16:16] <kees> norsetto: since duma was designed to overload those kinds of things, yeah, I think it's fine to pass -U_FORTIFY_SOURCE to it.
[16:57] <LaserJock> asac: around?
[16:57] <asac> LaserJock: on vac ;) whats up?
[17:00] <LaserJock> asac: oh, sorry. was just a NM question
[17:01] <LaserJock> asac: I can't seem to get NM to stick with a connection when I have eth0 and wifi available
[17:01] <LaserJock> 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] <LaserJock> is there some way to like prioritize them or something?
[17:02] <ScottK-laptop> Airplane mode switch should do it.
[17:02] <ScottK-laptop> ;-)
[17:02] <cody-somerville> 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] <cody-somerville> Aborted because of invalid compressed format (error=2)
[17:02] <cody-somerville> Kernel Panic: SYNCING VFS, unable to mount root fs on unknown-block.
[17:03] <asac> LaserJock: commonly complained feature ... only solution as of now is to disable wireless while being on wired
[17:04] <LaserJock> asac: ok
[17:04] <LaserJock> 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] <LaserJock> asac: does NM keep that setting?
[17:04] <asac> LaserJock: system connection?
[17:04] <LaserJock> no
[17:04] <asac> LaserJock: usually it works for me
[17:05] <LaserJock> asac: ok, I'll play with it some more
[17:21] <norsetto> kees, okki, thx
[17:47] <rtg> evand: when is ext4 gonna appear as an option when installing server?
[17:52] <ion_> When It’s Ready™ would be my guess. :-)
[17:54] <cjwatson> 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] <cjwatson> 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] <rtg> 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] <cjwatson> somebody might need to hack minimal ext4 support into parted
[17:55] <rtg> s/installed/install/
[17:55] <cjwatson> dist-upgrades> yeah, I didn't doubt that
[17:55] <rtg> ext3 will remain the default, but ext4 needs exercizing.
[17:57] <evand> I'd love to have ext4 support for fallocate.
[17:57] <cjwatson> doesn't appear to be any ext4 support in libparted. poo.
[17:57] <rtg> indded, ext4 has a number of advantages.
[17:58] <rtg> I'm interested in the trim instruction on SSDs
[17:59] <slangasek> hmm, I thought fallocate was being implemented in ext3 as well?
[18:00] <fta> kees, we planed to point to the partner repository instead of the adobe web site.
[18:00] <evand> 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] <evand> slangasek: link?
[18:00] <calc> 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] <slangasek> evand: some factoid I absorbed from skimming the samba-technical mailing list; it's possible I misunderstood
[18:02] <evand> I'll just continue to hope then :)
[18:02] <kees> fta: yeah, just got a brain-dump from asac
[18:03] <cjwatson> calc: looks like e2fsprogs is but that nobody's worked on libparted at all
[18:03] <fta> kees, if you're already done, well.. go ahead
[18:03] <calc> cjwatson: ah ok
[18:20] <ScottK> cody-somerville: What update caused that crash?
[18:21] <ScottK> slangasek: Is there anything from Kubuntu holding you back from Alpha 2?
[18:22] <slangasek> ScottK: no, I just have one more Ubuntu test failure to review and some publishing to do, then we should be there
[18:22] <slangasek> though xubuntu alternate/amd64 is untested
[18:22] <slangasek> cody-somerville, NCommander: either of you in a position to test that?
[18:22] <ScottK> slangasek: Great.  Just wanted to make sure we weren't on the critical path.
[18:23] <slangasek> sure, thanks for asking
[18:23] <cody-somerville> slangasek, NCommander is
[18:24] <ScottK> 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] <LaserJock> ScottK: why is kde-edu in NEW?
[18:25] <slangasek> ScottK: yes, but not before I finish up alpha2
[18:25] <ScottK> New/renamed biany, I assume.
[18:25] <ScottK> biany/bianary
[18:25] <ScottK> slangasek: Great.
[18:26] <ScottK> LaserJock: What university are you at again?
[18:26] <LaserJock> ScottK: University of Nevada
[18:27] <hunger> Is somebody working on fixing X again in jaunty?
[18:27] <ScottK> LaserJock: plasmoid-worldclock is the new package for kde-edu
[18:28] <ScottK> LaserJock: ondrej from DPMT is moving to Reno to go to U of N, Reno.
[18:29] <LaserJock> why is worldclock in KDE Edu?
[18:29] <ScottK> Debian Python Modules Team (where you show up to talk matplotlib sometimes)
[18:29] <ScottK> Dunno.  Upstream does as upstream wills.
[18:29] <LaserJock> 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] <directhex> if such a person had applied, anyway
[20:07] <EvanCarroll-box2> Is there a channel for mirror maintence, the /fiesty/* is down at 91.189.88.40 80
[20:07] <EvanCarroll-box2> does any one have an alt ip i can use?
[20:12] <calc> EvanCarroll-box2: feisty is EOL its available at old-releases but should no longer be used in general
[20:13] <EvanCarroll-box2> hrm, i thought it was supported for 1yr
[20:13] <Nafallo> EvanCarroll-box2: 1.5 years...
[20:13] <calc> EvanCarroll-box2: 18 months and it came out in apr 2007
[20:13] <EvanCarroll-box2> oh shit. I'm a year behind the rest of the world.
[20:13] <calc> EvanCarroll-box2: no longer supported as of Oct 2008
[20:15] <calc> EvanCarroll-box2: current release is intrepid (8.10)
[20:17] <EvanCarroll-box2> 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] <EvanCarroll-box2> I aparently overachived.
[20:18] <EvanCarroll-box2> I wanted 8.04, i got 7.04
[20:20] <calc> EvanCarroll-box2: heh
[20:20] <calc> EvanCarroll-box2: well if you do need to go back that far you can get all releases at old-releases.ubuntu.com
[20:45] <tedg> 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] <ScottK> Well they both probably have their points.
[20:46] <tedg> Yes, but you'd have to admit there is a certain amount of irony there.
[20:46] <ScottK> OTOH, I'm still waiting to find out which update broke cody-somerville's friend's box
[20:46] <ScottK> Totally
[20:46] <cody-somerville> ScottK, I have no idea. I'm in Ontario and they're in New Brunswick
[20:46] <cody-somerville> ScottK, they can't even boot their machine
[20:47] <elmo> cody-somerville: surely they can use an older kernel?
[20:47] <elmo> like vorlon said, that's just the kind of error that comes from update-initramfs being killed or breaking
[20:47] <elmo> last time I saw it, a user had closed the upgrade window mid-run
[20:48] <cody-somerville> elmo, Yes, I was going to give those directions but unfortunately the power is out now for her
[20:48] <cody-somerville> (yea winter!)
[20:48] <LaserJock> ScottK: I find it pretty hard to figure out which update breaks things
[20:49] <LaserJock> if you're getting ~20 packages/update and you don't notice the breakage right away it's hard to pin down
[20:49] <slangasek> elmo: hrm, our kernel postinsts should be robust against a mid-upgrade abort
[20:50] <LaserJock> you know, I think I had one of those the other day
[20:50] <slangasek> ("should" in both the "damn well oughta be" and "I believe they're designed correctly" senses)
[20:51] <LaserJock> I was upgrading and my computer froze at updating the initramfs
[20:51] <LaserJock> but I was able to reboot ok, and running dpkg --configure -a got everything in shape
[20:51] <elmo> 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] <slangasek> in the future I will have a consultancy firm named "Helpful Muppets"
[20:57] <elmo> 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] <slangasek> hmm
[20:57] <elmo> or rather, TheMuso fixed it
[20:57] <slangasek> bad that it was ever broken; the root design of initramfs-tools was always correct in this matter
[21:04] <cjwatson> 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] <calc> 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] <calc> if they are already attached together
[21:07] <calc> i have a new dupe that i can't find the original bug report for
[21:19] <cjwatson> calc: yeah, there's a special redirect, let me look up how you get to it
[21:23] <cjwatson> 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] <cjwatson> if the bug is linked, it'll redirect you to the LP bug; otherwise it'll 404
[21:25] <calc> cjwatson: cool, thanks :)
[22:01] <bryce> slangasek: is archive still frozen for alpha-2, or can we start uploading post-alpha-2 stuff?
[22:01] <slangasek> bryce: go ahead with uploading, I'm pushing the button now
[22:01] <slangasek> (need to set up some kind of better pulley system to push the button for me)
[22:07] <cjwatson> err. did somebody NBS the armel kernel without making sure there was a new one there?
[22:08] <cjwatson> Please Don't Do That
[22:08] <cjwatson> (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] <cjwatson> (reason not to do it is that it means the kernel-overrides script won't be usable)
[22:22] <slangasek> cjwatson: possibly my fault for not thinking through the implications for armel, sorry
[22:23] <slangasek> 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?
[22:46] <NCommander> ScottK, ping?
[23:04] <Caesar> slangasek: can you help out with #304907 at all?
[23:06] <ScottK-palm> 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] <slangasek> 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] <slangasek> Caesar: I can start by helping to stare at it in disbelief
[23:18] <slangasek> Caesar: this seems to be a package version newer than hardy, older than hardy-updates?
[23:19] <slangasek> 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] <cr3> 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] <Hobbsee> cjwatson: rescored
[23:46] <cr3> 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] <slangasek> 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] <cr3> slangasek: is there a usual naming convention or recommendation for the branch used by the ubuntu-core-dev team/
[23:48] <slangasek> Caesar: actually, I can't find any record of this particular file conflict existing in the Ubuntu archive
[23:48] <cr3> slangasek: and, in launchpad, should the branch be under the ubuntu project or under the upstream project?
[23:48] <slangasek> cr3: that would normally be created by the ubuntu-core-dev team itself
[23:48] <slangasek> it would be a branch associated with the upstream project
[23:49] <slangasek> but belonging to the ubuntu-core-dev
[23:49] <slangasek> group
[23:49] <slangasek> e.g., lp:~ubuntu-core-dev/grub/ubuntu
[23:51] <StevenK> And if you're not in ubuntu-core-dev, you can request a merge into that branch
[23:54] <cr3> slangasek: thanks for the explanation, everything is now clear :)