2011/10/16 Thomas Spuhler <[email protected]>: > On Sunday, October 16, 2011 10:55:46 am Jani Välimaa wrote: >> 2011/10/16 Thomas Spuhler <[email protected]>: >> > On Sunday, October 16, 2011 09:32:35 am Jani Välimaa wrote: >> >> 2011/10/16 nicolas vigier <[email protected]>: >> >> > On Sun, 16 Oct 2011, Thomas Spuhler wrote: >> >> >> > How exactly are you doing the upload of new sources as the old >> >> >> > sources are never removed from sha1.lst? Old sources should be >> >> >> > removed automatically when using 'mgarepo sync'.. >> >> >> >> >> >> I use mgarepo upload >> >> > >> >> > You should also remove old ones, using 'mgarepo del', or 'mgarepo >> >> > sync', or by editing sha1.lst. >> >> >> >> I tend to upload sources by first downloading new sources, editing new >> >> version to .spec and then using 'mgarepo sync' which uploads new >> >> sources automatically and edits sha1.lst. After that I only need to >> >> commit my changes to .spec and sha1.lst. >> >> >> >> Sometimes, when I'm lazy, I also use 'mgarepo sync -d' which downloads >> >> new sources from upstream and uploads them to mageia binrepos. >> > >> > I usually remove the old sources after the new sources have been built >> > successfully. >> >> If you decide to do so in the future too, please use SILENT in commit >> msg as removing/adding sources without it pollutes the %changelog. >> IMHO there's no need to mention in pkg %changelog when sources are >> added or deleted. > > is there a procedure in the wiki (or somewhere else) explaning this? > I upload source packages with mgarepo upload. > This adds the package to the local sha1.lst file > The the local sha1.lst change has to be committed to the repo and a log entry > is requires, isn't it?
Yes, every commit needs a log message to explain what changed. This commit/log message ends to a pkg %changelog when our BS is building the pkg. You can prevent all this by "silencing the commit msg". See: http://wiki.mandriva.com/en/Development/Packaging/RepositorySystem#.22SILENT.22_changelog_messages
