On 11/23/2010 06:28 PM, Ralf Corsepius wrote:
> On 11/23/2010 07:36 PM, Jan Vcelak wrote:
>> On Tuesday 23 November 2010 19:13:09, Panu Matilainen wrote:
>>> Another related thing is that Berkeley DB which openldap uses is
>>> notoriously picky about getting updated. I'm fairly certain openldap doe
On Wed, 24 Nov 2010 11:03:41 +0100, Ralf wrote:
> On 11/24/2010 10:45 AM, Matej Cepl wrote:
> > Dne 24.11.2010 03:28, Ralf Corsepius napsal(a):
> >> No, it's not your fault (Or at least only partially). A functional QA
> >> would catch such kind of breakages.
> >
> > Yes, but functional QA would r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/2010 08:54 PM, Ben Boeckel wrote:
> Jan Vcelak wrote:
>> This is the problem: The database migration could take a really long time. I
>> have testing data with 56 entries (nodes) - exporting (slapcat) is quite
>> fast,
>> but importing (sl
On 11/24/2010 10:45 AM, Matej Cepl wrote:
> Dne 24.11.2010 03:28, Ralf Corsepius napsal(a):
>> No, it's not your fault (Or at least only partially). A functional QA
>> would catch such kind of breakages.
>
> Yes, but functional QA would require more manpower than Fedora QA
> currently has.
That's
Dne 24.11.2010 03:28, Ralf Corsepius napsal(a):
> No, it's not your fault (Or at least only partially). A functional QA
> would catch such kind of breakages.
Yes, but functional QA would require more manpower than Fedora QA
currently has.
Matěj
--
devel mailing list
devel@lists.fedoraproject.o
On 11/23/2010 07:36 PM, Jan Vcelak wrote:
> On Tuesday 23 November 2010 19:13:09, Panu Matilainen wrote:
>> Another related thing is that Berkeley DB which openldap uses is
>> notoriously picky about getting updated. I'm fairly certain openldap does
>> not update their bundled BDB version to preven
Jan Vcelak wrote:
> This is the problem: The database migration could take a really long time. I
> have testing data with 56 entries (nodes) - exporting (slapcat) is quite
> fast,
> but importing (slapadd) takes around 10 seconds.
Hmm. I've seen selinux-policy-targeted take longer than this on
On Tue, 23 Nov 2010, Jan Vcelak wrote:
> On Tuesday 23 November 2010 19:13:09, Panu Matilainen wrote:
>> Another related thing is that Berkeley DB which openldap uses is
>> notoriously picky about getting updated. I'm fairly certain openldap does
>> not update their bundled BDB version to prevent
On Tue, 23 Nov 2010, Ralf Corsepius wrote:
> On 11/23/2010 05:30 PM, Jesse Keating wrote:
>> On 11/23/10 5:55 AM, Jan Vcelak wrote:
>>> Hi!
>>>
>>> Currently, the upgrade process in openldap looks like this:
>>> * during db4 package upgrade run db_upgrade (%triggerin and %triggerun)
>>> * if minor
On Tue, 2010-11-23 at 18:21 +0100, Ralf Corsepius wrote:
> > Why was this update made on F14 in the first place?
> >
> IMO, this is the wrong question.
>
> The better questions would be - How could it happen, this package made
> it into updates, dispite all this QA bureaucracy is in place?
Reme
On 11/23/2010 05:30 PM, Jesse Keating wrote:
> On 11/23/10 5:55 AM, Jan Vcelak wrote:
>> Hi!
>>
>> Currently, the upgrade process in openldap looks like this:
>> * during db4 package upgrade run db_upgrade (%triggerin and %triggerun)
>> * if minor version of openldap changes (e.g. 2.3 -> 2.4), exp
Once upon a time, Jan Vcelak said:
> Am I allowed to write some additional output in %pre/%post scriptlets? And
> shall I use stdout or stderr? I haven't found it in guidelines.
No, because there's no telling where it will go.
> This is the problem: The database migration could take a really lo
On 11/23/10 5:55 AM, Jan Vcelak wrote:
> Hi!
>
> Currently, the upgrade process in openldap looks like this:
> * during db4 package upgrade run db_upgrade (%triggerin and %triggerun)
> * if minor version of openldap changes (e.g. 2.3 -> 2.4), export the database,
> delete it and import it back (
On Tue, 2010-11-23 at 17:09 +0100, Jan Vcelak wrote:
> Am I allowed to write some additional output in %pre/%post scriptlets? And
> shall I use stdout or stderr? I haven't found it in guidelines.
I was always told "no output allowed", which is sad. Sure, it might not
be seen in all cases. What w
On Tue, 2010-11-23 at 17:09 +0100, Jan Vcelak wrote:
> This is the problem: The database migration could take a really long time. I
> have testing data with 56 entries (nodes) - exporting (slapcat) is quite
> fast,
> but importing (slapadd) takes around 10 seconds.
>
> Imagine you have a large
On Tue, 2010-11-23 at 14:55 +0100, Jan Vcelak wrote:
> Patric, thank you for reporting this. And sorry for the difficulties.
You're welcome. And never mind for the difficulties: I understand your
trouble and I wouldn't be in such a sh... myself !
I succeeded in restoring the LDAP usability by do
On Tue, 23 Nov 2010, Panu Matilainen wrote:
> On Tue, 23 Nov 2010, Paul Howarth wrote:
>
>> On 23/11/10 10:11, Patrick MONNERAT wrote:
>>> While applying today's updates on a machine running a slapd server, the
>>> following error occurred:
>>>
>>> Stopping slapd: [ OK ]
>>> Checking configurati
On Tue, 23 Nov 2010, Paul Howarth wrote:
> On 23/11/10 10:11, Patrick MONNERAT wrote:
>> While applying today's updates on a machine running a slapd server, the
>> following error occurred:
>>
>> Stopping slapd: [ OK ]
>> Checking configuration files for slapd: [FAILED]
>> bdb(dc=linuxdev,dc=dat
On 23/11/10 10:11, Patrick MONNERAT wrote:
> While applying today's updates on a machine running a slapd server, the
> following error occurred:
>
> Stopping slapd: [ OK ]
> Checking configuration files for slapd: [FAILED]
> bdb(dc=linuxdev,dc=datasphere,dc=ch): Build signature doesn't match
> en
On Tue, 2010-11-23 at 11:23 +0100, Michal Schmidt wrote:
> On Tue, 23 Nov 2010 11:11:13 +0100 Patrick MONNERAT wrote:
> > While applying today's updates on a machine running a slapd server,
> > the following error occurred: [...]
>
> Have you reported it as a bug against the openldap package?
Not
On Tue, 23 Nov 2010 11:11:13 +0100 Patrick MONNERAT wrote:
> While applying today's updates on a machine running a slapd server,
> the following error occurred: [...]
Have you reported it as a bug against the openldap package?
Have you tried yum downgrade to the previous version?
Michal
--
devel
While applying today's updates on a machine running a slapd server, the
following error occurred:
Stopping slapd: [ OK ]
Checking configuration files for slapd: [FAILED]
bdb(dc=linuxdev,dc=datasphere,dc=ch): Build signature doesn't match
environment
bdb_db_open: database "dc=linuxdev,dc=datasphe
22 matches
Mail list logo
