Project

General

Profile

Actions

Architecture #1545

closed

Fix hack for rudder-reports SuSE RPM

Added by Nicolas PERRON over 13 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
Packaging
Effort required:
Name check:
Fix check:
Regression:

Description

In order to ensure being capable of connecting to postgresql, rudder-reports add 2 lines in the begining of pg_hba.conf and reload postgresql.

The lines need to be correctly placed in the file (somewhere in the middle :)

Actions #1

Updated by Jonathan CLARKE over 13 years ago

  • Target version set to 10
Actions #2

Updated by François ARMAND about 13 years ago

  • Status changed from New to Discussion
  • Target version deleted (10)

I think that was done recently, no ?

Actions #3

Updated by Jonathan CLARKE about 13 years ago

  • Status changed from Discussion to 2
  • Priority changed from 4 to 3
  • Target version set to 23

François ARMAND wrote:

I think that was done recently, no ?

No, not yet.

Actions #4

Updated by Jonathan CLARKE about 13 years ago

  • Target version changed from 23 to 18
Actions #5

Updated by François ARMAND about 13 years ago

  • Target version changed from 18 to 2.4.0~alpha1
Actions #6

Updated by Jonathan CLARKE about 13 years ago

  • Target version changed from 2.4.0~alpha1 to 2.4.0~alpha2
Actions #7

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
Actions #8

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
Actions #9

Updated by François ARMAND almost 13 years ago

  • Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
Actions #10

Updated by Jonathan CLARKE almost 13 years ago

  • Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6
Actions #11

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~alpha6 to 2.3.8
Actions #12

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.3.8 to 2.3.9
Actions #13

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.3.9 to 2.4.0~rc1
Actions #14

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.4.0~rc1 to 2.3.9
Actions #15

Updated by Nicolas PERRON about 12 years ago

  • Status changed from 2 to Discussion
  • Assignee set to Jonathan CLARKE

I suppose we should "fix" the package rudder-reports with using the same implementation with CFEngine instead of packaging ?

Actions #16

Updated by Nicolas PERRON about 12 years ago

  • Target version changed from 2.3.9 to 2.3.10
Actions #17

Updated by François ARMAND about 12 years ago

  • Tracker changed from Bug to Architecture
  • Description updated (diff)
  • Status changed from Discussion to 8
  • Assignee changed from Jonathan CLARKE to Nicolas PERRON
  • Target version changed from 2.3.10 to Ideas (not version specific)

This is clearly not a bug, and will be added in some next version.

Actions #18

Updated by Jonathan CLARKE about 12 years ago

Nicolas PERRON wrote:

I suppose we should "fix" the package rudder-reports with using the same implementation with CFEngine instead of packaging ?

Yes, this is the right approach.

Actions #19

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #20

Updated by Nicolas PERRON over 11 years ago

  • Assignee deleted (Nicolas PERRON)

I've never worked on it

Actions #21

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions #22

Updated by Benoît PECCATTE over 9 years ago

  • Status changed from 8 to New
Actions #23

Updated by Benoît PECCATTE about 8 years ago

I suppose we should "fix" the package rudder-reports with using the same implementation with CFEngine instead of packaging ?

I do not understand this sentence at all.

Moreover the issue description doesn't match reality :

In order to ensure being capable of connecting to postgresql, rudder-reports add 2 lines in the begining of pg_hba.conf and reload postgresql." 

rudder-reports does nothing, it is postgres-check in system technique that does this.

The lines need to be correctly placed in the file (somewhere in the middle :)

Since it is already done, why should they be placed again in the file ?
Actions #24

Updated by Benoît PECCATTE about 8 years ago

  • Status changed from New to Rejected

This seems to be done in #2207

Actions

Also available in: Atom PDF