** Description changed:
bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
directory (when it not readable or not executable)
steps to reproduce
DIR=`mktemp -d`
cd $DIR
mkdir -p 1/1 2
+ chmod a-rw 2
cd 2
find $DIR/1 -type d -exec echo {} \;
find $DIR/1
Dave Chiluk (chiluk) wrote on 2016-01-07: #11
> Findutils just released a new blessed stable version 4.6.0
[...]
> What are the chances of getting this included into xenial?
Xenial is now at > 4.6. (4.6.0+git+20160126-2 )
--
You received this bug notification because you are a member of
Findutils just released a new blessed stable version 4.6.0
http://savannah.gnu.org/bugs/?46438
What are the chances of getting this included into xenial?
** Bug watch added: GNU Savannah Bug Tracker #46438
http://savannah.gnu.org/bugs/?46438
--
You received this bug notification because
Well that's supremely disappointing. I'll see what I can do.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working directory
FTR, the sync of the Debian experimental package was pulled because it
fails on ppc64el. So this needs a cherry-picked fix instead.
** Changed in: findutils (Ubuntu Xenial)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of
** Changed in: findutils (Ubuntu Xenial)
Assignee: Dave Chiluk (chiluk) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed
Talked to Pitti during the last foundations meeting. He mentioned
possibly doing a merge of findutils 4.5.14-3 from debian-experitmental
to xenial. That should contain fix required to resolve this bug.
** Changed in: findutils (Ubuntu Xenial)
Assignee: (unassigned) => Martin Pitt (pitti)
** Also affects: findutils (Ubuntu Xenial)
Importance: Low
Assignee: Dave Chiluk (chiluk)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
I also reviewed the upstream patch that purports to resolve the issue
(7dc7006). This fix is contained within the 4.5.9 and newer versions of
findutils. That's where the good news ends. The code portion of that
single commit is 817 lines long. It doesn't apply cleanly, and it
appears to have
I opened
https://savannah.gnu.org/bugs/index.php?46438
against upstream findutils to see if we can't get them to to a blessed release
of 4.5 of findutils.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
** Changed in: findutils (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when
** Changed in: findutils (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working
Upstream bug:
---
bug #44078: Find fails if executed from a directory on which the user has no
list permissions and exec is an option used[1]
---
Fix:
---
commit 7dc70069a3095a42eadb22b24cb9260c243aff8f
Author: James Youngman
Date: Sat Apr 10 17:15:01 2010 +0100
Exec predicates
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: findutils (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
I just marked this as affecting me as well. However, I had to add one
other step to reproduce the bug using the instructions above. As the bug
title says, the problem only happens when the working directory (not
necessarily the one on which find is being run) is unreadable or not
executable by the
15 matches
Mail list logo