Bug 96258 - [PATCH] graphics/f-spot calls exec() with arguments
Summary: [PATCH] graphics/f-spot calls exec() with arguments
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Tom McLaughlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-24 13:30 UTC by Frank Altpeter
Modified: 2006-04-24 14:50 UTC (History)
0 users

See Also:

Attachments
file.diff (334 bytes, patch)
2006-04-24 13:30 UTC, Frank Altpeter 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Altpeter 2006-04-24 13:30:17 UTC 
	After installing the new f-spot-0.1.11_1 the program cannot be
	started:

	root@pegasus:/usr/X11R6/bin 0# ./f-spot
	exec: -a: not found

Fix: /usr/X11R6/bin/f-spot is marked as to be started by /bin/sh,
	which doesn't know "-a [name]" option like the bash exec builtin.
	To prevent having to install bash for this, that option should be
	removed.


Patch (add as files/patch-src_f-spot.in):
------------------------------- eat here ---------------------------------
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2006-04-24 13:32:10 UTC 
State Changed
From-To: open->feedback

Awaiting maintainers feedback 

(please note that maintainer address bounces)
Comment 2 Tom McLaughlin freebsd_committer freebsd_triage 2006-04-24 14:21:08 UTC 
State Changed
From-To: feedback->closed

Sorry about that, I fixed that locally to get f-spot off the ground and then 
got bogged down looking at other issues.  Forgot to do a patch for that first 
problem.  All fixed now, thanks for the patch.
Comment 3 Tom McLaughlin freebsd_committer freebsd_triage 2006-04-24 14:21:08 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->tmclaugh

Sorry about that, I fixed that locally to get f-spot off the ground and then 
got bogged down looking at other issues.  Forgot to do a patch for that first 
problem.  All fixed now, thanks for the patch.