Generated.

diff --git a/blog/New_oggz_release_1_1_2_after_15_years.html b/blog/New_oggz_release_1_1_2_after_15_years.html
index 99212ef0af70df37a56ef8caf0470ddba4d2d929..58736c9b33b5c06ea874ae6ec4a965780c71104f 100644 (file)
--- a/blog/New_oggz_release_1_1_2_after_15_years.html
+++ b/blog/New_oggz_release_1_1_2_after_15_years.html
@@ -31,7 +31,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/archive/2025/02/02.rss b/blog/archive/2025/02/02.rss
index 200c43fcbe4c5142150b0b94a4a923641e24c87d..829f9d8f94c7808a219e89cceb30d483a36d05e3 100644 (file)
--- a/blog/archive/2025/02/02.rss
+++ b/blog/archive/2025/02/02.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/archive/2025/02/index.html b/blog/archive/2025/02/index.html
index 1f69edf291e3656be47e249a027346d3b358be71..f4a51f6ca2795a4d54b5c986611ea66a5615671d 100644 (file)
--- a/blog/archive/2025/02/index.html
+++ b/blog/archive/2025/02/index.html
@@ -38,7 +38,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/index.html b/blog/index.html
index ec518ae7480976b757c96b7e39e76bd5ddb223f3..19601d0e1667a95b9feea2a1fd9de8786239f20a 100644 (file)
--- a/blog/index.html
+++ b/blog/index.html
@@ -31,7 +31,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/index.rss b/blog/index.rss
index 786196719fba6ebd7aa6ce3fecb1360efdd53e0f..6b6c47afa5df361b9498b01207d99ac60cf51128 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index ba794947850fcd98d19f86ccfac7c2ca421da870..a5c25b9631f83101efe23340101fa47de50f6336 100644 (file)
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index d405a29576448a52197d96e41fdf4bbc2a3abfd5..fe1e60dc27d40bec5af2adaef1706e484359d05a 100644 (file)
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -37,7 +37,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index c2f0d7e4c532a9b62346a554b1950d107b24d18a..3d81e116c25f96303d68cb377ff6d72a89f66251 100644 (file)
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 95db49eda2e64b486e412354cef3610c48f0e7ed..32cbdaaa89415c924b79a9fe0ff89ca1c0eeb5f1 100644 (file)
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -37,7 +37,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/multimedia/index.html b/blog/tags/multimedia/index.html
index 21b415a8a704e459af7765db0c9e82d26e8df971..222b23f9b0fb32a8573b8c9a1960cdac5e5853cd 100644 (file)
--- a/blog/tags/multimedia/index.html
+++ b/blog/tags/multimedia/index.html
@@ -37,7 +37,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/multimedia/multimedia.rss b/blog/tags/multimedia/multimedia.rss
index d19f6972e4e217cca3156f2d859ed8ce20c710fb..a041df6fe4bfb2a3c5c79357f505d8f5d93bf298 100644 (file)
--- a/blog/tags/multimedia/multimedia.rss
+++ b/blog/tags/multimedia/multimedia.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html
index 405640bc327dc605e55bf3b26c5759fbe33101d2..72024dcc728ae1fe9f119030461bd4eaa63f9712 100644 (file)
--- a/blog/tags/standard/index.html
+++ b/blog/tags/standard/index.html
@@ -37,7 +37,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss
index 3eaf7b7c817600ebea9221144b98269840b7fad5..1d2bb3376a9ac4a77b9bd917dfc4bff3174ecd54 100644 (file)
--- a/blog/tags/standard/standard.rss
+++ b/blog/tags/standard/standard.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/video/index.html b/blog/tags/video/index.html
index d27a5daa74930d2e873188716eab97a9fa622567..e0c604dc9bb91606ef47fe946fe4282fbcc28b84 100644 (file)
--- a/blog/tags/video/index.html
+++ b/blog/tags/video/index.html
@@ -37,7 +37,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I

diff --git a/blog/tags/video/video.rss b/blog/tags/video/video.rss
index d980bc30baffdad1b605c5413ed9bbff70cce0ab..e10a8db42588685e2b31bae83a025ed640773795 100644 (file)
--- a/blog/tags/video/video.rss
+++ b/blog/tags/video/video.rss
@@ -20,7 +20,7 @@ package, and I even noticed that I had passed on these patches to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to
 upstream five years ago.  A handful crash bugs had been reported
 against the Debian package, and looking at the upstream repository I
 even found a few crash bugs reported there too.  To add insult to

-injury, I discovered that upstream had accumulated several fixes the
+injury, I discovered that upstream had accumulated several fixes in the

 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I
 years between 2010 and now, and many of them had not made their way
 into the Debian package.  I decided enough was enough, and that a new
 upstream release was needed fixing these nasty crash bugs.  Luckily I