[00:40] <crass> how long should it take for an uploaded to src pkg to show up in the ppa?
[00:41] <saiarcot895> crass: the source package should appear in 5-10 minutes
[00:42] <saiarcot895> crass: the binaries have to be built and depend on the build queue
[00:42] <crass> sure, maybe I haven't waited long enough
[00:42] <saiarcot895> crass: the wait is around 30 minutes for i386 and amd64, so binaries will appear in 30 minutes+build time
[00:43] <saiarcot895> approximately
[00:43] <crass> yeah, usually longer for my recipe builds, but I was just wondering about the time till you actually see anything change in the UI (even if to say waiting to build)
[00:44] <saiarcot895> crass: are the recipes themselves waiting to build or are the builds for the arch waiting?
[00:46] <crass> no, no, forget about recipes, I was talking about a dputt'ed source pkg
[00:46] <StevenK> czajkowski: When did you upload it?
[00:46] <crass> how can I tell?
[00:47] <crass> probably around 10min ago, I'll wait a little longer and see what happens
[00:47] <crass> said successfully uploaded
[00:47] <StevenK> That's only local
[00:47] <crass> but I'd expect and automatic email confirming the upload, but there is none
[00:47] <StevenK> It gets processed server side
[00:47] <crass> yes
[00:47] <StevenK> crass: What's your LP username?
[00:47] <crass> crass
[00:47] <wgrant> crass: You'd expect an email within 10 minuts
[00:48]  * StevenK digs up some logs
[00:48] <crass> actually, I was thinking right away
[00:48] <wgrant> They're still processed by a */5 cronjob
[00:48] <wgrant> No such thing as right away in that world :)
[00:49] <crass> yep, def been more than 5 though
[00:49] <StevenK> 2013-06-28 00:35:22 INFO        Launchpad failed to process the upload path '~cr
[00:49] <StevenK> ass/crass/ppa/ubuntu':
[00:49] <StevenK> Could not find a PPA named 'crass' for 'crass'.
[00:49] <wgrant> So you'll have a rejection email
[00:49] <StevenK> Your PPA is probably called 'ppa'
[00:49] <crass> ok, got a failure email
[00:49] <crass> yeah it is
[00:49] <StevenK> It was sent 15 minutes ago
[00:50] <StevenK> Oh, I wonder if indium is having fun again
[00:50] <crass> strange, I guess its taking gmail a while to get it
[00:51] <wgrant> StevenK: It was fine an hour ago
[00:51] <StevenK> crass: You have two much crass in your path: ~crass/ppa is what you're after
[00:51] <kalaka> what does "Source/binary (i.e. mixed) uploads are not allowed." mean? should I move the binaries to a different folder and try uploading again?
[00:51] <StevenK> kalaka: You can only upload source.
[00:52] <wgrant> kalaka: How are you invoking dpkg-buildpackage or debuild?
[00:52] <StevenK> We do not permit binary uploads from anywhere but the builders themselves.
[00:52] <wgrant> kalaka: You need to give them the -S option to ask them to just produce a source upload
[00:52] <crass> ok, that's because of a missing ~
[00:53] <wgrant> crass: You should just want to say 'dput ppa:crass/ppa FOO_VERSION_source.changes
[00:53] <wgrant> '
[00:53] <crass> wgrant: did that, I think it should be dput ppa:~crass/ppa ..., no?
[00:53] <kalaka> so just the -S flag should do the trick (w/o moving files around)?
[00:53] <StevenK> crass: The config file includes the ~
[00:54] <wgrant> crass: Due to various historical mistakes the ~ is implied in dput
[00:54] <wgrant> Your PPA page will show you the upload command
[00:54] <kalaka> it just says dput ppa:kalaka/ppa <source.changes>
[00:55] <kalaka> I'm invoking dpkg-buildpackage, btw wgrant
[00:55] <wgrant> kalaka: Give it the -S argument
[00:55] <kalaka> ok, thanks
[00:55] <wgrant> It'll generate a PACKAGE_VERSION_source.changes
[00:55] <wgrant> dput that instead
[00:56] <kalaka> but wgrant, I have other files on that folder, should I move them?
[00:56] <wgrant> kalaka: They don't matter
[00:56] <kalaka> I see, thanks
[00:56] <wgrant> The .changes defines which files are uploaded by dput
[00:58] <kalaka> It says files have already been uploaded (but I'm already using the -f flag)
[00:58] <wgrant> What is the exact command you're using, and the exact text of the error message?
[00:58] <crass> I must upload once per distro, right?
[00:58] <kalaka> I tried several ways
[00:59] <kalaka> according to dput --help though, there is no -S flag
[00:59] <wgrant> crass: Once per distro release, yes
[01:00] <wgrant> kalaka: -S is a flag to dpkg-buildpackage or debuild
[01:00] <wgrant> Not dput
[01:00] <crass> kalaka: the -S is for dpkg-buildpackage
[01:00] <kalaka> I feel pretty dumb :)
[01:00] <kalaka> thanks
[01:12] <kalaka> Yes, finally! my first ppa, thanks wgrant and StevenK!
[01:22] <saiarcot895> Are there any plans of making debdiffs so that, in the case of large debs, users only have to download what's changed?
[01:24] <wgrant> saiarcot895: I don't think Ubuntu is working on debdelta support at the moment.
[02:56] <thomi> Does launchpad publish packages for each architecture as they're built, or does it wait for all architectures to be built, and then publish them all at once?
[02:57] <tsimpson> it publishes them as they are built
[02:57] <thomi> awesome, thankds
[02:57] <thomi> I'm really glad I don't have t wait for this arm build :)
[03:07]  * kalaka *sighs*
[03:09] <kalaka> I uploaded a file into my PPA, I had some build problems so I changed the src and reuploaded but I'm getting an error saying the file already exists but has different contents
[03:09] <kalaka> I mean, I changed the src, recompiled and reuploaded
[03:09] <kalaka> I checked the wiki but I dont understand the answer
[03:13] <tsimpson> you should not modify the original source, but rather add patches to the build system
[03:13] <tsimpson> or you'll have to upload the source with a newer version
[03:14] <kalaka> ah, I see
[03:14] <kalaka> thats what the help file should say! thanks :)
[03:15] <tsimpson> I'm sure it's there somewhere, but I don't feel like wading through the wiki right now ;)
[03:25] <wgrant> kalaka: If you make a change to the package, you need to add a new changelog entry with a new version
[03:25] <wgrant> You can't have two different packages with the same version; that doesn't make sense, and will be rejected.
[03:26] <kalaka> I see
[03:26] <kalaka> What if I just change the version slightly?
[03:26] <kalaka> is that a terrible thing to do for a minor change in the code? its really just one line
[03:27] <wgrant> https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Versioning
[03:28] <wgrant> Your version should probably have been something like 2.0.0+git20130627-0ppa1
[03:28] <wgrant> Otherwise an official version won't supersede it
[03:28] <wgrant> Then for a minor change like you're making now, you'd just increment the last digit
[03:28] <kalaka> The official version is outdated
[03:29] <wgrant> Sure, but then when the official Ubuntu version becomes unoutdated, it should surely supersede your unofficial one
[03:29] <kalaka> It's from the SVN that was discontinued in 2011
[03:29] <kalaka> OK, I understand
[03:29] <kalaka> Like, if Ubuntu developers finally build the newest version, it should replace mine
[03:30] <wgrant> Right
[03:30] <wgrant> If Debian does it, it'll be 2.0.0+git20130627-1. If Ubuntu does it first, it'd be 2.0.0+git20130627-0ubuntu1
[03:30] <kalaka> I already dput the package though
[03:30] <wgrant> 0ppa1 is less than both 1 and 0ubuntu1, so it's a good version to use to ensure that your package is superseded by any official one
[03:31] <kalaka> should I change the name to 2.0.0+git20130627-0ppa1 and upload it again?
[03:32] <kalaka> even if it builds correctly? can i remove the old package afterwards?
[03:38] <czajkowski> StevenK: when did I upload what ?
[03:39] <StevenK> czajkowski: I must of missed when I was talking to crass, I'm sorry.
[03:42] <czajkowski> ah no worries
[03:58] <kalaka> hey, packages that failed to build don't really matter, right? I mean, can I delete them somehow or what should I do?
[04:00] <kalaka> sorry if im being annoying with all this questions, I really have no idea what i'm doing? ^^
[04:07] <tsimpson> if a package didn't build then there's nothing really to delete
[04:11] <kalaka> OK, i should quit IRC, im asking the most ridiculous of questions, deleting a package is super simple, there's a bunch help files
[04:11] <kalaka> thanks everyone for your help, though
[12:38] <crass> so what's the procedure for uploading source pkgs to build for multiple distros?
[12:38] <crass> I can upload for one distro, but then for another of the same version, it says I'm uploading a tarball that exists on the server but with different contents
[12:39] <tsimpson> just upload the .changes and .dsc, not the source tarball
[12:41] <tsimpson> or if you don't require a rebuild you can just copy the packages to a different series, just beware that packages built on one series may not work on another (especially older ones)
[12:41] <crass> any hints on how to do that? I don't see any such option in dput
[12:42] <tsimpson> just don't build your source package with -sa
[12:42] <crass> ahh, ok, thanks
[12:51] <dobey> rebuild source for each series too. and append the series to the changelog version string such as "~precise1" or "~saucy1" which will ensure upgrades will work properly for same version in different series
[12:51] <geser> you can't upload the same package version for multiple releases (unless you copy it through the LP interface), for uploading you need different package versions (e.g. by including the targeted release name/version)
[12:52] <crass> ok, so not uploading the source doesn't work?
[12:52] <dobey> no
[12:52] <crass> dobey: I do add that to the changelog
[12:53] <dobey> uploaded version numbers have to be unique
[12:54] <crass> ok, so the only way is to copy the pkg to the same ppa via LP site and select the desired release and to rebuild src
[12:55] <dobey> you can rebuild the source for each series as i said, and just not use the -sa option to debuild, to avoid including the tarball.
[12:56] <dobey> but the version number must be unique for each series, hence the appendage of ~precise1 etc when rebuilding
[12:56] <crass> ok, so not uploading the source _does_ work?
[12:57] <crass> dobey: ok, but the problem is that the src tarball doesn't have the version part after the '-' which is usually where you put the ~distro
[12:57] <geser> crass: you upload e.g. mypackage-0.0-0myppa1~raring1 to raring and mypackage-0.0-0myppa1~quantal1 to quantal, mypackage-0.0-0myppa1~precise1 to precise (or a silimar version scheme)
[12:58] <crass> geser: that's what I'm trying to do, but the issue is that for all 3 of those the uploaded tarball has the same filename
[12:58] <dobey> crass: yes, do NOT use the -sa option for debuild -S.
[12:58] <dobey> crass: without that, it won't upload the tarball
[12:59] <crass> ok, let me see
[12:59] <geser> (but the sha1sum of that tarball has to be the same to let it work)
[13:04] <cjwatson> crass: the other option is that if you can get away with the same binary on all the series you care about (so no different library sonames etc.) then just upload to the oldest series and then copy-with-binaries to all the newer series once built
[13:05] <cjwatson> but generally wisest to copy forwards not backwards
[13:06] <crass> ok, thanks, I'll keep that in mind.  I've got a script for generating and uploading the src for all the distros, which is easier than having to go through the LP UI
[13:14] <crass> so, let's say that I upload a src pkg that fails to build, how can I upload another with fixes? I have to change the upstream version? (not just the part after the '-')
[13:16] <geser> crass: it's still the same upstream version, just a different package version (the part after the last -)
[13:16] <geser> if your 0.0-0myppa1 failed to build, fix it and upload as 0.0-0myppa2
[13:17] <crass> right, so the .orig tarball should be the same? cause mine has the debian folder in it
[13:17] <cjwatson> you only need to change the bit before the dash if you're changing the upstream tarball
[13:17] <cjwatson> don't put debian/ in your .orig
[13:17] <cjwatson> bad and wrong
[13:17] <geser> sounds like a native package
[13:17] <crass> ok, well, its the tools that are doing it
[13:17] <cjwatson> if you want to maintain it all in one place then just use native versioning (no -), indeed
[13:17] <cjwatson> no, this is a choice
[13:18] <cjwatson> if you're using an .orig, then generate it without debian/
[13:18] <cjwatson> if that's horribly inconvenient or unsuitable or whatever, there is the option to just put it all in one tarball and use native versioning
[13:18] <crass> I'm doing dpkg-buildpackage -S in the src dir, so the src dir shouldn't have a debian folder?
[13:19] <cjwatson> the directory where you run dpkg-buildpackage -S must have a debian directory
[13:19] <crass> that's what I thought
[13:19] <cjwatson> but dpkg-buildpackage -S never generates an .orig for you
[13:19] <crass> oh! yes, that is me
[13:20] <cjwatson> the default layout is intended for the model where you're packaging software created by somebody else, so the tarballs that that somebody else produces typically won't contain the packaging
[13:21] <crass> yes, and I am doing that, but from a git repo, so I need to make the tarball myself
[13:23] <crass> so, if I've already uploaded a bad tarball, how do I get rid of it?
[13:24] <cjwatson> new version
[13:25] <cjwatson> or you can also use the 3.0 (quilt) source format (controlled by debian/source/format; see 'man dpkg-source') which ignores any debian directory in the .orig
[13:25] <crass> hmm, I am using that format
[13:26] <cjwatson> then no problem, just change the part of the version after -
[13:27] <cjwatson> the debian directory in your .orig is being ignored when the source package is unpacked, overwritten by the one in the .debian.tar.gz
[13:27] <crass> ok, let see if that works