On Wed, Nov 25, 2009 at 09:18:50AM +0900, Charles Plessy wrote: > I intend to package the ExtUtils::Manifest Perl module. It is already packaged > in the perl-modules packages, but in Lenny the provided version is too low to > allow backports of one package of mine that would be fine otherwise.
Have you checked if your package actually needs something from the newer ExtUtils::Manifest? It could be just a spurious dependency. > My purpose > is therefore to prepare a libextutils-manifest-perl package similar in design > to libmodule-build-perl, which is also dually present in Debian, and then to > submit a backport to backports.org after the package migrated in Testing. Do you mean a sid+squeeze package is only needed because of a backports.org policy to only accept packages in squeeze? That seems a bit backwards to me. > Please let me know if this would create problems or if more coordination is > required with the perl-modules package. We should add Provides: libextutils-manifest-perl Replaces: libextutils-manifest-perl Conflicts: libextutils-manifest-perl (<< 1.56) into perl-modules if there's going to be a separate package too. Even if it ends up only in backports.org, the control entries don't hurt and they could be useful for upgrades. Please file a bug against perl about this if libextutils-manifest-perl is uploaded. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org