[DRE-maint] Bug#856606: gitlab: fails to upgrade from 'stretch': nginx example configuration file not found

[Andreas Beckmann]

On 2017-03-04 13:27, Pirate Praveen wrote:
> On ശനി 04 മാര്‍ച്ച് 2017 04:25 വൈകു, Andreas Beckmann wrote:
>> Yes, upgrading packages must work. And especially between versions in
>> testing (which will become relevant if 8.13.11+dfsg-4 migrates to
>> testing). And later on from stable to stable-pu (in case you need to
>> apply fixes after the release).
> I thought you need support upgrading between stable to next stable only.
> Can you show the relevant policy that says upgrading between versions in
> testing has to work?

I don't think that is written explicitly in the policy, but there seems
to be general understanding that you must be able upgrade from one
package version to the next package version within a suite (unstable,
testing, stable) as well as between suites (oldstable->stable,
stable->testing, testing->unstable). (This may not be true for packages
in experimental, but once the package gets uploaded to unstable ... you
want to be able to upgrade from the previous version in unstable to the
current one).
What is usually not supported are upgrades that skip stable releases
(e.g. upgrading directly from old-oldstable to stable without upgrading
from old-oldstable to oldstable first).

If you disagree, please take this to the tech-ctte.

>> What else would you want to do with a gitlab installation in testing if
>> upgrading does not work?
> Did you update /etc/gitlab/gitlab-debian.conf?

I didn't touch anything, I'm just doing automated upgrade tests with
piuparts, so all config files are at their defaults.

> This happened because a
> configuration file has changed. How am I supposed to make changes in
> configuration files then?

Use ucf? But you already use this.
Or what do you mean with "making changes in configuration files"?

Having briefly looked at the postinst script, it appears to me that all
the nginx_* variables are not set at all ...


Andreas