On Fri 2013-06-28 10:40:37 -0400, Daniel Kahn Gillmor wrote:

> On 06/28/2013 10:32 AM, Daniel Kahn Gillmor wrote:
>> On 06/28/2013 04:04 AM, Christoph Martin wrote:
>> 
>>> thanks for the patch. I looks ok for me. Do you want to make the upload?
>> 
>> sure, i'll do that today, after i test an upgrade on a demo VM.
>
> to be clear: I expect to upload a 1.1.3-3 version to sid later today if
> i can demonstrate the problem and a fix; if that looks good to people
> and works OK, i'll go ahead and upload to wheezy proposed-updates.

sorry, i'm running out of time today, and need to head out.  I was
unable to get a clean example of the problem to happen that would be
fixed by this proposed change -- i got tripped up by some other problems
that i haven't had the time to report.

I'll try to get this sorted out (with a 1.1.3-3 upload to unstable) over
this weekend.  I've moved the branches around on the pkg-sks git
repository so that my work on packaging 1.1.4 is on the experimental
branch, and this 1.1.3-3 cleanup is on master.

once i can demonstrate the situation directly with a 1.1.3 upload with
DB_CONFIG, i'll try to sort out a wheezy-update.

finally, i think we really need to look into cleaning up the upgrade
scripts; i think they could be much more robust if we made the upgrade
script an explicit upgrade script (in /usr/share/sks/ someplace?) that
we just invoke simply in the package's postinst.

I'll try to model those changes in a future package too.

   --dkg

Attachment: pgpNvq2U4IS2Y.pgp
Description: PGP signature

Reply via email to