On Tue, Jan 22, 2019 at 09:25:01AM +0100, Mattia Rizzolo wrote:
> It does?
> mattia@warren ~ % rmadison -S -s unstable muparser
> libmuparser-dev | 2.2.6.1+dfsg-1 | unstable | amd64, arm64, armel, armhf,
> hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel,
> ppc64el, s390x
> libmuparser-doc | 2.2.3-6 | unstable | all
> libmuparser2v5 | 2.2.6.1+dfsg-1 | unstable | amd64, arm64, armel, armhf,
> hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel,
> ppc64el, s390x
> muparser | 2.2.3-6 | unstable | source
> muparser | 2.2.6.1+dfsg-1 | unstable | source
>
>
> You have a cruft libmuparser-doc (that interestingly is not listed in
> the cruft-report…).
Should I file a separate bug report or will you deal with this?
> For the future, also what Lucas said may be relevant in some cases,
> although luckily it's a rare matter and not many developers need to
> mess with (or even know about) that.
I agree that you do not really stumble about this kind of issues in
every day work. I'm just working down a list of packages which do not
have (or do not seem to have) Salsa in Vcs fields. I could probably
create a more nifty SQL query for my purpose ignoring this kind of stuff
but I think its rather a feature to stumble upon this cruft and report
it.
BTW, if we are talking about this I found two other packages:
$ rmadison -S -s unstable libmuscle
libmuscle | 3.7+4565-2 | unstable | source
libmuscle | 3.7+4565-6 | unstable | source
libmuscle-3.7-1 | 3.7+4565-2 | unstable | hurd-i386, kfreebsd-amd64,
kfreebsd-i386
libmuscle-3.7-dev | 3.7+4565-2 | unstable | hurd-i386, kfreebsd-amd64,
kfreebsd-i386
libmuscle-dev | 3.7+4565-6 | unstable | amd64, arm64, armel, armhf,
i386, mips, mips64el, mipsel, ppc64el, s390x
libmuscle1 | 3.7+4565-6 | unstable | amd64, arm64, armel, armhf,
i386, mips, mips64el, mipsel, ppc64el, s390x
$ rmadison -S -s unstable libmems
libmems | 1.6.0+4725-4 | unstable | source
libmems | 1.6.0+4725-8 | unstable | source
libmems-1.6-1v5 | 1.6.0+4725-4 | unstable | kfreebsd-amd64, kfreebsd-i386
libmems-1.6-dev | 1.6.0+4725-4 | unstable | kfreebsd-amd64, kfreebsd-i386
libmems-dev | 1.6.0+4725-8+b1 | unstable | amd64, arm64, armel, armhf,
i386, mips, mips64el, mipsel, ppc64el, s390x
libmems1 | 1.6.0+4725-8+b1 | unstable | amd64, arm64, armel, armhf,
i386, mips, mips64el, mipsel, ppc64el, s390x
Please let me know whether I should file separate bug reports about
deleting libmuscle 3.7+4565-2 and libmems 1.6.0+4725-4.
Kind regards
Andreas.
--
http://fam-tille.de
