Your message dated Sat, 16 Aug 2025 02:54:13 +0000 with message-id <[email protected]> and subject line Bug#1105858: Removed package(s) from unstable has caused the Debian Bug report #1105858, regarding RM: unagi -- RoM; orphaned upstream, possibly not useful any more 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 [email protected] immediately.) -- 1105858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105858 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: unagi Version: 0.3.4-1 Severity: important X-Debbugs-Cc: Arnaud Fontaine <[email protected]>, Package Salvaging Team <[email protected]> Dear maintainer, Your package was highlighted in the Bug of the Day[1] initiative and I was considering migrating the package to Salsa as well as moderinsing the packaging. However, when locking at it I wonder whether this time is well spent. I wonder whether removing unagi from Debian is more senible since: * It is a leaf package. * Popcon was always low and is decreasing https://qa.debian.org/popcon-graph.php?packages=unagi&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 * Seems to be obsolete and largely unmaintained upstream * Most users today rely on modern compositing managers This bug just serves as a basis to discuss the removal of this package. It would be great of you could raise your opinion in the next month. In case the package should be kept in unstable, please answer accordingly. In case the package should be removed from unstable, you may reassign this bug report: Control: severity -1 normal Control: retitle -1 RM: unagi -- RoM; orphaned upstream, possibly not useful any more Control: reassign -1 ftp.debian.org Control: affects -1 + src:unagi If you (or some interested user) will not respond I might bump this bug to severity serious after Trixie release to raise more awareness and will reassigned the bug after a sufficient waiting period. In case you disagree with the above, please add a wontfix tag to this bug. Control: tags -1 + wontfix This would be some signal for me to spent time into moving the package to Salsa in case you might agree with this move. As stated earlier your package was highlighted in the Bug of the Day[1] 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://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 ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: unagi | 0.3.4-1 | source unagi | 0.3.4-1+b2 | riscv64 unagi | 0.3.4-1+b4 | amd64, armel, armhf, i386, mips64el, ppc64el, s390x unagi | 0.3.4-1+b5 | arm64 unagi-dbg | 0.3.4-1+b2 | riscv64 unagi-dbg | 0.3.4-1+b4 | amd64, armel, armhf, i386, mips64el, ppc64el, s390x unagi-dbg | 0.3.4-1+b5 | arm64 unagi-dev | 0.3.4-1+b2 | riscv64 unagi-dev | 0.3.4-1+b4 | amd64, armel, armhf, i386, mips64el, ppc64el, s390x unagi-dev | 0.3.4-1+b5 | arm64 ------------------- Reason ------------------- RoM; orphaned upstream, possibly not useful any more ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/1105858 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
