PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000768PacketFencecorepublic2009-08-11 10:102015-02-13 15:26
Reporterobilodeau 
Assigned Toobilodeau 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0000768: new packetfence install on centos with rpmforge pulls in postgresql..?
Descriptionthis might be invalidated by the new yum rpm repo installation mode, we should confirm
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-08-11 10:10obilodeauNew Issue
2009-08-19 15:55obilodeauStatusnew => assigned
2009-08-19 15:55obilodeauAssigned To => obilodeau
2009-08-24 16:16obilodeauNote Added: 0001301
2009-08-24 16:16obilodeauReproducibilityhave not tried => always
2009-11-30 15:33obilodeauNote Added: 0001421
2009-11-30 15:33obilodeauCategoryfuture => 1.8.6
2009-11-30 16:36obilodeauNote Added: 0001424
2009-11-30 18:00obilodeauProjectPacketFence => PacketFence 1.9
2009-11-30 18:00obilodeauNote Added: 0001429
2009-11-30 18:00obilodeauCategory1.8.6 => future
2010-04-15 17:43obilodeauProjectPacketFence 1.9 => PacketFence
2011-01-18 11:57obilodeauSummarynew packetfence 1.8.4 install on centos 5.3 with rpmforge pulls in postgresql..? => new packetfence install on centos with rpmforge pulls in postgresql..?
2011-01-18 12:02obilodeauTarget Version => 2.1.0
2011-03-03 15:15obilodeauTarget Version2.1.0 => +1
2011-03-03 15:19obilodeauTarget Version+1 => +2
2011-03-25 14:15fgaudreaultNote Added: 0001995
2011-03-25 14:24obilodeauNote Added: 0001996
2012-02-29 10:58obilodeauCategoryfuture => core
2015-02-13 15:26lmunroNote Added: 0003714
2015-02-13 15:26lmunroStatusassigned => closed

Notes
(0001301)
obilodeau   
2009-08-24 16:16   
I was able to reproduce using 1.8.5's new rpm repo.

It does pull in postgresql
postgresql i386 8.1.11-1.el5_1.1 base 2.9 M

but that could well be because of perl's dbd-pg:
perl-DBD-Pg i386 2.13.1-1.el5.rf rpmforge 308 k
(0001421)
obilodeau   
2009-11-30 15:33   
targeted for 1.8.6
(0001424)
obilodeau   
2009-11-30 16:36   
its pulled in by perl-CGI-Session
(0001429)
obilodeau   
2009-11-30 18:00   
not easy to fix after all, I'll look at it later
(0001995)
fgaudreault   
2011-03-25 14:15   
I dont see anything related to PG-SQL in perl-CGI-Session :

BuildRequires: perl(CGI) >= 3.26
BuildRequires: perl(Data::Dumper)
BuildRequires: perl(Digest::MD5)
BuildRequires: perl(Scalar::Util)
BuildRequires: perl(Test::More)
Requires: perl(CGI) >= 3.26
Requires: perl(Data::Dumper)
Requires: perl(Digest::MD5)
Requires: perl(Scalar::Util)
Requires: perl(Test::More)
(0001996)
obilodeau   
2011-03-25 14:24   
it might have been fixed upstream already

To reproduce, I would suggest pulling packetfence on a clean centos base system and looking if postgresql is in the list or not.
(0003714)
lmunro   
2015-02-13 15:26   
Old issues.
Most are not relevant to PF 4 and up.

Let's reopen the ones that matter when we move to github.