On 5/18/20 11:24 AM, jojo wrote:
> One private question: What do you use? I remember that back then when I
> found out that Debian stable is pretty oldish I was always using
> testing. My teamleader recently told me that he's actually using
> unstable these days and prefers it over testing. I think if one wants
> halfway modern software there is only two options: Use Ubuntu(ish) or
> use Debian unstable? Right?
I use Debian Stable, and whenever I need something new (which is very
rare), then I do my own backports.
> Thanks so much for all this hints
My pleasure.
> One question: Often I
> read the workflow is to first create a source package and then the
> binary package from it. Is that true for python tools as well?
Yes.
> I mean
> there is no "source/binary" in this sense.
There is. I am not sure I understand...
> And this does not seem to be
> a source package but a regular package I would install as user using
> apt: https://salsa.debian.org/python-team/applications/rename-flac.git
This git is using pristine-tar, just like everything else within the
Python team. The debian/master branch contains the upstream sources plus
the Debian folder. This really is a source package repository.
> I guess I knew the answer already ;-) IMHO it's a shame that Discogs is
> not responsive at all to pull-requests in the last ~1-2 years, I would
> rather prefer if I package the official discogs_client (really
> maintained by discogs.com themselves) but to complete my task, I will
> just package my fork because it just works and has two features that I
> just require.
Best is if you can package upstream code, and add your specific patches
in debian/patches, so that they are well identified.
> Anyway, tell me what you think: First package my fork to get things
> done, then ask discogs.com if they want to be in debian and I would do
> it if they would finally work on some of the pulls that are open for
> almost "years" already.
Hopefully that works. I can't tell though, you'll see!
>> You're talking about joining the list. But what about the Python APP
>> team? Do you intend to join it?
>
> I think I still don't understand the difference between "being on the
> debian-python list" and joining the "python app packagning team". Please
> elaborate again! Most of all: What exactly would it mean if I "join the
> team".
Joining the list only means your receive messages from it. Joining the
team means you become a member of the Salsa Python APP group. We ask
people to first read our policy about it, and agree with it. Then you
can ask to join. If you're accepted, then you get write access to the
Git directly (and you can create new projects too).
Cheers,
Thomas Goirand (zigo)
