Re: Packaging releases without a tarball (sometimes)
On 17-05-13 08:01, Pau Garcia i Quiles wrote:
>
>
> On Fri, May 17, 2013 at 4:31 AM, Chow Loong Jin <hyperair@debian.org
> <mailto:hyperair@debian.org>> wrote:
>
> On 17/05/2013 01:01, Pau Garcia i Quiles wrote:
> >
> > Patch releases are NOT available as zip files and the list of
> wrongdoings is long:
> > - Patch releases are only available from the git repository
> c5fe17bb4459164bd59153b57248cf94b8867373
> Maybe I'm daft, but I can't seem to find any patch releases,
> actually. Where are
> they stored?
>
>
> They are in the git repository with no tags and no indication in the
> commit message, you have to read the diff. Upstream usually announces
> patch releases in the mailing list (without saying the commit id of the
> release) but sometimes they even forget :-(
>
> c2417972af1295be8dcc07470b0e3d25b0a77e0b is 2.3.2 (untagged)
>
> 8ccc429598d62eebe9f65a0a4e6fd406a123c8b4 is 2.3.1 (untagged)
>
> c1c7a4dfa63bb6684d3670202e4a65d400dfce86 is 2.3.0 (tagged)
>
> c5fe17bb4459164bd59153b57248cf94b8867373 is 2.2.23 (untagged)
Oh. my. god.
Just ask your upstream to do proper releases rather than manually
*pointing* to git commits? Really, this kind of behaviour is horrible,
and causing you all kinds of problems. I doubt you'll be the only one
who's having problems; people who install from source will have issues, too.
Git is a version control system, not a version release system.
--
This end should point toward the ground if you want to go to space.
If it starts pointing toward space you are having a bad problem and you
will not go to space today.
-- http://xkcd.com/1133/
Reply to: