Re: Moving KLog to Testing
Relax Adeodato...
It may be seems difficult but it is possible, believe me ;-)
Maybe I has forgotten something... I really do not pretend to know
everything about Debian develop. I would like to but I don't know
everything and sometimes I may make some errors... lucky you that you
don't.
However I read the following sentence: "Not touching package, as requested
by freeze (contact debian-release if update is needed)" in the excuses
page of KLog[1].
So I just thought that contacting debian-release could be the solution, it
seems that it is not. Thank you for your help.
Yes, I though that maybe the debian-release team could move a package to
testing. Dependencies of KLog in testing are not satisfied but just
because of the hamlib's version in unstable. KLog work even with the
stable hamlib.
I supposed that people in this mailing list could help or at least send me
some links to learn how I could work to put KLog in testing if it is
possible (maybe forcing the dependencies to a lower version of hamlib) as
I suppose people in this list knows about that kind of issue. I though it
is not the first time you have to deal with something like this.
If you don't want to loose your time, don't do it Adeodato but I am sure
you can be more polite, even if you think I should leave the project or
redo the NM.
Relax... and, if I can suggest something I would like to tell you to enjoy
developing and allow others to do it. Debian develop has to be fun or many
people will leave the project. I am sure this is not your objective.
Regarding my activity in the list, this is the SECOND mail I am sending...
so the time you have lost because of my messages here is not much.
I will not enter in a flamewar. I simply don't understand, what I think,
your overreaction.
Sorry for any inconveniences.
Regards.
Jaime
[1] http://qa.debian.org/excuses.php?package=klog
> I would like to reply to your message in a calmly way, but it's proving
> very difficult, because this is not the first nor the second time you do
> something akin to this. Ignorance is not outrageous, not at all, but
> repeated failure to take up on the suggestions that yours needs
> addressing,
> certainly is.¹
>
> (¹) For those reading along, much of this happened in the devel-spanish
> mailing list AFAICR.
>
> You lack knowledge about a lot of things a Developer should know about.
> I don't know if you used to know about them back when you did NM, and
> you forgot, or what happened there. I would like to tell you: «If you
> feel your lack of knowledge is preventing you from exercising your DD
> duties with responsibility and sucess, perhaps you should consider
> unofficially redoing NM.» But I'm not going to say that, because it's
> obvious you wouldn't deem it necessary. So I'm going to say to you: «You
> really need to clue up, and a good way would be grabbing the NM templates,
> read upon the subjects covered, and have your answers reviewed by some
> AM.»
>
> If you fail to clue up, I'll find it very hard to reply constructively
> to your (admittedly not very frequent) mails on this list, so I'll just
> pass and let some other person deal with them. That surely works.
>
> In case you're wondering what the hell I'm talking about:
>
> * either you are not subscribed to debian-devel-announce, or you are
> not reading messages sent to it, or you are reading them but
> ignoring the part where I asked people not to waste my time, or you
> outsmarted me for I became enlightened that this may not be a waste
> of my time after all.
>
> * you seem to believe that the Release Team can put packages in
> testing even if their dependencies will not be satisfied, because
> the package will work regardless of what dpkg may think of the
> matter. Believing that is bad, very very bad.
>
> With kind regards,
>
> ---
>
>> Hello all, good night,
>
>> I am writting to you because I have seen here:
>> http://qa.debian.org/excuses.php?package=klog
>
>> That I could contact you if needed.
>
>> Well, I think it is needed.
>
>> KLog depends on hamlib but its dependency is not for the unstable
>> release
>> of hamlib. The testing hamlib is enough for KLog.
>
>> The new versions of KLog fixes bugs and I really thing that KLog should
>> be
>> moved to testing.
>
>> Is anything that can be done to add KLog to testing?
>
>> Thank you very much.
>
>
>
> --
> Adeodato Simó dato at net.com.org.es
> Debian Developer adeodato at debian.org
>
> Man is certainly stark mad; he cannot make a flea, yet he makes gods by
> the
> dozens.
> -- Michel de Montaigne
>
Reply to: