hi
would it be possible to get this fixed in fedora because upstream nobody cares since a very long time?
On 09/21/2011 05:57 AM, Reindl Harald wrote:
hi
would it be possible to get this fixed in fedora because upstream nobody cares since a very long time?
How would Fedora fix it? They just package the upstream source.
https://bugs.kde.org/show_bug.cgi?id=270414
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Am 21.09.2011 11:44, schrieb Patrick Boutilier:
On 09/21/2011 05:57 AM, Reindl Harald wrote:
hi
would it be possible to get this fixed in fedora because upstream nobody cares since a very long time?
How would Fedora fix it? They just package the upstream source
the same way as in thousands of other packages / spec-files patches are included? since this bug is stable over months and major-releases a patch for it would also and the patch could go upstream
i am not able to fix this, upstream is too stupid to recognize how bad reputation such things are introducing for the whole KDE - what should a new user think if the main-desktop is too stupid for a simple file-rename?
Am 21.09.2011 11:44, schrieb Patrick Boutilier:On 09/21/2011 05:57 AM, Reindl Harald wrote:
hi
would it be possible to get this fixed in fedora because upstream nobody cares since a very long time?
How would Fedora fix it? They just package the upstream source.
why do you think they only fire the upstream-source to the compiler? below the patches only for "kdenase-4.7.1" (you can look at the SPEC-file) http://kojipkgs.fedoraproject.org/packages/kdebase/4.7.1/1.fc16/src/kdebase-...
# search path for plugins Patch0: kdebase-4.1.80-nsplugins-paths.patch # make menuitem Home visible Patch2: kdebase-4.2.1-home-icon.patch # fix disabling automatic spell checking in the Konqueror UI (kde#228593) Patch3: kdebase-4.4.0-konqueror-kde#228593.patch # Password & User account becomes non responding Patch4: kdebase-4.3.4-bz#609039-chfn-parse.patch
On 09/21/2011 06:55 AM, Reindl Harald wrote:
Am 21.09.2011 11:44, schrieb Patrick Boutilier:On 09/21/2011 05:57 AM, Reindl Harald wrote:
hi
would it be possible to get this fixed in fedora because upstream nobody cares since a very long time?
How would Fedora fix it? They just package the upstream source.
why do you think they only fire the upstream-source to the compiler?
Maybe nobody wants to fix it?
below the patches only for "kdenase-4.7.1" (you can look at the SPEC-file) http://kojipkgs.fedoraproject.org/packages/kdebase/4.7.1/1.fc16/src/kdebase-...
# search path for plugins Patch0: kdebase-4.1.80-nsplugins-paths.patch # make menuitem Home visible Patch2: kdebase-4.2.1-home-icon.patch # fix disabling automatic spell checking in the Konqueror UI (kde#228593) Patch3: kdebase-4.4.0-konqueror-kde#228593.patch # Password& User account becomes non responding Patch4: kdebase-4.3.4-bz#609039-chfn-parse.patch
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Am 21.09.2011 11:57, schrieb Patrick Boutilier:
On 09/21/2011 06:55 AM, Reindl Harald wrote:
Am 21.09.2011 11:44, schrieb Patrick Boutilier:On 09/21/2011 05:57 AM, Reindl Harald wrote:
hi
would it be possible to get this fixed in fedora because upstream nobody cares since a very long time?
How would Fedora fix it? They just package the upstream source.
why do you think they only fire the upstream-source to the compiler?
Maybe nobody wants to fix it?
congratulations - somebody was touching code without understand what doing, without testing, without using the desktop, the other upstream developers seems also not using the desktop and nobdy WANTS to get this fixed?
so they should not touch working things if they do not want to fix what they break - in the year 2011 such error-messages while doing a basic-operation like rename a file are simply laughable
Am 21.09.2011 14:56, schrieb Markus Slopianka:
On Mittwoch 21 September 2011 11:44:56 Patrick Boutilier wrote:
How would Fedora fix it?
One possibility would be by letting one of Red Hat's paid employees with upstream KDE commit rights write a fix.
after rantig on the kde-devel list and get multiple "fix it by yourself" it was found out that the maintainer of this code has orphaned it and some minutes ago a fix has gone into 4.7 trunk
On St 21. září 2011 15:08:53 Reindl Harald wrote:
Am 21.09.2011 14:56, schrieb Markus Slopianka:
On Mittwoch 21 September 2011 11:44:56 Patrick Boutilier wrote:
How would Fedora fix it?
One possibility would be by letting one of Red Hat's paid employees with upstream KDE commit rights write a fix.
after rantig on the kde-devel list and get multiple "fix it by yourself" it was found out that the maintainer of this code has orphaned it and some minutes ago a fix has gone into 4.7 trunk
Seeing this has been committed to 4.7 branch only today, you can expect the fix to land in KDE 4.7.2
On 09/21/2011 08:20 AM, Lukáš Tinkl wrote:
On St 21. září 2011 15:08:53 Reindl Harald wrote:
Am 21.09.2011 14:56, schrieb Markus Slopianka:
On Mittwoch 21 September 2011 11:44:56 Patrick Boutilier wrote:
How would Fedora fix it?
One possibility would be by letting one of Red Hat's paid employees with upstream KDE commit rights write a fix.
after rantig on the kde-devel list and get multiple "fix it by yourself" it was found out that the maintainer of this code has orphaned it and some minutes ago a fix has gone into 4.7 trunk
Seeing this has been committed to 4.7 branch only today, you can expect the fix to land in KDE 4.7.2
And, ta da, just pulled it into kdebase-4.7.1-2 packaging
-- rex
Am 21.09.2011 15:29, schrieb Rex Dieter:
after rantig on the kde-devel list and get multiple "fix it by yourself" it was found out that the maintainer of this code has orphaned it and some minutes ago a fix has gone into 4.7 trunk https://bugs.kde.org/show_bug.cgi?id=270414#c43
Seeing this has been committed to 4.7 branch only today, you can expect the fix to land in KDE 4.7.2
And, ta da, just pulled it into kdebase-4.7.1-2 packaging
thank you!
Reindl Harald wrote:
Am 21.09.2011 15:29, schrieb Rex Dieter:
after rantig on the kde-devel list and get multiple "fix it by yourself" it was found out that the maintainer of this code has orphaned it and some minutes ago a fix has gone into 4.7 trunk https://bugs.kde.org/show_bug.cgi?id=270414#c43
Seeing this has been committed to 4.7 branch only today, you can expect the fix to land in KDE 4.7.2
And, ta da, just pulled it into kdebase-4.7.1-2 packaging
thank you!
I have to say the followups on the upstream mailing list and this bug report make me one sad panda.
-- rex
Am 21.09.2011 19:37, schrieb Rex Dieter:
Reindl Harald wrote:
Am 21.09.2011 15:29, schrieb Rex Dieter:
after rantig on the kde-devel list and get multiple "fix it by yourself" it was found out that the maintainer of this code has orphaned it and some minutes ago a fix has gone into 4.7 trunk https://bugs.kde.org/show_bug.cgi?id=270414#c43
Seeing this has been committed to 4.7 branch only today, you can expect the fix to land in KDE 4.7.2
And, ta da, just pulled it into kdebase-4.7.1-2 packaging
thank you!
I have to say the followups on the upstream mailing list and this bug report make me one sad panda.
get "why haven't you fixed it in the last six months. If you don't know how, why haven't you learned?" as first reply of the first mail to the upstream list in the hope anybody will take notice of this bug me too
answers like "why do you not fix it", "learn to fix it", "this is free software, fix it by yourself" are not helpful for open-source software at all and i read such answers way too much the last years to calm down after that
-
Lukáš Tinkl -
Markus Slopianka -
Patrick Boutilier -
Reindl Harald -
Rex Dieter