CentOS docs - Dec 2014 - CentOS forum search link in http://wiki.centos.org/AdditionalResources/Repositories under Atomic Repo

[
https://www.centos.org/search.php?query=atomicorp&mid=30&action=showall&andor=AND
forum search] returns a 404.


Can the forum search https://www.centos.org/forums/search.php? be used with
parameters that will provide the supporting material for the warning "Many
CentOS users have had problems after enabling this repo"?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-docs/attachments/20141212/ef28eee0/attachment-0002.html>

Maybe I posted this a little late on Friday for anyone to take an interest
in suggesting a properly built search URL for the current forum software,
so I did some experiments which led to the suggestion added below the copy
of the previous post.

On Fri, Dec 12, 2014 at 6:52 PM, I wrote:
> [
https://www.centos.org/search.php?query=atomicorp&mid=30&action=showall&andor=AND
forum search] returns a 404.
>
> Can the forum search https://www.centos.org/forums/search.php? be used
with parameters that will provide the supporting material for the warning
"Many CentOS users have had problems after enabling this
repo"?
>
My experimentation indicates this URL:
https://www.centos.org/forums/search.php?submit=Search&keywords=atomicorp+repo
returns 13 postings that discuss to use the Atomicorp repo with less than
satisfactory results.

Do those 13 postings adequately support the admonition to use the Atomicorp
repo only with particular care?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-docs/attachments/20141213/e5cb1a3e/attachment-0002.html>

On 14/12/14 03:59, PatrickD Garvey wrote:
> Maybe I posted this a little late on Friday for anyone to take an
> interest in suggesting a properly built search URL for the current
> forum software, so I did some experiments which led to the suggestion
> added below the copy of the previous post.
>
> On Fri, Dec 12, 2014 at 6:52 PM, I wrote:
> >
>
[https://www.centos.org/search.php?query=atomicorp&mid=30&action=showall&andor=AND
> forum search] returns a 404.
> >                              
>
>
> > Can the forum search https://www.centos.org/forums/search.php? be
> used with parameters that will provide the supporting material for the
> warning "Many CentOS users have had problems after enabling this
repo"?
> >
>
> My experimentation indicates this URL:
>
https://www.centos.org/forums/search.php?submit=Search&keywords=atomicorp+repo
> returns 13 postings that discuss to use the Atomicorp repo with less
> than satisfactory results.
>
> Do those 13 postings adequately support the admonition to use the
> Atomicorp repo only with particular care?
All third party repos should be used with care but the Atomic one is
known to contain many packages that overwrite core packages from the
CentOS base and updates repos without warning. Mere installation of the
atomic repo will proceed to update all those packages that are in that
repo and that also reside in CentOS base and updates repos unless the
end user has already configured yum-plugin-priorities to exclude
duplicates from lower priority repos. Not many first time users bother
to do this before they've been bitten once (or more!).

As an example, I went to
https://www.atomicorp.com/channels/atomic/centos/6/x86_64/RPMS/ and went
through the list of packages there and made a list of what's there. I
then ran

yum list --disablerepo=\* --enablerepo=base,updates  GeoOP Pound PyYAML
alien apachetop aqueduct\* asl-lite atop bglibs boostcompat\* ccache
clam\* clapf cloud-utils\* csync2 daemontools\* daq\* dcc denyhosts dirb
dkms dotconf dpkg dselect firebird\* firedns\* freetds\* galera\*
gperftools gpsd\* greenbone\* gsd havegd http-parser\* hydra\* iftop\*
imapsync incron\ inotify-tools jemalloc kmodtool ldns libbsd\*
libc-client libedit libident libmcrypt libmemcached libmicrohttpd libmnl
libnetfilter_queue libnfnetlink libopendkim librsync libssh libssh2
libuv libvirt libvirt-client libvirt-python libvpx libyaml lsyncd
lua-socket luajit lynis maildrop mariadb\* masscan memcached mhash
mingw32\* miniupnpc mod_fcgid mod_cgroup mod_qos mod_rpaf mod_ruid2
mod_security mod_sed mydumper mysql mysql-bench mysql-libs mysql-server
mysqlcient16 ncrack nettle nginx ngircd nikto nmap\* opendkim openpgm
openssl-compat\* openvas\* ossec ovaldi pyPdf pylibacl pysvn
python-BeautifulSoup python-SocksiPy python-clamd python-cluster
python-esmre python-futures python-guess-language python-httplib2
python-miniupnpc python-msgpack python-nltk python-pdfminer
python-pybloomfiltermmap python-zmq pyxattr pyzor qgreylist qmail\*
qt-mobility qtwebkit razoragents rblcheck rbldnsd rdiff-backup recode
redis reprepro roadsend salt salt-master salt-minion scap-security-guide
scapy scons secstate skdet skipfish snort socat spamassassin spamdyke
sqlite\* sqlninja sshpass sudosh sudosh2 supervise-scripts suricata
sysbench tidy tnef ucspi-tcp uscpi-unix unbound\* unhide uni2ascii v8
varnish w3af wapiti wmi xalan-c xerces-c xl2tpd

on my CentOS 6.6 system. As you can see from that command, I disabled
all other third party repos that I have installed so that only those
packages that are in the CentOS base and updates repos would be listed.
My command may contain typos and may also not be a complete list of all
packages there. For example there are lots of perl-* and php-* packages
in atomic that I could not be bothered to include because there were so
many of them so I omitted them but all of those have the potential to
overwrite core packages. The list I got back was as follows:

Installed Packages
libedit.x86_64                        
2.11-4.20080712cvs.1.el6            
@anaconda-CentOS-201311291202.x86_64/6.5
libmnl.x86_64                         
1.0.2-3.el6                         
@anaconda-CentOS-201311291202.x86_64/6.5
libnfnetlink.x86_64                   
1.0.0-1.el6                         
@anaconda-CentOS-201311291202.x86_64/6.5
libssh2.i686                          
1.4.2-1.el6                         
@base                                  
libssh2.x86_64                        
1.4.2-1.el6                         
@anaconda-CentOS-201311291202.x86_64/6.5
libvpx.i686                           
1.3.0-5.el6_5                       
@updates                               
libvpx.x86_64                         
1.3.0-5.el6_5                       
@updates                               
mysql.x86_64                          
5.1.73-3.el6_5                      
@updates                               
mysql-libs.x86_64                     
5.1.73-3.el6_5                      
@updates                               
mysql-server.x86_64                   
5.1.73-3.el6_5                      
@updates                               
nmap.x86_64                           
2:5.51-4.el6                        
@fasttrack                             
sqlite.i686                           
3.6.20-1.el6                        
@base                                  
sqlite.x86_64                         
3.6.20-1.el6                        
@anaconda-CentOS-201311291202.x86_64/6.5
Available Packages
PyYAML.i686                           
3.10-3.1.el6                        
updates                                
PyYAML.x86_64                         
3.10-3.1.el6                        
updates                                
libc-client.i686                      
2007e-11.el6                        
base                                   
libc-client.x86_64                    
2007e-11.el6                        
base                                   
libedit.i686                          
2.11-4.20080712cvs.1.el6            
base                                   
libmemcached.i686                     
0.31-1.1.el6                        
base                                   
libmemcached.x86_64                   
0.31-1.1.el6                        
base                                   
libmicrohttpd.i686                    
0.9.33-4.el6                        
base                                   
libmicrohttpd.x86_64                  
0.9.33-4.el6                        
base                                   
libmnl.i686                           
1.0.2-3.el6                         
base                                   
libnetfilter_queue.i686               
1.0.1-3.el6                         
base                                   
libnetfilter_queue.x86_64             
1.0.1-3.el6                         
base                                   
libnfnetlink.i686                     
1.0.0-1.el6                         
base                                   
libvirt.x86_64                        
0.10.2-46.el6_6.2                   
updates                                
libvirt-client.i686                   
0.10.2-46.el6_6.2                   
updates                                
libvirt-client.x86_64                 
0.10.2-46.el6_6.2                   
updates                                
libvirt-python.x86_64                 
0.10.2-46.el6_6.2                   
updates                                
libyaml.i686                          
0.1.3-1.4.el6                       
base                                   
libyaml.x86_64                        
0.1.3-1.4.el6                       
base                                   
memcached.x86_64                      
1.4.4-3.el6                         
base                                   
mysql-bench.x86_64                    
5.1.73-3.el6_5                      
base                                   
mysql-libs.i686                       
5.1.73-3.el6_5                      
base                                   
nmap-frontend.noarch                  
2:5.51-4.el6                        
base                                   
recode.i686                           
3.6-28.1.el6                        
base                                   
recode.x86_64                         
3.6-28.1.el6                        
base                                   
scap-security-guide.noarch            
0.1.18-3.el6                        
base                                   
scons.noarch                          
2.0.1-1.el6                         
base                                   
spamassassin.x86_64                   
3.3.1-3.el6                         
base                                   
sqlite-devel.i686                     
3.6.20-1.el6                        
base                                   
sqlite-devel.x86_64                   
3.6.20-1.el6                        
base                                   
sqlite-doc.x86_64                     
3.6.20-1.el6                        
base                                   
sqlite-tcl.x86_64                     
3.6.20-1.el6                        
base                                   
tidy.x86_64                           
0.99.0-19.20070615.1.el6            
base                                   
xerces-c.i686                         
3.0.1-20.el6                        
base                                   
xerces-c.x86_64                       
3.0.1-20.el6                         base

Last time I looked, yum used sqlite as a database so replacing sqlite is
a Really Bad Idea(tm). Replacing the distro php, mysql and various perl
packages is also not a good thing nor am I very keen on it replacing
libvirt nor do I look the look of many of the other lib* packages listed.

May I ask: do you work for atomicorp?

Trevor

I did the last major rewrite of the AdditionalRepos page, in large part
because of issues we see repeatedly on the IRC channels. The repos placed
in the "known problem" section are there for a good reason -- they
replace
base packages by default, or they're poorly maintained, leading to security
issues. Or both.

Atomic falls squarely into the former category -- it replaces key parts of
the base OS with its own packages, and it has broken yum on numerous
occasions in the process. While fixable, for most inexperienced users this
is difficult and the best way forward is a full reinstall.

Any repo that does that, repeatedly, deserves to be placed in that section.


On Sat, Dec 13, 2014 at 10:59 PM, PatrickD Garvey <patrickdgarveyt at
gmail.com
> wrote:
> Maybe I posted this a little late on Friday for anyone to take an interest
> in suggesting a properly built search URL for the current forum software,
> so I did some experiments which led to the suggestion added below the copy
> of the previous post.
>
> On Fri, Dec 12, 2014 at 6:52 PM, I wrote:
> > [
>
https://www.centos.org/search.php?query=atomicorp&mid=30&action=showall&andor=AND
> forum search] returns a 404.
> >
>
>
> > Can the forum search https://www.centos.org/forums/search.php? be used
> with parameters that will provide the supporting material for the warning
> "Many CentOS users have had problems after enabling this repo"?
> >
>
> My experimentation indicates this URL:
>
>
https://www.centos.org/forums/search.php?submit=Search&amp;keywords=atomicorp+repo
> returns 13 postings that discuss to use the Atomicorp repo with less than
> satisfactory results.
>
> Do those 13 postings adequately support the admonition to use the
> Atomicorp repo only with particular care?
>
> _______________________________________________
> CentOS-docs mailing list
> CentOS-docs at centos.org
> http://lists.centos.org/mailman/listinfo/centos-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-docs/attachments/20141214/84295cac/attachment-0002.html>