Ticket #202 (closed defect: fixed)

Opened 13 years ago

Last modified 7 years ago

add -r misbehaves if you create another arch/foo while a locker is added

Reported by: geofft Owned by:
Priority: low Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

lunatique:~ geofft$ ls arch
common  i386_deb31  i386_deb40  i386_rhel4  scripts  sun4x_510
lunatique:~ geofft$ add geofft
lunatique:~ geofft$ mkdir -p arch/i386_deb50/bin
lunatique:~ geofft$ add -r geofft
lunatique:~ geofft$ add
/usr/local/bin:/usr/bin:/bin:/usr/games:{add windowmanagers*}:{add alpine*}:{add consult*}:{add git*}:{add nelhage*}:{add ops*}:{add outland*}:{add scripts*}:{add sipb*}:{add svn*}:{add alpine}:{add consult*}:{add sipb*}:{add svn}:{add geofft*}

In short, add tries to remove /mit/geofft/arch/i386_deb50/bin from my path, instead of the /mit/geofft/arch/i386_deb40/bin that is actually in my path.

Change History

comment:1 Changed 12 years ago by jdreed

  • Milestone set to The Distant Future

I think this falls under "Don't do that", but I'll keep it around in case we decide we care.

comment:2 Changed 8 years ago by jdreed

Yeah, I'm tempted to WONTFIX this. I suppose one solution is for add to attempt to remove something from the path, and if it doesn't find it, then list all athdir paths for the locker, and attempt to remove those. That's... kind of inefficient, but would work.

comment:3 Changed 8 years ago by jdreed

Fixed in the new liblocker, which hasn't been released yet.

comment:4 Changed 7 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.