On Sat, May 21, 2005 at 09:08:34PM +0200, Christian Hammers wrote:
> On 2005-05-19 Steve Langasek wrote:
> > > Thus BDB support could now complete been removed as luckily support for
> > > BDB was not present on most architectures, disabled by default and
> > > being warned at startup for a while n
On Sun, May 22, 2005 at 12:01:58AM +0200, Adrian Bunk wrote:
> On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
> >...
> > I see the same three options. Joey has said he is working on a final woody
> > point release for the last weekend in May; you'll probably need to
> > coordinate
On Thu, May 19, 2005 at 08:35:03AM -0700, Steve Langasek wrote:
> On Thu, May 19, 2005 at 05:08:28PM +0200, GOMBAS Gabor wrote:
> > On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
>
> > > 3 does not sound so bad to me; it's arguably user error anyway to replace
> > > a
> > > packa
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
>...
> I see the same three options. Joey has said he is working on a final woody
> point release for the last weekend in May; you'll probably need to
> coordinate with him and get something uploaded soon if you want to try for
> this
On Wed, May 18, 2005 at 05:33:01PM -0400, sean finney wrote:
> On Wed, May 18, 2005 at 11:00:29PM +0200, Adrian Bunk wrote:
>...
> > Other issues like #308762 are also still possible on direct
> > mysql-server/woody -> mysql-server-4.1/sarge upgrade paths - and
> > there will be users doing such up
Hello Steve
On 2005-05-19 Steve Langasek wrote:
> > Thus BDB support could now complete been removed as luckily support for
> > BDB was not present on most architectures, disabled by default and
> > being warned at startup for a while now and will most likely be removed in
> > 5.0 upstream anyway.
hey,
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
> I see the same three options. Joey has said he is working on a final woody
> point release for the last weekend in May; you'll probably need to
> coordinate with him and get something uploaded soon if you want to try for
> thi
hey,
On Thu, May 19, 2005 at 08:35:03AM -0700, Steve Langasek wrote:
> > > 3 does not sound so bad to me; it's arguably user error anyway to replace
> > > a
> > > package-provided directory with a symlink in this manner
>
> > If you consider this an user error, then what is the officially blesse
On Thu, May 19, 2005 at 02:16:55AM +0200, Christian Hammers wrote:
> On 2005-05-18 Roberto C. Sanchez wrote:
> > Quoting sean finney <[EMAIL PROTECTED]>:
> >
> > > so at this point, we're not sure what to do to cover this last problem,
> > > as we have no guarantee the preinst of mysql-server-4.1
Hello
[1st RC issue - dpkg removes symlinks when upgrading from 3.23]
As discussed before in some corner cases we can do nothing except
for showing the user an explanation what happened which has been
done in 4.1.11a-2 and 4.0.24-10.
[2nd RC issue - statically linked db3]
> The new bug #30896
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
> 3 does not sound so bad to me; it's arguably user error anyway to replace a
> package-provided directory with a symlink in this manner
If you consider this an user error, then what is the officially blessed
way of relocating a pack
On Thu, May 19, 2005 at 05:08:28PM +0200, GOMBAS Gabor wrote:
> On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote:
> > 3 does not sound so bad to me; it's arguably user error anyway to replace a
> > package-provided directory with a symlink in this manner
> If you consider this an us
Hello
On 2005-05-19 Steve Langasek wrote:
...
> > so we've come up with three options, none of which are great:
>
> > 1 the most recenty woody security update caused problems for some
> > people, and there's a package already waiting to go in to fix this
> > problem. we could put a fix into
Hi Sean,
On Wed, May 18, 2005 at 11:23:35AM -0400, sean finney wrote:
> the following upgrade paths work:
> mysql-server/woody -> mysql-server/sarge
> mysql-server/woody -> mysql-server/sarge -> mysql-server-4.1/sarge
> but this does not:
> mysql-server/woody -> mysql-server-4.1/sarge
> so at
Christian Hammers wrote:
> Hello
>
> [1st issue - dpkg symlink bug workaround]
>
> On 2005-05-18 Roberto C. Sanchez wrote:
>
>>Quoting sean finney <[EMAIL PROTECTED]>:
>>
>>
>>>so at this point, we're not sure what to do to cover this last problem,
>>>as we have no guarantee the preinst of mysql
Hello
[1st issue - dpkg symlink bug workaround]
On 2005-05-18 Roberto C. Sanchez wrote:
> Quoting sean finney <[EMAIL PROTECTED]>:
>
> > so at this point, we're not sure what to do to cover this last problem,
> > as we have no guarantee the preinst of mysql-server-4.1 will even run
> > before my
On Wed, May 18, 2005 at 11:23:35AM -0400, sean finney wrote:
>...
> the following upgrade paths work:
>
> mysql-server/woody -> mysql-server/sarge
> mysql-server/woody -> mysql-server/sarge -> mysql-server-4.1/sarge
>
> but this does not:
>
> mysql-server/woody -> mysql-server-4.1/sarge
>
> so
On Wed, May 18, 2005 at 11:00:29PM +0200, Adrian Bunk wrote:
> 4 drop mysql-dfsg-4.1 from unstable/sarge
not exactly an attractive option, but i guess everything is on
the table at this point so it's worth bringing up... the reverse
dependencies aren't nearly as severe as i had assumed, actually,
Quoting sean finney <[EMAIL PROTECTED]>:
so at this point, we're not sure what to do to cover this last problem,
as we have no guarantee the preinst of mysql-server-4.1 will even run
before mysql-server/woody is removed. the only fix we can think of is
to remove the two directories from the files
(please excuse the cross-posting, i felt it was necessary to get all
affected parties' input)
hi,
for some time now, christian and i have been trying to build in a
workaround for a rather tricky bug in the mysql-server and
mysql-server-4.1 packages, and we'd like to field some comments
on what o
20 matches
Mail list logo
