[01:02] I'm sometimes looking for a particular string in a package to (re)translate it really quick. Downloading and uploading the .po file would take too much time and the search does not look inside the packages. [01:04] kiko: so is it ok for us to go through the Janitor closings and reopen? Will that mess anything up? [01:04] Balaams_Miracle: I think that's bug #44, but I can't check now. [01:04] Having a program like i envision would download the first translation page of a package, then download the rest in the background. It would also allow for search and/or replace. Translated strings would be uploaded once an entire page (or perhaps package) is translated [01:04] LaserJock, no, if you reopen and we do a pass that it should have been reopened, we'll just ignore and move on. [01:04] Fujitsu: Really? I thought i wasn't being very original :-) [01:04] Balaams_Miracle: THe lack of searching, that is. [01:06] Fujitsu: Would you use an app like the one i just dreamed up? [01:06] I do no translations, so no. [01:06] LOL [01:06] But if you did do translations? [01:07] bazaar.launchpad.net seems to be refusing connections on port 22... [01:07] I have no idea about the workflow, so I really don't know. [01:07] Odd_Bloke: lp down for maintaince [01:07] Odd_Bloke: Launchpad is down for maintenance for around another 20 minutes. [01:07] Ah, OK. Could that be in the topic? [01:07] +spelling indeed [01:07] Odd_Bloke: You'd think. [01:07] Fujitsu: yeah, people need to write more non-English software so we can have a crack at translating ;-) [01:07] Odd_Bloke: that's what I asked :-P [01:07] Odd_Bloke: in the mean tme, let's have a chat-a-thon! :-) [01:08] people read the topic?? [01:08] LaserJock: Heheh, yes. [01:08] Fujitsu: I need the karma :-) [01:08] LaserJock: I did before I asked, to avoid being piled on by people who had read the topic. :p [01:08] LaserJock: You can still translate (or correct the spelling of) the English packages [01:09] I tried to find some en_GB I could translate to en_US but I didn't see much :-) [01:09] LaserJock: How about en_US to en_GB? Or en_ZA? [01:10] hmm, I *might* be able to do en_US to en_GB :-) [01:10] but I generally don't touch Rosetta at all [01:11] I wish there was an en_SILLY option... :-) [01:11] I've tried to do some stuff on the dev end trying to get .pots put on LP and back down [01:11] but even that hurt my brain [01:11] I want and en_hacker option, and a en_fudd too like google. [01:11] After installing that, you'd get stuff like "WHEE! There was an error!" [01:12] "Press any key to continue, dude." [01:13] "Busted! That was an illegal option." [01:14] The OK-buttomn should read "Hmmmkay..." [01:16] And imagine the fun to be had whilst translating the default messaages to one's native language. When translating verbatim, they can yield some crazy results === tck [n=tck@213-202-140-102.bas502.dsl.esat.net] has joined #launchpad === mayeco [n=mayeco@201.218.105.31] has joined #launchpad [01:27] ==> We're going to be down for a bit longer that 1 hour. Sorry for the inconvenience. [01:28] Rinchen: topic please? :-) [01:28] What's being cherrypicked today? [01:28] shesh, now what am I going to do? like real life stuff?!?! ;-) [01:29] LaserJock: :-P [01:29] LaserJock: bzr diff etc still works with LP. === ..[topic/#launchpad:Rinchen] : Launchpad is down for maintenance. Please stand by. :-) [01:29] no worries. [01:30] cheers [01:36] We were applying some final bug fixes today and found some results we didn't like in our QA check. We're addressing them now, hence the delay. [01:36] Rinchen, actually, PostgreSQL didn't like our results either. :) [01:37] man this has got to be a friday [01:37] I was trying to be subtle. === Rinchen smiles. [01:37] no other days could be like this [01:37] bad news from morning till evening === yeager [n=yeager@ubuntu/member/yeager] has joined #launchpad [01:37] DB constraints wanted adjusting? [01:37] At least we know our QA process works. :-) [01:37] heh [01:38] Fujitsu, actually, a broken trigger being tickled by some bad data in a bug in the 2000s range [01:38] not sure which bug yet [01:38] Ah, nice. [01:39] nice, as in, the sound it makes when you bite on a olive seed and your teeth goes crack! [01:39] or pip [01:39] your tooth. [01:39] obviously I have had way too much lsd tonight [01:39] Quite obviously. [01:41] New bug: #141614 in launchpad "Launchpad pages not displaying properly in Internet Explorer 7 as of 9/21" [Undecided,New] https://launchpad.net/bugs/141614 [01:41] We're up again? === EdwinGrubbs [n=edwin@cpe-66-25-92-150.satx.res.rr.com] has joined #launchpad [01:42] New bug: #141597 in malone "bug janitor expires duplicate bug reports" [Medium,Confirmed] https://launchpad.net/bugs/141597 [01:42] New bug: #141604 in malone "Expiration janitor should put an expiration notice on bug page" [Undecided,Confirmed] https://launchpad.net/bugs/141604 [01:42] it's ubotu catching up [01:42] although the LP page is up at the moment [01:42] It is, yes. === james_w [i=jw2328@jameswestby.net] has joined #launchpad [01:43] Not exactly fast, but it works. === Rinchen walks over the guys huddled around the server to see if he can get a status report. [01:45] ==> We're trying to identify and fix the bad data. If we can do it in the 15-20 minutes we may bring LP down again for a short pause. Stay tuned. === ..[topic/#launchpad:Rinchen] : Launchpad may go down at 00:00 UTC for further maintenance. Please stand by. :-) [01:50] I need to step away for an hour or so. Kiko will provide you all with further updates. [01:51] Thanks Rinchen. [01:51] We've identified the bad bug data. :-) [01:51] yes [01:51] it's good ole Bug #1567 [01:51] Launchpad bug 1567 in hwdb-client "Ubuntu Device Database" [Medium,Invalid] https://launchpad.net/bugs/1567 - Assigned to Oliver Grawert (ogra) === Fujitsu must have cursed it when he rejected a task. === intellectronica [n=intellec@host81-153-175-29.range81-153.btcentralplus.com] has joined #launchpad [01:55] Fujitsu, I noticed that. don't think I didn't. I saw your evil touch! [01:55] Heh. [02:07] Fujitsu, your evil touch bled all the way to bug 1566. [02:07] Launchpad bug 1566 in rosetta "Duplicated msgids and wrong exports prevents some .mo exports" [High,Fix released] https://launchpad.net/bugs/1566 - Assigned to Carlos Perell Marn (carlos) === sinzui [n=sinzui@pool-70-17-91-59.res.east.verizon.net] has left #launchpad [] === sinzui [n=sinzui@pool-70-17-91-59.res.east.verizon.net] has joined #launchpad === Fujitsu glares evilly at a few more bugs. === Philip5 [n=Philip@c83-253-56-100.bredband.comhem.se] has joined #launchpad [02:09] I found a bug two days ago that had a 6 meg description. I couldn't change the status because the query to get all the bug took too long. [02:10] sinzui, yeah, we fixed that too [02:11] kiko: pity, that would have killed the expiration job [02:11] one step at a time === merriam [n=merriam@85-211-21-215.dyn.gotadsl.co.uk] has joined #launchpad [02:20] New bug: #141627 in launchpad "The fti update trigger blows up for bug 1566." [Undecided,New] https://launchpad.net/bugs/141627 [02:24] Fujitsu, see! [02:25] That syntax does look rather valid. [02:37] holy fudge janitor is working its butt off [02:37] i think ill save them for tomorrow when i have time to decide what stays and what can go [02:37] 'bout time it earns its keep [02:37] hexmode: once bugs are worked out it will ;) === Igorot [n=dax@ubuntu/member/knightlust] has joined #launchpad [02:45] kiko: did someone change janitor to only mark dupes and close? [02:45] gnomefreak, no, it's not running any longer. you're getting bugmail that was sent out. [02:46] gnomefreak: No, it just turns out that a lot of what was expired were dupes [02:46] ah ok cool === ..[topic/#launchpad:Rinchen] : Launchpad may go down between 01:00 - 02:00 UTC for further maintenance. Please stand by. :-) === gouki_ [n=gouki@ubuntu/member/gouki] has joined #launchpad === gouki_ is now known as gouki === yeager [n=yeager@ubuntu/member/yeager] has joined #launchpad === `23meg [n=m@ubuntu/member/-23meg] has joined #launchpad [03:43] okay. [03:43] we're doing it! [03:43] LP going down for maintenance in 15 minutes for 1 hour [03:43] Um, yay. === ..[topic/#launchpad:Rinchen] : Launchpad may go down between 02:00 - 03:00 UTC for further maintenance. Please stand by. :-) [03:47] Is this the FTI trigger fixing, or something else? [03:47] mthaddon: It seems to be down now? [03:47] Well, bazaar.launchpad.net is refusing SSH connections. [03:47] Haha. [03:48] So hopefully that's intended downtime. :p [03:48] Odd_Bloke, yeah, that gets stopped as part of the rollout - sorry - by the timing I meant the web frontend for Launchpad [03:48] mthaddon: OK, no worries. [03:48] Just wanted to make sure it was expected. :p [03:48] Odd_Bloke, thx for bearing with us [03:48] How many more downtime windows are we having today? [03:49] Fujitsu, with luck, this will be the last - nasty DB issue caught us last time, but we believe we have it resolved now === sjohannes [n=js@60-242-10-232.static.tpgi.com.au] has joined #launchpad [03:54] hmm, late nights in the DC [04:02] indeed LaserJock === tck [n=tck@213-202-140-102.bas502.dsl.esat.net] has joined #launchpad === johanbr [n=j@blk-137-105-82.eastlink.ca] has joined #launchpad [04:15] "[Expired for Ubuntu because there has been no activity for 60 days.] " Is this some kind of joke? [04:16] johanbr: No, that's a feature introduced in Launchpad 1.1.9. [04:16] Fujitsu, well, with some caveats. [04:16] :) [04:16] Heh heh heh. [04:17] johanbr, there's been a lot of discussion here already, it will go on-list on monday [04:17] Seems to be a feature from the "if I don't acknowledge it, it doesn't exist" school of bug management. [04:17] johanbr, it was meant to only touch inactive bugs; we'll fix them up on monday. [04:17] johanbr: It only happens if the bug had status Incomplete. [04:18] johanbr: Will these rules fix your bug: [04:18] -- Restore expired bugs to INCOMPETE (17) status [04:18] -- when any of the following are true: [04:18] -- A. The bug is a duplicate. [04:18] -- B. The bugtask has a milestone. [04:18] -- C. The bug has has a valid upstream bugtask. [04:18] -- D. The date_last_message < 60 days old. === kiko high fives sinzui [04:19] sinzui: No, they won't. It's not uncommon for bugs to go uncommented on for longer than sixty days. [04:19] I think many of mine aren't covered by that [04:19] but kiko is trying to convince me my bug triaging sucks ;-p [04:20] With rules like that, I am unlikely to waste my time reporting any more bugs. [04:20] johanbr, in the Incomplete status? [04:20] johanbr, can you give me an example where the bug should be Incomplete and still untouched for 60 days? [04:20] LaserJock, if you have an example too, it'll help us tune. [04:21] johanbr: In addition to those new restrictions, the current ones are unassigned, INCOMPETE for 60 day without a bugwatch [04:21] kiko: well, I have quite a few bugs that are olde than 60days that I don't want to close [04:22] LaserJock, incomplete and unassigned and with no activity? [04:22] yep [04:22] and with no upstream bug? [04:22] I don't assign, I don't do upstream [04:22] I just fix when I get the chance [04:23] kiko: It wasn't clear from what sinzui wrote that the rules only apply to Incomplete bugs. In any case, there certainly are such bugs too. Here's one that I reported (but that seemed to later have been fixed manually): https://bugs.launchpad.net/bugs/61009 [04:23] Launchpad bug 61009 in alsa-driver "No alsa sound through Motorola V300 phone" [Wishlist,Confirmed] [04:23] LaserJock, /incomplete/? that doesn't make sense [04:23] kiko: well, I left it in incomplete because I wanted more info at the time [04:23] you're thinking that I'd come back to it and mark it "Confirmed" within 60 days, right? [04:23] Another example: https://bugs.launchpad.net/bugs/52410 [04:23] Launchpad bug 52410 in alsa-lib "Choppy sound/crash in ekiga" [Low,Invalid] [04:24] johanbr, that bug is certainly either Confirmed or New, it had no business being Incomplete. === ..[topic/#launchpad:Rinchen] : https://launchpad.net | Next developer meeting: Thu 27 Sep 2007, 1400UTC | List: launchpad-users@lists.canonical.com | Support: https://answers.launchpad.net/launchpad | Help: https://help.launchpad.net | Channel logs: http://tinyurl.com/72w39 [04:24] johanbr: That bug was INCOMPLETE. should it have been CONFIRMED to begin with? DO I misunderstand that status os this bug [04:25] New bug: #141637 in launchpad "Updating FTI on one of our bugs causes PostgreSQL to SEGV" [Critical,New] https://launchpad.net/bugs/141637 [04:26] kiko: my concern is that this change seems to depend on the statuses being used correctly, right? [04:26] kiko,sinzui: Crimsun (Daniel Chen) claims that "Incomplete" is the correct status for "hasn't been fixed upstream yet". [04:26] johanbr, well, at least that confusion will be cleared up now. I had no idea [04:27] johanbr, that's not correct, though. the correct status would be Confirmed. [04:27] a special pending-upstream mechanism is something we have considered [04:27] I'm not sure how it might work though [04:28] anyway, let me get to the pizza shop before they close for the night [04:28] I'll bbiab [04:28] 23:28, wow [04:28] 18h of work [04:28] LaserJock: That is the assumption. This has been an awful experience to see the variation in how people use Launchpad. Tee goal is to save the contributors time tracking down delinquent bug reports. [04:28] yep [04:29] that's my concern [04:32] the *idea* is nice [04:32] but if the implementation depends on people doing things they aren't then you're gonna get problems [04:33] for the work I do probably moving the status back to what it was before Incomplete would be the easiest [04:34] LaserJock: I'm preparing the restoration script now. Well vet the rules over the next 3 weeks to get this right. [04:35] well, I think mostly the rules you've got going now will work for most people [04:35] but it is going to force to use Incomplete better [04:35] LaserJock: I you fix your statuses if you wish, but If you can enjoy the weekend and contribute on other things do it. I'll fix this. [04:36] sinzui: I'm not complaining, it forces me to retriage my bugs :-) [04:36] which apparently I haven't done for 60 days :-) [04:36] So with the new version release can we delete from PPA yet, or is that in the next one? [04:37] LaserJock: Indeed. Tags are the only flexible part of the Launchpad bugtracking system. Everything else does have a strict meaning. [04:38] tonyyarusso: next one [04:38] LaserJock: ah, ok - around a month-ish between, right? [04:38] yep [04:39] Okay [04:39] just keep uploading over the top for now :-) [04:39] tonyyarusso, with this version your packages will get removed when new packages come in. manual deletion is in the next cycle. [04:40] kiko: ah, cool. So now here's the kicker - if I have previous ones, would an upload that superceded all kill all of them, or only the immediately previous one? [04:40] it would really be nice you LP had a doc on how *you* expect us to use the statuses [04:40] *nice if [04:41] and probably other things [04:41] but in the abscence of any real guidlines, best practices, or policies it's not surprising that people just make it up as they go [04:42] tonyyarusso, all of them. [04:42] Yeah - I've still been pondering what the most intelligent versioning scheme is [04:43] kiko: cool [04:43] tonyyarusso, in fact, you don't need to upload -- process-death-row should delete them regardless of an upload. [04:43] LaserJock, you're absolutely right. [04:43] kiko: cron job? [04:44] tonyyarusso, yeah. I think cprov-out meant to run it manually today but I'm still waiting for the results [04:44] kiko: nifty === kiko is now known as kiko-zzz [04:54] tonyyarusso: process-death-row will run again 3 AM BST for PPAs. What is exactly your problem ? === sjohannes [n=js@60-242-10-232.static.tpgi.com.au] has left #launchpad [] [04:54] cprov-out: Not exactly a problem, but I have some old versions that could be cleaned out - just wonder when they would by and such [04:56] tonyyarusso: I've run it manually 6 hours ago, all the obsolete versions should be already removed from pool. [04:58] hmmmm. [04:59] tonyyarusso: as you can see in https://edge.launchpad.net/~tonyyarusso/+archive (*removed* sources) [04:59] cprov-out, maybe we shouldn't list removed sources there, eh? [05:00] sinzui: you happen to know how many bugs total Janitor closed today? [05:00] LaserJock, 2000+ [05:00] O.O [05:00] sinzui knows the exact number. [05:00] *blinks* [05:00] kiko-zzz: maybe ... not by default. [05:00] LaserJock: No, I don't since the number changes daily. I have a close number in hand [05:01] cprov-out, I don't think it makes sense to list removed packages there, ever. [05:01] cprov-out, the fact that the package is removed is much less relevant to the PPA owner [05:01] it's history [05:01] hmm, would it be possible to have a "PPA History" page? [05:01] LaserJock: 2894 was the predicted number to close a few days ago. [05:01] cprov-out: You're right... I didn't look that closely just now (just got home; remembered question from earlier) [05:02] sinzui: k, that's not too bad === l_ [n=l_@mix.mmjgroup.com] has joined #launchpad [05:02] Yeah, I'd like it available through some sort of history, or even just another section lower on the page, but yeah, I got confused. [05:03] kiko-zzz: yes, maybe presenting it in some other page, as the new sourcepackage page do ... (I should have not resurrect this subject this late in the night ...) [05:03] heh [05:03] zzz === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad === Hobbsee waves === mayeco [n=mayeco@201.218.105.31] has joined #launchpad === `23meg [n=m@ubuntu/member/-23meg] has joined #launchpad === tarheelcoxn waves to Hobbsee [05:57] hiya tarheelcoxn [05:57] :) [05:57] how goes? [05:57] it's going. although my car isnt. [05:58] and i've jus tnoticed that the auto expiry mails dont have a specific header on them, to filter by. [06:00] sinzui: do you know how many total open bugs there are total? [06:00] Hobbsee: yeah, but it's got very predictable body text [06:00] LaserJock: No I do not [06:00] LaserJock: this is true === statik [n=emurphy@189.66.188.72.cfl.res.rr.com] has joined #launchpad === sinzui is now known as sinzui-zzz === jelmer_ [n=jelmer@h66-201-205-140.gtconnect.net] has joined #launchpad [07:21] New bug: #141652 in launchpad "Active bugs get expired anyway (activity two days ago)" [Undecided,New] https://launchpad.net/bugs/141652 [07:22] I'm going to bed, but based on that bug ^^^ I'm going to go through all the expired mail I got pretty carefully. === EtAlors [n=bad@gob75-7-82-247-115-200.fbx.proxad.net] has joined #launchpad === silwol [n=silwol@d91-128-236-59.cust.tele2.at] has joined #launchpad === Igorot [n=dax@ubuntu/member/knightlust] has joined #launchpad === Igorot [n=dax@ubuntu/member/knightlust] has left #launchpad [] === Dhakka [n=patildha@221.135.178.210] has joined #launchpad [08:06] !list [08:06] I am ubotu, all-knowing infobot. You can browse my brain at http://ubotu.ubuntu-nl.org/factoids.cgi - Usage info: http://wiki.ubuntu.com/UbuntuBots === james_w [i=jw2328@jameswestby.net] has left #launchpad [] === dorto [n=dorto@220.226.151.33] has joined #launchpad === hexmode [n=mah@24.115.83.248.res-cmts.eph.ptd.net] has left #launchpad [] === Starting logfile irclogs/launchpad.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #launchpad === Topic for #launchpad: https://launchpad.net | Next developer meeting: Thu 27 Sep 2007, 1400UTC | List: launchpad-users@lists.canonical.com | Support: https://answers.launchpad.net/launchpad | Help: https://help.launchpad.net | Channel logs: http://tinyurl.com/72w39 === Topic (#launchpad): set by Rinchen at Sat Sep 22 04:24:21 2007 [10:17] let's see if it works now [10:21] Fujitsu: Accepted ssmtp 2.61-11~mz~ppa4 (source) [10:21] Fujitsu: thanks! === Spads_ [n=spacehob@host-87-74-19-12.bulldogdsl.com] has joined #launchpad === Spads_ [n=spacehob@host-87-74-19-12.bulldogdsl.com] has joined #launchpad [10:28] zasf: No problem. === Spads [n=spacehob@unaffiliated/spads] has joined #launchpad [10:35] New bug: #143972 in launchpad "Package description maintenance" [Undecided,New] https://launchpad.net/bugs/143972 === ubuntulog [i=ubuntulo@trider-g7.fabbione.net] has joined #launchpad === Topic for #launchpad: https://launchpad.net | Next developer meeting: Thu 27 Sep 2007, 1400UTC | List: launchpad-users@lists.canonical.com | Support: https://answers.launchpad.net/launchpad | Help: https://help.launchpad.net | Channel logs: http://tinyurl.com/72w39 === Topic (#launchpad): set by Rinchen at Sat Sep 22 04:24:21 2007 === #launchpad [freenode-info] help freenode weed out clonebots, please register your IRC nick and auto-identify: http://freenode.net/faq.shtml#nicksetup === meduxa [n=agustin@199.Red-83-36-56.staticIP.rima-tde.net] has joined #launchpad === effie_jayx [n=valles@ubuntu/member/effie-jayx] has joined #launchpad === phanatic [n=phanatic@dsl54028230.pool.t-online.hu] has joined #launchpad === Balaams_Miracle [n=balaam@g175073.upc-g.chello.nl] has joined #launchpad === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad === leonel [n=leonel@189.155.178.19] has joined #launchpad [02:05] There are packages that are hard to backport to dapper or feisty can I have my created / backported packages in PPA ? [02:05] Not taking in count the dependencies [02:06] I mean for clamav I only need clamav in dapper and no other package [02:06] can I have the newer clamav package created by me or someone else in ppa for dapper and feisty ? [02:08] leonel: clamav for dapper has clamav-team working on it [02:09] and bug already open [02:09] Kmos: yes we are [02:09] leonel: you can create your own, yes. [02:09] thanks Hobbsee [02:09] leonel: you can create for any supported ubuntu release. [02:09] leonel: stick the release name (ie, dapper), in debian/changelog before building. === Hobbsee thought clamav for dapper was done - or there was a newer version... [02:10] Hobbsee: dapper~ppa [02:10] leonel: no, dapper. dapper~ppa is not an ubuntu release. [02:10] Hobbsee: ok thank you [02:10] leonel: eg network-manager (0.6.5-0ubuntu10) UNRELEASED; urgency=low [02:11] leonel: there, the version number is in the brackets, and the UNRELEASED is the release name. [02:11] Hobbsee: so replace UNRELEASED to dapper ? [02:11] leonel: yes [02:11] there is a new clamav [02:11] leonel: you'll need to version the feisty and dapper ones separately, btw. [02:12] ok 2 packages [02:12] great [02:12] leonel: so i'd suggest use gutsyversion~feisty~ppa1, or something [02:12] Hobbsee: ok === effie_jayx [n=valles@ubuntu/member/effie-jayx] has joined #launchpad === Gwaihir [n=Gwaihir@ubuntu/member/gwaihir] has joined #launchpad === asac [n=asac@debian/developer/asac] has joined #launchpad [03:21] gah. damned launchpad. [03:21] hiya asac [03:22] okay, so how am i supposed to log in to the wiki section of launchpad? [03:22] oh, here we go. [03:22] if one goes form the main page, it will let you login. [03:23] oh yay, i cant edit the damned thing anyway. [03:23] hi Hobbsee [03:24] Hobbsee: does NM still work for you? [03:24] asac: wpasupplicant downgraded WFM, at least at thi spoint. [03:24] yeah [03:24] any idea what knetworkmanager puts into its rc file? [03:24] (i remeber that you had to purge that once) === zakame [i=zakame@ubuntu/member/zakame] has joined #launchpad [03:27] asac: yeah, i'll pastebin. [03:28] asac: http://pastebin.ca/706985 [03:28] asac: it usually has more, iirc - that's because i've purged it, and havent connected to other networks since then === bootle [n=bootle@dslb-088-072-035-073.pools.arcor-ip.net] has joined #launchpad [03:30] Hobbsee: is that $HOME/.knetworkmanagerrc ? [03:30] asac: /home/sarah/.kde/share/config/knetworkmanagerrc [03:31] Hi folks, sorry if thats its faq, but I haven't found any right solution yet. I want to move a project to launchpad service. The project is hosted on sourceforge (svn). Is there a way to move the trunk of the project to launchpad without loosing the current commit history? [03:51] New bug: #144027 in launchpad "ppa amd64 build fails due to time mismatch" [Undecided,New] https://launchpad.net/bugs/144027 [04:01] bootle: I think this page explains how to do that https://help.launchpad.net/FeatureHighlights/BranchImports [04:03] stdin, thanks I read it now. === hexmode [n=mah@24.115.83.248.res-cmts.eph.ptd.net] has joined #launchpad === PriceChild [n=pricechi@ubuntu/member/pdpc.supporter.student.PriceChild] has joined #launchpad === _gpg_ [n=_gpg_@82.64.92.57] has joined #launchpad [04:18] <_gpg_> hello [04:19] hello, _gpg_ [04:22] <_gpg_> is launchpad written from scrach or using any existing technology (zope ..) [04:24] It uses Zope3 === Kmos [n=gothicx@unaffiliated/kmos] has joined #launchpad [04:27] <_gpg_> ty [04:36] New bug: #144038 in malone "launchpad incorrectly closes bugs while users are waiting on dev response" [Undecided,New] https://launchpad.net/bugs/144038 === jelmer_ [n=jelmer@h66-201-205-140.gtconnect.net] has joined #launchpad === alex-weej [n=alex@cpc2-darl3-0-0-cust237.midd.cable.ntl.com] has joined #launchpad [04:45] uh :/ [04:45] launchpad "janitor" is closing lots of bugs that are still around it's just no-one cares to fix them [04:45] this is annoying. [04:51] It's also closing ones that are actively being worked. === nealmcb [n=neal@wikipedia/nealmcb] has left #launchpad [] === bigon [n=bigon@ubuntu/member/bigon] has joined #launchpad [05:02] hi, could some buildd admin have a look at https://launchpad.net/~telepathy/+archive/+build/397159 ? I think there is a bug in ppa or something [05:04] that's probably a timezone issue? [05:07] laga: maybe but the build was successful on i386 [05:08] maybe that build happened later [05:09] only a few minutes [05:09] is it possible to schedule a new build attempt? [05:10] bigon: that's bug #144038 [05:10] Launchpad bug 144038 in malone "launchpad incorrectly closes bugs while users are waiting on dev response (dup-of: 141652)" [Undecided,New] https://launchpad.net/bugs/144038 [05:10] Launchpad bug 141652 in launchpad "Active bugs get expired anyway (activity two days ago)" [Undecided,Confirmed] https://launchpad.net/bugs/141652 [05:11] erm, no it isn't :p [05:11] bug #144027 [05:11] Launchpad bug 144027 in launchpad "ppa amd64 build fails due to time mismatch" [Undecided,Confirmed] https://launchpad.net/bugs/144027 [05:12] thx === intellectronica [n=intellec@host81-153-175-29.range81-153.btcentralplus.com] has left #launchpad [] [05:17] and about a new build attempt? [05:19] you see the retry build link on the left ? === bigon hides [05:23] stdin: thx [05:23] bigon: By definition that's a failure of U/I design. You should file a bug. [05:24] it's true, most people (including myself) don't see it until their told it's there [05:24] bigon: There: File the bug and stdin will confirm it. [05:25] yep [05:25] I think this was mentioned on the mailinglist too, I'll look that post up... [05:32] https://bugs.edge.launchpad.net/launchpad/+bug/144057 [05:32] Launchpad bug 144057 in launchpad "Rebuild link not easily findable on ppa build log page" [Undecided,New] [05:40] New bug: #144057 in launchpad "Retry build link not easily findable on ppa build log page" [Undecided,Confirmed] https://launchpad.net/bugs/144057 [05:45] New bug: #144062 in launchpad-bazaar "The list of 'Recent revisions' should include the 'author' when appropriate" [Undecided,New] https://launchpad.net/bugs/144062 [05:51] Would someone please help me figure out how to link Bug #141546 to the upstream bug. [05:51] Launchpad bug 141546 in libnet-dns-perl "make_query_packet() IP address detection broken" [Low,Confirmed] https://launchpad.net/bugs/141546 [05:55] New bug: #144066 in malone "launchpad usability problems lose bugs" [Undecided,New] https://launchpad.net/bugs/144066 [05:58] ScottK: the package needs to be registered in launchpad. then click on 'Also affects', and update the package info. Then you'll be able to intro the url [05:58] Why do I have to do that? [05:58] Before I could just put the URL in [05:59] Gah. [05:59] ScottK: you shouldnt need to register [05:59] gnomefreak: I'd appreciate it if you can help me figure this out. [05:59] only for branching or making a prooject [05:59] It used to be easy. [05:59] ScottK: you have link to upstream bug? [06:00] Yes. It's in the bug I mentioned above [06:00] I just put it in the body since I couldn't link it. [06:00] wtf happened [06:00] ok let me look at this a min [06:02] gnomefreak: I believe that wtf happened is they improved LP, but I'd like to get confirmation of that. [06:02] but we lost anyway of using upstream now [06:02] Unless upstream is in LP, yes. [06:02] since there shouldnt be a need to register an upstream project since upstream doesnt use LP [06:02] Agreed. [06:02] doesnt/may not [06:03] ScottK: talk to kiki or one of the LP admins this was with 1.1.9 release but first time i saw it [06:03] There were related changes in the 1.1.9 release. I'll file a bug. [06:04] trying something else [06:04] OK. I'll wait. [06:04] ha [06:04] i found it [06:04] OK. How do I do it. [06:04] ? [06:05] its added into distribution/package [06:05] not project anymore [06:05] Ah. [06:05] I'll look. [06:05] but now do i need to select a project? [06:05] or just paste url [06:05] ScottK: please let me know what you find out :) [06:06] That won't help you as you have to pick a distro that's on the list. [06:06] I tried that one already. [06:06] Thanks for looking. [06:06] sorry i would file bug than === Igobot [n=dax@122.2.251.210] has joined #launchpad [06:10] gnomefreak: Would you please confirm Bug #144072 [06:10] Launchpad bug 144072 in launchpad "No way to link to upstream bug if it's not registered as a project in LP" [Undecided,New] https://launchpad.net/bugs/144072 [06:10] yes one sec [06:12] ScottK: done [06:12] gnomefreak: Thanks. [06:12] np === Igorot [n=dax@ubuntu/member/knightlust] has left #launchpad [] [06:21] New bug: #144072 in launchpad "No way to link to upstream bug if it's not registered as a project in LP" [Undecided,Confirmed] https://launchpad.net/bugs/144072 [06:22] ScottK: any clue how to make a branch using bzr+ssh [06:22] gnomefreak: No. I've almost entirely managed to avoid bzr. When I have to use it, I use it like it's svn. [06:23] well it keep complaing to me no such file or dir lol [06:23] bzr branch bzr+ssh://codebrowse.lp.net... iirc [06:24] ah i didnt see branch in the instructions [06:24] gnomefreak: Are you trying to branch from somewhere on Launchpad, or create a new branch in LP? [06:24] create a branch on LP from a package [06:25] Is it already versioned with Bazaar? [06:25] bzr: ERROR: Not a branch: /home/gnomefreak/nspluginwrapper/nspluginwrapper-0.9.91.4/ [06:26] bzr push bzr+ssh://gnomefreak@bazaar.launchpad.net/~mozillateam/nspluginwrapper/ubuntu-0.9.91.x [06:26] thats command and output. it should already be registered as it is a package in gutsy [06:27] gnomefreak: You'll want to 'bzr init', 'bzr add', 'bzr commit -m "Initial import."' before pushing it. [06:29] thats more steps than it used to be [06:29] by like 4 [06:29] maybe 2 [06:30] but ty it is pushing === kiko [n=kiko@canonical/launchpad/pdpc.supporter.active.kiko] has joined #launchpad [06:38] gnomefreak: add a " ." at the end. [06:38] >? [06:39] gnomefreak: oh, right, you're pushing now === laga [n=laga@mythwiki.de] has left #launchpad [] [06:50] oh urgh. the janitor has caused the influx of mail. [06:51] ScottK: I've moved 144072 to malone [06:52] pochu, ScottK: that's a dupe. we'll make registering a product possible as part of adding a bugwatch for 1.1.10. [06:59] kiko: LP has screwed up. [07:00] kiko: i should be able to see https://edge.launchpad.net/bugs/141378 and cant. please fix, kthxbye :) [07:02] kiko: looks like subscribers are utterly screwed - the bug contacts are not listed as subscribers anymore. [07:02] let alone anyone in ~ubuntu-dev from being able to see it. === Ba7eBeK [n=Ba7eBeK@bzq-79-179-9-170.red.bezeqint.net] has joined #launchpad === mayeco [n=mayeco@mayeco-kubuntu.cpe.cableonda.net] has joined #launchpad [07:06] kiko: in future, please ensure that you do *not* release on a friday, particularly around ubuntu tribes, as there's no one around to clean up any of the mess from the new launchpad. === Hobbsee now cannot grab security-related bugs for the gutsy beta, which she knows have been filed, as she cant see them, unless the filer happens to go and manually subscribe her. === Hobbsee cant see any private bugs either, for the same reason. [07:12] kiko: Registering the product is completely infeasible for the thousands of packages in Universe. I just want to be able to put the URL in. [07:12] ScottK: i suspect for anything non-critical, you'd better bug people during the week. [07:12] Hobbsee: I was responding to the comment above. It's in the bug I filed [07:12] ah === pochu [n=emilio@95.Red-83-32-161.dynamicIP.rima-tde.net] has joined #launchpad === tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net] has joined #launchpad === PriceChild [n=pricechi@ubuntu/member/pdpc.supporter.student.PriceChild] has joined #launchpad === PriceChild [n=pricechi@ubuntu/member/pdpc.supporter.student.PriceChild] has joined #launchpad === tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net] has joined #launchpad === u-foka [n=u-foka@dsl51B6B3B0.pool.t-online.hu] has joined #launchpad [08:09] Hy! Please help my, because I can't register:S [08:09] i tried with two different mail-s but neither of them work :S [08:10] anybody here??? [08:16]