Difference between revisions of "Category talk:Yum Repository"

From SME Server
Jump to navigationJump to search
m (Added signature)
(Marked WIP)
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
the exclude line needs work if it is a long line.
+
{{Template:WIP box|prbird}}--[[User:Prbird|Prbird]])
−
there are not allowed to be any spaces.
+
Should we add rpmforge, SME pulls rpms from it automatically already as part of updates and the buildsys
−
if there is one you get an error if there are an even number.
 
−
you get rubbish in the db
 
  
−
[[User:Snoble|Snoble]] 04:43, 7 April 2007 (EDT)
+
do we suggest using the rpm (below) or with the db as per the other repos
  
−
You are right, but I don't see any errors in the repositories in the Wiki at the moment. - [[User:Cactus|Cactus]] 04:49, 7 April 2007 (EDT)
+
https://rpmrepo.org/RPMforge/Using
  
−
---
+
Added rpmforge in db format, please check.
  
−
check dries history, now fixed
+
--[[User:Markleman|Markleman]] 23:48, 14 January 2010 (UTC)
−
[[User:Snoble|Snoble]] 05:02, 7 April 2007 (EDT)
 
  
−
----
+
== RPMForge page removed for now ==
  
−
can we rename reponame to reponame_repo, or similar
+
:Next time first ask before adding it. The way you added it it might have caused serious issues as RPMForge distributes pacakges that might be newer than on SME Server, therefore you need to exclude a lot of packages as otherwise undesired updates of SME Server packages could have lead to issues which the small development team can not resolve.
  
−
reponame may be used for other reasons later
+
:Besides that we already list the [[Dries]] and the [[Dag]] repositories, which together form RPMForge.
  
−
[[User:Snoble|Snoble]]
+
:For now I have removed RPMForge as I see no need for it ATM. Please be a little more carefull next time and raise your questions before taking action certainly when risks like this are involved. Thank in advance. <small>—&nbsp;[[User:Cactus|Cactus]] ([[User talk:Cactus|talk]]&nbsp;|&nbsp;[[Special:Contributions/Cactus|contribs]])&nbsp;</small> 17:24, 15 January 2010 (UTC)
  
−
== Protected Repos ==
+
== RPMForge page requested again :-) ==
  
−
Do the Repos need to be locked?
+
I agree that RPMforge used without care could cause problems, which is why I set it to be "enabled=0".
 +
I would still like to see it added, with appropriate 'excludes' to make it safe, because being a superset of Dag and Dries (and others) it contains a wealth of useful RPM for customizing our servers.
  
−
Linking them into the manual just adds a block of code. They need a heading. [[User:William|William_Syd]] 21:03, 9 July 2007 (EDT)
+
I also find it slightly odd that it is so dangerous to add when the SME7 documentation [http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter1] states "SME Server 7 uses many packages from CentOS and RPMForge".
  
−
== RE: Protected Repos==
+
So rather than delete RPMforge page I made why not add to or correct what I had started?
  
−
I have added a short description to the repository configuration information, perhaps I will extend it a little more. But I don't think that we should unprotect the repository configuration information:<br/>
+
Respectfully yours, --[[User:Markleman|Markleman]] 20:56, 15 January 2010 (UTC)
−
1. Not everybody needs to change this information, it is pretty critical information and everyone having a go at it could result in non-responsive systems or other strange errors we don't want the user community to suffer of.<br/>
+
 
−
2. The use of the pages with configuration information is templated by means of the [[Template:Repository]] so we do not need to look through all of the wiki pages and all configuration changes are changed at once, as well as a little (standard) information that is displayed when inserting the repository configuration anywhere in  the Wiki. - [[User:Cactus|Cactus]] 12:34, 10 July 2007 (EDT)
+
== Once again: no need for rpmforge ==
 +
 
 +
:It is not a superset. It is just a merge of packages in Dag and Dries and since they are already listed there is no need to list RPMForge as it would duplicate information and maintenance IMHO. <small>—&nbsp;[[User:Cactus|Cactus]] ([[User talk:Cactus|talk]]&nbsp;|&nbsp;[[Special:Contributions/Cactus|contribs]])&nbsp;</small> 16:24, 18 January 2010 (UTC)

Latest revision as of 23:36, 17 December 2013

Warning.png Work in Progress:
prbird has marked this page as a Work in Progress. The contents off this page may be in flux, please have a look at this page history the to see list of changes.


--Prbird)

Should we add rpmforge, SME pulls rpms from it automatically already as part of updates and the buildsys

do we suggest using the rpm (below) or with the db as per the other repos

https://rpmrepo.org/RPMforge/Using

Added rpmforge in db format, please check.

--Markleman 23:48, 14 January 2010 (UTC)

RPMForge page removed for now

Next time first ask before adding it. The way you added it it might have caused serious issues as RPMForge distributes pacakges that might be newer than on SME Server, therefore you need to exclude a lot of packages as otherwise undesired updates of SME Server packages could have lead to issues which the small development team can not resolve.
Besides that we already list the Dries and the Dag repositories, which together form RPMForge.
For now I have removed RPMForge as I see no need for it ATM. Please be a little more carefull next time and raise your questions before taking action certainly when risks like this are involved. Thank in advance. — Cactus (talk | contribs)  17:24, 15 January 2010 (UTC)

RPMForge page requested again :-)

I agree that RPMforge used without care could cause problems, which is why I set it to be "enabled=0". I would still like to see it added, with appropriate 'excludes' to make it safe, because being a superset of Dag and Dries (and others) it contains a wealth of useful RPM for customizing our servers.

I also find it slightly odd that it is so dangerous to add when the SME7 documentation [1] states "SME Server 7 uses many packages from CentOS and RPMForge".

So rather than delete RPMforge page I made why not add to or correct what I had started?

Respectfully yours, --Markleman 20:56, 15 January 2010 (UTC)

Once again: no need for rpmforge

It is not a superset. It is just a merge of packages in Dag and Dries and since they are already listed there is no need to list RPMForge as it would duplicate information and maintenance IMHO. — Cactus (talk | contribs)  16:24, 18 January 2010 (UTC)
Retrieved from "https://wiki.koozali.org/index.php?title=Category_talk:Yum_Repository&oldid=22752"