libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Heinrich Schuchardt]

libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd

[Till Kamppeter (till-kamppeter)]

Checking autopkgtest results on armhf for the mentioned packages AFTER upload of cups 2.4.7-1.2ubuntu2, which fixed the autopkgtest failure of cups-browsed, bug 2059157 and bug 2059089:

libcupsfilters:
    https://autopkgtest.ubuntu.com/packages/c/libcupsfilters/noble/armhf
    --> OK

libppd:
    https://autopkgtest.ubuntu.com/packages/c/libppd/noble/armhf
    --> OK

cups-browsed:
    https://autopkgtest.ubuntu.com/packages/c/cups-browsed/noble/armhf
    --> OK

cpdb-libs:
    https://autopkgtest.ubuntu.com/packages/c/cpdb-libs/noble/armhf
    --> OK

cpdb-backend-cups:
    https://autopkgtest.ubuntu.com/packages/c/cpdb-backend-cups/noble/armhf
    --> OK

So generally, the 64-bit time_t problem (y2038 bug fix), seems to be sorted.

Only package causing problems is c2esp which segfaults.

[Till Kamppeter (till-kamppeter)]

Problem seems to be rather the broken cups.pc file from Debian in the cups package, which is fixed in 2.4.7-1.2ubuntu2, as after this cups release the tests of said packages have passed.

[Till Kamppeter (till-kamppeter)]

I have uploaded c2esp 27-11ubuntu4 now.

In the code of c2esp I have found some logging statements which cast pointer addresses to long int. Probably this works only on 64-bit and not on 32-bit and so caused the crashes in the autopkgtest. I could not test whether it is really the fix, I am simply giving it a try.

[Launchpad Janitor (janitor)]

This bug was fixed in the package c2esp - 27-11ubuntu7

---------------
c2esp (27-11ubuntu7) noble; urgency=medium

  * Made c2esp working on both 32-bit and 64-bit architectures with
    64-bit time_t in both cases (LP: #2059157, LP: #2059281):
    - Removed any logging of times in raw (seconds after the epoch) format
      as for (64-bit) time_t different integer variable types are used on
      32-bit/64-bit architectures. Also the log lines land in CUPS' error_log
      which adds human-readable time stamps to each line.
    - In printer keep-alive functions use time_t (and NOT int) for all
      variables used for time calculations.

 -- Till Kamppeter <email address hidden> Mon, 8 Apr 2024 23:36:00 +0200