1.4.9 and update README.md.src from README.md

BRANDING.mak

@@ -3,7 +3,7 @@
 
 VERSION_MAJOR = 1
 VERSION_MINOR = 4
-VERSION_MICRO = 8
+VERSION_MICRO = 9
 BRANDING_SHORTNAME = mainline
 BRANDING_LONGNAME = Mainline Kernels
 BRANDING_AUTHORNAME = Brian K. White

README.md

@@ -174,13 +174,13 @@ Sorting on the "Notes" column is a way to see all kernels that have any notes to
   https://github.com/M-P-P-C/Signing-a-Linux-Kernel-for-Secure-Boot
 
 ## Kernels with broken dependencies  
-  The build environment that builds the kernels is newer than most installed systems, and so the built kernels occasionally but regularly break compatibility with all current release and older systems.  
+  The build environment that builds the kernels is newer than most installed systems, and so the built kernels occasionally but regularly break compatibility with all current release and older systems.
 
   The only convenient, practical, clean, safe resolution is "Update your system to the level that includes those dependencies naturally.".  
-  And don't install any newer kernels until that is possible. And if that means the next version of Ubuntu isn't even due to be released for another 6 months, so be it.  
-  
+  And don't install any newer kernels until that is possible. And if that means the next version of Ubuntu isn't even due to be released for another 6 months, so be it.
+
   Otherwise, here are some hack options you may amuse yourself with (substitute "libssl3" for whatever is actually broken for you today): [Install libssl3](../../wiki/Install-libssl3)  
-  TLDR: monkey with apt configs to add beta repos and use priority settings and pinning to try to only let certain packages auto update from them, or manually download specific .deb files from the beta repos and install them with dpkg.  
+  TLDR: monkey with apt configs to add beta repos and use priority settings and pinning to try to only let certain packages auto update from them, or manually download specific .deb files from the beta repos and install them with dpkg.
 
   See [Not Features](#not-features)
 

README.md.src

@@ -143,9 +143,9 @@ Sorting on the "Notes" column is a way to see all kernels that have any notes to
 
 # Help / FAQ
 
-* [MainlineBuilds WIKI](https://wiki.ubuntu.com/Kernel/MainlineBuilds)
+## [MainlineBuilds WIKI](https://wiki.ubuntu.com/Kernel/MainlineBuilds)
 
-* General debugging  
+## General debugging  
   The `-v` or `-v #` option, or the environment variable `VERBOSE=#`, enables increasing levels of verbosity.  
   Example: `$ BRANDING_SHORTNAME-gtk -v 3` or `$ VERBOSE=3 mainline-gtk`  
   The -v option may also be used alone or repeated. The default with no `-v` is the same as `-v 1`.  
@@ -159,24 +159,32 @@ Sorting on the "Notes" column is a way to see all kernels that have any notes to
 
   A few lines of output are printed before the commandline has been parsed, so `-v 0` doesn't silence them.  
   The environment variable is read earlier in the process and can silence all output.  
-  `VERBOSE=0 BRANDING_SHORTNAME --install-latest --yes`
+  `VERBOSE=0 BRANDING_SHORTNAME install-latest --yes`
 
   The exit value is also meaningful.  
-  `VERBOSE=0 ;BRANDING_SHORTNAME --install-latest --yes && BRANDING_SHORTNAME --uninstall-old --yes`  
+  `VERBOSE=0 ;BRANDING_SHORTNAME install-latest --yes && BRANDING_SHORTNAME uninstall-old --yes`  
 
-* If **Uninstall Old** doesn't remove some distribution kernel packages  
+## If **Uninstall Old** doesn't remove some distribution kernel packages  
   Use your normal package manager like apt or synaptic to remove the parent meta-package:  
   `$ sudo apt remove linux-image-generic`  
   Then **Uninstall Old** should successfully remove everything.  
 
-* Secure Boot  
+## Secure Boot  
   Possibly useful, I have not tried:  
   https://github.com/M-P-P-C/Signing-a-Linux-Kernel-for-Secure-Boot
 
-* Kernel versions 5.15.7+ and libssl3  
-  [Install libssl3](../../wiki/Install-libssl3)
+## Kernels with broken dependencies  
+  The build environment that builds the kernels is newer than most installed systems, and so the built kernels occasionally but regularly break compatibility with all current release and older systems.
 
-* Missing kernels  
+  The only convenient, practical, clean, safe resolution is "Update your system to the level that includes those dependencies naturally.".  
+  And don't install any newer kernels until that is possible. And if that means the next version of Ubuntu isn't even due to be released for another 6 months, so be it.
+
+  Otherwise, here are some hack options you may amuse yourself with (substitute "libssl3" for whatever is actually broken for you today): [Install libssl3](../../wiki/Install-libssl3)  
+  TLDR: monkey with apt configs to add beta repos and use priority settings and pinning to try to only let certain packages auto update from them, or manually download specific .deb files from the beta repos and install them with dpkg.
+
+  See [Not Features](#not-features)
+
+## Missing kernels  
   Only viable installable kernels are shown by default. Failed or incomplete builds for your platform/arch are not shown unless the "Hide Invalid" setting is un-selected.  
   If you think the list is missing a kernel, press the "PPA" button to jump to the mainline-ppa web site where the .deb packages come from, and look at the build results for the missing kernel, and you will usually find that it is a failed or incomplete build for your arch (ex: amd64), and can not be installed.
 

debian/changelog

@@ -1,3 +1,11 @@
+mainline (1.4.9) UNRELEASED; urgency=medium
+
+  * Ubuntu kernel site changed their main url
+    from https://kernel.ubuntu.com/~kernel-ppa/mainline/
+    to   https://kernel.ubuntu.com/mainline/
+
+ -- Brian K. White <b.kenyon.w@gmail.com>  Mon, 16 Oct 2023 02:22:33 -0400
+
 mainline (1.4.8) unstable; urgency=medium
 
   * change option --save-config to command write-config