From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Vagrant Cascadian <vagrant-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DTC v1.4.6 released
Date: Mon, 22 Jan 2018 10:44:27 +1100 [thread overview]
Message-ID: <20180121234427.GA11419@umbus> (raw)
In-Reply-To: <87k1wauaxd.fsf-LkDtOWtB3X7R7s880joybQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
On Sun, Jan 21, 2018 at 02:03:26PM -0800, Vagrant Cascadian wrote:
> On 2018-01-04, David Gibson wrote:
> > Hi everyone. There have been a number of useful bugfixes added to the
> > dtc tree since v1.4.5, so I decided to tag another release.
>
> Thanks for all the work on dtc!
>
>
> > The signed tag is in the master git tree at:
> >
> > git://git.kernel.org/pub/scm/utils/dtc/dtc.git
>
> I'm not seeing a signed tag for v1.4.6, and it doesn't appear in the web
> interface either:
>
> https://git.kernel.org/pub/scm/utils/dtc/dtc.git/refs/tags
Oops, I forgot to push the tag up to the main repo. Should be fixed
now.
> > Or you can download tarballs from:
> >
> > https://www.kernel.org/pub/software/utils/dtc/
>
> Fortunately, commit:e54388015af1fb4bf04d0bca99caba1074d9cc42 appears to
> be consistent with the contents of the 1.4.6 tarballs.
>
>
> On a related note, I was wondering if it would be possible to have the
> compressed tarballs have their own signature:
>
> https://www.kernel.org/pub/software/utils/dtc/dtc-1.4.6.tar.sign
>
> Only validates against the uncompressed tarball, which makes
> verification of the signature a bit more complicated, having to
> decompresss the tarball before verification.
So, that's not under my control AFAIK - it's handed by the kup scripts
that I use to upload blobs. It handles the compression for me.
> It also means I can not include the signature file in the Debian
> archive, as the signature needs to verify against the compressed tarball
> in the Debian archive. For this reason especially, it would be nice to
> have dtc-X.Y.Z.tar.xz.sign available as well.
>
> Thanks for considering!
>
> Please CC me in replies; I'm not subscribed to the list.
>
> live well,
> vagrant
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-21 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 22:03 DTC v1.4.6 released Vagrant Cascadian
[not found] ` <87k1wauaxd.fsf-LkDtOWtB3X7R7s880joybQ@public.gmane.org>
2018-01-21 23:44 ` David Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-04 3:03 David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180121234427.GA11419@umbus \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vagrant-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).