I had trouble with packages I created and was about to
post a question. However, I found the problem. In case
anyone else gets the same problem, I thought I would
post anyway.
The problem occurs when an apparently good qpg file
starts to fail. This happened to me after I checked
all my stuff into SourceSafe. The qpg files recovered
from SourceSafe matched exactly those that went in (according
to diff), but I got the error message:
packager libisa.qpg
…
Searching for all files to include…
Warning: There are files at the root, where only directories should
reside.
[problem: ]
[caused by: libisa.qpg]
Abort the packager (A) or continue with these settings (C)? a
It turns out that the execute bit had become set on the qpg file
and the error is a result of that. Why this should be so is a
mystery to me.
Hope this helps someone, sometime.
Regards
William Morris
William, thanks for the bug report. This has been fixed and will be made
available in a future version of packager.
Jerry Chappell
“William Morris” <william@bangel.demon.co.uk> wrote in message
news:3E89A6BF.6CFFC161@bangel.demon.co.uk…
I had trouble with packages I created and was about to
post a question. However, I found the problem. In case
anyone else gets the same problem, I thought I would
post anyway.
The problem occurs when an apparently good qpg file
starts to fail. This happened to me after I checked
all my stuff into SourceSafe. The qpg files recovered
from SourceSafe matched exactly those that went in (according
to diff), but I got the error message:
packager libisa.qpg
…
Searching for all files to include…
Warning: There are files at the root, where only directories should
reside.
[problem: ]
[caused by: libisa.qpg]
Abort the packager (A) or continue with these settings (C)? a
It turns out that the execute bit had become set on the qpg file
and the error is a result of that. Why this should be so is a
mystery to me.
Hope this helps someone, sometime.
Regards
William Morris