[00:12] uni4dfx: The policy was set by Ubuntu, so #ubuntu-bugs is the place to discuss it. [00:13] sorry to annoy you here :) [02:11] there is no activity log link in the bug reports now? was this a conscious decision? [02:13] plars: Bug #436818 [02:13] Launchpad bug 436818 in malone "Bug Activity Log no longer linked in 3.0 UI" [Undecided,New] https://launchpad.net/bugs/436818 [02:13] wgrant: ah, thanks [02:32] having difficulty dputting to ppa, getting errno 111 [02:33] bjsnider: Indeed, the FTP server is dead. [02:33] wow, really? [02:33] dead? [02:33] It crashes sometimes. [02:33] that would interfere with the ftp upload, without doubt [02:38] I don't seem to be able to mark private bugs as public anymore [02:38] the "(!)" icon is visible while the page is loading, but then disappears [02:38] mdz: Use !WebKit for now. [02:41] bjsnider: Fixed now. [02:41] wgrant, LP bug or WebKit bug? [02:41] mdz: LP. [02:43] mdz: bug #397457 [02:43] Launchpad bug 397457 in malone "Bug privacy edit icon is not visible in WebKit browsers" [High,Triaged] https://launchpad.net/bugs/397457 [02:56] I cannot figure out how to report bugs in 3.0 [02:56] cyberix: You're looking at https://bugs.launchpad.net/, aren't you? [02:56] Well, I have been bouncing around all over the site [02:57] cyberix: https://launchpad.net/PROJECT wasn't one of the places you ended up? [02:58] I go to https://launchpad.net/ubuntu [02:58] I click on "Report a bug" [02:58] I end up at https://help.ubuntu.com/community/ReportingBugs [02:58] Did you read that page? [02:58] I scimmed it trough [02:58] (this is an Ubuntu-specific thing, nothing to do with LP 3.0) [02:58] translations export are said to be daily, but they're not being. Not even after pushing changes to the po and pot files [02:59] It seems I need to make some software crash so I get to reporting a bug [02:59] cyberix: That page thoroughly describes all methods of filing an Ubuntu bug, in order of preference. [02:59] cyberix: Only one method on that page requires it.... [03:00] also fyi milestone deletion is not working [03:00] I was going to file a [needs-packaging] bug [03:01] I cannot see which category that would fit in [03:01] cyberix: Yes, that is a problem. See the "Filing bugs at Launchpad.net" section. [03:01] Again, this is an Ubuntu policy decision, and not anything to do with the LP 3.0 UI changes. [03:02] So I have to link the bug to some existing package [03:02] interesting [03:03] No. [03:03] Ah, it doesn't say how to avoid it. Omit the '+source/PACKAGENAME/' [03:11] wgrant: I fixed that [03:12] wgrant: Thanks for patience [03:12] cyberix: np [03:46] spm: You around? [03:46] spm: Hopefully not at lunch time on Saturday. [03:46] Er. [03:46] wgrant: maybe you? [03:46] MTecknology: ^^ [03:46] wgrant: can I forward you an interesting email? [03:47] entirely LP related [03:47] MTecknology: If you so desire, and it is not enticing me to increase the size of my body parts. [03:47] wgrant: it's along that line though [03:49] it might just be somebody infected w/ a virus trying to reply to every email addy - which is why I think it might be good for you to be aware of [03:49] MTecknology: You mean it's spam? https://answers.launchpad.net/launchpad/+addquestion if the user hasn't been killed yet. [03:49] I don't see what me being aware does. [03:50] wgrant: I know the user is fine - I just wanted to say something about it - just noticed the part about an update to a deactivated project [04:26] One of my mirrored branches is in a slightly odd state: 1.) It failed to mirror last time -- network issue or somesuch. 2.) It says "Updating branch...", "processing changes" and all. It seems broken branches do that now. 3.) The given repository format is out-of-date. It changed recently. https://code.edge.launchpad.net/~mnordhoff/loggerhead/pretty-url [04:26] Is there anything bug-worthy about that? [04:29] Peng_: 2) is known. [04:29] I think 3) should fix itself when the mirror happens, but I'm not entirely sure. [04:33] wgrant: <3 [04:34] The thing is, the repo format changed before the last mirror. But it was 1.9 -> 2a, so it was affected by that bug that was recently fixed. [04:34] So it might take a while for the format change to sink in. Shrug. [04:35] Pizza! Bye. :P [04:50] wgrant: You wouldn't happen to know if there's anyone around that could look into why suddenly I can't accept packages anymore via the LP UI (suddenly like in the last 10 minute)? [04:50] hi, I'm getting the following error when trying to upload with dput: Connection failed, aborting. Check your network [Errno 111] Connection refused. Any ideas? [04:51] OK, Got one. Maybe kdebase-workspace is just too big. [04:52] ? [04:53] KIAaze: Different conversation, not related to you. [05:02] to be able to upload to my PPA, I just need a GPG key registered at launchpad, no? [05:06] Older builds are deleted from launchpad, right? E.g. a ppa now has "package 1.5", and 3 months before it had "package 1.3", could I somehow get the binaries for package 1.3? [06:02] Am I a terrible person if I use OpenSSH's "ControlMaster" to leave a connection open to LP all the time? [06:15] I can copy packages from the Ubuntu primary archive to my PPA from here: https://launchpad.net/ubuntu/+archive/primary/+copy-packages?field.series_filter=karmic&field.name_filter=PACKAGE_YOU_WANT [06:15] Can I also copy packages from jaunty-proposed or jaunty-backports? [07:19] my rules file's "install" should install into something like $(CURDIR)/debian/tmp/usr/include/ right? [07:19] cause I've just uploaded a source package but I notice that none of the built files get packaged [08:41] is it possible to cancel a build? [09:07] just wanted to say I solved my upload problem: the .dput.cf file was incorrect. Luckily, I had an old backup somewhere. [09:08] it now looks liks this: [launchpad-login] [09:08] fqdn = ppa.launchpad.net [09:08] method = ftp [09:08] incoming = ~launchpad-login/ubuntu [09:08] login = anonymous [09:08] allow_unsigned_uploads = 0 [09:40] pro-rsoft: No, its not possible to cancel a build. [09:41] ok, thanks [09:43] it seems launchpad has changed a lot recently. Is it now impossible to download packages from a PPA directly? [09:44] ah ok [09:44] view package details === doko_ is now known as doko [10:23] Hello. I want to add my project's mailinglist automatically for any bug notifications [10:24] but would like to make sure they don't see my user account's emails about other things [10:24] ? [10:25] dreamcat4: Why do you want the emails to go to the mailing list? I find it's generally a better idea to let people subscribe themselves. [10:25] because it's where we discuss our bugs [10:25] Don't you discuss your bugs on the bug? [10:26] we just want others to see a new bug come in (who aren't on launchpad but subscribe to highload-php-en mailinglist) [10:27] otherwise they generally wouldn't see it [10:27] Ah, so this isn't a Launchpad mailing list? [10:27] we aren't 100% launchpad [10:27] it's a google group + nginx forum [10:27] I see. [10:27] (and is well established) [10:28] Is the mailing list the contact address for a team? [10:28] (so i can't go around just asking everyone to get a launchpad account) [10:28] i dont know but ill go & check right now [10:29] its not yet been set by the team owner [10:29] https://launchpad.net/~php-fpm [10:30] If it was, an admin of the team could just subscribe the team to all bug notifications. [10:30] that's great. thank you [10:31] (at https://launchpad.net/php-fpm/+subscribe) === sayakb_ is now known as sayakb [10:38] have now emailed the group admin with these instructions, thank you [10:38] bye [14:28] how to force dput to upload my orig.tar.gz? it doesn't, and lp complains about that [14:28] pro-rsoft, which error do you get? [14:29] I don't see the point in 'forcing' to dput a orig. file [14:29] pro-rsoft, if you did things properly you should see it in your .changes file, [14:30] Rejected: [14:30] Unable to find artoolkit_2.72.1+20070927.orig.tar.gz in upload or distribution. [14:30] Files specified in DSC are broken or missing, skipping package unpack verification. [14:30] pro-rsoft, wrong debuild [14:30] hm, what should I do to fix it then? [14:31] #ubuntu-motu is your channel now :) [14:31] pro-rsoft: Give the '-sa' option to debuild. [14:31] av`: Not particularly, unless he's trying to upload to the Ubuntu archive. [14:32] ScottK, debuild flags are not the right things to discuss on #launchpad, I guess [14:32] av`: PPA packaging isn't the right thing to discuss on #ubuntu-motu. [14:32] ScottK, debuild is not strictly related to PPA, it's a general packaging tool [14:33] ScottK, I can use debuild also outside PPA [14:33] Right, but #ubuntu-motu isn't the channel for everyone in the work that feels like using Debian packaging tools. [14:33] don't know which channel would be fine for such issues then [14:34] It's a problem that the Launchpad team doesn't support their users then. [14:34] yep [14:35] pro-rsoft, start doing your work on a clean tree and follow wgrant's suggestion [14:35] wgrant, thanks! [14:35] this works [14:48] I read about PPA-pages being split to a user page, and a developer page [14:49] How do I find both of these? === zirpu2 is now known as zirpu [17:13] So, is it just me or does anyone else get pointed to this help page upon clicking the "Report a bug" button from Ubuntu's Launchpad page? https://help.ubuntu.com/community/ReportingBugs [17:20] picklesworth: It's on purpose. [17:22] Ah... I guess reading the help page will help [17:27] https://answers.edge.launchpad.net/ubuntu/+question/83874 [17:27] how did that get marked solved? [17:42] hello [17:43] I want to report a bug in Ubuntu, but the https://bugs.launchpad.net/ubuntu/+filebug redirects me to the Ubuntu Wiki (https://help.ubuntu.com/community/ReportingBugs) [17:52] is this a bug, or this is a feature? [17:53] ulysses__: feature [17:54] ... [17:54] thanks [17:54] ulysses__: Ubuntu has a bug reporting procedure they want followed === sale_ is now known as sale [17:57] so then I should live with them, however it is very strange [17:57] why is that strange? [17:59] before launchpad 3.0 released, I opened the https://bugs.launchpad.net/ubuntu/+filebug page, choosed the right package from the search form, and then wrote the reprt [17:59] * LarstiQ doesn't know ubuntu enough to say what changed [18:00] not an Ubuntu bug, it's in the kubuntu-docs package, some small mistake only:) [18:00] * ulysses__ translates kubuntu-docs to hungarian [18:04] Hello. I've imported my project from github. Later I cloned the branch from launchpad using bzr but now I can't push. I get a "readonly transport" eror. Is this fixable without re-cloning the branch? [18:04] napsy: yes [18:04] how? [18:04] napsy: you're likely trying to push to http://, instead of bzr+ssh:// or sftp:// [18:05] Using saved push location: bzr+ssh://bazaar.launchpad.net/~vcs-imports/gsfm/trunk/ [18:05] this is what bzr push prints out [18:06] I did set up my launchpad username and imported my ssh public key [18:06] ah [18:06] ~vcs-imports is not writable to your user [18:06] hum so what can I do now? [18:07] napsy: you can push to lp:~napsy/gsfm/trunk instead [18:08] cool it works [18:08] But I got this "Created new stacked branch referring to /~vcs-imports/gsfm/trunk" [18:08] what does it mean? [18:08] napsy: do you intend to switch development from github to launchpad? Or should vcs-imports continue pulling across? [18:08] I intend to switch to launchpad [18:09] napsy: that means it hasn't uploaded _all_ revisions to ~napsy/gsfm/trunk, but instead it knows to look in ~vcs-imports/gsfm/trunk for revisions it doesn't have itself [18:09] napsy: sorta like hardlinking [18:09] ok [18:10] how do I now unlink my branch from vcs-imports? [18:11] good question [18:11] * LarstiQ needs to find a webbrowser [18:12] napsy: there is a --no-stack on bzr push I think for creating branches [18:13] hm ok hm [18:14] I have now two branches, one is trunk and the other is luka-napotnik/gsfm/trunk with my latest code [18:14] can I delete the trunk branch and rename the other one? [18:15] napsy: yup [18:18] hum apperently I can't delete trunk [18:20] you should be able to afaik [18:20] but you can at least rename it? [18:22] Yes I can rename the branch. But I want only one official lp:gsfm/trunk branc not "personal" branch [18:24] right [18:24] the official trunk is managed by setting the series focus [18:24] you can select a different branch for it there [19:27] if I /part [19:57] <\u03b5> is there a place to give feedback on lp's new look? [19:58] \u03b5: https://launchpad.net/launchpad/+filebug [19:58] <\u03b5> ah, hm === yofel_ is now known as yofel [21:18] Is keyserver.ubuntu.com dead for anyone else, or is it just me? [21:19] http://downforeveryoneorjustme.com/keyserver.ubuntu.com [21:19] Is downforeveryoneorjustme.com down for everyone else, or is it just me? [21:19] Kidding, great site. [21:20] Anyone here in a position to fix? :) [21:26] Tack: You can use subkeys.pgp.net. Ubuntu keys are mirrored there. [21:27] ScottK: Ah perfect, thanks. === _Extend is now known as Extend [22:20] hi there [22:20] i cant seem to be able to report a bug in an ubuntu package in the new launchpad [22:20] it keeps redirecting me to the wiki [22:20] a moment [22:21] it was changed, so you should open this link: http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect [22:21] replace PACKAGENAME with the name of the package, what you want to report [22:22] ulysses__: thanks [22:22] thats quite a weird practice, though [22:22] yeah, I find it also strange:P [22:23] It will probably help with the amount of incomming bugs [22:23] That might drop to zero :-D [22:23] :D [22:23] SiDi: The idea is to use ubuntu-bug to file bug reports [22:24] and the Kubuntu users?:P [22:24] ulysses__: The same. [22:25] Amaranth: i dont wanna have to use ubuntu-bug or whatever to report a bug in a package for which i propose a patch :) [22:25] SiDi: That is one place it falls over [22:25] and assuming users will report bugs FROM ubuntu is in my opinion quite wrong [22:25] SiDi: We use bugs too much for other workflow [22:26] SiDi: Your situation would be better served by a merge request for a packaging branch, for example [22:26] well, packaging errors / mistakes are for instance definately bugs in packages [22:26] Amaranth: this also means setup a branch, which requires an open port 22 on my network, + proposing a merge for a project using its own git repo... [22:27] that sounds overoveroverkill to me, all i need to do is to send the patch to the package maintainers and to make sure its tracked somewhere on the web [22:27] Yeah, no one actually uses the merge request tool in ubuntu [22:28] When I tried my branches got forgotten until I filed bugs, linked them to the branch, and assigned them to the people I wanted to review them [22:29] i never managed to successfully merge a branch via lp [22:29] its just simpler to manually merge and then commit.... [22:29] and honnestly, there still are valid use cases for attaching patches [22:31] SiDi: Just for curiosity sake, what package are you trying to fix? [22:33] Amaranth: xfce4-power-manager today [22:33] i wrote a patch to allow it to use our custom notification-battery icons for its notification bubbles [22:33] but i sometimes have to file bugs against packages for xfce4-volumed and exaile too [22:34] that change will really not be practical [23:45] Morning [23:45] How long does a langiage translation request usually take ? [23:45] a one time import from a BZR tree [23:45] laanguage* [23:45] language* [23:45] * Fly-Man- blames the drink he's having [23:46] i'm not sure, probably ~a day? [23:47] Is there also a admin here that can delete a branch ? [23:47] https://code.launchpad.net/~vcs-imports/fusionforge/trunk [23:48] I managed to get a working transaction from bzr now ... [23:48] Fly-Man-: yeah, i can delete that [23:49] mwhudson: Thank you :) [23:49] Fly-Man-: it's gone [23:49] :) [23:49] Now that other one is a mirrored one [23:49] would I need to make a new branch for the export of the translations ? [23:54] Hmm [23:54] that's fast :D [23:54] It already found all the files in the branches [23:58] Is there going to be dedicated ppa launchpad bug reports? I maintain alot of packages in my gmpc-trunk team and I'd like to make easier to pass bugs to upstream