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

Bug#601957: pending NMU

Hi Serafeim,

On Wed, Nov 10, 2010 at 05:28, Serafeim Zanikolas <sez at debian.org> wrote:
> Hi again,
> On Tue, Nov 09, 2010 at 10:31:29AM +0800, Desmond O. Chang wrote [edited]:
>> I have a question about the patch. ?If I remove (not purge) c-l-c
>> first, I will also encounter the conflict when I install the new
>> version.
> Is that a hypothesis or have you verified it? Between which versions?
> My understanding is that that's ?correct, but only for uninstall/install of
> releases from testing->sid (and sid->latest). It's not the case for
> lenny->squeeze because lisp-config.lisp is not a conffile in lenny, and thus
> will be removed even with a plain (non-purge) pkg removal.
>> I think we also need remove lisp-config.lisp when executing
>> 'new-preinst install old-version' (according to debian-policy). ?Is it
>> right?
> The conflict might only occur when the stale lisp-config.lisp is a conffile,
> and by definition we're not allowed to wipe conffiles. I believe that there's
> user prompting only upon a conflict between local changes and the new conffile
> (ie. no prompting when an unmodified old conffile is replaced by an updated
> conffile)

It's just my hypothesis.  We can use your patch first.

>> I hope your patch can be merged into master, but since I don't have
>> uploading permission, I also need you sponsor c-l-c and cl-asdf
>> (dependency of c-l-c). ?So my opinion is that you build & upload our
>> master code of c-l-c.
> So you prefer the release and I do the sponsorship? Why would you update
> cl-asdf? (it's has no rc bugs)

Because c-l-c repo code depends on cl-asdf 2:2.010-1, it's on mentors.

If you don't upload cl-asdf, please do a NMU.  I'll merge your patch.


Reply to: