Re: [PATCH] OSTree: Force to create new ostree commit during updates compose run

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 06/29/2018 11:14 AM, Sinny Kumari wrote:
> This patch (available in email attachment) is to create new ostree
> commit when there is no content changes since last commit during
> updates compose run. By passing force_new_commit as True, pungi
> runs rpm-ostree command with option --force-nocache .
> 
> More details are in releng ticket - https://pagure.io/releng/issue/7585
> 
> Thanks,
> Sinny


Thanks Sinny. Can I ask for one change? We actually want "force_new_commit"
only for Atomic Host. For Atomic Workstation/Silverblue we actually don't
want "force_new_commit" because we don't do any formal releases (i.e. 2
week releases) for them and "force_new_commit" actually causes them to get
empty updates.

WDYT?

Dusty 
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx/message/TVDQGWW7QH53OSG3PE7GUNUEGUMSQEU2/




[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux