apt-compat cron error (testing)

[Member xinomilo]

not sure if this fits here, but after latest apt upgrade in testing (yesterday), i get this message from apt-compat cron :

/etc/cron.daily/apt-compat: 55: exec: /usr/lib/apt/apt.systemd.daily: not found
run-parts: /etc/cron.daily/apt-compat exited with return code 127

apt policy apt                  
apt:
  Installed: 2.5.5.0nosystemd1

and a more general question, is there a way to get previous version (eg apt 2.5.4.0nosystemd1), to see the diff?

thanks,

[Member stevesr0]

Helpful

Up

0

::

Hi xinomilo,

In regard to your first question, if you are not using systemd, then it presumably is normal NOT to have that file (/usr/lib/apt/apt.system.daily).

I haven’t played with apt-compat so I don’t know what “code 127” means.

stevesr0

[Member xinomilo]

Helpful

Up

0

::

i agree it would be normal if i was using the debian package/version.

but with antiX apt/nosystemd version, this is the first time i see this message. first seen yesterday, shortly after upgrade. ( apt 2.5.4.0nosystemd1 -> 2.5.5.0nosystemd1 )
so, something changed between versions.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Unfortunately I don’t have the apt 2.5.4.0nosystemd1 source diffs (long story, but the file size gets getting changed when uploading to the server, so it cannot be opened).
I do have the apt 2.5.5.0nosystemd1 ones if you want to compare with vanilla Debian.
IIRC, there wasn’t anything different in the new build compared to apt 2.5.4.0nosystemd1

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member stevesr0]

Helpful

Up

0

::

Hi xinomilo,

Return code 127 means command not found.

Just curious. Are you running unattended updates?

stevesr0

• This reply was modified 3 months, 1 week ago by stevesr0.

[Member xinomilo]

Helpful

Up

0

::

sorry, i forgot about this, had answer below for some time stored in some text. (posting late…)
—–

stevesr0 wrote:

Just curious. Are you running unattended updates?

no. always upgrade by hand in this pc.
—

well, i restored previous apt version, and diff is clear…

anacron (2.3-36.0antix1) came in 19/01 (day the error notice started being mailed out)

changelog :

anacron (2.3-36.0antix1) unstable; urgency=medium

  * include runit scripts 

so maybe anacron wasn’t really working before, but since 2.3-36.0antix1, is working as expected and posting all cron errors?
but the only new difference is /etc/sv/anacron/supervise dir (didn’t exist before upgrade).

[fresh/todays edit: purged anacron – not getting these cron notifications anymore]

—

anyway,
this missing apt file (/usr/lib/apt/apt.systemd.daily), doesn’t really seem to be systemd-specific (but not sure..) seems mostly cleaning staff/apt maintenance..
https://salsa.debian.org/apt-team/apt/-/blob/main/debian/apt.systemd.daily
so, maybe
1) apt.systemd.daily reference can be removed from /etc/cron.daily/apt-compat
or
2) include this file as debian does in apt package
?

[Author]

Posts