Package: dak Severity: normal The database schema used by katie presumes that no package related file can belong in more than one location throughout the archive. This affects .orig.tar.gz files but is not really limited to those, nor should any fix be.
Furthermore when an upload requests that a package related file is to be placed in a location different from the location already listed in the database, katie SILENTLY accepts the upload but throws away information about the requested new location, leaving the file only in a different place than the location that will be listed in Sources, Packages, .dsc etc. This is the root cause of 232730, which has remained open and unhandled for more than 2 years. I suggest that the code in katie be changed to reject uploads that would trigger the bug, with a clear message as to what the problem is. A suggested rejection message could be: Your upload would require the file %s to be placed in the directory %s, but a file by that name is already in the directory %s and the current dak suite unfortunately cannot handle one file being located in two different places (see bug #xxxxxx). Please upload to the location where the file already is, or change the file name, perhaps by changing the version number. I am not sufficiently proficient in python or the inner workings of dak to create a detailed patch, sorry. -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.17jbj3.4-20 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
