With "wheezy" being used for Debian LTS, the archive needs to be
published not only when policy queue uploads are accepted, but also
when direct uploads to "wheezy" arrive.
The same applies to uploads to "jessie-kfreebsd".
dopolicy=false
LOCKFILE="$lockdir/unchecked.lock"
dopolicy=false
LOCKFILE="$lockdir/unchecked.lock"
+last_changed() {
+ psql -qAtc "SELECT MAX(last_changed) FROM suite WHERE archive_id=(SELECT id FROM archive WHERE name='$1')"
+}
+
cleanup() {
rm -f "$LOCKFILE"
}
cleanup() {
rm -f "$LOCKFILE"
}
+old_last_changed=$(last_changed security)
+
cd $unchecked
changes=$(find . -maxdepth 1 -mindepth 1 -type f -name \*.changes | sed -e "s,./,," | xargs)
if [ -n "$changes" ]; then
cd $unchecked
changes=$(find . -maxdepth 1 -mindepth 1 -type f -name \*.changes | sed -e "s,./,," | xargs)
if [ -n "$changes" ]; then
dak generate-releases -a build-queues >/dev/null
${scriptsdir}/update-buildd-archive ${base}/build-queues ${incoming}/debian-security-buildd
dak generate-releases -a build-queues >/dev/null
${scriptsdir}/update-buildd-archive ${base}/build-queues ${incoming}/debian-security-buildd
-if [ "x${dopolicy}x" = "xtruex" ]; then
+new_last_changed=$(last_changed security)
+
+if [[ "${old_last_changed}" != "${new_last_changed}" ]]; then
# We had something approved from a policy queue, push out new archive
dak dominate
cd $configdir
# We had something approved from a policy queue, push out new archive
dak dominate
cd $configdir