On Thu, 29 Oct 2020, Sebastian Andrzej Siewior wrote:
The bug report is about freshclam not clamd.
yes, but both freshclam and clamd, starting from the same package version, have exactly the same behaviour, failing to start with exactly the same error message. So the above information is likely pertinent to freshclam as well. What is the appropriate debian policy in this case? File another, more or less identical, bug report for the clamav-daemon package? Or can the same bug id refer to two different packages, if they are both simultaneously affected in the same way and originate from the same source package? Or should it be duplicated, even if it probably is indeed the same bug affecting two packages? I'm asking so that I know what to do in such a case, should it happen again. thanks, best regards Giacomo Mulas -- _________________________________________________________________ Giacomo Mulas <[email protected]> _________________________________________________________________ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180255 mob. : +39 329 6603810 _________________________________________________________________ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _________________________________________________________________ _______________________________________________ Pkg-clamav-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-clamav-devel
