Your message dated Fri, 29 Apr 2022 09:46:22 -0400
with message-id
<cad+gyvz4yravbecykz4x1qibwrujdaogct76voehbmn6mbg...@mail.gmail.com>
and subject line Re: Bug#1010352: wpewebkit: No longer provides libsoup2
version needed by gstreamer
has caused the Debian Bug report #1010352,
regarding wpewebkit: No longer provides libsoup2 version needed by gstreamer
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.)
--
1010352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010352
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: wpewebkit
Version: 2.36.0-1
Severity: serious
X-Debbugs-CC: [email protected]
wpewebkit has 2 reverse dependencies in Debian: cog and
gstreamer1.0-wpe. Although cog was switched to use the new libsoup3,
gstreamer1.0-wpe was not.
Currently, the Debian wpewebkit package only builds the libsoup3
version but it needs to keep building the libsoup2 version until
gstreamer has switched.
Also, the package names in debian/control do not match the actual
package names built. I believe this is a violation of Debian Policy.
(Also it appears to break Ubuntu's NBS tracker.)
I suggest you do like webkit2gtk and offer both libsoup2 and libsoup3
for now if you want to have the libsoup3 version available.
Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
On Fri, Apr 29, 2022 at 9:25 AM Alberto Garcia <[email protected]> wrote:
> On Fri, Apr 29, 2022 at 06:56:45AM -0400, Jeremy Bicha wrote:
> > Also, the package names in debian/control do not match the actual
> > package names built. I believe this is a violation of Debian Policy.
> > (Also it appears to break Ubuntu's NBS tracker.)
>
> It lists both versions but we only build one or the other depending on
> the target distro. If it causes breakage I guess I'll change it.
The breakage was because I tried to enable the libsoup2 build. If we
only do the libsoup3 build, then debian/control matches.
So I'll close this bug. Thanks for the help.
Thank you,
Jeremy Bicha
--- End Message ---
