Your message dated Wed, 04 May 2022 15:49:25 +0000
with message-id <e1nmhfl-00005o...@fasolo.debian.org>
and subject line Bug#974038: fixed in cronie 1.6.1-1
has caused the Debian Bug report #974038,
regarding ITA: cronie -- Process Scheduling Daemon
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 ow...@bugs.debian.org
immediately.)


-- 
974038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal

I am looking for a new maintainer for cronie, which I believe should
become the new default cron daemon.

src:cronie is Fedora's fork of the original (and now unmaintained) ISC
cron that has been extended with a number of features.

Debian's own src:cron (which I co-maintain) is a fork of an even earlier
version that has also been extended with its own number of features.


My original goal, as (co-)maintainer of both, was to get at least
feature parity into src:cron, but two things have become clear:

  1. cronie should be the way forward. It contains many more features,
     some that have frequently been requested against src:cron, and more
     than we could reasonably duplicate (and even if: what would be the
     purpose).

     Copying code from src:cronie to src:cron is pointless.

  2. I never managed to get cronie into unstable (in a way that
     switching from cron to cronie would break as little as possible),
     and I probably never will.

     My time was entirely consumed by cron, mostly be converting it to
     source format 3.0 (quilt), which was a pain given that the 1.0
     patch had accumulated almost 30 years of changes. This took me a
     long, long time, but was necessary in order to make our cron
     codebase comparable/relatable to all the other cron forks out
     there.


The cronie package itself is not in bad shape, I did occasionally bring
it up to date.

What a new maintainer would need to to is

  * First and foremost: ensure that switching between cron and cronie
    should work flawlessly. There's already code for that (with
    conffiles handed over, and so on), but I haven't tested that in a
    long time, and I'm sure it could be improved.

  * Better: go through the patch series of src:cron, and incorporate/
    upstream anything applicable into cronie. The last time I checked,
    there were 5-6 patches for minor fixes not yet in cronie.

  * Best: Make cronie the new default cron in bullseye+1 (or bullseye,
    if one were to be super-ambitious).

    Our own src:cron, in which I have invested a great deal of my
    personal time (it was the first package I started contributing to),
    has reached a dead-end, I'm afraid.


If you're interested, I can try to help with some of the points above,
but I can't promise anything.

Christian

--- End Message ---
--- Begin Message ---
Source: cronie
Source-Version: 1.6.1-1
Done: Lance Lin <lqi...@protonmail.com>

We believe that the bug you reported is fixed in the latest version of
cronie, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 974...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lance Lin <lqi...@protonmail.com> (supplier of updated cronie package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 03 May 2022 21:21:59 +0700
Source: cronie
Architecture: source
Version: 1.6.1-1
Distribution: experimental
Urgency: medium
Maintainer: Lance Lin <lqi...@protonmail.com>
Changed-By: Lance Lin <lqi...@protonmail.com>
Closes: 974038
Changes:
 cronie (1.6.1-1) experimental; urgency=medium
 .
   * New upstream version (1.6.1)
   * Refreshed patches
   * d/control: New maintainer (Closes: #974038)
   * d/control: Updated standards (4.6.0), dh-compat (13)
Checksums-Sha1:
 6be0327b0fefe8bee45879da94ffb9767a201e36 1876 cronie_1.6.1-1.dsc
 1686d254b46e7bb094b5c5d7bf3e4f22e7c5810e 263995 cronie_1.6.1.orig.tar.gz
 4668fe66fd37a1536fdf26a7ccf649ecc38e3b5c 11560 cronie_1.6.1-1.debian.tar.xz
 785f1a411884046a1f1e43686613fc029e757186 5892 cronie_1.6.1-1_source.buildinfo
Checksums-Sha256:
 3d4359fd8e9554d9bf2be2869c725c88173a551d52185c48604fd51e55e6894e 1876 
cronie_1.6.1-1.dsc
 2cd0f0dd1680e6b9c39bf1e3a5e7ad6df76aa940de1ee90a453633aa59984e62 263995 
cronie_1.6.1.orig.tar.gz
 c706a1a53c6a2a058b231fb8816d6afcdf3590488f1f0a99bb4baf741ac39855 11560 
cronie_1.6.1-1.debian.tar.xz
 9227b3d39acb1bbeec7e1a7c7e55ff4179449477144ab48ec70ae6ac3b919434 5892 
cronie_1.6.1-1_source.buildinfo
Files:
 728256344af0276d56e49d8b92ace7cb 1876 admin optional cronie_1.6.1-1.dsc
 de07b7229520bc859d987c721bab87c5 263995 admin optional cronie_1.6.1.orig.tar.gz
 d89636646ae35dd20200ee5bc37671b9 11560 admin optional 
cronie_1.6.1-1.debian.tar.xz
 e19c1bb49bbd9ed86cacc7c95507a697 5892 admin optional 
cronie_1.6.1-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmJymmkACgkQweDZLphv
fH5jPRAAuZvmNfkYc7+bLSQzFfUWpSGAal+0zReXtDx5UeEiFj72J6iQbVkVkbX0
XShx2Q5ukfZTo8gu/3tAqA2vNIlXsJRN4pBPB5PXyD7MeVa77//YSeCEtVPgitkX
L6nZhVGgZqTsjMuQI627a0NqEgue+lXFE43xx03AhnTeWUKE/VMLVNkcLAzNuWGo
u5khO45U/cLNndMXCvHOwlCx1joX+jKogBl2Ve5ozMGYwmHdEZykkEQ8/cA1XyAY
SlhSPDzsNCUpSBfEsDk2pgQi4EijKidIQmKoefxtFQ/Px29wEzzMfV9XlzycekN4
VW5NUibxaLPnDSZm8Ojp7Ja/JqhxPnid/sR1dnj+GNN2sn3/u2qei/owO/rWk4iQ
yqea/g1NCooQAs5wWwjD0IMC3h5J07WYlFqbUjV292LYhuPBBUsNiY3hyIdZFuvB
x52sANoXO6zoS3zlemllSHARg6WFlu2gHPkCSCYGfoS2DHBvlqD5sL4iLjxadBCU
35qkVHV8vBWQkBhU0nRsjIX3i2QK6WmqBWpojwpnkRZRu478LF4Gxi7wTmTyqTvA
4XV/D6FmRrEd8SrjZJ1/1IABanZbKcr03jVxkZm+3gaCza4u5O+niqEcNKQGgv1E
OguOCjX5cu4kU6FORd95RuuVHicn3vdfLJeiCvyox6aWpxnpR4Y=
=sNjS
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to