pykde4_4.14.3-3_armhf.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Jun 2017 14:47:34 -0400 Source: pykde4 Binary: python-kde4 python-kde4-dev python-kde4-doc python3-pykde4 Architecture: armhf Version: 4:4.14.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE

Processing of pykde4_4.14.3-3_armhf.changes

pykde4_4.14.3-3_armhf.changes uploaded successfully to localhost along with the files: pykde4_4.14.3-3_armhf.buildinfo python-kde4-dbgsym_4.14.3-3_armhf.deb python-kde4_4.14.3-3_armhf.deb python3-pykde4-dbgsym_4.14.3-3_armhf.deb python3-pykde4_4.14.3-3_armhf.deb Greetings, Your

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 866506 src:qtbase-opensource-src 5.7.1+dfsg-1 Bug #866506 [src:nageru] qtbase-opensource-src: either drop GLES2 defintions from public headers or pass the right flags Bug reassigned from package 'src:nageru' to 'src:qtbase-opensource-src

Bug#836544: marked as done (libutempter FTCBFS: uses build architecture compiler)

Your message dated Thu, 29 Jun 2017 21:38:58 +0200 with message-id <20170629193858.t3uuttugqnplu...@alf.mars> and subject line Re: libutempter FTCBFS: uses build architecture compiler has caused the Debian Bug report #836544, regarding libutempter FTCBFS: uses build architecture compiler to be mark

Bug#836544: libutempter FTCBFS: uses build architecture compiler

Hi, On Sat, 3 Sep 2016 22:51:34 +0200 Helmut Grohne wrote: > Source: libutempter > Version: 1.1.6-3 > Tags: patch > User: helm...@debian.org > Usertags: rebootstrap > > libutempter fails to cross build from source, because it uses the build > architecture compiler. The later dh_strip (which uses

Bug#841411: libkf5kface: FTBFS: error with opencv 3.1

Hola Maximiliano, I have investigated a bit to compile libkf5kface against opencv3.1. I have found one patch from upstream and another to activate CMake to build against opencv 3.1. With this two patches libkf5kface builds but fail in the test: /usr/bin/ctest --force-new-ctest-process -j8 Tes

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On 29 June 2017 at 13:13, Steinar H. Gunderson wrote: > On Thu, Jun 29, 2017 at 01:10:20PM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > The header if there at build time, but as it is exposed as public API you > > might need it too. > > If Qt tries to #include a GLES header in its publ

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On Thu, Jun 29, 2017 at 01:10:20PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > The header if there at build time, but as it is exposed as public API you > might need it too. If Qt tries to #include a GLES header in its public headers, surely lack of those headers would be en error message

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

The header if there at build time, but as it is exposed as public API you might need it too. Anyways I'll give it a try as soon as possible. El 29 jun. 2017 1:01 p.m., "Steinar H. Gunderson" escribió: > On Thu, Jun 29, 2017 at 10:49:42AM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > I

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On Thu, Jun 29, 2017 at 10:49:42AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > I would first add libgles2-mesa-dev as a build dependency and try building > nageru on arm. If it works maybe adding that dependency to > libqt5opengl5-dev will do the trick (and I'm pretty confident that buildi

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On 29 June 2017 at 10:41, Steinar H. Gunderson wrote: > On Thu, Jun 29, 2017 at 04:38:26PM +0300, Dmitry Shachnev wrote: > > This was fixed in Qt 5.9 upstream, see this commit: > > https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7e393280e4d07393 > > > > We are already working on a transition to

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On Thu, Jun 29, 2017 at 04:38:26PM +0300, Dmitry Shachnev wrote: > This was fixed in Qt 5.9 upstream, see this commit: > https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7e393280e4d07393 > > We are already working on a transition to Qt 5.9, so the fix should be > available within a month. OK. I'd

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

Hi all, On Thu, Jun 22, 2017 at 11:59:15PM +0300, Adrian Bunk wrote: > At first sight it actually looks like a bug in qtbase5-dev to me, > adding the maintainer to Cc: > > /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h > > inline void QOpenGLFunctions::glBindTexture(GLenum target, GLui

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

Maybe we need to let qtopengl depend upon libgles2-mesa-dev. Steinar: can you check that adding that B-D makes the build work on arm? On 29 June 2017 at 10:18, Lisandro Damián Nicanor Pérez Meyer < perezme...@gmail.com> wrote: > Or if it is implemented at all. > > On 29 June 2017 at 10:01, Stein

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

Or if it is implemented at all. On 29 June 2017 at 10:01, Steinar H. Gunderson wrote: > On Thu, Jun 29, 2017 at 09:52:22AM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > Normally the issue was with apps using GLU/GLUT because it has not been > ported > > to GLES, so I first suspected th

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On Thu, Jun 29, 2017 at 09:52:22AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Normally the issue was with apps using GLU/GLUT because it has not been > ported > to GLES, so I first suspected this... but it seems not the issue. > > ::glBindTexture is definitely not a Qt call: > >

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On jueves, 29 de junio de 2017 09:27:19 -03 Steinar H. Gunderson wrote: > On Thu, Jun 22, 2017 at 11:59:15PM +0300, Adrian Bunk wrote: > > On Thu, Jun 22, 2017 at 02:41:17PM +0200, Steinar H. Gunderson wrote: > >> On Thu, Jun 22, 2017 at 03:35:33PM +0300, Adrian Bunk wrote: > >> > Am armel and armh

Processed: user debian...@lists.debian.org, usertagging 864927, affects 864927

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 864927 piuparts Usertags were: piuparts. Usertags are now: piuparts. > affects 864927 + live-task-kde Bug #864927 [plasma-desktop-data,kde

Fixed: chroot-installation_sid_install_qt5/930

See https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/930//console or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/930/ for more information.

Fixed: chroot-installation_sid_install_qt4/923

See https://jenkins.debian.net/job/chroot-installation_sid_install_qt4/923//console or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt4/923/ for more information.

KDE Plasma network speed display using plasma-nm

Hi, I installed the KDE Plasma desktop included in the new Debian Stretch (9) distribution. I noticed that the network speed display always displayed zero speed despite ongoing network traffic. It started displaying the network speed properly after some time. I think it is because I installed

Fixed: chroot-installation_sid_install_kde/1615

See https://jenkins.debian.net/job/chroot-installation_sid_install_kde/1615//console or just https://jenkins.debian.net/job/chroot-installation_sid_install_kde/1615/ for more information.

Re: Bug#865530: nageru FTBFS on armhf/armel: error: '::glBindTexture' has not been declared

On Thu, Jun 22, 2017 at 11:59:15PM +0300, Adrian Bunk wrote: > On Thu, Jun 22, 2017 at 02:41:17PM +0200, Steinar H. Gunderson wrote: >> On Thu, Jun 22, 2017 at 03:35:33PM +0300, Adrian Bunk wrote: >> > Am armel and armhf, Qt is compiled with OpenGL ES instead of full OpenGL. >> >> Interesting. But