On Fri, 2024-03-08 at 03:20 -0800, Zoltan Boszormenyi wrote: > Hi, > > I just found out that if an updated package ships a modified > configuration file, then the Yocto package upgrade does this: > > * rename the edited conffile to conffile.rpmsave > * install the new, modified one from the package > > instead of: > > * keep the edited conffile intact > * install the new, modified one from the package as conffile.rpmnew > > I think this is what was asked in 2017 here: > https://docs.yoctoproject.org/pipermail/yocto/2017-May/036031.html > > The answer was a little uninformed about saying that using > CONFFILES is the fix, because rpm can behave two ways, see above. > > Yocto, to this day, uses "%config /path/to/conffile" instead of > "%config(noreplace) /path/to/conffile" in package_rpm.bbclass. > The latter would behave as "keep modified conffile + install > conffile.rpmnew". > > What's the official stance on this behaviour? > Is it a known issue? > Is this what the project would expect from a package upgrade?
I would be interested to know what the ipk and deb backends do... In some ways, I'd also like to have a test case and then we can define and document what the correct behaviour is too. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196865): https://lists.openembedded.org/g/openembedded-core/message/196865 Mute This Topic: https://lists.openembedded.org/mt/104806483/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
