Please consider merging this PR and re-indexing the pirogue part of the repository as usual.
Here's the pirogue-ap changelog:
pirogue-ap (1.1.2) bookworm; urgency=medium
* Remove dhcpcd5 from Depends: it's a transitional package for dhcpcd
in the first place, can trigger conflicts with raspberrypi-sys-mods
in Raspberry OS (which some users attempted to use until we added
experimental support for Raspberry Pi 5), and is likely responsible
for some reported connection losses, possibly by racing against
dhclient.
* Stop shipping dhcpcd.conf accordingly.
* Stop tweaking dhcpcd.conf during postinst accordingly.
* Adjust /etc/network/interfaces.d/wlan0:
- If upgrading, from a version strictly before 1.1.2, archive it
under /root, then stop, disable, mask dhcpcd. Make sure wlan0 is
still configured with 10.8.0.1/24 afterwards.
- In any case, write the static configuration: IPv4 = 10.8.0.1/24.
-- Cyril Brulebois <cyril@debamax.com> Sun, 28 Jul 2024 18:36:24 +0200
Upgrade from the PTS 2.1.0 release
It's been developed and tested during the last live session. Since then, just one more thing was changed (added):
Make sure wlan0 is still configured with 10.8.0.1/24 [after upgrading and migrating away from dhcpcd].
If you want to check before merging, you can point your PiRogue to the following repository:
deb https://pirogue.apt.debamax.com/debian-12/pirogue ./
deb https://pirogue.apt.debamax.com/debian-12/pirogue-3rd-party ./
The following packages were automatically installed and are no longer required:
dhcpcd dhcpcd5
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
pirogue-ap
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
As discussed, we don't force a removal/purge to stay on the safe side.
Right after dist-upgrade, the PiRogue should be functional still (no reboot required).
Fresh install
This release makes the state after a fresh install, before the reboot, a little worse. But users were already getting “No internet connection” anyway. Details can be found in https://github.com/PiRogueToolSuite/deb-packages/issues/31.
Hi,
Please consider merging this PR and re-indexing the
piroguepart of the repository as usual.Here's the
pirogue-apchangelog:Upgrade from the PTS 2.1.0 release
It's been developed and tested during the last live session. Since then, just one more thing was changed (added):
If you want to check before merging, you can point your PiRogue to the following repository:
The signing key is available here: https://debamax.com/data/cyril@debamax.com.asc
The upgrade looks like this:
As discussed, we don't force a removal/purge to stay on the safe side.
Right after
dist-upgrade, the PiRogue should be functional still (no reboot required).Fresh install
This release makes the state after a fresh install, before the reboot, a little worse. But users were already getting “No internet connection” anyway. Details can be found in https://github.com/PiRogueToolSuite/deb-packages/issues/31.