Indeed. Actually when new builds did not overwrite old packages, built from the same project, it led to much more problems with updates/installs and build chroots. BTW you can republish old builds of ncurses in order to replace new packages. I can also replace files manually, but i need an exact repo name, list of files to remove and links to the old packages, that should be placed there instead.
2014-04-05 20:48 GMT+04:00 Denis Silakov <[email protected]>: > 05.04.2014 20:02, Paulo César Pereira de Andrade пишет: > > Hi, >> >> I cannot work on cooker for 24 hours now, I pinged in irc when >> detected the problem but nobody commented :-( >> >> The issue is that ncurses was updated, and it changed major of >> libncursesw. It did properly follow Mandriva libname specs changing >> the major of the package, e.g. changed libncursesw5 to libncursesw6, >> *but* when publishing, "abf" just removed all packages generated >> by the previous ncurses, that included libncursesw5. >> >> Now the cooker build system is broken because it cannot install >> bash, that requires libncursesw5. >> >> Some months ago this issue had raised, about Mandriva library >> specs, and where I told I had been using fedora semantics for >> several of my packages, since I knew the abf issue, and was >> not against it, but we need to change policy or change how abf >> works when there is a soname bump. >> >> Anyway, to fix the cooker issue, I hereby request some kind of >> abf access, maybe a way to upload files, e.g. rebuild bash >> locally with the newer libncursesw (but I would do it only for >> i586 and x86_64) and upload it, at least this way I would not >> be blocked from working for at least 24 hours. >> > > This is the way the abf followed since the very beginning and nothing was > changed since then. You just had to build new curses to a separate > container without publishing it, then rebuild bash and other crucial > programs using that container and then publish all of them at once. Since > you have already published the new ncurses - well, you have a chance to > publish older version if some of older build lists are still available. > Surely, you can ask somebody with root access to publish some packages > manually, but this is a question for cooker admins. > > And well, feel free to propose your patches to abf - build/publishing > scripts are available at abf/mdv-scripts projects. Yes, we have discussed > this question earlier, but there were no patches suggested, only > discussion. As for ROSA, we prefer to follow stricter policies and rebuild > all packages depending on some library when this library changes soname. > Usage of containers allows us to do this without breaking the chroot. > > -- > Regards, > Denis. > >
