From: Sami Kerola <kerolasa@iki.fi>
To: ml@ft-c.de
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: rename bug
Date: Tue, 12 May 2020 07:30:35 +0100 [thread overview]
Message-ID: <CAG27Bk0mU1AG6ysX=rbrvUBU6N2-b1QZgy4xOXOOj50NgPPTFg@mail.gmail.com> (raw)
In-Reply-To: <06b88d20-4753-bba5-4df6-ea992aca214e@ft-c.de>
On Tue, 12 May 2020 at 00:30, <ml@ft-c.de> wrote:
> here is a bug in the rename command.
> Pleae test it:
>
> The rename command doesn't work from another directory, when there is a
> "^" (beginn-line) in the regular-expression.
[snip]
> $ rename -V
> /usr/bin/rename using File::Rename version 1.10
Hi Franz
The email list you sent the bug report is maintaining different
rename(1) implementation.
$ rename -V
rename from util-linux 2.35.1
I think good place to report the issue is Debian distribution bug
tracker or straight to Perl cpan upstream.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=rename;dist=unstable
https://rt.cpan.org/Public/Dist/Display.html?Name=File-Rename
--
Sami Kerola
http://www.iki.fi/kerolasa/
prev parent reply other threads:[~2020-05-12 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 23:13 rename bug ml
2020-05-12 6:30 ` Sami Kerola [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG27Bk0mU1AG6ysX=rbrvUBU6N2-b1QZgy4xOXOOj50NgPPTFg@mail.gmail.com' \
--to=kerolasa@iki.fi \
--cc=kerolasa@gmail.com \
--cc=ml@ft-c.de \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).