Loudly promoting my own software here...
la, 2005-11-12 kello 10:39 -0200, Henrique de Moraes Holschuh kirjoitti:
> On Sat, 12 Nov 2005, Steve Langasek wrote:
> > > Besides, depends/pre-depends and conflicts should be more than enough if
> > > done right.
> >
> > Yes, this is what is meant by sup
On Sat, 12 Nov 2005, Steve Langasek wrote:
> > Besides, depends/pre-depends and conflicts should be more than enough if
> > done right.
>
> Yes, this is what is meant by supporting partial upgrades. "Supporting
Ah, ok. THAT is what I meant too, in a roundabout way. So we're in
agreement.
> pa
> > New shadow would conflict with ALL packages that do not support the new
> > syntax
>
> Unfortunately, yes; and we saw plenty of occasions in woody->sarge where
> conflicts with old packages made the upgrade path more difficult than it
> should have been...
Up to now, we have identified pbui
On Fri, Nov 11, 2005 at 10:04:47AM -0200, Henrique de Moraes Holschuh wrote:
> On Fri, 11 Nov 2005, Bill Allombert wrote:
> > Whatever you choose to do, you need to take care of partial upgrade.
> Not across released stable versions! Since when do we support
> stable/stable+1 mixed systems?
Since
> e.g. you cannot fix Sarge pbuilder anyway, so etch su must work with sarge
> pbuilder. That why it would have been better to announce the change before
> Sarge release.
Maybe, but unfortunately, this bug was properly analysed a few weeks
*after* sarge release. Remember, there were over 150 ope
> FWIW, pbuilder in sid is fixed since 0.129 (17 August 2005),
> and I am hoping that will
> probagate into some stable backports, so that practically,
> pbuilder side is ready for the new su.
Well, this is actually great news as pbuilder was by far the main
blocker for this change. Sorry for ha
Hi,
> > support for that change (like POSIXLY_CORRECT)
> >
> > Then change.
> >
> > We've got quite a bit of tools in sarge that doesn't work with
> > this change, right?
>
>
> >From what Nicolas investigated, not that much. He only found dchroot
> and pbuilder up to now. Nicolas does not pret
> The ideal way to approach this is to announce a change,
Which is what we are doing now. We neglected to do so the first time
(mostly because we didn't anticipate this would break pbuilder so
much) and this is why we reverted the change very quickly.
> document that change, provide some envir
Hi,
> > > We would now like to get rid of this bug. What do you recommend:
> > > * keep a Debian specific implementation and tag this bug wontfix
> > > * reapply the patch to fix this bug, and report bugs on the packages that
> > >uses this "feature"
> >
> > Could you document and wait unti
On Fri, 11 Nov 2005, Bill Allombert wrote:
> Whatever you choose to do, you need to take care of partial upgrade.
Not across released stable versions! Since when do we support
stable/stable+1 mixed systems?
Besides, depends/pre-depends and conflicts should be more than enough if
done right. New
On Sun, Nov 06, 2005 at 11:14:39PM +0100, Nicolas Fran?ois wrote:
> Hi,
>
> In #276419, the bug submitter complained that when a command and some
> arguments were passed to su, all these arguments were concatenated, and
> provided to the shell -c option.
>
> This behavior differs from su on other
Quoting Junichi Uekawa ([EMAIL PROTECTED]):
> > We would now like to get rid of this bug. What do you recommend:
> > * keep a Debian specific implementation and tag this bug wontfix
> > * reapply the patch to fix this bug, and report bugs on the packages that
> >uses this "feature"
>
> Coul
Hi,
> Unfortunately, this broke pbuilder (see #317264), and other Debian
> packages (e.g. dchroot). So this patch was (at least temporarily) removed,
> and the current behavior documented.
>
>
> We would now like to get rid of this bug. What do you recommend:
> * keep a Debian specific implemen
Hi,
In #276419, the bug submitter complained that when a command and some
arguments were passed to su, all these arguments were concatenated, and
provided to the shell -c option.
This behavior differs from su on other systems [0].
This also forbid to pass arguments to the shell [1].
As these beh
14 matches
Mail list logo
