From: Steinar Bang <sb@dod.no>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50988@debbugs.gnu.org
Subject: bug#50988: 26.3; gnus-cloud gets wrong chunk byte count writing sync from windows
Date: Tue, 13 Sep 2022 19:28:58 +0200 [thread overview]
Message-ID: <87zgf3ji91.fsf@dod.no> (raw)
In-Reply-To: <87wna8ao08.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 12 Sep 2022 12:24:55 +0200")
>>>>> Lars Ingebrigtsen <larsi@gnus.org>:
> sb@dod.no writes:
>> The first chunk has the following header:
>> (:type :file :file-name "~/.gnus.el" :timestamp
>> "2021-09-19T15:04:33+0200" :length 16241)
>>
>> The byte count here is 16241, but it should have been 15754.
> I'm not able to reproduce this exactly, but I think I've identified a
> possible problem in this area now. Do you still see these issues on
> the current "master" branch?
No, sorry!
I removed gnus-cloud sync of .gnus.el and .authinfo.gpg on "Wed Oct 6 20:50:09 2021 +0200"
modified .emacs
@@ -783,6 +783,7 @@ to be something different.")
'(gnus-cloud-interactive nil)
'(gnus-cloud-method "nnimap:privat")
'(gnus-cloud-storage-method nil)
+ '(gnus-cloud-synced-files '((:directory "~/News" :match ".*.SCORE\\'")))
'(gnus-picon-style 'right)
'(gnus-treat-fill-long-lines nil)
'(gnus-treat-newsgroups-picon nil)
(also, I'm now using a debian GNU/linux laptop, so I don't see any
CRLF/LF related issues (which I still think this was, even if Eli
doesn't). I.e. not easy to reproduce)
next prev parent reply other threads:[~2022-09-13 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 8:34 bug#50988: 26.3; gnus-cloud gets wrong chunk byte count writing sync from windows sb
2021-10-03 9:15 ` Eli Zaretskii
2021-10-03 10:32 ` Steinar Bang
2021-10-03 11:04 ` Eli Zaretskii
2022-09-12 10:24 ` Lars Ingebrigtsen
2022-09-13 17:28 ` Steinar Bang [this message]
2022-09-14 12:34 ` Lars Ingebrigtsen
2022-09-14 15:04 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgf3ji91.fsf@dod.no \
--to=sb@dod.no \
--cc=50988@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).