Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"
Dear Carsten,
thanks for your feedback, your kind words and your patience with my
frustration. :)
I was thinking about what it is what bothers me here. It is not that
"the work" isn't done or bugs not fixed. It is that there is no
reaction; zero; total silence.
The current Debian release is fresh. All of you maintainers have done a
lot of extra work in the last weeks to get it done. The next release is
two years in the future. Totally understandable if someone now would
take half or one year off from the maintainers job.
But this needs to be communicated somehow. A simple mail with "I'm on
holiday for the next 6 months" would be OK for me.
But without any reaction it feels to me that the package is not
important to the maintainer.
This is not about a simple bug ticket. I asked seriously in public on
the list if the DPT could take over the package. Especially in this
situation I would expect a reaction. Asking in public is quit
impolite by me. But before I've done this I tried to reach jmw several
times.
On 2023-07-23 09:45 Carsten Schoenert
<c.schoenert@t-online.de> wrote:
> their work for Debian within their free and spare time and they can
> decide when to work on something.
It is the same on my upstream site. No one gets and wants applause. We
do this for our own.
> > There is also this bug ticket where I had specific questions (in
> > August last year) only the maintainer can answer but got no
> > reaction. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940319
>
> Why can't only the maintainer answer this?
You might haven't read all ticket comments or I wasn't able to make my
question clear. The intention of my last comments to that ticket are to
understand how Jonathan worked around the problem while packaging. It
is my learning on the way becoming a Debian packager myself.
As he describes the problem and I as understand, it must be impossible
to build and package backintime for Debian. But as it is obvious it is
somehow possible and I want to know how. I want to learn something
specific about that packaging here.
> I don't understand what or who is blocking whom here?
> Is it that you feel you are blocked with your upstream work by the
> maintainer?
> [..]
> If you only think that the maintainer of backintime should be
> switched to the DPT then this is only a wish. And I don't think doing
> such a switch is improving the situation for you, still someone needs
> to do the work you requesting.
All this is not about work in the meaning of fixing, uploading or
something else. It is just about having a dialog. Without dialog I'm
not able to learn and to take over packaging someday to save your
resources. Not sure if it is against the Debian rules that upstream do
its own Debian packaging.
Participating to Debian sometimes feels like talking to a wall. I want
to learn and improve my skills to someday jump into the Debian
packaging wheel. From my experience with this list it seems easier to
have dialog with the DPT.
> this then you are welcome to become a member of the DPT by doing work
> on packages which are in the maintenance of the DPT
Exactly! That is why I want my package being switch from jmw to the DPT
to make it "in the maintenance of the DPT".
> So you want to process further something?
> Provide patches, improve packages, enhance documentation, do some
> kind of the work. That's the typical answers to that question.
I hope I made my point clear now that I want and still do this. E.g. I
checked all debian bug tickets for backintime. But I'm not able doing
this further when there is no dialog.
> it might be sounds strange to you, but 5 or sometimes also 8 weeks
> and longer isn't a long time within Debian.
I know this and I'm not that new to Debian. :)
Waiting weeks and months for a reaction (not work) is IMHO not OK.
Kind
Christian
Reply to: