On 25 Jul 07, at 12:34 PM 25 Jul 07, Dennis Lundberg wrote:
It's time again... time for the stage plugin blues :(
I just used the stage plugin and this time it failed on me. The
previous runs had gone fine. Note that I'm using my locally patched
version to be able to supply a different username.
Why don't you push that in?
This time it got almost all the way. It copied all the artifacts
and their checksums and sinatures to the right place and then
seemed to hang after that. That's in the middle of running the
rename script.
That's bad.
It's looks like people have different umasks. And I'm not doing any
group swizzling when the file is dropped on to the system. We'll need
to chmod that rewrite script that gets dumped into the system.
I had a look at people.a.o and found something interesting:
[EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync-
repository> l
total 34
-rw-rw-r-- 1 apsite apcvs 2552 Feb 9 18:50 README.txt
drwxrwxr-x 3 jochen apcvs 512 Feb 20 03:31 commons-
fileupload/
drwxr-xr-x 3 cdoremus apcvs 512 Mar 19 19:51 javax/
-rw-rw-r-- 1 jvanzyl apcvs 62 Apr 13 08:52 maven-
repository.properties
drwxrwxr-x 3 apsite apcvs 512 Dec 26 2005 org/
-rw-r--r-- 1 jmcconnell apcvs 1597 Apr 16 16:33 staging-
plugin-1-rename.sh
-rw-r--r-- 1 jdcasey apcvs 823 Jul 17 15:58 staging-
plugin-1.0-rename.sh
-rw-rw-r-- 1 evenisse apcvs 13233 Jul 25 11:19 staging-
plugin-1.1-beta-1-rename.sh
-rwxr-xr-x 1 dennisl apcvs 855 Jul 25 20:44 staging-
plugin-2.1-rename.sh *
-rw-r--r-- 1 vsiveton apcvs 839 Jul 21 06:37 staging-
plugin-2.3-rename.sh
It seems that I'm not the first one to run into this :-/ The
interesting thing to note here are the file permissions. Except for
staging-plugin-2.1-rename.sh (which I changed manually to be able
to run it) none of the rename scripts have execute permissions.
Don't know if that is needed. Probably not - since we do sh
<scriptname>. Anyway, I then ran the rename script manually:
Yah, doens't need to be executable.
[EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync-
repository> sh staging-plugin-2.1-rename.sh
mv: rename org/apache/maven/plugins/maven-changelog-plugin/2.1.rip
to org/apache/maven/plugins/maven-changelog-plugin/2.1/2.1.rip: No
such file or directory
override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/
maven-changelog-plugin/maven-metadata.xml.md5? (y/n [n]) y
override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/
maven-changelog-plugin/maven-metadata.xml? (y/n [n]) y
override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/
maven-changelog-plugin/maven-metadata.xml.sha1? (y/n [n]) y
The first line had obviously already been run (the artifacts). I
confirmed this before running the script manually.
After that I had to answer y for each of the metadata files. Is
this because of wrong file permissions on those files? Or do we
have to add some kind of force switch on the mv command?
I can add one.
Here are the contents of my rename script:
[EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync-
repository> more staging-plugin-2.1-rename.sh
mv org/apache/maven/plugins/maven-changelog-plugin/2.1.rip org/
apache/maven/plugins/maven-changelog-plugin/2.1
mv org/apache/maven/plugins/maven-changelog-plugin/maven-
metadata.xml.md5.rip org/apache/maven/plugins/maven-changelog-
plugin/maven-metadata.xml.md5
mv org/apache/maven/plugins/maven-changelog-plugin/maven-
metadata.xml.rip org/apache/maven/plugins/maven-changelog-plugin/
maven-metadata.xml
mv org/apache/maven/plugins/maven-changelog-plugin/maven-
metadata.xml.sha1.rip org/apache/maven/plugins/maven-changelog-
plugin/maven-metadata.xml.sha1
mv org/apache/maven/plugins/maven-metadata.xml.md5.rip org/apache/
maven/plugins/maven-metadata.xml.md5
mv org/apache/maven/plugins/maven-metadata.xml.rip org/apache/maven/
plugins/maven-metadata.xml
mv org/apache/maven/plugins/maven-metadata.xml.sha1.rip org/apache/
maven/plugins/maven-metadata.xml.sha1
The good thing here was that I was at least able to manually finish
the job.
Yah, I leave everything lying around.
But this experience shows two things. That we really need an
application sitting on the accepting end of a release, and secondly
that it probably would have been have been wiser in the repository
layout to make a version atomic i.e. everything for a new version sit
under one directory instead of multiple.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
