(In reply to Kip from comment #121)
> (In reply to Yuri R. Sucupira from comment #120)
> > And
> > unfortunately I didn't succeed in uploading data to the PPA (I'm using dput,
> > but something's going wrong). I thought I could push the DEB files to the
> > PPA, but it's actually forbidden: one must push the sources, which I'm
> > failing to do, maybe because I'm failing to find out how to sign the
> > source-code and how to authenticate into the PPA in order to push the files
> > into it. I'll try again later, but I'm under the impression that I won't
> > succeed.
>
> Hey Yuri,
>
> Yes, working with a PPA (sbuild) can be a real pain. I've learned over the
> years how to do it. All of the things you raised are definitely annoying,
> but there's actually very good reasons for all of them that make packages
> better. This is the reason why Debian has such a very high quality selection
> of packages because of their high standards. I really recommend checking out
> the Debian Policy Manual at some point for future benefit too.
After a LOT of pain (it took me some hours) I finally managed to sign my sources and upload'em to a PPA. Here's the PPA:
However, I noticed that APT is considering "1.6.10-2ubuntu1" as a newer version than my "1.6.10-2ubuntu1~patch1" version. Does anyone know how I shall version my packages, in order to make APT choose them instead of those in version 1.6.10-2ubuntu1?
(In reply to Kip from comment #121)
> (In reply to Yuri R. Sucupira from comment #120)
> > And
> > unfortunately I didn't succeed in uploading data to the PPA (I'm using dput,
> > but something's going wrong). I thought I could push the DEB files to the
> > PPA, but it's actually forbidden: one must push the sources, which I'm
> > failing to do, maybe because I'm failing to find out how to sign the
> > source-code and how to authenticate into the PPA in order to push the files
> > into it. I'll try again later, but I'm under the impression that I won't
> > succeed.
>
> Hey Yuri,
>
> Yes, working with a PPA (sbuild) can be a real pain. I've learned over the
> years how to do it. All of the things you raised are definitely annoying,
> but there's actually very good reasons for all of them that make packages
> better. This is the reason why Debian has such a very high quality selection
> of packages because of their high standards. I really recommend checking out
> the Debian Policy Manual at some point for future benefit too.
After a LOT of pain (it took me some hours) I finally managed to sign my sources and upload'em to a PPA. Here's the PPA:
https:/ /launchpad. net/~yuri- sucupira/ +archive/ ubuntu/ thunar1. 6.10-patched
However, I noticed that APT is considering "1.6.10-2ubuntu1" as a newer version than my "1.6.10- 2ubuntu1~ patch1" version. Does anyone know how I shall version my packages, in order to make APT choose them instead of those in version 1.6.10-2ubuntu1?