Hi Amul, Am Thu, Jun 16, 2022 at 05:58:54PM +0000 schrieb Shah, Amul: > > Please reconsider the "add any minor version bump leads to a new binary > > file name" strategy. This means that fis-gtm always needs to pass the > > Debian new queue which always means that there is a hardly predictable > > delay when the package will reach the distribution. > > Could you remind me about what we are doing to cause this problem? Is it the > installation path? > > Or did you mean the below situation where there are two possible GT.M > versions? > > aptitude search fis-gtm > p fis-gtm > - metapackage for the latest version of > FIS-GT.M database > i fis-gtm-6.3-002 > - package for FIS-GT.M database > p fis-gtm-6.3-014 > - package for FIS-GT.M database
We (rather you, Bashkar and Luis Ibanez) decided to create a new binary package name for any mikro fis-gtm release to enable co-installation of all those packages. I'm personally not convinced, that any single minor version bump needs to be installed on a typical Debian installation. This I would rather go with binary package names like fis-gtm-6.3 or fis-gtm-7.0 no matter whether what mikro version "-002" currently - may be "-003" next etc. the package is featuring. However, I do not know anything about fis-gtm and its compatibility between micro versions - so may be I'm just on the wrong track while looking from a Debian packaging perspective. My perspective is that I'm just scared by uploading to the new queue for every single micro version bump which always is causing unpredictable delays until the package gets accepted in unstable. Kind regards Andreas. -- http://fam-tille.de
