Your message dated Fri, 9 Aug 2019 20:07:26 -0400
with message-id
<CANTw=MPNjfJx+KvAc2=ycsz-xtt6h0p8dvblraesbgr7cbt...@mail.gmail.com>
and subject line Re: [pkg-wine-party] Bug#852494: wine: Add libwine.so and
libwine.so.1 alternatives
has caused the Debian Bug report #852494,
regarding wine: Add libwine.so and libwine.so.1 alternatives
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
852494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852494
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: wine
Version: 1.8.6-3
Severity: wishlist
Please add a libwine.so.1 alternative to libwine packages, and
libwine.so to libwine-dev ones. These alternatives should be placed
under /usr/lib/MULTIARCH so that applications depending on libwine avoid
the use of RUNPATH and the binary-or-shlib-defines-rpath lintian error.
The alternatives should not be slaves in the wine package. I suggest to
move the slave alternatives from wine package to their respective
packages (wine32-tools and such), and to depend on an
update-wine-alternatives script (in libwine) that runs
update-alternatives for the installed packages.
smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
On Wed, Jan 10, 2018 at 3:42 PM Javier Serrano Polo wrote:
> > There are no reverse dependencies of libwine, so it is not clear to me
> > how this would actually be helpful.
>
> Sorry, I missed your message. lmms-vst-server depends on wine, but I
> cannot help with lmms-related packaging right now.
My point of view is that lmms should rely solely on the "stable" wine
API, which is the libwine package. Too much complexity will be
required to support that and libwine-development via alternatives.
Best wishes,
Mike
--- End Message ---
