Note one can create .deb packages with arbitrary version numbers not
matching what is listed in debian/changelog.
And this package does that, for Spaß and clarity.
And both builds appear to produce binaries with version numbers
matching the underlying source gcc versions e.g. both builds produce:
gccgo-alpha-linux-gnu-4:8.3.0-1ubuntu1.2
Which launchpad will not allow to publish.
Also I don't think you need to strictly rebuild and republish
gcc-defaults-ports and similar packages. as they should be
metapackages only and don't contain any toolchains.... (and i.e. are
safe to copy into -security pocket)
Note one can create .deb packages with arbitrary version numbers not
matching what is listed in debian/changelog.
And this package does that, for Spaß and clarity.
And both builds appear to produce binaries with version numbers
matching the underlying source gcc versions e.g. both builds produce:
gccgo-alpha- linux-gnu- 4:8.3.0- 1ubuntu1. 2
Which launchpad will not allow to publish.
Also I don't think you need to strictly rebuild and republish
gcc-defaults-ports and similar packages. as they should be
metapackages only and don't contain any toolchains.... (and i.e. are
safe to copy into -security pocket)
--
Regards,
Dimitri.