Re: Bioconductor 3.19 transition
Hi Michael,
Le Thu, Jul 11, 2024 at 12:22:32PM +0200, Michael R. Crusoe a écrit :
> If there are no objections, I'd like to upload the new r-bioc-biocgenerics to experimental and continue on with the rest of bioconductor 3.19
I do not want to stop you doing it, but I have a question.
> ```
> git checkout -b debian/experimental
> routine-update --no-build --experimental --branch debian/experimental -t
Great news that we have it and sorry that I overlooked it.
Is there also a trick for automatically merging the experimental branch
into master once we start uploading to unstable ?
Apart from that,
> I understand that. Did we have problems skipping releases before?
I think that we never skipped releases. The main problem is that the
old release causes incompatibilities in Testing. Last time, I proposed
to skip a release and remove the packages from Testing in the meantime,
but the Release team refused to do so. This is one of the reasons I
took time this time: I wanted to see if something would happen if we
would wait for autoremoval. The answer is no, nothing happens and the
release team does not complain. If it makes the migration simpler, next
time I want to ask again the release team again to kindly help us by
removing the old BioC packages from testing.
> As it was, I had to do a local build of over 90 bioc packages to confirm that the newly needed packages for 3.19 worked.
> So it would be about another 80 packages to update, which I don't mind doing now that I've gotten practive.
That is really great. Can you share the part of your gbp configuration
that allows sbuild to pick locally built packages to resolve
dependencies? Do you run autopktest through sbuild's hooks?
> If they are 32-bit issues, then I'm fine with excluding them using
> `architecture-is-64-bits` and allowing the relevant autopkgtests to
> skip archs where the dependencies aren't available.
I think that 32-bit issues are bound to pop up with time, in an
unpredictable frequency. I fear that adding architecture-is-64-bits
information package per package on a case-by-case basis is going to be
quite some work. Opening bugs, closing bugs, adding patches, removing
patches. And I am not aware of Bioconductor does not support non-64 bit
arches. I will not stand on the way of people working on providing
32-bit surpport for Bioconductor in Debian. But if there is no appetite
or excitement for that task, why don't we take the opportunity of this
Bioc release for adding architecture-is-64-bits everywhere?
Have a nice day,
Charles
--
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from work, https://fediscience.org/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy
Reply to: