[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#394946: marked as done (unison: merge2 option rejected)



Your message dated Thu, 29 Oct 2015 14:40:40 +0100
with message-id <563221D8.20607@debian.org>
and subject line Re: Bug#394946: unison: merge2 option rejected
has caused the Debian Bug report #394946,
regarding unison: merge2 option rejected
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 owner@bugs.debian.org
immediately.)


-- 
394946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394946
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: unison
Version: 2.13.16-5
Severity: normal

If I use a "merge2" option in a profile, it is rejected as an invalid
option by the current version of unison-gtk, but I can't see anything
in the documentation telling me that this option has been removed, and
strings tells me that there is still a lot of text about it in the
binary itself.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages unison depends on:
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries

Versions of packages unison recommends:
ii  openssh-client [ssh-client]   1:4.3p2-5  Secure shell client, an rlogin/rsh

-- no debconf information


--- End Message ---
--- Begin Message ---
Le 25/10/2015 07:35, Mark J. Nelson a écrit :
> Triaging an old bug:
> 
> I believe the maintainers can safely close this bug. The 'merge2' option
> was removed almost a decade ago, and the documentation has long since
> been updated to remove any lingering confusion.

Thank you for this triaging! Closing this bug...

-- 
Stéphane

--- End Message ---

Reply to: