Update to latest stable release

I'll take a look at this as I'm currently in the process of preparing another ntfs-3g update anyway

This is slightly complicated at the moment due to the version numbering scheme change. I've contacted the Debian maintainer of ntfs-3g to discuss how to handle it, as it is important that we handle it the same in Ubuntu (ie, will the new version become "2:2009.1.1-0ubuntu1" or "1:2009.1.1-0ubuntu1"?)

I spoke with Adam Cécile (who maintains ntfs-3g in Debian), and he isn't going to increment the epoch when he packages the new version of ntfs-3g for Debian, so the Ubuntu version is going to become "1:2009.1.1-0ubuntu1". Here we go:

ntfs-3g (1:2009.1.1-0ubuntu1) jaunty; urgency=low

  * New upstream version (LP: #320031):
    - Built-in, transparent UTF-8 conversion support.
    - The 'locale=' mount option is not used anymore for filename
      characterset conversion. Filenames are always converted to UTF-8.
    - Support for unlimited file ane directory creation.
  * Updated files due to SO version bump:
    - debian/control, debian/rules, libntfs-3g48.docs,
      libntfs-3g48.install, libntfs-3g48-udeb.install,
      libntfs-3g-dev.links, ntfs-3g.links
  * debian/25-ntfs-3g-policy.fdi:
   - Renamed, as policies have to be applied after
     20-storage-methods.fdi.
    - Updated for objects where "volume.fstype=ntfs":
      - Append "ntfs" in to "volume.fstype.alternative".
      - Copy contents of "volume.mount.valid_options" in to
        "volume.mount.ntfs.valid_options".
      - Set "volume.fstype=ntfs-3g"
      - Populate "volume.fstype.valid_options" with options supported
        by ntfs-3g.
      - Set "volume.policy.mount_filesystem=ntfs-3g".
      - This is because HAL will no longer mount a volume with a
        filesystem driver that is different to "volume.fstype", unless
        it is defined in "volume.fstype.alternatives". By default,
        gnome-mount attempts to mount ntfs volumes with the ntfs-3g
        driver. This change will make ntfs-3g the default driver for NTFS
        volumes when the ntfs-3g package is installed, but will still allow
        users to manually specify the old ntfs driver (fixes LP: #300443).
  * debian/changes/Changelog:
    - Updated to document new upstream changes.

 -- Chris Coulson <email address hidden> Thu, 22 Jan 2009 20:31:21 +0000

D'oh! Subscribed the wrong team.

I updated it slightly as I missed some supported options from the HAL fdi file.

Take 3! I made a slight packaging error in the last one

This bug was fixed in the package ntfs-3g - 1:2009.1.1-0ubuntu1

---------------
ntfs-3g (1:2009.1.1-0ubuntu1) jaunty; urgency=low

  * New upstream version (LP: #320031):
    - Built-in, transparent UTF-8 conversion support.
    - The 'locale=' mount option is not used anymore for filename
      characterset conversion. Filenames are always converted to UTF-8.
    - Support for unlimited file ane directory creation.
  * Updated files due to SO version bump:
    - debian/control, debian/rules, libntfs-3g48.docs,
      libntfs-3g48.install, libntfs-3g48-udeb.install,
      libntfs-3g-dev.links, ntfs-3g.links
  * debian/25-ntfs-3g-policy.fdi:
   - Renamed, as policies now have to be applied after
     20-storage-methods.fdi.
    - Updated for objects where "volume.fstype=ntfs":
      - Make ntfs-3g the default driver and make the old ntfs
        driver an alternative.
      - This is because HAL will no longer mount a volume with a
        filesystem driver that is different to what is specified in
        "volume.fstype", unless it is explicitly defined in
        "volume.fstype.alternatives". By default, gnome-mount
        attempts to mount ntfs volumes with the ntfs-3g driver.
        This change makes this work properly again, and makes
        it possible for users to choose the old ntfs driver too.
        (fixes LP: #300443)
  * debian/changes/Changelog:
    - Updated to document new upstream changes.

 -- Chris Coulson <email address hidden> Thu, 22 Jan 2009 20:31:21 +0000

hi,
today i can't mount a fat32 usb-stick plugged on jaunty 32

" cannot get volume.fstype.alternative" error.
This stick has no problem on intrepid, this jaunty is a clean install on it's own partition.

dino99 - if you're having issues, please open a separate bug report. Besides, this is a ntfs-3g bug report and you're talking about vfat usb sticks.

 ntfs-3g (1:2009.2.1-1) unstable; urgency=low

   * New upstream release (Closes: #508028, #512716).
   * Ack Michael Biebl's NMU.
   * Update the HAL policy file from latest Ubuntu packages.
   * As usual, bump library package name and update upstream changelog.
   * Add missing ${misc:Depends} to all binary packages.

 -- Adam Cécile (Le_Vert) <email address hidden> Fri, 13 Mar 2009 21:57:11 +0100