[softwaremgmt] Situation and what's expected/needed for 12.3?
Software Center, Appstream, Matthias Klumpp GSoC... I'm lost. First, will any of this be provided as an official update for 12.2 or are we aiming to 12.3? Then do we still have some problems with the packagekit zypp backend and zypp itself? (http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html). Plus it seems there is a need for some changes in the backend with the latest PackageKit (http://blog.tenstral.net/2012/08/appstream-distro-howto.html). Or is Matthias doing that for the zypp backend? So, could somebody please summarize the current situation for openSUSE? If somebody wanted to help, where should he start looking? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On Friday 17 Aug 2012 19:25:13 Cristian Morales Vega wrote:
Software Center, Appstream, Matthias Klumpp GSoC... I'm lost.
First, will any of this be provided as an official update for 12.2 or are we aiming to 12.3? Then do we still have some problems with the packagekit zypp backend and zypp itself? (http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html). Plus it seems there is a need for some changes in the backend with the latest PackageKit (http://blog.tenstral.net/2012/08/appstream-distro-howto.html). Or is Matthias doing that for the zypp backend?
So, could somebody please summarize the current situation for openSUSE? If somebody wanted to help, where should he start looking?
In the early part of the year the Boosters team started working on Software Center/Appstore/Project Brezn stuff, which resulted in some progress on the backend metadata needed to link our OBS with a generic AppStream frontend. However, this effort had to be suspended for 12.2 due to turnover within the team. Matthias submitted and was accepted to do a GSoC to work on AppStream (the fork of Ubuntu Software Center). This is not coordinated with an openSUSE release. I've been trying to sort out the many bugs reported versus Apper for 12.2 and basically they are all bugs in PackageKit or PackageKit's zypp backend common to any PK frontend. As far as I can see nobody has been trying to fix those for 12.2 and I've raised the worst of those (bnc#775651) as a possible ship stopper as it prevents online update using our GUI tools . Gary Lin is trying to help fix the worst of those. In my opinion YaST s/w management and zypper patch/up are the only working ways to update 12.2. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On 18 August 2012 03:34, Will Stephenson <wstephenson@suse.de> wrote:
In the early part of the year the Boosters team started working on Software Center/Appstore/Project Brezn stuff, which resulted in some progress on the backend metadata needed to link our OBS with a generic AppStream frontend. However, this effort had to be suspended for 12.2 due to turnover within the team.
From what I have seen in the 12.2 build logs the metadata is generated correctly, isn't?
Matthias submitted and was accepted to do a GSoC to work on AppStream (the fork of Ubuntu Software Center). This is not coordinated with an openSUSE release.
I just noticed there are two different words, AppStream and Appstore :-p
I've been trying to sort out the many bugs reported versus Apper for 12.2 and basically they are all bugs in PackageKit or PackageKit's zypp backend common to any PK frontend. As far as I can see nobody has been trying to fix those for 12.2 and I've raised the worst of those (bnc#775651) as a possible ship stopper as it prevents online update using our GUI tools . Gary Lin is trying to help fix the worst of those. In my opinion YaST s/w management and zypper patch/up are the only working ways to update 12.2.
Since it seems the problems are mostly in the zypp backend and some changed needed in libzypp I would be mostly interested in that part (perhaps I should write to zypp-devel...). The thing is that since Duncan wrote http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html 9 months aqo I though the problem was being taking care from the zypp/yast team. But after that email I never saw anything else about the topic, and looking at https://github.com/openSUSE/libzypp/commits/master it looks like mlandres is the only one working in libzypp at the moment. Do you know anything about the work of the zypp/yast team (and who composes it) or are you in different offices? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On Thu, Aug 23, 2012 at 10:52:59AM +0100, Cristian Morales Vega wrote:
Since it seems the problems are mostly in the zypp backend and some changed needed in libzypp I would be mostly interested in that part (perhaps I should write to zypp-devel...). The thing is that since Duncan wrote http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html 9 months aqo I though the problem was being taking care from the zypp/yast team.
The main complaint from Duncan is the lock issue. While the rest of the zypp backend is missing a couple of features, it normally does the job.
But after that email I never saw anything else about the topic, and looking at https://github.com/openSUSE/libzypp/commits/master it looks like mlandres is the only one working in libzypp at the moment.
That seems to be the case. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On 23 August 2012 11:13, Michael Schroeder <mls@suse.de> wrote:
On Thu, Aug 23, 2012 at 10:52:59AM +0100, Cristian Morales Vega wrote:
Since it seems the problems are mostly in the zypp backend and some changed needed in libzypp I would be mostly interested in that part (perhaps I should write to zypp-devel...). The thing is that since Duncan wrote http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html 9 months aqo I though the problem was being taking care from the zypp/yast team.
The main complaint from Duncan is the lock issue. While the rest of the zypp backend is missing a couple of features, it normally does the job.
So, there is a list of operations that should be lock-free and currently aren't? Somebody is working on it? If someone wanted to work on it now should he coordinate with somebody? Same about the zypp backend. Anybody looking at it?
From http://gitorious.org/packagekit/packagekit/blobs/master/backends/PORTING.txt is seems it would be good if libzypp would be thread-safe. It's the case? If not, could be done in a reasonably time or it would be way too much work? From the git commit log it looks the only one doing any work on it is the PackageKit main developer. Somebody has something done in private? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On Thu, Aug 23, 2012 at 11:49:07AM +0100, Cristian Morales Vega wrote:
So, there is a list of operations that should be lock-free and currently aren't? Somebody is working on it?
Uh, I don't know (I'm not a member of the zypp team). I think Michael Andres did some work to fix the lock issue but I don't know the current state.
If someone wanted to work on it now should he coordinate with somebody?
Yes, coordinate with zypp-devel
Same about the zypp backend. Anybody looking at it?
From http://gitorious.org/packagekit/packagekit/blobs/master/backends/PORTING.txt is seems it would be good if libzypp would be thread-safe. It's the case? If not, could be done in a reasonably time or it would be way too much work?
Thread safe? I don't think that's really needed. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On 23 August 2012 12:50, Michael Schroeder <mls@suse.de> wrote:
On Thu, Aug 23, 2012 at 11:49:07AM +0100, Cristian Morales Vega wrote:
Same about the zypp backend. Anybody looking at it?
From http://gitorious.org/packagekit/packagekit/blobs/master/backends/PORTING.txt is seems it would be good if libzypp would be thread-safe. It's the case? If not, could be done in a reasonably time or it would be way too much work?
Thread safe? I don't think that's really needed.
I didn't look into the details, just read this in the backend porting guide to 0.8.x: "Make your backend is threadsafe, so tasks can be executed in parallel. If your package manager is not threadsafe, create a new process and do IPC from the main thread, or - if possible - change your package manager to be threadsafe." Not needed, but good to have to avoid the fork()/exec() and IPC. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On Thu, Aug 23, 2012 at 01:01:38PM +0100, Cristian Morales Vega wrote:
I didn't look into the details, just read this in the backend porting guide to 0.8.x: "Make your backend is threadsafe, so tasks can be executed in parallel. If your package manager is not threadsafe, create a new process and do IPC from the main thread, or - if possible - change your package manager to be threadsafe."
Not needed, but good to have to avoid the fork()/exec() and IPC.
Yes, but that's probably easier than making libzypp thread safe if it wasn't designed with that goal in mind. (But maybe it is already thread safe.) M. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
On 18 August 2012 03:34, Will Stephenson <wstephenson@suse.de> wrote:
I've been trying to sort out the many bugs reported versus Apper for 12.2 and basically they are all bugs in PackageKit or PackageKit's zypp backend common
Do you know about this? I run pkmon and went to System Settings -> Software Management -> Updates. I got two transactions, get-updates and get-distro-upgrades. Then I click on "Check for new Updates" and I get a "refresh-cache" followed of one get-updates and TWO get-distro-upgrades. When going to System Settings -> Software Management -> Installed Software -> Settings I get TWO "get-repo-list" transactions. It's normal, a bug that you found is in PackageKit or PackageKit's zypp backend or a bug that you never saw before? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-softwaremgmt+owner@opensuse.org
participants (3)
-
Cristian Morales Vega -
Michael Schroeder -
Will Stephenson