[14:56] <fungi> if any launchpad admins are on hand, you've got someone leveraging your openid system to try and exploit cross-site scripting holes in systems they're authenticating into... openid url is https://login.launchpad.net/+id/DYhTLTE and the e-mail address that pulled in is nestor.aglobo@yahoo.com
[14:58] <fungi> i tried to map that back to an lp account page with a launchpad.people.getByOpenIDIdentifier() call, but it's not returning a match
[15:22] <saiarcot895> Is the package upload portion of launchpad down or something?
[15:35] <martix> Best regards!
[15:35] <martix> Is it possible to upload a metapackage code to launchpad?
[15:36] <saiarcot895> martix: like one package that installs a bunch of different packages?
[15:37] <martix> yes
[15:38] <saiarcot895> martix: Sure. The list of other packages should be listed in the Depends section of debian/control, and I think you just need to create an empty package install folder in debian/rules
[15:39] <saiarcot895> martix: there is a source package here, right?
[15:40] <martix> I'll back in five...sorry for that
[15:51] <martix> I'm back...
[15:52] <martix> I'm following: askubuntu.com/questions/33413
[15:52] <martix> I upload all files but laucnhpad doen't compile it...
[15:56] <martix> Is there a way from a .deb package -in this case a empty one, only with control- to obtain the sources files needed to be upload to launchpad?
[15:56] <martix> something like decompiling...
[15:56] <teward> martix, as an FYI, that was written back in 2011...
[15:57] <teward> You may also want to look at this: If you wish to also create a source package, the --full option can be passed to equivs-build, e.g. equivs-build --full ns-control. This will use debuild & also create .dsc & .tar.gz files.
[15:57] <teward> then the rest of the answer on that
[15:57] <teward> (that was my question btw :P)
[15:57] <martix> yes... I did it, with no compiling results
[15:58] <saiarcot895> martix: Can you post a link to the build log on Launchpad?
[15:59] <teward> or a link to the PPA if it's not in a private group's PPA.
[15:59] <teward> (because buildlogs are kinda easy to find :P)
[15:59] <martix> http://bazaar.launchpad.net/~delldor/+junk/metalibreofficedd/files
[16:00] <martix> that's
[16:00] <teward> ahh
[16:00] <teward> you uploaded to BZR
[16:00] <teward> not a PPA
[16:00] <martix> ????
[16:01] <saiarcot895> You need to use dput to upload to a PPA
[16:01] <teward> ^
[16:01] <teward> https://help.launchpad.net/Packaging/PPA/Uploading
[16:01] <teward> that page is relevant
[16:01] <teward> assuming you've followed the question/answer
[16:01] <martix> ...ups
[16:01] <martix> lol
[16:02] <martix> It's for reading very old aswered questions
[16:02] <teward> martix, `bzr` is the VCS (Version Control System) that is used to manage code, but isn't directly going to build a PPA package.  For most things you don't need bzr, but meh.
[16:02] <teward> (especially uploading a source package that you've built and probably don't need to touch again, if it's a metapackage)
[16:03] <martix> I read that it's neccesary upload to bzr and then it will be compiled
[16:04] <martix> https://code.launchpad.net/~delldor/+junk/metalibreofficedd
[16:04] <saiarcot895> martix: nope, unless you want to use recipes, which are useful for builds of changing sources
[16:04] <teward> ^
[16:04] <teward> but for a metapackage it won't be as useful
[16:04] <martix> Exactly!
[16:04] <teward> since the source probably isn't going to be changing
[16:05] <martix> ...only the control file
[16:05] <teward> which you can just rebuild yourself when you change it
[16:05] <teward> martix, i highly doubt you're going to be changing the control file very often
[16:05] <saiarcot895> martix: You can even build locally by running debuild
[16:06] <saiarcot895> to test to make sure it builds before sending to launchpad
[16:06] <teward> ^
[16:06] <jtaylor> apropo recipes, has bug 1273487 chances of getting fixed soon?
[16:07] <martix> Yes...I have a few metapackage that I managed locally... but I want to share It with some friends
[16:29] <teward> DellDor, i suggest you just dput the package into a PPA after you have the source package, that's waht I did.
[16:29] <teward> actually i need to redo that...
[16:35] <DellDor> I'll tray to do that... I'm triying to figurate how to do that... reading https://help.launchpad.net/Packaging/PPA/Uploading
[16:36] <DellDor> in https://help.launchpad.net/Packaging/PPA/Uploading says that we can upload source code
[16:36] <DellDor> not a package. How do you do that?
[16:37] <teward> "source package" means the source code for the package
[16:37] <teward> read the first section: "Once you've built your source package, you need to upload it to Launchpad using the dput tool. "
[16:37] <teward> in the question/answer you were using it gives you steps to produce a source package to upload
[16:38] <teward> `debuild -S` will create the source package, then you upload the source package to the PPA
[16:53] <DellDor> Thanks...I'll test