Your message dated Fri, 12 Apr 2024 06:35:48 +0000
with message-id <e1rvavo-00delm...@fasolo.debian.org>
and subject line Bug#1068834: Removed package(s) from unstable
has caused the Debian Bug report #943405,
regarding unsuitable for release: no upstream patch releases
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 ow...@bugs.debian.org
immediately.)
--
943405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sopel
Version: 6.6.2-1
Severity: serious
Tags: upstream
In bug #927481, I was bit by a bug that wasn't solved upstream in a
simple patch release. It would force me to maintain a fork of the
project for every supported debian release to fix any bug, because
upstream doesn't follow the semver.org convention of using "patch"
releases for critical bugfixes and security issues.
Instead, Sopel upstream releases x.y.z release with major changes in
"z" patch releases. An example from #927481 is:
> For example right now there is 6.6.4 release that fixes this bug:
>
> https://sopel.chat/changelog/6.6.4/
>
> ... but it also includes changes like:
>
> * Cleaned up code in instagram and unicode modules
> * Core modules now use bot.channels instead of deprecated bot.privileges
>
> Which couldn't be eligible for a stable update.
So I even though the original bug was fixed in the latest upload, I
don't think sopel should be shipped with bullseye until this situation
changes, especially since the package is orphaned.
Next step in this bug would be to open the discussion with upstream
about this, maybe this is something they could work on.
-- System Information:
Debian Release: 10.1
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sopel depends on:
ii adduser 3.118
ii lsb-base 10.2019051400
ii python3 3.7.3-1
ii python3-dnspython 1.16.0-1
pn python3-geoip2 <none>
pn python3-praw <none>
ii python3-requests 2.21.0-1
ii python3-tz 2019.1-1
ii python3-xmltodict 0.11.0-2
Versions of packages sopel recommends:
ii ipython3 5.8.0-1
ii python3-enchant 2.0.0-1
ii python3-feedparser 5.2.1-1
ii python3-lxml 4.3.2-1
sopel suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 6.6.9-2.2+rm
Dear submitter,
as the package sopel 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/1068834
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
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
