Am 30.03.21 um 09:04 schrieb dk8kk:
> Package: fetchmailconf
> Version: 6.4.0~beta4-3+deb10u1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
>
> Dear Maintainer,
>
> apt-get update/apt-get upgrade suggests these package for upgrade:
> - fetchmail (6.4.0~beta4-3+deb10u1)
> - fetchmailconf (6.4.0~beta4-3+deb10u1)
>
> Installation/Configurations fails afterwards because of the
> following error:
> ------------------------------------------------------------------------
> fetchmail (6.4.0~beta4-3+deb10u1) wird eingerichtet ...
> Job for fetchmail.service failed because the control process exited with
> error code.
> See "systemctl status fetchmail.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript fetchmail, action "restart" failed.
> ● fetchmail.service - LSB: init-Script for system wide fetchmail daemon
> Loaded: loaded (/etc/init.d/fetchmail; generated)
> Active: failed (Result: exit-code) since Tue 2021-03-30 08:59:33 CEST; 4ms
> ago
> Docs: man:systemd-sysv-generator(8)
> Process: 3556 ExecStart=/etc/init.d/fetchmail start (code=exited,
> status=1/FAILURE)
As external/upstream maintainer I cannot comment on this part.
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: Starting LSB: init-Script for
> system wide fetchmail daemon...
> Mär 30 08:59:33 regulus.fritz.box fetchmail[3556]: Starting mail retriever
> agent: fetchmailfetchmail: es wurden keine Mailserver spezifiziert.
This means "no mail servers configured", i. e. virgin installation.
> Mär 30 08:59:33 regulus.fritz.box fetchmail[3556]: failed!
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: fetchmail.service: Control
> process exited, code=exited, status=1/FAILURE
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: fetchmail.service: Failed with
> result 'exit-code'.
> Mär 30 08:59:33 regulus.fritz.box systemd[1]: Failed to start LSB:
> init-Script for system wide fetchmail daemon.
> dpkg: Fehler beim Bearbeiten des Paketes fetchmail (--configure):
> »installiertes fetchmail-Skript des Paketes post-installation«-Unterprozess
> gab den Fehlerwert 1 zurück
> dpkg: Abhängigkeitsprobleme verhindern Konfiguration von fetchmailconf:
> fetchmailconf hängt ab von fetchmail (>= 6.4.0~beta4-3+deb10u1); aber:
> Paket fetchmail ist noch nicht konfiguriert.
This means fetchmailconf can't be configured while fetchmail is pending
configuration.
> dpkg: Fehler beim Bearbeiten des Paketes fetchmailconf (--configure):
> Abhängigkeitsprobleme - verbleibt unkonfiguriert
> Fehler traten auf beim Bearbeiten von:
> fetchmail
> fetchmailconf
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> ------------------------------------------------------------------------
>
> Trying to configure fetchmailconf manually fails too:
>
> root@regulus:/etc# fetchmailconf --configure
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/fetchmailconf.py", line 2081, in
> <module>
> "version"])
> File "/usr/lib/python2.7/getopt.py", line 88, in getopt
> opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
> File "/usr/lib/python2.7/getopt.py", line 152, in do_longs
> has_arg, opt = long_has_args(opt, longopts)
> File "/usr/lib/python2.7/getopt.py", line 169, in long_has_args
> raise GetoptError('option --%s not recognized' % opt, opt)
> getopt.GetoptError: option --configure not recognized
To the submitter: That is expected and cannot possibly work.
If you were to manually try to configure fetchmailconf, you'd have to
run: dpkg --configure fetchmailconf.
fetchmailconf is a Python-Tk-(Tkinter)-based graphical configuration
utility.
