Processed: Forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 896098 https://bugs.kde.org/show_bug.cgi?id=393307
Bug #896098 [krita] krita: Krita's Python scripting not working
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=393307'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
896098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: okular "cannot find latex executable"

[Luigi Toscano]

inkbottle ha scritto:
> On Thursday, April 19, 2018 3:22:26 PM CEST Lisandro Damián Nicanor Pérez 
> Meyer wrote:
>> El miércoles, 18 de abril de 2018 16:38:37 -03 Luigi Toscano escribió:
>>> Lisandro Damián Nicanor Pérez Meyer ha scritto:
 El miércoles, 18 de abril de 2018 12:31:28 -03 inkbottle escribió:
> However the resulting Okular behavior is far from satisfactory:
> The inline note shows only the latex code: in order to see the result
> of
> it, one has to first double click the inline note, and then to click on
> "render latex code"; which is far from providing an immediate and
> intuitive view of the formulas.
>
> However, again, that could be use to compensate that poppler's utf8
> related
> bug: https://bugs.freedesktop.org/show_bug.cgi?id=65956
>
> Provided one possibly modify
> https://github.com/KDE/okular/blob/2aa006fa87240a89ff8446744ccd9f86a48c
> 8d
> d0/ ui/latexrenderer.cpp through the addition of latex packages to
> render
> desired fonts;
> not sure it is so easy, but is is probably easier than fixing a 5 years
> old
> poppler's bug.

 Maybe suggesting this to upstream?
>>>
>>> It would not fix the bug anyway: you don't want to strictly depend on a
>>> (huge deployment of) latex for this.
>>
>> Indeed, this is true.
> 
> So it boils done to a functionality: not very useful, not working very well, 
> and enabling it could clutter the system.
> 
> Which lead to a very straightforward bug reporting course of action: doing 
> noting. I like it.
> 
> 


What I don't like it is when someone reads what I didn't write.
I didn't say that that adding an optional dependency on latex is a problem.
I wrote that this is not *the* solution, because most of the deployments
don't, won't and can't have latex.

-- 
Luigi

Bug#896098: krita: Krita's Python scripting not working

[Aleksey Samoilov]

19.04.2018 21:56, Lisandro Damián Nicanor Pérez Meyer пишет:

Oh, please do reply to the bug report! This has been sent to me in private!

On 19 April 2018 at 14:16, Sunderland93  wrote:

It needs libpython3.6m.so, which is contained in libpython3.6-dev. Without
it Python scripting is not available in Tools > Scripting menu, and error is

Loading Python plugin
"" false
()
()
()
Could not create /usr/lib/x86_64-linux-gnu/libpython3.6m.so
"Cannot load Python library"


On 19.04.2018 20:33, Lisandro Damián Nicanor Pérez Meyer wrote:

El jue., 19 de abr. de 2018 10:15, Sunderland93 
escribió:

Package: krita
Version: 1:4.0.1+dfsg-1
Severity: important

Dear Maintainer,

Krita's Python scripting not working in this version. It needs
libpython3-dev package,
which must added into dependency's (or Recommends section), just like in
Ubuntu


Why would it need a development package for runtime use?

Bug#896098: krita: Krita's Python scripting not working

[Lisandro Damián Nicanor Pérez Meyer]

On 19 April 2018 at 13:33, Lisandro Damián Nicanor Pérez Meyer
 wrote:
[snip]
> Why would it need a development package for runtime use?

User just checked: the app is looking for the unversioned .so instead
of the versioned one. This is a bug in the app I''m afraid.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Re: okular "cannot find latex executable"

[inkbottle]

On Thursday, April 19, 2018 3:22:26 PM CEST Lisandro Damián Nicanor Pérez 
Meyer wrote:
> El miércoles, 18 de abril de 2018 16:38:37 -03 Luigi Toscano escribió:
> > Lisandro Damián Nicanor Pérez Meyer ha scritto:
> > > El miércoles, 18 de abril de 2018 12:31:28 -03 inkbottle escribió:
> > >> However the resulting Okular behavior is far from satisfactory:
> > >> The inline note shows only the latex code: in order to see the result
> > >> of
> > >> it, one has to first double click the inline note, and then to click on
> > >> "render latex code"; which is far from providing an immediate and
> > >> intuitive view of the formulas.
> > >> 
> > >> However, again, that could be use to compensate that poppler's utf8
> > >> related
> > >> bug: https://bugs.freedesktop.org/show_bug.cgi?id=65956
> > >> 
> > >> Provided one possibly modify
> > >> https://github.com/KDE/okular/blob/2aa006fa87240a89ff8446744ccd9f86a48c
> > >> 8d
> > >> d0/ ui/latexrenderer.cpp through the addition of latex packages to
> > >> render
> > >> desired fonts;
> > >> not sure it is so easy, but is is probably easier than fixing a 5 years
> > >> old
> > >> poppler's bug.
> > > 
> > > Maybe suggesting this to upstream?
> > 
> > It would not fix the bug anyway: you don't want to strictly depend on a
> > (huge deployment of) latex for this.
> 
> Indeed, this is true.

So it boils done to a functionality: not very useful, not working very well, 
and enabling it could clutter the system.

Which lead to a very straightforward bug reporting course of action: doing 
noting. I like it.

Bug#896098: krita: Krita's Python scripting not working

[Lisandro Damián Nicanor Pérez Meyer]

El jue., 19 de abr. de 2018 10:15, Sunderland93 
escribió:

> Package: krita
> Version: 1:4.0.1+dfsg-1
> Severity: important
>
> Dear Maintainer,
>
> Krita's Python scripting not working in this version. It needs
> libpython3-dev package,
> which must added into dependency's (or Recommends section), just like in
> Ubuntu


Why would it need a development package for runtime use?

Re: okular "cannot find latex executable"

[Lisandro Damián Nicanor Pérez Meyer]

El miércoles, 18 de abril de 2018 16:38:37 -03 Luigi Toscano escribió:
> Lisandro Damián Nicanor Pérez Meyer ha scritto:
> > El miércoles, 18 de abril de 2018 12:31:28 -03 inkbottle escribió:
> >> However the resulting Okular behavior is far from satisfactory:
> >> The inline note shows only the latex code: in order to see the result of
> >> it, one has to first double click the inline note, and then to click on
> >> "render latex code"; which is far from providing an immediate and
> >> intuitive view of the formulas.
> >> 
> >> However, again, that could be use to compensate that poppler's utf8
> >> related
> >> bug: https://bugs.freedesktop.org/show_bug.cgi?id=65956
> >> 
> >> Provided one possibly modify
> >> https://github.com/KDE/okular/blob/2aa006fa87240a89ff8446744ccd9f86a48c8d
> >> d0/ ui/latexrenderer.cpp through the addition of latex packages to render
> >> desired fonts;
> >> not sure it is so easy, but is is probably easier than fixing a 5 years
> >> old
> >> poppler's bug.
> > 
> > Maybe suggesting this to upstream?
> 
> It would not fix the bug anyway: you don't want to strictly depend on a
> (huge deployment of) latex for this.

Indeed, this is true.

-- 
¿Qué vamos a hacer esta noche Cerebro?
-Lo mismo que todas las noches Pinky...
¡¡¡tratar de conquistar el mundo!!!
  Pinky y Cerebro. Narf.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#896098: krita: Krita's Python scripting not working

[Sunderland93]

Package: krita
Version: 1:4.0.1+dfsg-1
Severity: important

Dear Maintainer,

Krita's Python scripting not working in this version. It needs 
libpython3-dev package,
which must added into dependency's (or Recommends section), just like in 
Ubuntu



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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krita depends on:
ii  kio    5.44.0-2
ii  krita-data 1:4.0.1+dfsg-1
ii  libboost-system1.62.0  1.62.0+dfsg-5+b1
ii  libc6  2.27-3
ii  libexiv2-14    0.25-3.1
ii  libfftw3-double3   3.3.7-1+b1
ii  libgcc1    1:8-20180414-1
ii  libgif7    5.1.4-2
ii  libgsl23   2.4+dfsg-6
ii  libgslcblas0   2.4+dfsg-6
ii  libilmbase23   2.2.1-2
ii  libjpeg62-turbo    1:1.5.2-2+b1
ii  libkf5archive5 5.44.0-1
ii  libkf5completion5  5.44.0-1
ii  libkf5configcore5  5.44.0-1
ii  libkf5configgui5   5.44.0-1
ii  libkf5coreaddons5  5.44.0-1
ii  libkf5crash5   5.44.0-1
ii  libkf5guiaddons5   5.44.0-1
ii  libkf5i18n5    5.44.0-1
ii  libkf5itemviews5   5.44.0-1
ii  libkf5kiocore5 5.44.0-2
ii  libkf5widgetsaddons5   5.44.0-1
ii  libkf5windowsystem5    5.44.0-1
ii  liblcms2-2 2.9-1
ii  libopencolorio1v5  1.1.0~dfsg0-1
ii  libopenexr23   2.2.1-4
ii  libpng16-16    1.6.34-1
ii  libpoppler-qt5-1   0.62.0-2
ii  libpython3.6   3.6.5-3
ii  libqt5concurrent5  5.10.1+dfsg-5
ii  libqt5core5a   5.10.1+dfsg-5
ii  libqt5dbus5    5.10.1+dfsg-5
ii  libqt5gui5 5.10.1+dfsg-5
ii  libqt5multimedia5  5.10.1-2
ii  libqt5network5 5.10.1+dfsg-5
ii  libqt5printsupport5    5.10.1+dfsg-5
ii  libqt5qml5 5.10.1-4
ii  libqt5quick5   5.10.1-4
ii  libqt5quickwidgets5    5.10.1-4
ii  libqt5svg5 5.10.1-2
ii  libqt5widgets5 5.10.1+dfsg-5
ii  libqt5x11extras5   5.10.1-2
ii  libqt5xml5 5.10.1+dfsg-5
ii  libraw16   0.18.8-2
ii  libstdc++6 8-20180414-1
ii  libtiff5   4.0.9-5
ii  libx11-6   2:1.6.5-1
ii  libxcb1    1.13-1
ii  libxi6 2:1.7.9-1
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages krita recommends:
ii  python3-pyqt5    5.10.1+dfsg-1
ii  python3-sip  4.19.8+dfsg-1
ii  qml-module-qtmultimedia  5.10.1-2

Versions of packages krita suggests:
ii  colord  1.3.3-2
ii  ffmpeg  7:3.4.2-2
pn  krita-l10n  

-- no debconf information

Re: peruse_1.2+dfsg-2_source.changes ACCEPTED into unstable

[Lisandro Damián Nicanor Pérez Meyer]

>
>
>[ Pino Toscano ]
>* Move the appdata, and desktop files from peruse-common to peruse: they
>  need to stay together with the executable they refer to, otherwise the
>  installation with AppStream is broken, and just installing
> peruse-common
>  creates broken menu entries
>  - add proper breaks/replaces for this
>

This I definitely need to learn.


   * Do not include debian-qt-kde.mk in rules, since the dh sequencer is
> used
>  directly.
>

Ditto. Do we have proper doc for this?

   * Remove unused build dependencies: kdoctools-dev, libkf5newstuff-dev,
> and
>  libkf5plasma-dev.
>* Remove the unused ${shlibs:Depends} substvar in peruse-common.
>* Tighten the peruse-common dependency in peruse.


And I should have noted this last three, specially the last two.