[lucy-dev] Copying release artifacts to dist directory

[Logan Bell <lo...@gmail.com>]

Hi,

For some reason I don't seem to have privileges to copy the current release
artifacts into /www/www.apache.org/dist/lucy/. This is part of the steps
described in the generated commands when releasing Lucy. Would anyone know
if this step is correct or incorrect, or if I need to contact
Infrastructure to obtain the proper permissions?

The step is: cp -p apache-lucy-0.3.2-rc1/* /www/www.apache.org/dist/lucy/

Fwiw, when I do a ls -la in that path it looks like everything is owned by
"svnwc"

Thanks,
Logan

Re: [lucy-dev] Copying release artifacts to dist directory

[Marvin Humphrey <ma...@rectangular.com>]

On Mon, Jul 9, 2012 at 7:46 AM, Logan Bell <lo...@gmail.com> wrote:
> For some reason I don't seem to have privileges to copy the current release
> artifacts into /www/www.apache.org/dist/lucy/. This is part of the steps
> described in the generated commands when releasing Lucy. Would anyone know
> if this step is correct or incorrect, or if I need to contact
> Infrastructure to obtain the proper permissions?

It looks like that's the version of release_commands.pl from the 0.3 branch,
which has not been updated for the svn-based release system now in use.

    http://www.apache.org/dev/release-publishing.html#distribution_dist

Try the version of release_commands.pl from trunk; it will generate commands
which work for the 0.3 branch.

> The step is: cp -p apache-lucy-0.3.2-rc1/* /www/www.apache.org/dist/lucy/

For the sake of keeping everyone in the loop, ere are the old commands in
full...

    # Copy release artifacts to dist directory, remove RC dir.
    ssh logie@people.apache.org
    cd public_html/
    cp -p apache-lucy-0.3.2-rc1/* /www/www.apache.org/dist/lucy/
    rm -rf apache-lucy-0.3.2-rc1/

    # Carefully remove the artifacts for any previous releases superseded
    # by this one.  DO NOT overwrite any release artifact files, as that
    # triggers the Infra team's security alarm bells.
    cd /www/www.apache.org/dist/lucy/
    [...]

... and here are the new commands:

    # Copy release artifacts to the production dist directory and
    # remove the RC dir.  The "svnmucc" app, which ships with Subversion
    # 1.7, is required.  If you don't have it, you can ssh to
    # people.apache.org and run the commands from there.
    ssh logie@people.apache.org
    svnmucc -m "Publish Apache Lucy 0.3.2" -U
https://dist.apache.org/repos/dist/ mv
dev/lucy/apache-lucy-0.3.2-rc1/apache-lucy-0.3.2.tar.gz release/lucy/
mv dev/lucy/apache-lucy-0.3.2-rc1/apache-lucy-0.3.2.tar.gz.md5
release/lucy/ mv
dev/lucy/apache-lucy-0.3.2-rc1/apache-lucy-0.3.2.tar.gz.sha
release/lucy/ mv
dev/lucy/apache-lucy-0.3.2-rc1/apache-lucy-0.3.2.tar.gz.asc
release/lucy/ mv dev/lucy/apache-lucy-0.3.2-rc1/CHANGES-0.3.2.txt
release/lucy/ rm dev/lucy/apache-lucy-0.3.2-rc1

    # Carefully remove the artifacts for any previous releases superseded
    # by this one.
    svnmucc -m "Remove Apache Lucy 0.3.1" -U
https://dist.apache.org/repos/dist/release/lucy/ rm
apache-lucy-0.3.1.tar.gz rm apache-lucy-0.3.1.tar.gz.md5 rm
apache-lucy-0.3.1.tar.gz.sha rm apache-lucy-0.3.1.tar.gz.asc rm
CHANGES-0.3.1.txt
    [...]

> Fwiw, when I do a ls -la in that path it looks like everything is owned by
> "svnwc"

Right, and we're not supposed to be able to override that, so the system
worked as intended. :)

Marvin Humphrey