On 2019-11-09 05:45, Paul Gevers wrote:
Hi Drew,
On 03-11-2019 21:01, Paul Gevers wrote:
On 30-10-2019 08:26, Drew Parsons wrote:
So yes, the unversioned libhypre package name is certainly the option
that will preserve the greatest sanity (I'll proceed directly with
2.18.2 once you give the
Control: tags -1 confirmed
Hi Drew,
On 30-10-2019 08:26, Drew Parsons wrote:
> So yes, the unversioned libhypre package name is certainly the option
> that will preserve the greatest sanity (I'll proceed directly with
> 2.18.2 once you give the thumbs up).
Thumbs up.
Paul
signature.asc
On 2019-10-30 15:21, Drew Parsons wrote:
hypre 2.18.1 is now ready in experimental.
I've implemented the common libhypre option with shlibs patch-version
dependency. If this approach proves problematic in practice then we
can switch back to version-based library package names afterwards if
we
On 2019-10-18 15:56, Emilio Pozuelo Monfort wrote:
On 17/10/2019 17:05, Drew Parsons wrote:
Hi Emilio, this is rather awkward. Hypre upstream has just released
2.18.1, so
this would be the one to run the transition on.
...
"The hypre team currently does nothing to ensure application binary
On 2019-10-18 15:56, Emilio Pozuelo Monfort wrote:
On 17/10/2019 17:05, Drew Parsons wrote:
Control: tags -1 - confirmed
On 2019-10-17 15:23, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed
On 17/10/2019 05:53, Drew Parsons wrote:
On 2019-10-12 22:19, Emilio Pozuelo Monfort wrote:
On 17/10/2019 17:05, Drew Parsons wrote:
> Control: tags -1 - confirmed
>
> On 2019-10-17 15:23, Emilio Pozuelo Monfort wrote:
>> Control: tags -1 confirmed
>>
>> On 17/10/2019 05:53, Drew Parsons wrote:
>>> On 2019-10-12 22:19, Emilio Pozuelo Monfort wrote:
On 12/10/2019 16:08, Drew Parsons
Control: tags -1 - confirmed
On 2019-10-17 15:23, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed
On 17/10/2019 05:53, Drew Parsons wrote:
On 2019-10-12 22:19, Emilio Pozuelo Monfort wrote:
On 12/10/2019 16:08, Drew Parsons wrote:
Thanks Emilio. 2.18.0 is now released, and
Control: tags -1 confirmed
On 17/10/2019 05:53, Drew Parsons wrote:
> On 2019-10-12 22:19, Emilio Pozuelo Monfort wrote:
>> On 12/10/2019 16:08, Drew Parsons wrote:
>>>
>>> Thanks Emilio. 2.18.0 is now released, and waiting now in the new queue.
>>> Perhaps we should hold on a bit and jump
On 2019-10-12 22:19, Emilio Pozuelo Monfort wrote:
On 12/10/2019 16:08, Drew Parsons wrote:
Thanks Emilio. 2.18.0 is now released, and waiting now in the new
queue.
Perhaps we should hold on a bit and jump straight to 2.18.0. That
will save
having to process 2 transitions. What do you
On 2019-10-12 22:19, Emilio Pozuelo Monfort wrote:
Control: tags -1 - confirmed
Hi Drew,
On 12/10/2019 16:08, Drew Parsons wrote:
On 2019-10-12 21:59, Emilio Pozuelo Monfort wrote:
I'd like to proceed with the hypre transition to 2.17.0.
I've tested that petsc and sundials build
Control: tags -1 - confirmed
Hi Drew,
On 12/10/2019 16:08, Drew Parsons wrote:
> On 2019-10-12 21:59, Emilio Pozuelo Monfort wrote:
>>>
>>> I'd like to proceed with the hypre transition to 2.17.0.
>>>
>>> I've tested that petsc and sundials build successfully with the new
>>> hypre.
>>
>> Please
On 2019-10-12 21:59, Emilio Pozuelo Monfort wrote:
I'd like to proceed with the hypre transition to 2.17.0.
I've tested that petsc and sundials build successfully with the new
hypre.
Please go ahead.
Thanks Emilio. 2.18.0 is now released, and waiting now in the new
queue. Perhaps we
Control: tags -1 confirmed
On 17/09/2019 17:35, Drew Parsons wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> I'd like to proceed with the hypre transition to 2.17.0.
>
> I've tested that petsc and sundials build
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I'd like to proceed with the hypre transition to 2.17.0.
I've tested that petsc and sundials build successfully with the new
hypre.
Ben file:
title = "hypre";
is_affected = .depends ~
14 matches
Mail list logo
