New year and who has access to calligra.org website?
2017 is here, and I wish for it to be a good year for us all! Well, 2016 didn't produce the release we all expected, but I'm sure we will make it before the end of this year ;) To get releases rolling seems we need a page like this on calligra.org: https://www.kde.org/info/plasma-5.8.0.php where we have fingerprints for all that is authorized to release calligra. Who can do this? Cheers, Dag
Re: 3.0.0.1 tarball + signature
Hi, Boudewijn Happy new year. The tarball seems ok, except it is not compressed. The create_tarball script also uses the -a (or --armor) option to sign. Cheers, Dag Boudewijn Rempt skrev den 2016-12-28 15:05: Hi, I've finally figured out how to fix gpg-agent, so next to http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz there's now also http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig which you can use to check whether I've done everything correctly... This should be the corresponding public key: http://valdyas.org/~boud/0x58b9596c722ea3bd.asc (anyone know of a better place to put that? My webserver isn't configured to use https yet...)
Re: 3.0.0.1 tarball + signature
Weird... I just let the script do its work, and then sign manually. So it should compress the tarball. Even weirder, when I tried today, it suddenly started asking for my key's passphrase for checking out the translations a zillion times. On Mon, 2 Jan 2017, Dag wrote: > Hi, Boudewijn > Happy new year. > > The tarball seems ok, except it is not compressed. > The create_tarball script also uses the -a (or --armor) option to sign. > > Cheers, > Dag > > Boudewijn Rempt skrev den 2016-12-28 15:05: > > Hi, > > > > I've finally figured out how to fix gpg-agent, so next to > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz > > > > there's now also > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig > > > > which you can use to check whether I've done everything correctly... > > > > This should be the corresponding public key: > > > > http://valdyas.org/~boud/0x58b9596c722ea3bd.asc > > > > (anyone know of a better place to put that? My webserver isn't > > configured to use https yet...) > -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
Re: 3.0.0.1 tarball + signature
On Mon, 2 Jan 2017, Boudewijn Rempt wrote: > Weird... I just let the script do its work, and then sign manually. So it > should compress the tarball. Even weirder, when I tried today, it suddenly > started asking for my key's passphrase for checking out the translations > a zillion times. Hm, looks like that was a glitch... > > On Mon, 2 Jan 2017, Dag wrote: > > > Hi, Boudewijn > > Happy new year. > > > > The tarball seems ok, except it is not compressed. > > The create_tarball script also uses the -a (or --armor) option to sign. > > > > Cheers, > > Dag > > > > Boudewijn Rempt skrev den 2016-12-28 15:05: > > > Hi, > > > > > > I've finally figured out how to fix gpg-agent, so next to > > > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz > > > > > > there's now also > > > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig > > > > > > which you can use to check whether I've done everything correctly... > > > > > > This should be the corresponding public key: > > > > > > http://valdyas.org/~boud/0x58b9596c722ea3bd.asc > > > > > > (anyone know of a better place to put that? My webserver isn't > > > configured to use https yet...) > > > > -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
Re: 3.0.0.1 tarball + signature
I've updated the tarball and the sig -- the tarball is now 58M On Mon, 2 Jan 2017, Boudewijn Rempt wrote: > On Mon, 2 Jan 2017, Boudewijn Rempt wrote: > > > Weird... I just let the script do its work, and then sign manually. So it > > should compress the tarball. Even weirder, when I tried today, it suddenly > > started asking for my key's passphrase for checking out the translations > > a zillion times. > > Hm, looks like that was a glitch... > > > > > On Mon, 2 Jan 2017, Dag wrote: > > > > > Hi, Boudewijn > > > Happy new year. > > > > > > The tarball seems ok, except it is not compressed. > > > The create_tarball script also uses the -a (or --armor) option to sign. > > > > > > Cheers, > > > Dag > > > > > > Boudewijn Rempt skrev den 2016-12-28 15:05: > > > > Hi, > > > > > > > > I've finally figured out how to fix gpg-agent, so next to > > > > > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz > > > > > > > > there's now also > > > > > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig > > > > > > > > which you can use to check whether I've done everything correctly... > > > > > > > > This should be the corresponding public key: > > > > > > > > http://valdyas.org/~boud/0x58b9596c722ea3bd.asc > > > > > > > > (anyone know of a better place to put that? My webserver isn't > > > > configured to use https yet...) > > > > > > > > > -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
Re: 3.0.0.1 tarball + signature
Boudewijn Rempt skrev den 2017-01-02 13:12: I've updated the tarball and the sig -- the tarball is now 58M Yes, looks better, I'm running a clean build now to test. On Mon, 2 Jan 2017, Boudewijn Rempt wrote: On Mon, 2 Jan 2017, Boudewijn Rempt wrote: > Weird... I just let the script do its work, and then sign manually. So it > should compress the tarball. Even weirder, when I tried today, it suddenly > started asking for my key's passphrase for checking out the translations > a zillion times. Hm, looks like that was a glitch... > > On Mon, 2 Jan 2017, Dag wrote: > > > Hi, Boudewijn > > Happy new year. > > > > The tarball seems ok, except it is not compressed. > > The create_tarball script also uses the -a (or --armor) option to sign. > > > > Cheers, > > Dag > > > > Boudewijn Rempt skrev den 2016-12-28 15:05: > > > Hi, > > > > > > I've finally figured out how to fix gpg-agent, so next to > > > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz > > > > > > there's now also > > > > > > http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig > > > > > > which you can use to check whether I've done everything correctly... > > > > > > This should be the corresponding public key: > > > > > > http://valdyas.org/~boud/0x58b9596c722ea3bd.asc > > > > > > (anyone know of a better place to put that? My webserver isn't > > > configured to use https yet...) > > > >
