Generated.

diff --git a/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html b/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
index 402f508c37147500c100135ad670b86e40990c4e..1efcb53246473a754497de6e05d4c1e1f9d31068 100644 (file)
--- a/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
+++ b/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
@@ -81,6 +81,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/archive/2018/07/07.rss b/blog/archive/2018/07/07.rss
index d46bf7d70f7714ad1a4a2a7792d444d179a9313f..cb41197b83e519b16839a15e696564fca113094e 100644 (file)
--- a/blog/archive/2018/07/07.rss
+++ b/blog/archive/2018/07/07.rss
@@ -70,6 +70,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/archive/2018/07/index.html b/blog/archive/2018/07/index.html
index 9522c2890b8a54699850414688f0fa561c653c65..447cdf730194ac837a0713050f90e57d3dca583d 100644 (file)
--- a/blog/archive/2018/07/index.html
+++ b/blog/archive/2018/07/index.html
@@ -88,6 +88,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/index.html b/blog/index.html
index 75f771d84e4eebec4417b32904c1a0f47e8fe5f1..e446b3af93c095361bfc7b33728ea5551d2aff27 100644 (file)
--- a/blog/index.html
+++ b/blog/index.html
@@ -81,6 +81,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/index.rss b/blog/index.rss
index 7715f464455f9ae068908ff7154ebe237dff462e..d61414e40423badb887f83ea3871cd6999071c54 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -70,6 +70,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index d656bfbd62c824b74c56f86619b743de1a857317..73f65a35890a212fe0182ae8fa9e4c81de8d566a 100644 (file)
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.rss
@@ -70,6 +70,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index d481ed6e9e2e3fa276c61570eab06576dc88d40a..d85296bead360d8ee3f526556afcec6595c10344 100644 (file)
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -87,6 +87,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index 2ae24819ab0f1e145fef009e8e740775fc07cbb6..0bf4cc00581a730a8073fb375273aa608618c694 100644 (file)
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -70,6 +70,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>

diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 1eecc309d4746c9eb65b16abf3b3be1b060d744b..fb8db73d22b664a99d45c2eb1a36725e68761011 100644 (file)
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -87,6 +87,14 @@ the packages that are simply too large to unpack.  Today this was
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 
 'ghc', but I have run into other large packages causing similar
 problems earlier (like TeX).</p>
 

+<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
+alternative ways to handle this.  The "unattended-upgrades
+--minimal-upgrade-steps" option will try to calculate upgrade sets for
+each package to upgrade, and then upgrade them in order, smallest set
+first.  It might be a better option than my above mentioned script.
+Also, "aptutude upgrade" can upgrade single packages, thus avoiding
+the need for using "dpkg -i" in the script above.</p>
+

 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 <p>As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>