Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10090 - [pacman-contrib][pacdiff] Find error (limit)

Attached to Project: Community Packages
Opened by Ray Rashif (schivmeister) - Sunday, 06 April 2008, 09:51 GMT
Last edited by Allan McRae (Allan) - Monday, 07 April 2008, 08:44 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Issue:

Running pacdiff from /etc will produce an error similar to "paths must precede expression".

This is due to find's -name limit on patterns without quotes.

Fix:

Simply adding double quotes to the names in the primary find command would solve this.

-for x in $(find /etc/ -name *.pacnew -o -name *.pacorig -o -name *.pacsave)
+for x in $(find /etc/ -name "*.pacnew" -o -name "*.pacorig" -o -name "*.pacsave")

Package:

pacman-contrib 3.1.4-1
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 07 April 2008, 08:44 GMT
Reason for closing:  Fixed
Comment by Allan McRae (Allan) - Sunday, 06 April 2008, 10:24 GMT
I can't replicate this but reading the -name section in the man page make the request seem reasonable. What shell are you using?
Comment by Ray Rashif (schivmeister) - Sunday, 06 April 2008, 10:55 GMT
Both Bash and Zsh. Strange thing is, it doesn't complain anywhere else - only at /etc.
Comment by Dan McGee (toofishes) - Sunday, 06 April 2008, 15:43 GMT
It is actually due to glob expansion by your shell- if you quote what you pass to find, find will get the '*' character instead of an expanded list of filenames. We'll get this in the next maint release of pacman.
Comment by Allan McRae (Allan) - Monday, 07 April 2008, 08:44 GMT
I have patched the version in pacman-contrib to fix this problem.

Loading...