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

Re: GMT



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 06/20/2015 06:41 PM, Ross Gammon wrote:
> On 06/20/2015 05:51 PM, Sebastiaan Couwenberg wrote:
>> On 06/14/2015 11:39 AM, Sebastiaan Couwenberg wrote:
>>> On 06/14/2015 10:55 AM, Ross Gammon wrote:
>>>> As it is going to have to go through the NEW queue, and if it
>>>>  builds okay without -dcw & -gshhg, shouldn't we target 
>>>> experimental and upload?
>> 
>>> Yes, since libgmt had a SONAME bump the new gmt package should 
>>> first be uploaded to experimental.
>> 
>> Now that gmt-dcw & gmt-gshhg have been accepted, I've uploaded
>> the first gmt 5 revision to experimental.
>> 
>> Once that's passed the NEW queue I'll try to reproduce the many 
>> outstanding gmt bugs to see if they're still applicable to GMT 5.
>> I expect we can close many of them.

It a couple of tries to get the packaging right after the passing the
NEW queue, but it looks like ~exp4 will build successfully on all
architectures. I haven't been able to try a build on hurd-i386 because
both porterboxes (exodar & strass) are down, that may still need a
patch like those for kfreebsd & mips.

Since a transition for GMT 5 won't be required, we can upload it to
unstable soon after it's built on all architectures for experimental.

> Real life is getting in the way at the moment. But I can will try
> and fit in a little bug triage here and there as well. It is a good
> way to learn the package.

Help with the outstanding gmt bugs is still very much appreciated now
that we have working packages in experimental.

Before uploading gmt to unstable I'll first make sure all outstanding
bugs have been triaged with GMT 5.

Kind Regards,

Bas

- -- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVjuAyAAoJEGdQ8QrojUrxQTYP/jGjcAUdh1ZpRuWdpHczOEqt
xe9jA3tuUMbIIJ3b5SMg7airF/MkHFT1aBIRhcAhBWqg5cEKVyj1FKFsON8VZndH
CiVAiRyfnVOwWyD7fBr54BbMJarwtsX+OiHK6T9PFAvwmmjnydSOQCtscFnfB8Rx
y21FaRgQdZIFYzeyJzxI50lnbEdowGGnoxLsLzrpzftwSCVVpca346ru6NDv57zL
hcYmNdmO1biAzZDJVzftR1r0N9hQAh7pe8y6UxefZkAswQeicWkguivA4m6OMGjH
EueMKWSqit3Vk3flaF9rZdprLRUZzA2jvzJ10KjaYP5C+KumkupGMDLyqAMDi+qJ
3NKpzEANPFoyK61uON1aPLmhp28FVJBj1GPB6Lr49u+dJCQ0JciKVb34YZtAjg1G
IGV9dD9SV6hm8CuxAHaGkpyjCBYJOmrIAJOMnwN3p8rtScrK+1M1YEmJXgb+K76h
vVFZvySZa0OyhG2KD2Pse3wdxJAAStYWuEyfgabJeOtqpIjL17lZcRF2YrwWcYDx
W+GLhUT9uT/CVCaoFDhjs5QKBIL8eBA6AUa3vNeGApTvEQOg0U8BQcSPZBAq4AFT
mdtbiCZ6x/LeOxlT6Emu3ityzv+EhEQ+gom5v5moo8enmC1GLrl9ez/JE1UUqO3L
Mz/0N5Kxp9twcSGQfXWA
=7COJ
-----END PGP SIGNATURE-----


Reply to: