From: "André A. Gomes" <andremegafone@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 57543@debbugs.gnu.org
Subject: bug#57543: emacs-telega is broken
Date: Fri, 09 Sep 2022 18:36:38 +0300 [thread overview]
Message-ID: <87edwksgop.fsf@gmail.com> (raw)
In-Reply-To: <87zgf861wq.fsf@xelera.eu> (Giovanni Biscuolo's message of "Fri, 09 Sep 2022 16:46:45 +0200")
Giovanni Biscuolo <g@xelera.eu> writes:
> AFAIU when I ran telega with the new tdlib verson, the database got
> upgraded and the new database version is not compatible with the old
> tdlib library; there is an old (Mar 2021) telega.el issue that helped me
> understand this one: https://github.com/zevlg/telega.el/issues/276
>
> If I'm not getting it wrong, reverting the "offending" patch and
> restoring tdlib to 1.8.0 is not enough for people like us who already
> upgraded tdlib (and started telega), we need to restore from backups.
Hi Giovanni,
Great investigation, thanks.
I'm a bit confused when you say "restore from backups". Are you saying
that, for those who have already upgraded tdlib, it's not sufficient to
simply switching to an older generation?
--
André A. Gomes
"You cannot even find the ruins..."
next prev parent reply other threads:[~2022-09-09 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 11:15 bug#57543: emacs-telega is broken André A. Gomes
2022-09-08 17:57 ` Giovanni Biscuolo
2022-09-09 9:00 ` André A. Gomes
2022-09-09 14:46 ` Giovanni Biscuolo
2022-09-09 15:36 ` André A. Gomes [this message]
2022-09-09 17:48 ` Giovanni Biscuolo
2022-09-10 20:11 ` André A. Gomes
2022-09-13 13:42 ` Giovanni Biscuolo
2022-09-13 20:10 ` André A. Gomes
2022-09-14 7:09 ` Giovanni Biscuolo
2022-09-14 8:54 ` Ludovic Courtès
2022-09-22 12:44 ` Giovanni Biscuolo
2022-09-09 14:58 ` Zhu Zihao
2022-09-09 19:00 ` Giovanni Biscuolo
2022-09-10 11:02 ` Giovanni Biscuolo
2023-11-02 9:44 ` bug#57543: Update André A. Gomes
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edwksgop.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=57543@debbugs.gnu.org \
--cc=g@xelera.eu \
--cc=ludo@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.