[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1122194: ITS: mp3splt



Hi Sebastian,

Am Tue, Dec 09, 2025 at 09:25:00AM +0100 schrieb Sebastian Ramacher:
> 
> So, are you becoming the upstream?

No.

> If not, uploading it with the team as
> maintainer we give the wrong impression that this package is still
> maintained.

I intend to maintain the existing codebase within Debian. To give a
concrete example: Bug #1112231 - mp3splt-gtk: Depends on deprecated
dbus-glib - is clearly an issue that ideally should be solved upstream.
As Debian maintainer of the package I see my responsibilities as:

 1. Tagging the issue upstream (which I just did).

 2. Ensuring that the package does not block progress inside Debian (for
    example, if mp3splt-gtk prevents removal of dbus-glib, I would take
    care of removing the GUI component while keeping the CLI tool
    functional, if feasible).

> A prospective maintainer needs to also take up upstream
> maintenance.

There are many packages in Debian with inactive upstreams that are still
maintained on the Debian side. Could you clarify what you expect in
practice under "take up upstream maintenance"?

For instance, do you mean creating new releases, rewriting parts of the
codebase, or something else?

> > If this is not the direction the Multimedia team wants to follow in
> > general, please let me know. I do not want to go against established
> > practice. I just want to find a sustainable home for the package.
> 
> I am personally in favor of orphaning those packages. They usually
> require work and commitment upstream. I don't expect anybody in the
> multimedia team is willing to take over the upstream work.

Please be more verbose about what you consider "upstream work" in this
context. Understanding this helps me evaluate whether team maintenance
is appropriate or whether orphaning is indeed the better path here.

Kind regards
   Andreas.

-- 
https://fam-tille.de


Reply to: