please merge cron 3.0pl1-178 from Debian unstable

Bug #2044015 reported by Vladimir Petko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
Fix Released
Wishlist
Vladimir Petko

Bug Description

tracking bug

Related branches

Vladimir Petko (vpa1977)
Changed in cron (Ubuntu):
importance: Undecided → Wishlist
assignee: nobody → Vladimir Petko (vpa1977)
Revision history for this message
Vladimir Petko (vpa1977) wrote :

cron piuparts install/upgrade/purge test

Revision history for this message
Vladimir Petko (vpa1977) wrote :

piuparts test mantic->noble upgrade

Changed in cron (Ubuntu):
status: New → In Progress
Simon Quigley (tsimonq2)
Changed in cron (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (7.4 KiB)

This bug was fixed in the package cron - 3.0pl1-178ubuntu1

---------------
cron (3.0pl1-178ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2044015). Remaining changes:
    - debian/control: Move MTA to Suggests field.
    - debian/cron.default: change to a deprecated message to make it clear
      that the file is no longer in use.
    - d/p/f/inherit-path.patch: Add -P option to inherit PATH from environment,
      thanks to Tom Jones for the patch
    - Inherit PATH by default:
      + debian/crontab.main: Stop setting PATH
      + debian/cron.service, debian/cron.init: Pass -P to cron
  * Drop changes:
    - debian/tests/compare-with-old-cron-files: Compare against cron package
      shipped in Ubuntu Jammy instead of that shipped in Debian Bullseye
      [ Test removed in 3.0pl1-167 ]

cron (3.0pl1-178) unstable; urgency=medium

  * checked that debian/crontab.main keeps /bin and /sbin in the PATH.
    Closes: #1051138
  * modified crontab.c, so `crontab -l` emits a COLOR_RESET escape sequence
    to a tty unconditionaly at the end of the lines, to prevent prompt
    corruption later. Closes: #1054327

cron (3.0pl1-177) unstable; urgency=medium

  * Included Alexander Schwinn's PR: this is about checking steps in crontabs,
    to prevent insane divisions, like dividing one hour in more than 60 steps
    for example
  * added a new test 'step_size_out_of_bound' to check the previous change
  * modified the fake editor debian/tests/cronfiller.py so it can take in
    account an environment variable LINES to append some lines to a
    crontab file.
  * made a longer sleep (now 4 seconds) in the test
    'check-messages-sent-by-cron' to prevent random failures due to a
    heavily loaded host

cron (3.0pl1-176) unstable; urgency=medium

  * added the switch -n in the synopsis line of cron.8
  * enable debug by default (it must still be triggered by -x when
    calling cron); enabled the -N switch when DEBUGGING is enabled for
    cron.
  * documented the -x switch in cron.8
  * declared myself as maintainer
  * made a roud trip with `gbp pq import/export`, which modifies the
    debian patches (adding some information, like for example a summary
    for every modified file)
  * modified the patch features/Coloring_the_ouput_of_crontab_l.patch
    in order to touch the background color when the foregroud color is
    changed, and keep an acceptable contrast. Closes: #1053288
  * added SyslogFacility=cron in the file cron.service. Closes: #1051619

cron (3.0pl1-175) unstable; urgency=medium

  * removed the line SHELL=/usr/bin/sh from an example in crontab.5; this,
    Closes: #166533
  * according to Message-ID: <email address hidden> sent to
    <email address hidden>, this bug should be closed now ??
    Closes: #915289 anyway.
  * uncommented EXTRA_OPTS="" in debian/cron.default; Closes: #1050702

cron (3.0pl1-174) unstable; urgency=medium

  * modified the debian patch features/cron_now.patch. Removed the script
    make_cron_now.py. Added a new switch (-N) to the cron command, which
    makes it run the cron jobs once, like when a tick happens, an exit.
    Documented the new features in cron.8, removed ...

Read more...

Changed in cron (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.