[xml/sgml-pkgs] Expat 2.0.1 packaging

[Daniel Leidert]

Am Mittwoch, den 20.06.2007, 20:58 -0600 schrieb ardo at ardolabs.com:

[..]
> >    * configure.in: Drop .so version hackery, and use upstream's values.
> 
> And now you've broken the world (that is, the world according to Debian).
> 
> As I said in my reply to your bug report: Due to a major screw up in an
> NMU many moons ago, expat in Debian has TWO sonames: 0 and 1.  See the
> Debian changelog for this.
> 
> This is a major issue in an upgrade to a newer version.  The ideal
> situation would be to upgrade to a expat version that has a soname of '2'.
>  But that might take quite a while.
[snip]
> This chunk is the major screw up I mentioned above.  This never should've
> happened.  I've never understood what the person that did this was
> thinking.  The only possible explanation I can think of is that the person
> thought that the soname needed the match the package name.  Wrong: the
> package name needs to match the soname.  Unfortunately the timing of the
> NMU was such that I could not fix this NMU screw up, as the package was
> frozen for the upcoming release at the time.  Ever since we've lived with
> two sonames...
> 
> A possible solution to do the upgrade would be to call the package
> something  like libexpat1X with 'X' to be determined, use the soname '1'
> (as in, follow upstream again) and put the proper conflicts and such in
> the control file.  This would force rebuilds of all package dependent on
> libexpat1, although the soname would not change.  This might work, as I
> somehow got the impression on the expat mailing list that the ABI is
> backwards compatible (but we need to verify this) but they just added some
> new functionality to the API.  Again, we need to verify this.
> 
> We also need to run this by the release team, as they like to know which
> libraries are upgrading.  And since this is a very special case, we need
> to make sure that what we're going to do works.

Do you first want to test a possible solution or should we bring this up
on debian-release/devel soon?

> > As mentioned above, I'm interested in helping out with maintenance of
> > this package, but I will need a sponsor, as I'm not a formal debian
> > developer as of yet.
>
> (I'm a bit limited as to what I can do right now, as I'm on vacation until
> this weekend. :-))
> 
> I absolutely don't mind a co-maintainer.  Please create a guest account on
> alioth and we'll add you to the project.  Then please add yourself to the
> 'Uploaders' field.

ACK. 

Regards, Daniel