[opensuse-factory] openSUSE Tumbleweed status for the week of April 9, 2011
Here's a short note as to the status of some recent activity in the openSUSE:Tumbleweed repo: - the kernel is at the 2.6.38 release level - a number of multimedia packages and libraries were updated to their Factory level - Banshee 2 is now in the repository - LibreOffice 3.3.2 is in the repository. - I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough. Note, it seems that when _any_ package is added or updated in the openSUSE:Tumbleweed repository, LibreOffice rebuilds itself. This can be annoying for those on bandwidth-challenged network connections, and seems to be due to the dependency chain that the LibreOffice developers have defined in their .spec files. Hopefully this will be resolved for the next major release, but in the meantime, I'll try to limit library updates in openSUSE:Tumbleweed to once a week at the most unless security issues require it. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/10/2011 02:30 AM, Greg KH wrote:
Here's a short note as to the status of some recent activity in the openSUSE:Tumbleweed repo:
- the kernel is at the 2.6.38 release level - a number of multimedia packages and libraries were updated to their Factory level
Hi, thanks for all the work. Could you link unison package (network project)?
Note, it seems that when _any_ package is added or updated in the openSUSE:Tumbleweed repository, LibreOffice rebuilds itself.
Have you considered direct dependency building rule instead of transitive? Or do the packages depend directly on the libraries you are adding? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Apr 10, 2011 at 03:08:33PM +0200, Jiri Slaby wrote:
On 04/10/2011 02:30 AM, Greg KH wrote:
Here's a short note as to the status of some recent activity in the openSUSE:Tumbleweed repo:
- the kernel is at the 2.6.38 release level - a number of multimedia packages and libraries were updated to their Factory level
Hi, thanks for all the work.
Could you link unison package (network project)?
Sure, it's now added.
Note, it seems that when _any_ package is added or updated in the openSUSE:Tumbleweed repository, LibreOffice rebuilds itself.
Have you considered direct dependency building rule instead of transitive? Or do the packages depend directly on the libraries you are adding?
I don't think that libreoffice directly depends on stuff like samba, but updating it causes a rebuild. Feel free to take a look at it if you are curious, the LibreOffice developers said they are working on it so I trust them. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/10/2011 05:22 PM, Greg KH wrote:
I don't think that libreoffice directly depends on stuff like samba, but updating it causes a rebuild.
Yes, OBS by default computes a transitive closure of dependencies. And rebuilds everything what transitively depends on something what has changed. If you don't want this default behaviour, you may use rebuild="direct" or rebuild="local". This was changed also in factory to not rebuild everything after Kay Sievers complained in one of the discussions. For how to do it, you may take a look at output of osc meta prj openSUSE:Factory and search for 'rebuild='. Note that this may not rebuild things and break the system for some weird cornercases. But everything should rpm-depend directly on packages which it really depends on, so rebuild="direct" should be safe. I don't remember any breakage in factory since this was turned on. And Factory uses even more conservative "local" option -- rebuild a package if and only if sources of the particular package change.
Feel free to take a look at it if you are curious, the LibreOffice developers said they are working on it so I trust them.
I don't know what is the real problem here. Maybe there will change the dependency on the samba library? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/10/2011 05:47 PM, Jiri Slaby wrote:
On 04/10/2011 05:22 PM, Greg KH wrote:
I don't think that libreoffice directly depends on stuff like samba, but updating it causes a rebuild.
Yes, OBS by default computes a transitive closure of dependencies. And rebuilds everything what transitively depends on something what has changed. If you don't want this default behaviour, you may use rebuild="direct" or rebuild="local".
It just reminded me that there was a documentation. And I found it at: http://en.opensuse.org/openSUSE:Build_Service_Concept_build_scheduling_strat... regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Apr 10, 2011 at 05:50:32PM +0200, Jiri Slaby wrote:
On 04/10/2011 05:47 PM, Jiri Slaby wrote:
On 04/10/2011 05:22 PM, Greg KH wrote:
I don't think that libreoffice directly depends on stuff like samba, but updating it causes a rebuild.
Yes, OBS by default computes a transitive closure of dependencies. And rebuilds everything what transitively depends on something what has changed. If you don't want this default behaviour, you may use rebuild="direct" or rebuild="local".
It just reminded me that there was a documentation. And I found it at: http://en.opensuse.org/openSUSE:Build_Service_Concept_build_scheduling_strat...
Thanks, I'll remember that for the future. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Apr 10, 2011 at 05:47:03PM +0200, Jiri Slaby wrote:
Note that this may not rebuild things and break the system for some weird cornercases. But everything should rpm-depend directly on packages which it really depends on, so rebuild="direct" should be safe. I don't remember any breakage in factory since this was turned on. And Factory uses even more conservative "local" option -- rebuild a package if and only if sources of the particular package change.
Such cases are fixed behind our backs usually. Coolo does much of selective rebuild triggers when necessary. Also factory has way more cycles than in previous days now, some quality drops were taken. And transitive closure is an advantage for integrity ... :/ Tumbleweed however as a post-released product does not necessarily need it, but for some base changes it should be done at least once. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Apr 10, 2011 at 07:09:58PM +0200, Marcus Meissner wrote:
On Sun, Apr 10, 2011 at 05:47:03PM +0200, Jiri Slaby wrote:
Note that this may not rebuild things and break the system for some weird cornercases. But everything should rpm-depend directly on packages which it really depends on, so rebuild="direct" should be safe. I don't remember any breakage in factory since this was turned on. And Factory uses even more conservative "local" option -- rebuild a package if and only if sources of the particular package change.
Such cases are fixed behind our backs usually. Coolo does much of selective rebuild triggers when necessary. Also factory has way more cycles than in previous days now, some quality drops were taken.
And transitive closure is an advantage for integrity ... :/
Tumbleweed however as a post-released product does not necessarily need it, but for some base changes it should be done at least once.
Yeah, for that reason I think I'll stick to the default we have now to be on the "safe" side. Especially when we start updating libraries, like we are now doing. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
At Sun, 10 Apr 2011 11:48:37 -0700, Greg KH wrote:
On Sun, Apr 10, 2011 at 07:09:58PM +0200, Marcus Meissner wrote:
On Sun, Apr 10, 2011 at 05:47:03PM +0200, Jiri Slaby wrote:
Note that this may not rebuild things and break the system for some weird cornercases. But everything should rpm-depend directly on packages which it really depends on, so rebuild="direct" should be safe. I don't remember any breakage in factory since this was turned on. And Factory uses even more conservative "local" option -- rebuild a package if and only if sources of the particular package change.
Such cases are fixed behind our backs usually. Coolo does much of selective rebuild triggers when necessary. Also factory has way more cycles than in previous days now, some quality drops were taken.
And transitive closure is an advantage for integrity ... :/
Tumbleweed however as a post-released product does not necessarily need it, but for some base changes it should be done at least once.
Yeah, for that reason I think I'll stick to the default we have now to be on the "safe" side. Especially when we start updating libraries, like we are now doing.
I think you can enable the automatic rebuilds in Tumbleweed:Test repo for integrity tests while the manual rebuild is used in Tumbleweed repo itself? Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Apr 14, 2011 at 08:12:31AM +0200, Takashi Iwai wrote:
At Sun, 10 Apr 2011 11:48:37 -0700, Greg KH wrote:
On Sun, Apr 10, 2011 at 07:09:58PM +0200, Marcus Meissner wrote:
On Sun, Apr 10, 2011 at 05:47:03PM +0200, Jiri Slaby wrote:
Note that this may not rebuild things and break the system for some weird cornercases. But everything should rpm-depend directly on packages which it really depends on, so rebuild="direct" should be safe. I don't remember any breakage in factory since this was turned on. And Factory uses even more conservative "local" option -- rebuild a package if and only if sources of the particular package change.
Such cases are fixed behind our backs usually. Coolo does much of selective rebuild triggers when necessary. Also factory has way more cycles than in previous days now, some quality drops were taken.
And transitive closure is an advantage for integrity ... :/
Tumbleweed however as a post-released product does not necessarily need it, but for some base changes it should be done at least once.
Yeah, for that reason I think I'll stick to the default we have now to be on the "safe" side. Especially when we start updating libraries, like we are now doing.
I think you can enable the automatic rebuilds in Tumbleweed:Test repo for integrity tests while the manual rebuild is used in Tumbleweed repo itself?
So then I would need to do manual rebuilds in the main Tumbleweed repo? Hm, that might work, I'll play around with that, thanks for the idea. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/14/2011 08:31 PM, Greg KH wrote:
So then I would need to do manual rebuilds in the main Tumbleweed repo?
Iff something really screws up. It's not that it doesn't rebuild at all. It's that it stops rebuilding packages which indirectly depend on a package which was rebuilt. It only rebuilds packages with _direct_ dependency on a package which was rebuilt. (If you decide to go with "direct" and not "local" -- unlike factory.) thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2011/4/10 Jiri Slaby
Feel free to take a look at it if you are curious, the LibreOffice developers said they are working on it so I trust them.
I don't know what is the real problem here. Maybe there will change the dependency on the samba library?
When the spec file BuildRequires a lot of things https://build.opensuse.org/package/view_file?file=libreoffice-bootstrap.spec&package=libreoffice-bootstrap&project=openSUSE%3ATumbleweed&srcmd5=d951ab8a686228ece1bb37459396c93a you don't see as requirements https://build.opensuse.org/package/binary?arch=x86_64&filename=libreoffice-bootstrap-3.3.2.2-2.7.x86_64.rpm&package=libreoffice-bootstrap&project=openSUSE%3ATumbleweed&repository=standard usually it means there are BuildRequires that shouldn't be there. And with BuildRequires as "gstreamer010-plugins-base-devel" you can end indirectly depending on half the multimedia libraries. The fact that libreoffice-bootstrap, which seems to be a build dependency of most parts of libreoffice, packages date/time dependent files https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libreoffice-bootstrap&project=openSUSE%3ATumbleweed&repository=standard breaking build-compare, also shows there is room for improvement. But anyway, what we really need is an "osc dependson" command that shows the *tree* of dependencies. This way it would be easier to see how the dependencies are generated and not just which are the dependencies. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Apr 10, 2011 at 05:47:03PM +0200, Jiri Slaby wrote:
On 04/10/2011 05:22 PM, Greg KH wrote: [ 8< ]
Feel free to take a look at it if you are curious, the LibreOffice developers said they are working on it so I trust them.
I don't know what is the real problem here. Maybe there will change the dependency on the samba library?
None I'm aware of. IIRC we moved from 3.5.7 (openSUSE 11.4 GA) to 3.5.8 in Tumbleweed as soon as we pushed this version to network:samba:STABLE From our upstream samba.org policy we would not make an breaking interface change as part of a minor update inside of the same major version (3.5 in this case). Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Mon, Apr 11, 2011 at 08:32:28AM +0200, Lars Müller wrote:
On Sun, Apr 10, 2011 at 05:47:03PM +0200, Jiri Slaby wrote:
On 04/10/2011 05:22 PM, Greg KH wrote: [ 8< ]
Feel free to take a look at it if you are curious, the LibreOffice developers said they are working on it so I trust them.
I don't know what is the real problem here. Maybe there will change the dependency on the samba library?
None I'm aware of. IIRC we moved from 3.5.7 (openSUSE 11.4 GA) to 3.5.8 in Tumbleweed as soon as we pushed this version to network:samba:STABLE
From our upstream samba.org policy we would not make an breaking interface change as part of a minor update inside of the same major version (3.5 in this case).
Yes, I don't think this is a samba issue at all, but rather some over-zealous Requires: package list in the LibreOffice .spec files. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-) Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it. 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
On Monday, April 11, 2011 10:20:50 AM Vincent Untz wrote:
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the
openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-)
Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it.
That would break Plasma Network Manager applet, I am afraid. -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Apr 11, 2011 at 10:19:15AM +0200, İsmail Dönmez wrote:
On Monday, April 11, 2011 10:20:50 AM Vincent Untz wrote:
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the
openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-)
Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it.
That would break Plasma Network Manager applet, I am afraid.
Is there an updated version of this in Factory that I could pull from to resolve the breakage? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday, April 11, 2011 04:55:11 PM Greg KH wrote:
On Mon, Apr 11, 2011 at 10:19:15AM +0200, İsmail Dönmez wrote:
On Monday, April 11, 2011 10:20:50 AM Vincent Untz wrote:
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the
openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-)
Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it.
That would break Plasma Network Manager applet, I am afraid.
Is there an updated version of this in Factory that I could pull from to resolve the breakage?
Not at the moment no, this needs to be discussed on opensuse-kde@ I believe because AFAIK upstream does not support nm-0.9 API yet. -- İsmail Dönmez - openSUSE Booster SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Apr 11, 2011 at 10:20:50AM +0200, Vincent Untz wrote:
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-)
Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it.
Does G:S:3.0 need the new NetworkManager? If not, I can leave it out for now. But overall, it would be good to get it in, what is needed to fix in the KDE packages to get it to work properly there? I'm guessing that I need to wait until the GNOME developers actually publish G:S:3.0 before adding it to Tumbleweed, right? I still see a few build problems in that repo at the moment. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le lundi 11 avril 2011 à 07:54 -0700, Greg KH a écrit :
On Mon, Apr 11, 2011 at 10:20:50AM +0200, Vincent Untz wrote:
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-)
Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it.
Does G:S:3.0 need the new NetworkManager? If not, I can leave it out for now.
Yes, it does (and it provides it).
But overall, it would be good to get it in, what is needed to fix in the KDE packages to get it to work properly there?
I added some patches from fedora15 branch for NM 0.9 which is supposed to bring some compatibility for KDE but I haven't tested if they work or not (they are part of NM 0.9 package in both my repo and G:S:3.0).
I'm guessing that I need to wait until the GNOME developers actually publish G:S:3.0 before adding it to Tumbleweed, right? I still see a few build problems in that repo at the moment.
Well, we hope to be able to publish it this week.
--
Frederic Crozat
On Mon, Apr 11, 2011 at 05:20:03PM +0200, Frederic Crozat wrote:
Le lundi 11 avril 2011 à 07:54 -0700, Greg KH a écrit :
On Mon, Apr 11, 2011 at 10:20:50AM +0200, Vincent Untz wrote:
Le samedi 09 avril 2011, à 17:30 -0700, Greg KH a écrit :
- I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough.
That'd be cool, thanks for being proactive on this :-)
Just one thing: we have NetworkManager 0.9 in G:S:3.0, which might break some stuff, so I guess some care is needed for it.
Does G:S:3.0 need the new NetworkManager? If not, I can leave it out for now.
Yes, it does (and it provides it).
But overall, it would be good to get it in, what is needed to fix in the KDE packages to get it to work properly there?
I added some patches from fedora15 branch for NM 0.9 which is supposed to bring some compatibility for KDE but I haven't tested if they work or not (they are part of NM 0.9 package in both my repo and G:S:3.0).
Great, thanks for adding those. Anyone from KDE want to verify that these do or do not work for them? Or how would I test them myself?
I'm guessing that I need to wait until the GNOME developers actually publish G:S:3.0 before adding it to Tumbleweed, right? I still see a few build problems in that repo at the moment.
Well, we hope to be able to publish it this week.
That's great to hear. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le lundi 11 avril 2011, à 10:20 -0700, Greg KH a écrit :
On Mon, Apr 11, 2011 at 05:20:03PM +0200, Frederic Crozat wrote:
I added some patches from fedora15 branch for NM 0.9 which is supposed to bring some compatibility for KDE but I haven't tested if they work or not (they are part of NM 0.9 package in both my repo and G:S:3.0).
Great, thanks for adding those. Anyone from KDE want to verify that these do or do not work for them? Or how would I test them myself?
I think it's worth pointing out that we'll want to push NetworkManager 0.9 to Factory soon anyway (where soon is 1-2 weeks, I guess). So anyone interesting in making sure their stuff still works with the new NM (that includes KDE, obviously, but there might be other groups) should look at the NM 0.9 packages in G:S:3.0. And please report successes/failures so we know if it's okay to go ahead. Thanks, 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
Am Mittwoch 13 April 2011, 08:50:22 schrieb Vincent Untz:
So anyone interesting in making sure their stuff still works with the new NM (that includes KDE, obviously, but there might be other groups) should look at the NM 0.9 packages in G:S:3.0. And please report successes/failures so we know if it's okay to go ahead.
It broke everything here. KDE's Network Management did no longer function. Not even NM-Applet function any longer (something about no network device found). GNOME run neither just giving the extremely helpful error message "Something went wrong". Luckily wired connections still worked, so I could disable the GS3 repo, remove everything related to GNOME and downgrade to NM 0.8. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le jeudi 14 avril 2011, à 14:45 +0200, Markus Slopianka a écrit :
Am Mittwoch 13 April 2011, 08:50:22 schrieb Vincent Untz:
So anyone interesting in making sure their stuff still works with the new NM (that includes KDE, obviously, but there might be other groups) should look at the NM 0.9 packages in G:S:3.0. And please report successes/failures so we know if it's okay to go ahead.
It broke everything here. KDE's Network Management did no longer function. Not even NM-Applet function any longer (something about no network device found).
It'd be helpful to have more information, like: + versions of all NetworkManager-related packages + exact error message
GNOME run neither just giving the extremely helpful error message "Something went wrong".
Sorry if I wasn't clear -- the test only involves updating NetworkManager, and not taking anything else from GNOME:STABLE:3.0. We know the upgrade process to GNOME 3.0 right now is not smooth (you need to do some things manually), which is why we haven't recommended this repository for wide use yet. Cheers, 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
Am Freitag 15 April 2011, 08:58:56 schrieb Vincent Untz:
It'd be helpful to have more information, like:
+ versions of all NetworkManager-related packages
Exactly the same versions offered in GS3 and KDE/Release/46.
+ exact error message
"Device not available or not managed by NetworkManager" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, 2011-04-15 at 15:05 +0200, Markus Slopianka wrote:
+ versions of all NetworkManager-related packages
Exactly the same versions offered in GS3 and KDE/Release/46.
+ exact error message
"Device not available or not managed by NetworkManager"
WiFi Devices? Did you get wpa_supplicant from the location where NM lives as well? It has been patched. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag 15 April 2011, 15:18:52 schrieb Dimstar / Dominique Leuenberger:
WiFi Devices?
Well, "Unavailable" was printed for the wired connection as well but worked nonetheless.
Did you get wpa_supplicant from the location where NM lives as well?
No idea. I enabled the repo and ran "zypper dup". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le mercredi 13 avril 2011, à 08:50 +0200, Vincent Untz a écrit :
Le lundi 11 avril 2011, à 10:20 -0700, Greg KH a écrit :
On Mon, Apr 11, 2011 at 05:20:03PM +0200, Frederic Crozat wrote:
I added some patches from fedora15 branch for NM 0.9 which is supposed to bring some compatibility for KDE but I haven't tested if they work or not (they are part of NM 0.9 package in both my repo and G:S:3.0).
Great, thanks for adding those. Anyone from KDE want to verify that these do or do not work for them? Or how would I test them myself?
I think it's worth pointing out that we'll want to push NetworkManager 0.9 to Factory soon anyway (where soon is 1-2 weeks, I guess).
So anyone interesting in making sure their stuff still works with the new NM (that includes KDE, obviously, but there might be other groups) should look at the NM 0.9 packages in G:S:3.0. And please report successes/failures so we know if it's okay to go ahead.
We'll likely want to push NM 0.9 at the end of this week. Would that work with people, or is more time needed (and if that's the case, how much more time)? Cheers, 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
Am Dienstag 26 April 2011, 10:41:24 schrieb Vincent Untz:
We'll likely want to push NM 0.9 at the end of this week. Would that work with people, or is more time needed (and if that's the case, how much more time)?
Is KDE Network Management in KDE:/Playground built from the NM09 git.kde.org branch? If not, could someone please provide KNM for 0.9 in some repo? I've made enough room on my HDD to set up a VM for testing. Markus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Apr 26, 2011 at 10:41:24AM +0200, Vincent Untz wrote:
Le mercredi 13 avril 2011, à 08:50 +0200, Vincent Untz a écrit :
Le lundi 11 avril 2011, à 10:20 -0700, Greg KH a écrit :
On Mon, Apr 11, 2011 at 05:20:03PM +0200, Frederic Crozat wrote:
I added some patches from fedora15 branch for NM 0.9 which is supposed to bring some compatibility for KDE but I haven't tested if they work or not (they are part of NM 0.9 package in both my repo and G:S:3.0).
Great, thanks for adding those. Anyone from KDE want to verify that these do or do not work for them? Or how would I test them myself?
I think it's worth pointing out that we'll want to push NetworkManager 0.9 to Factory soon anyway (where soon is 1-2 weeks, I guess).
So anyone interesting in making sure their stuff still works with the new NM (that includes KDE, obviously, but there might be other groups) should look at the NM 0.9 packages in G:S:3.0. And please report successes/failures so we know if it's okay to go ahead.
We'll likely want to push NM 0.9 at the end of this week. Would that work with people, or is more time needed (and if that's the case, how much more time)?
Are there KDE fixes somewhere to keep that working properly? If so, and they get also checked in, that sounds fine to me, it would let me get this into Tumbleweed which would be very good to have. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Dienstag 26 April 2011, 15:08:24 schrieb Greg KH:
Are there KDE fixes somewhere to keep that working properly? If so, and they get also checked in, that sounds fine to me, it would let me get this into Tumbleweed which would be very good to have.
Red Hat created a "F15" branch for Fedora15 in NM's git repo that supposedly adds compatibility with older NM08 clients (KDE). Those patches are applied to openSUSE's NM09 as well but my experience 2 or so weeks ago was that they don't work. But there is also work going on on the KDE side to modify KNM for NM09. I have not yet tested that. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, Le mardi 26 avril 2011, à 06:08 -0700, Greg KH a écrit :
On Tue, Apr 26, 2011 at 10:41:24AM +0200, Vincent Untz wrote:
We'll likely want to push NM 0.9 at the end of this week. Would that work with people, or is more time needed (and if that's the case, how much more time)?
Are there KDE fixes somewhere to keep that working properly?
Anybody from KDE who knows the exact status? I'll just assume it works in Factory if nobody replies... And if it's still not working, please provide a timeline for a fix so we can know how long we should wait, or if we should find an alternative way to deal with that. Thanks, 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
On Thursday 28 Apr 2011 18:08:15 Vincent Untz wrote:
Hi,
Le mardi 26 avril 2011, à 06:08 -0700, Greg KH a écrit :
On Tue, Apr 26, 2011 at 10:41:24AM +0200, Vincent Untz wrote:
We'll likely want to push NM 0.9 at the end of this week. Would that work with people, or is more time needed (and if that's the case, how much more time)?
Are there KDE fixes somewhere to keep that working properly?
Anybody from KDE who knows the exact status? I'll just assume it works in Factory if nobody replies...
And if it's still not working, please provide a timeline for a fix so we can know how long we should wait, or if we should find an alternative way to deal with that.
Thanks,
Vincent
It almost works.. wpa enterprise still crashes it (eduroam network)... there is a bug on bnc. Alin -- I force myself to contradict myself in order to avoid conforming to my own taste. -- Marcel Duchamp Without Questions there are no Answers! _____________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Vincent, Unfortunately Will is not in the office, but you can push NetworkManager to Factory. We have the fixes for kdebase-workspace and the KDE-networkmanager. As soon as NM 0.9 lands in Factory, we will add the fixes to the two packages in KDE:Distro:Factory and from there push them into Factory. I have already build the packages with those buildfixes. There are still some small things that needs to be fixed properly, but overall the functionality of KNM/PNM works. Regards Raymond On Thursday 28 April 2011 18:08:15 Vincent Untz wrote:
Hi,
Le mardi 26 avril 2011, à 06:08 -0700, Greg KH a écrit :
On Tue, Apr 26, 2011 at 10:41:24AM +0200, Vincent Untz wrote:
We'll likely want to push NM 0.9 at the end of this week. Would that work with people, or is more time needed (and if that's the case, how much more time)?
Are there KDE fixes somewhere to keep that working properly?
Anybody from KDE who knows the exact status? I'll just assume it works in Factory if nobody replies...
And if it's still not working, please provide a timeline for a fix so we can know how long we should wait, or if we should find an alternative way to deal with that.
Thanks,
Vincent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le jeudi 28 avril 2011 à 18:54 +0200, Raymond Wooninck a écrit :
Hi Vincent,
Unfortunately Will is not in the office, but you can push NetworkManager to Factory. We have the fixes for kdebase-workspace and the KDE-networkmanager.
As soon as NM 0.9 lands in Factory, we will add the fixes to the two packages in KDE:Distro:Factory and from there push them into Factory.
I have already build the packages with those buildfixes. There are still some small things that needs to be fixed properly, but overall the functionality of KNM/PNM works.
Out of curiosity, does those fixes requires the f15 patch we are
applying to NM 0.9 ?
--
Frederic Crozat
Hi Frederic, Yes, KNM has not been rewritten yet for NM 0.9 (and I am not sure about the timeline for it either). This is up to Will. For now we are using the patches for KDE that Dan Williams created, which require the f15 patch. Raymond On Thursday 28 April 2011 18:57:55 Frederic Crozat wrote:
Le jeudi 28 avril 2011 à 18:54 +0200, Raymond Wooninck a écrit :
Hi Vincent,
Unfortunately Will is not in the office, but you can push NetworkManager to Factory. We have the fixes for kdebase-workspace and the KDE-networkmanager.
As soon as NM 0.9 lands in Factory, we will add the fixes to the two packages in KDE:Distro:Factory and from there push them into Factory.
I have already build the packages with those buildfixes. There are still some small things that needs to be fixed properly, but overall the functionality of KNM/PNM works.
Out of curiosity, does those fixes requires the f15 patch we are applying to NM 0.9 ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le jeudi 28 avril 2011 à 19:14 +0200, Raymond Wooninck a écrit :
Hi Frederic,
Yes, KNM has not been rewritten yet for NM 0.9 (and I am not sure about the timeline for it either). This is up to Will.
For now we are using the patches for KDE that Dan Williams created, which require the f15 patch.
Ok, good to know.
Of course, it would be nice if we could get KDE from 11.4 to work with
NM 0.9 ;)
--
Frederic Crozat
On Fri, Apr 29, 2011 at 09:48:24AM +0200, Frederic Crozat wrote:
Le jeudi 28 avril 2011 à 19:14 +0200, Raymond Wooninck a écrit :
Hi Frederic,
Yes, KNM has not been rewritten yet for NM 0.9 (and I am not sure about the timeline for it either). This is up to Will.
For now we are using the patches for KDE that Dan Williams created, which require the f15 patch.
Ok, good to know.
Of course, it would be nice if we could get KDE from 11.4 to work with NM 0.9 ;)
If you are using 11.4, then you would never updgrade NM either. As long as it all plays well together in Tumbleweed, everyone will be happy. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (13)
-
Alin Marin Elena -
Cristian Morales Vega -
Dimstar / Dominique Leuenberger -
Frederic Crozat -
Greg KH -
İsmail Dönmez -
Jiri Slaby -
Lars Müller -
Marcus Meissner -
Markus Slopianka -
Raymond Wooninck -
Takashi Iwai -
Vincent Untz