Launchpad itself

package is not published after successful build

Asked by Hiroaki Nakamura

According to build log, my ngx-ats-lmdb_0.4.0-1ppa2~ubuntu18.04 package was built successfully at 2023-10-25T02:11:45Z.
https://launchpadlibrarian.net/693998634/buildlog_ubuntu-jammy-amd64.ngx-ats-lmdb_0.4.0-1ppa2~ubuntu18.04_BUILDING.txt.gz

However it does not exist in published pacakges:
https://launchpad.net/~hnakamur/+archive/ubuntu/ngx-ats-lmdb

Other versions like 0.4.0-1ppa2~ubuntu20.04 and 0.4.0-1ppa2~ubuntu20.04 are listed as expected.
I suppose 0.4.0-1ppa2~ubuntu18.04 should be listed as well.

Could you take a look at it and fix it?
Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Hiroaki Nakamura
Solved:
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said : 		#1

If you visit https://launchpad.net/~hnakamur/+archive/ubuntu/ngx-ats-lmdb/+packages and switch the "Publiished" filter to "Any status", you'll see that you accidentally uploaded the bionic (18.04) package to jammy (22.04), where it was superseded by the real jammy package. This is also visible from the "jammy" in the build log URL.

You'll need to edit the changelog of the bionic package to target bionic instead of jammy, and also increase the version number.

Revision history for this message
Hiroaki Nakamura (hnakamur) said : 		#2

Ah sorry for my mistake.
I confirmed distribution in debian/changelog was wrong.

Thanks for your prompt support!