Bug 254693 - I can't provide updated Debian packages
Summary: I can't provide updated Debian packages
Status: RESOLVED NOT A BUG
Alias: None
Product: kwebkitpart
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: webkit-devel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-19 21:42 UTC by Adrian von Bidder
Modified: 2010-10-21 12:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian von Bidder 2010-10-19 21:42:23 UTC
Version:           unspecified (using KDE 4.5.2) 
OS:                Linux

Heyho!

Way to go, woebbe.  It would really be great if I could update the kpart-webkit Debian package.  It would get you more than >100 [1] additional testers  (difficult to judge.  popcon sets a lower boundary, but how many haven't installed popcon?)

So I hope a way can be found to keep backward compatible.  Note that although Debian squeeze and sid only contain KDE 4.4.5, I'd already be happy for compatibility with 4.5.2 which is ready in the KDE team's uber-experimental repository.

http://qa.debian.org/popcon-graph.php?packages=kpart-webkit

(Actually, what would be great would be a commitment to stay compatible with the latest released KDE version.)

Reproducible: Didn't try
Comment 1 Jonathan Thomas 2010-10-19 23:31:13 UTC
Please report this to Debian's bugtracker at http://www.debian.org/Bugs/
Comment 2 Adrian von Bidder 2010-10-20 15:46:40 UTC
Excuse me?

*If* webkitpart's source were compatible with currently released kdelibs, I would very much like to update the kpart-webkit package.  So my request to the webkitkde developers is: please keep compatibility at least with the most recent released version of KDE.

woebbe has tried to do this, and I would very much encourage him to to do this.  I very much doubt that openong a debian.org bug report would be read by anybody except myself, and I already know that I don't know enough about KDE's API to do this work myself.  I have talked with the Debian package maintainer of the kpart-webkit (source package name webkitkde) Debian package and he very much agrees with me.
Comment 3 Dawit Alemayehu 2010-10-20 21:58:54 UTC
(In reply to comment #2)
> Excuse me?
> 
> *If* webkitpart's source were compatible with currently released kdelibs, I
> would very much like to update the kpart-webkit package.  So my request to the
> webkitkde developers is: please keep compatibility at least with the most
> recent released version of KDE.
>
> woebbe has tried to do this, and I would very much encourage him to to do this.
>  I very much doubt that openong a debian.org bug report would be read by
> anybody except myself, and I already know that I don't know enough about KDE's
> API to do this work myself.  I have talked with the Debian package maintainer
> of the kpart-webkit (source package name webkitkde) Debian package and he 
> very much agrees with me.

The stable version of kwebkitpart packages for the current KDE stable release of KDE are located here:

http://websvn.kde.org/branches/stable/extragear-kde4/base/kwebkitpart/

There was no implicit or explicit guarantee given for the trunk version of kwebkitpart to work with the current stable KDE releases. It just happened to be that way until recently because I was nice enough to #ifdef code out. However, that has quickly become a maintianence nightmare ; so now I have put the stable version for the current release (with updates for necessary bug fixes) in the repo shown above.
Comment 4 Jonathan Thomas 2010-10-20 23:29:53 UTC
To my credit, no reason as to why the package couldn't be updated were given. It looked like you were just requesting for a packaging update.
Comment 5 Adrian von Bidder 2010-10-21 09:37:08 UTC
Dawit, thanks for the explanation & the link to the stable tree (which I hadn't discovered, my fault.)

Jonathan, ok, on second reading my original message was indeed a bit ... shall we say cryptic? ;-)
Comment 6 Jonathan Thomas 2010-10-21 12:58:29 UTC
No hard feelings. :)
It was perhaps a hasty closing on my part. (Though I think it really should remain closed. But at the least, it's not Debian's fault, so at best this is invalid.