[01:45] maybe i'm just too tired but its hard to figure out what needs to be done in ubuntu. I wanna start to help out but everything seems spread all over [01:47] SirBob1701: you can start on #-motu [01:47] zul: ok thanks [02:08] ping * [02:22] emgent: ? [02:23] done. [02:23] i was found a security bug in ubuntu.com website [02:23] https://bugs.edge.launchpad.net/ubuntu-website/+bug/180468 [02:26] emgent: can you subscribe "ubuntu-security" to that bug? [02:26] sure [02:26] thx [02:27] heya keescook :* [02:27] hiya :) just stepping out for dinner [02:28] whats the release date for hardy? aprl may ? [02:28] nuxil: wiki.ubuntu.com/HardyReleaseSchedule [02:29] thank you === noobuntu is now known as n00buntu [03:34] * lamont plays with his new laptop [03:35] nifty, what kind? [03:40] Dell Inspiron 1520 [03:40] LaserJock: PONIES [03:40] LaserJock: In all seriousness, Gutsy was out two months ago [03:41] yeah ... I know :/ [03:41] Umm.. It's January. That's three months [03:41] persia: 2.5 [04:06] anyone know if hardy alpha 3 will ship with firefox 3? [04:09] Considering Gutsy was released with a version of it, I'd say yes. [04:09] But shipping is different to it being in the archives IMO. [04:10] yea.. I know it'll be in the archives I am currently using it [04:10] I doubt firefox 3 will be out early enough to be shipped on hardy CD. [04:11] Hardy, being LTS and all, probably won't use a beta version for default browser. [04:11] does it have to be fully out to make it to an alpha cd? [04:11] And I don't see it shipping both firefox 2 and 3 either. [04:11] Even if 3 is out, I don't see it being shipped for an LTS. [04:12] TheMuso: Why not? 2 won't be supportable. [04:12] Well, it will be even less supportable. [04:12] Fujitsu: Oh... [04:12] Mozilla kills off old series very quickly. [04:12] I do believe there is already a commitment to use xulrunner in the final release, so I think it'll be FF3. [04:12] yea.. I assumed it would ship final with 3 [04:12] gQuig1: You are still not clear with your question though, what is the "ship" you mean? Default browser? Installed by default? In main? [04:12] I was asking about the alpha 3 [04:13] on default cd [04:13] Alpha 3 will ship with Firefox 2 on the CD. [04:13] ScottK: Does the firefox-3.0 currently in archive already using xulrunner? [04:13] yup [04:14] Everything on the desktop CD will be installed, right? [04:14] minghua: It depends on it. [04:14] minghua: Except for a couple of live-specific things which are removed after it's installed. [04:14] what's the reason we can't go to firefox 3 for an alpha? [04:14] Nice, probably I should try it, instead of using the binary downloaded from mozilla.com. [04:14] s/com/org/, I think. [04:14] minghua: I think so. [04:15] I find Firefox 3 to be much, much nicer than Firefox 2. It's actually usable! [04:15] Fujitsu, ScottK: Thanks for the info. [04:15] Firefox 3 beta1 was terrible on my Debian. [04:16] What was wrong with it? [04:16] I find some of the features slow without video acceleration [04:16] but I'm currently running nouveau so... [04:16] The scrolling tab bar is infuriating. [04:16] Arrrrrgh! [04:17] It's turning into Windows XP! [04:17] I don't want to be questioned when going into about:config, TYVM. [04:17] ....Firefox 3 is turning into XP? [04:17] Considering we already need permission to patch it. [04:17] Fujitsu: What's wrong with beta1? The font rendering was completely unbearable. It was much better in beta2 though. [04:18] gQuig1: It gives me a page warning not to do bad things when I go to about:config. XP does similar when opening up C:, Program Files, etc. [04:18] eh.. I liked it [04:18] Be careful, this gun is loaded! [04:19] Heh. [04:20] Fujitsu: That can be disabled in about:config, IIRC. [04:20] minghua: Or by unchecking the `show this every time' checkbox. [04:20] Looks like it's general.warnOnAboutConfig. [04:21] ... why is there a key named general.config.obscure_value? [04:25] don't know why but I want to say for compatibility [04:27] * gQuig1 would like to see firefox 3 in alpha 3 if possible to get better testing coverage and wishes all a good night === cassidy_ is now known as cassidy === bigon is now known as bigon` === emgent_ is now known as emgent === asac_ is now known as asac [07:46] I've got a question about defualt settings for hardy. I work over on the ubuntu forums in the absolute beginners fourms answering questions, lately I've seen a bunch of problems from people with fresh installs that have all of thier repositories disabled because they installed gutsy while not connected to the internet. Is there a bug report for, or discussion, of removing the repository check during the install? It seems like a good i [07:48] #ubuntu+1 [08:54] peterjtech: https://blueprints.launchpad.net/ubuntu/+spec/networkless-installation-fixes [08:55] It's targeted for Hardy: https://blueprints.launchpad.net/ubuntu/hardy/ [08:55] evand: that's good to know [08:56] I was looking around in launchpad but couldn't think of good search terms to find what I was looking for, seems rather obvious now [08:58] * Fujitsu would like that, particularly with smaller timeouts, as he installed yesterday when au.a.u.c was down, which caused much waiting and brokenness. === Lure is now known as Lure_ === Lure_ is now known as Lure [09:46] how do i disable the login window after resuming from suspend? [09:51] tuntun: This channel isn't for support. Use #ubuntu. [10:24] can somebody give-back kdeedu-kde4 (kde4libs is built now) === Lure_ is now known as Lure === \sh_away is now known as \sh [11:28] imbrandon, you still around? [11:29] superm1: It's getting to the time when people in his part of the world /should/ be up. Thus, you can fairly safely say he's not. [11:29] Fujitsu, he does work odd hours for central time though on a regular basis [11:29] so i figured it'd be worth a shot [11:44] well if any other core-devs would have a few moments to look over the patch i was going to show imbrandon, i'd appreciate it: http://pastebin.ubuntu.com/3300/ [11:45] * persia gets reminded, and goes digging for rarely used hardware [11:45] persia, i was thinking more about what you said the other day, and realized there was a corner case that caused it to reconfigure itself without user asking [11:45] persia, hence was pre-empted this patch [11:46] superm1: The changelog looks to hit all the points I had referenced, but I really should test with my hardware and get back to you. I'll wait for the new rev to send feedback (but make sure I have my HW handy first). [12:33] hmh, what broke gdbm? [12:34] bug 180368 for instance [12:34] Launchpad bug 180368 in command-not-found "gdbm fatal: lseek error" [Undecided,Confirmed] https://launchpad.net/bugs/180368 [12:43] oh, seems that the error message is from c-n-f after all.. I just didn't have the command installed that I tried to run :) === bigon` is now known as bigon === fabbione is now known as thegodfather === thekorn__ is now known as thekorn [15:36] is ntop broken in gutsy ? [15:38] i dont know. but it seems to broken. buggy === Lure_ is now known as Lure === Traxer is now known as Traxer|on === Traxer|on is now known as Traxer === TheK is now known as KaiL === cassidy_ is now known as cassidy === cassidy_ is now known as cassidy [19:14] any archive admins hanging out today? I need a give back on kaider-kde4 that I just uploaded...thanks === \sh is now known as \sh_away [19:22] nixternal: this package doesn't seem to exist? [19:25] nixternal: hasn't got past NEW [19:32] nixternal: then you don't need a giveback (that's necessary for a previously failed build which should work now) === pitti_ is now known as pitti [19:50] pitti: thanks [19:53] pitti: if I upload new will it overwrite, or should I bump the revision to ensure it? [19:54] nixternal: you mean upload the same version again? [19:54] ya [19:54] nixternal: you can do that, both will be in NEW [19:54] groovy [19:54] nixternal: but I'd prefer rejecting the previous one first to avoid confusion which is the good one [19:54] k, how do I reject or request that? [19:54] haven't had to do that ever [19:54] nixternal: so, shall I kill kaider-kde4 from NEW? [19:54] yes please [19:54] and I owe you a cookie, or a drink of your choice :) [19:54] killed; NP :) [19:55] you rock! thanks again [19:55] I cd'd into the wrong directory and dput the wrong one [19:58] pitti: do you have a suggestion what to do with a package which uses ${source:Version} to depend on an package from an other source? In Debian the versions are kept in sync but in Ubuntu one package has changes which breaks this dependency [19:59] geser: hm, that sounds pretty fragile to begin with [19:59] why can't we keep those in sync, too? [19:59] if the strict dependency is actually justified, we have to do that anyway [19:59] and if not, we should file a Debian bug to relax it [20:00] we could, but then I would need to upload an cyrus-sasl2-heimdal 2.1.22.dfsg1-16ubuntu2 as a rebuild [20:00] the strict dependency is from cyrus-sasl2-heimdal-dbg to cyrus-sasl2-dbg [20:01] hm; in this case I think a rebuild is justified (new compiler, toolchain, etc.) [20:03] it looks odd to use ubuntu2 as a rebuild and skipping ubuntu1 [20:03] oh, right, it's unmodified ATM [20:04] would be unfortunate to break it indeed [20:08] so, I wouldn't mind fixing cyrus-sasl's dependency either [20:11] I see now that uploading cyrus-sasl2-heimdal with ubuntu2 would also fix the unmet deps for libsasl2-modules-gssapi-heimdal [20:11] so I don't get hurt when I do this strange upload? :) [20:12] or is there a better solution? [20:17] DktrKranz: ./configure && make && debuild binary giusto? [21:23] Is nobody interested in sponsoring the fix for bug 177032? :) [21:23] Launchpad bug 177032 in dash "Regression with filename glob expanding" [High,Triaged] https://launchpad.net/bugs/177032 [21:26] blueyed: I guess now is not a good moment to search for a main sponsor :) [21:36] geser: are you refering to weekdays/weekend? [21:37] blueyed: yes, and that it's evening in europe [21:38] there are some core devs not in europe ;-) [21:47] LaserJock: true, but the chance to find a non-european core-dev on a weekend here aren't much better (in particular one who is willing to do some sponsoring) [21:50] LaserJock: Are you up for some Main sponsoring? [21:51] actually depends on the patch/package [21:51] I generally don't like being the guy who breaks core apps ;-) [21:51] I've got two small ones. [21:51] Both should be safe. [21:52] Bug 17169 is one [21:52] Launchpad bug 17169 in dput "Avoid warning when uploading packages with -0ubuntu1 revision" [Medium,Fix committed] https://launchpad.net/bugs/17169 [21:53] Bug #178203 is the other. [21:53] Launchpad bug 178203 in pinentry "Please merge pinentry (0.7.4-2) from Debian Unstable (Main)" [Wishlist,Fix committed] https://launchpad.net/bugs/178203 [21:53] ScottK: k [21:54] LaserJock: Thanks. === jpatrick_ is now known as jpatrick [22:05] ScottK: was there a rationale for adding in debian-mentors to dput.cf other than it's nice to have? [22:08] LaserJock: My rationale is that it does no harm and makes it easier to contribute back to Debian (one less barrier) and that's a good thing. [22:08] right, I just wondered if there was a bug [22:09] No. I didn't see value in filing a bug for that. [22:09] I wouldn't have done it if I wasn't actually fixing something at the same time. [22:09] I did recently set up a new laptop and it was slightly annoying to have to add it by hand. [22:10] sure, I think it's a good idea [22:10] we have revu in there [22:10] Exactly. [22:15] ScottK: hmm, actually there is a new Debian version that has a number of fixes, perhaps a merge would be good? [22:15] LaserJock: I'll have a look at it. [22:15] I'll look at the other one while you're doing that === noobuntu is now known as wqadfqag [22:16] Sounds good. [22:35] LaserJock: Merge debdiff attached to the bug. [22:40] ScottK: pinentry done [22:41] LaserJock: Thanks. [22:41] I have to run out for a while to drop one of my kids off for a church function. I'll be back in about 45 minutes or so. [23:07] ScottK: dput done as well, thanks for the merge [23:10] It would be nice if /etc/dput.cf had an entry for ppa by default. That would require ppa to be changed a bit, though. [23:11] ion_: I don't know how you could do that. How would you determine what PPA to upload to? [23:11] By the signing key [23:12] that's not enough [23:12] that might work for personal PPAs I guess, but wouldn't for teams [23:12] If you want to upload to a team PPA, then you’d need to add your own ppa entry. [23:13] I guess the common use case would be for personal ppas [23:16] LaserJock: Thanks.