Colin, Richard,
Thanks again for the discussion here. The upstream maintainer was willing
to patch the change onto their 3.3 support branch, from which I applied the
patches onto the existing 3.3.7 package and released the result to PPA.
I've filed a bug on Launchpad with the details as suggested:
> No, if you're filing bugs on Ubuntu, you should use /ubuntu, not
> /debian, so https://launchpad.net/ubuntu/+source/eigen3.
> (https://launchpad.net/debian exists mainly as a convenience and as a
> by-product of the way we sync changes from Debian; it's not part of
> Debian's development workflow
On Tue, Feb 25, 2020 at 03:48:14PM -0500, Mike Purvis wrote:
> As far as launchpad engagement, it looks like this would be the page for
> that, but the bugtracker isn't active on it:
> https://launchpad.net/debian/+source/eigen3
No, if you're filing bugs on Ubuntu, you should use /ubuntu, not
/deb
On Tue, Feb 25, 2020 at 02:38:54PM -0600, Richard Laager wrote:
> Without knowing the specifics of the patch, most likely. But you're
> running out of time. At this point, it's too late to get something into
> Debian testing and have it migrate to Focal. (I think Focal is syncing
> from Debian test
Yeah, I doubt Debian upstream would care as they're not about to commit to
an LTS— they can just wait for Eigen 3.4. :)
I have some familiarity with backporting and general dsc/deb preparation
but am by no means an expert. I'll take a quick look and see if it's
something I can sort out.
As far as
On 2/25/20 2:29 PM, Mike Purvis wrote:
> Would it be reasonable to patch this change onto the current 3.3.7
> version to avoid dependent packages turning off warnings or doing other
> workarounds?
Without knowing the specifics of the patch, most likely. But you're
running out of time. At this poin