Your message dated Sun, 14 Jul 2024 01:04:17 +0000
with message-id <[email protected]>
and subject line Bug#1075895: fixed in netavark 1.9.0-3
has caused the Debian Bug report #1075895,
regarding netavark: upcoming zbus update
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 [email protected]
immediately.)


-- 
1075895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075895
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: netavark
Version: 1.4.0-4.1
Severity: normal
X-Debbugs-Cc: [email protected]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I am planning to do the zbus 3.x -> 4.x transition in Debian. netavark
b-ds on zbus 3.x. I have most other packages already uploaded to
experimental and want to go ahead with this at the end month, if
possible. zbus 4.0 is already available from experimental. I will look
into patching netavark to 4.0 but have no cycles to do so atm and would
appreciate it if you could look into this.

best,

werdahias


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

Kernel: Linux 6.9.7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

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

iIsEARYIADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCZoqBUhUcd2VyZGFoaWFz
QHJpc2V1cC5uZXQACgkQ7L7btge5sr4p8wD8D2xv3oBbteH4waPueZyAFiUFeq4u
JMoiSIH07YeKkQkBALm5TqlSDuXQX1xL8AOS8K+KQFusmNzRXjpw//wnvtIG
=BXpp
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Source: netavark
Source-Version: 1.9.0-3
Done: Reinhard Tartler <[email protected]>

We believe that the bug you reported is fixed in the latest version of
netavark, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler <[email protected]> (supplier of updated netavark 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 [email protected])


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

Format: 1.8
Date: Sat, 13 Jul 2024 20:42:28 -0400
Source: netavark
Architecture: source
Version: 1.9.0-3
Distribution: experimental
Urgency: medium
Maintainer: Reinhard Tartler <[email protected]>
Changed-By: Reinhard Tartler <[email protected]>
Closes: 1075895
Changes:
 netavark (1.9.0-3) experimental; urgency=medium
 .
   * refresh patches
   * compile against rust-zbus 4.3, Closes: #1075895
Checksums-Sha1:
 e520cbfc12a862a71851713e02e4bdc550b68cb5 3061 netavark_1.9.0-3.dsc
 745f14cad0469e5e27edb72ff8a64d24fb80d7ca 6384 netavark_1.9.0-3.debian.tar.xz
Checksums-Sha256:
 c8e1b806191f0d22e89414b05067855a21dfb1eb5a42872498169e43beafb252 3061 
netavark_1.9.0-3.dsc
 92991743b75acf890db3c2d1acf9ca16e9270c906ee71058a439f85e150bc868 6384 
netavark_1.9.0-3.debian.tar.xz
Files:
 20a7a291652a52331fd1c4fe3137bf95 3061 net optional netavark_1.9.0-3.dsc
 e5ba6db42583f2fd981073869a04852d 6384 net optional 
netavark_1.9.0-3.debian.tar.xz

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

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmaTHyUUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsveBw//Xfz1cNjLLGQTetGqStpZmsLlkkJQ
PSGsya7Wq/RAEqr4D4HfhoxBkoQr9U4yVGe0MiRLLT9zXDmnkYfDNypUwk2JdtLm
C9cLSiRV0m9P575BAG9kUABuOMqN65O4+819/EZDnGBEY58EQ3BU0Vc0rd6wR5BC
0UQjADR/nKbw8Q5X1CcNK3lJbJBORs9feevvB4WemPJNv/3Qtcdt9NSwOkDu8N1G
ZDX3OcoY1HKS7ZsnV0iYDoSOy3aiK47IcIPrGvgh07J6j/Vs+RiPVZ/CGvItNlEh
30UVBM96NhVICEHygTl16U+2roq1LcxrlHcv4Jcc5W1bTpohu6Q0ZNIgt9JSAm4X
t9uRI7VxNxXql5FrTZvECVn2LSbq5cX3JX1HBB4qk/eFHRsCJ0c1TxBh44ja1rJE
vDGVMuUU3YENemqPXaOsGYaAso8aA4sAx0skd/QvwD6oT8a1m4Yu+usFXmyw3dY2
EB4NxUAtPtB2ZC1uttkbjuJ6qHpHW9o3y/89+wyuStT8mSeA6D+IhASOqaIklOPf
1aRnJMv3TALtBfmea0UfFZcTeXwC6k5NNxA9fG7RX24Bzl+K6K05wxs68bjrAQ4d
wKhj6eRe0fOOh0UX/O55XnZl2b2ZWiiwdOtq79/Snz8977YCSMjvWKvJpdtgMfRi
BuR7Lg9Q9zK9/aM=
=g3n/
-----END PGP SIGNATURE-----

Attachment: pgpTBb6YSqMNF.pgp
Description: PGP signature


--- End Message ---

Reply via email to