[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#857257: marked as done (Supporting configuration file changes between versions in unstable/testing)

Your message dated Wed, 22 Mar 2017 21:10:46 +0100
with message-id <878tnx5ayh.fsf@err.no>
and subject line Re: Bug#857257: Re: Supporting configuration file changes between versions in unstable/testing
has caused the Debian Bug report #857257,
regarding Supporting configuration file changes between versions in unstable/testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

857257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857257
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tech-ctte
Control: block 856606 by -1


#856606 is filed as a serious bug against gitlab version 8.13.11+dfsg-4
in unstable as upgrading from 8.13.11+dfsg-3 in testing fails because
/etc/gitlab/gitlab-debian.conf is changed in the new version. I think
this should not be considered an RC bug as it will require making
complicated changes in postinst to support a configuration file that was
never part of any stable release. It is much simpler to make this change
manually and I think it is reasonable to expect users who use testing or
unstable to make those changes manually. Such a requirement will make
changes in unstable/testing much harder than required. I fully agree to
support upgrading between versions in stable releases.

This was the change made to /etc/gitlab/gitlab-debian.conf:


I request CTTE to declare this bug as not RC.

Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---
--- Begin Message ---
]] "Adam D. Barratt" 

> [this doesn't appear to have reached the tech-ctte list yet, so I'm
> replying from the BTS archive]

We've decided to close this bug. It's pretty clear that supporting
upgrades, also within unreleased suites, is a requirement, even if it's
not formally documented in Policy.

If you want to conduct experiments where you don't want to support
upgrades, use experimental instead, since the requirements there are
less strict.

Tollef Fog Heen, for the CTTE
UNIX is user friendly, it's just picky about who its friends are

--- End Message ---

Reply to: