Your message dated Wed, 12 Mar 2025 03:05:46 +0000 with message-id <[email protected]> and subject line Bug#1095433: Removed package(s) from unstable has caused the Debian Bug report #1095433, regarding RM: mcron -- RoQA; unmaintained (upstream as well as packaging), many alternatives in Debian 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.) -- 1095433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095433 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: mcron Version: 1.0.8-1.1 Severity: serious Justification: grab attention of maintainer X-Debbugs-Cc: Dale Mellor <[email protected]>, Package Salvaging Team <[email protected]> Dear Dale, I suggest removing mcron from Debian for the following reasons: * Debian has bcron, cron, cronie and systemd-cron providing the virtual package cron-daemon * mcron seems to be just another cron daemon and it has the lowest usage compared to the above udd=# select package, insts, vote from popcon where package like '%cron%' and package in ('bcron', 'cron', 'cronie', 'mcron', 'systemd-cron') order by vote desc; package | insts | vote --------------+--------+-------- cron | 245259 | 218615 systemd-cron | 572 | 458 cronie | 29 | 29 bcron | 14 | 9 mcron | 14 | 1 (5 Zeilen) * Simple usage stats are surely not a good reason but it also does not seem not actively maintained. One strong reason is that it is not even providing the cron-daemon virtual package. (see bug #909691) * Bug reports later than Sept 2018 are not answered. * The package was uploaded twice by you as the maintainer-last time more than 10 years ago-and is lagging severely behind upstream This bug serves as a pre-removal warning. After one month, the bug will be reassigned to ftp.debian.org to actually request removal of the package. In case the package should be kept in unstable, I'd happily help migrating it to Salsa to the debian/ team and fix most of the open bugs. In case the package should be removed from unstable, you may reassign this bug report: Control: severity -1 normal Control: retitle -1 RM: mcron -- RoM; rc-buggy Control: reassign -1 ftp.debian.org Control: affects -1 + src:mcron Alternatively, you may wait a month and have it reassigned. In case you disagree with the above, please add a wontfix tag to this bug. Control: tags -1 + wontfix Your package was highlighted in the Bug of the Day[1] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to familiarize newcomers with a consistent Git-based workflow. Kind regards Andreas. [1] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/8 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: mcron | 1.0.8-1.1 | source, amd64, armel, armhf, i386, mips64el, ppc64el, s390x mcron | 1.0.8-1.1+b1 | arm64, riscv64 ------------------- Reason ------------------- RoQA; unmaintained (upstream as well as packaging), many alternatives in Debian ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/1095433 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
