[15:41] <RikMills> dragonlord: a separate upload for each series is required (focal, groovy etc) in the changelog header
[15:43] <dragonlord> can i do this with the same debianized branch?
[15:43] <RikMills> also versioning ppa builds with a ppa suffix is usually good policy. e.g. adding for say groovy, ~ubuntu20.10~ppa1 to the end of the version string
[15:44] <dragonlord> okay. so i've got right now this string at the top of my changelog
[15:44] <dragonlord> dragengine (1.2.1-ubuntu2) focal; urgency=medium
[15:44] <dragonlord> so i would have to change this to this?
[15:45] <dragonlord> dragengine (1.2.1-ubuntu20.10-ppa1) focal; urgency=medium
[15:45] <RikMills> (1.2.1-ubuntu2 is a version that should only go in the official archive uploads
[15:46] <RikMills> 1.2.1-ubuntu2~ubuntu20.10-ppa1 would be how I would do it
[15:47] <dragonlord> i assume i can change this only for the next release to not upset launchpad right?
[15:47] <RikMills> the tilde ~ makes that sort before the 1.2.1-ubuntu2, so you don't clash and supercede official ubuntu archive stuff
[15:48] <RikMills> dragonlord: yeah, you have used the higher 1.2.1 version in the ppa now, so will have to change it when you get a 1.2.2 or higher
[15:49] <dragonlord> okay. so now about eoan or bionic. can I add these release strings to the same changelog and launchpad works with it or do i need a separate branch with separate debian directory for this work?
[15:51] <RikMills> dragonlord: I don't know how you are doing your VCS, but launchpad will only accept direct uploads with the changelog for a release specified. how you handle your packaging VCS to achieve that result is up to you
[15:52] <dragonlord> i'm using git with a debianized branch right now
[15:55] <RikMills> git-buildpackage might do what you want. I am afraid that the version I use of that is highly customised for Kubuntu releases, so I can't comment on it's normal use
[15:56] <dragonlord> i'm using git-buildpackage because the bzr version mentioned on the ubuntu pages is not working (python errors thrown when run)
[15:56] <RikMills> or sometimes you can do something as simple as sed the release name and version with a script, then git reset when you have the source built
[15:57] <dragonlord> i think i can roll with multiple branches for each distro version. if only the debian directory content changes this does not consume much repo space
[15:58] <dragonlord> one more question. my final goal is to get the packages into the main ubuntu repository in the future. starting out in a PPA is not a problem for this, or?
[16:00] <RikMills> PPA builds (with a few exceptions for some security release builds etc) use the exact same builders as packages built for the main archive do. so moslty you are simulating what would happen if you got your package uploaded to ubuntu for real
[16:01] <dragonlord> okay. that sounds good. how can I best get feedback on what I need to improve on the package to get it included in ubuntu?
[16:03] <RikMills> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[16:06] <RikMills> unless you can demonstrate an urgent demand for it to be un ubuntu, debian is sadly the preferred way
[16:06] <RikMills> and painfully slow way
[16:08] <dragonlord> i've been there already but since the package is using FOX-1.7 and they somehow do not want to move from FOX-1.6 to FOX-1.7 I did not venture further there
[16:09] <dragonlord> having the FOX-1.7 build in-tree did not even help. not sure what exactly is the problem.
[16:10] <RikMills> It is always difficult. I have trouble getting new things in that are ESSENTIAL for Kubuntu each release. non essential things in universe are very difficult to get in