This one was uploaded *after* I reverted the previous changes. Now I can't do that anymore without a fake upload, since the PureOS version is newer than in Debian.

I don't understand which timeline you are talking about.

The timeline I talk about is this:

• November 25: povray 1:3.7.0.4-2 enters Debian testing, but blocked for PureOS by our 1:3.7.0.0-9+pureos2
• November 27: povray 1:3.7.0.4-2pureos1 pushed for landing, but blocked in PureOS NEW because it contains new binary package
• November 27: I file this issue, requesting 2 things: a) drop our fork, and b) unblock Debian package
• November 30: You close this issue, seemingly addressing only b)

I understand that by now it is too late to change, because the fork has entered green.

What I do not understand is what you say was uploaded after something else.

The package went through NEW after I synchronized it with Debian, which leads to this situation now:
INFO: Can not sync povray: Target version '1:3.7.0.4-2pureos1' is newer/equal than source version '1:3.7.0.4-2'.
So, we can only properly sync this with Debian when the Debian version is newer (the archive will not allow downgrades).

I'll keep an eye on this.

Either povray 1:3.7.0.4-2pureos1 went through NEW when I uploaded it on November 27 - three days _before_ your changes, or in went through NEW caused by your interventions.

As already stated I understand it is too late to change. My point when reopening was simply that we should close this issue when solved, not before.