Hei!

I am reading the bug reports but except for the first few times, when there was 
a "mentor", my feeling from the communication with uploaders was that my work 
on the package is not welcome. I had the impression that I am being met either 
with silence or with replies akin to "don't care about what you write". So I 
was passive.

I am not sure how xfig and fig2sxd are related to photography, if that is what 
"phototools" should suggest. Or is it just the maintainer group called 
"phototools" that you think of?

I agree that separating program and packaging is a good idea. I can remove the 
packaging, i.e. the debian directory, from the upstream repo(s).

Cheers

Alexander

On 17 June 2026 09:21:37 UTC, Andreas Tille <[email protected]> wrote:
>Source: fig2sxd
>Version: 0.23-1
>Severity: important
>X-Debbugs-Cc: [email protected], [email protected], 
>[email protected], Debian PhotoTools Maintainers 
><[email protected]>, Package Salvaging Team 
><[email protected]>
>
>Hi,
>
>I would be interested in helping with fig2sxd, following the Package
>Salvaging procedure outlined in the Developers Reference[1]. From what I
>see, the package seems to meet the criteria for this process, and I'd
>like to support keeping it maintained in Debian. As the Salvage process
>suggests, here is a list of the criteria that I believe apply:
>
>  - Bugs filed against the package do not have answers from the
>    maintainer.
>  - There are QA issues with the package.
>
>I believe the package would be fit into the Phototools team, and I
>took the liberty to create the Salsa repository here[2]. If you choose
>not to accept the ITS, I'd be more than happy to help you move it to
>another location, such as debian/, or wherever you prefer. My goal is to
>make it as easy as possible for you to join the team. I'd also be
>delighted to assist in adding you as a team member if you could share
>your Salsa login.
>
>I noticed that you are upstream of this software and maintained the
>Debian packaging inside the upstream repository.  It has turned out that
>this might be not an optimal way to connect to the Debian community.
>Thus my offer to migrate the packaging to Salsa, which simplifies access
>of Debian developers regarding sponsoring your package, run Salsa CI as
>a QA means etc.  I hope you like this - if not feel free to merge my
>changes fixing the open bugs, specifically the patch for the Makefile
>which you might like to take over to your upstream code.
>
>Kind regards
>    Andreas.
>
>[1] 
>https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
>[2] https://salsa.debian.org/debian-phototools-team/fig2sxd
>[3] 
>https://salsa.debian.org/debian-phototools-team/fig2sxd/-/blob/master/debian/patches/buildflags.patch?ref_type=heads
>
>
>-- System Information:
>Debian Release: forky/sid
>  APT prefers testing
>  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 
> 'experimental')
>Architecture: amd64 (x86_64)
>
>Kernel: Linux 7.0.9+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
>Kernel taint flags: TAINT_WARN
>Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not 
>set
>Shell: /bin/sh linked to /usr/bin/dash
>Init: systemd (via /run/systemd/system)
>LSM: AppArmor: enabled

Reply via email to