On Fri, Jan 27, 2012 at 6:50 PM, Bernhard R. Link <[email protected]> wrote: > I could add some options to give this heuristic and also give > it unconditionally, but I don't quite understand what it is > interesting for. Either one would want to do something depending > on whether a file is signed (like with uploader files), which > should be done before it is included to some distribution. > Or one might use some information from that file afterwards, > in which case I do not see how that line alone is enough (and > one would not want to look at the .changes file anyway). >
Basically, I use that information to find out if the 'processincoming' failed because the data (.changes and/or .dsc files) are not signed, while the repository is configured to only accept signed uploads (the import system generates reprepro config files so it knows this). I had to check both conditions because I found no specific error message from reprepro for this scenario. This solution was much simpler than checking it manually, since it would not only imply checking if the .changes is signed, but also parse it to find the other files that might be required to be signed (such as .dsc). Alberto -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
