Your message dated Mon, 6 Mar 2023 13:41:08 +0200 with message-id <ZAXRVHkIp1iJnuB/@tty.gr> and subject line Re: Bug#1008077: new upstream, new name has caused the Debian Bug report #1008077, regarding new upstream, new name 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.) -- 1008077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008077 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: kafkacat Version: 1.6.0-1 Upstream has changed the name and provides a new version 1.7.0: https://github.com/edenhill/kcat Would it be possible to update the package in Debian? I wouldn't care if the source and binary packages are still called kafkacat. Thank you very much in advance Harri
--- End Message ---
--- Begin Message ---Version: 1.7.1-1 On Tue, Mar 22, 2022 at 07:20:38AM +0100, Harald Dunkel wrote: > Package: kafkacat > Version: 1.6.0-1 > > Upstream has changed the name and provides a new version 1.7.0: > > https://github.com/edenhill/kcat > > Would it be possible to update the package in Debian? I wouldn't > care if the source and binary packages are still called kafkacat. Vincent took care of this with the 1.7.1-1 upload late last year, including the rename to kcat. Faidon
--- End Message ---
