Update failed for bug watch status of Debian bug 447040

[Daniel Hahler]

The recent activity for https://bugs.launchpad.net/bugs/165184/+watch/38400 reveals:

[Bug Not Found] Update failed with error 'Bug Not Found' (OOPS-1802CCW464) on 2010-12-07
[Bug Not Found] Update failed with error 'Bug Not Found' (OOPS-1790CCW4130) on 2010-11-25
[Bug Not Found] Update failed with error 'Bug Not Found' (OOPS-1783CCW4188) on 2010-11-18
[Bug Not Found] Update failed with error 'Bug Not Found' (OOPS-1776CCW4539) on 2010-11-11
[Bug Not Found] Update failed with error 'Bug Not Found' (OOPS-1766CCW3101) on 2010-11-01

This obviously prevents the bug watch from being updated (should be "Fixed").

[Deryck Hodge (deryck)]

I wonder if this is another case of bug 380362? Graham, can you take a peak when you have time? (/me recognizes the holidays are here and that might not be soon.)

[Gavin Panella (allenap)]

I did some digging on this and talked to mthaddon about it:

<mthaddon> allenap: $ find /srv/bugs-mirror.debian.org -name
    '447040.*' gives nothing

<allenap> mthaddon: Mmm. Can you check it's syncing the archive
    database correctly, because it does exist on
    bugs-mirror.debian.org: rsync -l
    'rsync://bugs-mirror.debian.org/bts-spool-archive/*/447040.*'

FTR, this is the output of that command:

  $ rsync -l 'rsync://bugs-mirror.debian.org/bts-spool-archive/*/447040.*'
  -rw-rw-r-- 158352 2009/03/31 08:29:34 447040.log
  -rw-rw-r-- 4507 2007/10/17 17:51:02 447040.report
  -rw-rw-r-- 226 2009/03/02 21:57:07 447040.status
  -rw-rw-r-- 453 2009/03/02 21:57:07 447040.summary

The conversation continued:

<mthaddon> allenap: trying to follow up for you - we sync from an
    internal target, so I'm trying to see what that internal target is

[Robert Collins (lifeless)]

critical per zero-oops-policy