Menu

#257 Debian Packaging Takeover

future
closed
nobody
None
1
2015-05-18
2014-08-22
No

Couldn't see any active mailing list, so a bug will get everyone's attention.

I'll be maintaining the Debian package of HFST as part of the Apertium packaging effort.

I already run a nightly packaging service which has up-to-date versions of HFST for all Debian/Ubuntu based distros:
http://www.mail-archive.com/apertium-stuff%40lists.sourceforge.net/msg04581.html

Debian control files are kept in Apertium's svn:
http://svn.code.sf.net/p/apertium/svn/branches/packaging/external/hfst/

There is a quirk in that HFST 3.7.x still builds libhfst36. Were there just no breaking API/ABI changes, or was that an oversight?

There were also issues with "make test" failing on 64bit archs, so I simply disable testing in the build.

Also, HFST still will not build in a single run with -j8, which is kinda annoying.

The stable packages will be made from svn. The released tarballs have pre-generated automake files, which are actually bad. Debian's debhelper can run autoreconf during building, avoiding the whole mess of pre-generation. So, for any stable release, I just need to know which svn revision it corresponds to.

Related

Bugs: #257

Discussion

  • Flammie Pirinen

    Flammie Pirinen - 2014-08-22

    I second handing over the deb stuff, Tino's versions of the packaging are much closer to debian quality standards and packaging style, I've been using them on my work machines for a while now. The parallel build fail is tracked in [#234] but there might be other problems. The svn revision of a release should always match the one that's indicated in the configure.ac and repeated by e.g., hfst-info application from hfst.hpp I think.

     

    Related

    Bugs: #234

    • Krister Lindén

      Krister Lindén - 2014-08-24

      I see no particular problems in giving over the Debian packaging to
      Tino. It will take some practical work off Erik's schedule, but gives
      him more time for testing and debugging as well as supporting other
      platforms.

      Regards,
      Krister

      On 22.8.2014 16:47, Flammie Pirinen wrote:

      I second handing over the deb stuff, Tino's versions of the packaging
      are much closer to debian quality standards and packaging style, I've
      been using them on my work machines for a while now. The parallel build
      fail is tracked in [#234] http://sourceforge.net/p/hfst/bugs/234 but
      there might be other problems. The svn revision of a release should
      always match the one that's indicated in the configure.ac and repeated
      by e.g., hfst-info application from hfst.hpp I think.


      [bugs:#257] http://sourceforge.net/p/hfst/bugs/257 Debian Packaging
      Takeover

      Status: open
      Group: future
      Created: Fri Aug 22, 2014 12:57 PM UTC by Tino Didriksen
      Last Updated: Fri Aug 22, 2014 12:57 PM UTC
      Owner: nobody

      Couldn't see any active mailing list, so a bug will get everyone's
      attention.

      I'll be maintaining the Debian package of HFST as part of the Apertium
      packaging effort.

      I already run a nightly packaging service which has up-to-date versions
      of HFST for all Debian/Ubuntu based distros:
      http://www.mail-archive.com/apertium-stuff%40lists.sourceforge.net/msg04581.html

      Debian control files are kept in Apertium's svn:
      http://svn.code.sf.net/p/apertium/svn/branches/packaging/external/hfst/
      http://svn.code.sf.net/p/apertium/svn/branches/packaging/external/hfst

      There is a quirk in that HFST 3.7.x still builds libhfst36. Were there
      just no breaking API/ABI changes, or was that an oversight?

      There were also issues with "make test" failing on 64bit archs, so I
      simply disable testing in the build.

      Also, HFST still will not build in a single run with -j8, which is kinda
      annoying.

      The stable packages will be made from svn. The released tarballs have
      pre-generated automake files, which are actually bad. Debian's debhelper
      can run autoreconf during building, avoiding the whole mess of
      pre-generation. So, for any stable release, I just need to know which
      svn revision it corresponds to.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/hfst/bugs/257/
      https://sourceforge.net/p/hfst/bugs/257

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/
      https://sourceforge.net/auth/subscriptions

       

      Related

      Bugs: #234
      Bugs: #257

  • Erik Axelson

    Erik Axelson - 2015-05-18
    • status: open --> closed