[Pkg-kde-extras] digikam_7.0.0-1_amd64.changes ACCEPTED into experimental

[Pino Toscano]

In data mercoledì 19 agosto 2020 15:38:46 CEST, Steven Robbins ha scritto:
> On Wednesday, August 19, 2020 5:48:50 A.M. CDT Pino Toscano wrote:
> > Hi Steve,
> > 
> > Can you please not upload binaries, and do source-only uploads?
> 
> I was under the impression that a new source tarball required a binary upload.  
> I'll certainly do a source-only when transition to unstable.

Luckly not! It would be maddness otherwise.

The only two situations that require binary uploads are when going
through the NEW queue, which means either
a) src:foo does not exist, like for a new package
b) any binary package of an existing source was added; for example you
   have src:kfoo that builds deb:kfoo, and you split a deb:kfoo-data
   out of it

> Right now I'm stuck because qtwebengine5-dev, a newly-added build-dep is not 
> built on all architectures.  So I have to figure out a way around that.

Does digikam require QtWebEngine exclusively?
- if yes, there is nothing much that can be done, and you will need to
  remove digikam from release architectures without QtWebEngine
  (see for example my recent #966699 for parley)
- if no, use QtWebKit if still available as option, or nothing and
  disable features

HTH,
-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-extras/attachments/20200819/d2c94b7f/attachment.sig>