Fedora Commons

It is possible that some of the sh scripts were checked into (svn or similar) repository from Windows (not Linux/Unix) and contains newline character "\r"

Try this fix script dos2linux.sh:

#!/bin/bash

cat $1 | tr -d '\r' > $1.fixed


to get rid of it.

The new script *.sh.fixed should be working fine.

Neil

-----Original Message-----
From: Deborah Kaplan [mailto:Deborah.Kaplan@...] 
Sent: Thursday, March 26, 2009 3:22 PM
To: Fedora Users
Subject: [Fedora-commons-users] ingests fail at CLI, succeed in GUI

I am testing out Fedora 3.1 ingests in preparation for our migration. In 
order for us to migrate to 3.1, our workflow requires that the commandline 
tools all be functional.

What I have found so far is that I can get a batch to build with the 
commandline. I can also get some of those batches to ingest either via the 
command line or via the GUI. However, most other batches can ingest via the 
GUI, but via the command line give me only the error message "Error : 1", 
without logging any messages elsewhere in the system.

(As a probably unrelated aside, I noticed the same problem when doing batch 
modifies when we moved from Fedora 2.2.2 to Fedora 2.2.4, but we do batch 
modifies rarely enough that I was willing to live with the difficulty of 
having to use the GUI.)

The error messages so uninformative I'm not even sure what other 
information to provide in order to debug. I could attach an example of a 
batch which succeeds and another batch which fails?

But under what circumstances would the CLI fail and the GUI succeed? As far 
as I can tell their settings are identical: repository, port, foxml 
version, username, password.

(One of the difficulties is that this "Error : 1" seems to be turning up an 
awful lot of the time for a whole slew of problems: duplicate pid, wrong 
foxml version, incorrect password. So it's really hard to debug what it means.)
-- 
Deborah Kaplan
Digital Resources Archivist
Digital Collections and Archives
Tufts University

------------------------------------------------------------------------------
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@...
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Guo, Xinjian wrote:
> It is possible that some of the sh scripts were checked into (svn or similar) repository from Windows (not Linux/Unix) and contains newline character "\r"

No, that is a good idea, but I am running on Windows (running the .bat 
scripts). I double checked anyway just to make sure that there were no 
bizarre line endings -- to make sure that they do have Windows carriage 
return -- and they do.

Thank you, though.

-Deborah
-- 
Deborah Kaplan
Digital Resources Archivist
Digital Collections and Archives
Tufts University

Hi Deborah,

I don't know where "Error:1" is coming from but if this is still
happening it might be worth copying the latest (trunk) copies of the
.bat scripts to your environment and trying them.

They can be downloaded here:

https://fedora-commons.svn.sourceforge.net/svnroot/fedora-commons/fedora/trunk/src/bat/client/

These scripts were recently refactored (after Fedora 3.1) in relation
to FCREPO-466 (issue with spaces), and should be compatible with
Fedora 3.1.  If nothing else, trying the newer version of the scripts
may give more informative error messages.

- Chris

On Thu, Mar 26, 2009 at 3:46 PM, Deborah Kaplan
<Deborah.Kaplan@...> wrote:
> Guo, Xinjian wrote:
>> It is possible that some of the sh scripts were checked into (svn or similar) repository from Windows (not Linux/Unix) and contains newline character "\r"
>
> No, that is a good idea, but I am running on Windows (running the .bat
> scripts). I double checked anyway just to make sure that there were no
> bizarre line endings -- to make sure that they do have Windows carriage
> return -- and they do.
>
> Thank you, though.
>
> -Deborah
> --
> Deborah Kaplan
> Digital Resources Archivist
> Digital Collections and Archives
> Tufts University
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Fedora-commons-users mailing list
> Fedora-commons-users@...
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>

Chris Wilper wrote:
> These scripts were recently refactored (after Fedora 3.1) in relation
> to FCREPO-466 (issue with spaces), and should be compatible with
> Fedora 3.1.  If nothing else, trying the newer version of the scripts
> may give more informative error messages.

Chris --

Thank you for this. Our developers here figured out what this particular 
error was that I needed to do a syntax change for my ingests, as well as a 
change in the way of referring to the foxml version. I continue to get 
uninformative errors at various times, though, so the more informative 
error messages will help me as they move forward. I am definitely going to 
try these new scripts. Thanks!

For posterity, in case anybody is browsing this thread for a similar 
problem, the terminology I needed to change was:

\fedora\client\bin\fedora-ingest d [path to objects] 
info:fedora/fedora-system:FOXML-1.1  [server]: [port] fedoraAdmin 
[password] https

Changes here from my old (Fedora 2.*) ingest command include

1. Removing the FTYPS of "O" to indicate that these are object files. (I 
should do further testing to see whether or not this change was required to 
make it work, because if so, that contradicts the documentation at 
<http://www.fedora-commons.org/confluence/display/FCR30/Client+Command-line+Utilities#ClientCommand-lineUtilities-ingest>.)

2. Changing the syntax of the FORMAT to the new syntax used, instead of the 
Fedora 2.* syntax of "foxml1.0", as documented at the above URL.

-Deborah
-- 
Deborah Kaplan
Digital Resources Archivist
Digital Collections and Archives
Tufts University

Hello Deborah,
Sorry for the confusion with the out-of-date documentation, the
"fedora-ingest" section has been updated.
As of release-3.0b2, the FTYPS option has been removed for "fedora-ingest d".

As for the ingest commands, the following FORMAT arguments are supported:

::with foxml-1.0::
    "info:fedora/fedora-system:FOXML-1.0"
and
    "foxml1.0"

::with foxml-1.1::
    "info:fedora/fedora-system:FOXML-1.1"
but NOT
    "foxml1.1"

Andrew




> For posterity, in case anybody is browsing this thread for a similar
> problem, the terminology I needed to change was:
>
> \fedora\client\bin\fedora-ingest d [path to objects]
> info:fedora/fedora-system:FOXML-1.1  [server]: [port] fedoraAdmin
> [password] https
>
> Changes here from my old (Fedora 2.*) ingest command include
>
> 1. Removing the FTYPS of "O" to indicate that these are object files. (I
> should do further testing to see whether or not this change was required to
> make it work, because if so, that contradicts the documentation at
> <http://www.fedora-commons.org/confluence/display/FCR30/Client+Command-line+Utilities#ClientCommand-lineUtilities-ingest>.)
>
> 2. Changing the syntax of the FORMAT to the new syntax used, instead of the
> Fedora 2.* syntax of "foxml1.0", as documented at the above URL.
>
> -Deborah
> --
> Deborah Kaplan
> Digital Resources Archivist
> Digital Collections and Archives
> Tufts University
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Fedora-commons-users mailing list
> Fedora-commons-users@...
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>