Re: Bug#1054657: transition: r-bioc-biocgenerics
Le Thu, Nov 09, 2023 at 02:01:57PM +0100, Paul Gevers a écrit :
>
> The first and foremost reason why we're not enthusiastic about defaulting to
> removal of packages from testing is that that's a disservice to our users of
> testing.
Hi Paul,
I understand that you feel responsible for the state of testing, but
please consider that the r-bioc-* package users are our users too. Some
of them are our colleagues, or our friends. Those who we do not know,
we see their blogs, their toots, their Dockerfiles. We meet them at
conferences. We also feel responsible and we have the intuition that
having the packages absent from testing for a couple of weeks is not
going to cause too much trouble.
> I have the *feeling* (which might be unjust, but then consider past
> interactions) that we often need to tell you about issues and how to solve
> them.
A lot of the issues are due to continuous integrations tests, where we
uncover bugs on architectures unsupported upstream (who only builds on
amd64 and Apple arm64). One of the reasons we sometimes take time to
make a visible action in response to CI failures is that we, like you,
are limited in our time. But if this is important for you we can surely
write ack messages faster.
> If the r-bioc team were to actively monitor the situation
I read the R and Bioc devel mailing list. I am upstream developer of a
Bioconductor package. Yes, I have been caught by surprise in the last
transition by the addition of new packages at the core of the dependency
tree. Yes, reputation is easy to lose and hard to gain. If I tell you
that I have been more careful because I wanted to avoid it to happen
again, you are free to think that the previous mistake proves my
incompetence, and that it means that my care and monitoring are useless.
This is what I feel when I see the new request from your team coming at
the last minute and not as a debriefing of the previous transition.
> Several other ecosystems, e.g. perl, python and ruby, do preparation outside
> of the Debian archive and often have some idea (or know quite well) of what
> to expect during the transition. It's that pro-activeness that makes a
> difference to us; it *sounds* much better than "let's start and find out how
> much work it is". Maybe it's just the tone, but we're all humans.
Please trust us this time, and if you think that next time you need to
monitor our monitoring, I can for instance toot regularly under a
pre-decided hashtag about our preparation and you can review it at the
time of the transition, (in about 5 months; the clock is ticking).
Have a nice day,
Charles
--
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from home https://framapiaf.org/@charles_plessy
- You do not have my permission to use this email to train an AI -
Reply to: