[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#921741: cups: Cups sheduler stops with program error when using JobPreserveHistory <seconds>



Hello Didier,

With all due respect, but I think it should be integrated.

- This option was provided since a long time, never worked as designed.

- When used, it delete ALL c and d files in /var/spool/cups,
That means, even print job files which were leaved there for archiving purposes, re-printing jobs,
accounting of printjobs, etc.

It deletes the whole history of print jobs, in the file system and, as result of this, in the section "job history" in the management website of cups.

- The website part of cups-sheduler stopp because of this with message leaving in /var/log/cups/error_log:
[E] cups-shedule stopped due to program error.

It will be restarted however, but until the cupsd.conf is not cleaned of PreserveJobHistory <seconds>
It will continue to delete those files/ prevent from creating them, which have the same effect.

No this is not a "normal" bug, were just an option is simply not working instead, this option actively delete all data, which the user of cups may rely on later, unrecoverable.

So I ask you to reconsider your decision to not include the provided patch by Micheal and include it.

It's a patch which add no additional functions, instead fixing a really bad behaviour of cups. I'm sure, Michael can agree on this.

And I thought, Debian was proud in the past, to deliver stable software, not a buggy one, which is cups in this version selected to release.

With all due respect.

Emin Kaya


Didier 'OdyX' Raboud <odyx@debian.org> schrieb am Fr., 19. Apr. 2019, 22:57:
Le samedi, 30 mars 2019, 20.20:19 h CEST Emin Kaya a écrit :
> Hello Brian,
>
> as i saw on github, Michael provided a patch, which solve the problem.
> Any date where this patch will be integrated into Debian Buster?

It will not. This is (rightfully) a severity: normal bug. So from the Debian
perspective, it's unfortunately too late in the Buster freeze to fix it.

Sorry.

    OdyX

Reply to: