revu doesn't know when a package has been removed after the latest debian sync

Bug #252305 reported by Javier Uruen Val
2
Affects Status Importance Assigned to Milestone
REVU
New
Low
Unassigned

Bug Description

When a package foo has been removed from the archive by a debian sync, revu is not aware of that. If you try upload the package to revu is listed as "updated packaged" even though that package doesn't exist in the current release.

This came up when I tried to upload libapache-authcookie-perl for intrepid. The package was removed by the debian sync, so it doesn't exist in intrepid right now, but it's showed up by revu as "updated packaged".

I'm not sure if this is the expected workflow.

Changed in revu:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.