[opensuse-factory] Tumbleweed - systemd installed via dup - intentional?
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services. The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'. I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 06/23/2011 11:17 AM, Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right?
+ 1 I really appreciate the developers work now done in Factory to test systemd and integrate it for the next 12.1 release. And it is for sure that keeping a rolling release rolling and stable requires quit some efforts. But the description http://en.opensuse.org/Tumbleweed states that it "tumbleweed is for those who wants the newest *but* stable software" and that "Tumbleweed is the newest stable and *ready for daily use*". I know that these terms can be stretched and undergo personal interpretations. But might it be possible to be a bit more conservative when it comes to big change like the recent switch to systemd and to wait for some stabilization? Just for curiosity: Is there any kind of policy (like e.g for the debian unstable -> testing package flow) which determines the package flow into Tumbleweed? In any case, thanks for the work in Tumbleweed! Cheers, Andre Massing -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Jun 23, 2011 at 02:04:58PM +0200, Andre Massing wrote:
On 06/23/2011 11:17 AM, Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right?
+ 1
I really appreciate the developers work now done in Factory to test systemd and integrate it for the next 12.1 release. And it is for sure that keeping a rolling release rolling and stable requires quit some efforts. But the description http://en.opensuse.org/Tumbleweed states that it "tumbleweed is for those who wants the newest *but* stable software" and that "Tumbleweed is the newest stable and *ready for daily use*". I know that these terms can be stretched and undergo personal interpretations. But might it be possible to be a bit more conservative when it comes to big change like the recent switch to systemd and to wait for some stabilization?
Again, nothing switched to systemd. Unless you were using systemd before, nothing changed. So please don't think otherwise.
Just for curiosity: Is there any kind of policy (like e.g for the debian unstable -> testing package flow) which determines the package flow into Tumbleweed?
Yes, it needs to be in Factory, and it passes tests in Tumbleweed:Testing. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday, June 23, 2011 02:17:21 AM Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right? I would have to agree. After reading this, my curiosity about Tumbleweed is gone. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Jun 23, 2011 at 01:17:17PM -0700, Roger Luedecke wrote:
On Thursday, June 23, 2011 02:17:21 AM Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right? I would have to agree. After reading this, my curiosity about Tumbleweed is gone.
Why? Tumbleweed did not switch to systemd by default, you can use 11.4 today with systemd, and if you do, and use Tumbleweed, you will get the newer version of systemd. Nothing changes otherwise, it works just as good as it did before, nothing changed. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Jun 23, 2011 at 05:17:21AM -0400, Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right?
Yes, and systemd should not be enabled by default in Tumbleweed (yet), so I find the above boot problem very strange as it doesn't happen here for me on my test systems, or my main development machine. Are you sure you aren't enabling systemd on your boot somehow accidentally? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2011/06/23 14:36 (GMT-0700) Greg KH composed:
On Thu, Jun 23, 2011 at 05:17:21AM -0400, Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right?
Yes, and systemd should not be enabled by default in Tumbleweed (yet), so I find the above boot problem very strange as it doesn't happen here for me on my test systems, or my main development machine.
Are you sure you aren't enabling systemd on your boot somehow accidentally?
I can't imagine how that might be possible. Following are the URL lines from /etc/zypp/repos.d/*.repo: KOTDstable.repo:baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/ Mozilla.repo:baseurl=http://download.opensuse.org/repositories/mozilla/openSUSE_11.4/ Non-OSS.repo:baseurl=http://download.opensuse.org/distribution/11.4/repo/non-oss/ OSS.repo:baseurl=http://download.opensuse.org/distribution/11.4/repo/oss/ Tumbleweed.repo:baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ Updates.repo:baseurl=http://download.opensuse.org/update/11.4/ Another question: why does zypper lu tell me some 2.6.37 kernel is an update to the newest installed kernel, 2.6.39? Is there a way to make zypper stop offering to "update" to 2.6.37 kernels? Loading repository data... Reading installed packages... S | Repository | Name | Current Version | Available Version | Arch --+------------+---------------------+-----------------------+-------------------------+----- v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 v | Tumbleweed | mkinitrd | 2.7.0-15.1 | 2.7.0-17.1 | i586 v | Updates | preload-kmp-desktop | 1.2_k2.6.37.1_1.2-5.3 | 1.2_k2.6.37.6_0.5-6.7.3 | i586 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 06/23/2011 11:31 PM, Felix Miata pecked at the keyboard and wrote:
On 2011/06/23 14:36 (GMT-0700) Greg KH composed:
On Thu, Jun 23, 2011 at 05:17:21AM -0400, Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right?
Yes, and systemd should not be enabled by default in Tumbleweed (yet), so I find the above boot problem very strange as it doesn't happen here for me on my test systems, or my main development machine.
Are you sure you aren't enabling systemd on your boot somehow accidentally?
I can't imagine how that might be possible. Following are the URL lines from /etc/zypp/repos.d/*.repo:
KOTDstable.repo:baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/
Mozilla.repo:baseurl=http://download.opensuse.org/repositories/mozilla/openSUSE_11.4/
Non-OSS.repo:baseurl=http://download.opensuse.org/distribution/11.4/repo/non-oss/
OSS.repo:baseurl=http://download.opensuse.org/distribution/11.4/repo/oss/ Tumbleweed.repo:baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
Updates.repo:baseurl=http://download.opensuse.org/update/11.4/
Another question: why does zypper lu tell me some 2.6.37 kernel is an update to the newest installed kernel, 2.6.39? Is there a way to make zypper stop offering to "update" to 2.6.37 kernels?
Loading repository data... Reading installed packages... S | Repository | Name | Current Version | Available Version | Arch --+------------+---------------------+-----------------------+-------------------------+-----
v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 v | Tumbleweed | mkinitrd | 2.7.0-15.1 | 2.7.0-17.1 | i586 v | Updates | preload-kmp-desktop | 1.2_k2.6.37.1_1.2-5.3 | 1.2_k2.6.37.6_0.5-6.7.3 | i586
Giving tumbleweed a higher priority should do the trick. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2011/06/24 08:06 (GMT-0400) Ken Schneider - openSUSE composed:
On 06/23/2011 11:31 PM, Felix Miata pecked at the keyboard and wrote:
why does zypper lu tell me some 2.6.37 kernel is an update to the newest installed kernel, 2.6.39? Is there a way to make zypper stop offering to "update" to 2.6.37 kernels?
Loading repository data... Reading installed packages... S | Repository | Name | Current Version | Available Version | Arch --+---------+---------------------+-----------------------+-------------------------+----- v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 v | Tumbleweed | mkinitrd | 2.7.0-15.1 | 2.7.0-17.1 | i586 v | Updates | preload-kmp-desktop | 1.2_k2.6.37.1_1.2-5.3 | 1.2_k2.6.37.6_0.5-6.7.3 | i586
Giving tumbleweed a higher priority should do the trick.
[KOTD] baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/ priority=80 ... [Tumbleweed] baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ priority=90 ... [Update] baseurl=http://download.opensuse.org/update/11.4/ priority=95 ... Repository 'KerneloftheDay-stable' is up to date. Repository 'Mozilla' is up to date. Repository 'Non-OSS' is up to date. Repository 'OSS' is up to date. Repository 'Tumbleweed' is up to date. Repository 'Updates' is up to date. All repositories have been refreshed. ... v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 Any other ideas? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2011/06/24 08:06 (GMT-0400) Ken Schneider - openSUSE composed:
On 06/23/2011 11:31 PM, Felix Miata pecked at the keyboard and wrote:
why does zypper lu tell me some 2.6.37 kernel is an update to the newest installed kernel, 2.6.39? Is there a way to make zypper stop offering to "update" to 2.6.37 kernels?
Loading repository data... Reading installed packages... S | Repository | Name | Current Version | Available Version | Arch --+---------+---------------------+-----------------------+-------------------------+-----
v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 v | Tumbleweed | mkinitrd | 2.7.0-15.1 | 2.7.0-17.1 | i586 v | Updates | preload-kmp-desktop | 1.2_k2.6.37.1_1.2-5.3 | 1.2_k2.6.37.6_0.5-6.7.3 | i586
Giving tumbleweed a higher priority should do the trick.
[KOTD] baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/ priority=80 ... [Tumbleweed] baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
priority=90 ... [Update] baseurl=http://download.opensuse.org/update/11.4/ priority=95 ... Repository 'KerneloftheDay-stable' is up to date. Repository 'Mozilla' is up to date. Repository 'Non-OSS' is up to date. Repository 'OSS' is up to date. Repository 'Tumbleweed' is up to date. Repository 'Updates' is up to date. All repositories have been refreshed. ... v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586
Any other ideas? You've got the wrong repositories. Should switch off the KernelOfTheDay repo (and optionally add Packman_Tumbleweed), make all
On 06/25/2011 02:45 AM, Felix Miata wrote: the same priority and see what "zypper dup -D" proposes. Regards John A and nothing wrong with having -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2011/06/25 06:24 (GMT+1000) John Andrews (swerdna) composed:
Felix Miata wrote:
Ken Schneider - openSUSE composed:
Felix Miata pecked at the keyboard and wrote:
why does zypper lu tell me some 2.6.37 kernel is an update to the newest installed kernel, 2.6.39? Is there a way to make zypper stop offering to "update" to 2.6.37 kernels?
Loading repository data... Reading installed packages... S | Repository | Name | Current Version | Available Version | Arch --+---------+---------------------+-----------------------+-------------------------+-----
v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 v | Tumbleweed | mkinitrd | 2.7.0-15.1 | 2.7.0-17.1 | i586 v | Updates | preload-kmp-desktop | 1.2_k2.6.37.1_1.2-5.3 | 1.2_k2.6.37.6_0.5-6.7.3 | i586
Giving tumbleweed a higher priority should do the trick.
[KOTD] baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/ priority=80 ... [Tumbleweed] baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
priority=90 ... [Update] baseurl=http://download.opensuse.org/update/11.4/ priority=95 ... Repository 'KerneloftheDay-stable' is up to date. Repository 'Mozilla' is up to date. Repository 'Non-OSS' is up to date. Repository 'OSS' is up to date. Repository 'Tumbleweed' is up to date. Repository 'Updates' is up to date. All repositories have been refreshed. ... v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586
Any other ideas?
You've got the wrong repositories. Should switch off the KernelOfTheDay repo (and optionally add Packman_Tumbleweed), make all the same priority and see what "zypper dup -D" proposes.
Prior to trying Ken's suggestion to assign priorities, all were set to defaults (unset actually). When I went looking for 2.6.39, "KOTD" was the only place I could find one for TW or 11.4, particularly not Packman, where I don't remember ever seeing any kernels. https://bugzilla.novell.com/show_bug.cgi?id=584493 has been highly annoying for well over a year, so I take every opportunity to discover if it might have disappeared. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 06/25/2011 06:47 AM, Felix Miata wrote:
On 2011/06/25 06:24 (GMT+1000) John Andrews (swerdna) composed:
Felix Miata wrote:
Ken Schneider - openSUSE composed:
Felix Miata pecked at the keyboard and wrote:
why does zypper lu tell me some 2.6.37 kernel is an update to the newest installed kernel, 2.6.39? Is there a way to make zypper stop offering to "update" to 2.6.37 kernels?
Loading repository data... Reading installed packages... S | Repository | Name | Current Version | Available Version | Arch --+---------+---------------------+-----------------------+-------------------------+-----
v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586 v | Tumbleweed | mkinitrd | 2.7.0-15.1 | 2.7.0-17.1 | i586 v | Updates | preload-kmp-desktop | 1.2_k2.6.37.1_1.2-5.3 | 1.2_k2.6.37.6_0.5-6.7.3 | i586
Giving tumbleweed a higher priority should do the trick.
[KOTD] baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/
priority=80 ... [Tumbleweed] baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
priority=90 ... [Update] baseurl=http://download.opensuse.org/update/11.4/ priority=95 ... Repository 'KerneloftheDay-stable' is up to date. Repository 'Mozilla' is up to date. Repository 'Non-OSS' is up to date. Repository 'OSS' is up to date. Repository 'Tumbleweed' is up to date. Repository 'Updates' is up to date. All repositories have been refreshed. ... v | Updates | kernel-desktop | 2.6.39.1-33.1 | 2.6.37.6-0.5.1 | i586
Any other ideas?
You've got the wrong repositories. Should switch off the KernelOfTheDay repo (and optionally add Packman_Tumbleweed), make all the same priority and see what "zypper dup -D" proposes.
Prior to trying Ken's suggestion to assign priorities, all were set to defaults (unset actually).
When I went looking for 2.6.39, "KOTD" was the only place I could find one for TW or 11.4, particularly not Packman, where I don't remember ever seeing any kernels.
https://bugzilla.novell.com/show_bug.cgi?id=584493 has been highly annoying for well over a year, so I take every opportunity to discover if it might have disappeared.
There is a suite of kernels in Tumbleweed repo e.g. look here: http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/x86_... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2011/06/25 07:57 (GMT+1000) John Andrews (swerdna) composed:
There is a suite of kernels in Tumbleweed repo e.g. look here: http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/x86_...
Your point escapes me. The newest I see there is the 2.6.39.1-33.1 that was installed already when zypper offered to "update" to 2.6.37.6whatever. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 06/25/2011 09:15 AM, Felix Miata wrote:
On 2011/06/25 07:57 (GMT+1000) John Andrews (swerdna) composed:
There is a suite of kernels in Tumbleweed repo e.g. look here: http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/x86_...
Your point escapes me. The newest I see there is the 2.6.39.1-33.1 that was installed already when zypper offered to "update" to 2.6.37.6whatever. I thought you were seeking 2.6.39 -- missed that point, missed that you have picked up precisely 2.6.39.1-33.1 from somewhere else.
The offer to downgrade the kernel must be associated with some other package being downgraded or was downgraded earlier, that requires matching to the lower kernel. So you probably need to look closely at tall of the packages that zypper is declaring will be changed, to see what that package is/are; i.e. to see what package/s is/are going to drag the kernel down with it. And in those circumstances (if my rough guess turns out to relevant), in those circumstances you should turn off the additional kernel repository, because it is at least an additional variable that makes process of elimination more complicated. Better to focus on Tumbleweed repos only if you're trying to solve a Tumbleweed issue. Regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Jun 23, 2011 at 11:31:24PM -0400, Felix Miata wrote:
On 2011/06/23 14:36 (GMT-0700) Greg KH composed:
On Thu, Jun 23, 2011 at 05:17:21AM -0400, Felix Miata wrote:
Several hours ago I did a zypper dup on a Tumbleweed system. The next several boots took an eternity each to complete, and made a mess of boot message output until I figured out systemd had been installed. The init command was broken for switching among runlevels, keyboard was producing unexpected behavior, and boot was producing messages about problems with *.services.
The fix was simple enough: 'zypper rm systemd systemd-sysvinit; zypper al systemd'.
I realize Tumbleweed is rather young and somewhat experimental, but a testbed for systemd development it should not be. That's Factory's job, right?
Yes, and systemd should not be enabled by default in Tumbleweed (yet), so I find the above boot problem very strange as it doesn't happen here for me on my test systems, or my main development machine.
Are you sure you aren't enabling systemd on your boot somehow accidentally?
I can't imagine how that might be possible. Following are the URL lines from /etc/zypp/repos.d/*.repo:
KOTDstable.repo:baseurl=http://download.opensuse.org/repositories/Kernel:/stable/standard/
Delete this one, it's not needed if you use Tumbleweed.
Mozilla.repo:baseurl=http://download.opensuse.org/repositories/mozilla/openSUSE_11.4/
Same here, don't use it.
Non-OSS.repo:baseurl=http://download.opensuse.org/distribution/11.4/repo/non-oss/ OSS.repo:baseurl=http://download.opensuse.org/distribution/11.4/repo/oss/ Tumbleweed.repo:baseurl=http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ Updates.repo:baseurl=http://download.opensuse.org/update/11.4/
Those are fine, but delete all priority levels and you should be fine. Let me know if that works. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Andre Massing -
Felix Miata -
Greg KH -
John Andrews (swerdna) -
Ken Schneider - openSUSE -
Roger Luedecke