Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Beta v6.34.2 #3981

Merged
merged 21 commits into from
Dec 18, 2020
Merged

Beta v6.34.2 #3981

merged 21 commits into from
Dec 18, 2020

Conversation

MichaIng
Copy link
Owner

@MichaIng MichaIng commented Dec 17, 2020 •
edited
Loading

Beta v6.34.2

Date of merge: 2020-12-17

Changes since v6.34.1

  • DietPi-CloudShell | Several enhancements have been applied. The autostart option now runs the script in foreground, which means that it can always be terminated via "CTRL+C" from an attached keyboard. The original sized font is now restored on exit and terminal settings reset. Also the menu has gone through some fine tuning, showing current settings hopefully a bid more outstanding.

Removed Software Packages since v6.34.1

  • DietPi-Software | DietPi-CloudShell: The install option has been removed, but DietPi-CloudShell stays available of course. The install did nothing else than creating the service file and enabling the autostart option, but the script was always available and did work well without having the software option installed. The service is now as well available statically, the script can always be started from console via "dietpi-cloudshell" shortcut alias now and is shown in dietpi-launcher. Also non-root users can run now run it via "dietpi-cloudshell 1" (with intro) or "dietpi-cloudshell 2" (no intro), only changing the settings via menu (no command argument) requires root permissions.

MichaIng and others added 18 commits December 12, 2020 17:27
@MichaIng
v6.34
1ef4068 
+ DietPi-CloudShell | Tor Monitor: Store and kill the explicit PID we created within this DietPi-CloudShell instance instead of all "nyx" processes.
+ DietPi-CloudShell | Tor Monitor: Pre-create config file within Run_Cloudshell function. It could have been removed meanwhile nyx installed manually while not actively selected in scene selector but then enabled by default.
@MichaIng
v6.34
2e5bab4 
+ DietPi-Patch | Beta: Remove falsely created nyx config directory where a file should have been placed
@MichaIng
v6.34
99ece78 
+ DietPi-CloudShell | Assure that nyx Tor monitor is killed as well when the screen enters blank time
@MichaIng
v6.34
0a9f5d9 
+ DietPi-Software | No-IP: Error handle binary and config install commands, for transparency and to detect errors in the first place
@MichaIng
v6.34 (#3974)
83d59b1 
+ DietPi-CloudShell | Store current font and restore on exit, together with terminal settings
+ DietPi-CloudShell | Minor menu layout enhancements
+ DietPi-CloudShell | Assure that we always identify the STDOUT terminal instead of STDIN terminal (output of "tty" command), as STDIN is irrelevant and not available from e.g. systemd service
+ DietPi-CloudShell | Remove unnecessary redirect of setterm command to /dev/tty1. This does neither apply the settings on /dev/tty1 (when running from different tty), not is it what we want.
+ DietPi-CloudShell | Kill nyx (Tor Relay monitor) only when loop reaches another "enabled" scene. Currently it is killed as well if the next scene is not enabled, which at best break smooth execution when Tor Relay is the only enabled scene.
+ DietPi-Login | Check for STDOUT terminal instead of STDIN terminal when deciding whether to run autostart programs or not
+ DietPi-Login | DietPi-CloudShell: Start script directly instead of service. This allows killing it from that console while the service runs without STDIN in background and can only killed by stopping the service, which is hard to while CloudShell is producing output. All terminal settings are now applied from within the script so that the service has no other purpose than starting CloudShell from a different terminal or SSH on /dev/tty1. In this case we know that such a second terminal exist from where the service can be stopped as well.
+ DietPi-CloudShell | Add service statically, as there is not much point in having an install option that does nothing else than placing a service for a script that can run well standalone
+ DietPi-Software | DietPi-CloudShell: Remove software option as the script runs fine in standalone and is called like this by the autostart option as well. The service is now available statically and has a use only to start CloudShell from a different terminal/SSH on tty1.
+ DietPi-CloudShell | Make alias available statically, as the service now is
+ DietPi-CloudShell | Allow final execution as non-root user, only changing settings via menu requires root
+ DietPi-Launcher | Since DietPi-CloudShell install option has been removed and it is statically available, always show it in launcher
+ DietPi-Patch | Remove DietPi-CloudShell install flag
+ DietPi-Survey_report | Remove DietPi-CloudShell install flag with DietPi v6.34
@MichaIng
v6.34
25bbd93 
+ DietPi-Start_Kodi | Satisfy shellcheck
@MichaIng
v6.34
594a345 
+ DietPi-Set_software | Satisfy shellcheck
@MichaIng
v6.34
33fbd34 
+ DietPi-Software | Verify and update all GitHub API fallback URLs and the few cases where a fixed version is downloaded
@MichaIng
v6.34
8f24a9a 
+ DietPi-Software | HAProxy: Minor: Remove commented logging settings, logging to systemd-journald (journalctl) is what we want
@MichaIng
v6.34
75a578c 
+ DietPi-Banner | Align APT update info colour and style with DietPi update info
+ DietPi-Banner | Remove image update info, since we do not use it anymore: A migration or support branch will be automatically applied instead.
@ravenclaw900
v6.34 (#3969)
3ba37e8 
+ DietPi-CloudShell | Run nyx on a separate TTY
@StephanStS
v6.34 (#3980)
f6058c3 
+ README | Additional link to FeatHub may be found easier instead of clicking on one of the software package links
+ README | Add hint to open a related GitHub issue when creating a FeatHub request
@MichaIng
v6.34
4bcf7a6 
+ DietPi-Update | Do not check for APT updates, if a DietPi update is available. DietPi-Banner shows the latter, if present, so the APT update flag file is not used. DietPi-Update includes APT upgrades anyway. This resolves an issue where on early login, an available DietPi update could be shown in banner already while dietpi-update is still running for the APT update checks. Executing dietpi-update then fails due to concurrency: #3963 (comment)
@MichaIng
v6.34
54b6dc4 
+ DietPi-Cron_daily | "dietpi-update 2" won't check for APT updates anymore, if a DietPi update is available. To assure that daily APT auto-upgrades still work, in this case those need to be checked separately.
@MichaIng
v6.34
cfc7a38 
+ META | myip.php has been moved to the DietPi-Website repository
@MichaIng
v6.34
bd0549e 
+ META | Remove another obsolete image from this repository
@MichaIng
v6.34
33c87ca 
+ DietPi-Banner | Remove currently sadly obsolete Patreon Legend line + tiny code and comment changes
@MichaIng
v6.34 (#3979)
3629d91 
+ DietPi-Software | OctoPrint: Migrate to user-level Python instance
+ DietPi-Software | Remove DietPi-CloudShell related code
+ DietPi-Patch | OctoPrint: Add whiptail prompt to explain the required OctoPrint reinstall and give a hint that plugins usually need to be reinstalled.
@MichaIng MichaIng added the Beta 🧪 Issues specific to the Beta branch testing label Dec 17, 2020
@MichaIng MichaIng added this to the v6.34 milestone Dec 17, 2020
@MichaIng
v6.34
a793fa2 
+ RC up
@MichaIng
v6.34
1bf8541 
+ DietPi-Globals | Default RC up
@MichaIng
v6.34
f2dd95d 
+ CHANGELOG | Apply v6.34 release date and PR index
@MichaIng MichaIng merged commit f27fac0 into beta Dec 18, 2020
@MichaIng MichaIng mentioned this pull request Dec 18, 2020
Closed
@seniorgod
Copy link

which mpd version is included in 6.34?
Is it now the 0.22.x ?
if yes i would testing :-)

@MichaIng
Copy link
Owner Author

MichaIng commented Dec 19, 2020 •
edited
Loading

MPD is installed from the Debian repository, so on Buster it is 0.21.5: https://packages.debian.org/mpd
DietPi updates generally are not tied to software updates or the other way round.

Only in rare cases we do a software reinstall/update/migration when it would become incompatible with a changed dietpi-software implementation (like OctoPrint with DietPi v6.34). In most cases the latest available version (either upstream or on Debian repository, depending on where we pull it from) of a software is installed, regardless of the DietPi version, but older DietPi versions may fail to install software when it has changed too much, download URLs changed or something like that 😉.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fpetru fpetru Awaiting requested review from fpetru

@Fourdee Fourdee Awaiting requested review from Fourdee

@Joulinar Joulinar Awaiting requested review from Joulinar

@StephanStS StephanStS Awaiting requested review from StephanStS

Assignees
No one assigned
Labels
Beta 🧪 Issues specific to the Beta branch testing
Projects
None yet
Milestone
v6.34
Development

Successfully merging this pull request may close these issues.
4 participants
@MichaIng @seniorgod @ravenclaw900 @StephanStS