So
https://launchpad.net/ubuntu/+source/libstreamvbyte/0.5.1-2/+build/31504922 was build on 2025-11-19
https://launchpad.net/ubuntu/+source/nanopolish/0.14.0-2build1/+build/31510649 was built on 2025-11-21 around the time the build migrated from resolute-proposed to resolute and was served the old version:
``` Get:124 http://ftpmaster.internal/ubuntu resolute/universe amd64 libstreamvbyte0 amd64 0.4.1-4ubuntu1 [6244 B] ```
The expectation there is that from the point on where 0.5.1-2 was published to resolute-proposed a no point a builder should be getting 0.4.1-4ubuntu1 anymore.
The code of the tool doing the pocket move is https://git.launchpad.net/ubuntu-archive-tools/tree/promote-to-release#n61
options.archive.copyPackage( move=True, source_name=name, version=version, from_archive=options.archive, from_series=options.series.name, from_pocket="Proposed", to_series=options.series.name, to_pocket=options.pocket.title(), include_binaries=True, sponsored=options.requestor, phased_update_percentage=percentage, auto_approve=True)
that's using copyPackage() with move=True and including binaries
So
https:/ /launchpad. net/ubuntu/ +source/ libstreamvbyte/ 0.5.1-2/ +build/ 31504922 was build on 2025-11-19
https:/ /launchpad. net/ubuntu/ +source/ nanopolish/ 0.14.0- 2build1/ +build/ 31510649 was built on 2025-11-21 around the time the build migrated from resolute-proposed to resolute and was served the old version:
``` ftpmaster. internal/ ubuntu resolute/universe amd64 libstreamvbyte0 amd64 0.4.1-4ubuntu1 [6244 B]
Get:124 http://
```
The expectation there is that from the point on where 0.5.1-2 was published to resolute-proposed a no point a builder should be getting 0.4.1-4ubuntu1 anymore.
The code of the tool doing the pocket move is https:/ /git.launchpad. net/ubuntu- archive- tools/tree/ promote- to-release# n61
that's using copyPackage() with move=True and including binaries