Bug#933217: RM: check-mk -- RoQA, RC-Buggy, unmaintained, no reverse dependency
On 10/8/19 2:06 PM, Moritz Mühlenhoff wrote: > On Mon, Sep 30, 2019 at 09:34:46AM -0700, Matt Taggart wrote: >> Hi, >> >> >> I think it's fine for check-mk to be removed from unstable, if it does >> end up in Debian again it will be repackaged and should go through NEW >> again anyway. > > Ack, I've just filed a removal bug. I suppose the version from > experimental should be removed as well? Yes. Thanks, -- Matt Taggart tagg...@debian.org
Bug#933217: RM: check-mk -- RoQA, RC-Buggy, unmaintained, no reverse dependency
On Mon, Sep 30, 2019 at 09:34:46AM -0700, Matt Taggart wrote: > Hi, > > > I think it's fine for check-mk to be removed from unstable, if it does > end up in Debian again it will be repackaged and should go through NEW > again anyway. Ack, I've just filed a removal bug. I suppose the version from experimental should be removed as well? Cheers, Moritz
Bug#933217: RM: check-mk -- RoQA, RC-Buggy, unmaintained, no reverse dependency
Hi, Thanks for opening this bug, this should have been discussed a while ago. check-mk in debian was originally packaged and uploaded for Debian when it was a pretty basic nagios add-on. Since then upstream has both continued to add features and automation layers above that basic functionality (OMD, BI, etc) and also at the same time made a commercial business out of selling support and added non-FOSS components. It is now very difficult to support the check-mk core functionality as it's packaged in Debian. I began packaging the 1.4.0 stable release and realized that the levels of integration of the core functionality and the higher layers were going to make it nearly impossible to untangle. For check-mk to continue in Debian we'd need to either: 1) fork the "Checkmk Raw Edition (CRE)" and work to remove the dependencies and non-FOSS integration, maintaining the fork over time and merging changes made to the core agents. 2) repackage the FOSS components, adopting all of upstream's levels of automation and integration as a monolithic package and no longer just be an add-on for other monitoring system. My own use of check-mk involved using a puppet module to automatically configure checks for new systems as they were added, by automatically editing config files. This does not work well with the "full stack" model where the administrator is expected to do things via a UI. So option #2 is not interesting to me, and option #1 sounds like a lot of work. What I need to do next is investigate icinga2's equivalent functionality and see if that's a good replacement option. I think it's fine for check-mk to be removed from unstable, if it does end up in Debian again it will be repackaged and should go through NEW again anyway. Thanks, -- Matt Taggart tagg...@debian.org
Bug#933217: RM: check-mk -- RoQA, RC-Buggy, unmaintained, no reverse dependency
Source: check-mk Severity: serious Justification: QA/MIA-Team Dear maintainers of check-mk, check-mk is currently RC-Buggy with 2 RC bugs: #876686 [S| | ] [check-mk-config-icinga] check-mk-config-icinga: file conflict with check-mk-common: /usr/share/check_mk/cmk/paths.py #924727 [S| | ] [src:check-mk] check-mk: build-depends on no longer available g++-6 as well as plenty of many other bugs. It missed Buster and the last upload was two years ago, so this package seems to be unmaintained. "dak rm -Rn check-mk" tells that there are no reverse dependencies, so I think it would be sane to just let the package go. If there is no answer to this bug within 3 months, I will reassign this bug to ftp.debian.org for the actual removal. If you disagree, just close the bug, but it would be great if the package could be fixed into back into an releasble state. -- tobi -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
