No worries, I wasn’t particularly quick with my response. What you sent looks good to me. I will reply to those emails once I review them.
> On 16 Jun 2026, at 12:47, Matthias Fischer <[email protected]> > wrote: > > On 16.06.2026 13:20, Michael Tremer wrote: >> Hello Matthias, > > Hi Michael, > >> Yes, this is a bug update because there are plenty of modules built after >> the main package. >> >> The best way would be to update them one by one - i.e. commit them one by >> one. But since this is a lot, I would be happy to listen to any other >> proposals. > > Ups. Just saw your mail - a few seconds after I pushed the whole thing, > sorry. > > Take a look and decide - its really huge... ;-) > > Best > Matthias >> Best, >> -Michael >> >>> On 14 Jun 2026, at 22:04, Matthias Fischer <[email protected]> >>> wrote: >>> >>> Hi, >>> >>> On 12.06.2026 13:19, Adolf Belka wrote: >>>> ... >>>> Feel free to do so but maybe you should also look at updating the perl >>>> package itself. >>>> ... >>> >>> I did. But I'm not quite sure what to do next and need a hint. >>> >>> After "a few" rootfile-adjustments I got a build based on 'next' with >>> 'perl 5.42.2' that is building without any errors. No seen problems. >>> >>> Adjusting the rootfile for the new perl version was a bit...extensive, >>> but I think I managed it. Build is running without any errors. >>> >>> But there are about 70 rootfiles from 'common' to 'packages' who thought >>> they were all alone now and wanted to come along. They all contained the >>> perl version string '5.36.0', which now had to be changed to 5.42.2. >>> >>> I think I need to push these files together with the actual perl update. >>> This will take some place for an update... Since this is my first perl >>> update I was a bit surprised how many files were affected. >>> >>> Would this be ok? Updating perl leads to about ~70 files that need to be >>> updated too and pushed because of changed rootfiles? >>> >>> Best >>> Matthias >>> >>> >> >> >
