Re: [Slackbuilds-users] Chromium build broken in 14.1

On 02/01/2017 10:38 AM, Willy Sudiarto Raharjo wrote: >> Considering we've not seen an update in 3 years, at this point I think >> we can safely say that the SBo Chromium is a zombie ship ;) >> >> Seriously though, it's not good to leave stagnant builds for high >> profile networking software

Re: [Slackbuilds-users] Chromium build broken in 14.1

> Considering we've not seen an update in 3 years, at this point I think > we can safely say that the SBo Chromium is a zombie ship ;) > > Seriously though, it's not good to leave stagnant builds for high > profile networking software (that must be riddled with security holes). > There simply is

Re: [Slackbuilds-users] Chromium build broken in 14.1

On 02/01/2017 10:27 AM, Willy Sudiarto Raharjo wrote: >> Is there any reason why SBo doesn't just use the slackbuild that >> alienbob maintains for chromium anyway? > > That's up to the maintainer Considering we've not seen an update in 3 years, at this point I think we can safely say that the

Re: [Slackbuilds-users] Chromium build broken in 14.1

Is there any reason why SBo doesn't just use the slackbuild that alienbob maintains for chromium anyway? I think this is a good reason: # This package is built with Alien's Google API keys for Chromium. # The keys are contained in the file "chromium_apikeys". # If you want to rebuild this

Re: [Slackbuilds-users] Chromium build broken in 14.1

> Is there any reason why SBo doesn't just use the slackbuild that > alienbob maintains for chromium anyway? That's up to the maintainer -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing

Re: [Slackbuilds-users] Chromium build broken in 14.1

On 02/01/2017 10:14 AM, Rich Shepard wrote: > On Wed, 1 Feb 2017, David O'Shaughnessy wrote: > >> The chromium version on SBo (31.0.1650.57) was released in late 2013! > > I'm using Alien BOB's package, chromium-51.0.2704.84-i486-1alien, on > 14.1. > He might have an upgrade available, but

Re: [Slackbuilds-users] Chromium build broken in 14.1

On 02/01/2017 10:23 AM, David O'Shaughnessy wrote: > On 02/01/2017 10:19 AM, JCA wrote: >> Well, that's what is available in Slackbuilds for 14.1. I guess that it >> is not really maintained anymore :-( > > It's not maintained for any Slackware version. Vivaldi (based on > chromium) is probably a

Re: [Slackbuilds-users] Chromium build broken in 14.1

On 02/01/2017 10:19 AM, JCA wrote: > Well, that's what is available in Slackbuilds for 14.1. I guess that it > is not really maintained anymore :-( It's not maintained for any Slackware version. Vivaldi (based on chromium) is probably a better SBo option at this point. -- Dave

Re: [Slackbuilds-users] Chromium build broken in 14.1

> Well, that's what is available in Slackbuilds for 14.1. I guess that it is > not really maintained anymore :-( Unfortunately no. We simply don't have resources to maintain 2 repositories at the same time. -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature

Re: [Slackbuilds-users] Chromium build broken in 14.1

On Tue, Jan 31, 2017 at 5:12 PM, David O'Shaughnessy wrote: > On 02/01/2017 06:34 AM, JCA wrote: > > I have tried building Chromium for 14.1, using the relevant Slackbuilds > > scripts. > > The chromium version on SBo (31.0.1650.57) was released in late 2013! > (see >

Re: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput

> From your explanation I agree that adding libinput as a required dependency > for qt5 makes sense. I only see these applications that need to be tested > with libinput as a required dep., which also have qt5 as a required dep. > > desktop/compton-conf > network/qbittorrent-qt5 >

Re: [Slackbuilds-users] Chromium build broken in 14.1

On 02/01/2017 06:34 AM, JCA wrote: > I have tried building Chromium for 14.1, using the relevant Slackbuilds > scripts. The chromium version on SBo (31.0.1650.57) was released in late 2013! (see https://chromereleases.googleblog.com/2013/11/stable-channel-update_14.html). I wouldn't touch it;

Re: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput

>>> Installing libinput fixes the stellarium error which then runs normally. >>> I recommend the following: >>> 1. bump stellarium to 0.15.1 >>> 2. mention that libinput is required as a run time dependency. >>> 3. on qt5 page, move libinput to "required" or "optional" as a run time >>>

Re: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput

On Tue, Jan 31, 2017 at 2:36 PM, Willy Sudiarto Raharjo < will...@slackbuilds.org> wrote: > > Installing libinput fixes the stellarium error which then runs normally. > > I recommend the following: > > 1. bump stellarium to 0.15.1 > > 2. mention that libinput is required as a run time

Re: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput

> Installing libinput fixes the stellarium error which then runs normally. > I recommend the following: > 1. bump stellarium to 0.15.1 > 2. mention that libinput is required as a run time dependency. > 3. on qt5 page, move libinput to "required" or "optional" as a run time > dependency for Qt5

Re: [Slackbuilds-users] ftp.kernel.org will shut down at this year

> This still yields zero results on 14.2 but on 14.1 there are two hits. > > kees@pcict9:/var/lib/sbopkg/SBo/14.1$ grep -i 'ftp.*kernel\.org' */*/*.info > graphics/plotutils/plotutils.info:DOWNLOAD="ftp://mirrors.kernel.org/gnu/plotutils/plotutils-2.6.tar.gz; >

[Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput

All: This error keeps popping up here when running Stellarium. - $ stellarium This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb.

[Slackbuilds-users] Stellarium update

Stellarium just needs a minor version bump to 0.15.1. Diff attached. diff --git a/academic/stellarium/stellarium.SlackBuild b/academic/stellarium/stellarium.SlackBuild index 131bf48..6b95d9e 100644 --- a/academic/stellarium/stellarium.SlackBuild +++ b/academic/stellarium/stellarium.SlackBuild @@

[Slackbuilds-users] Chromium build broken in 14.1

I have tried building Chromium for 14.1, using the relevant Slackbuilds scripts. Here is what I am getting: cc '-DANGLE_DX11' '-D_FILE_OFFSET_BITS=64' '-DDISABLE_NACL' '-DCHROMIUM_BUILD' '-DUSE_DEFAULT_RENDER_THEME=1' '-DUSE_LIBJPEG_TURBO=1' '-DUSE_NSS=1' '-DUSE_X11=1'

Re: [Slackbuilds-users] Help needed building pgadmin3

On Tue, 31 Jan 2017, King Beowulf wrote: pgadmin4 is based on QT and uses a completely different build system based on qmake. See build instruction in: https://www.pgadmin.org/download/source4.php The slackbuild for pgadmin3 will not work. Ed, Oh. OK. I have Qt5 (and PyQt5) installed so

Re: [Slackbuilds-users] Help needed building pgadmin3

On 01/31/2017 05:51 AM, Rich Shepard wrote: > On Mon, 30 Jan 2017, King Beowulf wrote: > >> You need to install wxPython (2.8.12) not wxPython3. I suspect you >> installed wxGTK3 (included in wxPython3) and is too new. > > Ed, > > I used to have both wxPython-2.8.12 and wxPython-3.0.2.0

Re: [Slackbuilds-users] Help needed building pgadmin3

On Mon, 30 Jan 2017, King Beowulf wrote: You need to install wxPython (2.8.12) not wxPython3. I suspect you installed wxGTK3 (included in wxPython3) and is too new. Ed, I used to have both wxPython-2.8.12 and wxPython-3.0.2.0 installed. Learning that the latter works with python2 and