[Debian-med-packaging] Bug#959643: Any idea whether latest version of pbbam is 1.0.7 or rather 1.3.0 (Was: Bug#959643)
Andreas Tille
tille at debian.org
Sun Jun 21 17:52:38 BST 2020
Hi Adrian,
On Sun, Jun 21, 2020 at 07:13:25PM +0300, Adrian Bunk wrote:
> On Wed, May 27, 2020 at 02:06:40PM +1200, Michael Hudson-Doyle wrote:
> > FWIW there is a new release (1.0.7) available and that seems to fix this
> > failure (in Ubuntu, anyway).
>
> Andreas, after looking at the sources I would say upgrading pbbam like
> Ubuntu has done (including a round through NEW for the changed soname)
> is the best way to fix this FTBFS.
>
> BTW: The watch feels seems to no longer work.
I intended to fix the watch file using
diff --git a/debian/watch b/debian/watch
index 1b64644..d6bee57 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,4 +1,4 @@
version=4
opts="repacksuffix=+dfsg,dversionmangle=s/\+dfsg//g,repack,compression=xz" \
- https://github.com/PacificBiosciences/pbbam/releases .*/archive/@ANY_VERSION@@ARCHIVE_EXT@
+ https://github.com/PacificBiosciences/pbbam/releases .*/archive/v?@ANY_VERSION@@ARCHIVE_EXT@
and expected to get version 1.0.7 as result since this is the latest
version mentioned on the Releases page. However, it returns 1.3.0
which is actually the latest tag. I'm now wondering what we should
package. Any user of pbbam here on the list to clarify?
Kind regards
Andreas.
--
http://fam-tille.de
More information about the Debian-med-packaging
mailing list