Your message dated Sat, 10 May 2025 23:19:02 +0000 with message-id <e1udttc-00etya...@fasolo.debian.org> and subject line Bug#1104828: fixed in fortunes-mario 0.21-2 has caused the Debian Bug report #1104828, regarding ITN: fortunes-mario to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1104828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: fortunes-mario Version: 0.21-1.1 Severity: important X-Debbugs-Cc: Fernando Ike de Oliveira <f...@midstorm.org>, Carlos Henrique Lima Melara <char...@debian.org>, 1073...@bugs.debian.org, 847...@bugs.debian.org, Package Salvaging Team <team+salv...@tracker.debian.org> Hi, As per bug #847262 I did not included Otavio in CC. However, I hope that either you Charles or some of your friends might put a new maintainer ID and might volunteer to maintain this probably very low maintenance package. At least the RC bug is fixed and the package can be just uploaded. I would have no problem to put my own name as maintainer but I'd prefer someone from Brasil taking responsibility. If this is not happening I will decide what to do in 21 days ... (Now the ITN template follows ...) This is an attempt to introduce a new procedure, which I propose to call Intend To NMU. While we have an established process for making minimal, fine-grained changes to a package, it does not cover broader improvements such as migrating to Salsa, updating the Standards-Version, or adjusting the debhelper compatibility level. However, some packages could benefit from more extensive changes, and this procedure aims to provide a structured way to implement them. Unlike the well-established Package Salvage procedure[1] which requires an active Uploader, the goal here is to allow collaborative work on a package on Salsa, even if no active uploader expresses interest in maintaining it. If you do not agree to large-scale changes to your package, including maintaining it on Salsa, you are welcome to close this bug or tag it as 'wont-fix' to inform others. There is no obligation to continue reading if your stance is clear, and your decision will, of course, be respected. Otherwise, I will follow the well-established timing of the ITS procedure, waiting 21 days before performing a Non-Maintainer Upload (NMU) to delayed=10. Specifically, since we are approaching the freeze the upload will be delayed until after Trixie is released. This procedure has not yet reached consensus-I am simply exploring whether it could be accepted. It remains open for discussion, particularly at DebConf25. Please keep in mind that the goal of this process is to assist in keeping your package up to date. If you have suggestions for improving it, your feedback is most welcome. I'm interested in NMUing your package FIXME. It meets the following criteria for the ITN procedure - NMU - Bugs filed against the package do not have answers from the maintainer. - There are QA issues with the package. - Not on Salsa but it could profit from team maintenance - Not uploaded by you in the last 5 years - Standards-Version < 4 I have set up a repository within Debian/[2]. This team functions similarly to the former collab-maint on Alioth, allowing any Debian Developer to make team uploads. I understand that some maintainers may prefer not to transition to collaborative maintenance, and I want to emphasize that this is not intended as a hostile action. My goal is to make the transition to using a Git repository on Salsa smoother and more convenient for you. Your package was highlighted in the Bug of the Day[3] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to familiarize newcomers with a consistent Git-based workflow. Kind regards Andreas. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://salsa.debian.org/debian/fortunes-mario [3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.12.22-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Source: fortunes-mario Source-Version: 0.21-2 Done: Carlos Henrique Lima Melara <charlesmel...@riseup.net> We believe that the bug you reported is fixed in the latest version of fortunes-mario, 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 1104...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carlos Henrique Lima Melara <charlesmel...@riseup.net> (supplier of updated fortunes-mario 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 09 May 2025 16:38:30 -0300 Source: fortunes-mario Architecture: source Version: 0.21-2 Distribution: unstable Urgency: medium Maintainer: Carlos Henrique Lima Melara <charlesmel...@riseup.net> Changed-By: Carlos Henrique Lima Melara <charlesmel...@riseup.net> Closes: 847262 1073475 1104828 Changes: fortunes-mario (0.21-2) unstable; urgency=medium . [ Andreas Tille ] * Former repository where Vcs fields were pointing to was archived in 2020 thus moving packaging to Salsa in Debian team * Standards-Version: 4.7.2 (routine-update) * debhelper-compat 13 (routine-update) * Secure URI in copyright format (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Remove trailing whitespace in debian/copyright (routine-update) * watch file standard 4 (routine-update) * Fix LaTeX build Closes: #1073475 * d/copyright: review * Secure URI in Homepage . [ Carlos Henrique Lima Melara ] * Take over maintainership. Closes: #847262, #1104828 * debian/dirs: remove. Directories used are automagically created. * debian/gbp.conf: add default branches and sign-tags options. Checksums-Sha1: 971a60262b6f62264de5a206cff74243bf94259d 2124 fortunes-mario_0.21-2.dsc f97a2aa47b5fd9bdd829c108f426669b6c41ede2 4960 fortunes-mario_0.21-2.debian.tar.xz 728043334fd822846d584871a18f4f554c893f9f 10514 fortunes-mario_0.21-2_amd64.buildinfo Checksums-Sha256: ef4ebac26b9f785d023063d53c181c528fa761f953e4d5c2f3bbbe04492ae07e 2124 fortunes-mario_0.21-2.dsc 83449199e5823b7c8a07e3dc65fade8633fd7b38fd6949f4cba4362df967fc4e 4960 fortunes-mario_0.21-2.debian.tar.xz 13f2b5e4f407985a0fc614e3dd9999d11357eaf4743cf6885c13397c641f22c1 10514 fortunes-mario_0.21-2_amd64.buildinfo Files: 3038d133796779c8e34308b0ae45068f 2124 games optional fortunes-mario_0.21-2.dsc 584593e63cdcbe0fee4088fe831b0e27 4960 games optional fortunes-mario_0.21-2.debian.tar.xz d6dea5345fa5c4f545223be48d963826 10514 games optional fortunes-mario_0.21-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJNBAEBCgA3FiEECgzx8d8+AINglLHJt4M9ggJ8mQsFAmgf2uYZHGNoYXJsZXNt ZWxhcmFAcmlzZXVwLm5ldAAKCRC3gz2CAnyZCyAND/9tkCmU/RgYx2Gq3nJs3w80 siHQeTbC9qtrwzO/7GKsgcDbk+xBdpGQWozo60ZQYcf5ZXd0OqRNzqjuZMKczwDX pJ/cT4pkXesfqqABC1N3O9ZyXfGm7Ija/H4G+ypQPttmAYZ5WLYI6kucjEhNbekw DyOBt+uuJ0XO8QGiLK8sGMuX1a9BXM/QlcjIEbsO75BK8eADl7s+kELYtGtbbK8+ eymOrc9XwgYPt40PWRmUNkBp5KepRinh2iC+Hhq9f1T1hFBE+6z/MO9wLT/tO90y XR20vKs7v+sJ3tabyxuCDfhum8pncbdu0rg8l8UsxGKsVVifQWuTgTFDYqpy1p9f b8tJdNDitmAD9mhiNzhdSY+rwpY74LC+2SDuflbN2f8UqnWo/0YKK/CvyhMQraw/ TzpfARC817ZxFCuJudwcFSED9RU2SsnC6twRJzj+qq/kslhHnokRpdkKfha7yTZ9 r5lI1fdvXJpa17pNr4cty6oLnxIEKu/lA8NjfrV6tacw4zNPxVHdhOwnEeTHlVFH V1aOG2mjY8V00Eez3MiX5ro03eCb/WRxnte+AlnPU6JTHvV/9E5k5TxabZLoPRNt 5RSzzQ5TXneKbuB144uKT7b+xnYek2QOKusIMJ4e8Lcu4mAPgEELirjUPPKg2oFQ V/Fs5PFGD/OsFzrAiXGUOw== =jwwT -----END PGP SIGNATURE-----
pgpY7_pefZ0jt.pgp
Description: PGP signature
--- End Message ---
