NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: hdparm_9.51+ds-1+deb9u1_mips64el.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: hdparm_9.51+ds-1+deb9u1_mipsel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: hdparm_9.51+ds-1+deb9u1_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: hdparm_9.51+ds-1+deb9u1_arm64.changes
  ACCEPT
Processing changes file: hdparm_9.51+ds-1+deb9u1_armhf.changes
  ACCEPT
Processing changes file: hdparm_9.51+ds-1+deb9u1_i386.changes
  ACCEPT
Processing changes file: hdparm_9.51+ds-1+deb9u1_mips.changes
  ACCEPT
Processing changes file: hdparm_9.51+ds-1+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: hdparm_9.51+ds-1+deb9u1_s390x.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: hdparm_9.51+ds-1+deb9u1_amd64.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_sourceonly.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_amd64.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_arm64.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_armel.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_armhf.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_i386.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_mips.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_mips64el.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_mipsel.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_ppc64el.changes
  ACCEPT
Processing changes file: mailman_2.1.23-1+deb9u3_s390x.changes
  ACCEPT

Bug#903853: transition: removal of nepomuk support from src:kde4libs

[Pino Toscano]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

I'd like to remove the support for Nepomuk in src:kde4libs.

Since Nepomuk has been deprecated, and already unused in Debian for
quite some time, this allows us to drop src:soprano &
src:shared-desktop-ontologies. The result is the drop of 3 library
packages from src:kde4libs: libnepomuk4, libnepomukquery4a, and
libnepomukutils4.

The reason of this transition is that libnepomuk was so far listed as
public library dependency for the kde4 versions of kio (libkio5), and
kparts (libkparts4), resulting in overlinking. Fortunately, almost all
the packages either already link in as-needed more, or switched to KDE
Frameworks 5. The only exception is src:kpartsplugin.

Hence, the plan is the following:
1) upload src:kde4libs without Nepomuk support
2) binNMU src:kpartsplugin

I verified that src:kpartsplugin builds fine even without Nepomuk
libraries, effectively not linking against them anymore. I also did
a rebuild of all the other sources still using kdelibs 4.x, and there
were no changes in their build.

PS: since I uploaded kde4libs 4:4.14.38-1 yesterday, I'd wait for it to
migrate to testing, first.

Ben file:

title = "kde4libs without nepomuk";
is_affected = .depends ~ /\blibnepomuk/;
is_good = '';
is_bad = .depends ~ /\blibnepomuk/;

Thanks,
-- 
Pino

Bug#898741: hdparm 9.51+ds-1+deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: hdparm
Version: 9.51+ds-1+deb9u1

Explanation: only enable APM on disks that advertise it

Processed: hdparm 9.51+ds-1+deb9u1 flagged for acceptance

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #898741 [release.debian.org] stretch-pu: package hdparm/9.51+ds-1+deb9u1
Added tag(s) pending.

-- 
898741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: hdparm 9.51+ds-1+deb9u1 flagged for acceptance

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #898741 [release.debian.org] stretch-pu: package hdparm/9.51+ds-1+deb9u1
Ignoring request to alter tags of bug #898741 to the same tags previously set

-- 
898741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898741: stretch-pu: package hdparm/9.51+ds-1+deb9u1

[Adam D. Barratt]

Hi,

On Sun, 2018-07-15 at 18:35 +0200, Cyril Brulebois wrote:
> Adam D. Barratt  (2018-07-14):
> > I missed that hdparm builds a udeb, so CCing the d-i RM for
> > confirmation.
> > 
> > KiBi - hdparm is in the "could be handled by britney" list in
> > hints/freeze, which I think we'd previously agreed meant it didn't
> > need d-i sign-off, but I'm not 100% sure of that right now.
> 
> I think I really should have looked at organizing the lists better,
> but can't really do that now… So looking for a confirmation is
> appreciated.

No worries. It'd be good if we could work out how to not have to bother
you about packages that don't affect d-i at some point.

> Regarding hdparm specifically, I can't seem able to immediately find
> where its udeb is used, so I guess letting the change go through
> should be safe. ;)
> 

Thanks.

Regards,

Adam

Processed: user release.debian....@packages.debian.org, cloning 903830, reassign -1 to release.debian.org ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was a...@debian.org).
> clone 903830 -1
Bug #903830 [ftp.debian.org] RM: intel-processor-trace [s390x] -- RoM; ANAIS; 
package only meanful on Intel architecture
Bug 903830 cloned as bug 903848
> reassign -1 release.debian.org
Bug #903848 [ftp.debian.org] RM: intel-processor-trace [s390x] -- RoM; ANAIS; 
package only meanful on Intel architecture
Bug reassigned from package 'ftp.debian.org' to 'release.debian.org'.
Ignoring request to alter found versions of bug #903848 to the same values 
previously set
Ignoring request to alter fixed versions of bug #903848 to the same values 
previously set
> tags -1 + stretch
Bug #903848 [release.debian.org] RM: intel-processor-trace [s390x] -- RoM; 
ANAIS; package only meanful on Intel architecture
Added tag(s) stretch.
> usertags -1 rm
There were no usertags set.
Usertags are now: rm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903830
903848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898741: stretch-pu: package hdparm/9.51+ds-1+deb9u1

[Cyril Brulebois]

Hi,

Adam D. Barratt  (2018-07-14):
> I missed that hdparm builds a udeb, so CCing the d-i RM for
> confirmation.
> 
> KiBi - hdparm is in the "could be handled by britney" list in
> hints/freeze, which I think we'd previously agreed meant it didn't
> need d-i sign-off, but I'm not 100% sure of that right now.

I think I really should have looked at organizing the lists better, but
can't really do that now… So looking for a confirmation is appreciated.

Regarding hdparm specifically, I can't seem able to immediately find
where its udeb is used, so I guess letting the change go through should
be safe. ;)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#901431: RM: ruby-compass/1.0.3~dfsg-5

[Jonas Smedegaard]

Quoting Emilio Pozuelo Monfort (2018-07-15 12:13:34)
> On 13/06/18 09:55, Jonas Smedegaard wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: rm
> > 
> > ruby-compass is dead upstream, and does not work with recent ruby-sass.
> > This is tracked in bug#876608 of severity serious.
> > 
> > For some reason, instead of bug#876608 kicking out (and keeping out)
> > ruby-compass from testing, apparently instead it has caused recent
> > ruby-sass to be kept out of testing instead.
> > 
> > Please remove ruby-compass from testing, since it has no future.
> 
> Hinted for removal, though if it's got no future and no rdeps, you may want to
> get it removed from unstable with an ftp.debian.org RM bug.

Thanks.

There is no future in sight for Compass, but rdeps exist in unstable.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#903830: RM: intel-processor-trace/stable [s390x] -- ANAIS; package only meanful on Intel architecture

[Héctor Orón Martínez]

Package: ftp.debian.org
Severity: normal

The `intel-processor-trace` package is only meanful on Intel arches, therefore 
other binaries should be removed from the archive.
Please, remove  s390x binaries (libipt1, libipt-dev) for stable/testing and 
unstable distributions.

Regards

Bug#903822: Package(s) broken by CLANG_RESOURCE_DIR change

[Graham Inggs]

Control: clone -1 -2
Control: reassign -2 src:llvm-toolchain-6.0 1:6.0.1-1
Control: retitle -2 resource directory changes with minor upstream release
Control: severity -2 important

Cloning and re-assigning so we can fix this for future releases.

Processed: Package(s) broken by CLANG_RESOURCE_DIR change

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #903822 [release.debian.org] Package(s) broken by CLANG_RESOURCE_DIR change
Bug 903822 cloned as bug 903827
> reassign -2 src:llvm-toolchain-6.0 1:6.0.1-1
Bug #903827 [release.debian.org] Package(s) broken by CLANG_RESOURCE_DIR change
Bug reassigned from package 'release.debian.org' to 'src:llvm-toolchain-6.0'.
Ignoring request to alter found versions of bug #903827 to the same values 
previously set
Ignoring request to alter fixed versions of bug #903827 to the same values 
previously set
Bug #903827 [src:llvm-toolchain-6.0] Package(s) broken by CLANG_RESOURCE_DIR 
change
Marked as found in versions llvm-toolchain-6.0/1:6.0.1-1.
> retitle -2 resource directory changes with minor upstream release
Bug #903827 [src:llvm-toolchain-6.0] Package(s) broken by CLANG_RESOURCE_DIR 
change
Changed Bug title to 'resource directory changes with minor upstream release' 
from 'Package(s) broken by CLANG_RESOURCE_DIR change'.
> severity -2 important
Bug #903827 [src:llvm-toolchain-6.0] resource directory changes with minor 
upstream release
Severity set to 'important' from 'normal'

-- 
903822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903822
903827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903822: Package(s) broken by CLANG_RESOURCE_DIR change

[Rebecca N. Palmer]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
(or should this be 'nmu'?)

The Clang resource directory (clang --print-resource-dir) changes every 
upstream *bugfix* release (e.g. /usr/lib/llvm-6.0/lib/clang/6.0.1/ ), 
but clang's reverse dependencies are only rebuilt every *feature* release.


At least pocl, and possibly also mesa-opencl-icd, qtcreator and 
irony-mode, store this directory name in CLANG_RESOURCE_DIR at build 
time then expect it to be the same at run time.


Hence, pocl is mostly unusable (clBuildProgram fails with
error: :2:10: 
'/usr/lib/llvm-6.0/lib/clang/6.0.0/include/opencl-c.h' file not found

); I haven't tested the others.

BinNMUs will probably fix the immediate problem, but it would recur on 
future bugfix releases.

Bug#901431: marked as done (RM: ruby-compass/1.0.3~dfsg-5)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 12:13:34 +0200
with message-id 
and subject line Re: Bug#901431: RM: ruby-compass/1.0.3~dfsg-5
has caused the Debian Bug report #901431,
regarding RM: ruby-compass/1.0.3~dfsg-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 ow...@bugs.debian.org
immediately.)


-- 
901431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

ruby-compass is dead upstream, and does not work with recent ruby-sass.
This is tracked in bug#876608 of severity serious.

For some reason, instead of bug#876608 kicking out (and keeping out)
ruby-compass from testing, apparently instead it has caused recent
ruby-sass to be kept out of testing instead.

Please remove ruby-compass from testing, since it has no future.


 - Jonas

- -- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-rc3-amd64 (SMP w/4 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlsgzekACgkQLHwxRsGg
ASFr1g/+KMLm7uPgDTzNmau0M0N9ObKluw3rPxlpltlFFGrlmj0GaMJKETFrvo0A
HbrV2p+SAreD3nRMvL/zJCJfwnnaab8VEB9VwyccJjl86c5cl+sdGTnXjZ2m1FSL
iudR9cFc57npEZnPA/S4JflEQArf7Jb8roBH+P15BjIEDSkpEcn8dkfMpSX8QXkY
bd9QRz6TO5tT2ifXgJI7QwW26XT6TQQNVJoxXCRClg2SDlqDOwkE48K68Njq6oxa
sjdUDNXT/KqY3yiNtmZa9Jjtr4oUy/SgardNtFM2/8jFtEWKeGDr4Mh4SQBURrmT
zsU/ic88NW6RXwszRDHKv61io/+qeAtU/p4PIigklg8TPgsy/nCJcLNbvYzNDaUB
9WovAd4axhPxAtMkxvVAdEzEZZTKODF/J9hdo848FmLEWjLmk9GDUFjlzFSV5xrN
/EDGWNV0qRYECLbkDJj+3FJZWT49p00dd4XG7pRVwigaJZcsKPjXyn7esrI0i6/L
0h8eBYF46bLGmIJtwEcK2S5+yG6Ha2ACf96kjtKyi6YD/urZ4EkchDZDl5Dghfnb
RBbdSDlkmTSOFRgbxMMZOY1xf2uc8t2BakKXSt1GfEbjlktv5pF/c4UjsqRTon6K
KX77WDd3TaGul216IfiOMcC2PhiCy+KpqKt88ZqdEMeI0c94I5E=
=2ZtP
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On 13/06/18 09:55, Jonas Smedegaard wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> ruby-compass is dead upstream, and does not work with recent ruby-sass.
> This is tracked in bug#876608 of severity serious.
> 
> For some reason, instead of bug#876608 kicking out (and keeping out)
> ruby-compass from testing, apparently instead it has caused recent
> ruby-sass to be kept out of testing instead.
> 
> Please remove ruby-compass from testing, since it has no future.

Hinted for removal, though if it's got no future and no rdeps, you may want to
get it removed from unstable with an ftp.debian.org RM bug.

Cheers,
Emilio--- End Message ---

Bug#903764: marked as done (nmu: librep_0.92.6-1)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 10:47:27 +0200
with message-id <41b41219-77f5-a67d-2040-b35c09ad9...@debian.org>
and subject line Re: Bug#903764: nmu: librep_0.92.6-1
has caused the Debian Bug report #903764,
regarding nmu: librep_0.92.6-1
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 ow...@bugs.debian.org
immediately.)


-- 
903764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu librep_0.92.6-1 . ANY . experimental . -m "Rebuild against libgdbm5."

librep-dev/experimental still depends on the no longer available
libgdbm3.

Andreas
--- End Message ---
--- Begin Message ---
On 14/07/18 13:56, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu librep_0.92.6-1 . ANY . experimental . -m "Rebuild against libgdbm5."
> 
> librep-dev/experimental still depends on the no longer available
> libgdbm3.

Done.

Emilio--- End Message ---

Bug#903765: marked as done (nmu: tvc_5.0.3+dfsg-2)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 10:44:50 +0200
with message-id 
and subject line Re: Bug#903765: nmu: tvc_5.0.3+dfsg-2
has caused the Debian Bug report #903765,
regarding nmu: tvc_5.0.3+dfsg-2
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 ow...@bugs.debian.org
immediately.)


-- 
903765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu tvc_5.0.3+dfsg-2 . ANY . experimental . -m "Rebuild against 
libbamtools2.5.1."

That was missed during the transition in sid.


Andreas
--- End Message ---
--- Begin Message ---
On 14/07/18 14:25, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu tvc_5.0.3+dfsg-2 . ANY . experimental . -m "Rebuild against 
> libbamtools2.5.1."
> 
> That was missed during the transition in sid.

Scheduled.

Emilio--- End Message ---

Bug#903697: marked as done (nmu: ros-geometry2_0.6.2-6)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 10:44:07 +0200
with message-id 
and subject line Re: Bug#903697: nmu: ros-geometry2_0.6.2-6
has caused the Debian Bug report #903697,
regarding nmu: ros-geometry2_0.6.2-6
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 ow...@bugs.debian.org
immediately.)


-- 
903697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Due to being stuck in new due to the transition, this was build against
the old ros-ros-comm, can you please schedule a rebuild? Thanks!

nmu ros-geometry2_0.6.2-6 . amd64 . unstable . -m "Rebuild against ros-ros-comm 
1.14.2."

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.16.0-2-armmp (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 13/07/18 13:20, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> Due to being stuck in new due to the transition, this was build against
> the old ros-ros-comm, can you please schedule a rebuild? Thanks!
> 
> nmu ros-geometry2_0.6.2-6 . amd64 . unstable . -m "Rebuild against 
> ros-ros-comm 1.14.2."

Scheduled.

Emilio--- End Message ---

Bug#903766: marked as done (nmu: hdf5_1.10.2+repack-1~exp1)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 10:41:36 +0200
with message-id <6b661f5d-5666-ef6f-d4eb-07ae929c9...@debian.org>
and subject line Re: Bug#903766: nmu: hdf5_1.10.2+repack-1~exp1
has caused the Debian Bug report #903766,
regarding nmu: hdf5_1.10.2+repack-1~exp1
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 ow...@bugs.debian.org
immediately.)


-- 
903766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu hdf5_1.10.2+repack-1~exp1 . ANY . experimental . -m "Rebuild against 
libopenmpi3."

This was missed during the openmpi transition.


Andreas
--- End Message ---
--- Begin Message ---
On 14/07/18 15:36, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu hdf5_1.10.2+repack-1~exp1 . ANY . experimental . -m "Rebuild against 
> libopenmpi3."
> 
> This was missed during the openmpi transition.

Done.

Emilio--- End Message ---