Am 06.09.20 um 13:59 schrieb Alexander Volkov:
> Looks like merge requests are disabled for
> https://salsa.debian.org/debian/gimagereader
True, I enabled them now (I tend to do taht as it seems to be the easiest way to
disable the debian-janitor)
Thanks for your contribution, I'll upload a new
Hi,
Looks like merge requests are disabled for
https://salsa.debian.org/debian/gimagereader
I can't create a merge request from
https://salsa.debian.org/avolkov-guest/gimagereader/-/commits/qt5
Will take care of once qtspell is fixed, right now it FTBFS.
(https://bugs.debian.org/918351)
Should be no problem.
Cheers Alf
Hi,
uh, I somehow lost my work on the qt5 version :-(
If anyone prepares a merge request I'm happy to accept it - I fear I will not be
able to do the work before the upcoming freeze myself.
Best,
Philip
signature.asc
Description: OpenPGP digital signature
No worries and no hurry, have the same problem with audacious - the Qt
version has improved a lot, but i guess it is not prime time ready. So -
patience is a virtue.
Cheers Alf
signature.asc
Description: OpenPGP digital signature
Hi,
don't worry, although I just uploaded gImageReader 3.3.0 without qt5 front-end
this does not mean that I will not add it with the next upload. I try to upload
a
qt5 enabled version later this week (but I have to contact my former sponsor and
it has to pass the NEW queue).
Best,
Philip
Thanks. And waiting is the best thing one could do for now (fingers
crossed).
signature.asc
Description: OpenPGP digital signature
Hi Alf,
On 19.09.18 at 23:04, Alf Gaida wrote:
> QtSpell is in Debian now - so this is not a problem any longer. If you
> accept merge requests i would be able to write the missed things for Qt5
> and maintain it long term. (I'm selfish, i want gimagereader-qt5 for LXQt)
thanks, I have already
Hi,
QtSpell is in Debian now - so this is not a problem any longer. If you
accept merge requests i would be able to write the missed things for Qt5
and maintain it long term. (I'm selfish, i want gimagereader-qt5 for LXQt)
Cheers Alf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
> additionally, I would like to add that even if nobody volunteers to maintain
> qtspell in debian the developer himself maintains a packaging for debian in
> the source tree
>
>
additionally, I would like to add that even if nobody volunteers to
maintain qtspell in debian the developer himself maintains a packaging
for debian in the source tree
https://github.com/manisandro/qtspell/tree/master/packaging/debian
and it could be taken from there. This could be
well, not exactly aesthetics...
In any case, and as you pointed out the real problem of not having the
qt front-end is that qtspell package is not in Debian, which would be
equivalent to gtkspellmm for gtk3. Thanks a lot anyway
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OK, it's about aesthetics. But who will maintain qtspell? As far as I see, it's
not in Debian. Technically it's not possible to enable the qt front-end at the
moment.
Best,
Philip
-BEGIN PGP SIGNATURE-
The main benefits will be better usability, cleaner interface,
compatibility with any window manager and desktop environment. It does
not depend on kdelibs since it is a pure qt application and thus it will
be very lightweight.
The gtk3 front-end, on the other hand, breaks many window
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: severity -1 wishlist
Control: tags -1 moreinfo
I'm not a fan of doing this so you have to convince me ;-).
Could you please elaborate why I should do this? I don't see problems using the
gtk3 front-end in a qt environment. What's the
Package: gimagereader
Version: 3.2.3-2
please enable qt5 front-end, a sample packaging for debian with both gtk
and qt fron-ends is available in the source code:
https://github.com/manisandro/gImageReader/tree/master/packaging/debian
you might also need qtspell package:
16 matches
Mail list logo
