Bug#1061079: RFS pidgin-skype

[Patrick ZAJDA]

Hello,

Le 30/01/2024 à 19:20, Gianfranco Costamagna a écrit :

Hello,
please switch VCS fields to the new location
https://salsa.debian.org/debian/pidgin-skype/-/blob/master/debian/control?ref_type=heads

Done, in both repositories.

And then just delete the old repository once the new version is uploaded in sid.

There is no rush, if you plan some upload in the near future.

It is really random, for upstream modification.

But it looks I could have to do something for auto-glib2.0 <https://release.debian.org/transitions/html/auto-glib2.0.html> transition.

Which I don't really understand yet.

I plan to make a backport for Bookworm. Do you think I should:
- Backport this version even if VCS fields are not up to date?

- Make a new version with update VCS fields and backport it as soon as it is in testing? - Wait again for the auto-glib2.0 <https://release.debian.org/transitions/html/auto-glib2.0.html> transition. to make all needed modifications, create a version with also updated VCS fields and see what will happen for the backport?

Thanks,

Patrick

G.


Il martedì 30 gennaio 2024 alle ore 16:28:14 CET, Patrick ZAJDA 
<patr...@zajda.fr> ha scritto:





Hello,

On Fri, 26 Jan 2024 18:36:02 +0100 Gianfranco Costamagna
<locutusofb...@debian.org> wrote:

Happily done, btw how do you feel about pushing your work somewhere

in Debian git repositories?

https://salsa.debian.org/debian/pidgin-skype might be a good place.

This way other people can help maintaining your package

I've just pushed all branches and tags to this repository and set CI.

What do you suggest me to do after knowing it is referenced in the
package meta-data?
Maintaining both repositories synced until there is a new version to
publish?

Thanks and best regards,

--
Patrick ZAJDA
<https://certification.nvaccess.org/>Logo certification NVDA expert 2022

OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature