Bug#981009: charybdis abandoned upstream, do not ship in bullseye
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: severity -2 normal Control: retitle -2 RM: charybdis -- RoQA; upstream dead; replacements exist * Antoine Beaupré [220813 20:07]: > On 2022-08-02 13:46:44, Chris Hofstaedtler wrote: > > * Antoine Beaupre : > >> After a somewhat long period of uncertainty, Charybdis has been > >> finally abandoned upstream. The official git repository here: > >> > >> https://github.com/charybdis-ircd/charybdis > >> > >> .. is marked as "archived by the owner [and] read-only". > > > > Is it time to file an RM bug, given that its probably going to be > > solanum? > > Sure, feel free. Thanks for the feedback. Cloning to ftpmaster for removal then. Best, Chris
Bug#981009: charybdis abandoned upstream, do not ship in bullseye
On 2022-08-02 13:46:44, Chris Hofstaedtler wrote: > * Antoine Beaupre : >> After a somewhat long period of uncertainty, Charybdis has been >> finally abandoned upstream. The official git repository here: >> >> https://github.com/charybdis-ircd/charybdis >> >> .. is marked as "archived by the owner [and] read-only". > > Is it time to file an RM bug, given that its probably going to be > solanum? Sure, feel free. -- Be yourself. Everyone else is already taken! - Oscar Wilde
Bug#981009: charybdis abandoned upstream, do not ship in bullseye
* Antoine Beaupre : > After a somewhat long period of uncertainty, Charybdis has been > finally abandoned upstream. The official git repository here: > > https://github.com/charybdis-ircd/charybdis > > .. is marked as "archived by the owner [and] read-only". Is it time to file an RM bug, given that its probably going to be solanum? Chris
Bug#981009: Charybdis abandoned upstream, do not ship in bullseye
On 2021-02-18 02:32:10, Sadie Powell wrote: > Charybdis' development was terminated due to (among other reasons) threats by > a former maintainer. It probably won't be revived. > > It's successor is probably Solanum (https://github.com/solanum-ircd/solanum) > which is a fork that is led by freenode and OFTC people some of whom were > contributors to Charybdis. It might be a good idea to package that instead > when it gets a release? I believe my co-maintainer here is working on this, actually. No WNPP bug, as far as I know, but as you say, without an upstream release it might not be worth it just yet. But yes, it's pretty much the replacement for charybdis, but do note that it's not a drop-in replacement. A. -- We will create a civilization of the Mind in Cyberspace. May it be more humane and fair than the world your governments have made before. - John Perry Barlow, 1996 A Declaration of Independence of Cyberspace
Bug#981009: Charybdis abandoned upstream, do not ship in bullseye
Charybdis' development was terminated due to (among other reasons) threats by a former maintainer. It probably won't be revived. It's successor is probably Solanum (https://github.com/solanum-ircd/solanum) which is a fork that is led by freenode and OFTC people some of whom were contributors to Charybdis. It might be a good idea to package that instead when it gets a release? ~ Sadie
Bug#981009: charybdis abandoned upstream, do not ship in bullseye
Package: charybdis Severity: serious Tags: upstream After a somewhat long period of uncertainty, Charybdis has been finally abandoned upstream. The official git repository here: https://github.com/charybdis-ircd/charybdis .. is marked as "archived by the owner [and] read-only". It is unclear what the future of the project will be, but it seems like a bad idea to rely on it in Debian, in the timeframe of a stable release. A fork, called Solanum, has been started in an amazing collaboration by the Freenode and OFTC staff, and looks much more promising. It has, unfortunately, no official release just yet, so may not be ready for Debian stable either. And besides, it is not backwards-compatible, so wouldn't offer a direct replacement. This bug should not be closed until Charybdis development resumes upstream. I would also suggest that, if no one picks it up, the package is just removed from Debian altogether, with a note pointing to solanum in the release notes. It's been a good ride though. :) a. -- System Information: Debian Release: 10.7 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-0.bpo.5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages charybdis depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii libc62.28-10 ii libltdl7 2.4.6-9 ii libmbedcrypto3 2.16.0-1 ii libmbedtls12 2.16.0-1 ii libmbedx509-02.16.0-1 ii libsqlite3-0 3.27.2-3+deb10u1 ii lsb-base 10.2019051400 ii zlib1g 1:1.2.11.dfsg-1 charybdis recommends no packages. charybdis suggests no packages.
