MX Linux Forum

Hello, everyone. Currently, timekpr-next exists in the MX Test Repo as version 0.4.1-0.1~mx19+1. However, on the website for timekpr-next https://launchpad.net/timekpr-next, there is a tar.gz archive available that is version 0.5.0. The latest version has many more features, so I would really appreciate it if the MX devs update the package in the MX Test Repo to 0.5.0, and if you see fit, it would be very nice to have it promoted to the stable repo.

Thank you, and have a good day/night.

computerworm01001 wrote: Tue Jan 26, 2021 1:30 am Hello, everyone. Currently, timekpr-next exists in the MX Test Repo as version 0.4.1-0.1~mx19+1. However, on the website for timekpr-next https://launchpad.net/timekpr-next, there is a tar.gz archive available that is version 0.5.0. The latest version has many more features, so I would really appreciate it if the MX devs update the package in the MX Test Repo to 0.5.0, and if you see fit, it would be very nice to have it promoted to the stable repo.

Thank you, and have a good day/night.

Thank you for the request, yes understand it needs updated, but this package is a troublesome one because the developer won’t support sysvinit OOTB.

It’s going to take time to get it updated again and it’s behind other things for me right now.

SwampRabbit wrote: Tue Jan 26, 2021 2:26 am
Thank you for the request, yes understand it needs updated, but this package is a troublesome one because the developer won’t support sysvinit OOTB.

It’s going to take time to get it updated again and it’s behind other things for me right now.

Hello, SwampRabbit. Yeah, it's extremely annoying that systemd has taken over the Linux world to that extent. But I understand, and I can be patient. Thank you for noticing my request. Also, I want to give thanks to you and all the developers for working so hard to make MX awesome!

Hello again, MX devs. I just wanted to let you know that I figured out how to add timekpr-next as a SysVinit service. I downloaded this .deb package: http://ppa.launchpad.net/mjasnik/ppa/ub ... _amd64.deb (that's the last version before systemd took over), opened the compressed archive, and extracted the SysVinit script. Then I added it as a SysVinit service, and rebooted. It works like a charm on MX 19.4.

I also wanted to let you know that the newest release of timekpr-next is now 0.5.2. And timekpr-next is now in Debian Stable for the first time ever, debuting at version 0.5.0-2 with the release of Bullseye.

Thank you for your time, and I hope this information helps with the release of MX-21!

computerworm01001 wrote: Wed Sep 01, 2021 7:59 pm Hello again, MX devs. I just wanted to let you know that I figured out how to add timekpr-next as a SysVinit service. I downloaded this .deb package: http://ppa.launchpad.net/mjasnik/ppa/ub ... _amd64.deb (that's the last version before systemd took over), opened the compressed archive, and extracted the SysVinit script. Then I added it as a SysVinit service, and rebooted. It works like a charm on MX 19.4.

I also wanted to let you know that the newest release of timekpr-next is now 0.5.2. And timekpr-next is now in Debian Stable for the first time ever, debuting at version 0.5.0-2 with the release of Bullseye.

Thank you for your time, and I hope this information helps with the release of MX-21!

Thats the same init script we already have in our 0.4.1 package.

Are you saying it also works with version 0.5.0-2 and or 0.5.2?

Hello, SwampRabbit.

There is no SysVinit script included in the 0.4.1 package. That's why I had to add the service manually. I double-checked this by manually downloading the .deb archive from the MX Test Repo (http://mxrepo.com/mx/testrepo/pool/test ... _amd64.deb) and opening it with Ark. You can see for yourself in the attached screenshot; there is a systemd script, but no SysVinit script.

Also, yes, I've tried the SysVinit script with 0.4.1, 0.5.0-2, and 0.5.2. It appears to work fine in all of them.

Thank you for your time and attention to this matter, I truly appreciate it.

The init script is in the debian tarball, but it seems it wasn't being copied over into the .deb, easy fix for when we package the newest version.
I'll probably mess with it next week pending time to do it.

Okay, thank you so much!