Re: Ardour 5.0

[Debian/GNU]

On 08/29/2016 11:22 PM, Robin Gareus wrote:
> That should be trivial for uscan.
> 
> Alas, I'm traveling this week and will probably not get this in place
> before early Sept, but certainly will before 5.4.
> 
>> > BTW IOhannes ardour 5.3 is out ;)
> Get it while it's hot: https://community.ardour.org/srctar :)
> 

for now i have tweaked the debian/watch file to fetch the tarball from
that link instead as from github.

due to the race-condition you mentioned, i would still love the cgi-script.

gamsdr
IOhannes




signature.asc
Description: OpenPGP digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Robin Gareus]

On 08/29/2016 08:56 PM, Jaromír Mikeš wrote:

>> the suggestion about the custom CGI script sounds great.
> 
> Hi Robin,
> 
> do you read the our list regularly or we should keep you in copy?

yes, I did see IOhannes' reply.

> I second IOhannes about CGI script ... it would be really helpful.

I spoke with Paul and he's also OK to also provide a versioned link.

Proposed (not yet working)

  https://community.ardour.org/src/

returns

-8<---
Ardour Source

ardour-5.3.0.tar.bz2

-8<---

That should be trivial for uscan.

Alas, I'm traveling this week and will probably not get this in place
before early Sept, but certainly will before 5.4.

> BTW IOhannes ardour 5.3 is out ;)

Get it while it's hot: https://community.ardour.org/srctar :)

Cheers!
robin


___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Debian/GNU]

On 08/29/2016 08:56 PM, Jaromír Mikeš wrote:
> I second IOhannes about CGI script ... it would be really helpful.
> 
> BTW IOhannes ardour 5.3 is out ;)

let's use the 5.3 release to test the cgi-script.

gfdmasr
IOhannes



signature.asc
Description: OpenPGP digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Jaromír Mikeš]

2016-08-29 9:22 GMT+02:00 IOhannes m zmölnig (Debian/GNU) :
> On 08/28/2016 03:31 PM, Robin Gareus wrote:
>> It was a very practical thing. After blacklisting the files, the
>> support-rate on #ardour IRC dropped significantly. I suppose most users
>
> i see.
>
>> don't read the README, nor 'configure' output,
>
> i'm sure they don't.
>
>> but they do understand "empty zip". :)
>
> wow, so they are cleverer than me, as i would (and did) naturally
> suspect a problem with the github's export.
>
> so here's a suggestion: how about including a single README-like file
> (README.github-exports) in the otherwise-empty tarball that explains the
> issue? (if this is possible at all with .gitattributes)
>
>
> the suggestion about the custom CGI script sounds great.

Hi Robin,

do you read the our list regularly or we should keep you in copy?
I second IOhannes about CGI script ... it would be really helpful.

BTW IOhannes ardour 5.3 is out ;)

best regards

mira

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Debian/GNU]

On 08/28/2016 03:31 PM, Robin Gareus wrote:
> It was a very practical thing. After blacklisting the files, the
> support-rate on #ardour IRC dropped significantly. I suppose most users

i see.

> don't read the README, nor 'configure' output,  

i'm sure they don't.

> but they do understand "empty zip". :)

wow, so they are cleverer than me, as i would (and did) naturally
suspect a problem with the github's export.

so here's a suggestion: how about including a single README-like file
(README.github-exports) in the otherwise-empty tarball that explains the
issue? (if this is possible at all with .gitattributes)


the suggestion about the custom CGI script sounds great.

gfmards
IOhannes



signature.asc
Description: OpenPGP digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Robin Gareus]

tl;dr: We can't offer a better solution for the time being

On 08/28/2016 02:19 PM, Jaromír Mikeš wrote:
>>>
>>> ardour 5.1 is out ... I still don't have a idea how get a tarball :(

And 5.3 will be out later today :)

https://community.ardour.org/srctar is a direct link to the latest
upstream source of released version (currently still 5.1.0).

>> indeed the github download seems to be very broken.
>> it seems that this is intentional (at least that is how i interpret the
>> line `/* export-ignore` in .gitattributes¹).
>> i guess this is to force people to download via the ardour website².
>> ...

The motivation is different. As IOhannes already mentioned, Ardour
relies on `git describe` to work in order to extract the version.
Shallow git clones fail for the same reason.

One needs to run `./waf dist` on a full git clone in order to generate
libs/ardour/revision.cc prior to export. Github does not allow that.
GH does also not allow one to disable snapshots.

It was a very practical thing. After blacklisting the files, the
support-rate on #ardour IRC dropped significantly. I suppose most users
don't read the README, nor 'configure' output,  but they do understand
"empty zip". :)

If there's anything we can do to make debian packaging easier without
adding more 'newbie' support load on our end, I'll gladly do the
required changes.


The actual problem: We do not want to maintain version information in
multiple places. git tags are awesome.

Sadly gitattributes export-subst can only use information that is
available to git-log. One cannot currently walk the tree as git-describe
does.

Closest thing we've found is
http://stackoverflow.com/questions/19659976/add-tag-in-export-subst-file
but GH does not allow one to run arbitrary smudge filter commands either.

If you have a better solution, please don't hesitate to tell.

We're currently looking into getting `git describe` as supported feature
for export-subst upstream at git. But that's rather long term.

>> anyhow, i just fetched the upstream tarball and ran gbp-import-orig on it.
>> it should be possible (and possibly simple) to hack the d/watch to run
>> the actual download from the official download site, and use github only
>> as an announcement channel to check for new releases.

That sounds sensible to me, at least short/mid term. I suggest to add a
24h delay, though:

The git tag is the very first step in a release-cycle and as it happened
in the past (4.3, 4.5) and just now again with 5.2, the ensuing testing
after the tag may result in another version bump.

The "proper" way would be to parse the first  from
https://ardour.org/whatsnew.html That page is updated as last step every
release cycle.

If it helps I could set up a CGI script on ardour.org that is uscan
compatible. but I'll need some help to work around the missing
version-number in the upstream URL. Does uscan support Content-Disposition ?

ciao,
robin

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Jaromír Mikeš]

2016-08-26 21:18 GMT+02:00 IOhannes m zmölnig (Debian/GNU)
:
> On 08/26/2016 09:24 AM, Jaromír Mikeš wrote:
>> 2016-08-15 22:13 GMT+02:00 Jaromír Mikeš :

>>> ardour 5.0 has been released. I tried download source for updating,
>>> but getting only empty tarball.
>>> Anybody knows whats can be wrong?
>>>
>>> https://github.com/Ardour/ardour/tags
>>>
>>> Last working tag seems to be 5.0-pre0 :(
>>
>> ardour 5.1 is out ... I still don't have a idea how get a tarball :(
>
> indeed the github download seems to be very broken.
> it seems that this is intentional (at least that is how i interpret the
> line `/* export-ignore` in .gitattributes¹).
> i guess this is to force people to download via the ardour website².
> ...

ok ..

> actually i just checked the commit message on .gitattributes, and it
> seems that the reason is technical by nature: the build-system in git
> Depends on `git desscribe` working (something which we would patch away
> in Debian but which of course is inconvenient for "ordinary" users of
> the source exports)

ok ..

> anyhow, i just fetched the upstream tarball and ran gbp-import-orig on it.
> it should be possible (and possibly simple) to hack the d/watch to run
> the actual download from the official download site, and use github only
> as an announcement channel to check for new releases.
> since robin is a both a major contributor to ardour these days and a DM
> in our team, he might be able to shed some light (and code)...

I am copying Robin to help us make decision.

best regards

mira

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: Ardour 5.0

[Jaromír Mikeš]

2016-08-15 22:13 GMT+02:00 Jaromír Mikeš :

Hi,

> ardour 5.0 has been released. I tried download source for updating,
> but getting only empty tarball.
> Anybody knows whats can be wrong?
>
> https://github.com/Ardour/ardour/tags
>
> Last working tag seems to be 5.0-pre0 :(

ardour 5.1 is out ... I still don't have a idea how get a tarball :(

mira

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers