You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jeremias Maerki (JIRA)" <ji...@apache.org> on 2005/09/06 10:31:31 UTC
[jira] Created: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
[PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
--------------------------------------------------------------------------
Key: INFRA-544
URL: http://issues.apache.org/jira/browse/INFRA-544
Project: Infrastructure
Type: Bug
Components: Subversion
Reporter: Jeremias Maerki
Priority: Minor
Attachments: taritup-patch.diff
I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Henri Yandell resolved INFRA-544:
---------------------------------
Resolution: Fixed
Applied. Please close if it appears to work.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Jeremias Maerki (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Jeremias Maerki updated INFRA-544:
----------------------------------
Attachment: taritup-patch.diff
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Henri Yandell reassigned INFRA-544:
-----------------------------------
Assign To: Henri Yandell
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-544) [PATCH] Taritup patch for XML Commons,
Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell updated INFRA-544:
--------------------------------
Component/s: (was: Snapshots)
Subversion
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: https://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=comments#action_12322950 ]
Henri Yandell commented on INFRA-544:
-------------------------------------
New patch applied. Also remembered to kill the old checkouts this time, so dumped xml-commons/ and commons/ to force it to start from scratch.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML
Commons, Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533594 ]
Henri Yandell commented on INFRA-544:
-------------------------------------
There are that many people who are unable to use svn?
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: https://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (INFRA-544) [PATCH] Taritup patch for XML Commons,
Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Henri Yandell reassigned INFRA-544:
-----------------------------------
Assignee: (was: Henri Yandell)
Unassigning myself on this as it's not something I'm expecting to fix/figure out anytime soon.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Snapshots
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=comments#action_12322951 ]
Henri Yandell commented on INFRA-544:
-------------------------------------
gtar apparantly causes problems with Winzip/Solaris. Best to use is a tool called 'pax'. Here's Justin's hint so I don't lose it:
15:07 < jerenkrantz> pax -x ustar -w "dir" > foo.tar
15:07 < jerenkrantz> http://svn.collab.net/repos/svn/trunk/dist.sh
I'm going to dig more into the script so I can run it manually and prove things work, then I'll go ahead and try to move to pax.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML
Commons, Batik and FOP after the move to SVN
Posted by "Adrian Cumiskey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533329 ]
Adrian Cumiskey commented on INFRA-544:
---------------------------------------
I think gnutar is the right tool for this job, the background to this problem can be found at http://cclib.nsu.ru/projects/gnudocs/gnudocs/tar/tar_117.html. From what I can gather, I believe you can use the gtar --portability or --old-archive or --format=v7 or some other flag to create a backwards compatible archive file that should work fine on Winzip/Solaris etc. There have been quite a few requests on FOP users for snapshot builds, could someone with the power please look at this.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: https://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Jeremias Maerki (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Jeremias Maerki reopened INFRA-544:
-----------------------------------
There's a similar problem with the Batik snapshot. Looks like it would be worth to have a look at Bertrand's suggestion. But obviously, this will affect the whole script.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Roy T. Fielding (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Roy T. Fielding updated INFRA-544:
----------------------------------
Component: Snapshots
(was: Subversion)
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Snapshots
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML
Commons, Batik and FOP after the move to SVN
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668657#action_12668657 ]
#asfinfra IRC Bot commented on INFRA-544:
-----------------------------------------
<joes4> We're probably going to phase out the taritup script at some point in the near future, sorry.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: https://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch-xmlgraphics.diff, taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-544) [PATCH] Taritup patch for XML Commons,
Batik and FOP after the move to SVN
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-544.
-----------------------------------
Resolution: Won't Fix
Assignee: #asfinfra IRC Bot
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: https://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: #asfinfra IRC Bot
> Priority: Minor
> Attachments: taritup-patch-xmlgraphics.diff, taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Jeremias Maerki (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=all ]
Jeremias Maerki updated INFRA-544:
----------------------------------
Attachment: taritup-patch2.diff
Thanks, Henri. Looks like it's not good enough, yet. I'm attaching another patch the generates XML Commons into the xml-commons directory. The default put it in the "commons" directory.
Another problem is the FOP snapshot where tar has a problem with a few very long filenames. Some of our test cases landed in the root directory of the tar file. As I am no Unix guru I don't know how to fix this. I remember reading something about filename length restrictions for certain versions of tar. Maybe the version in FreeBSD 5.4 has a problem. Not sure how to solve this. Sorry for the trouble.
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-544) [PATCH] Taritup patch for XML Commons,
Batik and FOP after the move to SVN
Posted by "Jeremias Maerki (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremias Maerki updated INFRA-544:
----------------------------------
Attachment: taritup-patch-xmlgraphics.diff
It's not an acute problem but there are some people who have trouble getting through HTTP proxies and even HTTPS sometimes doesn't work for them.
Anyway, with Adrian's hint about gtar and "--format" I've done some experiments and finally got a valid FOP snapshot. I've attached a patch which should create correct snapshots for batik and fop (both have the same problem with long filenames). Please note that I haven't been able to test the change directly. I've experimented in my home directory with a test script. But I think the change is trivial enough so I shouldn't have made any mistakes. Thanks in advance for considering the patch!
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: https://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Jeremias Maerki
> Priority: Minor
> Attachments: taritup-patch-xmlgraphics.diff, taritup-patch.diff, taritup-patch2.diff
>
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=comments#action_12322911 ]
Bertrand Delacretaz commented on INFRA-544:
-------------------------------------------
FWIW, the usual fix for long filenames is to use gtar instead of tar
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Subversion
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-544) [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-544?page=comments#action_12331948 ]
Henri Yandell commented on INFRA-544:
-------------------------------------
Jeremias Maerki <de...@jeremias-maerki.ch> to Apache More options Oct 11 (1 day ago)
In order to push the fixing of the SVN snapshots with long file and path
names, I tried the "pax" utility suggested by Justin. Using "-x ustar"
(as suggested in [1]) produces the same problems as with the current
"tar" command. I found a "man" page that suggested that "-x xustar"
might solve the problem but the version installed on minotaur's FreeBSD
doesn't support it. D'oh. I'm almost as far as to suggest the usage of
the Java's "jar" command with the -M parameter which will produce nice
ZIPs with no filename problems. See /home/jeremias/tarfop on minotaur.
Any ideas welcome. I'd really like to have snapshots for FOP and Batik
again.
BTW, do we really need 4 snapshots a day?
> [PATCH] Taritup patch for XML Commons, Batik and FOP after the move to SVN
> --------------------------------------------------------------------------
>
> Key: INFRA-544
> URL: http://issues.apache.org/jira/browse/INFRA-544
> Project: Infrastructure
> Type: Bug
> Components: Snapshots
> Reporter: Jeremias Maerki
> Assignee: Henri Yandell
> Priority: Minor
> Attachments: taritup-patch.diff, taritup-patch2.diff
>
> I'll attach a patch for taritup under https://svn.apache.org/repos/asf/infrastructure/apmail/trunk. It fixes the repo snapshot production after the migration to SVN for XML Commons, Batik and FOP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira