[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#941068: marked as done (nmu: dolfin_2019.1.0-5)

Your message dated Sun, 29 Sep 2019 15:04:58 +0200
with message-id <9b49928c-9e4c-edce-98c7-885f42a6fc0e@debian.org>
and subject line Re: Bug#941068: nmu: dolfin_2019.1.0-5
has caused the Debian Bug report #941068,
regarding nmu: dolfin_2019.1.0-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
941068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941068
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@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 against pybind11 2.4.2."



mshr will follow after this, dep-wait on dolfin (is this needed?),

dw mshr_2019.1.0+dfsg1-4 . ANY . unstable . -m "python3-dolfin (>= 2019.1.0-5+b1)"

then,

nmu mshr_2019.1.0+dfsg1-4 . ANY . unstable . -m "Rebuild against pybind11 2.4.2."

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Drew,

On 24-09-2019 09:44, Drew Parsons wrote:
> 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 against pybind11 2.4.2."

dolfin saw a new version, so I assume this is obsolete.

> mshr will follow after this, dep-wait on dolfin (is this needed?),
> 
> dw mshr_2019.1.0+dfsg1-4 . ANY . unstable . -m "python3-dolfin (>= 2019.1.0-5+b1)"
> 
> then,
> 
> nmu mshr_2019.1.0+dfsg1-4 . ANY . unstable . -m "Rebuild against pybind11 2.4.2."

I have done:
nmu mshr_2019.1.0+dfsg1-4 . ANY . unstable . -m "Rebuild against
pybind11 2.4.2." --extra-depends "python3-dolfin (>= 2019.1.0-6)"

Thanks.
Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: