Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tags/releases #2

Closed
gregoa opened this issue Aug 2, 2014 · 3 comments
Closed

Tags/releases #2

gregoa opened this issue Aug 2, 2014 · 3 comments

Comments

@gregoa
Copy link

gregoa commented Aug 2, 2014

Following up on https://bugs.debian.org/714966 ...

Updating the hompage URL is the easy part, but I'm not sure where we can (automatically) find tarballs of new releases now. An easy solution what be to have releases/tags on github.

What do you think?

Cheers,
gregor, Debian Perl Group

@ftilmann
Copy link
Owner

ftilmann commented Aug 2, 2014

Dear Gregor

I have always considered the CTAN website as the 'master' distribution
channel for latexdiff releases (www.ctan.org/latexdiff) - I have pushed
the latest release to CTAN only yesterday night, and as there is an
element of manual intervention, it might not yet be updated there yet.
But CTAN does not keep an accessible version history.

I am new to git, so have not really investigated investigated tags, but
of course I could easily learn this. However, the latexdiff in the
release is subtly different (though generated automatically from) the
latexdiff in the root of the repository.
In fact, I have been explicitly generating the different releases and
including them as (archived) sub-directories in the main repository.
So an auto-generated tar-ball of a tagged release would contain the
development version of latexdiff along with sub-directories for each
release.
From a strict versioning point of view, this is redundant, of course,
but it is a workflow that works for me, and I would only change if the
reasons are strong.

Let me know if the tar ball available from CTAN is sufficient, or
whether you would like me to create tags in spite of the points listed
above (this would take a little while as I am on holiday now, and will
be very busy on returning to work)

Cheers
Frederik

On 02/08/14 02:09, gregor herrmann wrote:

Following up on https://bugs.debian.org/714966 ...

Updating the hompage URL is the easy part, but I'm not sure where we can
(automatically) find tarballs of new releases now. An easy solution what
be to have releases/tags on github.

What do you think?

Cheers,
gregor, Debian Perl Group


Reply to this email directly or view it on GitHub
#2.

Frederik Tilmann
Helmholtz-Zentrum Potsdam alt.:
Deutsches GeoForschungsZentrum Freie Universität Berlin
Sektion 2.4, Seismologie Fachrichtung Geophysik
Telegrafenberg 1 Malteserstr. 74 - 100
14473 Potsdam 12249 Berlin
Germany

Building A3 Room D 105
Tel.: +49 331-288 1240 Tel.: +49 30 838-70587
Fax: +49 331-288 1277
E-mail: [email protected]

@gregoa
Copy link
Author

gregoa commented Aug 2, 2014

On Sat, 02 Aug 2014 00:21:34 -0700, ftilmann wrote:

I have always considered the CTAN website as the 'master' distribution
channel for latexdiff releases (www.ctan.org/latexdiff) - I have pushed
the latest release to CTAN only yesterday night, and as there is an
element of manual intervention, it might not yet be updated there yet.

Ok, thanks for the clarification, then we will handle it this way as
well.

But CTAN does not keep an accessible version history.

And no versioned tarballs (just 'latexdiff.zip').

I am new to git, so have not really investigated investigated tags, but
of course I could easily learn this. However, the latexdiff in the
release is subtly different (though generated automatically from) the
latexdiff in the root of the repository.

I see. In this case we want to go with the release tarballs indeed.

Let me know if the tar ball available from CTAN is sufficient, or
whether you would like me to create tags in spite of the points listed
above (this would take a little while as I am on holiday now, and will
be very busy on returning to work)

Tags make sense for a git workflow in general, but for Debian we'll
need to use the releases from CTAN, so no hurry for you :)

The problem is that it's not so easy to automatically detect new
releases with Debian tools; but I've just found
http://anonscm.debian.org/viewvc/qa/trunk/cgi-bin/fakeupstream.cgi?view=markup
which will do this for us after someone pulls my patch on the live
machine; temporarily a copy on my server works:
http://info.comodo.priv.at/cgi-bin/fakeupstream.cgi?upstream=ctan/latexdiff

Thanks again for your explanations, and it seems there's nothing you
need to do, and we'll work out the last rough edges on the Debian
side ourselves.

Cheers,
gregor

.''. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ . ' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe - NP: Bob Marley/Jimmy Cliff/Erica Badu: No Woman No Cry

@gregoa
Copy link
Author

gregoa commented Aug 2, 2014

And the patch for the redirector is already live:
https://qa.debian.org/cgi-bin/fakeupstream.cgi?upstream=ctan/latexdiff

Cheers,
gregor, closing the issue since everything's fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants