0 +0200
@@ -1,3 +1,11 @@
+trilinos (12.18.1-2) unstable; urgency=medium
+
+ * Team upload.
+ * libtrilinos-ml-dev Depends: libtrilinos-aztecoo-dev.
+Closes: #989488.
+
+ -- Drew Parsons Sat, 05 Jun 2021 12:50:20 +0200
+
trilinos (12.18.1-1) unstable; urgency=medium
* New upstream re
for demos properly legible.
+
+ -- Drew Parsons Wed, 09 Jun 2021 13:23:16 +0200
+
dolfin (2019.2.0~git20201207.b495043-4) unstable; urgency=medium
* debian/tests: add ppc64el to the list of arches skipping some tests
diff -Nru dolfin-2019.2.0~git20201207.b495043/debian/rules
dolfin-2019.2.0
~git20210130.c14cb0a-5) unstable; urgency=medium
+
+ * use triple-slash (file:///) for mathjax local url replacement to
+make docs for demos properly legible.
+
+ -- Drew Parsons Wed, 09 Jun 2021 14:59:59 +0200
+
dolfinx (2019.2.0~git20210130.c14cb0a-4) unstable; urgency=medium
* update
Package: nfs-common
Followup-For: Bug #883194
X-Debbugs-Cc: debian-release@lists.debian.org
I was surprised to see python2 pulled in on a new bullseye
installation using nfs.
It's a trivial patch of course to update the hashbangs for mountstats
and nfsiostat in nfs-common 1:1.3.4-5 to python3.
A
Package: nfs-common
Followup-For: Bug #883194
X-Debbugs-Cc: debian-release@lists.debian.org
Control: severity 883194 serious
Control: usertag 883194 py2removal
Since removing Python2 is a release goal for bullseye (other packages
have been removed because of their python2 dependencies), and since
On 2021-06-28 00:35, Diederik de Haas wrote:
On zondag 27 juni 2021 22:37:10 CEST Salvatore Bonaccorso wrote:
Let's ask the release team instead. Here my arguments why: nfs-utils
needs a major rehaul, this was not possible to finish in time for
bullseye, so this means nfs-utils is generally in n
Thanks Ivo, I'll prepare a filtered diff for consideration.
Drew
On 2021-03-16 17:32, Ivo De Decker wrote:
Control: tags -1 moreinfo
...
[ ] attach debdiff against the package in testing
We ask these this for a reason. The current diff between the version in
testing and unstable is very
On 2021-03-16 17:32, Ivo De Decker wrote:
Control: tags -1 moreinfo
...
On Sun, Mar 14, 2021 at 09:01:26PM +0100, Drew Parsons wrote:
upstream released petsc 3.14.5 with bug fixes only.
This will help improve the stability of the package over the lifetime
of the bullseye release.
I'
: libmumps-64pord-seq-5.3
+(not libmumps-seq-dev, libmumps-seq-5.3). Closes: #985514.
+ * Standards-Version: 4.5.1
+
+ -- Drew Parsons Sat, 20 Mar 2021 04:52:40 +0100
+
mumps (5.3.5-1) unstable; urgency=medium
* Team upload.
diff -Nru mumps-5.3.5/debian/control mumps-5.3.5/debian/control
s pkg-config file
+ (not available in libhdf5-mpi-dev 1.10.4+repack-10 for buster)
+- revert use of system liblzf-dev from 2.10.0-8
+ * use wildcard for mathjax version when replacing references
+(but only replace references if they are found)
+
+ -- Drew Parsons Tue, 30 Mar 2021 13:
3-30 13:41, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
On Tue, 2021-03-30 at 13:18 +0200, Drew Parsons wrote:
[ Reason ]
Bug#984638 has requested a backport of h5py to buster in order to
support other packages used on it.
Usually I'd expect that wording to mean an upload to buster-ba
On 2021-04-08 14:29, Graham Inggs wrote:
Unblocked.
Thanks Graham.
While petsc and release is close to mind, I'd like to request
preauthorization for petsc/3.14.5+dfsg1-3 to make a minimal update to
fix Bug#985659 (fixing broken symlinks in docs).
Beyond that, what is your mood with respec
On 2021-04-08 15:25, Paul Gevers wrote:
Hi Drew,
On 08-04-2021 15:01, Drew Parsons wrote:
While petsc and release is close to mind, I'd like to request
preauthorization for petsc/3.14.5+dfsg1-3 to make a minimal update to
fix Bug#985659 (fixing broken symlinks in docs).
You stretch
excreate.c
+- PR3722_umfpack_ordering.diff, use default umfpack ordering
+ since much faster than PETSc ordering
+- PR3728_DM_anchor_initialize.diff, initialize variable in DM
+ anchor calculation
+
+ -- Drew Parsons Fri, 09 Apr 2021 13:28:02 +0200
+
petsc (3.14.5+dfsg1-2) unstable; urgency=medium
*
ogadrolibs (1.93.1-3) unstable; urgency=medium
+
+ * debian patch export_molecule_save_68fb007.patch applies upstream
+commit 68fb007 (PR#517) to fix the Save dialog when exporting
+molecules (upstream issue #439).
+
+ -- Drew Parsons Wed, 14 Apr 2021 22:48:26 +0200
+
avogadrolibs (1.93.1-
ioned python.
+Closes: #987618.
+
+ [ Drew Parsons ]
+ * add lintian overrides to ignore breaks-without-version warning in
+libpetsc-real3.14 and libpetsc-complex3.14 from Breaks: libpetsc*3.10*
+and Breaks libslepc*3.10*. The version is embedded in the package
+names.
+
+ -- Drew Parso
@@
+golang-go.opencensus (0.22.4-2) unstable; urgency=medium
+
+ * Team upload.
+ * debian patch skip_flaky_test.patch skips Test_Worker_MultiExport
+in stats/view. The test is flaky, occasionally failing.
+See Debian Bug#988250, upstream Issue#1259.
+
+ -- Drew Parsons Fri, 14 May 2021 23:11
On 2021-05-15 07:53, Paul Gevers wrote:
Hi Drew,
On 14-05-2021 23:43, Drew Parsons wrote:
Please unblock package golang-go.opencensus
Assuming all the test will pass, there's nothing for us to do as the
package isn't blocked in this stage of the freeze.
Thanks Paul. I forgo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-scie...@lists.debian.org, Anton Gladky
I'd like to proceed with a transition of the numerical library stack.
This involves
superlu 5.2.2+dfsg1 -> 5.3.0+dfsg1
On 2021-10-15 21:02, Sebastian Ramacher wrote:
Control: tags -1 confirmed
On 2021-10-12 13:09:02 +0200, Drew Parsons wrote:
I'd like to proceed with a transition of the numerical library stack.
This involves
...
Please go ahead
Cheers
Ben file:
title = "numerical lib
On 2021-10-16 00:01, Drew Parsons wrote:
On 2021-10-15 21:02, Sebastian Ramacher wrote:
I'd like to proceed with a transition of the numerical library stack.
This involves
...
Thanks Sebastian. I'll start from superlu (and xtensor already
underway).
Waiting for the trilin
The sundials 5.8.0 test build in experimental looks successful.
Probably not worth waiting for the mipsel build, it's been slow to
build, especially for experimental.
Drew
On 2021-10-22 17:40, Anton Gladky wrote:
Great, thanks! Will do it very shortly.
Anton
Sebastian Ramacher schrieb
5 Uhr schrieb Drew Parsons
:
The sundials 5.8.0 test build in experimental looks successful.
Probably not worth waiting for the mipsel build, it's been slow to
build, especially for experimental.
On 2021-10-22 14:35, Sebastian Ramacher wrote:
On 2021-10-12 13:09:02, Drew Parsons wrote:
...
I'd like to proceed with a transition of the numerical library stack.
...
(along with other fenics components). There is currently some problem
with fenics-dolfinx 1:0.3.0-4 on 32-bit arches
On 2021-10-30 11:04, Sebastian Ramacher wrote:
On 2021-10-30 00:50:49 +0200, Drew Parsons wrote:
I've got dolfinx passing (or skipping) its own tests on 32-bit.
There's a problem with 32-bit MPI though. i386 and armhf are failing
to run
pytest over python unit tests in MPI
...
On 2021-10-31 20:57, Anton Gladky wrote:
sundials_5.8.0 is in unstable already.
Thanks Anton.
Is deal.ii the core blocker at this point? Looks like it has other
issues, Bug#996277, not related to the numerical library transition.
It's scheduled for removal next week.
Drew
On 2021-11-03 20:57, Sebastian Ramacher wrote:
Source: hypre
Severity: serious
...
The real blocker is hypre, specifically:
hypre (2.18.1-1) experimental; urgency=medium
.
* Team upload.
* New upstream release.
* Standards-Version: 4.4.1
* Provide library binary package as libhypr
On 2021-11-04 21:41, Sebastian Ramacher wrote:
On 2021-11-03 22:33:01 +0100, Drew Parsons wrote:
...
The problem that hypre 2.18.1-1 (un-versioned libhypre) intended to
solve is
that hypre is ABI-ignorant
(https://github.com/hypre-space/hypre/issues/56),
so each point patch release would have
On 2021-11-04 22:35, Drew Parsons wrote:
On 2021-11-04 21:41, Sebastian Ramacher wrote:
On 2021-11-03 22:33:01 +0100, Drew Parsons wrote:
...
Is it best to revert back to strict Policy 8.1 compliance, which will
slow
down hypre patch release updates?
Yes. Having to wait for binNEW to being
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
We've got a pile-up of numerical libraries waiting in experimental.
I'd like to clear them out into unstable. This will also let
scalapack rebuild against mpich 4.
The transitions are:
On 2022-03-05 12:29, Sebastian Ramacher wrote:
Control: tags -1 confirmed
On 2022-03-01 13:34:21 +0100, Drew Parsons wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
We've got a pile-up of numerical libraries waiti
Control: block 1006648 by 1006615
On 2022-03-05 12:29, Sebastian Ramacher wrote:
Control: tags -1 confirmed
On 2022-03-01 13:34:21 +0100, Drew Parsons wrote:
The transitions are:
scalapack 2.1 → 2.2
scotch 6.1 → 7.0
hypre 2.22 → 2.23
petsc 3.15 → 3.16
slepc 3.15 → 3.16
On 2022-03-16 09:27, Sebastian Ramacher wrote:
On 2022-03-15 20:33:02 +0100, Drew Parsons wrote:
Control: block 1006648 by 1006615
On 2022-03-05 12:29, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
>
> On 2022-03-01 13:34:21 +0100, Drew Parsons wrote:
> >
> >
On 2023-02-04 18:02, Adrian Bunk wrote:
Usertags: binnmu
nmu pyfai_0.21.3+dfsg1-2 . ANY . unstable . -m "Rebuild to pick up
python3-h5py dependency (see #1030220)"
nmu unifrac_1.2-3 . ANY . unstable . -m "Rebuild to pick up
python3-h5py dependency (see #1030220)"
nmu xraylarch_0.9.58+ds1-5 . ANY
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: sc...@packages.debian.org
Control: affects -1 + src:scipy
Please unblock package scipy
This is a prerequest, before uploading.
[ Reason ]
scipy is central tool for numerical
Copying the upstream scipy 1.10.1 Release Notes for your convenience.
From https://docs.scipy.org/doc/scipy/release.1.10.1.html
SciPy 1.10.1 is a bug-fix release with no new features compared to
1.10.0.
Issues closed for 1.10.1
#14980: BUG: Johnson’s algorithm fails without negative cyc
errors by
+asserting use of Gtk 3.
+ * Standards-Version: 4.6.2
+
+ -- Drew Parsons Thu, 09 Mar 2023 02:24:59 +0100
+
opendrop (3.3.1-4) unstable; urgency=medium
* debian/patches/sundials_nvector_API6.patch updates sundials
diff -Nru opendrop-3.3.1/debian/control opendrop-3.3.1/debian
-mpich.README.Debian to document the need to use
+ARMCI_USE_WIN_ALLOCATE=0 when running nwchem with MPICH 4.0.2
+(binary nwchem.mpich, fixed in mpich 4.0.3).
+See upstream Issue#633.
+
+ -- Drew Parsons Sun, 19 Mar 2023 15:01:42 +0100
+
nwchem (7.0.2-3) unstable; urgency=medium
ci-mpi (0.3.1~beta-7) unstable; urgency=medium
+
+ * Team upload.
+ * run build-time tests on only 1 process if only 1 CPU is available.
+Closes: #1031064.
+ * debian/tests: don't run mpich tests on s390x. Closes: #1009772.
+
+ -- Drew Parsons Sun, 19 Mar 2023 14:08:54 +0100
+
armci-m
+
+ -- Drew Parsons Tue, 30 Apr 2019 16:42:08 +0800
+
golang-golang-x-net-dev (1:0.0+git20181201.351d144+dfsg-2) unstable;
urgency=medium
* Remove obsolete patch for s390. Closes: #916236.
diff -Nru
golang-golang-x-net-dev-0.0+git20181201.351d144+dfsg/debian/patches/CVE-2018-17846_d26f9f9.patch
Paul Gevers wrote:
I have decided that I'll let golang-golang-x-net-dev migrate to testing
do the binNMUs in buster. I'll leave the bug open until the rebuilds
have succeeded to keep track of the issue.
Is there a buildd url we can use to track the status of the binNMUs? Or
something akin to
Just want to say, thanks Shengjing, Tobias and Paul for working through
the issues to get golang ready for buster.
Drew
On 2019-06-19 01:01, Paul Gevers wrote:
Hi Drew,
On 18-06-2019 16:22, Drew Parsons wrote:
Just want to say, thanks Shengjing, Tobias and Paul for working
through
the issues to get golang ready for buster.
Thank you for the thanks, but to be fair, it isn't finished. The
golang-golang-
+0800
+++ python-periodictable-1.5.0/debian/changelog 2019-06-26 16:18:35.0
+0800
@@ -1,3 +1,10 @@
+python-periodictable (1.5.0-8) unstable; urgency=medium
+
+ [ Stuart Prescott ]
+ * Fix typo in Suggests entry for documentation (Closes: #923744).
+
+ -- Drew Parsons Wed, 26 Jun 2019 16:18:35
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Hypre 2.16.0 is uploaded to unstable so we need binNMUs for a small
transition.
nmu petsc_3.10.5+dfsg1-1 . ANY . unstable . -m "rebuild against hypre 2.16.0"
After petsc is done, slepc and
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I'd like to proceed with the next upgrade of the numerical library
stack*.
superlu-dist 7.2.0 -> 8.1.0
hypre 2.23.0 -> 2.25.0
mumps 5.4.1 -> 5.5.0
petsc 3.16
On 2022-08-16 21:12, Sebastian Ramacher wrote:
Control: tags -1 confirmed
On 2022-07-31 12:47:15 +0200, Sebastian Ramacher wrote:
On 2022-07-26 20:34:10 +0200, Drew Parsons wrote:
>
> I'd like to proceed with the next upgrade of the numerical library
> stack*.
>
> superlu-d
On 2022-08-16 21:44, Drew Parsons wrote:
We're conflicted by pmix Bug#1017356.
I would be better if MPI (ucx/pmix) upgrades were handled as a
transition tested first in experimental :(
The pmix problem is now worked around by reverting back to the earlier
version. I'll procee
On 2022-08-31 11:57, Drew Parsons wrote:
The pmix problem is now worked around by reverting back to the earlier
version. I'll proceed with the transition of the numerical stack now.
Lower level libraries are uploaded. We'll want mumps level 2 built to
prepare trilinos for the p
On 2022-09-01 23:32, Sebastian Ramacher wrote:
Lower level libraries are uploaded. We'll want mumps level 2 built to
prepare trilinos for the petsc build.
Scheduled mumps level 2 (except trilinos)
^^^
Wait no, it's trilinos that I'm waiting for! petsc
All uploads are done now. Let the binNMUs rip.
Drew
On 2022-09-08 10:19, Sebastian Ramacher wrote:
On 2022-09-04 10:02:53 +0200, Drew Parsons wrote:
All uploads are done now. Let the binNMUs rip.
The rebuilds have been done. The transition is now blocked on #1019287.
Bug#1019287 is now fixed, all new builds have now migrated to testing
On 2022-09-19 12:47, Sebastian Ramacher wrote:
On 2022-09-19 11:54:36 +0200, Drew Parsons wrote:
This transition can be considered done, if we're happy with the state
of
rheolef reported by
https://release.debian.org/transitions/html/auto-mumps.html
https://buildd.debian.org/s
On 2022-09-22 10:07, Sebastian Ramacher wrote:
On 2022-09-19 13:28:21 +0200, Drew Parsons wrote:
On 2022-09-19 12:47, Sebastian Ramacher wrote:
> On 2022-09-19 11:54:36 +0200, Drew Parsons wrote:
> > This transition can be considered done, if we're happy with the
> >
On 2022-09-22 10:07, Sebastian Ramacher wrote:
On 2022-09-19 13:28:21 +0200, Drew Parsons wrote:
On 2022-09-19 12:47, Sebastian Ramacher wrote:
> On 2022-09-19 11:54:36 +0200, Drew Parsons wrote:
> > This transition can be considered done, if we're happy with the
> >
ll
request.
https://salsa.debian.org/science-team/getfem/-/merge_requests/3
I can also add the transition to a newer mumps in the same branch if
you like.
Best regards
Konstantinos
On Thu, Sep 22, 2022 at 2:12 PM Drew Parsons
wrote:
On 2022-09-22 10:07, Sebastian Ramacher wrote:
On 2022-09-19 13:2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: Anton Gladky
We'd like to update the numerical library stack in time for the new
stable release.
Affected libraries are
hypre2.25.0 -> 2.26.0
petsc/slepc3.17
The hypre/petsc part of this transition is complete.
The sundials part is waiting for dyssol to be patched. Anton is
preparing this.
Drew
On 2022-11-29 23:34, Sebastian Ramacher wrote:
Control: tags -1 confirmed
Hi Drew
On 2022-11-29 12:16:55 +0100, Drew Parsons wrote:
Package
On 2022-12-31 17:59, Anton Gladky wrote:
Hi Sebastian,
thanks for noting it! #1027402 is fixed now in unstable (that was wrong
version
in Breaks+Replaces).
Am Sa., 31. Dez. 2022 um 14:20 Uhr schrieb Sebastian Ramacher
:
It's now in unstable. Please also fix #1027402.
Looks like deal.ii
On 2019-07-26 08:57, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here: 933043:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933043.
I missed the name of sundials in the second set of binNMUs with slepc:
nmu pets
On 2019-07-31 20:58, Paul Gevers wrote:
All those have been built now. However, hypre will not be able to
migrate because the autopkgtest of petsc is failing, as it does in
unstable as well.
Awkward. I'll check if petsc 3.11 has the same problem.
Drew
On 2019-07-31 22:14, Drew Parsons wrote:
On 2019-07-31 20:58, Paul Gevers wrote:
All those have been built now. However, hypre will not be able to
migrate because the autopkgtest of petsc is failing, as it does in
unstable as well.
Awkward. I'll check if petsc 3.11 has the same pr
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
The hypre 2.16.0 upgrade revealed an incompatibility between petsc 3.10
and hypre 2.16.0. PETSc upstream has dealt with the issue with a
couple of recent patches. The best way to stabil
I noticed a lot of transition tracking bugs for old transitions are
still open at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=release.debian@packages.debian.org;tag=transition
Just wondering, what is the Release Team's protocol for closing these
old transition bugs?
Would you lik
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
golang-github-google-pprof is holding up other Go packages from
migrating to testing. pprof itself is not migrating since it was
built by the uploader and never built on the buildds. So this
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 ~
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
armci-mpi has been updated, so ga should be rebuilt to match
(nwchem binNMU will follow after this)
nmu ga_5.7-4 . ANY . unstable . -m "rebuild against armci-mpi
0.0~git20190412.643ea1a"
-
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
dolfin has a tight dependency on pybind11 (we were burnt in the past
by mismatching pybind11 builds), so requires binNMU to update.
nmu dolfin_2019.1.0-5 . ANY . unstable . -m "Rebuild again
On 2019-09-29 21:17, Paul Gevers wrote:
Hi Drew,
On 21-09-2019 06:23, Drew Parsons wrote:
armci-mpi has been updated, so ga should be rebuilt to match
(nwchem binNMU will follow after this)
nmu ga_5.7-4 . ANY . unstable . -m "rebuild against armci-mpi
0.0~git20190412.643ea1a"
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Following binNMU #940866 for ga, nwchem now needs to be rebuilt
against armci-mpi 0.0~git20190412.643ea1a.
As discussed in #940866 both ga and nwchem link statically against
armci.
nmu nwch
On 2019-10-04 16:19, Sébastien Villemot wrote:
Dear ftpmasters,
If time permits, would it be possible for you to fasttrack nlopt 2.6.1-
1 that stands in the NEW queue?
The version in unstable currently fails to build and is blocking the
octave transition. The version in the NEW queue should sol
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 shoul
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 sund
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
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
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 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 b
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
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 giv
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I'd like to proceed with the PETSc 3.12 transition.
The MUMPS 5.2.1 is also ready to go, but I think it might be more
constructive to demonstrate via testing migration that the new petsc
On 2019-12-05 20:22, Paul Gevers wrote:
Hi Drew,
On 02-12-2019 09:31, Drew Parsons wrote:
I'd like to proceed with the PETSc 3.12 transition.
The MUMPS 5.2.1 is also ready to go, but I think it might be more
constructive to demonstrate via testing migration that the new petsc
is stable
On 2019-12-14 20:40, Paul Gevers wrote:
On 02-12-2019 09:31, Drew Parsons wrote:
I'd like to proceed with the PETSc 3.12 transition.
The MUMPS 5.2.1 is also ready to go, but I think it might be more
constructive to demonstrate via testing migration that the new petsc
is stable with th
On 2019-12-15 17:20, Paul Gevers wrote:
In that case in the spirit of a package deal, I suggest
throwing in scalapack 2.1.0 as well.
Go ahead.
Thanks Paul, proceeding.
Drew
On 2019-12-15 17:20, Paul Gevers wrote:
Hi Drew,
In that case in the spirit of a package deal, I suggest
throwing in scalapack 2.1.0 as well.
Go ahead.
ga will need a binNMU for scalapack too.
It gets missed in some transition lists since it provides static
libraries, but it shows up in
On 2019-12-21 20:43, Paul Gevers wrote:
Hi Drew,
On 20-12-2019 23:56, Drew Parsons wrote:
ga will need a binNMU for scalapack too.
Scheduled.
Well huh. The ga build failed, go figure. I'll dig into it.
Thanks Paul,
Drew
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
mshr needs to be rebuild against dolfin, otherwise we get
'unknown base type "dolfin::Variable"' errors.
Please binNMU mshr in unstable:
nmu mshr_2019.2.0~git20200213.8895485+dfsg1-2 . ANY
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I wanted to make a combo transition with superlu-dist 5.3.1 and hypre
2.20. But the hypre upgrade requires superlu-dist 5.3 and
superlu-dist 5.3 FTBFS (see
https://github.com/xiaoyeli/su
On 2020-09-30 17:38, Sebastian Ramacher wrote:
So let's proceed with the MUMPS 5.3.3 transition on its own and get
the mumps upgrade into the archives
Please go ahead.
Thanks Sebastian.
Interestingly, upstream has just released MUMPS 5.3.4.
And at the same time upstream has just confirme
Hi Alastair, I'm getting a PMIX undefined symbol in new builds of MUMPS
5.3.3 amd armel and mipsel,
see https://buildd.debian.org/status/package.php?p=mumps
The armel log at
https://buildd.debian.org/status/fetch.php?pkg=mumps&arch=armel&ver=5.3.3-2&stamp=1601578910&raw=0
reports:
...
mpifort
I uploaded petsc 3.13.6+dfsg1-1 (one of mumps' reverse dependencies) to
unstable in order to clear the way for PETSc 3.14 in experimental.
It built "successfully" against the old mumps on armel and mipsel but
the openmpi inconsistency causes dolfin to FTBFS on these failing
arches.
I think p
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I had an oopsie uploading petsc4py 3.14.0-1 to unstable instead of
experimental, and it got accepted immediately from the NEW queue
before the message on IRC was read to reject it.
I'd t
Thanks Sebastian, proceeding.
On 2020-10-28 21:29, Sebastian Ramacher wrote:
Control: tags -1 + confirmed
On 2020-10-28 19:54:15 +0800, Drew Parsons wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I had an oopsie
On 2020-10-28 21:29, Sebastian Ramacher wrote:
Control: tags -1 + confirmed
On 2020-10-28 19:54:15 +0800, Drew Parsons wrote:
...
I'd therefore like to proceed with the transition of the scientific
numerical library stack to get the packages back into consistent
versions.
The source pac
On 2020-11-10 03:32, Adrian Bunk wrote:
On Tue, Nov 10, 2020 at 01:45:04AM +0800, Drew Parsons wrote:
...
You can see it got applied in the last successful mips64el build,
https://buildd.debian.org/status/fetch.php?pkg=dolfin&arch=mips64el&ver=2019.2.0%7Egit20200629.946dbd3-3%2B
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
The latest version of superlu-dist introduces a API/ABI bump (it came
in superlu-dist 6.3, but we can pick it up from v6.4)
The new package is currently waiting in the NEW queue aimed at
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Judging by the dolfin debci failures, slepc needs to be rebuilt.
Either that, or dolfin itself needs a rebuild.
Dolfin tests report:
File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/_
upload.
+ * debian patch fix_dtype_random_title_1444936.patch applies
+upstream commit #1444936 to fix random dtype titles used in tests.
+Closes: #971806.
+ * Standards-Version: 4.5.1
+
+ -- Drew Parsons Wed, 17 Feb 2021 21:33:33 +0100
+
python-hdf5storage (0.1.15+git20200608.09dfc5f-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package petsc
[ Reason ]
upstream released petsc 3.14.5 with bug fixes only.
This will help improve the stability of the package over the lifetime
of the bullseye release.
Control: retitle -1 release.debian.org: britney: publish a dose report
for each non-migrable item
On Mon, Apr 13, 2020 at 07:01:00PM +0800, Drew Parsons wrote:
A current example is hdf5 1.10.6+repack-1, tracker page
https://tracker.debian.org/pkg/hdf5. Listed as ready for migration for
several days
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I think the joint mumps 5.3.1 / petsc 3.13 / slepc 3.13 transition is
ready to proceed. Packages seem well behaved in experimental.
Auto transition trackers are already in place.
1 - 100 of 253 matches
Mail list logo
