Project

General

Profile

Actions
Copy link

Bug #4675

closed

When installing and updating an identical package with rpmPackageManagement 5.1, we have only one reporting

Added by Nicolas CHARLES about 10 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
Techniques
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If I want to install a package A, and update this package A to a specific version (to mimic the addupdate), the directive make only one report about A

It seems that cfengine is completly skipping the second promise, even if the parameters are differents (version, ifvarclass, etc)

and so we only have one report about package A, and so unknown status

This is most likely to be a cfengine bug :/

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - Bug #8034: When we manage twice a same package in rpm package management, we don't get the second reportReleasedAlexis Mousset2016-03-03Actions
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 133 to 2.9.5
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.9.5 to 2.9.6
Actions
Copy link
 #3

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.9.6 to 2.9.7
Actions
Copy link
 #4

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.9.7 to 150
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 150 to 2.10.4
Actions
Copy link
 #6

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.10.4 to 2.10.5
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions
Copy link
 #8

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #14

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 2.11.18
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #36

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #37

Updated by Alexis Mousset about 7 years ago

  • Status changed from New to Rejected

This has been fixed in the latest releases, by using the id of the package in addition to its name in reporting.

Actions
Copy link
 #38

Updated by Alexis Mousset about 7 years ago

  • Is duplicate of Bug #8034: When we manage twice a same package in rpm package management, we don't get the second report added
Actions
Copy link

Also available in: Atom PDF