bug in PEAR_PackageFileManager?

In a nutshell, writePackageFile() writes a blank file instead of the
XML.

I discovered this while running a script I have for a package I develop.
In the past, the script has run correctly, reading from the current
package.xml, updating it with the info I provide, and writing the new
package.xml. When it didn't work, I tried running it again with new
summary/description fields to genarate the package.xml, but even this
operation resulted in the blank file.

Unfortunately, a number of things have changed on my system, so I'm not
sure if I can pinpoint any one thing in particular.

One thing I know changed: I was on a PEAR 1.4.0a series, I think around
a9; I'm now on a11.

I'm not sure what version of PackageFileManager I had, nor for XML_Tree
or PHP_CompatInfo (if they were even installed). I'm now running with
XML_Tree-1.1 and PHP_CompatInfo-1.0

I'm on php 5.0.3 (this hasn't changed).

Anybody else seen this? or know of a remedy?

--
Matthew Weier O'Phinney           | WEBSITES:
Webmaster and IT Specialist       | http://www.garden.org
National Gardening Association    | http://www.kidsgardening.com
802-863-5251 x156                 | http://nationalgardenmonth.org
mailto:matthew@garden.org         | http://vermontbotanical.org

Matthew Weier O'Phinney wrote:
> In a nutshell, writePackageFile() writes a blank file instead of the
> XML.
>
> I discovered this while running a script I have for a package I develop.
> In the past, the script has run correctly, reading from the current
> package.xml, updating it with the info I provide, and writing the new
> package.xml. When it didn't work, I tried running it again with new
> summary/description fields to genarate the package.xml, but even this
> operation resulted in the blank file.
>
> Unfortunately, a number of things have changed on my system, so I'm not
> sure if I can pinpoint any one thing in particular.
>
> One thing I know changed: I was on a PEAR 1.4.0a series, I think around
> a9; I'm now on a11.
>
> I'm not sure what version of PackageFileManager I had, nor for XML_Tree
> or PHP_CompatInfo (if they were even installed). I'm now running with
> XML_Tree-1.1 and PHP_CompatInfo-1.0
>
> I'm on php 5.0.3 (this hasn't changed).
>
> Anybody else seen this? or know of a remedy?

run pear pv package.xml on the existing package.xml and see what you get
(a bug would be good if this still happens with 1.5.2 or the latest
alpha 1.6.0a1, also always use the latest alpha of PEAR if you're going
to use the alpha - bugfixes throughout)

Greg