commit 27f66052c20d9178c2462f8a6aa4fab4cceda033
Author: Georges Khaznadar <georgesk@debian.org>
Date: Tue Aug 4 19:00:57 2026 +0200
removed a debian patch
commit b7210ad5157109b3c096f46c561122399f4aa7ee
Author: Georges Khaznadar <georgesk@debian.org>
Date: Tue Aug 4 18:40:27 2026 +0200
remove the double entry for 5.10.3
commit e98d8f8ceb1db4b84d9d99e0360c55c19861e1a9
Author: Georges Khaznadar <georgesk@debian.org>
Date: Tue Aug 4 18:34:52 2026 +0200
upload to unstable
commit 7414100dc0f16d0278183f2c1b3c7a8673d42008
Merge: cef923e 103517b
Author: Georges Khaznadar <georgesk@debian.org>
Date: Tue Aug 4 18:33:43 2026 +0200
Update upstream source from tag 'upstream/5.10.3'
Update to upstream version '5.10.3'
with Debian dir 98223f074e4d790ffe67ca5f9e9152883a6ab8c8
commit 103517b258318a636765191d2c22d58bb4db2e7a
Author: Georges Khaznadar <georgesk@debian.org>
Date: Tue Aug 4 18:33:26 2026 +0200
New upstream version 5.10.3
Among the 1 debian patch available in version 5.10.3-1 of the package, we noticed the following issues: