What is good practice for package requests? Asking for Zim Update [Solved]

[dings]

What is good practice for a package request?

I want to kindly request an upgrade of Zim to the latest version 0.76.3.
Currently Zim 0.75.1 is in Enabled Repos of MX Linux.
So I first looked for it in Debian (here) and found

bookworm (stable) (x11): Grafischer Texteditor auf Grundlage von Wiki-Techniken
0.75.1-1: all
trixie (testing) (x11): Grafischer Texteditor auf Grundlage von Wiki-Techniken
0.76.3-1: all
sid (unstable) (x11): Grafischer Texteditor auf Grundlage von Wiki-Techniken
0.76.3-1: all

Does this mean that Zim 0.76.3.1 will automatically be included in MX25 repo? Or should I rather ask for an update?
(More than 2 years have passed since 0.75.1, with a lot of bug fixes und additions)

[asqwerth]

read this thread for good practice

https://forum.mxlinux.org/viewtopic.php ... 32#p455532



The packaging team will TRY to rebuild the package for MX23 compatibility on their own schedule [they have a long queue of rebuild task].

Sometime it cannot be done and they will let you know.

If it is successfully rebuilt, it will be placed in MX Test Repo so the requestor and other members can test it first and GIVE FEEDBACK. If there is enough positive feedback, it will be moved to the main repos. Otherwise, it will remain in Test Repo for people to install, at their own discretion.

Access Test Repo with MX Packageinstaller.

[Jerry3904]

Since it's already in Trixie which is getting near completion, you could just download it from one of the sources on this page and see if it installs using a right-click on MX-23.

[asqwerth]

If the deb file won't install without removing tons of packages, do not proceed.

To be honest I would not suggest that at all. It gives newcomers the idea that this (trying to install packages from a different release of Debian) generally can be done.

[dings]

Will an updated version that is already in the next version of the Debian repos be included in the repo of the next big MX update, like MX 25?

[Jerry3904]

Normally, yes.

[oops]

A nice alternative to Zim is also Cherrytree.

[Jerry3904]

FWIW: I downloaded the deb, right-clicked it > Install. It installed without problem and appears good when I launch it.

FYI here is the terminal output during the instalation

Code: Select all

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'zim' instead of '/home/jb/Downloads/zim_0.76.3-1_all.deb'
Suggested packages:
  bzr mercurial fossil ditaa dvipng gir1.2-gtksource-3.0 python3-zeitgeist
  lilypond
Recommended packages:
  gir1.2-gtkspell3-3.0
The following NEW packages will be installed:
  zim
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,311 kB of archives.
After this operation, 5,485 kB of additional disk space will be used.
Get:1 /home/jb/Downloads/zim_0.76.3-1_all.deb zim all 0.76.3-1 [1,311 kB]
Selecting previously unselected package zim.
(Reading database ... 337242 files and directories currently installed.)
Preparing to unpack .../Downloads/zim_0.76.3-1_all.deb ...
Unpacking zim (0.76.3-1) ...
Setting up zim (0.76.3-1) ...
Processing triggers for bamfdaemon (0.5.6+repack-1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for shared-mime-info (2.2-1) ...
Processing triggers for mailcap (3.70+nmu1) ...

Then, since I didn't want to keep it, I ran (with a space at the end b/c lots of packages start with zim):

Code: Select all

sudo apt purge zim 

[Stevo]

Zim is a Python3 scripting language application, not compiled into machine language binaries, so has a lot better chance of running on an older Debian release.

That should make it easier to backport, so I'll give it a try.