[Bug-gnu-arch] [bug #6384] tag command can embed bogus archive names in archives

[nobody]

=================== BUG #6384: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=6384&group_id=4899

Changes by: Robert Collins <address@hidden>
Date: Sat 11/08/2003 at 23:57 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
                  CC |                           | address@hidden


------------------ Additional Follow-up Comments ----------------------------
I think checking is better as it will at least tell the user they have an error 
- and prevent them propogating that via other commands.



=================== BUG #6384: FULL BUG SNAPSHOT ===================


Submitted by: flat5                   Project: GNU arch -- a revision control 
system
Submitted on: Wed 11/05/2003 at 20:46
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Status:  Open                         Release:                              
Fixed Release:                        Merge Request?:  None                 
Your Archive Name:                    Your Archive Location:                
Assigned to:  None                    

Summary:  tag command can embed bogus archive names in archives

Original Submission:  The following user error is not detected:



% tla make-archive address@hidden /archive

...

% tla register-archive address@hidden /archive

% tla tag address@hidden/cat--branch--0 cat--branch--0



which will result in the creation of, at the very least, CONTINUATION files 
that contain the name "address@hidden" which is not consistent with 
/archive/=meta-info/name.



When tla accesses an archive, it should either check for consistency between 
the archive's =meta-info/name and the name used to access the archive, or 
override the name through which the access occurred and use =meta-info/name in 
any resulting write operations.





Follow-up Comments
*******************

-------------------------------------------------------
Date: Sat 11/08/2003 at 23:57       By: robertc
I think checking is better as it will at least tell the user they have an error 
- and prevent them propogating that via other commands.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
address@hidden             | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=6384&group_id=4899

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/