Your message dated Thu, 29 Feb 2024 04:57:55 +0000
with message-id <e1rfyuv-009dl3...@fasolo.debian.org>
and subject line Bug#1064313: fixed in rdma-core 50.0-2
has caused the Debian Bug report #1064313,
regarding rdma-core: NMU diff for 64-bit time_t transition
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.)


-- 
1064313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdma-core
Version: 48.0-1.1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
rdma-core as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for rdma-core
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru rdma-core-48.0/debian/changelog rdma-core-48.0/debian/changelog
--- rdma-core-48.0/debian/changelog     2024-01-22 15:08:10.000000000 +0000
+++ rdma-core-48.0/debian/changelog     2024-02-19 22:06:00.000000000 +0000
@@ -1,3 +1,10 @@
+rdma-core (48.0-1.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vor...@debian.org>  Mon, 19 Feb 2024 22:06:00 +0000
+
 rdma-core (48.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rdma-core-48.0/debian/control rdma-core-48.0/debian/control
--- rdma-core-48.0/debian/control       2024-01-22 15:08:10.000000000 +0000
+++ rdma-core-48.0/debian/control       2024-02-19 22:06:00.000000000 +0000
@@ -191,7 +191,7 @@
 Section: libdevel
 Architecture: linux-any
 Multi-Arch: same
-Depends: libibverbs-dev, librdmacm1 (= ${binary:Version}), ${misc:Depends}
+Depends: libibverbs-dev, librdmacm1t64 (= ${binary:Version}), ${misc:Depends}
 Description: Development files for the librdmacm library
  librdmacm is a library that allows applications to set up reliable
  connected and unreliable datagram transfers when using RDMA adapters.
@@ -210,7 +210,10 @@
  It contains the header files and static libraries (optionally)
  needed for compiling.
 
-Package: librdmacm1
+Package: librdmacm1t64
+Provides: ${t64:Provides}
+Replaces: librdmacm1
+Breaks: librdmacm1 (<< ${source:Version})
 Architecture: linux-any
 Multi-Arch: same
 Section: libs
@@ -249,7 +252,7 @@
  provided by libibverbs, which provides the interface used to actually
  transfer data.
  .
- This package contains useful librdmacm1 example programs such as
+ This package contains useful librdmacm1t64 example programs such as
  rping and udaddy.
 
 Package: srptools
@@ -280,7 +283,7 @@
 
 Package: infiniband-diags
 Architecture: linux-any
-Depends: libibnetdisc5 (= ${binary:Version}),
+Depends: libibnetdisc5t64 (= ${binary:Version}),
          ${misc:Depends},
          ${perl:Depends},
          ${shlibs:Depends}
@@ -322,7 +325,10 @@
  It contains the header files and static libraries (optionally)
  needed for compiling.
 
-Package: libibnetdisc5
+Package: libibnetdisc5t64
+Provides: ${t64:Provides}
+Replaces: libibnetdisc5
+Breaks: libibnetdisc5 (<< ${source:Version})
 Section: libs
 Architecture: linux-any
 Multi-Arch: same
@@ -341,7 +347,7 @@
 Section: libdevel
 Architecture: linux-any
 Multi-Arch: same
-Depends: libibnetdisc5 (= ${binary:Version}), ${misc:Depends}
+Depends: libibnetdisc5t64 (= ${binary:Version}), ${misc:Depends}
 Breaks: infiniband-diags (<< 2.0.0)
 Replaces: infiniband-diags (<< 2.0.0)
 Description: InfiniBand diagnostics library headers
@@ -351,5 +357,5 @@
  failover, and it is designed to be scalable.
  .
  This package provides development files required to build
- applications aginast the libibnetdisc5 InfiniBand diagnostic
+ applications aginast the libibnetdisc5t64 InfiniBand diagnostic
  libraries.
diff -Nru rdma-core-48.0/debian/libibnetdisc5.install 
rdma-core-48.0/debian/libibnetdisc5.install
--- rdma-core-48.0/debian/libibnetdisc5.install 2019-11-25 20:26:38.000000000 
+0000
+++ rdma-core-48.0/debian/libibnetdisc5.install 1970-01-01 00:00:00.000000000 
+0000
@@ -1 +0,0 @@
-usr/lib/*/libibnetdisc*.so.*
diff -Nru rdma-core-48.0/debian/libibnetdisc5.symbols 
rdma-core-48.0/debian/libibnetdisc5.symbols
--- rdma-core-48.0/debian/libibnetdisc5.symbols 2023-10-23 16:37:08.000000000 
+0000
+++ rdma-core-48.0/debian/libibnetdisc5.symbols 1970-01-01 00:00:00.000000000 
+0000
@@ -1,21 +0,0 @@
-libibnetdisc.so.5 libibnetdisc5 #MINVER#
-* Build-Depends-Package: libibnetdisc-dev
- IBNETDISC_1.0@IBNETDISC_1.0 1.6.1
- ibnd_cache_fabric@IBNETDISC_1.0 1.6.1
- ibnd_destroy_fabric@IBNETDISC_1.0 1.6.1
- ibnd_discover_fabric@IBNETDISC_1.0 1.6.1
- ibnd_find_node_dr@IBNETDISC_1.0 1.6.1
- ibnd_find_node_guid@IBNETDISC_1.0 1.6.1
- ibnd_find_port_dr@IBNETDISC_1.0 1.6.1
- ibnd_find_port_guid@IBNETDISC_1.0 1.6.1
- ibnd_find_port_lid@IBNETDISC_1.0 1.6.4
- ibnd_get_chassis_guid@IBNETDISC_1.0 1.6.1
- ibnd_get_chassis_slot_str@IBNETDISC_1.0 1.6.1
- ibnd_get_chassis_type@IBNETDISC_1.0 1.6.1
- ibnd_is_xsigo_guid@IBNETDISC_1.0 1.6.1
- ibnd_is_xsigo_hca@IBNETDISC_1.0 1.6.1
- ibnd_is_xsigo_tca@IBNETDISC_1.0 1.6.1
- ibnd_iter_nodes@IBNETDISC_1.0 1.6.1
- ibnd_iter_nodes_type@IBNETDISC_1.0 1.6.1
- ibnd_iter_ports@IBNETDISC_1.0 1.6.1
- ibnd_load_fabric@IBNETDISC_1.0 1.6.1
diff -Nru rdma-core-48.0/debian/libibnetdisc5t64.install 
rdma-core-48.0/debian/libibnetdisc5t64.install
--- rdma-core-48.0/debian/libibnetdisc5t64.install      1970-01-01 
00:00:00.000000000 +0000
+++ rdma-core-48.0/debian/libibnetdisc5t64.install      2019-11-25 
20:26:38.000000000 +0000
@@ -0,0 +1 @@
+usr/lib/*/libibnetdisc*.so.*
diff -Nru rdma-core-48.0/debian/libibnetdisc5t64.lintian-overrides 
rdma-core-48.0/debian/libibnetdisc5t64.lintian-overrides
--- rdma-core-48.0/debian/libibnetdisc5t64.lintian-overrides    1970-01-01 
00:00:00.000000000 +0000
+++ rdma-core-48.0/debian/libibnetdisc5t64.lintian-overrides    2024-02-19 
22:06:00.000000000 +0000
@@ -0,0 +1 @@
+libibnetdisc5t64: package-name-doesnt-match-sonames libibnetdisc5
diff -Nru rdma-core-48.0/debian/libibnetdisc5t64.symbols 
rdma-core-48.0/debian/libibnetdisc5t64.symbols
--- rdma-core-48.0/debian/libibnetdisc5t64.symbols      1970-01-01 
00:00:00.000000000 +0000
+++ rdma-core-48.0/debian/libibnetdisc5t64.symbols      2024-02-19 
22:06:00.000000000 +0000
@@ -0,0 +1,21 @@
+libibnetdisc.so.5 libibnetdisc5t64 #MINVER#
+* Build-Depends-Package: libibnetdisc-dev
+ IBNETDISC_1.0@IBNETDISC_1.0 1.6.1
+ ibnd_cache_fabric@IBNETDISC_1.0 1.6.1
+ ibnd_destroy_fabric@IBNETDISC_1.0 1.6.1
+ ibnd_discover_fabric@IBNETDISC_1.0 1.6.1
+ ibnd_find_node_dr@IBNETDISC_1.0 1.6.1
+ ibnd_find_node_guid@IBNETDISC_1.0 1.6.1
+ ibnd_find_port_dr@IBNETDISC_1.0 1.6.1
+ ibnd_find_port_guid@IBNETDISC_1.0 1.6.1
+ ibnd_find_port_lid@IBNETDISC_1.0 1.6.4
+ ibnd_get_chassis_guid@IBNETDISC_1.0 1.6.1
+ ibnd_get_chassis_slot_str@IBNETDISC_1.0 1.6.1
+ ibnd_get_chassis_type@IBNETDISC_1.0 1.6.1
+ ibnd_is_xsigo_guid@IBNETDISC_1.0 1.6.1
+ ibnd_is_xsigo_hca@IBNETDISC_1.0 1.6.1
+ ibnd_is_xsigo_tca@IBNETDISC_1.0 1.6.1
+ ibnd_iter_nodes@IBNETDISC_1.0 1.6.1
+ ibnd_iter_nodes_type@IBNETDISC_1.0 1.6.1
+ ibnd_iter_ports@IBNETDISC_1.0 1.6.1
+ ibnd_load_fabric@IBNETDISC_1.0 1.6.1
diff -Nru rdma-core-48.0/debian/librdmacm1.install 
rdma-core-48.0/debian/librdmacm1.install
--- rdma-core-48.0/debian/librdmacm1.install    2018-01-21 15:20:12.000000000 
+0000
+++ rdma-core-48.0/debian/librdmacm1.install    1970-01-01 00:00:00.000000000 
+0000
@@ -1,3 +0,0 @@
-usr/lib/*/librdmacm*.so.*
-usr/lib/*/rsocket/librspreload*.so*
-usr/share/doc/rdma-core/librdmacm.md usr/share/doc/librdmacm1/
diff -Nru rdma-core-48.0/debian/librdmacm1.symbols 
rdma-core-48.0/debian/librdmacm1.symbols
--- rdma-core-48.0/debian/librdmacm1.symbols    2021-11-10 11:54:20.000000000 
+0000
+++ rdma-core-48.0/debian/librdmacm1.symbols    1970-01-01 00:00:00.000000000 
+0000
@@ -1,74 +0,0 @@
-librdmacm.so.1 librdmacm1 #MINVER#
-* Build-Depends-Package: librdmacm-dev
- RDMACM_1.0@RDMACM_1.0 1.0.15
- RDMACM_1.1@RDMACM_1.1 16
- RDMACM_1.2@RDMACM_1.2 23
- RDMACM_1.3@RDMACM_1.3 31
- raccept@RDMACM_1.0 1.0.16
- rbind@RDMACM_1.0 1.0.16
- rclose@RDMACM_1.0 1.0.16
- rconnect@RDMACM_1.0 1.0.16
- rdma_accept@RDMACM_1.0 1.0.15
- rdma_ack_cm_event@RDMACM_1.0 1.0.15
- rdma_bind_addr@RDMACM_1.0 1.0.15
- rdma_connect@RDMACM_1.0 1.0.15
- rdma_create_ep@RDMACM_1.0 1.0.15
- rdma_create_event_channel@RDMACM_1.0 1.0.15
- rdma_create_id@RDMACM_1.0 1.0.15
- rdma_create_qp@RDMACM_1.0 1.0.15
- rdma_create_qp_ex@RDMACM_1.0 1.0.19
- rdma_create_srq@RDMACM_1.0 1.0.15
- rdma_create_srq_ex@RDMACM_1.0 1.0.19
- rdma_destroy_ep@RDMACM_1.0 1.0.15
- rdma_destroy_event_channel@RDMACM_1.0 1.0.15
- rdma_destroy_id@RDMACM_1.0 1.0.15
- rdma_destroy_qp@RDMACM_1.0 1.0.15
- rdma_destroy_srq@RDMACM_1.0 1.0.15
- rdma_disconnect@RDMACM_1.0 1.0.15
- rdma_event_str@RDMACM_1.0 1.0.15
- rdma_establish@RDMACM_1.2 23
- rdma_free_devices@RDMACM_1.0 1.0.15
- rdma_freeaddrinfo@RDMACM_1.0 1.0.15
- rdma_get_cm_event@RDMACM_1.0 1.0.15
- rdma_get_devices@RDMACM_1.0 1.0.15
- rdma_get_dst_port@RDMACM_1.0 1.0.19
- rdma_get_remote_ece@RDMACM_1.3 31
- rdma_get_request@RDMACM_1.0 1.0.15
- rdma_get_src_port@RDMACM_1.0 1.0.19
- rdma_getaddrinfo@RDMACM_1.0 1.0.15
- rdma_init_qp_attr@RDMACM_1.2 23
- rdma_join_multicast@RDMACM_1.0 1.0.15
- rdma_join_multicast_ex@RDMACM_1.1 16
- rdma_leave_multicast@RDMACM_1.0 1.0.15
- rdma_listen@RDMACM_1.0 1.0.15
- rdma_migrate_id@RDMACM_1.0 1.0.15
- rdma_notify@RDMACM_1.0 1.0.15
- rdma_reject@RDMACM_1.0 1.0.15
- rdma_reject_ece@RDMACM_1.3 31
- rdma_resolve_addr@RDMACM_1.0 1.0.15
- rdma_resolve_route@RDMACM_1.0 1.0.15
- rdma_set_local_ece@RDMACM_1.3 31
- rdma_set_option@RDMACM_1.0 1.0.15
- rfcntl@RDMACM_1.0 1.0.16
- rgetpeername@RDMACM_1.0 1.0.16
- rgetsockname@RDMACM_1.0 1.0.16
- rgetsockopt@RDMACM_1.0 1.0.16
- riomap@RDMACM_1.0 1.0.19
- riounmap@RDMACM_1.0 1.0.19
- riowrite@RDMACM_1.0 1.0.19
- rlisten@RDMACM_1.0 1.0.16
- rpoll@RDMACM_1.0 1.0.16
- rread@RDMACM_1.0 1.0.16
- rreadv@RDMACM_1.0 1.0.16
- rrecv@RDMACM_1.0 1.0.16
- rrecvfrom@RDMACM_1.0 1.0.16
- rrecvmsg@RDMACM_1.0 1.0.16
- rselect@RDMACM_1.0 1.0.16
- rsend@RDMACM_1.0 1.0.16
- rsendmsg@RDMACM_1.0 1.0.16
- rsendto@RDMACM_1.0 1.0.16
- rsetsockopt@RDMACM_1.0 1.0.16
- rshutdown@RDMACM_1.0 1.0.16
- rsocket@RDMACM_1.0 1.0.16
- rwrite@RDMACM_1.0 1.0.16
- rwritev@RDMACM_1.0 1.0.16
diff -Nru rdma-core-48.0/debian/librdmacm1t64.install 
rdma-core-48.0/debian/librdmacm1t64.install
--- rdma-core-48.0/debian/librdmacm1t64.install 1970-01-01 00:00:00.000000000 
+0000
+++ rdma-core-48.0/debian/librdmacm1t64.install 2018-01-21 15:20:12.000000000 
+0000
@@ -0,0 +1,3 @@
+usr/lib/*/librdmacm*.so.*
+usr/lib/*/rsocket/librspreload*.so*
+usr/share/doc/rdma-core/librdmacm.md usr/share/doc/librdmacm1/
diff -Nru rdma-core-48.0/debian/librdmacm1t64.lintian-overrides 
rdma-core-48.0/debian/librdmacm1t64.lintian-overrides
--- rdma-core-48.0/debian/librdmacm1t64.lintian-overrides       1970-01-01 
00:00:00.000000000 +0000
+++ rdma-core-48.0/debian/librdmacm1t64.lintian-overrides       2024-02-19 
22:06:00.000000000 +0000
@@ -0,0 +1 @@
+librdmacm1t64: package-name-doesnt-match-sonames librdmacm1
diff -Nru rdma-core-48.0/debian/librdmacm1t64.symbols 
rdma-core-48.0/debian/librdmacm1t64.symbols
--- rdma-core-48.0/debian/librdmacm1t64.symbols 1970-01-01 00:00:00.000000000 
+0000
+++ rdma-core-48.0/debian/librdmacm1t64.symbols 2024-02-19 22:06:00.000000000 
+0000
@@ -0,0 +1,74 @@
+librdmacm.so.1 librdmacm1t64 #MINVER#
+* Build-Depends-Package: librdmacm-dev
+ RDMACM_1.0@RDMACM_1.0 1.0.15
+ RDMACM_1.1@RDMACM_1.1 16
+ RDMACM_1.2@RDMACM_1.2 23
+ RDMACM_1.3@RDMACM_1.3 31
+ raccept@RDMACM_1.0 1.0.16
+ rbind@RDMACM_1.0 1.0.16
+ rclose@RDMACM_1.0 1.0.16
+ rconnect@RDMACM_1.0 1.0.16
+ rdma_accept@RDMACM_1.0 1.0.15
+ rdma_ack_cm_event@RDMACM_1.0 1.0.15
+ rdma_bind_addr@RDMACM_1.0 1.0.15
+ rdma_connect@RDMACM_1.0 1.0.15
+ rdma_create_ep@RDMACM_1.0 1.0.15
+ rdma_create_event_channel@RDMACM_1.0 1.0.15
+ rdma_create_id@RDMACM_1.0 1.0.15
+ rdma_create_qp@RDMACM_1.0 1.0.15
+ rdma_create_qp_ex@RDMACM_1.0 1.0.19
+ rdma_create_srq@RDMACM_1.0 1.0.15
+ rdma_create_srq_ex@RDMACM_1.0 1.0.19
+ rdma_destroy_ep@RDMACM_1.0 1.0.15
+ rdma_destroy_event_channel@RDMACM_1.0 1.0.15
+ rdma_destroy_id@RDMACM_1.0 1.0.15
+ rdma_destroy_qp@RDMACM_1.0 1.0.15
+ rdma_destroy_srq@RDMACM_1.0 1.0.15
+ rdma_disconnect@RDMACM_1.0 1.0.15
+ rdma_event_str@RDMACM_1.0 1.0.15
+ rdma_establish@RDMACM_1.2 23
+ rdma_free_devices@RDMACM_1.0 1.0.15
+ rdma_freeaddrinfo@RDMACM_1.0 1.0.15
+ rdma_get_cm_event@RDMACM_1.0 1.0.15
+ rdma_get_devices@RDMACM_1.0 1.0.15
+ rdma_get_dst_port@RDMACM_1.0 1.0.19
+ rdma_get_remote_ece@RDMACM_1.3 31
+ rdma_get_request@RDMACM_1.0 1.0.15
+ rdma_get_src_port@RDMACM_1.0 1.0.19
+ rdma_getaddrinfo@RDMACM_1.0 1.0.15
+ rdma_init_qp_attr@RDMACM_1.2 23
+ rdma_join_multicast@RDMACM_1.0 1.0.15
+ rdma_join_multicast_ex@RDMACM_1.1 16
+ rdma_leave_multicast@RDMACM_1.0 1.0.15
+ rdma_listen@RDMACM_1.0 1.0.15
+ rdma_migrate_id@RDMACM_1.0 1.0.15
+ rdma_notify@RDMACM_1.0 1.0.15
+ rdma_reject@RDMACM_1.0 1.0.15
+ rdma_reject_ece@RDMACM_1.3 31
+ rdma_resolve_addr@RDMACM_1.0 1.0.15
+ rdma_resolve_route@RDMACM_1.0 1.0.15
+ rdma_set_local_ece@RDMACM_1.3 31
+ rdma_set_option@RDMACM_1.0 1.0.15
+ rfcntl@RDMACM_1.0 1.0.16
+ rgetpeername@RDMACM_1.0 1.0.16
+ rgetsockname@RDMACM_1.0 1.0.16
+ rgetsockopt@RDMACM_1.0 1.0.16
+ riomap@RDMACM_1.0 1.0.19
+ riounmap@RDMACM_1.0 1.0.19
+ riowrite@RDMACM_1.0 1.0.19
+ rlisten@RDMACM_1.0 1.0.16
+ rpoll@RDMACM_1.0 1.0.16
+ rread@RDMACM_1.0 1.0.16
+ rreadv@RDMACM_1.0 1.0.16
+ rrecv@RDMACM_1.0 1.0.16
+ rrecvfrom@RDMACM_1.0 1.0.16
+ rrecvmsg@RDMACM_1.0 1.0.16
+ rselect@RDMACM_1.0 1.0.16
+ rsend@RDMACM_1.0 1.0.16
+ rsendmsg@RDMACM_1.0 1.0.16
+ rsendto@RDMACM_1.0 1.0.16
+ rsetsockopt@RDMACM_1.0 1.0.16
+ rshutdown@RDMACM_1.0 1.0.16
+ rsocket@RDMACM_1.0 1.0.16
+ rwrite@RDMACM_1.0 1.0.16
+ rwritev@RDMACM_1.0 1.0.16

--- End Message ---
--- Begin Message ---
Source: rdma-core
Source-Version: 50.0-2
Done: Benjamin Drung <bdr...@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
rdma-core, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung <bdr...@ubuntu.com> (supplier of updated rdma-core package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 29 Feb 2024 03:11:46 +0100
Source: rdma-core
Built-For-Profiles: noudeb
Architecture: source
Version: 50.0-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung <bdr...@ubuntu.com>
Changed-By: Benjamin Drung <bdr...@ubuntu.com>
Closes: 1064313
Changes:
 rdma-core (50.0-2) unstable; urgency=medium
 .
   * Rename libraries for 64-bit time_t transition (Closes: #1064313)
Checksums-Sha1:
 f21c04632a2136bf9af2cc623b2ad0f2396fc7af 3201 rdma-core_50.0-2.dsc
 b1ed0de2b1fb35a2edd2d0547f6a404b4623439d 24168 rdma-core_50.0-2.debian.tar.xz
 71bad311b285839507340e527b47974796d0956f 8912 rdma-core_50.0-2_source.buildinfo
Checksums-Sha256:
 ff71e77c0083b75b5419bd4fc61260d1c9391398714b36a1a728d0c4119b2488 3201 
rdma-core_50.0-2.dsc
 a53f8eec82f5cf382eddb7e4fa2d2644e5072ddd39cb562715171d29dd422b41 24168 
rdma-core_50.0-2.debian.tar.xz
 a9c0d4c501020ff1a97b83b2b84895888bc6a0e92983d4be606607ed5f427c98 8912 
rdma-core_50.0-2_source.buildinfo
Files:
 8d06a9dc49a77cac685afe16f5f4f4ed 3201 net optional rdma-core_50.0-2.dsc
 addf2cef3d3567b0f913f87f745668e8 24168 net optional 
rdma-core_50.0-2.debian.tar.xz
 dc1794c8ce861ac025891a932527e2ec 8912 net optional 
rdma-core_50.0-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmXf6QIACgkQFZ61xO/I
d0xWrg//ZpsNh2f6VGrPQRPTK63aR9HuVg1FwX5R/FnwoyzTGg0ooWg0WqeJAswg
MQj/PjXng0IHXz1ZMROIt55uP4wVH+qlrjkyU6Dkr035CND6U0KpWlgWQzPrpPxk
pXetgYpbOxzrqx7kWSQd3hLs6IDam+iHI2xQrKuOv9mG2hqcxqkzu1RMsqrThIX6
0Qjmyx1Scw4kL+YoXmaO1xtZuNJ7EhJNLegjYQINFwYqh/jg3mbN7vYYO7k29ShL
1a4ZDT7jdbiSpPB7nCy4Q/KFxvN3e2KME79JnW/8yfWhvqRN0Rocw0g7gRMh4d0i
RGZHEXm3vjKirzaEtoWC61DqTxGtMEkqV+4Xt1cvrsAZ8l0G2v+9sC1mWgh3+2iC
TImhnCIOuMLAbft95ToygZgokEI+elIqNrAxRaHmr9CvkvnXMvJ3CMpb1WZJwrdR
26tlcWDxKphruxEhEmhARQDgX5iy5aj486Xx2e70TKGMIqcANqF6cuWe3vOvASRq
zFlOhHdXEGHQmy2DQiZvKbVWYBTG3vJ1uYW1jq2uGWK5dqiRmmc+7h047QmSZ+R1
xD39p8/C6SVmm+tf6AInz+taDJ28C1hHhWO0XriHHuKEI6LIiBbOVkhcGBf1UVmm
aMN480DB9ArrT6QrL+vKj/kliPih0P83Cx4Wjy8OyfThQGBJlCY=
=bmIv
-----END PGP SIGNATURE-----

Attachment: pgpPyg7VfCgn7.pgp
Description: PGP signature


--- End Message ---

Reply via email to