Jonathan Riddell skrev den 2016-12-20 12:39:
On 20 December 2016 at 11:29, Dag wrote:
Any pgp key will do, the only requirement is a packager like myself
can verify it's the one the Calligra devs used which is usually done
by putting it on a pgp key server and putting the full fingerprint on
On 20 December 2016 at 11:29, Dag wrote:
>> Any pgp key will do, the only requirement is a packager like myself
>> can verify it's the one the Calligra devs used which is usually done
>> by putting it on a pgp key server and putting the full fingerprint on
>> the release announcement web page and/
Jonathan Riddell skrev den 2016-12-20 11:58:
On 20 December 2016 at 08:12, Dag wrote:
- Who can generate the final release tarball. (pnt 4 below)
It must be someone with a trusted pgp key (I'm not trusted, so can't
do
it).
It should take <30 minutes, so is there somebody out there who cou
On 20 December 2016 at 08:12, Dag wrote:
> - Who can generate the final release tarball. (pnt 4 below)
> It must be someone with a trusted pgp key (I'm not trusted, so can't do
> it).
> It should take <30 minutes, so is there somebody out there who could help?
Any pgp key will do, the only re
On Tue, 20 Dec 2016, Dag wrote:
> tar xJvf /home/dev/Hentet/calligra-3.0.0.1.tar.xz
> xz: (stdin): File format not recognized
> tar: Child returned status 1
> tar: Error is not recoverable: exiting now
Hm, I bet the script still made a tar.gz then, I'll recheck.
> Sorry, totally blank on gpg
M
Boudewijn Rempt skrev den 2016-12-20 11:22:
I've made a new test tarball today, and put it on my own web server
since I
didn't want to repeat the problems with the one I put on
downloads.kde.org:
http://www.valdyas.org/~boud/calligra-3.0.0.1.tar.xz
I get 'File format not recognized' on this
t; I'd like to discuss how to handle future releases, we don't want to continue
> to burden Boudewijn with it.
>
> To summarize, I see two problem areas:
> - Who can generate the final release tarball. (pnt 4 below)
> It must be someone with a trusted pgp key (I'm not t
I'd like to discuss how to handle future releases, we don't want to
continue to burden Boudewijn with it.
To summarize, I see two problem areas:
- Who can generate the final release tarball. (pnt 4 below)
It must be someone with a trusted pgp key (I'm not trusted, so can&
