Submitted by ben.morphett@silverbrookresearch.com
If (perhaps by mistake) you do an aenf on a file that already exists in the repository, it (correctly) does not make that file a "new file" in the change set, but it also (incorrectly) deletes the symbolic link to the file.
There is a straightforward work-around: the next time you remake the symbolic link farm (perhaps with aeb), the file comes back.
But it shouldn't have been deleted in the first place.
------------------------
Here is the bug being demonstrated:
$ ls -l Jamfile
lrwxrwxrwx 1 bmorphett aegis 127 May 4 09:43 Jamfile -> /usr/local/home/aegis/qai/branch.1/branch.0/baseline/12-QAInfrastructure/16-Memjet_Tester/04-Software_Modules/host_test/Jamfile
$ aenf Jamfile
aegis: appending log to "/usr/local/home/bmorphett/qai.1.0.C1221/aegis.log"
aegis: project "qai.1.0": file "12-QAInfrastructure/16-Memjet_Tester/04-Software_Modules/host_test/Jamfile" already exists in the project
aegis: project "qai.1.0": change 1221: found 1 fatal error, no new files added
$ ls -l Jamfile
ls: Jamfile: No such file or directory
$ aeb
aegis: appending log to "/usr/local/home/bmorphett/qai.1.0.C1221/aegis.log"
aegis: project "qai.1.0": change 1221: creating symbolic links to baseline
aegis: project "qai.1.0": change 1221: development build started 09:44
...
$ ls -l Jamfile
lrwxrwxrwx 1 bmorphett aegis 127 May 4 09:44 Jamfile -> /usr/local/home/aegis/qai/branch.1/branch.0/baseline/12-QAInfrastructure/16-Memjet_Tester/04-Software_Modules/host_test/Jamfile
$
Logged In: NO
This is reproducable (every time) in aegis version 4.22.D005.
I'm running on a Linux box ("Linux ... 2.4.28-gentoo-r9 #4 SMP Thu Dec 28
07:50:47 EST 2006 i686 Intel(R) Xeon(TM) CPU 2.80GHz GenuineIntel
GNU/Linux")