Re: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-26 Thread Anton Gladky
Hi guys, thanks for taking care of it. I can only promise to keep in mind, that ceres should be rebuilt after each new eigen3 upload and trigger it if no any other proper solution for this problem exists. Regards. Anton On Tue, Feb 26, 2019, 19:23 Philipp Huebner Am 26.02.19 um 11:25 schrieb

Re: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-26 Thread Philipp Huebner
Am 26.02.19 um 11:25 schrieb Andreas Tille: > On Tue, Feb 26, 2019 at 10:45:52AM +0100, Philipp Huebner wrote: >> >>> I mean: There is no *effective* change since the Build-Depends we set is >>> fullfilled anyway by the existing packages. Its just that it is >>> explicitly declared in the package

Re: Bug#868355: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-26 Thread Mo Zhou
On Tue, Feb 26, 2019 at 11:25:49AM +0100, Andreas Tille wrote: > > The eigen3 maintainer and I are happy to simply rebuild affected > > packages after every eigen3 update, but Emilio considers it an upstream bug. > > Unfortunately I could not find anybody able to shed more light on the > > eigen3 t

Re: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-26 Thread Andreas Tille
Hi Philipp, On Tue, Feb 26, 2019 at 10:45:52AM +0100, Philipp Huebner wrote: > > > I mean: There is no *effective* change since the Build-Depends we set is > > fullfilled anyway by the existing packages. Its just that it is > > explicitly declared in the package metadata. > > IMO that's a valid

Re: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-26 Thread Philipp Huebner
Hi, Am 26.02.19 um 08:54 schrieb Andreas Tille: >>> to Git. Is there any reason not to upload this and simply fix #883619. >>> Looks like a pretty low hanging fruit to fix an RC bug and save the >>> package for Buster that I can not imagine nobody else would have >>> harvested it. >> >> It's only

Re: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-25 Thread Andreas Tille
Hi, On Tue, Feb 26, 2019 at 03:13:39PM +0800, Drew Parsons wrote: > On 2019-02-26 14:54, Andreas Tille wrote: > > > > I just pushed > > +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium > ... > > to Git. Is there any reason not to upload this and simply fix #883619. > > Looks like a pretty low

Re: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-25 Thread Drew Parsons
On 2019-02-26 14:54, Andreas Tille wrote: I just pushed +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium ... to Git. Is there any reason not to upload this and simply fix #883619. Looks like a pretty low hanging fruit to fix an RC bug and save the package for Buster that I can not imagine

Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev

2019-02-25 Thread Andreas Tille
Hi, I just pushed diff --git a/debian/changelog b/debian/changelog index db364aa..a10efd1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium + + * Team upload. + * Bump versioned Build-Depends: libeigen3-dev (>= 3.3.4) +