[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#919218: marked as done (non-transition: libqt5gui5-gles)

Your message dated Thu, 19 Dec 2019 23:15:19 +0300
with message-id <20191219201519.GA375621@mitya57.me>
and subject line Re: Bug#919218: non-transition: libqt5gui5-gles
has caused the Debian Bug report #919218,
regarding non-transition: libqt5gui5-gles
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 owner@bugs.debian.org
immediately.)


-- 
919218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919218
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org

Dear Release team,

In Qt/KDE team, we have recently been working on Qt packages built
with OpenGL ES support. This is what most participants of the Qt OpenGL
thread [1] expressed their wish for.

The main idea is that there is now a libqt5gui5-gles package (and,
in future, libqt5quick5-gles and some others) that can be installed
instead of their non-gles equivalents and provide mostly the same API.
It is described in more details in README.Debian [2].

However, in order for this scheme to work properly, we need to rebuild
all packages depending on libqt5gui5 to gain a new dependency on
libqt5gui5 | libqt5gui5-gles (they will get it automatically from the
symbols file if they do not use any desktop OpenGL specific ABI).

This is not a regular transition because the packages can be rebuilt
at any time, in any order, and there are no testing migrations involved.

Would such a rebuild be possible? If yes, can we plan for it to happen
after the freeze? Or maybe it's even possible to do it now?

Ben file:

title = "libqt5gui5-gles";
is_affected = .depends ~ "libqt5gui5";
is_good = .depends ~ "libqt5gui5-gles";
is_bad = .depends ~ "libqt5gui5" & ! .depends ~ "libqt5gui5-gles";

[1]: https://lists.debian.org/debian-arm/2018/11/msg00021.html
[2]: https://salsa.debian.org/qt-kde-team/qt/qtbase/blob/gles/master/debian/README.Debian

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Mon, Dec 09, 2019 at 11:32:10PM +0200, Graham Inggs wrote:
> Hi Dmitry
>
> [...]
> If I missed something, or if something needs to be given back, please
> let me know.

I am closing this bug as nothing is left to be done here.

I am currently preparing a qtdeclarative5-gles package, and I will file
a new bug for rebuilds against it when it is accepted from the NEW queue.

> There were a number of FTBFS, I haven't been through them yet to see
> which need bugs filed.  Is this something you plan to do?

There are quite a lot of packages that FTBFS, and it looks like most of
them do not have FTBFS bugs filed yet.

I can go through the list and file some bugs manually, but I do not have
time to file all of them. Maybe someone has a script to automate filing
FTBFS bugs?

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: