First of all, thank Gustavo for your time spent packaging and maintaining 'yad' on Debian. I have noticed that 'yad' on Debian has been without apparent maintenance for years (since around the last quarter of 2018): no new upload at this time and all bug reports (since the "#919785 yad new version available" bug in January 2019) received no response. I wrote you a personal email but I got a non-existent email error: <gustavo@logicus.com.br>: host mail.logicus.com.br[162.240.50.69] said: 550 No Such User Here (in reply to RCPT TO command) I offer to take over as the new maintainer of 'yad' on Debian. Over the last few years, due to the age of yad on Debian and bug fixes and new features in new versions of 'yad', I have packaged (in the Debian way: debmake, debuild, lintian) and used several Yad versions on a daily basis without problems. Best regards, Alexis
Control: owner -1 Alexis <alexispm@disroot.org> Where do you provide the package? Do you need a sponsor for this?
Hello Alexis, Any success in updating yad? Were there any actual problems or this just faded out into oblivion? Is there any problem in packaging it? Do you need any help? Thanks Peter
I have created https://github.com/v1cont/yad/pull/233 in the upstream repo, it packages yad just fine to current (12.3). Peter
My sincere apologies. As MIA is immediate if the mail of the package maintainer has ceased to exist, I was attentive to receive a response in the following days. After a couple of weeks without any response I assumed that my email had been forgotten on the mailing list, my intention was to resend my request after the release of the next stable (I understand that people are now overwhelmed preparing the next release). It seems that the MIA was resolved in the middle of the Christmas holidays and I must have mistakenly deleted the mail along with hundreds of Christmas invitations. The package, created in the Debian way, I already have it done since the day of my email in November (and I've been using it ever since), so I only need a sponsor who kindly makes it easier for me to upload it to the Debian repo (currently I don't have the capacity to upload it). Note that I use yad version 7.2 because it is the most recent version that does not suffer bug(s) https://github.com/v1cont/yad/issues/107 https://github.com/v1cont/yad/issues/140 which make the package useless.
We believe that the bug you reported is fixed in the latest version of yad, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024523@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann <bage@debian.org> (supplier of updated yad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Tue, 30 May 2023 16:27:22 +0200 Source: yad Architecture: source Version: 7.2-0.1 Distribution: experimental Urgency: medium Maintainer: Alexis <alexispm@disroot.org> Changed-By: Bastian Germann <bage@debian.org> Closes: 1024523 1029395 Changes: yad (7.2-0.1) experimental; urgency=medium . * Non-maintainer upload. * Update debhelper to compat 10. * Switch to GitHub upstream and import new version (Closes: #1029395). * Salvage packgage (Closes: #1024523). Checksums-Sha1: 585d7a5c4e7d00deae6a4fefb59ff83ff4f7ed09 1550 yad_7.2-0.1.dsc ec44c4e39df4de9f8b05091febab58c61495b778 196116 yad_7.2.orig.tar.xz 724dbc4287e2f9c5cb7f6e5c9270cc0cde062a19 3212 yad_7.2-0.1.debian.tar.xz 70000d470e0b3e44cf11e9696a8620eee1bd2db9 14459 yad_7.2-0.1_source.buildinfo Checksums-Sha256: d5a936043845dcf201f0d6eed699afc86d11087ee6c098a4d3bd33947226dfa3 1550 yad_7.2-0.1.dsc cbca0f38c773693a559acbaf4458da95681494ec6bb3389ee7adb28171485a9a 196116 yad_7.2.orig.tar.xz 5fa7282bdc6965f54bbf75d0a4e7014ef233218830a107a104fa0cc98908da5f 3212 yad_7.2-0.1.debian.tar.xz c583244502b0a0c2e2b6efea44b9beb89e1ae44e4ac4beaa7de4b696d119c6a3 14459 yad_7.2-0.1_source.buildinfo Files: 6198c4f08bc1fa4c48b2844776e78a01 1550 utils optional yad_7.2-0.1.dsc eedb70bae00de863acfc78dfeed10bdc 196116 utils optional yad_7.2.orig.tar.xz 79b4333630975acb8feb1cac41f743e3 3212 utils optional yad_7.2-0.1.debian.tar.xz b086747da82e441de9d85e1843ffa9c4 14459 utils optional yad_7.2-0.1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmR2CFQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFJCoDACwdh9e4flqd9mxmn1FQS1u8Vld6Lg2dl/h GrID9oklXImlWjpQJEMBiyFrQwzK0QflYVRJX5l5Yize9afJGQIOt1spmwt1e29Y 1CknNvGLCG/h6POhevbJzw1xojSjnUDiHwab9XG8ZO1/R6kJ2EZ4k9btShtP01kp KPuCtSn+fxfBxJy6cXdmIlC9qCl11mNDKc0jLztMdwhtnIONQZkuU7jPVdLPL5O7 1zXB0z1tSibvvbqO5mzTpYsaA50apyqS0oK9PqQF/RiA/joLztrCc5yaCV56l1Iw p5f6N6ocnkd7/Qb5iAhP1ldt93m4MYQzGd/OPLcpskERVZndw8sK/1KT3BQkTjM/ saK4V07Hot5sbGXq3XObt+E9qziPQq8qSXR59vVSesvtRcv5MWhjb0HeKNtN1erZ 4ZFC2yb6M+Ido+NLIeCMVmslVux07qwbQCo98z0Z/SfP/dzJX6blkcrjbn07oBY/ iXRyyhUCoihoiQZTAD7iGCwtZGRbIZU= =nXJM -----END PGP SIGNATURE-----
Hi Alexis, To get the ball rolling I went ahead with importing the 7.2 release into experimental. Please hand in an unstable upload when the bookworm release is done. Thanks, Bastian
Thank you so much I had to find someone with permissions to upload to the repository. If possible, please upload the Yad 7.2 sources available on https://deb.picalibre.org/src/yad/ or its mirror https://deb2.picalibre.org/src/yad/ (binaries on https://deb.picalibre.org/pool/main/y/yad/ and https://deb2.picalibre.org/pool/main/y/yad/ ) It has some extra patches of its own. We have been testing these binaries on different architectures, all good. Best regards El 2023-05-30 17:11, Bastian Germann escribió:
Am 01.06.23 um 20:06 schrieb Alexis: I will have a look at them but for now upload to experimental. Please see the GitHub issue that I posted on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919785 This was brought to my attention after the upload. Please make sure that the update to 7.2 does not result in a regression, as claimed by the issue.