-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 01 Mar 2018 01:37:16 +0300
Source: qconf
Binary: qconf
Architecture: source
Version: 2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt extras Maintainers
Changed-By: Boris Pek
Description:
qconf - nice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 27 Feb 2018 00:53:35 +0300
Source: qconf
Binary: qconf
Architecture: source amd64
Version: 2.4-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Boris Pek
Changed-By: Boris Pek
Description:
qconf
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=374046
> I don't think there is anything to be discussed actually.
>
> After closer studying of the latest upstream sources of QtCurve it
> appears same exact bug was submitted a while back to them. Same exact
> patch was committed to the
Hi Sergey,
> Patch had some malformed header (was mixing information from previous
> maintainer patch and residue of some older description). Here is an
> updated patch with hopefully all headers filled correct.
>
> Hopefully this one will work fine :)
Please discuss this patch with QtCurve devel
Hi Dmitry,
> On Fri, Jul 07, 2017 at 05:18:41PM +0300, Dmitry Shachnev wrote:
>> qtcurve fails to build with Qt 5.9 (available in experimental):
>>
>> [...]
>>
>> This upstream commit fixes this failure:
>> https://cgit.kde.org/qtcurve.git/commit/?id=7ddd3782ea5635cc
>
> I have now committed t
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: tehn...@debian.org, pkg-kde-extras@lists.alioth.debian.org
Hi FTP masters,
xembedsniproxy module was included into plasma-workspace since 5.5.0 release
and plasma-workspace/4:5.6.4-2 is already in testing, so a separate package
is not require
>> This is a wrong assumption, just look at directory access permissions:
>>
>> $ LC_ALL=C ls -alp ~/.config/ | grep '\./'
>> drwx-- 96 user user 4096 Nov 28 23:44 ./
>> drwx-- 192 user user 12288 Nov 28 22:39 ../
>
> Mine are not the same:
>
> diederik@bagend:~$ LC_ALL=C ls -alp ~/.con
Hi,
> As I was trying to setup CertFP I had a look at
> ~/.config/quassel-irc.org and noticed the following:
> -rw-r--r-- 1 diederik diederik 8101 nov 28 03:01 quasselclient.conf
>
> Looking into that file I could easily see my password and that combined
> with the security settings of that file d
Hi,
Could you check if your bugs are still present in
plasma-systray-legacy/0~git20151104-ded1538-1 ?
Best regards,
Boris
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg
control: forcemerge 793869 793890
Hi,
> The package fails to install, due to a file conflict with
> libqtcurve-utils2:
>
> Preparing to unpack
> .../libqtcurve-utils1_1.8.18+git20150711-a3fff13-2_amd64.deb ...
> Unpacking libqtcurve-utils1:amd64 (1.8.18+git20150711-a3fff13-2) ...
> dpkg: error p
Hi,
> This is solvable by removing kde-style-qtcurve.
>
> Then libqtcurve-utils1 is not required as kde-style-qtcurve-qt5 requires
> libqtcurve-utils2.
>
> Maybe kde-style-qtcurve needs to be recompiled with libqtcurve-utils2 as well,
> or is it obsoleted by kde-style-qtcurve-qt5?
Please read cha
Hi,
> However, doesn't your patch now skip the first line of the file?
Now fixed. Thanks.
Best regards,
Boris
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
Hi,
> this bug actually had already been fixed upstream when I reported it, it
> just hasn't been merged to master:
> https://projects.kde.org/projects/extragear/base/kde-gtk-config/repository/revisions/8f23071c6e7719970be9383246df8f321131048b
> Another bug concerning mis-matched boolean configura
Hi,
> There is no such package in repository (kde-config-gtk-style), at least
> at testing branch.
You could help Release Team to make decision about including it into Wheezy:
http://bugs.debian.org/685456
> Even if we will have such package, we should to put
> it to "gtk2-engines-*" dependenc
Hi,
> the [1] patch is not really useful. It's removing symlinks but it's
> not harmful to follow them in this case. It's not a
> recursive/iterative function so it's harmless. It shouldn't be
> applied.
Yes, you are right. I made test sample and checked it.
So the first point in this bug report
> Git commit 81b7e1e43e5fce39ace676ef40637059b9bb9317 by Aleix Pol.
> Committed on 11/07/2012 at 13:29.
> Pushed by apol into branch 'master'.
>
> Fix freezing problem on load
>
> Don't iterate over the home directory, this happened in cases
> where the fallback icon theme was set to "" and Qt tran
Hi,
I have prepared a patch for ignoring symlinks. But I need more info about your
second point.
Program don't scan user's home directory, but only ~/.themes/ subdirectory.
So I think the problem is related with symlinks. Could you check it please?
Also strace log can be helpful. Because I have
Hi,
>> It looks like Wheeze will be without this package.
>
> Not necessarily. As far as I can read the release.debian.org hints, 2.0-3 has
> been hinted to migrate despite the freeze. So I think we can safely assume
> that a fixed 2.0-3 could pass the freeze.
I have asked release team about thi
Hi,
> sorry, the freeze caught us. Please head to debian-release to ask for a freeze
> exception (I suspect you might need to only backport the needed patch to the
> version actually in testing). I'll sponsor the package iff the freeze
> exception is granted.
The package is not in testing:
http
Hi,
I have updated the package:
kde-gtk-config (3:2.1-1) unstable; urgency=low
* Update to stable release 2.1.
* Deleted file debian/patches/fix-build-on-kfreebsd-and-hurd-i386:
accepted in upstream.
* Added file debian/patches/ignore-symlinks:
prevents of possible infinite loop be
Hi,
> Yes. Uploaded now; thanks for your work.
Thanks a lot!
> That said, I take as granted that you'll followup bugreports and eventual
> issues that might arise with kde-gtk-config now in unstable or later in
> testing and then as stable.
Yes, of course, this is my package and I will maintain
experimental
2012-06-08 11:29, Boris Pek wrote:
> Hi,
>
> Now package builds fine on kfreebsd-* and hurd-i386:
> https://buildd.debian.org/status/package.php?p=kde-gtk-config&suite=experimental
>
> And it should be no problems with linux-based environments on other su
Hi,
Now package builds fine on kfreebsd-* and hurd-i386:
https://buildd.debian.org/status/package.php?p=kde-gtk-config&suite=experimental
And it should be no problems with linux-based environments on other supported
architectures. So I have updated the package:
kde-gtk-config (3:2.0-3) unstab
Hi,
I have updated the package:
kde-gtk-config (3:2.0-2) experimental; urgency=low
* Added file debian/patches/fix-build-on-kfreebsd-and-hurd-i386:
fixes FTBFS in Debian GNU/kFreeBSD and in Debian GNU/Hurd.
Could you upload it?
Direct link for download:
http://mentors.debian.net/debian
Hi,
> src:kcm-gtk is available on all Debian architectures where src:kde-
> gtk-config at least failed on hurd and kfreebsd with the following error:
>
> …/kde-gtk-config-2.0/gtk3proxies/preview3.c:28:25: fatal error: sys/inotify.h:
> No such file or directory
>
> See https://buildd.debian.org/sta
Hi,
> Uploaded; thanks for your work. It will land in NEW for experimental later
> tonight.
>
> ftpmaster: for your information, src:kde-gtk-config takes over the kde-config-
> gtk-style binary package from src:kcm-gtk on purpose. This has been discussed
> in the #672268 ITP bugreport and on the d
Hi,
> Sorry, but no. I just tested and it doesn't work.
>
> With the attached .gtkrc-2.0-kde as created by the current src:kcm-gtk, when
> entering the dialog of src:kde-gtk-config, the dialogs don't show "Raleigh"
> nor "DejaVu Sans 9", but "oxygen-gtk" and "Bitstream Charter 12" (and "Emacs"
> f
Hi,
> Sorry, but no. I just tested and it doesn't work.
>
> With the attached .gtkrc-2.0-kde as created by the current src:kcm-gtk, when
> entering the dialog of src:kde-gtk-config, the dialogs don't show "Raleigh"
> nor "DejaVu Sans 9", but "oxygen-gtk" and "Bitstream Charter 12" (and "Emacs"
> f
Hi,
Thank you for a reply.
> 2) Handling of the transition
>
> I just tested with a clean user: the current kde-config-gtk-style creates one
> .gtkrc-2.0-kde while your new kde-config-gtk-style creates one .gtkrc-2.0-kde4
> that is a symlink to .gtkrc-2.0 . You should probably cope with
> 04_no_
Hi,
Thank you for a reply.
>> We are talking about replacing the package kcm-gtk by package
>> kde-gtk-config which has wider functionality.
> That's debatable.
I can't agree with you: kde-gtk-config has wider functionality objectively.
As I wrote earlier, kcm-gtk does not allow to:
* sele
Sorry for a broken message. Here is the correct one:
Hi,
You could read the beginning of this thread:
https://lists.debian.org/debian-mentors/2012/05/threads.html#00115
(Please Cc me in replies, I am not subscribed to pkg-kde-extras mailing list)
>> kde-config-gtk-style does not allow to:
>>
Hi,
You could read the beginning of this thread:
https://lists.debian.org/debian-mentors/2012/05/threads.html#00115
(Please Cc me in replies, I am not subscribed to pkg-kde-extras mailing list)
>> kde-config-gtk-style does not allow to:
>> * select themes for Gtk 3.x applications
>> * preview
Hi,
I am looking for a sponsor for updated packages "gtk2-engines-qtcurve" and
"kde-style-qtcurve". Packages were orphaned and I intend to maintain them.
Packages in m.d.n:
http://mentors.debian.net/package/gtk2-engines-qtcurve
http://mentors.debian.net/package/kde-style-qtcurve
Direct links
33 matches
Mail list logo
