[root@Nethserver ~]# config setprop subscription ExtraRepositories testthis
[root@Nethserver ~]# signal-event software-repos-save
[root@Nethserver ~]# cat /etc/nethserver/pkginfo.conf
# ================= DO NOT MODIFY THIS FILE =================
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at NethServer official site: https://www.nethserver.org
#
#
#
# This is the list of YUM repositories that have their groups listed
# on the Software Center UI page, through the pkginfo helper.
#
# One repository identifier per line
#
sb-nethserver-updates
testthis
[root@Nethserver ~]# cat /etc/nethserver/eorepo.conf
# ================= DO NOT MODIFY THIS FILE =================
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at NethServer official site: https://www.nethserver.org
#
#
#
# This file is read by software-repos-save event
#
# Listed repositories will be enabled, everything else will be disabled
#
# Blank lines and lines beginning with "#" are ignored
#
sb-base
sb-updates
sb-epel
sb-extras
sb-centos-sclo-rh
sb-centos-sclo-sclo
sb-nethserver-base
sb-nethserver-updates
testthis
stephdl
# Add my repositories in
jdoss-wireguard
nordvpn
PlexRepo
tor
[root@Nethserver ~]#
One little worry: can enabling the (comps) groups off all extra repo’s have some unwanted side effects?
(I mean if a 3party repo has groups not being nethserver-modules )
3rd party repo should have the groups metadata if they want to show packages on the Software Center.
There could be a problem only if different modules have the same id, but it’s very unlikely to happen.
So, in the end, it will be safe to have all 3rd party repositories available through the Software Center.
thank, this has been asked few time in the past, I am not sure it worth efforts right now, I prefer to waste my time on a mirror architecture or on some modules.
It is a third repository that you must install manually like other of markus,dan…
No need to roll back, just update as you used to do.
Some Background:
This testing package is versioned 3.6.7-1.4.g100b078 the released update is 3.6.8-1.
While technically both packages are the same the released one will be considered an update by yum and (as a mater of speech) be (re)installed.
(EDIT: it can take a while before this update lands in the subscription repo, just wait for it )
)
)