Source: libaosd Version: 0.2.7-1.1 Severity: important X-Debbugs-Cc: [email protected], [email protected], [email protected], Eugene Paskevich <[email protected]>, Package Salvaging Team <[email protected]>, Eric Cooper <[email protected]>, boffi <[email protected]>, Francois Fleuret <[email protected]>, William Pitcock <[email protected]>
Dear Eugene, I had a look into libaosd some time ago and even created a Git repository on Salsa[1] for it. While thinking twice about this package I'm wondering whether it would be better to remove it from Debian for the following reasons: * It accumulated some long standing bugs that show that it is not really convenient to use or needs upstream work nobody really cares about * It is dead upstream and can be only found in the web archive (see Homepage field in the Git repository) * The popcon *usage* (=vote) numbers where never really high and decreased after 2014 https://qa.debian.org/popcon-graph.php?packages=libaosd-text2&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 * Your last upload was in 2010 and some RC bug was fixed in NMU which might mean you've lost interest in this package. (I've also added the former maintainer to CC of this bug for comments) This bug serves as a pre-removal warning. After one month, the bug will be reassigned to ftp.debian.org to actually request removal of the package. In case the package should be removed from unstable, you may reassign this bug report: Control: severity -1 normal Control: retitle -1 RM: libaosd -- RoM; Orphaned upstream, unmaintained Control: reassign -1 ftp.debian.org Control: affects -1 + src:libaosd In case you disagree with the above and think that this package remains a nice addition to Debian, please add a wontfix tag to this bug. Control: tags -1 + wontfix I would be happy if you would upload the state of the Git repository[1] which contains a polished version of the package. Most probably it makes sense to move this package to the Debian team and I'll happily help you to do so and grant you permissions on this repository and will sponsor your upload if needed. Alternatively if you think the package should remain in Debian but you have no capacity to care for it I'd recommend to orphan the package and I'd do a QA upload. This package was highlighted in the Bug of the Day[2] 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 help newcomers become familiar with a consistent Git-based workflow. Kind regards Andreas. [1] https://salsa.debian.org/salvage-team/libaosd [2] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
