Bug#1063511: RFS: pidgin-skype/20240122+gitab786a3+dfsg-2~bpo12+1 -- Skype plugin for libpurple messengers
Package: sponsorship-requests Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear mentors, I am looking for a sponsor for my package "pidgin-skype": * Package name : pidgin-skype Version : 20240122+gitab786a3+dfsg-2~bpo12+1 Upstream contact : Eion Robb * URL : https://github.com/EionRobb/skype4pidgin * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/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) 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_20240122+gitab786a3+dfsg-2~bpo12+1.dsc Changes since the last upload: pidgin-skype (20240122+gitab786a3+dfsg-2~bpo12+1) bookworm-backports; urgency=medium . * Rebuild for bookworm-backports. Regards, - -- Patrick Zajda -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmXFzgwACgkQnUrTW+on PcpPXQ//fUrHkyaaOuyMXACWJ2gGBBPCKUnUGPpxjyJ/RQY2mlIiBBcc7z5afHVV V9vxyTo2K0IMF6A9NW0lHC31LrO3ZZSG4Nfko9agripHECjF7hGvABKnzcZLNOpB xshtZ1TwCZqik28yWIK8IP+o+lGpF1Bp15L9XuQ32jWTHCq968yWc75jdUDzq755 qXs8/mp3uXvOA5QMm48uulHFRVgiNdY0yONPKex6+C0V3jWxWqBe1KnS+VrKwHhT 0lWeRe/4bKsIB5ZkjN+IcDtjzmSEpwLEVZaN0hnSgvekowKnYB/1UTeiVfNBI4n/ OXqDnOhi7H36s0pKPjPFQvla+F9HyVe3dUsvLftCQ1V7L+MKckYkn94zKq2GveUj Ej4IsQZCF+ojusioF8FlfUU4kJm4/cPeoxDOEWZwdHB8wGJf3VymcslxNz3uba1B 0cFuom38F/Dz335FAxybQisSytYHYV1jPIdT7Nb1CgHqV0DIXhvOOKw61ny6aWR/ de0XXi99yOqQiBYt0usbhacwExHu+TEzV4xFJ/bm4NYqpVSny4qlPwIxMQdc62fm VtCUZTP+krwh4RUk1R27rcCc0MBJ8D2Z+9KRaFnznvGGyOFkXKtKU5P1pcZVGCwi O6+dyP+zWBRDI5WLHxOiLwqEMy+lK91BCpifBcqD2aypYD/Lalc= =/25V -END PGP SIGNATURE-
Re: Request for Salsa repo on debian group
Hi, Le 02/02/2024 à 19:31, Patrick ZAJDA a écrit : Hello, Could it be possible to have debian/purple-discord and debian/harmony on Salsa and to have maintainer access on these new repositories ? Done, I asked a Debian developer offlist who created the repositories and granted me the maintainer access. I am going to import from the old repository and create a new Debian revision and RFS for both packages. Best regards, Patrick OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062812: RFS: pidgin-skype/20240122+gitab786a3+dfsg-2 -- Skype plugin for libpurple messengers
Package: sponsorship-requests Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear mentors, I am looking for a sponsor for my package "pidgin-skype": * Package name : pidgin-skype Version : 20240122+gitab786a3+dfsg-2 Upstream contact : Eion Robb * URL : https://github.com/EionRobb/skype4pidgin * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/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) 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_20240122+gitab786a3+dfsg-2.dsc Changes since the last upload: pidgin-skype (20240122+gitab786a3+dfsg-2) unstable; urgency=medium . * debian/control: update VCS URLs Regards, - -- Patrick Zajda -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmW+RdoACgkQnUrTW+on PcrCyRAArnI8ynoFCzsn8tAksdoeo3iXnzvZuplxxw7XY4Mt6zRPWm9R5R8pGWib fryPgXwqM59k43xBUwK/sEchNxPRrDmgFQGO30rVad3orfNknQdPNp8OIRyvoxFl Rk1V6F/d838WN4F03r7uQZon73xa/8AQpldU1feLZMQqWHs+7LKfbAUPrxYGFI7U etY2plX4OVLqhzKDGOfBYDnT0mLgI2Kr3UA/mSlF7Z8FPzinbxzSeQOs7ltVeDp3 aX8p154kmesjQRJp/FT3Y3Sg7mdJfeiZMZX5Nn5xVLEsB3ip3dngiWfCYyhURkwf TsrjAFCrktRb3MqNejiyvbqZaFVT3NKbaxb2/kx4HdV1sEkFKj2dVeKSkqmBY2UM ADlkf2hwTsdT3UNcTMXTliUnA5OeGDccJg96ysggzSQ3NtoUdj6jKEoxr2pZQ4tz 4scuFiNb9/DZ4dbAu3R/oolIiIqWdMP/fCzLUAwlW8i43OchCbb0TiF/BHSBJj7x DrA/4E5rJxqTs5qIgZBu4/LTbAst0/qaaxKibWWTQHuau4F2k6sh42U6aENMO45o XhEiBKvn5UgSflU32ciMKHKQqR49xzbiA6E+unE3WWs8REbaAF0HKpZeN76pBFL/ cctgE6cTwTX+qtEry2Hezsx91uJ+yFGMbcn1+QgduCQnjqRacvU= =tU/I -END PGP SIGNATURE-
Request for Salsa repo on debian group
Hello, Could it be possible to have debian/purple-discord and debian/harmony on Salsa and to have maintainer access on these new repositories ? I have already created Nardol/purple-discord and debian/harmony even if not referenced in respective debian/control of these packages yet. 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
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 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 <https://certification.nvaccess.org/>Logo certification NVDA expert 2022 OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061079: RFS pidgin-skype
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
Remaining bug in pidgin-skype
Hello, Now pidgin-skype has been sponsored thanks to Gianfranco Costamagna, what should I do with remaining? I have not read all of them yet but after a first look, the major part (not to say all) of remaining bugs are not still relevant because related to old plugins. This seems to be nothing more than common sense, but I prefer to ask the question before acting: should I prepare a message and close all bugs that are no longer relevant, specifying that only the web plugin is available and that the bug should therefore be closed because related plugin is not part of the package anymore? I found information about when a specific fix was implemented but not in this kind of case. 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
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
Re: Version changing while there is an opened RFS
Hello, Thanks, so now I know I was on the right way with what I did on the Salsa repository [1]. In fact at first my wish was to switch from snapshot versions to released version, but 1.7 is not greater than the actual version. So even if it is not the best solution, it looks I will have to keep using Git snapshot versions... [1]: https://salsa.debian.org/Nardol/pidgin-skype Best regards, Patrick Le 23/01/2024 à 16:44, Gianfranco Costamagna a écrit : Hello, You can maybe do something like: download tarball from last master branch https://github.com/EionRobb/skype4pidgin/tarball/master (automatic tarball generation) call it something like 20240123+gitecef199+dfsg-1 20140930+svn665+dfsg-2 $ dpkg --compare-versions 20240123+gitecef199+dfsg-1 gt 20140930+svn665+dfsg-2 && echo true true G. Il martedì 23 gennaio 2024 alle ore 09:40:11 CET, Patrick ZAJDA ha scritto: Hello, Le 23/01/2024 à 01:27, Gianfranco Costamagna a écrit : I intent to adopt pidgin-skype package. The package version is based on last upstream Git main branch commit, to keep same versioning the package has already. To successfully enable hardening, I created a patch I contributed upstream by opening a pull request. The pull request was merged some hours after. What should I do now? Continue with the same version using the patch? Bump new version and in this case, should I only change the actual version in debian/changelog or create a new version to change upstream version and keep the version the RFS is opened for? Thanks and best regards, As first answer? Please ask upstream to release something new, don't make every distribution rely on git snapshots, because it's hard to understand when something is "stable" enough without a tagged release. If this isn't possible, either packaging a new snapshot or applying it as patch and bump Debian revision from N to N+1 is ok. (maybe it depends on the patch size, if small, a patch is ok to avoid import of a new tarball, if the patch is huge, maybe the latter is preferred. Also, there might be other commits between the Debian snapshot and the patch upstream acceptance, so check all the commits for their stability). Sorry for not providing a good answer but "it depends" is probably the right one. G. Firstly, I would really have preferred to avoid these kind of version :-) But the latest release was about three years ago, maybe I could ask the project maintainer to tag a new version... Before the yesterday commit which applies the patch, previous was on July 10, 2023. And because actual package version is an SVN snapshot, I don't know how I could change version chem without using epoch. Woule yyymmdd+realyversion+dfsg be OK? But there is still the fact latest version is very old and a lot of fixes have been applied since. Anyway, if I read you correctly and because my patch modifies only two lines with only one useful for the Debian package, maybe it is OK to wait for a review of the actual package I opened a RFS for. Thanks and best regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Version changing while there is an opened RFS
Hello, Le 23/01/2024 à 01:27, Gianfranco Costamagna a écrit : I intent to adopt pidgin-skype package. The package version is based on last upstream Git main branch commit, to keep same versioning the package has already. To successfully enable hardening, I created a patch I contributed upstream by opening a pull request. The pull request was merged some hours after. What should I do now? Continue with the same version using the patch? Bump new version and in this case, should I only change the actual version in debian/changelog or create a new version to change upstream version and keep the version the RFS is opened for? Thanks and best regards, As first answer? Please ask upstream to release something new, don't make every distribution rely on git snapshots, because it's hard to understand when something is "stable" enough without a tagged release. If this isn't possible, either packaging a new snapshot or applying it as patch and bump Debian revision from N to N+1 is ok. (maybe it depends on the patch size, if small, a patch is ok to avoid import of a new tarball, if the patch is huge, maybe the latter is preferred. Also, there might be other commits between the Debian snapshot and the patch upstream acceptance, so check all the commits for their stability). Sorry for not providing a good answer but "it depends" is probably the right one. G. Firstly, I would really have preferred to avoid these kind of version :-) But the latest release was about three years ago, maybe I could ask the project maintainer to tag a new version... Before the yesterday commit which applies the patch, previous was on July 10, 2023. And because actual package version is an SVN snapshot, I don't know how I could change version chem without using epoch. Woule yyymmdd+realyversion+dfsg be OK? But there is still the fact latest version is very old and a lot of fixes have been applied since. Anyway, if I read you correctly and because my patch modifies only two lines with only one useful for the Debian package, maybe it is OK to wait for a review of the actual package I opened a RFS for. Thanks and best regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Version changing while there is an opened RFS
Hello, I intent to adopt pidgin-skype package. The package version is based on last upstream Git main branch commit, to keep same versioning the package has already. To successfully enable hardening, I created a patch I contributed upstream by opening a pull request. The pull request was merged some hours after. What should I do now? Continue with the same version using the patch? Bump new version and in this case, should I only change the actual version in debian/changelog or create a new version to change upstream version and keep the version the RFS is opened for? 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
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)
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
Re: Help with GBP
Le 31/12/2023 à 18:16, Andrey Rakhmatullin a écrit : On Sun, Dec 31, 2023 at 05:25:24PM +0100, Patrick ZAJDA wrote: First of all, I switched to the branch debian/stable/master where last bookworm backport is. Then I merged the tag debian/2.0.18-1 to have all commits until the version I wish to backport. Firstly, when running gbp dch --bpo I cannot pass also the --commit-msg or any commit related switch because "* unreleased" is added to the changes list below "* Rebuild for bookworm-backports". How can I avoid it? To avoid it temporarily, I simply used dch --bpo which made things as usual for me. But I really want to use gbp in the cleanest way. I don't think using dch doesn't count as that. It's really optional. Thanks, it looks it is another moment I ask myself too much questions... So I will continue doing this way for this part. In the VCS there is the commit for the changelog, then another commit which contains the changes in its message, but this does not modify any file. I use Git a lot but it is the first time I encounter a commit which modify nothing. Do you mean c28a8d75ce3277b104cd195548e6252bf2dbd4e0, "Import Debian changes 2.0.15-2~bpo12+1"? Yes. I guess it's from running gbp-import-dsc, it's empty because the same package was imported that was built from the previous commit, and I don't think running it was intended or is needed. I confirm, I have the same after running gbp import-dsc after building the package. And it created the tag for the backports version. I did not know it was possible to do this kind of thing in Git. So if I understand correctly, I did things right for this backport? The next (and last I hop) question is to know how to proceed to upload, uploading it myself to mentors and ask for a sponsor or ask the team? I wrote to the team mailing list without success about these questions I asked here. And I did not find the answer in documentations available on mentors.debian.net but I won't protest if someone replies I have not searched the right place ;) Thanks and best wishes for this new year, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Help with GBP
Hello, I wish to make a backport for Bookworm of Mosquitto 2.0.18-1, which is on Debian testing. I joined the Debian IOT Team, specifying I would like to make this backport, which has been accepted. I read some documentation for GBP, but I am unable to have the same result as the Mosquitto package VCS [1]. [1]: https://salsa.debian.org/debian-iot-team/mosquitto First of all, I switched to the branch debian/stable/master where last bookworm backport is. Then I merged the tag debian/2.0.18-1 to have all commits until the version I wish to backport. Firstly, when running gbp dch --bpo I cannot pass also the --commit-msg or any commit related switch because "* unreleased" is added to the changes list below "* Rebuild for bookworm-backports". How can I avoid it? To avoid it temporarily, I simply used dch --bpo which made things as usual for me. But I really want to use gbp in the cleanest way. Then I build the package with gbp build-package to check if all is OK. I thought to automatically add the tag but I cannot obtain the same kind of log there is in the VCS. In the VCS there is the commit for the changelog, then another commit which contains the changes in its message, but this does not modify any file. I use Git a lot but it is the first time I encounter a commit which modify nothing. Could someone explain it to me? I am totally lost with GBP, more I read documentation and less I feel I really understand something. I made a merge request [2] because I am not sure at all, I only feel I made disorder. I have already proposed some backports before, not using GBP. I thought I would have understood by reading some docs I found but I really need help to understand why and what I did wrong and how to do right. [2]: https://salsa.debian.org/debian-iot-team/mosquitto/-/merge_requests/12 I hop I explained correctly these things which are confused for me. As a beginner I thought these beginner question could have their place on this list. Best regards. -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059029: RFS: harmony/0.7.2-1~bpo12+1 -- program and library for creating and managing Discord accounts
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "harmony": * Package name : harmony Version : 0.7.2-1~bpo12+1 Upstream contact : * URL : https://github.com/taylordotfish/harmony/ * License : GPL-3+ * Vcs : Section : web The source builds the following binary packages: python3-harmony - program and library for creating and managing Discord accounts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/harmony/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/h/harmony/harmony_0.7.2-1~bpo12+1.dsc Changes since the last upload: harmony (0.7.2-1~bpo12+1) bookworm-backports; urgency=medium . * Rebuild for bookworm-backports. . harmony (0.7.2-1) unstable; urgency=medium . * New upstream release. * New maintainer (closes: #1032369) * Use tags to determine upstream version * Declare compliance with Debian Policy 4.6.2, no changes needed. Regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts
Hi, Le 12/12/2023 à 07:57, Paul Wise a écrit : * Suppress Lintian warning about man page It is incorrect to suppress valid lintian warnings, instead you should either ignore them or fix them, probably upstream in this case. I removed the suppression of the lintian warning and sent the package again. I plan to generate a manpage using help2man then suggest it upstream after some eventual modifications, I think it can wait for a next version seeing there are only --help and --debug in command line parameters. While this package isn't possible to autopkgtest easily since it is for a live proprietary service, you could add superficial testing that the Python module can be imported; in the Source section of debian/control: Testsuite: autopkgtest-pkg-python Done in the last sent package of today. These issues may be interesting to work on if you have spare time: Upstream may like to modernise the Python packaging: https://packaging.python.org/en/latest/tutorials/packaging-projects/ pycodestyle/pydocstyle/pyflakes3/pylint/vulture/ruff report some (likely minor) code issues if you want to contribute fixes upstream. Looks feasible, also for a next version to have all upstream or do you think all should be done for this version? Best regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts
Hello, I missed to include the fix in debian/watch to check for upstream version, which was already documented in the changelog. I re-uploaded the package to Mentors to fix my mistake. Best regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "harmony": * Package name : harmony Version : 0.7.2-1 Upstream contact : * URL : https://github.com/taylordotfish/harmony/ * License : GPL-3+ * Vcs : Section : web The source builds the following binary packages: python3-harmony - program and library for creating and managing Discord accounts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/harmony/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/h/harmony/harmony_0.7.2-1.dsc Changes since the last upload: harmony (0.7.2-1) unstable; urgency=medium . * New upstream release. * New maintainer (closes: #1032369) * Use tags to determine upstream version * Declare compliance with Debian Policy 4.6.2, no changes needed. * Suppress Lintian warning about man page Regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057022: RFS: purple-discord/0.9.2023.10.23.git.f8b0c59-1~bpo12+1 -- Discord messaging service plugin for libpurple
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "purple-discord": * Package name : purple-discord Version : 0.9.2023.10.23.git.f8b0c59-1~bpo12+1 Upstream contact : * URL : https://github.com/EionRobb/purple-discord/ * License : GPL-3+ * Vcs : Section : net The source builds the following binary packages: purple-discord - Discord messaging service plugin for libpurple To access further information about this package, please visit the following URL: https://mentors.debian.net/package/purple-discord/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/purple-discord/purple-discord_0.9.2023.10.23.git.f8b0c59-1~bpo12+1.dsc Changes since the last upload: purple-discord (0.9.2023.10.23.git.f8b0c59-1~bpo12+1) bookworm-backports; urgency=medium . * Rebuild for bookworm-backports. Regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056402: RFS: purple-discord/0.9.2023.10.23.git.f8b0c59-1 [ITA] -- Discord messaging service plugin for libpurple
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "purple-discord": * Package name : purple-discord Version : 0.9.2023.10.23.git.f8b0c59-1 Upstream contact : * URL : https://github.com/EionRobb/purple-discord/ * License : GPL-3+ * Vcs : Section : net The source builds the following binary packages: purple-discord - Discord messaging service plugin for libpurple To access further information about this package, please visit the following URL: https://mentors.debian.net/package/purple-discord/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/purple-discord/purple-discord_0.9.2023.10.23.git.f8b0c59-1.dsc Changes since the last upload: purple-discord (0.9.2023.10.23.git.f8b0c59-1) unstable; urgency=medium
