Install error

[Dusan Tatomirovic]

I have attempted several installs on a Mint machine, and every time I get the following error:

dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error exit
 status 2
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)

Can anyone, please help?

Thanks.

[matthew wall]

could you provide a bit more information?

- which version of mint are you using?

- is this an upgrade of weewx, or a new installation?

- could you provide the full output from the install/upgrade, not just the last bit?

thank you!

[Werner Krenn]

Had the same problem. 

The reason for this was:

The file weewx in /etc/default was 0 bytes long.

After removing this file, the update (from 5.0.0 to 5.0.1) was installed successfully .

The update to 5.0.2 then had no problem.

Werner

[Dusan Tatomirovic]

Matthew Wall, as requested:

Mint version 21.3

Cinnamon version 6.0.4

Here is the entire response:

sudo apt install weewx

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
weewx is already the newest version (5.0.2-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up weewx (5.0.2-1) ...
Using weewx:weewx as user:group
Saving old defaults to /etc/default/weewx-20240210155912
Creating /etc/default/weewx
usage: weectl.py -v|--version
       weectl.py -h|--help
       weectl.py database --help
       weectl.py debug --help
       weectl.py device --help
       weectl.py extension --help
       weectl.py import --help
       weectl.py report --help
       weectl.py station --help
weectl.py: error: unrecognized arguments: meters,foot

dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error exit
 status 2
Errors were encountered while processing:
 weewx

[Dusan Tatomirovic]

Werner Krenn - I will look for that, thanks.

[matthew wall]

On Sunday, February 11, 2024 at 1:32:19 PM UTC-5 dusan.ta...@gmail.com wrote:

usage: weectl.py -v|--version
       weectl.py -h|--help
       weectl.py database --help
       weectl.py debug --help
       weectl.py device --help
       weectl.py extension --help
       weectl.py import --help
       weectl.py report --help
       weectl.py station --help
weectl.py: error: unrecognized arguments: meters,foot
dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error exit
 status 2
Errors were encountered while processing:
 weewx

it looks like you have a bogus value for the units in your station altitude.  apparently you entered 'meters,foot' instead of just 'meter' or 'foot'.  this is in the debconf database.

you can verify this by looking at the values in /var/cache/debconf

you can purge the values for weewx by doing this:

echo PURGE | sudo debconf-communicate weewx

then do 'apt install weewx' again, and be sure to enter the correct units for altitude.

m

[matthew wall]

On Sunday, February 11, 2024 at 1:24:13 PM UTC-5 xzei...@googlemail.com wrote:

Had the same problem. 

The reason for this was:

The file weewx in /etc/default was 0 bytes long.

After removing this file, the update (from 5.0.0 to 5.0.1) was installed successfully .

The update to 5.0.2 then had no problem.

werner, did you also have a message of "weectl.py: error: unrecognized arguments: meters,foot"?  if so, then i do not understand the problem experienced by dusan.  m

[Werner Krenn]

matthew, 

I'm not sure. But I think not. 

Is there a way to find the older installations logs to verify this?

[matthew wall]

On Monday, February 12, 2024 at 11:24:16 AM UTC-5 xzei...@googlemail.com wrote:

matthew, 

I'm not sure. But I think not. 

Is there a way to find the older installations logs to verify this?

werner,

if you are using a system based on redhat, then look in /var/log/dnf.rpm.log

if you are using a system based on debian, then look in /var/log/apt/history.log

m

[Werner Krenn]

Here the log:

Start-Date: 2024-02-08  16:08:53
Commandline: apt remove weewx
Requested-By: werner (1000)
Remove: weewx:arm64 (5.0.1-4)
End-Date: 2024-02-08  16:08:56

Start-Date: 2024-02-08  16:09:45
Commandline: apt install weewx
Requested-By: werner (1000)
Install: weewx:arm64 (5.0.1-4)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2024-02-08  16:09:48

Start-Date: 2024-02-08  16:11:33
Commandline: apt remove weewx
Requested-By: werner (1000)
Remove: weewx:arm64 (5.0.1-4)
End-Date: 2024-02-08  16:11:35

Start-Date: 2024-02-08  16:31:58
Commandline: apt install weewx
Requested-By: werner (1000)
Install: weewx:arm64 (5.0.1-4)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2024-02-08  16:32:00

Start-Date: 2024-02-09  15:29:27
Commandline: apt upgrade
Upgrade: libjavascriptcoregtk-4.1-0:arm64 (2.42.4-1~deb12u1, 2.42.5-1~deb12u1), libwebkit2gtk-4.1-0:arm64 (2.42.4-1~deb12u1, 2.42.5-1~deb12u1)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2024-02-09  15:29:33

Start-Date: 2024-02-09  16:13:08
Commandline: apt upgrade
Upgrade: weewx:arm64 (4.10.2-1, 5.0.1-4)
End-Date: 2024-02-09  16:13:26

clear

​

126 / 5.000

Übersetzungsergebnisse

Übersetzung

I tried several times and also went back to 4.10.2. Only when I deleted the "empty" weewx file did the update work.

[Werner Krenn]

Here the update starting:

Start-Date: 2024-02-08  15:56:54
Commandline: apt upgrade
Requested-By: werner (1000)
Install: linux-headers-6.1.0-rpi8-rpi-v8:arm64 (1:6.1.73-1+rpt1, automatic), python3-ephem:arm64 (4.1.4-2+b1, automatic), linux-headers-6.1.0-rpi8-rpi-2712:arm64 (1:6.1.73-1+rpt1, automatic), linux-headers-6.1.0-rpi8-common-rpi:arm64 (1:6.1.73-1+rpt1, automatic), linux-image-6.1.0-rpi8-rpi-2712:arm64 (1:6.1.73-1+rpt1, automatic), linux-image-6.1.0-rpi8-rpi-v8:arm64 (1:6.1.73-1+rpt1, automatic)
Upgrade: libglx-mesa0:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), firefox-l10n-de:arm64 (121.0-1+rpt4, 122.0-1+rpt4), rpi-eeprom:arm64 (21.0-1, 21.2-1), weewx:arm64 (4.10.2-1, 5.0.1-4), xserver-xorg-core:arm64 (2:21.1.7-3+rpt2+deb12u4, 2:21.1.7-3+rpt2+deb12u5), libzbar0:arm64 (0.23.92-7, 0.23.92-7+deb12u1), openjdk-17-jre:arm64 (17.0.9+9-1~deb12u1, 17.0.10+7-1~deb12u1), libgbm1:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), linux-headers-rpi-v8:arm64 (1:6.1.63-1+rpt1, 1:6.1.73-1+rpt1), libfm-gtk-data:arm64 (1.3.2-1+rpt11, 1.3.2-1+rpt12), wf-panel-pi:arm64 (0.56, 0.59), linux-headers-rpi-2712:arm64 (1:6.1.63-1+rpt1, 1:6.1.73-1+rpt1), linux-image-rpi-2712:arm64 (1:6.1.63-1+rpt1, 1:6.1.73-1+rpt1), linux-kbuild-6.1:arm64 (1:6.1.63-1+rpt1, 1:6.1.73-1+rpt1), libgl1-mesa-dev:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), libgl1-mesa-dri:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), wayvnc:arm64 (0.8.0-rc0-1, 0.8.0-rc0-2), firefox:arm64 (121.0-1+rpt4, 122.0-1+rpt4), libc6:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), locales:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libgstreamer-plugins-bad1.0-0:arm64 (1.22.0-4+deb12u4, 1.22.0-4+deb12u5), xserver-common:arm64 (2:21.1.7-3+rpt2+deb12u4, 2:21.1.7-3+rpt2+deb12u5), raspi-firmware:arm64 (1:1.20231024+ds-1+rpt2, 1:1.20231024+ds-1+rpt5), libfm-gtk4:arm64 (1.3.2-1+rpt11, 1.3.2-1+rpt12), rpi-firefox-mods:arm64 (20231002, 20240110), linux-image-rpi-v8:arm64 (1:6.1.63-1+rpt1, 1:6.1.73-1+rpt1), libglapi-mesa:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), libc-dev-bin:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libc-l10n:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libfm-extra4:arm64 (1.3.2-1+rpt11, 1.3.2-1+rpt12), libcamera-apps:arm64 (1.4.1-1, 1.4.2-1), libc-bin:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libc-devtools:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libc6-dbg:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libc6-dev:arm64 (2.36-9+rpt2+deb12u3, 2.36-9+rpt2+deb12u4), libfm-modules:arm64 (1.3.2-1+rpt11, 1.3.2-1+rpt12), gstreamer1.0-plugins-bad:arm64 (1.22.0-4+deb12u4, 1.22.0-4+deb12u5), libegl-mesa0:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), libfm4:arm64 (1.3.2-1+rpt11, 1.3.2-1+rpt12), mesa-vdpau-drivers:arm64 (23.2.1-1~bpo12+rpt2, 23.2.1-1~bpo12+rpt3), rpicam-apps:arm64 (1.4.1-1, 1.4.2-1), openjdk-17-jre-headless:arm64 (17.0.9+9-1~deb12u1, 17.0.10+7-1~deb12u1), raspberrypi-sys-mods:arm64 (20231208, 20240123), libfm-data:arm64 (1.3.2-1+rpt11, 1.3.2-1+rpt12), linux-libc-dev:arm64 (1:6.1.63-1+rpt1, 1:6.1.73-1+rpt1)

Error: Sub-process /usr/bin/dpkg returned an error code (1)

End-Date: 2024-02-08  15:58:56

Start-Date: 2024-02-08  15:59:51
Commandline: apt upgrade
Requested-By: werner (1000)

Error: Sub-process /usr/bin/dpkg returned an error code (1)

End-Date: 2024-02-08  15:59:52

[Dusan Tatomirovic]

Matthew,

It worked! Thank you so much, and thanks to Werner as well.

Follow-up question: I am looking into getting one of those Misol stations that have RS-485 connections. I prefer hardwired solutions instead of wifi. Would you recommend that, or should I look for something else?

My ideal solution would be a POE station, but I wasn't able to find any that are affordable. A Czech company apparently has one - but I haven't seen any reviews.

Please advise.