Advice on set up/maintain Launchpad PPAs

[Alin-Andrei]

You don't create the .deb package to upload to a PPA. This is the command to
create the package to be uploaded: debuild -S -sa

Then you run "dput <my_ppa> myackage.changes" and the package will be
uploaded to Launchpad and it's servers will build the .debs!


On Sat, Mar 13, 2010 at 10:56, Andrew Farris <flyindragon1 at aol.com> wrote:

> On Thu, 2010-03-11 at 04:16 -0500, James Michael Fultz wrote:
> [snip]
> > The package in my PPA is a Python application; I for the most part
> > followed the following guide:
> > <https://wiki.ubuntu.com/PackagingGuide/Python>
> >
> > Binary packages are built from source packages, and even pure Python
> > applications require a source package.  If you've created some packages,
> > you may have little more to do than upload them to your PPA.
>
> Thanks for the advice. If I could though, I'd appreciate one
> clarification:
>
> This launchpad page https://help.launchpad.net/Packaging/PPA/Uploading
> describes using dput to upload, and states that it uploads 3 files:
> *.dsc, *.changes, and *.diff.gz... that confused me, as that makes it
> sound like I can't upload the *.deb file I've already constructed with
> debhelper/dpkg... is this correct, or do I actually upload the .deb
> package, and dput just *additionally* uploads those other files as well?
>
> --
> Andrew
> _____________________________
> Registered Linux User: 473690
> Registered Ubuntu User: 22747
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20100313/aec55cbd/attachment.html>