Hi,
> On 28. Feb 2020, at 08:34, scsijon <[email protected]> wrote: > > > No, more problems with build-orders and packages and headers and includes > failing with r49451, even when I 'play' around with revisions and > build-orders after it's failed I keep hitting walls! Enough is Enough! May I suggest to not “play randomly around”? Just look at the build error and understand what is going on. With all the recent feedback I spend days updating and smoothing out things, however, many upstream updates sometimes also result in new conflicts and build errors. And yes, I also do not like it which is why I started to make YT videos about this imperfect state of IT. Additionally I’m getting more and more disappointed by the whole monolithic, everything in C Linux and ecosystem code, which is why I’m starting my own microkernel to be prepared for the future. However, randomly changing stuff and yelling at build errors is not helpful ;-) > I have decided that i'm going back to r49158, which was the last revision I > was able to completely build a 20-minimal with. After checking it builds > properly under the later r49198.iso still, as I had used the r49128.iso > previously to build with, I shall start to update those packages I used for > it in steps until I find what is not working. I suspect there is a package > with either a flaw for building in T2 or a patch missing, so things may > either be quiet from me about this for a while, or there will be yells about > dumb packages. From the other email I wonder if some of the errors you see are from random additional files and mismatched source checkouts. svn st will give you a list of files modified and unverstinoed lingering between the versioned T2 files. In general you should also only svn up the whole T2 tree and not randomly one directory or file here and there. René -- https://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
