[pkg-bacula-devel] Does the mtx package still have an "upstream" maintainer?

[Alexander Moibenko]

Hello,
As you can see on https://github.com/moibenko/mtx I took the last version from Sorceforge after trying to contact authors and applied patches from CentOS distro taken from CERN.
My changes were to have mtx routines calls from C code or, in my case Python. This approach speeds up execution drastically.
At this time the code is stable. As for support: I intend to contunue support of the cod in https://github.com/moibenko/mtx, but only for Fermilab needs.
Regards,
Alexander.

On Jun 1, 2021, at 8:21 AM, Will Sutton <will at sutton-family.org<mailto:will at sutton-family.org>> wrote:

James,

I am interested in keeping this project moving forward. The code seems very stable and mature, and my day job takes me more into the C an C++ side of things, so I can be a more competent maintainer as well. I have no problem sharing ownership with the right maintainers to keep it alive.

I've been using this repo on arch for quite a while with my TL4000 and not encountered any issues.

That being said, I've not heard anything from the original author since I created this repository.

Carsten, I pulled your patches into their own branch. I think it should be identical to the debian branch at this point. Feel free to send me any additional patches I might be missing.

I pulled my repo in from here: https://sourceforge.net/p/mtx/code/HEAD/tree/branches/stable-1.3/<https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_mtx_code_HEAD_tree_branches_stable-2D1.3_&d=DwMFaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=qUUJfY9rcpnSDJD1RsKzrrBmsb6vkJm31XurldnXpOw&m=Wg1FLFuUGabdrieY-4ZDlLLukuTZRUaR1GNg7pZCT3s&s=JTNr2Ece1Lz2iOvpE-Oq3ZVlnGo6z0axQtTFtCxokTE&e=>

At this point, the latest code is from soruceforge is 13 years old.

I'd be thrilled to open dialog with the rest of you as well.

William Sutton

On Tue, Jun 1, 2021 at 6:15 AM Carsten Leonhardt <leo at debian.org<mailto:leo at debian.org>> wrote:
Hello all,

I'm the Debian mtx package Maintainer.

James Youngman <james at youngman.org<mailto:james at youngman.org>> writes:

> I'd really like us to get to a place where there was a
> community-driven and group-managed upstream project (so that we're not
> singly-homed on one maintainer any more) where at least initial
> releases are conservative in their changes, to encourage distributions
> all to select the same upstream.   Right now, I don't have opinions on
> what the basis (e.g. what repo) for that should be, and I'm aware that
> naming might need some careful consideration.

as far as I can see, most distributions have based their mtx package on
the last stable version from Robert. I've tried to find all patches that
other distributions use and added them to the Debian package. Later I've
submitted them to Will for inclusion, but the version in Will's
repository is based on Robert's development branch.

>From my point of view I'd prefer starting from Robert's last stable
version plus the generally accepted patches.

The patches applied for the Debian package can be found here:
https://salsa.debian.org/bacula-team/mtx/-/tree/master/debian/patches<https://urldefense.proofpoint.com/v2/url?u=https-3A__salsa.debian.org_bacula-2Dteam_mtx_-2D_tree_master_debian_patches&d=DwMFaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=qUUJfY9rcpnSDJD1RsKzrrBmsb6vkJm31XurldnXpOw&m=Wg1FLFuUGabdrieY-4ZDlLLukuTZRUaR1GNg7pZCT3s&s=85hr3L6SmjSM6KTsteLYYg3LwMnXgUjn6djF8Qb5YKI&e=>

Regards,

Carsten


--
No trees were harmed in the sending of this message, but a rather large number of electrons were terribly inconvenienced.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20210609/6e715b93/attachment-0001.htm>