Your message dated Sun, 4 Dec 2022 12:12:09 +0100 with message-id <[email protected]> and subject line Re: qrisk2: 2017 upstream release has caused the Debian Bug report #912118, regarding qrisk2: 2017 upstream release 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.) -- 912118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912118 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: qrisk2 Version: 0.1.20150729-4 Severity: normal Dear Maintainer, for QRisk2 there's the 2017 upstream release. Please consider packaging that. The currently packaged one seems to be the 2015 version. Thanks, Karsten -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.18.0-2-686-pae (SMP w/2 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) LSM: AppArmor: enabled Versions of packages qrisk2 depends on: ii libc6 2.27-6 qrisk2 recommends no packages. qrisk2 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi, I'm closing this bug report since there is no upstream source for qrisk2 any more and there is bug #912119 asking for qrisk3 which is probably worth fixing. Kind regards Andreas. -- http://fam-tille.de
--- End Message ---
