ubuntu-packaging-guide-team team mailing list archive

[Jelmer Vernooij <jelmer.vernooij@xxxxxxxxxxxxx>]

On Mon, Jun 25, 2012 at 03:58:42PM -0000, Andrew Starr-Bochicchio wrote:
> Ya, but I really am uncertain about the point of this whole thing.
> This is a native package. The "latest upstream source tarball" is
> what will be uploaded. With a native package, there should be no
> difference between the latest "upstream" and the current distro
> package. They are the same thing. There is no other tarball! Yet the
> archive-admins have decided that "native or not, people need to be
> able to verify the integrity of a source package from some upstream
> source." I don't know why this rule applies to this package and not
> the many others that are native, Ubuntu-only packages (including
> those accepted this cycle like say ubuntu-drivers-common) that do
> not have watch files, get-orig-source targets, or README.source
> files.
Right, I agree that it doesn't really make sense to have a
get-orig-source target in this case - especially since as a native
package ubuntu-packaging-guide doesn't actually have a .orig.tar.gz.

I also think that this is a hard requirement, then it should be
documented somewhere..

> Sorry for the ranting, now for a real question. =) Is there a better
> way to determine the latest tag (not revision) in a bzr branch and
> export that than parsing `bzr tags`? (BTW: I'm off to file a bug on
> there being not `bzr help tag`)
There isn't. See this bug: https://bugs.launchpad.net/bzr/+bug/689367

Cheers,

Jelmer

-- 
https://code.launchpad.net/~andrewsomething/ubuntu-packaging-guide/get-orig-source/+merge/111700
Your team Ubuntu Packaging Guide Team is subscribed to branch lp:ubuntu-packaging-guide.