[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#63347: tcsh-i18n: Incorrect dependancy



On 00-05-13 Luis Francisco Gonzalez wrote:
> > On 00-05-10 Luis Francisco Gonzalez wrote:
> > > Christian Kurz wrote:
> > > > On 00-05-06 Josip Rodin wrote:
> > > > > On Sat, May 06, 2000 at 08:19:29AM +0200, Christian Kurz wrote:
> > > > > > > tcsh-i18n does *not* depend on tcsh-kanji-user, it depends on
> > > > > > > "tcsh (>= 6.08.01-3) | tcsh-kanji". Certainly, this is not *a* package 
> > > > > > > having a lower priority value but a combination of several packages.
> > > > > > 
> > > > > > Hm, you forget there there a lot of user of tcsh-kanji. And for those
> > > > > > this is the case and you are wrong. We should fix such bugs as they make
> > > > > > it hard for every user who needs kanji-support and I would say that this
> > > > > > are lot of people of the eastern timezone.
> > > > 
> > > > > We can't go lower the priority of tcsh or raise the priority of tcsh-kanji
> > > > > just to satisfy a dependency for a minority of users.
> > > > 
> > > > > > > Do you claim that each and every MTA should be of important priority
> > > > > > > because of the rule about dependencies and priorities? This is 
> > > > > > > impossible, since only one MTA package may be of important priority, 
> > > > > > > the others should be of extra priority.
> > > > > > 
> > > > > > This is completely different to the problem above. You can compare the
> > > > > > problem with real existing package that have not satisfied dependancys
> > > > > > with packages that depends on virtual-packets. This are completely
> > > > > > different, so please don't mix them up.
> > > > 
> > > > > I think the comparison is quite applicable, this is not a bug.
> > > > 
> > > > > Consider this: a lot of packages have a dependency on perl5 | perl, to
> > > > > enable slink users to use the package without installing whole bunch of
> > > > > newer perl packages. However, perl is now a Priority: extra package.
> > > > > Do you _really_ want to file a bug report one each of those just because
> > > > > they're being a bit backwards compatible? Please don't.
> > > > 
> > > > No, but I make a decision between a shell, with which you do your daily
> > > > work and applications. And tcsh-kanji is a shell for users in the
> > > > eastern part of the world. So in my opinion it's important to fix the
> > > > dependancy to create no problems when installing tcsh-kanji. So _this_
> > > > bug should be fixed. You always need to clearly look what the program
> > > > does and then decide to fill a bug or not.
> > > So that I understand how this affects people. Could you please elaborate
> > > as to how this is problematic to tcsh-kanji users? Could you give a situation
> > > where that would lead to them not being able to have the combination of
> > > packages they would like?
> > 
> > What? Didn't you read the policy section 2.2? 
> You know, this comment doesn't really help. I really want to understand what

Why doesn't this help? I tell you, the exact location, where you can
read the statement in the debian policy how a dependancy should be and
how it should be not. So why is it not helpful?

> problem *this* specific combination causes. You seem to think that this won't
> allow people to use tcsh-kanji in the intended way. Could you please explain
> in what way this is the case?

Yes, because it violates our policy. If such a violation of our policy
of standard-shell is acceptable, I better leave this project. I think we
used the dependancy-system to make it easier for people to install
packages and create the policy with this in mind. If we now start
violating the policy and ignore it and it's content, I'm should really
start thinking about this project and if I should invest still my time
for it.

> > So currently tcsh-i18n is violating our policy and if anybody thinks
> > this is okay, he should better work on fixing our policy. Otherwise we
> > should discuss this on debian-devel, but I won't ignore our policy in
> > these cases.
> Policy also states that the developer does have the power over the packages.
> Until I understand why the combination of tcsh/tcsh-kanji/tcsh-i18n is 
> problematic I will in fact ignore this completely.

And as I hate to see such a policy violation, I will sent a copy of this
statement of me to debian-devel, so that everybody understands me and
the reactions which may follow.

Ciao
     Christian
-- 
#!/bin/perl -s-- -export-a-crypto-system-sig -RSA-3-lines-PERL
$m=unpack(H.$w,$m."\0"x$w),$_=`echo "16do$w 2+4Oi0$d*-^1[d2%Sa
2/d0<X+d*La1=z\U$n%0]SX$k"[$m*]\EszlXx++p|dc`,s/^.|\W//g,print
pack('H*',$_)while read(STDIN,$m,($w=2*$d-1+length$n&~1)/2)



Reply to: