Your message dated Sun, 13 Oct 2024 10:01:11 +0000 with message-id <[email protected]> and subject line Bug#1082605: Removed package(s) from unstable has caused the Debian Bug report #951333, regarding telegram-purple: Logs error "Query Failed - 71: RPC_CALL_FAIL 400: CHANNEL_INVALID", lost posting functionality 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.) -- 951333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951333 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: telegram-purple Version: 1.4.1-1+b1 Severity: important After several months of using telegram-purple (thanks for it!) via bitlbee, I started receiving the following message in thelog, with frequencies that go from every ten seconds to every ten minutes: 10:33:27 @root | purple - Error: Query Failed - 71: RPC_CALL_FAIL 400: CHANNEL_INVALID 10:38:52 @root | purple - Error: Query Failed - 71: RPC_CALL_FAIL 400: CHANNEL_INVALID 10:46:48 @root | purple - Error: Query Failed - 71: RPC_CALL_FAIL 400: CHANNEL_INVALID 10:50:53 @root | purple - Error: Query Failed - 71: RPC_CALL_FAIL 400: CHANNEL_INVALID I am not sure on the exact impact this has, bu I can at least say: - One particular channel I subscribe to (https://t.me/sysarmymx) no longer marks messages as read - I receive the messages, but cannot post to the group (my messages are silently dropped) - A couple of days ago, _all_ of my posting and personal messaging ability failed (could only read what was being posted) I have tried unsubscribing and subscribing again, to no avail. Thank you very much, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-purple depends on: ii libc6 2.29-3 ii libgcrypt20 1.8.5-3 ii libglib2.0-0 2.62.2-3 ii libpng16-16 1.6.37-1 ii libpurple0 2.13.0-2.2+b1 ii libwebp6 0.6.1-2+b1 ii zlib1g 1:1.2.11.dfsg-1+b1 telegram-purple recommends no packages. telegram-purple suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.4.3-3+rm Dear submitter, as the package telegram-purple has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1082605 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note 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. 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. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
