From: Dave Taht <dave.taht@gmail.com>
To: Brian Munyao Longwe <blongwe@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Upgrade?
Date: Sat, 3 Jun 2023 09:15:16 -0600 [thread overview]
Message-ID: <CAA93jw5vjGWZvYMNyZXcMNY-BEbACQbsVAAkxx7GTXukE-4Miw@mail.gmail.com> (raw)
In-Reply-To: <CAHSdPfbz=JyXTyZmrccjLpFrst76Sh8hry5i--sC9PN2dthotg@mail.gmail.com>
The safest thing to do is get into the chat, stash your v1.4 somewhere
as a backup, and try it during "office hours" in the USA. While we
have worked hard to make the ongoing upgrade process transparent and
simple, and a pure superset of each stage, making a jump from rc1 to
rc8 in one go... I would sleep better if I weren´t asleep while you
tried it.
On Sat, Jun 3, 2023 at 9:12 AM Brian Munyao Longwe via LibreQoS
<libreqos@lists.bufferbloat.net> wrote:
>
> Hi,
>
> I have a running v1.4 that was installed manually via the various CLI commands
>
> I’d like to upgrade to v1.4-rc8
>
> Can o just run the apt-get approach? Will it automatically upgrade? Keep config files in place?
>
> Thanks,
>
> Brian
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
prev parent reply other threads:[~2023-06-03 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 15:12 Brian Munyao Longwe
2023-06-03 15:15 ` Dave Taht [this message]
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://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5vjGWZvYMNyZXcMNY-BEbACQbsVAAkxx7GTXukE-4Miw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=blongwe@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox