Bug#1061079: RFS pidgin-skype

[Gianfranco Costamagna]

Hello,


>It is really random, for upstream modification.
>
>But it looks I could have to do something for auto-glib2.0 
> transition.
>Which I don't really understand yet.

Just don't do any action should be fine.
There is a time_t -> time64_t transition ongoing (not yet, but will start soon 
TM)
this should happen for armel/armhf only, 

https://lists.debian.org/debian-release/2024/01/msg00033.html

>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?


up to you!

>- Wait again for the auto-glib2.0 
> 
>transition. to make all needed modifications, create a version with also 
>updated VCS fields and see what will happen for the backport?

This won't affect the package, it should be a no change rebuild done semi 
automatically
by Release Team, and only for 32 bit architectures excluded i386.

So, it is really up to you.

G.

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 
 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 
 
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 
 ha scritto:





Hello,

On Fri, 26 Jan 2024 18:36:02 +0100 Gianfranco Costamagna
 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
Logo certification NVDA expert 2022


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061079: RFS pidgin-skype

[Gianfranco Costamagna]

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

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.


G.


Il martedì 30 gennaio 2024 alle ore 16:28:14 CET, Patrick ZAJDA 
 ha scritto: 





Hello,

On Fri, 26 Jan 2024 18:36:02 +0100 Gianfranco Costamagna 
 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

Bug#1061079: RFS pidgin-skype

[Patrick ZAJDA]

Hello,

On Fri, 26 Jan 2024 18:36:02 +0100 Gianfranco Costamagna 
 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


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061079: RFS pidgin-skype

[Patrick ZAJDA]

Hi,

I changed the version to 20240122+gitab786a3+dfsg-1 because the patch I 
added has been applied upstream and hardening work now.

Changelog is the same and this version is uploaded on Mentors.

Best regards,

--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061079: RFS pidgin-skype

[Patrick ZAJDA]

Hello,

I fixed some lintian info and migrated debug symbols to new standard, 
they are now in pidgin-skybe-common-dbgsym instead of pidgin-skype-dbg


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061079: RFS: pidgin-skype/20230710+git5daf79d+dfsg-1 [ITA] -- Skype plugin for libpurple messengers (Pidgin-specific files)

[Patrick ZAJDA]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pidgin-skype":

* Package name : pidgin-skype
Version : 20230710+git5daf79d+dfsg-1
Upstream contact : Eion Robb 
* URL : https://github.com/EionRobb/skype4pidgin
* License : GPL-3+
* Vcs : https://salsa.debian.org/Nardol/pidgin-skype
Section : net

The source builds the following binary packages:

pidgin-skype-common - Skype plugin for libpurple messengers (common files)
pidgin-skype - Skype plugin for libpurple messengers (Pidgin-specific files)
empathy-skype - Skype plugin for libpurple messengers (Empathy-specific 
files)

pidgin-skype-dbg - Skype plugin for libpurple messengers (debug symbols)

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/pidgin-skype/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pidgin-skype/pidgin-skype_20230710+git5daf79d+dfsg-1.dsc


Changes since the last upload:

pidgin-skype (20230710+git5daf79d+dfsg-1) unstable; urgency=medium
.
* New maintainer (Closes: #856736)
* Declare compliance with Debian Policy 4.6.2
* New upstream version
* Remove support for Skype and Skype DBus plugins
* Add SkypeWeb plugin (Closes: #788922)
* Use debian/watch to update from upstream source excluding icons
* Remove patches
* debian/controle:
- Move from contrib to main
- Adjust build dependencies
- Change descriptions, now only provide Skype web
* debian/*.links: update paths to icons
* debian/*.install: update paths to icons
* debian/rules:
- Adjust to new directory structure
- Fix custom-compression-in-debian-rules

Regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature