Thanks. After looking through the source, I can confirm that this bug exists in the Intrepid version of update-manager
Thanks. After looking through the source, I can confirm that this bug exists in the Intrepid version of update-manager