Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

2018-07-23 Thread Reinhard Tartler
Control: tags -1 -d-i
Control: retitle -1 "Investigate the use of versioned provides in place of
the alternative dependencies in shlibdeps"
Control: severity -1 wishlist

Hi James,


On Sat, Jul 21, 2018 at 11:45 AM James Cowgill  wrote:

> Control: tags -1 - moreinfo
>
> Hi,
>
> On 21/07/18 16:23, Mattia Rizzolo wrote:
> > On Sat, Jul 21, 2018 at 02:41:32PM +0100, James Cowgill wrote:
> >> If versioned provides was working properly everywhere then
> >> possibly it could be used, but I don't think it does yet (although I'm
> >> happy to be corrected!).
> >
> > They do.  In the past 2 years many bugs around the infrastructure were
> > fixed and versioned provides can now be fully used (in particular, there
> > were some last pieces regarding wanna-build and britney, that have been
> > fixed ~1 year ago IIRC).
> >
> > The only thing is that they may be confusing to some, as it's not so
> > straightforward to find a virtual package compared to a plain `apt show`
> > :>
>
> OK thanks. I'll see what I can do about this after the ffmpeg 4.0
> transition has completed.
>
> ​Thanks for looking into this.

If the infrastructure is in place for this now, and there are upsides with
this approach then I agree that this should be evaluated, and the results
documented in this ticket. The thing is, I'm not sure I understand the
upsides.

Discoverability is indeed a concern. How are users supposed to know what to
install in order to get the extra functionality? Will meta-packages (think
libavcodec-extra) help with picking up the right package? Does this also
work for package upgrades, or are there situations where APT might prefer
to remove the -extra variants in favor for base variant?

My main concern with this proposal is the motivation behind it: To support
3rd party packages that have been compiled against a version of ffmpeg that
is NOT found in Debian. I don't think this is something we should
encourage. In the past, people have asked for help with the ffmpeg package
and our reply is typically to replace 3rd party packages with the version
found in Debian, which is frustrating, time-consuming and not in anyone's
interest.

​Dirk, I think the right course of action to get your jitsi backport
working is to contact the supplier of the jitsi package, and ask them to
recompile the package without the use of 3rd party package archives. Feel
free to point them to this email.

​--
regards,
Reinhard


Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

2018-07-21 Thread James Cowgill
Control: tags -1 - moreinfo

Hi,

On 21/07/18 16:23, Mattia Rizzolo wrote:
> On Sat, Jul 21, 2018 at 02:41:32PM +0100, James Cowgill wrote:
>> If versioned provides was working properly everywhere then
>> possibly it could be used, but I don't think it does yet (although I'm
>> happy to be corrected!).
> 
> They do.  In the past 2 years many bugs around the infrastructure were
> fixed and versioned provides can now be fully used (in particular, there
> were some last pieces regarding wanna-build and britney, that have been
> fixed ~1 year ago IIRC).
> 
> The only thing is that they may be confusing to some, as it's not so
> straightforward to find a virtual package compared to a plain `apt show`
> :>

OK thanks. I'll see what I can do about this after the ffmpeg 4.0
transition has completed.

James



signature.asc
Description: OpenPGP digital signature


Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

2018-07-21 Thread Mattia Rizzolo
On Sat, Jul 21, 2018 at 02:41:32PM +0100, James Cowgill wrote:
> If versioned provides was working properly everywhere then
> possibly it could be used, but I don't think it does yet (although I'm
> happy to be corrected!).

They do.  In the past 2 years many bugs around the infrastructure were
fixed and versioned provides can now be fully used (in particular, there
were some last pieces regarding wanna-build and britney, that have been
fixed ~1 year ago IIRC).

The only thing is that they may be confusing to some, as it's not so
straightforward to find a virtual package compared to a plain `apt show`
:>

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

2018-07-21 Thread James Cowgill
Control: tags -1 moreinfo

Hi,

On 20/07/18 23:14, Dirk Lehmann wrote:
> Package: libavcodec-extra57
> Version: 7:3.4.3-1
> Severity: normal
> Tags: d-i
> 
> Dear Maintainer,
> 
> I try to install a backport package which is depending on package
> 'libavcodec57'.  But I have installed the package libavcodec-extra57
> on my machine.  If I try to install it, I get the following error:
> 
> --
> root$> apt-get install jitsi
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  jitsi : Depends: libavcodec57 but it is not going to be installed or
>   libavcodec-ffmpeg56 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> --

Where is this package from? There is no "jitsi" in Debian (anymore) so
it must be unofficial. When packages are built against ffmpeg they
should get a dependency like this which should work with libavcodec-extra:
 libavcodec57 (>= 7:3.4.3) | libavcodec-extra57 (>= 7:3.4.3)

Probably the jitsi packages itself is at fault, or something else is
preventing the installation.

> I'm not really familiar with DPKG, but I think it could be solved if
> the manifest of dpkg-archive from 'libavcodec-extra57' includes a
> 
> --
> [...]
> Provides: libavcodec57
> [...]
> --

Unfortunately this won't work because it won't satisfy versioned
dependencies. If versioned provides was working properly everywhere then
possibly it could be used, but I don't think it does yet (although I'm
happy to be corrected!).

James



signature.asc
Description: OpenPGP digital signature


Bug#904163: libavcodec-extra57 should PROVIDE package libavcodec57

2018-07-20 Thread Dirk Lehmann
Package: libavcodec-extra57
Version: 7:3.4.3-1
Severity: normal
Tags: d-i

Dear Maintainer,

I try to install a backport package which is depending on package
'libavcodec57'.  But I have installed the package libavcodec-extra57
on my machine.  If I try to install it, I get the following error:

--
root$> apt-get install jitsi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 jitsi : Depends: libavcodec57 but it is not going to be installed or
  libavcodec-ffmpeg56 but it is not installable
E: Unable to correct problems, you have held broken packages.
--

I'm not really familiar with DPKG, but I think it could be solved if
the manifest of dpkg-archive from 'libavcodec-extra57' includes a

--
[...]
Provides: libavcodec57
[...]
--

Greetz, Dirk =)

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libavcodec-extra57 depends on:
ii  libavutil55 7:3.4.3-1
ii  libc6   2.27-3
ii  libcairo2   1.15.10-3
ii  libcrystalhd3   1:0.0~git20110715.fdd2f19-13
ii  libglib2.0-02.56.1-2
ii  libgsm1 1.0.13-4+b2
ii  liblzma55.2.2-1.3
ii  libmp3lame0 3.100-2+b1
ii  libopencore-amrnb0  0.1.3-2.1+b2
ii  libopencore-amrwb0  0.1.3-2.1+b2
ii  libopenjp2-72.3.0-1
ii  libopus01.3~beta+20180518-1
ii  librsvg2-2  2.40.20-2
ii  libshine3   3.1.1-2
ii  libsnappy1v51.1.7-1
ii  libspeex1   1.2~rc1.2-1+b2
ii  libswresample2  7:3.4.3-1
ii  libtheora0  1.1.1+dfsg.1-14+b1
ii  libtwolame0 0.3.13-4
ii  libva2  2.1.0-3
ii  libvo-amrwbenc0 0.1.3-1+b1
ii  libvorbis0a 1.3.6-1
ii  libvorbisenc2   1.3.6-1
ii  libvpx5 1.7.0-3
ii  libwavpack1 5.1.0-3
ii  libwebp60.6.1-2
ii  libwebpmux3 0.6.1-2
ii  libx264-152 2:0.152.2854+gite9a5903-2
ii  libx265-160 2.8-4
ii  libxvidcore42:1.3.5-1
ii  libzvbi00.2.35-13
ii  zlib1g  1:1.2.11.dfsg-1

libavcodec-extra57 recommends no packages.

libavcodec-extra57 suggests no packages.

-- debconf-show failed