From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Alexander GQ Gerasiov <gq@cs.msu.su>
Cc: 568303@bugs.debian.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Markus Becker" <mab@comnets.uni-bremen.de>,
"Yegor Yefremov" <yegorslists@googlemail.com>,
linux-can@vger.kernel.org, debian-devel@lists.debian.org
Subject: Re: Bug#568303: can-utils Debian package
Date: Mon, 24 Feb 2014 10:31:27 +0100 [thread overview]
Message-ID: <530B116F.8040203@physik.fu-berlin.de> (raw)
In-Reply-To: <20140224125933.44d8ab7b@snail>
Hi Alexander!
On 02/24/2014 09:59 AM, Alexander GQ Gerasiov wrote:
> Unfortunately I missed to fixup pair of changes when build package,
> that's why second revision was uploaded right after first.
> You are talking about revision -1 which really had some issues.
> Please comment on the last version available.
Sure, I can have a look at the second revision. But you could also
just asked the FTP team to set the package on REJECT to be able
to sort out the issues, then do a clean upload.
I usually try to keep a clean package history.
>> If you had incorporated some of his changes, you'd just have use the
>> default rules file from the template.
>>
>> You should also have asked yourself why Uwe had added those overrides
>> and not just silently commented them out. If someone adds extra
>> overrides, he usually has very good reasons. You should have asked Uwe
>> about that.
> I think you did not get clean with this or that's Uwe who mislead you.
Yep. I misunderstood Uwe. From his first comments it appeared to me
that exactly that had happened. So, I apologize to you Alexander
and take my statements back.
> Those commented out overrides were left in rules file from my previous
> experiments, and not needed anymore. And they have nothing with Uwe's
> package, I believe.
Alright, thanks for the explanation.
> I can count all changes I took from his work:
> Arch: linux-any (totally forget that SocketCAN is Linux specific)
> Several strings in description field.
>
> And that's all. =\
Ok, it appeared to me that the situation was the complete opposite of
that, i.e. you took Uwe's work and put your name onto it.
Thanks for the clarification.
>>
>> The package currently also includes the debian/README.source template
>> and git-related files (.gitignore, gbp.conf).
> Template README.source was also removed in -2 revision.
Good!
> As for .gitignore and gbp.conf, this package is maintained under git
> and git-buildpackage and I see no reason, why thees files should not be
> included in debian/
True. I am using gbp as well and I completely forgot about that. The
files shouldn't pop up in the actual package.
> I think some gbp related info should goes to README.source. One day
> I'll write it.
Good idea!
>>
>> As someone who is sponsoring very often and has some experience with
>> reviewing packages now, can-utils wouldn't have passed my quality
>> requirements in its current state.
> I could not agree with you if we speak about revision -2.
Well, unless you have fixed the copyright issues that Uwe has
mentioned, you will get a REJECT with absolute certainty.
Did you fix the copyright information? Are the sources from
Volkswagen actually covered by a free license?
> Conclusion:
> Looks like Uwe decided that I modified his package, removed him from
> Maintainer and broke all around. And he started offense instead of
> discussion.
Well, you see what poor communication leads to. When you decide
to let him join as a comaintainer, you should communicate such
changes, especially before doing uploads.
>>> Package is in new queue right now and will be soon available in
>>> unstable repository.
>>
>> It's actually been set to not be reviewed before February 28th to be
>> able to discuss this matter first.
> Well, I remember time when packages were held in new for 2-3 months =)
They still are. Depends on the package, Look at zfs-utils which has
been in NEW for 6 months now. Obviously no one dares to touch it.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2014-02-24 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGm1_ktzQgs92L0RxoVYGVhbb88hZi9dQACF8=pazYHouXh-1w@mail.gmail.com>
[not found] ` <4947876.WXEsvsyjiy@shelbyville.comnets.uni-bremen.de>
[not found] ` <20140115200207.512cf5e8@snail>
[not found] ` <20140123183951.GA20892@perseus.defre.xn--kleine-knig-yfb.de>
2014-02-20 9:51 ` Bug#568303: can-utils Debian package Uwe Kleine-König
2014-02-20 13:30 ` Alexander Gerasiov
2014-02-20 14:39 ` Uwe Kleine-König
2014-02-24 6:44 ` Alexander GQ Gerasiov
2014-02-24 7:08 ` John Paul Adrian Glaubitz
2014-02-24 8:25 ` Uwe Kleine-König
2014-02-24 9:18 ` John Paul Adrian Glaubitz
2014-02-24 8:59 ` Alexander GQ Gerasiov
2014-02-24 9:31 ` John Paul Adrian Glaubitz [this message]
2014-02-24 10:04 ` Uwe Kleine-König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530B116F.8040203@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=568303@bugs.debian.org \
--cc=debian-devel@lists.debian.org \
--cc=gq@cs.msu.su \
--cc=linux-can@vger.kernel.org \
--cc=mab@comnets.uni-bremen.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yegorslists@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.