Package: qt6-charts-dev
Version: 6.4.2-1
Severity: normal
Dear Maintainer,
I was trying to configure a project which Build-Depends on qt6-charts-dev
At build time I have the error below.
If I install also qml6-module-qtcharts, then configure is made successfully.
Should this be added as a
Hello,
Not sure this fits your issue and if this could work.
I used to produce android-builds that are sort of 'target' builds (and not
host builds). There is a specific qmake to be called when building with a
target-build. That qmake is in the bin directory of the target build. And that
s applied.
Rgds
Fab
Le mardi 2 mars 2021, 16:59:35 CEST Fab Stz a écrit :
> Hello,
>
> > Well, the original code is rather bad indeed, because it relies on the
> > order of groups returned by getgrent, and picks the *last* available
> > one. In your case, if you have a
Hello,
I had the same problem after migrating from Buster to Bullseye.
However, I remembered that in the past I moved the akonadi folder in ~/.local/
share/ to another partition and then created a symbolic link to it.
I reverted that and relocated the akonadi folder to its initial place, what
Hello,
I'm trying to package Qt for Android.
With v5.12, one has to run ./configure with -android-arch option
This options takes only one value at a time.
So I can compile once for armeabi-v71.
Then after that, restart and compile the arm64-v8a version, and the x86 &
x86_64... That makes
4
Hello,
> Well, the original code is rather bad indeed, because it relies on the
> order of groups returned by getgrent, and picks the *last* available
> one. In your case, if you have an "operator" group, it will be used.
Ok, this explains it then.
Well it's a fresh debian install of
Package: k3b
Version: 20.12.2-1
Severity: normal
Tags: patch
Dear Maintainer,
With k3b, when wanting to set the external program permissions, it wants to
set
them with user "operator" instead of "cdrom" which may be more adequate
according to the description of the groups in
Hello,
I confirm this is still present in latest bullseye having sddm version
0.19.0-2 (amd64)
Maybe this is somehow linked to https://github.com/systemd/systemd/issues/
12345 ?
Is that actually a sddm or a systemd bug ?
Regards
On Sat, 07 Mar 2020 20:55:57 + Andy Wood wrote:
>
8 matches
Mail list logo
