sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] Debian Jessie package for sks-1.1.6 was: [Announcement]


From: George K,
Subject: Re: [Sks-devel] Debian Jessie package for sks-1.1.6 was: [Announcement] SKS 1.1.6 Released
Date: Tue, 9 Aug 2016 00:25:44 +0300

On Mon, 08 Aug 2016 15:45:12 -0400
Daniel Kahn Gillmor <address@hidden> wrote:

> Hi all--
> 
> On Mon 2016-08-08 14:45:15 -0400, George K. wrote:
> > On Sun, 07 Aug 2016 17:17:03 +0200
> > Christoph Egger <address@hidden> wrote:
> >
> >> Gabor Kiss <address@hidden> writes:
> >> >> > Out of curiosity, is there any Debian-type repository one can
> >> >> > use to install updates automatically?
> >> >> > 
> >> >> https://packages.debian.org/jessie/sks ???
> >> >
> >> > Jessie is the _stable_ version. Its sks package won't be upgraded
> >> > unless a major security hole will be found in 1.1.5.
> >> >
> >> > We hope sid gets 1.1.6 soon.
> 
> 1.1.6-1 was uploaded to debian today and is at the autobuilders
> already:
> 
>  https://buildd.debian.org/status/logs.php?arch=&pkg=sks
> 
> >> And I'd expect it on backports shortly after .. just like the 1.1.5
> >> for wheezy
> 
> I've prepared a jessie-backports package that i'm running on
> zimmermann.mayfirst.org as well.  As soon as 1.1.6-1 makes it into
> testing, i'll push it into jessie-backports.
> 
> > I've built a Debian Jessie package for sks version 1.1.6. I'm
> > currently running it on keys.void.gr
> > (https://keys.void.gr/pks/lookup?op=stats).
> >
> > If you want to test it:
> > # wget https://keys.void.gr/package/sks_1.1.6-1_amd64.deb
> > # wget https://keys.void.gr/package/sks_1.1.6-1_amd64.deb.sig
> > # gpg --recv-keys 0x721006E470459C9C
> > # gpg --verify sks_1.1.6-1_amd64.deb.sig
> > # dpkg -i sks_1.1.6-1_amd64.deb
> >
> > It's based on debian patches from 1.1.5 with minor changes to them.
> 
> Thanks for doing this, George!  If you're distributing packages that
> aren't part of debian specifically, can i recommend that you choose
> version numbers that are not likely to collide with standard debian
> versions in the future?  For people like me who try to support folks
> running debian-packaged versions of sks, it'd be great to know that
> 1.1.6-1 is the *same* 1.1.6-1 as the one i thought :)
> 

Since Debian/you are providing packages real soon, I've removed the
links from my web server to avoid confusion.

> the debian standard for versions of non-maintainer uploads is to have
> a two-part version number in the debian part.  and if you really want
> to be helpful in identifying the variants out there, you could do put
> your own identifier in the version string.
> 
> so, for example, you could use:
> 
>   1.1.6-0.georgek1
> 

Sure, will do that next time

> Alternately (and even better), you could:
> 
>  git clone https://anonscm.debian.org/git/pkg-sks/pkg-sks.git
> 
> Then record your changes on a git branch, and send a report to the
> debian BTS describing what you did (either containing your patches
> directly or pointing to them on whatever public-facing git repo you
> prefer).  It'd be great to have more people helping with the debian
> packaging!
> 

I'll check that too and see if I can help in someway

> (if you're struggling with reporting a bug to the debian BTS, i
> recommend the "reportbug" package, or reading up at
> https://bugs.debian.org/)
> 
> Regards,
> 
>      --dkg
> 
> PS there is a nice list in debian/TODO about ways that we might
> improve sks packaging for debian in the future.  Anyone who proposes
>    concrete fixes for any of those TODO items would be my hero! :)



-- 
George K.

Attachment: pgppDM7ZnBypr.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]