Your message dated Sat, 11 Apr 2020 12:22:58 +0200
with message-id <402ff3f13023dc356f3a066ee09b9ddca42aee65.ca...@debian.org>
and subject line Re: Bug#925277: freecad: there's no manpage entry
has caused the Debian Bug report #925277,
regarding freecad: there's no manpage entry
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.)
--
925277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Version: 0.18~pre1+dfsg1-5
Severity: normal
Dear Maintainer,
There is no manpage entry after installing freecad but there is one here
*debian/freecad.1*, which needs to be updated. But I suppose having an
old manpage which misses some options is better than having no manpage.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
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 freecad depends on:
ii freecad-python3 0.18~pre1+dfsg1-5
Versions of packages freecad recommends:
ii calculix-ccx 2.11-1+b3
ii graphviz 2.40.1-5+b2
Versions of packages freecad suggests:
pn freecad-doc <none>
pn povray <none>
pn python-collada <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 freecad/0.18+dfsg1-1
> I can confirm this issue. It looks like the freecad-python2 package
> needs to be installed for the manpage to be available, so I'll have to
> correct that.
Fixed in 0.18+dfsg1-1 (but not mentioned in the changelogs)
--- End Message ---
