[Bug 654825] [NEW] FFe: Sync libnfo 1.0.1-1 (universe) from Debian unstable (main)

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Fabrice Coutadeur (fabricesp):

Please sync libnfo 1.0.1-1 (universe) from Debian unstable (main)

Explanation of FeatureFreeze exception:
This package is required for newer enna that I am trying to get into Maverick.
There is no soname bump, and the only rdepends is libvalhalla, that builds and
installs fine.

The new package builds fine (see attached log) and installs fine:
sudo dpkg -i libnfo-dev_1.0.1-1_amd64.deb libnfo1_1.0.1-1_amd64.deb
(Leyendo la base de datos ...  00%
227914 ficheros y directorios instalados actualmente.)
Preparando para reemplazar libnfo-dev 1.0.1-1 (usando libnfo-dev_1.0.1-1_amd64.deb) ...
Desempaquetando el reemplazo de libnfo-dev ...
Preparando para reemplazar libnfo1 1.0.1-1 (usando libnfo1_1.0.1-1_amd64.deb) ...
Desempaquetando el reemplazo de libnfo1 ...
Configurando libnfo1 (1.0.1-1) ...
Configurando libnfo-dev (1.0.1-1) ...
Procesando disparadores para libc-bin ...
ldconfig deferred processing now taking place

As this package is only used in libvalhalla, and libvalhalla builds and installs
fine with this new package, it seems safe to sync it.

As this is a lib, and libvalhalla is only used in enna (not installable right
 now), it's hard ot test it,

Changelog entries since current maverick version 1.0.0-3:

libnfo (1.0.1-1) unstable; urgency=low

  * New upstream release:
    - drop Debian package patches as they are now upstream
    - drop Debian manpage for libnfo-reader it's now upstream
  * Update Standards-Version to 3.9.1 (no changes)
  * Drop Vcs-Pkg fields from control file
  * Update upstream author copyright date
  * Add debian/upstream-metadata.yaml

 -- Davide Cavalca <davide at geexbox.org>  Sat, 02 Oct 2010 15:53:26 +0200

** Affects: libnfo (Ubuntu)
     Importance: Wishlist
         Status: Confirmed

-- 
FFe: Sync libnfo 1.0.1-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/654825
You received this bug notification because you are a member of Ubuntu Package Archive Administrators, which is a direct subscriber.