Your message dated Fri, 25 Apr 2014 22:00:06 +0000
with message-id <[email protected]>
and subject line Bug#738135: fixed in rename 0.20-2
has caused the Debian Bug report #738135,
regarding libfile-rename-perl: rename package to 'rename'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
738135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738135
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libfile-rename-perl
Version: 0.20-1
Severity: wishlist
Owner: [email protected]

On Fri, Feb 07, 2014 at 11:07:56PM +0000, Dominic Hargreaves wrote in #735134:
> On Mon, Feb 03, 2014 at 09:28:03AM +0000, Jonathan Dowland wrote:
> > Hi Gregor,
> > 
> > On Sun, Feb 02, 2014 at 07:31:02PM +0100, gregor herrmann wrote:
> > > It's the package for the CPAN File::Rename distribution, and
> > > therefore named accordingly to
> > > https://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html#s-package_names
> > > in Debian.
> > 
> > Thanks for pointing me at that. It seems to me this makes sense for
> > libraries but not for end-user binaries.
> >  
> > > (Cf. also
> > > http://pkg-perl.alioth.debian.org/policy.html#package_naming_policy )
> > 
> > This seems to agree since it suggests end-user binary packages should
> > not follow the libfoo-bar-perl scheme.
> > 
> > [ as a side-note, if the perl group are following the latter, then
> >   a minor-severity bug against policy to update the former to reflect
> >   that practise sounds like it might be in order. I'll do this unless
> >   anyone objects. ]
> > 
> > I guess there are common situations where you have both an end-user
> > binary and a perl module in the same source, and you might not want
> > to split that into two binary packages (if they're very small or 
> > something), however that doesn't appear to be the case here.
> 
> Yeah, I think I agree that this package should be named 'rename' since
> it will be predominantly used as an standalone utility rather than
> library. (I'm assuming noone is going to object to such a generic name).
> I'll file a new bug for that.

Here it is.

Dominic.

--- End Message ---
--- Begin Message ---
Source: rename
Source-Version: 0.20-2

We believe that the bug you reported is fixed in the latest version of
rename, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominic Hargreaves <[email protected]> (supplier of updated rename package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 23 Feb 2014 19:04:56 +0000
Source: rename
Binary: rename
Architecture: source all
Version: 0.20-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <[email protected]>
Changed-By: Dominic Hargreaves <[email protected]>
Description: 
 rename     - Perl extension for renaming multiple files
Closes: 738135
Changes: 
 rename (0.20-2) unstable; urgency=medium
 .
   * Rename package to 'rename' (Closes: #738135)
Checksums-Sha1: 
 43cffa4659c5596cbd8c76866981c7adc2cabb29 1928 rename_0.20-2.dsc
 571c6f1110da55c69e4a5f38987472121b4d2f0b 10301 rename_0.20.orig.tar.gz
 75e75bbab34ff220429dd91095a6011e308adc1b 1812 rename_0.20-2.debian.tar.xz
 9c03ad6a8148bf67edfdab33a0994079adabac34 12328 rename_0.20-2_all.deb
Checksums-Sha256: 
 dc565d08f769f9c1d0fcf02392ce0458526f1d6e2249b9dc52c13b0e4111c214 1928 
rename_0.20-2.dsc
 5eee75ea92a987930c5bec4a631ee0201f23c77908ba322e553df80845efc6b1 10301 
rename_0.20.orig.tar.gz
 930493ed455319404baca8abd8d1e8e07d4b8d41cc95a6c0671b593f74f61cad 1812 
rename_0.20-2.debian.tar.xz
 d08f14c8bb5859996efc8e17438fc506e37543c8bda334fe3e03896964844d07 12328 
rename_0.20-2_all.deb
Files: 
 fe11bc6561f2b4f5f2ace21a1a4d6878 1928 perl optional rename_0.20-2.dsc
 c91d42b25294ac001bfb1391258daec5 10301 perl optional rename_0.20.orig.tar.gz
 0278926f29a0befa3c25f50ffd52445f 1812 perl optional rename_0.20-2.debian.tar.xz
 24b04145b58e59c1866e454241075a5f 12328 perl optional rename_0.20-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTCkaDAAoJEMAFfnFNaU+yWGcQAJpCocUYD1JrgRFTqY/rv4sL
elw4vpqHoz0eSkTsp69IIhVxOxBLevNUe6VqSCna7x1fOurN8T+6ol4i5lnVzerH
vyxgX+PqvK+3LugmCUPxEsNPlUOUrmdG4p6tkq+Ln80VTWY4VAME59zWx7VIK376
tgdYiv3TYyqCf9CoQPup6+9eD3ah2Fm8IwlWY9NkGhgojfjhrSrPqmJW2I71goZ6
A/kN9YkfgZyYBe0QiKsdsSD/BSrszlGeNLBc9chjCCEY0chHWN8RpYoxBurk4vIW
WfsTJCi2LSpsvfPlMu0+wsHiCP7Mn1R11w69plx9kNwVBuR1yyO03iq9NCpL2BAX
KdFRi7cuZYtnLKBz7c+mC6KGD76NqXoVhIWW7AgbMkGaJU8a2Vka/bfbw4Rnn6uQ
u43Fu7h16gASGQB2HPPSNGH/5mLQlG+f8pMAPMW3wJuDhzkhCtebk6X0Wz7DPPNK
cIMQgOOBSM+110M1TYGNgP6jwV4zyb8YOPSpmC8X80kZUiDjf6lO+3TkrlaGWRTI
8kj+x6YU9ioCl1+KTmN6YRhlDrovtUjcl8xwtM/nEdK9vdHgrTo2QpX2O3iq0JBo
DsMtSbJIu0WgzguM96HDfUDBhdiBWokonvjh+N0RkiQOIjqrmyR6GVDpqo3RWnco
+c65euM9Bdia2mM5tK3m
=FYrU
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to