Hi,
Concerning the patch: It seems like -O2 is the default in Debian now anyway.
Will the patch still work as it is?
I did some investigations on platti.debian.org. I have no idea what the problem
is. My hunch is that compiler optimization breaks the code here. If I add a
simple print statement
Hi,
Am Thu, Nov 23, 2023 at 09:32:31AM +0100 schrieb Sebastian Ramacher:
On 2023-11-12 21:42:20 +0100, Markus Blatt wrote:
Dear Debian release team,
A new upstream release of OPM is available. To ease migration to testing I am
requesting a mini-transition. Uploading to unstable would
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-scie...@lists.debian.org
Dear Debian release team,
A new upstream release of OPM is available. To ease migration to testing I am
requesting a mini-transition. Upload
Hi Paul,
Am Sun, Apr 16, 2023 at 10:03:07PM +0200 schrieb Paul Gevers:
On 13-04-2023 22:56, Markus Blatt wrote:
None, because no real code is changed
Can you elaborate why this is needed? I confirm I see nothing of interest.
you are right, there are no real changes in here.
The only
/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+opm-upscaling (2022.10+ds-4) unstable; urgency=medium
+
+ * Removed stale static benchmarks to really not need git.
+
+ -- Markus Blatt Thu, 09 Mar 2023 13:36:31 +0100
+
+opm-upscaling (2022.10+ds-3) unstable; urgency=medium
+
+ * d/control
missing imported Alberta targets.
+ * d/control: Fixed version string used in binaries.
+
+ -- Markus Blatt Thu, 09 Mar 2023 13:31:04 +0100
+
opm-simulators (2022.10+ds-1) unstable; urgency=medium
* New upstream version 2022.10
diff --git a/debian/control b/debian/control
index 50cb90194
(2022.10+ds-4) unstable; urgency=medium
+
+ * d/(tests/)control: Limit the architectures to known working ones.
+
+ -- Markus Blatt Fri, 24 Mar 2023 09:43:28 +0100
+
+opm-models (2022.10+ds-3) unstable; urgency=medium
+
+ * Release to unstable (no-change)
+
+ -- Markus Blatt Wed, 08 Mar 2023 23:45:45
-material (2022.10+ds-4) unstable; urgency=medium
+
+ * d/(tests/)control: Limit the architectures to known working ones.
+
+ -- Markus Blatt Fri, 24 Mar 2023 09:33:42 +0100
+
+opm-material (2022.10+ds-3) unstable; urgency=medium
+
+ * d/control: Removed unneeded git from Build-Depends.
+
+ -- Markus
; urgency=medium
+
+ * d/control: Removed unneeded git from Build-Depends.
+
+ -- Markus Blatt Wed, 08 Mar 2023 23:49:15 +0100
+
+opm-grid (2022.10+ds-2) experimental; urgency=medium
+
+ * d/control: Bumped standards version to 4.6.2 (no-change)
+
+ -- Markus Blatt Mon, 09 Jan 2023 12:08:19 +0100
-common/2022.10+ds-7
diff --git a/debian/changelog b/debian/changelog
index 0af409a45..a011537d5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,23 @@
+opm-common (2022.10+ds-7) unstable; urgency=medium
+
+ * d/control: Limit the architectures to known working ones.
+
+ -- Markus Blatt
Dear Graham,
Am Sun, Jan 15, 2023 at 04:25:04PM +0200 schrieb Graham Inggs:
Hi Markus
On Tue, 3 Jan 2023 at 02:46, Markus Blatt wrote:
Nevertheless opm-grid, opm-material, opm-models, opm-simulators, and
opm-upscaling will
need to be rebuild for the mini-transition. Otherwise they won
Hi,
Am Wed, Mar 30, 2022 at 12:22:29PM +0200 schrieb Markus Blatt:
I think I figured out what the issue is. The cmake configuration files of all
opm modules
have an explicit list of libraries that need to be linked with the library of
the module and
this is always used for linking. This list
Hi,
Am Wed, Mar 30, 2022 at 09:45:30AM +0200 schrieb Markus Blatt:
Am Tue, Mar 29, 2022 at 09:28:22PM +0200 schrieb Graham Inggs:
It seems opm-simulators FTBFS in much the same way now after
opm-common has been rebuilt.
I will take a look and try to fix it. It seems there is a reference to
Hi,
Am Tue, Mar 29, 2022 at 09:28:22PM +0200 schrieb Graham Inggs:
It seems opm-simulators FTBFS in much the same way now after
opm-common has been rebuilt.
I will take a look and try to fix it. It seems there is a reference to
libpython3.9.so.
Markus
Hi,
I just took a look at the tracker and noticed that opm-common is level 3 and
opm-simulators is level 2. If build attempts for level 3 come after level 2
that migth explain the failure in the logs [1] and opm-common should be in a
level before opm-simulators.
If there is anything that I need
15 matches
Mail list logo