Your message dated Mon, 2 Jan 2023 01:23:39 +0800
with message-id 
<cafyclw_opo4boehmbclzpr6otccmm6k34kn8qbw216y5lba...@mail.gmail.com>
and subject line Re: Bug#986084: etcd-server: broken symlink: 
/usr/share/doc/etcd-server/README.md -> docs.md
has caused the Debian Bug report #986084,
regarding etcd-server: broken symlink: /usr/share/doc/etcd-server/README.md -> 
docs.md
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.)


-- 
986084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: etcd-server
Version: 3.3.25+dfsg-6
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m22.7s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/etcd-server/README.md -> docs.md (etcd-server)


cheers,

Andreas

Attachment: etcd-server_3.3.25+dfsg-6+b2.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: etcd
Version: 3.4.23-1

On Mon, Mar 29, 2021 at 7:45 PM Andreas Beckmann <a...@debian.org> wrote:
>
> Package: etcd-server
> Version: 3.3.25+dfsg-6
> Severity: normal
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
>
> From the attached log (scroll to the bottom...):
>
> 0m22.7s ERROR: FAIL: Broken symlinks:
>   /usr/share/doc/etcd-server/README.md -> docs.md (etcd-server)
>

Fixed in 3.4, forget to close in d/changelog.

-- 
Shengjing Zhu

--- End Message ---

Reply via email to