Bug#946855: Therion still fails on old proj dependency; loch fixed in upstream
Control: tags -1 +pending On Tue, Dec 17, 2019 at 01:55:54AM +, Olly Betts wrote: > On Mon, Dec 16, 2019 at 04:33:58PM +0100, Benedikt Hallinger wrote: > > It would be nice to recompile the package including the latest > > upstream sources, thank you! > > We usually update to the latest upstream sources only when upstream make > a release (since that's a strong signal that it's "ready"). If we start > pulling arbitrary snapshots from upstream git where we have to worry > about there being changes which might not yet be ready, so in between > we would usually apply a targetted fix for a problem. A handy illustration of why we do that popped up today: https://mailman.speleo.sk/pipermail/therion/2019-December/008086.html > So we can probably apply the tiny patch from > https://github.com/therion/therion/pull/151 but it would really make > sense for upstream to make an actual release. Upload with this patch applied on its way. Cheers, Olly
Bug#946855: Therion still fails on old proj dependency; loch fixed in upstream
Thank you Olly for that insights. In this case applying the patch would be good because currently the package therion is broken if one uses the „cs“ command. > Am 17.12.2019 um 02:55 schrieb Olly Betts : > >> On Mon, Dec 16, 2019 at 04:33:58PM +0100, Benedikt Hallinger wrote: >> Hello, i just wanted to inform you that therion still fails with the proj >> issue[1] on my system when installing from the new package 5.4.4ds1-4. >> >> Also the loch glx issue[2] was fixed recently in upstream (Olly did a patch >> on this in the last deb package which is obsoleted by Stachos upstream fix. >> >> It would be nice to recompile the package including the latest >> upstream sources, thank you! > > We usually update to the latest upstream sources only when upstream make > a release (since that's a strong signal that it's "ready"). If we start > pulling arbitrary snapshots from upstream git where we have to worry > about there being changes which might not yet be ready, so in between > we would usually apply a targetted fix for a problem. > > So we can probably apply the tiny patch from > https://github.com/therion/therion/pull/151 but it would really make > sense for upstream to make an actual release. > > Cheers, >Olly
Bug#946855: Therion still fails on old proj dependency; loch fixed in upstream
On Mon, Dec 16, 2019 at 04:33:58PM +0100, Benedikt Hallinger wrote: > Hello, i just wanted to inform you that therion still fails with the proj > issue[1] on my system when installing from the new package 5.4.4ds1-4. > > Also the loch glx issue[2] was fixed recently in upstream (Olly did a patch > on this in the last deb package which is obsoleted by Stachos upstream fix. > > It would be nice to recompile the package including the latest > upstream sources, thank you! We usually update to the latest upstream sources only when upstream make a release (since that's a strong signal that it's "ready"). If we start pulling arbitrary snapshots from upstream git where we have to worry about there being changes which might not yet be ready, so in between we would usually apply a targetted fix for a problem. So we can probably apply the tiny patch from https://github.com/therion/therion/pull/151 but it would really make sense for upstream to make an actual release. Cheers, Olly
Bug#946855: Therion still fails on old proj dependency; loch fixed in upstream
Package: therion Version: 5.4.4ds1-4 Hello, i just wanted to inform you that therion still fails with the proj issue[1] on my system when installing from the new package 5.4.4ds1-4. Also the loch glx issue[2] was fixed recently in upstream (Olly did a patch on this in the last deb package which is obsoleted by Stachos upstream fix. It would be nice to recompile the package including the latest upstream sources, thank you! [1] https://github.com/therion/therion/issues/130 [2] https://github.com/therion/therion/issues/158
