The bug comes from configuring two instances with the same db user.
dbconfig-common regenerates a random password when configuring
the second instance, wiping the password set for the first instance
that has already been recorded in database.yml.
Workaround : get the password of the second
On 16/12/2012 12:40, Jonas Smedegaard wrote:
I like that our current structures work well for unstable, testing,
stable and oldstable - i.e. that it is only tricky to handle
experimental which we make no promises for anyway.
I suspect the better approach than force-merging with --strategy
Your message dated Sun, 16 Dec 2012 18:21:41 +0100
with message-id
cadk7b0mdevyuw7eskecfdgkaowx-r05nmd4jhn59kmt-yt6...@mail.gmail.com
and subject line Package removed
has caused the Debian Bug report #569876,
regarding libactivesupport-ruby1.9: Please drop the dependency on ruby 1.9.0
to be
Your message dated Sun, 16 Dec 2012 18:20:58 +0100
with message-id
cadk7b0nn7kcaj5psqsxxqdg8rnhl4d-ke4_0khh9kst3wn4...@mail.gmail.com
and subject line Package removed
has caused the Debian Bug report #569871,
regarding libactiverecord-ruby1.9: Please drop the dependency on ruby 1.9.0
to be marked
