Skip to content

Updates to clamav-data build process for volatile

I have again worked on the automatic package build, test and publishing process for clamav-data, which runs twice an hour on a host. Details of the process are described in VUA 2-2 on debian-volatile-announce

The "backup" copy on now has accurate mtimes in the directory, and actually the last three published packages are available from here. The rsync process was previously broken in a way that only the current package and two older ones from middle of July (from before the automatisms were in place) were available there.

The publish process now barfs if the specially hacked katie which is used to move the new clamav-data package into without a maintainer signature leaves the publication directory (which is to be considered part of queue/unchecked for katie's environment) in a non-empty stage. This will hopefully catch more katie errors than the parsing of katie's output, which is of course still being done.

After a new package has been built and sucessfully published, the package build directory is cleaned up. All files belonging to changes files older than 60 days are deleted to keep the disk from filling up badly. But that's an internal matter only which you shouldn't be noticing at all.

Additionally, after the last changes, I have hiked up the verbosity level of the package build process for a while so that I can notice when the new process dies or encounters new challenges. That shouldn't be noticeable outside my personal mailbox though.

One issue that is still left is that the automatic clean up of the Pool doesn't seem to work for source packages. Binary packages that are not referenced by any Packages file are supposed to be removed after 15 days, but the source packages seem to stay around. I cannot do anything about that, and am targetting aba on this issue.


No Trackbacks


Display comments as Linear | Threaded

No comments

Add Comment

Markdown format allowed
Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
Form options