#EVCC update fails and no repros are added to debian

34 messages · Page 1 of 1 (latest)

proper folio
#

Hi after quite some time I wanted to update my evcc container. Running the script within the container, it pulls the usual debian repros and tells me there are 35 updateable packages but that evcc is on the latest version (which it isn't). Nothing is installed or updated after that. On further inspections, I can't find an entry in apt sources for evcc (not in sources.list and not in sources.d). Albeit the script seems to do exactly this.

Did I maybe wait to long and the script changed so significantly, that an update doesn't work anymore? Debian is still on bookworm. EVCC version is 0.209, kernel @6.17.2-2-pve

errant citrus
#

what version of pve are you on ?

proper folio
#

9.1.2

errant citrus
#

ok run apt update && apt upgrade

zinc herald
#

Whats inside sources.d.list?

proper folio
#

nothing its empty. In sources.list I still have repros of bookworm. Right now I'm trying to update to trixie manually and see if the script catches up from there. Is a distro upgrade part of the update process for helper-scripts?

proper folio
errant citrus
#

and they have all now been updated yes?

proper folio
#

yes but this did not include evcc

zinc herald
#

If you dont have Sources, then its Strange that you have evcc inside

proper folio
#

well it came from the inital install I guess...

errant citrus
#

so now what does it say if u run update

#

past the full output here

zinc herald
#
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/core.func)
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/tools.func)
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/error_handler.func)

setup_deb822_repo \
  "evcc-stable" \
  "https://dl.evcc.io/public/evcc/stable/gpg.EAD5D0E07B0EC0FD.key" \
  "https://dl.evcc.io/public/evcc/stable/deb/debian/" \
  "$(get_os_info codename)" \
  "main"
 apt update
#

Without the first bash

errant citrus
#

i have feeling it will fail but im just interested

proper folio
#
Hit:1 https://deb.debian.org/debian trixie InRelease
Hit:2 https://deb.debian.org/debian trixie-updates InRelease
Hit:3 https://deb.debian.org/debian-security trixie-security InRelease
All packages are up to date.    
evcc is already the newest version (0.209.7).
The following package was automatically installed and is no longer required:
  libassuan0
Use 'apt autoremove' to remove it.

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
  ✔️   Updated successfully!
#

That is after I updated to trixie manually by adding the trixie repros

errant citrus
#

that what i thought, yer do the command Mick posted

proper folio
#

ok running the script above I get an entry in /etc/apt/sources.d for evcc. The script itself as well as the running update I get:

update
⏳ Updating evcc LXC
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

#

Maybe there was an update now, but it seems to that it broke somehow the output

errant citrus
#

run apt upgrade

proper folio
#

all apt commands end with this odd warnings and no output

#

there is no apt-upgrade did you mean apt upgrade?

errant citrus
#

yer sry typo

#

what does it say?

proper folio
#

that was fun.... executing the script I was still somehow within the script execution. Poor debian tried to tell me with the warning. multiple exit and a relogin later, now I can run update and it seems it has updated evcc as well

#

ok evcc runs it needs multiple config updates but that is evcc stuff and not related here. Just to learn a little more, if there is a underlying OS update like bookworm (12) to trixie (13) will that be covered usually with the update scripts as well?

errant citrus
#

there ya go 🙂 Mick is rarely wrong that why i was confused but i think what originally happen was when you manually tried to update debian it somehow wiped the source file so broke the ypdate script 🙂 moral of story make sure to do your updates more regularly.

proper folio
#

nah the source file was missing from the beginning. The update however is tailored to trixie and the new /etc/apt/source.d/ style. Not sure if the sources in bookworm were simply added to sources.list. Maybe that broke it somehow.

#

"moral of story make sure to do your updates more regularly" .... but .... never the change a running system 😉

#

@zinc herald @errant citrus That was fun, thanks a lot for the quick help, I have 99% SoC in my EV to fix the EVCC config, before my wife gets mad at me.... wish me luck.

errant citrus
#

it was all MIck i was just curious tbfh 🙂