Package Details: pkgbrowser 0.28.1-4

Git Clone URL: https://aur.archlinux.org/pkgbrowser.git (read-only, click to copy)
Package Base: pkgbrowser
Description: A utility for browsing pacman databases and the AUR
Upstream URL: https://codeberg.org/kachelaqa/pkgbrowser
Licenses: GPL2
Submitter: kachelaqa
Maintainer: kachelaqa
Last Packager: kachelaqa
Votes: 283
Popularity: 0.78
First Submitted: 2011-04-20 18:18 (UTC)
Last Updated: 2024-12-23 20:29 (UTC)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 20 Next › Last »

OldNuc commented on 2017-01-06 14:16 (UTC)

latest upgrade of python to 3.6.0-1 breaks pkgbrowser dependency 'python<3.6'

biloucat commented on 2017-01-06 09:20 (UTC)

python 3.6 is out so python<3.6 fail

ackalker commented on 2016-08-20 04:05 (UTC) (edited on 2016-08-20 05:07 (UTC) by ackalker)

@kachelaqa Still doesn't explain why something like pyqt's examples/itemviews/dirview.py has no problems but pkgbrowser does. Could it be that of all pkgbrowser's widgets, only the Packages pane QTreeView has a "styleSheet" property? EDIT: Yup :-) removing the "styleSheet" property 'fixes' the problem when using QT_QPA_PLATFORMTHEME="qt5ct". Anyway, I've resolved it (somewhat) by switching from using QT_QPA_PLATFORMTHEME="qt5ct" and setting "gtk2" in qt5ct to using just QT_STYLE_OVERRIDE="gtk2". Why this works is a mystery to me (and qt5ct complains LOUDLY about me using QT_STYLE_OVERRIDE), but anyway, let's savour the great joys of framework API and configuration transitions...

kachelaqa commented on 2016-08-20 03:43 (UTC)

@ackalker. This has got nothing to do with pkgbrowser. It's most likely due to a bug in qt and/or a style plugin.

ackalker commented on 2016-08-20 02:59 (UTC) (edited on 2016-08-20 03:32 (UTC) by ackalker)

Also tested with BlackMATE and ContrastHighInverse themes from mate-themes package: same problem, so it doesn't appear to be a problem with one specific dark theme. Even tried building pyqt from [testing] to get pyqt5-common,python-pyqt5 5.7-2, then rebuilding(!) and reinstalling pkgbrowser: no dice, same problem. Sigh.

ackalker commented on 2016-08-20 02:15 (UTC) (edited on 2016-08-20 03:39 (UTC) by ackalker)

Using a dark theme (Breeze-Dark), qt5ct and qt5-styleplugins to match GTK+ and QT themes, when I start pkgbrowser: - the package list pane initially has a white background while everything else is dark as it should be. - on listing some packages (e.g. clicking "Installed" in filter), the package list text color is black on a dark background: very hard to read. - with a package listing in place, there's a white vertical bar in front of the column with package names, also the scrollbars are white. When I open the file designer/window.ui in Qt Designer, I see none of these problems. Also, none of the PyQT examples with QTreeView's in them have any of these problems. Steps to reproduce (making sure not to complicate things with personal theme configs etc. getting in the way): - In X, but not running KDE (I'm using SDDM display manager, i3 window manager) - Have the following packages installed (all official, unless indicated otherwise): pkgbrowser 0.20-1 (build from AUR) pacman 5.0.1-4 python 3.5.2-1 python-pyqt5 5.6-1 qt5-styleplugins 5.0.0-1 (build from AUR) qt5ct 0.25-1 breeze-gtk 5.7.3-1 - In a terminal window, execute the following commands: $ rm -rf ~/tmp/test; mkdir -p ~/tmp/test $ env -i HOME=~/tmp/test DISPLAY=:0 XAUTHORITY=~/.Xauthority QT_QPA_PLATFORMTHEME="qt5ct" GTK2_RC_FILES=/usr/share/themes/Breeze-Dark/gtk-2.0/gtkrc qt5ct - In qt5ct, under Appearance, select "gtk2", dark theme should be visible in Preview pane. - In qt5ct, click Apply, OK, - Finally, in a terminal window execute: $ env -i HOME=~/tmp/test DISPLAY=:0 XAUTHORITY=~/.Xauthority QT_QPA_PLATFORMTHEME="qt5ct" GTK2_RC_FILES=/usr/share/themes/Breeze-Dark/gtk-2.0/gtkrc pkgbrowser

kachelaqa commented on 2016-03-23 17:44 (UTC)

@Thah. See my comment on 2015-02-07 17:57.

Thah commented on 2016-03-23 08:25 (UTC) (edited on 2016-03-23 08:26 (UTC) by Thah)

The build error below is probably due to /bin/sh being linked to a not-Bash shell, e.g. Dash; see my comment on 2015-02-07 09:36: Make uses /bin/sh as a shell which only guaranties POSIX compliance. The makefile uses bash extension(s). See my previous comment for a workaround/fix. Version 0.20-1 compiles fine under Dash but 'make install' still needs Bash. checkbashisms reports possible problems with brace expansions.

kachelaqa commented on 2016-02-16 18:45 (UTC)

@jefbed. I can't reproduce this - it all works fine for me. The problem must at your end. Are you using an aur helper programme?

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 20 Next › Last »