Le lundi 25 janvier 2010, à 13:09 +0100, Marcus Meissner a écrit :

On Mon, Jan 25, 2010 at 12:13:19PM +0100, Vincent Untz wrote:

...

Hi,

Looking at the git log from PackageKit, it looks like Scott managed to fix the build of the zypp backend -- which was the reason we were stuck with an old PackageKit (0.5.1).

So we'll put the next release of PackageKit in Factory (0.6.1, due next week, I think). Note that this changes the API (at least deprecated API were removed) and therefore will possibly break tools using PackageKit that were not prepared for this. You can take a look at the NEWS file for more details: http://cgit.freedesktop.org/packagekit/tree/NEWS

As far as I know, there are two major consumers of PackageKit: gnome-packagekit (which should be fine) and the KDE update applet (no idea what the status is here).

Is it an option to not update PackageKit? Not really: the version we have is old, not really maintained, and my guess is that we'll soon have tools that will require the new stuff there.

Actually the one who breaks stuff should fix it...

I'm sorry, but at some point, this doesn't work: if we're working together, there are changes that, if announced, we can work together on. That's actually why we decided to send here announcements that might affect various people. And it's fine for people to reply to such an announcement with "okay, but can we wait $n_weeks so I can do $task?" or "hrm, I think it's a bad thing because..."

Or at least evaluate on what breaks before the update (in a test project).

Let me update my evaluation which was already in the mail. Three packages are affected as far as I can tell (I missed kpackagekit in my previous mail): + gnome-packagekit: should be fine after it's updated (the GNOME team will take care of it) + kpackagekit: needs to be updated. There's a 0.5.4 tarball which might work; if not, Fedora ships a snapshot from git right now, so we can take this. (Fedora had 0.5.2 before the git snapshot, so it means nothing about 0.5.4) + kupdateapplet: uses the PackageKit dbus interface, so will build. No idea if it will work fine, though: someone needs to look at the dbus API that is used there. And since we are upstream for this, I'd expect the right people to tell us if the PackageKit update can be an issue. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org