[opensuse-virtual] 'Virtualization' repo for Leap -- name, and activate?
I currently run/test xen-4.5.1_13-391.1.x86_64 <-- d.o.o://Virtualization/openSUSE_13.2 kernel-xen 4.3.0-1.g7b374a4-xen <-- d.o.o:///Kernel:/stable/standard on Opensuse 13.2. With Leap release, I see https://build.opensuse.org/project/repository_state/Virtualization/openSUSE_... , currently unpopulated. For other Leap repos being activated, the naming convention appears to be: .../openSUSE_Leap_42.1 (1) Should the Virtualization repo be similarly named? (2) Can whatever the correctly-named repo is to be get activated/populated? , if not already in the works ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Thu, Nov 05, PGNet Dev wrote:
For other Leap repos being activated, the naming convention appears to be:
.../openSUSE_Leap_42.1
(1) Should the Virtualization repo be similarly named?
The repository of non-home:* repos have various names: 125 openSUSE_Leap_42.1 37 openSUSE_42.1 8 openSUSE_42 1 openSUSE_Leap_42_1 1 openSUSE_Leap_42.1_PowerPC 1 openSUSE_Leap_42.1_Ports
(2) Can whatever the correctly-named repo is to be get activated/populated?
Yes. Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
I saw this for Tcl as well. I thought Leap was a kind of working name
like all openSUSE release have. And that it was just the number that
should be used, as in previous releases. At least it should be
consistent. I suspect the problem with standardizing and being
consistent (with Linux, you say? ;) ) is all the stuff in OBS that use
Leap in the name.
Anyway, what is the official name things should be known as in OBS?
Shouldn't it be only: openSUSE_42.1
On Fri, Nov 6, 2015 at 8:31 AM, Olaf Hering
On Thu, Nov 05, PGNet Dev wrote:
For other Leap repos being activated, the naming convention appears to be:
.../openSUSE_Leap_42.1
(1) Should the Virtualization repo be similarly named?
The repository of non-home:* repos have various names:
125 openSUSE_Leap_42.1 37 openSUSE_42.1 8 openSUSE_42 1 openSUSE_Leap_42_1 1 openSUSE_Leap_42.1_PowerPC 1 openSUSE_Leap_42.1_Ports
(2) Can whatever the correctly-named repo is to be get activated/populated?
Yes.
Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Fri, Nov 06, Roger Oberholtzer wrote:
Shouldn't it be only: openSUSE_42.1
Yes, it should! The repos below got it right. But, we follow the crowd. Olaf Application:ERP:Tryton:3.8 Application:Geo:Staging Documentation FATE Java:Factory Java:Factory:Sandbox LibreOffice:5.0 LibreOffice:Factory OBS:Server:Unstable Publishing Virtualization:Tests X11:Deepin X11:Enlightenment:E20 X11:LXQt X11:QtDesktop YaST:Head devel:languages:R:released devel:languages:erlang:Factory devel:openQA:stable devel:tools:statica filesystems filesystems:snapper hamradio server:dns spins:invis:benno spins:invis:common spins:invis:rootpack spins:invis:stable spins:invis:testing spins:invis:testing:perl-packages spins:invis:testing:python-packages spins:invis:testing:zarafa-freeze spins:invis:unstable windows:mingw windows:mingw:win32 windows:mingw:win32:compat windows:mingw:win64 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Fri, Nov 6, 2015 at 8:51 AM, Olaf Hering
On Fri, Nov 06, Roger Oberholtzer wrote:
Shouldn't it be only: openSUSE_42.1
Yes, it should! The repos below got it right. But, we follow the crowd.
As well as everything in: home:rogeroberholtzer OBS uses openSUSE_42.1 by default. You have to go out of your way to put results somewhere else.... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Fri, Nov 06, Roger Oberholtzer wrote:
OBS uses openSUSE_42.1 by default. You have to go out of your way to put results somewhere else....
Did you use the web interface to add the Leap repo? Right now the name of such repo is "openSUSE_Leap_42.1". Maybe in the past it used to be just "openSUSE_42.1". Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Don't recall. Maybe I edited things direct. Still, it really needs to
be cleaned up. I see that my definitions are like:
<repository name="openSUSE_42.1">
<path project="openSUSE:Leap:42.1" repository="standard"/>
<arch>x86_64</arch>
</repository>
So I publish to openSUSE_42.1, but I have to get things from openSUSE:Leap:42.1
Messy...
On Fri, Nov 6, 2015 at 9:17 AM, Olaf Hering
On Fri, Nov 06, Roger Oberholtzer wrote:
OBS uses openSUSE_42.1 by default. You have to go out of your way to put results somewhere else....
Did you use the web interface to add the Leap repo? Right now the name of such repo is "openSUSE_Leap_42.1". Maybe in the past it used to be just "openSUSE_42.1".
Olaf
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
(2) Can whatever the correctly-named repo is to be get activated/populated? Yes.
Thanks. Noted as http://download.opensuse.org/repositories/Virtualization/openSUSE_Leap_42.1/
Shouldn't it be only: openSUSE_42.1
Yes, it should! The repos below got it right. But, we follow the crowd.
This tangent should probably be (also) addressed on a different/broader ML ... The whole situation is quite messy, atm -- and, quite familiar. I've one particularly "Frankenstein'd" machine, running Opensuse "last release" (13.2 in this case), with lots of update repos added; it represents a superset of the various repos that are used around here. At each major release, I run checks on the availability of next-release's repos. Neither testing, nor certainly upgrades, get much activity at all until all the target repos are active, populated, and stable. Currently, for example, a number of v42.1 repos ARE already populated at the "follow the crowd"-named baseurls, baseurl=.../openSUSE_Leap_42.1 These other-named variants exist Documentation:/Tools/openSUSE_42 Java:/Factory/openSUSE_42.1 LibreOffice:/Factory/openSUSE_42.1 While, still, none of these, nor any v42-name-variant, do not exist at all yet; note, they're all 'non-home' repos: network:/chromium/openSUSE_Leap_42.1 editors/openSUSE_Leap_42.1 devel:/gcc/openSUSE_Leap_42.1 KDE:/Unstable:/Applications/KDE_Unstable_Frameworks_openSUSE_Leap_42.1 KDE:/Unstable:/Extra/KDE_Unstable_Frameworks_openSUSE_Leap_42.1 devel:/languages:/lua/openSUSE_Leap_42.1 multimedia:/color_management/openSUSE_Leap_42.1 network:/vpn/openSUSE_Leap_42.1/ isv:/ownCloud:/community/openSUSE_Leap_42.1 security:/logging:/elma:/devel/openSUSE_Leap_42.1 security:/Stunnel/openSUSE_Leap_42.1 shells/openSUSE_Leap_42.1 server:/messaging/openSUSE_Leap_42.1 systemsmanagement:/puppet/openSUSE_Leap_42.1 X11:/common:/Factory/openSUSE_Leap_42.1 It'd be quite helpful to have a sweep of wrong-named & inactive next-release repos done, with notifications to each maintainer. Atm, it's file-a-bug-for-each-repo. Some form of automation, or at least defined/expected process, would be useful. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (3)
-
Olaf Hering -
PGNet Dev -
Roger Oberholtzer