Jira (PUP-8664) rpm package provider is too specific

2019-07-03 Thread Gheorghe Popescu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Fix Version/s: 
 PUP 6.4.3  
 
 
Fix Version/s: 
 PUP 6.0.10  
 
 
Fix Version/s: 
 PUP 5.5.15  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246189.1524007177000.4343.1562143320167%40Atlassian.JIRA.
For more options, visit 

Jira (PUP-8664) rpm package provider is too specific

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 cs_pr_review  resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246189.1524007177000.44597.1560363120401%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-06-10 Thread Oana Tanasoiu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Oana Tanasoiu  
 
 
Fix Version/s: 
 PUP 6.5.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246189.1524007177000.39345.1560150421365%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-05-02 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03, PR - 2019-04-17, PR - 2019-05-02 , PR - 2019-05-15  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-04-17 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03, PR - 2019-04-17 , PR - 2019-05-02  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-04-08 Thread Sebastian Miclea (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Miclea assigned an issue to Sebastian Miclea  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Sebastian Miclea  
 
 
Assignee: 
 Sebastian Miclea  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03 , PR - 2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-03-27 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-04-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-03-27 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-03-25 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Sprint: 
 PR - Triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-03-25 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Team: 
 Platform OS Puppet Romania  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-09-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Coremunity Platform OS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-05-15 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Needs Priority Normal  
 
 
CS Impact: 
 The rpm provider should allow for a single run to ensure absent one package and ensure present another.  The fact this fails in any case is a bug worth fixing.  There is already a PR attached.  
 
 
CS Severity: 
 3 - Serious  
 
 
CS Business Value: 
 3 -   
 
 
CS Frequency: 
 1 - 1-5% of Customers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
  

Jira (PUP-8664) rpm package provider is too specific

2018-05-15 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
Labels: 
 cs_pr_review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-05-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
CS Priority: 
 Needs Priority  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-05-13 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-8664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: rpm package provider is too specific   
 

  
 
 
 
 

 
 Another situation where 'caching' brings unexpected results. RHEL7 supplies subversion version 1.7, which is old and we were asked to upgrade it. Wandisco provides their version of RPMs, but without separating libraries into a different RPM, like RedHat does, so we have to force uninstalling subversion-libs package before installing packages from Wandisco. Here is the code:  
 
 
 
 
   yumrepo { 'wandisco':  
 
 
 baseurl => "http://opensource.wandisco.com/rhel/\$releasever/svn-${version}/RPMS/\$basearch",  
 
 
 descr   => 'Wandisco Subversion',  
 
 
 gpgcheck=> '1',  
 
 
 gpgkey  => 'http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco',  
 
 
 includepkgs => 'mod_dav_svn serf libserf subversion*',  
 
 
   }  
 
 
    
 
 
   # RHEL library conflicts with wandisco binary  
 
 
   package { 'subversion-libs':  
 
 
 ensure => purged,  
 
 
   }  
 

Jira (PUP-8664) rpm package provider is too specific

2018-04-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-04-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 

  
 
 
 
 

 
 *Puppet Version: 5.3.5 (and older)* *Puppet Server Version: N/A* *OS Name/Version: Centos/Redhat*The uninstall method in the rpm package provider is more specific than the package resource it is uninstalling, and uses a cache that can become out of date by the time it executes.*Desired Behavior:*Unconditionally uninstall a package when conditions are not specified.*Actual Behavior:*Example:{code:java}  package { 'cronie-anacron':    ensure  => absent,    require => Package['cronie-noanacron']  }  package { 'cronie-noanacron':    ensure => installed,  }{code} {code:java}yum[3546]: Updated: cronie-anacron-1.4.11-19.el7.x86_64 yum[3546]: Updated: cronie-1.4.11-19.el7.x86_64 yum[3546]: Installed: cronie-noanacron-1.4.11-19.el7.x86_64puppet-agent[1371]: (/Stage[main]/Package[cronie-noanacron]/ensure) created puppet-agent[1371]: Execution of '/usr/bin/rpm -e cronie-anacron-1.4.11-17.el7.x86_64' returned 1: error: package cronie-anacron-1.4.11-17.el7.x86_64 is not installed puppet-agent[1371]: (/Stage[main]/Package[cronie-anacron]/ensure) change from '1.4.11-17.el7' to 'absent' failed: Execution of '/usr/bin/rpm -e cronie-anacron-1.4.11-17.el7.x86_64' returned 1: error: package cronie-anacron-1.4.11-17.el7.x86_64 is not installed{code}  To reset the test environment after that puppet run, download cronie-1.4.11-14.el7.x86_64.rpm and cronie-anacron-1.4.11-14.el7.x86_64.rpm and run:{code:java}rpm -e cronie cronie-noanacron crontabs ; yum install -y cronie-* ; rpm -qa | grep cron ; puppet agent -t ; rpm -qa | grep cron{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 

Jira (PUP-8664) rpm package provider is too specific

2018-04-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Method Found: 
 Needs Assessment Customer Feedback  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-04-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Priority: 
 Normal Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2018-04-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: rpm package provider is too specific   
 

  
 
 
 
 

 
 Example-Specific Notes: cronie-anacron can't be installed without installing cronie-noanacron first as an alternative. By installing cronie-noanacron, cronie gets updated as a dependency:  
 
 
 
 
 # rpm -q --requires cronie-noanacron  
 
 
 cronie = 1.4.11-19.el7
  
 
 
 
    That in turn updates cronie-anacron:    
 
 
 
 
 # rpm -q --requires cronie-anacron  
 
 
 cronie = 1.4.11-19.el7
  
 
 
 
    So by the time the rpm -e command runs, the cache is no longer valid.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (PUP-8664) rpm package provider is too specific

2018-04-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.3.5  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2018/04/17 4:19 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Puppet Version: 5.3.5 (and older) Puppet Server Version: N/A OS Name/Version: Centos/Redhat The uninstall method in the rpm package provider is more specific than the package resource it is uninstalling, and uses a cache that can become out of date by the time it executes. Desired Behavior: Unconditionally uninstall a package when conditions are not specified. Actual Behavior: Example:  
 
 
 
 
   package { 'cronie-anacron':  
 
 
     ensure  => absent,  
 
 
     require => Package['cronie-noanacron']  
 
 
   }