vcswatch reports that
this package seems to have a new changelog entry (version
0~20251011-1, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 5ec998ff8cd938878e01a7921a9c5b48a5c9f744
Author: Robie Basak <robie.basak@oss.qualcomm.com>
Date: Wed Nov 19 09:04:36 2025 +0000
Add and integrate d/check-symlinks
From a package user perspective, we're just shipping a bunch of binaries
without anything else special going on. What goes into which binary
package is managed between upstream metadata and debian/regen.sh.
As a packaging reviewer, I had been checking the output binary packages
by hand, and not manually looking for collisions between packages since
the nature of debian/regen.sh made that less likely.
However, the introduction of symlinks across packages[1] makes things
harder. debian/regen.sh is getting increasingly complicated and it is
easier to focus on verifying the output, but checking the symlinks all
resolve by hand is tedious. So I automated this checking.
[1]: https://salsa.debian.org/lumag/hexagon-dsp-binaries/-/merge_requests/2
Signed-off-by: Robie Basak <robie.basak@oss.qualcomm.com>
commit 0a002f8ee2ddb9ff8614c0a88298993cf9c826fc
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Date: Tue Nov 11 11:08:51 2025 +0200
d/rules: handle Links clauses in config.txt
DSP binaries for some of the devices are shared, upstream uses symlinks
(and Links clauses in config.txt) to handle these cases. Create
corresponding per-device packages.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
commit 73d0c459d9b056b52d26dd5217129b3f1c3589ce
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Date: Wed Nov 12 21:10:52 2025 +0200
d/changelog: start working on 20251011
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
![[bug history graph]](https://qa.debian.org/data/bts/graphs/h/hexagon-dsp-binaries.png){kind=link}