[opensuse-factory] Tumbleweed repo structure question
Hello guys. I have a simple question, but can not find an answer. Manual recommends to use only one repo -- Tumbleweed. But we have not enought software there. And because of this we need to have 11.4-oss, 11.4-non-oss and updates repo enabled. As result we have repo hell: packages conflicts and so on. For example, first update with "zypper dup --from Tumbleweed" was completed great. But later, when new packages appeared in Tumbleweed repo, "zypper dup" (as Greg K-H recommends) instead "zypper dup --from Tumbleweed" didn`t update these packages because zypper doesn`t change repository for package by default. And it`s needed to use priorities or --from option again. The question is why not to pull _all_ packages from oss-repo and non-oss-repo to tumbleweed repo. Even if the most part of them will be at the same version. This way we can use really single tumbleweed repo. Also it`ll be great to have tumbleweed-oss and tumbleweed-non-oss to avoid licence issues. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, May 20, 2011 at 04:28:08PM +0400, barton`ello wrote:
Hello guys.
I have a simple question, but can not find an answer. Manual recommends to use only one repo -- Tumbleweed.
What "manual"?
But we have not enought software there. And because of this we need to have 11.4-oss, 11.4-non-oss and updates repo enabled. As result we have repo hell: packages conflicts and so on.
Huh? No, you should have all of those repos enabled, and tumbleweed as well. That's it, and you should not have any conflicts. If you do, please let me know what they are.
For example, first update with "zypper dup --from Tumbleweed" was completed great. But later, when new packages appeared in Tumbleweed repo, "zypper dup" (as Greg K-H recommends) instead "zypper dup --from Tumbleweed" didn`t update these packages because zypper doesn`t change repository for package by default. And it`s needed to use priorities or --from option again.
I never recommend the "--from Tumbleweed" option. Just always do a simple "zypper dup" and that's all you need. Sometimes, depending on the state of Tumbleweed, packages will move to and from the Tumbleweed repo and the 11.4 repo.
The question is why not to pull _all_ packages from oss-repo and non-oss-repo to tumbleweed repo. Even if the most part of them will be at the same version. This way we can use really single tumbleweed repo.
Because of the size and because we don't need to do this. It also offers a "safe way out" if something goes wrong in Tumbleweed. We can (and do) drop packages from Tumbleweed and they revert back to the original, "safe" version from 11.4. Same for you, if you don't want to use Tumbleweed, just drop that one repo, and everything reverts back to a stable release level.
Also it`ll be great to have tumbleweed-oss and tumbleweed-non-oss to avoid licence issues.
What license issues are you seeing today? What non-oss package do you want in Tumbleweed? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2011/5/20 Greg KH <gregkh@suse.de>:
What "manual"?
For example there was "HowTo" at opensuse tumbleweed forums, but now it seems to be updated.
I never recommend the "--from Tumbleweed" option.
Correct. I tried to say that you recommend to use "zypper dup" and not to use "zypper dup --from Tumbleweed".
Just always do a simple "zypper dup" and that's all you need. Sometimes, depending on the state of Tumbleweed, packages will move to and from the Tumbleweed repo and the 11.4 repo.
Heh... It's logical that Tumbleweed contains the newest stable software, tested for compatibility with each other and it's not good idea to mix it with 11.4. I thought that it is not normal to change vendor from Tumbleweed to 11.4 during regular updates, but it is as I see.
Because of the size and because we don't need to do this. It also offers a "safe way out" if something goes wrong in Tumbleweed. We can (and do) drop packages from Tumbleweed and they revert back to the original, "safe" version from 11.4. Same for you, if you don't want to use Tumbleweed, just drop that one repo, and everything reverts back to a stable release level.
The size... I didn't think that disk space is the problem nowadays, but looks like it is. About "safe way out" if it will be tumbleweed-all-in-one-repo. You can still replace messy package with last stable one, for example from 11.4. And it'll be downgraded next update. It's some kind of critical measures and not a good practice I think. Because Tumbleweed declared as "newest _stable_ and ready for daily use". It's better to do fixes and updates. For me, if I don't want to use Tumbleweed. I will change tumbleweed repo to 11.4 repo and will do a "dup". And everything reverts back to a stable release level.
What license issues are you seeing today? What non-oss package do you want in Tumbleweed?
I do not see any license problems today. Moreover I do not stick any strict license policy. But it is a good practice to split repo this way I think. May be in future. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 05/21/2011 12:19 AM, barton`ello wrote:
2011/5/20 Greg KH<gregkh@suse.de>:
What "manual"?
For example there was "HowTo" at opensuse tumbleweed forums, but now it seems to be updated.
I never recommend the "--from Tumbleweed" option.
Correct. I tried to say that you recommend to use "zypper dup" and not to use "zypper dup --from Tumbleweed".
Just always do a simple "zypper dup" and that's all you need. Sometimes, depending on the state of Tumbleweed, packages will move to and from the Tumbleweed repo and the 11.4 repo.
Heh... It's logical that Tumbleweed contains the newest stable software, tested for compatibility with each other and it's not good idea to mix it with 11.4. I thought that it is not normal to change vendor from Tumbleweed to 11.4 during regular updates, but it is as I see.
Because of the size and because we don't need to do this. It also offers a "safe way out" if something goes wrong in Tumbleweed. We can (and do) drop packages from Tumbleweed and they revert back to the original, "safe" version from 11.4. Same for you, if you don't want to use Tumbleweed, just drop that one repo, and everything reverts back to a stable release level.
The size... I didn't think that disk space is the problem nowadays, but looks like it is. About "safe way out" if it will be tumbleweed-all-in-one-repo. You can still replace messy package with last stable one, for example from 11.4. And it'll be downgraded next update. It's some kind of critical measures and not a good practice I think. Because Tumbleweed declared as "newest _stable_ and ready for daily use". It's better to do fixes and updates. For me, if I don't want to use Tumbleweed. I will change tumbleweed repo to 11.4 repo and will do a "dup". And everything reverts back to a stable release level.
What license issues are you seeing today? What non-oss package do you want in Tumbleweed?
I do not see any license problems today. Moreover I do not stick any strict license policy. But it is a good practice to split repo this way I think. May be in future.
Thanks.
Regarding "zypper dup" and "zypper dup --from Tumbleweed". Much confusion stems from the Portal Page. Originally the "--from Tumbleweed" qualifier was advocated. Now last few days it's been changed to recommend the simple "zypper dup". Glad to see that it's been clarified/fixed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, May 20, 2011 at 06:19:22PM +0400, barton`ello wrote:
2011/5/20 Greg KH <gregkh@suse.de>:
Because of the size and because we don't need to do this. It also offers a "safe way out" if something goes wrong in Tumbleweed. We can (and do) drop packages from Tumbleweed and they revert back to the original, "safe" version from 11.4. Same for you, if you don't want to use Tumbleweed, just drop that one repo, and everything reverts back to a stable release level.
The size... I didn't think that disk space is the problem nowadays, but looks like it is.
No, it's not a "size" for disk space, it's a "how to manage this number of packages" issue. It also handles dependancies better, see the fun we have with libreoffice constantly rebuilding for an example of that. I don't think you really want that for hundreds of packages all the time.
What license issues are you seeing today? What non-oss package do you want in Tumbleweed?
I do not see any license problems today. Moreover I do not stick any strict license policy. But it is a good practice to split repo this way I think. May be in future.
We will cross that bridge when we get to it. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
barton`ello -
Greg KH -
John Andrews (swerdna)