Devuan logs - #667, boring messages

Message sent to [email protected], [email protected], [email protected]:

Subject: bug#667: rsync: fails to honour a tilde (~) in --log-file option
Reply-To: Dave <[email protected]>, [email protected]
Resent-From: Dave <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected], [email protected]
Resent-Date: Fri, 04 Mar 2022 22:58:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Dave <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Cc: Devuan Bug Tracking System <[email protected]>
Date: Fri, 04 Mar 2022 17:55:52 -0500
Message-Id: <[email protected]>

Package: rsync
Version: 3.1.3-6
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Normal rsync local system directory copying/archiving using the '--log-file' option

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

1. Executing "rsync -a --verbose --log-file=~/xx/mylog ~/xxxx ~/xx"
Resulted in:
 rsync: failed to open log-file ~/xx/mylog: No such file or directory (2)
 Ignoring "log file" setting.
 sending incremental file list
 xxxx/
 xxxx/20211230171244.mkv
...snip normal output...
 xxxx/xx/20220212123456-mask2.xcf

 sent 2,687,537 bytes  received 222 bytes  5,375,518.00 bytes/sec
 total size is 2,686,183  speedup is 1.00

Note the error output and 'Ignoring "log file" setting.' line when the --logfile option contained a tilde: '--log-file=~/xx/mylog'
Also note that the source and destination directories do contain the tilde (~).
No log file was produced anywhere on the local system. (The directory archive was successful.)

2. Executing "rsync -a --verbose --log-file=xx/mylog ~/xxxx ~/xx" (relative directory)
or with '--log-file=/home/myid/xx/mylog' (fully qualified path) resulted in the expected logging operation. 


If the tilde is honoured in the arguments, shouldn't it also be honoured in the options?


Thanx.

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 3 (beowulf)
Release:	3
Codename:	beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-14-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages rsync depends on:
ii  base-files           10.3+devuan3.5
ii  init-system-helpers  1.56+nmu1+devuan3
ii  libacl1              2.2.53-4
ii  libattr1             1:2.4.48-4
ii  libc6                2.28-10
ii  libpopt0             1.16-12
ii  lsb-base             10.2019051400

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:7.9p1-10+deb10u2
ii  openssh-server  1:7.9p1-10+deb10u2

-- no debconf information

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Dave <[email protected]>
Subject: bug#667: Acknowledgement (rsync: fails to honour a tilde (~) in
 --log-file option)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack 667
X-Devuan-PR-Package: rsync
Reply-To: [email protected]
Date: Fri, 04 Mar 2022 22:58:04 +0000

Thank you for filing a new bug report with Devuan.

You can follow progress on this bug here: 667: https://bugs.devuan.org/cgi/=
bugreport.cgi?bug=3D667.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
  [email protected]
(after having been given a bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
 [email protected]

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
667: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D667
Devuan Bug Tracking System
Contact [email protected] with problems

Message sent to [email protected], [email protected]:

Subject: bug#667: rsync: fails to honour a tilde (~) in --log-file option
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Sun, 06 Mar 2022 07:50:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
References: <[email protected]> <[email protected]>
Date: Sun, 6 Mar 2022 07:49:34 +0000
From: Mark Hindley <[email protected]>
To: Dave <[email protected]>, [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Dave,

On Fri, Mar 04, 2022 at 05:55:52PM -0500, Dave wrote:
> Package: rsync
> Version: 3.1.3-6
> Severity: normal
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> Normal rsync local system directory copying/archiving using the '--log-file' option
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?

I doubt this is an rsync issue. Tilde expansion on the command line is handled
by your shell before executing the expanded command line. See sh(1).

> 1. Executing "rsync -a --verbose --log-file=~/xx/mylog ~/xxxx ~/xx"

If you are quoting the command, that will prevent tilde expansion.

Mark

Message sent:

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#667: marked as done (rsync: fails to honour a tilde (~) in
 --log-file option)
Message-ID: <[email protected]>
References: <Y+tGAe0Pw/[email protected]>
 <[email protected]>
X-Devuan-PR-Message: closed 667
X-Devuan-PR-Package: rsync
Reply-To: [email protected]
Date: Tue, 14 Feb 2023 08:30:02 +0000
Content-Type: multipart/mixed; boundary="----------=_1676363402-2106-0"

This is a multi-part message in MIME format...

------------=_1676363402-2106-0
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Your message dated Tue, 14 Feb 2023 08:27:45 +0000
with message-id <Y+tGAe0Pw/[email protected]>
and subject line Re: bug#667: rsync: fails to honour a tilde (~) in --log-f=
ile option
has caused the Devuan bug report #667,
regarding rsync: fails to honour a tilde (~) in --log-file option
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 [email protected]
immediately.)


--=20
667: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D667
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1676363402-2106-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 4 Mar 2022 22:57:12 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 04 Mar 2022 22:57:12 +0000 (UTC)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.196])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.dyne.org (Postfix) with ESMTPS id D504266135F
	for <[email protected]>; Fri,  4 Mar 2022 23:56:00 +0100 (CET)
Authentication-Results: mail.dyne.org;
	dkim=pass (1024-bit key; unprotected) header.d=elscof.net [email protected] header.b="UZu6hfja";
	dkim-atps=neutral
Received: from elscof.net ([98.229.127.25]) by mrelay.perfora.net (mreueus003
 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LwsL0-1oEo2m0T28-016Nmd; Fri, 04 Mar
 2022 23:55:56 +0100
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=elscof.net;
	 s=dkim13c5; h=Message-Id:Date:Subject:Cc:To:From:Content-Transfer-Encoding:
	MIME-Version:Content-Type:Sender:Reply-To:Content-ID:Content-Description:
	Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
	In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=1HhFY2hicV6PQGJh3TqBpm5P/CmmeT6YApuHwp0BXSI=; b=UZu6hfja8x03y3PocbNg6ZX2Bf
	fou7XDy84lkRh0MI1IghdX+KImj3OESRi3slT2lLNQfBIBqACuBfYhQhSxJaVHGXoLM0UpTiISbk3
	kedDeKD/xoaZBfUdTWjBBdy6k85FelI54vMuJWS8hp+7DGDVtVDEZB38dIf+VNGtva6s=;
Received: from dhcp-68.homenet ([192.168.99.68]:34162 helo=defau-lt43.homenet) 
	by elscof.net using smtp with id 1nQGq0-0007zt-Mr ; Fri, 04 Mar 2022 17:55:53 -0500
Received: (nullmailer pid 25227 invoked by uid 1000);
	Fri, 04 Mar 2022 22:55:52 -0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Dave <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Cc: Devuan Bug Tracking System <[email protected]>
Subject: rsync: fails to honour a tilde (~) in --log-file option
X-Debbugs-Cc: [email protected]
Date: Fri, 04 Mar 2022 17:55:52 -0500
Message-Id: <[email protected]>
X-elscof-al: X495X accept +local_hosts
X-elscof: noloop r_adkim 1nQGq0-0007zt-Mr 2145 67 p587_oao
X-Provags-ID: V03:K1:m1lKlVhpr3y1fk7ZJk5O+R8ZGYhgxzHWt4nFasRB61WP00xfYuZ
 e7TvBQkNtwVc7pIWXBSmyErAoHMsnx/0Jekx0gDt/QRtTcqru6RcySLQMZ8oYzS/aRkTax9
 aPCxG3ra0IXI6ghpw/UzawCEy1ALUhrHFpYWORzEsOD2fZHeQv90mwg6c5o2P+A+kay+Mid
 tOoWwSBqJwyUw0jwmITAg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:hkIThwurDEM=:vMqA9RDC/XmUO3ZIV2wd9A
 i7uKMWrEVB0rYsH4U+6v07q2haPMeIB3J3ssVY8spo+kPjXJhUqdl9whgNuDBamEMb4KL0yCX
 1T/3h7bY1VoBj6QIqvdEv9F/YP2tvYrLYYKplSYdJGxxnI+45syHzzOZ/A8yLg3GP8E7dDHGm
 5gSCrRerlRyMe4T8vIDdrMdBoq4MhJW4GXcx6Sc1Zk1Wtn7+k+CwG4RImuvf6iEAMmqXCRgrF
 eiAr5yYeoBsV4RyA4/zLSW1ULon/b0rMpZtIGpLuiHaIVw6Ns5am7iJI1oRL0h/Qgg1gmkZKA
 C6AssJ7Vy6xuhQGljDIeQNGgXSPK2H7Vee0MtkRh4Qc4uQTu0a00coMBUXdVSKPavyF3tBoeJ
 FpA6BZiCLhp/Dw8XFLrB/ZgoJT2aXzAve09OtxMxHpCfXleH3MNVx4SCxYjvIYCCO9wvTYcBg
 95B/jx+CjjqgN7aheYzoYOYRMYwgienVnvN8qkXrPJhYIEsHBhvF3tmup4pQBt1oDTXZGR8En
 hmSDIffVDnQvHADazPOEf88lQGFUMYKbdwFZOlmeuS921kJ5deeLzoK0Zq3AipzAohPJt7ajK
 67hnlQrtmEtVeXpUr75AmpJ6+6yErZ2+2Rseafzrda9+qrny0i4Z3cYcaxoueye6DoghjO0oD
 +tqM437fBR5TXXrWCKX9Bgb9SXvidRhki8PzenkptG0LdWQD6EBzomwD+YEloJzQ1oogvjPed
 fHZUMRIH8ZlW4/dy
X-Spam-Status: No, score=-0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,URIBL_BLOCKED autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dyne.org

Package: rsync
Version: 3.1.3-6
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Normal rsync local system directory copying/archiving using the '--log-file' option

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

1. Executing "rsync -a --verbose --log-file=~/xx/mylog ~/xxxx ~/xx"
Resulted in:
 rsync: failed to open log-file ~/xx/mylog: No such file or directory (2)
 Ignoring "log file" setting.
 sending incremental file list
 xxxx/
 xxxx/20211230171244.mkv
...snip normal output...
 xxxx/xx/20220212123456-mask2.xcf

 sent 2,687,537 bytes  received 222 bytes  5,375,518.00 bytes/sec
 total size is 2,686,183  speedup is 1.00

Note the error output and 'Ignoring "log file" setting.' line when the --logfile option contained a tilde: '--log-file=~/xx/mylog'
Also note that the source and destination directories do contain the tilde (~).
No log file was produced anywhere on the local system. (The directory archive was successful.)

2. Executing "rsync -a --verbose --log-file=xx/mylog ~/xxxx ~/xx" (relative directory)
or with '--log-file=/home/myid/xx/mylog' (fully qualified path) resulted in the expected logging operation. 


If the tilde is honoured in the arguments, shouldn't it also be honoured in the options?


Thanx.

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 3 (beowulf)
Release:	3
Codename:	beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-14-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages rsync depends on:
ii  base-files           10.3+devuan3.5
ii  init-system-helpers  1.56+nmu1+devuan3
ii  libacl1              2.2.53-4
ii  libattr1             1:2.4.48-4
ii  libc6                2.28-10
ii  libpopt0             1.16-12
ii  lsb-base             10.2019051400

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:7.9p1-10+deb10u2
ii  openssh-server  1:7.9p1-10+deb10u2

-- no debconf information

------------=_1676363402-2106-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 667-done) by bugs.devuan.org; 14 Feb 2023 08:28:49 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 14 Feb 2023 08:28:49 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 1cKYCglG62MFUAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 14 Feb 2023 08:27:53 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 20B47A1; Tue, 14 Feb 2023 08:27:53 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 1844584
	for <[email protected]>; Tue, 14 Feb 2023 08:27:47 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pRqfC-00034N-4o; Tue, 14 Feb 2023 08:27:46 +0000
Received: (nullmailer pid 30289 invoked by uid 1000);
	Tue, 14 Feb 2023 08:27:46 -0000
Date: Tue, 14 Feb 2023 08:27:45 +0000
From: Mark Hindley <[email protected]>
To: Dave <[email protected]>, [email protected]
Subject: Re: bug#667: rsync: fails to honour a tilde (~) in --log-file option
Message-ID: <Y+tGAe0Pw/[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks

Closing as this is a user shell quoting issue: tilde expansion is performed by
the shell not rsync.

Mark
------------=_1676363402-2106-0--

Message sent:

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Dave <[email protected]>
Subject: bug#667 closed by Mark Hindley <[email protected]> (Re:
 bug#667: rsync: fails to honour a tilde (~) in --log-file option)
Message-ID: <[email protected]>
References: <Y+tGAe0Pw/[email protected]>
 <[email protected]>
X-Devuan-PR-Message: they-closed 667
X-Devuan-PR-Package: rsync
Reply-To: [email protected]
Date: Tue, 14 Feb 2023 08:30:05 +0000
Content-Type: multipart/mixed; boundary="----------=_1676363405-2106-1"

This is a multi-part message in MIME format...

------------=_1676363405-2106-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

This is an automatic notification regarding your bug report
which was filed against the rsync package:

#667: rsync: fails to honour a tilde (~) in --log-file option

It has been closed by Mark Hindley <[email protected]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hin=
dley.org.uk> by
replying to this email.


--=20
667: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D667
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1676363405-2106-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 667-done) by bugs.devuan.org; 14 Feb 2023 08:28:49 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 14 Feb 2023 08:28:49 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 1cKYCglG62MFUAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 14 Feb 2023 08:27:53 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 20B47A1; Tue, 14 Feb 2023 08:27:53 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 1844584
	for <[email protected]>; Tue, 14 Feb 2023 08:27:47 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pRqfC-00034N-4o; Tue, 14 Feb 2023 08:27:46 +0000
Received: (nullmailer pid 30289 invoked by uid 1000);
	Tue, 14 Feb 2023 08:27:46 -0000
Date: Tue, 14 Feb 2023 08:27:45 +0000
From: Mark Hindley <[email protected]>
To: Dave <[email protected]>, [email protected]
Subject: Re: bug#667: rsync: fails to honour a tilde (~) in --log-file option
Message-ID: <Y+tGAe0Pw/[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks

Closing as this is a user shell quoting issue: tilde expansion is performed by
the shell not rsync.

Mark
------------=_1676363405-2106-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 4 Mar 2022 22:57:12 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 04 Mar 2022 22:57:12 +0000 (UTC)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.196])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.dyne.org (Postfix) with ESMTPS id D504266135F
	for <[email protected]>; Fri,  4 Mar 2022 23:56:00 +0100 (CET)
Authentication-Results: mail.dyne.org;
	dkim=pass (1024-bit key; unprotected) header.d=elscof.net [email protected] header.b="UZu6hfja";
	dkim-atps=neutral
Received: from elscof.net ([98.229.127.25]) by mrelay.perfora.net (mreueus003
 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LwsL0-1oEo2m0T28-016Nmd; Fri, 04 Mar
 2022 23:55:56 +0100
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=elscof.net;
	 s=dkim13c5; h=Message-Id:Date:Subject:Cc:To:From:Content-Transfer-Encoding:
	MIME-Version:Content-Type:Sender:Reply-To:Content-ID:Content-Description:
	Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
	In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=1HhFY2hicV6PQGJh3TqBpm5P/CmmeT6YApuHwp0BXSI=; b=UZu6hfja8x03y3PocbNg6ZX2Bf
	fou7XDy84lkRh0MI1IghdX+KImj3OESRi3slT2lLNQfBIBqACuBfYhQhSxJaVHGXoLM0UpTiISbk3
	kedDeKD/xoaZBfUdTWjBBdy6k85FelI54vMuJWS8hp+7DGDVtVDEZB38dIf+VNGtva6s=;
Received: from dhcp-68.homenet ([192.168.99.68]:34162 helo=defau-lt43.homenet) 
	by elscof.net using smtp with id 1nQGq0-0007zt-Mr ; Fri, 04 Mar 2022 17:55:53 -0500
Received: (nullmailer pid 25227 invoked by uid 1000);
	Fri, 04 Mar 2022 22:55:52 -0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Dave <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Cc: Devuan Bug Tracking System <[email protected]>
Subject: rsync: fails to honour a tilde (~) in --log-file option
X-Debbugs-Cc: [email protected]
Date: Fri, 04 Mar 2022 17:55:52 -0500
Message-Id: <[email protected]>
X-elscof-al: X495X accept +local_hosts
X-elscof: noloop r_adkim 1nQGq0-0007zt-Mr 2145 67 p587_oao
X-Provags-ID: V03:K1:m1lKlVhpr3y1fk7ZJk5O+R8ZGYhgxzHWt4nFasRB61WP00xfYuZ
 e7TvBQkNtwVc7pIWXBSmyErAoHMsnx/0Jekx0gDt/QRtTcqru6RcySLQMZ8oYzS/aRkTax9
 aPCxG3ra0IXI6ghpw/UzawCEy1ALUhrHFpYWORzEsOD2fZHeQv90mwg6c5o2P+A+kay+Mid
 tOoWwSBqJwyUw0jwmITAg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:hkIThwurDEM=:vMqA9RDC/XmUO3ZIV2wd9A
 i7uKMWrEVB0rYsH4U+6v07q2haPMeIB3J3ssVY8spo+kPjXJhUqdl9whgNuDBamEMb4KL0yCX
 1T/3h7bY1VoBj6QIqvdEv9F/YP2tvYrLYYKplSYdJGxxnI+45syHzzOZ/A8yLg3GP8E7dDHGm
 5gSCrRerlRyMe4T8vIDdrMdBoq4MhJW4GXcx6Sc1Zk1Wtn7+k+CwG4RImuvf6iEAMmqXCRgrF
 eiAr5yYeoBsV4RyA4/zLSW1ULon/b0rMpZtIGpLuiHaIVw6Ns5am7iJI1oRL0h/Qgg1gmkZKA
 C6AssJ7Vy6xuhQGljDIeQNGgXSPK2H7Vee0MtkRh4Qc4uQTu0a00coMBUXdVSKPavyF3tBoeJ
 FpA6BZiCLhp/Dw8XFLrB/ZgoJT2aXzAve09OtxMxHpCfXleH3MNVx4SCxYjvIYCCO9wvTYcBg
 95B/jx+CjjqgN7aheYzoYOYRMYwgienVnvN8qkXrPJhYIEsHBhvF3tmup4pQBt1oDTXZGR8En
 hmSDIffVDnQvHADazPOEf88lQGFUMYKbdwFZOlmeuS921kJ5deeLzoK0Zq3AipzAohPJt7ajK
 67hnlQrtmEtVeXpUr75AmpJ6+6yErZ2+2Rseafzrda9+qrny0i4Z3cYcaxoueye6DoghjO0oD
 +tqM437fBR5TXXrWCKX9Bgb9SXvidRhki8PzenkptG0LdWQD6EBzomwD+YEloJzQ1oogvjPed
 fHZUMRIH8ZlW4/dy
X-Spam-Status: No, score=-0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,URIBL_BLOCKED autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dyne.org

Package: rsync
Version: 3.1.3-6
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Normal rsync local system directory copying/archiving using the '--log-file' option

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

1. Executing "rsync -a --verbose --log-file=~/xx/mylog ~/xxxx ~/xx"
Resulted in:
 rsync: failed to open log-file ~/xx/mylog: No such file or directory (2)
 Ignoring "log file" setting.
 sending incremental file list
 xxxx/
 xxxx/20211230171244.mkv
...snip normal output...
 xxxx/xx/20220212123456-mask2.xcf

 sent 2,687,537 bytes  received 222 bytes  5,375,518.00 bytes/sec
 total size is 2,686,183  speedup is 1.00

Note the error output and 'Ignoring "log file" setting.' line when the --logfile option contained a tilde: '--log-file=~/xx/mylog'
Also note that the source and destination directories do contain the tilde (~).
No log file was produced anywhere on the local system. (The directory archive was successful.)

2. Executing "rsync -a --verbose --log-file=xx/mylog ~/xxxx ~/xx" (relative directory)
or with '--log-file=/home/myid/xx/mylog' (fully qualified path) resulted in the expected logging operation. 


If the tilde is honoured in the arguments, shouldn't it also be honoured in the options?


Thanx.

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 3 (beowulf)
Release:	3
Codename:	beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-14-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages rsync depends on:
ii  base-files           10.3+devuan3.5
ii  init-system-helpers  1.56+nmu1+devuan3
ii  libacl1              2.2.53-4
ii  libattr1             1:2.4.48-4
ii  libc6                2.28-10
ii  libpopt0             1.16-12
ii  lsb-base             10.2019051400

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:7.9p1-10+deb10u2
ii  openssh-server  1:7.9p1-10+deb10u2

-- no debconf information

------------=_1676363405-2106-1--