Dear Debian GTK/GNOME Team members,

I maintain some software that needs 3.x version of libsigc++ library in its newer releases[1]. However, only the 2.x branch is available in Debian [2].
As a result, I am wondering if it's okay for us to package the 3.x branch.

I have prepared a packaging repo at [3] with completed packaging instruction and copyright review. I am wondering if it's okay to maintain libsigc++-3.0 under Debian GNOME Team similar to the 2.x branch package, or if I should
place the packaging repo under salsa.debian.org/debian/ and have it uploaded
to NEW queue for review first.

If you find any issues with my packaging scripts, please let me know
(ideally with a patch). Any suggestion would be appreciated. A known issue
is the Uploader substitution in control.in for GNOME team and I haven't
figured out the solution, but this should be a minor problem.

Thanks,
Boyuan

[1] https://github.com/wwmm/easyeffects/issues/1000
[2] https://tracker.debian.org/pkg/libsigc++-2.0
[3] https://salsa.debian.org/byang/libsigcplusplus-3.0

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmJ9byIACgkQwpPntGGC Ws452Q//R58oUSt2ZFmOvmf2xO8Ky8t+TnsZ9N9nDnWRGCH1y592PW2tHcShvHIS o1L4sdw809g7ya856xvElJe0EWSnz3D3jJQGbq1LZbf5vp908xx9YWuqpMiljQCP 0V4QRMpeF2qobVpnJZ6m9YoP/ys6PVUvLX+UBGQVLqpq98pGTUljTtfwh1qPwrYy OIcEXlk6C1RDDj71s2j4XXO/BXHOZPm8qFjHtUuViPjGlIhtwxtdqM2kvIOmO1KI wrmehuVOSiALDOCSzkMAeB2cfxyIsO+mAxzLBAl6slEAvBJQmYK+ZMqSe7q8UxRH lHYJhrJPDoG5ELiWawQGcWDgPNhhru4fhxPVayOBu4XXb+LbDEV6ejPpgAnsNmlc i6hfXsOWPd8T9gp09lKiprgcYkUbvwIjWlXBD8GHTFNctEJ5qKV+3BthhH7pH/oQ bXWoh2sMm11NsVz7W3SRlt49R6++axAqHxzruqZvIVKzFwVOyfOVAI91ewmyilEf TYDjhmish7ajwyoZmLXhbbYSeJLE87iA06ic3KSK8NwJTm1kwi6QkSDr0pCW1SWM 4Y3p1CqTXx4SZQTEV3L2wkb9SBQfloE4bbPtJkgEjw6ZBop/q/HVOPmK4pOWmc3W 04Dcbg8wJL+2fIurt2UHw2Ixaun2daSWx5z7wZOFhWLYw8OWaxs=
=qggO
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

在 2022-05-12星期四的 16:33 -0400，Boyuan Yang写道：

Dear Debian GTK/GNOME Team members,

I maintain some software that needs 3.x version of libsigc++ library in
its
newer releases[1]. However, only the 2.x branch is available in Debian
[2].
As a result, I am wondering if it's okay for us to package the 3.x branch.

I have prepared a packaging repo at [3] with completed packaging
instruction
and copyright review. I am wondering if it's okay to maintain libsigc++-
3.0
under Debian GNOME Team similar to the 2.x branch package, or if I should place the packaging repo under salsa.debian.org/debian/ and have it
uploaded
to NEW queue for review first.

If you find any issues with my packaging scripts, please let me know
(ideally with a patch). Any suggestion would be appreciated. A known issue
is the Uploader substitution in control.in for GNOME team and I haven't figured out the solution, but this should be a minor problem.

Thanks,
Boyuan

[1] https://github.com/wwmm/easyeffects/issues/1000
[2] https://tracker.debian.org/pkg/libsigc++-2.0
[3] https://salsa.debian.org/byang/libsigcplusplus-3.0

Just an update: this is now in Debian Sid: https://tracker.debian.org/pkg/libsigc++-3.0 . The git packaging repo is at https://salsa.debian.org/debian/libsigcplusplus-3.0 . Feel free to make any updates that you find necessary.

Thanks,
Boyuan Yang

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmKuaC0ACgkQwpPntGGC Ws5Lmw/+JRHIjsfU5SU60PKU3FicFRrxsIjjSXtWA5mTpZ5x4xpOcO6i+XeGsCqd Civ7KdEpRQ4qK7JHf7wn5gaQ8ADXU0vMArwYFzh7pB+LjFVv3kEVtbkexu4TV9HE v8Ms5GrC4MLHrln1UTU5Ibm6g2uQaBphncBCY66Y9FsFMEQkzWz0hRCUF4aHVgZ4 yF+mlWGTATGVfLecy7SCmidIcmgpKjYG3qw0iCL6XfT5yPM9OVea5tEA3YNJ9hDw 5+68LEEJwA6Z/28i8bYC6TN1rkqVkOPRnsY23D9TlHunXcSZIBLq5HDWi3WGVyMW vWXzyjC/Mns4vl7izU4osUUBA9k+8QvY26wOnzpIJWE9EPcshYw2sflvg0IG2Bmq npVgFLrOl1tqT5AbSRuEbhWhGez+SFvGNcq1dbeBMa54CujE/8sdpG59y/6+8jZx +Rs/3pq2PzByBORpfisioA99oVk5nCTTFxb3FoJ9zEFB9QceNp1I4uin8GndARmy yjnpcIvXPnkHtESqw6oqY2OSXrs95vBgslQlX6w0yE3FAiFki2wmAe5al4b4z9KV jlrrRQBq8B2kBXpF0ZaH4OmOynGsvpWKWis2T7PyLxTIJWH/F2WR4OvV8rZCI4fF hf7Vj7Eze2Ce4QoXQDvmacNU0qLVwUhy57ZAlxnZgfZqOmj9Bb8=
=4TTO
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Jun 18, 2022 at 8:05 PM Boyuan Yang <byang@debian.org> wrote:

Just an update: this is now in Debian Sid: https://tracker.debian.org/pkg/libsigc++-3.0 . The git packaging repo is at https://salsa.debian.org/debian/libsigcplusplus-3.0 . Feel free to make any updates that you find necessary.

Hi,

I apologize that we didn't reply to your email earlier. Thank you very
much for packaging this library update!

I went ahead and pushed the packaging to https://salsa.debian.org/gnome-team/libsigcplusplus-3.0
You'll need to re-clone because it uses different branch names
(upstream/latest instead of upstream especially).

gbp clone git@salsa.debian.org:gnome-team/libsigcplusplus-3.0.git

I rebased your commits on top of the libsigc++-2.0 git repo to
preserve the git history & some packaging details.
I guess you should get the https://salsa.debian.org/debian/ repo
deleted or at least archived now.

We don't have documentation for how to package a renamed library like
this and the rest of our documentation [1] is missing a lot of
details. Sorry!

I have begun work on packaging gtkmm4.0 and its dependencies. Did you
have any other related app you were looking at packaging or is it just easyeffects?

Please let us know if you need any more help.

[1] https://wiki.debian.org/Gnome/Git

Thank you,
Jeremy Bicha

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

在 2022-06-20星期一的 17:07 -0400，Jeremy Bicha写道：

On Sat, Jun 18, 2022 at 8:05 PM Boyuan Yang <byang@debian.org> wrote:

Just an update: this is now in Debian Sid: https://tracker.debian.org/pkg/libsigc++-3.0 . The git packaging repo is at
https://salsa.debian.org/debian/libsigcplusplus-3.0 . Feel free to make any
updates that you find necessary.

Hi,

I apologize that we didn't reply to your email earlier. Thank you very
much for packaging this library update!

I went ahead and pushed the packaging to https://salsa.debian.org/gnome-team/libsigcplusplus-3.0
You'll need to re-clone because it uses different branch names (upstream/latest instead of upstream especially).

gbp clone git@salsa.debian.org:gnome-team/libsigcplusplus-3.0.git

I rebased your commits on top of the libsigc++-2.0 git repo to
preserve the git history & some packaging details.
I guess you should get the https://salsa.debian.org/debian/ repo
deleted or at least archived now.

We don't have documentation for how to package a renamed library like
this and the rest of our documentation [1] is missing a lot of
details. Sorry!

I have begun work on packaging gtkmm4.0 and its dependencies. Did you
have any other related app you were looking at packaging or is it just easyeffects?

Easyeffects used to depend on gtkmm4.0 but not anymore. I think there's no other extra package work needed for now.

I noticed that libsigc++-3.0/3.2.0-4 did not properly handle symbol files,
such as using 2.x version strings, debian revision in versions (lintian
error) and unmatched symbols for different archs. Since you added this
symbol file, it would be great if you can fix it and have libsigc++-3.0 migrated to Testing at least once.

Thanks,
Boyuan Yang

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmKyMa0ACgkQwpPntGGC Ws6Yww/8D/fZpFw1JDLsF1mg8LLbO//OXzM/5/kKva113jM3FgjbIvjKcEx9oFRx 5h+ddaAEgStEZ+GgvckOmhPKvPSq1PyP6QV6NgW8/dfo7gQUmDpbmGmFHh2vVCpp fAp9Hyo93TqJ2jun4ztHxeSORGs3TexiajzMGpPs8pXkotk/UbHuWV9V0epg0cK1 jvxjZO72542Ds6dPUxzOk+EnJhYPt6YyJ1F4jEIJ65tqbuhQqijVZC+f3dpo6TI+ 2v8iVwRbX7T2pUUaQ3rM9qmECdCopmQKwDAYUfgN8gHE6kfjVo4cxeA2JYGZiNf6 hYFfS11dl9piMWZypAQdzGb3xE4YzCOKWedM0RbsKFUxHQ0t7AQJuOxwPnSy8yPr 54L3qAiGpnfrwGmZgkBBIqEFVldoCiaMVVuOZdHbRXGcK6JeTdjEIJ/gCycFHZiG 2VfYcJGqDuGuRc2lB0ut0lsVdn16musGsLShNncxZz7OfWW6aWkuz4ncu8gDzJ0M HDSrxsfkHn6lIiIDGjMB2scK1tRP/T0qywL3PnMk69tK9bgG4ENVG2AzASjPDSOa trinUtOqB+bSbQIG3NJ0mGJo41ttoQaDpJsqj+SVr+X4bpBGib6fhkcmgepbq501 bDS6n9njgnOe0ZIE37U3dE2dH+12fmGoTHsCLnZu/p0BCUPsBVU=
=KlLI
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, Jun 21, 2022 at 5:01 PM Boyuan Yang <byang@debian.org> wrote:

I noticed that libsigc++-3.0/3.2.0-4 did not properly handle symbol files, such as using 2.x version strings, debian revision in versions (lintian error) and unmatched symbols for different archs. Since you added this
symbol file, it would be great if you can fix it and have libsigc++-3.0 migrated to Testing at least once.

Sorry I didn't get to it right away, but thank you for the new upload!

Jeremy Bicha

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)