[issue217] Ampersand in suse updates filelist.xml

[linux_learner]

Wrong! the very fact that it also affected yum and zypp is very
material. The bug report confirms that it is not a smart problem.

Could smart handle it better? Sure. But this is an rpm-md XML problem.
Smart, yum, and zypp simply use the protocol.

On 9/21/06, Pascal Bleser <pascal.bleser at skynet.be> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Basil Chupin wrote:
> > jon at Labix Tracker wrote:
> >> jon <linux.learner at gmail.com> added the comment:
> >>
> >> This is not a smart bug. This is a problem with a package in the repos
> >> that
> >> screwed the repo file. The bug for it has been files here
> >> https://bugzilla.novell.com/show_bug.cgi?id=207111
> >>
> >> This is not affecting just smart, but yum and rug/zypp as well
> >
> > Sorry, but it is a smart problem.
> >
> > If smart can be brought down to its knees by a simple typo and then
> > requires manual intervention of some degree of complexity to get smart
> > to just simply function again then it is definitely a smart problem.
>
> Learn XML, the rpm-md metadata is broken (it is not valid XML), period.
>
> smart could handle the issue more gracefully though, no question.
>
> > How it may or may not affect yam or carpet or zapp is immaterial.
>
> Ok, if you say so.
>
> - --
>   -o) Pascal Bleser     http://linux01.gwdg.de/~pbleser/
>   /\\ <pascal.bleser at skynet.be>       <guru at unixtech.be>
>  _\_v The more things change, the more they stay insane.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFFEvttr3NMWliFcXcRAnrwAJ4g1a3tyySnuYKgdiDL87JhrBIVcwCfQ2bZ
> vnS3x9jqwkCRaRPvZVQJ14s=
> =aSsW
> -----END PGP SIGNATURE-----
>