On 04.03.14 08:58:58, Dominique Dumont wrote:
> On Monday 03 March 2014 17:56:38 Dariusz Dwornikowski wrote:
> > The part "undo damage" I do not understand. From what I understand
> > dpkg compares the new config with the existing one. So to upgrade from
> > stable properly I would have to replace
On Monday 03 March 2014 17:56:38 Dariusz Dwornikowski wrote:
> The part "undo damage" I do not understand. From what I understand
> dpkg compares the new config with the existing one. So to upgrade from
> stable properly I would have to replace my new config with the
> identical to the existing one
On 3 March 2014 16:41, Dominique Dumont wrote:
> On Monday 03 March 2014 16:23:28 Dariusz Dwornikowski wrote:
>> I agree this is a nice solution with a patch, I will integrate it for sure.
>> However what should be done in such situation with bug 740332 ?
>> Should I close it with the new release
On Monday 03 March 2014 16:23:28 Dariusz Dwornikowski wrote:
> I agree this is a nice solution with a patch, I will integrate it for sure.
> However what should be done in such situation with bug 740332 ?
> Should I close it with the new release?
ok, I did not realize that the upgrade test is don
On 3 March 2014 13:51, Dominique Dumont wrote:
> On Monday 03 March 2014 08:59:01 Dariusz Dwornikowski wrote:
>> It is upstream's choice. But I will include such a patch, it is quite
>> trivial. But this is not the case here.
>> The problem is that installing the package asks for users' decision
On Monday 03 March 2014 08:59:01 Dariusz Dwornikowski wrote:
> It is upstream's choice. But I will include such a patch, it is quite
> trivial. But this is not the case here.
> The problem is that installing the package asks for users' decision
> (keep config, replace with maintainer, etc).
> Appl
On 2 March 2014 21:45, Russ Allbery wrote:
> Dariusz Dwornikowski writes:
>
>> The previous maintainer of maradns modified conffiles in postinst
>> (dynamically checked for the maradns user id and filled
>> /etc/maradns/mararc with this info). This obviously rendered RC bug of
>> violation of pol
Dariusz Dwornikowski writes:
> The previous maintainer of maradns modified conffiles in postinst
> (dynamically checked for the maradns user id and filled
> /etc/maradns/mararc with this info). This obviously rendered RC bug of
> violation of policy 10.7.3 [2]. I closed the bug in a new release b
hi,
I would like to request some advice on a case I need to resolve with
maradns package [1].
The previous maintainer of maradns modified conffiles in postinst
(dynamically checked for the maradns user id and filled
/etc/maradns/mararc with this info). This obviously rendered RC bug of
violation
9 matches
Mail list logo