Nginx mercurial mirror

I have published a Mercurial mirror of Nginx:
http://hg.mirror.mperillo.ath.cx/

It should contain the full history of Nginx.

The import has been done using two scripts, that can be found here:
http://hg.mperillo.ath.cx/nginx/nginx-utils/

The Python script requires a Python interpreter >= 2.4, a POSIX system
and wget installed.
The shell script requires a compatible shell (bash).

The mirror is a beta, since there are some problems:

  1. Nginx 0.1.0 and 0.3.59 are not available

  2. The “merge” of the 0.6.x version from the “old” development branch to
    the “new” stable branch has been done with:

    # Merge the 0.6.x development branch in the stable branch
    # XXX check me: the merge will fail so we only update.
    #     The repository will have two heads
    hg push -R nginx-development -f
    hg update -R nginx-stable -C
    

    So, this is not a real merge, and I’m not sure if this is the right
    thing to do.

Use the script with care, since it will download 80 MB from
http://sysoev.ru/.
As a comparison: the development repository take 8 MB
(3.5 the store and 4.5 the working directory)

Manlio P.

Hello!

On Sat, Aug 02, 2008 at 11:41:42PM +0200, Manlio P. wrote:

I have published a Mercurial mirror of Nginx:
http://hg.mirror.mperillo.ath.cx/

It should contain the full history of Nginx.

Do you have problems with http://mdounin.ru/hg/nginx-vendor-*? It
really contains all versions and works AFAIK.

The import has been done using two scripts, that can be found here:
http://hg.mperillo.ath.cx/nginx/nginx-utils/

The Python script requires a Python interpreter >= 2.4, a POSIX system
and wget installed.
The shell script requires a compatible shell (bash).

The mirror is a beta, since there are some problems:

  1. Nginx 0.1.0 and 0.3.59 are not available

You may find them here:

http://mdounin.ru/files/nginx-0.1.0.tar.gz
http://mdounin.ru/files/nginx-0.3.59.tar.gz

thing to do.
I don’t really think it’s right thing to do since no real merge
happened. And, actually, after stable has been switched to 0.6.*
there were new versions in 0.5.* branch. I think the better
aproach is to maintain numbered branches.

Maxim D.

Maxim D. ha scritto:

Do you have problems with http://mdounin.ru/hg/nginx-vendor-*? It
really contains all versions and works AFAIK.

No, just forgot ;).

[…]
You may find them here:

http://mdounin.ru/files/nginx-0.1.0.tar.gz
http://mdounin.ru/files/nginx-0.3.59.tar.gz

Where did you get them?

thing to do.

I don’t really think it’s right thing to do since no real merge
happened.

Right, in fact the history is “wrong” for the stable branch.
Before 0.6.0 there is 0.5.36, instead of 0.5.25.

And I also forgot to delete extra files removed after the ‘update -C’!

[…]

I think the better aproach is to
maintain numbered branches.

I don’t usually use branches, so I’m not expert.
Can you post the istructions used to build the mirrors?

Maxim D.

Thanks Manlio P.

Hello!

On Sun, Aug 03, 2008 at 10:14:24PM +0200, Manlio P. wrote:

Do you have problems with http://mdounin.ru/hg/nginx-vendor-*? It
really contains all versions and works AFAIK.

No, just forgot ;).

:slight_smile:

[…]
You may find them here:

http://mdounin.ru/files/nginx-0.1.0.tar.gz
http://mdounin.ru/files/nginx-0.3.59.tar.gz

Where did you get them?

Found somewhere, can’t recall exactly - I did it almost year ago.
They aren’t on Igor’s site for some reason, but they were public
and can’t be lost. :slight_smile:

I checked them - they are really original archives. Archive for
0.3.59 may be easily verified against checksums recorded in
FreeBSD ports tree:

http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/nginx/distinfo?rev=1.78;content-type=text%2Fplain

I’m not aware of checksums for 0.1.0, but diffs looks ok.

thing to do.

I think the better aproach is to maintain numbered branches.

I don’t usually use branches, so I’m not expert.
Can you post the istructions used to build the mirrors?

Here is the ugly perl script I use:

http://mdounin.ru/hg/nginx-vendor-import/

Syntax:

./nginx-vendor-import.pl --repo --changes <path/to/CHANGES>

It expects distfiles and to be under current dir.
You have to gunzip/untar last version before import to supply CHANGES
file to script. Script is ugly one, so please use with care (and
read source before you do - this is the only docs available).

Please note: to reproduce imports on should use exactly (almost)
same script runs, since CHANGES file aren’t append-only and
therefore changelog recorded in repository may not be the same for
re-import with CHANGES from other versions.

Maxim D.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs