From: Petter Reinholdtsen Date: Sun, 9 Feb 2025 00:05:59 +0000 (+0100) Subject: Generated. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/6cbb441f66a4d126b888a36b4fa46536b650eabd 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 99212ef0af..58736c9b33 100644 --- 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 -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 diff --git a/blog/archive/2025/02/02.rss b/blog/archive/2025/02/02.rss index 200c43fcbe..829f9d8f94 100644 --- 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 -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 diff --git a/blog/archive/2025/02/index.html b/blog/archive/2025/02/index.html index 1f69edf291..f4a51f6ca2 100644 --- 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 -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 diff --git a/blog/index.html b/blog/index.html index ec518ae748..19601d0e16 100644 --- 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 -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 diff --git a/blog/index.rss b/blog/index.rss index 786196719f..6b6c47afa5 100644 --- 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 -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 diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss index ba79494785..a5c25b9631 100644 --- 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 -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 diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index d405a29576..fe1e60dc27 100644 --- 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 -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 diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index c2f0d7e4c5..3d81e116c2 100644 --- 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 -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 diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index 95db49eda2..32cbdaaa89 100644 --- 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 -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 diff --git a/blog/tags/multimedia/index.html b/blog/tags/multimedia/index.html index 21b415a8a7..222b23f9b0 100644 --- 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 -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 diff --git a/blog/tags/multimedia/multimedia.rss b/blog/tags/multimedia/multimedia.rss index d19f6972e4..a041df6fe4 100644 --- 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 -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 diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html index 405640bc32..72024dcc72 100644 --- 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 -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 diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss index 3eaf7b7c81..1d2bb3376a 100644 --- 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 -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 diff --git a/blog/tags/video/index.html b/blog/tags/video/index.html index d27a5daa74..e0c604dc9b 100644 --- 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 -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 diff --git a/blog/tags/video/video.rss b/blog/tags/video/video.rss index d980bc30ba..e10a8db425 100644 --- 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 -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