Bug#925430: findutils: regextype egrep repitition count doesn't work

2019-03-24 Thread Chris Dunlop 
Package: findutils
Version: 4.6.0+git+20170828-2
Severity: normal

Dear Maintainer,

The repitition count doesn't work with 'find -regextype egrep'.

>From the grep man page:

Repetition
{n}The preceding item is matched exactly n times.
{n,}   The preceding item is matched n or more times.
{,m}   The preceding item is matched at most m times.  This is a GNU extension.
{n,m}  The preceding item is matched at least n times, but not more than m 
times.

E.g. with egrep:

$ echo a | egrep '^a{5}$'
a

However this doesn't work with 'find -regextype egrep', e.g.:

$ touch /tmp/a; find /tmp -maxdepth 1 -regextype egrep -name 'a{5}'

The other repitition count forms (e.g. {n,}) also don't work.

Cheers,

Chris

-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-46-generic (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages findutils depends on:
ii  libc62.27-3ubuntu1
ii  libselinux1  2.7-2build2

findutils recommends no packages.

Versions of packages findutils suggests:
ii  mlocate  0.26-2ubuntu3.1

-- no debconf information

Bug#659762: lvm2: LVM commands freeze after snapshot delete fails

2012-04-26 Thread Chris Dunlop 
On Mon, Feb 13, 2012 at 04:03:53PM +, Paul LeoNerd Evans wrote:
 Package: lvm2
 Version: 2.02.88-2
 Severity: normal
 
 Tried and failed to remove an LVM snapshot:
 
 
 root@cel:~
 # lvremove vg_cel/backups-20110930
 Do you really want to remove active logical volume backups-20110930? [y/n]: ^C
   Logical volume backups-20110930 not removed
 
 root@cel:~
 # lvchange -an vg_cel/backups-20110930
   Can't change snapshot logical volume backups-20110930
 
 root@cel:~
 # lvremove vg_cel/backups-20110930
 Do you really want to remove active logical volume backups-20110930? [y/n]: y
   Unable to deactivate open vg_cel-backups--20110930-cow (254:35)
   Failed to resume backups-20110930.
   libdevmapper exiting with 7 device(s) still suspended.
 
 
 At this point now the entire LVM subsystem is totally frozen. No commands
 ever complete. Any LVM-related command hangs and is not SIGKILLable.

Me too, with same lvm2 package, on home-grown linux-3.3.1.

Synopsis...

I was able to get out of this state without rebooting using:

  dmsetup resume /dev/mapper/vg00-foo
  dmsetup remove /dev/mapper/vg00-foo-real

Expansion...

I had 2 snapshots, foo and foo2, mounted at /mnt/foo and
/mnt/foo2. I tried removing them like:

  # for d in foo foo2
  do
umount /mnt/${d}  lvremove -f vg00/${d}-snap
  done

...and got:

  Logical volume foo-snap successfully removed
  Unable to deactivate open vg00-foo2--snap-cow (253:10)
  Failed to resume foo2-snap.
  libdevmapper exiting with 1 device(s) still suspended.

After that my 'lvs' hung as Paul decribes.

Note: this was actually the second time I've had this problem
under the same circumstances, the first time I ended up
reluctantly rebooting. I wonder if doing multiple lvremoves in
quick succession has anything to do with it?

This time I looked a little deeper into it and found this bug
report which prompted me to look at the dmsetup stuff with which
I've been extravagently unfamiliar. So...

  # dmsetup info /dev/mapper/*foo2*
  Name:  vg00-foo2
  State: SUSPENDED 
  Read Ahead:26624
  Tables present:LIVE  INACTIVE   
  Open count:2
  Event number:  0
  Major, minor:  253, 2
  Number of targets: 1
  UUID: LVM-nxK1Vn04ULIJaEIiwxsldXVoJAS9rp3APs0zI7cK2SDQf1lM2CHiXAfQsvKRfeWg

  Name:  vg00-foo2-real
  State: ACTIVE
  Read Ahead:0
  Tables present:LIVE
  Open count:1
  Event number:  0
  Major, minor:  253, 9
  Number of targets: 3
  UUID: 
LVM-nxK1Vn04ULIJaEIiwxsldXVoJAS9rp3APs0zI7cK2SDQf1lM2CHiXAfQsvKRfeWg-real

  Name:  vg00-foo2--snap
  State: ACTIVE
  Read Ahead:26624
  Tables present:LIVE
  Open count:0
  Event number:  0
  Major, minor:  253, 8
  Number of targets: 1
  UUID: LVM-nxK1Vn04ULIJaEIiwxsldXVoJAS9rp3AV6mYEfmfj24I3epL0ldVOHeOXfLDi3SI

  Name:  vg00-foo2--snap-cow
  State: ACTIVE
  Read Ahead:0
  Tables present:LIVE
  Open count:0
  Event number:  0
  Major, minor:  253, 10
  Number of targets: 1
  UUID: LVM-nxK1Vn04ULIJaEIiwxsldXVoJAS9rp3AV6mYEfmfj24I3epL0ldVOHeOXfLDi3SI-cow

Not knowing what I was doing, but because of the SUSPENDED state I
tried to resume that device:

  # dmsetup resume /dev/mapper/vg00-foo2

At this point the previously-hung 'lvs' returned. A new 'lvs' showed
the snapshot in question was not longer present, however I still had:

  # ls -l /dev/mapper/*foo2*
  lrwxrwxrwx 1 root root   7 2012-04-26 14:51 vg00-foo2 - ../dm-2
  lrwxrwxrwx 1 root root   7 2012-04-26 14:21 vg00-foo2-real - ../dm-9

Using dmsetup to remove that extra device worked:

  # dmsetup remove /dev/mapper/vg00-foo2-real
  # ls -l /dev/mapper/*foo2*
  lrwxrwxrwx 1 root root   7 2012-04-26 14:51 vg00-foo2 - ../dm-2


Cheers,

Chris



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631077: typo in /etc/network/if-up.d/mountnfs

2011-11-24 Thread Chris Dunlop 
On Thu, Nov 24, 2011 at 11:38:12AM +, Roger Leigh wrote:
 On Thu, Nov 24, 2011 at 04:24:21PM +1100, Chris Dunlop wrote:
 On Mon, Jun 20, 2011 at 10:55:17AM +0200, Milan Kocian wrote:
 Older versions of grep  seems ok.
 
 It's definately a bug in the script, not grep: the newer grep is simply
 reporting what must be a common problem. The script is trying to allow
 for possible spaces at the beginning of the line, but failing with
 the incorrect regular expression:
 
 Please could you try the latest git commit at
 
 http://anonscm.debian.org/gitweb/?p=collab-maint/sysvinit;a=blob_plain;f=debian/src/initscripts/etc/network/if-up.d/mountnfs;h=e5c1dba385e89eafb3eed1acc9042f6cd0269360;hb=19dccaa3e52703ae051bb8fa266ad9396df8fd5b
 
 Which should fix this (and other) problems with the script.

It works for me!

And the cleaned up 'while' loop looks far better than before.

Cheers,

Chris.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631077: typo in /etc/network/if-up.d/mountnfs

2011-11-23 Thread Chris Dunlop 
On Mon, Jun 20, 2011 at 10:55:17AM +0200, Milan Kocian wrote:
 hello,
 
 may be I am wrong and it's problem with grep. I see this problem only with
 newest grep package:
 
 root@ntm:~# grep --version
 grep (GNU grep) 2.8
 Copyright (C) 2011 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html.
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.
 
 Written by Mike Haertel and others, see 
 http://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS.
 
 
 root@ntm:/etc/apt# grep ^[:space:]*auto /etc/network/interfaces
 grep: character class syntax is [[:space:]], not [:space:]
 
 
 Older versions of grep  seems ok.

It's definately a bug in the script, not grep: the newer grep is simply
reporting what must be a common problem. The script is trying to allow
for possible spaces at the beginning of the line, but failing with
the incorrect regular expression:

  echo auto | grep ^[:space:]*auto   # works
  auto

  echo  auto | grep ^[:space:]*auto  # doesn't work

And with the proper regular expression:

  echo  auto | grep ^[[:space:]]*auto# works
   auto

  echo auto | grep ^[[:space:]]*auto # works
  auto

Of course it's only going to bite people that have an 'auto' line that
starts with spaces but if they do then this problem is will cause them a
problem that's very hard to track down!

Cheers,

Chris



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#559335: aoetools: init script doesn't wait long enough, tries to umount not mounted filesystems

2011-07-19 Thread Chris Dunlop 
Note: this is still an issue, 18 months later.

Is the maintainer still active?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#344694: libauthen-captcha-perl: misspelled description

2007-02-04 Thread Chris Dunlop 
Package: libauthen-captcha-perl
Version: 1.023-2
Severity: minor

This bug (Turing vs Turning) is still present in the
perldoc:

  $ perldoc Authen::Captcha

  ABSTRACT
Authen::Captcha provides an object oriented interface to
captcha file creations.  Captcha stands for Completely
Automated Public Turning  test to tell Computers


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#409731: libauthen-captcha-perl: not taint safe

2007-02-04 Thread Chris Dunlop 
Package: libauthen-captcha-perl
Version: 1.023-2

When running with perl's '-T' taint switch, the package aborts
the script with following error when trying to unlink expired
images:

  Insecure dependency in unlink while running with -T switch at
  /usr/share/perl5/Authen/Captcha.pm line 261.

This introduces a security issue for scripts using the package
as they cannot use the '-T' switch.

This script demonstrate the problem:

--
#!/usr/bin/perl -T
use Authen::Captcha;
my $captcha = Authen::Captcha-new(
  expire = 1,
  data_folder = '/tmp',
  output_folder = '/tmp',
);
my $md5sum = $captcha-generate_code(5);
sleep(3);
$captcha-check_code($md5sum, $md5sum);
exit 0;
--

The following patch fixes this problem:

--- Authen/Captcha.pm-orig  2007-02-05 11:25:13.0 +1100
+++ Authen/Captcha.pm   2007-02-05 11:26:22.0 +1100
@@ -232,7 +232,11 @@
foreach my $line (@data) 
{
$line =~ s/\n//;
-   my ($data_time,$data_code) = split(/::/,$line);
+
+   #
+   # Extract untainted time and code
+   #
+   my ($data_time,$data_code) = $line =~ 
m/(^\d+)::([[:xdigit:]]{32})$/;

my $png_file = 
File::Spec-catfile($self-output_folder(),$data_code . .png);
if ($data_code eq $crypt)
@@ -351,7 +355,12 @@
foreach my $line (@data) 
{
$line =~ s/\n//;
-   my ($data_time,$data_code) = split(/::/,$line);
+
+   #
+   # Extract untainted time and code
+   #
+   my ($data_time,$data_code) = $line =~ 
m/(^\d+)::([[:xdigit:]]{32})$/;
+
if ( (($current_time - $data_time)  ($self-expire())) ||
 ($data_code  eq $md5) )
{   # remove expired captcha, or a dup


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#387560: mutt: segfault when started in removed directory

2007-01-29 Thread Chris Dunlop 
G'day Chris,

On Sat, Jan 27, 2007 at 03:27:32PM +0100, Christoph Berg wrote:
 I suspect your bug is the same as #386003. Are you using the
 header_cache? If so, can you try disabling it and try if mutt
 still crashes for you?

Yes, I'm using header_cache, and mutt no longer crashes when I
disable header_cache.  So yes, it indeed looks very much like
#386003!

Cheers,

Chris.

 Re: Chris Dunlop 2006-09-15 [EMAIL PROTECTED]
 This sequence of events:
 --
 mkdir /tmp/foo
 cd /tmp/foo
 rmdir /tmp/foo
 mutt
 --
 
 Results in a segfault:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#387560: mutt: segfault when started in removed directory

2006-09-14 Thread Chris Dunlop 
Package: mutt
Version: 1.5.13-1
Severity: normal


This sequence of events:
--
mkdir /tmp/foo
cd /tmp/foo
rmdir /tmp/foo
mutt
--

Results in a segfault:

Reading /var/mail/chris...shell-init: error retrieving current directory: 
getcwd: cannot access parent directories: No such file or directory
   520 (99%)shell-init: error retrieving current 
directory: getcwd: cannot access parent directories: No such file or directory 
Sorting mailbox...Segmentation fault


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.3-1
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages mutt depends on:
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  libdb4.4 4.4.20-3Berkeley v4.4 Database Libraries [
ii  libgnutls13  1.4.2-1 the GNU TLS library - runtime libr
ii  libidn11 0.6.5-1 GNU libidn library, implementation

Versions of packages mutt recommends:
ii  locales  2.3.6.ds1-4 GNU C Library: National Language (
ii  mime-support 3.37-1  MIME files 'mime.types'  'mailcap

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]