Niko Tyni wrote: > On Mon, Jan 21, 2008 at 05:06:09PM -0500, Joey Hess wrote: > >> In #132989 I described four ways to fix that bug, and ended up using >> the first of them, since the maintainer made the mecessary changes to >> libxml-encoding-perl to allow it, and since that was more NMU-amenable >> solution to the bug than adding a bunch of uuencoded encoding files to >> libxml-parser-perl. >> >> To avoid the build dependency loop, any of the other three solutions >> could be used. Note that #132989 includes an old patch implementing the >> fourth option, if you're looking for a quick fix. I'm not sure if that >> patch includes all the encoding files, so it might need to be updated. > > Time is running out: libxml-parser-perl will be uninstallable and > unbuildable (taking along a bunch of other packages) in a week or so > unless this is fixed. See > > http://lists.debian.org/debian-perl/2008/02/msg00093.html > > I came up with one more possible solution: as the encoding maps are > architecture independent, they could be split out into a separate package > so that libxml-encoding-perl isn't needed for binNMUs at all. > > Proposed patch attached; this seems to work for me. It's not a solution > suitable for an NMU, so I would appreciate comments from the package > maintainers. > > The patch puts the encodings in /usr/share/libxml-parser-perl and symlinks > /usr/share/perl5/XML/Parser/Encodings there. XML::Parser looks for the > encoding files in the whole @INC, so moving them from /usr/lib/perl5 > isn't a problem. > > Cheers,
Hi, I think it is better if for the time being we simply break the dependency. I'll add the generated encoding files to libxml-parser-perl and remove the build dependency on libxml-encoding-perl. This is suboptimal but keeps us going. I'll leave 458144 open and work on a permanent bootstrap solution. Thanks, Ardo -- Ardo van Rangelrooij Debian XML/SGML Group <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://people.debian.org/~ardo/ http://debian-xml-sgml.alioth.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
