Package: rssguard
Version: 4.0.4+dfsg-1.1build2
Severity: wishlist
X-Debbugs-Cc: al...@organicrobot.com

Dear Maintainer,

There are many newer versions of rssguard available (latest is 4.7.4 as of this 
moment). The current version is around 3 years old. I've noticed that the fork 
used for Debian (https://github.com/norbusan/rssguard-debian) has been archived.

Does this mean that the package can be considered dead? If so, would it be ok 
for me to try to get newer version upstreamed?  (I am reporting from Ubuntu. 
Would this be an impediment?)

Cheers,
alejandro

-- System Information:
Debian Release: trixie/sid
  APT prefers noble-updates
  APT policy: (500, 'noble-updates'), (500, 'noble-security'), (500, 'noble'), 
(100, 'noble-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-50-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rssguard depends on:
ii  libc6                    2.39-0ubuntu8.3
ii  libgcc-s1                14.2.0-4ubuntu2~24.04
ii  libqt5core5t64           5.15.13+dfsg-1ubuntu1
ii  libqt5dbus5t64           5.15.13+dfsg-1ubuntu1
ii  libqt5gui5t64            5.15.13+dfsg-1ubuntu1
ii  libqt5multimedia5        5.15.13-1
ii  libqt5network5t64        5.15.13+dfsg-1ubuntu1
ii  libqt5qml5               5.15.13+dfsg-1
ii  libqt5sql5-sqlite        5.15.13+dfsg-1ubuntu1
ii  libqt5sql5t64            5.15.13+dfsg-1ubuntu1
ii  libqt5webenginecore5     5.15.16+dfsg-3
ii  libqt5webenginewidgets5  5.15.16+dfsg-3
ii  libqt5widgets5t64        5.15.13+dfsg-1ubuntu1
ii  libqt5xml5t64            5.15.13+dfsg-1ubuntu1
ii  libstdc++6               14.2.0-4ubuntu2~24.04

rssguard recommends no packages.

rssguard suggests no packages.

-- no debconf information

Reply via email to