Your message dated Sat, 17 Sep 2016 12:29:01 +0000
with message-id <e1blejt-0007ym...@franck.debian.org>
and subject line Bug#838089: fixed in libconfig-crontab-perl 1.41-2
has caused the Debian Bug report #838089,
regarding libconfig-crontab-perl: check for crontab(1) seems broken and 
unnecessary
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.)


-- 
838089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libconfig-crontab-perl
Version: 1.41-1
Severity: minor
Tags: upstream

The test suite gets totally skipped for me with the message
"no crontab available".

It looks like this refers to the crontab(1) command rather than a user
crontab file. From t/setup.pl:

  sub have_crontab {
      eval 'system("crontab -l 2>/dev/null")';
      return ($? >> 8 == 1);
  }

The documentation for crontab(1) doesn't specify the exit code, but it
looks like it returns 0 if the user has a crontab file and 1 if not.
So the test suite gets skipped for users with a crontab file, which
doesn't seem to be the intention.

Background for the check seems to be testing for Windows:
  https://rt.cpan.org/Public/Bug/Display.html?id=59578

Furthermore, the crontab(1) command is apparently not used by the actual
tests, only for the check, so the check seems doubly useless for us. I
intend to patch it away for now.
-- 
Niko Tyni   nt...@debian.org

--- End Message ---
--- Begin Message ---
Source: libconfig-crontab-perl
Source-Version: 1.41-2

We believe that the bug you reported is fixed in the latest version of
libconfig-crontab-perl, 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 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niko Tyni <nt...@debian.org> (supplier of updated libconfig-crontab-perl 
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: SHA256

Format: 1.8
Date: Sat, 17 Sep 2016 13:31:02 +0300
Source: libconfig-crontab-perl
Binary: libconfig-crontab-perl
Architecture: source
Version: 1.41-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org>
Changed-By: Niko Tyni <nt...@debian.org>
Description:
 libconfig-crontab-perl - module to read/write Vixie-compatible crontab(5) files
Closes: 837131 838087 838089
Changes:
 libconfig-crontab-perl (1.41-2) unstable; urgency=medium
 .
   * Team upload.
   * Patch the test suite work without cwd in @INC. (Closes: #837131)
   * Recommend cron for crontab(1). (Closes: #838087)
   * Patch the test suite to not check for crontab(1) unnecessarily.
     (Closes: #838089)
Checksums-Sha1:
 c920e96b58a8da5b0c2fa2b7984b68d660f70a8a 2115 libconfig-crontab-perl_1.41-2.dsc
 da4c6362f2c5b058c34e2e5631fab1f77531cb4c 2840 
libconfig-crontab-perl_1.41-2.debian.tar.xz
Checksums-Sha256:
 a515e89693cdc758571fb823694e777b4dd123505281bd8c2546d4ad77d2eb3c 2115 
libconfig-crontab-perl_1.41-2.dsc
 3c2e594b55f808c9e35bbbbe38e05087fdcf9bfb980cac884b1db9921d2f6cee 2840 
libconfig-crontab-perl_1.41-2.debian.tar.xz
Files:
 1dcc1b57bcb7df79aba62cbc025661e9 2115 perl optional 
libconfig-crontab-perl_1.41-2.dsc
 d6ef6c0a93fa35778562726e0ec7a0cb 2840 perl optional 
libconfig-crontab-perl_1.41-2.debian.tar.xz

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

iQIcBAEBCAAGBQJX3RzgAAoJEC7A/7O3MBsfDqsP/inzOgETVJ2eNOOgTLZrkt2g
76iOOQ7msuhWl77nqLfON2yqFGY1DDBIfvEN3A4Akk+Oa3ApNScVp5XmTJuJ1qx4
/Jfd0iXSSdragUaIEveWN+/ul0QQhLCXKIPu+ROV2vZUUqys7P2/vifMV7NAVIVg
iAxraDk2Xg902DS5CEKozEjg17y10kDtXspj8Rh2f0+xgdcIRT4kI1oC/qqd/Mgf
ZZe9GFTxbJiLrjC6w2lcGyroFzoMvWlObQ9oexEgITJN4Mt+Io2tFpsK1K3+TZ8G
pLd+B58R7caXZfE75p5/7Z9ekIHeRD4t/dedlNUDYAbqgIdL54O/IAeuMf7V0wU0
OpgdpwAfTYrXggf6XFSXOwga3xPmRJu9x2jU2eTXoKGJEp78xJshoHtq6uX9GWsb
7wtEVbSDSxQee32nwATNLnuj8P745i8xF/ufrvOKz9dgDa98yabNxoQkWmhaZWID
J+cQuspH/Ct6/0NZFyP4lHRz5trC9ICBXa7nfDjeTLhoqqhi6qL3eR9e4QOGJ+pY
peMcNFPh/ETS2iqMASQutMiaYfz42aAF3Wv9d7b/HnYY6/EdeDm8DgEEFAK8c5Gi
MbKduFPd78xiyjFwBwIiHEQ+9gGaPVSn3d7MepQb2QnSn0vqxtFTXD/Vf7CnOwsz
NzJM66DrLETlwqmVWUii
=n53q
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to