Your message dated Tue, 18 May 2021 20:07:09 +0000 with message-id <E1lj5zh-0008Ob-3f@respighi.debian.org> and subject line unblock eiskaltdcpp has caused the Debian Bug report #988601, regarding unblock: eiskaltdcpp/2.4.2-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 owner@bugs.debian.org immediately.) -- 988601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988601 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: eiskaltdcpp/2.4.2-1
- From: Boris Pek <tehnick@debian.org>
- Date: Sun, 16 May 2021 19:42:11 +0300
- Message-id: <[🔎] 174011621183126@mail.yandex.ru>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock X-Debbugs-Cc: tehnick@debian.org Please unblock package eiskaltdcpp This was a bugfix release of program with small amount of changes. The most important one: * Fix search on ADC hubs. (It was accidentally broken in 2.4.1 release.) Notes: Hub is just server software in terms of Direct Connect (DC aka NMDC) and Advanced Direct Connect (ADC) protocols. For example, in Debian we have uhub program which is ADC hub (without support of old DC protocol). [ Reason ] Bugfix release + updated translations. Package was uploaded at 2021-03-03 01:02:49 +0300, almost ten days before Hard Freeze (2021-03-12), but did not migrate to testing and I forgot to check its status... [ Impact ] > What is the impact for the user if the unblock isn't granted? Users connected only to ADC hubs will not be able to search files. All other features (public and private chats, file exchange, observing file list, etc.) work fine. [ Tests ] > What automated or manual tests cover the affected code? There are no automated tests for code, but this version of program has been successfully checked by a lot of users (including me) during long time (since 2021-03-03). [ Risks ] There are no known risks. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] * I am upstream developer of program as well. * Important patch: https://github.com/eiskaltdcpp/eiskaltdcpp/commit/e1717a8e * Full diff: https://github.com/eiskaltdcpp/eiskaltdcpp/compare/v2.4.1...v2.4.2 unblock eiskaltdcpp/2.4.2-1Attachment: __debdiff.changes.diff
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: 988601-done@bugs.debian.org
- Subject: unblock eiskaltdcpp
- From: Sebastian Ramacher <sramacher@respighi.debian.org>
- Date: Tue, 18 May 2021 20:07:09 +0000
- Message-id: <E1lj5zh-0008Ob-3f@respighi.debian.org>
Unblocked.
--- End Message ---