On 22 October, 2017 - Dirk Hohndel wrote:
> With all the confusion (caused by me, no one else to blame - ok, I blame
> the bad internet here which made it worse) I decided to call this one
> 4.7.1. The OBS builds of 4.7.0 snuck out and I didn't realize until much
> later that they were available f
> On Oct 22, 2017, at 7:20 PM, Dirk Hohndel wrote:
>
> No, the mistake is mine for putting the wrong tar ball there. Should be fixed
> now.
And my release tooling has been improved to prevent this from happening again.
/D
___
subsurface mailing list
> On Oct 22, 2017, at 5:44 PM, Gaetan Bisson wrote:
>
> [2017-10-22 11:18:20 -1000] Gaetan Bisson:
>> Thanks for this new release! I'm ashamed I can't get subsurface-4.7.1 to
>> compile against the new libdivecomputer-subsurface-branch tarball...
>
> Ah, my mistake, I used the tarball from:
>
[2017-10-22 11:18:20 -1000] Gaetan Bisson:
> Thanks for this new release! I'm ashamed I can't get subsurface-4.7.1 to
> compile against the new libdivecomputer-subsurface-branch tarball...
Ah, my mistake, I used the tarball from:
https://subsurface-divelog.org/downloads/libdivecomputer-s
I must have packed the wrong libdivecomputer 😨
What didn't I mess up in this release???
Will check / fix when we're back at the hotel.
/D
On October 22, 2017 5:18:20 PM GMT-04:00, Gaetan Bisson
wrote:
>Hi Dirk,
>
>Thanks for this new release! I'm ashamed I can't get subsurface-4.7.1
>to
>com
Hi Dirk,
Thanks for this new release! I'm ashamed I can't get subsurface-4.7.1 to
compile against the new libdivecomputer-subsurface-branch tarball... I'm
getting errors like this:
In file included from /build/src/Subsurface-4.7.1/core/qt-ble.cpp:18:0:
/build/src/Subsurface-4.7.1/./core/qt-ble.h:
> On Oct 22, 2017, at 11:13 AM, Martin Gysel wrote:
>
> Dirk, can you please also tag the corresponding libdc version (I suppose
> c0f025b?)
Done; and no, we use a newer commit: 0099aeeb7088
/D___
subsurface mailing list
subsurface@subsurface-divelog
Am 22.10.2017 um 12:46 schrieb Dirk Hohndel:
> With all the confusion (caused by me, no one else to blame - ok, I blame
> the bad internet here which made it worse) I decided to call this one
> 4.7.1. The OBS builds of 4.7.0 snuck out and I didn't realize until much
> later that they were available