[04:30] <Jesse_V> does Launchpad support builds for Debian or Fedora? Is it only specific to Ubuntu?
[04:31] <Jesse_V> nm
[04:31] <wgrant> Jesse_V: PPAs only build for Ubuntu today.
[04:31] <Jesse_V> ok, thanks
[04:32] <wgrant> We'd like to support Debian too, but build resources are at capacity with just Ubunut.
[04:32] <Jesse_V> is there anyway to have Launchpad build for more than one distro, or do I have to change my /debian/changelog file and reupload every time?
[04:32] <Jesse_V> ah ok
[04:32] <Jesse_V> thanks
[04:32] <wgrant> You have to reupload for each release, or copy the source and binaries between releases
[04:33] <wgrant> The latter won't work for everything; you'll need to check if each package needs a rebuild.
[04:33] <Jesse_V> I'm working with my own project that isn't present in Ubuntu/Debian/Linux. It's new software.
[04:34] <Jesse_V> what determines if it can be compatible across distros? It's an OpenGL/C++ project.
[04:35] <Jesse_V> I don't fully understand binary compatibility in Linux
[04:45] <wgrant> Jesse_V: Shared library SONAMEs are a good start, if the libraries you use are fairly sane.
[04:47] <Jesse_V> Glew and Freeglut are the only ones
[04:47] <Jesse_V> what's SONAME?
[04:48] <wgrant> A library version number that indicates ABI compatibility.
[04:50] <Jesse_V> the freeglut3 package has the version number 2.6.0-4ubuntu1 for Quantal.
[04:51] <Jesse_V> so how can I tell ABI compatibility from that information?
[04:51] <Jesse_V> sorry, I'm on a bit of steep learning curve here...
[04:52] <wgrant> The 3 there is usually the soname version.
[04:52] <wgrant> Anything built against freeglut3 should run against any later version of freeglut3.
[04:52] <Jesse_V> oh
[04:52] <wgrant> If they make a change that breaks backwards compatibility, it should become freeglut4.
[04:52] <Jesse_V> yeah I've always wondered about that
[04:52] <Jesse_V> thanks
[04:53] <Jesse_V> I've always thought "why don't they just update the package version?" now I know why
[04:53] <wgrant> Note that building for freeglut3 in saucy and running against quantal's might not work.
[04:53] <wgrant> Because you can add new interfaces without breaking ABI
[04:53] <wgrant> You just can't change old one.
[04:53] <Jesse_V> so what's your recommendation then?
[04:53] <Jesse_V> change /debian/changelog and then reupload?
[04:54] <Jesse_V> wgrant: I've been working on a script to automate the build process for me: https://github.com/Jesse-V/Folding-Atomata/blob/master/src/pushPackage.sh
[04:55] <Jesse_V> so I guess my plan then is to change /debian/changelog and then rerun the script. Would that work?
[04:55] <wgrant> Jesse_V: quantal->saucy has freeglut3 and libglew1.8, so you could upload a package to quantal, copy it to raring and saucy, and it would probably work fine.
[04:56] <Jesse_V> sorry, but how do you copy it without having Launchpad rebuild it?
[04:56] <Jesse_V> I'm trying to understand the order of operations here
[04:57] <wgrant> Jesse_V: Upload to quantal, wait for it to build, then use the "Copy packages" page to copy to raring and saucy.
[04:57] <Jesse_V> ahh
[04:58] <Jesse_V> and if that doesn't work, then I'll resort to uploading for each distro, right?
[04:58] <Jesse_V> wait, can I build for Saucy, even though it's not actually out yet?
[04:59] <wgrant> You can if you want.
[04:59] <wgrant> PPAs support Saucy from day 1 of development.
[04:59] <wgrant> Because they're used for development :)
[04:59] <Jesse_V> ah
[05:03] <Jesse_V> thanks for the help, I think I've got it better figured out now :)
[06:35] <Jesse_V> hi it's me again
[06:36] <Jesse_V> wgrant, maybe you can help me again, or someone else if you're not around
[06:36] <Jesse_V> how can I get Launchpad to verify my digital signature?
[06:36] <Jesse_V> I get:
[06:36] <Jesse_V> gpgv: Signature made Fri Aug 23 06:22:11 2013 UTC using RSA key ID C20BEC80
[06:36] <Jesse_V> gpgv: Can't check signature: public key not found
[06:36] <Jesse_V> in the build log
[06:36] <Jesse_V> how can I get it to import my OpenPGP key?
[06:37] <Jesse_V> and wgrant, I found the "copy package" feature, thanks for pointing that out :)
[06:38] <wgrant> Jesse_V: In the build log? That warning is normal.
[06:38] <Jesse_V> yes ok
[06:38] <Jesse_V> but shouldn't Launchpad verify that?
[06:39] <Jesse_V> it looks like it could, if it had the public key, which it can get because it's on the Ubuntu keyserver
[06:39] <wgrant> It's checked on upload.
[06:39] <Jesse_V> ah ok
[06:39] <wgrant> It's trusted once it's in Launchpad, so the buildds don't have to shuffle around keys etc.
[06:39] <Jesse_V> so no one can upload to my PPA, except the owner of the private key, right?
[06:39] <Jesse_V> ok
[06:40] <wgrant> Right.
[06:43] <Jesse_V> thanks wgrant for the help
[06:44] <Jesse_V> my package is so close to building successfully: it fails right at the "make install" part... :)
[06:44] <wgrant> Heh
[06:44] <wgrant> Nearly there!
[06:44] <Jesse_V> I know
[06:45] <Jesse_V> it makes all of this progress and then dies because I forgot to include certain files in /debian so that they'd be sent to Launchpad. So it's all my fault...
[06:45] <Jesse_V> https://launchpadlibrarian.net/148223219/buildlog_ubuntu-quantal-amd64.foldingatomata_0.4.2_FAILEDTOBUILD.txt.gz
[06:45] <Jesse_V> fixed easily enough though
[06:56] <Jesse_V> YES
[06:57] <Jesse_V> IT BUILT!
[06:57] <Jesse_V> thanks wgrant
[06:57] <Jesse_V> :)
[06:57] <wgrant> Excellent :)
[06:57] <Jesse_V> I'm so happy right now
[11:45] <toabctl> hi
[11:46] <toabctl> is it possible to delete ppa dependencies?
[11:46] <toabctl> I just want to know that before I add a dependency to one of my ppas .
[11:47] <jpds> toabctl: Try it on staging.launchpad.net.
[12:20] <cjohnston> StevenK: wgrant Ursinha, thanks for figuring out the bug that caused status to get upset and taking care of it :-)
[16:02] <Logan_> Is it just me, or is Launchpad not showing the updated versions of Ubuntu packages?
[16:04] <LoganCloud> ^ Still here.
[16:32] <dobey> Logan_: what do you mean it isn't showing them?
[16:38] <qman__work_> Hi, I'm having a problem trying to backport a package (shibboleth 2.5.2) from saucy to precise, and it says "dependency wait": https://launchpad.net/~cs-cracker/+archive/shibboleth-ppa/+build/4895264  What, if anything, do I need to do to move this forward? I used the backportpackage tool to create the build.
[16:47] <dobey> you need the missing dependencies
[16:48] <dobey> as a newer package it likely requires newer versions of some of its dependencies that are also in saucy, but not in precise. or it may require new ones that do not exist at all in precise.
[16:48] <qman__work_> so would I have to backport those separately then?
[16:48] <dobey> yes
[16:49] <qman__work_> ok, thanks, I'll look into that
[18:02] <shadej> hi guys
[18:02] <shadej> new to launchpad
[18:03] <shadej> I want to work on ubuntu localization where to start?
[18:03] <shadej> I have joined the team of my lang now
[18:04] <dobey> the irc channel for your lang, or #ubuntu-i18n would be a better place to get help
[18:59] <Logan_> dobey: Lemme rephrase, because I think I see the actual issue now - the proposed repositories aren't showing up on the source package pages anymore.
[19:01] <Logan_> See, for example: https://launchpad.net/ubuntu/+source/libzrtpcpp
[19:01] <Logan_> It should show 2.3.4-1 in saucy-proposed, but it just shows what's in release.
[19:09] <Munchor> Hi
[19:09] <Munchor> >Licences:
[19:09] <Munchor> Where does Launchpad read the License from?
[19:09] <Munchor> oh wait, I can change details and have it changed, nvm
[19:10] <dobey> Logan_: i'm not sure that has anything to do with launchpad itself. things that have been pusehd to the release pocket though show up as in release instead, and the proposed one no longer shows up. maybe it was rejected from proposed and therefore is not shown any more. better to ask in #ubuntu-devel maybe
[19:13] <OvenWerks> I have aproblem with my launchpad account. When I push to a branch, the revision just shows my name/email instead of a link to my launchpad home page. This used to work, but stopped. as an example see: https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-default-settings/UbuntuStudio
[19:14] <OvenWerks> I have tried setting bzr lplogin etc. with no luck
[19:14] <OvenWerks> pl id = len-ovenwerks BTW
[19:16] <dobey> you have to commit using an e-mail that is listed on your launchpad account
[19:17] <OvenWerks> I am doing tht
[19:19] <OvenWerks> dobey: I am using the same email as my lp account
[19:19] <dobey> what is your lp username?
[19:19] <OvenWerks> len-ovenwerks
[19:20] <dobey> "Committer: len at ovenwerks"
[19:20] <dobey> not exactly :)
[19:21] <OvenWerks> I have not entered that anywhere dobey where would I set that up?
[19:22] <dobey> are you doing bzr commit --author "Foo <foo@host.com>" ? or what? how did you configure your commit email?
[19:23] <OvenWerks> $ bzr whoami
[19:23] <OvenWerks> Len Ovens len@ovenwerks.net
[19:23] <OvenWerks> $ echo $DEBEMAIL
[19:23] <OvenWerks> len@ovenwerks.net
[19:24] <dobey> you are missing the < > around your e-mail
[19:24] <dobey> so change your bzr whoami
[19:24] <dobey> should be "Name <email>"
[19:24] <dobey> or just email
[19:26] <OvenWerks> dobey: like this: $ bzr whoami
[19:26] <OvenWerks> Len Ovens <len@ovenwerks.net>
[19:26] <OvenWerks> Will try again.
[19:28] <dobey> yes
[19:39] <OvenWerks> dobey: Thank you that works, I guess I made that mistake after I reinstalled my machine.
[22:09] <g0twig> do you accept lintian overrides for PPA packages
[22:13] <g0twig> trism: hey